Remove doc-xc directory and supporting infrastructure to build XC docs

We now change the documentation in-place and hence don't need this additional
copy of the docs. The doc changes are already rebased on the original 9.5 docs
per previous commit

385 files changed, 10 insertions, 296261 deletions

diff --git a/GNUmakefile.in b/GNUmakefile.in
index 8bbd1cb83d..15fba9fce0 100644
--- a/GNUmakefile.in
+++ b/GNUmakefile.in
@@ -14,9 +14,9 @@ all:
 	+@echo "All of PostgreSQL successfully made. Ready to install."
 
 docs:
-	$(MAKE) -C doc-xc all
+	$(MAKE) -C doc all
 
-$(call recurse,world,doc-xc src config contrib,all)
+$(call recurse,world,doc src config contrib,all)
 world:
 	+@echo "PostgreSQL, contrib, and documentation successfully made. Ready to install."
 
@@ -24,28 +24,28 @@ world:
 world-contrib-recurse: world-src-recurse
 
 html man:
-	$(MAKE) -C doc-xc $@
+	$(MAKE) -C doc $@
 
 install:
 	+@echo "PostgreSQL installation complete."
 
 install-docs:
-	$(MAKE) -C doc-xc install
+	$(MAKE) -C doc install
 
-$(call recurse,install-world,doc-xc src config contrib,install)
+$(call recurse,install-world,doc src config contrib,install)
 install-world:
 	+@echo "PostgreSQL, contrib, and documentation installation complete."
 
 # build src/ before contrib/
 install-world-contrib-recurse: install-world-src-recurse
 
-$(call recurse,installdirs uninstall coverage init-po update-po,doc-xc src config)
+$(call recurse,installdirs uninstall coverage init-po update-po,doc src config)
 
-$(call recurse,distprep,doc-xc src config contrib)
+$(call recurse,distprep,doc src config contrib)
 
 # clean, distclean, etc should apply to contrib too, even though
 # it's not built by default
-$(call recurse,clean,doc-xc contrib src config)
+$(call recurse,clean,doc contrib src config)
 clean:
 	rm -rf tmp_install/
 # Garbage from autoconf:
@@ -54,7 +54,7 @@ clean:
 # Important: distclean `src' last, otherwise Makefile.global
 # will be gone too soon.
 distclean maintainer-clean:
-	$(MAKE) -C doc-xc $@
+	$(MAKE) -C doc $@
 	$(MAKE) -C contrib $@
 	$(MAKE) -C config $@
 	$(MAKE) -C src $@
diff --git a/doc-xc/KNOWN_BUGS b/doc-xc/KNOWN_BUGS
deleted file mode 100644
index 44dd8812b7..0000000000
--- a/doc-xc/KNOWN_BUGS
+++ /dev/null
@@ -1,3 +0,0 @@
-PostgreSQL has a single combined bugs, missing features, and todo list
-simply called TODO, in this directory.  A current copy is always
-available on our web site.
diff --git a/doc-xc/MISSING_FEATURES b/doc-xc/MISSING_FEATURES
deleted file mode 100644
index 44dd8812b7..0000000000
--- a/doc-xc/MISSING_FEATURES
+++ /dev/null
@@ -1,3 +0,0 @@
-PostgreSQL has a single combined bugs, missing features, and todo list
-simply called TODO, in this directory.  A current copy is always
-available on our web site.
diff --git a/doc-xc/Makefile b/doc-xc/Makefile
deleted file mode 100644
index 2e5e09ef88..0000000000
--- a/doc-xc/Makefile
+++ /dev/null
@@ -1,16 +0,0 @@
-#----------------------------------------------------------------------------
-#
-# PostgreSQL documentation top-level makefile
-#
-# Copyright (c) 1994, Regents of the University of California
-#
-# doc/Makefile
-#
-#----------------------------------------------------------------------------
-
-subdir = doc
-top_builddir = ..
-include $(top_builddir)/src/Makefile.global
-
-all distprep html man install installdirs uninstall clean distclean maintainer-clean maintainer-check:
-	$(MAKE) -C src $@
diff --git a/doc-xc/README.mb.big5 b/doc-xc/README.mb.big5
deleted file mode 100644
index 529af95591..0000000000
--- a/doc-xc/README.mb.big5
+++ /dev/null
@@ -1,326 +0,0 @@
-PostgreSQL 7.0.1 multi-byte (MB) support README	  May 20 2000
-
-						Tatsuo Ishii
-						[email protected]
-		  http://www.sra.co.jp/people/t-ishii/PostgreSQL/
-
-[��] 1. �P�¥ۤ��F�� (Tatsuo Ishii) ����!
-     2. �����������ҵL, ��Ķ�Y�����~, ���p�� [email protected]
-
-
-0. ²��
-
-MB �䴩�O���F�� PostgreSQL ��B�z�h�줸�զr�� (multi-byte character),
-�Ҧp: EUC (Extended Unix Code), Unicode (�Τ@�X) �M Mule internal code
-(�h��y�����X). �b MB ���䴩�U, �A�i�H�b���W���ܦ� (regexp), LIKE ��
-��L�@�Ǩ禡���ϥΦh�줸�զr��. �w�]���s�X�t�Υi���M��A�w�� PostgreSQL
-�ɪ� initdb(1) �R�O, ��i�� createdb(1) �R�O�Ϋإ߸�Ʈw�� SQL �R�O�M�w.
-�ҥH�A�i�H���h�Ӥ��P�s�X�t�Ϊ���Ʈw.
-
-MB �䴩�]�ѨM�F�@�� 8 �줸��줸�զr���� (�]�t ISO-8859-1) ���������D,
-(�ڨèS�����Ҧ����������D���ѨM�F, �ڥu�O�T�{�F�j�k���հ��榨�\,
-�Ӥ@�Ǫk�y�r���b MB �׸ɤU�i�H�ϥ�. �p�G�A�b�ϥ� 8 �줸�r���ɵo�{�F
-������D, �гq����)
-
-1. �p��ϥ�
-
-�sĶ PostgreSQL �e, ���� configure �ɨϥ� multibyte ���ﶵ
-
-	% ./configure --enable-multibyte[=encoding_system]
-	% ./configure --enable-multibyte[=�s�X�t��]
-
-�䤤���s�X�t�Υi�H���w���U���䤤���@:
-
-	SQL_ASCII		ASCII
-	EUC_JP			Japanese EUC
-	EUC_CN			Chinese EUC
-	EUC_KR			Korean EUC
-	EUC_TW			Taiwan EUC
-	UNICODE			Unicode(UTF-8)
-	MULE_INTERNAL		Mule internal
-	LATIN1			ISO 8859-1 English and some European languages
-	LATIN2			ISO 8859-2 English and some European languages
-	LATIN3			ISO 8859-3 English and some European languages
-	LATIN4			ISO 8859-4 English and some European languages
-	LATIN5			ISO 8859-5 English and some European languages
-	KOI8			KOI8-R
-	WIN			Windows CP1251
-	ALT			Windows CP866
-
-�Ҧp:
-
-	% ./configure --enable-multibyte=EUC_JP
-
-�p�G�ٲ����w�s�X�t��, ����w�]�ȴN�O SQL_ASCII.
-
-2. �p��]�w�s�X
-
-initdb �R�O�w�q PostgresSQL �w�˫᪺�w�]�s�X, �Ҧp:
-
-	% initdb -E EUC_JP
-
-�N�w�]���s�X�]�w�� EUC_JP (Extended Unix Code for Japanese), �p�G�A���w
-�������r��, �A�]�i�H�� "--encoding" �Ӥ��� "-E". �p�G�S���ϥ� -E ��
---encoding ���ﶵ, ����sö�ɪ��]�w�|�����w�]��.
-
-�A�i�H�إߨϥΤ��P�s�X����Ʈw:
-
-	% createdb -E EUC_KR korean
-
-�o�өR�O�|�إߤ@�ӥs�� "korean" ����Ʈw, �Ө�ĥ� EUC_KR �s�X.
-�t�~���@�Ӥ�k, �O�ϥ� SQL �R�O, �]�i�H�F��P�˪��ت�:
-
-	CREATE DATABASE korean WITH ENCODING = 'EUC_KR';
-
-�b pg_database �t�γW��� (system catalog) �����@�� "encoding" �����,
-�N�O�ΨӬ����@�Ӹ�Ʈw���s�X. �A�i�H�� psql -l �ζi�J psql ��� \l ��
-�R�O�Ӭd�ݸ�Ʈw�ĥΦ�ؽs�X:
-
-$ psql -l
-            List of databases
-   Database    |  Owner  |   Encoding    
----------------+---------+---------------
- euc_cn        | t-ishii | EUC_CN
- euc_jp        | t-ishii | EUC_JP
- euc_kr        | t-ishii | EUC_KR
- euc_tw        | t-ishii | EUC_TW
- mule_internal | t-ishii | MULE_INTERNAL
- regression    | t-ishii | SQL_ASCII
- template1     | t-ishii | EUC_JP
- test          | t-ishii | EUC_JP
- unicode       | t-ishii | UNICODE
-(9 rows)
-
-3. �e�ݻP��ݽs�X���۰��ഫ
-
-[��: �e�ݪx���Ȥ�ݪ��{��, �i��O psql �R�O��Ķ��, �αĥ� libpq �� C 
-�{��, Perl �{��, �Ϊ̬O�z�L ODBC ���������ε{��. �ӫ�ݴN�O�� PostgreSQL
-��Ʈw�����A�{��]
-
-PostgreSQL �䴩�Y�ǽs�X�b�e�ݻP��ݶ����۰��ഫ: [��: �o�̩ҿת��۰�
-�ഫ�O���A�b�e�ݤΫ�ݩҫŧi�ĥΪ��s�X���P, ���u�n PostgreSQL �䴩�o
-��ؽs�X�����ഫ, ���򥦷|���A�b�s���e���ഫ]
-
-  encoding of backend			available encoding of frontend
-  --------------------------------------------------------------------
-	EUC_JP				EUC_JP, SJIS
-  
-	EUC_TW				EUC_TW, BIG5
-  
-  	LATIN2				LATIN2, WIN1250
-  
-	LATIN5				LATIN5, WIN, ALT
-  
-	MULE_INTERNAL			EUC_JP, SJIS, EUC_KR, EUC_CN, 
-					EUC_TW, BIG5, LATIN1 to LATIN5, 
-					WIN, ALT, WIN1250
-
-�b�Ұʦ۰ʽs�X�ഫ���e, �A�����i�D PostgreSQL �A�n�b�e�ݱĥΦ�ؽs�X.
-���n�X�Ӥ�k�i�H�F��o�ӥت�:
-
-o �b psql �R�O��Ķ�����ϥ� \encoding �o�өR�O
-
-\encoding �o�өR�O�i�H���A���W�����e�ݽs�X, �Ҧp, �A�n�N�e�ݽs�X������ SJIS,
-�����:
-
-	\encoding SJIS
-
-o �ϥ� libpq [��: PostgreSQL ��Ʈw�� C API �{���w] ���禡
-
-psql �� \encoding �R�O���u�O�h�I�s PQsetClientEncoding() �o�Ө禡�ӹF��ت�.
-
-  int PQsetClientEncoding(PGconn *conn, const char *encoding)
-
-�W���� conn �o�ӰѼƥN���@�ӹ��ݪ��s�u, encoding �o�ӰѼƭn��A�Q�Ϊ��s�X,
-���p�����\�a�]�w�F�s�X, �K�|�Ǧ^ 0 ��, ���Ѫ��ܶǦ^ -1. �ܩ�ثe�s�u���s�X�i
-�Q�ΥH�U�禡�d��:
-
-  int PQclientEncoding(const PGconn *conn)
-
-�o�̭n�`�N���O: �o�Ө禡�Ǧ^���O�s�X���N�� (encoding id, �O�Ӿ�ƭ�),
-�Ӥ��O�s�X���W�٦r�� (�p "EUC_JP"), �p�G�A�n�ѽs�X�N���o���s�X�W��,
-�����I�s:
-
-char *pg_encoding_to_char(int encoding_id)
-
-o �ϥ� PGCLIENTENCODING �o�������ܼ�
-
-�p�G�e�ݩ��]�w�F PGCLIENTENCODING �o�@�������ܼ�, �����ݷ|���s�X�۰��ഫ.
-
-[��] PostgreSQL 7.0.0 ~ 7.0.3 ���� bug -- ���{�o�������ܼ�
-
-o �ϥ� SET CLIENT_ENCODING TO �o�� SQL ���R�O
-
-�n�]�w�e�ݪ��s�X�i�H�ΥH�U�o�� SQL �R�O:
-
-	SET CLIENT_ENCODING TO 'encoding';
-
-�A�]�i�H�ϥ� SQL92 ���y�k "SET NAMES" �F��P�˪��ت�:
-
-	SET NAMES 'encoding';
-
-�d�ߥثe���e�ݽs�X�i�H�ΥH�U�o�� SQL �R�O:
-
-	SHOW CLIENT_ENCODING;
-
-��������ӹw�]���s�X, �ΥH�U�o�� SQL �R�O:
-
-	RESET CLIENT_ENCODING;
-
-[��] �ϥ� psql �R�O��Ķ����, ��ij���n�γo�Ӥ�k, �Х� \encoding
-
-4. ���� Unicode (�Τ@�X)
-
-�Τ@�X�M��L�s�X�����ഫ�i��n�b 7.1 ����~�|��{.
-
-5. �p�G�L�k�ഫ�|�o�ͤ����?
-
-���]�A�b��ݿ�ܤF EUC_JP �o�ӽs�X, �e�ݨϥ� LATIN1, (�Y�Ǥ��r���L�k�ഫ�� 
-LATIN1) �b�o�Ӫ��p�U, �Y�Ӧr���Y�����ন LATIN1 �r����, �N�|�Q�ন�H�U������:
-
-	(�Q���i���)
-
-6. �ѦҸ��
-
-These are good sources to start learning various kind of encoding
-systems.
-
-ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/cjk.inf
-	Detailed explanations of EUC_JP, EUC_CN, EUC_KR, EUC_TW
-	appear in section 3.2.
-
-Unicode: http://www.unicode.org/
-	The homepage of UNICODE.
-
-	RFC 3629
-	UTF-8 is defined here.
-
-5. History
-
-May 20, 2000
-	* SJIS UDC (NEC selection IBM kanji) support contributed
-	  by Eiji Tokuya
-	* Changes above will appear in 7.0.1
-
-Mar 22, 2000
-	* Add new libpq functions PQsetClientEncoding, PQclientEncoding
-	* ./configure --with-mb=EUC_JP
-	  now deprecated. use 
-	  ./configure --enable-multibyte=EUC_JP
-	  instead
-  	* Add SQL_ASCII regression test case
-	* Add SJIS User Defined Character (UDC) support
-	* All of above will appear in 7.0
-
-July 11, 1999
-	* Add support for WIN1250 (Windows Czech) as a client encoding
-	  (contributed by Pavel Behal)
-	* fix some compiler warnings (contributed by Tomoaki Nishiyama)
-
-Mar 23, 1999
-	* Add support for KOI8(KOI8-R), WIN(CP1251), ALT(CP866)
-	  (thanks Oleg Broytmann for testing)
-	* Fix problem with MB and locale
-
-Jan 26, 1999
-	* Add support for Big5 for fronend encoding
-	  (you need to create a database with EUC_TW to use Big5)
-	* Add regression test case for EUC_TW
-	  (contributed by Jonah Kuo <[email protected]>)
-
-Dec 15, 1998
-	* Bugs related to SQL_ASCII support fixed
-
-Nov 5, 1998
-	* 6.4 release. In this version, pg_database has "encoding"
-	  column that represents the database encoding
-
-Jul 22, 1998
-	* determine encoding at initdb/createdb rather than compile time
-	* support for PGCLIENTENCODING when issuing COPY command
-	* support for SQL92 syntax "SET NAMES"
-	* support for LATIN2-5
-	* add UNICODE regression test case
-	* new test suite for MB
-	* clean up source files
-
-Jun 5, 1998
-	* add support for the encoding translation between the backend
-	  and the frontend
-	* new command SET CLIENT_ENCODING etc. added
-	* add support for LATIN1 character set
-	* enhance 8 bit cleaness
-
-April 21, 1998 some enhancements/fixes
-	* character_length(), position(), substring() are now aware of 
-	  multi-byte characters
-	* add octet_length()
-	* add --with-mb option to configure
-	* new regression tests for EUC_KR
-  	  (contributed by "Soonmyung. Hong" <[email protected]>)
-	* add some test cases to the EUC_JP regression test
-	* fix problem in regress/regress.sh in case of System V
-	* fix toupper(), tolower() to handle 8bit chars
-
-Mar 25, 1998 MB PL2 is incorporated into PostgreSQL 6.3.1
-
-Mar 10, 1998 PL2 released
-	* add regression test for EUC_JP, EUC_CN and MULE_INTERNAL
-	* add an English document (this file)
-	* fix problems concerning 8-bit single byte characters
-
-Mar 1, 1998 PL1 released
-
-Appendix:
-
-[Here is a good documentation explaining how to use WIN1250 on
-Windows/ODBC from Pavel Behal. Please note that Installation step 1)
-is not necceary in 6.5.1 -- Tatsuo]
-
-Version: 0.91 for PgSQL 6.5
-Author: Pavel Behal
-Revised by: Tatsuo Ishii
-Email: [email protected]
-Licence: The Same as PostgreSQL
-
-Sorry for my Eglish and C code, I'm not native :-)
-
-!!!!!!!!!!!!!!!!!!!!!!!!! NO WARRANTY !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
-Instalation:
-------------
-1) Change three affected files in source directories 
-    (I don't have time to create proper patch diffs, I don't know how)
-2) Compile with enabled locale and multibyte set to LATIN2
-3) Setup properly your instalation, do not forget to create locale
-   variables in your profile (environment). Ex. (may not be exactly true):
-	LC_ALL=cs_CZ.ISO8859-2
-	LC_COLLATE=cs_CZ.ISO8859-2
-	LC_CTYPE=cs_CZ.ISO8859-2
-	LC_MONETARY=cs_CZ.ISO8859-2
-	LC_NUMERIC=cs_CZ.ISO8859-2
-	LC_TIME=cs_CZ.ISO8859-2
-4) You have to start the postmaster with locales set!
-5) Try it with Czech language, it have to sort
-5) Install ODBC driver for PgSQL into your M$ Windows
-6) Setup properly your data source. Include this line in your ODBC
-   configuration dialog in field "Connect Settings:" :
-	SET CLIENT_ENCODING = 'WIN1250';
-7) Now try it again, but in Windows with ODBC.
-
-Description:
-------------
-- Depends on proper system locales, tested with RH6.0 and Slackware 3.6,
-  with cs_CZ.iso8859-2 loacle
-- Never try to set-up server multibyte database encoding to WIN1250,
-  always use LATIN2 instead. There is not WIN1250 locale in Unix
-- WIN1250 encoding is useable only for M$W ODBC clients. The characters are
-  on thy fly re-coded, to be displayed and stored back properly
- 
-Important:
-----------
-- it reorders your sort order depending on your LC_... setting, so don't be
-  confused with regression tests, they don't use locale
-- "ch" is corectly sorted only in some newer locales (Ex. RH6.0)
-- you have to insert money as '162,50' (with comma in aphostrophes!)
-- not tested properly
diff --git a/doc-xc/README.mb.jp b/doc-xc/README.mb.jp
deleted file mode 100644
index 7cafb2426e..0000000000
--- a/doc-xc/README.mb.jp
+++ /dev/null
@@ -1,814 +0,0 @@
-PostgreSQL 7.3 multi-byte (MB) support README	       2002/10/21 $B:n@.(B
-
-							$B@P0fC#IW(B
-						[email protected]
-
-$B"#$O$8$a$K(B
-
-  PostgreSQL $B$K$*$1$k%^%k%A%P%$%H%5%]!<%H$O0J2<$N$h$&$JFCD'$r;}$C$F$$$^$9!%(B
-
-    1. $B%^%k%A%P%$%HJ8;z$H$7$F!$F|K\8l!$Cf9q8l$J$I$N3F9q$N(B EUC$B!$(BUnicode$B!$(B
-       mule internal code, ISO-8859-* $B$,%G!<%?%Y!<%9:n@.;~$KA*Br2DG=!%(B
-       $B%G!<%?%Y!<%9$K$O$3$N%(%s%3!<%G%#%s%0$N$^$^3JG<$5$l$^$9!%(B
-    2. $B%F!<%V%kL>$K%^%k%A%P%$%HJ8;z$,;HMQ2DG=(B
-    3. $B%+%i%`L>$K%^%k%A%P%$%HJ8;z$,;HMQ2DG=(B
-    4. $B%G!<%?$=$N$b$N$K$b%^%k%A%P%$%HJ8;z$,;HMQ2DG=(B
-    5. $B%^%k%A%P%$%HJ8;z$N@55,I=8=8!:w$,;HMQ2DG=(B
-    6. $B%^%k%A%P%$%HJ8;z$N(B LIKE $B8!:w$,;HMQ2DG=(B
-    7. character_length(), position(), substring() $B$J$I$NJ8;zNs4X?t$G(B
-       $B$N%^%k%A%P%$%H%5%]!<%H(B
-    8. $B%U%m%s%H%(%s%IB&$N%(%s%3!<%G%#%s%0$,%P%C%/%(%s%IB&$H0[$k>l9g$K!$(B
-       $B<+F0E*$K%(%s%3!<%G%#%s%0JQ49$r9T$J$$$^$9!%(B
-    9. $B%f!<%6Dj5A$N%(%s%3!<%G%#%s%0JQ49$r:[email protected]=!%(B
-
-  $B%^%k%A%P%$%H%5%]!<%H$,07$&$3$H$N$G$-$k%(%s%3!<%G%#%s%0$O0J2<$K$J$j$^(B
-  $B$9!%(B
-
-	SQL_ASCII	ASCII
-	EUC_JP		$BF|K\8l(B EUC
-	EUC_CN		GB $B$r%Y!<%9$K$7$?CfJ8(BEUC$B!%(Bcode set 2 $B$O(B
-			SS2+2$B%P%$%H%3!<%I(B = 3$B%P%$%HI=8=$G$9!%(B
-	EUC_KR		$B4Z9q8l(B EUC$B!%(B
-	JOHAB		$B%O%s%0%k%Y!<%9$N4Z9q8l(BEUC.
-	EUC_TW		$BBfOQ$N(B EUC$B!%(Bcode set 2 $B$O(B
-			SS2+$BLLHV9f(B+2$B%P%$%H%3!<%I(B = 4$B%P%$%HI=8=$G$9!%(B
-	UNICODE		UTF-8$B!%$?$@$7%5%]!<%H$9$k$N$O(B UCS-2 $B$NHO0O!$(B
-			$B$9$J$o$A(B 0xffff $B$^$G$G$9!%(B
-	MULE_INTERNAL	mule $B$NFbIt%3!<%I!%$?$@$7!$(BType N $B$NITDjD9J8;z$O(B
-			$B%5%]!<%H$7$F$$$^$;$s!%(B
-	LATIN1 $B$+$i(B LATIN10$B$^$G(B
-	ISO_8859_1 $B$+$i(B 16$B$^$G(B
-	$B%-%j%kJ8;z(B	KOI8(KOI8-R), WIN(CP1251), ALT(CP866)$B$r%5%]!<%H(B
-			$B$7$F$$$^$9!%$b$A$m$s(B ISO 8859-5 $B$b;HMQ2DG=$G$9!%(B
-			$B$3$N>l9g!$(B"LATIN5" $B$H$7$F;XDj$7$F2<$5$$!%(B
-	WIN1256		$B%"%i%V=t9q8l(BWindows$BMQ%(%s%3!<%G%#%s%0(B.
-	TCVN		$B%Y%H%J%`8l(B."ABC"$B$d(B"VSCII"$B$b;HMQ2DG=(B.
-	WIN874		$B%?%$8l(B.
-
-  $B%U%m%s%H%(%s%IB&$G$O$5$i$K0J2<$N%(%s%3!<%G%#%s%0$,;HMQ$G$-$^$9!%(B
-
-	SJIS		$B%7%U%H(BJIS(MS932$B$H$[$\8_49(B)
-	BIG5		$BBfOQ$d9a9A$G;HMQ$5$l$F$$$kCf9q8l!%(BEUC_TW$B$H8_49(B
-			$B@-$,$"$j$^$9!%(B
-	GBK		Windows-936
-	UHC		Windows-949
-	WIN1250		Windows-1250
-	GB18030		GB18030
-
-$B"#F|K\8l$r;HMQ$9$k$3$H$N$G$-$k%(%s%3!<%G%#%s%0(B
-
-  $BA*Br$NL\0B$H$7$F$O!$1Q8l$HF|K\8l$7$+;H$o$J$$>l9g$O(B EUC_JP($BF1MM$K!$Cf(B
-  $B9q8l$7$+;H$o$J$$>l9g$O(B EUC_CN... $B$J$I$H$J$j$^$9(B)$B!$$=$NB>$N8@8l$b;H$$$?(B
-  $B$$>l9g$O(B UNICODE $B$b$7$/$O(B MULE_INTERNAL $B$H$J$k$G$7$g$&!%(B
-
-  $BCm0U!'(BMULE_INTERNAL $B$rA*$V$H!$$?$/$5$s$NJ8;z=89g$KBP1~$G$-$FJXMx$G$9(B
-  $B$,!$@55,I=8=$GJ#?t$NJ8;z=89g$K$^$?$,$k$h$&$JHO0O;XDj(B($B$?$H$($P!$(B[a-$BHO(B]
-  $B$H$+!$(B[abc$BHO0O(B]$B$N$h$&$J(B)$B$O;H$($^$;$s!%J#?t$NHO0O;XDj$G0[$J$kJ8;z=89g(B
-  $B$r;H$&$N$O9=$$$^$;$s(B($B$?$H$($P(B [abc][$BHO(B-$B0O(B])$B!%$^$?!$(B[^a] $B$N$h$&$JI=8=(B
-  $B$O!$(B"a" $B$NB0$9$kJ8;z=89g(B($B$3$N>l9g!$(BUS-ASCII)$B$K$*$$$F(B "a" $B0J30$G$"$k(B
-  $B$3$H$rI=$7$^$9!%7h$7$F4A;z$dJ?2>L>$J$I(B "a" $B0J30$r$9$Y$FI=$9$o$1$G$O(B
-  $B$J$$$3$H$KCm0U$7$F2<$5$$!%(B
-
-$B"#%$%s%9%H!<%k(B
-
-  PostgreSQL 7.3$B$+$i$O(Bconfigure$B$N%*%W%7%g%s;XDj$NM-L5$K4X$o$i$:!$%^%k(B
-  $B%A%P%$%H%5%]!<%H$,M-8z$K$J$C$F$$$^$9$N$G!$FC$K(Bconifgure$B;~$K%^%k%A%P(B
-  $B%$%HMQ$NFCJL$J%*%W%7%g%s$r;XDj$9$kI,MW$O$"$j$^$;$s!%(B
-
-$B"#(Binitdb/createdb/create database $B$K$*$1$k%(%s%3!<%G%#%s%0$N;XDj$K$D$$$F(B
-
-  initdb $B$G$O0J2<$N%*%W%7%g%s$G%(%s%3!<%G%#%s%0$,;XDj$G$-$^$9!%(B
-
-	-E $B%(%s%3!<%G%#%s%0(B
-	--encoding=$B%(%s%3!<%G%#%s%0(B
-
-  $B$3$3$G;XDj$7$?%(%s%3!<%G%#%s%0$O!$0J8e(B createdb/create database $B$G%((B
-  $B%s%3!<%G%#%s%0$r>JN,$7$?>l9g$K@_Dj$5$l$k%(%s%3!<%G%#%s%0$K$J$j$^$9!%(B
-  -E $B$^$?$O(B --encoding $B%*%W%7%g%s$r>JN,$7$?>l9g$O!$%(%s%3!<%G%#%s%0$H(B
-  $B$7$F(BSQL_ASCII$B$,:NMQ$5$l$F$7$^$&$N$G!$F|K\8l$r%G%U%)%k%H$G;HMQ$9$k>l(B
-  $B9g$O!$(B
-
-	-E EUC_JP
-
-   $B$"$k$$$O(B
-
-	--encoding=EUC_JP
-
-  $B$H$7$FI,$:L@<(E*$K%(%s%3!<%G%#%s%0$r;XDj$7$F$/$@$5$$!%(B
-
-  $B$J$*!$(BPostgreSQL 7.3$B0J9_%m%1!<%k%5%]!<%H$,I,$:M-8z$K$J$C$F$$$^$9$,!$(B
-  $B$3$l$OF|K\8l$J$I$r;HMQ$9$k:]$K$O2?$N%a%C%j%H$b$J$$$P$+$j$G$J$/!$>c32(B
-  $B$N860x$K$J$C$?$j!$(BLIKE$B8!:w$d@55,I=8=8!:w$G%$%s%G%C%/%9$,M-8z$K$J$i$J(B
-  $B$$$J$I$NLdBj$r0z$-5/$3$9$N$G!$L58z$K$7$F$*$/$3$H$r$*$9$9$a$7$^$9!%%m(B
-  $B%1!<%k%5%]!<%H$rL58z$K$9$k$?$a$K$O!$(B
-
-	--no-locale
-
-  $B%*%W%7%g%s$r;XDj$7$^$9!%(B
-
-  createdb $B$G$O0J2<$N%*%W%7%g%s$G%(%s%3!<%G%#%s%0$,;XDj$G$-$^$9!%(B
-
-	-E $B%(%s%3!<%G%#%s%0(B
-	--encoding=$B%(%s%3!<%G%#%s%0(B
-
-  create database $B$G$O0J2<$N%*%W%7%g%s$G%(%s%3!<%G%#%s%0$,;XDj$G$-$^$9!%(B
-
-	CREATE DATABASE dbanme WITH ENCODING = '$B%(%s%3!<%G%#%s%0(B';
-
-  LOCATION $B$rF1;~$K;XDj$9$k>l9g$O0J2<$N$h$&$K$J$j$^$9!%(B
-
-	CREATE DATABASE dbanme WITH LOCATION = 'path' ENCODING = '$B%(%s%3!<%G%#%s%0(B';
-
-  createdb/create database $B$G$O!$%(%s%3!<%G%#%s%0;XDj$r>JN,$7$?>l9g$O!$(Binitdb 
-  $B$G;XDj$7$?%(%s%3!<%G%#%s%0$,:NMQ$5$l$^$9!%$3$l$O!$(Binitdb $B$,:n@.$9$k(B
-  $B%F%s%W%l!<%H%G!<%?%Y!<%9(B(template1)$B$N(B encoding $B%"%H%j%S%e!<%H$r7Q>5(B
-  $B$9$k$+$i$G$9!%(B
-
-  $B%G!<%?%Y!<%9$N%(%s%3!<%G%#%s%0$O!$(Bpsql -l$B!$(Bpsql $B$N(B \l $B$G;2>H$G$-$^$9!%(B
-
-$ psql -l
-            List of databases
-   Database    |  Owner  |   Encoding    
----------------+---------+---------------
- euc_cn        | t-ishii | EUC_CN
- euc_jp        | t-ishii | EUC_JP
- euc_kr        | t-ishii | EUC_KR
- euc_tw        | t-ishii | EUC_TW
- mule_internal | t-ishii | MULE_INTERNAL
- regression    | t-ishii | SQL_ASCII
- template1     | t-ishii | EUC_JP
- test          | t-ishii | EUC_JP
- unicode       | t-ishii | UNICODE
-(9 rows)
-
-$B"#J8;z7?$N%G!<%?7?$K$D$$$F(B
-
-  7.2$B$G$O!$(BCHAR(n)$B$H(BVARCHAR(n)$B$N(B n $B$OJ8;z?t$r0UL#$7$^$9!%(Bn $B$,%P%$%H?t$r(B
-  $B0UL#$9$k(B 7.1 $B0JA0$H$O0[$J$j$^$9$N$G$4Cm0U2<$5$$!%(B
-
-  $BNc$r<($7$^$9!%(B
-
-  7.2$B$G$O!$(BCHAR(1)$B$K(B"$B$"(B"$B$r3JG<$G$-$^$9$,!$(B7.1$B0JA0$G$O3JG<$G$-$^$;$s$3(B
-  $B$l$O!$(B"$B$"(B"$B$r3JG<$9$k$?$a$K>/$J$/$H$b(B2$B%P%$%H0J>e$rMW$9$k$+$i$G$9!%(B
-  $B5U$K!$(B"a" $B$O(B1$B%P%$%H$7$+>CHq$7$J$$$?$a!$(B7.1$B$G$b(B CHAR(1) $B$K3JG<$G$-$^(B
-  $B$9!%(B
-
-  $B$J$*!$(B7.2$B$G$O!$(B7.1$B$^$G$H0[$J$j!$(BCHAR(n)$B$K3JG<$G$-$J$$(B n $BJ8;z$h$jBg$-(B
-  $B$$J8;zNs$O(B n $BJ8;z$G@Z$j<N$F$i$l$k$N$G$O$J$/!$%(%i!<$K$J$k$3$H$K$4Cm(B
-  $B0U2<$5$$!%$3$l$O!$%^%k%A%P%$%HBP1~$NM-L5$K4X$o$i$:!$J8;zNs$N07$$$,(B
-  SQL$BI8=`$K1h$&$h$&$KJQ$C$?$+$i$G$9!%(B
-
-$B"#%U%m%s%H%(%s%I$H%P%C%/%(%s%I$N<+F0%(%s%3!<%G%#%s%0JQ49$K$D$$$F(B
-
-  $B%P%C%/%(%s%I(B($B%G!<%?%Y!<%9(B)$B$H(B psql $B$J$I$N%U%m%s%H%(%s%I$N%(%s%3!<%G%#(B
-  $B%s%0$O0lCW$7$F$$$k$N$,86B'$G$9$,!$$$$/$D$+$N%(%s%3!<%G%#%s%0$K$D$$$F(B
-  $B$O%P%C%/%(%s%I$H%U%m%s%H%(%s%I$N4V$G0[$J$k$b$N$r;HMQ$9$k$3$H$,$G$-$^(B
-  $B$9!%$3$N>l9g!$<+F0E*$K%P%C%/%(%s%I$G%(%s%3!<%G%#%s%0JQ49$,9T$o$l$^$9!%(B
-
-  $B%P%C%/%(%s%I$N%(%s%3!<%G%#%s%0(B	$B5vMF$5$l$k%U%m%s%H%(%s%I$N(B
-					$B%(%s%3!<%G%#%s%0(B
-  ----------------------------------------------------------------
-	EUC_JP				EUC_JP, SJIS, UNICODE
-
-	EUC_TW				EUC_TW, BIG5, UNICODE
-
-	EUC_CN				EUC_CN, UNICODE
-
-	EUC_KR				EUC_KR, UNICODE
-
-	JOHAB				JOHAB, UNICODE
-
-	LATIN1,3,4			LATIN1,3,4, UNICODE
-
-  	LATIN2				LATIN2, WIN1250, UNICODE
-
-	LATIN5				LATIN5, WIN, ALT, UNICODE
-
-	LATIN6,7,8,9,10			LATIN6,7,8,9,10, UNICODE
-
-	ISO_8859_5,6,7,8		ISO_8859_5,6,7,8, UNICODE
-
-	WIN1256				WIN1256, UNICODE
-
-	TCVN				TCVN, UNICODE
-
-	WIN874				WIN874, UNICODE
-
-	MULE_INTERNAL			EUC_JP, SJIS, EUC_KR, EUC_CN, 
-					EUC_TW, BIG5, LATIN1$B$+$i(B5, 
-					WIN, ALT, WIN1250
-
-	UNICODE				EUC_JP, SJIS, EUC_KR, UHC,
-					EUC_CN, GBK, EUC_TW, BIG5,
-					LATIN1$B$+$i(B10, ISO_8859_5$B$+$i(B8,
-					WIN, ALT, WIN1250, WIN1256,
-					TCVN, WIN874, JOHAB
-  ----------------------------------------------------------------
-
-  $B%P%C%/%(%s%I$H%U%m%s%H%(%s%I$N%(%s%3!<%G%#%s%0$,0[$J$k>l9g!$$=$N$3$H(B
-  $B$r%P%C%/%(%s%I$KEA$($kI,MW$,$"$j$^$9!%$=$N$?$a$NJ}K!$,$$$/$D$+$"$j$^(B
-  $B$9!%(B
-
-o psql $B$N(B \encoding $B%3%^%s%I$r;H$&J}K!(B
-
-  psql$B$G$O!$(B\encoding$B%3%^%s%I$r;H$C$FF0E*$K%U%m%s%H%(%s%IB&$NJ8;z%3!<(B
-  $B%I$r@ZBX$($k$3$H$,$G$-$^$9!%Nc(B:
-
-	\encoding SJIS
-
-o libpq $B$N4X?t(B PQsetClientEncoding $B$r;H$&J}K!(B
-
-  7.0 $B$+$i?7$7$$(B libpq $B4X?t(B PQsetClientEncoding $B$,DI2C$5$l$F$$$^$9!%(B
-
-  PQsetClientEncoding(PGconn *conn, const char *encoding)
-
-  $B$3$N4X?t$r;H$($P!$%3%M%/%7%g%sKh$K%(%s%3!<%G%#%s%0$r@ZBX$($k$3$H$,$G(B
-  $B$-$^$9!%8=:_$N%(%s%3!<%G%#%s%0$NLd$$9g$o$;$O(B
-
-  int PQclientEncoding(const PGconn *conn)
-
-  $B$G$9!%(B
-
-o postgresql.conf $B$G@_Dj$9$kJ}K!(B
-
-  $B%U%m%s%H%(%s%I$N%G%U%)%k%H%(%s%3!<%G%#%s%0$r;XDj$9$k$K$O!$(B
-  postgresql.conf $B$N(B client_encoding $B$r;XDj$7$^$9!%;XDjNc(B:
-
-  client_encoding = SJIS
-
-o $B4D6-JQ?t(B PGCLIENTENCODING $B$r;H$&J}K!(B
-
-  (1) postmaster $B5/F0;~$K4D6-JQ?t$r@_Dj$9$kJ}K!(B
-
-  $B4D6-JQ?t(B PGCLIENTENCODING $B$r@_Dj$9$k$3$H$K$h$j!$(B postgresql.conf $B$G(B
-  $B%(%s%3!<%G%#%s%0$r;XDj$9$k$N$HF1$88z2L$,F@$i$l$^$9!%$?$@$7!$$3$l$ONr(B
-  $B;KE*7P0^$+$i;D$5$l$F$$$k5!G=$G!$:#8e$O$3$N5!G=$rMxMQ$7$J$$$3$H$r$*$9(B
-  $B$9$a$7$^$9!%@_DjNc(B:
-
-  export PGCLIENTENCODING=SJIS postmaster -S
-
-  (2) $B%/%i%$%"%s%H!$%U%m%s%H%(%s%IKh$K%(%s%3!<%G%#%s%0$r@_Dj$7$?$$>l9g(B
-
-  $B$=$N%U%m%s%H%(%s%I(B($B$?$H$($P(B psql)$B$r5/F0$9$kA0$K4D6-JQ?t(B 
-  PGCLIENTENCODING $B$r@_Dj$7$^$9!%(B
-
-o set client_encoding $B%3%^%s%I$r;H$&J}K!(B
-
-  SET CLIENT_ENCODING SQL$B%3%^%s%I$r;H$C$FF0E*$K%U%m%s%H%(%s%I$N%(%s%3!<(B
-  $B%G%#%s%0$rJQ99$G$-$^$9!%Nc(B:
-
-	SET CLIENT_ENCODING TO SJIS;
-
-$B"#8=:_@_Dj$5$l$F$$$k%U%m%s%H%(%s%IB&$N%(%s%3!<%G%#%s%0$rD4$Y$k(B
-
- $B8=:_@_Dj$5$l$F$$$k%U%m%s%H%(%s%IB&$N%(%s%3!<%G%#%s%0$O(B
-
-	show client_encoding;
-
- $B$G;2>H$G$-$^$9(B($B>.J8;z$GI=<($5$l$^$9(B)$B!%(B
-
-$B"#%G%U%)%k%H$N%(%s%3!<%G%#%s%0$X$NI|5"(B
-
-  SQL$B%3%^%s%I(B:
-
-	RESET CLIENT_ENCODING;
-
-  $B$O!$%G%U%)%k%H$N%U%m%s%H%(%s%I%(%s%3!<%G%#%s%0@_Dj$KI|5"$5$;$^$9!%(B
-  postmaster$B$rN)$A>e$2$k$H$-$K(B postgresql.conf $B$N(B client_encoding $B$d4D(B
-  $B6-JQ?t(B PGCLIENTENCODING $B$,@_Dj$5$l$F$$$k$H$=$N%(%s%3!<%G%#%s%0$K!$$=(B
-  $B$&$G$J$1$l$P%G!<%?%Y!<%9$N%(%s%3!<%G%#%s%0$HF1$8$K$J$j$^$9!%(B
-  
-$B"#L@<(E*$J%(%s%3!<%G%#%s%0JQ49(B
-
-  7.2$B$G$O!$(Bconvert$B$H$$$&4X?t$r;H$$!$L@<(E*$J%(%s%3!<%G%#%s%0JQ49$,$G$-(B
-  $B$^$9!%(B
-
-  convert(string text, [src_encoding name,] dest_encoding name) 
-
-  $B$3$3$G(Bsrc_encoding$B$O(Btext$B$N%(%s%3!<%G%#%s%0L>$G$9!%>JN,$9$k$H!$%G!<%?(B
-  $B%Y!<%9%(%s%3!<%G%#%s%0L>$HF1$8$G$"$k$H8+$J$5$l$^$9!%(Bdest_encoding$B$O!$(B
-  $BJQ498e$N%(%s%3!<%G%#%s%0L>$G$9!%(B
-
-  $BNc$r<($7$^$9!%(B
-
-  SELECT convert(text, EUC_JP) FROM unicode_tbl;
-
-  $B$O!$(BUnicode$B$N%F!<%V%k(Bunicode_tbl$B$N(Btext$BNs$r(BEUC_JP$B$KJQ49$7$FJV$7$^$9!%(B
-
-  7.3$B$G$O$5$i$K(BSQL$BI8=`$N(BCONVERT$B4X?t$,;H$($^$9!%(BSQL$BI8=`$N(BCONVERT$B$O(B
-  PostgreSQL$B$N(BCONVERT$B$H5!G=$O$[$H$s$IF1$8$G$9$,!$8F$S=P$77A<0$,0[$j$^(B
-  $B$9!%(B
-
-  SELECT convert(text using euc_jp_to_utf8) FROM unicode_tbl;
-
-  "using" $B$N8e$N0z?t$O!V%3%s%P!<%8%g%sL>!W$G$9!%$3$NNc$G$O!$(BEUC_JP $B$+(B
-  $B$i(B UTF-8 $B$KJQ49$9$k%3%s%P!<%8%g%s$r;XDj$7$F$$$^$9!%Dj5A:Q$N%3%s%P!<(B
-  $B%8%g%s$K$D$$$F$O!$%f!<%6!<%:%,%$%I$N(B "String Functions and
-  Operators" $B$NI=(B"Built-in Conversions" $B$r8+$F$/$@$5$$!%(B
-
-$B"#%(%s%3!<%G%#%s%0JQ49ITG=$N>l9g$N=hM}(B
-
-  $B%P%C%/%(%s%IB&$N%(%s%3!<%G%#%s%0$H%U%m%s%H%(%s%IB&$N%(%s%3!<%G%#%s%0(B
-  $B$,$$$D$bAj8_JQ49$G$-$k$H$O8B$j$^$;$s!%6KC<$JOC!$%P%C%/%(%s%IB&$,(B 
-  EUC_JP $B$J$N$K!$%U%m%s%H%(%s%IB&$,(B EUC_KR $B$@$C$?$i$I$&$J$k$G$7$g$&!%(B
-  $B$3$N>l9g(B PostgreSQL $B$OJQ49$G$-$J$$%3!<%I$r(B 16$B?JI=8=$KJQ49$7$^$9!%(B
-  $B$?$H$($P!$(B"(bdae)" $B$N$h$&$K!%$J$*!$$3$N(B 16$B?JI=8=$O(B mule
-  internal code $B$N%3!<%I$G$"$k$3$H$KCm0U$7$F2<$5$$!%$3$l$O!$D>@\%U%m%s(B
-  $B%H%(%s%I(B <--> $B%P%C%/%(%s%I$N%(%s%3!<%G%#%s%0$rJQ49$9$k$N$G$O$J$/!$0l(B
-  $BEYFbItI=8=$G$"$k(B mule internal code $B$r7PM3$7$F$$$k$?$a$G$9!%(B
-
-  $B$J$*!$(BUnicode$B$H$=$l0J30$N%(%s%3!<%G%#%s%0$NJQ49$@$1$ONc30$G!$(BNOTICE
-  $B%a%C%;!<%8$,I=<($5$l!$JQ49ITG=$NJ8;z$OL5;k$5$l$^$9!%(B
-
-$B"#%G%U%)%k%H%3%s%P!<%8%g%s(B
-
-  $B%G%U%)%k%H%3%s%P!<%8%g%s$O!$%P%C%/%(%s%I$H%U%m%s%H%(%s%I$H$N4V$N%(%s(B
-  $B%3!<%G%#%s%0$N<+F0JQ49$K;H$o$l$kFCJL$J%3%s%P!<%8%g%s$G$9!%%G%U%)%k%H(B
-  $B%3%s%P!<%8%g%s$O3F!9$N(B{$B%9%-!<%^!$%=!<%9%(%s%3!<%G%#%s%0!$%G%9%F%#%M!<(B
-  $B%7%g%s%(%s%3!<%G%#%s%0(B}$B$NAH$_9g$o$;$K$*$$$F!$$?$@0l8D$@$1B8:_$7$^$9!%(B
-  $B>e5-$G@bL@$7$?AH$_9~$_:Q$N%3%s%P!<%8%g%s$O!$(Bpg_catalog$B%9%-!<%^$K$*$$(B
-  $B$FDj5A$5$l$F$*$j!$%9%-!<%^%5!<%A%Q%9$N@_Dj$K4X$o$i$:I,$:MxMQ$G$-$k%3(B
-  $B%s%P!<%8%g%s$K$J$C$F$$$^$9!%(B
-
-  $B5U$K8@$&$H!$(B pg_catalog $B0J30$N%9%-!<%^$K%G%U%)%k%H%3%s%P!<%8%g%s$r:n(B
-  $B@.$9$k$3$H$K$h$j!$%G%U%)%k%H%3%s%P!<%8%g%s$r<+M3$KA*Br$9$k$3$H$b$G$-(B
-  $B$k$o$1$G$9!%$?$H$($P(B SJIS $B$H$NJQ49$K$*$$$F!$(BPostgreSQL $B$,MQ0U$7$F$$(B
-  $B$k(B MS932$B8_49(B $B$NJQ49$G$O$J$/!$(BJIS $B5,3J$N%7%U%H%8%9$KAjEv$9$kJQ49$r9T(B
-  $B$&$h$&$J%3%s%P!<%8%g%s$r:n@.$9$k$3$H$b2DG=$G$9!%(B
-
-$B"#%f!<%6Dj5A%3%s%P!<%8%g%s$N:n@.(B
-
-  PostgreSQL 7.3$B0J9_!$%f!<%6Dj5A$N%3%s%P!<%8%g%s$r:n@.$G$-$k$h$&$K$J$C(B
-  $B$F$$$^$9!%%3%s%P!<%8%g%s$NDj5A$O(B CREATE CONVERSION $B$H$$$&(B SQL $B%3%^%s(B
-  $B%I$r;H$C$F9T$$$^$9!%(B
-
-    CREATE [DEFAULT] CONVERSION conversion_name
-        FOR source_encoding
-        TO dest_encoding FROM funcname
-
-  $B>\:Y$O%j%U%!%l%s%9%^%K%e%"%k$r$4Mw2<$5$$!%(B
-
-$B"#(BSJIS$B%f!<%6Dj5AJ8;z$X$NBP1~(B
-
-  7.0 $B$+$i(B SJIS$B%f!<%6Dj5AJ8;z(B (UDC) $B$KBP1~$7$F$$$^$9!%(BUDC $B$r$I$&07$&$+(B
-  $B$H8@$&$3$H$K$D$$$FCf>r$5$s(B([email protected])$B$+$iLdBjDs5/$H>\:Y$J2r@b$r(B
-  $BD:$-$^$7$?$N$G!$;29M$N$?$a$K$3$N%I%-%e%a%s%H$N:G8e$KIU$1$F$*$-$^$9!%(B
-  $B$^$?!$$3$NLdBj$K$D$$$F$O!$(BPostgreSQL$BF|K\8l%a!<%j%s%0%j%9%H$N(B 
-  [pgsql-jp 12288] (1999/12/17$BIU(B)$B$H(B [pgsql-jp 12486] (2000/1/5$BIU(B) $B$+$i(B
-  $B;O$^$k%9%l%C%I$G5DO@$r8+$k$3$H$,$G$-$^$9(B($B%a!<%k$N%"!<%+%$%V$O(B
-  http://www.sra.co.jp/people/t-ishii/PostgreSQL/ $B$G;2>H$G$-$^$9(B)$B!%(B
-
-  $B$3$3$G$O!$$=$l$i$N5DO@$r$U$^$(!$4JC1$K2r@b$7$^$9!%(B
-
-  PostgreSQL$B$G$O!$F|K\8l$r;HMQ$9$k:]$K%P%C%/%(%s%IB&$N%(%s%3!<%G%#%s%0(B
-  $B$r(B EUC_JP $B$^$?$O(B MULE_INTERNAL or Unicode $B$K$9$kI,MW$,$"$j$^$9!%(B
-  MULE_INTERNAL $B$O(B EUC_JP $B$KJ8;z=89g$rI=$9%3!<%I$rIU$1$?$b$N$J$N$G!$K\(B
-  $B<AE*$KF1$8$G$9!%$^$?!$(BUnicode <---> SJIS $BJQ49$O8=:_$N$H$3$m%5%]!<%H(B
-  $B$5$l$F$$$^$;$s$N$GL5;k$7$^$9!%$7$?$,$C$F!$$3$3$G$O(B EUC_JP $B$H(B SJIS $B$N(B
-  $BAj8_JQ49$N$_$r9M$($^$9!%(B
-
-  $BM=HwCN<1(B
-
-  $B0l8}$K(B EUC_JP $B$H$$$C$F$b!$<B:]$K$OCf?H$OJ#?t$NJ8;z=89g$+$i@.$jN)$C$F(B
-  $B$$$^$9!%(B
-
-	G0: JIS ROMAN (ASCII $B$H$[$\F1$8(B)
-	G1: JIS X 0208 (JIS $B4A;z(B)
-	G2: JIS X 0201 (1$B%P%$%H%+%J(B)
-	G3: JIS X 0212 (JIS $BJd=u4A;z(B)
-
-  $B0lJ}(B SJIS $B$O$3$N$&$A4pK\E*$K(B G0, G1, G2 $B$r%5%]!<%H$7$F$*$j!$(BG3 $B$O%5(B
-  $B%]!<%H$7$F$$$^$;$s!%$7$?$,$C$F!$(BSJIS $B$O(B EUC_JP $B$NItJ,=89g$H$_$J$9$3(B
-  $B$H$,$G$-!$<B:](B PostgreSQL 6.5 $B$^$G$O$3$N9M$($G<BAu$5$l$F$$$^$7$?!%(B
-
-  $B$H$3$m$,!$(BWindows PC $B$N(B SJIS $B$N@$3&$G$O!$>e5-(B JIS $B5,3J$GDj5A$5$l$F$$(B
-  $B$J$$J8;z%3!<%I$,0lItMxMQ$5$l$F$*$j!$$3$NItJ,(B (UDC) $B$O=>Mh(B PostgreSQL 
-  $B$G$OA4$/9MN8$5$l$F$$$^$;$s$G$7$?!%<B:](B UDC $B$r4^$`(B SJIS $B$r(B EUC_JP $B$K(B
-  $BJQ49$9$k$H$-$KIT@5$JJQ49$,9T$o$l$F$$$^$7$?!%$=$3$G(B PostgreSQL 7.0 $B$G(B
-  $B$O!$$^$:$3$NLdBj$r2r7h$9$k$3$H$K$7$^$7$?!%(B
-
-  $B$^$?!$(BUDC $B$NMxMQJ}$K$D$$$F$OI8=`5,3J$N$h$&$J$b$N$O$"$j$^$;$s$,!$<B$O(B
-  $B6H3&CDBN$G$N<h$j7h$a$,$"$j!$$$$o$f$k%G%U%!%/%H%9%?%s%@!<%I$J$i$PB8:_(B
-  $B$9$k$3$H$,J,$+$j$^$7$?!%$=$3$G$3$l$K$D$$$F$b$G$-$k$@$1%5%]!<%H$9$k$3(B
-  $B$H$K$7$^$7$?!%(B
-
-  PostgreSQL 7.0 $B$G$N(B UDC $BBP1~$N<BAu(B
-
-  (1) $B%f!<%6Dj5AJ8;zNN0h$O(B JIS $B$N%f!<%6Dj5AJ8;zNN0h$K%^%C%T%s%0$9$k!%(B
-  SJIS $B$H(B EUC_JP $B$G(B1$BBP(B1$B$NBP1~$K$J$j$^$9!%(B
-
-    - SJIS $B%f!<%6Dj5AJ8;zNN0h(B A ($B2>>N(B)
-          95$B!A(B104 $B6h(B  $B"+"*(B $BF|K\8l(B EUC / G1 (JIS X 0208) 85$B!A(B95 $B6h(B
-
-    - SJIS $B%f!<%6Dj5AJ8;zNN0h(B B ($B2>>N(B)
-         105$B!A(B114 $B6h(B  $B"+"*(B $BF|K\8l(B EUC / G3 (JIS X 0212) 85$B!A(B95 $B6h(B
-
-  (2) IBM $B3HD%J8;zNN0h(B (SJIS 115$B!A(B120 $B6h(B)
-
-  $BJQ49%F!<%V%k$K$h$C$F(B G1 (JIS X 0208)$B$H!$(BG3 (JIS X 0212)$B$KJQ49$5$l$^(B
-  $B$9!%$J$*!$$3$NJQ49$K$*$$$F$O!$(BSJIS --> EUC_JP $B$GJQ49$7!$:F$S(B EUC_JP --
-  > SJIS $B$KJQ49$9$k$H85$N(B SJIS $B$KLa$i$J$$$3$H$,$"$j$^$9!%$^$?!$(BEUC_JP --
-  > SJIS $B$NJQ49$G$O!$$9$Y$F$NJ8;z$rJQ49$G$-$k$o$1$G$O$J$$$N$G!$$=$N>l(B
-  $B9g$OJQ49ITG=J8;z$H$7$F!V".!W$KCV$-49$($^$9!%(B
-
-  *$B6H3&CDBN$N<h$j7h$a$G$O!$JQ49ITG=J8;z$O!V<BAu0MB8!W$H$J$C$F$$$^$9$,!$(B
-  Solaris $B$r$O$8$a!$B?$/$N%7%9%F%`$,!V".!W$rJQ49ITG=J8;z$K:NMQ$7$F$$$^(B
-  $B$9!%(BPostgreSQL$B$b$3$l$K9g$o$;$^$7$?!%(B
-
-  (3) NEC $BA*Dj(B IBM $B3HD%J8;zNN0h(B (SJIS 89$B!A(B92 $B6h(B)
-  
-  PostgreSQL 7.0$B$G$O$9$Y$FJQ49ITG=J8;z!V".!W$KCV$-49$($i$l$^$9!%(B
-
-  PostgreSQL 7.0.1$B0J9_$G$O!$0lC6(B IBM $B3HD%J8;zNN0h$KJQ49$5$l$?8e!$(BG1
-  (JIS X 0208)$B$H!$(BG3 (JIS X 0212)$B$KJQ49$5$l$^$9!%(B
-
-$B<U<-!'(B
-
-  o $BFA2H(B@$B;06(1?M"%5!<%S%9$5$s$+$i!$(BNEC $BA*Dj(B IBM $B4A;zBP1~%Q%C%A$rDs6!$7(B
-    $B$F$$$?$@$-$^$7$?!%(B
-
-  o $B3F<oJ8;z%;%C%H!$%3!<%I7O$K$D$$$F!$F|K\8l(B PostgreSQL $B%a!<%j%s%0%j%9%H(B
-    $B$N%a%s%P$NJ}$+$i%"%I%P%$%9$rD:$-$^$7$?!%$3$3$K46<U$7$^$9!%(B
-    $B$^$?!$(BSJIS $BBP1~$K$D$$$F$O!$;T@n(B@$B$*CcBg$5$s$N%Q%C%A$r;29M$K$5$;$F$$(B
-    $B$?$@$-$^$7$?!%(B
-
-  o SJIS$B%f!<%6Dj5AJ8;z(B (UDC) $B$r$I$&07$&$+$H8@$&$3$H$K$D$$$FCf>r$5$s(B
-    ([email protected])$B$+$iLdBjDs5/$H>\:Y$J2r@b$rD:$-$^$7$?!%(B
-
-$B"#(BUnicode$B$H$=$l0J30$N%(%s%3!<%G%#%s%0$H$NAj8_JQ49$K$D$$$F(B
-
-  PostgreSQL 7.1$B$+$i(BUnicode$B$H$=$l0J30$N%(%s%3!<%G%#%s%0$H$NAj8_JQ49$,(B
-  $B2DG=$K$J$j$^$7$?!%$3$NJQ49$O$4$/0lIt$NJ8;z%3!<%I(B(ISO 8859-1)$B$r$N$>$-!$(B
-  $B%m%8%C%/$K$h$kJQ49$,$G$-$J$$$?$a!$JQ49$N:]$K$O%F!<%V%k$,I,MW$K$J$j$^(B
-  $B$9!%(BPostgreSQL$B$N<BAu$G$O!$(BUnicode$BJQ49%F!<%V%k$O(B Unicode organization 
-  $B$,Ds6!$9$k$b$N$r;HMQ!$$3$l$r(BPerl$B%W%m%0%i%`$G(BC$B8@8l$N%F!<%V%k$KJQ49$7(B
-  $B$F:n@.$7$F$$$^$9(B(Perl$B%W%m%0%i%`$O(BNARITA Tomio$B;a:n@.$N(Blv$B%P!<%8%g%s(B
-  4.3.6 $B$KIUB0$9$k$b$N$r2~B$$N>e!$MxMQ$7$F$$$^$9(B)$B!%(BUnicode
-  organization$B$NDs6!$9$kJQ49%F!<%V%k$O:FG[I[$,5v2D$5$l$F$$$J$$$?$a!$(B
-  PostgreSQL$B$N%=!<%9%3!<%I$K$O4^$^$l$F$$$^$;$s!%0J2<!$;HMQ$7$?JQ49%F!<(B
-  $B%V%k$rNs5s$7$^$9!%(B
-
-  $B%(%s%3!<%G%#%s%0(B	$BJQ49%F!<%V%k(B
-  ============================================================
-  ISO 8859-1		$B$J$7(B
-  ISO 8859-2		8859-2.TXT
-  ISO 8859-3		8859-3.TXT
-  ISO 8859-4		8859-4.TXT
-  ISO 8859-5		8859-5.TXT
-  ISO 8859-6		8859-6.TXT
-  ISO 8859-7		8859-7.TXT
-  ISO 8859-8		8859-8.TXT
-  ISO 8859-9		8859-9.TXT
-  ISO 8859-10		8859-10.TXT
-  ISO 8859-13		8859-13.TXT
-  ISO 8859-14		8859-14.TXT
-  ISO 8859-15		8859-15.TXT
-  ISO 8859-16		8859-16.TXT
-  EUC_JP		JIS0201.TXT, JIS0208.TXT, JIS0212.TXT,
-			CP932.TXT, sjis.map
-  SJIS			CP932.TXT
-  EUC_CN		GB2312.TXT
-  GBK			CP936.TXT
-  EUC_KR		KSX1001.TXT
-  UHC			CP949.TXT
-  JOHAB			JOHAB.TXT
-  EUC_TW		CNS11643.TXT
-  Big5			BIG5.TXT
-  WIN1256		CP1256.TXT
-  TCVN			CP1258.TXT
-  WIN874		CP874.TXT
-  ============================================================
-
-$B<U<-!'(B
-
-  o $BFA2H(B@$B;06(1?M"%5!<%S%9$5$s$+$i!$(BCP932.TXT$B$h$j@8@.$7$?(BSJIS$BMQ$NJQ49%F!<(B
-    $B%V%k$rDs6!$7$F$$$?$@$-$^$7$?!%$3$l$K$h$j!$(BIBM $B3HD%J8;zNN0h(B (SJIS
-    115$B!A(B120 $B6h(B), NEC $BA*Dj(B IBM $B3HD%J8;zNN0h(B (SJIS 89$B!A(B92 $B6h(B)$B$KBP1~$9$k(B
-    $B$3$H$,$G$-$k$h$&$K$J$j$^$7$?!%(B
-
-
-$B;29M(B1$B!'(B
-
-  Pavel Behal$B;a$K$h$jDs6!$5$l$?(BWIN1250$B%5%]!<%H$G$9$,!$(BWindows$B4D6-$G$N(B
-  $BMxMQ$N;EJ}$K$D$$$F;29M$K$J$k%I%-%e%a%s%H$,IUB0$7$F$$$k$N$G!$$3$3$KE:(B
-  $BIU$7$F$*$-$^$9!%(B
-
-  -------------------------------------------------------------------
-Version: 0.91 for PgSQL 6.5
-Author: Pavel Behal
-Revised by: Tatsuo Ishii
-Email: [email protected]
-Licence: The Same as PostgreSQL
-
-Sorry for my Eglish and C code, I'm not native :-)
-
-!!!!!!!!!!!!!!!!!!!!!!!!! NO WARRANTY !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
-Instalation:
-------------
-1) Change three affected files in source directories 
-    (I don't have time to create proper patch diffs, I don't know how)
-	[PostgreSQL 6.5.1$B$G$O$3$N%9%F%C%W$OI,MW$"$j$^$;$s!%(B-- $B@P0f(B]
-2) Compile with enabled locale and multibyte set to LATIN2
-3) Setup properly your instalation, do not forget to create locale
-   variables in your profile (environment). Ex. (may not be exactly true):
-	LC_ALL=cs_CZ.ISO8859-2
-	LC_COLLATE=cs_CZ.ISO8859-2
-	LC_CTYPE=cs_CZ.ISO8859-2
-	LC_MONETARY=cs_CZ.ISO8859-2
-	LC_NUMERIC=cs_CZ.ISO8859-2
-	LC_TIME=cs_CZ.ISO8859-2
-4) You have to start the postmaster with locales set!
-5) Try it with Czech language, it have to sort
-5) Install ODBC driver for PgSQL into your M$ Windows
-6) Setup properly your data source. Include this line in your ODBC
-   configuration dialog in field "Connect Settings:" :
-	SET CLIENT_ENCODING = 'WIN1250';
-7) Now try it again, but in Windows with ODBC.
-
-Description:
-------------
-- Depends on proper system locales, tested with RH6.0 and Slackware 3.6,
-  with cs_CZ.iso8859-2 loacle
-- Never try to set-up server multibyte database encoding to WIN1250,
-  always use LATIN2 instead. There is not WIN1250 locale in Unix
-- WIN1250 encoding is useable only for M$W ODBC clients. The characters are
-  on thy fly re-coded, to be displayed and stored back properly
- 
-Important:
-----------
-- it reorders your sort order depending on your LC_... setting, so don't be
-  confused with regression tests, they don't use locale
-- "ch" is corectly sorted only in some newer locales (Ex. RH6.0)
-- you have to insert money as '162,50' (with comma in aphostrophes!)
-- not tested properly
-  -------------------------------------------------------------------
-
-$B;29M(B2$B!'(BSJIS$B%f!<%6Dj5AJ8;z(B (UDC) $B$r$I$&07$&$+$H8@$&$3$H$K$D$$$FCf>r$5$s(B
-    ([email protected])$B$+$i$$$?$@$$$?LdBjDs5/$H2r@b$G$9!%(B
-
--------------------------- $B0zMQ3+;O(B ----------------------------------
----
-1. SJIS $B%3!<%I$NHO0O(B
-
-    1 $B%P%$%HL\(B 0x81 - 0x9F$B!$(B0xE0 - 0xFC
-    2 $B%P%$%HL\(B 0x40 - 0x7E$B!$(B0x80 - 0xFC
-
-    $B$$$o$f$k!V30;zNN0h!W$NHO0O(B:
-
-    - X0208 $B6&DL<+M3NN0h(B
-
-    |--------------------
-    | 85 $B6h(B  0xEB40 $B!A(B
-    |...
-    |--------------------
-    | 89 $B6h(B  0xED40 $B!A(B    ; 89$B!A(B92 $B6h$O(B
-    |...                  ; $B!V(BNEC $BA*Dj(B IBM $B3HD%J8;zNN0h!W(B
-    |-------------------- ; $B$H8F$P$l$k(B
-    | 93 $B6h(B  0xEF40 $B!A(B
-    | 94 $B6h(B  0xEF9F $B!A(B 0xEFFC
-
-    - $B%f!<%6Dj5AJ8;zNN0h(B
-    
-    |--------------------
-    | 95 $B6h(B  0xF040 $B!A(B    ; 95$B!A(B104 $B6h(B
-    |...                  ; $B!V%f!<%6Dj5AJ8;zNN0h(B A$B!W(B($B2>>N(B)
-    |--------------------
-    |105 $B6h(B  0xF540 $B!A(B    ; 105$B!A(B114 $B6h(B
-    |...                  ; $B!V%f!<%6Dj5AJ8;zNN0h(B B$B!W(B($B2>>N(B)
-    |--------------------
-    |115 $B6h(B  0xFA40 $B!A(B    ; 115$B!A(B120 $B6h$O0lHL$K(B
-    |...                  ; $B!V(BIBM $B3HD%J8;zNN0h!W(B
-    |120 $B6h(B  ...          ; $B$H8F$P$l$k(B
-    |--------------------
-
----
-2. i-mode $BC<Kv$,;H$C$F$$$k?^7AJ8;z%3!<%I$NHO0O(B
-
-    0xF89F - 0xF8FC  (112 $B6h(B)
-    0xF940 - 0xF949  (113 $B6h(B)
-    0xF972 - 0xF97E  (113 $B6h(B)
-    0xF980 - 0xF990  (113 $B6h(B)
-    0xF9B0           (114 $B6h(B)
-
----
-3. $B0lHLE*$J(B EUC $BF|K\8l%3!<%I$NDj5A(B
-
-    G0 : [0x21-0x7E]                  ; $B$$$o$f$k(B JIS ROMAN
-    G1 : [0xA1-0xFE] [0xA1-0xFE]      ; JIS X 0208 
-    G2 : 0x8E [0xA1-0xDF]             ; JIS X 0201 $B%+%J(B
-    G3 : 0x8F [0xA1-0xFE] [0x21-0x7E] ; JIS X 0212 $BJd=u4A;z(B
-
----
-[$BLdBjE@(B]
-
-SJIS 95$B!A(B120 $B6h$O(B JIS X0208 $B$K3:Ev$9$kNN0h$,B8:_$7$J$$(B
-$B$?$a!$$3$NNN0h$N(B EUC - SJIS $BJ8;z%3!<%IJQ49$O3F%Y%s%@$K(B
-$B$h$C$F0[$J$k$N$G$O$J$$$+!$$H$$$&$N$,@P0fMM$+$i$N$4;XE&(B
-$B$G$7$?!%(B
-
----
-[$B5DO@(B]
-
-$BD4::$N7k2L!$(BSJIS 95$B!A(B120 $B6h$r(B EUC $B$KJQ49$9$k$?$a$NI8=`E*$J(B
-$B%k!<%k$,$J$$$o$1$G$O$J$$!$$H$$$&$3$H$,$o$+$j$^$7$?!%>\:Y$O(B
-$B8e=R$N;29M;qNA$r$4Mw$$$?$@$/$H$7$F!$$3$3$G$O$=$N%k!<%k$r(B
-$B4JC1$K$4@bL@$$$?$7$^$9!%(B
-
-   - SJIS $B%f!<%6Dj5AJ8;zNN0h(B A ($B2>>N(B)
-          95$B!A(B104 $B6h(B  $B"+"*(B $BF|K\8l(B EUC / G1 85$B!A(B95 $B6h(B
-
-         $B$?$H$($P(B SJIS $B$N(B (95, 1) = 0xF040 $B$O(B
-         EUC $B$N(B 0xF5A1 $B$K$J$j$^$9!%(B
-
-   - SJIS $B%f!<%6Dj5AJ8;zNN0h(B B ($B2>>N(B)
-         105$B!A(B114 $B6h(B  $B"+"*(B $BF|K\8l(B EUC / G3 85$B!A(B95 $B6h(B
-
-         $B$?$H$($P(B SJIS $B$N(B (105, 1) = 0xF540 $B$O(B
-         EUC $B$N(B 0x8FF5A1 $B$K$J$j$^$9!%(B
-
-   - IBM $B3HD%J8;zNN0h(B
-         115$B!A(B120 $B6h(B
-
-         JIS X 0208 ($BF|K\8l(B EUC / G1)$B!$(BJIS X 0212 
-         ($BF|K\8l(B EUC / G3) $B$K3:Ev$9$kJ8;z$,$"$k>l9g(B
-         $B$O$=$NJ8;z$K%^%C%T%s%0!%$=$&$G$J$$>l9g$O(B
-         $BF|K\8l(B EUC / G3 83$B!A(B84 $B6h$r!$6hE@%3!<%I$N>e0L(B
-         $B$+$i=g$K3d$jEv$F$F$$$/(B ($BJQ49%F!<%V%kJ}<0(B)
-
-$B$3$N;EMM$O!$9-$/;H$o$l$F$$$k(B SJIS $B$H(B EUC $B$N%^%C%T%s%0$,%Y%s%@$K(B
-$B$h$C$F0[$J$k$?$a!$Aj8_1?MQ$N:]$KLdBj$K$J$C$F$$$k$3$H$+$i!$(B1996 
-$BG/$K(B OSF $BF|K\%Y%s%@6(5D2q$,8!F$:n@.$7$?Js9p=q$,%Y!<%9$K$J$C$F$$(B
-$B$k$h$&$G$9!%(B
-
-Solaris $B$N%I%-%e%a%s%H$K$O!V(BTOG $BF|K\%Y%s%@6(5D2q?d>)(B EUC$B!&%7%U%H(B 
-JIS $B%3!<%IJQ49;EMM!W$K$b$H$E$/$H=q$$$F$"$j!$(BSolaris 2.6 $B$+$iF3F~(B
-$B$7$F$$$k$N$@$=$&$G!$;d$+$i8+$l$P;v<B>e$NI8=`$H9M$($F$bIT<+A3$G$O(B
-$B$J$$$H46$8$^$9!%(B
-
-$B$J$*!$>/$J$/$H$b(B 1996 $BG/Ev;~$K$*$$$F$O!$(BOracle $B$d(B Sybase $B$O(B 
-SJIS $B$N%f!<%6Dj5A(B/$B%Y%s%@Dj5AJ8;zNN0h$r(B EUC $B$KJQ49$9$k:]!$H=JLIT(B
-$B2DG=J8;z$H$7$F07$C$F$$$k$i$7$$$H$$$&$3$H$bJdB-$7$F$*$-$^$9!%(B
-
----
-[$B;29M;qNA(B]
-
-// URL $B$,D9$$$N$G!$ESCf$G@Z$l$J$$$H$$$$$N$G$9$,(B...
-
--$B!VF|K\8l(B EUC$B!&%7%U%H(B JIS $B%3!<%IJQ49;EMM$H%3!<%I7O<BBVD4::!W(B
-    1966, OSF $BF|K\%Y%s%@6(5D2q(B
-    http://www.opengroup.or.jp/jvc/cde/sjis-euc.html
-
--$B!VJ8;z%3!<%IJQ495,B'!W(B
-    Solaris 7$B!$(BJFP $B%f!<%6!<%:%,%$%I(B
-    http://docs.sun.com/ab2/coll.139.3/JFPUG/@Ab2PageView/11683?Ab2Lang=ja&Ab2Enc=euc-jp
-
--$B!VF|K\8lJ8;z%3!<%I!W(B
-    Solaris 7$B!$(BJFP $B%f!<%6!<%:%,%$%I(B
-    http://docs.sun.com/ab2/coll.139.3/JFPUG/@Ab2PageView/879;td=5?Ab2Lang=ja&Ab2Enc=euc-jp
-
-    // $BFf$N!V(B1$B!A(B20 $B6h!W$N5-=R$O$3$3$+$i$-$F$$$^$9!%(B
-
----
--------------------------- $B0zMQ$3$3$^$G(B ---------------------------------
-
-$B2~DjMzNr!'(B
-
-  2002/10/21
-	* $B%^%k%A%P%$%HBP1~$,%*%W%7%g%s$G$O$J$/!$8GDj$GI,$:AH$_9~$^$l$k(B
-	  $B$h$&$K$J$j$^$7$?!%(B
-
-	* CREATE CONVERSION/DROP CONVERSION$B$NDI2C!%$3$l$K$H$b$J$$!$%((B
-	  $B%s%3!<%G%#%s%0JQ494X?t$,%m!<%@%V%k4X?t$K$J$j!$%P%C%/%(%s%I$N(B
-	  $B%m!<%I%b%8%e!<%k%5%$%:$,(B7.2$B$h$j$b>.$5$/$J$C$F$$$^$9!%$^$?!$(B
-	  SQL$BI8=`$N(BCONVERT$B4X?t$rDI2C$7$^$7$?!%(B
-	* $B$$$/$D$+%(%s%3!<%G%#%s%0$,DI2C$5$l$F$$$^$9!%(B
-	* $B0J>e!$(B7.3$B$KH?1G$5$l$^$9!%(B
-
-  2001/10/01
-	* CONVERT$B$NDI2C!%(Blpad/rpad/trim/btrim/ltrim/rtrim/translate$B$N(B
-	  $B%^%k%A%P%$%HBP1~DI2C!%(Bchar/varchar$B$G%P%$%H?t$G$O$J$/!$J8;z?t(B
-	  $B$G%5%$%:$rDj5A$9$k$h$&$KJQ99!%0J>e!$(B7.2$B$KH?1G$5$l$^$9!%(B
-
-  2001/2/15
-	* $BFA2H(B@$B;06(1?M"%5!<%S%9$5$s$+$i!$(BCP932.TXT$B$h$j@8@.$7$?(BSJIS$BMQ$N(B
-	  $BJQ49%F!<%V%k$rDs6!$7$F$$$?$@$-$^$7$?!%(B7.1$B$KH?1G$5$l$^$9!%(B
-
-  2001/1/6
-	* UNICODE$B$HB>$N%(%s%3!<%G%#%s%0$H$NAj8_JQ495!G=$rDI2C!%(B
-	* 7.1$B$KH?1G$5$l$^$9!%(B
-
-  2000/5/20
-	* NEC $BA*Dj(B IBM $B4A;zBP1~$rDI2C$7$^$7$?!%$3$l$O(B $BFA2H(B@$B;06(1?M"%5!<%S%9(B
-	  $B$5$s$+$i$N(B contribute $B$G$9!%(B
-	* $B$3$l$i$O!$(B7.0.1 $B$KH?1G$5$l$^$9!%(B
-
-  2000/3/22
-	* PQsetClientEncoding, PQclientEncoding $B$r(Blibpq $B4X?t$KDI2C!$(B
-	  $B%3%M%/%7%g%sKh$K%(%s%3!<%G%#%s%0$rJQ992DG=$K!%(B
-	* SJIS $B%f!<%6Dj5AJ8;z(B (UDC) $B$X$NBP1~(B
-  	* ./configure --with-mb=EUC_JP $B$+$i(B
-	  ./configure --enable-multibyte=EUC_JP $B$KJQ99(B
-  	* SQL_ASCII $B$N(B regression test $BDI2C(B
-	* $B$3$l$i$O(B 7.0 $B$KH?1G$5$l$^$9!%(B
-
-  1999/7/11 WIN1250(Windows$BMQ$N%A%'%38l(B)$B%5%]!<%H$rDI2C$7$^$7$?!%(B
-	* WIN1250 $B$,%U%m%s%H%(%s%IB&$N%(%s%3!<%G%#%s%0$H$7$FMxMQ$G$-$k$h(B
-	  $B$&$K$J$j$^$7$?!%$3$N>l9g!$%P%C%/%(%s%IB&$N%(%s%3!<%G%#%s%0$O(B
-	  LATIN2 $B$^$?$O(B MULE_INTERNAL $B$H$7$^$9!%(B
-	  (contributed by Pavel Behal)
-	* backend/utils/mb/conv.c$B$K$*$1$k7?$NIT@09g$r=$@5$7$^$7$?!%(B
-	  (contributed by Tomoaki Nishiyama)
-	* $B$3$l$i$O(B6.5.1$B$KH?1G$5$l$^$9!%(B
-
-  1999/3/23 $B%-%j%kJ8;z%5%]!<%HDI2CB>(B(6.5 $B$KH?1G:Q(B)
-	* $B%(%s%3!<%G%#%s%0$H$7$F(B KOI8(KOI8-R), WIN(CP1251), ALT(CP866) $B$r(B
-	  $B%5%]!<%H$7$F$$$^$9!%$3$l$i$O!$%U%m%s%H%(%s%I!$%P%C%/%(%s%I!$(B
-	  $B$I$A$i$N%(%s%3!<%G%#%s%0$H$7$F$b;HMQ2DG=$G$"$j!$%(%s%3!<%G%#%s%0$N(B
-	  $BAj8_JQ49$,2DG=$G$9!%$^$?!$=>Mh$+$i%5%]!<%H$7$F$$$k(B ISO 8859-5 $B$b(B
-	  $BF1MM$K;HMQ2DG=$G$9!%(B
-	  $B%-%j%kJ8;z%5%]!<%H$O!$(BOleg Broytmann <[email protected]> $B;a$N(B
-	  $B%j%/%(%9%H5Z$S6(NO$K$h$j<B8=$7$^$7$?!%$3$l$O!$=>Mh$+$i$"$k(B
-	  RCODE $B%5%]!<%H$N5!G=$r<h$j9~$`$b$N$G$b$"$j$^$9!%(B
-	* MB $B$H(B locale $B$rF1;~$K;XDj$7$?>l9g$KBgJ8;z!?>.J8;z$rL5;k$7$?(B
-	  $B@55,I=8=8!:w$,@5>o$KF0:n$7$J$$%P%0$r=$@5(B
-
-  1999/1/26 Big5 $B%5%]!<%HDI2C(B(6.4.2-patched/6.5 $B$KH?1G:Q(B)
-	* Big5 $B$,%U%m%s%H%(%s%IB&$N%(%s%3!<%G%#%s%0$H$7$FMxMQ$G$-$k$h(B
-	  $B$&$K$J$j$^$7$?!%$3$N>l9g!$%P%C%/%(%s%IB&$N%(%s%3!<%G%#%s%0$O(B
-	  EUC_TW $B$^$?$O(B MULE_INTERNAL $B$H$7$^$9!%(B
-	* EUC_TW $B$N(B regression test $B%1!<%9$rDI2C(B
-	  (contributed by Jonah Kuo <[email protected]>)
-
-  1998/12/16 $BK\%I%-%e%a%s%H=$@5(B(6.4.2 $B$KH?1G:Q(B)$B!%(B
-	* Makefile.custom $B$G(B MB=EUC_JP $B$J$I$H@_Dj$9$kJ}K!$O(B 6.4 $B0J9_(B
-	  $B%5%]!<%H$5$l$F$$$J$$$N$G:o=|$7$?!%(B
-	* $BJ8;z%3!<%I(B $B"*(B $B%(%s%3!<%G%#%s%0!$%/%i%$%"%s%H"*%U%m%s%H%(%s%I(B
-	  $B%5!<%P"*%P%C%/%(%s%I(B $B$K$=$l$>$l8l6g$r=$@5!%(B
-
-  1998/12/15 6.4 $B8~$1%P%0=$@5%Q%C%A%j%j!<%9(B(6.4.2 $B$KH?1G:Q(B)$B!%(B
-	* SQL_ASCII $B%5%]!<%H$N%P%0=$@5(B
-
-  1998/11/21 6.4 $B8~$1%P%0=$@5%Q%C%A%j%j!<%9(B(6.4.2 $B$KH?1G:Q(B)$B!%(B
-	* BINARY CURSOR $B$NLdBj$r=$@5(B
-	* pg_dumpall $B$N%P%0=$@5(B
-
-  1998/11/5 6.4 $B%j%j!<%9!%(B
-	* pg_database $B$N(B encoding $B%+%i%`$,(B MB $B$,M-8z$G$J$$$H$-$K$b(B
-	  $BDI2C$5$l$k$h$&$K$J$C$?!%$=$N$?$a!$(BMB $B$,M-8z$G$J$$$H$-$K$O!$(B
-	  ASCII $B$N%(%s%3!<%G%#%s%0$rI=$9(B SQL_ASCII $B$r?7$7$$%(%s%3!<%G%#%s%0(B
-	  $B$H$7$FDI2C$7$?!%$3$l$K$H$b$J$$!$%(%s%3!<%G%#%s%0L>$KBP1~$9$k(B
-	  $B%(%s%3!<%G%#%s%0(BID$B$,(B SQL_ASCII $B$r(B 0 $B$H$9$kHV9f$KJQ99$K$J$C$?!%(B
-
-  1998/7/22 6.4 $B&A8~$1$K%Q%C%A$r%j%j!<%9!%(B
-	* initdb/createdb/create database $B$G%P%C%/%(%s%IB&$N(B
-	  $B%(%s%3!<%G%#%s%0$r@_Dj$-$k5!G=<BAu!%$3$N$?$a!$%7%9%F%`%+%?%m(B
-	  $B%0$N(B pg_database $B$K?7$7$$%+%i%`(B encoding $B$rDI2C(B(MB$B$,M-8z$J;~$@$1(B)
-	* copy $B$,(B PGCLIENTENCODING $B$KBP1~(B
-	* SQL92 $B$N(B "SET NAMES" $B$r%5%]!<%H(B(MB$B$,M-8z$J;~$@$1(B)
-	* LATIN2-5 $B$r%5%]!<%H(B
-	* regression test $B$K(B unicode $B$N%F%9%H%1!<%9$rDI2C(B
-	* MB $B@lMQ$N(B regression $B%F%9%H%G%#%l%/%H%j(B test/mb $B$rDI2C(B
-	* $B%=!<%9%U%!%$%k$NCV$->l=j$rBgI}8+D>$7!%(BMB $B4X78$O(B
-	  include/mb, backend/utils/mb $B$KCV$/$h$&$K$7$?(B
-
-  1998/5/25 $B%P%0=$@5(B(mb_b3.patch $B$H$7$F(B pgsql-jp ML $B$K%j%j!<%9!$(B
-	$BK\2H$G$O(B 6.4 snapshot $B$K<h$j9~$^$l$kM=Dj(B)	
-
-  1998/5/18 $B5!G=DI2C!?%P%0=$@5(B(mb_b2.patch $B$H$7$F(B pgsql-jp ML $B$K%j%j!<%9!$(B
-	$BK\2H$G$O(B 6.4 snapshot $B$K<h$j9~$^$l$kM=Dj(B)
-	* $B4D6-JQ?t(B PGCLIENTENCODING $B$N%5%]!<%H!%%U%m%s%H%(%s%IB&$N(B
-	  $B%(%s%3!<%G%#%s%0$r;XDj$9$k!%8=:_!$(BSJIS, EUC_*, MULE_INTERNAL, 
-	  LATIN1 $B$,;XDj$G$-$k!%$^$?!$(B
-	  set client_encoding to 'sjis';
-	  $B$G$b2DG=(B
-	* 8bit $BJ8;z$,EO$k$HLdBj$,5/$-$k2U=j$K$G$-$k$@$1BP1~(B
-
-  1998/4/21 $B5!G=DI2C!?%P%0=$@5(B(mb_b1.patch $B$H$7$F(B pgsql-jp ML $B$K%j%j!<%9!$(B
-	$BK\2H$G$O(B 6.4 snapshot $B$K<h$j9~$^$l$F$$$k(B)
-	* character_length(), position(), substring() $B$N%^%k%A%P%$%H(B
-	  $BBP1~(B
-	* octet_length() $BDI2C(B $B"*(B initdb $B$N$d$jD>$7I,MW(B
-	* configure $B$N%*%W%7%g%s$K(B MB $B%5%]!<%HDI2C(B
-	  (ex. configure --with-mb=EUC_JP)
-	* EUC_KR $B$N(B regression test $BDI2C(B
-	  ("Soonmyung. Hong" <[email protected]> $B$5$sDs6!(B)
-	* EUC_JP $B$N(B regression test $B$K(B character_length(), position(),
-	  substring(), octet_length() $BDI2C(B
-	* regress.sh $B$N(B SystemV $B$K$*$1$kHs8_49@-=$@5(B
-	* toupper(), tolower() $B$K(B 8bit $BJ8;z$,EO$k$HMn$A$k$3$H$,(B
-	  $B$"$k$N$r=$@5(B
-
-  1998/3/25 PostgreSQL 6.3.1 $B%j%j!<%9!$(BMB PL2 $B$,<h$j9~$^$l$k(B
-
-  1998/3/10 PL2 $B$r%j%j!<%9(B
-	* EUC_JP, EUC_CN, MULE_INTERNAL $B$N(B regression test $B$rDI2C(B
-	  (EUC_CN $B$N%G!<%?$O(B [email protected] $B$5$sDs6!(B)
-	* regexp $B$K$*$$$F!$(Bisalpha $B$J$I$K(B unsigend char $B0J30$NCM$,(B
-          $BEO$i$J$$$h$&$K%,!<%I$r$+$1$k(B
-	* $B1Q8l$N%I%-%e%a%s%H$rDI2C(B
-	* MB $B$rDj5A$7$J$$>l9g$KH/@8$9$k%P%0$r=$@5(B
-
-  1998/3/1 PL1 $B$r%j%j!<%9(B
-
-$B0J>e!%(B
diff --git a/doc-xc/TODO b/doc-xc/TODO
deleted file mode 100644
index 4b7b3da476..0000000000
--- a/doc-xc/TODO
+++ /dev/null
@@ -1,3 +0,0 @@
-The TODO list is now maintained at:
-
-	http://wiki.postgresql.org/wiki/Todo
diff --git a/doc-xc/bug.template b/doc-xc/bug.template
deleted file mode 100644
index 392394fed8..0000000000
--- a/doc-xc/bug.template
+++ /dev/null
@@ -1,53 +0,0 @@
-If PostgreSQL failed to compile on your computer or you found a bug,
-please fill out this form and e-mail it to [email protected].
-
-If your bug report has security implications and you'd prefer that it not
-become immediately visible in public archives, don't send it to postgres-xl-bugs.
-Security issues can be reported privately to [email protected].
-
-If you not only found the problem but solved it and generated a patch
-then e-mail it to [email protected] instead.  Please use the
-command "diff -c" to generate the patch.
-
-You may also enter a bug report at http://sourceforge.net/projects/postgres-xl/
-instead of e-mailing this form.
-
-============================================================================
-                        POSTGRES-XL BUG REPORT TEMPLATE
-============================================================================
-
-
-Your name		:
-Your email address	:
-
-
-System Configuration:
----------------------
-  Architecture (example: Intel Pentium)		:
-
-  Operating System (example: Linux 2.4.18)	:
-
-  Postgres-XL version (example: Postgres-XL 9.2):  Postgres-XL 9.2
-
-  Compiler used (example: gcc 3.3.5)		:
-
-
-Please enter a FULL description of your problem:
-------------------------------------------------
-
-
-
-
-
-Please describe a way to repeat the problem.   Please try to provide a
-concise reproducible example, if at all possible:
-----------------------------------------------------------------------
-
-
-
-
-
-If you know how this problem might be fixed, list the solution below:
----------------------------------------------------------------------
-
-
diff --git a/doc-xc/src/Makefile b/doc-xc/src/Makefile
deleted file mode 100644
index b0d4f1f506..0000000000
--- a/doc-xc/src/Makefile
+++ /dev/null
@@ -1,8 +0,0 @@
-# doc/src/Makefile
-
-subdir = doc/src
-top_builddir = ../..
-include $(top_builddir)/src/Makefile.global
-
-all distprep html man install installdirs uninstall clean distclean maintainer-clean maintainer-check:
-	$(MAKE) -C sgml $@
diff --git a/doc-xc/src/sgml/.gitignore b/doc-xc/src/sgml/.gitignore
deleted file mode 100644
index e1b84b490f..0000000000
--- a/doc-xc/src/sgml/.gitignore
+++ /dev/null
@@ -1,33 +0,0 @@
-# Stuff shipped in tarballs
-/html/
-/html-stamp
-/man1/
-/man3/
-/man7/
-/man-stamp
-# Other popular build targets
-/HISTORY
-/INSTALL
-/regress_README
-/postgres-US.pdf
-/postgres-A4.pdf
-/postgres.html
-/postgres.txt
-# GENERATED_SGML
-/features-supported.sgml
-/features-unsupported.sgml
-/errcodes-table.sgml
-/version.sgml
-/bookindex.sgml
-/HTML.index
-# Assorted byproducts from building the above
-/postgres.xml
-/HISTORY.html
-/INSTALL.html
-/regress_README.html
-/postgres-US.aux
-/postgres-US.log
-/postgres-US.out
-/postgres-A4.aux
-/postgres-A4.log
-/postgres-A4.out
diff --git a/doc-xc/src/sgml/Makefile b/doc-xc/src/sgml/Makefile
deleted file mode 100644
index 9c69b15f21..0000000000
--- a/doc-xc/src/sgml/Makefile
+++ /dev/null
@@ -1,421 +0,0 @@
-#----------------------------------------------------------------------------
-#
-# PostgreSQL documentation makefile
-#
-# doc/src/sgml/Makefile
-#
-#----------------------------------------------------------------------------
-
-# This makefile is for building and installing the documentation.
-# When a release tarball is created, the documentation files are
-# prepared using the distprep target.  In Git-based trees these files
-# don't exist, unless explicitly built, so we skip the installation in
-# that case.
-
-
-# Make "html" the default target, since that is what most people tend
-# to want to use.
-html:
-
-subdir = doc-xc/src/sgml
-top_builddir = ../../..
-include $(top_builddir)/src/Makefile.global
-
-MAKESGMLDIR = $(top_builddir)/src/pgxc/tools/makesgml
-MAKESGML = $(MAKESGMLDIR)/makesgml
-
-
-all: html man
-
-distprep: html distprep-man
-
-
-ifndef COLLATEINDEX
-COLLATEINDEX = $(DOCBOOKSTYLE)/bin/collateindex.pl
-endif
-
-ifndef JADE
-JADE = jade
-endif
-SGMLINCLUDE = -D . -D $(srcdir)
-
-ifndef NSGMLS
-NSGMLS = nsgmls
-endif
-
-ifndef OSX
-OSX = osx
-endif
-
-ifndef XSLTPROC
-XSLTPROC = xsltproc
-endif
-
-VERSION = 9.2
-
-override XSLTPROCFLAGS += --stringparam pg.version '$(VERSION)'
-
-
-GENERATED_SGML = bookindex.sgml version.sgml \
-	features-supported.sgml features-unsupported.sgml errcodes-table.sgml
-
-ALLSGMLIN := $(wildcard $(srcdir)/*.sgmlin $(srcdir)/ref/*.sgmlin)
-
-#ALLSGML := $(wildcard $(srcdir)/*.sgml $(srcdir)/ref/*.sgml) $(GENERATED_SGML)
-ALLSGML := $(ALLSGMLIN:%sgmlin=%sgml) $(GENERATED_SGML)
-
-ALLSGMLTOREMOVE := $(ALLSGMLIN:%sgmlin=%sgml)
-
-
-# Sometimes we don't want this one.
-ALMOSTALLSGML := $(filter-out %bookindex.sgml,$(ALLSGML))
-
-ifdef DOCBOOKSTYLE
-CATALOG = -c $(DOCBOOKSTYLE)/catalog
-endif
-
-# Enable some extra warnings
-# -wfully-tagged needed to throw a warning on missing tags
-# for older tool chains, 2007-08-31
-# Note: try "make SPFLAGS=-wxml" to catch a lot of other dubious constructs,
-# in particular < and & that haven't been made into entities.  It's far too
-# noisy to turn on by default, unfortunately.
-override SPFLAGS += -wall -wno-unused-param -wno-empty -wfully-tagged
-
-##
-## SGML files
-##
-
-sgml-files: $(ALLSGMLIN:%sgmlin=%sgml)
-
-##
-## Man pages
-##
-
-man distprep-man: man-stamp
-
-man-stamp: stylesheet-man.xsl postgres.xml
-	$(XSLTPROC) $(XSLTPROCFLAGS) $(XSLTPROC_MAN_FLAGS) $^
-	touch $@
-
-
-##
-## HTML
-##
-
-.PHONY: draft
-
-JADE.html.call = $(JADE) $(JADEFLAGS) $(SPFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -t sgml -i output-html
-
-# The draft target creates HTML output in draft mode, without index (for faster build).
-draft: postgres.sgml $(ALMOSTALLSGML) stylesheet.dsl
-	$(MKDIR_P) html
-	$(JADE.html.call) -V draft-mode $<
-	cp $(srcdir)/stylesheet.css html/
-
-html: html-stamp
-
-html-stamp: postgres.sgml $(ALLSGML) stylesheet.dsl
-	$(MKDIR_P) html
-	$(JADE.html.call) -i include-index $<
-	cp $(srcdir)/stylesheet.css html/
-	touch $@
-
-# single-page HTML
-postgres.html: postgres.sgml $(ALLSGML) stylesheet.dsl
-	$(JADE.html.call) -V nochunks -V rootchunk -V '(define %root-filename% #f)' -V '(define use-output-dir #f)' -i include-index $<
-
-# single-page text
-postgres.txt: postgres.html
-	$(LYNX) -force_html -dump -nolist $< > $@
-
-HTML.index: postgres.sgml $(ALMOSTALLSGML) stylesheet.dsl
-	@$(MKDIR_P) html
-	$(JADE.html.call) -V html-index $<
-
-bookindex.sgml: HTML.index
-	LC_ALL=C $(PERL) $(COLLATEINDEX) -f -g -i 'bookindex' -o $@ $<
-
-# Technically, this should depend on Makefile.global, but then
-# version.sgml would need to be rebuilt after every configure run,
-# even in distribution tarballs.  So this is cheating a bit, but it
-# will achieve the goal of updating the version number when it
-# changes.
-version.sgml: $(top_srcdir)/configure
-	{ \
-	  echo "<!ENTITY version \"$(VERSION)\">"; \
-	  echo "<!ENTITY majorversion \"$(MAJORVERSION)\">"; \
-	} > $@
-
-features-supported.sgml: $(top_srcdir)/src/backend/catalog/sql_feature_packages.txt $(top_srcdir)/src/backend/catalog/sql_features.txt
-	$(PERL) $(srcdir)/mk_feature_tables.pl YES $^ > $@
-
-features-unsupported.sgml: $(top_srcdir)/src/backend/catalog/sql_feature_packages.txt $(top_srcdir)/src/backend/catalog/sql_features.txt
-	$(PERL) $(srcdir)/mk_feature_tables.pl NO $^ > $@
-
-errcodes-table.sgml: $(top_srcdir)/src/backend/utils/errcodes.txt generate-errcodes-table.pl
-	$(PERL) $(srcdir)/generate-errcodes-table.pl $< > $@
-
-##
-## Print
-##
-
-
-# RTF to allow minor editing for hardcopy
-%.rtf: %.sgml $(ALLSGML)
-	$(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -t rtf -V rtf-backend -i output-print  -i include-index postgres.sgml
-
-# TeX
-# Regular TeX and pdfTeX have slightly differing requirements, so we
-# need to distinguish the path we're taking.
-
-JADE.tex.call = $(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d $(srcdir)/stylesheet.dsl -t tex -V tex-backend -i output-print -i include-index
-
-%-A4.tex-ps: %.sgml $(ALLSGML)
-	$(JADE.tex.call) -V texdvi-output -V '%paper-type%'=A4 -o $@ $<
-
-%-US.tex-ps: %.sgml $(ALLSGML)
-	$(JADE.tex.call) -V texdvi-output -V '%paper-type%'=USletter -o $@ $<
-
-%-A4.tex-pdf: %.sgml $(ALLSGML)
-	$(JADE.tex.call) -V texpdf-output -V '%paper-type%'=A4 -o $@ $<
-
-%-US.tex-pdf: %.sgml $(ALLSGML)
-	$(JADE.tex.call) -V texpdf-output -V '%paper-type%'=USletter -o $@ $<
-
-%.dvi: %.tex-ps
-	@rm -f $*.aux $*.log
-# multiple runs are necessary to create proper intra-document links
-	jadetex $<
-	jadetex $<
-	jadetex $<
-
-# PostScript from TeX
-postgres.ps:
-	$(error Invalid target;  use postgres-A4.ps or postgres-US.ps as targets)
-
-%.ps: %.dvi
-	dvips -o $@ $<
-
-postgres.pdf:
-	$(error Invalid target;  use postgres-A4.pdf or postgres-US.pdf as targets)
-
-%.pdf: %.tex-pdf
-	@rm -f $*.aux $*.log $*.out
-# multiple runs are necessary to create proper intra-document links
-	pdfjadetex $<
-	pdfjadetex $<
-	pdfjadetex $<
-
-# Cancel built-in suffix rules, interfering with PS building
-.SUFFIXES:
-.SUFFIXES: .sgml .sgmlin
-
-INC_LIST = -I PG -I EN
-#INC_LIST = -I PGXC -I EN
-
-.sgmlin.sgml:
-	$(MAKE) -C $(MAKESGMLDIR)
-	$(MAKESGML) -i $< -o $@ $(INC_LIST) $(EXC_LIST)
-
-
-# This generates an XML version of the flow-object tree.  It's useful
-# for debugging DSSSL code, and possibly to interface to some other
-# tools that can make use of this.
-%.fot: %.sgml $(ALLSGML)
-	$(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -t fot -i output-print -i include-index -o $@ $<
-
-
-##
-## Semi-automatic generation of some text files.
-##
-
-JADE.text = $(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -i output-text -t sgml
-LYNX = lynx
-
-INSTALL HISTORY regress_README: % : %.html
-	$(PERL) -p -e 's/<H(1|2)$$/<H\1 align=center/g' $< | $(LYNX) -force_html -dump -nolist -stdin > $@
-
-INSTALL.html: standalone-install.sgml installation.sgml version.sgml
-	$(JADE.text) -V nochunks standalone-install.sgml installation.sgml > $@
-
-HISTORY.html: generate_history.pl $(wildcard $(srcdir)/release*.sgml)
-	$(PERL) $< "$(srcdir)" release.sgml >tempfile_HISTORY.sgml
-	$(JADE.text) -V nochunks tempfile_HISTORY.sgml > $@
-	rm tempfile_HISTORY.sgml
-
-regress_README.html: regress.sgml
-	( echo '<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN" ['; \
-	  echo '<!ENTITY % standalone-ignore "IGNORE">'; \
-	  echo '<!ENTITY % standalone-include "INCLUDE"> ]>'; \
-	  cat $< ) >tempfile_regress_README.sgml
-	$(JADE.text) -V nochunks tempfile_regress_README.sgml > $@
-	rm tempfile_regress_README.sgml
-
-
-##
-## XSLT processing
-##
-
-# For obscure reasons, gmake 3.81 complains about circular dependencies
-# if we try to do "make all" in a VPATH build without the explicit
-# $(srcdir) on the postgres.sgml dependency in this rule.  gmake bug?
-postgres.xml: $(srcdir)/postgres.sgml $(ALMOSTALLSGML)
-	$(OSX) -D. -x lower $< >postgres.xmltmp
-	$(PERL) -p -e 's/\[(amp|copy|egrave|gt|lt|mdash|nbsp|ouml|pi|quot|uuml) *\]/\&\1;/g;' \
-	           -e '$$_ .= qq{<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">\n} if $$. == 1;' \
-	  <postgres.xmltmp > $@
-	rm postgres.xmltmp
-# ' hello Emacs
-
-xslthtml: stylesheet.xsl postgres.xml
-	$(XSLTPROC) $(XSLTPROCFLAGS) $(XSLTPROC_HTML_FLAGS) $^
-
-htmlhelp: stylesheet-hh.xsl postgres.xml
-	$(XSLTPROC) $(XSLTPROCFLAGS) $^
-
-%-A4.fo: stylesheet-fo.xsl %.xml
-	$(XSLTPROC) $(XSLTPROCFLAGS) --stringparam paper.type A4 -o $@ $^
-
-%-US.fo: stylesheet-fo.xsl %.xml
-	$(XSLTPROC) $(XSLTPROCFLAGS) --stringparam paper.type USletter -o $@ $^
-
-
-##
-## Experimental Texinfo targets
-##
-
-DB2X_TEXIXML = db2x_texixml
-DB2X_XSLTPROC = db2x_xsltproc
-MAKEINFO = makeinfo
-
-%.texixml: %.xml
-	$(DB2X_XSLTPROC) -s texi -g output-file=$(basename $@) $< -o $@
-
-%.texi: %.texixml
-	$(DB2X_TEXIXML) --encoding=iso-8859-1//TRANSLIT $< --to-stdout > $@
-
-%.info: %.texi
-	$(MAKEINFO) --enable-encoding --no-split --no-validate $< -o $@
-
-
-##
-## Check
-##
-
-# Quick syntax check without style processing
-check maintainer-check: postgres.sgml $(ALMOSTALLSGML) check-tabs
-	$(NSGMLS) $(SPFLAGS) $(SGMLINCLUDE) -s $<
-
-
-##
-## Install
-##
-
-install: install-html
-
-ifneq ($(PORTNAME), sco)
-install: install-man
-endif
-
-installdirs:
-	$(MKDIR_P) '$(DESTDIR)$(htmldir)'/html $(addprefix '$(DESTDIR)$(mandir)'/man, 1 3 $(sqlmansectnum))
-
-uninstall:
-	rm -f '$(DESTDIR)$(htmldir)/html/'* $(addprefix  '$(DESTDIR)$(mandir)'/man, 1/* 3/* $(sqlmansectnum)/*)
-
-
-## Install html
-
-install-html: html installdirs
-	cp -R $(call vpathsearch,html) '$(DESTDIR)$(htmldir)'
-
-
-## Install man
-
-install-man: man installdirs
-
-sqlmansect ?= 7
-sqlmansectnum = $(shell expr X'$(sqlmansect)' : X'\([0-9]\)')
-
-# Before we install the man pages, we massage the section numbers to
-# follow the local conventions.
-#
-ifeq ($(sqlmansectnum),7)
-install-man:
-	cp -R $(foreach dir,man1 man3 man7,$(call vpathsearch,$(dir))) '$(DESTDIR)$(mandir)'
-
-else # sqlmansectnum != 7
-fix_sqlmansectnum = sed -e '/^\.TH/s/"7"/"$(sqlmansect)"/' \
-			-e 's/\\fR(7)/\\fR($(sqlmansectnum))/g' \
-			-e '1s/^\.so man7/.so man$(sqlmansectnum)/g;1s/^\(\.so.*\)\.7$$/\1.$(sqlmansect)/g'
-
-man: fixed-man-stamp
-
-fixed-man-stamp: man-stamp
-	@$(MKDIR_P) $(addprefix fixedman/,man1 man3 man$(sqlmansectnum))
-	for file in $(call vpathsearch,man1)/*.1; do $(fix_sqlmansectnum) $$file >fixedman/man1/`basename $$file` || exit; done
-	for file in $(call vpathsearch,man3)/*.3; do $(fix_sqlmansectnum) $$file >fixedman/man3/`basename $$file` || exit; done
-	for file in $(call vpathsearch,man7)/*.7; do $(fix_sqlmansectnum) $$file >fixedman/man$(sqlmansectnum)/`basename $$file | sed s/\.7$$/.$(sqlmansect)/` || exit; done
-
-install-man:
-	cp -R $(foreach dir,man1 man3 man$(sqlmansectnum),fixedman/$(dir)) '$(DESTDIR)$(mandir)'
-
-clean: clean-man clean-sgml
-
-.PHONY: clean-man
-clean-man:
-	rm -rf fixedman/ fixed-man-stamp
-
-.PHONY: clean-sgml:
-clean-sgml:
-	rm -rf $(ALLSGML)
-
-endif # sqlmansectnum != 7
-
-# tabs are harmless, but it is best to avoid them in SGML files
-check-tabs:
-	@( ! grep '	' $(wildcard $(srcdir)/*.sgml $(srcdir)/ref/*.sgml) ) || (echo "Tabs appear in SGML files";  exit 1)
-
-##
-## Clean
-##
-
-# This allows removing some files from the distribution tarballs while
-# keeping the dependencies satisfied.
-.SECONDARY: postgres.xml $(GENERATED_SGML) HTML.index
-.SECONDARY: INSTALL.html HISTORY.html regress_README.html
-.SECONDARY: %-A4.tex-ps %-US.tex-ps %-A4.tex-pdf %-US.tex-pdf
-
-clean:
-# text --- these are shipped, but not in this directory
-	rm -f INSTALL HISTORY regress_README
-	rm -f INSTALL.html HISTORY.html regress_README.html
-# single-page output
-	rm -f postgres.html postgres.txt
-# print
-	rm -f *.rtf *.tex-ps *.tex-pdf *.dvi *.aux *.log *.ps *.pdf *.out *.fot
-# index
-	rm -f HTML.index $(GENERATED_SGML)
-# XSLT
-	rm -f postgres.xml postgres.xmltmp htmlhelp.hhp toc.hhc index.hhk *.fo
-# Texinfo
-	rm -f *.texixml *.texi *.info db2texi.refs
-# sgml
-	rm -f $(ALLSGMLTOREMOVE)
-
-distclean: clean
-
-maintainer-clean: distclean
-# HTML
-	rm -fr html/ html-stamp
-# man
-	rm -rf man1/ man3/ man7/ man-stamp
-
-.PHONY: sgmlfiles
-
-INC_LIST = -I XL -I EN
-EXC_LIST = -E PG -E JP
-
-sgmlfiles:
-	./makesgmlfiles $(INC_LIST) $(EXC_LIST)
diff --git a/doc-xc/src/sgml/Makefile.xc.wk b/doc-xc/src/sgml/Makefile.xc.wk
deleted file mode 100644
index 5bf5fce8b9..0000000000
--- a/doc-xc/src/sgml/Makefile.xc.wk
+++ /dev/null
@@ -1,407 +0,0 @@
-#----------------------------------------------------------------------------
-#
-# PostgreSQL documentation makefile
-#
-# $PostgreSQL: pgsql/doc/src/sgml/Makefile,v 1.148 2010/06/12 21:40:31 tgl Exp $
-#
-#----------------------------------------------------------------------------
-
-# This makefile is for building and installing the documentation.
-# When a release tarball is created, the documentation files are
-# prepared using the distprep target.  In Git-based trees these files
-# don't exist, unless explicitly built, so we skip the installation in
-# that case.
-
-
-# Make "html" the default target, since that is what most people tend
-# to want to use.
-html:
-
-subdir = doc/src/sgml
-top_builddir = ../../..
-include $(top_builddir)/src/Makefile.global
-
-
-all: html man
-
-distprep: html distprep-man
-
-
-ifndef COLLATEINDEX
-COLLATEINDEX = $(DOCBOOKSTYLE)/bin/collateindex.pl
-endif
-
-ifndef JADE
-JADE = jade
-endif
-SGMLINCLUDE = -D . -D $(srcdir)
-
-ifndef NSGMLS
-NSGMLS = nsgmls
-endif
-
-ifndef OSX
-OSX = osx
-endif
-
-ifndef XSLTPROC
-XSLTPROC = xsltproc
-endif
-
-override XSLTPROCFLAGS += --stringparam pg.version '$(VERSION)'
-
-
-GENERATED_SGML = bookindex.sgml version.sgml \
-	features-supported.sgml features-unsupported.sgml
-
-ALLSGMLIN := $(wildcard $(srcdir)/*.sgmlin $(srcdir)/ref/*.sgmlin)
-
-#ALLSGML := $(wildcard $(srcdir)/*.sgml $(srcdir)/ref/*.sgml) $(GENERATED_SGML)
-ALLSGML := $(ALLSGMLIN:%sgmlin=%sgml) $(GENERATED_SGML)
-
-ALLSGMLTOREMOVE := $(ALLSGMLIN:%sgmlin=%sgml)
-
-
-# Sometimes we don't want this one.
-ALMOSTALLSGML := $(filter-out %bookindex.sgml,$(ALLSGML))
-
-ifdef DOCBOOKSTYLE
-CATALOG = -c $(DOCBOOKSTYLE)/catalog
-endif
-
-# Enable some extra warnings
-# -wfully-tagged needed to throw a warning on missing tags 
-# for older tool chains, 2007-08-31
-# Note: try "make SPFLAGS=-wxml" to catch a lot of other dubious constructs,
-# in particular < and & that haven't been made into entities.  It's far too
-# noisy to turn on by default, unfortunately.
-override SPFLAGS += -wall -wno-unused-param -wno-empty -wfully-tagged
-
-##
-## Man pages
-##
-
-man distprep-man: man-stamp
-
-man-stamp: stylesheet-man.xsl postgres.xml
-	$(XSLTPROC) $(XSLTPROCFLAGS) $(XSLTPROC_MAN_FLAGS) $^
-	touch $@
-
-
-##
-## HTML
-##
-
-.PHONY: draft
-
-JADE.html.call = $(JADE) $(JADEFLAGS) $(SPFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -t sgml -i output-html
-
-# The draft target creates HTML output in draft mode, without index (for faster build).
-draft: postgres.sgml $(ALMOSTALLSGML) stylesheet.dsl
-	$(MKDIR_P) html
-	$(JADE.html.call) -V draft-mode $<
-	cp $(srcdir)/stylesheet.css html/
-
-html: html-stamp
-
-html-stamp: postgres.sgml $(ALLSGML) stylesheet.dsl
-	$(MKDIR_P) html
-	$(JADE.html.call) -i include-index $<
-	cp $(srcdir)/stylesheet.css html/
-	touch $@
-
-# single-page HTML
-postgres.html: postgres.sgml $(ALLSGML) stylesheet.dsl
-	$(JADE.html.call) -V nochunks -V rootchunk -V '(define %root-filename% #f)' -V '(define use-output-dir #f)' -i include-index $<
-
-# single-page text
-postgres.txt: postgres.html
-	$(LYNX) -force_html -dump -nolist $< > $@
-
-HTML.index: postgres.sgml $(ALMOSTALLSGML) stylesheet.dsl
-	@$(MKDIR_P) html
-	$(JADE.html.call) -V html-index $<
-
-bookindex.sgml: HTML.index
-	LC_ALL=C $(PERL) $(COLLATEINDEX) -f -g -i 'bookindex' -o $@ $<
-
-# Technically, this should depend on Makefile.global, but then
-# version.sgml would need to be rebuilt after every configure run,
-# even in distribution tarballs.  So this is cheating a bit, but it
-# will achieve the goal of updating the version number when it
-# changes.
-version.sgml: $(top_srcdir)/configure
-	{ \
-	  echo "<!entity version \"$(VERSION)\">"; \
-	  echo "<!entity majorversion \"$(MAJORVERSION)\">"; \
-	} > $@
-
-features-supported.sgml: $(top_srcdir)/src/backend/catalog/sql_feature_packages.txt $(top_srcdir)/src/backend/catalog/sql_features.txt
-	$(PERL) $(srcdir)/mk_feature_tables.pl YES $^ > $@
-
-features-unsupported.sgml: $(top_srcdir)/src/backend/catalog/sql_feature_packages.txt $(top_srcdir)/src/backend/catalog/sql_features.txt
-	$(PERL) $(srcdir)/mk_feature_tables.pl NO $^ > $@
-
-
-##
-## Print
-##
-
-
-# RTF to allow minor editing for hardcopy
-%.rtf: %.sgml $(ALLSGML)
-	$(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -t rtf -V rtf-backend -i output-print  -i include-index postgres.sgml
-
-# TeX
-# Regular TeX and pdfTeX have slightly differing requirements, so we
-# need to distinguish the path we're taking.
-
-JADE.tex.call = $(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d $(srcdir)/stylesheet.dsl -t tex -V tex-backend -i output-print -i include-index
-
-%-A4.tex-ps: %.sgml $(ALLSGML)
-	$(JADE.tex.call) -V texdvi-output -V '%paper-type%'=A4 -o $@ $<
-
-%-US.tex-ps: %.sgml $(ALLSGML)
-	$(JADE.tex.call) -V texdvi-output -V '%paper-type%'=USletter -o $@ $<
-
-%-A4.tex-pdf: %.sgml $(ALLSGML)
-	$(JADE.tex.call) -V texpdf-output -V '%paper-type%'=A4 -o $@ $<
-
-%-US.tex-pdf: %.sgml $(ALLSGML)
-	$(JADE.tex.call) -V texpdf-output -V '%paper-type%'=USletter -o $@ $<
-
-%.dvi: %.tex-ps
-	@rm -f $*.aux $*.log
-# multiple runs are necessary to create proper intra-document links
-	jadetex $<
-	jadetex $<
-	jadetex $<
-
-# PostScript from TeX
-postgres.ps:
-	$(error Invalid target;  use postgres-A4.ps or postgres-US.ps as targets)
-
-%.ps: %.dvi
-	dvips -o $@ $<
-
-postgres.pdf:
-	$(error Invalid target;  use postgres-A4.pdf or postgres-US.pdf as targets)
-
-%.pdf: %.tex-pdf
-	@rm -f $*.aux $*.log $*.out
-# multiple runs are necessary to create proper intra-document links
-	pdfjadetex $<
-	pdfjadetex $<
-	pdfjadetex $<
-
-# Cancel built-in suffix rules, interfering with PS building
-.SUFFIXES:
-.SUFFIXES: .sgml .sgmlin
-
-INC_LIST = -I PG -I EN
-#INC_LIST = -I PGXC -I EN
-
-.sgmlin.sgml:
-	makesgml -i $< -o $@ $(INC_LIST) $(EXC_LIST)
-
-
-# This generates an XML version of the flow-object tree.  It's useful
-# for debugging DSSSL code, and possibly to interface to some other
-# tools that can make use of this.
-%.fot: %.sgml $(ALLSGML)
-	$(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -t fot -i output-print -i include-index -o $@ $<
-
-
-##
-## Semi-automatic generation of some text files.
-##
-
-JADE.text = $(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -i output-text -t sgml
-LYNX = lynx
-
-INSTALL HISTORY regress_README: % : %.html
-	$(PERL) -p -e 's/<H(1|2)$$/<H\1 align=center/g' $< | $(LYNX) -force_html -dump -nolist -stdin > $@
-
-INSTALL.html: standalone-install.sgml installation.sgml version.sgml
-	$(JADE.text) -V nochunks standalone-install.sgml installation.sgml > $@
-
-HISTORY.html: generate_history.pl $(wildcard $(srcdir)/release*.sgml)
-	$(PERL) $< "$(srcdir)" release.sgml >tempfile_HISTORY.sgml
-	$(JADE.text) -V nochunks tempfile_HISTORY.sgml > $@
-	rm tempfile_HISTORY.sgml
-
-regress_README.html: regress.sgml
-	( echo '<!doctype chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN" ['; \
-	  echo '<!entity % standalone-ignore "IGNORE">'; \
-	  echo '<!entity % standalone-include "INCLUDE"> ]>'; \
-	  cat $< ) >tempfile_regress_README.sgml
-	$(JADE.text) -V nochunks tempfile_regress_README.sgml > $@
-	rm tempfile_regress_README.sgml
-
-
-##
-## XSLT processing
-##
-
-# For obscure reasons, gmake 3.81 complains about circular dependencies
-# if we try to do "make all" in a VPATH build without the explicit
-# $(srcdir) on the postgres.sgml dependency in this rule.  gmake bug?
-postgres.xml: $(srcdir)/postgres.sgml $(ALMOSTALLSGML)
-	$(OSX) -D. -x lower $< >postgres.xmltmp
-	$(PERL) -p -e 's/\[(amp|copy|egrave|gt|lt|mdash|nbsp|ouml|pi|quot|uuml) *\]/\&\1;/g;' \
-	           -e '$$_ .= qq{<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">\n} if $$. == 1;' \
-	  <postgres.xmltmp > $@
-	rm postgres.xmltmp
-# ' hello Emacs
-
-xslthtml: stylesheet.xsl postgres.xml
-	$(XSLTPROC) $(XSLTPROCFLAGS) $(XSLTPROC_HTML_FLAGS) $^
-
-htmlhelp: stylesheet-hh.xsl postgres.xml
-	$(XSLTPROC) $(XSLTPROCFLAGS) $^
-
-%-A4.fo: stylesheet-fo.xsl %.xml
-	$(XSLTPROC) $(XSLTPROCFLAGS) --stringparam paper.type A4 -o $@ $^
-
-%-US.fo: stylesheet-fo.xsl %.xml
-	$(XSLTPROC) $(XSLTPROCFLAGS) --stringparam paper.type USletter -o $@ $^
-
-
-##
-## Experimental Texinfo targets
-##
-
-DB2X_TEXIXML = db2x_texixml
-DB2X_XSLTPROC = db2x_xsltproc
-MAKEINFO = makeinfo
-
-%.texixml: %.xml
-	$(DB2X_XSLTPROC) -s texi -g output-file=$(basename $@) $< -o $@
-
-%.texi: %.texixml
-	$(DB2X_TEXIXML) --encoding=iso-8859-1//TRANSLIT $< --to-stdout > $@
-
-%.info: %.texi
-	$(MAKEINFO) --enable-encoding --no-split --no-validate $< -o $@
-
-
-##
-## Check
-##
-
-# Quick syntax check without style processing
-check: postgres.sgml $(ALMOSTALLSGML) check-tabs
-	$(NSGMLS) $(SPFLAGS) $(SGMLINCLUDE) -s $<
-
-
-##
-## Install
-##
-
-install: install-html
-
-ifneq ($(PORTNAME), sco)
-install: install-man
-endif
-
-installdirs:
-	$(MKDIR_P) '$(DESTDIR)$(htmldir)'/html $(addprefix '$(DESTDIR)$(mandir)'/man, 1 3 $(sqlmansectnum))
-
-uninstall:
-	rm -f '$(DESTDIR)$(htmldir)/html/'* $(addprefix  '$(DESTDIR)$(mandir)'/man, 1/* 3/* $(sqlmansectnum)/*)
-
-
-## Install html
-
-install-html: html installdirs
-	cp -R $(call vpathsearch,html) '$(DESTDIR)$(htmldir)'
-
-
-## Install man
-
-install-man: man installdirs
-
-sqlmansect ?= 7
-sqlmansectnum = $(shell expr X'$(sqlmansect)' : X'\([0-9]\)')
-
-# Before we install the man pages, we massage the section numbers to
-# follow the local conventions.
-#
-ifeq ($(sqlmansectnum),7)
-install-man:
-	cp -R $(foreach dir,man1 man3 man7,$(call vpathsearch,$(dir))) '$(DESTDIR)$(mandir)'
-
-else # sqlmansectnum != 7
-fix_sqlmansectnum = sed -e '/^\.TH/s/"7"/"$(sqlmansect)"/' \
-			-e 's/\\fR(7)/\\fR($(sqlmansectnum))/g' \
-			-e '1s/^\.so man7/.so man$(sqlmansectnum)/g;1s/^\(\.so.*\)\.7$$/\1.$(sqlmansect)/g'
-
-man: fixed-man-stamp
-
-fixed-man-stamp: man-stamp
-	@$(MKDIR_P) $(addprefix fixedman/,man1 man3 man$(sqlmansectnum))
-	for file in $(call vpathsearch,man1)/*.1; do $(fix_sqlmansectnum) $$file >fixedman/man1/`basename $$file` || exit; done
-	for file in $(call vpathsearch,man3)/*.3; do $(fix_sqlmansectnum) $$file >fixedman/man3/`basename $$file` || exit; done
-	for file in $(call vpathsearch,man7)/*.7; do $(fix_sqlmansectnum) $$file >fixedman/man$(sqlmansectnum)/`basename $$file | sed s/\.7$$/.$(sqlmansect)/` || exit; done
-
-install-man:
-	cp -R $(foreach dir,man1 man3 man$(sqlmansectnum),fixedman/$(dir)) '$(DESTDIR)$(mandir)'
-
-clean: clean-man clean-sgml
-
-.PHONY: clean-man
-clean-man:
-	rm -rf fixedman/ fixed-man-stamp
-
-.PHONY: clean-sgml:
-clean-sgml:
-	rm -rf $(ALLSGML)
-
-endif # sqlmansectnum != 7
-
-# tabs are harmless, but it is best to avoid them in SGML files
-check-tabs:
-	@( ! grep '	' $(wildcard $(srcdir)/*.sgml $(srcdir)/ref/*.sgml) ) || (echo "Tabs appear in SGML files";  exit 1)
-
-##
-## Clean
-##
-
-# This allows removing some files from the distribution tarballs while
-# keeping the dependencies satisfied.
-.SECONDARY: postgres.xml $(GENERATED_SGML) HTML.index
-.SECONDARY: INSTALL.html HISTORY.html regress_README.html
-.SECONDARY: %-A4.tex-ps %-US.tex-ps %-A4.tex-pdf %-US.tex-pdf
-
-clean:
-# text --- these are shipped, but not in this directory
-	rm -f INSTALL HISTORY regress_README
-	rm -f INSTALL.html HISTORY.html regress_README.html
-# single-page output
-	rm -f postgres.html postgres.txt
-# print
-	rm -f *.rtf *.tex-ps *.tex-pdf *.dvi *.aux *.log *.ps *.pdf *.out *.fot
-# index
-	rm -f HTML.index $(GENERATED_SGML)
-# XSLT
-	rm -f postgres.xml postgres.xmltmp htmlhelp.hhp toc.hhc index.hhk *.fo
-# Texinfo
-	rm -f *.texixml *.texi *.info db2texi.refs
-# sgml
-	rm -f $(ALLSGMLTOREMOVE)
-
-distclean: clean
-
-maintainer-clean: distclean
-# HTML
-	rm -fr html/ html-stamp
-# man
-	rm -rf man1/ man3/ man7/ man-stamp
-
-.PHONY: sgmlfiles
-
-INC_LIST = -I XC -I EN
-EXC_LIST = -E PG -E JP
-
-sgmlfiles:
-	./makesgmlfiles $(INC_LIST) $(EXC_LIST)
diff --git a/doc-xc/src/sgml/README.links b/doc-xc/src/sgml/README.links
deleted file mode 100644
index 2668b00d7f..0000000000
--- a/doc-xc/src/sgml/README.links
+++ /dev/null
@@ -1,45 +0,0 @@
-<!-- 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 # from the title of the target
-	link, or xreflabel if defined at the target; 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
diff --git a/doc-xc/src/sgml/acronyms.sgmlin b/doc-xc/src/sgml/acronyms.sgmlin
deleted file mode 100644
index f61d477b35..0000000000
--- a/doc-xc/src/sgml/acronyms.sgmlin
+++ /dev/null
@@ -1,832 +0,0 @@
-<!-- doc/src/sgml/acronyms.sgml -->
-
-<appendix id="acronyms">
- <title>Acronyms</title>
-
- <para>
-<!## PG>
-  This is a list of acronyms commonly used in the <productname>PostgreSQL</>
-  documentation and in discussions about <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-  This is a list of acronyms commonly used in the <productname>Postgres-XC</>
-  documentation and in discussions about <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-  This is a list of acronyms commonly used in the <productname>Postgres-XL</>
-  documentation and in discussions about <productname>Postgres-XL</>.
-<!## end>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><acronym>ANSI</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/American_National_Standards_Institute">
-      American National Standards Institute</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>API</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/API">Application Programming Interface</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>ASCII</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Ascii">American Standard
-      Code for Information Interchange</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>BKI</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="bki">Backend Interface</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>CA</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Certificate_authority">Certificate Authority</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>CIDR</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing">Classless
-      Inter-Domain Routing</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>CPAN</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://www.cpan.org/">Comprehensive Perl Archive Network</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>CRL</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Certificate_revocation_list">Certificate
-      Revocation List</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>CSV</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Comma-separated_values">Comma
-      Separated Values</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>CTE</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="queries-with">Common Table Expression</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>CVE</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://cve.mitre.org/">Common Vulnerabilities and Exposures</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>DBA</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Database_administrator">Database
-      Administrator</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>DBI</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://dbi.perl.org/">Database Interface (Perl)</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>DBMS</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Dbms">Database Management
-      System</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>DDL</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Data_Definition_Language">Data
-      Definition Language</ulink>, SQL commands such as <command>CREATE
-      TABLE</>, <command>ALTER USER</>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>DML</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Data_Manipulation_Language">Data
-      Manipulation Language</ulink>, SQL commands such as <command>INSERT</>,
-      <command>UPDATE</>, <command>DELETE</>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>DST</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Daylight_saving_time">Daylight
-      Saving Time</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>ECPG</acronym></term>
-    <listitem>
-     <para>
-<!## PG>
-      <link linkend="ecpg">Embedded C for PostgreSQL</link>
-<!## end>
-<!## XC>
-      <link linkend="ecpg">Embedded C for Postgres-XC</link>
-<!## end>
-<!## XL>
-      <link linkend="ecpg">Embedded C for Postgres-XL</link>
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>ESQL</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Embedded_SQL">Embedded
-      SQL</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>FAQ</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/FAQ">Frequently Asked
-      Questions</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>FSM</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="storage-fsm">Free Space Map</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>GEQO</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="geqo">Genetic Query Optimizer</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>GIN</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="GIN">Generalized Inverted Index</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>GiST</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="GiST">Generalized Search Tree</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>Git</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Git_(software)">Git</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>GMT</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/GMT">Greenwich Mean Time</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-<!## XC>
-   <varlistentry>
-    <term><acronym>GTM</acronym></term>
-    <listitem>
-     <para>
-      Global Transaction Manager
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-<!## XL>
-   <varlistentry>
-    <term><acronym>GTM</acronym></term>
-    <listitem>
-     <para>
-      Global Transaction Manager
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-   <varlistentry>
-    <term><acronym>GSSAPI</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Generic_Security_Services_Application_Program_Interface">Generic
-      Security Services Application Programming Interface</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>GUC</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="config-setting">Grand Unified Configuration</link>,
-<!## PG>
-      the <productname>PostgreSQL</> subsystem that handles server configuration
-<!## end>
-<!## XC>
-      the <productname>Postgres-XC</> subsystem that handles server configuration
-<!## end>
-<!## XL>
-      the <productname>Postgres-XL</> subsystem that handles server configuration
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-<!## XC>
-   <varlistentry>
-    <term><acronym>GXID</acronym></term>
-    <listitem>
-     <para>
-      Global Transaction Identifier
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-<!## XL>
-   <varlistentry>
-    <term><acronym>GXID</acronym></term>
-    <listitem>
-     <para>
-      Global Transaction Identifier
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-   <varlistentry>
-    <term><acronym>HBA</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="auth-pg-hba-conf">Host-Based Authentication</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>HOT</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://git.postgresql.org/gitweb?p=postgresql.git;a=blob;f=src/backend/access/heap/README.HOT;hb=HEAD">Heap-Only
-      Tuples</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>IEC</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/International_Electrotechnical_Commission">International
-      Electrotechnical Commission</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>IEEE</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://standards.ieee.org/">Institute of Electrical and
-      Electronics Engineers</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>IPC</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Inter-process_communication">Inter-Process
-      Communication</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>ISO</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://www.iso.org/iso/home.htm">International Organization for
-      Standardization</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>ISSN</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Issn">International Standard
-      Serial Number</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>JDBC</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Java_Database_Connectivity">Java
-      Database Connectivity</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>LDAP</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol">Lightweight
-      Directory Access Protocol</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>MSVC</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Visual_C++"><productname>Microsoft
-      Visual C</productname></ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>MVCC</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="mvcc">Multi-Version Concurrency Control</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>NLS</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Internationalization_and_localization">National
-      Language Support</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>ODBC</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Open_Database_Connectivity">Open
-      Database Connectivity</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>OID</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="datatype-oid">Object Identifier</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>OLAP</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Olap">Online Analytical
-      Processing</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>OLTP</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/OLTP">Online Transaction
-      Processing</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>ORDBMS</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/ORDBMS">Object-Relational
-      Database Management System</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>PAM</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Pluggable_Authentication_Modules">Pluggable
-      Authentication Modules</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>PGSQL</acronym></term>
-    <listitem>
-     <para>
-<!## PG>
-      <link linkend="postgres"><productname>PostgreSQL</></link>
-<!## end>
-<!## XC>
-      <link linkend="postgres"><productname>Postgres-XC</></link>
-<!## end>
-<!## XL>
-      <link linkend="postgres"><productname>Postgres-XL</></link>
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>PGXS</acronym></term>
-    <listitem>
-     <para>
-<!## PG>
-      <link linkend="extend-pgxs"><productname>PostgreSQL</> Extension System</link>
-<!## end>
-<!## XC>
-      <link linkend="extend-pgxs"><productname>Postgres-XC</> Extension System</link>
-<!## end>
-<!## XL>
-      <link linkend="extend-pgxs"><productname>Postgres-XL</> Extension System</link>
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>PID</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Process_identifier">Process Identifier</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>PITR</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="continuous-archiving">Point-In-Time
-      Recovery</link> (Continuous Archiving)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>PL</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="server-programming">Procedural Languages (server-side)</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>POSIX</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/POSIX">Portable Operating
-      System Interface</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>RDBMS</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Relational_database_management_system">Relational
-      Database Management System</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>RFC</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Request_for_Comments">Request For
-      Comments</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>SGML</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/SGML">Standard Generalized
-      Markup Language</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>SPI</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="spi">Server Programming Interface</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>SQL</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/SQL">Structured Query Language</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>SRF</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="xfunc-c-return-set">Set-Returning Function</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>SSH</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Secure_Shell">Secure
-      Shell</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>SSL</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Secure_Sockets_Layer">Secure Sockets Layer</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>SSPI</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://msdn.microsoft.com/en-us/library/aa380493%28VS.85%29.aspx">Security
-      Support Provider Interface</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>SYSV</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/System_V">Unix System V</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>TCP/IP</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Transmission_Control_Protocol">Transmission
-      Control Protocol (TCP) / Internet Protocol (IP)</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>TID</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="datatype-oid">Tuple Identifier</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>TOAST</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="storage-toast">The Oversized-Attribute Storage Technique</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>TPC</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://www.tpc.org/">Transaction Processing
-      Performance Council</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>URL</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/URL">Uniform Resource
-      Locator</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>UTC</acronym></term>
-    <listitem>
-     <para>
-      <ulink
-      url="http://en.wikipedia.org/wiki/Coordinated_Universal_Time">Coordinated
-      Universal Time</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>UTF</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://www.unicode.org/">Unicode Transformation
-      Format</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>UTF8</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Utf8">Eight-Bit Unicode
-      Transformation Format</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>UUID</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="datatype-uuid">Universally Unique Identifier</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>WAL</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="wal">Write-Ahead Log</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>XID</acronym></term>
-    <listitem>
-     <para>
-      <link linkend="datatype-oid">Transaction Identifier</link>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><acronym>XML</acronym></term>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/XML">Extensible Markup
-      Language</ulink>
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </para>
-
-</appendix>
diff --git a/doc-xc/src/sgml/add-node.sgmlin b/doc-xc/src/sgml/add-node.sgmlin
deleted file mode 100644
index b8bf1816f4..0000000000
--- a/doc-xc/src/sgml/add-node.sgmlin
+++ /dev/null
@@ -1,273 +0,0 @@
-<!-- doc/src/sgml/add-node.sgml -->
-
-<chapter id="add-node">
- <title>Adding a New Node</title>
-
- <indexterm zone="add-node">
-  <primary>Add a new node</primary>
- </indexterm>
-
-&xlonly;
-
- <para>
-  This chapter outlines steps to add a new Coordinator or a Datanode to a running cluster.
-  Note that an easier way to do this is to make use of the pgxc_ctl utility.
- </para>
-
-  <para>
-
-  </para>
-
- <sect1 id="add-node-coordinator">
-  <title>Adding a New Coordinator</title>
-
-  <indexterm zone="add-node-coordinator">
-   <primary>Add a new coordinator</primary>
-  </indexterm>
-
-  <para>
-    The following steps should be performed to add a new coordinator to a running cluster:
-  </para>
-
-  <para>
-    <orderedlist>
-      <listitem>
-        <para>Initialize the new coordinator. The following example initilizes a coordinator named coord_3.</para>
-        <programlisting>
-          /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data_cord3 --nodename coord_3
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Make necessary changes in postgresql.conf of the new coordinator,
-          in particular specify new coordinator name and pooler port.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Connect to any of the existing coordinators and lock the cluster for backup, do not close this session.
-          The following example assumes a coordinator is running on port 5432. Make sure the function call returns true.
-          The detailed description of the function <function>pgxc_lock_for_backup</> can be found 
-          in <xref linkend="functions-pgxc-add-new-node">
-        </para>
-        <programlisting>
-          ./psql postgres -p 5432
-          select pgxc_lock_for_backup();
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Connect to any of the existing coordinators and take backup of the database.
-          Please note that only schema (i.e. no data) is to be dumped.
-          Also note the use of <option>--include-nodes</>, so that the <command>CREATE TABLE</> contains <command>TO NODE</> clause.
-          Similarly <option>--dump-nodes</> ensures that the dump does contain existing nodes and node groups.
-        </para>
-        <programlisting>
-          ./pg_dumpall -p 5432 -s --include-nodes --dump-nodes --file=/some/valid/path/some_file_name.sql
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Start the new coordinator specifying <option>--restoremode</> while starting.
-          The following example starts the new coordinator on port 5455
-        </para>
-        <programlisting>
-          ./postgres --restoremode -D ../data_cord3 -p 5455
-        </programlisting>
-	    <para>
-	     You can use <literal>pg_ctl</literal> with <option>-Z restoremode</option> option.
-	    </para>
-	    <programlisting>
-	     ./pg_ctl start -Z restoremode -D ../data_coord3 -p 5455
-	    </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Restore the backup (taken in step 4) by connecting to the new coordinator directly.
-        </para>
-        <programlisting>
-          ./psql -d postgres -f /some/valid/path/some_file_name.sql -p 5455
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Quit the new coordinator.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Start the new coordinator specifying <option>--coordinator</> while starting.
-          The following example starts the new coordinator on port 5455
-        </para>
-        <programlisting>
-          ./postgres --coordinator -D ../data_cord3 -p 5455
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Create the new coordinator on rest of the coordinators and reload configuration.
-          The following example creates coord_3, with host localhost and port 5455.
-        </para>
-        <programlisting>
-          CREATE NODE COORD_3 WITH (HOST = 'localhost', type = 'coordinator', PORT = 5455);
-          SELECT pgxc_pool_reload();
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Quit the session of step 3, this will unlock the cluster. The new coordinator is now ready.
-        </para>
-      </listitem>
-
-    </orderedlist>
-  </para>
-
- </sect1>
-
- <sect1 id="add-node-datanode">
-  <title>Adding a New Datanode</title>
-
-  <indexterm zone="add-node-datanode">
-   <primary>Add a new Datanode</primary>
-  </indexterm>
-
-  <para>
-    Following steps should be performed to add a new datanode to a running cluster:
-  </para>
-
-  <para>
-    <orderedlist>
-
-      <listitem>
-        <para>
-          Initialize the new datanode. The following example initializes a new datanode named data_node_3.
-        </para>
-        <programlisting>
-          /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data3 --nodename data_node_3
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Make the necessary changes in postgresql.conf of the new datanode, in particular specify new datanode name
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Connect to any of the existing coordinators and lock the cluster for backup, do not close this session.
-          The following example assumes a coordinator is running on port 5432. Make sure the function call returns true.
-          The detailed description of the function <function>pgxc_lock_for_backup</> can be found 
-          in <xref linkend="functions-pgxc-add-new-node">
-        </para>
-        <programlisting>
-          ./psql postgres -p 5432
-          select pgxc_lock_for_backup();
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Connect to any of the existing datanodes and take backup of the database.
-          Please note that only schema (i.e. no data) is to be dumped.
-          The following example assumes that a datanode is running on port 15432.
-        </para>
-        <programlisting>
-          ./pg_dumpall -p 15432 -s --file=/some/valid/path/some_file_name.sql
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Start the new datanode specifying <option>--restoremode</> while starting the it.
-          The following example starts the new datanode on port 35432.
-        </para>
-        <programlisting>
-          ./postgres --restoremode -D ../data3 -p 35432
-        </programlisting>
-	    <para>
-	     You can use <literal>pg_ctl</literal> with <option>-Z restoremode</option> option.
-	    </para>
-	    <programlisting>
-	     ./pg_ctl start -Z restoremode -D ../data3 -p 5455
-	    </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Restore the backup (taken in step 4) by connecting to the new datanode directly.
-        </para>
-        <programlisting>
-          ./psql -d postgres -f /some/valid/path/some_file_name.sql -p 35432
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Quit the new datanode.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Start the new datanode specifying --datanode while starting.
-        </para>
-        <programlisting>
-          ./postgres --datanode -D ../data3 -p 35432
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Create the new datanode on all the coordinators and reload configuration.
-          The following example creates data_node_3, with host localhost and port 35432.
-        </para>
-        <programlisting>
-          CREATE NODE DATA_NODE_3 WITH (HOST = 'localhost', type = 'datanode', PORT = 35432);
-          SELECT pgxc_pool_reload();
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Create the new datanode on all the other datanodes too and reload configuration.
-          The following example creates data_node_3, with host localhost and port 35432.
-        </para>
-        <programlisting>
-          EXECUTE DIRECT ON (DATA_NODE_1) 'CREATE NODE DATA_NODE_3 WITH (HOST = ''localhost'', type = ''datanode'', PORT = 35432)';
-          EXECUTE DIRECT ON (DATA_NODE_2) 'CREATE NODE DATA_NODE_3 WITH (HOST = ''localhost'', type = ''datanode'', PORT = 35432)';
-          EXECUTE DIRECT ON (DATA_NODE_3) 'ALTER NODE DATA_NODE_3 WITH (HOST = ''localhost'', type = ''datanode'', PORT = 35432)';
-          EXECUTE DIRECT ON (DATA_NODE_1) 'SELECT pgxc_pool_reload()';
-          EXECUTE DIRECT ON (DATA_NODE_2) 'SELECT pgxc_pool_reload()';
-          EXECUTE DIRECT ON (DATA_NODE_3) 'SELECT pgxc_pool_reload()';
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Quit the session of step 3, this will unlock the cluster.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para> The new datanode is now ready.
-          Redistribute existing data by using <command>ALTER TABLE
-<replaceable>my_table</replaceable> ADD NODE (DATA_NODE_3)</>.
-        </para>
-      </listitem>
-
-    </orderedlist>
-  </para>
-
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/adminpack.sgmlin b/doc-xc/src/sgml/adminpack.sgmlin
deleted file mode 100644
index fef740a815..0000000000
--- a/doc-xc/src/sgml/adminpack.sgmlin
+++ /dev/null
@@ -1,47 +0,0 @@
-<!-- doc/src/sgml/adminpack.sgml -->
-
-<sect1 id="adminpack" xreflabel="adminpack">
- <title>adminpack</title>
-
- <indexterm zone="adminpack">
-  <primary>adminpack</primary>
- </indexterm>
-&common;
- <para>
-  <filename>adminpack</> provides a number of support functions which
-  <application>pgAdmin</> and other administration and management tools can
-  use to provide additional functionality, such as remote management
-  of server log files.
- </para>
-
- <sect2>
-  <title>Functions Implemented</title>
-
-&common;
-  <para>
-   The functions implemented by <filename>adminpack</> can only be run by a
-   superuser. Here's a list of these functions:
-
-<programlisting>
-int8 pg_catalog.pg_file_write(fname text, data text, append bool)
-bool pg_catalog.pg_file_rename(oldname text, newname text, archivename text)
-bool pg_catalog.pg_file_rename(oldname text, newname text)
-bool pg_catalog.pg_file_unlink(fname text)
-setof record pg_catalog.pg_logdir_ls()
-
-/* Renaming of existing backend functions for pgAdmin compatibility */
-int8 pg_catalog.pg_file_read(fname text, data text, append bool)
-bigint pg_catalog.pg_file_length(text)
-int4 pg_catalog.pg_logfile_rotate()
-</programlisting>
-  </para>
-
-  <note>
-   <para>
-    Functions of this module run only on the Coordinator you're connecting.
-   </para>
-  </note>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/advanced.sgmlin b/doc-xc/src/sgml/advanced.sgmlin
deleted file mode 100644
index daae1dc8b2..0000000000
--- a/doc-xc/src/sgml/advanced.sgmlin
+++ /dev/null
@@ -1,929 +0,0 @@
-<!-- doc/src/sgml/advanced.sgml -->
-
- <chapter id="tutorial-advanced">
-  <title>Advanced Features</title>
-
-  <sect1 id="tutorial-advanced-intro">
-   <title>Introduction</title>
-
-&common;
-   <para>
-<!## PG>
-    In the previous chapter we have covered the basics of using
-    <acronym>SQL</acronym> to store and access your data in
-    <productname>PostgreSQL</productname>.  We will now discuss some
-    more advanced features of <acronym>SQL</acronym> that simplify
-    management and prevent loss or corruption of your data.  Finally,
-    we will look at some <productname>PostgreSQL</productname>
-    extensions.
-<!## end>
-<!## XC>
-    In the previous chapter we have covered the basics of using
-    <acronym>SQL</acronym> to store and access your data in
-    <productname>Postgres-XC</productname>.  We will now discuss some
-    more advanced features of <acronym>SQL</acronym> that simplify
-    management and prevent loss or corruption of your data.  Finally,
-    we will look at some <productname>Postgres-XC</productname>
-    extensions.
-<!## end>
-<!## XL>
-    In the previous chapter we have covered the basics of using
-    <acronym>SQL</acronym> to store and access your data in
-    <productname>Postgres-XL</productname>.  We will now discuss some
-    more advanced features of <acronym>SQL</acronym> that simplify
-    management and prevent loss or corruption of your data.  Finally,
-    we will look at some <productname>Postgres-XL</productname>
-    extensions.
-<!## end>
-   </para>
-
-   <para>
-    This chapter will on occasion refer to examples found in <xref
-    linkend="tutorial-sql"> to change or improve them, so it will be
-    useful to have read that chapter.  Some examples from
-    this chapter can also be found in
-    <filename>advanced.sql</filename> in the tutorial directory.  This
-    file also contains some sample data to load, which is not
-    repeated here.  (Refer to <xref linkend="tutorial-sql-intro"> for
-    how to use the file.)
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-views">
-   <title>Views</title>
-
-   <indexterm zone="tutorial-views">
-    <primary>view</primary>
-   </indexterm>
-&common;
-   <para>
-    Refer back to the queries in <xref linkend="tutorial-join">.
-    Suppose the combined listing of weather records and city location
-    is of particular interest to your application, but you do not want
-    to type the query each time you need it.  You can create a
-    <firstterm>view</firstterm> over the query, which gives a name to
-    the query that you can refer to like an ordinary table:
-
-<programlisting>
-CREATE VIEW myview AS
-    SELECT city, temp_lo, temp_hi, prcp, date, location
-        FROM weather, cities
-        WHERE city = name;
-
-SELECT * FROM myview;
-</programlisting>
-   </para>
-
-   <para>
-    Making liberal use of views is a key aspect of good SQL database
-    design.  Views allow you to encapsulate the details of the
-    structure of your tables, which might change as your application
-    evolves, behind consistent interfaces.
-   </para>
-
-   <para>
-    Views can be used in almost any place a real table can be used.
-    Building views upon other views is not uncommon.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-fk">
-   <title>Foreign Keys</title>
-
-   <indexterm zone="tutorial-fk">
-    <primary>foreign key</primary>
-   </indexterm>
-
-   <indexterm zone="tutorial-fk">
-    <primary>referential integrity</primary>
-   </indexterm>
-&common;
-   <para>
-    Recall the <classname>weather</classname> and
-    <classname>cities</classname> tables from <xref
-    linkend="tutorial-sql">.  Consider the following problem:  You
-    want to make sure that no one can insert rows in the
-    <classname>weather</classname> table that do not have a matching
-    entry in the <classname>cities</classname> table.  This is called
-    maintaining the <firstterm>referential integrity</firstterm> of
-    your data.  In simplistic database systems this would be
-    implemented (if at all) by first looking at the
-    <classname>cities</classname> table to check if a matching record
-    exists, and then inserting or rejecting the new
-    <classname>weather</classname> records.  This approach has a
-    number of problems and is very inconvenient, so
-<!## PG>
-    <productname>PostgreSQL</productname> can do this for you.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> can do this for you.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> can do this for you.
-<!## end>
-   </para>
-
-   <para>
-    The new declaration of the tables would look like this:
-
-<programlisting>
-CREATE TABLE cities (
-        city     varchar(80) primary key,
-        location point
-);
-
-CREATE TABLE weather (
-        city      varchar(80) references cities(city),
-        temp_lo   int,
-        temp_hi   int,
-        prcp      real,
-        date      date
-);
-</programlisting>
-
-    Now try inserting an invalid record:
-
-<programlisting>
-INSERT INTO weather VALUES ('Berkeley', 45, 53, 0.0, '1994-11-28');
-</programlisting>
-
-<screen>
-ERROR:  insert or update on table "weather" violates foreign key constraint "weather_city_fkey"
-DETAIL:  Key (city)=(Berkeley) is not present in table "cities".
-</screen>
-   </para>
-
-   <para>
-    The behavior of foreign keys can be finely tuned to your
-    application.  We will not go beyond this simple example in this
-    tutorial, but just refer you to <xref linkend="ddl">
-    for more information.  Making correct use of
-    foreign keys will definitely improve the quality of your database
-    applications, so you are strongly encouraged to learn about them.
-   </para>
-
-<!## XC>
-&xconly;
-   <para>
-    Please note that primary key and reference key are both allowed
-    only when these columns are distribution keys when tables are
-    distributed.  As a default, <productname>Postgres-XC</>
-    distributes each row of tables based upon the value of the first
-    column of the table.  You can choose any column as a basis of
-    table distribution, or you can have copies of a table in all the
-    Datanodes.
-   </para>
-   <para>
-    Please refer to <xref linkend="sql-select"> for details.
-   </para>
-
-  </sect1>
-
-
-  <sect1 id="tutorial-transactions">
-   <title>Transactions</title>
-
-   <indexterm zone="tutorial-transactions">
-    <primary>transaction</primary>
-   </indexterm>
-
-&common;
-   <para>
-    <firstterm>Transactions</> are a fundamental concept of all database
-    systems.  The essential point of a transaction is that it bundles
-    multiple steps into a single, all-or-nothing operation.  The intermediate
-    states between the steps are not visible to other concurrent transactions,
-    and if some failure occurs that prevents the transaction from completing,
-    then none of the steps affect the database at all.
-   </para>
-
-   <para>
-    For example, consider a bank database that contains balances for various
-    customer accounts, as well as total deposit balances for branches.
-    Suppose that we want to record a payment of $100.00 from Alice's account
-    to Bob's account.  Simplifying outrageously, the SQL commands for this
-    might look like:
-
-<programlisting>
-UPDATE accounts SET balance = balance - 100.00
-    WHERE name = 'Alice';
-UPDATE branches SET balance = balance - 100.00
-    WHERE name = (SELECT branch_name FROM accounts WHERE name = 'Alice');
-UPDATE accounts SET balance = balance + 100.00
-    WHERE name = 'Bob';
-UPDATE branches SET balance = balance + 100.00
-    WHERE name = (SELECT branch_name FROM accounts WHERE name = 'Bob');
-</programlisting>
-   </para>
-
-   <para>
-    The details of these commands are not important here; the important
-    point is that there are several separate updates involved to accomplish
-    this rather simple operation.  Our bank's officers will want to be
-    assured that either all these updates happen, or none of them happen.
-    It would certainly not do for a system failure to result in Bob
-    receiving $100.00 that was not debited from Alice.  Nor would Alice long
-    remain a happy customer if she was debited without Bob being credited.
-    We need a guarantee that if something goes wrong partway through the
-    operation, none of the steps executed so far will take effect.  Grouping
-    the updates into a <firstterm>transaction</> gives us this guarantee.
-    A transaction is said to be <firstterm>atomic</>: from the point of
-    view of other transactions, it either happens completely or not at all.
-   </para>
-
-   <para>
-    We also want a
-    guarantee that once a transaction is completed and acknowledged by
-    the database system, it has indeed been permanently recorded
-    and won't be lost even if a crash ensues shortly thereafter.
-    For example, if we are recording a cash withdrawal by Bob,
-    we do not want any chance that the debit to his account will
-    disappear in a crash just after he walks out the bank door.
-    A transactional database guarantees that all the updates made by
-    a transaction are logged in permanent storage (i.e., on disk) before
-    the transaction is reported complete.
-   </para>
-
-   <para>
-    Another important property of transactional databases is closely
-    related to the notion of atomic updates: when multiple transactions
-    are running concurrently, each one should not be able to see the
-    incomplete changes made by others.  For example, if one transaction
-    is busy totalling all the branch balances, it would not do for it
-    to include the debit from Alice's branch but not the credit to
-    Bob's branch, nor vice versa.  So transactions must be all-or-nothing
-    not only in terms of their permanent effect on the database, but
-    also in terms of their visibility as they happen.  The updates made
-    so far by an open transaction are invisible to other transactions
-    until the transaction completes, whereupon all the updates become
-    visible simultaneously.
-   </para>
-
-   <para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Please note that primary key and reference key are both allowed
-    only when these columns are distribution keys when tables are
-    distributed.  As a default, <productname>Postgres-XL</>
-    distributes each row of tables based upon the value of the first
-    column of the table.  You can choose any column as a basis of
-    table distribution, or you can have copies of a table in all the
-    Datanodes by specifying that it should be distributed by replication.
-   </para>
-   <para>
-    Please refer to <xref linkend="sql-select"> for details.
-   </para>
-
-  </sect1>
-
-
-  <sect1 id="tutorial-transactions">
-   <title>Transactions</title>
-
-   <indexterm zone="tutorial-transactions">
-    <primary>transaction</primary>
-   </indexterm>
-
-&common;
-   <para>
-    <firstterm>Transactions</> are a fundamental concept of all database
-    systems.  The essential point of a transaction is that it bundles
-    multiple steps into a single, all-or-nothing operation.  The intermediate
-    states between the steps are not visible to other concurrent transactions,
-    and if some failure occurs that prevents the transaction from completing,
-    then none of the steps affect the database at all.
-   </para>
-
-   <para>
-    For example, consider a bank database that contains balances for various
-    customer accounts, as well as total deposit balances for branches.
-    Suppose that we want to record a payment of $100.00 from Alice's account
-    to Bob's account.  Simplifying outrageously, the SQL commands for this
-    might look like:
-
-<programlisting>
-UPDATE accounts SET balance = balance - 100.00
-    WHERE name = 'Alice';
-UPDATE branches SET balance = balance - 100.00
-    WHERE name = (SELECT branch_name FROM accounts WHERE name = 'Alice');
-UPDATE accounts SET balance = balance + 100.00
-    WHERE name = 'Bob';
-UPDATE branches SET balance = balance + 100.00
-    WHERE name = (SELECT branch_name FROM accounts WHERE name = 'Bob');
-</programlisting>
-   </para>
-
-   <para>
-    The details of these commands are not important here; the important
-    point is that there are several separate updates involved to accomplish
-    this rather simple operation.  Our bank's officers will want to be
-    assured that either all these updates happen, or none of them happen.
-    It would certainly not do for a system failure to result in Bob
-    receiving $100.00 that was not debited from Alice.  Nor would Alice long
-    remain a happy customer if she was debited without Bob being credited.
-    We need a guarantee that if something goes wrong partway through the
-    operation, none of the steps executed so far will take effect.  Grouping
-    the updates into a <firstterm>transaction</> gives us this guarantee.
-    A transaction is said to be <firstterm>atomic</>: from the point of
-    view of other transactions, it either happens completely or not at all.
-   </para>
-
-   <para>
-    We also want a
-    guarantee that once a transaction is completed and acknowledged by
-    the database system, it has indeed been permanently recorded
-    and won't be lost even if a crash ensues shortly thereafter.
-    For example, if we are recording a cash withdrawal by Bob,
-    we do not want any chance that the debit to his account will
-    disappear in a crash just after he walks out the bank door.
-    A transactional database guarantees that all the updates made by
-    a transaction are logged in permanent storage (i.e., on disk) before
-    the transaction is reported complete.
-   </para>
-
-   <para>
-    Another important property of transactional databases is closely
-    related to the notion of atomic updates: when multiple transactions
-    are running concurrently, each one should not be able to see the
-    incomplete changes made by others.  For example, if one transaction
-    is busy totalling all the branch balances, it would not do for it
-    to include the debit from Alice's branch but not the credit to
-    Bob's branch, nor vice versa.  So transactions must be all-or-nothing
-    not only in terms of their permanent effect on the database, but
-    also in terms of their visibility as they happen.  The updates made
-    so far by an open transaction are invisible to other transactions
-    until the transaction completes, whereupon all the updates become
-    visible simultaneously.
-   </para>
-<!## end>
-
-   <para>
-<!## PG>
-    In <productname>PostgreSQL</>, a transaction is set up by surrounding
-    the SQL commands of the transaction with
-    <command>BEGIN</> and <command>COMMIT</> commands.  So our banking
-    transaction would actually look like:
-<!## end>
-<!## XC>
-    In <productname>Postgres-XC</>, a transaction is set up by surrounding
-    the SQL commands of the transaction with
-    <command>BEGIN</> and <command>COMMIT</> commands.  So our banking
-    transaction would actually look like:
-<!## end>
-<!## XL>
-    In <productname>Postgres-XL</>, a transaction is set up by surrounding
-    the SQL commands of the transaction with
-    <command>BEGIN</> and <command>COMMIT</> commands.  So our banking
-    transaction would actually look like:
-<!## end>
-
-<programlisting>
-BEGIN;
-UPDATE accounts SET balance = balance - 100.00
-    WHERE name = 'Alice';
--- etc etc
-COMMIT;
-</programlisting>
-   </para>
-
-   <para>
-    If, partway through the transaction, we decide we do not want to
-    commit (perhaps we just noticed that Alice's balance went negative),
-    we can issue the command <command>ROLLBACK</> instead of
-    <command>COMMIT</>, and all our updates so far will be canceled.
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</> actually treats every SQL statement as being
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> actually treats every SQL statement as being
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> actually treats every SQL statement as being
-<!## end>
-    executed within a transaction.  If you do not issue a <command>BEGIN</>
-    command,
-    then each individual statement has an implicit <command>BEGIN</> and
-    (if successful) <command>COMMIT</> wrapped around it.  A group of
-    statements surrounded by <command>BEGIN</> and <command>COMMIT</>
-    is sometimes called a <firstterm>transaction block</>.
-   </para>
-
-   <note>
-    <para>
-     Some client libraries issue <command>BEGIN</> and <command>COMMIT</>
-     commands automatically, so that you might get the effect of transaction
-     blocks without asking.  Check the documentation for the interface
-     you are using.
-    </para>
-   </note>
-
-<!## PG>
-<!-- NOTE:
-     XC does not support savepoint yet.
--->
-   <para>
-    It's possible to control the statements in a transaction in a more
-    granular fashion through the use of <firstterm>savepoints</>.  Savepoints
-    allow you to selectively discard parts of the transaction, while
-    committing the rest.  After defining a savepoint with
-    <command>SAVEPOINT</>, you can if needed roll back to the savepoint
-    with <command>ROLLBACK TO</>.  All the transaction's database changes
-    between defining the savepoint and rolling back to it are discarded, but
-    changes earlier than the savepoint are kept.
-   </para>
-
-   <para>
-    After rolling back to a savepoint, it continues to be defined, so you can
-    roll back to it several times.  Conversely, if you are sure you won't need
-    to roll back to a particular savepoint again, it can be released, so the
-    system can free some resources.  Keep in mind that either releasing or
-    rolling back to a savepoint
-    will automatically release all savepoints that were defined after it.
-   </para>
-<!## end>
-
-   <para>
-    All this is happening within the transaction block, so none of it
-    is visible to other database sessions.  When and if you commit the
-    transaction block, the committed actions become visible as a unit
-    to other sessions, while the rolled-back actions never become visible
-    at all.
-   </para>
-
-<!## PG>
-<!-- NOTE:
-     Again, XC does not supoprt savepoint yet.
--->
-
-   <para>
-    Remembering the bank database, suppose we debit $100.00 from Alice's
-    account, and credit Bob's account, only to find later that we should
-    have credited Wally's account.  We could do it using savepoints like
-    this:
-
-<programlisting>
-BEGIN;
-UPDATE accounts SET balance = balance - 100.00
-    WHERE name = 'Alice';
-SAVEPOINT my_savepoint;
-UPDATE accounts SET balance = balance + 100.00
-    WHERE name = 'Bob';
--- oops ... forget that and use Wally's account
-ROLLBACK TO my_savepoint;
-UPDATE accounts SET balance = balance + 100.00
-    WHERE name = 'Wally';
-COMMIT;
-</programlisting>
-   </para>
-
-   <para>
-    This example is, of course, oversimplified, but there's a lot of control
-    possible in a transaction block through the use of savepoints.
-    Moreover, <command>ROLLBACK TO</> is the only way to regain control of a
-    transaction block that was put in aborted state by the
-    system due to an error, short of rolling it back completely and starting
-    again.
-   </para>
-
-<!## end>
-
-  </sect1>
-
-<!-- Window Functions are not supported yet -->
-
-  <sect1 id="tutorial-window">
-   <title>Window Functions</title>
-
-   <indexterm zone="tutorial-window">
-    <primary>window function</primary>
-   </indexterm>
-
-   <para>
-    A <firstterm>window function</> performs a calculation across a set of
-    table rows that are somehow related to the current row.  This is comparable
-    to the type of calculation that can be done with an aggregate function.
-    But unlike regular aggregate functions, use of a window function does not
-    cause rows to become grouped into a single output row &mdash; the
-    rows retain their separate identities.  Behind the scenes, the window
-    function is able to access more than just the current row of the query
-    result.
-   </para>
-
-   <para>
-    Here is an example that shows how to compare each employee's salary
-    with the average salary in his or her department:
-
-<programlisting>
-SELECT depname, empno, salary, avg(salary) OVER (PARTITION BY depname) FROM empsalary;
-</programlisting>
-
-<screen>
-  depname  | empno | salary |          avg          
------------+-------+--------+-----------------------
- develop   |    11 |   5200 | 5020.0000000000000000
- develop   |     7 |   4200 | 5020.0000000000000000
- develop   |     9 |   4500 | 5020.0000000000000000
- develop   |     8 |   6000 | 5020.0000000000000000
- develop   |    10 |   5200 | 5020.0000000000000000
- personnel |     5 |   3500 | 3700.0000000000000000
- personnel |     2 |   3900 | 3700.0000000000000000
- sales     |     3 |   4800 | 4866.6666666666666667
- sales     |     1 |   5000 | 4866.6666666666666667
- sales     |     4 |   4800 | 4866.6666666666666667
-(10 rows)
-</screen>
-
-    The first three output columns come directly from the table
-    <structname>empsalary</>, and there is one output row for each row in the
-    table.  The fourth column represents an average taken across all the table
-    rows that have the same <structfield>depname</> value as the current row.
-    (This actually is the same function as the regular <function>avg</>
-    aggregate function, but the <literal>OVER</> clause causes it to be
-    treated as a window function and computed across an appropriate set of
-    rows.)
-   </para>
-
-   <para>
-    A window function call always contains an <literal>OVER</> clause
-    directly following the window function's name and argument(s).  This is what
-    syntactically distinguishes it from a regular function or aggregate
-    function.  The <literal>OVER</> clause determines exactly how the
-    rows of the query are split up for processing by the window function.
-    The <literal>PARTITION BY</> list within <literal>OVER</> specifies
-    dividing the rows into groups, or partitions, that share the same
-    values of the <literal>PARTITION BY</> expression(s).  For each row,
-    the window function is computed across the rows that fall into the
-    same partition as the current row.
-   </para>
-
-   <para>
-    You can also control the order in which rows are processed by
-    window functions using <literal>ORDER BY</> within <literal>OVER</>.
-    (The window <literal>ORDER BY</> does not even have to match the
-    order in which the rows are output.)  Here is an example:
-
-<programlisting>
-SELECT depname, empno, salary, rank() OVER (PARTITION BY depname ORDER BY salary DESC) FROM empsalary;
-</programlisting>
-
-<screen>
-  depname  | empno | salary | rank 
------------+-------+--------+------
- develop   |     8 |   6000 |    1
- develop   |    10 |   5200 |    2
- develop   |    11 |   5200 |    2
- develop   |     9 |   4500 |    4
- develop   |     7 |   4200 |    5
- personnel |     2 |   3900 |    1
- personnel |     5 |   3500 |    2
- sales     |     1 |   5000 |    1
- sales     |     4 |   4800 |    2
- sales     |     3 |   4800 |    2
-(10 rows)
-</screen>
-
-    As shown here, the <function>rank</> function produces a numerical rank
-    within the current row's partition for each distinct <literal>ORDER BY</>
-    value, in the order defined by the <literal>ORDER BY</> clause.
-    <function>rank</> needs no explicit parameter, because its behavior
-    is entirely determined by the <literal>OVER</> clause.
-   </para>
-
-   <para>
-    The rows considered by a window function are those of the <quote>virtual
-    table</> produced by the query's <literal>FROM</> clause as filtered by its
-    <literal>WHERE</>, <literal>GROUP BY</>, and <literal>HAVING</> clauses
-    if any.  For example, a row removed because it does not meet the
-    <literal>WHERE</> condition is not seen by any window function.
-    A query can contain multiple window functions that slice up the data
-    in different ways by means of different <literal>OVER</> clauses, but
-    they all act on the same collection of rows defined by this virtual table.
-   </para>
-
-   <para>
-    We already saw that <literal>ORDER BY</> can be omitted if the ordering
-    of rows is not important.  It is also possible to omit <literal>PARTITION
-    BY</>, in which case there is just one partition containing all the rows.
-   </para>
-
-   <para>
-    There is another important concept associated with window functions:
-    for each row, there is a set of rows within its partition called its
-    <firstterm>window frame</>.  Many (but not all) window functions act only
-    on the rows of the window frame, rather than of the whole partition.
-    By default, if <literal>ORDER BY</> is supplied then the frame consists of
-    all rows from the start of the partition up through the current row, plus
-    any following rows that are equal to the current row according to the
-    <literal>ORDER BY</> clause.  When <literal>ORDER BY</> is omitted the
-    default frame consists of all rows in the partition.
-     <footnote>
-      <para>
-       There are options to define the window frame in other ways, but
-       this tutorial does not cover them.  See
-       <xref linkend="syntax-window-functions"> for details.
-      </para>
-     </footnote>
-    Here is an example using <function>sum</>:
-   </para>
-
-<programlisting>
-SELECT salary, sum(salary) OVER () FROM empsalary;
-</programlisting>
-
-<screen>
- salary |  sum  
---------+-------
-   5200 | 47100
-   5000 | 47100
-   3500 | 47100
-   4800 | 47100
-   3900 | 47100
-   4200 | 47100
-   4500 | 47100
-   4800 | 47100
-   6000 | 47100
-   5200 | 47100
-(10 rows)
-</screen>
-
-   <para>
-    Above, since there is no <literal>ORDER BY</> in the <literal>OVER</>
-    clause, the window frame is the same as the partition, which for lack of
-    <literal>PARTITION BY</> is the whole table; in other words each sum is
-    taken over the whole table and so we get the same result for each output
-    row.  But if we add an <literal>ORDER BY</> clause, we get very different
-    results:
-   </para>
-
-<programlisting>
-SELECT salary, sum(salary) OVER (ORDER BY salary) FROM empsalary;
-</programlisting>
-
-<screen>
- salary |  sum  
---------+-------
-   3500 |  3500
-   3900 |  7400
-   4200 | 11600
-   4500 | 16100
-   4800 | 25700
-   4800 | 25700
-   5000 | 30700
-   5200 | 41100
-   5200 | 41100
-   6000 | 47100
-(10 rows)
-</screen>
-
-   <para>
-    Here the sum is taken from the first (lowest) salary up through the
-    current one, including any duplicates of the current one (notice the
-    results for the duplicated salaries).
-   </para>
-
-   <para>
-    Window functions are permitted only in the <literal>SELECT</literal> list
-    and the <literal>ORDER BY</> clause of the query. They are forbidden
-    elsewhere, such as in <literal>GROUP BY</>, <literal>HAVING</>
-    and <literal>WHERE</literal> clauses.  This is because they logically
-    execute after the processing of those clauses.  Also, window functions
-    execute after regular aggregate functions.  This means it is valid to
-    include an aggregate function call in the arguments of a window function,
-    but not vice versa.
-   </para>
-
-   <para>
-    If there is a need to filter or group rows after the window calculations
-    are performed, you can use a sub-select.  For example:
-
-<programlisting>
-SELECT depname, empno, salary, enroll_date
-FROM
-  (SELECT depname, empno, salary, enroll_date,
-          rank() OVER (PARTITION BY depname ORDER BY salary DESC, empno) AS pos
-     FROM empsalary
-  ) AS ss
-WHERE pos &lt; 3;
-</programlisting>
-
-    The above query only shows the rows from the inner query having
-    <literal>rank</> less than 3.
-   </para>
-
-   <para>
-    When a query involves multiple window functions, it is possible to write
-    out each one with a separate <literal>OVER</> clause, but this is
-    duplicative and error-prone if the same windowing behavior is wanted
-    for several functions.  Instead, each windowing behavior can be named
-    in a <literal>WINDOW</> clause and then referenced in <literal>OVER</>.
-    For example:
-
-<programlisting>
-SELECT sum(salary) OVER w, avg(salary) OVER w
-  FROM empsalary
-  WINDOW w AS (PARTITION BY depname ORDER BY salary DESC);
-</programlisting>
-   </para>
-
-   <para>
-    More details about window functions can be found in
-    <xref linkend="syntax-window-functions">,
-    <xref linkend="functions-window">,
-    <xref linkend="queries-window">, and the
-    <xref linkend="sql-select"> reference page.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-inheritance">
-   <title>Inheritance</title>
-
-   <indexterm zone="tutorial-inheritance">
-    <primary>inheritance</primary>
-   </indexterm>
-
-&common;
-   <para>
-    Inheritance is a concept from object-oriented databases.  It opens
-    up interesting new possibilities of database design.
-   </para>
-
-   <para>
-    Let's create two tables:  A table <classname>cities</classname>
-    and a table <classname>capitals</classname>.  Naturally, capitals
-    are also cities, so you want some way to show the capitals
-    implicitly when you list all cities.  If you're really clever you
-    might invent some scheme like this:
-
-<programlisting>
-CREATE TABLE capitals (
-  name       text,
-  population real,
-  altitude   int,    -- (in ft)
-  state      char(2)
-);
-
-CREATE TABLE non_capitals (
-  name       text,
-  population real,
-  altitude   int     -- (in ft)
-);
-
-CREATE VIEW cities AS
-  SELECT name, population, altitude FROM capitals
-    UNION
-  SELECT name, population, altitude FROM non_capitals;
-</programlisting>
-
-    This works OK as far as querying goes, but it gets ugly when you
-    need to update several rows, for one thing.
-   </para>
-
-   <para>
-    A better solution is this:
-
-<programlisting>
-CREATE TABLE cities (
-  name       text,
-  population real,
-  altitude   int     -- (in ft)
-);
-
-CREATE TABLE capitals (
-  state      char(2)
-) SELECT name, altitude
-  FROM cities
-  WHERE altitude &gt; 500;INHERITS (cities);
-</programlisting>
-   </para>
-
-   <para>
-    In this case, a row of <classname>capitals</classname>
-    <firstterm>inherits</firstterm> all columns (<structfield>name</>,
-    <structfield>population</>, and <structfield>altitude</>) from its
-    <firstterm>parent</firstterm>, <classname>cities</classname>.  The
-    type of the column <structfield>name</structfield> is
-<!## PG>
-    <type>text</type>, a native <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-    <type>text</type>, a native <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-    <type>text</type>, a native <productname>Postgres-XL</productname>
-<!## end>
-    type for variable length character strings.  State capitals have
-    an extra column, <structfield>state</>, that shows their state.  In
-<!## PG>
-    <productname>PostgreSQL</productname>, a table can inherit from
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>, a table can inherit from
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>, a table can inherit from
-<!## end>
-    zero or more other tables.
-   </para>
-
-   <para>
-    For example, the  following  query finds the  names  of  all  cities,
-    including  state capitals, that are located at an altitude
-    over 500 feet:
-
-<programlisting>
-SELECT name, altitude
-  FROM cities
-  WHERE altitude &gt; 500;
-</programlisting>
-
-    which returns:
-
-<screen>
-   name    | altitude
------------+----------
- Las Vegas |     2174
- Mariposa  |     1953
- Madison   |      845
-(3 rows)
-</screen>
-   </para>
-
-   <para>
-    On the other hand, the  following  query  finds
-    all  the cities that are not state capitals and
-    are situated at an altitude of 500 feet or higher:
-
-<programlisting>
-SELECT name, altitude
-    FROM ONLY cities
-    WHERE altitude &gt; 500;
-</programlisting>
-
-<screen>
-   name    | altitude
------------+----------
- Las Vegas |     2174
- Mariposa  |     1953
-(2 rows)
-</screen>
-   </para>
-
-   <para>
-    Here the <literal>ONLY</literal> before <literal>cities</literal>
-    indicates that the query should be run over only the
-    <classname>cities</classname> table, and not tables below
-    <classname>cities</classname> in the inheritance hierarchy.  Many
-    of the commands that we have already discussed &mdash;
-    <command>SELECT</command>, <command>UPDATE</command>, and
-    <command>DELETE</command> &mdash; support this <literal>ONLY</literal>
-    notation.
-   </para>
-
-   <note>
-    <para>
-     Although inheritance is frequently useful, it has not been integrated
-     with unique constraints or foreign keys, which limits its usefulness.
-     See <xref linkend="ddl-inherit"> for more detail.
-    </para>
-   </note>
-  </sect1>
-
-
-
-  <sect1 id="tutorial-conclusion">
-   <title>Conclusion</title>
-
-&common;
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> has many features not
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> has many features not
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> has many features not
-<!## end>
-    touched upon in this tutorial introduction, which has been
-    oriented toward newer users of <acronym>SQL</acronym>.  These
-    features are discussed in more detail in the remainder of this
-    book.
-   </para>
-
-<!## PG>
-   <para>
-    If you feel you need more introductory material, please visit the PostgreSQL
-    <ulink url="http://www.postgresql.org">web site</ulink>
-    for links to more resources.
-   </para>
-<!## end>
-  </sect1>
- </chapter>
diff --git a/doc-xc/src/sgml/arch-dev.sgmlin b/doc-xc/src/sgml/arch-dev.sgmlin
deleted file mode 100644
index fe4ef807b8..0000000000
--- a/doc-xc/src/sgml/arch-dev.sgmlin
+++ /dev/null
@@ -1,1630 +0,0 @@
-<!-- doc/src/sgml/arch-dev.sgml -->
-
- <chapter id="overview">
-  <title>Overview of PostgreSQL Internals</title>
-
-  <note>
-   <title>Author</title>
-   <para>
-    This chapter originated as part of
-    <xref linkend="SIM98">, Stefan Simkovics'
-    Master's Thesis prepared at Vienna University of Technology under the direction
-    of O.Univ.Prof.Dr. Georg Gottlob and Univ.Ass. Mag. Katrin Seyr.
-   </para>
-  </note>
-
-<!## XC>
-  <para>
-   This chapter describes internals
-   of <productname>PostgreSQL</productname>
-   which <productname>Postgres-XC</productname> inherited most of
-   features.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   This chapter describes the internals
-   of <productname>PostgreSQL</productname>,
-   from which <productname>Postgres-XL</productname> inherited most of
-   features.
-  </para>
-<!## end>
-&common;
-
-  <para>
-   This chapter gives an overview of the internal structure of the
-   backend of <productname>PostgreSQL</productname>.  After having
-   read the following sections you should have an idea of how a query
-   is processed. This chapter does not aim to provide a detailed
-   description of the internal operation of
-   <productname>PostgreSQL</productname>, as such a document would be
-   very extensive. Rather, this chapter is intended to help the reader
-   understand the general sequence of operations that occur within the
-   backend from the point at which a query is received, to the point
-   at which the results are returned to the client.
-  </para>
-
-  <sect1 id="query-path">
-   <title>The Path of a Query</title>
-
-&common;
-   <para>
-    Here we give a short overview of the stages a query has to pass in
-    order to obtain a result.
-   </para>
-
-   <procedure>
-    <step>
-     <para>
-      A connection from an application program to the <productname>PostgreSQL</productname>
-      server has to be established. The application program transmits a
-      query to the server and waits to receive the results sent back by the
-      server.
-     </para>
-    </step>
-
-    <step>
-     <para>
-      The <firstterm>parser stage</firstterm> checks the query
-      transmitted by the application
-      program for correct syntax and creates
-      a <firstterm>query tree</firstterm>.
-     </para>
-    </step>
-
-    <step>
-     <para>
-      The <firstterm>rewrite system</firstterm> takes
-      the query tree created by the parser stage and looks for
-      any <firstterm>rules</firstterm> (stored in the
-      <firstterm>system catalogs</firstterm>) to apply to
-      the query tree.  It performs the
-      transformations given in the <firstterm>rule bodies</firstterm>.
-     </para>
-
-     <para>
-      One application of the rewrite system is in the realization of
-      <firstterm>views</firstterm>.
-      Whenever a query against a view
-      (i.e., a <firstterm>virtual table</firstterm>) is made,
-      the rewrite system rewrites the user's query to
-      a query that accesses the <firstterm>base tables</firstterm> given in
-      the <firstterm>view definition</firstterm> instead.
-     </para>
-    </step>
-
-    <step>
-     <para>
-      The <firstterm>planner/optimizer</firstterm> takes
-      the (rewritten) query tree and creates a
-      <firstterm>query plan</firstterm> that will be the input to the
-      <firstterm>executor</firstterm>.
-     </para>
-
-     <para>
-      It does so by first creating all possible <firstterm>paths</firstterm>
-      leading to the same result. For example if there is an index on a
-      relation to be scanned, there are two paths for the
-      scan. One possibility is a simple sequential scan and the other
-      possibility is to use the index. Next the cost for the execution of
-      each path is estimated and the cheapest path is chosen.  The cheapest
-      path is expanded into a complete plan that the executor can use.
-     </para>
-    </step>
-
-    <step>
-     <para>
-      The executor recursively steps through
-      the <firstterm>plan tree</firstterm> and
-      retrieves rows in the way represented by the plan.
-      The executor makes use of the
-      <firstterm>storage system</firstterm> while scanning
-      relations, performs <firstterm>sorts</firstterm> and <firstterm>joins</firstterm>,
-      evaluates <firstterm>qualifications</firstterm> and finally hands back the rows derived.
-     </para>
-    </step>
-   </procedure>
-
-   <para>
-    In the following sections we will cover each of the above listed items
-    in more detail to give a better understanding of <productname>PostgreSQL</productname>'s internal
-    control and data structures.
-   </para>
-  </sect1>
-
-  <sect1 id="connect-estab">
-   <title>How Connections are Established</title>
-
-&common;
-   <para>
-    <productname>PostgreSQL</productname> is implemented using a
-    simple <quote>process per user</> client/server model.  In this model
-    there is one <firstterm>client process</firstterm> connected to
-    exactly one <firstterm>server process</firstterm>.  As we do not
-    know ahead of time how many connections will be made, we have to
-    use a <firstterm>master process</firstterm> that spawns a new
-    server process every time a connection is requested. This master
-    process is called <literal>postgres</literal> and listens at a
-    specified TCP/IP port for incoming connections. Whenever a request
-    for a connection is detected the <literal>postgres</literal>
-    process spawns a new server process. The server tasks
-    communicate with each other using <firstterm>semaphores</firstterm> and
-    <firstterm>shared memory</firstterm> to ensure data integrity
-    throughout concurrent data access.
-   </para>
-
-   <para>
-    The client process can be any program that understands the
-    <productname>PostgreSQL</productname> protocol described in
-    <xref linkend="protocol">.  Many clients are based on the
-    C-language library <application>libpq</>, but several independent
-    implementations of the protocol exist, such as the Java
-    <application>JDBC</> driver.
-   </para>
-
-   <para>
-    Once a connection is established the client process can send a query
-    to the <firstterm>backend</firstterm> (server). The query is transmitted using plain text,
-    i.e., there is no parsing done in the <firstterm>frontend</firstterm> (client). The
-    server parses the query, creates an <firstterm>execution plan</firstterm>,
-    executes the plan and returns the retrieved rows to the client
-    by transmitting them over the established connection.
-   </para>
-  </sect1>
-
-  <sect1 id="parser-stage">
-   <title>The Parser Stage</title>
-
-&common;
-   <para>
-    The <firstterm>parser stage</firstterm> consists of two parts:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       The <firstterm>parser</firstterm> defined in
-       <filename>gram.y</filename> and <filename>scan.l</filename> is
-       built using the Unix tools <application>bison</application>
-       and <application>flex</application>.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       The <firstterm>transformation process</firstterm> does
-       modifications and augmentations to the data structures returned by the parser.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <sect2>
-    <title>Parser</title>
-
-&common;
-    <para>
-     The parser has to check the query string (which arrives as plain
-     ASCII text) for valid syntax. If the syntax is correct a
-     <firstterm>parse tree</firstterm> is built up and handed back;
-     otherwise an error is returned. The parser and lexer are
-     implemented using the well-known Unix tools <application>bison</>
-     and <application>flex</>.
-    </para>
-
-    <para>
-     The <firstterm>lexer</firstterm> is defined in the file
-     <filename>scan.l</filename> and is responsible
-     for recognizing <firstterm>identifiers</firstterm>,
-     the <firstterm>SQL key words</firstterm> etc. For
-     every key word or identifier that is found, a <firstterm>token</firstterm>
-     is generated and handed to the parser.
-    </para>
-
-    <para>
-     The parser is defined in the file <filename>gram.y</filename> and
-     consists of a set of <firstterm>grammar rules</firstterm> and
-     <firstterm>actions</firstterm> that are executed whenever a rule
-     is fired. The code of the actions (which is actually C code) is
-     used to build up the parse tree.
-    </para>
-
-    <para>
-     The file <filename>scan.l</filename> is transformed to the C
-     source file <filename>scan.c</filename> using the program
-     <application>flex</application> and <filename>gram.y</filename> is
-     transformed to <filename>gram.c</filename> using
-     <application>bison</application>.  After these transformations
-     have taken place a normal C compiler can be used to create the
-     parser. Never make any changes to the generated C files as they
-     will be overwritten the next time <application>flex</application>
-     or <application>bison</application> is called.
-
-     <note>
-      <para>
-       The mentioned transformations and compilations are normally done
-       automatically using the <firstterm>makefiles</firstterm>
-       shipped with the <productname>PostgreSQL</productname>
-       source distribution.
-      </para>
-     </note>
-    </para>
-
-    <para>
-     A detailed description of <application>bison</application> or
-     the grammar rules given in <filename>gram.y</filename> would be
-     beyond the scope of this paper. There are many books and
-     documents dealing with <application>flex</application> and
-     <application>bison</application>. You should be familiar with
-     <application>bison</application> before you start to study the
-     grammar given in <filename>gram.y</filename> otherwise you won't
-     understand what happens there.
-    </para>
-
-   </sect2>
-
-   <sect2>
-     <title>Transformation Process</title>
-
-&common;
-    <para>
-     The parser stage creates a parse tree using only fixed rules about
-     the syntactic structure of SQL.  It does not make any lookups in the
-     system catalogs, so there is no possibility to understand the detailed
-     semantics of the requested operations.  After the parser completes,
-     the <firstterm>transformation process</firstterm> takes the tree handed
-     back by the parser as input and does the semantic interpretation needed
-     to understand which tables, functions, and operators are referenced by
-     the query.  The data structure that is built to represent this
-     information is called the <firstterm>query tree</>.
-    </para>
-
-    <para>
-     The reason for separating raw parsing from semantic analysis is that
-     system catalog lookups can only be done within a transaction, and we
-     do not wish to start a transaction immediately upon receiving a query
-     string.  The raw parsing stage is sufficient to identify the transaction
-     control commands (<command>BEGIN</>, <command>ROLLBACK</>, etc), and
-     these can then be correctly executed without any further analysis.
-     Once we know that we are dealing with an actual query (such as
-     <command>SELECT</> or <command>UPDATE</>), it is okay to
-     start a transaction if we're not already in one.  Only then can the
-     transformation process be invoked.
-    </para>
-
-    <para>
-     The query tree created by the transformation process is structurally
-     similar to the raw parse tree in most places, but it has many differences
-     in detail.  For example, a <structname>FuncCall</> node in the
-     parse tree represents something that looks syntactically like a function
-     call.  This might be transformed to either a <structname>FuncExpr</>
-     or <structname>Aggref</> node depending on whether the referenced
-     name turns out to be an ordinary function or an aggregate function.
-     Also, information about the actual data types of columns and expression
-     results is added to the query tree.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="rule-system">
-   <title>The <productname>PostgreSQL</productname> Rule System</title>
-
-&common;
-   <para>
-    <productname>PostgreSQL</productname> supports a powerful
-    <firstterm>rule system</firstterm> for the specification
-    of <firstterm>views</firstterm> and ambiguous <firstterm>view updates</firstterm>.
-    Originally the <productname>PostgreSQL</productname>
-    rule system consisted of two implementations:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       The first one worked using <firstterm>row level</firstterm> processing and was
-       implemented deep in the <firstterm>executor</firstterm>. The rule system was
-       called whenever an individual row had been accessed. This
-       implementation was removed in 1995 when the last official release
-       of the <productname>Berkeley Postgres</productname> project was
-       transformed into <productname>Postgres95</productname>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The second implementation of the rule system is a technique
-       called <firstterm>query rewriting</firstterm>.
-       The <firstterm>rewrite system</firstterm> is a module
-       that exists between the <firstterm>parser stage</firstterm> and the
-       <firstterm>planner/optimizer</firstterm>. This technique is still implemented.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    The query rewriter is discussed in some detail in
-    <xref linkend="rules">, so there is no need to cover it here.
-    We will only point out that both the input and the output of the
-    rewriter are query trees, that is, there is no change in the
-    representation or level of semantic detail in the trees.  Rewriting
-    can be thought of as a form of macro expansion.
-   </para>
-
-  </sect1>
-
-  <sect1 id="planner-optimizer">
-   <title>Planner/Optimizer</title>
-
-&common;
-   <para>
-    The task of the <firstterm>planner/optimizer</firstterm> is to
-    create an optimal execution plan. A given SQL query (and hence, a
-    query tree) can be actually executed in a wide variety of
-    different ways, each of which will produce the same set of
-    results.  If it is computationally feasible, the query optimizer
-    will examine each of these possible execution plans, ultimately
-    selecting the execution plan that is expected to run the fastest.
-   </para>
-
-   <note>
-    <para>
-     In some situations, examining each possible way in which a query
-     can be executed would take an excessive amount of time and memory
-     space. In particular, this occurs when executing queries
-     involving large numbers of join operations. In order to determine
-     a reasonable (not necessarily optimal) query plan in a reasonable amount
-     of time, <productname>PostgreSQL</productname> uses a <firstterm>Genetic
-     Query Optimizer</firstterm> (see <xref linkend="geqo">) when the number of joins
-     exceeds a threshold (see <xref linkend="guc-geqo-threshold">).
-    </para>
-   </note>
-
-   <para>
-    The planner's search procedure actually works with data structures
-    called <firstterm>paths</>, which are simply cut-down representations of
-    plans containing only as much information as the planner needs to make
-    its decisions. After the cheapest path is determined, a full-fledged
-    <firstterm>plan tree</> is built to pass to the executor.  This represents
-    the desired execution plan in sufficient detail for the executor to run it.
-    In the rest of this section we'll ignore the distinction between paths
-    and plans.
-   </para>
-
-   <sect2>
-    <title>Generating Possible Plans</title>
-
-&common;
-    <para>
-     The planner/optimizer starts by generating plans for scanning each
-     individual relation (table) used in the query.  The possible plans
-     are determined by the available indexes on each relation.
-     There is always the possibility of performing a
-     sequential scan on a relation, so a sequential scan plan is always
-     created. Assume an index is defined on a
-     relation (for example a B-tree index) and a query contains the
-     restriction
-     <literal>relation.attribute OPR constant</literal>. If
-     <literal>relation.attribute</literal> happens to match the key of the B-tree
-     index and <literal>OPR</literal> is one of the operators listed in
-     the index's <firstterm>operator class</>, another plan is created using
-     the B-tree index to scan the relation. If there are further indexes
-     present and the restrictions in the query happen to match a key of an
-     index, further plans will be considered.  Index scan plans are also
-     generated for indexes that have a sort ordering that can match the
-     query's <literal>ORDER BY</> clause (if any), or a sort ordering that
-     might be useful for merge joining (see below).
-    </para>
-
-    <para>
-     If the query requires joining two or more relations,
-     plans for joining relations are considered
-     after all feasible plans have been found for scanning single relations.
-     The three available join strategies are:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        <firstterm>nested loop join</firstterm>: The right relation is scanned
-        once for every row found in the left relation. This strategy
-        is easy to implement but can be very time consuming.  (However,
-        if the right relation can be scanned with an index scan, this can
-        be a good strategy.  It is possible to use values from the current
-        row of the left relation as keys for the index scan of the right.)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <firstterm>merge join</firstterm>: Each relation is sorted on the join
-        attributes before the join starts. Then the two relations are
-        scanned in parallel, and matching rows are combined to form
-        join rows. This kind of join is more
-        attractive because each relation has to be scanned only once.
-        The required sorting might be achieved either by an explicit sort
-        step, or by scanning the relation in the proper order using an
-        index on the join key.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <firstterm>hash join</firstterm>: the right relation is first scanned
-        and loaded into a hash table, using its join attributes as hash keys.
-        Next the left relation is scanned and the
-        appropriate values of every row found are used as hash keys to
-        locate the matching rows in the table.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     When the query involves more than two relations, the final result
-     must be built up by a tree of join steps, each with two inputs.
-     The planner examines different possible join sequences to find the
-     cheapest one.
-    </para>
-
-    <para>
-     If the query uses fewer than <xref linkend="guc-geqo-threshold">
-     relations, a near-exhaustive search is conducted to find the best
-     join sequence.  The planner preferentially considers joins between any
-     two relations for which there exist a corresponding join clause in the
-     <literal>WHERE</literal> qualification (i.e., for
-     which a restriction like <literal>where rel1.attr1=rel2.attr2</literal>
-     exists). Join pairs with no join clause are considered only when there
-     is no other choice, that is, a particular relation has no available
-     join clauses to any other relation. All possible plans are generated for
-     every join pair considered by the planner, and the one that is
-     (estimated to be) the cheapest is chosen.
-    </para>
-
-    <para>
-     When <varname>geqo_threshold</varname> is exceeded, the join
-     sequences considered are determined by heuristics, as described
-     in <xref linkend="geqo">.  Otherwise the process is the same.
-    </para>
-
-    <para>
-     The finished plan tree consists of sequential or index scans of
-     the base relations, plus nested-loop, merge, or hash join nodes as
-     needed, plus any auxiliary steps needed, such as sort nodes or
-     aggregate-function calculation nodes.  Most of these plan node
-     types have the additional ability to do <firstterm>selection</>
-     (discarding rows that do not meet a specified Boolean condition)
-     and <firstterm>projection</> (computation of a derived column set
-     based on given column values, that is, evaluation of scalar
-     expressions where needed).  One of the responsibilities of the
-     planner is to attach selection conditions from the
-     <literal>WHERE</literal> clause and computation of required
-     output expressions to the most appropriate nodes of the plan
-     tree.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="executor">
-   <title>Executor</title>
-
-&common;
-   <para>
-    The <firstterm>executor</firstterm> takes the plan created by the
-    planner/optimizer and recursively processes it to extract the required set
-    of rows.  This is essentially a demand-pull pipeline mechanism.
-    Each time a plan node is called, it must deliver one more row, or
-    report that it is done delivering rows.
-   </para>
-
-   <para>
-    To provide a concrete example, assume that the top
-    node is a <literal>MergeJoin</literal> node.
-    Before any merge can be done two rows have to be fetched (one from
-    each subplan). So the executor recursively calls itself to
-    process the subplans (it starts with the subplan attached to
-    <literal>lefttree</literal>). The new top node (the top node of the left
-    subplan) is, let's say, a
-    <literal>Sort</literal> node and again recursion is needed to obtain
-    an input row.  The child node of the <literal>Sort</literal> might
-    be a <literal>SeqScan</> node, representing actual reading of a table.
-    Execution of this node causes the executor to fetch a row from the
-    table and return it up to the calling node.  The <literal>Sort</literal>
-    node will repeatedly call its child to obtain all the rows to be sorted.
-    When the input is exhausted (as indicated by the child node returning
-    a NULL instead of a row), the <literal>Sort</literal> code performs
-    the sort, and finally is able to return its first output row, namely
-    the first one in sorted order.  It keeps the remaining rows stored so
-    that it can deliver them in sorted order in response to later demands.
-   </para>
-
-   <para>
-    The <literal>MergeJoin</literal> node similarly demands the first row
-    from its right subplan.  Then it compares the two rows to see if they
-    can be joined; if so, it returns a join row to its caller.  On the next
-    call, or immediately if it cannot join the current pair of inputs,
-    it advances to the next row of one table
-    or the other (depending on how the comparison came out), and again
-    checks for a match.  Eventually, one subplan or the other is exhausted,
-    and the <literal>MergeJoin</literal> node returns NULL to indicate that
-    no more join rows can be formed.
-   </para>
-
-   <para>
-    Complex queries can involve many levels of plan nodes, but the general
-    approach is the same: each node computes and returns its next output
-    row each time it is called.  Each node is also responsible for applying
-    any selection or projection expressions that were assigned to it by
-    the planner.
-   </para>
-
-   <para>
-    The executor mechanism is used to evaluate all four basic SQL query types:
-    <command>SELECT</>, <command>INSERT</>, <command>UPDATE</>, and
-    <command>DELETE</>.  For <command>SELECT</>, the top-level executor
-    code only needs to send each row returned by the query plan tree off
-    to the client.  For <command>INSERT</>, each returned row is inserted
-    into the target table specified for the <command>INSERT</>.  This is
-    done in a special top-level plan node called <literal>ModifyTable</>.
-    (A simple
-    <command>INSERT ... VALUES</> command creates a trivial plan tree
-    consisting of a single <literal>Result</> node, which computes just one
-    result row, and <literal>ModifyTable</> above it to perform the insertion.
-    But <command>INSERT ... SELECT</> can demand the full power
-    of the executor mechanism.)  For <command>UPDATE</>, the planner arranges
-    that each computed row includes all the updated column values, plus
-    the <firstterm>TID</> (tuple ID, or row ID) of the original target row;
-    this data is fed into a <literal>ModifyTable</> node, which uses the
-    information to create a new updated row and mark the old row deleted.
-    For <command>DELETE</>, the only column that is actually returned by the
-    plan is the TID, and the <literal>ModifyTable</> node simply uses the TID
-    to visit each target row and mark it deleted.
-   </para>
-
-  </sect1>
-
- </chapter>
-
-
-<!## XC>
- <chapter id="xc-overview">
-  <title>Overview of <productname>Postgres-XC</productname> Internals</title>
-
-&xconly;
-  <para>
-   This chapter gives an overview of the internal structure
-   of <productname>Postgres-XC</productname>.
-  </para>
-
-  <sect1 id="xc-overview-components">
-   <title><productname>Postgres-XC</productname> Components</title>
-&xconly;
-   <para>
-    As described
-    in <xref linkend="intro-whatis">, <productname>Postgres-XC</productname>
-    is a database cluster which consists of multiple database servers
-    based
-    upon <productname>PostgreSQL</productname>.  <productname>Postgres-XC</productname>
-    provides global transparent transaction management to all the
-    database servers involved and provide both read and write
-    scalability.
-   </para>
-
-   <para>
-    To achieve these features, <productname>Postgres-XC</productname>
-    is composed of three major components as follows:
-
-    <variablelist>
-     <varlistentry>
-      <term>GTM</term>
-      <listitem>
-       <para>
-        GTM stands for global transaction manager.  It provides global
-        transaction ID and snapshot to each transaction
-        in <productname>Postgres-XC</productname> database cluster.
-        It also provide several global value such as sequence and
-        global timestamp.
-       </para>
-       <para>
-        To improve scalability itself, each server hardware or virtual
-        machine may have GTM-Proxy.  GTM-Proxy groups commands and
-        response from/to GTM to reduce number of interaction and the
-        amount of data which GTM reads and writes.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>Coordinator</term>
-      <listitem>
-       <para>
-        Coordinator is an entry point
-        to <productname>Postgres-XC</productname> from applications.
-        You can configure more than one Coordinators in the
-        same <productname>Postgres-XC</productname>.  With the help
-        of GTM, they provide transparent concurrency and integrity of
-        transactions globally.  Application can choose any
-        Coordinator to connect with.  Any Coordinator provides the
-        same view of the database.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>Datanode</term>
-      <listitem>
-       <para>
-        Datanode stores user data.  As described
-        in <xref linkend="whatis-in-short">
-        and <xref linkend="SQL-CREATETABLE">, more than one Datanodes
-        can be configured.  Each table can be replicated or
-          distributed among Datanodes.  A table is distributed, you can
-         choose a column as the distribute key, whose value is used to
-         determine which Datanode each row should be stored.
-        </para>
-       </listitem>
-      </varlistentry>
-    </variablelist>
-   </para>
-  </sect1>
-
-  <sect1 id="xc-overview-gtm">
-   <title>GTM and Global Transaction Management</title>
-&xconly;
-   <sect2 id="xc-overview-gtm-pgreview">
-    <title>Review of <productname>PostgreSQL</productname> Transaction Management Internals</title>
-&common;
-    <para>
-     In PostgreSQL, each transaction is given unique ID called
-     transaction ID (or XID). XID is given in ascending order to
-     distinguish which transaction is older/newer.
-     <footnote>
-      <para>
-       More precisely, XID is 32bit integer. When XID reaches the max
-       value, it wraps around to the lowest value (3, as to the latest
-       definition). PostgreSQL has a means to handle this, as well as
-       Postgres-XC. For simplicity, it will not be described in this
-       document.
-      </para>
-     </footnote>
-     When a transaction tries to read a tuple, 
-     <footnote>
-      <para>
-       This description is somewhat simplified for explanation. You
-       will find the precise rule in <filename>tqual.c</filename> file
-       in PostgreSQL's source code.
-      </para>
-     </footnote>
-     each tuple has a set of XIDs to indicate transactions which
-     created and deleted the tuple. So if the target tuple is created
-     by an active transaction, it is not committed or aborted and the
-     transaction should ignore such tuple. In such way (in practice,
-     this is done by versup module in PostgreSQL core), if we give
-     each transaction a unique transaction Id throughout the system
-     and maintain snapshot what transaction is active, not only in a
-     single server but transaction in all the servers, we can maintain
-     global consistent visibility of each tuple even when a server
-     accepts new statement from other transactions running on the
-     other server.
-    </para>
-    <para>
-     These information is stored in "<varname>xmin</varname>" and
-     "<varname>xmax</varname>" fields of each row of table. When
-     we <command>INSERT</command> rows, <varname>XID</varname> of
-     inserting transaction is recorded at xmin field. When we update
-     rows of tables (with <command>UPDATE</command>
-     or <command>DELETE</command> statement), PostgreSQL does not
-     simply overwrite the old rows. Instead, PostgreSQL
-     "<emphasis>marks</emphasis>" the old rows as
-     "<emphasis>deleted</emphasis>" by writing updating
-     transaction's <varname>XID</varname> to xmax field. In the case
-     of <command>UPDATE</command> (just
-     like <command>INSERT</command>), new rows are created whose xmin
-     field is "<emphasis>marked</emphasis>"
-     with <varname>XID</varname>s of the creating transaction.
-    </para>
-    <para>
-     These "<varname>xmin</varname>" and "<varname>xmax</varname>" are
-     used to determine which row is visible to a transaction. To do
-     this, PostgreSQL needs a data to indicate what transactions are
-     running, which is called the "<emphasis>snapshot</emphasis>".
-    </para>
-    <para>
-     If the creating transaction is not running, visibility of each
-     row depends upon the fact if the creating transaction was
-     committed or aborted. Suppose a row of a table which was created
-     by some transaction and is not deleted yet. If the creating
-     transaction is running, such row is visible to the transaction
-     which created the row, but not visible to other transactions.  If
-     the creating transaction is not running and was committed the row
-     is visible. If the transaction was aborted, this row is not
-     visible.
-    </para>
-    <para>
-     Therefore, PostgreSQL needs two kinds of information to determine
-     "which transaction is running" and "if an old transaction was
-     committed or aborted."
-    </para>
-    <para>
-     The former information is obtained as
-     "<emphasis>snapshot</emphasis>."  PostgreSQL maintains the latter
-     information as "<filename>CLOG</filename>."
-    </para>
-    <para>
-     PostgreSQL uses all these information to determine which row is
-     visible to a given transaction.
-    </para>
-   </sect2>
-
-   <sect2 id="xc-overview-global-mvcc">
-    <title>Making Transaction Management Global</title>
-&xconly;
-    <para>
-     In Postgres-XC, the following features of transaction management
-     and visibility checking were picked up:
-    </para>
-    <itemizedlist>
-     <listitem>
-      <para>
-       Assigning XID globally to transactions (GXID, Global
-       Transaction ID). This can be done globally to identify each
-       Transactions in the system.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Providing snapshot. GTM collects all the transaction's status
-       (running, committed, aborted etc.) to provide snapshot globally
-       (global snapshot). Please note that global snapshot
-       includes <varname>GXID</varname> initiated by other
-       Coordinators or Datanodes.  This is needed because some older
-       transaction may visit new server after a while. In this case,
-       if <varname>GXID</varname> of such a transaction is not
-       included in the snapshot, this transaction may be regarded as
-       "old enough" and uncommitted rows may be
-       read. If <varname>GXID</varname> of such transaction is
-       included in the snapshot from the beginning, such inconsistency
-       does not take place.
-      </para>
-     </listitem>
-    </itemizedlist>
-    <para>
-     To do this, <productname>Postgres-XC</productname> introduced a dedicated component called
-     GTM (Global Transaction Manager). GTM runs on one of the servers
-     and provide unique and ordered transaction id to each transaction
-     running on <productname>Postgres-XC</productname> servers. Because this is globally unique
-     ID, we call this <varname>GXID</varname> (Global Transaction Id).
-    </para>
-    <para>
-     GTM receives <varname>GXID</varname> request from transactions
-     and provide <varname>GXID</varname>. It also keep track of all
-     the transactions when it started and finished to generate
-     snapshot used to control each tuple visibility. Because snapshot
-     here is also global property, it is called <emphasis>Global
-     Snapshot</emphasis>.
-    </para>
-    <para>
-     As long as each transaction runs with <varname>GXID</varname> and
-     Global Snapshot, it can maintain consistent visibility throughout
-     the system and it is safe to run transactions in parallel in any
-     servers.  On the other hand, a transaction, composed of multiple
-     statements, can be executed using multiple servers maintaining
-     database consistency.
-    </para>
-    <para>
-     GTM provides Global Transaction Id to each transaction and keeps
-     track of the status of all the transactions, whether it is
-     running, committed or aborted, to calculate global snapshot to
-     maintain tuple visibility.
-    </para>
-    <para>
-     For this purpose, each transaction reports when it starts and
-     ends, as well as when it issues <command>PREPARE</command>
-     command in two-phase commit protocol.
-    </para>
-    <para>
-     Each transaction requests snapshot according to the transaction
-     isolation level as done in PostgreSQL. If the transaction
-     isolation level is "<emphasis>read committed</emphasis>", then
-     transaction will request a snapshot for each statement. If it is
-     "<emphasis>serializable</emphasis>" transaction will request a
-     snapshot at the beginning of transaction and reuse it thought the
-     transaction.
-    </para>
-   </sect2>
-
-   <sect2 id="xc-overview-gtm-proxy">
-    <title>Improving GTM Performance</title>
-&xconly;
-    <para>
-     Because GTM can be regarded as "serializing" all the transaction
-     processing, people may think that GTM can be a performance
-     bottleneck.
-    </para>
-
-    <para>
-     In fact, GTM can limit the whole scalability. GTM should not be
-     used in very slow network environment such as wide area
-     network. GTM architecture is intended to be used with Gigabit
-     local network.  We encourage to install Postgres-XC with local
-     Gigabit network with minimum latency, that is, use as fewer
-     switches involved in the connection among GTM, Coordinator and
-     Datanodes.
-    </para>
-
-    <sect3>
-     <title>Primitive GTM Implementation</title>
-
-     <para>
-      Primitive GTM implementation can be done as follows:
-     </para>
-
-    <procedure>
-     <step>
-      <para>
-       Coordinator backend is provided with GTM client library to
-       obtain GXID and snapshot and to report the transaction status.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       GTM opens a port to accept connection from each Coordinator and
-       Datanode backend. When GTM accepts a connection, it creates a
-       thread (GTM Thread) to handle request to GTM from the connected
-       Coordinator backend.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       GTM Thread receives each request, record it and
-       sends <varname>GXID</varname>, <emphasis>snapshot</emphasis>
-       and other response to the Coordinator backend.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       They are repeated until the Coordinator backend requests
-       disconnect.
-      </para>
-     </step>
-    </procedure>
-
-    </sect3>
-
-    <sect3>
-     <title>GTM Proxy Implementation</title>
-
-     <para>
-      You may have been noticed that each transaction is issuing
-      request to GTM so frequently and we can collect them into single
-      block of requests in each Coordinator to reduce the amount of
-      interaction, as <emphasis>GTM-Proxy</emphasis>.
-     </para>
-
-     <para>
-      In this configuration, each Coordinator and Datanode backend
-      does not connect to GTM directly. Instead, we have GTM Proxy
-      between GTM and Coordinator backend to group multiple requests
-      and responses. GTM Proxy, like GTM explained in the previous
-      sections, accepts connection from the Coordinator
-      backend. However, it does not create new thread. The following
-      paragraphs explains how GTM Proxy is initialized and how it
-      handles requests from Coordinator backends.
-     </para>
-
-     <para>
-      GTM Proxy, as well as GTM, is initialized as follows:
-     </para>
-
-     <procedure>
-      <step>
-       <para>
-        GTM starts up normally, but now can accept connections from
-        GTM proxies.
-       </para>
-      </step>
-
-      <step>
-       <para>
-        GTM Proxy starts up. GTM Proxy creates GTM Proxy Threads. Each
-        GTM Proxy Threads connect to the GTM in advance. The number of
-        GTM Proxy Threads can be specified at the startup. Typical
-        number of threads is one or two so it can save the number of
-        connections between GTM and Coordinators.
-       </para>
-      </step>
-
-      <step>
-       <para>
-        GTM Main Thread waits for the request connection from each
-        backend.
-       </para>
-      </step>
-
-     </procedure>
-
-     <para>
-      When each Coordinator backend requests for connection, Proxy
-      Main Thread assigns a GTM Proxy Thread to handle
-      request. Therefore, one GTM Proxy Thread handles multiple
-      Coordinator backends. If a Coordinator has one hundred
-      Coordinator backends and one GTM Proxy Thread, this thread takes
-      care of one hundred Coordinator backend.
-     </para>
-
-     <para>
-      Then GTM Proxy Thread scans all the requests from Coordinator
-      backend. If Coordinator is more busy, it is expected to capture
-      more requests in a single scan. Therefore, the proxy can group
-      many requests into single block of requests, to reduce the
-      number of interaction between GTM and the Coordinator.
-     </para>
-
-     <para>
-      Furthermore, in a single scan, we may have multiple request for
-      snapshots. Because these requests can be regarded as received at
-      the same time, we can represent multiple snapshots with single
-      one. This will reduce the amount of data which GTM provides.
-     </para>
-
-    </sect3>
-   </sect2>
-
-   <sect2 id="xc-overview-Coordinator">
-    <title>Coordinator</title>
-&xconly;
-    <para>
-     Coordinator handles SQL statements from applications and
-     determine which Datanode should be involved and generates local
-     SQL statements for each Datanode.  In the most simplest case, if
-     single Datanode is involved, the Coordinator simply proxies
-     incoming statement to the Datanode.  In more complicated case,
-     for example, if the target Datanode cannot be determined, then
-     the Coordinator generates local statements for each Datanode,
-     collects the result to materialize at the Coordinator for further
-     handling.  In this case, the Coordinator will try to optimize the
-     plan by
-     <itemizedlist>
-      <listitem>
-       <para>
-        Pushdown <command>WHERE</command> clause to Datanodes,
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        Pushdown <emphasis>joins</emphasis> to Datanodes,
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        Pushdown <emphasis>projection</emphasis> (column list in <command>SELECT</command> clause),
-        </para>
-      </listitem>
-      <listitem>
-       <para>
-        Pushdown <command>ORDER BY</command> clause, as well as other clauses.
-       </para>
-      </listitem>
-     </itemizedlist>
-
-     If a transaction is involved by more than one Datanodes and/or
-     Coordinators, the Coordinator will handle the transaction with
-     two-phase commit protocol internally.
-    </para>
-
-    <para>
-     In the case of aggregate
-     functions, <productname>Postgres-XC</productname> introduced new
-     function collection function between existing transition function
-     and finalize function.  Collection function runs on the
-     Coordinator to collect all the intermediate results from involved
-     Datanodes.  For details, see <xref linkend="xaggr">
-     and <xref linkend="SQL-CREATEAGGREGATE">.
-    </para>
-
-    <para>
-     In the case of reading replicated tables, Coordinator can choose
-     any Datanode to read.  The most efficient way is to select one
-     running in the same hardware or virtual machine.  This is
-     called <emphasis>preferred Datanode</emphasis> and can be
-     specified by a GUC local to each Coordinator.
-    </para>
-
-    <para>
-     On the other hand, in the case of writing replicated tables, all
-     the Coordinators choose the same Datanode to begin with to avoid
-     update conflicts.  This is called <emphasis>primary
-     Datanode</emphasis>.
-    </para>
-
-    <para>
-     Coordinators also take care of DDL statements.  Because DDL
-     statements handles system catalogs, which are replicated in all
-     the Coordinators and Datanodes, they are proxied to all the
-     Coordinators and Datanodes.  To synchronize the catalog update in
-     all the nodes, the Coordinator handles DDL with two-phase commit
-     protocol internally.
-    </para>
-
-   </sect2>
-
-   <sect2 id="xc-overview-Datanode">
-    <title>Datanode</title>
-&xconly;
-    <para>
-     While Coordinators handle cluster-wide SQL statements, Datanodes
-     take care of just local issues.  In this sense, Datanodes are
-     essentially <productname>PostgreSQL</productname> servers except
-     that transaction management information is obtained from GTM, as
-     well as other global value.
-    </para>
-
-   </sect2>
-
-
-   <sect2 id="xc-overview-pooler">
-    <title>Coordinator And Datanode Connection</title>
-
-    <para>
-     The number of connection between Coordinator and Datanode may
-     increase from time to time. This may leave unused connection and
-     waste system resources. Repeating real connect and disconnect
-     requires Datanode backend initialization which increases latency
-     and also wastes system resources.
-    </para>
-
-    <para>
-     For example, as in the case of GTM, if each Coordinator has one
-     hundred connections to applications and we have ten Coordinators,
-     after a while, each Coordinator may have connection to each data
-     node. It means that each Coordinator backend has ten connections
-     to Coordinators and each Coordinator has one thousand (10 x 10)
-     connections to Coordinators.
-    </para>
-
-    <para>
-     Because we consume much more resources for locks and other
-     control information per backend and only a few of such connection
-     is active at a given time, it is not a good idea to hold such
-     unused connection between Coordinator and Datanode.
-    </para>
-
-    <para>
-     To improve this, Postgres-XC is equipped with connection pooler
-     between Coordinator and Datanode. When a Coordinator backend
-     requires connection to a Datanode, the pooler looks for
-     appropriate connection from the pool. If there's an available
-     one, the pooler assigns it to the Coordinator backend. When the
-     connection is no longer needed, the Coordinator backend returns
-     the connection to the pooler. Pooler does not disconnect the
-     connection.  It keeps the connection to the pool for later reuse,
-     keeping Datanode backend running.
-    </para>
-
-   </sect2>
-
-  </sect1>
- </chapter>
-<!## end>
-<!## XL>
- <chapter id="xc-overview">
-  <title>Overview of <productname>Postgres-XL</productname> Internals</title>
-
-&xlonly;
-  <para>
-   This chapter gives an overview of the internal structure
-   of <productname>Postgres-XL</productname>.
-  </para>
-
-  <sect1 id="xc-overview-components">
-   <title><productname>Postgres-XL</productname> Components</title>
-&xlonly;
-   <para>
-    As described
-    in <xref linkend="intro-whatis">, <productname>Postgres-XL</productname>
-    is a database cluster which consists of multiple database servers
-    based
-    upon <productname>PostgreSQL</productname>.  <productname>Postgres-XL</productname>
-    provides global transparent transaction management to all the
-    database servers involved and provide both read and write
-    scalability.
-   </para>
-
-   <para>
-    To achieve these features, <productname>Postgres-XL</productname>
-    is composed of three major components as follows:
-
-    <variablelist>
-     <varlistentry>
-      <term>GTM</term>
-      <listitem>
-       <para>
-        GTM stands for Global Transaction Manager.  It provides global
-        transaction IDs and snapshots for each transaction
-        in the <productname>Postgres-XL</productname> database cluster.
-        It also provide several global values such as sequences and
-        global timestamps.
-       </para>
-       <para>
-        To improve scalability itself, each server hardware or virtual
-        machine may have GTM-Proxy.  GTM-Proxy groups commands and
-        response from/to GTM to reduce number of interaction and the
-        amount of data which GTM reads and writes.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>Coordinator</term>
-      <listitem>
-       <para>
-        Coordinator is an entry point
-        for <productname>Postgres-XL</productname> from applications.
-        You can configure more than one Coordinators in the
-        same <productname>Postgres-XL</productname>.  With the help
-        of GTM, they provide transparent concurrency and integrity of
-        transactions globally.  Applications can choose any
-        Coordinator to connect to.  Any Coordinator provides the
-        same view of the database.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>Datanode</term>
-      <listitem>
-       <para>
-        Datanode stores user data.  As described
-        in <xref linkend="whatis-in-short">
-        and <xref linkend="SQL-CREATETABLE">, more than one Datanodes
-        can be configured.  Each table can be replicated or
-          distributed among Datanodes.  A table is distributed, you can
-         choose a column as the distribute key, whose value is used to
-         determine which Datanode each row should be stored.
-        </para>
-       </listitem>
-      </varlistentry>
-    </variablelist>
-   </para>
-  </sect1>
-
-  <sect1 id="xc-overview-gtm">
-   <title>GTM and Global Transaction Management</title>
-&xlonly;
-   <sect2 id="xc-overview-gtm-pgreview">
-    <title>Review of <productname>PostgreSQL</productname> Transaction Management Internals</title>
-&common;
-    <para>
-     In PostgreSQL, each transaction is given unique ID called
-     transaction ID (or XID). XID is given in ascending order to
-     distinguish which transaction is older/newer.
-     <footnote>
-      <para>
-       More precisely, XID is 32bit integer. When XID reaches the max
-       value, it wraps around to the lowest value (3, as to the latest
-       definition). PostgreSQL has a means to handle this, as well as
-       Postgres-XL. For simplicity, it will not be described in this
-       document.
-      </para>
-     </footnote>
-     When a transaction tries to read a tuple, 
-     <footnote>
-      <para>
-       This description is somewhat simplified for explanation. You
-       will find the precise rule in <filename>tqual.c</filename> file
-       in PostgreSQL's source code.
-      </para>
-     </footnote>
-     each tuple has a set of XIDs to indicate transactions which
-     created and deleted the tuple. So if the target tuple is created
-     by an active transaction, it is not committed or aborted and the
-     transaction should ignore such tuple. In such way (in practice,
-     this is done by versup module in PostgreSQL core), if we give
-     each transaction a unique transaction Id throughout the system
-     and maintain snapshot what transaction is active, not only in a
-     single server but transaction in all the servers, we can maintain
-     global consistent visibility of each tuple even when a server
-     accepts new statement from other transactions running on the
-     other server.
-    </para>
-    <para>
-     These information is stored in "<varname>xmin</varname>" and
-     "<varname>xmax</varname>" fields of each row of table. When
-     we <command>INSERT</command> rows, <varname>XID</varname> of
-     inserting transaction is recorded at xmin field. When we update
-     rows of tables (with <command>UPDATE</command>
-     or <command>DELETE</command> statement), PostgreSQL does not
-     simply overwrite the old rows. Instead, PostgreSQL
-     "<emphasis>marks</emphasis>" the old rows as
-     "<emphasis>deleted</emphasis>" by writing updating
-     transaction's <varname>XID</varname> to xmax field. In the case
-     of <command>UPDATE</command> (just
-     like <command>INSERT</command>), new rows are created whose xmin
-     field is "<emphasis>marked</emphasis>"
-     with <varname>XID</varname>s of the creating transaction.
-    </para>
-    <para>
-     These "<varname>xmin</varname>" and "<varname>xmax</varname>" are
-     used to determine which row is visible to a transaction. To do
-     this, PostgreSQL needs a data to indicate what transactions are
-     running, which is called the "<emphasis>snapshot</emphasis>".
-    </para>
-    <para>
-     If the creating transaction is not running, visibility of each
-     row depends upon the fact if the creating transaction was
-     committed or aborted. Suppose a row of a table which was created
-     by some transaction and is not deleted yet. If the creating
-     transaction is running, such row is visible to the transaction
-     which created the row, but not visible to other transactions.  If
-     the creating transaction is not running and was committed the row
-     is visible. If the transaction was aborted, this row is not
-     visible.
-    </para>
-    <para>
-     Therefore, PostgreSQL needs two kinds of information to determine
-     "which transaction is running" and "if an old transaction was
-     committed or aborted."
-    </para>
-    <para>
-     The former information is obtained as
-     "<emphasis>snapshot</emphasis>."  PostgreSQL maintains the latter
-     information as "<filename>CLOG</filename>."
-    </para>
-    <para>
-     PostgreSQL uses all these information to determine which row is
-     visible to a given transaction.
-    </para>
-   </sect2>
-
-   <sect2 id="xc-overview-global-mvcc">
-    <title>Making Transaction Management Global</title>
-&xlonly;
-    <para>
-     In Postgres-XL, the following features of transaction management
-     and visibility checking extracted out from the nodes and pulled 
-     into the GTM.
-    </para>
-    <itemizedlist>
-     <listitem>
-      <para>
-       Assigning XID globally to transactions (GXID, Global
-       Transaction ID). This can be done globally to identify each
-       Transactions in the system.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Providing snapshots. GTM collects all the transaction's status
-       (running, committed, aborted etc.) to provide snapshots globally
-       (global snapshot). Please note that each global snapshot
-       includes <varname>GXID</varname> initiated by other
-       Coordinators or Datanodes.  This is needed because some older
-       transaction may visit new server after a while. In this case,
-       if <varname>GXID</varname> of such a transaction is not
-       included in the snapshot, this transaction may be regarded as
-       "old enough" and uncommitted rows may be
-       read. If <varname>GXID</varname> of such transaction is
-       included in the snapshot from the beginning, such inconsistency
-       does not take place.
-      </para>
-     </listitem>
-    </itemizedlist>
-    <para>
-     To do this, <productname>Postgres-XL</productname> introduced a dedicated component called
-     GTM (Global Transaction Manager). GTM runs on one of the servers
-     and provides unique and ordered transaction id to each transaction
-     running on <productname>Postgres-XL</productname> servers. Because this is a globally unique
-     ID, we call this <varname>GXID</varname> (Global Transaction Id).
-    </para>
-    <para>
-     GTM receives <varname>GXID</varname> request from transactions
-     and provide <varname>GXID</varname>. It also keeps track of all
-     the transactions when it started and finished to generate
-     snapshots used to control each tuple visibility. Because snapshots
-     here is also a global property, it is called <emphasis>Global
-     Snapshot</emphasis>.
-    </para>
-    <para>
-     As long as each transaction runs with a <varname>GXID</varname> and
-     a Global Snapshot, it can maintain consistent visibility throughout
-     the system and it is safe to run transactions in parallel in any
-     servers.  On the other hand, a transaction, composed of multiple
-     statements, can be executed using multiple servers maintaining
-     database consistency.
-    </para>
-    <para>
-     GTM provides Global Transaction Id to each transaction and keeps
-     track of the status of all the transactions, whether it is
-     running, committed or aborted, to calculate global snapshots to
-     maintain tuple visibility.
-    </para>
-    <para>
-     For this purpose, each transaction reports when it starts and
-     ends, as well as when it issues <command>PREPARE</command>
-     command in two-phase commit protocol.
-    </para>
-    <para>
-     Each transaction requests snapshots according to the transaction
-     isolation level as done in PostgreSQL. If the transaction
-     isolation level is "<emphasis>read committed</emphasis>", then
-     transaction will request a snapshot for each statement. If it is
-     "<emphasis>serializable</emphasis>" transaction will request a
-     snapshot at the beginning of transaction and reuse it thought the
-     transaction.
-    </para>
-   </sect2>
-
-   <sect2 id="xc-overview-gtm-proxy">
-    <title>Improving GTM Performance</title>
-&xlonly;
-    <para>
-     Because GTM can be regarded as "serializing" all the transaction
-     processing, people may think that GTM can be a performance
-     bottleneck.
-    </para>
-
-    <para>
-     In fact, GTM can limit the whole scalability. GTM should not be
-     used in very slow network environment such as wide area
-     network. GTM architecture is intended to be used with Gigabit
-     local network.  It is encouraged to install Postgres-XL with a local
-     Gigabit network with minimum latency, that is, use as few
-     switches involved in the connection among GTM, Coordinator and
-     Datanodes.
-     In addition, consider putting all components on their own subnet
-     if you have multiple network ports in the systems.
-    </para>
-
-    <sect3>
-     <title>Primitive GTM Implementation</title>
-
-     <para>
-      Primitive GTM implementation can be done as follows:
-     </para>
-
-    <procedure>
-     <step>
-      <para>
-       The Coordinator backend is provided with a GTM client library to
-       obtain GXID and snapshots and to report the transaction status.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       GTM opens a port to accept connections from each Coordinator and
-       Datanode backend. When GTM accepts a connection, it creates a
-       thread (GTM Thread) to handle requests to GTM from the connected
-       Coordinator backend.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       GTM Thread receives each request, records it and
-       sends <varname>GXID</varname>, <emphasis>snapshot</emphasis>
-       and other response to the Coordinator backend.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       They are repeated until the Coordinator backend requests
-       disconnect.
-      </para>
-     </step>
-    </procedure>
-
-    </sect3>
-
-    <sect3>
-     <title>GTM Proxy Implementation</title>
-
-     <para>
-      Each transaction is issuing
-      requests to GTM frequently.  We can collect them into single
-      block of requests in each Coordinator to reduce the amount of
-      interaction by using a <emphasis>GTM-Proxy</emphasis>.
-     </para>
-
-     <para>
-      In this configuration, each Coordinator and Datanode backend
-      does not connect to GTM directly. Instead, we have GTM Proxy
-      between GTM and Coordinator backend to group multiple requests
-      and responses. GTM Proxy, like GTM explained in the previous
-      sections, accepts connections from the Coordinator
-      backend. However, it does not create new thread. The following
-      paragraphs explains how GTM Proxy is initialized and how it
-      handles requests from Coordinator backends.
-     </para>
-
-     <para>
-      GTM Proxy, as well as GTM, is initialized as follows:
-     </para>
-
-     <procedure>
-      <step>
-       <para>
-        GTM starts up normally, but now can accept connections from
-        GTM proxies.
-       </para>
-      </step>
-
-      <step>
-       <para>
-        GTM Proxy starts up. GTM Proxy creates GTM Proxy Threads. Each
-        GTM Proxy Thread connects to the GTM in advance. The number of
-        GTM Proxy Threads can be specified at the startup. A typical
-        number of threads is one or two so it can save the number of
-        connections between GTM and Coordinators.
-       </para>
-      </step>
-
-      <step>
-       <para>
-        GTM Main Thread waits for the request connection from each
-        backend.
-       </para>
-      </step>
-
-     </procedure>
-
-     <para>
-      When each Coordinator backend requests for connection, the Proxy
-      Main Thread assigns a GTM Proxy Thread to handle
-      request. Therefore, one GTM Proxy Thread handles multiple
-      Coordinator backends. If a Coordinator has one hundred
-      Coordinator backends and one GTM Proxy Thread, this thread takes
-      care of one hundred Coordinator backend.
-     </para>
-
-     <para>
-      Then GTM Proxy Thread scans all the requests from Coordinator
-      backend. If Coordinator is busy, it is expected to capture
-      more requests in a single scan. Therefore, the proxy can group
-      many requests into single block of requests, to reduce the
-      number of interaction between GTM and the Coordinator.
-     </para>
-
-     <para>
-      Furthermore, in a single scan, we may have multiple request for
-      snapshots. Because these requests can be regarded as received at
-      the same time, we can represent multiple snapshots with single
-      one. This will reduce the amount of data which GTM provides.
-     </para>
-
-    </sect3>
-   </sect2>
-
-   <sect2 id="xc-overview-Coordinator">
-    <title>Coordinator</title>
-&xlonly;
-    <para>
-     Coordinator handles SQL statements from applications and
-     determines which Datanode should be involved and generates local
-     SQL statements for each Datanode.  In the most simplest case, if
-     a single Datanode is involved, the Coordinator simply proxies
-     incoming statements to the Datanode.  In more complicated cases,
-     for example, if the target Datanode cannot be determined, then
-     the Coordinator generates local statements for each Datanode,
-     collects the result to materialize at the Coordinator for further
-     handling.  In this case, the Coordinator will try to optimize the
-     plan by
-     <itemizedlist>
-      <listitem>
-       <para>
-        Pushdown <command>WHERE</command> clause to Datanodes,
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        Pushdown <emphasis>joins</emphasis> to Datanodes,
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        Pushdown <emphasis>projection</emphasis> (column list in <command>SELECT</command> clause),
-        </para>
-      </listitem>
-      <listitem>
-       <para>
-        Pushdown <command>ORDER BY</command> clause, as well as other clauses.
-       </para>
-      </listitem>
-     </itemizedlist>
-
-     If a transaction is involved by more than one Datanodes and/or
-     Coordinators, the Coordinator will handle the transaction with
-     two-phase commit protocol internally.
-    </para>
-
-    <para>
-     In the case of aggregate
-     functions, <productname>Postgres-XL</productname> introduced new
-     function collection function between existing transition function
-     and finalize function.  Collection function runs on the
-     Coordinator to collect all the intermediate results from involved
-     Datanodes.  For details, see <xref linkend="xaggr">
-     and <xref linkend="SQL-CREATEAGGREGATE">.
-    </para>
-
-    <para>
-     In the case of reading replicated tables, the Coordinator can choose
-     any Datanode to read.  The most efficient way is to select one
-     running in the same hardware or virtual machine.  This is
-     called <emphasis>preferred Datanode</emphasis> and can be
-     specified by a GUC local to each Coordinator.
-    </para>
-
-    <para>
-     On the other hand, in the case of writing replicated tables, all
-     the Coordinators choose the same Datanode to begin with to avoid
-     update conflicts.  This is called <emphasis>primary
-     Datanode</emphasis>.
-    </para>
-
-    <para>
-     Coordinators also take care of DDL statements.  Because DDL
-     statements handles system catalogs, which are replicated in all
-     the Coordinators and Datanodes, they are proxied to all the
-     Coordinators and Datanodes.  To synchronize the catalog update in
-     all the nodes, the Coordinator handles DDL with two-phase commit
-     protocol internally.
-    </para>
-
-   </sect2>
-
-   <sect2 id="xc-overview-Datanode">
-    <title>Datanode</title>
-&xlonly;
-    <para>
-     While Coordinators handle cluster-wide SQL statements, Datanodes
-     take care of just local issues.  In this sense, Datanodes are
-     essentially <productname>PostgreSQL</productname> servers except
-     that transaction management information is obtained from GTM, as
-     well as other global value.
-    </para>
-
-   </sect2>
-
-
-   <sect2 id="xc-overview-pooler">
-    <title>Coordinator And Datanode Connection</title>
-
-    <para>
-     The number of connections between Coordinators and Datanodes may
-     increase from time to time. This may leave unused connection and
-     waste system resources. Repeating real connect and disconnect
-     requires Datanode backend initialization which increases latency
-     and also wastes system resources.
-    </para>
-
-    <para>
-     For example, as in the case of GTM, if each Coordinator has one
-     hundred connections to applications and we have ten Coordinators,
-     after a while, each Coordinator may have connection to each data
-     node. It means that each Coordinator backend has ten connections
-     to Coordinators and each Coordinator has one thousand (10 x 10)
-     connections to Coordinators.
-    </para>
-
-    <para>
-     Because we consume much more resources for locks and other
-     control information per backend and only a few of such connection
-     is active at a given time, it is not a good idea to hold such
-     unused connections between Coordinator and Datanode.
-    </para>
-
-    <para>
-     To improve this, Postgres-XL is equipped with connection pooler
-     between Coordinator and Datanode. When a Coordinator backend
-     requires connection to a Datanode, the pooler looks for
-     appropriate connection from the pool. If there's an available
-     one, the pooler assigns it to the Coordinator backend. When the
-     connection is no longer needed, the Coordinator backend returns
-     the connection to the pooler. The pooler does not disconnect the
-     connection.  It keeps the connection to the pool for later reuse,
-     keeping Datanode backend running.
-    </para>
-
-   </sect2>
-
-  </sect1>
- </chapter>
-<!## end>
-  
diff --git a/doc-xc/src/sgml/array.sgmlin b/doc-xc/src/sgml/array.sgmlin
deleted file mode 100644
index 2e7220426e..0000000000
--- a/doc-xc/src/sgml/array.sgmlin
+++ /dev/null
@@ -1,749 +0,0 @@
-<!-- doc/src/sgml/array.sgml -->
-
-<sect1 id="arrays">
- <title>Arrays</title>
-
- <indexterm>
-  <primary>array</primary>
- </indexterm>
-&common;
- <para>
-<!## PG>
-  <productname>PostgreSQL</productname> allows columns of a table to be
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> allows columns of a table to be
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> allows columns of a table to be
-<!## end>
-  defined as variable-length multidimensional arrays. Arrays of any
-  built-in or user-defined base type, enum type, or composite type
-  can be created.
-  Arrays of domains are not yet supported.
- </para>
-
- <sect2 id="arrays-declaration">
-  <title>Declaration of Array Types</title>
-
-  <indexterm>
-   <primary>array</primary>
-   <secondary>declaration</secondary>
-  </indexterm>
-&common;
- <para>
-  To illustrate the use of array types, we create this table:
-<programlisting>
-CREATE TABLE sal_emp (
-    name            text,
-    pay_by_quarter  integer[],
-    schedule        text[][]
-);
-</programlisting>
-  As shown, an array data type is named by appending square brackets
-  (<literal>[]</>) to the data type name of the array elements.  The
-  above command will create a table named
-  <structname>sal_emp</structname> with a column of type
-  <type>text</type> (<structfield>name</structfield>), a
-  one-dimensional array of type <type>integer</type>
-  (<structfield>pay_by_quarter</structfield>), which represents the
-  employee's salary by quarter, and a two-dimensional array of
-  <type>text</type> (<structfield>schedule</structfield>), which
-  represents the employee's weekly schedule.
- </para>
-
- <para>
-  The syntax for <command>CREATE TABLE</command> allows the exact size of
-  arrays to be specified, for example:
-
-<programlisting>
-CREATE TABLE tictactoe (
-    squares   integer[3][3]
-);
-</programlisting>
-
-  However, the current implementation ignores any supplied array size
-  limits, i.e., the behavior is the same as for arrays of unspecified
-  length.
- </para>
-
- <para>
-  The current implementation does not enforce the declared
-  number of dimensions either.  Arrays of a particular element type are
-  all considered to be of the same type, regardless of size or number
-  of dimensions.  So, declaring the array size or number of dimensions in
-  <command>CREATE TABLE</command> is simply documentation; it does not
-  affect run-time behavior.
- </para>
-
- <para>
-  An alternative syntax, which conforms to the SQL standard by using
-  the keyword <literal>ARRAY</>, can be used for one-dimensional arrays.
-  <structfield>pay_by_quarter</structfield> could have been defined
-  as:
-<programlisting>
-    pay_by_quarter  integer ARRAY[4],
-</programlisting>
-  Or, if no array size is to be specified:
-<programlisting>
-    pay_by_quarter  integer ARRAY,
-</programlisting>
-<!## PG>
-  As before, however, <productname>PostgreSQL</> does not enforce the
-<!## end>
-<!## XC>
-  As before, however, <productname>Postgres-XC</> does not enforce the
-<!## end>
-<!## XL>
-  As before, however, <productname>Postgres-XL</> does not enforce the
-<!## end>
-  size restriction in any case.
- </para>
- </sect2>
-
- <sect2 id="arrays-input">
-  <title>Array Value Input</title>
-
-  <indexterm>
-   <primary>array</primary>
-   <secondary>constant</secondary>
-  </indexterm>
-&common;
-  <para>
-   To write an array value as a literal constant, enclose the element
-   values within curly braces and separate them by commas.  (If you
-   know C, this is not unlike the C syntax for initializing
-   structures.)  You can put double quotes around any element value,
-   and must do so if it contains commas or curly braces.  (More
-   details appear below.)  Thus, the general format of an array
-   constant is the following:
-<synopsis>
-'{ <replaceable>val1</replaceable> <replaceable>delim</replaceable> <replaceable>val2</replaceable> <replaceable>delim</replaceable> ... }'
-</synopsis>
-   where <replaceable>delim</replaceable> is the delimiter character
-   for the type, as recorded in its <literal>pg_type</literal> entry.
-   Among the standard data types provided in the
-<!## PG>
-   <productname>PostgreSQL</productname> distribution, all use a comma
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> distribution, all use a comma
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> distribution, all use a comma
-<!## end>
-   (<literal>,</>), except for type <type>box</> which uses a semicolon
-   (<literal>;</>). Each <replaceable>val</replaceable> is
-   either a constant of the array element type, or a subarray. An example
-   of an array constant is:
-<programlisting>
-'{{1,2,3},{4,5,6},{7,8,9}}'
-</programlisting>
-   This constant is a two-dimensional, 3-by-3 array consisting of
-   three subarrays of integers.
-  </para>
-
-  <para>
-   To set an element of an array constant to NULL, write <literal>NULL</>
-   for the element value.  (Any upper- or lower-case variant of
-   <literal>NULL</> will do.)  If you want an actual string value
-   <quote>NULL</>, you must put double quotes around it.
-  </para>
-
-  <para>
-   (These kinds of array constants are actually only a special case of
-   the generic type constants discussed in <xref
-   linkend="sql-syntax-constants-generic">.  The constant is initially
-   treated as a string and passed to the array input conversion
-   routine.  An explicit type specification might be necessary.)
-  </para>
-
-  <para>
-   Now we can show some <command>INSERT</command> statements:
-
-<programlisting>
-INSERT INTO sal_emp
-    VALUES ('Bill',
-    '{10000, 10000, 10000, 10000}',
-    '{{"meeting", "lunch"}, {"training", "presentation"}}');
-
-INSERT INTO sal_emp
-    VALUES ('Carol',
-    '{20000, 25000, 25000, 25000}',
-    '{{"breakfast", "consulting"}, {"meeting", "lunch"}}');
-</programlisting>
-  </para>
-
- <para>
-  The result of the previous two inserts looks like this:
-
-<programlisting>
-SELECT * FROM sal_emp;
- name  |      pay_by_quarter       |                 schedule
--------+---------------------------+-------------------------------------------
- Bill  | {10000,10000,10000,10000} | {{meeting,lunch},{training,presentation}}
- Carol | {20000,25000,25000,25000} | {{breakfast,consulting},{meeting,lunch}}
-(2 rows)
-</programlisting>
- </para>
-
- <para>
-  Multidimensional arrays must have matching extents for each
-  dimension. A mismatch causes an error, for example:
-
-<programlisting>
-INSERT INTO sal_emp
-    VALUES ('Bill',
-    '{10000, 10000, 10000, 10000}',
-    '{{"meeting", "lunch"}, {"meeting"}}');
-ERROR:  multidimensional arrays must have array expressions with matching dimensions
-</programlisting>
- </para>
-
- <para>
-  The <literal>ARRAY</> constructor syntax can also be used:
-<programlisting>
-INSERT INTO sal_emp
-    VALUES ('Bill',
-    ARRAY[10000, 10000, 10000, 10000],
-    ARRAY[['meeting', 'lunch'], ['training', 'presentation']]);
-
-INSERT INTO sal_emp
-    VALUES ('Carol',
-    ARRAY[20000, 25000, 25000, 25000],
-    ARRAY[['breakfast', 'consulting'], ['meeting', 'lunch']]);
-</programlisting>
-  Notice that the array elements are ordinary SQL constants or
-  expressions; for instance, string literals are single quoted, instead of
-  double quoted as they would be in an array literal.  The <literal>ARRAY</>
-  constructor syntax is discussed in more detail in
-  <xref linkend="sql-syntax-array-constructors">.
- </para>
- </sect2>
-
- <sect2 id="arrays-accessing">
-  <title>Accessing Arrays</title>
-
-  <indexterm>
-   <primary>array</primary>
-   <secondary>accessing</secondary>
-  </indexterm>
-&common;
- <para>
-  Now, we can run some queries on the table.
-  First, we show how to access a single element of an array.
-  This query retrieves the names of the employees whose pay changed in
-  the second quarter:
-
-<programlisting>
-SELECT name FROM sal_emp WHERE pay_by_quarter[1] &lt;&gt; pay_by_quarter[2];
-
- name
--------
- Carol
-(1 row)
-</programlisting>
-
-  The array subscript numbers are written within square brackets.
-<!## PG>
-  By default <productname>PostgreSQL</productname> uses a
-<!## end>
-<!## XC>
-  By default <productname>Postgres-XC</productname> uses a
-<!## end>
-<!## XL>
-  By default <productname>Postgres-XL</productname> uses a
-<!## end>
-  one-based numbering convention for arrays, that is,
-  an array of <replaceable>n</> elements starts with <literal>array[1]</literal> and
-  ends with <literal>array[<replaceable>n</>]</literal>.
- </para>
-
- <para>
-  This query retrieves the third quarter pay of all employees:
-
-<programlisting>
-SELECT pay_by_quarter[3] FROM sal_emp;
-
- pay_by_quarter
-----------------
-          10000
-          25000
-(2 rows)
-</programlisting>
- </para>
-
- <para>
-  We can also access arbitrary rectangular slices of an array, or
-  subarrays.  An array slice is denoted by writing
-  <literal><replaceable>lower-bound</replaceable>:<replaceable>upper-bound</replaceable></literal>
-  for one or more array dimensions.  For example, this query retrieves the first
-  item on Bill's schedule for the first two days of the week:
-
-<programlisting>
-SELECT schedule[1:2][1:1] FROM sal_emp WHERE name = 'Bill';
-
-        schedule
-------------------------
- {{meeting},{training}}
-(1 row)
-</programlisting>
-
-  If any dimension is written as a slice, i.e., contains a colon, then all
-  dimensions are treated as slices.  Any dimension that has only a single
-  number (no colon) is treated as being from 1
-  to the number specified.  For example, <literal>[2]</> is treated as
-  <literal>[1:2]</>, as in this example:
-
-<programlisting>
-SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';
-
-                 schedule
--------------------------------------------
- {{meeting,lunch},{training,presentation}}
-(1 row)
-</programlisting>
-
-  To avoid confusion with the non-slice case, it's best to use slice syntax
-  for all dimensions, e.g., <literal>[1:2][1:1]</>, not <literal>[2][1:1]</>.
- </para>
-
- <para>
-  An array subscript expression will return null if either the array itself or
-  any of the subscript expressions are null.  Also, null is returned if a
-  subscript is outside the array bounds (this case does not raise an error).
-  For example, if <literal>schedule</>
-  currently has the dimensions <literal>[1:3][1:2]</> then referencing
-  <literal>schedule[3][3]</> yields NULL.  Similarly, an array reference
-  with the wrong number of subscripts yields a null rather than an error.
- </para>
-
- <para>
-  An array slice expression likewise yields null if the array itself or
-  any of the subscript expressions are null.  However, in other
-  cases such as selecting an array slice that
-  is completely outside the current array bounds, a slice expression
-  yields an empty (zero-dimensional) array instead of null.  (This
-  does not match non-slice behavior and is done for historical reasons.)
-  If the requested slice partially overlaps the array bounds, then it
-  is silently reduced to just the overlapping region instead of
-  returning null.
- </para>
-
- <para>
-  The current dimensions of any array value can be retrieved with the
-  <function>array_dims</function> function:
-
-<programlisting>
-SELECT array_dims(schedule) FROM sal_emp WHERE name = 'Carol';
-
- array_dims
-------------
- [1:2][1:2]
-(1 row)
-</programlisting>
-
-  <function>array_dims</function> produces a <type>text</type> result,
-  which is convenient for people to read but perhaps inconvenient
-  for programs.  Dimensions can also be retrieved with
-  <function>array_upper</function> and <function>array_lower</function>,
-  which return the upper and lower bound of a
-  specified array dimension, respectively:
-
-<programlisting>
-SELECT array_upper(schedule, 1) FROM sal_emp WHERE name = 'Carol';
-
- array_upper
--------------
-           2
-(1 row)
-</programlisting>
-
- <function>array_length</function> will return the length of a specified
- array dimension:
-
-<programlisting>
-SELECT array_length(schedule, 1) FROM sal_emp WHERE name = 'Carol';
-
- array_length
---------------
-            2
-(1 row)
-</programlisting>
- </para>
- </sect2>
-
- <sect2 id="arrays-modifying">
-  <title>Modifying Arrays</title>
-
-  <indexterm>
-   <primary>array</primary>
-   <secondary>modifying</secondary>
-  </indexterm>
-&common;
- <para>
-  An array value can be replaced completely:
-
-<programlisting>
-UPDATE sal_emp SET pay_by_quarter = '{25000,25000,27000,27000}'
-    WHERE name = 'Carol';
-</programlisting>
-
-  or using the <literal>ARRAY</literal> expression syntax:
-
-<programlisting>
-UPDATE sal_emp SET pay_by_quarter = ARRAY[25000,25000,27000,27000]
-    WHERE name = 'Carol';
-</programlisting>
-
-  An array can also be updated at a single element:
-
-<programlisting>
-UPDATE sal_emp SET pay_by_quarter[4] = 15000
-    WHERE name = 'Bill';
-</programlisting>
-
-  or updated in a slice:
-
-<programlisting>
-UPDATE sal_emp SET pay_by_quarter[1:2] = '{27000,27000}'
-    WHERE name = 'Carol';
-</programlisting>
-
- </para>
-
- <para>
-  A stored array value can be enlarged by assigning to elements not already
-  present.  Any positions between those previously present and the newly
-  assigned elements will be filled with nulls.  For example, if array
-  <literal>myarray</> currently has 4 elements, it will have six
-  elements after an update that assigns to <literal>myarray[6]</>;
-  <literal>myarray[5]</> will contain null.
-  Currently, enlargement in this fashion is only allowed for one-dimensional
-  arrays, not multidimensional arrays.
- </para>
-
- <para>
-  Subscripted assignment allows creation of arrays that do not use one-based
-  subscripts.  For example one might assign to <literal>myarray[-2:7]</> to
-  create an array with subscript values from -2 to 7.
- </para>
-
- <para>
-  New array values can also be constructed using the concatenation operator,
-  <literal>||</literal>:
-<programlisting>
-SELECT ARRAY[1,2] || ARRAY[3,4];
- ?column?
------------
- {1,2,3,4}
-(1 row)
-
-SELECT ARRAY[5,6] || ARRAY[[1,2],[3,4]];
-      ?column?
----------------------
- {{5,6},{1,2},{3,4}}
-(1 row)
-</programlisting>
- </para>
-
- <para>
-  The concatenation operator allows a single element to be pushed onto the
-  beginning or end of a one-dimensional array. It also accepts two
-  <replaceable>N</>-dimensional arrays, or an <replaceable>N</>-dimensional
-  and an <replaceable>N+1</>-dimensional array.
- </para>
-
- <para>
-  When a single element is pushed onto either the beginning or end of a
-  one-dimensional array, the result is an array with the same lower bound
-  subscript as the array operand. For example:
-<programlisting>
-SELECT array_dims(1 || '[0:1]={2,3}'::int[]);
- array_dims
-------------
- [0:2]
-(1 row)
-
-SELECT array_dims(ARRAY[1,2] || 3);
- array_dims
-------------
- [1:3]
-(1 row)
-</programlisting>
- </para>
-
- <para>
-  When two arrays with an equal number of dimensions are concatenated, the
-  result retains the lower bound subscript of the left-hand operand's outer
-  dimension. The result is an array comprising every element of the left-hand
-  operand followed by every element of the right-hand operand. For example:
-<programlisting>
-SELECT array_dims(ARRAY[1,2] || ARRAY[3,4,5]);
- array_dims
-------------
- [1:5]
-(1 row)
-
-SELECT array_dims(ARRAY[[1,2],[3,4]] || ARRAY[[5,6],[7,8],[9,0]]);
- array_dims
-------------
- [1:5][1:2]
-(1 row)
-</programlisting>
- </para>
-
- <para>
-  When an <replaceable>N</>-dimensional array is pushed onto the beginning
-  or end of an <replaceable>N+1</>-dimensional array, the result is
-  analogous to the element-array case above. Each <replaceable>N</>-dimensional
-  sub-array is essentially an element of the <replaceable>N+1</>-dimensional
-  array's outer dimension. For example:
-<programlisting>
-SELECT array_dims(ARRAY[1,2] || ARRAY[[3,4],[5,6]]);
- array_dims
-------------
- [1:3][1:2]
-(1 row)
-</programlisting>
- </para>
-
- <para>
-  An array can also be constructed by using the functions
-  <function>array_prepend</function>, <function>array_append</function>,
-  or <function>array_cat</function>. The first two only support one-dimensional
-  arrays, but <function>array_cat</function> supports multidimensional arrays.
-
-  Note that the concatenation operator discussed above is preferred over
-  direct use of these functions. In fact, these functions primarily exist for use
-  in implementing the concatenation operator. However, they might be directly
-  useful in the creation of user-defined aggregates. Some examples:
-
-<programlisting>
-SELECT array_prepend(1, ARRAY[2,3]);
- array_prepend
----------------
- {1,2,3}
-(1 row)
-
-SELECT array_append(ARRAY[1,2], 3);
- array_append
---------------
- {1,2,3}
-(1 row)
-
-SELECT array_cat(ARRAY[1,2], ARRAY[3,4]);
- array_cat
------------
- {1,2,3,4}
-(1 row)
-
-SELECT array_cat(ARRAY[[1,2],[3,4]], ARRAY[5,6]);
-      array_cat
----------------------
- {{1,2},{3,4},{5,6}}
-(1 row)
-
-SELECT array_cat(ARRAY[5,6], ARRAY[[1,2],[3,4]]);
-      array_cat
----------------------
- {{5,6},{1,2},{3,4}}
-</programlisting>
- </para>
- </sect2>
-
- <sect2 id="arrays-searching">
-  <title>Searching in Arrays</title>
-
-  <indexterm>
-   <primary>array</primary>
-   <secondary>searching</secondary>
-  </indexterm>
-&common;
- <para>
-  To search for a value in an array, each value must be checked.
-  This can be done manually, if you know the size of the array.
-  For example:
-
-<programlisting>
-SELECT * FROM sal_emp WHERE pay_by_quarter[1] = 10000 OR
-                            pay_by_quarter[2] = 10000 OR
-                            pay_by_quarter[3] = 10000 OR
-                            pay_by_quarter[4] = 10000;
-</programlisting>
-
-  However, this quickly becomes tedious for large arrays, and is not
-  helpful if the size of the array is unknown. An alternative method is
-  described in <xref linkend="functions-comparisons">. The above
-  query could be replaced by:
-
-<programlisting>
-SELECT * FROM sal_emp WHERE 10000 = ANY (pay_by_quarter);
-</programlisting>
-
-  In addition, you can find rows where the array has all values
-  equal to 10000 with:
-
-<programlisting>
-SELECT * FROM sal_emp WHERE 10000 = ALL (pay_by_quarter);
-</programlisting>
-
- </para>
-
- <para>
-  Alternatively, the <function>generate_subscripts</> function can be used.
-  For example:
-
-<programlisting>
-SELECT * FROM
-   (SELECT pay_by_quarter,
-           generate_subscripts(pay_by_quarter, 1) AS s
-      FROM sal_emp) AS foo
- WHERE pay_by_quarter[s] = 10000;
-</programlisting>
-
-  This function is described in <xref linkend="functions-srf-subscripts">.
- </para>
-
- <tip>
-  <para>
-   Arrays are not sets; searching for specific array elements
-   can be a sign of database misdesign.  Consider
-   using a separate table with a row for each item that would be an
-   array element.  This will be easier to search, and is likely to
-   scale better for a large number of elements.
-  </para>
- </tip>
- </sect2>
-
- <sect2 id="arrays-io">
-  <title>Array Input and Output Syntax</title>
-
-  <indexterm>
-   <primary>array</primary>
-   <secondary>I/O</secondary>
-  </indexterm>
-&common;
-  <para>
-   The external text representation of an array value consists of items that
-   are interpreted according to the I/O conversion rules for the array's
-   element type, plus decoration that indicates the array structure.
-   The decoration consists of curly braces (<literal>{</> and <literal>}</>)
-   around the array value plus delimiter characters between adjacent items.
-   The delimiter character is usually a comma (<literal>,</>) but can be
-   something else: it is determined by the <literal>typdelim</> setting
-   for the array's element type.  Among the standard data types provided
-<!## PG>
-   in the <productname>PostgreSQL</productname> distribution, all use a comma,
-<!## end>
-<!## XC>
-   in the <productname>Postgres-XC</productname> distribution, all use a comma,
-<!## end>
-<!## XL>
-   in the <productname>Postgres-XL</productname> distribution, all use a comma,
-<!## end>
-   except for type <type>box</>, which uses a semicolon (<literal>;</>).
-   In a multidimensional array, each dimension (row, plane,
-   cube, etc.) gets its own level of curly braces, and delimiters
-   must be written between adjacent curly-braced entities of the same level.
-  </para>
-
-  <para>
-   The array output routine will put double quotes around element values
-   if they are empty strings, contain curly braces, delimiter characters,
-   double quotes, backslashes, or white space, or match the word
-   <literal>NULL</>.  Double quotes and backslashes
-   embedded in element values will be backslash-escaped.  For numeric
-   data types it is safe to assume that double quotes will never appear, but
-   for textual data types one should be prepared to cope with either the presence
-   or absence of quotes.
-  </para>
-
-  <para>
-   By default, the lower bound index value of an array's dimensions is
-   set to one.  To represent arrays with other lower bounds, the array
-   subscript ranges can be specified explicitly before writing the
-   array contents.
-   This decoration consists of square brackets (<literal>[]</>)
-   around each array dimension's lower and upper bounds, with
-   a colon (<literal>:</>) delimiter character in between. The
-   array dimension decoration is followed by an equal sign (<literal>=</>).
-   For example:
-<programlisting>
-SELECT f1[1][-2][3] AS e1, f1[1][-1][5] AS e2
- FROM (SELECT '[1:1][-2:-1][3:5]={{{1,2,3},{4,5,6}}}'::int[] AS f1) AS ss;
-
- e1 | e2
-----+----
-  1 |  6
-(1 row)
-</programlisting>
-   The array output routine will include explicit dimensions in its result
-   only when there are one or more lower bounds different from one.
-  </para>
-
-  <para>
-   If the value written for an element is <literal>NULL</> (in any case
-   variant), the element is taken to be NULL.  The presence of any quotes
-   or backslashes disables this and allows the literal string value
-   <quote>NULL</> to be entered.  Also, for backward compatibility with
-   pre-8.2 versions of <productname>PostgreSQL</>, the <xref
-   linkend="guc-array-nulls"> configuration parameter can be turned
-   <literal>off</> to suppress recognition of <literal>NULL</> as a NULL.
-  </para>
-
-  <para>
-   As shown previously, when writing an array value you can use double
-   quotes around any individual array element. You <emphasis>must</> do so
-   if the element value would otherwise confuse the array-value parser.
-   For example, elements containing curly braces, commas (or the data type's
-   delimiter character), double quotes, backslashes, or leading or trailing
-   whitespace must be double-quoted.  Empty strings and strings matching the
-   word <literal>NULL</> must be quoted, too.  To put a double quote or
-   backslash in a quoted array element value, use escape string syntax
-   and precede it with a backslash. Alternatively, you can avoid quotes and use
-   backslash-escaping to protect all data characters that would otherwise
-   be taken as array syntax.
-  </para>
-
-  <para>
-   You can add whitespace before a left brace or after a right
-   brace. You can also add whitespace before or after any individual item
-   string. In all of these cases the whitespace will be ignored. However,
-   whitespace within double-quoted elements, or surrounded on both sides by
-   non-whitespace characters of an element, is not ignored.
-  </para>
-
- <note>
-  <para>
-   Remember that what you write in an SQL command will first be interpreted
-   as a string literal, and then as an array.  This doubles the number of
-   backslashes you need.  For example, to insert a <type>text</> array
-   value containing a backslash and a double quote, you'd need to write:
-<programlisting>
-INSERT ... VALUES (E'{"\\\\","\\""}');
-</programlisting>
-   The escape string processor removes one level of backslashes, so that
-   what arrives at the array-value parser looks like <literal>{"\\","\""}</>.
-   In turn, the strings fed to the <type>text</> data type's input routine
-   become <literal>\</> and <literal>"</> respectively.  (If we were working
-   with a data type whose input routine also treated backslashes specially,
-   <type>bytea</> for example, we might need as many as eight backslashes
-   in the command to get one backslash into the stored array element.)
-   Dollar quoting (see <xref linkend="sql-syntax-dollar-quoting">) can be
-   used to avoid the need to double backslashes.
-  </para>
- </note>
-
- <tip>
-  <para>
-   The <literal>ARRAY</> constructor syntax (see
-   <xref linkend="sql-syntax-array-constructors">) is often easier to work
-   with than the array-literal syntax when writing array values in SQL
-   commands. In <literal>ARRAY</>, individual element values are written the
-   same way they would be written when not members of an array.
-  </para>
- </tip>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/auth-delay.sgmlin b/doc-xc/src/sgml/auth-delay.sgmlin
deleted file mode 100644
index b91a7ecda7..0000000000
--- a/doc-xc/src/sgml/auth-delay.sgmlin
+++ /dev/null
@@ -1,67 +0,0 @@
-<!-- doc/src/sgml/auth-delay.sgml -->
-
-<sect1 id="auth-delay" xreflabel="auth_delay">
- <title>auth_delay</title>
-
- <indexterm zone="auth-delay">
-  <primary>auth_delay</primary>
- </indexterm>
-
- <para>
-  <filename>auth_delay</filename> causes the server to pause briefly before
-  reporting authentication failure, to make brute-force attacks on database
-  passwords more difficult.  Note that it does nothing to prevent
-  denial-of-service attacks, and may even exacerbate them, since processes
-  that are waiting before reporting authentication failure will still consume
-  connection slots.
- </para>
-
- <para>
-  In order to function, this module must be loaded via 
-  <xref linkend="guc-shared-preload-libraries"> in <filename>postgresql.conf</>.
- </para>
-
- <sect2>
-  <title>Configuration Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term>
-     <varname>auth_delay.milliseconds</varname> (<type>int</type>)
-    </term>
-    <indexterm>
-     <primary><varname>auth_delay.milliseconds</> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      The number of milliseconds to wait before reporting an authentication
-      failure.  The default is 0.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   In order to set these parameters in your <filename>postgresql.conf</> file,
-   you will need to add <literal>auth_delay</> to
-   <xref linkend="guc-custom-variable-classes">.  Typical usage might be:
-  </para>
-
-<programlisting>
-# postgresql.conf
-shared_preload_libraries = 'auth_delay'
-
-custom_variable_classes = 'auth_delay'
-auth_delay.milliseconds = '500'
-</programlisting>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   KaiGai Kohei <email>[email protected]</email>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/auto-explain.sgmlin b/doc-xc/src/sgml/auto-explain.sgmlin
deleted file mode 100644
index 0188053118..0000000000
--- a/doc-xc/src/sgml/auto-explain.sgmlin
+++ /dev/null
@@ -1,239 +0,0 @@
-<!-- doc/src/sgml/auto-explain.sgml -->
-
-<sect1 id="auto-explain" xreflabel="auto_explain">
- <title>auto_explain</title>
-
- <indexterm zone="auto-explain">
-  <primary>auto_explain</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>auto_explain</filename> module provides a means for
-  logging execution plans of slow statements automatically, without
-  having to run <xref linkend="sql-explain">
-  by hand.  This is especially helpful for tracking down un-optimized queries
-  in large applications.
- </para>
-
- <para>
-  The module provides no SQL-accessible functions.  To use it, simply
-  load it into the server.  You can load it into an individual session:
-
-<programlisting>
-LOAD 'auto_explain';
-</programlisting>
-
-  (You must be superuser to do that.)  More typical usage is to preload
-  it into all sessions by including <literal>auto_explain</> in
-  <xref linkend="guc-shared-preload-libraries"> in
-  <filename>postgresql.conf</>.  Then you can track unexpectedly slow queries
-  no matter when they happen.  Of course there is a price in overhead for
-  that.
- </para>
-
-<!## XC>
-&xconly;
- <para>
-  To log plans on Datanodes, you must preload this module in each
-  Datanode.  This module will log local plans of each node.  For
-  example, Coordinator log will include the plan for Coordinator only.
-  Corresponding plan in Datanodes will be found in each Datanode's
-  log.
- </para>
-<!## end>
-<!## XL>
- <para>
-  To log plans on Datanodes, you must preload this module in each
-  Datanode.  This module will log local plans of each node.  For
-  example, a Coordinator log will include the plan for Coordinator only.
-  the Corresponding plan in Datanodes will be found in each Datanode's
-  log.
- </para>
-<!## end>
-
-
- <sect2>
-  <title>Configuration Parameters</title>
-
-&common;
- <para>
-  There are several configuration parameters that control the behavior of
-  <filename>auto_explain</filename>.  Note that the default behavior is
-  to do nothing, so you must set at least
-  <varname>auto_explain.log_min_duration</varname> if you want any results.
- </para>
-
-  <variablelist>
-   <varlistentry>
-    <term>
-     <varname>auto_explain.log_min_duration</varname> (<type>integer</type>)
-    </term>
-    <indexterm>
-     <primary><varname>auto_explain.log_min_duration</> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      <varname>auto_explain.log_min_duration</varname> is the minimum statement
-      execution time, in milliseconds, that will cause the statement's plan to
-      be logged. Setting this to zero logs all plans. Minus-one (the default)
-      disables logging of plans.  For example, if you set it to
-      <literal>250ms</literal> then all statements that run 250ms or longer
-      will be logged. Only superusers can change this setting.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <varname>auto_explain.log_analyze</varname> (<type>boolean</type>)
-    </term>
-    <indexterm>
-     <primary><varname>auto_explain.log_analyze</> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      <varname>auto_explain.log_analyze</varname> causes <command>EXPLAIN ANALYZE</>
-      output, rather than just <command>EXPLAIN</> output, to be printed
-      when an execution plan is logged. This parameter is off by default.
-      Only superusers can change this setting.
-     </para>
-     <note>
-      <para>
-       When this parameter is on, per-plan-node timing occurs for all
-       statements executed, whether or not they run long enough to actually
-       get logged.  This can have extremely negative impact on performance.
-      </para>
-     </note>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <varname>auto_explain.log_verbose</varname> (<type>boolean</type>)
-    </term>
-    <indexterm>
-     <primary><varname>auto_explain.log_verbose</> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      <varname>auto_explain.log_verbose</varname> causes <command>EXPLAIN VERBOSE</>
-      output, rather than just <command>EXPLAIN</> output, to be printed
-      when an execution plan is logged. This parameter is off by default.
-      Only superusers can change this setting.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <varname>auto_explain.log_buffers</varname> (<type>boolean</type>)
-    </term>
-    <indexterm>
-     <primary><varname>auto_explain.log_buffers</> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      <varname>auto_explain.log_buffers</varname> causes <command>EXPLAIN
-      (ANALYZE, BUFFERS)</> output, rather than just <command>EXPLAIN</>
-      output, to be printed when an execution plan is logged. This parameter is
-      off by default. Only superusers can change this setting. This
-      parameter has no effect unless <varname>auto_explain.log_analyze</>
-      parameter is set.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <varname>auto_explain.log_format</varname> (<type>enum</type>)
-    </term>
-    <indexterm>
-     <primary><varname>auto_explain.log_format</> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      <varname>auto_explain.log_format</varname> selects the
-      <command>EXPLAIN</> output format to be used.
-      The allowed values are <literal>text</literal>, <literal>xml</literal>,
-      <literal>json</literal>, and <literal>yaml</literal>.  The default is text.
-      Only superusers can change this setting.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <varname>auto_explain.log_nested_statements</varname> (<type>boolean</type>)
-    </term>
-    <indexterm>
-     <primary><varname>auto_explain.log_nested_statements</> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      <varname>auto_explain.log_nested_statements</varname> causes nested
-      statements (statements executed inside a function) to be considered
-      for logging.  When it is off, only top-level query plans are logged. This
-      parameter is off by default. Only superusers can change this setting.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   In order to set these parameters in your <filename>postgresql.conf</> file,
-   you will need to add <literal>auto_explain</> to
-   <xref linkend="guc-custom-variable-classes">.  Typical usage might be:
-  </para>
-
-<programlisting>
-# postgresql.conf
-shared_preload_libraries = 'auto_explain'
-
-custom_variable_classes = 'auto_explain'
-auto_explain.log_min_duration = '3s'
-</programlisting>
- </sect2>
-
- <sect2>
-  <title>Example</title>
-
-<programlisting>
-postgres=# LOAD 'auto_explain';
-postgres=# SET auto_explain.log_min_duration = 0;
-postgres=# SELECT count(*)
-           FROM pg_class, pg_index
-           WHERE oid = indrelid AND indisunique;
-</programlisting>
-
-&common;
-  <para>
-   This might produce log output such as:
-  </para>
-
-<screen><![CDATA[
-LOG:  duration: 3.651 ms  plan:
-  Query Text: SELECT count(*)
-              FROM pg_class, pg_index
-              WHERE oid = indrelid AND indisunique;
-  Aggregate  (cost=16.79..16.80 rows=1 width=0) (actual time=3.626..3.627 rows=1 loops=1)
-    ->  Hash Join  (cost=4.17..16.55 rows=92 width=0) (actual time=3.349..3.594 rows=92 loops=1)
-          Hash Cond: (pg_class.oid = pg_index.indrelid)
-          ->  Seq Scan on pg_class  (cost=0.00..9.55 rows=255 width=4) (actual time=0.016..0.140 rows=255 loops=1)
-          ->  Hash  (cost=3.02..3.02 rows=92 width=4) (actual time=3.238..3.238 rows=92 loops=1)
-                Buckets: 1024  Batches: 1  Memory Usage: 4kB
-                ->  Seq Scan on pg_index  (cost=0.00..3.02 rows=92 width=4) (actual time=0.008..3.187 rows=92 loops=1)
-                      Filter: indisunique
-]]></screen>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Takahiro Itagaki <email>[email protected]</email>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/backup.sgmlin b/doc-xc/src/sgml/backup.sgmlin
deleted file mode 100644
index 30950986ee..0000000000
--- a/doc-xc/src/sgml/backup.sgmlin
+++ /dev/null
@@ -1,1487 +0,0 @@
-<!-- doc/src/sgml/backup.sgml -->
-
-<chapter id="backup">
- <title>Backup and Restore</title>
-
- <indexterm zone="backup"><primary>backup</></>
-
-&common;
- <para>
-  As with everything that contains valuable data, <productname>PostgreSQL</>
-  databases should be backed up regularly. While the procedure is
-  essentially simple, it is important to have a clear understanding of
-  the underlying techniques and assumptions.
- </para>
-
- <para>
-  There are three fundamentally different approaches to backing up
-  <productname>PostgreSQL</> data:
-  <itemizedlist>
-   <listitem><para><acronym>SQL</> dump</para></listitem>
-   <listitem><para>File system level backup</para></listitem>
-   <listitem><para>Continuous archiving</para></listitem>
-  </itemizedlist>
-  Each has its own strengths and weaknesses; each is discussed in turn
-  in the following sections.
- </para>
-
- <sect1 id="backup-dump">
-  <title><acronym>SQL</> Dump</title>
-
-&common;
-  <para>
-   The idea behind this dump method is to generate a text file with SQL
-   commands that, when fed back to the server, will recreate the
-   database in the same state as it was at the time of the dump.
-   <productname>PostgreSQL</> provides the utility program
-   <xref linkend="app-pgdump"> for this purpose. The basic usage of this
-   command is:
-<synopsis>
-pg_dump <replaceable class="parameter">dbname</replaceable> &gt; <replaceable class="parameter">outfile</replaceable>
-</synopsis>
-   As you see, <application>pg_dump</> writes its result to the
-   standard output. We will see below how this can be useful.
-  </para>
-
-  <para>
-   <application>pg_dump</> is a regular <productname>PostgreSQL</>
-   client application (albeit a particularly clever one). This means
-   that you can perform this backup procedure from any remote host that has
-   access to the database. But remember that <application>pg_dump</>
-   does not operate with special permissions. In particular, it must
-   have read access to all tables that you want to back up, so in
-   practice you almost always have to run it as a database superuser.
-  </para>
-
-  <para>
-   To specify which database server <application>pg_dump</> should
-   contact, use the command line options <option>-h
-   <replaceable>host</></> and <option>-p <replaceable>port</></>. The
-   default host is the local host or whatever your
-   <envar>PGHOST</envar> environment variable specifies. Similarly,
-   the default port is indicated by the <envar>PGPORT</envar>
-   environment variable or, failing that, by the compiled-in default.
-   (Conveniently, the server will normally have the same compiled-in
-   default.)
-  </para>
-
-  <para>
-   Like any other <productname>PostgreSQL</> client application,
-   <application>pg_dump</> will by default connect with the database
-   user name that is equal to the current operating system user name. To override
-   this, either specify the <option>-U</option> option or set the
-   environment variable <envar>PGUSER</envar>. Remember that
-   <application>pg_dump</> connections are subject to the normal
-   client authentication mechanisms (which are described in <xref
-   linkend="client-authentication">).
-  </para>
-
-  <para>
-   An important advantage of <application>pg_dump</> over the other backup
-   methods described later is that <application>pg_dump</>'s output can
-   generally be re-loaded into newer versions of <productname>PostgreSQL</>,
-   whereas file-level backups and continuous archiving are both extremely
-   server-version-specific.  <application>pg_dump</> is also the only method
-   that will work when transferring a database to a different machine
-   architecture, such as going from a 32-bit to a 64-bit server.
-  </para>
-
-  <para>
-   Dumps created by <application>pg_dump</> are internally consistent,
-   meaning, the dump represents a snapshot of the database at the time
-   <application>pg_dump</> began running. <application>pg_dump</> does not
-   block other operations on the database while it is working.
-   (Exceptions are those operations that need to operate with an
-   exclusive lock, such as most forms of <command>ALTER TABLE</command>.)
-  </para>
-
-  <important>
-   <para>
-    If your database schema relies on OIDs (for instance, as foreign
-    keys) you must instruct <application>pg_dump</> to dump the OIDs
-    as well. To do this, use the <option>-o</option> command-line
-    option.
-   </para>
-  </important>
-
-<!## XC>
-&xconly;
-  <important>
-   <para>
-    In <productname>Postgres-XC</>, <application>pg_dump</>
-    and <application>pg_dumpall</> backs up all the information stored
-    both in Coordinators and Datanodes.
-   </para>
-  </important>
-<!## end>
-<!## XL>
-&xlonly;
-  <important>
-   <para>
-    In <productname>Postgres-XL</>, <application>pg_dump</>
-    and <application>pg_dumpall</> backs up all the information stored
-    both in Coordinators and Datanodes.
-    That is, it dumps the entire database just like in regular PostgreSQL
-    and outputs similarly.  The output will contain additional table
-    distribution information.
-   </para>
-  </important>
-<!## end>
-
-
-  <sect2 id="backup-dump-restore">
-   <title>Restoring the Dump</title>
-
-&common;
-   <para>
-    The text files created by <application>pg_dump</> are intended to
-    be read in by the <application>psql</application> program. The
-    general command form to restore a dump is
-<synopsis>
-psql <replaceable class="parameter">dbname</replaceable> &lt; <replaceable class="parameter">infile</replaceable>
-</synopsis>
-    where <replaceable class="parameter">infile</replaceable> is the
-    file output by the <application>pg_dump</> command. The database <replaceable
-    class="parameter">dbname</replaceable> will not be created by this
-    command, so you must create it yourself from <literal>template0</>
-    before executing <application>psql</> (e.g., with
-    <literal>createdb -T template0 <replaceable
-    class="parameter">dbname</></literal>).  <application>psql</>
-    supports options similar to <application>pg_dump</> for specifying
-    the database server to connect to and the user name to use. See
-    the <xref linkend="app-psql"> reference page for more information.
-   </para>
-
-   <para>
-    Before restoring an SQL dump, all the users who own objects or were
-    granted permissions on objects in the dumped database must already
-    exist. If they do not, the restore will fail to recreate the
-    objects with the original ownership and/or permissions.
-    (Sometimes this is what you want, but usually it is not.)
-   </para>
-
-   <para>
-    By default, the <application>psql</> script will continue to
-    execute after an SQL error is encountered. You might wish to run
-    <application>psql</application> with
-    the <literal>ON_ERROR_STOP</> variable set to alter that
-    behavior and have <application>psql</application> exit with an
-    exit status of 3 if an SQL error occurs:
-<programlisting>
-psql --set ON_ERROR_STOP=on dbname &lt; infile
-</programlisting>
-    Either way, you will only have a partially restored database.
-    Alternatively, you can specify that the whole dump should be
-    restored as a single transaction, so the restore is either fully
-    completed or fully rolled back. This mode can be specified by
-    passing the <option>-1</> or <option>--single-transaction</>
-    command-line options to <application>psql</>. When using this
-    mode, be aware that even a minor error can rollback a
-    restore that has already run for many hours. However, that might
-    still be preferable to manually cleaning up a complex database
-    after a partially restored dump.
-   </para>
-
-   <para>
-    The ability of <application>pg_dump</> and <application>psql</> to
-    write to or read from pipes makes it possible to dump a database
-    directly from one server to another, for example:
-<programlisting>
-pg_dump -h <replaceable>host1</> <replaceable>dbname</> | psql -h <replaceable>host2</> <replaceable>dbname</>
-</programlisting>
-   </para>
-
-   <important>
-    <para>
-     The dumps produced by <application>pg_dump</> are relative to
-     <literal>template0</>. This means that any languages, procedures,
-     etc. added via <literal>template1</> will also be dumped by
-     <application>pg_dump</>. As a result, when restoring, if you are
-     using a customized <literal>template1</>, you must create the
-     empty database from <literal>template0</>, as in the example
-     above.
-    </para>
-   </important>
-
-   <para>
-    After restoring a backup, it is wise to run <xref
-    linkend="sql-analyze"> on each
-    database so the query optimizer has useful statistics;
-    see <xref linkend="vacuum-for-statistics">
-    and <xref linkend="autovacuum"> for more information.
-    For more advice on how to load large amounts of data
-    into <productname>PostgreSQL</> efficiently, refer to <xref
-    linkend="populate">.
-   </para>
-  </sect2>
-
-  <sect2 id="backup-dump-all">
-   <title>Using <application>pg_dumpall</></title>
-
-&common;
-   <para>
-    <application>pg_dump</> dumps only a single database at a time,
-    and it does not dump information about roles or tablespaces
-    (because those are cluster-wide rather than per-database).
-    To support convenient dumping of the entire contents of a database
-    cluster, the <xref linkend="app-pg-dumpall"> program is provided.
-    <application>pg_dumpall</> backs up each database in a given
-    cluster, and also preserves cluster-wide data such as role and
-    tablespace definitions. The basic usage of this command is:
-<synopsis>
-pg_dumpall &gt; <replaceable>outfile</>
-</synopsis>
-    The resulting dump can be restored with <application>psql</>:
-<synopsis>
-psql -f <replaceable class="parameter">infile</replaceable> postgres
-</synopsis>
-    (Actually, you can specify any existing database name to start from,
-    but if you are loading into an empty cluster then <literal>postgres</>
-    should usually be used.)  It is always necessary to have
-    database superuser access when restoring a <application>pg_dumpall</>
-    dump, as that is required to restore the role and tablespace information.
-    If you use tablespaces, make sure that the tablespace paths in the
-    dump are appropriate for the new installation.
-   </para>
-
-   <para>
-    <application>pg_dumpall</> works by emitting commands to re-create
-    roles, tablespaces, and empty databases, then invoking
-    <application>pg_dump</> for each database.  This means that while
-    each database will be internally consistent, the snapshots of
-    different databases might not be exactly in-sync.
-   </para>
-  </sect2>
-
-  <sect2 id="backup-dump-large">
-   <title>Handling Large Databases</title>
-
-&common;
-   <para>
-    Some operating systems have maximum file size limits that cause
-    problems when creating large <application>pg_dump</> output files.
-    Fortunately, <application>pg_dump</> can write to the standard
-    output, so you can use standard Unix tools to work around this
-    potential problem.  There are several possible methods:
-   </para>
-
-   <formalpara>
-    <title>Use compressed dumps.</title>
-    <para>
-     You can use your favorite compression program, for example
-     <application>gzip</application>:
-
-<programlisting>
-pg_dump <replaceable class="parameter">dbname</replaceable> | gzip &gt; <replaceable class="parameter">filename</replaceable>.gz
-</programlisting>
-
-     Reload with:
-
-<programlisting>
-gunzip -c <replaceable class="parameter">filename</replaceable>.gz | psql <replaceable class="parameter">dbname</replaceable>
-</programlisting>
-
-     or:
-
-<programlisting>
-cat <replaceable class="parameter">filename</replaceable>.gz | gunzip | psql <replaceable class="parameter">dbname</replaceable>
-</programlisting>
-    </para>
-   </formalpara>
-
-   <formalpara>
-    <title>Use <command>split</>.</title>
-    <para>
-     The <command>split</command> command
-     allows you to split the output into smaller files that are
-     acceptable in size to the underlying file system. For example, to
-     make chunks of 1 megabyte:
-
-<programlisting>
-pg_dump <replaceable class="parameter">dbname</replaceable> | split -b 1m - <replaceable class="parameter">filename</replaceable>
-</programlisting>
-
-     Reload with:
-
-<programlisting>
-cat <replaceable class="parameter">filename</replaceable>* | psql <replaceable class="parameter">dbname</replaceable>
-</programlisting>
-    </para>
-   </formalpara>
-
-   <formalpara>
-    <title>Use <application>pg_dump</>'s custom dump format.</title>
-    <para>
-     If <productname>PostgreSQL</productname> was built on a system with the
-     <application>zlib</> compression library installed, the custom dump
-     format will compress data as it writes it to the output file. This will
-     produce dump file sizes similar to using <command>gzip</command>, but it
-     has the added advantage that tables can be restored selectively. The
-     following command dumps a database using the custom dump format:
-
-<programlisting>
-pg_dump -Fc <replaceable class="parameter">dbname</replaceable> &gt; <replaceable class="parameter">filename</replaceable>
-</programlisting>
-
-     A custom-format dump is not a script for <application>psql</>, but
-     instead must be restored with <application>pg_restore</>, for example:
-
-<programlisting>
-pg_restore -d <replaceable class="parameter">dbname</replaceable> <replaceable class="parameter">filename</replaceable>
-</programlisting>
-
-     See the <xref linkend="app-pgdump"> and <xref
-     linkend="app-pgrestore"> reference pages for details.
-    </para>
-   </formalpara>
-
-   <para>
-    For very large databases, you might need to combine <command>split</>
-    with one of the other two approaches.
-   </para>
-
-  </sect2>
- </sect1>
-
- <sect1 id="backup-file">
-  <title>File System Level Backup</title>
-
-<!## XC>
-&xconly;
-  <para>
-   File system level backup covers only each Coordinator or Datanode.
-   To make file system level backup, you should backup each
-   Coordinator and Datanode manually.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   File system level backup covers only each Coordinator or Datanode.
-   To make file system level backup, you should backup each
-   Coordinator and Datanode manually.
-  </para>
-<!## end>
-
-&common;
-  <para>
-   An alternative backup strategy is to directly copy the files that
-   <productname>PostgreSQL</> uses to store the data in the database;
-   <xref linkend="creating-cluster"> explains where these files
-   are located.  You can use whatever method you prefer
-   for doing file system backups; for example:
-
-<programlisting>
-tar -cf backup.tar /usr/local/pgsql/data
-</programlisting>
-  </para>
-
-  <para>
-   There are two restrictions, however, which make this method
-   impractical, or at least inferior to the <application>pg_dump</>
-   method:
-
-   <orderedlist>
-    <listitem>
-     <para>
-      The database server <emphasis>must</> be shut down in order to
-      get a usable backup. Half-way measures such as disallowing all
-      connections will <emphasis>not</emphasis> work
-      (in part because <command>tar</command> and similar tools do not take
-      an atomic snapshot of the state of the file system,
-      but also because of internal buffering within the server).
-      Information about stopping the server can be found in
-      <xref linkend="server-shutdown">.  Needless to say, you
-      also need to shut down the server before restoring the data.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      If you have dug into the details of the file system layout of the
-      database, you might be tempted to try to back up or restore only certain
-      individual tables or databases from their respective files or
-      directories. This will <emphasis>not</> work because the
-      information contained in these files is not usable without
-      the commit log files,
-      <filename>pg_clog/*</filename>, which contain the commit status of
-      all transactions. A table file is only usable with this
-      information. Of course it is also impossible to restore only a
-      table and the associated <filename>pg_clog</filename> data
-      because that would render all other tables in the database
-      cluster useless.  So file system backups only work for complete
-      backup and restoration of an entire database cluster.
-     </para>
-    </listitem>
-   </orderedlist>
-  </para>
-
-  <para>
-   An alternative file-system backup approach is to make a
-   <quote>consistent snapshot</quote> of the data directory, if the
-   file system supports that functionality (and you are willing to
-   trust that it is implemented correctly).  The typical procedure is
-   to make a <quote>frozen snapshot</> of the volume containing the
-   database, then copy the whole data directory (not just parts, see
-   above) from the snapshot to a backup device, then release the frozen
-   snapshot.  This will work even while the database server is running.
-   However, a backup created in this way saves
-   the database files in a state as if the database server was not
-   properly shut down; therefore, when you start the database server
-   on the backed-up data, it will think the previous server instance
-   crashed and will replay the WAL log.  This is not a problem; just
-   be aware of it (and be sure to include the WAL files in your backup).
-   You can perform a <command>CHECKPOINT</command> before taking the
-   snapshot to reduce recovery time.
-  </para>
-
-  <para>
-   If your database is spread across multiple file systems, there might not
-   be any way to obtain exactly-simultaneous frozen snapshots of all
-   the volumes.  For example, if your data files and WAL log are on different
-   disks, or if tablespaces are on different file systems, it might
-   not be possible to use snapshot backup because the snapshots
-   <emphasis>must</> be simultaneous.
-   Read your file system documentation very carefully before trusting
-   the consistent-snapshot technique in such situations.
-  </para>
-
-  <para>
-   If simultaneous snapshots are not possible, one option is to shut down
-   the database server long enough to establish all the frozen snapshots.
-   Another option is to perform a continuous archiving base backup (<xref
-   linkend="backup-base-backup">) because such backups are immune to file
-   system changes during the backup.  This requires enabling continuous
-   archiving just during the backup process; restore is done using
-   continuous archive recovery (<xref linkend="backup-pitr-recovery">).
-  </para>
-
-  <para>
-   Another option is to use <application>rsync</> to perform a file
-   system backup.  This is done by first running <application>rsync</>
-   while the database server is running, then shutting down the database
-   server just long enough to do a second <application>rsync</>.  The
-   second <application>rsync</> will be much quicker than the first,
-   because it has relatively little data to transfer, and the end result
-   will be consistent because the server was down.  This method
-   allows a file system backup to be performed with minimal downtime.
-  </para>
-
-  <para>
-   Note that a file system backup will typically be larger
-   than an SQL dump. (<application>pg_dump</application> does not need to dump
-   the contents of indexes for example, just the commands to recreate
-   them.)  However, taking a file system backup might be faster.
-  </para>
- </sect1>
-
- <sect1 id="continuous-archiving">
-  <title>Continuous Archiving and Point-in-Time Recovery (PITR)</title>
-
-  <indexterm zone="backup">
-   <primary>continuous archiving</primary>
-  </indexterm>
-
-  <indexterm zone="backup">
-   <primary>point-in-time recovery</primary>
-  </indexterm>
-
-  <indexterm zone="backup">
-   <primary>PITR</primary>
-  </indexterm>
-
-<!## XC> 
-&xconly;
-  <para>
-   This section describes PITR for <productname>PostgreSQL</>.
-   Because Coordinator and Datanode of <productname>Postgres-XC</> are
-   essentially <productname>PostgreSQL</productname>server, you can do
-   PITR for each Coordinator and Datanode manually.
-  </para>
-<!## end>
-
-  <para>
-   At all times, <productname>PostgreSQL</> maintains a
-   <firstterm>write ahead log</> (WAL) in the <filename>pg_xlog/</>
-   subdirectory of the cluster's data directory. The log records
-   every change made to the database's data files.  This log exists
-   primarily for crash-safety purposes: if the system crashes, the
-   database can be restored to consistency by <quote>replaying</> the
-   log entries made since the last checkpoint.  However, the existence
-   of the log makes it possible to use a third strategy for backing up
-   databases: we can combine a file-system-level backup with backup of
-   the WAL files.  If recovery is needed, we restore the file system backup and
-   then replay from the backed-up WAL files to bring the system to a
-   current state.  This approach is more complex to administer than
-   either of the previous approaches, but it has some significant
-   benefits:
-  <itemizedlist>
-   <listitem>
-    <para>
-     We do not need a perfectly consistent file system backup as the starting point.
-     Any internal inconsistency in the backup will be corrected by log
-     replay (this is not significantly different from what happens during
-     crash recovery).  So we do not need a file system snapshot capability,
-     just <application>tar</> or a similar archiving tool.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Since we can combine an indefinitely long sequence of WAL files
-     for replay, continuous backup can be achieved simply by continuing to archive
-     the WAL files.  This is particularly valuable for large databases, where
-     it might not be convenient to take a full backup frequently.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     It is not necessary to replay the WAL entries all the
-     way to the end.  We could stop the replay at any point and have a
-     consistent snapshot of the database as it was at that time.  Thus,
-     this technique supports <firstterm>point-in-time recovery</>: it is
-     possible to restore the database to its state at any time since your base
-     backup was taken.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     If we continuously feed the series of WAL files to another
-     machine that has been loaded with the same base backup file, we
-     have a <firstterm>warm standby</> system: at any point we can bring up
-     the second machine and it will have a nearly-current copy of the
-     database.
-    </para>
-   </listitem>
-  </itemizedlist>
-  </para>
-
-  <note>
-   <para>
-    <application>pg_dump</application> and
-    <application>pg_dumpall</application> do not produce file-system-level
-    backups and cannot be used as part of a continuous-archiving solution.
-    Such dumps are <emphasis>logical</> and do not contain enough
-    information to be used by WAL replay.
-   </para>
-  </note>
-
-  <para>
-   As with the plain file-system-backup technique, this method can only
-   support restoration of an entire database cluster, not a subset.
-   Also, it requires a lot of archival storage: the base backup might be bulky,
-   and a busy system will generate many megabytes of WAL traffic that
-   have to be archived.  Still, it is the preferred backup technique in
-   many situations where high reliability is needed.
-  </para>
-
-  <para>
-   To recover successfully using continuous archiving (also called
-   <quote>online backup</> by many database vendors), you need a continuous
-   sequence of archived WAL files that extends back at least as far as the
-   start time of your backup.  So to get started, you should set up and test
-   your procedure for archiving WAL files <emphasis>before</> you take your
-   first base backup.  Accordingly, we first discuss the mechanics of
-   archiving WAL files.
-  </para>
-
-  <sect2 id="backup-archiving-wal">
-   <title>Setting Up WAL Archiving</title>
-
-<!## XC> 
-&xconly;
-  <para>
-   This section describes PITR for <productname>PostgreSQL</>.
-   Because Coordinator and Datanode of <productname>Postgres-XC</> are
-   essentially <productname>PostgreSQL</productname>server, you can
-   set up WAL archiving for each Coordinator and Datanode manually.
-  </para>
-<!## end>
-
-   <para>
-    In an abstract sense, a running <productname>PostgreSQL</> system
-    produces an indefinitely long sequence of WAL records.  The system
-    physically divides this sequence into WAL <firstterm>segment
-    files</>, which are normally 16MB apiece (although the segment size
-    can be altered when building <productname>PostgreSQL</>).  The segment
-    files are given numeric names that reflect their position in the
-    abstract WAL sequence.  When not using WAL archiving, the system
-    normally creates just a few segment files and then
-    <quote>recycles</> them by renaming no-longer-needed segment files
-    to higher segment numbers.  It's assumed that segment files whose
-    contents precede the checkpoint-before-last are no longer of
-    interest and can be recycled.
-   </para>
-
-   <para>
-    When archiving WAL data, we need to capture the contents of each segment
-    file once it is filled, and save that data somewhere before the segment
-    file is recycled for reuse.  Depending on the application and the
-    available hardware, there could be many different ways of <quote>saving
-    the data somewhere</>: we could copy the segment files to an NFS-mounted
-    directory on another machine, write them onto a tape drive (ensuring that
-    you have a way of identifying the original name of each file), or batch
-    them together and burn them onto CDs, or something else entirely.  To
-    provide the database administrator with flexibility,
-    <productname>PostgreSQL</> tries not to make any assumptions about how
-    the archiving will be done.  Instead, <productname>PostgreSQL</> lets
-    the administrator specify a shell command to be executed to copy a
-    completed segment file to wherever it needs to go.  The command could be
-    as simple as a <literal>cp</>, or it could invoke a complex shell
-    script &mdash; it's all up to you.
-   </para>
-
-   <para>
-    To enable WAL archiving, set the <xref linkend="guc-wal-level">
-    configuration parameter to <literal>archive</> (or <literal>hot_standby</>),
-    <xref linkend="guc-archive-mode"> to <literal>on</>,
-    and specify the shell command to use in the <xref
-    linkend="guc-archive-command"> configuration parameter.  In practice
-    these settings will always be placed in the
-    <filename>postgresql.conf</filename> file.
-    In <varname>archive_command</>,
-    <literal>%p</> is replaced by the path name of the file to
-    archive, while <literal>%f</> is replaced by only the file name.
-    (The path name is relative to the current working directory,
-    i.e., the cluster's data directory.)
-    Use <literal>%%</> if you need to embed an actual <literal>%</>
-    characterin the command.  The simplest useful command is something
-    like:
-<programlisting>
-archive_command = 'cp -i %p /mnt/server/archivedir/%f &lt;/dev/null'  # Unix
-archive_command = 'copy "%p" "C:\\server\\archivedir\\%f"'  # Windows
-</programlisting>
-    which will copy archivable WAL segments to the directory
-    <filename>/mnt/server/archivedir</>.  (This is an example, not a
-    recommendation, and might not work on all platforms.)  After the
-    <literal>%p</> and <literal>%f</> parameters have been replaced,
-    the actual command executed might look like this:
-<programlisting>
-cp -i pg_xlog/00000001000000A900000065 /mnt/server/archivedir/00000001000000A900000065 &lt;/dev/null
-</programlisting>
-    A similar command will be generated for each new file to be archived.
-   </para>
-
-   <para>
-    The archive command will be executed under the ownership of the same
-    user that the <productname>PostgreSQL</> server is running as.  Since
-    the series of WAL files being archived contains effectively everything
-    in your database, you will want to be sure that the archived data is
-    protected from prying eyes; for example, archive into a directory that
-    does not have group or world read access.
-   </para>
-
-   <para>
-    It is important that the archive command return zero exit status if and
-    only if it succeeds.  Upon getting a zero result,
-    <productname>PostgreSQL</> will assume that the file has been
-    successfully archived, and will remove or recycle it.  However, a nonzero
-    status tells <productname>PostgreSQL</> that the file was not archived;
-    it will try again periodically until it succeeds.
-   </para>
-
-   <para>
-    The archive command should generally be designed to refuse to overwrite
-    any pre-existing archive file.  This is an important safety feature to
-    preserve the integrity of your archive in case of administrator error
-    (such as sending the output of two different servers to the same archive
-    directory).
-    It is advisable to test your proposed archive command to ensure that it
-    indeed does not overwrite an existing file, <emphasis>and that it returns
-    nonzero status in this case</>.  On many Unix platforms, <command>cp
-    -i</> causes copy to prompt before overwriting a file, and
-    <literal>&lt; /dev/null</> causes the prompt (and overwriting) to
-    fail.  If your platform does not support this behavior, you should
-    add a command to test for the existence of the archive file.  For
-    example, something like:
-<programlisting>
-archive_command = 'test ! -f /mnt/server/archivedir/%f &amp;&amp; cp %p /mnt/server/archivedir/%f'
-</programlisting>
-    works correctly on most Unix variants.
-   </para>
-
-   <para>
-    While designing your archiving setup, consider what will happen if
-    the archive command fails repeatedly because some aspect requires
-    operator intervention or the archive runs out of space. For example, this
-    could occur if you write to tape without an autochanger; when the tape
-    fills, nothing further can be archived until the tape is swapped.
-    You should ensure that any error condition or request to a human operator
-    is reported appropriately so that the situation can be
-    resolved reasonably quickly. The <filename>pg_xlog/</> directory will
-    continue to fill with WAL segment files until the situation is resolved.
-    (If the file system containing <filename>pg_xlog/</> fills up,
-    <productname>PostgreSQL</> will do a PANIC shutdown.  No committed
-    transactions will be lost, but the database will remain offline until
-    you free some space.)
-   </para>
-
-   <para>
-    The speed of the archiving command is unimportant as long as it can keep up
-    with the average rate at which your server generates WAL data.  Normal
-    operation continues even if the archiving process falls a little behind.
-    If archiving falls significantly behind, this will increase the amount of
-    data that would be lost in the event of a disaster. It will also mean that
-    the <filename>pg_xlog/</> directory will contain large numbers of
-    not-yet-archived segment files, which could eventually exceed available
-    disk space. You are advised to monitor the archiving process to ensure that
-    it is working as you intend.
-   </para>
-
-   <para>
-    In writing your archive command, you should assume that the file names to
-    be archived can be up to 64 characters long and can contain any
-    combination of ASCII letters, digits, and dots.  It is not necessary to
-    preserve the original relative path (<literal>%p</>) but it is necessary to
-    preserve the file name (<literal>%f</>).
-   </para>
-
-   <para>
-    Note that although WAL archiving will allow you to restore any
-    modifications made to the data in your <productname>PostgreSQL</> database,
-    it will not restore changes made to configuration files (that is,
-    <filename>postgresql.conf</>, <filename>pg_hba.conf</> and
-    <filename>pg_ident.conf</>), since those are edited manually rather
-    than through SQL operations.
-    You might wish to keep the configuration files in a location that will
-    be backed up by your regular file system backup procedures.  See
-    <xref linkend="runtime-config-file-locations"> for how to relocate the
-    configuration files.
-   </para>
-
-   <para>
-    The archive command is only invoked on completed WAL segments.  Hence,
-    if your server generates only little WAL traffic (or has slack periods
-    where it does so), there could be a long delay between the completion
-    of a transaction and its safe recording in archive storage.  To put
-    a limit on how old unarchived data can be, you can set
-    <xref linkend="guc-archive-timeout"> to force the server to switch
-    to a new WAL segment file at least that often.  Note that archived
-    files that are archived early due to a forced switch are still the same
-    length as completely full files.  It is therefore unwise to set a very
-    short <varname>archive_timeout</> &mdash; it will bloat your archive
-    storage.  <varname>archive_timeout</> settings of a minute or so are
-    usually reasonable.
-   </para>
-
-   <para>
-    Also, you can force a segment switch manually with
-    <function>pg_switch_xlog</> if you want to ensure that a
-    just-finished transaction is archived as soon as possible.  Other utility
-    functions related to WAL management are listed in <xref
-    linkend="functions-admin-backup-table">.
-   </para>
-
-   <para>
-    When <varname>wal_level</> is <literal>minimal</> some SQL commands
-    are optimized to avoid WAL logging, as described in <xref
-    linkend="populate-pitr">.  If archiving or streaming replication were
-    turned on during execution of one of these statements, WAL would not
-    contain enough information for archive recovery.  (Crash recovery is
-    unaffected.)  For this reason, <varname>wal_level</> can only be changed at
-    server start.  However, <varname>archive_command</> can be changed with a
-    configuration file reload.  If you wish to temporarily stop archiving,
-    one way to do it is to set <varname>archive_command</> to the empty
-    string (<literal>''</>).
-    This will cause WAL files to accumulate in <filename>pg_xlog/</> until a
-    working <varname>archive_command</> is re-established.
-   </para>
-  </sect2>
-
-  <sect2 id="backup-base-backup">
-   <title>Making a Base Backup</title>
-
-<!## XC> 
-&xconly;
-   <para>
-    This section describes how to make a base backup of single
-    Datanode or Coordinator.  Please note that you should take base
-    backup of all the Datanodes and Coordinators.  Also please note
-    that you don't have to take base backups at exactly the same time.
-    You may take base backup of each Datanode or Coordinator one after
-    another, or you may take some of them at the same time.  You don't
-    have to do it at exactly the same time.
-   </para>
-<!## end>
-
-   <para>
-    The procedure for making a base backup is relatively simple:
-  <orderedlist>
-   <listitem>
-    <para>
-     Ensure that WAL archiving is enabled and working.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Connect to the database as a superuser and issue the command:
-<programlisting>
-SELECT pg_start_backup('label');
-</programlisting>
-     where <literal>label</> is any string you want to use to uniquely
-     identify this backup operation.  (One good practice is to use the
-     full path where you intend to put the backup dump file.)
-     <function>pg_start_backup</> creates a <firstterm>backup label</> file,
-     called <filename>backup_label</>, in the cluster directory with
-     information about your backup, including the start time and label
-     string.
-    </para>
-
-    <para>
-     It does not matter which database within the cluster you connect to to
-     issue this command.  You can ignore the result returned by the function;
-     but if it reports an error, deal with that before proceeding.
-    </para>
-
-    <para>
-     By default, <function>pg_start_backup</> can take a long time to finish.
-     This is because it performs a checkpoint, and the I/O
-     required for the checkpoint will be spread out over a significant
-     period of time, by default half your inter-checkpoint interval
-     (see the configuration parameter
-     <xref linkend="guc-checkpoint-completion-target">).  This is
-     usually what you want, because it minimizes the impact on query
-     processing.  If you want to start the backup as soon as
-     possible, use:
-<programlisting>
-SELECT pg_start_backup('label', true);
-</programlisting>
-     This forces the checkpoint to be done as quickly as possible.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Perform the backup, using any convenient file-system-backup tool
-     such as <application>tar</> or <application>cpio</> (not
-     <application>pg_dump</application> or
-     <application>pg_dumpall</application>).  It is neither
-     necessary nor desirable to stop normal operation of the database
-     while you do this.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Again connect to the database as a superuser, and issue the command:
-<programlisting>
-SELECT pg_stop_backup();
-</programlisting>
-     This terminates the backup mode and performs an automatic switch to
-     the next WAL segment.  The reason for the switch is to arrange for
-     the last WAL segment file written during the backup interval to be
-     ready to archive.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Once the WAL segment files active during the backup are archived, you are
-     done.  The file identified by <function>pg_stop_backup</>'s result is
-     the last segment that is required to form a complete set of backup files.
-     If <varname>archive_mode</> is enabled,
-     <function>pg_stop_backup</> does not return until the last segment has
-     been archived.
-     Archiving of these files happens automatically since you have
-     already configured <varname>archive_command</>. In most cases this
-     happens quickly, but you are advised to monitor your archive
-     system to ensure there are no delays.
-     If the archive process has fallen behind
-     because of failures of the archive command, it will keep retrying
-     until the archive succeeds and the backup is complete.
-     If you wish to place a time limit on the execution of
-     <function>pg_stop_backup</>, set an appropriate
-     <varname>statement_timeout</varname> value.
-    </para>
-   </listitem>
-  </orderedlist>
-   </para>
-
-   <para>
-    You can also use the <xref linkend="app-pgbasebackup"> tool to take
-    the backup, instead of manually copying the files. This tool will do
-    the equivalent of <function>pg_start_backup()</>, copy and
-    <function>pg_stop_backup()</> steps automatically, and transfers the
-    backup over a regular <productname>PostgreSQL</productname> connection
-    using the replication protocol, instead of requiring file system level
-    access. <command>pg_basebackup</command> does not interfere with file system level backups
-    taken using <function>pg_start_backup()</>/<function>pg_stop_backup()</>.
-   </para>
-
-   <para>
-    Some file system backup tools emit warnings or errors
-    if the files they are trying to copy change while the copy proceeds.
-    When taking a base backup of an active database, this situation is normal
-    and not an error.  However, you need to ensure that you can distinguish
-    complaints of this sort from real errors.  For example, some versions
-    of <application>rsync</> return a separate exit code for
-    <quote>vanished source files</>, and you can write a driver script to
-    accept this exit code as a non-error case.  Also, some versions of
-    GNU <application>tar</> return an error code indistinguishable from
-    a fatal error if a file was truncated while <application>tar</> was
-    copying it.  Fortunately, GNU <application>tar</> versions 1.16 and
-    later exit with 1 if a file was changed during the backup,
-    and 2 for other errors.
-   </para>
-
-   <para>
-    It is not necessary to be concerned about the amount of time elapsed
-    between <function>pg_start_backup</> and the start of the actual backup,
-    nor between the end of the backup and <function>pg_stop_backup</>; a
-    few minutes' delay won't hurt anything.  (However, if you normally run the
-    server with <varname>full_page_writes</> disabled, you might notice a drop
-    in performance between <function>pg_start_backup</> and
-    <function>pg_stop_backup</>, since <varname>full_page_writes</> is
-    effectively forced on during backup mode.)  You must ensure that these
-    steps are carried out in sequence, without any possible
-    overlap, or you will invalidate the backup.
-   </para>
-
-   <para>
-    Be certain that your backup dump includes all of the files under
-    the database cluster directory (e.g., <filename>/usr/local/pgsql/data</>).
-    If you are using tablespaces that do not reside underneath this directory,
-    be careful to include them as well (and be sure that your backup dump
-    archives symbolic links as links, otherwise the restore will corrupt
-    your tablespaces).
-   </para>
-
-   <para>
-    You can, however, omit from the backup dump the files within the
-    cluster's <filename>pg_xlog/</> subdirectory.  This
-    slight adjustment is worthwhile because it reduces the risk
-    of mistakes when restoring.  This is easy to arrange if
-    <filename>pg_xlog/</> is a symbolic link pointing to someplace outside
-    the cluster directory, which is a common setup anyway for performance
-    reasons.
-   </para>
-
-   <para>
-    To make use of the backup, you will need to keep all the WAL
-    segment files generated during and after the file system backup.
-    To aid you in doing this, the <function>pg_stop_backup</> function
-    creates a <firstterm>backup history file</> that is immediately
-    stored into the WAL archive area. This file is named after the first
-    WAL segment file that you need for the file system backup.
-    For example, if the starting WAL file is
-    <literal>0000000100001234000055CD</> the backup history file will be
-    named something like
-    <literal>0000000100001234000055CD.007C9330.backup</>. (The second
-    part of the file name stands for an exact position within the WAL
-    file, and can ordinarily be ignored.) Once you have safely archived
-    the file system backup and the WAL segment files used during the
-    backup (as specified in the backup history file), all archived WAL
-    segments with names numerically less are no longer needed to recover
-    the file system backup and can be deleted. However, you should
-    consider keeping several backup sets to be absolutely certain that
-    you can recover your data.
-   </para>
-
-   <para>
-    The backup history file is just a small text file. It contains the
-    label string you gave to <function>pg_start_backup</>, as well as
-    the starting and ending times and WAL segments of the backup.
-    If you used the label to identify the associated dump file,
-    then the archived history file is enough to tell you which dump file to
-    restore.
-   </para>
-
-   <para>
-    Since you have to keep around all the archived WAL files back to your
-    last base backup, the interval between base backups should usually be
-    chosen based on how much storage you want to expend on archived WAL
-    files.  You should also consider how long you are prepared to spend
-    recovering, if recovery should be necessary &mdash; the system will have to
-    replay all those WAL segments, and that could take awhile if it has
-    been a long time since the last base backup.
-   </para>
-
-   <para>
-    It's also worth noting that the <function>pg_start_backup</> function
-    makes a file named <filename>backup_label</> in the database cluster
-    directory, which is removed by <function>pg_stop_backup</>.
-    This file will of course be archived as a part of your backup dump file.
-    The backup label file includes the label string you gave to
-    <function>pg_start_backup</>, as well as the time at which
-    <function>pg_start_backup</> was run, and the name of the starting WAL
-    file.  In case of confusion it is
-    therefore possible to look inside a backup dump file and determine
-    exactly which backup session the dump file came from.
-   </para>
-
-   <para>
-    It is also possible to make a backup dump while the server is
-    stopped.  In this case, you obviously cannot use
-    <function>pg_start_backup</> or <function>pg_stop_backup</>, and
-    you will therefore be left to your own devices to keep track of which
-    backup dump is which and how far back the associated WAL files go.
-    It is generally better to follow the continuous archiving procedure above.
-   </para>
-  </sect2>
-
-  <sect2 id="backup-pitr-recovery">
-   <title>Recovering Using a Continuous Archive Backup</title>
-
-<!## XC> 
-&xconly;
-  <para>
-   This section describes recovering with continuous archive backup
-   for <productname>PostgreSQL</>.  Because Coordinator and Datanode
-   of <productname>Postgres-XC</> are
-   essentially <productname>PostgreSQL</productname>server, you can do
-   this for each Coordinator and Datanode manually.
-  </para>
-<!## end>
-
-   <para>
-    Okay, the worst has happened and you need to recover from your backup.
-    Here is the procedure:
-  <orderedlist>
-   <listitem>
-    <para>
-     Stop the server, if it's running.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     If you have the space to do so,
-     copy the whole cluster data directory and any tablespaces to a temporary
-     location in case you need them later. Note that this precaution will
-     require that you have enough free space on your system to hold two
-     copies of your existing database. If you do not have enough space,
-     you should at least save the contents of the cluster's <filename>pg_xlog</>
-     subdirectory, as it might contain logs which
-     were not archived before the system went down.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Remove all existing files and subdirectories under the cluster data
-     directory and under the root directories of any tablespaces you are using.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Restore the database files from your file system backup.  Be sure that they
-     are restored with the right ownership (the database system user, not
-     <literal>root</>!) and with the right permissions.  If you are using
-     tablespaces,
-     you should verify that the symbolic links in <filename>pg_tblspc/</>
-     were correctly restored.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Remove any files present in <filename>pg_xlog/</>; these came from the
-     file system backup and are therefore probably obsolete rather than current.
-     If you didn't archive <filename>pg_xlog/</> at all, then recreate
-     it with proper permissions,
-     being careful to ensure that you re-establish it as a symbolic link
-     if you had it set up that way before.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     If you have unarchived WAL segment files that you saved in step 2,
-     copy them into <filename>pg_xlog/</>.  (It is best to copy them,
-     not move them, so you still have the unmodified files if a
-     problem occurs and you have to start over.)
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Create a recovery command file <filename>recovery.conf</> in the cluster
-     data directory (see <xref linkend="recovery-config">). You might
-     also want to temporarily modify <filename>pg_hba.conf</> to prevent
-     ordinary users from connecting until you are sure the recovery was successful.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Start the server.  The server will go into recovery mode and
-     proceed to read through the archived WAL files it needs.  Should the
-     recovery be terminated because of an external error, the server can
-     simply be restarted and it will continue recovery.  Upon completion
-     of the recovery process, the server will rename
-     <filename>recovery.conf</> to <filename>recovery.done</> (to prevent
-     accidentally re-entering recovery mode later) and then
-     commence normal database operations.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Inspect the contents of the database to ensure you have recovered to
-     the desired state.  If not, return to step 1.  If all is well,
-     allow your users to connect by restoring <filename>pg_hba.conf</> to normal.
-    </para>
-   </listitem>
-  </orderedlist>
-   </para>
-
-   <para>
-    The key part of all this is to set up a recovery configuration file that
-    describes how you want to recover and how far the recovery should
-    run.  You can use <filename>recovery.conf.sample</> (normally
-    located in the installation's <filename>share/</> directory) as a
-    prototype.  The one thing that you absolutely must specify in
-    <filename>recovery.conf</> is the <varname>restore_command</>,
-    which tells <productname>PostgreSQL</> how to retrieve archived
-    WAL file segments.  Like the <varname>archive_command</>, this is
-    a shell command string.  It can contain <literal>%f</>, which is
-    replaced by the name of the desired log file, and <literal>%p</>,
-    which is replaced by the path name to copy the log file to.
-    (The path name is relative to the current working directory,
-    i.e., the cluster's data directory.)
-    Write <literal>%%</> if you need to embed an actual <literal>%</>
-    character in the command.  The simplest useful command is
-    something like:
-<programlisting>
-restore_command = 'cp /mnt/server/archivedir/%f %p'
-</programlisting>
-    which will copy previously archived WAL segments from the directory
-    <filename>/mnt/server/archivedir</>.  Of course, you can use something
-    much more complicated, perhaps even a shell script that requests the
-    operator to mount an appropriate tape.
-   </para>
-
-   <para>
-    It is important that the command return nonzero exit status on failure.
-    The command <emphasis>will</> be called requesting files that are not present
-    in the archive; it must return nonzero when so asked.  This is not an
-    error condition.  Not all of the requested files will be WAL segment
-    files; you should also expect requests for files with a suffix of
-    <literal>.backup</> or <literal>.history</>. Also be aware that
-    the base name of the <literal>%p</> path will be different from
-    <literal>%f</>; do not expect them to be interchangeable.
-   </para>
-
-   <para>
-    WAL segments that cannot be found in the archive will be sought in
-    <filename>pg_xlog/</>; this allows use of recent un-archived segments.
-    However, segments that are available from the archive will be used in
-    preference to files in <filename>pg_xlog/</>.  The system will not
-    overwrite the existing contents of <filename>pg_xlog/</> when retrieving
-    archived files.
-   </para>
-
-   <para>
-    Normally, recovery will proceed through all available WAL segments,
-    thereby restoring the database to the current point in time (or as
-    close as possible given the available WAL segments).  Therefore, a normal
-    recovery will end with a <quote>file not found</> message, the exact text
-    of the error message depending upon your choice of
-    <varname>restore_command</>.  You may also see an error message
-    at the start of recovery for a file named something like
-    <filename>00000001.history</>.  This is also normal and does not
-    indicate a problem in simple recovery situations; see
-    <xref linkend="backup-timelines"> for discussion.
-   </para>
-
-   <para>
-    If you want to recover to some previous point in time (say, right before
-    the junior DBA dropped your main transaction table), just specify the
-    required stopping point in <filename>recovery.conf</>.  You can specify
-    the stop point, known as the <quote>recovery target</>, either by
-    date/time, named restore point or by completion of a specific transaction
-    ID.  As of this writing only the date/time and named restore point options
-    are very usable, since there are no tools to help you identify with any
-    accuracy which transaction ID to use.
-   </para>
-
-   <note>
-     <para>
-      The stop point must be after the ending time of the base backup, i.e.,
-      the end time of <function>pg_stop_backup</>.  You cannot use a base backup
-      to recover to a time when that backup was in progress.  (To
-      recover to such a time, you must go back to your previous base backup
-      and roll forward from there.)
-     </para>
-   </note>
-
-   <para>
-    If recovery finds corrupted WAL data, recovery will
-    halt at that point and the server will not start. In such a case the
-    recovery process could be re-run from the beginning, specifying a
-    <quote>recovery target</> before the point of corruption so that recovery
-    can complete normally.
-    If recovery fails for an external reason, such as a system crash or
-    if the WAL archive has become inaccessible, then the recovery can simply
-    be restarted and it will restart almost from where it failed.
-    Recovery restart works much like checkpointing in normal operation:
-    the server periodically forces all its state to disk, and then updates
-    the <filename>pg_control</> file to indicate that the already-processed
-    WAL data need not be scanned again.
-   </para>
-
-  </sect2>
-
-  <sect2 id="backup-timelines">
-   <title>Timelines</title>
-
-  <indexterm zone="backup">
-   <primary>timelines</primary>
-  </indexterm>
-
-<!## XC> 
-&xconly;
-  <para>
-   Because Coordinator and Datanode of <productname>Postgres-XC</> are
-   essentially <productname>PostgreSQL</productname>server, you can 
-   apply timelines for each Coordinator and Datanode manually.
-  </para>
-<!## end>
-
-   <para>
-    The ability to restore the database to a previous point in time creates
-    some complexities that are akin to science-fiction stories about time
-    travel and parallel universes.  For example, in the original history of the database,
-    suppose you dropped a critical table at 5:15PM on Tuesday evening, but
-    didn't realize your mistake until Wednesday noon.
-    Unfazed, you get out your backup, restore to the point-in-time 5:14PM
-    Tuesday evening, and are up and running.  In <emphasis>this</> history of
-    the database universe, you never dropped the table.  But suppose
-    you later realize this wasn't such a great idea, and would like
-    to return to sometime Wednesday morning in the original history.
-    You won't be able
-    to if, while your database was up-and-running, it overwrote some of the
-    WAL segment files that led up to the time you now wish you
-    could get back to.  Thus, to avoid this, you need to distinguish the series of
-    WAL records generated after you've done a point-in-time recovery from
-    those that were generated in the original database history.
-   </para>
-
-   <para>
-    To deal with this problem, <productname>PostgreSQL</> has a notion
-    of <firstterm>timelines</>.  Whenever an archive recovery completes,
-    a new timeline is created to identify the series of WAL records
-    generated after that recovery.  The timeline
-    ID number is part of WAL segment file names so a new timeline does
-    not overwrite the WAL data generated by previous timelines.  It is
-    in fact possible to archive many different timelines.  While that might
-    seem like a useless feature, it's often a lifesaver.  Consider the
-    situation where you aren't quite sure what point-in-time to recover to,
-    and so have to do several point-in-time recoveries by trial and error
-    until you find the best place to branch off from the old history.  Without
-    timelines this process would soon generate an unmanageable mess.  With
-    timelines, you can recover to <emphasis>any</> prior state, including
-    states in timeline branches that you abandoned earlier.
-   </para>
-
-   <para>
-    Every time a new timeline is created, <productname>PostgreSQL</> creates
-    a <quote>timeline history</> file that shows which timeline it branched
-    off from and when.  These history files are necessary to allow the system
-    to pick the right WAL segment files when recovering from an archive that
-    contains multiple timelines.  Therefore, they are archived into the WAL
-    archive area just like WAL segment files.  The history files are just
-    small text files, so it's cheap and appropriate to keep them around
-    indefinitely (unlike the segment files which are large).  You can, if
-    you like, add comments to a history file to record your own notes about
-    how and why this particular timeline was created.  Such comments will be
-    especially valuable when you have a thicket of different timelines as
-    a result of experimentation.
-   </para>
-
-   <para>
-    The default behavior of recovery is to recover along the same timeline
-    that was current when the base backup was taken.  If you wish to recover
-    into some child timeline (that is, you want to return to some state that
-    was itself generated after a recovery attempt), you need to specify the
-    target timeline ID in <filename>recovery.conf</>.  You cannot recover into
-    timelines that branched off earlier than the base backup.
-   </para>
-
-  </sect2>
-
-  <sect2 id="backup-tips">
-   <title>Tips and Examples</title>
-
-&pgnotice;
-   <para>
-    Some tips for configuring continuous archiving are given here.
-   </para>
-
-    <sect3 id="backup-standalone">
-     <title>Standalone Hot Backups</title>
-
-&pgnotice;
-     <para>
-      It is possible to use <productname>PostgreSQL</>'s backup facilities to
-      produce standalone hot backups. These are backups that cannot be used
-      for point-in-time recovery, yet are typically much faster to backup and
-      restore than <application>pg_dump</> dumps.  (They are also much larger
-      than <application>pg_dump</> dumps, so in some cases the speed advantage
-      might be negated.)
-     </para>
-
-     <para>
-      To prepare for standalone hot backups, set <varname>wal_level</> to
-      <literal>archive</> (or <literal>hot_standby</>), <varname>archive_mode</> to
-      <literal>on</>, and set up an <varname>archive_command</> that performs
-      archiving only when a <emphasis>switch file</> exists.  For example:
-<programlisting>
-archive_command = 'test ! -f /var/lib/pgsql/backup_in_progress || cp -i %p /var/lib/pgsql/archive/%f &lt; /dev/null'
-</programlisting>
-      This command will perform archiving when
-      <filename>/var/lib/pgsql/backup_in_progress</> exists, and otherwise
-      silently return zero exit status (allowing <productname>PostgreSQL</>
-      to recycle the unwanted WAL file).
-     </para>
-
-     <para>
-      With this preparation, a backup can be taken using a script like the
-      following:
-<programlisting>
-touch /var/lib/pgsql/backup_in_progress
-psql -c "select pg_start_backup('hot_backup');"
-tar -cf /var/lib/pgsql/backup.tar /var/lib/pgsql/data/
-psql -c "select pg_stop_backup();"
-rm /var/lib/pgsql/backup_in_progress
-tar -rf /var/lib/pgsql/backup.tar /var/lib/pgsql/archive/
-</programlisting>
-      The switch file <filename>/var/lib/pgsql/backup_in_progress</> is
-      created first, enabling archiving of completed WAL files to occur.
-      After the backup the switch file is removed. Archived WAL files are
-      then added to the backup so that both base backup and all required
-      WAL files are part of the same <application>tar</> file.
-      Please remember to add error handling to your backup scripts.
-     </para>
-
-     <para>
-      If archive storage size is a concern, use <application>pg_compresslog</>,
-      <ulink url="http://pglesslog.projects.postgresql.org"></ulink>, to
-      remove unnecessary <xref linkend="guc-full-page-writes"> and trailing
-      space from the WAL files.  You can then use
-      <application>gzip</application> to further compress the output of
-      <application>pg_compresslog</>:
-<programlisting>
-archive_command = 'pg_compresslog %p - | gzip &gt; /var/lib/pgsql/archive/%f'
-</programlisting>
-      You will then need to use <application>gunzip</> and
-      <application>pg_decompresslog</> during recovery:
-<programlisting>
-restore_command = 'gunzip &lt; /mnt/server/archivedir/%f | pg_decompresslog - %p'
-</programlisting>
-     </para>
-    </sect3>
-
-    <sect3 id="backup-scripts">
-     <title><varname>archive_command</varname> Scripts</title>
-
-&pgnotice;
-     <para>
-      Many people choose to use scripts to define their
-      <varname>archive_command</varname>, so that their
-      <filename>postgresql.conf</> entry looks very simple:
-<programlisting>
-archive_command = 'local_backup_script.sh'
-</programlisting>
-      Using a separate script file is advisable any time you want to use
-      more than a single command in the archiving process.
-      This allows all complexity to be managed within the script, which
-      can be written in a popular scripting language such as
-      <application>bash</> or <application>perl</>.
-      Any messages written to <literal>stderr</> from the script will appear
-      in the database server log, allowing complex configurations to be
-      diagnosed easily if they fail.
-     </para>
-
-     <para>
-      Examples of requirements that might be solved within a script include:
-      <itemizedlist>
-       <listitem>
-        <para>
-         Copying data to secure off-site data storage
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Batching WAL files so that they are transferred every three hours,
-         rather than one at a time
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Interfacing with other backup and recovery software
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Interfacing with monitoring software to report errors
-        </para>
-       </listitem>
-      </itemizedlist>
-     </para>
-    </sect3>
-  </sect2>
-
-
-  <sect2 id="continuous-archiving-caveats">
-   <title>Caveats</title>
-
-   <para>
-    At this writing, there are several limitations of the continuous archiving
-    technique.  These will probably be fixed in future releases:
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Operations on hash indexes are not presently WAL-logged, so
-     replay will not update these indexes.  This will mean that any new inserts
-     will be ignored by the index, updated rows will apparently disappear and
-     deleted rows will still retain pointers. In other words, if you modify a
-     table with a hash index on it then you will get incorrect query results
-     on a standby server.  When recovery completes it is recommended that you
-     manually <xref linkend="sql-reindex">
-     each such index after completing a recovery operation.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     If a <xref linkend="sql-createdatabase">
-     command is executed while a base backup is being taken, and then
-     the template database that the <command>CREATE DATABASE</> copied
-     is modified while the base backup is still in progress, it is
-     possible that recovery will cause those modifications to be
-     propagated into the created database as well.  This is of course
-     undesirable.  To avoid this risk, it is best not to modify any
-     template databases while taking a base backup.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <xref linkend="sql-createtablespace">
-     commands are WAL-logged with the literal absolute path, and will
-     therefore be replayed as tablespace creations with the same
-     absolute path.  This might be undesirable if the log is being
-     replayed on a different machine.  It can be dangerous even if the
-     log is being replayed on the same machine, but into a new data
-     directory: the replay will still overwrite the contents of the
-     original tablespace.  To avoid potential gotchas of this sort,
-     the best practice is to take a new base backup after creating or
-     dropping tablespaces.
-    </para>
-   </listitem>
-  </itemizedlist>
-   </para>
-
-   <para>
-    It should also be noted that the default <acronym>WAL</acronym>
-    format is fairly bulky since it includes many disk page snapshots.
-    These page snapshots are designed to support crash recovery, since
-    we might need to fix partially-written disk pages.  Depending on
-    your system hardware and software, the risk of partial writes might
-    be small enough to ignore, in which case you can significantly
-    reduce the total volume of archived logs by turning off page
-    snapshots using the <xref linkend="guc-full-page-writes">
-    parameter.  (Read the notes and warnings in <xref linkend="wal">
-    before you do so.)  Turning off page snapshots does not prevent
-    use of the logs for PITR operations.  An area for future
-    development is to compress archived WAL data by removing
-    unnecessary page copies even when <varname>full_page_writes</> is
-    on.  In the meantime, administrators might wish to reduce the number
-    of page snapshots included in WAL by increasing the checkpoint
-    interval parameters as much as feasible.
-   </para>
-  </sect2>
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/biblio.sgmlin b/doc-xc/src/sgml/biblio.sgmlin
deleted file mode 100644
index 290f28c086..0000000000
--- a/doc-xc/src/sgml/biblio.sgmlin
+++ /dev/null
@@ -1,594 +0,0 @@
-<!-- doc/src/sgml/biblio.sgml -->
-
- <bibliography id="biblio">
-  <title>Bibliography</title>
-
-  <para>
-   Selected references and readings for <acronym>SQL</acronym>
-   and <productname>PostgreSQL</productname>.
-  </para>
-
-  <para>
-   Some white papers and technical reports from the original
-   <productname>POSTGRES</productname> development team
-   are available at the University of California, Berkeley, Computer Science
-   Department <ulink url="http://db.cs.berkeley.edu/papers/">
-   web site</ulink>.
-  </para>
-
-  <bibliodiv>
-   <title><acronym>SQL</acronym> Reference Books</title>
-   <para>Reference texts for <acronym>SQL</acronym> features.</para>
-
-   <biblioentry id="BOWMAN01">
-    <title>The Practical <acronym>SQL</acronym> Handbook</title>
-    <titleabbrev>Bowman et al, 2001</titleabbrev>
-    <subtitle>Using SQL Variants</subtitle>
-    <edition>Fourth Edition</edition>
-    <authorgroup>
-     <author>
-      <firstname>Judith</firstname>
-      <surname>Bowman</surname>
-     </author>
-     <author>
-      <firstname>Sandra</firstname>
-      <surname>Emerson</surname>
-     </author>
-     <author>
-      <firstname>Marcy</firstname>
-      <surname>Darnovsky</surname>
-     </author>
-    </authorgroup>
-    <isbn>0-201-70309-2</isbn>
-    <pubdate>2001</pubdate>
-    <publisher>
-     <publishername>Addison-Wesley Professional</publishername>
-    </publisher>
-    <copyright>
-     <year>2001</year>
-    </copyright>
-   </biblioentry>
-
-   <biblioentry id="DATE97">
-    <title>A Guide to the <acronym>SQL</acronym> Standard</title>
-    <titleabbrev>Date and Darwen, 1997</titleabbrev>
-    <subtitle>A user's guide to the standard database language <acronym>SQL</acronym></subtitle>
-    <edition>Fourth Edition</edition>
-    <authorgroup>
-     <author>
-      <firstname>C. J.</firstname>
-      <surname>Date</surname>
-     </author>
-     <author>
-      <firstname>Hugh</firstname>
-      <surname>Darwen</surname>
-     </author>
-    </authorgroup>
-    <isbn>0-201-96426-0</isbn>
-    <pubdate>1997</pubdate>
-    <publisher>
-     <publishername>Addison-Wesley</publishername>
-    </publisher>
-    <copyright>
-     <year>1997</year>
-     <holder>Addison-Wesley Longman, Inc.</holder>
-    </copyright>
-   </biblioentry>
-
-   <biblioentry id="DATE04">
-    <title>An Introduction to Database Systems</title>
-    <titleabbrev>Date, 2004</titleabbrev>
-    <edition>Eighth Edition</edition>
-    <authorgroup>
-     <author>
-      <firstname>C. J.</firstname>
-      <surname>Date</surname>
-     </author>
-    </authorgroup>
-    <isbn>0-321-19784-4</isbn>
-    <pubdate>2003</pubdate>
-    <publisher>
-     <publishername>Addison-Wesley</publishername>
-    </publisher>
-    <copyright>
-     <year>2004</year>
-     <holder>Pearson Education, Inc.</holder>
-    </copyright>
-   </biblioentry>
-
-  <biblioentry id="ELMA04">
-   <title>Fundamentals of Database Systems</title>
-   <edition>Fourth Edition</edition>
-   <authorgroup>
-    <author>
-     <firstname>Ramez</firstname>
-     <surname>Elmasri</surname>
-    </author>
-    <author>
-     <firstname>Shamkant</firstname>
-     <surname>Navathe</surname>
-    </author>
-   </authorgroup>
-   <isbn>0-321-12226-7</isbn>
-   <pubdate>2003</pubdate>
-   <publisher>
-    <publishername>Addison-Wesley</publishername>
-   </publisher>
-   <copyright>
-    <year>2004</year>
-   </copyright>
-  </biblioentry>
-
-   <biblioentry id="MELT93">
-    <title>Understanding the New <acronym>SQL</acronym></title>
-    <titleabbrev>Melton and Simon, 1993</titleabbrev>
-    <subtitle>A complete guide</subtitle>
-    <authorgroup>
-     <author>
-      <firstname>Jim</firstname>
-      <surname>Melton</surname>
-     </author>
-     <author>
-      <firstname>Alan R.</firstname>
-      <surname>Simon</surname>
-     </author>
-    </authorgroup>
-    <isbn>1-55860-245-3</isbn>
-    <pubdate>1993</pubdate>
-    <publisher>
-     <publishername>Morgan Kaufmann</publishername>
-    </publisher>
-    <copyright>
-     <year>1993</year>
-     <holder>Morgan Kaufmann Publishers, Inc.</holder>
-    </copyright>
-   </biblioentry>
-
-   <biblioentry id="ULL88">
-    <title>Principles of Database and Knowledge</title>
-    <subtitle>Base Systems</subtitle>
-    <titleabbrev>Ullman, 1988</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>Jeffrey D.</firstname>
-      <surname>Ullman</surname>
-     </author>
-    </authorgroup>
-    <volumenum>Volume 1</volumenum>
-    <publisher>
-     <publishername>Computer Science Press</publishername>
-    </publisher>
-    <pubdate>1988</pubdate>
-   </biblioentry>
-
-  </bibliodiv>
-
-  <bibliodiv>
-   <title>PostgreSQL-specific Documentation</title>
-   <para>This section is for related documentation.</para>
-
-   <biblioentry id="SIM98">
-    <title>Enhancement of the ANSI SQL Implementation of PostgreSQL</title>
-    <titleabbrev>Simkovics, 1998</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>Stefan</firstname>
-      <surname>Simkovics</surname>
-<!--
-Paul-Peters-Gasse 36
-2384 Breitenfurt
-AUSTRIA
[email protected]
--->
-     </author>
-    </authorgroup>
-<!--
-    <othercredit>
-     <contrib>
-      with support by
-     </contrib>
-     <honorific>O. Univ. Prof. Dr.</honorific>
-     <firstname>Georg</firstname>
-     <surname>Gottlob</surname>
-     <honorific>Univ. Ass. Mag.</honorific>
-     <firstname>Katrin</firstname>
-     <surname>Seyr</surname>
-    </othercredit>
--->
-    <abstract>
-     <para>
-      Discusses SQL history and syntax, and describes the addition of
-      <literal>INTERSECT</> and <literal>EXCEPT</> constructs into
-      <productname>PostgreSQL</productname>.  Prepared as a Master's
-      Thesis with the support of O. Univ. Prof. Dr. Georg Gottlob and
-      Univ. Ass. Mag. Katrin Seyr at Vienna University of Technology.
-     </para>
-    </abstract>
-
-    <pubdate>November 29, 1998</pubdate>
-    <publisher>
-     <publishername>Department of Information Systems, Vienna University of Technology</publishername>
-     <address>Vienna, Austria</address>
-    </publisher>
-   </biblioentry>
-
-   <biblioentry id="YU95">
-    <title>The <productname>Postgres95</productname> User Manual</title>
-    <titleabbrev>Yu and Chen, 1995</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>A.</firstname>
-      <surname>Yu</surname>
-     </author>
-     <author>
-      <firstname>J.</firstname>
-      <surname>Chen</surname>
-     </author>
-    </authorgroup>
-    <authorgroup>
-     <collab>
-      <collabname>The POSTGRES Group</collabname>
-     </collab>
-    </authorgroup>
-
-    <pubdate>Sept. 5, 1995</pubdate>
-    <publisher>
-     <publishername>University  of  California</publishername>
-     <address>Berkeley, California</address>
-    </publisher>
-   </biblioentry>
-
-  <biblioentry id="FONG">
-   <title>
-   <ulink url="http://db.cs.berkeley.edu/papers/UCB-MS-zfong.pdf">
-   The design and implementation of the <productname>POSTGRES</productname> query optimizer
-   </ulink></title>
-   <author>
-    <firstname>Zelaine</firstname>
-    <surname>Fong</surname>
-   </author>
-   <publisher>
-    <publishername>University of California, Berkeley, Computer Science Department</publishername>
-   </publisher>
-  </biblioentry>
-
-  </bibliodiv>
-
-  <bibliodiv>
-   <title>Proceedings and Articles</title>
-   <para>This section is for articles and newsletters.</para>
-
-   <biblioentry id="OLSON93">
-    <title>Partial indexing in POSTGRES: research project</title>
-    <titleabbrev>Olson, 1993</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>Nels</firstname>
-      <surname>Olson</surname>
-     </author>
-    </authorgroup>
-    <pubdate>1993</pubdate>
-    <pubsnumber>UCB Engin T7.49.1993 O676</pubsnumber>
-    <publisher>
-     <publishername>University  of  California</publishername>
-     <address>Berkeley, California</address>
-    </publisher>
-   </biblioentry>
-
-   <biblioentry id="ONG90">
-   <biblioset relation="article">
-    <title>A Unified Framework for Version Modeling Using Production Rules in a Database System</title>
-    <titleabbrev>Ong and Goh, 1990</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>L.</firstname>
-      <surname>Ong</surname>
-     </author>
-     <author>
-      <firstname>J.</firstname>
-      <surname>Goh</surname>
-     </author>
-    </authorgroup>
-   </biblioset>
-   <biblioset relation="journal">
-    <title>ERL Technical Memorandum M90/33</title>
-    <pubdate>April, 1990</pubdate>
-    <publisher>
-     <publishername>University  of  California</publishername>
-     <address>Berkely, California</address>
-    </publisher>
-   </biblioset>
-   </biblioentry>
-
-   <biblioentry id="ROWE87">
-   <biblioset relation="article">
-    <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M87-13.pdf">
-    The <productname>POSTGRES</productname> data model
-    </ulink></title>
-    <titleabbrev>Rowe and Stonebraker, 1987</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>L.</firstname>
-      <surname>Rowe</surname>
-     </author>
-     <author>
-      <firstname>M.</firstname>
-      <surname>Stonebraker</surname>
-     </author>
-    </authorgroup>
-    </biblioset>
-    <confgroup>
-     <conftitle>VLDB Conference</conftitle>
-     <confdates>Sept. 1987</confdates>
-     <address>Brighton, England</address>
-    </confgroup>
-   </biblioentry>
-
-   <biblioentry id="SESHADRI95">
-   <biblioset relation="article">
-    <title>Generalized Partial Indexes
-    <ulink url="http://citeseer.ist.psu.edu/seshadri95generalized.html">(cached version)
-<!--
-     Original URL:  http://citeseer.ist.psu.edu/seshadri95generalized.html
--->
-    </ulink>
-    </title>
-    <titleabbrev>Seshardri, 1995</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>P.</firstname>
-      <surname>Seshadri</surname>
-     </author>
-     <author>
-      <firstname>A.</firstname>
-      <surname>Swami</surname>
-     </author>
-    </authorgroup>
-   </biblioset>
-    <confgroup>
-     <conftitle>Eleventh International Conference on Data Engineering</conftitle>
-     <confdates>6-10 March 1995</confdates>
-     <address>Taipeh, Taiwan</address>
-    </confgroup>
-    <pubdate>1995</pubdate>
-    <pubsnumber>Cat. No.95CH35724</pubsnumber>
-    <publisher>
-     <publishername>IEEE Computer Society Press</publishername>
-     <address>Los Alamitos, California</address>
-    </publisher>
-    <pagenums>420-7</pagenums>
-   </biblioentry>
-
-   <biblioentry id="STON86">
-   <biblioset relation="article">
-    <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M85-95.pdf">
-    The design of <productname>POSTGRES</productname>
-    </ulink></title>
-    <titleabbrev>Stonebraker and Rowe, 1986</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>M.</firstname>
-      <surname>Stonebraker</surname>
-     </author>
-     <author>
-      <firstname>L.</firstname>
-      <surname>Rowe</surname>
-     </author>
-    </authorgroup>
-   </biblioset>
-    <confgroup>
-     <conftitle>ACM-SIGMOD Conference on Management of Data</conftitle>
-     <confdates>May 1986</confdates>
-     <address>Washington, DC</address>
-    </confgroup>
-   </biblioentry>
-
-   <biblioentry id="STON87a">
-   <biblioset relation="article">
-    <title>The design of the <productname>POSTGRES</productname> rules system</title>
-    <titleabbrev>Stonebraker, Hanson, Hong, 1987</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>M.</firstname>
-      <surname>Stonebraker</surname>
-     </author>
-     <author>
-      <firstname>E.</firstname>
-      <surname>Hanson</surname>
-     </author>
-     <author>
-      <firstname>C. H.</firstname>
-      <surname>Hong</surname>
-     </author>
-    </authorgroup>
-   </biblioset>
-    <confgroup>
-     <conftitle>IEEE Conference on Data Engineering</conftitle>
-     <confdates>Feb. 1987</confdates>
-     <address>Los Angeles, California</address>
-    </confgroup>
-   </biblioentry>
-
-   <biblioentry id="STON87b">
-   <biblioset relation="article">
-    <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M87-06.pdf">
-    The design of the <productname>POSTGRES</productname> storage system
-    </ulink></title>
-    <titleabbrev>Stonebraker, 1987</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>M.</firstname>
-      <surname>Stonebraker</surname>
-     </author>
-    </authorgroup>
-   </biblioset>
-    <confgroup>
-     <conftitle>VLDB Conference</conftitle>
-     <confdates>Sept. 1987</confdates>
-     <address>Brighton, England</address>
-    </confgroup>
-   </biblioentry>
-
-   <biblioentry id="STON89">
-   <biblioset relation="article">
-    <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M89-82.pdf">
-    A commentary on the <productname>POSTGRES</productname> rules system
-    </ulink></title>
-    <titleabbrev>Stonebraker et al, 1989</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>M.</firstname>
-      <surname>Stonebraker</surname>
-     </author>
-     <author>
-      <firstname>M.</firstname>
-      <surname>Hearst</surname>
-     </author>
-     <author>
-      <firstname>S.</firstname>
-      <surname>Potamianos</surname>
-     </author>
-    </authorgroup>
-   </biblioset>
-   <biblioset relation="journal">
-    <title>SIGMOD Record 18(3)</title>
-    <date>Sept. 1989</date>
-   </biblioset>
-   </biblioentry>
-
-   <biblioentry id="STON89b">
-   <biblioset relation="article">
-    <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M89-17.pdf">
-    The case for partial indexes
-    </ulink></title>
-    <titleabbrev>Stonebraker, M, 1989b</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>M.</firstname>
-      <surname>Stonebraker</surname>
-     </author>
-    </authorgroup>
-   </biblioset>
-   <biblioset relation="journal">
-    <title>SIGMOD Record 18(4)</title>
-    <pagenums>4-11</pagenums>
-    <date>Dec. 1989</date>
-   </biblioset>
-   </biblioentry>
-
-   <biblioentry id="STON90a">
-   <biblioset relation="article">
-    <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M90-34.pdf">
-    The implementation of <productname>POSTGRES</productname>
-    </ulink></title>
-    <titleabbrev>Stonebraker, Rowe, Hirohama, 1990</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>M.</firstname>
-      <surname>Stonebraker</surname>
-     </author>
-     <author>
-      <firstname>L. A.</firstname>
-      <surname>Rowe</surname>
-     </author>
-     <author>
-      <firstname>M.</firstname>
-      <surname>Hirohama</surname>
-      </author>
-    </authorgroup>
-   </biblioset>
-   <biblioset relation="journal">
-    <title>Transactions on Knowledge and Data Engineering 2(1)</title>
-    <publisher>
-     <publishername>IEEE</publishername>
-    </publisher>
-    <date>March 1990</date>
-   </biblioset>
-   </biblioentry>
-
-   <biblioentry id="STON90b">
-   <biblioset relation="article">
-    <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M90-36.pdf">
-    On Rules, Procedures, Caching and Views in Database Systems
-    </ulink></title>
-    <titleabbrev>Stonebraker et al, ACM, 1990</titleabbrev>
-    <authorgroup>
-     <author>
-      <firstname>M.</firstname>
-      <surname>Stonebraker</surname>
-     </author>
-     <author>
-      <firstname>A.</firstname>
-      <surname>Jhingran</surname>
-     </author>
-     <author>
-      <firstname>J.</firstname>
-      <surname>Goh</surname>
-     </author>
-     <author>
-      <firstname>S.</firstname>
-      <surname>Potamianos</surname>
-     </author>
-    </authorgroup>
-   </biblioset>
-    <confgroup>
-     <conftitle>ACM-SIGMOD Conference on Management of Data</conftitle>
-     <confdates>June 1990</confdates>
-    </confgroup>
-   </biblioentry>
-
-<!## XC>
-   <biblioentry id="OZS91">
-    <title>Principles of Distributed Database Systems</title>
-    <titleabbrev>Ozsu and Valduriez, 1991</titleabbrev>
-    <edition>Second Edition</edition>
-    <authorgroup>
-     <author>
-      <firstname>M. Tamer</firstname>
-      <surname>Ozsu</surname>
-     </author>
-     <author>
-      <firstname>Patrick</firstname>
-      <surname>Valduriez</surname>
-     </author>
-    </authorgroup>
-    <isbn>0-13-659707-6</isbn>
-    <pubdate>1991</pubdate>
-    <publisher>
-     <publishername>Prentice Hall</publishername>
-    </publisher>
-    <copyright>
-     <year>1991, 1999</year>
-     <holder>Prentice-Hall, Inc.</holder>
-    </copyright>
-   </biblioentry>
-<!## end>
-<!## XL>
-   <biblioentry id="OZS91">
-    <title>Principles of Distributed Database Systems</title>
-    <titleabbrev>Ozsu and Valduriez, 1991</titleabbrev>
-    <edition>Second Edition</edition>
-    <authorgroup>
-     <author>
-      <firstname>M. Tamer</firstname>
-      <surname>Ozsu</surname>
-     </author>
-     <author>
-      <firstname>Patrick</firstname>
-      <surname>Valduriez</surname>
-     </author>
-    </authorgroup>
-    <isbn>0-13-659707-6</isbn>
-    <pubdate>1991</pubdate>
-    <publisher>
-     <publishername>Prentice Hall</publishername>
-    </publisher>
-    <copyright>
-     <year>1991, 1999</year>
-     <holder>Prentice-Hall, Inc.</holder>
-    </copyright>
-   </biblioentry>
-<!## end>
-
-  </bibliodiv>
- </bibliography>
diff --git a/doc-xc/src/sgml/bki.sgmlin b/doc-xc/src/sgml/bki.sgmlin
deleted file mode 100644
index 92655d0dfb..0000000000
--- a/doc-xc/src/sgml/bki.sgmlin
+++ /dev/null
@@ -1,371 +0,0 @@
-<!-- doc/src/sgml/bki.sgml -->
-
-<chapter id="bki">
- <title><acronym>BKI</acronym> Backend Interface</title>
-
-&common;
-
- <para>
-  Backend Interface (<acronym>BKI</acronym>) files are scripts in a
-  special language that is understood by the
-<!## PG>
-  <productname>PostgreSQL</productname> backend when running in the
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> backend when running in the
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> backend when running in the
-<!## end>
-  <quote>bootstrap</quote> mode.  The bootstrap mode allows system catalogs
-  to be created and filled from scratch, whereas ordinary SQL commands
-  require the catalogs to exist already.
-  <acronym>BKI</acronym> files can therefore be used to create the
-  database system in the first place.  (And they are probably not
-  useful for anything else.)
- </para>
-
- <para>
-  <application>initdb</application> uses a <acronym>BKI</acronym> file
-  to do part of its job when creating a new database cluster.  The
-  input file used by <application>initdb</application> is created as
-  part of building and installing <productname>PostgreSQL</productname>
-  by a program named <filename>genbki.pl</filename>, which reads some
-  specially formatted C header files in the <filename>src/include/catalog/</>
-  directory of the source tree.  The created <acronym>BKI</acronym> file
-  is called <filename>postgres.bki</filename> and is
-  normally installed in the
-  <filename>share</filename> subdirectory of the installation tree.
- </para>
-
- <para>
-  Related information can be found in the documentation for
-  <application>initdb</application>.
- </para>
-
- <sect1 id="bki-format">
-  <title><acronym>BKI</acronym> File Format</title>
-
-&common;
-  <para>
-   This section describes how the <productname>PostgreSQL</productname>
-   backend interprets <acronym>BKI</acronym> files.  This description
-   will be easier to understand if the <filename>postgres.bki</filename>
-   file is at hand as an example.
-  </para>
-
-  <para>
-   <acronym>BKI</acronym> input consists of a sequence of commands.  Commands are made up
-   of a number of tokens, depending on the syntax of the command.
-   Tokens are usually separated by whitespace, but need not be if
-   there is no ambiguity.  There is no special command separator; the
-   next token that syntactically cannot belong to the preceding
-   command starts a new one.  (Usually you would put a new command on
-   a new line, for clarity.)  Tokens can be certain key words, special
-   characters (parentheses, commas, etc.), numbers, or double-quoted
-   strings.  Everything is case sensitive.
-  </para>
-
-  <para>
-   Lines starting with <literal>#</literal> are ignored.
-  </para>
-
- </sect1>
-
- <sect1 id="bki-commands">
-  <title><acronym>BKI</acronym> Commands</title>
-
-  <variablelist>
-   <varlistentry>
-    <term>
-     <literal>create</>
-     <replaceable class="parameter">tablename</replaceable>
-     <replaceable class="parameter">tableoid</replaceable>
-     <optional><literal>bootstrap</></optional>
-     <optional><literal>shared_relation</></optional>
-     <optional><literal>without_oids</></optional>
-     <optional><literal>rowtype_oid</> <replaceable>oid</></optional>
-     (<replaceable class="parameter">name1</replaceable> =
-     <replaceable class="parameter">type1</replaceable> <optional>,
-     <replaceable class="parameter">name2</replaceable> = <replaceable
-     class="parameter">type2</replaceable>, ...</optional>)
-    </term>
-
-    <listitem>
-&common;
-     <para>
-      Create a table named <replaceable
-      class="parameter">tablename</replaceable>, and having the OID
-      <replaceable class="parameter">tableoid</replaceable>,
-      with the columns given in parentheses.
-     </para>
-
-     <para>
-      The following column types are supported directly by
-      <filename>bootstrap.c</>: <type>bool</type>,
-      <type>bytea</type>, <type>char</type> (1 byte),
-      <type>name</type>, <type>int2</type>,
-      <type>int4</type>, <type>regproc</type>, <type>regclass</type>,
-      <type>regtype</type>, <type>text</type>,
-      <type>oid</type>, <type>tid</type>, <type>xid</type>,
-      <type>cid</type>, <type>int2vector</type>, <type>oidvector</type>,
-      <type>_int4</type> (array), <type>_text</type> (array),
-      <type>_oid</type> (array), <type>_char</type> (array),
-      <type>_aclitem</type> (array).  Although it is possible to create
-      tables containing columns of other types, this cannot be done until
-      after <structname>pg_type</> has been created and filled with
-      appropriate entries.  (That effectively means that only these
-      column types can be used in bootstrapped tables, but non-bootstrap
-      catalogs can contain any built-in type.)
-     </para>
-
-     <para>
-      When <literal>bootstrap</> is specified,
-      the table will only be created on disk; nothing is entered into
-      <structname>pg_class</structname>,
-      <structname>pg_attribute</structname>, etc, for it.  Thus the
-      table will not be accessible by ordinary SQL operations until
-      such entries are made the hard way (with <literal>insert</>
-      commands).  This option is used for creating
-      <structname>pg_class</structname> etc themselves.
-     </para>
-
-     <para>
-      The table is created as shared if <literal>shared_relation</> is
-      specified.
-      It will have OIDs unless <literal>without_oids</> is specified.
-      The table's row type OID (<structname>pg_type</> OID) can optionally
-      be specified via the <literal>rowtype_oid</> clause; if not specified,
-      an OID is automatically generated for it.  (The <literal>rowtype_oid</>
-      clause is useless if <literal>bootstrap</> is specified, but it can be
-      provided anyway for documentation.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <literal>open</> <replaceable class="parameter">tablename</replaceable>
-    </term>
-
-    <listitem>
-     <para>
-      Open the table named
-      <replaceable class="parameter">tablename</replaceable>
-      for insertion of data.  Any currently open table is closed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <literal>close</> <optional><replaceable class="parameter">tablename</replaceable></optional>
-    </term>
-
-    <listitem>
-     <para>
-      Close the open table.  The name of the table can be given as a
-      cross-check, but this is not required.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <literal>insert</> <optional><literal>OID =</> <replaceable class="parameter">oid_value</replaceable></optional> <literal>(</> <replaceable class="parameter">value1</replaceable> <replaceable class="parameter">value2</replaceable> ... <literal>)</>
-    </term>
-
-    <listitem>
-     <para>
-      Insert a new row into the open table using <replaceable
-      class="parameter">value1</replaceable>, <replaceable
-      class="parameter">value2</replaceable>, etc., for its column
-      values and <replaceable
-      class="parameter">oid_value</replaceable> for its OID.  If
-      <replaceable class="parameter">oid_value</replaceable> is zero
-      (0) or the clause is omitted, and the table has OIDs, then the
-      next available OID is assigned.
-     </para>
-
-     <para>
-      NULL values can be specified using the special key word
-      <literal>_null_</literal>.  Values containing spaces must be
-      double quoted.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <literal>declare</> <optional><literal>unique</></optional>
-     <literal>index</> <replaceable class="parameter">indexname</replaceable>
-     <replaceable class="parameter">indexoid</replaceable>
-     <literal>on</> <replaceable class="parameter">tablename</replaceable>
-     <literal>using</> <replaceable class="parameter">amname</replaceable>
-     <literal>(</> <replaceable class="parameter">opclass1</replaceable>
-     <replaceable class="parameter">name1</replaceable>
-     <optional>, ...</optional> <literal>)</>
-    </term>
-
-    <listitem>
-     <para>
-      Create an index named <replaceable
-      class="parameter">indexname</replaceable>, having OID
-      <replaceable class="parameter">indexoid</replaceable>,
-      on the table named
-      <replaceable class="parameter">tablename</replaceable>, using the
-      <replaceable class="parameter">amname</replaceable> access
-      method.  The fields to index are called <replaceable
-      class="parameter">name1</replaceable>, <replaceable
-      class="parameter">name2</replaceable> etc., and the operator
-      classes to use are <replaceable
-      class="parameter">opclass1</replaceable>, <replaceable
-      class="parameter">opclass2</replaceable> etc., respectively.
-      The index file is created and appropriate catalog entries are
-      made for it, but the index contents are not initialized by this command.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <literal>declare toast</>
-     <replaceable class="parameter">toasttableoid</replaceable>
-     <replaceable class="parameter">toastindexoid</replaceable>
-     <literal>on</> <replaceable class="parameter">tablename</replaceable>
-    </term>
-
-    <listitem>
-     <para>
-      Create a TOAST table for the table named
-      <replaceable class="parameter">tablename</replaceable>.
-      The TOAST table is assigned OID
-      <replaceable class="parameter">toasttableoid</replaceable>
-      and its index is assigned OID
-      <replaceable class="parameter">toastindexoid</replaceable>.
-      As with <literal>declare index</>, filling of the index
-      is postponed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>build indices</></term>
-
-    <listitem>
-     <para>
-      Fill in the indices that have previously been declared.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
- </sect1>
-
- <sect1 id="bki-structure">
-  <title>Structure of the Bootstrap <acronym>BKI</acronym> File</title>
-&common;
-
-  <para>
-   The <literal>open</> command cannot be used until the tables it uses
-   exist and have entries for the table that is to be opened.
-   (These minimum tables are <structname>pg_class</>,
-   <structname>pg_attribute</>, <structname>pg_proc</>, and
-   <structname>pg_type</>.)   To allow those tables themselves to be filled,
-   <literal>create</> with the <literal>bootstrap</> option implicitly opens
-   the created table for data insertion.
-  </para>
-
-  <para>
-   Also, the <literal>declare index</> and <literal>declare toast</>
-   commands cannot be used until the system catalogs they need have been
-   created and filled in.
-  </para>
-
-  <para>
-   Thus, the structure of the <filename>postgres.bki</filename> file has to
-   be:
-   <orderedlist>
-    <listitem>
-     <para>
-      <literal>create bootstrap</> one of the critical tables
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>insert</> data describing at least the critical tables
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>close</>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Repeat for the other critical tables.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>create</> (without <literal>bootstrap</>) a noncritical table
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>open</>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>insert</> desired data
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>close</>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Repeat for the other noncritical tables.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Define indexes and toast tables.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>build indices</>
-     </para>
-    </listitem>
-   </orderedlist>
-  </para>
-
-  <para>
-   There are doubtless other, undocumented ordering dependencies.
-  </para>
- </sect1>
-
- <sect1 id="bki-example">
-  <title>Example</title>
-
-&common;
-  <para>
-   The following sequence of commands will create the
-   table <literal>test_table</literal> with OID 420, having two columns
-   <literal>cola</literal> and <literal>colb</literal> of type
-   <type>int4</type> and <type>text</type>, respectively, and insert
-   two rows into the table:
-<programlisting>
-create test_table 420 (cola = int4, colb = text)
-open test_table
-insert OID=421 ( 1 "value1" )
-insert OID=422 ( 2 _null_ )
-close test_table
-</programlisting>
-  </para>
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/btree-gin.sgmlin b/doc-xc/src/sgml/btree-gin.sgmlin
deleted file mode 100644
index 8e321bb891..0000000000
--- a/doc-xc/src/sgml/btree-gin.sgmlin
+++ /dev/null
@@ -1,59 +0,0 @@
-<!-- doc/src/sgml/btree-gin.sgml -->
-
-<sect1 id="btree-gin" xreflabel="btree_gin">
- <title>btree_gin</title>
-
- <indexterm zone="btree-gin">
-  <primary>btree_gin</primary>
- </indexterm>
-
-&common;
- <para>
-  <filename>btree_gin</> provides sample GIN operator classes that
-  implement B-tree equivalent behavior for the data types
-  <type>int2</>, <type>int4</>, <type>int8</>, <type>float4</>,
-  <type>float8</>, <type>timestamp with time zone</>,
-  <type>timestamp without time zone</>, <type>time with time zone</>,
-  <type>time without time zone</>, <type>date</>, <type>interval</>,
-  <type>oid</>, <type>money</>, <type>"char"</>,
-  <type>varchar</>, <type>text</>, <type>bytea</>, <type>bit</>,
-  <type>varbit</>, <type>macaddr</>, <type>inet</>, and <type>cidr</>.
- </para>
-
- <para>
-  In general, these operator classes will not outperform the equivalent
-  standard B-tree index methods, and they lack one major feature of the
-  standard B-tree code: the ability to enforce uniqueness.  However,
-  they are useful for GIN testing and as a base for developing other
-  GIN operator classes.  Also, for queries that test both a GIN-indexable
-  column and a B-tree-indexable column, it might be more efficient to create
-  a multicolumn GIN index that uses one of these operator classes than to create
-  two separate indexes that would have to be combined via bitmap ANDing.
- </para>
-
- <sect2>
-  <title>Example Usage</title>
-&common;
-<programlisting>
-CREATE TABLE test (a int4);
--- create index
-CREATE INDEX testidx ON test USING gin (a);
--- query
-SELECT * FROM test WHERE a &lt; 10;
-</programlisting>
-
- </sect2>
-
- <sect2>
-  <title>Authors</title>
-
-  <para>
-   Teodor Sigaev (<email>[email protected]</email>) and
-   Oleg Bartunov (<email>[email protected]</email>).  See
-   <ulink url="http://www.sai.msu.su/~megera/oddmuse/index.cgi/Gin"></ulink>
-   for additional information.
-  </para>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/btree-gist.sgmlin b/doc-xc/src/sgml/btree-gist.sgmlin
deleted file mode 100644
index c0348648bd..0000000000
--- a/doc-xc/src/sgml/btree-gist.sgmlin
+++ /dev/null
@@ -1,131 +0,0 @@
-<!-- doc/src/sgml/btree-gist.sgml -->
-
-<sect1 id="btree-gist" xreflabel="btree_gist">
- <title>btree_gist</title>
-
- <indexterm zone="btree-gist">
-  <primary>btree_gist</primary>
- </indexterm>
-
-&common;
-
- <para>
-  <filename>btree_gist</> provides GiST index operator classes that
-  implement B-tree equivalent behavior for the data types
-  <type>int2</>, <type>int4</>, <type>int8</>, <type>float4</>,
-  <type>float8</>, <type>numeric</>, <type>timestamp with time zone</>,
-  <type>timestamp without time zone</>, <type>time with time zone</>,
-  <type>time without time zone</>, <type>date</>, <type>interval</>,
-  <type>oid</>, <type>money</>, <type>char</>,
-  <type>varchar</>, <type>text</>, <type>bytea</>, <type>bit</>,
-  <type>varbit</>, <type>macaddr</>, <type>inet</>, and <type>cidr</>.
- </para>
-
- <para>
-  In general, these operator classes will not outperform the equivalent
-  standard B-tree index methods, and they lack one major feature of the
-  standard B-tree code: the ability to enforce uniqueness.  However,
-  they provide some other features that are not available with a B-tree
-  index, as described below.  Also, these operator classes are useful
-  when a multicolumn GiST index is needed, wherein some of the columns
-  are of data types that are only indexable with GiST but other columns
-  are just simple data types.  Lastly, these operator classes are useful for
-  GiST testing and as a base for developing other GiST operator classes.
- </para>
-
- <para>
-<!## PG>
-  In addition to the typical B-tree search operators, <filename>btree_gist</>
-  also provides index support for <literal>&lt;&gt;</literal> (<quote>not
-  equals</quote>). This may be useful in combination with an
-  <link linkend="SQL-CREATETABLE-EXCLUDE">exclusion constraint</link>,
-  as described below.
-<!## end>
-<!## XC>
-  <!-- XC does not support "exclude" constraint now -->
-  In addition to the typical B-tree search operators, <filename>btree_gist</>
-  also provides index support for <literal>&lt;&gt;</literal> (<quote>not
-  equals</quote>). 
-<!## end>
-<!## XL>
-  <!-- XL does not support "exclude" constraint now -->
-  In addition to the typical B-tree search operators, <filename>btree_gist</>
-  also provides index support for <literal>&lt;&gt;</literal> (<quote>not
-  equals</quote>). 
-<!## end>
- </para>
-
- <para>
-  Also, for data types for which there is a natural distance metric,
-  <filename>btree_gist</> defines a distance operator <literal>&lt;-&gt;</>,
-  and provides GiST index support for nearest-neighbor searches using
-  this operator.  Distance operators are provided for
-  <type>int2</>, <type>int4</>, <type>int8</>, <type>float4</>,
-  <type>float8</>, <type>timestamp with time zone</>,
-  <type>timestamp without time zone</>,
-  <type>time without time zone</>, <type>date</>, <type>interval</>,
-  <type>oid</>, and <type>money</>.
- </para>
-
- <sect2>
-  <title>Example Usage</title>
-
-&common;
-  <para>
-   Simple example using <literal>btree_gist</literal> instead of <literal>btree</literal>:
-  </para>
-
-<programlisting>
-CREATE TABLE test (a int4);
--- create index
-CREATE INDEX testidx ON test USING gist (a);
--- query
-SELECT * FROM test WHERE a &lt; 10;
--- nearest-neighbor search: find the ten entries closest to "42"
-SELECT *, a &lt;-&gt; 42 AS dist FROM test ORDER BY a &lt;-&gt; 42 LIMIT 10;
-</programlisting>
-
-<!## PG>
-  <!-- XC does not support exclude constraint now -->
-  <para>
-   Use an <link linkend="SQL-CREATETABLE-EXCLUDE">exclusion
-   constraint</link> to enforce the rule that a cage at a zoo
-   can contain only one kind of animal:
-  </para>
-
-<programlisting>
-=&gt; CREATE TABLE zoo (
-  cage   INTEGER,
-  animal TEXT,
-  EXCLUDE USING gist (cage WITH =, animal WITH &lt;&gt;)
-);
-
-=&gt; INSERT INTO zoo VALUES(123, 'zebra');
-INSERT 0 1
-=&gt; INSERT INTO zoo VALUES(123, 'zebra');
-INSERT 0 1
-=&gt; INSERT INTO zoo VALUES(123, 'lion');
-ERROR:  conflicting key value violates exclusion constraint "zoo_cage_animal_excl"
-DETAIL:  Key (cage, animal)=(123, lion) conflicts with existing key (cage, animal)=(123, zebra).
-=&gt; INSERT INTO zoo VALUES(124, 'lion');
-INSERT 0 1
-</programlisting>
-
-<!## end>
-
- </sect2>
-
- <sect2>
-  <title>Authors</title>
-
-  <para>
-   Teodor Sigaev (<email>[email protected]</email>) ,
-   Oleg Bartunov (<email>[email protected]</email>), and
-   Janko Richter (<email>[email protected]</email>).  See
-   <ulink url="http://www.sai.msu.su/~megera/postgres/gist/"></ulink>
-   for additional information.
-  </para>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/catalogs.sgmlin b/doc-xc/src/sgml/catalogs.sgmlin
deleted file mode 100644
index bd949ddd57..0000000000
--- a/doc-xc/src/sgml/catalogs.sgmlin
+++ /dev/null
@@ -1,9076 +0,0 @@
-<!-- doc/src/sgml/catalogs.sgml -->
-<!--
- Documentation of the system catalogs, directed toward PostgreSQL developers
- -->
-
-<chapter id="catalogs">
- <title>System Catalogs</title>
-
-&common;
-
-  <para>
-   The system catalogs are the place where a relational database
-   management system stores schema metadata, such as information about
-   tables and columns, and internal bookkeeping information.
-<!## PG>
-   <productname>PostgreSQL</productname>'s system catalogs are regular
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>'s system catalogs are regular
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>'s system catalogs are regular
-<!## end>
-   tables.  You can drop and recreate the tables, add columns, insert
-   and update values, and severely mess up your system that way.
-   Normally, one should not change the system catalogs by hand, there
-   are always SQL commands to do that.  (For example, <command>CREATE
-   DATABASE</command> inserts a row into the
-   <structname>pg_database</structname> catalog &mdash; and actually
-   creates the database on disk.)  There are some exceptions for
-   particularly esoteric operations, such as adding index access methods.
-  </para>
-
- <sect1 id="catalogs-overview">
-  <title>Overview</title>
-
-&common;
-  <para>
-   <xref linkend="catalog-table"> lists the system catalogs.
-   More detailed documentation of each catalog follows below.
-  </para>
-
-  <para>
-   Most system catalogs are copied from the template database during
-   database creation and are thereafter database-specific. A few
-   catalogs are physically shared across all databases in a cluster;
-   these are noted in the descriptions of the individual catalogs.
-  </para>
-
-  <table id="catalog-table">
-   <title>System Catalogs</title>
-
-   <tgroup cols="2">
-    <thead>
-     <row>
-      <entry>Catalog Name</entry>
-      <entry>Purpose</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><link linkend="catalog-pg-aggregate"><structname>pg_aggregate</structname></link></entry>
-      <entry>aggregate functions</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-am"><structname>pg_am</structname></link></entry>
-      <entry>index access methods</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-amop"><structname>pg_amop</structname></link></entry>
-      <entry>access method operators</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-amproc"><structname>pg_amproc</structname></link></entry>
-      <entry>access method support procedures</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-attrdef"><structname>pg_attrdef</structname></link></entry>
-      <entry>column default values</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-attribute"><structname>pg_attribute</structname></link></entry>
-      <entry>table columns (<quote>attributes</quote>)</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link></entry>
-      <entry>authorization identifiers (roles)</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-auth-members"><structname>pg_auth_members</structname></link></entry>
-      <entry>authorization identifier membership relationships</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-cast"><structname>pg_cast</structname></link></entry>
-      <entry>casts (data type conversions)</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-class"><structname>pg_class</structname></link></entry>
-      <entry>tables, indexes, sequences, views (<quote>relations</quote>)</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-constraint"><structname>pg_constraint</structname></link></entry>
-      <entry>check constraints, unique constraints, primary key constraints, foreign key constraints</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-collation"><structname>pg_collation</structname></link></entry>
-      <entry>collations (locale information)</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-conversion"><structname>pg_conversion</structname></link></entry>
-      <entry>encoding conversion information</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-database"><structname>pg_database</structname></link></entry>
-      <entry>databases within this database cluster</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-db-role-setting"><structname>pg_db_role_setting</structname></link></entry>
-      <entry>per-role and per-database settings</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-default-acl"><structname>pg_default_acl</structname></link></entry>
-      <entry>default privileges for object types</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-depend"><structname>pg_depend</structname></link></entry>
-      <entry>dependencies between database objects</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-description"><structname>pg_description</structname></link></entry>
-      <entry>descriptions or comments on database objects</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-enum"><structname>pg_enum</structname></link></entry>
-      <entry>enum label and value definitions</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-extension"><structname>pg_extension</structname></link></entry>
-      <entry>installed extensions</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-foreign-data-wrapper"><structname>pg_foreign_data_wrapper</structname></link></entry>
-      <entry>foreign-data wrapper definitions</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-foreign-server"><structname>pg_foreign_server</structname></link></entry>
-      <entry>foreign server definitions</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-foreign-table"><structname>pg_foreign_table</structname></link></entry>
-      <entry>additional foreign table information</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-index"><structname>pg_index</structname></link></entry>
-      <entry>additional index information</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-inherits"><structname>pg_inherits</structname></link></entry>
-      <entry>table inheritance hierarchy</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-language"><structname>pg_language</structname></link></entry>
-      <entry>languages for writing functions</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-largeobject"><structname>pg_largeobject</structname></link></entry>
-      <entry>data pages for large objects</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-largeobject-metadata"><structname>pg_largeobject_metadata</structname></link></entry>
-      <entry>metadata for large objects</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link></entry>
-      <entry>schemas</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-opclass"><structname>pg_opclass</structname></link></entry>
-      <entry>access method operator classes</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-operator"><structname>pg_operator</structname></link></entry>
-      <entry>operators</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-opfamily"><structname>pg_opfamily</structname></link></entry>
-      <entry>access method operator families</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-pltemplate"><structname>pg_pltemplate</structname></link></entry>
-      <entry>template data for procedural languages</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link></entry>
-      <entry>functions and procedures</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-rewrite"><structname>pg_rewrite</structname></link></entry>
-      <entry>query rewrite rules</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-seclabel"><structname>pg_seclabel</structname></link></entry>
-      <entry>security labels on database objects</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-shdepend"><structname>pg_shdepend</structname></link></entry>
-      <entry>dependencies on shared objects</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-shdescription"><structname>pg_shdescription</structname></link></entry>
-      <entry>comments on shared objects</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-statistic"><structname>pg_statistic</structname></link></entry>
-      <entry>planner statistics</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-tablespace"><structname>pg_tablespace</structname></link></entry>
-      <entry>tablespaces within this database cluster</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-trigger"><structname>pg_trigger</structname></link></entry>
-      <entry>triggers</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-ts-config"><structname>pg_ts_config</structname></link></entry>
-      <entry>text search configurations</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-ts-config-map"><structname>pg_ts_config_map</structname></link></entry>
-      <entry>text search configurations' token mappings</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-ts-dict"><structname>pg_ts_dict</structname></link></entry>
-      <entry>text search dictionaries</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-ts-parser"><structname>pg_ts_parser</structname></link></entry>
-      <entry>text search parsers</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-ts-template"><structname>pg_ts_template</structname></link></entry>
-      <entry>text search templates</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-type"><structname>pg_type</structname></link></entry>
-      <entry>data types</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="catalog-pg-user-mapping"><structname>pg_user_mapping</structname></link></entry>
-      <entry>mappings of users to foreign servers</entry>
-     </row>
-<!## XC>
-     <row>
-      <entry><link linkend="catalog-pgxc-class"><structname>pgxc_class</structname></link></entry>
-      <entry>replication or distribution information of tables (Postgres-XC only)</entry>
-     </row>
-     <row>
-      <entry><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link></entry>
-      <entry>Postgres-XC cluster nodes (Postgres-XC only)</entry>
-     </row>
-     <row>
-      <entry><link linkend="catalog-pgxc-group"><structname>pgxc_group</structname></link></entry>
-      <entry>Postgres-XC cluster node groups (Postgres-XC only)</entry>
-     </row>
-<!## end>
-<!## XL>
-     <row>
-      <entry><link linkend="catalog-pgxc-class"><structname>pgxc_class</structname></link></entry>
-      <entry>replication or distribution information of tables (Postgres-XL only)</entry>
-     </row>
-     <row>
-      <entry><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link></entry>
-      <entry>Postgres-XL cluster nodes (Postgres-XC only)</entry>
-     </row>
-     <row>
-      <entry><link linkend="catalog-pgxc-group"><structname>pgxc_group</structname></link></entry>
-      <entry>Postgres-XL cluster node groups (Postgres-XC only)</entry>
-     </row>
-<!## end>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-aggregate">
-  <title><structname>pg_aggregate</structname></title>
-
-  <indexterm zone="catalog-pg-aggregate">
-   <primary>pg_aggregate</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_aggregate</structname> stores information about
-   aggregate functions.  An aggregate function is a function that
-   operates on a set of values (typically one column from each row
-   that matches a query condition) and returns a single value computed
-   from all these values.  Typical aggregate functions are
-   <function>sum</function>, <function>count</function>, and
-   <function>max</function>.  Each entry in
-   <structname>pg_aggregate</structname> is an extension of an entry
-   in <structname>pg_proc</structname>.  The <structname>pg_proc</structname>
-   entry carries the aggregate's name, input and output data types, and
-   other information that is similar to ordinary functions.
-  </para>
-
-  <table>
-   <title><structname>pg_aggregate</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>aggfnoid</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><structname>pg_proc</structname> OID of the aggregate function</entry>
-     </row>
-     <row>
-      <entry><structfield>aggtransfn</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Transition function</entry>
-     </row>
-<!## XC>
-     <row>
-      <entry><structfield>aggcollectfn</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Collection function (Only for Postgres-XC></entry>
-     </row>
-<!## end>
-<!## XL>
-     <row>
-      <entry><structfield>aggcollectfn</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Collection function (Only for Postgres-XL>)</entry>
-     </row>
-<!## end>
-     <row>
-      <entry><structfield>aggfinalfn</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Final function (zero if none)</entry>
-     </row>
-     <row>
-      <entry><structfield>aggsortop</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-operator"><structname>pg_operator</structname></link>.oid</literal></entry>
-      <entry>Associated sort operator (zero if none)</entry>
-     </row>
-     <row>
-      <entry><structfield>aggtranstype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-<!## PG>
-      <entry>Data type of the aggregate function's internal transition (state) data</entry>
-<!## end>
-<!## XC>
-      <entry>Data type of the aggregate function's internal transition and collection (state) data (Revised for Postgres-XC)</entry>
-<!## end>
-<!## XL>
-      <entry>Data type of the aggregate function's internal transition and collection (state) data (Revised for Postgres-XL)</entry>
-<!## end>
-     </row>
-     <row>
-      <entry><structfield>agginitval</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       The initial value of the transition state.  This is a text
-       field containing the initial value in its external string
-       representation.  If this field is null, the transition state
-       value starts out null.
-      </entry>
-     </row>
-<!## XC>
-     <row>
-      <entry><structfield>agginitcollect</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       The initial value of the collection state.  This is a text
-       field containing the initial value in its external string
-       representation.  If this field is null, the collection state
-       value starts out null. (Only for Postgres-XC)
-      </entry>
-     </row>
-<!## end>
-<!## XL>
-     <row>
-      <entry><structfield>agginitcollect</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       The initial value of the collection state.  This is a text
-       field containing the initial value in its external string
-       representation.  If this field is null, the collection state
-       value starts out null. (Only for Postgres-XL)
-      </entry>
-     </row>
-<!## end>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   New aggregate functions are registered with the <xref
-   linkend="sql-createaggregate">
-   command.  See <xref linkend="xaggr"> for more information about
-   writing aggregate functions and the meaning of the transition
-   functions, etc.
-  </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-am">
-  <title><structname>pg_am</structname></title>
-
-  <indexterm zone="catalog-pg-am">
-   <primary>pg_am</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_am</structname> stores information about index
-   access methods.  There is one row for each index access method supported by
-   the system.  The contents of this catalog are discussed in detail in
-   <xref linkend="indexam">.
-  </para>
-
-  <table>
-   <title><structname>pg_am</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-
-     <row>
-      <entry><structfield>amname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the access method</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amstrategies</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Number of operator strategies for this access method,
-       or zero if access method does not have a fixed set of operator
-       strategies</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amsupport</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Number of support routines for this access method</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amcanorder</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Does the access method support ordered scans sorted by the
-       indexed column's value?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amcanorderbyop</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Does the access method support ordered scans sorted by the result
-       of an operator on the indexed column?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amcanbackward</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Does the access method support backward scanning?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amcanunique</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Does the access method support unique indexes?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amcanmulticol</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Does the access method support multicolumn indexes?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amoptionalkey</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Does the access method support a scan without any constraint
-       for the first index column?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amsearchnulls</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Does the access method support <literal>IS NULL</>/<literal>NOT NULL</> searches?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amstorage</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Can index storage data type differ from column data type?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amclusterable</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Can an index of this type be clustered on?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ampredlocks</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Does an index of this type manage fine-grained predicate locks?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amkeytype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Type of data stored in index, or zero if not a fixed type</entry>
-     </row>
-
-     <row>
-      <entry><structfield>aminsert</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><quote>Insert this tuple</quote> function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ambeginscan</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><quote>Prepare for index scan</quote> function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amgettuple</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><quote>Next valid tuple</quote> function, or zero if none</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amgetbitmap</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><quote>Fetch all valid tuples</quote> function, or zero if none</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amrescan</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><quote>(Re)start index scan</quote> function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amendscan</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><quote>Clean up after index scan</quote> function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ammarkpos</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><quote>Mark current scan position</quote> function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amrestrpos</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><quote>Restore marked scan position</quote> function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ambuild</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><quote>Build new index</quote> function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ambuildempty</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry><quote>Build empty index</quote> function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ambulkdelete</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Bulk-delete function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amvacuumcleanup</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Post-<command>VACUUM</command> cleanup function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amcostestimate</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Function to estimate cost of an index scan</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amoptions</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Function to parse and validate <structfield>reloptions</> for an index</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-amop">
-  <title><structname>pg_amop</structname></title>
-
-  <indexterm zone="catalog-pg-amop">
-   <primary>pg_amop</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_amop</structname> stores information about
-   operators associated with access method operator families.  There is one
-   row for each operator that is a member of an operator family.  A family
-   member can be either a <firstterm>search</> operator or an
-   <firstterm>ordering</> operator.  An operator
-   can appear in more than one family, but cannot appear in more than one
-   search position nor more than one ordering position within a family.
-   (It is allowed, though unlikely, for an operator to be used for both
-   search and ordering purposes.)
-  </para>
-
-  <table>
-   <title><structname>pg_amop</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-
-     <row>
-      <entry><structfield>amopfamily</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-opfamily"><structname>pg_opfamily</structname></link>.oid</literal></entry>
-      <entry>The operator family this entry is for</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amoplefttype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Left-hand input data type of operator</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amoprighttype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Right-hand input data type of operator</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amopstrategy</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Operator strategy number</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amoppurpose</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>Operator purpose, either <literal>s</> for search or
-       <literal>o</> for ordering</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amopopr</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-operator"><structname>pg_operator</structname></link>.oid</literal></entry>
-      <entry>OID of the operator</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amopmethod</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-am"><structname>pg_am</structname></link>.oid</literal></entry>
-      <entry>Index access method operator family is for</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amopsortfamily</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-opfamily"><structname>pg_opfamily</structname></link>.oid</literal></entry>
-      <entry>The btree operator family this entry sorts according to, if an
-       ordering operator; zero if a search operator</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   A <quote>search</> operator entry indicates that an index of this operator
-   family can be searched to find all rows satisfying
-   <literal>WHERE</>
-   <replaceable>indexed_column</>
-   <replaceable>operator</>
-   <replaceable>constant</>.
-   Obviously, such an operator must return boolean, and its left-hand input
-   type must match the index's column data type.
-  </para>
-
-  <para>
-   An <quote>ordering</> operator entry indicates that an index of this
-   operator family can be scanned to return rows in the order represented by
-   <literal>ORDER BY</>
-   <replaceable>indexed_column</>
-   <replaceable>operator</>
-   <replaceable>constant</>.
-   Such an operator could return any sortable data type, though again
-   its left-hand input type must match the index's column data type.
-   The exact semantics of the <literal>ORDER BY</> are specified by the
-   <structfield>amopsortfamily</structfield> column, which must reference
-   a btree operator family for the operator's result type.
-  </para>
-
-  <note>
-   <para>
-    At present, it's assumed that the sort order for an ordering operator
-    is the default for the referenced opfamily, i.e., <literal>ASC NULLS
-    LAST</>.  This might someday be relaxed by adding additional columns
-    to specify sort options explicitly.
-   </para>
-  </note>
-
-  <para>
-   An entry's <structfield>amopmethod</> must match the
-   <structname>opfmethod</> of its containing operator family (including
-   <structfield>amopmethod</> here is an intentional denormalization of the
-   catalog structure for performance reasons).  Also,
-   <structfield>amoplefttype</> and <structfield>amoprighttype</> must match
-   the <structfield>oprleft</> and <structfield>oprright</> fields of the
-   referenced <structname>pg_operator</> entry.
-  </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-amproc">
-  <title><structname>pg_amproc</structname></title>
-
-  <indexterm zone="catalog-pg-amproc">
-   <primary>pg_amproc</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_amproc</structname> stores information about
-   support procedures associated with access method operator families.  There
-   is one row for each support procedure belonging to an operator family.
-  </para>
-
-  <table>
-   <title><structname>pg_amproc</structname> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-
-     <row>
-      <entry><structfield>amprocfamily</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-opfamily"><structname>pg_opfamily</structname></link>.oid</literal></entry>
-      <entry>The operator family this entry is for</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amproclefttype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Left-hand input data type of associated operator</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amprocrighttype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Right-hand input data type of associated operator</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amprocnum</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Support procedure number</entry>
-     </row>
-
-     <row>
-      <entry><structfield>amproc</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>OID of the procedure</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The usual interpretation of the
-   <structfield>amproclefttype</> and <structfield>amprocrighttype</> fields
-   is that they identify the left and right input types of the operator(s)
-   that a particular support procedure supports.  For some access methods
-   these match the input data type(s) of the support procedure itself, for
-   others not.  There is a notion of <quote>default</> support procedures for
-   an index, which are those with <structfield>amproclefttype</> and
-   <structfield>amprocrighttype</> both equal to the index opclass's
-   <structfield>opcintype</>.
-  </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-attrdef">
-  <title><structname>pg_attrdef</structname></title>
-
-  <indexterm zone="catalog-pg-attrdef">
-   <primary>pg_attrdef</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_attrdef</structname> stores column default values.  The main information
-   about columns is stored in <structname>pg_attribute</structname>
-   (see below).  Only columns that explicitly specify a default value
-   (when the table is created or the column is added) will have an
-   entry here.
-  </para>
-
-  <table>
-   <title><structname>pg_attrdef</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>adrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The table this column belongs to</entry>
-     </row>
-
-     <row>
-      <entry><structfield>adnum</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry><literal><link linkend="catalog-pg-attribute"><structname>pg_attribute</structname></link>.attnum</literal></entry>
-      <entry>The number of the column</entry>
-     </row>
-
-     <row>
-      <entry><structfield>adbin</structfield></entry>
-      <entry><type>pg_node_tree</type></entry>
-      <entry></entry>
-      <entry>The internal representation of the column default value</entry>
-     </row>
-
-     <row>
-      <entry><structfield>adsrc</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>A human-readable representation of the default value</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-   <para>
-    The <structfield>adsrc</structfield> field is historical, and is best
-    not used, because it does not track outside changes that might affect
-    the representation of the default value.  Reverse-compiling the
-    <structfield>adbin</structfield> field (with <function>pg_get_expr</> for
-    example) is a better way to display the default value.
-   </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-attribute">
-  <title><structname>pg_attribute</structname></title>
-
-  <indexterm zone="catalog-pg-attribute">
-   <primary>pg_attribute</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_attribute</structname> stores information about
-   table columns.  There will be exactly one
-   <structname>pg_attribute</structname> row for every column in every
-   table in the database.  (There will also be attribute entries for
-   indexes, and indeed all objects that have <structname>pg_class</structname>
-   entries.)
-  </para>
-
-  <para>
-   The term attribute is equivalent to column and is used for
-   historical reasons.
-  </para>
-
-  <table>
-   <title><structname>pg_attribute</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>attrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The table this column belongs to</entry>
-     </row>
-
-     <row>
-      <entry><structfield>attname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>The column name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>atttypid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>The data type of this column</entry>
-     </row>
-
-     <row>
-      <entry><structfield>attstattarget</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       <structfield>attstattarget</structfield> controls the level of detail
-       of statistics accumulated for this column by
-       <xref linkend="sql-analyze">.
-       A zero value indicates that no statistics should be collected.
-       A negative value says to use the system default statistics target.
-       The exact meaning of positive values is data type-dependent.
-       For scalar data types, <structfield>attstattarget</structfield>
-       is both the target number of <quote>most common values</quote>
-       to collect, and the target number of histogram bins to create.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attlen</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       A copy of <literal>pg_type.typlen</literal> of this column's
-       type
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attnum</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       The number of the column.  Ordinary columns are numbered from 1
-       up.  System columns, such as <structfield>oid</structfield>,
-       have (arbitrary) negative numbers.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attndims</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       Number of dimensions, if the column is an array type; otherwise 0.
-       (Presently, the number of dimensions of an array is not enforced,
-       so any nonzero value effectively means <quote>it's an array</>.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attcacheoff</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       Always -1 in storage, but when loaded into a row descriptor
-       in memory this might be updated to cache the offset of the attribute
-       within the row
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>atttypmod</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       <structfield>atttypmod</structfield> records type-specific data
-       supplied at table creation time (for example, the maximum
-       length of a <type>varchar</type> column).  It is passed to
-       type-specific input functions and length coercion functions.
-       The value will generally be -1 for types that do not need <structfield>atttypmod</>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attbyval</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       A copy of <literal>pg_type.typbyval</> of this column's type
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attstorage</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       Normally a copy of <literal>pg_type.typstorage</> of this
-       column's type.  For TOAST-able data types, this can be altered
-       after column creation to control storage policy.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attalign</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       A copy of <literal>pg_type.typalign</> of this column's type
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attnotnull</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       This represents a not-null constraint.  It is possible to
-       change this column to enable or disable the constraint.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>atthasdef</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       This column has a default value, in which case there will be a
-       corresponding entry in the <structname>pg_attrdef</structname>
-       catalog that actually defines the value.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attisdropped</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       This column has been dropped and is no longer valid.  A dropped
-       column is still physically present in the table, but is
-       ignored by the parser and so cannot be accessed via SQL.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attislocal</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       This column is defined locally in the relation.  Note that a column can
-       be locally defined and inherited simultaneously.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attinhcount</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       The number of direct ancestors this column has.  A column with a
-       nonzero number of ancestors cannot be dropped nor renamed.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attcollation</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-collation"><structname>pg_collation</structname></link>.oid</literal></entry>
-      <entry>
-       The defined collation of the column, or zero if the column is
-       not of a collatable data type.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Column-level access privileges, if any have been granted specifically
-       on this column
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>attoptions</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>
-       Attribute-level options, as <quote>keyword=value</> strings
-      </entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   In a dropped column's <structname>pg_attribute</structname> entry,
-   <structfield>atttypid</structfield> is reset to zero, but
-   <structfield>attlen</structfield> and the other fields copied from
-   <structname>pg_type</> are still valid.  This arrangement is needed
-   to cope with the situation where the dropped column's data type was
-   later dropped, and so there is no <structname>pg_type</> row anymore.
-   <structfield>attlen</structfield> and the other fields can be used
-   to interpret the contents of a row of the table.
-  </para>
- </sect1>
-
-
- <sect1 id="catalog-pg-authid">
-  <title><structname>pg_authid</structname></title>
-
-  <indexterm zone="catalog-pg-authid">
-   <primary>pg_authid</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_authid</structname> contains information about
-   database authorization identifiers (roles).  A role subsumes the concepts
-   of <quote>users</> and <quote>groups</>.  A user is essentially just a
-   role with the <structfield>rolcanlogin</> flag set.  Any role (with or
-   without <structfield>rolcanlogin</>) can have other roles as members; see
-   <link linkend="catalog-pg-auth-members"><structname>pg_auth_members</structname></link>.
-  </para>
-
-  <para>
-   Since this catalog contains passwords, it must not be publicly readable.
-   <link linkend="view-pg-roles"><structname>pg_roles</structname></link>
-   is a publicly readable view on
-   <structname>pg_authid</structname> that blanks out the password field.
-  </para>
-
-  <para>
-   <xref linkend="user-manag"> contains detailed information about user and
-   privilege management.
-  </para>
-
-  <para>
-   Because user identities are cluster-wide,
-   <structname>pg_authid</structname>
-   is shared across all databases of a cluster: there is only one
-   copy of <structname>pg_authid</structname> per cluster, not
-   one per database.
-  </para>
-
-  <table>
-   <title><structname>pg_authid</> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>rolname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry>Role name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolsuper</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>Role has superuser privileges</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolinherit</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>Role automatically inherits privileges of roles it is a
-       member of</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolcreaterole</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>Role can create more roles</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolcreatedb</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>Role can create databases</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolcatupdate</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>
-       Role can update system catalogs directly.  (Even a superuser cannot do
-       this unless this column is true)
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolcanlogin</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>
-       Role can log in. That is, this role can be given as the initial
-       session authorization identifier.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolreplication</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>
-       Role is a replication role. That is, this role can initiate streaming
-       replication (see <xref linkend="streaming-replication">) and set/unset
-       the system backup mode using <function>pg_start_backup</> and
-       <function>pg_stop_backup</>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolconnlimit</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry>
-       For roles that can log in, this sets maximum number of concurrent
-       connections this role can make.  -1 means no limit.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolpassword</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>
-       Password (possibly encrypted); null if none.  If the password
-       is encrypted, this column will begin with the string <literal>md5</>
-       followed by a 32-character hexadecimal MD5 hash.  The MD5 hash
-       will be of the user's password concatenated to their user name.
-       For example, if user <literal>joe</> has password <literal>xyzzy</>,
-       <productname>PostgreSQL</> will store the md5 hash of
-       <literal>xyzzyjoe</>.  A password that does not follow that
-       format is assumed to be unencrypted.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolvaliduntil</structfield></entry>
-      <entry><type>timestamptz</type></entry>
-      <entry>Password expiry time (only used for password authentication);
-       null if no expiration</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-auth-members">
-  <title><structname>pg_auth_members</structname></title>
-
-  <indexterm zone="catalog-pg-auth-members">
-   <primary>pg_auth_members</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_auth_members</structname> shows the membership
-   relations between roles.  Any non-circular set of relationships is allowed.
-  </para>
-
-  <para>
-   Because user identities are cluster-wide,
-   <structname>pg_auth_members</structname>
-   is shared across all databases of a cluster: there is only one
-   copy of <structname>pg_auth_members</structname> per cluster, not
-   one per database.
-  </para>
-
-  <table>
-   <title><structname>pg_auth_members</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>roleid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>ID of a role that has a member</entry>
-     </row>
-
-     <row>
-      <entry><structfield>member</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>ID of a role that is a member of <structfield>roleid</></entry>
-     </row>
-
-     <row>
-      <entry><structfield>grantor</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>ID of the role that granted this membership</entry>
-     </row>
-
-     <row>
-      <entry><structfield>admin_option</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if <structfield>member</> can grant membership in
-       <structfield>roleid</> to others</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-cast">
-  <title><structname>pg_cast</structname></title>
-
-  <indexterm zone="catalog-pg-cast">
-   <primary>pg_cast</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_cast</structname> stores data type conversion
-   paths, both built-in paths and those defined with
-   <xref linkend="sql-createcast">.
-  </para>
-
-  <para>
-   It should be noted that <structname>pg_cast</structname> does not represent
-   every type conversion that the system knows how to perform; only those that
-   cannot be deduced from some generic rule.  For example, casting between a
-   domain and its base type is not explicitly represented in
-   <structname>pg_cast</structname>.  Another important exception is that
-   <quote>automatic I/O conversion casts</>, those performed using a data
-   type's own I/O functions to convert to or from <type>text</> or other
-   string types, are not explicitly represented in
-   <structname>pg_cast</structname>.
-  </para>
-
-  <table>
-   <title><structname>pg_cast</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>castsource</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>OID of the source data type</entry>
-     </row>
-
-     <row>
-      <entry><structfield>casttarget</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>OID of the target data type</entry>
-     </row>
-
-     <row>
-      <entry><structfield>castfunc</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the function to use to perform this cast.  Zero is
-       stored if the cast method doesn't require a function.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>castcontext</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       Indicates what contexts the cast can be invoked in.
-       <literal>e</> means only as an explicit cast (using
-       <literal>CAST</> or <literal>::</> syntax).
-       <literal>a</> means implicitly in assignment
-       to a target column, as well as explicitly.
-       <literal>i</> means implicitly in expressions, as well as the
-       other cases.
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>castmethod</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       Indicates how the cast is performed.
-       <literal>f</> means that the function specified in the <structfield>castfunc</> field is used.
-       <literal>i</> means that the input/output functions are used.
-       <literal>b</> means that the types are binary-coercible, thus no conversion is required.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The cast functions listed in <structname>pg_cast</structname> must
-   always take the cast source type as their first argument type, and
-   return the cast destination type as their result type.  A cast
-   function can have up to three arguments.  The second argument,
-   if present, must be type <type>integer</>; it receives the type
-   modifier associated with the destination type, or -1
-   if there is none.  The third argument,
-   if present, must be type <type>boolean</>; it receives <literal>true</>
-   if the cast is an explicit cast, <literal>false</> otherwise.
-  </para>
-
-  <para>
-   It is legitimate to create a <structname>pg_cast</structname> entry
-   in which the source and target types are the same, if the associated
-   function takes more than one argument.  Such entries represent
-   <quote>length coercion functions</> that coerce values of the type
-   to be legal for a particular type modifier value.
-  </para>
-
-  <para>
-   When a <structname>pg_cast</structname> entry has different source and
-   target types and a function that takes more than one argument, it
-   represents converting from one type to another and applying a length
-   coercion in a single step.  When no such entry is available, coercion
-   to a type that uses a type modifier involves two steps, one to
-   convert between data types and a second to apply the modifier.
-  </para>
- </sect1>
-
- <sect1 id="catalog-pg-class">
-  <title><structname>pg_class</structname></title>
-
-  <indexterm zone="catalog-pg-class">
-   <primary>pg_class</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_class</structname> catalogs tables and most
-   everything else that has columns or is otherwise similar to a
-   table.  This includes indexes (but see also
-   <structname>pg_index</structname>), sequences, views, composite types,
-   and TOAST tables; see <structfield>relkind</>.
-   Below, when we mean all of these
-   kinds of objects we speak of <quote>relations</quote>.  Not all
-   columns are meaningful for all relation types.
-  </para>
-
-  <table>
-   <title><structname>pg_class</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>relname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the table, index, view, etc.</entry>
-     </row>
-
-     <row>
-      <entry><structfield>relnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this relation
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>reltype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the data type that corresponds to this table's row type,
-       if any (zero for indexes, which have no <structname>pg_type</> entry)
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>reloftype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>
-       For typed tables, the OID of the underlying composite type,
-       zero for all other relations
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the relation</entry>
-     </row>
-
-     <row>
-      <entry><structfield>relam</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-am"><structname>pg_am</structname></link>.oid</literal></entry>
-      <entry>If this is an index, the access method used (B-tree, hash, etc.)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>relfilenode</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry></entry>
-      <entry>Name of the on-disk file of this relation; zero means this
-       is a <quote>mapped</> relation whose disk file name is determined
-       by low-level state</entry>
-     </row>
-
-     <row>
-      <entry><structfield>reltablespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-tablespace"><structname>pg_tablespace</structname></link>.oid</literal></entry>
-      <entry>
-       The tablespace in which this relation is stored.  If zero,
-       the database's default tablespace is implied.  (Not meaningful
-       if the relation has no on-disk file.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relpages</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       Size of the on-disk representation of this table in pages (of size
-       <symbol>BLCKSZ</symbol>).  This is only an estimate used by the
-       planner.  It is updated by <command>VACUUM</command>,
-       <command>ANALYZE</command>, and a few DDL commands such as
-       <command>CREATE INDEX</command>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>reltuples</structfield></entry>
-      <entry><type>float4</type></entry>
-      <entry></entry>
-      <entry>
-       Number of rows in the table.  This is only an estimate used by the
-       planner.  It is updated by <command>VACUUM</command>,
-       <command>ANALYZE</command>, and a few DDL commands such as
-       <command>CREATE INDEX</command>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>reltoastrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>
-       OID of the TOAST table associated with this table, 0 if none.  The
-       TOAST table stores large attributes <quote>out of line</quote> in a
-       secondary table.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>reltoastidxid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>
-       For a TOAST table, the OID of its index.  0 if not a TOAST table.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relhasindex</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       True if this is a table and it has (or recently had) any indexes
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relisshared</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       True if this table is shared across all databases in the cluster.  Only
-       certain system catalogs (such as <structname>pg_database</structname>)
-       are shared.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relpersistence</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       <literal>p</> = permanent table, <literal>u</> = unlogged table,
-       <literal>t</> = temporary table
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relkind</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       <literal>r</> = ordinary table, <literal>i</> = index,
-       <literal>S</> = sequence, <literal>v</> = view, <literal>c</> =
-       composite type, <literal>t</> = TOAST table,
-       <literal>f</> = foreign table
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relnatts</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       Number of user columns in the relation (system columns not
-       counted).  There must be this many corresponding entries in
-       <structname>pg_attribute</structname>.  See also
-       <literal>pg_attribute.attnum</literal>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relchecks</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       Number of <literal>CHECK</> constraints on the table; see
-       <link linkend="catalog-pg-constraint"><structname>pg_constraint</structname></link> catalog
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relhasoids</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       True if we generate an OID for each row of the relation
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relhaspkey</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       True if the table has (or once had) a primary key
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relhasrules</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       True if table has (or once had) rules; see
-       <link linkend="catalog-pg-rewrite"><structname>pg_rewrite</structname></link> catalog
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relhastriggers</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       True if table has (or once had) triggers; see
-       <link linkend="catalog-pg-trigger"><structname>pg_trigger</structname></link> catalog
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relhassubclass</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if table has (or once had) any inheritance children</entry>
-     </row>
-
-     <row>
-      <entry><structfield>relfrozenxid</structfield></entry>
-      <entry><type>xid</type></entry>
-      <entry></entry>
-      <entry>
-       All transaction IDs before this one have been replaced with a permanent
-       (<quote>frozen</>) transaction ID in this table.  This is used to track
-       whether the table needs to be vacuumed in order to prevent transaction
-       ID wraparound or to allow <literal>pg_clog</> to be shrunk.  Zero
-       (<symbol>InvalidTransactionId</symbol>) if the relation is not a table.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>relacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access privileges; see
-       <xref linkend="sql-grant"> and
-       <xref linkend="sql-revoke">
-       for details
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>reloptions</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access-method-specific options, as <quote>keyword=value</> strings
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Several of the Boolean flags in <structname>pg_class</> are maintained
-   lazily: they are guaranteed to be true if that's the correct state, but
-   may not be reset to false immediately when the condition is no longer
-   true.  For example, <structfield>relhasindex</> is set by
-   <command>CREATE INDEX</command>, but it is never cleared by
-   <command>DROP INDEX</command>.  Instead, <command>VACUUM</command> clears
-   <structfield>relhasindex</> if it finds the table has no indexes.  This
-   arrangement avoids race conditions and improves concurrency.
-  </para>
- </sect1>
-
- <sect1 id="catalog-pg-constraint">
-  <title><structname>pg_constraint</structname></title>
-
-  <indexterm zone="catalog-pg-constraint">
-   <primary>pg_constraint</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_constraint</structname> stores check, primary
-   key, unique, foreign key, and exclusion constraints on tables.
-   (Column constraints are not treated specially.  Every column constraint is
-   equivalent to some table constraint.)
-   Not-null constraints are represented in the <structname>pg_attribute</>
-   catalog, not here.
-  </para>
-
-  <para>
-   User-defined constraint triggers (created with <command>CREATE CONSTRAINT
-   TRIGGER</>) also give rise to an entry in this table.
-  </para>
-
-  <para>
-   Check constraints on domains are stored here, too.
-  </para>
-
-  <table>
-   <title><structname>pg_constraint</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>conname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Constraint name (not necessarily unique!)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>connamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this constraint
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>contype</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-        <literal>c</> = check constraint,
-        <literal>f</> = foreign key constraint,
-        <literal>p</> = primary key constraint,
-        <literal>u</> = unique constraint,
-        <literal>t</> = constraint trigger,
-        <literal>x</> = exclusion constraint
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>condeferrable</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Is the constraint deferrable?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>condeferred</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Is the constraint deferred by default?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>convalidated</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Has the constraint been validated? Can only be false for foreign keys</entry>
-     </row>
-
-     <row>
-      <entry><structfield>conrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The table this constraint is on; 0 if not a table constraint</entry>
-     </row>
-
-     <row>
-      <entry><structfield>contypid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>The domain this constraint is on; 0 if not a domain constraint</entry>
-     </row>
-
-     <row>
-      <entry><structfield>conindid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The index supporting this constraint, if it's a unique, primary
-       key, foreign key, or exclusion constraint; else 0</entry>
-     </row>
-
-     <row>
-      <entry><structfield>confrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>If a foreign key, the referenced table; else 0</entry>
-     </row>
-
-     <row>
-      <entry><structfield>confupdtype</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>Foreign key update action code:
-            <literal>a</> = no action,
-            <literal>r</> = restrict,
-            <literal>c</> = cascade,
-            <literal>n</> = set null,
-            <literal>d</> = set default
-          </entry>
-     </row>
-
-     <row>
-      <entry><structfield>confdeltype</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>Foreign key deletion action code:
-            <literal>a</> = no action,
-            <literal>r</> = restrict,
-            <literal>c</> = cascade,
-            <literal>n</> = set null,
-            <literal>d</> = set default
-          </entry>
-     </row>
-
-     <row>
-      <entry><structfield>confmatchtype</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>Foreign key match type:
-            <literal>f</> = full,
-            <literal>p</> = partial,
-            <literal>u</> = simple (unspecified)
-          </entry>
-     </row>
-
-     <row>
-      <entry><structfield>conislocal</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       This constraint is defined locally for the relation.  Note that a
-       constraint can be locally defined and inherited simultaneously.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>coninhcount</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       The number of direct inheritance ancestors this constraint has.
-       A constraint with
-       a nonzero number of ancestors cannot be dropped nor renamed.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>conkey</structfield></entry>
-      <entry><type>int2[]</type></entry>
-      <entry><literal><link linkend="catalog-pg-attribute"><structname>pg_attribute</structname></link>.attnum</></entry>
-      <entry>If a table constraint (including foreign keys, but not constraint
-       triggers), list of the constrained columns</entry>
-     </row>
-
-     <row>
-      <entry><structfield>confkey</structfield></entry>
-      <entry><type>int2[]</type></entry>
-      <entry><literal><link linkend="catalog-pg-attribute"><structname>pg_attribute</structname></link>.attnum</></entry>
-      <entry>If a foreign key, list of the referenced columns</entry>
-     </row>
-
-     <row>
-      <entry><structfield>conpfeqop</structfield></entry>
-      <entry><type>oid[]</type></entry>
-      <entry><literal><link linkend="catalog-pg-operator"><structname>pg_operator</structname></link>.oid</></entry>
-      <entry>If a foreign key, list of the equality operators for PK = FK comparisons</entry>
-     </row>
-
-     <row>
-      <entry><structfield>conppeqop</structfield></entry>
-      <entry><type>oid[]</type></entry>
-      <entry><literal><link linkend="catalog-pg-operator"><structname>pg_operator</structname></link>.oid</></entry>
-      <entry>If a foreign key, list of the equality operators for PK = PK comparisons</entry>
-     </row>
-
-     <row>
-      <entry><structfield>conffeqop</structfield></entry>
-      <entry><type>oid[]</type></entry>
-      <entry><literal><link linkend="catalog-pg-operator"><structname>pg_operator</structname></link>.oid</></entry>
-      <entry>If a foreign key, list of the equality operators for FK = FK comparisons</entry>
-     </row>
-
-     <row>
-      <entry><structfield>conexclop</structfield></entry>
-      <entry><type>oid[]</type></entry>
-      <entry><literal><link linkend="catalog-pg-operator"><structname>pg_operator</structname></link>.oid</></entry>
-      <entry>If an exclusion constraint, list of the per-column exclusion operators</entry>
-     </row>
-
-     <row>
-      <entry><structfield>conbin</structfield></entry>
-      <entry><type>pg_node_tree</type></entry>
-      <entry></entry>
-      <entry>If a check constraint, an internal representation of the expression</entry>
-     </row>
-
-     <row>
-      <entry><structfield>consrc</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>If a check constraint, a human-readable representation of the expression</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   In the case of an exclusion constraint, <structfield>conkey</structfield>
-   is only useful for constraint elements that are simple column references.
-   For other cases, a zero appears in <structfield>conkey</structfield>
-   and the associated index must be consulted to discover the expression
-   that is constrained.  (<structfield>conkey</structfield> thus has the
-   same contents as <structname>pg_index</>.<structfield>indkey</> for the
-   index.)
-  </para>
-
-  <note>
-   <para>
-    <structfield>consrc</structfield> is not updated when referenced objects
-    change; for example, it won't track renaming of columns.  Rather than
-    relying on this field, it's best to use <function>pg_get_constraintdef()</>
-    to extract the definition of a check constraint.
-   </para>
-  </note>
-
-  <note>
-   <para>
-    <literal>pg_class.relchecks</literal> needs to agree with the
-    number of check-constraint entries found in this table for each
-    relation.
-   </para>
-  </note>
-
- </sect1>
-
- <sect1 id="catalog-pg-collation">
-  <title><structname>pg_collation</structname></title>
-
-  <indexterm zone="catalog-pg-collation">
-   <primary>pg_collation</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_collation</structname> describes the
-   available collations, which are essentially mappings from an SQL
-   name to operating system locale categories.
-   See <xref linkend="collation"> for more information.
-  </para>
-
-  <table>
-   <title><structname>pg_collation</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>collname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Collation name (unique per namespace and encoding)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>collnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this collation
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>collowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the collation</entry>
-     </row>
-
-     <row>
-      <entry><structfield>collencoding</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>Encoding in which the collation is applicable, or -1 if it
-       works for any encoding</entry>
-     </row>
-
-     <row>
-      <entry><structfield>collcollate</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry><symbol>LC_COLLATE</> for this collation object</entry>
-     </row>
-
-     <row>
-      <entry><structfield>collctype</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry><symbol>LC_CTYPE</> for this collation object</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Note that the unique key on this catalog is (<structfield>collname</>,
-   <structfield>collencoding</>, <structfield>collnamespace</>) not just
-   (<structfield>collname</>, <structfield>collnamespace</>).
-   <productname>PostgreSQL</productname> generally ignores all
-   collations that do not have <structfield>collencoding</> equal to
-   either the current database's encoding or -1, and creation of new entries
-   with the same name as an entry with <structfield>collencoding</> = -1
-   is forbidden.  Therefore it is sufficient to use a qualified SQL name
-   (<replaceable>schema</>.<replaceable>name</>) to identify a collation,
-   even though this is not unique according to the catalog definition.
-   The reason for defining the catalog this way is that
-   <application>initdb</> fills it in at cluster initialization time with
-   entries for all locales available on the system, so it must be able to
-   hold entries for all encodings that might ever be used in the cluster.
-  </para>
-
-  <para>
-   In the <literal>template0</> database, it could be useful to create
-   collations whose encoding does not match the database encoding,
-   since they could match the encodings of databases later cloned from
-   <literal>template0</>.  This would currently have to be done manually.
-  </para>
- </sect1>
-
- <sect1 id="catalog-pg-conversion">
-  <title><structname>pg_conversion</structname></title>
-
-  <indexterm zone="catalog-pg-conversion">
-   <primary>pg_conversion</primary>
-  </indexterm>
-
-  <para>
-   The catalog <structname>pg_conversion</structname> describes
-   encoding conversion procedures.  See <xref linkend="sql-createconversion">
-   for more information.
-  </para>
-
-  <table>
-   <title><structname>pg_conversion</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>conname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Conversion name (unique within a namespace)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>connamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this conversion
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>conowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the conversion</entry>
-     </row>
-
-     <row>
-      <entry><structfield>conforencoding</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>Source encoding ID</entry>
-     </row>
-
-     <row>
-      <entry><structfield>contoencoding</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>Destination encoding ID</entry>
-     </row>
-
-     <row>
-      <entry><structfield>conproc</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Conversion procedure</entry>
-     </row>
-
-     <row>
-      <entry><structfield>condefault</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if this is the default conversion</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="catalog-pg-database">
-  <title><structname>pg_database</structname></title>
-
-  <indexterm zone="catalog-pg-database">
-   <primary>pg_database</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_database</structname> stores information about
-   the available databases.  Databases are created with the <xref
-   linkend="sql-createdatabase"> command.
-   Consult <xref linkend="managing-databases"> for details about the meaning
-   of some of the parameters.
-  </para>
-
-  <para>
-   Unlike most system catalogs, <structname>pg_database</structname>
-   is shared across all databases of a cluster: there is only one
-   copy of <structname>pg_database</structname> per cluster, not
-   one per database.
-  </para>
-
-  <table>
-   <title><structname>pg_database</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>datname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Database name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>datdba</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the database, usually the user who created it</entry>
-     </row>
-
-     <row>
-      <entry><structfield>encoding</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>Character encoding for this database
-          (<function>pg_encoding_to_char()</function> can translate
-           this number to the encoding name)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>datcollate</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>LC_COLLATE for this database</entry>
-     </row>
-
-     <row>
-      <entry><structfield>datctype</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>LC_CTYPE for this database</entry>
-     </row>
-
-     <row>
-      <entry><structfield>datistemplate</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       If true then this database can be used in the
-       <literal>TEMPLATE</literal> clause of <command>CREATE
-       DATABASE</command> to create a new database as a clone of
-       this one
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>datallowconn</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       If false then no one can connect to this database.  This is
-       used to protect the <literal>template0</> database from being altered.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>datconnlimit</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       Sets maximum number of concurrent connections that can be made
-       to this database.  -1 means no limit.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>datlastsysoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry></entry>
-      <entry>
-       Last system OID in the database; useful
-       particularly to <application>pg_dump</application>
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>datfrozenxid</structfield></entry>
-      <entry><type>xid</type></entry>
-      <entry></entry>
-      <entry>
-       All transaction IDs before this one have been replaced with a permanent
-       (<quote>frozen</>) transaction ID in this database.  This is used to
-       track whether the database needs to be vacuumed in order to prevent
-       transaction ID wraparound or to allow <literal>pg_clog</> to be shrunk.
-       It is the minimum of the per-table
-       <structname>pg_class</>.<structfield>relfrozenxid</> values.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>dattablespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-tablespace"><structname>pg_tablespace</structname></link>.oid</literal></entry>
-      <entry>
-       The default tablespace for the database.
-       Within this database, all tables for which
-       <structname>pg_class</>.<structfield>reltablespace</> is zero
-       will be stored in this tablespace; in particular, all the non-shared
-       system catalogs will be there.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>datacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access privileges; see
-       <xref linkend="sql-grant"> and
-       <xref linkend="sql-revoke">
-       for details
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-db-role-setting">
-  <title><structname>pg_db_role_setting</structname></title>
-
-  <indexterm zone="catalog-pg-db-role-setting">
-   <primary>pg_db_role_setting</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_db_role_setting</structname> records the default
-   values that have been set for run-time configuration variables,
-   for each role and database combination.
-  </para>
-
-  <para>
-   Unlike most system catalogs, <structname>pg_db_role_setting</structname>
-   is shared across all databases of a cluster: there is only one
-   copy of <structname>pg_db_role_setting</structname> per cluster, not
-   one per database.
-  </para>
-
-  <table>
-   <title><structname>pg_db_role_setting</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>setdatabase</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-database"><structname>pg_database</structname></link>.oid</literal></entry>
-      <entry>The OID of the database the setting is applicable to, or zero if not database-specific</entry>
-     </row>
-
-     <row>
-      <entry><structfield>setrole</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>The OID of the role the setting is applicable to, or zero if not role-specific</entry>
-     </row>
-
-     <row>
-      <entry><structfield>setconfig</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>Defaults for run-time configuration variables</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-default-acl">
-  <title><structname>pg_default_acl</structname></title>
-
-  <indexterm zone="catalog-pg-default-acl">
-   <primary>pg_default_acl</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_default_acl</> stores initial
-   privileges to be assigned to newly created objects.
-  </para>
-
-  <table>
-   <title><structname>pg_default_acl</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>defaclrole</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>The OID of the role associated with this entry</entry>
-     </row>
-
-     <row>
-      <entry><structfield>defaclnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>The OID of the namespace associated with this entry,
-       or 0 if none</entry>
-     </row>
-
-     <row>
-      <entry><structfield>defaclobjtype</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       Type of object this entry is for:
-       <literal>r</> = relation (table, view),
-       <literal>S</> = sequence,
-       <literal>f</> = function
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>defaclacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access privileges that this type of object should have on creation
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   A <structname>pg_default_acl</> entry shows the initial privileges to
-   be assigned to an object belonging to the indicated user.  There are
-   currently two types of entry: <quote>global</> entries with
-   <structfield>defaclnamespace</> = 0, and <quote>per-schema</> entries
-   that reference a particular schema.  If a global entry is present then
-   it <emphasis>overrides</> the normal hard-wired default privileges
-   for the object type.  A per-schema entry, if present, represents privileges
-   to be <emphasis>added to</> the global or hard-wired default privileges.
-  </para>
-
-  <para>
-   Note that when an ACL entry in another catalog is null, it is taken
-   to represent the hard-wired default privileges for its object,
-   <emphasis>not</> whatever might be in <structname>pg_default_acl</>
-   at the moment.  <structname>pg_default_acl</> is only consulted during
-   object creation.
-  </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-depend">
-  <title><structname>pg_depend</structname></title>
-
-  <indexterm zone="catalog-pg-depend">
-   <primary>pg_depend</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_depend</structname> records the dependency
-   relationships between database objects.  This information allows
-   <command>DROP</> commands to find which other objects must be dropped
-   by <command>DROP CASCADE</> or prevent dropping in the <command>DROP
-   RESTRICT</> case.
-  </para>
-
-  <para>
-   See also <link linkend="catalog-pg-shdepend"><structname>pg_shdepend</structname></link>,
-   which performs a similar function for dependencies involving objects
-   that are shared across a database cluster.
-  </para>
-
-  <table>
-   <title><structname>pg_depend</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>classid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The OID of the system catalog the dependent object is in</entry>
-     </row>
-
-     <row>
-      <entry><structfield>objid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry>any OID column</entry>
-      <entry>The OID of the specific dependent object</entry>
-     </row>
-
-     <row>
-      <entry><structfield>objsubid</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       For a table column, this is the column number (the
-       <structfield>objid</> and <structfield>classid</> refer to the
-       table itself).  For all other object types, this column is
-       zero.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>refclassid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The OID of the system catalog the referenced object is in</entry>
-     </row>
-
-     <row>
-      <entry><structfield>refobjid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry>any OID column</entry>
-      <entry>The OID of the specific referenced object</entry>
-     </row>
-
-     <row>
-      <entry><structfield>refobjsubid</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       For a table column, this is the column number (the
-       <structfield>refobjid</> and <structfield>refclassid</> refer
-       to the table itself).  For all other object types, this column
-       is zero.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>deptype</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       A code defining the specific semantics of this dependency relationship; see text
-      </entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   In all cases, a <structname>pg_depend</structname> entry indicates that the
-   referenced object cannot be dropped without also dropping the dependent
-   object.  However, there are several subflavors identified by
-   <structfield>deptype</>:
-
-   <variablelist>
-    <varlistentry>
-     <term><symbol>DEPENDENCY_NORMAL</> (<literal>n</>)</term>
-     <listitem>
-      <para>
-       A normal relationship between separately-created objects.  The
-       dependent object can be dropped without affecting the
-       referenced object.  The referenced object can only be dropped
-       by specifying <literal>CASCADE</>, in which case the dependent
-       object is dropped, too.  Example: a table column has a normal
-       dependency on its data type.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>DEPENDENCY_AUTO</> (<literal>a</>)</term>
-     <listitem>
-      <para>
-       The dependent object can be dropped separately from the
-       referenced object, and should be automatically dropped
-       (regardless of <literal>RESTRICT</> or <literal>CASCADE</>
-       mode) if the referenced object is dropped.  Example: a named
-       constraint on a table is made autodependent on the table, so
-       that it will go away if the table is dropped.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>DEPENDENCY_INTERNAL</> (<literal>i</>)</term>
-     <listitem>
-      <para>
-       The dependent object was created as part of creation of the
-       referenced object, and is really just a part of its internal
-       implementation.  A <command>DROP</> of the dependent object
-       will be disallowed outright (we'll tell the user to issue a
-       <command>DROP</> against the referenced object, instead).  A
-       <command>DROP</> of the referenced object will be propagated
-       through to drop the dependent object whether
-       <command>CASCADE</> is specified or not.  Example: a trigger
-       that's created to enforce a foreign-key constraint is made
-       internally dependent on the constraint's
-       <structname>pg_constraint</> entry.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>DEPENDENCY_EXTENSION</> (<literal>e</>)</term>
-     <listitem>
-      <para>
-       The dependent object is a member of the <firstterm>extension</> that is
-       the referenced object (see
-       <link linkend="catalog-pg-extension"><structname>pg_extension</structname></link>).
-       The dependent object can be dropped only via
-       <command>DROP EXTENSION</> on the referenced object.  Functionally
-       this dependency type acts the same as an internal dependency, but
-       it's kept separate for clarity and to simplify <application>pg_dump</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>DEPENDENCY_PIN</> (<literal>p</>)</term>
-     <listitem>
-      <para>
-       There is no dependent object; this type of entry is a signal
-       that the system itself depends on the referenced object, and so
-       that object must never be deleted.  Entries of this type are
-       created only by <command>initdb</command>.  The columns for the
-       dependent object contain zeroes.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-   Other dependency flavors might be needed in future.
-  </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-description">
-  <title><structname>pg_description</structname></title>
-
-  <indexterm zone="catalog-pg-description">
-   <primary>pg_description</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_description</> stores optional descriptions
-   (comments) for each database object.  Descriptions can be manipulated
-   with the <xref linkend="sql-comment"> command and viewed with
-   <application>psql</application>'s <literal>\d</literal> commands.
-   Descriptions of many built-in system objects are provided in the initial
-   contents of <structname>pg_description</structname>.
-  </para>
-
-  <para>
-   See also <link linkend="catalog-pg-shdescription"><structname>pg_shdescription</structname></link>,
-   which performs a similar function for descriptions involving objects that
-   are shared across a database cluster.
-  </para>
-
-  <table>
-   <title><structname>pg_description</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>objoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry>any OID column</entry>
-      <entry>The OID of the object this description pertains to</entry>
-     </row>
-
-     <row>
-      <entry><structfield>classoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The OID of the system catalog this object appears in</entry>
-     </row>
-
-     <row>
-      <entry><structfield>objsubid</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       For a comment on a table column, this is the column number (the
-       <structfield>objoid</> and <structfield>classoid</> refer to
-       the table itself).  For all other object types, this column is
-       zero.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>description</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Arbitrary text that serves as the description of this object</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-enum">
-  <title><structname>pg_enum</structname></title>
-
-  <indexterm zone="catalog-pg-enum">
-   <primary>pg_enum</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The <structname>pg_enum</structname> catalog contains entries
-   showing the values and labels for each enum type. The
-   internal representation of a given enum value is actually the OID
-   of its associated row in <structname>pg_enum</structname>.
-  </para>
-
-  <table>
-   <title><structname>pg_enum</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>enumtypid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>The OID of the <structname>pg_type</> entry owning this enum value</entry>
-     </row>
-
-     <row>
-      <entry><structfield>enumsortorder</structfield></entry>
-      <entry><type>float4</type></entry>
-      <entry></entry>
-      <entry>The sort position of this enum value within its enum type</entry>
-     </row>
-
-     <row>
-      <entry><structfield>enumlabel</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>The textual label for this enum value</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The OIDs for <structname>pg_enum</structname> rows follow a special
-   rule: even-numbered OIDs are guaranteed to be ordered in the same way
-   as the sort ordering of their enum type.  That is, if two even OIDs
-   belong to the same enum type, the smaller OID must have the smaller
-   <structfield>enumsortorder</structfield> value.  Odd-numbered OID values
-   need bear no relationship to the sort order.  This rule allows the
-   enum comparison routines to avoid catalog lookups in many common cases.
-   The routines that create and alter enum types attempt to assign even
-   OIDs to enum values whenever possible.
-  </para>
-
-  <para>
-   When an enum type is created, its members are assigned sort-order
-   positions 1..<replaceable>n</>.  But members added later might be given
-   negative or fractional values of <structfield>enumsortorder</structfield>.
-   The only requirement on these values is that they be correctly
-   ordered and unique within each enum type.
-  </para>
- </sect1>
-
-
- <sect1 id="catalog-pg-extension">
-  <title><structname>pg_extension</structname></title>
-
-  <indexterm zone="catalog-pg-extension">
-   <primary>pg_extension</primary>
-  </indexterm>
-
-  <para>
-   The catalog <structname>pg_extension</structname> stores information
-   about the installed extensions.  See <xref linkend="extend-extensions">
-   for details about extensions.
-  </para>
-
-  <table>
-   <title><structname>pg_extension</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>extname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the extension</entry>
-     </row>
-
-     <row>
-      <entry><structfield>extowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the extension</entry>
-     </row>
-
-     <row>
-      <entry><structfield>extnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>Schema containing the extension's exported objects</entry>
-     </row>
-
-     <row>
-      <entry><structfield>extrelocatable</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if extension can be relocated to another schema</entry>
-     </row>
-
-     <row>
-      <entry><structfield>extversion</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Version name for the extension</entry>
-     </row>
-
-     <row>
-      <entry><structfield>extconfig</structfield></entry>
-      <entry><type>oid[]</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>Array of <type>regclass</> OIDs for the extension's configuration
-       table(s), or <literal>NULL</> if none</entry>
-     </row>
-
-     <row>
-      <entry><structfield>extcondition</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>Array of <literal>WHERE</>-clause filter conditions for the
-       extension's configuration table(s), or <literal>NULL</> if none</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Note that unlike most catalogs with a <quote>namespace</> column,
-   <structfield>extnamespace</structfield> is not meant to imply
-   that the extension belongs to that schema.  Extension names are never
-   schema-qualified.  Rather, <structfield>extnamespace</structfield>
-   indicates the schema that contains most or all of the extension's
-   objects.  If <structfield>extrelocatable</structfield> is true, then
-   this schema must in fact contain all schema-qualifiable objects
-   belonging to the extension.
-  </para>
- </sect1>
-
-
- <sect1 id="catalog-pg-foreign-data-wrapper">
-  <title><structname>pg_foreign_data_wrapper</structname></title>
-
-  <indexterm zone="catalog-pg-foreign-data-wrapper">
-   <primary>pg_foreign_data_wrapper</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_foreign_data_wrapper</structname> stores
-   foreign-data wrapper definitions.  A foreign-data wrapper is the
-   mechanism by which external data, residing on foreign servers, is
-   accessed.
-  </para>
-
-  <table>
-   <title><structname>pg_foreign_data_wrapper</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>fdwname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the foreign-data wrapper</entry>
-     </row>
-
-     <row>
-      <entry><structfield>fdwowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the foreign-data wrapper</entry>
-     </row>
-
-     <row>
-      <entry><structfield>fdwhandler</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>
-       References a handler function that is responsible for
-       supplying execution routines for the foreign-data wrapper.
-       Zero if no handler is provided
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>fdwvalidator</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>
-       References a validator function that is responsible for
-       checking the validity of the options given to the
-       foreign-data wrapper, as well as options for foreign servers and user
-       mappings using the foreign-data wrapper.  Zero if no validator
-       is provided
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>fdwacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access privileges; see
-       <xref linkend="sql-grant"> and
-       <xref linkend="sql-revoke">
-       for details
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>fdwoptions</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>
-       Foreign-data wrapper specific options, as <quote>keyword=value</> strings
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-foreign-server">
-  <title><structname>pg_foreign_server</structname></title>
-
-  <indexterm zone="catalog-pg-foreign-server">
-   <primary>pg_foreign_server</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_foreign_server</structname> stores
-   foreign server definitions.  A foreign server describes a source
-   of external data, such as a remote server.  Foreign
-   servers are accessed via foreign-data wrappers.
-  </para>
-
-  <table>
-   <title><structname>pg_foreign_server</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>srvname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the foreign server</entry>
-     </row>
-
-     <row>
-      <entry><structfield>srvowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the foreign server</entry>
-     </row>
-
-     <row>
-      <entry><structfield>srvfdw</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-foreign-data-wrapper"><structname>pg_foreign_data_wrapper</structname></link>.oid</literal></entry>
-      <entry>OID of the foreign-data wrapper of this foreign server</entry>
-     </row>
-
-     <row>
-      <entry><structfield>srvtype</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Type of the server (optional)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>srvversion</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Version of the server (optional)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>srvacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access privileges; see
-       <xref linkend="sql-grant"> and
-       <xref linkend="sql-revoke">
-       for details
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>srvoptions</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>
-       Foreign server specific options, as <quote>keyword=value</> strings
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-foreign-table">
-  <title><structname>pg_foreign_table</structname></title>
-
-  <indexterm zone="catalog-pg-foreign-table">
-   <primary>pg_foreign_table</primary>
-  </indexterm>
-
-  <para>
-   The catalog <structname>pg_foreign_table</structname> contains
-   auxiliary information about foreign tables.  A foreign table is
-   primarily represented by a <structname>pg_class</structname> entry,
-   just like a regular table.  Its <structname>pg_foreign_table</structname>
-   entry contains the information that is pertinent only to foreign tables
-   and not any other kind of relation.
-  </para>
-
-  <table>
-   <title><structname>pg_foreign_table</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>ftrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>OID of the <structname>pg_class</> entry for this foreign table</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ftserver</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-foreign-server"><structname>pg_foreign_server</structname></link>.oid</literal></entry>
-      <entry>OID of the foreign server for this foreign table</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ftoptions</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>
-       Foreign table options, as <quote>keyword=value</> strings
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-index">
-  <title><structname>pg_index</structname></title>
-
-  <indexterm zone="catalog-pg-index">
-   <primary>pg_index</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_index</structname> contains part of the information
-   about indexes.  The rest is mostly in
-   <structname>pg_class</structname>.
-  </para>
-
-  <table>
-   <title><structname>pg_index</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>indexrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The OID of the <structname>pg_class</> entry for this index</entry>
-     </row>
-
-     <row>
-      <entry><structfield>indrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The OID of the <structname>pg_class</> entry for the table this index is for</entry>
-     </row>
-
-     <row>
-      <entry><structfield>indnatts</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>The number of columns in the index (duplicates
-      <literal>pg_class.relnatts</literal>)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>indisunique</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>If true, this is a unique index</entry>
-     </row>
-
-     <row>
-      <entry><structfield>indisprimary</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>If true, this index represents the primary key of the table
-      (<structfield>indisunique</> should always be true when this is true)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>indisexclusion</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>If true, this index supports an exclusion constraint</entry>
-     </row>
-
-     <row>
-      <entry><structfield>indimmediate</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>If true, the uniqueness check is enforced immediately on
-       insertion
-       (irrelevant if <structfield>indisunique</> is not true)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>indisclustered</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>If true, the table was last clustered on this index</entry>
-     </row>
-
-     <row>
-      <entry><structfield>indisvalid</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       If true, the index is currently valid for queries.  False means the
-       index is possibly incomplete: it must still be modified by
-       <command>INSERT</>/<command>UPDATE</> operations, but it cannot safely
-       be used for queries. If it is unique, the uniqueness property is not
-       true either.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>indcheckxmin</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       If true, queries must not use the index until the <structfield>xmin</>
-       of this <structname>pg_index</> row is below their <symbol>TransactionXmin</symbol>
-       event horizon, because the table may contain broken HOT chains with
-       incompatible rows that they can see
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>indisready</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       If true, the index is currently ready for inserts.  False means the
-       index must be ignored by <command>INSERT</>/<command>UPDATE</>
-       operations.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>indkey</structfield></entry>
-      <entry><type>int2vector</type></entry>
-      <entry><literal><link linkend="catalog-pg-attribute"><structname>pg_attribute</structname></link>.attnum</literal></entry>
-      <entry>
-       This is an array of <structfield>indnatts</structfield> values that
-       indicate which table columns this index indexes.  For example a value
-       of <literal>1 3</literal> would mean that the first and the third table
-       columns make up the index key.  A zero in this array indicates that the
-       corresponding index attribute is an expression over the table columns,
-       rather than a simple column reference.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>indcollation</structfield></entry>
-      <entry><type>oidvector</type></entry>
-      <entry><literal><link linkend="catalog-pg-collation"><structname>pg_collation</structname></link>.oid</literal></entry>
-      <entry>
-       For each column in the index key, this contains the OID of the
-       collation to use for the index.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>indclass</structfield></entry>
-      <entry><type>oidvector</type></entry>
-      <entry><literal><link linkend="catalog-pg-opclass"><structname>pg_opclass</structname></link>.oid</literal></entry>
-      <entry>
-       For each column in the index key, this contains the OID of
-       the operator class to use.  See
-       <link linkend="catalog-pg-opclass"><structname>pg_opclass</structname></link> for details.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>indoption</structfield></entry>
-      <entry><type>int2vector</type></entry>
-      <entry></entry>
-      <entry>
-       This is an array of <structfield>indnatts</structfield> values that
-       store per-column flag bits.  The meaning of the bits is defined by
-       the index's access method.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>indexprs</structfield></entry>
-      <entry><type>pg_node_tree</type></entry>
-      <entry></entry>
-      <entry>
-       Expression trees (in <function>nodeToString()</function>
-       representation) for index attributes that are not simple column
-       references.  This is a list with one element for each zero
-       entry in <structfield>indkey</>.  Null if all index attributes
-       are simple references.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>indpred</structfield></entry>
-      <entry><type>pg_node_tree</type></entry>
-      <entry></entry>
-      <entry>
-       Expression tree (in <function>nodeToString()</function>
-       representation) for partial index predicate.  Null if not a
-       partial index.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-inherits">
-  <title><structname>pg_inherits</structname></title>
-
-  <indexterm zone="catalog-pg-inherits">
-   <primary>pg_inherits</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_inherits</> records information about
-   table inheritance hierarchies.  There is one entry for each direct
-   child table in the database.  (Indirect inheritance can be determined
-   by following chains of entries.)
-  </para>
-
-  <table>
-   <title><structname>pg_inherits</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>inhrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the child table
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>inhparent</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the parent table
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>inhseqno</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       If there is more than one direct parent for a child table (multiple
-       inheritance), this number tells the order in which the
-       inherited columns are to be arranged.  The count starts at 1.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-language">
-  <title><structname>pg_language</structname></title>
-
-  <indexterm zone="catalog-pg-language">
-   <primary>pg_language</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_language</structname> registers
-   languages in which you can write functions or stored procedures.
-   See <xref linkend="sql-createlanguage">
-   and <xref linkend="xplang"> for more information about language handlers.
-  </para>
-
-  <table>
-   <title><structname>pg_language</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>lanname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the language</entry>
-     </row>
-
-     <row>
-      <entry><structfield>lanowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the language</entry>
-     </row>
-
-     <row>
-      <entry><structfield>lanispl</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       This is false for internal languages (such as
-       <acronym>SQL</acronym>) and true for user-defined languages.
-       Currently, <application>pg_dump</application> still uses this
-       to determine which languages need to be dumped, but this might be
-       replaced by a different mechanism in the future.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>lanpltrusted</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       True if this is a trusted language, which means that it is believed
-       not to grant access to anything outside the normal SQL execution
-       environment.  Only superusers can create functions in untrusted
-       languages.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>lanplcallfoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>
-       For noninternal languages this references the language
-       handler, which is a special function that is responsible for
-       executing all functions that are written in the particular
-       language
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>laninline</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>
-       This references a function that is responsible for executing
-       <quote>inline</> anonymous code blocks
-       (<xref linkend="sql-do"> blocks).
-       Zero if inline blocks are not supported.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>lanvalidator</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>
-       This references a language validator function that is responsible
-       for checking the syntax and validity of new functions when they
-       are created.  Zero if no validator is provided.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>lanacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access privileges; see
-       <xref linkend="sql-grant"> and
-       <xref linkend="sql-revoke">
-       for details
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-largeobject">
-  <title><structname>pg_largeobject</structname></title>
-
-  <indexterm zone="catalog-pg-largeobject">
-   <primary>pg_largeobject</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_largeobject</structname> holds the data making up
-   <quote>large objects</quote>.  A large object is identified by an OID
-   assigned when it is created.  Each large object is broken into
-   segments or <quote>pages</> small enough to be conveniently stored as rows
-   in <structname>pg_largeobject</structname>.
-   The amount of data per page is defined to be <symbol>LOBLKSIZE</> (which is currently
-   <literal>BLCKSZ/4</>, or typically 2 kB).
-  </para>
-
-  <para>
-   Prior to <productname>PostgreSQL</> 9.0, there was no permission structure
-   associated with large objects.  As a result,
-   <structname>pg_largeobject</structname> was publicly readable and could be
-   used to obtain the OIDs (and contents) of all large objects in the system.
-   This is no longer the case; use
-   <link linkend="catalog-pg-largeobject-metadata"><structname>pg_largeobject_metadata</></link>
-   to obtain a list of large object OIDs.
-  </para>
-
-  <table>
-   <title><structname>pg_largeobject</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>loid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-largeobject-metadata"><structname>pg_largeobject_metadata</structname></link>.oid</literal></entry>
-      <entry>Identifier of the large object that includes this page</entry>
-     </row>
-
-     <row>
-      <entry><structfield>pageno</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>Page number of this page within its large object
-      (counting from zero)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>data</structfield></entry>
-      <entry><type>bytea</type></entry>
-      <entry></entry>
-      <entry>
-       Actual data stored in the large object.
-       This will never be more than <symbol>LOBLKSIZE</> bytes and might be less.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Each row of <structname>pg_largeobject</structname> holds data
-   for one page of a large object, beginning at
-   byte offset (<literal>pageno * LOBLKSIZE</>) within the object.  The implementation
-   allows sparse storage: pages might be missing, and might be shorter than
-   <literal>LOBLKSIZE</> bytes even if they are not the last page of the object.
-   Missing regions within a large object read as zeroes.
-  </para>
-
- </sect1>
-
- <sect1 id="catalog-pg-largeobject-metadata">
-  <title><structname>pg_largeobject_metadata</structname></title>
-
-  <indexterm zone="catalog-pg-largeobject-metadata">
-   <primary>pg_largeobject_metadata</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_largeobject_metadata</structname>
-   holds metadata associated with large objects.  The actual large object
-   data is stored in
-   <link linkend="catalog-pg-largeobject"><structname>pg_largeobject</></link>.
-  </para>
-
-  <table>
-   <title><structname>pg_largeobject_metadata</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>lomowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the large object</entry>
-     </row>
-
-     <row>
-      <entry><structfield>lomacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access privileges; see
-       <xref linkend="sql-grant"> and
-       <xref linkend="sql-revoke">
-       for details
-      </entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="catalog-pg-namespace">
-  <title><structname>pg_namespace</structname></title>
-
-  <indexterm zone="catalog-pg-namespace">
-   <primary>pg_namespace</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_namespace</> stores namespaces.
-   A namespace is the structure underlying SQL schemas: each namespace
-   can have a separate collection of relations, types, etc. without name
-   conflicts.
-  </para>
-
-  <table>
-   <title><structname>pg_namespace</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>nspname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the namespace</entry>
-     </row>
-
-     <row>
-      <entry><structfield>nspowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the namespace</entry>
-     </row>
-
-     <row>
-      <entry><structfield>nspacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access privileges; see
-       <xref linkend="sql-grant"> and
-       <xref linkend="sql-revoke">
-       for details
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-opclass">
-  <title><structname>pg_opclass</structname></title>
-
-  <indexterm zone="catalog-pg-opclass">
-   <primary>pg_opclass</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_opclass</structname> defines
-   index access method operator classes.  Each operator class defines
-   semantics for index columns of a particular data type and a particular
-   index access method.  An operator class essentially specifies that a
-   particular operator family is applicable to a particular indexable column
-   data type.  The set of operators from the family that are actually usable
-   with the indexed column are whichever ones accept the column's data type
-   as their lefthand input.
-  </para>
-
-  <para>
-   Operator classes are described at length in <xref linkend="xindex">.
-  </para>
-
-  <table>
-   <title><structname>pg_opclass</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-
-     <row>
-      <entry><structfield>opcmethod</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-am"><structname>pg_am</structname></link>.oid</literal></entry>
-      <entry>Index access method operator class is for</entry>
-     </row>
-
-     <row>
-      <entry><structfield>opcname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of this operator class</entry>
-     </row>
-
-     <row>
-      <entry><structfield>opcnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>Namespace of this operator class</entry>
-     </row>
-
-     <row>
-      <entry><structfield>opcowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the operator class</entry>
-     </row>
-
-     <row>
-      <entry><structfield>opcfamily</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-opfamily"><structname>pg_opfamily</structname></link>.oid</literal></entry>
-      <entry>Operator family containing the operator class</entry>
-     </row>
-
-     <row>
-      <entry><structfield>opcintype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Data type that the operator class indexes</entry>
-     </row>
-
-     <row>
-      <entry><structfield>opcdefault</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if this operator class is the default for <structfield>opcintype</></entry>
-     </row>
-
-     <row>
-      <entry><structfield>opckeytype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Type of data stored in index, or zero if same as <structfield>opcintype</></entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   An operator class's <structfield>opcmethod</> must match the
-   <structname>opfmethod</> of its containing operator family.
-   Also, there must be no more than one <structname>pg_opclass</structname>
-   row having <structname>opcdefault</> true for any given combination of
-   <structname>opcmethod</> and <structname>opcintype</>.
-  </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-operator">
-  <title><structname>pg_operator</structname></title>
-
-  <indexterm zone="catalog-pg-operator">
-   <primary>pg_operator</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_operator</> stores information about operators.
-   See <xref linkend="sql-createoperator">
-   and <xref linkend="xoper"> for more information.
-  </para>
-
-  <table>
-   <title><structname>pg_operator</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>oprname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the operator</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this operator
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the operator</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprkind</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       <literal>b</> = infix (<quote>both</quote>), <literal>l</> = prefix
-       (<quote>left</quote>), <literal>r</> = postfix (<quote>right</quote>)
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprcanmerge</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>This operator supports merge joins</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprcanhash</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>This operator supports hash joins</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprleft</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Type of the left operand</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprright</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Type of the right operand</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprresult</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Type of the result</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprcom</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-operator"><structname>pg_operator</structname></link>.oid</literal></entry>
-      <entry>Commutator of this operator, if any</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprnegate</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-operator"><structname>pg_operator</structname></link>.oid</literal></entry>
-      <entry>Negator of this operator, if any</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprcode</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Function that implements this operator</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprrest</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Restriction selectivity estimation function for this operator</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oprjoin</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Join selectivity estimation function for this operator</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Unused column contain zeroes. For example, <structfield>oprleft</structfield>
-   is zero for a prefix operator.
-  </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-opfamily">
-  <title><structname>pg_opfamily</structname></title>
-
-  <indexterm zone="catalog-pg-opfamily">
-   <primary>pg_opfamily</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_opfamily</structname> defines operator families.
-   Each operator family is a collection of operators and associated
-   support routines that implement the semantics specified for a particular
-   index access method.  Furthermore, the operators in a family are all
-   <quote>compatible</>, in a way that is specified by the access method.
-   The operator family concept allows cross-data-type operators to be used
-   with indexes and to be reasoned about using knowledge of access method
-   semantics.
-  </para>
-
-  <para>
-   Operator families are described at length in <xref linkend="xindex">.
-  </para>
-
-  <table>
-   <title><structname>pg_opfamily</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-
-     <row>
-      <entry><structfield>opfmethod</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-am"><structname>pg_am</structname></link>.oid</literal></entry>
-      <entry>Index access method operator family is for</entry>
-     </row>
-
-     <row>
-      <entry><structfield>opfname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of this operator family</entry>
-     </row>
-
-     <row>
-      <entry><structfield>opfnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>Namespace of this operator family</entry>
-     </row>
-
-     <row>
-      <entry><structfield>opfowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the operator family</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The majority of the information defining an operator family is not in its
-   <structname>pg_opfamily</structname> row, but in the associated rows in
-   <link linkend="catalog-pg-amop"><structname>pg_amop</structname></link>,
-   <link linkend="catalog-pg-amproc"><structname>pg_amproc</structname></link>,
-   and
-   <link linkend="catalog-pg-opclass"><structname>pg_opclass</structname></link>.
-  </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-pltemplate">
-  <title><structname>pg_pltemplate</structname></title>
-
-  <indexterm zone="catalog-pg-pltemplate">
-   <primary>pg_pltemplate</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_pltemplate</structname> stores
-   <quote>template</> information for procedural languages.
-   A template for a language allows the language to be created in a
-   particular database by a simple <command>CREATE LANGUAGE</> command,
-   with no need to specify implementation details.
-  </para>
-
-  <para>
-   Unlike most system catalogs, <structname>pg_pltemplate</structname>
-   is shared across all databases of a cluster: there is only one
-   copy of <structname>pg_pltemplate</structname> per cluster, not
-   one per database.  This allows the information to be accessible in
-   each database as it is needed.
-  </para>
-
-  <table>
-   <title><structname>pg_pltemplate</> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>tmplname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry>Name of the language this template is for</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tmpltrusted</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry>True if language is considered trusted</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tmpldbacreate</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry>True if language may be created by a database owner</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tmplhandler</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Name of call handler function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tmplinline</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Name of anonymous-block handler function, or null if none</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tmplvalidator</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Name of validator function, or null if none</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tmpllibrary</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Path of shared library that implements language</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tmplacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry>Access privileges for template (not actually used)</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   There are not currently any commands that manipulate procedural language
-   templates; to change the built-in information, a superuser must modify
-   the table using ordinary <command>INSERT</command>, <command>DELETE</command>,
-   or <command>UPDATE</command> commands.
-  </para>
-
-  <note>
-   <para>
-    It is likely that <structname>pg_pltemplate</> will be removed in some
-    future release of <productname>PostgreSQL</productname>, in favor of
-    keeping this knowledge about procedural languages in their respective
-    extension installation scripts.
-   </para>
-  </note>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-proc">
-  <title><structname>pg_proc</structname></title>
-
-  <indexterm zone="catalog-pg-proc">
-   <primary>pg_proc</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_proc</> stores information about functions (or procedures).
-   See <xref linkend="sql-createfunction">
-   and <xref linkend="xfunc"> for more information.
-  </para>
-
-  <para>
-   The table contains data for aggregate functions as well as plain functions.
-   If <structfield>proisagg</structfield> is true, there should be a matching
-   row in <structfield>pg_aggregate</structfield>.
-  </para>
-
-  <table>
-   <title><structname>pg_proc</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>proname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>pronamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this function
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>proowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>prolang</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-language"><structname>pg_language</structname></link>.oid</literal></entry>
-      <entry>Implementation language or call interface of this function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>procost</structfield></entry>
-      <entry><type>float4</type></entry>
-      <entry></entry>
-      <entry>Estimated execution cost (in units of
-       <xref linkend="guc-cpu-operator-cost">); if <structfield>proretset</>,
-       this is cost per row returned</entry>
-     </row>
-
-     <row>
-      <entry><structfield>prorows</structfield></entry>
-      <entry><type>float4</type></entry>
-      <entry></entry>
-      <entry>Estimated number of result rows (zero if not <structfield>proretset</>)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>provariadic</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Data type of the variadic array parameter's elements,
-       or zero if the function does not have a variadic parameter</entry>
-     </row>
-
-     <row>
-      <entry><structfield>proisagg</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Function is an aggregate function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>proiswindow</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Function is a window function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>prosecdef</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Function is a security definer (i.e., a <quote>setuid</>
-      function)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>proisstrict</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       Function returns null if any call argument is null.  In that
-       case the function won't actually be called at all.  Functions
-       that are not <quote>strict</quote> must be prepared to handle
-       null inputs.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>proretset</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Function returns a set (i.e., multiple values of the specified
-      data type)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>provolatile</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       <structfield>provolatile</structfield> tells whether the function's
-       result depends only on its input arguments, or is affected by outside
-       factors.
-       It is <literal>i</literal> for <quote>immutable</> functions,
-       which always deliver the same result for the same inputs.
-       It is <literal>s</literal> for <quote>stable</> functions,
-       whose results (for fixed inputs) do not change within a scan.
-       It is <literal>v</literal> for <quote>volatile</> functions,
-       whose results might change at any time.  (Use <literal>v</literal> also
-       for functions with side-effects, so that calls to them cannot get
-       optimized away.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>pronargs</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Number of input arguments</entry>
-     </row>
-
-     <row>
-      <entry><structfield>pronargdefaults</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Number of arguments that have defaults</entry>
-     </row>
-
-     <row>
-      <entry><structfield>prorettype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>Data type of the return value</entry>
-     </row>
-
-     <row>
-      <entry><structfield>proargtypes</structfield></entry>
-      <entry><type>oidvector</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>
-       An array with the data types of the function arguments.  This includes
-       only input arguments (including <literal>INOUT</literal> and
-       <literal>VARIADIC</> arguments), and thus represents
-       the call signature of the function.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>proallargtypes</structfield></entry>
-      <entry><type>oid[]</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>
-       An array with the data types of the function arguments.  This includes
-       all arguments (including <literal>OUT</literal> and
-       <literal>INOUT</literal> arguments); however, if all the
-       arguments are <literal>IN</literal> arguments, this field will be null.
-       Note that subscripting is 1-based, whereas for historical reasons
-       <structfield>proargtypes</> is subscripted from 0.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>proargmodes</structfield></entry>
-      <entry><type>char[]</type></entry>
-      <entry></entry>
-      <entry>
-        An array with the modes of the function arguments, encoded as
-        <literal>i</literal> for <literal>IN</> arguments,
-        <literal>o</literal> for <literal>OUT</> arguments,
-        <literal>b</literal> for <literal>INOUT</> arguments,
-        <literal>v</literal> for <literal>VARIADIC</> arguments,
-        <literal>t</literal> for <literal>TABLE</> arguments.
-        If all the arguments are <literal>IN</literal> arguments,
-        this field will be null.
-        Note that subscripts correspond to positions of
-        <structfield>proallargtypes</> not <structfield>proargtypes</>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>proargnames</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>
-        An array with the names of the function arguments.
-        Arguments without a name are set to empty strings in the array.
-        If none of the arguments have a name, this field will be null.
-        Note that subscripts correspond to positions of
-        <structfield>proallargtypes</> not <structfield>proargtypes</>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>proargdefaults</structfield></entry>
-      <entry><type>pg_node_tree</type></entry>
-      <entry></entry>
-      <entry>
-       Expression trees (in <function>nodeToString()</function> representation)
-       for default values.  This is a list with
-       <structfield>pronargdefaults</> elements, corresponding to the last
-       <replaceable>N</> <emphasis>input</> arguments (i.e., the last
-       <replaceable>N</> <structfield>proargtypes</> positions).
-       If none of the arguments have defaults, this field will be null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>prosrc</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       This tells the function handler how to invoke the function.  It
-       might be the actual source code of the function for interpreted
-       languages, a link symbol, a file name, or just about anything
-       else, depending on the implementation language/call convention.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>probin</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       Additional information about how to invoke the function.
-       Again, the interpretation is language-specific.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>proconfig</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>Function's local settings for run-time configuration variables</entry>
-     </row>
-
-     <row>
-      <entry><structfield>proacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access privileges; see
-       <xref linkend="sql-grant"> and
-       <xref linkend="sql-revoke">
-       for details
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   For compiled functions, both built-in and dynamically loaded,
-   <structfield>prosrc</structfield> contains the function's C-language
-   name (link symbol).  For all other currently-known language types,
-   <structfield>prosrc</structfield> contains the function's source
-   text.  <structfield>probin</structfield> is unused except for
-   dynamically-loaded C functions, for which it gives the name of the
-   shared library file containing the function.
-  </para>
-
- </sect1>
-
- <sect1 id="catalog-pg-rewrite">
-  <title><structname>pg_rewrite</structname></title>
-
-  <indexterm zone="catalog-pg-rewrite">
-   <primary>pg_rewrite</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_rewrite</structname> stores rewrite rules for tables and views.
-  </para>
-
-  <table>
-   <title><structname>pg_rewrite</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>rulename</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Rule name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ev_class</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The table this rule is for</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ev_attr</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>The column this rule is for (currently, always zero to
-      indicate the whole table)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ev_type</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       Event type that the rule is for: 1 = <command>SELECT</>, 2 =
-       <command>UPDATE</>, 3 = <command>INSERT</>, 4 =
-       <command>DELETE</>
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>ev_enabled</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       Controls in which <xref linkend="guc-session-replication-role"> modes
-       the rule fires.
-       <literal>O</> = rule fires in <quote>origin</> and <quote>local</> modes,
-       <literal>D</> = rule is disabled,
-       <literal>R</> = rule fires in <quote>replica</> mode,
-       <literal>A</> = rule fires always.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>is_instead</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if the rule is an <literal>INSTEAD</literal> rule</entry>
-     </row>
-
-     <row>
-      <entry><structfield>ev_qual</structfield></entry>
-      <entry><type>pg_node_tree</type></entry>
-      <entry></entry>
-      <entry>
-       Expression tree (in the form of a
-       <function>nodeToString()</function> representation) for the
-       rule's qualifying condition
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>ev_action</structfield></entry>
-      <entry><type>pg_node_tree</type></entry>
-      <entry></entry>
-      <entry>
-       Query tree (in the form of a
-       <function>nodeToString()</function> representation) for the
-       rule's action
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <note>
-   <para>
-    <literal>pg_class.relhasrules</literal>
-    must be true if a table has any rules in this catalog.
-   </para>
-  </note>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-seclabel">
-  <title><structname>pg_seclabel</structname></title>
-
-  <indexterm zone="catalog-pg-seclabel">
-   <primary>pg_seclabel</primary>
-  </indexterm>
-
-  <para>
-   The catalog <structname>pg_seclabel</structname> stores security
-   labels on database objects.  See the
-   <xref linkend="sql-security-label"> statement.
-  </para>
-
-  <table>
-   <title><structname>pg_seclabel</structname> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>objoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry>any OID column</entry>
-      <entry>The OID of the object this security label pertains to</entry>
-     </row>
-
-     <row>
-      <entry><structfield>classoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The OID of the system catalog this object appears in</entry>
-     </row>
-
-     <row>
-      <entry><structfield>objsubid</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       For a security label on a table column, this is the column number (the
-       <structfield>objoid</> and <structfield>classoid</> refer to
-       the table itself).  For all other object types, this column is
-       zero.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>provider</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>The label provider associated with this label.</entry>
-     </row>
-
-     <row>
-      <entry><structfield>label</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>The security label applied to this object.</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="catalog-pg-shdepend">
-  <title><structname>pg_shdepend</structname></title>
-
-  <indexterm zone="catalog-pg-shdepend">
-   <primary>pg_shdepend</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_shdepend</structname> records the
-   dependency relationships between database objects and shared objects,
-   such as roles.  This information allows
-   <productname>PostgreSQL</productname> to ensure that those objects are
-   unreferenced before attempting to delete them.
-  </para>
-
-  <para>
-   See also <link linkend="catalog-pg-depend"><structname>pg_depend</structname></link>,
-   which performs a similar function for dependencies involving objects
-   within a single database.
-  </para>
-
-  <para>
-   Unlike most system catalogs, <structname>pg_shdepend</structname>
-   is shared across all databases of a cluster: there is only one
-   copy of <structname>pg_shdepend</structname> per cluster, not
-   one per database.
-  </para>
-
-  <table>
-   <title><structname>pg_shdepend</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>dbid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-database"><structname>pg_database</structname></link>.oid</literal></entry>
-      <entry>The OID of the database the dependent object is in,
-       or zero for a shared object</entry>
-     </row>
-
-     <row>
-      <entry><structfield>classid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The OID of the system catalog the dependent object is in</entry>
-     </row>
-
-     <row>
-      <entry><structfield>objid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry>any OID column</entry>
-      <entry>The OID of the specific dependent object</entry>
-     </row>
-
-     <row>
-      <entry><structfield>objsubid</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       For a table column, this is the column number (the
-       <structfield>objid</> and <structfield>classid</> refer to the
-       table itself).  For all other object types, this column is zero.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>refclassid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The OID of the system catalog the referenced object is in
-       (must be a shared catalog)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>refobjid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry>any OID column</entry>
-      <entry>The OID of the specific referenced object</entry>
-     </row>
-
-     <row>
-      <entry><structfield>deptype</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       A code defining the specific semantics of this dependency relationship; see text
-      </entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   In all cases, a <structname>pg_shdepend</structname> entry indicates that
-   the referenced object cannot be dropped without also dropping the dependent
-   object.  However, there are several subflavors identified by
-   <structfield>deptype</>:
-
-   <variablelist>
-    <varlistentry>
-     <term><symbol>SHARED_DEPENDENCY_OWNER</> (<literal>o</>)</term>
-     <listitem>
-      <para>
-       The referenced object (which must be a role) is the owner of the
-       dependent object.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SHARED_DEPENDENCY_ACL</> (<literal>a</>)</term>
-     <listitem>
-      <para>
-       The referenced object (which must be a role) is mentioned in the
-       ACL (access control list, i.e., privileges list) of the
-       dependent object.  (A <symbol>SHARED_DEPENDENCY_ACL</> entry is
-       not made for the owner of the object, since the owner will have
-       a <symbol>SHARED_DEPENDENCY_OWNER</> entry anyway.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SHARED_DEPENDENCY_PIN</> (<literal>p</>)</term>
-     <listitem>
-      <para>
-       There is no dependent object; this type of entry is a signal
-       that the system itself depends on the referenced object, and so
-       that object must never be deleted.  Entries of this type are
-       created only by <command>initdb</command>.  The columns for the
-       dependent object contain zeroes.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-   Other dependency flavors might be needed in future.  Note in particular
-   that the current definition only supports roles as referenced objects.
-  </para>
-
- </sect1>
-
- <sect1 id="catalog-pg-shdescription">
-  <title><structname>pg_shdescription</structname></title>
-
-  <indexterm zone="catalog-pg-shdescription">
-   <primary>pg_shdescription</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_shdescription</structname> stores optional
-   descriptions (comments) for shared database objects.  Descriptions can be
-   manipulated with the <xref linkend="sql-comment"> command and viewed with
-   <application>psql</application>'s <literal>\d</literal> commands.
-  </para>
-
-  <para>
-   See also <link linkend="catalog-pg-description"><structname>pg_description</structname></link>,
-   which performs a similar function for descriptions involving objects
-   within a single database.
-  </para>
-
-  <para>
-   Unlike most system catalogs, <structname>pg_shdescription</structname>
-   is shared across all databases of a cluster: there is only one
-   copy of <structname>pg_shdescription</structname> per cluster, not
-   one per database.
-  </para>
-
-  <table>
-   <title><structname>pg_shdescription</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>objoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry>any OID column</entry>
-      <entry>The OID of the object this description pertains to</entry>
-     </row>
-
-     <row>
-      <entry><structfield>classoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The OID of the system catalog this object appears in</entry>
-     </row>
-
-     <row>
-      <entry><structfield>description</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Arbitrary text that serves as the description of this object</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-statistic">
-  <title><structname>pg_statistic</structname></title>
-
-  <indexterm zone="catalog-pg-statistic">
-   <primary>pg_statistic</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_statistic</structname> stores
-   statistical data about the contents of the database.  Entries are
-   created by <xref linkend="sql-analyze">
-   and subsequently used by the query planner.  Note that all the
-   statistical data is inherently approximate, even assuming that it
-   is up-to-date.
-  </para>
-
-  <para>
-   Normally there is one entry, with <structfield>stainherit</> =
-   <literal>false</>, for each table column that has been analyzed.
-   If the table has inheritance children, a second entry with
-   <structfield>stainherit</> = <literal>true</> is also created.  This row
-   represents the column's statistics over the inheritance tree, i.e.,
-   statistics for the data you'd see with
-   <literal>SELECT <replaceable>column</> FROM <replaceable>table</>*</literal>,
-   whereas the <structfield>stainherit</> = <literal>false</> row represents
-   the results of
-   <literal>SELECT <replaceable>column</> FROM ONLY <replaceable>table</></literal>.
-  </para>
-
-  <para>
-   <structname>pg_statistic</structname> also stores statistical data about
-   the values of index expressions.  These are described as if they were
-   actual data columns; in particular, <structfield>starelid</structfield>
-   references the index.  No entry is made for an ordinary non-expression
-   index column, however, since it would be redundant with the entry
-   for the underlying table column.  Currently, entries for index expressions
-   always have <structfield>stainherit</> = <literal>false</>.
-  </para>
-
-  <para>
-   Since different kinds of statistics might be appropriate for different
-   kinds of data, <structname>pg_statistic</structname> is designed not
-   to assume very much about what sort of statistics it stores.  Only
-   extremely general statistics (such as nullness) are given dedicated
-   columns in <structname>pg_statistic</structname>.  Everything else
-   is stored in <quote>slots</quote>, which are groups of associated columns
-   whose content is identified by a code number in one of the slot's columns.
-   For more information see
-   <filename>src/include/catalog/pg_statistic.h</filename>.
-  </para>
-
-  <para>
-   <structname>pg_statistic</structname> should not be readable by the
-   public, since even statistical information about a table's contents
-   might be considered sensitive.  (Example: minimum and maximum values
-   of a salary column might be quite interesting.)
-   <link linkend="view-pg-stats"><structname>pg_stats</structname></link>
-   is a publicly readable view on
-   <structname>pg_statistic</structname> that only exposes information
-   about those tables that are readable by the current user.
-  </para>
-
-  <table>
-   <title><structname>pg_statistic</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>starelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The table or index that the described column belongs to</entry>
-     </row>
-
-     <row>
-      <entry><structfield>staattnum</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry><literal><link linkend="catalog-pg-attribute"><structname>pg_attribute</structname></link>.attnum</literal></entry>
-      <entry>The number of the described column</entry>
-     </row>
-
-     <row>
-      <entry><structfield>stainherit</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>If true, the stats include inheritance child columns, not just the
-       values in the specified relation</entry>
-     </row>
-
-     <row>
-      <entry><structfield>stanullfrac</structfield></entry>
-      <entry><type>float4</type></entry>
-      <entry></entry>
-      <entry>The fraction of the column's entries that are null</entry>
-     </row>
-
-     <row>
-      <entry><structfield>stawidth</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>The average stored width, in bytes, of nonnull entries</entry>
-     </row>
-
-     <row>
-      <entry><structfield>stadistinct</structfield></entry>
-      <entry><type>float4</type></entry>
-      <entry></entry>
-      <entry>The number of distinct nonnull data values in the column.
-      A value greater than zero is the actual number of distinct values.
-      A value less than zero is the negative of a multiplier for the number
-      of rows in the table; for example, a column in which values appear about
-      twice on the average could be represented by
-      <structfield>stadistinct</> = -0.5.
-      A zero value means the number of distinct values is unknown.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>stakind<replaceable>N</></structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       A code number indicating the kind of statistics stored in the
-       <replaceable>N</>th <quote>slot</quote> of the
-       <structname>pg_statistic</structname> row.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>staop<replaceable>N</></structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-operator"><structname>pg_operator</structname></link>.oid</literal></entry>
-      <entry>
-       An operator used to derive the statistics stored in the
-       <replaceable>N</>th <quote>slot</quote>.  For example, a
-       histogram slot would show the <literal>&lt;</literal> operator
-       that defines the sort order of the data.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>stanumbers<replaceable>N</></structfield></entry>
-      <entry><type>float4[]</type></entry>
-      <entry></entry>
-      <entry>
-       Numerical statistics of the appropriate kind for the
-       <replaceable>N</>th <quote>slot</quote>, or null if the slot
-       kind does not involve numerical values
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>stavalues<replaceable>N</></structfield></entry>
-      <entry><type>anyarray</type></entry>
-      <entry></entry>
-      <entry>
-       Column data values of the appropriate kind for the
-       <replaceable>N</>th <quote>slot</quote>, or null if the slot
-       kind does not store any data values.  Each array's element
-       values are actually of the specific column's data type, so there
-       is no way to define these columns' type more specifically than
-       <type>anyarray</>.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-tablespace">
-  <title><structname>pg_tablespace</structname></title>
-
-  <indexterm zone="catalog-pg-tablespace">
-   <primary>pg_tablespace</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_tablespace</structname> stores information
-   about the available tablespaces.  Tables can be placed in particular
-   tablespaces to aid administration of disk layout.
-  </para>
-
-  <para>
-   Unlike most system catalogs, <structname>pg_tablespace</structname>
-   is shared across all databases of a cluster: there is only one
-   copy of <structname>pg_tablespace</structname> per cluster, not
-   one per database.
-  </para>
-
-  <table>
-   <title><structname>pg_tablespace</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>spcname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Tablespace name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>spcowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the tablespace, usually the user who created it</entry>
-     </row>
-
-     <row>
-      <entry><structfield>spclocation</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Location (directory path) of the tablespace</entry>
-     </row>
-
-     <row>
-      <entry><structfield>spcacl</structfield></entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access privileges; see
-       <xref linkend="sql-grant"> and
-       <xref linkend="sql-revoke">
-       for details
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>spcoptions</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>
-       Tablespace-level options, as <quote>keyword=value</> strings
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-trigger">
-  <title><structname>pg_trigger</structname></title>
-
-  <indexterm zone="catalog-pg-trigger">
-   <primary>pg_trigger</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_trigger</structname> stores triggers on tables
-   and views.
-   See <xref linkend="sql-createtrigger">
-   for more information.
-  </para>
-
-  <table>
-   <title><structname>pg_trigger</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>tgrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The table this trigger is on</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Trigger name (must be unique among triggers of same table)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgfoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>The function to be called</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgtype</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Bit mask identifying trigger firing conditions</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgenabled</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       Controls in which <xref linkend="guc-session-replication-role"> modes
-       the trigger fires.
-       <literal>O</> = trigger fires in <quote>origin</> and <quote>local</> modes,
-       <literal>D</> = trigger is disabled,
-       <literal>R</> = trigger fires in <quote>replica</> mode,
-       <literal>A</> = trigger fires always.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgisinternal</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if trigger is internally generated (usually, to enforce
-       the constraint identified by <structfield>tgconstraint</>)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgconstrrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The table referenced by a referential integrity constraint</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgconstrindid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The index supporting a unique, primary key, or referential integrity constraint</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgconstraint</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-constraint"><structname>pg_constraint</structname></link>.oid</literal></entry>
-      <entry>The <structname>pg_constraint</> entry associated with the trigger, if any</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgdeferrable</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if constraint trigger is deferrable</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tginitdeferred</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if constraint trigger is initially deferred</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgnargs</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Number of argument strings passed to trigger function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgattr</structfield></entry>
-      <entry><type>int2vector</type></entry>
-      <entry><literal><link linkend="catalog-pg-attribute"><structname>pg_attribute</structname></link>.attnum</literal></entry>
-      <entry>Column numbers, if trigger is column-specific; otherwise an
-       empty array</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgargs</structfield></entry>
-      <entry><type>bytea</type></entry>
-      <entry></entry>
-      <entry>Argument strings to pass to trigger, each NULL-terminated</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tgqual</structfield></entry>
-      <entry><type>pg_node_tree</type></entry>
-      <entry></entry>
-      <entry>Expression tree (in <function>nodeToString()</function>
-       representation) for the trigger's <literal>WHEN</> condition, or null
-       if none</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Currently, column-specific triggering is supported only for
-   <literal>UPDATE</> events, and so <structfield>tgattr</> is relevant
-   only for that event type.  <structfield>tgtype</structfield> might
-   contain bits for other event types as well, but those are presumed
-   to be table-wide regardless of what is in <structfield>tgattr</>.
-  </para>
-
-  <note>
-   <para>
-    When <structfield>tgconstraint</> is nonzero,
-    <structfield>tgconstrrelid</>, <structfield>tgconstrindid</>,
-    <structfield>tgdeferrable</>, and <structfield>tginitdeferred</> are
-    largely redundant with the referenced <structname>pg_constraint</> entry.
-    However, it is possible for a non-deferrable trigger to be associated
-    with a deferrable constraint: foreign key constraints can have some
-    deferrable and some non-deferrable triggers.
-   </para>
-  </note>
-
-  <note>
-   <para>
-    <literal>pg_class.relhastriggers</literal>
-    must be true if a relation has any triggers in this catalog.
-   </para>
-  </note>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-ts-config">
-  <title><structname>pg_ts_config</structname></title>
-
-  <indexterm zone="catalog-pg-ts-config">
-   <primary>pg_ts_config</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The <structname>pg_ts_config</structname> catalog contains entries
-   representing text search configurations.  A configuration specifies
-   a particular text search parser and a list of dictionaries to use
-   for each of the parser's output token types.  The parser is shown
-   in the <structname>pg_ts_config</structname> entry, but the
-   token-to-dictionary mapping is defined by subsidiary entries in <link
-   linkend="catalog-pg-ts-config-map"><structname>pg_ts_config_map</structname></link>.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname>'s text search features are
-   described at length in <xref linkend="textsearch">.
-  </para>
-
-  <table>
-   <title><structname>pg_ts_config</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>cfgname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Text search configuration name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>cfgnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this configuration
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>cfgowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the configuration</entry>
-     </row>
-
-     <row>
-      <entry><structfield>cfgparser</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-ts-parser"><structname>pg_ts_parser</structname></link>.oid</literal></entry>
-      <entry>The OID of the text search parser for this configuration</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-ts-config-map">
-  <title><structname>pg_ts_config_map</structname></title>
-
-  <indexterm zone="catalog-pg-ts-config-map">
-   <primary>pg_ts_config_map</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The <structname>pg_ts_config_map</structname> catalog contains entries
-   showing which text search dictionaries should be consulted, and in
-   what order, for each output token type of each text search configuration's
-   parser.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname>'s text search features are
-   described at length in <xref linkend="textsearch">.
-  </para>
-
-  <table>
-   <title><structname>pg_ts_config_map</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>mapcfg</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-ts-config"><structname>pg_ts_config</structname></link>.oid</literal></entry>
-      <entry>The OID of the <structname>pg_ts_config</> entry owning this map entry</entry>
-     </row>
-
-     <row>
-      <entry><structfield>maptokentype</structfield></entry>
-      <entry><type>integer</type></entry>
-      <entry></entry>
-      <entry>A token type emitted by the configuration's parser</entry>
-     </row>
-
-     <row>
-      <entry><structfield>mapseqno</structfield></entry>
-      <entry><type>integer</type></entry>
-      <entry></entry>
-      <entry>Order in which to consult this entry (lower
-       <structfield>mapseqno</>s first)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>mapdict</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-ts-dict"><structname>pg_ts_dict</structname></link>.oid</literal></entry>
-      <entry>The OID of the text search dictionary to consult</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-ts-dict">
-  <title><structname>pg_ts_dict</structname></title>
-
-  <indexterm zone="catalog-pg-ts-dict">
-   <primary>pg_ts_dict</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The <structname>pg_ts_dict</structname> catalog contains entries
-   defining text search dictionaries.  A dictionary depends on a text
-   search template, which specifies all the implementation functions
-   needed; the dictionary itself provides values for the user-settable
-   parameters supported by the template.  This division of labor allows
-   dictionaries to be created by unprivileged users.  The parameters
-   are specified by a text string <structfield>dictinitoption</>,
-   whose format and meaning vary depending on the template.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname>'s text search features are
-   described at length in <xref linkend="textsearch">.
-  </para>
-
-  <table>
-   <title><structname>pg_ts_dict</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>dictname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Text search dictionary name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>dictnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this dictionary
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>dictowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the dictionary</entry>
-     </row>
-
-     <row>
-      <entry><structfield>dicttemplate</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-ts-template"><structname>pg_ts_template</structname></link>.oid</literal></entry>
-      <entry>The OID of the text search template for this dictionary</entry>
-     </row>
-
-     <row>
-      <entry><structfield>dictinitoption</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Initialization option string for the template</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-ts-parser">
-  <title><structname>pg_ts_parser</structname></title>
-
-  <indexterm zone="catalog-pg-ts-parser">
-   <primary>pg_ts_parser</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The <structname>pg_ts_parser</structname> catalog contains entries
-   defining text search parsers.  A parser is responsible for splitting
-   input text into lexemes and assigning a token type to each lexeme.
-   Since a parser must be implemented by C-language-level functions,
-   creation of new parsers is restricted to database superusers.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname>'s text search features are
-   described at length in <xref linkend="textsearch">.
-  </para>
-
-  <table>
-   <title><structname>pg_ts_parser</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>prsname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Text search parser name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>prsnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this parser
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>prsstart</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>OID of the parser's startup function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>prstoken</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>OID of the parser's next-token function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>prsend</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>OID of the parser's shutdown function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>prsheadline</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>OID of the parser's headline function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>prslextype</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>OID of the parser's lextype function</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-ts-template">
-  <title><structname>pg_ts_template</structname></title>
-
-  <indexterm zone="catalog-pg-ts-template">
-   <primary>pg_ts_template</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The <structname>pg_ts_template</structname> catalog contains entries
-   defining text search templates.  A template is the implementation
-   skeleton for a class of text search dictionaries.
-   Since a template must be implemented by C-language-level functions,
-   creation of new templates is restricted to database superusers.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname>'s text search features are
-   described at length in <xref linkend="textsearch">.
-  </para>
-
-  <table>
-   <title><structname>pg_ts_template</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>tmplname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Text search template name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tmplnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this template
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>tmplinit</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>OID of the template's initialization function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tmpllexize</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>OID of the template's lexize function</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-type">
-  <title><structname>pg_type</structname></title>
-
-  <indexterm zone="catalog-pg-type">
-   <primary>pg_type</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_type</structname> stores information about data
-   types.  Base types and enum types (scalar types) are created with
-   <xref linkend="sql-createtype">, and
-   domains with
-   <xref linkend="sql-createdomain">.
-   A composite type is automatically created for each table in the database, to
-   represent the row structure of the table.  It is also possible to create
-   composite types with <command>CREATE TYPE AS</command>.
-  </para>
-
-  <table>
-   <title><structname>pg_type</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>typname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Data type name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>typnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace that contains this type
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typowner</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>Owner of the type</entry>
-     </row>
-
-     <row>
-      <entry><structfield>typlen</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       For a fixed-size type, <structfield>typlen</structfield> is the number
-       of bytes in the internal representation of the type.  But for a
-       variable-length type, <structfield>typlen</structfield> is negative.
-       -1 indicates a <quote>varlena</> type (one that has a length word),
-       -2 indicates a null-terminated C string.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typbyval</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       <structfield>typbyval</structfield> determines whether internal
-       routines pass a value of this type by value or by reference.
-       <structfield>typbyval</structfield> had better be false if
-       <structfield>typlen</structfield> is not 1, 2, or 4 (or 8 on machines
-       where Datum is 8 bytes).
-       Variable-length types are always passed by reference. Note that
-       <structfield>typbyval</structfield> can be false even if the
-       length would allow pass-by-value.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typtype</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       <structfield>typtype</structfield> is
-       <literal>b</literal> for a base type,
-       <literal>c</literal> for a composite type (e.g., a table's row type),
-       <literal>d</literal> for a domain,
-       <literal>e</literal> for an enum type,
-       or <literal>p</literal> for a pseudo-type.
-       See also <structfield>typrelid</structfield> and
-       <structfield>typbasetype</structfield>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typcategory</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       <structfield>typcategory</structfield> is an arbitrary classification
-       of data types that is used by the parser to determine which implicit
-       casts should be <quote>preferred</>.
-       See <xref linkend="catalog-typcategory-table">.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typispreferred</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       True if the type is a preferred cast target within its
-       <structfield>typcategory</structfield>
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typisdefined</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       True if the type is defined, false if this is a placeholder
-       entry for a not-yet-defined type.  When
-       <structfield>typisdefined</structfield> is false, nothing
-       except the type name, namespace, and OID can be relied on.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typdelim</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       Character that separates two values of this type when parsing
-       array input.  Note that the delimiter is associated with the array
-       element data type, not the array data type.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>
-       If this is a composite type (see
-       <structfield>typtype</structfield>), then this column points to
-       the <structname>pg_class</structname> entry that defines the
-       corresponding table.  (For a free-standing composite type, the
-       <structname>pg_class</structname> entry doesn't really represent
-       a table, but it is needed anyway for the type's
-       <structname>pg_attribute</structname> entries to link to.)
-       Zero for non-composite types.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typelem</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>
-       If <structfield>typelem</structfield> is not 0 then it
-       identifies another row in <structname>pg_type</structname>.
-       The current type can then be subscripted like an array yielding
-       values of type <structfield>typelem</structfield>.  A
-       <quote>true</quote> array type is variable length
-       (<structfield>typlen</structfield> = -1),
-       but some fixed-length (<structfield>typlen</structfield> &gt; 0) types
-       also have nonzero <structfield>typelem</structfield>, for example
-       <type>name</type> and <type>point</type>.
-       If a fixed-length type has a <structfield>typelem</structfield> then
-       its internal representation must be some number of values of the
-       <structfield>typelem</structfield> data type with no other data.
-       Variable-length array types have a header defined by the array
-       subroutines.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typarray</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry>
-       If <structfield>typarray</structfield> is not 0 then it
-       identifies another row in <structname>pg_type</structname>, which
-       is the <quote>true</quote> array type having this type as element
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>typinput</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Input conversion function (text format)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>typoutput</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Output conversion function (text format)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>typreceive</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Input conversion function (binary format), or 0 if none</entry>
-     </row>
-
-     <row>
-      <entry><structfield>typsend</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Output conversion function (binary format), or 0 if none</entry>
-     </row>
-
-     <row>
-      <entry><structfield>typmodin</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Type modifier input function, or 0 if type does not support modifiers</entry>
-     </row>
-
-     <row>
-      <entry><structfield>typmodout</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Type modifier output function, or 0 to use the standard format</entry>
-     </row>
-
-     <row>
-      <entry><structfield>typanalyze</structfield></entry>
-      <entry><type>regproc</type></entry>
-      <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Custom <command>ANALYZE</command> function, or 0 to use the standard function</entry>
-     </row>
-
-     <row>
-      <entry><structfield>typalign</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry><para>
-
-       <structfield>typalign</structfield> is the alignment required
-       when storing a value of this type.  It applies to storage on
-       disk as well as most representations of the value inside
-       <productname>PostgreSQL</>.
-       When multiple values are stored consecutively, such
-       as in the representation of a complete row on disk, padding is
-       inserted before a datum of this type so that it begins on the
-       specified boundary.  The alignment reference is the beginning
-       of the first datum in the sequence.
-      </para>
-
-      <para>
-       Possible values are:
-       <itemizedlist>
-        <listitem>
-         <para><literal>c</> = <type>char</type> alignment, i.e., no alignment needed.</para>
-        </listitem>
-        <listitem>
-         <para><literal>s</> = <type>short</type> alignment (2 bytes on most machines).</para>
-        </listitem>
-        <listitem>
-         <para><literal>i</> = <type>int</type> alignment (4 bytes on most machines).</para>
-        </listitem>
-        <listitem>
-         <para><literal>d</> = <type>double</type> alignment (8 bytes on many machines, but by no means all).</para>
-        </listitem>
-       </itemizedlist>
-      </para><note>
-       <para>
-        For types used in system tables, it is critical that the size
-        and alignment defined in <structname>pg_type</structname>
-        agree with the way that the compiler will lay out the column in
-        a structure representing a table row.
-       </para>
-      </note></entry>
-     </row>
-
-     <row>
-      <entry><structfield>typstorage</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry><para>
-       <structfield>typstorage</structfield> tells for varlena
-       types (those with <structfield>typlen</structfield> = -1) if
-       the type is prepared for toasting and what the default strategy
-       for attributes of this type should be.
-       Possible values are
-       <itemizedlist>
-        <listitem>
-         <para><literal>p</>: Value must always be stored plain.</para>
-        </listitem>
-        <listitem>
-         <para>
-          <literal>e</>: Value can be stored in a <quote>secondary</quote>
-          relation (if relation has one, see
-          <literal>pg_class.reltoastrelid</literal>).
-         </para>
-        </listitem>
-        <listitem>
-         <para><literal>m</>: Value can be stored compressed inline.</para>
-        </listitem>
-        <listitem>
-         <para><literal>x</>: Value can be stored compressed inline or stored in <quote>secondary</quote> storage.</para>
-        </listitem>
-       </itemizedlist>
-       Note that <literal>m</> columns can also be moved out to secondary
-       storage, but only as a last resort (<literal>e</> and <literal>x</> columns are
-       moved first).
-      </para></entry>
-     </row>
-
-     <row>
-      <entry><structfield>typnotnull</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry><para>
-       <structfield>typnotnull</structfield> represents a not-null
-       constraint on a type.  Used for domains only.
-      </para></entry>
-     </row>
-
-     <row>
-      <entry><structfield>typbasetype</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
-      <entry><para>
-       If this is a domain (see <structfield>typtype</structfield>), then
-       <structfield>typbasetype</structfield> identifies the type that this
-       one is based on.  Zero if this type is not a domain.
-      </para></entry>
-     </row>
-
-     <row>
-      <entry><structfield>typtypmod</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry><para>
-       Domains use <structfield>typtypmod</structfield> to record the <literal>typmod</>
-       to be applied to their base type (-1 if base type does not use a
-       <literal>typmod</>).  -1 if this type is not a domain.
-      </para></entry>
-     </row>
-
-     <row>
-      <entry><structfield>typndims</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry><para>
-       <structfield>typndims</structfield> is the number of array dimensions
-       for a domain over an array (that is, <structfield>typbasetype</> is
-       an array type).
-       Zero for types other than domains over array types.
-       </para></entry>
-     </row>
-
-     <row>
-      <entry><structfield>typcollation</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-collation"><structname>pg_collation</structname></link>.oid</literal></entry>
-      <entry><para>
-       <structfield>typcollation</structfield> specifies the collation
-       of the type.  If the type does not support collations, this will
-       be zero.  A base type that supports collations will have
-       <symbol>DEFAULT_COLLATION_OID</symbol> here.  A domain over a
-       collatable type can have some other collation OID, if one was
-       specified for the domain.
-      </para></entry>
-     </row>
-
-     <row>
-      <entry><structfield>typdefaultbin</structfield></entry>
-      <entry><type>pg_node_tree</type></entry>
-      <entry></entry>
-      <entry><para>
-       If <structfield>typdefaultbin</> is not null, it is the
-       <function>nodeToString()</function>
-       representation of a default expression for the type.  This is
-       only used for domains.
-      </para></entry>
-     </row>
-
-     <row>
-      <entry><structfield>typdefault</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry><para>
-       <structfield>typdefault</> is null if the type has no associated
-       default value. If <structfield>typdefaultbin</> is not null,
-       <structfield>typdefault</> must contain a human-readable version of the
-       default expression represented by <structfield>typdefaultbin</>.  If
-       <structfield>typdefaultbin</> is null and <structfield>typdefault</> is
-       not, then <structfield>typdefault</> is the external representation of
-       the type's default value, which can be fed to the type's input
-       converter to produce a constant.
-      </para></entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   <xref linkend="catalog-typcategory-table"> lists the system-defined values
-   of <structfield>typcategory</>.  Any future additions to this list will
-   also be upper-case ASCII letters.  All other ASCII characters are reserved
-   for user-defined categories.
-  </para>
-
-  <table id="catalog-typcategory-table">
-   <title><structfield>typcategory</> Codes</title>
-
-   <tgroup cols="2">
-    <thead>
-     <row>
-      <entry>Code</entry>
-      <entry>Category</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>A</literal></entry>
-      <entry>Array types</entry>
-     </row>
-     <row>
-      <entry><literal>B</literal></entry>
-      <entry>Boolean types</entry>
-     </row>
-     <row>
-      <entry><literal>C</literal></entry>
-      <entry>Composite types</entry>
-     </row>
-     <row>
-      <entry><literal>D</literal></entry>
-      <entry>Date/time types</entry>
-     </row>
-     <row>
-      <entry><literal>E</literal></entry>
-      <entry>Enum types</entry>
-     </row>
-     <row>
-      <entry><literal>G</literal></entry>
-      <entry>Geometric types</entry>
-     </row>
-     <row>
-      <entry><literal>I</literal></entry>
-      <entry>Network address types</entry>
-     </row>
-     <row>
-      <entry><literal>N</literal></entry>
-      <entry>Numeric types</entry>
-     </row>
-     <row>
-      <entry><literal>P</literal></entry>
-      <entry>Pseudo-types</entry>
-     </row>
-     <row>
-      <entry><literal>S</literal></entry>
-      <entry>String types</entry>
-     </row>
-     <row>
-      <entry><literal>T</literal></entry>
-      <entry>Timespan types</entry>
-     </row>
-     <row>
-      <entry><literal>U</literal></entry>
-      <entry>User-defined types</entry>
-     </row>
-     <row>
-      <entry><literal>V</literal></entry>
-      <entry>Bit-string types</entry>
-     </row>
-     <row>
-      <entry><literal>X</literal></entry>
-      <entry><type>unknown</> type</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-user-mapping">
-  <title><structname>pg_user_mapping</structname></title>
-
-  <indexterm zone="catalog-pg-user-mapping">
-   <primary>pg_user_mapping</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The catalog <structname>pg_user_mapping</structname> stores
-   the mappings from local user to remote.  Access to this catalog is
-   restricted from normal users, use the view
-   <link linkend="view-pg-user-mappings"><structname>pg_user_mappings</structname></link>
-   instead.
-  </para>
-
-  <table>
-   <title><structname>pg_user_mapping</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>umuser</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>OID of the local role being mapped, 0 if the user mapping is public</entry>
-     </row>
-
-     <row>
-      <entry><structfield>umserver</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-foreign-server"><structname>pg_foreign_server</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the foreign server that contains this mapping
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>umoptions</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>
-       User mapping specific options, as <quote>keyword=value</> strings
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-<!## XC>
- <sect1 id="catalog-pgxc-class">
-  <title><structname>pgxc_class</structname></title>
-
-  <indexterm zone="catalog-pgxc-class">
-   <primary>pgxc_class</primary>
-  </indexterm>
-
-&xconly;
-  <para>
-   The catalog <structname>pgxc_class</structname> stores information
-   whether each table is replicated or distributed, as well as
-   distribution method and the distribution column.
-  </para>
-
-  <table>
-   <title><structname>pgxc_class</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>pcrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><link linkend="catalog-pg-class"><structname>pg_class</structname></link><literal>.oid</literal></entry>
-      <entry>OID of the table</entry>
-     </row>
-
-     <row>
-      <entry><structfield>pclocatortype</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       Type of locator.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>pcattnum</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       Column number of used as distribution key.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>pchashalgorithm</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       Indicates hashing algorithm used to distribute the tuples.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>pchashbuckets</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       Indicates the number of hash buckets used to distribute duple.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>nodeoids</structfield></entry>
-      <entry><type>oidvector</type></entry>
-      <entry><literal><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.oid</literal></entry>
-      <entry>
-       List of node OIDs where table is located.
-       This list is ordered by <literal><link linkend="catalog-pgxc-node"><structname>
-       pgxc_node</structname></link>.node_name</literal>. This list is then
-       indexed in information in user session cache and reused as a node target list
-       when doing SQL operations on cluster tables.
-      </entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="catalog-pgxc-node">
-  <title><structname>pgxc_node</structname></title>
-
-  <indexterm zone="catalog-pgxc-node">
-   <primary>pgxc_node</primary>
-  </indexterm>
-
-&xconly;
-  <para>
-   The catalog <structname>pgxc_node</structname> stores information
-   about cluster node information, such as connection information with
-   node port and host, node name, primary and preferred nodes.
-  </para>
-
-  <table>
-   <title><structname>pgxc_node</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>node_name</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of cluster node</entry>
-     </row>
-
-     <row>
-      <entry><structfield>node_type</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>Type of cluster node.
-       It is <literal>C</literal> for a Coordinator.
-       It is <literal>D</literal> for a Datanode.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>node_port</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>Port number of cluster node</entry>
-     </row>
-
-     <row>
-      <entry><structfield>node_host</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Host name or IP number of cluster node</entry>
-     </row>
-
-     <row>
-      <entry><structfield>nodeis_primary</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Defines if node is a primary node.
-       Only Datanode can be a primary node.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>nodeis_preferred</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Defines if node is a preferred node.
-       Only a Datanode can be a preferred node.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>node_id</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>Integer node identifier of node.
-       It is generated when node is created.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="catalog-pgxc-group">
-  <title><structname>pgxc_group</structname></title>
-
-  <indexterm zone="catalog-pgxc-group">
-   <primary>pgxc_group</primary>
-  </indexterm>
-
-&xconly;
-  <para>
-   The catalog <structname>pgxc_group</structname> stores information
-   about cluster node group information, which is a list of cluster node
-   OIDs. Groups can be used as aliases.
-  </para>
-
-  <table>
-   <title><structname>pgxc_group</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>group_name</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of cluster node group</entry>
-     </row>
-
-     <row>
-      <entry><structfield>group_members</structfield></entry>
-      <entry><type>oidvector</type></entry>
-      <entry><literal><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.oid</literal></entry>
-      <entry>List of node OIDs of the node group</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-<!## end>
-<!## XL>
- <sect1 id="catalog-pgxc-class">
-  <title><structname>pgxc_class</structname></title>
-
-  <indexterm zone="catalog-pgxc-class">
-   <primary>pgxc_class</primary>
-  </indexterm>
-
-&xlonly;
-  <para>
-   The catalog <structname>pgxc_class</structname> stores information
-   whether each table is replicated or distributed, as well as
-   distribution method and the distribution column.
-  </para>
-
-  <table>
-   <title><structname>pgxc_class</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>pcrelid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><link linkend="catalog-pg-class"><structname>pg_class</structname></link><literal>.oid</literal></entry>
-      <entry>OID of the table</entry>
-     </row>
-
-     <row>
-      <entry><structfield>pclocatortype</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       Type of locator.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>pcattnum</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       Column number of used as distribution key.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>pchashalgorithm</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       Indicates hashing algorithm used to distribute the tuples.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>pchashbuckets</structfield></entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       Indicates the number of hash buckets used to distribute duple.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>nodeoids</structfield></entry>
-      <entry><type>oidvector</type></entry>
-      <entry><literal><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.oid</literal></entry>
-      <entry>
-       List of node OIDs where table is located.
-       This list is ordered by <literal><link linkend="catalog-pgxc-node"><structname>
-       pgxc_node</structname></link>.node_name</literal>. This list is then
-       indexed in information in user session cache and reused as a node target list
-       when doing SQL operations on cluster tables.
-      </entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="catalog-pgxc-node">
-  <title><structname>pgxc_node</structname></title>
-
-  <indexterm zone="catalog-pgxc-node">
-   <primary>pgxc_node</primary>
-  </indexterm>
-
-&xlonly;
-  <para>
-   The catalog <structname>pgxc_node</structname> stores information
-   about cluster node information, such as connection information with
-   node port and host, node name, primary and preferred nodes.
-  </para>
-
-  <table>
-   <title><structname>pgxc_node</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>node_name</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of cluster node</entry>
-     </row>
-
-     <row>
-      <entry><structfield>node_type</structfield></entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>Type of cluster node.
-       It is <literal>C</literal> for a Coordinator.
-       It is <literal>D</literal> for a Datanode.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>node_port</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>Port number of cluster node</entry>
-     </row>
-
-     <row>
-      <entry><structfield>node_host</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Host name or IP number of cluster node</entry>
-     </row>
-
-     <row>
-      <entry><structfield>nodeis_primary</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Defines if node is a primary node.
-       Only Datanode can be a primary node.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>nodeis_preferred</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Defines if node is a preferred node.
-       Only a Datanode can be a preferred node.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>node_id</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>Integer node identifier of node.
-       It is generated when node is created.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="catalog-pgxc-group">
-  <title><structname>pgxc_group</structname></title>
-
-  <indexterm zone="catalog-pgxc-group">
-   <primary>pgxc_group</primary>
-  </indexterm>
-
-&xlonly;
-  <para>
-   The catalog <structname>pgxc_group</structname> stores information
-   about cluster node group information, which is a list of cluster node
-   OIDs. Groups can be used as aliases.
-  </para>
-
-  <table>
-   <title><structname>pgxc_group</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>group_name</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of cluster node group</entry>
-     </row>
-
-     <row>
-      <entry><structfield>group_members</structfield></entry>
-      <entry><type>oidvector</type></entry>
-      <entry><literal><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.oid</literal></entry>
-      <entry>List of node OIDs of the node group</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-<!## end>
-
- <sect1 id="views-overview">
-  <title>System Views</title>
-
-&common;
-  <para>
-   In addition to the system catalogs, <productname>PostgreSQL</productname>
-   provides a number of built-in views.  Some system views provide convenient
-   access to some commonly used queries on the system catalogs.  Other views
-   provide access to internal server state.
-  </para>
-
-  <para>
-   The information schema (<xref linkend="information-schema">) provides
-   an alternative set of views which overlap the functionality of the system
-   views.  Since the information schema is SQL-standard whereas the views
-   described here are <productname>PostgreSQL</productname>-specific,
-   it's usually better to use the information schema if it provides all
-   the information you need.
-  </para>
-
-  <para>
-   <xref linkend="view-table"> lists the system views described here.
-   More detailed documentation of each view follows below.
-   There are some additional views that provide access to the results of
-   the statistics collector; they are described in <xref
-   linkend="monitoring-stats-views-table">.
-  </para>
-
-  <para>
-   Except where noted, all the views described here are read-only.
-  </para>
-
-  <table id="view-table">
-   <title>System Views</title>
-
-   <tgroup cols="2">
-    <thead>
-     <row>
-      <entry>View Name</entry>
-      <entry>Purpose</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><link linkend="view-pg-available-extensions"><structname>pg_available_extensions</structname></link></entry>
-      <entry>available extensions</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-available-extension-versions"><structname>pg_available_extension_versions</structname></link></entry>
-      <entry>available versions of extensions</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-cursors"><structname>pg_cursors</structname></link></entry>
-      <entry>open cursors</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-group"><structname>pg_group</structname></link></entry>
-      <entry>groups of database users</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-indexes"><structname>pg_indexes</structname></link></entry>
-      <entry>indexes</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-locks"><structname>pg_locks</structname></link></entry>
-      <entry>currently held locks</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-prepared-statements"><structname>pg_prepared_statements</structname></link></entry>
-      <entry>prepared statements</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-prepared-xacts"><structname>pg_prepared_xacts</structname></link></entry>
-      <entry>prepared transactions</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-roles"><structname>pg_roles</structname></link></entry>
-      <entry>database roles</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-rules"><structname>pg_rules</structname></link></entry>
-      <entry>rules</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-seclabels"><structname>pg_seclabels</structname></link></entry>
-      <entry>security labels</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-settings"><structname>pg_settings</structname></link></entry>
-      <entry>parameter settings</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-shadow"><structname>pg_shadow</structname></link></entry>
-      <entry>database users</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-stats"><structname>pg_stats</structname></link></entry>
-      <entry>planner statistics</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-tables"><structname>pg_tables</structname></link></entry>
-      <entry>tables</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-timezone-abbrevs"><structname>pg_timezone_abbrevs</structname></link></entry>
-      <entry>time zone abbreviations</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-timezone-names"><structname>pg_timezone_names</structname></link></entry>
-      <entry>time zone names</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-user"><structname>pg_user</structname></link></entry>
-      <entry>database users</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-user-mappings"><structname>pg_user_mappings</structname></link></entry>
-      <entry>user mappings</entry>
-     </row>
-
-     <row>
-      <entry><link linkend="view-pg-views"><structname>pg_views</structname></link></entry>
-      <entry>views</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="view-pg-available-extensions">
-  <title><structname>pg_available_extensions</structname></title>
-
-  <indexterm zone="view-pg-available-extensions">
-   <primary>pg_available_extensions</primary>
-  </indexterm>
-
-  <para>
-   The <structname>pg_available_extensions</structname> view lists the
-   extensions that are available for installation.
-   See also the
-   <link linkend="catalog-pg-extension"><structname>pg_extension</structname></link>
-   catalog, which shows the extensions currently installed.
-  </para>
-
-  <table>
-   <title><structname>pg_available_extensions</> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>name</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry>Extension name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>default_version</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Name of default version, or <literal>NULL</literal> if none is
-       specified</entry>
-     </row>
-
-     <row>
-      <entry><structfield>installed_version</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Currently installed version of the extension,
-       or <literal>NULL</literal> if not installed</entry>
-     </row>
-
-     <row>
-      <entry><structfield>comment</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Comment string from the extension's control file</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The <structname>pg_available_extensions</structname> view is read only.
-  </para>
- </sect1>
-
- <sect1 id="view-pg-available-extension-versions">
-  <title><structname>pg_available_extension_versions</structname></title>
-
-  <indexterm zone="view-pg-available-extension-versions">
-   <primary>pg_available_extension_versions</primary>
-  </indexterm>
-
-  <para>
-   The <structname>pg_available_extension_versions</structname> view lists the
-   specific extension versions that are available for installation.
-   See also the <link
-   linkend="catalog-pg-extension"><structname>pg_extension</structname></link>
-   catalog, which shows the extensions currently installed.
-  </para>
-
-  <table>
-   <title><structname>pg_available_extension_versions</> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>name</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry>Extension name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>version</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Version name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>installed</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>True if this version of this extension is currently
-       installed</entry>
-     </row>
-
-     <row>
-      <entry><structfield>superuser</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>True if only superusers are allowed to install this extension</entry>
-     </row>
-
-     <row>
-      <entry><structfield>relocatable</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>True if extension can be relocated to another schema</entry>
-     </row>
-
-     <row>
-      <entry><structfield>schema</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry>Name of the schema that the extension must be installed into,
-       or <literal>NULL</literal> if partially or fully relocatable</entry>
-     </row>
-
-     <row>
-      <entry><structfield>requires</structfield></entry>
-      <entry><type>name[]</type></entry>
-      <entry>Names of prerequisite extensions,
-       or <literal>NULL</literal> if none</entry>
-     </row>
-
-     <row>
-      <entry><structfield>comment</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Comment string from the extension's control file</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The <structname>pg_available_extension_versions</structname> view is read
-   only.
-  </para>
- </sect1>
-
- <sect1 id="view-pg-cursors">
-  <title><structname>pg_cursors</structname></title>
-
-  <indexterm zone="view-pg-cursors">
-   <primary>pg_cursors</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The <structname>pg_cursors</structname> view lists the cursors that
-   are currently available. Cursors can be defined in several ways:
-   <itemizedlist>
-    <listitem>
-     <para>
-      via the <xref linkend="sql-declare">
-      statement in SQL
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      via the Bind message in the frontend/backend protocol, as
-      described in <xref linkend="protocol-flow-ext-query">
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      via the Server Programming Interface (SPI), as described in
-      <xref linkend="spi-interface">
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   The <structname>pg_cursors</structname> view displays cursors
-   created by any of these means. Cursors only exist for the duration
-   of the transaction that defines them, unless they have been
-   declared <literal>WITH HOLD</literal>. Therefore non-holdable
-   cursors are only present in the view until the end of their
-   creating transaction.
-
-   <note>
-    <para>
-     Cursors are used internally to implement some of the components
-     of <productname>PostgreSQL</>, such as procedural languages.
-     Therefore, the <structname>pg_cursors</> view might include cursors
-     that have not been explicitly created by the user.
-    </para>
-   </note>
-  </para>
-
-  <table>
-   <title><structname>pg_cursors</> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>name</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>The name of the cursor</entry>
-     </row>
-
-     <row>
-      <entry><structfield>statement</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>The verbatim query string submitted to declare this cursor</entry>
-     </row>
-
-     <row>
-      <entry><structfield>is_holdable</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry>
-       <literal>true</literal> if the cursor is holdable (that is, it
-       can be accessed after the transaction that declared the cursor
-       has committed); <literal>false</literal> otherwise
-       </entry>
-     </row>
-
-     <row>
-      <entry><structfield>is_binary</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry>
-       <literal>true</literal> if the cursor was declared
-       <literal>BINARY</literal>; <literal>false</literal>
-       otherwise
-       </entry>
-     </row>
-
-     <row>
-      <entry><structfield>is_scrollable</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry>
-       <literal>true</> if the cursor is scrollable (that is, it
-       allows rows to be retrieved in a nonsequential manner);
-       <literal>false</literal> otherwise
-       </entry>
-     </row>
-
-     <row>
-      <entry><structfield>creation_time</structfield></entry>
-      <entry><type>timestamptz</type></entry>
-      <entry>The time at which the cursor was declared</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The <structname>pg_cursors</structname> view is read only.
-  </para>
-
- </sect1>
-
- <sect1 id="view-pg-group">
-  <title><structname>pg_group</structname></title>
-
-  <indexterm zone="view-pg-group">
-   <primary>pg_group</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_group</structname> exists for backwards
-   compatibility: it emulates a catalog that existed in
-   <productname>PostgreSQL</productname> before version 8.1.
-   It shows the names and members of all roles that are marked as not
-   <structfield>rolcanlogin</>, which is an approximation to the set
-   of roles that are being used as groups.
-  </para>
-
-  <table>
-   <title><structname>pg_group</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>groname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.rolname</literal></entry>
-      <entry>Name of the group</entry>
-     </row>
-
-     <row>
-      <entry><structfield>grosysid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>ID of this group</entry>
-     </row>
-
-     <row>
-      <entry><structfield>grolist</structfield></entry>
-      <entry><type>oid[]</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>An array containing the IDs of the roles in this group</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="view-pg-indexes">
-  <title><structname>pg_indexes</structname></title>
-
-  <indexterm zone="view-pg-indexes">
-   <primary>pg_indexes</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_indexes</structname> provides access to
-   useful information about each index in the database.
-  </para>
-
-  <table>
-   <title><structname>pg_indexes</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>schemaname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.nspname</literal></entry>
-      <entry>Name of schema containing table and index</entry>
-     </row>
-     <row>
-      <entry><structfield>tablename</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.relname</literal></entry>
-      <entry>Name of table the index is for</entry>
-     </row>
-     <row>
-      <entry><structfield>indexname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.relname</literal></entry>
-      <entry>Name of index</entry>
-     </row>
-     <row>
-      <entry><structfield>tablespace</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-tablespace"><structname>pg_tablespace</structname></link>.spcname</literal></entry>
-      <entry>Name of tablespace containing index (null if default for database)</entry>
-     </row>
-     <row>
-      <entry><structfield>indexdef</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Index definition (a reconstructed <command>CREATE INDEX</command>
-      command)</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="view-pg-locks">
-  <title><structname>pg_locks</structname></title>
-
-  <indexterm zone="view-pg-locks">
-   <primary>pg_locks</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_locks</structname> provides access to
-   information about the locks held by open transactions within the
-   database server.  See <xref linkend="mvcc"> for more discussion
-   of locking.
-  </para>
-
-  <para>
-   <structname>pg_locks</structname> contains one row per active lockable
-   object, requested lock mode, and relevant transaction.  Thus, the same
-   lockable object might
-   appear many times, if multiple transactions are holding or waiting
-   for locks on it.  However, an object that currently has no locks on it
-   will not appear at all.
-  </para>
-
-  <para>
-   There are several distinct types of lockable objects:
-   whole relations (e.g., tables), individual pages of relations,
-   individual tuples of relations,
-   transaction IDs (both virtual and permanent IDs),
-   and general database objects (identified by class OID and object OID,
-   in the same way as in <structname>pg_description</structname> or
-   <structname>pg_depend</structname>).  Also, the right to extend a
-   relation is represented as a separate lockable object.
-  </para>
-
-  <table>
-   <title><structname>pg_locks</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>locktype</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       Type of the lockable object:
-       <literal>relation</>,
-       <literal>extend</>,
-       <literal>page</>,
-       <literal>tuple</>,
-       <literal>transactionid</>,
-       <literal>virtualxid</>,
-       <literal>object</>,
-       <literal>userlock</>, or
-       <literal>advisory</>
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>database</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-database"><structname>pg_database</structname></link>.oid</literal></entry>
-      <entry>
-       OID of the database in which the object exists, or
-       zero if the object is a shared object, or
-       null if the object is a transaction ID
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>relation</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>
-       OID of the relation, or null if the object is not
-       a relation or part of a relation
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>page</structfield></entry>
-      <entry><type>integer</type></entry>
-      <entry></entry>
-      <entry>
-       Page number within the relation, or null if the object
-       is not a tuple or relation page
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>tuple</structfield></entry>
-      <entry><type>smallint</type></entry>
-      <entry></entry>
-      <entry>
-       Tuple number within the page, or null if the object is not a tuple
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>virtualxid</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       Virtual ID of a transaction, or null if the object is not a
-       virtual transaction ID
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>transactionid</structfield></entry>
-      <entry><type>xid</type></entry>
-      <entry></entry>
-      <entry>
-       ID of a transaction, or null if the object is not a transaction ID
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>classid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>
-       OID of the system catalog containing the object, or null if the
-       object is not a general database object
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>objid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry>any OID column</entry>
-      <entry>
-       OID of the object within its system catalog, or null if the
-       object is not a general database object.
-       For advisory locks it is used to distinguish the two key
-       spaces (1 for an int8 key, 2 for two int4 keys).
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>objsubid</structfield></entry>
-      <entry><type>smallint</type></entry>
-      <entry></entry>
-      <entry>
-       For a table column, this is the column number (the
-       <structfield>classid</> and <structfield>objid</> refer to the
-       table itself).  For all other object types, this column is
-       zero.  Null if the object is not a general database object
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>virtualtransaction</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       Virtual ID of the transaction that is holding or awaiting this lock
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>pid</structfield></entry>
-      <entry><type>integer</type></entry>
-      <entry></entry>
-      <entry>
-       Process ID of the server process holding or awaiting this
-       lock.  Null if the lock is held by a prepared transaction.
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>mode</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Name of the lock mode held or desired by this process (see <xref
-      linkend="locking-tables"> and <xref linkend="xact-serializable">)</entry>
-     </row>
-     <row>
-      <entry><structfield>granted</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry></entry>
-      <entry>True if lock is held, false if lock is awaited</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   <structfield>granted</structfield> is true in a row representing a lock
-   held by the indicated transaction.  False indicates that this transaction is
-   currently waiting to acquire this lock, which implies that some other
-   transaction is holding a conflicting lock mode on the same lockable object.
-   The waiting transaction will sleep until the other lock is released (or a
-   deadlock situation is detected). A single transaction can be waiting to
-   acquire at most one lock at a time.
-  </para>
-
-  <para>
-   Every transaction holds an exclusive lock on its virtual transaction ID for
-   its entire duration.  If a permanent ID is assigned to the transaction
-   (which normally happens only if the transaction changes the state of the
-   database), it also holds an exclusive lock on its permanent transaction ID
-   until it ends.  When one transaction finds it necessary to wait specifically
-   for another transaction, it does so by attempting to acquire share lock on
-   the other transaction ID (either virtual or permanent ID depending on the
-   situation). That will succeed only when the other transaction
-   terminates and releases its locks.
-  </para>
-
-  <para>
-   Although tuples are a lockable type of object,
-   information about row-level locks is stored on disk, not in memory,
-   and therefore row-level locks normally do not appear in this view.
-   If a transaction is waiting for a
-   row-level lock, it will usually appear in the view as waiting for the
-   permanent transaction ID of the current holder of that row lock.
-  </para>
-
-  <para>
-   Advisory locks can be acquired on keys consisting of either a single
-   <type>bigint</type> value or two integer values.  A <type>bigint</type> key is displayed with its
-   high-order half in the <structfield>classid</> column, its low-order half
-   in the <structfield>objid</> column, and <structfield>objsubid</> equal
-   to 1.  Integer keys are displayed with the first key in the
-   <structfield>classid</> column, the second key in the <structfield>objid</>
-   column, and <structfield>objsubid</> equal to 2.  The actual meaning of
-   the keys is up to the user.  Advisory locks are local to each database,
-   so the <structfield>database</> column is meaningful for an advisory lock.
-  </para>
-
-  <para>
-   When the <structname>pg_locks</structname> view is accessed, the
-   internal lock manager data structures are momentarily locked, and
-   a copy is made for the view to display.  This ensures that the
-   view produces a consistent set of results, while not blocking
-   normal lock manager operations longer than necessary.  Nonetheless
-   there could be some impact on database performance if this view is
-   frequently accessed.
-  </para>
-
-  <para>
-   <structname>pg_locks</structname> provides a global view of all locks
-   in the database cluster, not only those relevant to the current database.
-   Although its <structfield>relation</structfield> column can be joined
-   against <structname>pg_class</>.<structfield>oid</> to identify locked
-   relations, this will only work correctly for relations in the current
-   database (those for which the <structfield>database</structfield> column
-   is either the current database's OID or zero).
-  </para>
-
-  <para>
-   The <structfield>pid</structfield> column can be joined to the
-   <structfield>procpid</structfield> column of the
-   <structname>pg_stat_activity</structname> view to get more
-   information on the session holding or waiting to hold each lock.
-   Also, if you are using prepared transactions, the
-   <structfield>transaction</> column can be joined to the
-   <structfield>transaction</structfield> column of the
-   <structname>pg_prepared_xacts</structname> view to get more
-   information on prepared transactions that hold locks.
-   (A prepared transaction can never be waiting for a lock,
-   but it continues to hold the locks it acquired while running.)
-  </para>
-
- </sect1>
-
- <sect1 id="view-pg-prepared-statements">
-  <title><structname>pg_prepared_statements</structname></title>
-
-  <indexterm zone="view-pg-prepared-statements">
-   <primary>pg_prepared_statements</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The <structname>pg_prepared_statements</structname> view displays
-   all the prepared statements that are available in the current
-   session. See <xref linkend="sql-prepare"> for more information about prepared
-   statements.
-  </para>
-
-  <para>
-   <structname>pg_prepared_statements</structname> contains one row
-   for each prepared statement. Rows are added to the view when a new
-   prepared statement is created and removed when a prepared statement
-   is released (for example, via the <xref linkend="sql-deallocate"> command).
-  </para>
-
-  <table>
-   <title><structname>pg_prepared_statements</> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>name</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>
-       The identifier of the prepared statement
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>statement</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>
-       The query string submitted by the client to create this
-       prepared statement. For prepared statements created via SQL,
-       this is the <command>PREPARE</command> statement submitted by
-       the client. For prepared statements created via the
-       frontend/backend protocol, this is the text of the prepared
-       statement itself.
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>prepare_time</structfield></entry>
-      <entry><type>timestamptz</type></entry>
-      <entry>
-       The time at which the prepared statement was created
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>parameter_types</structfield></entry>
-      <entry><type>regtype[]</type></entry>
-      <entry>
-       The expected parameter types for the prepared statement in the
-       form of an array of <type>regtype</type>. The OID corresponding
-       to an element of this array can be obtained by casting the
-       <type>regtype</type> value to <type>oid</type>.
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>from_sql</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry>
-       <literal>true</literal> if the prepared statement was created
-       via the <command>PREPARE</command> SQL statement;
-       <literal>false</literal> if the statement was prepared via the
-       frontend/backend protocol
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The <structname>pg_prepared_statements</structname> view is read only.
-  </para>
- </sect1>
-
- <sect1 id="view-pg-prepared-xacts">
-  <title><structname>pg_prepared_xacts</structname></title>
-
-  <indexterm zone="view-pg-prepared-xacts">
-   <primary>pg_prepared_xacts</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_prepared_xacts</structname> displays
-   information about transactions that are currently prepared for two-phase
-   commit (see <xref linkend="sql-prepare-transaction"> for details).
-  </para>
-
-  <para>
-   <structname>pg_prepared_xacts</structname> contains one row per prepared
-   transaction.  An entry is removed when the transaction is committed or
-   rolled back.
-  </para>
-
-  <table>
-   <title><structname>pg_prepared_xacts</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>transaction</structfield></entry>
-      <entry><type>xid</type></entry>
-      <entry></entry>
-      <entry>
-       Numeric transaction identifier of the prepared transaction
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>gid</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       Global transaction identifier that was assigned to the transaction
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>prepared</structfield></entry>
-      <entry><type>timestamp with time zone</type></entry>
-      <entry></entry>
-      <entry>
-       Time at which the transaction was prepared for commit
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>owner</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.rolname</literal></entry>
-      <entry>
-       Name of the user that executed the transaction
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>database</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-database"><structname>pg_database</structname></link>.datname</literal></entry>
-      <entry>
-       Name of the database in which the transaction was executed
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   When the <structname>pg_prepared_xacts</structname> view is accessed, the
-   internal transaction manager data structures are momentarily locked, and
-   a copy is made for the view to display.  This ensures that the
-   view produces a consistent set of results, while not blocking
-   normal operations longer than necessary.  Nonetheless
-   there could be some impact on database performance if this view is
-   frequently accessed.
-  </para>
-
- </sect1>
-
- <sect1 id="view-pg-roles">
-  <title><structname>pg_roles</structname></title>
-
-  <indexterm zone="view-pg-roles">
-   <primary>pg_roles</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_roles</structname> provides access to
-   information about database roles.  This is simply a publicly
-   readable view of
-   <link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>
-   that blanks out the password field.
-  </para>
-
-  <para>
-   This view explicitly exposes the OID column of the underlying table,
-   since that is needed to do joins to other catalogs.
-  </para>
-
-  <table>
-   <title><structname>pg_roles</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>rolname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Role name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolsuper</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Role has superuser privileges</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolinherit</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Role automatically inherits privileges of roles it is a
-       member of</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolcreaterole</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Role can create more roles</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolcreatedb</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Role can create databases</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolcatupdate</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       Role can update system catalogs directly.  (Even a superuser cannot do
-       this unless this column is true.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolcanlogin</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       Role can log in. That is, this role can be given as the initial
-       session authorization identifier
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolconnlimit</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       For roles that can log in, this sets maximum number of concurrent
-       connections this role can make.  -1 means no limit.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolpassword</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Not the password (always reads as <literal>********</>)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rolvaliduntil</structfield></entry>
-      <entry><type>timestamptz</type></entry>
-      <entry></entry>
-      <entry>Password expiry time (only used for password authentication);
-       null if no expiration</entry>
-     </row>
-
-     <row>
-      <entry><structfield>oid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>ID of role</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="view-pg-rules">
-  <title><structname>pg_rules</structname></title>
-
-  <indexterm zone="view-pg-rules">
-   <primary>pg_rules</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_rules</structname> provides access to
-   useful information about query rewrite rules.
-  </para>
-
-  <table>
-   <title><structname>pg_rules</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>schemaname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.nspname</literal></entry>
-      <entry>Name of schema containing table</entry>
-     </row>
-     <row>
-      <entry><structfield>tablename</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.relname</literal></entry>
-      <entry>Name of table the rule is for</entry>
-     </row>
-     <row>
-      <entry><structfield>rulename</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-rewrite"><structname>pg_rewrite</structname></link>.rulename</literal></entry>
-      <entry>Name of rule</entry>
-     </row>
-     <row>
-      <entry><structfield>definition</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Rule definition (a reconstructed creation command)</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The <structname>pg_rules</> view excludes the <literal>ON SELECT</> rules
-   of views; those can be seen in <structname>pg_views</>.
-  </para>
-
- </sect1>
-
- <sect1 id="view-pg-seclabels">
-  <title><structname>pg_seclabels</structname></title>
-
-  <indexterm zone="view-pg-seclabels">
-   <primary>pg_seclabels</primary>
-  </indexterm>
-
-  <para>
-   The view <structname>pg_seclabels</structname> provides information about
-   security labels.  It as an easier-to-query version of the
-   <link linkend="catalog-pg-seclabel"><structname>pg_seclabel</></> catalog.
-  </para>
-
-  <table>
-   <title><structname>pg_seclabels</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>objoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry>any OID column</entry>
-      <entry>The OID of the object this security label pertains to</entry>
-     </row>
-     <row>
-      <entry><structfield>classoid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.oid</literal></entry>
-      <entry>The OID of the system catalog this object appears in</entry>
-     </row>
-     <row>
-      <entry><structfield>objsubid</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       For a security label on a table column, this is the column number (the
-       <structfield>objoid</> and <structfield>classoid</> refer to
-       the table itself).  For all other object types, this column is
-       zero.
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>objtype</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-         The type of object to which this label applies, as text.
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>objnamespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the namespace for this object, if applicable;
-       otherwise NULL.
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>objname</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       The name of the object to which this label applies, as text.
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>provider</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry><literal><link linkend="catalog-pg-seclabel"><structname>pg_seclabel</structname></link>.provider</literal></entry>
-      <entry>The label provider associated with this label.</entry>
-     </row>
-     <row>
-      <entry><structfield>label</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry><literal><link linkend="catalog-pg-seclabel"><structname>pg_seclabel</structname></link>.label</literal></entry>
-      <entry>The security label applied to this object.</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="view-pg-settings">
-  <title><structname>pg_settings</structname></title>
-
-  <indexterm zone="view-pg-settings">
-   <primary>pg_settings</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_settings</structname> provides access to
-   run-time parameters of the server.  It is essentially an alternative
-   interface to the <xref linkend="sql-show">
-   and <xref linkend="sql-set"> commands.
-   It also provides access to some facts about each parameter that are
-   not directly available from <command>SHOW</>, such as minimum and
-   maximum values.
-  </para>
-
-  <table>
-   <title><structname>pg_settings</> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>name</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Run-time configuration parameter name</entry>
-     </row>
-     <row>
-      <entry><structfield>setting</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Current value of the parameter</entry>
-     </row>
-     <row>
-      <entry><structfield>unit</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Implicit unit of the parameter</entry>
-     </row>
-     <row>
-      <entry><structfield>category</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Logical group of the parameter</entry>
-     </row>
-     <row>
-      <entry><structfield>short_desc</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>A brief description of the parameter</entry>
-     </row>
-     <row>
-      <entry><structfield>extra_desc</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Additional, more detailed, description of the parameter</entry>
-     </row>
-     <row>
-      <entry><structfield>context</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Context required to set the parameter's value (see below)</entry>
-     </row>
-     <row>
-      <entry><structfield>vartype</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Parameter type (<literal>bool</>, <literal>enum</>,
-       <literal>integer</>, <literal>real</>, or <literal>string</>)
-      </entry>
-     </row>
-     <row>
-      <entry><structfield>source</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Source of the current parameter value</entry>
-     </row>
-     <row>
-      <entry><structfield>min_val</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Minimum allowed value of the parameter (null for non-numeric
-      values)</entry>
-     </row>
-     <row>
-      <entry><structfield>max_val</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Maximum allowed value of the parameter (null for non-numeric
-      values)</entry>
-     </row>
-     <row>
-      <entry><structfield>enumvals</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry>Allowed values of an enum parameter (null for non-enum
-      values)</entry>
-     </row>
-     <row>
-      <entry><structfield>boot_val</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Parameter value assumed at server startup if the parameter is
-      not otherwise set</entry>
-     </row>
-     <row>
-      <entry><structfield>reset_val</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Value that <command>RESET</command> would reset the parameter to
-      in the current session</entry>
-     </row>
-     <row>
-      <entry><structfield>sourcefile</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Configuration file the current value was set in (null for
-      values set from sources other than configuration files, or when
-      examined by a non-superuser);
-      helpful when using <literal>include</> directives in configuration files</entry>
-     </row>
-     <row>
-      <entry><structfield>sourceline</structfield></entry>
-      <entry><type>integer</type></entry>
-      <entry>Line number within the configuration file the current value was
-      set at (null for values set from sources other than configuration files,
-      or when examined by a non-superuser)
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   There are several possible values of <structfield>context</structfield>.
-   In order of decreasing difficulty of changing the setting, they are:
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>internal</literal></term>
-    <listitem>
-     <para>
-      These settings cannot be changed directly; they reflect internally
-      determined values.  Some of them may be adjustable by rebuilding the
-      server with different configuration options, or by changing options
-      supplied to <command>initdb</command>.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry>
-    <term><literal>postmaster</literal></term>
-    <listitem>
-     <para>
-      These settings can only be applied when the server starts, so any change
-      requires restarting the server.  Values for these settings are typically
-      stored in the <filename>postgresql.conf</filename> file, or passed on
-      the command line when starting the server.  Of course, settings with any
-      of the lower <structfield>context</structfield> types can also be
-      set at server start time.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry>
-    <term><literal>sighup</literal></term>
-    <listitem>
-     <para>
-      Changes to these settings can be made in
-      <filename>postgresql.conf</filename> without restarting the server.
-      Send a <systemitem>SIGHUP</systemitem> signal to the postmaster to
-      cause it to re-read <filename>postgresql.conf</filename> and apply
-      the changes.  The postmaster will also forward the
-      <systemitem>SIGHUP</systemitem> signal to its child processes so that
-      they all pick up the new value.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry>
-    <term><literal>backend</literal></term>
-    <listitem>
-     <para>
-      Changes to these settings can be made in
-      <filename>postgresql.conf</filename> without restarting the server;
-      they can also be set for a particular session in the connection request
-      packet (for example, via <application>libpq</>'s <literal>PGOPTIONS</>
-      environment variable).  However, these settings never change in a
-      session after it is started.  If you change them in
-      <filename>postgresql.conf</filename>, send a
-      <systemitem>SIGHUP</systemitem> signal to the postmaster to cause it to
-      re-read <filename>postgresql.conf</filename>.  The new values will only
-      affect subsequently-launched sessions.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry>
-    <term><literal>superuser</literal></term>
-    <listitem>
-     <para>
-      These settings can be set from <filename>postgresql.conf</filename>,
-      or within a session via the <command>SET</> command; but only superusers
-      can change them via <command>SET</>.  Changes in
-      <filename>postgresql.conf</filename> will affect existing sessions
-      only if no session-local value has been established with <command>SET</>.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry>
-    <term><literal>user</literal></term>
-    <listitem>
-     <para>
-      These settings can be set from <filename>postgresql.conf</filename>,
-      or within a session via the <command>SET</> command.  Any user is
-      allowed to change his session-local value.  Changes in
-      <filename>postgresql.conf</filename> will affect existing sessions
-      only if no session-local value has been established with <command>SET</>.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   See <xref linkend="config-setting"> for more information about the various
-   ways to change these parameters.
-  </para>
-
-  <para>
-   The <structname>pg_settings</structname> view cannot be inserted into or
-   deleted from, but it can be updated.  An <command>UPDATE</command> applied
-   to a row of <structname>pg_settings</structname> is equivalent to executing
-   the <xref linkend="sql-set"> command on that named
-   parameter. The change only affects the value used by the current
-   session. If an <command>UPDATE</command> is issued within a transaction
-   that is later aborted, the effects of the <command>UPDATE</command> command
-   disappear when the transaction is rolled back. Once the surrounding
-   transaction is committed, the effects will persist until the end of the
-   session, unless overridden by another <command>UPDATE</command> or
-   <command>SET</command>.
-  </para>
-
- </sect1>
-
- <sect1 id="view-pg-shadow">
-  <title><structname>pg_shadow</structname></title>
-
-  <indexterm zone="view-pg-shadow">
-   <primary>pg_shadow</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_shadow</structname> exists for backwards
-   compatibility: it emulates a catalog that existed in
-   <productname>PostgreSQL</productname> before version 8.1.
-   It shows properties of all roles that are marked as
-   <structfield>rolcanlogin</> in
-   <link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.
-  </para>
-
-  <para>
-   The name stems from the fact that this table
-   should not be readable by the public since it contains passwords.
-   <link linkend="view-pg-user"><structname>pg_user</structname></link>
-   is a publicly readable view on
-   <structname>pg_shadow</structname> that blanks out the password field.
-  </para>
-
-  <table>
-   <title><structname>pg_shadow</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>usename</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.rolname</literal></entry>
-      <entry>User name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>usesysid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>ID of this user</entry>
-     </row>
-
-     <row>
-      <entry><structfield>usecreatedb</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>User can create databases</entry>
-     </row>
-
-     <row>
-      <entry><structfield>usesuper</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>User is a superuser</entry>
-     </row>
-
-     <row>
-      <entry><structfield>usecatupd</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       User can update system catalogs.  (Even a superuser cannot do
-       this unless this column is true.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>passwd</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Password (possibly encrypted); null if none.  See
-      <link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>
-      for details of how encrypted passwords are stored.</entry>
-     </row>
-
-     <row>
-      <entry><structfield>valuntil</structfield></entry>
-      <entry><type>abstime</type></entry>
-      <entry></entry>
-      <entry>Password expiry time (only used for password authentication)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>useconfig</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>Session defaults for run-time configuration variables</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="view-pg-stats">
-  <title><structname>pg_stats</structname></title>
-
-  <indexterm zone="view-pg-stats">
-   <primary>pg_stats</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_stats</structname> provides access to
-   the information stored in the <link
-   linkend="catalog-pg-statistic"><structname>pg_statistic</structname></link>
-   catalog.  This view allows access only to rows of
-   <structname>pg_statistic</structname> that correspond to tables the
-   user has permission to read, and therefore it is safe to allow public
-   read access to this view.
-  </para>
-
-  <para>
-   <structname>pg_stats</structname> is also designed to present the
-   information in a more readable format than the underlying catalog
-   &mdash; at the cost that its schema must be extended whenever new slot types
-   are defined for <structname>pg_statistic</structname>.
-  </para>
-
-  <table>
-   <title><structname>pg_stats</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>schemaname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.nspname</literal></entry>
-      <entry>Name of schema containing table</entry>
-     </row>
-
-     <row>
-      <entry><structfield>tablename</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.relname</literal></entry>
-      <entry>Name of table</entry>
-     </row>
-
-     <row>
-      <entry><structfield>attname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-attribute"><structname>pg_attribute</structname></link>.attname</literal></entry>
-      <entry>Name of the column described by this row</entry>
-     </row>
-
-     <row>
-      <entry><structfield>inherited</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>If true, this row includes inheritance child columns, not just the
-       values in the specified table</entry>
-     </row>
-
-     <row>
-      <entry><structfield>null_frac</structfield></entry>
-      <entry><type>real</type></entry>
-      <entry></entry>
-      <entry>Fraction of column entries that are null</entry>
-     </row>
-
-     <row>
-      <entry><structfield>avg_width</structfield></entry>
-      <entry><type>integer</type></entry>
-      <entry></entry>
-      <entry>Average width in bytes of column's entries</entry>
-     </row>
-
-     <row>
-      <entry><structfield>n_distinct</structfield></entry>
-      <entry><type>real</type></entry>
-      <entry></entry>
-      <entry>
-       If greater than zero, the estimated number of distinct values in the
-       column.  If less than zero, the negative of the number of distinct
-       values divided by the number of rows.  (The negated form is used when
-       <command>ANALYZE</> believes that the number of distinct values is
-       likely to increase as the table grows; the positive form is used when
-       the column seems to have a fixed number of possible values.)  For
-       example, -1 indicates a unique column in which the number of distinct
-       values is the same as the number of rows.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>most_common_vals</structfield></entry>
-      <entry><type>anyarray</type></entry>
-      <entry></entry>
-      <entry>
-       A list of the most common values in the column. (Null if
-       no values seem to be more common than any others.)
-       For some data types such as <type>tsvector</>, this is a list of
-       the most common element values rather than values of the type itself.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>most_common_freqs</structfield></entry>
-      <entry><type>real[]</type></entry>
-      <entry></entry>
-      <entry>
-       A list of the frequencies of the most common values or elements,
-       i.e., number of occurrences of each divided by total number of rows.
-       (Null when <structfield>most_common_vals</structfield> is.)
-       For some data types such as <type>tsvector</>, it can also store some
-       additional information, making it longer than the
-       <structfield>most_common_vals</> array.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>histogram_bounds</structfield></entry>
-      <entry><type>anyarray</type></entry>
-      <entry></entry>
-      <entry>
-       A list of values that divide the column's values into groups of
-       approximately equal population.  The values in
-       <structfield>most_common_vals</>, if present, are omitted from this
-       histogram calculation.  (This column is null if the column data type
-       does not have a <literal>&lt;</> operator or if the
-       <structfield>most_common_vals</> list accounts for the entire
-       population.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>correlation</structfield></entry>
-      <entry><type>real</type></entry>
-      <entry></entry>
-      <entry>
-       Statistical correlation between physical row ordering and
-       logical ordering of the column values.  This ranges from -1 to +1.
-       When the value is near -1 or +1, an index scan on the column will
-       be estimated to be cheaper than when it is near zero, due to reduction
-       of random access to the disk.  (This column is null if the column data
-       type does not have a <literal>&lt;</> operator.)
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The maximum number of entries in the <structfield>most_common_vals</>
-   and <structfield>histogram_bounds</> arrays can be set on a
-   column-by-column basis using the <command>ALTER TABLE SET STATISTICS</>
-   command, or globally by setting the
-   <xref linkend="guc-default-statistics-target"> run-time parameter.
-  </para>
-
- </sect1>
-
- <sect1 id="view-pg-tables">
-  <title><structname>pg_tables</structname></title>
-
-  <indexterm zone="view-pg-tables">
-   <primary>pg_tables</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_tables</structname> provides access to
-   useful information about each table in the database.
-  </para>
-
-  <table>
-   <title><structname>pg_tables</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>schemaname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.nspname</literal></entry>
-      <entry>Name of schema containing table</entry>
-     </row>
-     <row>
-      <entry><structfield>tablename</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.relname</literal></entry>
-      <entry>Name of table</entry>
-     </row>
-     <row>
-      <entry><structfield>tableowner</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.rolname</literal></entry>
-      <entry>Name of table's owner</entry>
-     </row>
-     <row>
-      <entry><structfield>tablespace</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-tablespace"><structname>pg_tablespace</structname></link>.spcname</literal></entry>
-      <entry>Name of tablespace containing table (null if default for database)</entry>
-     </row>
-     <row>
-      <entry><structfield>hasindexes</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.relhasindex</literal></entry>
-      <entry>True if table has (or recently had) any indexes</entry>
-     </row>
-     <row>
-      <entry><structfield>hasrules</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.relhasrules</literal></entry>
-      <entry>True if table has (or once had) rules</entry>
-     </row>
-     <row>
-      <entry><structfield>hastriggers</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.relhastriggers</literal></entry>
-      <entry>True if table has (or once had) triggers</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="view-pg-timezone-abbrevs">
-  <title><structname>pg_timezone_abbrevs</structname></title>
-
-  <indexterm zone="view-pg-timezone-abbrevs">
-   <primary>pg_timezone_abbrevs</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_timezone_abbrevs</structname> provides a list
-   of time zone abbreviations that are currently recognized by the datetime
-   input routines.  The contents of this view change when the
-   <xref linkend="guc-timezone-abbreviations"> run-time parameter is modified.
-  </para>
-
-  <table>
-   <title><structname>pg_timezone_abbrevs</> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>abbrev</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Time zone abbreviation</entry>
-     </row>
-     <row>
-      <entry><structfield>utc_offset</structfield></entry>
-      <entry><type>interval</type></entry>
-      <entry>Offset from UTC (positive means east of Greenwich)</entry>
-     </row>
-     <row>
-      <entry><structfield>is_dst</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry>True if this is a daylight-savings abbreviation</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="view-pg-timezone-names">
-  <title><structname>pg_timezone_names</structname></title>
-
-  <indexterm zone="view-pg-timezone-names">
-   <primary>pg_timezone_names</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_timezone_names</structname> provides a list
-   of time zone names that are recognized by <command>SET TIMEZONE</>,
-   along with their associated abbreviations, UTC offsets,
-   and daylight-savings status.
-   Unlike the abbreviations shown in <link
-   linkend="view-pg-timezone-abbrevs"><structname>pg_timezone_abbrevs</structname></link>, many of these names imply a set of daylight-savings transition
-   date rules.  Therefore, the associated information changes across local DST
-   boundaries.  The displayed information is computed based on the current
-   value of <function>CURRENT_TIMESTAMP</>.
-  </para>
-
-  <table>
-   <title><structname>pg_timezone_names</> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>name</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Time zone name</entry>
-     </row>
-     <row>
-      <entry><structfield>abbrev</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Time zone abbreviation</entry>
-     </row>
-     <row>
-      <entry><structfield>utc_offset</structfield></entry>
-      <entry><type>interval</type></entry>
-      <entry>Offset from UTC (positive means east of Greenwich)</entry>
-     </row>
-     <row>
-      <entry><structfield>is_dst</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry>True if currently observing daylight savings</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="view-pg-user">
-  <title><structname>pg_user</structname></title>
-
-  <indexterm zone="view-pg-user">
-   <primary>pg_user</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_user</structname> provides access to
-   information about database users.  This is simply a publicly
-   readable view of
-   <link linkend="view-pg-shadow"><structname>pg_shadow</structname></link>
-   that blanks out the password field.
-  </para>
-
-  <table>
-   <title><structname>pg_user</> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>usename</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry>User name</entry>
-     </row>
-
-     <row>
-      <entry><structfield>usesysid</structfield></entry>
-      <entry><type>int4</type></entry>
-      <entry>User ID (arbitrary number used to reference this user)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>usecreatedb</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>User can create databases</entry>
-     </row>
-
-     <row>
-      <entry><structfield>usesuper</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>User is a superuser</entry>
-     </row>
-
-     <row>
-      <entry><structfield>usecatupd</structfield></entry>
-      <entry><type>bool</type></entry>
-      <entry>
-       User can update system catalogs.  (Even a superuser cannot do
-       this unless this column is true.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>passwd</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry>Not the password (always reads as <literal>********</>)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>valuntil</structfield></entry>
-      <entry><type>abstime</type></entry>
-      <entry>Password expiry time (only used for password authentication)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>useconfig</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry>Session defaults for run-time configuration variables</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="view-pg-user-mappings">
-  <title><structname>pg_user_mappings</structname></title>
-
-  <indexterm zone="view-pg-user-mappings">
-   <primary>pg_user_mappings</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_user_mappings</structname> provides access
-   to information about user mappings.  This is essentially a publicly
-   readable view of
-   <link linkend="catalog-pg-user-mapping"><structname>pg_user_mapping</structname></link>
-   that leaves out the options field if the user has no rights to use
-   it.
-  </para>
-
-  <table>
-   <title><structname>pg_user_mappings</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structfield>umid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-user-mapping"><structname>pg_user_mapping</structname></link>.oid</literal></entry>
-      <entry>OID of the user mapping</entry>
-     </row>
-
-     <row>
-      <entry><structfield>srvid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-foreign-server"><structname>pg_foreign_server</structname></link>.oid</literal></entry>
-      <entry>
-       The OID of the foreign server that contains this mapping
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>srvname</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       Name of the foreign server
-      </entry>
-     </row>
-
-     <row>
-      <entry><structfield>umuser</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>OID of the local role being mapped, 0 if the user mapping is public</entry>
-     </row>
-
-     <row>
-      <entry><structfield>usename</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the local user to be mapped</entry>
-     </row>
-
-     <row>
-      <entry><structfield>umoptions</structfield></entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>
-       User mapping specific options, as <quote>keyword=value</>
-       strings, if the current user is the owner of the foreign
-       server, else null
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="view-pg-views">
-  <title><structname>pg_views</structname></title>
-
-  <indexterm zone="view-pg-views">
-   <primary>pg_views</primary>
-  </indexterm>
-
-&common;
-  <para>
-   The view <structname>pg_views</structname> provides access to
-   useful information about each view in the database.
-  </para>
-
-  <table>
-   <title><structname>pg_views</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>schemaname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-namespace"><structname>pg_namespace</structname></link>.nspname</literal></entry>
-      <entry>Name of schema containing view</entry>
-     </row>
-     <row>
-      <entry><structfield>viewname</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-class"><structname>pg_class</structname></link>.relname</literal></entry>
-      <entry>Name of view</entry>
-     </row>
-     <row>
-      <entry><structfield>viewowner</structfield></entry>
-      <entry><type>name</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.rolname</literal></entry>
-      <entry>Name of view's owner</entry>
-     </row>
-     <row>
-      <entry><structfield>definition</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>View definition (a reconstructed <command>SELECT</command> query)</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/charset.sgmlin b/doc-xc/src/sgml/charset.sgmlin
deleted file mode 100644
index 64ef6e8692..0000000000
--- a/doc-xc/src/sgml/charset.sgmlin
+++ /dev/null
@@ -1,1716 +0,0 @@
-<!-- doc/src/sgml/charset.sgml -->
-
-<chapter id="charset">
- <title>Localization</title>
-
-
-&common;
- <para>
-  This chapter describes the available localization features from the
-  point of view of the administrator.
-<!## PG>
-  <productname>PostgreSQL</productname> supports two localization
-  facilities:
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> inherits supports of two localization
-  facilities from <productname>PostgreSQL</>:
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> inherits supports of two localization
-  facilities from <productname>PostgreSQL</>:
-<!## end>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Using the locale features of the operating system to provide
-      locale-specific collation order, number formatting, translated
-      messages, and other aspects.
-      This is covered in <xref linkend="locale"> and
-      <xref linkend="collation">.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Providing a number of different character sets to support storing text
-      in all kinds of languages, and providing character set translation
-      between client and server.
-      This is covered in <xref linkend="multibyte">.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-
- <sect1 id="locale">
-  <title>Locale Support</title>
-
-  <indexterm zone="locale"><primary>locale</></>
-&common;
-
-  <para>
-   <firstterm>Locale</> support refers to an application respecting
-   cultural preferences regarding alphabets, sorting, number
-<!## PG>
-   formatting, etc.  <productname>PostgreSQL</> uses the standard ISO
-<!## end>
-<!## XC>
-   formatting, etc.  <productname>Postgres-XC</> uses the standard ISO
-<!## end>
-<!## XL>
-   formatting, etc.  <productname>Postgres-XL</> uses the standard ISO
-<!## end>
-   C and <acronym>POSIX</acronym> locale facilities provided by the server operating
-   system.  For additional information refer to the documentation of your
-   system.
-  </para>
-
-  <sect2>
-   <title>Overview</title>
-
-&common;
-   <para>
-    Locale support is automatically initialized when a database
-    cluster is created using <command>initdb</command>.
-    <command>initdb</command> will initialize the database cluster
-    with the locale setting of its execution environment by default,
-    so if your system is already set to use the locale that you want
-    in your database cluster then there is nothing else you need to
-    do.  If you want to use a different locale (or you are not sure
-    which locale your system is set to), you can instruct
-    <command>initdb</command> exactly which locale to use by
-    specifying the <option>--locale</option> option. For example:
-<screen>
-initdb --locale=sv_SE
-</screen>
-   </para>
-
-   <para>
-    This example for Unix systems sets the locale to Swedish
-    (<literal>sv</>) as spoken
-    in Sweden (<literal>SE</>).  Other possibilities might include
-    <literal>en_US</> (U.S. English) and <literal>fr_CA</> (French
-    Canadian).  If more than one character set can be used for a
-    locale then the specifications can take the form
-    <replaceable>language_territory.codeset</>.  For example,
-    <literal>fr_BE.UTF-8</> represents the French language (fr) as
-    spoken in Belgium (BE), with a <acronym>UTF-8</> character set
-    encoding.
-   </para>
-
-   <para>
-    What locales are available on your
-    system under what names depends on what was provided by the operating
-    system vendor and what was installed.  On most Unix systems, the command
-    <literal>locale -a</> will provide a list of available locales.
-    Windows uses more verbose locale names, such as <literal>German_Germany</>
-    or <literal>Swedish_Sweden.1252</>, but the principles are the same.
-   </para>
-
-   <para>
-    Occasionally it is useful to mix rules from several locales, e.g.,
-    use English collation rules but Spanish messages.  To support that, a
-    set of locale subcategories exist that control only certain
-    aspects of the localization rules:
-
-    <informaltable>
-     <tgroup cols="2">
-      <tbody>
-       <row>
-        <entry><envar>LC_COLLATE</></>
-        <entry>String sort order</>
-       </row>
-       <row>
-        <entry><envar>LC_CTYPE</></>
-        <entry>Character classification (What is a letter? Its upper-case equivalent?)</>
-       </row>
-       <row>
-        <entry><envar>LC_MESSAGES</></>
-        <entry>Language of messages</>
-       </row>
-       <row>
-        <entry><envar>LC_MONETARY</></>
-        <entry>Formatting of currency amounts</>
-       </row>
-       <row>
-        <entry><envar>LC_NUMERIC</></>
-        <entry>Formatting of numbers</>
-       </row>
-       <row>
-        <entry><envar>LC_TIME</></>
-        <entry>Formatting of dates and times</>
-       </row>
-      </tbody>
-     </tgroup>
-    </informaltable>
-
-    The category names translate into names of
-    <command>initdb</command> options to override the locale choice
-    for a specific category.  For instance, to set the locale to
-    French Canadian, but use U.S. rules for formatting currency, use
-    <literal>initdb --locale=fr_CA --lc-monetary=en_US</literal>.
-   </para>
-
-   <para>
-    If you want the system to behave as if it had no locale support,
-    use the special locale name <literal>C</>, or equivalently
-    <literal>POSIX</>.
-   </para>
-
-   <para>
-    Some locale categories must have their values
-    fixed when the database is created.  You can use different settings
-    for different databases, but once a database is created, you cannot
-    change them for that database anymore. <literal>LC_COLLATE</literal>
-    and <literal>LC_CTYPE</literal> are these categories.  They affect
-    the sort order of indexes, so they must be kept fixed, or indexes on
-    text columns would become corrupt.
-    (But you can alleviate this restriction using collations, as discussed
-    in <xref linkend="collation">.)
-    The default values for these
-    categories are determined when <command>initdb</command> is run, and
-    those values are used when new databases are created, unless
-    specified otherwise in the <command>CREATE DATABASE</command> command.
-   </para>
-
-   <para>
-    The other locale categories can be changed whenever desired
-    by setting the server configuration parameters
-    that have the same name as the locale categories (see <xref
-    linkend="runtime-config-client-format"> for details).  The values
-    that are chosen by <command>initdb</command> are actually only written
-    into the configuration file <filename>postgresql.conf</filename> to
-    serve as defaults when the server is started.  If you remove these
-    assignments from <filename>postgresql.conf</filename> then the
-    server will inherit the settings from its execution environment.
-   </para>
-
-   <para>
-    Note that the locale behavior of the server is determined by the
-    environment variables seen by the server, not by the environment
-    of any client.  Therefore, be careful to configure the correct locale settings
-    before starting the server.  A consequence of this is that if
-    client and server are set up in different locales, messages might
-    appear in different languages depending on where they originated.
-   </para>
-
-   <note>
-    <para>
-     When we speak of inheriting the locale from the execution
-     environment, this means the following on most operating systems:
-     For a given locale category, say the collation, the following
-     environment variables are consulted in this order until one is
-     found to be set: <envar>LC_ALL</envar>, <envar>LC_COLLATE</envar>
-     (or the variable corresponding to the respective category),
-     <envar>LANG</envar>.  If none of these environment variables are
-     set then the locale defaults to <literal>C</literal>.
-    </para>
-
-    <para>
-     Some message localization libraries also look at the environment
-     variable <envar>LANGUAGE</envar> which overrides all other locale
-     settings for the purpose of setting the language of messages.  If
-     in doubt, please refer to the documentation of your operating
-     system, in particular the documentation about
-     <application>gettext</>.
-    </para>
-   </note>
-
-   <para>
-    To enable messages to be translated to the user's preferred language,
-    <acronym>NLS</acronym> must have been selected at build time
-    (<literal>configure --enable-nls</>).  All other locale support is
-    built in automatically.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Behavior</title>
-
-&common;
-   <para>
-    The locale settings influence the following SQL features:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Sort order in queries using <literal>ORDER BY</> or the standard
-       comparison operators on textual data
-       <indexterm><primary>ORDER BY</><secondary>and locales</></indexterm>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The <function>upper</>, <function>lower</>, and <function>initcap</>
-       functions
-       <indexterm><primary>upper</><secondary>and locales</></indexterm>
-       <indexterm><primary>lower</><secondary>and locales</></indexterm>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Pattern matching operators (<literal>LIKE</>, <literal>SIMILAR TO</>,
-       and POSIX-style regular expressions); locales affect both case
-       insensitive matching and the classification of characters by
-       character-class regular expressions
-       <indexterm><primary>LIKE</><secondary>and locales</></indexterm>
-       <indexterm><primary>regular expressions</><secondary>and locales</></indexterm>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The <function>to_char</> family of functions
-       <indexterm><primary>to_char</><secondary>and locales</></indexterm>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The ability to use indexes with <literal>LIKE</> clauses
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    The drawback of using locales other than <literal>C</> or
-<!## PG>
-    <literal>POSIX</> in <productname>PostgreSQL</> is its performance
-<!## end>
-<!## XC>
-    <literal>POSIX</> in <productname>Postgres-XC</> is its performance
-<!## end>
-<!## XL>
-    <literal>POSIX</> in <productname>Postgres-XL</> is its performance
-<!## end>
-    impact. It slows character handling and prevents ordinary indexes
-    from being used by <literal>LIKE</>. For this reason use locales
-    only if you actually need them.
-   </para>
-
-   <para>
-<!## PG>
-    As a workaround to allow <productname>PostgreSQL</> to use indexes
-<!## end>
-<!## XC>
-    As a workaround to allow <productname>Postgres-XC</> to use indexes
-<!## end>
-<!## XL>
-    As a workaround to allow <productname>Postgres-XL</> to use indexes
-<!## end>
-    with <literal>LIKE</> clauses under a non-C locale, several custom
-    operator classes exist. These allow the creation of an index that
-    performs a strict character-by-character comparison, ignoring
-    locale comparison rules. Refer to <xref linkend="indexes-opclass">
-    for more information.  Another approach is to create indexes using
-    the <literal>C</> collation, as discussed in
-    <xref linkend="collation">.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Problems</title>
-
-&common;
-   <para>
-    If locale support doesn't work according to the explanation above,
-    check that the locale support in your operating system is
-    correctly configured.  To check what locales are installed on your
-    system, you can use the command <literal>locale -a</literal> if
-    your operating system provides it.
-   </para>
-
-   <para>
-<!## PG>
-    Check that <productname>PostgreSQL</> is actually using the locale
-<!## end>
-<!## XC>
-    Check that <productname>Postgres-XC</> is actually using the locale
-<!## end>
-<!## XL>
-    Check that <productname>Postgres-XL</> is actually using the locale
-<!## end>
-    that you think it is.  The <envar>LC_COLLATE</> and <envar>LC_CTYPE</>
-    settings are determined when a database is created, and cannot be
-    changed except by creating a new database.  Other locale
-    settings including <envar>LC_MESSAGES</> and <envar>LC_MONETARY</>
-    are initially determined by the environment the server is started
-    in, but can be changed on-the-fly.  You can check the active locale
-    settings using the <command>SHOW</> command.
-   </para>
-
-   <para>
-    The directory <filename>src/test/locale</> in the source
-    distribution contains a test suite for
-<!## PG>
-    <productname>PostgreSQL</>'s locale support.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</>'s locale support.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</>'s locale support.
-<!## end>
-   </para>
-
-   <para>
-    Client applications that handle server-side errors by parsing the
-    text of the error message will obviously have problems when the
-    server's messages are in a different language.  Authors of such
-    applications are advised to make use of the error code scheme
-    instead.
-   </para>
-
-   <para>
-    Maintaining catalogs of message translations requires the on-going
-    efforts of many volunteers that want to see
-<!## PG>
-    <productname>PostgreSQL</> speak their preferred language well.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> speak their preferred language well.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> speak their preferred language well.
-<!## end>
-    If messages in your language are currently not available or not fully
-    translated, your assistance would be appreciated.  If you want to
-    help, refer to <xref linkend="nls"> or write to the developers'
-    mailing list.
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="collation">
-  <title>Collation Support</title>
-
-  <indexterm zone="collation"><primary>collation</></>
-
-  <para>
-   The collation feature allows specifying the sort order and character
-   classification behavior of data per-column, or even per-operation.
-   This alleviates the restriction that the
-   <symbol>LC_COLLATE</symbol> and <symbol>LC_CTYPE</symbol> settings
-   of a database cannot be changed after its creation.
-  </para>
-
-  <sect2>
-   <title>Concepts</title>
-
-   <para>
-    Conceptually, every expression of a collatable data type has a
-    collation.  (The built-in collatable data types are
-    <type>text</type>, <type>varchar</type>, and <type>char</type>.
-    User-defined base types can also be marked collatable, and of course
-    a domain over a collatable data type is collatable.)  If the
-    expression is a column reference, the collation of the expression is the
-    defined collation of the column.  If the expression is a constant, the
-    collation is the default collation of the data type of the
-    constant.  The collation of a more complex expression is derived
-    from the collations of its inputs, as described below.
-   </para>
-
-   <para>
-    The collation of an expression can be the <quote>default</quote>
-    collation, which means the locale settings defined for the
-    database.  It is also possible for an expression's collation to be
-    indeterminate.  In such cases, ordering operations and other
-    operations that need to know the collation will fail.
-   </para>
-
-   <para>
-    When the database system has to perform an ordering or a character
-    classification, it uses the collation of the input expression.  This
-    happens, for example, with <literal>ORDER BY</literal> clauses
-    and function or operator calls such as <literal>&lt;</literal>.
-    The collation to apply for an <literal>ORDER BY</literal> clause
-    is simply the collation of the sort key.  The collation to apply for a
-    function or operator call is derived from the arguments, as described
-    below.  In addition to comparison operators, collations are taken into
-    account by functions that convert between lower and upper case
-    letters, such as <function>lower</>, <function>upper</>, and
-    <function>initcap</>; by pattern matching operators; and by
-    <function>to_char</> and related functions.
-   </para>
-
-   <para>
-    For a function or operator call, the collation that is derived by
-    examining the argument collations is used at run time for performing
-    the specified operation.  If the result of the function or operator
-    call is of a collatable data type, the collation is also used at parse
-    time as the defined collation of the function or operator expression,
-    in case there is a surrounding expression that requires knowledge of
-    its collation.
-   </para>
-
-   <para>
-    The <firstterm>collation derivation</firstterm> of an expression can be
-    implicit or explicit.  This distinction affects how collations are
-    combined when multiple different collations appear in an
-    expression.  An explicit collation derivation occurs when a
-    <literal>COLLATE</literal> clause is used; all other collation
-    derivations are implicit.  When multiple collations need to be
-    combined, for example in a function call, the following rules are
-    used:
-
-    <orderedlist>
-     <listitem>
-      <para>
-       If any input expression has an explicit collation derivation, then
-       all explicitly derived collations among the input expressions must be
-       the same, otherwise an error is raised.  If any explicitly
-       derived collation is present, that is the result of the
-       collation combination.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Otherwise, all input expressions must have the same implicit
-       collation derivation or the default collation.  If any non-default
-       collation is present, that is the result of the collation combination.
-       Otherwise, the result is the default collation.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If there are conflicting non-default implicit collations among the
-       input expressions, then the combination is deemed to have indeterminate
-       collation.  This is not an error condition unless the particular
-       function being invoked requires knowledge of the collation it should
-       apply.  If it does, an error will be raised at run-time.
-      </para>
-     </listitem>
-    </orderedlist>
-
-    For example, consider this table definition:
-<programlisting>
-CREATE TABLE test1 (
-    a text COLLATE "de_DE",
-    b text COLLATE "es_ES",
-    ...
-);
-</programlisting>
-
-    Then in
-<programlisting>
-SELECT a &lt; 'foo' FROM test1;
-</programlisting>
-    the <literal>&lt;</literal> comparison is performed according to
-    <literal>de_DE</literal> rules, because the expression combines an
-    implicitly derived collation with the default collation.  But in
-<programlisting>
-SELECT a &lt; ('foo' COLLATE "fr_FR") FROM test1;
-</programlisting>
-    the comparison is performed using <literal>fr_FR</literal> rules,
-    because the explicit collation derivation overrides the implicit one.
-    Furthermore, given
-<programlisting>
-SELECT a &lt; b FROM test1;
-</programlisting>
-    the parser cannot determine which collation to apply, since the
-    <structfield>a</> and <structfield>b</> columns have conflicting
-    implicit collations.  Since the <literal>&lt;</literal> operator
-    does need to know which collation to use, this will result in an
-    error.  The error can be resolved by attaching an explicit collation
-    specifier to either input expression, thus:
-<programlisting>
-SELECT a &lt; b COLLATE "de_DE" FROM test1;
-</programlisting>
-    or equivalently
-<programlisting>
-SELECT a COLLATE "de_DE" &lt; b FROM test1;
-</programlisting>
-    On the other hand, the structurally similar case
-<programlisting>
-SELECT a || b FROM test1;
-</programlisting>
-    does not result in an error, because the <literal>||</> operator
-    does not care about collations: its result is the same regardless
-    of the collation.
-   </para>
-
-   <para>
-    The collation assigned to a function or operator's combined input
-    expressions is also considered to apply to the function or operator's
-    result, if the function or operator delivers a result of a collatable
-    data type.  So, in
-<programlisting>
-SELECT * FROM test1 ORDER BY a || 'foo';
-</programlisting>
-    the ordering will be done according to <literal>de_DE</literal> rules.
-    But this query:
-<programlisting>
-SELECT * FROM test1 ORDER BY a || b;
-</programlisting>
-    results in an error, because even though the <literal>||</> operator
-    doesn't need to know a collation, the <literal>ORDER BY</> clause does.
-    As before, the conflict can be resolved with an explicit collation
-    specifier:
-<programlisting>
-SELECT * FROM test1 ORDER BY a || b COLLATE "fr_FR";
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Managing Collations</title>
-
-   <para>
-    A collation is an SQL schema object that maps an SQL name to
-    operating system locales.  In particular, it maps to a combination
-    of <symbol>LC_COLLATE</symbol> and <symbol>LC_CTYPE</symbol>.  (As
-    the name would suggest, the main purpose of a collation is to set
-    <symbol>LC_COLLATE</symbol>, which controls the sort order.  But
-    it is rarely necessary in practice to have an
-    <symbol>LC_CTYPE</symbol> setting that is different from
-    <symbol>LC_COLLATE</symbol>, so it is more convenient to collect
-    these under one concept than to create another infrastructure for
-    setting <symbol>LC_CTYPE</symbol> per expression.)  Also, a collation
-    is tied to a character set encoding (see <xref linkend="multibyte">).
-    The same collation name may exist for different encodings.
-   </para>
-
-   <para>
-    On all platforms, the collations named <literal>default</>,
-    <literal>C</>, and <literal>POSIX</> are available.  Additional
-    collations may be available depending on operating system support.
-    The <literal>default</> collation selects the <symbol>LC_COLLATE</symbol>
-    and <symbol>LC_CTYPE</symbol> values specified at database creation time.
-    The <literal>C</> and <literal>POSIX</> collations both specify
-    <quote>traditional C</> behavior, in which only the ASCII letters
-    <quote><literal>A</></quote> through <quote><literal>Z</></quote>
-    are treated as letters, and sorting is done strictly by character
-    code byte values.
-   </para>
-
-   <para>
-    If the operating system provides support for using multiple locales
-    within a single program (<function>newlocale</> and related functions),
-    then when a database cluster is initialized, <command>initdb</command>
-    populates the system catalog <literal>pg_collation</literal> with
-    collations based on all the locales it finds on the operating
-    system at the time.  For example, the operating system might
-    provide a locale named <literal>de_DE.utf8</literal>.
-    <command>initdb</command> would then create a collation named
-    <literal>de_DE.utf8</literal> for encoding <literal>UTF8</literal>
-    that has both <symbol>LC_COLLATE</symbol> and
-    <symbol>LC_CTYPE</symbol> set to <literal>de_DE.utf8</literal>.
-    It will also create a collation with the <literal>.utf8</literal>
-    tag stripped off the name.  So you could also use the collation
-    under the name <literal>de_DE</literal>, which is less cumbersome
-    to write and makes the name less encoding-dependent.  Note that,
-    nevertheless, the initial set of collation names is
-    platform-dependent.
-   </para>
-
-   <para>
-    In case a collation is needed that has different values for
-    <symbol>LC_COLLATE</symbol> and <symbol>LC_CTYPE</symbol>, a new
-    collation may be created using
-    the <xref linkend="sql-createcollation"> command.  That command
-    can also be used to create a new collation from an existing
-    collation, which can be useful to be able to use
-    operating-system-independent collation names in applications.
-   </para>
-
-   <para>
-    Within any particular database, only collations that use that
-    database's encoding are of interest.  Other entries in
-    <literal>pg_collation</literal> are ignored.  Thus, a stripped collation
-    name such as <literal>de_DE</literal> can be considered unique
-    within a given database even though it would not be unique globally.
-    Use of the stripped collation names is recommendable, since it will
-    make one less thing you need to change if you decide to change to
-    another database encoding.  Note however that the <literal>default</>,
-    <literal>C</>, and <literal>POSIX</> collations can be used
-    regardless of the database encoding.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</productname> considers distinct collation
-    objects to be incompatible even when they have identical properties.
-    Thus for example,
-<programlisting>
-SELECT a COLLATE "C" &lt; b COLLATE "POSIX" FROM test1;
-</programlisting>
-    will draw an error even though the <literal>C</> and <literal>POSIX</>
-    collations have identical behaviors.  Mixing stripped and non-stripped
-    collation names is therefore not recommended.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="multibyte">
-  <title>Character Set Support</title>
-
-  <indexterm zone="multibyte"><primary>character set</></>
-&common;
-
-  <para>
-<!## PG>
-   The character set support in <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   The character set support in <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   The character set support in <productname>Postgres-XL</productname>
-<!## end>
-   allows you to store text in a variety of character sets (also called
-   encodings), including
-   single-byte character sets such as the ISO 8859 series and
-   multiple-byte character sets such as <acronym>EUC</> (Extended Unix
-   Code), UTF-8, and Mule internal code.  All supported character sets
-   can be used transparently by clients, but a few are not supported
-   for use within the server (that is, as a server-side encoding).
-   The default character set is selected while
-<!## PG>
-   initializing your <productname>PostgreSQL</productname> database
-<!## end>
-<!## XC>
-   initializing your <productname>Postgres-XC</productname> database
-<!## end>
-<!## XL>
-   initializing your <productname>Postgres-XL</productname> database
-<!## end>
-   cluster using <command>initdb</>.  It can be overridden when you
-   create a database, so you can have multiple
-   databases each with a different character set.
-  </para>
-
-  <para>
-   An important restriction, however, is that each database's character set
-   must be compatible with the database's <envar>LC_CTYPE</> (character
-   classification) and <envar>LC_COLLATE</> (string sort order) locale
-   settings. For <literal>C</> or
-   <literal>POSIX</> locale, any character set is allowed, but for other
-   locales there is only one character set that will work correctly.
-   (On Windows, however, UTF-8 encoding can be used with any locale.)
-  </para>
-
-   <sect2 id="multibyte-charset-supported">
-    <title>Supported Character Sets</title>
-&common;
-
-    <para>
-     <xref linkend="charset-table"> shows the character sets available
-<!## PG>
-     for use in <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-     for use in <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-     for use in <productname>Postgres-XL</productname>.
-<!## end>
-    </para>
-
-     <table id="charset-table">
-<!## PG>
-      <title><productname>PostgreSQL</productname> Character Sets</title>
-<!## end>
-<!## XC>
-      <title><productname>Postgres-XC</productname> Character Sets</title>
-<!## end>
-<!## XL>
-      <title><productname>Postgres-XL</productname> Character Sets</title>
-<!## end>
-      <tgroup cols="6">
-       <thead>
-        <row>
-         <entry>Name</entry>
-         <entry>Description</entry>
-         <entry>Language</entry>
-         <entry>Server?</entry>
-         <!--
-          The Bytes/Char field is populated by looking at the values returned
-          by pg_wchar_table.mblen function for each encoding.
-         -->
-         <entry>Bytes/Char</entry>
-         <entry>Aliases</entry>
-        </row>
-       </thead>
-       <tbody>
-        <row>
-         <entry><literal>BIG5</literal></entry>
-         <entry>Big Five</entry>
-         <entry>Traditional Chinese</entry>
-         <entry>No</entry>
-         <entry>1-2</entry>
-         <entry><literal>WIN950</>, <literal>Windows950</></entry>
-        </row>
-        <row>
-         <entry><literal>EUC_CN</literal></entry>
-         <entry>Extended UNIX Code-CN</entry>
-         <entry>Simplified Chinese</entry>
-         <entry>Yes</entry>
-         <entry>1-3</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>EUC_JP</literal></entry>
-         <entry>Extended UNIX Code-JP</entry>
-         <entry>Japanese</entry>
-         <entry>Yes</entry>
-         <entry>1-3</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>EUC_JIS_2004</literal></entry>
-         <entry>Extended UNIX Code-JP, JIS X 0213</entry>
-         <entry>Japanese</entry>
-         <entry>Yes</entry>
-         <entry>1-3</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>EUC_KR</literal></entry>
-         <entry>Extended UNIX Code-KR</entry>
-         <entry>Korean</entry>
-         <entry>Yes</entry>
-         <entry>1-3</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>EUC_TW</literal></entry>
-         <entry>Extended UNIX Code-TW</entry>
-         <entry>Traditional Chinese, Taiwanese</entry>
-         <entry>Yes</entry>
-         <entry>1-3</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>GB18030</literal></entry>
-         <entry>National Standard</entry>
-         <entry>Chinese</entry>
-         <entry>No</entry>
-         <entry>1-2</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>GBK</literal></entry>
-         <entry>Extended National Standard</entry>
-         <entry>Simplified Chinese</entry>
-         <entry>No</entry>
-         <entry>1-2</entry>
-         <entry><literal>WIN936</>, <literal>Windows936</></entry>
-        </row>
-        <row>
-         <entry><literal>ISO_8859_5</literal></entry>
-         <entry>ISO 8859-5, <acronym>ECMA</> 113</entry>
-         <entry>Latin/Cyrillic</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>ISO_8859_6</literal></entry>
-         <entry>ISO 8859-6, <acronym>ECMA</> 114</entry>
-         <entry>Latin/Arabic</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>ISO_8859_7</literal></entry>
-         <entry>ISO 8859-7, <acronym>ECMA</> 118</entry>
-         <entry>Latin/Greek</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>ISO_8859_8</literal></entry>
-         <entry>ISO 8859-8, <acronym>ECMA</> 121</entry>
-         <entry>Latin/Hebrew</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>JOHAB</literal></entry>
-         <entry><acronym>JOHAB</></entry>
-         <entry>Korean (Hangul)</entry>
-         <entry>No</entry>
-         <entry>1-3</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>KOI8R</literal></entry>
-         <entry><acronym>KOI</acronym>8-R</entry>
-         <entry>Cyrillic (Russian)</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>KOI8</></entry>
-        </row>
-        <row>
-         <entry><literal>KOI8U</literal></entry>
-         <entry><acronym>KOI</acronym>8-U</entry>
-         <entry>Cyrillic (Ukrainian)</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>LATIN1</literal></entry>
-         <entry>ISO 8859-1, <acronym>ECMA</> 94</entry>
-         <entry>Western European</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ISO88591</></entry>
-        </row>
-        <row>
-         <entry><literal>LATIN2</literal></entry>
-         <entry>ISO 8859-2, <acronym>ECMA</> 94</entry>
-         <entry>Central European</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ISO88592</></entry>
-        </row>
-        <row>
-         <entry><literal>LATIN3</literal></entry>
-         <entry>ISO 8859-3, <acronym>ECMA</> 94</entry>
-         <entry>South European</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ISO88593</></entry>
-        </row>
-        <row>
-         <entry><literal>LATIN4</literal></entry>
-         <entry>ISO 8859-4, <acronym>ECMA</> 94</entry>
-         <entry>North European</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ISO88594</></entry>
-        </row>
-        <row>
-         <entry><literal>LATIN5</literal></entry>
-         <entry>ISO 8859-9, <acronym>ECMA</> 128</entry>
-         <entry>Turkish</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ISO88599</></entry>
-        </row>
-        <row>
-         <entry><literal>LATIN6</literal></entry>
-         <entry>ISO 8859-10, <acronym>ECMA</> 144</entry>
-         <entry>Nordic</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ISO885910</></entry>
-        </row>
-        <row>
-         <entry><literal>LATIN7</literal></entry>
-         <entry>ISO 8859-13</entry>
-         <entry>Baltic</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ISO885913</></entry>
-        </row>
-        <row>
-         <entry><literal>LATIN8</literal></entry>
-         <entry>ISO 8859-14</entry>
-         <entry>Celtic</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ISO885914</></entry>
-        </row>
-        <row>
-         <entry><literal>LATIN9</literal></entry>
-         <entry>ISO 8859-15</entry>
-         <entry>LATIN1 with Euro and accents</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ISO885915</></entry>
-        </row>
-        <row>
-         <entry><literal>LATIN10</literal></entry>
-         <entry>ISO 8859-16, <acronym>ASRO</> SR 14111</entry>
-         <entry>Romanian</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ISO885916</></entry>
-        </row>
-        <row>
-         <entry><literal>MULE_INTERNAL</literal></entry>
-         <entry>Mule internal code</entry>
-         <entry>Multilingual Emacs</entry>
-         <entry>Yes</entry>
-         <entry>1-4</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>SJIS</literal></entry>
-         <entry>Shift JIS</entry>
-         <entry>Japanese</entry>
-         <entry>No</entry>
-         <entry>1-2</entry>
-         <entry><literal>Mskanji</>, <literal>ShiftJIS</>, <literal>WIN932</>, <literal>Windows932</></entry>
-        </row>
-        <row>
-         <entry><literal>SHIFT_JIS_2004</literal></entry>
-         <entry>Shift JIS, JIS X 0213</entry>
-         <entry>Japanese</entry>
-         <entry>No</entry>
-         <entry>1-2</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>SQL_ASCII</literal></entry>
-         <entry>unspecified (see text)</entry>
-         <entry><emphasis>any</></entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>UHC</literal></entry>
-         <entry>Unified Hangul Code</entry>
-         <entry>Korean</entry>
-         <entry>No</entry>
-         <entry>1-2</entry>
-         <entry><literal>WIN949</>, <literal>Windows949</></entry>
-        </row>
-        <row>
-         <entry><literal>UTF8</literal></entry>
-         <entry>Unicode, 8-bit</entry>
-         <entry><emphasis>all</></entry>
-         <entry>Yes</entry>
-         <entry>1-4</entry>
-         <entry><literal>Unicode</></entry>
-        </row>
-        <row>
-         <entry><literal>WIN866</literal></entry>
-         <entry>Windows CP866</entry>
-         <entry>Cyrillic</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ALT</></entry>
-        </row>
-        <row>
-         <entry><literal>WIN874</literal></entry>
-         <entry>Windows CP874</entry>
-         <entry>Thai</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>WIN1250</literal></entry>
-         <entry>Windows CP1250</entry>
-         <entry>Central European</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>WIN1251</literal></entry>
-         <entry>Windows CP1251</entry>
-         <entry>Cyrillic</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>WIN</></entry>
-        </row>
-        <row>
-         <entry><literal>WIN1252</literal></entry>
-         <entry>Windows CP1252</entry>
-         <entry>Western European</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>WIN1253</literal></entry>
-         <entry>Windows CP1253</entry>
-         <entry>Greek</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>WIN1254</literal></entry>
-         <entry>Windows CP1254</entry>
-         <entry>Turkish</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>WIN1255</literal></entry>
-         <entry>Windows CP1255</entry>
-         <entry>Hebrew</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>WIN1256</literal></entry>
-         <entry>Windows CP1256</entry>
-         <entry>Arabic</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>WIN1257</literal></entry>
-         <entry>Windows CP1257</entry>
-         <entry>Baltic</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry></entry>
-        </row>
-        <row>
-         <entry><literal>WIN1258</literal></entry>
-         <entry>Windows CP1258</entry>
-         <entry>Vietnamese</entry>
-         <entry>Yes</entry>
-         <entry>1</entry>
-         <entry><literal>ABC</>, <literal>TCVN</>, <literal>TCVN5712</>, <literal>VSCII</></entry>
-        </row>
-       </tbody>
-      </tgroup>
-     </table>
-
-     <para>
-      Not all client <acronym>API</>s support all the listed character sets. For example, the
-<!## PG>
-      <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</>
-<!## end>
-      JDBC driver does not support <literal>MULE_INTERNAL</>, <literal>LATIN6</>,
-      <literal>LATIN8</>, and <literal>LATIN10</>.
-     </para>
-
-     <para>
-      The <literal>SQL_ASCII</> setting behaves considerably differently
-      from the other settings.  When the server character set is
-      <literal>SQL_ASCII</>, the server interprets byte values 0-127
-      according to the ASCII standard, while byte values 128-255 are taken
-      as uninterpreted characters.  No encoding conversion will be done when
-      the setting is <literal>SQL_ASCII</>.  Thus, this setting is not so
-      much a declaration that a specific encoding is in use, as a declaration
-      of ignorance about the encoding.  In most cases, if you are
-      working with any non-ASCII data, it is unwise to use the
-      <literal>SQL_ASCII</> setting because
-<!## PG>
-      <productname>PostgreSQL</productname> will be unable to help you by
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname> will be unable to help you by
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname> will be unable to help you by
-<!## end>
-      converting or validating non-ASCII characters.
-     </para>
-    </sect2>
-
-   <sect2>
-    <title>Setting the Character Set</title>
-&common;
-
-    <para>
-     <command>initdb</> defines the default character set (encoding)
-<!## PG>
-     for a <productname>PostgreSQL</productname> cluster. For example,
-<!## end>
-<!## XC>
-     for a <productname>Postgres-XC</productname> cluster. For example,
-<!## end>
-<!## XL>
-     for a <productname>Postgres-XL</productname> cluster. For example,
-<!## end>
-
-<screen>
-initdb -E EUC_JP
-</screen>
-
-     sets the default character set to
-     <literal>EUC_JP</literal> (Extended Unix Code for Japanese).  You
-     can use <option>--encoding</option> instead of
-     <option>-E</option> if you prefer longer option strings.
-     If no <option>-E</> or <option>--encoding</option> option is
-     given, <command>initdb</> attempts to determine the appropriate
-     encoding to use based on the specified or default locale.
-    </para>
-
-    <para>
-     You can specify a non-default encoding at database creation time,
-     provided that the encoding is compatible with the selected locale:
-
-<screen>
-createdb -E EUC_KR -T template0 --lc-collate=ko_KR.euckr --lc-ctype=ko_KR.euckr korean
-</screen>
-
-     This will create a database named <literal>korean</literal> that
-     uses the character set <literal>EUC_KR</literal>, and locale <literal>ko_KR</literal>.
-     Another way to accomplish this is to use this SQL command:
-
-<programlisting>
-CREATE DATABASE korean WITH ENCODING 'EUC_KR' LC_COLLATE='ko_KR.euckr' LC_CTYPE='ko_KR.euckr' TEMPLATE=template0;
-</programlisting>
-
-     Notice that the above commands specify copying the <literal>template0</>
-     database.  When copying any other database, the encoding and locale
-     settings cannot be changed from those of the source database, because
-     that might result in corrupt data.  For more information see
-     <xref linkend="manage-ag-templatedbs">.
-    </para>
-
-    <para>
-     The encoding for a database is stored in the system catalog
-     <literal>pg_database</literal>.  You can see it by using the
-     <command>psql</command> <option>-l</option> option or the
-     <command>\l</command> command.
-
-<screen>
-$ <userinput>psql -l</userinput>
-                                         List of databases
-   Name    |  Owner   | Encoding  |  Collation  |    Ctype    |          Access Privileges          
------------+----------+-----------+-------------+-------------+-------------------------------------
- clocaledb | hlinnaka | SQL_ASCII | C           | C           | 
- englishdb | hlinnaka | UTF8      | en_GB.UTF8  | en_GB.UTF8  | 
- japanese  | hlinnaka | UTF8      | ja_JP.UTF8  | ja_JP.UTF8  | 
- korean    | hlinnaka | EUC_KR    | ko_KR.euckr | ko_KR.euckr | 
- postgres  | hlinnaka | UTF8      | fi_FI.UTF8  | fi_FI.UTF8  | 
- template0 | hlinnaka | UTF8      | fi_FI.UTF8  | fi_FI.UTF8  | {=c/hlinnaka,hlinnaka=CTc/hlinnaka}
- template1 | hlinnaka | UTF8      | fi_FI.UTF8  | fi_FI.UTF8  | {=c/hlinnaka,hlinnaka=CTc/hlinnaka}
-(7 rows)
-</screen>
-    </para>
-
-    <important>
-     <para>
-<!## PG>
-      On most modern operating systems, <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-      On most modern operating systems, <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-      On most modern operating systems, <productname>Postgres-XL</productname>
-<!## end>
-      can determine which character set is implied by the <envar>LC_CTYPE</>
-      setting, and it will enforce that only the matching database encoding is
-      used.  On older systems it is your responsibility to ensure that you use
-      the encoding expected by the locale you have selected.  A mistake in
-      this area is likely to lead to strange behavior of locale-dependent
-      operations such as sorting.
-     </para>
-
-     <para>
-<!## PG>
-      <productname>PostgreSQL</productname> will allow superusers to create
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname> will allow superusers to create
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname> will allow superusers to create
-<!## end>
-      databases with <literal>SQL_ASCII</> encoding even when
-      <envar>LC_CTYPE</> is not <literal>C</> or <literal>POSIX</>.  As noted
-      above, <literal>SQL_ASCII</> does not enforce that the data stored in
-      the database has any particular encoding, and so this choice poses risks
-      of locale-dependent misbehavior.  Using this combination of settings is
-      deprecated and may someday be forbidden altogether.
-     </para>
-    </important>
-   </sect2>
-
-   <sect2>
-    <title>Automatic Character Set Conversion Between Server and Client</title>
-&common;
-
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> supports automatic
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> supports automatic
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> supports automatic
-<!## end>
-     character set conversion between server and client for certain
-     character set combinations. The conversion information is stored in the
-<!## PG>
-     <literal>pg_conversion</> system catalog.  <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-     <literal>pg_conversion</> system catalog.  <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-     <literal>pg_conversion</> system catalog.  <productname>Postgres-XL</>
-<!## end>
-     comes with some predefined conversions, as shown in <xref
-     linkend="multibyte-translation-table">. You can create a new
-     conversion using the SQL command <command>CREATE CONVERSION</command>.
-    </para>
-
-     <table id="multibyte-translation-table">
-      <title>Client/Server Character Set Conversions</title>
-      <tgroup cols="2">
-       <thead>
-        <row>
-         <entry>Server Character Set</entry>
-         <entry>Available Client Character Sets</entry>
-        </row>
-       </thead>
-       <tbody>
-        <row>
-         <entry><literal>BIG5</literal></entry>
-         <entry><emphasis>not supported as a server encoding</emphasis>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>EUC_CN</literal></entry>
-         <entry><emphasis>EUC_CN</emphasis>,
-         <literal>MULE_INTERNAL</literal>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>EUC_JP</literal></entry>
-         <entry><emphasis>EUC_JP</emphasis>,
-         <literal>MULE_INTERNAL</literal>,
-         <literal>SJIS</literal>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>EUC_KR</literal></entry>
-         <entry><emphasis>EUC_KR</emphasis>,
-         <literal>MULE_INTERNAL</literal>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>EUC_TW</literal></entry>
-         <entry><emphasis>EUC_TW</emphasis>,
-         <literal>BIG5</literal>,
-         <literal>MULE_INTERNAL</literal>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>GB18030</literal></entry>
-         <entry><emphasis>not supported as a server encoding</emphasis>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>GBK</literal></entry>
-         <entry><emphasis>not supported as a server encoding</emphasis>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>ISO_8859_5</literal></entry>
-         <entry><emphasis>ISO_8859_5</emphasis>,
-         <literal>KOI8R</literal>,
-         <literal>MULE_INTERNAL</literal>,
-         <literal>UTF8</literal>,
-         <literal>WIN866</literal>,
-         <literal>WIN1251</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>ISO_8859_6</literal></entry>
-         <entry><emphasis>ISO_8859_6</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>ISO_8859_7</literal></entry>
-         <entry><emphasis>ISO_8859_7</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>ISO_8859_8</literal></entry>
-         <entry><emphasis>ISO_8859_8</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>JOHAB</literal></entry>
-         <entry><emphasis>JOHAB</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>KOI8R</literal></entry>
-         <entry><emphasis>KOI8R</emphasis>,
-         <literal>ISO_8859_5</literal>,
-         <literal>MULE_INTERNAL</literal>,
-         <literal>UTF8</literal>,
-         <literal>WIN866</literal>,
-         <literal>WIN1251</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>KOI8U</literal></entry>
-         <entry><emphasis>KOI8U</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>LATIN1</literal></entry>
-         <entry><emphasis>LATIN1</emphasis>,
-         <literal>MULE_INTERNAL</literal>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>LATIN2</literal></entry>
-         <entry><emphasis>LATIN2</emphasis>,
-         <literal>MULE_INTERNAL</literal>,
-         <literal>UTF8</literal>,
-         <literal>WIN1250</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>LATIN3</literal></entry>
-         <entry><emphasis>LATIN3</emphasis>,
-         <literal>MULE_INTERNAL</literal>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>LATIN4</literal></entry>
-         <entry><emphasis>LATIN4</emphasis>,
-         <literal>MULE_INTERNAL</literal>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>LATIN5</literal></entry>
-         <entry><emphasis>LATIN5</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>LATIN6</literal></entry>
-         <entry><emphasis>LATIN6</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>LATIN7</literal></entry>
-         <entry><emphasis>LATIN7</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>LATIN8</literal></entry>
-         <entry><emphasis>LATIN8</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>LATIN9</literal></entry>
-         <entry><emphasis>LATIN9</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>LATIN10</literal></entry>
-         <entry><emphasis>LATIN10</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>MULE_INTERNAL</literal></entry>
-         <entry><emphasis>MULE_INTERNAL</emphasis>,
-          <literal>BIG5</literal>,
-          <literal>EUC_CN</literal>,
-          <literal>EUC_JP</literal>,
-          <literal>EUC_KR</literal>,
-          <literal>EUC_TW</literal>,
-          <literal>ISO_8859_5</literal>,
-          <literal>KOI8R</literal>,
-          <literal>LATIN1</literal> to <literal>LATIN4</literal>,
-          <literal>SJIS</literal>,
-          <literal>WIN866</literal>,
-          <literal>WIN1250</literal>,
-          <literal>WIN1251</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>SJIS</literal></entry>
-         <entry><emphasis>not supported as a server encoding</emphasis>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>SQL_ASCII</literal></entry>
-         <entry><emphasis>any (no conversion will be performed)</emphasis>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>UHC</literal></entry>
-         <entry><emphasis>not supported as a server encoding</emphasis>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>UTF8</literal></entry>
-         <entry><emphasis>all supported encodings</emphasis>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN866</literal></entry>
-         <entry><emphasis>WIN866</emphasis>,
-          <literal>ISO_8859_5</literal>,
-          <literal>KOI8R</literal>,
-          <literal>MULE_INTERNAL</literal>,
-          <literal>UTF8</literal>,
-          <literal>WIN1251</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN874</literal></entry>
-         <entry><emphasis>WIN874</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN1250</literal></entry>
-         <entry><emphasis>WIN1250</emphasis>,
-          <literal>LATIN2</literal>,
-          <literal>MULE_INTERNAL</literal>,
-          <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN1251</literal></entry>
-         <entry><emphasis>WIN1251</emphasis>,
-          <literal>ISO_8859_5</literal>,
-          <literal>KOI8R</literal>,
-          <literal>MULE_INTERNAL</literal>,
-          <literal>UTF8</literal>,
-          <literal>WIN866</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN1252</literal></entry>
-         <entry><emphasis>WIN1252</emphasis>,
-          <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN1253</literal></entry>
-         <entry><emphasis>WIN1253</emphasis>,
-          <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN1254</literal></entry>
-         <entry><emphasis>WIN1254</emphasis>,
-          <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN1255</literal></entry>
-         <entry><emphasis>WIN1255</emphasis>,
-          <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN1256</literal></entry>
-         <entry><emphasis>WIN1256</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN1257</literal></entry>
-         <entry><emphasis>WIN1257</emphasis>,
-          <literal>UTF8</literal>
-         </entry>
-        </row>
-        <row>
-         <entry><literal>WIN1258</literal></entry>
-         <entry><emphasis>WIN1258</emphasis>,
-         <literal>UTF8</literal>
-         </entry>
-        </row>
-       </tbody>
-      </tgroup>
-     </table>
-
-    <para>
-     To enable automatic character set conversion, you have to
-<!## PG>
-     tell <productname>PostgreSQL</productname> the character set
-<!## end>
-<!## XC>
-     tell <productname>Postgres-XC</productname> the character set
-<!## end>
-<!## XL>
-     tell <productname>Postgres-XL</productname> the character set
-<!## end>
-     (encoding) you would like to use in the client. There are several
-     ways to accomplish this:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        Using the <command>\encoding</command> command in
-        <application>psql</application>.
-        <command>\encoding</command> allows you to change client
-        encoding on the fly. For
-        example, to change the encoding to <literal>SJIS</literal>, type:
-
-<programlisting>
-\encoding SJIS
-</programlisting>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <application>libpq</> (<xref linkend="libpq-control">) has functions to control the client encoding.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Using <command>SET client_encoding TO</command>.
-
-        Setting the client encoding can be done with this SQL command:
-
-<programlisting>
-SET CLIENT_ENCODING TO '<replaceable>value</>';
-</programlisting>
-
-        Also you can use the standard SQL syntax <literal>SET NAMES</literal>
-        for this purpose:
-
-<programlisting>
-SET NAMES '<replaceable>value</>';
-</programlisting>
-
-        To query the current client encoding:
-
-<programlisting>
-SHOW client_encoding;
-</programlisting>
-
-        To return to the default encoding:
-
-<programlisting>
-RESET client_encoding;
-</programlisting>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Using <envar>PGCLIENTENCODING</envar>. If the environment variable
-        <envar>PGCLIENTENCODING</envar> is defined in the client's
-        environment, that client encoding is automatically selected
-        when a connection to the server is made.  (This can
-        subsequently be overridden using any of the other methods
-        mentioned above.)
-       </para>
-      </listitem>
-
-      <listitem>
-      <para>
-       Using the configuration variable <xref
-       linkend="guc-client-encoding">. If the
-       <varname>client_encoding</> variable is set, that client
-       encoding is automatically selected when a connection to the
-       server is made.  (This can subsequently be overridden using any
-       of the other methods mentioned above.)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-    </para>
-
-    <para>
-     If the conversion of a particular character is not possible
-     &mdash; suppose you chose <literal>EUC_JP</literal> for the
-     server and <literal>LATIN1</literal> for the client, and some
-     Japanese characters are returned that do not have a representation in
-     <literal>LATIN1</literal> &mdash; an error is reported.
-    </para>
-
-    <para>
-     If the client character set is defined as <literal>SQL_ASCII</>,
-     encoding conversion is disabled, regardless of the server's character
-     set.  Just as for the server, use of <literal>SQL_ASCII</> is unwise
-     unless you are working with all-ASCII data.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Further Reading</title>
-&common;
-
-    <para>
-     These are good sources to start learning about various kinds of encoding
-     systems.
-
-     <variablelist>
-      <varlistentry>
-       <term><ulink url="http://www.i18ngurus.com/docs/984813247.html"></ulink></term>
-
-       <listitem>
-        <para>
-         An extensive collection of documents about character sets, encodings,
-         and code pages.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><citetitle>CJKV Information Processing: Chinese, Japanese, Korean &amp; Vietnamese Computing</citetitle></term>
-
-       <listitem>
-        <para>
-         Contains detailed explanations of <literal>EUC_JP</literal>,
-         <literal>EUC_CN</literal>, <literal>EUC_KR</literal>,
-         <literal>EUC_TW</literal>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><ulink url="http://www.unicode.org/"></ulink></term>
-
-       <listitem>
-        <para>
-         The web site of the Unicode Consortium.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>RFC 3629</term>
-
-       <listitem>
-        <para>
-         <acronym>UTF</acronym>-8 (8-bit UCS/Unicode Transformation
-         Format) is defined here.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-   </sect2>
-
-  </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/chkpass.sgmlin b/doc-xc/src/sgml/chkpass.sgmlin
deleted file mode 100644
index fdbe0feacc..0000000000
--- a/doc-xc/src/sgml/chkpass.sgmlin
+++ /dev/null
@@ -1,97 +0,0 @@
-<!-- doc/src/sgml/chkpass.sgml -->
-
-<sect1 id="chkpass" xreflabel="chkpass">
- <title>chkpass</title>
-
- <indexterm zone="chkpass">
-  <primary>chkpass</primary>
- </indexterm>
-
-&common;
-
- <para>
-  This module implements a data type <type>chkpass</> that is
-  designed for storing encrypted passwords.
-  Each password is automatically converted to encrypted form upon entry,
-  and is always stored encrypted.  To compare, simply compare against a clear
-  text password and the comparison function will encrypt it before comparing.
- </para>
-
- <para>
-  There are provisions in the code to report an error if the password is
-  determined to be easily crackable.  However, this is currently just
-  a stub that does nothing.
- </para>
-
- <para>
-  If you precede an input string with a colon, it is assumed to be an
-  already-encrypted password, and is stored without further encryption.
-  This allows entry of previously-encrypted passwords.
- </para>
-
- <para>
-  On output, a colon is prepended.  This makes it possible to dump and reload
-  passwords without re-encrypting them.  If you want the encrypted password
-  without the colon then use the <function>raw()</> function.
-  This allows you to use the
-  type with things like Apache's <literal>Auth_PostgreSQL</> module.
- </para>
-
- <para>
-  The encryption uses the standard Unix function <function>crypt()</>,
-  and so it suffers
-  from all the usual limitations of that function; notably that only the
-  first eight characters of a password are considered.
- </para>
-
- <para>
-  Note that the <type>chkpass</type> data type is not indexable.
-  <!--
-  I haven't worried about making this type indexable.  I doubt that anyone
-  would ever need to sort a file in order of encrypted password.
-  -->
- </para>
-
- <para>
-  Sample usage:
- </para>
-
-<programlisting>
-test=# create table test (p chkpass);
-CREATE TABLE
-test=# insert into test values ('hello');
-INSERT 0 1
-test=# select * from test;
-       p
-----------------
- :dVGkpXdOrE3ko
-(1 row)
-
-test=# select raw(p) from test;
-      raw
----------------
- dVGkpXdOrE3ko
-(1 row)
-
-test=# select p = 'hello' from test;
- ?column?
-----------
- t
-(1 row)
-
-test=# select p = 'goodbye' from test;
- ?column?
-----------
- f
-(1 row)
-</programlisting>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   D'Arcy J.M. Cain (<email>[email protected]</email>)
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/citext.sgmlin b/doc-xc/src/sgml/citext.sgmlin
deleted file mode 100644
index 26e2fab679..0000000000
--- a/doc-xc/src/sgml/citext.sgmlin
+++ /dev/null
@@ -1,313 +0,0 @@
-<!-- doc/src/sgml/citext.sgml -->
-
-<sect1 id="citext" xreflabel="citext">
- <title>citext</title>
-
- <indexterm zone="citext">
-  <primary>citext</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>citext</> module provides a case-insensitive
-  character string type, <type>citext</>. Essentially, it internally calls
-  <function>lower</> when comparing values. Otherwise, it behaves almost
-  exactly like <type>text</>.
- </para>
-
- <sect2>
-  <title>Rationale</title>
-
-&common;
-
-  <para>
-   The standard approach to doing case-insensitive matches
-   in <productname>PostgreSQL</> has been to use the <function>lower</>
-   function when comparing values, for example
-
-<programlisting>
-SELECT * FROM tab WHERE lower(col) = LOWER(?);
-</programlisting>
-  </para>
-
-  <para>
-   This works reasonably well, but has a number of drawbacks:
-  </para>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      It makes your SQL statements verbose, and you always have to remember to
-      use <function>lower</> on both the column and the query value.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      It won't use an index, unless you create a functional index using
-      <function>lower</>.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      If you declare a column as <literal>UNIQUE</> or <literal>PRIMARY
-      KEY</>, the implicitly generated index is case-sensitive.  So it's
-      useless for case-insensitive searches, and it won't enforce
-      uniqueness case-insensitively.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   <para>
-    The <type>citext</> data type allows you to eliminate calls
-    to <function>lower</> in SQL queries, and allows a primary key to
-    be case-insensitive. <type>citext</> is locale-aware, just
-    like <type>text</>, which means that the matching of upper case and
-    lower case characters is dependent on the rules of
-    the database's <literal>LC_CTYPE</> setting. Again, this behavior is
-    identical to the use of <function>lower</> in queries. But because it's
-    done transparently by the data type, you don't have to remember to do
-    anything special in your queries.
-   </para>
-
- </sect2>
-
- <sect2>
-  <title>How to Use It</title>
-
-  <para>
-   Here's a simple example of usage:
-
-<!## PG>
-<programlisting>
-CREATE TABLE users (
-    nick CITEXT PRIMARY KEY,
-    pass TEXT   NOT NULL
-);
-
-INSERT INTO users VALUES ( 'larry',  md5(random()::text) );
-INSERT INTO users VALUES ( 'Tom',    md5(random()::text) );
-INSERT INTO users VALUES ( 'Damian', md5(random()::text) );
-INSERT INTO users VALUES ( 'NEAL',   md5(random()::text) );
-INSERT INTO users VALUES ( 'Bj&oslash;rn',  md5(random()::text) );
-
-SELECT * FROM users WHERE nick = 'Larry';
-</programlisting>
-<!## end>
-<!## XC>
-<programlisting>
-CREATE TABLE users (
-    id   int    PRIMARY KEY,
-    nick CITEXT,
-    pass TEXT   NOT NULL
-);
-
-INSERT INTO users VALUES (1,  'larry',  md5(random()::text) );
-INSERT INTO users VALUES (2,  'Tom',    md5(random()::text) );
-INSERT INTO users VALUES (3,  'Damian', md5(random()::text) );
-INSERT INTO users VALUES (4,  'NEAL',   md5(random()::text) );
-INSERT INTO users VALUES (5,  'Bj&oslash;rn',  md5(random()::text) );
-
-SELECT * FROM users WHERE nick = 'Larry';
-</programlisting>
-<!## end>
-<!## XL>
-<programlisting>
-CREATE TABLE users (
-    id   int    PRIMARY KEY,
-    nick CITEXT,
-    pass TEXT   NOT NULL
-);
-
-INSERT INTO users VALUES (1,  'larry',  md5(random()::text) );
-INSERT INTO users VALUES (2,  'Tom',    md5(random()::text) );
-INSERT INTO users VALUES (3,  'Damian', md5(random()::text) );
-INSERT INTO users VALUES (4,  'NEAL',   md5(random()::text) );
-INSERT INTO users VALUES (5,  'Bj&oslash;rn',  md5(random()::text) );
-
-SELECT * FROM users WHERE nick = 'Larry';
-</programlisting>
-<!## end>
-
-   The <command>SELECT</> statement will return one tuple, even though
-   the <structfield>nick</> column was set to <literal>larry</> and the query
-   was for <literal>Larry</>.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   Please note that the column of the type <literal>CITEXT</literal>
-   cannot be the distribution column;
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   Please note that the column of the type <literal>CITEXT</literal>
-   cannot be the distribution column;
-  </para>
-<!## end>
-
- </sect2>
-
- <sect2>
-  <title>String Comparison Behavior</title>
-
-&common;
-  <para>
-   <type>citext</> performs comparisons by converting each string to lower
-   case (as though <function>lower</> were called) and then comparing the
-   results normally.  Thus, for example, two strings are considered equal
-   if <function>lower</> would produce identical results for them.
-  </para>
-
-  <para>
-   In order to emulate a case-insensitive collation as closely as possible,
-   there are <type>citext</>-specific versions of a number of string-processing
-   operators and functions.  So, for example, the regular expression
-   operators <literal>~</> and <literal>~*</> exhibit the same behavior when
-   applied to <type>citext</>: they both match case-insensitively.
-   The same is true
-   for <literal>!~</> and <literal>!~*</>, as well as for the
-   <literal>LIKE</> operators <literal>~~</> and <literal>~~*</>, and
-   <literal>!~~</> and <literal>!~~*</>. If you'd like to match
-   case-sensitively, you can cast the operator's arguments to <type>text</>.
-  </para>
-
-  <para>
-   Similarly, all of the following functions perform matching
-   case-insensitively if their arguments are <type>citext</>:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-      <function>regexp_replace()</>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-      <function>regexp_split_to_array()</>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-      <function>regexp_split_to_table()</>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-      <function>replace()</>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-      <function>split_part()</>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-      <function>strpos()</>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-      <function>translate()</>
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   For the regexp functions, if you want to match case-sensitively, you can
-   specify the <quote>c</> flag to force a case-sensitive match.  Otherwise,
-   you must cast to <type>text</> before using one of these functions if
-   you want case-sensitive behavior.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>Limitations</title>
-
-   <itemizedlist>
-    <listitem>
-&common;
-
-     <para>
-      <type>citext</>'s case-folding behavior depends on
-      the <literal>LC_CTYPE</> setting of your database. How it compares
-      values is therefore determined when the database is created.
-      It is not truly
-      case-insensitive in the terms defined by the Unicode standard.
-      Effectively, what this means is that, as long as you're happy with your
-      collation, you should be happy with <type>citext</>'s comparisons. But
-      if you have data in different languages stored in your database, users
-      of one language may find their query results are not as expected if the
-      collation is for another language.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      As of <productname>PostgreSQL</> 9.1, you can attach a
-      <literal>COLLATE</> specification to <type>citext</> columns or data
-      values.  Currently, <type>citext</> operators will honor a non-default
-      <literal>COLLATE</> specification while comparing case-folded strings,
-      but the initial folding to lower case is always done according to the
-      database's <literal>LC_CTYPE</> setting (that is, as though
-      <literal>COLLATE "default"</> were given).  This may be changed in a
-      future release so that both steps follow the input <literal>COLLATE</>
-      specification.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-       <type>citext</> is not as efficient as <type>text</> because the
-       operator functions and the B-tree comparison functions must make copies
-       of the data and convert it to lower case for comparisons. It is,
-       however, slightly more efficient than using <function>lower</> to get
-       case-insensitive matching.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <type>citext</> doesn't help much if you need data to compare
-      case-sensitively in some contexts and case-insensitively in other
-      contexts.  The standard answer is to use the <type>text</> type and
-      manually use the <function>lower</> function when you need to compare
-      case-insensitively; this works all right if case-insensitive comparison
-      is needed only infrequently.  If you need case-insensitive behavior most
-      of the time and case-sensitive infrequently, consider storing the data
-      as <type>citext</> and explicitly casting the column to <type>text</>
-      when you want case-sensitive comparison.  In either situation, you will
-      need two indexes if you want both types of searches to be fast.
-    </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The schema containing the <type>citext</> operators must be
-      in the current <varname>search_path</> (typically <literal>public</>);
-      if it is not, the normal case-sensitive <type>text</> operators
-      will be invoked instead.
-    </para>
-    </listitem>
-   </itemizedlist>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   David E. Wheeler <email>[email protected]</email>
-  </para>
-
-  <para>
-    Inspired by the original <type>citext</> module by Donald Fraser.
-  </para>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/client-auth.sgmlin b/doc-xc/src/sgml/client-auth.sgmlin
deleted file mode 100644
index d43d626be3..0000000000
--- a/doc-xc/src/sgml/client-auth.sgmlin
+++ /dev/null
@@ -1,1938 +0,0 @@
-<!-- doc/src/sgml/client-auth.sgml -->
-
-<chapter id="client-authentication">
- <title>Client Authentication</title>
-
- <indexterm zone="client-authentication">
-  <primary>client authentication</primary>
- </indexterm>
-
-&common;
- <para>
-  When a client application connects to the database server, it
-<!## PG>
-  specifies which <productname>PostgreSQL</productname> database user name it
-<!## end>
-<!## XC>
-  specifies which <productname>Postgres-XC</productname> database user name it
-<!## end>
-<!## XL>
-  specifies which <productname>Postgres-XL</productname> database user name it
-<!## end>
-  wants to connect as, much the same way one logs into a Unix computer
-  as a particular user. Within the SQL environment the active database
-  user name determines access privileges to database objects &mdash; see
-  <xref linkend="user-manag"> for more information. Therefore, it is
-  essential to restrict which database users can connect.
- </para>
-
- <note>
-  <para>
-   As explained in <xref linkend="user-manag">,
-<!## PG>
-   <productname>PostgreSQL</productname> actually does privilege
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> actually does privilege
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> actually does privilege
-<!## end>
-   management in terms of <quote>roles</>.  In this chapter, we
-   consistently use <firstterm>database user</> to mean <quote>role with the
-   <literal>LOGIN</> privilege</quote>.
-  </para>
- </note>
-
- <para>
-  <firstterm>Authentication</firstterm> is the process by which the
-  database server establishes the identity of the client, and by
-  extension determines whether the client application (or the user
-  who runs the client application) is permitted to connect with the
-  database user name that was requested.
- </para>
-
- <para>
-<!## PG>
-  <productname>PostgreSQL</productname> offers a number of different
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> offers a number of different
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> offers a number of different
-<!## end>
-  client authentication methods. The method used to authenticate a
-  particular client connection can be selected on the basis of
-  (client) host address, database, and user.
- </para>
-
- <para>
-<!## PG>
-  <productname>PostgreSQL</productname> database user names are logically
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> database user names are logically
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> database user names are logically
-<!## end>
-  separate from user names of the operating system in which the server
-  runs. If all the users of a particular server also have accounts on
-  the server's machine, it makes sense to assign database user names
-  that match their operating system user names. However, a server that
-  accepts remote connections might have many database users who have no local
-  operating system
-  account, and in such cases there need be no connection between
-  database user names and OS user names.
- </para>
-
- <sect1 id="auth-pg-hba-conf">
-  <title>The <filename>pg_hba.conf</filename> File</title>
-
-  <indexterm zone="auth-pg-hba-conf">
-   <primary>pg_hba.conf</primary>
-  </indexterm>
-&common;
-
-  <para>
-   Client authentication is controlled by a configuration file,
-   which traditionally is named
-   <filename>pg_hba.conf</filename> and is stored in the database
-   cluster's data directory.
-   (<acronym>HBA</> stands for host-based authentication.) A default
-   <filename>pg_hba.conf</filename> file is installed when the data
-   directory is initialized by <command>initdb</command>.  It is
-   possible to place the authentication configuration file elsewhere,
-   however; see the <xref linkend="guc-hba-file"> configuration parameter.
-  </para>
-
-  <para>
-   The general format of the <filename>pg_hba.conf</filename> file is
-   a set of records, one per line. Blank lines are ignored, as is any
-   text after the <literal>#</literal> comment character.
-   Records cannot be continued across lines.
-   A record is made
-   up of a number of fields which are separated by spaces and/or tabs.
-   Fields can contain white space if the field value is quoted.
-   Quoting one of the keywords in a database, user, or address field (e.g.,
-   <literal>all</> or <literal>replication</>) makes the word lose its special
-   character, and just match a database, user, or host with that name.
-  </para>
-
-  <para>
-   Each record specifies a connection type, a client IP address range
-   (if relevant for the connection type), a database name, a user name,
-   and the authentication method to be used for connections matching
-   these parameters. The first record with a matching connection type,
-   client address, requested database, and user name is used to perform
-   authentication. There is no <quote>fall-through</> or
-   <quote>backup</>: if one record is chosen and the authentication
-   fails, subsequent records are not considered. If no record matches,
-   access is denied.
-  </para>
-
-  <para>
-   A record can have one of the seven formats
-<synopsis>
-local      <replaceable>database</replaceable>  <replaceable>user</replaceable>  <replaceable>auth-method</replaceable>  <optional><replaceable>auth-options</replaceable></optional>
-host       <replaceable>database</replaceable>  <replaceable>user</replaceable>  <replaceable>address</replaceable>  <replaceable>auth-method</replaceable>  <optional><replaceable>auth-options</replaceable></optional>
-hostssl    <replaceable>database</replaceable>  <replaceable>user</replaceable>  <replaceable>address</replaceable>  <replaceable>auth-method</replaceable>  <optional><replaceable>auth-options</replaceable></optional>
-hostnossl  <replaceable>database</replaceable>  <replaceable>user</replaceable>  <replaceable>address</replaceable>  <replaceable>auth-method</replaceable>  <optional><replaceable>auth-options</replaceable></optional>
-host       <replaceable>database</replaceable>  <replaceable>user</replaceable>  <replaceable>IP-address</replaceable>  <replaceable>IP-mask</replaceable>  <replaceable>auth-method</replaceable>  <optional><replaceable>auth-options</replaceable></optional>
-hostssl    <replaceable>database</replaceable>  <replaceable>user</replaceable>  <replaceable>IP-address</replaceable>  <replaceable>IP-mask</replaceable>  <replaceable>auth-method</replaceable>  <optional><replaceable>auth-options</replaceable></optional>
-hostnossl  <replaceable>database</replaceable>  <replaceable>user</replaceable>  <replaceable>IP-address</replaceable>  <replaceable>IP-mask</replaceable>  <replaceable>auth-method</replaceable>  <optional><replaceable>auth-options</replaceable></optional>
-</synopsis>
-   The meaning of the fields is as follows:
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>local</literal></term>
-     <listitem>
-      <para>
-       This record matches connection attempts using Unix-domain
-       sockets.  Without a record of this type, Unix-domain socket
-       connections are disallowed.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>host</literal></term>
-     <listitem>
-      <para>
-       This record matches connection attempts made using TCP/IP.
-       <literal>host</literal> records match either
-       <acronym>SSL</acronym> or non-<acronym>SSL</acronym> connection
-       attempts.
-      </para>
-     <note>
-      <para>
-       Remote TCP/IP connections will not be possible unless
-       the server is started with an appropriate value for the
-       <xref linkend="guc-listen-addresses"> configuration parameter,
-       since the default behavior is to listen for TCP/IP connections
-       only on the local loopback address <literal>localhost</>.
-      </para>
-     </note>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>hostssl</literal></term>
-     <listitem>
-      <para>
-       This record matches connection attempts made using TCP/IP,
-       but only when the connection is made with <acronym>SSL</acronym>
-       encryption.
-      </para>
-
-      <para>
-       To make use of this option the server must be built with
-       <acronym>SSL</acronym> support. Furthermore,
-       <acronym>SSL</acronym> must be enabled at server start time
-       by setting the <xref linkend="guc-ssl"> configuration parameter (see
-       <xref linkend="ssl-tcp"> for more information).
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>hostnossl</literal></term>
-     <listitem>
-      <para>
-       This record type has the opposite behavior of <literal>hostssl</>;
-       it only matches connection attempts made over
-       TCP/IP that do not use <acronym>SSL</acronym>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>database</replaceable></term>
-     <listitem>
-      <para>
-       Specifies which database name(s) this record matches.  The value
-       <literal>all</literal> specifies that it matches all databases.
-       The value <literal>sameuser</> specifies that the record
-       matches if the requested database has the same name as the
-       requested user.  The value <literal>samerole</> specifies that
-       the requested user must be a member of the role with the same
-       name as the requested database.  (<literal>samegroup</> is an
-       obsolete but still accepted spelling of <literal>samerole</>.)
-       The value <literal>replication</> specifies that the record
-       matches if a replication connection is requested (note that
-       replication connections do not specify any particular database).
-       Otherwise, this is the name of
-<!## PG>
-       a specific <productname>PostgreSQL</productname> database.
-<!## end>
-<!## XC>
-       a specific <productname>Postgres-XC</productname> database.
-<!## end>
-<!## XL>
-       a specific <productname>Postgres-XL</productname> database.
-<!## end>
-       Multiple database names can be supplied by separating them with
-       commas.  A separate file containing database names can be specified by
-       preceding the file name with <literal>@</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>user</replaceable></term>
-     <listitem>
-      <para>
-       Specifies which database user name(s) this record
-       matches. The value <literal>all</literal> specifies that it
-       matches all users.  Otherwise, this is either the name of a specific
-       database user, or a group name preceded by <literal>+</>.
-       (Recall that there is no real distinction between users and groups
-<!## PG>
-       in <productname>PostgreSQL</>; a <literal>+</> mark really means
-<!## end>
-<!## XC>
-       in <productname>Postgres-XC</>; a <literal>+</> mark really means
-<!## end>
-<!## XL>
-       in <productname>Postgres-XL</>; a <literal>+</> mark really means
-<!## end>
-       <quote>match any of the roles that are directly or indirectly members
-       of this role</>, while a name without a <literal>+</> mark matches
-       only that specific role.)
-       Multiple user names can be supplied by separating them with commas.
-       A separate file containing user names can be specified by preceding the
-       file name with <literal>@</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>address</replaceable></term>
-     <listitem>
-      <para>
-       Specifies the client machine addresses that this record
-       matches.  This field can contain either a host name, an IP
-       address range, or one of the special key words mentioned below.
-      </para>
-
-      <para>
-       An IP address is specified in standard dotted decimal
-       notation with a <acronym>CIDR</> mask length.  The mask
-       length indicates the number of high-order bits of the client
-       IP address that must match.  Bits to the right of this must
-       be zero in the given IP address.
-       There must not be any white space between the IP address, the
-       <literal>/</literal>, and the CIDR mask length.
-      </para>
-
-      <para>
-       Typical examples of an IP address range specified this way are
-       <literal>172.20.143.89/32</literal> for a single host, or
-       <literal>172.20.143.0/24</literal> for a small network, or
-       <literal>10.6.0.0/16</literal> for a larger one.
-       <literal>0.0.0.0/0</literal> represents all
-       IPv4 addresses, and <literal>::/0</literal> represents
-       all IPv6 addresses.
-       To specify a single host, use a CIDR mask of 32 for IPv4 or
-       128 for IPv6.  In a network address, do not omit trailing zeroes.
-      </para>
-
-      <para>
-       An IP address given in IPv4 format will match IPv6 connections that
-       have the corresponding address, for example <literal>127.0.0.1</>
-       will match the IPv6 address <literal>::ffff:127.0.0.1</>.  An entry
-       given in IPv6 format will match only IPv6 connections, even if the
-       represented address is in the IPv4-in-IPv6 range.  Note that entries
-       in IPv6 format will be rejected if the system's C library does not have
-       support for IPv6 addresses.
-      </para>
-
-      <para>
-       You can also write <literal>all</literal> to match any IP address,
-       <literal>samehost</literal> to match any of the server's own IP
-       addresses, or <literal>samenet</literal> to match any address in any
-       subnet that the server is directly connected to.
-      </para>
-
-      <para>
-       If a host name is specified (anything that is not an IP address
-       or a special key word is processed as a potential host name),
-       that name is compared with the result of a reverse name
-       resolution of the client's IP address (e.g., reverse DNS
-       lookup, if DNS is used).  Host name comparisons are case
-       insensitive.  If there is a match, then a forward name
-       resolution (e.g., forward DNS lookup) is performed on the host
-       name to check whether any of the addresses it resolves to are
-       equal to the client's IP address.  If both directions match,
-       then the entry is considered to match.  (The host name that is
-       used in <filename>pg_hba.conf</filename> should be the one that
-       address-to-name resolution of the client's IP address returns,
-       otherwise the line won't be matched.  Some host name databases
-       allow associating an IP address with multiple host names, but
-       the operating system will only return one host name when asked
-       to resolve an IP address.)
-      </para>
-
-      <para>
-       A host name specification that starts with a dot
-       (<literal>.</literal>) matches a suffix of the actual host
-       name.  So <literal>.example.com</literal> would match
-       <literal>foo.example.com</literal> (but not just
-       <literal>example.com</literal>).
-      </para>
-
-      <para>
-       When host names are specified
-       in <filename>pg_hba.conf</filename>, you should make sure that
-       name resolution is reasonably fast.  It can be of advantage to
-       set up a local name resolution cache such
-       as <command>nscd</command>.  Also, you may wish to enable the
-       configuration parameter <varname>log_hostname</varname> to see
-       the client's host name instead of the IP address in the log.
-      </para>
-
-      <sidebar>
-       <para>
-        Occasionally, users have wondered why host names are handled
-        in this seemingly complicated way with two name resolutions
-        and requiring reverse lookup of IP addresses, which is
-        sometimes not set up or points to some undesirable host name.
-        It is primarily for efficiency: A connection attempt requires
-        two resolver lookups of the current client's address.  If
-        there is resolver problem with that address, it becomes only
-        that client's problem.  A hypothetical alternative
-        implementation which only does forward lookups would have to
-        resolve every host name mentioned in
-        <filename>pg_hba.conf</filename> at every connection attempt.
-        That would already be slow by itself.  And if there is a
-        resolver problem with one of the host names, it becomes
-        everyone's problem.
-       </para>
-
-       <para>
-        Also, a reverse lookup is necessary to implement the suffix
-        matching feature, because the actual client host name needs to
-        be known in order to match it against the pattern.
-       </para>
-
-       <para>
-        Note that this behavior is consistent with other popular
-        implementations of host name-based access control, such as the
-        Apache HTTP Server and TCP Wrappers.
-       </para>
-      </sidebar>
-
-      <para>
-       This field only applies to <literal>host</literal>,
-       <literal>hostssl</literal>, and <literal>hostnossl</> records.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>IP-address</replaceable></term>
-     <term><replaceable>IP-mask</replaceable></term>
-     <listitem>
-      <para>
-       These fields can be used as an alternative to the
-       <replaceable>CIDR-address</replaceable> notation. Instead of
-       specifying the mask length, the actual mask is specified in a
-       separate column. For example, <literal>255.0.0.0</> represents an IPv4
-       CIDR mask length of 8, and <literal>255.255.255.255</> represents a
-       CIDR mask length of 32.
-      </para>
-
-      <para>
-       These fields only apply to <literal>host</literal>,
-       <literal>hostssl</literal>, and <literal>hostnossl</> records.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>auth-method</replaceable></term>
-     <listitem>
-      <para>
-       Specifies the authentication method to use when a connection matches
-       this record. The possible choices are summarized here; details
-       are in <xref linkend="auth-methods">.
-
-       <variablelist>
-        <varlistentry>
-         <term><literal>trust</></term>
-         <listitem>
-         <para>
-          Allow the connection unconditionally. This method
-          allows anyone that can connect to the
-<!## PG>
-          <productname>PostgreSQL</productname> database server to login as
-          any <productname>PostgreSQL</productname> user they wish,
-<!## end>
-<!## XC>
-          <productname>Postgres-XC</productname> database server to login as
-          any <productname>Postgres-XC</productname> user they wish,
-<!## end>
-<!## XL>
-          <productname>Postgres-XL</productname> database server to login as
-          any <productname>Postgres-XL</productname> user they wish,
-<!## end>
-          without the need for a password or any other authentication.  See <xref
-          linkend="auth-trust"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>reject</></term>
-        <listitem>
-         <para>
-          Reject the connection unconditionally. This is useful for
-          <quote>filtering out</> certain hosts from a group, for example a
-          <literal>reject</> line could block a specific host from connecting,
-          while a later line allows the remaining hosts in a specific
-          network to connect.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>md5</></term>
-        <listitem>
-         <para>
-          Require the client to supply an MD5-encrypted password for
-          authentication.
-          See <xref linkend="auth-password"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>password</></term>
-        <listitem>
-         <para>
-          Require the client to supply an unencrypted password for
-          authentication.
-          Since the password is sent in clear text over the
-          network, this should not be used on untrusted networks.
-          See <xref linkend="auth-password"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>gss</></term>
-        <listitem>
-         <para>
-          Use GSSAPI to authenticate the user. This is only
-          available for TCP/IP connections. See <xref
-          linkend="gssapi-auth"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>sspi</></term>
-        <listitem>
-         <para>
-          Use SSPI to authenticate the user. This is only
-          available on Windows. See <xref
-          linkend="sspi-auth"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>krb5</></term>
-        <listitem>
-         <para>
-          Use Kerberos V5 to authenticate the user. This is only
-          available for TCP/IP connections.  See <xref
-          linkend="kerberos-auth"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>ident</></term>
-        <listitem>
-         <para>
-          Obtain the operating system user name of the client
-          by contacting the ident server on the client
-          and check if it matches the requested database user name.
-          Ident authentication can only be used on TCP/IP
-          connections. When specified for local connections, peer
-          authentication will be used instead.
-          See <xref linkend="auth-ident"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>peer</></term>
-        <listitem>
-         <para>
-          Obtain the client's operating system user name from the operating
-          system and check if it matches the requested database user name.
-          This is only available for local connections.
-          See <xref linkend="auth-peer"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>ldap</></term>
-        <listitem>
-         <para>
-          Authenticate using an <acronym>LDAP</> server. See <xref
-          linkend="auth-ldap"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>radius</></term>
-        <listitem>
-         <para>
-          Authenticate using a RADIUS server. See <xref
-          linkend="auth-radius"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>cert</></term>
-        <listitem>
-         <para>
-          Authenticate using SSL client certificates. See
-          <xref linkend="auth-cert"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>pam</></term>
-        <listitem>
-         <para>
-          Authenticate using the Pluggable Authentication Modules
-          (PAM) service provided by the operating system.  See <xref
-          linkend="auth-pam"> for details.
-         </para>
-        </listitem>
-       </varlistentry>
-      </variablelist>
-
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>auth-options</replaceable></term>
-     <listitem>
-      <para>
-       After the <replaceable>auth-method</> field, there can be field(s) of
-       the form <replaceable>name</><literal>=</><replaceable>value</> that
-       specify options for the authentication method. Details about which
-       options are available for which authentication methods appear below.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   Files included by <literal>@</> constructs are read as lists of names,
-   which can be separated by either whitespace or commas.  Comments are
-   introduced by <literal>#</literal>, just as in
-   <filename>pg_hba.conf</filename>, and nested <literal>@</> constructs are
-   allowed.  Unless the file name following <literal>@</> is an absolute
-   path, it is taken to be relative to the directory containing the
-   referencing file.
-  </para>
-
-  <para>
-   Since the <filename>pg_hba.conf</filename> records are examined
-   sequentially for each connection attempt, the order of the records is
-   significant. Typically, earlier records will have tight connection
-   match parameters and weaker authentication methods, while later
-   records will have looser match parameters and stronger authentication
-   methods. For example, one might wish to use <literal>trust</>
-   authentication for local TCP/IP connections but require a password for
-   remote TCP/IP connections. In this case a record specifying
-   <literal>trust</> authentication for connections from 127.0.0.1 would
-   appear before a record specifying password authentication for a wider
-   range of allowed client IP addresses.
-  </para>
-
-  <para>
-   The <filename>pg_hba.conf</filename> file is read on start-up and when
-   the main server process receives a
-   <systemitem>SIGHUP</systemitem><indexterm><primary>SIGHUP</primary></indexterm>
-   signal. If you edit the file on an
-   active system, you will need to signal the postmaster
-   (using <literal>pg_ctl reload</> or <literal>kill -HUP</>) to make it
-   re-read the file.
-  </para>
-
-  <tip>
-   <para>
-    To connect to a particular database, a user must not only pass the
-    <filename>pg_hba.conf</filename> checks, but must have the
-    <literal>CONNECT</> privilege for the database.  If you wish to
-    restrict which users can connect to which databases, it's usually
-    easier to control this by granting/revoking <literal>CONNECT</> privilege
-    than to put the rules in <filename>pg_hba.conf</filename> entries.
-   </para>
-  </tip>
-
-  <para>
-   Some examples of <filename>pg_hba.conf</filename> entries are shown in
-   <xref linkend="example-pg-hba.conf">. See the next section for details on the
-   different authentication methods.
-  </para>
-
-   <example id="example-pg-hba.conf">
-    <title>Example <filename>pg_hba.conf</filename> Entries</title>
-<programlisting>
-# Allow any user on the local system to connect to any database with
-# any database user name using Unix-domain sockets (the default for local
-# connections).
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-local   all             all                                     trust
-
-# The same using local loopback TCP/IP connections.
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-host    all             all             127.0.0.1/32            trust
-
-# The same as the previous line, but using a separate netmask column
-#
-# TYPE  DATABASE        USER            IP-ADDRESS      IP-MASK             METHOD
-host    all             all             127.0.0.1       255.255.255.255     trust
-
-# The same over IPv6.
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-host    all             all             ::1/128                 trust
-
-# The same using a host name (would typically cover both IPv4 and IPv6).
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-host    all             all             localhost               trust
-
-# Allow any user from any host with IP address 192.168.93.x to connect
-# to database "postgres" as the same user name that ident reports for
-# the connection (typically the operating system user name).
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-host    postgres        all             192.168.93.0/24         ident
-
-# Allow any user from host 192.168.12.10 to connect to database
-# "postgres" if the user's password is correctly supplied.
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-host    postgres        all             192.168.12.10/32        md5
-
-# Allow any user from hosts in the example.com domain to connect to
-# any database if the user's password is correctly supplied.
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-host    all             all             .example.com            md5
-
-# In the absence of preceding "host" lines, these two lines will
-# reject all connections from 192.168.54.1 (since that entry will be
-# matched first), but allow Kerberos 5 connections from anywhere else
-# on the Internet.  The zero mask causes no bits of the host IP
-# address to be considered, so it matches any host.
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-host    all             all             192.168.54.1/32         reject
-host    all             all             0.0.0.0/0               krb5
-
-# Allow users from 192.168.x.x hosts to connect to any database, if
-# they pass the ident check.  If, for example, ident says the user is
-# "bryanh" and he requests to connect as PostgreSQL user "guest1", the
-# connection is allowed if there is an entry in pg_ident.conf for map
-# "omicron" that says "bryanh" is allowed to connect as "guest1".
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-host    all             all             192.168.0.0/16          ident map=omicron
-
-# If these are the only three lines for local connections, they will
-# allow local users to connect only to their own databases (databases
-# with the same name as their database user name) except for administrators
-# and members of role "support", who can connect to all databases.  The file
-# $PGDATA/admins contains a list of names of administrators.  Passwords
-# are required in all cases.
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-local   sameuser        all                                     md5
-local   all             @admins                                 md5
-local   all             +support                                md5
-
-# The last two lines above can be combined into a single line:
-local   all             @admins,+support                        md5
-
-# The database column can also use lists and file names:
-local   db1,db2,@demodbs  all                                   md5
-</programlisting>
-   </example>
- </sect1>
-
- <sect1 id="auth-username-maps">
-  <title>User Name Maps</title>
-
-  <indexterm zone="auth-username-maps">
-   <primary>User name maps</primary>
-  </indexterm>
-&common;
-
-  <para>
-   When using an external authentication system like Ident or GSSAPI,
-   the name of the operating system user that initiated the connection
-   might not be the same as the database user he needs to connect as.
-   In this case, a user name map can be applied to map the operating system
-   user name to a database user.  To use user name mapping, specify
-   <literal>map</literal>=<replaceable>map-name</replaceable>
-   in the options field in <filename>pg_hba.conf</filename>. This option is
-   supported for all authentication methods that receive external user names.
-   Since different mappings might be needed for different connections,
-   the name of the map to be used is specified in the
-   <replaceable>map-name</replaceable> parameter in <filename>pg_hba.conf</filename>
-   to indicate which map to use for each individual connection.
-  </para>
-
-  <para>
-   User name maps are defined in the ident map file, which by default is named
-   <filename>pg_ident.conf</><indexterm><primary>pg_ident.conf</primary></indexterm>
-   and is stored in the
-   cluster's data directory.  (It is possible to place the map file
-   elsewhere, however; see the <xref linkend="guc-ident-file">
-   configuration parameter.)
-   The ident map file contains lines of the general form:
-<synopsis>
-<replaceable>map-name</> <replaceable>system-username</> <replaceable>database-username</>
-</synopsis>
-   Comments and whitespace are handled in the same way as in
-   <filename>pg_hba.conf</>.  The
-   <replaceable>map-name</> is an arbitrary name that will be used to
-   refer to this mapping in <filename>pg_hba.conf</filename>. The other
-   two fields specify an operating system user name and a matching
-   database user name. The same <replaceable>map-name</> can be
-   used repeatedly to specify multiple user-mappings within a single map.
-  </para>
-  <para>
-   There is no restriction regarding how many database users a given
-   operating system user can correspond to, nor vice versa.  Thus, entries
-   in a map should be thought of as meaning <quote>this operating system
-   user is allowed to connect as this database user</quote>, rather than
-   implying that they are equivalent.  The connection will be allowed if
-   there is any map entry that pairs the user name obtained from the
-   external authentication system with the database user name that the
-   user has requested to connect as.
-  </para>
-  <para>
-   If the <replaceable>system-username</> field starts with a slash (<literal>/</>),
-   the remainder of the field is treated as a regular expression.
-   (See <xref linkend="posix-syntax-details"> for details of
-<!## PG>
-   <productname>PostgreSQL</>'s regular expression syntax.)  The regular
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</>'s regular expression syntax.)  The regular
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</>'s regular expression syntax.)  The regular
-<!## end>
-   expression can include a single capture, or parenthesized subexpression,
-   which can then be referenced in the <replaceable>database-username</>
-   field as <literal>\1</> (backslash-one).  This allows the mapping of
-   multiple user names in a single line, which is particularly useful for
-   simple syntax substitutions.  For example, these entries
-<programlisting>
-mymap   /^(.*)@mydomain\.com$      \1
-mymap   /^(.*)@otherdomain\.com$   guest
-</programlisting>
-   will remove the domain part for users with system user names that end with
-   <literal>@mydomain.com</>, and allow any user whose system name ends with
-   <literal>@otherdomain.com</> to log in as <literal>guest</>.
-  </para>
-
-  <tip>
-   <para>
-    Keep in mind that by default, a regular expression can match just part of
-    a string.  It's usually wise to use <literal>^</> and <literal>$</>, as
-    shown in the above example, to force the match to be to the entire
-    system user name.
-   </para>
-  </tip>
-
-  <para>
-   The <filename>pg_ident.conf</filename> file is read on start-up and
-   when the main server process receives a
-   <systemitem>SIGHUP</systemitem><indexterm><primary>SIGHUP</primary></indexterm>
-   signal. If you edit the file on an
-   active system, you will need to signal the postmaster
-   (using <literal>pg_ctl reload</> or <literal>kill -HUP</>) to make it
-   re-read the file.
-  </para>
-
-  <para>
-   A <filename>pg_ident.conf</filename> file that could be used in
-   conjunction with the <filename>pg_hba.conf</> file in <xref
-   linkend="example-pg-hba.conf"> is shown in <xref
-   linkend="example-pg-ident.conf">. In this example, anyone
-   logged in to a machine on the 192.168 network that does not have the
-   operating system user name <literal>bryanh</>, <literal>ann</>, or
-   <literal>robert</> would not be granted access. Unix user
-   <literal>robert</> would only be allowed access when he tries to
-<!## PG>
-   connect as <productname>PostgreSQL</> user <literal>bob</>, not
-<!## end>
-<!## XC>
-   connect as <productname>Postgres-XC</> user <literal>bob</>, not
-<!## end>
-<!## XL>
-   connect as <productname>Postgres-XL</> user <literal>bob</>, not
-<!## end>
-   as <literal>robert</> or anyone else. <literal>ann</> would
-   only be allowed to connect as <literal>ann</>. User
-   <literal>bryanh</> would be allowed to connect as either
-   <literal>bryanh</> or as <literal>guest1</>.
-  </para>
-
-  <example id="example-pg-ident.conf">
-   <title>An Example <filename>pg_ident.conf</> File</title>
-<programlisting>
-# MAPNAME       SYSTEM-USERNAME         PG-USERNAME
-
-omicron         bryanh                  bryanh
-omicron         ann                     ann
-# bob has user name robert on these machines
-omicron         robert                  bob
-# bryanh can also connect as guest1
-omicron         bryanh                  guest1
-</programlisting>
-  </example>
- </sect1>
-
- <sect1 id="auth-methods">
-  <title>Authentication Methods</title>
-  <para>
-   The following subsections describe the authentication methods in more detail.
-  </para>
-
-  <sect2 id="auth-trust">
-   <title>Trust Authentication</title>
-
-&common;
-   <para>
-    When <literal>trust</> authentication is specified,
-<!## PG>
-     <productname>PostgreSQL</productname> assumes that anyone who can
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> assumes that anyone who can
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> assumes that anyone who can
-<!## end>
-    connect to the server is authorized to access the database with
-    whatever database user name they specify (even superuser names).
-    Of course, restrictions made in the <literal>database</> and
-    <literal>user</> columns still apply.
-    This method should only be used when there is adequate
-    operating-system-level protection on connections to the server.
-   </para>
-
-   <para>
-    <literal>trust</> authentication is appropriate and very
-    convenient for local connections on a single-user workstation.  It
-    is usually <emphasis>not</> appropriate by itself on a multiuser
-    machine.  However, you might be able to use <literal>trust</> even
-    on a multiuser machine, if you restrict access to the server's
-    Unix-domain socket file using file-system permissions.  To do this, set the
-    <varname>unix_socket_permissions</varname> (and possibly
-    <varname>unix_socket_group</varname>) configuration parameters as
-    described in <xref linkend="runtime-config-connection">.  Or you
-    could set the <varname>unix_socket_directory</varname>
-    configuration parameter to place the socket file in a suitably
-    restricted directory.
-   </para>
-
-   <para>
-    Setting file-system permissions only helps for Unix-socket connections.
-    Local TCP/IP connections are not restricted by file-system permissions.
-    Therefore, if you want to use file-system permissions for local security,
-    remove the <literal>host ... 127.0.0.1 ...</> line from
-    <filename>pg_hba.conf</>, or change it to a
-    non-<literal>trust</> authentication method.
-   </para>
-
-   <para>
-    <literal>trust</> authentication is only suitable for TCP/IP connections
-    if you trust every user on every machine that is allowed to connect
-    to the server by the <filename>pg_hba.conf</> lines that specify
-    <literal>trust</>.  It is seldom reasonable to use <literal>trust</>
-    for any TCP/IP connections other than those from <systemitem>localhost</> (127.0.0.1).
-   </para>
-
-  </sect2>
-
-  <sect2 id="auth-password">
-   <title>Password Authentication</title>
-
-   <indexterm>
-    <primary>MD5</>
-   </indexterm>
-   <indexterm>
-    <primary>password</primary>
-    <secondary>authentication</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    The password-based authentication methods are <literal>md5</>
-    and <literal>password</>. These methods operate
-    similarly except for the way that the password is sent across the
-    connection, namely MD5-hashed and clear-text respectively.
-   </para>
-
-   <para>
-    If you are at all concerned about password
-    <quote>sniffing</> attacks then <literal>md5</> is preferred.
-    Plain <literal>password</> should always be avoided if possible.
-    However, <literal>md5</> cannot be used with the <xref
-    linkend="guc-db-user-namespace"> feature.  If the connection is
-    protected by SSL encryption then <literal>password</> can be used
-    safely (though SSL certificate authentication might be a better
-    choice if one is depending on using SSL).
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> database passwords are
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> database passwords are
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> database passwords are
-<!## end>
-    separate from operating system user passwords. The password for
-    each database user is stored in the <literal>pg_authid</> system
-    catalog. Passwords can be managed with the SQL commands
-    <xref linkend="sql-createuser"> and
-    <xref linkend="sql-alterrole">,
-    e.g., <userinput>CREATE USER foo WITH PASSWORD 'secret'</userinput>.
-    If no password has been set up for a user, the stored password
-    is null and password authentication will always fail for that user.
-   </para>
-
-  </sect2>
-
-  <sect2 id="gssapi-auth">
-   <title>GSSAPI Authentication</title>
-
-   <indexterm zone="gssapi-auth">
-    <primary>GSSAPI</primary>
-   </indexterm>
-&common;
-
-   <para>
-    <productname>GSSAPI</productname> is an industry-standard protocol
-    for secure authentication defined in RFC 2743.
-<!## PG>
-    <productname>PostgreSQL</productname> supports
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> supports
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> supports
-<!## end>
-    <productname>GSSAPI</productname> with <productname>Kerberos</productname>
-    authentication according to RFC 1964. <productname>GSSAPI</productname>
-    provides automatic authentication (single sign-on) for systems
-    that support it. The authentication itself is secure, but the
-    data sent over the database connection will be sent unencrypted unless
-    <acronym>SSL</acronym> is used.
-   </para>
-
-   <para>
-    When <productname>GSSAPI</productname> uses
-    <productname>Kerberos</productname>, it uses a standard principal
-    in the format
-    <literal><replaceable>servicename</>/<replaceable>hostname</>@<replaceable>realm</></literal>. For information about the parts of the principal, and
-    how to set up the required keys, see <xref linkend="kerberos-auth">.
-   </para>
-
-   <para>
-<!## PG>
-    GSSAPI support has to be enabled when <productname>PostgreSQL</> is built;
-<!## end>
-<!## XC>
-    GSSAPI support has to be enabled when <productname>Postgres-XC</> is built;
-<!## end>
-<!## XL>
-    GSSAPI support has to be enabled when <productname>Postgres-XL</> is built;
-<!## end>
-    see <xref linkend="installation"> for more information.
-   </para>
-
-   <para>
-    The following configuration options are supported for <productname>GSSAPI</productname>:
-    <variablelist>
-     <varlistentry>
-      <term><literal>include_realm</literal></term>
-      <listitem>
-       <para>
-        If set to 1, the realm name from the authenticated user
-        principal is included in the system user name that's passed through
-        user name mapping (<xref linkend="auth-username-maps">). This is
-        useful for handling users from multiple realms.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>map</literal></term>
-      <listitem>
-       <para>
-        Allows for mapping between system and database user names. See
-        <xref linkend="auth-username-maps"> for details. For a Kerberos
-        principal <literal>username/[email protected]</literal>, the
-        user name used for mapping is <literal>username/hostbased</literal>
-        if <literal>include_realm</literal> is disabled, and
-        <literal>username/[email protected]</literal> if
-        <literal>include_realm</literal> is enabled.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>krb_realm</literal></term>
-      <listitem>
-       <para>
-        Sets the realm to match user principal names against. If this parameter
-        is set, only users of that realm will be accepted.  If it is not set,
-        users of any realm can connect, subject to whatever user name mapping
-        is done.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="sspi-auth">
-   <title>SSPI Authentication</title>
-
-   <indexterm zone="sspi-auth">
-    <primary>SSPI</primary>
-   </indexterm>
-&common;
-
-   <para>
-    <productname>SSPI</productname> is a <productname>Windows</productname>
-    technology for secure authentication with single sign-on.
-<!## PG>
-    <productname>PostgreSQL</productname> will use SSPI in
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> will use SSPI in
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> will use SSPI in
-<!## end>
-    <literal>negotiate</literal> mode, which will use
-    <productname>Kerberos</productname> when possible and automatically
-    fall back to <productname>NTLM</productname> in other cases.
-    <productname>SSPI</productname> authentication only works when both
-    server and client are running <productname>Windows</productname>.
-   </para>
-
-   <para>
-    When using <productname>Kerberos</productname> authentication,
-    <productname>SSPI</productname> works the same way
-    <productname>GSSAPI</productname> does; see <xref linkend="gssapi-auth">
-    for details.
-   </para>
-
-   <para>
-    The following configuration options are supported for <productname>SSPI</productname>:
-    <variablelist>
-
-     <varlistentry>
-      <term><literal>include_realm</literal></term>
-      <listitem>
-       <para>
-        If set to 1, the realm name from the authenticated user
-        principal is included in the system user name that's passed through
-        user name mapping (<xref linkend="auth-username-maps">). This is
-        useful for handling users from multiple realms.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>map</literal></term>
-      <listitem>
-       <para>
-        Allows for mapping between system and database user names. See
-        <xref linkend="auth-username-maps"> for details.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>krb_realm</literal></term>
-      <listitem>
-       <para>
-        Sets the realm to match user principal names against. If this parameter
-        is set, only users of that realm will be accepted.  If it is not set,
-        users of any realm can connect, subject to whatever user name mapping
-        is done.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="kerberos-auth">
-   <title>Kerberos Authentication</title>
-
-   <indexterm zone="kerberos-auth">
-    <primary>Kerberos</primary>
-   </indexterm>
-&common;
-
-   <note>
-    <para>
-     Native Kerberos authentication has been deprecated and should be used
-     only for backward compatibility. New and upgraded installations are
-     encouraged to use the industry-standard <productname>GSSAPI</productname>
-     authentication method (see <xref linkend="gssapi-auth">) instead.
-    </para>
-   </note>
-
-   <para>
-    <productname>Kerberos</productname> is an industry-standard secure
-    authentication system suitable for distributed computing over a public
-    network. A description of the <productname>Kerberos</productname> system
-    is beyond the scope of this document; in full generality it can be
-    quite complex (yet powerful). The
-    <ulink url="http://www.cmf.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html">
-    Kerberos <acronym>FAQ</></ulink> or
-    <ulink url="http://web.mit.edu/kerberos/www/">MIT Kerberos page</ulink>
-    can be good starting points for exploration.
-    Several sources for <productname>Kerberos</> distributions exist.
-    <productname>Kerberos</productname> provides secure authentication but
-    does not encrypt queries or data passed over the network;  for that
-    use <acronym>SSL</acronym>.
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</> supports Kerberos version 5.  Kerberos
-    support has to be enabled when <productname>PostgreSQL</> is built;
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> supports Kerberos version 5.  Kerberos
-    support has to be enabled when <productname>Postgres-XC</> is built;
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> supports Kerberos version 5.  Kerberos
-    support has to be enabled when <productname>Postgres-XL</> is built;
-<!## end>
-    see <xref linkend="installation"> for more information.
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</> operates like a normal Kerberos service.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> operates like a normal Kerberos service.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> operates like a normal Kerberos service.
-<!## end>
-    The name of the service principal is
-    <literal><replaceable>servicename</>/<replaceable>hostname</>@<replaceable>realm</></literal>.
-   </para>
-
-   <para>
-    <replaceable>servicename</> can be set on the server side using the
-    <xref linkend="guc-krb-srvname"> configuration parameter, and on the
-    client side using the <literal>krbsrvname</> connection parameter. (See
-    also <xref linkend="libpq-connect">.)  The installation default can be
-    changed from the default <literal>postgres</literal> at build time using
-    <literal>./configure --with-krb-srvnam=</><replaceable>whatever</>.
-    In most environments,
-    this parameter never needs to be changed. However, it is necessary
-<!## PG>
-    when supporting multiple <productname>PostgreSQL</> installations
-<!## end>
-<!## XC>
-    when supporting multiple <productname>Postgres-XC</> installations
-<!## end>
-<!## XL>
-    when supporting multiple <productname>Postgres-XL</> installations
-<!## end>
-    on the same host.
-    Some Kerberos implementations might also require a different service name,
-    such as Microsoft Active Directory which requires the service name
-    to be in upper case (<literal>POSTGRES</literal>).
-   </para>
-
-   <para>
-    <replaceable>hostname</> is the fully qualified host name of the
-    server machine. The service principal's realm is the preferred realm
-    of the server machine.
-   </para>
-
-   <para>
-<!## PG>
-    Client principals must have their <productname>PostgreSQL</> database user
-<!## end>
-<!## XC>
-    Client principals must have their <productname>Postgres-XC</> database user
-<!## end>
-<!## XL>
-    Client principals must have their <productname>Postgres-XL</> database user
-<!## end>
-    name as their first component, for example
-    <literal>pgusername@realm</>.  Alternatively, you can use a user name
-    mapping to map from the first component of the principal name to the
-    database user name.  By default, the realm of the client is
-<!## PG>
-    not checked by <productname>PostgreSQL</>. If you have cross-realm
-<!## end>
-<!## XC>
-    not checked by <productname>Postgres-XC</>. If you have cross-realm
-<!## end>
-<!## XL>
-    not checked by <productname>Postgres-XL</>. If you have cross-realm
-<!## end>
-    authentication enabled and need to verify the realm, use the
-    <literal>krb_realm</> parameter, or enable <literal>include_realm</>
-    and use user name mapping to check the realm.
-   </para>
-
-   <para>
-    Make sure that your server keytab file is readable (and preferably
-<!## PG>
-    only readable) by the <productname>PostgreSQL</productname> server
-<!## end>
-<!## XC>
-    only readable) by the <productname>Postgres-XC</productname> server
-<!## end>
-<!## XL>
-    only readable) by the <productname>Postgres-XL</productname> server
-<!## end>
-    account.  (See also <xref linkend="postgres-user">.) The location
-    of the key file is specified by the <xref
-    linkend="guc-krb-server-keyfile"> configuration
-    parameter. The default is
-    <filename>/usr/local/pgsql/etc/krb5.keytab</> (or whatever
-    directory was specified as <varname>sysconfdir</> at build time).
-   </para>
-
-   <para>
-    The keytab file is generated by the Kerberos software; see the
-    Kerberos documentation for details. The following example is
-   for MIT-compatible Kerberos 5 implementations:
-<screen>
-<prompt>kadmin% </><userinput>ank -randkey postgres/server.my.domain.org</>
-<prompt>kadmin% </><userinput>ktadd -k krb5.keytab postgres/server.my.domain.org</>
-</screen>
-   </para>
-
-   <para>
-    When connecting to the database make sure you have a ticket for a
-    principal matching the requested database user name. For example, for
-    database user name <literal>fred</>, principal
-    <literal>[email protected]</> would be able to connect. To also allow
-    principal <literal>fred/[email protected]</>, use a user name
-    map, as described in <xref linkend="auth-username-maps">.
-   </para>
-
-   <para>
-    If you use <ulink url="http://modauthkerb.sf.net">
-    <application>mod_auth_kerb</application></ulink>
-    and <application>mod_perl</application> on your
-    <productname>Apache</productname> web server, you can use
-    <literal>AuthType KerberosV5SaveCredentials</literal> with a
-    <application>mod_perl</application> script. This gives secure
-    database access over the web, with no additional passwords required.
-   </para>
-
-   <para>
-    The following configuration options are supported for
-    <productname>Kerberos</productname>:
-    <variablelist>
-     <varlistentry>
-      <term><literal>map</literal></term>
-      <listitem>
-       <para>
-        Allows for mapping between system and database user names. See
-        <xref linkend="auth-username-maps"> for details.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>include_realm</literal></term>
-      <listitem>
-       <para>
-        If set to 1, the realm name from the authenticated user
-        principal is included in the system user name that's passed through
-        user name mapping (<xref linkend="auth-username-maps">). This is
-        useful for handling users from multiple realms.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>krb_realm</literal></term>
-      <listitem>
-       <para>
-        Sets the realm to match user principal names against. If this parameter
-        is set, only users of that realm will be accepted.  If it is not set,
-        users of any realm can connect, subject to whatever user name mapping
-        is done.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>krb_server_hostname</literal></term>
-      <listitem>
-       <para>
-        Sets the host name part of the service principal.
-        This, combined with <varname>krb_srvname</>, is used to generate
-        the complete service principal, that is
-        <varname>krb_srvname</><literal>/</><varname>krb_server_hostname</><literal>@</>REALM.
-        If not set, the default is the server host name.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="auth-ident">
-   <title>Ident Authentication</title>
-
-   <indexterm>
-    <primary>ident</primary>
-   </indexterm>
-&common;
-
-   <para>
-    The ident authentication method works by obtaining the client's
-    operating system user name from an ident server and using it as
-    the allowed database user name (with an optional user name mapping).
-    This is only supported on TCP/IP connections.
-   </para>
-
-   <note>
-    <para>
-     When ident is specified for a local (non-TCP/IP) connection,
-     peer authentication (see <xref linkend="auth-peer">) will be
-     used instead.
-    </para>
-   </note>
-
-   <para>
-    The following configuration options are supported for <productname>ident</productname>:
-    <variablelist>
-     <varlistentry>
-      <term><literal>map</literal></term>
-      <listitem>
-       <para>
-        Allows for mapping between system and database user names. See
-        <xref linkend="auth-username-maps"> for details.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    The <quote>Identification Protocol</quote> is described in
-    RFC 1413. Virtually every Unix-like
-    operating system ships with an ident server that listens on TCP
-    port 113 by default. The basic functionality of an ident server
-    is to answer questions like <quote>What user initiated the
-    connection that goes out of your port <replaceable>X</replaceable>
-    and connects to my port <replaceable>Y</replaceable>?</quote>.
-<!## PG>
-    Since <productname>PostgreSQL</> knows both <replaceable>X</> and
-<!## end>
-<!## XC>
-    Since <productname>Postgres-XC</> knows both <replaceable>X</> and
-<!## end>
-<!## XL>
-    Since <productname>Postgres-XL</> knows both <replaceable>X</> and
-<!## end>
-    <replaceable>Y</> when a physical connection is established, it
-    can interrogate the ident server on the host of the connecting
-    client and can theoretically determine the operating system user
-    for any given connection.
-   </para>
-
-   <para>
-    The drawback of this procedure is that it depends on the integrity
-    of the client: if the client machine is untrusted or compromised,
-    an attacker could run just about any program on port 113 and
-    return any user name he chooses. This authentication method is
-    therefore only appropriate for closed networks where each client
-    machine is under tight control and where the database and system
-    administrators operate in close contact. In other words, you must
-    trust the machine running the ident server.
-    Heed the warning:
-    <blockquote>
-     <attribution>RFC 1413</attribution>
-     <para>
-      The Identification Protocol is not intended as an authorization
-      or access control protocol.
-     </para>
-    </blockquote>
-   </para>
-
-   <para>
-    Some ident servers have a nonstandard option that causes the returned
-    user name to be encrypted, using a key that only the originating
-    machine's administrator knows.  This option <emphasis>must not</> be
-<!## PG>
-     used when using the ident server with <productname>PostgreSQL</>,
-     since <productname>PostgreSQL</> does not have any way to decrypt the
-<!## end>
-<!## XC>
-    used when using the ident server with <productname>Postgres-XC</>,
-    since <productname>Postgres-XC</> does not have any way to decrypt the
-<!## end>
-<!## XL>
-    used when using the ident server with <productname>Postgres-XL</>,
-    since <productname>Postgres-XL</> does not have any way to decrypt the
-<!## end>
-    returned string to determine the actual user name.
-   </para>
-  </sect2>
-
-  <sect2 id="auth-peer">
-   <title>Peer Authentication</title>
-
-   <indexterm>
-    <primary>peer</primary>
-   </indexterm>
-
-&common;
-   <para>
-    The peer authentication method works by obtaining the client's
-    operating system user name from the kernel and using it as the
-    allowed database user name (with optional user name mapping). This
-    method is only supported on local connections.
-   </para>
-
-   <para>
-    The following configuration options are supported for <productname>peer</productname>:
-    <variablelist>
-     <varlistentry>
-      <term><literal>map</literal></term>
-      <listitem>
-       <para>
-        Allows for mapping between system and database user names. See
-        <xref linkend="auth-username-maps"> for details.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    Peer authentication is only available on operating systems providing
-    the <function>getpeereid()</> function, the <symbol>SO_PEERCRED</symbol>
-    socket parameter, or similar mechanisms.  Currently that includes
-    <systemitem class="osname">Linux</>,
-    most flavors of <systemitem class="osname">BSD</> including
-    <systemitem class="osname">Mac OS X</>,
-    and <systemitem class="osname">Solaris</systemitem>.
-   </para>
-
-  </sect2>
-
-  <sect2 id="auth-ldap">
-   <title>LDAP Authentication</title>
-
-   <indexterm zone="auth-ldap">
-    <primary>LDAP</primary>
-   </indexterm>
-&common;
-
-   <para>
-    This authentication method operates similarly to
-    <literal>password</literal> except that it uses LDAP
-    as the password verification method. LDAP is used only to validate
-    the user name/password pairs. Therefore the user must already
-    exist in the database before LDAP can be used for
-    authentication.
-   </para>
-
-   <para>
-    LDAP authentication can operate in two modes. In the first mode,
-    the server will bind to the distinguished name constructed as
-    <replaceable>prefix</> <replaceable>username</> <replaceable>suffix</>.
-    Typically, the <replaceable>prefix</> parameter is used to specify
-    <literal>cn=</>, or <replaceable>DOMAIN</><literal>\</> in an Active
-    Directory environment.  <replaceable>suffix</> is used to specify the
-    remaining part of the DN in a non-Active Directory environment.
-   </para>
-
-   <para>
-    In the second mode, the server first binds to the LDAP directory with
-    a fixed user name and password, specified with <replaceable>ldapbinduser</>
-    and <replaceable>ldapbinddn</>, and performs a search for the user trying
-    to log in to the database. If no user and password is configured, an
-    anonymous bind will be attempted to the directory. The search will be
-    performed over the subtree at <replaceable>ldapbasedn</>, and will try to
-    do an exact match of the attribute specified in
-    <replaceable>ldapsearchattribute</>. If no attribute is specified, the
-    <literal>uid</> attribute will be used. Once the user has been found in
-    this search, the server disconnects and re-binds to the directory as
-    this user, using the password specified by the client, to verify that the
-    login is correct. This method allows for significantly more flexibility
-    in where the user objects are located in the directory, but will cause
-    two separate connections to the LDAP server to be made.
-   </para>
-
-   <para>
-    The following configuration options are supported for LDAP:
-    <variablelist>
-     <varlistentry>
-      <term><literal>ldapserver</literal></term>
-      <listitem>
-       <para>
-        Name or IP of LDAP server to connect to.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>ldapport</literal></term>
-      <listitem>
-       <para>
-        Port number on LDAP server to connect to. If no port is specified,
-        the LDAP library's default port setting will be used.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>ldaptls</literal></term>
-      <listitem>
-       <para>
-<!## PG>
-        Set to 1 to make the connection between PostgreSQL and the
-<!## end>
-<!## XC>
-        Set to <literal>1</> to make the connection between Postgres-XC and the
-<!## end>
-<!## XL>
-        Set to <literal>1</> to make the connection between Postgres-XL and the
-<!## end>
-        LDAP server use TLS encryption. Note that this only encrypts
-        the traffic to the LDAP server &mdash; the connection to the client
-        will still be unencrypted unless SSL is used.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>ldapprefix</literal></term>
-      <listitem>
-       <para>
-        String to prepend to the user name when forming the DN to bind as,
-        when doing simple bind authentication.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>ldapsuffix</literal></term>
-      <listitem>
-       <para>
-        String to append to the user name when forming the DN to bind as,
-        when doing simple bind authentication.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>ldapbasedn</literal></term>
-      <listitem>
-       <para>
-        Root DN to begin the search for the user in, when doing search+bind
-        authentication.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>ldapbinddn</literal></term>
-      <listitem>
-       <para>
-        DN of user to bind to the directory with to perform the search when
-        doing search+bind authentication.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>ldapbindpasswd</literal></term>
-      <listitem>
-       <para>
-        Password for user to bind to the directory with to perform the search
-        when doing search+bind authentication.
-       </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-       <term><literal>ldapsearchattribute</literal></term>
-       <listitem>
-        <para>
-         Attribute to match against the user name in the search when doing
-         search+bind authentication.
-        </para>
-       </listitem>
-      </varlistentry>
-    </variablelist>
-   </para>
-
-   <note>
-    <para>
-     Since LDAP often uses commas and spaces to separate the different
-     parts of a DN, it is often necessary to use double-quoted parameter
-     values when configuring LDAP options, for example:
-<programlisting>
-ldapserver=ldap.example.net ldapprefix="cn=" ldapsuffix=", dc=example, dc=net"
-</programlisting>
-    </para>
-   </note>
-
-  </sect2>
-
-  <sect2 id="auth-radius">
-   <title>RADIUS Authentication</title>
-
-   <indexterm zone="auth-radius">
-    <primary>RADIUS</primary>
-   </indexterm>
-&common;
-
-   <para>
-    This authentication method operates similarly to
-    <literal>password</literal> except that it uses RADIUS
-    as the password verification method. RADIUS is used only to validate
-    the user name/password pairs. Therefore the user must already
-    exist in the database before RADIUS can be used for
-    authentication.
-   </para>
-
-   <para>
-    When using RADIUS authentication, an Access Request message will be sent
-    to the configured RADIUS server. This request will be of type
-    <literal>Authenticate Only</literal>, and include parameters for
-    <literal>user name</>, <literal>password</> (encrypted) and
-    <literal>NAS Identifier</>. The request will be encrypted using
-    a secret shared with the server. The RADIUS server will respond to
-    this server with either <literal>Access Accept</> or
-    <literal>Access Reject</>. There is no support for RADIUS accounting.
-   </para>
-
-   <para>
-    The following configuration options are supported for RADIUS:
-     <variablelist>
-      <varlistentry>
-       <term><literal>radiusserver</literal></term>
-       <listitem>
-        <para>
-         The name or IP address of the RADIUS server to connect to.
-         This parameter is required.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>radiussecret</literal></term>
-       <listitem>
-        <para>
-         The shared secret used when talking securely to the RADIUS
-<!## PG>
-         server. This must have exactly the same value on the PostgreSQL
-<!## end>
-<!## XC>
-         server. This must have exactly the same value on the Postgres-XC
-<!## end>
-<!## XL>
-         server. This must have exactly the same value on the Postgres-XL
-<!## end>
-         and RADIUS servers. It is recommended that this be a string of
-         at least 16 characters. This parameter is required.
-         <note>
-         <para>
-          The encryption vector used will only be cryptographically
-<!## PG>
-          strong if <productname>PostgreSQL</> is built with support for
-<!## end>
-<!## XC>
-          strong if <productname>Postgres-XC</> is built with support for
-<!## end>
-<!## XL>
-          strong if <productname>Postgres-XL</> is built with support for
-<!## end>
-          <productname>OpenSSL</>. In other cases, the transmission to the
-          RADIUS server should only be considered obfuscated, not secured, and
-          external security measures should be applied if necessary.
-         </para>
-         </note>
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>radiusport</literal></term>
-       <listitem>
-        <para>
-         The port number on the RADIUS server to connect to. If no port
-         is specified, the default port <literal>1812</> will be used.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>radiusidentifier</literal></term>
-       <listitem>
-        <para>
-         The string used as <literal>NAS Identifier</> in the RADIUS
-         requests. This parameter can be used as a second parameter
-         identifying for example which database user the user is attempting
-         to authenticate as, which can be used for policy matching on
-         the RADIUS server. If no identifier is specified, the default
-         <literal>postgresql</> will be used.
-        </para>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="auth-cert">
-   <title>Certificate Authentication</title>
-
-   <indexterm zone="auth-cert">
-    <primary>Certificate</primary>
-   </indexterm>
-&common;
-
-   <para>
-    This authentication method uses SSL client certificates to perform
-    authentication. It is therefore only available for SSL connections.
-    When using this authentication method, the server will require that
-    the client provide a valid certificate. No password prompt will be sent
-    to the client. The <literal>cn</literal> (Common Name) attribute of the
-    certificate
-    will be compared to the requested database user name, and if they match
-    the login will be allowed.  User name mapping can be used to allow
-    <literal>cn</literal> to be different from the database user name.
-   </para>
-
-   <para>
-    The following configuration options are supported for SSL certificate
-    authentication:
-    <variablelist>
-     <varlistentry>
-      <term><literal>map</literal></term>
-      <listitem>
-       <para>
-        Allows for mapping between system and database user names. See
-        <xref linkend="auth-username-maps"> for details.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="auth-pam">
-   <title>PAM Authentication</title>
-
-   <indexterm zone="auth-pam">
-    <primary>PAM</primary>
-   </indexterm>
-&common;
-
-   <para>
-    This authentication method operates similarly to
-    <literal>password</literal> except that it uses PAM (Pluggable
-    Authentication Modules) as the authentication mechanism. The
-    default PAM service name is <literal>postgresql</literal>.
-    PAM is used only to validate user name/password pairs.
-    Therefore the user must already exist in the database before PAM
-    can be used for authentication.  For more information about
-    PAM, please read the <ulink url="http://www.kernel.org/pub/linux/libs/pam/">
-    <productname>Linux-PAM</> Page</ulink>
-    and the <ulink url="http://www.sun.com/software/solaris/pam/">
-    <systemitem class="osname">Solaris</> PAM Page</ulink>.
-   </para>
-
-   <para>
-    The following configuration options are supported for PAM:
-    <variablelist>
-     <varlistentry>
-      <term><literal>pamservice</literal></term>
-      <listitem>
-       <para>
-        PAM service name.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <note>
-    <para>
-     If PAM is set up to read <filename>/etc/shadow</>, authentication
-<!## PG>
-     will fail because the PostgreSQL server is started by a non-root
-<!## end>
-<!## XC>
-     will fail because the Postgres-XC server is started by a non-root
-<!## end>
-<!## XL>
-     will fail because the Postgres-XL server is started by a non-root
-<!## end>
-     user.  However, this is not an issue when PAM is configured to use
-     LDAP or other authentication methods.
-    </para>
-   </note>
-  </sect2>
- </sect1>
-
-  <sect1 id="client-authentication-problems">
-   <title>Authentication Problems</title>
-
-&common;
-   <para>
-    Authentication failures and related problems generally
-    manifest themselves through error messages like the following:
-   </para>
-
-   <para>
-<programlisting>
-FATAL:  no pg_hba.conf entry for host "123.123.123.123", user "andym", database "testdb"
-</programlisting>
-    This is what you are most likely to get if you succeed in contacting
-    the server, but it does not want to talk to you. As the message
-    suggests, the server refused the connection request because it found
-    no matching entry in its <filename>pg_hba.conf</filename>
-    configuration file.
-   </para>
-
-   <para>
-<programlisting>
-FATAL:  password authentication failed for user "andym"
-</programlisting>
-    Messages like this indicate that you contacted the server, and it is
-    willing to talk to you, but not until you pass the authorization
-    method specified in the <filename>pg_hba.conf</filename> file. Check
-    the password you are providing, or check your Kerberos or ident
-    software if the complaint mentions one of those authentication
-    types.
-   </para>
-
-   <para>
-<programlisting>
-FATAL:  user "andym" does not exist
-</programlisting>
-    The indicated database user name was not found.
-   </para>
-
-   <para>
-<programlisting>
-FATAL:  database "testdb" does not exist
-</programlisting>
-    The database you are trying to connect to does not exist. Note that
-    if you do not specify a database name, it defaults to the database
-    user name, which might or might not be the right thing.
-   </para>
-
-   <tip>
-   <para>
-    The server log might contain more information about an
-    authentication failure than is reported to the client. If you are
-    confused about the reason for a failure, check the server log.
-   </para>
-   </tip>
-  </sect1>
-
- </chapter>
diff --git a/doc-xc/src/sgml/common.sgmlin b/doc-xc/src/sgml/common.sgmlin
deleted file mode 100644
index 5f18dcc5b4..0000000000
--- a/doc-xc/src/sgml/common.sgmlin
+++ /dev/null
@@ -1,14 +0,0 @@
-<!## XC>
-<note>
-<para>
-The following description applies both to <productname>Postgres-XC</> and <productname>PostgreSQL</> if not described explicitly.
-</para>
-</note>
-<!## end>
-<!## XL>
-<note>
-<para>
-The following description applies both to <productname>Postgres-XL</> and <productname>PostgreSQL</> if not described explicitly.
-</para>
-</note>
-<!## end>
diff --git a/doc-xc/src/sgml/config.sgmlin b/doc-xc/src/sgml/config.sgmlin
deleted file mode 100644
index 9ed17fd759..0000000000
--- a/doc-xc/src/sgml/config.sgmlin
+++ /dev/null
@@ -1,7544 +0,0 @@
-<!-- doc/src/sgml/config.sgml -->
-
-<chapter id="runtime-config">
-<!## PG>
-  <title>Server Configuration</title>
-<!## end>
-<!## XC>
-  <title>Coordinator and Datanode Configuration</title>
-<!## end>
-<!## XL>
-  <title>Coordinator and Datanode Configuration</title>
-<!## end>
-
-  <indexterm>
-   <primary>configuration</primary>
-   <secondary>of the server</secondary>
-  </indexterm>
-
-&common;
-<!## PG>
-  <para>
-   There are many configuration parameters that affect the behavior of
-   the database system. In the first section of this chapter, we
-   describe how to set configuration parameters. The subsequent sections
-   discuss each parameter in detail.
-  </para>
-<!## end>
-<!## XC>
-  <para>
-   There are many configuration parameters that affect the behavior of
-   the database system. In the first section of this chapter, we
-   describe how to set configuration parameters for Coordinator and
-   Datanodes. The subsequent sections discuss each parameter in
-   detail.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   There are many configuration parameters that affect the behavior of
-   the database system. In the first section of this chapter, we
-   describe how to set configuration parameters for Coordinator and
-   Datanodes. The subsequent sections discuss each parameter in
-   detail.
-  </para>
-<!## end>
-
-  <sect1 id="config-setting">
-   <title>Setting Parameters</title>
-
-&common;
-   <para>
-    All parameter names are case-insensitive. Every parameter takes a
-    value of one of five types: Boolean, integer, floating point,
-    string or enum. Boolean values can be written as <literal>on</literal>,
-    <literal>off</literal>, <literal>true</literal>,
-    <literal>false</literal>, <literal>yes</literal>,
-    <literal>no</literal>, <literal>1</literal>, <literal>0</literal>
-    (all case-insensitive) or any unambiguous prefix of these.
-   </para>
-
-   <para>
-    Some settings specify a memory or time value.  Each of these has an
-    implicit unit, which is either kilobytes, blocks (typically eight
-    kilobytes), milliseconds, seconds, or minutes.  Default units can be
-    found by referencing <structname>pg_settings</>.<structfield>unit</>.
-    For convenience,
-    a different unit can also be specified explicitly.  Valid memory units
-    are <literal>kB</literal> (kilobytes), <literal>MB</literal>
-    (megabytes), and <literal>GB</literal> (gigabytes); valid time units
-    are <literal>ms</literal> (milliseconds), <literal>s</literal>
-    (seconds), <literal>min</literal> (minutes), <literal>h</literal>
-    (hours), and <literal>d</literal> (days).  Note that the multiplier
-    for memory units is 1024, not 1000.
-   </para>
-
-   <para>
-    Parameters of type <quote>enum</> are specified in the same way as string
-    parameters, but are restricted to a limited set of values.  The allowed
-    values can be found
-    from <structname>pg_settings</>.<structfield>enumvals</>.
-    Enum parameter values are case-insensitive.
-   </para>
-
-   <para>
-    One way to set these parameters is to edit the file
-    <filename>postgresql.conf</><indexterm><primary>postgresql.conf</></>,
-    which is normally kept in the data directory.  (A default copy is
-    installed there when the database cluster directory is
-    initialized.)  An example of what this file might look like is:
-<programlisting>
-# This is a comment
-log_connections = yes
-log_destination = 'syslog'
-search_path = '"$user", public'
-shared_buffers = 128MB
-</programlisting>
-    One parameter is specified per line. The equal sign between name and
-    value is optional. Whitespace is insignificant and blank lines are
-    ignored. Hash marks (<literal>#</literal>) designate the rest of the
-    line as a comment.  Parameter values that are not simple identifiers or
-    numbers must be single-quoted.  To embed a single quote in a parameter
-    value, write either two quotes (preferred) or backslash-quote.
-   </para>
-
-   <para>
-    <indexterm>
-     <primary><literal>include</></primary>
-     <secondary>in configuration file</secondary>
-    </indexterm>
-    In addition to parameter settings, the <filename>postgresql.conf</>
-    file can contain <firstterm>include directives</>, which specify
-    another file to read and process as if it were inserted into the
-    configuration file at this point.  Include directives simply look like:
-<programlisting>
-include 'filename'
-</programlisting>
-    If the file name is not an absolute path, it is taken as relative to
-    the directory containing the referencing configuration file.
-    Inclusions can be nested.
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>SIGHUP</primary>
-    </indexterm>
-<!## PG>
-    The configuration file is reread whenever the main server process receives a
-    <systemitem>SIGHUP</> signal (which is most easily sent by means
-    of <literal>pg_ctl reload</>). The main server process
-    also propagates this signal to all currently running server
-    processes so that existing sessions also get the new
-    value. Alternatively, you can send the signal to a single server
-    process directly.  Some parameters can only be set at server start;
-    any changes to their entries in the configuration file will be ignored
-    until the server is restarted.
-<!## end>
-<!## XC>
-    The configuration file is reread whenever the main Coordinator/Datanode process receives a
-    <systemitem>SIGHUP</> signal (which is most easily sent by means
-    of <literal>pg_ctl reload</>). The main Coordinator/Datanode process
-    also propagates this signal to all currently running server
-    processes so that existing sessions also get the new
-    value. Alternatively, you can send the signal to a single server
-    process directly.  Some parameters can only be set at server start;
-    any changes to their entries in the configuration file will be ignored
-    until the server is restarted.
-<!## end>
-<!## XL>
-    The configuration file is reread whenever the main Coordinator/Datanode process receives a
-    <systemitem>SIGHUP</> signal (which is most easily sent by means
-    of <literal>pg_ctl reload</>). The main Coordinator/Datanode process
-    also propagates this signal to all currently running server
-    processes so that existing sessions also get the new
-    value. Alternatively, you can send the signal to a single server
-    process directly.  Some parameters can only be set at server start;
-    any changes to their entries in the configuration file will be ignored
-    until the server is restarted.
-<!## end>
-   </para>
-
-   <para>
-    A second way to set these configuration parameters is to give them
-    as a command-line option to the <command>postgres</command> command, such as:
-<!## PG>
-<programlisting>
-postgres -c log_connections=yes -c log_destination='syslog'
-</programlisting>
-<!## end>
-<!## XC>
-<programlisting>
-postgres --coordinator -c log_connections=yes -c log_destination='syslog'
-</programlisting>
-<!## end>
-<!## XL>
-<programlisting>
-postgres --coordinator -c log_connections=yes -c log_destination='syslog'
-</programlisting>
-<!## end>
-    Command-line options override any conflicting settings in
-    <filename>postgresql.conf</filename>.  Note that this means you won't
-    be able to change the value on-the-fly by editing
-    <filename>postgresql.conf</filename>, so while the command-line
-    method might be convenient, it can cost you flexibility later.
-   </para>
-
-   <para>
-    Occasionally it is useful to give a command line option to
-    one particular session only. The environment variable
-    <envar>PGOPTIONS</envar> can be used for this purpose on the
-    client side:
-<programlisting>
-env PGOPTIONS='-c geqo=off' psql
-</programlisting>
-    (This works for any <application>libpq</>-based client application, not
-    just <application>psql</application>.) Note that this won't work for
-    parameters that are fixed when the server is started or that must be
-    specified in <filename>postgresql.conf</filename>.
-   </para>
-
-   <para>
-    Furthermore, it is possible to assign a set of parameter settings to
-    a user or a database.  Whenever a session is started, the default
-    settings for the user and database involved are loaded.  The
-    commands <xref linkend="sql-alterrole">
-    and <xref linkend="sql-alterdatabase">,
-    respectively, are used to configure these settings.  Per-database
-    settings override anything received from the
-    <command>postgres</command> command-line or the configuration
-    file, and in turn are overridden by per-user settings; both are
-    overridden by per-session settings.
-   </para>
-
-   <para>
-    Some parameters can be changed in individual <acronym>SQL</acronym>
-    sessions with the <xref linkend="SQL-SET">
-    command, for example:
-<screen>
-SET ENABLE_SEQSCAN TO OFF;
-</screen>
-    If <command>SET</> is allowed, it overrides all other sources of
-    values for the parameter. Some parameters cannot be changed via
-    <command>SET</command>: for example, if they control behavior that
-    cannot be changed without restarting the entire
-<!## PG>
-    <productname>PostgreSQL</productname> server.  Also,
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> server.  Also,
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> server.  Also,
-<!## end>
-    some <command>SET</command> or <command>ALTER</> parameter modifications
-    require superuser permission.
-   </para>
-
-   <para>
-    The <xref linkend="SQL-SHOW">
-    command allows inspection of the current values of all parameters.
-   </para>
-
-   <para>
-    The virtual table <structname>pg_settings</structname> also allows
-    displaying and updating session run-time parameters;  see <xref
-    linkend="view-pg-settings"> for details and a description of the
-    different variable types and when they can be changed.
-    <structname>pg_settings</structname> is equivalent to <command>SHOW</>
-    and <command>SET</>, but can be more convenient
-    to use because it can be joined with other tables, or selected from using
-    any desired selection condition. It also contains more information about
-    what values are allowed for the parameters.
-   </para>
-  </sect1>
-
-   <sect1 id="runtime-config-file-locations">
-    <title>File Locations</title>
-&common;
-     <para>
-      In addition to the <filename>postgresql.conf</filename> file
-<!## PG>
-      already mentioned, <productname>PostgreSQL</productname> uses
-<!## end>
-<!## XC>
-      already mentioned, <productname>Postgres-XC</productname> uses
-<!## end>
-<!## XL>
-      already mentioned, <productname>Postgres-XL</productname> uses
-<!## end>
-      two other manually-edited configuration files, which control
-      client authentication (their use is discussed in <xref
-      linkend="client-authentication">).  By default, all three
-      configuration files are stored in the database cluster's data
-      directory.  The parameters described in this section allow the
-      configuration files to be placed elsewhere.  (Doing so can ease
-      administration.  In particular it is often easier to ensure that
-      the configuration files are properly backed-up when they are
-      kept separate.)
-     </para>
-
-     <variablelist>
-     <varlistentry id="guc-data-directory" xreflabel="data_directory">
-      <term><varname>data_directory</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>data_directory</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-         Specifies the directory to use for data storage.
-         This parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-config-file" xreflabel="config_file">
-      <term><varname>config_file</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>config_file</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-         Specifies the main server configuration file
-         (customarily called <filename>postgresql.conf</>).
-         This parameter can only be set on the <command>postgres</command> command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-hba-file" xreflabel="hba_file">
-      <term><varname>hba_file</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>hba_file</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-         Specifies the configuration file for host-based authentication
-         (customarily called <filename>pg_hba.conf</>).
-         This parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-ident-file" xreflabel="ident_file">
-      <term><varname>ident_file</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>ident_file</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-         Specifies the configuration file for
-         <xref linkend="auth-username-maps"> user name mapping
-         (customarily called <filename>pg_ident.conf</>).
-         This parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-external-pid-file" xreflabel="external_pid_file">
-      <term><varname>external_pid_file</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>external_pid_file</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the name of an additional process-id (PID) file that the
-        server should create for use by server administration programs.
-        This parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-     </variablelist>
-
-     <para>
-      In a default installation, none of the above parameters are set
-      explicitly.  Instead, the
-      data directory is specified by the <option>-D</option> command-line
-      option or the <envar>PGDATA</envar> environment variable, and the
-      configuration files are all found within the data directory.
-     </para>
-
-     <para>
-      If you wish to keep the configuration files elsewhere than the
-      data directory, the <command>postgres</command> <option>-D</option>
-      command-line option or <envar>PGDATA</envar> environment variable
-      must point to the directory containing the configuration files,
-      and the <varname>data_directory</> parameter must be set in
-      <filename>postgresql.conf</filename> (or on the command line) to show
-      where the data directory is actually located.  Notice that
-      <varname>data_directory</> overrides <option>-D</option> and
-      <envar>PGDATA</envar> for the location
-      of the data directory, but not for the location of the configuration
-      files.
-     </para>
-
-     <para>
-      If you wish, you can specify the configuration file names and locations
-      individually using the parameters <varname>config_file</>,
-      <varname>hba_file</> and/or <varname>ident_file</>.
-      <varname>config_file</> can only be specified on the
-      <command>postgres</command> command line, but the others can be
-      set within the main configuration file.  If all three parameters plus
-      <varname>data_directory</> are explicitly set, then it is not necessary
-      to specify <option>-D</option> or <envar>PGDATA</envar>.
-     </para>
-
-     <para>
-      When setting any of these parameters, a relative path will be interpreted
-      with respect to the directory in which <command>postgres</command>
-      is started.
-     </para>
-   </sect1>
-
-   <sect1 id="runtime-config-connection">
-    <title>Connections and Authentication</title>
-
-    <sect2 id="runtime-config-connection-settings">
-     <title>Connection Settings</title>
-&common;
-     <variablelist>
-
-     <varlistentry id="guc-listen-addresses" xreflabel="listen_addresses">
-      <term><varname>listen_addresses</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>listen_addresses</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-         Specifies the TCP/IP address(es) on which the server is
-         to listen for connections from client applications.
-         The value takes the form of a comma-separated list of host names
-         and/or numeric IP addresses.  The special entry <literal>*</>
-         corresponds to all available IP interfaces.  The entry
-         <literal>0.0.0.0</> allows listening for all IPv4 addresses and
-         <literal>::</> allows listening for all IPv6 addresses.
-         If the list is empty, the server does not listen on any IP interface
-         at all, in which case only Unix-domain sockets can be used to connect
-         to it.
-         The default value is <systemitem class="systemname">localhost</>,
-         which allows only local TCP/IP <quote>loopback</> connections to be
-         made.  While client authentication (<xref
-         linkend="client-authentication">) allows fine-grained control
-         over who can access the server, <varname>listen_addresses</varname>
-         controls which interfaces accept connection attempts, which
-         can help prevent repeated malicious connection requests on
-         insecure network interfaces.  This parameter can only be set
-         at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-port" xreflabel="port">
-      <term><varname>port</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>port</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        The TCP port the server listens on; 5432 by default.  Note that the
-        same port number is used for all IP addresses the server listens on.
-        This parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-connections" xreflabel="max_connections">
-      <term><varname>max_connections</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_connections</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Determines the maximum number of concurrent connections to the
-        database server. The default is typically 100 connections, but
-        might be less if your kernel settings will not support it (as
-        determined during <application>initdb</>).  This parameter can
-        only be set at server start.
-       </para>
-
-<!## XC>
-       <para>
-        In the case of the Coordinator, this parameter determines how many 
-        connections can each Coordinator accept.
-       </para>
-       <para>
-        In the case of the Datanode, number of connection to each
-        Datanode may become as large as <varname>max_connections</>
-        multiplied by the number of Coordinators.
-       </para>
-<!## end>
-<!## XL>
-       <para>
-        In the case of the Coordinator, this parameter determines how many 
-        connections can each Coordinator accept.
-       </para>
-       <para>
-        In the case of the Datanode, number of connection to each
-        Datanode may become as large as <varname>max_connections</>
-        multiplied by the number of Coordinators.
-       </para>
-<!## end>
-
-       <para>
-<!## PG>
-        Increasing this parameter might cause <productname>PostgreSQL</>
-        to request more <systemitem class="osname">System V</> shared
-        memory or semaphores than your operating system's default configuration
-        allows. See <xref linkend="sysvipc"> for information on how to
-        adjust those parameters, if necessary.
-<!## end>
-<!## XC>
-        Increasing this parameter might cause <filename>Coordinator</> or <filename>Datanode</>
-        to request more <systemitem class="osname">System V</> shared
-        memory or semaphores than your operating system's default configuration
-        allows. See <xref linkend="sysvipc"> for information on how to
-        adjust those parameters, if necessary.
-<!## end>
-<!## XL>
-        Increasing this parameter might cause <filename>Coordinator</> or <filename>Datanode</>
-        to request more <systemitem class="osname">System V</> shared
-        memory or semaphores than your operating system's default configuration
-        allows. See <xref linkend="sysvipc"> for information on how to
-        adjust those parameters, if necessary.
-<!## end>
-       </para>
-
-       <para>
-        When running a standby server, you must set this parameter to the
-        same or higher value than on the master server. Otherwise, queries
-        will not be allowed in the standby server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-superuser-reserved-connections"
-     xreflabel="superuser_reserved_connections">
-      <term><varname>superuser_reserved_connections</varname>
-      (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>superuser_reserved_connections</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-<!## PG>
-        Determines the number of connection <quote>slots</quote> that
-        are reserved for connections by <productname>PostgreSQL</>
-        superusers.  At most <xref linkend="guc-max-connections">
-        connections can ever be active simultaneously.  Whenever the
-        number of active concurrent connections is at least
-        <varname>max_connections</> minus
-        <varname>superuser_reserved_connections</varname>, new
-        connections will be accepted only for superusers, and no
-        new replication connections will be accepted.
-<!## end>
-<!## XC>
-        Determines the number of connection <quote>slots</quote> that
-        are reserved for connections by <filename>Coordinator</> or <filename>Datanode</>
-        superusers.  At most <xref linkend="guc-max-connections">
-        connections can ever be active simultaneously.  Whenever the
-        number of active concurrent connections is at least
-        <varname>max_connections</> minus
-        <varname>superuser_reserved_connections</varname>, new
-        connections will be accepted only for superusers, and no
-        new replication connections will be accepted.
-<!## end>
-<!## XL>
-        Determines the number of connection <quote>slots</quote> that
-        are reserved for connections by <filename>Coordinator</> or <filename>Datanode</>
-        superusers.  At most <xref linkend="guc-max-connections">
-        connections can ever be active simultaneously.  Whenever the
-        number of active concurrent connections is at least
-        <varname>max_connections</> minus
-        <varname>superuser_reserved_connections</varname>, new
-        connections will be accepted only for superusers, and no
-        new replication connections will be accepted.
-<!## end>
-       </para>
-
-       <para>
-        The default value is three connections. The value must be less
-        than the value of <varname>max_connections</varname>. This
-        parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-unix-socket-directory" xreflabel="unix_socket_directory">
-      <term><varname>unix_socket_directory</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>unix_socket_directory</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the directory of the Unix-domain socket on which the
-        server is to listen for
-        connections from client applications.  The default is normally
-        <filename>/tmp</filename>, but can be changed at build time.
-        This parameter can only be set at server start.
-       </para>
-
-       <para>
-        In addition to the socket file itself, which is named
-        <literal>.s.PGSQL.<replaceable>nnnn</></literal> where
-        <replaceable>nnnn</> is the server's port number, an ordinary file
-        named <literal>.s.PGSQL.<replaceable>nnnn</>.lock</literal> will be
-        created in the <varname>unix_socket_directory</> directory.  Neither
-        file should ever be removed manually.
-       </para>
-
-       <para>
-        This parameter is irrelevant on Windows, which does not have
-        Unix-domain sockets.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-unix-socket-group" xreflabel="unix_socket_group">
-      <term><varname>unix_socket_group</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>unix_socket_group</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the owning group of the Unix-domain socket.  (The owning
-        user of the socket is always the user that starts the
-        server.)  In combination with the parameter
-        <varname>unix_socket_permissions</varname> this can be used as
-        an additional access control mechanism for Unix-domain connections.
-        By default this is the empty string, which uses the default
-        group of the server user.  This parameter can only be set at
-        server start.
-       </para>
-
-       <para>
-        This parameter is irrelevant on Windows, which does not have
-        Unix-domain sockets.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-unix-socket-permissions" xreflabel="unix_socket_permissions">
-      <term><varname>unix_socket_permissions</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>unix_socket_permissions</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the access permissions of the Unix-domain socket.  Unix-domain
-        sockets use the usual Unix file system permission set.
-        The parameter value is expected to be a numeric mode
-        specified in the format accepted by the
-        <function>chmod</function> and <function>umask</function>
-        system calls.  (To use the customary octal format the number
-        must start with a <literal>0</literal> (zero).)
-       </para>
-
-       <para>
-        The default permissions are <literal>0777</literal>, meaning
-        anyone can connect. Reasonable alternatives are
-        <literal>0770</literal> (only user and group, see also
-        <varname>unix_socket_group</varname>) and <literal>0700</literal>
-        (only user). (Note that for a Unix-domain socket, only write
-        permission matters, so there is no point in setting or revoking
-        read or execute permissions.)
-       </para>
-
-       <para>
-        This access control mechanism is independent of the one
-        described in <xref linkend="client-authentication">.
-       </para>
-
-       <para>
-        This parameter can only be set at server start.
-       </para>
-
-       <para>
-        This parameter is irrelevant on Windows, which does not have
-        Unix-domain sockets.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-bonjour" xreflabel="bonjour">
-      <term><varname>bonjour</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>bonjour</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables advertising the server's existence via
-        <productname>Bonjour</productname>.  The default is off.
-        This parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-bonjour-name" xreflabel="bonjour_name">
-      <term><varname>bonjour_name</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>bonjour_name</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the <productname>Bonjour</productname> service
-        name.  The computer name is used if this parameter is set to the
-        empty string <literal>''</> (which is the default).  This parameter is
-        ignored if the server was not compiled with
-        <productname>Bonjour</productname> support.
-        This parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-tcp-keepalives-idle" xreflabel="tcp_keepalives_idle">
-      <term><varname>tcp_keepalives_idle</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>tcp_keepalives_idle</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the number of seconds before sending a keepalive packet on
-        an otherwise idle connection.  A value of 0 uses the system default.
-        This parameter is supported only on systems that support the
-        <symbol>TCP_KEEPIDLE</> or <symbol>TCP_KEEPALIVE</> symbols, and on
-        Windows; on other systems, it must be zero. This parameter is ignored
-        for connections made via a Unix-domain socket.
-       </para>
-       <note>
-        <para>
-         On Windows, a value of 0 will set this parameter to 2 hours,
-         since Windows does not provide a way to read the system default value.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-tcp-keepalives-interval" xreflabel="tcp_keepalives_interval">
-      <term><varname>tcp_keepalives_interval</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>tcp_keepalives_interval</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the number of seconds between sending keepalives on an
-        otherwise idle connection.  A value of 0 uses the system default.
-        This parameter is supported only on systems that support the
-        <symbol>TCP_KEEPINTVL</> symbol, and on Windows; on other systems, it
-        must be zero. This parameter is ignored for connections made via a
-        Unix-domain socket.
-       </para>
-       <note>
-        <para>
-         On Windows, a value of 0 will set this parameter to 1 second,
-         since Windows does not provide a way to read the system default value.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-tcp-keepalives-count" xreflabel="tcp_keepalives_count">
-      <term><varname>tcp_keepalives_count</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>tcp_keepalives_count</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the number of keepalive packets to send on an otherwise idle
-        connection.  A value of 0 uses the system default.  This parameter is
-        supported only on systems that support the <symbol>TCP_KEEPCNT</>
-        symbol; on other systems, it must be zero. This parameter is ignored
-        for connections made via a Unix-domain socket.
-       </para>
-       <note>
-        <para>
-         This parameter is not supported on Windows, and must be zero.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-     </sect2>
-     <sect2 id="runtime-config-connection-security">
-     <title>Security and Authentication</title>
-&common;
-     <variablelist>
-     <varlistentry id="guc-authentication-timeout" xreflabel="authentication_timeout">
-      <term><varname>authentication_timeout</varname> (<type>integer</type>)</term>
-      <indexterm><primary>timeout</><secondary>client authentication</></indexterm>
-      <indexterm><primary>client authentication</><secondary>timeout during</></indexterm>
-      <indexterm>
-       <primary><varname>authentication_timeout</> configuration parameter</primary>
-      </indexterm>
-
-      <listitem>
-       <para>
-        Maximum time to complete client authentication, in seconds. If a
-        would-be client has not completed the authentication protocol in
-        this much time, the server closes the connection. This prevents
-        hung clients from occupying a connection indefinitely.
-        The default is one minute (<literal>1m</>).
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-ssl" xreflabel="ssl">
-      <term><varname>ssl</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>ssl</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables <acronym>SSL</> connections. Please read
-        <xref linkend="ssl-tcp"> before using this. The default
-        is <literal>off</>. This parameter can only be set at server
-        start.  <acronym>SSL</> communication is only possible with
-        TCP/IP connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-ssl-renegotiation-limit" xreflabel="ssl_renegotiation_limit">
-      <term><varname>ssl_renegotiation_limit</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>ssl_renegotiation_limit</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies how much data can flow over an <acronym>SSL</>-encrypted
-        connection before renegotiation of the session keys will take
-        place. Renegotiation decreases an attacker's chances of doing
-        cryptanalysis when large amounts of traffic can be examined, but it
-        also carries a large performance penalty. The sum of sent and received
-        traffic is used to check the limit. If this parameter is set to 0,
-        renegotiation is disabled. The default is <literal>512MB</>.
-       </para>
-       <note>
-        <para>
-         SSL libraries from before November 2009 are insecure when using SSL
-         renegotiation, due to a vulnerability in the SSL protocol. As a
-         stop-gap fix for this vulnerability, some vendors shipped SSL
-         libraries incapable of doing renegotiation. If any such libraries
-         are in use on the client or server, SSL renegotiation should be
-         disabled.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-ssl-ciphers" xreflabel="ssl_ciphers">
-      <term><varname>ssl_ciphers</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>ssl_ciphers</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies a list of <acronym>SSL</> ciphers that are allowed to be
-        used on secure connections. See the <application>openssl</>
-        manual page for a list of supported ciphers.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-password-encryption" xreflabel="password_encryption">
-      <term><varname>password_encryption</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>password_encryption</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When a password is specified in <xref
-        linkend="sql-createuser"> or
-        <xref linkend="sql-alterrole">
-        without writing either <literal>ENCRYPTED</> or
-        <literal>UNENCRYPTED</>, this parameter determines whether the
-        password is to be encrypted. The default is <literal>on</>
-        (encrypt the password).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-krb-server-keyfile" xreflabel="krb_server_keyfile">
-      <term><varname>krb_server_keyfile</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>krb_server_keyfile</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the location of the Kerberos server key file. See
-        <xref linkend="kerberos-auth"> or <xref linkend="gssapi-auth">
-        for details. This parameter can only be set in the
-        <filename>postgresql.conf</> file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-krb-srvname" xreflabel="krb_srvname">
-      <term><varname>krb_srvname</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>krb_srvname</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the Kerberos service name. See <xref linkend="kerberos-auth">
-        for details. This parameter can only be set in the
-        <filename>postgresql.conf</> file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-krb-caseins-users" xreflabel="krb_caseins_users">
-      <term><varname>krb_caseins_users</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>krb_caseins_users</varname> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets whether Kerberos and GSSAPI user names should be treated
-        case-insensitively.
-        The default is <literal>off</> (case sensitive). This parameter can only be
-        set in the <filename>postgresql.conf</> file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-db-user-namespace" xreflabel="db_user_namespace">
-      <term><varname>db_user_namespace</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>db_user_namespace</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This parameter enables per-database user names.  It is off by default.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-
-       <para>
-        If this is on, you should create users as <literal>username@dbname</>.
-        When <literal>username</> is passed by a connecting client,
-        <literal>@</> and the database name are appended to the user
-        name and that database-specific user name is looked up by the
-        server. Note that when you create users with names containing
-        <literal>@</> within the SQL environment, you will need to
-        quote the user name.
-       </para>
-
-       <para>
-        With this parameter enabled, you can still create ordinary global
-        users.  Simply append <literal>@</> when specifying the user
-        name in the client, e.g. <literal>joe@</>.  The <literal>@</>
-        will be stripped off before the user name is looked up by the
-        server.
-       </para>
-
-       <para>
-        <varname>db_user_namespace</> causes the client's and
-        server's user name representation to differ.
-        Authentication checks are always done with the server's user name
-        so authentication methods must be configured for the
-        server's user name, not the client's.  Because
-        <literal>md5</> uses the user name as salt on both the
-        client and server, <literal>md5</> cannot be used with
-        <varname>db_user_namespace</>.
-       </para>
-
-       <note>
-        <para>
-         This feature is intended as a temporary measure until a
-         complete solution is found.  At that time, this option will
-         be removed.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-    </sect2>
-   </sect1>
-
-   <sect1 id="runtime-config-resource">
-    <title>Resource Consumption</title>
-
-    <sect2 id="runtime-config-resource-memory">
-     <title>Memory</title>
-&common;
-     <variablelist>
-     <varlistentry id="guc-shared-buffers" xreflabel="shared_buffers">
-      <term><varname>shared_buffers</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>shared_buffers</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the amount of memory the database server uses for shared
-        memory buffers.  The default is typically 32 megabytes
-        (<literal>32MB</>), but might be less if your kernel settings will
-        not support it (as determined during <application>initdb</>).
-        This setting must be at least 128 kilobytes.  (Non-default
-        values of <symbol>BLCKSZ</symbol> change the minimum.)  However,
-        settings significantly higher than the minimum are usually needed
-        for good performance.  This parameter can only be set at server start.
-       </para>
-
-       <para>
-        If you have a dedicated database server with 1GB or more of RAM, a
-        reasonable starting value for <varname>shared_buffers</varname> is 25%
-        of the memory in your system.  There are some workloads where even
-        large settings for <varname>shared_buffers</varname> are effective, but
-<!## PG>
-        because <productname>PostgreSQL</productname> also relies on the
-<!## end>
-<!## XC>
-        because <productname>Postgres-XC</productname> also relies on the
-<!## end>
-<!## XL>
-        because <productname>Postgres-XL</productname> also relies on the
-<!## end>
-        operating system cache, it is unlikely that an allocation of more than
-        40% of RAM to <varname>shared_buffers</varname> will work better than a
-        smaller amount.  Larger settings for <varname>shared_buffers</varname>
-        usually require a corresponding increase in
-        <varname>checkpoint_segments</varname>, in order to spread out the
-        process of writing large quantities of new or changed data over a
-        longer period of time.
-       </para>
-
-       <para>
-        On systems with less than 1GB of RAM, a smaller percentage of RAM is
-        appropriate, so as to leave adequate space for the operating system.
-        Also, on Windows, large values for <varname>shared_buffers</varname>
-        aren't as effective.  You may find better results keeping the setting
-        relatively low and using the operating system cache more instead.  The
-        useful range for <varname>shared_buffers</varname> on Windows systems
-        is generally from 64MB to 512MB.
-       </para>
-
-       <para>
-<!## PG>
-        Increasing this parameter might cause <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-        Increasing this parameter might cause <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-        Increasing this parameter might cause <productname>Postgres-XL</>
-<!## end>
-        to request more <systemitem class="osname">System V</> shared
-        memory than your operating system's default configuration
-        allows. See <xref linkend="sysvipc"> for information on how to
-        adjust those parameters, if necessary.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-temp-buffers" xreflabel="temp_buffers">
-      <term><varname>temp_buffers</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>temp_buffers</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the maximum number of temporary buffers used by each database
-        session.  These are session-local buffers used only for access to
-        temporary tables.  The default is eight megabytes
-        (<literal>8MB</>).  The setting can be changed within individual
-        sessions, but only before the first use of temporary tables
-        within the session; subsequent attempts to change the value will
-        have no effect on that session.
-       </para>
-
-       <para>
-        A session will allocate temporary buffers as needed up to the limit
-        given by <varname>temp_buffers</>.  The cost of setting a large
-        value in sessions that do not actually need many temporary
-        buffers is only a buffer descriptor, or about 64 bytes, per
-        increment in <varname>temp_buffers</>.  However if a buffer is
-        actually used an additional 8192 bytes will be consumed for it
-        (or in general, <symbol>BLCKSZ</symbol> bytes).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-prepared-transactions" xreflabel="max_prepared_transactions">
-      <term><varname>max_prepared_transactions</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_prepared_transactions</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the maximum number of transactions that can be in the
-        <quote>prepared</> state simultaneously (see <xref
-        linkend="sql-prepare-transaction">).
-        Setting this parameter to zero (which is the default)
-        disables the prepared-transaction feature.
-        This parameter can only be set at server start.
-       </para>
-
-       <para>
-        If you are not planning to use prepared transactions, this parameter
-        should be set to zero to prevent accidental creation of prepared
-        transactions.  If you are using prepared transactions, you will
-        probably want <varname>max_prepared_transactions</varname> to be at
-        least as large as <xref linkend="guc-max-connections">, so that every
-        session can have a prepared transaction pending.
-       </para>
-
-       <para>
-<!## PG>
-        Increasing this parameter might cause <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-        Increasing this parameter might cause <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-        Increasing this parameter might cause <productname>Postgres-XL</>
-<!## end>
-        to request more <systemitem class="osname">System V</> shared
-        memory than your operating system's default configuration
-        allows. See <xref linkend="sysvipc"> for information on how to
-        adjust those parameters, if necessary.
-       </para>
-
-       <para>
-        When running a standby server, you must set this parameter to the
-        same or higher value than on the master server. Otherwise, queries
-        will not be allowed in the standby server.
-       </para>
-
-<!## XC>
-       <para>
-        Even though your application does not issue <command>PREPARE
-        TRANSACTION</> explicitly, Coordinator may generate this
-        command when an updating transaction involves more than one
-        Coordinators and Datanodes. For Datanodes, you should specify
-        this value as the same value as <varname>max_connections</>.
-       </para>
-<!## end>
-<!## XL>
-       <para>
-        Even though your application does not issue <command>PREPARE
-        TRANSACTION</> explicitly, Coordinator may generate this
-        command when an updating transaction involves more than one
-        Coordinators and Datanodes. For Datanodes, you should specify
-        this value as the same value as <varname>max_connections</>.
-       </para>
-<!## end>
-
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-work-mem" xreflabel="work_mem">
-      <term><varname>work_mem</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>work_mem</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the amount of memory to be used by internal sort operations
-        and hash tables before writing to temporary disk files. The value
-        defaults to one megabyte (<literal>1MB</>).
-        Note that for a complex query, several sort or hash operations might be
-        running in parallel; each operation will be allowed to use as much memory
-        as this value specifies before it starts to write data into temporary
-        files. Also, several running sessions could be doing such operations
-        concurrently.  Therefore, the total memory used could be many
-        times the value of <varname>work_mem</varname>; it is necessary to
-        keep this fact in mind when choosing the value. Sort operations are
-        used for <literal>ORDER BY</>, <literal>DISTINCT</>, and
-        merge joins.
-        Hash tables are used in hash joins, hash-based aggregation, and
-        hash-based processing of <literal>IN</> subqueries.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-maintenance-work-mem" xreflabel="maintenance_work_mem">
-      <term><varname>maintenance_work_mem</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>maintenance_work_mem</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the maximum amount of memory to be used by maintenance
-        operations, such as <command>VACUUM</command>, <command>CREATE
-        INDEX</>, and <command>ALTER TABLE ADD FOREIGN KEY</>.  It defaults
-        to 16 megabytes (<literal>16MB</>).  Since only one of these
-        operations can be executed at a time by a database session, and
-        an installation normally doesn't have many of them running
-        concurrently, it's safe to set this value significantly larger
-        than <varname>work_mem</varname>.  Larger settings might improve
-        performance for vacuuming and for restoring database dumps.
-       </para>
-       <para>
-        Note that when autovacuum runs, up to
-        <xref linkend="guc-autovacuum-max-workers"> times this memory may be
-        allocated, so be careful not to set the default value too high.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-stack-depth" xreflabel="max_stack_depth">
-      <term><varname>max_stack_depth</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_stack_depth</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the maximum safe depth of the server's execution stack.
-        The ideal setting for this parameter is the actual stack size limit
-        enforced by the kernel (as set by <literal>ulimit -s</> or local
-        equivalent), less a safety margin of a megabyte or so.  The safety
-        margin is needed because the stack depth is not checked in every
-        routine in the server, but only in key potentially-recursive routines
-        such as expression evaluation.  The default setting is two
-        megabytes (<literal>2MB</>), which is conservatively small and
-        unlikely to risk crashes.  However, it might be too small to allow
-        execution of complex functions.  Only superusers can change this
-        setting.
-       </para>
-
-       <para>
-        Setting <varname>max_stack_depth</> higher than
-        the actual kernel limit will mean that a runaway recursive function
-        can crash an individual backend process.  On platforms where
-<!## PG>
-        <productname>PostgreSQL</productname> can determine the kernel limit,
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> can determine the kernel limit,
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> can determine the kernel limit,
-<!## end>
-        the server will not allow this variable to be set to an unsafe
-        value.  However, not all platforms provide the information,
-        so caution is recommended in selecting a value.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-     </sect2>
-
-     <sect2 id="runtime-config-resource-kernel">
-     <title>Kernel Resource Usage</title>
-     <variablelist>
-&common;
-     <varlistentry id="guc-max-files-per-process" xreflabel="max_files_per_process">
-      <term><varname>max_files_per_process</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_files_per_process</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the maximum number of simultaneously open files allowed to each
-        server subprocess. The default is one thousand files. If the kernel is enforcing
-        a safe per-process limit, you don't need to worry about this setting.
-        But on some platforms (notably, most BSD systems), the kernel will
-        allow individual processes to open many more files than the system
-        can actually support if many processes all try to open
-        that many files. If you find yourself seeing <quote>Too many open
-        files</> failures, try reducing this setting.
-        This parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-shared-preload-libraries" xreflabel="shared_preload_libraries">
-      <term><varname>shared_preload_libraries</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>shared_preload_libraries</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This variable specifies one or more shared libraries
-        to be preloaded at server start. For example,
-        <literal>'$libdir/mylib'</literal> would cause
-        <literal>mylib.so</> (or on some platforms,
-        <literal>mylib.sl</>) to be preloaded from the installation's
-        standard library directory.
-        All library names are converted to lower case unless double-quoted.
-        If more than one library is to be loaded, separate their names
-        with commas.  This parameter can only be set at server start.
-       </para>
-
-       <para>
-<!## PG>
-        <productname>PostgreSQL</productname> procedural language
-        libraries can be preloaded in this way, typically by using the
-        syntax <literal>'$libdir/plXXX'</literal> where
-        <literal>XXX</literal> is <literal>pgsql</>, <literal>perl</>,
-        <literal>tcl</>, or <literal>python</>.
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> procedural language
-        libraries can be preloaded in this way, typically by using the
-        syntax <literal>'$libdir/plXXX'</literal> where
-        <literal>XXX</literal> is <literal>pgsql</>, <literal>perl</>,
-        <literal>tcl</>, or <literal>python</>.
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> procedural language
-        libraries can be preloaded in this way, typically by using the
-        syntax <literal>'$libdir/plXXX'</literal> where
-        <literal>XXX</literal> is <literal>pgsql</>, <literal>perl</>,
-        <literal>tcl</>, or <literal>python</>.
-<!## end>
-       </para>
-
-       <para>
-        By preloading a shared library, the library startup time is avoided
-        when the library is first used.  However, the time to start each new
-        server process might increase slightly, even if that process never
-        uses the library.  So this parameter is recommended only for
-        libraries that will be used in most sessions.
-       </para>
-
-<!## PG>
-<!-- No Window Support yet! -->
-     <note>
-      <para>
-        On Windows hosts, preloading a library at server start will not reduce
-        the time required to start each new server process; each server process
-        will re-load all preload libraries.  However, <varname>shared_preload_libraries
-        </varname> is still useful on Windows hosts because some shared libraries may
-        need to perform certain operations that only take place at postmaster start
-        (for example, a shared library may need to reserve lightweight locks
-        or shared memory and you can't do that after the postmaster has started).
-       </para>
-      </note>
-<!## end>
-       <para>
-        If a specified library is not found,
-        the server will fail to start.
-       </para>
-
-       <para>
-<!## PG>
-        Every  PostgreSQL-supported library has a <quote>magic
-        block</> that is checked to guarantee compatibility.
-        For this reason, non-PostgreSQL libraries cannot be
-        loaded in this way.
-<!## end>
-<!## XC>
-        Every  Postgres-XC-supported library has a <quote>magic
-        block</> that is checked to guarantee compatibility.  
-        For this reason, non-Postgres-XC libraries cannot be 
-        loaded in this way.
-<!## end>
-<!## XL>
-        Every  Postgres-XL-supported library has a <quote>magic
-        block</> that is checked to guarantee compatibility.  
-        For this reason, non-Postgres-XL libraries cannot be 
-        loaded in this way.
-<!## end>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-
-    <sect2 id="runtime-config-resource-vacuum-cost">
-     <title>Cost-based Vacuum Delay</title>
-
-&common;
-     <para>
-      During the execution of <xref linkend="sql-vacuum">
-      and <xref linkend="sql-analyze">
-      commands, the system maintains an
-      internal counter that keeps track of the estimated cost of the
-      various I/O operations that are performed.  When the accumulated
-      cost reaches a limit (specified by
-      <varname>vacuum_cost_limit</varname>), the process performing
-      the operation will sleep for a short period of time, as specified by
-      <varname>vacuum_cost_delay</varname>. Then it will reset the
-      counter and continue execution.
-     </para>
-
-     <para>
-      The intent of this feature is to allow administrators to reduce
-      the I/O impact of these commands on concurrent database
-      activity. There are many situations where it is not
-      important that maintenance commands like
-      <command>VACUUM</command> and <command>ANALYZE</command> finish
-      quickly; however, it is usually very important that these
-      commands do not significantly interfere with the ability of the
-      system to perform other database operations. Cost-based vacuum
-      delay provides a way for administrators to achieve this.
-     </para>
-
-     <para>
-      This feature is disabled by default for manually issued
-      <command>VACUUM</command> commands. To enable it, set the
-      <varname>vacuum_cost_delay</varname> variable to a nonzero
-      value.
-     </para>
-
-     <variablelist>
-      <varlistentry id="guc-vacuum-cost-delay" xreflabel="vacuum_cost_delay">
-       <term><varname>vacuum_cost_delay</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>vacuum_cost_delay</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-        <para>
-         The length of time, in milliseconds, that the process will sleep
-         when the cost limit has been exceeded.
-         The default value is zero, which disables the cost-based vacuum
-         delay feature.  Positive values enable cost-based vacuuming.
-         Note that on many systems, the effective resolution
-         of sleep delays is 10 milliseconds; setting
-         <varname>vacuum_cost_delay</varname> to a value that is
-         not a multiple of 10 might have the same results as setting it
-         to the next higher multiple of 10.
-        </para>
-
-        <para>
-         When using cost-based vacuuming, appropriate values for
-         <varname>vacuum_cost_delay</> are usually quite small, perhaps
-         10 or 20 milliseconds.  Adjusting vacuum's resource consumption
-         is best done by changing the other vacuum cost parameters.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry id="guc-vacuum-cost-page-hit" xreflabel="vacuum_cost_page_hit">
-       <term><varname>vacuum_cost_page_hit</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>vacuum_cost_page_hit</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-        <para>
-         The estimated cost for vacuuming a buffer found in the shared buffer
-         cache. It represents the cost to lock the buffer pool, lookup
-         the shared hash table and scan the content of the page. The
-         default value is one.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry id="guc-vacuum-cost-page-miss" xreflabel="vacuum_cost_page_miss">
-       <term><varname>vacuum_cost_page_miss</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>vacuum_cost_page_miss</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-        <para>
-         The estimated cost for vacuuming a buffer that has to be read from
-         disk.  This represents the effort to lock the buffer pool,
-         lookup the shared hash table, read the desired block in from
-         the disk and scan its content. The default value is 10.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry id="guc-vacuum-cost-page-dirty" xreflabel="vacuum_cost_page_dirty">
-       <term><varname>vacuum_cost_page_dirty</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>vacuum_cost_page_dirty</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-        <para>
-         The estimated cost charged when vacuum modifies a block that was
-         previously clean. It represents the extra I/O required to
-         flush the dirty block out to disk again. The default value is
-         20.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry id="guc-vacuum-cost-limit" xreflabel="vacuum_cost_limit">
-       <term><varname>vacuum_cost_limit</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>vacuum_cost_limit</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-        <para>
-         The accumulated cost that will cause the vacuuming process to sleep.
-         The default value is 200.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-
-     <note>
-      <para>
-       There are certain operations that hold critical locks and should
-       therefore complete as quickly as possible.  Cost-based vacuum
-       delays do not occur during such operations.  Therefore it is
-       possible that the cost accumulates far higher than the specified
-       limit.  To avoid uselessly long delays in such cases, the actual
-       delay is calculated as <varname>vacuum_cost_delay</varname> *
-       <varname>accumulated_balance</varname> /
-       <varname>vacuum_cost_limit</varname> with a maximum of
-       <varname>vacuum_cost_delay</varname> * 4.
-      </para>
-     </note>
-    </sect2>
-
-    <sect2 id="runtime-config-resource-background-writer">
-     <title>Background Writer</title>
-&common;
-     <para>
-      There is a separate server
-      process called the <firstterm>background writer</>, whose function
-      is to issue writes of <quote>dirty</> (new or modified) shared
-      buffers.  It writes shared buffers so server processes handling
-      user queries seldom or never need to wait for a write to occur.
-      However, the background writer does cause a net overall
-      increase in I/O load, because while a repeatedly-dirtied page might
-      otherwise be written only once per checkpoint interval, the
-      background writer might write it several times as it is dirtied
-      in the same interval.  The parameters discussed in this subsection
-      can be used to tune the behavior for local needs.
-     </para>
-
-     <variablelist>
-      <varlistentry id="guc-bgwriter-delay" xreflabel="bgwriter_delay">
-       <term><varname>bgwriter_delay</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>bgwriter_delay</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-        <para>
-         Specifies the delay between activity rounds for the
-         background writer.  In each round the writer issues writes
-         for some number of dirty buffers (controllable by the
-         following parameters).  It then sleeps for <varname>bgwriter_delay</>
-         milliseconds, and repeats.  The default value is 200 milliseconds
-         (<literal>200ms</>). Note that on many systems, the effective
-         resolution of sleep delays is 10 milliseconds; setting
-         <varname>bgwriter_delay</> to a value that is not a multiple of
-         10 might have the same results as setting it to the next higher
-         multiple of 10.  This parameter can only be set in the
-         <filename>postgresql.conf</> file or on the server command line.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry id="guc-bgwriter-lru-maxpages" xreflabel="bgwriter_lru_maxpages">
-       <term><varname>bgwriter_lru_maxpages</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>bgwriter_lru_maxpages</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-        <para>
-         In each round, no more than this many buffers will be written
-         by the background writer.  Setting this to zero disables
-         background writing (except for checkpoint activity).
-         The default value is 100 buffers.
-         This parameter can only be set in the <filename>postgresql.conf</>
-         file or on the server command line.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry id="guc-bgwriter-lru-multiplier" xreflabel="bgwriter_lru_multiplier">
-       <term><varname>bgwriter_lru_multiplier</varname> (<type>floating point</type>)</term>
-       <indexterm>
-        <primary><varname>bgwriter_lru_multiplier</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-        <para>
-         The number of dirty buffers written in each round is based on the
-         number of new buffers that have been needed by server processes
-         during recent rounds.  The average recent need is multiplied by
-         <varname>bgwriter_lru_multiplier</> to arrive at an estimate of the
-         number of buffers that will be needed during the next round.  Dirty
-         buffers are written until there are that many clean, reusable buffers
-         available.  (However, no more than <varname>bgwriter_lru_maxpages</>
-         buffers will be written per round.)
-         Thus, a setting of 1.0 represents a <quote>just in time</> policy
-         of writing exactly the number of buffers predicted to be needed.
-         Larger values provide some cushion against spikes in demand,
-         while smaller values intentionally leave writes to be done by
-         server processes.
-         The default is 2.0.
-         This parameter can only be set in the <filename>postgresql.conf</>
-         file or on the server command line.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-
-     <para>
-      Smaller values of <varname>bgwriter_lru_maxpages</varname> and
-      <varname>bgwriter_lru_multiplier</varname> reduce the extra I/O load
-      caused by the background writer, but make it more likely that server
-      processes will have to issue writes for themselves, delaying interactive
-      queries.
-     </para>
-    </sect2>
-
-    <sect2 id="runtime-config-resource-async-behavior">
-     <title>Asynchronous Behavior</title>
-&common;
-     <variablelist>
-      <varlistentry id="guc-effective-io-concurrency" xreflabel="effective_io_concurrency">
-       <term><varname>effective_io_concurrency</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>effective_io_concurrency</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-        <para>
-         Sets the number of concurrent disk I/O operations that
-         <productname>PostgreSQL</> expects can be executed
-         simultaneously.  Raising this value will increase the number of I/O
-         operations that any individual <productname>PostgreSQL</> session
-         attempts to initiate in parallel.  The allowed range is 1 to 1000,
-         or zero to disable issuance of asynchronous I/O requests. Currently,
-         this setting only affects bitmap heap scans.
-        </para>
-
-        <para>
-         A good starting point for this setting is the number of separate
-         drives comprising a RAID 0 stripe or RAID 1 mirror being used for the
-         database.  (For RAID 5 the parity drive should not be counted.)
-         However, if the database is often busy with multiple queries issued in
-         concurrent sessions, lower values may be sufficient to keep the disk
-         array busy.  A value higher than needed to keep the disks busy will
-         only result in extra CPU overhead.
-        </para>
-
-        <para>
-         For more exotic systems, such as memory-based storage or a RAID array
-         that is limited by bus bandwidth, the correct value might be the
-         number of I/O paths available.  Some experimentation may be needed
-         to find the best value.
-        </para>
-
-        <para>
-         Asynchronous I/O depends on an effective <function>posix_fadvise</>
-         function, which some operating systems lack.  If the function is not
-         present then setting this parameter to anything but zero will result
-         in an error.  On some operating systems (e.g., Solaris), the function
-         is present but does not actually do anything.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </sect2>
-   </sect1>
-
-   <sect1 id="runtime-config-wal">
-    <title>Write Ahead Log</title>
-&common;
-   <para>
-    See also <xref linkend="wal-configuration"> for details on WAL
-    and checkpoint tuning.
-   </para>
-
-    <sect2 id="runtime-config-wal-settings">
-     <title>Settings</title>
-     <variablelist>
-&common;
-     <varlistentry id="guc-wal-level" xreflabel="wal_level">
-      <term><varname>wal_level</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>wal_level</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        <varname>wal_level</> determines how much information is written
-        to the WAL. The default value is <literal>minimal</>, which writes
-        only the information needed to recover from a crash or immediate
-        shutdown. <literal>archive</> adds logging required for WAL archiving,
-        and <literal>hot_standby</> further adds information required to run
-        read-only queries on a standby server.
-        This parameter can only be set at server start.
-       </para>
-       <para>
-        In <literal>minimal</> level, WAL-logging of some bulk operations, like
-        <command>CREATE INDEX</>, <command>CLUSTER</> and <command>COPY</> on
-        a table that was created or truncated in the same transaction can be
-        safely skipped, which can make those operations much faster (see
-        <xref linkend="populate-pitr">). But minimal WAL does not contain
-        enough information to reconstruct the data from a base backup and the
-        WAL logs, so either <literal>archive</> or <literal>hot_standby</>
-        level must be used to enable
-        WAL archiving (<xref linkend="guc-archive-mode">) and streaming
-        replication.
-       </para>
-<!## PG>
-       <para>
-        In <literal>hot_standby</> level, the same information is logged as
-        with <literal>archive</>, plus information needed to reconstruct
-        the status of running transactions from the WAL. To enable read-only
-        queries on a standby server, <varname>wal_level</> must be set to
-        <literal>hot_standby</> on the primary, and
-        <xref linkend="guc-hot-standby"> must be enabled in the standby. It is
-        thought that there is
-        little measurable difference in performance between using
-        <literal>hot_standby</> and <literal>archive</> levels, so feedback
-        is welcome if any production impacts are noticeable.
-       </para>
-<!## end>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-fsync" xreflabel="fsync">
-      <indexterm>
-       <primary><varname>fsync</> configuration parameter</primary>
-      </indexterm>
-      <term><varname>fsync</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-<!## PG>
-        If this parameter is on, the <productname>PostgreSQL</> server
-<!## end>
-<!## XC>
-        If this parameter is on, the <productname>Postgres-XC</> server
-<!## end>
-<!## XL>
-        If this parameter is on, the <productname>Postgres-XL</> server
-<!## end>
-        will try to make sure that updates are physically written to
-        disk, by issuing <function>fsync()</> system calls or various
-        equivalent methods (see <xref linkend="guc-wal-sync-method">).
-        This ensures that the database cluster can recover to a
-        consistent state after an operating system or hardware crash.
-       </para>
-
-       <para>
-        While turning off <varname>fsync</varname> is often a performance
-        benefit, this can result in unrecoverable data corruption in
-        the event of a power failure or system crash.  Thus it
-        is only advisable to turn off <varname>fsync</varname> if
-        you can easily recreate your entire database from external
-        data.
-       </para>
-
-       <para>
-        Examples of safe circumstances for turning off
-        <varname>fsync</varname> include the initial loading of a new
-        database cluster from a backup file, using a database cluster
-        for processing a batch of data after which the database
-        will be thrown away and recreated,
-        or for a read-only database clone which
-        gets recreated frequently and is not used for failover.  High
-        quality hardware alone is not a sufficient justification for
-        turning off <varname>fsync</varname>.
-       </para>
-
-       <para>
-        In many situations, turning off <xref linkend="guc-synchronous-commit">
-        for noncritical transactions can provide much of the potential
-        performance benefit of turning off <varname>fsync</varname>, without
-        the attendant risks of data corruption.
-       </para>
-
-       <para>
-        <varname>fsync</varname> can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-        If you turn this parameter off, also consider turning off
-        <xref linkend="guc-full-page-writes">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-synchronous-commit" xreflabel="synchronous_commit">
-      <term><varname>synchronous_commit</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>synchronous_commit</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies whether transaction commit will wait for WAL records
-        to be written to disk before the command returns a <quote>success</>
-        indication to the client.  Valid values are <literal>on</>,
-        <literal>local</>, and <literal>off</>.  The default, and safe, value
-        is <literal>on</>.  When <literal>off</>, there can be a delay between
-        when success is reported to the client and when the transaction is
-        really guaranteed to be safe against a server crash.  (The maximum
-        delay is three times <xref linkend="guc-wal-writer-delay">.)  Unlike
-        <xref linkend="guc-fsync">, setting this parameter to <literal>off</>
-        does not create any risk of database inconsistency: an operating
-        system or database crash might
-        result in some recent allegedly-committed transactions being lost, but
-        the database state will be just the same as if those transactions had
-        been aborted cleanly.  So, turning <varname>synchronous_commit</> off
-        can be a useful alternative when performance is more important than
-        exact certainty about the durability of a transaction.  For more
-        discussion see <xref linkend="wal-async-commit">.
-       </para>
-       <para>
-        If <xref linkend="guc-synchronous-standby-names"> is set, this
-        parameter also controls whether or not transaction commit will wait
-        for the transaction's WAL records to be flushed to disk and replicated
-        to the standby server.  The commit wait will last until a reply from
-        the current synchronous standby indicates it has written the commit
-        record of the transaction to durable storage.  If synchronous
-        replication is in use, it will normally be sensible either to wait
-        both for WAL records to reach both the local and remote disks, or
-        to allow the transaction to commit asynchronously.  However, the
-        special value <literal>local</> is available for transactions that
-        wish to wait for local flush to disk, but not synchronous replication.
-       </para>
-       <para>
-        This parameter can be changed at any time; the behavior for any
-        one transaction is determined by the setting in effect when it
-        commits.  It is therefore possible, and useful, to have some
-        transactions commit synchronously and others asynchronously.
-        For example, to make a single multistatement transaction commit
-        asynchronously when the default is the opposite, issue <command>SET
-        LOCAL synchronous_commit TO OFF</> within the transaction.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-wal-sync-method" xreflabel="wal_sync_method">
-      <term><varname>wal_sync_method</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>wal_sync_method</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Method used for forcing WAL updates out to disk.
-        If <varname>fsync</varname> is off then this setting is irrelevant,
-        since WAL file updates will not be forced out at all.
-        Possible values are:
-       </para>
-       <itemizedlist>
-        <listitem>
-        <para>
-         <literal>open_datasync</> (write WAL files with <function>open()</> option <symbol>O_DSYNC</>)
-        </para>
-        </listitem>
-        <listitem>
-        <para>
-         <literal>fdatasync</> (call <function>fdatasync()</> at each commit)
-        </para>
-        </listitem>
-        <listitem>
-        <para>
-         <literal>fsync</> (call <function>fsync()</> at each commit)
-        </para>
-        </listitem>
-        <listitem>
-        <para>
-         <literal>fsync_writethrough</> (call <function>fsync()</> at each commit, forcing write-through of any disk write cache)
-        </para>
-        </listitem>
-        <listitem>
-        <para>
-         <literal>open_sync</> (write WAL files with <function>open()</> option <symbol>O_SYNC</>)
-        </para>
-        </listitem>
-       </itemizedlist>
-       <para>
-        The <literal>open_</>* options also use <literal>O_DIRECT</> if available.
-        Not all of these choices are available on all platforms.
-        The default is the first method in the above list that is supported
-        by the platform, except that <literal>fdatasync</> is the default on
-        Linux.  The default is not necessarily ideal; it might be
-        necessary to change this setting or other aspects of your system
-        configuration in order to create a crash-safe configuration or
-        achieve optimal performance.
-        These aspects are discussed in <xref linkend="wal-reliability">.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-full-page-writes" xreflabel="full_page_writes">
-      <indexterm>
-       <primary><varname>full_page_writes</> configuration parameter</primary>
-      </indexterm>
-      <term><varname>full_page_writes</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-<!## PG>
-        When this parameter is on, the <productname>PostgreSQL</> server
-<!## end>
-<!## XC>
-        When this parameter is on, the <productname>Postgres-XC</> server
-<!## end>
-<!## XL>
-        When this parameter is on, the <productname>Postgres-XL</> server
-<!## end>
-        writes the entire content of each disk page to WAL during the
-        first modification of that page after a checkpoint.
-        This is needed because
-        a page write that is in process during an operating system crash might
-        be only partially completed, leading to an on-disk page
-        that contains a mix of old and new data.  The row-level change data
-        normally stored in WAL will not be enough to completely restore
-        such a page during post-crash recovery.  Storing the full page image
-        guarantees that the page can be correctly restored, but at the price
-        of increasing the amount of data that must be written to WAL.
-        (Because WAL replay always starts from a checkpoint, it is sufficient
-        to do this during the first change of each page after a checkpoint.
-        Therefore, one way to reduce the cost of full-page writes is to
-        increase the checkpoint interval parameters.)
-       </para>
-
-       <para>
-        Turning this parameter off speeds normal operation, but
-        might lead to either unrecoverable data corruption, or silent
-        data corruption, after a system failure. The risks are similar to turning off
-        <varname>fsync</varname>, though smaller, and it should be turned off
-        only based on the same circumstances recommended for that parameter.
-       </para>
-
-       <para>
-        Turning off this parameter does not affect use of
-        WAL archiving for point-in-time recovery (PITR)
-        (see <xref linkend="continuous-archiving">).
-       </para>
-
-       <para>
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-        The default is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-wal-buffers" xreflabel="wal_buffers">
-      <term><varname>wal_buffers</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>wal_buffers</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        The amount of shared memory used for WAL data that has not yet been
-        written to disk.  The default setting of -1 selects a size equal to
-        1/32nd (about 3%) of <xref linkend="guc-shared-buffers">, but not less
-        than <literal>64kB</literal> nor more than the size of one WAL
-        segment, typically <literal>16MB</literal>.  This value can be set
-        manually if the automatic choice is too large or too small,
-        but any positive value less than <literal>32kB</literal> will be
-        treated as <literal>32kB</literal>.
-        This parameter can only be set at server start.
-       </para>
-
-       <para>
-        The contents of the WAL buffers are written out to disk at every
-        transaction commit, so extremely large values are unlikely to
-        provide a significant benefit.  However, setting this value to at
-        least a few megabytes can improve write performance on a busy
-        server where many clients are committing at once.  The auto-tuning
-        selected by the default setting of -1 should give reasonable
-        results in most cases.
-       </para>
-
-       <para>
-<!## PG>
-        Increasing this parameter might cause <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-        Increasing this parameter might cause <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-        Increasing this parameter might cause <productname>Postgres-XL</>
-<!## end>
-        to request more <systemitem class="osname">System V</> shared
-        memory than your operating system's default configuration
-        allows. See <xref linkend="sysvipc"> for information on how to
-        adjust those parameters, if necessary.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-wal-writer-delay" xreflabel="wal_writer_delay">
-      <term><varname>wal_writer_delay</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>wal_writer_delay</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the delay between activity rounds for the WAL writer.
-        In each round the writer will flush WAL to disk. It then sleeps for
-        <varname>wal_writer_delay</> milliseconds, and repeats.  The default
-        value is 200 milliseconds (<literal>200ms</>).  Note that on many
-        systems, the effective resolution of sleep delays is 10 milliseconds;
-        setting <varname>wal_writer_delay</> to a value that is not a multiple
-        of 10 might have the same results as setting it to the next higher
-        multiple of 10. This parameter can only be set in the
-        <filename>postgresql.conf</> file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-commit-delay" xreflabel="commit_delay">
-      <term><varname>commit_delay</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>commit_delay</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When the commit data for a transaction is flushed to disk, any
-        additional commits ready at that time are also flushed out.
-        <varname>commit_delay</varname> adds a time delay, set in
-        microseconds, before a transaction attempts to
-        flush the WAL buffer out to disk.  A nonzero delay can allow more
-        transactions to be committed with only one flush operation, if
-        system load is high enough that additional transactions become
-        ready to commit within the given interval. But the delay is
-        just wasted if no other transactions become ready to
-        commit. Therefore, the delay is only performed if at least
-        <varname>commit_siblings</varname> other transactions are
-        active at the instant that a server process has written its
-        commit record.
-        The default <varname>commit_delay</> is zero (no delay).
-        Since all pending commit data will be written at every flush
-        regardless of this setting, it is rare that adding delay
-        by increasing this parameter will actually improve performance.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-commit-siblings" xreflabel="commit_siblings">
-      <term><varname>commit_siblings</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>commit_siblings</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Minimum number of concurrent open transactions to require
-        before performing the <varname>commit_delay</> delay. A larger
-        value makes it more probable that at least one other
-        transaction will become ready to commit during the delay
-        interval. The default is five transactions.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-     </sect2>
-     <sect2 id="runtime-config-wal-checkpoints">
-     <title>Checkpoints</title>
-&common;
-    <variablelist>
-     <varlistentry id="guc-checkpoint-segments" xreflabel="checkpoint_segments">
-      <term><varname>checkpoint_segments</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>checkpoint_segments</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Maximum number of log file segments between automatic WAL
-        checkpoints (each segment is normally 16 megabytes). The default
-        is three segments.  Increasing this parameter can increase the
-        amount of time needed for crash recovery.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-checkpoint-timeout" xreflabel="checkpoint_timeout">
-      <term><varname>checkpoint_timeout</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>checkpoint_timeout</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Maximum time between automatic WAL checkpoints, in
-        seconds. The default is five minutes (<literal>5min</>).
-        Increasing this parameter can increase the amount of time needed
-        for crash recovery.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-checkpoint-completion-target" xreflabel="checkpoint_completion_target">
-      <term><varname>checkpoint_completion_target</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>checkpoint_completion_target</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the target of checkpoint completion, as a fraction of
-        total time between checkpoints. The default is 0.5.
-
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-checkpoint-warning" xreflabel="checkpoint_warning">
-      <term><varname>checkpoint_warning</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>checkpoint_warning</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Write a message to the server log if checkpoints caused by
-        the filling of checkpoint segment files happen closer together
-        than this many seconds (which suggests that
-        <varname>checkpoint_segments</> ought to be raised).  The default is
-        30 seconds (<literal>30s</>).  Zero disables the warning.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-     </sect2>
-     <sect2 id="runtime-config-wal-archiving">
-     <title>Archiving</title>
-&common;
-    <variablelist>
-     <varlistentry id="guc-archive-mode" xreflabel="archive_mode">
-      <term><varname>archive_mode</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>archive_mode</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When <varname>archive_mode</> is enabled, completed WAL segments
-        are sent to archive storage by setting
-        <xref linkend="guc-archive-command">.
-        <varname>archive_mode</> and <varname>archive_command</> are
-        separate variables so that <varname>archive_command</> can be
-        changed without leaving archiving mode.
-        This parameter can only be set at server start. <varname>wal_level</>
-        must be set to <literal>archive</> or <literal>hot_standby</> to
-        enable <varname>archive_mode</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-archive-command" xreflabel="archive_command">
-      <term><varname>archive_command</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>archive_command</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        The shell command to execute to archive a completed WAL file
-        segment.  Any <literal>%p</> in the string is
-        replaced by the path name of the file to archive, and any
-        <literal>%f</> is replaced by only the file name.
-        (The path name is relative to the working directory of the server,
-        i.e., the cluster's data directory.)
-        Use <literal>%%</> to embed an actual <literal>%</> character in the
-        command.  It is important for the command to return a zero
-        exit status only if it succeeds. For more information see
-        <xref linkend="backup-archiving-wal">.
-       </para>
-       <para>
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.  It is ignored unless
-        <varname>archive_mode</> was enabled at server start.
-        If <varname>archive_command</> is an empty string (the default) while
-        <varname>archive_mode</> is enabled, WAL archiving is temporarily
-        disabled, but the server continues to accumulate WAL segment files in
-        the expectation that a command will soon be provided.  Setting
-        <varname>archive_command</> to a command that does nothing but
-        return true, e.g. <literal>/bin/true</> (<literal>REM</> on
-        Windows), effectively disables
-        archiving, but also breaks the chain of WAL files needed for
-        archive recovery, so it should only be used in unusual circumstances.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-archive-timeout" xreflabel="archive_timeout">
-      <term><varname>archive_timeout</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>archive_timeout</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        The <xref linkend="guc-archive-command"> is only invoked for
-        completed WAL segments. Hence, if your server generates little WAL
-        traffic (or has slack periods where it does so), there could be a
-        long delay between the completion of a transaction and its safe
-        recording in archive storage.  To limit how old unarchived
-        data can be, you can set <varname>archive_timeout</> to force the
-        server to switch to a new WAL segment file periodically.  When this
-        parameter is greater than zero, the server will switch to a new
-        segment file whenever this many seconds have elapsed since the last
-        segment file switch, and there has been any database activity,
-        including a single checkpoint.  (Increasing
-        <varname>checkpoint_timeout</> will reduce unnecessary
-        checkpoints on an idle system.)
-        Note that archived files that are closed early
-        due to a forced switch are still the same length as completely full
-        files.  Therefore, it is unwise to use a very short
-        <varname>archive_timeout</> &mdash; it will bloat your archive
-        storage.  <varname>archive_timeout</> settings of a minute or so are
-        usually reasonable.  This parameter can only be set in the
-        <filename>postgresql.conf</> file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-
-<!-- No evaluation for asynchronous streaming replication -->
-    <sect2 id="runtime-config-replication">
-     <title>Streaming Replication</title>
-<!## XC>
-&pgonly;
-     <para>
-      Streaming replication has not been tested
-      with <productname>Postgres-XC</productname> yet.  Because this
-      version of streaming replication is based upon asynchronous log shipping,
-      there could be a risk to have the status of Coordinators and
-      Datanodes inconsistent.  The development team leaves the test
-      and the use of this entirely to users.
-     </para>
-<!## end>
-<!## XL>
-&pgonly;
-     <para>
-      Streaming replication only been thoroughly tested in asynchronous mode
-      with <productname>Postgres-XL</productname>.
-     </para>
-<!## end>
-
-     <para>
-      These settings control the behavior of the built-in
-      <firstterm>streaming replication</> feature.
-      These parameters would be set on the primary server that is
-      to send replication data to one or more standby servers.
-     </para>
-
-     <variablelist>
-      <varlistentry id="guc-max-wal-senders" xreflabel="max_wal_senders">
-       <term><varname>max_wal_senders</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>max_wal_senders</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-       <para>
-        Specifies the maximum number of concurrent connections from standby
-        servers or streaming base backup clients (i.e., the maximum number of
-        simultaneously running WAL sender
-        processes). The default is zero. This parameter can only be set at
-        server start. <varname>wal_level</> must be set to <literal>archive</>
-        or <literal>hot_standby</> to allow connections from standby servers.
-       </para>
-       </listitem>
-      </varlistentry>
-      <varlistentry id="guc-wal-sender-delay" xreflabel="wal_sender_delay">
-       <term><varname>wal_sender_delay</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>wal_sender_delay</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-       <para>
-        Specifies the delay between activity rounds for WAL sender processes.
-        In each round the WAL sender sends any WAL accumulated since the last
-        round to the standby server. It then sleeps for
-        <varname>wal_sender_delay</> milliseconds, and repeats. The sleep
-        is interrupted by transaction commit, so the effects of a committed
-        transaction are sent to standby servers as soon as the commit
-        happens, regardless of this setting. The default value is one second
-        (<literal>1s</>).
-        Note that on many systems, the effective resolution of sleep delays is
-        10 milliseconds; setting <varname>wal_sender_delay</> to a value that
-        is not a multiple of 10 might have the same results as setting it to
-        the next higher multiple of 10. This parameter can only be set in the
-        <filename>postgresql.conf</> file or on the server command line.
-       </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry id="guc-wal-keep-segments" xreflabel="wal_keep_segments">
-       <term><varname>wal_keep_segments</varname> (<type>integer</type>)</term>
-       <indexterm>
-        <primary><varname>wal_keep_segments</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-       <para>
-        Specifies the minimum number of past log file segments kept in the
-        <filename>pg_xlog</>
-        directory, in case a standby server needs to fetch them for streaming
-        replication. Each segment is normally 16 megabytes. If a standby
-        server connected to the primary falls behind by more than
-        <varname>wal_keep_segments</> segments, the primary might remove
-        a WAL segment still needed by the standby, in which case the
-        replication connection will be terminated.  (However, the standby
-        server can recover by fetching the segment from archive, if WAL
-        archiving is in use.)
-       </para>
-
-       <para>
-        This sets only the minimum number of segments retained in
-        <filename>pg_xlog</>; the system might need to retain more segments
-        for WAL archival or to recover from a checkpoint. If
-        <varname>wal_keep_segments</> is zero (the default), the system
-        doesn't keep any extra segments for standby purposes, and the number
-        of old WAL segments available to standby servers is a function of
-        the location of the previous checkpoint and status of WAL
-        archiving.  This parameter has no effect on restartpoints.
-        This parameter can only be set in the
-        <filename>postgresql.conf</> file or on the server command line.
-       </para>
-       </listitem>
-      </varlistentry>
-
-     <varlistentry id="guc-vacuum-defer-cleanup-age" xreflabel="vacuum_defer_cleanup_age">
-      <term><varname>vacuum_defer_cleanup_age</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>vacuum_defer_cleanup_age</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the number of transactions by which <command>VACUUM</> and
-        <acronym>HOT</> updates will defer cleanup of dead row versions. The
-        default is zero transactions, meaning that dead row versions can be
-        removed as soon as possible, that is, as soon as they are no longer
-        visible to any open transaction.  You may wish to set this to a
-        non-zero value on a primary server that is supporting hot standby
-        servers, as described in <xref linkend="hot-standby">.  This allows
-        more time for queries on the standby to complete without incurring
-        conflicts due to early cleanup of rows.  However, since the value
-        is measured in terms of number of write transactions occurring on the
-        primary server, it is difficult to predict just how much additional
-        grace time will be made available to standby queries.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-       <para>
-        You should also consider setting <varname>hot_standby_feedback</>
-        as an alternative to using this parameter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-replication-timeout" xreflabel="replication_timeout">
-      <term><varname>replication_timeout</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>replication_timeout</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Terminate replication connections that are inactive longer
-        than the specified number of milliseconds. This is useful for
-        the primary server to detect a standby crash or network outage.
-        A value of zero disables the timeout mechanism.  This parameter
-        can only be set in
-        the <filename>postgresql.conf</> file or on the server command line.
-        The default value is 60 seconds.
-       </para>
-       <para>
-        To prevent connections from being terminated prematurely,
-        <xref linkend="guc-wal-receiver-status-interval">
-        must be enabled on the standby, and its value must be less than the
-        value of <varname>replication_timeout</>.
-       </para>
-      </listitem>
-     </varlistentry>
-     </variablelist>
-    </sect2>
-
-    <sect2 id="runtime-config-sync-rep">
-     <title>Synchronous Replication</title>
-
-     <para>
-      These settings control the behavior of the built-in
-      <firstterm>synchronous replication</> feature.
-      These parameters would be set on the primary server that is
-      to send replication data to one or more standby servers.
-     </para>
-
-     <variablelist>
-     <varlistentry id="guc-synchronous-standby-names" xreflabel="synchronous_standby_names">
-      <term><varname>synchronous_standby_names</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>synchronous_standby_names</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies a priority ordered list of standby names that can offer
-        synchronous replication.  At any one time there will be at most one
-        synchronous standby that will wake sleeping users following commit.
-        The synchronous standby will be the first named standby that is
-        both currently connected and streaming in real-time to the standby
-        (as shown by a state of "STREAMING").  Other standby servers
-        with listed later will become potential synchronous standbys.
-        If the current synchronous standby disconnects for whatever reason
-        it will be replaced immediately with the next highest priority standby.
-        Specifying more than one standby name can allow very high availability.
-       </para>
-       <para>
-        The standby name is currently taken as the application_name of the
-        standby, as set in the primary_conninfo on the standby. Names are
-        not enforced for uniqueness. In case of duplicates one of the standbys
-        will be chosen to be the synchronous standby, though exactly which
-        one is indeterminate.
-        The special entry <literal>*</> matches any application_name, including
-        the default application name of <literal>walreceiver</>.
-       </para>
-       <para>
-        If no synchronous standby names are specified, then synchronous
-        replication is not enabled and transaction commit will never wait for
-        replication.  This is the default configuration.  Even when
-        synchronous replication is enabled, individual transactions can be
-        configured not to wait for replication by setting the
-        <xref linkend="guc-synchronous-commit"> parameter to
-        <literal>local</> or <literal>off</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-
-<!-- No evaluation for standby servers yet! -->
-    <sect2 id="runtime-config-standby">
-    <title>Standby Servers</title>
-     <para>
-      These settings control the behavior of a standby server that is
-      to receive replication data.
-     </para>
-
-    <variablelist>
-
-<!## PG>
-<!-- No Hot Standby Server Support Yet -->
-     <varlistentry id="guc-hot-standby" xreflabel="hot_standby">
-      <term><varname>hot_standby</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>hot_standby</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies whether or not you can connect and run queries during
-        recovery, as described in <xref linkend="hot-standby">.
-        The default value is <literal>off</literal>.
-        This parameter can only be set at server start. It only has effect
-        during archive recovery or in standby mode.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-
-     <varlistentry id="guc-max-standby-archive-delay" xreflabel="max_standby_archive_delay">
-      <term><varname>max_standby_archive_delay</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_standby_archive_delay</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-<!## PG>
-        <!-- No Hot Standby Support Yet -->
-        When Hot Standby is active, this parameter determines how long the
-        standby server should wait before canceling standby queries that
-        conflict with about-to-be-applied WAL entries, as described in
-        <xref linkend="hot-standby-conflict">.
-<!## end>
-        <varname>max_standby_archive_delay</> applies when WAL data is
-        being read from WAL archive (and is therefore not current).
-        The default is 30 seconds. Units are milliseconds if not specified.
-        A value of -1 allows the standby to wait forever for conflicting
-        queries to complete.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-       <para>
-        Note that <varname>max_standby_archive_delay</> is not the same as the
-        maximum length of time a query can run before cancellation; rather it
-        is the maximum total time allowed to apply any one WAL segment's data.
-        Thus, if one query has resulted in significant delay earlier in the
-        WAL segment, subsequent conflicting queries will have much less grace
-        time.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-standby-streaming-delay" xreflabel="max_standby_streaming_delay">
-      <term><varname>max_standby_streaming_delay</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_standby_streaming_delay</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-<!## PG>
-        <!-- No Hot Standby Support Yet -->
-        When Hot Standby is active, this parameter determines how long the
-        standby server should wait before canceling standby queries that
-        conflict with about-to-be-applied WAL entries, as described in
-        <xref linkend="hot-standby-conflict">.
-<!## end>
-        <varname>max_standby_streaming_delay</> applies when WAL data is
-        being received via streaming replication.
-        The default is 30 seconds. Units are milliseconds if not specified.
-        A value of -1 allows the standby to wait forever for conflicting
-        queries to complete.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-       <para>
-        Note that <varname>max_standby_streaming_delay</> is not the same as
-        the maximum length of time a query can run before cancellation; rather
-        it is the maximum total time allowed to apply WAL data once it has
-        been received from the primary server.  Thus, if one query has
-        resulted in significant delay, subsequent conflicting queries will
-        have much less grace time until the standby server has caught up
-        again.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-wal-receiver-status-interval" xreflabel="wal_receiver_status_interval">
-      <term><varname>wal_receiver_status_interval</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>wal_receiver_status_interval</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-      <para>
-       Specifies the minimum frequency, in seconds, for the WAL receiver
-       process on the standby to send information about replication progress
-       to the primary, where they can be seen using the
-       <literal>pg_stat_replication</literal> view.  The standby will report
-       the last transaction log position it has written, the last position it
-       has flushed to disk, and the last position it has applied.  Updates are
-       sent each time the write or flush positions changed, or at least as
-       often as specified by this parameter.  Thus, the apply position may
-       lag slightly behind the true position.  Setting this parameter to zero
-       disables status updates completely.  This parameter can only be set in
-       the <filename>postgresql.conf</> file or on the server command line.
-       The default value is 10 seconds.
-      </para>
-      <para>
-       When <xref linkend="guc-replication-timeout"> is enabled on the primary,
-       <varname>wal_receiver_status_interval</> must be enabled, and its value
-       must be less than the value of <varname>replication_timeout</>.
-      </para>
-      </listitem>
-     </varlistentry>
-
-<!## PG>
-     <!-- No Not Standby Support Yet -->
-     <varlistentry id="guc-hot-standby-feedback" xreflabel="hot_standby">
-      <term><varname>hot_standby_feedback</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>hot_standby_feedback</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies whether or not a hot standby will send feedback to the primary
-        about queries currently executing on the standby. This parameter can
-        be used to eliminate query cancels caused by cleanup records, but
-        can cause database bloat on the primary for some workloads.
-        The default value is <literal>off</literal>.  Feedback messages will not
-        be sent more frequently than once per <varname>wal_receiver_status_interval</>.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-
-     </variablelist>
-    </sect2>
-   </sect1>
-
-   <sect1 id="runtime-config-query">
-    <title>Query Planning</title>
-
-    <sect2 id="runtime-config-query-enable">
-     <title>Planner Method Configuration</title>
-
-      <para>
-       These configuration parameters provide a crude method of
-       influencing the query plans chosen by the query optimizer. If
-       the default plan chosen by the optimizer for a particular query
-       is not optimal, a <emphasis>temporary</> solution is to use one
-       of these configuration parameters to force the optimizer to
-       choose a different plan.
-       Better ways to improve the quality of the
-       plans chosen by the optimizer include adjusting the planer cost
-       constants (see <xref linkend="runtime-config-query-constants">),
-       running <xref linkend="sql-analyze"> manually, increasing
-       the value of the <xref
-       linkend="guc-default-statistics-target"> configuration parameter,
-       and increasing the amount of statistics collected for
-       specific columns using <command>ALTER TABLE SET
-       STATISTICS</command>.
-      </para>
-
-     <variablelist>
-     <varlistentry id="guc-enable-bitmapscan" xreflabel="enable_bitmapscan">
-      <term><varname>enable_bitmapscan</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary>bitmap scan</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>enable_bitmapscan</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of bitmap-scan plan
-        types. The default is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-enable-hashagg" xreflabel="enable_hashagg">
-      <term><varname>enable_hashagg</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>enable_hashagg</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of hashed
-        aggregation plan types. The default is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-enable-hashjoin" xreflabel="enable_hashjoin">
-      <term><varname>enable_hashjoin</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>enable_hashjoin</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of hash-join plan
-        types. The default is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-enable-indexscan" xreflabel="enable_indexscan">
-      <term><varname>enable_indexscan</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary>index scan</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>enable_indexscan</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of index-scan plan
-        types. The default is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-enable-material" xreflabel="enable_material">
-      <term><varname>enable_material</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>enable_material</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of materialization.
-        It is impossible to suppress materialization entirely,
-        but turning this variable off prevents the planner from inserting
-        materialize nodes except in cases where it is required for correctness.
-        The default is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-enable-mergejoin" xreflabel="enable_mergejoin">
-      <term><varname>enable_mergejoin</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>enable_mergejoin</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of merge-join plan
-        types. The default is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-enable-nestloop" xreflabel="enable_nestloop">
-      <term><varname>enable_nestloop</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>enable_nestloop</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of nested-loop join
-        plans. It is impossible to suppress nested-loop joins entirely,
-        but turning this variable off discourages the planner from using
-        one if there are other methods available. The default is
-        <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-enable-seqscan" xreflabel="enable_seqscan">
-      <term><varname>enable_seqscan</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary>sequential scan</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>enable_seqscan</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of sequential scan
-        plan types. It is impossible to suppress sequential scans
-        entirely, but turning this variable off discourages the planner
-        from using one if there are other methods available. The
-        default is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-enable-sort" xreflabel="enable_sort">
-      <term><varname>enable_sort</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>enable_sort</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of explicit sort
-        steps. It is impossible to suppress explicit sorts entirely,
-        but turning this variable off discourages the planner from
-        using one if there are other methods available. The default
-        is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-enable-tidscan" xreflabel="enable_tidscan">
-      <term><varname>enable_tidscan</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>enable_tidscan</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of <acronym>TID</>
-        scan plan types. The default is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-     </sect2>
-     <sect2 id="runtime-config-query-constants">
-     <title>Planner Cost Constants</title>
-
-    <para>
-     The <firstterm>cost</> variables described in this section are measured
-     on an arbitrary scale.  Only their relative values matter, hence
-     scaling them all up or down by the same factor will result in no change
-     in the planner's choices.  By default, these cost variables are based on
-     the cost of sequential page fetches; that is,
-     <varname>seq_page_cost</> is conventionally set to <literal>1.0</>
-     and the other cost variables are set with reference to that.  But
-     you can use a different scale if you prefer, such as actual execution
-     times in milliseconds on a particular machine.
-    </para>
-
-   <note>
-    <para>
-     Unfortunately, there is no well-defined method for determining ideal
-     values for the cost variables.  They are best treated as averages over
-     the entire mix of queries that a particular installation will receive.  This
-     means that changing them on the basis of just a few experiments is very
-     risky.
-    </para>
-   </note>
-
-     <variablelist>
-
-     <varlistentry id="guc-seq-page-cost" xreflabel="seq_page_cost">
-      <term><varname>seq_page_cost</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>seq_page_cost</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the planner's estimate of the cost of a disk page fetch
-        that is part of a series of sequential fetches.  The default is 1.0.
-        This value can be overridden for a particular tablespace by setting
-        the tablespace parameter of the same name
-        (see <xref linkend="sql-altertablespace">).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-random-page-cost" xreflabel="random_page_cost">
-      <term><varname>random_page_cost</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>random_page_cost</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the planner's estimate of the cost of a
-        non-sequentially-fetched disk page.  The default is 4.0.
-        This value can be overridden for a particular tablespace by setting
-        the tablespace parameter of the same name
-        (see <xref linkend="sql-altertablespace">).
-       </para>
-
-       <para>
-        Reducing this value relative to <varname>seq_page_cost</>
-        will cause the system to prefer index scans; raising it will
-        make index scans look relatively more expensive.  You can raise
-        or lower both values together to change the importance of disk I/O
-        costs relative to CPU costs, which are described by the following
-        parameters.
-       </para>
-
-       <tip>
-        <para>
-         Although the system will let you set <varname>random_page_cost</> to
-         less than <varname>seq_page_cost</>, it is not physically sensible
-         to do so.  However, setting them equal makes sense if the database
-         is entirely cached in RAM, since in that case there is no penalty
-         for touching pages out of sequence.  Also, in a heavily-cached
-         database you should lower both values relative to the CPU parameters,
-         since the cost of fetching a page already in RAM is much smaller
-         than it would normally be.
-        </para>
-       </tip>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-cpu-tuple-cost" xreflabel="cpu_tuple_cost">
-      <term><varname>cpu_tuple_cost</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>cpu_tuple_cost</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the planner's estimate of the cost of processing
-        each row during a query.
-        The default is 0.01.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-cpu-index-tuple-cost" xreflabel="cpu_index_tuple_cost">
-      <term><varname>cpu_index_tuple_cost</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>cpu_index_tuple_cost</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the planner's estimate of the cost of processing
-        each index entry during an index scan.
-        The default is 0.005.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-cpu-operator-cost" xreflabel="cpu_operator_cost">
-      <term><varname>cpu_operator_cost</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>cpu_operator_cost</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the planner's estimate of the cost of processing each
-        operator or function executed during a query.
-        The default is 0.0025.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-effective-cache-size" xreflabel="effective_cache_size">
-      <term><varname>effective_cache_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>effective_cache_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the planner's assumption about the effective size of the
-        disk cache that is available to a single query.  This is
-        factored into estimates of the cost of using an index; a
-        higher value makes it more likely index scans will be used, a
-        lower value makes it more likely sequential scans will be
-        used. When setting this parameter you should consider both
-<!## PG>
-        <productname>PostgreSQL</productname>'s shared buffers and the
-        portion of the kernel's disk cache that will be used for
-        <productname>PostgreSQL</productname> data files.  Also, take
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname>'s shared buffers and the
-        portion of the kernel's disk cache that will be used for
-        <productname>Postgres-XC</productname> data files.  Also, take
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname>'s shared buffers and the
-        portion of the kernel's disk cache that will be used for
-        <productname>Postgres-XL</productname> data files.  Also, take
-<!## end>
-        into account the expected number of concurrent queries on different
-        tables, since they will have to share the available
-        space.  This parameter has no effect on the size of shared
-<!## PG>
-        memory allocated by <productname>PostgreSQL</productname>, nor
-<!## end>
-<!## XC>
-        memory allocated by <productname>Postgres-XC</productname>, nor
-<!## end>
-<!## XL>
-        memory allocated by <productname>Postgres-XL</productname>, nor
-<!## end>
-        does it reserve kernel disk cache; it is used only for estimation
-        purposes.  The system also does not assume data remains in
-        the disk cache between queries.  The default is 128 megabytes
-        (<literal>128MB</>).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-
-    </sect2>
-     <sect2 id="runtime-config-query-geqo">
-     <title>Genetic Query Optimizer</title>
-
-     <para>
-      The genetic query optimizer (GEQO) is an algorithm that does query
-      planning using heuristic searching.  This reduces planning time for
-      complex queries (those joining many relations), at the cost of producing
-      plans that are sometimes inferior to those found by the normal
-      exhaustive-search algorithm.  Also, GEQO's searching is randomized and
-      therefore its plans may vary nondeterministically.
-      For more information see <xref linkend="geqo">.
-     </para>
-
-     <variablelist>
-
-     <varlistentry id="guc-geqo" xreflabel="geqo">
-      <indexterm>
-       <primary>genetic query optimization</primary>
-      </indexterm>
-      <indexterm>
-       <primary>GEQO</primary>
-       <see>genetic query optimization</see>
-      </indexterm>
-      <indexterm>
-       <primary><varname>geqo</> configuration parameter</primary>
-      </indexterm>
-      <term><varname>geqo</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Enables or disables genetic query optimization.
-        This is on by default.  It is usually best not to turn it off in
-        production; the <varname>geqo_threshold</varname> variable provides
-        more granular control of GEQO.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-geqo-threshold" xreflabel="geqo_threshold">
-      <term><varname>geqo_threshold</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>geqo_threshold</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Use genetic query optimization to plan queries with at least
-        this many <literal>FROM</> items involved. (Note that a
-        <literal>FULL OUTER JOIN</> construct counts as only one <literal>FROM</>
-        item.) The default is 12. For simpler queries it is usually best
-        to use the deterministic, exhaustive planner, but for queries with
-        many tables the deterministic planner takes too long, often
-        longer than the penalty of executing a suboptimal plan.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-geqo-effort" xreflabel="geqo_effort">
-      <term><varname>geqo_effort</varname>
-      (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>geqo_effort</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls the trade-off between planning time and query plan
-        quality in GEQO. This variable must be an integer in the
-        range from 1 to 10. The default value is five. Larger values
-        increase the time spent doing query planning, but also
-        increase the likelihood that an efficient query plan will be
-        chosen.
-       </para>
-
-       <para>
-        <varname>geqo_effort</varname> doesn't actually do anything
-        directly; it is only used to compute the default values for
-        the other variables that influence GEQO behavior (described
-        below). If you prefer, you can set the other parameters by
-        hand instead.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-geqo-pool-size" xreflabel="geqo_pool_size">
-      <term><varname>geqo_pool_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>geqo_pool_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls the pool size used by GEQO, that is the
-        number of individuals in the genetic population.  It must be
-        at least two, and useful values are typically 100 to 1000.  If
-        it is set to zero (the default setting) then a suitable
-        value is chosen based on <varname>geqo_effort</varname> and
-        the number of tables in the query.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-geqo-generations" xreflabel="geqo_generations">
-      <term><varname>geqo_generations</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>geqo_generations</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls the number of generations used by GEQO, that is
-        the number of iterations of the algorithm.  It must
-        be at least one, and useful values are in the same range as
-        the pool size.  If it is set to zero (the default setting)
-        then a suitable value is chosen based on
-        <varname>geqo_pool_size</varname>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-geqo-selection-bias" xreflabel="geqo_selection_bias">
-      <term><varname>geqo_selection_bias</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>geqo_selection_bias</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls the selection bias used by GEQO. The selection bias
-        is the selective pressure within the population. Values can be
-        from 1.50 to 2.00; the latter is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-geqo-seed" xreflabel="geqo_seed">
-      <term><varname>geqo_seed</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>geqo_seed</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls the initial value of the random number generator used
-        by GEQO to select random paths through the join order search space.
-        The value can range from zero (the default) to one.  Varying the
-        value changes the set of join paths explored, and may result in a
-        better or worse best path being found.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-     <sect2 id="runtime-config-query-other">
-     <title>Other Planner Options</title>
-
-     <variablelist>
-
-     <varlistentry id="guc-default-statistics-target" xreflabel="default_statistics_target">
-      <term><varname>default_statistics_target</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>default_statistics_target</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the default statistics target for table columns without
-        a column-specific target set via <command>ALTER TABLE
-        SET STATISTICS</>.  Larger values increase the time needed to
-        do <command>ANALYZE</>, but might improve the quality of the
-        planner's estimates. The default is 100. For more information
-<!## PG>
-        on the use of statistics by the <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-        on the use of statistics by the <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-        on the use of statistics by the <productname>Postgres-XL</>
-<!## end>
-        query planner, refer to <xref linkend="planner-stats">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-constraint-exclusion" xreflabel="constraint_exclusion">
-      <term><varname>constraint_exclusion</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary>constraint exclusion</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>constraint_exclusion</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls the query planner's use of table constraints to
-        optimize queries.
-        The allowed values of <varname>constraint_exclusion</> are
-        <literal>on</> (examine constraints for all tables),
-        <literal>off</> (never examine constraints), and
-        <literal>partition</> (examine constraints only for inheritance child
-        tables and <literal>UNION ALL</> subqueries).
-        <literal>partition</> is the default setting.
-        It is often used with inheritance and partitioned tables to
-        improve performance.
-      </para>
-
-       <para>
-        When this parameter allows it for a particular table, the planner
-        compares query conditions with the table's <literal>CHECK</>
-        constraints, and omits scanning tables for which the conditions
-        contradict the constraints.  For example:
-
-<programlisting>
-CREATE TABLE parent(key integer, ...);
-CREATE TABLE child1000(check (key between 1000 and 1999)) INHERITS(parent);
-CREATE TABLE child2000(check (key between 2000 and 2999)) INHERITS(parent);
-...
-SELECT * FROM parent WHERE key = 2400;
-</programlisting>
-
-        With constraint exclusion enabled, this <command>SELECT</>
-        will not scan <structname>child1000</> at all, improving performance.
-       </para>
-
-       <para>
-        Currently, constraint exclusion is enabled by default
-        only for cases that are often used to implement table partitioning.
-        Turning it on for all tables imposes extra planning overhead that is
-        quite noticeable on simple queries, and most often will yield no
-        benefit for simple queries.  If you have no partitioned tables
-        you might prefer to turn it off entirely.
-       </para>
-
-<!## PG>
-<!-- NOTICE:
-     Partitioning!
--->
-       <para>
-        Refer to <xref linkend="ddl-partitioning-constraint-exclusion"> for
-        more information on using constraint exclusion and partitioning.
-       </para>
-<!## end>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-cursor-tuple-fraction" xreflabel="cursor_tuple_fraction">
-      <term><varname>cursor_tuple_fraction</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>cursor_tuple_fraction</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the planner's estimate of the fraction of a cursor's rows that
-        will be retrieved.  The default is 0.1.  Smaller values of this
-        setting bias the planner towards using <quote>fast start</> plans
-        for cursors, which will retrieve the first few rows quickly while
-        perhaps taking a long time to fetch all rows.  Larger values
-        put more emphasis on the total estimated time.  At the maximum
-        setting of 1.0, cursors are planned exactly like regular queries,
-        considering only the total estimated time and not how soon the
-        first rows might be delivered.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-from-collapse-limit" xreflabel="from_collapse_limit">
-      <term><varname>from_collapse_limit</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>from_collapse_limit</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        The planner will merge sub-queries into upper queries if the
-        resulting <literal>FROM</literal> list would have no more than
-        this many items.  Smaller values reduce planning time but might
-        yield inferior query plans.  The default is eight.
-        For more information see <xref linkend="explicit-joins">.
-       </para>
-
-       <para>
-        Setting this value to <xref linkend="guc-geqo-threshold"> or more
-        may trigger use of the GEQO planner, resulting in nondeterministic
-        plans.  See <xref linkend="runtime-config-query-geqo">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-join-collapse-limit" xreflabel="join_collapse_limit">
-      <term><varname>join_collapse_limit</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>join_collapse_limit</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        The planner will rewrite explicit <literal>JOIN</>
-        constructs (except <literal>FULL JOIN</>s) into lists of
-        <literal>FROM</> items whenever a list of no more than this many items
-        would result.  Smaller values reduce planning time but might
-        yield inferior query plans.
-       </para>
-
-       <para>
-        By default, this variable is set the same as
-        <varname>from_collapse_limit</varname>, which is appropriate
-        for most uses. Setting it to 1 prevents any reordering of
-        explicit <literal>JOIN</>s. Thus, the explicit join order
-        specified in the query will be the actual order in which the
-        relations are joined. Because the query planner does not always choose
-        the optimal join order, advanced users can elect to
-        temporarily set this variable to 1, and then specify the join
-        order they desire explicitly.
-        For more information see <xref linkend="explicit-joins">.
-       </para>
-
-       <para>
-        Setting this value to <xref linkend="guc-geqo-threshold"> or more
-        may trigger use of the GEQO planner, resulting in nondeterministic
-        plans.  See <xref linkend="runtime-config-query-geqo">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-   </sect1>
-
-   <sect1 id="runtime-config-logging">
-    <title>Error Reporting and Logging</title>
-
-    <indexterm zone="runtime-config-logging">
-     <primary>server log</primary>
-    </indexterm>
-
-    <sect2 id="runtime-config-logging-where">
-     <title>Where To Log</title>
-
-     <indexterm zone="runtime-config-logging-where">
-      <primary>where to log</primary>
-     </indexterm>
-&common;
-     <variablelist>
-
-     <varlistentry id="guc-log-destination" xreflabel="log_destination">
-      <term><varname>log_destination</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>log_destination</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-<!## PG>
-        <productname>PostgreSQL</productname> supports several methods
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> supports several methods
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> supports several methods
-<!## end>
-         for logging server messages, including
-         <systemitem>stderr</systemitem>, <systemitem>csvlog</systemitem> and
-         <systemitem>syslog</systemitem>. On Windows,
-         <systemitem>eventlog</systemitem> is also supported. Set this
-         parameter to a list of desired log destinations separated by
-         commas. The default is to log to <systemitem>stderr</systemitem>
-         only.
-         This parameter can only be set in the <filename>postgresql.conf</>
-         file or on the server command line.
-       </para>
-       <para>
-        If <systemitem>csvlog</> is included in <varname>log_destination</>,
-        log entries are output in <quote>comma separated
-        value</> (<acronym>CSV</>) format, which is convenient for
-        loading logs into programs.
-        See <xref linkend="runtime-config-logging-csvlog"> for details.
-        <varname>logging_collector</varname> must be enabled to generate
-        CSV-format log output.
-       </para>
-
-       <note>
-        <para>
-         On most Unix systems, you will need to alter the configuration of
-         your system's <application>syslog</application> daemon in order
-         to make use of the <systemitem>syslog</systemitem> option for
-<!## PG>
-         <varname>log_destination</>.  <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-         <varname>log_destination</>.  <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-         <varname>log_destination</>.  <productname>Postgres-XL</productname>
-<!## end>
-         can log to <application>syslog</application> facilities
-         <literal>LOCAL0</> through <literal>LOCAL7</> (see <xref
-         linkend="guc-syslog-facility">), but the default
-         <application>syslog</application> configuration on most platforms
-         will discard all such messages.  You will need to add something like:
-<programlisting>
-local0.*    /var/log/postgresql
-</programlisting>
-         to the  <application>syslog</application> daemon's configuration file
-         to make it work.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-logging-collector" xreflabel="logging_collector">
-      <term><varname>logging_collector</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>logging_collector</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-         This parameter captures plain and CSV-format log messages
-         sent to <application>stderr</> and redirects them into log files.
-         This approach is often more useful than
-         logging to <application>syslog</>, since some types of messages
-         might not appear in <application>syslog</> output (a common example
-         is dynamic-linker failure messages).
-         This parameter can only be set at server start.
-       </para>
-
-       <note>
-        <para>
-          The logging collector is designed to never lose messages.  This means
-          that in case of extremely high load, server processes could be
-          blocked due to trying to send additional log messages when the
-          collector has fallen behind.  In contrast, <application>syslog</>
-          prefers to drop messages if it cannot write them, which means it's
-          less reliable in those cases but it will not block the rest of the
-          system.
-        </para>
-       </note>
-
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-directory" xreflabel="log_directory">
-      <term><varname>log_directory</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>log_directory</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When <varname>logging_collector</> is enabled,
-        this parameter determines the directory in which log files will be created.
-        It can be specified as an absolute path, or relative to the
-        cluster data directory.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-filename" xreflabel="log_filename">
-      <term><varname>log_filename</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>log_filename</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When <varname>logging_collector</varname> is enabled,
-        this parameter sets the file names of the created log files.  The value
-        is treated as a <systemitem>strftime</systemitem> pattern,
-        so <literal>%</literal>-escapes can be used to specify time-varying
-        file names.  (Note that if there are
-        any time-zone-dependent <literal>%</literal>-escapes, the computation
-        is done in the zone specified
-        by <xref linkend="guc-log-timezone">.)
-        Note that the system's <systemitem>strftime</systemitem> is not used
-        directly, so platform-specific (nonstandard) extensions do not work.
-       </para>
-       <para>
-        If you specify a file name without escapes, you should plan to
-        use a log rotation utility to avoid eventually filling the
-        entire disk.  In releases prior to 8.4, if
-        no <literal>%</literal> escapes were
-<!## PG>
-        present, <productname>PostgreSQL</productname> would append
-<!## end>
-<!## XC>
-        present, <productname>Postgres-XC</productname> would append
-<!## end>
-<!## XL>
-        present, <productname>Postgres-XL</productname> would append
-<!## end>
-        the epoch of the new log file's creation time, but this is no
-        longer the case.
-       </para>
-       <para>
-        If CSV-format output is enabled in <varname>log_destination</>,
-        <literal>.csv</> will be appended to the timestamped
-        log file name to create the file name for CSV-format output.
-        (If <varname>log_filename</> ends in <literal>.log</>, the suffix is
-        replaced instead.)
-        In the case of the example above, the CSV
-        file name will be <literal>server_log.1093827753.csv</literal>.
-       </para>
-       <para>
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-file-mode" xreflabel="log_file_mode">
-      <term><varname>log_file_mode</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>log_file_mode</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        On Unix systems this parameter sets the permissions for log files
-        when <varname>logging_collector</varname> is enabled. (On Microsoft
-        Windows this parameter is ignored.)
-        The parameter value is expected to be a numeric mode
-        specified in the format accepted by the
-        <function>chmod</function> and <function>umask</function>
-        system calls.  (To use the customary octal format the number
-        must start with a <literal>0</literal> (zero).)
-       </para>
-       <para>
-        The default permissions are <literal>0600</>, meaning only the
-        server owner can read or write the log files.  The other commonly
-        useful setting is <literal>0640</>, allowing members of the owner's
-        group to read the files.  Note however that to make use of such a
-        setting, you'll need to alter <xref linkend="guc-log-directory"> to
-        store the files somewhere outside the cluster data directory.  In
-        any case, it's unwise to make the log files world-readable, since
-        they might contain sensitive data.
-       </para>
-       <para>
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-rotation-age" xreflabel="log_rotation_age">
-      <term><varname>log_rotation_age</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>log_rotation_age</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When <varname>logging_collector</varname> is enabled,
-        this parameter determines the maximum lifetime of an individual log file.
-        After this many minutes have elapsed, a new log file will
-        be created.  Set to zero to disable time-based creation of
-        new log files.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-rotation-size" xreflabel="log_rotation_size">
-      <term><varname>log_rotation_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>log_rotation_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When <varname>logging_collector</varname> is enabled,
-        this parameter determines the maximum size of an individual log file.
-        After this many kilobytes have been emitted into a log file,
-        a new log file will be created.  Set to zero to disable size-based
-        creation of new log files.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-truncate-on-rotation" xreflabel="log_truncate_on_rotation">
-      <term><varname>log_truncate_on_rotation</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>log_truncate_on_rotation</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When <varname>logging_collector</varname> is enabled,
-<!## PG>
-        this parameter will cause <productname>PostgreSQL</productname> to truncate (overwrite),
-<!## end>
-<!## XC>
-        this parameter will cause <productname>Postgres-XC</productname> to truncate (overwrite),
-<!## end>
-<!## XL>
-        this parameter will cause <productname>Postgres-XL</productname> to truncate (overwrite),
-<!## end>
-        rather than append to, any existing log file of the same name.
-        However, truncation will occur only when a new file is being opened
-        due to time-based rotation, not during server startup or size-based
-        rotation.  When off, pre-existing files will be appended to in
-        all cases.  For example, using this setting in combination with
-        a <varname>log_filename</varname> like <literal>postgresql-%H.log</literal>
-        would result in generating twenty-four hourly log files and then
-        cyclically overwriting them.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-       <para>
-        Example:  To keep 7 days of logs, one log file per day named
-        <literal>server_log.Mon</literal>, <literal>server_log.Tue</literal>,
-        etc, and automatically overwrite last week's log with this week's log,
-        set <varname>log_filename</varname> to <literal>server_log.%a</literal>,
-        <varname>log_truncate_on_rotation</varname> to <literal>on</literal>, and
-        <varname>log_rotation_age</varname> to <literal>1440</literal>.
-       </para>
-       <para>
-        Example: To keep 24 hours of logs, one log file per hour, but
-        also rotate sooner if the log file size exceeds 1GB, set
-        <varname>log_filename</varname> to <literal>server_log.%H%M</literal>,
-        <varname>log_truncate_on_rotation</varname> to <literal>on</literal>,
-        <varname>log_rotation_age</varname> to <literal>60</literal>, and
-        <varname>log_rotation_size</varname> to <literal>1000000</literal>.
-        Including <literal>%M</> in <varname>log_filename</varname> allows
-        any size-driven rotations that might occur to select a file name
-        different from the hour's initial file name.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-syslog-facility" xreflabel="syslog_facility">
-      <term><varname>syslog_facility</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>syslog_facility</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When logging to <application>syslog</> is enabled, this parameter
-        determines the <application>syslog</application>
-        <quote>facility</quote> to be used.  You can choose
-        from <literal>LOCAL0</>, <literal>LOCAL1</>,
-        <literal>LOCAL2</>, <literal>LOCAL3</>, <literal>LOCAL4</>,
-        <literal>LOCAL5</>, <literal>LOCAL6</>, <literal>LOCAL7</>;
-        the default is <literal>LOCAL0</>. See also the
-        documentation of your system's
-        <application>syslog</application> daemon.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-syslog-ident" xreflabel="syslog_ident">
-      <term><varname>syslog_ident</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>syslog_identity</> configuration parameter</primary>
-      </indexterm>
-       <listitem>
-        <para>
-         When logging to <application>syslog</> is enabled, this parameter
-         determines the program name used to identify
-<!## PG>
-         <productname>PostgreSQL</productname> messages in
-<!## end>
-<!## XC>
-         <productname>Postgres-XC</productname> messages in
-<!## end>
-<!## XL>
-         <productname>Postgres-XL</productname> messages in
-<!## end>
-         <application>syslog</application> logs. The default is
-         <literal>postgres</literal>.
-         This parameter can only be set in the <filename>postgresql.conf</>
-         file or on the server command line.
-        </para>
-       </listitem>
-      </varlistentry>
-
-     <varlistentry id="guc-silent-mode" xreflabel="silent_mode">
-      <term><varname>silent_mode</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>silent_mode</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Runs the server silently. If this parameter is set, the server
-        will automatically run in background and disassociate from the
-        controlling terminal.
-        This parameter can only be set at server start.
-       </para>
-
-       <caution>
-       <para>
-        When this parameter is set,
-        the server's standard output and standard error are redirected
-        to the file <filename>postmaster.log</> within the data directory.
-        There is no provision for rotating this file, so it will grow
-        indefinitely unless server log output is redirected elsewhere
-        by other settings.  It is recommended that <varname>log_destination</>
-        be set to <literal>syslog</> or that <varname>logging_collector</> be
-        enabled when using this option.  Even with those measures, errors
-        reported early during startup may appear in
-        <filename>postmaster.log</> rather than the normal log destination.
-       </para>
-       </caution>
-      </listitem>
-     </varlistentry>
-
-      </variablelist>
-    </sect2>
-     <sect2 id="runtime-config-logging-when">
-     <title>When To Log</title>
-
-     <variablelist>
-
-     <varlistentry id="guc-client-min-messages" xreflabel="client_min_messages">
-      <term><varname>client_min_messages</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>client_min_messages</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-&common;
-       <para>
-        Controls which message levels are sent to the client.
-        Valid values are <literal>DEBUG5</>,
-        <literal>DEBUG4</>, <literal>DEBUG3</>, <literal>DEBUG2</>,
-        <literal>DEBUG1</>, <literal>LOG</>, <literal>NOTICE</>,
-        <literal>WARNING</>, <literal>ERROR</>, <literal>FATAL</>,
-        and <literal>PANIC</>.  Each level
-        includes all the levels that follow it.  The later the level,
-        the fewer messages are sent.  The default is
-        <literal>NOTICE</>.  Note that <literal>LOG</> has a different
-        rank here than in <varname>log_min_messages</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-min-messages" xreflabel="log_min_messages">
-      <term><varname>log_min_messages</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>log_min_messages</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls which message levels are written to the server log.
-        Valid values are <literal>DEBUG5</>, <literal>DEBUG4</>,
-        <literal>DEBUG3</>, <literal>DEBUG2</>, <literal>DEBUG1</>,
-        <literal>INFO</>, <literal>NOTICE</>, <literal>WARNING</>,
-        <literal>ERROR</>, <literal>LOG</>, <literal>FATAL</>, and
-        <literal>PANIC</>.  Each level includes all the levels that
-        follow it.  The later the level, the fewer messages are sent
-        to the log.  The default is <literal>WARNING</>.  Note that
-        <literal>LOG</> has a different rank here than in
-        <varname>client_min_messages</>.
-        Only superusers can change this setting.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-min-error-statement" xreflabel="log_min_error_statement">
-      <term><varname>log_min_error_statement</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>log_min_error_statement</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls which SQL statements that cause an error
-        condition are recorded in the server log.  The current
-        SQL statement is included in the log entry for any message of
-        the specified severity or higher.
-        Valid values are <literal>DEBUG5</literal>,
-        <literal>DEBUG4</literal>, <literal>DEBUG3</literal>,
-        <literal>DEBUG2</literal>, <literal>DEBUG1</literal>,
-        <literal>INFO</literal>, <literal>NOTICE</literal>,
-        <literal>WARNING</literal>, <literal>ERROR</literal>,
-        <literal>LOG</literal>,
-        <literal>FATAL</literal>, and <literal>PANIC</literal>.
-        The default is <literal>ERROR</literal>, which means statements
-        causing errors, log messages, fatal errors, or panics will be logged.
-        To effectively turn off logging of failing statements,
-        set this parameter to <literal>PANIC</literal>.
-        Only superusers can change this setting.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-min-duration-statement" xreflabel="log_min_duration_statement">
-      <term><varname>log_min_duration_statement</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>log_min_duration_statement</> configuration parameter</primary>
-      </indexterm>
-       <listitem>
-        <para>
-         Causes the duration of each completed statement to be logged
-         if the statement ran for at least the specified number of
-         milliseconds.  Setting this to zero prints all statement durations.
-         Minus-one (the default) disables logging statement durations.
-         For example, if you set it to <literal>250ms</literal>
-         then all SQL statements that run 250ms or longer will be
-         logged.  Enabling this parameter can be helpful in tracking down
-         unoptimized queries in your applications.
-         Only superusers can change this setting.
-        </para>
-
-        <para>
-         For clients using extended query protocol, durations of the Parse,
-         Bind, and Execute steps are logged independently.
-        </para>
-
-       <note>
-        <para>
-         When using this option together with
-         <xref linkend="guc-log-statement">,
-         the text of statements that are logged because of
-         <varname>log_statement</> will not be repeated in the
-         duration log message.
-         If you are not using <application>syslog</>, it is recommended
-         that you log the PID or session ID using
-         <xref linkend="guc-log-line-prefix">
-         so that you can link the statement message to the later
-         duration message using the process ID or session ID.
-        </para>
-       </note>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-
-    <para>
-     <xref linkend="runtime-config-severity-levels"> explains the message
-<!## PG>
-     severity levels used by <productname>PostgreSQL</>.  If logging output
-<!## end>
-<!## XC>
-     severity levels used by <productname>Postgres-XC</>.  If logging output
-<!## end>
-<!## XL>
-     severity levels used by <productname>Postgres-XL</>.  If logging output
-<!## end>
-     is sent to <systemitem>syslog</systemitem> or Windows'
-     <systemitem>eventlog</systemitem>, the severity levels are translated
-     as shown in the table.
-    </para>
-
-    <table id="runtime-config-severity-levels">
-     <title>Message Severity Levels</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Severity</entry>
-        <entry>Usage</entry>
-        <entry><systemitem>syslog</></entry>
-        <entry><systemitem>eventlog</></entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry><literal>DEBUG1..DEBUG5</></entry>
-        <entry>Provides successively-more-detailed information for use by
-         developers.</entry>
-        <entry><literal>DEBUG</></entry>
-        <entry><literal>INFORMATION</></entry>
-       </row>
-
-       <row>
-        <entry><literal>INFO</></entry>
-        <entry>Provides information implicitly requested by the user,
-         e.g., output from <command>VACUUM VERBOSE</>.</entry>
-        <entry><literal>INFO</></entry>
-        <entry><literal>INFORMATION</></entry>
-       </row>
-
-       <row>
-        <entry><literal>NOTICE</></entry>
-        <entry>Provides information that might be helpful to users, e.g.,
-         notice of truncation of long identifiers.</entry>
-        <entry><literal>NOTICE</></entry>
-        <entry><literal>INFORMATION</></entry>
-       </row>
-
-       <row>
-        <entry><literal>WARNING</></entry>
-        <entry>Provides warnings of likely problems, e.g., <command>COMMIT</>
-         outside a transaction block.</entry>
-        <entry><literal>NOTICE</></entry>
-        <entry><literal>WARNING</></entry>
-       </row>
-
-       <row>
-        <entry><literal>ERROR</></entry>
-        <entry>Reports an error that caused the current command to
-         abort.</entry>
-        <entry><literal>WARNING</></entry>
-        <entry><literal>ERROR</></entry>
-       </row>
-
-       <row>
-        <entry><literal>LOG</></entry>
-        <entry>Reports information of interest to administrators, e.g.,
-         checkpoint activity.</entry>
-        <entry><literal>INFO</></entry>
-        <entry><literal>INFORMATION</></entry>
-       </row>
-
-       <row>
-        <entry><literal>FATAL</></entry>
-        <entry>Reports an error that caused the current session to
-         abort.</entry>
-        <entry><literal>ERR</></entry>
-        <entry><literal>ERROR</></entry>
-       </row>
-
-       <row>
-        <entry><literal>PANIC</></entry>
-        <entry>Reports an error that caused all database sessions to abort.</entry>
-        <entry><literal>CRIT</></entry>
-        <entry><literal>ERROR</></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-    </sect2>
-     <sect2 id="runtime-config-logging-what">
-     <title>What To Log</title>
-
-     <variablelist>
-
-     <varlistentry id="guc-application-name" xreflabel="application_name">
-      <term><varname>application_name</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>application_name</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-&common;
-       <para>
-        The <varname>application_name</varname> can be any string of less than
-        <symbol>NAMEDATALEN</> characters (64 characters in a standard build).
-        It is typically set by an application upon connection to the server.
-        The name will be displayed in the <structname>pg_stat_activity</> view
-        and included in CSV log entries.  It can also be included in regular
-        log entries via the <xref linkend="guc-log-line-prefix"> parameter.
-        Only printable ASCII characters may be used in the
-        <varname>application_name</varname> value. Other characters will be
-        replaced with question marks (<literal>?</literal>).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>debug_print_parse</varname> (<type>boolean</type>)</term>
-      <term><varname>debug_print_rewritten</varname> (<type>boolean</type>)</term>
-      <term><varname>debug_print_plan</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>debug_print_parse</> configuration parameter</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>debug_print_rewritten</> configuration parameter</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>debug_print_plan</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        These parameters enable various debugging output to be emitted.
-        When set, they print the resulting parse tree, the query rewriter
-        output, or the execution plan for each executed query.
-        These messages are emitted at <literal>LOG</> message level, so by
-        default they will appear in the server log but will not be sent to the
-        client.  You can change that by adjusting
-        <xref linkend="guc-client-min-messages"> and/or
-        <xref linkend="guc-log-min-messages">.
-        These parameters are off by default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>debug_pretty_print</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>debug_pretty_print</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When set, <varname>debug_pretty_print</varname> indents the messages
-        produced by <varname>debug_print_parse</varname>,
-        <varname>debug_print_rewritten</varname>, or
-        <varname>debug_print_plan</varname>.  This results in more readable
-        but much longer output than the <quote>compact</> format used when
-        it is off.  It is on by default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-checkpoints" xreflabel="log_checkpoints">
-      <term><varname>log_checkpoints</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>log_checkpoints</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Causes checkpoints and restartpoints to be logged in the server log.
-        Some statistics are included in the log messages, including the number
-        of buffers written and the time spent writing them.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line. The default is off.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-connections" xreflabel="log_connections">
-      <term><varname>log_connections</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>log_connections</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Causes each attempted connection to the server to be logged,
-        as well as successful completion of client authentication.
-        This parameter cannot be changed after session start.
-        The default is off.
-       </para>
-
-       <note>
-        <para>
-         Some client programs, like <application>psql</>, attempt
-         to connect twice while determining if a password is required, so
-         duplicate <quote>connection received</> messages do not
-         necessarily indicate a problem.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-disconnections" xreflabel="log_disconnections">
-      <term><varname>log_disconnections</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>log_disconnections</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This outputs a line in the server log similar to
-        <varname>log_connections</varname> but at session termination,
-        and includes the duration of the session.  This is off by
-        default.
-        This parameter cannot be changed after session start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry id="guc-log-duration" xreflabel="log_duration">
-      <term><varname>log_duration</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>log_duration</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Causes the duration of every completed statement to be logged.
-        The default is <literal>off</>.
-        Only superusers can change this setting.
-       </para>
-
-       <para>
-        For clients using extended query protocol, durations of the Parse,
-        Bind, and Execute steps are logged independently.
-       </para>
-
-       <note>
-        <para>
-         The difference between setting this option and setting
-         <xref linkend="guc-log-min-duration-statement"> to zero is that
-         exceeding <varname>log_min_duration_statement</> forces the text of
-         the query to be logged, but this option doesn't.  Thus, if
-         <varname>log_duration</> is <literal>on</> and
-         <varname>log_min_duration_statement</> has a positive value, all
-         durations are logged but the query text is included only for
-         statements exceeding the threshold.  This behavior can be useful for
-         gathering statistics in high-load installations.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-error-verbosity" xreflabel="log_error_verbosity">
-      <term><varname>log_error_verbosity</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>log_error_verbosity</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls the amount of detail written in the server log for each
-        message that is logged.  Valid values are <literal>TERSE</>,
-        <literal>DEFAULT</>, and <literal>VERBOSE</>, each adding more
-        fields to displayed messages.  <literal>TERSE</> excludes
-        the logging of <literal>DETAIL</>, <literal>HINT</>,
-        <literal>QUERY</>, and <literal>CONTEXT</> error information.
-        <literal>VERBOSE</> output includes the <symbol>SQLSTATE</> error
-        code (see also <xref linkend="errcodes-appendix">) and the source code file name, function name,
-        and line number that generated the error.
-        Only superusers can change this setting.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-hostname" xreflabel="log_hostname">
-      <term><varname>log_hostname</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>log_hostname</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        By default, connection log messages only show the IP address of the
-        connecting host. Turning this parameter on causes logging of the
-        host name as well.  Note that depending on your host name resolution
-        setup this might impose a non-negligible performance penalty.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-line-prefix" xreflabel="log_line_prefix">
-      <term><varname>log_line_prefix</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>log_line_prefix</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-         This is a <function>printf</>-style string that is output at the
-         beginning of each log line.
-         <literal>%</> characters begin <quote>escape sequences</>
-         that are replaced with status information as outlined below.
-         Unrecognized escapes are ignored. Other
-         characters are copied straight to the log line. Some escapes are
-         only recognized by session processes, and are ignored by
-         background processes such as the main server process.
-         This parameter can only be set in the <filename>postgresql.conf</>
-         file or on the server command line. The default is an empty string.
-
-         <informaltable>
-          <tgroup cols="3">
-           <thead>
-            <row>
-             <entry>Escape</entry>
-             <entry>Effect</entry>
-             <entry>Session only</entry>
-             </row>
-            </thead>
-           <tbody>
-            <row>
-             <entry><literal>%a</literal></entry>
-             <entry>Application name</entry>
-             <entry>yes</entry>
-            </row>
-            <row>
-             <entry><literal>%u</literal></entry>
-             <entry>User name</entry>
-             <entry>yes</entry>
-            </row>
-            <row>
-             <entry><literal>%d</literal></entry>
-             <entry>Database name</entry>
-             <entry>yes</entry>
-            </row>
-            <row>
-             <entry><literal>%r</literal></entry>
-             <entry>Remote host name or IP address, and remote port</entry>
-             <entry>yes</entry>
-            </row>
-            <row>
-             <entry><literal>%h</literal></entry>
-             <entry>Remote host name or IP address</entry>
-             <entry>yes</entry>
-            </row>
-            <row>
-             <entry><literal>%p</literal></entry>
-             <entry>Process ID</entry>
-             <entry>no</entry>
-            </row>
-            <row>
-             <entry><literal>%t</literal></entry>
-             <entry>Time stamp without milliseconds</entry>
-             <entry>no</entry>
-            </row>
-            <row>
-             <entry><literal>%m</literal></entry>
-             <entry>Time stamp with milliseconds</entry>
-             <entry>no</entry>
-            </row>
-            <row>
-             <entry><literal>%i</literal></entry>
-             <entry>Command tag: type of session's current command</entry>
-             <entry>yes</entry>
-            </row>
-            <row>
-             <entry><literal>%e</literal></entry>
-             <entry>SQLSTATE error code</entry>
-             <entry>no</entry>
-            </row>
-            <row>
-             <entry><literal>%c</literal></entry>
-             <entry>Session ID: see below</entry>
-             <entry>no</entry>
-            </row>
-            <row>
-             <entry><literal>%l</literal></entry>
-             <entry>Number of the log line for each session or process, starting at 1</entry>
-             <entry>no</entry>
-            </row>
-            <row>
-             <entry><literal>%s</literal></entry>
-             <entry>Process start time stamp</entry>
-             <entry>no</entry>
-            </row>
-            <row>
-             <entry><literal>%v</literal></entry>
-             <entry>Virtual transaction ID (backendID/localXID)</entry>
-             <entry>no</entry>
-            </row>
-            <row>
-             <entry><literal>%x</literal></entry>
-             <entry>Transaction ID (0 if none is assigned)</entry>
-             <entry>no</entry>
-            </row>
-            <row>
-             <entry><literal>%q</literal></entry>
-             <entry>Produces no output, but tells non-session
-             processes to stop at this point in the string; ignored by
-             session processes</entry>
-             <entry>no</entry>
-            </row>
-            <row>
-             <entry><literal>%%</literal></entry>
-             <entry>Literal <literal>%</></entry>
-             <entry>no</entry>
-            </row>
-           </tbody>
-          </tgroup>
-         </informaltable>
-
-         The <literal>%c</> escape prints a quasi-unique session identifier,
-         consisting of two 4-byte hexadecimal numbers (without leading zeros)
-         separated by a dot.  The numbers are the process start time and the
-         process ID, so <literal>%c</> can also be used as a space saving way
-         of printing those items.  For example, to generate the session
-         identifier from <literal>pg_stat_activity</>, use this query:
-<programlisting>
-SELECT to_hex(EXTRACT(EPOCH FROM backend_start)::integer) || '.' ||
-       to_hex(procpid)
-FROM pg_stat_activity;
-</programlisting>
-
-       </para>
-
-       <tip>
-        <para>
-         If you set a nonempty value for <varname>log_line_prefix</>,
-         you should usually make its last character be a space, to provide
-         visual separation from the rest of the log line.  A punctuation
-         character can be used too.
-        </para>
-       </tip>
-
-       <tip>
-        <para>
-         <application>Syslog</> produces its own
-         time stamp and process ID information, so you probably do not want to
-         include those escapes if you are logging to <application>syslog</>.
-        </para>
-       </tip>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-lock-waits" xreflabel="log_lock_waits">
-      <term><varname>log_lock_waits</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>log_lock_waits</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls whether a log message is produced when a session waits
-        longer than <xref linkend="guc-deadlock-timeout"> to acquire a
-        lock.  This is useful in determining if lock waits are causing
-        poor performance.  The default is <literal>off</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-statement" xreflabel="log_statement">
-      <term><varname>log_statement</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>log_statement</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls which SQL statements are logged. Valid values are
-        <literal>none</> (off), <literal>ddl</>, <literal>mod</>, and
-        <literal>all</> (all statements). <literal>ddl</> logs all data definition
-        statements, such as <command>CREATE</>, <command>ALTER</>, and
-        <command>DROP</> statements. <literal>mod</> logs all
-        <literal>ddl</> statements, plus data-modifying statements
-        such as <command>INSERT</>,
-        <command>UPDATE</>, <command>DELETE</>, <command>TRUNCATE</>,
-        and <command>COPY FROM</>.
-        <command>PREPARE</>, <command>EXECUTE</>, and
-        <command>EXPLAIN ANALYZE</> statements are also logged if their
-        contained command is of an appropriate type.  For clients using
-        extended query protocol, logging occurs when an Execute message
-        is received, and values of the Bind parameters are included
-        (with any embedded single-quote marks doubled).
-       </para>
-
-       <para>
-        The default is <literal>none</>. Only superusers can change this
-        setting.
-       </para>
-
-       <note>
-        <para>
-         Statements that contain simple syntax errors are not logged
-         even by the <varname>log_statement</> = <literal>all</> setting,
-         because the log message is emitted only after basic parsing has
-         been done to determine the statement type.  In the case of extended
-         query protocol, this setting likewise does not log statements that
-         fail before the Execute phase (i.e., during parse analysis or
-         planning).  Set <varname>log_min_error_statement</> to
-         <literal>ERROR</> (or lower) to log such statements.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-temp-files" xreflabel="log_temp_files">
-      <term><varname>log_temp_files</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>log_temp_files</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls logging of temporary file names and sizes.
-        Temporary files can be
-        created for sorts, hashes, and temporary query results.
-        A log entry is made for each temporary file when it is deleted.
-        A value of zero logs all temporary file information, while positive
-        values log only files whose size is greater than or equal to
-        the specified number of kilobytes.  The
-        default setting is -1, which disables such logging.
-        Only superusers can change this setting.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-timezone" xreflabel="log_timezone">
-      <term><varname>log_timezone</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>log_timezone</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the time zone used for timestamps written in the server log.
-        Unlike <xref linkend="guc-timezone">, this value is cluster-wide,
-        so that all sessions will report timestamps consistently.
-        If not explicitly set, the server initializes this variable to the
-        time zone specified by its system environment.  See <xref
-        linkend="datatype-timezones"> for more information.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-     <sect2 id="runtime-config-logging-csvlog">
-     <title>Using CSV-Format Log Output</title>
-&common;
-       <para>
-        Including <literal>csvlog</> in the <varname>log_destination</> list
-        provides a convenient way to import log files into a database table.
-        This option emits log lines in comma-separated-values
-        (<acronym>CSV</>) format,
-        with these columns:
-        time stamp with milliseconds,
-        user name,
-        database name,
-        process ID,
-        client host:port number,
-        session ID,
-        per-session line number,
-        command tag,
-        session start time,
-        virtual transaction ID,
-        regular transaction ID,
-        error severity,
-        SQLSTATE code,
-        error message,
-        error message detail,
-        hint,
-        internal query that led to the error (if any),
-        character count of the error position therein,
-        error context,
-        user query that led to the error (if any and enabled by
-        <varname>log_min_error_statement</>),
-        character count of the error position therein,
-<!## PG>
-        location of the error in the PostgreSQL source code
-<!## end>
-<!## XC>
-        location of the error in the Postgres-XC source code
-<!## end>
-<!## XL>
-        location of the error in the Postgres-XL source code
-<!## end>
-        (if <varname>log_error_verbosity</> is set to <literal>verbose</>),
-        and application name.
-        Here is a sample table definition for storing CSV-format log output:
-
-<programlisting>
-CREATE TABLE postgres_log
-(
-  log_time timestamp(3) with time zone,
-  user_name text,
-  database_name text,
-  process_id integer,
-  connection_from text,
-  session_id text,
-  session_line_num bigint,
-  command_tag text,
-  session_start_time timestamp with time zone,
-  virtual_transaction_id text,
-  transaction_id bigint,
-  error_severity text,
-  sql_state_code text,
-  message text,
-  detail text,
-  hint text,
-  internal_query text,
-  internal_query_pos integer,
-  context text,
-  query text,
-  query_pos integer,
-  location text,
-  application_name text,
-  PRIMARY KEY (session_id, session_line_num)
-);
-</programlisting>
-       </para>
-
-       <para>
-        To import a log file into this table, use the <command>COPY FROM</>
-        command:
-
-<programlisting>
-COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
-</programlisting>
-       </para>
-
-       <para>
-       There are a few things you need to do to simplify importing CSV log
-       files:
-
-       <orderedlist>
-         <listitem>
-           <para>
-            Set <varname>log_filename</varname> and
-            <varname>log_rotation_age</> to provide a consistent,
-            predictable naming scheme for your log files.  This lets you
-            predict what the file name will be and know when an individual log
-            file is complete and therefore ready to be imported.
-         </para>
-        </listitem>
-
-        <listitem>
-           <para>
-            Set <varname>log_rotation_size</varname> to 0 to disable
-            size-based log rotation, as it makes the log file name difficult
-            to predict.
-           </para>
-        </listitem>
-
-        <listitem>
-          <para>
-           Set <varname>log_truncate_on_rotation</varname> to <literal>on</> so
-           that old log data isn't mixed with the new in the same file.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-           The table definition above includes a primary key specification.
-           This is useful to protect against accidentally importing the same
-           information twice.  The <command>COPY</> command commits all of the
-           data it imports at one time, so any error will cause the entire
-           import to fail.  If you import a partial log file and later import
-           the file again when it is complete, the primary key violation will
-           cause the import to fail.  Wait until the log is complete and
-           closed before importing.  This procedure will also protect against
-           accidentally importing a partial line that hasn't been completely
-           written, which would also cause <command>COPY</> to fail.
-          </para>
-        </listitem>
-        </orderedlist>
-      </para>
-
-    </sect2>
-   </sect1>
-
-   <sect1 id="runtime-config-statistics">
-    <title>Run-time Statistics</title>
-
-    <sect2 id="runtime-config-statistics-collector">
-     <title>Query and Index Statistics Collector</title>
-&common;
-     <para>
-      These parameters control server-wide statistics collection features.
-      When statistics collection is enabled, the data that is produced can be
-      accessed via the <structname>pg_stat</structname> and
-      <structname>pg_statio</structname> family of system views.
-      Refer to <xref linkend="monitoring"> for more information.
-     </para>
-
-     <variablelist>
-
-     <varlistentry id="guc-track-activities" xreflabel="track_activities">
-      <term><varname>track_activities</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>track_activities</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables the collection of information on the currently
-        executing command of each session, along with the time when
-        that command began execution. This parameter is on by
-        default. Note that even when enabled, this information is not
-        visible to all users, only to superusers and the user owning
-        the session being reported on, so it should not represent a
-        security risk.
-        Only superusers can change this setting.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-track-activity-query-size" xreflabel="track_activity_query_size">
-      <term><varname>track_activity_query_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>track_activity_query_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-       Specifies the number of bytes reserved to track the currently
-       executing command for each active session, for the
-       <structname>pg_stat_activity</>.<structfield>current_query</> field.
-       The default value is 1024. This parameter can only be set at server
-       start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-track-counts" xreflabel="track_counts">
-      <term><varname>track_counts</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>track_counts</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables collection of statistics on database activity.
-        This parameter is on by default, because the autovacuum
-        daemon needs the collected information.
-        Only superusers can change this setting.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-track-functions" xreflabel="track_functions">
-      <term><varname>track_functions</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>track_functions</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables tracking of function call counts and time used. Specify
-        <literal>pl</literal> to track only procedural-language functions,
-        <literal>all</literal> to also track SQL and C language functions.
-        The default is <literal>none</literal>, which disables function
-        statistics tracking.  Only superusers can change this setting.
-       </para>
-
-       <note>
-        <para>
-         SQL-language functions that are simple enough to be <quote>inlined</>
-         into the calling query will not be tracked, regardless of this
-         setting.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-update-process-title" xreflabel="update_process_title">
-      <term><varname>update_process_title</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>update_process_title</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables updating of the process title every time a new SQL command
-        is received by the server.  The process title is typically viewed
-        by the <command>ps</> command,
-        or in Windows by using the <application>Process Explorer</>.
-        Only superusers can change this setting.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-stats-temp-directory" xreflabel="stats_temp_directory">
-      <term><varname>stats_temp_directory</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>stats_temp_directory</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the directory to store temporary statistics data in. This can be
-        a path relative to the data directory or an absolute path. The default
-        is <filename>pg_stat_tmp</filename>. Pointing this at a RAM-based
-        file system will decrease physical I/O requirements and can lead to
-        improved performance.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-
-    <sect2 id="runtime-config-statistics-monitor">
-     <title>Statistics Monitoring</title>
-&common;
-
-     <variablelist>
-
-     <varlistentry>
-      <term><varname>log_statement_stats</varname> (<type>boolean</type>)</term>
-      <term><varname>log_parser_stats</varname> (<type>boolean</type>)</term>
-      <term><varname>log_planner_stats</varname> (<type>boolean</type>)</term>
-      <term><varname>log_executor_stats</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>log_statement_stats</> configuration parameter</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>log_parser_stats</> configuration parameter</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>log_planner_stats</> configuration parameter</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>log_executor_stats</> configuration parameter</primary>
-      </indexterm>
-
-      <listitem>
-       <para>
-        For each query, output performance statistics of the respective
-        module to the server log. This is a crude profiling
-        instrument, similar to the Unix <function>getrusage()</> operating
-        system facility.  <varname>log_statement_stats</varname> reports total
-        statement statistics, while the others report per-module statistics.
-        <varname>log_statement_stats</varname> cannot be enabled together with
-        any of the per-module options.  All of these options are disabled by
-        default.   Only superusers can change these settings.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-
-    </sect2>
-   </sect1>
-
-   <sect1 id="runtime-config-autovacuum">
-    <title>Automatic Vacuuming</title>
-
-    <indexterm>
-     <primary>autovacuum</primary>
-     <secondary>configuration parameters</secondary>
-    </indexterm>
-&common;
-     <para>
-      These settings control the behavior of the <firstterm>autovacuum</>
-      feature.  Refer to <xref linkend="autovacuum"> for
-      more information.
-     </para>
-
-    <variablelist>
-
-     <varlistentry id="guc-autovacuum" xreflabel="autovacuum">
-      <term><varname>autovacuum</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>autovacuum</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls whether the server should run the
-        autovacuum launcher daemon.  This is on by default; however,
-        <xref linkend="guc-track-counts"> must also be enabled for
-        autovacuum to work.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-       <para>
-        Note that even when this parameter is disabled, the system
-        will launch autovacuum processes if necessary to
-        prevent transaction ID wraparound.  See <xref
-        linkend="vacuum-for-wraparound"> for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-log-autovacuum-min-duration" xreflabel="log_autovacuum_min_duration">
-      <term><varname>log_autovacuum_min_duration</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>log_autovacuum_min_duration</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Causes each action executed by autovacuum to be logged if it ran for at
-        least the specified number of milliseconds.  Setting this to zero logs
-        all autovacuum actions. Minus-one (the default) disables logging
-        autovacuum actions.  For example, if you set this to
-        <literal>250ms</literal> then all automatic vacuums and analyzes that run
-        250ms or longer will be logged.  In addition, when this parameter is
-        set to any value other than <literal>-1</literal>, a message will be
-        logged if an autovacuum action is skipped due to the existence of a
-        conflicting lock.  Enabling this parameter can be helpful
-        in tracking autovacuum activity.  This setting can only be set in
-        the <filename>postgresql.conf</> file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-autovacuum-max-workers" xreflabel="autovacuum_max_workers">
-      <term><varname>autovacuum_max_workers</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>autovacuum_max_workers</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the maximum number of autovacuum processes (other than the
-        autovacuum launcher) which may be running at any one time.  The default
-        is three.  This parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-autovacuum-naptime" xreflabel="autovacuum_naptime">
-      <term><varname>autovacuum_naptime</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>autovacuum_naptime</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the minimum delay between autovacuum runs on any given
-        database.  In each round the daemon examines the
-        database and issues <command>VACUUM</> and <command>ANALYZE</> commands
-        as needed for tables in that database.  The delay is measured
-        in seconds, and the default is one minute (<literal>1min</>).
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-autovacuum-vacuum-threshold" xreflabel="autovacuum_vacuum_threshold">
-      <term><varname>autovacuum_vacuum_threshold</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>autovacuum_vacuum_threshold</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the minimum number of updated or deleted tuples needed
-        to trigger a <command>VACUUM</> in any one table.
-        The default is 50 tuples.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-        This setting can be overridden for individual tables by
-        changing storage parameters.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-autovacuum-analyze-threshold" xreflabel="autovacuum_analyze_threshold">
-      <term><varname>autovacuum_analyze_threshold</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>autovacuum_analyze_threshold</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the minimum number of inserted, updated or deleted tuples
-        needed to trigger an <command>ANALYZE</> in any one table.
-        The default is 50 tuples.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-        This setting can be overridden for individual tables by
-        changing storage parameters.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-autovacuum-vacuum-scale-factor" xreflabel="autovacuum_vacuum_scale_factor">
-      <term><varname>autovacuum_vacuum_scale_factor</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>autovacuum_vacuum_scale_factor</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies a fraction of the table size to add to
-        <varname>autovacuum_vacuum_threshold</varname>
-        when deciding whether to trigger a <command>VACUUM</>.
-        The default is 0.2 (20% of table size).
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-        This setting can be overridden for individual tables by
-        changing storage parameters.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-autovacuum-analyze-scale-factor" xreflabel="autovacuum_analyze_scale_factor">
-      <term><varname>autovacuum_analyze_scale_factor</varname> (<type>floating point</type>)</term>
-      <indexterm>
-       <primary><varname>autovacuum_analyze_scale_factor</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies a fraction of the table size to add to
-        <varname>autovacuum_analyze_threshold</varname>
-        when deciding whether to trigger an <command>ANALYZE</>.
-        The default is 0.1 (10% of table size).
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-        This setting can be overridden for individual tables by
-        changing storage parameters.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-autovacuum-freeze-max-age" xreflabel="autovacuum_freeze_max_age">
-      <term><varname>autovacuum_freeze_max_age</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>autovacuum_freeze_max_age</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the maximum age (in transactions) that a table's
-        <structname>pg_class</>.<structfield>relfrozenxid</> field can
-        attain before a <command>VACUUM</> operation is forced
-        to prevent transaction ID wraparound within the table.
-        Note that the system will launch autovacuum processes to
-        prevent wraparound even when autovacuum is otherwise disabled.
-       </para>
-
-       <para>
-        Vacuum also allows removal of old files from the
-        <filename>pg_clog</> subdirectory, which is why the default
-        is a relatively low 200 million transactions.
-        This parameter can only be set at server start, but the setting
-        can be reduced for individual tables by
-        changing storage parameters.
-        For more information see <xref linkend="vacuum-for-wraparound">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-autovacuum-vacuum-cost-delay" xreflabel="autovacuum_vacuum_cost_delay">
-      <term><varname>autovacuum_vacuum_cost_delay</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>autovacuum_vacuum_cost_delay</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the cost delay value that will be used in automatic
-        <command>VACUUM</> operations.  If -1 is specified, the regular
-        <xref linkend="guc-vacuum-cost-delay"> value will be used.
-        The default value is 20 milliseconds.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-        This setting can be overridden for individual tables by
-        changing storage parameters.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-autovacuum-vacuum-cost-limit" xreflabel="autovacuum_vacuum_cost_limit">
-      <term><varname>autovacuum_vacuum_cost_limit</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>autovacuum_vacuum_cost_limit</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the cost limit value that will be used in automatic
-        <command>VACUUM</> operations.  If -1 is specified (which is the
-        default), the regular
-        <xref linkend="guc-vacuum-cost-limit"> value will be used.  Note that
-        the value is distributed proportionally among the running autovacuum
-        workers, if there is more than one, so that the sum of the limits of
-        each worker never exceeds the limit on this variable.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-        This setting can be overridden for individual tables by
-        changing storage parameters.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </sect1>
-
-   <sect1 id="runtime-config-client">
-    <title>Client Connection Defaults</title>
-
-    <sect2 id="runtime-config-client-statement">
-     <title>Statement Behavior</title>
-     <variablelist>
-&common;
-
-     <varlistentry id="guc-search-path" xreflabel="search_path">
-      <term><varname>search_path</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>search_path</> configuration parameter</primary>
-      </indexterm>
-      <indexterm><primary>path</><secondary>for schemas</></>
-      <listitem>
-       <para>
-        This variable specifies the order in which schemas are searched
-        when an object (table, data type, function, etc.) is referenced by a
-        simple name with no schema specified.  When there are objects of
-        identical names in different schemas, the one found first
-        in the search path is used.  An object that is not in any of the
-        schemas in the search path can only be referenced by specifying
-        its containing schema with a qualified (dotted) name.
-       </para>
-
-       <para>
-        The value for <varname>search_path</varname> must be a comma-separated
-        list of schema names.  If one of the list items is
-        the special value <literal>$user</literal>, then the schema
-        having the name returned by <function>SESSION_USER</> is substituted, if there
-        is such a schema.  (If not, <literal>$user</literal> is ignored.)
-       </para>
-
-       <para>
-        The system catalog schema, <literal>pg_catalog</>, is always
-        searched, whether it is mentioned in the path or not.  If it is
-        mentioned in the path then it will be searched in the specified
-        order.  If <literal>pg_catalog</> is not in the path then it will
-        be searched <emphasis>before</> searching any of the path items.
-       </para>
-
-       <para>
-        Likewise, the current session's temporary-table schema,
-        <literal>pg_temp_<replaceable>nnn</></>, is always searched if it
-        exists.  It can be explicitly listed in the path by using the
-        alias <literal>pg_temp</>.  If it is not listed in the path then
-        it is searched first (even before <literal>pg_catalog</>).  However,
-        the temporary schema is only searched for relation (table, view,
-        sequence, etc) and data type names.  It is never searched for
-        function or operator names.
-       </para>
-
-       <para>
-        When objects are created without specifying a particular target
-        schema, they will be placed in the first schema listed
-        in the search path.  An error is reported if the search path is
-        empty.
-       </para>
-
-       <para>
-        The default value for this parameter is
-        <literal>'"$user", public'</literal> (where the second part will be
-        ignored if there is no schema named <literal>public</>).
-        This supports shared use of a database (where no users
-        have private schemas, and all share use of <literal>public</>),
-        private per-user schemas, and combinations of these.  Other
-        effects can be obtained by altering the default search path
-        setting, either globally or per-user.
-       </para>
-
-       <para>
-        The current effective value of the search path can be examined
-        via the <acronym>SQL</acronym> function
-        <function>current_schemas()</>.  This is not quite the same as
-        examining the value of <varname>search_path</varname>, since
-        <function>current_schemas()</> shows how the items
-        appearing in <varname>search_path</varname> were resolved.
-       </para>
-
-       <para>
-        For more information on schema handling, see <xref linkend="ddl-schemas">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-default-tablespace" xreflabel="default_tablespace">
-      <term><varname>default_tablespace</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>default_tablespace</> configuration parameter</primary>
-      </indexterm>
-      <indexterm><primary>tablespace</><secondary>default</></>
-      <listitem>
-       <para>
-        This variable specifies the default tablespace in which to create
-        objects (tables and indexes) when a <command>CREATE</> command does
-        not explicitly specify a tablespace.
-       </para>
-
-       <para>
-        The value is either the name of a tablespace, or an empty string
-        to specify using the default tablespace of the current database.
-        If the value does not match the name of any existing tablespace,
-<!## PG>
-        <productname>PostgreSQL</> will automatically use the default
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</> will automatically use the default
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</> will automatically use the default
-<!## end>
-        tablespace of the current database.  If a nondefault tablespace
-        is specified, the user must have <literal>CREATE</> privilege
-        for it, or creation attempts will fail.
-       </para>
-
-       <para>
-        This variable is not used for temporary tables; for them,
-        <xref linkend="guc-temp-tablespaces"> is consulted instead.
-       </para>
-
-       <para>
-        This variable is also not used when creating databases.
-        By default, a new database inherits its tablespace setting from
-        the template database it is copied from.
-       </para>
-
-       <para>
-        For more information on tablespaces,
-        see <xref linkend="manage-ag-tablespaces">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-temp-tablespaces" xreflabel="temp_tablespaces">
-      <term><varname>temp_tablespaces</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>temp_tablespaces</> configuration parameter</primary>
-      </indexterm>
-      <indexterm><primary>tablespace</><secondary>temporary</></>
-      <listitem>
-       <para>
-        This variable specifies tablespaces in which to create temporary
-        objects (temp tables and indexes on temp tables) when a
-        <command>CREATE</> command does not explicitly specify a tablespace.
-        Temporary files for purposes such as sorting large data sets
-        are also created in these tablespaces.
-       </para>
-
-       <para>
-        The value is a list of names of tablespaces.  When there is more than
-<!## PG>
-        one name in the list, <productname>PostgreSQL</> chooses a random
-<!## end>
-<!## XC>
-        one name in the list, <productname>Postgres-XC</> chooses a random
-<!## end>
-<!## XL>
-        one name in the list, <productname>Postgres-XL</> chooses a random
-<!## end>
-        member of the list each time a temporary object is to be created;
-        except that within a transaction, successively created temporary
-        objects are placed in successive tablespaces from the list.
-        If the selected element of the list is an empty string,
-<!## PG>
-        <productname>PostgreSQL</> will automatically use the default
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</> will automatically use the default
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</> will automatically use the default
-<!## end>
-        tablespace of the current database instead.
-       </para>
-
-       <para>
-        When <varname>temp_tablespaces</> is set interactively, specifying a
-        nonexistent tablespace is an error, as is specifying a tablespace for
-        which the user does not have <literal>CREATE</> privilege.  However,
-        when using a previously set value, nonexistent tablespaces are
-        ignored, as are tablespaces for which the user lacks
-        <literal>CREATE</> privilege.  In particular, this rule applies when
-        using a value set in <filename>postgresql.conf</>.
-       </para>
-
-       <para>
-        The default value is an empty string, which results in all temporary
-        objects being created in the default tablespace of the current
-        database.
-       </para>
-
-       <para>
-        See also <xref linkend="guc-default-tablespace">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-check-function-bodies" xreflabel="check_function_bodies">
-      <term><varname>check_function_bodies</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>check_function_bodies</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This parameter is normally on. When set to <literal>off</>, it
-        disables validation of the function body string during <xref
-        linkend="sql-createfunction">. Disabling validation is
-        occasionally useful to avoid problems such as forward references
-        when restoring function definitions from a dump.
-<!## XC>
-        <note>
-         <para>
-          In <productname>Postgres-XC</> setting <varname>check_function_bodies</varname>
-          to <literal>off</> is not recommended. If SQL functions are created after setting
-          <varname>check_function_bodies</varname> to <literal>off</>, the behaviour of the
-          function when executed is un-defined.
-         </para>
-        </note>
-<!## end>
-<!## XL>
-        <note>
-         <para>
-          In <productname>Postgres-XL</> setting <varname>check_function_bodies</varname>
-          to <literal>off</> is not recommended. If SQL functions are created after setting
-          <varname>check_function_bodies</varname> to <literal>off</>, the behaviour of the
-          function when executed is un-defined.
-         </para>
-        </note>
-<!## end>
-
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-default-transaction-isolation" xreflabel="default_transaction_isolation">
-      <indexterm>
-       <primary>transaction isolation level</primary>
-       <secondary>setting default</secondary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>default_transaction_isolation</> configuration parameter</primary>
-      </indexterm>
-      <term><varname>default_transaction_isolation</varname> (<type>enum</type>)</term>
-      <listitem>
-       <para>
-        Each SQL transaction has an isolation level, which can be
-        either <quote>read uncommitted</quote>, <quote>read
-        committed</quote>, <quote>repeatable read</quote>, or
-        <quote>serializable</quote>.  This parameter controls the
-        default isolation level of each new transaction. The default
-        is <quote>read committed</quote>.
-       </para>
-
-       <para>
-        Consult <xref linkend="mvcc"> and <xref
-        linkend="sql-set-transaction"> for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-default-transaction-read-only" xreflabel="default_transaction_read_only">
-      <indexterm>
-       <primary>read-only transaction</primary>
-       <secondary>setting default</secondary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>default_transaction_read_only</> configuration parameter</primary>
-      </indexterm>
-
-      <term><varname>default_transaction_read_only</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        A read-only SQL transaction cannot alter non-temporary tables.
-        This parameter controls the default read-only status of each new
-        transaction. The default is <literal>off</> (read/write).
-       </para>
-
-       <para>
-        Consult <xref linkend="sql-set-transaction"> for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-default-transaction-deferrable" xreflabel="default_transaction_deferrable">
-      <indexterm>
-       <primary>deferrable transaction</primary>
-       <secondary>setting default</secondary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>default_transaction_deferrable</> configuration parameter</primary>
-      </indexterm>
-
-      <term><varname>default_transaction_deferrable</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        When running at the <literal>serializable</> isolation level,
-        a deferrable read-only SQL transaction may be delayed before
-        it is allowed to proceed.  However, once it begins executing
-        it does not incur any of the overhead required to ensure
-        serializability; so serialization code will have no reason to
-        force it to abort because of concurrent updates, making this
-        option suitable for long-running read-only transactions.
-        </para>
-
-        <para>
-        This parameter controls the default deferrable status of each
-        new transaction.  It currently has no effect on read-write
-        transactions or those operating at isolation levels lower
-        than <literal>serializable</>. The default is <literal>off</>.
-       </para>
-
-       <para>
-        Consult <xref linkend="sql-set-transaction"> for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry id="guc-session-replication-role" xreflabel="session_replication_role">
-      <term><varname>session_replication_role</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>session_replication_role</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Controls firing of replication-related triggers and rules for the
-        current session.  Setting this variable requires
-        superuser privilege and results in discarding any previously cached
-        query plans.  Possible values are <literal>origin</> (the default),
-        <literal>replica</> and <literal>local</>.
-        See <xref linkend="sql-altertable"> for
-        more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-statement-timeout" xreflabel="statement_timeout">
-      <term><varname>statement_timeout</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>statement_timeout</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Abort any statement that takes over the specified number of
-        milliseconds, starting from the time the command arrives at the server
-        from the client.  If <varname>log_min_error_statement</> is set to
-        <literal>ERROR</> or lower, the statement that timed out will also be
-        logged.  A value of zero (the default) turns this off.
-       </para>
-
-       <para>
-        Setting <varname>statement_timeout</> in
-        <filename>postgresql.conf</> is not recommended because it
-        affects all sessions.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-vacuum-freeze-table-age" xreflabel="vacuum_freeze_table_age">
-      <term><varname>vacuum_freeze_table_age</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>vacuum_freeze_table_age</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        <command>VACUUM</> performs a whole-table scan if the table's
-        <structname>pg_class</>.<structfield>relfrozenxid</> field has reached
-        the age specified by this setting.  The default is 150 million
-        transactions.  Although users can set this value anywhere from zero to
-        one billion, <command>VACUUM</> will silently limit the effective value
-        to 95% of <xref linkend="guc-autovacuum-freeze-max-age">, so that a
-        periodical manual <command>VACUUM</> has a chance to run before an
-        anti-wraparound autovacuum is launched for the table. For more
-        information see
-        <xref linkend="vacuum-for-wraparound">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-vacuum-freeze-min-age" xreflabel="vacuum_freeze_min_age">
-      <term><varname>vacuum_freeze_min_age</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>vacuum_freeze_min_age</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the cutoff age (in transactions) that <command>VACUUM</>
-        should use to decide whether to replace transaction IDs with
-        <literal>FrozenXID</> while scanning a table.
-        The default is 50 million transactions.  Although
-        users can set this value anywhere from zero to one billion,
-        <command>VACUUM</> will silently limit the effective value to half
-        the value of <xref linkend="guc-autovacuum-freeze-max-age">, so
-        that there is not an unreasonably short time between forced
-        autovacuums.  For more information see <xref
-        linkend="vacuum-for-wraparound">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-bytea-output" xreflabel="bytea_output">
-      <term><varname>bytea_output</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>bytea_output</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the output format for values of type <type>bytea</type>.
-        Valid values are <literal>hex</literal> (the default)
-<!## PG>
-        and <literal>escape</literal> (the traditional PostgreSQL
-<!## end>
-<!## XC>
-        and <literal>escape</literal> (the traditional Postgres-XC
-<!## end>
-<!## XL>
-        and <literal>escape</literal> (the traditional Postgres-XL
-<!## end>
-        format).  See <xref linkend="datatype-binary"> for more
-        information.  The <type>bytea</type> type always
-        accepts both formats on input, regardless of this setting.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-xmlbinary" xreflabel="xmlbinary">
-      <term><varname>xmlbinary</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>xmlbinary</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets how binary values are to be encoded in XML.  This applies
-        for example when <type>bytea</type> values are converted to
-        XML by the functions <function>xmlelement</function> or
-        <function>xmlforest</function>.  Possible values are
-        <literal>base64</literal> and <literal>hex</literal>, which
-        are both defined in the XML Schema standard.  The default is
-        <literal>base64</literal>.  For further information about
-        XML-related functions, see <xref linkend="functions-xml">.
-       </para>
-
-       <para>
-        The actual choice here is mostly a matter of taste,
-        constrained only by possible restrictions in client
-        applications.  Both methods support all possible values,
-        although the hex encoding will be somewhat larger than the
-        base64 encoding.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-xmloption" xreflabel="xmloption">
-      <term><varname>xmloption</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>xmloption</> configuration parameter</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>SET XML OPTION</></primary>
-      </indexterm>
-      <indexterm>
-       <primary>XML option</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets whether <literal>DOCUMENT</literal> or
-        <literal>CONTENT</literal> is implicit when converting between
-        XML and character string values.  See <xref
-        linkend="datatype-xml"> for a description of this.  Valid
-        values are <literal>DOCUMENT</literal> and
-        <literal>CONTENT</literal>.  The default is
-        <literal>CONTENT</literal>.
-       </para>
-
-       <para>
-        According to the SQL standard, the command to set this option is
-<synopsis>
-SET XML OPTION { DOCUMENT | CONTENT };
-</synopsis>
-<!## PG>
-        This syntax is also available in PostgreSQL.
-<!## end>
-<!## XC>
-        This syntax is also available in Postgres-XC.
-<!## end>
-<!## XL>
-        This syntax is also available in Postgres-XL.
-<!## end>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-     <sect2 id="runtime-config-client-format">
-     <title>Locale and Formatting</title>
-&common;
-
-     <variablelist>
-
-     <varlistentry id="guc-datestyle" xreflabel="DateStyle">
-      <term><varname>DateStyle</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>DateStyle</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the display format for date and time values, as well as the
-        rules for interpreting ambiguous date input values. For
-        historical reasons, this variable contains two independent
-        components: the output format specification (<literal>ISO</>,
-        <literal>Postgres</>, <literal>SQL</>, or <literal>German</>)
-        and the input/output specification for year/month/day ordering
-        (<literal>DMY</>, <literal>MDY</>, or <literal>YMD</>). These
-        can be set separately or together. The keywords <literal>Euro</>
-        and <literal>European</> are synonyms for <literal>DMY</>; the
-        keywords <literal>US</>, <literal>NonEuro</>, and
-        <literal>NonEuropean</> are synonyms for <literal>MDY</>. See
-        <xref linkend="datatype-datetime"> for more information. The
-        built-in default is <literal>ISO, MDY</>, but
-        <application>initdb</application> will initialize the
-        configuration file with a setting that corresponds to the
-        behavior of the chosen <varname>lc_time</varname> locale.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-intervalstyle" xreflabel="IntervalStyle">
-      <term><varname>IntervalStyle</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>IntervalStyle</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the display format for interval values.
-        The value <literal>sql_standard</> will produce
-        output matching <acronym>SQL</acronym> standard interval literals.
-        The value <literal>postgres</> (which is the default) will produce
-        output matching <productname>PostgreSQL</> releases prior to 8.4
-        when the <xref linkend="guc-datestyle">
-        parameter was set to <literal>ISO</>.
-        The value <literal>postgres_verbose</> will produce output
-        matching <productname>PostgreSQL</> releases prior to 8.4
-        when the <varname>DateStyle</>
-        parameter was set to non-<literal>ISO</> output.
-        The value <literal>iso_8601</> will produce output matching the time
-        interval <quote>format with designators</> defined in section
-        4.4.3.2 of ISO 8601.
-       </para>
-       <para>
-        The <varname>IntervalStyle</> parameter also affects the
-        interpretation of ambiguous interval input.  See
-        <xref linkend="datatype-interval-input"> for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-timezone" xreflabel="timezone">
-      <term><varname>timezone</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>timezone</> configuration parameter</primary>
-      </indexterm>
-      <indexterm><primary>time zone</></>
-      <listitem>
-       <para>
-        Sets the time zone for displaying and interpreting time stamps.
-        If not explicitly set, the server initializes this variable to the
-        time zone specified by its system environment.  See <xref
-        linkend="datatype-timezones"> for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-timezone-abbreviations" xreflabel="timezone_abbreviations">
-      <term><varname>timezone_abbreviations</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>timezone_abbreviations</> configuration parameter</primary>
-      </indexterm>
-      <indexterm><primary>time zone names</></>
-      <listitem>
-       <para>
-        Sets the collection of time zone abbreviations that will be accepted
-        by the server for datetime input.  The default is <literal>'Default'</>,
-        which is a collection that works in most of the world; there are
-        also <literal>'Australia'</literal> and <literal>'India'</literal>, and other collections can be defined
-        for a particular installation.  See <xref
-        linkend="datetime-appendix"> for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-extra-float-digits" xreflabel="extra_float_digits">
-      <indexterm>
-       <primary>significant digits</primary>
-      </indexterm>
-      <indexterm>
-       <primary>floating-point</primary>
-       <secondary>display</secondary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>extra_float_digits</> configuration parameter</primary>
-      </indexterm>
-
-      <term><varname>extra_float_digits</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        This parameter adjusts the number of digits displayed for
-        floating-point values, including <type>float4</>, <type>float8</>,
-        and geometric data types.  The parameter value is added to the
-        standard number of digits (<literal>FLT_DIG</> or <literal>DBL_DIG</>
-        as appropriate).  The value can be set as high as 3, to include
-        partially-significant digits; this is especially useful for dumping
-        float data that needs to be restored exactly.  Or it can be set
-        negative to suppress unwanted digits.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-client-encoding" xreflabel="client_encoding">
-      <term><varname>client_encoding</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>client_encoding</> configuration parameter</primary>
-      </indexterm>
-      <indexterm><primary>character set</></>
-      <listitem>
-       <para>
-        Sets the client-side encoding (character set).
-        The default is to use the database encoding.
-        The character sets supported by the <productname>PostgreSQL</productname>
-        server are described in <xref linkend="multibyte-charset-supported">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-lc-messages" xreflabel="lc_messages">
-      <term><varname>lc_messages</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>lc_messages</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the language in which messages are displayed.  Acceptable
-        values are system-dependent; see <xref linkend="locale"> for
-        more information.  If this variable is set to the empty string
-        (which is the default) then the value is inherited from the
-        execution environment of the server in a system-dependent way.
-       </para>
-
-       <para>
-        On some systems, this locale category does not exist.  Setting
-        this variable will still work, but there will be no effect.
-        Also, there is a chance that no translated messages for the
-        desired language exist.  In that case you will continue to see
-        the English messages.
-       </para>
-
-       <para>
-        Only superusers can change this setting, because it affects the
-        messages sent to the server log as well as to the client, and
-        an improper value might obscure the readability of the server
-        logs.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-lc-monetary" xreflabel="lc_monetary">
-      <term><varname>lc_monetary</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>lc_monetary</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the locale to use for formatting monetary amounts, for
-        example with the <function>to_char</function> family of
-        functions.  Acceptable values are system-dependent; see <xref
-        linkend="locale"> for more information.  If this variable is
-        set to the empty string (which is the default) then the value
-        is inherited from the execution environment of the server in a
-        system-dependent way.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-lc-numeric" xreflabel="lc_numeric">
-      <term><varname>lc_numeric</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>lc_numeric</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the locale to use for formatting numbers, for example
-        with the <function>to_char</function> family of
-        functions. Acceptable values are system-dependent; see <xref
-        linkend="locale"> for more information.  If this variable is
-        set to the empty string (which is the default) then the value
-        is inherited from the execution environment of the server in a
-        system-dependent way.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-lc-time" xreflabel="lc_time">
-      <term><varname>lc_time</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>lc_time</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Sets the locale to use for formatting dates and times, for example
-        with the <function>to_char</function> family of
-        functions. Acceptable values are system-dependent; see <xref
-        linkend="locale"> for more information.  If this variable is
-        set to the empty string (which is the default) then the value
-        is inherited from the execution environment of the server in a
-        system-dependent way.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-default-text-search-config" xreflabel="default_text_search_config">
-      <term><varname>default_text_search_config</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>default_text_search_config</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Selects the text search configuration that is used by those variants
-        of the text search functions that do not have an explicit argument
-        specifying the configuration.
-        See <xref linkend="textsearch"> for further information.
-        The built-in default is <literal>pg_catalog.simple</>, but
-        <application>initdb</application> will initialize the
-        configuration file with a setting that corresponds to the
-        chosen <varname>lc_ctype</varname> locale, if a configuration
-        matching that locale can be identified.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-
-    </sect2>
-     <sect2 id="runtime-config-client-other">
-     <title>Other Defaults</title>
-&common;
-
-     <variablelist>
-
-     <varlistentry id="guc-dynamic-library-path" xreflabel="dynamic_library_path">
-      <term><varname>dynamic_library_path</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>dynamic_library_path</> configuration parameter</primary>
-      </indexterm>
-      <indexterm><primary>dynamic loading</></>
-      <listitem>
-       <para>
-        If a dynamically loadable module needs to be opened and the
-        file name specified in the <command>CREATE FUNCTION</command> or
-        <command>LOAD</command> command
-        does not have a directory component (i.e., the
-        name does not contain a slash), the system will search this
-        path for the required file.
-       </para>
-
-       <para>
-        The value for <varname>dynamic_library_path</varname> must be a
-        list of absolute directory paths separated by colons (or semi-colons
-        on Windows).  If a list element starts
-        with the special string <literal>$libdir</literal>, the
-<!## PG>
-        compiled-in <productname>PostgreSQL</productname> package
-<!## end>
-<!## XC>
-        compiled-in <productname>Postgres-XC</productname> package
-<!## end>
-<!## XL>
-        compiled-in <productname>Postgres-XL</productname> package
-<!## end>
-        library directory is substituted for <literal>$libdir</literal>; this
-        is where the modules provided by the standard
-<!## PG>
-        <productname>PostgreSQL</productname> distribution are installed.
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> distribution are installed.
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> distribution are installed.
-<!## end>
-        (Use <literal>pg_config --pkglibdir</literal> to find out the name of
-        this directory.) For example:
-<programlisting>
-dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
-</programlisting>
-        or, in a Windows environment:
-<programlisting>
-dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
-</programlisting>
-       </para>
-
-       <para>
-        The default value for this parameter is
-        <literal>'$libdir'</literal>. If the value is set to an empty
-        string, the automatic path search is turned off.
-       </para>
-
-       <para>
-        This parameter can be changed at run time by superusers, but a
-        setting done that way will only persist until the end of the
-        client connection, so this method should be reserved for
-        development purposes. The recommended way to set this parameter
-        is in the <filename>postgresql.conf</filename> configuration
-        file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-gin-fuzzy-search-limit" xreflabel="gin_fuzzy_search_limit">
-      <term><varname>gin_fuzzy_search_limit</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>gin_fuzzy_search_limit</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Soft upper limit of the size of the set returned by GIN index scans. For more
-        information see <xref linkend="gin-tips">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-local-preload-libraries" xreflabel="local_preload_libraries">
-      <term><varname>local_preload_libraries</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>local_preload_libraries</> configuration parameter</primary>
-      </indexterm>
-      <indexterm>
-       <primary><filename>$libdir/plugins</></primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This variable specifies one or more shared libraries that are
-        to be preloaded at connection start.  If more than one library
-        is to be loaded, separate their names with commas.  All library
-        names are converted to lower case unless double-quoted.
-        This parameter cannot be changed after the start of a particular
-        session.
-       </para>
-
-       <para>
-        Because this is not a superuser-only option, the libraries
-        that can be loaded are restricted to those appearing in the
-        <filename>plugins</> subdirectory of the installation's
-        standard library directory.  (It is the database administrator's
-        responsibility to ensure that only <quote>safe</> libraries
-        are installed there.)  Entries in <varname>local_preload_libraries</>
-        can specify this directory explicitly, for example
-        <literal>$libdir/plugins/mylib</literal>, or just specify
-        the library name &mdash; <literal>mylib</literal> would have
-        the same effect as <literal>$libdir/plugins/mylib</literal>.
-       </para>
-
-       <para>
-        Unlike <varname>local_preload_libraries</>, there is no
-        performance advantage to loading a library at session
-        start rather than when it is first used.  Rather, the intent of
-        this feature is to allow debugging or performance-measurement
-        libraries to be loaded into specific sessions without an explicit
-        <command>LOAD</> command being given.  For example, debugging could
-        be enabled for all sessions under a given user name by setting
-        this parameter with <command>ALTER ROLE SET</>.
-       </para>
-
-       <para>
-        If a specified library is not found,
-        the connection attempt will fail.
-       </para>
-
-       <para>
-        Every  PostgreSQL-supported library has a <quote>magic
-        block</> that is checked to guarantee compatibility.
-        For this reason, non-PostgreSQL libraries cannot be
-        loaded in this way.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-   </sect1>
-
-   <sect1 id="runtime-config-locks">
-    <title>Lock Management</title>
-&common;
-
-     <variablelist>
-
-     <varlistentry id="guc-deadlock-timeout" xreflabel="deadlock_timeout">
-      <indexterm>
-       <primary>deadlock</primary>
-       <secondary>timeout during</secondary>
-      </indexterm>
-      <indexterm>
-       <primary>timeout</primary>
-       <secondary>deadlock</secondary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>deadlock_timeout</> configuration parameter</primary>
-      </indexterm>
-
-      <term><varname>deadlock_timeout</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        This is the amount of time, in milliseconds, to wait on a lock
-        before checking to see if there is a deadlock condition. The
-        check for deadlock is relatively expensive, so the server doesn't run
-        it every time it waits for a lock. We optimistically assume
-        that deadlocks are not common in production applications and
-        just wait on the lock for a while before checking for a
-        deadlock. Increasing this value reduces the amount of time
-        wasted in needless deadlock checks, but slows down reporting of
-        real deadlock errors. The default is one second (<literal>1s</>),
-        which is probably about the smallest value you would want in
-        practice. On a heavily loaded server you might want to raise it.
-        Ideally the setting should exceed your typical transaction time,
-        so as to improve the odds that a lock will be released before
-        the waiter decides to check for deadlock.
-       </para>
-
-       <para>
-        When <xref linkend="guc-log-lock-waits"> is set,
-        this parameter also determines the length of time to wait before
-        a log message is issued about the lock wait.  If you are trying
-        to investigate locking delays you might want to set a shorter than
-        normal <varname>deadlock_timeout</varname>.
-       </para>
-<!## XC>
-&xconly;
-       <para>
-        <productname>Postgres-XC</> does not detect global deadlocks
-        where multiple node (Coordinators and/or Datanodes) are
-        involved.
-       </para>
-<!## end>
-<!## XL>
-&xlonly;
-       <para>
-        <productname>Postgres-XL</> does not detect global deadlocks
-        where multiple node (Coordinators and/or Datanodes) are
-        involved. To get around this it is recommended to set
-        <varname>statement_timeout</varname> to cause those statements to
-        fail in a normal processing environment. If however, it is a reporting
-        environment, you may want to set this higher globally, or just for
-        the session temporarily.
-       </para>
-<!## end>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-locks-per-transaction" xreflabel="max_locks_per_transaction">
-      <term><varname>max_locks_per_transaction</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_locks_per_transaction</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        The shared lock table tracks locks on
-        <varname>max_locks_per_transaction</varname> * (<xref
-        linkend="guc-max-connections"> + <xref
-        linkend="guc-max-prepared-transactions">) objects (e.g.,  tables);
-        hence, no more than this many distinct objects can be locked at
-        any one time.  This parameter controls the average number of object
-        locks allocated for each transaction;  individual transactions
-        can lock more objects as long as the locks of all transactions
-        fit in the lock table.  This is <emphasis>not</> the number of
-        rows that can be locked; that value is unlimited.  The default,
-        64, has historically proven sufficient, but you might need to
-        raise this value if you have clients that touch many different
-        tables in a single transaction. This parameter can only be set at
-        server start.
-       </para>
-
-       <para>
-<!## PG>
-        Increasing this parameter might cause <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-        Increasing this parameter might cause <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-        Increasing this parameter might cause <productname>Postgres-XL</>
-<!## end>
-        to request more <systemitem class="osname">System V</> shared
-        memory than your operating system's default configuration
-        allows. See <xref linkend="sysvipc"> for information on how to
-        adjust those parameters, if necessary.
-       </para>
-
-       <para>
-        When running a standby server, you must set this parameter to the
-        same or higher value than on the master server. Otherwise, queries
-        will not be allowed in the standby server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-pred-locks-per-transaction" xreflabel="max_pred_locks_per_transaction">
-      <term><varname>max_pred_locks_per_transaction</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_pred_locks_per_transaction</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        The shared predicate lock table tracks locks on
-        <varname>max_pred_locks_per_transaction</varname> * (<xref
-        linkend="guc-max-connections"> + <xref
-        linkend="guc-max-prepared-transactions">) objects (e.g., tables);
-        hence, no more than this many distinct objects can be locked at
-        any one time.  This parameter controls the average number of object
-        locks allocated for each transaction;  individual transactions
-        can lock more objects as long as the locks of all transactions
-        fit in the lock table.  This is <emphasis>not</> the number of
-        rows that can be locked; that value is unlimited.  The default,
-        64, has generally been sufficient in testing, but you might need to
-        raise this value if you have clients that touch many different
-        tables in a single serializable transaction. This parameter can
-        only be set at server start.
-       </para>
-
-       <para>
-        Increasing this parameter might cause <productname>PostgreSQL</>
-        to request more <systemitem class="osname">System V</> shared
-        memory than your operating system's default configuration
-        allows. See <xref linkend="sysvipc"> for information on how to
-        adjust those parameters, if necessary.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-   </sect1>
-
-   <sect1 id="runtime-config-compatible">
-    <title>Version and Platform Compatibility</title>
-
-    <sect2 id="runtime-config-compatible-version">
-     <title>Previous PostgreSQL Versions</title>
-&common;
-     <variablelist>
-
-     <varlistentry id="guc-array-nulls" xreflabel="array_nulls">
-      <term><varname>array_nulls</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>array_nulls</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This controls whether the array input parser recognizes
-        unquoted <literal>NULL</> as specifying a null array element.
-        By default, this is <literal>on</>, allowing array values containing
-        null values to be entered.  However, <productname>PostgreSQL</> versions
-        before 8.2 did not support null values in arrays, and therefore would
-        treat <literal>NULL</> as specifying a normal array element with
-        the string value <quote>NULL</>.  For backward compatibility with
-        applications that require the old behavior, this variable can be
-        turned <literal>off</>.
-       </para>
-
-       <para>
-        Note that it is possible to create array values containing null values
-        even when this variable is <literal>off</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-backslash-quote" xreflabel="backslash_quote">
-      <term><varname>backslash_quote</varname> (<type>enum</type>)</term>
-      <indexterm><primary>strings</><secondary>backslash quotes</></>
-      <indexterm>
-       <primary><varname>backslash_quote</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This controls whether a quote mark can be represented by
-        <literal>\'</> in a string literal.  The preferred, SQL-standard way
-        to represent a quote mark is by doubling it (<literal>''</>) but
-<!## PG>
-        <productname>PostgreSQL</> has historically also accepted
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</> has historically also accepted
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</> has historically also accepted
-<!## end>
-        <literal>\'</>. However, use of <literal>\'</> creates security risks
-        because in some client character set encodings, there are multibyte
-        characters in which the last byte is numerically equivalent to ASCII
-        <literal>\</>.  If client-side code does escaping incorrectly then a
-        SQL-injection attack is possible.  This risk can be prevented by
-        making the server reject queries in which a quote mark appears to be
-        escaped by a backslash.
-        The allowed values of <varname>backslash_quote</> are
-        <literal>on</> (allow <literal>\'</> always),
-        <literal>off</> (reject always), and
-        <literal>safe_encoding</> (allow only if client encoding does not
-        allow ASCII <literal>\</> within a multibyte character).
-        <literal>safe_encoding</> is the default setting.
-       </para>
-
-       <para>
-        Note that in a standard-conforming string literal, <literal>\</> just
-        means <literal>\</> anyway.  This parameter only affects the handling of
-        non-standard-conforming literals, including
-        escape string syntax (<literal>E'...'</>).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-default-with-oids" xreflabel="default_with_oids">
-      <term><varname>default_with_oids</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>default_with_oids</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This controls whether <command>CREATE TABLE</command> and
-        <command>CREATE TABLE AS</command> include an OID column in
-        newly-created tables, if neither <literal>WITH OIDS</literal>
-        nor <literal>WITHOUT OIDS</literal> is specified. It also
-        determines whether OIDs will be included in tables created by
-        <command>SELECT INTO</command>. The parameter is <literal>off</>
-        by default; in <productname>PostgreSQL</> 8.0 and earlier, it
-        was on by default.
-       </para>
-
-       <para>
-        The use of OIDs in user tables is considered deprecated, so
-        most installations should leave this variable disabled.
-        Applications that require OIDs for a particular table should
-        specify <literal>WITH OIDS</literal> when creating the
-        table. This variable can be enabled for compatibility with old
-        applications that do not follow this behavior.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-escape-string-warning" xreflabel="escape_string_warning">
-      <term><varname>escape_string_warning</varname> (<type>boolean</type>)</term>
-      <indexterm><primary>strings</><secondary>escape warning</></>
-      <indexterm>
-       <primary><varname>escape_string_warning</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When on, a warning is issued if a backslash (<literal>\</>)
-        appears in an ordinary string literal (<literal>'...'</>
-        syntax) and <varname>standard_conforming_strings</varname> is off.
-        The default is <literal>on</>.
-       </para>
-       <para>
-        Applications that wish to use backslash as escape should be
-        modified to use escape string syntax (<literal>E'...'</>),
-        because the default behavior of ordinary strings is now to treat
-        backslash as an ordinary character, per SQL standard.  This variable
-        can be enabled to help locate code that needs to be changed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-lo-compat-privileges" xreflabel="lo_compat_privileges">
-      <term><varname>lo_compat_privileges</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>lo_compat_privileges</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        In <productname>PostgreSQL</> releases prior to 9.0, large objects
-        did not have access privileges and were, in effect, readable and
-        writable by all users.  Setting this variable to <literal>on</>
-        disables the new privilege checks, for compatibility with prior
-        releases.  The default is <literal>off</>.
-       </para>
-       <para>
-        Setting this variable does not disable all security checks related to
-        large objects &mdash; only those for which the default behavior has
-        changed in <productname>PostgreSQL</> 9.0.
-        For example, <literal>lo_import()</literal> and
-        <literal>lo_export()</literal> need superuser privileges independent
-        of this setting.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    <varlistentry id="guc-quote-all-identifiers" xreflabel="quote-all-identifiers">
-      <term><varname>quote_all_identifiers</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>quote_all_identifiers</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When the database generates SQL, force all identifiers to be quoted,
-        even if they are not (currently) keywords.  This will affect the
-        output of <command>EXPLAIN</> as well as the results of functions
-        like <function>pg_get_viewdef</>.  See also the
-        <option>--quote-all-identifiers</option> option of
-        <xref linkend="app-pgdump"> and <xref linkend="app-pg-dumpall">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-sql-inheritance" xreflabel="sql_inheritance">
-      <term><varname>sql_inheritance</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>sql_inheritance</> configuration parameter</primary>
-      </indexterm>
-      <indexterm><primary>inheritance</></>
-      <listitem>
-       <para>
-        This controls the inheritance semantics.  If turned <literal>off</>,
-        subtables are not accessed by various commands by default; basically
-        an implied <literal>ONLY</literal> key word.  This was added for
-        compatibility with releases prior to 7.1.  See
-        <xref linkend="ddl-inherit"> for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-standard-conforming-strings" xreflabel="standard_conforming_strings">
-      <term><varname>standard_conforming_strings</varname> (<type>boolean</type>)</term>
-      <indexterm><primary>strings</><secondary>standard conforming</></>
-      <indexterm>
-       <primary><varname>standard_conforming_strings</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This controls whether ordinary string literals
-        (<literal>'...'</>) treat backslashes literally, as specified in
-        the SQL standard.
-        Beginning in <productname>PostgreSQL</productname> 9.1, the default is
-        <literal>on</> (prior releases defaulted to <literal>off</>).
-        Applications can check this
-        parameter to determine how string literals will be processed.
-        The presence of this parameter can also be taken as an indication
-        that the escape string syntax (<literal>E'...'</>) is supported.
-        Escape string syntax (<xref linkend="sql-syntax-strings-escape">)
-        should be used if an application desires
-        backslashes to be treated as escape characters.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-synchronize-seqscans" xreflabel="synchronize_seqscans">
-      <term><varname>synchronize_seqscans</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>synchronize_seqscans</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This allows sequential scans of large tables to synchronize with each
-        other, so that concurrent scans read the same block at about the
-        same time and hence share the I/O workload.  When this is enabled,
-        a scan might start in the middle of the table and then <quote>wrap
-        around</> the end to cover all rows, so as to synchronize with the
-        activity of scans already in progress.  This can result in
-        unpredictable changes in the row ordering returned by queries that
-        have no <literal>ORDER BY</> clause.  Setting this parameter to
-        <literal>off</> ensures the pre-8.3 behavior in which a sequential
-        scan always starts from the beginning of the table.  The default
-        is <literal>on</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-
-    <sect2 id="runtime-config-compatible-clients">
-     <title>Platform and Client Compatibility</title>
-&common;
-     <variablelist>
-
-     <varlistentry id="guc-transform-null-equals" xreflabel="transform_null_equals">
-      <term><varname>transform_null_equals</varname> (<type>boolean</type>)</term>
-      <indexterm><primary>IS NULL</></>
-      <indexterm>
-       <primary><varname>transform_null_equals</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When on, expressions of the form <literal><replaceable>expr</> =
-        NULL</literal> (or <literal>NULL =
-        <replaceable>expr</></literal>) are treated as
-        <literal><replaceable>expr</> IS NULL</literal>, that is, they
-        return true if <replaceable>expr</> evaluates to the null value,
-        and false otherwise. The correct SQL-spec-compliant behavior of
-        <literal><replaceable>expr</> = NULL</literal> is to always
-        return null (unknown). Therefore this parameter defaults to
-        <literal>off</>.
-       </para>
-
-       <para>
-        However, filtered forms in <productname>Microsoft
-        Access</productname> generate queries that appear to use
-        <literal><replaceable>expr</> = NULL</literal> to test for
-        null values, so if you use that interface to access the database you
-        might want to turn this option on.  Since expressions of the
-        form <literal><replaceable>expr</> = NULL</literal> always
-        return the null value (using the SQL standard interpretation), they are not
-        very useful and do not appear often in normal applications so
-        this option does little harm in practice.  But new users are
-        frequently confused about the semantics of expressions
-        involving null values, so this option is off by default.
-       </para>
-
-       <para>
-        Note that this option only affects the exact form <literal>= NULL</>,
-        not other comparison operators or other expressions
-        that are computationally equivalent to some expression
-        involving the equals operator (such as <literal>IN</literal>).
-        Thus, this option is not a general fix for bad programming.
-       </para>
-
-       <para>
-        Refer to <xref linkend="functions-comparison"> for related information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-    </sect2>
-   </sect1>
-
-   <sect1 id="runtime-config-error-handling">
-    <title>Error Handling</title>
-
-    <variablelist>
-
-     <varlistentry id="guc-exit-on-error" xreflabel="exit_on_error">
-      <term><varname>exit_on_error</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>exit_on_error</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If true, any error will terminate the current session.  By default,
-        this is set to false, so that only FATAL errors will terminate the
-        session.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-restart-after-crash" xreflabel="restart_after_crash">
-      <term><varname>restart_after_crash</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>restart_after_crash</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When set to true, which is the default, <productname>PostgreSQL</>
-        will automatically reinitialize after a backend crash.  Leaving this
-        value set to true is normally the best way to maximize the availability
-        of the database.  However, in some circumstances, such as when
-        <productname>PostgreSQL</> is being invoked by clusterware, it may be
-        useful to disable the restart so that the clusterware can gain
-        control and take any actions it deems appropriate.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-   </sect1>
-
-   <sect1 id="runtime-config-preset">
-    <title>Preset Options</title>
-&common;
-
-    <para>
-     The following <quote>parameters</> are read-only, and are determined
-<!## PG>
-     when <productname>PostgreSQL</productname> is compiled or when it is
-<!## end>
-<!## XC>
-     when <productname>Postgres-XC</productname> is compiled or when it is
-<!## end>
-<!## XL>
-     when <productname>Postgres-XL</productname> is compiled or when it is
-<!## end>
-     installed. As such, they have been excluded from the sample
-     <filename>postgresql.conf</> file.  These options report
-<!## PG>
-     various aspects of <productname>PostgreSQL</productname> behavior
-<!## end>
-<!## XC>
-     various aspects of <productname>Postgres-XC</productname> behavior
-<!## end>
-<!## XL>
-     various aspects of <productname>Postgres-XL</productname> behavior
-<!## end>
-     that might be of interest to certain applications, particularly
-     administrative front-ends.
-    </para>
-
-    <variablelist>
-
-     <varlistentry id="guc-block-size" xreflabel="block_size">
-      <term><varname>block_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>block_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the size of a disk block.  It is determined by the value
-        of <literal>BLCKSZ</> when building the server. The default
-        value is 8192 bytes.  The meaning of some configuration
-        variables (such as <xref linkend="guc-shared-buffers">) is
-        influenced by <varname>block_size</varname>. See <xref
-        linkend="runtime-config-resource"> for information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-integer-datetimes" xreflabel="integer_datetimes">
-      <term><varname>integer_datetimes</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>integer_datetimes</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-<!## PG>
-        Reports whether <productname>PostgreSQL</> was built with
-        support for 64-bit-integer dates and times.  This can be
-        disabled by configuring with <literal>--disable-integer-datetimes</>
-        when building <productname>PostgreSQL</>.  The default value is
-        <literal>on</literal>.
-<!## end>
-<!## XC>
-        Reports whether <productname>Postgres-XC</> was built with
-        support for 64-bit-integer dates and times.  This can be
-        disabled by configuring with <literal>--disable-integer-datetimes</>
-        when building <productname>Postgres-XC</>.  The default value is
-        <literal>on</literal>.
-<!## end>
-<!## XL>
-        Reports whether <productname>Postgres-XL</> was built with
-        support for 64-bit-integer dates and times.  This can be
-        disabled by configuring with <literal>--disable-integer-datetimes</>
-        when building <productname>Postgres-XL</>.  The default value is
-        <literal>on</literal>.
-<!## end>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-lc-collate" xreflabel="lc_collate">
-      <term><varname>lc_collate</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>lc_collate</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the locale in which sorting of textual data is done.
-        See <xref linkend="locale"> for more information.
-        This value is determined when a database is created.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-lc-ctype" xreflabel="lc_ctype">
-      <term><varname>lc_ctype</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>lc_ctype</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the locale that determines character classifications.
-        See <xref linkend="locale"> for more information.
-        This value is determined when a database is created.
-        Ordinarily this will be the same as <varname>lc_collate</varname>,
-        but for special applications it might be set differently.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-function-args" xreflabel="max_function_args">
-      <term><varname>max_function_args</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_function_args</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the maximum number of function arguments. It is determined by
-        the value of <literal>FUNC_MAX_ARGS</> when building the server. The
-        default value is 100 arguments.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-identifier-length" xreflabel="max_identifier_length">
-      <term><varname>max_identifier_length</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_identifier_length</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the maximum identifier length. It is determined as one
-        less than the value of <literal>NAMEDATALEN</> when building
-        the server. The default value of <literal>NAMEDATALEN</> is
-        64; therefore the default
-        <varname>max_identifier_length</varname> is 63 bytes, which
-        can be less than 63 characters when using multibyte encodings.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-index-keys" xreflabel="max_index_keys">
-      <term><varname>max_index_keys</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_index_keys</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the maximum number of index keys. It is determined by
-        the value of <literal>INDEX_MAX_KEYS</> when building the server. The
-        default value is 32 keys.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-segment-size" xreflabel="segment_size">
-      <term><varname>segment_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>segment_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the number of blocks (pages) that can be stored within a file
-        segment.  It is determined by the value of <literal>RELSEG_SIZE</>
-        when building the server.  The maximum size of a segment file in bytes
-        is equal to <varname>segment_size</> multiplied by
-        <varname>block_size</>; by default this is 1GB.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-server-encoding" xreflabel="server_encoding">
-      <term><varname>server_encoding</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>server_encoding</> configuration parameter</primary>
-      </indexterm>
-      <indexterm><primary>character set</></>
-      <listitem>
-       <para>
-        Reports the database encoding (character set).
-        It is determined when the database is created.  Ordinarily,
-        clients need only be concerned with the value of <xref
-        linkend="guc-client-encoding">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-server-version" xreflabel="server_version">
-      <term><varname>server_version</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>server_version</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the version number of the server. It is determined by the
-        value of <literal>PG_VERSION</> when building the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-server-version-num" xreflabel="server_version_num">
-      <term><varname>server_version_num</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>server_version_num</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the version number of the server as an integer. It is determined
-        by the value of <literal>PG_VERSION_NUM</> when building the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-wal-block-size" xreflabel="wal_block_size">
-      <term><varname>wal_block_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>wal_block_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the size of a WAL disk block.  It is determined by the value
-        of <literal>XLOG_BLCKSZ</> when building the server. The default value
-        is 8192 bytes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-wal-segment-size" xreflabel="wal_segment_size">
-      <term><varname>wal_segment_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>wal_segment_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the number of blocks (pages) in a WAL segment file.
-        The total size of a WAL segment file in bytes is equal to
-        <varname>wal_segment_size</> multiplied by <varname>wal_block_size</>;
-        by default this is 16MB.  See <xref linkend="wal-configuration"> for
-        more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </sect1>
-
-   <sect1 id="runtime-config-custom">
-    <title>Customized Options</title>
-&common;
-
-    <para>
-     This feature was designed to allow parameters not normally known to
-<!## PG>
-     <productname>PostgreSQL</productname> to be added by add-on modules
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> to be added by add-on modules
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> to be added by add-on modules
-<!## end>
-     (such as procedural languages).  This allows add-on modules to be
-     configured in the standard ways.
-    </para>
-
-    <variablelist>
-
-     <varlistentry id="guc-custom-variable-classes" xreflabel="custom_variable_classes">
-      <term><varname>custom_variable_classes</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>custom_variable_classes</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This variable specifies one or several class names to be used for
-        custom variables, in the form of a comma-separated list. A custom
-        variable is a variable not normally known
-<!## PG>
-        to <productname>PostgreSQL</productname> proper but used by some
-<!## end>
-<!## XC>
-        to <productname>Postgres-XC</productname> proper but used by some
-<!## end>
-<!## XL>
-        to <productname>Postgres-XL</productname> proper but used by some
-<!## end>
-        add-on module.  Such variables must have names consisting of a class
-        name, a dot, and a variable name.  <varname>custom_variable_classes</>
-        specifies all the class names in use in a particular installation.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    <para>
-     The difficulty with setting custom variables in
-     <filename>postgresql.conf</> is that the file must be read before add-on
-     modules have been loaded, and so custom variables would ordinarily be
-     rejected as unknown.  When <varname>custom_variable_classes</> is set,
-     the server will accept definitions of arbitrary variables within each
-     specified class.  These variables will be treated as placeholders and
-     will have no function until the module that defines them is loaded. When a
-     module for a specific class is loaded, it will add the proper variable
-     definitions for its class name, convert any placeholder
-     values according to those definitions, and issue warnings for any
-     unrecognized placeholders of its class that remain.
-    </para>
-
-    <para>
-     Here is an example of what <filename>postgresql.conf</> might contain
-     when using custom variables:
-
-<programlisting>
-custom_variable_classes = 'plpgsql,plperl'
-plpgsql.variable_conflict = use_variable
-plperl.use_strict = true
-plruby.use_strict = true        # generates error: unknown class name
-</programlisting>
-    </para>
-   </sect1>
-
-   <sect1 id="runtime-config-developer">
-    <title>Developer Options</title>
-&common;
-
-    <para>
-     The following parameters are intended for work on the
-<!## PG>
-     <productname>PostgreSQL</productname> source code, and in some cases
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> source code, and in some cases
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> source code, and in some cases
-<!## end>
-     to assist with recovery of severely damaged databases.  There
-     should be no reason to use them on a production database.
-     As such, they have been excluded from the sample
-     <filename>postgresql.conf</> file.  Note that many of these
-     parameters require special source compilation flags to work at all.
-    </para>
-
-    <variablelist>
-     <varlistentry id="guc-allow-system-table-mods" xreflabel="allow_system_table_mods">
-      <term><varname>allow_system_table_mods</varname> (<type>boolean</type>)</term>
-      <indexterm>
-        <primary><varname>allow_system_table_mods</varname> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Allows modification of the structure of system tables.
-        This is used by <command>initdb</command>.
-        This parameter can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-debug-assertions" xreflabel="debug_assertions">
-      <term><varname>debug_assertions</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>debug_assertions</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Turns on various assertion checks. This is a debugging aid. If
-        you are experiencing strange problems or crashes you might want
-        to turn this on, as it might expose programming mistakes. To use
-        this parameter, the macro <symbol>USE_ASSERT_CHECKING</symbol>
-<!## PG>
-        must be defined when <productname>PostgreSQL</productname> is
-<!## end>
-<!## XC>
-        must be defined when <productname>Postgres-XC</productname> is
-<!## end>
-<!## XL>
-        must be defined when <productname>Postgres-XL</productname> is
-<!## end>
-        built (accomplished by the <command>configure</command> option
-        <option>--enable-cassert</option>). Note that
-        <varname>debug_assertions</varname> defaults to <literal>on</>
-<!## PG>
-        if <productname>PostgreSQL</productname> has been built with
-<!## end>
-<!## XC>
-        if <productname>Postgres-XC</productname> has been built with
-<!## end>
-<!## XL>
-        if <productname>Postgres-XL</productname> has been built with
-<!## end>
-        assertions enabled.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-ignore-system-indexes" xreflabel="ignore_system_indexes">
-      <term><varname>ignore_system_indexes</varname> (<type>boolean</type>)</term>
-      <indexterm>
-        <primary><varname>ignore_system_indexes</varname> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Ignore system indexes when reading system tables (but still
-        update the indexes when modifying the tables).  This is useful
-        when recovering from damaged system indexes.
-        This parameter cannot be changed after session start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-post-auth-delay" xreflabel="post_auth_delay">
-      <term><varname>post_auth_delay</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>post_auth_delay</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If nonzero, a delay of this many seconds occurs when a new
-        server process is started, after it conducts the
-        authentication procedure.  This is intended to give developers an
-        opportunity to attach to the server process with a debugger.
-        This parameter cannot be changed after session start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-pre-auth-delay" xreflabel="pre_auth_delay">
-      <term><varname>pre_auth_delay</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>pre_auth_delay</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If nonzero, a delay of this many seconds occurs just after a
-        new server process is forked, before it conducts the
-        authentication procedure.  This is intended to give developers an
-        opportunity to attach to the server process with a debugger to
-        trace down misbehavior in authentication.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-trace-notify" xreflabel="trace_notify">
-      <term><varname>trace_notify</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>trace_notify</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Generates a great amount of debugging output for the
-        <command>LISTEN</command> and <command>NOTIFY</command>
-        commands.  <xref linkend="guc-client-min-messages"> or
-        <xref linkend="guc-log-min-messages"> must be
-        <literal>DEBUG1</literal> or lower to send this output to the
-        client or server logs, respectively.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-trace-recovery-messages" xreflabel="trace_recovery_messages">
-      <term><varname>trace_recovery_messages</varname> (<type>enum</type>)</term>
-      <indexterm>
-       <primary><varname>trace_recovery_messages</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enables logging of recovery-related debugging output that otherwise
-        would not be logged. This parameter allows the user to override the
-        normal setting of <xref linkend="guc-log-min-messages">, but only for
-        specific messages. This is intended for use in debugging Hot Standby.
-        Valid values are <literal>DEBUG5</>, <literal>DEBUG4</>,
-        <literal>DEBUG3</>, <literal>DEBUG2</>, <literal>DEBUG1</>, and
-        <literal>LOG</>.  The default, <literal>LOG</>, does not affect
-        logging decisions at all.  The other values cause recovery-related
-        debug messages of that priority or higher to be logged as though they
-        had <literal>LOG</> priority; for common settings of
-        <varname>log_min_messages</> this results in unconditionally sending
-        them to the server log.
-        This parameter can only be set in the <filename>postgresql.conf</>
-        file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-trace-sort" xreflabel="trace_sort">
-      <term><varname>trace_sort</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>trace_sort</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If on, emit information about resource usage during sort operations.
-        This parameter is only available if the <symbol>TRACE_SORT</symbol> macro
-<!## PG>
-        was defined when <productname>PostgreSQL</productname> was compiled.
-<!## end>
-<!## XC>
-        was defined when <productname>Postgres-XC</productname> was compiled.
-<!## end>
-<!## XL>
-        was defined when <productname>Postgres-XL</productname> was compiled.
-<!## end>
-        (However, <symbol>TRACE_SORT</symbol> is currently defined by default.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>trace_locks</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>trace_locks</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If on, emit information about lock usage.  Information dumped
-        includes the type of lock operation, the type of lock and the unique
-        identifier of the object being locked or unlocked.  Also included
-        are bit masks for the lock types already granted on this object as
-        well as for the lock types awaited on this object.  For each lock
-        type a count of the number of granted locks and waiting locks is
-        also dumped as well as the totals.  An example of the log file output
-        is shown here:
-<screen>
-LOG:  LockAcquire: new: lock(0xb7acd844) id(24688,24696,0,0,0,1)
-      grantMask(0) req(0,0,0,0,0,0,0)=0 grant(0,0,0,0,0,0,0)=0
-      wait(0) type(AccessShareLock)
-LOG:  GrantLock: lock(0xb7acd844) id(24688,24696,0,0,0,1)
-      grantMask(2) req(1,0,0,0,0,0,0)=1 grant(1,0,0,0,0,0,0)=1
-      wait(0) type(AccessShareLock)
-LOG:  UnGrantLock: updated: lock(0xb7acd844) id(24688,24696,0,0,0,1)
-      grantMask(0) req(0,0,0,0,0,0,0)=0 grant(0,0,0,0,0,0,0)=0
-      wait(0) type(AccessShareLock)
-LOG:  CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
-      grantMask(0) req(0,0,0,0,0,0,0)=0 grant(0,0,0,0,0,0,0)=0
-      wait(0) type(INVALID)
-</screen>
-        Details of the structure being dumped may be found in
-        <filename>src/include/storage/lock.h</filename>.
-       </para>
-       <para>
-        This parameter is only available if the <symbol>LOCK_DEBUG</symbol>
-<!## PG>
-        macro was defined when <productname>PostgreSQL</productname> was
-<!## end>
-<!## XC>
-        macro was defined when <productname>Postgres-XC</productname> was
-<!## end>
-<!## XL>
-        macro was defined when <productname>Postgres-XL</productname> was
-<!## end>
-        compiled.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>trace_lwlocks</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>trace_lwlocks</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If on, emit information about lightweight lock usage.  Lightweight
-        locks are intended primarily to provide mutual exclusion of access
-        to shared-memory data structures.
-       </para>
-       <para>
-        This parameter is only available if the <symbol>LOCK_DEBUG</symbol>
-<!## PG>
-        macro was defined when <productname>PostgreSQL</productname> was
-<!## end>
-<!## XC>
-        macro was defined when <productname>Postgres-XC</productname> was
-<!## end>
-<!## XL>
-        macro was defined when <productname>Postgres-XL</productname> was
-<!## end>
-        compiled.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>trace_userlocks</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>trace_userlocks</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If on, emit information about user lock usage.  Output is the same
-        as for <symbol>trace_locks</symbol>, only for user locks.
-       </para>
-       <para>
-        User locks were removed as of PostgreSQL version 8.2.  This option
-        currently has no effect.
-       </para>
-       <para>
-        This parameter is only available if the <symbol>LOCK_DEBUG</symbol>
-<!## PG>
-        macro was defined when <productname>PostgreSQL</productname> was
-<!## end>
-<!## XC>
-        macro was defined when <productname>Postgres-XC</productname> was
-<!## end>
-<!## XL>
-        macro was defined when <productname>Postgres-XL</productname> was
-<!## end>
-        compiled.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>trace_lock_oidmin</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>trace_lock_oidmin</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If set, do not trace locks for tables below this OID. (use to avoid
-        output on system tables)
-       </para>
-       <para>
-        This parameter is only available if the <symbol>LOCK_DEBUG</symbol>
-<!## PG>
-        macro was defined when <productname>PostgreSQL</productname> was
-<!## end>
-<!## XC>
-        macro was defined when <productname>Postgres-XC</productname> was
-<!## end>
-<!## XL>
-        macro was defined when <productname>Postgres-XL</productname> was
-<!## end>
-        compiled.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>trace_lock_table</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>trace_lock_table</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Unconditionally trace locks on this table (OID).
-       </para>
-       <para>
-        This parameter is only available if the <symbol>LOCK_DEBUG</symbol>
-<!## PG>
-        macro was defined when <productname>PostgreSQL</productname> was
-<!## end>
-<!## XC>
-        macro was defined when <productname>Postgres-XC</productname> was
-<!## end>
-<!## XL>
-        macro was defined when <productname>Postgres-XL</productname> was
-<!## end>
-        compiled.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>debug_deadlocks</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>debug_deadlocks</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If set, dumps information about all current locks when a
-        deadlock timeout occurs.
-       </para>
-       <para>
-        This parameter is only available if the <symbol>LOCK_DEBUG</symbol>
-<!## PG>
-        macro was defined when <productname>PostgreSQL</productname> was
-<!## end>
-<!## XC>
-        macro was defined when <productname>Postgres-XC</productname> was
-<!## end>
-<!## XL>
-        macro was defined when <productname>Postgres-XL</productname> was
-<!## end>
-        compiled.
-       </para>
-<!## XC>
-&xconly;
-       <para>
-        <productname>Postgres-XC</> does not detect global deadlocks
-        where multiple node (Coordinators and/or Datanodes) are
-        involved.
-       </para>
-<!## end>
-<!## XL>
-&xlonly;
-       <para>
-        <productname>Postgres-XL</> does not detect global deadlocks
-        where multiple node (Coordinators and/or Datanodes) are
-        involved.
-       </para>
-<!## end>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>log_btree_build_stats</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>log_btree_build_stats</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If set, logs system resource usage statistics (memory and CPU) on
-        various B-tree operations.
-       </para>
-       <para>
-        This parameter is only available if the <symbol>BTREE_BUILD_STATS</symbol>
-<!## PG>
-        macro was defined when <productname>PostgreSQL</productname> was
-<!## end>
-<!## XC>
-        macro was defined when <productname>Postgres-XC</productname> was
-<!## end>
-<!## XL>
-        macro was defined when <productname>Postgres-XL</productname> was
-<!## end>
-        compiled.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-wal-debug" xreflabel="wal_debug">
-      <term><varname>wal_debug</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>wal_debug</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        If on, emit WAL-related debugging output. This parameter is
-        only available if the <symbol>WAL_DEBUG</symbol> macro was
-<!## PG>
-        defined when <productname>PostgreSQL</productname> was
-<!## end>
-<!## XC>
-        defined when <productname>Postgres-XC</productname> was
-<!## end>
-<!## XL>
-        defined when <productname>Postgres-XL</productname> was
-<!## end>
-        compiled.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    <varlistentry id="guc-zero-damaged-pages" xreflabel="zero_damaged_pages">
-      <term><varname>zero_damaged_pages</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>zero_damaged_pages</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Detection of a damaged page header normally causes
-<!## PG>
-         <productname>PostgreSQL</> to report an error, aborting the current
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</> to report an error, aborting the current
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</> to report an error, aborting the current
-<!## end>
-        transaction.  Setting <varname>zero_damaged_pages</> to on causes
-        the system to instead report a warning, zero out the damaged
-        page in memory, and continue processing.  This behavior <emphasis>will destroy data</>,
-        namely all the rows on the damaged page.  However, it does allow you to get
-        past the error and retrieve rows from any undamaged pages that might
-        be present in the table.  It is useful for recovering data if
-        corruption has occurred due to a hardware or software error.  You should
-        generally not set this on until you have given up hope of recovering
-        data from the damaged pages of a table.  Zeroed-out pages are not
-        forced to disk so it is recommended to recreate the table or
-        the index before turning this parameter off again.  The
-        default setting is <literal>off</>, and it can only be changed
-        by a superuser.
-       </para>
-      </listitem>
-     </varlistentry>
-   </variablelist>
-  </sect1>
-  <sect1 id="runtime-config-short">
-   <title>Short Options</title>
-&common;
-
-   <para>
-    For convenience there are also single letter command-line option
-    switches available for some parameters.  They are described in
-    <xref linkend="runtime-config-short-table">.  Some of these
-    options exist for historical reasons, and their presence as a
-    single-letter option does not necessarily indicate an endorsement
-    to use the option heavily.
-   </para>
-
-    <table id="runtime-config-short-table">
-     <title>Short Option Key</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>Short Option</entry>
-        <entry>Equivalent</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry><option>-A <replaceable>x</replaceable></option></entry>
-        <entry><literal>debug_assertions = <replaceable>x</replaceable></></entry>
-       </row>
-       <row>
-        <entry><option>-B <replaceable>x</replaceable></option></entry>
-        <entry><literal>shared_buffers = <replaceable>x</replaceable></></entry>
-       </row>
-       <row>
-        <entry><option>-d <replaceable>x</replaceable></option></entry>
-        <entry><literal>log_min_messages = DEBUG<replaceable>x</replaceable></></entry>
-       </row>
-       <row>
-        <entry><option>-e</option></entry>
-        <entry><literal>datestyle = euro</></entry>
-       </row>
-       <row>
-        <entry>
-          <option>-fb</option>, <option>-fh</option>, <option>-fi</option>,
-          <option>-fm</option>, <option>-fn</option>,
-          <option>-fs</option>, <option>-ft</option>
-         </entry>
-         <entry>
-          <literal>enable_bitmapscan = off</>,
-          <literal>enable_hashjoin = off</>,
-          <literal>enable_indexscan = off</>,
-          <literal>enable_mergejoin = off</>,
-          <literal>enable_nestloop = off</>,
-          <literal>enable_seqscan = off</>,
-          <literal>enable_tidscan = off</>
-         </entry>
-       </row>
-       <row>
-        <entry><option>-F</option></entry>
-        <entry><literal>fsync = off</></entry>
-       </row>
-       <row>
-        <entry><option>-h <replaceable>x</replaceable></option></entry>
-        <entry><literal>listen_addresses = <replaceable>x</replaceable></></entry>
-       </row>
-       <row>
-        <entry><option>-i</option></entry>
-        <entry><literal>listen_addresses = '*'</></entry>
-       </row>
-       <row>
-        <entry><option>-k <replaceable>x</replaceable></option></entry>
-        <entry><literal>unix_socket_directory = <replaceable>x</replaceable></></entry>
-       </row>
-       <row>
-        <entry><option>-l</option></entry>
-        <entry><literal>ssl = on</></entry>
-       </row>
-       <row>
-        <entry><option>-N <replaceable>x</replaceable></option></entry>
-        <entry><literal>max_connections = <replaceable>x</replaceable></></entry>
-       </row>
-       <row>
-        <entry><option>-O</option></entry>
-        <entry><literal>allow_system_table_mods = on</></entry>
-       </row>
-       <row>
-        <entry><option>-p <replaceable>x</replaceable></option></entry>
-        <entry><literal>port = <replaceable>x</replaceable></></entry>
-       </row>
-       <row>
-        <entry><option>-P</option></entry>
-        <entry><literal>ignore_system_indexes = on</></entry>
-       </row>
-       <row>
-        <entry><option>-s</option></entry>
-        <entry><literal>log_statement_stats = on</></entry>
-       </row>
-       <row>
-        <entry><option>-S <replaceable>x</replaceable></option></entry>
-        <entry><literal>work_mem = <replaceable>x</replaceable></></entry>
-       </row>
-       <row>
-        <entry><option>-tpa</option>, <option>-tpl</option>, <option>-te</option></entry>
-        <entry><literal>log_parser_stats = on</>,
-        <literal>log_planner_stats = on</>,
-        <literal>log_executor_stats = on</></entry>
-       </row>
-       <row>
-        <entry><option>-W <replaceable>x</replaceable></option></entry>
-        <entry><literal>post_auth_delay = <replaceable>x</replaceable></></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-  </sect1>
-
-<!## XC>
-<!--
-Postgres-XC Specific Parameters
--->
-  <sect1 id="pg-xc-specifics">
-   <title>Postgres-XC Specific Parameters</title>
-&xconly;
-   <para>
-    Because <productname>Postgres-XC</> distribute data into multiple
-    Datanodes and multiple Coordinators can accept transactions in
-    parallel, specific Coordinator must know what Coordinators and
-    Datanodes to connect.  Coordinator and Datanode also must know
-    where they can request transaction information.  The following
-    describes these additional GUC parameters.
-   </para>
-
-    <variablelist>
-
-     <varlistentry id="guc-max-pool-size" xreflabel="max_pool_size">
-      <term><varname>max_pool_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_pool_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specify the maximum connection pool of the Coordinator to Datanodes.
-        Because each transaction can be involved by all the Datanodes,
-        this parameter should at least be <varname>max_connections</>
-        multiplied by number of Datanodes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-min-pool-size" xreflabel="min_pool_size">
-      <term><varname>min_pool_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>min_pool_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Minumum number of the connection from the Coordinator to Datanodes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-coordinators" xreflabel="max_coordinators">
-      <term><varname>max_coordinators</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_coordinators</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Maximum number of Coordinators that can be configured in the cluster.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-datanodes" xreflabel="max_datanodes">
-      <term><varname>max_datanodes</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_datanodes</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Maximum number of Datanodes that can be configured in the cluster.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-pgxc-node-name" xreflabel="pgxc_node_name">
-      <term><varname>pgxc_node_name</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>pgxc_node_name</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the node name. A node uses this parameter to identify itself
-        with <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname>
-        </link>.nodename
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-pooler-port" xreflabel="pooler_port">
-      <term><varname>pooler_port</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>pooler_port</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the port number assigned to the connection pooler.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-gtm-host" xreflabel="gtm_host">
-      <term><varname>gtm_host</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>gtm_host</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the name or IP address of the <filename>GTM</>.  If you use <filename>GTM-Proxy</>, specify the <filename>GTM-Proxy</>'s one.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-gtm-port" xreflabel="gtm_port">
-      <term><varname>gtm_port</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>gtm_port</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Reports the port number of GTM.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="gtm_backup_barrier" xreflabel="backup_barrier">
-      <term><varname>gtm_backup_barrier</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>gtm_backup_barrier</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specify if GTM backs up the restart point for each barrier.
-        Default value is "OFF".
-        Superuser may set this variable by SET command, or this can be set in the file
-        <filename>postgresql.conf</filename> file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry id="guc-enforce-two-phase-commit" xreflabel="enforce_two_phase_commit">
-      <term><varname>enforce_two_phase_commit</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>enforce_two_phase_commit</varname> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Enforce the usage of two-phase commit instead for transactions involving temporary
-        objects or ON COMMIT actions.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-xc-maintenance-mode" xreflabel="xc_maintenance_mode">
-      <term><varname>xc_maintenance_mode</varname> (<type>bool</type>)</term>
-      <indexterm>
-       <primary><varname>xc_maintenance_mode</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specify to enter into maintenance mode. Turning this parameter to on will
-        change behavior of several statements. Each statement
-        behavior may not be compatible in future releases, so users
-        must be extremely careful when they attempt to set this
-        value to <literal>on</literal>.
-       </para>
-       <para>
-        Behavior of <xref linkend="sql-commit-prepared"> and
-        <xref linkend="sql-rollback-prepared"> statements are affected by
-        this parameter.
-       </para>
-       <para>
-        If this is set to ON, you can do many other maintenance work to update
-        Datanode locally through <literal>EXECUTE DIRECT</literal> or connecting
-        directly to Datanodes. As a DBA, you are totally responsible to any side
-        effects. You must be extremely careful not to bring in any inconsistencies
-        to Postgres-XC database cluster.
-       </para>
-       <para>
-        This parameter can only be set by superuser
-        with <literal>SET</literal> command. Otherwise, the setting
-        will be ignored.
-       </para>
-       <para>
-        As a session parameter, this parameter is shared among all
-        the connections of the session. It affects originating Coordinator as
-        well as remote nodes involved in session.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-  </sect1>
-<!## end>
-<!## XL>
-<!--
-Postgres-XL Specific Parameters
--->
-  <sect1 id="pg-xc-specifics">
-   <title>Postgres-XL Specific Parameters</title>
-&xlonly;
-   <para>
-    Because <productname>Postgres-XL</> distributes data into multiple
-    Datanodes and multiple Coordinators can accept transactions in
-    parallel, the Coordinators must know what Coordinators and
-    Datanodes to connect to.  The Coordinators and Datanodes also must know
-    where they can request transaction information.  The following
-    describes these additional GUC parameters.
-   </para>
-
-    <variablelist>
-
-     <varlistentry id="guc-max-pool-size" xreflabel="max_pool_size">
-      <term><varname>max_pool_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_pool_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specify the maximum connection pool of the Coordinator to Datanodes.
-        Because each transaction can be involved by all the Datanodes,
-        this parameter should at least be <varname>max_connections</>
-        multiplied by number of Datanodes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-min-pool-size" xreflabel="min_pool_size">
-      <term><varname>min_pool_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>min_pool_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Minumum number of the connection from the Coordinator to Datanodes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-pool-maintenance-timeout" xreflabel="pool_maintenance_timeout">
-     <term><varname>pool_maintenance_timeout</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>pool_maintenance_timeout</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This parameter specifies how long to wait until pooler
-        maintenance is performed. During such maintenance,
-        old idle connections are discarded.
-        This parameter is useful in multi-tenant environments where
-        many connections to many different databases may be used,
-        so that idle connections may cleaned up.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-remote-query-cost" xreflabel="remote_query_cost">
-     <term><varname>remote_query_cost</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>remote_query_cost</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This parameter specifies the cost overhead of setting up
-        a remote query to obtain remote data. It is used by
-        the planner in costing queries.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-network-byte-cost" xreflabel="network_byte_cost">
-     <term><varname>network_byte_cost</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>network_byte_cost</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This parameter is used in query cost planning to
-        estimate the cost involved in row shipping and obtaining
-        remote data based on the expected data size.
-        Row shipping is expensive and adds latency, so this
-        setting helps to favor plans that minimizes row shipping.
-       </para>
-      </listitem>
-     </varlistentry>
- 
-     <varlistentry id="guc-sequence-range" xreflabel="sequence_range">
-     <term><varname>sequence_range</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>sequence_range</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This parameter is used to get several sequence values
-        at once from GTM.  This greatly speeds up COPY and INSERT SELECT
-        operations where the target table uses sequences.
-        <productname>Postgres-XL</productname> will not use this entire
-        amount at once, but will increase the request size over
-        time if many requests are done in a short time frame in
-        the same session.
-        After a short time without any sequence requests, decreases back down to 1.
-        Note that any settings here are overriden if the CACHE clause was
-        used in <xref linkend='sql-createsequence'> or <xref linkend='sql-altersequence'>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-coordinators" xreflabel="max_coordinators">
-      <term><varname>max_coordinators</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_coordinators</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Maximum number of Coordinators that can be configured in the cluster.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-max-datanodes" xreflabel="max_datanodes">
-      <term><varname>max_datanodes</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>max_datanodes</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Maximum number of Datanodes that can be configured in the cluster.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-pgxc-node-name" xreflabel="pgxc_node_name">
-      <term><varname>pgxc_node_name</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>pgxc_node_name</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the node name. A node uses this parameter to identify itself
-        with <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname>
-        </link>.nodename
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-pooler-port" xreflabel="pooler_port">
-      <term><varname>pooler_port</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>pooler_port</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the port number assigned to the connection pooler process.
-        This is used in both the Coordinator and Datanode processes to
-        connect to other nodes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-gtm-host" xreflabel="gtm_host">
-      <term><varname>gtm_host</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>gtm_host</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies the host name or IP address of the <filename>GTM</>.  If you use <filename>GTM-Proxy</>, specify the <filename>GTM-Proxy</>'s one.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-gtm-port" xreflabel="gtm_port">
-      <term><varname>gtm_port</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>gtm_port</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifieis the port number of GTM.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-xc-maintenance-mode" xreflabel="xc_maintenance_mode">
-      <term><varname>xc_maintenance_mode</varname> (<type>bool</type>)</term>
-      <indexterm>
-       <primary><varname>xc_maintenance_mode</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specify to enter into maintenance mode. Turning this parameter to on will
-        change behavior of several statements. Each statement
-        behavior may not be compatible in future releases, so users
-        must be extremely careful when they attempt to set this
-        value to <literal>on</literal>.
-       </para>
-       <para>
-        Behavior of <xref linkend="sql-commit-prepared"> and
-        <xref linkend="sql-rollback-prepared"> statements are affected by
-        this parameter.
-       </para>
-       <para>
-        If this is set to ON, you can do maintenance work to update
-        Datanode locally through <literal>EXECUTE DIRECT</literal> or connecting
-        directly to Datanodes. As a DBA, you are totally responsible to any side
-        effects. You must be extremely careful not to bring in any inconsistencies
-        to Postgres-XL database cluster.
-       </para>
-       <para>
-        This parameter can only be set by superuser
-        with <literal>SET</literal> command. Otherwise, the setting
-        will be ignored.
-       </para>
-       <para>
-        As a session parameter, this parameter is shared among all
-        the connections of the session. It affects originating Coordinator as
-        well as remote nodes involved in session.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-shared-queues" xreflabel="shared_queues">
-      <term><varname>shared_queues</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>shared_queues</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Datanode Only
-       </para>
-       <para>
-        For some joins that occur in queries, data from one Datanode may
-        need to be joined with data from another Datanode.
-        <productname>Postgres-XL</productname> uses shared queues for this purpose.
-        During execution each Datanode knows if it needs to produce or consume
-        tuples, or both.
-       </para>
-       <para>
-        Note that there may be mulitple shared_queues used even for a single
-        query. So a value should be set taking into account the number of
-        connections it can accept and expected number of such joins occurring
-        simultaneously.
-       </para>
-     </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-shared-queue-size" xreflabel="shared_queue_size">
-      <term><varname>shared_queue_size</varname> (<type>integer</type>)</term>
-      <indexterm>
-       <primary><varname>shared_queue_size</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Datanode Only
-       </para>
-       <para>
-        This parameter sets the size of each each shared queue allocated.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-  </sect1>
-<!## end>
-
-</chapter>
diff --git a/doc-xc/src/sgml/contacts.sgmlin b/doc-xc/src/sgml/contacts.sgmlin
deleted file mode 100644
index a981625027..0000000000
--- a/doc-xc/src/sgml/contacts.sgmlin
+++ /dev/null
@@ -1,26 +0,0 @@
-<!-- doc/src/sgml/contacts.sgml -->
-
-<appendix label="B" id="contacts">
-<title>Contacts</title>
-
-<!--
-<para>
-Support for <productname>PostgreSQL</productname> comes primarily from
-this printed documentation, the web-based mailing list archives,
-and the mailing lists themselves.
-</para>
-
-<sect1 id="mailing-list">
-<title>Mailing Lists</title>
-
-<para>
-Refer to the introduction in this manual or to the
-<productname>PostgreSQL</productname>
-<ulink url="http://www.postgresql.org">web page</ulink>
-for subscription information to the no-cost mailing lists.
-</para>
-
-<sect1 id="people">
-<title>People</title>
--->
-</appendix>
diff --git a/doc-xc/src/sgml/contrib-spi.sgmlin b/doc-xc/src/sgml/contrib-spi.sgmlin
deleted file mode 100644
index 5ef2da84c8..0000000000
--- a/doc-xc/src/sgml/contrib-spi.sgmlin
+++ /dev/null
@@ -1,237 +0,0 @@
-<!-- doc/src/sgml/contrib-spi.sgml -->
-
-<sect1 id="contrib-spi" xreflabel="spi">
- <title>spi</title>
-
- <indexterm zone="contrib-spi">
-  <primary>SPI</primary>
-  <secondary>examples</secondary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  The <application>spi</> module provides several workable examples
-  of using SPI and triggers.  While these functions are of some value in
-  their own right, they are even more useful as examples to modify for
-  your own purposes.  The functions are general enough to be used
-  with any table, but you have to specify table and field names (as described
-  below) while creating a trigger.
- </para>
-
- <para>
-  Each of the groups of functions described below is provided as a
-  separately-installable extension.
- </para>
-
- <sect2>
-  <title>refint &mdash; Functions for Implementing Referential Integrity</title>
-
-&pgnotice;
-  <para>
-   <function>check_primary_key()</> and
-   <function>check_foreign_key()</> are used to check foreign key constraints.
-   (This functionality is long since superseded by the built-in foreign
-   key mechanism, of course, but the module is still useful as an example.)
-  </para>
-
-  <para>
-   <function>check_primary_key()</> checks the referencing table.
-   To use, create a <literal>BEFORE INSERT OR UPDATE</> trigger using this
-   function on a table referencing another table. Specify as the trigger
-   arguments: the referencing table's column name(s) which form the foreign
-   key, the referenced table name, and the column names in the referenced table
-   which form the primary/unique key.  To handle multiple foreign
-   keys, create a trigger for each reference.
-  </para>
-
-  <para>
-   <function>check_foreign_key()</> checks the referenced table.
-   To use, create a <literal>BEFORE DELETE OR UPDATE</> trigger using this
-   function on a table referenced by other table(s).  Specify as the trigger
-   arguments: the number of referencing tables for which the function has to
-   perform checking, the action if a referencing key is found
-   (<literal>cascade</> &mdash; to delete the referencing row,
-   <literal>restrict</> &mdash; to abort transaction if referencing keys
-   exist, <literal>setnull</> &mdash; to set referencing key fields to null),
-   the triggered table's column names which form the primary/unique key, then
-   the referencing table name and column names (repeated for as many
-   referencing tables as were specified by first argument).  Note that the
-   primary/unique key columns should be marked NOT NULL and should have a
-   unique index.
-  </para>
-
-  <para>
-   There are examples in <filename>refint.example</>.
-  </para>
- </sect2>
-
- <sect2>
-  <title>timetravel &mdash; Functions for Implementing Time Travel</title>
-
-&pgnotice;
-  <para>
-   Long ago, <productname>PostgreSQL</> had a built-in time travel feature
-   that kept the insert and delete times for each tuple.  This can be
-   emulated using these functions.  To use these functions,
-   you must add to a table two columns of <type>abstime</> type to store
-   the date when a tuple was inserted (start_date) and changed/deleted
-   (stop_date):
-
-<programlisting>
-CREATE TABLE mytab (
-        ...             ...
-        start_date      abstime,
-        stop_date       abstime
-        ...             ...
-);
-</programlisting>
-
-   The columns can be named whatever you like, but in this discussion
-   we'll call them start_date and stop_date.
-  </para>
-
-  <para>
-   When a new row is inserted, start_date should normally be set to
-   current time, and stop_date to <literal>infinity</>.  The trigger
-   will automatically substitute these values if the inserted data
-   contains nulls in these columns.  Generally, inserting explicit
-   non-null data in these columns should only be done when re-loading
-   dumped data.
-  </para>
-
-  <para>
-   Tuples with stop_date equal to <literal>infinity</> are <quote>valid
-   now</quote>, and can be modified.  Tuples with a finite stop_date cannot
-   be modified anymore &mdash; the trigger will prevent it.  (If you need
-   to do that, you can turn off time travel as shown below.)
-  </para>
-
-  <para>
-   For a modifiable row, on update only the stop_date in the tuple being
-   updated will be changed (to current time) and a new tuple with the modified
-   data will be inserted.  Start_date in this new tuple will be set to current
-   time and stop_date to <literal>infinity</>.
-  </para>
-
-  <para>
-   A delete does not actually remove the tuple but only sets its stop_date
-   to current time.
-  </para>
-
-  <para>
-   To query for tuples <quote>valid now</quote>, include
-   <literal>stop_date = 'infinity'</> in the query's WHERE condition.
-   (You might wish to incorporate that in a view.)  Similarly, you can
-   query for tuples valid at any past time with suitable conditions on
-   start_date and stop_date.
-  </para>
-
-  <para>
-   <function>timetravel()</> is the general trigger function that supports
-   this behavior.  Create a <literal>BEFORE INSERT OR UPDATE OR DELETE</>
-   trigger using this function on each time-traveled table. Specify two
-   trigger arguments: the actual
-   names of the start_date and stop_date columns.
-   Optionally, you can specify one to three more arguments, which must refer
-   to columns of type <type>text</>.  The trigger will store the name of
-   the current user into the first of these columns during INSERT, the
-   second column during UPDATE, and the third during DELETE.
-  </para>
-
-  <para>
-   <function>set_timetravel()</> allows you to turn time-travel on or off for
-   a table.
-   <literal>set_timetravel('mytab', 1)</> will turn TT ON for table <literal>mytab</>.
-   <literal>set_timetravel('mytab', 0)</> will turn TT OFF for table <literal>mytab</>.
-   In both cases the old status is reported.  While TT is off, you can modify
-   the start_date and stop_date columns freely.  Note that the on/off status
-   is local to the current database session &mdash; fresh sessions will
-   always start out with TT ON for all tables.
-  </para>
-
-  <para>
-   <function>get_timetravel()</> returns the TT state for a table without
-   changing it.
-  </para>
-
-  <para>
-   There is an example in <filename>timetravel.example</>.
-  </para>
- </sect2>
-
- <sect2>
-  <title>autoinc &mdash; Functions for Autoincrementing Fields</title>
-
-&pgnotice;
-  <para>
-   <function>autoinc()</> is a trigger that stores the next value of
-   a sequence into an integer field.  This has some overlap with the
-   built-in <quote>serial column</> feature, but it is not the same:
-   <function>autoinc()</> will override attempts to substitute a
-   different field value during inserts, and optionally it can be
-   used to increment the field during updates, too.
-  </para>
-
-  <para>
-   To use, create a <literal>BEFORE INSERT</> (or optionally <literal>BEFORE
-   INSERT OR UPDATE</>) trigger using this function.  Specify two
-   trigger arguments: the name of the integer column to be modified,
-   and the name of the sequence object that will supply values.
-   (Actually, you can specify any number of pairs of such names, if
-   you'd like to update more than one autoincrementing column.)
-  </para>
-
-  <para>
-   There is an example in <filename>autoinc.example</>.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>insert_username &mdash; Functions for Tracking Who Changed a Table</title>
-
-&pgnotice;
-  <para>
-   <function>insert_username()</> is a trigger that stores the current
-   user's name into a text field.  This can be useful for tracking
-   who last modified a particular row within a table.
-  </para>
-
-  <para>
-   To use, create a <literal>BEFORE INSERT</> and/or <literal>UPDATE</>
-   trigger using this function.  Specify a single trigger
-   argument: the name of the text column to be modified.
-  </para>
-
-  <para>
-   There is an example in <filename>insert_username.example</>.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>moddatetime &mdash; Functions for Tracking Last Modification Time</title>
-
-&pgnotice;
-  <para>
-   <function>moddatetime()</> is a trigger that stores the current
-   time into a <type>timestamp</> field.  This can be useful for tracking
-   the last modification time of a particular row within a table.
-  </para>
-
-  <para>
-   To use, create a <literal>BEFORE UPDATE</>
-   trigger using this function.  Specify a single trigger
-   argument: the name of the column to be modified.
-   The column must be of type <type>timestamp</> or <type>timestamp with
-   time zone</>.
-  </para>
-
-  <para>
-   There is an example in <filename>moddatetime.example</>.
-  </para>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/contrib.sgmlin b/doc-xc/src/sgml/contrib.sgmlin
deleted file mode 100644
index d53edfeb4d..0000000000
--- a/doc-xc/src/sgml/contrib.sgmlin
+++ /dev/null
@@ -1,152 +0,0 @@
-<!-- doc/src/sgml/contrib.sgml -->
-
-<appendix id="contrib">
- <title>Additional Supplied Modules</title>
-
-&pgnotice;
-
- <para>
-  This appendix contains information regarding the modules that
-  can be found in the <literal>contrib</literal> directory of the
-  <productname>PostgreSQL</> distribution.
-  These include porting tools, analysis utilities,
-  and plug-in features that are not part of the core PostgreSQL system,
-  mainly because they address a limited audience or are too experimental
-  to be part of the main source tree.  This does not preclude their
-  usefulness.
- </para>
-
- <para>
-  When building from the source distribution, these modules are not built
-  automatically, unless you build the "world" target
-  (see <xref linkend="build">).
-  You can build and install all of them by running:
-<screen>
-<userinput>gmake</userinput>
-<userinput>gmake install</userinput>
-</screen>
-  in the <literal>contrib</literal> directory of a configured source tree;
-  or to build and install
-  just one selected module, do the same in that module's subdirectory.
-  Many of the modules have regression tests, which can be executed by
-  running:
-<screen>
-<userinput>gmake installcheck</userinput>
-</screen>
-  once you have a <productname>PostgreSQL</> server running.  (Note that
-  <literal>gmake check</> is not supported; you must have an operational
-  database server to perform these tests, and you must have built and
-  installed the module(s) to be tested.)
- </para>
-
- <para>
-  If you are using a pre-packaged version of <productname>PostgreSQL</>,
-  these modules are typically made available as a separate subpackage,
-  such as <literal>postgresql-contrib</>.
- </para>
-
- <para>
-  Many modules supply new user-defined functions, operators, or types.
-  To make use of one of these modules, after you have installed the code
-  you need to register the new SQL objects in the database system.
-  In <productname>PostgreSQL</> 9.1 and later, this is done by executing
-  a <xref linkend="sql-createextension"> command.  In a fresh database,
-  you can simply do
-
-<programlisting>
-CREATE EXTENSION <replaceable>module_name</>;
-</programlisting>
-
-  This command must be run by a database superuser.  This registers the
-  new SQL objects in the current database only, so you need to run this
-  command in each database that you want
-  the module's facilities to be available in.  Alternatively, run it in
-  database <literal>template1</> so that the extension will be copied into
-  subsequently-created databases by default.
- </para>
-
- <para>
-  Many modules allow you to install their objects in a schema of your
-  choice.  To do that, add <literal>SCHEMA
-  <replaceable>schema_name</></literal> to the <command>CREATE EXTENSION</>
-  command.  By default, the objects will be placed in your current creation
-  target schema, typically <literal>public</>.
- </para>
-
- <para>
-  If your database was brought forward by dump and reload from a pre-9.1
-  version of <productname>PostgreSQL</>, and you had been using the pre-9.1
-  version of the module in it, you should instead do
-
-<programlisting>
-CREATE EXTENSION <replaceable>module_name</> FROM unpackaged;
-</programlisting>
-
-  This will update the pre-9.1 objects of the module into a proper
-  <firstterm>extension</> object.  Future updates to the module will be
-  managed by <xref linkend="sql-alterextension">.
-  For more information about extension updates, see
-  <xref linkend="extend-extensions">.
- </para>
-
- &adminpack;
- &auth-delay;
- &auto-explain;
- &btree-gin;
- &btree-gist;
- &chkpass;
- &citext;
- &cube;
- &dblink;
- &dict-int;
- &dict-xsyn;
- &dummy-seclabel;
- &earthdistance;
- &file-fdw;
- &fuzzystrmatch;
- &hstore;
- &intagg;
- &intarray;
- &isn;
- &lo;
- &ltree;
- &oid2name;
- &pageinspect;
- &passwordcheck;
- &pgarchivecleanup;
- &pgbench;
- &pgbuffercache;
- &pgcrypto;
- &pgfreespacemap;
- &pgrowlocks;
- &pgstandby;
- &pgstatstatements;
- &pgstattuple;
- &pgtestfsync;
- &pgtrgm;
- &pgupgrade;
-<!## XC>
- &pgxcclean;
- &pgxcctl;
- &pgxcddl;
- &pgxcmonitor;
-<!## end>
-<!## XL>
- &pgxcclean;
- &pgxcctl;
- &pgxcddl;
- &pgxcmonitor;
-<!## end>
- &seg;
- &sepgsql;
- &contrib-spi;
- &sslinfo;
- &tablefunc;
- &test-parser;
- &tsearch2;
- &unaccent;
- &uuid-ossp;
- &vacuumlo;
- &xml2;
-
-</appendix>
diff --git a/doc-xc/src/sgml/cube.sgmlin b/doc-xc/src/sgml/cube.sgmlin
deleted file mode 100644
index 1508c6da1f..0000000000
--- a/doc-xc/src/sgml/cube.sgmlin
+++ /dev/null
@@ -1,432 +0,0 @@
-<!-- doc/src/sgml/cube.sgml -->
-
-<sect1 id="cube" xreflabel="cube">
- <title>cube</title>
-
- <indexterm zone="cube">
-  <primary>cube</primary>
- </indexterm>
-
-&common;
-
- <para>
-  This module implements a data type <type>cube</> for
-  representing multidimensional cubes.
- </para>
-
- <sect2>
-  <title>Syntax</title>
-
-&common;
-
-  <para>
-   <xref linkend="cube-repr-table"> shows the valid external
-   representations for the <type>cube</>
-   type.  <replaceable>x</>, <replaceable>y</>, etc. denote
-   floating-point numbers.
-  </para>
-
-  <table id="cube-repr-table">
-   <title>Cube External Representations</title>
-   <tgroup cols="2">
-    <tbody>
-     <row>
-      <entry><literal><replaceable>x</></literal></entry>
-      <entry>A one-dimensional point
-       (or, zero-length one-dimensional interval)
-      </entry>
-     </row>
-     <row>
-      <entry><literal>(<replaceable>x</>)</literal></entry>
-      <entry>Same as above</entry>
-     </row>
-     <row>
-      <entry><literal><replaceable>x1</>,<replaceable>x2</>,...,<replaceable>xn</></literal></entry>
-      <entry>A point in n-dimensional space, represented internally as a
-      zero-volume cube
-      </entry>
-     </row>
-     <row>
-      <entry><literal>(<replaceable>x1</>,<replaceable>x2</>,...,<replaceable>xn</>)</literal></entry>
-      <entry>Same as above</entry>
-     </row>
-     <row>
-      <entry><literal>(<replaceable>x</>),(<replaceable>y</>)</literal></entry>
-      <entry>A one-dimensional interval starting at <replaceable>x</> and ending at <replaceable>y</> or vice versa; the
-       order does not matter
-      </entry>
-     </row>
-     <row>
-      <entry><literal>[(<replaceable>x</>),(<replaceable>y</>)]</literal></entry>
-      <entry>Same as above</entry>
-     </row>
-     <row>
-      <entry><literal>(<replaceable>x1</>,...,<replaceable>xn</>),(<replaceable>y1</>,...,<replaceable>yn</>)</literal></entry>
-      <entry>An n-dimensional cube represented by a pair of its diagonally
-       opposite corners
-      </entry>
-     </row>
-     <row>
-      <entry><literal>[(<replaceable>x1</>,...,<replaceable>xn</>),(<replaceable>y1</>,...,<replaceable>yn</>)]</literal></entry>
-      <entry>Same as above</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   It does not matter which order the opposite corners of a cube are
-   entered in.  The <type>cube</> functions
-   automatically swap values if needed to create a uniform
-   <quote>lower left &mdash; upper right</> internal representation.
-  </para>
-
-  <para>
-   White space is ignored, so <literal>[(<replaceable>x</>),(<replaceable>y</>)]</literal> is the same as
-   <literal>[ ( <replaceable>x</> ), ( <replaceable>y</> ) ]</literal>.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Precision</title>
-
-&common;
-
-  <para>
-   Values are stored internally as 64-bit floating point numbers. This means
-   that numbers with more than about 16 significant digits will be truncated.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Usage</title>
-
-&common;
-
-  <para>
-   The <filename>cube</> module includes a GiST index operator class for
-   <type>cube</> values.
-   The operators supported by the GiST operator class are shown in <xref linkend="cube-gist-operators">.
-  </para>
-
-  <table id="cube-gist-operators">
-   <title>Cube GiST Operators</title>
-   <tgroup cols="2">
-    <thead>
-     <row>
-      <entry>Operator</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>a = b</></entry>
-      <entry>The cubes a and b are identical.</entry>
-     </row>
-
-     <row>
-      <entry><literal>a &amp;&amp; b</></entry>
-      <entry>The cubes a and b overlap.</entry>
-     </row>
-
-     <row>
-      <entry><literal>a @&gt; b</></entry>
-      <entry>The cube a contains the cube b.</entry>
-     </row>
-
-     <row>
-      <entry><literal>a &lt;@ b</></entry>
-      <entry>The cube a is contained in the cube b.</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   (Before PostgreSQL 8.2, the containment operators <literal>@&gt;</> and <literal>&lt;@</> were
-   respectively called <literal>@</> and <literal>~</>.  These names are still available, but are
-   deprecated and will eventually be retired.  Notice that the old names
-   are reversed from the convention formerly followed by the core geometric
-   data types!)
-  </para>
-
-  <para>
-   The standard B-tree operators are also provided, for example
-
-   <informaltable>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Operator</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal>[a, b] &lt; [c, d]</literal></entry>
-       <entry>Less than</entry>
-      </row>
-
-      <row>
-       <entry><literal>[a, b] &gt; [c, d]</literal></entry>
-       <entry>Greater than</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </informaltable>
-
-   These operators do not make a lot of sense for any practical
-   purpose but sorting. These operators first compare (a) to (c),
-   and if these are equal, compare (b) to (d). That results in
-   reasonably good sorting in most cases, which is useful if
-   you want to use ORDER BY with this type.
-  </para>
-
-  <para>
-   <xref linkend="cube-functions-table"> shows the available functions.
-  </para>
-
-  <table id="cube-functions-table">
-   <title>Cube Functions</title>
-   <tgroup cols="2">
-    <tbody>
-     <row>
-      <entry><literal>cube(float8) returns cube</literal></entry>
-      <entry>Makes a one dimensional cube with both coordinates the same.
-       <literal>cube(1) == '(1)'</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube(float8, float8) returns cube</literal></entry>
-      <entry>Makes a one dimensional cube.
-       <literal>cube(1,2) == '(1),(2)'</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube(float8[]) returns cube</literal></entry>
-      <entry>Makes a zero-volume cube using the coordinates
-       defined by the array.
-       <literal>cube(ARRAY[1,2]) == '(1,2)'</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube(float8[], float8[]) returns cube</literal></entry>
-      <entry>Makes a cube with upper right and lower left
-       coordinates as defined by the two arrays, which must be of the
-       same length.
-       <literal>cube('{1,2}'::float[], '{3,4}'::float[]) == '(1,2),(3,4)'
-       </literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube(cube, float8) returns cube</literal></entry>
-      <entry>Makes a new cube by adding a dimension on to an
-       existing cube with the same values for both parts of the new coordinate.
-       This is useful for building cubes piece by piece from calculated values.
-       <literal>cube('(1)',2) == '(1,2),(1,2)'</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube(cube, float8, float8) returns cube</literal></entry>
-      <entry>Makes a new cube by adding a dimension on to an
-       existing cube. This is useful for building cubes piece by piece from
-       calculated values. <literal>cube('(1,2)',3,4) == '(1,3),(2,4)'</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube_dim(cube) returns int</literal></entry>
-      <entry>Returns the number of dimensions of the cube
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube_ll_coord(cube, int) returns double </literal></entry>
-      <entry>Returns the n'th coordinate value for the lower left
-       corner of a cube
-      </entry>
-     </row>
-
-    <row>
-      <entry><literal>cube_ur_coord(cube, int) returns double
-      </literal></entry>
-      <entry>Returns the n'th coordinate value for the
-       upper right corner of a cube
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube_is_point(cube) returns bool</literal></entry>
-      <entry>Returns true if a cube is a point, that is,
-       the two defining corners are the same.</entry>
-     </row>
-
-     <row>
-      <entry><literal>cube_distance(cube, cube) returns double</literal></entry>
-      <entry>Returns the distance between two cubes. If both
-       cubes are points, this is the normal distance function.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube_subset(cube, int[]) returns cube
-      </literal></entry>
-      <entry>Makes a new cube from an existing cube, using a list of
-       dimension indexes from an array. Can be used to find both the LL and UR
-       coordinates of a single dimension, e.g.
-       <literal>cube_subset(cube('(1,3,5),(6,7,8)'), ARRAY[2]) = '(3),(7)'</>.
-       Or can be used to drop dimensions, or reorder them as desired, e.g.
-       <literal>cube_subset(cube('(1,3,5),(6,7,8)'), ARRAY[3,2,1,1]) = '(5, 3,
-       1, 1),(8, 7, 6, 6)'</>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube_union(cube, cube) returns cube</literal></entry>
-      <entry>Produces the union of two cubes
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube_inter(cube, cube) returns cube</literal></entry>
-      <entry>Produces the intersection of two cubes
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>cube_enlarge(cube c, double r, int n) returns cube</literal></entry>
-      <entry>Increases the size of a cube by a specified radius in at least
-       n dimensions. If the radius is negative the cube is shrunk instead. This
-       is useful for creating bounding boxes around a point for searching for
-       nearby points. All defined dimensions are changed by the radius r.
-       LL coordinates are decreased by r and UR coordinates are increased by r.
-       If a LL coordinate is increased to larger than the corresponding UR
-       coordinate (this can only happen when r &lt; 0) than both coordinates
-       are set to their average.  If n is greater than the number of defined
-       dimensions and the cube is being increased (r &gt;= 0) then 0 is used
-       as the base for the extra coordinates.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect2>
-
- <sect2>
-  <title>Defaults</title>
-
-&common;
-
-  <para>
-   I believe this union:
-  </para>
-<programlisting>
-select cube_union('(0,5,2),(2,3,1)', '0');
-cube_union
--------------------
-(0, 0, 0),(2, 5, 2)
-(1 row)
-</programlisting>
-
-   <para>
-    does not contradict common sense, neither does the intersection
-   </para>
-
-<programlisting>
-select cube_inter('(0,-1),(1,1)', '(-2),(2)');
-cube_inter
--------------
-(0, 0),(1, 0)
-(1 row)
-</programlisting>
-
-   <para>
-    In all binary operations on differently-dimensioned cubes, I assume the
-    lower-dimensional one to be a Cartesian projection, i. e., having zeroes
-    in place of coordinates omitted in the string representation. The above
-    examples are equivalent to:
-   </para>
-
-<programlisting>
-cube_union('(0,5,2),(2,3,1)','(0,0,0),(0,0,0)');
-cube_inter('(0,-1),(1,1)','(-2,0),(2,0)');
-</programlisting>
-
-   <para>
-    The following containment predicate uses the point syntax,
-    while in fact the second argument is internally represented by a box.
-    This syntax makes it unnecessary to define a separate point type
-    and functions for (box,point) predicates.
-   </para>
-
-<programlisting>
-select cube_contains('(0,0),(1,1)', '0.5,0.5');
-cube_contains
---------------
-t
-(1 row)
-</programlisting>
- </sect2>
-
- <sect2>
-  <title>Notes</title>
-
-&common;
-
-  <para>
-   For examples of usage, see the regression test <filename>sql/cube.sql</>.
-  </para>
-
-  <para>
-   To make it harder for people to break things, there
-   is a limit of 100 on the number of dimensions of cubes. This is set
-   in <filename>cubedata.h</> if you need something bigger.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Credits</title>
-
-  <para>
-   Original author: Gene Selkov, Jr. <email>[email protected]</email>,
-   Mathematics and Computer Science Division, Argonne National Laboratory.
-  </para>
-
-  <para>
-   My thanks are primarily to Prof. Joe Hellerstein
-   (<ulink url="http://db.cs.berkeley.edu/jmh/"></ulink>) for elucidating the
-   gist of the GiST (<ulink url="http://gist.cs.berkeley.edu/"></ulink>), and
-   to his former student, Andy Dong (<ulink
-   url="http://best.me.berkeley.edu/~adong/"></ulink>), for his example
-   written for Illustra,
-   <ulink url="http://best.berkeley.edu/~adong/rtree/index.html"></ulink>.
-   I am also grateful to all Postgres developers, present and past, for
-   enabling myself to create my own world and live undisturbed in it. And I
-   would like to acknowledge my gratitude to Argonne Lab and to the
-   U.S. Department of Energy for the years of faithful support of my database
-   research.
-  </para>
-
-  <para>
-   Minor updates to this package were made by Bruno Wolff III
-   <email>[email protected]</email> in August/September of 2002. These include
-   changing the precision from single precision to double precision and adding
-   some new functions.
-  </para>
-
-  <para>
-   Additional updates were made by Joshua Reich <email>[email protected]</email> in
-   July 2006. These include <literal>cube(float8[], float8[])</literal> and
-   cleaning up the code to use the V1 call protocol instead of the deprecated
-   V0 protocol.
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/datatype.sgmlin b/doc-xc/src/sgml/datatype.sgmlin
deleted file mode 100644
index 0e7ad9606e..0000000000
--- a/doc-xc/src/sgml/datatype.sgmlin
+++ /dev/null
@@ -1,5067 +0,0 @@
-<!-- doc/src/sgml/datatype.sgml -->
-
- <chapter id="datatype">
-  <title>Data Types</title>
-
-  <indexterm zone="datatype">
-   <primary>data type</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>type</primary>
-   <see>data type</see>
-  </indexterm>
-
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> has a rich set of native data
-   types available to users.  Users can add new types to
-   <productname>PostgreSQL</productname> using the <xref
-   linkend="sql-createtype"> command.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> has inherits from <productname>PostgreSQL</> a rich set of native data
-   types available to users.  Users can add new types to
-   <productname>Postgres-XC</productname> using the <xref
-   linkend="sql-createtype"> command.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> inherits from a rich set of native data
-   types available to users.  Users can add new types to
-   <productname>Postgres-XL</productname> using the <xref
-   linkend="sql-createtype"> command.
-<!## end>
-  </para>
-
-  <para>
-   <xref linkend="datatype-table"> shows all the built-in general-purpose data
-   types. Most of the alternative names listed in the
-   <quote>Aliases</quote> column are the names used internally by
-<!## PG>
-   <productname>PostgreSQL</productname> for historical reasons.  In
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> for historical reasons.  In
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> for historical reasons.  In
-<!## end>
-   addition, some internally used or deprecated types are available,
-   but are not listed here.
-  </para>
-
-   <table id="datatype-table">
-    <title>Data Types</title>
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Name</entry>
-       <entry>Aliases</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><type>bigint</type></entry>
-       <entry><type>int8</type></entry>
-       <entry>signed eight-byte integer</entry>
-      </row>
-
-      <row>
-       <entry><type>bigserial</type></entry>
-       <entry><type>serial8</type></entry>
-       <entry>autoincrementing eight-byte integer</entry>
-      </row>
-
-      <row>
-       <entry><type>bit [ (<replaceable>n</replaceable>) ]</type></entry>
-       <entry></entry>
-       <entry>fixed-length bit string</entry>
-      </row>
-
-      <row>
-       <entry><type>bit varying [ (<replaceable>n</replaceable>) ]</type></entry>
-       <entry><type>varbit</type></entry>
-       <entry>variable-length bit string</entry>
-      </row>
-
-      <row>
-       <entry><type>boolean</type></entry>
-       <entry><type>bool</type></entry>
-       <entry>logical Boolean (true/false)</entry>
-      </row>
-
-      <row>
-       <entry><type>box</type></entry>
-       <entry></entry>
-       <entry>rectangular box on a plane</entry>
-      </row>
-
-      <row>
-       <entry><type>bytea</type></entry>
-       <entry></entry>
-       <entry>binary data (<quote>byte array</>)</entry>
-      </row>
-
-      <row>
-       <entry><type>character varying [ (<replaceable>n</replaceable>) ]</type></entry>
-       <entry><type>varchar [ (<replaceable>n</replaceable>) ]</type></entry>
-       <entry>variable-length character string</entry>
-      </row>
-
-      <row>
-       <entry><type>character [ (<replaceable>n</replaceable>) ]</type></entry>
-       <entry><type>char [ (<replaceable>n</replaceable>) ]</type></entry>
-       <entry>fixed-length character string</entry>
-      </row>
-
-      <row>
-       <entry><type>cidr</type></entry>
-       <entry></entry>
-       <entry>IPv4 or IPv6 network address</entry>
-      </row>
-
-      <row>
-       <entry><type>circle</type></entry>
-       <entry></entry>
-       <entry>circle on a plane</entry>
-      </row>
-
-      <row>
-       <entry><type>date</type></entry>
-       <entry></entry>
-       <entry>calendar date (year, month, day)</entry>
-      </row>
-
-      <row>
-       <entry><type>double precision</type></entry>
-       <entry><type>float8</type></entry>
-       <entry>double precision floating-point number (8 bytes)</entry>
-      </row>
-
-      <row>
-       <entry><type>inet</type></entry>
-       <entry></entry>
-       <entry>IPv4 or IPv6 host address</entry>
-      </row>
-
-      <row>
-       <entry><type>integer</type></entry>
-       <entry><type>int</type>, <type>int4</type></entry>
-       <entry>signed four-byte integer</entry>
-      </row>
-
-      <row>
-       <entry><type>interval [ <replaceable>fields</replaceable> ] [ (<replaceable>p</replaceable>) ]</type></entry>
-       <entry></entry>
-       <entry>time span</entry>
-      </row>
-
-      <row>
-       <entry><type>line</type></entry>
-       <entry></entry>
-       <entry>infinite line on a plane</entry>
-      </row>
-
-      <row>
-       <entry><type>lseg</type></entry>
-       <entry></entry>
-       <entry>line segment on a plane</entry>
-      </row>
-
-      <row>
-       <entry><type>macaddr</type></entry>
-       <entry></entry>
-       <entry>MAC (Media Access Control) address</entry>
-      </row>
-
-      <row>
-       <entry><type>money</type></entry>
-       <entry></entry>
-       <entry>currency amount</entry>
-      </row>
-
-      <row>
-       <entry><type>numeric [ (<replaceable>p</replaceable>,
-         <replaceable>s</replaceable>) ]</type></entry>
-       <entry><type>decimal [ (<replaceable>p</replaceable>,
-         <replaceable>s</replaceable>) ]</type></entry>
-       <entry>exact numeric of selectable precision</entry>
-      </row>
-
-      <row>
-       <entry><type>path</type></entry>
-       <entry></entry>
-       <entry>geometric path on a plane</entry>
-      </row>
-
-      <row>
-       <entry><type>point</type></entry>
-       <entry></entry>
-       <entry>geometric point on a plane</entry>
-      </row>
-
-      <row>
-       <entry><type>polygon</type></entry>
-       <entry></entry>
-       <entry>closed geometric path on a plane</entry>
-      </row>
-
-      <row>
-       <entry><type>real</type></entry>
-       <entry><type>float4</type></entry>
-       <entry>single precision floating-point number (4 bytes)</entry>
-      </row>
-
-      <row>
-       <entry><type>smallint</type></entry>
-       <entry><type>int2</type></entry>
-       <entry>signed two-byte integer</entry>
-      </row>
-
-      <row>
-       <entry><type>serial</type></entry>
-       <entry><type>serial4</type></entry>
-       <entry>autoincrementing four-byte integer</entry>
-      </row>
-
-      <row>
-       <entry><type>text</type></entry>
-       <entry></entry>
-       <entry>variable-length character string</entry>
-      </row>
-
-      <row>
-       <entry><type>time [ (<replaceable>p</replaceable>) ] [ without time zone ]</type></entry>
-       <entry></entry>
-       <entry>time of day (no time zone)</entry>
-      </row>
-
-      <row>
-       <entry><type>time [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
-       <entry><type>timetz</type></entry>
-       <entry>time of day, including time zone</entry>
-      </row>
-
-      <row>
-       <entry><type>timestamp [ (<replaceable>p</replaceable>) ] [ without time zone ]</type></entry>
-       <entry></entry>
-       <entry>date and time (no time zone)</entry>
-      </row>
-
-      <row>
-       <entry><type>timestamp [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
-       <entry><type>timestamptz</type></entry>
-       <entry>date and time, including time zone</entry>
-      </row>
-
-      <row>
-       <entry><type>tsquery</type></entry>
-       <entry></entry>
-       <entry>text search query</entry>
-      </row>
-
-      <row>
-       <entry><type>tsvector</type></entry>
-       <entry></entry>
-       <entry>text search document</entry>
-      </row>
-
-      <row>
-       <entry><type>txid_snapshot</type></entry>
-       <entry></entry>
-       <entry>user-level transaction ID snapshot</entry>
-      </row>
-
-      <row>
-       <entry><type>uuid</type></entry>
-       <entry></entry>
-       <entry>universally unique identifier</entry>
-      </row>
-
-      <row>
-       <entry><type>xml</type></entry>
-       <entry></entry>
-       <entry>XML data</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <note>
-   <title>Compatibility</title>
-   <para>
-    The following types (or spellings thereof) are specified by
-    <acronym>SQL</acronym>: <type>bigint</type>, <type>bit</type>, <type>bit
-    varying</type>, <type>boolean</type>, <type>char</type>,
-    <type>character varying</type>, <type>character</type>,
-    <type>varchar</type>, <type>date</type>, <type>double
-    precision</type>, <type>integer</type>, <type>interval</type>,
-    <type>numeric</type>, <type>decimal</type>, <type>real</type>,
-    <type>smallint</type>, <type>time</type> (with or without time zone),
-    <type>timestamp</type> (with or without time zone),
-    <type>xml</type>.
-   </para>
-  </note>
-
-  <para>
-   Each data type has an external representation determined by its input
-   and output functions.  Many of the built-in types have
-   obvious external formats.  However, several types are either unique
-<!## PG>
-   to <productname>PostgreSQL</productname>, such as geometric
-<!## end>
-<!## XC>
-   to <productname>Postgres-XC</productname>, such as geometric
-<!## end>
-<!## XL>
-   to <productname>Postgres-XL</productname>, such as geometric
-<!## end>
-   paths, or have several possible formats, such as the date
-   and time types.
-   Some of the input and output functions are not invertible, i.e.,
-   the result of an output function might lose accuracy when compared to
-   the original input.
-  </para>
-
-  <sect1 id="datatype-numeric">
-   <title>Numeric Types</title>
-
-   <indexterm zone="datatype-numeric">
-    <primary>data type</primary>
-    <secondary>numeric</secondary>
-   </indexterm>
-&common;
-   <para>
-    Numeric types consist of two-, four-, and eight-byte integers,
-    four- and eight-byte floating-point numbers, and selectable-precision
-    decimals.  <xref linkend="datatype-numeric-table"> lists the
-    available types.
-   </para>
-
-    <table id="datatype-numeric-table">
-     <title>Numeric Types</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Name</entry>
-        <entry>Storage Size</entry>
-        <entry>Description</entry>
-        <entry>Range</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry><type>smallint</></entry>
-        <entry>2 bytes</entry>
-        <entry>small-range integer</entry>
-        <entry>-32768 to +32767</entry>
-       </row>
-       <row>
-        <entry><type>integer</></entry>
-        <entry>4 bytes</entry>
-        <entry>typical choice for integer</entry>
-        <entry>-2147483648 to +2147483647</entry>
-       </row>
-       <row>
-        <entry><type>bigint</></entry>
-        <entry>8 bytes</entry>
-        <entry>large-range integer</entry>
-        <entry>-9223372036854775808 to 9223372036854775807</entry>
-       </row>
-
-       <row>
-        <entry><type>decimal</></entry>
-        <entry>variable</entry>
-        <entry>user-specified precision, exact</entry>
-        <entry>up to 131072 digits before the decimal point; up to 16383 digits after the decimal point</entry>
-       </row>
-       <row>
-        <entry><type>numeric</></entry>
-        <entry>variable</entry>
-        <entry>user-specified precision, exact</entry>
-        <entry>up to 131072 digits before the decimal point; up to 16383 digits after the decimal point</entry>
-       </row>
-
-       <row>
-        <entry><type>real</></entry>
-        <entry>4 bytes</entry>
-        <entry>variable-precision, inexact</entry>
-        <entry>6 decimal digits precision</entry>
-       </row>
-       <row>
-        <entry><type>double precision</></entry>
-        <entry>8 bytes</entry>
-        <entry>variable-precision, inexact</entry>
-        <entry>15 decimal digits precision</entry>
-       </row>
-
-       <row>
-        <entry><type>serial</></entry>
-        <entry>4 bytes</entry>
-        <entry>autoincrementing integer</entry>
-        <entry>1 to 2147483647</entry>
-       </row>
-
-       <row>
-        <entry><type>bigserial</type></entry>
-        <entry>8 bytes</entry>
-        <entry>large autoincrementing integer</entry>
-        <entry>1 to 9223372036854775807</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    The syntax of constants for the numeric types is described in
-    <xref linkend="sql-syntax-constants">.  The numeric types have a
-    full set of corresponding arithmetic operators and
-    functions. Refer to <xref linkend="functions"> for more
-    information.  The following sections describe the types in detail.
-   </para>
-
-   <sect2 id="datatype-int">
-    <title>Integer Types</title>
-
-    <indexterm zone="datatype-int">
-     <primary>integer</primary>
-    </indexterm>
-
-    <indexterm zone="datatype-int">
-     <primary>smallint</primary>
-    </indexterm>
-
-    <indexterm zone="datatype-int">
-     <primary>bigint</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>int4</primary>
-     <see>integer</see>
-    </indexterm>
-
-    <indexterm>
-     <primary>int2</primary>
-     <see>smallint</see>
-    </indexterm>
-
-    <indexterm>
-     <primary>int8</primary>
-     <see>bigint</see>
-    </indexterm>
-&common;
-    <para>
-     The types <type>smallint</type>, <type>integer</type>, and
-     <type>bigint</type> store whole numbers, that is, numbers without
-     fractional components, of various ranges.  Attempts to store
-     values outside of the allowed range will result in an error.
-    </para>
-
-    <para>
-     The type <type>integer</type> is the common choice, as it offers
-     the best balance between range, storage size, and performance.
-     The <type>smallint</type> type is generally only used if disk
-     space is at a premium.  The <type>bigint</type> type should only
-     be used if the range of the <type>integer</type> type is insufficient,
-     because the latter is definitely faster.
-    </para>
-
-    <para>
-     On very minimal operating systems the <type>bigint</type> type
-     might not function correctly, because it relies on compiler support
-     for eight-byte integers.  On such machines, <type>bigint</type>
-     acts the same as <type>integer</type>, but still takes up eight
-     bytes of storage.  (We are not aware of any modern
-     platform where this is the case.)
-    </para>
-
-    <para>
-     <acronym>SQL</acronym> only specifies the integer types
-     <type>integer</type> (or <type>int</type>),
-     <type>smallint</type>, and <type>bigint</type>.  The
-     type names <type>int2</type>, <type>int4</type>, and
-     <type>int8</type> are extensions, which are also used by some
-     other <acronym>SQL</acronym> database systems.
-    </para>
-
-   </sect2>
-
-   <sect2 id="datatype-numeric-decimal">
-    <title>Arbitrary Precision Numbers</title>
-
-    <indexterm>
-     <primary>numeric (data type)</primary>
-    </indexterm>
-
-   <indexterm>
-    <primary>arbitrary precision numbers</primary>
-   </indexterm>
-
-    <indexterm>
-     <primary>decimal</primary>
-     <see>numeric</see>
-    </indexterm>
-&common;
-    <para>
-     The type <type>numeric</type> can store numbers with a
-     very large number of digits and perform calculations exactly. It is
-     especially recommended for storing monetary amounts and other
-     quantities where exactness is required. However, arithmetic on
-     <type>numeric</type> values is very slow compared to the integer
-     types, or to the floating-point types described in the next section.
-    </para>
-
-    <para>
-     We use the following terms below:  The
-     <firstterm>scale</firstterm> of a <type>numeric</type> is the
-     count of decimal digits in the fractional part, to the right of
-     the decimal point.  The <firstterm>precision</firstterm> of a
-     <type>numeric</type> is the total count of significant digits in
-     the whole number, that is, the number of digits to both sides of
-     the decimal point.  So the number 23.5141 has a precision of 6
-     and a scale of 4.  Integers can be considered to have a scale of
-     zero.
-    </para>
-
-    <para>
-     Both the maximum precision and the maximum scale of a
-     <type>numeric</type> column can be
-     configured.  To declare a column of type <type>numeric</type> use
-     the syntax:
-<programlisting>
-NUMERIC(<replaceable>precision</replaceable>, <replaceable>scale</replaceable>)
-</programlisting>
-     The precision must be positive, the scale zero or positive.
-     Alternatively:
-<programlisting>
-NUMERIC(<replaceable>precision</replaceable>)
-</programlisting>
-     selects a scale of 0.  Specifying:
-<programlisting>
-NUMERIC
-</programlisting>
-     without any precision or scale creates a column in which numeric
-     values of any precision and scale can be stored, up to the
-     implementation limit on precision.  A column of this kind will
-     not coerce input values to any particular scale, whereas
-     <type>numeric</type> columns with a declared scale will coerce
-     input values to that scale.  (The <acronym>SQL</acronym> standard
-     requires a default scale of 0, i.e., coercion to integer
-     precision.  We find this a bit useless.  If you're concerned
-     about portability, always specify the precision and scale
-     explicitly.)
-    </para>
-
-    <note>
-     <para>
-      The maximum allowed precision when explicitly specified in the
-      type declaration is 1000; <type>NUMERIC</type> without a specified
-      precision is subject to the limits described in <xref
-      linkend="datatype-numeric-table">.
-     </para>
-    </note>
-
-    <para>
-     If the scale of a value to be stored is greater than the declared
-     scale of the column, the system will round the value to the specified
-     number of fractional digits.  Then, if the number of digits to the
-     left of the decimal point exceeds the declared precision minus the
-     declared scale, an error is raised.
-    </para>
-
-    <para>
-     Numeric values are physically stored without any extra leading or
-     trailing zeroes.  Thus, the declared precision and scale of a column
-     are maximums, not fixed allocations.  (In this sense the <type>numeric</>
-     type is more akin to <type>varchar(<replaceable>n</>)</type>
-     than to <type>char(<replaceable>n</>)</type>.)  The actual storage
-     requirement is two bytes for each group of four decimal digits,
-     plus five to eight bytes overhead.
-    </para>
-
-    <indexterm>
-     <primary>NaN</primary>
-     <see>not a number</see>
-   </indexterm>
-
-    <indexterm>
-     <primary>not a number</primary>
-     <secondary>numeric (data type)</secondary>
-    </indexterm>
-
-    <para>
-     In addition to ordinary numeric values, the <type>numeric</type>
-     type allows the special value <literal>NaN</>, meaning
-     <quote>not-a-number</quote>.  Any operation on <literal>NaN</>
-     yields another <literal>NaN</>.  When writing this value
-     as a constant in an SQL command, you must put quotes around it,
-     for example <literal>UPDATE table SET x = 'NaN'</>.  On input,
-     the string <literal>NaN</> is recognized in a case-insensitive manner.
-    </para>
-
-    <note>
-     <para>
-      In most implementations of the <quote>not-a-number</> concept,
-      <literal>NaN</> is not considered equal to any other numeric
-      value (including <literal>NaN</>).  In order to allow
-      <type>numeric</> values to be sorted and used in tree-based
-<!## PG>
-      indexes, <productname>PostgreSQL</> treats <literal>NaN</>
-<!## end>
-<!## XC>
-      indexes, <productname>Postgres-XC</> treats <literal>NaN</>
-<!## end>
-<!## XL>
-      indexes, <productname>Postgres-XL</> treats <literal>NaN</>
-<!## end>
-      values as equal, and greater than all non-<literal>NaN</>
-      values.
-     </para>
-    </note>
-
-    <para>
-     The types <type>decimal</type> and <type>numeric</type> are
-     equivalent.  Both types are part of the <acronym>SQL</acronym>
-     standard.
-    </para>
-   </sect2>
-
-
-   <sect2 id="datatype-float">
-    <title>Floating-Point Types</title>
-
-    <indexterm zone="datatype-float">
-     <primary>real</primary>
-    </indexterm>
-
-    <indexterm zone="datatype-float">
-     <primary>double precision</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>float4</primary>
-     <see>real</see>
-    </indexterm>
-
-    <indexterm>
-     <primary>float8</primary>
-     <see>double precision</see>
-    </indexterm>
-
-    <indexterm zone="datatype-float">
-     <primary>floating point</primary>
-    </indexterm>
-&common;
-    <para>
-     The data types <type>real</type> and <type>double
-     precision</type> are inexact, variable-precision numeric types.
-     In practice, these types are usually implementations of
-     <acronym>IEEE</acronym> Standard 754 for Binary Floating-Point
-     Arithmetic (single and double precision, respectively), to the
-     extent that the underlying processor, operating system, and
-     compiler support it.
-    </para>
-
-    <para>
-     Inexact means that some values cannot be converted exactly to the
-     internal format and are stored as approximations, so that storing
-     and retrieving a value might show slight discrepancies.
-     Managing these errors and how they propagate through calculations
-     is the subject of an entire branch of mathematics and computer
-     science and will not be discussed here, except for the
-     following points:
-     <itemizedlist>
-      <listitem>
-       <para>
-        If you require exact storage and calculations (such as for
-        monetary amounts), use the <type>numeric</type> type instead.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        If you want to do complicated calculations with these types
-        for anything important, especially if you rely on certain
-        behavior in boundary cases (infinity, underflow), you should
-        evaluate the implementation carefully.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Comparing two floating-point values for equality might not
-        always work as expected.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     On most platforms, the <type>real</type> type has a range of at least
-     1E-37 to 1E+37 with a precision of at least 6 decimal digits.  The
-     <type>double precision</type> type typically has a range of around
-     1E-307 to 1E+308 with a precision of at least 15 digits.  Values that
-     are too large or too small will cause an error.  Rounding might
-     take place if the precision of an input number is too high.
-     Numbers too close to zero that are not representable as distinct
-     from zero will cause an underflow error.
-    </para>
-
-    <indexterm>
-     <primary>not a number</primary>
-     <secondary>double precision</secondary>
-    </indexterm>
-
-    <para>
-     In addition to ordinary numeric values, the floating-point types
-     have several special values:
-<literallayout>
-<literal>Infinity</literal>
-<literal>-Infinity</literal>
-<literal>NaN</literal>
-</literallayout>
-     These represent the IEEE 754 special values
-     <quote>infinity</quote>, <quote>negative infinity</quote>, and
-     <quote>not-a-number</quote>, respectively.  (On a machine whose
-     floating-point arithmetic does not follow IEEE 754, these values
-     will probably not work as expected.)  When writing these values
-     as constants in an SQL command, you must put quotes around them,
-     for example <literal>UPDATE table SET x = 'Infinity'</>.  On input,
-     these strings are recognized in a case-insensitive manner.
-    </para>
-
-    <note>
-     <para>
-      IEEE754 specifies that <literal>NaN</> should not compare equal
-      to any other floating-point value (including <literal>NaN</>).
-      In order to allow floating-point values to be sorted and used
-<!## PG>
-       in tree-based indexes, <productname>PostgreSQL</> treats
-<!## end>
-<!## XC>
-      in tree-based indexes, <productname>Postgres-XC</> treats
-<!## end>
-<!## XL>
-      in tree-based indexes, <productname>Postgres-XL</> treats
-<!## end>
-      <literal>NaN</> values as equal, and greater than all
-      non-<literal>NaN</> values.
-     </para>
-    </note>
-
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> also supports the SQL-standard
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> also supports the SQL-standard
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> also supports the SQL-standard
-<!## end>
-     notations <type>float</type> and
-     <type>float(<replaceable>p</replaceable>)</type> for specifying
-     inexact numeric types.  Here, <replaceable>p</replaceable> specifies
-     the minimum acceptable precision in <emphasis>binary</> digits.
-<!## PG>
-     <productname>PostgreSQL</productname> accepts
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> accepts 
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> accepts 
-<!## end>
-     <type>float(1)</type> to <type>float(24)</type> as selecting the
-     <type>real</type> type, while
-     <type>float(25)</type> to <type>float(53)</type> select
-     <type>double precision</type>.  Values of <replaceable>p</replaceable>
-     outside the allowed range draw an error.
-     <type>float</type> with no precision specified is taken to mean
-     <type>double precision</type>.
-    </para>
-
-    <note>
-     <para>
-      Prior to <productname>PostgreSQL</productname> 7.4, the precision in
-      <type>float(<replaceable>p</replaceable>)</type> was taken to mean
-      so many <emphasis>decimal</> digits.  This has been corrected to match the SQL
-      standard, which specifies that the precision is measured in binary
-      digits.  The assumption that <type>real</type> and
-      <type>double precision</type> have exactly 24 and 53 bits in the
-      mantissa respectively is correct for IEEE-standard floating point
-      implementations.  On non-IEEE platforms it might be off a little, but
-      for simplicity the same ranges of <replaceable>p</replaceable> are used
-      on all platforms.
-     </para>
-    </note>
-
-   </sect2>
-
-   <sect2 id="datatype-serial">
-    <title>Serial Types</title>
-
-    <indexterm zone="datatype-serial">
-     <primary>serial</primary>
-    </indexterm>
-
-    <indexterm zone="datatype-serial">
-     <primary>bigserial</primary>
-    </indexterm>
-
-    <indexterm zone="datatype-serial">
-     <primary>serial4</primary>
-    </indexterm>
-
-    <indexterm zone="datatype-serial">
-     <primary>serial8</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>auto-increment</primary>
-     <see>serial</see>
-    </indexterm>
-
-    <indexterm>
-     <primary>sequence</primary>
-     <secondary>and serial type</secondary>
-    </indexterm>
-&common;
-    <para>
-     The data types <type>serial</type> and <type>bigserial</type>
-     are not true types, but merely
-     a notational convenience for creating unique identifier columns
-     (similar to the <literal>AUTO_INCREMENT</literal> property
-     supported by some other databases). In the current
-     implementation, specifying:
-
-<programlisting>
-CREATE TABLE <replaceable class="parameter">tablename</replaceable> (
-    <replaceable class="parameter">colname</replaceable> SERIAL
-);
-</programlisting>
-
-     is equivalent to specifying:
-
-<programlisting>
-CREATE SEQUENCE <replaceable class="parameter">tablename</replaceable>_<replaceable class="parameter">colname</replaceable>_seq;
-CREATE TABLE <replaceable class="parameter">tablename</replaceable> (
-    <replaceable class="parameter">colname</replaceable> integer NOT NULL DEFAULT nextval('<replaceable class="parameter">tablename</replaceable>_<replaceable class="parameter">colname</replaceable>_seq')
-);
-ALTER SEQUENCE <replaceable class="parameter">tablename</replaceable>_<replaceable class="parameter">colname</replaceable>_seq OWNED BY <replaceable class="parameter">tablename</replaceable>.<replaceable class="parameter">colname</replaceable>;
-</programlisting>
-
-     Thus, we have created an integer column and arranged for its default
-     values to be assigned from a sequence generator.  A <literal>NOT NULL</>
-     constraint is applied to ensure that a null value cannot be
-     inserted.  (In most cases you would also want to attach a
-     <literal>UNIQUE</> or <literal>PRIMARY KEY</> constraint to prevent
-     duplicate values from being inserted by accident, but this is
-     not automatic.)  Lastly, the sequence is marked as <quote>owned by</>
-     the column, so that it will be dropped if the column or table is dropped.
-    </para>
-
-    <note>
-     <para>
-      Prior to <productname>PostgreSQL</productname> 7.3, <type>serial</type>
-      implied <literal>UNIQUE</literal>.  This is no longer automatic.  If
-      you wish a serial column to have a unique constraint or be a
-      primary key, it must now be specified, just like
-      any other data type.
-     </para>
-    </note>
-
-    <para>
-     To insert the next value of the sequence into the <type>serial</type>
-     column, specify that the <type>serial</type>
-     column should be assigned its default value. This can be done
-     either by excluding the column from the list of columns in
-     the <command>INSERT</command> statement, or through the use of
-     the <literal>DEFAULT</literal> key word.
-    </para>
-
-    <para>
-     The type names <type>serial</type> and <type>serial4</type> are
-     equivalent: both create <type>integer</type> columns.  The type
-     names <type>bigserial</type> and <type>serial8</type> work
-     the same way, except that they create a <type>bigint</type>
-     column.  <type>bigserial</type> should be used if you anticipate
-     the use of more than 2<superscript>31</> identifiers over the
-     lifetime of the table.
-    </para>
-
-    <para>
-     The sequence created for a <type>serial</type> column is
-     automatically dropped when the owning column is dropped.
-     You can drop the sequence without dropping the column, but this
-     will force removal of the column default expression.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="datatype-money">
-   <title>Monetary Types</title>
-
-&common;
-   <para>
-    The <type>money</type> type stores a currency amount with a fixed
-    fractional precision; see <xref
-    linkend="datatype-money-table">.  The fractional precision is
-    determined by the database's <xref linkend="guc-lc-monetary"> setting.
-    The range shown in the table assumes there are two fractional digits.
-    Input is accepted in a variety of formats, including integer and
-    floating-point literals, as well as typical
-    currency formatting, such as <literal>'$1,000.00'</literal>.
-    Output is generally in the latter form but depends on the locale.
-   </para>
-
-    <table id="datatype-money-table">
-     <title>Monetary Types</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Name</entry>
-        <entry>Storage Size</entry>
-        <entry>Description</entry>
-        <entry>Range</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>money</entry>
-        <entry>8 bytes</entry>
-        <entry>currency amount</entry>
-        <entry>-92233720368547758.08 to +92233720368547758.07</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Since the output of this data type is locale-sensitive, it might not
-    work to load <type>money</> data into a database that has a different
-    setting of <varname>lc_monetary</>.  To avoid problems, before
-    restoring a dump into a new database make sure <varname>lc_monetary</> has
-    the same or equivalent value as in the database that was dumped.
-   </para>
-
-   <para>
-    Values of the <type>numeric</type>, <type>int</type>, and
-    <type>bigint</type> data types can be cast to <type>money</type>.
-    Conversion from the <type>real</type> and <type>double precision</type>
-    data types can be done by casting to <type>numeric</type> first, for
-    example:
-<programlisting>
-SELECT '12.34'::float8::numeric::money;
-</programlisting>
-    However, this is not recommended.  Floating point numbers should not be
-    used to handle money due to the potential for rounding errors.
-   </para>
-
-   <para>
-    A <type>money</type> value can be cast to <type>numeric</type> without
-    loss of precision. Conversion to other types could potentially lose
-    precision, and must also be done in two stages:
-<programlisting>
-SELECT '52093.89'::money::numeric::float8;
-</programlisting>
-   </para>
-
-   <para>
-    When a <type>money</type> value is divided by another <type>money</type>
-    value, the result is <type>double precision</type> (i.e., a pure number,
-    not money); the currency units cancel each other out in the division.
-   </para>
-  </sect1>
-
-
-  <sect1 id="datatype-character">
-   <title>Character Types</title>
-
-   <indexterm zone="datatype-character">
-    <primary>character string</primary>
-    <secondary>data types</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>string</primary>
-    <see>character string</see>
-   </indexterm>
-
-   <indexterm zone="datatype-character">
-    <primary>character</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-character">
-    <primary>character varying</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-character">
-    <primary>text</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-character">
-    <primary>char</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-character">
-    <primary>varchar</primary>
-   </indexterm>
-
-&common;
-    <table id="datatype-character-table">
-     <title>Character Types</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>Name</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><type>character varying(<replaceable>n</>)</type>, <type>varchar(<replaceable>n</>)</type></entry>
-        <entry>variable-length with limit</entry>
-       </row>
-       <row>
-        <entry><type>character(<replaceable>n</>)</type>, <type>char(<replaceable>n</>)</type></entry>
-        <entry>fixed-length, blank padded</entry>
-       </row>
-       <row>
-        <entry><type>text</type></entry>
-        <entry>variable unlimited length</entry>
-       </row>
-     </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    <xref linkend="datatype-character-table"> shows the
-    general-purpose character types available in
-<!## PG>
-    <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>.
-<!## end>
-   </para>
-
-   <para>
-    <acronym>SQL</acronym> defines two primary character types:
-    <type>character varying(<replaceable>n</>)</type> and
-    <type>character(<replaceable>n</>)</type>, where <replaceable>n</>
-    is a positive integer.  Both of these types can store strings up to
-    <replaceable>n</> characters (not bytes) in length.  An attempt to store a
-    longer string into a column of these types will result in an
-    error, unless the excess characters are all spaces, in which case
-    the string will be truncated to the maximum length. (This somewhat
-    bizarre exception is required by the <acronym>SQL</acronym>
-    standard.) If the string to be stored is shorter than the declared
-    length, values of type <type>character</type> will be space-padded;
-    values of type <type>character varying</type> will simply store the
-    shorter
-    string.
-   </para>
-
-   <para>
-    If one explicitly casts a value to <type>character
-    varying(<replaceable>n</>)</type> or
-    <type>character(<replaceable>n</>)</type>, then an over-length
-    value will be truncated to <replaceable>n</> characters without
-    raising an error. (This too is required by the
-    <acronym>SQL</acronym> standard.)
-   </para>
-
-   <para>
-    The notations <type>varchar(<replaceable>n</>)</type> and
-    <type>char(<replaceable>n</>)</type> are aliases for <type>character
-    varying(<replaceable>n</>)</type> and
-    <type>character(<replaceable>n</>)</type>, respectively.
-    <type>character</type> without length specifier is equivalent to
-    <type>character(1)</type>. If <type>character varying</type> is used
-    without length specifier, the type accepts strings of any size. The
-<!## PG>
-    latter is a <productname>PostgreSQL</> extension.
-<!## end>
-<!## XC>
-    latter is a <productname>Postgres-XC</>, as well as <productname>PostgreSQL</> extension.
-<!## end>
-<!## XL>
-    latter is a <productname>Postgres-XL</>, as well as <productname>PostgreSQL</> extension.
-<!## end>
-   </para>
-
-   <para>
-<!## PG>
-    In addition, <productname>PostgreSQL</productname> provides the
-<!## end>
-<!## XC>
-    In addition, <productname>Postgres-XC</productname> provides the
-<!## end>
-<!## XL>
-    In addition, <productname>Postgres-XL</productname> provides the
-<!## end>
-    <type>text</type> type, which stores strings of any length.
-    Although the type <type>text</type> is not in the
-    <acronym>SQL</acronym> standard, several other SQL database
-    management systems have it as well.
-   </para>
-
-   <para>
-    Values of type <type>character</type> are physically padded
-    with spaces to the specified width <replaceable>n</>, and are
-    stored and displayed that way.  However, the padding spaces are
-    treated as semantically insignificant.  Trailing spaces are
-    disregarded when comparing two values of type <type>character</type>,
-    and they will be removed when converting a <type>character</type> value
-    to one of the other string types.  Note that trailing spaces
-    <emphasis>are</> semantically significant in
-    <type>character varying</type> and <type>text</type> values, and
-    when using pattern matching, e.g. <literal>LIKE</>,
-    regular expressions.
-   </para>
-
-   <para>
-    The storage requirement for a short string (up to 126 bytes) is 1 byte
-    plus the actual string, which includes the space padding in the case of
-    <type>character</type>.  Longer strings have 4 bytes of overhead instead
-    of 1.  Long strings are compressed by the system automatically, so
-    the physical requirement on disk might be less. Very long values are also
-    stored in background tables so that they do not interfere with rapid
-    access to shorter column values. In any case, the longest
-    possible character string that can be stored is about 1 GB. (The
-    maximum value that will be allowed for <replaceable>n</> in the data
-    type declaration is less than that. It wouldn't be useful to
-    change this because with multibyte character encodings the number of
-    characters and bytes can be quite different. If you desire to
-    store long strings with no specific upper limit, use
-    <type>text</type> or <type>character varying</type> without a length
-    specifier, rather than making up an arbitrary length limit.)
-   </para>
-
-   <tip>
-    <para>
-     There is no performance difference among these three types,
-     apart from increased storage space when using the blank-padded
-     type, and a few extra CPU cycles to check the length when storing into
-     a length-constrained column.  While
-     <type>character(<replaceable>n</>)</type> has performance
-     advantages in some other database systems, there is no such advantage in
-<!## PG>
-     <productname>PostgreSQL</productname>; in fact
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname>; in fact
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname>; in fact
-<!## end>
-     <type>character(<replaceable>n</>)</type> is usually the slowest of
-     the three because of its additional storage costs.  In most situations
-     <type>text</type> or <type>character varying</type> should be used
-     instead.
-    </para>
-   </tip>
-
-   <para>
-    Refer to <xref linkend="sql-syntax-strings"> for information about
-    the syntax of string literals, and to <xref linkend="functions">
-    for information about available operators and functions. The
-    database character set determines the character set used to store
-    textual values; for more information on character set support,
-    refer to <xref linkend="multibyte">.
-   </para>
-
-   <example>
-    <title>Using the Character Types</title>
-
-<programlisting>
-CREATE TABLE test1 (a character(4));
-INSERT INTO test1 VALUES ('ok');
-SELECT a, char_length(a) FROM test1; -- <co id="co.datatype-char">
-<computeroutput>
-  a   | char_length
-------+-------------
- ok   |           2
-</computeroutput>
-
-CREATE TABLE test2 (b varchar(5));
-INSERT INTO test2 VALUES ('ok');
-INSERT INTO test2 VALUES ('good      ');
-INSERT INTO test2 VALUES ('too long');
-<computeroutput>ERROR:  value too long for type character varying(5)</computeroutput>
-INSERT INTO test2 VALUES ('too long'::varchar(5)); -- explicit truncation
-SELECT b, char_length(b) FROM test2;
-<computeroutput>
-   b   | char_length
--------+-------------
- ok    |           2
- good  |           5
- too l |           5
-</computeroutput>
-</programlisting>
-    <calloutlist>
-     <callout arearefs="co.datatype-char">
-      <para>
-       The <function>char_length</function> function is discussed in
-       <xref linkend="functions-string">.
-      </para>
-     </callout>
-    </calloutlist>
-   </example>
-
-   <para>
-    There are two other fixed-length character types in
-<!## PG>
-    <productname>PostgreSQL</productname>, shown in <xref
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>, shown in <xref
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>, shown in <xref
-<!## end>
-    linkend="datatype-character-special-table">. The <type>name</type>
-    type exists <emphasis>only</emphasis> for the storage of identifiers
-    in the internal system catalogs and is not intended for use by the general user. Its
-    length is currently defined as 64 bytes (63 usable characters plus
-    terminator) but should be referenced using the constant
-    <symbol>NAMEDATALEN</symbol> in <literal>C</> source code.
-    The length is set at compile time (and
-    is therefore adjustable for special uses); the default maximum
-    length might change in a future release. The type <type>"char"</type>
-    (note the quotes) is different from <type>char(1)</type> in that it
-    only uses one byte of storage. It is internally used in the system
-    catalogs as a simplistic enumeration type.
-   </para>
-
-    <table id="datatype-character-special-table">
-     <title>Special Character Types</title>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Name</entry>
-        <entry>Storage Size</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><type>"char"</type></entry>
-        <entry>1 byte</entry>
-        <entry>single-byte internal type</entry>
-       </row>
-       <row>
-        <entry><type>name</type></entry>
-        <entry>64 bytes</entry>
-        <entry>internal type for object names</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-  </sect1>
-
- <sect1 id="datatype-binary">
-  <title>Binary Data Types</title>
-
-  <indexterm zone="datatype-binary">
-   <primary>binary data</primary>
-  </indexterm>
-
-  <indexterm zone="datatype-binary">
-   <primary>bytea</primary>
-  </indexterm>
-&common;
-   <para>
-    The <type>bytea</type> data type allows storage of binary strings;
-    see <xref linkend="datatype-binary-table">.
-   </para>
-
-   <table id="datatype-binary-table">
-    <title>Binary Data Types</title>
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Name</entry>
-       <entry>Storage Size</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry><type>bytea</type></entry>
-       <entry>1 or 4 bytes plus the actual binary string</entry>
-       <entry>variable-length binary string</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    A binary string is a sequence of octets (or bytes).  Binary
-    strings are distinguished from character strings in two
-    ways.  First, binary strings specifically allow storing
-    octets of value zero and other <quote>non-printable</quote>
-    octets (usually, octets outside the range 32 to 126).
-    Character strings disallow zero octets, and also disallow any
-    other octet values and sequences of octet values that are invalid
-    according to the database's selected character set encoding.
-    Second, operations on binary strings process the actual bytes,
-    whereas the processing of character strings depends on locale settings.
-    In short, binary strings are appropriate for storing data that the
-    programmer thinks of as <quote>raw bytes</>, whereas character
-    strings are appropriate for storing text.
-   </para>
-
-   <para>
-    The <type>bytea</type> type supports two external formats for
-<!## PG>
-    input and output: <productname>PostgreSQL</productname>'s historical
-<!## end>
-<!## XC>
-    input and output: <productname>Postgres-XC</productname>'s historical
-<!## end>
-<!## XL>
-    input and output: <productname>Postgres-XL</productname>'s historical
-<!## end>
-    <quote>escape</quote> format, and <quote>hex</quote> format.  Both
-    of these are always accepted on input.  The output format depends
-    on the configuration parameter <xref linkend="guc-bytea-output">;
-    the default is hex.  (Note that the hex format was introduced in
-    <productname>PostgreSQL</productname> 9.0; earlier versions and some
-    tools don't understand it.)
-   </para>
-
-   <para>
-    The <acronym>SQL</acronym> standard defines a different binary
-    string type, called <type>BLOB</type> or <type>BINARY LARGE
-    OBJECT</type>.  The input format is different from
-    <type>bytea</type>, but the provided functions and operators are
-    mostly the same.
-   </para>
-
-  <sect2>
-   <title><type>bytea</> Hex Format</title>
-
-&common;
-   <para>
-    The <quote>hex</> format encodes binary data as 2 hexadecimal digits
-    per byte, most significant nibble first.  The entire string is
-    preceded by the sequence <literal>\x</literal> (to distinguish it
-    from the escape format).  In some contexts, the initial backslash may
-    need to be escaped by doubling it, in the same cases in which backslashes
-    have to be doubled in escape format; details appear below.
-    The hexadecimal digits can
-    be either upper or lower case, and whitespace is permitted between
-    digit pairs (but not within a digit pair nor in the starting
-    <literal>\x</literal> sequence).
-    The hex format is compatible with a wide
-    range of external applications and protocols, and it tends to be
-    faster to convert than the escape format, so its use is preferred.
-   </para>
-
-   <para>
-    Example:
-<programlisting>
-SELECT E'\\xDEADBEEF';
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title><type>bytea</> Escape Format</title>
-
-&common;
-   <para>
-    The <quote>escape</quote> format is the traditional
-<!## PG>
-    <productname>PostgreSQL</productname> format for the <type>bytea</type>
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> format for the <type>bytea</type>
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> format for the <type>bytea</type>
-<!## end>
-    type.  It
-    takes the approach of representing a binary string as a sequence
-    of ASCII characters, while converting those bytes that cannot be
-    represented as an ASCII character into special escape sequences.
-    If, from the point of view of the application, representing bytes
-    as characters makes sense, then this representation can be
-    convenient.  But in practice it is usually confusing because it
-    fuzzes up the distinction between binary strings and character
-    strings, and also the particular escape mechanism that was chosen is
-    somewhat unwieldy.  So this format should probably be avoided
-    for most new applications.
-   </para>
-
-   <para>
-    When entering <type>bytea</type> values in escape format,
-    octets of certain
-    values <emphasis>must</emphasis> be escaped, while all octet
-    values <emphasis>can</emphasis> be escaped.  In
-    general, to escape an octet, convert it into its three-digit
-    octal value and precede it
-    by a backslash (or two backslashes, if writing the value as a
-    literal using escape string syntax).
-    Backslash itself (octet value 92) can alternatively be represented by
-    double backslashes.
-    <xref linkend="datatype-binary-sqlesc">
-    shows the characters that must be escaped, and gives the alternative
-    escape sequences where applicable.
-   </para>
-
-   <table id="datatype-binary-sqlesc">
-    <title><type>bytea</> Literal Escaped Octets</title>
-    <tgroup cols="5">
-     <thead>
-      <row>
-       <entry>Decimal Octet Value</entry>
-       <entry>Description</entry>
-       <entry>Escaped Input Representation</entry>
-       <entry>Example</entry>
-       <entry>Output Representation</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>0</entry>
-       <entry>zero octet</entry>
-       <entry><literal>E'\\000'</literal></entry>
-       <entry><literal>SELECT E'\\000'::bytea;</literal></entry>
-       <entry><literal>\000</literal></entry>
-      </row>
-
-      <row>
-       <entry>39</entry>
-       <entry>single quote</entry>
-       <entry><literal>''''</literal> or <literal>E'\\047'</literal></entry>
-       <entry><literal>SELECT E'\''::bytea;</literal></entry>
-       <entry><literal>'</literal></entry>
-      </row>
-
-      <row>
-       <entry>92</entry>
-       <entry>backslash</entry>
-       <entry><literal>E'\\\\'</literal> or <literal>E'\\134'</literal></entry>
-       <entry><literal>SELECT E'\\\\'::bytea;</literal></entry>
-       <entry><literal>\\</literal></entry>
-      </row>
-
-      <row>
-       <entry>0 to 31 and 127 to 255</entry>
-       <entry><quote>non-printable</quote> octets</entry>
-       <entry><literal>E'\\<replaceable>xxx'</></literal> (octal value)</entry>
-       <entry><literal>SELECT E'\\001'::bytea;</literal></entry>
-       <entry><literal>\001</literal></entry>
-      </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    The requirement to escape <emphasis>non-printable</emphasis> octets
-    varies depending on locale settings. In some instances you can get away
-    with leaving them unescaped. Note that the result in each of the examples
-    in <xref linkend="datatype-binary-sqlesc"> was exactly one octet in
-    length, even though the output representation is sometimes
-    more than one character.
-   </para>
-
-   <para>
-    The reason multiple backslashes are required, as shown
-    in <xref linkend="datatype-binary-sqlesc">, is that an input
-    string written as a string literal must pass through two parse
-<!## PG>
-    phases in the <productname>PostgreSQL</productname> server.
-<!## end>
-<!## XC>
-    phases in the <productname>Postgres-XC</productname> server.
-<!## end>
-<!## XL>
-    phases in the <productname>Postgres-XL</productname> server.
-<!## end>
-    The first backslash of each pair is interpreted as an escape
-    character by the string-literal parser (assuming escape string
-    syntax is used) and is therefore consumed, leaving the second backslash of the
-    pair.  (Dollar-quoted strings can be used to avoid this level
-    of escaping.)  The remaining backslash is then recognized by the
-    <type>bytea</type> input function as starting either a three
-    digit octal value or escaping another backslash.  For example,
-    a string literal passed to the server as <literal>E'\\001'</literal>
-    becomes <literal>\001</literal> after passing through the
-    escape string parser. The <literal>\001</literal> is then sent
-    to the <type>bytea</type> input function, where it is converted
-    to a single octet with a decimal value of 1.  Note that the
-    single-quote character is not treated specially by <type>bytea</type>,
-    so it follows the normal rules for string literals.  (See also
-    <xref linkend="sql-syntax-strings">.)
-   </para>
-
-   <para>
-    <type>Bytea</type> octets are sometimes escaped when output. In general, each
-    <quote>non-printable</quote> octet is converted into
-    its equivalent three-digit octal value and preceded by one backslash.
-    Most <quote>printable</quote> octets are represented by their standard
-    representation in the client character set. The octet with decimal
-    value 92 (backslash) is doubled in the output.
-    Details are in <xref linkend="datatype-binary-resesc">.
-   </para>
-
-   <table id="datatype-binary-resesc">
-    <title><type>bytea</> Output Escaped Octets</title>
-    <tgroup cols="5">
-     <thead>
-      <row>
-       <entry>Decimal Octet Value</entry>
-       <entry>Description</entry>
-       <entry>Escaped Output Representation</entry>
-       <entry>Example</entry>
-       <entry>Output Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-
-      <row>
-       <entry>92</entry>
-       <entry>backslash</entry>
-       <entry><literal>\\</literal></entry>
-       <entry><literal>SELECT E'\\134'::bytea;</literal></entry>
-       <entry><literal>\\</literal></entry>
-      </row>
-
-      <row>
-       <entry>0 to 31 and 127 to 255</entry>
-       <entry><quote>non-printable</quote> octets</entry>
-       <entry><literal>\<replaceable>xxx</></literal> (octal value)</entry>
-       <entry><literal>SELECT E'\\001'::bytea;</literal></entry>
-       <entry><literal>\001</literal></entry>
-      </row>
-
-      <row>
-       <entry>32 to 126</entry>
-       <entry><quote>printable</quote> octets</entry>
-       <entry>client character set representation</entry>
-       <entry><literal>SELECT E'\\176'::bytea;</literal></entry>
-       <entry><literal>~</literal></entry>
-      </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-<!## PG>
-    Depending on the front end to <productname>PostgreSQL</> you use,
-<!## end>
-<!## XC>
-    Depending on the front end to <productname>Postgres-XC</> you use,
-<!## end>
-<!## XL>
-    Depending on the front end to <productname>Postgres-XL</> you use,
-<!## end>
-    you might have additional work to do in terms of escaping and
-    unescaping <type>bytea</type> strings. For example, you might also
-    have to escape line feeds and carriage returns if your interface
-    automatically translates these.
-   </para>
-  </sect2>
- </sect1>
-
-
-  <sect1 id="datatype-datetime">
-   <title>Date/Time Types</title>
-
-   <indexterm zone="datatype-datetime">
-    <primary>date</primary>
-   </indexterm>
-   <indexterm zone="datatype-datetime">
-    <primary>time</primary>
-   </indexterm>
-   <indexterm zone="datatype-datetime">
-    <primary>time without time zone</primary>
-   </indexterm>
-   <indexterm zone="datatype-datetime">
-    <primary>time with time zone</primary>
-   </indexterm>
-   <indexterm zone="datatype-datetime">
-    <primary>timestamp</primary>
-   </indexterm>
-   <indexterm zone="datatype-datetime">
-    <primary>timestamptz</primary>
-   </indexterm>
-   <indexterm zone="datatype-datetime">
-    <primary>timestamp with time zone</primary>
-   </indexterm>
-   <indexterm zone="datatype-datetime">
-    <primary>timestamp without time zone</primary>
-   </indexterm>
-   <indexterm zone="datatype-datetime">
-    <primary>interval</primary>
-   </indexterm>
-   <indexterm zone="datatype-datetime">
-    <primary>time span</primary>
-   </indexterm>
-&common;
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> supports the full set of
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> supports the full set of
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> supports the full set of
-<!## end>
-    <acronym>SQL</acronym> date and time types, shown in <xref
-    linkend="datatype-datetime-table">.  The operations available
-    on these data types are described in
-    <xref linkend="functions-datetime">.
-   </para>
-
-    <table id="datatype-datetime-table">
-     <title>Date/Time Types</title>
-     <tgroup cols="6">
-      <thead>
-       <row>
-        <entry>Name</entry>
-        <entry>Storage Size</entry>
-        <entry>Description</entry>
-        <entry>Low Value</entry>
-        <entry>High Value</entry>
-        <entry>Resolution</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><type>timestamp [ (<replaceable>p</replaceable>) ] [ without time zone ]</type></entry>
-        <entry>8 bytes</entry>
-        <entry>both date and time (no time zone)</entry>
-        <entry>4713 BC</entry>
-        <entry>294276 AD</entry>
-        <entry>1 microsecond / 14 digits</entry>
-       </row>
-       <row>
-        <entry><type>timestamp [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
-        <entry>8 bytes</entry>
-        <entry>both date and time, with time zone</entry>
-        <entry>4713 BC</entry>
-        <entry>294276 AD</entry>
-        <entry>1 microsecond / 14 digits</entry>
-       </row>
-       <row>
-        <entry><type>date</type></entry>
-        <entry>4 bytes</entry>
-        <entry>date (no time of day)</entry>
-        <entry>4713 BC</entry>
-        <entry>5874897 AD</entry>
-        <entry>1 day</entry>
-       </row>
-       <row>
-        <entry><type>time [ (<replaceable>p</replaceable>) ] [ without time zone ]</type></entry>
-        <entry>8 bytes</entry>
-        <entry>time of day (no date)</entry>
-        <entry>00:00:00</entry>
-        <entry>24:00:00</entry>
-        <entry>1 microsecond / 14 digits</entry>
-       </row>
-       <row>
-        <entry><type>time [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
-        <entry>12 bytes</entry>
-        <entry>times of day only, with time zone</entry>
-        <entry>00:00:00+1459</entry>
-        <entry>24:00:00-1459</entry>
-        <entry>1 microsecond / 14 digits</entry>
-       </row>
-       <row>
-        <entry><type>interval [ <replaceable>fields</replaceable> ] [ (<replaceable>p</replaceable>) ]</type></entry>
-        <entry>12 bytes</entry>
-        <entry>time interval</entry>
-        <entry>-178000000 years</entry>
-        <entry>178000000 years</entry>
-        <entry>1 microsecond / 14 digits</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <note>
-    <para>
-     The SQL standard requires that writing just <type>timestamp</type>
-     be equivalent to <type>timestamp without time
-<!## PG>
-     zone</type>, and <productname>PostgreSQL</productname> honors that
-<!## end>
-<!## XC>
-     zone</type>, and <productname>Postgres-XC</productname> honors that
-<!## end>
-<!## XL>
-     zone</type>, and <productname>Postgres-XL</productname> honors that
-<!## end>
-     behavior.  (Releases prior to 7.3 treated it as <type>timestamp
-     with time zone</type>.)  <type>timestamptz</type> is accepted as an
-     abbreviation for <type>timestamp with time zone</type>; this is a
-     <productname>PostgreSQL</productname> extension.
-    </para>
-   </note>
-
-   <para>
-    <type>time</type>, <type>timestamp</type>, and
-    <type>interval</type> accept an optional precision value
-    <replaceable>p</replaceable> which specifies the number of
-    fractional digits retained in the seconds field. By default, there
-    is no explicit bound on precision.  The allowed range of
-    <replaceable>p</replaceable> is from 0 to 6 for the
-    <type>timestamp</type> and <type>interval</type> types.
-   </para>
-
-   <note>
-   <para>
-    When <type>timestamp</> values are stored as eight-byte integers
-    (currently the default), microsecond precision is available over
-    the full range of values. When <type>timestamp</> values are
-    stored as double precision floating-point numbers instead (a
-    deprecated compile-time option), the effective limit of precision
-    might be less than 6. <type>timestamp</type> values are stored as
-    seconds before or after midnight 2000-01-01.  When
-    <type>timestamp</type> values are implemented using floating-point
-    numbers, microsecond precision is achieved for dates within a few
-    years of 2000-01-01, but the precision degrades for dates further
-    away. Note that using floating-point datetimes allows a larger
-    range of <type>timestamp</type> values to be represented than
-    shown above: from 4713 BC up to 5874897 AD.
-   </para>
-
-   <para>
-    The same compile-time option also determines whether
-    <type>time</type> and <type>interval</type> values are stored as
-    floating-point numbers or eight-byte integers.  In the
-    floating-point case, large <type>interval</type> values degrade in
-    precision as the size of the interval increases.
-   </para>
-   </note>
-
-   <para>
-    For the <type>time</type> types, the allowed range of
-    <replaceable>p</replaceable> is from 0 to 6 when eight-byte integer
-    storage is used, or from 0 to 10 when floating-point storage is used.
-   </para>
-
-   <para>
-    The <type>interval</type> type has an additional option, which is
-    to restrict the set of stored fields by writing one of these phrases:
-<literallayout class="monospaced">
-YEAR
-MONTH
-DAY
-HOUR
-MINUTE
-SECOND
-YEAR TO MONTH
-DAY TO HOUR
-DAY TO MINUTE
-DAY TO SECOND
-HOUR TO MINUTE
-HOUR TO SECOND
-MINUTE TO SECOND
-</literallayout>
-    Note that if both <replaceable>fields</replaceable> and
-    <replaceable>p</replaceable> are specified, the
-    <replaceable>fields</replaceable> must include <literal>SECOND</>,
-    since the precision applies only to the seconds.
-   </para>
-
-   <para>
-    The type <type>time with time zone</type> is defined by the SQL
-    standard, but the definition exhibits properties which lead to
-    questionable usefulness. In most cases, a combination of
-    <type>date</type>, <type>time</type>, <type>timestamp without time
-    zone</type>, and <type>timestamp with time zone</type> should
-    provide a complete range of date/time functionality required by
-    any application.
-   </para>
-
-   <para>
-    The types <type>abstime</type>
-    and <type>reltime</type> are lower precision types which are used internally.
-    You are discouraged from using these types in
-    applications;  these internal types
-    might disappear in a future release.
-   </para>
-
-   <sect2 id="datatype-datetime-input">
-    <title>Date/Time Input</title>
-&common;
-    <para>
-     Date and time input is accepted in almost any reasonable format, including
-     ISO 8601, <acronym>SQL</acronym>-compatible,
-     traditional <productname>POSTGRES</productname>, and others.
-     For some formats, ordering of day, month, and year in date input is
-     ambiguous and there is support for specifying the expected
-     ordering of these fields.  Set the <xref linkend="guc-datestyle"> parameter
-     to <literal>MDY</> to select month-day-year interpretation,
-     <literal>DMY</> to select day-month-year interpretation, or
-     <literal>YMD</> to select year-month-day interpretation.
-    </para>
-
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> is more flexible in
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> is more flexible in
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> is more flexible in
-<!## end>
-     handling date/time input than the
-     <acronym>SQL</acronym> standard requires.
-     See <xref linkend="datetime-appendix">
-     for the exact parsing rules of date/time input and for the
-     recognized text fields including months, days of the week, and
-     time zones.
-    </para>
-
-    <para>
-     Remember that any date or time literal input needs to be enclosed
-     in single quotes, like text strings.  Refer to
-     <xref linkend="sql-syntax-constants-generic"> for more
-     information.
-     <acronym>SQL</acronym> requires the following syntax
-<synopsis>
-<replaceable>type</replaceable> [ (<replaceable>p</replaceable>) ] '<replaceable>value</replaceable>'
-</synopsis>
-     where <replaceable>p</replaceable> is an optional precision
-     specification giving the number of
-     fractional digits in the seconds field. Precision can be
-     specified for <type>time</type>, <type>timestamp</type>, and
-     <type>interval</type> types.  The allowed values are mentioned
-     above.  If no precision is specified in a constant specification,
-     it defaults to the precision of the literal value.
-    </para>
-
-    <sect3>
-    <title>Dates</title>
-
-    <indexterm>
-     <primary>date</primary>
-    </indexterm>
-
-&common;
-    <para>
-     <xref linkend="datatype-datetime-date-table"> shows some possible
-     inputs for the <type>date</type> type.
-    </para>
-
-     <table id="datatype-datetime-date-table">
-      <title>Date Input</title>
-      <tgroup cols="2">
-       <thead>
-        <row>
-         <entry>Example</entry>
-         <entry>Description</entry>
-        </row>
-       </thead>
-       <tbody>
-        <row>
-         <entry>1999-01-08</entry>
-         <entry>ISO 8601; January 8 in any mode
-         (recommended format)</entry>
-        </row>
-        <row>
-         <entry>January 8, 1999</entry>
-         <entry>unambiguous in any <varname>datestyle</varname> input mode</entry>
-        </row>
-        <row>
-         <entry>1/8/1999</entry>
-         <entry>January 8 in <literal>MDY</> mode;
-          August 1 in <literal>DMY</> mode</entry>
-        </row>
-        <row>
-         <entry>1/18/1999</entry>
-         <entry>January 18 in <literal>MDY</> mode;
-          rejected in other modes</entry>
-        </row>
-        <row>
-         <entry>01/02/03</entry>
-         <entry>January 2, 2003 in <literal>MDY</> mode;
-          February 1, 2003 in <literal>DMY</> mode;
-          February 3, 2001 in <literal>YMD</> mode
-         </entry>
-        </row>
-        <row>
-         <entry>1999-Jan-08</entry>
-         <entry>January 8 in any mode</entry>
-        </row>
-        <row>
-         <entry>Jan-08-1999</entry>
-         <entry>January 8 in any mode</entry>
-        </row>
-        <row>
-         <entry>08-Jan-1999</entry>
-         <entry>January 8 in any mode</entry>
-        </row>
-        <row>
-         <entry>99-Jan-08</entry>
-         <entry>January 8 in <literal>YMD</> mode, else error</entry>
-        </row>
-        <row>
-         <entry>08-Jan-99</entry>
-         <entry>January 8, except error in <literal>YMD</> mode</entry>
-        </row>
-        <row>
-         <entry>Jan-08-99</entry>
-         <entry>January 8, except error in <literal>YMD</> mode</entry>
-        </row>
-        <row>
-         <entry>19990108</entry>
-         <entry>ISO 8601; January 8, 1999 in any mode</entry>
-        </row>
-        <row>
-         <entry>990108</entry>
-         <entry>ISO 8601; January 8, 1999 in any mode</entry>
-        </row>
-        <row>
-         <entry>1999.008</entry>
-         <entry>year and day of year</entry>
-        </row>
-        <row>
-         <entry>J2451187</entry>
-         <entry>Julian day</entry>
-        </row>
-        <row>
-         <entry>January 8, 99 BC</entry>
-         <entry>year 99 BC</entry>
-        </row>
-       </tbody>
-      </tgroup>
-     </table>
-    </sect3>
-
-    <sect3>
-     <title>Times</title>
-
-     <indexterm>
-      <primary>time</primary>
-     </indexterm>
-     <indexterm>
-      <primary>time without time zone</primary>
-     </indexterm>
-     <indexterm>
-      <primary>time with time zone</primary>
-     </indexterm>
-&common;
-     <para>
-      The time-of-day types are <type>time [
-      (<replaceable>p</replaceable>) ] without time zone</type> and
-      <type>time [ (<replaceable>p</replaceable>) ] with time
-      zone</type>.  <type>time</type> alone is equivalent to
-      <type>time without time zone</type>.
-     </para>
-
-     <para>
-      Valid input for these types consists of a time of day followed
-      by an optional time zone. (See <xref
-      linkend="datatype-datetime-time-table">
-      and <xref linkend="datatype-timezone-table">.)  If a time zone is
-      specified in the input for <type>time without time zone</type>,
-      it is silently ignored. You can also specify a date but it will
-      be ignored, except when you use a time zone name that involves a
-      daylight-savings rule, such as
-      <literal>America/New_York</literal>. In this case specifying the date
-      is required in order to determine whether standard or daylight-savings
-      time applies.  The appropriate time zone offset is recorded in the
-      <type>time with time zone</type> value.
-     </para>
-
-      <table id="datatype-datetime-time-table">
-       <title>Time Input</title>
-       <tgroup cols="2">
-        <thead>
-         <row>
-          <entry>Example</entry>
-          <entry>Description</entry>
-         </row>
-        </thead>
-        <tbody>
-         <row>
-          <entry><literal>04:05:06.789</literal></entry>
-          <entry>ISO 8601</entry>
-         </row>
-         <row>
-          <entry><literal>04:05:06</literal></entry>
-          <entry>ISO 8601</entry>
-         </row>
-         <row>
-          <entry><literal>04:05</literal></entry>
-          <entry>ISO 8601</entry>
-         </row>
-         <row>
-          <entry><literal>040506</literal></entry>
-          <entry>ISO 8601</entry>
-         </row>
-         <row>
-          <entry><literal>04:05 AM</literal></entry>
-          <entry>same as 04:05; AM does not affect value</entry>
-         </row>
-         <row>
-          <entry><literal>04:05 PM</literal></entry>
-          <entry>same as 16:05; input hour must be &lt;= 12</entry>
-         </row>
-         <row>
-          <entry><literal>04:05:06.789-8</literal></entry>
-          <entry>ISO 8601</entry>
-         </row>
-         <row>
-          <entry><literal>04:05:06-08:00</literal></entry>
-          <entry>ISO 8601</entry>
-         </row>
-         <row>
-          <entry><literal>04:05-08:00</literal></entry>
-          <entry>ISO 8601</entry>
-         </row>
-         <row>
-          <entry><literal>040506-08</literal></entry>
-          <entry>ISO 8601</entry>
-         </row>
-         <row>
-          <entry><literal>04:05:06 PST</literal></entry>
-          <entry>time zone specified by abbreviation</entry>
-         </row>
-         <row>
-          <entry><literal>2003-04-12 04:05:06 America/New_York</literal></entry>
-          <entry>time zone specified by full name</entry>
-         </row>
-        </tbody>
-       </tgroup>
-      </table>
-
-      <table tocentry="1" id="datatype-timezone-table">
-       <title>Time Zone Input</title>
-       <tgroup cols="2">
-        <thead>
-         <row>
-          <entry>Example</entry>
-          <entry>Description</entry>
-         </row>
-        </thead>
-        <tbody>
-         <row>
-          <entry><literal>PST</literal></entry>
-          <entry>Abbreviation (for Pacific Standard Time)</entry>
-         </row>
-         <row>
-          <entry><literal>America/New_York</literal></entry>
-          <entry>Full time zone name</entry>
-         </row>
-         <row>
-          <entry><literal>PST8PDT</literal></entry>
-          <entry>POSIX-style time zone specification</entry>
-         </row>
-         <row>
-          <entry><literal>-8:00</literal></entry>
-          <entry>ISO-8601 offset for PST</entry>
-         </row>
-         <row>
-          <entry><literal>-800</literal></entry>
-          <entry>ISO-8601 offset for PST</entry>
-         </row>
-         <row>
-          <entry><literal>-8</literal></entry>
-          <entry>ISO-8601 offset for PST</entry>
-         </row>
-         <row>
-          <entry><literal>zulu</literal></entry>
-          <entry>Military abbreviation for UTC</entry>
-         </row>
-         <row>
-          <entry><literal>z</literal></entry>
-          <entry>Short form of <literal>zulu</literal></entry>
-         </row>
-        </tbody>
-       </tgroup>
-      </table>
-
-     <para>
-     Refer to <xref linkend="datatype-timezones"> for more information on how
-     to specify time zones.
-    </para>
-    </sect3>
-
-    <sect3>
-    <title>Time Stamps</title>
-
-    <indexterm>
-     <primary>timestamp</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>timestamp with time zone</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>timestamp without time zone</primary>
-    </indexterm>
-&common;
-     <para>
-      Valid input for the time stamp types consists of the concatenation
-      of a date and a time, followed by an optional time zone,
-      followed by an optional <literal>AD</literal> or <literal>BC</literal>.
-      (Alternatively, <literal>AD</literal>/<literal>BC</literal> can appear
-      before the time zone, but this is not the preferred ordering.)
-      Thus:
-
-<programlisting>
-1999-01-08 04:05:06
-</programlisting>
-      and:
-<programlisting>
-1999-01-08 04:05:06 -8:00
-</programlisting>
-
-      are valid values, which follow the <acronym>ISO</acronym> 8601
-      standard.  In addition, the common format:
-<programlisting>
-January 8 04:05:06 1999 PST
-</programlisting>
-      is supported.
-     </para>
-
-     <para>
-      The <acronym>SQL</acronym> standard differentiates
-      <type>timestamp without time zone</type>
-      and <type>timestamp with time zone</type> literals by the presence of a
-      <quote>+</quote> or <quote>-</quote> symbol and time zone offset after
-      the time.  Hence, according to the standard,
-
-      <programlisting>TIMESTAMP '2004-10-19 10:23:54'</programlisting>
-
-      is a <type>timestamp without time zone</type>, while
-
-      <programlisting>TIMESTAMP '2004-10-19 10:23:54+02'</programlisting>
-
-      is a <type>timestamp with time zone</type>.
-<!## PG>
-      <productname>PostgreSQL</productname> never examines the content of a
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname> never examines the content of a
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname> never examines the content of a
-<!## end>
-      literal string before determining its type, and therefore will treat
-      both of the above as <type>timestamp without time zone</type>.  To
-      ensure that a literal is treated as <type>timestamp with time
-      zone</type>, give it the correct explicit type:
-
-      <programlisting>TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'</programlisting>
-
-      In a literal that has been determined to be <type>timestamp without time
-<!## PG>
-      zone</type>, <productname>PostgreSQL</productname> will silently ignore
-<!## end>
-<!## XC>
-      zone</type>, <productname>Postgres-XC</productname> will silently ignore
-<!## end>
-<!## XL>
-      zone</type>, <productname>Postgres-XL</productname> will silently ignore
-<!## end>
-      any time zone indication.
-      That is, the resulting value is derived from the date/time
-      fields in the input value, and is not adjusted for time zone.
-     </para>
-
-     <para>
-      For <type>timestamp with time zone</type>, the internally stored
-      value is always in UTC (Universal
-      Coordinated Time, traditionally known as Greenwich Mean Time,
-      <acronym>GMT</>).  An input value that has an explicit
-      time zone specified is converted to UTC using the appropriate offset
-      for that time zone.  If no time zone is stated in the input string,
-      then it is assumed to be in the time zone indicated by the system's
-      <xref linkend="guc-timezone"> parameter, and is converted to UTC using the
-      offset for the <varname>timezone</> zone.
-     </para>
-
-     <para>
-      When a <type>timestamp with time
-      zone</type> value is output, it is always converted from UTC to the
-      current <varname>timezone</> zone, and displayed as local time in that
-      zone.  To see the time in another time zone, either change
-      <varname>timezone</> or use the <literal>AT TIME ZONE</> construct
-      (see <xref linkend="functions-datetime-zoneconvert">).
-     </para>
-
-     <para>
-      Conversions between <type>timestamp without time zone</type> and
-      <type>timestamp with time zone</type> normally assume that the
-      <type>timestamp without time zone</type> value should be taken or given
-      as <varname>timezone</> local time.  A different time zone can
-      be specified for the conversion using <literal>AT TIME ZONE</>.
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Special Values</title>
-
-     <indexterm>
-      <primary>time</primary>
-      <secondary>constants</secondary>
-     </indexterm>
-
-     <indexterm>
-      <primary>date</primary>
-      <secondary>constants</secondary>
-     </indexterm>
-&common;
-     <para>
-<!## PG>
-      <productname>PostgreSQL</productname> supports several
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname> supports several
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname> supports several
-<!## end>
-      special date/time input values for convenience, as shown in <xref
-      linkend="datatype-datetime-special-table">.  The values
-      <literal>infinity</literal> and <literal>-infinity</literal>
-      are specially represented inside the system and will be displayed
-      unchanged; but the others are simply notational shorthands
-      that will be converted to ordinary date/time values when read.
-      (In particular, <literal>now</> and related strings are converted
-      to a specific time value as soon as they are read.)
-      All of these values need to be enclosed in single quotes when used
-      as constants in SQL commands.
-     </para>
-
-      <table id="datatype-datetime-special-table">
-       <title>Special Date/Time Inputs</title>
-       <tgroup cols="3">
-        <thead>
-         <row>
-          <entry>Input String</entry>
-          <entry>Valid Types</entry>
-          <entry>Description</entry>
-         </row>
-        </thead>
-        <tbody>
-         <row>
-          <entry><literal>epoch</literal></entry>
-          <entry><type>date</type>, <type>timestamp</type></entry>
-          <entry>1970-01-01 00:00:00+00 (Unix system time zero)</entry>
-         </row>
-         <row>
-          <entry><literal>infinity</literal></entry>
-          <entry><type>date</type>, <type>timestamp</type></entry>
-          <entry>later than all other time stamps</entry>
-         </row>
-         <row>
-          <entry><literal>-infinity</literal></entry>
-          <entry><type>date</type>, <type>timestamp</type></entry>
-          <entry>earlier than all other time stamps</entry>
-         </row>
-         <row>
-          <entry><literal>now</literal></entry>
-          <entry><type>date</type>, <type>time</type>, <type>timestamp</type></entry>
-          <entry>current transaction's start time</entry>
-         </row>
-         <row>
-          <entry><literal>today</literal></entry>
-          <entry><type>date</type>, <type>timestamp</type></entry>
-          <entry>midnight today</entry>
-         </row>
-         <row>
-          <entry><literal>tomorrow</literal></entry>
-          <entry><type>date</type>, <type>timestamp</type></entry>
-          <entry>midnight tomorrow</entry>
-         </row>
-         <row>
-          <entry><literal>yesterday</literal></entry>
-          <entry><type>date</type>, <type>timestamp</type></entry>
-          <entry>midnight yesterday</entry>
-         </row>
-         <row>
-          <entry><literal>allballs</literal></entry>
-          <entry><type>time</type></entry>
-          <entry>00:00:00.00 UTC</entry>
-         </row>
-        </tbody>
-       </tgroup>
-      </table>
-
-     <para>
-      The following <acronym>SQL</acronym>-compatible functions can also
-      be used to obtain the current time value for the corresponding data
-      type:
-      <literal>CURRENT_DATE</literal>, <literal>CURRENT_TIME</literal>,
-      <literal>CURRENT_TIMESTAMP</literal>, <literal>LOCALTIME</literal>,
-      <literal>LOCALTIMESTAMP</literal>.  The latter four accept an
-      optional subsecond precision specification.  (See <xref
-      linkend="functions-datetime-current">.)  Note that these are
-      SQL functions and are <emphasis>not</> recognized in data input strings.
-     </para>
-
-    </sect3>
-   </sect2>
-
-   <sect2 id="datatype-datetime-output">
-    <title>Date/Time Output</title>
-
-    <indexterm>
-     <primary>date</primary>
-     <secondary>output format</secondary>
-     <seealso>formatting</seealso>
-    </indexterm>
-
-    <indexterm>
-     <primary>time</primary>
-     <secondary>output format</secondary>
-     <seealso>formatting</seealso>
-    </indexterm>
-&common;
-    <para>
-     The output format of the date/time types can be set to one of the four
-     styles ISO 8601,
-     <acronym>SQL</acronym> (Ingres), traditional <productname>POSTGRES</>
-     (Unix <application>date</> format), or
-     German.  The default
-     is the <acronym>ISO</acronym> format.  (The
-     <acronym>SQL</acronym> standard requires the use of the ISO 8601
-     format.  The name of the <quote>SQL</quote> output format is a
-     historical accident.)  <xref
-     linkend="datatype-datetime-output-table"> shows examples of each
-     output style.  The output of the <type>date</type> and
-     <type>time</type> types is of course only the date or time part
-     in accordance with the given examples.
-    </para>
-
-     <table id="datatype-datetime-output-table">
-      <title>Date/Time Output Styles</title>
-      <tgroup cols="3">
-       <thead>
-        <row>
-         <entry>Style Specification</entry>
-         <entry>Description</entry>
-         <entry>Example</entry>
-        </row>
-       </thead>
-       <tbody>
-        <row>
-         <entry>ISO</entry>
-         <entry>ISO 8601/SQL standard</entry>
-         <entry>1997-12-17 07:37:16-08</entry>
-        </row>
-        <row>
-         <entry>SQL</entry>
-         <entry>traditional style</entry>
-         <entry>12/17/1997 07:37:16.00 PST</entry>
-        </row>
-        <row>
-         <entry>POSTGRES</entry>
-         <entry>original style</entry>
-         <entry>Wed Dec 17 07:37:16 1997 PST</entry>
-        </row>
-        <row>
-         <entry>German</entry>
-         <entry>regional style</entry>
-         <entry>17.12.1997 07:37:16.00 PST</entry>
-        </row>
-       </tbody>
-      </tgroup>
-     </table>
-
-    <para>
-     In the <acronym>SQL</acronym> and POSTGRES styles, day appears before
-     month if DMY field ordering has been specified, otherwise month appears
-     before day.
-     (See <xref linkend="datatype-datetime-input">
-     for how this setting also affects interpretation of input values.)
-     <xref linkend="datatype-datetime-output2-table"> shows an
-     example.
-    </para>
-
-     <table id="datatype-datetime-output2-table">
-      <title>Date Order Conventions</title>
-      <tgroup cols="3">
-       <thead>
-        <row>
-         <entry><varname>datestyle</varname> Setting</entry>
-         <entry>Input Ordering</entry>
-         <entry>Example Output</entry>
-        </row>
-       </thead>
-       <tbody>
-        <row>
-         <entry><literal>SQL, DMY</></entry>
-         <entry><replaceable>day</replaceable>/<replaceable>month</replaceable>/<replaceable>year</replaceable></entry>
-         <entry>17/12/1997 15:37:16.00 CET</entry>
-        </row>
-        <row>
-         <entry><literal>SQL, MDY</></entry>
-         <entry><replaceable>month</replaceable>/<replaceable>day</replaceable>/<replaceable>year</replaceable></entry>
-         <entry>12/17/1997 07:37:16.00 PST</entry>
-        </row>
-        <row>
-         <entry><literal>Postgres, DMY</></entry>
-         <entry><replaceable>day</replaceable>/<replaceable>month</replaceable>/<replaceable>year</replaceable></entry>
-         <entry>Wed 17 Dec 07:37:16 1997 PST</entry>
-        </row>
-       </tbody>
-      </tgroup>
-     </table>
-
-    <para>
-     The date/time styles can be selected by the user using the
-     <command>SET datestyle</command> command, the <xref
-     linkend="guc-datestyle"> parameter in the
-     <filename>postgresql.conf</filename> configuration file, or the
-     <envar>PGDATESTYLE</envar> environment variable on the server or
-     client.  The formatting function <function>to_char</function>
-     (see <xref linkend="functions-formatting">) is also available as
-     a more flexible way to format date/time output.
-    </para>
-   </sect2>
-
-   <sect2 id="datatype-timezones">
-    <title>Time Zones</title>
-
-    <indexterm zone="datatype-timezones">
-     <primary>time zone</primary>
-    </indexterm>
-&common;
-   <para>
-    Time zones, and time-zone conventions, are influenced by
-    political decisions, not just earth geometry. Time zones around the
-    world became somewhat standardized during the 1900's,
-    but continue to be prone to arbitrary changes, particularly with
-    respect to daylight-savings rules.
-<!## PG>
-    <productname>PostgreSQL</productname> uses the widely-used
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> uses the widely-used
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> uses the widely-used
-<!## end>
-    <literal>zoneinfo</> time zone database for information about
-    historical time zone rules.  For times in the future, the assumption
-    is that the latest known rules for a given time zone will
-    continue to be observed indefinitely far into the future.
-   </para>
-
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> endeavors to be compatible with
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> endeavors to be compatible with
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> endeavors to be compatible with
-<!## end>
-     the <acronym>SQL</acronym> standard definitions for typical usage.
-     However, the <acronym>SQL</acronym> standard has an odd mix of date and
-     time types and capabilities. Two obvious problems are:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        Although the <type>date</type> type
-        cannot have an associated time zone, the
-        <type>time</type> type can.
-        Time zones in the real world have little meaning unless
-        associated with a date as well as a time,
-        since the offset can vary through the year with daylight-saving
-        time boundaries.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The default time zone is specified as a constant numeric offset
-        from <acronym>UTC</>. It is therefore impossible to adapt to
-        daylight-saving time when doing date/time arithmetic across
-        <acronym>DST</acronym> boundaries.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-    </para>
-
-    <para>
-     To address these difficulties, we recommend using date/time types
-     that contain both date and time when using time zones. We
-     do <emphasis>not</> recommend using the type <type>time with
-     time zone</type> (though it is supported by
-<!## PG>
-     <productname>PostgreSQL</productname> for legacy applications and
-     for compliance with the <acronym>SQL</acronym> standard).
-     <productname>PostgreSQL</productname> assumes
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> for legacy applications and
-     for compliance with the <acronym>SQL</acronym> standard).
-     <productname>Postgres-XC</productname> assumes
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> for legacy applications and
-     for compliance with the <acronym>SQL</acronym> standard).
-     <productname>Postgres-XL</productname> assumes
-<!## end>
-     your local time zone for any type containing only date or time.
-    </para>
-
-    <para>
-     All timezone-aware dates and times are stored internally in
-     <acronym>UTC</acronym>.  They are converted to local time
-     in the zone specified by the <xref linkend="guc-timezone"> configuration
-     parameter before being displayed to the client.
-    </para>
-
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> allows you to specify time zones in
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> allows you to specify time zones in
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> allows you to specify time zones in
-<!## end>
-     three different forms:
-     <itemizedlist>
-      <listitem>
-       <para>
-        A full time zone name, for example <literal>America/New_York</>.
-        The recognized time zone names are listed in the
-        <literal>pg_timezone_names</literal> view (see <xref
-        linkend="view-pg-timezone-names">).
-<!## PG>
-        <productname>PostgreSQL</productname> uses the widely-used
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> uses the widely-used
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> uses the widely-used
-<!## end>
-        <literal>zoneinfo</> time zone data for this purpose, so the same
-        names are also recognized by much other software.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        A time zone abbreviation, for example <literal>PST</>.  Such a
-        specification merely defines a particular offset from UTC, in
-        contrast to full time zone names which can imply a set of daylight
-        savings transition-date rules as well.  The recognized abbreviations
-        are listed in the <literal>pg_timezone_abbrevs</> view (see <xref
-        linkend="view-pg-timezone-abbrevs">).  You cannot set the
-        configuration parameters <xref linkend="guc-timezone"> or
-        <xref linkend="guc-log-timezone"> to a time
-        zone abbreviation, but you can use abbreviations in
-        date/time input values and with the <literal>AT TIME ZONE</>
-        operator.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        In addition to the timezone names and abbreviations,
-<!## PG>
-        <productname>PostgreSQL</productname> will accept POSIX-style time zone
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> will accept POSIX-style time zone
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> will accept POSIX-style time zone
-<!## end>
-        specifications of the form <replaceable>STD</><replaceable>offset</> or
-        <replaceable>STD</><replaceable>offset</><replaceable>DST</>, where
-        <replaceable>STD</> is a zone abbreviation, <replaceable>offset</> is a
-        numeric offset in hours west from UTC, and <replaceable>DST</> is an
-        optional daylight-savings zone abbreviation, assumed to stand for one
-        hour ahead of the given offset. For example, if <literal>EST5EDT</>
-        were not already a recognized zone name, it would be accepted and would
-        be functionally equivalent to United States East Coast time.  When a
-        daylight-savings zone name is present, it is assumed to be used
-        according to the same daylight-savings transition rules used in the
-        <literal>zoneinfo</> time zone database's <filename>posixrules</> entry.
-<!## PG>
-        In a standard <productname>PostgreSQL</productname> installation,
-<!## end>
-<!## XC>
-        In a standard <productname>Postgres-XC</productname> installation,
-<!## end>
-<!## XL>
-        In a standard <productname>Postgres-XL</productname> installation,
-<!## end>
-        <filename>posixrules</> is the same as <literal>US/Eastern</>, so
-        that POSIX-style time zone specifications follow USA daylight-savings
-        rules.  If needed, you can adjust this behavior by replacing the
-        <filename>posixrules</> file.
-       </para>
-      </listitem>
-     </itemizedlist>
-
-     In short, this is the difference between abbreviations
-     and full names: abbreviations always represent a fixed offset from
-     UTC, whereas most of the full names imply a local daylight-savings time
-     rule, and so have two possible UTC offsets.
-    </para>
-
-    <para>
-     One should be wary that the POSIX-style time zone feature can
-     lead to silently accepting bogus input, since there is no check on the
-     reasonableness of the zone abbreviations.  For example, <literal>SET
-     TIMEZONE TO FOOBAR0</> will work, leaving the system effectively using
-     a rather peculiar abbreviation for UTC.
-     Another issue to keep in mind is that in POSIX time zone names,
-     positive offsets are used for locations <emphasis>west</> of Greenwich.
-<!## PG>
-     Everywhere else, <productname>PostgreSQL</productname> follows the
-<!## end>
-<!## XC>
-     Everywhere else, <productname>Postgres-XC</productname> follows the
-<!## end>
-<!## XL>
-     Everywhere else, <productname>Postgres-XL</productname> follows the
-<!## end>
-     ISO-8601 convention that positive timezone offsets are <emphasis>east</>
-     of Greenwich.
-    </para>
-
-    <para>
-     In all cases, timezone names are recognized case-insensitively.
-     (This is a change from <productname>PostgreSQL</productname> versions
-     prior to 8.2, which were case-sensitive in some contexts but not others.)
-    </para>
-
-    <para>
-     Neither full names nor abbreviations are hard-wired into the server;
-     they are obtained from configuration files stored under
-     <filename>.../share/timezone/</> and <filename>.../share/timezonesets/</>
-     of the installation directory
-     (see <xref linkend="datetime-config-files">).
-    </para>
-
-    <para>
-     The <xref linkend="guc-timezone"> configuration parameter can
-     be set in the file <filename>postgresql.conf</>, or in any of the
-     other standard ways described in <xref linkend="runtime-config">.
-     There are also several special ways to set it:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        If <varname>timezone</> is not specified in
-        <filename>postgresql.conf</> or as a server command-line option,
-        the server attempts to use the value of the <envar>TZ</envar>
-        environment variable as the default time zone.  If <envar>TZ</envar>
-        is not defined or is not any of the time zone names known to
-<!## PG>
-        <productname>PostgreSQL</productname>, the server attempts to
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname>, the server attempts to
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname>, the server attempts to
-<!## end>
-        determine the operating system's default time zone by checking the
-        behavior of the C library function <literal>localtime()</>.  The
-        default time zone is selected as the closest match among
-<!## PG>
-        <productname>PostgreSQL</productname>'s known time zones.
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname>'s known time zones.
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname>'s known time zones.
-<!## end>
-        (These rules are also used to choose the default value of
-        <xref linkend="guc-log-timezone">, if not specified.)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The <acronym>SQL</acronym> command <command>SET TIME ZONE</command>
-        sets the time zone for the session.  This is an alternative spelling
-        of <command>SET TIMEZONE TO</> with a more SQL-spec-compatible syntax.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The <envar>PGTZ</envar> environment variable is used by
-        <application>libpq</application> clients
-        to send a <command>SET TIME ZONE</command>
-        command to the server upon connection.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </sect2>
-
-   <sect2 id="datatype-interval-input">
-    <title>Interval Input</title>
-
-    <indexterm>
-     <primary>interval</primary>
-    </indexterm>
-&common;
-     <para>
-      <type>interval</type> values can be written using the following
-      verbose syntax:
-
-<synopsis>
-<optional>@</> <replaceable>quantity</> <replaceable>unit</> <optional><replaceable>quantity</> <replaceable>unit</>...</> <optional><replaceable>direction</></optional>
-</synopsis>
-
-     where <replaceable>quantity</> is a number (possibly signed);
-     <replaceable>unit</> is <literal>microsecond</literal>,
-     <literal>millisecond</literal>, <literal>second</literal>,
-     <literal>minute</literal>, <literal>hour</literal>, <literal>day</literal>,
-     <literal>week</literal>, <literal>month</literal>, <literal>year</literal>,
-     <literal>decade</literal>, <literal>century</literal>, <literal>millennium</literal>,
-     or abbreviations or plurals of these units;
-     <replaceable>direction</> can be <literal>ago</literal> or
-     empty.  The at sign (<literal>@</>) is optional noise.  The amounts
-     of the different units are implicitly added with appropriate
-     sign accounting.  <literal>ago</literal> negates all the fields.
-     This syntax is also used for interval output, if
-     <xref linkend="guc-intervalstyle"> is set to
-     <literal>postgres_verbose</>.
-    </para>
-
-    <para>
-     Quantities of days, hours, minutes, and seconds can be specified without
-     explicit unit markings.  For example, <literal>'1 12:59:10'</> is read
-     the same as <literal>'1 day 12 hours 59 min 10 sec'</>.  Also,
-     a combination of years and months can be specified with a dash;
-     for example <literal>'200-10'</> is read the same as <literal>'200 years
-     10 months'</>.  (These shorter forms are in fact the only ones allowed
-     by the <acronym>SQL</acronym> standard, and are used for output when
-     <varname>IntervalStyle</> is set to <literal>sql_standard</literal>.)
-    </para>
-
-    <para>
-     Interval values can also be written as ISO 8601 time intervals, using
-     either the <quote>format with designators</> of the standard's section
-     4.4.3.2 or the <quote>alternative format</> of section 4.4.3.3.  The
-     format with designators looks like this:
-<synopsis>
-P <replaceable>quantity</> <replaceable>unit</> <optional> <replaceable>quantity</> <replaceable>unit</> ...</optional> <optional> T <optional> <replaceable>quantity</> <replaceable>unit</> ...</optional></optional>
-</synopsis>
-      The string must start with a <literal>P</>, and may include a
-      <literal>T</> that introduces the time-of-day units.  The
-      available unit abbreviations are given in <xref
-      linkend="datatype-interval-iso8601-units">.  Units may be
-      omitted, and may be specified in any order, but units smaller than
-      a day must appear after <literal>T</>.  In particular, the meaning of
-      <literal>M</> depends on whether it is before or after
-      <literal>T</>.
-     </para>
-
-     <table id="datatype-interval-iso8601-units">
-      <title>ISO 8601 Interval Unit Abbreviations</title>
-     <tgroup cols="2">
-       <thead>
-        <row>
-         <entry>Abbreviation</entry>
-         <entry>Meaning</entry>
-        </row>
-       </thead>
-       <tbody>
-        <row>
-         <entry>Y</entry>
-         <entry>Years</entry>
-        </row>
-        <row>
-         <entry>M</entry>
-         <entry>Months (in the date part)</entry>
-        </row>
-        <row>
-         <entry>W</entry>
-         <entry>Weeks</entry>
-        </row>
-        <row>
-         <entry>D</entry>
-         <entry>Days</entry>
-        </row>
-        <row>
-         <entry>H</entry>
-         <entry>Hours</entry>
-        </row>
-        <row>
-         <entry>M</entry>
-         <entry>Minutes (in the time part)</entry>
-        </row>
-        <row>
-         <entry>S</entry>
-         <entry>Seconds</entry>
-        </row>
-       </tbody>
-      </tgroup>
-     </table>
-
-     <para>
-      In the alternative format:
-<synopsis>
-P <optional> <replaceable>years</>-<replaceable>months</>-<replaceable>days</> </optional> <optional> T <replaceable>hours</>:<replaceable>minutes</>:<replaceable>seconds</> </optional>
-</synopsis>
-      the string must begin with <literal>P</literal>, and a
-      <literal>T</> separates the date and time parts of the interval.
-      The values are given as numbers similar to ISO 8601 dates.
-    </para>
-
-    <para>
-     When writing an interval constant with a <replaceable>fields</>
-     specification, or when assigning a string to an interval column that was
-     defined with a <replaceable>fields</> specification, the interpretation of
-     unmarked quantities depends on the <replaceable>fields</>.  For
-     example <literal>INTERVAL '1' YEAR</> is read as 1 year, whereas
-     <literal>INTERVAL '1'</> means 1 second.  Also, field values
-     <quote>to the right</> of the least significant field allowed by the
-     <replaceable>fields</> specification are silently discarded.  For
-     example, writing <literal>INTERVAL '1 day 2:03:04' HOUR TO MINUTE</>
-     results in dropping the seconds field, but not the day field.
-    </para>
-
-    <para>
-     According to the <acronym>SQL</> standard all fields of an interval
-     value must have the same sign, so a leading negative sign applies to all
-     fields; for example the negative sign in the interval literal
-     <literal>'-1 2:03:04'</> applies to both the days and hour/minute/second
-<!## PG>
-     parts.  <productname>PostgreSQL</> allows the fields to have different
-<!## end>
-<!## XC>
-     parts.  <productname>Postgres-XC</> allows the fields to have different
-<!## end>
-<!## XL>
-     parts.  <productname>Postgres-XL</> allows the fields to have different
-<!## end>
-     signs, and traditionally treats each field in the textual representation
-     as independently signed, so that the hour/minute/second part is
-     considered positive in this example.  If <varname>IntervalStyle</> is
-     set to <literal>sql_standard</literal> then a leading sign is considered
-     to apply to all fields (but only if no additional signs appear).
-<!## PG>
-     Otherwise the traditional <productname>PostgreSQL</> interpretation is
-<!## end>
-<!## XC>
-     Otherwise the traditional <productname>Postgres-XC</> interpretation is
-<!## end>
-<!## XL>
-     Otherwise the traditional <productname>Postgres-XL</> interpretation is
-<!## end>
-     used.  To avoid ambiguity, it's recommended to attach an explicit sign
-     to each field if any field is negative.
-    </para>
-
-    <para>
-     Internally <type>interval</> values are stored as months, days,
-     and seconds. This is done because the number of days in a month
-     varies, and a day can have 23 or 25 hours if a daylight savings
-     time adjustment is involved.  The months and days fields are integers
-     while the seconds field can store fractions.  Because intervals are
-     usually created from constant strings or <type>timestamp</> subtraction,
-     this storage method works well in most cases. Functions
-     <function>justify_days</> and <function>justify_hours</> are
-     available for adjusting days and hours that overflow their normal
-     ranges.
-    </para>
-
-    <para>
-     In the verbose input format, and in some fields of the more compact
-     input formats, field values can have fractional parts; for example
-     <literal>'1.5 week'</> or <literal>'01:02:03.45'</>.  Such input is
-     converted to the appropriate number of months, days, and seconds
-     for storage.  When this would result in a fractional number of
-     months or days, the fraction is added to the lower-order fields
-     using the conversion factors 1 month = 30 days and 1 day = 24 hours.
-     For example, <literal>'1.5 month'</> becomes 1 month and 15 days.
-     Only seconds will ever be shown as fractional on output.
-    </para>
-
-    <para>
-     <xref linkend="datatype-interval-input-examples"> shows some examples
-     of valid <type>interval</> input.
-    </para>
-
-     <table id="datatype-interval-input-examples">
-      <title>Interval Input</title>
-      <tgroup cols="2">
-       <thead>
-        <row>
-         <entry>Example</entry>
-         <entry>Description</entry>
-        </row>
-       </thead>
-       <tbody>
-        <row>
-         <entry>1-2</entry>
-         <entry>SQL standard format: 1 year 2 months</entry>
-        </row>
-        <row>
-         <entry>3 4:05:06</entry>
-         <entry>SQL standard format: 3 days 4 hours 5 minutes 6 seconds</entry>
-        </row>
-        <row>
-         <entry>1 year 2 months 3 days 4 hours 5 minutes 6 seconds</entry>
-         <entry>Traditional Postgres format: 1 year 2 months 3 days 4 hours 5 minutes 6 seconds</entry>
-        </row>
-        <row>
-         <entry>P1Y2M3DT4H5M6S</entry>
-         <entry>ISO 8601 <quote>format with designators</>: same meaning as above</entry>
-        </row>
-        <row>
-         <entry>P0001-02-03T04:05:06</entry>
-         <entry>ISO 8601 <quote>alternative format</>: same meaning as above</entry>
-        </row>
-       </tbody>
-      </tgroup>
-     </table>
-
-   </sect2>
-
-   <sect2 id="datatype-interval-output">
-    <title>Interval Output</title>
-
-    <indexterm>
-     <primary>interval</primary>
-     <secondary>output format</secondary>
-     <seealso>formatting</seealso>
-    </indexterm>
-&common;
-    <para>
-     The output format of the interval type can be set to one of the
-     four styles <literal>sql_standard</>, <literal>postgres</>,
-     <literal>postgres_verbose</>, or <literal>iso_8601</>,
-     using the command <literal>SET intervalstyle</literal>.
-     The default is the <literal>postgres</> format.
-     <xref linkend="interval-style-output-table"> shows examples of each
-     output style.
-    </para>
-
-    <para>
-     The <literal>sql_standard</> style produces output that conforms to
-     the SQL standard's specification for interval literal strings, if
-     the interval value meets the standard's restrictions (either year-month
-     only or day-time only, with no mixing of positive
-     and negative components).  Otherwise the output looks like a standard
-     year-month literal string followed by a day-time literal string,
-     with explicit signs added to disambiguate mixed-sign intervals.
-    </para>
-
-    <para>
-     The output of the <literal>postgres</> style matches the output of
-     <productname>PostgreSQL</> releases prior to 8.4 when the
-     <xref linkend="guc-datestyle"> parameter was set to <literal>ISO</>.
-    </para>
-
-    <para>
-     The output of the <literal>postgres_verbose</> style matches the output of
-     <productname>PostgreSQL</> releases prior to 8.4 when the
-     <varname>DateStyle</> parameter was set to non-<literal>ISO</> output.
-    </para>
-
-    <para>
-     The output of the <literal>iso_8601</> style matches the <quote>format
-     with designators</> described in section 4.4.3.2 of the
-     ISO 8601 standard.
-    </para>
-
-     <table id="interval-style-output-table">
-       <title>Interval Output Style Examples</title>
-       <tgroup cols="4">
-        <thead>
-         <row>
-          <entry>Style Specification</entry>
-          <entry>Year-Month Interval</entry>
-          <entry>Day-Time Interval</entry>
-          <entry>Mixed Interval</entry>
-         </row>
-        </thead>
-        <tbody>
-         <row>
-          <entry><literal>sql_standard</></entry>
-          <entry>1-2</entry>
-          <entry>3 4:05:06</entry>
-          <entry>-1-2 +3 -4:05:06</entry>
-         </row>
-         <row>
-          <entry><literal>postgres</></entry>
-          <entry>1 year 2 mons</entry>
-          <entry>3 days 04:05:06</entry>
-          <entry>-1 year -2 mons +3 days -04:05:06</entry>
-         </row>
-         <row>
-          <entry><literal>postgres_verbose</></entry>
-          <entry>@ 1 year 2 mons</entry>
-          <entry>@ 3 days 4 hours 5 mins 6 secs</entry>
-          <entry>@ 1 year 2 mons -3 days 4 hours 5 mins 6 secs ago</entry>
-         </row>
-         <row>
-          <entry><literal>iso_8601</></entry>
-          <entry>P1Y2M</entry>
-          <entry>P3DT4H5M6S</entry>
-          <entry>P-1Y-2M3DT-4H-5M-6S</entry>
-         </row>
-        </tbody>
-       </tgroup>
-    </table>
-
-   </sect2>
-
-   <sect2 id="datatype-datetime-internals">
-    <title>Internals</title>
-&common;
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> uses Julian dates
-     for all date/time calculations. This has the useful property of correctly
-     calculating dates from 4713 BC
-     to far into the future, using the assumption that the length of the
-     year is 365.2425 days.
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</>, as <productname>PostgreSQL</productname>, uses Julian dates
-     for all date/time calculations. This has the useful property of correctly
-     calculating dates from 4713 BC
-     to far into the future, using the assumption that the length of the
-     year is 365.2425 days.
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</>, as <productname>PostgreSQL</productname>, uses Julian dates
-     for all date/time calculations. This has the useful property of correctly
-     calculating dates from 4713 BC
-     to far into the future, using the assumption that the length of the
-     year is 365.2425 days.
-<!## end>
-    </para>
-
-    <para>
-     Date conventions before the 19th century make for interesting reading,
-     but are not consistent enough to warrant coding into a date/time handler.
-    </para>
-   </sect2>
-
-  </sect1>
-
-  <sect1 id="datatype-boolean">
-   <title>Boolean Type</title>
-
-   <indexterm zone="datatype-boolean">
-    <primary>Boolean</primary>
-    <secondary>data type</secondary>
-   </indexterm>
-
-   <indexterm zone="datatype-boolean">
-    <primary>true</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-boolean">
-    <primary>false</primary>
-   </indexterm>
-&common;
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> provides the
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> provides the
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> provides the
-<!## end>
-    standard <acronym>SQL</acronym> type <type>boolean</type>;
-    see <xref linkend="datatype-boolean-table">.
-    The <type>boolean</type> type can have several states:
-    <quote>true</quote>, <quote>false</quote>, and a third state,
-    <quote>unknown</quote>, which is represented by the
-    <acronym>SQL</acronym> null value.
-   </para>
-
-   <table id="datatype-boolean-table">
-    <title>Boolean Data Type</title>
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Name</entry>
-       <entry>Storage Size</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry><type>boolean</type></entry>
-       <entry>1 byte</entry>
-       <entry>state of true or false</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    Valid literal values for the <quote>true</quote> state are:
-    <simplelist>
-     <member><literal>TRUE</literal></member>
-     <member><literal>'t'</literal></member>
-     <member><literal>'true'</literal></member>
-     <member><literal>'y'</literal></member>
-     <member><literal>'yes'</literal></member>
-     <member><literal>'on'</literal></member>
-     <member><literal>'1'</literal></member>
-    </simplelist>
-    For the <quote>false</quote> state, the following values can be
-    used:
-    <simplelist>
-     <member><literal>FALSE</literal></member>
-     <member><literal>'f'</literal></member>
-     <member><literal>'false'</literal></member>
-     <member><literal>'n'</literal></member>
-     <member><literal>'no'</literal></member>
-     <member><literal>'off'</literal></member>
-     <member><literal>'0'</literal></member>
-    </simplelist>
-    Leading or trailing whitespace is ignored, and case does not matter.
-    The key words
-    <literal>TRUE</literal> and <literal>FALSE</literal> are the preferred
-    (<acronym>SQL</acronym>-compliant) usage.
-   </para>
-
-   <para>
-    <xref linkend="datatype-boolean-example"> shows that
-    <type>boolean</type> values are output using the letters
-    <literal>t</literal> and <literal>f</literal>.
-   </para>
-
-   <example id="datatype-boolean-example">
-    <title>Using the <type>boolean</type> Type</title>
-
-<programlisting>
-CREATE TABLE test1 (a boolean, b text);
-INSERT INTO test1 VALUES (TRUE, 'sic est');
-INSERT INTO test1 VALUES (FALSE, 'non est');
-SELECT * FROM test1;
- a |    b
----+---------
- t | sic est
- f | non est
-
-SELECT * FROM test1 WHERE a;
- a |    b
----+---------
- t | sic est
-</programlisting>
-   </example>
-  </sect1>
-
-  <sect1 id="datatype-enum">
-   <title>Enumerated Types</title>
-
-   <indexterm zone="datatype-enum">
-    <primary>data type</primary>
-    <secondary>enumerated (enum)</secondary>
-   </indexterm>
-
-   <indexterm zone="datatype-enum">
-    <primary>enumerated types</primary>
-   </indexterm>
-&common;
-   <para>
-    Enumerated (enum) types are data types that
-    comprise a static, ordered set of values.
-    They are equivalent to the <type>enum</type>
-    types supported in a number of programming languages. An example of an enum
-    type might be the days of the week, or a set of status values for
-    a piece of data.
-   </para>
-
-   <sect2>
-    <title>Declaration of Enumerated Types</title>
-&common;
-    <para>
-     Enum types are created using the <xref
-     linkend="sql-createtype"> command,
-     for example:
-
-<programlisting>
-CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');
-</programlisting>
-
-     Once created, the enum type can be used in table and function
-     definitions much like any other type:
-<programlisting>
-CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');
-CREATE TABLE person (
-    name text,
-    current_mood mood
-);
-INSERT INTO person VALUES ('Moe', 'happy');
-SELECT * FROM person WHERE current_mood = 'happy';
- name | current_mood 
-------+--------------
- Moe  | happy
-(1 row)
-</programlisting>
-    </para>
-    </sect2>
-
-    <sect2>
-     <title>Ordering</title>
-&common;
-     <para>
-      The ordering of the values in an enum type is the
-      order in which the values were listed when the type was created.
-      All standard comparison operators and related
-      aggregate functions are supported for enums.  For example:
-
-<programlisting>
-INSERT INTO person VALUES ('Larry', 'sad');
-INSERT INTO person VALUES ('Curly', 'ok');
-SELECT * FROM person WHERE current_mood > 'sad';
- name  | current_mood 
--------+--------------
- Moe   | happy
- Curly | ok
-(2 rows)
-
-SELECT * FROM person WHERE current_mood > 'sad' ORDER BY current_mood;
- name  | current_mood 
--------+--------------
- Curly | ok
- Moe   | happy
-(2 rows)
-
-SELECT name
-FROM person
-WHERE current_mood = (SELECT MIN(current_mood) FROM person);
- name  
--------
- Larry
-(1 row)
-</programlisting>
-     </para>
-   </sect2>
-
-   <sect2>
-    <title>Type Safety</title>
-&common;
-    <para>
-     Each enumerated data type is separate and cannot
-     be compared with other enumerated types.  See this example:
-
-<programlisting>
-CREATE TYPE happiness AS ENUM ('happy', 'very happy', 'ecstatic');
-CREATE TABLE holidays (
-    num_weeks integer,
-    happiness happiness
-);
-INSERT INTO holidays(num_weeks,happiness) VALUES (4, 'happy');
-INSERT INTO holidays(num_weeks,happiness) VALUES (6, 'very happy');
-INSERT INTO holidays(num_weeks,happiness) VALUES (8, 'ecstatic');
-INSERT INTO holidays(num_weeks,happiness) VALUES (2, 'sad');
-ERROR:  invalid input value for enum happiness: "sad"
-SELECT person.name, holidays.num_weeks FROM person, holidays
-  WHERE person.current_mood = holidays.happiness;
-ERROR:  operator does not exist: mood = happiness
-</programlisting>
-    </para>
-
-    <para>
-     If you really need to do something like that, you can either
-     write a custom operator or add explicit casts to your query:
-
-<programlisting>
-SELECT person.name, holidays.num_weeks FROM person, holidays
-  WHERE person.current_mood::text = holidays.happiness::text;
- name | num_weeks 
-------+-----------
- Moe  |         4
-(1 row)
-
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Implementation Details</title>
-
-&common;
-    <para>
-     An enum value occupies four bytes on disk.  The length of an enum
-     value's textual label is limited by the <symbol>NAMEDATALEN</symbol>
-<!## PG>
-     setting compiled into <productname>PostgreSQL</productname>; in standard
-<!## end>
-<!## XC>
-     setting compiled into <productname>Postgres-XC</productname>; in standard
-<!## end>
-<!## XL>
-     setting compiled into <productname>Postgres-XL</productname>; in standard
-<!## end>
-     builds this means at most 63 bytes.
-    </para>
-
-    <para>
-     Enum labels are case sensitive, so
-     <type>'happy'</type> is not the same as <type>'HAPPY'</type>.
-     White space in the labels is significant too.
-    </para>
-
-    <para>
-     The translations from internal enum values to textual labels are
-     kept in the system catalog
-     <link linkend="catalog-pg-enum"><structname>pg_enum</structname></link>.
-     Querying this catalog directly can be useful.
-    </para>
-
-   </sect2>
-  </sect1>
-
-  <sect1 id="datatype-geometric">
-   <title>Geometric Types</title>
-&common;
-   <para>
-    Geometric data types represent two-dimensional spatial
-    objects. <xref linkend="datatype-geo-table"> shows the geometric
-<!## PG>
-    types available in <productname>PostgreSQL</productname>.  The
-<!## end>
-<!## XC>
-    types available in <productname>Postgres-XC</productname>.  The
-<!## end>
-<!## XL>
-    types available in <productname>Postgres-XL</productname>.  The
-<!## end>
-    most fundamental type, the point, forms the basis for all of the
-    other types.
-   </para>
-
-    <table id="datatype-geo-table">
-     <title>Geometric Types</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Name</entry>
-        <entry>Storage Size</entry>
-        <entry>Representation</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><type>point</type></entry>
-        <entry>16 bytes</entry>
-        <entry>Point on a plane</entry>
-        <entry>(x,y)</entry>
-       </row>
-       <row>
-        <entry><type>line</type></entry>
-        <entry>32 bytes</entry>
-        <entry>Infinite line (not fully implemented)</entry>
-        <entry>((x1,y1),(x2,y2))</entry>
-       </row>
-       <row>
-        <entry><type>lseg</type></entry>
-        <entry>32 bytes</entry>
-        <entry>Finite line segment</entry>
-        <entry>((x1,y1),(x2,y2))</entry>
-       </row>
-       <row>
-        <entry><type>box</type></entry>
-        <entry>32 bytes</entry>
-        <entry>Rectangular box</entry>
-        <entry>((x1,y1),(x2,y2))</entry>
-       </row>
-       <row>
-        <entry><type>path</type></entry>
-        <entry>16+16n bytes</entry>
-        <entry>Closed path (similar to polygon)</entry>
-        <entry>((x1,y1),...)</entry>
-       </row>
-       <row>
-        <entry><type>path</type></entry>
-        <entry>16+16n bytes</entry>
-        <entry>Open path</entry>
-        <entry>[(x1,y1),...]</entry>
-       </row>
-       <row>
-        <entry><type>polygon</type></entry>
-        <entry>40+16n bytes</entry>
-        <entry>Polygon (similar to closed path)</entry>
-        <entry>((x1,y1),...)</entry>
-       </row>
-       <row>
-        <entry><type>circle</type></entry>
-        <entry>24 bytes</entry>
-        <entry>Circle</entry>
-        <entry>&lt;(x,y),r&gt; (center point and radius)</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    A rich set of functions and operators is available to perform various geometric
-    operations such as scaling, translation, rotation, and determining
-    intersections.  They are explained in <xref linkend="functions-geometry">.
-   </para>
-
-   <sect2>
-    <title>Points</title>
-
-    <indexterm>
-     <primary>point</primary>
-    </indexterm>
-&common;
-    <para>
-     Points are the fundamental two-dimensional building block for geometric
-     types.  Values of type <type>point</type> are specified using either of
-     the following syntaxes:
-
-<synopsis>
-( <replaceable>x</replaceable> , <replaceable>y</replaceable> )
-  <replaceable>x</replaceable> , <replaceable>y</replaceable>
-</synopsis>
-
-     where <replaceable>x</> and <replaceable>y</> are the respective
-     coordinates, as floating-point numbers.
-    </para>
-
-    <para>
-     Points are output using the first syntax.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Line Segments</title>
-&common;
-    <indexterm>
-     <primary>lseg</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>line segment</primary>
-    </indexterm>
-
-    <para>
-     Line segments (<type>lseg</type>) are represented by pairs of points.
-     Values of type <type>lseg</type> are specified using any of the following
-     syntaxes:
-
-<synopsis>
-[ ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ( <replaceable>x2</replaceable> , <replaceable>y2</replaceable> ) ]
-( ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ( <replaceable>x2</replaceable> , <replaceable>y2</replaceable> ) )
-  ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ( <replaceable>x2</replaceable> , <replaceable>y2</replaceable> )
-    <replaceable>x1</replaceable> , <replaceable>y1</replaceable>   ,   <replaceable>x2</replaceable> , <replaceable>y2</replaceable>
-</synopsis>
-
-     where
-     <literal>(<replaceable>x1</replaceable>,<replaceable>y1</replaceable>)</literal>
-     and
-     <literal>(<replaceable>x2</replaceable>,<replaceable>y2</replaceable>)</literal>
-     are the end points of the line segment.
-    </para>
-
-    <para>
-     Line segments are output using the first syntax.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Boxes</title>
-
-    <indexterm>
-     <primary>box (data type)</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>rectangle</primary>
-    </indexterm>
-&common;
-    <para>
-     Boxes are represented by pairs of points that are opposite
-     corners of the box.
-     Values of type <type>box</type> are specified using any of the following
-     syntaxes:
-
-<synopsis>
-( ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ( <replaceable>x2</replaceable> , <replaceable>y2</replaceable> ) )
-  ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ( <replaceable>x2</replaceable> , <replaceable>y2</replaceable> )
-    <replaceable>x1</replaceable> , <replaceable>y1</replaceable>   ,   <replaceable>x2</replaceable> , <replaceable>y2</replaceable>
-</synopsis>
-
-     where
-     <literal>(<replaceable>x1</replaceable>,<replaceable>y1</replaceable>)</literal>
-     and
-     <literal>(<replaceable>x2</replaceable>,<replaceable>y2</replaceable>)</literal>
-     are any two opposite corners of the box.
-    </para>
-
-    <para>
-     Boxes are output using the second syntax.
-    </para>
-
-    <para>
-     Any two opposite corners can be supplied on input, but the values
-     will be reordered as needed to store the
-     upper right and lower left corners, in that order.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Paths</title>
-
-    <indexterm>
-     <primary>path (data type)</primary>
-    </indexterm>
-&common;
-    <para>
-     Paths are represented by lists of connected points. Paths can be
-     <firstterm>open</firstterm>, where
-     the first and last points in the list are considered not connected, or
-     <firstterm>closed</firstterm>,
-     where the first and last points are considered connected.
-    </para>
-
-    <para>
-     Values of type <type>path</type> are specified using any of the following
-     syntaxes:
-
-<synopsis>
-[ ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ... , ( <replaceable>xn</replaceable> , <replaceable>yn</replaceable> ) ]
-( ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ... , ( <replaceable>xn</replaceable> , <replaceable>yn</replaceable> ) )
-  ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ... , ( <replaceable>xn</replaceable> , <replaceable>yn</replaceable> )
-  ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable>   , ... ,   <replaceable>xn</replaceable> , <replaceable>yn</replaceable> )
-    <replaceable>x1</replaceable> , <replaceable>y1</replaceable>   , ... ,   <replaceable>xn</replaceable> , <replaceable>yn</replaceable>
-</synopsis>
-
-     where the points are the end points of the line segments
-     comprising the path.  Square brackets (<literal>[]</>) indicate
-     an open path, while parentheses (<literal>()</>) indicate a
-     closed path.  When the outermost parentheses are omitted, as
-     in the third through fifth syntaxes, a closed path is assumed.
-    </para>
-
-    <para>
-     Paths are output using the first or second syntax, as appropriate.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Polygons</title>
-
-    <indexterm>
-     <primary>polygon</primary>
-    </indexterm>
-&common;
-    <para>
-     Polygons are represented by lists of points (the vertexes of the
-     polygon). Polygons are very similar to closed paths, but are
-     stored differently and have their own set of support routines.
-    </para>
-
-    <para>
-     Values of type <type>polygon</type> are specified using any of the
-     following syntaxes:
-
-<synopsis>
-( ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ... , ( <replaceable>xn</replaceable> , <replaceable>yn</replaceable> ) )
-  ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ... , ( <replaceable>xn</replaceable> , <replaceable>yn</replaceable> )
-  ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable>   , ... ,   <replaceable>xn</replaceable> , <replaceable>yn</replaceable> )
-    <replaceable>x1</replaceable> , <replaceable>y1</replaceable>   , ... ,   <replaceable>xn</replaceable> , <replaceable>yn</replaceable>
-</synopsis>
-
-     where the points are the end points of the line segments
-     comprising the boundary of the polygon.
-    </para>
-
-    <para>
-     Polygons are output using the first syntax.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Circles</title>
-
-    <indexterm>
-     <primary>circle</primary>
-    </indexterm>
-&common;
-    <para>
-     Circles are represented by a center point and radius.
-     Values of type <type>circle</type> are specified using any of the
-     following syntaxes:
-
-<synopsis>
-&lt; ( <replaceable>x</replaceable> , <replaceable>y</replaceable> ) , <replaceable>r</replaceable> &gt;
-( ( <replaceable>x</replaceable> , <replaceable>y</replaceable> ) , <replaceable>r</replaceable> )
-  ( <replaceable>x</replaceable> , <replaceable>y</replaceable> ) , <replaceable>r</replaceable>
-    <replaceable>x</replaceable> , <replaceable>y</replaceable>   , <replaceable>r</replaceable>
-</synopsis>
-
-     where
-     <literal>(<replaceable>x</replaceable>,<replaceable>y</replaceable>)</>
-     is the center point and <replaceable>r</replaceable> is the radius of the
-     circle.
-    </para>
-
-    <para>
-     Circles are output using the first syntax.
-    </para>
-   </sect2>
-
-  </sect1>
-
-  <sect1 id="datatype-net-types">
-   <title>Network Address Types</title>
-
-   <indexterm zone="datatype-net-types">
-    <primary>network</primary>
-    <secondary>data types</secondary>
-   </indexterm>
-&common;
-   <para>
-<!## PG>
-    <productname>PostgreSQL</> offers data types to store IPv4, IPv6, and MAC
-<!## end>
-<!## XC>
-    <productname>PostgreSQL</> inherits data types to store IPv4, IPv6, and MAC
-<!## end>
-<!## XL>
-    <productname>PostgreSQL</> inherits data types to store IPv4, IPv6, and MAC
-<!## end>
-    addresses, as shown in <xref linkend="datatype-net-types-table">.  It
-    is better to use these types instead of plain text types to store
-    network addresses, because
-    these types offer input error checking and specialized
-    operators and functions (see <xref linkend="functions-net">).
-   </para>
-
-    <table tocentry="1" id="datatype-net-types-table">
-     <title>Network Address Types</title>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Name</entry>
-        <entry>Storage Size</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-
-       <row>
-        <entry><type>cidr</type></entry>
-        <entry>7 or 19 bytes</entry>
-        <entry>IPv4 and IPv6 networks</entry>
-       </row>
-
-       <row>
-        <entry><type>inet</type></entry>
-        <entry>7 or 19 bytes</entry>
-        <entry>IPv4 and IPv6 hosts and networks</entry>
-       </row>
-
-       <row>
-        <entry><type>macaddr</type></entry>
-        <entry>6 bytes</entry>
-        <entry>MAC addresses</entry>
-       </row>
-
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    When sorting <type>inet</type> or <type>cidr</type> data types,
-    IPv4 addresses will always sort before IPv6 addresses, including
-    IPv4 addresses encapsulated or mapped to IPv6 addresses, such as
-    ::10.2.3.4 or ::ffff:10.4.3.2.
-   </para>
-
-
-   <sect2 id="datatype-inet">
-    <title><type>inet</type></title>
-
-    <indexterm>
-     <primary>inet (data type)</primary>
-    </indexterm>
-&common;
-    <para>
-     The <type>inet</type> type holds an IPv4 or IPv6 host address, and
-     optionally its subnet, all in one field.
-     The subnet is represented by the number of network address bits
-     present in the host address (the
-     <quote>netmask</quote>).  If the netmask is 32 and the address is IPv4,
-     then the value does not indicate a subnet, only a single host.
-     In IPv6, the address length is 128 bits, so 128 bits specify a
-     unique host address.  Note that if you
-     want to accept only networks, you should use the
-     <type>cidr</type> type rather than <type>inet</type>.
-    </para>
-
-    <para>
-      The input format for this type is
-      <replaceable class="parameter">address/y</replaceable>
-      where
-      <replaceable class="parameter">address</replaceable>
-      is an IPv4 or IPv6 address and
-      <replaceable class="parameter">y</replaceable>
-      is the number of bits in the netmask.  If the
-      <replaceable class="parameter">/y</replaceable>
-      portion is missing, the
-      netmask is 32 for IPv4 and 128 for IPv6, so the value represents
-      just a single host.  On display, the
-      <replaceable class="parameter">/y</replaceable>
-      portion is suppressed if the netmask specifies a single host.
-    </para>
-   </sect2>
-
-   <sect2 id="datatype-cidr">
-    <title><type>cidr</></title>
-
-    <indexterm>
-     <primary>cidr</primary>
-    </indexterm>
-&common;
-    <para>
-     The <type>cidr</type> type holds an IPv4 or IPv6 network specification.
-     Input and output formats follow Classless Internet Domain Routing
-     conventions.
-     The format for specifying networks is <replaceable
-     class="parameter">address/y</> where <replaceable
-     class="parameter">address</> is the network represented as an
-     IPv4 or IPv6 address, and <replaceable
-     class="parameter">y</> is the number of bits in the netmask.  If
-     <replaceable class="parameter">y</> is omitted, it is calculated
-     using assumptions from the older classful network numbering system, except
-     it will be at least large enough to include all of the octets
-     written in the input.  It is an error to specify a network address
-     that has bits set to the right of the specified netmask.
-    </para>
-
-    <para>
-     <xref linkend="datatype-net-cidr-table"> shows some examples.
-    </para>
-
-     <table id="datatype-net-cidr-table">
-      <title><type>cidr</> Type Input Examples</title>
-      <tgroup cols="3">
-       <thead>
-        <row>
-         <entry><type>cidr</type> Input</entry>
-         <entry><type>cidr</type> Output</entry>
-         <entry><literal><function>abbrev(<type>cidr</type>)</function></literal></entry>
-        </row>
-       </thead>
-       <tbody>
-        <row>
-         <entry>192.168.100.128/25</entry>
-         <entry>192.168.100.128/25</entry>
-         <entry>192.168.100.128/25</entry>
-        </row>
-        <row>
-         <entry>192.168/24</entry>
-         <entry>192.168.0.0/24</entry>
-         <entry>192.168.0/24</entry>
-        </row>
-        <row>
-         <entry>192.168/25</entry>
-         <entry>192.168.0.0/25</entry>
-         <entry>192.168.0.0/25</entry>
-        </row>
-        <row>
-         <entry>192.168.1</entry>
-         <entry>192.168.1.0/24</entry>
-         <entry>192.168.1/24</entry>
-        </row>
-        <row>
-         <entry>192.168</entry>
-         <entry>192.168.0.0/24</entry>
-         <entry>192.168.0/24</entry>
-        </row>
-        <row>
-         <entry>128.1</entry>
-         <entry>128.1.0.0/16</entry>
-         <entry>128.1/16</entry>
-        </row>
-        <row>
-         <entry>128</entry>
-         <entry>128.0.0.0/16</entry>
-         <entry>128.0/16</entry>
-        </row>
-        <row>
-         <entry>128.1.2</entry>
-         <entry>128.1.2.0/24</entry>
-         <entry>128.1.2/24</entry>
-        </row>
-        <row>
-         <entry>10.1.2</entry>
-         <entry>10.1.2.0/24</entry>
-         <entry>10.1.2/24</entry>
-        </row>
-        <row>
-         <entry>10.1</entry>
-         <entry>10.1.0.0/16</entry>
-         <entry>10.1/16</entry>
-        </row>
-        <row>
-         <entry>10</entry>
-         <entry>10.0.0.0/8</entry>
-         <entry>10/8</entry>
-        </row>
-        <row>
-         <entry>10.1.2.3/32</entry>
-         <entry>10.1.2.3/32</entry>
-         <entry>10.1.2.3/32</entry>
-        </row>
-        <row>
-         <entry>2001:4f8:3:ba::/64</entry>
-         <entry>2001:4f8:3:ba::/64</entry>
-         <entry>2001:4f8:3:ba::/64</entry>
-        </row>
-        <row>
-         <entry>2001:4f8:3:ba:2e0:81ff:fe22:d1f1/128</entry>
-         <entry>2001:4f8:3:ba:2e0:81ff:fe22:d1f1/128</entry>
-         <entry>2001:4f8:3:ba:2e0:81ff:fe22:d1f1</entry>
-        </row>
-        <row>
-         <entry>::ffff:1.2.3.0/120</entry>
-         <entry>::ffff:1.2.3.0/120</entry>
-         <entry>::ffff:1.2.3/120</entry>
-        </row>
-        <row>
-         <entry>::ffff:1.2.3.0/128</entry>
-         <entry>::ffff:1.2.3.0/128</entry>
-         <entry>::ffff:1.2.3.0/128</entry>
-        </row>
-       </tbody>
-      </tgroup>
-     </table>
-   </sect2>
-
-   <sect2 id="datatype-inet-vs-cidr">
-    <title><type>inet</type> vs. <type>cidr</type></title>
-&common;
-    <para>
-    The essential difference between <type>inet</type> and <type>cidr</type>
-    data types is that <type>inet</type> accepts values with nonzero bits to
-    the right of the netmask, whereas <type>cidr</type> does not.
-    </para>
-
-      <tip>
-        <para>
-        If you do not like the output format for <type>inet</type> or
-        <type>cidr</type> values, try the functions <function>host</>,
-        <function>text</>, and <function>abbrev</>.
-        </para>
-      </tip>
-   </sect2>
-
-   <sect2 id="datatype-macaddr">
-    <title><type>macaddr</type></title>
-
-    <indexterm>
-     <primary>macaddr (data type)</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>MAC address</primary>
-     <see>macaddr</see>
-    </indexterm>
-&common;
-    <para>
-     The <type>macaddr</> type stores MAC addresses, known for example
-     from Ethernet card hardware addresses (although MAC addresses are
-     used for other purposes as well).  Input is accepted in the
-     following formats:
-
-     <simplelist>
-      <member><literal>'08:00:2b:01:02:03'</></member>
-      <member><literal>'08-00-2b-01-02-03'</></member>
-      <member><literal>'08002b:010203'</></member>
-      <member><literal>'08002b-010203'</></member>
-      <member><literal>'0800.2b01.0203'</></member>
-      <member><literal>'08002b010203'</></member>
-     </simplelist>
-
-     These examples would all specify the same address.  Upper and
-     lower case is accepted for the digits
-     <literal>a</> through <literal>f</>.  Output is always in the
-     first of the forms shown.
-    </para>
-
-    <para>
-     IEEE Std 802-2001 specifies the second shown form (with hyphens)
-     as the canonical form for MAC addresses, and specifies the first
-     form (with colons) as the bit-reversed notation, so that
-     08-00-2b-01-02-03 = 01:00:4D:08:04:0C.  This convention is widely
-     ignored nowadays, and it is only relevant for obsolete network
-<!## PG>
-     protocols (such as Token Ring).  PostgreSQL makes no provisions
-<!## end>
-<!## XC>
-     protocols (such as Token Ring).  Postgres-XC makes no provisions
-<!## end>
-<!## XL>
-     protocols (such as Token Ring).  Postgres-XL makes no provisions
-<!## end>
-     for bit reversal, and all accepted formats use the canonical LSB
-     order.
-    </para>
-
-    <para>
-     The remaining four input formats are not part of any standard.
-    </para>
-   </sect2>
-
-  </sect1>
-
-  <sect1 id="datatype-bit">
-   <title>Bit String Types</title>
-
-   <indexterm zone="datatype-bit">
-    <primary>bit string</primary>
-    <secondary>data type</secondary>
-   </indexterm>
-&common;
-   <para>
-    Bit strings are strings of 1's and 0's.  They can be used to store
-    or visualize bit masks.  There are two SQL bit types:
-    <type>bit(<replaceable>n</replaceable>)</type> and <type>bit
-    varying(<replaceable>n</replaceable>)</type>, where
-    <replaceable>n</replaceable> is a positive integer.
-   </para>
-
-   <para>
-    <type>bit</type> type data must match the length
-    <replaceable>n</replaceable> exactly; it is an error to attempt to
-    store shorter or longer bit strings.  <type>bit varying</type> data is
-    of variable length up to the maximum length
-    <replaceable>n</replaceable>; longer strings will be rejected.
-    Writing <type>bit</type> without a length is equivalent to
-    <literal>bit(1)</literal>, while <type>bit varying</type> without a length
-    specification means unlimited length.
-   </para>
-
-   <note>
-    <para>
-     If one explicitly casts a bit-string value to
-     <type>bit(<replaceable>n</>)</type>, it will be truncated or
-     zero-padded on the right to be exactly <replaceable>n</> bits,
-     without raising an error.  Similarly,
-     if one explicitly casts a bit-string value to
-     <type>bit varying(<replaceable>n</>)</type>, it will be truncated
-     on the right if it is more than <replaceable>n</> bits.
-    </para>
-   </note>
-
-   <para>
-    Refer to <xref
-    linkend="sql-syntax-bit-strings"> for information about the syntax
-    of bit string constants.  Bit-logical operators and string
-    manipulation functions are available; see <xref
-    linkend="functions-bitstring">.
-   </para>
-
-   <example>
-    <title>Using the Bit String Types</title>
-
-<programlisting>
-CREATE TABLE test (a BIT(3), b BIT VARYING(5));
-INSERT INTO test VALUES (B'101', B'00');
-INSERT INTO test VALUES (B'10', B'101');
-<computeroutput>
-ERROR:  bit string length 2 does not match type bit(3)
-</computeroutput>
-INSERT INTO test VALUES (B'10'::bit(3), B'101');
-SELECT * FROM test;
-<computeroutput>
-  a  |  b
------+-----
- 101 | 00
- 100 | 101
-</computeroutput>
-</programlisting>
-   </example>
-
-   <para>
-    A bit string value requires 1 byte for each group of 8 bits, plus
-    5 or 8 bytes overhead depending on the length of the string
-    (but long values may be compressed or moved out-of-line, as explained
-    in <xref linkend="datatype-character"> for character strings).
-   </para>
-  </sect1>
-
-  <sect1 id="datatype-textsearch">
-   <title>Text Search Types</title>
-
-   <indexterm zone="datatype-textsearch">
-    <primary>full text search</primary>
-    <secondary>data types</secondary>
-   </indexterm>
-
-   <indexterm zone="datatype-textsearch">
-    <primary>text search</primary>
-    <secondary>data types</secondary>
-   </indexterm>
-&common;
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> provides two data types that
-<!## end>
-<!## PG>
-    <productname>Postgres-XC</productname> inherits two data types that
-<!## end>
-    are designed to support full text search, which is the activity of
-    searching through a collection of natural-language <firstterm>documents</>
-    to locate those that best match a <firstterm>query</>.
-    The <type>tsvector</type> type represents a document in a form optimized
-    for text search; the <type>tsquery</type> type similarly represents
-    a text query.
-    <xref linkend="textsearch"> provides a detailed explanation of this
-    facility, and <xref linkend="functions-textsearch"> summarizes the
-    related functions and operators.
-   </para>
-
-   <sect2 id="datatype-tsvector">
-    <title><type>tsvector</type></title>
-
-    <indexterm>
-     <primary>tsvector (data type)</primary>
-    </indexterm>
-&common;
-    <para>
-     A <type>tsvector</type> value is a sorted list of distinct
-     <firstterm>lexemes</>, which are words that have been
-     <firstterm>normalized</> to merge different variants of the same word
-     (see <xref linkend="textsearch"> for details).  Sorting and
-     duplicate-elimination are done automatically during input, as shown in
-     this example:
-
-<programlisting>
-SELECT 'a fat cat sat on a mat and ate a fat rat'::tsvector;
-                      tsvector
-----------------------------------------------------
- 'a' 'and' 'ate' 'cat' 'fat' 'mat' 'on' 'rat' 'sat'
-</programlisting>
-
-     To represent
-     lexemes containing whitespace or punctuation, surround them with quotes:
-
-<programlisting>
-SELECT $$the lexeme '    ' contains spaces$$::tsvector;
-                 tsvector                  
--------------------------------------------
- '    ' 'contains' 'lexeme' 'spaces' 'the'
-</programlisting>
-
-     (We use dollar-quoted string literals in this example and the next one
-     to avoid the confusion of having to double quote marks within the
-     literals.)  Embedded quotes and backslashes must be doubled:
-
-<programlisting>
-SELECT $$the lexeme 'Joe''s' contains a quote$$::tsvector;
-                    tsvector                    
-------------------------------------------------
- 'Joe''s' 'a' 'contains' 'lexeme' 'quote' 'the'
-</programlisting>
-
-     Optionally, integer <firstterm>positions</>
-     can be attached to lexemes:
-
-<programlisting>
-SELECT 'a:1 fat:2 cat:3 sat:4 on:5 a:6 mat:7 and:8 ate:9 a:10 fat:11 rat:12'::tsvector;
-                                  tsvector
--------------------------------------------------------------------------------
- 'a':1,6,10 'and':8 'ate':9 'cat':3 'fat':2,11 'mat':7 'on':5 'rat':12 'sat':4
-</programlisting>
-
-     A position normally indicates the source word's location in the
-     document.  Positional information can be used for
-     <firstterm>proximity ranking</firstterm>.  Position values can
-     range from 1 to 16383; larger numbers are silently set to 16383.
-     Duplicate positions for the same lexeme are discarded.
-    </para>
-
-    <para>
-     Lexemes that have positions can further be labeled with a
-     <firstterm>weight</>, which can be <literal>A</literal>,
-     <literal>B</literal>, <literal>C</literal>, or <literal>D</literal>.
-     <literal>D</literal> is the default and hence is not shown on output:
-
-<programlisting>
-SELECT 'a:1A fat:2B,4C cat:5D'::tsvector;
-          tsvector          
-----------------------------
- 'a':1A 'cat':5 'fat':2B,4C
-</programlisting>
-
-     Weights are typically used to reflect document structure, for example
-     by marking title words differently from body words.  Text search
-     ranking functions can assign different priorities to the different
-     weight markers.
-    </para>
-
-    <para>
-     It is important to understand that the
-     <type>tsvector</type> type itself does not perform any normalization;
-     it assumes the words it is given are normalized appropriately
-     for the application.  For example,
-
-<programlisting>
-select 'The Fat Rats'::tsvector;
-      tsvector      
---------------------
- 'Fat' 'Rats' 'The'
-</programlisting>
-
-     For most English-text-searching applications the above words would
-     be considered non-normalized, but <type>tsvector</type> doesn't care.
-     Raw document text should usually be passed through
-     <function>to_tsvector</> to normalize the words appropriately
-     for searching:
-
-<programlisting>
-SELECT to_tsvector('english', 'The Fat Rats');
-   to_tsvector   
------------------
- 'fat':2 'rat':3
-</programlisting>
-
-     Again, see <xref linkend="textsearch"> for more detail.
-    </para>
-
-   </sect2>
-
-   <sect2 id="datatype-tsquery">
-    <title><type>tsquery</type></title>
-
-    <indexterm>
-     <primary>tsquery (data type)</primary>
-    </indexterm>
-&common;
-    <para>
-     A <type>tsquery</type> value stores lexemes that are to be
-     searched for, and combines them honoring the Boolean operators
-     <literal>&amp;</literal> (AND), <literal>|</literal> (OR), and
-     <literal>!</> (NOT).  Parentheses can be used to enforce grouping
-     of the operators:
-
-<programlisting>
-SELECT 'fat &amp; rat'::tsquery;
-    tsquery    
----------------
- 'fat' &amp; 'rat'
-
-SELECT 'fat &amp; (rat | cat)'::tsquery;
-          tsquery          
----------------------------
- 'fat' &amp; ( 'rat' | 'cat' )
-
-SELECT 'fat &amp; rat &amp; ! cat'::tsquery;
-        tsquery         
-------------------------
- 'fat' &amp; 'rat' &amp; !'cat'
-</programlisting>
-
-     In the absence of parentheses, <literal>!</> (NOT) binds most tightly,
-     and <literal>&amp;</literal> (AND) binds more tightly than
-     <literal>|</literal> (OR).
-    </para>
-
-    <para>
-     Optionally, lexemes in a <type>tsquery</type> can be labeled with
-     one or more weight letters, which restricts them to match only
-     <type>tsvector</> lexemes with matching weights:
-
-<programlisting>
-SELECT 'fat:ab &amp; cat'::tsquery;
-    tsquery
-------------------
- 'fat':AB &amp; 'cat'
-</programlisting>
-    </para>
-
-    <para>
-     Also, lexemes in a <type>tsquery</type> can be labeled with <literal>*</>
-     to specify prefix matching:
-<programlisting>
-SELECT 'super:*'::tsquery;
-  tsquery  
------------
- 'super':*
-</programlisting>
-     This query will match any word in a <type>tsvector</> that begins
-     with <quote>super</>.  Note that prefixes are first processed by
-     text search configurations, which means this comparison returns
-     true:
-<programlisting>
-SELECT to_tsvector( 'postgraduate' ) @@ to_tsquery( 'postgres:*' );
- ?column? 
-----------
- t
-(1 row)
-</programlisting>
-     because <literal>postgres</> gets stemmed to <literal>postgr</>: 
-<programlisting>
-SELECT to_tsquery('postgres:*');
- to_tsquery 
-------------
- 'postgr':*
-(1 row)
-</programlisting>
-     which then matches <literal>postgraduate</>.
-    </para>
-
-    <para>
-     Quoting rules for lexemes are the same as described previously for
-     lexemes in <type>tsvector</>; and, as with <type>tsvector</>,
-     any required normalization of words must be done before converting
-     to the <type>tsquery</> type.  The <function>to_tsquery</>
-     function is convenient for performing such normalization:
-
-<programlisting>
-SELECT to_tsquery('Fat:ab &amp; Cats');
-    to_tsquery    
-------------------
- 'fat':AB &amp; 'cat'
-</programlisting>
-    </para>
-
-   </sect2>
-
-  </sect1>
-
-  <sect1 id="datatype-uuid">
-   <title><acronym>UUID</acronym> Type</title>
-
-   <indexterm zone="datatype-uuid">
-    <primary>UUID</primary>
-   </indexterm>
-&common;
-   <para>
-    The data type <type>uuid</type> stores Universally Unique Identifiers
-    (UUID) as defined by RFC 4122, ISO/IEC 9834-8:2005, and related standards.
-    (Some systems refer to this data type as a globally unique identifier, or
-    GUID,<indexterm><primary>GUID</primary></indexterm> instead.)  This
-    identifier is a 128-bit quantity that is generated by an algorithm chosen
-    to make it very unlikely that the same identifier will be generated by
-    anyone else in the known universe using the same algorithm.  Therefore,
-    for distributed systems, these identifiers provide a better uniqueness
-    guarantee than sequence generators, which
-    are only unique within a single database.
-   </para>
-
-   <para>
-    A UUID is written as a sequence of lower-case hexadecimal digits,
-    in several groups separated by hyphens, specifically a group of 8
-    digits followed by three groups of 4 digits followed by a group of
-    12 digits, for a total of 32 digits representing the 128 bits.  An
-    example of a UUID in this standard form is:
-<programlisting>
-a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11
-</programlisting>
-<!## PG>
-    <productname>PostgreSQL</productname> also accepts the following
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> also accepts the following
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> also accepts the following
-<!## end>
-    alternative forms for input:
-    use of upper-case digits, the standard format surrounded by
-    braces, omitting some or all hyphens, adding a hyphen after any
-    group of four digits.  Examples are:
-<programlisting>
-A0EEBC99-9C0B-4EF8-BB6D-6BB9BD380A11
-{a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11}
-a0eebc999c0b4ef8bb6d6bb9bd380a11
-a0ee-bc99-9c0b-4ef8-bb6d-6bb9-bd38-0a11
-{a0eebc99-9c0b4ef8-bb6d6bb9-bd380a11}
-</programlisting>
-    Output is always in the standard form.
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> provides storage and comparison
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> provides storage and comparison
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> provides storage and comparison
-<!## end>
-    functions for UUIDs, but the core database does not include any
-    function for generating UUIDs, because no single algorithm is well
-    suited for every application.  The <xref
-    linkend="uuid-ossp"> module
-    provides functions that implement several standard algorithms.
-    Alternatively, UUIDs could be generated by client applications or
-    other libraries invoked through a server-side function.
-   </para>
-  </sect1>
-
-  <sect1 id="datatype-xml">
-   <title><acronym>XML</> Type</title>
-
-   <indexterm zone="datatype-xml">
-    <primary>XML</primary>
-   </indexterm>
-&common;
-   <para>
-    The <type>xml</type> data type can be used to store XML data.  Its
-    advantage over storing XML data in a <type>text</type> field is that it
-    checks the input values for well-formedness, and there are support
-    functions to perform type-safe operations on it; see <xref
-    linkend="functions-xml">.  Use of this data type requires the
-    installation to have been built with <command>configure
-    --with-libxml</>.
-   </para>
-
-   <para>
-    The <type>xml</type> type can store well-formed
-    <quote>documents</quote>, as defined by the XML standard, as well
-    as <quote>content</quote> fragments, which are defined by the
-    production <literal>XMLDecl? content</literal> in the XML
-    standard.  Roughly, this means that content fragments can have
-    more than one top-level element or character node.  The expression
-    <literal><replaceable>xmlvalue</replaceable> IS DOCUMENT</literal>
-    can be used to evaluate whether a particular <type>xml</type>
-    value is a full document or only a content fragment.
-   </para>
-
-   <sect2>
-    <title>Creating XML Values</title>
-&common;
-   <para>
-    To produce a value of type <type>xml</type> from character data,
-    use the function
-    <function>xmlparse</function>:<indexterm><primary>xmlparse</primary></indexterm>
-<synopsis>
-XMLPARSE ( { DOCUMENT | CONTENT } <replaceable>value</replaceable>)
-</synopsis>
-    Examples:
-<programlisting><![CDATA[
-XMLPARSE (DOCUMENT '<?xml version="1.0"?><book><title>Manual</title><chapter>...</chapter></book>')
-XMLPARSE (CONTENT 'abc<foo>bar</foo><bar>foo</bar>')
-]]></programlisting>
-    While this is the only way to convert character strings into XML
-<!## PG>
-    values according to the SQL standard, the PostgreSQL-specific
-<!## end>
-<!## XC>
-    values according to the SQL standard, the Postgres-XC-specific
-<!## end>
-<!## XL>
-    values according to the SQL standard, the Postgres-XL-specific
-<!## end>
-    syntaxes:
-<programlisting><![CDATA[
-xml '<foo>bar</foo>'
-'<foo>bar</foo>'::xml
-]]></programlisting>
-    can also be used.
-   </para>
-
-   <para>
-    The <type>xml</type> type does not validate input values
-    against a document type declaration
-    (DTD),<indexterm><primary>DTD</primary></indexterm>
-    even when the input value specifies a DTD.
-    There is also currently no built-in support for validating against
-    other XML schema languages such as XML Schema.
-   </para>
-
-   <para>
-    The inverse operation, producing a character string value from
-    <type>xml</type>, uses the function
-    <function>xmlserialize</function>:<indexterm><primary>xmlserialize</primary></indexterm>
-<synopsis>
-XMLSERIALIZE ( { DOCUMENT | CONTENT } <replaceable>value</replaceable> AS <replaceable>type</replaceable> )
-</synopsis>
-    <replaceable>type</replaceable> can be
-    <type>character</type>, <type>character varying</type>, or
-    <type>text</type> (or an alias for one of those).  Again, according
-    to the SQL standard, this is the only way to convert between type
-<!## PG>
-    <type>xml</type> and character types, but PostgreSQL also allows
-<!## end>
-<!## XC>
-    <type>xml</type> and character types, but Postgres-XC also allows
-<!## end>
-<!## XL>
-    <type>xml</type> and character types, but Postgres-XL also allows
-<!## end>
-    you to simply cast the value.
-   </para>
-
-   <para>
-    When a character string value is cast to or from type
-    <type>xml</type> without going through <type>XMLPARSE</type> or
-    <type>XMLSERIALIZE</type>, respectively, the choice of
-    <literal>DOCUMENT</literal> versus <literal>CONTENT</literal> is
-    determined by the <quote>XML option</quote>
-    <indexterm><primary>XML option</primary></indexterm>
-    session configuration parameter, which can be set using the
-    standard command:
-<synopsis>
-SET XML OPTION { DOCUMENT | CONTENT };
-</synopsis>
-<!## PG>
-    or the more PostgreSQL-like syntax
-<!## end>
-<!## XC>
-    or the more Postgres-XC-like syntax
-<!## end>
-<!## XL>
-    or the more Postgres-XL-like syntax
-<!## end>
-<synopsis>
-SET xmloption TO { DOCUMENT | CONTENT };
-</synopsis>
-    The default is <literal>CONTENT</literal>, so all forms of XML
-    data are allowed.
-   </para>
-
-   <note>
-    <para>
-     With the default XML option setting, you cannot directly cast
-     character strings to type <type>xml</type> if they contain a
-     document type declaration, because the definition of XML content
-     fragment does not accept them.  If you need to do that, either
-     use <literal>XMLPARSE</literal> or change the XML option.
-    </para>
-   </note>
-
-   </sect2>
-
-   <sect2>
-    <title>Encoding Handling</title>
-&common;
-   <para>
-    Care must be taken when dealing with multiple character encodings
-    on the client, server, and in the XML data passed through them.
-    When using the text mode to pass queries to the server and query
-<!## PG>
-    results to the client (which is the normal mode), PostgreSQL
-<!## end>
-<!## XC>
-    results to the client (which is the normal mode), Postgres-XC
-<!## end>
-<!## XL>
-    results to the client (which is the normal mode), Postgres-XL
-<!## end>
-    converts all character data passed between the client and the
-    server and vice versa to the character encoding of the respective
-    end; see <xref linkend="multibyte">.  This includes string
-    representations of XML values, such as in the above examples.
-    This would ordinarily mean that encoding declarations contained in
-    XML data can become invalid as the character data is converted
-    to other encodings while traveling between client and server,
-    because the embedded encoding declaration is not changed.  To cope
-    with this behavior, encoding declarations contained in
-    character strings presented for input to the <type>xml</type> type
-    are <emphasis>ignored</emphasis>, and content is assumed
-    to be in the current server encoding.  Consequently, for correct
-    processing, character strings of XML data must be sent
-    from the client in the current client encoding.  It is the
-    responsibility of the client to either convert documents to the
-    current client encoding before sending them to the server, or to
-    adjust the client encoding appropriately.  On output, values of
-    type <type>xml</type> will not have an encoding declaration, and
-    clients should assume all data is in the current client
-    encoding.
-   </para>
-
-   <para>
-    When using binary mode to pass query parameters to the server
-    and query results back to the client, no character set conversion
-    is performed, so the situation is different.  In this case, an
-    encoding declaration in the XML data will be observed, and if it
-    is absent, the data will be assumed to be in UTF-8 (as required by
-<!## PG>
-    the XML standard; note that PostgreSQL does not support UTF-16).
-<!## end>
-<!## XC>
-    the XML standard; note that Postgres-XC does not support UTF-16).
-<!## end>
-<!## XL>
-    the XML standard; note that Postgres-XL does not support UTF-16).
-<!## end>
-    On output, data will have an encoding declaration
-    specifying the client encoding, unless the client encoding is
-    UTF-8, in which case it will be omitted.
-   </para>
-
-   <para>
-<!## PG>
-    Needless to say, processing XML data with PostgreSQL will be less
-<!## end>
-<!## XC>
-    Needless to say, processing XML data with Postgres-XC will be less
-<!## end>
-<!## XL>
-    Needless to say, processing XML data with Postgres-XL will be less
-<!## end>
-    error-prone and more efficient if the XML data encoding, client encoding,
-    and server encoding are the same.  Since XML data is internally
-    processed in UTF-8, computations will be most efficient if the
-    server encoding is also UTF-8.
-   </para>
-
-   <caution>
-    <para>
-     Some XML-related functions may not work at all on non-ASCII data
-     when the server encoding is not UTF-8.  This is known to be an
-     issue for <function>xpath()</> in particular.
-    </para>
-   </caution>
-   </sect2>
-
-   <sect2>
-   <title>Accessing XML Values</title>
-&common;
-   <para>
-    The <type>xml</type> data type is unusual in that it does not
-    provide any comparison operators.  This is because there is no
-    well-defined and universally useful comparison algorithm for XML
-    data.  One consequence of this is that you cannot retrieve rows by
-    comparing an <type>xml</type> column against a search value.  XML
-    values should therefore typically be accompanied by a separate key
-    field such as an ID.  An alternative solution for comparing XML
-    values is to convert them to character strings first, but note
-    that character string comparison has little to do with a useful
-    XML comparison method.
-   </para>
-
-   <para>
-    Since there are no comparison operators for the <type>xml</type>
-    data type, it is not possible to create an index directly on a
-    column of this type.  If speedy searches in XML data are desired,
-    possible workarounds include casting the expression to a
-    character string type and indexing that, or indexing an XPath
-    expression.  Of course, the actual query would have to be adjusted
-    to search by the indexed expression.
-   </para>
-
-   <para>
-<!## PG>
-    The text-search functionality in PostgreSQL can also be used to speed
-<!## end>
-<!## XC>
-    The text-search functionality in Postgres-XC can also be used to speed
-<!## end>
-<!## XL>
-    The text-search functionality in Postgres-XL can also be used to speed
-<!## end>
-    up full-document searches of XML data.  The necessary
-<!## PG>
-    preprocessing support is, however, not yet available in the PostgreSQL
-<!## end>
-<!## XC>
-    preprocessing support is, however, not yet available in the Postgres-XC
-<!## end>
-<!## XL>
-    preprocessing support is, however, not yet available in the Postgres-XL
-<!## end>
-    distribution.
-   </para>
-   </sect2>
-  </sect1>
-
-  &array;
-
-  &rowtypes;
-
-  <sect1 id="datatype-oid">
-   <title>Object Identifier Types</title>
-
-   <indexterm zone="datatype-oid">
-    <primary>object identifier</primary>
-    <secondary>data type</secondary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>oid</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>regproc</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>regprocedure</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>regoper</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>regoperator</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>regclass</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>regtype</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>regconfig</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>regdictionary</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>xid</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>cid</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>tid</primary>
-   </indexterm>
-&common;
-   <para>
-    Object identifiers (OIDs) are used internally by
-<!## PG>
-    <productname>PostgreSQL</productname> as primary keys for various
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> as primary keys for various
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> as primary keys for various
-<!## end>
-    system tables.  OIDs are not added to user-created tables, unless
-    <literal>WITH OIDS</literal> is specified when the table is
-    created, or the <xref linkend="guc-default-with-oids">
-    configuration variable is enabled.  Type <type>oid</> represents
-    an object identifier.  There are also several alias types for
-    <type>oid</>: <type>regproc</>, <type>regprocedure</>,
-    <type>regoper</>, <type>regoperator</>, <type>regclass</>,
-    <type>regtype</>, <type>regconfig</>, and <type>regdictionary</>.
-    <xref linkend="datatype-oid-table"> shows an overview.
-   </para>
-
-   <para>
-    The <type>oid</> type is currently implemented as an unsigned
-    four-byte integer.  Therefore, it is not large enough to provide
-    database-wide uniqueness in large databases, or even in large
-    individual tables.  So, using a user-created table's OID column as
-    a primary key is discouraged.  OIDs are best used only for
-    references to system tables.
-   </para>
-
-   <para>
-    The <type>oid</> type itself has few operations beyond comparison.
-    It can be cast to integer, however, and then manipulated using the
-    standard integer operators.  (Beware of possible
-    signed-versus-unsigned confusion if you do this.)
-   </para>
-
-   <para>
-    The OID alias types have no operations of their own except
-    for specialized input and output routines.  These routines are able
-    to accept and display symbolic names for system objects, rather than
-    the raw numeric value that type <type>oid</> would use.  The alias
-    types allow simplified lookup of OID values for objects.  For example,
-    to examine the <structname>pg_attribute</> rows related to a table
-    <literal>mytable</>, one could write:
-<programlisting>
-SELECT * FROM pg_attribute WHERE attrelid = 'mytable'::regclass;
-</programlisting>
-    rather than:
-<programlisting>
-SELECT * FROM pg_attribute
-  WHERE attrelid = (SELECT oid FROM pg_class WHERE relname = 'mytable');
-</programlisting>
-    While that doesn't look all that bad by itself, it's still oversimplified.
-    A far more complicated sub-select would be needed to
-    select the right OID if there are multiple tables named
-    <literal>mytable</> in different schemas.
-    The <type>regclass</> input converter handles the table lookup according
-    to the schema path setting, and so it does the <quote>right thing</>
-    automatically.  Similarly, casting a table's OID to
-    <type>regclass</> is handy for symbolic display of a numeric OID.
-   </para>
-
-    <table id="datatype-oid-table">
-     <title>Object Identifier Types</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Name</entry>
-        <entry>References</entry>
-        <entry>Description</entry>
-        <entry>Value Example</entry>
-       </row>
-      </thead>
-
-      <tbody>
-
-       <row>
-        <entry><type>oid</></entry>
-        <entry>any</entry>
-        <entry>numeric object identifier</entry>
-        <entry><literal>564182</></entry>
-       </row>
-
-       <row>
-        <entry><type>regproc</></entry>
-        <entry><structname>pg_proc</></entry>
-        <entry>function name</entry>
-        <entry><literal>sum</></entry>
-       </row>
-
-       <row>
-        <entry><type>regprocedure</></entry>
-        <entry><structname>pg_proc</></entry>
-        <entry>function with argument types</entry>
-        <entry><literal>sum(int4)</></entry>
-       </row>
-
-       <row>
-        <entry><type>regoper</></entry>
-        <entry><structname>pg_operator</></entry>
-        <entry>operator name</entry>
-        <entry><literal>+</></entry>
-       </row>
-
-       <row>
-        <entry><type>regoperator</></entry>
-        <entry><structname>pg_operator</></entry>
-        <entry>operator with argument types</entry>
-        <entry><literal>*(integer,integer)</> or <literal>-(NONE,integer)</></entry>
-       </row>
-
-       <row>
-        <entry><type>regclass</></entry>
-        <entry><structname>pg_class</></entry>
-        <entry>relation name</entry>
-        <entry><literal>pg_type</></entry>
-       </row>
-
-       <row>
-        <entry><type>regtype</></entry>
-        <entry><structname>pg_type</></entry>
-        <entry>data type name</entry>
-        <entry><literal>integer</></entry>
-       </row>
-
-       <row>
-        <entry><type>regconfig</></entry>
-        <entry><structname>pg_ts_config</></entry>
-        <entry>text search configuration</entry>
-        <entry><literal>english</></entry>
-       </row>
-
-       <row>
-        <entry><type>regdictionary</></entry>
-        <entry><structname>pg_ts_dict</></entry>
-        <entry>text search dictionary</entry>
-        <entry><literal>simple</></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    All of the OID alias types accept schema-qualified names, and will
-    display schema-qualified names on output if the object would not
-    be found in the current search path without being qualified.
-    The <type>regproc</> and <type>regoper</> alias types will only
-    accept input names that are unique (not overloaded), so they are
-    of limited use; for most uses <type>regprocedure</> or
-    <type>regoperator</> are more appropriate.  For <type>regoperator</>,
-    unary operators are identified by writing <literal>NONE</> for the unused
-    operand.
-   </para>
-
-   <para>
-    An additional property of the OID alias types is the creation of
-    dependencies.  If a
-    constant of one of these types appears in a stored expression
-    (such as a column default expression or view), it creates a dependency
-    on the referenced object.  For example, if a column has a default
-    expression <literal>nextval('my_seq'::regclass)</>,
-<!## PG>
-    <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>
-<!## end>
-    understands that the default expression depends on the sequence
-    <literal>my_seq</>; the system will not let the sequence be dropped
-    without first removing the default expression.
-   </para>
-
-   <para>
-    Another identifier type used by the system is <type>xid</>, or transaction
-    (abbreviated <abbrev>xact</>) identifier.  This is the data type of the system columns
-    <structfield>xmin</> and <structfield>xmax</>.  Transaction identifiers are 32-bit quantities.
-   </para>
-
-   <para>
-    A third identifier type used by the system is <type>cid</>, or
-    command identifier.  This is the data type of the system columns
-    <structfield>cmin</> and <structfield>cmax</>. Command identifiers are also 32-bit quantities.
-   </para>
-
-   <para>
-    A final identifier type used by the system is <type>tid</>, or tuple
-    identifier (row identifier).  This is the data type of the system column
-    <structfield>ctid</>.  A tuple ID is a pair
-    (block number, tuple index within block) that identifies the
-    physical location of the row within its table.
-   </para>
-
-   <para>
-    (The system columns are further explained in <xref
-    linkend="ddl-system-columns">.)
-   </para>
-<!## XC>
-   <para>
-    Please note that <productname>Postgres-XC</> enforces OID identity only locally.
-    Different object at different Coordinator or Datanode may be assigned the same
-    OID value.
-   </para>
-<!## end>
-<!## XL>
-   <para>
-    Please note that <productname>Postgres-XL</> enforces OID identity only locally.
-    Different object at different Coordinator or Datanode may be assigned the same
-    OID value.
-   </para>
-<!## end>
-  </sect1>
-
-  <sect1 id="datatype-pseudo">
-   <title>Pseudo-Types</title>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>record</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>any</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>anyelement</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>anyarray</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>anynonarray</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>anyenum</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>void</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>trigger</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>language_handler</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>fdw_handler</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>cstring</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>internal</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-pseudo">
-    <primary>opaque</primary>
-   </indexterm>
-&common;
-   <para>
-<!## PG>
-    The <productname>PostgreSQL</productname> type system contains a
-<!## end>
-<!## XC>
-    The <productname>Postgres-XC</productname> type system contains a
-<!## end>
-<!## XL>
-    The <productname>Postgres-XL</productname> type system contains a
-<!## end>
-    number of special-purpose entries that are collectively called
-    <firstterm>pseudo-types</>.  A pseudo-type cannot be used as a
-    column data type, but it can be used to declare a function's
-    argument or result type.  Each of the available pseudo-types is
-    useful in situations where a function's behavior does not
-    correspond to simply taking or returning a value of a specific
-    <acronym>SQL</acronym> data type.  <xref
-    linkend="datatype-pseudotypes-table"> lists the existing
-    pseudo-types.
-   </para>
-
-    <table id="datatype-pseudotypes-table">
-     <title>Pseudo-Types</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>Name</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry><type>any</></entry>
-        <entry>Indicates that a function accepts any input data type.</entry>
-       </row>
-
-       <row>
-        <entry><type>anyarray</></entry>
-        <entry>Indicates that a function accepts any array data type
-        (see <xref linkend="extend-types-polymorphic">).</entry>
-       </row>
-
-       <row>
-        <entry><type>anyelement</></entry>
-        <entry>Indicates that a function accepts any data type
-        (see <xref linkend="extend-types-polymorphic">).</entry>
-       </row>
-
-       <row>
-        <entry><type>anyenum</></entry>
-        <entry>Indicates that a function accepts any enum data type
-        (see <xref linkend="extend-types-polymorphic"> and
-        <xref linkend="datatype-enum">).</entry>
-       </row>
-
-       <row>
-        <entry><type>anynonarray</></entry>
-        <entry>Indicates that a function accepts any non-array data type
-        (see <xref linkend="extend-types-polymorphic">).</entry>
-       </row>
-
-       <row>
-        <entry><type>cstring</></entry>
-        <entry>Indicates that a function accepts or returns a null-terminated C string.</entry>
-       </row>
-
-       <row>
-        <entry><type>internal</></entry>
-        <entry>Indicates that a function accepts or returns a server-internal
-        data type.</entry>
-       </row>
-
-       <row>
-        <entry><type>language_handler</></entry>
-        <entry>A procedural language call handler is declared to return <type>language_handler</>.</entry>
-       </row>
-
-       <row>
-        <entry><type>fdw_handler</></entry>
-        <entry>A foreign-data wrapper handler is declared to return <type>fdw_handler</>.</entry>
-       </row>
-
-       <row>
-        <entry><type>record</></entry>
-        <entry>Identifies a function returning an unspecified row type.</entry>
-       </row>
-
-       <row>
-        <entry><type>trigger</></entry>
-        <entry>A trigger function is declared to return <type>trigger.</></entry>
-       </row>
-
-       <row>
-        <entry><type>void</></entry>
-        <entry>Indicates that a function returns no value.</entry>
-       </row>
-
-       <row>
-        <entry><type>opaque</></entry>
-        <entry>An obsolete type name that formerly served all the above purposes.</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Functions coded in C (whether built-in or dynamically loaded) can be
-    declared to accept or return any of these pseudo data types.  It is up to
-    the function author to ensure that the function will behave safely
-    when a pseudo-type is used as an argument type.
-   </para>
-
-   <para>
-    Functions coded in procedural languages can use pseudo-types only as
-    allowed by their implementation languages.  At present the procedural
-    languages all forbid use of a pseudo-type as argument type, and allow
-    only <type>void</> and <type>record</> as a result type (plus
-    <type>trigger</> when the function is used as a trigger).  Some also
-    support polymorphic functions using the types <type>anyarray</>,
-    <type>anyelement</>, <type>anyenum</>, and <type>anynonarray</>.
-   </para>
-
-   <para>
-    The <type>internal</> pseudo-type is used to declare functions
-    that are meant only to be called internally by the database
-    system, and not by direct invocation in an <acronym>SQL</acronym>
-    query.  If a function has at least one <type>internal</>-type
-    argument then it cannot be called from <acronym>SQL</acronym>.  To
-    preserve the type safety of this restriction it is important to
-    follow this coding rule: do not create any function that is
-    declared to return <type>internal</> unless it has at least one
-    <type>internal</> argument.
-   </para>
-
-  </sect1>
-
- </chapter>
diff --git a/doc-xc/src/sgml/datetime.sgmlin b/doc-xc/src/sgml/datetime.sgmlin
deleted file mode 100644
index 41c0f9dd4c..0000000000
--- a/doc-xc/src/sgml/datetime.sgmlin
+++ /dev/null
@@ -1,633 +0,0 @@
-<!-- doc/src/sgml/datetime.sgml -->
-
- <appendix id="datetime-appendix">
-  <title>Date/Time Support</title>
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> uses an internal heuristic
-   parser for all date/time input support. Dates and times are input as
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> inherits uses an internal heuristic
-   parser from <productname>PostgreSQL</> for all date/time input support. Dates and times are input as
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> inherits uses an internal heuristic
-   parser from <productname>PostgreSQL</> for all date/time input support. Dates and times are input as
-<!## end>
-   strings, and are broken up into distinct fields with a preliminary
-   determination of what kind of information can be in the
-   field. Each field is interpreted and either assigned a numeric
-   value, ignored, or rejected.
-   The parser contains internal lookup tables for all textual fields,
-   including months, days of the week, and time zones.
-  </para>
-
-  <para>
-   This appendix includes information on the content of these
-   lookup tables and describes the steps used by the parser to decode
-   dates and times.
-  </para>
-
-  <sect1 id="datetime-input-rules">
-   <title>Date/Time Input Interpretation</title>
-
-&common;
-   <para>
-    The date/time type inputs are all decoded using the following procedure.
-   </para>
-
-   <procedure>
-    <step>
-     <para>
-      Break the input string into tokens and categorize each token as
-      a string, time, time zone, or number.
-     </para>
-
-     <substeps>
-      <step>
-       <para>
-        If the numeric token contains a colon (<literal>:</>), this is
-        a time string. Include all subsequent digits and colons.
-       </para>
-      </step>
-
-      <step>
-       <para>
-        If the numeric token contains a dash (<literal>-</>), slash
-        (<literal>/</>), or two or more dots (<literal>.</>), this is
-        a date string which might have a text month.  If a date token has
-        already been seen, it is instead interpreted as a time zone
-        name (e.g., <literal>America/New_York</>).
-       </para>
-      </step>
-
-      <step>
-       <para>
-        If the token is numeric only, then it is either a single field
-        or an ISO 8601 concatenated date (e.g.,
-        <literal>19990113</literal> for January 13, 1999) or time
-        (e.g., <literal>141516</literal> for 14:15:16).
-       </para>
-      </step>
-
-      <step>
-       <para>
-        If the token starts with a plus (<literal>+</>) or minus
-        (<literal>-</>), then it is either a numeric time zone or a special
-        field.
-       </para>
-      </step>
-     </substeps>
-    </step>
-
-    <step>
-     <para>
-      If the token is a text string, match up with possible strings:
-     </para>
-
-     <substeps>
-      <step>
-       <para>
-        Do a binary-search table lookup for the token as a time zone
-        abbreviation.
-       </para>
-      </step>
-
-      <step>
-       <para>
-        If not found, do a similar binary-search table lookup to match
-        the token as either a special string (e.g., <literal>today</literal>),
-        day (e.g., <literal>Thursday</literal>),
-        month (e.g., <literal>January</literal>),
-        or noise word (e.g., <literal>at</literal>, <literal>on</literal>).
-       </para>
-      </step>
-
-      <step>
-       <para>
-        If still not found, throw an error.
-       </para>
-      </step>
-     </substeps>
-    </step>
-
-    <step>
-     <para>
-      When the token is a number or number field:
-     </para>
-
-     <substeps>
-      <step>
-       <para>
-        If there are eight or six digits,
-        and if no other date fields have been previously read, then interpret
-        as a <quote>concatenated date</quote> (e.g.,
-        <literal>19990118</literal> or <literal>990118</literal>).
-        The interpretation is <literal>YYYYMMDD</> or <literal>YYMMDD</>.
-       </para>
-      </step>
-
-      <step>
-       <para>
-        If the token is three digits
-        and a year has already been read, then interpret as day of year.
-       </para>
-      </step>
-
-      <step>
-       <para>
-        If four or six digits and a year has already been read, then
-        interpret as a time (<literal>HHMM</> or <literal>HHMMSS</>).
-       </para>
-      </step>
-
-      <step>
-       <para>
-        If three or more digits and no date fields have yet been found,
-        interpret as a year (this forces yy-mm-dd ordering of the remaining
-        date fields).
-       </para>
-      </step>
-
-      <step>
-       <para>
-        Otherwise the date field ordering is assumed to follow the
-        <varname>DateStyle</> setting: mm-dd-yy, dd-mm-yy, or yy-mm-dd.
-        Throw an error if a month or day field is found to be out of range.
-       </para>
-      </step>
-     </substeps>
-    </step>
-
-    <step>
-     <para>
-      If BC has been specified, negate the year and add one for
-      internal storage.  (There is no year zero in the Gregorian
-      calendar, so numerically 1 BC becomes year zero.)
-     </para>
-    </step>
-
-    <step>
-     <para>
-      If BC was not specified, and if the year field was two digits in length,
-      then adjust the year to four digits. If the field is less than 70, then
-      add 2000, otherwise add 1900.
-
-      <tip>
-       <para>
-        Gregorian years AD 1-99 can be entered by using 4 digits with leading
-        zeros (e.g., <literal>0099</> is AD 99).
-       </para>
-      </tip>
-     </para>
-    </step>
-   </procedure>
-  </sect1>
-
-
-  <sect1 id="datetime-keywords">
-   <title>Date/Time Key Words</title>
-
-&common;
-   <para>
-    <xref linkend="datetime-month-table"> shows the tokens that are
-    recognized as names of months.
-   </para>
-
-    <table id="datetime-month-table">
-     <title>Month Names</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>Month</entry>
-        <entry>Abbreviations</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>January</entry>
-        <entry>Jan</entry>
-       </row>
-       <row>
-        <entry>February</entry>
-        <entry>Feb</entry>
-       </row>
-       <row>
-        <entry>March</entry>
-        <entry>Mar</entry>
-       </row>
-       <row>
-        <entry>April</entry>
-        <entry>Apr</entry>
-       </row>
-       <row>
-        <entry>May</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>June</entry>
-        <entry>Jun</entry>
-       </row>
-       <row>
-        <entry>July</entry>
-        <entry>Jul</entry>
-       </row>
-       <row>
-        <entry>August</entry>
-        <entry>Aug</entry>
-       </row>
-       <row>
-        <entry>September</entry>
-        <entry>Sep, Sept</entry>
-       </row>
-       <row>
-        <entry>October</entry>
-        <entry>Oct</entry>
-       </row>
-       <row>
-        <entry>November</entry>
-        <entry>Nov</entry>
-       </row>
-       <row>
-        <entry>December</entry>
-        <entry>Dec</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-    <para>
-     <xref linkend="datetime-dow-table"> shows the tokens that are
-     recognized as names of days of the week.
-    </para>
-
-     <table id="datetime-dow-table">
-      <title>Day of the Week Names</title>
-      <tgroup cols="2">
-       <thead>
-        <row>
-         <entry>Day</entry>
-         <entry>Abbreviations</entry>
-        </row>
-       </thead>
-       <tbody>
-        <row>
-         <entry>Sunday</entry>
-         <entry>Sun</entry>
-        </row>
-        <row>
-         <entry>Monday</entry>
-         <entry>Mon</entry>
-        </row>
-        <row>
-         <entry>Tuesday</entry>
-         <entry>Tue, Tues</entry>
-        </row>
-        <row>
-         <entry>Wednesday</entry>
-         <entry>Wed, Weds</entry>
-        </row>
-        <row>
-         <entry>Thursday</entry>
-         <entry>Thu, Thur, Thurs</entry>
-        </row>
-        <row>
-         <entry>Friday</entry>
-         <entry>Fri</entry>
-        </row>
-        <row>
-         <entry>Saturday</entry>
-         <entry>Sat</entry>
-        </row>
-       </tbody>
-      </tgroup>
-     </table>
-
-   <para>
-    <xref linkend="datetime-mod-table"> shows the tokens that serve
-    various modifier purposes.
-   </para>
-
-    <table id="datetime-mod-table">
-     <title>Date/Time Field Modifiers</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>Identifier</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><literal>AM</literal></entry>
-        <entry>Time is before 12:00</entry>
-       </row>
-       <row>
-        <entry><literal>AT</literal></entry>
-        <entry>Ignored</entry>
-       </row>
-       <row>
-        <entry><literal>JULIAN</>, <literal>JD</>, <literal>J</></entry>
-        <entry>Next field is Julian Day</entry>
-       </row>
-       <row>
-        <entry><literal>ON</literal></entry>
-        <entry>Ignored</entry>
-       </row>
-       <row>
-        <entry><literal>PM</literal></entry>
-        <entry>Time is on or after 12:00</entry>
-       </row>
-       <row>
-        <entry><literal>T</literal></entry>
-        <entry>Next field is time</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-  </sect1>
-
-  <sect1 id="datetime-config-files">
-  <title>Date/Time Configuration Files</title>
-
-   <indexterm>
-    <primary>time zone</primary>
-    <secondary>input abbreviations</secondary>
-   </indexterm>
-
-&common;
-   <para>
-    Since timezone abbreviations are not well standardized,
-<!## PG>
-    <productname>PostgreSQL</productname> provides a means to customize
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> provides a means to customize
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> provides a means to customize
-<!## end>
-    the set of abbreviations accepted by the server.  The
-    <xref linkend="guc-timezone-abbreviations"> run-time parameter
-    determines the active set of abbreviations.  While this parameter
-    can be altered by any database user, the possible values for it
-    are under the control of the database administrator &mdash; they
-    are in fact names of configuration files stored in
-    <filename>.../share/timezonesets/</> of the installation directory.
-    By adding or altering files in that directory, the administrator
-    can set local policy for timezone abbreviations.
-   </para>
-
-   <para>
-    <varname>timezone_abbreviations</> can be set to any file name
-    found in <filename>.../share/timezonesets/</>, if the file's name
-    is entirely alphabetic.  (The prohibition against non-alphabetic
-    characters in <varname>timezone_abbreviations</> prevents reading
-    files outside the intended directory, as well as reading editor
-    backup files and other extraneous files.)
-   </para>
-
-   <para>
-    A timezone abbreviation file can contain blank lines and comments
-    beginning with <literal>#</>.  Non-comment lines must have one of
-    these formats:
-
-<synopsis>
-<replaceable>time_zone_name</replaceable> <replaceable>offset</replaceable>
-<replaceable>time_zone_name</replaceable> <replaceable>offset</replaceable> D
-@INCLUDE <replaceable>file_name</replaceable>
-@OVERRIDE
-</synopsis>
-   </para>
-
-   <para>
-    A <replaceable>time_zone_name</replaceable> is just the abbreviation
-    being defined.  The <replaceable>offset</replaceable> is the zone's
-    offset in seconds from UTC, positive being east from Greenwich and
-    negative being west.  For example, -18000 would be five hours west
-    of Greenwich, or North American east coast standard time.  <literal>D</>
-    indicates that the zone name represents local daylight-savings time
-    rather than standard time. Since all known time zone offsets are on
-    15 minute boundaries, the number of seconds has to be a multiple of 900.
-   </para>
-
-   <para>
-    The <literal>@INCLUDE</> syntax allows inclusion of another file in the
-    <filename>.../share/timezonesets/</> directory.  Inclusion can be nested,
-    to a limited depth.
-   </para>
-
-   <para>
-    The <literal>@OVERRIDE</> syntax indicates that subsequent entries in the
-    file can override previous entries (i.e., entries obtained from included
-    files).  Without this, conflicting definitions of the same timezone
-    abbreviation are considered an error.
-   </para>
-
-   <para>
-    In an unmodified installation, the file <filename>Default</> contains
-    all the non-conflicting time zone abbreviations for most of the world.
-    Additional files <filename>Australia</> and <filename>India</> are
-    provided for those regions: these files first include the
-    <literal>Default</> file and then add or modify timezones as needed.
-   </para>
-
-   <para>
-    For reference purposes, a standard installation also contains files
-    <filename>Africa.txt</>, <filename>America.txt</>, etc, containing
-    information about every time zone abbreviation known to be in use
-    according to the <literal>zoneinfo</> timezone database.  The zone name
-    definitions found in these files can be copied and pasted into a custom
-    configuration file as needed.  Note that these files cannot be directly
-    referenced as <varname>timezone_abbreviations</> settings, because of
-    the dot embedded in their names.
-   </para>
-
-   <note>
-    <para>
-     If an error occurs while reading the time zone data sets, no new value is
-     applied but the old set is kept. If the error occurs while starting the
-     database, startup fails.
-    </para>
-   </note>
-
-   <caution>
-    <para>
-     Time zone abbreviations defined in the configuration file override
-<!## PG>
-     non-timezone meanings built into <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-     non-timezone meanings built into <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-     non-timezone meanings built into <productname>Postgres-XL</productname>.
-<!## end>
-     For example, the <filename>Australia</> configuration file defines
-     <literal>SAT</> (for South Australian Standard Time).  When this
-     file is active, <literal>SAT</> will not be recognized as an abbreviation
-     for Saturday.
-    </para>
-   </caution>
-
-   <caution>
-    <para>
-     If you modify files in <filename>.../share/timezonesets/</>,
-     it is up to you to make backups &mdash; a normal database dump
-     will not include this directory.
-    </para>
-   </caution>
-
-  </sect1>
-
-  <sect1 id="datetime-units-history">
-  <title>History of Units</title>
-
-&common;
-  <para>
-   The Julian calendar was introduced by Julius Caesar in 45 BC.
-   It was in common use in the Western world
-   until the year 1582, when countries started changing to the Gregorian
-   calendar.  In the Julian calendar, the tropical year is
-   approximated as 365 1/4 days = 365.25 days. This gives an error of
-   about 1 day in 128 years.
-  </para>
-
-  <para>
-   The accumulating calendar error prompted
-   Pope Gregory XIII to reform the calendar in accordance with
-   instructions from the Council of Trent.
-   In the Gregorian calendar, the tropical year is approximated as
-   365 + 97 / 400 days = 365.2425 days. Thus it takes approximately 3300
-   years for the tropical year to shift one day with respect to the
-   Gregorian calendar.
-  </para>
-
-  <para>
-   The approximation 365+97/400 is achieved by having 97 leap years
-   every 400 years, using the following rules:
-
-   <simplelist>
-    <member>
-     Every year divisible by 4 is a leap year.
-    </member>
-    <member>
-     However, every year divisible by 100 is not a leap year.
-    </member>
-    <member>
-     However, every year divisible by 400 is a leap year after all.
-    </member>
-   </simplelist>
-
-   So, 1700, 1800, 1900, 2100, and 2200 are not leap years. But 1600,
-   2000, and 2400 are leap years.
-
-   By contrast, in the older Julian calendar all years divisible by 4 are leap
-   years.
-  </para>
-
-  <para>
-   The papal bull of February 1582 decreed that 10 days should be dropped
-   from October 1582 so that 15 October should follow immediately after
-   4 October.
-   This was observed in Italy, Poland, Portugal, and Spain. Other Catholic
-   countries followed shortly after, but Protestant countries were
-   reluctant to change, and the Greek Orthodox countries didn't change
-   until the start of the 20th century.
-
-   The reform was observed by Great Britain and Dominions (including what is
-   now the USA) in 1752.
-   Thus 2 September 1752 was followed by 14 September 1752.
-
-   This is why Unix systems have the <command>cal</command> program
-   produce the following:
-
-<screen>
-$ <userinput>cal 9 1752</userinput>
-   September 1752
- S  M Tu  W Th  F  S
-       1  2 14 15 16
-17 18 19 20 21 22 23
-24 25 26 27 28 29 30
-</screen>
-  </para>
-
-  <para>
-   The SQL standard states that <quote>Within the definition of a
-   <quote>datetime literal</quote>, the <quote>datetime
-   value</quote>s are constrained by the natural rules for dates and
-   times according to the Gregorian calendar</quote>.  Dates between
-   1582-10-05 and 1582-10-14, although eliminated in some countries
-   by Papal fiat, conform to <quote>natural rules</quote> and are
-<!## PG>
-   hence valid dates.  <productname>PostgreSQL</> follows the SQL
-<!## end>
-<!## XC>
-   hence valid dates.  <productname>Postgres-XC</> follows the SQL
-<!## end>
-<!## XL>
-   hence valid dates.  <productname>Postgres-XL</> follows the SQL
-<!## end>
-   standard's lead by counting dates exclusively in the Gregorian
-   calendar, even for years before that calendar was in use.
-  </para>
-
-  <para>
-   Different calendars have been developed in various parts of the
-   world, many predating the Gregorian system.
-
-   For example,
-   the beginnings of the Chinese calendar can be traced back to the 14th
-   century BC. Legend has it that the Emperor Huangdi invented that
-   calendar in 2637 BC.
-
-   The People's Republic of China uses the Gregorian calendar
-   for civil purposes. The Chinese calendar is used for determining
-   festivals.
-  </para>
-
-  <para>
-   The <quote>Julian Date</quote> is unrelated to the <quote>Julian
-   calendar</quote>.
-   The Julian Date system was invented by the French scholar
-   Joseph Justus Scaliger (1540-1609)
-   and probably takes its name from Scaliger's father,
-   the Italian scholar Julius Caesar Scaliger (1484-1558).
-   In the Julian Date system, each day has a sequential number, starting
-   from JD 0 (which is sometimes called <emphasis>the</> Julian Date).
-   JD 0 corresponds to 1 January 4713 BC in the Julian calendar, or
-   24 November 4714 BC in the Gregorian calendar.  Julian Date counting
-   is most often used by astronomers for labeling their nightly observations,
-   and therefore a date runs from noon UTC to the next noon UTC, rather than
-   from midnight to midnight: JD 0 designates the 24 hours from noon UTC on
-   1 January 4713 BC to noon UTC on 2 January 4713 BC.
-  </para>
-
-  <para>
-<!## PG>
-   Although <productname>PostgreSQL</> supports Julian Date notation for
-<!## end>
-<!## XC>
-   Although <productname>Postgres-XC</> supports Julian Date notation for
-<!## end>
-<!## XL>
-   Although <productname>Postgres-XL</> supports Julian Date notation for
-<!## end>
-   input and output of dates (and also uses them for some internal datetime
-   calculations), it does not observe the nicety of having dates run from
-<!## PG>
-   noon to noon.  <productname>PostgreSQL</> treats a Julian Date as running
-<!## end>
-<!## XC>
-   noon to noon.  <productname>Postgres-XC</> treats a Julian Date as running
-<!## end>
-<!## XL>
-   noon to noon.  <productname>Postgres-XL</> treats a Julian Date as running
-<!## end>
-   from midnight to midnight.
-  </para>
-
- </sect1>
-</appendix>
diff --git a/doc-xc/src/sgml/dblink.sgmlin b/doc-xc/src/sgml/dblink.sgmlin
deleted file mode 100644
index 28efce19a2..0000000000
--- a/doc-xc/src/sgml/dblink.sgmlin
+++ /dev/null
@@ -1,2717 +0,0 @@
-<!-- doc/src/sgml/dblink.sgml -->
-
-<sect1 id="dblink" xreflabel="dblink">
- <title>dblink</title>
-
- <indexterm zone="dblink">
-  <primary>dblink</primary>
- </indexterm>
-
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-
-&pgonly;
- <para>
-  <filename>dblink</> is a module which supports connections to
-  other <productname>PostgreSQL</> databases from within a database
-  session.
- </para>
-
- <refentry id="CONTRIB-DBLINK-CONNECT">
-  <refmeta>
-   <refentrytitle>dblink_connect</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_connect</refname>
-   <refpurpose>opens a persistent connection to a remote database</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_connect(text connstr) returns text
-dblink_connect(text connname, text connstr) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-   <para>
-    <function>dblink_connect()</> establishes a connection to a remote
-    <productname>PostgreSQL</> database.  The server and database to
-    be contacted are identified through a standard <application>libpq</>
-    connection string.  Optionally, a name can be assigned to the
-    connection.  Multiple named connections can be open at once, but
-    only one unnamed connection is permitted at a time.  The connection
-    will persist until closed or until the database session is ended.
-   </para>
-
-   <para>
-    The connection string may also be the name of an existing foreign
-    server.  It is recommended to use
-    the <function>postgresql_fdw_validator</function> when defining
-    the corresponding foreign-data wrapper.  See the example below, as
-    well as the following:
-    <simplelist type="inline">
-     <member><xref linkend="sql-createforeigndatawrapper"></member>
-     <member><xref linkend="sql-createserver"></member>
-     <member><xref linkend="sql-createusermapping"></member>
-    </simplelist>
-   </para>
-
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       The name to use for this connection; if omitted, an unnamed
-       connection is opened, replacing any existing unnamed connection.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>connstr</parameter></term>
-     <listitem>
-      <para>
-       <application>libpq</>-style connection info string, for example
-       <literal>hostaddr=127.0.0.1 port=5432 dbname=mydb user=postgres
-       password=mypasswd</>.
-       For details see <function>PQconnectdb</> in
-       <xref linkend="libpq-connect">.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-   <para>
-    Returns status, which is always <literal>OK</> (since any error
-    causes the function to throw an error instead of returning).
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Notes</title>
-&pgonly;
-   <para>
-    Only superusers may use <function>dblink_connect</> to create
-    non-password-authenticated connections.  If non-superusers need this
-    capability, use <function>dblink_connect_u</> instead.
-   </para>
-
-   <para>
-    It is unwise to choose connection names that contain equal signs,
-    as this opens a risk of confusion with connection info strings
-    in other <filename>dblink</> functions.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-<screen>
-SELECT dblink_connect('dbname=postgres');
- dblink_connect
-----------------
- OK
-(1 row)
-
-SELECT dblink_connect('myconn', 'dbname=postgres');
- dblink_connect
-----------------
- OK
-(1 row)
-
--- FOREIGN DATA WRAPPER functionality
--- Note: local connection must require password authentication for this to work properly
---       Otherwise, you will receive the following error from dblink_connect():
---       ----------------------------------------------------------------------
---       ERROR:  password is required
---       DETAIL:  Non-superuser cannot connect if the server does not request a password.
---       HINT:  Target server's authentication method must be changed.
-CREATE USER dblink_regression_test WITH PASSWORD 'secret';
-CREATE FOREIGN DATA WRAPPER postgresql VALIDATOR postgresql_fdw_validator;
-CREATE SERVER fdtest FOREIGN DATA WRAPPER postgresql OPTIONS (hostaddr '127.0.0.1', dbname 'contrib_regression');
-
-CREATE USER MAPPING FOR dblink_regression_test SERVER fdtest OPTIONS (user 'dblink_regression_test', password 'secret');
-GRANT USAGE ON FOREIGN SERVER fdtest TO dblink_regression_test;
-GRANT SELECT ON TABLE foo TO dblink_regression_test;
-
-\set ORIGINAL_USER :USER
-\c - dblink_regression_test
-SELECT dblink_connect('myconn', 'fdtest');
- dblink_connect 
-----------------
- OK
-(1 row)
-
-SELECT * FROM dblink('myconn','SELECT * FROM foo') AS t(a int, b text, c text[]);
- a  | b |       c       
-----+---+---------------
-  0 | a | {a0,b0,c0}
-  1 | b | {a1,b1,c1}
-  2 | c | {a2,b2,c2}
-  3 | d | {a3,b3,c3}
-  4 | e | {a4,b4,c4}
-  5 | f | {a5,b5,c5}
-  6 | g | {a6,b6,c6}
-  7 | h | {a7,b7,c7}
-  8 | i | {a8,b8,c8}
-  9 | j | {a9,b9,c9}
- 10 | k | {a10,b10,c10}
-(11 rows)
-
-\c - :ORIGINAL_USER
-REVOKE USAGE ON FOREIGN SERVER fdtest FROM dblink_regression_test;
-REVOKE SELECT ON TABLE foo FROM  dblink_regression_test;
-DROP USER MAPPING FOR dblink_regression_test SERVER fdtest;
-DROP USER dblink_regression_test;
-DROP SERVER fdtest;
-DROP FOREIGN DATA WRAPPER postgresql;
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-CONNECT-U">
-  <refmeta>
-   <refentrytitle>dblink_connect_u</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_connect_u</refname>
-   <refpurpose>opens a persistent connection to a remote database, insecurely</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_connect_u(text connstr) returns text
-dblink_connect_u(text connname, text connstr) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-   <para>
-    <function>dblink_connect_u()</> is identical to
-    <function>dblink_connect()</>, except that it will allow non-superusers
-    to connect using any authentication method.
-   </para>
-
-   <para>
-    If the remote server selects an authentication method that does not
-    involve a password, then impersonation and subsequent escalation of
-    privileges can occur, because the session will appear to have
-    originated from the user as which the local <productname>PostgreSQL</>
-    server runs.  Also, even if the remote server does demand a password,
-    it is possible for the password to be supplied from the server
-    environment, such as a <filename>~/.pgpass</> file belonging to the
-    server's user.  This opens not only a risk of impersonation, but the
-    possibility of exposing a password to an untrustworthy remote server.
-    Therefore, <function>dblink_connect_u()</> is initially
-    installed with all privileges revoked from <literal>PUBLIC</>,
-    making it un-callable except by superusers.  In some situations
-    it may be appropriate to grant <literal>EXECUTE</> permission for
-    <function>dblink_connect_u()</> to specific users who are considered
-    trustworthy, but this should be done with care.  It is also recommended
-    that any <filename>~/.pgpass</> file belonging to the server's user
-    <emphasis>not</> contain any records specifying a wildcard host name.
-   </para>
-
-   <para>
-    For further details see <function>dblink_connect()</>.
-   </para>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-DISCONNECT">
-  <refmeta>
-   <refentrytitle>dblink_disconnect</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_disconnect</refname>
-   <refpurpose>closes a persistent connection to a remote database</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_disconnect() returns text
-dblink_disconnect(text connname) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-   <para>
-    <function>dblink_disconnect()</> closes a connection previously opened
-    by <function>dblink_connect()</>.  The form with no arguments closes
-    an unnamed connection.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       The name of a named connection to be closed.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-   <para>
-    Returns status, which is always <literal>OK</> (since any error
-    causes the function to throw an error instead of returning).
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-SELECT dblink_disconnect();
- dblink_disconnect
--------------------
- OK
-(1 row)
-
-SELECT dblink_disconnect('myconn');
- dblink_disconnect
--------------------
- OK
-(1 row)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-FUNCTION">
-  <refmeta>
-   <refentrytitle>dblink</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink</refname>
-   <refpurpose>executes a query in a remote database</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink(text connname, text sql [, bool fail_on_error]) returns setof record
-dblink(text connstr, text sql [, bool fail_on_error]) returns setof record
-dblink(text sql [, bool fail_on_error]) returns setof record
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink</> executes a query (usually a <command>SELECT</>,
-    but it can be any SQL statement that returns rows) in a remote database.
-   </para>
-
-   <para>
-    When two <type>text</> arguments are given, the first one is first
-    looked up as a persistent connection's name; if found, the command
-    is executed on that connection.  If not found, the first argument
-    is treated as a connection info string as for <function>dblink_connect</>,
-    and the indicated connection is made just for the duration of this command.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       Name of the connection to use; omit this parameter to use the
-       unnamed connection.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>connstr</parameter></term>
-     <listitem>
-      <para>
-       A connection info string, as previously described for
-       <function>dblink_connect</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>sql</parameter></term>
-     <listitem>
-      <para>
-       The SQL query that you wish to execute in the remote database,
-       for example <literal>select * from foo</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>fail_on_error</parameter></term>
-     <listitem>
-      <para>
-       If true (the default when omitted) then an error thrown on the
-       remote side of the connection causes an error to also be thrown
-       locally. If false, the remote error is locally reported as a NOTICE,
-       and the function returns no rows.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>
-    The function returns the row(s) produced by the query.  Since
-    <function>dblink</> can be used with any query, it is declared
-    to return <type>record</>, rather than specifying any particular
-    set of columns.  This means that you must specify the expected
-    set of columns in the calling query &mdash; otherwise
-    <productname>PostgreSQL</> would not know what to expect.
-    Here is an example:
-
-<programlisting>
-SELECT *
-    FROM dblink('dbname=mydb', 'select proname, prosrc from pg_proc')
-      AS t1(proname name, prosrc text)
-    WHERE proname LIKE 'bytea%';
-</programlisting>
-
-    The <quote>alias</> part of the <literal>FROM</> clause must
-    specify the column names and types that the function will return.
-    (Specifying column names in an alias is actually standard SQL
-    syntax, but specifying column types is a <productname>PostgreSQL</>
-    extension.)  This allows the system to understand what
-    <literal>*</> should expand to, and what <structname>proname</>
-    in the <literal>WHERE</> clause refers to, in advance of trying
-    to execute the function.  At run time, an error will be thrown
-    if the actual query result from the remote database does not
-    have the same number of columns shown in the <literal>FROM</> clause.
-    The column names need not match, however, and <function>dblink</>
-    does not insist on exact type matches either.  It will succeed
-    so long as the returned data strings are valid input for the
-    column type declared in the <literal>FROM</> clause.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Notes</title>
-&pgonly;
-
-   <para>
-    <function>dblink</> fetches the entire remote query result before
-    returning any of it to the local system.  If the query is expected
-    to return a large number of rows, it's better to open it as a cursor
-    with <function>dblink_open</> and then fetch a manageable number
-    of rows at a time.
-   </para>
-
-   <para>
-    A convenient way to use <function>dblink</> with predetermined
-    queries is to create a view.
-    This allows the column type information to be buried in the view,
-    instead of having to spell it out in every query.  For example,
-
-<programlisting>
-CREATE VIEW myremote_pg_proc AS
-  SELECT *
-    FROM dblink('dbname=postgres', 'select proname, prosrc from pg_proc')
-    AS t1(proname name, prosrc text);
-
-SELECT * FROM myremote_pg_proc WHERE proname LIKE 'bytea%';
-</programlisting>
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-SELECT * FROM dblink('dbname=postgres', 'select proname, prosrc from pg_proc')
-  AS t1(proname name, prosrc text) WHERE proname LIKE 'bytea%';
-  proname   |   prosrc
-------------+------------
- byteacat   | byteacat
- byteaeq    | byteaeq
- bytealt    | bytealt
- byteale    | byteale
- byteagt    | byteagt
- byteage    | byteage
- byteane    | byteane
- byteacmp   | byteacmp
- bytealike  | bytealike
- byteanlike | byteanlike
- byteain    | byteain
- byteaout   | byteaout
-(12 rows)
-
-SELECT dblink_connect('dbname=postgres');
- dblink_connect
-----------------
- OK
-(1 row)
-
-SELECT * FROM dblink('select proname, prosrc from pg_proc')
-  AS t1(proname name, prosrc text) WHERE proname LIKE 'bytea%';
-  proname   |   prosrc
-------------+------------
- byteacat   | byteacat
- byteaeq    | byteaeq
- bytealt    | bytealt
- byteale    | byteale
- byteagt    | byteagt
- byteage    | byteage
- byteane    | byteane
- byteacmp   | byteacmp
- bytealike  | bytealike
- byteanlike | byteanlike
- byteain    | byteain
- byteaout   | byteaout
-(12 rows)
-
-SELECT dblink_connect('myconn', 'dbname=regression');
- dblink_connect
-----------------
- OK
-(1 row)
-
-SELECT * FROM dblink('myconn', 'select proname, prosrc from pg_proc')
-  AS t1(proname name, prosrc text) WHERE proname LIKE 'bytea%';
-  proname   |   prosrc
-------------+------------
- bytearecv  | bytearecv
- byteasend  | byteasend
- byteale    | byteale
- byteagt    | byteagt
- byteage    | byteage
- byteane    | byteane
- byteacmp   | byteacmp
- bytealike  | bytealike
- byteanlike | byteanlike
- byteacat   | byteacat
- byteaeq    | byteaeq
- bytealt    | bytealt
- byteain    | byteain
- byteaout   | byteaout
-(14 rows)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-EXEC">
-  <refmeta>
-   <refentrytitle>dblink_exec</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_exec</refname>
-   <refpurpose>executes a command in a remote database</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_exec(text connname, text sql [, bool fail_on_error]) returns text
-dblink_exec(text connstr, text sql [, bool fail_on_error]) returns text
-dblink_exec(text sql [, bool fail_on_error]) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_exec</> executes a command (that is, any SQL statement
-    that doesn't return rows) in a remote database.
-   </para>
-
-   <para>
-    When two <type>text</> arguments are given, the first one is first
-    looked up as a persistent connection's name; if found, the command
-    is executed on that connection.  If not found, the first argument
-    is treated as a connection info string as for <function>dblink_connect</>,
-    and the indicated connection is made just for the duration of this command.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       Name of the connection to use; omit this parameter to use the
-       unnamed connection.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>connstr</parameter></term>
-     <listitem>
-      <para>
-       A connection info string, as previously described for
-       <function>dblink_connect</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>sql</parameter></term>
-     <listitem>
-      <para>
-       The SQL command that you wish to execute in the remote database,
-       for example
-       <literal>insert into foo values(0,'a','{"a0","b0","c0"}')</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>fail_on_error</parameter></term>
-     <listitem>
-      <para>
-       If true (the default when omitted) then an error thrown on the
-       remote side of the connection causes an error to also be thrown
-       locally. If false, the remote error is locally reported as a NOTICE,
-       and the function's return value is set to <literal>ERROR</>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>
-    Returns status, either the command's status string or <literal>ERROR</>.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-SELECT dblink_connect('dbname=dblink_test_standby');
- dblink_connect
-----------------
- OK
-(1 row)
-
-SELECT dblink_exec('insert into foo values(21,''z'',''{"a0","b0","c0"}'');');
-   dblink_exec
------------------
- INSERT 943366 1
-(1 row)
-
-SELECT dblink_connect('myconn', 'dbname=regression');
- dblink_connect
-----------------
- OK
-(1 row)
-
-SELECT dblink_exec('myconn', 'insert into foo values(21,''z'',''{"a0","b0","c0"}'');');
-   dblink_exec
-------------------
- INSERT 6432584 1
-(1 row)
-
-SELECT dblink_exec('myconn', 'insert into pg_class values (''foo'')',false);
-NOTICE:  sql error
-DETAIL:  ERROR:  null value in column "relnamespace" violates not-null constraint
-
- dblink_exec
--------------
- ERROR
-(1 row)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-OPEN">
-  <refmeta>
-   <refentrytitle>dblink_open</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_open</refname>
-   <refpurpose>opens a cursor in a remote database</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_open(text cursorname, text sql [, bool fail_on_error]) returns text
-dblink_open(text connname, text cursorname, text sql [, bool fail_on_error]) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_open()</> opens a cursor in a remote database.
-    The cursor can subsequently be manipulated with
-    <function>dblink_fetch()</> and <function>dblink_close()</>.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       Name of the connection to use; omit this parameter to use the
-       unnamed connection.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>cursorname</parameter></term>
-     <listitem>
-      <para>
-       The name to assign to this cursor.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>sql</parameter></term>
-     <listitem>
-      <para>
-       The <command>SELECT</> statement that you wish to execute in the remote
-       database, for example <literal>select * from pg_class</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>fail_on_error</parameter></term>
-     <listitem>
-      <para>
-       If true (the default when omitted) then an error thrown on the
-       remote side of the connection causes an error to also be thrown
-       locally. If false, the remote error is locally reported as a NOTICE,
-       and the function's return value is set to <literal>ERROR</>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>
-    Returns status, either <literal>OK</> or <literal>ERROR</>.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Notes</title>
-&pgonly;
-
-   <para>
-    Since a cursor can only persist within a transaction,
-    <function>dblink_open</> starts an explicit transaction block
-    (<command>BEGIN</>) on the remote side, if the remote side was
-    not already within a transaction.  This transaction will be
-    closed again when the matching <function>dblink_close</> is
-    executed.  Note that if
-    you use <function>dblink_exec</> to change data between
-    <function>dblink_open</> and <function>dblink_close</>,
-    and then an error occurs or you use <function>dblink_disconnect</> before
-    <function>dblink_close</>, your change <emphasis>will be
-    lost</> because the transaction will be aborted.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-SELECT dblink_connect('dbname=postgres');
- dblink_connect
-----------------
- OK
-(1 row)
-
-SELECT dblink_open('foo', 'select proname, prosrc from pg_proc');
- dblink_open
--------------
- OK
-(1 row)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-FETCH">
-  <refmeta>
-   <refentrytitle>dblink_fetch</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_fetch</refname>
-   <refpurpose>returns rows from an open cursor in a remote database</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_fetch(text cursorname, int howmany [, bool fail_on_error]) returns setof record
-dblink_fetch(text connname, text cursorname, int howmany [, bool fail_on_error]) returns setof record
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_fetch</> fetches rows from a cursor previously
-    established by <function>dblink_open</>.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       Name of the connection to use; omit this parameter to use the
-       unnamed connection.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>cursorname</parameter></term>
-     <listitem>
-      <para>
-       The name of the cursor to fetch from.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>howmany</parameter></term>
-     <listitem>
-      <para>
-       The maximum number of rows to retrieve. The next <parameter>howmany</>
-       rows are fetched, starting at the current cursor position, moving
-       forward. Once the cursor has reached its end, no more rows are produced.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>fail_on_error</parameter></term>
-     <listitem>
-      <para>
-       If true (the default when omitted) then an error thrown on the
-       remote side of the connection causes an error to also be thrown
-       locally. If false, the remote error is locally reported as a NOTICE,
-       and the function returns no rows.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>
-    The function returns the row(s) fetched from the cursor.  To use this
-    function, you will need to specify the expected set of columns,
-    as previously discussed for <function>dblink</>.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Notes</title>
-&pgonly;
-
-   <para>
-    On a mismatch between the number of return columns specified in the
-    <literal>FROM</> clause, and the actual number of columns returned by the
-    remote cursor, an error will be thrown. In this event, the remote cursor
-    is still advanced by as many rows as it would have been if the error had
-    not occurred.  The same is true for any other error occurring in the local
-    query after the remote <command>FETCH</> has been done.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-SELECT dblink_connect('dbname=postgres');
- dblink_connect
-----------------
- OK
-(1 row)
-
-SELECT dblink_open('foo', 'select proname, prosrc from pg_proc where proname like ''bytea%''');
- dblink_open
--------------
- OK
-(1 row)
-
-SELECT * FROM dblink_fetch('foo', 5) AS (funcname name, source text);
- funcname |  source
-----------+----------
- byteacat | byteacat
- byteacmp | byteacmp
- byteaeq  | byteaeq
- byteage  | byteage
- byteagt  | byteagt
-(5 rows)
-
-SELECT * FROM dblink_fetch('foo', 5) AS (funcname name, source text);
- funcname  |  source
------------+-----------
- byteain   | byteain
- byteale   | byteale
- bytealike | bytealike
- bytealt   | bytealt
- byteane   | byteane
-(5 rows)
-
-SELECT * FROM dblink_fetch('foo', 5) AS (funcname name, source text);
-  funcname  |   source
-------------+------------
- byteanlike | byteanlike
- byteaout   | byteaout
-(2 rows)
-
-SELECT * FROM dblink_fetch('foo', 5) AS (funcname name, source text);
- funcname | source
-----------+--------
-(0 rows)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-CLOSE">
-  <refmeta>
-   <refentrytitle>dblink_close</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_close</refname>
-   <refpurpose>closes a cursor in a remote database</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_close(text cursorname [, bool fail_on_error]) returns text
-dblink_close(text connname, text cursorname [, bool fail_on_error]) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_close</> closes a cursor previously opened with
-    <function>dblink_open</>.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       Name of the connection to use; omit this parameter to use the
-       unnamed connection.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>cursorname</parameter></term>
-     <listitem>
-      <para>
-       The name of the cursor to close.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>fail_on_error</parameter></term>
-     <listitem>
-      <para>
-       If true (the default when omitted) then an error thrown on the
-       remote side of the connection causes an error to also be thrown
-       locally. If false, the remote error is locally reported as a NOTICE,
-       and the function's return value is set to <literal>ERROR</>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>
-    Returns status, either <literal>OK</> or <literal>ERROR</>.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Notes</title>
-&pgonly;
-
-   <para>
-    If <function>dblink_open</> started an explicit transaction block,
-    and this is the last remaining open cursor in this connection,
-    <function>dblink_close</> will issue the matching <command>COMMIT</>.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-SELECT dblink_connect('dbname=postgres');
- dblink_connect
-----------------
- OK
-(1 row)
-
-SELECT dblink_open('foo', 'select proname, prosrc from pg_proc');
- dblink_open
--------------
- OK
-(1 row)
-
-SELECT dblink_close('foo');
- dblink_close
---------------
- OK
-(1 row)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-GET-CONNECTIONS">
-  <refmeta>
-   <refentrytitle>dblink_get_connections</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_get_connections</refname>
-   <refpurpose>returns the names of all open named dblink connections</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_get_connections() returns text[]
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_get_connections</> returns an array of the names
-    of all open named <filename>dblink</> connections.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>Returns a text array of connection names, or NULL if none.</para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<programlisting>
-SELECT dblink_get_connections();
-</programlisting>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-ERROR-MESSAGE">
-  <refmeta>
-   <refentrytitle>dblink_error_message</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_error_message</refname>
-   <refpurpose>gets last error message on the named connection</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_error_message(text connname) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_error_message</> fetches the most recent remote
-    error message for a given connection.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       Name of the connection to use.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>
-    Returns last error message, or an empty string if there has been
-    no error in this connection.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<programlisting>
-SELECT dblink_error_message('dtest1');
-</programlisting>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-SEND-QUERY">
-  <refmeta>
-   <refentrytitle>dblink_send_query</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_send_query</refname>
-   <refpurpose>sends an async query to a remote database</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_send_query(text connname, text sql) returns int
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_send_query</> sends a query to be executed
-    asynchronously, that is, without immediately waiting for the result.
-    There must not be an async query already in progress on the
-    connection.
-   </para>
-
-   <para>
-    After successfully dispatching an async query, completion status
-    can be checked with <function>dblink_is_busy</>, and the results
-    are ultimately collected with <function>dblink_get_result</>.
-    It is also possible to attempt to cancel an active async query
-    using <function>dblink_cancel_query</>.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       Name of the connection to use.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>sql</parameter></term>
-     <listitem>
-      <para>
-       The SQL statement that you wish to execute in the remote database,
-       for example <literal>select * from pg_class</>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-
-&pgonly;
-   <para>
-    Returns 1 if the query was successfully dispatched, 0 otherwise.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<programlisting>
-SELECT dblink_send_query('dtest1', 'SELECT * FROM foo WHERE f1 &lt; 3');
-</programlisting>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-IS-BUSY">
-  <refmeta>
-   <refentrytitle>dblink_is_busy</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_is_busy</refname>
-   <refpurpose>checks if connection is busy with an async query</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_is_busy(text connname) returns int
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_is_busy</> tests whether an async query is in progress.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       Name of the connection to check.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>
-    Returns 1 if connection is busy, 0 if it is not busy.
-    If this function returns 0, it is guaranteed that
-    <function>dblink_get_result</> will not block.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<programlisting>
-SELECT dblink_is_busy('dtest1');
-</programlisting>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-GET-NOTIFY">
-  <refmeta>
-   <refentrytitle>dblink_get_notify</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_get_notify</refname>
-   <refpurpose>retrieve async notifications on a connection</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_get_notify() returns setof (notify_name text, be_pid int, extra text)
-dblink_get_notify(text connname) returns setof (notify_name text, be_pid int, extra text)
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-   <para>
-    <function>dblink_get_notify</> retrieves notifications on either
-    the unnamed connection, or on a named connection if specified.
-    To receive notifications via dblink, <function>LISTEN</> must
-    first be issued, using <function>dblink_exec</>.
-    For details see <xref linkend="sql-listen"> and <xref linkend="sql-notify">.
-   </para>
-
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       The name of a named connection to get notifications on.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-    <para>Returns <type>setof (notify_name text, be_pid int, extra text)</type>, or an empty set if none.</para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-SELECT dblink_exec('LISTEN virtual');
- dblink_exec 
--------------
- LISTEN
-(1 row)
-
-SELECT * FROM dblink_get_notify();
- notify_name | be_pid | extra
--------------+--------+-------
-(0 rows)
-
-NOTIFY virtual;
-NOTIFY
-
-SELECT * FROM dblink_get_notify();
- notify_name | be_pid | extra
--------------+--------+-------
- virtual     |   1229 |
-(1 row)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-GET-RESULT">
-  <refmeta>
-   <refentrytitle>dblink_get_result</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_get_result</refname>
-   <refpurpose>gets an async query result</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_get_result(text connname [, bool fail_on_error]) returns setof record
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_get_result</> collects the results of an
-    asynchronous query previously sent with <function>dblink_send_query</>.
-    If the query is not already completed, <function>dblink_get_result</>
-    will wait until it is.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       Name of the connection to use.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>fail_on_error</parameter></term>
-     <listitem>
-      <para>
-       If true (the default when omitted) then an error thrown on the
-       remote side of the connection causes an error to also be thrown
-       locally. If false, the remote error is locally reported as a NOTICE,
-       and the function returns no rows.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>
-    For an async query (that is, a SQL statement returning rows),
-    the function returns the row(s) produced by the query.  To use this
-    function, you will need to specify the expected set of columns,
-    as previously discussed for <function>dblink</>.
-   </para>
-
-   <para>
-    For an async command (that is, a SQL statement not returning rows),
-    the function returns a single row with a single text column containing
-    the command's status string.  It is still necessary to specify that
-    the result will have a single text column in the calling <literal>FROM</>
-    clause.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Notes</title>
-&pgonly;
-
-   <para>
-    This function <emphasis>must</> be called if
-    <function>dblink_send_query</> returned 1.
-    It must be called once for each query
-    sent, and one additional time to obtain an empty set result,
-    before the connection can be used again.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-contrib_regression=# SELECT dblink_connect('dtest1', 'dbname=contrib_regression');
- dblink_connect
-----------------
- OK
-(1 row)
-
-contrib_regression=# SELECT * FROM
-contrib_regression-# dblink_send_query('dtest1', 'select * from foo where f1 &lt; 3') AS t1;
- t1
-----
-  1
-(1 row)
-
-contrib_regression=# SELECT * FROM dblink_get_result('dtest1') AS t1(f1 int, f2 text, f3 text[]);
- f1 | f2 |     f3
-----+----+------------
-  0 | a  | {a0,b0,c0}
-  1 | b  | {a1,b1,c1}
-  2 | c  | {a2,b2,c2}
-(3 rows)
-
-contrib_regression=# SELECT * FROM dblink_get_result('dtest1') AS t1(f1 int, f2 text, f3 text[]);
- f1 | f2 | f3
-----+----+----
-(0 rows)
-
-contrib_regression=# SELECT * FROM
-contrib_regression-# dblink_send_query('dtest1', 'select * from foo where f1 &lt; 3; select * from foo where f1 &gt; 6') AS t1;
- t1
-----
-  1
-(1 row)
-
-contrib_regression=# SELECT * FROM dblink_get_result('dtest1') AS t1(f1 int, f2 text, f3 text[]);
- f1 | f2 |     f3
-----+----+------------
-  0 | a  | {a0,b0,c0}
-  1 | b  | {a1,b1,c1}
-  2 | c  | {a2,b2,c2}
-(3 rows)
-
-contrib_regression=# SELECT * FROM dblink_get_result('dtest1') AS t1(f1 int, f2 text, f3 text[]);
- f1 | f2 |      f3
-----+----+---------------
-  7 | h  | {a7,b7,c7}
-  8 | i  | {a8,b8,c8}
-  9 | j  | {a9,b9,c9}
- 10 | k  | {a10,b10,c10}
-(4 rows)
-
-contrib_regression=# SELECT * FROM dblink_get_result('dtest1') AS t1(f1 int, f2 text, f3 text[]);
- f1 | f2 | f3
-----+----+----
-(0 rows)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-CANCEL-QUERY">
-  <refmeta>
-   <refentrytitle>dblink_cancel_query</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_cancel_query</refname>
-   <refpurpose>cancels any active query on the named connection</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_cancel_query(text connname) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_cancel_query</> attempts to cancel any query that
-    is in progress on the named connection.  Note that this is not
-    certain to succeed (since, for example, the remote query might
-    already have finished).  A cancel request simply improves the
-    odds that the query will fail soon.  You must still complete the
-    normal query protocol, for example by calling
-    <function>dblink_get_result</>.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>conname</parameter></term>
-     <listitem>
-      <para>
-       Name of the connection to use.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-
-   <para>
-    Returns <literal>OK</> if the cancel request has been sent, or
-    the text of an error message on failure.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<programlisting>
-SELECT dblink_cancel_query('dtest1');
-</programlisting>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-GET-PKEY">
-  <refmeta>
-   <refentrytitle>dblink_get_pkey</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_get_pkey</refname>
-   <refpurpose>returns the positions and field names of a relation's
-    primary key fields
-   </refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_get_pkey(text relname) returns setof dblink_pkey_results
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_get_pkey</> provides information about the primary
-    key of a relation in the local database.  This is sometimes useful
-    in generating queries to be sent to remote databases.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>relname</parameter></term>
-     <listitem>
-      <para>
-       Name of a local relation, for example <literal>foo</> or
-       <literal>myschema.mytab</>.  Include double quotes if the
-       name is mixed-case or contains special characters, for
-       example <literal>"FooBar"</>; without quotes, the string
-       will be folded to lower case.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>
-    Returns one row for each primary key field, or no rows if the relation
-    has no primary key.  The result row type is defined as
-
-<programlisting>
-CREATE TYPE dblink_pkey_results AS (position int, colname text);
-</programlisting>
-
-    The <literal>position</> column simply runs from 1 to <replaceable>N</>;
-    it is the number of the field within the primary key, not the number
-    within the table's columns.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-CREATE TABLE foobar (
-    f1 int,
-    f2 int,
-    f3 int,
-    PRIMARY KEY (f1, f2, f3)
-);
-CREATE TABLE
-
-SELECT * FROM dblink_get_pkey('foobar');
- position | colname
-----------+---------
-        1 | f1
-        2 | f2
-        3 | f3
-(3 rows)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-BUILD-SQL-INSERT">
-  <refmeta>
-   <refentrytitle>dblink_build_sql_insert</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_build_sql_insert</refname>
-   <refpurpose>
-    builds an INSERT statement using a local tuple, replacing the
-    primary key field values with alternative supplied values
-   </refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_build_sql_insert(text relname,
-                        int2vector primary_key_attnums,
-                        integer num_primary_key_atts,
-                        text[] src_pk_att_vals_array,
-                        text[] tgt_pk_att_vals_array) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_build_sql_insert</> can be useful in doing selective
-    replication of a local table to a remote database.  It selects a row
-    from the local table based on primary key, and then builds a SQL
-    <command>INSERT</> command that will duplicate that row, but with
-    the primary key values replaced by the values in the last argument.
-    (To make an exact copy of the row, just specify the same values for
-    the last two arguments.)
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>relname</parameter></term>
-     <listitem>
-      <para>
-       Name of a local relation, for example <literal>foo</> or
-       <literal>myschema.mytab</>.  Include double quotes if the
-       name is mixed-case or contains special characters, for
-       example <literal>"FooBar"</>; without quotes, the string
-       will be folded to lower case.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>primary_key_attnums</parameter></term>
-     <listitem>
-      <para>
-       Attribute numbers (1-based) of the primary key fields,
-       for example <literal>1 2</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>num_primary_key_atts</parameter></term>
-     <listitem>
-      <para>
-       The number of primary key fields.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>src_pk_att_vals_array</parameter></term>
-     <listitem>
-      <para>
-       Values of the primary key fields to be used to look up the
-       local tuple.  Each field is represented in text form.
-       An error is thrown if there is no local row with these
-       primary key values.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>tgt_pk_att_vals_array</parameter></term>
-     <listitem>
-      <para>
-       Values of the primary key fields to be placed in the resulting
-       <command>INSERT</> command.  Each field is represented in text form.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>Returns the requested SQL statement as text.</para>
-  </refsect1>
-
-  <refsect1>
-   <title>Notes</title>
-&pgonly;
-
-   <para>
-    As of <productname>PostgreSQL</> 9.0, the attribute numbers in
-    <parameter>primary_key_attnums</parameter> are interpreted as logical
-    column numbers, corresponding to the column's position in
-    <literal>SELECT * FROM relname</>.  Previous versions interpreted the
-    numbers as physical column positions.  There is a difference if any
-    column(s) to the left of the indicated column have been dropped during
-    the lifetime of the table.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-SELECT dblink_build_sql_insert('foo', '1 2', 2, '{"1", "a"}', '{"1", "b''a"}');
-             dblink_build_sql_insert
---------------------------------------------------
- INSERT INTO foo(f1,f2,f3) VALUES('1','b''a','1')
-(1 row)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-BUILD-SQL-DELETE">
-  <refmeta>
-   <refentrytitle>dblink_build_sql_delete</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_build_sql_delete</refname>
-   <refpurpose>builds a DELETE statement using supplied values for primary
-    key field values
-   </refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_build_sql_delete(text relname,
-                        int2vector primary_key_attnums,
-                        integer num_primary_key_atts,
-                        text[] tgt_pk_att_vals_array) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_build_sql_delete</> can be useful in doing selective
-    replication of a local table to a remote database.  It builds a SQL
-    <command>DELETE</> command that will delete the row with the given
-    primary key values.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>relname</parameter></term>
-     <listitem>
-      <para>
-       Name of a local relation, for example <literal>foo</> or
-       <literal>myschema.mytab</>.  Include double quotes if the
-       name is mixed-case or contains special characters, for
-       example <literal>"FooBar"</>; without quotes, the string
-       will be folded to lower case.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>primary_key_attnums</parameter></term>
-     <listitem>
-      <para>
-       Attribute numbers (1-based) of the primary key fields,
-       for example <literal>1 2</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>num_primary_key_atts</parameter></term>
-     <listitem>
-      <para>
-       The number of primary key fields.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>tgt_pk_att_vals_array</parameter></term>
-     <listitem>
-      <para>
-       Values of the primary key fields to be used in the resulting
-       <command>DELETE</> command.  Each field is represented in text form.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>Returns the requested SQL statement as text.</para>
-  </refsect1>
-
-  <refsect1>
-   <title>Notes</title>
-
-   <para>
-    As of <productname>PostgreSQL</> 9.0, the attribute numbers in
-    <parameter>primary_key_attnums</parameter> are interpreted as logical
-    column numbers, corresponding to the column's position in
-    <literal>SELECT * FROM relname</>.  Previous versions interpreted the
-    numbers as physical column positions.  There is a difference if any
-    column(s) to the left of the indicated column have been dropped during
-    the lifetime of the table.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-SELECT dblink_build_sql_delete('"MyFoo"', '1 2', 2, '{"1", "b"}');
-           dblink_build_sql_delete
----------------------------------------------
- DELETE FROM "MyFoo" WHERE f1='1' AND f2='b'
-(1 row)
-</screen>
-  </refsect1>
- </refentry>
-
- <refentry id="CONTRIB-DBLINK-BUILD-SQL-UPDATE">
-  <refmeta>
-   <refentrytitle>dblink_build_sql_update</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>dblink_build_sql_update</refname>
-   <refpurpose>builds an UPDATE statement using a local tuple, replacing
-    the primary key field values with alternative supplied values
-   </refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-<synopsis>
-dblink_build_sql_update(text relname,
-                        int2vector primary_key_attnums,
-                        integer num_primary_key_atts,
-                        text[] src_pk_att_vals_array,
-                        text[] tgt_pk_att_vals_array) returns text
-</synopsis>
-  </refsynopsisdiv>
-
-  <refsect1>
-   <title>Description</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    <function>dblink_build_sql_update</> can be useful in doing selective
-    replication of a local table to a remote database.  It selects a row
-    from the local table based on primary key, and then builds a SQL
-    <command>UPDATE</> command that will duplicate that row, but with
-    the primary key values replaced by the values in the last argument.
-    (To make an exact copy of the row, just specify the same values for
-    the last two arguments.)  The <command>UPDATE</> command always assigns
-    all fields of the row &mdash; the main difference between this and
-    <function>dblink_build_sql_insert</> is that it's assumed that
-    the target row already exists in the remote table.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Arguments</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-
-&pgonly;
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>relname</parameter></term>
-     <listitem>
-      <para>
-       Name of a local relation, for example <literal>foo</> or
-       <literal>myschema.mytab</>.  Include double quotes if the
-       name is mixed-case or contains special characters, for
-       example <literal>"FooBar"</>; without quotes, the string
-       will be folded to lower case.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>primary_key_attnums</parameter></term>
-     <listitem>
-      <para>
-       Attribute numbers (1-based) of the primary key fields,
-       for example <literal>1 2</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>num_primary_key_atts</parameter></term>
-     <listitem>
-      <para>
-       The number of primary key fields.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>src_pk_att_vals_array</parameter></term>
-     <listitem>
-      <para>
-       Values of the primary key fields to be used to look up the
-       local tuple.  Each field is represented in text form.
-       An error is thrown if there is no local row with these
-       primary key values.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>tgt_pk_att_vals_array</parameter></term>
-     <listitem>
-      <para>
-       Values of the primary key fields to be placed in the resulting
-       <command>UPDATE</> command.  Each field is represented in text form.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-   <title>Return Value</title>
-&pgonly;
-
-   <para>Returns the requested SQL statement as text.</para>
-  </refsect1>
-
-  <refsect1>
-   <title>Notes</title>
-<!## XC>
-&xconly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XC</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XC</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>dblink</> module has not been tested
-  with <productname>Postges-XL</> yet.  Although there're no reason
-  that <filename>dblink</> does not run
-  in <productname>Postgres-XL</>, the development team leaves the test
-  and the use of this module entirely to users.
- </para>
- <para>
-  This section is identical to the
-  corresponding <productname>PostgreSQL</> reference manual.
- </para>
-<!## end>
-&pgonly;
-
-   <para>
-    As of <productname>PostgreSQL</> 9.0, the attribute numbers in
-    <parameter>primary_key_attnums</parameter> are interpreted as logical
-    column numbers, corresponding to the column's position in
-    <literal>SELECT * FROM relname</>.  Previous versions interpreted the
-    numbers as physical column positions.  There is a difference if any
-    column(s) to the left of the indicated column have been dropped during
-    the lifetime of the table.
-   </para>
-  </refsect1>
-
-  <refsect1>
-   <title>Example</title>
-&pgonly;
-
-<screen>
-SELECT dblink_build_sql_update('foo', '1 2', 2, '{"1", "a"}', '{"1", "b"}');
-                   dblink_build_sql_update
--------------------------------------------------------------
- UPDATE foo SET f1='1',f2='b',f3='1' WHERE f1='1' AND f2='b'
-(1 row)
-</screen>
-  </refsect1>
- </refentry>
-
-</sect1>
diff --git a/doc-xc/src/sgml/ddl.sgmlin b/doc-xc/src/sgml/ddl.sgmlin
deleted file mode 100644
index f30f53915e..0000000000
--- a/doc-xc/src/sgml/ddl.sgmlin
+++ /dev/null
@@ -1,3837 +0,0 @@
-<!-- doc/src/sgml/ddl.sgml -->
-
-<chapter id="ddl">
- <title>Data Definition</title>
-&common;
-
- <para>
-  This chapter covers how one creates the database structures that
-  will hold one's data.  In a relational database, the raw data is
-  stored in tables, so the majority of this chapter is devoted to
-  explaining how tables are created and modified and what features are
-  available to control what data is stored in the tables.
-  Subsequently, we discuss how tables can be organized into
-  schemas, and how privileges can be assigned to tables.  Finally,
-  we will briefly look at other features that affect the data storage,
-  such as inheritance, views, functions, and triggers.
- </para>
-
- <sect1 id="ddl-basics">
-  <title>Table Basics</title>
-
-  <indexterm zone="ddl-basics">
-   <primary>table</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>row</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>column</primary>
-  </indexterm>
-&common;
-
-  <para>
-   A table in a relational database is much like a table on paper: It
-   consists of rows and columns.  The number and order of the columns
-   is fixed, and each column has a name.  The number of rows is
-   variable &mdash; it reflects how much data is stored at a given moment.
-   SQL does not make any guarantees about the order of the rows in a
-   table.  When a table is read, the rows will appear in an unspecified order,
-   unless sorting is explicitly requested.  This is covered in <xref
-   linkend="queries">.  Furthermore, SQL does not assign unique
-   identifiers to rows, so it is possible to have several completely
-   identical rows in a table.  This is a consequence of the
-   mathematical model that underlies SQL but is usually not desirable.
-   Later in this chapter we will see how to deal with this issue.
-  </para>
-
-  <para>
-   Each column has a data type.  The data type constrains the set of
-   possible values that can be assigned to a column and assigns
-   semantics to the data stored in the column so that it can be used
-   for computations.  For instance, a column declared to be of a
-   numerical type will not accept arbitrary text strings, and the data
-   stored in such a column can be used for mathematical computations.
-   By contrast, a column declared to be of a character string type
-   will accept almost any kind of data but it does not lend itself to
-   mathematical calculations, although other operations such as string
-   concatenation are available.
-  </para>
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> includes a sizable set of
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> includes a sizable set of
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> includes a sizable set of
-<!## end>
-   built-in data types that fit many applications.  Users can also
-   define their own data types.  Most built-in data types have obvious
-   names and semantics, so we defer a detailed explanation to <xref
-   linkend="datatype">.  Some of the frequently used data types are
-   <type>integer</type> for whole numbers, <type>numeric</type> for
-   possibly fractional numbers, <type>text</type> for character
-   strings, <type>date</type> for dates, <type>time</type> for
-   time-of-day values, and <type>timestamp</type> for values
-   containing both date and time.
-  </para>
-
-  <indexterm>
-   <primary>table</primary>
-   <secondary>creating</secondary>
-  </indexterm>
-
-  <para>
-   To create a table, you use the aptly named <xref
-   linkend="sql-createtable"> command.
-   In this command you specify at least a name for the new table, the
-   names of the columns and the data type of each column.  For
-   example:
-<programlisting>
-CREATE TABLE my_first_table (
-    first_column text,
-    second_column integer
-);
-</programlisting>
-   This creates a table named <literal>my_first_table</literal> with
-   two columns.  The first column is named
-   <literal>first_column</literal> and has a data type of
-   <type>text</type>; the second column has the name
-   <literal>second_column</literal> and the type <type>integer</type>.
-   The table and column names follow the identifier syntax explained
-   in <xref linkend="sql-syntax-identifiers">.  The type names are
-   usually also identifiers, but there are some exceptions.  Note that the
-   column list is comma-separated and surrounded by parentheses.
-  </para>
-
-  <para>
-   Of course, the previous example was heavily contrived.  Normally,
-   you would give names to your tables and columns that convey what
-   kind of data they store.  So let's look at a more realistic
-   example:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric
-);
-</programlisting>
-   (The <type>numeric</type> type can store fractional components, as
-   would be typical of monetary amounts.)
-  </para>
-
-  <tip>
-   <para>
-    When you create many interrelated tables it is wise to choose a
-    consistent naming pattern for the tables and columns.  For
-    instance, there is a choice of using singular or plural nouns for
-    table names, both of which are favored by some theorist or other.
-   </para>
-  </tip>
-
-  <para>
-   There is a limit on how many columns a table can contain.
-   Depending on the column types, it is between 250 and 1600.
-   However, defining a table with anywhere near this many columns is
-   highly unusual and often a questionable design.
-  </para>
-
-<!## XC>
-  <indexterm>
-   <primary>table</primary>
-  </indexterm>
-  <indexterm>
-   <primary>table</primary>
-   <secondary>replication</secondary>
-  </indexterm>
-
-&xconly;
-
-  <para>
-   In <productname>Postgres-XC</>, each table can be distributed or replicated
-   among Datanodes.  By distributing tables, each query, if the target is
-   determined from the incoming statement, can be handled by single or small
-   number of Datanodes and more transactions can be handled in parallel.
-   If you replicate tables, and if they're more read than written, transactions
-   reading such tables can be handled in parallel.
-  </para>
-
-  <para>
-   When you distribute a table, you can choose almost any column of a fundamental data type as distribution
-   column.
-   For details, please refer to <xref linkend="SQL-CREATETABLE">.
-   Datanode for specific row is determined based upon the value of the distribution
-   column.
-    By default, distribution column is the first column you specified in
-   <type>CREATE TABLE</type> statement and the column value is used to
-   generate hash value as an index for Datanode which accommodate the
-   row.
-   You can choose another distribution method such as <type>MODULO</> and
-   <type>ROUNDROBIN</>.
-   To specify what column to choose as the distribution column and what value test to
-   choose, you can do as follows:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric
-) DISTRIBUTE BY HASH(product_no);
-</programlisting>
-   In this case, the column <type>product_no</> is chosen as the distribute column and
-   the target Datanode of each row is determined based upon the hash value of the column.
-   You can use <type>MODULO</> to specify modulo to test and determine the target Datanode.
-   You can also specify <type>ROUNDROBIN</> to determine the Datanode by the order each
-   row is inserted.
-  </para>
-
-  <para>
-   Please note that with <type>HASH</> and <type>MODULO</>, Coordinator have a chance to determine the
-   location of target row from incoming statement.   This reduces the number of involved Datanodes
-   and can increase the number of transaction handled in parallel.
-  </para>
-
-  <para>
-   On the other hand, if exact value cannot be obtained from incoming statement, for example,
-   in the case of floating point number, <productname>Postgres-XC</> may fail to find precise
-   target Datanode and it is not recommended to use such column as a distribution column.
-  </para>
-
-  <para>
-   To replicate a table into all the Datanodes, specify <type>DISTRIBUTE BY REPLICATION</> as
-   follows:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric
-) DISTRIBUTE BY REPLICATION;
-</programlisting>
-
-  </para>
-<!## end>
-<!## XL>
-  <indexterm>
-   <primary>table</primary>
-  </indexterm>
-  <indexterm>
-   <primary>table</primary>
-   <secondary>replication</secondary>
-  </indexterm>
-
-&xlonly;
-
-  <para>
-   In <productname>Postgres-XL</>, each table can be distributed or replicated
-   among Datanodes.  By distributing tables each query
-   has the potential to be handled by a single or small
-   subset of the Datanodes and more transactions can be handled in parallel.
-   If you replicate tables, they can be read from just a single location, though
-   all writes will need to take place on all nodes.
-  </para>
-
-  <para>
-   When you distribute a table, you can choose almost any column of a fundamental data type as distribution
-   column.
-   For details, please refer to <xref linkend="SQL-CREATETABLE">.
-   The Datanode for a particular row is determined based upon the value of the distribution
-   column, chosen if DISTRIBUTE BY HASH was used.
-   If not used, the first column of a primary key or unique constraint is used
-   if present in the CREATE TABLE clause.
-   If neither of those are present, the first column of a foreign key constraint 
-   is used, the idea being that child data can be col-located on the same node
-   as the parent table.
-   If no such constraint is defined, Postgres-XL will choose the first reasonable
-   column it can find, that is the first column that has a deterministically 
-   distributable data type.
-
-   You may also choose another distribution method such as <type>MODULO</> and
-   <type>ROUNDROBIN</>.
-   To specify what column to choose as the distribution column and what value test to
-   choose, you can do as follows:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric
-) DISTRIBUTE BY HASH(product_no);
-</programlisting>
-   In this case, the column <type>product_no</> is chosen as the distribute column and
-   the target Datanode of each row is determined based upon the hash value of the column.
-   You can use <type>MODULO</> to specify modulo to test and determine the target Datanode.
-   You can also specify <type>ROUNDROBIN</> to determine the Datanode by the order each
-   row is inserted.
-  </para>
-
-  <para>
-   Please note that with <type>HASH</> and <type>MODULO</>, the Coordinator may be able to determine the
-   exact location of target row from incoming statement.   This reduces the number of involved Datanodes
-   and can increase the number of transaction handled in parallel.
-  </para>
-
-  <para>
-   On the other hand, if exact location cannot be obtained from incoming statement, the
-   Coordinator will have to involve all of the Datanodes on which the involved table 
-   is distributed.
-  </para>
-
-  <para>
-   To replicate a table into all the Datanodes, specify <type>DISTRIBUTE BY REPLICATION</> as
-   follows:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric
-) DISTRIBUTE BY REPLICATION;
-</programlisting>
-
-  </para>
-<!## end>
-
-  <indexterm>
-   <primary>table</primary>
-   <secondary>removing</secondary>
-  </indexterm>
-
-&common;
-  <para>
-   If you no longer need a table, you can remove it using the <xref
-   linkend="sql-droptable"> command.
-   For example:
-<programlisting>
-DROP TABLE my_first_table;
-DROP TABLE products;
-</programlisting>
-   Attempting to drop a table that does not exist is an error.
-   Nevertheless, it is common in SQL script files to unconditionally
-   try to drop each table before creating it, ignoring any error
-   messages, so that the script works whether or not the table exists.
-   (If you like, you can use the <literal>DROP TABLE IF EXISTS</> variant
-   to avoid the error messages, but this is not standard SQL.)
-  </para>
-
-  <para>
-   If you need to modify a table that already exists, see <xref
-   linkend="ddl-alter"> later in this chapter.
-  </para>
-
-  <para>
-   With the tools discussed so far you can create fully functional
-   tables.  The remainder of this chapter is concerned with adding
-   features to the table definition to ensure data integrity,
-   security, or convenience.  If you are eager to fill your tables with
-   data now you can skip ahead to <xref linkend="dml"> and read the
-   rest of this chapter later.
-  </para>
- </sect1>
-
- <sect1 id="ddl-default">
-  <title>Default Values</title>
-
-  <indexterm zone="ddl-default">
-   <primary>default value</primary>
-  </indexterm>
-&common;
-
-  <para>
-   A column can be assigned a default value.  When a new row is
-   created and no values are specified for some of the columns, those
-   columns will be filled with their respective default values.  A
-   data manipulation command can also request explicitly that a column
-   be set to its default value, without having to know what that value is.
-   (Details about data manipulation commands are in <xref linkend="dml">.)
-  </para>
-
-  <para>
-   <indexterm><primary>null value</primary><secondary>default value</secondary></indexterm>
-   If no default value is declared explicitly, the default value is the
-   null value.  This usually makes sense because a null value can
-   be considered to represent unknown data.
-  </para>
-
-  <para>
-   In a table definition, default values are listed after the column
-   data type.  For example:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric <emphasis>DEFAULT 9.99</emphasis>
-);
-</programlisting>
-  </para>
-
-  <para>
-
-   The default value can be an expression, which will be
-   evaluated whenever the default value is inserted
-   (<emphasis>not</emphasis> when the table is created).  A common example
-   is for a <type>timestamp</type> column to have a default of <literal>CURRENT_TIMESTAMP</>,
-   so that it gets set to the time of row insertion.  Another common
-   example is generating a <quote>serial number</> for each row.
-   In <productname>PostgreSQL</productname> this is typically done by
-   something like:
-<programlisting>
-CREATE TABLE products (
-    product_no integer <emphasis>DEFAULT nextval('products_product_no_seq')</emphasis>,
-    ...
-);
-</programlisting>
-   where the <literal>nextval()</> function supplies successive values
-   from a <firstterm>sequence object</> (see <xref
-   linkend="functions-sequence">). This arrangement is sufficiently common
-   that there's a special shorthand for it:
-<programlisting>
-CREATE TABLE products (
-    product_no <emphasis>SERIAL</emphasis>,
-    ...
-);
-</programlisting>
-   The <literal>SERIAL</> shorthand is discussed further in <xref
-   linkend="datatype-serial">.
-  </para>
- </sect1>
-
- <sect1 id="ddl-constraints">
-  <title>Constraints</title>
-
-  <indexterm zone="ddl-constraints">
-   <primary>constraint</primary>
-  </indexterm>
-&common;
-
-  <para>
-   Data types are a way to limit the kind of data that can be stored
-   in a table.  For many applications, however, the constraint they
-   provide is too coarse.  For example, a column containing a product
-   price should probably only accept positive values.  But there is no
-   standard data type that accepts only positive numbers.  Another issue is
-   that you might want to constrain column data with respect to other
-   columns or rows.  For example, in a table containing product
-   information, there should be only one row for each product number.
-  </para>
-
-  <para>
-   To that end, SQL allows you to define constraints on columns and
-   tables.  Constraints give you as much control over the data in your
-   tables as you wish.  If a user attempts to store data in a column
-   that would violate a constraint, an error is raised.  This applies
-   even if the value came from the default value definition.
-  </para>
-
-  <sect2>
-   <title>Check Constraints</title>
-
-   <indexterm>
-    <primary>check constraint</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>constraint</primary>
-    <secondary>check</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    A check constraint is the most generic constraint type.  It allows
-    you to specify that the value in a certain column must satisfy a
-    Boolean (truth-value) expression.  For instance, to require positive
-    product prices, you could use:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric <emphasis>CHECK (price &gt; 0)</emphasis>
-);
-</programlisting>
-   </para>
-
-   <para>
-    As you see, the constraint definition comes after the data type,
-    just like default value definitions.  Default values and
-    constraints can be listed in any order.  A check constraint
-    consists of the key word <literal>CHECK</literal> followed by an
-    expression in parentheses.  The check constraint expression should
-    involve the column thus constrained, otherwise the constraint
-    would not make too much sense.
-   </para>
-
-   <indexterm>
-    <primary>constraint</primary>
-    <secondary>name</secondary>
-   </indexterm>
-&common;
-   <para>
-    You can also give the constraint a separate name.  This clarifies
-    error messages and allows you to refer to the constraint when you
-    need to change it.  The syntax is:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric <emphasis>CONSTRAINT positive_price</emphasis> CHECK (price &gt; 0)
-);
-</programlisting>
-    So, to specify a named constraint, use the key word
-    <literal>CONSTRAINT</literal> followed by an identifier followed
-    by the constraint definition.  (If you don't specify a constraint
-    name in this way, the system chooses a name for you.)
-   </para>
-
-   <para>
-    A check constraint can also refer to several columns.  Say you
-    store a regular price and a discounted price, and you want to
-    ensure that the discounted price is lower than the regular price:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric CHECK (price &gt; 0),
-    discounted_price numeric CHECK (discounted_price &gt; 0),
-    <emphasis>CHECK (price &gt; discounted_price)</emphasis>
-);
-</programlisting>
-   </para>
-
-   <para>
-    The first two constraints should look familiar.  The third one
-    uses a new syntax.  It is not attached to a particular column,
-    instead it appears as a separate item in the comma-separated
-    column list.  Column definitions and these constraint
-    definitions can be listed in mixed order.
-   </para>
-
-   <para>
-    We say that the first two constraints are column constraints, whereas the
-    third one is a table constraint because it is written separately
-    from any one column definition.  Column constraints can also be
-    written as table constraints, while the reverse is not necessarily
-    possible, since a column constraint is supposed to refer to only the
-    column it is attached to.  (<productname>PostgreSQL</productname> doesn't
-    enforce that rule, but you should follow it if you want your table
-    definitions to work with other database systems.)  The above example could
-    also be written as:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric,
-    CHECK (price &gt; 0),
-    discounted_price numeric,
-    CHECK (discounted_price &gt; 0),
-    CHECK (price &gt; discounted_price)
-);
-</programlisting>
-    or even:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric CHECK (price &gt; 0),
-    discounted_price numeric,
-    CHECK (discounted_price &gt; 0 AND price &gt; discounted_price)
-);
-</programlisting>
-    It's a matter of taste.
-   </para>
-
-   <para>
-    Names can be assigned to table constraints in the same way as
-    column constraints:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric,
-    CHECK (price &gt; 0),
-    discounted_price numeric,
-    CHECK (discounted_price &gt; 0),
-    <emphasis>CONSTRAINT valid_discount</> CHECK (price &gt; discounted_price)
-);
-</programlisting>
-   </para>
-
-   <indexterm>
-    <primary>null value</primary>
-    <secondary sortas="check constraints">with check constraints</secondary>
-   </indexterm>
-&common;
-   <para>
-    It should be noted that a check constraint is satisfied if the
-    check expression evaluates to true or the null value.  Since most
-    expressions will evaluate to the null value if any operand is null,
-    they will not prevent null values in the constrained columns.  To
-    ensure that a column does not contain null values, the not-null
-    constraint described in the next section can be used.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Not-Null Constraints</title>
-
-   <indexterm>
-    <primary>not-null constraint</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>constraint</primary>
-    <secondary>NOT NULL</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    A not-null constraint simply specifies that a column must not
-    assume the null value.  A syntax example:
-<programlisting>
-CREATE TABLE products (
-    product_no integer <emphasis>NOT NULL</emphasis>,
-    name text <emphasis>NOT NULL</emphasis>,
-    price numeric
-);
-</programlisting>
-   </para>
-
-   <para>
-    A not-null constraint is always written as a column constraint.  A
-    not-null constraint is functionally equivalent to creating a check
-    constraint <literal>CHECK (<replaceable>column_name</replaceable>
-    IS NOT NULL)</literal>, but in
-    <productname>PostgreSQL</productname> creating an explicit
-    not-null constraint is more efficient.  The drawback is that you
-    cannot give explicit names to not-null constraints created this
-    way.
-   </para>
-
-   <para>
-    Of course, a column can have more than one constraint.  Just write
-    the constraints one after another:
-<programlisting>
-CREATE TABLE products (
-    product_no integer NOT NULL,
-    name text NOT NULL,
-    price numeric NOT NULL CHECK (price &gt; 0)
-);
-</programlisting>
-    The order doesn't matter.  It does not necessarily determine in which
-    order the constraints are checked.
-   </para>
-
-   <para>
-    The <literal>NOT NULL</literal> constraint has an inverse: the
-    <literal>NULL</literal> constraint.  This does not mean that the
-    column must be null, which would surely be useless.  Instead, this
-    simply selects the default behavior that the column might be null.
-    The <literal>NULL</literal> constraint is not present in the SQL
-    standard and should not be used in portable applications.  (It was
-    only added to <productname>PostgreSQL</productname> to be
-    compatible with some other database systems.)  Some users, however,
-    like it because it makes it easy to toggle the constraint in a
-    script file.  For example, you could start with:
-<programlisting>
-CREATE TABLE products (
-    product_no integer NULL,
-    name text NULL,
-    price numeric NULL
-);
-</programlisting>
-    and then insert the <literal>NOT</literal> key word where desired.
-   </para>
-
-   <tip>
-    <para>
-     In most database designs the majority of columns should be marked
-     not null.
-    </para>
-   </tip>
-  </sect2>
-
-  <sect2>
-   <title>Unique Constraints</title>
-
-   <indexterm>
-    <primary>unique constraint</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>constraint</primary>
-    <secondary>unique</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    Unique constraints ensure that the data contained in a column or a
-    group of columns is unique with respect to all the rows in the
-    table.  The syntax is:
-<programlisting>
-CREATE TABLE products (
-    product_no integer <emphasis>UNIQUE</emphasis>,
-    name text,
-    price numeric
-);
-</programlisting>
-    when written as a column constraint, and:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric,
-    <emphasis>UNIQUE (product_no)</emphasis>
-);
-</programlisting>
-    when written as a table constraint.
-   </para>
-
-   <para>
-    If a unique constraint refers to a group of columns, the columns
-    are listed separated by commas:
-<programlisting>
-CREATE TABLE example (
-    a integer,
-    b integer,
-    c integer,
-    <emphasis>UNIQUE (a, c)</emphasis>
-);
-</programlisting>
-    This specifies that the combination of values in the indicated columns
-    is unique across the whole table, though any one of the columns
-    need not be (and ordinarily isn't) unique.
-   </para>
-
-   <para>
-    You can assign your own name for a unique constraint, in the usual way:
-<programlisting>
-CREATE TABLE products (
-    product_no integer <emphasis>CONSTRAINT must_be_different</emphasis> UNIQUE,
-    name text,
-    price numeric
-);
-</programlisting>
-   </para>
-
-   <para>
-    Adding a unique constraint will automatically create a unique tree
-    index on the column or group of columns used in the constraint.
-   </para>
-
-   <indexterm>
-    <primary>null value</primary>
-    <secondary sortas="unique constraints">with unique constraints</secondary>
-   </indexterm>
-
-   <para>
-    In general, a unique constraint is violated when there is more than
-    one row in the table where the values of all of the
-    columns included in the constraint are equal.
-    However, two null values are not considered equal in this
-    comparison.  That means even in the presence of a
-    unique constraint it is possible to store duplicate
-    rows that contain a null value in at least one of the constrained
-    columns.  This behavior conforms to the SQL standard, but we have
-    heard that other SQL databases might not follow this rule.  So be
-    careful when developing applications that are intended to be
-    portable.
-   </para>
-
-<!## XC>
-&xconly;
-   <para>
-    In <productname>Postgres-XC</>, in distributed
-    tables, <literal>UNIQUE</literal> constraints must include the
-    distribution column of the table. If the table is distributed
-    by <type>ROUNDROBIN</type>, you cannot enforce <type>UNIQUE</>
-    constraint because it does not have a distribution column.
-    There's no restriction in <type>UNIQUE</> constraint in replicated
-    tables. When an expression is used on a <type>UNIQUE</> constraint,
-    this expression must contain the distribution column of its parent
-    table. It cannot use other columns as well.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    In <productname>Postgres-XL</>, in distributed
-    tables, <literal>UNIQUE</literal> constraints must include the
-    distribution column of the table. 
-    This is because Postgres-XL currently only allows that it can
-    push down to the Datanodes to be enforced locally. If we include
-    the distribution column in unique constraints, it stands to
-    reason that it can be enforced locally.
-
-    If a table is distributed
-    by <type>ROUNDROBIN</type>, we cannot enforce <type>UNIQUE</>
-    constraints because it does not have a distribution column;
-    it is possible that the same value for a column exists on
-    multiple nodes.
-
-    There's no restriction in <type>UNIQUE</> constraint in replicated
-    tables. When an expression is used on a <type>UNIQUE</> constraint,
-    this expression must contain the distribution column of its parent
-    table. It cannot use other columns as well.
-   </para>
-<!## end>
-  </sect2>
-
-  <sect2>
-   <title>Primary Keys</title>
-
-   <indexterm>
-    <primary>primary key</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>constraint</primary>
-    <secondary>primary key</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    Technically, a primary key constraint is simply a combination of a
-    unique constraint and a not-null constraint.  So, the following
-    two table definitions accept the same data:
-<programlisting>
-CREATE TABLE products (
-    product_no integer UNIQUE NOT NULL,
-    name text,
-    price numeric
-);
-</programlisting>
-
-<programlisting>
-CREATE TABLE products (
-    product_no integer <emphasis>PRIMARY KEY</emphasis>,
-    name text,
-    price numeric
-);
-</programlisting>
-   </para>
-
-   <para>
-    Primary keys can also constrain more than one column; the syntax
-    is similar to unique constraints:
-<programlisting>
-CREATE TABLE example (
-    a integer,
-    b integer,
-    c integer,
-    <emphasis>PRIMARY KEY (a, c)</emphasis>
-);
-</programlisting>
-   </para>
-
-   <para>
-    A primary key indicates that a column or group of columns can be
-    used as a unique identifier for rows in the table.  (This is a
-    direct consequence of the definition of a primary key.  Note that
-    a unique constraint does not, by itself, provide a unique identifier
-    because it does not exclude null values.)  This is useful both for
-    documentation purposes and for client applications.  For example,
-    a GUI application that allows modifying row values probably needs
-    to know the primary key of a table to be able to identify rows
-    uniquely.
-   </para>
-
-   <para>
-    Adding a primary key will automatically create a unique btree index
-    on the column or group of columns used in the primary key.
-   </para>
-
-   <para>
-    A table can have at most one primary key.  (There can be any number
-    of unique and not-null constraints, which are functionally the same
-    thing, but only one can be identified as the primary key.)
-    Relational database theory
-    dictates that every table must have a primary key.  This rule is
-    not enforced by <productname>PostgreSQL</productname>, but it is
-    usually best to follow it.
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    As mentioned in <type>UNIQUE</> constraint, distribution column
-    must be included in <type>PRIMARY KEY</type>.  Other restrictions
-    apply to <type>PRIMARY KEY</> too.  When an expression is used on
-    a <type>PRIMARY KEY</> constraint, this expression must contain
-    the distribution column of its parent table. It cannot use other
-    columns as well.
-   </para>
-<!## end>
-<!## XL>
-   <para>
-    As mentioned when discussing <type>UNIQUE</> constraint, the distribution column
-    must be included in <type>PRIMARY KEY</type>.  Other restrictions
-    apply to the <type>PRIMARY KEY</> as well.  When an expression is used on
-    a <type>PRIMARY KEY</> constraint, this expression must contain
-    the distribution column of its parent table. It cannot use other
-    columns as well.
-   </para>
-<!## end>
-  </sect2>
-
-  <sect2 id="ddl-constraints-fk">
-   <title>Foreign Keys</title>
-
-   <indexterm>
-    <primary>foreign key</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>constraint</primary>
-    <secondary>foreign key</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>referential integrity</primary>
-   </indexterm>
-&common;
-
-   <para>
-    A foreign key constraint specifies that the values in a column (or
-    a group of columns) must match the values appearing in some row
-    of another table.
-    We say this maintains the <firstterm>referential
-    integrity</firstterm> between two related tables.
-   </para>
-
-   <para>
-    Say you have the product table that we have used several times already:
-<programlisting>
-CREATE TABLE products (
-    product_no integer PRIMARY KEY,
-    name text,
-    price numeric
-);
-</programlisting>
-<!## PG>
-<!-- NOTICE
-     XC has a restriction to define reference integrity.
--->
-    Let's also assume you have a table storing orders of those
-    products.  We want to ensure that the orders table only contains
-    orders of products that actually exist.  So we define a foreign
-    key constraint in the orders table that references the products
-    table:
-<programlisting>
-CREATE TABLE orders (
-    order_id integer PRIMARY KEY,
-    product_no integer <emphasis>REFERENCES products (product_no)</emphasis>,
-    quantity integer
-);
-</programlisting>
-<!## end>
-<!## XC>
-&xconly
-
-    Let's also assume you have a table storing orders of those
-    products.  We want to ensure that the orders table only contains
-    orders of products that actually exist.  So we define a foreign
-    key constraint in the orders table that references the products
-    table.
-<programlisting>
-CREATE TABLE orders (
-    order_id integer,
-    product_no integer <emphasis>REFERENCES products (product_no)</emphasis>,
-    quantity integer
-) DISTRIBUTE BY HASH(product_no);
-</programlisting>
-   </para>
-&xconly;
-   <para>
-    Please note that column with <type>REFERENCE</> must be the distribution column.
-    In this case, we cannot add <type>PRIMARY KEY</> to <type>order_id</>
-    because <type>PRIMARY KEY</type> must be the distribution column as well.
-    This limitation is introduced because constraints are enforced only locally in each Datanode,
-    which will be resolved in the future.
-   </para>
-   <para>
-<!## end>
-<!## XL>
-&xlonly
-
-    Let's also assume you have a table storing orders of those
-    products.  We want to ensure that the orders table only contains
-    orders of products that actually exist.  So we define a foreign
-    key constraint in the orders table that references the products
-    table.
-<programlisting>
-CREATE TABLE orders (
-    order_id integer,
-    product_no integer <emphasis>REFERENCES products (product_no)</emphasis>,
-    quantity integer
-) DISTRIBUTE BY HASH(product_no);
-</programlisting>
-   </para>
-&xlonly;
-   <para>
-    Please note that column with <type>REFERENCES</> should be the distribution column.
-    In this case, we cannot add <type>PRIMARY KEY</> to <type>order_id</>
-    because <type>PRIMARY KEY</type> must be the distribution column as well.
-    This limitation is introduced because constraints are enforced only locally in each Datanode.
-   </para>
-   <para>
-<!## end>
-&common;
-    Now it is impossible to create orders with
-    <structfield>product_no</structfield> entries that do not appear in the
-    products table.
-   </para>
-
-   <para>
-    We say that in this situation the orders table is the
-    <firstterm>referencing</firstterm> table and the products table is
-    the <firstterm>referenced</firstterm> table.  Similarly, there are
-    referencing and referenced columns.
-   </para>
-
-<!## PG>
-<!-- NOTICE:
-     In XC, we cannot commit column name in REFERENCES clause.
--->
-   <para>
-    You can also shorten the above command to:
-<programlisting>
-CREATE TABLE orders (
-    order_id integer PRIMARY KEY,
-    product_no integer <emphasis>REFERENCES products</emphasis>,
-    quantity integer
-);
-</programlisting>
-    because in absence of a column list the primary key of the
-    referenced table is used as the referenced column(s).
-   </para>
-<!## end>
-
-<!## PG>
-<!-- NOTICE:
-     In XC, we cannot specify both PRIMARY KEY and REFERENCES key
-     for different columns.
--->
-   <para>
-    A foreign key can also constrain and reference a group of columns.
-    As usual, it then needs to be written in table constraint form.
-    Here is a contrived syntax example:
-<programlisting>
-CREATE TABLE t1 (
-  a integer PRIMARY KEY,
-  b integer,
-  c integer,
-  <emphasis>FOREIGN KEY (b, c) REFERENCES other_table (c1, c2)</emphasis>
-);
-</programlisting>
-    Of course, the number and type of the constrained columns need to
-    match the number and type of the referenced columns.
-   </para>
-<!## end>
-
-   <para>
-    You can assign your own name for a foreign key constraint,
-    in the usual way.
-   </para>
-
-<!## PG>
-<!-- NOTICE:
-     XC does not allow multiple reference integrity in a table.
--->
-   <para>
-    A table can contain more than one foreign key constraint.  This is
-    used to implement many-to-many relationships between tables.  Say
-    you have tables about products and orders, but now you want to
-    allow one order to contain possibly many products (which the
-    structure above did not allow).  You could use this table structure:
-<programlisting>
-CREATE TABLE products (
-    product_no integer PRIMARY KEY,
-    name text,
-    price numeric
-);
-
-CREATE TABLE orders (
-    order_id integer PRIMARY KEY,
-    shipping_address text,
-    ...
-);
-
-CREATE TABLE order_items (
-    product_no integer REFERENCES products,
-    order_id integer REFERENCES orders,
-    quantity integer,
-    PRIMARY KEY (product_no, order_id)
-);
-</programlisting>
-    Notice that the primary key overlaps with the foreign keys in
-    the last table.
-   </para>
-<!## end>
-<!## XC>
-&xconly;
-   <para>
-    Because a column with <type>REFERENCES</> integrity needs to be
-    the distribution column, it is <productname>Postgres-XC</>'s
-    restriction that we cannot specify more than one columns
-    with <type>REFERENCES</> constraint.
-   </para>
-<!## end>
-
-   <indexterm>
-    <primary>CASCADE</primary>
-    <secondary>foreign key action</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>RESTRICT</primary>
-    <secondary>foreign key action</secondary>
-   </indexterm>
-
-<!## PG>
-<!-- NOTICE:
-     XC does not allow REFERENCES to more than one columns.
--->
-   <para>
-    We know that the foreign keys disallow creation of orders that
-    do not relate to any products.  But what if a product is removed
-    after an order is created that references it?  SQL allows you to
-    handle that as well.  Intuitively, we have a few options:
-    <itemizedlist spacing="compact">
-     <listitem><para>Disallow deleting a referenced product</para></listitem>
-     <listitem><para>Delete the orders as well</para></listitem>
-     <listitem><para>Something else?</para></listitem>
-    </itemizedlist>
-   </para>
-<!## end>
-<!## XC>
-&xconly;
-   <para>
-    We know that the foreign keys disallow creation of orders that
-    do not relate to any products.  But what if a product is removed
-    after an order is created that references it?  SQL allows you to
-    handle that as well.  Intuitively, we have a few options:
-    <itemizedlist spacing="compact">
-     <listitem><para>Disallow deleting a referenced order</para></listitem>
-     <listitem><para>Delete the order line as well</para></listitem>
-     <listitem><para>Something else?</para></listitem>
-    </itemizedlist>
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    We know that the foreign keys disallow creation of orders that
-    do not relate to any products.  But what if a product is removed
-    after an order is created that references it?  SQL allows you to
-    handle that as well.  Intuitively, we have a few options:
-    <itemizedlist spacing="compact">
-     <listitem><para>Disallow deleting a referenced order</para></listitem>
-     <listitem><para>Delete the order line as well</para></listitem>
-     <listitem><para>Something else?</para></listitem>
-    </itemizedlist>
-   </para>
-<!## end>
-&common;
-   <para>
-    To illustrate this, let's implement the following policy on the
-    many-to-many relationship example above: when someone wants to
-    remove a product that is still referenced by an order (via
-    <literal>order_items</literal>), we disallow it.  If someone
-    removes an order, the order items are removed as well:
-<!## PG>
-<programlisting>
-CREATE TABLE products (
-    product_no integer PRIMARY KEY,
-    name text,
-    price numeric
-);
-
-CREATE TABLE orders (
-    order_id integer PRIMARY KEY,
-    shipping_address text,
-    ...
-);
-
-CREATE TABLE order_items (
-    product_no integer REFERENCES products <emphasis>ON DELETE RESTRICT</emphasis>,
-    order_id integer REFERENCES orders <emphasis>ON DELETE CASCADE</emphasis>,
-    quantity integer,
-    PRIMARY KEY (product_no, order_id)
-);
-</programlisting>
-<!## end>
-<!## XC>
-<programlisting>
-CREATE TABLE products (
-    product_no integer PRIMARY KEY,
-    name text,
-    price numeric
-);
-
-CREATE TABLE orders (
-    order_id integer PRIMARY KEY,
-    shipping_address text,
-    ...
-);
-
-CREATE TABLE order_items (
-    product_no integer,
-    order_id integer REFERENCES orders <emphasis>ON DELETE CASCADE</emphasis>,
-    quantity integer,
-    PRIMARY KEY (product_no, order_id)
-) DISTRIBUTE BY HASH(order_id);
-</programlisting>
-<!## end>
-<!## XL>
-<programlisting>
-CREATE TABLE products (
-    product_no integer PRIMARY KEY,
-    name text,
-    price numeric
-);
-
-CREATE TABLE orders (
-    order_id integer PRIMARY KEY,
-    shipping_address text,
-    ...
-);
-
-CREATE TABLE order_items (
-    product_no integer,
-    order_id integer REFERENCES orders <emphasis>ON DELETE CASCADE</emphasis>,
-    quantity integer,
-    PRIMARY KEY (product_no, order_id)
-) DISTRIBUTE BY HASH(order_id);
-</programlisting>
-<!## end>
-   </para>
-
-   <para>
-    Restricting and cascading deletes are the two most common options.
-    <literal>RESTRICT</literal> prevents deletion of a
-    referenced row. <literal>NO ACTION</literal> means that if any
-    referencing rows still exist when the constraint is checked, an error
-    is raised; this is the default behavior if you do not specify anything.
-    (The essential difference between these two choices is that
-    <literal>NO ACTION</literal> allows the check to be deferred until
-    later in the transaction, whereas <literal>RESTRICT</literal> does not.)
-    <literal>CASCADE</> specifies that when a referenced row is deleted,
-    row(s) referencing it should be automatically deleted as well.
-    There are two other options:
-    <literal>SET NULL</literal> and <literal>SET DEFAULT</literal>.
-    These cause the referencing columns to be set to nulls or default
-    values, respectively, when the referenced row is deleted.
-    Note that these do not excuse you from observing any constraints.
-    For example, if an action specifies <literal>SET DEFAULT</literal>
-    but the default value would not satisfy the foreign key, the
-    operation will fail.
-   </para>
-
-   <para>
-    Analogous to <literal>ON DELETE</literal> there is also
-    <literal>ON UPDATE</literal> which is invoked when a referenced
-    column is changed (updated).  The possible actions are the same.
-   </para>
-
-   <para>
-    Since a <command>DELETE</command> of a row from the referenced table
-    or an <command>UPDATE</command> of a referenced column will require
-    a scan of the referencing table for rows matching the old value, it
-    is often a good idea to index the referencing columns.  Because this
-    is not always needed, and there are many choices available on how
-    to index, declaration of a foreign key constraint does not
-    automatically create an index on the referencing columns.
-   </para>
-
-   <para>
-    More information about updating and deleting data is in <xref
-    linkend="dml">.
-   </para>
-
-   <para>
-    Finally, we should mention that a foreign key must reference
-    columns that either are a primary key or form a unique constraint.
-    If the foreign key references a unique constraint, there are some
-    additional possibilities regarding how null values are matched.
-    These are explained in the reference documentation for
-    <xref linkend="sql-createtable">.
-   </para>
-  </sect2>
-
-<!## PG>
-<!-- NOTICE:
-     XC does not support exclusion constraints
--->
-  <sect2 id="ddl-constraints-exclusion">
-   <title>Exclusion Constraints</title>
-
-   <indexterm>
-    <primary>exclusion constraint</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>constraint</primary>
-    <secondary>exclusion</secondary>
-   </indexterm>
-
-   <para>
-    Exclusion constraints ensure that if any two rows are compared on
-    the specified columns or expressions using the specified operators,
-    at least one of these operator comparisons will return false or null.
-    The syntax is:
-<programlisting>
-CREATE TABLE circles (
-    c circle,
-    EXCLUDE USING gist (c WITH &amp;&amp;)
-);
-</programlisting>
-   </para>
-
-   <para>
-    See also <link linkend="SQL-CREATETABLE-EXCLUDE"><command>CREATE
-    TABLE ... CONSTRAINT ... EXCLUDE</></link> for details.
-   </para>
-
-   <para>
-    Adding an exclusion constraint will automatically create an index
-    of the type specified in the constraint declaration.
-   </para>
-$xc-constraint;
-  </sect2>
-<!## end>
- </sect1>
-
- <sect1 id="ddl-system-columns">
-  <title>System Columns</title>
-&common;
-  <para>
-   Every table has several <firstterm>system columns</> that are
-   implicitly defined by the system.  Therefore, these names cannot be
-   used as names of user-defined columns.  (Note that these
-   restrictions are separate from whether the name is a key word or
-   not; quoting a name will not allow you to escape these
-   restrictions.)  You do not really need to be concerned about these
-   columns; just know they exist.
-  </para>
-
-  <indexterm>
-   <primary>column</primary>
-   <secondary>system column</secondary>
-  </indexterm>
-
-  <variablelist>
-   <varlistentry>
-    <term><structfield>oid</></term>
-    <listitem>
-     <para>
-      <indexterm>
-       <primary>OID</primary>
-       <secondary>column</secondary>
-      </indexterm>
-      The object identifier (object ID) of a row. This column is only
-      present if the table was created using <literal>WITH
-      OIDS</literal>, or if the <xref linkend="guc-default-with-oids">
-      configuration variable was set at the time. This column is of type
-      <type>oid</type> (same name as the column); see <xref
-      linkend="datatype-oid"> for more information about the type.
-     </para>
-<!## XC>
-&xconly;
-     <para>
-      Please note that <productname>Postgres-XC</> does not enforce
-      OID integrity among the cluster.  OID is assigned locally in
-      each Coordinator and Datanode.  You can use this in expressions
-      but you should not expect OID value is the same throughout the
-      <productname>XC</> cluster.
-     </para>
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      Please note that <productname>Postgres-XL</> does not enforce
-      OID integrity among the cluster.  OIDs are assigned locally in
-      each Coordinator and Datanode.  You can use this in expressions
-      but you should not expect OID values are the same throughout the
-      <productname>XL</> cluster.
-     </para>
-<!## end>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><structfield>tableoid</></term>
-    <listitem>
-     <indexterm>
-      <primary>tableoid</primary>
-     </indexterm>
-
-     <para>
-      The OID of the table containing this row.  This column is
-      particularly handy for queries that select from inheritance
-      hierarchies (see <xref linkend="ddl-inherit">), since without it,
-      it's difficult to tell which individual table a row came from.  The
-      <structfield>tableoid</structfield> can be joined against the
-      <structfield>oid</structfield> column of
-      <structname>pg_class</structname> to obtain the table name.
-     </para>
-<!## XC>
-&xconly;
-     <para>
-      Please note that <productname>Postgres-XC</> does not enforce
-      OID integrity among the cluster.  OID is assigned locally in
-      each Coordinator and Datanode.  You can use this in expressions
-      but you should not expect OID value is the same throughout the
-      <productname>XC</> cluster.
-     </para>
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      Please note that <productname>Postgres-XL</> does not enforce
-      OID integrity among the cluster.  OIDs are assigned locally in
-      each Coordinator and Datanode.  You can use this in expressions,
-      but you should not expect OID values are the same throughout the
-      <productname>XL</> cluster.
-     </para>
-<!## end>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><structfield>xmin</></term>
-    <listitem>
-     <indexterm>
-      <primary>xmin</primary>
-     </indexterm>
-&common;
-     <para>
-      The identity (transaction ID) of the inserting transaction for
-      this row version.  (A row version is an individual state of a
-      row; each update of a row creates a new row version for the same
-      logical row.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><structfield>cmin</></term>
-    <listitem>
-     <indexterm>
-      <primary>cmin</primary>
-     </indexterm>
-
-     <para>
-      The command identifier (starting at zero) within the inserting
-      transaction.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><structfield>xmax</></term>
-    <listitem>
-     <indexterm>
-      <primary>xmax</primary>
-     </indexterm>
-&common;
-     <para>
-      The identity (transaction ID) of the deleting transaction, or
-      zero for an undeleted row version.  It is possible for this column to
-      be nonzero in a visible row version. That usually indicates that the
-      deleting transaction hasn't committed yet, or that an attempted
-      deletion was rolled back.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><structfield>cmax</></term>
-    <listitem>
-     <indexterm>
-      <primary>cmax</primary>
-     </indexterm>
-
-     <para>
-      The command identifier within the deleting transaction, or zero.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><structfield>ctid</></term>
-    <listitem>
-     <indexterm>
-      <primary>ctid</primary>
-     </indexterm>
-
-     <para>
-      The physical location of the row version within its table.  Note that
-      although the <structfield>ctid</structfield> can be used to
-      locate the row version very quickly, a row's
-      <structfield>ctid</structfield> will change if it is
-      updated or moved by <command>VACUUM FULL</>.  Therefore
-      <structfield>ctid</structfield> is useless as a long-term row
-      identifier.  The OID, or even better a user-defined serial
-      number, should be used to identify logical rows.
-     </para>
-<!## XC>
-&xconly;
-     <para>
-      In <productname>Postgres-XC</>, ctid is local to Coordinators
-      and Datanodes.  It is not a good practice to use this value in
-      SQL statements.  In very restricted situation, for example, when
-      you query the database specifying the target Coordinator or
-      Datanode using <type>EXECUTE DIRECT</> statement, you may use
-      this value.
-     </para>
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      In <productname>Postgres-XL</>, ctid is local to Coordinators
-      and Datanodes.  It is not good practice to use this value in
-      SQL statements and can be very dangerous when using it to update
-      data. 
-     </para>
-<!## end>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-&common;
-   <para>
-    OIDs are 32-bit quantities and are assigned from a single
-    cluster-wide counter.  In a large or long-lived database, it is
-    possible for the counter to wrap around.  Hence, it is bad
-    practice to assume that OIDs are unique, unless you take steps to
-    ensure that this is the case.  If you need to identify the rows in
-    a table, using a sequence generator is strongly recommended.
-    However, OIDs can be used as well, provided that a few additional
-    precautions are taken:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       A unique constraint should be created on the OID column of each
-       table for which the OID will be used to identify rows.  When such
-       a unique constraint (or unique index) exists, the system takes
-       care not to generate an OID matching an already-existing row.
-       (Of course, this is only possible if the table contains fewer
-       than 2<superscript>32</> (4 billion) rows, and in practice the
-       table size had better be much less than that, or performance
-       might suffer.)
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       OIDs should never be assumed to be unique across tables; use
-       the combination of <structfield>tableoid</> and row OID if you
-       need a database-wide identifier.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Of course, the tables in question must be created <literal>WITH
-       OIDS</literal>.  As of <productname>PostgreSQL</productname> 8.1,
-       <literal>WITHOUT OIDS</> is the default.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    Transaction identifiers are also 32-bit quantities.  In a
-    long-lived database it is possible for transaction IDs to wrap
-    around.  This is not a fatal problem given appropriate maintenance
-    procedures; see <xref linkend="maintenance"> for details.  It is
-    unwise, however, to depend on the uniqueness of transaction IDs
-    over the long term (more than one billion transactions).
-   </para>
-
-<!## XC>
-&xconly;
-   <para>
-      Again, <productname>Postgres-XC</> does not enforce
-      OID integrity among the cluster.  OID is assigned locally in
-      each Coordinator and Datanode.  You can use this in expressions
-      but you should not expect OID value is the same throughout the
-      <productname>XC</> cluster.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-      Again, <productname>Postgres-XL</> does not enforce
-      OID integrity among the cluster.  OIDs are assigned locally in
-      each Coordinator and Datanode.  You can use this in expressions
-      but you should not expect OIDs values to refer to the same object throughout the
-      <productname>XL</> cluster.
-   </para>
-<!## end>
-&common;
-   <para>
-    Command identifiers are also 32-bit quantities.  This creates a hard limit
-    of 2<superscript>32</> (4 billion) <acronym>SQL</acronym> commands
-    within a single transaction.  In practice this limit is not a
-    problem &mdash; note that the limit is on the number of
-    <acronym>SQL</acronym> commands, not the number of rows processed.
-    Also, as of <productname>PostgreSQL</productname> 8.3, only commands
-    that actually modify the database contents will consume a command
-    identifier.
-   </para>
- </sect1>
-
- <sect1 id="ddl-alter">
-  <title>Modifying Tables</title>
-
-  <indexterm zone="ddl-alter">
-   <primary>table</primary>
-   <secondary>modifying</secondary>
-  </indexterm>
-&common;
-  <para>
-   When you create a table and you realize that you made a mistake, or
-   the requirements of the application change, you can drop the
-   table and create it again.  But this is not a convenient option if
-   the table is already filled with data, or if the table is
-   referenced by other database objects (for instance a foreign key
-   constraint).  Therefore <productname>PostgreSQL</productname>
-   provides a family of commands to make modifications to existing
-   tables.  Note that this is conceptually distinct from altering
-   the data contained in the table: here we are interested in altering
-   the definition, or structure, of the table.
-  </para>
-
-  <para>
-   You can:
-   <itemizedlist spacing="compact">
-    <listitem>
-     <para>Add columns</para>
-    </listitem>
-    <listitem>
-     <para>Remove columns</para>
-    </listitem>
-    <listitem>
-     <para>Add constraints</para>
-    </listitem>
-    <listitem>
-     <para>Remove constraints</para>
-    </listitem>
-    <listitem>
-     <para>Change default values</para>
-    </listitem>
-    <listitem>
-     <para>Change column data types</para>
-    </listitem>
-    <listitem>
-     <para>Rename columns</para>
-    </listitem>
-    <listitem>
-     <para>Rename tables</para>
-    </listitem>
-   </itemizedlist>
-
-   All these actions are performed using the
-   <xref linkend="sql-altertable">
-   command, whose reference page contains details beyond those given
-   here.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   In <productname>Postgres-XC</> the following are not allowed:
-   <itemizedlist spacing="compact">
-    <listitem>
-     <para>Modifying distribution columns definition</para>
-    </listitem>
-    <listitem>
-     <para>Modifying distribution column values</para>
-    </listitem>
-   </itemizedlist>
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-	In addition to these actions, in <productname>Postgres-XL</productname> you
-can also use <command>ALTER TABLE</> command to:
-   <itemizedlist spacing="compact">
-    <listitem>
-     <para>Change distribution strategy</para>
-    </listitem>
-    <listitem>
-     <para>Add a node to existing distribution target</para>
-    </listitem>
-    <listitem>
-     <para>Remove a node from existing distribution target</para>
-    </listitem>
-   </itemizedlist>
-  </para>
-  <para>
-   In <productname>Postgres-XL</> the following are not allowed:
-   <itemizedlist spacing="compact">
-    <listitem>
-     <para>Modifying distribution columns definition</para>
-    </listitem>
-    <listitem>
-     <para>Modifying distribution column values</para>
-    </listitem>
-   </itemizedlist>
-  </para>
-<!## end>
-  <sect2>
-   <title>Adding a Column</title>
-
-   <indexterm>
-    <primary>column</primary>
-    <secondary>adding</secondary>
-   </indexterm>
-&common;
-   <para>
-    To add a column, use a command like:
-<programlisting>
-ALTER TABLE products ADD COLUMN description text;
-</programlisting>
-    The new column is initially filled with whatever default
-    value is given (null if you don't specify a <literal>DEFAULT</> clause).
-   </para>
-
-   <para>
-    You can also define constraints on the column at the same time,
-    using the usual syntax:
-<programlisting>
-ALTER TABLE products ADD COLUMN description text CHECK (description &lt;&gt; '');
-</programlisting>
-    In fact all the options that can be applied to a column description
-    in <command>CREATE TABLE</> can be used here.  Keep in mind however
-    that the default value must satisfy the given constraints, or the
-    <literal>ADD</> will fail.  Alternatively, you can add
-    constraints later (see below) after you've filled in the new column
-    correctly.
-   </para>
-
-  <tip>
-   <para>
-    Adding a column with a default requires updating each row of the
-    table (to store the new column value).  However, if no default is
-    specified, <productname>PostgreSQL</productname> is able to avoid
-    the physical update.  So if you intend to fill the column with
-    mostly nondefault values, it's best to add the column with no default,
-    insert the correct values using <command>UPDATE</>, and then add any
-    desired default as described below.
-   </para>
-  </tip>
-  </sect2>
-
-  <sect2>
-   <title>Removing a Column</title>
-
-   <indexterm>
-    <primary>column</primary>
-    <secondary>removing</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    To remove a column, use a command like:
-<programlisting>
-ALTER TABLE products DROP COLUMN description;
-</programlisting>
-    Whatever data was in the column disappears.  Table constraints involving
-    the column are dropped, too.  However, if the column is referenced by a
-    foreign key constraint of another table,
-    <productname>PostgreSQL</productname> will not silently drop that
-    constraint.  You can authorize dropping everything that depends on
-    the column by adding <literal>CASCADE</>:
-<programlisting>
-ALTER TABLE products DROP COLUMN description CASCADE;
-</programlisting>
-    See <xref linkend="ddl-depend"> for a description of the general
-    mechanism behind this.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Adding a Constraint</title>
-
-   <indexterm>
-    <primary>constraint</primary>
-    <secondary>adding</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    To add a constraint, the table constraint syntax is used.  For example:
-<programlisting>
-ALTER TABLE products ADD CHECK (name &lt;&gt; '');
-ALTER TABLE products ADD CONSTRAINT some_name UNIQUE (product_no);
-ALTER TABLE products ADD FOREIGN KEY (product_group_id) REFERENCES product_groups;
-</programlisting>
-    To add a not-null constraint, which cannot be written as a table
-    constraint, use this syntax:
-<programlisting>
-ALTER TABLE products ALTER COLUMN product_no SET NOT NULL;
-</programlisting>
-   </para>
-
-   <para>
-    The constraint will be checked immediately, so the table data must
-    satisfy the constraint before it can be added.
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    Please remember that distribution column has to be included in UNIQUE and REFERENCE constraints.
-   </para>
-&xc-constraint;
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Please remember that the distribution column has to be included in UNIQUE and REFERENCE constraints.
-   </para>
-&xc-constraint;
-<!## end>
-  </sect2>
-
-  <sect2>
-   <title>Removing a Constraint</title>
-
-   <indexterm>
-    <primary>constraint</primary>
-    <secondary>removing</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    To remove a constraint you need to know its name.  If you gave it
-    a name then that's easy.  Otherwise the system assigned a
-    generated name, which you need to find out.  The
-    <application>psql</application> command <literal>\d
-    <replaceable>tablename</replaceable></literal> can be helpful
-    here; other interfaces might also provide a way to inspect table
-    details.  Then the command is:
-<programlisting>
-ALTER TABLE products DROP CONSTRAINT some_name;
-</programlisting>
-    (If you are dealing with a generated constraint name like <literal>$2</>,
-    don't forget that you'll need to double-quote it to make it a valid
-    identifier.)
-   </para>
-
-   <para>
-    As with dropping a column, you need to add <literal>CASCADE</> if you
-    want to drop a constraint that something else depends on.  An example
-    is that a foreign key constraint depends on a unique or primary key
-    constraint on the referenced column(s).
-   </para>
-
-   <para>
-    This works the same for all constraint types except not-null
-    constraints. To drop a not null constraint use:
-<programlisting>
-ALTER TABLE products ALTER COLUMN product_no DROP NOT NULL;
-</programlisting>
-    (Recall that not-null constraints do not have names.)
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changing a Column's Default Value</title>
-
-   <indexterm>
-    <primary>default value</primary>
-    <secondary>changing</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    To set a new default for a column, use a command like:
-<programlisting>
-ALTER TABLE products ALTER COLUMN price SET DEFAULT 7.77;
-</programlisting>
-    Note that this doesn't affect any existing rows in the table, it
-    just changes the default for future <command>INSERT</> commands.
-   </para>
-
-   <para>
-    To remove any default value, use:
-<programlisting>
-ALTER TABLE products ALTER COLUMN price DROP DEFAULT;
-</programlisting>
-    This is effectively the same as setting the default to null.
-    As a consequence, it is not an error
-    to drop a default where one hadn't been defined, because the
-    default is implicitly the null value.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changing a Column's Data Type</title>
-
-   <indexterm>
-    <primary>column data type</primary>
-    <secondary>changing</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    To convert a column to a different data type, use a command like:
-<programlisting>
-ALTER TABLE products ALTER COLUMN price TYPE numeric(10,2);
-</programlisting>
-    This will succeed only if each existing entry in the column can be
-    converted to the new type by an implicit cast.  If a more complex
-    conversion is needed, you can add a <literal>USING</> clause that
-    specifies how to compute the new values from the old.
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</> will attempt to convert the column's
-    default value (if any) to the new type, as well as any constraints
-    that involve the column.  But these conversions might fail, or might
-    produce surprising results.  It's often best to drop any constraints
-    on the column before altering its type, and then add back suitably
-    modified constraints afterwords.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> will attempt to convert the column's
-    default value (if any) to the new type, as well as any constraints
-    that involve the column.  But these conversions might fail, or might
-    produce surprising results.  It's often best to drop any constraints
-    on the column before altering its type, and then add back suitably
-    modified constraints afterwards.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> will attempt to convert the column's
-    default value (if any) to the new type, as well as any constraints
-    that involve the column.  But these conversions might fail, or might
-    produce surprising results.  It's often best to drop any constraints
-    on the column before altering its type, and then add back suitably
-    modified constraints afterwards.
-<!## end>
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    It is <productname>Postgres-XC</>'s restriction that you cannot change the
-    type of distribution column.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    It is <productname>Postgres-XL</>'s restriction that you cannot change the
-    type of distribution column.
-   </para>
-<!## end>
-  </sect2>
-
-  <sect2>
-   <title>Renaming a Column</title>
-
-   <indexterm>
-    <primary>column</primary>
-    <secondary>renaming</secondary>
-   </indexterm>
-&common;
-   <para>
-    To rename a column:
-<programlisting>
-ALTER TABLE products RENAME COLUMN product_no TO product_number;
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Renaming a Table</title>
-
-   <indexterm>
-    <primary>table</primary>
-    <secondary>renaming</secondary>
-   </indexterm>
-&common;
-   <para>
-    To rename a table:
-<programlisting>
-ALTER TABLE products RENAME TO items;
-</programlisting>
-   </para>
-  </sect2>
-
-<!## XL>
-  <sect2>
-   <title>Adding a Node to Distribution Target</title>
-
-   <indexterm>
-    <primary>table</primary>
-    <secondary>distribution</secondary>
-   </indexterm>
-   <para>
-    To add a new node to existing distribution:
-<programlisting>
-ALTER TABLE products ADD NODE (datanode_3);
-</programlisting>
-	The datanode must be a valid datanode name. If its a new datanode, then it
-must have been added to the cluster by appropriate mechanism. To learn how to
-add a node to the cluster, please see <xref linkend="add-node">.
-   </para>
-   <para>
-	This command will redistribute the existing table data so as to include the
-new node. For example, in case of <type>DISTRIBUTE BY HASH</> strategy, hash
-value for each row must be recomputed and the row must be moved to the selected
-node based on the new count of datanodes in the distribution list. This
-operation requires an exclusive lock on the table and hence all read and write
-access to the table is temporarily blocked. This can be important especially if
-the table is large and requires considerable time for
-redistribution.
-   </para>
-  </sect2>
-  <sect2>
-   <title>Removing a Node from Distribution Target</title>
-
-   <indexterm>
-    <primary>table</primary>
-    <secondary>distribution</secondary>
-   </indexterm>
-&common;
-   <para>
-    To remove a node from existing distribution:
-<programlisting>
-ALTER TABLE products DELETE NODE (datanode_3);
-</programlisting>
-	It must be noted that if you want to remove a node from the cluster, its
-important that you first remove such node from all existing tables using that
-node and then only remove the node from the cluster.
-   </para>
-   <para>
-	Like the previous command, this also takes an exclusive lock on the table,
-blocking all read and write access to the table.
-   </para>
-  </sect2>
-  <sect2>
-   <title>Changing Distribution Strategy</title>
-
-   <indexterm>
-    <primary>table</primary>
-    <secondary>distribution</secondary>
-   </indexterm>
-&common;
-   <para>
-    To change distribution strategy for a table:
-<programlisting>
-ALTER TABLE products DISSTRIBUTE BY REPLICATION;
-</programlisting>
-You can change distribution strategy for a table with this command. For
-example, a table which was previously distributed by <type>HASH</> can now be
-distributed by <type>REPLICATION</type>.
-   </para>
-   <para>
-	Like the previous command, this also takes an exclusive lock on the table,
-blocking all read and write access to the table.
-   </para>
-  </sect2>
-<!## end>
-
- </sect1>
-
- <sect1 id="ddl-priv">
-  <title>Privileges</title>
-
-  <indexterm zone="ddl-priv">
-   <primary>privilege</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>permission</primary>
-   <see>privilege</see>
-  </indexterm>
-
-  <indexterm zone="ddl-priv">
-   <primary>owner</primary>
-  </indexterm>
-
-  <indexterm zone="ddl-priv">
-   <primary>GRANT</primary>
-  </indexterm>
-
-  <indexterm zone="ddl-priv">
-   <primary>REVOKE</primary>
-  </indexterm>
-&common;
-  <para>
-   When an object is created, it is assigned an owner. The
-   owner is normally the role that executed the creation statement.
-   For most kinds of objects, the initial state is that only the owner
-   (or a superuser) can do anything with the object. To allow
-   other roles to use it, <firstterm>privileges</firstterm> must be
-   granted.
-  </para>
-
-  <para>
-   There are different kinds of privileges: <literal>SELECT</>,
-   <literal>INSERT</>, <literal>UPDATE</>, <literal>DELETE</>,
-   <literal>TRUNCATE</>, <literal>REFERENCES</>, <literal>TRIGGER</>,
-   <literal>CREATE</>, <literal>CONNECT</>, <literal>TEMPORARY</>,
-   <literal>EXECUTE</>, and <literal>USAGE</>.
-   The privileges applicable to a particular
-   object vary depending on the object's type (table, function, etc).
-   For complete information on the different types of privileges
-   supported by <productname>PostgreSQL</productname>, refer to the
-   <xref linkend="sql-grant"> reference
-   page.  The following sections and chapters will also show you how
-   those privileges are used.
-  </para>
-
-  <para>
-   The right to modify or destroy an object is always the privilege of
-   the owner only.
-  </para>
-
-  <para>
-   An object can be assigned to a new owner with an <command>ALTER</command>
-   command of the appropriate kind for the object, e.g. <xref
-   linkend="sql-altertable">.  Superusers can always do
-   this; ordinary roles can only do it if they are both the current owner
-   of the object (or a member of the owning role) and a member of the new
-   owning role.
-  </para>
-
-  <para>
-   To assign privileges, the <command>GRANT</command> command is
-   used. For example, if <literal>joe</literal> is an existing user, and
-   <literal>accounts</literal> is an existing table, the privilege to
-   update the table can be granted with:
-<programlisting>
-GRANT UPDATE ON accounts TO joe;
-</programlisting>
-   Writing <literal>ALL</literal> in place of a specific privilege grants all
-   privileges that are relevant for the object type.
-  </para>
-
-  <para>
-   The special <quote>user</quote> name <literal>PUBLIC</literal> can
-   be used to grant a privilege to every user on the system.  Also,
-   <quote>group</> roles can be set up to help manage privileges when
-   there are many users of a database &mdash; for details see
-   <xref linkend="user-manag">.
-  </para>
-
-  <para>
-   To revoke a privilege, use the fittingly named
-   <command>REVOKE</command> command:
-<programlisting>
-REVOKE ALL ON accounts FROM PUBLIC;
-</programlisting>
-   The special privileges of the object owner (i.e., the right to do
-   <command>DROP</>, <command>GRANT</>, <command>REVOKE</>, etc.)
-   are always implicit in being the owner,
-   and cannot be granted or revoked.  But the object owner can choose
-   to revoke his own ordinary privileges, for example to make a
-   table read-only for himself as well as others.
-  </para>
-
-  <para>
-   Ordinarily, only the object's owner (or a superuser) can grant or
-   revoke privileges on an object.  However, it is possible to grant a
-   privilege <quote>with grant option</>, which gives the recipient
-   the right to grant it in turn to others.  If the grant option is
-   subsequently revoked then all who received the privilege from that
-   recipient (directly or through a chain of grants) will lose the
-   privilege.  For details see the <xref linkend="sql-grant"> and
-   <xref linkend="sql-revoke"> reference pages.
-  </para>
- </sect1>
-
- <sect1 id="ddl-schemas">
-  <title>Schemas</title>
-
-  <indexterm zone="ddl-schemas">
-   <primary>schema</primary>
-  </indexterm>
-&common;
-  <para>
-   A <productname>PostgreSQL</productname> database cluster
-   contains one or more named databases.  Users and groups of users are
-   shared across the entire cluster, but no other data is shared across
-   databases.  Any given client connection to the server can access
-   only the data in a single database, the one specified in the connection
-   request.
-  </para>
-
-  <note>
-   <para>
-    Users of a cluster do not necessarily have the privilege to access every
-    database in the cluster.  Sharing of user names means that there
-    cannot be different users named, say, <literal>joe</> in two databases
-    in the same cluster; but the system can be configured to allow
-    <literal>joe</> access to only some of the databases.
-   </para>
-  </note>
-
-  <para>
-   A database contains one or more named <firstterm>schemas</>, which
-   in turn contain tables.  Schemas also contain other kinds of named
-   objects, including data types, functions, and operators.  The same
-   object name can be used in different schemas without conflict; for
-   example, both <literal>schema1</> and <literal>myschema</> can
-   contain tables named <literal>mytable</>.  Unlike databases,
-   schemas are not rigidly separated: a user can access objects in any
-   of the schemas in the database he is connected to, if he has
-   privileges to do so.
-  </para>
-
-  <para>
-   There are several reasons why one might want to use schemas:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      To allow many users to use one database without interfering with
-      each other.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      To organize database objects into logical groups to make them
-      more manageable.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Third-party applications can be put into separate schemas so
-      they do not collide with the names of other objects.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   Schemas are analogous to directories at the operating system level,
-   except that schemas cannot be nested.
-  </para>
-
-  <sect2 id="ddl-schemas-create">
-   <title>Creating a Schema</title>
-
-   <indexterm zone="ddl-schemas-create">
-    <primary>schema</primary>
-    <secondary>creating</secondary>
-   </indexterm>
-&common;
-   <para>
-    To create a schema, use the <xref linkend="sql-createschema">
-    command.  Give the schema a name
-    of your choice.  For example:
-<programlisting>
-CREATE SCHEMA myschema;
-</programlisting>
-   </para>
-
-   <indexterm>
-    <primary>qualified name</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>name</primary>
-    <secondary>qualified</secondary>
-   </indexterm>
-
-   <para>
-    To create or access objects in a schema, write a
-    <firstterm>qualified name</> consisting of the schema name and
-    table name separated by a dot:
-<synopsis>
-<replaceable>schema</><literal>.</><replaceable>table</>
-</synopsis>
-    This works anywhere a table name is expected, including the table
-    modification commands and the data access commands discussed in
-    the following chapters.
-    (For brevity we will speak of tables only, but the same ideas apply
-    to other kinds of named objects, such as types and functions.)
-   </para>
-
-   <para>
-    Actually, the even more general syntax
-<synopsis>
-<replaceable>database</><literal>.</><replaceable>schema</><literal>.</><replaceable>table</>
-</synopsis>
-    can be used too, but at present this is just for <foreignphrase>pro
-    forma</> compliance with the SQL standard.  If you write a database name,
-    it must be the same as the database you are connected to.
-   </para>
-
-   <para>
-    So to create a table in the new schema, use:
-<programlisting>
-CREATE TABLE myschema.mytable (
- ...
-);
-</programlisting>
-   </para>
-
-   <indexterm>
-    <primary>schema</primary>
-    <secondary>removing</secondary>
-   </indexterm>
-
-   <para>
-    To drop a schema if it's empty (all objects in it have been
-    dropped), use:
-<programlisting>
-DROP SCHEMA myschema;
-</programlisting>
-    To drop a schema including all contained objects, use:
-<programlisting>
-DROP SCHEMA myschema CASCADE;
-</programlisting>
-    See <xref linkend="ddl-depend"> for a description of the general
-    mechanism behind this.
-   </para>
-
-   <para>
-    Often you will want to create a schema owned by someone else
-    (since this is one of the ways to restrict the activities of your
-    users to well-defined namespaces).  The syntax for that is:
-<programlisting>
-CREATE SCHEMA <replaceable>schemaname</replaceable> AUTHORIZATION <replaceable>username</replaceable>;
-</programlisting>
-    You can even omit the schema name, in which case the schema name
-    will be the same as the user name.  See <xref
-    linkend="ddl-schemas-patterns"> for how this can be useful.
-   </para>
-
-   <para>
-    Schema names beginning with <literal>pg_</> are reserved for
-    system purposes and cannot be created by users.
-   </para>
-  </sect2>
-
-  <sect2 id="ddl-schemas-public">
-   <title>The Public Schema</title>
-
-   <indexterm zone="ddl-schemas-public">
-    <primary>schema</primary>
-    <secondary>public</secondary>
-   </indexterm>
-&common;
-   <para>
-    In the previous sections we created tables without specifying any
-    schema names.  By default such tables (and other objects) are
-    automatically put into a schema named <quote>public</quote>.  Every new
-    database contains such a schema.  Thus, the following are equivalent:
-<programlisting>
-CREATE TABLE products ( ... );
-</programlisting>
-    and:
-<programlisting>
-CREATE TABLE public.products ( ... );
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="ddl-schemas-path">
-   <title>The Schema Search Path</title>
-
-   <indexterm>
-    <primary>search path</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>unqualified name</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>name</primary>
-    <secondary>unqualified</secondary>
-   </indexterm>
-&common;
-   <para>
-    Qualified names are tedious to write, and it's often best not to
-    wire a particular schema name into applications anyway.  Therefore
-    tables are often referred to by <firstterm>unqualified names</>,
-    which consist of just the table name.  The system determines which table
-    is meant by following a <firstterm>search path</>, which is a list
-    of schemas to look in.  The first matching table in the search path
-    is taken to be the one wanted.  If there is no match in the search
-    path, an error is reported, even if matching table names exist
-    in other schemas in the database.
-   </para>
-
-   <indexterm>
-    <primary>schema</primary>
-    <secondary>current</secondary>
-   </indexterm>
-
-   <para>
-    The first schema named in the search path is called the current schema.
-    Aside from being the first schema searched, it is also the schema in
-    which new tables will be created if the <command>CREATE TABLE</>
-    command does not specify a schema name.
-   </para>
-
-   <indexterm>
-    <primary>search_path</primary>
-   </indexterm>
-
-   <para>
-    To show the current search path, use the following command:
-<programlisting>
-SHOW search_path;
-</programlisting>
-    In the default setup this returns:
-<screen>
- search_path
---------------
- "$user",public
-</screen>
-    The first element specifies that a schema with the same name as
-    the current user is to be searched.  If no such schema exists,
-    the entry is ignored.  The second element refers to the
-    public schema that we have seen already.
-   </para>
-
-   <para>
-    The first schema in the search path that exists is the default
-    location for creating new objects.  That is the reason that by
-    default objects are created in the public schema.  When objects
-    are referenced in any other context without schema qualification
-    (table modification, data modification, or query commands) the
-    search path is traversed until a matching object is found.
-    Therefore, in the default configuration, any unqualified access
-    again can only refer to the public schema.
-   </para>
-
-   <para>
-    To put our new schema in the path, we use:
-<programlisting>
-SET search_path TO myschema,public;
-</programlisting>
-    (We omit the <literal>$user</literal> here because we have no
-    immediate need for it.)  And then we can access the table without
-    schema qualification:
-<programlisting>
-DROP TABLE mytable;
-</programlisting>
-    Also, since <literal>myschema</literal> is the first element in
-    the path, new objects would by default be created in it.
-   </para>
-
-   <para>
-    We could also have written:
-<programlisting>
-SET search_path TO myschema;
-</programlisting>
-    Then we no longer have access to the public schema without
-    explicit qualification.  There is nothing special about the public
-    schema except that it exists by default.  It can be dropped, too.
-   </para>
-
-   <para>
-    See also <xref linkend="functions-info"> for other ways to manipulate
-    the schema search path.
-   </para>
-
-   <para>
-    The search path works in the same way for data type names, function names,
-    and operator names as it does for table names.  Data type and function
-    names can be qualified in exactly the same way as table names.  If you
-    need to write a qualified operator name in an expression, there is a
-    special provision: you must write
-<synopsis>
-<literal>OPERATOR(</><replaceable>schema</><literal>.</><replaceable>operator</><literal>)</>
-</synopsis>
-    This is needed to avoid syntactic ambiguity.  An example is:
-<programlisting>
-SELECT 3 OPERATOR(pg_catalog.+) 4;
-</programlisting>
-    In practice one usually relies on the search path for operators,
-    so as not to have to write anything so ugly as that.
-   </para>
-  </sect2>
-
-  <sect2 id="ddl-schemas-priv">
-   <title>Schemas and Privileges</title>
-
-   <indexterm zone="ddl-schemas-priv">
-    <primary>privilege</primary>
-    <secondary sortas="schemas">for schemas</secondary>
-   </indexterm>
-&common;
-   <para>
-    By default, users cannot access any objects in schemas they do not
-    own.  To allow that, the owner of the schema must grant the
-    <literal>USAGE</literal> privilege on the schema.  To allow users
-    to make use of the objects in the schema, additional privileges
-    might need to be granted, as appropriate for the object.
-   </para>
-
-   <para>
-    A user can also be allowed to create objects in someone else's
-    schema.  To allow that, the <literal>CREATE</literal> privilege on
-    the schema needs to be granted.  Note that by default, everyone
-    has <literal>CREATE</literal> and <literal>USAGE</literal> privileges on
-    the schema
-    <literal>public</literal>.  This allows all users that are able to
-    connect to a given database to create objects in its
-    <literal>public</literal> schema.  If you do
-    not want to allow that, you can revoke that privilege:
-<programlisting>
-REVOKE CREATE ON SCHEMA public FROM PUBLIC;
-</programlisting>
-    (The first <quote>public</quote> is the schema, the second
-    <quote>public</quote> means <quote>every user</quote>.  In the
-    first sense it is an identifier, in the second sense it is a
-    key word, hence the different capitalization; recall the
-    guidelines from <xref linkend="sql-syntax-identifiers">.)
-   </para>
-  </sect2>
-
-  <sect2 id="ddl-schemas-catalog">
-   <title>The System Catalog Schema</title>
-
-   <indexterm zone="ddl-schemas-catalog">
-    <primary>system catalog</primary>
-    <secondary>schema</secondary>
-   </indexterm>
-&common;
-   <para>
-    In addition to <literal>public</> and user-created schemas, each
-    database contains a <literal>pg_catalog</> schema, which contains
-    the system tables and all the built-in data types, functions, and
-    operators.  <literal>pg_catalog</> is always effectively part of
-    the search path.  If it is not named explicitly in the path then
-    it is implicitly searched <emphasis>before</> searching the path's
-    schemas.  This ensures that built-in names will always be
-    findable.  However, you can explicitly place
-    <literal>pg_catalog</> at the end of your search path if you
-    prefer to have user-defined names override built-in names.
-   </para>
-
-   <para>
-    In <productname>PostgreSQL</productname> versions before 7.3,
-    table names beginning with <literal>pg_</> were reserved.  This is
-    no longer true: you can create such a table name if you wish, in
-    any non-system schema.  However, it's best to continue to avoid
-    such names, to ensure that you won't suffer a conflict if some
-    future version defines a system table named the same as your
-    table.  (With the default search path, an unqualified reference to
-    your table name would then be resolved as the system table instead.)
-    System tables will continue to follow the convention of having
-    names beginning with <literal>pg_</>, so that they will not
-    conflict with unqualified user-table names so long as users avoid
-    the <literal>pg_</> prefix.
-   </para>
-  </sect2>
-
-  <sect2 id="ddl-schemas-patterns">
-   <title>Usage Patterns</title>
-&common;
-   <para>
-    Schemas can be used to organize your data in many ways.  There are
-    a few usage patterns that are recommended and are easily supported by
-    the default configuration:
-    <itemizedlist>
-     <listitem>
-      <para>
-       If you do not create any schemas then all users access the
-       public schema implicitly.  This simulates the situation where
-       schemas are not available at all.  This setup is mainly
-       recommended when there is only a single user or a few cooperating
-       users in a database.  This setup also allows smooth transition
-       from the non-schema-aware world.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       You can create a schema for each user with the same name as
-       that user.  Recall that the default search path starts with
-       <literal>$user</literal>, which resolves to the user name.
-       Therefore, if each user has a separate schema, they access their
-       own schemas by default.
-      </para>
-
-      <para>
-       If you use this setup then you might also want to revoke access
-       to the public schema (or drop it altogether), so users are
-       truly constrained to their own schemas.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       To install shared applications (tables to be used by everyone,
-       additional functions provided by third parties, etc.), put them
-       into separate schemas.  Remember to grant appropriate
-       privileges to allow the other users to access them.  Users can
-       then refer to these additional objects by qualifying the names
-       with a schema name, or they can put the additional schemas into
-       their search path, as they choose.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-  </sect2>
-
-  <sect2 id="ddl-schemas-portability">
-   <title>Portability</title>
-&common;
-   <para>
-    In the SQL standard, the notion of objects in the same schema
-    being owned by different users does not exist.  Moreover, some
-    implementations do not allow you to create schemas that have a
-    different name than their owner.  In fact, the concepts of schema
-    and user are nearly equivalent in a database system that
-    implements only the basic schema support specified in the
-    standard.  Therefore, many users consider qualified names to
-    really consist of
-    <literal><replaceable>username</>.<replaceable>tablename</></literal>.
-    This is how <productname>PostgreSQL</productname> will effectively
-    behave if you create a per-user schema for every user.
-   </para>
-
-   <para>
-    Also, there is no concept of a <literal>public</> schema in the
-    SQL standard.  For maximum conformance to the standard, you should
-    not use (perhaps even remove) the <literal>public</> schema.
-   </para>
-
-   <para>
-    Of course, some SQL database systems might not implement schemas
-    at all, or provide namespace support by allowing (possibly
-    limited) cross-database access.  If you need to work with those
-    systems, then maximum portability would be achieved by not using
-    schemas at all.
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="ddl-inherit">
-  <title>Inheritance</title>
-
-  <indexterm>
-   <primary>inheritance</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>table</primary>
-   <secondary>inheritance</secondary>
-  </indexterm>
-&common;
-  <para>
-   <productname>PostgreSQL</productname> implements table inheritance,
-   which can be a useful tool for database designers.  (SQL:1999 and
-   later define a type inheritance feature, which differs in many
-   respects from the features described here.)
-  </para>
-
-  <para>
-   Let's start with an example: suppose we are trying to build a data
-   model for cities.  Each state has many cities, but only one
-   capital. We want to be able to quickly retrieve the capital city
-   for any particular state. This can be done by creating two tables,
-   one for state capitals and one for cities that are not
-   capitals. However, what happens when we want to ask for data about
-   a city, regardless of whether it is a capital or not? The
-   inheritance feature can help to resolve this problem. We define the
-   <structname>capitals</structname> table so that it inherits from
-   <structname>cities</structname>:
-
-<programlisting>
-CREATE TABLE cities (
-    name            text,
-    population      float,
-    altitude        int     -- in feet
-);
-
-CREATE TABLE capitals (
-    state           char(2)
-) INHERITS (cities);
-</programlisting>
-
-   In this case, the <structname>capitals</> table <firstterm>inherits</>
-   all the columns of its parent table, <structname>cities</>. State
-   capitals also have an extra column, <structfield>state</>, that shows
-   their state.
-  </para>
-
-  <para>
-   In <productname>PostgreSQL</productname>, a table can inherit from
-   zero or more other tables, and a query can reference either all
-   rows of a table or all rows of a table plus all of its descendant tables.
-   The latter behavior is the default.
-   For example, the following query finds the names of all cities,
-   including state capitals, that are located at an altitude over
-   500 feet:
-
-<programlisting>
-SELECT name, altitude
-    FROM cities
-    WHERE altitude &gt; 500;
-</programlisting>
-
-   Given the sample data from the <productname>PostgreSQL</productname>
-   tutorial (see <xref linkend="tutorial-sql-intro">), this returns:
-
-<programlisting>
-   name    | altitude
------------+----------
- Las Vegas |     2174
- Mariposa  |     1953
- Madison   |      845
-</programlisting>
-  </para>
-
-  <para>
-   On the other hand, the following query finds all the cities that
-   are not state capitals and are situated at an altitude over 500 feet:
-
-<programlisting>
-SELECT name, altitude
-    FROM ONLY cities
-    WHERE altitude &gt; 500;
-
-   name    | altitude
------------+----------
- Las Vegas |     2174
- Mariposa  |     1953
-</programlisting>
-  </para>
-
-  <para>
-   Here the <literal>ONLY</literal> keyword indicates that the query
-   should apply only to <structname>cities</structname>, and not any tables
-   below <structname>cities</structname> in the inheritance hierarchy.  Many
-   of the commands that we have already discussed &mdash;
-   <command>SELECT</command>, <command>UPDATE</command> and
-   <command>DELETE</command> &mdash; support the
-   <literal>ONLY</literal> keyword.
-  </para>
-
-  <para>
-   In some cases you might wish to know which table a particular row
-   originated from. There is a system column called
-   <structfield>tableoid</structfield> in each table which can tell you the
-   originating table:
-
-<programlisting>
-SELECT c.tableoid, c.name, c.altitude
-FROM cities c
-WHERE c.altitude &gt; 500;
-</programlisting>
-
-   which returns:
-
-<programlisting>
- tableoid |   name    | altitude
-----------+-----------+----------
-   139793 | Las Vegas |     2174
-   139793 | Mariposa  |     1953
-   139798 | Madison   |      845
-</programlisting>
-
-<!## PG>
-<!-- NOTICE:
-     XC doesn't enforce OID identity throughout the cluster.
--->
-   (If you try to reproduce this example, you will probably get
-   different numeric OIDs.)  By doing a join with
-   <structname>pg_class</> you can see the actual table names:
-
-<programlisting>
-SELECT p.relname, c.name, c.altitude
-FROM cities c, pg_class p
-WHERE c.altitude &gt; 500 AND c.tableoid = p.oid;
-</programlisting>
-
-   which returns:
-
-<programlisting>
- relname  |   name    | altitude
-----------+-----------+----------
- cities   | Las Vegas |     2174
- cities   | Mariposa  |     1953
- capitals | Madison   |      845
-</programlisting>
-<!## end>
-  </para>
-
-  <para>
-   Inheritance does not automatically propagate data from
-   <command>INSERT</command> or <command>COPY</command> commands to
-   other tables in the inheritance hierarchy. In our example, the
-   following <command>INSERT</command> statement will fail:
-<programlisting>
-INSERT INTO cities (name, population, altitude, state)
-VALUES ('New York', NULL, NULL, 'NY');
-</programlisting>
-   We might hope that the data would somehow be routed to the
-   <structname>capitals</structname> table, but this does not happen:
-   <command>INSERT</command> always inserts into exactly the table
-   specified.  In some cases it is possible to redirect the insertion
-   using a rule (see <xref linkend="rules">).  However that does not
-   help for the above case because the <structname>cities</> table
-   does not contain the column <structfield>state</>, and so the
-   command will be rejected before the rule can be applied.
-  </para>
-
-  <para>
-   All check constraints and not-null constraints on a parent table are
-   automatically inherited by its children.  Other types of constraints
-   (unique, primary key, and foreign key constraints) are not inherited.
-  </para>
-
-  <para>
-   A table can inherit from more than one parent table, in which case it has
-   the union of the columns defined by the parent tables.  Any columns
-   declared in the child table's definition are added to these.  If the
-   same column name appears in multiple parent tables, or in both a parent
-   table and the child's definition, then these columns are <quote>merged</>
-   so that there is only one such column in the child table.  To be merged,
-   columns must have the same data types, else an error is raised.  The
-   merged column will have copies of all the check constraints coming from
-   any one of the column definitions it came from, and will be marked not-null
-   if any of them are.
-  </para>
-
-  <para>
-   Table inheritance is typically established when the child table is
-   created, using the <literal>INHERITS</> clause of the
-   <xref linkend="sql-createtable">
-   statement.
-   Alternatively, a table which is already defined in a compatible way can
-   have a new parent relationship added, using the <literal>INHERIT</literal>
-   variant of <xref linkend="sql-altertable">.
-   To do this the new child table must already include columns with
-   the same names and types as the columns of the parent. It must also include
-   check constraints with the same names and check expressions as those of the
-   parent. Similarly an inheritance link can be removed from a child using the
-   <literal>NO INHERIT</literal> variant of <command>ALTER TABLE</>.
-<!## PG>
-<!-- NOTICE:
-     Reference to partitioning
--->
-   Dynamically adding and removing inheritance links like this can be useful
-   when the inheritance relationship is being used for table
-   partitioning (see <xref linkend="ddl-partitioning">).
-<!## end>
-  </para>
-
-  <para>
-   One convenient way to create a compatible table that will later be made
-   a new child is to use the <literal>LIKE</literal> clause in <command>CREATE
-   TABLE</command>. This creates a new table with the same columns as
-   the source table. If there are any <literal>CHECK</literal>
-   constraints defined on the source table, the <literal>INCLUDING
-   CONSTRAINTS</literal> option to <literal>LIKE</literal> should be
-   specified, as the new child must have constraints matching the parent
-   to be considered compatible.
-  </para>
-
-  <para>
-   A parent table cannot be dropped while any of its children remain. Neither
-   can columns or check constraints of child tables be dropped or altered
-   if they are inherited
-   from any parent tables. If you wish to remove a table and all of its
-   descendants, one easy way is to drop the parent table with the
-   <literal>CASCADE</literal> option.
-  </para>
-
-  <para>
-   <xref linkend="sql-altertable"> will
-   propagate any changes in column data definitions and check
-   constraints down the inheritance hierarchy.  Again, dropping
-   columns that are depended on by other tables is only possible when using
-   the <literal>CASCADE</literal> option. <command>ALTER
-   TABLE</command> follows the same rules for duplicate column merging
-   and rejection that apply during <command>CREATE TABLE</command>.
-  </para>
-
-  <para>
-   Note how table access permissions are handled.  Querying a parent
-   table can automatically access data in child tables without further
-   access privilege checking.  This preserves the appearance that the
-   data is (also) in the parent table.  Accessing the child tables
-   directly is, however, not automatically allowed and would require
-   further privileges to be granted.
-  </para>
-
- <sect2 id="ddl-inherit-caveats">
-  <title>Caveats</title>
-&common;
-  <para>
-   Note that not all SQL commands are able to work on
-   inheritance hierarchies.  Commands that are used for data querying,
-   data modification, or schema modification
-   (e.g., <literal>SELECT</literal>, <literal>UPDATE</literal>, <literal>DELETE</literal>,
-   most variants of <literal>ALTER TABLE</literal>, but
-   not <literal>INSERT</literal> and <literal>ALTER TABLE ...
-   RENAME</literal>) typically default to including child tables and
-   support the <literal>ONLY</literal> notation to exclude them.
-   Commands that do database maintenance and tuning
-   (e.g., <literal>REINDEX</literal>, <literal>VACUUM</literal>)
-   typically only work on individual, physical tables and do no
-   support recursing over inheritance hierarchies.  The respective
-   behavior of each individual command is documented in the reference
-   part (<xref linkend="sql-commands">).
-  </para>
-
-  <para>
-   A serious limitation of the inheritance feature is that indexes (including
-   unique constraints) and foreign key constraints only apply to single
-   tables, not to their inheritance children. This is true on both the
-   referencing and referenced sides of a foreign key constraint. Thus,
-   in the terms of the above example:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      If we declared <structname>cities</>.<structfield>name</> to be
-      <literal>UNIQUE</> or a <literal>PRIMARY KEY</>, this would not stop the
-      <structname>capitals</> table from having rows with names duplicating
-      rows in <structname>cities</>.  And those duplicate rows would by
-      default show up in queries from <structname>cities</>.  In fact, by
-      default <structname>capitals</> would have no unique constraint at all,
-      and so could contain multiple rows with the same name.
-      You could add a unique constraint to <structname>capitals</>, but this
-      would not prevent duplication compared to <structname>cities</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Similarly, if we were to specify that
-      <structname>cities</>.<structfield>name</> <literal>REFERENCES</> some
-      other table, this constraint would not automatically propagate to
-      <structname>capitals</>.  In this case you could work around it by
-      manually adding the same <literal>REFERENCES</> constraint to
-      <structname>capitals</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Specifying that another table's column <literal>REFERENCES
-      cities(name)</> would allow the other table to contain city names, but
-      not capital names.  There is no good workaround for this case.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   These deficiencies will probably be fixed in some future release,
-   but in the meantime considerable care is needed in deciding whether
-   inheritance is useful for your application.
-  </para>
-
-  <note>
-   <title>Deprecated</title>
-   <para>
-     In releases of <productname>PostgreSQL</productname> prior to 7.1, the
-     default behavior was not to include child tables in queries. This was
-     found to be error prone and also in violation of the SQL
-     standard.  You can get the pre-7.1 behavior by turning off the
-     <xref linkend="guc-sql-inheritance"> configuration
-     option.
-   </para>
-  </note>
-
-   </sect2>
-  </sect1>
-
-<!## PG>
-<!-- NOTICE:
-     XC seems to support almost all the feature here, but needs TRIGGER.
-     Should restore this section when XC supports TRIGGER.
--->
-
-  <sect1 id="ddl-partitioning">
-   <title>Partitioning</title>
-
-   <indexterm>
-    <primary>partitioning</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>table</primary>
-    <secondary>partitioning</secondary>
-   </indexterm>
-
-   <para>
-    <productname>PostgreSQL</productname> supports basic table
-    partitioning. This section describes why and how to implement
-    partitioning as part of your database design.
-   </para>
-
-   <sect2 id="ddl-partitioning-overview">
-     <title>Overview</title>
-
-   <para>
-    Partitioning refers to splitting what is logically one large table
-    into smaller physical pieces.
-    Partitioning can provide several benefits:
-   <itemizedlist>
-    <listitem>
-     <para>
-      Query performance can be improved dramatically in certain situations,
-      particularly when most of the heavily accessed rows of the table are in a
-      single partition or a small number of partitions.  The partitioning
-      substitutes for leading columns of indexes, reducing index size and
-      making it more likely that the heavily-used parts of the indexes
-      fit in memory.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      When queries or updates access a large percentage of a single
-      partition, performance can be improved by taking advantage
-      of sequential scan of that partition instead of using an
-      index and random access reads scattered across the whole table.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Bulk loads and deletes can be accomplished by adding or removing
-      partitions, if that requirement is planned into the partitioning design.
-      <command>ALTER TABLE</> is far faster than a bulk operation.
-      It also entirely avoids the <command>VACUUM</command>
-      overhead caused by a bulk <command>DELETE</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Seldom-used data can be migrated to cheaper and slower storage media.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-    The benefits will normally be worthwhile only when a table would
-    otherwise be very large. The exact point at which a table will
-    benefit from partitioning depends on the application, although a
-    rule of thumb is that the size of the table should exceed the physical
-    memory of the database server.
-   </para>
-
-   <para>
-    Currently, <productname>PostgreSQL</productname> supports partitioning
-    via table inheritance.  Each partition must be created as a child
-    table of a single parent table.  The parent table itself is normally
-    empty; it exists just to represent the entire data set.  You should be
-    familiar with inheritance (see <xref linkend="ddl-inherit">) before
-    attempting to set up partitioning.
-   </para>
-
-   <para>
-    The following forms of partitioning can be implemented in
-    <productname>PostgreSQL</productname>:
-
-    <variablelist>
-     <varlistentry>
-      <term>Range Partitioning</term>
-
-      <listitem>
-       <para>
-        The table is partitioned into <quote>ranges</quote> defined
-        by a key column or set of columns, with no overlap between
-        the ranges of values assigned to different partitions.  For
-        example one might partition by date ranges, or by ranges of
-        identifiers for particular business objects.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>List Partitioning</term>
-
-      <listitem>
-       <para>
-        The table is partitioned by explicitly listing which key values
-        appear in each partition.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-   </sect2>
-
-   <sect2 id="ddl-partitioning-implementation">
-     <title>Implementing Partitioning</title>
-
-    <para>
-     To set up a partitioned table, do the following:
-     <orderedlist spacing="compact">
-      <listitem>
-       <para>
-        Create the <quote>master</quote> table, from which all of the
-        partitions will inherit.
-       </para>
-       <para>
-        This table will contain no data.  Do not define any check
-        constraints on this table, unless you intend them to
-        be applied equally to all partitions.  There is no point
-        in defining any indexes or unique constraints on it, either.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Create several <quote>child</quote> tables that each inherit from
-        the master table.  Normally, these tables will not add any columns
-        to the set inherited from the master.
-       </para>
-
-       <para>
-        We will refer to the child tables as partitions, though they
-        are in every way normal <productname>PostgreSQL</> tables.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add table constraints to the partition tables to define the
-        allowed key values in each partition.
-       </para>
-
-       <para>
-        Typical examples would be:
-<programlisting>
-CHECK ( x = 1 )
-CHECK ( county IN ( 'Oxfordshire', 'Buckinghamshire', 'Warwickshire' ))
-CHECK ( outletID &gt;= 100 AND outletID &lt; 200 )
-</programlisting>
-        Ensure that the constraints guarantee that there is no overlap
-        between the key values permitted in different partitions.  A common
-        mistake is to set up range constraints like:
-<programlisting>
-CHECK ( outletID BETWEEN 100 AND 200 )
-CHECK ( outletID BETWEEN 200 AND 300 )
-</programlisting>
-        This is wrong since it is not clear which partition the key value
-        200 belongs in.
-       </para>
-
-       <para>
-        Note that there is no difference in
-        syntax between range and list partitioning; those terms are
-        descriptive only.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        For each partition, create an index on the key column(s),
-        as well as any other indexes you might want.  (The key index is
-        not strictly necessary, but in most scenarios it is helpful.
-        If you intend the key values to be unique then you should
-        always create a unique or primary-key constraint for each
-        partition.)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Optionally, define a trigger or rule to redirect data inserted into
-        the master table to the appropriate partition.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Ensure that the <xref linkend="guc-constraint-exclusion">
-        configuration parameter is not disabled in
-        <filename>postgresql.conf</>.
-        If it is, queries will not be optimized as desired.
-       </para>
-      </listitem>
-
-     </orderedlist>
-    </para>
-
-    <para>
-     For example, suppose we are constructing a database for a large
-     ice cream company. The company measures peak temperatures every
-     day as well as ice cream sales in each region. Conceptually,
-     we want a table like:
-
-<programlisting>
-CREATE TABLE measurement (
-    city_id         int not null,
-    logdate         date not null,
-    peaktemp        int,
-    unitsales       int
-);
-</programlisting>
-
-     We know that most queries will access just the last week's, month's or
-     quarter's data, since the main use of this table will be to prepare
-     online reports for management.
-     To reduce the amount of old data that needs to be stored, we
-     decide to only keep the most recent 3 years worth of data. At the
-     beginning of each month we will remove the oldest month's data.
-    </para>
-
-    <para>
-     In this situation we can use partitioning to help us meet all of our
-     different requirements for the measurements table. Following the
-     steps outlined above, partitioning can be set up as follows:
-    </para>
-
-    <para>
-     <orderedlist spacing="compact">
-      <listitem>
-       <para>
-        The master table is the <structname>measurement</> table, declared
-        exactly as above.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Next we create one partition for each active month:
-
-<programlisting>
-CREATE TABLE measurement_y2006m02 ( ) INHERITS (measurement);
-CREATE TABLE measurement_y2006m03 ( ) INHERITS (measurement);
-...
-CREATE TABLE measurement_y2007m11 ( ) INHERITS (measurement);
-CREATE TABLE measurement_y2007m12 ( ) INHERITS (measurement);
-CREATE TABLE measurement_y2008m01 ( ) INHERITS (measurement);
-</programlisting>
-
-        Each of the partitions are complete tables in their own right,
-        but they inherit their definitions from the
-        <structname>measurement</> table.
-       </para>
-
-       <para>
-        This solves one of our problems: deleting old data. Each
-        month, all we will need to do is perform a <command>DROP
-        TABLE</command> on the oldest child table and create a new
-        child table for the new month's data.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        We must provide non-overlapping table constraints.  Rather than
-        just creating the partition tables as above, the table creation
-        script should really be:
-
-<programlisting>
-CREATE TABLE measurement_y2006m02 (
-    CHECK ( logdate &gt;= DATE '2006-02-01' AND logdate &lt; DATE '2006-03-01' )
-) INHERITS (measurement);
-CREATE TABLE measurement_y2006m03 (
-    CHECK ( logdate &gt;= DATE '2006-03-01' AND logdate &lt; DATE '2006-04-01' )
-) INHERITS (measurement);
-...
-CREATE TABLE measurement_y2007m11 (
-    CHECK ( logdate &gt;= DATE '2007-11-01' AND logdate &lt; DATE '2007-12-01' )
-) INHERITS (measurement);
-CREATE TABLE measurement_y2007m12 (
-    CHECK ( logdate &gt;= DATE '2007-12-01' AND logdate &lt; DATE '2008-01-01' )
-) INHERITS (measurement);
-CREATE TABLE measurement_y2008m01 (
-    CHECK ( logdate &gt;= DATE '2008-01-01' AND logdate &lt; DATE '2008-02-01' )
-) INHERITS (measurement);
-</programlisting>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        We probably need indexes on the key columns too:
-
-<programlisting>
-CREATE INDEX measurement_y2006m02_logdate ON measurement_y2006m02 (logdate);
-CREATE INDEX measurement_y2006m03_logdate ON measurement_y2006m03 (logdate);
-...
-CREATE INDEX measurement_y2007m11_logdate ON measurement_y2007m11 (logdate);
-CREATE INDEX measurement_y2007m12_logdate ON measurement_y2007m12 (logdate);
-CREATE INDEX measurement_y2008m01_logdate ON measurement_y2008m01 (logdate);
-</programlisting>
-
-        We choose not to add further indexes at this time.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        We want our application to be able to say <literal>INSERT INTO
-        measurement ...</> and have the data be redirected into the
-        appropriate partition table.  We can arrange that by attaching
-        a suitable trigger function to the master table.
-        If data will be added only to the latest partition, we can
-        use a very simple trigger function:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION measurement_insert_trigger()
-RETURNS TRIGGER AS $$
-BEGIN
-    INSERT INTO measurement_y2008m01 VALUES (NEW.*);
-    RETURN NULL;
-END;
-$$
-LANGUAGE plpgsql;
-</programlisting>
-
-        After creating the function, we create a trigger which
-        calls the trigger function:
-
-<programlisting>
-CREATE TRIGGER insert_measurement_trigger
-    BEFORE INSERT ON measurement
-    FOR EACH ROW EXECUTE PROCEDURE measurement_insert_trigger();
-</programlisting>
-
-        We must redefine the trigger function each month so that it always
-        points to the current partition.  The trigger definition does
-        not need to be updated, however.
-       </para>
-
-       <para>
-        We might want to insert data and have the server automatically
-        locate the partition into which the row should be added. We
-        could do this with a more complex trigger function, for example:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION measurement_insert_trigger()
-RETURNS TRIGGER AS $$
-BEGIN
-    IF ( NEW.logdate &gt;= DATE '2006-02-01' AND
-         NEW.logdate &lt; DATE '2006-03-01' ) THEN
-        INSERT INTO measurement_y2006m02 VALUES (NEW.*);
-    ELSIF ( NEW.logdate &gt;= DATE '2006-03-01' AND
-            NEW.logdate &lt; DATE '2006-04-01' ) THEN
-        INSERT INTO measurement_y2006m03 VALUES (NEW.*);
-    ...
-    ELSIF ( NEW.logdate &gt;= DATE '2008-01-01' AND
-            NEW.logdate &lt; DATE '2008-02-01' ) THEN
-        INSERT INTO measurement_y2008m01 VALUES (NEW.*);
-    ELSE
-        RAISE EXCEPTION 'Date out of range.  Fix the measurement_insert_trigger() function!';
-    END IF;
-    RETURN NULL;
-END;
-$$
-LANGUAGE plpgsql;
-</programlisting>
-
-        The trigger definition is the same as before.
-        Note that each <literal>IF</literal> test must exactly match the
-        <literal>CHECK</literal> constraint for its partition.
-       </para>
-
-       <para>
-        While this function is more complex than the single-month case,
-        it doesn't need to be updated as often, since branches can be
-        added in advance of being needed.
-       </para>
-
-       <note>
-        <para>
-         In practice it might be best to check the newest partition first,
-         if most inserts go into that partition.  For simplicity we have
-         shown the trigger's tests in the same order as in other parts
-         of this example.
-        </para>
-       </note>
-      </listitem>
-     </orderedlist>
-    </para>
-
-    <para>
-     As we can see, a complex partitioning scheme could require a
-     substantial amount of DDL. In the above example we would be
-     creating a new partition each month, so it might be wise to write a
-     script that generates the required DDL automatically.
-    </para>
-
-   </sect2>
-
-   <sect2 id="ddl-partitioning-managing-partitions">
-   <title>Managing Partitions</title>
-
-   <para>
-     Normally the set of partitions established when initially
-     defining the table are not intended to remain static. It is
-     common to want to remove old partitions of data and periodically
-     add new partitions for new data. One of the most important
-     advantages of partitioning is precisely that it allows this
-     otherwise painful task to be executed nearly instantaneously by
-     manipulating the partition structure, rather than physically moving large
-     amounts of data around.
-   </para>
-
-   <para>
-     The simplest option for removing old data is simply to drop the partition
-     that is no longer necessary:
-<programlisting>
-DROP TABLE measurement_y2006m02;
-</programlisting>
-     This can very quickly delete millions of records because it doesn't have
-     to individually delete every record.
-   </para>
-
-   <para>
-     Another option that is often preferable is to remove the partition from
-     the partitioned table but retain access to it as a table in its own
-     right:
-<programlisting>
-ALTER TABLE measurement_y2006m02 NO INHERIT measurement;
-</programlisting>
-     This allows further operations to be performed on the data before
-     it is dropped. For example, this is often a useful time to back up
-     the data using <command>COPY</>, <application>pg_dump</>, or
-     similar tools. It might also be a useful time to aggregate data
-     into smaller formats, perform other data manipulations, or run
-     reports.
-   </para>
-
-   <para>
-     Similarly we can add a new partition to handle new data. We can create an
-     empty partition in the partitioned table just as the original partitions
-     were created above:
-
-<programlisting>
-CREATE TABLE measurement_y2008m02 (
-    CHECK ( logdate &gt;= DATE '2008-02-01' AND logdate &lt; DATE '2008-03-01' )
-) INHERITS (measurement);
-</programlisting>
-
-     As an alternative, it is sometimes more convenient to create the
-     new table outside the partition structure, and make it a proper
-     partition later. This allows the data to be loaded, checked, and
-     transformed prior to it appearing in the partitioned table:
-
-<programlisting>
-CREATE TABLE measurement_y2008m02
-  (LIKE measurement INCLUDING DEFAULTS INCLUDING CONSTRAINTS);
-ALTER TABLE measurement_y2008m02 ADD CONSTRAINT y2008m02
-   CHECK ( logdate &gt;= DATE '2008-02-01' AND logdate &lt; DATE '2008-03-01' );
-\copy measurement_y2008m02 from 'measurement_y2008m02'
--- possibly some other data preparation work
-ALTER TABLE measurement_y2008m02 INHERIT measurement;
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2 id="ddl-partitioning-constraint-exclusion">
-   <title>Partitioning and Constraint Exclusion</title>
-
-   <indexterm>
-    <primary>constraint exclusion</primary>
-   </indexterm>
-
-   <para>
-    <firstterm>Constraint exclusion</> is a query optimization technique
-    that improves performance for partitioned tables defined in the
-    fashion described above.  As an example:
-
-<programlisting>
-SET constraint_exclusion = on;
-SELECT count(*) FROM measurement WHERE logdate &gt;= DATE '2008-01-01';
-</programlisting>
-
-    Without constraint exclusion, the above query would scan each of
-    the partitions of the <structname>measurement</> table. With constraint
-    exclusion enabled, the planner will examine the constraints of each
-    partition and try to prove that the partition need not
-    be scanned because it could not contain any rows meeting the query's
-    <literal>WHERE</> clause.  When the planner can prove this, it
-    excludes the partition from the query plan.
-   </para>
-
-   <para>
-    You can use the <command>EXPLAIN</> command to show the difference
-    between a plan with <varname>constraint_exclusion</> on and a plan
-    with it off.  A typical unoptimized plan for this type of table setup is:
-
-<programlisting>
-SET constraint_exclusion = off;
-EXPLAIN SELECT count(*) FROM measurement WHERE logdate &gt;= DATE '2008-01-01';
-
-                                          QUERY PLAN
------------------------------------------------------------------------------------------------
- Aggregate  (cost=158.66..158.68 rows=1 width=0)
-   -&gt;  Append  (cost=0.00..151.88 rows=2715 width=0)
-         -&gt;  Seq Scan on measurement  (cost=0.00..30.38 rows=543 width=0)
-               Filter: (logdate &gt;= '2008-01-01'::date)
-         -&gt;  Seq Scan on measurement_y2006m02 measurement  (cost=0.00..30.38 rows=543 width=0)
-               Filter: (logdate &gt;= '2008-01-01'::date)
-         -&gt;  Seq Scan on measurement_y2006m03 measurement  (cost=0.00..30.38 rows=543 width=0)
-               Filter: (logdate &gt;= '2008-01-01'::date)
-...
-         -&gt;  Seq Scan on measurement_y2007m12 measurement  (cost=0.00..30.38 rows=543 width=0)
-               Filter: (logdate &gt;= '2008-01-01'::date)
-         -&gt;  Seq Scan on measurement_y2008m01 measurement  (cost=0.00..30.38 rows=543 width=0)
-               Filter: (logdate &gt;= '2008-01-01'::date)
-</programlisting>
-
-    Some or all of the partitions might use index scans instead of
-    full-table sequential scans, but the point here is that there
-    is no need to scan the older partitions at all to answer this query.
-    When we enable constraint exclusion, we get a significantly
-    cheaper plan that will deliver the same answer:
-
-<programlisting>
-SET constraint_exclusion = on;
-EXPLAIN SELECT count(*) FROM measurement WHERE logdate &gt;= DATE '2008-01-01';
-                                          QUERY PLAN
------------------------------------------------------------------------------------------------
- Aggregate  (cost=63.47..63.48 rows=1 width=0)
-   -&gt;  Append  (cost=0.00..60.75 rows=1086 width=0)
-         -&gt;  Seq Scan on measurement  (cost=0.00..30.38 rows=543 width=0)
-               Filter: (logdate &gt;= '2008-01-01'::date)
-         -&gt;  Seq Scan on measurement_y2008m01 measurement  (cost=0.00..30.38 rows=543 width=0)
-               Filter: (logdate &gt;= '2008-01-01'::date)
-</programlisting>
-   </para>
-
-   <para>
-    Note that constraint exclusion is driven only by <literal>CHECK</>
-    constraints, not by the presence of indexes.  Therefore it isn't
-    necessary to define indexes on the key columns.  Whether an index
-    needs to be created for a given partition depends on whether you
-    expect that queries that scan the partition will generally scan
-    a large part of the partition or just a small part.  An index will
-    be helpful in the latter case but not the former.
-   </para>
-
-   <para>
-    The default (and recommended) setting of
-    <xref linkend="guc-constraint-exclusion"> is actually neither
-    <literal>on</> nor <literal>off</>, but an intermediate setting
-    called <literal>partition</>, which causes the technique to be
-    applied only to queries that are likely to be working on partitioned
-    tables.  The <literal>on</> setting causes the planner to examine
-    <literal>CHECK</> constraints in all queries, even simple ones that
-    are unlikely to benefit.
-   </para>
-
-   </sect2>
-
-   <sect2 id="ddl-partitioning-alternatives">
-   <title>Alternative Partitioning Methods</title>
-
-    <para>
-     A different approach to redirecting inserts into the appropriate
-     partition table is to set up rules, instead of a trigger, on the
-     master table.  For example:
-
-<programlisting>
-CREATE RULE measurement_insert_y2006m02 AS
-ON INSERT TO measurement WHERE
-    ( logdate &gt;= DATE '2006-02-01' AND logdate &lt; DATE '2006-03-01' )
-DO INSTEAD
-    INSERT INTO measurement_y2006m02 VALUES (NEW.*);
-...
-CREATE RULE measurement_insert_y2008m01 AS
-ON INSERT TO measurement WHERE
-    ( logdate &gt;= DATE '2008-01-01' AND logdate &lt; DATE '2008-02-01' )
-DO INSTEAD
-    INSERT INTO measurement_y2008m01 VALUES (NEW.*);
-</programlisting>
-
-     A rule has significantly more overhead than a trigger, but the overhead
-     is paid once per query rather than once per row, so this method might be
-     advantageous for bulk-insert situations.  In most cases, however, the
-     trigger method will offer better performance.
-    </para>
-
-    <para>
-     Be aware that <command>COPY</> ignores rules.  If you want to
-     use <command>COPY</> to insert data, you'll need to copy into the correct
-     partition table rather than into the master.  <command>COPY</> does fire
-     triggers, so you can use it normally if you use the trigger approach.
-    </para>
-
-    <para>
-     Another disadvantage of the rule approach is that there is no simple
-     way to force an error if the set of rules doesn't cover the insertion
-     date; the data will silently go into the master table instead.
-    </para>
-
-    <para>
-     Partitioning can also be arranged using a <literal>UNION ALL</literal>
-     view, instead of table inheritance.  For example,
-
-<programlisting>
-CREATE VIEW measurement AS
-          SELECT * FROM measurement_y2006m02
-UNION ALL SELECT * FROM measurement_y2006m03
-...
-UNION ALL SELECT * FROM measurement_y2007m11
-UNION ALL SELECT * FROM measurement_y2007m12
-UNION ALL SELECT * FROM measurement_y2008m01;
-</programlisting>
-
-     However, the need to recreate the view adds an extra step to adding and
-     dropping individual partitions of the data set.  In practice this
-     method has little to recommend it compared to using inheritance.
-    </para>
-
-   </sect2>
-
-   <sect2 id="ddl-partitioning-caveats">
-   <title>Caveats</title>
-
-   <para>
-    The following caveats apply to partitioned tables:
-   <itemizedlist>
-    <listitem>
-     <para>
-      There is no automatic way to verify that all of the
-      <literal>CHECK</literal> constraints are mutually
-      exclusive.  It is safer to create code that generates
-      partitions and creates and/or modifies associated objects than
-      to write each by hand.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The schemes shown here assume that the partition key column(s)
-      of a row never change, or at least do not change enough to require
-      it to move to another partition.  An <command>UPDATE</> that attempts
-      to do that will fail because of the <literal>CHECK</> constraints.
-      If you need to handle such cases, you can put suitable update triggers
-      on the partition tables, but it makes management of the structure
-      much more complicated.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      If you are using manual <command>VACUUM</command> or
-      <command>ANALYZE</command> commands, don't forget that
-      you need to run them on each partition individually. A command like:
-<programlisting>
-ANALYZE measurement;
-</programlisting>
-      will only process the master table.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-   </para>
-
-   <para>
-    The following caveats apply to constraint exclusion:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Constraint exclusion only works when the query's <literal>WHERE</>
-      clause contains constants.  A parameterized query will not be
-      optimized, since the planner cannot know which partitions the
-      parameter value might select at run time.  For the same reason,
-      <quote>stable</> functions such as <function>CURRENT_DATE</function>
-      must be avoided.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Keep the partitioning constraints simple, else the planner may not be
-      able to prove that partitions don't need to be visited.  Use simple
-      equality conditions for list partitioning, or simple
-      range tests for range partitioning, as illustrated in the preceding
-      examples.  A good rule of thumb is that partitioning constraints should
-      contain only comparisons of the partitioning column(s) to constants
-      using B-tree-indexable operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      All constraints on all partitions of the master table are examined
-      during constraint exclusion, so large numbers of partitions are likely
-      to increase query planning time considerably.  Partitioning using
-      these techniques will work well with up to perhaps a hundred partitions;
-      don't try to use many thousands of partitions.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="ddl-foreign-data">
-  <title>Foreign Data</title>
-
-   <indexterm>
-    <primary>foreign data</primary>
-   </indexterm>
-   <indexterm>
-    <primary>foreign table</primary>
-   </indexterm>
-
-   <para>
-    <productname>PostgreSQL</productname> implements portions of the SQL/MED
-    specification, allowing you to access data that resides outside
-    PostgreSQL using regular SQL queries.  Such data is referred to as
-    <firstterm>foreign data</>.  (Note that this usage is not to be confused
-    with foreign keys, which are a type of constraint within the database.)
-   </para>
-
-   <para>
-    Foreign data is accessed with help from a
-    <firstterm>foreign data wrapper</firstterm>. A foreign data wrapper is a
-    library that can communicate with an external data source, hiding the
-    details of connecting to the data source and fetching data from it. There
-    are several foreign data wrappers available, which can for example read
-    plain data files residing on the server, or connect to another PostgreSQL
-    instance. If none of the existing foreign data wrappers suit your needs,
-    you can write your own; see <xref linkend="fdwhandler">.
-   </para>
-
-   <para>
-    To access foreign data, you need to create a <firstterm>foreign server</>
-    object, which defines how to connect to a particular external data source,
-    according to the set of options used by a particular foreign data
-    wrapper. Then you need to create one or more <firstterm>foreign
-    tables</firstterm>, which define the structure of the remote data. A
-    foreign table can be used in queries just like a normal table, but a
-    foreign table has no storage in the PostgreSQL server.  Whenever it is
-    used, PostgreSQL asks the foreign data wrapper to fetch the data from the
-    external source.
-   </para>
-
-   <para>
-    Currently, foreign tables are read-only.  This limitation may be fixed
-    in a future release.
-   </para>
- </sect1>
-
-<!-- NOTICE:
-     End of "partitioning"
--->
-<!## end>
-
- <sect1 id="ddl-others">
-  <title>Other Database Objects</title>
-&common;
-  <para>
-   Tables are the central objects in a relational database structure,
-   because they hold your data.  But they are not the only objects
-   that exist in a database.  Many other kinds of objects can be
-   created to make the use and management of the data more efficient
-   or convenient.  They are not discussed in this chapter, but we give
-   you a list here so that you are aware of what is possible:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Views
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Functions and operators
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Data types and domains
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Triggers and rewrite rules
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   Detailed information on
-   these topics appears in <xref linkend="server-programming">.
-  </para>
- </sect1>
-
- <sect1 id="ddl-depend">
-  <title>Dependency Tracking</title>
-
-  <indexterm zone="ddl-depend">
-   <primary>CASCADE</primary>
-   <secondary sortas="DROP">with DROP</secondary>
-  </indexterm>
-
-  <indexterm zone="ddl-depend">
-   <primary>RESTRICT</primary>
-   <secondary sortas="DROP">with DROP</secondary>
-  </indexterm>
-&common;
-  <para>
-   When you create complex database structures involving many tables
-   with foreign key constraints, views, triggers, functions, etc. you
-   implicitly create a net of dependencies between the objects.
-   For instance, a table with a foreign key constraint depends on the
-   table it references.
-  </para>
-
-  <para>
-   To ensure the integrity of the entire database structure,
-   <productname>PostgreSQL</productname> makes sure that you cannot
-   drop objects that other objects still depend on.  For example,
-   attempting to drop the products table we had considered in <xref
-   linkend="ddl-constraints-fk">, with the orders table depending on
-   it, would result in an error message such as this:
-<screen>
-DROP TABLE products;
-
-NOTICE:  constraint orders_product_no_fkey on table orders depends on table products
-ERROR:  cannot drop table products because other objects depend on it
-HINT:  Use DROP ... CASCADE to drop the dependent objects too.
-</screen>
-   The error message contains a useful hint: if you do not want to
-   bother deleting all the dependent objects individually, you can run:
-<screen>
-DROP TABLE products CASCADE;
-</screen>
-   and all the dependent objects will be removed.  In this case, it
-   doesn't remove the orders table, it only removes the foreign key
-   constraint.  (If you want to check what <command>DROP ... CASCADE</> will do,
-   run <command>DROP</> without <literal>CASCADE</> and read the <literal>NOTICE</> messages.)
-  </para>
-
-  <para>
-   All drop commands in <productname>PostgreSQL</productname> support
-   specifying <literal>CASCADE</literal>.  Of course, the nature of
-   the possible dependencies varies with the type of the object.  You
-   can also write <literal>RESTRICT</literal> instead of
-   <literal>CASCADE</literal> to get the default behavior, which is to
-   prevent the dropping of objects that other objects depend on.
-  </para>
-
-  <note>
-   <para>
-    According to the SQL standard, specifying either
-    <literal>RESTRICT</literal> or <literal>CASCADE</literal> is
-    required.  No database system actually enforces that rule, but
-    whether the default behavior is <literal>RESTRICT</literal> or
-    <literal>CASCADE</literal> varies across systems.
-   </para>
-  </note>
-
-  <note>
-   <para>
-    Foreign key constraint dependencies and serial column dependencies
-    from <productname>PostgreSQL</productname> versions prior to 7.3
-    are <emphasis>not</emphasis> maintained or created during the
-    upgrade process.  All other dependency types will be properly
-    created during an upgrade from a pre-7.3 database.
-   </para>
-  </note>
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/dfunc.sgmlin b/doc-xc/src/sgml/dfunc.sgmlin
deleted file mode 100644
index 16a2b1809e..0000000000
--- a/doc-xc/src/sgml/dfunc.sgmlin
+++ /dev/null
@@ -1,368 +0,0 @@
-<!-- doc/src/sgml/dfunc.sgml -->
-
-<sect2 id="dfunc">
- <title>Compiling and Linking Dynamically-loaded Functions</title>
-
-&common;
-
- <para>
-  Before you are able to use your
-<!## PG>
-  <productname>PostgreSQL</productname> extension functions written in
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> extension functions written in
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> extension functions written in
-<!## end>
-  C, they must be compiled and linked in a special way to produce a
-  file that can be dynamically loaded by the server.  To be precise, a
-  <firstterm>shared library</firstterm> needs to be
-  created.<indexterm><primary>shared library</></indexterm>
-
- </para>
-
- <para>
-  For information beyond what is contained in this section
-  you should read the documentation of your
-  operating system, in particular the manual pages for the C compiler,
-  <command>cc</command>, and the link editor, <command>ld</command>.
-<!## PG>
-  In addition, the <productname>PostgreSQL</productname> source code
-<!## end>
-<!## XC>
-  In addition, the <productname>Postgres-XC</productname> source code
-<!## end>
-<!## XL>
-  In addition, the <productname>Postgres-XL</productname> source code
-<!## end>
-  contains several working examples in the
-  <filename>contrib</filename> directory.  If you rely on these
-  examples you will make your modules dependent on the availability
-<!## PG>
-  of the <productname>PostgreSQL</productname> source code, however.
-<!## end>
-<!## XC>
-  of the <productname>Postgres-XC</productname> source code, however.
-<!## end>
-<!## XL>
-  of the <productname>Postgres-XL</productname> source code, however.
-<!## end>
- </para>
-
- <para>
-  Creating shared libraries is generally analogous to linking
-  executables: first the source files are compiled into object files,
-  then the object files are linked together.  The object files need to
-  be created as <firstterm>position-independent code</firstterm>
-  (<acronym>PIC</acronym>),<indexterm><primary>PIC</></> which
-  conceptually means that they can be placed at an arbitrary location
-  in memory when they are loaded by the executable.  (Object files
-  intended for executables are usually not compiled that way.)  The
-  command to link a shared library contains special flags to
-  distinguish it from linking an executable (at least in theory
-  &mdash; on some systems the practice is much uglier).
- </para>
-
- <para>
-  In the following examples we assume that your source code is in a
-  file <filename>foo.c</filename> and we will create a shared library
-  <filename>foo.so</filename>.  The intermediate object file will be
-  called <filename>foo.o</filename> unless otherwise noted.  A shared
-  library can contain more than one object file, but we only use one
-  here.
- </para>
-
-<!--
-  Note: Reading GNU Libtool sources is generally a good way of
-  figuring out this information.  The methods used within PostgreSQL
-  source code are not necessarily ideal.
--->
-
-<!## PG>
-  <variablelist>
-<!## end>
-
-<!## PG>
-   <varlistentry>
-    <term><systemitem class="osname">BSD/OS</></term>
-    <indexterm><primary>BSD/OS</><secondary>shared library</></>
-    <listitem>
-     <para>
-      The compiler flag to create <acronym>PIC</acronym> is
-      <option>-fpic</option>.  The linker flag to create shared
-      libraries is <option>-shared</option>.
-<programlisting>
-gcc -fpic -c foo.c
-ld -shared -o foo.so foo.o
-</programlisting>
-      This is applicable as of version 4.0 of
-      <systemitem class="osname">BSD/OS</>.
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-<!## PG>
-   <varlistentry>
-    <term><systemitem class="osname">FreeBSD</></term>
-    <indexterm><primary>FreeBSD</><secondary>shared library</></>
-    <listitem>
-     <para>
-      The compiler flag to create <acronym>PIC</acronym> is
-      <option>-fpic</option>.  To create shared libraries the compiler
-      flag is <option>-shared</option>.
-<programlisting>
-gcc -fpic -c foo.c
-gcc -shared -o foo.so foo.o
-</programlisting>
-      This is applicable as of version 3.0 of
-      <systemitem class="osname">FreeBSD</>.
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-<!## PG>
-   <varlistentry>
-    <term><systemitem class="osname">HP-UX</></term>
-    <indexterm><primary>HP-UX</><secondary>shared library</></>
-    <listitem>
-     <para>
-      The compiler flag of the system compiler to create
-      <acronym>PIC</acronym> is <option>+z</option>.  When using
-      <application>GCC</application> it's <option>-fpic</option>. The
-      linker flag for shared libraries is <option>-b</option>.  So:
-<programlisting>
-cc +z -c foo.c
-</programlisting>
-      or:
-<programlisting>
-gcc -fpic -c foo.c
-</programlisting>
-      and then:
-<programlisting>
-ld -b -o foo.sl foo.o
-</programlisting>
-      <systemitem class="osname">HP-UX</> uses the extension
-      <filename>.sl</filename> for shared libraries, unlike most other
-      systems.
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-<!## PG>
-   <varlistentry>
-    <term><systemitem class="osname">IRIX</></term>
-    <indexterm><primary>IRIX</><secondary>shared library</></>
-    <listitem>
-     <para>
-      <acronym>PIC</acronym> is the default, no special compiler
-      options are necessary.  The linker option to produce shared
-      libraries is <option>-shared</option>.
-<programlisting>
-cc -c foo.c
-ld -shared -o foo.so foo.o
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><systemitem class="osname">Linux</></term>
-    <indexterm><primary>Linux</><secondary>shared library</></>
-    <listitem>
-     <para>
-      The compiler flag to create <acronym>PIC</acronym> is
-      <option>-fpic</option>.  On some platforms in some situations
-      <option>-fPIC</option> must be used if <option>-fpic</option>
-      does not work.  Refer to the GCC manual for more information.
-      The compiler flag to create a shared library is
-      <option>-shared</option>.  A complete example looks like this:
-<programlisting>
-cc -fpic -c foo.c
-cc -shared -o foo.so foo.o
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-<!## PG>
-   <varlistentry>
-    <term><systemitem class="osname">MacOS X</></term>
-    <indexterm><primary>MacOS X</><secondary>shared library</></>
-    <listitem>
-     <para>
-      Here is an example.  It assumes the developer tools are installed.
-<programlisting>
-cc -c foo.c
-cc -bundle -flat_namespace -undefined suppress -o foo.so foo.o
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><systemitem class="osname">NetBSD</></term>
-    <indexterm><primary>NetBSD</><secondary>shared library</></>
-    <listitem>
-     <para>
-      The compiler flag to create <acronym>PIC</acronym> is
-      <option>-fpic</option>.  For <acronym>ELF</acronym> systems, the
-      compiler with the flag <option>-shared</option> is used to link
-      shared libraries.  On the older non-ELF systems, <literal>ld
-      -Bshareable</literal> is used.
-<programlisting>
-gcc -fpic -c foo.c
-gcc -shared -o foo.so foo.o
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-<!## PG>
-   <varlistentry>
-    <term><systemitem class="osname">OpenBSD</></term>
-    <indexterm><primary>OpenBSD</><secondary>shared library</></>
-    <listitem>
-     <para>
-      The compiler flag to create <acronym>PIC</acronym> is
-      <option>-fpic</option>.  <literal>ld -Bshareable</literal> is
-      used to link shared libraries.
-<programlisting>
-gcc -fpic -c foo.c
-ld -Bshareable -o foo.so foo.o
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><systemitem class="osname">Solaris</></term>
-    <indexterm><primary>Solaris</><secondary>shared library</></>
-    <listitem>
-     <para>
-      The compiler flag to create <acronym>PIC</acronym> is
-      <option>-KPIC</option> with the Sun compiler and
-      <option>-fpic</option> with <application>GCC</>.  To
-      link shared libraries, the compiler option is
-      <option>-G</option> with either compiler or alternatively
-      <option>-shared</option> with <application>GCC</>.
-<programlisting>
-cc -KPIC -c foo.c
-cc -G -o foo.so foo.o
-</programlisting>
-      or
-<programlisting>
-gcc -fpic -c foo.c
-gcc -G -o foo.so foo.o
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-<!## PG>
-   <varlistentry>
-    <term><systemitem class="osname">Tru64 UNIX</></term>
-    <indexterm><primary>Tru64 UNIX</><secondary>shared library</></>
-    <indexterm><primary>Digital UNIX</><see>Tru64 UNIX</></>
-    <listitem>
-     <para>
-      <acronym>PIC</acronym> is the default, so the compilation command
-      is the usual one.  <command>ld</command> with special options is
-      used to do the linking.
-<programlisting>
-cc -c foo.c
-ld -shared -expect_unresolved '*' -o foo.so foo.o
-</programlisting>
-      The same procedure is used with GCC instead of the system
-      compiler; no special options are required.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><systemitem class="osname">UnixWare</></term>
-    <indexterm><primary>UnixWare</><secondary>shared library</></>
-    <listitem>
-     <para>
-      The compiler flag to create <acronym>PIC</acronym> is <option>-K
-      PIC</option> with the SCO compiler and <option>-fpic</option>
-      with <productname>GCC</productname>.  To link shared libraries,
-      the compiler option is <option>-G</option> with the SCO compiler
-      and <option>-shared</option> with
-      <productname>GCC</productname>.
-<programlisting>
-cc -K PIC -c foo.c
-cc -G -o foo.so foo.o
-</programlisting>
-      or
-<programlisting>
-gcc -fpic -c foo.c
-gcc -shared -o foo.so foo.o
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-<!## PG>
-  </variablelist>
-<!## end>
-
- <tip>
-  <para>
-   If this is too complicated for you, you should consider using
-   <ulink url="http://www.gnu.org/software/libtool/">
-   <productname>GNU Libtool</productname></ulink>,
-   which hides the platform differences behind a uniform interface.
-  </para>
- </tip>
-
- <para>
-  The resulting shared library file can then be loaded into
-<!## PG>
-  <productname>PostgreSQL</productname>.  When specifying the file name
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname>.  When specifying the file name
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname>.  When specifying the file name
-<!## end>
-  to the <command>CREATE FUNCTION</command> command, one must give it
-  the name of the shared library file, not the intermediate object file.
-  Note that the system's standard shared-library extension (usually
-  <literal>.so</literal> or <literal>.sl</literal>) can be omitted from
-  the <command>CREATE FUNCTION</command> command, and normally should
-  be omitted for best portability.
- </para>
-
- <para>
-  Refer back to <xref linkend="xfunc-c-dynload"> about where the
-  server expects to find the shared library files.
- </para>
-
-<!--
-Under AIX, object files are compiled normally but building the shared
-library requires a couple of steps.  First, create the object file:
-.nf
-cc <other flags> -c foo.c
-.fi
-You must then create a symbol \*(lqexports\*(rq file for the object
-file:
-.nf
-mkldexport foo.o `pwd` &gt; foo.exp
-.fi
-Finally, you can create the shared library:
-.nf
-ld <other flags> -H512 -T512 -o foo.so -e _nostart \e
-   -bI:.../lib/postgres.exp -bE:foo.exp foo.o \e
-   -lm -lc 2>/dev/null
-.fi
-  -->
-
-</sect2>
diff --git a/doc-xc/src/sgml/dict-int.sgmlin b/doc-xc/src/sgml/dict-int.sgmlin
deleted file mode 100644
index 132be1ac2b..0000000000
--- a/doc-xc/src/sgml/dict-int.sgmlin
+++ /dev/null
@@ -1,94 +0,0 @@
-<!-- doc/src/sgml/dict-int.sgml -->
-
-<sect1 id="dict-int" xreflabel="dict_int">
- <title>dict_int</title>
-
- <indexterm zone="dict-int">
-  <primary>dict_int</primary>
- </indexterm>
-
-&pgnotice;
-
-
- <para>
-  <filename>dict_int</> is an example of an add-on dictionary template
-  for full-text search.  The motivation for this example dictionary is to
-  control the indexing of integers (signed and unsigned), allowing such
-  numbers to be indexed while preventing excessive growth in the number of
-  unique words, which greatly affects the performance of searching.
- </para>
-
- <sect2>
-  <title>Configuration</title>
-
-&pgnotice;
-
-
-  <para>
-   The dictionary accepts two options:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     The <literal>maxlen</> parameter specifies the maximum number of
-     digits allowed in an integer word.  The default value is 6.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     The <literal>rejectlong</> parameter specifies whether an overlength
-     integer should be truncated or ignored.  If <literal>rejectlong</> is
-     <literal>false</> (the default), the dictionary returns the first
-     <literal>maxlen</> digits of the integer. If <literal>rejectlong</> is
-     <literal>true</>, the dictionary treats an overlength integer as a stop
-     word, so that it will not be indexed.  Note that this also means that
-     such an integer cannot be searched for.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect2>
-
- <sect2>
-  <title>Usage</title>
-
-&pgnotice;
-
-
-  <para>
-   Installing the <literal>dict_int</> extension creates a text search
-   template <literal>intdict_template</> and a dictionary <literal>intdict</>
-   based on it, with the default parameters.  You can alter the
-   parameters, for example
-
-<programlisting>
-mydb# ALTER TEXT SEARCH DICTIONARY intdict (MAXLEN = 4, REJECTLONG = true);
-ALTER TEXT SEARCH DICTIONARY
-</programlisting>
-
-   or create new dictionaries based on the template.
-  </para>
-
-  <para>
-   To test the dictionary, you can try
-
-<programlisting>
-mydb# select ts_lexize('intdict', '12345678');
- ts_lexize
------------
- {123456}
-</programlisting>
-
-   but real-world usage will involve including it in a text search
-   configuration as described in <xref linkend="textsearch">.
-   That might look like this:
-
-<programlisting>
-ALTER TEXT SEARCH CONFIGURATION english
-    ALTER MAPPING FOR int, uint WITH intdict;
-</programlisting>
-
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/dict-xsyn.sgmlin b/doc-xc/src/sgml/dict-xsyn.sgmlin
deleted file mode 100644
index 242d30760f..0000000000
--- a/doc-xc/src/sgml/dict-xsyn.sgmlin
+++ /dev/null
@@ -1,158 +0,0 @@
-<!-- doc/src/sgml/dict-xsyn.sgml -->
-
-<sect1 id="dict-xsyn" xreflabel="dict_xsyn">
- <title>dict_xsyn</title>
-
- <indexterm zone="dict-xsyn">
-  <primary>dict_xsyn</primary>
- </indexterm>
-
-&pgnotice;
-
-
- <para>
-  <filename>dict_xsyn</> (Extended Synonym Dictionary) is an example of an
-  add-on dictionary template for full-text search.  This dictionary type
-  replaces words with groups of their synonyms, and so makes it possible to
-  search for a word using any of its synonyms.
- </para>
-
- <sect2>
-  <title>Configuration</title>
-
-&pgnotice;
-
-
-  <para>
-   A <literal>dict_xsyn</> dictionary accepts the following options:
-  </para>
-  <itemizedlist>
-   <listitem>
-    <para>
-     <literal>matchorig</> controls whether the original word is accepted by
-     the dictionary. Default is <literal>true</>.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <literal>matchsynonyms</> controls whether the synonyms are
-     accepted by the dictionary. Default is <literal>false</>.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <literal>keeporig</> controls whether the original word is included in
-     the dictionary's output. Default is <literal>true</>.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <literal>keepsynonyms</> controls whether the synonyms are included in
-     the dictionary's output. Default is <literal>true</>.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <literal>rules</> is the base name of the file containing the list of
-     synonyms.  This file must be stored in
-     <filename>$SHAREDIR/tsearch_data/</> (where <literal>$SHAREDIR</> means
-     the <productname>PostgreSQL</> installation's shared-data directory).
-     Its name must end in <literal>.rules</> (which is not to be included in
-     the <literal>rules</> parameter).
-    </para>
-   </listitem>
-  </itemizedlist>
-  <para>
-   The rules file has the following format:
-  </para>
-  <itemizedlist>
-   <listitem>
-    <para>
-     Each line represents a group of synonyms for a single word, which is
-     given first on the line. Synonyms are separated by whitespace, thus:
-<programlisting>
-word syn1 syn2 syn3
-</programlisting>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     The sharp (<literal>#</>) sign is a comment delimiter. It may appear at
-     any position in a line.  The rest of the line will be skipped.
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   Look at <filename>xsyn_sample.rules</>, which is installed in
-   <filename>$SHAREDIR/tsearch_data/</>, for an example.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Usage</title>
-
-&pgnotice;
-
-
-  <para>
-   Installing the <literal>dict_xsyn</> extension creates a text search
-   template <literal>xsyn_template</> and a dictionary <literal>xsyn</>
-   based on it, with default parameters.  You can alter the
-   parameters, for example
-
-<programlisting>
-mydb# ALTER TEXT SEARCH DICTIONARY xsyn (RULES='my_rules', KEEPORIG=false);
-ALTER TEXT SEARCH DICTIONARY
-</programlisting>
-
-   or create new dictionaries based on the template.
-  </para>
-
-  <para>
-   To test the dictionary, you can try
-
-<programlisting>
-mydb=# SELECT ts_lexize('xsyn', 'word');
-      ts_lexize
------------------------
- {syn1,syn2,syn3}
-
-mydb# ALTER TEXT SEARCH DICTIONARY xsyn (RULES='my_rules', KEEPORIG=true);
-ALTER TEXT SEARCH DICTIONARY
-
-mydb=# SELECT ts_lexize('xsyn', 'word');
-      ts_lexize
------------------------
- {word,syn1,syn2,syn3}
-
-mydb# ALTER TEXT SEARCH DICTIONARY xsyn (RULES='my_rules', KEEPORIG=false, MATCHSYNONYMS=true);
-ALTER TEXT SEARCH DICTIONARY
-
-mydb=# SELECT ts_lexize('xsyn', 'syn1');
-      ts_lexize
------------------------
- {syn1,syn2,syn3}
-
-mydb# ALTER TEXT SEARCH DICTIONARY xsyn (RULES='my_rules', KEEPORIG=true, MATCHORIG=false, KEEPSYNONYMS=false);
-ALTER TEXT SEARCH DICTIONARY
-
-mydb=# SELECT ts_lexize('xsyn', 'syn1');
-      ts_lexize
------------------------
- {word}
-</programlisting>
-
-   Real-world usage will involve including it in a text search
-   configuration as described in <xref linkend="textsearch">.
-   That might look like this:
-
-<programlisting>
-ALTER TEXT SEARCH CONFIGURATION english
-    ALTER MAPPING FOR word, asciiword WITH xsyn, english_stem;
-</programlisting>
-
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/diskusage.sgmlin b/doc-xc/src/sgml/diskusage.sgmlin
deleted file mode 100644
index 6f5595bc93..0000000000
--- a/doc-xc/src/sgml/diskusage.sgmlin
+++ /dev/null
@@ -1,147 +0,0 @@
-<!-- doc/src/sgml/diskusage.sgml -->
-
-<chapter id="diskusage">
- <title>Monitoring Disk Usage</title>
-
-&pgnotice;
-
- <para>
-  This chapter discusses how to monitor the disk usage of a
-  <productname>PostgreSQL</> database system.
- </para>
-
- <sect1 id="disk-usage">
-  <title>Determining Disk Usage</title>
-
-  <indexterm zone="disk-usage">
-   <primary>disk usage</primary>
-  </indexterm>
-
-  <para>
-   Each table has a primary heap disk file where most of the data is
-   stored. If the table has any columns with potentially-wide values,
-   there also might be a <acronym>TOAST</> file associated with the table,
-   which is used to store values too wide to fit comfortably in the main
-   table (see <xref linkend="storage-toast">).  There will be one index on the
-   <acronym>TOAST</> table, if present. There also might be indexes associated
-   with the base table.  Each table and index is stored in a separate disk
-   file &mdash; possibly more than one file, if the file would exceed one
-   gigabyte.  Naming conventions for these files are described in <xref
-   linkend="storage-file-layout">.
-  </para>
-
-  <para>
-   You can monitor disk space in three ways:
-   using the SQL functions listed in <xref linkend="functions-admin-dbsize">,
-   using the <xref linkend="oid2name"> module, or
-   using manual inspection of the system catalogs.
-   The SQL functions are the easiest to use and are generally recommended.
-   The remainder of this section shows how to do it by inspection of the
-   system catalogs.
-  </para>
-
-  <para>
-   Using <application>psql</> on a recently vacuumed or analyzed database,
-   you can issue queries to see the disk usage of any table:
-<programlisting>
-SELECT pg_relation_filepath(oid), relpages FROM pg_class WHERE relname = 'customer';
-
- pg_relation_filepath | relpages 
-----------------------+----------
- base/16384/16806     |       60
-(1 row)
-</programlisting>
-   Each page is typically 8 kilobytes. (Remember, <structfield>relpages</>
-   is only updated by <command>VACUUM</>, <command>ANALYZE</>, and
-   a few DDL commands such as <command>CREATE INDEX</>.)  The file path name
-   is of interest if you want to examine the table's disk file directly.
-  </para>
-
-  <para>
-   To show the space used by <acronym>TOAST</> tables, use a query
-   like the following:
-<programlisting>
-SELECT relname, relpages
-FROM pg_class,
-     (SELECT reltoastrelid
-      FROM pg_class
-      WHERE relname = 'customer') AS ss
-WHERE oid = ss.reltoastrelid OR
-      oid = (SELECT reltoastidxid
-             FROM pg_class
-             WHERE oid = ss.reltoastrelid)
-ORDER BY relname;
-
-       relname        | relpages 
-----------------------+----------
- pg_toast_16806       |        0
- pg_toast_16806_index |        1
-</programlisting>
-  </para>
-
-  <para>
-   You can easily display index sizes, too:
-<programlisting>
-SELECT c2.relname, c2.relpages
-FROM pg_class c, pg_class c2, pg_index i
-WHERE c.relname = 'customer' AND
-      c.oid = i.indrelid AND
-      c2.oid = i.indexrelid
-ORDER BY c2.relname;
-
-       relname        | relpages 
-----------------------+----------
- customer_id_indexdex |       26
-</programlisting>
-  </para>
-
-  <para>
-   It is easy to find your largest tables and indexes using this
-   information:
-<programlisting>
-SELECT relname, relpages
-FROM pg_class
-ORDER BY relpages DESC;
-
-       relname        | relpages 
-----------------------+----------
- bigtable             |     3290
- customer             |     3144
-</programlisting>
-  </para>
- </sect1>
-
- <sect1 id="disk-full">
-  <title>Disk Full Failure</title>
-&pgnotice;
-
-  <para>
-   The most important disk monitoring task of a database administrator
-   is to make sure the disk doesn't become full.  A filled data disk will
-   not result in data corruption, but it might prevent useful activity
-   from occurring. If the disk holding the WAL files grows full, database
-   server panic and consequent shutdown might occur.
-  </para>
-
-  <para>
-   If you cannot free up additional space on the disk by deleting
-   other things, you can move some of the database files to other file
-   systems by making use of tablespaces. See <xref
-   linkend="manage-ag-tablespaces"> for more information about that.
-  </para>
-
-  <tip>
-   <para>
-    Some file systems perform badly when they are almost full, so do
-    not wait until the disk is completely full to take action.
-   </para>
-  </tip>
-
-  <para>
-   If your system supports per-user disk quotas, then the database
-   will naturally be subject to whatever quota is placed on the user
-   the server runs as.  Exceeding the quota will have the same bad
-   effects as running out of disk space entirely.
-  </para>
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/dml.sgmlin b/doc-xc/src/sgml/dml.sgmlin
deleted file mode 100644
index 8c4507c732..0000000000
--- a/doc-xc/src/sgml/dml.sgmlin
+++ /dev/null
@@ -1,278 +0,0 @@
-<!-- doc/src/sgml/dml.sgml -->
-
-<chapter id="dml">
- <title>Data Manipulation</title>
-
- <remark>
-  This chapter is still quite incomplete.
- </remark>
-
- <para>
-  The previous chapter discussed how to create tables and other
-  structures to hold your data.  Now it is time to fill the tables
-  with data.  This chapter covers how to insert, update, and delete
-  table data.  The chapter
-  after this will finally explain how to extract your long-lost data
-  from the database.
- </para>
-
- <sect1 id="dml-insert">
-  <title>Inserting Data</title>
-
-  <indexterm zone="dml-insert">
-   <primary>inserting</primary>
-  </indexterm>
-
-  <indexterm zone="dml-insert">
-   <primary>INSERT</primary>
-  </indexterm>
-&common;
-  <para>
-   When a table is created, it contains no data.  The first thing to
-   do before a database can be of much use is to insert data.  Data is
-   conceptually inserted one row at a time.  Of course you can also
-   insert more than one row, but there is no way to insert less than
-   one row.  Even if you know only some column values, a
-   complete row must be created.
-  </para>
-
-  <para>
-   To create a new row, use the <xref linkend="sql-insert">
-   command.  The command requires the
-   table name and column values.  For
-   example, consider the products table from <xref linkend="ddl">:
-<programlisting>
-CREATE TABLE products (
-    product_no integer,
-    name text,
-    price numeric
-);
-</programlisting>
-   An example command to insert a row would be:
-<programlisting>
-INSERT INTO products VALUES (1, 'Cheese', 9.99);
-</programlisting>
-   The data values are listed in the order in which the columns appear
-   in the table, separated by commas.  Usually, the data values will
-   be literals (constants), but scalar expressions are also allowed.
-  </para>
-
-  <para>
-   The above syntax has the drawback that you need to know the order
-   of the columns in the table.  To avoid this you can also list the
-   columns explicitly.  For example, both of the following commands
-   have the same effect as the one above:
-<programlisting>
-INSERT INTO products (product_no, name, price) VALUES (1, 'Cheese', 9.99);
-INSERT INTO products (name, price, product_no) VALUES ('Cheese', 9.99, 1);
-</programlisting>
-   Many users consider it good practice to always list the column
-   names.
-  </para>
-
-  <para>
-   If you don't have values for all the columns, you can omit some of
-   them.  In that case, the columns will be filled with their default
-   values.  For example:
-<programlisting>
-INSERT INTO products (product_no, name) VALUES (1, 'Cheese');
-INSERT INTO products VALUES (1, 'Cheese');
-</programlisting>
-<!## PG>
-   The second form is a <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   The second form is a <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   The second form is a <productname>Postgres-XL</productname>
-<!## end>
-   extension.  It fills the columns from the left with as many values
-   as are given, and the rest will be defaulted.
-  </para>
-
-  <para>
-   For clarity, you can also request default values explicitly, for
-   individual columns or for the entire row:
-<programlisting>
-INSERT INTO products (product_no, name, price) VALUES (1, 'Cheese', DEFAULT);
-INSERT INTO products DEFAULT VALUES;
-</programlisting>
-  </para>
-
-  <para>
-   You can insert multiple rows in a single command:
-<programlisting>
-INSERT INTO products (product_no, name, price) VALUES
-    (1, 'Cheese', 9.99),
-    (2, 'Bread', 1.99),
-    (3, 'Milk', 2.99);
-</programlisting>
-  </para>
-
-  <tip>
-   <para>
-    When inserting a lot of data at the same time, considering using
-    the <xref linkend="sql-copy"> command.
-    It is not as flexible as the <xref linkend="sql-insert">
-    command, but is more efficient. Refer
-    to <xref linkend="populate"> for more information on improving
-    bulk loading performance.
-   </para>
-  </tip>
- </sect1>
-
- <sect1 id="dml-update">
-  <title>Updating Data</title>
-
-  <indexterm zone="dml-update">
-   <primary>updating</primary>
-  </indexterm>
-
-  <indexterm zone="dml-update">
-   <primary>UPDATE</primary>
-  </indexterm>
-&common;
-  <para>
-   The modification of data that is already in the database is
-   referred to as updating.  You can update individual rows, all the
-   rows in a table, or a subset of all rows.  Each column can be
-   updated separately; the other columns are not affected.
-  </para>
-
-  <para>
-   To update existing rows, use the <xref linkend="sql-update">
-   command.  This requires
-   three pieces of information:
-   <orderedlist spacing="compact">
-    <listitem>
-     <para>The name of the table and column to update</para>
-    </listitem>
-
-    <listitem>
-     <para>The new value of the column</para>
-    </listitem>
-
-    <listitem>
-     <para>Which row(s) to update</para>
-    </listitem>
-   </orderedlist>
-  </para>
-
-  <para>
-   Recall from <xref linkend="ddl"> that SQL does not, in general,
-   provide a unique identifier for rows.  Therefore it is not
-   always possible to directly specify which row to update.
-   Instead, you specify which conditions a row must meet in order to
-   be updated.  Only if you have a primary key in the table (independent of
-   whether you declared it or not) can you reliably address individual rows
-   by choosing a condition that matches the primary key.
-   Graphical database access tools rely on this fact to allow you to
-   update rows individually.
-  </para>
-
-  <para>
-   For example, this command updates all products that have a price of
-   5 to have a price of 10:
-<programlisting>
-UPDATE products SET price = 10 WHERE price = 5;
-</programlisting>
-    This might cause zero, one, or many rows to be updated.  It is not
-    an error to attempt an update that does not match any rows.
-  </para>
-
-  <para>
-   Let's look at that command in detail. First is the key word
-   <literal>UPDATE</literal> followed by the table name.  As usual,
-   the table name can be schema-qualified, otherwise it is looked up
-   in the path.  Next is the key word <literal>SET</literal> followed
-   by the column name, an equal sign, and the new column value.  The
-   new column value can be any scalar expression, not just a constant.
-   For example, if you want to raise the price of all products by 10%
-   you could use:
-<programlisting>
-UPDATE products SET price = price * 1.10;
-</programlisting>
-   As you see, the expression for the new value can refer to the existing
-   value(s) in the row.  We also left out the <literal>WHERE</literal> clause.
-   If it is omitted, it means that all rows in the table are updated.
-   If it is present, only those rows that match the
-   <literal>WHERE</literal> condition are updated.  Note that the equals
-   sign in the <literal>SET</literal> clause is an assignment while
-   the one in the <literal>WHERE</literal> clause is a comparison, but
-   this does not create any ambiguity.  Of course, the
-   <literal>WHERE</literal> condition does
-   not have to be an equality test.  Many other operators are
-   available (see <xref linkend="functions">).  But the expression
-   needs to evaluate to a Boolean result.
-  </para>
-
-  <para>
-   You can update more than one column in an
-   <command>UPDATE</command> command by listing more than one
-   assignment in the <literal>SET</literal> clause.  For example:
-<programlisting>
-UPDATE mytable SET a = 5, b = 3, c = 1 WHERE a &gt; 0;
-</programlisting>
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   Please remember that <productname>Postgres-XC</> does not allow to
-   modify the value of distribution column.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please remember that <productname>Postgres-XL</> does not allow to
-   modify the value of distribution column.
-  </para>
-<!## end>
- </sect1>
-
- <sect1 id="dml-delete">
-  <title>Deleting Data</title>
-
-  <indexterm zone="dml-delete">
-   <primary>deleting</primary>
-  </indexterm>
-
-  <indexterm zone="dml-delete">
-   <primary>DELETE</primary>
-  </indexterm>
-&common;
-  <para>
-   So far we have explained how to add data to tables and how to
-   change data.  What remains is to discuss how to remove data that is
-   no longer needed.  Just as adding data is only possible in whole
-   rows, you can only remove entire rows from a table.  In the
-   previous section we explained that SQL does not provide a way to
-   directly address individual rows.  Therefore, removing rows can
-   only be done by specifying conditions that the rows to be removed
-   have to match.  If you have a primary key in the table then you can
-   specify the exact row.  But you can also remove groups of rows
-   matching a condition, or you can remove all rows in the table at
-   once.
-  </para>
-
-  <para>
-   You use the <xref linkend="sql-delete">
-   command to remove rows; the syntax is very similar to the
-   <command>UPDATE</command> command.  For instance, to remove all
-   rows from the products table that have a price of 10, use:
-<programlisting>
-DELETE FROM products WHERE price = 10;
-</programlisting>
-  </para>
-
-  <para>
-   If you simply write:
-<programlisting>
-DELETE FROM products;
-</programlisting>
-   then all rows in the table will be deleted!  Caveat programmer.
-  </para>
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/docguide.sgmlin b/doc-xc/src/sgml/docguide.sgmlin
deleted file mode 100644
index 04e8005d11..0000000000
--- a/doc-xc/src/sgml/docguide.sgmlin
+++ /dev/null
@@ -1,1482 +0,0 @@
-<!-- doc/src/sgml/docguide.sgml -->
-
-<appendix id="docguide">
- <title>Documentation</title>
-
-&common;
-
- <para>
-<!## PG>
-  <productname>PostgreSQL</productname> has four primary documentation
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> has four primary documentation
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> has four primary documentation
-<!## end>
-  formats:
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Plain text, for pre-installation information
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <acronym>HTML</acronym>, for on-line browsing and reference
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     PDF or PostScript, for printing
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     man pages, for quick reference.
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  Additionally, a number of plain-text <filename>README</filename> files can
-<!## PG>
-  be found throughout the <productname>PostgreSQL</productname> source tree,
-<!## end>
-<!## XC>
-  be found throughout the <productname>Postgres-XC</productname> source tree,
-<!## end>
-<!## XL>
-  be found throughout the <productname>Postgres-XL</productname> source tree,
-<!## end>
-  documenting various implementation issues.
- </para>
-
- <para>
-  <acronym>HTML</acronym> documentation and man pages are part of a
-  standard distribution and are installed by default.  PDF and
-  PostScript format documentation is available separately for
-  download.
- </para>
-
- <sect1 id="docguide-docbook">
-  <title>DocBook</title>
-&common;
-  <para>
-   The documentation sources are written in
-   <firstterm>DocBook</firstterm>, which is a markup language
-   superficially similar to <acronym>HTML</acronym>.  Both of these
-   languages are applications of the <firstterm>Standard Generalized
-   Markup Language</firstterm>, <acronym>SGML</acronym>, which is
-   essentially a language for describing other languages.  In what
-   follows, the terms DocBook and <acronym>SGML</acronym> are both
-   used, but technically they are not interchangeable.
-  </para>
-
-  <para>
-  <productname>DocBook</productname> allows an author to specify the
-   structure and content of a technical document without worrying
-   about presentation details.  A document style defines how that
-   content is rendered into one of several final forms.  DocBook is
-   maintained by the <ulink url="http://www.oasis-open.org">
-   OASIS group</ulink>.  The <ulink url="http://www.oasis-open.org/docbook/">
-   official DocBook site</ulink> has good introductory and reference documentation and
-   a complete O'Reilly book for your online reading pleasure.  The
-   <ulink url="http://newbiedoc.sourceforge.net/metadoc/docbook-guide.html">
-   NewbieDoc Docbook Guide</ulink> is very helpful for beginners.
-   The <ulink url="http://www.freebsd.org/docproj/docproj.html">
-   FreeBSD Documentation Project</ulink> also uses DocBook and has some good
-   information, including a number of style guidelines that might be
-   worth considering.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   To make it simpler to compare original <productname>PostgreSQL</>
-   documentation with <productname>Postgres-XC</>, we decided to
-   generate <productname>DocBook</> file from new file prefixed
-   as <literal>sgmlin</>.  <literal>sgmlin</> file is
-   essentially <productname>DocBook</> file with additional
-   tags <literal>&lt;!## tag&gt;</> and <literal>&lt!## end&gt;</>.
-   The former is a start tag and the latter is the stop tag.  These
-   tags should occupy whole line.  No other tags or CCDATA should
-   appear in the same line.  The tool <command>makesgml</> takes these
-   file, filter only <productname>Postgres-XC</> specific contents and
-   generate target <literal>sgml</> files.
-  </para>
-  <para>
-   <literal>Makefile</> has been modified to accommodate these changes.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   To make it simpler to compare original <productname>PostgreSQL</>
-   documentation with <productname>Postgres-XL</>, we decided to
-   generate <productname>DocBook</> file from new file prefixed
-   as <literal>sgmlin</>.  <literal>sgmlin</> file is
-   essentially <productname>DocBook</> file with additional
-   tags <literal>&lt;!## tag&gt;</> and <literal>&lt!## end&gt;</>.
-   The former is a start tag and the latter is the stop tag.  These
-   tags should occupy whole line.  No other tags or CCDATA should
-   appear in the same line.  The tool <command>makesgml</> takes these
-   file, filter only <productname>Postgres-XL</> specific contents and
-   generate target <literal>sgml</> files.
-  </para>
-  <para>
-   <literal>Makefile</> has been modified to accommodate these changes.
-  </para>
-<!## end>
- </sect1>
-
-
- <sect1 id="docguide-toolsets">
-  <title>Tool Sets</title>
-
-&common;
-  <para>
-   The following tools are used to process the documentation.  Some
-   might be optional, as noted.
-
-   <variablelist>
-    <varlistentry>
-     <term><ulink url="http://www.oasis-open.org/docbook/">DocBook DTD</ulink></term>
-     <listitem>
-      <para>
-       This is the definition of DocBook itself.  We currently use
-       version 4.2; you cannot use later or earlier versions.  You
-       need the <acronym>SGML</acronym> variant of the DocBook DTD,
-       but to build man pages you also need the <acronym>XML</acronym>
-       variant of the same version.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><ulink url="http://www.oasis-open.org/cover/ISOEnts.zip">ISO 8879 character entities</ulink></term>
-     <listitem>
-      <para>
-       These are required by DocBook but are distributed separately
-       because they are maintained by ISO.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><ulink url="http://wiki.docbook.org/topic/DocBookDssslStylesheets">DocBook DSSSL Stylesheets</ulink></term>
-     <listitem>
-      <para>
-       These contain the processing instructions for converting the
-       DocBook sources to other formats, such as
-       <acronym>HTML</acronym>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><ulink url="http://wiki.docbook.org/topic/DocBookXslStylesheets">DocBook XSL Stylesheets</ulink></term>
-     <listitem>
-      <para>
-       This is another stylesheet for converting DocBook to other
-       formats.  We currently use this to produce man pages and
-       optionally HTMLHelp.  You can also use this toolchain to
-<!## PG>
-       produce HTML or PDF output, but official PostgreSQL releases
-<!## end>
-<!## XC>
-       produce HTML or PDF output, but official Postgres-XC releases
-<!## end>
-<!## XL>
-       produce HTML or PDF output, but official Postgres-XL releases
-<!## end>
-       use the DSSSL stylesheets for that.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><ulink url="http://openjade.sourceforge.net">OpenJade</ulink></term>
-     <listitem>
-      <para>
-       This is the base package of <acronym>SGML</acronym> processing.
-       It contains an <acronym>SGML</acronym> parser, a
-       <acronym>DSSSL</acronym> processor (that is, a program to
-       convert <acronym>SGML</acronym> to other formats using
-       <acronym>DSSSL</acronym> stylesheets), as well as a number of
-       related tools.  <productname>Jade</productname> is now being
-       maintained by the OpenJade group, no longer by James Clark.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><ulink url="http://xmlsoft.org/XSLT/">Libxslt</ulink> for <command>xsltproc</command></term>
-     <listitem>
-      <para>
-       This is the processing tool to use with the XSLT stylesheets
-       (like <command>jade</command> is the processing tool for DSSSL
-       stylesheets).
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><ulink url="http://jadetex.sourceforge.net">JadeTeX</ulink></term>
-     <listitem>
-      <para>
-       If you want to, you can also install
-       <productname>JadeTeX</productname> to use
-       <productname>TeX</productname> as a formatting backend for
-       <productname>Jade</productname>.
-       <application>JadeTeX</application> can create PostScript or
-       <acronym>PDF</acronym> files (the latter with bookmarks).
-      </para>
-
-      <para>
-       However, the output from <application>JadeTeX</application> is
-       inferior to what you get from the <acronym>RTF</acronym>
-       backend.  Particular problem areas are tables and various
-       artifacts of vertical and horizontal spacing.  Also, there is
-       no opportunity to manually polish the results.
-      </para>
-     </listitem>
-    </varlistentry>
-
-<!## XC>
-    <varlistentry>
-     <term>makesgml</term>
-
-     <listitem>
-&xconly;
-      <para>
-       <command>makesgml</> is <productname>Postgres-XC</> specific
-       tool to generate <literal>sgml</> file from <literal>sgmlin</>
-       file.  As described above, <literal>sgmlin</> file contains
-       both <productname>PostgreSQL</> and <productname>Postgres-XC</>
-       documentation source to make it simpler to deal with future
-       revision of original <productname>PostgreSQL</> documentation.
-      </para>
-      <para>
-       <command>makesgml</> source is included in the document source.
-       Build the binary and place this to appropriate path.
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-<!## end>
-<!## XL>
-    <varlistentry>
-     <term>makesgml</term>
-
-     <listitem>
-&xlonly;
-      <para>
-       <command>makesgml</> is <productname>Postgres-XL</> specific
-       tool to generate <literal>sgml</> file from <literal>sgmlin</>
-       file.  As described above, <literal>sgmlin</> file contains
-       both <productname>PostgreSQL</> and <productname>Postgres-XL</>
-       documentation source to make it simpler to deal with future
-       revision of original <productname>PostgreSQL</> documentation.
-      </para>
-      <para>
-       <command>makesgml</> source is included in the document source.
-       Build the binary and place this to appropriate path.
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-<!## end>
-
-   </variablelist>
-  </para>
-
-  <para>
-   We have documented experience with several installation methods for
-   the various tools that are needed to process the documentation.
-   These will be described below.  There might be some other packaged
-   distributions for these tools. Please report package status to the
-   documentation mailing list, and we will include that information
-   here.
-  </para>
-
-  <sect2>
-   <title><productname>Linux</productname> <acronym>RPM</acronym> Installation</title>
-
-&common;
-   <para>
-    Most vendors provide a complete RPM set for DocBook processing in
-    their distribution.  Look for an <quote>SGML</quote> option while
-    installing, or the following packages:
-    <filename>sgml-common</filename>, <filename>docbook</filename>,
-    <filename>stylesheets</filename>, <filename>openjade</filename>
-    (or <filename>jade</filename>).  Possibly
-    <filename>sgml-tools</filename> will be needed as well.  If your
-    distributor does not provide these then you should be able to make
-    use of the packages from some other, reasonably compatible vendor.
-   </para>
-  </sect2>
-
-<!## PG>
-  <sect2>
-   <title>FreeBSD Installation</title>
-
-&common;
-   <para>
-    The FreeBSD Documentation Project is itself a heavy user of
-    DocBook, so it comes as no surprise that there is a full set of
-    <quote>ports</quote> of the documentation tools available on
-    FreeBSD.  The following ports need to be installed to build the
-    documentation on FreeBSD.
-    <itemizedlist>
-     <listitem>
-      <para><filename>textproc/sp</filename></para>
-     </listitem>
-     <listitem>
-      <para><filename>textproc/openjade</filename></para>
-     </listitem>
-     <listitem>
-      <para><filename>textproc/iso8879</filename></para>
-     </listitem>
-     <listitem>
-      <para><filename>textproc/dsssl-docbook-modular</filename></para>
-     </listitem>
-     <listitem>
-      <para><filename>textproc/docbook-420</filename></para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    A number of things from <filename>/usr/ports/print</filename>
-    (<filename>tex</filename>, <filename>jadetex</filename>) might
-    also be of interest.
-   </para>
-
-   <para>
-    It's possible that the ports do not update the main catalog file
-    in <filename>/usr/local/share/sgml/catalog.ports</filename> or order
-    isn't proper .  Be sure to have the following lines in beginning of file:
-<programlisting>
-CATALOG "openjade/catalog"
-CATALOG "iso8879/catalog"
-CATALOG "docbook/dsssl/modular/catalog"
-CATALOG "docbook/4.2/catalog"
-</programlisting>
-    If you do not want to edit the file you can also set the
-    environment variable <envar>SGML_CATALOG_FILES</envar> to a
-    colon-separated list of catalog files (such as the one above).
-   </para>
-
-   <para>
-    More information about the FreeBSD documentation tools can be
-    found in the <ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/tools.html">
-    FreeBSD Documentation Project's instructions</ulink>.
-   </para>
-  </sect2>
-<!## end>
-
-<!## PG>
-  <sect2>
-   <title>Debian Packages</title>
-
-&common;
-   <para>
-    There is a full set of packages of the documentation tools
-    available for <productname>Debian GNU/Linux</productname>.
-    To install, simply use:
-<programlisting>
-apt-get install docbook docbook-dsssl docbook-xsl openjade1.3 xsltproc
-</programlisting>
-   </para>
-  </sect2>
-<!## end>
-
-  <sect2>
-   <title>Manual Installation from Source</title>
-
-&common;
-   <para>
-    The manual installation process of the DocBook tools is somewhat
-    complex, so if you have pre-built packages available, use them.
-    We describe here only a standard setup, with reasonably standard
-    installation paths, and no <quote>fancy</quote> features.  For
-    details, you should study the documentation of the respective
-    package, and read <acronym>SGML</acronym> introductory material.
-   </para>
-
-   <sect3>
-    <title>Installing OpenJade</title>
-
-    <procedure>
-      <step>
-&common;
-       <para>
-        The installation of OpenJade offers a GNU-style
-        <literal>./configure; make; make install</literal> build
-        process.  Details can be found in the OpenJade source
-        distribution. In a nutshell:
-<synopsis>
-./configure --enable-default-catalog=/usr/local/share/sgml/catalog
-make
-make install
-</synopsis>
-        Be sure to remember where you put the <quote>default
-        catalog</quote>; you will need it below.  You can also leave
-        it off, but then you will have to set the environment variable
-        <envar>SGML_CATALOG_FILES</envar> to point to the file
-        whenever you use <application>jade</application> later on.
-        (This method is also an option if OpenJade is already
-        installed and you want to install the rest of the toolchain
-        locally.)
-       </para>
-
-       <note>
-       <para>
-        Some users have reported encountering a segmentation fault using
-        openjade 1.4devel to build the PDFs, with a message like:
-<screen>
-openjade:./stylesheet.dsl:664:2:E: flow object not accepted by port; only display flow objects accepted
-make: *** [postgres-A4.tex-pdf] Segmentation fault
-</screen>
-        Downgrading to openjade 1.3 should get rid of this error.
-       </para>
-       </note>
-
-      </step>
-
-      <step id="doc-openjade-install">
-       <para>
-        Additionally, you should install the files
-        <filename>dsssl.dtd</filename>, <filename>fot.dtd</filename>,
-        <filename>style-sheet.dtd</filename>, and
-        <filename>catalog</filename> from the
-        <filename>dsssl</filename> directory somewhere, perhaps into
-        <filename>/usr/local/share/sgml/dsssl</filename>.  It's
-        probably easiest to copy the entire directory:
-<synopsis>
-cp -R dsssl /usr/local/share/sgml
-</synopsis>
-       </para>
-      </step>
-
-      <step>
-       <para>
-        Finally, create the file
-        <filename>/usr/local/share/sgml/catalog</filename> and add
-        this line to it:
-<programlisting>
-CATALOG "dsssl/catalog"
-</programlisting>
-        (This is a relative path reference to the file installed in
-        <xref linkend="doc-openjade-install">.  Be sure to adjust it
-        if you chose your installation layout differently.)
-       </para>
-      </step>
-     </procedure>
-   </sect3>
-
-   <sect3>
-    <title>Installing the <productname>DocBook</productname> <acronym>DTD</acronym> Kit</title>
-
-    <procedure>
-     <step>
-&common;
-      <para>
-       Obtain the <ulink url="http://www.docbook.org/sgml/4.2/docbook-4.2.zip">
-       DocBook V4.2 distribution</ulink>.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Create the directory
-       <filename>/usr/local/share/sgml/docbook-4.2</filename> and change
-       to it. (The exact location is irrelevant, but this one is
-       reasonable within the layout we are following here.)
-<screen>
-<prompt>$ </prompt><userinput>mkdir /usr/local/share/sgml/docbook-4.2</userinput>
-<prompt>$ </prompt><userinput>cd /usr/local/share/sgml/docbook-4.2</userinput>
-</screen>
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Unpack the archive:
-<screen>
-<prompt>$ </prompt><userinput>unzip -a ...../docbook-4.2.zip</userinput>
-</screen>
-       (The archive will unpack its files into the current directory.)
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Edit the file
-       <filename>/usr/local/share/sgml/catalog</filename> (or whatever
-       you told jade during installation) and put a line like this
-       into it:
-<programlisting>
-CATALOG "docbook-4.2/docbook.cat"
-</programlisting>
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Download the <ulink url="http://www.oasis-open.org/cover/ISOEnts.zip">
-       ISO 8879 character entities archive</ulink>, unpack it, and put the
-       files in the same directory you put the DocBook files in:
-<screen>
-<prompt>$ </prompt><userinput>cd /usr/local/share/sgml/docbook-4.2</userinput>
-<prompt>$ </prompt><userinput>unzip ...../ISOEnts.zip</userinput>
-</screen>
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Run the following command in the directory with the DocBook and ISO files:
-<programlisting>
-perl -pi -e 's/iso-(.*).gml/ISO\1/g' docbook.cat
-</programlisting>
-       (This fixes a mixup between the names used in the DocBook
-       catalog file and the actual names of the ISO character entity
-       files.)
-      </para>
-     </step>
-    </procedure>
-   </sect3>
-
-   <sect3>
-    <title>Installing the DocBook <acronym>DSSSL</acronym> Style Sheets</title>
-
-&common;
-    <para>
-     To install the style sheets, unzip and untar the distribution and
-     move it to a suitable place, for example
-     <filename>/usr/local/share/sgml</filename>.  (The archive will
-     automatically create a subdirectory.)
-<screen>
-<prompt>$</prompt> <userinput>gunzip docbook-dsssl-1.<replaceable>xx</>.tar.gz</userinput>
-<prompt>$</prompt> <userinput>tar -C /usr/local/share/sgml -xf docbook-dsssl-1.<replaceable>xx</>.tar</userinput>
-</screen>
-    </para>
-
-    <para>
-     The usual catalog entry in
-     <filename>/usr/local/share/sgml/catalog</filename> can also be
-     made:
-<programlisting>
-CATALOG "docbook-dsssl-1.<replaceable>xx</>/catalog"
-</programlisting>
-     Because stylesheets change rather often, and it's sometimes
-     beneficial to try out alternative versions,
-<!## PG>
-     <productname>PostgreSQL</productname> doesn't use this catalog
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> doesn't use this catalog
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> doesn't use this catalog
-<!## end>
-     entry.  See <xref linkend="docguide-toolsets-configure"> for
-     information about how to select the stylesheets instead.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Installing <productname>JadeTeX</productname></title>
-
-&common;
-    <para>
-     To install and use <productname>JadeTeX</productname>, you will
-     need a working installation of <productname>TeX</productname> and
-     <productname>LaTeX2e</productname>, including the supported
-     <productname>tools</productname> and
-     <productname>graphics</productname> packages,
-     <productname>Babel</productname>,
-     <productname><acronym>AMS</acronym> fonts</productname> and
-     <productname>AMS-LaTeX</productname>, the
-     <productname><acronym>PSNFSS</acronym></productname> extension
-     and companion kit of <quote>the 35 fonts</quote>, the
-     <productname>dvips</productname> program for generating
-     <productname>PostScript</productname>, the macro packages
-     <productname>fancyhdr</productname>,
-     <productname>hyperref</productname>,
-     <productname>minitoc</productname>,
-     <productname>url</productname> and
-     <productname>ot2enc</productname>.  All of these can be found on
-     your friendly neighborhood <ulink url="http://www.ctan.org">
-     <acronym>CTAN</acronym> site</ulink>.
-     The installation of the <application>TeX</application> base
-     system is far beyond the scope of this introduction.  Binary
-     packages should be available for any system that can run
-     <application>TeX</application>.
-    </para>
-
-    <para>
-     Before you can use <application>JadeTeX</application> with the
-<!## PG>
-     <productname>PostgreSQL</productname> documentation sources, you
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> documentation sources, you
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> documentation sources, you
-<!## end>
-     will need to increase the size of
-     <application>TeX</application>'s internal data structures.
-     Details on this can be found in the <application>JadeTeX</application>
-     installation instructions.
-    </para>
-
-    <para>
-     Once that is finished you can install <application>JadeTeX</application>:
-<screen>
-<prompt>$</prompt> <userinput>gunzip jadetex-<replaceable>xxx</replaceable>.tar.gz</userinput>
-<prompt>$</prompt> <userinput>tar xf jadetex-<replaceable>xxx</replaceable>.tar</userinput>
-<prompt>$</prompt> <userinput>cd jadetex</userinput>
-<prompt>$</prompt> <userinput>make install</userinput>
-<prompt>$</prompt> <userinput>mktexlsr</userinput>
-</screen>
-     The last two need to be done as <systemitem>root</systemitem>.
-    </para>
-
-   </sect3>
-
-  </sect2>
-
-  <sect2 id="docguide-toolsets-configure">
-   <title>Detection by <command>configure</command></title>
-
-&common;
-  <para>
-   Before you can build the documentation you need to run the
-   <filename>configure</filename> script as you would when building
-<!## PG>
-   the <productname>PostgreSQL</productname> programs themselves.
-<!## end>
-<!## XC>
-   the <productname>Postgres-XC</productname> programs themselves.
-<!## end>
-<!## XL>
-   the <productname>Postgres-XL</productname> programs themselves.
-<!## end>
-   Check the output near the end of the run, it should look something
-   like this:
-<screen>
-<computeroutput>
-checking for onsgmls... onsgmls
-checking for openjade... openjade
-checking for DocBook V4.2... yes
-checking for DocBook stylesheets... /usr/share/sgml/docbook/stylesheet/dsssl/modular
-checking for collateindex.pl... /usr/bin/collateindex.pl
-checking for xsltproc... xsltproc
-checking for osx... osx
-</computeroutput>
-</screen>
-   If neither <filename>onsgmls</filename> nor
-   <filename>nsgmls</filename> were found then some of the following tests
-   will be skipped.  <filename>nsgmls</filename> is part of the Jade
-   package.  You can pass the environment variables
-   <envar>JADE</envar> and <envar>NSGMLS</envar> to configure to point
-   to the programs if they are not found automatically.  If
-   <quote>DocBook V4.2</quote> was not found then you did not install
-   the DocBook DTD kit in a place where Jade can find it, or you have
-   not set up the catalog files correctly.  See the installation hints
-   above.  The DocBook stylesheets are looked for in a number of
-   relatively standard places, but if you have them some other place
-   then you should set the environment variable
-   <envar>DOCBOOKSTYLE</envar> to the location and rerun
-   <filename>configure</filename> afterwards.
-  </para>
-
-  </sect2>
- </sect1>
-
- <sect1 id="docguide-build">
-  <title>Building The Documentation</title>
-
-&common;
-  <para>
-   Once you have everything set up, change to the directory
-   <filename>doc/src/sgml</filename> and run one of the commands
-   described in the following subsections to build the
-   documentation. (Remember to use GNU make.)
-  </para>
-
-  <sect2>
-   <title>HTML</title>
-
-&common;
-   <para>
-    To build the <acronym>HTML</acronym> version of the documentation:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake html</userinput>
-</screen>
-    This is also the default target.  The output appears in the
-    subdirectory <filename>html</filename>.
-   </para>
-
-   <para>
-    To create a proper index, the build might process several identical
-    stages.  If you do not care about the index, and just want to
-    proof-read the output, use <literal>draft</>:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake draft</userinput>
-</screen>
-   </para>
-
-   <para>
-    To build the documentation as a single HTML page, use:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake postgres.html</userinput>
-</screen>
-   </para>
- </sect2>
-
- <sect2>
-  <title>Manpages</title>
-
-&common;
-  <para>
-   We use the DocBook XSL stylesheets to
-   convert <productname>DocBook</productname>
-   <sgmltag>refentry</sgmltag> pages to *roff output suitable for man
-   pages.  The man pages are also distributed as a tar archive,
-   similar to the <acronym>HTML</acronym> version.  To create the man
-   pages, use the commands:
-<programlisting>
-cd doc/src/sgml
-gmake man
-</programlisting>
-  </para>
- </sect2>
-
-  <sect2>
-   <title>Print Output via <application>JadeTeX</application></title>
-
-&common;
-   <para>
-    If you want to use <application>JadeTex</application> to produce a
-    printable rendition of the documentation, you can use one of the
-    following commands:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       To generate PostScript via <acronym>DVI</acronym> in A4 format:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake postgres-A4.ps</userinput>
-</screen>
-       In U.S. letter format:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake postgres-US.ps</userinput>
-</screen>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       To make a <acronym>PDF</acronym>:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake postgres-A4.pdf</userinput>
-</screen>
-       or:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake postgres-US.pdf</userinput>
-</screen>
-       (Of course you can also make a <acronym>PDF</acronym> version
-       from the PostScript, but if you generate <acronym>PDF</acronym>
-       directly, it will have hyperlinks and other enhanced features.)
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-<!## PG>
-    When using JadeTeX to build the PostgreSQL documentation, you will
-<!## end>
-<!## XC>
-    When using JadeTeX to build the Postgres-XC documentation, you will
-<!## end>
-<!## XL>
-    When using JadeTeX to build the Postgres-XL documentation, you will
-<!## end>
-    probably need to increase some of TeX's internal parameters.  These
-    can be set in the file <filename>texmf.cnf</filename>.  The following
-    settings worked at the time of this writing:
-<programlisting>
-hash_extra.jadetex  = 200000
-hash_extra.pdfjadetex  = 200000
-pool_size.jadetex = 2000000
-pool_size.pdfjadetex = 2000000
-string_vacancies.jadetex = 150000
-string_vacancies.pdfjadetex = 150000
-max_strings.jadetex = 300000
-max_strings.pdfjadetex = 300000
-save_size.jadetex = 15000
-save_size.pdfjadetex = 15000
-</programlisting>
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Overflow Text</title>
-
-&common;
-   <para>
-    Occasionally text is too wide for the printed margins, and in
-    extreme cases, too wide for the printed page, e.g.  non-wrapped
-    text, wide tables.  Overly wide text generates <quote>Overfull
-    hbox</quote> messages in the TeX log output file, e.g.
-    <filename>postgres-US.log</> or <filename>postgres-A4.log</>.
-    There are 72 points in an inch so anything reported as over 72
-    points too wide will probably not fit on the printed page (assuming
-    one inch margins).  To find the <acronym>SGML</acronym> text
-    causing the overflow, find the first page number mentioned above
-    the overflow message, e.g.  <literal>[50 ###]</> (page 50), and
-    look at the page after that (e.g. page 51) in the <acronym>PDF</acronym>
-    file to see the overflow text and adjust the <acronym>SGML</acronym>
-    accordingly.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Print Output via <acronym>RTF</acronym></title>
-
-&common;
-   <para>
-<!## PG>
-    You can also create a printable version of the <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-    You can also create a printable version of the <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-    You can also create a printable version of the <productname>Postgres-XL</productname>
-<!## end>
-    documentation by converting it to <acronym>RTF</acronym> and
-    applying minor formatting corrections using an office suite.
-    Depending on the capabilities of the particular office suite, you
-    can then convert the documentation to PostScript of
-    <acronym>PDF</acronym>.  The procedure below illustrates this
-    process using <productname>Applixware</productname>.
-   </para>
-
-   <note>
-    <para>
-<!## PG>
-     It appears that current versions of the <productname>PostgreSQL</productname> documentation
-<!## end>
-<!## XC>
-     It appears that current versions of the <productname>Postgres-XC</productname> documentation
-<!## end>
-<!## XL>
-     It appears that current versions of the <productname>Postgres-XL</productname> documentation
-<!## end>
-     trigger some bug in or exceed the size limit of OpenJade.  If the
-     build process of the <acronym>RTF</acronym> version hangs for a
-     long time and the output file still has size 0, then you might have
-     hit that problem.  (But keep in mind that a normal build takes 5
-     to 10 minutes, so don't abort too soon.)
-    </para>
-   </note>
-
-   <procedure>
-    <title><productname>Applixware</productname> <acronym>RTF</acronym> Cleanup</title>
-
-    <para>
-     <application>OpenJade</application> omits specifying a default
-     style for body text. In the past, this undiagnosed problem led to
-     a long process of table of contents generation. However, with
-     great help from the <productname>Applixware</productname> folks
-     the symptom was diagnosed and a workaround is available.
-    </para>
-
-    <step performance="required">
-     <para>
-      Generate the <acronym>RTF</acronym> version by typing:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake postgres.rtf</userinput>
-</screen>
-     </para>
-    </step>
-
-    <step performance="required">
-     <para>
-      Repair the RTF file to correctly specify all styles, in
-      particular the default style. If the document contains
-      <sgmltag>refentry</sgmltag> sections, one must also replace
-      formatting hints which tie a preceding paragraph to the current
-      paragraph, and instead tie the current paragraph to the
-      following one. A utility, <command>fixrtf</command>, is
-      available in <filename>doc/src/sgml</filename> to accomplish
-      these repairs:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>./fixrtf --refentry postgres.rtf</userinput>
-</screen>
-     </para>
-
-     <para>
-      The script adds <literal>{\s0 Normal;}</literal> as the zeroth
-      style in the document. According to
-      <productname>Applixware</productname>, the RTF standard would
-      prohibit adding an implicit zeroth style, though Microsoft Word
-      happens to handle this case. For repairing
-      <sgmltag>refentry</sgmltag> sections, the script replaces
-      <literal>\keepn</literal> tags with <literal>\keep</literal>.
-     </para>
-    </step>
-
-    <step performance="required">
-     <para>
-      Open a new document in <productname>Applixware Words</productname> and
-      then import the <acronym>RTF</acronym> file.
-     </para>
-    </step>
-
-    <step performance="required">
-     <para>
-      Generate a new table of contents (ToC) using
-      <productname>Applixware</productname>.
-     </para>
-
-     <substeps>
-      <step>
-       <para>
-        Select the existing ToC lines, from the beginning of the first
-        character on the first line to the last character of the last
-        line.
-       </para>
-      </step>
-
-      <step>
-       <para>
-        Build a new ToC using
-        <menuchoice><guimenu>Tools</guimenu><guisubmenu>Book
-        Building</guisubmenu><guimenuitem>Create Table of
-        Contents</guimenuitem></menuchoice>. Select the first three
-        levels of headers for inclusion in the ToC. This will replace
-        the existing lines imported in the RTF with a native
-        <productname>Applixware</productname> ToC.
-       </para>
-      </step>
-
-      <step>
-       <para>
-        Adjust the ToC formatting by using
-        <menuchoice><guimenu>Format</guimenu><guimenuitem>Style</guimenuitem></menuchoice>,
-        selecting each of the three ToC styles, and adjusting the
-        indents for <literal>First</literal> and
-        <literal>Left</literal>. Use the following values:
-
-        <informaltable>
-         <tgroup cols="3">
-          <thead>
-           <row>
-            <entry>Style</entry>
-            <entry>First Indent (inches)</entry>
-            <entry>Left Indent (inches)</entry>
-           </row>
-          </thead>
-
-          <tbody>
-           <row>
-            <entry><literal>TOC-Heading 1</literal></entry>
-            <entry><literal>0.4</literal></entry>
-            <entry><literal>0.4</literal></entry>
-           </row>
-
-           <row>
-            <entry><literal>TOC-Heading 2</literal></entry>
-            <entry><literal>0.8</literal></entry>
-            <entry><literal>0.8</literal></entry>
-           </row>
-
-           <row>
-            <entry><literal>TOC-Heading 3</literal></entry>
-            <entry><literal>1.2</literal></entry>
-            <entry><literal>1.2</literal></entry>
-           </row>
-          </tbody>
-         </tgroup>
-        </informaltable>
-       </para>
-      </step>
-     </substeps>
-    </step>
-
-    <step performance="required">
-     <para>
-      Work through the document to:
-
-      <itemizedlist>
-       <listitem>
-        <para>
-         Adjust page breaks.
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         Adjust table column widths.
-        </para>
-       </listitem>
-      </itemizedlist>
-     </para>
-    </step>
-
-    <step performance="required">
-     <para>
-      Replace the right-justified page numbers in the Examples and
-      Figures portions of the ToC with correct values. This only takes
-      a few minutes.
-     </para>
-    </step>
-
-    <step performance="optional">
-     <para>
-       Delete the index section from the document if it is empty.
-     </para>
-    </step>
-
-    <step performance="required">
-     <para>
-       Regenerate and adjust the table of contents.
-     </para>
-
-      <substeps>
-       <step>
-        <para>
-         Select the ToC field.
-        </para>
-       </step>
-
-       <step>
-        <para>
-         Select <menuchoice><guimenu>Tools</guimenu><guisubmenu>Book
-         Building</guisubmenu><guimenuitem>Create Table of
-         Contents</guimenuitem></menuchoice>.
-        </para>
-       </step>
-
-       <step>
-        <para>
-         Unbind the ToC by selecting
-         <menuchoice><guimenu>Tools</guimenu><guisubmenu>Field
-         Editing</guisubmenu><guimenuitem>Unprotect</guimenuitem></menuchoice>.
-        </para>
-       </step>
-
-       <step>
-        <para>
-         Delete the first line in the ToC, which is an entry for the
-         ToC itself.
-        </para>
-       </step>
-      </substeps>
-    </step>
-
-    <step performance="required">
-     <para>
-      Save the document as native <productname>Applixware
-      Words</productname> format to allow easier last minute editing
-      later.
-     </para>
-    </step>
-
-    <step performance="required">
-     <para>
-      <quote>Print</quote> the document
-      to a file in PostScript format.
-     </para>
-    </step>
-   </procedure>
-  </sect2>
-
-  <sect2>
-   <title>Plain Text Files</title>
-
-&common;
-   <para>
-    Several files are distributed as plain text, for reading during
-    the installation process. The <filename>INSTALL</filename> file
-    corresponds to <xref linkend="installation">, with some minor
-    changes to account for the different context.  To recreate the
-    file, change to the directory <filename>doc/src/sgml</filename>
-    and enter <userinput>gmake INSTALL</userinput>.  This will create
-    a file <filename>INSTALL.html</filename> that can be saved as text
-    with <productname>Netscape Navigator</productname> and put into
-    the place of the existing file.
-    <productname>Netscape</productname> seems to offer the best
-    quality for <acronym>HTML</acronym> to text conversions (over
-    <application>lynx</application> and
-    <application>w3m</application>).
-   </para>
-
-   <para>
-    The file <filename>HISTORY</filename> can be created similarly,
-    using the command <userinput>gmake HISTORY</userinput>.  For the
-    file <filename>src/test/regress/README</filename> the command is
-    <userinput>gmake regress_README</userinput>.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Syntax Check</title>
-
-&common;
-   <para>
-    Building the documentation can take very long.  But there is a
-    method to just check the correct syntax of the documentation
-    files, which only takes a few seconds:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake check</userinput>
-</screen>
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="docguide-authoring">
-  <title>Documentation Authoring</title>
-
-&common;
-   <para>
-    <acronym>SGML</acronym> and <productname>DocBook</productname> do
-    not suffer from an oversupply of open-source authoring tools. The
-    most common tool set is the
-    <productname>Emacs</productname>/<productname>XEmacs</productname>
-    editor with appropriate editing mode.  On some systems
-    these tools are provided in a typical full installation.
-   </para>
-
-   <sect2>
-    <title>Emacs/PSGML</title>
-
-&common;
-    <para>
-     <productname>PSGML</productname> is the most common and most
-     powerful mode for editing <acronym>SGML</acronym> documents.
-     When properly configured, it will allow you to use
-     <application>Emacs</application> to insert tags and check markup
-     consistency.  You could use it for <acronym>HTML</acronym> as
-     well.  Check the <ulink url="http://www.lysator.liu.se/projects/about_psgml.html">
-     PSGML web site</ulink> for downloads, installation instructions, and
-     detailed documentation.
-    </para>
-
-    <para>
-     There is one important thing to note with
-     <productname>PSGML</productname>: its author assumed that your
-     main <acronym>SGML</acronym> <acronym>DTD</acronym> directory
-     would be <filename>/usr/local/lib/sgml</filename>.  If, as in the
-     examples in this chapter, you use
-     <filename>/usr/local/share/sgml</filename>, you have to
-     compensate for this, either by setting
-     <envar>SGML_CATALOG_FILES</envar> environment variable, or you
-     can customize your <productname>PSGML</productname> installation
-     (its manual tells you how).
-    </para>
-
-    <para>
-     Put the following in your <filename>~/.emacs</filename>
-     environment file (adjusting the path names to be appropriate for
-     your system):
-
-<programlisting>
-; ********** for SGML mode (psgml)
-
-(setq sgml-omittag t)
-(setq sgml-shorttag t)
-(setq sgml-minimize-attributes nil)
-(setq sgml-always-quote-attributes t)
-(setq sgml-indent-step 1)
-(setq sgml-indent-data t)
-(setq sgml-parent-document nil)
-(setq sgml-exposed-tags nil)
-(setq sgml-catalog-files '("/usr/local/share/sgml/catalog"))
-
-(autoload 'sgml-mode "psgml" "Major mode to edit SGML files." t )
-</programlisting>
-
-     and in the same file add an entry for <acronym>SGML</acronym>
-     into the (existing) definition for
-     <varname>auto-mode-alist</varname>:
-<programlisting>
-(setq
-  auto-mode-alist
-  '(("\\.sgml$" . sgml-mode)
-   ))
-</programlisting>
-    </para>
-
-    <para>
-     You might find that when using <productname>PSGML</productname>, a
-     comfortable way of working with these separate files of book
-     parts is to insert a proper <literal>DOCTYPE</literal>
-     declaration while you're editing them.  If you are working on
-     this source, for instance, it is an appendix chapter, so you
-     would specify the document as an <quote>appendix</quote> instance
-     of a DocBook document by making the first line look like this:
-
-<programlisting>
-&lt;!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.2//EN"&gt;
-</programlisting>
-
-     This means that anything and everything that reads
-     <acronym>SGML</acronym> will get it right, and I can verify the
-     document with <command>nsgmls -s docguide.sgml</command>.  (But
-     you need to take out that line before building the entire
-     documentation set.)
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Other Emacs Modes</title>
-
-&common;
-    <para>
-     <productname>GNU Emacs</productname> ships with a different
-     <acronym>SGML</acronym> mode, which is not quite as powerful as
-     <productname>PSGML</productname>, but it's less confusing and
-     lighter weight.  Also, it offers syntax highlighting (font lock),
-     which can be very helpful.
-     <filename>src/tools/editors/emacs.samples</filename> contains
-     sample settings for this mode.
-    </para>
-
-    <para>
-     Norm Walsh offers a
-     <ulink url="http://nwalsh.com/emacs/docbookide/index.html">major mode</ulink>
-     specifically for DocBook which also has font-lock and a number of features to
-     reduce typing.
-    </para>
-   </sect2>
-
- </sect1>
-
-
- <sect1 id="docguide-style">
-  <title>Style Guide</title>
-
-  <sect2>
-   <title>Reference Pages</title>
-
-&common;
-   <para>
-    Reference pages should follow a standard layout.  This allows
-    users to find the desired information more quickly, and it also
-    encourages writers to document all relevant aspects of a command.
-    Consistency is not only desired among
-<!## PG>
-    <productname>PostgreSQL</productname> reference pages, but also
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> reference pages, but also
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> reference pages, but also
-<!## end>
-    with reference pages provided by the operating system and other
-    packages.  Hence the following guidelines have been developed.
-    They are for the most part consistent with similar guidelines
-    established by various operating systems.
-   </para>
-
-   <para>
-    Reference pages that describe executable commands should contain
-    the following sections, in this order.  Sections that do not apply
-    can be omitted.  Additional top-level sections should only be used
-    in special circumstances; often that information belongs in the
-    <quote>Usage</quote> section.
-
-    <variablelist>
-     <varlistentry>
-      <term>Name</term>
-      <listitem>
-       <para>
-        This section is generated automatically.  It contains the
-        command name and a half-sentence summary of its functionality.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Synopsis</term>
-      <listitem>
-       <para>
-        This section contains the syntax diagram of the command.  The
-        synopsis should normally not list each command-line option;
-        that is done below.  Instead, list the major components of the
-        command line, such as where input and output files go.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Description</term>
-      <listitem>
-       <para>
-        Several paragraphs explaining what the command does.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Options</term>
-      <listitem>
-       <para>
-        A list describing each command-line option.  If there are a
-        lot of options, subsections can be used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Exit Status</term>
-      <listitem>
-       <para>
-        If the program uses 0 for success and non-zero for failure,
-        then you do not need to document it.  If there is a meaning
-        behind the different non-zero exit codes, list them here.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Usage</term>
-      <listitem>
-       <para>
-        Describe any sublanguage or run-time interface of the program.
-        If the program is not interactive, this section can usually be
-        omitted.  Otherwise, this section is a catch-all for
-        describing run-time features.  Use subsections if appropriate.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Environment</term>
-      <listitem>
-       <para>
-        List all environment variables that the program might use.
-        Try to be complete; even seemingly trivial variables like
-        <envar>SHELL</envar> might be of interest to the user.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Files</term>
-      <listitem>
-       <para>
-        List any files that the program might access implicitly.  That
-        is, do not list input and output files that were specified on
-        the command line, but list configuration files, etc.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Diagnostics</term>
-      <listitem>
-       <para>
-        Explain any unusual output that the program might create.
-        Refrain from listing every possible error message.  This is a
-        lot of work and has little use in practice.  But if, say, the
-        error messages have a standard format that the user can parse,
-        this would be the place to explain it.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Notes</term>
-      <listitem>
-       <para>
-        Anything that doesn't fit elsewhere, but in particular bugs,
-        implementation flaws, security considerations, compatibility
-        issues.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Examples</term>
-      <listitem>
-       <para>
-        Examples
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>History</term>
-      <listitem>
-       <para>
-        If there were some major milestones in the history of the
-        program, they might be listed here.  Usually, this section can
-        be omitted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>See Also</term>
-      <listitem>
-       <para>
-        Cross-references, listed in the following order: other
-<!## PG>
-        <productname>PostgreSQL</productname> command reference pages,
-        <productname>PostgreSQL</productname> SQL command reference
-        pages, citation of <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> command reference pages,
-        <productname>Postgres-XC</productname> SQL command reference
-        pages, citation of <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> command reference pages,
-        <productname>Postgres-XL</productname> SQL command reference
-        pages, citation of <productname>Postgres-XL</productname>
-<!## end>
-        manuals, other reference pages (e.g., operating system, other
-        packages), other documentation.  Items in the same group are
-        listed alphabetically.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    Reference pages describing SQL commands should contain the
-    following sections: Name, Synopsis, Description, Parameters,
-    Outputs, Notes, Examples, Compatibility, History, See
-    Also.  The Parameters section is like the Options section, but
-    there is more freedom about which clauses of the command can be
-    listed.  The Outputs section is only needed if the command returns
-    something other than a default command-completion tag.  The Compatibility
-    section should explain to what extent
-    this command conforms to the SQL standard(s), or to which other
-    database system it is compatible.  The See Also section of SQL
-    commands should list SQL commands before cross-references to
-    programs.
-   </para>
-  </sect2>
-
- </sect1>
-</appendix>
diff --git a/doc-xc/src/sgml/dummy-seclabel.sgmlin b/doc-xc/src/sgml/dummy-seclabel.sgmlin
deleted file mode 100644
index 28d19d2409..0000000000
--- a/doc-xc/src/sgml/dummy-seclabel.sgmlin
+++ /dev/null
@@ -1,74 +0,0 @@
-<!-- doc/src/sgml/dummy_seclabel.sgml -->
-
-<sect1 id="dummy-seclabel" xreflabel="dummy_seclabel">
- <title>dummy_seclabel</title>
-
- <indexterm zone="dummy-seclabel">
-  <primary>dummy_seclabel</primary>
- </indexterm>
-
- <para>
-  The <filename>dummy_seclabel</> module exists only to support regression
-  testing of the <command>SECURITY LABEL</> statement.  It is not intended
-  to be used in production.
- </para>
-
- <sect2>
-  <title>Rationale</title>
-
-  <para>
-   The <command>SECURITY LABEL</> statement allows the user to assign security
-   labels to database objects; however, security labels can only be assigned
-   when specifically allowed by a loadable module, so this module is provided
-   to allow proper regression testing.
-  </para>
-
-  <para>
-   Security label providers intended to be used in production will typically be
-   dependent on a platform-specific feature such as
-   <productname>SE-Linux</productname>.  This module is platform-independent,
-   and therefore better-suited to regression testing.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Usage</title>
-
-  <para>
-   Here's a simple example of usage:
-  </para>
-
-<programlisting>
-# postgresql.conf
-shared_preload_libraries = 'dummy_label'
-</programlisting>
-
-<programlisting>
-postgres=# CREATE TABLE t (a int, b text);
-CREATE TABLE
-postgres=# SECURITY LABEL ON TABLE t IS 'classified';
-SECURITY LABEL
-</programlisting>
-
-  <para>
-   The <filename>dummy_seclabel</> module provides only four hardcoded
-   labels: <literal>unclassified</>, <literal>classified</>,
-   <literal>secret</>, and <literal>top secret</>.
-   It does not allow any other strings as security labels.
-  </para>
-  <para>
-   These labels are not used to enforce access controls.  They are only used
-   to check whether the <command>SECURITY LABEL</> statement works as expected,
-   or not.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   KaiGai Kohei <email>[email protected]</email>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/earthdistance.sgmlin b/doc-xc/src/sgml/earthdistance.sgmlin
deleted file mode 100644
index 7930f0bfca..0000000000
--- a/doc-xc/src/sgml/earthdistance.sgmlin
+++ /dev/null
@@ -1,201 +0,0 @@
-<!-- doc/src/sgml/earthdistance.sgml -->
-
-<sect1 id="earthdistance" xreflabel="earthdistance">
- <title>earthdistance</title>
-
- <indexterm zone="earthdistance">
-  <primary>earthdistance</primary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  The <filename>earthdistance</> module provides two different approaches to
-  calculating great circle distances on the surface of the Earth. The one
-  described first depends on the <filename>cube</> module (which
-  <emphasis>must</> be installed before <filename>earthdistance</> can be
-  installed). The second one is based on the built-in <type>point</> data type,
-  using longitude and latitude for the coordinates.
- </para>
-
- <para>
-  In this module, the Earth is assumed to be perfectly spherical.
-  (If that's too inaccurate for you, you might want to look at the
-  <application><ulink url="http://www.postgis.org/">PostGIS</ulink></>
-  project.)
- </para>
-
- <sect2>
-  <title>Cube-based Earth Distances</title>
-
-&pgnotice;
-
-
-  <para>
-   Data is stored in cubes that are points (both corners are the same) using 3
-   coordinates representing the x, y, and z distance from the center of the
-   Earth.  A domain <type>earth</> over <type>cube</> is provided, which
-   includes constraint checks that the value meets these restrictions and
-   is reasonably close to the actual surface of the Earth.
-  </para>
-
-  <para>
-   The radius of the Earth is obtained from the <function>earth()</>
-   function. It is given in meters. But by changing this one function you can
-   change the module to use some other units, or to use a different value of
-   the radius that you feel is more appropriate.
-  </para>
-
-  <para>
-   This package has applications to astronomical databases as well.
-   Astronomers will probably want to change <function>earth()</> to return a
-   radius of <literal>180/pi()</> so that distances are in degrees.
-  </para>
-
-  <para>
-   Functions are provided to support input in latitude and longitude (in
-   degrees), to support output of latitude and longitude, to calculate
-   the great circle distance between two points and to easily specify a
-   bounding box usable for index searches.
-  </para>
-
-  <para>
-   The provided functions are shown
-   in <xref linkend="earthdistance-cube-functions">.
-  </para>
-
-  <table id="earthdistance-cube-functions">
-   <title>Cube-based Earthdistance Functions</title>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Returns</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><function>earth()</function></entry>
-      <entry><type>float8</type></entry>
-      <entry>Returns the assumed radius of the Earth.</entry>
-     </row>
-     <row>
-      <entry><function>sec_to_gc(float8)</function></entry>
-      <entry><type>float8</type></entry>
-      <entry>Converts the normal straight line
-       (secant) distance between between two points on the surface of the Earth
-       to the great circle distance between them.
-      </entry>
-     </row>
-     <row>
-      <entry><function>gc_to_sec(float8)</function></entry>
-      <entry><type>float8</type></entry>
-      <entry>Converts the great circle distance between two points on the
-       surface of the Earth to the normal straight line (secant) distance
-       between them.
-      </entry>
-     </row>
-     <row>
-      <entry><function>ll_to_earth(float8, float8)</function></entry>
-      <entry><type>earth</type></entry>
-      <entry>Returns the location of a point on the surface of the Earth given
-       its latitude (argument 1) and longitude (argument 2) in degrees.
-      </entry>
-     </row>
-     <row>
-      <entry><function>latitude(earth)</function></entry>
-      <entry><type>float8</type></entry>
-      <entry>Returns the latitude in degrees of a point on the surface of the
-       Earth.
-      </entry>
-     </row>
-     <row>
-      <entry><function>longitude(earth)</function></entry>
-      <entry><type>float8</type></entry>
-      <entry>Returns the longitude in degrees of a point on the surface of the
-       Earth.
-      </entry>
-     </row>
-     <row>
-      <entry><function>earth_distance(earth, earth)</function></entry>
-      <entry><type>float8</type></entry>
-      <entry>Returns the great circle distance between two points on the
-       surface of the Earth.
-      </entry>
-     </row>
-     <row>
-      <entry><function>earth_box(earth, float8)</function></entry>
-      <entry><type>cube</type></entry>
-      <entry>Returns a box suitable for an indexed search using the cube
-       <literal>@&gt;</>
-       operator for points within a given great circle distance of a location.
-       Some points in this box are further than the specified great circle
-       distance from the location, so a second check using
-       <function>earth_distance</> should be included in the query.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect2>
-
- <sect2>
-  <title>Point-based Earth Distances</title>
-
-&pgnotice;
-
-
-  <para>
-   The second part of the module relies on representing Earth locations as
-   values of type <type>point</>, in which the first component is taken to
-   represent longitude in degrees, and the second component is taken to
-   represent latitude in degrees.  Points are taken as (longitude, latitude)
-   and not vice versa because longitude is closer to the intuitive idea of
-   x-axis and latitude to y-axis.
-  </para>
-
-  <para>
-   A single operator is provided, shown
-   in <xref linkend="earthdistance-point-operators">.
-  </para>
-
-  <table id="earthdistance-point-operators">
-   <title>Point-based Earthdistance Operators</title>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Operator</entry>
-      <entry>Returns</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><type>point</> <literal>&lt;@&gt;</literal> <type>point</></entry>
-      <entry><type>float8</type></entry>
-      <entry>Gives the distance in statute miles between
-       two points on the Earth's surface.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Note that unlike the <type>cube</>-based part of the module, units
-   are hardwired here: changing the <function>earth()</> function will
-   not affect the results of this operator.
-  </para>
-
-  <para>
-   One disadvantage of the longitude/latitude representation is that
-   you need to be careful about the edge conditions near the poles
-   and near +/- 180 degrees of longitude.  The <type>cube</>-based
-   representation avoids these discontinuities.
-  </para>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/ecpg.sgmlin b/doc-xc/src/sgml/ecpg.sgmlin
deleted file mode 100644
index 9004dbab23..0000000000
--- a/doc-xc/src/sgml/ecpg.sgmlin
+++ /dev/null
@@ -1,9736 +0,0 @@
-<!-- doc/src/sgml/ecpg.sgml -->
-
-<chapter id="ecpg">
- <title><application>ECPG</application> - Embedded <acronym>SQL</acronym> in C</title>
-
- <indexterm zone="ecpg"><primary>embedded SQL</primary><secondary>in C</secondary></indexterm>
- <indexterm zone="ecpg"><primary>C</primary></indexterm>
- <indexterm zone="ecpg"><primary>ECPG</primary></indexterm>
-
- <para>
-  This chapter describes the embedded <acronym>SQL</acronym> package
-  for <productname>PostgreSQL</productname>. It was written by
-  Linus Tolke (<email>[email protected]</email>) and Michael Meskes
-  (<email>[email protected]</email>). Originally it was written to work with
-  <acronym>C</acronym>. It also works with <acronym>C++</acronym>, but
-  it does not recognize all <acronym>C++</acronym> constructs yet.
- </para>
-
- <para>
-  This documentation is quite incomplete.  But since this
-  interface is standardized, additional information can be found in
-  many resources about SQL.
- </para>
-
- <sect1 id="ecpg-concept">
-  <title>The Concept</title>
-
-&common;
-  <para>
-   An embedded SQL program consists of code written in an ordinary
-   programming language, in this case C, mixed with SQL commands in
-   specially marked sections.  To build the program, the source code (<filename>*.pgc</filename>)
-   is first passed through the embedded SQL preprocessor, which converts it
-   to an ordinary C program (<filename>*.c</filename>), and afterwards it can be processed by a C
-   compiler.  (For details about the compiling and linking see <xref linkend="ecpg-process">).
-   Converted ECPG applications call functions in the libpq library
-   through the embedded SQL library (ecpglib), and communicate with
-   the PostgreSQL server using the normal frontend-backend protocol.
-  </para>
-
-  <para>
-   Embedded <acronym>SQL</acronym> has advantages over other methods
-   for handling <acronym>SQL</acronym> commands from C code. First, it
-   takes care of the tedious passing of information to and from
-   variables in your <acronym>C</acronym> program.  Second, the SQL
-   code in the program is checked at build time for syntactical
-   correctness.  Third, embedded <acronym>SQL</acronym> in C is
-   specified in the <acronym>SQL</acronym> standard and supported by
-   many other <acronym>SQL</acronym> database systems.  The
-   <productname>PostgreSQL</> implementation is designed to match this
-   standard as much as possible, and it is usually possible to port
-   embedded <acronym>SQL</acronym> programs written for other SQL
-   databases to <productname>PostgreSQL</productname> with relative
-   ease.
-  </para>
-
-  <para>
-   As already stated, programs written for the embedded
-   <acronym>SQL</acronym> interface are normal C programs with special
-   code inserted to perform database-related actions.  This special
-   code always has the form:
-<programlisting>
-EXEC SQL ...;
-</programlisting>
-   These statements syntactically take the place of a C statement.
-   Depending on the particular statement, they can appear at the
-   global level or within a function.  Embedded
-   <acronym>SQL</acronym> statements follow the case-sensitivity rules
-   of normal <acronym>SQL</acronym> code, and not those of C.
-  </para>
-
-  <para>
-   The following sections explain all the embedded SQL statements.
-  </para>
- </sect1>
-
- <sect1 id="ecpg-connect">
-  <title>Managing Database Connections</title>
-
-&common;
-  <para>
-   This section describes how to open, close, and switch database
-   connections.
-  </para>
-
-  <sect2 id="ecpg-connecting">
-   <title>Connecting to the Database Server</title>
-
-&common;
-  <para>
-   One connects to a database using the following statement:
-<programlisting>
-EXEC SQL CONNECT TO <replaceable>target</replaceable> <optional>AS <replaceable>connection-name</replaceable></optional> <optional>USER <replaceable>user-name</replaceable></optional>;
-</programlisting>
-   The <replaceable>target</replaceable> can be specified in the
-   following ways:
-
-   <itemizedlist>
-    <listitem>
-     <simpara>
-      <literal><replaceable>dbname</><optional>@<replaceable>hostname</></optional><optional>:<replaceable>port</></optional></literal>
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      <literal>tcp:postgresql://<replaceable>hostname</><optional>:<replaceable>port</></optional><optional>/<replaceable>dbname</></optional><optional>?<replaceable>options</></optional></literal>
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      <literal>unix:postgresql://<replaceable>hostname</><optional>:<replaceable>port</></optional><optional>/<replaceable>dbname</></optional><optional>?<replaceable>options</></optional></literal>
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      an SQL string literal containing one of the above forms
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      a reference to a character variable containing one of the above forms (see examples)
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      <literal>DEFAULT</literal>
-     </simpara>
-    </listitem>
-   </itemizedlist>
-
-   If you specify the connection target literally (that is, not
-   through a variable reference) and you don't quote the value, then
-   the case-insensitivity rules of normal SQL are applied.  In that
-   case you can also double-quote the individual parameters separately
-   as needed.  In practice, it is probably less error-prone to use a
-   (single-quoted) string literal or a variable reference.  The
-   connection target <literal>DEFAULT</literal> initiates a connection
-   to the default database under the default user name.  No separate
-   user name or connection name can be specified in that case.
-  </para>
-
-  <para>
-   There are also different ways to specify the user name:
-
-   <itemizedlist>
-    <listitem>
-     <simpara>
-      <literal><replaceable>username</replaceable></literal>
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      <literal><replaceable>username</replaceable>/<replaceable>password</replaceable></literal>
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      <literal><replaceable>username</replaceable> IDENTIFIED BY <replaceable>password</replaceable></literal>
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      <literal><replaceable>username</replaceable> USING <replaceable>password</replaceable></literal>
-     </simpara>
-    </listitem>
-   </itemizedlist>
-
-   As above, the parameters <replaceable>username</replaceable> and
-   <replaceable>password</replaceable> can be an SQL identifier, an
-   SQL string literal, or a reference to a character variable.
-  </para>
-
-  <para>
-   The <replaceable>connection-name</replaceable> is used to handle
-   multiple connections in one program.  It can be omitted if a
-   program uses only one connection.  The most recently opened
-   connection becomes the current connection, which is used by default
-   when an SQL statement is to be executed (see later in this
-   chapter).
-  </para>
-
-  <para>
-   Here are some examples of <command>CONNECT</command> statements:
-<programlisting>
-EXEC SQL CONNECT TO [email protected];
-
-EXEC SQL CONNECT TO unix:postgresql://sql.mydomain.com/mydb AS myconnection USER john;
-
-EXEC SQL BEGIN DECLARE SECTION;
-const char *target = "[email protected]";
-const char *user = "john";
-EXEC SQL END DECLARE SECTION;
- ...
-EXEC SQL CONNECT TO :target USER :user;
-</programlisting>
-   The last form makes use of the variant referred to above as
-   character variable reference.  You will see in later sections how C
-   variables can be used in SQL statements when you prefix them with a
-   colon.
-  </para>
-
-  <para>
-   Be advised that the format of the connection target is not
-   specified in the SQL standard.  So if you want to develop portable
-   applications, you might want to use something based on the last
-   example above to encapsulate the connection target string
-   somewhere.
-  </para>
-  </sect2>
-
-  <sect2 id="ecpg-set-connection">
-   <title>Choosing a Connection</title>
-
-&common;
-  <para>
-   SQL statements in embedded SQL programs are by default executed on
-   the current connection, that is, the most recently opened one.  If
-   an application needs to manage multiple connections, then there are
-   two ways to handle this.
-  </para>
-
-  <para>
-   The first option is to explicitly choose a connection for each SQL
-   statement, for example:
-<programlisting>
-EXEC SQL AT <replaceable>connection-name</replaceable> SELECT ...;
-</programlisting>
-   This option is particularly suitable if the application needs to
-   use several connections in mixed order.
-  </para>
-
-  <para>
-   If your application uses multiple threads of execution, they cannot share a
-   connection concurrently. You must either explicitly control access to the connection
-   (using mutexes) or use a connection for each thread. If each thread uses its own connection,
-   you will need to use the AT clause to specify which connection the thread will use.
-  </para>
-
-  <para>
-   The second option is to execute a statement to switch the current
-   connection.  That statement is:
-<programlisting>
-EXEC SQL SET CONNECTION <replaceable>connection-name</replaceable>;
-</programlisting>
-   This option is particularly convenient if many statements are to be
-   executed on the same connection.  It is not thread-aware.
-  </para>
-
-  <para>
-   Here is an example program managing multiple database connections:
-<programlisting><![CDATA[
-#include <stdio.h>
-
-EXEC SQL BEGIN DECLARE SECTION;
-    char dbname[1024];
-EXEC SQL END DECLARE SECTION;
-
-int
-main()
-{
-    EXEC SQL CONNECT TO testdb1 AS con1 USER testuser;
-    EXEC SQL CONNECT TO testdb2 AS con2 USER testuser;
-    EXEC SQL CONNECT TO testdb3 AS con3 USER testuser;
-
-    /* This query would be executed in the last opened database "testdb3". */
-    EXEC SQL SELECT current_database() INTO :dbname;
-    printf("current=%s (should be testdb3)\n", dbname);
-
-    /* Using "AT" to run a query in "testdb2" */
-    EXEC SQL AT con2 SELECT current_database() INTO :dbname;
-    printf("current=%s (should be testdb2)\n", dbname);
-
-    /* Switch the current connection to "testdb1". */
-    EXEC SQL SET CONNECTION con1;
-
-    EXEC SQL SELECT current_database() INTO :dbname;
-    printf("current=%s (should be testdb1)\n", dbname);
-
-    EXEC SQL DISCONNECT ALL;
-    return 0;
-}
-]]></programlisting>
-
-   This example would produce this output:
-<screen>
-current=testdb3 (should be testdb3)
-current=testdb2 (should be testdb2)
-current=testdb1 (should be testdb1)
-</screen>
-  </para>
-  </sect2>
-
-  <sect2 id="ecpg-disconnect">
-   <title>Closing a Connection</title>
-
-&common;
-  <para>
-   To close a connection, use the following statement:
-<programlisting>
-EXEC SQL DISCONNECT <optional><replaceable>connection</replaceable></optional>;
-</programlisting>
-   The <replaceable>connection</replaceable> can be specified
-   in the following ways:
-
-   <itemizedlist>
-    <listitem>
-     <simpara>
-      <literal><replaceable>connection-name</replaceable></literal>
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      <literal>DEFAULT</literal>
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      <literal>CURRENT</literal>
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      <literal>ALL</literal>
-     </simpara>
-    </listitem>
-   </itemizedlist>
-
-   If no connection name is specified, the current connection is
-   closed.
-  </para>
-
-  <para>
-   It is good style that an application always explicitly disconnect
-   from every connection it opened.
-  </para>
-  </sect2>
-
- </sect1>
-
- <sect1 id="ecpg-commands">
-  <title>Running SQL Commands</title>
-
-&common;
-  <para>
-   Any SQL command can be run from within an embedded SQL application.
-   Below are some examples of how to do that.
-  </para>
-
-  <sect2 id="ecpg-executing">
-   <title>Executing SQL Statements</title>
-
-&common;
-  <para>
-   Creating a table:
-<programlisting>
-EXEC SQL CREATE TABLE foo (number integer, ascii char(16));
-EXEC SQL CREATE UNIQUE INDEX num1 ON foo(number);
-EXEC SQL COMMIT;
-</programlisting>
-  </para>
-
-  <para>
-   Inserting rows:
-<programlisting>
-EXEC SQL INSERT INTO foo (number, ascii) VALUES (9999, 'doodad');
-EXEC SQL COMMIT;
-</programlisting>
-  </para>
-
-  <para>
-   Deleting rows:
-<programlisting>
-EXEC SQL DELETE FROM foo WHERE number = 9999;
-EXEC SQL COMMIT;
-</programlisting>
-  </para>
-
-  <para>
-   Updates:
-<programlisting>
-EXEC SQL UPDATE foo
-    SET ascii = 'foobar'
-    WHERE number = 9999;
-EXEC SQL COMMIT;
-</programlisting>
-  </para>
-
-  <para>
-   <literal>SELECT</literal> statements that return a single result
-   row can also be executed using
-   <literal>EXEC SQL</literal> directly.  To handle result sets with
-   multiple rows, an application has to use a cursor;
-   see <xref linkend="ecpg-cursors"> below.  (As a special case, an
-   application can fetch multiple rows at once into an array host
-   variable; see <xref linkend="ecpg-variables-arrays">.)
-  </para>
-
-  <para>
-   Single-row select:
-<programlisting>
-EXEC SQL SELECT foo INTO :FooBar FROM table1 WHERE ascii = 'doodad';
-</programlisting>
-  </para>
-
-  <para>
-   Also, a configuration parameter can be retrieved with the
-   <literal>SHOW</literal> command:
-<programlisting>
-EXEC SQL SHOW search_path INTO :var;
-</programlisting>
-  </para>
-
-  <para>
-   The tokens of the form
-   <literal>:<replaceable>something</replaceable></literal> are
-   <firstterm>host variables</firstterm>, that is, they refer to
-   variables in the C program.  They are explained in <xref
-   linkend="ecpg-variables">.
-  </para>
-  </sect2>
-
-  <sect2 id="ecpg-cursors">
-   <title>Using Cursors</title>
-
-&common;
-  <para>
-   To retrieve a result set holding multiple rows, an application has
-   to declare a cursor and fetch each row from the cursor.  The steps
-   to use a cursor are the following: declare a cursor, open it, fetch
-   a row from the cursor, repeat, and finally close it.
-  </para>
-
-  <para>
-   Select using cursors:
-<programlisting>
-EXEC SQL DECLARE foo_bar CURSOR FOR
-    SELECT number, ascii FROM foo
-    ORDER BY ascii;
-EXEC SQL OPEN foo_bar;
-EXEC SQL FETCH foo_bar INTO :FooBar, DooDad;
-...
-EXEC SQL CLOSE foo_bar;
-EXEC SQL COMMIT;
-</programlisting>
-  </para>
-
-  <para>
-   For more details about declaration of the cursor,
-   see <xref linkend="ecpg-sql-declare">, and
-   see <xref linkend="sql-fetch"> for <literal>FETCH</literal> command
-   details.
-  </para>
-
-   <note>
-    <para>
-     The ECPG <command>DECLARE</command> command does not actually
-     cause a statement to be sent to the PostgreSQL backend.  The
-     cursor is opened in the backend (using the
-     backend's <command>DECLARE</command> command) at the point when
-     the <command>OPEN</command> command is executed.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2 id="ecpg-transactions">
-   <title>Managing Transactions</title>
-
-&common;
-  <para>
-   In the default mode, statements are committed only when
-   <command>EXEC SQL COMMIT</command> is issued. The embedded SQL
-   interface also supports autocommit of transactions (similar to
-   <application>libpq</> behavior) via the <option>-t</option>
-   command-line option to <command>ecpg</command> (see <xref
-   linkend="app-ecpg">) or via the <literal>EXEC SQL SET AUTOCOMMIT TO
-   ON</literal> statement. In autocommit mode, each command is
-   automatically committed unless it is inside an explicit transaction
-   block. This mode can be explicitly turned off using <literal>EXEC
-   SQL SET AUTOCOMMIT TO OFF</literal>.
-  </para>
-
-   <para>
-    The following transaction management commands are available:
-
-    <variablelist>
-     <varlistentry>
-      <term><literal>EXEC SQL COMMIT</literal></term>
-      <listitem>
-       <para>
-        Commit an in-progress transaction.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>EXEC SQL ROLLBACK</literal></term>
-      <listitem>
-       <para>
-        Roll back an in-progress transaction.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>EXEC SQL SET AUTOCOMMIT TO ON</literal></term>
-      <listitem>
-       <para>
-        Enable autocommit mode.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>SET AUTOCOMMIT TO OFF</literal></term>
-      <listitem>
-       <para>
-        Disable autocommit mode.  This is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-prepared">
-   <title>Prepared Statements</title>
-
-&common;
-   <para>
-    When the values to be passed to an SQL statement are not known at
-    compile time, or the same statement is going to be used many
-    times, then prepared statements can be useful.
-   </para>
-
-   <para>
-    The statement is prepared using the
-    command <literal>PREPARE</literal>.  For the values that are not
-    known yet, use the
-    placeholder <quote><literal>?</literal></quote>:
-<programlisting>
-EXEC SQL PREPARE stmt1 FROM "SELECT oid, datname FROM pg_database WHERE oid = ?";
-</programlisting>
-   </para>
-
-   <para>
-    If a statement returns a single row, the application can
-    call <literal>EXECUTE</literal> after
-    <literal>PREPARE</literal> to execute the statement, supplying the
-    actual values for the placeholders with a <literal>USING</literal>
-    clause:
-<programlisting>
-EXEC SQL EXECUTE stmt1 INTO :dboid, :dbname USING 1;
-</programlisting>
-   </para>
-
-   <para>
-    If a statement returns multiple rows, the application can use a
-    cursor declared based on the prepared statement.  To bind input
-    parameters, the cursor must be opened with
-    a <literal>USING</literal> clause:
-<programlisting>
-EXEC SQL PREPARE stmt1 FROM "SELECT oid,datname FROM pg_database WHERE oid &gt; ?";
-EXEC SQL DECLARE foo_bar CURSOR FOR stmt1;
-
-/* when end of result set reached, break out of while loop */
-EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-EXEC SQL OPEN foo_bar USING 100;
-...
-while (1)
-{
-    EXEC SQL FETCH NEXT FROM foo_bar INTO :dboid, :dbname;
-    ...
-}
-EXEC SQL CLOSE foo_bar;
-</programlisting>
-   </para>
-
-   <para>
-    When you don't need the prepared statement anymore, you should
-    deallocate it:
-<programlisting>
-EXEC SQL DEALLOCATE PREPARE <replaceable>name</replaceable>;
-</programlisting>
-   </para>
-
-   <para>
-    For more details about <literal>PREPARE</literal>,
-    see <xref linkend="ecpg-sql-prepare">. Also
-    see <xref linkend="ecpg-dynamic"> for more details about using
-    placeholders and input parameters.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="ecpg-variables">
-  <title>Using Host Variables</title>
-
-&common;
-  <para>
-   In <xref linkend="ecpg-commands"> you saw how you can execute SQL
-   statements from an embedded SQL program.  Some of those statements
-   only used fixed values and did not provide a way to insert
-   user-supplied values into statements or have the program process
-   the values returned by the query.  Those kinds of statements are
-   not really useful in real applications.  This section explains in
-   detail how you can pass data between your C program and the
-   embedded SQL statements using a simple mechanism called
-   <firstterm>host variables</firstterm>. In an embedded SQL program  we
-   consider the SQL statements to be <firstterm>guests</firstterm> in the C
-   program code which is the <firstterm>host language</firstterm>. Therefore
-   the variables of the C program are called <firstterm>host
-   variables</firstterm>.
-  </para>
-
-  <para>
-   Another way to exchange values between PostgreSQL backends and ECPG
-   applications is the use of SQL descriptors, described
-   in <xref linkend="ecpg-descriptors">.
-  </para>
-
-  <sect2 id="ecpg-variables-overview">
-   <title>Overview</title>
-
-&common;
-   <para>
-    Passing data between the C program and the SQL statements is
-    particularly simple in embedded SQL.  Instead of having the
-    program paste the data into the statement, which entails various
-    complications, such as properly quoting the value, you can simply
-    write the name of a C variable into the SQL statement, prefixed by
-    a colon.  For example:
-<programlisting>
-EXEC SQL INSERT INTO sometable VALUES (:v1, 'foo', :v2);
-</programlisting>
-    This statements refers to two C variables named
-    <varname>v1</varname> and <varname>v2</varname> and also uses a
-    regular SQL string literal, to illustrate that you are not
-    restricted to use one kind of data or the other.
-   </para>
-
-   <para>
-    This style of inserting C variables in SQL statements works
-    anywhere a value expression is expected in an SQL statement.
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-declare-sections">
-   <title>Declare Sections</title>
-
-&common;
-   <para>
-    To pass data from the program to the database, for example as
-    parameters in a query, or to pass data from the database back to
-    the program, the C variables that are intended to contain this
-    data need to be declared in specially marked sections, so the
-    embedded SQL preprocessor is made aware of them.
-   </para>
-
-   <para>
-    This section starts with:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-</programlisting>
-    and ends with:
-<programlisting>
-EXEC SQL END DECLARE SECTION;
-</programlisting>
-    Between those lines, there must be normal C variable declarations,
-    such as:
-<programlisting>
-int   x = 4;
-char  foo[16], bar[16];
-</programlisting>
-    As you can see, you can optionally assign an initial value to the variable.
-    The variable's scope is determined by the location of its declaring
-    section within the program.
-    You can also declare variables with the following syntax which implicitly
-    creates a declare section:
-<programlisting>
-EXEC SQL int i = 4;
-</programlisting>
-    You can have as many declare sections in a program as you like.
-   </para>
-
-   <para>
-    The declarations are also echoed to the output file as normal C
-    variables, so there's no need to declare them again.  Variables
-    that are not intended to be used in SQL commands can be declared
-    normally outside these special sections.
-   </para>
-
-   <para>
-    The definition of a structure or union also must be listed inside
-    a <literal>DECLARE</> section. Otherwise the preprocessor cannot
-    handle these types since it does not know the definition.
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-retrieving">
-   <title>Retrieving Query Results</title>
-
-&common;
-   <para>
-    Now you should be able to pass data generated by your program into
-    an SQL command.  But how do you retrieve the results of a query?
-    For that purpose, embedded SQL provides special variants of the
-    usual commands <command>SELECT</command> and
-    <command>FETCH</command>.  These commands have a special
-    <literal>INTO</literal> clause that specifies which host variables
-    the retrieved values are to be stored in.
-    <command>SELECT</command> is used for a query that returns only
-    single row, and <command>FETCH</command> is used for a query that
-    returns multiple rows, using a cursor.
-   </para>
-
-   <para>
-    Here is an example:
-<programlisting>
-/*
- * assume this table:
- * CREATE TABLE test1 (a int, b varchar(50));
- */
-
-EXEC SQL BEGIN DECLARE SECTION;
-int v1;
-VARCHAR v2;
-EXEC SQL END DECLARE SECTION;
-
- ...
-
-EXEC SQL SELECT a, b INTO :v1, :v2 FROM test;
-</programlisting>
-    So the <literal>INTO</literal> clause appears between the select
-    list and the <literal>FROM</literal> clause.  The number of
-    elements in the select list and the list after
-    <literal>INTO</literal> (also called the target list) must be
-    equal.
-   </para>
-
-   <para>
-    Here is an example using the command <command>FETCH</command>:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-int v1;
-VARCHAR v2;
-EXEC SQL END DECLARE SECTION;
-
- ...
-
-EXEC SQL DECLARE foo CURSOR FOR SELECT a, b FROM test;
-
- ...
-
-do
-{
-    ...
-    EXEC SQL FETCH NEXT FROM foo INTO :v1, :v2;
-    ...
-} while (...);
-</programlisting>
-    Here the <literal>INTO</literal> clause appears after all the
-    normal clauses.
-   </para>
-
-   <para>
-    Both of these methods only allow retrieving one row at a time.  If
-    you need to process result sets that potentially contain more than
-    one row, you need to use a cursor, as shown in the second example.
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-variables-type-mapping">
-   <title>Type Mapping</title>
-
-&common;
-   <para>
-    When ECPG applications exchange values between the PostgreSQL
-    server and the C application, such as when retrieving query
-    results from the server or executing SQL statements with input
-    parameters, the values need to be converted between PostgreSQL
-    data types and host language variable types (C language data
-    types, concretely).  One of the main points of ECPG is that it
-    takes care of this automatically in most cases.
-   </para>
-
-   <para>
-    In this respect, there are two kinds of data types: Some simple
-    PostgreSQL data types, such as <type>integer</type>
-    and <type>text</type>, can be read and written by the application
-    directly.  Other PostgreSQL data types, such
-    as <type>timestamp</type> and <type>numeric</type> can only be
-    accessed through special library functions; see
-    <xref linkend="ecpg-special-types">.
-   </para>
-
-   <para>
-    <xref linkend="ecpg-datatype-hostvars-table"> shows which PostgreSQL
-    data types correspond to which C data types.  When you wish to
-    send or receive a value of a given PostgreSQL data type, you
-    should declare a C variable of the corresponding C data type in
-    the declare section.
-   </para>
-
-   <table id="ecpg-datatype-hostvars-table">
-    <title>Mapping Between PostgreSQL Data Types and C Variable Types</title>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>PostgreSQL data type</entry>
-       <entry>Host variable type</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><type>smallint</type></entry>
-       <entry><type>short</type></entry>
-      </row>
-
-      <row>
-       <entry><type>integer</type></entry>
-       <entry><type>int</type></entry>
-      </row>
-
-      <row>
-       <entry><type>bigint</type></entry>
-       <entry><type>long long int</type></entry>
-      </row>
-
-      <row>
-       <entry><type>decimal</type></entry>
-       <entry><type>decimal</type><footnote id="ecpg-datatype-table-fn"><para>This type can only be accessed through special library functions; see <xref linkend="ecpg-special-types">.</para></footnote></entry>
-      </row>
-
-      <row>
-       <entry><type>numeric</type></entry>
-       <entry><type>numeric</type><footnoteref linkend="ecpg-datatype-table-fn"></entry>
-      </row>
-
-      <row>
-       <entry><type>real</type></entry>
-       <entry><type>float</type></entry>
-      </row>
-
-      <row>
-       <entry><type>double precision</type></entry>
-       <entry><type>double</type></entry>
-      </row>
-
-      <row>
-       <entry><type>serial</type></entry>
-       <entry><type>int</type></entry>
-      </row>
-
-      <row>
-       <entry><type>bigserial</type></entry>
-       <entry><type>long long int</type></entry>
-      </row>
-
-      <row>
-       <entry><type>oid</type></entry>
-       <entry><type>unsigned int</type></entry>
-      </row>
-
-      <row>
-       <entry><type>character(<replaceable>n</>)</type>, <type>varchar(<replaceable>n</>)</type>, <type>text</type></entry>
-       <entry><type>char[<replaceable>n</>+1]</type>, <type>VARCHAR[<replaceable>n</>+1]</type><footnote><para>declared in <filename>ecpglib.h</filename></para></footnote></entry>
-      </row>
-
-      <row>
-       <entry><type>name</type></entry>
-       <entry><type>char[NAMEDATALEN]</type></entry>
-      </row>
-
-      <row>
-       <entry><type>timestamp</type></entry>
-       <entry><type>timestamp</type><footnoteref linkend="ecpg-datatype-table-fn"></entry>
-      </row>
-
-      <row>
-       <entry><type>interval</type></entry>
-       <entry><type>interval</type><footnoteref linkend="ecpg-datatype-table-fn"></entry>
-      </row>
-
-      <row>
-       <entry><type>date</type></entry>
-       <entry><type>date</type><footnoteref linkend="ecpg-datatype-table-fn"></entry>
-      </row>
-
-      <row>
-       <entry><type>boolean</type></entry>
-       <entry><type>bool</type><footnote><para>declared in <filename>ecpglib.h</filename> if not native</para></footnote></entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <sect3 id="ecpg-char">
-    <title>Handling Character Strings</title>
-
-&common;
-    <para>
-     To handle SQL character string data types, such
-     as <type>varchar</type> and <type>text</type>, there are two
-     possible ways to declare the host variables.
-    </para>
-
-    <para>
-     One way is using <type>char[]</type>, an array
-     of <type>char</type>, which is the most common way to handle
-     character data in C.
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-    char str[50];
-EXEC SQL END DECLARE SECTION;
-</programlisting>
-     Note that you have to take care of the length yourself.  If you
-     use this host variable as the target variable of a query which
-     returns a string with more than 49 characters, a buffer overflow
-     occurs.
-    </para>
-
-    <para>
-     The other way is using the <type>VARCHAR</type> type, which is a
-     special type provided by ECPG.  The definition on an array of
-     type <type>VARCHAR</type> is converted into a
-     named <type>struct</> for every variable. A declaration like:
-<programlisting>
-VARCHAR var[180];
-</programlisting>
-     is converted into:
-<programlisting>
-struct varchar_var { int len; char arr[180]; } var;
-</programlisting>
-     The member <structfield>arr</structfield> hosts the string
-     including a terminating zero byte.  Thus, to store a string in
-     a <type>VARCHAR</type> host variable, the host variable has to be
-     declared with the length including the zero byte terminator.  The
-     member <structfield>len</structfield> holds the length of the
-     string stored in the <structfield>arr</structfield> without the
-     terminating zero byte.  When a host variable is used as input for
-     a query, if <literal>strlen(arr)</literal>
-     and <structfield>len</structfield> are different, the shorter one
-     is used.
-    </para>
-
-    <para>
-     Two or more <type>VARCHAR</type> host variables cannot be defined
-     in single line statement.  The following code will confuse
-     the <command>ecpg</command> preprocessor:
-<programlisting>
-VARCHAR v1[128], v2[128];   /* WRONG */
-</programlisting>
-     Two variables should be defined in separate statements like this:
-<programlisting>
-VARCHAR v1[128];
-VARCHAR v2[128];
-</programlisting>
-    </para>
-
-    <para>
-     <type>VARCHAR</type> can be written in upper or lower case, but
-     not in mixed case.
-    </para>
-
-    <para>
-     <type>char</type> and <type>VARCHAR</type> host variables can
-     also hold values of other SQL types, which will be stored in
-     their string forms.
-    </para>
-   </sect3>
-
-   <sect3 id="ecpg-special-types">
-    <title>Accessing Special Data Types</title>
-
-&common;
-    <para>
-     ECPG contains some special types that help you to interact easily
-     with some special data types from the PostgreSQL server. In
-     particular, it has implemented support for the
-     <type>numeric</>, <type>decimal</type>, <type>date</>, <type>timestamp</>,
-     and <type>interval</> types.  These data types cannot usefully be
-     mapped to primitive host variable types (such
-     as <type>int</>, <type>long long int</type>,
-     or <type>char[]</type>), because they have a complex internal
-     structure.  Applications deal with these types by declaring host
-     variables in special types and accessing them using functions in
-     the pgtypes library.  The pgtypes library, described in detail
-     in <xref linkend="ecpg-pgtypes"> contains basic functions to deal
-     with those types, such that you do not need to send a query to
-     the SQL server just for adding an interval to a time stamp for
-     example.
-    </para>
-
-    <para>
-     The follow subsections describe these special data types. For
-     more details about pgtypes library functions,
-     see <xref linkend="ecpg-pgtypes">.
-    </para>
-
-    <sect4>
-     <title id="ecpg-type-timestamp-date">timestamp, date</title>
-
-&common;
-     <para>
-      Here is a pattern for handling <type>timestamp</type> variables
-      in the ECPG host application.
-     </para>
-
-     <para>
-      First, the program has to include the header file for the
-      <type>timestamp</type> type:
-<programlisting>
-#include &lt;pgtypes_timestamp.h>
-</programlisting>
-     </para>
-
-     <para>
-      Next, declare a host variable as type <type>timestamp</type> in
-      the declare section:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-timestamp ts;
-EXEC SQL END DECLARE SECTION;
-</programlisting>
-     </para>
-
-     <para>
-      And after reading a value into the host variable, process it
-      using pgtypes library functions. In following example, the
-      <type>timestamp</type> value is converted into text (ASCII) form
-      with the <function>PGTYPEStimestamp_to_asc()</function>
-      function:
-<programlisting>
-EXEC SQL SELECT now()::timestamp INTO :ts;
-
-printf("ts = %s\n", PGTYPEStimestamp_to_asc(ts));
-</programlisting>
-      This example will show some result like following:
-<screen>
-ts = 2010-06-27 18:03:56.949343
-</screen>
-     </para>
-
-     <para>
-      In addition, the DATE type can be handled in the same way. The
-      program has to include <filename>pg_types_date.h</filename>, declare a host variable
-      as the date type and convert a DATE value into a text form using
-      <function>PGTYPESdate_to_asc()</function> function. For more details about the
-      pgtypes library functions, see <xref linkend="ecpg-pgtypes">.
-     </para>
-    </sect4>
-
-    <sect4 id="ecpg-type-interval">
-     <title>interval</title>
-
-&common;
-     <para>
-      The handling of the <type>interval</type> type is also similar
-      to the <type>timestamp</type> and <type>date</type> types.  It
-      is required, however, to allocate memory for
-      an <type>interval</type> type value explicitly.  In other words,
-      the memory space for the variable has to be allocated in the
-      heap memory, not in the stack memory.
-     </para>
-
-     <para>
-      Here is an example program:
-<programlisting>
-#include &lt;stdio.h>
-#include &lt;stdlib.h>
-#include &lt;pgtypes_interval.h>
-
-int
-main(void)
-{
-EXEC SQL BEGIN DECLARE SECTION;
-    interval *in;
-EXEC SQL END DECLARE SECTION;
-
-    EXEC SQL CONNECT TO testdb;
-
-    in = PGTYPESinterval_new();
-    EXEC SQL SELECT '1 min'::interval INTO :in;
-    printf("interval = %s\n", PGTYPESinterval_to_asc(in));
-    PGTYPESinterval_free(in);
-
-    EXEC SQL COMMIT;
-    EXEC SQL DISCONNECT ALL;
-    return 0;
-}
-</programlisting>
-     </para>
-    </sect4>
-
-    <sect4 id="ecpg-type-numeric-decimal">
-     <title>numeric, decimal</title>
-
-&common;
-     <para>
-      The handling of the <type>numeric</type>
-      and <type>decimal</type> types is similar to the
-      <type>interval</type> type: It requires defining a pointer,
-      allocating some memory space on the heap, and accessing the
-      variable using the pgtypes library functions.  For more details
-      about the pgtypes library functions,
-      see <xref linkend="ecpg-pgtypes">.
-     </para>
-
-     <para>
-      No functions are provided specifically for
-      the <type>decimal</type> type.  An application has to convert it
-      to a <type>numeric</type> variable using a pgtypes library
-      function to do further processing.
-     </para>
-
-     <para>
-      Here is an example program handling <type>numeric</type>
-      and <type>decimal</type> type variables.
-<programlisting>
-#include &lt;stdio.h>
-#include &lt;stdlib.h>
-#include &lt;pgtypes_numeric.h>
-
-EXEC SQL WHENEVER SQLERROR STOP;
-
-int
-main(void)
-{
-EXEC SQL BEGIN DECLARE SECTION;
-    numeric *num;
-    numeric *num2;
-    decimal *dec;
-EXEC SQL END DECLARE SECTION;
-
-    EXEC SQL CONNECT TO testdb;
-
-    num = PGTYPESnumeric_new();
-    dec = PGTYPESdecimal_new();
-
-    EXEC SQL SELECT 12.345::numeric(4,2), 23.456::decimal(4,2) INTO :num, :dec;
-
-    printf("numeric = %s\n", PGTYPESnumeric_to_asc(num, 0));
-    printf("numeric = %s\n", PGTYPESnumeric_to_asc(num, 1));
-    printf("numeric = %s\n", PGTYPESnumeric_to_asc(num, 2));
-
-    /* Convert decimal to numeric to show a decimal value. */
-    num2 = PGTYPESnumeric_new();
-    PGTYPESnumeric_from_decimal(dec, num2);
-
-    printf("decimal = %s\n", PGTYPESnumeric_to_asc(num2, 0));
-    printf("decimal = %s\n", PGTYPESnumeric_to_asc(num2, 1));
-    printf("decimal = %s\n", PGTYPESnumeric_to_asc(num2, 2));
-
-    PGTYPESnumeric_free(num2);
-    PGTYPESdecimal_free(dec);
-    PGTYPESnumeric_free(num);
-
-    EXEC SQL COMMIT;
-    EXEC SQL DISCONNECT ALL;
-    return 0;
-}
-</programlisting>
-     </para>
-    </sect4>
-   </sect3>
-
-   <sect3 id="ecpg-variables-nonprimitive-c">
-    <title>Host Variables with Nonprimitive Types</title>
-
-&common;
-    <para>
-     As a host variable you can also use arrays, typedefs, structs, and
-     pointers.
-    </para>
-
-    <sect4 id="ecpg-variables-arrays">
-     <title>Arrays</title>
-
-&common;
-     <para>
-      There are two use cases for arrays as host variables.  The first
-      is a way to store some text string in <type>char[]</type>
-      or <type>VARCHAR[]</type>, as
-      explained <xref linkend="ecpg-char">.  The second use case is to
-      retrieve multiple rows from a query result without using a
-      cursor.  Without an array, to process a query result consisting
-      of multiple rows, it is required to use a cursor and
-      the <command>FETCH</command> command.  But with array host
-      variables, multiple rows can be received at once.  The length of
-      the array has to be defined to be able to accommodate all rows,
-      otherwise a buffer overflow will likely occur.
-     </para>
-
-     <para>
-      Following example scans the <literal>pg_database</literal>
-      system table and shows all OIDs and names of the available
-      databases:
-<programlisting>
-int
-main(void)
-{
-EXEC SQL BEGIN DECLARE SECTION;
-    int dbid[8];
-    char dbname[8][16];
-    int i;
-EXEC SQL END DECLARE SECTION;
-
-    memset(dbname, 0, sizeof(char)* 16 * 8);
-    memset(dbid, 0, sizeof(int) * 8);
-
-    EXEC SQL CONNECT TO testdb;
-
-    /* Retrieve multiple rows into arrays at once. */
-    EXEC SQL SELECT oid,datname INTO :dbid, :dbname FROM pg_database;
-
-    for (i = 0; i &lt; 8; i++)
-        printf("oid=%d, dbname=%s\n", dbid[i], dbname[i]);
-
-    EXEC SQL COMMIT;
-    EXEC SQL DISCONNECT ALL;
-    return 0;
-}
-</programlisting>
-
-    This example shows following result. (The exact values depend on
-    local circumstances.)
-<screen>
-oid=1, dbname=template1
-oid=11510, dbname=template0
-oid=11511, dbname=postgres
-oid=313780, dbname=testdb
-oid=0, dbname=
-oid=0, dbname=
-oid=0, dbname=
-</screen>
-     </para>
-    </sect4>
-
-    <sect4 id="ecpg-variables-struct">
-     <title>Structures</title>
-
-&common;
-     <para>
-      A structure whose member names match the column names of a query
-      result, can be used to retrieve multiple columns at once.  The
-      structure enables handling multiple column values in a single
-      host variable.
-     </para>
-
-     <para>
-      The following example retrieves OIDs, names, and sizes of the
-      available databases from the <literal>pg_database</literal>
-      system table and using
-      the <function>pg_database_size()</function> function.  In this
-      example, a structure variable <varname>dbinfo_t</varname> with
-      members whose names match each column in
-      the <literal>SELECT</literal> result is used to retrieve one
-      result row without putting multiple host variables in
-      the <literal>FETCH</literal> statement.
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-    typedef struct
-    {
-       int oid;
-       char datname[65];
-       long long int size;
-    } dbinfo_t;
-
-    dbinfo_t dbval;
-EXEC SQL END DECLARE SECTION;
-
-    memset(&amp;dbval, 0, sizeof(dbinfo_t));
-
-    EXEC SQL DECLARE cur1 CURSOR FOR SELECT oid, datname, pg_database_size(oid) AS size FROM pg_database;
-    EXEC SQL OPEN cur1;
-
-    /* when end of result set reached, break out of while loop */
-    EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-    while (1)
-    {
-        /* Fetch multiple columns into one structure. */
-        EXEC SQL FETCH FROM cur1 INTO :dbval;
-
-        /* Print members of the structure. */
-        printf("oid=%d, datname=%s, size=%lld\n", dbval.oid, dbval.datname, dbval.size);
-    }
-
-    EXEC SQL CLOSE cur1;
-</programlisting>
-     </para>
-
-     <para>
-      This example shows following result. (The exact values depend on
-      local circumstances.)
-<screen>
-oid=1, datname=template1, size=4324580
-oid=11510, datname=template0, size=4243460
-oid=11511, datname=postgres, size=4324580
-oid=313780, datname=testdb, size=8183012
-</screen>
-     </para>
-
-     <para>
-      Structure host variables <quote>absorb</quote> as many columns
-      as the structure as fields.  Additional columns can be assigned
-      to other host variables. For example, the above program could
-      also be restructured like this, with the <varname>size</varname>
-      variable outside the structure:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-    typedef struct
-    {
-       int oid;
-       char datname[65];
-    } dbinfo_t;
-
-    dbinfo_t dbval;
-    long long int size;
-EXEC SQL END DECLARE SECTION;
-
-    memset(&amp;dbval, 0, sizeof(dbinfo_t));
-
-    EXEC SQL DECLARE cur1 CURSOR FOR SELECT oid, datname, pg_database_size(oid) AS size FROM pg_database;
-    EXEC SQL OPEN cur1;
-
-    /* when end of result set reached, break out of while loop */
-    EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-    while (1)
-    {
-        /* Fetch multiple columns into one structure. */
-        EXEC SQL FETCH FROM cur1 INTO :dbval, :size;
-
-        /* Print members of the structure. */
-        printf("oid=%d, datname=%s, size=%lld\n", dbval.oid, dbval.datname, size);
-    }
-
-    EXEC SQL CLOSE cur1;
-</programlisting>
-     </para>
-    </sect4>
-
-    <sect4>
-     <title>Typedefs</title>
-
-&common;
-    <para>
-      Use the <literal>typedef</literal> keyword to map new types to already
-      existing types.
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-    typedef char mychartype[40];
-    typedef long serial_t;
-EXEC SQL END DECLARE SECTION;
-</programlisting>
-      Note that you could also use:
-<programlisting>
-EXEC SQL TYPE serial_t IS long;
-</programlisting>
-      This declaration does not need to be part of a declare section.
-     </para>
-    </sect4>
-
-    <sect4>
-     <title>Pointers</title>
-
-&common;
-     <para>
-      You can declare pointers to the most common types. Note however
-      that you cannot use pointers as target variables of queries
-      without auto-allocation. See <xref linkend="ecpg-descriptors">
-      for more information on auto-allocation.
-     </para>
-
-     <para>
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-    int   *intp;
-    char **charp;
-EXEC SQL END DECLARE SECTION;
-</programlisting>
-     </para>
-    </sect4>
-   </sect3>
-  </sect2>
-
-  <sect2 id="ecpg-variables-nonprimitive-sql">
-   <title>Handling Nonprimitive SQL Data Types</title>
-
-&common;
-   <para>
-    This section contains information on how to handle nonscalar and
-    user-defined SQL-level data types in ECPG applications.  Note that
-    this is distinct from the handling of host variables of
-    nonprimitive types, described in the previous section.
-   </para>
-
-   <sect3>
-    <title>Arrays</title>
-
-&common;
-    <para>
-     SQL-level arrays are not directly supported in ECPG.  It is not
-     possible to simply map an SQL array into a C array host variable.
-     This will result in undefined behavior.  Some workarounds exist,
-     however.
-    </para>
-
-    <para>
-     If a query accesses <emphasis>elements</emphasis> of an array
-     separately, then this avoids the use of arrays in ECPG.  Then, a
-     host variable with a type that can be mapped to the element type
-     should be used.  For example, if a column type is array of
-     <type>integer</type>, a host variable of type <type>int</type>
-     can be used.  Also if the element type is <type>varchar</type>
-     or <type>text</type>, a host variable of type <type>char[]</type>
-     or <type>VARCHAR[]</type> can be used.
-    </para>
-
-    <para>
-     Here is an example.  Assume the following table:
-<programlisting>
-CREATE TABLE t3 (
-    ii integer[]
-);
-
-testdb=> SELECT * FROM t3;
-     ii
--------------
- {1,2,3,4,5}
-(1 row)
-</programlisting>
-
-     The following example program retrieves the 4th element of the
-     array and stores it into a host variable of
-     type <type>int</type>:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-int ii;
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL DECLARE cur1 CURSOR FOR SELECT ii[4] FROM t3;
-EXEC SQL OPEN cur1;
-
-EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-while (1)
-{
-    EXEC SQL FETCH FROM cur1 INTO :ii ;
-    printf("ii=%d\n", ii);
-}
-
-EXEC SQL CLOSE cur1;
-</programlisting>
-
-     This example shows the following result:
-<screen>
-ii=4
-</screen>
-    </para>
-
-    <para>
-     To map multiple array elements to the multiple elements in an
-     array type host variables each element of array column and each
-     element of the host variable array have to be managed separately,
-     for example:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-int ii_a[8];
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL DECLARE cur1 CURSOR FOR SELECT ii[1], ii[2], ii[3], ii[4] FROM t3;
-EXEC SQL OPEN cur1;
-
-EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-while (1)
-{
-    EXEC SQL FETCH FROM cur1 INTO :ii_a[0], :ii_a[1], :ii_a[2], :ii_a[3];
-    ...
-}
-</programlisting>
-    </para>
-
-    <para>
-     Note again that
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-int ii_a[8];
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL DECLARE cur1 CURSOR FOR SELECT ii FROM t3;
-EXEC SQL OPEN cur1;
-
-EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-while (1)
-{
-    /* WRONG */
-    EXEC SQL FETCH FROM cur1 INTO :ii_a;
-    ...
-}
-</programlisting>
-     would not work correctly in this case, because you cannot map an
-     array type column to an array host variable directly.
-    </para>
-
-    <para>
-     Another workaround is to store arrays in their external string
-     representation in host variables of type <type>char[]</type>
-     or <type>VARCHAR[]</type>.  For more details about this
-     representation, see <xref linkend="arrays-input">.  Note that
-     this means that the array cannot be accessed naturally as an
-     array in the host program (without further processing that parses
-     the text representation).
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Composite Types</title>
-
-&common;
-    <para>
-     Composite types are not directly supported in ECPG, but an easy workaround is possible.
-  The
-     available workarounds are similar to the ones described for
-     arrays above: Either access each attribute separately or use the
-     external string representation.
-    </para>
-
-    <para>
-     For the following examples, assume the following type and table:
-<programlisting>
-CREATE TYPE comp_t AS (intval integer, textval varchar(32));
-CREATE TABLE t4 (compval comp_t);
-INSERT INTO t4 VALUES ( (256, 'PostgreSQL') );
-</programlisting>
-
-     The most obvious solution is to access each attribute separately.
-     The following program retrieves data from the example table by
-     selecting each attribute of the type <type>comp_t</type>
-     separately:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-int intval;
-varchar textval[33];
-EXEC SQL END DECLARE SECTION;
-
-/* Put each element of the composite type column in the SELECT list. */
-EXEC SQL DECLARE cur1 CURSOR FOR SELECT (compval).intval, (compval).textval FROM t4;
-EXEC SQL OPEN cur1;
-
-EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-while (1)
-{
-    /* Fetch each element of the composite type column into host variables. */
-    EXEC SQL FETCH FROM cur1 INTO :intval, :textval;
-
-    printf("intval=%d, textval=%s\n", intval, textval.arr);
-}
-
-EXEC SQL CLOSE cur1;
-</programlisting>
-    </para>
-
-    <para>
-     To enhance this example, the host variables to store values in
-     the <command>FETCH</command> command can be gathered into one
-     structure.  For more details about the host variable in the
-     structure form, see <xref linkend="ecpg-variables-struct">.
-     To switch to the structure, the example can be modified as below.
-     The two host variables, <varname>intval</varname>
-     and <varname>textval</varname>, become members of
-     the <structname>comp_t</structname> structure, and the structure
-     is specified on the <command>FETCH</command> command.
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-typedef struct
-{
-    int intval;
-    varchar textval[33];
-} comp_t;
-
-comp_t compval;
-EXEC SQL END DECLARE SECTION;
-
-/* Put each element of the composite type column in the SELECT list. */
-EXEC SQL DECLARE cur1 CURSOR FOR SELECT (compval).intval, (compval).textval FROM t4;
-EXEC SQL OPEN cur1;
-
-EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-while (1)
-{
-    /* Put all values in the SELECT list into one structure. */
-    EXEC SQL FETCH FROM cur1 INTO :compval;
-
-    printf("intval=%d, textval=%s\n", compval.intval, compval.textval.arr);
-}
-
-EXEC SQL CLOSE cur1;
-</programlisting>
-
-     Although a structure is used in the <command>FETCH</command>
-     command, the attribute names in the <command>SELECT</command>
-     clause are specified one by one.  This can be enhanced by using
-     a <literal>*</literal> to ask for all attributes of the composite
-     type value.
-<programlisting>
-...
-EXEC SQL DECLARE cur1 CURSOR FOR SELECT (compval).* FROM t4;
-EXEC SQL OPEN cur1;
-
-EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-while (1)
-{
-    /* Put all values in the SELECT list into one structure. */
-    EXEC SQL FETCH FROM cur1 INTO :compval;
-
-    printf("intval=%d, textval=%s\n", compval.intval, compval.textval.arr);
-}
-...
-</programlisting>
-     This way, composite types can be mapped into structures almost
-     seamlessly, even though ECPG does not understand the composite
-     type itself.
-    </para>
-
-    <para>
-     Finally, it is also possible to store composite type values in
-     their external string representation in host variables of
-     type <type>char[]</type> or <type>VARCHAR[]</type>.  But that
-     way, it is not easily possible to access the fields of the value
-     from the host program.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>User-defined Base Types</title>
-
-&common;
-    <para>
-     New user-defined base types are not directly supported by ECPG.
-     You can use the external string representation and host variables
-     of type <type>char[]</type> or <type>VARCHAR[]</type>, and this
-     solution is indeed appropriate and sufficient for many types.
-    </para>
-
-    <para>
-     Here is an example using the data type <type>complex</type> from
-     the example in <xref linkend="xtypes">.  The external string
-     representation of that type is <literal>(%lf,%lf)</literal>,
-     which is defined in the
-     functions <function>complex_in()</function>
-     and <function>complex_out()</function> functions
-     in <xref linkend="xtypes">.  The following example inserts the
-     complex type values <literal>(1,1)</literal>
-     and <literal>(3,3)</literal> into the
-     columns <literal>a</literal> and <literal>b</literal>, and select
-     them from the table after that.
-
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-    varchar a[64];
-    varchar b[64];
-EXEC SQL END DECLARE SECTION;
-
-    EXEC SQL INSERT INTO test_complex VALUES ('(1,1)', '(3,3)');
-
-    EXEC SQL DECLARE cur1 CURSOR FOR SELECT a, b FROM test_complex;
-    EXEC SQL OPEN cur1;
-
-    EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-    while (1)
-    {
-        EXEC SQL FETCH FROM cur1 INTO :a, :b;
-        printf("a=%s, b=%s\n", a.arr, b.arr);
-    }
-
-    EXEC SQL CLOSE cur1;
-</programlisting>
-
-     This example shows following result:
-<screen>
-a=(1,1), b=(3,3)
-</screen>
-   </para>
-
-    <para>
-     Another workaround is avoiding the direct use of the user-defined
-     types in ECPG and instead create a function or cast that converts
-     between the user-defined type and a primitive type that ECPG can
-     handle.  Note, however, that type casts, especially implicit
-     ones, should be introduced into the type system very carefully.
-    </para>
-
-    <para>
-     For example,
-<programlisting>
-CREATE FUNCTION create_complex(r double, i double) RETURNS complex
-LANGUAGE SQL
-IMMUTABLE
-AS $$ SELECT $1 * complex '(1,0')' + $2 * complex '(0,1)' $$;
-</programlisting>
-    After this definition, the following
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-double a, b, c, d;
-EXEC SQL END DECLARE SECTION;
-
-a = 1;
-b = 2;
-c = 3;
-d = 4;
-
-EXEC SQL INSERT INTO test_complex VALUES (create_complex(:a, :b), create_complex(:c, :d));
-</programlisting>
-    has the same effect as
-<programlisting>
-EXEC SQL INSERT INTO test_complex VALUES ('(1,2)', '(3,4)');
-</programlisting>
-    </para>
-   </sect3>
-  </sect2>
-
-  <sect2 id="ecpg-indicators">
-   <title>Indicators</title>
-
-&common;
-   <para>
-    The examples above do not handle null values.  In fact, the
-    retrieval examples will raise an error if they fetch a null value
-    from the database.  To be able to pass null values to the database
-    or retrieve null values from the database, you need to append a
-    second host variable specification to each host variable that
-    contains data.  This second host variable is called the
-    <firstterm>indicator</firstterm> and contains a flag that tells
-    whether the datum is null, in which case the value of the real
-    host variable is ignored.  Here is an example that handles the
-    retrieval of null values correctly:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-VARCHAR val;
-int val_ind;
-EXEC SQL END DECLARE SECTION:
-
- ...
-
-EXEC SQL SELECT b INTO :val :val_ind FROM test1;
-</programlisting>
-    The indicator variable <varname>val_ind</varname> will be zero if
-    the value was not null, and it will be negative if the value was
-    null.
-   </para>
-
-   <para>
-    The indicator has another function: if the indicator value is
-    positive, it means that the value is not null, but it was
-    truncated when it was stored in the host variable.
-   </para>
-
-   <para>
-    If the argument <literal>-r no_indicator</literal> is passed to
-    the preprocessor <command>ecpg</command>, it works in
-    <quote>no-indicator</quote> mode. In no-indicator mode, if no
-    indicator variable is specified, null values are signaled (on
-    input and output) for character string types as empty string and
-    for integer types as the lowest possible value for type (for
-    example, <symbol>INT_MIN</symbol> for <type>int</type>).
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="ecpg-dynamic">
-  <title>Dynamic SQL</title>
-
-&common;
-  <para>
-   In many cases, the particular SQL statements that an application
-   has to execute are known at the time the application is written.
-   In some cases, however, the SQL statements are composed at run time
-   or provided by an external source.  In these cases you cannot embed
-   the SQL statements directly into the C source code, but there is a
-   facility that allows you to call arbitrary SQL statements that you
-   provide in a string variable.
-  </para>
-
-  <sect2 id="ecpg-dynamic-without-result">
-   <title>Executing Statements without a Result Set</title>
-
-&common;
-   <para>
-    The simplest way to execute an arbitrary SQL statement is to use
-    the command <command>EXECUTE IMMEDIATE</command>.  For example:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-const char *stmt = "CREATE TABLE test1 (...);";
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL EXECUTE IMMEDIATE :stmt;
-</programlisting>
-    <command>EXECUTE IMMEDIATE</command> can be used for SQL
-    statements that do not return a result set (e.g.,
-    DDL, <command>INSERT</command>, <command>UPDATE</command>,
-    <command>DELETE</command>).  You cannot execute statements that
-    retrieve data (e.g., <command>SELECT</command>) this way.  The
-    next section describes how to do that.
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-dynamic-input">
-   <title>Executing a Statement with Input Parameters</title>
-
-&common;
-   <para>
-    A more powerful way to execute arbitrary SQL statements is to
-    prepare them once and execute the prepared statement as often as
-    you like.  It is also possible to prepare a generalized version of
-    a statement and then execute specific versions of it by
-    substituting parameters.  When preparing the statement, write
-    question marks where you want to substitute parameters later.  For
-    example:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-const char *stmt = "INSERT INTO test1 VALUES(?, ?);";
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL PREPARE mystmt FROM :stmt;
- ...
-EXEC SQL EXECUTE mystmt USING 42, 'foobar';
-</programlisting>
-   </para>
-
-   <para>
-    When you don't need the prepared statement anymore, you should
-    deallocate it:
-<programlisting>
-EXEC SQL DEALLOCATE PREPARE <replaceable>name</replaceable>;
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-dynamic-with-result">
-   <title>Executing a Statement with a Result Set</title>
-
-&common;
-   <para>
-    To execute an SQL statement with a single result row,
-    <command>EXECUTE</command> can be used.  To save the result, add
-    an <literal>INTO</literal> clause.
-<programlisting><![CDATA[
-EXEC SQL BEGIN DECLARE SECTION;
-const char *stmt = "SELECT a, b, c FROM test1 WHERE a > ?";
-int v1, v2;
-VARCHAR v3[50];
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL PREPARE mystmt FROM :stmt;
- ...
-EXEC SQL EXECUTE mystmt INTO :v1, :v2, :v3 USING 37;
-]]>
-</programlisting>
-    An <command>EXECUTE</command> command can have an
-    <literal>INTO</literal> clause, a <literal>USING</literal> clause,
-    both, or neither.
-   </para>
-
-   <para>
-    If a query is expected to return more than one result row, a
-    cursor should be used, as in the following example.
-    (See <xref linkend="ecpg-cursors"> for more details about the
-    cursor.)
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-char dbaname[128];
-char datname[128];
-char *stmt = "SELECT u.usename as dbaname, d.datname "
-             "  FROM pg_database d, pg_user u "
-             "  WHERE d.datdba = u.usesysid";
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL CONNECT TO testdb AS con1 USER testuser;
-
-EXEC SQL PREPARE stmt1 FROM :stmt;
-
-EXEC SQL DECLARE cursor1 CURSOR FOR stmt1;
-EXEC SQL OPEN cursor1;
-
-EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-while (1)
-{
-    EXEC SQL FETCH cursor1 INTO :dbaname,:datname;
-    printf("dbaname=%s, datname=%s\n", dbaname, datname);
-}
-
-EXEC SQL CLOSE cursor1;
-
-EXEC SQL COMMIT;
-EXEC SQL DISCONNECT ALL;
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="ecpg-pgtypes">
-  <title>pgtypes Library</title>
-
-&common;
-  <para>
-   The pgtypes library maps <productname>PostgreSQL</productname> database
-   types to C equivalents that can be used in C programs. It also offers
-   functions to do basic calculations with those types within C, i.e., without
-   the help of the <productname>PostgreSQL</productname> server. See the
-   following example:
-<programlisting><![CDATA[
-EXEC SQL BEGIN DECLARE SECTION;
-   date date1;
-   timestamp ts1, tsout;
-   interval iv1;
-   char *out;
-EXEC SQL END DECLARE SECTION;
-
-PGTYPESdate_today(&date1);
-EXEC SQL SELECT started, duration INTO :ts1, :iv1 FROM datetbl WHERE d=:date1;
-PGTYPEStimestamp_add_interval(&ts1, &iv1, &tsout);
-out = PGTYPEStimestamp_to_asc(&tsout);
-printf("Started + duration: %s\n", out);
-free(out);
-]]>
-</programlisting>
-  </para>
-
-  <sect2 id="ecpg-pgtypes-numeric">
-   <title>The numeric Type</title>
-&common;
-   <para>
-    The numeric type offers to do calculations with arbitrary precision. See
-    <xref linkend="datatype-numeric"> for the equivalent type in the
-    <productname>PostgreSQL</> server. Because of the arbitrary precision this
-    variable needs to be able to expand and shrink dynamically. That's why you
-    can only create numeric variables on the heap, by means of the
-    <function>PGTYPESnumeric_new</> and <function>PGTYPESnumeric_free</>
-    functions. The decimal type, which is similar but limited in precision,
-    can be created on the stack as well as on the heap.
-   </para>
-   <para>
-   The following functions can be used to work with the numeric type:
-   <variablelist>
-    <varlistentry>
-     <term><function>PGTYPESnumeric_new</function></term>
-     <listitem>
-      <para>
-      Request a pointer to a newly allocated numeric variable.
-<synopsis>
-numeric *PGTYPESnumeric_new(void);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_free</function></term>
-     <listitem>
-      <para>
-      Free a numeric type, release all of its memory.
-<synopsis>
-void PGTYPESnumeric_free(numeric *var);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_from_asc</function></term>
-     <listitem>
-      <para>
-       Parse a numeric type from its string notation.
-<synopsis>
-numeric *PGTYPESnumeric_from_asc(char *str, char **endptr);
-</synopsis>
-       Valid formats are for example:
-        <literal>-2</literal>,
-        <literal>.794</literal>,
-        <literal>+3.44</literal>,
-        <literal>592.49E07</literal> or
-        <literal>-32.84e-4</literal>.
-       If the value could be parsed successfully, a valid pointer is returned,
-       else the NULL pointer. At the moment ECPG always parses the complete
-       string and so it currently does not support to store the address of the
-       first invalid character in <literal>*endptr</literal>. You can safely
-       set <literal>endptr</literal> to NULL.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_to_asc</function></term>
-     <listitem>
-      <para>
-       Returns a pointer to a string allocated by <function>malloc</function> that contains the string
-       representation of the numeric type <literal>num</literal>.
-<synopsis>
-char *PGTYPESnumeric_to_asc(numeric *num, int dscale);
-</synopsis>
-       The numeric value will be printed with <literal>dscale</literal> decimal
-       digits, with rounding applied if necessary.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_add</function></term>
-     <listitem>
-      <para>
-       Add two numeric variables into a third one.
-<synopsis>
-int PGTYPESnumeric_add(numeric *var1, numeric *var2, numeric *result);
-</synopsis>
-       The function adds the variables <literal>var1</literal> and
-       <literal>var2</literal> into the result variable
-       <literal>result</literal>.
-       The function returns 0 on success and -1 in case of error.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_sub</function></term>
-     <listitem>
-      <para>
-       Subtract two numeric variables and return the result in a third one.
-<synopsis>
-int PGTYPESnumeric_sub(numeric *var1, numeric *var2, numeric *result);
-</synopsis>
-       The function subtracts the variable <literal>var2</literal> from
-       the variable <literal>var1</literal>. The result of the operation is
-       stored in the variable <literal>result</literal>.
-       The function returns 0 on success and -1 in case of error.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_mul</function></term>
-     <listitem>
-      <para>
-       Multiply two numeric variables and return the result in a third one.
-<synopsis>
-int PGTYPESnumeric_mul(numeric *var1, numeric *var2, numeric *result);
-</synopsis>
-       The function multiplies the variables <literal>var1</literal> and
-       <literal>var2</literal>. The result of the operation is stored in the
-       variable <literal>result</literal>.
-       The function returns 0 on success and -1 in case of error.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_div</function></term>
-     <listitem>
-      <para>
-       Divide two numeric variables and return the result in a third one.
-<synopsis>
-int PGTYPESnumeric_div(numeric *var1, numeric *var2, numeric *result);
-</synopsis>
-       The function divides the variables <literal>var1</literal> by
-       <literal>var2</literal>. The result of the operation is stored in the
-       variable <literal>result</literal>.
-       The function returns 0 on success and -1 in case of error.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_cmp</function></term>
-     <listitem>
-      <para>
-       Compare two numeric variables.
-<synopsis>
-int PGTYPESnumeric_cmp(numeric *var1, numeric *var2)
-</synopsis>
-       This function compares two numeric variables. In case of error,
-       <literal>INT_MAX</literal> is returned. On success, the function
-       returns one of three possible results:
-       <itemizedlist>
-        <listitem>
-         <para>
-          1, if <literal>var1</> is bigger than <literal>var2</>
-         </para>
-        </listitem>
-        <listitem>
-         <para>
-          -1, if <literal>var1</> is smaller than <literal>var2</>
-         </para>
-        </listitem>
-        <listitem>
-         <para>
-          0, if <literal>var1</> and <literal>var2</> are equal
-         </para>
-        </listitem>
-       </itemizedlist>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_from_int</function></term>
-     <listitem>
-      <para>
-       Convert an int variable to a numeric variable.
-<synopsis>
-int PGTYPESnumeric_from_int(signed int int_val, numeric *var);
-</synopsis>
-       This function accepts a variable of type signed int and stores it
-       in the numeric variable <literal>var</>. Upon success, 0 is returned and
-       -1 in case of a failure.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_from_long</function></term>
-     <listitem>
-      <para>
-       Convert a long int variable to a numeric variable.
-<synopsis>
-int PGTYPESnumeric_from_long(signed long int long_val, numeric *var);
-</synopsis>
-       This function accepts a variable of type signed long int and stores it
-       in the numeric variable <literal>var</>. Upon success, 0 is returned and
-       -1 in case of a failure.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_copy</function></term>
-     <listitem>
-      <para>
-       Copy over one numeric variable into another one.
-<synopsis>
-int PGTYPESnumeric_copy(numeric *src, numeric *dst);
-</synopsis>
-       This function copies over the value of the variable that
-       <literal>src</literal> points to into the variable that <literal>dst</>
-       points to. It returns 0 on success and -1 if an error occurs.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_from_double</function></term>
-     <listitem>
-      <para>
-       Convert a variable of type double to a numeric.
-<synopsis>
-int  PGTYPESnumeric_from_double(double d, numeric *dst);
-</synopsis>
-       This function accepts a variable of type double and stores the result
-       in the variable that <literal>dst</> points to. It returns 0 on success
-       and -1 if an error occurs.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_to_double</function></term>
-     <listitem>
-      <para>
-       Convert a variable of type numeric to double.
-<synopsis>
-int PGTYPESnumeric_to_double(numeric *nv, double *dp)
-</synopsis>
-       The function converts the numeric value from the variable that
-       <literal>nv</> points to into the double variable that <literal>dp</> points
-       to. It returns 0 on success and -1 if an error occurs, including
-       overflow. On overflow, the global variable <literal>errno</> will be set
-       to <literal>PGTYPES_NUM_OVERFLOW</> additionally.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_to_int</function></term>
-     <listitem>
-      <para>
-       Convert a variable of type numeric to int.
-<synopsis>
-int PGTYPESnumeric_to_int(numeric *nv, int *ip);
-</synopsis>
-       The function converts the numeric value from the variable that
-       <literal>nv</> points to into the integer variable that <literal>ip</>
-       points to. It returns 0 on success and -1 if an error occurs, including
-       overflow. On overflow, the global variable <literal>errno</> will be set
-       to <literal>PGTYPES_NUM_OVERFLOW</> additionally.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_to_long</function></term>
-     <listitem>
-      <para>
-       Convert a variable of type numeric to long.
-<synopsis>
-int PGTYPESnumeric_to_long(numeric *nv, long *lp);
-</synopsis>
-       The function converts the numeric value from the variable that
-       <literal>nv</> points to into the long integer variable that
-       <literal>lp</> points to. It returns 0 on success and -1 if an error
-       occurs, including overflow. On overflow, the global variable
-       <literal>errno</> will be set to <literal>PGTYPES_NUM_OVERFLOW</>
-       additionally.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_to_decimal</function></term>
-     <listitem>
-      <para>
-       Convert a variable of type numeric to decimal.
-<synopsis>
-int PGTYPESnumeric_to_decimal(numeric *src, decimal *dst);
-</synopsis>
-       The function converts the numeric value from the variable that
-       <literal>src</> points to into the decimal variable that
-       <literal>dst</> points to. It returns 0 on success and -1 if an error
-       occurs, including overflow. On overflow, the global variable
-       <literal>errno</> will be set to <literal>PGTYPES_NUM_OVERFLOW</>
-       additionally.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>PGTYPESnumeric_from_decimal</function></term>
-     <listitem>
-      <para>
-       Convert a variable of type decimal to numeric.
-<synopsis>
-int PGTYPESnumeric_from_decimal(decimal *src, numeric *dst);
-</synopsis>
-       The function converts the decimal value from the variable that
-       <literal>src</> points to into the numeric variable that
-       <literal>dst</> points to. It returns 0 on success and -1 if an error
-       occurs. Since the decimal type is implemented as a limited version of
-       the numeric type, overflow cannot occur with this conversion.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-pgtypes-date">
-   <title>The date Type</title>
-&common;
-   <para>
-    The date type in C enables your programs to deal with data of the SQL type
-    date. See <xref linkend="datatype-datetime"> for the equivalent type in the
-    <productname>PostgreSQL</> server.
-   </para>
-   <para>
-    The following functions can be used to work with the date type:
-    <variablelist>
-     <varlistentry id="PGTYPESdatefromtimestamp">
-      <term><function>PGTYPESdate_from_timestamp</function></term>
-      <listitem>
-       <para>
-        Extract the date part from a timestamp.
-<synopsis>
-date PGTYPESdate_from_timestamp(timestamp dt);
-</synopsis>
-        The function receives a timestamp as its only argument and returns the
-        extracted date part from this timestamp.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESdatefromasc">
-      <term><function>PGTYPESdate_from_asc</function></term>
-      <listitem>
-       <para>
-       Parse a date from its textual representation.
-<synopsis>
-date PGTYPESdate_from_asc(char *str, char **endptr);
-</synopsis>
-        The function receives a C char* string <literal>str</> and a pointer to
-        a C char* string <literal>endptr</>. At the moment ECPG always parses
-        the complete string and so it currently does not support to store the
-        address of the first invalid character in <literal>*endptr</literal>.
-        You can safely set <literal>endptr</literal> to NULL.
-       </para>
-       <para>
-        Note that the function always assumes MDY-formatted dates and there is
-        currently no variable to change that within ECPG.
-       </para>
-       <para>
-        <xref linkend="ecpg-pgtypesdate-from-asc-table"> shows the allowed input formats.
-       </para>
-        <table id="ecpg-pgtypesdate-from-asc-table">
-         <title>Valid Input Formats for <function>PGTYPESdate_from_asc</function></title>
-         <tgroup cols="2">
-          <thead>
-           <row>
-            <entry>Input</entry>
-            <entry>Result</entry>
-           </row>
-          </thead>
-          <tbody>
-           <row>
-            <entry><literal>January 8, 1999</literal></entry>
-            <entry><literal>January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>1999-01-08</literal></entry>
-            <entry><literal>January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>1/8/1999</literal></entry>
-            <entry><literal>January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>1/18/1999</literal></entry>
-            <entry><literal>January 18, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>01/02/03</literal></entry>
-            <entry><literal>February 1, 2003</literal></entry>
-           </row>
-           <row>
-            <entry><literal>1999-Jan-08</literal></entry>
-            <entry><literal>January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>Jan-08-1999</literal></entry>
-            <entry><literal>January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>08-Jan-1999</literal></entry>
-            <entry><literal>January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>99-Jan-08</literal></entry>
-            <entry><literal>January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>08-Jan-99</literal></entry>
-            <entry><literal>January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>08-Jan-06</literal></entry>
-            <entry><literal>January 8, 2006</literal></entry>
-           </row>
-           <row>
-            <entry><literal>Jan-08-99</literal></entry>
-            <entry><literal>January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>19990108</literal></entry>
-            <entry><literal>ISO 8601; January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>990108</literal></entry>
-            <entry><literal>ISO 8601; January 8, 1999</literal></entry>
-           </row>
-           <row>
-            <entry><literal>1999.008</literal></entry>
-            <entry><literal>year and day of year</literal></entry>
-           </row>
-           <row>
-            <entry><literal>J2451187</literal></entry>
-            <entry><literal>Julian day</literal></entry>
-           </row>
-           <row>
-            <entry><literal>January 8, 99 BC</literal></entry>
-            <entry><literal>year 99 before the Common Era</literal></entry>
-           </row>
-          </tbody>
-         </tgroup>
-        </table>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESdatetoasc">
-      <term><function>PGTYPESdate_to_asc</function></term>
-      <listitem>
-       <para>
-        Return the textual representation of a date variable.
-<synopsis>
-char *PGTYPESdate_to_asc(date dDate);
-</synopsis>
-        The function receives the date <literal>dDate</> as its only parameter.
-        It will output the date in the form <literal>1999-01-18</>, i.e., in the
-        <literal>YYYY-MM-DD</> format.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESdatejulmdy">
-      <term><function>PGTYPESdate_julmdy</function></term>
-      <listitem>
-       <para>
-        Extract the values for the day, the month and the year from a variable
-        of type date.
-<synopsis>
-void PGTYPESdate_julmdy(date d, int *mdy);
-</synopsis>
-       <!-- almost same description as for rjulmdy() -->
-        The function receives the date <literal>d</> and a pointer to an array
-        of 3 integer values <literal>mdy</>. The variable name indicates
-        the sequential order: <literal>mdy[0]</> will be set to contain the
-        number of the month, <literal>mdy[1]</> will be set to the value of the
-        day and <literal>mdy[2]</> will contain the year.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESdatemdyjul">
-      <term><function>PGTYPESdate_mdyjul</function></term>
-      <listitem>
-       <para>
-        Create a date value from an array of 3 integers that specify the
-        day, the month and the year of the date.
-<synopsis>
-void PGTYPESdate_mdyjul(int *mdy, date *jdate);
-</synopsis>
-        The function receives the array of the 3 integers (<literal>mdy</>) as
-        its first argument and as its second argument a pointer to a variable
-        of type date that should hold the result of the operation.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESdatedayofweek">
-      <term><function>PGTYPESdate_dayofweek</function></term>
-      <listitem>
-       <para>
-        Return a number representing the day of the week for a date value.
-<synopsis>
-int PGTYPESdate_dayofweek(date d);
-</synopsis>
-        The function receives the date variable <literal>d</> as its only
-        argument and returns an integer that indicates the day of the week for
-        this date.
-        <itemizedlist>
-         <listitem>
-          <para>
-           0 - Sunday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           1 - Monday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           2 - Tuesday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           3 - Wednesday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           4 - Thursday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           5 - Friday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           6 - Saturday
-          </para>
-         </listitem>
-        </itemizedlist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESdatetoday">
-      <term><function>PGTYPESdate_today</function></term>
-      <listitem>
-       <para>
-        Get the current date.
-<synopsis>
-void PGTYPESdate_today(date *d);
-</synopsis>
-        The function receives a pointer to a date variable (<literal>d</>)
-        that it sets to the current date.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESdatefmtasc">
-      <term><function>PGTYPESdate_fmt_asc</function></term>
-      <listitem>
-       <para>
-        Convert a variable of type date to its textual representation using a
-        format mask.
-<synopsis>
-int PGTYPESdate_fmt_asc(date dDate, char *fmtstring, char *outbuf);
-</synopsis>
-        The function receives the date to convert (<literal>dDate</>), the
-        format mask (<literal>fmtstring</>) and the string that will hold the
-        textual representation of the date (<literal>outbuf</>).
-       </para>
-       <para>
-        On success, 0 is returned and a negative value if an error occurred.
-       </para>
-       <para>
-        The following literals are the field specifiers you can use:
-        <itemizedlist>
-         <listitem>
-          <para>
-           <literal>dd</literal> - The number of the day of the month.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>mm</literal> - The number of the month of the year.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>yy</literal> - The number of the year as a two digit number.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>yyyy</literal> - The number of the year as a four digit number.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>ddd</literal> - The name of the day (abbreviated).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>mmm</literal> - The name of the month (abbreviated).
-          </para>
-         </listitem>
-        </itemizedlist>
-        All other characters are copied 1:1 to the output string.
-       </para>
-       <para>
-        <xref linkend="ecpg-pgtypesdate-fmt-asc-example-table"> indicates a few possible formats. This will give
-        you an idea of how to use this function. All output lines are based on
-        the same date: November 23, 1959.
-       </para>
-        <table id="ecpg-pgtypesdate-fmt-asc-example-table">
-         <title>Valid Input Formats for <function>PGTYPESdate_fmt_asc</function></title>
-         <tgroup cols="2">
-          <thead>
-           <row>
-            <entry>Format</entry>
-            <entry>Result</entry>
-           </row>
-          </thead>
-          <tbody>
-           <row>
-            <entry><literal>mmddyy</literal></entry>
-            <entry><literal>112359</literal></entry>
-           </row>
-           <row>
-            <entry><literal>ddmmyy</literal></entry>
-            <entry><literal>231159</literal></entry>
-           </row>
-           <row>
-            <entry><literal>yymmdd</literal></entry>
-            <entry><literal>591123</literal></entry>
-           </row>
-           <row>
-            <entry><literal>yy/mm/dd</literal></entry>
-            <entry><literal>59/11/23</literal></entry>
-           </row>
-           <row>
-            <entry><literal>yy mm dd</literal></entry>
-            <entry><literal>59 11 23</literal></entry>
-           </row>
-           <row>
-            <entry><literal>yy.mm.dd</literal></entry>
-            <entry><literal>59.11.23</literal></entry>
-           </row>
-           <row>
-            <entry><literal>.mm.yyyy.dd.</literal></entry>
-            <entry><literal>.11.1959.23.</literal></entry>
-           </row>
-           <row>
-            <entry><literal>mmm. dd, yyyy</literal></entry>
-            <entry><literal>Nov. 23, 1959</literal></entry>
-           </row>
-           <row>
-            <entry><literal>mmm dd yyyy</literal></entry>
-            <entry><literal>Nov 23 1959</literal></entry>
-           </row>
-           <row>
-            <entry><literal>yyyy dd mm</literal></entry>
-            <entry><literal>1959 23 11</literal></entry>
-           </row>
-           <row>
-            <entry><literal>ddd, mmm. dd, yyyy</literal></entry>
-            <entry><literal>Mon, Nov. 23, 1959</literal></entry>
-           </row>
-           <row>
-            <entry><literal>(ddd) mmm. dd, yyyy</literal></entry>
-            <entry><literal>(Mon) Nov. 23, 1959</literal></entry>
-           </row>
-          </tbody>
-         </tgroup>
-        </table>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESdatedefmtasc">
-      <term><function>PGTYPESdate_defmt_asc</function></term>
-      <listitem>
-       <para>
-        Use a format mask to convert a C <type>char*</type> string to a value of type
-        date.
-<synopsis>
-int PGTYPESdate_defmt_asc(date *d, char *fmt, char *str);
-</synopsis>
-        <!-- same description as rdefmtdate -->
-        The function receives a pointer to the date value that should hold the
-        result of the operation (<literal>d</>), the format mask to use for
-        parsing the date (<literal>fmt</>) and the C char* string containing
-        the textual representation of the date (<literal>str</>). The textual
-        representation is expected to match the format mask. However you do not
-        need to have a 1:1 mapping of the string to the format mask. The
-        function only analyzes the sequential order and looks for the literals
-        <literal>yy</literal> or <literal>yyyy</literal> that indicate the
-        position of the year, <literal>mm</literal> to indicate the position of
-        the month and <literal>dd</literal> to indicate the position of the
-        day.
-       </para>
-       <para>
-        <xref linkend="ecpg-rdefmtdate-example-table"> indicates a few possible formats. This will give
-        you an idea of how to use this function.
-       </para>
-        <table id="ecpg-rdefmtdate-example-table">
-         <title>Valid Input Formats for <function>rdefmtdate</function></title>
-         <tgroup cols="3">
-          <thead>
-           <row>
-            <entry>Format</entry>
-            <entry>String</entry>
-            <entry>Result</entry>
-           </row>
-          </thead>
-          <tbody>
-           <row>
-            <entry><literal>ddmmyy</literal></entry>
-            <entry><literal>21-2-54</literal></entry>
-            <entry><literal>1954-02-21</literal></entry>
-           </row>
-           <row>
-            <entry><literal>ddmmyy</literal></entry>
-            <entry><literal>2-12-54</literal></entry>
-            <entry><literal>1954-12-02</literal></entry>
-           </row>
-           <row>
-            <entry><literal>ddmmyy</literal></entry>
-            <entry><literal>20111954</literal></entry>
-            <entry><literal>1954-11-20</literal></entry>
-           </row>
-           <row>
-            <entry><literal>ddmmyy</literal></entry>
-            <entry><literal>130464</literal></entry>
-            <entry><literal>1964-04-13</literal></entry>
-           </row>
-           <row>
-            <entry><literal>mmm.dd.yyyy</literal></entry>
-            <entry><literal>MAR-12-1967</literal></entry>
-            <entry><literal>1967-03-12</literal></entry>
-           </row>
-           <row>
-            <entry><literal>yy/mm/dd</literal></entry>
-            <entry><literal>1954, February 3rd</literal></entry>
-            <entry><literal>1954-02-03</literal></entry>
-           </row>
-           <row>
-            <entry><literal>mmm.dd.yyyy</literal></entry>
-            <entry><literal>041269</literal></entry>
-            <entry><literal>1969-04-12</literal></entry>
-           </row>
-           <row>
-            <entry><literal>yy/mm/dd</literal></entry>
-            <entry><literal>In the year 2525, in the month of July, mankind will be alive on the 28th day</literal></entry>
-            <entry><literal>2525-07-28</literal></entry>
-           </row>
-           <row>
-            <entry><literal>dd-mm-yy</literal></entry>
-            <entry><literal>I said on the 28th of July in the year 2525</literal></entry>
-            <entry><literal>2525-07-28</literal></entry>
-           </row>
-           <row>
-            <entry><literal>mmm.dd.yyyy</literal></entry>
-            <entry><literal>9/14/58</literal></entry>
-            <entry><literal>1958-09-14</literal></entry>
-           </row>
-           <row>
-            <entry><literal>yy/mm/dd</literal></entry>
-            <entry><literal>47/03/29</literal></entry>
-            <entry><literal>1947-03-29</literal></entry>
-           </row>
-           <row>
-            <entry><literal>mmm.dd.yyyy</literal></entry>
-            <entry><literal>oct 28 1975</literal></entry>
-            <entry><literal>1975-10-28</literal></entry>
-           </row>
-           <row>
-            <entry><literal>mmddyy</literal></entry>
-            <entry><literal>Nov 14th, 1985</literal></entry>
-            <entry><literal>1985-11-14</literal></entry>
-           </row>
-          </tbody>
-         </tgroup>
-        </table>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-pgtypes-timestamp">
-   <title>The timestamp Type</title>
-&common;
-   <para>
-    The timestamp type in C enables your programs to deal with data of the SQL
-    type timestamp. See <xref linkend="datatype-datetime"> for the equivalent
-    type in the <productname>PostgreSQL</> server.
-   </para>
-   <para>
-    The following functions can be used to work with the timestamp type:
-    <variablelist>
-     <varlistentry id="PGTYPEStimestampfromasc">
-      <term><function>PGTYPEStimestamp_from_asc</function></term>
-      <listitem>
-       <para>
-        Parse a timestamp from its textual representation into a timestamp
-        variable.
-<synopsis>
-timestamp PGTYPEStimestamp_from_asc(char *str, char **endptr);
-</synopsis>
-        The function receives the string to parse (<literal>str</>) and a
-        pointer to a C char* (<literal>endptr</>).
-        At the moment ECPG always parses
-        the complete string and so it currently does not support to store the
-        address of the first invalid character in <literal>*endptr</literal>.
-        You can safely set <literal>endptr</literal> to NULL.
-       </para>
-       <para>
-        The function returns the parsed timestamp on success. On error,
-        <literal>PGTYPESInvalidTimestamp</literal> is returned and <varname>errno</> is
-        set to <literal>PGTYPES_TS_BAD_TIMESTAMP</>. See <xref linkend="PGTYPESInvalidTimestamp"> for important notes on this value.
-       </para>
-       <para>
-        In general, the input string can contain any combination of an allowed
-        date specification, a whitespace character and an allowed time
-        specification. Note that timezones are not supported by ECPG. It can
-        parse them but does not apply any calculation as the
-        <productname>PostgreSQL</> server does for example. Timezone
-        specifiers are silently discarded.
-       </para>
-       <para>
-        <xref linkend="ecpg-pgtypestimestamp-from-asc-example-table"> contains a few examples for input strings.
-       </para>
-        <table id="ecpg-pgtypestimestamp-from-asc-example-table">
-         <title>Valid Input Formats for <function>PGTYPEStimestamp_from_asc</function></title>
-         <tgroup cols="2">
-          <thead>
-           <row>
-            <entry>Input</entry>
-            <entry>Result</entry>
-           </row>
-          </thead>
-          <tbody>
-           <row>
-            <entry><literal>1999-01-08 04:05:06</literal></entry>
-            <entry><literal>1999-01-08 04:05:06</literal></entry>
-           </row>
-           <row>
-            <entry><literal>January 8 04:05:06 1999 PST</literal></entry>
-            <entry><literal>1999-01-08 04:05:06</literal></entry>
-           </row>
-           <row>
-            <entry><literal>1999-Jan-08 04:05:06.789-8</literal></entry>
-            <entry><literal>1999-01-08 04:05:06.789 (time zone specifier ignored)</literal></entry>
-           </row>
-           <row>
-            <entry><literal>J2451187 04:05-08:00</literal></entry>
-            <entry><literal>1999-01-08 04:05:00 (time zone specifier ignored)</literal></entry>
-           </row>
-          </tbody>
-         </tgroup>
-        </table>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPEStimestamptoasc">
-      <term><function>PGTYPEStimestamp_to_asc</function></term>
-      <listitem>
-       <para>
-        Converts a date to a C char* string.
-<synopsis>
-char *PGTYPEStimestamp_to_asc(timestamp tstamp);
-</synopsis>
-        The function receives the timestamp <literal>tstamp</> as
-        its only argument and returns an allocated string that contains the
-        textual representation of the timestamp.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPEStimestampcurrent">
-      <term><function>PGTYPEStimestamp_current</function></term>
-      <listitem>
-       <para>
-        Retrieve the current timestamp.
-<synopsis>
-void PGTYPEStimestamp_current(timestamp *ts);
-</synopsis>
-        The function retrieves the current timestamp and saves it into the
-        timestamp variable that <literal>ts</> points to.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPEStimestampfmtasc">
-      <term><function>PGTYPEStimestamp_fmt_asc</function></term>
-      <listitem>
-       <para>
-        Convert a timestamp variable to a C char* using a format mask.
-<synopsis>
-int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmtstr);
-</synopsis>
-        The function receives a pointer to the timestamp to convert as its
-        first argument (<literal>ts</>), a pointer to the output buffer
-        (<literal>output</>), the maximal length that has been allocated for
-        the output buffer (<literal>str_len</literal>) and the format mask to
-        use for the conversion (<literal>fmtstr</literal>).
-       </para>
-       <para>
-        Upon success, the function returns 0 and a negative value if an
-        error occurred.
-       </para>
-       <para>
-        You can use the following format specifiers for the format mask. The
-        format specifiers are the same ones that are used in the
-        <function>strftime</> function in <productname>libc</productname>. Any
-        non-format specifier will be copied into the output buffer.
-        <!-- This is from the FreeBSD man page:
-             http://www.freebsd.org/cgi/man.cgi?query=strftime&apropos=0&sektion=3&manpath=FreeBSD+7.0-current&format=html
-        -->
-        <itemizedlist>
-         <listitem>
-          <para>
-           <literal>%A</literal> - is replaced by national representation of
-           the full weekday name.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%a</literal> - is replaced by national representation of
-           the abbreviated weekday name.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%B</literal> - is replaced by national representation of
-           the full month name.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%b</literal> - is replaced by national representation of
-           the abbreviated month name.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%C</literal> - is replaced by (year / 100) as decimal
-           number; single digits are preceded by a zero.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%c</literal> - is replaced by national representation of
-           time and date.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%D</literal> - is equivalent to
-           <literal>%m/%d/%y</literal>.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%d</literal> - is replaced by the day of the month as a
-           decimal number (01-31).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%E*</literal> <literal>%O*</literal> -  POSIX locale
-           extensions. The sequences
-           <literal>%Ec</literal>
-           <literal>%EC</literal>
-           <literal>%Ex</literal>
-           <literal>%EX</literal>
-           <literal>%Ey</literal>
-           <literal>%EY</literal>
-           <literal>%Od</literal>
-           <literal>%Oe</literal>
-           <literal>%OH</literal>
-           <literal>%OI</literal>
-           <literal>%Om</literal>
-           <literal>%OM</literal>
-           <literal>%OS</literal>
-           <literal>%Ou</literal>
-           <literal>%OU</literal>
-           <literal>%OV</literal>
-           <literal>%Ow</literal>
-           <literal>%OW</literal>
-           <literal>%Oy</literal>
-           are supposed to provide alternative representations.
-          </para>
-          <para>
-           Additionally <literal>%OB</literal> implemented to represent
-           alternative months names (used standalone, without day mentioned).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%e</literal> - is replaced by the day of month as a decimal
-           number (1-31); single digits are preceded by a blank.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%F</literal> - is equivalent to <literal>%Y-%m-%d</literal>.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%G</literal> - is replaced by a year as a decimal number
-           with century. This year is the one that contains the greater part of
-           the week (Monday as the first day of the week).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%g</literal> - is replaced by the same year as in
-           <literal>%G</literal>, but as a decimal number without century
-           (00-99).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%H</literal> - is replaced by the hour (24-hour clock) as a
-           decimal number (00-23).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%h</literal> - the same as <literal>%b</literal>.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%I</literal> - is replaced by the hour (12-hour clock) as a
-           decimal number (01-12).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%j</literal> - is replaced by the day of the year as a
-           decimal number (001-366).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%k</literal> - is replaced by the hour (24-hour clock) as a
-           decimal number (0-23); single digits are preceded by a blank.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%l</literal> - is replaced by the hour (12-hour clock) as a
-           decimal number (1-12); single digits are preceded by a blank.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%M</literal> - is replaced by the minute as a decimal
-           number (00-59).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%m</literal> - is replaced by the month as a decimal number
-           (01-12).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-          <literal>%n</literal> - is replaced by a newline.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%O*</literal> - the same as <literal>%E*</literal>.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%p</literal> - is replaced by national representation of
-           either <quote>ante meridiem</quote> or <quote>post meridiem</quote> as appropriate.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%R</literal> - is equivalent to <literal>%H:%M</literal>.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%r</literal> - is equivalent to <literal>%I:%M:%S
-           %p</literal>.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%S</literal> - is replaced by the second as a decimal
-           number (00-60).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%s</literal> - is replaced by the number of seconds since
-           the Epoch, UTC.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%T</literal> - is equivalent to <literal>%H:%M:%S</literal>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%t</literal> - is replaced by a tab.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%U</literal> - is replaced by the week number of the year
-           (Sunday as the first day of the week) as a decimal number (00-53).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%u</literal> - is replaced by the weekday (Monday as the
-           first day of the week) as a decimal number (1-7).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%V</literal> - is replaced by the week number of the year
-           (Monday as the first day of the week) as a decimal number (01-53).
-           If the week containing January 1 has four or more days in the new
-           year, then it is week 1; otherwise it is the last week of the
-           previous year, and the next week is week 1.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%v</literal> - is equivalent to
-           <literal>%e-%b-%Y</literal>.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%W</literal> - is replaced by the week number of the year
-           (Monday as the first day of the week) as a decimal number (00-53).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%w</literal> - is replaced by the weekday (Sunday as the
-           first day of the week) as a decimal number (0-6).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%X</literal> - is replaced by national representation of
-           the time.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%x</literal> - is replaced by national representation of
-           the date.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%Y</literal> - is replaced by the year with century as a
-           decimal number.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%y</literal> - is replaced by the year without century as a
-           decimal number (00-99).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%Z</literal> - is replaced by the time zone name.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%z</literal> - is replaced by the time zone offset from
-           UTC; a leading plus sign stands for east of UTC, a minus sign for
-           west of UTC, hours and minutes follow with two digits each and no
-           delimiter between them (common form for RFC 822 date headers).
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%+</literal> - is replaced by national representation of
-           the date and time.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%-*</literal> - GNU libc extension. Do not do any padding
-           when performing numerical outputs.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           $_* - GNU libc extension.    Explicitly specify space for padding.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%0*</literal> - GNU libc extension. Explicitly specify zero
-           for padding.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>%%</literal> - is replaced by <literal>%</literal>.
-          </para>
-         </listitem>
-        </itemizedlist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPEStimestampsub">
-      <term><function>PGTYPEStimestamp_sub</function></term>
-      <listitem>
-       <para>
-        Subtract one timestamp from another one and save the result in a
-        variable of type interval.
-<synopsis>
-int PGTYPEStimestamp_sub(timestamp *ts1, timestamp *ts2, interval *iv);
-</synopsis>
-        The function will subtract the timestamp variable that <literal>ts2</>
-        points to from the timestamp variable that <literal>ts1</> points to
-        and will store the result in the interval variable that <literal>iv</>
-        points to.
-       </para>
-       <para>
-        Upon success, the function returns 0 and a negative value if an
-        error occurred.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPEStimestampdefmtasc">
-      <term><function>PGTYPEStimestamp_defmt_asc</function></term>
-      <listitem>
-       <para>
-        Parse a timestamp value from its textual representation using a
-        formatting mask.
-<synopsis>
-int PGTYPEStimestamp_defmt_asc(char *str, char *fmt, timestamp *d);
-</synopsis>
-        The function receives the textual representation of a timestamp in the
-        variable <literal>str</> as well as the formatting mask to use in the
-        variable <literal>fmt</>. The result will be stored in the variable
-        that <literal>d</> points to.
-       </para>
-       <para>
-        If the formatting mask <literal>fmt</> is NULL, the function will fall
-        back to the default formatting mask which is <literal>%Y-%m-%d
-        %H:%M:%S</literal>.
-       </para>
-       <para>
-        This is the reverse function to <xref
-        linkend="PGTYPEStimestampfmtasc">.  See the documentation there in
-        order to find out about the possible formatting mask entries.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPEStimestampaddinterval">
-      <term><function>PGTYPEStimestamp_add_interval</function></term>
-      <listitem>
-       <para>
-        Add an interval variable to a timestamp variable.
-<synopsis>
-int PGTYPEStimestamp_add_interval(timestamp *tin, interval *span, timestamp *tout);
-</synopsis>
-        The function receives a pointer to a timestamp variable <literal>tin</>
-        and a pointer to an interval variable <literal>span</>. It adds the
-        interval to the timestamp and saves the resulting timestamp in the
-        variable that <literal>tout</> points to.
-       </para>
-       <para>
-        Upon success, the function returns 0 and a negative value if an
-        error occurred.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPEStimestampsubinterval">
-      <term><function>PGTYPEStimestamp_sub_interval</function></term>
-      <listitem>
-       <para>
-        Subtract an interval variable from a timestamp variable.
-<synopsis>
-int PGTYPEStimestamp_sub_interval(timestamp *tin, interval *span, timestamp *tout);
-</synopsis>
-        The function subtracts the interval variable that <literal>span</>
-        points to from the timestamp variable that <literal>tin</> points to
-        and saves the result into the variable that <literal>tout</> points
-        to.
-       </para>
-       <para>
-        Upon success, the function returns 0 and a negative value if an
-        error occurred.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-pgtypes-interval">
-   <title>The interval Type</title>
-&common;
-   <para>
-    The interval type in C enables your programs to deal with data of the SQL
-    type interval. See <xref linkend="datatype-datetime"> for the equivalent
-    type in the <productname>PostgreSQL</> server.
-   </para>
-   <para>
-    The following functions can be used to work with the interval type:
-    <variablelist>
-
-     <varlistentry id="PGTYPESintervalnew">
-      <term><function>PGTYPESinterval_new</function></term>
-      <listitem>
-       <para>
-        Return a pointer to a newly allocated interval variable.
-<synopsis>
-interval *PGTYPESinterval_new(void);
-</synopsis>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESintervalfree">
-      <term><function>PGTYPESinterval_free</function></term>
-      <listitem>
-       <para>
-        Release the memory of a previously allocated interval variable.
-<synopsis>
-void PGTYPESinterval_new(interval *intvl);
-</synopsis>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESintervalfromasc">
-      <term><function>PGTYPESinterval_from_asc</function></term>
-      <listitem>
-       <para>
-        Parse an interval from its textual representation.
-<synopsis>
-interval *PGTYPESinterval_from_asc(char *str, char **endptr);
-</synopsis>
-        The function parses the input string <literal>str</> and returns a
-        pointer to an allocated interval variable.
-        At the moment ECPG always parses
-        the complete string and so it currently does not support to store the
-        address of the first invalid character in <literal>*endptr</literal>.
-        You can safely set <literal>endptr</literal> to NULL.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESintervaltoasc">
-      <term><function>PGTYPESinterval_to_asc</function></term>
-      <listitem>
-       <para>
-        Convert a variable of type interval to its textual representation.
-<synopsis>
-char *PGTYPESinterval_to_asc(interval *span);
-</synopsis>
-        The function converts the interval variable that <literal>span</>
-        points to into a C char*. The output looks like this example:
-        <literal>@ 1 day 12 hours 59 mins 10 secs</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="PGTYPESintervalcopy">
-      <term><function>PGTYPESinterval_copy</function></term>
-      <listitem>
-       <para>
-        Copy a variable of type interval.
-<synopsis>
-int PGTYPESinterval_copy(interval *intvlsrc, interval *intvldest);
-</synopsis>
-        The function copies the interval variable that <literal>intvlsrc</>
-        points to into the variable that <literal>intvldest</> points to. Note
-        that you need to allocate the memory for the destination variable
-        before.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-pgtypes-decimal">
-   <title>The decimal Type</title>
-&common;
-   <para>
-     The decimal type is similar to the numeric type. However it is limited to
-     a maximum precision of 30 significant digits. In contrast to the numeric
-     type which can be created on the heap only, the decimal type can be
-     created either on the stack or on the heap (by means of the functions
-     <function>PGTYPESdecimal_new</> and
-     <function>PGTYPESdecimal_free</>).
-     There are a lot of other functions that deal with the decimal type in the
-     <productname>Informix</productname> compatibility mode described in <xref
-     linkend="ecpg-informix-compat">.
-   </para>
-   <para>
-    The following functions can be used to work with the decimal type and are
-    not only contained in the <literal>libcompat</> library.
-    <variablelist>
-     <varlistentry>
-      <term><function>PGTYPESdecimal_new</function></term>
-      <listitem>
-       <para>
-       Request a pointer to a newly allocated decimal variable.
-<synopsis>
-decimal *PGTYPESdecimal_new(void);
-</synopsis>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>PGTYPESdecimal_free</function></term>
-      <listitem>
-       <para>
-       Free a decimal type, release all of its memory.
-<synopsis>
-void PGTYPESdecimal_free(decimal *var);
-</synopsis>
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-   <sect2 id="ecpg-pgtypes-errno">
-    <title>errno Values of pgtypeslib</title>
-&common;
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><literal>PGTYPES_NUM_BAD_NUMERIC</literal></term>
-      <listitem>
-       <para>
-        An argument should contain a numeric variable (or point to a numeric
-        variable) but in fact its in-memory representation was invalid.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_NUM_OVERFLOW</literal></term>
-      <listitem>
-       <para>
-        An overflow occurred. Since the numeric type can deal with almost
-        arbitrary precision, converting a numeric variable into other types
-        might cause overflow.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_NUM_UNDERFLOW</literal></term>
-      <listitem>
-       <para>
-        An underflow occurred. Since the numeric type can deal with almost
-        arbitrary precision, converting a numeric variable into other types
-        might cause underflow.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_NUM_DIVIDE_ZERO</literal></term>
-      <listitem>
-       <para>
-        A division by zero has been attempted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_DATE_BAD_DATE</literal></term>
-      <listitem>
-       <para>
-        An invalid date string was passed to
-        the <function>PGTYPESdate_from_asc</function> function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_DATE_ERR_EARGS</literal></term>
-      <listitem>
-       <para>
-        Invalid arguments were passed to the
-        <function>PGTYPESdate_defmt_asc</function> function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_DATE_ERR_ENOSHORTDATE</literal></term>
-      <listitem>
-       <para>
-        An invalid token in the input string was found by the
-        <function>PGTYPESdate_defmt_asc</function> function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_INTVL_BAD_INTERVAL</literal></term>
-      <listitem>
-       <para>
-        An invalid interval string was passed to the
-        <function>PGTYPESinterval_from_asc</function> function, or an
-        invalid interval value was passed to the
-        <function>PGTYPESinterval_to_asc</function> function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_DATE_ERR_ENOTDMY</literal></term>
-      <listitem>
-       <para>
-        There was a mismatch in the day/month/year assignment in the
-        <function>PGTYPESdate_defmt_asc</function> function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_DATE_BAD_DAY</literal></term>
-      <listitem>
-       <para>
-        An invalid day of the month value was found by
-        the <function>PGTYPESdate_defmt_asc</function> function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_DATE_BAD_MONTH</literal></term>
-      <listitem>
-       <para>
-        An invalid month value was found by
-        the <function>PGTYPESdate_defmt_asc</function> function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_TS_BAD_TIMESTAMP</literal></term>
-      <listitem>
-       <para>
-        An invalid timestamp string pass passed to
-        the <function>PGTYPEStimestamp_from_asc</function> function,
-        or an invalid timestamp value was passed to
-        the <function>PGTYPEStimestamp_to_asc</function> function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PGTYPES_TS_ERR_EINFTIME</literal></term>
-      <listitem>
-       <para>
-        An infinite timestamp value was encountered in a context that
-        cannot handle it.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-   <sect2 id="ecpg-pgtypes-constants">
-    <title>Special Constants of pgtypeslib</title>
-&common;
-   <para>
-    <variablelist>
-     <varlistentry id="PGTYPESInvalidTimestamp">
-      <term><literal>PGTYPESInvalidTimestamp</literal></term>
-      <listitem>
-       <para>
-        A value of type timestamp representing an invalid time stamp. This is
-        returned by the function <function>PGTYPEStimestamp_from_asc</> on
-        parse error.
-        Note that due to the internal representation of the <type>timestamp</type> data type,
-        <literal>PGTYPESInvalidTimestamp</literal> is also a valid timestamp at
-        the same time. It is set to <literal>1899-12-31 23:59:59</>. In order
-        to detect errors, make sure that your application does not only test
-        for <literal>PGTYPESInvalidTimestamp</literal> but also for
-        <literal>errno != 0</> after each call to
-        <function>PGTYPEStimestamp_from_asc</>.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="ecpg-descriptors">
-  <title>Using Descriptor Areas</title>
-
-&common;
-  <para>
-   An SQL descriptor area is a more sophisticated method for processing
-   the result of a <command>SELECT</command>, <command>FETCH</command> or
-   a <command>DESCRIBE</command> statement. An SQL descriptor area groups
-   the data of one row of data together with metadata items into one
-   data structure.  The metadata is particularly useful when executing
-   dynamic SQL statements, where the nature of the result columns might
-   not be known ahead of time. PostgreSQL provides two ways to use
-   Descriptor Areas: the named SQL Descriptor Areas and the C-structure
-   SQLDAs.
-  </para>
-
-  <sect2 id="ecpg-named-descriptors">
-   <title>Named SQL Descriptor Areas</title>
-
-&common;
-   <para>
-    A named SQL descriptor area consists of a header, which contains
-    information concerning the entire descriptor, and one or more item
-    descriptor areas, which basically each describe one column in the
-    result row.
-   </para>
-
-   <para>
-    Before you can use an SQL descriptor area, you need to allocate one:
-<programlisting>
-EXEC SQL ALLOCATE DESCRIPTOR <replaceable>identifier</replaceable>;
-</programlisting>
-    The identifier serves as the <quote>variable name</quote> of the
-    descriptor area.  <remark>The scope of the allocated descriptor is WHAT?.</remark>
-    When you don't need the descriptor anymore, you should deallocate
-    it:
-<programlisting>
-EXEC SQL DEALLOCATE DESCRIPTOR <replaceable>identifier</replaceable>;
-</programlisting>
-   </para>
-
-   <para>
-    To use a descriptor area, specify it as the storage target in an
-    <literal>INTO</literal> clause, instead of listing host variables:
-<programlisting>
-EXEC SQL FETCH NEXT FROM mycursor INTO SQL DESCRIPTOR mydesc;
-</programlisting>
-    If the result set is empty, the Descriptor Area will still contain
-    the metadata from the query, i.e. the field names.
-   </para>
-
-   <para>
-    For not yet executed prepared queries, the <command>DESCRIBE</command>
-    statement can be used to get the metadata of the result set:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-char *sql_stmt = "SELECT * FROM table1";
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL PREPARE stmt1 FROM :sql_stmt;
-EXEC SQL DESCRIBE stmt1 INTO SQL DESCRIPTOR mydesc;
-</programlisting>
-   </para>
-
-   <para>
-    Before PostgreSQL 9.0, the <literal>SQL</literal> keyword was optional,
-    so using <literal>DESCRIPTOR</literal> and <literal>SQL DESCRIPTOR</literal>
-    produced named SQL Descriptor Areas. Now it is mandatory, omitting
-    the <literal>SQL</literal> keyword produces SQLDA Descriptor Areas,
-    see <xref linkend="ecpg-sqlda-descriptors">.
-   </para>
-
-   <para>
-    In <command>DESCRIBE</command> and <command>FETCH</command> statements,
-    the <literal>INTO</literal> and <literal>USING</literal> keywords can be
-    used to similarly: they produce the result set and the metadata in a
-    Descriptor Area.
-   </para>
-
-   <para>
-    Now how do you get the data out of the descriptor area?  You can
-    think of the descriptor area as a structure with named fields.  To
-    retrieve the value of a field from the header and store it into a
-    host variable, use the following command:
-<programlisting>
-EXEC SQL GET DESCRIPTOR <replaceable>name</replaceable> :<replaceable>hostvar</replaceable> = <replaceable>field</replaceable>;
-</programlisting>
-    Currently, there is only one header field defined:
-    <replaceable>COUNT</replaceable>, which tells how many item
-    descriptor areas exist (that is, how many columns are contained in
-    the result).  The host variable needs to be of an integer type.  To
-    get a field from the item descriptor area, use the following
-    command:
-<programlisting>
-EXEC SQL GET DESCRIPTOR <replaceable>name</replaceable> VALUE <replaceable>num</replaceable> :<replaceable>hostvar</replaceable> = <replaceable>field</replaceable>;
-</programlisting>
-    <replaceable>num</replaceable> can be a literal integer or a host
-    variable containing an integer. Possible fields are:
-
-    <variablelist>
-     <varlistentry>
-      <term><literal>CARDINALITY</literal> (integer)</term>
-      <listitem>
-       <para>
-        number of rows in the result set
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>DATA</literal></term>
-      <listitem>
-       <para>
-        actual data item (therefore, the data type of this field
-        depends on the query)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>DATETIME_INTERVAL_CODE</literal> (integer)</term>
-      <listitem>
-       <para>
-        When <literal>TYPE</literal> is <literal>9</literal>,
-        <literal>DATETIME_INTERVAL_CODE</literal> will have a value of
-        <literal>1</literal> for <literal>DATE</literal>,
-        <literal>2</literal> for <literal>TIME</literal>,
-        <literal>3</literal> for <literal>TIMESTAMP</literal>,
-        <literal>4</literal> for <literal>TIME WITH TIME ZONE</literal>, or
-        <literal>5</literal> for <literal>TIMESTAMP WITH TIME ZONE</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>DATETIME_INTERVAL_PRECISION</literal> (integer)</term>
-      <listitem>
-       <para>
-        not implemented
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>INDICATOR</literal> (integer)</term>
-      <listitem>
-       <para>
-        the indicator (indicating a null value or a value truncation)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>KEY_MEMBER</literal> (integer)</term>
-      <listitem>
-       <para>
-        not implemented
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>LENGTH</literal> (integer)</term>
-      <listitem>
-       <para>
-        length of the datum in characters
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>NAME</literal> (string)</term>
-      <listitem>
-       <para>
-        name of the column
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>NULLABLE</literal> (integer)</term>
-      <listitem>
-       <para>
-        not implemented
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>OCTET_LENGTH</literal> (integer)</term>
-      <listitem>
-       <para>
-        length of the character representation of the datum in bytes
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PRECISION</literal> (integer)</term>
-      <listitem>
-       <para>
-        precision (for type <type>numeric</type>)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>RETURNED_LENGTH</literal> (integer)</term>
-      <listitem>
-       <para>
-        length of the datum in characters
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>RETURNED_OCTET_LENGTH</literal> (integer)</term>
-      <listitem>
-       <para>
-        length of the character representation of the datum in bytes
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>SCALE</literal> (integer)</term>
-      <listitem>
-       <para>
-        scale (for type <type>numeric</type>)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>TYPE</literal> (integer)</term>
-      <listitem>
-       <para>
-        numeric code of the data type of the column
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    In <command>EXECUTE</command>, <command>DECLARE</command> and <command>OPEN</command>
-    statements, the effect of the <literal>INTO</literal> and <literal>USING</literal>
-    keywords are different. A Descriptor Area can also be manually built to
-    provide the input parameters for a query or a cursor and
-    <literal>USING SQL DESCRIPTOR <replaceable>name</replaceable></literal>
-    is the way to pass the input parameters into a parametrized query. The statement
-    to build a named SQL Descriptor Area is below:
-<programlisting>
-EXEC SQL SET DESCRIPTOR <replaceable>name</replaceable> VALUE <replaceable>num</replaceable> <replaceable>field</replaceable> = :<replaceable>hostvar</replaceable>;
-</programlisting>
-   </para>
-
-   <para>
-    PostgreSQL supports retrieving more that one record in one <command>FETCH</command>
-    statement and storing the data in host variables in this case assumes that the
-    variable is an array. E.g.:
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-int id[5];
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL FETCH 5 FROM mycursor INTO SQL DESCRIPTOR mydesc;
-
-EXEC SQL GET DESCRIPTOR mydesc VALUE 1 :id = DATA;
-</programlisting>
-
-   </para>
-
-  </sect2>
-
-  <sect2 id="ecpg-sqlda-descriptors">
-   <title>SQLDA Descriptor Areas</title>
-
-&common;
-   <para>
-    An SQLDA Descriptor Area is a C language structure which can be also used
-    to get the result set and the metadata of a query. One structure stores one
-    record from the result set.
-<programlisting>
-EXEC SQL include sqlda.h;
-sqlda_t         *mysqlda;
-
-EXEC SQL FETCH 3 FROM mycursor INTO DESCRIPTOR mysqlda;
-</programlisting>
-    Note that the <literal>SQL</literal> keyword is omitted. The paragraphs about
-    the use cases of the <literal>INTO</literal> and <literal>USING</literal>
-    keywords in <xref linkend="ecpg-named-descriptors"> also apply here with an addition.
-    In a <command>DESCRIBE</command> statement the <literal>DESCRIPTOR</literal>
-    keyword can be completely omitted if the <literal>INTO</literal> keyword is used:
-<programlisting>
-EXEC SQL DESCRIBE prepared_statement INTO mysqlda;
-</programlisting>
-   </para>
-
-    <procedure>
-     <para>
-      The general flow of a program that uses SQLDA is:
-     </para>
-     <step><simpara>Prepare a query, and declare a cursor for it.</simpara></step>
-     <step><simpara>Declare an SQLDA for the result rows.</simpara></step>
-     <step><simpara>Declare an SQLDA for the input parameters, and initialize them (memory allocation, parameter settings).</simpara></step>
-     <step><simpara>Open a cursor with the input SQLDA.</simpara></step>
-     <step><simpara>Fetch rows from the cursor, and store them into an output SQLDA.</simpara></step>
-     <step><simpara>Read values from the output SQLDA into the host variables (with conversion if necessary).</simpara></step>
-     <step><simpara>Close the cursor.</simpara></step>
-     <step><simpara>Free the memory area allocated for the input SQLDA.</simpara></step>
-    </procedure>
-
-   <sect3>
-    <title>SQLDA Data Structure</title>
-
-&common;
-    <para>
-     SQLDA uses three data structure
-     types: <type>sqlda_t</type>, <type>sqlvar_t</type>,
-     and <type>struct sqlname</type>.
-    </para>
-
-    <tip>
-     <para>
-      PostgreSQL's SQLDA has a similar data structure to the one in
-      IBM DB2 Universal Database, so some technical information on
-      DB2's SQLDA could help understanding PostgreSQL's one better.
-     </para>
-    </tip>
-
-    <sect4 id="ecpg-sqlda-sqlda">
-     <title>sqlda_t Structure</title>
-
-&common;
-     <para>
-      The structure type <type>sqlda_t</type> is the type of the
-      actual SQLDA.  It holds one record.  And two or
-      more <type>sqlda_t</type> structures can be connected in a
-      linked list with the pointer in
-      the <structfield>desc_next</structfield> field, thus
-      representing an ordered collection of rows.  So, when two or
-      more rows are fetched, the application can read them by
-      following the <structfield>desc_next</structfield> pointer in
-      each <type>sqlda_t</type> node.
-     </para>
-
-     <para>
-      The definition of <type>sqlda_t</type> is:
-<programlisting>
-struct sqlda_struct
-{
-    char            sqldaid[8];
-    long            sqldabc;
-    short           sqln;
-    short           sqld;
-    struct sqlda_struct *desc_next;
-    struct sqlvar_struct sqlvar[1];
-};
-
-typedef struct sqlda_struct sqlda_t;
-</programlisting>
-
-      The meaning of the fields is:
-
-    <variablelist>
-     <varlistentry>
-      <term><literal>sqldaid</></term>
-      <listitem>
-       <para>
-        It contains the literal string <literal>"SQLDA  "</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>sqldabc</></term>
-      <listitem>
-       <para>
-        It contains the size of the allocated space in bytes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>sqln</></term>
-      <listitem>
-       <para>
-        It contains the number of input parameters for a parametrized query
-        case it's passed into <command>OPEN</command>, <command>DECLARE</command> or
-        <command>EXECUTE</command> statements using the <literal>USING</literal>
-        keyword. In case it's used as output of <command>SELECT</command>,
-        <command>EXECUTE</command> or <command>FETCH</command> statements,
-        its value is the same as <literal>sqld</literal>
-        statement
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>sqld</></term>
-      <listitem>
-       <para>
-        It contains the number of fields in a result set.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>desc_next</></term>
-      <listitem>
-       <para>
-        If the query returns more than one record, multiple linked
-        SQLDA structures are returned, and <literal>desc_next</> holds
-        a pointer to the next entry in the list.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>sqlvar</></term>
-      <listitem>
-       <para>
-        This is the array of the columns in the result set.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-     </para>
-    </sect4>
-
-    <sect4 id="ecpg-sqlda-sqlvar">
-     <title>sqlvar_t Structure</title>
-
-&common;
-     <para>
-      The structure type <type>sqlvar_t</type> holds a column value
-      and metadata such as type and length. The definition of the type
-      is:
-
-<programlisting>
-struct sqlvar_struct
-{
-    short          sqltype;
-    short          sqllen;
-    char          *sqldata;
-    short         *sqlind;
-    struct sqlname sqlname;
-};
-
-typedef struct sqlvar_struct sqlvar_t;
-</programlisting>
-
-      The meaning of the fields is:
-
-        <variablelist>
-         <varlistentry>
-         <term><literal>sqltype</></term>
-          <listitem>
-           <para>
-            Contains the type identifier of the field. For values,
-            see <literal>enum ECPGttype</literal> in <literal>ecpgtype.h</literal>.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-         <term><literal>sqllen</></term>
-          <listitem>
-           <para>
-            Contains the binary length of the field. e.g. 4 bytes for <type>ECPGt_int</type>.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-         <term><literal>sqldata</></term>
-          <listitem>
-           <para>
-            Points to the data.  The format of the data is described
-            in <xref linkend="ecpg-variables-type-mapping">.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-         <term><literal>sqlind</></term>
-          <listitem>
-           <para>
-            Points to the null indicator.  0 means not null, -1 means
-            null.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-         <term><literal>sqlname</></term>
-          <listitem>
-           <para>
-            The the name of the field.
-           </para>
-          </listitem>
-         </varlistentry>
-        </variablelist>
-     </para>
-    </sect4>
-
-    <sect4 id="ecpg-sqlda-sqlname">
-     <title>struct sqlname Structure</title>
-
-&common;
-     <para>
-      A <type>struct sqlname</type> structure holds a column name.  It
-      is used as a member of the <type>sqlvar_t</type> structure.  The
-      definition of the structure is:
-<programlisting>
-#define NAMEDATALEN 64
-
-struct sqlname
-{
-        short           length;
-        char            data[NAMEDATALEN];
-};
-</programlisting>
-      The meaning of the fields is:
-            <variablelist>
-             <varlistentry>
-              <term><literal>length</></term>
-               <listitem>
-                <para>
-                 Contains the length of the field name.
-                </para>
-               </listitem>
-              </varlistentry>
-             <varlistentry>
-              <term><literal>data</></term>
-               <listitem>
-                <para>
-                 Contains the actual field name.
-                </para>
-               </listitem>
-              </varlistentry>
-            </variablelist>
-     </para>
-    </sect4>
-   </sect3>
-
-   <sect3 id="ecpg-sqlda-output">
-    <title>Retrieving a Result Set Using an SQLDA</title>
-
-&common;
-    <procedure>
-     <para>
-      The general steps to retrieve a query result set through an
-      SQLDA are:
-     </para>
-     <step><simpara>Declare an <type>sqlda_t</type> structure to receive the result set.</simpara></step>
-     <step><simpara>Execute <command>FETCH</>/<command>EXECUTE</>/<command>DESCRIBE</> commands to process a query specifying the declared SQLDA.</simpara></step>
-     <step><simpara>Check the number of records in the result set by looking at <structfield>sqln</>, a member of the <type>sqlda_t</type> structure.</simpara></step>
-     <step><simpara>Get the values of each column from <literal>sqlvar[0]</>, <literal>sqlvar[1]</>, etc., members of the <type>sqlda_t</type> structure.</simpara></step>
-     <step><simpara>Go to next row (<type>sqlda_t</type> structure) by following the <structfield>desc_next</> pointer, a member of the <type>sqlda_t</type> structure.</simpara></step>
-     <step><simpara>Repeat above as you need.</simpara></step>
-    </procedure>
-
-    <para>
-     Here is an example retrieving a result set through an SQLDA.
-    </para>
-
-    <para>
-     First, declare a <type>sqlda_t</type> structure to receive the result set.
-<programlisting>
-sqlda_t *sqlda1;
-</programlisting>
-    </para>
-
-    <para>
-     Next, specify the SQLDA in a command.  This is
-     a <command>FETCH</> command example.
-<programlisting>
-EXEC SQL FETCH NEXT FROM cur1 INTO DESCRIPTOR sqlda1;
-</programlisting>
-    </para>
-
-    <para>
-     Run a loop following the linked list to retrieve the rows.
-<programlisting>
-sqlda_t *cur_sqlda;
-
-for (cur_sqlda = sqlda1;
-     cur_sqlda != NULL;
-     cur_sqlda = cur_sqlda->desc_next)
-{
-    ...
-}
-</programlisting>
-    </para>
-
-    <para>
-     Inside the loop, run another loop to retrieve each column data
-     (<type>sqlvar_t</type> structure) of the row.
-<programlisting>
-for (i = 0; i &lt; cur_sqlda->sqld; i++)
-{
-    sqlvar_t v = cur_sqlda->sqlvar[i];
-    char *sqldata = v.sqldata;
-    short sqllen  = v.sqllen;
-    ...
-}
-</programlisting>
-    </para>
-
-    <para>
-     To get a column value, check the <structfield>sqltype</> value,
-     a member of the <type>sqlvar_t</type> structure.  Then, switch
-     to an appropriate way, depending on the column type, to copy
-     data from the <structfield>sqlvar</> field to a host variable.
-<programlisting>
-char var_buf[1024];
-
-switch (v.sqltype)
-{
-    case ECPGt_char:
-        memset(&amp;var_buf, 0, sizeof(var_buf));
-        memcpy(&amp;var_buf, sqldata, (sizeof(var_buf) &lt;= sqllen ? sizeof(var_buf) - 1 : sqllen));
-        break;
-
-    case ECPGt_int: /* integer */
-        memcpy(&amp;intval, sqldata, sqllen);
-        snprintf(var_buf, sizeof(var_buf), "%d", intval);
-        break;
-
-    ...
-}
-</programlisting>
-    </para>
-   </sect3>
-
-   <sect3 id="ecpg-sqlda-input">
-    <title>Passing Query Parameters Using an SQLDA</title>
-
-&common;
-    <procedure>
-     <para>
-      The general steps to use an SQLDA to pass input
-      parameters to a prepared query are:
-     </para>
-     <step><simpara>Create a prepared query (prepared statement)</simpara></step>
-     <step><simpara>Declare a sqlda_t structure as an input SQLDA.</simpara></step>
-     <step><simpara>Allocate memory area (as sqlda_t structure) for the input SQLDA.</simpara></step>
-     <step><simpara>Set (copy) input values in the allocated memory.</simpara></step>
-     <step><simpara>Open a cursor with specifying the input SQLDA.</simpara></step>
-    </procedure>
-
-    <para>
-     Here is an example.
-    </para>
-
-    <para>
-     First, create a prepared statement.
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-char query[1024] = "SELECT d.oid, * FROM pg_database d, pg_stat_database s WHERE d.oid = s.datid AND (d.datname = ? OR d.oid = ?)";
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL PREPARE stmt1 FROM :query;
-</programlisting>
-    </para>
-
-    <para>
-     Next, allocate memory for an SQLDA, and set the number of input
-     parameters in <structfield>sqln</>, a member variable of
-     the <type>sqlda_t</type> structure.  When two or more input
-     parameters are required for the prepared query, the application
-     has to allocate additional memory space which is calculated by
-     (nr. of params - 1) * sizeof(sqlvar_t).  The example shown here
-     allocates memory space for two input parameters.
-<programlisting>
-sqlda_t *sqlda2;
-
-sqlda2 = (sqlda_t *) malloc(sizeof(sqlda_t) + sizeof(sqlvar_t));
-memset(sqlda2, 0, sizeof(sqlda_t) + sizeof(sqlvar_t));
-
-sqlda2->sqln = 2; /* number of input variables */
-</programlisting>
-    </para>
-
-    <para>
-     After memory allocation, store the parameter values into the
-     <literal>sqlvar[]</literal> array.  (This is same array used for
-     retrieving column values when the SQLDA is receiving a result
-     set.)  In this example, the input parameters
-     are <literal>"postgres"</literal>, having a string type,
-     and <literal>1</literal>, having an integer type.
-<programlisting>
-sqlda2->sqlvar[0].sqltype = ECPGt_char;
-sqlda2->sqlvar[0].sqldata = "postgres";
-sqlda2->sqlvar[0].sqllen  = 8;
-
-int intval = 1;
-sqlda2->sqlvar[1].sqltype = ECPGt_int;
-sqlda2->sqlvar[1].sqldata = (char *) &amp;intval;
-sqlda2->sqlvar[1].sqllen  = sizeof(intval);
-</programlisting>
-    </para>
-
-    <para>
-     By opening a cursor and specifying the SQLDA that was set up
-     beforehand, the input parameters are passed to the prepared
-     statement.
-<programlisting>
-EXEC SQL OPEN cur1 USING DESCRIPTOR sqlda2;
-</programlisting>
-    </para>
-
-    <para>
-     Finally, after using input SQLDAs, the allocated memory space
-     must be freed explicitly, unlike SQLDAs used for receiving query
-     results.
-<programlisting>
-free(sqlda2);
-</programlisting>
-    </para>
-   </sect3>
-
-   <sect3 id="ecpg-sqlda-example">
-    <title>A Sample Application Using SQLDA</title>
-
-&common;
-    <para>
-     Here is an example program, which describes how to fetch access
-     statistics of the databases, specified by the input parameters,
-     from the system catalogs.
-    </para>
-
-    <para>
-     This application joins two system tables, pg_database and
-     pg_stat_database on the database OID, and also fetches and shows
-     the database statistics which are retrieved by two input
-     parameters (a database <literal>postgres</literal>, and OID <literal>1</literal>).
-    </para>
-
-    <para>
-     First, declare an SQLDA for input and an SQLDA for output.
-<programlisting>
-EXEC SQL include sqlda.h;
-
-sqlda_t *sqlda1; /* an output descriptor */
-sqlda_t *sqlda2; /* an input descriptor  */
-</programlisting>
-    </para>
-
-    <para>
-     Next, connect to the database, prepare a statement, and declare a
-     cursor for the prepared statement.
-<programlisting>
-int
-main(void)
-{
-    EXEC SQL BEGIN DECLARE SECTION;
-    char query[1024] = "SELECT d.oid,* FROM pg_database d, pg_stat_database s WHERE d.oid=s.datid AND ( d.datname=? OR d.oid=? )";
-    EXEC SQL END DECLARE SECTION;
-
-    EXEC SQL CONNECT TO testdb AS con1 USER testuser;
-
-    EXEC SQL PREPARE stmt1 FROM :query;
-    EXEC SQL DECLARE cur1 CURSOR FOR stmt1;
-</programlisting>
-    </para>
-
-    <para>
-     Next, put some values in the input SQLDA for the input
-     parameters.  Allocate memory for the input SQLDA, and set the
-     number of input parameters to <literal>sqln</literal>.  Store
-     type, value, and value length into <literal>sqltype</literal>,
-     <literal>sqldata</literal>, and <literal>sqllen</literal> in the
-     <literal>sqlvar</literal> structure.
-
-<programlisting>
-    /* Create SQLDA structure for input parameters. */
-    sqlda2 = (sqlda_t *) malloc(sizeof(sqlda_t) + sizeof(sqlvar_t));
-    memset(sqlda2, 0, sizeof(sqlda_t) + sizeof(sqlvar_t));
-    sqlda2->sqln = 2; /* number of input variables */
-
-    sqlda2->sqlvar[0].sqltype = ECPGt_char;
-    sqlda2->sqlvar[0].sqldata = "postgres";
-    sqlda2->sqlvar[0].sqllen  = 8;
-
-    intval = 1;
-    sqlda2->sqlvar[1].sqltype = ECPGt_int;
-    sqlda2->sqlvar[1].sqldata = (char *)&amp;intval;
-    sqlda2->sqlvar[1].sqllen  = sizeof(intval);
-</programlisting>
-    </para>
-
-    <para>
-     After setting up the input SQLDA, open a cursor with the input
-     SQLDA.
-
-<programlisting>
-    /* Open a cursor with input parameters. */
-    EXEC SQL OPEN cur1 USING DESCRIPTOR sqlda2;
-</programlisting>
-    </para>
-
-    <para>
-     Fetch rows into the output SQLDA from the opened cursor.
-     (Generally, you have to call <command>FETCH</command> repeatedly
-     in the loop, to fetch all rows in the result set.)
-<programlisting>
-    while (1)
-    {
-        sqlda_t *cur_sqlda;
-
-        /* Assign descriptor to the cursor  */
-        EXEC SQL FETCH NEXT FROM cur1 INTO DESCRIPTOR sqlda1;
-</programlisting>
-    </para>
-
-    <para>
-     Next, retrieve the fetched records from the SQLDA, by following
-     the linked list of the <type>sqlda_t</type> structure.
-<programlisting>
-    for (cur_sqlda = sqlda1 ;
-         cur_sqlda != NULL ;
-         cur_sqlda = cur_sqlda->desc_next)
-    {
-        ...
-</programlisting>
-    </para>
-
-    <para>
-     Read each columns in the first record.  The number of columns is
-     stored in <structfield>sqld</>, the actual data of the first
-     column is stored in <literal>sqlvar[0]</>, both members of
-     the <type>sqlda_t</type> structure.
-
-<programlisting>
-        /* Print every column in a row. */
-        for (i = 0; i &lt; sqlda1-&gt;sqld; i++)
-        {
-            sqlvar_t v = sqlda1->sqlvar[i];
-            char *sqldata = v.sqldata;
-            short sqllen  = v.sqllen;
-
-            strncpy(name_buf, v.sqlname.data, v.sqlname.length);
-            name_buf[v.sqlname.length] = '\0';
-</programlisting>
-    </para>
-
-    <para>
-     Now, the column data is stored in the variable <varname>v</>.
-     Copy every datum into host variables, looking
-     at <literal>v.sqltype</> for the type of the column.
-<programlisting>
-            switch (v.sqltype) {
-                int intval;
-                double doubleval;
-                unsigned long long int longlongval;
-
-                case ECPGt_char:
-                    memset(&amp;var_buf, 0, sizeof(var_buf));
-                    memcpy(&amp;var_buf, sqldata, (sizeof(var_buf) &lt;= sqllen ? sizeof(var_buf)-1 : sqllen));
-                    break;
-
-                case ECPGt_int: /* integer */
-                    memcpy(&amp;intval, sqldata, sqllen);
-                    snprintf(var_buf, sizeof(var_buf), "%d", intval);
-                    break;
-
-                ...
-
-                default:
-                    ...
-            }
-
-            printf("%s = %s (type: %d)\n", name_buf, var_buf, v.sqltype);
-        }
-</programlisting>
-    </para>
-
-    <para>
-     Close the cursor after processing all of records, and disconnect
-     from the database.
-<programlisting>
-    EXEC SQL CLOSE cur1;
-    EXEC SQL COMMIT;
-
-    EXEC SQL DISCONNECT ALL;
-</programlisting>
-    </para>
-
-    <para>
-     The whole program is shown
-     in <xref linkend="ecpg-sqlda-example-example">.
-    </para>
-
-    <example id="ecpg-sqlda-example-example">
-     <title>Example SQLDA Program</title>
-<programlisting>
-#include &lt;stdlib.h>
-#include &lt;string.h>
-#include &lt;stdlib.h>
-#include &lt;stdio.h>
-#include &lt;unistd.h>
-
-EXEC SQL include sqlda.h;
-
-sqlda_t *sqlda1; /* descriptor for output */
-sqlda_t *sqlda2; /* descriptor for input */
-
-EXEC SQL WHENEVER NOT FOUND DO BREAK;
-EXEC SQL WHENEVER SQLERROR STOP;
-
-int
-main(void)
-{
-    EXEC SQL BEGIN DECLARE SECTION;
-    char query[1024] = "SELECT d.oid,* FROM pg_database d, pg_stat_database s WHERE d.oid=s.datid AND ( d.datname=? OR d.oid=? )";
-
-    int intval;
-    unsigned long long int longlongval;
-    EXEC SQL END DECLARE SECTION;
-
-    EXEC SQL CONNECT TO uptimedb AS con1 USER uptime;
-
-    EXEC SQL PREPARE stmt1 FROM :query;
-    EXEC SQL DECLARE cur1 CURSOR FOR stmt1;
-
-    /* Create a SQLDA structure for an input parameter */
-    sqlda2 = (sqlda_t *)malloc(sizeof(sqlda_t) + sizeof(sqlvar_t));
-    memset(sqlda2, 0, sizeof(sqlda_t) + sizeof(sqlvar_t));
-    sqlda2->sqln = 2; /* a number of input variables */
-
-    sqlda2->sqlvar[0].sqltype = ECPGt_char;
-    sqlda2->sqlvar[0].sqldata = "postgres";
-    sqlda2->sqlvar[0].sqllen  = 8;
-
-    intval = 1;
-    sqlda2->sqlvar[1].sqltype = ECPGt_int;
-    sqlda2->sqlvar[1].sqldata = (char *) &amp;intval;
-    sqlda2->sqlvar[1].sqllen  = sizeof(intval);
-
-    /* Open a cursor with input parameters. */
-    EXEC SQL OPEN cur1 USING DESCRIPTOR sqlda2;
-
-    while (1)
-    {
-        sqlda_t *cur_sqlda;
-
-        /* Assign descriptor to the cursor  */
-        EXEC SQL FETCH NEXT FROM cur1 INTO DESCRIPTOR sqlda1;
-
-        for (cur_sqlda = sqlda1 ;
-             cur_sqlda != NULL ;
-             cur_sqlda = cur_sqlda->desc_next)
-        {
-            int i;
-            char name_buf[1024];
-            char var_buf[1024];
-
-            /* Print every column in a row. */
-            for (i=0 ; i&lt;cur_sqlda->sqld ; i++)
-            {
-                sqlvar_t v = cur_sqlda->sqlvar[i];
-                char *sqldata = v.sqldata;
-                short sqllen  = v.sqllen;
-
-                strncpy(name_buf, v.sqlname.data, v.sqlname.length);
-                name_buf[v.sqlname.length] = '\0';
-
-                switch (v.sqltype)
-                {
-                    case ECPGt_char:
-                        memset(&amp;var_buf, 0, sizeof(var_buf));
-                        memcpy(&amp;var_buf, sqldata, (sizeof(var_buf)&lt;=sqllen ? sizeof(var_buf)-1 : sqllen) );
-                        break;
-
-                    case ECPGt_int: /* integer */
-                        memcpy(&amp;intval, sqldata, sqllen);
-                        snprintf(var_buf, sizeof(var_buf), "%d", intval);
-                        break;
-
-                    case ECPGt_long_long: /* bigint */
-                        memcpy(&amp;longlongval, sqldata, sqllen);
-                        snprintf(var_buf, sizeof(var_buf), "%lld", longlongval);
-                        break;
-
-                    default:
-                    {
-                        int i;
-                        memset(var_buf, 0, sizeof(var_buf));
-                        for (i = 0; i &lt; sqllen; i++)
-                        {
-                            char tmpbuf[16];
-                            snprintf(tmpbuf, sizeof(tmpbuf), "%02x ", (unsigned char) sqldata[i]);
-                            strncat(var_buf, tmpbuf, sizeof(var_buf));
-                        }
-                    }
-                        break;
-                }
-
-                printf("%s = %s (type: %d)\n", name_buf, var_buf, v.sqltype);
-            }
-
-            printf("\n");
-        }
-    }
-
-    EXEC SQL CLOSE cur1;
-    EXEC SQL COMMIT;
-
-    EXEC SQL DISCONNECT ALL;
-
-    return 0;
-}
-</programlisting>
-
-     <para>
-      The output of this example should look something like the
-      following (some numbers will vary).
-     </para>
-
-<screen>
-oid = 1 (type: 1)
-datname = template1 (type: 1)
-datdba = 10 (type: 1)
-encoding = 0 (type: 5)
-datistemplate = t (type: 1)
-datallowconn = t (type: 1)
-datconnlimit = -1 (type: 5)
-datlastsysoid = 11510 (type: 1)
-datfrozenxid = 379 (type: 1)
-dattablespace = 1663 (type: 1)
-datconfig =  (type: 1)
-datacl = {=c/uptime,uptime=CTc/uptime} (type: 1)
-datid = 1 (type: 1)
-datname = template1 (type: 1)
-numbackends = 0 (type: 5)
-xact_commit = 113606 (type: 9)
-xact_rollback = 0 (type: 9)
-blks_read = 130 (type: 9)
-blks_hit = 7341714 (type: 9)
-tup_returned = 38262679 (type: 9)
-tup_fetched = 1836281 (type: 9)
-tup_inserted = 0 (type: 9)
-tup_updated = 0 (type: 9)
-tup_deleted = 0 (type: 9)
-
-oid = 11511 (type: 1)
-datname = postgres (type: 1)
-datdba = 10 (type: 1)
-encoding = 0 (type: 5)
-datistemplate = f (type: 1)
-datallowconn = t (type: 1)
-datconnlimit = -1 (type: 5)
-datlastsysoid = 11510 (type: 1)
-datfrozenxid = 379 (type: 1)
-dattablespace = 1663 (type: 1)
-datconfig =  (type: 1)
-datacl =  (type: 1)
-datid = 11511 (type: 1)
-datname = postgres (type: 1)
-numbackends = 0 (type: 5)
-xact_commit = 221069 (type: 9)
-xact_rollback = 18 (type: 9)
-blks_read = 1176 (type: 9)
-blks_hit = 13943750 (type: 9)
-tup_returned = 77410091 (type: 9)
-tup_fetched = 3253694 (type: 9)
-tup_inserted = 0 (type: 9)
-tup_updated = 0 (type: 9)
-tup_deleted = 0 (type: 9)
-</screen>
-    </example>
-   </sect3>
-  </sect2>
- </sect1>
-
- <sect1 id="ecpg-errors">
-  <title>Error Handling</title>
-
-&common;
-  <para>
-   This section describes how you can handle exceptional conditions
-   and warnings in an embedded SQL program.  There are two
-   nonexclusive facilities for this.
-
-   <itemizedlist>
-    <listitem>
-     <simpara>
-      Callbacks can be configured to handle warning and error
-      conditions using the <literal>WHENEVER</literal> command.
-     </simpara>
-    </listitem>
-
-    <listitem>
-     <simpara>
-      Detailed information about the error or warning can be obtained
-      from the <varname>sqlca</varname> variable.
-     </simpara>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <sect2 id="ecpg-whenever">
-   <title>Setting Callbacks</title>
-
-&common;
-   <para>
-    One simple method to catch errors and warnings is to set a
-    specific action to be executed whenever a particular condition
-    occurs.  In general:
-<programlisting>
-EXEC SQL WHENEVER <replaceable>condition</replaceable> <replaceable>action</replaceable>;
-</programlisting>
-   </para>
-
-   <para>
-    <replaceable>condition</replaceable> can be one of the following:
-
-    <variablelist>
-     <varlistentry>
-      <term><literal>SQLERROR</literal></term>
-      <listitem>
-       <para>
-        The specified action is called whenever an error occurs during
-        the execution of an SQL statement.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>SQLWARNING</literal></term>
-      <listitem>
-       <para>
-        The specified action is called whenever a warning occurs
-        during the execution of an SQL statement.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>NOT FOUND</literal></term>
-      <listitem>
-       <para>
-        The specified action is called whenever an SQL statement
-        retrieves or affects zero rows.  (This condition is not an
-        error, but you might be interested in handling it specially.)
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    <replaceable>action</replaceable> can be one of the following:
-
-    <variablelist>
-     <varlistentry>
-      <term><literal>CONTINUE</literal></term>
-      <listitem>
-       <para>
-        This effectively means that the condition is ignored.  This is
-        the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>GOTO <replaceable>label</replaceable></literal></term>
-      <term><literal>GO TO <replaceable>label</replaceable></literal></term>
-      <listitem>
-       <para>
-        Jump to the specified label (using a C <literal>goto</literal>
-        statement).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>SQLPRINT</literal></term>
-      <listitem>
-       <para>
-        Print a message to standard error.  This is useful for simple
-        programs or during prototyping.  The details of the message
-        cannot be configured.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>STOP</literal></term>
-      <listitem>
-       <para>
-        Call <literal>exit(1)</literal>, which will terminate the
-        program.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>DO BREAK</literal></term>
-      <listitem>
-       <para>
-        Execute the C statement <literal>break</literal>.  This should
-        only be used in loops or <literal>switch</literal> statements.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CALL <replaceable>name</replaceable> (<replaceable>args</replaceable>)</literal></term>
-      <term><literal>DO <replaceable>name</replaceable> (<replaceable>args</replaceable>)</literal></term>
-      <listitem>
-       <para>
-        Call the specified C functions with the specified arguments.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    The SQL standard only provides for the actions
-    <literal>CONTINUE</literal> and <literal>GOTO</literal> (and
-    <literal>GO TO</literal>).
-   </para>
-
-   <para>
-    Here is an example that you might want to use in a simple program.
-    It prints a simple message when a warning occurs and aborts the
-    program when an error happens:
-<programlisting>
-EXEC SQL WHENEVER SQLWARNING SQLPRINT;
-EXEC SQL WHENEVER SQLERROR STOP;
-</programlisting>
-   </para>
-
-   <para>
-    The statement <literal>EXEC SQL WHENEVER</literal> is a directive
-    of the SQL preprocessor, not a C statement.  The error or warning
-    actions that it sets apply to all embedded SQL statements that
-    appear below the point where the handler is set, unless a
-    different action was set for the same condition between the first
-    <literal>EXEC SQL WHENEVER</literal> and the SQL statement causing
-    the condition, regardless of the flow of control in the C program.
-    So neither of the two following C program excerpts will have the
-    desired effect:
-<programlisting>
-/*
- * WRONG
- */
-int main(int argc, char *argv[])
-{
-    ...
-    if (verbose) {
-        EXEC SQL WHENEVER SQLWARNING SQLPRINT;
-    }
-    ...
-    EXEC SQL SELECT ...;
-    ...
-}
-</programlisting>
-
-<programlisting>
-/*
- * WRONG
- */
-int main(int argc, char *argv[])
-{
-    ...
-    set_error_handler();
-    ...
-    EXEC SQL SELECT ...;
-    ...
-}
-
-static void set_error_handler(void)
-{
-    EXEC SQL WHENEVER SQLERROR STOP;
-}
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-sqlca">
-   <title>sqlca</title>
-
-&common;
-   <para>
-    For more powerful error handling, the embedded SQL interface
-    provides a global variable with the name <varname>sqlca</varname>
-    (SQL communication area)
-    that has the following structure:
-<programlisting>
-struct
-{
-    char sqlcaid[8];
-    long sqlabc;
-    long sqlcode;
-    struct
-    {
-        int sqlerrml;
-        char sqlerrmc[SQLERRMC_LEN];
-    } sqlerrm;
-    char sqlerrp[8];
-    long sqlerrd[6];
-    char sqlwarn[8];
-    char sqlstate[5];
-} sqlca;
-</programlisting>
-    (In a multithreaded program, every thread automatically gets its
-    own copy of <varname>sqlca</varname>.  This works similarly to the
-    handling of the standard C global variable
-    <varname>errno</varname>.)
-   </para>
-
-   <para>
-    <varname>sqlca</varname> covers both warnings and errors.  If
-    multiple warnings or errors occur during the execution of a
-    statement, then <varname>sqlca</varname> will only contain
-    information about the last one.
-   </para>
-
-   <para>
-    If no error occurred in the last <acronym>SQL</acronym> statement,
-    <literal>sqlca.sqlcode</literal> will be 0 and
-    <literal>sqlca.sqlstate</literal> will be
-    <literal>"00000"</literal>.  If a warning or error occurred, then
-    <literal>sqlca.sqlcode</literal> will be negative and
-    <literal>sqlca.sqlstate</literal> will be different from
-    <literal>"00000"</literal>.  A positive
-    <literal>sqlca.sqlcode</literal> indicates a harmless condition,
-    such as that the last query returned zero rows.
-    <literal>sqlcode</literal> and <literal>sqlstate</literal> are two
-    different error code schemes; details appear below.
-   </para>
-
-   <para>
-    If the last SQL statement was successful, then
-    <literal>sqlca.sqlerrd[1]</literal> contains the OID of the
-    processed row, if applicable, and
-    <literal>sqlca.sqlerrd[2]</literal> contains the number of
-    processed or returned rows, if applicable to the command.
-   </para>
-
-   <para>
-    In case of an error or warning,
-    <literal>sqlca.sqlerrm.sqlerrmc</literal> will contain a string
-    that describes the error.  The field
-    <literal>sqlca.sqlerrm.sqlerrml</literal> contains the length of
-    the error message that is stored in
-    <literal>sqlca.sqlerrm.sqlerrmc</literal> (the result of
-    <function>strlen()</function>, not really interesting for a C
-    programmer).  Note that some messages are too long to fit in the
-    fixed-size <literal>sqlerrmc</literal> array; they will be truncated.
-   </para>
-
-   <para>
-    In case of a warning, <literal>sqlca.sqlwarn[2]</literal> is set
-    to <literal>W</literal>.  (In all other cases, it is set to
-    something different from <literal>W</literal>.)  If
-    <literal>sqlca.sqlwarn[1]</literal> is set to
-    <literal>W</literal>, then a value was truncated when it was
-    stored in a host variable.  <literal>sqlca.sqlwarn[0]</literal> is
-    set to <literal>W</literal> if any of the other elements are set
-    to indicate a warning.
-   </para>
-
-   <para>
-    The fields <structfield>sqlcaid</structfield>,
-    <structfield>sqlcabc</structfield>,
-    <structfield>sqlerrp</structfield>, and the remaining elements of
-    <structfield>sqlerrd</structfield> and
-    <structfield>sqlwarn</structfield> currently contain no useful
-    information.
-   </para>
-
-   <para>
-    The structure <varname>sqlca</varname> is not defined in the SQL
-    standard, but is implemented in several other SQL database
-    systems.  The definitions are similar at the core, but if you want
-    to write portable applications, then you should investigate the
-    different implementations carefully.
-   </para>
-
-   <para>
-    Here is one example that combines the use of <literal>WHENEVER</>
-    and <varname>sqlca</varname>, printing out the contents
-    of <varname>sqlca</varname> when an error occurs.  This is perhaps
-    useful for debugging or prototyping applications, before
-    installing a more <quote>user-friendly</quote> error handler.
-
-<programlisting>
-EXEC SQL WHENEVER SQLERROR CALL print_sqlca();
-
-void
-print_sqlca()
-{
-    fprintf(stderr, "==== sqlca ====\n");
-    fprintf(stderr, "sqlcode: %ld\n", sqlca.sqlcode);
-    fprintf(stderr, "sqlerrm.sqlerrml: %d\n", sqlca.sqlerrm.sqlerrml);
-    fprintf(stderr, "sqlerrm.sqlerrmc: %s\n", sqlca.sqlerrm.sqlerrmc);
-    fprintf(stderr, "sqlerrd: %ld %ld %ld %ld %ld %ld\n", sqlca.sqlerrd[0],sqlca.sqlerrd[1],sqlca.sqlerrd[2],
-                                                          sqlca.sqlerrd[3],sqlca.sqlerrd[4],sqlca.sqlerrd[5]);
-    fprintf(stderr, "sqlwarn: %d %d %d %d %d %d %d %d\n", sqlca.sqlwarn[0], sqlca.sqlwarn[1], sqlca.sqlwarn[2],
-                                                          sqlca.sqlwarn[3], sqlca.sqlwarn[4], sqlca.sqlwarn[5],
-                                                          sqlca.sqlwarn[6], sqlca.sqlwarn[7]);
-    fprintf(stderr, "sqlstate: %5s\n", sqlca.sqlstate);
-    fprintf(stderr, "===============\n");
-}
-</programlisting>
-
-    The result could look as follows (here an error due to a
-    misspelled table name):
-
-<screen>
-==== sqlca ====
-sqlcode: -400
-sqlerrm.sqlerrml: 49
-sqlerrm.sqlerrmc: relation "pg_databasep" does not exist on line 38
-sqlerrd: 0 0 0 0 0 0
-sqlwarn: 0 0 0 0 0 0 0 0
-sqlstate: 42P01
-===============
-</screen>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-sqlstate-sqlcode">
-   <title><literal>SQLSTATE</literal> vs. <literal>SQLCODE</literal></title>
-
-&common;
-   <para>
-    The fields <literal>sqlca.sqlstate</literal> and
-    <literal>sqlca.sqlcode</literal> are two different schemes that
-    provide error codes.  Both are derived from the SQL standard, but
-    <literal>SQLCODE</literal> has been marked deprecated in the SQL-92
-    edition of the standard and has been dropped in later editions.
-    Therefore, new applications are strongly encouraged to use
-    <literal>SQLSTATE</literal>.
-   </para>
-
-   <para>
-    <literal>SQLSTATE</literal> is a five-character array.  The five
-    characters contain digits or upper-case letters that represent
-    codes of various error and warning conditions.
-    <literal>SQLSTATE</literal> has a hierarchical scheme: the first
-    two characters indicate the general class of the condition, the
-    last three characters indicate a subclass of the general
-    condition.  A successful state is indicated by the code
-    <literal>00000</literal>.  The <literal>SQLSTATE</literal> codes are for
-    the most part defined in the SQL standard.  The
-    <productname>PostgreSQL</productname> server natively supports
-    <literal>SQLSTATE</literal> error codes; therefore a high degree
-    of consistency can be achieved by using this error code scheme
-    throughout all applications.  For further information see
-    <xref linkend="errcodes-appendix">.
-   </para>
-
-   <para>
-    <literal>SQLCODE</literal>, the deprecated error code scheme, is a
-    simple integer.  A value of 0 indicates success, a positive value
-    indicates success with additional information, a negative value
-    indicates an error.  The SQL standard only defines the positive
-    value +100, which indicates that the last command returned or
-    affected zero rows, and no specific negative values.  Therefore,
-    this scheme can only achieve poor portability and does not have a
-    hierarchical code assignment.  Historically, the embedded SQL
-    processor for <productname>PostgreSQL</productname> has assigned
-    some specific <literal>SQLCODE</literal> values for its use, which
-    are listed below with their numeric value and their symbolic name.
-    Remember that these are not portable to other SQL implementations.
-    To simplify the porting of applications to the
-    <literal>SQLSTATE</literal> scheme, the corresponding
-    <literal>SQLSTATE</literal> is also listed.  There is, however, no
-    one-to-one or one-to-many mapping between the two schemes (indeed
-    it is many-to-many), so you should consult the global
-    <literal>SQLSTATE</literal> listing in <xref linkend="errcodes-appendix">
-    in each case.
-   </para>
-
-   <para>
-    These are the assigned <literal>SQLCODE</literal> values:
-
-    <variablelist>
-     <varlistentry>
-      <term>0 (<symbol>ECPG_NO_ERROR</symbol>)</term>
-      <listitem>
-       <para>
-        Indicates no error. (SQLSTATE 00000)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>100 (<symbol>ECPG_NOT_FOUND</symbol>)</term>
-     <listitem>
-      <para>
-       This is a harmless condition indicating that the last command
-       retrieved or processed zero rows, or that you are at the end of
-       the cursor.  (SQLSTATE 02000)
-      </para>
-
-      <para>
-       When processing a cursor in a loop, you could use this code as
-       a way to detect when to abort the loop, like this:
-<programlisting>
-while (1)
-{
-    EXEC SQL FETCH ... ;
-    if (sqlca.sqlcode == ECPG_NOT_FOUND)
-        break;
-}
-</programlisting>
-       But <literal>WHENEVER NOT FOUND DO BREAK</literal> effectively
-       does this internally, so there is usually no advantage in
-       writing this out explicitly.
-      </para>
-     </listitem>
-    </varlistentry>
-
-     <varlistentry>
-      <term>-12 (<symbol>ECPG_OUT_OF_MEMORY</symbol>)</term>
-      <listitem>
-       <para>
-        Indicates that your virtual memory is exhausted.  The numeric
-        value is defined as <literal>-ENOMEM</literal>.  (SQLSTATE
-        YE001)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-200 (<symbol>ECPG_UNSUPPORTED</symbol>)</term>
-     <listitem>
-      <para>
-       Indicates the preprocessor has generated something that the
-       library does not know about.  Perhaps you are running
-       incompatible versions of the preprocessor and the
-       library. (SQLSTATE YE002)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-201 (<symbol>ECPG_TOO_MANY_ARGUMENTS</symbol>)</term>
-     <listitem>
-      <para>
-       This means that the command specified more host variables than
-       the command expected.  (SQLSTATE 07001 or 07002)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-202 (<symbol>ECPG_TOO_FEW_ARGUMENTS</symbol>)</term>
-     <listitem>
-      <para>
-       This means that the command specified fewer host variables than
-       the command expected.  (SQLSTATE 07001 or 07002)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-203 (<symbol>ECPG_TOO_MANY_MATCHES</symbol>)</term>
-     <listitem>
-      <para>
-       This means a query has returned multiple rows but the statement
-       was only prepared to store one result row (for example, because
-       the specified variables are not arrays).  (SQLSTATE 21000)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-204 (<symbol>ECPG_INT_FORMAT</symbol>)</term>
-     <listitem>
-      <para>
-       The host variable is of type <type>int</type> and the datum in
-       the database is of a different type and contains a value that
-       cannot be interpreted as an <type>int</type>.  The library uses
-       <function>strtol()</function> for this conversion.  (SQLSTATE
-       42804)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-205 (<symbol>ECPG_UINT_FORMAT</symbol>)</term>
-     <listitem>
-      <para>
-       The host variable is of type <type>unsigned int</type> and the
-       datum in the database is of a different type and contains a
-       value that cannot be interpreted as an <type>unsigned
-       int</type>.  The library uses <function>strtoul()</function>
-       for this conversion.  (SQLSTATE 42804)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-206 (<symbol>ECPG_FLOAT_FORMAT</symbol>)</term>
-     <listitem>
-      <para>
-       The host variable is of type <type>float</type> and the datum
-       in the database is of another type and contains a value that
-       cannot be interpreted as a <type>float</type>.  The library
-       uses <function>strtod()</function> for this conversion.
-       (SQLSTATE 42804)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-207 (<symbol>ECPG_NUMERIC_FORMAT</symbol>)</term>
-     <listitem>
-      <para>
-       The host variable is of type <type>numeric</type> and the datum
-       in the database is of another type and contains a value that
-       cannot be interpreted as a <type>numeric</type> value.
-       (SQLSTATE 42804)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-208 (<symbol>ECPG_INTERVAL_FORMAT</symbol>)</term>
-     <listitem>
-      <para>
-       The host variable is of type <type>interval</type> and the datum
-       in the database is of another type and contains a value that
-       cannot be interpreted as an <type>interval</type> value.
-       (SQLSTATE 42804)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-209 (<symbol>ECPG_DATE_FORMAT</symbol>)</term>
-     <listitem>
-      <para>
-       The host variable is of type <type>date</type> and the datum in
-       the database is of another type and contains a value that
-       cannot be interpreted as a <type>date</type> value.
-       (SQLSTATE 42804)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-210 (<symbol>ECPG_TIMESTAMP_FORMAT</symbol>)</term>
-     <listitem>
-      <para>
-       The host variable is of type <type>timestamp</type> and the
-       datum in the database is of another type and contains a value
-       that cannot be interpreted as a <type>timestamp</type> value.
-       (SQLSTATE 42804)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-211 (<symbol>ECPG_CONVERT_BOOL</symbol>)</term>
-     <listitem>
-      <para>
-       This means the host variable is of type <type>bool</type> and
-       the datum in the database is neither <literal>'t'</> nor
-       <literal>'f'</>.  (SQLSTATE 42804)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-212 (<symbol>ECPG_EMPTY</symbol>)</term>
-     <listitem>
-      <para>
-       The statement sent to the <productname>PostgreSQL</productname>
-       server was empty.  (This cannot normally happen in an embedded
-       SQL program, so it might point to an internal error.)  (SQLSTATE
-       YE002)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-213 (<symbol>ECPG_MISSING_INDICATOR</symbol>)</term>
-     <listitem>
-      <para>
-       A null value was returned and no null indicator variable was
-       supplied.  (SQLSTATE 22002)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-214 (<symbol>ECPG_NO_ARRAY</symbol>)</term>
-     <listitem>
-      <para>
-       An ordinary variable was used in a place that requires an
-       array.  (SQLSTATE 42804)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-215 (<symbol>ECPG_DATA_NOT_ARRAY</symbol>)</term>
-     <listitem>
-      <para>
-       The database returned an ordinary variable in a place that
-       requires array value.  (SQLSTATE 42804)
-      </para>
-     </listitem>
-    </varlistentry>
-
-<![IGNORE[
-    <!-- disabled by #if 0 in ecpglib -->
-    <varlistentry>
-     <term>-216 (<symbol>ECPG_ARRAY_INSERT</symbol>)</term>
-     <listitem>
-      <para>
-       The value could not be inserted into the array.  (SQLSTATE
-       42804)
-      </para>
-     </listitem>
-    </varlistentry>
-]]>
-
-    <varlistentry>
-     <term>-220 (<symbol>ECPG_NO_CONN</symbol>)</term>
-     <listitem>
-      <para>
-       The program tried to access a connection that does not exist.
-       (SQLSTATE 08003)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-221 (<symbol>ECPG_NOT_CONN</symbol>)</term>
-     <listitem>
-      <para>
-       The program tried to access a connection that does exist but is
-       not open.  (This is an internal error.)  (SQLSTATE YE002)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-230 (<symbol>ECPG_INVALID_STMT</symbol>)</term>
-     <listitem>
-      <para>
-       The statement you are trying to use has not been prepared.
-       (SQLSTATE 26000)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-239 (<symbol>ECPG_INFORMIX_DUPLICATE_KEY</symbol>)</term>
-     <listitem>
-      <para>
-       Duplicate key error, violation of unique constraint (Informix
-       compatibility mode).  (SQLSTATE 23505)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-240 (<symbol>ECPG_UNKNOWN_DESCRIPTOR</symbol>)</term>
-     <listitem>
-      <para>
-       The descriptor specified was not found.  The statement you are
-       trying to use has not been prepared.  (SQLSTATE 33000)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-241 (<symbol>ECPG_INVALID_DESCRIPTOR_INDEX</symbol>)</term>
-     <listitem>
-      <para>
-       The descriptor index specified was out of range.  (SQLSTATE
-       07009)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-242 (<symbol>ECPG_UNKNOWN_DESCRIPTOR_ITEM</symbol>)</term>
-     <listitem>
-      <para>
-       An invalid descriptor item was requested.  (This is an internal
-       error.)  (SQLSTATE YE002)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-243 (<symbol>ECPG_VAR_NOT_NUMERIC</symbol>)</term>
-     <listitem>
-      <para>
-       During the execution of a dynamic statement, the database
-       returned a numeric value and the host variable was not numeric.
-       (SQLSTATE 07006)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-244 (<symbol>ECPG_VAR_NOT_CHAR</symbol>)</term>
-     <listitem>
-      <para>
-       During the execution of a dynamic statement, the database
-       returned a non-numeric value and the host variable was numeric.
-       (SQLSTATE 07006)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-284 (<symbol>ECPG_INFORMIX_SUBSELECT_NOT_ONE</symbol>)</term>
-     <listitem>
-      <para>
-       A result of the subquery is not single row (Informix
-       compatibility mode).  (SQLSTATE 21000)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-400 (<symbol>ECPG_PGSQL</symbol>)</term>
-     <listitem>
-      <para>
-       Some error caused by the <productname>PostgreSQL</productname>
-       server.  The message contains the error message from the
-       <productname>PostgreSQL</productname> server.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-401 (<symbol>ECPG_TRANS</symbol>)</term>
-     <listitem>
-      <para>
-       The <productname>PostgreSQL</productname> server signaled that
-       we cannot start, commit, or rollback the transaction.
-       (SQLSTATE 08007)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-402 (<symbol>ECPG_CONNECT</symbol>)</term>
-     <listitem>
-      <para>
-       The connection attempt to the database did not succeed.
-       (SQLSTATE 08001)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-403 (<symbol>ECPG_DUPLICATE_KEY</symbol>)</term>
-     <listitem>
-      <para>
-       Duplicate key error, violation of unique constraint.  (SQLSTATE
-       23505)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-404 (<symbol>ECPG_SUBSELECT_NOT_ONE</symbol>)</term>
-     <listitem>
-      <para>
-       A result for the subquery is not single row. (SQLSTATE 21000)
-      </para>
-     </listitem>
-    </varlistentry>
-
-<![IGNORE[
-    <!-- currently not used by the code -->
-    <varlistentry>
-     <term>-600 (<symbol>ECPG_WARNING_UNRECOGNIZED</symbol>)</term>
-     <listitem>
-      <para>
-       An unrecognized warning was received from the server.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-601 (<symbol>ECPG_WARNING_QUERY_IGNORED</symbol>)</term>
-     <listitem>
-      <para>
-       Current transaction is aborted.  Queries are ignored until the
-       end of the transaction block.
-      </para>
-     </listitem>
-    </varlistentry>
-]]>
-
-    <varlistentry>
-     <term>-602 (<symbol>ECPG_WARNING_UNKNOWN_PORTAL</symbol>)</term>
-     <listitem>
-      <para>
-       An invalid cursor name was specified. (SQLSTATE 34000)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-603 (<symbol>ECPG_WARNING_IN_TRANSACTION</symbol>)</term>
-     <listitem>
-      <para>
-       Transaction is in progress. (SQLSTATE 25001)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-604 (<symbol>ECPG_WARNING_NO_TRANSACTION</symbol>)</term>
-     <listitem>
-      <para>
-       There is no active (in-progress) transaction. (SQLSTATE 25P01)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>-605 (<symbol>ECPG_WARNING_PORTAL_EXISTS</symbol>)</term>
-     <listitem>
-      <para>
-       An existing cursor name was specified. (SQLSTATE 42P03)
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-  </sect2>
- </sect1>
-
- <sect1 id="ecpg-preproc">
-  <title>Preprocessor Directives</title>
-
-&common;
-  <para>
-   Several preprocessor directives are available that modify how
-   the <command>ecpg</command> preprocessor parses and processes a
-   file.
-  </para>
-
-  <sect2 id="ecpg-include">
-   <title>Including Files</title>
-
-&common;
-   <para>
-    To include an external file into your embedded SQL program, use:
-<programlisting>
-EXEC SQL INCLUDE <replaceable>filename</replaceable>;
-EXEC SQL INCLUDE &lt;<replaceable>filename</replaceable>&gt;;
-EXEC SQL INCLUDE "<replaceable>filename</replaceable>";
-</programlisting>
-    The embedded SQL preprocessor will look for a file named
-    <literal><replaceable>filename</replaceable>.h</literal>,
-    preprocess it, and include it in the resulting C output.  Thus,
-    embedded SQL statements in the included file are handled correctly.
-   </para>
-
-   <para>
-    The <command>ecpg</command> preprocessor will search a file at
-    several directories in following order:
-
-    <itemizedlist>
-     <listitem><simpara>current directory</simpara></listitem>
-     <listitem><simpara><filename>/usr/local/include</filename></simpara></listitem>
-     <listitem><simpara>PostgreSQL include directory, defined at build time (e.g., <filename>/usr/local/pgsql/include</filename>)</simpara></listitem>
-     <listitem><simpara><filename>/usr/include</filename></simpara></listitem>
-    </itemizedlist>
-
-    But when <literal>EXEC SQL INCLUDE
-    "<replaceable>filename</replaceable>"</literal> is used, only the
-    current directory is searched.
-   </para>
-
-   <para>
-    In each directory, the preprocessor will first look for the file
-    name as given, and if not found will append <literal>.h</literal>
-    to the file name and try again (unless the specified file name
-    already has that suffix).
-   </para>
-
-   <para>
-    Note that <command>EXEC SQL INCLUDE</command> is <emphasis>not</emphasis> the same as:
-<programlisting>
-#include &lt;<replaceable>filename</replaceable>.h&gt;
-</programlisting>
-    because this file would not be subject to SQL command preprocessing.
-    Naturally, you can continue to use the C
-    <literal>#include</literal> directive to include other header
-    files.
-   </para>
-
-   <note>
-    <para>
-     The include file name is case-sensitive, even though the rest of
-     the <literal>EXEC SQL INCLUDE</literal> command follows the normal
-     SQL case-sensitivity rules.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2 id="ecpg-define">
-   <title>The define and undef Directives</title>
-&common;
-   <para>
-    Similar to the directive <literal>#define</literal> that is known from C,
-    embedded SQL has a similar concept:
-<programlisting>
-EXEC SQL DEFINE <replaceable>name</>;
-EXEC SQL DEFINE <replaceable>name</> <replaceable>value</>;
-</programlisting>
-    So you can define a name:
-<programlisting>
-EXEC SQL DEFINE HAVE_FEATURE;
-</programlisting>
-    And you can also define constants:
-<programlisting>
-EXEC SQL DEFINE MYNUMBER 12;
-EXEC SQL DEFINE MYSTRING 'abc';
-</programlisting>
-    Use <literal>undef</> to remove a previous definition:
-<programlisting>
-EXEC SQL UNDEF MYNUMBER;
-</programlisting>
-   </para>
-
-   <para>
-    Of course you can continue to use the C versions <literal>#define</literal>
-    and <literal>#undef</literal> in your embedded SQL program. The difference
-    is where your defined values get evaluated. If you use <literal>EXEC SQL
-    DEFINE</> then the <command>ecpg</> preprocessor evaluates the defines and substitutes
-    the values. For example if you write:
-<programlisting>
-EXEC SQL DEFINE MYNUMBER 12;
-...
-EXEC SQL UPDATE Tbl SET col = MYNUMBER;
-</programlisting>
-    then <command>ecpg</> will already do the substitution and your C compiler will never
-    see any name or identifier <literal>MYNUMBER</>. Note that you cannot use
-    <literal>#define</literal> for a constant that you are going to use in an
-    embedded SQL query because in this case the embedded SQL precompiler is not
-    able to see this declaration.
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-ifdef">
-   <title>ifdef, ifndef, else, elif, and endif Directives</title>
-&common;
-   <para>
-   You can use the following directives to compile code sections conditionally:
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>EXEC SQL ifdef <replaceable>name</>;</literal></term>
-     <listitem>
-     <para>
-      Checks a <replaceable>name</> and processes subsequent lines if
-      <replaceable>name</> has been created with <literal>EXEC SQL define
-      <replaceable>name</></literal>.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>EXEC SQL ifndef <replaceable>name</>;</literal></term>
-     <listitem>
-     <para>
-      Checks a <replaceable>name</> and processes subsequent lines if
-      <replaceable>name</> has <emphasis>not</emphasis> been created with
-      <literal>EXEC SQL define <replaceable>name</></literal>.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>EXEC SQL else;</literal></term>
-     <listitem>
-     <para>
-      Starts processing an alternative section to a section introduced by
-      either <literal>EXEC SQL ifdef <replaceable>name</></literal> or
-      <literal>EXEC SQL ifndef <replaceable>name</></literal>.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>EXEC SQL elif <replaceable>name</>;</literal></term>
-     <listitem>
-     <para>
-      Checks <replaceable>name</> and starts an alternative section if
-      <replaceable>name</> has been created with <literal>EXEC SQL define
-      <replaceable>name</></literal>.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>EXEC SQL endif;</literal></term>
-     <listitem>
-     <para>
-      Ends an alternative section.
-     </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-   </para>
-
-   <para>
-    Example:
-<programlisting>
-EXEC SQL ifndef TZVAR;
-EXEC SQL SET TIMEZONE TO 'GMT';
-EXEC SQL elif TZNAME;
-EXEC SQL SET TIMEZONE TO TZNAME;
-EXEC SQL else;
-EXEC SQL SET TIMEZONE TO TZVAR;
-EXEC SQL endif;
-</programlisting>
-   </para>
-
-  </sect2>
- </sect1>
-
-  <sect1 id="ecpg-process">
-  <title>Processing Embedded SQL Programs</title>
-
-&common;
-  <para>
-   Now that you have an idea how to form embedded SQL C programs, you
-   probably want to know how to compile them.  Before compiling you
-   run the file through the embedded <acronym>SQL</acronym>
-   <acronym>C</acronym> preprocessor, which converts the
-   <acronym>SQL</acronym> statements you used to special function
-   calls.  After compiling, you must link with a special library that
-   contains the needed functions. These functions fetch information
-   from the arguments, perform the <acronym>SQL</acronym> command using
-   the <application>libpq</application> interface, and put the result
-   in the arguments specified for output.
-  </para>
-
-  <para>
-   The preprocessor program is called <filename>ecpg</filename> and is
-   included in a normal <productname>PostgreSQL</> installation.
-   Embedded SQL programs are typically named with an extension
-   <filename>.pgc</filename>.  If you have a program file called
-   <filename>prog1.pgc</filename>, you can preprocess it by simply
-   calling:
-<programlisting>
-ecpg prog1.pgc
-</programlisting>
-   This will create a file called <filename>prog1.c</filename>.  If
-   your input files do not follow the suggested naming pattern, you
-   can specify the output file explicitly using the
-   <option>-o</option> option.
-  </para>
-
-  <para>
-   The preprocessed file can be compiled normally, for example:
-<programlisting>
-cc -c prog1.c
-</programlisting>
-   The generated C source files include header files from the
-   <productname>PostgreSQL</> installation, so if you installed
-   <productname>PostgreSQL</> in a location that is not searched by
-   default, you have to add an option such as
-   <literal>-I/usr/local/pgsql/include</literal> to the compilation
-   command line.
-  </para>
-
-  <para>
-   To link an embedded SQL program, you need to include the
-   <filename>libecpg</filename> library, like so:
-<programlisting>
-cc -o myprog prog1.o prog2.o ... -lecpg
-</programlisting>
-   Again, you might have to add an option like
-   <literal>-L/usr/local/pgsql/lib</literal> to that command line.
-  </para>
-
-  <para>
-   If you manage the build process of a larger project using
-   <application>make</application>, it might be convenient to include
-   the following implicit rule to your makefiles:
-<programlisting>
-ECPG = ecpg
-
-%.c: %.pgc
-        $(ECPG) $&lt;
-</programlisting>
-  </para>
-
-  <para>
-   The complete syntax of the <command>ecpg</command> command is
-   detailed in <xref linkend="app-ecpg">.
-  </para>
-
-  <para>
-   The <application>ecpg</application> library is thread-safe by
-   default.  However, you might need to use some threading
-   command-line options to compile your client code.
-  </para>
- </sect1>
-
- <sect1 id="ecpg-library">
-  <title>Library Functions</title>
-
-&common;
-  <para>
-   The <filename>libecpg</filename> library primarily contains
-   <quote>hidden</quote> functions that are used to implement the
-   functionality expressed by the embedded SQL commands.  But there
-   are some functions that can usefully be called directly.  Note that
-   this makes your code unportable.
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     <function>ECPGdebug(int <replaceable>on</replaceable>, FILE
-     *<replaceable>stream</replaceable>)</function> turns on debug
-     logging if called with the first argument non-zero. Debug logging
-     is done on <replaceable>stream</replaceable>.  The log contains
-     all <acronym>SQL</acronym> statements with all the input
-     variables inserted, and the results from the
-     <productname>PostgreSQL</productname> server. This can be very
-     useful when searching for errors in your <acronym>SQL</acronym>
-     statements.
-    </para>
-    <note>
-    <para>
-    On Windows, if the <application>ecpg</> libraries and an application are
-    compiled with different flags, this function call will crash the
-    application because the internal representation of the
-    <literal>FILE</> pointers differ.  Specifically,
-    multithreaded/single-threaded, release/debug, and static/dynamic
-    flags should be the same for the library and all applications using
-    that library.
-    </para>
-    </note>
-   </listitem>
-
-   <listitem>
-     <para>
-       <function>ECPGget_PGconn(const char *<replaceable>connection_name</replaceable>)
-       </function> returns the library database connection handle identified by the given name.
-       If <replaceable>connection_name</replaceable> is set to <literal>NULL</literal>, the current
-       connection handle is returned. If no connection handle can be identified, the function returns
-       <literal>NULL</literal>. The returned connection handle can be used to call any other functions
-       from <application>libpq</application>, if necessary.
-     </para>
-     <note>
-     <para>
-       It is a bad idea to manipulate database connection handles made from <application>ecpg</application> directly
-       with <application>libpq</application> routines.
-     </para>
-     </note>
-   </listitem>
-
-   <listitem>
-     <para>
-       <function>ECPGtransactionStatus(const char *<replaceable>connection_name</replaceable>)</function>
-       returns the current transaction status of the given connection identified by <replaceable>connection_name</replaceable>.
-       See <xref linkend="libpq-status"> and libpq's <function>PQtransactionStatus()</function> for details about the returned status codes.
-     </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <function>ECPGstatus(int <replaceable>lineno</replaceable>,
-     const char* <replaceable>connection_name</replaceable>)</function>
-     returns true if you are connected to a database and false if not.
-     <replaceable>connection_name</replaceable> can be <literal>NULL</>
-     if a single connection is being used.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect1>
-
- <sect1 id="ecpg-lo">
-  <title>Large Objects</title>
-
-&common;
-  <para>
-   Large objects are not directly supported by ECPG, but ECPG
-   application can manipulate large objects through the libpq large
-   object functions, obtaining the necessary <type>PGconn</type>
-   object by calling the <function>ECPGget_PGconn()</function>
-   function.  (However, use of
-   the <function>ECPGget_PGconn()</function> function and touching
-   <type>PGconn</type> objects directly should be done very carefully
-   and ideally not mixed with other ECPG database access calls.)
-  </para>
-
-  <para>
-   For more details about the <function>ECPGget_PGconn()</function>, see
-   <xref linkend="ecpg-library">.  For information about the large
-   object function interface, see <xref linkend="largeObjects">.
-  </para>
-
-  <para>
-   Large object functions have to be called in a transaction block, so
-   when autocommit is off, <command>BEGIN</command> commands have to
-   be issued explicitly.
-  </para>
-
-  <para>
-   <xref linkend="ecpg-lo-example"> shows an example program that
-   illustrates how to create, write, and read a large object in an
-   ECPG application.
-  </para>
-
-  <example id="ecpg-lo-example">
-   <title>ECPG Program Accessing Large Objects</title>
-<programlisting><![CDATA[
-#include <stdio.h>
-#include <stdlib.h>
-#include <libpq-fe.h>
-#include <libpq/libpq-fs.h>
-
-EXEC SQL WHENEVER SQLERROR STOP;
-
-int
-main(void)
-{
-    PGconn     *conn;
-    Oid         loid;
-    int         fd;
-    char        buf[256];
-    int         buflen = 256;
-    char        buf2[256];
-    int         rc;
-
-    memset(buf, 1, buflen);
-
-    EXEC SQL CONNECT TO testdb AS con1;
-
-    conn = ECPGget_PGconn("con1");
-    printf("conn = %p\n", conn);
-
-    /* create */
-    loid = lo_create(conn, 0);
-    if (loid &lt; 0)
-        printf("lo_create() failed: %s", PQerrorMessage(conn));
-
-    printf("loid = %d\n", loid);
-
-    /* write test */
-    fd = lo_open(conn, loid, INV_READ|INV_WRITE);
-    if (fd &lt; 0)
-        printf("lo_open() failed: %s", PQerrorMessage(conn));
-
-    printf("fd = %d\n", fd);
-
-    rc = lo_write(conn, fd, buf, buflen);
-    if (rc &lt; 0)
-        printf("lo_write() failed\n");
-
-    rc = lo_close(conn, fd);
-    if (rc &lt; 0)
-        printf("lo_close() failed: %s", PQerrorMessage(conn));
-
-    /* read test */
-    fd = lo_open(conn, loid, INV_READ);
-    if (fd &lt; 0)
-        printf("lo_open() failed: %s", PQerrorMessage(conn));
-
-    printf("fd = %d\n", fd);
-
-    rc = lo_read(conn, fd, buf2, buflen);
-    if (rc &lt; 0)
-        printf("lo_read() failed\n");
-
-    rc = lo_close(conn, fd);
-    if (rc &lt; 0)
-        printf("lo_close() failed: %s", PQerrorMessage(conn));
-
-    /* check */
-    rc = memcmp(buf, buf2, buflen);
-    printf("memcmp() = %d\n", rc);
-
-    /* cleanup */
-    rc = lo_unlink(conn, loid);
-    if (rc &lt; 0)
-        printf("lo_unlink() failed: %s", PQerrorMessage(conn));
-
-    EXEC SQL COMMIT;
-    EXEC SQL DISCONNECT ALL;
-    return 0;
-}
-]]></programlisting>
-  </example>
- </sect1>
-
- <sect1 id="ecpg-cpp">
-  <title><acronym>C++</acronym> Applications</title>
-
-&common;
-  <para>
-   ECPG has some limited support for C++ applications.  This section
-   describes some caveats.
-  </para>
-
-  <para>
-   The <command>ecpg</command> preprocessor takes an input file
-   written in C (or something like C) and embedded SQL commands,
-   converts the embedded SQL commands into C language chunks, and
-   finally generates a <filename>.c</filename> file.  The header file
-   declarations of the library functions used by the C language chunks
-   that <command>ecpg</command> generates are wrapped
-   in <literal>extern "C" { ... }</literal> blocks when used under
-   C++, so they should work seamlessly in C++.
-  </para>
-
-  <para>
-   In general, however, the <command>ecpg</command> preprocessor only
-   understands C; it does not handle the special syntax and reserved
-   words of the C++ language.  So, some embedded SQL code written in
-   C++ application code that uses complicated features specific to C++
-   might fail to be preprocessed correctly or might not work as
-   expected.
-  </para>
-
-  <para>
-   A safe way to use the embedded SQL code in a C++ application is
-   hiding the ECPG calls in a C module, which the C++ application code
-   calls into to access the database, and linking that together with
-   the rest of the C++ code.  See <xref linkend="ecpg-cpp-and-c">
-   about that.
-  </para>
-
-  <sect2 id="ecpg-cpp-scope">
-   <title>Scope for Host Variables</title>
-
-&common;
-   <para>
-    The <command>ecpg</command> preprocessor understands the scope of
-    variables in C.  In the C language, this is rather simple because
-    the scopes of variables is based on their code blocks.  In C++,
-    however, the class member variables are referenced in a different
-    code block from the declared position, so
-    the <command>ecpg</command> preprocessor will not understand the
-    scope of the class member variables.
-   </para>
-
-   <para>
-    For example, in the following case, the <command>ecpg</command>
-    preprocessor cannot find any declaration for the
-    variable <literal>dbname</literal> in the <literal>test</literal>
-    method, so an error will occur.
-
-<programlisting>
-class TestCpp
-{
-    EXEC SQL BEGIN DECLARE SECTION;
-    char dbname[1024];
-    EXEC SQL END DECLARE SECTION;
-
-  public:
-    TestCpp();
-    void test();
-    ~TestCpp();
-};
-
-TestCpp::TestCpp()
-{
-    EXEC SQL CONNECT TO testdb1;
-}
-
-void Test::test()
-{
-    EXEC SQL SELECT current_database() INTO :dbname;
-    printf("current_database = %s\n", dbname);
-}
-
-TestCpp::~TestCpp()
-{
-    EXEC SQL DISCONNECT ALL;
-}
-</programlisting>
-
-    This code will result in an error like this:
-<screen>
-<userinput>ecpg test_cpp.pgc</userinput>
-test_cpp.pgc:28: ERROR: variable "dbname" is not declared
-</screen>
-   </para>
-
-   <para>
-    To avoid this scope issue, the <literal>test</literal> method
-    could be modified to use a local variable as intermediate storage.
-    But this approach is only a poor workaround, because it uglifies
-    the code and reduces performance.
-
-<programlisting>
-void TestCpp::test()
-{
-    EXEC SQL BEGIN DECLARE SECTION;
-    char tmp[1024];
-    EXEC SQL END DECLARE SECTION;
-
-    EXEC SQL SELECT current_database() INTO :tmp;
-    strlcpy(dbname, tmp, sizeof(tmp));
-
-    printf("current_database = %s\n", dbname);
-}
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-cpp-and-c">
-   <title>C++ Application Development with External C Module</title>
-
-&common;
-   <para>
-    If you understand these technical limitations of
-    the <command>ecpg</command> preprocessor in C++, you might come to
-    the conclusion that linking C objects and C++ objects at the link
-    stage to enable C++ applications to use ECPG features could be
-    better than writing some embedded SQL commands in C++ code
-    directly.  This section describes a way to separate some embedded
-    SQL commands from C++ application code with a simple example.  In
-    this example, the application is implemented in C++, while C and
-    ECPG is used to connect to the PostgreSQL server.
-   </para>
-
-   <para>
-    Three kinds of files have to be created: a C file
-    (<filename>*.pgc</filename>), a header file, and a C++ file:
-
-    <variablelist>
-     <varlistentry>
-      <term><filename>test_mod.pgc</filename></term>
-      <listitem>
-       <para>
-        A sub-routine module to execute SQL commands embedded in C.
-        It is going to be converted
-        into <filename>test_mod.c</filename> by the preprocessor.
-
-<programlisting>
-#include "test_mod.h"
-#include &lt;stdio.h&gt;
-
-void
-db_connect()
-{
-    EXEC SQL CONNECT TO testdb1;
-}
-
-void
-db_test()
-{
-    EXEC SQL BEGIN DECLARE SECTION;
-    char dbname[1024];
-    EXEC SQL END DECLARE SECTION;
-
-    EXEC SQL SELECT current_database() INTO :dbname;
-    printf("current_database = %s\n", dbname);
-}
-
-void
-db_disconnect()
-{
-    EXEC SQL DISCONNECT ALL;
-}
-</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><filename>test_mod.h</filename></term>
-      <listitem>
-       <para>
-        A header file with declarations of the functions in the C
-        module (<filename>test_mod.pgc</filename>).  It is included by
-        <filename>test_cpp.cpp</filename>.  This file has to have an
-        <literal>extern "C"</literal> block around the declarations,
-        because it will be linked from the C++ module.
-
-<programlisting>
-#ifdef __cplusplus
-extern "C" {
-#endif
-
-void db_connect();
-void db_test();
-void db_disconnect();
-
-#ifdef __cplusplus
-}
-#endif
-</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><filename>test_cpp.cpp</filename></term>
-      <listitem>
-       <para>
-        The main code for the application, including
-        the <function>main</function> routine, and in this example a
-        C++ class.
-
-<programlisting>
-#include "test_mod.h"
-
-class TestCpp
-{
-  public:
-    TestCpp();
-    void test();
-    ~TestCpp();
-};
-
-TestCpp::TestCpp()
-{
-    db_connect();
-}
-
-void
-TestCpp::test()
-{
-    db_test();
-}
-
-TestCpp::~TestCpp()
-{
-    db_disconnect();
-}
-
-int
-main(void)
-{
-    TestCpp *t = new TestCpp();
-
-    t->test();
-    return 0;
-}
-</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    To build the application, proceed as follows.  Convert
-    <filename>test_mod.pgc</> into <filename>test_mod.c</> by
-    running <command>ecpg</command>, and generate
-    <filename>test_mod.o</> by compiling
-    <filename>test_mod.c</> with the C compiler:
-<programlisting>
-ecpg -o test_mod.c test_mod.pgc
-cc -c test_mod.c -o test_mod.o
-</programlisting>
-   </para>
-
-   <para>
-    Next, generate <filename>test_cpp.o</> by compiling
-    <filename>test_cpp.cpp</> with the C++ compiler:.
-<programlisting>
-c++ -c test_cpp.cpp -o test_cpp.o
-</programlisting>
-   </para>
-
-   <para>
-    Finally, link these object files, <filename>test_cpp.o</>
-    and <filename>test_mod.o</>, into one executable, using the C++
-    compiler driver:
-<programlisting>
-c++ test_cpp.o test_mod.o -lecpg -o test_cpp
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="ecpg-sql-commands">
-  <title>Embedded SQL Commands</title>
-
-&common;
-  <para>
-   This section describes all SQL commands that are specific to
-   embedded SQL.  Also refer to the SQL commands listed
-   in <xref linkend="sql-commands">, which can also be used in
-   embedded SQL, unless stated otherwise.
-  </para>
-
-  <refentry id="ecpg-sql-allocate-descriptor">
-   <refnamediv>
-    <refname>ALLOCATE DESCRIPTOR</refname>
-    <refpurpose>allocate an SQL descriptor area</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-ALLOCATE DESCRIPTOR <replaceable class="PARAMETER">name</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>ALLOCATE DESCRIPTOR</command> allocates a new named SQL
-     descriptor area, which can be used to exchange data between the
-     PostgreSQL server and the host program.
-    </para>
-
-    <para>
-     Descriptor areas should be freed after use using
-     the <command>DEALLOCATE DESCRIPTOR</command> command.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-        A name of SQL descriptor, case sensitive.  This can be an SQL
-        identifier or a host variable.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-<programlisting>
-EXEC SQL ALLOCATE DESCRIPTOR mydesc;
-</programlisting>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>ALLOCATE DESCRIPTOR</command> is specified in the SQL
-     standard.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="ecpg-sql-deallocate-descriptor"></member>
-     <member><xref linkend="ecpg-sql-get-descriptor"></member>
-     <member><xref linkend="ecpg-sql-set-descriptor"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-connect">
-   <refnamediv>
-    <refname>CONNECT</refname>
-    <refpurpose>establish a database connection</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-CONNECT TO <replaceable>connection_target</replaceable> [ AS <replaceable>connection_name</replaceable> ] [ USER <replaceable>connection_user_name</replaceable> ]
-CONNECT TO DEFAULT
-CONNECT <replaceable>connection_user_name</replaceable>
-DATABASE <replaceable>connection_target</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     The <command>CONNECT</command> command establishes a connection
-     between the client and the PostgreSQL server.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">connection_target</replaceable></term>
-      <listitem>
-       <para>
-        <replaceable class="PARAMETER">connection_target</replaceable>
-        specifies the target server of the connection on one of
-        several forms.
-
-        <variablelist>
-         <varlistentry>
-          <term>[ <replaceable>database_name</replaceable> ] [ <literal>@</literal><replaceable>host</replaceable> ] [ <literal>:</literal><replaceable>port</replaceable> ]</term>
-          <listitem>
-           <para>
-            Connect over TCP/IP
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>unix:postgresql://</literal><replaceable>host</replaceable> [ <literal>:</literal><replaceable>port</replaceable> ] <literal>/</literal> [ <replaceable>database_name</replaceable> ] [ <literal>?</literal><replaceable>connection_option</replaceable> ]</term>
-          <listitem>
-           <para>
-            Connect over Unix-domain sockets
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>tcp:postgresql://</literal><replaceable>host</replaceable> [ <literal>:</literal><replaceable>port</replaceable> ] <literal>/</literal> [ <replaceable>database_name</replaceable> ] [ <literal>?</literal><replaceable>connection_option</replaceable> ]</term>
-          <listitem>
-           <para>
-            Connect over TCP/IP
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term>SQL string constant</term>
-          <listitem>
-           <para>
-            containing a value in one of the above forms
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term>host variable</term>
-          <listitem>
-           <para>
-            host variable of type <type>char[]</type>
-            or <type>VARCHAR[]</type> containing a value in one of the
-            above forms
-           </para>
-          </listitem>
-         </varlistentry>
-        </variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">connection_object</replaceable></term>
-      <listitem>
-       <para>
-        An optional identifier for the connection, so that it can be
-        referred to in other commands.  This can be an SQL identifier
-        or a host variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">connection_user</replaceable></term>
-      <listitem>
-       <para>
-        The user name for the database connection.
-       </para>
-
-       <para>
-        This parameter can also specify user name and password, using one the forms
-        <literal><replaceable>user_name</replaceable>/<replaceable>password</replaceable></literal>,
-        <literal><replaceable>user_name</replaceable> IDENTIFIED BY <replaceable>password</replaceable></literal>, or
-        <literal><replaceable>user_name</replaceable> USING <replaceable>password</replaceable></literal>.
-       </para>
-
-       <para>
-        User name and password can be SQL identifiers, string
-        constants, or host variables.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>DEFAULT</literal></term>
-      <listitem>
-       <para>
-        Use all default connection parameters, as defined by libpq.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-    <para>
-     Here a several variants for specifying connection parameters:
-<programlisting>
-EXEC SQL CONNECT TO "connectdb" AS main;
-EXEC SQL CONNECT TO "connectdb" AS second;
-EXEC SQL CONNECT TO "unix:postgresql://200.46.204.71/connectdb" AS main USER connectuser;
-EXEC SQL CONNECT TO "unix:postgresql://localhost/connectdb" AS main USER connectuser;
-EXEC SQL CONNECT TO 'connectdb' AS main;
-EXEC SQL CONNECT TO 'unix:postgresql://localhost/connectdb' AS main USER :user;
-EXEC SQL CONNECT TO :db AS :id;
-EXEC SQL CONNECT TO :db USER connectuser USING :pw;
-EXEC SQL CONNECT TO @localhost AS main USER connectdb;
-EXEC SQL CONNECT TO REGRESSDB1 as main;
-EXEC SQL CONNECT TO AS main USER connectdb;
-EXEC SQL CONNECT TO connectdb AS :id;
-EXEC SQL CONNECT TO connectdb AS main USER connectuser/connectdb;
-EXEC SQL CONNECT TO connectdb AS main;
-EXEC SQL CONNECT TO connectdb@localhost AS main;
-EXEC SQL CONNECT TO tcp:postgresql://localhost/ USER connectdb;
-EXEC SQL CONNECT TO tcp:postgresql://localhost/connectdb USER connectuser IDENTIFIED BY connectpw;
-EXEC SQL CONNECT TO tcp:postgresql://localhost:20/connectdb USER connectuser IDENTIFIED BY connectpw;
-EXEC SQL CONNECT TO unix:postgresql://localhost/ AS main USER connectdb;
-EXEC SQL CONNECT TO unix:postgresql://localhost/connectdb AS main USER connectuser;
-EXEC SQL CONNECT TO unix:postgresql://localhost/connectdb USER connectuser IDENTIFIED BY "connectpw";
-EXEC SQL CONNECT TO unix:postgresql://localhost/connectdb USER connectuser USING "connectpw";
-EXEC SQL CONNECT TO unix:postgresql://localhost/connectdb?connect_timeout=14 USER connectuser;
-</programlisting>
-    </para>
-
-    <para>
-     Here is an example program that illustrates the use of host
-     variables to specify connection parameters:
-<programlisting>
-int
-main(void)
-{
-EXEC SQL BEGIN DECLARE SECTION;
-    char *dbname     = "testdb";    /* database name */
-    char *user       = "testuser";  /* connection user name */
-    char *connection = "tcp:postgresql://localhost:5432/testdb";
-                                    /* connection string */
-    char ver[256];                  /* buffer to store the version string */
-EXEC SQL END DECLARE SECTION;
-
-    ECPGdebug(1, stderr);
-
-    EXEC SQL CONNECT TO :dbname USER :user;
-    EXEC SQL SELECT version() INTO :ver;
-    EXEC SQL DISCONNECT;
-
-    printf("version: %s\n", ver);
-
-    EXEC SQL CONNECT TO :connection USER :user;
-    EXEC SQL SELECT version() INTO :ver;
-    EXEC SQL DISCONNECT;
-
-    printf("version: %s\n", ver);
-
-    return 0;
-}
-</programlisting>
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>CONNECT</command> is specified in the SQL standard, but
-     the format of the connection parameters is
-     implementation-specific.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="ecpg-sql-disconnect"></member>
-     <member><xref linkend="ecpg-sql-set-connection"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-deallocate-descriptor">
-   <refnamediv>
-    <refname>DEALLOCATE DESCRIPTOR</refname>
-    <refpurpose>deallocate an SQL descriptor area</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-DEALLOCATE DESCRIPTOR <replaceable class="PARAMETER">name</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>DEALLOCATE DESCRIPTOR</command> deallocates a named SQL
-     descriptor area.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the descriptor which is going to be deallocated.
-        It is case sensitive.  This can be an SQL identifier or a host
-        variable.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-<programlisting>
-EXEC SQL DEALLOCATE DESCRIPTOR mydesc;
-</programlisting>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>DEALLOCATE DESCRIPTOR</command> is specified in the SQL
-     standard.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="ecpg-sql-allocate-descriptor"></member>
-     <member><xref linkend="ecpg-sql-get-descriptor"></member>
-     <member><xref linkend="ecpg-sql-set-descriptor"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-declare">
-   <refnamediv>
-    <refname>DECLARE</refname>
-    <refpurpose>define a cursor</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-DECLARE <replaceable class="PARAMETER">cursor_name</replaceable> [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ] CURSOR [ { WITH | WITHOUT } HOLD ] FOR <replaceable class="PARAMETER">prepared_name</replaceable>
-DECLARE <replaceable class="PARAMETER">cursor_name</replaceable> [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ] CURSOR [ { WITH | WITHOUT } HOLD ] FOR <replaceable class="PARAMETER">query</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>DECLARE</command> declares a cursor for iterating over
-     the result set of a prepared statement.  This command has
-     slightly different semantics from the direct SQL
-     command <command>DECLARE</command>: Whereas the latter executes a
-     query and prepares the result set for retrieval, this embedded
-     SQL command merely declares a name as a <quote>loop
-     variable</quote> for iterating over the result set of a query;
-     the actual execution happens when the cursor is opened with
-     the <command>OPEN</command> command.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-    <variablelist>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">cursor_name</replaceable></term>
-      <listitem>
-       <para>
-        A cursor name, case sensitive.  This can be an SQL identifier
-        or a host variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">prepared_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of a prepared query, either as an SQL identifier or a
-        host variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">query</replaceable></term>
-      <listitem>
-       <para>
-        A <xref linkend="sql-select"> or
-        <xref linkend="sql-values"> command which will provide the
-        rows to be returned by the cursor.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    <para>
-     For the meaning of the cursor options,
-     see <xref linkend="sql-declare">.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-    <para>
-     Examples declaring a cursor for a query:
-<programlisting>
-EXEC SQL DECLARE C CURSOR FOR SELECT * FROM My_Table;
-EXEC SQL DECLARE C CURSOR FOR SELECT Item1 FROM T;
-EXEC SQL DECLARE cur1 CURSOR FOR SELECT version();
-</programlisting>
-    </para>
-
-    <para>
-     An example declaring a cursor for a prepared statement:
-<programlisting>
-EXEC SQL PREPARE stmt1 AS SELECT version();
-EXEC SQL DECLARE cur1 CURSOR FOR stmt1;
-</programlisting>
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>DECLARE</command> is specified in the SQL standard.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="ecpg-sql-open"></member>
-     <member><xref linkend="sql-close"></member>
-     <member><xref linkend="sql-declare"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-describe">
-   <refnamediv>
-    <refname>DESCRIBE</refname>
-    <refpurpose>obtain information about a prepared statement or result set</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-DESCRIBE [ OUTPUT ] <replaceable class="PARAMETER">prepared_name</replaceable> USING [ SQL ] DESCRIPTOR <replaceable class="PARAMETER">descriptor_name</replaceable>
-DESCRIBE [ OUTPUT ] <replaceable class="PARAMETER">prepared_name</replaceable> INTO [ SQL ] DESCRIPTOR <replaceable class="PARAMETER">descriptor_name</replaceable>
-DESCRIBE [ OUTPUT ] <replaceable class="PARAMETER">prepared_name</replaceable> INTO <replaceable class="PARAMETER">sqlda_name</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>DESCRIBE</command> retrieves metadata information about
-     the result columns contained in a prepared statement, without
-     actually fetching a row.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">prepared_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of a prepared statement.  This can be an SQL
-        identifier or a host variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">descriptor_name</replaceable></term>
-      <listitem>
-       <para>
-        A descriptor name. It is case sensitive.  It can be an SQL
-        identifier or a host variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">sqlda_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of an SQLDA variable.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-<programlisting>
-EXEC SQL ALLOCATE DESCRIPTOR mydesc;
-EXEC SQL PREPARE stmt1 FROM :sql_stmt;
-EXEC SQL DESCRIBE stmt1 INTO SQL DESCRIPTOR mydesc;
-EXEC SQL GET DESCRIPTOR mydesc VALUE 1 :charvar = NAME;
-EXEC SQL DEALLOCATE DESCRIPTOR mydesc;
-</programlisting>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>DESCRIBE</command> is specified in the SQL standard.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="ecpg-sql-allocate-descriptor"></member>
-     <member><xref linkend="ecpg-sql-get-descriptor"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-disconnect">
-   <refnamediv>
-    <refname>DISCONNECT</refname>
-    <refpurpose>terminate a database connection</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-DISCONNECT <replaceable class="PARAMETER">connection_name</replaceable>
-DISCONNECT [ CURRENT ]
-DISCONNECT DEFAULT
-DISCONNECT ALL
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>DISCONNECT</command> closes a connection (or all
-     connections) to the database.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">connection_name</replaceable></term>
-      <listitem>
-       <para>
-        A database connection name established by
-        the <command>CONNECT</command> command.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CURRENT</literal></term>
-      <listitem>
-       <para>
-        Close the <quote>current</quote> connection, which is either
-        the most recently opened connection, or the connection set by
-        the <command>SET CONNECTION</command> command.  This is also
-        the default if no argument is given to
-        the <command>DISCONNECT</command> command.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>DEFAULT</literal></term>
-      <listitem>
-       <para>
-        Close the default connection.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ALL</literal></term>
-      <listitem>
-       <para>
-        Close all open connections.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-<programlisting>
-int
-main(void)
-{
-    EXEC SQL CONNECT TO testdb AS DEFAULT USER testuser;
-    EXEC SQL CONNECT TO testdb AS con1 USER testuser;
-    EXEC SQL CONNECT TO testdb AS con2 USER testuser;
-    EXEC SQL CONNECT TO testdb AS con3 USER testuser;
-
-    EXEC SQL DISCONNECT CURRENT;  /* close con3          */
-    EXEC SQL DISCONNECT DEFAULT;  /* close DEFAULT       */
-    EXEC SQL DISCONNECT ALL;      /* close con2 and con1 */
-
-    return 0;
-}
-</programlisting>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>DISCONNECT</command> is specified in the SQL standard.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="ecpg-sql-connect"></member>
-     <member><xref linkend="ecpg-sql-set-connection"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-execute-immediate">
-   <refnamediv>
-    <refname>EXECUTE IMMEDIATE</refname>
-    <refpurpose>dynamically prepare and execute a statement</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-EXECUTE IMMEDIATE <replaceable class="PARAMETER">string</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>EXECUTE IMMEDIATE</command> immediately prepares and
-     executes a dynamically specified SQL statement, without
-     retrieving result rows.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">string</replaceable></term>
-      <listitem>
-       <para>
-        A literal C string or a host variable containing the SQL
-        statement to be executed.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-    <para>
-     Here is an example that executes an <command>INSERT</command>
-     statement using <command>EXECUTE IMMEDIATE</command> and a host
-     variable named <varname>command</varname>:
-<programlisting>
-sprintf(command, "INSERT INTO test (name, amount, letter) VALUES ('db: ''r1''', 1, 'f')");
-EXEC SQL EXECUTE IMMEDIATE :command;
-</programlisting>
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>EXECUTE IMMEDIATE</command> is specified in the SQL standard.
-    </para>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-get-descriptor">
-   <refnamediv>
-    <refname>GET DESCRIPTOR</refname>
-    <refpurpose>get information from an SQL descriptor area</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-GET DESCRIPTOR <replaceable class="PARAMETER">descriptor_name</replaceable> <replaceable class="PARAMETER">:cvariable</replaceable> = <replaceable class="PARAMETER">descriptor_header_item</replaceable> [, ... ]
-GET DESCRIPTOR <replaceable class="PARAMETER">descriptor_name</replaceable> VALUE <replaceable class="PARAMETER">column_number</replaceable> <replaceable class="PARAMETER">:cvariable</replaceable> = <replaceable class="PARAMETER">descriptor_item</replaceable> [, ... ]
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>GET DESCRIPTOR</command> retrieves information about a
-     query result set from an SQL descriptor area and stores it into
-     host variables.  A descriptor area is typically populated
-     using <command>FETCH</command> or <command>SELECT</command>
-     before using this command to transfer the information into host
-     language variables.
-    </para>
-
-    <para>
-     This command has two forms: The first form retrieves
-     descriptor <quote>header</quote> items, which apply to the result
-     set in its entirety.  One example is the row count.  The second
-     form, which requires the column number as additional parameter,
-     retrieves information about a particular column.  Examples are
-     the column name and the actual column value.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">descriptor_name</replaceable></term>
-      <listitem>
-       <para>
-        A descriptor name.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">descriptor_header_item</replaceable></term>
-      <listitem>
-       <para>
-        A token identifying which header information item to retrieve.
-        Only <literal>COUNT</literal>, to get the number of columns in the
-        result set, is currently supported.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">column_number</replaceable></term>
-      <listitem>
-       <para>
-        The number of the column about which information is to be
-        retrieved.  The count starts at 1.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">descriptor_item</replaceable></term>
-      <listitem>
-       <para>
-        A token identifying which item of information about a column
-        to retrieve.  See <xref linkend="ecpg-named-descriptors"> for
-        a list of supported items.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">cvariable</replaceable></term>
-      <listitem>
-       <para>
-        A host variable that will receive the data retrieved from the
-        descriptor area.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-    <para>
-     An example to retrieve the number of columns in a result set:
-<programlisting>
-EXEC SQL GET DESCRIPTOR d :d_count = COUNT;
-</programlisting>
-    </para>
-
-    <para>
-     An example to retrieve a data length in the first column:
-<programlisting>
-EXEC SQL GET DESCRIPTOR d VALUE 1 :d_returned_octet_length = RETURNED_OCTET_LENGTH;
-</programlisting>
-    </para>
-
-    <para>
-     An example to retrieve the data body of the second column as a
-     string:
-<programlisting>
-EXEC SQL GET DESCRIPTOR d VALUE 2 :d_data = DATA;
-</programlisting>
-    </para>
-
-    <para>
-     Here is an example for a whole procedure of
-     executing <literal>SELECT current_database();</> and showing the number of
-     columns, the column data length, and the column data:
-<programlisting>
-int
-main(void)
-{
-EXEC SQL BEGIN DECLARE SECTION;
-    int  d_count;
-    char d_data[1024];
-    int  d_returned_octet_length;
-EXEC SQL END DECLARE SECTION;
-
-    EXEC SQL CONNECT TO testdb AS con1 USER testuser;
-    EXEC SQL ALLOCATE DESCRIPTOR d;
-
-    /* Declare, open a cursor, and assign a descriptor to the cursor  */
-    EXEC SQL DECLARE cur CURSOR FOR SELECT current_database();
-    EXEC SQL OPEN cur;
-    EXEC SQL FETCH NEXT FROM cur INTO SQL DESCRIPTOR d;
-
-    /* Get a number of total columns */
-    EXEC SQL GET DESCRIPTOR d :d_count = COUNT;
-    printf("d_count                 = %d\n", d_count);
-
-    /* Get length of a returned column */
-    EXEC SQL GET DESCRIPTOR d VALUE 1 :d_returned_octet_length = RETURNED_OCTET_LENGTH;
-    printf("d_returned_octet_length = %d\n", d_returned_octet_length);
-
-    /* Fetch the returned column as a string */
-    EXEC SQL GET DESCRIPTOR d VALUE 1 :d_data = DATA;
-    printf("d_data                  = %s\n", d_data);
-
-    /* Closing */
-    EXEC SQL CLOSE cur;
-    EXEC SQL COMMIT;
-
-    EXEC SQL DEALLOCATE DESCRIPTOR d;
-    EXEC SQL DISCONNECT ALL;
-
-    return 0;
-}
-</programlisting>
-     When the example is executed, the result will look like this:
-<screen>
-d_count                 = 1
-d_returned_octet_length = 6
-d_data                  = testdb
-</screen>
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>GET DESCRIPTOR</command> is specified in the SQL standard.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="ecpg-sql-allocate-descriptor"></member>
-     <member><xref linkend="ecpg-sql-set-descriptor"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-open">
-   <refnamediv>
-    <refname>OPEN</refname>
-    <refpurpose>open a dynamic cursor</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-OPEN <replaceable class="PARAMETER">cursor_name</replaceable>
-OPEN <replaceable class="PARAMETER">cursor_name</replaceable> USING <replaceable class="PARAMETER">value</replaceable> [, ... ]
-OPEN <replaceable class="PARAMETER">cursor_name</replaceable> USING SQL DESCRIPTOR <replaceable class="PARAMETER">descriptor_name</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>OPEN</command> opens a cursor and optionally binds
-     actual values to the placeholders in the cursor's declaration.
-     The cursor must previously have been declared with
-     the <command>DECLARE</command> command.  The execution
-     of <command>OPEN</command> causes the query to start executing on
-     the server.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">cursor_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the cursor to be opened.  This can be an SQL
-        identifier or a host variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">value</replaceable></term>
-      <listitem>
-       <para>
-        A value to be bound to a placeholder in the cursor.  This can
-        be an SQL constant, a host variable, or a host variable with
-        indicator.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">descriptor_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of a descriptor containing values to be bound to the
-        placeholders in the cursor.  This can be an SQL identifier or
-        a host variable.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-<programlisting>
-EXEC SQL OPEN a;
-EXEC SQL OPEN d USING 1, 'test';
-EXEC SQL OPEN c1 USING SQL DESCRIPTOR mydesc;
-EXEC SQL OPEN :curname1;
-</programlisting>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>OPEN</command> is specified in the SQL standard.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="ecpg-sql-declare"></member>
-     <member><xref linkend="sql-close"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-prepare">
-   <refnamediv>
-    <refname>PREPARE</refname>
-    <refpurpose>prepare a statement for execution</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-PREPARE <replaceable class="PARAMETER">name</replaceable> FROM <replaceable class="PARAMETER">string</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>PREPARE</command> prepares a statement dynamically
-     specified as a string for execution.  This is different from the
-     direct SQL statement <xref linkend="sql-prepare">, which can also
-     be used in embedded programs.  The <xref linkend="sql-execute">
-     command is used to execute either kind of prepared statement.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">prepared_name</replaceable></term>
-      <listitem>
-       <para>
-        An identifier for the prepared query.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">string</replaceable></term>
-      <listitem>
-       <para>
-        A literal C string or a host variable containing a preparable
-        statement, one of the SELECT, INSERT, UPDATE, or
-        DELETE.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-<programlisting>
-char *stmt = "SELECT * FROM test1 WHERE a = ? AND b = ?";
-
-EXEC SQL ALLOCATE DESCRIPTOR outdesc;
-EXEC SQL PREPARE foo FROM :stmt;
-
-EXEC SQL EXECUTE foo USING SQL DESCRIPTOR indesc INTO SQL DESCRIPTOR outdesc;
-</programlisting>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>PREPARE</command> is specified in the SQL standard.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="sql-execute"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-set-autocommit">
-   <refnamediv>
-    <refname>SET AUTOCOMMIT</refname>
-    <refpurpose>set the autocommit behavior of the current session</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-SET AUTOCOMMIT { = | TO } { ON | OFF }
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>SET AUTOCOMMIT</command> sets the autocommit behavior of
-     the current database session.  By default, embedded SQL programs
-     are <emphasis>not</emphasis> in autocommit mode,
-     so <command>COMMIT</command> needs to be issued explicitly when
-     desired.  This command can change the session to autocommit mode,
-     where each individual statement is committed implicitly.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>SET AUTOCOMMIT</command> is an extension of PostgreSQL ECPG.
-    </para>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-set-connection">
-   <refnamediv>
-    <refname>SET CONNECTION</refname>
-    <refpurpose>select a database connection</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-SET CONNECTION [ TO | = ] <replaceable class="PARAMETER">connection_name</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>SET CONNECTION</command> sets the <quote>current</quote>
-     database connection, which is the one that all commands use
-     unless overridden.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">connection_name</replaceable></term>
-      <listitem>
-       <para>
-        A database connection name established by
-        the <command>CONNECT</command> command.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>DEFAULT</literal></term>
-      <listitem>
-       <para>
-        Set the connection to the default connection.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-<programlisting>
-EXEC SQL SET CONNECTION TO con2;
-EXEC SQL SET CONNECTION = con1;
-</programlisting>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>SET CONNECTION</command> is specified in the SQL standard.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="ecpg-sql-connect"></member>
-     <member><xref linkend="ecpg-sql-disconnect"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-set-descriptor">
-   <refnamediv>
-    <refname>SET DESCRIPTOR</refname>
-    <refpurpose>set information in an SQL descriptor area</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-SET DESCRIPTOR <replaceable class="PARAMETER">descriptor_name</replaceable> <replaceable class="PARAMETER">descriptor_header_item</replaceable> = <replaceable>value</replaceable> [, ... ]
-SET DESCRIPTOR <replaceable class="PARAMETER">descriptor_name</replaceable> VALUE <replaceable class="PARAMETER">number</replaceable> <replaceable class="PARAMETER">descriptor_item</replaceable> = <replaceable>value</replaceable> [, ...]
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     <command>SET DESCRIPTOR</command> populates an SQL descriptor
-     area with values.  The descriptor area is then typically used to
-     bind parameters in a prepared query execution.
-    </para>
-
-    <para>
-     This command has two forms: The first form applies to the
-     descriptor <quote>header</quote>, which is independent of a
-     particular datum.  The second form assigns values to particular
-     datums, identified by number.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">descriptor_name</replaceable></term>
-      <listitem>
-       <para>
-        A descriptor name.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">descriptor_header_item</replaceable></term>
-      <listitem>
-       <para>
-        A token identifying which header information item to set.
-        Only <literal>COUNT</literal>, to set the number of descriptor
-        items, is currently supported.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">number</replaceable></term>
-      <listitem>
-       <para>
-        The number of the descriptor item to set.  The count starts at
-        1.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">descriptor_item</replaceable></term>
-      <listitem>
-       <para>
-        A token identifying which item of information to set in the
-        descriptor.  See <xref linkend="ecpg-named-descriptors"> for a
-        list of supported items.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">value</replaceable></term>
-      <listitem>
-       <para>
-        A value to store into the descriptor item.  This can be an SQL
-        constant or a host variable.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-<programlisting>
-EXEC SQL SET DESCRIPTOR indesc COUNT = 1;
-EXEC SQL SET DESCRIPTOR indesc VALUE 1 DATA = 2;
-EXEC SQL SET DESCRIPTOR indesc VALUE 1 DATA = :val1;
-EXEC SQL SET DESCRIPTOR indesc VALUE 2 INDICATOR = :val1, DATA = 'some string';
-EXEC SQL SET DESCRIPTOR indesc VALUE 2 INDICATOR = :val2null, DATA = :val2;
-</programlisting>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>SET DESCRIPTOR</command> is specified in the SQL standard.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>See Also</title>
-
-    <simplelist type="inline">
-     <member><xref linkend="ecpg-sql-allocate-descriptor"></member>
-     <member><xref linkend="ecpg-sql-get-descriptor"></member>
-    </simplelist>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-type">
-   <refnamediv>
-    <refname>TYPE</refname>
-    <refpurpose>define a new data type</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-TYPE <replaceable class="PARAMETER">type_name</replaceable> IS <replaceable class="PARAMETER">ctype</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     The <command>TYPE</command> command defines a new C type.  It is
-     equivalent to putting a <literal>typedef</literal> into a declare
-     section.
-    </para>
-
-    <para>
-     This command is only recognized when <command>ecpg</command> is
-     run with the <option>-c</option> option.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">type_name</replaceable></term>
-      <listitem>
-       <para>
-        The name for the new type.  It must be a valid C type name.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">ctype</replaceable></term>
-      <listitem>
-       <para>
-        A C type specification.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-<programlisting>
-EXEC SQL TYPE customer IS
-    struct
-    {
-        varchar name[50];
-        int     phone;
-    };
-
-EXEC SQL TYPE cust_ind IS
-    struct ind
-    {
-        short   name_ind;
-        short   phone_ind;
-    };
-
-EXEC SQL TYPE c IS char reference;
-EXEC SQL TYPE ind IS union { int integer; short smallint; };
-EXEC SQL TYPE intarray IS int[AMOUNT];
-EXEC SQL TYPE str IS varchar[BUFFERSIZ];
-EXEC SQL TYPE string IS char[11];
-</programlisting>
-
-    <para>
-     Here is an example program that uses <command>EXEC SQL
-     TYPE</command>:
-<programlisting>
-EXEC SQL WHENEVER SQLERROR SQLPRINT;
-
-EXEC SQL TYPE tt IS
-    struct
-    {
-        varchar v[256];
-        int     i;
-    };
-
-EXEC SQL TYPE tt_ind IS
-    struct ind {
-        short   v_ind;
-        short   i_ind;
-    };
-
-int
-main(void)
-{
-EXEC SQL BEGIN DECLARE SECTION;
-    tt t;
-    tt_ind t_ind;
-EXEC SQL END DECLARE SECTION;
-
-    EXEC SQL CONNECT TO testdb AS con1;
-
-    EXEC SQL SELECT current_database(), 256 INTO :t:t_ind LIMIT 1;
-
-    printf("t.v = %s\n", t.v.arr);
-    printf("t.i = %d\n", t.i);
-
-    printf("t_ind.v_ind = %d\n", t_ind.v_ind);
-    printf("t_ind.i_ind = %d\n", t_ind.i_ind);
-
-    EXEC SQL DISCONNECT con1;
-
-    return 0;
-}
-</programlisting>
-
-     The output from this program looks like this:
-<screen>
-t.v = testdb
-t.i = 256
-t_ind.v_ind = 0
-t_ind.i_ind = 0
-</screen>
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     The <command>TYPE</command> command is a PostgreSQL extension.
-    </para>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-var">
-   <refnamediv>
-    <refname>VAR</refname>
-    <refpurpose>define a variable</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-VAR <replaceable>varname</replaceable> IS <replaceable>ctype</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     The <command>VAR</command> command defines a host variable.  It
-     is equivalent to an ordinary C variable definition inside a
-     declare section.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">varname</replaceable></term>
-      <listitem>
-       <para>
-        A C variable name.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">ctype</replaceable></term>
-      <listitem>
-       <para>
-        A C type specification.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-<programlisting>
-EXEC SQL VAR vc IS VARCHAR[10];
-EXEC SQL VAR boolvar IS bool;
-</programlisting>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     The <command>VAR</command> command is a PostgreSQL extension.
-    </para>
-   </refsect1>
-  </refentry>
-
-  <refentry id="ecpg-sql-whenever">
-   <refnamediv>
-    <refname>WHENEVER</refname>
-    <refpurpose>specify the action to be taken when an SQL statement causes a specific class condition to be raised</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-WHENEVER { NOT FOUND | SQLERROR | SQLWARNING } <replaceable class="PARAMETER">action</replaceable>
-</synopsis>
-   </refsynopsisdiv>
-
-   <refsect1>
-    <title>Description</title>
-
-    <para>
-     Define a behavior which is called on the special cases (Rows not
-     found, SQL warnings or errors) in the result of SQL execution.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Parameters</title>
-
-    <para>
-     See <xref linkend="ecpg-whenever"> for a description of the
-     parameters.
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Examples</title>
-
-<programlisting>
-EXEC SQL WHENEVER NOT FOUND CONTINUE;
-EXEC SQL WHENEVER NOT FOUND DO BREAK;
-EXEC SQL WHENEVER SQLWARNING SQLPRINT;
-EXEC SQL WHENEVER SQLWARNING DO warn();
-EXEC SQL WHENEVER SQLERROR sqlprint;
-EXEC SQL WHENEVER SQLERROR CALL print2();
-EXEC SQL WHENEVER SQLERROR DO handle_error("select");
-EXEC SQL WHENEVER SQLERROR DO sqlnotice(NULL, NONO);
-EXEC SQL WHENEVER SQLERROR DO sqlprint();
-EXEC SQL WHENEVER SQLERROR GOTO error_label;
-EXEC SQL WHENEVER SQLERROR STOP;
-</programlisting>
-
-    <para>
-     A typical application is the use of <literal>WHENEVER NOT FOUND
-     BREAK</literal> to handle looping through result sets:
-<programlisting>
-int
-main(void)
-{
-    EXEC SQL CONNECT TO testdb AS con1;
-    EXEC SQL ALLOCATE DESCRIPTOR d;
-    EXEC SQL DECLARE cur CURSOR FOR SELECT current_database(), 'hoge', 256;
-    EXEC SQL OPEN cur;
-
-    /* when end of result set reached, break out of while loop */
-    EXEC SQL WHENEVER NOT FOUND DO BREAK;
-
-    while (1)
-    {
-        EXEC SQL FETCH NEXT FROM cur INTO SQL DESCRIPTOR d;
-        ...
-    }
-
-    EXEC SQL CLOSE cur;
-    EXEC SQL COMMIT;
-
-    EXEC SQL DEALLOCATE DESCRIPTOR d;
-    EXEC SQL DISCONNECT ALL;
-
-    return 0;
-}
-</programlisting>
-    </para>
-   </refsect1>
-
-   <refsect1>
-    <title>Compatibility</title>
-
-    <para>
-     <command>WHENEVER</command> is specified in the SQL standard, but
-     most of the actions are PostgreSQL extensions.
-    </para>
-   </refsect1>
-  </refentry>
- </sect1>
-
- <sect1 id="ecpg-informix-compat">
-  <title><productname>Informix</productname> Compatibility Mode</title>
-&common;
-  <para>
-   <command>ecpg</command> can be run in a so-called <firstterm>Informix compatibility mode</>. If
-   this mode is active, it tries to behave as if it were the <productname>Informix</productname>
-   precompiler for <productname>Informix</productname> E/SQL. Generally spoken this will allow you to use
-   the dollar sign instead of the <literal>EXEC SQL</> primitive to introduce
-   embedded SQL commands.:
-<programlisting>
-$int j = 3;
-$CONNECT TO :dbname;
-$CREATE TABLE test(i INT PRIMARY KEY, j INT);
-$INSERT INTO test(i, j) VALUES (7, :j);
-$COMMIT;
-</programlisting>
-  </para>
-
-  <note>
-   <para>
-    There must not be any white space between the <literal>$</literal>
-    and a following preprocessor directive, that is,
-    <literal>include</literal>, <literal>define</literal>, <literal>ifdef</literal>,
-    etc.  Otherwise, the preprocessor will parse the token as a host
-    variable.
-   </para>
-  </note>
-
-  <para>
-   There are two compatibility modes: <literal>INFORMIX</>, <literal>INFORMIX_SE</>
-  </para>
-  <para>
-   When linking programs that use this compatibility mode, remember to link
-   against <literal>libcompat</> that is shipped with ECPG.
-  </para>
-  <para>
-   Besides the previously explained syntactic sugar, the <productname>Informix</productname> compatibility
-   mode ports some functions for input, output and transformation of data as
-   well as embedded SQL statements known from E/SQL to ECPG.
-  </para>
-  <para>
-   <productname>Informix</productname> compatibility mode is closely connected to the pgtypeslib library
-   of ECPG. pgtypeslib maps SQL data types to data types within the C host
-   program and most of the additional functions of the <productname>Informix</productname> compatibility
-   mode allow you to operate on those C host program types. Note however that
-   the extent of the compatibility is limited. It does not try to copy <productname>Informix</productname>
-   behavior; it allows you to do more or less the same operations and gives
-   you functions that have the same name and the same basic behavior but it is
-   no drop-in replacement if you are using <productname>Informix</productname> at the moment. Moreover,
-   some of the data types are different. For example,
-   <productname>PostgreSQL's</productname> datetime and interval types do not
-   know about ranges like for example <literal>YEAR TO MINUTE</> so you won't
-   find support in ECPG for that either.
-  </para>
-
-  <sect2 id="ecpg-informix-types">
-   <title>Additional Types</title>
-&common;
-   <para>
-    The Informix-special "string" pseudo-type for storing right-trimmed character string data is now
-    supported in Informix-mode without using <literal>typedef</literal>. In fact, in Informix-mode,
-    ECPG refuses to process source files that contain <literal>typedef sometype string;</literal>
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-string userid; /* this variable will contain trimmed data */
-EXEC SQL END DECLARE SECTION;
-
-EXEC SQL FETCH MYCUR INTO :userid;
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-informix-statements">
-   <title>Additional/Missing Embedded SQL Statements</title>
-&common;
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><literal>CLOSE DATABASE</></term>
-      <listitem>
-       <para>
-        This statement closes the current connection. In fact, this is a
-        synonym for ECPG's <literal>DISCONNECT CURRENT</>.:
-<programlisting>
-$CLOSE DATABASE;                /* close the current connection */
-EXEC SQL CLOSE DATABASE;
-</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>FREE cursor_name</></term>
-      <listitem>
-       <para>
-        Due to the differences how ECPG works compared to Informix's ESQL/C (i.e. which steps
-        are purely grammar transformations and which steps rely on the underlying run-time library)
-        there is no <literal>FREE cursor_name</> statement in ECPG. This is because in ECPG,
-        <literal>DECLARE CURSOR</literal> doesn't translate to a function call into
-        the run-time library that uses to the cursor name. This means that there's no run-time
-        bookkeeping of SQL cursors in the ECPG run-time library, only in the PostgreSQL server.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>FREE statement_name</></term>
-      <listitem>
-       <para>
-        <literal>FREE statement_name</> is a synonym for <literal>DEALLOCATE PREPARE statement_name</>.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-informix-sqlda">
-   <title>Informix-compatible SQLDA Descriptor Areas</title>
-&common;
-   <para>
-    Informix-compatible mode supports a different structure than the one described in
-    <xref linkend="ecpg-sqlda-descriptors">. See below:
-<programlisting>
-struct sqlvar_compat
-{
-    short   sqltype;
-    int     sqllen;
-    char   *sqldata;
-    short  *sqlind;
-    char   *sqlname;
-    char   *sqlformat;
-    short   sqlitype;
-    short   sqlilen;
-    char   *sqlidata;
-    int     sqlxid;
-    char   *sqltypename;
-    short   sqltypelen;
-    short   sqlownerlen;
-    short   sqlsourcetype;
-    char   *sqlownername;
-    int     sqlsourceid;
-    char   *sqlilongdata;
-    int     sqlflags;
-    void   *sqlreserved;
-};
-
-struct sqlda_compat
-{
-    short  sqld;
-    struct sqlvar_compat *sqlvar;
-    char   desc_name[19];
-    short  desc_occ;
-    struct sqlda_compat *desc_next;
-    void  *reserved;
-};
-
-typedef struct sqlvar_compat    sqlvar_t;
-typedef struct sqlda_compat     sqlda_t;
-</programlisting>
-   </para>
-
-   <para>
-    The global properties are:
-    <variablelist>
-
-     <varlistentry>
-     <term><literal>sqld</></term>
-      <listitem>
-       <para>
-        The number of fields in the <literal>SQLDA</> descriptor.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqlvar</></term>
-      <listitem>
-       <para>
-        Pointer to the per-field properties.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>desc_name</></term>
-      <listitem>
-       <para>
-        Unused, filled with zero-bytes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>desc_occ</></term>
-      <listitem>
-       <para>
-        Size of the allocated structure.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>desc_next</></term>
-      <listitem>
-       <para>
-        Pointer to the next SQLDA structure if the result set contains more than one record.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>reserved</></term>
-      <listitem>
-       <para>
-        Unused pointer, contains NULL. Kept for Informix-compatibility.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-    The per-field properties are below, they are stored in the <literal>sqlvar</literal> array:
-
-    <variablelist>
-
-     <varlistentry>
-     <term><literal>sqltype</></term>
-      <listitem>
-       <para>
-        Type of the field. Constants are in <literal>sqltypes.h</literal>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqllen</></term>
-      <listitem>
-       <para>
-        Length of the field data.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqldata</></term>
-      <listitem>
-       <para>
-        Pointer to the field data. The pointer is of <literal>char *</literal> type,
-        the data pointed by it is in a binary format. Example:
-<programlisting>
-int intval;
-
-switch (sqldata->sqlvar[i].sqltype)
-{
-    case SQLINTEGER:
-        intval = *(int *)sqldata->sqlvar[i].sqldata;
-        break;
-  ...
-}
-</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqlind</></term>
-      <listitem>
-       <para>
-        Pointer to the NULL indicator. If returned by DESCRIBE or FETCH then it's always a valid pointer.
-        If used as input for <literal>EXECUTE ... USING sqlda;</literal> then NULL-pointer value means
-        that the value for this field is non-NULL. Otherwise a valid pointer and <literal>sqlitype</literal>
-        has to be properly set. Example:
-<programlisting>
-if (*(int2 *)sqldata->sqlvar[i].sqlind != 0)
-    printf("value is NULL\n");
-</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqlname</></term>
-      <listitem>
-       <para>
-        Name of the field. 0-terminated string.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqlformat</></term>
-      <listitem>
-       <para>
-        Reserved in Informix, value of <function>PQfformat()</> for the field.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqlitype</></term>
-      <listitem>
-       <para>
-        Type of the NULL indicator data. It's always SQLSMINT when returning data from the server.
-        When the <literal>SQLDA</literal> is used for a parametrized query, the data is treated
-        according to the set type.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqlilen</></term>
-      <listitem>
-       <para>
-        Length of the NULL indicator data.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqlxid</></term>
-      <listitem>
-       <para>
-        Extended type of the field, result of <function>PQftype()</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqltypename</></term>
-     <term><literal>sqltypelen</></term>
-     <term><literal>sqlownerlen</></term>
-     <term><literal>sqlsourcetype</></term>
-     <term><literal>sqlownername</></term>
-     <term><literal>sqlsourceid</></term>
-     <term><literal>sqlflags</></term>
-     <term><literal>sqlreserved</></term>
-      <listitem>
-       <para>
-        Unused.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-     <term><literal>sqlilongdata</></term>
-      <listitem>
-       <para>
-        It equals to <literal>sqldata</literal> if <literal>sqllen</literal> is larger than 32KB.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-    Example:
-<programlisting>
-EXEC SQL INCLUDE sqlda.h;
-
-    sqlda_t        *sqlda; /* This doesn't need to be under embedded DECLARE SECTION */
-
-    EXEC SQL BEGIN DECLARE SECTION;
-    char *prep_stmt = "select * from table1";
-    int i;
-    EXEC SQL END DECLARE SECTION;
-
-    ...
-
-    EXEC SQL PREPARE mystmt FROM :prep_stmt;
-
-    EXEC SQL DESCRIBE mystmt INTO sqlda;
-
-    printf("# of fields: %d\n", sqlda-&gt;sqld);
-    for (i = 0; i &lt; sqlda-&gt;sqld; i++)
-      printf("field %d: \"%s\"\n", sqlda-&gt;sqlvar[i]-&gt;sqlname);
-
-    EXEC SQL DECLARE mycursor CURSOR FOR mystmt;
-    EXEC SQL OPEN mycursor;
-    EXEC SQL WHENEVER NOT FOUND GOTO out;
-
-    while (1)
-    {
-      EXEC SQL FETCH mycursor USING sqlda;
-    }
-
-    EXEC SQL CLOSE mycursor;
-
-    free(sqlda); /* The main structure is all to be free(),
-                  * sqlda and sqlda-&gt;sqlvar is in one allocated area */
-</programlisting>
-    For more information, see the <literal>sqlda.h</> header and the
-    <literal>src/interfaces/ecpg/test/compat_informix/sqlda.pgc</literal> regression test.
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-informix-functions">
-   <title>Additional Functions</title>
-&common;
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><function>decadd</></term>
-      <listitem>
-       <para>
-        Add two decimal type values.
-<synopsis>
-int decadd(decimal *arg1, decimal *arg2, decimal *sum);
-</synopsis>
-        The function receives a pointer to the first operand of type decimal
-        (<literal>arg1</>), a pointer to the second operand of type decimal
-        (<literal>arg2</>) and a pointer to a value of type decimal that will
-        contain the sum (<literal>sum</>). On success, the function returns 0.
-        <symbol>ECPG_INFORMIX_NUM_OVERFLOW</> is returned in case of overflow and
-        <symbol>ECPG_INFORMIX_NUM_UNDERFLOW</> in case of underflow. -1 is returned for
-        other failures and <varname>errno</> is set to the respective <varname>errno</> number of the
-        pgtypeslib.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>deccmp</></term>
-      <listitem>
-       <para>
-        Compare two variables of type decimal.
-<synopsis>
-int deccmp(decimal *arg1, decimal *arg2);
-</synopsis>
-        The function receives a pointer to the first decimal value
-        (<literal>arg1</>), a pointer to the second decimal value
-        (<literal>arg2</>) and returns an integer value that indicates which is
-        the bigger value.
-        <itemizedlist>
-         <listitem>
-          <para>
-           1, if the value that <literal>arg1</> points to is bigger than the
-           value that <literal>var2</> points to
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           -1, if the value that <literal>arg1</> points to is smaller than the
-           value that <literal>arg2</> points to </para>
-         </listitem>
-         <listitem>
-          <para>
-           0, if the value that <literal>arg1</> points to and the value that
-           <literal>arg2</> points to are equal
-          </para>
-         </listitem>
-        </itemizedlist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>deccopy</></term>
-      <listitem>
-       <para>
-        Copy a decimal value.
-<synopsis>
-void deccopy(decimal *src, decimal *target);
-</synopsis>
-        The function receives a pointer to the decimal value that should be
-        copied as the first argument (<literal>src</>) and a pointer to the
-        target structure of type decimal (<literal>target</>) as the second
-        argument.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>deccvasc</></term>
-      <listitem>
-       <para>
-        Convert a value from its ASCII representation into a decimal type.
-<synopsis>
-int deccvasc(char *cp, int len, decimal *np);
-</synopsis>
-        The function receives a pointer to string that contains the string
-        representation of the number to be converted (<literal>cp</>) as well
-        as its length <literal>len</>. <literal>np</> is a pointer to the
-        decimal value that saves the result of the operation.
-       </para>
-       <para>
-        Valid formats are for example:
-         <literal>-2</literal>,
-         <literal>.794</literal>,
-         <literal>+3.44</literal>,
-         <literal>592.49E07</literal> or
-         <literal>-32.84e-4</literal>.
-       </para>
-       <para>
-        The function returns 0 on success. If overflow or underflow occurred,
-        <literal>ECPG_INFORMIX_NUM_OVERFLOW</> or
-        <literal>ECPG_INFORMIX_NUM_UNDERFLOW</> is returned. If the ASCII
-        representation could not be parsed,
-        <literal>ECPG_INFORMIX_BAD_NUMERIC</> is returned or
-        <literal>ECPG_INFORMIX_BAD_EXPONENT</> if this problem occurred while
-        parsing the exponent.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>deccvdbl</></term>
-      <listitem>
-       <para>
-        Convert a value of type double to a value of type decimal.
-<synopsis>
-int deccvdbl(double dbl, decimal *np);
-</synopsis>
-        The function receives the variable of type double that should be
-        converted as its first argument (<literal>dbl</>). As the second
-        argument (<literal>np</>), the function receives a pointer to the
-        decimal variable that should hold the result of the operation.
-       </para>
-       <para>
-        The function returns 0 on success and a negative value if the
-        conversion failed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>deccvint</></term>
-      <listitem>
-       <para>
-        Convert a value of type int to a value of type decimal.
-<synopsis>
-int deccvint(int in, decimal *np);
-</synopsis>
-        The function receives the variable of type int that should be
-        converted as its first argument (<literal>in</>). As the second
-        argument (<literal>np</>), the function receives a pointer to the
-        decimal variable that should hold the result of the operation.
-       </para>
-       <para>
-        The function returns 0 on success and a negative value if the
-        conversion failed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>deccvlong</></term>
-      <listitem>
-       <para>
-        Convert a value of type long to a value of type decimal.
-<synopsis>
-int deccvlong(long lng, decimal *np);
-</synopsis>
-        The function receives the variable of type long that should be
-        converted as its first argument (<literal>lng</>). As the second
-        argument (<literal>np</>), the function receives a pointer to the
-        decimal variable that should hold the result of the operation.
-       </para>
-       <para>
-        The function returns 0 on success and a negative value if the
-        conversion failed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>decdiv</></term>
-      <listitem>
-       <para>
-        Divide two variables of type decimal.
-<synopsis>
-int decdiv(decimal *n1, decimal *n2, decimal *result);
-</synopsis>
-        The function receives pointers to the variables that are the first
-        (<literal>n1</>) and the second (<literal>n2</>) operands and
-        calculates <literal>n1</>/<literal>n2</>. <literal>result</> is a
-        pointer to the variable that should hold the result of the operation.
-       </para>
-       <para>
-        On success, 0 is returned and a negative value if the division fails.
-        If overflow or underflow occurred, the function returns
-        <literal>ECPG_INFORMIX_NUM_OVERFLOW</> or
-        <literal>ECPG_INFORMIX_NUM_UNDERFLOW</> respectively. If an attempt to
-        divide by zero is observed, the function returns
-        <literal>ECPG_INFORMIX_DIVIDE_ZERO</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>decmul</></term>
-      <listitem>
-       <para>
-        Multiply two decimal values.
-<synopsis>
-int decmul(decimal *n1, decimal *n2, decimal *result);
-</synopsis>
-        The function receives pointers to the variables that are the first
-        (<literal>n1</>) and the second (<literal>n2</>) operands and
-        calculates <literal>n1</>*<literal>n2</>. <literal>result</> is a
-        pointer to the variable that should hold the result of the operation.
-       </para>
-       <para>
-        On success, 0 is returned and a negative value if the multiplication
-        fails. If overflow or underflow occurred, the function returns
-        <literal>ECPG_INFORMIX_NUM_OVERFLOW</> or
-        <literal>ECPG_INFORMIX_NUM_UNDERFLOW</> respectively.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>decsub</></term>
-      <listitem>
-       <para>
-        Subtract one decimal value from another.
-<synopsis>
-int decsub(decimal *n1, decimal *n2, decimal *result);
-</synopsis>
-        The function receives pointers to the variables that are the first
-        (<literal>n1</>) and the second (<literal>n2</>) operands and
-        calculates <literal>n1</>-<literal>n2</>. <literal>result</> is a
-        pointer to the variable that should hold the result of the operation.
-       </para>
-       <para>
-        On success, 0 is returned and a negative value if the subtraction
-        fails. If overflow or underflow occurred, the function returns
-        <literal>ECPG_INFORMIX_NUM_OVERFLOW</> or
-        <literal>ECPG_INFORMIX_NUM_UNDERFLOW</> respectively.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>dectoasc</></term>
-      <listitem>
-       <para>
-        Convert a variable of type decimal to its ASCII representation in a C
-        char* string.
-<synopsis>
-int dectoasc(decimal *np, char *cp, int len, int right)
-</synopsis>
-        The function receives a pointer to a variable of type decimal
-        (<literal>np</>) that it converts to its textual representation.
-        <literal>cp</> is the buffer that should hold the result of the
-        operation. The parameter <literal>right</> specifies, how many digits
-        right of the decimal point should be included in the output. The result
-        will be rounded to this number of decimal digits. Setting
-        <literal>right</> to -1 indicates that all available decimal digits
-        should be included in the output. If the length of the output buffer,
-        which is indicated by <literal>len</> is not sufficient to hold the
-        textual representation including the trailing zero byte, only a
-        single <literal>*</> character is stored in the result and -1 is
-        returned.
-       </para>
-       <para>
-        The function returns either -1 if the buffer <literal>cp</> was too
-        small or <literal>ECPG_INFORMIX_OUT_OF_MEMORY</> if memory was
-        exhausted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>dectodbl</></term>
-      <listitem>
-       <para>
-        Convert a variable of type decimal to a double.
-<synopsis>
-int dectodbl(decimal *np, double *dblp);
-</synopsis>
-        The function receives a pointer to the decimal value to convert
-        (<literal>np</>) and a pointer to the double variable that
-        should hold the result of the operation (<literal>dblp</>).
-       </para>
-       <para>
-        On success, 0 is returned and a negative value if the conversion
-        failed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>dectoint</></term>
-      <listitem>
-       <para>
-        Convert a variable to type decimal to an integer.
-<synopsis>
-int dectoint(decimal *np, int *ip);
-</synopsis>
-        The function receives a pointer to the decimal value to convert
-        (<literal>np</>) and a pointer to the integer variable that
-        should hold the result of the operation (<literal>ip</>).
-       </para>
-       <para>
-        On success, 0 is returned and a negative value if the conversion
-        failed. If an overflow occurred, <literal>ECPG_INFORMIX_NUM_OVERFLOW</>
-        is returned.
-       </para>
-       <para>
-        Note that the ECPG implementation differs from the <productname>Informix</productname>
-        implementation. <productname>Informix</productname> limits an integer to the range from -32767 to
-        32767, while the limits in the ECPG implementation depend on the
-        architecture (<literal>-INT_MAX .. INT_MAX</>).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>dectolong</></term>
-      <listitem>
-       <para>
-        Convert a variable to type decimal to a long integer.
-<synopsis>
-int dectolong(decimal *np, long *lngp);
-</synopsis>
-        The function receives a pointer to the decimal value to convert
-        (<literal>np</>) and a pointer to the long variable that
-        should hold the result of the operation (<literal>lngp</>).
-       </para>
-       <para>
-        On success, 0 is returned and a negative value if the conversion
-        failed. If an overflow occurred, <literal>ECPG_INFORMIX_NUM_OVERFLOW</>
-        is returned.
-       </para>
-       <para>
-        Note that the ECPG implementation differs from the <productname>Informix</productname>
-        implementation. <productname>Informix</productname> limits a long integer to the range from
-        -2,147,483,647 to 2,147,483,647, while the limits in the ECPG
-        implementation depend on the architecture (<literal>-LONG_MAX ..
-        LONG_MAX</>).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rdatestr</></term>
-      <listitem>
-       <para>
-        Converts a date to a C char* string.
-<synopsis>
-int rdatestr(date d, char *str);
-</synopsis>
-        The function receives two arguments, the first one is the date to
-        convert (<literal>d</> and the second one is a pointer to the target
-        string. The output format is always <literal>yyyy-mm-dd</>, so you need
-        to allocate at least 11 bytes (including the zero-byte terminator) for the
-        string.
-       </para>
-       <para>
-        The function returns 0 on success and a negative value in case of
-        error.
-       </para>
-       <para>
-        Note that ECPG's implementation differs from the <productname>Informix</productname>
-        implementation. In <productname>Informix</productname> the format can be influenced by setting
-        environment variables. In ECPG however, you cannot change the output
-        format.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rstrdate</></term>
-      <listitem>
-       <para>
-        Parse the textual representation of a date.
-<synopsis>
-int rstrdate(char *str, date *d);
-</synopsis>
-        The function receives the textual representation of the date to convert
-        (<literal>str</>) and a pointer to a variable of type date
-        (<literal>d</>). This function does not allow you to specify a format
-        mask. It uses the default format mask of <productname>Informix</productname> which is
-        <literal>mm/dd/yyyy</>. Internally, this function is implemented by
-        means of <function>rdefmtdate</>. Therefore, <function>rstrdate</> is
-        not faster and if you have the choice you should opt for
-        <function>rdefmtdate</> which allows you to specify the format mask
-        explicitly.
-       </para>
-       <para>
-        The function returns the same values as <function>rdefmtdate</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rtoday</></term>
-      <listitem>
-       <para>
-        Get the current date.
-<synopsis>
-void rtoday(date *d);
-</synopsis>
-        The function receives a pointer to a date variable (<literal>d</>)
-        that it sets to the current date.
-       </para>
-       <para>
-        Internally this function uses the <xref linkend="PGTYPESdatetoday">
-        function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rjulmdy</></term>
-      <listitem>
-       <para>
-        Extract the values for the day, the month and the year from a variable
-        of type date.
-<synopsis>
-int rjulmdy(date d, short mdy[3]);
-</synopsis>
-        The function receives the date <literal>d</> and a pointer to an array
-        of 3 short integer values <literal>mdy</>. The variable name indicates
-        the sequential order: <literal>mdy[0]</> will be set to contain the
-        number of the month, <literal>mdy[1]</> will be set to the value of the
-        day and <literal>mdy[2]</> will contain the year.
-       </para>
-       <para>
-        The function always returns 0 at the moment.
-       </para>
-       <para>
-        Internally the function uses the <xref linkend="PGTYPESdatejulmdy">
-        function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rdefmtdate</></term>
-      <listitem>
-       <para>
-        Use a format mask to convert a character string to a value of type
-        date.
-<synopsis>
-int rdefmtdate(date *d, char *fmt, char *str);
-</synopsis>
-        The function receives a pointer to the date value that should hold the
-        result of the operation (<literal>d</>), the format mask to use for
-        parsing the date (<literal>fmt</>) and the C char* string containing
-        the textual representation of the date (<literal>str</>). The textual
-        representation is expected to match the format mask. However you do not
-        need to have a 1:1 mapping of the string to the format mask. The
-        function only analyzes the sequential order and looks for the literals
-        <literal>yy</literal> or <literal>yyyy</literal> that indicate the
-        position of the year, <literal>mm</literal> to indicate the position of
-        the month and <literal>dd</literal> to indicate the position of the
-        day.
-       </para>
-       <para>
-        The function returns the following values:
-        <itemizedlist>
-         <listitem>
-          <para>
-           0 - The function terminated successfully.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>ECPG_INFORMIX_ENOSHORTDATE</> - The date does not contain
-           delimiters between day, month and year. In this case the input
-           string must be exactly 6 or 8 bytes long but isn't.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>ECPG_INFORMIX_ENOTDMY</> - The format string did not
-           correctly indicate the sequential order of year, month and day.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>ECPG_INFORMIX_BAD_DAY</> - The input string does not
-           contain a valid day.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>ECPG_INFORMIX_BAD_MONTH</> - The input string does not
-           contain a valid month.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>ECPG_INFORMIX_BAD_YEAR</> - The input string does not
-           contain a valid year.
-          </para>
-         </listitem>
-        </itemizedlist>
-       </para>
-       <para>
-        Internally this function is implemented to use the <xref
-        linkend="PGTYPESdatedefmtasc"> function. See the reference there for a
-        table of example input.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rfmtdate</></term>
-      <listitem>
-       <para>
-        Convert a variable of type date to its textual representation using a
-        format mask.
-<synopsis>
-int rfmtdate(date d, char *fmt, char *str);
-</synopsis>
-        The function receives the date to convert (<literal>d</>), the format
-        mask (<literal>fmt</>) and the string that will hold the textual
-        representation of the date (<literal>str</>).
-       </para>
-       <para>
-        On success, 0 is returned and a negative value if an error occurred.
-       </para>
-       <para>
-        Internally this function uses the <xref linkend="PGTYPESdatefmtasc">
-        function, see the reference there for examples.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rmdyjul</></term>
-      <listitem>
-       <para>
-        Create a date value from an array of 3 short integers that specify the
-        day, the month and the year of the date.
-<synopsis>
-int rmdyjul(short mdy[3], date *d);
-</synopsis>
-        The function receives the array of the 3 short integers
-        (<literal>mdy</>) and a pointer to a variable of type date that should
-        hold the result of the operation.
-       </para>
-       <para>
-        Currently the function returns always 0.
-       </para>
-       <para>
-        Internally the function is implemented to use the function <xref
-        linkend="PGTYPESdatemdyjul">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rdayofweek</></term>
-      <listitem>
-       <para>
-        Return a number representing the day of the week for a date value.
-<synopsis>
-int rdayofweek(date d);
-</synopsis>
-        The function receives the date variable <literal>d</> as its only
-        argument and returns an integer that indicates the day of the week for
-        this date.
-        <itemizedlist>
-         <listitem>
-          <para>
-           0 - Sunday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           1 - Monday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           2 - Tuesday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           3 - Wednesday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           4 - Thursday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           5 - Friday
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           6 - Saturday
-          </para>
-         </listitem>
-        </itemizedlist>
-       </para>
-       <para>
-        Internally the function is implemented to use the function <xref
-        linkend="PGTYPESdatedayofweek">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>dtcurrent</></term>
-      <listitem>
-       <para>
-        Retrieve the current timestamp.
-<synopsis>
-void dtcurrent(timestamp *ts);
-</synopsis>
-        The function retrieves the current timestamp and saves it into the
-        timestamp variable that <literal>ts</> points to.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>dtcvasc</></term>
-      <listitem>
-       <para>
-        Parses a timestamp from its textual representation
-        into a timestamp variable.
-<synopsis>
-int dtcvasc(char *str, timestamp *ts);
-</synopsis>
-        The function receives the string to parse (<literal>str</>) and a
-        pointer to the timestamp variable that should hold the result of the
-        operation (<literal>ts</>).
-       </para>
-       <para>
-        The function returns 0 on success and a negative value in case of
-        error.
-       </para>
-       <para>
-        Internally this function uses the <xref
-        linkend="PGTYPEStimestampfromasc"> function. See the reference there
-        for a table with example inputs.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>dtcvfmtasc</></term>
-      <listitem>
-       <para>
-        Parses a timestamp from its textual representation
-        using a format mask into a timestamp variable.
-<synopsis>
-dtcvfmtasc(char *inbuf, char *fmtstr, timestamp *dtvalue)
-</synopsis>
-        The function receives the string to parse (<literal>inbuf</>), the
-        format mask to use (<literal>fmtstr</>) and a pointer to the timestamp
-        variable that should hold the result of the operation
-        (<literal>dtvalue</>).
-       </para>
-       <para>
-        This function is implemented by means of the <xref
-        linkend="PGTYPEStimestampdefmtasc"> function. See the documentation
-        there for a list of format specifiers that can be used.
-       </para>
-       <para>
-        The function returns 0 on success and a negative value in case of
-        error.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>dtsub</></term>
-      <listitem>
-       <para>
-        Subtract one timestamp from another and return a variable of type
-        interval.
-<synopsis>
-int dtsub(timestamp *ts1, timestamp *ts2, interval *iv);
-</synopsis>
-        The function will subtract the timestamp variable that <literal>ts2</>
-        points to from the timestamp variable that <literal>ts1</> points to
-        and will store the result in the interval variable that <literal>iv</>
-        points to.
-       </para>
-       <para>
-        Upon success, the function returns 0 and a negative value if an
-        error occurred.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>dttoasc</></term>
-      <listitem>
-       <para>
-        Convert a timestamp variable to a C char* string.
-<synopsis>
-int dttoasc(timestamp *ts, char *output);
-</synopsis>
-        The function receives a pointer to the timestamp variable to convert
-        (<literal>ts</>) and the string that should hold the result of the
-        operation <literal>output</>). It converts <literal>ts</> to its
-        textual representation according to the SQL standard, which is
-        be <literal>YYYY-MM-DD HH:MM:SS</literal>.
-       </para>
-       <para>
-        Upon success, the function returns 0 and a negative value if an
-        error occurred.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>dttofmtasc</></term>
-      <listitem>
-       <para>
-        Convert a timestamp variable to a C char* using a format mask.
-<synopsis>
-int dttofmtasc(timestamp *ts, char *output, int str_len, char *fmtstr);
-</synopsis>
-        The function receives a pointer to the timestamp to convert as its
-        first argument (<literal>ts</>), a pointer to the output buffer
-        (<literal>output</>), the maximal length that has been allocated for
-        the output buffer (<literal>str_len</literal>) and the format mask to
-        use for the conversion (<literal>fmtstr</literal>).
-       </para>
-       <para>
-        Upon success, the function returns 0 and a negative value if an
-        error occurred.
-       </para>
-       <para>
-        Internally, this function uses the <xref
-        linkend="PGTYPEStimestampfmtasc"> function. See the reference there for
-        information on what format mask specifiers can be used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>intoasc</></term>
-      <listitem>
-       <para>
-        Convert an interval variable to a C char* string.
-<synopsis>
-int intoasc(interval *i, char *str);
-</synopsis>
-        The function receives a pointer to the interval variable to convert
-        (<literal>i</>) and the string that should hold the result of the
-        operation <literal>str</>). It converts <literal>i</> to its
-        textual representation according to the SQL standard, which is
-        be <literal>YYYY-MM-DD HH:MM:SS</literal>.
-       </para>
-       <para>
-        Upon success, the function returns 0 and a negative value if an
-        error occurred.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rfmtlong</></term>
-      <listitem>
-       <para>
-        Convert a long integer value to its textual representation using a
-        format mask.
-<synopsis>
-int rfmtlong(long lng_val, char *fmt, char *outbuf);
-</synopsis>
-        The function receives the long value <literal>lng_val</>, the format
-        mask <literal>fmt</> and a pointer to the output buffer
-        <literal>outbuf</>. It converts the long value according to the format
-        mask to its textual representation.
-       </para>
-       <para>
-        The format mask can be composed of the following format specifying
-        characters:
-        <itemizedlist>
-         <listitem>
-          <para>
-           <literal>*</literal> (asterisk) - if this position would be blank
-           otherwise, fill it with an asterisk.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>&amp;</literal> (ampersand) - if this position would be
-           blank otherwise, fill it with a zero.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>#</literal> - turn leading zeroes into blanks.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>&lt;</literal> - left-justify the number in the string.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>,</literal> (comma) - group numbers of four or more digits
-           into groups of three digits separated by a comma.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>.</literal> (period) - this character separates the
-           whole-number part of the number from the fractional part.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>-</literal> (minus) - the minus sign appears if the number
-           is a negative value.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>+</literal> (plus) - the plus sign appears if the number is
-           a positive value.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>(</literal> - this replaces the minus sign in front of the
-           negative number. The minus sign will not appear.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>)</literal> - this character replaces the minus and is
-           printed behind the negative value.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>$</literal> - the currency symbol.
-          </para>
-         </listitem>
-        </itemizedlist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rupshift</></term>
-      <listitem>
-       <para>
-        Convert a string to upper case.
-<synopsis>
-void rupshift(char *str);
-</synopsis>
-        The function receives a pointer to the string and transforms every
-        lower case character to upper case.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>byleng</></term>
-      <listitem>
-       <para>
-        Return the number of characters in a string without counting trailing
-        blanks.
-<synopsis>
-int byleng(char *str, int len);
-</synopsis>
-        The function expects a fixed-length string as its first argument
-        (<literal>str</>) and its length as its second argument
-        (<literal>len</>). It returns the number of significant characters,
-        that is the length of the string without trailing blanks.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>ldchar</></term>
-      <listitem>
-       <para>
-        Copy a fixed-length string into a null-terminated string.
-<synopsis>
-void ldchar(char *src, int len, char *dest);
-</synopsis>
-        The function receives the fixed-length string to copy
-        (<literal>src</>), its length (<literal>len</>) and a pointer to the
-        destination memory (<literal>dest</>). Note that you need to reserve at
-        least <literal>len+1</> bytes for the string that <literal>dest</>
-        points to. The function copies at most <literal>len</> bytes to the new
-        location (less if the source string has trailing blanks) and adds the
-        null-terminator.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rgetmsg</></term>
-      <listitem>
-       <para>
-<synopsis>
-int rgetmsg(int msgnum, char *s, int maxsize);
-</synopsis>
-        This function exists but is not implemented at the moment!
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rtypalign</></term>
-      <listitem>
-       <para>
-<synopsis>
-int rtypalign(int offset, int type);
-</synopsis>
-        This function exists but is not implemented at the moment!
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rtypmsize</></term>
-      <listitem>
-       <para>
-<synopsis>
-int rtypmsize(int type, int len);
-</synopsis>
-        This function exists but is not implemented at the moment!
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>rtypwidth</></term>
-      <listitem>
-       <para>
-<synopsis>
-int rtypwidth(int sqltype, int sqllen);
-</synopsis>
-        This function exists but is not implemented at the moment!
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="rsetnull">
-      <term><function>rsetnull</></term>
-      <listitem>
-       <para>
-        Set a variable to NULL.
-<synopsis>
-int rsetnull(int t, char *ptr);
-</synopsis>
-        The function receives an integer that indicates the type of the
-        variable and a pointer to the variable itself that is casted to a C
-        char* pointer.
-       </para>
-       <para>
-        The following types exist:
-        <itemizedlist>
-         <listitem>
-          <para>
-           <literal>CCHARTYPE</literal> - For a variable of type <type>char</type> or <type>char*</type>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>CSHORTTYPE</literal> - For a variable of type <type>short int</type>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>CINTTYPE</literal> - For a variable of type <type>int</type>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>CBOOLTYPE</literal> - For a variable of type <type>boolean</type>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>CFLOATTYPE</literal> - For a variable of type <type>float</type>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>CLONGTYPE</literal> - For a variable of type <type>long</type>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>CDOUBLETYPE</literal> - For a variable of type <type>double</type>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>CDECIMALTYPE</literal> - For a variable of type <type>decimal</type>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>CDATETYPE</literal> - For a variable of type <type>date</type>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <literal>CDTIMETYPE</literal> - For a variable of type <type>timestamp</type>
-          </para>
-         </listitem>
-        </itemizedlist>
-       </para>
-
-       <para>
-        Here is an example of a call to this function:
-<programlisting><![CDATA[
-$char c[] = "abc       ";
-$short s = 17;
-$int i = -74874;
-
-rsetnull(CCHARTYPE, (char *) c);
-rsetnull(CSHORTTYPE, (char *) &s);
-rsetnull(CINTTYPE, (char *) &i);
-]]>
-</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>risnull</></term>
-      <listitem>
-       <para>
-        Test if a variable is NULL.
-<synopsis>
-int risnull(int t, char *ptr);
-</synopsis>
-        The function receives the type of the variable to test (<literal>t</>)
-        as well a pointer to this variable (<literal>ptr</>). Note that the
-        latter needs to be casted to a char*. See the function <xref
-        linkend="rsetnull"> for a list of possible variable types.
-       </para>
-       <para>
-        Here is an example of how to use this function:
-<programlisting><![CDATA[
-$char c[] = "abc       ";
-$short s = 17;
-$int i = -74874;
-
-risnull(CCHARTYPE, (char *) c);
-risnull(CSHORTTYPE, (char *) &s);
-risnull(CINTTYPE, (char *) &i);
-]]>
-</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="ecpg-informix-constants">
-   <title>Additional Constants</title>
-&common;
-   <para>
-    Note that all constants here describe errors and all of them are defined
-    to represent negative values. In the descriptions of the different
-    constants you can also find the value that the constants represent in the
-    current implementation. However you should not rely on this number. You can
-    however rely on the fact all of them are defined to represent negative
-    values.
-    <variablelist>
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_NUM_OVERFLOW</></term>
-      <listitem>
-       <para>
-        Functions return this value if an overflow occurred in a
-        calculation. Internally it is defined as -1200 (the <productname>Informix</productname>
-        definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_NUM_UNDERFLOW</></term>
-      <listitem>
-       <para>
-        Functions return this value if an underflow occurred in a calculation.
-        Internally it is defined as -1201 (the <productname>Informix</productname> definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_DIVIDE_ZERO</></term>
-      <listitem>
-       <para>
-        Functions return this value if an attempt to divide by zero is
-        observed. Internally it is defined as -1202 (the <productname>Informix</productname> definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_BAD_YEAR</></term>
-      <listitem>
-       <para>
-        Functions return this value if a bad value for a year was found while
-        parsing a date. Internally it is defined as -1204 (the <productname>Informix</productname>
-        definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_BAD_MONTH</></term>
-      <listitem>
-       <para>
-        Functions return this value if a bad value for a month was found while
-        parsing a date. Internally it is defined as -1205 (the <productname>Informix</productname>
-        definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_BAD_DAY</></term>
-      <listitem>
-       <para>
-        Functions return this value if a bad value for a day was found while
-        parsing a date. Internally it is defined as -1206 (the <productname>Informix</productname>
-        definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_ENOSHORTDATE</></term>
-      <listitem>
-       <para>
-        Functions return this value if a parsing routine needs a short date
-        representation but did not get the date string in the right length.
-        Internally it is defined as -1209 (the <productname>Informix</productname> definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_DATE_CONVERT</></term>
-      <listitem>
-       <para>
-        Functions return this value if an error occurred during date
-        formatting.  Internally it is defined as -1210 (the
-        <productname>Informix</productname> definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_OUT_OF_MEMORY</></term>
-      <listitem>
-       <para>
-        Functions return this value if memory was exhausted during
-        their operation.  Internally it is defined as -1211 (the
-        <productname>Informix</productname> definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_ENOTDMY</></term>
-      <listitem>
-       <para>
-        Functions return this value if a parsing routine was supposed to get a
-        format mask (like <literal>mmddyy</>) but not all fields were listed
-        correctly. Internally it is defined as -1212 (the <productname>Informix</productname> definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_BAD_NUMERIC</></term>
-      <listitem>
-       <para>
-        Functions return this value either if a parsing routine cannot parse
-        the textual representation for a numeric value because it contains
-        errors or if a routine cannot complete a calculation involving numeric
-        variables because at least one of the numeric variables is invalid.
-        Internally it is defined as -1213 (the <productname>Informix</productname> definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_BAD_EXPONENT</></term>
-      <listitem>
-       <para>
-        Functions return this value if a parsing routine cannot parse
-        an exponent.  Internally it is defined as -1216 (the
-        <productname>Informix</productname> definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_BAD_DATE</></term>
-      <listitem>
-       <para>
-        Functions return this value if a parsing routine cannot parse
-        a date.  Internally it is defined as -1218 (the
-        <productname>Informix</productname> definition).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ECPG_INFORMIX_EXTRA_CHARS</></term>
-      <listitem>
-       <para>
-        Functions return this value if a parsing routine is passed extra
-        characters is cannot parse.  Internally it is defined as -1264 (the
-        <productname>Informix</productname> definition).
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="ecpg-develop">
-  <title>Internals</title>
-
-&common;
-  <para>
-   This section explains how <application>ECPG</application> works
-   internally. This information can occasionally be useful to help
-   users understand how to use <application>ECPG</application>.
-  </para>
-
-   <para>
-    The first four lines written by <command>ecpg</command> to the
-    output are fixed lines.  Two are comments and two are include
-    lines necessary to interface to the library.  Then the
-    preprocessor reads through the file and writes output.  Normally
-    it just echoes everything to the output.
-   </para>
-
-   <para>
-    When it sees an <command>EXEC SQL</command> statement, it
-    intervenes and changes it. The command starts with <command>EXEC
-    SQL</command> and ends with <command>;</command>. Everything in
-    between is treated as an <acronym>SQL</acronym> statement and
-    parsed for variable substitution.
-   </para>
-
-   <para>
-    Variable substitution occurs when a symbol starts with a colon
-    (<literal>:</literal>). The variable with that name is looked up
-    among the variables that were previously declared within a
-    <literal>EXEC SQL DECLARE</> section.
-   </para>
-
-   <para>
-    The most important function in the library is
-    <function>ECPGdo</function>, which takes care of executing most
-    commands. It takes a variable number of arguments. This can easily
-    add up to 50 or so arguments, and we hope this will not be a
-    problem on any platform.
-   </para>
-
-   <para>
-    The arguments are:
-
-    <variablelist>
-     <varlistentry>
-      <term>A line number</term>
-      <listitem>
-       <para>
-        This is the line number of the original line; used in error
-        messages only.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>A string</term>
-      <listitem>
-       <para>
-        This is the <acronym>SQL</acronym> command that is to be issued.
-        It is modified by the input variables, i.e., the variables that
-        where not known at compile time but are to be entered in the
-        command. Where the variables should go the string contains
-        <literal>?</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Input variables</term>
-      <listitem>
-       <para>
-        Every input variable causes ten arguments to be created.  (See below.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><parameter>ECPGt_EOIT</></term>
-      <listitem>
-       <para>
-        An <type>enum</> telling that there are no more input
-        variables.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Output variables</term>
-      <listitem>
-       <para>
-        Every output variable causes ten arguments to be created.
-        (See below.)  These variables are filled by the function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-      <varlistentry>
-       <term><parameter>ECPGt_EORT</></term>
-       <listitem>
-       <para>
-        An <type>enum</> telling that there are no more variables.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    For every variable that is part of the <acronym>SQL</acronym>
-    command, the function gets ten arguments:
-
-    <orderedlist>
-     <listitem>
-      <para>
-       The type as a special symbol.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       A pointer to the value or a pointer to the pointer.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The size of the variable if it is a <type>char</type> or <type>varchar</type>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The number of elements in the array (for array fetches).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The offset to the next element in the array (for array fetches).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The type of the indicator variable as a special symbol.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       A pointer to the indicator variable.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       0
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The number of elements in the indicator array (for array fetches).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The offset to the next element in the indicator array (for
-       array fetches).
-      </para>
-     </listitem>
-    </orderedlist>
-   </para>
-
-   <para>
-    Note that not all SQL commands are treated in this way.  For
-    instance, an open cursor statement like:
-<programlisting>
-EXEC SQL OPEN <replaceable>cursor</replaceable>;
-</programlisting>
-    is not copied to the output. Instead, the cursor's
-    <command>DECLARE</> command is used at the position of the <command>OPEN</> command
-    because it indeed opens the cursor.
-   </para>
-
-   <para>
-    Here is a complete example describing the output of the
-    preprocessor of a file <filename>foo.pgc</filename> (details might
-    change with each particular version of the preprocessor):
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-int index;
-int result;
-EXEC SQL END DECLARE SECTION;
-...
-EXEC SQL SELECT res INTO :result FROM mytable WHERE index = :index;
-</programlisting>
-    is translated into:
-<programlisting><![CDATA[
-/* Processed by ecpg (2.6.0) */
-/* These two include files are added by the preprocessor */
-#include <ecpgtype.h>;
-#include <ecpglib.h>;
-
-/* exec sql begin declare section */
-
-#line 1 "foo.pgc"
-
- int index;
- int result;
-/* exec sql end declare section */
-...
-ECPGdo(__LINE__, NULL, "SELECT res FROM mytable WHERE index = ?     ",
-        ECPGt_int,&(index),1L,1L,sizeof(int),
-        ECPGt_NO_INDICATOR, NULL , 0L, 0L, 0L, ECPGt_EOIT,
-        ECPGt_int,&(result),1L,1L,sizeof(int),
-        ECPGt_NO_INDICATOR, NULL , 0L, 0L, 0L, ECPGt_EORT);
-#line 147 "foo.pgc"
-]]>
-</programlisting>
-    (The indentation here is added for readability and not
-    something the preprocessor does.)
-   </para>
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/errcodes.sgmlin b/doc-xc/src/sgml/errcodes.sgmlin
deleted file mode 100644
index 08a24dd7bd..0000000000
--- a/doc-xc/src/sgml/errcodes.sgmlin
+++ /dev/null
@@ -1,79 +0,0 @@
-<!-- doc/src/sgml/errcodes.sgml -->
-
-<appendix id="errcodes-appendix">
- <title><productname>PostgreSQL</productname> Error Codes</title>
-
- <indexterm zone="errcodes-appendix">
-  <primary>error codes</primary>
-  <secondary>list of</secondary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  All messages emitted by the <productname>PostgreSQL</productname>
-  server are assigned five-character error codes that follow the SQL
-  standard's conventions for <quote>SQLSTATE</> codes.  Applications
-  that need to know which error condition has occurred should usually
-  test the error code, rather than looking at the textual error
-  message.  The error codes are less likely to change across
-  <productname>PostgreSQL</> releases, and also are not subject to
-  change due to localization of error messages. Note that some, but
-  not all, of the error codes produced by <productname>PostgreSQL</>
-  are defined by the SQL standard; some additional error codes for
-  conditions not defined by the standard have been invented or
-  borrowed from other databases.
- </para>
-
- <para>
-  According to the standard, the first two characters of an error code
-  denote a class of errors, while the last three characters indicate
-  a specific condition within that class.  Thus, an application that
-  does not recognize the specific error code can still be able to infer
-  what to do from the error class.
- </para>
-
- <para>
-  <xref linkend="errcodes-table"> lists all the error codes defined in
-  <productname>PostgreSQL</productname> &version;.  (Some are not actually
-  used at present, but are defined by the SQL standard.)
-  The error classes are also shown.  For each error class there is a
-  <quote>standard</> error code having the last three characters
-  <literal>000</>.  This code is used only for error conditions that fall
-  within the class but do not have any more-specific code assigned.
- </para>
-
- <para>
-  The symbol shown in the column <quote>Condition Name</quote> is also
-  the condition name to use in <application>PL/pgSQL</>.  Condition
-  names can be written in either upper or lower case.  (Note that
-  <application>PL/pgSQL</> does not recognize warning, as opposed to error,
-  condition names; those are classes 00, 01, and 02.)
- </para>
-
-
-<table id="errcodes-table">
- <title><productname>PostgreSQL</productname> Error Codes</title>
-
- <tgroup cols="2">
-  <colspec colnum="1" colname="errorcode">
-  <colspec colnum="2" colname="condname">
-  <spanspec namest="errorcode" nameend="condname" spanname="span12">
-
-  <thead>
-   <row>
-    <entry>Error Code</entry>
-    <entry>Condition Name</entry>
-   </row>
-  </thead>
-
-  <tbody>
-
-    &errcodes-table;
-
-  </tbody>
- </tgroup>
-</table>
-
-
-</appendix>
diff --git a/doc-xc/src/sgml/extend.sgmlin b/doc-xc/src/sgml/extend.sgmlin
deleted file mode 100644
index 8c0e6876ce..0000000000
--- a/doc-xc/src/sgml/extend.sgmlin
+++ /dev/null
@@ -1,1265 +0,0 @@
-<!-- doc/src/sgml/extend.sgml -->
-
- <chapter id="extend">
-  <title>Extending <acronym>SQL</acronym></title>
-
-  <indexterm zone="extend">
-   <primary>extending SQL</primary>
-  </indexterm>
-
-&common;
-  <para>
-   In  the  sections  that follow, we will discuss how you
-<!## PG>
-   can extend the <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   can extend the <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   can extend the <productname>Postgres-XL</productname>
-<!## end>
-   <acronym>SQL</acronym> query language by adding:
-
-   <itemizedlist spacing="compact" mark="bullet">
-    <listitem>
-     <para>
-      functions (starting in <xref linkend="xfunc">)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      aggregates (starting in <xref linkend="xaggr">)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      data types (starting in <xref linkend="xtypes">)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      operators (starting in <xref linkend="xoper">)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      operator classes for indexes (starting in <xref linkend="xindex">)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      packages of related objects (starting in <xref linkend="extend-extensions">)
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <sect1 id="extend-how">
-   <title>How Extensibility Works</title>
-
-&common;
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> is extensible because its operation  is
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> is extensible because its operation  is
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> is extensible because its operation  is
-<!## end>
-    catalog-driven.   If  you  are familiar with standard
-    relational database systems, you know that  they  store  information
-    about  databases,  tables,  columns,  etc., in what are
-    commonly known as system catalogs.  (Some systems  call
-    this  the data dictionary.)  The catalogs appear to the
-    user as tables like any other, but  the  <acronym>DBMS</acronym>  stores
-    its  internal  bookkeeping in them.  One key difference
-<!## PG>
-    between <productname>PostgreSQL</productname> and  standard  relational database systems  is
-    that <productname>PostgreSQL</productname> stores much more information in its
-<!## end>
-<!## XC>
-    between <productname>Postgres-XC</productname> and  standard  relational database systems  is
-    that <productname>Postgres-XC</productname> stores much more information in its
-<!## end>
-<!## XL>
-    between <productname>Postgres-XL</productname> and  standard  relational database systems  is
-    that <productname>Postgres-XL</productname> stores much more information in its
-<!## end>
-    catalogs: not only information about tables and  columns,
-    but also information about data types, functions, access
-    methods, and so on.  These tables can be  modified  by
-<!## PG>
-    the  user, and since <productname>PostgreSQL</productname> bases its operation
-    on these tables, this means that <productname>PostgreSQL</productname> can  be
-<!## end>
-<!## XC>
-    the  user, and since <productname>Postgres-XC</productname> bases its operation
-    on these tables, this means that <productname>Postgres-XC</productname> can  be
-<!## end>
-<!## XL>
-    the  user, and since <productname>Postgres-XL</productname> bases its operation
-    on these tables, this means that <productname>Postgres-XL</productname> can  be
-<!## end>
-    extended   by   users.    By  comparison,  conventional
-    database systems can only be extended by changing hardcoded
-    procedures in the source code or by loading modules
-    specially written by the <acronym>DBMS</acronym> vendor.
-   </para>
-
-<!## XC>
-   <para>
-    <productname>Postgres-XC</> inherits all of this feature
-    from <productname>PostgreSQL</>.
-   </para>
-<!## end>
-<!## XL>
-   <para>
-    <productname>Postgres-XL</> inherits all of this feature
-    from <productname>PostgreSQL</>.
-   </para>
-<!## end>
-
-   <para>
-<!## PG>
-    The <productname>PostgreSQL</productname> server can moreover
-    incorporate user-written code into itself through dynamic loading.
-    That is, the user can specify an object code file (e.g., a shared
-    library) that implements a new type or function, and
-    <productname>PostgreSQL</productname> will load it as required.
-    Code written in <acronym>SQL</acronym> is even more trivial to add
-    to the server.  This ability to modify its operation <quote>on the
-    fly</quote> makes <productname>PostgreSQL</productname> uniquely
-    suited for rapid prototyping of new applications and storage
-    structures.
-<!## end>
-<!## XC>
-    The <productname>Postgres-XC</productname> server can moreover
-    incorporate user-written code into itself through dynamic loading.
-    That is, the user can specify an object code file (e.g., a shared
-    library) that implements a new type or function, and
-    <productname>Postgres-XC</productname> will load it as required.
-    Code written in <acronym>SQL</acronym> is even more trivial to add
-    to the server.  This ability to modify its operation <quote>on the
-    fly</quote> makes <productname>Postgres-XC</productname> uniquely
-    suited for rapid prototyping of new applications and storage
-    structures.
-<!## end>
-<!## XL>
-    The <productname>Postgres-XL</productname> server can moreover
-    incorporate user-written code into itself through dynamic loading.
-    That is, the user can specify an object code file (e.g., a shared
-    library) that implements a new type or function, and
-    <productname>Postgres-XL</productname> will load it as required.
-    Code written in <acronym>SQL</acronym> is even more trivial to add
-    to the server.  This ability to modify its operation <quote>on the
-    fly</quote> makes <productname>Postgres-XL</productname> uniquely
-    suited for rapid prototyping of new applications and storage
-    structures.
-<!## end>
-   </para>
-  </sect1>
-
-  <sect1 id="extend-type-system">
-<!## PG>
-   <title>The <productname>PostgreSQL</productname> Type System</title>
-<!## end>
-<!## XC>
-   <title>The <productname>Postgres-XC</productname> Type System</title>
-<!## end>
-<!## XL>
-   <title>The <productname>Postgres-XL</productname> Type System</title>
-<!## end>
-
-   <indexterm zone="extend-type-system">
-    <primary>base type</primary>
-   </indexterm>
-
-   <indexterm zone="extend-type-system">
-    <primary>data type</primary>
-    <secondary>base</secondary>
-   </indexterm>
-
-   <indexterm zone="extend-type-system">
-    <primary>composite type</primary>
-   </indexterm>
-
-   <indexterm zone="extend-type-system">
-    <primary>data type</primary>
-    <secondary>composite</secondary>
-   </indexterm>
-
-&common;
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> data types are divided into base
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</>'s, and <productname>PostgreSQL</productname>'s as well, data types are divided into base
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</>'s, and <productname>PostgreSQL</productname>'s as well, data types are divided into base
-<!## end>
-    types, composite types, domains, and pseudo-types.
-   </para>
-
-   <sect2>
-    <title>Base Types</title>
-
-&common;
-    <para>
-     Base types are those, like <type>int4</type>, that are
-     implemented below the level of the <acronym>SQL</> language
-     (typically in a low-level language such as C).  They generally
-     correspond to what are often known as abstract data types.
-<!## PG>
-     <productname>PostgreSQL</productname> can only operate on such
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> can only operate on such
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> can only operate on such
-<!## end>
-     types through functions provided by the user and only understands
-     the behavior of such types to the extent that the user describes
-     them.  Base types are further subdivided into scalar and array
-     types.  For each scalar type, a corresponding array type is
-     automatically created that can hold variable-size arrays of that
-     scalar type.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Composite Types</title>
-
-&common;
-    <para>
-     Composite types, or row types, are created whenever the user
-     creates a table. It is also possible to use <xref
-     linkend="sql-createtype"> to
-     define a <quote>stand-alone</> composite type with no associated
-     table.  A composite type is simply a list of types with
-     associated field names.  A value of a composite type is a row or
-     record of field values.  The user can access the component fields
-     from <acronym>SQL</> queries. Refer to <xref linkend="rowtypes">
-     for more information on composite types.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Domains</title>
-
-&common;
-    <para>
-     A domain is based on a particular base type and for many purposes
-     is interchangeable with its base type.  However, a domain can
-     have constraints that restrict its valid values to a subset of
-     what the underlying base type would allow.
-    </para>
-
-    <para>
-     Domains can be created using the <acronym>SQL</> command
-     <xref linkend="sql-createdomain">.
-     Their creation and use is not discussed in this chapter.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Pseudo-Types</title>
-
-&common;
-    <para>
-     There are a few <quote>pseudo-types</> for special purposes.
-     Pseudo-types cannot appear as columns of tables or attributes of
-     composite types, but they can be used to declare the argument and
-     result types of functions.  This provides a mechanism within the
-     type system to identify special classes of functions.  <xref
-     linkend="datatype-pseudotypes-table"> lists the existing
-     pseudo-types.
-    </para>
-   </sect2>
-
-   <sect2 id="extend-types-polymorphic">
-    <title>Polymorphic Types</title>
-
-   <indexterm zone="extend-types-polymorphic">
-    <primary>polymorphic type</primary>
-   </indexterm>
-
-   <indexterm zone="extend-types-polymorphic">
-    <primary>polymorphic function</primary>
-   </indexterm>
-
-   <indexterm zone="extend-types-polymorphic">
-    <primary>type</primary>
-    <secondary>polymorphic</secondary>
-   </indexterm>
-
-   <indexterm zone="extend-types-polymorphic">
-    <primary>function</primary>
-    <secondary>polymorphic</secondary>
-   </indexterm>
-
-&common;
-    <para>
-     Four pseudo-types of special interest are <type>anyelement</>,
-     <type>anyarray</>, <type>anynonarray</>, and <type>anyenum</>,
-     which are collectively called <firstterm>polymorphic types</>.
-     Any function declared using these types is said to be
-     a <firstterm>polymorphic function</>.  A polymorphic function can
-     operate on many different data types, with the specific data type(s)
-     being determined by the data types actually passed to it in a particular
-     call.
-    </para>
-
-    <para>
-     Polymorphic arguments and results are tied to each other and are resolved
-     to a specific data type when a query calling a polymorphic function is
-     parsed.  Each position (either argument or return value) declared as
-     <type>anyelement</type> is allowed to have any specific actual
-     data type, but in any given call they must all be the
-     <emphasis>same</emphasis> actual type. Each
-     position declared as <type>anyarray</type> can have any array data type,
-     but similarly they must all be the same type. If there are
-     positions declared <type>anyarray</type> and others declared
-     <type>anyelement</type>, the actual array type in the
-     <type>anyarray</type> positions must be an array whose elements are
-     the same type appearing in the <type>anyelement</type> positions.
-     <type>anynonarray</> is treated exactly the same as <type>anyelement</>,
-     but adds the additional constraint that the actual type must not be
-     an array type.
-     <type>anyenum</> is treated exactly the same as <type>anyelement</>,
-     but adds the additional constraint that the actual type must
-     be an enum type.
-    </para>
-
-    <para>
-     Thus, when more than one argument position is declared with a polymorphic
-     type, the net effect is that only certain combinations of actual argument
-     types are allowed.  For example, a function declared as
-     <literal>equal(anyelement, anyelement)</> will take any two input values,
-     so long as they are of the same data type.
-    </para>
-
-    <para>
-     When the return value of a function is declared as a polymorphic type,
-     there must be at least one argument position that is also polymorphic,
-     and the actual data type supplied as the argument determines the actual
-     result type for that call.  For example, if there were not already
-     an array subscripting mechanism, one could define a function that
-     implements subscripting as <literal>subscript(anyarray, integer)
-     returns anyelement</>.  This declaration constrains the actual first
-     argument to be an array type, and allows the parser to infer the correct
-     result type from the actual first argument's type.  Another example
-     is that a function declared as <literal>f(anyarray) returns anyenum</>
-     will only accept arrays of enum types.
-    </para>
-
-    <para>
-     Note that <type>anynonarray</> and <type>anyenum</> do not represent
-     separate type variables; they are the same type as
-     <type>anyelement</type>, just with an additional constraint.  For
-     example, declaring a function as <literal>f(anyelement, anyenum)</>
-     is equivalent to declaring it as <literal>f(anyenum, anyenum)</>:
-     both actual arguments have to be the same enum type.
-    </para>
-
-    <para>
-     A variadic function (one taking a variable number of arguments, as in
-     <xref linkend="xfunc-sql-variadic-functions">) can be
-     polymorphic: this is accomplished by declaring its last parameter as
-     <literal>VARIADIC</> <type>anyarray</>.  For purposes of argument
-     matching and determining the actual result type, such a function behaves
-     the same as if you had written the appropriate number of
-     <type>anynonarray</> parameters.
-    </para>
-   </sect2>
-  </sect1>
-
-  &xfunc;
-  &xaggr;
-  &xtypes;
-  &xoper;
-  &xindex;
-
-
-  <sect1 id="extend-extensions">
-   <title>Packaging Related Objects into an Extension</title>
-
-   <indexterm zone="extend-extensions">
-    <primary>extension</primary>
-   </indexterm>
-
-   <para>
-    A useful extension to <productname>PostgreSQL</> typically includes
-    multiple SQL objects; for example, a new data type will require new
-    functions, new operators, and probably new index operator classes.
-    It is helpful to collect all these objects into a single package
-    to simplify database management.  <productname>PostgreSQL</> calls
-    such a package an <firstterm>extension</>.  To define an extension,
-    you need at least a <firstterm>script file</> that contains the
-    <acronym>SQL</> commands to create the extension's objects, and a
-    <firstterm>control file</> that specifies a few basic properties
-    of the extension itself.  If the extension includes C code, there
-    will typically also be a shared library file into which the C code
-    has been built.  Once you have these files, a simple
-    <xref linkend="sql-createextension"> command loads the objects into
-    your database.
-   </para>
-
-   <para>
-    The main advantage of using an extension, rather than just running the
-    <acronym>SQL</> script to load a bunch of <quote>loose</> objects
-    into your database, is that <productname>PostgreSQL</> will then
-    understand that the objects of the extension go together.  You can
-    drop all the objects with a single <xref linkend="sql-dropextension">
-    command (no need to maintain a separate <quote>uninstall</> script).
-    Even more useful, <application>pg_dump</> knows that it should not
-    dump the individual member objects of the extension &mdash; it will
-    just include a <command>CREATE EXTENSION</> command in dumps, instead.
-    This vastly simplifies migration to a new version of the extension
-    that might contain more or different objects than the old version.
-    Note however that you must have the extension's control, script, and
-    other files available when loading such a dump into a new database.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</> will not let you drop an individual object
-    contained in an extension, except by dropping the whole extension.
-    Also, while you can change the definition of an extension member object
-    (for example, via <command>CREATE OR REPLACE FUNCTION</command> for a
-    function), bear in mind that the modified definition will not be dumped
-    by <application>pg_dump</>.  Such a change is usually only sensible if
-    you concurrently make the same change in the extension's script file.
-    (But there are special provisions for tables containing configuration
-    data; see below.)
-   </para>
-
-   <para>
-    The extension mechanism also has provisions for packaging modification
-    scripts that adjust the definitions of the SQL objects contained in an
-    extension.  For example, if version 1.1 of an extension adds one function
-    and changes the body of another function compared to 1.0, the extension
-    author can provide an <firstterm>update script</> that makes just those
-    two changes.  The <command>ALTER EXTENSION UPDATE</> command can then
-    be used to apply these changes and track which version of the extension
-    is actually installed in a given database.
-   </para>
-
-   <para>
-    The kinds of SQL objects that can be members of an extension are shown in
-    the description of <xref linkend="sql-alterextension">.  Notably, objects
-    that are database-cluster-wide, such as databases, roles, and tablespaces,
-    cannot be extension members since an extension is only known within one
-    database.  (Although an extension script is not prohibited from creating
-    such objects, if it does so they will not be tracked as part of the
-    extension.)  Also notice that while a table can be a member of an
-    extension, its subsidiary objects such as indexes are not directly
-    considered members of the extension.
-   </para>
-
-   <sect2>
-    <title>Extension Files</title>
-
-   <indexterm>
-    <primary>control file</primary>
-   </indexterm>
-
-    <para>
-     The <xref linkend="sql-createextension"> command relies on a control
-     file for each extension, which must be named the same as the extension
-     with a suffix of <literal>.control</>, and must be placed in the
-     installation's <literal>SHAREDIR/extension</literal> directory.  There
-     must also be at least one <acronym>SQL</> script file, which follows the
-     naming pattern
-     <literal><replaceable>extension</>--<replaceable>version</>.sql</literal>
-     (for example, <literal>foo--1.0.sql</> for version <literal>1.0</> of
-     extension <literal>foo</>).  By default, the script file(s) are also
-     placed in the <literal>SHAREDIR/extension</literal> directory; but the
-     control file can specify a different directory for the script file(s).
-    </para>
-
-    <para>
-     The file format for an extension control file is the same as for the
-     <filename>postgresql.conf</> file, namely a list of
-     <replaceable>parameter_name</> <literal>=</> <replaceable>value</>
-     assignments, one per line.  Blank lines and comments introduced by
-     <literal>#</> are allowed.  Be sure to quote any value that is not
-     a single word or number.
-    </para>
-
-    <para>
-     A control file can set the following parameters:
-    </para>
-
-    <variablelist>
-     <varlistentry>
-      <term><varname>directory</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        The directory containing the extension's <acronym>SQL</> script
-        file(s).  Unless an absolute path is given, the name is relative to
-        the installation's <literal>SHAREDIR</literal> directory.  The
-        default behavior is equivalent to specifying
-        <literal>directory = 'extension'</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>default_version</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        The default version of the extension (the one that will be installed
-        if no version is specified in <command>CREATE EXTENSION</>).  Although
-        this can be omitted, that will result in <command>CREATE EXTENSION</>
-        failing if no <literal>VERSION</> option appears, so you generally
-        don't want to do that.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>comment</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        A comment (any string) about the extension.  Alternatively,
-        the comment can be set by means of the <xref linkend="sql-comment">
-        command in the script file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>encoding</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        The character set encoding used by the script file(s).  This should
-        be specified if the script files contain any non-ASCII characters.
-        Otherwise the files will be assumed to be in the database encoding.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>module_pathname</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        The value of this parameter will be substituted for each occurrence
-        of <literal>MODULE_PATHNAME</> in the script file(s).  If it is not
-        set, no substitution is made.  Typically, this is set to
-        <literal>$libdir/<replaceable>shared_library_name</></literal> and
-        then <literal>MODULE_PATHNAME</> is used in <command>CREATE
-        FUNCTION</> commands for C-language functions, so that the script
-        files do not need to hard-wire the name of the shared library.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>requires</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        A list of names of extensions that this extension depends on,
-        for example <literal>requires = 'foo, bar'</literal>.  Those
-        extensions must be installed before this one can be installed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>superuser</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        If this parameter is <literal>true</> (which is the default),
-        only superusers can create the extension or update it to a new
-        version.  If it is set to <literal>false</>, just the privileges
-        required to execute the commands in the installation or update script
-        are required.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>relocatable</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        An extension is <firstterm>relocatable</> if it is possible to move
-        its contained objects into a different schema after initial creation
-        of the extension.  The default is <literal>false</>, i.e. the
-        extension is not relocatable.
-        See below for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>schema</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        This parameter can only be set for non-relocatable extensions.
-        It forces the extension to be loaded into exactly the named schema
-        and not any other.  See below for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    <para>
-     In addition to the primary control file
-     <literal><replaceable>extension</>.control</literal>,
-     an extension can have secondary control files named in the style
-     <literal><replaceable>extension</>--<replaceable>version</>.control</literal>.
-     If supplied, these must be located in the script file directory.
-     Secondary control files follow the same format as the primary control
-     file.  Any parameters set in a secondary control file override the
-     primary control file when installing or updating to that version of
-     the extension.  However, the parameters <varname>directory</> and
-     <varname>default_version</> cannot be set in a secondary control file.
-    </para>
-
-    <para>
-     An extension's <acronym>SQL</> script files can contain any SQL commands,
-     except for transaction control commands (<command>BEGIN</>,
-     <command>COMMIT</>, etc) and commands that cannot be executed inside a
-     transaction block (such as <command>VACUUM</>).  This is because the
-     script files are implicitly executed within a transaction block.
-    </para>
-
-    <para>
-     While the script files can contain any characters allowed by the specified
-     encoding, control files should contain only plain ASCII, because there
-     is no way for <productname>PostgreSQL</> to know what encoding a
-     control file is in.  In practice this is only an issue if you want to
-     use non-ASCII characters in the extension's comment.  Recommended
-     practice in that case is to not use the control file <varname>comment</>
-     parameter, but instead use <command>COMMENT ON EXTENSION</>
-     within a script file to set the comment.
-    </para>
-
-   </sect2>
-
-   <sect2>
-    <title>Extension Relocatability</title>
-
-    <para>
-     Users often wish to load the objects contained in an extension into a
-     different schema than the extension's author had in mind.  There are
-     three supported levels of relocatability:
-    </para>
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       A fully relocatable extension can be moved into another schema
-       at any time, even after it's been loaded into a database.
-       This is done with the <command>ALTER EXTENSION SET SCHEMA</>
-       command, which automatically renames all the member objects into
-       the new schema.  Normally, this is only possible if the extension
-       contains no internal assumptions about what schema any of its
-       objects are in.  Also, the extension's objects must all be in one
-       schema to begin with (ignoring objects that do not belong to any
-       schema, such as procedural languages).  Mark a fully relocatable
-       extension by setting <literal>relocatable = true</> in its control
-       file.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       An extension might be relocatable during installation but not
-       afterwards.  This is typically the case if the extension's script
-       file needs to reference the target schema explicitly, for example
-       in setting <literal>search_path</> properties for SQL functions.
-       For such an extension, set <literal>relocatable = false</> in its
-       control file, and use <literal>@extschema@</> to refer to the target
-       schema in the script file.  All occurrences of this string will be
-       replaced by the actual target schema's name before the script is
-       executed.  The user can set the target schema using the
-       <literal>SCHEMA</> option of <command>CREATE EXTENSION</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If the extension does not support relocation at all, set
-       <literal>relocatable = false</> in its control file, and also set
-       <literal>schema</> to the name of the intended target schema.  This
-       will prevent use of the <literal>SCHEMA</> option of <command>CREATE
-       EXTENSION</>, unless it specifies the same schema named in the control
-       file.  This choice is typically necessary if the extension contains
-       internal assumptions about schema names that can't be replaced by
-       uses of <literal>@extschema@</>.  The <literal>@extschema@</>
-       substitution mechanism is available in this case too, although it is
-       of limited use since the schema name is determined by the control file.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    <para>
-     In all cases, the script file will be executed with
-     <xref linkend="guc-search-path"> initially set to point to the target
-     schema; that is, <command>CREATE EXTENSION</> does the equivalent of
-     this:
-<programlisting>
-SET LOCAL search_path TO @extschema@;
-</programlisting>
-     This allows the objects created by the script file to go into the target
-     schema.  The script file can change <varname>search_path</> if it wishes,
-     but that is generally undesirable.  <varname>search_path</> is restored
-     to its previous setting upon completion of <command>CREATE EXTENSION</>.
-    </para>
-
-    <para>
-     The target schema is determined by the <varname>schema</> parameter in
-     the control file if that is given, otherwise by the <literal>SCHEMA</>
-     option of <command>CREATE EXTENSION</> if that is given, otherwise the
-     current default object creation schema (the first one in the caller's
-     <varname>search_path</>).  When the control file <varname>schema</>
-     parameter is used, the target schema will be created if it doesn't
-     already exist, but in the other two cases it must already exist.
-    </para>
-
-    <para>
-     If any prerequisite extensions are listed in <varname>requires</varname>
-     in the control file, their target schemas are appended to the initial
-     setting of <varname>search_path</>.  This allows their objects to be
-     visible to the new extension's script file.
-    </para>
-
-    <para>
-     Although a non-relocatable extension can contain objects spread across
-     multiple schemas, it is usually desirable to place all the objects meant
-     for external use into a single schema, which is considered the extension's
-     target schema.  Such an arrangement works conveniently with the default
-     setting of <varname>search_path</> during creation of dependent
-     extensions.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Extension Configuration Tables</title>
-
-    <para>
-     Some extensions include configuration tables, which contain data that
-     might be added or changed by the user after installation of the
-     extension.  Ordinarily, if a table is part of an extension, neither
-     the table's definition nor its content will be dumped by
-     <application>pg_dump</>.  But that behavior is undesirable for a
-     configuration table; any data changes made by the user need to be
-     included in dumps, or the extension will behave differently after a dump
-     and reload.
-    </para>
-
-    <para>
-     To solve this problem, an extension's script file can mark a table
-     it has created as a configuration table, which will cause
-     <application>pg_dump</> to include the table's contents (not its
-     definition) in dumps.  To do that, call the function
-     <function>pg_extension_config_dump(regclass, text)</> after creating the
-     table, for example
-<programlisting>
-CREATE TABLE my_config (key text, value text);
-
-SELECT pg_catalog.pg_extension_config_dump('my_config', '');
-</programlisting>
-     Any number of tables can be marked this way.
-    </para>
-
-    <para>
-     When the second argument of <function>pg_extension_config_dump</> is
-     an empty string, the entire contents of the table are dumped by
-     <application>pg_dump</>.  This is usually only correct if the table
-     is initially empty as created by the extension script.  If there is
-     a mixture of initial data and user-provided data in the table,
-     the second argument of <function>pg_extension_config_dump</> provides
-     a <literal>WHERE</> condition that selects the data to be dumped.
-     For example, you might do
-<programlisting>
-CREATE TABLE my_config (key text, value text, standard_entry boolean);
-
-SELECT pg_catalog.pg_extension_config_dump('my_config', 'WHERE NOT standard_entry');
-</programlisting>
-     and then make sure that <structfield>standard_entry</> is true only
-     in the rows created by the extension's script.
-    </para>
-
-    <para>
-     More complicated situations, such as initially-provided rows that might
-     be modified by users, can be handled by creating triggers on the
-     configuration table to ensure that modified rows are marked correctly.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Extension Updates</title>
-
-    <para>
-     One advantage of the extension mechanism is that it provides convenient
-     ways to manage updates to the SQL commands that define an extension's
-     objects.  This is done by associating a version name or number with
-     each released version of the extension's installation script.
-     In addition, if you want users to be able to update their databases
-     dynamically from one version to the next, you should provide
-     <firstterm>update scripts</> that make the necessary changes to go from
-     one version to the next.  Update scripts have names following the pattern
-     <literal><replaceable>extension</>--<replaceable>oldversion</>--<replaceable>newversion</>.sql</literal>
-     (for example, <literal>foo--1.0--1.1.sql</> contains the commands to modify
-     version <literal>1.0</> of extension <literal>foo</> into version
-     <literal>1.1</>).
-    </para>
-
-    <para>
-     Given that a suitable update script is available, the command
-     <command>ALTER EXTENSION UPDATE</> will update an installed extension
-     to the specified new version.  The update script is run in the same
-     environment that <command>CREATE EXTENSION</> provides for installation
-     scripts: in particular, <varname>search_path</> is set up in the same
-     way, and any new objects created by the script are automatically added
-     to the extension.
-    </para>
-
-    <para>
-     If an extension has secondary control files, the control parameters
-     that are used for an update script are those associated with the script's
-     target (new) version.
-    </para>
-
-    <para>
-     The update mechanism can be used to solve an important special case:
-     converting a <quote>loose</> collection of objects into an extension.
-     Before the extension mechanism was added to
-     <productname>PostgreSQL</productname> (in 9.1), many people wrote
-     extension modules that simply created assorted unpackaged objects.
-     Given an existing database containing such objects, how can we convert
-     the objects into a properly packaged extension?  Dropping them and then
-     doing a plain <command>CREATE EXTENSION</> is one way, but it's not
-     desirable if the objects have dependencies (for example, if there are
-     table columns of a data type created by the extension).  The way to fix
-     this situation is to create an empty extension, then use <command>ALTER
-     EXTENSION ADD</> to attach each pre-existing object to the extension,
-     then finally create any new objects that are in the current extension
-     version but were not in the unpackaged release.  <command>CREATE
-     EXTENSION</> supports this case with its <literal>FROM</> <replaceable
-     class="parameter">old_version</> option, which causes it to not run the
-     normal installation script for the target version, but instead the update
-     script named
-     <literal><replaceable>extension</>--<replaceable>old_version</>--<replaceable>target_version</>.sql</literal>.
-     The choice of the dummy version name to use as <replaceable
-     class="parameter">old_version</> is up to the extension author, though
-     <literal>unpackaged</> is a common convention.  If you have multiple
-     prior versions you need to be able to update into extension style, use
-     multiple dummy version names to identify them.
-    </para>
-
-    <para>
-     <command>ALTER EXTENSION</> is able to execute sequences of update
-     script files to achieve a requested update.  For example, if only
-     <literal>foo--1.0--1.1.sql</> and <literal>foo--1.1--2.0.sql</> are
-     available, <command>ALTER EXTENSION</> will apply them in sequence if an
-     update to version <literal>2.0</> is requested when <literal>1.0</> is
-     currently installed.
-    </para>
-
-    <para>
-     <productname>PostgreSQL</> doesn't assume anything about the properties
-     of version names: for example, it does not know whether <literal>1.1</>
-     follows <literal>1.0</>.  It just matches up the available version names
-     and follows the path that requires applying the fewest update scripts.
-     (A version name can actually be any string that doesn't contain
-     <literal>--</> or leading or trailing <literal>-</>.)
-    </para>
-
-    <para>
-     Sometimes it is useful to provide <quote>downgrade</> scripts, for
-     example <literal>foo--1.1--1.0.sql</> to allow reverting the changes
-     associated with version <literal>1.1</>.  If you do that, be careful
-     of the possibility that a downgrade script might unexpectedly
-     get applied because it yields a shorter path.  The risky case is where
-     there is a <quote>fast path</> update script that jumps ahead several
-     versions as well as a downgrade script to the fast path's start point.
-     It might take fewer steps to apply the downgrade and then the fast
-     path than to move ahead one version at a time.  If the downgrade script
-     drops any irreplaceable objects, this will yield undesirable results.
-    </para>
-
-    <para>
-     To check for unexpected update paths, use this command:
-<programlisting>
-SELECT * FROM pg_extension_update_paths('<replaceable>extension_name</>');
-</programlisting>
-     This shows each pair of distinct known version names for the specified
-     extension, together with the update path sequence that would be taken to
-     get from the source version to the target version, or <literal>NULL</> if
-     there is no available update path.  The path is shown in textual form
-     with <literal>--</> separators.  You can use
-     <literal>regexp_split_to_array(path,'--')</> if you prefer an array
-     format.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Extension Example</title>
-
-    <para>
-     Here is a complete example of an <acronym>SQL</>-only
-     extension, a two-element composite type that can store any type of value
-     in its slots, which are named <quote>k</> and <quote>v</>.  Non-text
-     values are automatically coerced to text for storage.
-    </para>
-
-    <para>
-     The script file <filename>pair--1.0.sql</> looks like this:
-
-<programlisting><![CDATA[
-CREATE TYPE pair AS ( k text, v text );
-
-CREATE OR REPLACE FUNCTION pair(anyelement, text)
-RETURNS pair LANGUAGE SQL AS 'SELECT ROW($1, $2)::pair';
-
-CREATE OR REPLACE FUNCTION pair(text, anyelement)
-RETURNS pair LANGUAGE SQL AS 'SELECT ROW($1, $2)::pair';
-
-CREATE OR REPLACE FUNCTION pair(anyelement, anyelement)
-RETURNS pair LANGUAGE SQL AS 'SELECT ROW($1, $2)::pair';
-
-CREATE OR REPLACE FUNCTION pair(text, text)
-RETURNS pair LANGUAGE SQL AS 'SELECT ROW($1, $2)::pair;';
-
-CREATE OPERATOR ~> (LEFTARG = text, RIGHTARG = anyelement, PROCEDURE = pair);
-CREATE OPERATOR ~> (LEFTARG = anyelement, RIGHTARG = text, PROCEDURE = pair);
-CREATE OPERATOR ~> (LEFTARG = anyelement, RIGHTARG = anyelement, PROCEDURE = pair);
-CREATE OPERATOR ~> (LEFTARG = text, RIGHTARG = text, PROCEDURE = pair);
-]]>
-</programlisting>
-    </para>
-
-    <para>
-     The control file <filename>pair.control</> looks like this:
-
-<programlisting>
-# pair extension
-comment = 'A key/value pair data type'
-default_version = '1.0'
-relocatable = true
-</programlisting>
-    </para>
-
-    <para>
-     While you hardly need a makefile to install these two files into the
-     correct directory, you could use a <filename>Makefile</> containing this:
-
-<programlisting>
-EXTENSION = pair
-DATA = pair--1.0.sql
-
-PG_CONFIG = pg_config
-PGXS := $(shell $(PG_CONFIG) --pgxs)
-include $(PGXS)
-</programlisting>
-
-     This makefile relies on <acronym>PGXS</acronym>, which is described
-     in <xref linkend="extend-pgxs">.  The command <literal>make install</>
-     will install the control and script files into the correct
-     directory as reported by <application>pg_config</>.
-    </para>
-
-    <para>
-     Once the files are installed, use the
-     <xref linkend="sql-createextension"> command to load the objects into
-     any particular database.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="extend-pgxs">
-   <title>Extension Building Infrastructure</title>
-
-   <indexterm zone="extend-pgxs">
-    <primary>pgxs</primary>
-   </indexterm>
-
-   <para>
-    If you are thinking about distributing your
-    <productname>PostgreSQL</> extension modules, setting up a
-    portable build system for them can be fairly difficult.  Therefore
-    the <productname>PostgreSQL</> installation provides a build
-    infrastructure for extensions, called <acronym>PGXS</acronym>, so
-    that simple extension modules can be built simply against an
-    already installed server.  <acronym>PGXS</acronym> is mainly intended
-    for extensions that include C code, although it can be used for
-    pure-SQL extensions too.  Note that <acronym>PGXS</acronym> is not
-    intended to be a universal build system framework that can be used
-    to build any software interfacing to <productname>PostgreSQL</>;
-    it simply automates common build rules for simple server extension
-    modules.  For more complicated packages, you might need to write your
-    own build system.
-   </para>
-
-   <para>
-    To use the <acronym>PGXS</acronym> infrastructure for your extension,
-    you must write a simple makefile.
-    In the makefile, you need to set some variables
-    and finally include the global <acronym>PGXS</acronym> makefile.
-    Here is an example that builds an extension module named
-    <literal>isbn_issn</literal>, consisting of a shared library containing
-    some C code, an extension control file, a SQL script, and a documentation
-    text file:
-<programlisting>
-MODULES = isbn_issn
-EXTENSION = isbn_issn
-DATA = isbn_issn--1.0.sql
-DOCS = README.isbn_issn
-
-PG_CONFIG = pg_config
-PGXS := $(shell $(PG_CONFIG) --pgxs)
-include $(PGXS)
-</programlisting>
-    The last three lines should always be the same.  Earlier in the
-    file, you assign variables or add custom
-    <application>make</application> rules.
-   </para>
-
-   <para>
-    Set one of these three variables to specify what is built:
-
-    <variablelist>
-     <varlistentry>
-      <term><varname>MODULES</varname></term>
-      <listitem>
-       <para>
-        list of shared-library objects to be built from source files with same
-        stem (do not include library suffixes in this list)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>MODULE_big</varname></term>
-      <listitem>
-       <para>
-        a shared library to build from multiple source files
-        (list object files in <varname>OBJS</varname>)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>PROGRAM</varname></term>
-      <listitem>
-       <para>
-        an executable program to build
-        (list object files in <varname>OBJS</varname>)
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    The following variables can also be set:
-
-    <variablelist>
-     <varlistentry>
-      <term><varname>EXTENSION</varname></term>
-      <listitem>
-       <para>
-        extension name(s); for each name you must provide an
-        <literal><replaceable>extension</replaceable>.control</literal> file,
-        which will be installed into
-        <literal><replaceable>prefix</replaceable>/share/extension</literal>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>MODULEDIR</varname></term>
-      <listitem>
-       <para>
-        subdirectory of <literal><replaceable>prefix</>/share</literal>
-        into which DATA and DOCS files should be installed
-        (if not set, default is <literal>extension</literal> if
-        <varname>EXTENSION</varname> is set,
-        or <literal>contrib</literal> if not)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>DATA</varname></term>
-      <listitem>
-       <para>
-        random files to install into <literal><replaceable>prefix</replaceable>/share/$MODULEDIR</literal>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>DATA_built</varname></term>
-      <listitem>
-       <para>
-        random files to install into
-        <literal><replaceable>prefix</replaceable>/share/$MODULEDIR</literal>,
-        which need to be built first
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>DATA_TSEARCH</varname></term>
-      <listitem>
-       <para>
-        random files to install under
-        <literal><replaceable>prefix</replaceable>/share/tsearch_data</literal>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>DOCS</varname></term>
-      <listitem>
-       <para>
-        random files to install under
-        <literal><replaceable>prefix</replaceable>/doc/$MODULEDIR</literal>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SCRIPTS</varname></term>
-      <listitem>
-       <para>
-        script files (not binaries) to install into
-        <literal><replaceable>prefix</replaceable>/bin</literal>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SCRIPTS_built</varname></term>
-      <listitem>
-       <para>
-        script files (not binaries) to install into
-        <literal><replaceable>prefix</replaceable>/bin</literal>,
-        which need to be built first
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>REGRESS</varname></term>
-      <listitem>
-       <para>
-        list of regression test cases (without suffix), see below
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>EXTRA_CLEAN</varname></term>
-      <listitem>
-       <para>
-        extra files to remove in <literal>make clean</literal>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>PG_CPPFLAGS</varname></term>
-      <listitem>
-       <para>
-        will be added to <varname>CPPFLAGS</varname>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>PG_LIBS</varname></term>
-      <listitem>
-       <para>
-        will be added to <varname>PROGRAM</varname> link line
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SHLIB_LINK</varname></term>
-      <listitem>
-       <para>
-        will be added to <varname>MODULE_big</varname> link line
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>PG_CONFIG</varname></term>
-      <listitem>
-       <para>
-        path to <application>pg_config</> program for the
-        <productname>PostgreSQL</productname> installation to build against
-        (typically just <literal>pg_config</> to use the first one in your
-        <varname>PATH</>)
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    Put this makefile as <literal>Makefile</literal> in the directory
-    which holds your extension. Then you can do
-    <literal>make</literal> to compile, and then <literal>make
-    install</literal> to install your module.  By default, the extension is
-    compiled and installed for the
-    <productname>PostgreSQL</productname> installation that
-    corresponds to the first <command>pg_config</command> program
-    found in your <varname>PATH</>.  You can use a different installation by
-    setting <varname>PG_CONFIG</varname> to point to its
-    <command>pg_config</command> program, either within the makefile
-    or on the <literal>make</literal> command line.
-   </para>
-
-   <caution>
-    <para>
-     Changing <varname>PG_CONFIG</varname> only works when building
-     against <productname>PostgreSQL</productname> 8.3 or later.
-     With older releases it does not work to set it to anything except
-     <literal>pg_config</>; you must alter your <varname>PATH</>
-     to select the installation to build against.
-    </para>
-   </caution>
-
-   <para>
-    The scripts listed in the <varname>REGRESS</> variable are used for
-    regression testing of your module, which can be invoked by <literal>make
-    installcheck</literal> after doing <literal>make install</>.  For this to
-    work you must have a running <productname>PostgreSQL</productname> server.
-    The script files listed in <varname>REGRESS</> must appear in a
-    subdirectory named <literal>sql/</literal> in your extension's directory.
-    These files must have extension <literal>.sql</literal>, which must not be
-    included in the <varname>REGRESS</varname> list in the makefile.  For each
-    test there should also be a file containing the expected output in a
-    subdirectory named <literal>expected/</literal>, with the same stem and
-    extension <literal>.out</literal>.  <literal>make installcheck</literal>
-    executes each test script with <application>psql</>, and compares the
-    resulting output to the matching expected file.  Any differences will be
-    written to the file <literal>regression.diffs</literal> in <command>diff
-    -c</command> format.  Note that trying to run a test that is missing its
-    expected file will be reported as <quote>trouble</quote>, so make sure you
-    have all expected files.
-   </para>
-
-   <tip>
-    <para>
-     The easiest way to create the expected files is to create empty files,
-     then do a test run (which will of course report differences).  Inspect
-     the actual result files found in the <literal>results/</literal>
-     directory, then copy them to <literal>expected/</literal> if they match
-     what you expect from the test.
-    </para>
-
-   </tip>
-  </sect1>
-
- </chapter>
diff --git a/doc-xc/src/sgml/external-projects.sgmlin b/doc-xc/src/sgml/external-projects.sgmlin
deleted file mode 100644
index d2b227d482..0000000000
--- a/doc-xc/src/sgml/external-projects.sgmlin
+++ /dev/null
@@ -1,284 +0,0 @@
-<!-- doc/src/sgml/external-projects.sgml -->
-
- <appendix id="external-projects">
-  <title>External Projects</title>
-
-<!## XC>
-&xconly;
-  <para>
-   Original <productname>PostgreSQL</> has a lot of external projects.
-   For details, please see the corresponding sections of
-   original <productname>PostgreSQL</> manuals.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Original <productname>PostgreSQL</> has a lot of external projects.
-   For details, please see the corresponding sections of
-   original <productname>PostgreSQL</> manuals.
-  </para>
-<!## end>
-
-<!## PG>
-  <para>
-   <productname>PostgreSQL</productname> is a complex software project,
-   and managing the project is difficult. We have found that many
-   enhancements to <productname>PostgreSQL</productname> can be more
-   efficiently developed separately from the core project.
-  </para>
-
-  <para>
-   To help our community with the development of their external projects, we
-   have created <ulink url="http://www.pgfoundry.org/">PgFoundry</ulink>, a
-   website that provides hosting for <productname>PostgreSQL</>-related
-   projects that are maintained outside the core <productname>PostgreSQL</>
-   distribution. PgFoundry is built using the GForge software project and is
-   similar to <ulink url="http://sourceforge.net">SourceForge.net</> in its
-   feature set, providing mailing lists, forums, bug tracking, SCM, and web
-   hosting. If you have a <productname>PostgreSQL</>-related open source
-   project that you would like to have hosted at PgFoundry, please feel free
-   to create a new project there.
-  </para>
-
- <sect1 id="external-interfaces">
-  <title>Client Interfaces</title>
-
-  <indexterm>
-   <primary>interfaces</primary>
-   <secondary>externally maintained</secondary>
-  </indexterm>
-
-&pgnotice;
-  <para>
-   There are only two client interfaces included in the base
-   <productname>PostgreSQL</productname> distribution:
-   <itemizedlist>
-    <listitem>
-     <para>
-      <link linkend="libpq">libpq</link> is included because it is the
-      primary C language interface, and because many other client interfaces
-      are built on top of it.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <link linkend="ecpg">ECPG</link> is included because it depends on the
-      server-side SQL grammar, and is therefore sensitive to changes in
-      <productname>PostgreSQL</productname> itself.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   All other language interfaces are external projects and are distributed
-   separately. <xref linkend="language-interface-table"> includes a list of
-   some of these projects. Note that some of these packages might not be
-   released under the same license as <productname>PostgreSQL</>. For more
-   information on each language interface, including licensing terms, refer to
-   its website and documentation.
-  </para>
-
-  <table id="language-interface-table">
-   <title>Externally Maintained Client Interfaces</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Language</entry>
-      <entry>Comments</entry>
-      <entry>Website</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry>DBD::Pg</entry>
-      <entry>Perl</entry>
-      <entry>Perl DBI driver</entry>
-      <entry><ulink url="http://search.cpan.org/dist/DBD-Pg/">http://search.cpan.org/dist/DBD-Pg/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>JDBC</entry>
-      <entry>JDBC</entry>
-      <entry>Type 4 JDBC driver</entry>
-      <entry><ulink url="http://jdbc.postgresql.org/">http://jdbc.postgresql.org/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>libpqxx</entry>
-      <entry>C++</entry>
-      <entry>New-style C++ interface</entry>
-      <entry><ulink url="http://pqxx.org/">http://pqxx.org/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>Npgsql</entry>
-      <entry>.NET</entry>
-      <entry>.NET data provider</entry>
-      <entry><ulink url="http://npgsql.projects.postgresql.org/">http://npgsql.projects.postgresql.org/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>ODBCng</entry>
-      <entry>ODBC</entry>
-      <entry>An alternative ODBC driver</entry>
-      <entry><ulink url="http://projects.commandprompt.com/public/odbcng/">http://projects.commandprompt.com/public/odbcng/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>pgtclng</entry>
-      <entry>Tcl</entry>
-      <entry></entry>
-      <entry><ulink url="http://pgfoundry.org/projects/pgtclng/">http://pgfoundry.org/projects/pgtclng/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>psqlODBC</entry>
-      <entry>ODBC</entry>
-      <entry>The most commonly-used ODBC driver</entry>
-      <entry><ulink url="http://psqlodbc.projects.postgresql.org/">http://psqlodbc.projects.postgresql.org/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>psycopg</entry>
-      <entry>Python</entry>
-      <entry>DB API 2.0-compliant</entry>
-      <entry><ulink url="http://www.initd.org/">http://www.initd.org/</ulink></entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="external-admin-tools">
- <title>Administration Tools</title>
-
-  <indexterm>
-   <primary>administration tools</primary>
-   <secondary>externally maintained</secondary>
-  </indexterm>
-
-  <para>
-   There are several administration tools available for
-   <productname>PostgreSQL</>. The most popular is
-   <application><ulink url="http://www.pgadmin.org/">pgAdmin III</ulink></>,
-   and there are several commercially available ones as well.
-  </para>
- </sect1>
-
- <sect1 id="external-pl">
-  <title>Procedural Languages</title>
-
-  <indexterm>
-   <primary>procedural language</primary>
-   <secondary>externally maintained</secondary>
-  </indexterm>
-
-&pgnotice;
-  <para>
-   <productname>PostgreSQL</productname> includes several procedural
-   languages with the base distribution: <link
-   linkend="plpgsql">PL/pgSQL</link>, <link linkend="pltcl">PL/Tcl</link>,
-   <link linkend="plperl">PL/Perl</link>, and <link
-   linkend="plpython">PL/Python</link>.
-  </para>
-
-  <para>
-   In addition, there are a number of procedural languages that are developed
-   and maintained outside the core <productname>PostgreSQL</productname>
-   distribution. <xref linkend="pl-language-table"> lists some of these
-   packages. Note that some of these projects might not be released under the same
-   license as <productname>PostgreSQL</>. For more information on each
-   procedural language, including licensing information, refer to its website
-   and documentation.
-  </para>
-
-  <table id="pl-language-table">
-   <title>Externally Maintained Procedural Languages</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Language</entry>
-      <entry>Website</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry>PL/Java</entry>
-      <entry>Java</entry>
-      <entry><ulink url="http://pljava.projects.postgresql.org/">http://pljava.projects.postgresql.org/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>PL/PHP</entry>
-      <entry>PHP</entry>
-      <entry><ulink url="http://www.commandprompt.com/community/plphp/">http://www.commandprompt.com/community/plphp/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>PL/Py</entry>
-      <entry>Python</entry>
-      <entry><ulink url="http://python.projects.postgresql.org/">http://python.projects.postgresql.org/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>PL/R</entry>
-      <entry>R</entry>
-      <entry><ulink url="http://www.joeconway.com/plr/">http://www.joeconway.com/plr/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>PL/Ruby</entry>
-      <entry>Ruby</entry>
-      <entry><ulink url="http://raa.ruby-lang.org/project/pl-ruby/">http://raa.ruby-lang.org/project/pl-ruby/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>PL/Scheme</entry>
-      <entry>Scheme</entry>
-      <entry><ulink url="http://plscheme.projects.postgresql.org/">http://plscheme.projects.postgresql.org/</ulink></entry>
-     </row>
-
-     <row>
-      <entry>PL/sh</entry>
-      <entry>Unix shell</entry>
-      <entry><ulink url="http://plsh.projects.postgresql.org/">http://plsh.projects.postgresql.org/</ulink></entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="external-extensions">
- <title>Extensions</title>
-
-  <indexterm>
-   <primary>extension</primary>
-   <secondary>externally maintained</secondary>
-  </indexterm>
-
-&pgnotice;
-  <para>
-   <productname>PostgreSQL</> is designed to be easily extensible. For
-   this reason, extensions loaded into the database can function
-   just like features that are built in. The
-   <filename>contrib/</> directory shipped with the source code
-   contains several extensions, which are described in
-   <xref linkend="contrib">.  Other extensions are developed
-   independently, like <application><ulink
-   url="http://www.postgis.org/">PostGIS</ulink></>.  Even
-   <productname>PostgreSQL</> replication solutions can be developed
-   externally. For example, <application> <ulink
-   url="http://www.slony.info">Slony-I</ulink></> is a popular
-   master/standby replication solution that is developed independently
-   from the core project.
-  </para>
- </sect1>
-<!## end>
-</appendix>
diff --git a/doc-xc/src/sgml/fdwhandler.sgmlin b/doc-xc/src/sgml/fdwhandler.sgmlin
deleted file mode 100644
index fc07f129b7..0000000000
--- a/doc-xc/src/sgml/fdwhandler.sgmlin
+++ /dev/null
@@ -1,212 +0,0 @@
-<!-- doc/src/sgml/fdwhandler.sgml -->
-
- <chapter id="fdwhandler">
-   <title>Writing A Foreign Data Wrapper</title>
-
-   <indexterm zone="fdwhandler">
-    <primary>foreign data wrapper</primary>
-    <secondary>handler for</secondary>
-   </indexterm>
-
-   <para>
-    All operations on a foreign table are handled through its foreign data
-    wrapper, which consists of a set of functions that the planner and
-    executor call. The foreign data wrapper is responsible for fetching
-    data from the remote data source and returning it to the
-    <productname>PostgreSQL</productname> executor. This chapter outlines how
-    to write a new foreign data wrapper.
-   </para>
-
-   <para>
-    The FDW author needs to implement a handler function, and optionally
-    a validator function. Both functions must be written in a compiled
-    language such as C, using the version-1 interface.
-    For details on C language calling conventions and dynamic loading,
-    see <xref linkend="xfunc-c">.
-   </para>
-
-   <para>
-    The handler function simply returns a struct of function pointers to
-    callback functions that will be called by the planner and executor.
-    Most of the effort in writing an FDW is in implementing these callback
-    functions.
-    The handler function must be registered with
-    <productname>PostgreSQL</productname> as taking no arguments and returning
-    the special pseudo-type <type>fdw_handler</type>.
-    The callback functions are plain C functions and are not visible or
-    callable at the SQL level.
-   </para>
-
-   <para>
-    The validator function is responsible for validating options given in the
-    <command>CREATE FOREIGN DATA WRAPPER</command>, <command>CREATE
-    SERVER</command> and <command>CREATE FOREIGN TABLE</command> commands.
-    The validator function must be registered as taking two arguments, a text
-    array containing the options to be validated, and an OID representing the
-    type of object the options are associated with (in the form of the OID
-    of the system catalog the object would be stored in).  If no validator
-    function is supplied, the options are not checked at object creation time.
-   </para>
-
-   <para>
-    The foreign data wrappers included in the standard distribution are good
-    references when trying to write your own.  Look into the
-    <filename>contrib/file_fdw</> subdirectory of the source tree.
-    The <xref linkend="sql-createforeigndatawrapper"> reference page also has
-    some useful details.
-   </para>
-
-   <note>
-    <para>
-     The SQL standard specifies an interface for writing foreign data wrappers.
-     However, PostgreSQL does not implement that API, because the effort to
-     accommodate it into PostgreSQL would be large, and the standard API hasn't
-     gained wide adoption anyway.
-    </para>
-   </note>
-
-   <sect1 id="fdw-routines">
-    <title>Foreign Data Wrapper Callback Routines</title>
-
-    <para>
-     The FDW handler function returns a palloc'd <structname>FdwRoutine</>
-     struct containing pointers to the following callback functions:
-    </para>
-
-    <para>
-<programlisting>
-FdwPlan *
-PlanForeignScan (Oid foreigntableid,
-                 PlannerInfo *root,
-                 RelOptInfo *baserel);
-</programlisting>
-
-     Plan a scan on a foreign table. This is called when a query is planned.
-     <literal>foreigntableid</> is the <structname>pg_class</> OID of the
-     foreign table.  <literal>root</> is the planner's global information
-     about the query, and <literal>baserel</> is the planner's information
-     about this table.
-     The function must return a palloc'd struct that contains cost estimates
-     plus any FDW-private information that is needed to execute the foreign
-     scan at a later time.  (Note that the private information must be
-     represented in a form that <function>copyObject</> knows how to copy.)
-    </para>
-
-    <para>
-     The information in <literal>root</> and <literal>baserel</> can be used
-     to reduce the amount of information that has to be fetched from the
-     foreign table (and therefore reduce the cost estimate).
-     <literal>baserel-&gt;baserestrictinfo</> is particularly interesting, as
-     it contains restriction quals (<literal>WHERE</> clauses) that can be
-     used to filter the rows to be fetched.  (The FDW is not required to
-     enforce these quals, as the finished plan will recheck them anyway.)
-     <literal>baserel-&gt;reltargetlist</> can be used to determine which
-     columns need to be fetched.
-    </para>
-
-    <para>
-     In addition to returning cost estimates, the function should update
-     <literal>baserel-&gt;rows</> to be the expected number of rows returned
-     by the scan, after accounting for the filtering done by the restriction
-     quals.  The initial value of <literal>baserel-&gt;rows</> is just a
-     constant default estimate, which should be replaced if at all possible.
-     The function may also choose to update <literal>baserel-&gt;width</> if
-     it can compute a better estimate of the average result row width.
-    </para>
-
-    <para>
-<programlisting>
-void
-ExplainForeignScan (ForeignScanState *node,
-                    ExplainState *es);
-</programlisting>
-
-     Print additional <command>EXPLAIN</> output for a foreign table scan.
-     This can just return if there is no need to print anything.
-     Otherwise, it should call <function>ExplainPropertyText</> and
-     related functions to add fields to the <command>EXPLAIN</> output.
-     The flag fields in <literal>es</> can be used to determine what to
-     print, and the state of the <structname>ForeignScanState</> node
-     can be inspected to provide runtime statistics in the <command>EXPLAIN
-     ANALYZE</> case.
-    </para>
-
-    <para>
-<programlisting>
-void
-BeginForeignScan (ForeignScanState *node,
-                  int eflags);
-</programlisting>
-
-     Begin executing a foreign scan. This is called during executor startup.
-     It should perform any initialization needed before the scan can start.
-     The <structname>ForeignScanState</> node has already been created, but
-     its <structfield>fdw_state</> field is still NULL.  Information about
-     the table to scan is accessible through the
-     <structname>ForeignScanState</> node (in particular, from the underlying
-     <structname>ForeignScan</> plan node, which contains a pointer to the
-     <structname>FdwPlan</> structure returned by
-     <function>PlanForeignScan</>).
-    </para>
-
-    <para>
-     Note that when <literal>(eflags &amp; EXEC_FLAG_EXPLAIN_ONLY)</> is
-     true, this function should not perform any externally-visible actions;
-     it should only do the minimum required to make the node state valid
-     for <function>ExplainForeignScan</> and <function>EndForeignScan</>.
-    </para>
-
-    <para>
-<programlisting>
-TupleTableSlot *
-IterateForeignScan (ForeignScanState *node);
-</programlisting>
-
-     Fetch one row from the foreign source, returning it in a tuple table slot
-     (the node's <structfield>ScanTupleSlot</> should be used for this
-     purpose).  Return NULL if no more rows are available.  The tuple table
-     slot infrastructure allows either a physical or virtual tuple to be
-     returned; in most cases the latter choice is preferable from a
-     performance standpoint.  Note that this is called in a short-lived memory
-     context that will be reset between invocations.  Create a memory context
-     in <function>BeginForeignScan</> if you need longer-lived storage, or use
-     the <structfield>es_query_cxt</> of the node's <structname>EState</>.
-    </para>
-
-    <para>
-     The rows returned must match the column signature of the foreign table
-     being scanned.  If you choose to optimize away fetching columns that
-     are not needed, you should insert nulls in those column positions.
-    </para>
-
-    <para>
-<programlisting>
-void
-ReScanForeignScan (ForeignScanState *node);
-</programlisting>
-
-     Restart the scan from the beginning.  Note that any parameters the
-     scan depends on may have changed value, so the new scan does not
-     necessarily return exactly the same rows.
-    </para>
-
-    <para>
-<programlisting>
-void
-EndForeignScan (ForeignScanState *node);
-</programlisting>
-
-     End the scan and release resources.  It is normally not important
-     to release palloc'd memory, but for example open files and connections
-     to remote servers should be cleaned up.
-    </para>
-
-    <para>
-     The <structname>FdwRoutine</> and <structname>FdwPlan</> struct types
-     are declared in <filename>src/include/foreign/fdwapi.h</>, which see
-     for additional details.
-    </para>
-
-   </sect1>
-
- </chapter>
diff --git a/doc-xc/src/sgml/features-supported.sgmlin b/doc-xc/src/sgml/features-supported.sgmlin
deleted file mode 100644
index 2930e6418c..0000000000
--- a/doc-xc/src/sgml/features-supported.sgmlin
+++ /dev/null
@@ -1,2078 +0,0 @@
-<tbody>
- <row>
-  <entry>B012</entry>
-  <entry></entry>
-  <entry>Embedded C</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B021</entry>
-  <entry></entry>
-  <entry>Direct SQL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E011</entry>
-  <entry>Core</entry>
-  <entry>Numeric data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E011-01</entry>
-  <entry>Core</entry>
-  <entry>INTEGER and SMALLINT data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E011-02</entry>
-  <entry>Core</entry>
-  <entry>REAL, DOUBLE PRECISION, and FLOAT data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E011-03</entry>
-  <entry>Core</entry>
-  <entry>DECIMAL and NUMERIC data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E011-04</entry>
-  <entry>Core</entry>
-  <entry>Arithmetic operators</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E011-05</entry>
-  <entry>Core</entry>
-  <entry>Numeric comparison</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E011-06</entry>
-  <entry>Core</entry>
-  <entry>Implicit casting among the numeric data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021</entry>
-  <entry>Core</entry>
-  <entry>Character data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-01</entry>
-  <entry>Core</entry>
-  <entry>CHARACTER data type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-02</entry>
-  <entry>Core</entry>
-  <entry>CHARACTER VARYING data type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-03</entry>
-  <entry>Core</entry>
-  <entry>Character literals</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-04</entry>
-  <entry>Core</entry>
-  <entry>CHARACTER_LENGTH function</entry>
-  <entry>trims trailing spaces from CHARACTER values before counting</entry>
- </row>
- <row>
-  <entry>E021-05</entry>
-  <entry>Core</entry>
-  <entry>OCTET_LENGTH function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-06</entry>
-  <entry>Core</entry>
-  <entry>SUBSTRING function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-07</entry>
-  <entry>Core</entry>
-  <entry>Character concatenation</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-08</entry>
-  <entry>Core</entry>
-  <entry>UPPER and LOWER functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-09</entry>
-  <entry>Core</entry>
-  <entry>TRIM function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-10</entry>
-  <entry>Core</entry>
-  <entry>Implicit casting among the character string types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-11</entry>
-  <entry>Core</entry>
-  <entry>POSITION function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E021-12</entry>
-  <entry>Core</entry>
-  <entry>Character comparison</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E031</entry>
-  <entry>Core</entry>
-  <entry>Identifiers</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E031-01</entry>
-  <entry>Core</entry>
-  <entry>Delimited identifiers</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E031-02</entry>
-  <entry>Core</entry>
-  <entry>Lower case identifiers</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E031-03</entry>
-  <entry>Core</entry>
-  <entry>Trailing underscore</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E051</entry>
-  <entry>Core</entry>
-  <entry>Basic query specification</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E051-01</entry>
-  <entry>Core</entry>
-  <entry>SELECT DISTINCT</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E051-02</entry>
-  <entry>Core</entry>
-  <entry>GROUP BY clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E051-04</entry>
-  <entry>Core</entry>
-  <entry>GROUP BY can contain columns not in &lt;select list&gt;</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E051-05</entry>
-  <entry>Core</entry>
-  <entry>Select list items can be renamed</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E051-06</entry>
-  <entry>Core</entry>
-  <entry>HAVING clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E051-07</entry>
-  <entry>Core</entry>
-  <entry>Qualified * in select list</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E051-08</entry>
-  <entry>Core</entry>
-  <entry>Correlation names in the FROM clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E051-09</entry>
-  <entry>Core</entry>
-  <entry>Rename columns in the FROM clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061</entry>
-  <entry>Core</entry>
-  <entry>Basic predicates and search conditions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-01</entry>
-  <entry>Core</entry>
-  <entry>Comparison predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-02</entry>
-  <entry>Core</entry>
-  <entry>BETWEEN predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-03</entry>
-  <entry>Core</entry>
-  <entry>IN predicate with list of values</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-04</entry>
-  <entry>Core</entry>
-  <entry>LIKE predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-05</entry>
-  <entry>Core</entry>
-  <entry>LIKE predicate ESCAPE clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-06</entry>
-  <entry>Core</entry>
-  <entry>NULL predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-07</entry>
-  <entry>Core</entry>
-  <entry>Quantified comparison predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-08</entry>
-  <entry>Core</entry>
-  <entry>EXISTS predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-09</entry>
-  <entry>Core</entry>
-  <entry>Subqueries in comparison predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-11</entry>
-  <entry>Core</entry>
-  <entry>Subqueries in IN predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-12</entry>
-  <entry>Core</entry>
-  <entry>Subqueries in quantified comparison predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-13</entry>
-  <entry>Core</entry>
-  <entry>Correlated subqueries</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E061-14</entry>
-  <entry>Core</entry>
-  <entry>Search condition</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E071</entry>
-  <entry>Core</entry>
-  <entry>Basic query expressions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E071-01</entry>
-  <entry>Core</entry>
-  <entry>UNION DISTINCT table operator</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E071-02</entry>
-  <entry>Core</entry>
-  <entry>UNION ALL table operator</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E071-03</entry>
-  <entry>Core</entry>
-  <entry>EXCEPT DISTINCT table operator</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E071-05</entry>
-  <entry>Core</entry>
-  <entry>Columns combined via table operators need not have exactly the same data type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E071-06</entry>
-  <entry>Core</entry>
-  <entry>Table operators in subqueries</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081-01</entry>
-  <entry>Core</entry>
-  <entry>SELECT privilege</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081-02</entry>
-  <entry>Core</entry>
-  <entry>DELETE privilege</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081-03</entry>
-  <entry>Core</entry>
-  <entry>INSERT privilege at the table level</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081-04</entry>
-  <entry>Core</entry>
-  <entry>UPDATE privilege at the table level</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081-05</entry>
-  <entry>Core</entry>
-  <entry>UPDATE privilege at the column level</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081-06</entry>
-  <entry>Core</entry>
-  <entry>REFERENCES privilege at the table level</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081-07</entry>
-  <entry>Core</entry>
-  <entry>REFERENCES privilege at the column level</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081-08</entry>
-  <entry>Core</entry>
-  <entry>WITH GRANT OPTION</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081-10</entry>
-  <entry>Core</entry>
-  <entry>EXECUTE privilege</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E091</entry>
-  <entry>Core</entry>
-  <entry>Set functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E091-01</entry>
-  <entry>Core</entry>
-  <entry>AVG</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E091-02</entry>
-  <entry>Core</entry>
-  <entry>COUNT</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E091-03</entry>
-  <entry>Core</entry>
-  <entry>MAX</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E091-04</entry>
-  <entry>Core</entry>
-  <entry>MIN</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E091-05</entry>
-  <entry>Core</entry>
-  <entry>SUM</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E091-06</entry>
-  <entry>Core</entry>
-  <entry>ALL quantifier</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E091-07</entry>
-  <entry>Core</entry>
-  <entry>DISTINCT quantifier</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E101</entry>
-  <entry>Core</entry>
-  <entry>Basic data manipulation</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E101-01</entry>
-  <entry>Core</entry>
-  <entry>INSERT statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E101-03</entry>
-  <entry>Core</entry>
-  <entry>Searched UPDATE statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E101-04</entry>
-  <entry>Core</entry>
-  <entry>Searched DELETE statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E111</entry>
-  <entry>Core</entry>
-  <entry>Single row SELECT statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E121</entry>
-  <entry>Core</entry>
-  <entry>Basic cursor support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E121-01</entry>
-  <entry>Core</entry>
-  <entry>DECLARE CURSOR</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E121-02</entry>
-  <entry>Core</entry>
-  <entry>ORDER BY columns need not be in select list</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E121-03</entry>
-  <entry>Core</entry>
-  <entry>Value expressions in ORDER BY clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E121-04</entry>
-  <entry>Core</entry>
-  <entry>OPEN statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E121-06</entry>
-  <entry>Core</entry>
-  <entry>Positioned UPDATE statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E121-07</entry>
-  <entry>Core</entry>
-  <entry>Positioned DELETE statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E121-08</entry>
-  <entry>Core</entry>
-  <entry>CLOSE statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E121-10</entry>
-  <entry>Core</entry>
-  <entry>FETCH statement implicit NEXT</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E121-17</entry>
-  <entry>Core</entry>
-  <entry>WITH HOLD cursors</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E131</entry>
-  <entry>Core</entry>
-  <entry>Null value support (nulls in lieu of values)</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E141</entry>
-  <entry>Core</entry>
-  <entry>Basic integrity constraints</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E141-01</entry>
-  <entry>Core</entry>
-  <entry>NOT NULL constraints</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E141-02</entry>
-  <entry>Core</entry>
-  <entry>UNIQUE constraints of NOT NULL columns</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E141-03</entry>
-  <entry>Core</entry>
-  <entry>PRIMARY KEY constraints</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E141-04</entry>
-  <entry>Core</entry>
-  <entry>Basic FOREIGN KEY constraint with the NO ACTION default for both referential delete action and referential update action</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E141-06</entry>
-  <entry>Core</entry>
-  <entry>CHECK constraints</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E141-07</entry>
-  <entry>Core</entry>
-  <entry>Column defaults</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E141-08</entry>
-  <entry>Core</entry>
-  <entry>NOT NULL inferred on PRIMARY KEY</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E141-10</entry>
-  <entry>Core</entry>
-  <entry>Names in a foreign key can be specified in any order</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E151</entry>
-  <entry>Core</entry>
-  <entry>Transaction support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E151-01</entry>
-  <entry>Core</entry>
-  <entry>COMMIT statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E151-02</entry>
-  <entry>Core</entry>
-  <entry>ROLLBACK statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E152</entry>
-  <entry>Core</entry>
-  <entry>Basic SET TRANSACTION statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E152-01</entry>
-  <entry>Core</entry>
-  <entry>SET TRANSACTION statement: ISOLATION LEVEL SERIALIZABLE clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E152-02</entry>
-  <entry>Core</entry>
-  <entry>SET TRANSACTION statement: READ ONLY and READ WRITE clauses</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E161</entry>
-  <entry>Core</entry>
-  <entry>SQL comments using leading double minus</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E171</entry>
-  <entry>Core</entry>
-  <entry>SQLSTATE support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F021</entry>
-  <entry>Core</entry>
-  <entry>Basic information schema</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F021-01</entry>
-  <entry>Core</entry>
-  <entry>COLUMNS view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F021-02</entry>
-  <entry>Core</entry>
-  <entry>TABLES view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F021-03</entry>
-  <entry>Core</entry>
-  <entry>VIEWS view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F021-04</entry>
-  <entry>Core</entry>
-  <entry>TABLE_CONSTRAINTS view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F021-05</entry>
-  <entry>Core</entry>
-  <entry>REFERENTIAL_CONSTRAINTS view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F021-06</entry>
-  <entry>Core</entry>
-  <entry>CHECK_CONSTRAINTS view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F031</entry>
-  <entry>Core</entry>
-  <entry>Basic schema manipulation</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F031-01</entry>
-  <entry>Core</entry>
-  <entry>CREATE TABLE statement to create persistent base tables</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F031-02</entry>
-  <entry>Core</entry>
-  <entry>CREATE VIEW statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F031-03</entry>
-  <entry>Core</entry>
-  <entry>GRANT statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F031-04</entry>
-  <entry>Core</entry>
-  <entry>ALTER TABLE statement: ADD COLUMN clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F031-13</entry>
-  <entry>Core</entry>
-  <entry>DROP TABLE statement: RESTRICT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F031-16</entry>
-  <entry>Core</entry>
-  <entry>DROP VIEW statement: RESTRICT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F031-19</entry>
-  <entry>Core</entry>
-  <entry>REVOKE statement: RESTRICT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F032</entry>
-  <entry></entry>
-  <entry>CASCADE drop behavior</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F033</entry>
-  <entry></entry>
-  <entry>ALTER TABLE statement: DROP COLUMN clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F034</entry>
-  <entry></entry>
-  <entry>Extended REVOKE statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F034-01</entry>
-  <entry></entry>
-  <entry>REVOKE statement performed by other than the owner of a schema object</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F034-02</entry>
-  <entry></entry>
-  <entry>REVOKE statement: GRANT OPTION FOR clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F034-03</entry>
-  <entry></entry>
-  <entry>REVOKE statement to revoke a privilege that the grantee has WITH GRANT OPTION</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F041</entry>
-  <entry>Core</entry>
-  <entry>Basic joined table</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F041-01</entry>
-  <entry>Core</entry>
-  <entry>Inner join (but not necessarily the INNER keyword)</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F041-02</entry>
-  <entry>Core</entry>
-  <entry>INNER keyword</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F041-03</entry>
-  <entry>Core</entry>
-  <entry>LEFT OUTER JOIN</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F041-04</entry>
-  <entry>Core</entry>
-  <entry>RIGHT OUTER JOIN</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F041-05</entry>
-  <entry>Core</entry>
-  <entry>Outer joins can be nested</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F041-07</entry>
-  <entry>Core</entry>
-  <entry>The inner table in a left or right outer join can also be used in an inner join</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F041-08</entry>
-  <entry>Core</entry>
-  <entry>All comparison operators are supported (rather than just =)</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F051</entry>
-  <entry>Core</entry>
-  <entry>Basic date and time</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F051-01</entry>
-  <entry>Core</entry>
-  <entry>DATE data type (including support of DATE literal)</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F051-02</entry>
-  <entry>Core</entry>
-  <entry>TIME data type (including support of TIME literal) with fractional seconds precision of at least 0</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F051-03</entry>
-  <entry>Core</entry>
-  <entry>TIMESTAMP data type (including support of TIMESTAMP literal) with fractional seconds precision of at least 0 and 6</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F051-04</entry>
-  <entry>Core</entry>
-  <entry>Comparison predicate on DATE, TIME, and TIMESTAMP data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F051-05</entry>
-  <entry>Core</entry>
-  <entry>Explicit CAST between datetime types and character string types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F051-06</entry>
-  <entry>Core</entry>
-  <entry>CURRENT_DATE</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F051-07</entry>
-  <entry>Core</entry>
-  <entry>LOCALTIME</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F051-08</entry>
-  <entry>Core</entry>
-  <entry>LOCALTIMESTAMP</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F052</entry>
-  <entry>Enhanced datetime facilities</entry>
-  <entry>Intervals and datetime arithmetic</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F053</entry>
-  <entry></entry>
-  <entry>OVERLAPS predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F081</entry>
-  <entry>Core</entry>
-  <entry>UNION and EXCEPT in views</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F111</entry>
-  <entry></entry>
-  <entry>Isolation levels other than SERIALIZABLE</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F111-01</entry>
-  <entry></entry>
-  <entry>READ UNCOMMITTED isolation level</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F111-02</entry>
-  <entry></entry>
-  <entry>READ COMMITTED isolation level</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F111-03</entry>
-  <entry></entry>
-  <entry>REPEATABLE READ isolation level</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F131</entry>
-  <entry>Core</entry>
-  <entry>Grouped operations</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F131-01</entry>
-  <entry>Core</entry>
-  <entry>WHERE, GROUP BY, and HAVING clauses supported in queries with grouped views</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F131-02</entry>
-  <entry>Core</entry>
-  <entry>Multiple tables supported in queries with grouped views</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F131-03</entry>
-  <entry>Core</entry>
-  <entry>Set functions supported in queries with grouped views</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F131-04</entry>
-  <entry>Core</entry>
-  <entry>Subqueries with GROUP BY and HAVING clauses and grouped views</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F131-05</entry>
-  <entry>Core</entry>
-  <entry>Single row SELECT with GROUP BY and HAVING clauses and grouped views</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F171</entry>
-  <entry></entry>
-  <entry>Multiple schemas per user</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F191</entry>
-  <entry>Enhanced integrity management</entry>
-  <entry>Referential delete actions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F200</entry>
-  <entry></entry>
-  <entry>TRUNCATE TABLE statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F201</entry>
-  <entry>Core</entry>
-  <entry>CAST function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F221</entry>
-  <entry>Core</entry>
-  <entry>Explicit defaults</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F222</entry>
-  <entry></entry>
-  <entry>INSERT statement: DEFAULT VALUES clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F231</entry>
-  <entry></entry>
-  <entry>Privilege tables</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F231-01</entry>
-  <entry></entry>
-  <entry>TABLE_PRIVILEGES view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F231-02</entry>
-  <entry></entry>
-  <entry>COLUMN_PRIVILEGES view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F231-03</entry>
-  <entry></entry>
-  <entry>USAGE_PRIVILEGES view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F251</entry>
-  <entry></entry>
-  <entry>Domain support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F261</entry>
-  <entry>Core</entry>
-  <entry>CASE expression</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F261-01</entry>
-  <entry>Core</entry>
-  <entry>Simple CASE</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F261-02</entry>
-  <entry>Core</entry>
-  <entry>Searched CASE</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F261-03</entry>
-  <entry>Core</entry>
-  <entry>NULLIF</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F261-04</entry>
-  <entry>Core</entry>
-  <entry>COALESCE</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F271</entry>
-  <entry></entry>
-  <entry>Compound character literals</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F281</entry>
-  <entry></entry>
-  <entry>LIKE enhancements</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F302</entry>
-  <entry></entry>
-  <entry>INTERSECT table operator</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F302-01</entry>
-  <entry></entry>
-  <entry>INTERSECT DISTINCT table operator</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F302-02</entry>
-  <entry></entry>
-  <entry>INTERSECT ALL table operator</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F304</entry>
-  <entry></entry>
-  <entry>EXCEPT ALL table operator</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F311-01</entry>
-  <entry>Core</entry>
-  <entry>CREATE SCHEMA</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F311-02</entry>
-  <entry>Core</entry>
-  <entry>CREATE TABLE for persistent base tables</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F311-03</entry>
-  <entry>Core</entry>
-  <entry>CREATE VIEW</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F311-05</entry>
-  <entry>Core</entry>
-  <entry>GRANT statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F321</entry>
-  <entry></entry>
-  <entry>User authorization</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F361</entry>
-  <entry></entry>
-  <entry>Subprogram support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F381</entry>
-  <entry></entry>
-  <entry>Extended schema manipulation</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F381-01</entry>
-  <entry></entry>
-  <entry>ALTER TABLE statement: ALTER COLUMN clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F381-02</entry>
-  <entry></entry>
-  <entry>ALTER TABLE statement: ADD CONSTRAINT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F381-03</entry>
-  <entry></entry>
-  <entry>ALTER TABLE statement: DROP CONSTRAINT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F382</entry>
-  <entry></entry>
-  <entry>Alter column data type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F391</entry>
-  <entry></entry>
-  <entry>Long identifiers</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F392</entry>
-  <entry></entry>
-  <entry>Unicode escapes in identifiers</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F393</entry>
-  <entry></entry>
-  <entry>Unicode escapes in literals</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F401</entry>
-  <entry></entry>
-  <entry>Extended joined table</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F401-01</entry>
-  <entry></entry>
-  <entry>NATURAL JOIN</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F401-02</entry>
-  <entry></entry>
-  <entry>FULL OUTER JOIN</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F401-04</entry>
-  <entry></entry>
-  <entry>CROSS JOIN</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F402</entry>
-  <entry></entry>
-  <entry>Named column joins for LOBs, arrays, and multisets</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F411</entry>
-  <entry>Enhanced datetime facilities</entry>
-  <entry>Time zone specification</entry>
-  <entry>differences regarding literal interpretation</entry>
- </row>
- <row>
-  <entry>F421</entry>
-  <entry></entry>
-  <entry>National character</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F431</entry>
-  <entry></entry>
-  <entry>Read-only scrollable cursors</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F431-01</entry>
-  <entry></entry>
-  <entry>FETCH with explicit NEXT</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F431-02</entry>
-  <entry></entry>
-  <entry>FETCH FIRST</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F431-03</entry>
-  <entry></entry>
-  <entry>FETCH LAST</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F431-04</entry>
-  <entry></entry>
-  <entry>FETCH PRIOR</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F431-05</entry>
-  <entry></entry>
-  <entry>FETCH ABSOLUTE</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F431-06</entry>
-  <entry></entry>
-  <entry>FETCH RELATIVE</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F441</entry>
-  <entry></entry>
-  <entry>Extended set function support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F442</entry>
-  <entry></entry>
-  <entry>Mixed column references in set functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F471</entry>
-  <entry>Core</entry>
-  <entry>Scalar subquery values</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F481</entry>
-  <entry>Core</entry>
-  <entry>Expanded NULL predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F491</entry>
-  <entry>Enhanced integrity management</entry>
-  <entry>Constraint management</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F501</entry>
-  <entry>Core</entry>
-  <entry>Features and conformance views</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F501-01</entry>
-  <entry>Core</entry>
-  <entry>SQL_FEATURES view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F501-02</entry>
-  <entry>Core</entry>
-  <entry>SQL_SIZING view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F501-03</entry>
-  <entry>Core</entry>
-  <entry>SQL_LANGUAGES view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F502</entry>
-  <entry></entry>
-  <entry>Enhanced documentation tables</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F502-01</entry>
-  <entry></entry>
-  <entry>SQL_SIZING_PROFILES view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F502-02</entry>
-  <entry></entry>
-  <entry>SQL_IMPLEMENTATION_INFO view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F502-03</entry>
-  <entry></entry>
-  <entry>SQL_PACKAGES view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F531</entry>
-  <entry></entry>
-  <entry>Temporary tables</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F555</entry>
-  <entry>Enhanced datetime facilities</entry>
-  <entry>Enhanced seconds precision</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F561</entry>
-  <entry></entry>
-  <entry>Full value expressions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F571</entry>
-  <entry></entry>
-  <entry>Truth value tests</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F591</entry>
-  <entry></entry>
-  <entry>Derived tables</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F611</entry>
-  <entry></entry>
-  <entry>Indicator data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F651</entry>
-  <entry></entry>
-  <entry>Catalog name qualifiers</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F661</entry>
-  <entry></entry>
-  <entry>Simple tables</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F672</entry>
-  <entry></entry>
-  <entry>Retrospective check constraints</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F701</entry>
-  <entry>Enhanced integrity management</entry>
-  <entry>Referential update actions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F711</entry>
-  <entry></entry>
-  <entry>ALTER domain</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F731</entry>
-  <entry></entry>
-  <entry>INSERT column privileges</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F761</entry>
-  <entry></entry>
-  <entry>Session management</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F762</entry>
-  <entry></entry>
-  <entry>CURRENT_CATALOG</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F763</entry>
-  <entry></entry>
-  <entry>CURRENT_SCHEMA</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F771</entry>
-  <entry></entry>
-  <entry>Connection management</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F781</entry>
-  <entry></entry>
-  <entry>Self-referencing operations</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F791</entry>
-  <entry></entry>
-  <entry>Insensitive cursors</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F801</entry>
-  <entry></entry>
-  <entry>Full set function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F850</entry>
-  <entry></entry>
-  <entry>Top-level &lt;order by clause&gt; in &lt;query expression&gt;</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F851</entry>
-  <entry></entry>
-  <entry>&lt;order by clause&gt; in subqueries</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F852</entry>
-  <entry></entry>
-  <entry>Top-level &lt;order by clause&gt; in views</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F855</entry>
-  <entry></entry>
-  <entry>Nested &lt;order by clause&gt; in &lt;query expression&gt;</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F856</entry>
-  <entry></entry>
-  <entry>Nested &lt;fetch first clause&gt; in &lt;query expression&gt;</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F857</entry>
-  <entry></entry>
-  <entry>Top-level &lt;fetch first clause&gt; in &lt;query expression&gt;</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F858</entry>
-  <entry></entry>
-  <entry>&lt;fetch first clause&gt; in subqueries</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F859</entry>
-  <entry></entry>
-  <entry>Top-level &lt;fetch first clause&gt; in views</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F860</entry>
-  <entry></entry>
-  <entry>&lt;fetch first row count&gt; in &lt;fetch first clause&gt;</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F861</entry>
-  <entry></entry>
-  <entry>Top-level &lt;result offset clause&gt; in &lt;query expression&gt;</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F862</entry>
-  <entry></entry>
-  <entry>&lt;result offset clause&gt; in subqueries</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F863</entry>
-  <entry></entry>
-  <entry>Nested &lt;result offset clause&gt; in &lt;query expression&gt;</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F864</entry>
-  <entry></entry>
-  <entry>Top-level &lt;result offset clause&gt; in views</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F865</entry>
-  <entry></entry>
-  <entry>&lt;offset row count&gt; in &lt;result offset clause&gt;</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S071</entry>
-  <entry>Enhanced object support</entry>
-  <entry>SQL paths in function and type name resolution</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S092</entry>
-  <entry></entry>
-  <entry>Arrays of user-defined types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S095</entry>
-  <entry></entry>
-  <entry>Array constructors by query</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S096</entry>
-  <entry></entry>
-  <entry>Optional array bounds</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S098</entry>
-  <entry></entry>
-  <entry>ARRAY_AGG</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S111</entry>
-  <entry>Enhanced object support</entry>
-  <entry>ONLY in query expressions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S201</entry>
-  <entry></entry>
-  <entry>SQL-invoked routines on arrays</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S201-01</entry>
-  <entry></entry>
-  <entry>Array parameters</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S201-02</entry>
-  <entry></entry>
-  <entry>Array as result type of functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S211</entry>
-  <entry>Enhanced object support</entry>
-  <entry>User-defined cast functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T031</entry>
-  <entry></entry>
-  <entry>BOOLEAN data type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T071</entry>
-  <entry></entry>
-  <entry>BIGINT data type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T121</entry>
-  <entry></entry>
-  <entry>WITH (excluding RECURSIVE) in query expression</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T122</entry>
-  <entry></entry>
-  <entry>WITH (excluding RECURSIVE) in subquery</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T131</entry>
-  <entry></entry>
-  <entry>Recursive query</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T132</entry>
-  <entry></entry>
-  <entry>Recursive query in subquery</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T141</entry>
-  <entry></entry>
-  <entry>SIMILAR predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T151</entry>
-  <entry></entry>
-  <entry>DISTINCT predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T152</entry>
-  <entry></entry>
-  <entry>DISTINCT predicate with negation</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T171</entry>
-  <entry></entry>
-  <entry>LIKE clause in table definition</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T172</entry>
-  <entry></entry>
-  <entry>AS subquery clause in table definition</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T173</entry>
-  <entry></entry>
-  <entry>Extended LIKE clause in table definition</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T191</entry>
-  <entry>Enhanced integrity management</entry>
-  <entry>Referential action RESTRICT</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T201</entry>
-  <entry>Enhanced integrity management</entry>
-  <entry>Comparable data types for referential constraints</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T211-01</entry>
-  <entry>Active database, Enhanced integrity management</entry>
-  <entry>Triggers activated on UPDATE, INSERT, or DELETE of one base table</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T211-02</entry>
-  <entry>Active database, Enhanced integrity management</entry>
-  <entry>BEFORE triggers</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T211-03</entry>
-  <entry>Active database, Enhanced integrity management</entry>
-  <entry>AFTER triggers</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T211-04</entry>
-  <entry>Active database, Enhanced integrity management</entry>
-  <entry>FOR EACH ROW triggers</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T211-05</entry>
-  <entry>Active database, Enhanced integrity management</entry>
-  <entry>Ability to specify a search condition that must be true before the trigger is invoked</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T211-07</entry>
-  <entry>Active database, Enhanced integrity management</entry>
-  <entry>TRIGGER privilege</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T212</entry>
-  <entry>Enhanced integrity management</entry>
-  <entry>Enhanced trigger capability</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T231</entry>
-  <entry></entry>
-  <entry>Sensitive cursors</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T241</entry>
-  <entry></entry>
-  <entry>START TRANSACTION statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T271</entry>
-  <entry></entry>
-  <entry>Savepoints</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T281</entry>
-  <entry></entry>
-  <entry>SELECT privilege with column granularity</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T312</entry>
-  <entry></entry>
-  <entry>OVERLAY function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T321-01</entry>
-  <entry>Core</entry>
-  <entry>User-defined functions with no overloading</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T321-03</entry>
-  <entry>Core</entry>
-  <entry>Function invocation</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T321-06</entry>
-  <entry>Core</entry>
-  <entry>ROUTINES view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T321-07</entry>
-  <entry>Core</entry>
-  <entry>PARAMETERS view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T322</entry>
-  <entry>PSM</entry>
-  <entry>Overloading of SQL-invoked functions and procedures</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T323</entry>
-  <entry></entry>
-  <entry>Explicit security for external routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T351</entry>
-  <entry></entry>
-  <entry>Bracketed SQL comments (/*...*/ comments)</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T441</entry>
-  <entry></entry>
-  <entry>ABS and MOD functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T461</entry>
-  <entry></entry>
-  <entry>Symmetric BETWEEN predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T501</entry>
-  <entry></entry>
-  <entry>Enhanced EXISTS predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T551</entry>
-  <entry></entry>
-  <entry>Optional key words for default syntax</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T581</entry>
-  <entry></entry>
-  <entry>Regular expression substring function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T591</entry>
-  <entry></entry>
-  <entry>UNIQUE constraints of possibly null columns</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T614</entry>
-  <entry></entry>
-  <entry>NTILE function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T615</entry>
-  <entry></entry>
-  <entry>LEAD and LAG functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T617</entry>
-  <entry></entry>
-  <entry>FIRST_VALUE and LAST_VALUE function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T621</entry>
-  <entry></entry>
-  <entry>Enhanced numeric functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T631</entry>
-  <entry>Core</entry>
-  <entry>IN predicate with one list element</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T651</entry>
-  <entry></entry>
-  <entry>SQL-schema statements in SQL routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T655</entry>
-  <entry></entry>
-  <entry>Cyclically dependent routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X010</entry>
-  <entry></entry>
-  <entry>XML type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X011</entry>
-  <entry></entry>
-  <entry>Arrays of XML type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X016</entry>
-  <entry></entry>
-  <entry>Persistent XML values</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X020</entry>
-  <entry></entry>
-  <entry>XMLConcat</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X031</entry>
-  <entry></entry>
-  <entry>XMLElement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X032</entry>
-  <entry></entry>
-  <entry>XMLForest</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X034</entry>
-  <entry></entry>
-  <entry>XMLAgg</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X035</entry>
-  <entry></entry>
-  <entry>XMLAgg: ORDER BY option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X036</entry>
-  <entry></entry>
-  <entry>XMLComment</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X037</entry>
-  <entry></entry>
-  <entry>XMLPI</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X040</entry>
-  <entry></entry>
-  <entry>Basic table mapping</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X041</entry>
-  <entry></entry>
-  <entry>Basic table mapping: nulls absent</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X042</entry>
-  <entry></entry>
-  <entry>Basic table mapping: null as nil</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X043</entry>
-  <entry></entry>
-  <entry>Basic table mapping: table as forest</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X044</entry>
-  <entry></entry>
-  <entry>Basic table mapping: table as element</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X045</entry>
-  <entry></entry>
-  <entry>Basic table mapping: with target namespace</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X046</entry>
-  <entry></entry>
-  <entry>Basic table mapping: data mapping</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X047</entry>
-  <entry></entry>
-  <entry>Basic table mapping: metadata mapping</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X048</entry>
-  <entry></entry>
-  <entry>Basic table mapping: base64 encoding of binary strings</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X049</entry>
-  <entry></entry>
-  <entry>Basic table mapping: hex encoding of binary strings</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X050</entry>
-  <entry></entry>
-  <entry>Advanced table mapping</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X051</entry>
-  <entry></entry>
-  <entry>Advanced table mapping: nulls absent</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X052</entry>
-  <entry></entry>
-  <entry>Advanced table mapping: null as nil</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X053</entry>
-  <entry></entry>
-  <entry>Advanced table mapping: table as forest</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X054</entry>
-  <entry></entry>
-  <entry>Advanced table mapping: table as element</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X055</entry>
-  <entry></entry>
-  <entry>Advanced table mapping: target namespace</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X056</entry>
-  <entry></entry>
-  <entry>Advanced table mapping: data mapping</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X057</entry>
-  <entry></entry>
-  <entry>Advanced table mapping: metadata mapping</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X058</entry>
-  <entry></entry>
-  <entry>Advanced table mapping: base64 encoding of binary strings</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X059</entry>
-  <entry></entry>
-  <entry>Advanced table mapping: hex encoding of binary strings</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X060</entry>
-  <entry></entry>
-  <entry>XMLParse: Character string input and CONTENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X061</entry>
-  <entry></entry>
-  <entry>XMLParse: Character string input and DOCUMENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X070</entry>
-  <entry></entry>
-  <entry>XMLSerialize: Character string serialization and CONTENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X071</entry>
-  <entry></entry>
-  <entry>XMLSerialize: Character string serialization and DOCUMENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X072</entry>
-  <entry></entry>
-  <entry>XMLSerialize: Character string serialization</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X090</entry>
-  <entry></entry>
-  <entry>XML document predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X120</entry>
-  <entry></entry>
-  <entry>XML parameters in SQL routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X121</entry>
-  <entry></entry>
-  <entry>XML parameters in external routines</entry>
-  <entry></entry>
- </row>
-</tbody>
diff --git a/doc-xc/src/sgml/features-unsupported.sgmlin b/doc-xc/src/sgml/features-unsupported.sgmlin
deleted file mode 100644
index 671fbec9df..0000000000
--- a/doc-xc/src/sgml/features-unsupported.sgmlin
+++ /dev/null
@@ -1,1826 +0,0 @@
-<tbody>
- <row>
-  <entry>B011</entry>
-  <entry></entry>
-  <entry>Embedded Ada</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B013</entry>
-  <entry></entry>
-  <entry>Embedded COBOL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B014</entry>
-  <entry></entry>
-  <entry>Embedded Fortran</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B015</entry>
-  <entry></entry>
-  <entry>Embedded MUMPS</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B016</entry>
-  <entry></entry>
-  <entry>Embedded Pascal</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B017</entry>
-  <entry></entry>
-  <entry>Embedded PL/I</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B031</entry>
-  <entry></entry>
-  <entry>Basic dynamic SQL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B032</entry>
-  <entry></entry>
-  <entry>Extended dynamic SQL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B032-01</entry>
-  <entry></entry>
-  <entry>&lt;describe input statement&gt;</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B033</entry>
-  <entry></entry>
-  <entry>Untyped SQL-invoked function arguments</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B034</entry>
-  <entry></entry>
-  <entry>Dynamic specification of cursor attributes</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B035</entry>
-  <entry></entry>
-  <entry>Non-extended descriptor names</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B041</entry>
-  <entry></entry>
-  <entry>Extensions to embedded SQL exception declarations</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B051</entry>
-  <entry></entry>
-  <entry>Enhanced execution rights</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B111</entry>
-  <entry></entry>
-  <entry>Module language Ada</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B112</entry>
-  <entry></entry>
-  <entry>Module language C</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B113</entry>
-  <entry></entry>
-  <entry>Module language COBOL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B114</entry>
-  <entry></entry>
-  <entry>Module language Fortran</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B115</entry>
-  <entry></entry>
-  <entry>Module language MUMPS</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B116</entry>
-  <entry></entry>
-  <entry>Module language Pascal</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B117</entry>
-  <entry></entry>
-  <entry>Module language PL/I</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B121</entry>
-  <entry></entry>
-  <entry>Routine language Ada</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B122</entry>
-  <entry></entry>
-  <entry>Routine language C</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B123</entry>
-  <entry></entry>
-  <entry>Routine language COBOL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B124</entry>
-  <entry></entry>
-  <entry>Routine language Fortran</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B125</entry>
-  <entry></entry>
-  <entry>Routine language MUMPS</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B126</entry>
-  <entry></entry>
-  <entry>Routine language Pascal</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B127</entry>
-  <entry></entry>
-  <entry>Routine language PL/I</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>B128</entry>
-  <entry></entry>
-  <entry>Routine language SQL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081</entry>
-  <entry>Core</entry>
-  <entry>Basic Privileges</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E081-09</entry>
-  <entry>Core</entry>
-  <entry>USAGE privilege</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E153</entry>
-  <entry>Core</entry>
-  <entry>Updatable queries with subqueries</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>E182</entry>
-  <entry>Core</entry>
-  <entry>Module language</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F121</entry>
-  <entry></entry>
-  <entry>Basic diagnostics management</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F121-01</entry>
-  <entry></entry>
-  <entry>GET DIAGNOSTICS statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F121-02</entry>
-  <entry></entry>
-  <entry>SET TRANSACTION statement: DIAGNOSTICS SIZE clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F122</entry>
-  <entry></entry>
-  <entry>Enhanced diagnostics management</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F123</entry>
-  <entry></entry>
-  <entry>All diagnostics</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F181</entry>
-  <entry>Core</entry>
-  <entry>Multiple module support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F202</entry>
-  <entry></entry>
-  <entry>TRUNCATE TABLE: identity column restart option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F262</entry>
-  <entry></entry>
-  <entry>Extended CASE expression</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F263</entry>
-  <entry></entry>
-  <entry>Comma-separated predicates in simple CASE expression</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F291</entry>
-  <entry></entry>
-  <entry>UNIQUE predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F301</entry>
-  <entry></entry>
-  <entry>CORRESPONDING in query expressions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F311</entry>
-  <entry>Core</entry>
-  <entry>Schema definition statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F311-04</entry>
-  <entry>Core</entry>
-  <entry>CREATE VIEW: WITH CHECK OPTION</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F312</entry>
-  <entry></entry>
-  <entry>MERGE statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F313</entry>
-  <entry></entry>
-  <entry>Enhanced MERGE statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F341</entry>
-  <entry></entry>
-  <entry>Usage tables</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F394</entry>
-  <entry></entry>
-  <entry>Optional normal form specification</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F403</entry>
-  <entry></entry>
-  <entry>Partitioned joined tables</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F451</entry>
-  <entry></entry>
-  <entry>Character set definition</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F461</entry>
-  <entry></entry>
-  <entry>Named character sets</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F521</entry>
-  <entry>Enhanced integrity management</entry>
-  <entry>Assertions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F641</entry>
-  <entry></entry>
-  <entry>Row and table constructors</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F671</entry>
-  <entry>Enhanced integrity management</entry>
-  <entry>Subqueries in CHECK</entry>
-  <entry>intentionally omitted</entry>
- </row>
- <row>
-  <entry>F690</entry>
-  <entry></entry>
-  <entry>Collation support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F692</entry>
-  <entry></entry>
-  <entry>Enhanced collation support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F693</entry>
-  <entry></entry>
-  <entry>SQL-session and client module collations</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F695</entry>
-  <entry></entry>
-  <entry>Translation support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F696</entry>
-  <entry></entry>
-  <entry>Additional translation documentation</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F721</entry>
-  <entry></entry>
-  <entry>Deferrable constraints</entry>
-  <entry>foreign and unique keys only</entry>
- </row>
- <row>
-  <entry>F741</entry>
-  <entry></entry>
-  <entry>Referential MATCH types</entry>
-  <entry>no partial match yet</entry>
- </row>
- <row>
-  <entry>F751</entry>
-  <entry></entry>
-  <entry>View CHECK enhancements</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F812</entry>
-  <entry>Core</entry>
-  <entry>Basic flagging</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F813</entry>
-  <entry></entry>
-  <entry>Extended flagging</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F821</entry>
-  <entry></entry>
-  <entry>Local table references</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F831</entry>
-  <entry></entry>
-  <entry>Full cursor update</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F831-01</entry>
-  <entry></entry>
-  <entry>Updatable scrollable cursors</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F831-02</entry>
-  <entry></entry>
-  <entry>Updatable ordered cursors</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F841</entry>
-  <entry></entry>
-  <entry>LIKE_REGEX predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F842</entry>
-  <entry></entry>
-  <entry>OCCURENCES_REGEX function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F843</entry>
-  <entry></entry>
-  <entry>POSITION_REGEX function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F844</entry>
-  <entry></entry>
-  <entry>SUBSTRING_REGEX function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F845</entry>
-  <entry></entry>
-  <entry>TRANSLATE_REGEX function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F846</entry>
-  <entry></entry>
-  <entry>Octet support in regular expression operators</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>F847</entry>
-  <entry></entry>
-  <entry>Nonconstant regular expressions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S011</entry>
-  <entry>Core</entry>
-  <entry>Distinct data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S011-01</entry>
-  <entry>Core</entry>
-  <entry>USER_DEFINED_TYPES view</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S023</entry>
-  <entry>Basic object support</entry>
-  <entry>Basic structured types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S024</entry>
-  <entry>Enhanced object support</entry>
-  <entry>Enhanced structured types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S025</entry>
-  <entry></entry>
-  <entry>Final structured types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S026</entry>
-  <entry></entry>
-  <entry>Self-referencing structured types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S027</entry>
-  <entry></entry>
-  <entry>Create method by specific method name</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S028</entry>
-  <entry></entry>
-  <entry>Permutable UDT options list</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S041</entry>
-  <entry>Basic object support</entry>
-  <entry>Basic reference types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S043</entry>
-  <entry>Enhanced object support</entry>
-  <entry>Enhanced reference types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S051</entry>
-  <entry>Basic object support</entry>
-  <entry>Create table of type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S081</entry>
-  <entry>Enhanced object support</entry>
-  <entry>Subtables</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S091</entry>
-  <entry></entry>
-  <entry>Basic array support</entry>
-  <entry>partially supported</entry>
- </row>
- <row>
-  <entry>S091-01</entry>
-  <entry></entry>
-  <entry>Arrays of built-in data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S091-02</entry>
-  <entry></entry>
-  <entry>Arrays of distinct types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S091-03</entry>
-  <entry></entry>
-  <entry>Array expressions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S094</entry>
-  <entry></entry>
-  <entry>Arrays of reference types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S097</entry>
-  <entry></entry>
-  <entry>Array element assignment</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S151</entry>
-  <entry>Basic object support</entry>
-  <entry>Type predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S161</entry>
-  <entry>Enhanced object support</entry>
-  <entry>Subtype treatment</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S162</entry>
-  <entry></entry>
-  <entry>Subtype treatment for references</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S202</entry>
-  <entry></entry>
-  <entry>SQL-invoked routines on multisets</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S231</entry>
-  <entry>Enhanced object support</entry>
-  <entry>Structured type locators</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S232</entry>
-  <entry></entry>
-  <entry>Array locators</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S233</entry>
-  <entry></entry>
-  <entry>Multiset locators</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S241</entry>
-  <entry></entry>
-  <entry>Transform functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S242</entry>
-  <entry></entry>
-  <entry>Alter transform statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S251</entry>
-  <entry></entry>
-  <entry>User-defined orderings</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S261</entry>
-  <entry></entry>
-  <entry>Specific type method</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S271</entry>
-  <entry></entry>
-  <entry>Basic multiset support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S272</entry>
-  <entry></entry>
-  <entry>Multisets of user-defined types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S274</entry>
-  <entry></entry>
-  <entry>Multisets of reference types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S275</entry>
-  <entry></entry>
-  <entry>Advanced multiset support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S281</entry>
-  <entry></entry>
-  <entry>Nested collection types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S291</entry>
-  <entry></entry>
-  <entry>Unique constraint on entire row</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S301</entry>
-  <entry></entry>
-  <entry>Enhanced UNNEST</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S401</entry>
-  <entry></entry>
-  <entry>Distinct types based on array types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S402</entry>
-  <entry></entry>
-  <entry>Distinct types based on distinct types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S403</entry>
-  <entry></entry>
-  <entry>MAX_CARDINALITY</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>S404</entry>
-  <entry></entry>
-  <entry>TRIM_ARRAY</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T011</entry>
-  <entry></entry>
-  <entry>Timestamp in Information Schema</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T021</entry>
-  <entry></entry>
-  <entry>BINARY and VARBINARY data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T022</entry>
-  <entry></entry>
-  <entry>Advanced support for BINARY and VARBINARY data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T023</entry>
-  <entry></entry>
-  <entry>Compound binary literal</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T024</entry>
-  <entry></entry>
-  <entry>Spaces in binary literals</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T041</entry>
-  <entry>Basic object support</entry>
-  <entry>Basic LOB data type support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T041-01</entry>
-  <entry>Basic object support</entry>
-  <entry>BLOB data type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T041-02</entry>
-  <entry>Basic object support</entry>
-  <entry>CLOB data type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T041-03</entry>
-  <entry>Basic object support</entry>
-  <entry>POSITION, LENGTH, LOWER, TRIM, UPPER, and SUBSTRING functions for LOB data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T041-04</entry>
-  <entry>Basic object support</entry>
-  <entry>Concatenation of LOB data types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T041-05</entry>
-  <entry>Basic object support</entry>
-  <entry>LOB locator: non-holdable</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T042</entry>
-  <entry></entry>
-  <entry>Extended LOB data type support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T043</entry>
-  <entry></entry>
-  <entry>Multiplier T</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T044</entry>
-  <entry></entry>
-  <entry>Multiplier P</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T051</entry>
-  <entry></entry>
-  <entry>Row types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T052</entry>
-  <entry></entry>
-  <entry>MAX and MIN for row types</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T053</entry>
-  <entry></entry>
-  <entry>Explicit aliases for all-fields reference</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T061</entry>
-  <entry></entry>
-  <entry>UCS support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T101</entry>
-  <entry></entry>
-  <entry>Enhanced nullability determiniation</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T111</entry>
-  <entry></entry>
-  <entry>Updatable joins, unions, and columns</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T174</entry>
-  <entry></entry>
-  <entry>Identity columns</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T175</entry>
-  <entry></entry>
-  <entry>Generated columns</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T176</entry>
-  <entry></entry>
-  <entry>Sequence generator support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T177</entry>
-  <entry></entry>
-  <entry>Sequence generator support: simple restart option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T178</entry>
-  <entry></entry>
-  <entry>Identity columns:  simple restart option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T211</entry>
-  <entry>Active database, Enhanced integrity management</entry>
-  <entry>Basic trigger capability</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T211-06</entry>
-  <entry>Active database, Enhanced integrity management</entry>
-  <entry>Support for run-time rules for the interaction of triggers and constraints</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T211-08</entry>
-  <entry>Active database, Enhanced integrity management</entry>
-  <entry>Multiple triggers for the same event are executed in the order in which they were created in the catalog</entry>
-  <entry>intentionally omitted</entry>
- </row>
- <row>
-  <entry>T213</entry>
-  <entry></entry>
-  <entry>INSTEAD OF triggers</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T251</entry>
-  <entry></entry>
-  <entry>SET TRANSACTION statement: LOCAL option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T261</entry>
-  <entry></entry>
-  <entry>Chained transactions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T272</entry>
-  <entry></entry>
-  <entry>Enhanced savepoint management</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T285</entry>
-  <entry></entry>
-  <entry>Enhanced derived column names</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T301</entry>
-  <entry></entry>
-  <entry>Functional dependencies</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T321</entry>
-  <entry>Core</entry>
-  <entry>Basic SQL-invoked routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T321-02</entry>
-  <entry>Core</entry>
-  <entry>User-defined stored procedures with no overloading</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T321-04</entry>
-  <entry>Core</entry>
-  <entry>CALL statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T321-05</entry>
-  <entry>Core</entry>
-  <entry>RETURN statement</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T324</entry>
-  <entry></entry>
-  <entry>Explicit security for SQL routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T325</entry>
-  <entry></entry>
-  <entry>Qualified SQL parameter references</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T326</entry>
-  <entry></entry>
-  <entry>Table functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T331</entry>
-  <entry></entry>
-  <entry>Basic roles</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T332</entry>
-  <entry></entry>
-  <entry>Extended roles</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T431</entry>
-  <entry>OLAP</entry>
-  <entry>Extended grouping capabilities</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T432</entry>
-  <entry></entry>
-  <entry>Nested and concatenated GROUPING SETS</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T433</entry>
-  <entry></entry>
-  <entry>Multiargument GROUPING function</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T434</entry>
-  <entry></entry>
-  <entry>GROUP BY DISTINCT</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T471</entry>
-  <entry></entry>
-  <entry>Result sets return value</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T491</entry>
-  <entry></entry>
-  <entry>LATERAL derived table</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T511</entry>
-  <entry></entry>
-  <entry>Transaction counts</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T541</entry>
-  <entry></entry>
-  <entry>Updatable table references</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T561</entry>
-  <entry></entry>
-  <entry>Holdable locators</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T571</entry>
-  <entry></entry>
-  <entry>Array-returning external SQL-invoked functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T572</entry>
-  <entry></entry>
-  <entry>Multiset-returning external SQL-invoked functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T601</entry>
-  <entry></entry>
-  <entry>Local cursor references</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T611</entry>
-  <entry>OLAP</entry>
-  <entry>Elementary OLAP operations</entry>
-  <entry>most forms supported</entry>
- </row>
- <row>
-  <entry>T612</entry>
-  <entry></entry>
-  <entry>Advanced OLAP operations</entry>
-  <entry>some forms supported</entry>
- </row>
- <row>
-  <entry>T613</entry>
-  <entry></entry>
-  <entry>Sampling</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T616</entry>
-  <entry></entry>
-  <entry>Null treatment option for LEAD and LAG functions</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T618</entry>
-  <entry></entry>
-  <entry>NTH_VALUE function</entry>
-  <entry>function exists, but some options missing</entry>
- </row>
- <row>
-  <entry>T641</entry>
-  <entry></entry>
-  <entry>Multiple column assignment</entry>
-  <entry>only some syntax variants supported</entry>
- </row>
- <row>
-  <entry>T652</entry>
-  <entry></entry>
-  <entry>SQL-dynamic statements in SQL routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T653</entry>
-  <entry></entry>
-  <entry>SQL-schema statements in external routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>T654</entry>
-  <entry></entry>
-  <entry>SQL-dynamic statements in external routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M001</entry>
-  <entry></entry>
-  <entry>Datalinks</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M002</entry>
-  <entry></entry>
-  <entry>Datalinks via SQL/CLI</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M003</entry>
-  <entry></entry>
-  <entry>Datalinks via Embedded SQL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M004</entry>
-  <entry></entry>
-  <entry>Foreign data support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M005</entry>
-  <entry></entry>
-  <entry>Foreign schema support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M006</entry>
-  <entry></entry>
-  <entry>GetSQLString routine</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M007</entry>
-  <entry></entry>
-  <entry>TransmitRequest</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M009</entry>
-  <entry></entry>
-  <entry>GetOpts and GetStatistics routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M010</entry>
-  <entry></entry>
-  <entry>Foreign data wrapper support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M011</entry>
-  <entry></entry>
-  <entry>Datalinks via Ada</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M012</entry>
-  <entry></entry>
-  <entry>Datalinks via C</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M013</entry>
-  <entry></entry>
-  <entry>Datalinks via COBOL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M014</entry>
-  <entry></entry>
-  <entry>Datalinks via Fortran</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M015</entry>
-  <entry></entry>
-  <entry>Datalinks via M</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M016</entry>
-  <entry></entry>
-  <entry>Datalinks via Pascal</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M017</entry>
-  <entry></entry>
-  <entry>Datalinks via PL/I</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M018</entry>
-  <entry></entry>
-  <entry>Foreign data wrapper interface routines in Ada</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M019</entry>
-  <entry></entry>
-  <entry>Foreign data wrapper interface routines in C</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M020</entry>
-  <entry></entry>
-  <entry>Foreign data wrapper interface routines in COBOL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M021</entry>
-  <entry></entry>
-  <entry>Foreign data wrapper interface routines in Fortran</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M022</entry>
-  <entry></entry>
-  <entry>Foreign data wrapper interface routines in MUMPS</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M023</entry>
-  <entry></entry>
-  <entry>Foreign data wrapper interface routines in Pascal</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M024</entry>
-  <entry></entry>
-  <entry>Foreign data wrapper interface routines in PL/I</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M030</entry>
-  <entry></entry>
-  <entry>SQL-server foreign data support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>M031</entry>
-  <entry></entry>
-  <entry>Foreign data wrapper general routines</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X012</entry>
-  <entry></entry>
-  <entry>Multisets of XML type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X013</entry>
-  <entry></entry>
-  <entry>Distinct types of XML type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X014</entry>
-  <entry></entry>
-  <entry>Attributes of XML type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X015</entry>
-  <entry></entry>
-  <entry>Fields of XML type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X025</entry>
-  <entry></entry>
-  <entry>XMLCast</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X030</entry>
-  <entry></entry>
-  <entry>XMLDocument</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X038</entry>
-  <entry></entry>
-  <entry>XMLText</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X065</entry>
-  <entry></entry>
-  <entry>XMLParse: BLOB input and CONTENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X066</entry>
-  <entry></entry>
-  <entry>XMLParse: BLOB input and DOCUMENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X068</entry>
-  <entry></entry>
-  <entry>XMLSerialize: BOM</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X069</entry>
-  <entry></entry>
-  <entry>XMLSerialize: INDENT</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X073</entry>
-  <entry></entry>
-  <entry>XMLSerialize: BLOB serialization and CONTENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X074</entry>
-  <entry></entry>
-  <entry>XMLSerialize: BLOB serialization and DOCUMENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X075</entry>
-  <entry></entry>
-  <entry>XMLSerialize: BLOB serialization</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X076</entry>
-  <entry></entry>
-  <entry>XMLSerialize: VERSION</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X077</entry>
-  <entry></entry>
-  <entry>XMLSerialize: explicit ENCODING option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X078</entry>
-  <entry></entry>
-  <entry>XMLSerialize: explicit XML declaration</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X080</entry>
-  <entry></entry>
-  <entry>Namespaces in XML publishing</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X081</entry>
-  <entry></entry>
-  <entry>Query-level XML namespace declarations</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X082</entry>
-  <entry></entry>
-  <entry>XML namespace declarations in DML</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X083</entry>
-  <entry></entry>
-  <entry>XML namespace declarations in DDL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X084</entry>
-  <entry></entry>
-  <entry>XML namespace declarations in compound statements</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X085</entry>
-  <entry></entry>
-  <entry>Predefined namespace prefixes</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X086</entry>
-  <entry></entry>
-  <entry>XML namespace declarations in XMLTable</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X091</entry>
-  <entry></entry>
-  <entry>XML content predicate</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X096</entry>
-  <entry></entry>
-  <entry>XMLExists</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X100</entry>
-  <entry></entry>
-  <entry>Host language support for XML: CONTENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X101</entry>
-  <entry></entry>
-  <entry>Host language support for XML: DOCUMENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X110</entry>
-  <entry></entry>
-  <entry>Host language support for XML: VARCHAR mapping</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X111</entry>
-  <entry></entry>
-  <entry>Host language support for XML: CLOB mapping</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X112</entry>
-  <entry></entry>
-  <entry>Host language support for XML: BLOB mapping</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X113</entry>
-  <entry></entry>
-  <entry>Host language support for XML: STRIP WHITESPACE option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X114</entry>
-  <entry></entry>
-  <entry>Host language support for XML: PRESERVE WHITESPACE option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X131</entry>
-  <entry></entry>
-  <entry>Query-level XMLBINARY clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X132</entry>
-  <entry></entry>
-  <entry>XMLBINARY clause in DML</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X133</entry>
-  <entry></entry>
-  <entry>XMLBINARY clause in DDL</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X134</entry>
-  <entry></entry>
-  <entry>XMLBINARY clause in compound statements</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X135</entry>
-  <entry></entry>
-  <entry>XMLBINARY clause in subqueries</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X141</entry>
-  <entry></entry>
-  <entry>IS VALID predicate: data-driven case</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X142</entry>
-  <entry></entry>
-  <entry>IS VALID predicate: ACCORDING TO clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X143</entry>
-  <entry></entry>
-  <entry>IS VALID predicate: ELEMENT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X144</entry>
-  <entry></entry>
-  <entry>IS VALID predicate: schema location</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X145</entry>
-  <entry></entry>
-  <entry>IS VALID predicate outside check constraints</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X151</entry>
-  <entry></entry>
-  <entry>IS VALID predicate with DOCUMENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X152</entry>
-  <entry></entry>
-  <entry>IS VALID predicate with CONTENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X153</entry>
-  <entry></entry>
-  <entry>IS VALID predicate with SEQUENCE option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X155</entry>
-  <entry></entry>
-  <entry>IS VALID predicate: NAMESPACE without ELEMENT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X157</entry>
-  <entry></entry>
-  <entry>IS VALID predicate: NO NAMESPACE with ELEMENT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X160</entry>
-  <entry></entry>
-  <entry>Basic Information Schema for registered XML Schemas</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X161</entry>
-  <entry></entry>
-  <entry>Advanced Information Schema for registered XML Schemas</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X170</entry>
-  <entry></entry>
-  <entry>XML null handling options</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X171</entry>
-  <entry></entry>
-  <entry>NIL ON NO CONTENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X181</entry>
-  <entry></entry>
-  <entry>XML(DOCUMENT(UNTYPED)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X182</entry>
-  <entry></entry>
-  <entry>XML(DOCUMENT(ANY)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X190</entry>
-  <entry></entry>
-  <entry>XML(SEQUENCE) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X191</entry>
-  <entry></entry>
-  <entry>XML(DOCUMENT(XMLSCHEMA)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X192</entry>
-  <entry></entry>
-  <entry>XML(CONTENT(XMLSCHEMA)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X200</entry>
-  <entry></entry>
-  <entry>XMLQuery</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X201</entry>
-  <entry></entry>
-  <entry>XMLQuery: RETURNING CONTENT</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X202</entry>
-  <entry></entry>
-  <entry>XMLQuery: RETURNING SEQUENCE</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X203</entry>
-  <entry></entry>
-  <entry>XMLQuery: passing a context item</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X204</entry>
-  <entry></entry>
-  <entry>XMLQuery: initializing an XQuery variable</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X205</entry>
-  <entry></entry>
-  <entry>XMLQuery: EMPTY ON EMPTY option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X206</entry>
-  <entry></entry>
-  <entry>XMLQuery: NULL ON EMPTY option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X211</entry>
-  <entry></entry>
-  <entry>XML 1.1 support</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X221</entry>
-  <entry></entry>
-  <entry>XML passing mechanism BY VALUE</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X222</entry>
-  <entry></entry>
-  <entry>XML passing mechanism BY REF</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X231</entry>
-  <entry></entry>
-  <entry>XML(CONTENT(UNTYPED)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X232</entry>
-  <entry></entry>
-  <entry>XML(CONTENT(ANY)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X241</entry>
-  <entry></entry>
-  <entry>RETURNING CONTENT in XML publishing</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X242</entry>
-  <entry></entry>
-  <entry>RETURNING SEQUENCE in XML publishing</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X251</entry>
-  <entry></entry>
-  <entry>Persistent XML values of XML(DOCUMENT(UNTYPED)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X252</entry>
-  <entry></entry>
-  <entry>Persistent XML values of XML(DOCUMENT(ANY)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X253</entry>
-  <entry></entry>
-  <entry>Persistent XML values of XML(CONTENT(UNTYPED)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X254</entry>
-  <entry></entry>
-  <entry>Persistent XML values of XML(CONTENT(ANY)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X255</entry>
-  <entry></entry>
-  <entry>Persistent XML values of XML(SEQUENCE) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X256</entry>
-  <entry></entry>
-  <entry>Persistent XML values of XML(DOCUMENT(XMLSCHEMA)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X257</entry>
-  <entry></entry>
-  <entry>Persistent XML values of XML(CONTENT(XMLSCHEMA)) type</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X260</entry>
-  <entry></entry>
-  <entry>XML type: ELEMENT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X261</entry>
-  <entry></entry>
-  <entry>XML type: NAMESPACE without ELEMENT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X263</entry>
-  <entry></entry>
-  <entry>XML type: NO NAMESPACE with ELEMENT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X264</entry>
-  <entry></entry>
-  <entry>XML type: schema location</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X271</entry>
-  <entry></entry>
-  <entry>XMLValidate: data-driven case</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X272</entry>
-  <entry></entry>
-  <entry>XMLValidate: ACCORDING TO clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X273</entry>
-  <entry></entry>
-  <entry>XMLValidate: ELEMENT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X274</entry>
-  <entry></entry>
-  <entry>XMLValidate: schema location</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X281</entry>
-  <entry></entry>
-  <entry>XMLValidate: with DOCUMENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X282</entry>
-  <entry></entry>
-  <entry>XMLValidate with CONTENT option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X283</entry>
-  <entry></entry>
-  <entry>XMLValidate with SEQUENCE option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X284</entry>
-  <entry></entry>
-  <entry>XMLValidate NAMESPACE without ELEMENT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X286</entry>
-  <entry></entry>
-  <entry>XMLValidate: NO NAMESPACE with ELEMENT clause</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X300</entry>
-  <entry></entry>
-  <entry>XMLTable</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X301</entry>
-  <entry></entry>
-  <entry>XMLTable: derived column list option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X302</entry>
-  <entry></entry>
-  <entry>XMLTable: ordinality column option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X303</entry>
-  <entry></entry>
-  <entry>XMLTable: column default option</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X304</entry>
-  <entry></entry>
-  <entry>XMLTable: passing a context item</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X305</entry>
-  <entry></entry>
-  <entry>XMLTable: initializing an XQuery variable</entry>
-  <entry></entry>
- </row>
- <row>
-  <entry>X400</entry>
-  <entry></entry>
-  <entry>Name and identifier mapping</entry>
-  <entry></entry>
- </row>
-</tbody>
diff --git a/doc-xc/src/sgml/features.sgmlin b/doc-xc/src/sgml/features.sgmlin
deleted file mode 100644
index 36af4a7689..0000000000
--- a/doc-xc/src/sgml/features.sgmlin
+++ /dev/null
@@ -1,164 +0,0 @@
-<!-- doc/src/sgml/features.sgml -->
-
-<appendix id="features">
- <title>SQL Conformance</title>
-
- <para>
-  This section attempts to outline to what extent
-  <productname>PostgreSQL</productname> conforms to the current SQL
-  standard.  The following information is not a full statement of
-  conformance, but it presents the main topics in as much detail as is
-  both reasonable and useful for users.
- </para>
-
- <para>
-  The formal name of the SQL standard is ISO/IEC 9075 <quote>Database
-  Language SQL</quote>.  A revised version of the standard is released
-  from time to time; the most recent update appearing in 2008.
-  The 2008 version is referred to as ISO/IEC 9075:2008, or simply as SQL:2008.
-  The versions prior to that were SQL:2003, SQL:1999, and SQL-92.  Each version
-  replaces the previous one, so claims of conformance to earlier
-  versions have no official merit.
-  <productname>PostgreSQL</productname> development aims for
-  conformance with the latest official version of the standard where
-  such conformance does not contradict traditional features or common
-  sense.  The PostgreSQL project is not represented in the ISO/IEC
-  9075 Working Group during the preparation of the SQL standard
-  releases, but even so, many of the features required by the SQL
-  standard are supported, though sometimes with slightly differing
-  syntax or function.  Further moves towards conformance can be
-  expected over time.
- </para>
-
- <para>
-  <acronym>SQL-92</acronym> defined three feature sets for
-  conformance: Entry, Intermediate, and Full.  Most database
-  management systems claiming <acronym>SQL</acronym> standard
-  conformance were conforming at only the Entry level, since the
-  entire set of features in the Intermediate and Full levels was
-  either too voluminous or in conflict with legacy behaviors.
- </para>
-
- <para>
-  Starting with <acronym>SQL:1999</acronym>, the SQL standard defines
-  a large set of individual features rather than the ineffectively
-  broad three levels found in <acronym>SQL-92</acronym>.  A large
-  subset of these features represents the <quote>Core</quote>
-  features, which every conforming SQL implementation must supply.
-  The rest of the features are purely optional.  Some optional
-  features are grouped together to form <quote>packages</quote>, which
-  SQL implementations can claim conformance to, thus claiming
-  conformance to particular groups of features.
- </para>
-
- <para>
-  The <acronym>SQL:2008</acronym> and <acronym>SQL:2003</acronym>
-  standard versions are also split into a number
-  of parts.  Each is known by a shorthand name.  Note that these parts
-  are not consecutively numbered.
-
-  <itemizedlist>
-   <listitem><para>ISO/IEC 9075-1 Framework (SQL/Framework)</para><indexterm><primary>SQL/Framework</primary></indexterm></listitem>
-   <listitem><para>ISO/IEC 9075-2 Foundation (SQL/Foundation)</para><indexterm><primary>SQL/Foundation</primary></indexterm></listitem>
-   <listitem><para>ISO/IEC 9075-3 Call Level Interface (SQL/CLI)</para><indexterm><primary>SQL/CLI</primary></indexterm></listitem>
-   <listitem><para>ISO/IEC 9075-4 Persistent Stored Modules (SQL/PSM)</para><indexterm><primary>SQL/PSM</primary></indexterm></listitem>
-   <listitem><para>ISO/IEC 9075-9 Management of External Data (SQL/MED)</para><indexterm><primary>SQL/MED</primary></indexterm></listitem>
-   <listitem><para>ISO/IEC 9075-10 Object Language Bindings (SQL/OLB)</para><indexterm><primary>SQL/OLB</primary></indexterm></listitem>
-   <listitem><para>ISO/IEC 9075-11 Information and Definition Schemas (SQL/Schemata)</para><indexterm><primary>SQL/Schemata</primary></indexterm></listitem>
-   <listitem><para>ISO/IEC 9075-13 Routines and Types using the Java Language (SQL/JRT)</para><indexterm><primary>SQL/JRT</primary></indexterm></listitem>
-   <listitem><para>ISO/IEC 9075-14 XML-related specifications (SQL/XML)</para><indexterm><primary>SQL/XML</primary></indexterm></listitem>
-  </itemizedlist>
- </para>
-
- <para>
-  The <productname>PostgreSQL</productname> core covers parts 1, 2, 9,
-  11, and 14.  Part 3 is covered by the ODBC driver, and part 13 is
-  covered by the PL/Java plug-in, but exact conformance is currently
-  not being verified for these components.  There are currently no
-  implementations of parts 4 and 10
-  for <productname>PostgreSQL</productname>.
- </para>
-
- <para>
-  PostgreSQL supports most of the major features of SQL:2008.  Out of
-  179 mandatory features required for full Core conformance,
-  PostgreSQL conforms to at least 160.  In addition, there is a long
-  list of supported optional features.  It might be worth noting that at
-  the time of writing, no current version of any database management
-  system claims full conformance to Core SQL:2008.
- </para>
-
- <para>
-  In the following two sections, we provide a list of those features
-  that <productname>PostgreSQL</productname> supports, followed by a
-  list of the features defined in <acronym>SQL:2008</acronym> which
-  are not yet supported in <productname>PostgreSQL</productname>.
-  Both of these lists are approximate: There might be minor details that
-  are nonconforming for a feature that is listed as supported, and
-  large parts of an unsupported feature might in fact be implemented.
-  The main body of the documentation always contains the most accurate
-  information about what does and does not work.
- </para>
-
- <note>
-  <para>
-   Feature codes containing a hyphen are subfeatures.  Therefore, if a
-   particular subfeature is not supported, the main feature is listed
-   as unsupported even if some other subfeatures are supported.
-  </para>
- </note>
-
-  <sect1 id="features-sql-standard">
-   <title>Supported Features</title>
-
-&pgnotice;
-
-   <para>
-    <informaltable>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Identifier</entry>
-        <entry>Package</entry>
-        <entry>Description</entry>
-        <entry>Comment</entry>
-       </row>
-      </thead>
-
-      &features-supported;
-
-     </tgroup>
-    </informaltable>
-   </para>
-  </sect1>
-
-  <sect1 id="unsupported-features-sql-standard">
-   <title>Unsupported Features</title>
-
-&pgnotice;
-
-   <para>
-    The following features defined in <acronym>SQL:2008</acronym> are not
-    implemented in this release of
-    <productname>PostgreSQL</productname>. In a few cases, equivalent
-    functionality is available.
-
-    <informaltable>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Identifier</entry>
-        <entry>Package</entry>
-        <entry>Description</entry>
-        <entry>Comment</entry>
-       </row>
-      </thead>
-
-      &features-unsupported;
-
-     </tgroup>
-    </informaltable>
-   </para>
-  </sect1>
-
- </appendix>
diff --git a/doc-xc/src/sgml/file-fdw.sgmlin b/doc-xc/src/sgml/file-fdw.sgmlin
deleted file mode 100644
index 8497d9a45f..0000000000
--- a/doc-xc/src/sgml/file-fdw.sgmlin
+++ /dev/null
@@ -1,138 +0,0 @@
-<!-- doc/src/sgml/file-fdw.sgml -->
-
-<sect1 id="file-fdw" xreflabel="file_fdw">
- <title>file_fdw</title>
-
- <indexterm zone="file-fdw">
-  <primary>file_fdw</primary>
- </indexterm>
-
- <para>
-  The <filename>file_fdw</> module provides the foreign-data wrapper
-  <function>file_fdw</function>, which can be used to access data
-  files in the server's file system.  Data files must be in a format
-  that can be read by <command>COPY FROM</command>;
-  see <xref linkend="sql-copy"> for details.
- </para>
-
- <para>
-  A foreign table created using this wrapper can have the following options:
- </para>
-
- <variablelist>
-
-  <varlistentry>
-   <term><literal>filename</literal></term>
-
-   <listitem>
-    <para>
-     Specifies the file to be read.  Required.  Must be an absolute path name.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><literal>format</literal></term>
-
-   <listitem>
-    <para>
-     Specifies the file's format,
-     the same as <command>COPY</>'s <literal>FORMAT</literal> option.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><literal>header</literal></term>
-
-   <listitem>
-    <para>
-     Specifies whether the file has a header line,
-     the same as <command>COPY</>'s <literal>HEADER</literal> option.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><literal>delimiter</literal></term>
-
-   <listitem>
-    <para>
-     Specifies the file's delimiter character,
-     the same as <command>COPY</>'s <literal>DELIMITER</literal> option.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><literal>quote</literal></term>
-
-   <listitem>
-    <para>
-     Specifies the file's quote character,
-     the same as <command>COPY</>'s <literal>QUOTE</literal> option.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><literal>escape</literal></term>
-
-   <listitem>
-    <para>
-     Specifies the file's escape character,
-     the same as <command>COPY</>'s <literal>ESCAPE</literal> option.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><literal>null</literal></term>
-
-   <listitem>
-    <para>
-     Specifies the file's null string,
-     the same as <command>COPY</>'s <literal>NULL</literal> option.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><literal>encoding</literal></term>
-
-   <listitem>
-    <para>
-     Specifies the file's encoding.
-     the same as <command>COPY</>'s <literal>ENCODING</literal> option.
-    </para>
-   </listitem>
-  </varlistentry>
-
- </variablelist>
-
- <para>
-  <command>COPY</>'s <literal>OIDS</literal>, <literal>FORCE_QUOTE</literal>,
-  and <literal>FORCE_NOT_NULL</literal> options are currently not supported by
-  <literal>file_fdw</>.
- </para>
-
- <para>
-  These options can only be specified for a foreign table, not in the
-  options of the <literal>file_fdw</> foreign-data wrapper, nor in the
-  options of a server or user mapping using the wrapper.
- </para>
-
- <para>
-  Changing table-level options requires superuser privileges, for security
-  reasons: only a superuser should be able to determine which file is read.
-  In principle non-superusers could be allowed to change the other options,
-  but that's not supported at present.
- </para>
-
- <para>
-  For a foreign table using <literal>file_fdw</>, <command>EXPLAIN</> shows
-  the name of the file to be read.  Unless <literal>COSTS OFF</> is
-  specified, the file size (in bytes) is shown as well.
- </para>
-
-</sect1>
diff --git a/doc-xc/src/sgml/filelist.sgmlin b/doc-xc/src/sgml/filelist.sgmlin
deleted file mode 100644
index 107bc1b1cd..0000000000
--- a/doc-xc/src/sgml/filelist.sgmlin
+++ /dev/null
@@ -1,226 +0,0 @@
-<!-- doc/src/sgml/filelist.sgml -->
-
-<!ENTITY history    SYSTEM "history.sgml">
-<!ENTITY info       SYSTEM "info.sgml">
-<!ENTITY intro      SYSTEM "intro.sgml">
-<!ENTITY legal      SYSTEM "legal.sgml">
-<!ENTITY notation   SYSTEM "notation.sgml">
-<!ENTITY problems   SYSTEM "problems.sgml">
-<!## XC>
-<!entity pgnotice   SYSTEM "pgnotice.sgml">
-<!entity xconly		SYSTEM "xconly.sgml">
-<!entity pgonly     SYSTEM "pgonly.sgml">
-<!entity common		SYSTEM "common.sgml">
-<!entity xc-constraint SYSTEM "xc-constraint.sgml">
-<!## end>
-<!## XL>
-<!entity pgnotice   SYSTEM "pgnotice.sgml">
-<!entity xlonly		SYSTEM "xlonly.sgml">
-<!entity pgonly     SYSTEM "pgonly.sgml">
-<!entity common		SYSTEM "common.sgml">
-<!entity xc-constraint SYSTEM "xc-constraint.sgml">
-<!## end>
-
-<!-- tutorial -->
-<!ENTITY advanced   SYSTEM "advanced.sgml">
-<!ENTITY query      SYSTEM "query.sgml">
-<!ENTITY start      SYSTEM "start.sgml">
-
-<!-- currently unused, but contains some interesting information -->
-<!ENTITY sql        SYSTEM "sql.sgml">
-
-<!-- user's guide -->
-<!ENTITY array      SYSTEM "array.sgml">
-<!ENTITY datatype   SYSTEM "datatype.sgml">
-<!ENTITY ddl        SYSTEM "ddl.sgml">
-<!ENTITY dml        SYSTEM "dml.sgml">
-<!ENTITY func       SYSTEM "func.sgml">
-<!ENTITY indices    SYSTEM "indices.sgml">
-<!ENTITY mvcc       SYSTEM "mvcc.sgml">
-<!ENTITY perform    SYSTEM "perform.sgml">
-<!ENTITY queries    SYSTEM "queries.sgml">
-<!ENTITY rowtypes   SYSTEM "rowtypes.sgml">
-<!ENTITY syntax     SYSTEM "syntax.sgml">
-<!ENTITY textsearch SYSTEM "textsearch.sgml">
-<!ENTITY typeconv   SYSTEM "typeconv.sgml">
-
-<!-- administrator's guide -->
-<!ENTITY backup        SYSTEM "backup.sgml">
-<!ENTITY charset       SYSTEM "charset.sgml">
-<!ENTITY client-auth   SYSTEM "client-auth.sgml">
-<!ENTITY diskusage     SYSTEM "diskusage.sgml">
-<!ENTITY high-availability      SYSTEM "high-availability.sgml">
-<!ENTITY installation  SYSTEM "installation.sgml">
-<!## PG>
-<!ENTITY installw      SYSTEM "install-windows.sgml">
-<!## end>
-<!ENTITY maintenance   SYSTEM "maintenance.sgml">
-<!ENTITY manage-ag     SYSTEM "manage-ag.sgml">
-<!ENTITY monitoring    SYSTEM "monitoring.sgml">
-<!ENTITY regress       SYSTEM "regress.sgml">
-<!ENTITY recovery-config SYSTEM "recovery-config.sgml">
-<!ENTITY runtime       SYSTEM "runtime.sgml">
-<!ENTITY config        SYSTEM "config.sgml">
-<!ENTITY user-manag    SYSTEM "user-manag.sgml">
-<!ENTITY wal           SYSTEM "wal.sgml">
-<!ENTITY add-node      SYSTEM "add-node.sgml">
-<!ENTITY remove-node   SYSTEM "remove-node.sgml">
-
-<!-- programmer's guide -->
-<!ENTITY dfunc      SYSTEM "dfunc.sgml">
-<!ENTITY ecpg       SYSTEM "ecpg.sgml">
-<!ENTITY extend     SYSTEM "extend.sgml">
-<!ENTITY external-projects SYSTEM "external-projects.sgml">
-<!ENTITY func-ref   SYSTEM "func-ref.sgml">
-<!ENTITY infoschema SYSTEM "information_schema.sgml">
-<!ENTITY libpq      SYSTEM "libpq.sgml">
-<!ENTITY lobj       SYSTEM "lobj.sgml">
-<!ENTITY rules      SYSTEM "rules.sgml">
-<!ENTITY spi        SYSTEM "spi.sgml">
-<!ENTITY trigger    SYSTEM "trigger.sgml">
-<!ENTITY xaggr      SYSTEM "xaggr.sgml">
-<!ENTITY xfunc      SYSTEM "xfunc.sgml">
-<!ENTITY xindex     SYSTEM "xindex.sgml">
-<!ENTITY xplang     SYSTEM "xplang.sgml">
-<!ENTITY xoper      SYSTEM "xoper.sgml">
-<!ENTITY xtypes     SYSTEM "xtypes.sgml">
-<!ENTITY plperl     SYSTEM "plperl.sgml">
-<!ENTITY plpython   SYSTEM "plpython.sgml">
-<!ENTITY plsql      SYSTEM "plpgsql.sgml">
-<!ENTITY pltcl      SYSTEM "pltcl.sgml">
-
-<!-- reference pages -->
-<!ENTITY % allfiles   SYSTEM "ref/allfiles.sgml">
-%allfiles;
-
-<!-- developer's guide -->
-<!ENTITY arch-dev   SYSTEM "arch-dev.sgml">
-<!ENTITY bki        SYSTEM "bki.sgml">
-<!ENTITY catalogs   SYSTEM "catalogs.sgml">
-<!ENTITY geqo       SYSTEM "geqo.sgml">
-<!ENTITY gist       SYSTEM "gist.sgml">
-<!ENTITY gin        SYSTEM "gin.sgml">
-<!ENTITY planstats    SYSTEM "planstats.sgml">
-<!ENTITY indexam    SYSTEM "indexam.sgml">
-<!ENTITY nls        SYSTEM "nls.sgml">
-<!ENTITY plhandler  SYSTEM "plhandler.sgml">
-<!ENTITY fdwhandler SYSTEM "fdwhandler.sgml">
-<!ENTITY protocol   SYSTEM "protocol.sgml">
-<!ENTITY sources    SYSTEM "sources.sgml">
-<!ENTITY storage    SYSTEM "storage.sgml">
-
-<!-- contrib information -->
-<!ENTITY contrib         SYSTEM "contrib.sgml">
-<!ENTITY adminpack       SYSTEM "adminpack.sgml">
-<!ENTITY auth-delay      SYSTEM "auth-delay.sgml">
-<!ENTITY auto-explain    SYSTEM "auto-explain.sgml">
-<!ENTITY btree-gin       SYSTEM "btree-gin.sgml">
-<!ENTITY btree-gist      SYSTEM "btree-gist.sgml">
-<!ENTITY chkpass         SYSTEM "chkpass.sgml">
-<!ENTITY citext          SYSTEM "citext.sgml">
-<!ENTITY cube            SYSTEM "cube.sgml">
-<!ENTITY dblink          SYSTEM "dblink.sgml">
-<!ENTITY dict-int        SYSTEM "dict-int.sgml">
-<!ENTITY dict-xsyn       SYSTEM "dict-xsyn.sgml">
-<!ENTITY dummy-seclabel  SYSTEM "dummy-seclabel.sgml">
-<!ENTITY earthdistance   SYSTEM "earthdistance.sgml">
-<!ENTITY file-fdw        SYSTEM "file-fdw.sgml">
-<!ENTITY fuzzystrmatch   SYSTEM "fuzzystrmatch.sgml">
-<!ENTITY hstore          SYSTEM "hstore.sgml">
-<!ENTITY intagg          SYSTEM "intagg.sgml">
-<!ENTITY intarray        SYSTEM "intarray.sgml">
-<!ENTITY isn             SYSTEM "isn.sgml">
-<!ENTITY lo              SYSTEM "lo.sgml">
-<!ENTITY ltree           SYSTEM "ltree.sgml">
-<!ENTITY oid2name        SYSTEM "oid2name.sgml">
-<!ENTITY pageinspect     SYSTEM "pageinspect.sgml">
-<!ENTITY passwordcheck   SYSTEM "passwordcheck.sgml">
-<!ENTITY pgbench         SYSTEM "pgbench.sgml">
-<!ENTITY pgarchivecleanup SYSTEM "pgarchivecleanup.sgml">
-<!ENTITY pgbuffercache   SYSTEM "pgbuffercache.sgml">
-<!ENTITY pgcrypto        SYSTEM "pgcrypto.sgml">
-<!ENTITY pgfreespacemap  SYSTEM "pgfreespacemap.sgml">
-<!ENTITY pgrowlocks      SYSTEM "pgrowlocks.sgml">
-<!ENTITY pgstandby       SYSTEM "pgstandby.sgml">
-<!ENTITY pgstatstatements SYSTEM "pgstatstatements.sgml">
-<!ENTITY pgstattuple     SYSTEM "pgstattuple.sgml">
-<!ENTITY pgtestfsync     SYSTEM "pgtestfsync.sgml">
-<!ENTITY pgtrgm          SYSTEM "pgtrgm.sgml">
-<!ENTITY pgupgrade       SYSTEM "pgupgrade.sgml">
-<!## XC>
-<!ENTITY pgxcclean       SYSTEM "pgxcclean.sgml">
-<!ENTITY pgxcctl         SYSTEM "pgxc_ctl-ref.sgml">
-<!ENTITY pgxcddl         SYSTEM "pgxcddl.sgml">
-<!ENTITY pgxcmonitor	 SYSTEM "pgxcmonitor.sgml">
-<!## end>
-<!## XL>
-<!ENTITY pgxcclean       SYSTEM "pgxcclean.sgml">
-<!ENTITY pgxcctl         SYSTEM "pgxc_ctl-ref.sgml">
-<!ENTITY pgxcddl         SYSTEM "pgxcddl.sgml">
-<!ENTITY pgxcmonitor	 SYSTEM "pgxcmonitor.sgml">
-<!## end>
-<!ENTITY seg             SYSTEM "seg.sgml">
-<!ENTITY contrib-spi     SYSTEM "contrib-spi.sgml">
-<!ENTITY sepgsql         SYSTEM "sepgsql.sgml">
-<!ENTITY sslinfo         SYSTEM "sslinfo.sgml">
-<!ENTITY tablefunc       SYSTEM "tablefunc.sgml">
-<!ENTITY test-parser     SYSTEM "test-parser.sgml">
-<!ENTITY tsearch2        SYSTEM "tsearch2.sgml">
-<!ENTITY unaccent      SYSTEM "unaccent.sgml">
-<!ENTITY uuid-ossp       SYSTEM "uuid-ossp.sgml">
-<!ENTITY vacuumlo        SYSTEM "vacuumlo.sgml">
-<!ENTITY xml2            SYSTEM "xml2.sgml">
-
-<!-- appendixes -->
-<!ENTITY contacts   SYSTEM "contacts.sgml">
-<!ENTITY datetime   SYSTEM "datetime.sgml">
-<!ENTITY docguide   SYSTEM "docguide.sgml">
-<!ENTITY errcodes   SYSTEM "errcodes.sgml">
-<!ENTITY features   SYSTEM "features.sgml">
-<!ENTITY keywords   SYSTEM "keywords.sgml">
-<!ENTITY sourcerepo SYSTEM "sourcerepo.sgml">
-
-<!ENTITY release    SYSTEM "release.sgml">
-<!## XC>
-<!ENTITY release-xc-1.0 SYSTEM "release-xc-1.0.sgml">
-<!## end>
-<!## XL>
-<!ENTITY release-xl-9.2 SYSTEM "release-xl-9.2.sgml">
-<!## end>
-<!## PG>
-<!ENTITY release-9.1    SYSTEM "release-9.1.sgml">
-<!ENTITY release-9.0    SYSTEM "release-9.0.sgml">
-<!ENTITY release-8.4    SYSTEM "release-8.4.sgml">
-<!ENTITY release-8.3    SYSTEM "release-8.3.sgml">
-<!ENTITY release-8.2    SYSTEM "release-8.2.sgml">
-<!ENTITY release-8.1    SYSTEM "release-8.1.sgml">
-<!ENTITY release-8.0    SYSTEM "release-8.0.sgml">
-<!ENTITY release-7.4    SYSTEM "release-7.4.sgml">
-<!ENTITY release-old    SYSTEM "release-old.sgml">
-<!## end>
-
-<!ENTITY acronyms   SYSTEM "acronyms.sgml">
-
-<!ENTITY features-supported   SYSTEM "features-supported.sgml">
-<!ENTITY features-unsupported SYSTEM "features-unsupported.sgml">
-
-<!ENTITY errcodes-table SYSTEM "errcodes-table.sgml">
-
-<!-- back matter -->
-<!ENTITY biblio     SYSTEM "biblio.sgml">
-<!ENTITY bookindex  SYSTEM "bookindex.sgml">
-
-<!--
- Some parts of the documentation are also source for some plain-text
- files used during installation.  To selectively ignore or include
- some parts (e.g., external xref's) when generating these files we use
- these parameter entities.  See also standalone-install.sgml.
- -->
-<!ENTITY % standalone-ignore  "INCLUDE">
-<!ENTITY % standalone-include "IGNORE">
-
-<!--
- By default, no index is included.  Use -i include-index on the command line
- to include it.
- -->
-<!ENTITY % include-index "IGNORE">
diff --git a/doc-xc/src/sgml/fixrtf b/doc-xc/src/sgml/fixrtf
deleted file mode 100755
index 31cb5f85c0..0000000000
--- a/doc-xc/src/sgml/fixrtf
+++ /dev/null
@@ -1,46 +0,0 @@
-#!/bin/sh
-# fixrtf
-
-# doc/src/sgml/fixrtf
-
-# Repair (slightly) damaged RTF generated by jade
-# Applixware wants the s0 stylesheet defined, whereas
-#  M$Word does not care about it.
-# (c) 2001, Thomas Lockhart, PostgreSQL Inc.
-
-flist=""
-RPAT=""
-for i in $@ ; do
-  case "$i" in
-    -r|--refentry)
-      RPAT='-e s/\\\keepn/\\\keep/g'
-      ;;
-    -?|--help)
-      echo "$0 [--refentry] <rtf file> ..."
-      exit 0
-      ;;
-    -*)
-      echo "Command $i not recognized"
-      $0 --help
-      exit 1
-      ;;
-    *)
-      flist="$flist $i"
-  esac
-done
-
-if [ "$flist" = "" ] ; then
-  flist=*.rtf
-fi
-
-for f in $flist ; do
-  echo -n "Repairing '$f' ..."
-  if [ -r $f ] ; then
-    (sed -e 's/{\\stylesheet{\\s1/{\\stylesheet{\\s0 Normal 0;}{\\s1/g' $RPAT $f > $f.new \
-      && mv -f $f.new $f \
-      && echo " done") || echo " failed"
-  else
-    echo " file not found"
-  fi
-done
-exit
diff --git a/doc-xc/src/sgml/func.sgmlin b/doc-xc/src/sgml/func.sgmlin
deleted file mode 100644
index 6cc9f78c8b..0000000000
--- a/doc-xc/src/sgml/func.sgmlin
+++ /dev/null
@@ -1,16285 +0,0 @@
-<!-- doc/src/sgml/func.sgml -->
-
- <chapter id="functions">
-  <title>Functions and Operators</title>
-
-  <indexterm zone="functions">
-   <primary>function</primary>
-  </indexterm>
-
-  <indexterm zone="functions">
-   <primary>operator</primary>
-  </indexterm>
-
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> provides a large number of
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> inherits a large number of
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> inherits a large number of
-<!## end>
-   functions and operators for the built-in data types.  Users can also
-   define their own functions and operators, as described in
-   <xref linkend="server-programming">.  The
-   <application>psql</application> commands <command>\df</command> and
-   <command>\do</command> can be used to list all
-   available functions and operators, respectively.
-  </para>
-
-  <para>
-   If you are concerned about portability then note that most of
-   the functions and operators described in this chapter, with the
-   exception of the most trivial arithmetic and comparison operators
-   and some explicitly marked functions, are not specified by the
-   <acronym>SQL</acronym> standard. Some of this extended functionality
-   is present in other <acronym>SQL</acronym> database management
-   systems, and in many cases this functionality is compatible and
-   consistent between the various implementations.  This chapter is also
-   not exhaustive;  additional functions appear in relevant sections of
-   the manual.
-  </para>
-
-
-  <sect1 id="functions-logical">
-   <title>Logical Operators</title>
-
-   <indexterm zone="functions-logical">
-    <primary>operator</primary>
-    <secondary>logical</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>Boolean</primary>
-    <secondary>operators</secondary>
-    <see>operators, logical</see>
-   </indexterm>
-&common;
-   <para>
-    The usual logical operators are available:
-
-    <indexterm>
-     <primary>AND (operator)</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>OR (operator)</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>NOT (operator)</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>conjunction</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>disjunction</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>negation</primary>
-    </indexterm>
-
-    <simplelist>
-     <member><literal>AND</></member>
-     <member><literal>OR</></member>
-     <member><literal>NOT</></member>
-    </simplelist>
-
-    <acronym>SQL</acronym> uses a three-valued Boolean logic where the null value represents
-    <quote>unknown</quote>.  Observe the following truth tables:
-
-    <informaltable>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry><replaceable>a</replaceable></entry>
-        <entry><replaceable>b</replaceable></entry>
-        <entry><replaceable>a</replaceable> AND <replaceable>b</replaceable></entry>
-        <entry><replaceable>a</replaceable> OR <replaceable>b</replaceable></entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry>TRUE</entry>
-        <entry>TRUE</entry>
-        <entry>TRUE</entry>
-        <entry>TRUE</entry>
-       </row>
-
-       <row>
-        <entry>TRUE</entry>
-        <entry>FALSE</entry>
-        <entry>FALSE</entry>
-        <entry>TRUE</entry>
-       </row>
-
-       <row>
-        <entry>TRUE</entry>
-        <entry>NULL</entry>
-        <entry>NULL</entry>
-        <entry>TRUE</entry>
-       </row>
-
-       <row>
-        <entry>FALSE</entry>
-        <entry>FALSE</entry>
-        <entry>FALSE</entry>
-        <entry>FALSE</entry>
-       </row>
-
-       <row>
-        <entry>FALSE</entry>
-        <entry>NULL</entry>
-        <entry>FALSE</entry>
-        <entry>NULL</entry>
-       </row>
-
-       <row>
-        <entry>NULL</entry>
-        <entry>NULL</entry>
-        <entry>NULL</entry>
-        <entry>NULL</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </informaltable>
-
-    <informaltable>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry><replaceable>a</replaceable></entry>
-        <entry>NOT <replaceable>a</replaceable></entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry>TRUE</entry>
-        <entry>FALSE</entry>
-       </row>
-
-       <row>
-        <entry>FALSE</entry>
-        <entry>TRUE</entry>
-       </row>
-
-       <row>
-        <entry>NULL</entry>
-        <entry>NULL</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </informaltable>
-   </para>
-
-   <para>
-    The operators <literal>AND</literal> and <literal>OR</literal> are
-    commutative, that is, you can switch the left and right operand
-    without affecting the result.  But see <xref
-    linkend="syntax-express-eval"> for more information about the
-    order of evaluation of subexpressions.
-   </para>
-  </sect1>
-
-  <sect1 id="functions-comparison">
-   <title>Comparison Operators</title>
-
-   <indexterm zone="functions-comparison">
-    <primary>comparison</primary>
-    <secondary>operators</secondary>
-   </indexterm>
-&common;
-   <para>
-    The usual comparison operators are available, shown in <xref
-    linkend="functions-comparison-table">.
-   </para>
-
-   <table id="functions-comparison-table">
-    <title>Comparison Operators</title>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Operator</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry> <literal>&lt;</literal> </entry>
-       <entry>less than</entry>
-      </row>
-
-      <row>
-       <entry> <literal>&gt;</literal> </entry>
-       <entry>greater than</entry>
-      </row>
-
-      <row>
-       <entry> <literal>&lt;=</literal> </entry>
-       <entry>less than or equal to</entry>
-      </row>
-
-      <row>
-       <entry> <literal>&gt;=</literal> </entry>
-       <entry>greater than or equal to</entry>
-      </row>
-
-      <row>
-       <entry> <literal>=</literal> </entry>
-       <entry>equal</entry>
-      </row>
-
-      <row>
-       <entry> <literal>&lt;&gt;</literal> or <literal>!=</literal> </entry>
-       <entry>not equal</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <note>
-    <para>
-     The <literal>!=</literal> operator is converted to
-     <literal>&lt;&gt;</literal> in the parser stage.  It is not
-     possible to implement <literal>!=</literal> and
-     <literal>&lt;&gt;</literal> operators that do different things.
-    </para>
-   </note>
-
-   <para>
-    Comparison operators are available for all relevant data types.
-    All comparison operators are binary operators that
-    return values of type <type>boolean</type>; expressions like
-    <literal>1 &lt; 2 &lt; 3</literal> are not valid (because there is
-    no <literal>&lt;</literal> operator to compare a Boolean value with
-    <literal>3</literal>).
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>BETWEEN</primary>
-    </indexterm>
-    In addition to the comparison operators, the special
-    <token>BETWEEN</token> construct is available:
-<synopsis>
-<replaceable>a</replaceable> BETWEEN <replaceable>x</replaceable> AND <replaceable>y</replaceable>
-</synopsis>
-    is equivalent to
-<synopsis>
-<replaceable>a</replaceable> &gt;= <replaceable>x</replaceable> AND <replaceable>a</replaceable> &lt;= <replaceable>y</replaceable>
-</synopsis>
-    Notice that <token>BETWEEN</token> treats the endpoint values as included
-    in the range.
-    <literal>NOT BETWEEN</literal> does the opposite comparison:
-<synopsis>
-<replaceable>a</replaceable> NOT BETWEEN <replaceable>x</replaceable> AND <replaceable>y</replaceable>
-</synopsis>
-    is equivalent to
-<synopsis>
-<replaceable>a</replaceable> &lt; <replaceable>x</replaceable> OR <replaceable>a</replaceable> &gt; <replaceable>y</replaceable>
-</synopsis>
-    <indexterm>
-     <primary>BETWEEN SYMMETRIC</primary>
-    </indexterm>
-    <literal>BETWEEN SYMMETRIC</> is the same as <literal>BETWEEN</>
-    except there is no requirement that the argument to the left of
-    <literal>AND</> be less than or equal to the argument on the right.
-    If it is not, those two arguments are automatically swapped, so that
-    a nonempty range is always implied.
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>IS NULL</primary>
-    </indexterm>
-    <indexterm>
-     <primary>IS NOT NULL</primary>
-    </indexterm>
-    <indexterm>
-     <primary>ISNULL</primary>
-    </indexterm>
-    <indexterm>
-     <primary>NOTNULL</primary>
-    </indexterm>
-    To check whether a value is or is not null, use the constructs:
-<synopsis>
-<replaceable>expression</replaceable> IS NULL
-<replaceable>expression</replaceable> IS NOT NULL
-</synopsis>
-    or the equivalent, but nonstandard, constructs:
-<synopsis>
-<replaceable>expression</replaceable> ISNULL
-<replaceable>expression</replaceable> NOTNULL
-</synopsis>
-    <indexterm><primary>null value</primary><secondary>comparing</secondary></indexterm>
-   </para>
-
-   <para>
-    Do <emphasis>not</emphasis> write
-    <literal><replaceable>expression</replaceable> = NULL</literal>
-    because <literal>NULL</> is not <quote>equal to</quote>
-    <literal>NULL</>.  (The null value represents an unknown value,
-    and it is not known whether two unknown values are equal.) This
-    behavior conforms to the SQL standard.
-   </para>
-
-  <tip>
-   <para>
-    Some applications might expect that
-    <literal><replaceable>expression</replaceable> = NULL</literal>
-    returns true if <replaceable>expression</replaceable> evaluates to
-    the null value.  It is highly recommended that these applications
-    be modified to comply with the SQL standard. However, if that
-    cannot be done the <xref linkend="guc-transform-null-equals">
-    configuration variable is available. If it is enabled,
-<!## PG>
-    <productname>PostgreSQL</productname> will convert <literal>x =
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> will convert <literal>x =
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> will convert <literal>x =
-<!## end>
-    NULL</literal> clauses to <literal>x IS NULL</literal>.
-   </para>
-  </tip>
-
-  <note>
-   <para>
-    If the <replaceable>expression</replaceable> is row-valued, then
-    <literal>IS NULL</> is true when the row expression itself is null
-    or when all the row's fields are null, while
-    <literal>IS NOT NULL</> is true when the row expression itself is non-null
-    and all the row's fields are non-null.  Because of this behavior,
-    <literal>IS NULL</> and <literal>IS NOT NULL</> do not always return
-    inverse results for row-valued expressions, i.e., a row-valued
-    expression that contains both NULL and non-null values will return false
-    for both tests.
-    This definition conforms to the SQL standard, and is a change from the
-    inconsistent behavior exhibited by <productname>PostgreSQL</productname>
-    versions prior to 8.2.
-   </para>
-  </note>
-
-   <para>
-    <indexterm>
-     <primary>IS DISTINCT FROM</primary>
-    </indexterm>
-    <indexterm>
-     <primary>IS NOT DISTINCT FROM</primary>
-    </indexterm>
-    Ordinary comparison operators yield null (signifying <quote>unknown</>),
-    not true or false, when either input is null.  For example,
-    <literal>7 = NULL</> yields null.  When this behavior is not suitable,
-    use the
-    <literal>IS <optional> NOT </> DISTINCT FROM</literal> constructs:
-<synopsis>
-<replaceable>expression</replaceable> IS DISTINCT FROM <replaceable>expression</replaceable>
-<replaceable>expression</replaceable> IS NOT DISTINCT FROM <replaceable>expression</replaceable>
-</synopsis>
-    For non-null inputs, <literal>IS DISTINCT FROM</literal> is
-    the same as the <literal>&lt;&gt;</> operator.  However, if both
-    inputs are null it returns false, and if only one input is
-    null it returns true.  Similarly, <literal>IS NOT DISTINCT
-    FROM</literal> is identical to <literal>=</literal> for non-null
-    inputs, but it returns true when both inputs are null, and false when only
-    one input is null. Thus, these constructs effectively act as though null
-    were a normal data value, rather than <quote>unknown</>.
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>IS TRUE</primary>
-    </indexterm>
-    <indexterm>
-     <primary>IS NOT TRUE</primary>
-    </indexterm>
-    <indexterm>
-     <primary>IS FALSE</primary>
-    </indexterm>
-    <indexterm>
-     <primary>IS NOT FALSE</primary>
-    </indexterm>
-    <indexterm>
-     <primary>IS UNKNOWN</primary>
-    </indexterm>
-    <indexterm>
-     <primary>IS NOT UNKNOWN</primary>
-    </indexterm>
-    Boolean values can also be tested using the constructs
-<synopsis>
-<replaceable>expression</replaceable> IS TRUE
-<replaceable>expression</replaceable> IS NOT TRUE
-<replaceable>expression</replaceable> IS FALSE
-<replaceable>expression</replaceable> IS NOT FALSE
-<replaceable>expression</replaceable> IS UNKNOWN
-<replaceable>expression</replaceable> IS NOT UNKNOWN
-</synopsis>
-    These will always return true or false, never a null value, even when the
-    operand is null.
-    A null input is treated as the logical value <quote>unknown</>.
-    Notice that <literal>IS UNKNOWN</> and <literal>IS NOT UNKNOWN</> are
-    effectively the same as <literal>IS NULL</literal> and
-    <literal>IS NOT NULL</literal>, respectively, except that the input
-    expression must be of Boolean type.
-   </para>
-
-<!-- IS OF does not conform to the ISO SQL behavior, so it is undocumented here
-   <para>
-    <indexterm>
-     <primary>IS OF</primary>
-    </indexterm>
-    <indexterm>
-     <primary>IS NOT OF</primary>
-    </indexterm>
-    It is possible to check the data type of an expression using the
-    constructs
-<synopsis>
-<replaceable>expression</replaceable> IS OF (typename, ...)
-<replaceable>expression</replaceable> IS NOT OF (typename, ...)
-</synopsis>
-    They return a boolean value based on whether the expression's data
-    type is one of the listed data types.
-   </para>
--->
-
-  </sect1>
-
-  <sect1 id="functions-math">
-   <title>Mathematical Functions and Operators</title>
-&common;
-   <para>
-    Mathematical operators are provided for many
-<!## PG>
-    <productname>PostgreSQL</productname> types. For types without
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> types. For types without
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> types. For types without
-<!## end>
-    standard mathematical conventions
-    (e.g., date/time types) we
-    describe the actual behavior in subsequent sections.
-   </para>
-
-   <para>
-    <xref linkend="functions-math-op-table"> shows the available mathematical operators.
-   </para>
-
-   <table id="functions-math-op-table">
-    <title>Mathematical Operators</title>
-
-    <tgroup cols="4">
-     <thead>
-      <row>
-       <entry>Operator</entry>
-       <entry>Description</entry>
-       <entry>Example</entry>
-       <entry>Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry> <literal>+</literal> </entry>
-       <entry>addition</entry>
-       <entry><literal>2 + 3</literal></entry>
-       <entry><literal>5</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>-</literal> </entry>
-       <entry>subtraction</entry>
-       <entry><literal>2 - 3</literal></entry>
-       <entry><literal>-1</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>*</literal> </entry>
-       <entry>multiplication</entry>
-       <entry><literal>2 * 3</literal></entry>
-       <entry><literal>6</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>/</literal> </entry>
-       <entry>division (integer division truncates the result)</entry>
-       <entry><literal>4 / 2</literal></entry>
-       <entry><literal>2</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>%</literal> </entry>
-       <entry>modulo (remainder)</entry>
-       <entry><literal>5 % 4</literal></entry>
-       <entry><literal>1</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>^</literal> </entry>
-       <entry>exponentiation</entry>
-       <entry><literal>2.0 ^ 3.0</literal></entry>
-       <entry><literal>8</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>|/</literal> </entry>
-       <entry>square root</entry>
-       <entry><literal>|/ 25.0</literal></entry>
-       <entry><literal>5</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>||/</literal> </entry>
-       <entry>cube root</entry>
-       <entry><literal>||/ 27.0</literal></entry>
-       <entry><literal>3</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>!</literal> </entry>
-       <entry>factorial</entry>
-       <entry><literal>5 !</literal></entry>
-       <entry><literal>120</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>!!</literal> </entry>
-       <entry>factorial (prefix operator)</entry>
-       <entry><literal>!! 5</literal></entry>
-       <entry><literal>120</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>@</literal> </entry>
-       <entry>absolute value</entry>
-       <entry><literal>@ -5.0</literal></entry>
-       <entry><literal>5</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>&amp;</literal> </entry>
-       <entry>bitwise AND</entry>
-       <entry><literal>91 &amp; 15</literal></entry>
-       <entry><literal>11</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>|</literal> </entry>
-       <entry>bitwise OR</entry>
-       <entry><literal>32 | 3</literal></entry>
-       <entry><literal>35</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>#</literal> </entry>
-       <entry>bitwise XOR</entry>
-       <entry><literal>17 # 5</literal></entry>
-       <entry><literal>20</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>~</literal> </entry>
-       <entry>bitwise NOT</entry>
-       <entry><literal>~1</literal></entry>
-       <entry><literal>-2</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>&lt;&lt;</literal> </entry>
-       <entry>bitwise shift left</entry>
-       <entry><literal>1 &lt;&lt; 4</literal></entry>
-       <entry><literal>16</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>&gt;&gt;</literal> </entry>
-       <entry>bitwise shift right</entry>
-       <entry><literal>8 &gt;&gt; 2</literal></entry>
-       <entry><literal>2</literal></entry>
-      </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    The bitwise operators work only on integral data types, whereas
-    the others are available for all numeric data types.  The bitwise
-    operators are also available for the bit
-    string types <type>bit</type> and <type>bit varying</type>, as
-    shown in <xref linkend="functions-bit-string-op-table">.
-   </para>
-
-  <para>
-   <xref linkend="functions-math-func-table"> shows the available
-   mathematical functions.  In the table, <literal>dp</literal>
-   indicates <type>double precision</type>.  Many of these functions
-   are provided in multiple forms with different argument types.
-   Except where noted, any given form of a function returns the same
-   data type as its argument.
-   The functions working with <type>double precision</type> data are mostly
-   implemented on top of the host system's C library; accuracy and behavior in
-   boundary cases can therefore vary depending on the host system.
-  </para>
-
-   <table id="functions-math-func-table">
-    <title>Mathematical Functions</title>
-    <tgroup cols="5">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Return Type</entry>
-       <entry>Description</entry>
-       <entry>Example</entry>
-       <entry>Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <indexterm>
-         <primary>abs</primary>
-        </indexterm>
-        <literal><function>abs(<replaceable>x</replaceable>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>absolute value</entry>
-       <entry><literal>abs(-17.4)</literal></entry>
-       <entry><literal>17.4</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>cbrt</primary>
-        </indexterm>
-        <literal><function>cbrt(<type>dp</type>)</function></literal>
-       </entry>
-       <entry><type>dp</type></entry>
-       <entry>cube root</entry>
-       <entry><literal>cbrt(27.0)</literal></entry>
-       <entry><literal>3</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>ceil</primary>
-        </indexterm>
-        <literal><function>ceil(<type>dp</type> or <type>numeric</type>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>smallest integer not less than argument</entry>
-       <entry><literal>ceil(-42.8)</literal></entry>
-       <entry><literal>-42</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>ceiling</primary>
-        </indexterm>
-        <literal><function>ceiling(<type>dp</type> or <type>numeric</type>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>smallest integer not less than argument (alias for <function>ceil</function>)</entry>
-       <entry><literal>ceiling(-95.3)</literal></entry>
-       <entry><literal>-95</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>degrees</primary>
-        </indexterm>
-        <literal><function>degrees(<type>dp</type>)</function></literal>
-       </entry>
-       <entry><type>dp</type></entry>
-       <entry>radians to degrees</entry>
-       <entry><literal>degrees(0.5)</literal></entry>
-       <entry><literal>28.6478897565412</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>div</primary>
-        </indexterm>
-        <literal><function>div(<parameter>y</parameter> <type>numeric</>,
-         <parameter>x</parameter> <type>numeric</>)</function></literal>
-       </entry>
-       <entry><type>numeric</></entry>
-       <entry>integer quotient of <parameter>y</parameter>/<parameter>x</parameter></entry>
-       <entry><literal>div(9,4)</literal></entry>
-       <entry><literal>2</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>exp</primary>
-        </indexterm>
-        <literal><function>exp(<type>dp</type> or <type>numeric</type>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>exponential</entry>
-       <entry><literal>exp(1.0)</literal></entry>
-       <entry><literal>2.71828182845905</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>floor</primary>
-        </indexterm>
-        <literal><function>floor(<type>dp</type> or <type>numeric</type>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>largest integer not greater than argument</entry>
-       <entry><literal>floor(-42.8)</literal></entry>
-       <entry><literal>-43</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>ln</primary>
-        </indexterm>
-        <literal><function>ln(<type>dp</type> or <type>numeric</type>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>natural logarithm</entry>
-       <entry><literal>ln(2.0)</literal></entry>
-       <entry><literal>0.693147180559945</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>log</primary>
-        </indexterm>
-        <literal><function>log(<type>dp</type> or <type>numeric</type>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>base 10 logarithm</entry>
-       <entry><literal>log(100.0)</literal></entry>
-       <entry><literal>2</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>log(<parameter>b</parameter> <type>numeric</type>,
-        <parameter>x</parameter> <type>numeric</type>)</function></literal></entry>
-       <entry><type>numeric</type></entry>
-       <entry>logarithm to base <parameter>b</parameter></entry>
-       <entry><literal>log(2.0, 64.0)</literal></entry>
-       <entry><literal>6.0000000000</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>mod</primary>
-        </indexterm>
-        <literal><function>mod(<parameter>y</parameter>,
-         <parameter>x</parameter>)</function></literal>
-       </entry>
-       <entry>(same as argument types)</entry>
-       <entry>remainder of <parameter>y</parameter>/<parameter>x</parameter></entry>
-       <entry><literal>mod(9,4)</literal></entry>
-       <entry><literal>1</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>pi</primary>
-        </indexterm>
-        <literal><function>pi()</function></literal>
-       </entry>
-       <entry><type>dp</type></entry>
-       <entry><quote>&pi;</quote> constant</entry>
-       <entry><literal>pi()</literal></entry>
-       <entry><literal>3.14159265358979</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>power</primary>
-        </indexterm>
-        <literal><function>power(<parameter>a</parameter> <type>dp</type>,
-        <parameter>b</parameter> <type>dp</type>)</function></literal>
-       </entry>
-       <entry><type>dp</type></entry>
-       <entry><parameter>a</> raised to the power of <parameter>b</parameter></entry>
-       <entry><literal>power(9.0, 3.0)</literal></entry>
-       <entry><literal>729</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>power(<parameter>a</parameter> <type>numeric</type>,
-        <parameter>b</parameter> <type>numeric</type>)</function></literal></entry>
-       <entry><type>numeric</type></entry>
-       <entry><parameter>a</> raised to the power of <parameter>b</parameter></entry>
-       <entry><literal>power(9.0, 3.0)</literal></entry>
-       <entry><literal>729</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>radians</primary>
-        </indexterm>
-        <literal><function>radians(<type>dp</type>)</function></literal>
-       </entry>
-       <entry><type>dp</type></entry>
-       <entry>degrees to radians</entry>
-       <entry><literal>radians(45.0)</literal></entry>
-       <entry><literal>0.785398163397448</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>random</primary>
-        </indexterm>
-        <literal><function>random()</function></literal>
-       </entry>
-       <entry><type>dp</type></entry>
-       <entry>random value in the range 0.0 &lt;= x &lt; 1.0</entry>
-       <entry><literal>random()</literal></entry>
-       <entry></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>round</primary>
-        </indexterm>
-        <literal><function>round(<type>dp</type> or <type>numeric</type>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>round to nearest integer</entry>
-       <entry><literal>round(42.4)</literal></entry>
-       <entry><literal>42</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>round(<parameter>v</parameter> <type>numeric</type>, <parameter>s</parameter> <type>int</type>)</function></literal></entry>
-       <entry><type>numeric</type></entry>
-       <entry>round to <parameter>s</parameter> decimal places</entry>
-       <entry><literal>round(42.4382, 2)</literal></entry>
-       <entry><literal>42.44</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>setseed</primary>
-        </indexterm>
-        <literal><function>setseed(<type>dp</type>)</function></literal>
-       </entry>
-       <entry><type>void</type></entry>
-       <entry>set seed for subsequent <literal>random()</literal> calls (value between -1.0 and
-       1.0, inclusive)</entry>
-       <entry><literal>setseed(0.54823)</literal></entry>
-       <entry></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>sign</primary>
-        </indexterm>
-        <literal><function>sign(<type>dp</type> or <type>numeric</type>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>sign of the argument (-1, 0, +1)</entry>
-       <entry><literal>sign(-8.4)</literal></entry>
-       <entry><literal>-1</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>sqrt</primary>
-        </indexterm>
-        <literal><function>sqrt(<type>dp</type> or <type>numeric</type>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>square root</entry>
-       <entry><literal>sqrt(2.0)</literal></entry>
-       <entry><literal>1.4142135623731</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>trunc</primary>
-        </indexterm>
-        <literal><function>trunc(<type>dp</type> or <type>numeric</type>)</function></literal>
-       </entry>
-       <entry>(same as input)</entry>
-       <entry>truncate toward zero</entry>
-       <entry><literal>trunc(42.8)</literal></entry>
-       <entry><literal>42</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>trunc(<parameter>v</parameter> <type>numeric</type>, <parameter>s</parameter> <type>int</type>)</function></literal></entry>
-       <entry><type>numeric</type></entry>
-       <entry>truncate to <parameter>s</parameter> decimal places</entry>
-       <entry><literal>trunc(42.4382, 2)</literal></entry>
-       <entry><literal>42.43</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>width_bucket</primary>
-        </indexterm>
-        <literal><function>width_bucket(<parameter>op</parameter> <type>numeric</type>, <parameter>b1</parameter> <type>numeric</type>, <parameter>b2</parameter> <type>numeric</type>, <parameter>count</parameter> <type>int</type>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>return the bucket to which <parameter>operand</> would
-       be assigned in an equidepth histogram with <parameter>count</>
-       buckets, in the range <parameter>b1</> to <parameter>b2</></entry>
-       <entry><literal>width_bucket(5.35, 0.024, 10.06, 5)</literal></entry>
-       <entry><literal>3</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>width_bucket(<parameter>op</parameter> <type>dp</type>, <parameter>b1</parameter> <type>dp</type>, <parameter>b2</parameter> <type>dp</type>, <parameter>count</parameter> <type>int</type>)</function></literal></entry>
-       <entry><type>int</type></entry>
-       <entry>return the bucket to which <parameter>operand</> would
-       be assigned in an equidepth histogram with <parameter>count</>
-       buckets, in the range <parameter>b1</> to <parameter>b2</></entry>
-       <entry><literal>width_bucket(5.35, 0.024, 10.06, 5)</literal></entry>
-       <entry><literal>3</literal></entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   Finally, <xref linkend="functions-math-trig-table"> shows the
-   available trigonometric functions.  All trigonometric functions
-   take arguments and return values of type <type>double
-   precision</type>. Trigonometric functions arguments are expressed
-   in radians. Inverse functions return values are expressed in
-   radians.  See unit transformation functions
-   <literal><function>radians()</function></literal> and
-   <literal><function>degrees()</function></literal> above.
-  </para>
-
-   <table id="functions-math-trig-table">
-    <title>Trigonometric Functions</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <indexterm>
-         <primary>acos</primary>
-        </indexterm><literal><function>acos(<replaceable>x</replaceable>)</function></literal>
-       </entry>
-       <entry>inverse cosine</entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>asin</primary>
-        </indexterm>
-        <literal><function>asin(<replaceable>x</replaceable>)</function></literal>
-       </entry>
-       <entry>inverse sine</entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>atan</primary>
-        </indexterm>
-        <literal><function>atan(<replaceable>x</replaceable>)</function></literal>
-       </entry>
-       <entry>inverse tangent</entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>atan2</primary>
-        </indexterm>
-        <literal><function>atan2(<replaceable>y</replaceable>,
-        <replaceable>x</replaceable>)</function></literal>
-       </entry>
-       <entry>inverse tangent of
-        <literal><replaceable>y</replaceable>/<replaceable>x</replaceable></literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>cos</primary>
-        </indexterm>
-        <literal><function>cos(<replaceable>x</replaceable>)</function></literal>
-       </entry>
-       <entry>cosine</entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>cot</primary>
-        </indexterm>
-        <literal><function>cot(<replaceable>x</replaceable>)</function></literal>
-       </entry>
-       <entry>cotangent</entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>sin</primary>
-        </indexterm>
-        <literal><function>sin(<replaceable>x</replaceable>)</function></literal>
-       </entry>
-       <entry>sine</entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>tan</primary>
-        </indexterm>
-        <literal><function>tan(<replaceable>x</replaceable>)</function></literal>
-       </entry>
-       <entry>tangent</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  </sect1>
-
-
-  <sect1 id="functions-string">
-   <title>String Functions and Operators</title>
-&common;
-   <para>
-    This section describes functions and operators for examining and
-    manipulating string values.  Strings in this context include values
-    of the types <type>character</type>, <type>character varying</type>,
-    and <type>text</type>.  Unless otherwise noted, all
-    of the functions listed below work on all of these types, but be
-    wary of potential effects of automatic space-padding when using the
-    <type>character</type> type.  Some functions also exist
-    natively for the bit-string types.
-   </para>
-
-   <para>
-    <acronym>SQL</acronym> defines some string functions that use
-    key words, rather than commas, to separate
-    arguments.  Details are in
-    <xref linkend="functions-string-sql">.
-<!## PG>
-    <productname>PostgreSQL</> also provides versions of these functions
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> also provides versions of these functions
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> also provides versions of these functions
-<!## end>
-    that use the regular function invocation syntax
-    (see <xref linkend="functions-string-other">).
-   </para>
-
-   <note>
-    <para>
-     Before <productname>PostgreSQL</productname> 8.3, these functions would
-     silently accept values of several non-string data types as well, due to
-     the presence of implicit coercions from those data types to
-     <type>text</>.  Those coercions have been removed because they frequently
-     caused surprising behaviors.  However, the string concatenation operator
-     (<literal>||</>) still accepts non-string input, so long as at least one
-     input is of a string type, as shown in <xref
-     linkend="functions-string-sql">.  For other cases, insert an explicit
-     coercion to <type>text</> if you need to duplicate the previous behavior.
-    </para>
-   </note>
-
-   <table id="functions-string-sql">
-    <title><acronym>SQL</acronym> String Functions and Operators</title>
-    <tgroup cols="5">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Return Type</entry>
-       <entry>Description</entry>
-       <entry>Example</entry>
-       <entry>Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal><parameter>string</parameter> <literal>||</literal>
-        <parameter>string</parameter></literal></entry>
-       <entry> <type>text</type> </entry>
-       <entry>
-        String concatenation
-        <indexterm>
-         <primary>character string</primary>
-         <secondary>concatenation</secondary>
-        </indexterm>
-       </entry>
-       <entry><literal>'Post' || 'greSQL'</literal></entry>
-       <entry><literal>PostgreSQL</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <literal><parameter>string</parameter> <literal>||</literal>
-        <parameter>non-string</parameter></literal>
-        or
-        <literal><parameter>non-string</parameter> <literal>||</literal>
-        <parameter>string</parameter></literal>
-       </entry>
-       <entry> <type>text</type> </entry>
-       <entry>
-        String concatenation with one non-string input
-       </entry>
-       <entry><literal>'Value: ' || 42</literal></entry>
-       <entry><literal>Value: 42</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>bit_length</primary>
-        </indexterm>
-        <literal><function>bit_length(<parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>Number of bits in string</entry>
-       <entry><literal>bit_length('jose')</literal></entry>
-       <entry><literal>32</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>char_length</primary>
-        </indexterm>
-        <literal><function>char_length(<parameter>string</parameter>)</function></literal> or <literal><function>character_length(<parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>
-        Number of characters in string
-        <indexterm>
-         <primary>character string</primary>
-         <secondary>length</secondary>
-        </indexterm>
-        <indexterm>
-         <primary>length</primary>
-         <secondary sortas="character string">of a character string</secondary>
-         <see>character string, length</see>
-        </indexterm>
-       </entry>
-       <entry><literal>char_length('jose')</literal></entry>
-       <entry><literal>4</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>lower</primary>
-        </indexterm>
-        <literal><function>lower(<parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>Convert string to lower case</entry>
-       <entry><literal>lower('TOM')</literal></entry>
-       <entry><literal>tom</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>octet_length</primary>
-        </indexterm>
-        <literal><function>octet_length(<parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>Number of bytes in string</entry>
-       <entry><literal>octet_length('jose')</literal></entry>
-       <entry><literal>4</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>overlay</primary>
-        </indexterm>
-        <literal><function>overlay(<parameter>string</parameter> placing <parameter>string</parameter> from <type>int</type> <optional>for <type>int</type></optional>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Replace substring
-       </entry>
-       <entry><literal>overlay('Txxxxas' placing 'hom' from 2 for 4)</literal></entry>
-       <entry><literal>Thomas</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>position</primary>
-        </indexterm>
-        <literal><function>position(<parameter>substring</parameter> in <parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>Location of specified substring</entry>
-       <entry><literal>position('om' in 'Thomas')</literal></entry>
-       <entry><literal>3</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>substring</primary>
-        </indexterm>
-        <literal><function>substring(<parameter>string</parameter> <optional>from <type>int</type></optional> <optional>for <type>int</type></optional>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Extract substring
-       </entry>
-       <entry><literal>substring('Thomas' from 2 for 3)</literal></entry>
-       <entry><literal>hom</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>substring(<parameter>string</parameter> from <replaceable>pattern</replaceable>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Extract substring matching POSIX regular expression. See
-        <xref linkend="functions-matching"> for more information on pattern
-        matching.
-       </entry>
-       <entry><literal>substring('Thomas' from '...$')</literal></entry>
-       <entry><literal>mas</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>substring(<parameter>string</parameter> from <replaceable>pattern</replaceable> for <replaceable>escape</replaceable>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Extract substring matching <acronym>SQL</acronym> regular expression.
-        See <xref linkend="functions-matching"> for more information on
-        pattern matching.
-       </entry>
-       <entry><literal>substring('Thomas' from '%#"o_a#"_' for '#')</literal></entry>
-       <entry><literal>oma</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>trim</primary>
-        </indexterm>
-        <literal><function>trim(<optional>leading | trailing | both</optional>
-        <optional><parameter>characters</parameter></optional> from
-        <parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Remove the longest string containing only the
-        <parameter>characters</parameter> (a space by default) from the
-        start/end/both ends of the <parameter>string</parameter>
-       </entry>
-       <entry><literal>trim(both 'x' from 'xTomxx')</literal></entry>
-       <entry><literal>Tom</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>upper</primary>
-        </indexterm>
-        <literal><function>upper(<parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>Convert string to upper case</entry>
-       <entry><literal>upper('tom')</literal></entry>
-       <entry><literal>TOM</literal></entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    Additional string manipulation functions are available and are
-    listed in <xref linkend="functions-string-other">.  Some of them are used internally to implement the
-    <acronym>SQL</acronym>-standard string functions listed in <xref linkend="functions-string-sql">.
-   </para>
-
-   <table id="functions-string-other">
-    <title>Other String Functions</title>
-    <tgroup cols="5">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Return Type</entry>
-       <entry>Description</entry>
-       <entry>Example</entry>
-       <entry>Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <indexterm>
-         <primary>ascii</primary>
-        </indexterm>
-        <literal><function>ascii(<parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>
-        <acronym>ASCII</acronym> code of the first character of the
-        argument.  For <acronym>UTF8</acronym> returns the Unicode code
-        point of the character.  For other multibyte encodings, the
-        argument must be an <acronym>ASCII</acronym> character.
-       </entry>
-       <entry><literal>ascii('x')</literal></entry>
-       <entry><literal>120</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>btrim</primary>
-        </indexterm>
-        <literal><function>btrim(<parameter>string</parameter> <type>text</type>
-        <optional>, <parameter>characters</parameter> <type>text</type></optional>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Remove the longest string consisting only of characters
-        in <parameter>characters</parameter> (a space by default)
-        from the start and end of <parameter>string</parameter>
-       </entry>
-       <entry><literal>btrim('xyxtrimyyx', 'xy')</literal></entry>
-       <entry><literal>trim</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>chr</primary>
-        </indexterm>
-        <literal><function>chr(<type>int</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Character with the given code. For <acronym>UTF8</acronym> the
-        argument is treated as a Unicode code point. For other multibyte
-        encodings the argument must designate an
-        <acronym>ASCII</acronym> character.  The NULL (0) character is not
-        allowed because text data types cannot store such bytes.
-       </entry>
-       <entry><literal>chr(65)</literal></entry>
-       <entry><literal>A</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>concat</primary>
-        </indexterm>
-        <literal><function>concat(<parameter>str</parameter> <type>"any"</type>
-         [, <parameter>str</parameter> <type>"any"</type> [, ...] ])</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Concatenate all arguments. NULL arguments are ignored.
-       </entry>
-       <entry><literal>concat('abcde', 2, NULL, 22)</literal></entry>
-       <entry><literal>abcde222</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>concat_ws</primary>
-        </indexterm>
-        <literal><function>concat_ws(<parameter>sep</parameter> <type>text</type>,
-        <parameter>str</parameter> <type>"any"</type>
-        [, <parameter>str</parameter> <type>"any"</type> [, ...] ])</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Concatenate all but first arguments with separators. The first
-        parameter is used as a separator. NULL arguments are ignored.
-       </entry>
-       <entry><literal>concat_ws(',', 'abcde', 2, NULL, 22)</literal></entry>
-       <entry><literal>abcde,2,22</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>convert</primary>
-        </indexterm>
-        <literal><function>convert(<parameter>string</parameter> <type>bytea</type>,
-        <parameter>src_encoding</parameter> <type>name</type>,
-        <parameter>dest_encoding</parameter> <type>name</type>)</function></literal>
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Convert string to <parameter>dest_encoding</parameter>.  The
-        original encoding is specified by
-        <parameter>src_encoding</parameter>. The
-        <parameter>string</parameter> must be valid in this encoding.
-        Conversions can be defined by <command>CREATE CONVERSION</command>.
-        Also there are some predefined conversions. See <xref
-        linkend="conversion-names"> for available conversions.
-       </entry>
-       <entry><literal>convert('text_in_utf8', 'UTF8', 'LATIN1')</literal></entry>
-       <entry><literal>text_in_utf8</literal> represented in Latin-1
-       encoding (ISO 8859-1)</entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>convert_from</primary>
-        </indexterm>
-        <literal><function>convert_from(<parameter>string</parameter> <type>bytea</type>,
-        <parameter>src_encoding</parameter> <type>name</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Convert string to the database encoding.  The original encoding
-        is specified by <parameter>src_encoding</parameter>. The
-        <parameter>string</parameter> must be valid in this encoding.
-       </entry>
-       <entry><literal>convert_from('text_in_utf8', 'UTF8')</literal></entry>
-       <entry><literal>text_in_utf8</literal> represented in the current database encoding</entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>convert_to</primary>
-        </indexterm>
-        <literal><function>convert_to(<parameter>string</parameter> <type>text</type>,
-        <parameter>dest_encoding</parameter> <type>name</type>)</function></literal>
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Convert string to <parameter>dest_encoding</parameter>.
-       </entry>
-       <entry><literal>convert_to('some text', 'UTF8')</literal></entry>
-       <entry><literal>some text</literal> represented in the UTF8 encoding</entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>decode</primary>
-        </indexterm>
-        <literal><function>decode(<parameter>string</parameter> <type>text</type>,
-        <parameter>type</parameter> <type>text</type>)</function></literal>
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Decode binary data from <parameter>string</parameter> previously
-        encoded with <function>encode</>.  Parameter type is same as in <function>encode</>.
-       </entry>
-       <entry><literal>decode('MTIzAAE=', 'base64')</literal></entry>
-       <entry><literal>123\000\001</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>encode</primary>
-        </indexterm>
-        <literal><function>encode(<parameter>data</parameter> <type>bytea</type>,
-        <parameter>type</parameter> <type>text</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Encode binary data to different representation.  Supported
-        types are: <literal>base64</>, <literal>hex</>, <literal>escape</>.
-        <literal>Escape</> merely outputs null bytes as <literal>\000</> and
-        doubles backslashes.
-       </entry>
-       <entry><literal>encode(E'123\\000\\001', 'base64')</literal></entry>
-       <entry><literal>MTIzAAE=</literal></entry>
-      </row>
-
-      <row>
-       <entry id="format">
-        <indexterm>
-         <primary>format</primary>
-        </indexterm>
-        <literal><function>format</function>(<parameter>formatstr</parameter> <type>text</type>
-        [, <parameter>str</parameter> <type>"any"</type> [, ...] ])</literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-         Format a string.  This function is similar to the C function
-         <function>sprintf</>; but only the following conversions
-         are recognized: <literal>%s</literal> interpolates the corresponding
-         argument as a string; <literal>%I</literal> escapes its argument as
-         an SQL identifier; <literal>%L</literal> escapes its argument as an
-         SQL literal; <literal>%%</literal> outputs a literal <literal>%</>.
-         A conversion can reference an explicit parameter position by preceding
-         the conversion specifier with <literal><replaceable>n</>$</>, where
-         <replaceable>n</replaceable> is the argument position.
-         See also <xref linkend="plpgsql-quote-literal-example">.
-       </entry>
-       <entry><literal>format('Hello %s, %1$s', 'World')</literal></entry>
-       <entry><literal>Hello World, World</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>initcap</primary>
-        </indexterm>
-        <literal><function>initcap(<parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Convert the first letter of each word to upper case and the
-        rest to lower case. Words are sequences of alphanumeric
-        characters separated by non-alphanumeric characters.
-       </entry>
-       <entry><literal>initcap('hi THOMAS')</literal></entry>
-       <entry><literal>Hi Thomas</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>left</primary>
-        </indexterm>
-        <literal><function>left(<parameter>str</parameter> <type>text</type>,
-        <parameter>n</parameter> <type>int</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Return first <replaceable>n</> characters in the string. When <replaceable>n</>
-        is negative, return all but last |<replaceable>n</>| characters.
-        </entry>
-       <entry><literal>left('abcde', 2)</literal></entry>
-       <entry><literal>ab</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>length</primary>
-        </indexterm>
-        <literal><function>length(<parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>
-        Number of characters in <parameter>string</parameter>
-       </entry>
-       <entry><literal>length('jose')</literal></entry>
-       <entry><literal>4</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>length(<parameter>string</parameter><type>bytea</type>,
-        <parameter>encoding</parameter> <type>name</type> )</function></literal></entry>
-       <entry><type>int</type></entry>
-       <entry>
-        Number of characters in <parameter>string</parameter> in the given
-        <parameter>encoding</parameter>. The <parameter>string</parameter>
-        must be valid in this encoding.
-       </entry>
-       <entry><literal>length('jose', 'UTF8')</literal></entry>
-       <entry><literal>4</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>lpad</primary>
-        </indexterm>
-        <literal><function>lpad(<parameter>string</parameter> <type>text</type>,
-        <parameter>length</parameter> <type>int</type>
-        <optional>, <parameter>fill</parameter> <type>text</type></optional>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Fill up the <parameter>string</parameter> to length
-        <parameter>length</parameter> by prepending the characters
-        <parameter>fill</parameter> (a space by default).  If the
-        <parameter>string</parameter> is already longer than
-        <parameter>length</parameter> then it is truncated (on the
-        right).
-       </entry>
-       <entry><literal>lpad('hi', 5, 'xy')</literal></entry>
-       <entry><literal>xyxhi</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>ltrim</primary>
-        </indexterm>
-        <literal><function>ltrim(<parameter>string</parameter> <type>text</type>
-        <optional>, <parameter>characters</parameter> <type>text</type></optional>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Remove the longest string containing only characters from
-        <parameter>characters</parameter> (a space by default) from the start of
-        <parameter>string</parameter>
-       </entry>
-       <entry><literal>ltrim('zzzytrim', 'xyz')</literal></entry>
-       <entry><literal>trim</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>md5</primary>
-        </indexterm>
-        <literal><function>md5(<parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Calculates the MD5 hash of <parameter>string</parameter>,
-        returning the result in hexadecimal
-       </entry>
-       <entry><literal>md5('abc')</literal></entry>
-       <entry><literal>900150983cd24fb0 d6963f7d28e17f72</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>pg_client_encoding</primary>
-        </indexterm>
-        <literal><function>pg_client_encoding()</function></literal>
-       </entry>
-       <entry><type>name</type></entry>
-       <entry>
-        Current client encoding name
-       </entry>
-       <entry><literal>pg_client_encoding()</literal></entry>
-       <entry><literal>SQL_ASCII</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>quote_ident</primary>
-        </indexterm>
-        <literal><function>quote_ident(<parameter>string</parameter> <type>text</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Return the given string suitably quoted to be used as an identifier
-        in an <acronym>SQL</acronym> statement string.
-        Quotes are added only if necessary (i.e., if the string contains
-        non-identifier characters or would be case-folded).
-        Embedded quotes are properly doubled.
-        See also <xref linkend="plpgsql-quote-literal-example">.
-       </entry>
-       <entry><literal>quote_ident('Foo bar')</literal></entry>
-       <entry><literal>"Foo bar"</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>quote_literal</primary>
-        </indexterm>
-        <literal><function>quote_literal(<parameter>string</parameter> <type>text</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Return the given string suitably quoted to be used as a string literal
-        in an <acronym>SQL</acronym> statement string.
-        Embedded single-quotes and backslashes are properly doubled.
-        Note that <function>quote_literal</function> returns null on null
-        input; if the argument might be null,
-        <function>quote_nullable</function> is often more suitable.
-        See also <xref linkend="plpgsql-quote-literal-example">.
-       </entry>
-       <entry><literal>quote_literal('O\'Reilly')</literal></entry>
-       <entry><literal>'O''Reilly'</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>quote_literal(<parameter>value</parameter> <type>anyelement</type>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Coerce the given value to text and then quote it as a literal.
-        Embedded single-quotes and backslashes are properly doubled.
-       </entry>
-       <entry><literal>quote_literal(42.5)</literal></entry>
-       <entry><literal>'42.5'</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>quote_nullable</primary>
-        </indexterm>
-        <literal><function>quote_nullable(<parameter>string</parameter> <type>text</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Return the given string suitably quoted to be used as a string literal
-        in an <acronym>SQL</acronym> statement string; or, if the argument
-        is null, return <literal>NULL</>.
-        Embedded single-quotes and backslashes are properly doubled.
-        See also <xref linkend="plpgsql-quote-literal-example">.
-       </entry>
-       <entry><literal>quote_nullable(NULL)</literal></entry>
-       <entry><literal>NULL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>quote_nullable(<parameter>value</parameter> <type>anyelement</type>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Coerce the given value to text and then quote it as a literal;
-        or, if the argument is null, return <literal>NULL</>.
-        Embedded single-quotes and backslashes are properly doubled.
-       </entry>
-       <entry><literal>quote_nullable(42.5)</literal></entry>
-       <entry><literal>'42.5'</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>regexp_matches</primary>
-        </indexterm>
-        <literal><function>regexp_matches(<parameter>string</parameter> <type>text</type>, <parameter>pattern</parameter> <type>text</type> [, <parameter>flags</parameter> <type>text</type>])</function></literal>
-       </entry>
-       <entry><type>setof text[]</type></entry>
-       <entry>
-        Return all captured substrings resulting from matching a POSIX regular
-        expression against the <parameter>string</parameter>. See
-        <xref linkend="functions-posix-regexp"> for more information.
-       </entry>
-       <entry><literal>regexp_matches('foobarbequebaz', '(bar)(beque)')</literal></entry>
-       <entry><literal>{bar,beque}</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>regexp_replace</primary>
-        </indexterm>
-        <literal><function>regexp_replace(<parameter>string</parameter> <type>text</type>, <parameter>pattern</parameter> <type>text</type>, <parameter>replacement</parameter> <type>text</type> [, <parameter>flags</parameter> <type>text</type>])</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Replace substring(s) matching a POSIX regular expression. See
-        <xref linkend="functions-posix-regexp"> for more information.
-       </entry>
-       <entry><literal>regexp_replace('Thomas', '.[mN]a.', 'M')</literal></entry>
-       <entry><literal>ThM</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>regexp_split_to_array</primary>
-        </indexterm>
-        <literal><function>regexp_split_to_array(<parameter>string</parameter> <type>text</type>, <parameter>pattern</parameter> <type>text</type> [, <parameter>flags</parameter> <type>text</type> ])</function></literal>
-       </entry>
-       <entry><type>text[]</type></entry>
-       <entry>
-        Split <parameter>string</parameter> using a POSIX regular expression as
-        the delimiter.  See <xref linkend="functions-posix-regexp"> for more
-        information.
-       </entry>
-       <entry><literal>regexp_split_to_array('hello world', E'\\s+')</literal></entry>
-       <entry><literal>{hello,world}</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>regexp_split_to_table</primary>
-        </indexterm>
-        <literal><function>regexp_split_to_table(<parameter>string</parameter> <type>text</type>, <parameter>pattern</parameter> <type>text</type> [, <parameter>flags</parameter> <type>text</type>])</function></literal>
-       </entry>
-       <entry><type>setof text</type></entry>
-       <entry>
-        Split <parameter>string</parameter> using a POSIX regular expression as
-        the delimiter.  See <xref linkend="functions-posix-regexp"> for more
-        information.
-       </entry>
-       <entry><literal>regexp_split_to_table('hello world', E'\\s+')</literal></entry>
-       <entry><literal>hello</literal><para><literal>world</literal></para> (2 rows)</entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>repeat</primary>
-        </indexterm>
-        <literal><function>repeat(<parameter>string</parameter> <type>text</type>, <parameter>number</parameter> <type>int</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>Repeat <parameter>string</parameter> the specified
-       <parameter>number</parameter> of times</entry>
-       <entry><literal>repeat('Pg', 4)</literal></entry>
-       <entry><literal>PgPgPgPg</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>replace</primary>
-        </indexterm>
-        <literal><function>replace(<parameter>string</parameter> <type>text</type>,
-        <parameter>from</parameter> <type>text</type>,
-        <parameter>to</parameter> <type>text</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>Replace all occurrences in <parameter>string</parameter> of substring
-        <parameter>from</parameter> with substring <parameter>to</parameter>
-       </entry>
-       <entry><literal>replace('abcdefabcdef', 'cd', 'XX')</literal></entry>
-       <entry><literal>abXXefabXXef</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>reverse</primary>
-        </indexterm>
-        <literal><function>reverse(<parameter>str</parameter>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Return reversed string.
-       </entry>
-       <entry><literal>reverse('abcde')</literal></entry>
-       <entry><literal>edcba</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>right</primary>
-        </indexterm>
-        <literal><function>right(<parameter>str</parameter> <type>text</type>,
-         <parameter>n</parameter> <type>int</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Return last <replaceable>n</> characters in the string. When <replaceable>n</>
-        is negative, return all but first |<replaceable>n</>| characters.
-       </entry>
-       <entry><literal>right('abcde', 2)</literal></entry>
-       <entry><literal>de</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>rpad</primary>
-        </indexterm>
-        <literal><function>rpad(<parameter>string</parameter> <type>text</type>,
-        <parameter>length</parameter> <type>int</type>
-        <optional>, <parameter>fill</parameter> <type>text</type></optional>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Fill up the <parameter>string</parameter> to length
-        <parameter>length</parameter> by appending the characters
-        <parameter>fill</parameter> (a space by default).  If the
-        <parameter>string</parameter> is already longer than
-        <parameter>length</parameter> then it is truncated.
-       </entry>
-       <entry><literal>rpad('hi', 5, 'xy')</literal></entry>
-       <entry><literal>hixyx</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>rtrim</primary>
-        </indexterm>
-        <literal><function>rtrim(<parameter>string</parameter> <type>text</type>
-         <optional>, <parameter>characters</parameter> <type>text</type></optional>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Remove the longest string containing only characters from
-        <parameter>characters</parameter> (a space by default) from the end of
-        <parameter>string</parameter>
-       </entry>
-       <entry><literal>rtrim('trimxxxx', 'x')</literal></entry>
-       <entry><literal>trim</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>split_part</primary>
-        </indexterm>
-        <literal><function>split_part(<parameter>string</parameter> <type>text</type>,
-        <parameter>delimiter</parameter> <type>text</type>,
-        <parameter>field</parameter> <type>int</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>Split <parameter>string</parameter> on <parameter>delimiter</parameter>
-        and return the given field (counting from one)
-       </entry>
-       <entry><literal>split_part('abc~@~def~@~ghi', '~@~', 2)</literal></entry>
-       <entry><literal>def</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>strpos</primary>
-        </indexterm>
-        <literal><function>strpos(<parameter>string</parameter>, <parameter>substring</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>
-        Location of specified substring (same as
-        <literal>position(<parameter>substring</parameter> in
-         <parameter>string</parameter>)</literal>, but note the reversed
-        argument order)
-       </entry>
-       <entry><literal>strpos('high', 'ig')</literal></entry>
-       <entry><literal>2</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>substr</primary>
-        </indexterm>
-        <literal><function>substr(<parameter>string</parameter>, <parameter>from</parameter> <optional>, <parameter>count</parameter></optional>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Extract substring (same as
-        <literal>substring(<parameter>string</parameter> from <parameter>from</parameter> for <parameter>count</parameter>)</literal>)
-       </entry>
-       <entry><literal>substr('alphabet', 3, 2)</literal></entry>
-       <entry><literal>ph</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>to_ascii</primary>
-        </indexterm>
-        <literal><function>to_ascii(<parameter>string</parameter> <type>text</type>
-        <optional>, <parameter>encoding</parameter> <type>text</type></optional>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-       Convert <parameter>string</parameter> to <acronym>ASCII</acronym> from another encoding
-       (only supports conversion from  <literal>LATIN1</>, <literal>LATIN2</>, <literal>LATIN9</>,
-       and <literal>WIN1250</> encodings)
-       </entry>
-       <entry><literal>to_ascii('Karel')</literal></entry>
-       <entry><literal>Karel</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>to_hex</primary>
-        </indexterm>
-        <literal><function>to_hex(<parameter>number</parameter> <type>int</type>
-        or <type>bigint</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>Convert <parameter>number</parameter> to its equivalent hexadecimal
-        representation
-       </entry>
-       <entry><literal>to_hex(2147483647)</literal></entry>
-       <entry><literal>7fffffff</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>translate</primary>
-        </indexterm>
-        <literal><function>translate(<parameter>string</parameter> <type>text</type>,
-        <parameter>from</parameter> <type>text</type>,
-        <parameter>to</parameter> <type>text</type>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Any character in <parameter>string</parameter> that matches a
-        character in the <parameter>from</parameter> set is replaced by
-        the corresponding character in the <parameter>to</parameter>
-        set. If <parameter>from</parameter> is longer than
-        <parameter>to</parameter>, occurrences of the extra characters in
-        <parameter>from</parameter> are removed.
-       </entry>
-       <entry><literal>translate('12345', '143', 'ax')</literal></entry>
-       <entry><literal>a2x5</literal></entry>
-      </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-   See also the aggregate function <function>string_agg</function> in
-   <xref linkend="functions-aggregate">.
-   </para>
-
-   <table id="conversion-names">
-    <title>Built-in Conversions</title>
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Conversion Name
-        <footnote>
-         <para>
-          The conversion names follow a standard naming scheme: The
-          official name of the source encoding with all
-          non-alphanumeric characters replaced by underscores, followed
-          by <literal>_to_</literal>, followed by the similarly processed
-          destination encoding name. Therefore, the names might deviate
-          from the customary encoding names.
-         </para>
-        </footnote>
-       </entry>
-       <entry>Source Encoding</entry>
-       <entry>Destination Encoding</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal>ascii_to_mic</literal></entry>
-       <entry><literal>SQL_ASCII</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>ascii_to_utf8</literal></entry>
-       <entry><literal>SQL_ASCII</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>big5_to_euc_tw</literal></entry>
-       <entry><literal>BIG5</literal></entry>
-       <entry><literal>EUC_TW</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>big5_to_mic</literal></entry>
-       <entry><literal>BIG5</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>big5_to_utf8</literal></entry>
-       <entry><literal>BIG5</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_cn_to_mic</literal></entry>
-       <entry><literal>EUC_CN</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_cn_to_utf8</literal></entry>
-       <entry><literal>EUC_CN</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_jp_to_mic</literal></entry>
-       <entry><literal>EUC_JP</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_jp_to_sjis</literal></entry>
-       <entry><literal>EUC_JP</literal></entry>
-       <entry><literal>SJIS</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_jp_to_utf8</literal></entry>
-       <entry><literal>EUC_JP</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_kr_to_mic</literal></entry>
-       <entry><literal>EUC_KR</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_kr_to_utf8</literal></entry>
-       <entry><literal>EUC_KR</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_tw_to_big5</literal></entry>
-       <entry><literal>EUC_TW</literal></entry>
-       <entry><literal>BIG5</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_tw_to_mic</literal></entry>
-       <entry><literal>EUC_TW</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_tw_to_utf8</literal></entry>
-       <entry><literal>EUC_TW</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>gb18030_to_utf8</literal></entry>
-       <entry><literal>GB18030</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>gbk_to_utf8</literal></entry>
-       <entry><literal>GBK</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_10_to_utf8</literal></entry>
-       <entry><literal>LATIN6</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_13_to_utf8</literal></entry>
-       <entry><literal>LATIN7</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_14_to_utf8</literal></entry>
-       <entry><literal>LATIN8</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_15_to_utf8</literal></entry>
-       <entry><literal>LATIN9</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_16_to_utf8</literal></entry>
-       <entry><literal>LATIN10</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_1_to_mic</literal></entry>
-       <entry><literal>LATIN1</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_1_to_utf8</literal></entry>
-       <entry><literal>LATIN1</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_2_to_mic</literal></entry>
-       <entry><literal>LATIN2</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_2_to_utf8</literal></entry>
-       <entry><literal>LATIN2</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_2_to_windows_1250</literal></entry>
-       <entry><literal>LATIN2</literal></entry>
-       <entry><literal>WIN1250</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_3_to_mic</literal></entry>
-       <entry><literal>LATIN3</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_3_to_utf8</literal></entry>
-       <entry><literal>LATIN3</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_4_to_mic</literal></entry>
-       <entry><literal>LATIN4</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_4_to_utf8</literal></entry>
-       <entry><literal>LATIN4</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_5_to_koi8_r</literal></entry>
-       <entry><literal>ISO_8859_5</literal></entry>
-       <entry><literal>KOI8R</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_5_to_mic</literal></entry>
-       <entry><literal>ISO_8859_5</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_5_to_utf8</literal></entry>
-       <entry><literal>ISO_8859_5</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_5_to_windows_1251</literal></entry>
-       <entry><literal>ISO_8859_5</literal></entry>
-       <entry><literal>WIN1251</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_5_to_windows_866</literal></entry>
-       <entry><literal>ISO_8859_5</literal></entry>
-       <entry><literal>WIN866</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_6_to_utf8</literal></entry>
-       <entry><literal>ISO_8859_6</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_7_to_utf8</literal></entry>
-       <entry><literal>ISO_8859_7</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_8_to_utf8</literal></entry>
-       <entry><literal>ISO_8859_8</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>iso_8859_9_to_utf8</literal></entry>
-       <entry><literal>LATIN5</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>johab_to_utf8</literal></entry>
-       <entry><literal>JOHAB</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>koi8_r_to_iso_8859_5</literal></entry>
-       <entry><literal>KOI8R</literal></entry>
-       <entry><literal>ISO_8859_5</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>koi8_r_to_mic</literal></entry>
-       <entry><literal>KOI8R</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>koi8_r_to_utf8</literal></entry>
-       <entry><literal>KOI8R</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>koi8_r_to_windows_1251</literal></entry>
-       <entry><literal>KOI8R</literal></entry>
-       <entry><literal>WIN1251</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>koi8_r_to_windows_866</literal></entry>
-       <entry><literal>KOI8R</literal></entry>
-       <entry><literal>WIN866</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>koi8_u_to_utf8</literal></entry>
-       <entry><literal>KOI8U</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_ascii</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>SQL_ASCII</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_big5</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>BIG5</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_euc_cn</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>EUC_CN</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_euc_jp</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>EUC_JP</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_euc_kr</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>EUC_KR</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_euc_tw</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>EUC_TW</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_iso_8859_1</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>LATIN1</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_iso_8859_2</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>LATIN2</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_iso_8859_3</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>LATIN3</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_iso_8859_4</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>LATIN4</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_iso_8859_5</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>ISO_8859_5</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_koi8_r</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>KOI8R</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_sjis</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>SJIS</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_windows_1250</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>WIN1250</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_windows_1251</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>WIN1251</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>mic_to_windows_866</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-       <entry><literal>WIN866</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>sjis_to_euc_jp</literal></entry>
-       <entry><literal>SJIS</literal></entry>
-       <entry><literal>EUC_JP</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>sjis_to_mic</literal></entry>
-       <entry><literal>SJIS</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>sjis_to_utf8</literal></entry>
-       <entry><literal>SJIS</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>tcvn_to_utf8</literal></entry>
-       <entry><literal>WIN1258</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>uhc_to_utf8</literal></entry>
-       <entry><literal>UHC</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_ascii</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>SQL_ASCII</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_big5</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>BIG5</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_euc_cn</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>EUC_CN</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_euc_jp</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>EUC_JP</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_euc_kr</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>EUC_KR</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_euc_tw</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>EUC_TW</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_gb18030</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>GB18030</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_gbk</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>GBK</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_1</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>LATIN1</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_10</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>LATIN6</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_13</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>LATIN7</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_14</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>LATIN8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_15</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>LATIN9</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_16</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>LATIN10</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_2</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>LATIN2</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_3</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>LATIN3</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_4</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>LATIN4</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_5</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>ISO_8859_5</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_6</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>ISO_8859_6</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_7</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>ISO_8859_7</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_8</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>ISO_8859_8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_iso_8859_9</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>LATIN5</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_johab</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>JOHAB</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_koi8_r</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>KOI8R</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_koi8_u</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>KOI8U</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_sjis</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>SJIS</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_tcvn</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN1258</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_uhc</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>UHC</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_windows_1250</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN1250</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_windows_1251</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN1251</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_windows_1252</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN1252</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_windows_1253</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN1253</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_windows_1254</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN1254</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_windows_1255</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN1255</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_windows_1256</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN1256</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_windows_1257</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN1257</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_windows_866</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN866</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>utf8_to_windows_874</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>WIN874</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_1250_to_iso_8859_2</literal></entry>
-       <entry><literal>WIN1250</literal></entry>
-       <entry><literal>LATIN2</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_1250_to_mic</literal></entry>
-       <entry><literal>WIN1250</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_1250_to_utf8</literal></entry>
-       <entry><literal>WIN1250</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_1251_to_iso_8859_5</literal></entry>
-       <entry><literal>WIN1251</literal></entry>
-       <entry><literal>ISO_8859_5</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_1251_to_koi8_r</literal></entry>
-       <entry><literal>WIN1251</literal></entry>
-       <entry><literal>KOI8R</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_1251_to_mic</literal></entry>
-       <entry><literal>WIN1251</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_1251_to_utf8</literal></entry>
-       <entry><literal>WIN1251</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_1251_to_windows_866</literal></entry>
-       <entry><literal>WIN1251</literal></entry>
-       <entry><literal>WIN866</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_1252_to_utf8</literal></entry>
-       <entry><literal>WIN1252</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_1256_to_utf8</literal></entry>
-       <entry><literal>WIN1256</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_866_to_iso_8859_5</literal></entry>
-       <entry><literal>WIN866</literal></entry>
-       <entry><literal>ISO_8859_5</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_866_to_koi8_r</literal></entry>
-       <entry><literal>WIN866</literal></entry>
-       <entry><literal>KOI8R</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_866_to_mic</literal></entry>
-       <entry><literal>WIN866</literal></entry>
-       <entry><literal>MULE_INTERNAL</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_866_to_utf8</literal></entry>
-       <entry><literal>WIN866</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_866_to_windows_1251</literal></entry>
-       <entry><literal>WIN866</literal></entry>
-       <entry><literal>WIN</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>windows_874_to_utf8</literal></entry>
-       <entry><literal>WIN874</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_jis_2004_to_utf8</literal></entry>
-       <entry><literal>EUC_JIS_2004</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>ut8_to_euc_jis_2004</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>EUC_JIS_2004</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>shift_jis_2004_to_utf8</literal></entry>
-       <entry><literal>SHIFT_JIS_2004</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>ut8_to_shift_jis_2004</literal></entry>
-       <entry><literal>UTF8</literal></entry>
-       <entry><literal>SHIFT_JIS_2004</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>euc_jis_2004_to_shift_jis_2004</literal></entry>
-       <entry><literal>EUC_JIS_2004</literal></entry>
-       <entry><literal>SHIFT_JIS_2004</literal></entry>
-      </row>
-
-      <row>
-       <entry><literal>shift_jis_2004_to_euc_jis_2004</literal></entry>
-       <entry><literal>SHIFT_JIS_2004</literal></entry>
-       <entry><literal>EUC_JIS_2004</literal></entry>
-      </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-  </sect1>
-
-
-  <sect1 id="functions-binarystring">
-   <title>Binary String Functions and Operators</title>
-
-   <indexterm zone="functions-binarystring">
-    <primary>binary data</primary>
-    <secondary>functions</secondary>
-   </indexterm>
-&common;
-   <para>
-    This section describes functions and operators for examining and
-    manipulating values of type <type>bytea</type>.
-   </para>
-
-   <para>
-    <acronym>SQL</acronym> defines some string functions that use
-    key words, rather than commas, to separate
-    arguments.  Details are in
-    <xref linkend="functions-binarystring-sql">.
-<!## PG>
-    <productname>PostgreSQL</> also provides versions of these functions
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> also provides versions of these functions
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> also provides versions of these functions
-<!## end>
-    that use the regular function invocation syntax
-    (see <xref linkend="functions-binarystring-other">).
-   </para>
-
-   <table id="functions-binarystring-sql">
-    <title><acronym>SQL</acronym> Binary String Functions and Operators</title>
-    <tgroup cols="5">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Return Type</entry>
-       <entry>Description</entry>
-       <entry>Example</entry>
-       <entry>Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal><parameter>string</parameter> <literal>||</literal>
-        <parameter>string</parameter></literal></entry>
-       <entry> <type>bytea</type> </entry>
-       <entry>
-        String concatenation
-        <indexterm>
-         <primary>binary string</primary>
-         <secondary>concatenation</secondary>
-        </indexterm>
-       </entry>
-       <entry><literal>E'\\\\Post'::bytea || E'\\047gres\\000'::bytea</literal></entry>
-       <entry><literal>\\Post'gres\000</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>octet_length</primary>
-        </indexterm>
-        <literal><function>octet_length(<parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>Number of bytes in binary string</entry>
-       <entry><literal>octet_length(E'jo\\000se'::bytea)</literal></entry>
-       <entry><literal>5</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>overlay</primary>
-        </indexterm>
-        <literal><function>overlay(<parameter>string</parameter> placing <parameter>string</parameter> from <type>int</type> <optional>for <type>int</type></optional>)</function></literal>
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Replace substring
-       </entry>
-       <entry><literal>overlay(E'Th\\000omas'::bytea placing E'\\002\\003'::bytea from 2 for 3)</literal></entry>
-       <entry><literal>T\\002\\003mas</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>position</primary>
-        </indexterm>
-        <literal><function>position(<parameter>substring</parameter> in <parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>Location of specified substring</entry>
-      <entry><literal>position(E'\\000om'::bytea in E'Th\\000omas'::bytea)</literal></entry>
-       <entry><literal>3</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>substring</primary>
-        </indexterm>
-        <literal><function>substring(<parameter>string</parameter> <optional>from <type>int</type></optional> <optional>for <type>int</type></optional>)</function></literal>
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Extract substring
-       </entry>
-       <entry><literal>substring(E'Th\\000omas'::bytea from 2 for 3)</literal></entry>
-       <entry><literal>h\000o</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>trim</primary>
-        </indexterm>
-        <literal><function>trim(<optional>both</optional>
-        <parameter>bytes</parameter> from
-        <parameter>string</parameter>)</function></literal>
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Remove the longest string containing only the bytes in
-        <parameter>bytes</parameter> from the start
-        and end of <parameter>string</parameter>
-       </entry>
-       <entry><literal>trim(E'\\000'::bytea from E'\\000Tom\\000'::bytea)</literal></entry>
-       <entry><literal>Tom</literal></entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    Additional binary string manipulation functions are available and
-    are listed in <xref linkend="functions-binarystring-other">.  Some
-    of them are used internally to implement the
-    <acronym>SQL</acronym>-standard string functions listed in <xref
-    linkend="functions-binarystring-sql">.
-   </para>
-
-   <table id="functions-binarystring-other">
-    <title>Other Binary String Functions</title>
-    <tgroup cols="5">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Return Type</entry>
-       <entry>Description</entry>
-       <entry>Example</entry>
-       <entry>Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <indexterm>
-         <primary>btrim</primary>
-        </indexterm>
-        <literal><function>btrim(<parameter>string</parameter>
-        <type>bytea</type>, <parameter>bytes</parameter> <type>bytea</type>)</function></literal>
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Remove the longest string consisting only of bytes
-        in <parameter>bytes</parameter> from the start and end of
-        <parameter>string</parameter>
-      </entry>
-      <entry><literal>btrim(E'\\000trim\\000'::bytea, E'\\000'::bytea)</literal></entry>
-      <entry><literal>trim</literal></entry>
-     </row>
-
-     <row>
-      <entry>
-        <indexterm>
-         <primary>decode</primary>
-        </indexterm>
-       <literal><function>decode(<parameter>string</parameter> <type>text</type>,
-              <parameter>type</parameter> <type>text</type>)</function></literal>
-      </entry>
-      <entry><type>bytea</type></entry>
-      <entry>
-       Decode binary string from <parameter>string</parameter> previously
-       encoded with <function>encode</>.  Parameter type is same as in <function>encode</>.
-      </entry>
-      <entry><literal>decode(E'123\\000456', 'escape')</literal></entry>
-      <entry><literal>123\000456</literal></entry>
-     </row>
-
-     <row>
-      <entry>
-        <indexterm>
-         <primary>encode</primary>
-        </indexterm>
-       <literal><function>encode(<parameter>string</parameter> <type>bytea</type>,
-              <parameter>type</parameter> <type>text</type>)</function></literal>
-      </entry>
-      <entry><type>text</type></entry>
-      <entry>
-       Encode binary string to <acronym>ASCII</acronym>-only representation.  Supported
-       types are: <literal>base64</>, <literal>hex</>, <literal>escape</>.
-      </entry>
-      <entry><literal>encode(E'123\\000456'::bytea, 'escape')</literal></entry>
-      <entry><literal>123\000456</literal></entry>
-     </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>get_bit</primary>
-        </indexterm>
-        <literal><function>get_bit(<parameter>string</parameter>, <parameter>offset</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>
-        Extract bit from string
-       </entry>
-       <entry><literal>get_bit(E'Th\\000omas'::bytea, 45)</literal></entry>
-       <entry><literal>1</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>get_byte</primary>
-        </indexterm>
-        <literal><function>get_byte(<parameter>string</parameter>, <parameter>offset</parameter>)</function></literal>
-       </entry>
-       <entry><type>int</type></entry>
-       <entry>
-        Extract byte from string
-       </entry>
-       <entry><literal>get_byte(E'Th\\000omas'::bytea, 4)</literal></entry>
-       <entry><literal>109</literal></entry>
-      </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>length</primary>
-       </indexterm>
-       <literal><function>length(<parameter>string</parameter>)</function></literal>
-      </entry>
-      <entry><type>int</type></entry>
-      <entry>
-       Length of binary string
-       <indexterm>
-        <primary>binary string</primary>
-        <secondary>length</secondary>
-       </indexterm>
-       <indexterm>
-        <primary>length</primary>
-        <secondary sortas="binary string">of a binary string</secondary>
-        <see>binary strings, length</see>
-       </indexterm>
-      </entry>
-      <entry><literal>length(E'jo\\000se'::bytea)</literal></entry>
-      <entry><literal>5</literal></entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>md5</primary>
-       </indexterm>
-       <literal><function>md5(<parameter>string</parameter>)</function></literal>
-      </entry>
-      <entry><type>text</type></entry>
-      <entry>
-       Calculates the MD5 hash of <parameter>string</parameter>,
-       returning the result in hexadecimal
-      </entry>
-      <entry><literal>md5(E'Th\\000omas'::bytea)</literal></entry>
-      <entry><literal>8ab2d3c9689aaf18 b4958c334c82d8b1</literal></entry>
-     </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>set_bit</primary>
-        </indexterm>
-        <literal><function>set_bit(<parameter>string</parameter>,
-        <parameter>offset</parameter>, <parameter>newvalue</>)</function></literal>
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Set bit in string
-       </entry>
-       <entry><literal>set_bit(E'Th\\000omas'::bytea, 45, 0)</literal></entry>
-       <entry><literal>Th\000omAs</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <indexterm>
-         <primary>set_byte</primary>
-        </indexterm>
-        <literal><function>set_byte(<parameter>string</parameter>,
-        <parameter>offset</parameter>, <parameter>newvalue</>)</function></literal>
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Set byte in string
-       </entry>
-       <entry><literal>set_byte(E'Th\\000omas'::bytea, 4, 64)</literal></entry>
-       <entry><literal>Th\000o@as</literal></entry>
-      </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   <function>get_byte</> and <function>set_byte</> number the first byte
-   of a binary string as byte 0.
-   <function>get_bit</> and <function>set_bit</> number bits from the
-   right within each byte; for example bit 0 is the least significant bit of
-   the first byte, and bit 15 is the most significant bit of the second byte.
-  </para>
- </sect1>
-
-
-  <sect1 id="functions-bitstring">
-   <title>Bit String Functions and Operators</title>
-
-   <indexterm zone="functions-bitstring">
-    <primary>bit strings</primary>
-    <secondary>functions</secondary>
-   </indexterm>
-&common;
-   <para>
-    This section describes functions and operators for examining and
-    manipulating bit strings, that is values of the types
-    <type>bit</type> and <type>bit varying</type>.  Aside from the
-    usual comparison operators, the operators
-    shown in <xref linkend="functions-bit-string-op-table"> can be used.
-    Bit string operands of <literal>&amp;</literal>, <literal>|</literal>,
-    and <literal>#</literal> must be of equal length.  When bit
-    shifting, the original length of the string is preserved, as shown
-    in the examples.
-   </para>
-
-   <table id="functions-bit-string-op-table">
-    <title>Bit String Operators</title>
-
-    <tgroup cols="4">
-     <thead>
-      <row>
-       <entry>Operator</entry>
-       <entry>Description</entry>
-       <entry>Example</entry>
-       <entry>Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry> <literal>||</literal> </entry>
-       <entry>concatenation</entry>
-       <entry><literal>B'10001' || B'011'</literal></entry>
-       <entry><literal>10001011</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>&amp;</literal> </entry>
-       <entry>bitwise AND</entry>
-       <entry><literal>B'10001' &amp; B'01101'</literal></entry>
-       <entry><literal>00001</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>|</literal> </entry>
-       <entry>bitwise OR</entry>
-       <entry><literal>B'10001' | B'01101'</literal></entry>
-       <entry><literal>11101</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>#</literal> </entry>
-       <entry>bitwise XOR</entry>
-       <entry><literal>B'10001' # B'01101'</literal></entry>
-       <entry><literal>11100</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>~</literal> </entry>
-       <entry>bitwise NOT</entry>
-       <entry><literal>~ B'10001'</literal></entry>
-       <entry><literal>01110</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>&lt;&lt;</literal> </entry>
-       <entry>bitwise shift left</entry>
-       <entry><literal>B'10001' &lt;&lt; 3</literal></entry>
-       <entry><literal>01000</literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>&gt;&gt;</literal> </entry>
-       <entry>bitwise shift right</entry>
-       <entry><literal>B'10001' &gt;&gt; 2</literal></entry>
-       <entry><literal>00100</literal></entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    The following <acronym>SQL</acronym>-standard functions work on bit
-    strings as well as character strings:
-    <literal><function>length</function></literal>,
-    <literal><function>bit_length</function></literal>,
-    <literal><function>octet_length</function></literal>,
-    <literal><function>position</function></literal>,
-    <literal><function>substring</function></literal>,
-    <literal><function>overlay</function></literal>.
-   </para>
-
-   <para>
-    The following functions work on bit strings as well as binary
-    strings:
-    <literal><function>get_bit</function></literal>,
-    <literal><function>set_bit</function></literal>.
-    When working with a bit string, these functions number the first
-    (leftmost) bit of the string as bit 0.
-   </para>
-
-   <para>
-    In addition, it is possible to cast integral values to and from type
-    <type>bit</>.
-    Some examples:
-<programlisting>
-44::bit(10)                    <lineannotation>0000101100</lineannotation>
-44::bit(3)                     <lineannotation>100</lineannotation>
-cast(-44 as bit(12))           <lineannotation>111111010100</lineannotation>
-'1110'::bit(4)::integer        <lineannotation>14</lineannotation>
-</programlisting>
-    Note that casting to just <quote>bit</> means casting to
-    <literal>bit(1)</>, and so will deliver only the least significant
-    bit of the integer.
-   </para>
-
-    <note>
-     <para>
-      Prior to <productname>PostgreSQL</productname> 8.0, casting an
-      integer to <type>bit(n)</> would copy the leftmost <literal>n</>
-      bits of the integer, whereas now it copies the rightmost <literal>n</>
-      bits.  Also, casting an integer to a bit string width wider than
-      the integer itself will sign-extend on the left.
-     </para>
-    </note>
-
-  </sect1>
-
-
- <sect1 id="functions-matching">
-  <title>Pattern Matching</title>
-
-  <indexterm zone="functions-matching">
-   <primary>pattern matching</primary>
-  </indexterm>
-&common;
-   <para>
-    There are three separate approaches to pattern matching provided
-<!## PG>
-    by <productname>PostgreSQL</productname>: the traditional
-<!## end>
-<!## XC>
-    by <productname>Postgres-XC</productname>: the traditional
-<!## end>
-<!## XL>
-    by <productname>Postgres-XL</productname>: the traditional
-<!## end>
-    <acronym>SQL</acronym> <function>LIKE</function> operator, the
-    more recent <function>SIMILAR TO</function> operator (added in
-    SQL:1999), and <acronym>POSIX</acronym>-style regular
-    expressions.  Aside from the basic <quote>does this string match
-    this pattern?</> operators, functions are available to extract
-    or replace matching substrings and to split a string at matching
-    locations.
-   </para>
-
-   <tip>
-    <para>
-     If you have pattern matching needs that go beyond this,
-     consider writing a user-defined function in Perl or Tcl.
-    </para>
-   </tip>
-
-  <sect2 id="functions-like">
-   <title><function>LIKE</function></title>
-
-   <indexterm>
-    <primary>LIKE</primary>
-   </indexterm>
-
-<synopsis>
-<replaceable>string</replaceable> LIKE <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
-<replaceable>string</replaceable> NOT LIKE <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
-</synopsis>
-
-    <para>
-     The <function>LIKE</function> expression returns true if the
-     <replaceable>string</replaceable> matches the supplied
-     <replaceable>pattern</replaceable>.  (As
-     expected, the <function>NOT LIKE</function> expression returns
-     false if <function>LIKE</function> returns true, and vice versa.
-     An equivalent expression is
-     <literal>NOT (<replaceable>string</replaceable> LIKE
-      <replaceable>pattern</replaceable>)</literal>.)
-    </para>
-
-    <para>
-     If <replaceable>pattern</replaceable> does not contain percent
-     signs or underscores, then the pattern only represents the string
-     itself; in that case <function>LIKE</function> acts like the
-     equals operator.  An underscore (<literal>_</literal>) in
-     <replaceable>pattern</replaceable> stands for (matches) any single
-     character; a percent sign (<literal>%</literal>) matches any sequence
-     of zero or more characters.
-    </para>
-
-   <para>
-    Some examples:
-<programlisting>
-'abc' LIKE 'abc'    <lineannotation>true</lineannotation>
-'abc' LIKE 'a%'     <lineannotation>true</lineannotation>
-'abc' LIKE '_b_'    <lineannotation>true</lineannotation>
-'abc' LIKE 'c'      <lineannotation>false</lineannotation>
-</programlisting>
-   </para>
-
-   <para>
-    <function>LIKE</function> pattern matching always covers the entire
-    string.  Therefore, to match a sequence anywhere within a string, the
-    pattern must start and end with a percent sign.
-   </para>
-
-   <para>
-    To match a literal underscore or percent sign without matching
-    other characters, the respective character in
-    <replaceable>pattern</replaceable> must be
-    preceded by the escape character.  The default escape
-    character is the backslash but a different one can be selected by
-    using the <literal>ESCAPE</literal> clause.  To match the escape
-    character itself, write two escape characters.
-   </para>
-
-   <para>
-    Note that the backslash already has a special meaning in string literals,
-    so to write a pattern constant that contains a backslash you must write two
-    backslashes in an SQL statement (assuming escape string syntax is used, see
-    <xref linkend="sql-syntax-strings">).  Thus, writing a pattern that
-    actually matches a literal backslash means writing four backslashes in the
-    statement.  You can avoid this by selecting a different escape character
-    with <literal>ESCAPE</literal>; then a backslash is not special to
-    <function>LIKE</function> anymore. (But backslash is still special to the
-    string literal parser, so you still need two of them to match a backslash.)
-   </para>
-
-   <para>
-    It's also possible to select no escape character by writing
-    <literal>ESCAPE ''</literal>.  This effectively disables the
-    escape mechanism, which makes it impossible to turn off the
-    special meaning of underscore and percent signs in the pattern.
-   </para>
-
-   <para>
-    The key word <token>ILIKE</token> can be used instead of
-    <token>LIKE</token> to make the match case-insensitive according
-    to the active locale.  This is not in the <acronym>SQL</acronym> standard but is a
-<!## PG>
-    <productname>PostgreSQL</productname> extension.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> extension.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> extension.
-<!## end>
-   </para>
-
-   <para>
-    The operator <literal>~~</literal> is equivalent to
-    <function>LIKE</function>, and <literal>~~*</literal> corresponds to
-    <function>ILIKE</function>.  There are also
-    <literal>!~~</literal> and <literal>!~~*</literal> operators that
-    represent <function>NOT LIKE</function> and <function>NOT
-    ILIKE</function>, respectively.  All of these operators are
-<!## PG>
-    <productname>PostgreSQL</productname>-specific.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>-specific.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>-specific.
-<!## end>
-   </para>
-  </sect2>
-
-
-  <sect2 id="functions-similarto-regexp">
-   <title><function>SIMILAR TO</function> Regular Expressions</title>
-
-   <indexterm>
-    <primary>regular expression</primary>
-    <!-- <seealso>pattern matching</seealso> breaks index build -->
-   </indexterm>
-
-   <indexterm>
-    <primary>SIMILAR TO</primary>
-   </indexterm>
-   <indexterm>
-    <primary>substring</primary>
-   </indexterm>
-
-<synopsis>
-<replaceable>string</replaceable> SIMILAR TO <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
-<replaceable>string</replaceable> NOT SIMILAR TO <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
-</synopsis>
-&common;
-   <para>
-    The <function>SIMILAR TO</function> operator returns true or
-    false depending on whether its pattern matches the given string.
-    It is similar to <function>LIKE</function>, except that it
-    interprets the pattern using the SQL standard's definition of a
-    regular expression.  SQL regular expressions are a curious cross
-    between <function>LIKE</function> notation and common regular
-    expression notation.
-   </para>
-
-   <para>
-    Like <function>LIKE</function>, the <function>SIMILAR TO</function>
-    operator succeeds only if its pattern matches the entire string;
-    this is unlike common regular expression behavior where the pattern
-    can match any part of the string.
-    Also like
-    <function>LIKE</function>, <function>SIMILAR TO</function> uses
-    <literal>_</> and <literal>%</> as wildcard characters denoting
-    any single character and any string, respectively (these are
-    comparable to <literal>.</> and <literal>.*</> in POSIX regular
-    expressions).
-   </para>
-
-   <para>
-    In addition to these facilities borrowed from <function>LIKE</function>,
-    <function>SIMILAR TO</function> supports these pattern-matching
-    metacharacters borrowed from POSIX regular expressions:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <literal>|</literal> denotes alternation (either of two alternatives).
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>*</literal> denotes repetition of the previous item zero
-      or more times.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>+</literal> denotes repetition of the previous item one
-      or more times.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>?</literal> denotes repetition of the previous item zero
-      or one time.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>{</><replaceable>m</><literal>}</literal> denotes repetition
-      of the previous item exactly <replaceable>m</> times.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>{</><replaceable>m</><literal>,}</literal> denotes repetition
-      of the previous item <replaceable>m</> or more times.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}</>
-      denotes repetition of the previous item at least <replaceable>m</> and
-      not more than <replaceable>n</> times.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Parentheses <literal>()</literal> can be used to group items into
-      a single logical item.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      A bracket expression <literal>[...]</literal> specifies a character
-      class, just as in POSIX regular expressions.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-    Notice that the period (<literal>.</>) is not a metacharacter
-    for <function>SIMILAR TO</>.
-   </para>
-
-   <para>
-    As with <function>LIKE</>, a backslash disables the special meaning
-    of any of these metacharacters; or a different escape character can
-    be specified with <literal>ESCAPE</>.
-   </para>
-
-   <para>
-    Some examples:
-<programlisting>
-'abc' SIMILAR TO 'abc'      <lineannotation>true</lineannotation>
-'abc' SIMILAR TO 'a'        <lineannotation>false</lineannotation>
-'abc' SIMILAR TO '%(b|d)%'  <lineannotation>true</lineannotation>
-'abc' SIMILAR TO '(b|c)%'   <lineannotation>false</lineannotation>
-</programlisting>
-   </para>
-
-   <para>
-    The <function>substring</> function with three parameters,
-    <function>substring(<replaceable>string</replaceable> from
-    <replaceable>pattern</replaceable> for
-    <replaceable>escape-character</replaceable>)</function>, provides
-    extraction of a substring that matches an SQL
-    regular expression pattern.  As with <literal>SIMILAR TO</>, the
-    specified pattern must match the entire data string, or else the
-    function fails and returns null.  To indicate the part of the
-    pattern that should be returned on success, the pattern must contain
-    two occurrences of the escape character followed by a double quote
-    (<literal>"</>). <!-- " font-lock sanity -->
-    The text matching the portion of the pattern
-    between these markers is returned.
-   </para>
-
-   <para>
-    Some examples, with <literal>#&quot;</> delimiting the return string:
-<programlisting>
-substring('foobar' from '%#"o_b#"%' for '#')   <lineannotation>oob</lineannotation>
-substring('foobar' from '#"o_b#"%' for '#')    <lineannotation>NULL</lineannotation>
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="functions-posix-regexp">
-   <title><acronym>POSIX</acronym> Regular Expressions</title>
-
-   <indexterm zone="functions-posix-regexp">
-    <primary>regular expression</primary>
-    <seealso>pattern matching</seealso>
-   </indexterm>
-   <indexterm>
-    <primary>substring</primary>
-   </indexterm>
-   <indexterm>
-    <primary>regexp_replace</primary>
-   </indexterm>
-   <indexterm>
-    <primary>regexp_matches</primary>
-   </indexterm>
-   <indexterm>
-    <primary>regexp_split_to_table</primary>
-   </indexterm>
-   <indexterm>
-    <primary>regexp_split_to_array</primary>
-   </indexterm>
-&common;
-   <para>
-    <xref linkend="functions-posix-table"> lists the available
-    operators for pattern matching using POSIX regular expressions.
-   </para>
-
-   <table id="functions-posix-table">
-    <title>Regular Expression Match Operators</title>
-
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Operator</entry>
-       <entry>Description</entry>
-       <entry>Example</entry>
-      </row>
-     </thead>
-
-      <tbody>
-       <row>
-        <entry> <literal>~</literal> </entry>
-        <entry>Matches regular expression, case sensitive</entry>
-        <entry><literal>'thomas' ~ '.*thomas.*'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>~*</literal> </entry>
-        <entry>Matches regular expression, case insensitive</entry>
-        <entry><literal>'thomas' ~* '.*Thomas.*'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>!~</literal> </entry>
-        <entry>Does not match regular expression, case sensitive</entry>
-        <entry><literal>'thomas' !~ '.*Thomas.*'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>!~*</literal> </entry>
-        <entry>Does not match regular expression, case insensitive</entry>
-        <entry><literal>'thomas' !~* '.*vadim.*'</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-    <para>
-     <acronym>POSIX</acronym> regular expressions provide a more
-     powerful means for pattern matching than the <function>LIKE</function> and
-     <function>SIMILAR TO</> operators.
-     Many Unix tools such as <command>egrep</command>,
-     <command>sed</command>, or <command>awk</command> use a pattern
-     matching language that is similar to the one described here.
-    </para>
-
-    <para>
-     A regular expression is a character sequence that is an
-     abbreviated definition of a set of strings (a <firstterm>regular
-     set</firstterm>).  A string is said to match a regular expression
-     if it is a member of the regular set described by the regular
-     expression.  As with <function>LIKE</function>, pattern characters
-     match string characters exactly unless they are special characters
-     in the regular expression language &mdash; but regular expressions use
-     different special characters than <function>LIKE</function> does.
-     Unlike <function>LIKE</function> patterns, a
-     regular expression is allowed to match anywhere within a string, unless
-     the regular expression is explicitly anchored to the beginning or
-     end of the string.
-    </para>
-
-    <para>
-     Some examples:
-<programlisting>
-'abc' ~ 'abc'    <lineannotation>true</lineannotation>
-'abc' ~ '^a'     <lineannotation>true</lineannotation>
-'abc' ~ '(b|d)'  <lineannotation>true</lineannotation>
-'abc' ~ '^(b|c)' <lineannotation>false</lineannotation>
-</programlisting>
-    </para>
-
-    <para>
-     The <acronym>POSIX</acronym> pattern language is described in much
-     greater detail below.
-    </para>
-
-    <para>
-     The <function>substring</> function with two parameters,
-     <function>substring(<replaceable>string</replaceable> from
-     <replaceable>pattern</replaceable>)</function>, provides extraction of a
-     substring
-     that matches a POSIX regular expression pattern.  It returns null if
-     there is no match, otherwise the portion of the text that matched the
-     pattern.  But if the pattern contains any parentheses, the portion
-     of the text that matched the first parenthesized subexpression (the
-     one whose left parenthesis comes first) is
-     returned.  You can put parentheses around the whole expression
-     if you want to use parentheses within it without triggering this
-     exception.  If you need parentheses in the pattern before the
-     subexpression you want to extract, see the non-capturing parentheses
-     described below.
-    </para>
-
-   <para>
-    Some examples:
-<programlisting>
-substring('foobar' from 'o.b')     <lineannotation>oob</lineannotation>
-substring('foobar' from 'o(.)b')   <lineannotation>o</lineannotation>
-</programlisting>
-   </para>
-
-    <para>
-     The <function>regexp_replace</> function provides substitution of
-     new text for substrings that match POSIX regular expression patterns.
-     It has the syntax
-     <function>regexp_replace</function>(<replaceable>source</>,
-     <replaceable>pattern</>, <replaceable>replacement</>
-     <optional>, <replaceable>flags</> </optional>).
-     The <replaceable>source</> string is returned unchanged if
-     there is no match to the <replaceable>pattern</>.  If there is a
-     match, the <replaceable>source</> string is returned with the
-     <replaceable>replacement</> string substituted for the matching
-     substring.  The <replaceable>replacement</> string can contain
-     <literal>\</><replaceable>n</>, where <replaceable>n</> is 1
-     through 9, to indicate that the source substring matching the
-     <replaceable>n</>'th parenthesized subexpression of the pattern should be
-     inserted, and it can contain <literal>\&amp;</> to indicate that the
-     substring matching the entire pattern should be inserted.  Write
-     <literal>\\</> if you need to put a literal backslash in the replacement
-     text.  (As always, remember to double backslashes written in literal
-     constant strings, assuming escape string syntax is used.)
-     The <replaceable>flags</> parameter is an optional text
-     string containing zero or more single-letter flags that change the
-     function's behavior.  Flag <literal>i</> specifies case-insensitive
-     matching, while flag <literal>g</> specifies replacement of each matching
-     substring rather than only the first one.  Other supported flags are
-     described in <xref linkend="posix-embedded-options-table">.
-    </para>
-
-   <para>
-    Some examples:
-<programlisting>
-regexp_replace('foobarbaz', 'b..', 'X')
-                                   <lineannotation>fooXbaz</lineannotation>
-regexp_replace('foobarbaz', 'b..', 'X', 'g')
-                                   <lineannotation>fooXX</lineannotation>
-regexp_replace('foobarbaz', 'b(..)', E'X\\1Y', 'g')
-                                   <lineannotation>fooXarYXazY</lineannotation>
-</programlisting>
-   </para>
-
-    <para>
-     The <function>regexp_matches</> function returns a text array of
-     all of the captured substrings resulting from matching a POSIX
-     regular expression pattern.  It has the syntax
-     <function>regexp_matches</function>(<replaceable>string</>, <replaceable>pattern</>
-     <optional>, <replaceable>flags</> </optional>).
-     The function can return no rows, one row, or multiple rows (see
-     the <literal>g</> flag below).  If the <replaceable>pattern</>
-     does not match, the function returns no rows.  If the pattern
-     contains no parenthesized subexpressions, then each row
-     returned is a single-element text array containing the substring
-     matching the whole pattern.  If the pattern contains parenthesized
-     subexpressions, the function returns a text array whose
-     <replaceable>n</>'th element is the substring matching the
-     <replaceable>n</>'th parenthesized subexpression of the pattern
-     (not counting <quote>non-capturing</> parentheses; see below for
-     details).
-     The <replaceable>flags</> parameter is an optional text
-     string containing zero or more single-letter flags that change the
-     function's behavior.  Flag <literal>g</> causes the function to find
-     each match in the string, not only the first one, and return a row for
-     each such match.  Other supported
-     flags are described in <xref linkend="posix-embedded-options-table">.
-    </para>
-
-   <para>
-    Some examples:
-<programlisting>
-SELECT regexp_matches('foobarbequebaz', '(bar)(beque)');
- regexp_matches 
-----------------
- {bar,beque}
-(1 row)
-
-SELECT regexp_matches('foobarbequebazilbarfbonk', '(b[^b]+)(b[^b]+)', 'g');
- regexp_matches 
-----------------
- {bar,beque}
- {bazil,barf}
-(2 rows)
-
-SELECT regexp_matches('foobarbequebaz', 'barbeque');
- regexp_matches 
-----------------
- {barbeque}
-(1 row)
-</programlisting>
-   </para>
-
-   <para>
-    It is possible to force <function>regexp_matches()</> to always
-    return one row by using a sub-select;  this is particularly useful
-    in a <literal>SELECT</> target list when you want all rows
-    returned, even non-matching ones:
-<programlisting>
-SELECT col1, (SELECT regexp_matches(col2, '(bar)(beque)')) FROM tab;
-</programlisting>
-   </para>
-
-    <para>
-     The <function>regexp_split_to_table</> function splits a string using a POSIX
-     regular expression pattern as a delimiter.  It has the syntax
-     <function>regexp_split_to_table</function>(<replaceable>string</>, <replaceable>pattern</>
-     <optional>, <replaceable>flags</> </optional>).
-     If there is no match to the <replaceable>pattern</>, the function returns the
-     <replaceable>string</>.  If there is at least one match, for each match it returns
-     the text from the end of the last match (or the beginning of the string)
-     to the beginning of the match.  When there are no more matches, it
-     returns the text from the end of the last match to the end of the string.
-     The <replaceable>flags</> parameter is an optional text string containing
-     zero or more single-letter flags that change the function's behavior.
-     <function>regexp_split_to_table</function> supports the flags described in
-     <xref linkend="posix-embedded-options-table">.
-    </para>
-
-    <para>
-     The <function>regexp_split_to_array</> function behaves the same as
-     <function>regexp_split_to_table</>, except that <function>regexp_split_to_array</>
-     returns its result as an array of <type>text</>.  It has the syntax
-     <function>regexp_split_to_array</function>(<replaceable>string</>, <replaceable>pattern</>
-     <optional>, <replaceable>flags</> </optional>).
-     The parameters are the same as for <function>regexp_split_to_table</>.
-    </para>
-
-   <para>
-    Some examples:
-<programlisting>
-
-SELECT foo FROM regexp_split_to_table('the quick brown fox jumped over the lazy dog', E'\\s+') AS foo;
-  foo   
---------
- the    
- quick  
- brown  
- fox    
- jumped 
- over   
- the    
- lazy   
- dog    
-(9 rows)
-
-SELECT regexp_split_to_array('the quick brown fox jumped over the lazy dog', E'\\s+');
-              regexp_split_to_array             
-------------------------------------------------
- {the,quick,brown,fox,jumped,over,the,lazy,dog}
-(1 row)
-
-SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo;
- foo 
------
- t         
- h         
- e         
- q         
- u         
- i         
- c         
- k         
- b         
- r         
- o         
- w         
- n         
- f         
- o         
- x         
-(16 rows)
-</programlisting>
-   </para>
-
-   <para>
-    As the last example demonstrates, the regexp split functions ignore
-    zero-length matches that occur at the start or end of the string
-    or immediately after a previous match.  This is contrary to the strict
-    definition of regexp matching that is implemented by
-    <function>regexp_matches</>, but is usually the most convenient behavior
-    in practice.  Other software systems such as Perl use similar definitions.
-   </para>
-
-<!-- derived from the re_syntax.n man page -->
-
-   <sect3 id="posix-syntax-details">
-    <title>Regular Expression Details</title>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname>'s regular expressions are implemented
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>'s regular expressions are implemented
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>'s regular expressions are implemented
-<!## end>
-    using a software package written by Henry Spencer.  Much of
-    the description of regular expressions below is copied verbatim from his
-    manual.
-   </para>
-
-   <para>
-    Regular expressions (<acronym>RE</acronym>s), as defined in
-    <acronym>POSIX</acronym> 1003.2, come in two forms:
-    <firstterm>extended</> <acronym>RE</acronym>s or <acronym>ERE</>s
-    (roughly those of <command>egrep</command>), and
-    <firstterm>basic</> <acronym>RE</acronym>s or <acronym>BRE</>s
-    (roughly those of <command>ed</command>).
-<!## PG>
-    <productname>PostgreSQL</productname> supports both forms, and
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> supports both forms, and
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> supports both forms, and
-<!## end>
-    also implements some extensions
-    that are not in the POSIX standard, but have become widely used
-    due to their availability in programming languages such as Perl and Tcl.
-    <acronym>RE</acronym>s using these non-POSIX extensions are called
-    <firstterm>advanced</> <acronym>RE</acronym>s or <acronym>ARE</>s
-    in this documentation.  AREs are almost an exact superset of EREs,
-    but BREs have several notational incompatibilities (as well as being
-    much more limited).
-    We first describe the ARE and ERE forms, noting features that apply
-    only to AREs, and then describe how BREs differ.
-   </para>
-
-   <note>
-    <para>
-<!## PG>
-     <productname>PostgreSQL</> always initially presumes that a regular
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</> always initially presumes that a regular
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</> always initially presumes that a regular
-<!## end>
-     expression follows the ARE rules.  However, the more limited ERE or
-     BRE rules can be chosen by prepending an <firstterm>embedded option</>
-     to the RE pattern, as described in <xref linkend="posix-metasyntax">.
-     This can be useful for compatibility with applications that expect
-     exactly the <acronym>POSIX</acronym> 1003.2 rules.
-    </para>
-   </note>
-
-   <para>
-    A regular expression is defined as one or more
-    <firstterm>branches</firstterm>, separated by
-    <literal>|</literal>.  It matches anything that matches one of the
-    branches.
-   </para>
-
-   <para>
-    A branch is zero or more <firstterm>quantified atoms</> or
-    <firstterm>constraints</>, concatenated.
-    It matches a match for the first, followed by a match for the second, etc;
-    an empty branch matches the empty string.
-   </para>
-
-   <para>
-    A quantified atom is an <firstterm>atom</> possibly followed
-    by a single <firstterm>quantifier</>.
-    Without a quantifier, it matches a match for the atom.
-    With a quantifier, it can match some number of matches of the atom.
-    An <firstterm>atom</firstterm> can be any of the possibilities
-    shown in <xref linkend="posix-atoms-table">.
-    The possible quantifiers and their meanings are shown in
-    <xref linkend="posix-quantifiers-table">.
-   </para>
-
-   <para>
-    A <firstterm>constraint</> matches an empty string, but matches only when
-    specific conditions are met.  A constraint can be used where an atom
-    could be used, except it cannot be followed by a quantifier.
-    The simple constraints are shown in
-    <xref linkend="posix-constraints-table">;
-    some more constraints are described later.
-   </para>
-
-
-   <table id="posix-atoms-table">
-    <title>Regular Expression Atoms</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Atom</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-      <tbody>
-       <row>
-       <entry> <literal>(</><replaceable>re</><literal>)</> </entry>
-       <entry> (where <replaceable>re</> is any regular expression)
-       matches a match for
-       <replaceable>re</>, with the match noted for possible reporting </entry>
-       </row>
-
-       <row>
-       <entry> <literal>(?:</><replaceable>re</><literal>)</> </entry>
-       <entry> as above, but the match is not noted for reporting
-       (a <quote>non-capturing</> set of parentheses)
-       (AREs only) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>.</> </entry>
-       <entry> matches any single character </entry>
-       </row>
-
-       <row>
-       <entry> <literal>[</><replaceable>chars</><literal>]</> </entry>
-       <entry> a <firstterm>bracket expression</>,
-       matching any one of the <replaceable>chars</> (see
-       <xref linkend="posix-bracket-expressions"> for more detail) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\</><replaceable>k</> </entry>
-       <entry> (where <replaceable>k</> is a non-alphanumeric character)
-       matches that character taken as an ordinary character,
-       e.g., <literal>\\</> matches a backslash character </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\</><replaceable>c</> </entry>
-       <entry> where <replaceable>c</> is alphanumeric
-       (possibly followed by other characters)
-       is an <firstterm>escape</>, see <xref linkend="posix-escape-sequences">
-       (AREs only; in EREs and BREs, this matches <replaceable>c</>) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>{</> </entry>
-       <entry> when followed by a character other than a digit,
-       matches the left-brace character <literal>{</>;
-       when followed by a digit, it is the beginning of a
-       <replaceable>bound</> (see below) </entry>
-       </row>
-
-       <row>
-       <entry> <replaceable>x</> </entry>
-       <entry> where <replaceable>x</> is a single character with no other
-       significance, matches that character </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    An RE cannot end with <literal>\</>.
-   </para>
-
-   <note>
-    <para>
-     Remember that the backslash (<literal>\</literal>) already has a special
-<!## PG>
-     meaning in <productname>PostgreSQL</> string literals.
-<!## end>
-<!## XC>
-     meaning in <productname>Postgres-XC</> string literals.
-<!## end>
-<!## XL>
-     meaning in <productname>Postgres-XL</> string literals.
-<!## end>
-     To write a pattern constant that contains a backslash,
-     you must write two backslashes in the statement, assuming escape
-     string syntax is used (see <xref linkend="sql-syntax-strings">).
-    </para>
-   </note>
-
-   <table id="posix-quantifiers-table">
-    <title>Regular Expression Quantifiers</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Quantifier</entry>
-       <entry>Matches</entry>
-      </row>
-     </thead>
-
-      <tbody>
-       <row>
-       <entry> <literal>*</> </entry>
-       <entry> a sequence of 0 or more matches of the atom </entry>
-       </row>
-
-       <row>
-       <entry> <literal>+</> </entry>
-       <entry> a sequence of 1 or more matches of the atom </entry>
-       </row>
-
-       <row>
-       <entry> <literal>?</> </entry>
-       <entry> a sequence of 0 or 1 matches of the atom </entry>
-       </row>
-
-       <row>
-       <entry> <literal>{</><replaceable>m</><literal>}</> </entry>
-       <entry> a sequence of exactly <replaceable>m</> matches of the atom </entry>
-       </row>
-
-       <row>
-       <entry> <literal>{</><replaceable>m</><literal>,}</> </entry>
-       <entry> a sequence of <replaceable>m</> or more matches of the atom </entry>
-       </row>
-
-       <row>
-       <entry>
-       <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}</> </entry>
-       <entry> a sequence of <replaceable>m</> through <replaceable>n</>
-       (inclusive) matches of the atom; <replaceable>m</> cannot exceed
-       <replaceable>n</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>*?</> </entry>
-       <entry> non-greedy version of <literal>*</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>+?</> </entry>
-       <entry> non-greedy version of <literal>+</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>??</> </entry>
-       <entry> non-greedy version of <literal>?</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>{</><replaceable>m</><literal>}?</> </entry>
-       <entry> non-greedy version of <literal>{</><replaceable>m</><literal>}</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>{</><replaceable>m</><literal>,}?</> </entry>
-       <entry> non-greedy version of <literal>{</><replaceable>m</><literal>,}</> </entry>
-       </row>
-
-       <row>
-       <entry>
-       <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}?</> </entry>
-       <entry> non-greedy version of <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}</> </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    The forms using <literal>{</><replaceable>...</><literal>}</>
-    are known as <firstterm>bounds</>.
-    The numbers <replaceable>m</> and <replaceable>n</> within a bound are
-    unsigned decimal integers with permissible values from 0 to 255 inclusive.
-   </para>
-
-    <para>
-     <firstterm>Non-greedy</> quantifiers (available in AREs only) match the
-     same possibilities as their corresponding normal (<firstterm>greedy</>)
-     counterparts, but prefer the smallest number rather than the largest
-     number of matches.
-     See <xref linkend="posix-matching-rules"> for more detail.
-   </para>
-
-   <note>
-    <para>
-     A quantifier cannot immediately follow another quantifier, e.g.,
-     <literal>**</> is invalid.
-     A quantifier cannot
-     begin an expression or subexpression or follow
-     <literal>^</literal> or <literal>|</literal>.
-    </para>
-   </note>
-
-   <table id="posix-constraints-table">
-    <title>Regular Expression Constraints</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Constraint</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-      <tbody>
-       <row>
-       <entry> <literal>^</> </entry>
-       <entry> matches at the beginning of the string </entry>
-       </row>
-
-       <row>
-       <entry> <literal>$</> </entry>
-       <entry> matches at the end of the string </entry>
-       </row>
-
-       <row>
-       <entry> <literal>(?=</><replaceable>re</><literal>)</> </entry>
-       <entry> <firstterm>positive lookahead</> matches at any point
-       where a substring matching <replaceable>re</> begins
-       (AREs only) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>(?!</><replaceable>re</><literal>)</> </entry>
-       <entry> <firstterm>negative lookahead</> matches at any point
-       where no substring matching <replaceable>re</> begins
-       (AREs only) </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Lookahead constraints cannot contain <firstterm>back references</>
-    (see <xref linkend="posix-escape-sequences">),
-    and all parentheses within them are considered non-capturing.
-   </para>
-   </sect3>
-
-   <sect3 id="posix-bracket-expressions">
-    <title>Bracket Expressions</title>
-&common;
-   <para>
-    A <firstterm>bracket expression</firstterm> is a list of
-    characters enclosed in <literal>[]</literal>.  It normally matches
-    any single character from the list (but see below).  If the list
-    begins with <literal>^</literal>, it matches any single character
-    <emphasis>not</> from the rest of the list.
-    If two characters
-    in the list are separated by <literal>-</literal>, this is
-    shorthand for the full range of characters between those two
-    (inclusive) in the collating sequence,
-    e.g., <literal>[0-9]</literal> in <acronym>ASCII</acronym> matches
-    any decimal digit.  It is illegal for two ranges to share an
-    endpoint, e.g.,  <literal>a-c-e</literal>.  Ranges are very
-    collating-sequence-dependent, so portable programs should avoid
-    relying on them.
-   </para>
-
-   <para>
-    To include a literal <literal>]</literal> in the list, make it the
-    first character (after <literal>^</literal>, if that is used).  To
-    include a literal <literal>-</literal>, make it the first or last
-    character, or the second endpoint of a range.  To use a literal
-    <literal>-</literal> as the first endpoint of a range, enclose it
-    in <literal>[.</literal> and <literal>.]</literal> to make it a
-    collating element (see below).  With the exception of these characters,
-    some combinations using <literal>[</literal>
-    (see next paragraphs), and escapes (AREs only), all other special
-    characters lose their special significance within a bracket expression.
-    In particular, <literal>\</literal> is not special when following
-    ERE or BRE rules, though it is special (as introducing an escape)
-    in AREs.
-   </para>
-
-   <para>
-    Within a bracket expression, a collating element (a character, a
-    multiple-character sequence that collates as if it were a single
-    character, or a collating-sequence name for either) enclosed in
-    <literal>[.</literal> and <literal>.]</literal> stands for the
-    sequence of characters of that collating element.  The sequence is
-    treated as a single element of the bracket expression's list.  This
-    allows a bracket
-    expression containing a multiple-character collating element to
-    match more than one character, e.g., if the collating sequence
-    includes a <literal>ch</literal> collating element, then the RE
-    <literal>[[.ch.]]*c</literal> matches the first five characters of
-    <literal>chchcc</literal>.
-   </para>
-
-   <note>
-    <para>
-<!## PG>
-     <productname>PostgreSQL</> currently does not support multi-character collating
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</> currently does not support multi-character collating
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</> currently does not support multi-character collating
-<!## end>
-     elements. This information describes possible future behavior.
-    </para>
-   </note>
-
-   <para>
-    Within a bracket expression, a collating element enclosed in
-    <literal>[=</literal> and <literal>=]</literal> is an <firstterm>equivalence
-    class</>, standing for the sequences of characters of all collating
-    elements equivalent to that one, including itself.  (If there are
-    no other equivalent collating elements, the treatment is as if the
-    enclosing delimiters were <literal>[.</literal> and
-    <literal>.]</literal>.)  For example, if <literal>o</literal> and
-    <literal>^</literal> are the members of an equivalence class, then
-    <literal>[[=o=]]</literal>, <literal>[[=^=]]</literal>, and
-    <literal>[o^]</literal> are all synonymous.  An equivalence class
-    cannot be an endpoint of a range.
-   </para>
-
-   <para>
-    Within a bracket expression, the name of a character class
-    enclosed in <literal>[:</literal> and <literal>:]</literal> stands
-    for the list of all characters belonging to that class.  Standard
-    character class names are: <literal>alnum</literal>,
-    <literal>alpha</literal>, <literal>blank</literal>,
-    <literal>cntrl</literal>, <literal>digit</literal>,
-    <literal>graph</literal>, <literal>lower</literal>,
-    <literal>print</literal>, <literal>punct</literal>,
-    <literal>space</literal>, <literal>upper</literal>,
-    <literal>xdigit</literal>.  These stand for the character classes
-    defined in
-    <citerefentry><refentrytitle>ctype</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
-    A locale can provide others.  A character class cannot be used as
-    an endpoint of a range.
-   </para>
-
-   <para>
-    There are two special cases of bracket expressions:  the bracket
-    expressions <literal>[[:&lt;:]]</literal> and
-    <literal>[[:&gt;:]]</literal> are constraints,
-    matching empty strings at the beginning
-    and end of a word respectively.  A word is defined as a sequence
-    of word characters that is neither preceded nor followed by word
-    characters.  A word character is an <literal>alnum</> character (as
-    defined by
-    <citerefentry><refentrytitle>ctype</refentrytitle><manvolnum>3</manvolnum></citerefentry>)
-    or an underscore.  This is an extension, compatible with but not
-    specified by <acronym>POSIX</acronym> 1003.2, and should be used with
-    caution in software intended to be portable to other systems.
-    The constraint escapes described below are usually preferable; they
-    are no more standard, but are easier to type.
-   </para>
-   </sect3>
-
-   <sect3 id="posix-escape-sequences">
-    <title>Regular Expression Escapes</title>
-&common;
-   <para>
-    <firstterm>Escapes</> are special sequences beginning with <literal>\</>
-    followed by an alphanumeric character. Escapes come in several varieties:
-    character entry, class shorthands, constraint escapes, and back references.
-    A <literal>\</> followed by an alphanumeric character but not constituting
-    a valid escape is illegal in AREs.
-    In EREs, there are no escapes: outside a bracket expression,
-    a <literal>\</> followed by an alphanumeric character merely stands for
-    that character as an ordinary character, and inside a bracket expression,
-    <literal>\</> is an ordinary character.
-    (The latter is the one actual incompatibility between EREs and AREs.)
-   </para>
-
-   <para>
-    <firstterm>Character-entry escapes</> exist to make it easier to specify
-    non-printing and other inconvenient characters in REs.  They are
-    shown in <xref linkend="posix-character-entry-escapes-table">.
-   </para>
-
-   <para>
-    <firstterm>Class-shorthand escapes</> provide shorthands for certain
-    commonly-used character classes.  They are
-    shown in <xref linkend="posix-class-shorthand-escapes-table">.
-   </para>
-
-   <para>
-    A <firstterm>constraint escape</> is a constraint,
-    matching the empty string if specific conditions are met,
-    written as an escape.  They are
-    shown in <xref linkend="posix-constraint-escapes-table">.
-   </para>
-
-   <para>
-    A <firstterm>back reference</> (<literal>\</><replaceable>n</>) matches the
-    same string matched by the previous parenthesized subexpression specified
-    by the number <replaceable>n</>
-    (see <xref linkend="posix-constraint-backref-table">).  For example,
-    <literal>([bc])\1</> matches <literal>bb</> or <literal>cc</>
-    but not <literal>bc</> or <literal>cb</>.
-    The subexpression must entirely precede the back reference in the RE.
-    Subexpressions are numbered in the order of their leading parentheses.
-    Non-capturing parentheses do not define subexpressions.
-   </para>
-
-   <note>
-    <para>
-     Keep in mind that an escape's leading <literal>\</> will need to be
-     doubled when entering the pattern as an SQL string constant.  For example:
-<programlisting>
-'123' ~ E'^\\d{3}' <lineannotation>true</lineannotation>
-</programlisting>
-    </para>
-   </note>
-
-   <table id="posix-character-entry-escapes-table">
-    <title>Regular Expression Character-entry Escapes</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Escape</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-      <tbody>
-       <row>
-       <entry> <literal>\a</> </entry>
-       <entry> alert (bell) character, as in C </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\b</> </entry>
-       <entry> backspace, as in C </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\B</> </entry>
-       <entry> synonym for backslash (<literal>\</>) to help reduce the need for backslash
-       doubling </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\c</><replaceable>X</> </entry>
-       <entry> (where <replaceable>X</> is any character) the character whose
-       low-order 5 bits are the same as those of
-       <replaceable>X</>, and whose other bits are all zero </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\e</> </entry>
-       <entry> the character whose collating-sequence name
-       is <literal>ESC</>,
-       or failing that, the character with octal value 033 </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\f</> </entry>
-       <entry> form feed, as in C </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\n</> </entry>
-       <entry> newline, as in C </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\r</> </entry>
-       <entry> carriage return, as in C </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\t</> </entry>
-       <entry> horizontal tab, as in C </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\u</><replaceable>wxyz</> </entry>
-       <entry> (where <replaceable>wxyz</> is exactly four hexadecimal digits)
-       the UTF16 (Unicode, 16-bit) character <literal>U+</><replaceable>wxyz</>
-       in the local byte ordering </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\U</><replaceable>stuvwxyz</> </entry>
-       <entry> (where <replaceable>stuvwxyz</> is exactly eight hexadecimal
-       digits)
-       reserved for a hypothetical Unicode extension to 32 bits
-       </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\v</> </entry>
-       <entry> vertical tab, as in C </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\x</><replaceable>hhh</> </entry>
-       <entry> (where <replaceable>hhh</> is any sequence of hexadecimal
-       digits)
-       the character whose hexadecimal value is
-       <literal>0x</><replaceable>hhh</>
-       (a single character no matter how many hexadecimal digits are used)
-       </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\0</> </entry>
-       <entry> the character whose value is <literal>0</> (the null byte)</entry>
-       </row>
-
-       <row>
-       <entry> <literal>\</><replaceable>xy</> </entry>
-       <entry> (where <replaceable>xy</> is exactly two octal digits,
-       and is not a <firstterm>back reference</>)
-       the character whose octal value is
-       <literal>0</><replaceable>xy</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\</><replaceable>xyz</> </entry>
-       <entry> (where <replaceable>xyz</> is exactly three octal digits,
-       and is not a <firstterm>back reference</>)
-       the character whose octal value is
-       <literal>0</><replaceable>xyz</> </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Hexadecimal digits are <literal>0</>-<literal>9</>,
-    <literal>a</>-<literal>f</>, and <literal>A</>-<literal>F</>.
-    Octal digits are <literal>0</>-<literal>7</>.
-   </para>
-
-   <para>
-    The character-entry escapes are always taken as ordinary characters.
-    For example, <literal>\135</> is <literal>]</> in ASCII, but
-    <literal>\135</> does not terminate a bracket expression.
-   </para>
-
-   <table id="posix-class-shorthand-escapes-table">
-    <title>Regular Expression Class-shorthand Escapes</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Escape</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-      <tbody>
-       <row>
-       <entry> <literal>\d</> </entry>
-       <entry> <literal>[[:digit:]]</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\s</> </entry>
-       <entry> <literal>[[:space:]]</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\w</> </entry>
-       <entry> <literal>[[:alnum:]_]</>
-       (note underscore is included) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\D</> </entry>
-       <entry> <literal>[^[:digit:]]</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\S</> </entry>
-       <entry> <literal>[^[:space:]]</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\W</> </entry>
-       <entry> <literal>[^[:alnum:]_]</>
-       (note underscore is included) </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Within bracket expressions, <literal>\d</>, <literal>\s</>,
-    and <literal>\w</> lose their outer brackets,
-    and <literal>\D</>, <literal>\S</>, and <literal>\W</> are illegal.
-    (So, for example, <literal>[a-c\d]</> is equivalent to
-    <literal>[a-c[:digit:]]</>.
-    Also, <literal>[a-c\D]</>, which is equivalent to
-    <literal>[a-c^[:digit:]]</>, is illegal.)
-   </para>
-
-   <table id="posix-constraint-escapes-table">
-    <title>Regular Expression Constraint Escapes</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Escape</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-      <tbody>
-       <row>
-       <entry> <literal>\A</> </entry>
-       <entry> matches only at the beginning of the string
-       (see <xref linkend="posix-matching-rules"> for how this differs from
-       <literal>^</>) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\m</> </entry>
-       <entry> matches only at the beginning of a word </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\M</> </entry>
-       <entry> matches only at the end of a word </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\y</> </entry>
-       <entry> matches only at the beginning or end of a word </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\Y</> </entry>
-       <entry> matches only at a point that is not the beginning or end of a
-       word </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\Z</> </entry>
-       <entry> matches only at the end of the string
-       (see <xref linkend="posix-matching-rules"> for how this differs from
-       <literal>$</>) </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    A word is defined as in the specification of
-    <literal>[[:&lt;:]]</> and <literal>[[:&gt;:]]</> above.
-    Constraint escapes are illegal within bracket expressions.
-   </para>
-
-   <table id="posix-constraint-backref-table">
-    <title>Regular Expression Back References</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Escape</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-      <tbody>
-       <row>
-       <entry> <literal>\</><replaceable>m</> </entry>
-       <entry> (where <replaceable>m</> is a nonzero digit)
-       a back reference to the <replaceable>m</>'th subexpression </entry>
-       </row>
-
-       <row>
-       <entry> <literal>\</><replaceable>mnn</> </entry>
-       <entry> (where <replaceable>m</> is a nonzero digit, and
-       <replaceable>nn</> is some more digits, and the decimal value
-       <replaceable>mnn</> is not greater than the number of closing capturing
-       parentheses seen so far)
-       a back reference to the <replaceable>mnn</>'th subexpression </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <note>
-    <para>
-     There is an inherent ambiguity between octal character-entry
-     escapes and back references, which is resolved by the following heuristics,
-     as hinted at above.
-     A leading zero always indicates an octal escape.
-     A single non-zero digit, not followed by another digit,
-     is always taken as a back reference.
-     A multi-digit sequence not starting with a zero is taken as a back
-     reference if it comes after a suitable subexpression
-     (i.e., the number is in the legal range for a back reference),
-     and otherwise is taken as octal.
-    </para>
-   </note>
-   </sect3>
-
-   <sect3 id="posix-metasyntax">
-    <title>Regular Expression Metasyntax</title>
-&common;
-   <para>
-    In addition to the main syntax described above, there are some special
-    forms and miscellaneous syntactic facilities available.
-   </para>
-
-   <para>
-    An RE can begin with one of two special <firstterm>director</> prefixes.
-    If an RE begins with <literal>***:</>,
-    the rest of the RE is taken as an ARE.  (This normally has no effect in
-<!## PG>
-    <productname>PostgreSQL</>, since REs are assumed to be AREs;
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</>, since REs are assumed to be AREs;
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</>, since REs are assumed to be AREs;
-<!## end>
-    but it does have an effect if ERE or BRE mode had been specified by
-    the <replaceable>flags</> parameter to a regex function.)
-    If an RE begins with <literal>***=</>,
-    the rest of the RE is taken to be a literal string,
-    with all characters considered ordinary characters.
-   </para>
-
-   <para>
-    An ARE can begin with <firstterm>embedded options</>:
-    a sequence <literal>(?</><replaceable>xyz</><literal>)</>
-    (where <replaceable>xyz</> is one or more alphabetic characters)
-    specifies options affecting the rest of the RE.
-    These options override any previously determined options &mdash;
-    in particular, they can override the case-sensitivity behavior implied by
-    a regex operator, or the <replaceable>flags</> parameter to a regex
-    function.
-    The available option letters are
-    shown in <xref linkend="posix-embedded-options-table">.
-    Note that these same option letters are used in the <replaceable>flags</>
-    parameters of regex functions.
-   </para>
-
-   <table id="posix-embedded-options-table">
-    <title>ARE Embedded-option Letters</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Option</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-      <tbody>
-       <row>
-       <entry> <literal>b</> </entry>
-       <entry> rest of RE is a BRE </entry>
-       </row>
-
-       <row>
-       <entry> <literal>c</> </entry>
-       <entry> case-sensitive matching (overrides operator type) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>e</> </entry>
-       <entry> rest of RE is an ERE </entry>
-       </row>
-
-       <row>
-       <entry> <literal>i</> </entry>
-       <entry> case-insensitive matching (see
-       <xref linkend="posix-matching-rules">) (overrides operator type) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>m</> </entry>
-       <entry> historical synonym for <literal>n</> </entry>
-       </row>
-
-       <row>
-       <entry> <literal>n</> </entry>
-       <entry> newline-sensitive matching (see
-       <xref linkend="posix-matching-rules">) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>p</> </entry>
-       <entry> partial newline-sensitive matching (see
-       <xref linkend="posix-matching-rules">) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>q</> </entry>
-       <entry> rest of RE is a literal (<quote>quoted</>) string, all ordinary
-       characters </entry>
-       </row>
-
-       <row>
-       <entry> <literal>s</> </entry>
-       <entry> non-newline-sensitive matching (default) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>t</> </entry>
-       <entry> tight syntax (default; see below) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>w</> </entry>
-       <entry> inverse partial newline-sensitive (<quote>weird</>) matching
-       (see <xref linkend="posix-matching-rules">) </entry>
-       </row>
-
-       <row>
-       <entry> <literal>x</> </entry>
-       <entry> expanded syntax (see below) </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Embedded options take effect at the <literal>)</> terminating the sequence.
-    They can appear only at the start of an ARE (after the
-    <literal>***:</> director if any).
-   </para>
-
-   <para>
-    In addition to the usual (<firstterm>tight</>) RE syntax, in which all
-    characters are significant, there is an <firstterm>expanded</> syntax,
-    available by specifying the embedded <literal>x</> option.
-    In the expanded syntax,
-    white-space characters in the RE are ignored, as are
-    all characters between a <literal>#</>
-    and the following newline (or the end of the RE).  This
-    permits paragraphing and commenting a complex RE.
-    There are three exceptions to that basic rule:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       a white-space character or <literal>#</> preceded by <literal>\</> is
-       retained
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       white space or <literal>#</> within a bracket expression is retained
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       white space and comments cannot appear within multi-character symbols,
-       such as <literal>(?:</>
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    For this purpose, white-space characters are blank, tab, newline, and
-    any character that belongs to the <replaceable>space</> character class.
-   </para>
-
-   <para>
-    Finally, in an ARE, outside bracket expressions, the sequence
-    <literal>(?#</><replaceable>ttt</><literal>)</>
-    (where <replaceable>ttt</> is any text not containing a <literal>)</>)
-    is a comment, completely ignored.
-    Again, this is not allowed between the characters of
-    multi-character symbols, like <literal>(?:</>.
-    Such comments are more a historical artifact than a useful facility,
-    and their use is deprecated; use the expanded syntax instead.
-   </para>
-
-   <para>
-    <emphasis>None</> of these metasyntax extensions is available if
-    an initial <literal>***=</> director
-    has specified that the user's input be treated as a literal string
-    rather than as an RE.
-   </para>
-   </sect3>
-
-   <sect3 id="posix-matching-rules">
-    <title>Regular Expression Matching Rules</title>
-&common;
-   <para>
-    In the event that an RE could match more than one substring of a given
-    string, the RE matches the one starting earliest in the string.
-    If the RE could match more than one substring starting at that point,
-    either the longest possible match or the shortest possible match will
-    be taken, depending on whether the RE is <firstterm>greedy</> or
-    <firstterm>non-greedy</>.
-   </para>
-
-   <para>
-    Whether an RE is greedy or not is determined by the following rules:
-    <itemizedlist>
-     <listitem>
-      <para>
-       Most atoms, and all constraints, have no greediness attribute (because
-       they cannot match variable amounts of text anyway).
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Adding parentheses around an RE does not change its greediness.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       A quantified atom with a fixed-repetition quantifier
-       (<literal>{</><replaceable>m</><literal>}</>
-       or
-       <literal>{</><replaceable>m</><literal>}?</>)
-       has the same greediness (possibly none) as the atom itself.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       A quantified atom with other normal quantifiers (including
-       <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}</>
-       with <replaceable>m</> equal to <replaceable>n</>)
-       is greedy (prefers longest match).
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       A quantified atom with a non-greedy quantifier (including
-       <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}?</>
-       with <replaceable>m</> equal to <replaceable>n</>)
-       is non-greedy (prefers shortest match).
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       A branch &mdash; that is, an RE that has no top-level
-       <literal>|</> operator &mdash; has the same greediness as the first
-       quantified atom in it that has a greediness attribute.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       An RE consisting of two or more branches connected by the
-       <literal>|</> operator is always greedy.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    The above rules associate greediness attributes not only with individual
-    quantified atoms, but with branches and entire REs that contain quantified
-    atoms.  What that means is that the matching is done in such a way that
-    the branch, or whole RE, matches the longest or shortest possible
-    substring <emphasis>as a whole</>.  Once the length of the entire match
-    is determined, the part of it that matches any particular subexpression
-    is determined on the basis of the greediness attribute of that
-    subexpression, with subexpressions starting earlier in the RE taking
-    priority over ones starting later.
-   </para>
-
-   <para>
-    An example of what this means:
-<screen>
-SELECT SUBSTRING('XY1234Z', 'Y*([0-9]{1,3})');
-<lineannotation>Result: </lineannotation><computeroutput>123</computeroutput>
-SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
-<lineannotation>Result: </lineannotation><computeroutput>1</computeroutput>
-</screen>
-    In the first case, the RE as a whole is greedy because <literal>Y*</>
-    is greedy.  It can match beginning at the <literal>Y</>, and it matches
-    the longest possible string starting there, i.e., <literal>Y123</>.
-    The output is the parenthesized part of that, or <literal>123</>.
-    In the second case, the RE as a whole is non-greedy because <literal>Y*?</>
-    is non-greedy.  It can match beginning at the <literal>Y</>, and it matches
-    the shortest possible string starting there, i.e., <literal>Y1</>.
-    The subexpression <literal>[0-9]{1,3}</> is greedy but it cannot change
-    the decision as to the overall match length; so it is forced to match
-    just <literal>1</>.
-   </para>
-
-   <para>
-    In short, when an RE contains both greedy and non-greedy subexpressions,
-    the total match length is either as long as possible or as short as
-    possible, according to the attribute assigned to the whole RE.  The
-    attributes assigned to the subexpressions only affect how much of that
-    match they are allowed to <quote>eat</> relative to each other.
-   </para>
-
-   <para>
-    The quantifiers <literal>{1,1}</> and <literal>{1,1}?</>
-    can be used to force greediness or non-greediness, respectively,
-    on a subexpression or a whole RE.
-   </para>
-
-   <para>
-    Match lengths are measured in characters, not collating elements.
-    An empty string is considered longer than no match at all.
-    For example:
-    <literal>bb*</>
-    matches the three middle characters of <literal>abbbc</>;
-    <literal>(week|wee)(night|knights)</>
-    matches all ten characters of <literal>weeknights</>;
-    when <literal>(.*).*</>
-    is matched against <literal>abc</> the parenthesized subexpression
-    matches all three characters; and when
-    <literal>(a*)*</> is matched against <literal>bc</>
-    both the whole RE and the parenthesized
-    subexpression match an empty string.
-   </para>
-
-   <para>
-    If case-independent matching is specified,
-    the effect is much as if all case distinctions had vanished from the
-    alphabet.
-    When an alphabetic that exists in multiple cases appears as an
-    ordinary character outside a bracket expression, it is effectively
-    transformed into a bracket expression containing both cases,
-    e.g., <literal>x</> becomes <literal>[xX]</>.
-    When it appears inside a bracket expression, all case counterparts
-    of it are added to the bracket expression, e.g.,
-    <literal>[x]</> becomes <literal>[xX]</>
-    and <literal>[^x]</> becomes <literal>[^xX]</>.
-   </para>
-
-   <para>
-    If newline-sensitive matching is specified, <literal>.</>
-    and bracket expressions using <literal>^</>
-    will never match the newline character
-    (so that matches will never cross newlines unless the RE
-    explicitly arranges it)
-    and <literal>^</>and <literal>$</>
-    will match the empty string after and before a newline
-    respectively, in addition to matching at beginning and end of string
-    respectively.
-    But the ARE escapes <literal>\A</> and <literal>\Z</>
-    continue to match beginning or end of string <emphasis>only</>.
-   </para>
-
-   <para>
-    If partial newline-sensitive matching is specified,
-    this affects <literal>.</> and bracket expressions
-    as with newline-sensitive matching, but not <literal>^</>
-    and <literal>$</>.
-   </para>
-
-   <para>
-    If inverse partial newline-sensitive matching is specified,
-    this affects <literal>^</> and <literal>$</>
-    as with newline-sensitive matching, but not <literal>.</>
-    and bracket expressions.
-    This isn't very useful but is provided for symmetry.
-   </para>
-   </sect3>
-
-   <sect3 id="posix-limits-compatibility">
-    <title>Limits and Compatibility</title>
-&common;
-   <para>
-    No particular limit is imposed on the length of REs in this
-    implementation.  However,
-    programs intended to be highly portable should not employ REs longer
-    than 256 bytes,
-    as a POSIX-compliant implementation can refuse to accept such REs.
-   </para>
-
-   <para>
-    The only feature of AREs that is actually incompatible with
-    POSIX EREs is that <literal>\</> does not lose its special
-    significance inside bracket expressions.
-    All other ARE features use syntax which is illegal or has
-    undefined or unspecified effects in POSIX EREs;
-    the <literal>***</> syntax of directors likewise is outside the POSIX
-    syntax for both BREs and EREs.
-   </para>
-
-   <para>
-    Many of the ARE extensions are borrowed from Perl, but some have
-    been changed to clean them up, and a few Perl extensions are not present.
-    Incompatibilities of note include <literal>\b</>, <literal>\B</>,
-    the lack of special treatment for a trailing newline,
-    the addition of complemented bracket expressions to the things
-    affected by newline-sensitive matching,
-    the restrictions on parentheses and back references in lookahead
-    constraints, and the longest/shortest-match (rather than first-match)
-    matching semantics.
-   </para>
-
-   <para>
-    Two significant incompatibilities exist between AREs and the ERE syntax
-    recognized by pre-7.4 releases of <productname>PostgreSQL</>:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       In AREs, <literal>\</> followed by an alphanumeric character is either
-       an escape or an error, while in previous releases, it was just another
-       way of writing the alphanumeric.
-       This should not be much of a problem because there was no reason to
-       write such a sequence in earlier releases.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       In AREs, <literal>\</> remains a special character within
-       <literal>[]</>, so a literal <literal>\</> within a bracket
-       expression must be written <literal>\\</>.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-   </sect3>
-
-   <sect3 id="posix-basic-regexes">
-    <title>Basic Regular Expressions</title>
-&common;
-   <para>
-    BREs differ from EREs in several respects.
-    In BREs, <literal>|</>, <literal>+</>, and <literal>?</>
-    are ordinary characters and there is no equivalent
-    for their functionality.
-    The delimiters for bounds are
-    <literal>\{</> and <literal>\}</>,
-    with <literal>{</> and <literal>}</>
-    by themselves ordinary characters.
-    The parentheses for nested subexpressions are
-    <literal>\(</> and <literal>\)</>,
-    with <literal>(</> and <literal>)</> by themselves ordinary characters.
-    <literal>^</> is an ordinary character except at the beginning of the
-    RE or the beginning of a parenthesized subexpression,
-    <literal>$</> is an ordinary character except at the end of the
-    RE or the end of a parenthesized subexpression,
-    and <literal>*</> is an ordinary character if it appears at the beginning
-    of the RE or the beginning of a parenthesized subexpression
-    (after a possible leading <literal>^</>).
-    Finally, single-digit back references are available, and
-    <literal>\&lt;</> and <literal>\&gt;</>
-    are synonyms for
-    <literal>[[:&lt;:]]</> and <literal>[[:&gt;:]]</>
-    respectively; no other escapes are available in BREs.
-   </para>
-   </sect3>
-
-<!-- end re_syntax.n man page -->
-
-  </sect2>
- </sect1>
-
-
-  <sect1 id="functions-formatting">
-   <title>Data Type Formatting Functions</title>
-
-   <indexterm>
-    <primary>formatting</primary>
-   </indexterm>
-&common;
-   <para>
-<!## PG>
-    The <productname>PostgreSQL</productname> formatting functions
-<!## end>
-<!## XC>
-    The <productname>Postgres-XC</productname> formatting functions
-<!## end>
-<!## XL>
-    The <productname>Postgres-XL</productname> formatting functions
-<!## end>
-    provide a powerful set of tools for converting various data types
-    (date/time, integer, floating point, numeric) to formatted strings
-    and for converting from formatted strings to specific data types.
-    <xref linkend="functions-formatting-table"> lists them.
-    These functions all follow a common calling convention: the first
-    argument is the value to be formatted and the second argument is a
-    template that defines the output or input format.
-   </para>
-   <para>
-    A single-argument <function>to_timestamp</function> function is also
-    available;  it accepts a
-    <type>double precision</type> argument and converts from Unix epoch
-    (seconds since 1970-01-01 00:00:00+00) to
-    <type>timestamp with time zone</type>.
-    (<type>Integer</type> Unix epochs are implicitly cast to
-    <type>double precision</type>.)
-   </para>
-
-    <table id="functions-formatting-table">
-     <title>Formatting Functions</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Function</entry>
-        <entry>Return Type</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>to_char</primary>
-         </indexterm>
-         <literal><function>to_char(<type>timestamp</type>, <type>text</type>)</function></literal>
-        </entry>
-        <entry><type>text</type></entry>
-        <entry>convert time stamp to string</entry>
-        <entry><literal>to_char(current_timestamp, 'HH12:MI:SS')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>to_char(<type>interval</type>, <type>text</type>)</function></literal></entry>
-        <entry><type>text</type></entry>
-        <entry>convert interval to string</entry>
-        <entry><literal>to_char(interval '15h&nbsp;2m&nbsp;12s', 'HH24:MI:SS')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>to_char(<type>int</type>, <type>text</type>)</function></literal></entry>
-        <entry><type>text</type></entry>
-        <entry>convert integer to string</entry>
-        <entry><literal>to_char(125, '999')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>to_char</function>(<type>double precision</type>,
-        <type>text</type>)</literal></entry>
-        <entry><type>text</type></entry>
-        <entry>convert real/double precision to string</entry>
-        <entry><literal>to_char(125.8::real, '999D9')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>to_char(<type>numeric</type>, <type>text</type>)</function></literal></entry>
-        <entry><type>text</type></entry>
-        <entry>convert numeric to string</entry>
-        <entry><literal>to_char(-125.8, '999D99S')</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>to_date</primary>
-         </indexterm>
-         <literal><function>to_date(<type>text</type>, <type>text</type>)</function></literal>
-        </entry>
-        <entry><type>date</type></entry>
-        <entry>convert string to date</entry>
-        <entry><literal>to_date('05&nbsp;Dec&nbsp;2000', 'DD&nbsp;Mon&nbsp;YYYY')</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>to_number</primary>
-         </indexterm>
-         <literal><function>to_number(<type>text</type>, <type>text</type>)</function></literal>
-        </entry>
-        <entry><type>numeric</type></entry>
-        <entry>convert string to numeric</entry>
-        <entry><literal>to_number('12,454.8-', '99G999D9S')</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>to_timestamp</primary>
-         </indexterm>
-         <literal><function>to_timestamp(<type>text</type>, <type>text</type>)</function></literal>
-        </entry>
-        <entry><type>timestamp with time zone</type></entry>
-        <entry>convert string to time stamp</entry>
-        <entry><literal>to_timestamp('05&nbsp;Dec&nbsp;2000', 'DD&nbsp;Mon&nbsp;YYYY')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>to_timestamp(<type>double precision</type>)</function></literal></entry>
-        <entry><type>timestamp with time zone</type></entry>
-        <entry>convert Unix epoch to time stamp</entry>
-        <entry><literal>to_timestamp(1284352323)</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    In a <function>to_char</> output template string, there are certain
-    patterns that are recognized and replaced with appropriately-formatted
-    data based on the given value.  Any text that is not a template pattern is
-    simply copied verbatim.  Similarly, in an input template string (for the
-    other functions), template patterns identify the values to be supplied by
-    the input data string.
-   </para>
-
-  <para>
-   <xref linkend="functions-formatting-datetime-table"> shows the
-   template patterns available for formatting date and time values.
-  </para>
-
-    <table id="functions-formatting-datetime-table">
-     <title>Template Patterns for Date/Time Formatting</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>Pattern</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><literal>HH</literal></entry>
-        <entry>hour of day (01-12)</entry>
-       </row>
-       <row>
-        <entry><literal>HH12</literal></entry>
-        <entry>hour of day (01-12)</entry>
-       </row>
-       <row>
-        <entry><literal>HH24</literal></entry>
-        <entry>hour of day (00-23)</entry>
-       </row>
-       <row>
-        <entry><literal>MI</literal></entry>
-        <entry>minute (00-59)</entry>
-       </row>
-       <row>
-        <entry><literal>SS</literal></entry>
-        <entry>second (00-59)</entry>
-       </row>
-       <row>
-        <entry><literal>MS</literal></entry>
-        <entry>millisecond (000-999)</entry>
-       </row>
-       <row>
-        <entry><literal>US</literal></entry>
-        <entry>microsecond (000000-999999)</entry>
-       </row>
-       <row>
-        <entry><literal>SSSS</literal></entry>
-        <entry>seconds past midnight (0-86399)</entry>
-       </row>
-       <row>
-        <entry><literal>AM</literal>, <literal>am</literal>,
-        <literal>PM</literal> or <literal>pm</literal></entry>
-        <entry>meridiem indicator (without periods)</entry>
-       </row>
-       <row>
-        <entry><literal>A.M.</literal>, <literal>a.m.</literal>,
-        <literal>P.M.</literal> or <literal>p.m.</literal></entry>
-        <entry>meridiem indicator (with periods)</entry>
-       </row>
-       <row>
-        <entry><literal>Y,YYY</literal></entry>
-        <entry>year (4 and more digits) with comma</entry>
-       </row>
-       <row>
-        <entry><literal>YYYY</literal></entry>
-        <entry>year (4 and more digits)</entry>
-       </row>
-       <row>
-        <entry><literal>YYY</literal></entry>
-        <entry>last 3 digits of year</entry>
-       </row>
-       <row>
-        <entry><literal>YY</literal></entry>
-        <entry>last 2 digits of year</entry>
-       </row>
-       <row>
-        <entry><literal>Y</literal></entry>
-        <entry>last digit of year</entry>
-       </row>
-       <row>
-        <entry><literal>IYYY</literal></entry>
-        <entry>ISO year (4 and more digits)</entry>
-       </row>
-       <row>
-        <entry><literal>IYY</literal></entry>
-        <entry>last 3 digits of ISO year</entry>
-       </row>
-       <row>
-        <entry><literal>IY</literal></entry>
-        <entry>last 2 digits of ISO year</entry>
-       </row>
-       <row>
-        <entry><literal>I</literal></entry>
-        <entry>last digit of ISO year</entry>
-       </row>
-       <row>
-        <entry><literal>BC</literal>, <literal>bc</literal>,
-        <literal>AD</literal> or <literal>ad</literal></entry>
-        <entry>era indicator (without periods)</entry>
-       </row>
-       <row>
-        <entry><literal>B.C.</literal>, <literal>b.c.</literal>,
-        <literal>A.D.</literal> or <literal>a.d.</literal></entry>
-        <entry>era indicator (with periods)</entry>
-       </row>
-       <row>
-        <entry><literal>MONTH</literal></entry>
-        <entry>full upper case month name (blank-padded to 9 chars)</entry>
-       </row>
-       <row>
-        <entry><literal>Month</literal></entry>
-        <entry>full capitalized month name (blank-padded to 9 chars)</entry>
-       </row>
-       <row>
-        <entry><literal>month</literal></entry>
-        <entry>full lower case month name (blank-padded to 9 chars)</entry>
-       </row>
-       <row>
-        <entry><literal>MON</literal></entry>
-        <entry>abbreviated upper case month name (3 chars in English, localized lengths vary)</entry>
-       </row>
-       <row>
-        <entry><literal>Mon</literal></entry>
-        <entry>abbreviated capitalized month name (3 chars in English, localized lengths vary)</entry>
-       </row>
-       <row>
-        <entry><literal>mon</literal></entry>
-        <entry>abbreviated lower case month name (3 chars in English, localized lengths vary)</entry>
-       </row>
-       <row>
-        <entry><literal>MM</literal></entry>
-        <entry>month number (01-12)</entry>
-       </row>
-       <row>
-        <entry><literal>DAY</literal></entry>
-        <entry>full upper case day name (blank-padded to 9 chars)</entry>
-       </row>
-       <row>
-        <entry><literal>Day</literal></entry>
-        <entry>full capitalized day name (blank-padded to 9 chars)</entry>
-       </row>
-       <row>
-        <entry><literal>day</literal></entry>
-        <entry>full lower case day name (blank-padded to 9 chars)</entry>
-       </row>
-       <row>
-        <entry><literal>DY</literal></entry>
-        <entry>abbreviated upper case day name (3 chars in English, localized lengths vary)</entry>
-       </row>
-       <row>
-        <entry><literal>Dy</literal></entry>
-        <entry>abbreviated capitalized day name (3 chars in English, localized lengths vary)</entry>
-       </row>
-       <row>
-        <entry><literal>dy</literal></entry>
-        <entry>abbreviated lower case day name (3 chars in English, localized lengths vary)</entry>
-       </row>
-       <row>
-        <entry><literal>DDD</literal></entry>
-        <entry>day of year (001-366)</entry>
-       </row>
-       <row>
-        <entry><literal>IDDD</literal></entry>
-        <entry>ISO day of year (001-371; day 1 of the year is Monday of the first ISO week.)</entry>
-       </row>
-       <row>
-        <entry><literal>DD</literal></entry>
-        <entry>day of month (01-31)</entry>
-       </row>
-       <row>
-        <entry><literal>D</literal></entry>
-        <entry>day of the week, Sunday(<literal>1</>) to Saturday(<literal>7</>)</entry>
-       </row>
-       <row>
-        <entry><literal>ID</literal></entry>
-        <entry>ISO day of the week, Monday(<literal>1</>) to Sunday(<literal>7</>)</entry>
-       </row>
-       <row>
-        <entry><literal>W</literal></entry>
-        <entry>week of month (1-5) (The first week starts on the first day of the month.)</entry>
-       </row>
-       <row>
-        <entry><literal>WW</literal></entry>
-        <entry>week number of year (1-53) (The first week starts on the first day of the year.)</entry>
-       </row>
-       <row>
-        <entry><literal>IW</literal></entry>
-        <entry>ISO week number of year (01 - 53; the first Thursday of the new year is in week 1.)</entry>
-       </row>
-       <row>
-        <entry><literal>CC</literal></entry>
-        <entry>century (2 digits) (The twenty-first century starts on 2001-01-01.)</entry>
-       </row>
-       <row>
-        <entry><literal>J</literal></entry>
-        <entry>Julian Day (days since November 24, 4714 BC at midnight)</entry>
-       </row>
-       <row>
-        <entry><literal>Q</literal></entry>
-        <entry>quarter (ignored by <function>to_date</> and <function>to_timestamp</>)</entry>
-       </row>
-       <row>
-        <entry><literal>RM</literal></entry>
-        <entry>month in upper case Roman numerals (I-XII; I=January)</entry>
-       </row>
-       <row>
-        <entry><literal>rm</literal></entry>
-        <entry>month in lower case Roman numerals (i-xii; i=January)</entry>
-       </row>
-       <row>
-        <entry><literal>TZ</literal></entry>
-        <entry>upper case time-zone name</entry>
-       </row>
-       <row>
-        <entry><literal>tz</literal></entry>
-        <entry>lower case time-zone name</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Modifiers can be applied to any template pattern to alter its
-    behavior.  For example, <literal>FMMonth</literal>
-    is the <literal>Month</literal> pattern with the
-    <literal>FM</literal> modifier.
-    <xref linkend="functions-formatting-datetimemod-table"> shows the
-    modifier patterns for date/time formatting.
-   </para>
-
-    <table id="functions-formatting-datetimemod-table">
-     <title>Template Pattern Modifiers for Date/Time Formatting</title>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Modifier</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><literal>FM</literal> prefix</entry>
-        <entry>fill mode (suppress padding blanks and trailing zeroes)</entry>
-        <entry><literal>FMMonth</literal></entry>
-       </row>
-       <row>
-        <entry><literal>TH</literal> suffix</entry>
-        <entry>upper case ordinal number suffix</entry>
-        <entry><literal>DDTH</literal>, e.g., <literal>12TH</></entry>
-       </row>
-       <row>
-        <entry><literal>th</literal> suffix</entry>
-        <entry>lower case ordinal number suffix</entry>
-        <entry><literal>DDth</literal>, e.g., <literal>12th</></entry>
-       </row>
-       <row>
-        <entry><literal>FX</literal> prefix</entry>
-        <entry>fixed format global option (see usage notes)</entry>
-        <entry><literal>FX&nbsp;Month&nbsp;DD&nbsp;Day</literal></entry>
-       </row>
-       <row>
-        <entry><literal>TM</literal> prefix</entry>
-        <entry>translation mode (print localized day and month names based on
-         <xref linkend="guc-lc-time">)</entry>
-        <entry><literal>TMMonth</literal></entry>
-       </row>
-       <row>
-        <entry><literal>SP</literal> suffix</entry>
-        <entry>spell mode (not implemented)</entry>
-        <entry><literal>DDSP</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Usage notes for date/time formatting:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       <literal>FM</literal> suppresses leading zeroes and trailing blanks
-       that would otherwise be added to make the output of a pattern be
-<!## PG>
-       fixed-width.  In <productname>PostgreSQL</productname>,
-<!## end>
-<!## XC>
-       fixed-width.  In <productname>Postgres-XC</productname>,
-<!## end>
-<!## XL>
-       fixed-width.  In <productname>Postgres-XL</productname>,
-<!## end>
-       <literal>FM</literal> modifies only the next specification, while in
-       Oracle <literal>FM</literal> affects all subsequent
-       specifications, and repeated <literal>FM</literal> modifiers
-       toggle fill mode on and off.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>TM</literal> does not include trailing blanks.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>to_timestamp</function> and <function>to_date</function>
-       skip multiple blank spaces in the input string unless the
-       <literal>FX</literal> option is used. For example,
-       <literal>to_timestamp('2000&nbsp;&nbsp;&nbsp;&nbsp;JUN', 'YYYY MON')</literal> works, but
-       <literal>to_timestamp('2000&nbsp;&nbsp;&nbsp;&nbsp;JUN', 'FXYYYY MON')</literal> returns an error
-       because <function>to_timestamp</function> expects one space only.
-       <literal>FX</literal> must be specified as the first item in
-       the template.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Ordinary text is allowed in <function>to_char</function>
-       templates and will be output literally.  You can put a substring
-       in double quotes to force it to be interpreted as literal text
-       even if it contains pattern key words.  For example, in
-       <literal>'"Hello Year "YYYY'</literal>, the <literal>YYYY</literal>
-       will be replaced by the year data, but the single <literal>Y</literal> in <literal>Year</literal>
-       will not be.  In <function>to_date</>, <function>to_number</>,
-       and <function>to_timestamp</>, double-quoted strings skip the number of
-       input characters contained in the string, e.g. <literal>"XX"</>
-       skips two input characters.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If you want to have a double quote in the output you must
-       precede it with a backslash, for example <literal>E'\\"YYYY
-       Month\\"'</literal>. <!-- "" font-lock sanity :-) -->
-       (Two backslashes are necessary because the backslash
-       has special meaning when using the escape string syntax.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The <literal>YYYY</literal> conversion from string to <type>timestamp</type> or
-       <type>date</type> has a restriction when processing years with more than 4 digits. You must
-       use some non-digit character or template after <literal>YYYY</literal>,
-       otherwise the year is always interpreted as 4 digits. For example
-       (with the year 20000):
-       <literal>to_date('200001131', 'YYYYMMDD')</literal> will be
-       interpreted as a 4-digit year; instead use a non-digit
-       separator after the year, like
-       <literal>to_date('20000-1131', 'YYYY-MMDD')</literal> or
-       <literal>to_date('20000Nov31', 'YYYYMonDD')</literal>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In conversions from string to <type>timestamp</type> or
-       <type>date</type>, the <literal>CC</literal> (century) field is ignored
-       if there is a <literal>YYY</literal>, <literal>YYYY</literal> or
-       <literal>Y,YYY</literal> field. If <literal>CC</literal> is used with
-       <literal>YY</literal> or <literal>Y</literal> then the year is computed
-       as <literal>(CC-1)*100+YY</literal>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       An ISO week date (as distinct from a Gregorian date) can be
-       specified to <function>to_timestamp</function> and
-       <function>to_date</function> in one of two ways:
-       <itemizedlist>
-        <listitem>
-         <para>
-          Year, week, and weekday:  for example <literal>to_date('2006-42-4',
-          'IYYY-IW-ID')</literal> returns the date
-          <literal>2006-10-19</literal>.  If you omit the weekday it
-          is assumed to be 1 (Monday).
-         </para>
-        </listitem>
-        <listitem>
-         <para>
-          Year and day of year:  for example <literal>to_date('2006-291',
-          'IYYY-IDDD')</literal> also returns <literal>2006-10-19</literal>.
-         </para>
-        </listitem>
-       </itemizedlist>
-      </para>
-      <para>
-       Attempting to construct a date using a mixture of ISO week and
-       Gregorian date fields is nonsensical, and will cause an error.  In the
-       context of an ISO year, the concept of a <quote>month</> or <quote>day
-       of month</> has no meaning.  In the context of a Gregorian year, the
-       ISO week has no meaning.  Users should avoid mixing Gregorian and
-       ISO date specifications.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In a conversion from string to <type>timestamp</type>, millisecond
-       (<literal>MS</literal>) or microsecond (<literal>US</literal>)
-       values are used as the
-       seconds digits after the decimal point. For example
-       <literal>to_timestamp('12:3', 'SS:MS')</literal> is not 3 milliseconds,
-       but 300, because the conversion counts it as 12 + 0.3 seconds.
-       This means for the format <literal>SS:MS</literal>, the input values
-       <literal>12:3</literal>, <literal>12:30</literal>, and <literal>12:300</literal> specify the
-       same number of milliseconds. To get three milliseconds, one must use
-       <literal>12:003</literal>, which the conversion counts as
-       12 + 0.003 = 12.003 seconds.
-      </para>
-
-      <para>
-       Here is a more
-       complex example:
-       <literal>to_timestamp('15:12:02.020.001230', 'HH:MI:SS.MS.US')</literal>
-       is 15 hours, 12 minutes, and 2 seconds + 20 milliseconds +
-       1230 microseconds = 2.021230 seconds.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        <function>to_char(..., 'ID')</function>'s day of the week numbering
-        matches the <function>extract(isodow from ...)</function> function, but
-        <function>to_char(..., 'D')</function>'s does not match
-        <function>extract(dow from ...)</function>'s day numbering.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        <function>to_char(interval)</function> formats <literal>HH</> and
-        <literal>HH12</> as shown on a 12-hour clock, i.e. zero hours
-        and 36 hours output as <literal>12</>, while <literal>HH24</>
-        outputs the full hour value, which can exceed 23 for intervals.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </para>
-
-  <para>
-   <xref linkend="functions-formatting-numeric-table"> shows the
-   template patterns available for formatting numeric values.
-  </para>
-
-    <table id="functions-formatting-numeric-table">
-     <title>Template Patterns for Numeric Formatting</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>Pattern</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><literal>9</literal></entry>
-        <entry>value with the specified number of digits</entry>
-       </row>
-       <row>
-        <entry><literal>0</literal></entry>
-        <entry>value with leading zeros</entry>
-       </row>
-       <row>
-        <entry><literal>.</literal> (period)</entry>
-        <entry>decimal point</entry>
-       </row>
-       <row>
-        <entry><literal>,</literal> (comma)</entry>
-        <entry>group (thousand) separator</entry>
-       </row>
-       <row>
-        <entry><literal>PR</literal></entry>
-        <entry>negative value in angle brackets</entry>
-       </row>
-       <row>
-        <entry><literal>S</literal></entry>
-        <entry>sign anchored to number (uses locale)</entry>
-       </row>
-       <row>
-        <entry><literal>L</literal></entry>
-        <entry>currency symbol (uses locale)</entry>
-       </row>
-       <row>
-        <entry><literal>D</literal></entry>
-        <entry>decimal point (uses locale)</entry>
-       </row>
-       <row>
-        <entry><literal>G</literal></entry>
-        <entry>group separator (uses locale)</entry>
-       </row>
-       <row>
-        <entry><literal>MI</literal></entry>
-        <entry>minus sign in specified position (if number &lt; 0)</entry>
-       </row>
-       <row>
-        <entry><literal>PL</literal></entry>
-        <entry>plus sign in specified position (if number &gt; 0)</entry>
-       </row>
-       <row>
-        <entry><literal>SG</literal></entry>
-        <entry>plus/minus sign in specified position</entry>
-       </row>
-       <row>
-        <entry><literal>RN</literal></entry>
-        <entry>Roman numeral (input between 1 and 3999)</entry>
-       </row>
-       <row>
-        <entry><literal>TH</literal> or <literal>th</literal></entry>
-        <entry>ordinal number suffix</entry>
-       </row>
-       <row>
-        <entry><literal>V</literal></entry>
-        <entry>shift specified number of digits (see notes)</entry>
-       </row>
-       <row>
-        <entry><literal>EEEE</literal></entry>
-        <entry>exponent for scientific notation</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Usage notes for numeric formatting:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       A sign formatted using <literal>SG</literal>, <literal>PL</literal>, or
-       <literal>MI</literal> is not anchored to
-       the number; for example,
-       <literal>to_char(-12, 'MI9999')</literal> produces <literal>'-&nbsp;&nbsp;12'</literal>
-       but <literal>to_char(-12, 'S9999')</literal> produces <literal>'&nbsp;&nbsp;-12'</literal>.
-       The Oracle implementation does not allow the use of
-       <literal>MI</literal> before <literal>9</literal>, but rather
-       requires that <literal>9</literal> precede
-       <literal>MI</literal>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>9</literal> results in a value with the same number of
-       digits as there are <literal>9</literal>s. If a digit is
-       not available it outputs a space.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>TH</literal> does not convert values less than zero
-       and does not convert fractional numbers.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>PL</literal>, <literal>SG</literal>, and
-<!## PG>
-       <literal>TH</literal> are <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-       <literal>TH</literal> are <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-       <literal>TH</literal> are <productname>Postgres-XL</productname>
-<!## end>
-       extensions.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>V</literal> effectively
-       multiplies the input values by
-       <literal>10^<replaceable>n</replaceable></literal>, where
-       <replaceable>n</replaceable> is the number of digits following
-       <literal>V</literal>.
-       <function>to_char</function> does not support the use of
-       <literal>V</literal> combined with a decimal point
-       (e.g., <literal>99.9V99</literal> is not allowed).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>EEEE</literal> (scientific notation) cannot be used in
-       combination with any of the other formatting patterns or
-       modifiers other than digit and decimal point patterns, and must be at the end of the format string
-       (e.g., <literal>9.99EEEE</literal> is a valid pattern).
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    Certain modifiers can be applied to any template pattern to alter its
-    behavior.  For example, <literal>FM9999</literal>
-    is the <literal>9999</literal> pattern with the
-    <literal>FM</literal> modifier.
-    <xref linkend="functions-formatting-numericmod-table"> shows the
-    modifier patterns for numeric formatting.
-   </para>
-
-    <table id="functions-formatting-numericmod-table">
-     <title>Template Pattern Modifiers for Numeric Formatting</title>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Modifier</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><literal>FM</literal> prefix</entry>
-        <entry>fill mode (suppress padding blanks and trailing zeroes)</entry>
-        <entry><literal>FM9999</literal></entry>
-       </row>
-       <row>
-        <entry><literal>TH</literal> suffix</entry>
-        <entry>upper case ordinal number suffix</entry>
-        <entry><literal>999TH</literal></entry>
-       </row>
-       <row>
-        <entry><literal>th</literal> suffix</entry>
-        <entry>lower case ordinal number suffix</entry>
-        <entry><literal>999th</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-  <para>
-   <xref linkend="functions-formatting-examples-table"> shows some
-   examples of the use of the <function>to_char</function> function.
-  </para>
-
-    <table id="functions-formatting-examples-table">
-     <title><function>to_char</function> Examples</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>Expression</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><literal>to_char(current_timestamp, 'Day,&nbsp;DD&nbsp;&nbsp;HH12:MI:SS')</literal></entry>
-        <entry><literal>'Tuesday&nbsp;&nbsp;,&nbsp;06&nbsp;&nbsp;05:39:18'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(current_timestamp, 'FMDay,&nbsp;FMDD&nbsp;&nbsp;HH12:MI:SS')</literal></entry>
-        <entry><literal>'Tuesday,&nbsp;6&nbsp;&nbsp;05:39:18'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(-0.1, '99.99')</literal></entry>
-        <entry><literal>'&nbsp;&nbsp;-.10'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(-0.1, 'FM9.99')</literal></entry>
-        <entry><literal>'-.1'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(0.1, '0.9')</literal></entry>
-        <entry><literal>'&nbsp;0.1'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(12, '9990999.9')</literal></entry>
-        <entry><literal>'&nbsp;&nbsp;&nbsp;&nbsp;0012.0'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(12, 'FM9990999.9')</literal></entry>
-        <entry><literal>'0012.'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485, '999')</literal></entry>
-        <entry><literal>'&nbsp;485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(-485, '999')</literal></entry>
-        <entry><literal>'-485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485, '9&nbsp;9&nbsp;9')</literal></entry>
-        <entry><literal>'&nbsp;4&nbsp;8&nbsp;5'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(1485, '9,999')</literal></entry>
-        <entry><literal>'&nbsp;1,485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(1485, '9G999')</literal></entry>
-        <entry><literal>'&nbsp;1&nbsp;485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(148.5, '999.999')</literal></entry>
-        <entry><literal>'&nbsp;148.500'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(148.5, 'FM999.999')</literal></entry>
-        <entry><literal>'148.5'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(148.5, 'FM999.990')</literal></entry>
-        <entry><literal>'148.500'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(148.5, '999D999')</literal></entry>
-        <entry><literal>'&nbsp;148,500'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(3148.5, '9G999D999')</literal></entry>
-        <entry><literal>'&nbsp;3&nbsp;148,500'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(-485, '999S')</literal></entry>
-        <entry><literal>'485-'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(-485, '999MI')</literal></entry>
-        <entry><literal>'485-'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485, '999MI')</literal></entry>
-        <entry><literal>'485&nbsp;'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485, 'FM999MI')</literal></entry>
-        <entry><literal>'485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485, 'PL999')</literal></entry>
-        <entry><literal>'+485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485, 'SG999')</literal></entry>
-        <entry><literal>'+485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(-485, 'SG999')</literal></entry>
-        <entry><literal>'-485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(-485, '9SG99')</literal></entry>
-        <entry><literal>'4-85'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(-485, '999PR')</literal></entry>
-        <entry><literal>'&lt;485&gt;'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485, 'L999')</literal></entry>
-        <entry><literal>'DM&nbsp;485</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485, 'RN')</literal></entry>
-        <entry><literal>'&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDLXXXV'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485, 'FMRN')</literal></entry>
-        <entry><literal>'CDLXXXV'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(5.2, 'FMRN')</literal></entry>
-        <entry><literal>'V'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(482, '999th')</literal></entry>
-        <entry><literal>'&nbsp;482nd'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485, '"Good&nbsp;number:"999')</literal></entry>
-        <entry><literal>'Good&nbsp;number:&nbsp;485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485.8, '"Pre:"999"&nbsp;Post:"&nbsp;.999')</literal></entry>
-        <entry><literal>'Pre:&nbsp;485&nbsp;Post:&nbsp;.800'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(12, '99V999')</literal></entry>
-        <entry><literal>'&nbsp;12000'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(12.4, '99V999')</literal></entry>
-        <entry><literal>'&nbsp;12400'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(12.45, '99V9')</literal></entry>
-        <entry><literal>'&nbsp;125'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(0.0004859, '9.99EEEE')</literal></entry>
-        <entry><literal>' 4.86e-04'</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-  </sect1>
-
-
-  <sect1 id="functions-datetime">
-   <title>Date/Time Functions and Operators</title>
-&common;
-  <para>
-   <xref linkend="functions-datetime-table"> shows the available
-   functions for date/time value processing, with details appearing in
-   the following subsections.  <xref
-   linkend="operators-datetime-table"> illustrates the behaviors of
-   the basic arithmetic operators (<literal>+</literal>,
-   <literal>*</literal>, etc.).  For formatting functions, refer to
-   <xref linkend="functions-formatting">.  You should be familiar with
-   the background information on date/time data types from <xref
-   linkend="datatype-datetime">.
-  </para>
-
-  <para>
-   All the functions and operators described below that take <type>time</type> or <type>timestamp</type>
-   inputs actually come in two variants: one that takes <type>time with time zone</type> or <type>timestamp
-   with time zone</type>, and one that takes <type>time without time zone</type> or <type>timestamp without time zone</type>.
-   For brevity, these variants are not shown separately.  Also, the
-   <literal>+</> and <literal>*</> operators come in commutative pairs (for
-   example both date + integer and integer + date); we show only one of each
-   such pair.
-  </para>
-
-    <table id="operators-datetime-table">
-     <title>Date/Time Operators</title>
-
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Operator</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry><literal>date '2001-09-28' + integer '7'</literal></entry>
-        <entry><literal>date '2001-10-05'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry><literal>date '2001-09-28' + interval '1 hour'</literal></entry>
-        <entry><literal>timestamp '2001-09-28 01:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry><literal>date '2001-09-28' + time '03:00'</literal></entry>
-        <entry><literal>timestamp '2001-09-28 03:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry><literal>interval '1 day' + interval '1 hour'</literal></entry>
-        <entry><literal>interval '1 day 01:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry><literal>timestamp '2001-09-28 01:00' + interval '23 hours'</literal></entry>
-        <entry><literal>timestamp '2001-09-29 00:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry><literal>time '01:00' + interval '3 hours'</literal></entry>
-        <entry><literal>time '04:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><literal>- interval '23 hours'</literal></entry>
-        <entry><literal>interval '-23:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><literal>date '2001-10-01' - date '2001-09-28'</literal></entry>
-        <entry><literal>integer '3'</literal> (days)</entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><literal>date '2001-10-01' - integer '7'</literal></entry>
-        <entry><literal>date '2001-09-24'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><literal>date '2001-09-28' - interval '1 hour'</literal></entry>
-        <entry><literal>timestamp '2001-09-27 23:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><literal>time '05:00' - time '03:00'</literal></entry>
-        <entry><literal>interval '02:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><literal>time '05:00' - interval '2 hours'</literal></entry>
-        <entry><literal>time '03:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><literal>timestamp '2001-09-28 23:00' - interval '23 hours'</literal></entry>
-        <entry><literal>timestamp '2001-09-28 00:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><literal>interval '1 day' - interval '1 hour'</literal></entry>
-        <entry><literal>interval '1 day -01:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><literal>timestamp '2001-09-29 03:00' - timestamp '2001-09-27 12:00'</literal></entry>
-        <entry><literal>interval '1 day 15:00:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>*</literal> </entry>
-        <entry><literal>900 * interval '1 second'</literal></entry>
-        <entry><literal>interval '00:15:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>*</literal> </entry>
-        <entry><literal>21 * interval '1 day'</literal></entry>
-        <entry><literal>interval '21 days'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>*</literal> </entry>
-        <entry><literal>double precision '3.5' * interval '1 hour'</literal></entry>
-        <entry><literal>interval '03:30:00'</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>/</literal> </entry>
-        <entry><literal>interval '1 hour' / double precision '1.5'</literal></entry>
-        <entry><literal>interval '00:40:00'</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-    <table id="functions-datetime-table">
-     <title>Date/Time Functions</title>
-     <tgroup cols="5">
-      <thead>
-       <row>
-        <entry>Function</entry>
-        <entry>Return Type</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>age</primary>
-         </indexterm>
-         <literal><function>age(<type>timestamp</type>, <type>timestamp</type>)</function></literal>
-        </entry>
-        <entry><type>interval</type></entry>
-        <entry>Subtract arguments, producing a <quote>symbolic</> result that
-        uses years and months</entry>
-        <entry><literal>age(timestamp '2001-04-10', timestamp '1957-06-13')</literal></entry>
-        <entry><literal>43 years 9 mons 27 days</literal></entry>
-       </row>
-
-       <row>
-        <entry><literal><function>age(<type>timestamp</type>)</function></literal></entry>
-        <entry><type>interval</type></entry>
-        <entry>Subtract from <function>current_date</function> (at midnight)</entry>
-        <entry><literal>age(timestamp '1957-06-13')</literal></entry>
-        <entry><literal>43 years 8 mons 3 days</literal></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>clock_timestamp</primary>
-         </indexterm>
-         <literal><function>clock_timestamp()</function></literal>
-        </entry>
-        <entry><type>timestamp with time zone</type></entry>
-        <entry>Current date and time (changes during statement execution);
-         see <xref linkend="functions-datetime-current">
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>current_date</primary>
-         </indexterm>
-         <literal><function>current_date</function></literal>
-        </entry>
-        <entry><type>date</type></entry>
-        <entry>Current date;
-         see <xref linkend="functions-datetime-current">
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>current_time</primary>
-         </indexterm>
-         <literal><function>current_time</function></literal>
-        </entry>
-        <entry><type>time with time zone</type></entry>
-        <entry>Current time of day;
-         see <xref linkend="functions-datetime-current">
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>current_timestamp</primary>
-         </indexterm>
-         <literal><function>current_timestamp</function></literal>
-        </entry>
-        <entry><type>timestamp with time zone</type></entry>
-        <entry>Current date and time (start of current transaction);
-         see <xref linkend="functions-datetime-current">
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>date_part</primary>
-         </indexterm>
-         <literal><function>date_part(<type>text</type>, <type>timestamp</type>)</function></literal>
-        </entry>
-        <entry><type>double precision</type></entry>
-        <entry>Get subfield (equivalent to <function>extract</function>);
-         see <xref linkend="functions-datetime-extract">
-        </entry>
-        <entry><literal>date_part('hour', timestamp '2001-02-16 20:38:40')</literal></entry>
-        <entry><literal>20</literal></entry>
-       </row>
-
-       <row>
-        <entry><literal><function>date_part(<type>text</type>, <type>interval</type>)</function></literal></entry>
-        <entry><type>double precision</type></entry>
-        <entry>Get subfield (equivalent to
-         <function>extract</function>); see <xref linkend="functions-datetime-extract">
-        </entry>
-        <entry><literal>date_part('month', interval '2 years 3 months')</literal></entry>
-        <entry><literal>3</literal></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>date_trunc</primary>
-         </indexterm>
-         <literal><function>date_trunc(<type>text</type>, <type>timestamp</type>)</function></literal>
-        </entry>
-        <entry><type>timestamp</type></entry>
-        <entry>Truncate to specified precision; see also <xref linkend="functions-datetime-trunc">
-        </entry>
-        <entry><literal>date_trunc('hour', timestamp '2001-02-16 20:38:40')</literal></entry>
-        <entry><literal>2001-02-16 20:00:00</literal></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>extract</primary>
-         </indexterm>
-         <literal><function>extract</function>(<parameter>field</parameter> from
-         <type>timestamp</type>)</literal>
-        </entry>
-        <entry><type>double precision</type></entry>
-        <entry>Get subfield; see <xref linkend="functions-datetime-extract">
-        </entry>
-        <entry><literal>extract(hour from timestamp '2001-02-16 20:38:40')</literal></entry>
-        <entry><literal>20</literal></entry>
-       </row>
-
-       <row>
-        <entry><literal><function>extract</function>(<parameter>field</parameter> from
-         <type>interval</type>)</literal></entry>
-        <entry><type>double precision</type></entry>
-        <entry>Get subfield; see <xref linkend="functions-datetime-extract">
-        </entry>
-        <entry><literal>extract(month from interval '2 years 3 months')</literal></entry>
-        <entry><literal>3</literal></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>isfinite</primary>
-         </indexterm>
-         <literal><function>isfinite(<type>date</type>)</function></literal>
-        </entry>
-        <entry><type>boolean</type></entry>
-        <entry>Test for finite date (not +/-infinity)</entry>
-        <entry><literal>isfinite(date '2001-02-16')</literal></entry>
-        <entry><literal>true</literal></entry>
-       </row>
-
-       <row>
-        <entry><literal><function>isfinite(<type>timestamp</type>)</function></literal></entry>
-        <entry><type>boolean</type></entry>
-        <entry>Test for finite time stamp (not +/-infinity)</entry>
-        <entry><literal>isfinite(timestamp '2001-02-16 21:28:30')</literal></entry>
-        <entry><literal>true</literal></entry>
-       </row>
-
-       <row>
-        <entry><literal><function>isfinite(<type>interval</type>)</function></literal></entry>
-        <entry><type>boolean</type></entry>
-        <entry>Test for finite interval</entry>
-        <entry><literal>isfinite(interval '4 hours')</literal></entry>
-        <entry><literal>true</literal></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>justify_days</primary>
-         </indexterm>
-         <literal><function>justify_days(<type>interval</type>)</function></literal>
-        </entry>
-        <entry><type>interval</type></entry>
-        <entry>Adjust interval so 30-day time periods are represented as months</entry>
-        <entry><literal>justify_days(interval '35 days')</literal></entry>
-        <entry><literal>1 mon 5 days</literal></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>justify_hours</primary>
-         </indexterm>
-         <literal><function>justify_hours(<type>interval</type>)</function></literal>
-        </entry>
-        <entry><type>interval</type></entry>
-        <entry>Adjust interval so 24-hour time periods are represented as days</entry>
-        <entry><literal>justify_hours(interval '27 hours')</literal></entry>
-        <entry><literal>1 day 03:00:00</literal></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>justify_interval</primary>
-         </indexterm>
-         <literal><function>justify_interval(<type>interval</type>)</function></literal>
-        </entry>
-        <entry><type>interval</type></entry>
-        <entry>Adjust interval using <function>justify_days</> and <function>justify_hours</>, with additional sign adjustments</entry>
-        <entry><literal>justify_interval(interval '1 mon -1 hour')</literal></entry>
-        <entry><literal>29 days 23:00:00</literal></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>localtime</primary>
-         </indexterm>
-         <literal><function>localtime</function></literal>
-        </entry>
-        <entry><type>time</type></entry>
-        <entry>Current time of day;
-         see <xref linkend="functions-datetime-current">
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>localtimestamp</primary>
-         </indexterm>
-         <literal><function>localtimestamp</function></literal>
-        </entry>
-        <entry><type>timestamp</type></entry>
-        <entry>Current date and time (start of current transaction);
-         see <xref linkend="functions-datetime-current">
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>now</primary>
-         </indexterm>
-         <literal><function>now()</function></literal>
-        </entry>
-        <entry><type>timestamp with time zone</type></entry>
-        <entry>Current date and time (start of current transaction);
-         see <xref linkend="functions-datetime-current">
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>statement_timestamp</primary>
-         </indexterm>
-         <literal><function>statement_timestamp()</function></literal>
-        </entry>
-        <entry><type>timestamp with time zone</type></entry>
-        <entry>Current date and time (start of current statement);
-         see <xref linkend="functions-datetime-current">
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>timeofday</primary>
-         </indexterm>
-         <literal><function>timeofday()</function></literal>
-        </entry>
-        <entry><type>text</type></entry>
-        <entry>Current date and time
-         (like <function>clock_timestamp</>, but as a <type>text</> string);
-         see <xref linkend="functions-datetime-current">
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry>
-         <indexterm>
-          <primary>transaction_timestamp</primary>
-         </indexterm>
-         <literal><function>transaction_timestamp()</function></literal>
-        </entry>
-        <entry><type>timestamp with time zone</type></entry>
-        <entry>Current date and time (start of current transaction);
-         see <xref linkend="functions-datetime-current">
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    In addition to these functions, the SQL <literal>OVERLAPS</> operator is
-    supported:
-<synopsis>
-(<replaceable>start1</replaceable>, <replaceable>end1</replaceable>) OVERLAPS (<replaceable>start2</replaceable>, <replaceable>end2</replaceable>)
-(<replaceable>start1</replaceable>, <replaceable>length1</replaceable>) OVERLAPS (<replaceable>start2</replaceable>, <replaceable>length2</replaceable>)
-</synopsis>
-    This expression yields true when two time periods (defined by their
-    endpoints) overlap, false when they do not overlap.  The endpoints
-    can be specified as pairs of dates, times, or time stamps; or as
-    a date, time, or time stamp followed by an interval.  When a pair
-    of values is provided, either the start or the end can be written
-    first; <literal>OVERLAPS</> automatically takes the earlier value
-    of the pair as the start.  Each time period is considered to
-    represent the half-open interval <replaceable>start</> <literal>&lt;=</>
-    <replaceable>time</> <literal>&lt;</> <replaceable>end</>, unless
-    <replaceable>start</> and <replaceable>end</> are equal in which case it
-    represents that single time instant.  This means for instance that two
-    time periods with only an endpoint in common do not overlap.
-   </para>
-
-<screen>
-SELECT (DATE '2001-02-16', DATE '2001-12-21') OVERLAPS
-       (DATE '2001-10-30', DATE '2002-10-30');
-<lineannotation>Result: </lineannotation><computeroutput>true</computeroutput>
-SELECT (DATE '2001-02-16', INTERVAL '100 days') OVERLAPS
-       (DATE '2001-10-30', DATE '2002-10-30');
-<lineannotation>Result: </lineannotation><computeroutput>false</computeroutput>
-SELECT (DATE '2001-10-29', DATE '2001-10-30') OVERLAPS
-       (DATE '2001-10-30', DATE '2001-10-31');
-<lineannotation>Result: </lineannotation><computeroutput>false</computeroutput>
-SELECT (DATE '2001-10-30', DATE '2001-10-30') OVERLAPS
-       (DATE '2001-10-30', DATE '2001-10-31');
-<lineannotation>Result: </lineannotation><computeroutput>true</computeroutput>
-</screen>
-
-  <para>
-   When adding an <type>interval</type> value to (or subtracting an
-   <type>interval</type> value from) a <type>timestamp with time zone</type>
-   value, the days component advances (or decrements) the date of the
-   <type>timestamp with time zone</type> by the indicated number of days.
-   Across daylight saving time changes (with the session time zone set to a
-   time zone that recognizes DST), this means <literal>interval '1 day'</literal>
-   does not necessarily equal <literal>interval '24 hours'</literal>.
-   For example, with the session time zone set to <literal>CST7CDT</literal>,
-   <literal>timestamp with time zone '2005-04-02 12:00-07' + interval '1 day' </literal>
-   will produce <literal>timestamp with time zone '2005-04-03 12:00-06'</literal>,
-   while adding <literal>interval '24 hours'</literal> to the same initial
-   <type>timestamp with time zone</type> produces
-   <literal>timestamp with time zone '2005-04-03 13:00-06'</literal>, as there is
-   a change in daylight saving time at <literal>2005-04-03 02:00</literal> in time zone
-   <literal>CST7CDT</literal>.
-  </para>
-
-  <para>
-   Note there can be ambiguity in the <literal>months</> returned by
-   <function>age</> because different months have a different number of
-<!## PG>
-   days.  <productname>PostgreSQL</>'s approach uses the month from the
-<!## end>
-<!## XC>
-   days.  <productname>Postgres-XC</>'s approach uses the month from the
-<!## end>
-<!## XL>
-   days.  <productname>Postgres-XL</>'s approach uses the month from the
-<!## end>
-   earlier of the two dates when calculating partial months.  For example,
-   <literal>age('2004-06-01', '2004-04-30')</> uses April to yield
-   <literal>1 mon 1 day</>, while using May would yield <literal>1 mon 2
-   days</> because May has 31 days, while April has only 30.
-  </para>
-
-  <sect2 id="functions-datetime-extract">
-   <title><function>EXTRACT</function>, <function>date_part</function></title>
-
-   <indexterm>
-    <primary>date_part</primary>
-   </indexterm>
-   <indexterm>
-    <primary>extract</primary>
-   </indexterm>
-
-<synopsis>
-EXTRACT(<replaceable>field</replaceable> FROM <replaceable>source</replaceable>)
-</synopsis>
-&common;
-   <para>
-    The <function>extract</function> function retrieves subfields
-    such as year or hour from date/time values.
-    <replaceable>source</replaceable> must be a value expression of
-    type <type>timestamp</type>, <type>time</type>, or <type>interval</type>.
-    (Expressions of type <type>date</type> are
-    cast to <type>timestamp</type> and can therefore be used as
-    well.)  <replaceable>field</replaceable> is an identifier or
-    string that selects what field to extract from the source value.
-    The <function>extract</function> function returns values of type
-    <type>double precision</type>.
-    The following are valid field names:
-
-    <!-- alphabetical -->
-    <variablelist>
-     <varlistentry>
-      <term><literal>century</literal></term>
-      <listitem>
-       <para>
-        The century
-       </para>
-
-<screen>
-SELECT EXTRACT(CENTURY FROM TIMESTAMP '2000-12-16 12:21:13');
-<lineannotation>Result: </lineannotation><computeroutput>20</computeroutput>
-SELECT EXTRACT(CENTURY FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>21</computeroutput>
-</screen>
-
-       <para>
-        The first century starts at 0001-01-01 00:00:00 AD, although
-        they did not know it at the time. This definition applies to all
-        Gregorian calendar countries. There is no century number 0,
-        you go from -1 century to 1 century.
-
-        If you disagree with this, please write your complaint to:
-        Pope, Cathedral Saint-Peter of Roma, Vatican.
-       </para>
-
-       <para>
-        <productname>PostgreSQL</productname> releases before 8.0 did not
-        follow the conventional numbering of centuries, but just returned
-        the year field divided by 100.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>day</literal></term>
-      <listitem>
-       <para>
-        For <type>timestamp</type> values, the day (of the month) field
-        (1 - 31) ; for <type>interval</type> values, the number of days
-       </para>
-
-<screen>
-SELECT EXTRACT(DAY FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>16</computeroutput>
-
-SELECT EXTRACT(DAY FROM INTERVAL '40 days 1 minute');
-<lineannotation>Result: </lineannotation><computeroutput>40</computeroutput>
-</screen>
-
-
-
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>decade</literal></term>
-      <listitem>
-       <para>
-        The year field divided by 10
-       </para>
-
-<screen>
-SELECT EXTRACT(DECADE FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>200</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>dow</literal></term>
-      <listitem>
-       <para>
-        The day of the week as Sunday(<literal>0</>) to
-        Saturday(<literal>6</>)
-       </para>
-
-<screen>
-SELECT EXTRACT(DOW FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>5</computeroutput>
-</screen>
-       <para>
-        Note that <function>extract</function>'s day of the week numbering
-        differs from that of the <function>to_char(...,
-        'D')</function> function.
-       </para>
-
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>doy</literal></term>
-      <listitem>
-       <para>
-        The day of the year (1 - 365/366)
-       </para>
-
-<screen>
-SELECT EXTRACT(DOY FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>47</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>epoch</literal></term>
-      <listitem>
-       <para>
-        For <type>date</type> and <type>timestamp</type> values, the
-        number of seconds since 1970-01-01 00:00:00 UTC (can be negative);
-        for <type>interval</type> values, the total number
-        of seconds in the interval
-       </para>
-
-<screen>
-SELECT EXTRACT(EPOCH FROM TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40.12-08');
-<lineannotation>Result: </lineannotation><computeroutput>982384720.12</computeroutput>
-
-SELECT EXTRACT(EPOCH FROM INTERVAL '5 days 3 hours');
-<lineannotation>Result: </lineannotation><computeroutput>442800</computeroutput>
-</screen>
-
-       <para>
-        Here is how you can convert an epoch value back to a time
-        stamp:
-       </para>
-<screen>
-SELECT TIMESTAMP WITH TIME ZONE 'epoch' + 982384720.12 * INTERVAL '1 second';
-</screen>
-       <para>
-        (The <function>to_timestamp</> function encapsulates the above
-        conversion.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>hour</literal></term>
-      <listitem>
-       <para>
-        The hour field (0 - 23)
-       </para>
-
-<screen>
-SELECT EXTRACT(HOUR FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>20</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>isodow</literal></term>
-      <listitem>
-       <para>
-        The day of the week as Monday(<literal>1</>) to
-        Sunday(<literal>7</>)
-       </para>
-
-<screen>
-SELECT EXTRACT(ISODOW FROM TIMESTAMP '2001-02-18 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>7</computeroutput>
-</screen>
-       <para>
-        This is identical to <literal>dow</> except for Sunday.  This
-        matches the <acronym>ISO</> 8601 day of the week numbering.
-       </para>
-
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>isoyear</literal></term>
-      <listitem>
-       <para>
-        The <acronym>ISO</acronym> 8601 year that the date falls in (not applicable to intervals)
-       </para>
-
-<screen>
-SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-01');
-<lineannotation>Result: </lineannotation><computeroutput>2005</computeroutput>
-SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-02');
-<lineannotation>Result: </lineannotation><computeroutput>2006</computeroutput>
-</screen>
-
-       <para>
-        Each <acronym>ISO</acronym> year begins with the Monday of the week containing the 4th of January, so in early January or late December the <acronym>ISO</acronym> year may be different from the Gregorian year.  See the <literal>week</literal> field for more information.
-       </para>
-       <para>
-        This field is not available in PostgreSQL releases prior to 8.3.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>microseconds</literal></term>
-      <listitem>
-       <para>
-        The seconds field, including fractional parts, multiplied by 1
-        000 000;  note that this includes full seconds
-       </para>
-
-<screen>
-SELECT EXTRACT(MICROSECONDS FROM TIME '17:12:28.5');
-<lineannotation>Result: </lineannotation><computeroutput>28500000</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>millennium</literal></term>
-      <listitem>
-       <para>
-        The millennium
-       </para>
-
-<screen>
-SELECT EXTRACT(MILLENNIUM FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>3</computeroutput>
-</screen>
-
-       <para>
-        Years in the 1900s are in the second millennium.
-        The third millennium started January 1, 2001.
-       </para>
-
-       <para>
-        <productname>PostgreSQL</productname> releases before 8.0 did not
-        follow the conventional numbering of millennia, but just returned
-        the year field divided by 1000.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>milliseconds</literal></term>
-      <listitem>
-       <para>
-        The seconds field, including fractional parts, multiplied by
-        1000.  Note that this includes full seconds.
-       </para>
-
-<screen>
-SELECT EXTRACT(MILLISECONDS FROM TIME '17:12:28.5');
-<lineannotation>Result: </lineannotation><computeroutput>28500</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>minute</literal></term>
-      <listitem>
-       <para>
-        The minutes field (0 - 59)
-       </para>
-
-<screen>
-SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>38</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>month</literal></term>
-      <listitem>
-       <para>
-        For <type>timestamp</type> values, the number of the month
-        within the year (1 - 12) ; for <type>interval</type> values,
-        the number of months, modulo 12 (0 - 11)
-       </para>
-
-<screen>
-SELECT EXTRACT(MONTH FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>2</computeroutput>
-
-SELECT EXTRACT(MONTH FROM INTERVAL '2 years 3 months');
-<lineannotation>Result: </lineannotation><computeroutput>3</computeroutput>
-
-SELECT EXTRACT(MONTH FROM INTERVAL '2 years 13 months');
-<lineannotation>Result: </lineannotation><computeroutput>1</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>quarter</literal></term>
-      <listitem>
-       <para>
-        The quarter of the year (1 - 4) that the date is in
-       </para>
-
-<screen>
-SELECT EXTRACT(QUARTER FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>1</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>second</literal></term>
-      <listitem>
-       <para>
-        The seconds field, including fractional parts (0 -
-        59<footnote><simpara>60 if leap seconds are
-        implemented by the operating system</simpara></footnote>)
-       </para>
-
-<screen>
-SELECT EXTRACT(SECOND FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>40</computeroutput>
-
-SELECT EXTRACT(SECOND FROM TIME '17:12:28.5');
-<lineannotation>Result: </lineannotation><computeroutput>28.5</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>timezone</literal></term>
-      <listitem>
-       <para>
-        The time zone offset from UTC, measured in seconds.  Positive values
-        correspond to time zones east of UTC, negative values to
-        zones west of UTC.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>timezone_hour</literal></term>
-      <listitem>
-       <para>
-        The hour component of the time zone offset
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>timezone_minute</literal></term>
-      <listitem>
-       <para>
-        The minute component of the time zone offset
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>week</literal></term>
-      <listitem>
-       <para>
-        The number of the week of the year that the day is in.  By definition
-        (<acronym>ISO</acronym> 8601), the first week of a year
-        contains January 4 of that year.  (The <acronym>ISO</acronym>-8601
-        week starts on Monday.)  In other words, the first Thursday of
-        a year is in week 1 of that year.
-       </para>
-       <para>
-        Because of this, it is possible for early January dates to be part of the
-        52nd or 53rd week of the previous year.  For example, <literal>2005-01-01</>
-        is part of the 53rd week of year 2004, and <literal>2006-01-01</> is part of
-        the 52nd week of year 2005.
-       </para>
-
-<screen>
-SELECT EXTRACT(WEEK FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>7</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>year</literal></term>
-      <listitem>
-       <para>
-        The year field.  Keep in mind there is no <literal>0 AD</>, so subtracting
-        <literal>BC</> years from <literal>AD</> years should be done with care.
-       </para>
-
-<screen>
-SELECT EXTRACT(YEAR FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>2001</computeroutput>
-</screen>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    The <function>extract</function> function is primarily intended
-    for computational processing.  For formatting date/time values for
-    display, see <xref linkend="functions-formatting">.
-   </para>
-
-   <para>
-    The <function>date_part</function> function is modeled on the traditional
-    <productname>Ingres</productname> equivalent to the
-    <acronym>SQL</acronym>-standard function <function>extract</function>:
-<synopsis>
-date_part('<replaceable>field</replaceable>', <replaceable>source</replaceable>)
-</synopsis>
-    Note that here the <replaceable>field</replaceable> parameter needs to
-    be a string value, not a name.  The valid field names for
-    <function>date_part</function> are the same as for
-    <function>extract</function>.
-   </para>
-
-<screen>
-SELECT date_part('day', TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>16</computeroutput>
-
-SELECT date_part('hour', INTERVAL '4 hours 3 minutes');
-<lineannotation>Result: </lineannotation><computeroutput>4</computeroutput>
-</screen>
-
-  </sect2>
-
-  <sect2 id="functions-datetime-trunc">
-   <title><function>date_trunc</function></title>
-
-   <indexterm>
-    <primary>date_trunc</primary>
-   </indexterm>
-&common;
-   <para>
-    The function <function>date_trunc</function> is conceptually
-    similar to the <function>trunc</function> function for numbers.
-   </para>
-
-   <para>
-<synopsis>
-date_trunc('<replaceable>field</replaceable>', <replaceable>source</replaceable>)
-</synopsis>
-    <replaceable>source</replaceable> is a value expression of type
-    <type>timestamp</type> or <type>interval</>.
-    (Values of type <type>date</type> and
-    <type>time</type> are cast automatically to <type>timestamp</type> or
-    <type>interval</>, respectively.)
-    <replaceable>field</replaceable> selects to which precision to
-    truncate the input value.  The return value is of type
-    <type>timestamp</type> or <type>interval</>
-    with all fields that are less significant than the
-    selected one set to zero (or one, for day and month).
-   </para>
-
-   <para>
-    Valid values for <replaceable>field</replaceable> are:
-    <simplelist>
-     <member><literal>microseconds</literal></member>
-     <member><literal>milliseconds</literal></member>
-     <member><literal>second</literal></member>
-     <member><literal>minute</literal></member>
-     <member><literal>hour</literal></member>
-     <member><literal>day</literal></member>
-     <member><literal>week</literal></member>
-     <member><literal>month</literal></member>
-     <member><literal>quarter</literal></member>
-     <member><literal>year</literal></member>
-     <member><literal>decade</literal></member>
-     <member><literal>century</literal></member>
-     <member><literal>millennium</literal></member>
-    </simplelist>
-   </para>
-
-   <para>
-    Examples:
-<screen>
-SELECT date_trunc('hour', TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>2001-02-16 20:00:00</computeroutput>
-
-SELECT date_trunc('year', TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>2001-01-01 00:00:00</computeroutput>
-</screen>
-   </para>
-  </sect2>
-
-  <sect2 id="functions-datetime-zoneconvert">
-   <title><literal>AT TIME ZONE</literal></title>
-
-   <indexterm>
-    <primary>time zone</primary>
-    <secondary>conversion</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>AT TIME ZONE</primary>
-   </indexterm>
-&common;
-   <para>
-    The <literal>AT TIME ZONE</literal> construct allows conversions
-    of time stamps to different time zones.  <xref
-    linkend="functions-datetime-zoneconvert-table"> shows its
-    variants.
-   </para>
-
-    <table id="functions-datetime-zoneconvert-table">
-     <title><literal>AT TIME ZONE</literal> Variants</title>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Expression</entry>
-        <entry>Return Type</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry>
-         <literal><type>timestamp without time zone</type> AT TIME ZONE <replaceable>zone</></literal>
-        </entry>
-        <entry><type>timestamp with time zone</type></entry>
-        <entry>Treat given time stamp <emphasis>without time zone</> as located in the specified time zone</entry>
-       </row>
-
-       <row>
-        <entry>
-         <literal><type>timestamp with time zone</type> AT TIME ZONE <replaceable>zone</></literal>
-        </entry>
-        <entry><type>timestamp without time zone</type></entry>
-        <entry>Convert given time stamp <emphasis>with time zone</> to the new time
-        zone, with no time zone designation</entry>
-       </row>
-
-       <row>
-        <entry>
-         <literal><type>time with time zone</type> AT TIME ZONE <replaceable>zone</></literal>
-        </entry>
-        <entry><type>time with time zone</type></entry>
-        <entry>Convert given time <emphasis>with time zone</> to the new time zone</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    In these expressions, the desired time zone <replaceable>zone</> can be
-    specified either as a text string (e.g., <literal>'PST'</literal>)
-    or as an interval (e.g., <literal>INTERVAL '-08:00'</literal>).
-    In the text case, a time zone name can be specified in any of the ways
-    described in <xref linkend="datatype-timezones">.
-   </para>
-
-   <para>
-    Examples (assuming the local time zone is <literal>PST8PDT</>):
-<screen>
-SELECT TIMESTAMP '2001-02-16 20:38:40' AT TIME ZONE 'MST';
-<lineannotation>Result: </lineannotation><computeroutput>2001-02-16 19:38:40-08</computeroutput>
-
-SELECT TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40-05' AT TIME ZONE 'MST';
-<lineannotation>Result: </lineannotation><computeroutput>2001-02-16 18:38:40</computeroutput>
-</screen>
-    The first example takes a time stamp without time zone and interprets it as MST time
-    (UTC-7), which is then converted to PST (UTC-8) for display.  The second example takes
-    a time stamp specified in EST (UTC-5) and converts it to local time in MST (UTC-7).
-   </para>
-
-   <para>
-    The function <literal><function>timezone</function>(<replaceable>zone</>,
-    <replaceable>timestamp</>)</literal> is equivalent to the SQL-conforming construct
-    <literal><replaceable>timestamp</> AT TIME ZONE
-    <replaceable>zone</></literal>.
-   </para>
-  </sect2>
-
-  <sect2 id="functions-datetime-current">
-   <title>Current Date/Time</title>
-
-   <indexterm>
-    <primary>date</primary>
-    <secondary>current</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>time</primary>
-    <secondary>current</secondary>
-   </indexterm>
-&common;
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> provides a number of functions
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> provides a number of functions
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> provides a number of functions
-<!## end>
-    that return values related to the current date and time.  These
-    SQL-standard functions all return values based on the start time of
-    the current transaction:
-<synopsis>
-CURRENT_DATE
-CURRENT_TIME
-CURRENT_TIMESTAMP
-CURRENT_TIME(<replaceable>precision</replaceable>)
-CURRENT_TIMESTAMP(<replaceable>precision</replaceable>)
-LOCALTIME
-LOCALTIMESTAMP
-LOCALTIME(<replaceable>precision</replaceable>)
-LOCALTIMESTAMP(<replaceable>precision</replaceable>)
-</synopsis>
-    </para>
-
-    <para>
-     <function>CURRENT_TIME</function> and
-     <function>CURRENT_TIMESTAMP</function> deliver values with time zone;
-     <function>LOCALTIME</function> and
-     <function>LOCALTIMESTAMP</function> deliver values without time zone.
-    </para>
-
-    <para>
-     <function>CURRENT_TIME</function>,
-     <function>CURRENT_TIMESTAMP</function>,
-     <function>LOCALTIME</function>, and
-     <function>LOCALTIMESTAMP</function>
-     can optionally take
-     a precision parameter, which causes the result to be rounded
-     to that many fractional digits in the seconds field.  Without a precision parameter,
-     the result is given to the full available precision.
-    </para>
-
-   <para>
-    Some examples:
-<screen>
-SELECT CURRENT_TIME;
-<lineannotation>Result: </lineannotation><computeroutput>14:39:53.662522-05</computeroutput>
-
-SELECT CURRENT_DATE;
-<lineannotation>Result: </lineannotation><computeroutput>2001-12-23</computeroutput>
-
-SELECT CURRENT_TIMESTAMP;
-<lineannotation>Result: </lineannotation><computeroutput>2001-12-23 14:39:53.662522-05</computeroutput>
-
-SELECT CURRENT_TIMESTAMP(2);
-<lineannotation>Result: </lineannotation><computeroutput>2001-12-23 14:39:53.66-05</computeroutput>
-
-SELECT LOCALTIMESTAMP;
-<lineannotation>Result: </lineannotation><computeroutput>2001-12-23 14:39:53.662522</computeroutput>
-</screen>
-   </para>
-
-   <para>
-    Since these functions return
-    the start time of the current transaction, their values do not
-    change during the transaction. This is considered a feature:
-    the intent is to allow a single transaction to have a consistent
-    notion of the <quote>current</quote> time, so that multiple
-    modifications within the same transaction bear the same
-    time stamp.
-   </para>
-
-   <note>
-    <para>
-     Other database systems might advance these values more
-     frequently.
-    </para>
-   </note>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> also provides functions that
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> also provides functions that
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> also provides functions that
-<!## end>
-    return the start time of the current statement, as well as the actual
-    current time at the instant the function is called.  The complete list
-    of non-SQL-standard time functions is:
-<synopsis>
-transaction_timestamp()
-statement_timestamp()
-clock_timestamp()
-timeofday()
-now()
-</synopsis>
-   </para>
-
-   <para>
-    <function>transaction_timestamp()</> is equivalent to
-    <function>CURRENT_TIMESTAMP</function>, but is named to clearly reflect
-    what it returns.
-    <function>statement_timestamp()</> returns the start time of the current
-    statement (more specifically, the time of receipt of the latest command
-    message from the client).
-    <function>statement_timestamp()</> and <function>transaction_timestamp()</>
-    return the same value during the first command of a transaction, but might
-    differ during subsequent commands.
-    <function>clock_timestamp()</> returns the actual current time, and
-    therefore its value changes even within a single SQL command.
-    <function>timeofday()</> is a historical
-<!## PG>
-    <productname>PostgreSQL</productname> function.  Like
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> function.  Like
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> function.  Like
-<!## end>
-    <function>clock_timestamp()</>, it returns the actual current time,
-    but as a formatted <type>text</> string rather than a <type>timestamp
-    with time zone</> value.
-<!## PG>
-    <function>now()</> is a traditional <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-    <function>now()</> is a traditional <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-    <function>now()</> is a traditional <productname>Postgres-XL</productname>
-<!## end>
-    equivalent to <function>transaction_timestamp()</function>.
-   </para>
-
-   <para>
-    All the date/time data types also accept the special literal value
-    <literal>now</literal> to specify the current date and time (again,
-    interpreted as the transaction start time).  Thus,
-    the following three all return the same result:
-<programlisting>
-SELECT CURRENT_TIMESTAMP;
-SELECT now();
-SELECT TIMESTAMP 'now';  -- incorrect for use with DEFAULT
-</programlisting>
-   </para>
-
-    <tip>
-     <para>
-      You do not want to use the third form when specifying a <literal>DEFAULT</>
-      clause while creating a table.  The system will convert <literal>now</literal>
-      to a <type>timestamp</type> as soon as the constant is parsed, so that when
-      the default value is needed,
-      the time of the table creation would be used!  The first two
-      forms will not be evaluated until the default value is used,
-      because they are function calls.  Thus they will give the desired
-      behavior of defaulting to the time of row insertion.
-     </para>
-    </tip>
-  </sect2>
-
-  <sect2 id="functions-datetime-delay">
-   <title>Delaying Execution</title>
-
-   <indexterm>
-    <primary>pg_sleep</primary>
-   </indexterm>
-   <indexterm>
-    <primary>sleep</primary>
-   </indexterm>
-   <indexterm>
-    <primary>delay</primary>
-   </indexterm>
-&common;
-   <para>
-    The following function is available to delay execution of the server
-    process:
-<synopsis>
-pg_sleep(<replaceable>seconds</replaceable>)
-</synopsis>
-
-    <function>pg_sleep</function> makes the current session's process
-    sleep until <replaceable>seconds</replaceable> seconds have
-    elapsed.  <replaceable>seconds</replaceable> is a value of type
-    <type>double precision</>, so fractional-second delays can be specified.
-    For example:
-
-<programlisting>
-SELECT pg_sleep(1.5);
-</programlisting>
-   </para>
-
-   <note>
-     <para>
-      The effective resolution of the sleep interval is platform-specific;
-      0.01 seconds is a common value.  The sleep delay will be at least as long
-      as specified. It might be longer depending on factors such as server load.
-     </para>
-   </note>
-
-   <warning>
-     <para>
-      Make sure that your session does not hold more locks than necessary
-      when calling <function>pg_sleep</function>.  Otherwise other sessions
-      might have to wait for your sleeping process, slowing down the entire
-      system.
-     </para>
-   </warning>
-  </sect2>
-
- </sect1>
-
-
- <sect1 id="functions-enum">
-  <title>Enum Support Functions</title>
-&common;
-  <para>
-   For enum types (described in <xref linkend="datatype-enum">),
-   there are several functions that allow cleaner programming without
-   hard-coding particular values of an enum type.
-   These are listed in <xref linkend="functions-enum-table">. The examples
-   assume an enum type created as:
-
-<programlisting>
-CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple');
-</programlisting>
-
-  </para>
-
-  <table id="functions-enum-table">
-    <title>Enum Support Functions</title>
-    <tgroup cols="4">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Description</entry>
-       <entry>Example</entry>
-       <entry>Example Result</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>
-         <indexterm>
-          <primary>enum_first</primary>
-         </indexterm>
-         <literal>enum_first(anyenum)</literal>
-       </entry>
-       <entry>Returns the first value of the input enum type</entry>
-       <entry><literal>enum_first(null::rainbow)</literal></entry>
-       <entry><literal>red</literal></entry>
-      </row>
-      <row>
-       <entry>
-         <indexterm>
-          <primary>enum_last</primary>
-         </indexterm>
-         <literal>enum_last(anyenum)</literal>
-       </entry>
-       <entry>Returns the last value of the input enum type</entry>
-       <entry><literal>enum_last(null::rainbow)</literal></entry>
-       <entry><literal>purple</literal></entry>
-      </row>
-      <row>
-       <entry>
-         <indexterm>
-          <primary>enum_range</primary>
-         </indexterm>
-         <literal>enum_range(anyenum)</literal>
-       </entry>
-       <entry>Returns all values of the input enum type in an ordered array</entry>
-       <entry><literal>enum_range(null::rainbow)</literal></entry>
-       <entry><literal>{red,orange,yellow,green,blue,purple}</literal></entry>
-      </row>
-      <row>
-       <entry morerows="2"><literal>enum_range(anyenum, anyenum)</literal></entry>
-       <entry morerows="2">
-        Returns the range between the two given enum values, as an ordered
-        array. The values must be from the same enum type. If the first
-        parameter is null, the result will start with the first value of
-        the enum type.
-        If the second parameter is null, the result will end with the last
-        value of the enum type.
-       </entry>
-       <entry><literal>enum_range('orange'::rainbow, 'green'::rainbow)</literal></entry>
-       <entry><literal>{orange,yellow,green}</literal></entry>
-      </row>
-      <row>
-       <entry><literal>enum_range(NULL, 'green'::rainbow)</literal></entry>
-       <entry><literal>{red,orange,yellow,green}</literal></entry>
-      </row>
-      <row>
-       <entry><literal>enum_range('orange'::rainbow, NULL)</literal></entry>
-       <entry><literal>{orange,yellow,green,blue,purple}</literal></entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    Notice that except for the two-argument form of <function>enum_range</>,
-    these functions disregard the specific value passed to them; they care
-    only about its declared data type.  Either null or a specific value of
-    the type can be passed, with the same result.  It is more common to
-    apply these functions to a table column or function argument than to
-    a hardwired type name as suggested by the examples.
-   </para>
- </sect1>
-
- <sect1 id="functions-geometry">
-  <title>Geometric Functions and Operators</title>
-&common;
-   <para>
-    The geometric types <type>point</type>, <type>box</type>,
-    <type>lseg</type>, <type>line</type>, <type>path</type>,
-    <type>polygon</type>, and <type>circle</type> have a large set of
-    native support functions and operators, shown in <xref
-    linkend="functions-geometry-op-table">, <xref
-    linkend="functions-geometry-func-table">, and <xref
-    linkend="functions-geometry-conv-table">.
-   </para>
-
-   <caution>
-    <para>
-     Note that the <quote>same as</> operator, <literal>~=</>, represents
-     the usual notion of equality for the <type>point</type>,
-     <type>box</type>, <type>polygon</type>, and <type>circle</type> types.
-     Some of these types also have an <literal>=</> operator, but
-     <literal>=</> compares
-     for equal <emphasis>areas</> only.  The other scalar comparison operators
-     (<literal>&lt;=</> and so on) likewise compare areas for these types.
-    </para>
-   </caution>
-
-   <table id="functions-geometry-op-table">
-     <title>Geometric Operators</title>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Operator</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry>Translation</entry>
-        <entry><literal>box '((0,0),(1,1))' + point '(2.0,0)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry>Translation</entry>
-        <entry><literal>box '((0,0),(1,1))' - point '(2.0,0)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>*</literal> </entry>
-        <entry>Scaling/rotation</entry>
-        <entry><literal>box '((0,0),(1,1))' * point '(2.0,0)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>/</literal> </entry>
-        <entry>Scaling/rotation</entry>
-        <entry><literal>box '((0,0),(2,2))' / point '(2.0,0)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>#</literal> </entry>
-        <entry>Point or box of intersection</entry>
-        <entry><literal>'((1,-1),(-1,1))' # '((1,1),(-1,-1))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>#</literal> </entry>
-        <entry>Number of points in path or polygon</entry>
-        <entry><literal># '((1,0),(0,1),(-1,0))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>@-@</literal> </entry>
-        <entry>Length or circumference</entry>
-        <entry><literal>@-@ path '((0,0),(1,0))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>@@</literal> </entry>
-        <entry>Center</entry>
-        <entry><literal>@@ circle '((0,0),10)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>##</literal> </entry>
-        <entry>Closest point to first operand on second operand</entry>
-        <entry><literal>point '(0,0)' ## lseg '((2,0),(0,2))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&lt;-&gt;</literal> </entry>
-        <entry>Distance between</entry>
-        <entry><literal>circle '((0,0),1)' &lt;-&gt; circle '((5,0),1)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&amp;&amp;</literal> </entry>
-        <entry>Overlaps?  (One point in common makes this true.)</entry>
-        <entry><literal>box '((0,0),(1,1))' &amp;&amp; box '((0,0),(2,2))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&lt;&lt;</literal> </entry>
-        <entry>Is strictly left of?</entry>
-        <entry><literal>circle '((0,0),1)' &lt;&lt; circle '((5,0),1)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&gt;&gt;</literal> </entry>
-        <entry>Is strictly right of?</entry>
-        <entry><literal>circle '((5,0),1)' &gt;&gt; circle '((0,0),1)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&amp;&lt;</literal> </entry>
-        <entry>Does not extend to the right of?</entry>
-        <entry><literal>box '((0,0),(1,1))' &amp;&lt; box '((0,0),(2,2))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&amp;&gt;</literal> </entry>
-        <entry>Does not extend to the left of?</entry>
-        <entry><literal>box '((0,0),(3,3))' &amp;&gt; box '((0,0),(2,2))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&lt;&lt;|</literal> </entry>
-        <entry>Is strictly below?</entry>
-        <entry><literal>box '((0,0),(3,3))' &lt;&lt;| box '((3,4),(5,5))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>|&gt;&gt;</literal> </entry>
-        <entry>Is strictly above?</entry>
-        <entry><literal>box '((3,4),(5,5))' |&gt;&gt; box '((0,0),(3,3))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&amp;&lt;|</literal> </entry>
-        <entry>Does not extend above?</entry>
-        <entry><literal>box '((0,0),(1,1))' &amp;&lt;| box '((0,0),(2,2))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>|&amp;&gt;</literal> </entry>
-        <entry>Does not extend below?</entry>
-        <entry><literal>box '((0,0),(3,3))' |&amp;&gt; box '((0,0),(2,2))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&lt;^</literal> </entry>
-        <entry>Is below (allows touching)?</entry>
-        <entry><literal>circle '((0,0),1)' &lt;^ circle '((0,5),1)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&gt;^</literal> </entry>
-        <entry>Is above (allows touching)?</entry>
-        <entry><literal>circle '((0,5),1)' &gt;^ circle '((0,0),1)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>?#</literal> </entry>
-        <entry>Intersects?</entry>
-        <entry><literal>lseg '((-1,0),(1,0))' ?# box '((-2,-2),(2,2))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>?-</literal> </entry>
-        <entry>Is horizontal?</entry>
-        <entry><literal>?- lseg '((-1,0),(1,0))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>?-</literal> </entry>
-        <entry>Are horizontally aligned?</entry>
-        <entry><literal>point '(1,0)' ?- point '(0,0)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>?|</literal> </entry>
-        <entry>Is vertical?</entry>
-        <entry><literal>?| lseg '((-1,0),(1,0))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>?|</literal> </entry>
-        <entry>Are vertically aligned?</entry>
-        <entry><literal>point '(0,1)' ?| point '(0,0)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>?-|</literal> </entry>
-        <entry>Is perpendicular?</entry>
-        <entry><literal>lseg '((0,0),(0,1))' ?-| lseg '((0,0),(1,0))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>?||</literal> </entry>
-        <entry>Are parallel?</entry>
-        <entry><literal>lseg '((-1,0),(1,0))' ?|| lseg '((-1,2),(1,2))'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>@&gt;</literal> </entry>
-        <entry>Contains?</entry>
-        <entry><literal>circle '((0,0),2)' @&gt; point '(1,1)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&lt;@</literal> </entry>
-        <entry>Contained in or on?</entry>
-        <entry><literal>point '(1,1)' &lt;@ circle '((0,0),2)'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>~=</literal> </entry>
-        <entry>Same as?</entry>
-        <entry><literal>polygon '((0,0),(1,1))' ~= polygon '((1,1),(0,0))'</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-   </table>
-
-   <note>
-    <para>
-     Before <productname>PostgreSQL</productname> 8.2, the containment
-     operators <literal>@&gt;</> and <literal>&lt;@</> were respectively
-     called <literal>~</> and <literal>@</>.  These names are still
-     available, but are deprecated and will eventually be removed.
-    </para>
-   </note>
-
-   <indexterm>
-    <primary>area</primary>
-   </indexterm>
-   <indexterm>
-    <primary>center</primary>
-   </indexterm>
-   <indexterm>
-    <primary>diameter</primary>
-   </indexterm>
-   <indexterm>
-    <primary>height</primary>
-   </indexterm>
-   <indexterm>
-    <primary>isclosed</primary>
-   </indexterm>
-   <indexterm>
-    <primary>isopen</primary>
-   </indexterm>
-   <indexterm>
-    <primary>length</primary>
-   </indexterm>
-   <indexterm>
-    <primary>npoints</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pclose</primary>
-   </indexterm>
-   <indexterm>
-    <primary>popen</primary>
-   </indexterm>
-   <indexterm>
-    <primary>radius</primary>
-   </indexterm>
-   <indexterm>
-    <primary>width</primary>
-   </indexterm>
-
-   <table id="functions-geometry-func-table">
-     <title>Geometric Functions</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Function</entry>
-        <entry>Return Type</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><literal><function>area(<replaceable>object</>)</function></literal></entry>
-        <entry><type>double precision</type></entry>
-        <entry>area</entry>
-        <entry><literal>area(box '((0,0),(1,1))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>center(<replaceable>object</>)</function></literal></entry>
-        <entry><type>point</type></entry>
-        <entry>center</entry>
-        <entry><literal>center(box '((0,0),(1,2))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>diameter(<type>circle</>)</function></literal></entry>
-        <entry><type>double precision</type></entry>
-        <entry>diameter of circle</entry>
-        <entry><literal>diameter(circle '((0,0),2.0)')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>height(<type>box</>)</function></literal></entry>
-        <entry><type>double precision</type></entry>
-        <entry>vertical size of box</entry>
-        <entry><literal>height(box '((0,0),(1,1))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>isclosed(<type>path</>)</function></literal></entry>
-        <entry><type>boolean</type></entry>
-        <entry>a closed path?</entry>
-        <entry><literal>isclosed(path '((0,0),(1,1),(2,0))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>isopen(<type>path</>)</function></literal></entry>
-        <entry><type>boolean</type></entry>
-        <entry>an open path?</entry>
-        <entry><literal>isopen(path '[(0,0),(1,1),(2,0)]')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>length(<replaceable>object</>)</function></literal></entry>
-        <entry><type>double precision</type></entry>
-        <entry>length</entry>
-        <entry><literal>length(path '((-1,0),(1,0))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>npoints(<type>path</>)</function></literal></entry>
-        <entry><type>int</type></entry>
-        <entry>number of points</entry>
-        <entry><literal>npoints(path '[(0,0),(1,1),(2,0)]')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>npoints(<type>polygon</>)</function></literal></entry>
-        <entry><type>int</type></entry>
-        <entry>number of points</entry>
-        <entry><literal>npoints(polygon '((1,1),(0,0))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>pclose(<type>path</>)</function></literal></entry>
-        <entry><type>path</type></entry>
-        <entry>convert path to closed</entry>
-        <entry><literal>pclose(path '[(0,0),(1,1),(2,0)]')</literal></entry>
-       </row>
-<![IGNORE[
-<!-- Not defined by this name. Implements the intersection operator '#' -->
-       <row>
-        <entry><literal><function>point(<type>lseg</>, <type>lseg</>)</function></literal></entry>
-        <entry><type>point</type></entry>
-        <entry>intersection</entry>
-        <entry><literal>point(lseg '((-1,0),(1,0))',lseg '((-2,-2),(2,2))')</literal></entry>
-       </row>
-]]>
-       <row>
-        <entry><literal><function>popen(<type>path</>)</function></literal></entry>
-        <entry><type>path</type></entry>
-        <entry>convert path to open</entry>
-        <entry><literal>popen(path '((0,0),(1,1),(2,0))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>radius(<type>circle</type>)</function></literal></entry>
-        <entry><type>double precision</type></entry>
-        <entry>radius of circle</entry>
-        <entry><literal>radius(circle '((0,0),2.0)')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>width(<type>box</>)</function></literal></entry>
-        <entry><type>double precision</type></entry>
-        <entry>horizontal size of box</entry>
-        <entry><literal>width(box '((0,0),(1,1))')</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-   </table>
-
-   <table id="functions-geometry-conv-table">
-     <title>Geometric Type Conversion Functions</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Function</entry>
-        <entry>Return Type</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>box</primary>
-         </indexterm>
-         <literal><function>box(<type>circle</type>)</function></literal>
-        </entry>
-        <entry><type>box</type></entry>
-        <entry>circle to box</entry>
-        <entry><literal>box(circle '((0,0),2.0)')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>box(<type>point</type>, <type>point</type>)</function></literal></entry>
-        <entry><type>box</type></entry>
-        <entry>points to box</entry>
-        <entry><literal>box(point '(0,0)', point '(1,1)')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>box(<type>polygon</type>)</function></literal></entry>
-        <entry><type>box</type></entry>
-        <entry>polygon to box</entry>
-        <entry><literal>box(polygon '((0,0),(1,1),(2,0))')</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>circle</primary>
-         </indexterm>
-         <literal><function>circle(<type>box</type>)</function></literal>
-        </entry>
-        <entry><type>circle</type></entry>
-        <entry>box to circle</entry>
-        <entry><literal>circle(box '((0,0),(1,1))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>circle(<type>point</type>, <type>double precision</type>)</function></literal></entry>
-        <entry><type>circle</type></entry>
-        <entry>center and radius to circle</entry>
-        <entry><literal>circle(point '(0,0)', 2.0)</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>circle(<type>polygon</type>)</function></literal></entry>
-        <entry><type>circle</type></entry>
-        <entry>polygon to circle</entry>
-        <entry><literal>circle(polygon '((0,0),(1,1),(2,0))')</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>lseg</primary>
-         </indexterm>
-         <literal><function>lseg(<type>box</type>)</function></literal>
-        </entry>
-        <entry><type>lseg</type></entry>
-        <entry>box diagonal to line segment</entry>
-        <entry><literal>lseg(box '((-1,0),(1,0))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>lseg(<type>point</type>, <type>point</type>)</function></literal></entry>
-        <entry><type>lseg</type></entry>
-        <entry>points to line segment</entry>
-        <entry><literal>lseg(point '(-1,0)', point '(1,0)')</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>path</primary>
-         </indexterm>
-         <literal><function>path(<type>polygon</type>)</function></literal>
-        </entry>
-        <entry><type>point</type></entry>
-        <entry>polygon to path</entry>
-        <entry><literal>path(polygon '((0,0),(1,1),(2,0))')</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>point</primary>
-         </indexterm>
-         <literal><function>point</function>(<type>double
-         precision</type>, <type>double precision</type>)</literal>
-        </entry>
-        <entry><type>point</type></entry>
-        <entry>construct point</entry>
-        <entry><literal>point(23.4, -44.5)</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>point(<type>box</type>)</function></literal></entry>
-        <entry><type>point</type></entry>
-        <entry>center of box</entry>
-        <entry><literal>point(box '((-1,0),(1,0))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>point(<type>circle</type>)</function></literal></entry>
-        <entry><type>point</type></entry>
-        <entry>center of circle</entry>
-        <entry><literal>point(circle '((0,0),2.0)')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>point(<type>lseg</type>)</function></literal></entry>
-        <entry><type>point</type></entry>
-        <entry>center of line segment</entry>
-        <entry><literal>point(lseg '((-1,0),(1,0))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>point(<type>polygon</type>)</function></literal></entry>
-        <entry><type>point</type></entry>
-        <entry>center of polygon</entry>
-        <entry><literal>point(polygon '((0,0),(1,1),(2,0))')</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>polygon</primary>
-         </indexterm>
-         <literal><function>polygon(<type>box</type>)</function></literal>
-        </entry>
-        <entry><type>polygon</type></entry>
-        <entry>box to 4-point polygon</entry>
-        <entry><literal>polygon(box '((0,0),(1,1))')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>polygon(<type>circle</type>)</function></literal></entry>
-        <entry><type>polygon</type></entry>
-        <entry>circle to 12-point polygon</entry>
-        <entry><literal>polygon(circle '((0,0),2.0)')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>polygon(<replaceable class="parameter">npts</replaceable>, <type>circle</type>)</function></literal></entry>
-        <entry><type>polygon</type></entry>
-        <entry>circle to <replaceable class="parameter">npts</replaceable>-point polygon</entry>
-        <entry><literal>polygon(12, circle '((0,0),2.0)')</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>polygon(<type>path</type>)</function></literal></entry>
-        <entry><type>polygon</type></entry>
-        <entry>path to polygon</entry>
-        <entry><literal>polygon(path '((0,0),(1,1),(2,0))')</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-   </table>
-
-    <para>
-     It is possible to access the two component numbers of a <type>point</>
-     as though the point were an array with indexes 0 and 1.  For example, if
-     <literal>t.p</> is a <type>point</> column then
-     <literal>SELECT p[0] FROM t</> retrieves the X coordinate and
-     <literal>UPDATE t SET p[1] = ...</> changes the Y coordinate.
-     In the same way, a value of type <type>box</> or <type>lseg</> can be treated
-     as an array of two <type>point</> values.
-    </para>
-
-    <para>
-     The <function>area</function> function works for the types
-     <type>box</type>, <type>circle</type>, and <type>path</type>.
-     The <function>area</function> function only works on the
-     <type>path</type> data type if the points in the
-     <type>path</type> are non-intersecting.  For example, the
-     <type>path</type>
-     <literal>'((0,0),(0,1),(2,1),(2,2),(1,2),(1,0),(0,0))'::PATH</literal>
-     will not work;  however, the following visually identical
-     <type>path</type>
-     <literal>'((0,0),(0,1),(1,1),(1,2),(2,2),(2,1),(1,1),(1,0),(0,0))'::PATH</literal>
-     will work.  If the concept of an intersecting versus
-     non-intersecting <type>path</type> is confusing, draw both of the
-     above <type>path</type>s side by side on a piece of graph paper.
-    </para>
-
-  </sect1>
-
-
- <sect1 id="functions-net">
-  <title>Network Address Functions and Operators</title>
-&common;
-  <para>
-   <xref linkend="cidr-inet-operators-table"> shows the operators
-   available for the <type>cidr</type> and <type>inet</type> types.
-   The operators <literal>&lt;&lt;</literal>,
-   <literal>&lt;&lt;=</literal>, <literal>&gt;&gt;</literal>, and
-   <literal>&gt;&gt;=</literal> test for subnet inclusion.  They
-   consider only the network parts of the two addresses (ignoring any
-   host part) and determine whether one network is identical to
-   or a subnet of the other.
-  </para>
-
-    <table id="cidr-inet-operators-table">
-     <title><type>cidr</type> and <type>inet</type> Operators</title>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Operator</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry> <literal>&lt;</literal> </entry>
-        <entry>is less than</entry>
-        <entry><literal>inet '192.168.1.5' &lt; inet '192.168.1.6'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&lt;=</literal> </entry>
-        <entry>is less than or equal</entry>
-        <entry><literal>inet '192.168.1.5' &lt;= inet '192.168.1.5'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>=</literal> </entry>
-        <entry>equals</entry>
-        <entry><literal>inet '192.168.1.5' = inet '192.168.1.5'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&gt;=</literal> </entry>
-        <entry>is greater or equal</entry>
-        <entry><literal>inet '192.168.1.5' &gt;= inet '192.168.1.5'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&gt;</literal> </entry>
-        <entry>is greater than</entry>
-        <entry><literal>inet '192.168.1.5' &gt; inet '192.168.1.4'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&lt;&gt;</literal> </entry>
-        <entry>is not equal</entry>
-        <entry><literal>inet '192.168.1.5' &lt;&gt; inet '192.168.1.4'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&lt;&lt;</literal> </entry>
-        <entry>is contained within</entry>
-        <entry><literal>inet '192.168.1.5' &lt;&lt; inet '192.168.1/24'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&lt;&lt;=</literal> </entry>
-        <entry>is contained within or equals</entry>
-        <entry><literal>inet '192.168.1/24' &lt;&lt;= inet '192.168.1/24'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&gt;&gt;</literal> </entry>
-        <entry>contains</entry>
-        <entry><literal>inet '192.168.1/24' &gt;&gt; inet '192.168.1.5'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&gt;&gt;=</literal> </entry>
-        <entry>contains or equals</entry>
-        <entry><literal>inet '192.168.1/24' &gt;&gt;= inet '192.168.1/24'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>~</literal> </entry>
-        <entry>bitwise NOT</entry>
-        <entry><literal>~ inet '192.168.1.6'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&amp;</literal> </entry>
-        <entry>bitwise AND</entry>
-        <entry><literal>inet '192.168.1.6' &amp; inet '0.0.0.255'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>|</literal> </entry>
-        <entry>bitwise OR</entry>
-        <entry><literal>inet '192.168.1.6' | inet '0.0.0.255'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry>addition</entry>
-        <entry><literal>inet '192.168.1.6' + 25</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry>subtraction</entry>
-        <entry><literal>inet '192.168.1.43' - 36</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry>subtraction</entry>
-        <entry><literal>inet '192.168.1.43' - inet '192.168.1.19'</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-  <para>
-   <xref linkend="cidr-inet-functions-table"> shows the functions
-   available for use with the <type>cidr</type> and <type>inet</type>
-   types.  The <function>abbrev</function>, <function>host</function>,
-   and <function>text</function>
-   functions are primarily intended to offer alternative display
-   formats.
-  </para>
-
-    <table id="cidr-inet-functions-table">
-     <title><type>cidr</type> and <type>inet</type> Functions</title>
-     <tgroup cols="5">
-      <thead>
-       <row>
-        <entry>Function</entry>
-        <entry>Return Type</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>abbrev</primary>
-         </indexterm>
-         <literal><function>abbrev(<type>inet</type>)</function></literal>
-        </entry>
-        <entry><type>text</type></entry>
-        <entry>abbreviated display format as text</entry>
-        <entry><literal>abbrev(inet '10.1.0.0/16')</literal></entry>
-        <entry><literal>10.1.0.0/16</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>abbrev(<type>cidr</type>)</function></literal></entry>
-        <entry><type>text</type></entry>
-        <entry>abbreviated display format as text</entry>
-        <entry><literal>abbrev(cidr '10.1.0.0/16')</literal></entry>
-        <entry><literal>10.1/16</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>broadcast</primary>
-         </indexterm>
-         <literal><function>broadcast(<type>inet</type>)</function></literal>
-        </entry>
-        <entry><type>inet</type></entry>
-        <entry>broadcast address for network</entry>
-        <entry><literal>broadcast('192.168.1.5/24')</literal></entry>
-        <entry><literal>192.168.1.255/24</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>family</primary>
-         </indexterm>
-         <literal><function>family(<type>inet</type>)</function></literal>
-        </entry>
-        <entry><type>int</type></entry>
-        <entry>extract family of address; <literal>4</literal> for IPv4,
-         <literal>6</literal> for IPv6</entry>
-        <entry><literal>family('::1')</literal></entry>
-        <entry><literal>6</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>host</primary>
-         </indexterm>
-         <literal><function>host(<type>inet</type>)</function></literal>
-        </entry>
-        <entry><type>text</type></entry>
-        <entry>extract IP address as text</entry>
-        <entry><literal>host('192.168.1.5/24')</literal></entry>
-        <entry><literal>192.168.1.5</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>hostmask</primary>
-         </indexterm>
-         <literal><function>hostmask(<type>inet</type>)</function></literal>
-        </entry>
-        <entry><type>inet</type></entry>
-        <entry>construct host mask for network</entry>
-        <entry><literal>hostmask('192.168.23.20/30')</literal></entry>
-        <entry><literal>0.0.0.3</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>masklen</primary>
-         </indexterm>
-         <literal><function>masklen(<type>inet</type>)</function></literal>
-        </entry>
-        <entry><type>int</type></entry>
-        <entry>extract netmask length</entry>
-        <entry><literal>masklen('192.168.1.5/24')</literal></entry>
-        <entry><literal>24</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>netmask</primary>
-         </indexterm>
-         <literal><function>netmask(<type>inet</type>)</function></literal>
-        </entry>
-        <entry><type>inet</type></entry>
-        <entry>construct netmask for network</entry>
-        <entry><literal>netmask('192.168.1.5/24')</literal></entry>
-        <entry><literal>255.255.255.0</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>network</primary>
-         </indexterm>
-         <literal><function>network(<type>inet</type>)</function></literal>
-        </entry>
-        <entry><type>cidr</type></entry>
-        <entry>extract network part of address</entry>
-        <entry><literal>network('192.168.1.5/24')</literal></entry>
-        <entry><literal>192.168.1.0/24</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>set_masklen</primary>
-         </indexterm>
-         <literal><function>set_masklen(<type>inet</type>, <type>int</type>)</function></literal>
-        </entry>
-        <entry><type>inet</type></entry>
-        <entry>set netmask length for <type>inet</type> value</entry>
-        <entry><literal>set_masklen('192.168.1.5/24', 16)</literal></entry>
-        <entry><literal>192.168.1.5/16</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>set_masklen(<type>cidr</type>, <type>int</type>)</function></literal></entry>
-        <entry><type>cidr</type></entry>
-        <entry>set netmask length for <type>cidr</type> value</entry>
-        <entry><literal>set_masklen('192.168.1.0/24'::cidr, 16)</literal></entry>
-        <entry><literal>192.168.0.0/16</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>text</primary>
-         </indexterm>
-         <literal><function>text(<type>inet</type>)</function></literal>
-        </entry>
-        <entry><type>text</type></entry>
-        <entry>extract IP address and netmask length as text</entry>
-        <entry><literal>text(inet '192.168.1.5')</literal></entry>
-        <entry><literal>192.168.1.5/32</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-  <para>
-   Any <type>cidr</> value can be cast to <type>inet</> implicitly
-   or explicitly; therefore, the functions shown above as operating on
-   <type>inet</> also work on <type>cidr</> values.  (Where there are
-   separate functions for <type>inet</> and <type>cidr</>, it is because
-   the behavior should be different for the two cases.)
-   Also, it is permitted to cast an <type>inet</> value to <type>cidr</>.
-   When this is done, any bits to the right of the netmask are silently zeroed
-   to create a valid <type>cidr</> value.
-   In addition,
-   you can cast a text value to <type>inet</> or <type>cidr</>
-   using normal casting syntax: for example,
-   <literal>inet(<replaceable>expression</>)</literal> or
-   <literal><replaceable>colname</>::cidr</literal>.
-  </para>
-
-  <para>
-   <xref linkend="macaddr-functions-table"> shows the functions
-   available for use with the <type>macaddr</type> type.  The function
-   <literal><function>trunc(<type>macaddr</type>)</function></literal> returns a MAC
-   address with the last 3 bytes set to zero.  This can be used to
-   associate the remaining prefix with a manufacturer.
-  </para>
-
-    <table id="macaddr-functions-table">
-     <title><type>macaddr</type> Functions</title>
-     <tgroup cols="5">
-      <thead>
-       <row>
-        <entry>Function</entry>
-        <entry>Return Type</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>trunc</primary>
-         </indexterm>
-         <literal><function>trunc(<type>macaddr</type>)</function></literal>
-        </entry>
-        <entry><type>macaddr</type></entry>
-        <entry>set last 3 bytes to zero</entry>
-        <entry><literal>trunc(macaddr '12:34:56:78:90:ab')</literal></entry>
-        <entry><literal>12:34:56:00:00:00</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    The <type>macaddr</type> type also supports the standard relational
-    operators (<literal>&gt;</literal>, <literal>&lt;=</literal>, etc.) for
-    lexicographical ordering.
-   </para>
-
-  </sect1>
-
-
- <sect1 id="functions-textsearch">
-  <title>Text Search Functions and Operators</title>
-
-   <indexterm zone="datatype-textsearch">
-    <primary>full text search</primary>
-    <secondary>functions and operators</secondary>
-   </indexterm>
-
-   <indexterm zone="datatype-textsearch">
-    <primary>text search</primary>
-    <secondary>functions and operators</secondary>
-   </indexterm>
-&common;
-  <para>
-   <xref linkend="textsearch-operators-table">,
-   <xref linkend="textsearch-functions-table"> and
-   <xref linkend="textsearch-functions-debug-table">
-   summarize the functions and operators that are provided
-   for full text searching.  See <xref linkend="textsearch"> for a detailed
-<!## PG>
-   explanation of <productname>PostgreSQL</productname>'s text search
-<!## end>
-<!## XC>
-   explanation of <productname>Postgres-XC</productname>'s text search
-<!## end>
-<!## XL>
-   explanation of <productname>Postgres-XL</productname>'s text search
-<!## end>
-   facility.
-  </para>
-
-    <table id="textsearch-operators-table">
-     <title>Text Search Operators</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Operator</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry> <literal>@@</literal> </entry>
-        <entry><type>tsvector</> matches <type>tsquery</> ?</entry>
-        <entry><literal>to_tsvector('fat cats ate rats') @@ to_tsquery('cat &amp; rat')</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>@@@</literal> </entry>
-        <entry>deprecated synonym for <literal>@@</></entry>
-        <entry><literal>to_tsvector('fat cats ate rats') @@@ to_tsquery('cat &amp; rat')</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>||</literal> </entry>
-        <entry>concatenate <type>tsvector</>s</entry>
-        <entry><literal>'a:1 b:2'::tsvector || 'c:1 d:2 b:3'::tsvector</literal></entry>
-        <entry><literal>'a':1 'b':2,5 'c':3 'd':4</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&amp;&amp;</literal> </entry>
-        <entry>AND <type>tsquery</>s together</entry>
-        <entry><literal>'fat | rat'::tsquery &amp;&amp; 'cat'::tsquery</literal></entry>
-        <entry><literal>( 'fat' | 'rat' ) &amp; 'cat'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>||</literal> </entry>
-        <entry>OR <type>tsquery</>s together</entry>
-        <entry><literal>'fat | rat'::tsquery || 'cat'::tsquery</literal></entry>
-        <entry><literal>( 'fat' | 'rat' ) | 'cat'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>!!</literal> </entry>
-        <entry>negate a <type>tsquery</></entry>
-        <entry><literal>!! 'cat'::tsquery</literal></entry>
-        <entry><literal>!'cat'</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>@&gt;</literal> </entry>
-        <entry><type>tsquery</> contains another ?</entry>
-        <entry><literal>'cat'::tsquery @&gt; 'cat &amp; rat'::tsquery</literal></entry>
-        <entry><literal>f</literal></entry>
-       </row>
-       <row>
-        <entry> <literal>&lt;@</literal> </entry>
-        <entry><type>tsquery</> is contained in ?</entry>
-        <entry><literal>'cat'::tsquery &lt;@ 'cat &amp; rat'::tsquery</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-    <note>
-     <para>
-      The <type>tsquery</> containment operators consider only the lexemes
-      listed in the two queries, ignoring the combining operators.
-     </para>
-    </note>
-
-    <para>
-     In addition to the operators shown in the table, the ordinary B-tree
-     comparison operators (<literal>=</>, <literal>&lt;</>, etc) are defined
-     for types <type>tsvector</> and <type>tsquery</>.  These are not very
-     useful for text searching but allow, for example, unique indexes to be
-     built on columns of these types.
-    </para>
-
-    <table id="textsearch-functions-table">
-     <title>Text Search Functions</title>
-     <tgroup cols="5">
-      <thead>
-       <row>
-        <entry>Function</entry>
-        <entry>Return Type</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>get_current_ts_config</primary>
-         </indexterm>
-         <literal><function>get_current_ts_config()</function></literal>
-        </entry>
-        <entry><type>regconfig</type></entry>
-        <entry>get default text search configuration</entry>
-        <entry><literal>get_current_ts_config()</literal></entry>
-        <entry><literal>english</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>length</primary>
-         </indexterm>
-         <literal><function>length(<type>tsvector</>)</function></literal>
-        </entry>
-        <entry><type>integer</type></entry>
-        <entry>number of lexemes in <type>tsvector</></entry>
-        <entry><literal>length('fat:2,4 cat:3 rat:5A'::tsvector)</literal></entry>
-        <entry><literal>3</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>numnode</primary>
-         </indexterm>
-         <literal><function>numnode(<type>tsquery</>)</function></literal>
-        </entry>
-        <entry><type>integer</type></entry>
-        <entry>number of lexemes plus operators in <type>tsquery</></entry>
-        <entry><literal> numnode('(fat &amp; rat) | cat'::tsquery)</literal></entry>
-        <entry><literal>5</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>plainto_tsquery</primary>
-         </indexterm>
-         <literal><function>plainto_tsquery(<optional> <replaceable class="PARAMETER">config</> <type>regconfig</> , </optional> <replaceable class="PARAMETER">query</> <type>text</type>)</function></literal>
-        </entry>
-        <entry><type>tsquery</type></entry>
-        <entry>produce <type>tsquery</> ignoring punctuation</entry>
-        <entry><literal>plainto_tsquery('english', 'The Fat Rats')</literal></entry>
-        <entry><literal>'fat' &amp; 'rat'</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>querytree</primary>
-         </indexterm>
-         <literal><function>querytree(<replaceable class="PARAMETER">query</replaceable> <type>tsquery</>)</function></literal>
-        </entry>
-        <entry><type>text</type></entry>
-        <entry>get indexable part of a <type>tsquery</></entry>
-        <entry><literal>querytree('foo &amp; ! bar'::tsquery)</literal></entry>
-        <entry><literal>'foo'</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>setweight</primary>
-         </indexterm>
-         <literal><function>setweight(<type>tsvector</>, <type>"char"</>)</function></literal>
-        </entry>
-        <entry><type>tsvector</type></entry>
-        <entry>assign weight to each element of <type>tsvector</></entry>
-        <entry><literal>setweight('fat:2,4 cat:3 rat:5B'::tsvector, 'A')</literal></entry>
-        <entry><literal>'cat':3A 'fat':2A,4A 'rat':5A</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>strip</primary>
-         </indexterm>
-         <literal><function>strip(<type>tsvector</>)</function></literal>
-        </entry>
-        <entry><type>tsvector</type></entry>
-        <entry>remove positions and weights from <type>tsvector</></entry>
-        <entry><literal>strip('fat:2,4 cat:3 rat:5A'::tsvector)</literal></entry>
-        <entry><literal>'cat' 'fat' 'rat'</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>to_tsquery</primary>
-         </indexterm>
-         <literal><function>to_tsquery(<optional> <replaceable class="PARAMETER">config</> <type>regconfig</> , </optional> <replaceable class="PARAMETER">query</> <type>text</type>)</function></literal>
-        </entry>
-        <entry><type>tsquery</type></entry>
-        <entry>normalize words and convert to <type>tsquery</></entry>
-        <entry><literal>to_tsquery('english', 'The &amp; Fat &amp; Rats')</literal></entry>
-        <entry><literal>'fat' &amp; 'rat'</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>to_tsvector</primary>
-         </indexterm>
-         <literal><function>to_tsvector(<optional> <replaceable class="PARAMETER">config</> <type>regconfig</> , </optional> <replaceable class="PARAMETER">document</> <type>text</type>)</function></literal>
-        </entry>
-        <entry><type>tsvector</type></entry>
-        <entry>reduce document text to <type>tsvector</></entry>
-        <entry><literal>to_tsvector('english', 'The Fat Rats')</literal></entry>
-        <entry><literal>'fat':2 'rat':3</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>ts_headline</primary>
-         </indexterm>
-         <literal><function>ts_headline(<optional> <replaceable class="PARAMETER">config</replaceable> <type>regconfig</>, </optional> <replaceable class="PARAMETER">document</replaceable> <type>text</>, <replaceable class="PARAMETER">query</replaceable> <type>tsquery</> <optional>, <replaceable class="PARAMETER">options</replaceable> <type>text</> </optional>)</function></literal>
-        </entry>
-        <entry><type>text</type></entry>
-        <entry>display a query match</entry>
-        <entry><literal>ts_headline('x y z', 'z'::tsquery)</literal></entry>
-        <entry><literal>x y &lt;b&gt;z&lt;/b&gt;</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>ts_rank</primary>
-         </indexterm>
-         <literal><function>ts_rank(<optional> <replaceable class="PARAMETER">weights</replaceable> <type>float4[]</>, </optional> <replaceable class="PARAMETER">vector</replaceable> <type>tsvector</>, <replaceable class="PARAMETER">query</replaceable> <type>tsquery</> <optional>, <replaceable class="PARAMETER">normalization</replaceable> <type>integer</> </optional>)</function></literal>
-        </entry>
-        <entry><type>float4</type></entry>
-        <entry>rank document for query</entry>
-        <entry><literal>ts_rank(textsearch, query)</literal></entry>
-        <entry><literal>0.818</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>ts_rank_cd</primary>
-         </indexterm>
-         <literal><function>ts_rank_cd(<optional> <replaceable class="PARAMETER">weights</replaceable> <type>float4[]</>, </optional> <replaceable class="PARAMETER">vector</replaceable> <type>tsvector</>, <replaceable class="PARAMETER">query</replaceable> <type>tsquery</> <optional>, <replaceable class="PARAMETER">normalization</replaceable> <type>integer</> </optional>)</function></literal>
-        </entry>
-        <entry><type>float4</type></entry>
-        <entry>rank document for query using cover density</entry>
-        <entry><literal>ts_rank_cd('{0.1, 0.2, 0.4, 1.0}', textsearch, query)</literal></entry>
-        <entry><literal>2.01317</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>ts_rewrite</primary>
-         </indexterm>
-         <literal><function>ts_rewrite(<replaceable class="PARAMETER">query</replaceable> <type>tsquery</>, <replaceable class="PARAMETER">target</replaceable> <type>tsquery</>, <replaceable class="PARAMETER">substitute</replaceable> <type>tsquery</>)</function></literal>
-        </entry>
-        <entry><type>tsquery</type></entry>
-        <entry>replace target with substitute within query</entry>
-        <entry><literal>ts_rewrite('a &amp; b'::tsquery, 'a'::tsquery, 'foo|bar'::tsquery)</literal></entry>
-        <entry><literal>'b' &amp; ( 'foo' | 'bar' )</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>ts_rewrite(<replaceable class="PARAMETER">query</replaceable> <type>tsquery</>, <replaceable class="PARAMETER">select</replaceable> <type>text</>)</function></literal></entry>
-        <entry><type>tsquery</type></entry>
-        <entry>replace using targets and substitutes from a <command>SELECT</> command</entry>
-        <entry><literal>SELECT ts_rewrite('a &amp; b'::tsquery, 'SELECT t,s FROM aliases')</literal></entry>
-        <entry><literal>'b' &amp; ( 'foo' | 'bar' )</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>tsvector_update_trigger</primary>
-         </indexterm>
-         <literal><function>tsvector_update_trigger()</function></literal>
-        </entry>
-        <entry><type>trigger</type></entry>
-        <entry>trigger function for automatic <type>tsvector</> column update</entry>
-        <entry><literal>CREATE TRIGGER ... tsvector_update_trigger(tsvcol, 'pg_catalog.swedish', title, body)</literal></entry>
-        <entry><literal></literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>tsvector_update_trigger_column</primary>
-         </indexterm>
-         <literal><function>tsvector_update_trigger_column()</function></literal>
-        </entry>
-        <entry><type>trigger</type></entry>
-        <entry>trigger function for automatic <type>tsvector</> column update</entry>
-        <entry><literal>CREATE TRIGGER ... tsvector_update_trigger_column(tsvcol, configcol, title, body)</literal></entry>
-        <entry><literal></literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-  <note>
-   <para>
-    All the text search functions that accept an optional <type>regconfig</>
-    argument will use the configuration specified by
-    <xref linkend="guc-default-text-search-config">
-    when that argument is omitted.
-   </para>
-  </note>
-
-  <para>
-   The functions in
-   <xref linkend="textsearch-functions-debug-table">
-   are listed separately because they are not usually used in everyday text
-   searching operations.  They are helpful for development and debugging
-   of new text search configurations.
-  </para>
-
-    <table id="textsearch-functions-debug-table">
-     <title>Text Search Debugging Functions</title>
-     <tgroup cols="5">
-      <thead>
-       <row>
-        <entry>Function</entry>
-        <entry>Return Type</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>ts_debug</primary>
-         </indexterm>
-         <literal><function>ts_debug(<optional> <replaceable class="PARAMETER">config</replaceable> <type>regconfig</>, </optional> <replaceable class="PARAMETER">document</replaceable> <type>text</>, OUT <replaceable class="PARAMETER">alias</> <type>text</>, OUT <replaceable class="PARAMETER">description</> <type>text</>, OUT <replaceable class="PARAMETER">token</> <type>text</>, OUT <replaceable class="PARAMETER">dictionaries</> <type>regdictionary[]</>, OUT <replaceable class="PARAMETER">dictionary</> <type>regdictionary</>, OUT <replaceable class="PARAMETER">lexemes</> <type>text[]</>)</function></literal>
-        </entry>
-        <entry><type>setof record</type></entry>
-        <entry>test a configuration</entry>
-        <entry><literal>ts_debug('english', 'The Brightest supernovaes')</literal></entry>
-        <entry><literal>(asciiword,"Word, all ASCII",The,{english_stem},english_stem,{}) ...</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>ts_lexize</primary>
-         </indexterm>
-         <literal><function>ts_lexize(<replaceable class="PARAMETER">dict</replaceable> <type>regdictionary</>, <replaceable class="PARAMETER">token</replaceable> <type>text</>)</function></literal>
-        </entry>
-        <entry><type>text[]</type></entry>
-        <entry>test a dictionary</entry>
-        <entry><literal>ts_lexize('english_stem', 'stars')</literal></entry>
-        <entry><literal>{star}</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>ts_parse</primary>
-         </indexterm>
-         <literal><function>ts_parse(<replaceable class="PARAMETER">parser_name</replaceable> <type>text</>, <replaceable class="PARAMETER">document</replaceable> <type>text</>, OUT <replaceable class="PARAMETER">tokid</> <type>integer</>, OUT <replaceable class="PARAMETER">token</> <type>text</>)</function></literal>
-        </entry>
-        <entry><type>setof record</type></entry>
-        <entry>test a parser</entry>
-        <entry><literal>ts_parse('default', 'foo - bar')</literal></entry>
-        <entry><literal>(1,foo) ...</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>ts_parse(<replaceable class="PARAMETER">parser_oid</replaceable> <type>oid</>, <replaceable class="PARAMETER">document</replaceable> <type>text</>, OUT <replaceable class="PARAMETER">tokid</> <type>integer</>, OUT <replaceable class="PARAMETER">token</> <type>text</>)</function></literal></entry>
-        <entry><type>setof record</type></entry>
-        <entry>test a parser</entry>
-        <entry><literal>ts_parse(3722, 'foo - bar')</literal></entry>
-        <entry><literal>(1,foo) ...</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>ts_token_type</primary>
-         </indexterm>
-         <literal><function>ts_token_type(<replaceable class="PARAMETER">parser_name</> <type>text</>, OUT <replaceable class="PARAMETER">tokid</> <type>integer</>, OUT <replaceable class="PARAMETER">alias</> <type>text</>, OUT <replaceable class="PARAMETER">description</> <type>text</>)</function></literal>
-        </entry>
-        <entry><type>setof record</type></entry>
-        <entry>get token types defined by parser</entry>
-        <entry><literal>ts_token_type('default')</literal></entry>
-        <entry><literal>(1,asciiword,"Word, all ASCII") ...</literal></entry>
-       </row>
-       <row>
-        <entry><literal><function>ts_token_type(<replaceable class="PARAMETER">parser_oid</> <type>oid</>, OUT <replaceable class="PARAMETER">tokid</> <type>integer</>, OUT <replaceable class="PARAMETER">alias</> <type>text</>, OUT <replaceable class="PARAMETER">description</> <type>text</>)</function></literal></entry>
-        <entry><type>setof record</type></entry>
-        <entry>get token types defined by parser</entry>
-        <entry><literal>ts_token_type(3722)</literal></entry>
-        <entry><literal>(1,asciiword,"Word, all ASCII") ...</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <indexterm>
-          <primary>ts_stat</primary>
-         </indexterm>
-         <literal><function>ts_stat(<replaceable class="PARAMETER">sqlquery</replaceable> <type>text</>, <optional> <replaceable class="PARAMETER">weights</replaceable> <type>text</>, </optional> OUT <replaceable class="PARAMETER">word</replaceable> <type>text</>, OUT <replaceable class="PARAMETER">ndoc</replaceable> <type>integer</>, OUT <replaceable class="PARAMETER">nentry</replaceable> <type>integer</>)</function></literal>
-        </entry>
-        <entry><type>setof record</type></entry>
-        <entry>get statistics of a <type>tsvector</> column</entry>
-        <entry><literal>ts_stat('SELECT vector from apod')</literal></entry>
-        <entry><literal>(foo,10,15) ...</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
- </sect1>
-
-
- <sect1 id="functions-xml">
-  <title>XML Functions</title>
-&common;
-  <para>
-   The functions and function-like expressions described in this
-   section operate on values of type <type>xml</type>.  Check <xref
-   linkend="datatype-xml"> for information about the <type>xml</type>
-   type.  The function-like expressions <function>xmlparse</function>
-   and <function>xmlserialize</function> for converting to and from
-   type <type>xml</type> are not repeated here.  Use of most of these
-   functions requires the installation to have been built
-   with <command>configure --with-libxml</>.
-  </para>
-
-  <sect2 id="functions-producing-xml">
-   <title>Producing XML Content</title>
-&common;
-   <para>
-    A set of functions and function-like expressions are available for
-    producing XML content from SQL data.  As such, they are
-    particularly suitable for formatting query results into XML
-    documents for processing in client applications.
-   </para>
-
-   <sect3>
-    <title><literal>xmlcomment</literal></title>
-
-    <indexterm>
-     <primary>xmlcomment</primary>
-    </indexterm>
-
-<synopsis>
-<function>xmlcomment</function>(<replaceable>text</replaceable>)
-</synopsis>
-&common;
-    <para>
-     The function <function>xmlcomment</function> creates an XML value
-     containing an XML comment with the specified text as content.
-     The text cannot contain <quote><literal>--</literal></quote> or end with a
-     <quote><literal>-</literal></quote> so that the resulting construct is a valid
-     XML comment.  If the argument is null, the result is null.
-    </para>
-
-    <para>
-     Example:
-<screen><![CDATA[
-SELECT xmlcomment('hello');
-
-  xmlcomment
---------------
- <!--hello-->
-]]></screen>
-    </para>
-   </sect3>
-
-   <sect3>
-    <title><literal>xmlconcat</literal></title>
-
-    <indexterm>
-     <primary>xmlconcat</primary>
-    </indexterm>
-
-<synopsis>
-<function>xmlconcat</function>(<replaceable>xml</replaceable><optional>, ...</optional>)
-</synopsis>
-
-&common;
-    <para>
-     The function <function>xmlconcat</function> concatenates a list
-     of individual XML values to create a single value containing an
-     XML content fragment.  Null values are omitted; the result is
-     only null if there are no nonnull arguments.
-    </para>
-
-    <para>
-     Example:
-<screen><![CDATA[
-SELECT xmlconcat('<abc/>', '<bar>foo</bar>');
-
-      xmlconcat
-----------------------
- <abc/><bar>foo</bar>
-]]></screen>
-    </para>
-
-    <para>
-     XML declarations, if present, are combined as follows.  If all
-     argument values have the same XML version declaration, that
-     version is used in the result, else no version is used.  If all
-     argument values have the standalone declaration value
-     <quote>yes</quote>, then that value is used in the result.  If
-     all argument values have a standalone declaration value and at
-     least one is <quote>no</quote>, then that is used in the result.
-     Else the result will have no standalone declaration.  If the
-     result is determined to require a standalone declaration but no
-     version declaration, a version declaration with version 1.0 will
-     be used because XML requires an XML declaration to contain a
-     version declaration.  Encoding declarations are ignored and
-     removed in all cases.
-    </para>
-
-    <para>
-     Example:
-<screen><![CDATA[
-SELECT xmlconcat('<?xml version="1.1"?><foo/>', '<?xml version="1.1" standalone="no"?><bar/>');
-
-             xmlconcat
------------------------------------
- <?xml version="1.1"?><foo/><bar/>
-]]></screen>
-    </para>
-   </sect3>
-
-   <sect3>
-    <title><literal>xmlelement</literal></title>
-
-   <indexterm>
-    <primary>xmlelement</primary>
-   </indexterm>
-
-<synopsis>
-<function>xmlelement</function>(name <replaceable>name</replaceable> <optional>, xmlattributes(<replaceable>value</replaceable> <optional>AS <replaceable>attname</replaceable></optional> <optional>, ... </optional>)</optional> <optional><replaceable>, content, ...</replaceable></optional>)
-</synopsis>
-
-&common;
-    <para>
-     The <function>xmlelement</function> expression produces an XML
-     element with the given name, attributes, and content.
-    </para>
-
-    <para>
-     Examples:
-<screen><![CDATA[
-SELECT xmlelement(name foo);
-
- xmlelement
-------------
- <foo/>
-
-SELECT xmlelement(name foo, xmlattributes('xyz' as bar));
-
-    xmlelement
-------------------
- <foo bar="xyz"/>
-
-SELECT xmlelement(name foo, xmlattributes(current_date as bar), 'cont', 'ent');
-
-             xmlelement
--------------------------------------
- <foo bar="2007-01-26">content</foo>
-]]></screen>
-    </para>
-
-    <para>
-     Element and attribute names that are not valid XML names are
-     escaped by replacing the offending characters by the sequence
-     <literal>_x<replaceable>HHHH</replaceable>_</literal>, where
-     <replaceable>HHHH</replaceable> is the character's Unicode
-     codepoint in hexadecimal notation.  For example:
-<screen><![CDATA[
-SELECT xmlelement(name "foo$bar", xmlattributes('xyz' as "a&b"));
-
-            xmlelement
-----------------------------------
- <foo_x0024_bar a_x0026_b="xyz"/>
-]]></screen>
-    </para>
-
-    <para>
-     An explicit attribute name need not be specified if the attribute
-     value is a column reference, in which case the column's name will
-     be used as the attribute name by default.  In other cases, the
-     attribute must be given an explicit name.  So this example is
-     valid:
-<screen>
-CREATE TABLE test (a xml, b xml);
-SELECT xmlelement(name test, xmlattributes(a, b)) FROM test;
-</screen>
-     But these are not:
-<screen>
-SELECT xmlelement(name test, xmlattributes('constant'), a, b) FROM test;
-SELECT xmlelement(name test, xmlattributes(func(a, b))) FROM test;
-</screen>
-    </para>
-
-    <para>
-     Element content, if specified, will be formatted according to
-     its data type.  If the content is itself of type <type>xml</type>,
-     complex XML documents can be constructed.  For example:
-<screen><![CDATA[
-SELECT xmlelement(name foo, xmlattributes('xyz' as bar),
-                            xmlelement(name abc),
-                            xmlcomment('test'),
-                            xmlelement(name xyz));
-
-                  xmlelement
-----------------------------------------------
- <foo bar="xyz"><abc/><!--test--><xyz/></foo>
-]]></screen>
-
-     Content of other types will be formatted into valid XML character
-     data.  This means in particular that the characters &lt;, &gt;,
-     and &amp; will be converted to entities.  Binary data (data type
-     <type>bytea</type>) will be represented in base64 or hex
-     encoding, depending on the setting of the configuration parameter
-     <xref linkend="guc-xmlbinary">.  The particular behavior for
-     individual data types is expected to evolve in order to align the
-<!## PG>
-     SQL and PostgreSQL data types with the XML Schema specification,
-<!## end>
-<!## XC>
-     SQL and Postgres-XC data types with the XML Schema specification,
-<!## end>
-<!## XL>
-     SQL and Postgres-XL data types with the XML Schema specification,
-<!## end>
-     at which point a more precise description will appear.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title><literal>xmlforest</literal></title>
-
-   <indexterm>
-    <primary>xmlforest</primary>
-   </indexterm>
-
-<synopsis>
-<function>xmlforest</function>(<replaceable>content</replaceable> <optional>AS <replaceable>name</replaceable></optional> <optional>, ...</optional>)
-</synopsis>
-
-&common;
-    <para>
-     The <function>xmlforest</function> expression produces an XML
-     forest (sequence) of elements using the given names and content.
-    </para>
-
-    <para>
-     Examples:
-<screen><![CDATA[
-SELECT xmlforest('abc' AS foo, 123 AS bar);
-
-          xmlforest
-------------------------------
- <foo>abc</foo><bar>123</bar>
-
-
-SELECT xmlforest(table_name, column_name)
-FROM information_schema.columns
-WHERE table_schema = 'pg_catalog';
-
-                                         xmlforest
--------------------------------------------------------------------------------------------
- <table_name>pg_authid</table_name><column_name>rolname</column_name>
- <table_name>pg_authid</table_name><column_name>rolsuper</column_name>
- ...
-]]></screen>
-
-     As seen in the second example, the element name can be omitted if
-     the content value is a column reference, in which case the column
-     name is used by default.  Otherwise, a name must be specified.
-    </para>
-
-    <para>
-     Element names that are not valid XML names are escaped as shown
-     for <function>xmlelement</function> above.  Similarly, content
-     data is escaped to make valid XML content, unless it is already
-     of type <type>xml</type>.
-    </para>
-
-    <para>
-     Note that XML forests are not valid XML documents if they consist
-     of more than one element, so it might be useful to wrap
-     <function>xmlforest</function> expressions in
-     <function>xmlelement</function>.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title><literal>xmlpi</literal></title>
-
-   <indexterm>
-    <primary>xmlpi</primary>
-   </indexterm>
-
-<synopsis>
-<function>xmlpi</function>(name <replaceable>target</replaceable> <optional>, <replaceable>content</replaceable></optional>)
-</synopsis>
-
-&common;
-    <para>
-     The <function>xmlpi</function> expression creates an XML
-     processing instruction.  The content, if present, must not
-     contain the character sequence <literal>?&gt;</literal>.
-    </para>
-
-    <para>
-     Example:
-<screen><![CDATA[
-SELECT xmlpi(name php, 'echo "hello world";');
-
-            xmlpi
------------------------------
- <?php echo "hello world";?>
-]]></screen>
-    </para>
-   </sect3>
-
-   <sect3>
-    <title><literal>xmlroot</literal></title>
-
-   <indexterm>
-    <primary>xmlroot</primary>
-   </indexterm>
-
-<synopsis>
-<function>xmlroot</function>(<replaceable>xml</replaceable>, version <replaceable>text</replaceable> | no value <optional>, standalone yes|no|no value</optional>)
-</synopsis>
-
-&common;
-    <para>
-     The <function>xmlroot</function> expression alters the properties
-     of the root node of an XML value.  If a version is specified,
-     it replaces the value in the root node's version declaration; if a
-     standalone setting is specified, it replaces the value in the
-     root node's standalone declaration.
-    </para>
-
-    <para>
-<screen><![CDATA[
-SELECT xmlroot(xmlparse(document '<?xml version="1.1"?><content>abc</content>'),
-               version '1.0', standalone yes);
-
-                xmlroot
-----------------------------------------
- <?xml version="1.0" standalone="yes"?>
- <content>abc</content>
-]]></screen>
-    </para>
-   </sect3>
-
-   <sect3 id="functions-xml-xmlagg">
-    <title><literal>xmlagg</literal></title>
-
-    <indexterm>
-     <primary>xmlagg</primary>
-    </indexterm>
-
-<synopsis>
-<function>xmlagg</function>(<replaceable>xml</replaceable>)
-</synopsis>
-&common;
-    <para>
-     The function <function>xmlagg</function> is, unlike the other
-     functions described here, an aggregate function.  It concatenates the
-     input values to the aggregate function call,
-     much like <function>xmlconcat</function> does, except that concatenation
-     occurs across rows rather than across expressions in a single row.
-     See <xref linkend="functions-aggregate"> for additional information
-     about aggregate functions.
-    </para>
-
-    <para>
-     Example:
-<screen><![CDATA[
-CREATE TABLE test (y int, x xml);
-INSERT INTO test VALUES (1, '<foo>abc</foo>');
-INSERT INTO test VALUES (2, '<bar/>');
-SELECT xmlagg(x) FROM test;
-        xmlagg
-----------------------
- <foo>abc</foo><bar/>
-]]></screen>
-    </para>
-
-    <para>
-     To determine the order of the concatenation, an <literal>ORDER BY</>
-     clause may be added to the aggregate call as described in
-     <xref linkend="syntax-aggregates">. For example:
-
-<screen><![CDATA[
-SELECT xmlagg(x ORDER BY y DESC) FROM test;
-        xmlagg
-----------------------
- <bar/><foo>abc</foo>
-]]></screen>
-    </para>
-
-    <para>
-     The following non-standard approach used to be recommended
-     in previous versions, and may still be useful in specific
-     cases:
-
-<screen><![CDATA[
-SELECT xmlagg(x) FROM (SELECT * FROM test ORDER BY y DESC) AS tab;
-        xmlagg
-----------------------
- <bar/><foo>abc</foo>
-]]></screen>
-    </para>
-   </sect3>
-   </sect2>
-
-   <sect2 id="functions-xml-predicates">
-    <title>XML Predicates</title>
-
-    <para>
-     The expressions described in this section check properties
-     of <type>xml</type> values.
-    </para>
-
-   <sect3>
-    <title><literal>IS DOCUMENT</literal></title>
-
-    <indexterm>
-     <primary>IS DOCUMENT</primary>
-    </indexterm>
-
-<synopsis>
-<replaceable>xml</replaceable> IS DOCUMENT
-</synopsis>
-&common;
-    <para>
-     The expression <literal>IS DOCUMENT</literal> returns true if the
-     argument XML value is a proper XML document, false if it is not
-     (that is, it is a content fragment), or null if the argument is
-     null.  See <xref linkend="datatype-xml"> about the difference
-     between documents and content fragments.
-    </para>
-   </sect3>
-
-   <sect3 id="xml-exists">
-    <title><literal>XMLEXISTS</literal></title>
-
-    <indexterm>
-     <primary>XMLEXISTS</primary>
-    </indexterm>
-
-<synopsis>
-<function>XMLEXISTS</function>(<replaceable>text</replaceable> PASSING <optional>BY REF</optional> <replaceable>xml</replaceable> <optional>BY REF</optional>)
-</synopsis>
-
-    <para>
-     The function <function>xmlexists</function> returns true if the
-     XPath expression in the first argument returns any nodes, and
-     false otherwise.  (If either argument is null, the result is
-     null.)
-    </para>
-
-    <para>
-     Example:
-     <screen><![CDATA[
-SELECT xmlexists('//town[text() = ''Toronto'']' PASSING BY REF '<towns><town>Toronto</town><town>Ottawa</town></towns>');
-
- xmlexists
-------------
- t
-(1 row)
-]]></screen>
-    </para>
-
-    <para>
-     The <literal>BY REF</literal> clauses have no effect in
-     PostgreSQL, but are allowed for SQL conformance and compatibility
-     with other implementations.  Per SQL standard, the
-     first <literal>BY REF</literal> is required, the second is
-     optional.  Also note that the SQL standard specifies
-     the <function>xmlexists</function> construct to take an XQuery
-     expression as first argument, but PostgreSQL currently only
-     supports XPath, which is a subset of XQuery.
-    </para>
-   </sect3>
-
-   <sect3 id="xml-is-well-formed">
-    <title><literal>xml_is_well_formed</literal></title>
-
-    <indexterm>
-     <primary>xml_is_well_formed</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>xml_is_well_formed_document</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>xml_is_well_formed_content</primary>
-    </indexterm>
-
-<synopsis>
-<function>xml_is_well_formed</function>(<replaceable>text</replaceable>)
-<function>xml_is_well_formed_document</function>(<replaceable>text</replaceable>)
-<function>xml_is_well_formed_content</function>(<replaceable>text</replaceable>)
-</synopsis>
-
-    <para>
-     These functions check whether a <type>text</> string is well-formed XML,
-     returning a Boolean result.
-     <function>xml_is_well_formed_document</function> checks for a well-formed
-     document, while <function>xml_is_well_formed_content</function> checks
-     for well-formed content.  <function>xml_is_well_formed</function> does
-     the former if the <xref linkend="guc-xmloption"> configuration
-     parameter is set to <literal>DOCUMENT</>, or the latter if it is set to
-     <literal>CONTENT</>.  This means that
-     <function>xml_is_well_formed</function> is useful for seeing whether
-     a simple cast to type <type>xml</> will succeed, whereas the other two
-     functions are useful for seeing whether the corresponding variants of
-     <function>XMLPARSE</> will succeed.
-    </para>
-
-    <para>
-     Examples:
-
-<screen><![CDATA[
-SET xmloption TO DOCUMENT;
-SELECT xml_is_well_formed('<>');
- xml_is_well_formed 
---------------------
- f
-(1 row)
-
-SELECT xml_is_well_formed('<abc/>');
- xml_is_well_formed 
---------------------
- t
-(1 row)
-
-SET xmloption TO CONTENT;
-SELECT xml_is_well_formed('abc');
- xml_is_well_formed 
---------------------
- t
-(1 row)
-
-SELECT xml_is_well_formed_document('<pg:foo xmlns:pg="http://postgresql.org/stuff">bar</pg:foo>');
- xml_is_well_formed_document 
------------------------------
- t
-(1 row)
-
-SELECT xml_is_well_formed_document('<pg:foo xmlns:pg="http://postgresql.org/stuff">bar</my:foo>');
- xml_is_well_formed_document 
------------------------------
- f
-(1 row)
-]]></screen>
-
-     The last example shows that the checks include whether
-     namespaces are correctly matched.
-    </para>
-   </sect3>
-  </sect2>
-
-  <sect2 id="functions-xml-processing">
-   <title>Processing XML</title>
-
-   <indexterm>
-    <primary>XPath</primary>
-   </indexterm>
-
-&common;
-   <para>
-<!## PG>
-    To process values of data type <type>xml</type>, PostgreSQL offers
-<!## end>
-<!## XC>
-    To process values of data type <type>xml</type>, Postgres-XC offers
-<!## end>
-<!## XL>
-    To process values of data type <type>xml</type>, Postgres-XL offers
-<!## end>
-    the functions <function>xpath</function> and
-    <function>xpath_exists</function>, which evaluate XPath 1.0
-    expressions.
-   </para>
-
-<synopsis>
-<function>xpath</function>(<replaceable>xpath</replaceable>, <replaceable>xml</replaceable> <optional>, <replaceable>nsarray</replaceable></optional>)
-</synopsis>
-
-   <para>
-    The function <function>xpath</function> evaluates the XPath
-    expression <replaceable>xpath</replaceable> (a <type>text</> value)
-    against the XML value
-    <replaceable>xml</replaceable>.  It returns an array of XML values
-    corresponding to the node set produced by the XPath expression.
-   </para>
-
-  <para>
-    The second argument must be a well formed XML document. In particular,
-    it must have a single root node element.
-  </para>
-
-   <para>
-    The optional third argument of the function is an array of namespace
-    mappings.  This array should be a two-dimensional <type>text</> array with
-    the length of the second axis being equal to 2 (i.e., it should be an
-    array of arrays, each of which consists of exactly 2 elements).
-    The first element of each array entry is the namespace name (alias), the
-    second the namespace URI. It is not required that aliases provided in
-    this array be the same as those being used in the XML document itself (in
-    other words, both in the XML document and in the <function>xpath</function>
-    function context, aliases are <emphasis>local</>).
-   </para>
-
-   <para>
-    Example:
-<screen><![CDATA[
-SELECT xpath('/my:a/text()', '<my:a xmlns:my="http://example.com">test</my:a>',
-             ARRAY[ARRAY['my', 'http://example.com']]);
-
- xpath  
---------
- {test}
-(1 row)
-]]></screen>
-   </para>
-
-   <para>
-    To deal with default (anonymous) namespaces, do something like this:
-<screen><![CDATA[
-SELECT xpath('//mydefns:b/text()', '<a xmlns="http://example.com"><b>test</b></a>',
-             ARRAY[ARRAY['mydefns', 'http://example.com']]);
-
- xpath
---------
- {test}
-(1 row)
-]]></screen>
-   </para>
-
-   <indexterm>
-    <primary>xpath_exists</primary>
-   </indexterm>
-
-<synopsis>
-<function>xpath_exists</function>(<replaceable>xpath</replaceable>, <replaceable>xml</replaceable> <optional>, <replaceable>nsarray</replaceable></optional>)
-</synopsis>
-
-   <para>
-    The function <function>xpath_exists</function> is a specialized form
-    of the <function>xpath</function> function.  Instead of returning the
-    individual XML values that satisfy the XPath, this function returns a
-    Boolean indicating whether the query was satisfied or not.  This
-    function is equivalent to the standard <literal>XMLEXISTS</> predicate,
-    except that it also offers support for a namespace mapping argument.
-   </para>
-
-   <para>
-    Example:
-<screen><![CDATA[
-SELECT xpath_exists('/my:a/text()', '<my:a xmlns:my="http://example.com">test</my:a>',
-                     ARRAY[ARRAY['my', 'http://example.com']]);
-
- xpath_exists  
---------------
- t
-(1 row)
-]]></screen>
-   </para>
-  </sect2>
-
-  <sect2 id="functions-xml-mapping">
-   <title>Mapping Tables to XML</title>
-
-   <indexterm zone="functions-xml-mapping">
-    <primary>XML export</primary>
-   </indexterm>
-&common;
-   <para>
-    The following functions map the contents of relational tables to
-    XML values.  They can be thought of as XML export functionality:
-<synopsis>
-table_to_xml(tbl regclass, nulls boolean, tableforest boolean, targetns text)
-query_to_xml(query text, nulls boolean, tableforest boolean, targetns text)
-cursor_to_xml(cursor refcursor, count int, nulls boolean,
-              tableforest boolean, targetns text)
-</synopsis>
-    The return type of each function is <type>xml</type>.
-   </para>
-
-   <para>
-    <function>table_to_xml</function> maps the content of the named
-    table, passed as parameter <parameter>tbl</parameter>.  The
-    <type>regclass</type> type accepts strings identifying tables using the
-    usual notation, including optional schema qualifications and
-    double quotes.  <function>query_to_xml</function> executes the
-    query whose text is passed as parameter
-    <parameter>query</parameter> and maps the result set.
-    <function>cursor_to_xml</function> fetches the indicated number of
-    rows from the cursor specified by the parameter
-    <parameter>cursor</parameter>.  This variant is recommended if
-    large tables have to be mapped, because the result value is built
-    up in memory by each function.
-   </para>
-
-   <para>
-    If <parameter>tableforest</parameter> is false, then the resulting
-    XML document looks like this:
-<screen><![CDATA[
-<tablename>
-  <row>
-    <columnname1>data</columnname1>
-    <columnname2>data</columnname2>
-  </row>
-
-  <row>
-    ...
-  </row>
-
-  ...
-</tablename>
-]]></screen>
-
-    If <parameter>tableforest</parameter> is true, the result is an
-    XML content fragment that looks like this:
-<screen><![CDATA[
-<tablename>
-  <columnname1>data</columnname1>
-  <columnname2>data</columnname2>
-</tablename>
-
-<tablename>
-  ...
-</tablename>
-
-...
-]]></screen>
-
-    If no table name is available, that is, when mapping a query or a
-    cursor, the string <literal>table</literal> is used in the first
-    format, <literal>row</literal> in the second format.
-   </para>
-
-   <para>
-    The choice between these formats is up to the user.  The first
-    format is a proper XML document, which will be important in many
-    applications.  The second format tends to be more useful in the
-    <function>cursor_to_xml</function> function if the result values are to be
-    reassembled into one document later on.  The functions for
-    producing XML content discussed above, in particular
-    <function>xmlelement</function>, can be used to alter the results
-    to taste.
-   </para>
-
-   <para>
-    The data values are mapped in the same way as described for the
-    function <function>xmlelement</function> above.
-   </para>
-
-   <para>
-    The parameter <parameter>nulls</parameter> determines whether null
-    values should be included in the output.  If true, null values in
-    columns are represented as:
-<screen><![CDATA[
-<columnname xsi:nil="true"/>
-]]></screen>
-    where <literal>xsi</literal> is the XML namespace prefix for XML
-    Schema Instance.  An appropriate namespace declaration will be
-    added to the result value.  If false, columns containing null
-    values are simply omitted from the output.
-   </para>
-
-   <para>
-    The parameter <parameter>targetns</parameter> specifies the
-    desired XML namespace of the result.  If no particular namespace
-    is wanted, an empty string should be passed.
-   </para>
-
-   <para>
-    The following functions return XML Schema documents describing the
-    mappings performed by the corresponding functions above:
-<synopsis>
-table_to_xmlschema(tbl regclass, nulls boolean, tableforest boolean, targetns text)
-query_to_xmlschema(query text, nulls boolean, tableforest boolean, targetns text)
-cursor_to_xmlschema(cursor refcursor, nulls boolean, tableforest boolean, targetns text)
-</synopsis>
-    It is essential that the same parameters are passed in order to
-    obtain matching XML data mappings and XML Schema documents.
-   </para>
-
-   <para>
-    The following functions produce XML data mappings and the
-    corresponding XML Schema in one document (or forest), linked
-    together.  They can be useful where self-contained and
-    self-describing results are wanted:
-<synopsis>
-table_to_xml_and_xmlschema(tbl regclass, nulls boolean, tableforest boolean, targetns text)
-query_to_xml_and_xmlschema(query text, nulls boolean, tableforest boolean, targetns text)
-</synopsis>
-   </para>
-
-   <para>
-    In addition, the following functions are available to produce
-    analogous mappings of entire schemas or the entire current
-    database:
-<synopsis>
-schema_to_xml(schema name, nulls boolean, tableforest boolean, targetns text)
-schema_to_xmlschema(schema name, nulls boolean, tableforest boolean, targetns text)
-schema_to_xml_and_xmlschema(schema name, nulls boolean, tableforest boolean, targetns text)
-
-database_to_xml(nulls boolean, tableforest boolean, targetns text)
-database_to_xmlschema(nulls boolean, tableforest boolean, targetns text)
-database_to_xml_and_xmlschema(nulls boolean, tableforest boolean, targetns text)
-</synopsis>
-
-    Note that these potentially produce a lot of data, which needs to
-    be built up in memory.  When requesting content mappings of large
-    schemas or databases, it might be worthwhile to consider mapping the
-    tables separately instead, possibly even through a cursor.
-   </para>
-
-   <para>
-    The result of a schema content mapping looks like this:
-
-<screen><![CDATA[
-<schemaname>
-
-table1-mapping
-
-table2-mapping
-
-...
-
-</schemaname>]]></screen>
-
-    where the format of a table mapping depends on the
-    <parameter>tableforest</parameter> parameter as explained above.
-   </para>
-
-   <para>
-    The result of a database content mapping looks like this:
-
-<screen><![CDATA[
-<dbname>
-
-<schema1name>
-  ...
-</schema1name>
-
-<schema2name>
-  ...
-</schema2name>
-
-...
-
-</dbname>]]></screen>
-
-    where the schema mapping is as above.
-   </para>
-
-   <para>
-    As an example of using the output produced by these functions,
-    <xref linkend="xslt-xml-html"> shows an XSLT stylesheet that
-    converts the output of
-    <function>table_to_xml_and_xmlschema</function> to an HTML
-    document containing a tabular rendition of the table data.  In a
-    similar manner, the results from these functions can be
-    converted into other XML-based formats.
-   </para>
-
-   <figure id="xslt-xml-html">
-    <title>XSLT Stylesheet for Converting SQL/XML Output to HTML</title>
-<programlisting><![CDATA[
-<?xml version="1.0"?>
-<xsl:stylesheet version="1.0"
-    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-    xmlns="http://www.w3.org/1999/xhtml"
->
-
-  <xsl:output method="xml"
-      doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
-      doctype-public="-//W3C/DTD XHTML 1.0 Strict//EN"
-      indent="yes"/>
-
-  <xsl:template match="/*">
-    <xsl:variable name="schema" select="//xsd:schema"/>
-    <xsl:variable name="tabletypename"
-                  select="$schema/xsd:element[@name=name(current())]/@type"/>
-    <xsl:variable name="rowtypename"
-                  select="$schema/xsd:complexType[@name=$tabletypename]/xsd:sequence/xsd:element[@name='row']/@type"/>
-
-    <html>
-      <head>
-        <title><xsl:value-of select="name(current())"/></title>
-      </head>
-      <body>
-        <table>
-          <tr>
-            <xsl:for-each select="$schema/xsd:complexType[@name=$rowtypename]/xsd:sequence/xsd:element/@name">
-              <th><xsl:value-of select="."/></th>
-            </xsl:for-each>
-          </tr>
-
-          <xsl:for-each select="row">
-            <tr>
-              <xsl:for-each select="*">
-                <td><xsl:value-of select="."/></td>
-              </xsl:for-each>
-            </tr>
-          </xsl:for-each>
-        </table>
-      </body>
-    </html>
-  </xsl:template>
-
-</xsl:stylesheet>
-]]></programlisting>
-   </figure>
-  </sect2>
- </sect1>
-
-
- <sect1 id="functions-sequence">
-  <title>Sequence Manipulation Functions</title>
-
-  <indexterm>
-   <primary>sequence</primary>
-  </indexterm>
-  <indexterm>
-   <primary>nextval</primary>
-  </indexterm>
-  <indexterm>
-   <primary>currval</primary>
-  </indexterm>
-  <indexterm>
-   <primary>lastval</primary>
-  </indexterm>
-  <indexterm>
-   <primary>setval</primary>
-  </indexterm>
-&common;
-  <para>
-<!## PG>
-   This section describes <productname>PostgreSQL</productname>'s
-<!## end>
-<!## XC>
-   This section describes <productname>Postgres-XC</productname>'s
-<!## end>
-<!## XL>
-   This section describes <productname>Postgres-XL</productname>'s
-<!## end>
-   functions for operating on <firstterm>sequence objects</firstterm>.
-   Sequence objects (also called sequence generators or just
-   sequences) are special single-row tables created with <xref
-   linkend="sql-createsequence">.
-   A sequence object is usually used to generate unique identifiers
-   for rows of a table.  The sequence functions, listed in <xref
-   linkend="functions-sequence-table">, provide simple, multiuser-safe
-   methods for obtaining successive sequence values from sequence
-   objects.
-  </para>
-
-   <table id="functions-sequence-table">
-    <title>Sequence Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Function</entry> <entry>Return Type</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-      <row>
-        <entry><literal><function>currval(<type>regclass</type>)</function></literal></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Return value most recently obtained with
-        <function>nextval</function> for specified sequence</entry>
-      </row>
-      <row>
-        <entry><literal><function>lastval()</function></literal></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Return value most recently obtained with
-        <function>nextval</function> for any sequence</entry>
-      </row>
-      <row>
-        <entry><literal><function>nextval(<type>regclass</type>)</function></literal></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Advance sequence and return new value</entry>
-      </row>
-      <row>
-        <entry><literal><function>setval(<type>regclass</type>, <type>bigint</type>)</function></literal></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Set sequence's current value</entry>
-      </row>
-      <row>
-        <entry><literal><function>setval(<type>regclass</type>, <type>bigint</type>, <type>boolean</type>)</function></literal></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Set sequence's current value and <literal>is_called</literal> flag</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   The sequence to be operated on by a sequence function is specified by
-   a <type>regclass</> argument, which is simply the OID of the sequence in the
-   <structname>pg_class</> system catalog.  You do not have to look up the
-   OID by hand, however, since the <type>regclass</> data type's input
-   converter will do the work for you.  Just write the sequence name enclosed
-   in single quotes so that it looks like a literal constant.  For
-   compatibility with the handling of ordinary
-   <acronym>SQL</acronym> names, the string will be converted to lower case
-   unless it contains double quotes around the sequence name.  Thus:
-<programlisting>
-nextval('foo')      <lineannotation>operates on sequence <literal>foo</literal></>
-nextval('FOO')      <lineannotation>operates on sequence <literal>foo</literal></>
-nextval('"Foo"')    <lineannotation>operates on sequence <literal>Foo</literal></>
-</programlisting>
-   The sequence name can be schema-qualified if necessary:
-<programlisting>
-nextval('myschema.foo')     <lineannotation>operates on <literal>myschema.foo</literal></>
-nextval('"myschema".foo')   <lineannotation>same as above</lineannotation>
-nextval('foo')              <lineannotation>searches search path for <literal>foo</literal></>
-</programlisting>
-   See <xref linkend="datatype-oid"> for more information about
-   <type>regclass</>.
-  </para>
-
-  <note>
-   <para>
-    Before <productname>PostgreSQL</productname> 8.1, the arguments of the
-    sequence functions were of type <type>text</>, not <type>regclass</>, and
-    the above-described conversion from a text string to an OID value would
-    happen at run time during each call.  For backward compatibility, this
-    facility still exists, but internally it is now handled as an implicit
-    coercion from <type>text</> to <type>regclass</> before the function is
-    invoked.
-   </para>
-
-   <para>
-    When you write the argument of a sequence function as an unadorned
-    literal string, it becomes a constant of type <type>regclass</>.
-    Since this is really just an OID, it will track the originally
-    identified sequence despite later renaming, schema reassignment,
-    etc.  This <quote>early binding</> behavior is usually desirable for
-    sequence references in column defaults and views.  But sometimes you might
-    want <quote>late binding</> where the sequence reference is resolved
-    at run time.  To get late-binding behavior, force the constant to be
-    stored as a <type>text</> constant instead of <type>regclass</>:
-<programlisting>
-nextval('foo'::text)      <lineannotation><literal>foo</literal> is looked up at runtime</>
-</programlisting>
-    Note that late binding was the only behavior supported in
-    <productname>PostgreSQL</productname> releases before 8.1, so you
-    might need to do this to preserve the semantics of old applications.
-   </para>
-
-   <para>
-    Of course, the argument of a sequence function can be an expression
-    as well as a constant.  If it is a text expression then the implicit
-    coercion will result in a run-time lookup.
-   </para>
-  </note>
-
-  <para>
-   The available sequence functions are:
-
-    <variablelist>
-     <varlistentry>
-      <term><function>nextval</function></term>
-      <listitem>
-       <para>
-        Advance the sequence object to its next value and return that
-        value.  This is done atomically: even if multiple sessions
-        execute <function>nextval</function> concurrently, each will safely receive
-        a distinct sequence value.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>currval</function></term>
-      <listitem>
-       <para>
-        Return the value most recently obtained by <function>nextval</function>
-        for this sequence in the current session.  (An error is
-        reported if <function>nextval</function> has never been called for this
-        sequence in this session.)  Because this is returning
-        a session-local value, it gives a predictable answer whether or not
-        other sessions have executed <function>nextval</function> since the
-        current session did.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>lastval</function></term>
-      <listitem>
-       <para>
-        Return the value most recently returned by
-        <function>nextval</> in the current session. This function is
-        identical to <function>currval</function>, except that instead
-        of taking the sequence name as an argument it fetches the
-        value of the last sequence used by <function>nextval</function>
-        in the current session. It is an error to call
-        <function>lastval</function> if <function>nextval</function>
-        has not yet been called in the current session.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>setval</function></term>
-      <listitem>
-       <para>
-        Reset the sequence object's counter value.  The two-parameter
-        form sets the sequence's <literal>last_value</literal> field to the
-        specified value and sets its <literal>is_called</literal> field to
-        <literal>true</literal>, meaning that the next
-        <function>nextval</function> will advance the sequence before
-        returning a value.  The value reported by <function>currval</> is
-        also set to the specified value.  In the three-parameter form,
-        <literal>is_called</literal> can be set to either <literal>true</literal>
-        or <literal>false</literal>.  <literal>true</> has the same effect as
-        the two-parameter form. If it is set to <literal>false</literal>, the
-        next <function>nextval</function> will return exactly the specified
-        value, and sequence advancement commences with the following
-        <function>nextval</function>.  Furthermore, the value reported by
-        <function>currval</> is not changed in this case (this is a change
-        from pre-8.3 behavior).  For example,
-
-<screen>
-SELECT setval('foo', 42);           <lineannotation>Next <function>nextval</> will return 43</lineannotation>
-SELECT setval('foo', 42, true);     <lineannotation>Same as above</lineannotation>
-SELECT setval('foo', 42, false);    <lineannotation>Next <function>nextval</> will return 42</lineannotation>
-</screen>
-
-        The result returned by <function>setval</function> is just the value of its
-        second argument.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-  </para>
-
-  <para>
-   If a sequence object has been created with default parameters,
-   successive <function>nextval</function> calls will return successive values
-   beginning with 1.  Other behaviors can be obtained by using
-   special parameters in the <xref linkend="sql-createsequence"> command;
-   see its command reference page for more information.
-  </para>
-
-  <important>
-   <para>
-    To avoid blocking concurrent transactions that obtain numbers from the
-    same sequence, a <function>nextval</function> operation is never rolled back;
-    that is, once a value has been fetched it is considered used, even if the
-    transaction that did the <function>nextval</function> later aborts.  This means
-    that aborted transactions might leave unused <quote>holes</quote> in the
-    sequence of assigned values.  <function>setval</function> operations are never
-    rolled back, either.
-   </para>
-  </important>
-
- </sect1>
-
-
- <sect1 id="functions-conditional">
-  <title>Conditional Expressions</title>
-
-  <indexterm>
-   <primary>CASE</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>conditional expression</primary>
-  </indexterm>
-&common;
-  <para>
-   This section describes the <acronym>SQL</acronym>-compliant conditional expressions
-<!## PG>
-   available in <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-   available in <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-   available in <productname>Postgres-XL</productname>.
-<!## end>
-  </para>
-
-  <tip>
-   <para>
-    If your needs go beyond the capabilities of these conditional
-    expressions, you might want to consider writing a stored procedure
-    in a more expressive programming language.
-   </para>
-  </tip>
-
-  <sect2 id="functions-case">
-   <title><literal>CASE</></title>
-&common;
-  <para>
-   The <acronym>SQL</acronym> <token>CASE</token> expression is a
-   generic conditional expression, similar to if/else statements in
-   other programming languages:
-
-<synopsis>
-CASE WHEN <replaceable>condition</replaceable> THEN <replaceable>result</replaceable>
-     <optional>WHEN ...</optional>
-     <optional>ELSE <replaceable>result</replaceable></optional>
-END
-</synopsis>
-
-   <token>CASE</token> clauses can be used wherever
-   an expression is valid.  Each <replaceable>condition</replaceable> is an
-   expression that returns a <type>boolean</type> result.  If the condition's
-   result is true, the value of the <token>CASE</token> expression is the
-   <replaceable>result</replaceable> that follows the condition, and the
-   remainder of the <token>CASE</token> expression is not processed.  If the
-   condition's result is not true, any subsequent <token>WHEN</token> clauses
-   are examined in the same manner.  If no <token>WHEN</token>
-   <replaceable>condition</replaceable> yields true, the value of the
-   <token>CASE</> expression is the <replaceable>result</replaceable> of the
-   <token>ELSE</token> clause.  If the <token>ELSE</token> clause is
-   omitted and no condition is true, the result is null.
-  </para>
-
-   <para>
-    An example:
-<screen>
-SELECT * FROM test;
-
- a
----
- 1
- 2
- 3
-
-
-SELECT a,
-       CASE WHEN a=1 THEN 'one'
-            WHEN a=2 THEN 'two'
-            ELSE 'other'
-       END
-    FROM test;
-
- a | case
----+-------
- 1 | one
- 2 | two
- 3 | other
-</screen>
-   </para>
-
-  <para>
-   The data types of all the <replaceable>result</replaceable>
-   expressions must be convertible to a single output type.
-   See <xref linkend="typeconv-union-case"> for more details.
-  </para>
-
-  <para>
-   There is a <quote>simple</> form of <token>CASE</token> expression
-   that is a variant of the general form above:
-
-<synopsis>
-CASE <replaceable>expression</replaceable>
-    WHEN <replaceable>value</replaceable> THEN <replaceable>result</replaceable>
-    <optional>WHEN ...</optional>
-    <optional>ELSE <replaceable>result</replaceable></optional>
-END
-</synopsis>
-
-   The first
-   <replaceable>expression</replaceable> is computed, then compared to
-   each of the <replaceable>value</replaceable> expressions in the
-   <token>WHEN</token> clauses until one is found that is equal to it.  If
-   no match is found, the <replaceable>result</replaceable> of the
-   <token>ELSE</token> clause (or a null value) is returned.  This is similar
-   to the <function>switch</function> statement in C.
-  </para>
-
-   <para>
-    The example above can be written using the simple
-    <token>CASE</token> syntax:
-<screen>
-SELECT a,
-       CASE a WHEN 1 THEN 'one'
-              WHEN 2 THEN 'two'
-              ELSE 'other'
-       END
-    FROM test;
-
- a | case
----+-------
- 1 | one
- 2 | two
- 3 | other
-</screen>
-   </para>
-
-   <para>
-    A <token>CASE</token> expression does not evaluate any subexpressions
-    that are not needed to determine the result.  For example, this is a
-    possible way of avoiding a division-by-zero failure:
-<programlisting>
-SELECT ... WHERE CASE WHEN x &lt;&gt; 0 THEN y/x &gt; 1.5 ELSE false END;
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="functions-coalesce-nvl-ifnull">
-   <title><literal>COALESCE</></title>
-
-  <indexterm>
-   <primary>COALESCE</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>NVL</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>IFNULL</primary>
-  </indexterm>
-
-<synopsis>
-<function>COALESCE</function>(<replaceable>value</replaceable> <optional>, ...</optional>)
-</synopsis>
-&common;
-  <para>
-   The <function>COALESCE</function> function returns the first of its
-   arguments that is not null.  Null is returned only if all arguments
-   are null.  It is often used to substitute a default value for
-   null values when data is retrieved for display, for example:
-<programlisting>
-SELECT COALESCE(description, short_description, '(none)') ...
-</programlisting>
-  </para>
-
-   <para>
-    Like a <token>CASE</token> expression, <function>COALESCE</function> only
-    evaluates the arguments that are needed to determine the result;
-    that is, arguments to the right of the first non-null argument are
-    not evaluated.  This SQL-standard function provides capabilities similar
-    to <function>NVL</> and <function>IFNULL</>, which are used in some other
-    database systems.
-   </para>
-  </sect2>
-
-  <sect2 id="functions-nullif">
-   <title><literal>NULLIF</></title>
-
-  <indexterm>
-   <primary>NULLIF</primary>
-  </indexterm>
-
-<synopsis>
-<function>NULLIF</function>(<replaceable>value1</replaceable>, <replaceable>value2</replaceable>)
-</synopsis>
-&common;
-  <para>
-   The <function>NULLIF</function> function returns a null value if
-   <replaceable>value1</replaceable> equals <replaceable>value2</replaceable>;
-   otherwise it returns <replaceable>value1</replaceable>.
-   This can be used to perform the inverse operation of the
-   <function>COALESCE</function> example given above:
-<programlisting>
-SELECT NULLIF(value, '(none)') ...
-</programlisting>
-  </para>
-  <para>
-   In this example, if <literal>value</literal> is <literal>(none)</>,
-   null is returned, otherwise the value of <literal>value</literal>
-   is returned.
-  </para>
-
-  </sect2>
-
-  <sect2 id="functions-greatest-least">
-   <title><literal>GREATEST</literal> and <literal>LEAST</literal></title>
-
-  <indexterm>
-   <primary>GREATEST</primary>
-  </indexterm>
-  <indexterm>
-   <primary>LEAST</primary>
-  </indexterm>
-
-<synopsis>
-<function>GREATEST</function>(<replaceable>value</replaceable> <optional>, ...</optional>)
-</synopsis>
-<synopsis>
-<function>LEAST</function>(<replaceable>value</replaceable> <optional>, ...</optional>)
-</synopsis>
-&common;
-   <para>
-    The <function>GREATEST</> and <function>LEAST</> functions select the
-    largest or smallest value from a list of any number of expressions.
-    The expressions must all be convertible to a common data type, which
-    will be the type of the result
-    (see <xref linkend="typeconv-union-case"> for details).  NULL values
-    in the list are ignored.  The result will be NULL only if all the
-    expressions evaluate to NULL.
-   </para>
-
-   <para>
-    Note that <function>GREATEST</> and <function>LEAST</> are not in
-    the SQL standard, but are a common extension.  Some other databases
-    make them return NULL if any argument is NULL, rather than only when
-    all are NULL.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="functions-array">
-  <title>Array Functions and Operators</title>
-&common;
-  <para>
-   <xref linkend="array-operators-table"> shows the operators
-   available for array types.
-  </para>
-
-    <table id="array-operators-table">
-     <title>Array Operators</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>Operator</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry> <literal>=</literal> </entry>
-        <entry>equal</entry>
-        <entry><literal>ARRAY[1.1,2.1,3.1]::int[] = ARRAY[1,2,3]</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>&lt;&gt;</literal> </entry>
-        <entry>not equal</entry>
-        <entry><literal>ARRAY[1,2,3] &lt;&gt; ARRAY[1,2,4]</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>&lt;</literal> </entry>
-        <entry>less than</entry>
-        <entry><literal>ARRAY[1,2,3] &lt; ARRAY[1,2,4]</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>&gt;</literal> </entry>
-        <entry>greater than</entry>
-        <entry><literal>ARRAY[1,4,3] &gt; ARRAY[1,2,4]</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>&lt;=</literal> </entry>
-        <entry>less than or equal</entry>
-        <entry><literal>ARRAY[1,2,3] &lt;= ARRAY[1,2,3]</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>&gt;=</literal> </entry>
-        <entry>greater than or equal</entry>
-        <entry><literal>ARRAY[1,4,3] &gt;= ARRAY[1,4,3]</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>@&gt;</literal> </entry>
-        <entry>contains</entry>
-        <entry><literal>ARRAY[1,4,3] @&gt; ARRAY[3,1]</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>&lt;@</literal> </entry>
-        <entry>is contained by</entry>
-        <entry><literal>ARRAY[2,7] &lt;@ ARRAY[1,7,4,2,6]</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>&amp;&amp;</literal> </entry>
-        <entry>overlap (have elements in common)</entry>
-        <entry><literal>ARRAY[1,4,3] &amp;&amp; ARRAY[2,1]</literal></entry>
-        <entry><literal>t</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>||</literal> </entry>
-        <entry>array-to-array concatenation</entry>
-        <entry><literal>ARRAY[1,2,3] || ARRAY[4,5,6]</literal></entry>
-        <entry><literal>{1,2,3,4,5,6}</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>||</literal> </entry>
-        <entry>array-to-array concatenation</entry>
-        <entry><literal>ARRAY[1,2,3] || ARRAY[[4,5,6],[7,8,9]]</literal></entry>
-        <entry><literal>{{1,2,3},{4,5,6},{7,8,9}}</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>||</literal> </entry>
-        <entry>element-to-array concatenation</entry>
-        <entry><literal>3 || ARRAY[4,5,6]</literal></entry>
-        <entry><literal>{3,4,5,6}</literal></entry>
-       </row>
-
-       <row>
-        <entry> <literal>||</literal> </entry>
-        <entry>array-to-element concatenation</entry>
-        <entry><literal>ARRAY[4,5,6] || 7</literal></entry>
-        <entry><literal>{4,5,6,7}</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-  <para>
-   Array comparisons compare the array contents element-by-element,
-   using the default B-tree comparison function for the element data type.
-   In multidimensional arrays the elements are visited in row-major order
-   (last subscript varies most rapidly).
-   If the contents of two arrays are equal but the dimensionality is
-   different, the first difference in the dimensionality information
-   determines the sort order.  (This is a change from versions of
-   <productname>PostgreSQL</> prior to 8.2: older versions would claim
-   that two arrays with the same contents were equal, even if the
-   number of dimensions or subscript ranges were different.)
-  </para>
-
-  <para>
-   See <xref linkend="arrays"> for more details about array operator
-   behavior.
-  </para>
-
-  <para>
-   <xref linkend="array-functions-table"> shows the functions
-   available for use with array types. See <xref linkend="arrays">
-   for more information  and examples of the use of these functions.
-  </para>
-
-  <indexterm>
-    <primary>array_append</primary>
-  </indexterm>
-  <indexterm>
-    <primary>array_cat</primary>
-  </indexterm>
-  <indexterm>
-    <primary>array_ndims</primary>
-  </indexterm>
-  <indexterm>
-    <primary>array_dims</primary>
-  </indexterm>
-  <indexterm>
-    <primary>array_fill</primary>
-  </indexterm>
-  <indexterm>
-    <primary>array_length</primary>
-  </indexterm>
-  <indexterm>
-    <primary>array_lower</primary>
-  </indexterm>
-  <indexterm>
-    <primary>array_prepend</primary>
-  </indexterm>
-  <indexterm>
-    <primary>array_to_string</primary>
-  </indexterm>
- <indexterm>
-    <primary>array_upper</primary>
-  </indexterm>
-  <indexterm>
-    <primary>string_to_array</primary>
-  </indexterm>
-  <indexterm>
-    <primary>unnest</primary>
-  </indexterm>
-
-    <table id="array-functions-table">
-     <title>Array Functions</title>
-     <tgroup cols="5">
-      <thead>
-       <row>
-        <entry>Function</entry>
-        <entry>Return Type</entry>
-        <entry>Description</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>
-         <literal>
-          <function>array_append</function>(<type>anyarray</type>, <type>anyelement</type>)
-         </literal>
-        </entry>
-        <entry><type>anyarray</type></entry>
-        <entry>append an element to the end of an array</entry>
-        <entry><literal>array_append(ARRAY[1,2], 3)</literal></entry>
-        <entry><literal>{1,2,3}</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>array_cat</function>(<type>anyarray</type>, <type>anyarray</type>)
-         </literal>
-        </entry>
-        <entry><type>anyarray</type></entry>
-        <entry>concatenate two arrays</entry>
-        <entry><literal>array_cat(ARRAY[1,2,3], ARRAY[4,5])</literal></entry>
-        <entry><literal>{1,2,3,4,5}</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>array_ndims</function>(<type>anyarray</type>)
-         </literal>
-        </entry>
-        <entry><type>int</type></entry>
-        <entry>returns the number of dimensions of the array</entry>
-        <entry><literal>array_ndims(ARRAY[[1,2,3], [4,5,6]])</literal></entry>
-        <entry><literal>2</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>array_dims</function>(<type>anyarray</type>)
-         </literal>
-        </entry>
-        <entry><type>text</type></entry>
-        <entry>returns a text representation of array's dimensions</entry>
-        <entry><literal>array_dims(ARRAY[[1,2,3], [4,5,6]])</literal></entry>
-        <entry><literal>[1:2][1:3]</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>array_fill</function>(<type>anyelement</type>, <type>int[]</type>,
-          <optional>, <type>int[]</type></optional>)
-         </literal>
-        </entry>
-        <entry><type>anyarray</type></entry>
-        <entry>returns an array initialized with supplied value and
-         dimensions, optionally with lower bounds other than 1</entry>
-        <entry><literal>array_fill(7, ARRAY[3], ARRAY[2])</literal></entry>
-        <entry><literal>[2:4]={7,7,7}</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>array_length</function>(<type>anyarray</type>, <type>int</type>)
-         </literal>
-        </entry>
-        <entry><type>int</type></entry>
-        <entry>returns the length of the requested array dimension</entry>
-        <entry><literal>array_length(array[1,2,3], 1)</literal></entry>
-        <entry><literal>3</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>array_lower</function>(<type>anyarray</type>, <type>int</type>)
-         </literal>
-        </entry>
-        <entry><type>int</type></entry>
-        <entry>returns lower bound of the requested array dimension</entry>
-        <entry><literal>array_lower('[0:2]={1,2,3}'::int[], 1)</literal></entry>
-        <entry><literal>0</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>array_prepend</function>(<type>anyelement</type>, <type>anyarray</type>)
-         </literal>
-        </entry>
-        <entry><type>anyarray</type></entry>
-        <entry>append an element to the beginning of an array</entry>
-        <entry><literal>array_prepend(1, ARRAY[2,3])</literal></entry>
-        <entry><literal>{1,2,3}</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>array_to_string</function>(<type>anyarray</type>, <type>text</type> <optional>, <type>text</type></optional>)
-         </literal>
-        </entry>
-        <entry><type>text</type></entry>
-        <entry>concatenates array elements using supplied delimiter and
-         optional null string</entry>
-        <entry><literal>array_to_string(ARRAY[1, 2, 3, NULL, 5], ',', '*')</literal></entry>
-        <entry><literal>1,2,3,*,5</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>array_upper</function>(<type>anyarray</type>, <type>int</type>)
-         </literal>
-        </entry>
-        <entry><type>int</type></entry>
-        <entry>returns upper bound of the requested array dimension</entry>
-        <entry><literal>array_upper(ARRAY[1,8,3,7], 1)</literal></entry>
-        <entry><literal>4</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>string_to_array</function>(<type>text</type>, <type>text</type> <optional>, <type>text</type></optional>)
-         </literal>
-        </entry>
-        <entry><type>text[]</type></entry>
-        <entry>splits string into array elements using supplied delimiter and
-         optional null string</entry>
-        <entry><literal>string_to_array('xx~^~yy~^~zz', '~^~', 'yy')</literal></entry>
-        <entry><literal>{xx,NULL,zz}</literal></entry>
-       </row>
-       <row>
-        <entry>
-         <literal>
-          <function>unnest</function>(<type>anyarray</type>)
-         </literal>
-        </entry>
-        <entry><type>setof anyelement</type></entry>
-        <entry>expand an array to a set of rows</entry>
-        <entry><literal>unnest(ARRAY[1,2])</literal></entry>
-        <entry><literallayout class="monospaced">1
-2</literallayout>(2 rows)</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    In <function>string_to_array</function>, if the delimiter parameter is
-    NULL, each character in the input string will become a separate element in
-    the resulting array.  If the delimiter is an empty string, then the entire
-    input string is returned as a one-element array.  Otherwise the input
-    string is split at each occurrence of the delimiter string.
-   </para>
-
-   <para>
-    In <function>string_to_array</function>, if the null-string parameter
-    is omitted or NULL, none of the substrings of the input will be replaced
-    by NULL.
-    In <function>array_to_string</function>, if the null-string parameter
-    is omitted or NULL, any null elements in the array are simply skipped
-    and not represented in the output string.
-   </para>
-
-   <note>
-    <para>
-     There are two differences in the behavior of <function>string_to_array</>
-     from pre-9.1 versions of <productname>PostgreSQL</>.
-     First, it will return an empty (zero-element) array rather than NULL when
-     the input string is of zero length.  Second, if the delimiter string is
-     NULL, the function splits the input into individual characters, rather
-     than returning NULL as before.
-    </para>
-   </note>
-
-   <para>
-    See also <xref linkend="functions-aggregate"> about the aggregate
-    function <function>array_agg</function> for use with arrays.
-   </para>
-  </sect1>
-
- <sect1 id="functions-aggregate">
-  <title>Aggregate Functions</title>
-
-  <indexterm zone="functions-aggregate">
-   <primary>aggregate function</primary>
-   <secondary>built-in</secondary>
-  </indexterm>
-&common;
-  <para>
-   <firstterm>Aggregate functions</firstterm> compute a single result
-   from a set of input values.  The built-in aggregate functions
-   are listed in
-   <xref linkend="functions-aggregate-table"> and
-   <xref linkend="functions-aggregate-statistics-table">.
-   The special syntax considerations for aggregate
-   functions are explained in <xref linkend="syntax-aggregates">.
-   Consult <xref linkend="tutorial-agg"> for additional introductory
-   information.
-  </para>
-
-  <table id="functions-aggregate-table">
-   <title>General-Purpose Aggregate Functions</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Argument Type(s)</entry>
-      <entry>Return Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry>
-       <indexterm>
-        <primary>array_agg</primary>
-       </indexterm>
-       <function>array_agg(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       any
-      </entry>
-      <entry>
-       array of the argument type
-      </entry>
-      <entry>input values, including nulls, concatenated into an array</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>average</primary>
-       </indexterm>
-       <indexterm>
-        <primary>avg</primary>
-       </indexterm>
-       <function>avg(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>smallint</type>, <type>int</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, <type>numeric</type>, or <type>interval</type>
-      </entry>
-      <entry>
-       <type>numeric</type> for any integer-type argument,
-       <type>double precision</type> for a floating-point argument,
-       otherwise the same as the argument data type
-      </entry>
-      <entry>the average (arithmetic mean) of all input values</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>bit_and</primary>
-       </indexterm>
-       <function>bit_and(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>smallint</type>, <type>int</type>, <type>bigint</type>, or
-       <type>bit</type>
-      </entry>
-      <entry>
-        same as argument data type
-      </entry>
-      <entry>the bitwise AND of all non-null input values, or null if none</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>bit_or</primary>
-       </indexterm>
-       <function>bit_or(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>smallint</type>, <type>int</type>, <type>bigint</type>, or
-       <type>bit</type>
-      </entry>
-      <entry>
-        same as argument data type
-      </entry>
-      <entry>the bitwise OR of all non-null input values, or null if none</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>bool_and</primary>
-       </indexterm>
-       <function>bool_and(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>bool</type>
-      </entry>
-      <entry>
-       <type>bool</type>
-      </entry>
-      <entry>true if all input values are true, otherwise false</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>bool_or</primary>
-       </indexterm>
-       <function>bool_or(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>bool</type>
-      </entry>
-      <entry>
-       <type>bool</type>
-      </entry>
-      <entry>true if at least one input value is true, otherwise false</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>count</primary>
-       </indexterm>
-       <function>count(*)</function>
-      </entry>
-      <entry></entry>
-      <entry><type>bigint</type></entry>
-      <entry>number of input rows</entry>
-     </row>
-
-     <row>
-      <entry><function>count(<replaceable class="parameter">expression</replaceable>)</function></entry>
-      <entry>any</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       number of input rows for which the value of <replaceable
-       class="parameter">expression</replaceable> is not null
-      </entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>every</primary>
-       </indexterm>
-       <function>every(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>bool</type>
-      </entry>
-      <entry>
-       <type>bool</type>
-      </entry>
-      <entry>equivalent to <function>bool_and</function></entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>max</primary>
-       </indexterm>
-       <function>max(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>any array, numeric, string, or date/time type</entry>
-      <entry>same as argument type</entry>
-      <entry>
-       maximum value of <replaceable
-       class="parameter">expression</replaceable> across all input
-       values
-      </entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>min</primary>
-       </indexterm>
-       <function>min(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>any array, numeric, string, or date/time type</entry>
-      <entry>same as argument type</entry>
-      <entry>
-       minimum value of <replaceable
-       class="parameter">expression</replaceable> across all input
-       values
-      </entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>string_agg</primary>
-       </indexterm>
-       <function>
-         string_agg(<replaceable class="parameter">expression</replaceable>,
-                    <replaceable class="parameter">delimiter</replaceable>)
-       </function>
-      </entry>
-      <entry>
-       <type>text</type>, <type>text</type>
-      </entry>
-      <entry>
-       <type>text</type>
-      </entry>
-      <entry>input values concatenated into a string, separated by delimiter</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>sum</primary>
-       </indexterm>
-       <function>sum(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>smallint</type>, <type>int</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, <type>numeric</type>, or
-       <type>interval</type>
-      </entry>
-      <entry>
-       <type>bigint</type> for <type>smallint</type> or
-       <type>int</type> arguments, <type>numeric</type> for
-       <type>bigint</type> arguments, <type>double precision</type>
-       for floating-point arguments, otherwise the same as the
-       argument data type
-      </entry>
-      <entry>sum of <replaceable class="parameter">expression</replaceable> across all input values</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>xmlagg</primary>
-       </indexterm>
-       <function>xmlagg(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>xml</type>
-      </entry>
-      <entry>
-       <type>xml</type>
-      </entry>
-      <entry>concatenation of XML values (see also <xref linkend="functions-xml-xmlagg">)</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   It should be noted that except for <function>count</function>,
-   these functions return a null value when no rows are selected.  In
-   particular, <function>sum</function> of no rows returns null, not
-   zero as one might expect, and <function>array_agg</function>
-   returns null rather than an empty array when there are no input
-   rows.  The <function>coalesce</function> function can be used to
-   substitute zero or an empty array for null when necessary.
-  </para>
-
-  <note>
-    <indexterm>
-      <primary>ANY</primary>
-    </indexterm>
-    <indexterm>
-      <primary>SOME</primary>
-    </indexterm>
-    <para>
-      Boolean aggregates <function>bool_and</function> and
-      <function>bool_or</function> correspond to standard SQL aggregates
-      <function>every</function> and <function>any</function> or
-      <function>some</function>.
-      As for <function>any</function> and <function>some</function>,
-      it seems that there is an ambiguity built into the standard syntax:
-<programlisting>
-SELECT b1 = ANY((SELECT b2 FROM t2 ...)) FROM t1 ...;
-</programlisting>
-      Here <function>ANY</function> can be considered either as introducing
-      a subquery, or as being an aggregate function, if the subquery
-      returns one row with a Boolean value.
-      Thus the standard name cannot be given to these aggregates.
-    </para>
-  </note>
-
-  <note>
-   <para>
-    Users accustomed to working with other SQL database management
-    systems might be disappointed by the performance of the
-    <function>count</function> aggregate when it is applied to the
-    entire table. A query like:
-<programlisting>
-SELECT count(*) FROM sometable;
-</programlisting>
-<!## PG>
-    will be executed by <productname>PostgreSQL</productname> using a
-<!## end>
-<!## XC>
-    will be executed by <productname>Postgres-XC</productname> using a
-<!## end>
-<!## XL>
-    will be executed by <productname>Postgres-XL</productname> using a
-<!## end>
-    sequential scan of the entire table.
-   </para>
-  </note>
-
-  <para>
-   The aggregate functions <function>array_agg</function>,
-   <function>string_agg</function>,
-   and <function>xmlagg</function>, as well as similar user-defined
-   aggregate functions, produce meaningfully different result values
-   depending on the order of the input values.  This ordering is
-   unspecified by default, but can be controlled by writing an
-   <literal>ORDER BY</> clause within the aggregate call, as shown in
-   <xref linkend="syntax-aggregates">.
-   Alternatively, supplying the input values from a sorted subquery
-   will usually work.  For example:
-
-<screen><![CDATA[
-SELECT xmlagg(x) FROM (SELECT x FROM test ORDER BY y DESC) AS tab;
-]]></screen>
-
-   But this syntax is not allowed in the SQL standard, and is
-   not portable to other database systems.
-  </para>
-
-  <para>
-   <xref linkend="functions-aggregate-statistics-table"> shows
-   aggregate functions typically used in statistical analysis.
-   (These are separated out merely to avoid cluttering the listing
-   of more-commonly-used aggregates.)  Where the description mentions
-   <replaceable class="parameter">N</replaceable>, it means the
-   number of input rows for which all the input expressions are non-null.
-   In all cases, null is returned if the computation is meaningless,
-   for example when <replaceable class="parameter">N</replaceable> is zero.
-  </para>
-
-  <indexterm>
-   <primary>statistics</primary>
-  </indexterm>
-  <indexterm>
-   <primary>linear regression</primary>
-  </indexterm>
-
-  <table id="functions-aggregate-statistics-table">
-   <title>Aggregate Functions for Statistics</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Argument Type</entry>
-      <entry>Return Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>correlation</primary>
-       </indexterm>
-       <indexterm>
-        <primary>corr</primary>
-       </indexterm>
-       <function>corr(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>correlation coefficient</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>covariance</primary>
-        <secondary>population</secondary>
-       </indexterm>
-       <indexterm>
-        <primary>covar_pop</primary>
-       </indexterm>
-       <function>covar_pop(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>population covariance</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>covariance</primary>
-        <secondary>sample</secondary>
-       </indexterm>
-       <indexterm>
-        <primary>covar_samp</primary>
-       </indexterm>
-       <function>covar_samp(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>sample covariance</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>regr_avgx</primary>
-       </indexterm>
-       <function>regr_avgx(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>average of the independent variable
-      (<literal>sum(<replaceable class="parameter">X</replaceable>)/<replaceable class="parameter">N</replaceable></literal>)</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>regr_avgy</primary>
-       </indexterm>
-       <function>regr_avgy(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>average of the dependent variable
-      (<literal>sum(<replaceable class="parameter">Y</replaceable>)/<replaceable class="parameter">N</replaceable></literal>)</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>regr_count</primary>
-       </indexterm>
-       <function>regr_count(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>bigint</type>
-      </entry>
-      <entry>number of input rows in which both expressions are nonnull</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>regression intercept</primary>
-       </indexterm>
-       <indexterm>
-        <primary>regr_intercept</primary>
-       </indexterm>
-       <function>regr_intercept(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>y-intercept of the least-squares-fit linear equation
-      determined by the (<replaceable
-      class="parameter">X</replaceable>, <replaceable
-      class="parameter">Y</replaceable>) pairs</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>regr_r2</primary>
-       </indexterm>
-       <function>regr_r2(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>square of the correlation coefficient</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>regression slope</primary>
-       </indexterm>
-       <indexterm>
-        <primary>regr_slope</primary>
-       </indexterm>
-       <function>regr_slope(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>slope of the least-squares-fit linear equation determined
-      by the (<replaceable class="parameter">X</replaceable>,
-      <replaceable class="parameter">Y</replaceable>) pairs</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>regr_sxx</primary>
-       </indexterm>
-       <function>regr_sxx(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry><literal>sum(<replaceable
-      class="parameter">X</replaceable>^2) - sum(<replaceable
-      class="parameter">X</replaceable>)^2/<replaceable
-      class="parameter">N</replaceable></literal> (<quote>sum of
-      squares</quote> of the independent variable)</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>regr_sxy</primary>
-       </indexterm>
-       <function>regr_sxy(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry><literal>sum(<replaceable
-      class="parameter">X</replaceable>*<replaceable
-      class="parameter">Y</replaceable>) - sum(<replaceable
-      class="parameter">X</replaceable>) * sum(<replaceable
-      class="parameter">Y</replaceable>)/<replaceable
-      class="parameter">N</replaceable></literal> (<quote>sum of
-      products</quote> of independent times dependent
-      variable)</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>regr_syy</primary>
-       </indexterm>
-       <function>regr_syy(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry><literal>sum(<replaceable
-      class="parameter">Y</replaceable>^2) - sum(<replaceable
-      class="parameter">Y</replaceable>)^2/<replaceable
-      class="parameter">N</replaceable></literal> (<quote>sum of
-      squares</quote> of the dependent variable)</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>standard deviation</primary>
-       </indexterm>
-       <indexterm>
-        <primary>stddev</primary>
-       </indexterm>
-       <function>stddev(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>smallint</type>, <type>int</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, or <type>numeric</type>
-      </entry>
-      <entry>
-       <type>double precision</type> for floating-point arguments,
-       otherwise <type>numeric</type>
-      </entry>
-      <entry>historical alias for <function>stddev_samp</function></entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>standard deviation</primary>
-        <secondary>population</secondary>
-       </indexterm>
-       <indexterm>
-        <primary>stddev_pop</primary>
-       </indexterm>
-       <function>stddev_pop(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>smallint</type>, <type>int</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, or <type>numeric</type>
-      </entry>
-      <entry>
-       <type>double precision</type> for floating-point arguments,
-       otherwise <type>numeric</type>
-      </entry>
-      <entry>population standard deviation of the input values</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>standard deviation</primary>
-        <secondary>sample</secondary>
-       </indexterm>
-       <indexterm>
-        <primary>stddev_samp</primary>
-       </indexterm>
-       <function>stddev_samp(<replaceable class="parameter">expression</replaceable>)</function>
-      </entry>
-      <entry>
-       <type>smallint</type>, <type>int</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, or <type>numeric</type>
-      </entry>
-      <entry>
-       <type>double precision</type> for floating-point arguments,
-       otherwise <type>numeric</type>
-      </entry>
-      <entry>sample standard deviation of the input values</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>variance</primary>
-       </indexterm>
-       <function>variance</function>(<replaceable class="parameter">expression</replaceable>)
-      </entry>
-      <entry>
-       <type>smallint</type>, <type>int</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, or <type>numeric</type>
-      </entry>
-      <entry>
-       <type>double precision</type> for floating-point arguments,
-       otherwise <type>numeric</type>
-      </entry>
-      <entry>historical alias for <function>var_samp</function></entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>variance</primary>
-        <secondary>population</secondary>
-       </indexterm>
-       <indexterm>
-        <primary>var_pop</primary>
-       </indexterm>
-       <function>var_pop</function>(<replaceable class="parameter">expression</replaceable>)
-      </entry>
-      <entry>
-       <type>smallint</type>, <type>int</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, or <type>numeric</type>
-      </entry>
-      <entry>
-       <type>double precision</type> for floating-point arguments,
-       otherwise <type>numeric</type>
-      </entry>
-      <entry>population variance of the input values (square of the population standard deviation)</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>variance</primary>
-        <secondary>sample</secondary>
-       </indexterm>
-       <indexterm>
-        <primary>var_samp</primary>
-       </indexterm>
-       <function>var_samp</function>(<replaceable class="parameter">expression</replaceable>)
-      </entry>
-      <entry>
-       <type>smallint</type>, <type>int</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, or <type>numeric</type>
-      </entry>
-      <entry>
-       <type>double precision</type> for floating-point arguments,
-       otherwise <type>numeric</type>
-      </entry>
-      <entry>sample variance of the input values (square of the sample standard deviation)</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="functions-window">
-  <title>Window Functions</title>
-
-  <indexterm zone="functions-window">
-   <primary>window function</primary>
-   <secondary>built-in</secondary>
-  </indexterm>
-
-  <para>
-   <firstterm>Window functions</firstterm> provide the ability to perform
-   calculations across sets of rows that are related to the current query
-   row.  See <xref linkend="tutorial-window"> for an introduction to this
-   feature.
-  </para>
-
-  <para>
-   The built-in window functions are listed in
-   <xref linkend="functions-window-table">.  Note that these functions
-   <emphasis>must</> be invoked using window function syntax; that is an
-   <literal>OVER</> clause is required.
-  </para>
-
-  <para>
-   In addition to these functions, any built-in or user-defined aggregate
-   function can be used as a window function (see
-   <xref linkend="functions-aggregate"> for a list of the built-in aggregates).
-   Aggregate functions act as window functions only when an <literal>OVER</>
-   clause follows the call; otherwise they act as regular aggregates.
-  </para>
-
-  <table id="functions-window-table">
-   <title>General-Purpose Window Functions</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Return Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry>
-       <indexterm>
-        <primary>row_number</primary>
-       </indexterm>
-       <function>row_number()</function>
-      </entry>
-      <entry>
-       <type>bigint</type>
-      </entry>
-      <entry>number of the current row within its partition, counting from 1</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>rank</primary>
-       </indexterm>
-       <function>rank()</function>
-      </entry>
-      <entry>
-       <type>bigint</type>
-      </entry>
-      <entry>rank of the current row with gaps; same as <function>row_number</> of its first peer</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>dense_rank</primary>
-       </indexterm>
-       <function>dense_rank()</function>
-      </entry>
-      <entry>
-       <type>bigint</type>
-      </entry>
-      <entry>rank of the current row without gaps; this function counts peer groups</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>percent_rank</primary>
-       </indexterm>
-       <function>percent_rank()</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>relative rank of the current row: (<function>rank</> - 1) / (total rows - 1)</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>cume_dist</primary>
-       </indexterm>
-       <function>cume_dist()</function>
-      </entry>
-      <entry>
-       <type>double precision</type>
-      </entry>
-      <entry>relative rank of the current row: (number of rows preceding or peer with current row) / (total rows)</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>ntile</primary>
-       </indexterm>
-       <function>ntile(<replaceable class="parameter">num_buckets</replaceable> <type>integer</>)</function>
-      </entry>
-      <entry>
-       <type>integer</type>
-      </entry>
-      <entry>integer ranging from 1 to the argument value, dividing the
-       partition as equally as possible</entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>lag</primary>
-       </indexterm>
-       <function>
-         lag(<replaceable class="parameter">value</replaceable> <type>any</>
-             [, <replaceable class="parameter">offset</replaceable> <type>integer</>
-             [, <replaceable class="parameter">default</replaceable> <type>any</> ]])
-       </function>
-      </entry>
-      <entry>
-       <type>same type as <replaceable class="parameter">value</replaceable></type>
-      </entry>
-      <entry>
-       returns <replaceable class="parameter">value</replaceable> evaluated at
-       the row that is <replaceable class="parameter">offset</replaceable>
-       rows before the current row within the partition; if there is no such
-       row, instead return <replaceable class="parameter">default</replaceable>.
-       Both <replaceable class="parameter">offset</replaceable> and
-       <replaceable class="parameter">default</replaceable> are evaluated
-       with respect to the current row.  If omitted,
-       <replaceable class="parameter">offset</replaceable> defaults to 1 and
-       <replaceable class="parameter">default</replaceable> to null
-      </entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>lead</primary>
-       </indexterm>
-       <function>
-         lead(<replaceable class="parameter">value</replaceable> <type>any</>
-              [, <replaceable class="parameter">offset</replaceable> <type>integer</>
-              [, <replaceable class="parameter">default</replaceable> <type>any</> ]])
-       </function>
-      </entry>
-      <entry>
-       <type>same type as <replaceable class="parameter">value</replaceable></type>
-      </entry>
-      <entry>
-       returns <replaceable class="parameter">value</replaceable> evaluated at
-       the row that is <replaceable class="parameter">offset</replaceable>
-       rows after the current row within the partition; if there is no such
-       row, instead return <replaceable class="parameter">default</replaceable>.
-       Both <replaceable class="parameter">offset</replaceable> and
-       <replaceable class="parameter">default</replaceable> are evaluated
-       with respect to the current row.  If omitted,
-       <replaceable class="parameter">offset</replaceable> defaults to 1 and
-       <replaceable class="parameter">default</replaceable> to null
-      </entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>first_value</primary>
-       </indexterm>
-       <function>first_value(<replaceable class="parameter">value</replaceable> <type>any</>)</function>
-      </entry>
-      <entry>
-       <type>same type as <replaceable class="parameter">value</replaceable></type>
-      </entry>
-      <entry>
-       returns <replaceable class="parameter">value</replaceable> evaluated
-       at the row that is the first row of the window frame
-      </entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>last_value</primary>
-       </indexterm>
-       <function>last_value(<replaceable class="parameter">value</replaceable> <type>any</>)</function>
-      </entry>
-      <entry>
-       <type>same type as <replaceable class="parameter">value</replaceable></type>
-      </entry>
-      <entry>
-       returns <replaceable class="parameter">value</replaceable> evaluated
-       at the row that is the last row of the window frame
-      </entry>
-     </row>
-
-     <row>
-      <entry>
-       <indexterm>
-        <primary>nth_value</primary>
-       </indexterm>
-       <function>
-         nth_value(<replaceable class="parameter">value</replaceable> <type>any</>, <replaceable class="parameter">nth</replaceable> <type>integer</>)
-       </function>
-      </entry>
-      <entry>
-       <type>same type as <replaceable class="parameter">value</replaceable></type>
-      </entry>
-      <entry>
-       returns <replaceable class="parameter">value</replaceable> evaluated
-       at the row that is the <replaceable class="parameter">nth</replaceable>
-       row of the window frame (counting from 1); null if no such row
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   All of the functions listed in
-   <xref linkend="functions-window-table"> depend on the sort ordering
-   specified by the <literal>ORDER BY</> clause of the associated window
-   definition.  Rows that are not distinct in the <literal>ORDER BY</>
-   ordering are said to be <firstterm>peers</>; the four ranking functions
-   are defined so that they give the same answer for any two peer rows.
-  </para>
-
-  <para>
-   Note that <function>first_value</>, <function>last_value</>, and
-   <function>nth_value</> consider only the rows within the <quote>window
-   frame</>, which by default contains the rows from the start of the
-   partition through the last peer of the current row.  This is
-   likely to give unhelpful results for <function>last_value</> and
-   sometimes also <function>nth_value</>.  You can redefine the frame by
-   adding a suitable frame specification (<literal>RANGE</> or
-   <literal>ROWS</>) to the <literal>OVER</> clause.
-   See <xref linkend="syntax-window-functions"> for more information
-   about frame specifications.
-  </para>
-
-  <para>
-   When an aggregate function is used as a window function, it aggregates
-   over the rows within the current row's window frame.
-   An aggregate used with <literal>ORDER BY</> and the default window frame
-   definition produces a <quote>running sum</> type of behavior, which may or
-   may not be what's wanted.  To obtain
-   aggregation over the whole partition, omit <literal>ORDER BY</> or use
-   <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING</>.
-   Other frame specifications can be used to obtain other effects.
-  </para>
-
-  <note>
-   <para>
-    The SQL standard defines a <literal>RESPECT NULLS</> or
-    <literal>IGNORE NULLS</> option for <function>lead</>, <function>lag</>,
-    <function>first_value</>, <function>last_value</>, and
-    <function>nth_value</>.  This is not implemented in
-<!## PG>
-    <productname>PostgreSQL</productname>: the behavior is always the
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>: the behavior is always the
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>: the behavior is always the
-<!## end>
-    same as the standard's default, namely <literal>RESPECT NULLS</>.
-    Likewise, the standard's <literal>FROM FIRST</> or <literal>FROM LAST</>
-    option for <function>nth_value</> is not implemented: only the
-    default <literal>FROM FIRST</> behavior is supported.  (You can achieve
-    the result of <literal>FROM LAST</> by reversing the <literal>ORDER BY</>
-    ordering.)
-   </para>
-  </note>
-
- </sect1>
-
- <sect1 id="functions-subquery">
-  <title>Subquery Expressions</title>
-
-  <indexterm>
-   <primary>EXISTS</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>IN</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>NOT IN</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>ANY</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>ALL</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>SOME</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>subquery</primary>
-  </indexterm>
-&common;
-  <para>
-   This section describes the <acronym>SQL</acronym>-compliant subquery
-<!## PG>
-   expressions available in <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-   expressions available in <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-   expressions available in <productname>Postgres-XL</productname>.
-<!## end>
-   All of the expression forms documented in this section return
-   Boolean (true/false) results.
-  </para>
-
-  <sect2 id="functions-subquery-exists">
-   <title><literal>EXISTS</literal></title>
-
-<synopsis>
-EXISTS (<replaceable>subquery</replaceable>)
-</synopsis>
-&common;
-  <para>
-   The argument of <token>EXISTS</token> is an arbitrary <command>SELECT</> statement,
-   or <firstterm>subquery</firstterm>.  The
-   subquery is evaluated to determine whether it returns any rows.
-   If it returns at least one row, the result of <token>EXISTS</token> is
-   <quote>true</>; if the subquery returns no rows, the result of <token>EXISTS</token>
-   is <quote>false</>.
-  </para>
-
-  <para>
-   The subquery can refer to variables from the surrounding query,
-   which will act as constants during any one evaluation of the subquery.
-  </para>
-
-  <para>
-   The subquery will generally only be executed long enough to determine
-   whether at least one row is returned, not all the way to completion.
-   It is unwise to write a subquery that has side effects (such as
-   calling sequence functions); whether the side effects occur
-   might be unpredictable.
-  </para>
-
-  <para>
-   Since the result depends only on whether any rows are returned,
-   and not on the contents of those rows, the output list of the
-   subquery is normally unimportant.  A common coding convention is
-   to write all <literal>EXISTS</> tests in the form
-   <literal>EXISTS(SELECT 1 WHERE ...)</literal>.  There are exceptions to
-   this rule however, such as subqueries that use <token>INTERSECT</token>.
-  </para>
-
-  <para>
-   This simple example is like an inner join on <literal>col2</>, but
-   it produces at most one output row for each <literal>tab1</> row,
-   even if there are several matching <literal>tab2</> rows:
-<screen>
-SELECT col1
-FROM tab1
-WHERE EXISTS (SELECT 1 FROM tab2 WHERE col2 = tab1.col2);
-</screen>
-  </para>
-  </sect2>
-
-  <sect2 id="functions-subquery-in">
-   <title><literal>IN</literal></title>
-
-<synopsis>
-<replaceable>expression</replaceable> IN (<replaceable>subquery</replaceable>)
-</synopsis>
-&common;
-  <para>
-   The right-hand side is a parenthesized
-   subquery, which must return exactly one column.  The left-hand expression
-   is evaluated and compared to each row of the subquery result.
-   The result of <token>IN</token> is <quote>true</> if any equal subquery row is found.
-   The result is <quote>false</> if no equal row is found (including the
-   case where the subquery returns no rows).
-  </para>
-
-  <para>
-   Note that if the left-hand expression yields null, or if there are
-   no equal right-hand values and at least one right-hand row yields
-   null, the result of the <token>IN</token> construct will be null, not false.
-   This is in accordance with SQL's normal rules for Boolean combinations
-   of null values.
-  </para>
-
-  <para>
-   As with <token>EXISTS</token>, it's unwise to assume that the subquery will
-   be evaluated completely.
-  </para>
-
-<synopsis>
-<replaceable>row_constructor</replaceable> IN (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The left-hand side of this form of <token>IN</token> is a row constructor,
-   as described in <xref linkend="sql-syntax-row-constructors">.
-   The right-hand side is a parenthesized
-   subquery, which must return exactly as many columns as there are
-   expressions in the left-hand row.  The left-hand expressions are
-   evaluated and compared row-wise to each row of the subquery result.
-   The result of <token>IN</token> is <quote>true</> if any equal subquery row is found.
-   The result is <quote>false</> if no equal row is found (including the
-   case where the subquery returns no rows).
-  </para>
-
-  <para>
-   As usual, null values in the rows are combined per
-   the normal rules of SQL Boolean expressions.  Two rows are considered
-   equal if all their corresponding members are non-null and equal; the rows
-   are unequal if any corresponding members are non-null and unequal;
-   otherwise the result of that row comparison is unknown (null).
-   If all the per-row results are either unequal or null, with at least one
-   null, then the result of <token>IN</token> is null.
-  </para>
-  </sect2>
-
-  <sect2 id="functions-subquery-notin">
-   <title><literal>NOT IN</literal></title>
-
-<synopsis>
-<replaceable>expression</replaceable> NOT IN (<replaceable>subquery</replaceable>)
-</synopsis>
-&common;
-  <para>
-   The right-hand side is a parenthesized
-   subquery, which must return exactly one column.  The left-hand expression
-   is evaluated and compared to each row of the subquery result.
-   The result of <token>NOT IN</token> is <quote>true</> if only unequal subquery rows
-   are found (including the case where the subquery returns no rows).
-   The result is <quote>false</> if any equal row is found.
-  </para>
-
-  <para>
-   Note that if the left-hand expression yields null, or if there are
-   no equal right-hand values and at least one right-hand row yields
-   null, the result of the <token>NOT IN</token> construct will be null, not true.
-   This is in accordance with SQL's normal rules for Boolean combinations
-   of null values.
-  </para>
-
-  <para>
-   As with <token>EXISTS</token>, it's unwise to assume that the subquery will
-   be evaluated completely.
-  </para>
-
-<synopsis>
-<replaceable>row_constructor</replaceable> NOT IN (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The left-hand side of this form of <token>NOT IN</token> is a row constructor,
-   as described in <xref linkend="sql-syntax-row-constructors">.
-   The right-hand side is a parenthesized
-   subquery, which must return exactly as many columns as there are
-   expressions in the left-hand row.  The left-hand expressions are
-   evaluated and compared row-wise to each row of the subquery result.
-   The result of <token>NOT IN</token> is <quote>true</> if only unequal subquery rows
-   are found (including the case where the subquery returns no rows).
-   The result is <quote>false</> if any equal row is found.
-  </para>
-
-  <para>
-   As usual, null values in the rows are combined per
-   the normal rules of SQL Boolean expressions.  Two rows are considered
-   equal if all their corresponding members are non-null and equal; the rows
-   are unequal if any corresponding members are non-null and unequal;
-   otherwise the result of that row comparison is unknown (null).
-   If all the per-row results are either unequal or null, with at least one
-   null, then the result of <token>NOT IN</token> is null.
-  </para>
-  </sect2>
-
-  <sect2 id="functions-subquery-any-some">
-   <title><literal>ANY</literal>/<literal>SOME</literal></title>
-
-<synopsis>
-<replaceable>expression</replaceable> <replaceable>operator</replaceable> ANY (<replaceable>subquery</replaceable>)
-<replaceable>expression</replaceable> <replaceable>operator</replaceable> SOME (<replaceable>subquery</replaceable>)
-</synopsis>
-&common;
-  <para>
-   The right-hand side is a parenthesized
-   subquery, which must return exactly one column.  The left-hand expression
-   is evaluated and compared to each row of the subquery result using the
-   given <replaceable>operator</replaceable>, which must yield a Boolean
-   result.
-   The result of <token>ANY</token> is <quote>true</> if any true result is obtained.
-   The result is <quote>false</> if no true result is found (including the
-   case where the subquery returns no rows).
-  </para>
-
-  <para>
-   <token>SOME</token> is a synonym for <token>ANY</token>.
-   <token>IN</token> is equivalent to <literal>= ANY</literal>.
-  </para>
-
-  <para>
-   Note that if there are no successes and at least one right-hand row yields
-   null for the operator's result, the result of the <token>ANY</token> construct
-   will be null, not false.
-   This is in accordance with SQL's normal rules for Boolean combinations
-   of null values.
-  </para>
-
-  <para>
-   As with <token>EXISTS</token>, it's unwise to assume that the subquery will
-   be evaluated completely.
-  </para>
-
-<synopsis>
-<replaceable>row_constructor</replaceable> <replaceable>operator</> ANY (<replaceable>subquery</replaceable>)
-<replaceable>row_constructor</replaceable> <replaceable>operator</> SOME (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The left-hand side of this form of <token>ANY</token> is a row constructor,
-   as described in <xref linkend="sql-syntax-row-constructors">.
-   The right-hand side is a parenthesized
-   subquery, which must return exactly as many columns as there are
-   expressions in the left-hand row.  The left-hand expressions are
-   evaluated and compared row-wise to each row of the subquery result,
-   using the given <replaceable>operator</replaceable>.
-   The result of <token>ANY</token> is <quote>true</> if the comparison
-   returns true for any subquery row.
-   The result is <quote>false</> if the comparison returns false for every
-   subquery row (including the case where the subquery returns no
-   rows).
-   The result is NULL if the comparison does not return true for any row,
-   and it returns NULL for at least one row.
-  </para>
-
-  <para>
-   See <xref linkend="row-wise-comparison"> for details about the meaning
-   of a row-wise comparison.
-  </para>
-  </sect2>
-
-  <sect2 id="functions-subquery-all">
-   <title><literal>ALL</literal></title>
-
-<synopsis>
-<replaceable>expression</replaceable> <replaceable>operator</replaceable> ALL (<replaceable>subquery</replaceable>)
-</synopsis>
-&common;
-  <para>
-   The right-hand side is a parenthesized
-   subquery, which must return exactly one column.  The left-hand expression
-   is evaluated and compared to each row of the subquery result using the
-   given <replaceable>operator</replaceable>, which must yield a Boolean
-   result.
-   The result of <token>ALL</token> is <quote>true</> if all rows yield true
-   (including the case where the subquery returns no rows).
-   The result is <quote>false</> if any false result is found.
-   The result is NULL if the comparison does not return false for any row,
-   and it returns NULL for at least one row.
-  </para>
-
-  <para>
-   <token>NOT IN</token> is equivalent to <literal>&lt;&gt; ALL</literal>.
-  </para>
-
-  <para>
-   As with <token>EXISTS</token>, it's unwise to assume that the subquery will
-   be evaluated completely.
-  </para>
-
-<synopsis>
-<replaceable>row_constructor</replaceable> <replaceable>operator</replaceable> ALL (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The left-hand side of this form of <token>ALL</token> is a row constructor,
-   as described in <xref linkend="sql-syntax-row-constructors">.
-   The right-hand side is a parenthesized
-   subquery, which must return exactly as many columns as there are
-   expressions in the left-hand row.  The left-hand expressions are
-   evaluated and compared row-wise to each row of the subquery result,
-   using the given <replaceable>operator</replaceable>.
-   The result of <token>ALL</token> is <quote>true</> if the comparison
-   returns true for all subquery rows (including the
-   case where the subquery returns no rows).
-   The result is <quote>false</> if the comparison returns false for any
-   subquery row.
-   The result is NULL if the comparison does not return false for any
-   subquery row, and it returns NULL for at least one row.
-  </para>
-
-  <para>
-   See <xref linkend="row-wise-comparison"> for details about the meaning
-   of a row-wise comparison.
-  </para>
-  </sect2>
-
-  <sect2>
-   <title>Row-wise Comparison</title>
-
-   <indexterm zone="functions-subquery">
-    <primary>comparison</primary>
-    <secondary>subquery result row</secondary>
-   </indexterm>
-
-<synopsis>
-<replaceable>row_constructor</replaceable> <replaceable>operator</replaceable> (<replaceable>subquery</replaceable>)
-</synopsis>
-&common;
-  <para>
-   The left-hand side is a row constructor,
-   as described in <xref linkend="sql-syntax-row-constructors">.
-   The right-hand side is a parenthesized subquery, which must return exactly
-   as many columns as there are expressions in the left-hand row. Furthermore,
-   the subquery cannot return more than one row.  (If it returns zero rows,
-   the result is taken to be null.)  The left-hand side is evaluated and
-   compared row-wise to the single subquery result row.
-  </para>
-
-  <para>
-   See <xref linkend="row-wise-comparison"> for details about the meaning
-   of a row-wise comparison.
-  </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="functions-comparisons">
-  <title>Row and Array Comparisons</title>
-
-  <indexterm>
-   <primary>IN</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>NOT IN</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>ANY</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>ALL</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>SOME</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>row-wise comparison</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>comparison</primary>
-   <secondary>row-wise</secondary>
-  </indexterm>
-
-  <indexterm>
-   <primary>IS DISTINCT FROM</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>IS NOT DISTINCT FROM</primary>
-  </indexterm>
-&common;
-  <para>
-   This section describes several specialized constructs for making
-   multiple comparisons between groups of values.  These forms are
-   syntactically related to the subquery forms of the previous section,
-   but do not involve subqueries.
-   The forms involving array subexpressions are
-<!## PG>
-   <productname>PostgreSQL</productname> extensions; the rest are
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extensions; the rest are
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extensions; the rest are
-<!## end>
-   <acronym>SQL</acronym>-compliant.
-   All of the expression forms documented in this section return
-   Boolean (true/false) results.
-  </para>
-
-  <sect2>
-   <title><literal>IN</literal></title>
-
-<synopsis>
-<replaceable>expression</replaceable> IN (<replaceable>value</replaceable> <optional>, ...</optional>)
-</synopsis>
-&common;
-  <para>
-   The right-hand side is a parenthesized list
-   of scalar expressions.  The result is <quote>true</> if the left-hand expression's
-   result is equal to any of the right-hand expressions.  This is a shorthand
-   notation for
-
-<synopsis>
-<replaceable>expression</replaceable> = <replaceable>value1</replaceable>
-OR
-<replaceable>expression</replaceable> = <replaceable>value2</replaceable>
-OR
-...
-</synopsis>
-  </para>
-
-  <para>
-   Note that if the left-hand expression yields null, or if there are
-   no equal right-hand values and at least one right-hand expression yields
-   null, the result of the <token>IN</token> construct will be null, not false.
-   This is in accordance with SQL's normal rules for Boolean combinations
-   of null values.
-  </para>
-  </sect2>
-
-  <sect2>
-   <title><literal>NOT IN</literal></title>
-
-<synopsis>
-<replaceable>expression</replaceable> NOT IN (<replaceable>value</replaceable> <optional>, ...</optional>)
-</synopsis>
-&common;
-  <para>
-   The right-hand side is a parenthesized list
-   of scalar expressions.  The result is <quote>true</quote> if the left-hand expression's
-   result is unequal to all of the right-hand expressions.  This is a shorthand
-   notation for
-
-<synopsis>
-<replaceable>expression</replaceable> &lt;&gt; <replaceable>value1</replaceable>
-AND
-<replaceable>expression</replaceable> &lt;&gt; <replaceable>value2</replaceable>
-AND
-...
-</synopsis>
-  </para>
-
-  <para>
-   Note that if the left-hand expression yields null, or if there are
-   no equal right-hand values and at least one right-hand expression yields
-   null, the result of the <token>NOT IN</token> construct will be null, not true
-   as one might naively expect.
-   This is in accordance with SQL's normal rules for Boolean combinations
-   of null values.
-  </para>
-
-  <tip>
-  <para>
-   <literal>x NOT IN y</literal> is equivalent to <literal>NOT (x IN y)</literal> in all
-   cases.  However, null values are much more likely to trip up the novice when
-   working with <token>NOT IN</token> than when working with <token>IN</token>.
-   It is best to express your condition positively if possible.
-  </para>
-  </tip>
-  </sect2>
-
-  <sect2>
-   <title><literal>ANY</literal>/<literal>SOME</literal> (array)</title>
-
-<synopsis>
-<replaceable>expression</replaceable> <replaceable>operator</replaceable> ANY (<replaceable>array expression</replaceable>)
-<replaceable>expression</replaceable> <replaceable>operator</replaceable> SOME (<replaceable>array expression</replaceable>)
-</synopsis>
-&common;
-  <para>
-   The right-hand side is a parenthesized expression, which must yield an
-   array value.
-   The left-hand expression
-   is evaluated and compared to each element of the array using the
-   given <replaceable>operator</replaceable>, which must yield a Boolean
-   result.
-   The result of <token>ANY</token> is <quote>true</> if any true result is obtained.
-   The result is <quote>false</> if no true result is found (including the
-   case where the array has zero elements).
-  </para>
-
-  <para>
-   If the array expression yields a null array, the result of
-   <token>ANY</token> will be null.  If the left-hand expression yields null,
-   the result of <token>ANY</token> is ordinarily null (though a non-strict
-   comparison operator could possibly yield a different result).
-   Also, if the right-hand array contains any null elements and no true
-   comparison result is obtained, the result of <token>ANY</token>
-   will be null, not false (again, assuming a strict comparison operator).
-   This is in accordance with SQL's normal rules for Boolean combinations
-   of null values.
-  </para>
-
-  <para>
-   <token>SOME</token> is a synonym for <token>ANY</token>.
-  </para>
-  </sect2>
-
-  <sect2>
-   <title><literal>ALL</literal> (array)</title>
-
-<synopsis>
-<replaceable>expression</replaceable> <replaceable>operator</replaceable> ALL (<replaceable>array expression</replaceable>)
-</synopsis>
-&common;
-  <para>
-   The right-hand side is a parenthesized expression, which must yield an
-   array value.
-   The left-hand expression
-   is evaluated and compared to each element of the array using the
-   given <replaceable>operator</replaceable>, which must yield a Boolean
-   result.
-   The result of <token>ALL</token> is <quote>true</> if all comparisons yield true
-   (including the case where the array has zero elements).
-   The result is <quote>false</> if any false result is found.
-  </para>
-
-  <para>
-   If the array expression yields a null array, the result of
-   <token>ALL</token> will be null.  If the left-hand expression yields null,
-   the result of <token>ALL</token> is ordinarily null (though a non-strict
-   comparison operator could possibly yield a different result).
-   Also, if the right-hand array contains any null elements and no false
-   comparison result is obtained, the result of <token>ALL</token>
-   will be null, not true (again, assuming a strict comparison operator).
-   This is in accordance with SQL's normal rules for Boolean combinations
-   of null values.
-  </para>
-  </sect2>
-
-  <sect2 id="row-wise-comparison">
-   <title>Row-wise Comparison</title>
-
-<synopsis>
-<replaceable>row_constructor</replaceable> <replaceable>operator</replaceable> <replaceable>row_constructor</replaceable>
-</synopsis>
-&common;
-  <para>
-   Each side is a row constructor,
-   as described in <xref linkend="sql-syntax-row-constructors">.
-   The two row values must have the same number of fields.
-   Each side is evaluated and they are compared row-wise.  Row comparisons
-   are allowed when the <replaceable>operator</replaceable> is
-   <literal>=</>,
-   <literal>&lt;&gt;</>,
-   <literal>&lt;</>,
-   <literal>&lt;=</>,
-   <literal>&gt;</> or
-   <literal>&gt;=</>,
-   or has semantics similar to one of these.  (To be specific, an operator
-   can be a row comparison operator if it is a member of a B-tree operator
-   class, or is the negator of the <literal>=</> member of a B-tree operator
-   class.)
-  </para>
-
-  <para>
-   The <literal>=</> and <literal>&lt;&gt;</> cases work slightly differently
-   from the others.  Two rows are considered
-   equal if all their corresponding members are non-null and equal; the rows
-   are unequal if any corresponding members are non-null and unequal;
-   otherwise the result of the row comparison is unknown (null).
-  </para>
-
-  <para>
-   For the <literal>&lt;</>, <literal>&lt;=</>, <literal>&gt;</> and
-   <literal>&gt;=</> cases, the row elements are compared left-to-right,
-   stopping as soon as an unequal or null pair of elements is found.
-   If either of this pair of elements is null, the result of the
-   row comparison is unknown (null); otherwise comparison of this pair
-   of elements determines the result.  For example,
-   <literal>ROW(1,2,NULL) &lt; ROW(1,3,0)</>
-   yields true, not null, because the third pair of elements are not
-   considered.
-  </para>
-
-  <note>
-   <para>
-    Prior to <productname>PostgreSQL</productname> 8.2, the
-    <literal>&lt;</>, <literal>&lt;=</>, <literal>&gt;</> and <literal>&gt;=</>
-    cases were not handled per SQL specification.  A comparison like
-    <literal>ROW(a,b) &lt; ROW(c,d)</>
-    was implemented as
-    <literal>a &lt; c AND b &lt; d</>
-    whereas the correct behavior is equivalent to
-    <literal>a &lt; c OR (a = c AND b &lt; d)</>.
-   </para>
-  </note>
-
-<synopsis>
-<replaceable>row_constructor</replaceable> IS DISTINCT FROM <replaceable>row_constructor</replaceable>
-</synopsis>
-
-  <para>
-   This construct is similar to a <literal>&lt;&gt;</literal> row comparison,
-   but it does not yield null for null inputs.  Instead, any null value is
-   considered unequal to (distinct from) any non-null value, and any two
-   nulls are considered equal (not distinct).  Thus the result will
-   either be true or false, never null.
-  </para>
-
-<synopsis>
-<replaceable>row_constructor</replaceable> IS NOT DISTINCT FROM <replaceable>row_constructor</replaceable>
-</synopsis>
-
-  <para>
-   This construct is similar to a <literal>=</literal> row comparison,
-   but it does not yield null for null inputs.  Instead, any null value is
-   considered unequal to (distinct from) any non-null value, and any two
-   nulls are considered equal (not distinct).  Thus the result will always
-   be either true or false, never null.
-  </para>
-
-  <note>
-   <para>
-    The SQL specification requires row-wise comparison to return NULL if the
-    result depends on comparing two NULL values or a NULL and a non-NULL.
-<!## PG>
-    <productname>PostgreSQL</productname> does this only when comparing the
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> does this only when comparing the
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> does this only when comparing the
-<!## end>
-    results of two row constructors or comparing a row constructor to the
-    output of a subquery (as in <xref linkend="functions-subquery">).
-    In other contexts where two composite-type values are compared, two
-    NULL field values are considered equal, and a NULL is considered larger
-    than a non-NULL.  This is necessary in order to have consistent sorting
-    and indexing behavior for composite types.
-   </para>
-  </note>
-
-  </sect2>
- </sect1>
-
- <sect1 id="functions-srf">
-  <title>Set Returning Functions</title>
-&common;
-  <indexterm zone="functions-srf">
-   <primary>set returning functions</primary>
-   <secondary>functions</secondary>
-  </indexterm>
-
-  <indexterm>
-   <primary>generate_series</primary>
-  </indexterm>
-&common;
-  <para>
-   This section describes functions that possibly return more than one row.
-   Currently the only functions in this class are series generating functions,
-   as detailed in <xref linkend="functions-srf-series"> and
-   <xref linkend="functions-srf-subscripts">.
-  </para>
-
-  <table id="functions-srf-series">
-   <title>Series Generating Functions</title>
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Argument Type</entry>
-      <entry>Return Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal><function>generate_series(<parameter>start</parameter>, <parameter>stop</parameter>)</function></literal></entry>
-      <entry><type>int</type> or <type>bigint</type></entry>
-      <entry><type>setof int</type> or <type>setof bigint</type> (same as argument type)</entry>
-      <entry>
-       Generate a series of values, from <parameter>start</parameter> to <parameter>stop</parameter>
-       with a step size of one
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>generate_series(<parameter>start</parameter>, <parameter>stop</parameter>, <parameter>step</parameter>)</function></literal></entry>
-      <entry><type>int</type> or <type>bigint</type></entry>
-      <entry><type>setof int</type> or <type>setof bigint</type> (same as argument type)</entry>
-      <entry>
-       Generate a series of values, from <parameter>start</parameter> to <parameter>stop</parameter>
-       with a step size of <parameter>step</parameter>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>generate_series(<parameter>start</parameter>, <parameter>stop</parameter>, <parameter>step</parameter> <type>interval</>)</function></literal></entry>
-      <entry><type>timestamp</type> or <type>timestamp with time zone</type></entry>
-      <entry><type>setof timestamp</type> or <type>setof timestamp with time zone</type> (same as argument type)</entry>
-      <entry>
-       Generate a series of values, from <parameter>start</parameter> to <parameter>stop</parameter>
-       with a step size of <parameter>step</parameter>
-      </entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   When <parameter>step</parameter> is positive, zero rows are returned if
-   <parameter>start</parameter> is greater than <parameter>stop</parameter>.
-   Conversely, when <parameter>step</parameter> is negative, zero rows are
-   returned if <parameter>start</parameter> is less than <parameter>stop</parameter>.
-   Zero rows are also returned for <literal>NULL</literal> inputs. It is an error
-   for <parameter>step</parameter> to be zero. Some examples follow:
-<programlisting>
-SELECT * FROM generate_series(2,4);
- generate_series
------------------
-               2
-               3
-               4
-(3 rows)
-
-SELECT * FROM generate_series(5,1,-2);
- generate_series
------------------
-               5
-               3
-               1
-(3 rows)
-
-SELECT * FROM generate_series(4,3);
- generate_series
------------------
-(0 rows)
-
--- this example relies on the date-plus-integer operator
-SELECT current_date + s.a AS dates FROM generate_series(0,14,7) AS s(a);
-   dates
-------------
- 2004-02-05
- 2004-02-12
- 2004-02-19
-(3 rows)
-
-SELECT * FROM generate_series('2008-03-01 00:00'::timestamp,
-                              '2008-03-04 12:00', '10 hours');
-   generate_series   
----------------------
- 2008-03-01 00:00:00
- 2008-03-01 10:00:00
- 2008-03-01 20:00:00
- 2008-03-02 06:00:00
- 2008-03-02 16:00:00
- 2008-03-03 02:00:00
- 2008-03-03 12:00:00
- 2008-03-03 22:00:00
- 2008-03-04 08:00:00
-(9 rows)
-</programlisting>
-  </para>
-
-  <table id="functions-srf-subscripts">
-   <title>Subscript Generating Functions</title>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Return Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal><function>generate_subscripts(<parameter>array anyarray</parameter>, <parameter>dim int</parameter>)</function></literal></entry>
-      <entry><type>setof int</type></entry>
-      <entry>
-       Generate a series comprising the given array's subscripts.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>generate_subscripts(<parameter>array anyarray</parameter>, <parameter>dim int</parameter>, <parameter>reverse boolean</parameter>)</function></literal></entry>
-      <entry><type>setof int</type></entry>
-      <entry>
-       Generate a series comprising the given array's subscripts. When
-       <parameter>reverse</parameter> is true, the series is returned in
-       reverse order.
-      </entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <indexterm>
-   <primary>generate_subscripts</primary>
-  </indexterm>
-
-  <para>
-   <function>generate_subscripts</> is a convenience function that generates
-   the set of valid subscripts for the specified dimension of the given
-   array.
-   Zero rows are returned for arrays that do not have the requested dimension,
-   or for NULL arrays (but valid subscripts are returned for NULL array
-   elements).  Some examples follow:
-<programlisting>
--- basic usage
-SELECT generate_subscripts('{NULL,1,NULL,2}'::int[], 1) AS s;
- s 
----
- 1
- 2
- 3
- 4
-(4 rows)
-
--- presenting an array, the subscript and the subscripted
--- value requires a subquery
-SELECT * FROM arrays;
-         a          
---------------------
- {-1,-2}
- {100,200,300}
-(2 rows)
-
-SELECT a AS array, s AS subscript, a[s] AS value
-FROM (SELECT generate_subscripts(a, 1) AS s, a FROM arrays) foo;
-     array     | subscript | value
----------------+-----------+-------
- {-1,-2}       |         1 |    -1
- {-1,-2}       |         2 |    -2
- {100,200,300} |         1 |   100
- {100,200,300} |         2 |   200
- {100,200,300} |         3 |   300
-(5 rows)
-
--- unnest a 2D array
-CREATE OR REPLACE FUNCTION unnest2(anyarray)
-RETURNS SETOF anyelement AS $$
-select $1[i][j]
-   from generate_subscripts($1,1) g1(i),
-        generate_subscripts($1,2) g2(j);
-$$ LANGUAGE sql IMMUTABLE;
-CREATE FUNCTION
-postgres=# SELECT * FROM unnest2(ARRAY[[1,2],[3,4]]);
- unnest2 
----------
-       1
-       2
-       3
-       4
-(4 rows)
-</programlisting>
-  </para>
-
- </sect1>
-
- <sect1 id="functions-info">
-  <title>System Information Functions</title>
-&common;
-  <para>
-   <xref linkend="functions-info-session-table"> shows several
-   functions that extract session and system information.
-  </para>
-
-  <para>
-   In addition to the functions listed in this section, there are a number of
-   functions related to the statistics system that also provide system
-   information. See <xref linkend="monitoring-stats-views"> for more
-   information.
-  </para>
-
-   <table id="functions-info-session-table">
-    <title>Session Information Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal><function>current_catalog</function></literal></entry>
-       <entry><type>name</type></entry>
-       <entry>name of current database (called <quote>catalog</quote> in the SQL standard)</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>current_database()</function></literal></entry>
-       <entry><type>name</type></entry>
-       <entry>name of current database</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>current_query()</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>text of the currently executing query, as submitted
-       by the client (might contain more than one statement)</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>current_schema</function>[()]</literal></entry>
-       <entry><type>name</type></entry>
-       <entry>name of current schema</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>current_schemas(<type>boolean</type>)</function></literal></entry>
-       <entry><type>name[]</type></entry>
-       <entry>names of schemas in search path, optionally including implicit schemas</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>current_user</function></literal></entry>
-       <entry><type>name</type></entry>
-       <entry>user name of current execution context</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>inet_client_addr()</function></literal></entry>
-       <entry><type>inet</type></entry>
-        <entry>address of the remote connection</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>inet_client_port()</function></literal></entry>
-       <entry><type>int</type></entry>
-       <entry>port of the remote connection</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>inet_server_addr()</function></literal></entry>
-       <entry><type>inet</type></entry>
-        <entry>address of the local connection</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>inet_server_port()</function></literal></entry>
-       <entry><type>int</type></entry>
-       <entry>port of the local connection</entry>
-      </row>
-
-      <row>
-       <!-- See also the entry for this in monitoring.sgml -->
-       <entry><literal><function>pg_backend_pid()</function></literal></entry>
-       <entry><type>int</type></entry>
-       <entry>
-        Process ID of the server process attached to the current session
-       </entry>
-      </row>
-
-      <row>
-       <entry><literal><function>pg_conf_load_time()</function></literal></entry>
-       <entry><type>timestamp with time zone</type></entry>
-       <entry>configuration load time</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>pg_is_other_temp_schema(<type>oid</type>)</function></literal></entry>
-       <entry><type>boolean</type></entry>
-       <entry>is schema another session's temporary schema?</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>pg_listening_channels()</function></literal></entry>
-       <entry><type>setof text</type></entry>
-       <entry>channel names that the session is currently listening on</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>pg_my_temp_schema()</function></literal></entry>
-       <entry><type>oid</type></entry>
-       <entry>OID of session's temporary schema, or 0 if none</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>pg_postmaster_start_time()</function></literal></entry>
-       <entry><type>timestamp with time zone</type></entry>
-       <entry>server start time</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>session_user</function></literal></entry>
-       <entry><type>name</type></entry>
-       <entry>session user name</entry>
-      </row>
-
-      <row>
-       <entry><literal><function>user</function></literal></entry>
-       <entry><type>name</type></entry>
-       <entry>equivalent to <function>current_user</function></entry>
-      </row>
-
-      <row>
-       <entry><literal><function>version()</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry><productname>PostgreSQL</> version information</entry>
-      </row>
-
-<!## XC>
-      <row>
-       <entry><literal><function>pgxc_version()</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry><productname>Postgres-XC</> version information</entry>
-      </row>
-<!## end>
-<!## XL>
-      <row>
-       <entry><literal><function>pgxc_version()</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry><productname>Postgres-XL Cluster</> version information</entry>
-      </row>
-<!## end>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <note>
-    <para>
-     <function>current_catalog</function>, <function>current_schema</function>,
-     <function>current_user</function>, <function>session_user</function>,
-     and <function>user</function> have special syntactic status
-     in <acronym>SQL</acronym>: they must be called without trailing
-<!## PG>
-     parentheses.  (In PostgreSQL, parentheses can optionally be used with
-<!## end>
-<!## XC>
-     parentheses.  (In Postgres-XC, parentheses can optionally be used with
-<!## end>
-<!## XL>
-     parentheses.  (In Postgres-XL, parentheses can optionally be used with
-<!## end>
-     <function>current_schema</function>, but not with the others.)
-    </para>
-   </note>
-
-   <indexterm>
-    <primary>current_catalog</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>current_database</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>current_query</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>current_schema</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>current_schemas</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>current_user</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_backend_pid</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>schema</primary>
-    <secondary>current</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>search path</primary>
-    <secondary>current</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>session_user</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>user</primary>
-    <secondary>current</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>user</primary>
-   </indexterm>
-
-   <para>
-    The <function>session_user</function> is normally the user who initiated
-    the current database connection; but superusers can change this setting
-    with <xref linkend="sql-set-session-authorization">.
-    The <function>current_user</function> is the user identifier
-    that is applicable for permission checking. Normally it is equal
-    to the session user, but it can be changed with
-    <xref linkend="sql-set-role">.
-    It also changes during the execution of
-    functions with the attribute <literal>SECURITY DEFINER</literal>.
-    In Unix parlance, the session user is the <quote>real user</quote> and
-    the current user is the <quote>effective user</quote>.
-   </para>
-
-   <para>
-    <function>current_schema</function> returns the name of the schema that is
-    first in the search path (or a null value if the search path is
-    empty).  This is the schema that will be used for any tables or
-    other named objects that are created without specifying a target schema.
-    <function>current_schemas(boolean)</function> returns an array of the names of all
-    schemas presently in the search path.  The Boolean option determines whether or not
-    implicitly included system schemas such as <literal>pg_catalog</> are included in the
-    returned search path.
-   </para>
-
-   <note>
-    <para>
-     The search path can be altered at run time.  The command is:
-<programlisting>
-SET search_path TO <replaceable>schema</> <optional>, <replaceable>schema</>, ...</optional>
-</programlisting>
-    </para>
-   </note>
-
-   <indexterm>
-    <primary>pg_listening_channels</primary>
-   </indexterm>
-
-   <para>
-    <function>pg_listening_channels</function> returns a set of names of
-    channels that the current session is listening to.  See <xref
-    linkend="sql-listen"> for more information.
-   </para>
-
-   <indexterm>
-    <primary>inet_client_addr</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>inet_client_port</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>inet_server_addr</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>inet_server_port</primary>
-   </indexterm>
-
-   <para>
-     <function>inet_client_addr</function> returns the IP address of the
-     current client, and <function>inet_client_port</function> returns the
-     port number.
-     <function>inet_server_addr</function> returns the IP address on which
-     the server accepted the current connection, and
-     <function>inet_server_port</function> returns the port number.
-     All these functions return NULL if the current connection is via a
-     Unix-domain socket.
-   </para>
-
-   <indexterm>
-    <primary>pg_my_temp_schema</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_is_other_temp_schema</primary>
-   </indexterm>
-
-   <para>
-    <function>pg_my_temp_schema</function> returns the OID of the current
-    session's temporary schema, or zero if it has none (because it has not
-    created any temporary tables).
-    <function>pg_is_other_temp_schema</function> returns true if the
-    given OID is the OID of another session's temporary schema.
-    (This can be useful, for example, to exclude other sessions' temporary
-    tables from a catalog display.)
-   </para>
-
-   <indexterm>
-    <primary>pg_postmaster_start_time</primary>
-   </indexterm>
-
-   <para>
-    <function>pg_postmaster_start_time</function> returns the
-    <type>timestamp with time zone</type> when the
-    server started.
-   </para>
-
-   <indexterm>
-    <primary>pg_conf_load_time</primary>
-   </indexterm>
-
-   <para>
-    <function>pg_conf_load_time</function> returns the
-    <type>timestamp with time zone</type> when the
-    server configuration files were last loaded.
-    (If the current session was alive at the time, this will be the time
-    when the session itself re-read the configuration files, so the
-    reading will vary a little in different sessions.  Otherwise it is
-    the time when the postmaster process re-read the configuration files.)
-   </para>
-
-   <indexterm>
-    <primary>version</primary>
-   </indexterm>
-
-   <para>
-    <function>version</function> returns a string describing the
-<!## PG>
-    <productname>PostgreSQL</productname> server's version.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> server's version.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> server's version.
-<!## end>
-   </para>
-
-  <indexterm>
-   <primary>privilege</primary>
-   <secondary>querying</secondary>
-  </indexterm>
-
-  <para>
-   <xref linkend="functions-info-access-table"> lists functions that
-   allow the user to query object access privileges programmatically.
-   See <xref linkend="ddl-priv"> for more information about
-   privileges.
-  </para>
-
-   <table id="functions-info-access-table">
-    <title>Access Privilege Inquiry Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal><function>has_any_column_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>table</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for any column of table</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_any_column_privilege</function>(<parameter>table</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for any column of table</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_column_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>table</parameter>,
-                                  <parameter>column</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for column</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_column_privilege</function>(<parameter>table</parameter>,
-                                  <parameter>column</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for column</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_database_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>database</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for database</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_database_privilege</function>(<parameter>database</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for database</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_foreign_data_wrapper_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>fdw</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for foreign-data wrapper</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_foreign_data_wrapper_privilege</function>(<parameter>fdw</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for foreign-data wrapper</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_function_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>function</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for function</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_function_privilege</function>(<parameter>function</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for function</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_language_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>language</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for language</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_language_privilege</function>(<parameter>language</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for language</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_schema_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>schema</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for schema</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_schema_privilege</function>(<parameter>schema</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for schema</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_sequence_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>sequence</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for sequence</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_sequence_privilege</function>(<parameter>sequence</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for sequence</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_server_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>server</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for foreign server</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_server_privilege</function>(<parameter>server</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for foreign server</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_table_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>table</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for table</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_table_privilege</function>(<parameter>table</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for table</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_tablespace_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>tablespace</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for tablespace</entry>
-      </row>
-      <row>
-       <entry><literal><function>has_tablespace_privilege</function>(<parameter>tablespace</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for tablespace</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_has_role</function>(<parameter>user</parameter>,
-                                  <parameter>role</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have privilege for role</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_has_role</function>(<parameter>role</parameter>,
-                                  <parameter>privilege</parameter>)</literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have privilege for role</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm>
-    <primary>has_any_column_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>has_column_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>has_database_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>has_function_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>has_foreign_data_wrapper_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>has_language_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>has_schema_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>has_server_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>has_sequence_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>has_table_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>has_tablespace_privilege</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_has_role</primary>
-   </indexterm>
-
-   <para>
-    <function>has_table_privilege</function> checks whether a user
-    can access a table in a particular way.  The user can be
-    specified by name, by OID (<literal>pg_authid.oid</literal>),
-    <literal>public</> to indicate the PUBLIC pseudo-role, or if the argument is
-    omitted
-    <function>current_user</function> is assumed.  The table can be specified
-    by name or by OID.  (Thus, there are actually six variants of
-    <function>has_table_privilege</function>, which can be distinguished by
-    the number and types of their arguments.)  When specifying by name,
-    the name can be schema-qualified if necessary.
-    The desired access privilege type
-    is specified by a text string, which must evaluate to one of the
-    values <literal>SELECT</literal>, <literal>INSERT</literal>,
-    <literal>UPDATE</literal>, <literal>DELETE</literal>, <literal>TRUNCATE</>,
-    <literal>REFERENCES</literal>, or <literal>TRIGGER</literal>.  Optionally,
-    <literal>WITH GRANT OPTION</> can be added to a privilege type to test
-    whether the privilege is held with grant option.  Also, multiple privilege
-    types can be listed separated by commas, in which case the result will
-    be <literal>true</> if any of the listed privileges is held.
-    (Case of the privilege string is not significant, and extra whitespace
-    is allowed between but not within privilege names.)
-    Some examples:
-<programlisting>
-SELECT has_table_privilege('myschema.mytable', 'select');
-SELECT has_table_privilege('joe', 'mytable', 'INSERT, SELECT WITH GRANT OPTION');
-</programlisting>
-   </para>
-
-   <para>
-    <function>has_sequence_privilege</function> checks whether a user
-    can access a sequence in a particular way.  The possibilities for its
-    arguments are analogous to <function>has_table_privilege</function>.
-    The desired access privilege type must evaluate to one of
-    <literal>USAGE</literal>,
-    <literal>SELECT</literal>, or
-    <literal>UPDATE</literal>.
-   </para>
-
-   <para>
-    <function>has_any_column_privilege</function> checks whether a user can
-    access any column of a table in a particular way.
-    Its argument possibilities
-    are analogous to <function>has_table_privilege</>,
-    except that the desired access privilege type must evaluate to some
-    combination of
-    <literal>SELECT</literal>,
-    <literal>INSERT</literal>,
-    <literal>UPDATE</literal>, or
-    <literal>REFERENCES</literal>.  Note that having any of these privileges
-    at the table level implicitly grants it for each column of the table,
-    so <function>has_any_column_privilege</function> will always return
-    <literal>true</> if <function>has_table_privilege</> does for the same
-    arguments.  But <function>has_any_column_privilege</> also succeeds if
-    there is a column-level grant of the privilege for at least one column.
-   </para>
-
-   <para>
-    <function>has_column_privilege</function> checks whether a user
-    can access a column in a particular way.
-    Its argument possibilities
-    are analogous to <function>has_table_privilege</function>,
-    with the addition that the column can be specified either by name
-    or attribute number.
-    The desired access privilege type must evaluate to some combination of
-    <literal>SELECT</literal>,
-    <literal>INSERT</literal>,
-    <literal>UPDATE</literal>, or
-    <literal>REFERENCES</literal>.  Note that having any of these privileges
-    at the table level implicitly grants it for each column of the table.
-   </para>
-
-   <para>
-    <function>has_database_privilege</function> checks whether a user
-    can access a database in a particular way.
-    Its argument possibilities
-    are analogous to <function>has_table_privilege</function>.
-    The desired access privilege type must evaluate to some combination of
-    <literal>CREATE</literal>,
-    <literal>CONNECT</literal>,
-    <literal>TEMPORARY</literal>, or
-    <literal>TEMP</literal> (which is equivalent to
-    <literal>TEMPORARY</literal>).
-   </para>
-
-   <para>
-    <function>has_function_privilege</function> checks whether a user
-    can access a function in a particular way.
-    Its argument possibilities
-    are analogous to <function>has_table_privilege</function>.
-    When specifying a function by a text string rather than by OID,
-    the allowed input is the same as for the <type>regprocedure</> data type
-    (see <xref linkend="datatype-oid">).
-    The desired access privilege type must evaluate to
-    <literal>EXECUTE</literal>.
-    An example is:
-<programlisting>
-SELECT has_function_privilege('joeuser', 'myfunc(int, text)', 'execute');
-</programlisting>
-   </para>
-
-   <para>
-    <function>has_foreign_data_wrapper_privilege</function> checks whether a user
-    can access a foreign-data wrapper in a particular way.
-    Its argument possibilities
-    are analogous to <function>has_table_privilege</function>.
-    The desired access privilege type must evaluate to
-    <literal>USAGE</literal>.
-   </para>
-
-   <para>
-    <function>has_language_privilege</function> checks whether a user
-    can access a procedural language in a particular way.
-    Its argument possibilities
-    are analogous to <function>has_table_privilege</function>.
-    The desired access privilege type must evaluate to
-    <literal>USAGE</literal>.
-   </para>
-
-   <para>
-    <function>has_schema_privilege</function> checks whether a user
-    can access a schema in a particular way.
-    Its argument possibilities
-    are analogous to <function>has_table_privilege</function>.
-    The desired access privilege type must evaluate to some combination of
-    <literal>CREATE</literal> or
-    <literal>USAGE</literal>.
-   </para>
-
-   <para>
-    <function>has_server_privilege</function> checks whether a user
-    can access a foreign server in a particular way.
-    Its argument possibilities
-    are analogous to <function>has_table_privilege</function>.
-    The desired access privilege type must evaluate to
-    <literal>USAGE</literal>.
-   </para>
-
-   <para>
-    <function>has_tablespace_privilege</function> checks whether a user
-    can access a tablespace in a particular way.
-    Its argument possibilities
-    are analogous to <function>has_table_privilege</function>.
-    The desired access privilege type must evaluate to
-    <literal>CREATE</literal>.
-   </para>
-
-   <para>
-    <function>pg_has_role</function> checks whether a user
-    can access a role in a particular way.
-    Its argument possibilities
-    are analogous to <function>has_table_privilege</function>,
-    except that <literal>public</> is not allowed as a user name.
-    The desired access privilege type must evaluate to some combination of
-    <literal>MEMBER</literal> or
-    <literal>USAGE</literal>.
-    <literal>MEMBER</literal> denotes direct or indirect membership in
-    the role (that is, the right to do <command>SET ROLE</>), while
-    <literal>USAGE</literal> denotes whether the privileges of the role
-    are immediately available without doing <command>SET ROLE</>.
-   </para>
-
-  <para>
-   <xref linkend="functions-info-schema-table"> shows functions that
-   determine whether a certain object is <firstterm>visible</> in the
-   current schema search path.
-   For example, a table is said to be visible if its
-   containing schema is in the search path and no table of the same
-   name appears earlier in the search path.  This is equivalent to the
-   statement that the table can be referenced by name without explicit
-   schema qualification.  To list the names of all visible tables:
-<programlisting>
-SELECT relname FROM pg_class WHERE pg_table_is_visible(oid);
-</programlisting>
-  </para>
-
-   <table id="functions-info-schema-table">
-    <title>Schema Visibility Inquiry Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal><function>pg_collation_is_visible(<parameter>collation_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is collation visible in search path</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_conversion_is_visible(<parameter>conversion_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is conversion visible in search path</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_function_is_visible(<parameter>function_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is function visible in search path</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_opclass_is_visible(<parameter>opclass_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is operator class visible in search path</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_operator_is_visible(<parameter>operator_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is operator visible in search path</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_table_is_visible(<parameter>table_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is table visible in search path</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_ts_config_is_visible(<parameter>config_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is text search configuration visible in search path</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_ts_dict_is_visible(<parameter>dict_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is text search dictionary visible in search path</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_ts_parser_is_visible(<parameter>parser_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is text search parser visible in search path</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_ts_template_is_visible(<parameter>template_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is text search template visible in search path</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_type_is_visible(<parameter>type_oid</parameter>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>is type (or domain) visible in search path</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm>
-    <primary>pg_collation_is_visible</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_conversion_is_visible</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_function_is_visible</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_opclass_is_visible</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_operator_is_visible</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_table_is_visible</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_ts_config_is_visible</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_ts_dict_is_visible</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_ts_parser_is_visible</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_ts_template_is_visible</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_type_is_visible</primary>
-   </indexterm>
-
-   <para>
-    Each function performs the visibility check for one type of database
-    object.  Note that <function>pg_table_is_visible</function> can also be used
-    with views, indexes and sequences; <function>pg_type_is_visible</function>
-    can also be used with domains. For functions and operators, an object in
-    the search path is visible if there is no object of the same name
-    <emphasis>and argument data type(s)</> earlier in the path.  For operator
-    classes, both name and associated index access method are considered.
-   </para>
-
-   <para>
-    All these functions require object OIDs to identify the object to be
-    checked.  If you want to test an object by name, it is convenient to use
-    the OID alias types (<type>regclass</>, <type>regtype</>,
-    <type>regprocedure</>, <type>regoperator</>, <type>regconfig</>,
-    or <type>regdictionary</>),
-    for example:
-<programlisting>
-SELECT pg_type_is_visible('myschema.widget'::regtype);
-</programlisting>
-    Note that it would not make much sense to test a non-schema-qualified
-    type name in this way &mdash; if the name can be recognized at all, it must be visible.
-   </para>
-
-<!## XC>
-&xconly;
-   <para>
-    Because value of OID is enforced unique only in each Coordinator
-    or Datanode in <productname>Postgres-XC</>, you should use these
-    functions locally, typically through <type>EXECUTE DIRECT</>
-    statement.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Because value of OID is enforced unique only in each Coordinator
-    or Datanode in <productname>Postgres-XL</>, you should use these
-    functions locally, typically through <type>EXECUTE DIRECT</>
-    statement.
-   </para>
-<!## end>
-
-   <indexterm>
-    <primary>format_type</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_describe_object</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_constraintdef</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_expr</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_functiondef</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_function_arguments</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_function_identity_arguments</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_function_result</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_indexdef</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_keywords</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_ruledef</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_serial_sequence</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_triggerdef</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_userbyid</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_get_viewdef</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_options_to_table</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_tablespace_databases</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>pg_typeof</primary>
-   </indexterm>
-
-  <para>
-   <xref linkend="functions-info-catalog-table"> lists functions that
-   extract information from the system catalogs.
-  </para>
-
-   <table id="functions-info-catalog-table">
-    <title>System Catalog Information Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal><function>format_type(<parameter>type_oid</parameter>, <parameter>typemod</>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get SQL name of a data type</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_describe_object(<parameter>catalog_id</parameter>, <parameter>object_id</parameter>, <parameter>object_sub_id</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get description of a database object</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_constraintdef(<parameter>constraint_oid</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get definition of a constraint</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_constraintdef(<parameter>constraint_oid</parameter>, <parameter>pretty_bool</>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get definition of a constraint</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_expr(<parameter>pg_node_tree</parameter>, <parameter>relation_oid</>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>decompile internal form of an expression, assuming that any Vars
-       in it refer to the relation indicated by the second parameter</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_expr(<parameter>pg_node_tree</parameter>, <parameter>relation_oid</>, <parameter>pretty_bool</>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>decompile internal form of an expression, assuming that any Vars
-       in it refer to the relation indicated by the second parameter</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_functiondef(<parameter>func_oid</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get definition of a function</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_function_arguments(<parameter>func_oid</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get argument list of function's definition (with default values)</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_function_identity_arguments(<parameter>func_oid</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get argument list to identify a function (without default values)</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_function_result(<parameter>func_oid</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get <literal>RETURNS</> clause for function</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_indexdef(<parameter>index_oid</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get <command>CREATE INDEX</> command for index</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_indexdef(<parameter>index_oid</parameter>, <parameter>column_no</>, <parameter>pretty_bool</>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get <command>CREATE INDEX</> command for index,
-       or definition of just one index column when
-       <parameter>column_no</> is not zero</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_keywords()</function></literal></entry>
-       <entry><type>setof record</type></entry>
-       <entry>get list of SQL keywords and their categories</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_ruledef(<parameter>rule_oid</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get <command>CREATE RULE</> command for rule.</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_ruledef(<parameter>rule_oid</parameter>, <parameter>pretty_bool</>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get <command>CREATE RULE</> command for rule</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_serial_sequence(<parameter>table_name</parameter>, <parameter>column_name</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get name of the sequence that a <type>serial</type> or <type>bigserial</type> column
-       uses</entry>
-      </row>
-      <row>
-       <entry><function>pg_get_triggerdef</function>(<parameter>trigger_oid</parameter>)</entry>
-       <entry><type>text</type></entry>
-       <entry>get <command>CREATE [ CONSTRAINT ] TRIGGER</> command for trigger</entry>
-      </row>
-      <row>
-       <entry><function>pg_get_triggerdef</function>(<parameter>trigger_oid</parameter>, <parameter>pretty_bool</>)</entry>
-       <entry><type>text</type></entry>
-       <entry>get <command>CREATE [ CONSTRAINT ] TRIGGER</> command for trigger</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_userbyid(<parameter>role_oid</parameter>)</function></literal></entry>
-       <entry><type>name</type></entry>
-       <entry>get role name with given OID</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_viewdef(<parameter>view_name</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get underlying <command>SELECT</command> command for view (<emphasis>deprecated</emphasis>)</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_viewdef(<parameter>view_name</parameter>, <parameter>pretty_bool</>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get underlying <command>SELECT</command> command for view (<emphasis>deprecated</emphasis>)</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_viewdef(<parameter>view_oid</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get underlying <command>SELECT</command> command for view</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_get_viewdef(<parameter>view_oid</parameter>, <parameter>pretty_bool</>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get underlying <command>SELECT</command> command for view</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_options_to_table(<parameter>reloptions</parameter>)</function></literal></entry>
-       <entry><type>setof record</type></entry>
-       <entry>get the set of storage option name/value pairs</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_tablespace_databases(<parameter>tablespace_oid</parameter>)</function></literal></entry>
-       <entry><type>setof oid</type></entry>
-       <entry>get the set of database OIDs that have objects in the tablespace</entry>
-      </row>
-      <row>
-       <entry><literal><function>pg_typeof(<parameter>any</parameter>)</function></literal></entry>
-       <entry><type>regtype</type></entry>
-       <entry>get the data type of any value</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   <function>format_type</function> returns the SQL name of a data type that
-   is identified by its type OID and possibly a type modifier.  Pass NULL
-   for the type modifier if no specific modifier is known.
-  </para>
-
-  <para>
-   <function>pg_get_keywords</function> returns a set of records describing
-   the SQL keywords recognized by the server. The <structfield>word</> column
-   contains the keyword.  The <structfield>catcode</> column contains a
-   category code: <literal>U</> for unreserved, <literal>C</> for column name,
-   <literal>T</> for type or function name, or <literal>R</> for reserved.
-   The <structfield>catdesc</> column contains a possibly-localized string
-   describing the category.
-  </para>
-
-  <para>
-   <function>pg_get_constraintdef</function>,
-   <function>pg_get_indexdef</function>, <function>pg_get_ruledef</function>,
-   and <function>pg_get_triggerdef</function>, respectively reconstruct the
-   creating command for a constraint, index, rule, or trigger. (Note that this
-   is a decompiled reconstruction, not the original text of the command.)
-   <function>pg_get_expr</function> decompiles the internal form of an
-   individual expression, such as the default value for a column.  It can be
-   useful when examining the contents of system catalogs.  If the expression
-   might contain Vars, specify the OID of the relation they refer to as the
-   second parameter; if no Vars are expected, zero is sufficient.
-   <function>pg_get_viewdef</function> reconstructs the <command>SELECT</>
-   query that defines a view. Most of these functions come in two variants,
-   one of which can optionally <quote>pretty-print</> the result.  The
-   pretty-printed format is more readable, but the default format is more
-   likely to be interpreted the same way by future versions of
-<!## PG>
-   <productname>PostgreSQL</>; avoid using pretty-printed output for dump
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</>; avoid using pretty-printed output for dump
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</>; avoid using pretty-printed output for dump
-<!## end>
-   purposes.  Passing <literal>false</> for the pretty-print parameter yields
-   the same result as the variant that does not have the parameter at all.
-  </para>
-
-  <para>
-   <function>pg_get_functiondef</> returns a complete
-   <command>CREATE OR REPLACE FUNCTION</> statement for a function.
-   <function>pg_get_function_arguments</function> returns the argument list
-   of a function, in the form it would need to appear in within
-   <command>CREATE FUNCTION</>.
-   <function>pg_get_function_result</function> similarly returns the
-   appropriate <literal>RETURNS</> clause for the function.
-   <function>pg_get_function_identity_arguments</function> returns the
-   argument list necessary to identify a function, in the form it
-   would need to appear in within <command>ALTER FUNCTION</>, for
-   instance.  This form omits default values.
-  </para>
-
-  <para>
-   <function>pg_get_serial_sequence</function> returns the name of the
-   sequence associated with a column, or NULL if no sequence is associated
-   with the column.  The first input parameter is a table name with
-   optional schema, and the second parameter is a column name.  Because
-   the first parameter is potentially a schema and table, it is not treated
-   as a double-quoted identifier, meaning it is lower cased by default,
-   while the second parameter, being just a column name, is treated as
-   double-quoted and has its case preserved.  The function returns a value
-   suitably formatted for passing to sequence functions (see <xref
-   linkend="functions-sequence">).  This association can be modified or
-   removed with <command>ALTER SEQUENCE OWNED BY</>.  (The function
-   probably should have been called
-   <function>pg_get_owned_sequence</function>; its current name reflects the fact
-   that it's typically used with <type>serial</> or <type>bigserial</>
-   columns.)
-  </para>
-
-  <para>
-   <function>pg_get_userbyid</function> extracts a role's name given
-   its OID.
-  </para>
-
-  <para>
-   <function>pg_options_to_table</function> returns the set of storage
-   option name/value pairs
-   (<literal>option_name</>/<literal>option_value</>) when passed
-   <structname>pg_class</>.<structfield>reloptions</> or
-   <structname>pg_attribute</>.<structfield>attoptions</>.
-  </para>
-
-  <para>
-   <function>pg_tablespace_databases</function> allows a tablespace to be
-   examined. It returns the set of OIDs of databases that have objects stored
-   in the tablespace. If this function returns any rows, the tablespace is not
-   empty and cannot be dropped. To display the specific objects populating the
-   tablespace, you will need to connect to the databases identified by
-   <function>pg_tablespace_databases</function> and query their
-   <structname>pg_class</> catalogs.
-  </para>
-
-  <para>
-   <function>pg_describe_object</function> returns a description of a database
-   object specified by catalog OID, object OID and a (possibly zero) sub-object ID.
-   This is useful to determine the identity of an object as stored in the
-   <structname>pg_depend</structname> catalog.
-  </para>
-
-  <para>
-   <function>pg_typeof</function> returns the OID of the data type of the
-   value that is passed to it.  This can be helpful for troubleshooting or
-   dynamically constructing SQL queries.  The function is declared as
-   returning <type>regtype</>, which is an OID alias type (see
-   <xref linkend="datatype-oid">); this means that it is the same as an
-   OID for comparison purposes but displays as a type name.  For example:
-<programlisting>
-SELECT pg_typeof(33);
-
- pg_typeof 
------------
- integer
-(1 row)
-
-SELECT typlen FROM pg_type WHERE oid = pg_typeof(33);
- typlen 
---------
-      4
-(1 row)
-</programlisting>
-  </para>
-<!## XC>
-&xconly;
-  <para>
-   Please note that OID is valid locally in each Coordinator and
-   Datanode.  You should use specific OID value in statements
-   targeted to specific Coordinator or Datanode by <type>EXECUTE
-   DIRECT</> statement.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that OID is valid locally only in each Coordinator and
-   Datanode.  You should use specific OID value in statements
-   targeted to specific Coordinator or Datanode by <type>EXECUTE
-   DIRECT</> statement.
-  </para>
-<!## end>
-
-
-   <indexterm>
-    <primary>col_description</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>obj_description</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>shobj_description</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>comment</primary>
-    <secondary sortas="database objects">about database objects</secondary>
-   </indexterm>
-
-   <para>
-    The functions shown in <xref linkend="functions-info-comment-table">
-    extract comments previously stored with the <xref linkend="sql-comment">
-    command.  A null value is returned if no
-    comment could be found for the specified parameters.
-   </para>
-
-   <table id="functions-info-comment-table">
-    <title>Comment Information Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal><function>col_description(<parameter>table_oid</parameter>, <parameter>column_number</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get comment for a table column</entry>
-      </row>
-      <row>
-       <entry><literal><function>obj_description(<parameter>object_oid</parameter>, <parameter>catalog_name</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get comment for a database object</entry>
-      </row>
-      <row>
-       <entry><literal><function>obj_description(<parameter>object_oid</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get comment for a database object (<emphasis>deprecated</emphasis>)</entry>
-      </row>
-      <row>
-       <entry><literal><function>shobj_description(<parameter>object_oid</parameter>, <parameter>catalog_name</parameter>)</function></literal></entry>
-       <entry><type>text</type></entry>
-       <entry>get comment for a shared database object</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    <function>col_description</function> returns the comment for a table
-    column, which is specified by the OID of its table and its column number.
-    (<function>obj_description</function> cannot be used for table columns
-    since columns do not have OIDs of their own.)
-   </para>
-
-   <para>
-    The two-parameter form of <function>obj_description</function> returns the
-    comment for a database object specified by its OID and the name of the
-    containing system catalog.  For example,
-    <literal>obj_description(123456,'pg_class')</literal>
-    would retrieve the comment for the table with OID 123456.
-    The one-parameter form of <function>obj_description</function> requires only
-    the object OID.  It is deprecated since there is no guarantee that
-    OIDs are unique across different system catalogs; therefore, the wrong
-    comment might be returned.
-   </para>
-
-   <para>
-    <function>shobj_description</function> is used just like
-    <function>obj_description</function> except it is used for retrieving
-    comments on shared objects.  Some system catalogs are global to all
-    databases within each cluster, and the descriptions for objects in them
-    are stored globally as well.
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    In <productname>Postgres-XC</>, OID is maintained locally in each Coordinator and Datanode.
-    If you specify specific OID value, you should do it in SQL statements targeted to specif
-    Coordinator or Datanode by <type>EXECUTE DIRECT</> statement.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    In <productname>Postgres-XL</>, OID is maintained locally in each Coordinator and Datanode.
-    If you specify specific OID value, you should do it in SQL statements targeted to a specific
-    Coordinator or Datanode by <type>EXECUTE DIRECT</> statement.
-   </para>
-<!## end>
-
-   <indexterm>
-    <primary>txid_current</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>txid_current_snapshot</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>txid_snapshot_xip</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>txid_snapshot_xmax</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>txid_snapshot_xmin</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>txid_visible_in_snapshot</primary>
-   </indexterm>
-
-   <para>
-    The functions shown in <xref linkend="functions-txid-snapshot">
-    provide server transaction information in an exportable form.  The main
-    use of these functions is to determine which transactions were committed
-    between two snapshots.
-   </para>
-
-   <table id="functions-txid-snapshot">
-    <title>Transaction IDs and Snapshots</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-
-<!## XC>
-      <row>
-       <entry><literal><function>pgxc_is_committed(transaction_id)</function></literal></entry>
-       <entry><type>bool</type></entry>
-       <entry>If given xid (gxid) is committed or aborted.  NULL indicates the status is unknown (running, not yet started, prepared, frozen, etc).</entry>
-      </row>
-<!## end>
-<!## XL>
-      <row>
-       <entry><literal><function>pgxc_is_committed(transaction_id)</function></literal></entry>
-       <entry><type>bool</type></entry>
-       <entry>If given xid (gxid) is committed or aborted.  NULL indicates the status is unknown (running, not yet started, prepared, frozen, etc).</entry>
-      </row>
-<!## end>
-
-      <row>
-       <entry><literal><function>txid_current()</function></literal></entry>
-       <entry><type>bigint</type></entry>
-       <entry>get current transaction ID</entry>
-      </row>
-      <row>
-       <entry><literal><function>txid_current_snapshot()</function></literal></entry>
-       <entry><type>txid_snapshot</type></entry>
-       <entry>get current snapshot</entry>
-      </row>
-      <row>
-       <entry><literal><function>txid_snapshot_xip(<parameter>txid_snapshot</parameter>)</function></literal></entry>
-       <entry><type>setof bigint</type></entry>
-       <entry>get in-progress transaction IDs in snapshot</entry>
-      </row>
-      <row>
-       <entry><literal><function>txid_snapshot_xmax(<parameter>txid_snapshot</parameter>)</function></literal></entry>
-       <entry><type>bigint</type></entry>
-       <entry>get <literal>xmax</literal> of snapshot</entry>
-      </row>
-      <row>
-       <entry><literal><function>txid_snapshot_xmin(<parameter>txid_snapshot</parameter>)</function></literal></entry>
-       <entry><type>bigint</type></entry>
-       <entry>get <literal>xmin</literal> of snapshot</entry>
-      </row>
-      <row>
-       <entry><literal><function>txid_visible_in_snapshot(<parameter>bigint</parameter>, <parameter>txid_snapshot</parameter>)</function></literal></entry>
-       <entry><type>boolean</type></entry>
-       <entry>is transaction ID visible in snapshot? (do not use with subtransaction ids)</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    The internal transaction ID type (<type>xid</>) is 32 bits wide and
-    wraps around every 4 billion transactions.  However, these functions
-    export a 64-bit format that is extended with an <quote>epoch</> counter
-    so it will not wrap around during the life of an installation.
-    The data type used by these functions, <type>txid_snapshot</type>,
-    stores information about transaction ID
-    visibility at a particular moment in time.  Its components are
-    described in <xref linkend="functions-txid-snapshot-parts">.
-   </para>
-
-   <table id="functions-txid-snapshot-parts">
-    <title>Snapshot Components</title>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Name</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-
-      <row>
-       <entry><type>xmin</type></entry>
-       <entry>
-         Earliest transaction ID (txid) that is still active.  All earlier
-         transactions will either be committed and visible, or rolled
-         back and dead.
-       </entry>
-      </row>
-
-      <row>
-       <entry><type>xmax</type></entry>
-       <entry>
-        First as-yet-unassigned txid.  All txids greater than or equal to this
-        are not yet started as of the time of the snapshot, and thus invisible.
-       </entry>
-      </row>
-
-      <row>
-       <entry><type>xip_list</type></entry>
-       <entry>
-        Active txids at the time of the snapshot.  The list
-        includes only those active txids between <literal>xmin</>
-        and <literal>xmax</>; there might be active txids higher
-        than <literal>xmax</>.  A txid that is <literal>xmin &lt;= txid &lt;
-        xmax</literal> and not in this list was already completed
-        at the time of the snapshot, and thus either visible or
-        dead according to its commit status.  The list does not
-        include txids of subtransactions.
-       </entry>
-      </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    <type>txid_snapshot</>'s textual representation is
-    <literal><replaceable>xmin</>:<replaceable>xmax</>:<replaceable>xip_list</></literal>.
-    For example <literal>10:20:10,14,15</literal> means
-    <literal>xmin=10, xmax=20, xip_list=10, 14, 15</literal>.
-   </para>
-  </sect1>
-
-  <sect1 id="functions-admin">
-   <title>System Administration Functions</title>
-&common;
-   <para>
-    <xref linkend="functions-admin-set-table"> shows the functions
-    available to query and alter run-time configuration parameters.
-   </para>
-
-   <table id="functions-admin-set-table">
-    <title>Configuration Settings Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <indexterm>
-         <primary>current_setting</primary>
-        </indexterm>
-        <literal><function>current_setting(<parameter>setting_name</parameter>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>get current value of setting</entry>
-      </row>
-      <row>
-       <entry>
-        <indexterm>
-         <primary>set_config</primary>
-        </indexterm>
-        <literal><function>set_config(<parameter>setting_name</parameter>,
-                             <parameter>new_value</parameter>,
-                             <parameter>is_local</parameter>)</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>set parameter and return new value</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm>
-    <primary>SET</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>SHOW</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>configuration</primary>
-    <secondary sortas="server">of the server</secondary>
-    <tertiary>functions</tertiary>
-   </indexterm>
-
-   <para>
-    The function <function>current_setting</function> yields the
-    current value of the setting <parameter>setting_name</parameter>.
-    It corresponds to the <acronym>SQL</acronym> command
-    <command>SHOW</command>.  An example:
-<programlisting>
-SELECT current_setting('datestyle');
-
- current_setting
------------------
- ISO, MDY
-(1 row)
-</programlisting>
-   </para>
-
-   <para>
-    <function>set_config</function> sets the parameter
-    <parameter>setting_name</parameter> to
-    <parameter>new_value</parameter>.  If
-    <parameter>is_local</parameter> is <literal>true</literal>, the
-    new value will only apply to the current transaction. If you want
-    the new value to apply for the current session, use
-    <literal>false</literal> instead. The function corresponds to the
-    SQL command <command>SET</command>. An example:
-<programlisting>
-SELECT set_config('log_statement_stats', 'off', false);
-
- set_config
-------------
- off
-(1 row)
-</programlisting>
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    Similar to the SET command, the set_config() function makes sure
-    that as long as the session/transaction is active, the new parameter
-    value is set across all the nodes on which the SQL queries are being run
-    as part of that particular session or transaction.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Similar to the SET command, the set_config() function makes sure
-    that as long as the session/transaction is active, the new parameter
-    value is set across all the nodes on which the SQL queries are being run
-    as part of that particular session or transaction.
-   </para>
-<!## end>
-
-   <indexterm>
-    <primary>pg_cancel_backend</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_reload_conf</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_rotate_logfile</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_terminate_backend</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>signal</primary>
-    <secondary sortas="backend">backend processes</secondary>
-   </indexterm>
-
-   <para>
-    The functions shown in <xref
-    linkend="functions-admin-signal-table"> send control signals to
-    other server processes.  Use of these functions is restricted
-    to superusers.
-   </para>
-
-   <table id="functions-admin-signal-table">
-    <title>Server Signalling Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pg_cancel_backend(<parameter>pid</parameter> <type>int</>)</function></literal>
-        </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Cancel a backend's current query</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_reload_conf()</function></literal>
-        </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Cause server processes to reload their configuration files</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_rotate_logfile()</function></literal>
-        </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Rotate server's log file</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_terminate_backend(<parameter>pid</parameter> <type>int</>)</function></literal>
-        </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Terminate a backend</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    Each of these functions returns <literal>true</literal> if
-    successful and <literal>false</literal> otherwise.
-   </para>
-
-   <para>
-    <function>pg_cancel_backend</> and <function>pg_terminate_backend</>
-    send signals (<systemitem>SIGINT</> or <systemitem>SIGTERM</>
-    respectively) to backend processes identified by process ID.
-    The process ID of an active backend can be found from
-    the <structfield>procpid</structfield> column of the
-    <structname>pg_stat_activity</structname> view, or by listing the
-    <command>postgres</command> processes on the server (using
-    <application>ps</> on Unix or the <application>Task
-    Manager</> on <productname>Windows</>).
-   </para>
-
-   <para>
-    <function>pg_reload_conf</> sends a <systemitem>SIGHUP</> signal
-    to the server, causing configuration files
-    to be reloaded by all server processes.
-   </para>
-
-   <para>
-    <function>pg_rotate_logfile</> signals the log-file manager to switch
-    to a new output file immediately.  This works only when the built-in
-    log collector is running, since otherwise there is no log-file manager
-    subprocess.
-   </para>
-
-<!## XC>
-&xconly;
-   <para>
-    Please note that these functions works just locally.  To issue
-    these functions to another Coordinators or Datanodes, you should
-    issue these functions through <type>EXECUTE DIRECT</> statement.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Please note that these functions works just locally.  To issue
-    these functions to another Coordinators or Datanodes, you should
-    issue these functions through <type>EXECUTE DIRECT</> statement.
-   </para>
-<!## end>
-
-   <indexterm>
-    <primary>backup</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_create_restore_point</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_current_xlog_insert_location</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_current_xlog_location</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_start_backup</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_stop_backup</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_switch_xlog</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_xlogfile_name</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_xlogfile_name_offset</primary>
-   </indexterm>
-
-   <para>
-    The functions shown in <xref
-    linkend="functions-admin-backup-table"> assist in making on-line backups.
-    These functions cannot be executed during recovery.
-   </para>
-
-   <table id="functions-admin-backup-table">
-    <title>Backup Control Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pg_create_restore_point(<parameter>name</> <type>text</>)</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>Create a named point for performing restore (restricted to superusers)</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_current_xlog_insert_location()</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>Get current transaction log insert location</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_current_xlog_location()</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>Get current transaction log write location</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_start_backup(<parameter>label</> <type>text</> <optional>, <parameter>fast</> <type>boolean</> </optional>)</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>Prepare for performing on-line backup (restricted to superusers or replication roles)</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_stop_backup()</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>Finish performing on-line backup (restricted to superusers or replication roles)</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_switch_xlog()</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>Force switch to a new transaction log file (restricted to superusers)</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_xlogfile_name(<parameter>location</> <type>text</>)</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>Convert transaction log location string to file name</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_xlogfile_name_offset(<parameter>location</> <type>text</>)</function></literal>
-        </entry>
-       <entry><type>text</>, <type>integer</></entry>
-       <entry>Convert transaction log location string to file name and decimal byte offset within file</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    <function>pg_start_backup</> accepts an
-    arbitrary user-defined label for the backup.  (Typically this would be
-    the name under which the backup dump file will be stored.)  The function
-    writes a backup label file (<filename>backup_label</>) into the
-    database cluster's data directory, performs a checkpoint,
-    and then returns the backup's starting transaction log location as text.
-    The user can ignore this result value, but it is
-    provided in case it is useful.
-<programlisting>
-postgres=# select pg_start_backup('label_goes_here');
- pg_start_backup
------------------
- 0/D4445B8
-(1 row)
-</programlisting>
-    There is an optional second parameter of type <type>boolean</type>.  If <literal>true</>,
-    it specifies executing <function>pg_start_backup</> as quickly as
-    possible.  This forces an immediate checkpoint which will cause a
-    spike in I/O operations, slowing any concurrently executing queries.
-   </para>
-
-   <para>
-    <function>pg_stop_backup</> removes the label file created by
-    <function>pg_start_backup</>, and creates a backup history file in
-    the transaction log archive area.  The history file includes the label given to
-    <function>pg_start_backup</>, the starting and ending transaction log locations for
-    the backup, and the starting and ending times of the backup.  The return
-    value is the backup's ending transaction log location (which again
-    can be ignored).  After recording the ending location, the current
-    transaction log insertion
-    point is automatically advanced to the next transaction log file, so that the
-    ending transaction log file can be archived immediately to complete the backup.
-   </para>
-
-   <para>
-    <function>pg_switch_xlog</> moves to the next transaction log file, allowing the
-    current file to be archived (assuming you are using continuous archiving).
-    The return value is the ending transaction log location + 1 within the just-completed transaction log file.
-    If there has been no transaction log activity since the last transaction log switch,
-    <function>pg_switch_xlog</> does nothing and returns the start location
-    of the transaction log file currently in use.
-   </para>
-
-   <para>
-    <function>pg_create_restore_point</> creates a named transaction log
-    record that can be used as recovery target, and returns the corresponding
-    transaction log location.  The given name can then be used with
-    <xref linkend="recovery-target-name"> to specify the point up to which
-    recovery will proceed.  Avoid creating multiple restore points with the
-    same name, since recovery will stop at the first one whose name matches
-    the recovery target.
-   </para>
-
-   <para>
-    <function>pg_current_xlog_location</> displays the current transaction log write
-    location in the same format used by the above functions.  Similarly,
-    <function>pg_current_xlog_insert_location</> displays the current transaction log
-    insertion point.  The insertion point is the <quote>logical</> end
-    of the transaction log
-    at any instant, while the write location is the end of what has actually
-    been written out from the server's internal buffers.  The write location
-    is the end of what can be examined from outside the server, and is usually
-    what you want if you are interested in archiving partially-complete transaction log
-    files.  The insertion point is made available primarily for server
-    debugging purposes.  These are both read-only operations and do not
-    require superuser permissions.
-   </para>
-
-   <para>
-    You can use <function>pg_xlogfile_name_offset</> to extract the
-    corresponding transaction log file name and byte offset from the results of any of the
-    above functions.  For example:
-<programlisting>
-postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
-        file_name         | file_offset 
---------------------------+-------------
- 00000001000000000000000D |     4039624
-(1 row)
-</programlisting>
-    Similarly, <function>pg_xlogfile_name</> extracts just the transaction log file name.
-    When the given transaction log location is exactly at a transaction log file boundary, both
-    these functions return the name of the preceding transaction log file.
-    This is usually the desired behavior for managing transaction log archiving
-    behavior, since the preceding file is the last one that currently
-    needs to be archived.
-   </para>
-
-
-   <para>
-    For details about proper usage of these functions, see
-    <xref linkend="continuous-archiving">.
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    Please note that these functions works just locally.  To issue
-    these functions to another Coordinators or Datanodes, you should
-    issue these functions through <type>EXECUTE DIRECT</> statement.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Please note that these functions works just locally.  To issue
-    these functions to another Coordinators or Datanodes, you should
-    issue these functions through <type>EXECUTE DIRECT</> statement.
-   </para>
-<!## end>
-
-   <indexterm>
-    <primary>pg_is_in_recovery</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_last_xlog_receive_location</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_last_xlog_replay_location</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_last_xact_replay_timestamp</primary>
-   </indexterm>
-
-   <para>
-    The functions shown in <xref
-    linkend="functions-recovery-info-table"> provide information
-    about the current status of the standby.
-    These functions may be executed during both recovery and in normal running.
-   </para>
-
-   <table id="functions-recovery-info-table">
-    <title>Recovery Information Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pg_is_in_recovery()</function></literal>
-        </entry>
-       <entry><type>bool</type></entry>
-       <entry>True if recovery is still in progress.
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_last_xlog_receive_location()</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>Get last transaction log location received and synced to disk by
-        streaming replication. While streaming replication is in progress
-        this will increase monotonically. If recovery has completed this will
-        remain static at
-        the value of the last WAL record received and synced to disk during
-        recovery. If streaming replication is disabled, or if it has not yet
-        started, the function returns NULL.
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_last_xlog_replay_location()</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>Get last transaction log location replayed during recovery.
-        If recovery is still in progress this will increase monotonically.
-        If recovery has completed then this value will remain static at
-        the value of the last WAL record applied during that recovery.
-        When the server has been started normally without recovery
-        the function returns NULL.
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_last_xact_replay_timestamp()</function></literal>
-        </entry>
-       <entry><type>timestamp with time zone</type></entry>
-       <entry>Get time stamp of last transaction replayed during recovery.
-        This is the time at which the commit or abort WAL record for that
-        transaction was generated on the primary.
-        If no transactions have been replayed during recovery, this function
-        returns NULL.  Otherwise, if recovery is still in progress this will
-        increase monotonically.  If recovery has completed then this value will
-        remain static at the value of the last transaction applied during that
-        recovery.  When the server has been started normally without recovery
-        the function returns NULL.
-       </entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm>
-    <primary>pg_is_xlog_replay_paused</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_xlog_replay_pause</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_xlog_replay_resume</primary>
-   </indexterm>
-
-   <para>
-    The functions shown in <xref
-    linkend="functions-recovery-control-table"> control the progress of recovery.
-    These functions may be executed only during recovery.
-   </para>
-
-   <table id="functions-recovery-control-table">
-    <title>Recovery Control Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pg_is_xlog_replay_paused()</function></literal>
-        </entry>
-       <entry><type>bool</type></entry>
-       <entry>True if recovery is paused.
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_xlog_replay_pause()</function></literal>
-        </entry>
-       <entry><type>void</type></entry>
-       <entry>Pauses recovery immediately.
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_xlog_replay_resume()</function></literal>
-        </entry>
-       <entry><type>void</type></entry>
-       <entry>Restarts recovery if it was paused.
-       </entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-<!## XC>
-&xconly;
-   <para>
-    Please note that these functions works just locally.  To issue
-    these functions to another Coordinators or Datanodes, you should
-    issue these functions through <type>EXECUTE DIRECT</> statement.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Please note that these functions works just locally.  To issue
-    these functions to another Coordinators or Datanodes, you should
-    issue these functions through <type>EXECUTE DIRECT</> statement.
-   </para>
-<!## end>
-
-   <para>
-    While recovery is paused no further database changes are applied.
-    If in hot standby, all new queries will see the same consistent snapshot
-    of the database, and no further query conflicts will be generated until
-    recovery is resumed.
-   </para>
-
-   <para>
-    If streaming replication is disabled, the paused state may continue
-    indefinitely without problem. While streaming replication is in
-    progress WAL records will continue to be received, which will
-    eventually fill available disk space, depending upon the duration of
-    the pause, the rate of WAL generation and available disk space.
-   </para>
-
-   <para>
-    The functions shown in <xref linkend="functions-admin-dbsize"> calculate
-    the disk space usage of database objects.
-   </para>
-
-   <indexterm>
-    <primary>pg_column_size</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_database_size</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_indexes_size</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_relation_size</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_size_pretty</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_table_size</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_tablespace_size</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_total_relation_size</primary>
-   </indexterm>
-
-   <table id="functions-admin-dbsize">
-    <title>Database Object Size Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal><function>pg_column_size(<type>any</type>)</function></literal></entry>
-       <entry><type>int</type></entry>
-       <entry>Number of bytes used to store a particular value (possibly compressed)</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_database_size(<type>oid</type>)</function></literal>
-        </entry>
-       <entry><type>bigint</type></entry>
-       <entry>Disk space used by the database with the specified OID</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_database_size(<type>name</type>)</function></literal>
-        </entry>
-       <entry><type>bigint</type></entry>
-       <entry>Disk space used by the database with the specified name</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_indexes_size(<type>regclass</type>)</function></literal>
-        </entry>
-       <entry><type>bigint</type></entry>
-       <entry>
-        Total disk space used by indexes attached to the specified table
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_relation_size(<parameter>relation</parameter> <type>regclass</type>, <parameter>fork</parameter> <type>text</type>)</function></literal>
-        </entry>
-       <entry><type>bigint</type></entry>
-       <entry>
-        Disk space used by the specified fork (<literal>'main'</literal>,
-        <literal>'fsm'</literal> or <literal>'vm'</>)
-        of the specified table or index
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_relation_size(<parameter>relation</parameter> <type>regclass</type>)</function></literal>
-        </entry>
-       <entry><type>bigint</type></entry>
-       <entry>
-        Shorthand for <literal>pg_relation_size(..., 'main')</literal>
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_size_pretty(<type>bigint</type>)</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>Converts a size in bytes into a human-readable format with size units</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_table_size(<type>regclass</type>)</function></literal>
-        </entry>
-       <entry><type>bigint</type></entry>
-       <entry>
-        Disk space used by the specified table, excluding indexes
-        (but including TOAST, free space map, and visibility map)
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_tablespace_size(<type>oid</type>)</function></literal>
-        </entry>
-       <entry><type>bigint</type></entry>
-       <entry>Disk space used by the tablespace with the specified OID</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_tablespace_size(<type>name</type>)</function></literal>
-        </entry>
-       <entry><type>bigint</type></entry>
-       <entry>Disk space used by the tablespace with the specified name</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_total_relation_size(<type>regclass</type>)</function></literal>
-        </entry>
-       <entry><type>bigint</type></entry>
-       <entry>
-        Total disk space used by the specified table,
-        including all indexes and <acronym>TOAST</> data
-       </entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    <function>pg_column_size</> shows the space used to store any individual
-    data value.
-   </para>
-
-   <para>
-    <function>pg_total_relation_size</> accepts the OID or name of a
-    table or toast table, and returns the total on-disk space used for
-    that table, including all associated indexes.  This function is
-    equivalent to <function>pg_table_size</function>
-    <literal>+</> <function>pg_indexes_size</function>.
-   </para>
-
-   <para>
-    <function>pg_table_size</> accepts the OID or name of a table and
-    returns the disk space needed for that table, exclusive of indexes.
-    (TOAST space, free space map, and visibility map are included.)
-   </para>
-
-   <para>
-    <function>pg_indexes_size</> accepts the OID or name of a table and
-    returns the total disk space used by all the indexes attached to that
-    table.
-   </para>
-
-   <para>
-    <function>pg_database_size</function> and <function>pg_tablespace_size</>
-    accept the OID or name of a database or tablespace, and return the total
-    disk space used therein.
-   </para>
-
-   <para>
-    <function>pg_relation_size</> accepts the OID or name of a table, index or
-    toast table, and returns the on-disk size in bytes. Specifying
-    <literal>'main'</literal> or leaving out the second argument returns the
-    size of the main data fork of the relation. Specifying
-    <literal>'fsm'</literal> returns the size of the
-    Free Space Map (see <xref linkend="storage-fsm">) associated with the
-    relation. Specifying <literal>'vm'</literal> returns the size of the
-    Visibility Map (see <xref linkend="storage-vm">) associated with the
-    relation.  Note that this function shows the size of only one fork;
-    for most purposes it is more convenient to use the higher-level
-    functions <function>pg_total_relation_size</> or
-    <function>pg_table_size</>.
-   </para>
-
-   <para>
-    <function>pg_size_pretty</> can be used to format the result of one of
-    the other functions in a human-readable way, using kB, MB, GB or TB as
-    appropriate.
-   </para>
-
-   <para>
-    The functions above that operate on tables or indexes accept a
-    <type>regclass</> argument, which is simply the OID of the table or index
-    in the <structname>pg_class</> system catalog.  You do not have to look up
-    the OID by hand, however, since the <type>regclass</> data type's input
-    converter will do the work for you.  Just write the table name enclosed in
-    single quotes so that it looks like a literal constant.  For compatibility
-    with the handling of ordinary <acronym>SQL</acronym> names, the string
-    will be converted to lower case unless it contains double quotes around
-    the table name.
-   </para>
-
-<!## XC>
-&xconly;
-   <para>
-    The object size functions pg_database_size, pg_indexes_size, pg_relation_size,
-    pg_table_size, and pg_total_relation_size return the cumulative size
-    from all the Datanodes. For e.g., pg_relation_size returns the sum of disk
-    space used up by the specified fork at all the Datanodes where the table is
-    distributed or replicated. If the table is replicated on 3 tables, the size
-    will be  3 times that of individual nodes. If you need to retrieve the local
-    results from a particular Coordinator or Datanode, you should issue these
-    function calls explicitly through <type>EXECUTE DIRECT</> statement. All other
-    system functions run locally at the Coordinator, unless explicitly specified
-    otherwise in this document.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    The object size functions pg_database_size, pg_indexes_size, pg_relation_size,
-    pg_table_size, and pg_total_relation_size return the cumulative size
-    from all the Datanodes. For e.g., pg_relation_size returns the sum of disk
-    space used up by the specified fork at all the Datanodes where the table is
-    distributed or replicated. If the table is replicated on 3 tables, the size
-    will be  3 times that of individual nodes. If you need to retrieve the local
-    results from a particular Coordinator or Datanode, you should issue these
-    function calls explicitly through <type>EXECUTE DIRECT</> statement. All other
-    system functions run locally at the Coordinator, unless explicitly specified
-    otherwise in this document.
-   </para>
-<!## end>
-
-   <para>
-    The functions shown in <xref linkend="functions-admin-dblocation"> assist
-    in identifying the specific disk files associated with database objects.
-   </para>
-
-   <indexterm>
-    <primary>pg_relation_filenode</primary>
-   </indexterm>
-   <indexterm>
-    <primary>pg_relation_filepath</primary>
-   </indexterm>
-
-   <table id="functions-admin-dblocation">
-    <title>Database Object Location Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pg_relation_filenode(<parameter>relation</parameter> <type>regclass</type>)</function></literal>
-        </entry>
-       <entry><type>oid</type></entry>
-       <entry>
-        Filenode number of the specified relation
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_relation_filepath(<parameter>relation</parameter> <type>regclass</type>)</function></literal>
-        </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        File path name of the specified relation
-       </entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    <function>pg_relation_filenode</> accepts the OID or name of a table,
-    index, sequence, or toast table, and returns the <quote>filenode</> number
-    currently assigned to it.  The filenode is the base component of the file
-    name(s) used for the relation (see <xref linkend="storage-file-layout">
-    for more information).  For most tables the result is the same as
-    <structname>pg_class</>.<structfield>relfilenode</>, but for certain
-    system catalogs <structfield>relfilenode</> is zero and this function must
-    be used to get the correct value.  The function returns NULL if passed
-    a relation that does not have storage, such as a view.
-   </para>
-
-   <para>
-    <function>pg_relation_filepath</> is similar to
-    <function>pg_relation_filenode</>, but it returns the entire file path name
-    (relative to the database cluster's data directory <varname>PGDATA</>) of
-    the relation.
-   </para>
-
-<!## XC>
-&xconly;
-   <para>
-    Please note that these functions works just locally.  To issue
-    these functions to another Coordinators or Datanodes, you should
-    issue these functions through <type>EXECUTE DIRECT</> statement.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Please note that these functions works just locally.  To issue
-    these functions to another Coordinators or Datanodes, you should
-    issue these functions through <type>EXECUTE DIRECT</> statement.
-   </para>
-<!## end>
-
-&common;
-   <para>
-    The functions shown in <xref
-    linkend="functions-admin-genfile"> provide native access to
-    files on the machine hosting the server. Only files within the
-    database cluster directory and the <varname>log_directory</> can be
-    accessed.  Use a relative path for files in the cluster directory,
-    and a path matching the <varname>log_directory</> configuration setting
-    for log files.  Use of these functions is restricted to superusers.
-   </para>
-
-   <table id="functions-admin-genfile">
-    <title>Generic File Access Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pg_ls_dir(<parameter>dirname</> <type>text</>)</function></literal>
-       </entry>
-       <entry><type>setof text</type></entry>
-       <entry>List the contents of a directory</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_read_file(<parameter>filename</> <type>text</> [, <parameter>offset</> <type>bigint</>, <parameter>length</> <type>bigint</>])</function></literal>
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>Return the contents of a text file</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_read_binary_file(<parameter>filename</> <type>text</> [, <parameter>offset</> <type>bigint</>, <parameter>length</> <type>bigint</>])</function></literal>
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>Return the contents of a file</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_stat_file(<parameter>filename</> <type>text</>)</function></literal>
-       </entry>
-       <entry><type>record</type></entry>
-       <entry>Return information about a file</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm>
-    <primary>pg_ls_dir</primary>
-   </indexterm>
-   <para>
-    <function>pg_ls_dir</> returns all the names in the specified
-    directory, except the special entries <quote><literal>.</></> and
-    <quote><literal>..</></>.
-   </para>
-
-   <indexterm>
-    <primary>pg_read_file</primary>
-   </indexterm>
-   <para>
-    <function>pg_read_file</> returns part of a text file, starting
-    at the given <parameter>offset</>, returning at most <parameter>length</>
-    bytes (less if the end of file is reached first).  If <parameter>offset</>
-    is negative, it is relative to the end of the file.
-    If <parameter>offset</> and <parameter>length</> are omitted, the entire
-    file is returned.  The bytes read from the file are interpreted as a string
-    in the server encoding; an error is thrown if they are not valid in that
-    encoding.
-   </para>
-
-   <indexterm>
-    <primary>pg_read_binary_file</primary>
-   </indexterm>
-   <para>
-    <function>pg_read_binary_file</> is similar to
-    <function>pg_read_file</>, except that the result is a <type>bytea</type> value;
-    accordingly, no encoding checks are performed.
-    In combination with the <function>convert_from</> function, this function
-    can be used to read a file in a specified encoding:
-<programlisting>
-SELECT convert_from(pg_read_binary_file('file_in_utf8.txt'), 'UTF8');
-</programlisting>
-   </para>
-
-   <indexterm>
-    <primary>pg_stat_file</primary>
-   </indexterm>
-   <para>
-    <function>pg_stat_file</> returns a record containing the file
-    size, last accessed time stamp, last modified time stamp,
-    last file status change time stamp (Unix platforms only),
-    file creation time stamp (Windows only), and a <type>boolean</type>
-    indicating if it is a directory.  Typical usages include:
-<programlisting>
-SELECT * FROM pg_stat_file('filename');
-SELECT (pg_stat_file('filename')).modification;
-</programlisting>
-   </para>
-
-   <para>
-    The functions shown in <xref linkend="functions-advisory-locks"> manage
-    advisory locks.  For details about proper use of these functions, see
-    <xref linkend="advisory-locks">.
-   </para>
-
-   <table id="functions-advisory-locks">
-    <title>Advisory Lock Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_lock(<parameter>key</> <type>bigint</>)</function></literal>
-       </entry>
-       <entry><type>void</type></entry>
-       <entry>Obtain exclusive session level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_lock(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</function></literal>
-       </entry>
-       <entry><type>void</type></entry>
-       <entry>Obtain exclusive session level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_lock_shared(<parameter>key</> <type>bigint</>)</function></literal>
-       </entry>
-       <entry><type>void</type></entry>
-       <entry>Obtain shared session level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_lock_shared(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</function></literal>
-       </entry>
-       <entry><type>void</type></entry>
-       <entry>Obtain shared session level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_unlock(<parameter>key</> <type>bigint</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Release an exclusive session level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_unlock(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Release an exclusive session level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_unlock_all()</function></literal>
-       </entry>
-       <entry><type>void</type></entry>
-       <entry>Release all session level advisory locks held by the current session</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_unlock_shared(<parameter>key</> <type>bigint</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Release a shared session level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_unlock_shared(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Release a shared session level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_xact_lock(<parameter>key</> <type>bigint</>)</function></literal>
-       </entry>
-       <entry><type>void</type></entry>
-       <entry>Obtain exclusive transaction level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_xact_lock(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</function></literal>
-       </entry>
-       <entry><type>void</type></entry>
-       <entry>Obtain exclusive transaction level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_xact_lock_shared(<parameter>key</> <type>bigint</>)</function></literal>
-       </entry>
-       <entry><type>void</type></entry>
-       <entry>Obtain shared transaction level advisory lock</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_advisory_xact_lock_shared(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</function></literal>
-       </entry>
-       <entry><type>void</type></entry>
-       <entry>Obtain shared advisory lock for the current transaction</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_try_advisory_lock(<parameter>key</> <type>bigint</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Obtain exclusive session level advisory lock if available</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_try_advisory_lock(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Obtain exclusive session level advisory lock if available</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_try_advisory_lock_shared(<parameter>key</> <type>bigint</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Obtain shared session level advisory lock if available</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_try_advisory_lock_shared(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Obtain shared session level advisory lock if available</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_try_advisory_xact_lock(<parameter>key</> <type>bigint</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Obtain exclusive transaction level advisory lock if available</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_try_advisory_xact_lock(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Obtain exclusive transaction level advisory lock if available</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_try_advisory_xact_lock_shared(<parameter>key</> <type>bigint</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Obtain shared transaction level advisory lock if available</entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pg_try_advisory_xact_lock_shared(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Obtain shared transaction level advisory lock if available</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm>
-    <primary>pg_advisory_lock</primary>
-   </indexterm>
-   <para>
-    <function>pg_advisory_lock</> locks an application-defined resource,
-    which can be identified either by a single 64-bit key value or two
-    32-bit key values (note that these two key spaces do not overlap).
-    The key type is specified in <literal>pg_locks.objid</>.  If
-    another session already holds a lock on the same resource, the
-    function will wait until the resource becomes available.  The lock
-    is exclusive.  Multiple lock requests stack, so that if the same resource
-    is locked three times it must be also unlocked three times to be
-    released for other sessions' use.
-   </para>
-
-   <indexterm>
-    <primary>pg_advisory_lock_shared</primary>
-   </indexterm>
-   <para>
-    <function>pg_advisory_lock_shared</> works the same as
-    <function>pg_advisory_lock</>,
-    except the lock can be shared with other sessions requesting shared locks.
-    Only would-be exclusive lockers are locked out.
-   </para>
-
-   <indexterm>
-    <primary>pg_try_advisory_lock</primary>
-   </indexterm>
-   <para>
-    <function>pg_try_advisory_lock</> is similar to
-    <function>pg_advisory_lock</>, except the function will not wait for the
-    lock to become available.  It will either obtain the lock immediately and
-    return <literal>true</>, or return <literal>false</> if the lock cannot be
-    acquired immediately.
-   </para>
-
-   <indexterm>
-    <primary>pg_try_advisory_lock_shared</primary>
-   </indexterm>
-   <para>
-    <function>pg_try_advisory_lock_shared</> works the same as
-    <function>pg_try_advisory_lock</>, except it attempts to acquire
-    a shared rather than an exclusive lock.
-   </para>
-
-   <indexterm>
-    <primary>pg_advisory_xact_lock</primary>
-   </indexterm>
-   <para>
-    <function>pg_advisory_xact_lock</> works the same as
-    <function>pg_advisory_lock</>, expect the lock is automatically released
-    at the end of the current transaction and can not be released explicitly.
-   </para>
-
-   <indexterm>
-    <primary>pg_advisory_xact_lock_shared</primary>
-   </indexterm>
-   <para>
-    <function>pg_advisory_xact_lock_shared</> works the same as
-    <function>pg_advisory_lock_shared</>, expect the lock is automatically released
-    at the end of the current transaction and can not be released explicitly.
-   </para>
-
-   <indexterm>
-    <primary>pg_try_advisory_xact_lock</primary>
-   </indexterm>
-   <para>
-    <function>pg_try_advisory_xact_lock</> works the same as
-    <function>pg_try_advisory_lock</>, expect the lock, if acquired,
-    is automatically released at the end of the current transaction and
-    can not be released explicitly.
-   </para>
-
-   <indexterm>
-    <primary>pg_try_advisory_xact_lock_shared</primary>
-   </indexterm>
-   <para>
-    <function>pg_try_advisory_xact_lock_shared</> works the same as
-    <function>pg_try_advisory_lock_shared</>, expect the lock, if acquired,
-    is automatically released at the end of the current transaction and
-    can not be released explicitly.
-   </para>
-
-   <indexterm>
-    <primary>pg_advisory_unlock</primary>
-   </indexterm>
-   <para>
-    <function>pg_advisory_unlock</> will release a previously-acquired
-    exclusive session level advisory lock.  It
-    returns <literal>true</> if the lock is successfully released.
-    If the lock was not held, it will return <literal>false</>,
-    and in addition, an SQL warning will be raised by the server.
-   </para>
-
-   <indexterm>
-    <primary>pg_advisory_unlock_shared</primary>
-   </indexterm>
-   <para>
-    <function>pg_advisory_unlock_shared</> works the same as
-    <function>pg_advisory_unlock</>,
-    except it releases a shared session level advisory lock.
-   </para>
-
-   <indexterm>
-    <primary>pg_advisory_unlock_all</primary>
-   </indexterm>
-   <para>
-    <function>pg_advisory_unlock_all</> will release all session level advisory
-    locks held by the current session.  (This function is implicitly invoked
-    at session end, even if the client disconnects ungracefully.)
-   </para>
-
-<!## XC>
-&xconly;
-   <para>
-    The advisory lock functions are aware of the Postgres XC cluster. Hence,
-    if you use a function like pg_advisory_lock() from a particular Coordinator,
-	the resource will be locked across the complete cluster, so another
-	application calling the same function from a different Coordinator will see
-	this lock, and will wait on the resource until the lock is released.
-	This applies to both transaction and session level advisory locks.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    The advisory lock functions are aware of the Postgres XL cluster. Hence,
-    if you use a function like pg_advisory_lock() from a particular Coordinator,
-	the resource will be locked across the complete cluster, so another
-	application calling the same function from a different Coordinator will see
-	this lock, and will wait on the resource until the lock is released.
-	This applies to both transaction and session level advisory locks.
-   </para>
-<!## end>
-
-<!## XC>
-&xconly;
-   <para>
-    The functions shown in <xref linkend="functions-pgxc-pooler"> manage
-    Postgres-XC pooler.  For details about Postgres-XC pooler, see
-    <xref linkend="xc-overview-pooler">.
-   </para>
-   <table id="functions-pgxc-pooler">
-    <title>Postgres-XC pooler functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pgxc_pool_check()</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Check if connection data cached in pooler is consistent with
-              <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pgxc_pool_reload()</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Reload connection data cached in pooler and reload sessions in server</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm>
-    <primary>pgxc_pool_check</primary>
-   </indexterm>
-   <para>
-    <function>pgxc_pool_check</> verifies if connection data cached in Postgres-XC pooler
-    is consistent with <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>
-    catalog. Data checked for consistency is Node Oid (<literal><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.oid</literal>),
-    node port (<literal><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.node_port</literal>)
-    and node host (<literal><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.node_host</literal>).
-   </para>
-   <indexterm>
-    <primary>pgxc_pool_reload</primary>
-   </indexterm>
-   <para>
-    <function>pgxc_pool_reload</> reloads connection data cached in pooler from
-    <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link> catalog
-    and reloads all the information info cached in pooler. All the active transactions
-    are aborted and all existing pooler connections are dropped. This results in having
-    all the temporary and prepared objects dropped on remote and local node for session.
-   </para>
-
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    The functions shown in <xref linkend="functions-pgxc-pooler"> manage
-    Postgres-XL pooler.  For details about the Postgres-XL pooler, see
-    <xref linkend="xc-overview-pooler">.
-   </para>
-   <table id="functions-pgxc-pooler">
-    <title>Postgres-XL pooler functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pgxc_pool_check()</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Check if connection data cached in pooler is consistent with
-              <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.
-       </entry>
-      </row>
-      <row>
-       <entry>
-        <literal><function>pgxc_pool_reload()</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Reload connection data cached in pooler and reload sessions in server</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm>
-    <primary>pgxc_pool_check</primary>
-   </indexterm>
-   <para>
-    <function>pgxc_pool_check</> verifies if connection data cached in Postgres-XL pooler
-    is consistent with <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>
-    catalog. Data checked for consistency is Node Oid (<literal><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.oid</literal>),
-    node port (<literal><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.node_port</literal>)
-    and node host (<literal><link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.node_host</literal>).
-   </para>
-   <indexterm>
-    <primary>pgxc_pool_reload</primary>
-   </indexterm>
-   <para>
-    <function>pgxc_pool_reload</> reloads connection data cached in pooler from
-    <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link> catalog
-    and reloads all the information info cached in pooler. All the active transactions
-    are aborted and all existing pooler connections are dropped. This results in having
-    all the temporary and prepared objects dropped on remote and local node for session.
-   </para>
-
-<!## end>
-
-
-
-
-<!## XC>
-&xconly;
-   <para>
-    The functions shown in <xref linkend="functions-pgxc-add-new-node"> manage
-    addition of a new node to Postgres-XC cluster.
-   </para>
-   <table id="functions-pgxc-add-new-node">
-    <title>Postgres-XC functions to manage addition of a new node</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pgxc_lock_for_backup()</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Locks the cluster for taking backup that would be restored on the new node to be added.
-       </entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm>
-    <primary>pgxc_lock_for_backup</primary>
-   </indexterm>
-   <para>
-    <function>pgxc_lock_for_backup</> locks the cluster for taking backup using <application>pg_dump/pg_dumpall</application>.
-    Locking means that we disallow the statemets that change the portions of the catalog which are
-    backed up by <application>pg_dump/pg_dumpall</application>. When locked only the following utility statemets are allowed.
-    Please note that this function does not impact SELECTs or DMLs.
-   </para>
-
-   <table id="utility-statements-allowed-while-locked">
-    <title>Utility statements allowed while the cluster is locked for backup</title>
-    <tgroup cols="1">
-     <thead>
-      <row><entry>Statement</entry>
-      </row>
-     </thead>
-
-     <tbody>
-
-
-      <row>
-       <entry>
-        <literal><command>EXECUTE</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CREATE NODE</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>START TRANSACTION</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>BEGIN</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>COMMIT</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>ROLLBACK</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>PREPARE TRANSACTION</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>COMMIT PREPARED</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>ROLLBACK PREPARED</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>DECLARE CURSOR</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CLOSE CURSOR</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>FETCH</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>TRUNCATE</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>COPY</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>PREPARE</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>DEALLOCATE</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>DO</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>NOTIFY</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>LISTEN</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>UNLISTEN</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>LOAD</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CLUSTER</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>VACUUM</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>EXPLAIN</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>SET</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>SHOW</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>DISCARD</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>LOCK</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>SET CONSTRAINTS</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CHECKPOINT</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CREATE BARRIER</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>REINDEX</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CLEAN CONNECTION</command></literal>
-       </entry>
-      </row>
-
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-   To lock the cluster for backup while adding a new node <productname>Postgres-XC</productname> uses advisory locks.
-   Every time a disallowed statement is issued the system tries to acquire a transaction
-   level advisory lock in shared mode and the lock is released when
-   the DDL or the transaction issuing the DDL ends. The function <function>pgxc_lock_for_backup</>
-   tries to acquire the same advisory lock in exclusive mode at session level. It is therefore necessary
-   to keep the session issuing <function>pgxc_lock_for_backup</> alive as long as the issuer wants
-   the system to keep the lock.
-   <productname>Postgres-XC</productname> uses the key pair (0xFFFF, 0xFFFF) as object ID while using
-   advisory lock for backup.
-   The function fails to acquire the lock if any one of the following is true:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       The caller of the function is not a superuser.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       There are some uncommitted prepared transactions, because they might
-       contain any utility statement belonging to the disallowed group.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The lock is already held by an uncommitted transaction that has issued
-       a utility statement belonging to the disallowed group.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The lock is already held by a previous call to the same function
-       and current request is being issued from a different session.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    The functions shown in <xref linkend="functions-pgxc-add-new-node"> manage
-    addition of a new node to Postgres-XL cluster.
-   </para>
-   <table id="functions-pgxc-add-new-node">
-    <title>Postgres-XL functions to manage addition of a new node</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>
-        <literal><function>pgxc_lock_for_backup()</function></literal>
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>Locks the cluster for taking backup that would be restored on the new node to be added.
-       </entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm>
-    <primary>pgxc_lock_for_backup</primary>
-   </indexterm>
-   <para>
-    <function>pgxc_lock_for_backup</> locks the cluster for taking backup using <application>pg_dump/pg_dumpall</application>.
-    Locking means that we disallow the statemets that change the portions of the catalog which are
-    backed up by <application>pg_dump/pg_dumpall</application>. When locked only the following utility statemets are allowed.
-    Please note that this function does not impact SELECTs or DMLs.
-   </para>
-
-   <table id="utility-statements-allowed-while-locked">
-    <title>Utility statements allowed while the cluster is locked for backup</title>
-    <tgroup cols="1">
-     <thead>
-      <row><entry>Statement</entry>
-      </row>
-     </thead>
-
-     <tbody>
-
-
-      <row>
-       <entry>
-        <literal><command>EXECUTE</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CREATE NODE</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>START TRANSACTION</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>BEGIN</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>COMMIT</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>ROLLBACK</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>PREPARE TRANSACTION</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>COMMIT PREPARED</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>ROLLBACK PREPARED</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>DECLARE CURSOR</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CLOSE CURSOR</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>FETCH</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>TRUNCATE</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>COPY</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>PREPARE</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>DEALLOCATE</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>DO</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>NOTIFY</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>LISTEN</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>UNLISTEN</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>LOAD</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CLUSTER</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>VACUUM</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>EXPLAIN</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>SET</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>SHOW</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>DISCARD</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>LOCK</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>SET CONSTRAINTS</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CHECKPOINT</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CREATE BARRIER</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>REINDEX</command></literal>
-       </entry>
-      </row>
-
-
-      <row>
-       <entry>
-        <literal><command>CLEAN CONNECTION</command></literal>
-       </entry>
-      </row>
-
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-   To lock the cluster for backup while adding a new node <productname>Postgres-XL</productname> uses advisory locks.
-   Every time a disallowed statement is issued the system tries to acquire a transaction
-   level advisory lock in shared mode and the lock is released when
-   the DDL or the transaction issuing the DDL ends. The function <function>pgxc_lock_for_backup</>
-   tries to acquire the same advisory lock in exclusive mode at session level. It is therefore necessary
-   to keep the session issuing <function>pgxc_lock_for_backup</> alive as long as the issuer wants
-   the system to keep the lock.
-   <productname>Postgres-XL</productname> uses the key pair (0xFFFF, 0xFFFF) as object ID while using
-   advisory lock for backup.
-   The function fails to acquire the lock if any one of the following is true:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       The caller of the function is not a superuser.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       There are some uncommitted prepared transactions, because they might
-       contain any utility statement belonging to the disallowed group.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The lock is already held by an uncommitted transaction that has issued
-       a utility statement belonging to the disallowed group.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The lock is already held by a previous call to the same function
-       and current request is being issued from a different session.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </para>
-<!## end>
-
-  </sect1>
-
-<!## PG>
-<!-- NOTICE:
-     TRIGGER not supported yet.
--->
-  <sect1 id="functions-trigger">
-   <title>Trigger Functions</title>
-
-   <indexterm>
-     <primary>suppress_redundant_updates_trigger</primary>
-   </indexterm>
-
-   <para>
-      Currently <productname>PostgreSQL</> provides one built in trigger
-      function, <function>suppress_redundant_updates_trigger</>,
-      which will prevent any update
-      that does not actually change the data in the row from taking place, in
-      contrast to the normal behavior which always performs the update
-      regardless of whether or not the data has changed. (This normal behavior
-      makes updates run faster, since no checking is required, and is also
-      useful in certain cases.)
-    </para>
-
-    <para>
-      Ideally, you should normally avoid running updates that don't actually
-      change the data in the record. Redundant updates can cost considerable
-      unnecessary time, especially if there are lots of indexes to alter,
-      and space in dead rows that will eventually have to be vacuumed.
-      However, detecting such situations in client code is not
-      always easy, or even possible, and writing expressions to detect
-      them can be error-prone. An alternative is to use
-      <function>suppress_redundant_updates_trigger</>, which will skip
-      updates that don't change the data. You should use this with care,
-      however. The trigger takes a small but non-trivial time for each record,
-      so if most of the records affected by an update are actually changed,
-      use of this trigger will actually make the update run slower.
-    </para>
-
-    <para>
-      The <function>suppress_redundant_updates_trigger</> function can be
-      added to a table like this:
-<programlisting>
-CREATE TRIGGER z_min_update
-BEFORE UPDATE ON tablename
-FOR EACH ROW EXECUTE PROCEDURE suppress_redundant_updates_trigger();
-</programlisting>
-      In most cases, you would want to fire this trigger last for each row.
-      Bearing in mind that triggers fire in name order, you would then
-      choose a trigger name that comes after the name of any other trigger
-      you might have on the table.
-    </para>
-    <para>
-       For more information about creating triggers, see
-        <xref linkend="SQL-CREATETRIGGER">.
-    </para>
-  </sect1>
-
-<!## end>
-
-</chapter>
diff --git a/doc-xc/src/sgml/fuzzystrmatch.sgmlin b/doc-xc/src/sgml/fuzzystrmatch.sgmlin
deleted file mode 100644
index 4544c38bdf..0000000000
--- a/doc-xc/src/sgml/fuzzystrmatch.sgmlin
+++ /dev/null
@@ -1,220 +0,0 @@
-<!-- doc/src/sgml/fuzzystrmatch.sgml -->
-
-<sect1 id="fuzzystrmatch" xreflabel="fuzzystrmatch">
- <title>fuzzystrmatch</title>
-
- <indexterm zone="fuzzystrmatch">
-  <primary>fuzzystrmatch</primary>
- </indexterm>
-
-&common;
-
-
- <para>
-  The <filename>fuzzystrmatch</> module provides several
-  functions to determine similarities and distance between strings.
- </para>
-
- <caution>
-  <para>
-   At present, the <function>soundex</>, <function>metaphone</>,
-   <function>dmetaphone</>, and <function>dmetaphone_alt</> functions do
-   not work well with multibyte encodings (such as UTF-8).
-  </para>
- </caution>
-
- <sect2>
-  <title>Soundex</title>
-
-&common;
-
-
-  <para>
-   The Soundex system is a method of matching similar-sounding names
-   by converting them to the same code.  It was initially used by the
-   United States Census in 1880, 1900, and 1910.  Note that Soundex
-   is not very useful for non-English names.
-  </para>
-
-  <para>
-   The <filename>fuzzystrmatch</> module provides two functions
-   for working with Soundex codes:
-  </para>
-
-<synopsis>
-soundex(text) returns text
-difference(text, text) returns int
-</synopsis>
-
-  <para>
-   The <function>soundex</> function converts a string to its Soundex code.
-   The <function>difference</> function converts two strings to their Soundex
-   codes and then reports the number of matching code positions.  Since
-   Soundex codes have four characters, the result ranges from zero to four,
-   with zero being no match and four being an exact match.  (Thus, the
-   function is misnamed &mdash; <function>similarity</> would have been
-   a better name.)
-  </para>
-
-  <para>
-   Here are some usage examples:
-  </para>
-
-<programlisting>
-SELECT soundex('hello world!');
-
-SELECT soundex('Anne'), soundex('Ann'), difference('Anne', 'Ann');
-SELECT soundex('Anne'), soundex('Andrew'), difference('Anne', 'Andrew');
-SELECT soundex('Anne'), soundex('Margaret'), difference('Anne', 'Margaret');
-
-CREATE TABLE s (nm text);
-
-INSERT INTO s VALUES ('john');
-INSERT INTO s VALUES ('joan');
-INSERT INTO s VALUES ('wobbly');
-INSERT INTO s VALUES ('jack');
-
-SELECT * FROM s WHERE soundex(nm) = soundex('john');
-
-SELECT * FROM s WHERE difference(s.nm, 'john') &gt; 2;
-</programlisting>
- </sect2>
-
- <sect2>
-  <title>Levenshtein</title>
-
-&common;
-
-
-  <para>
-   This function calculates the Levenshtein distance between two strings:
-  </para>
-
-<synopsis>
-levenshtein(text source, text target, int ins_cost, int del_cost, int sub_cost) returns int
-levenshtein(text source, text target) returns int
-levenshtein_less_equal(text source, text target, int ins_cost, int del_cost, int sub_cost, int max_d) returns int
-levenshtein_less_equal(text source, text target, int max_d) returns int
-</synopsis>
-
-  <para>
-   Both <literal>source</literal> and <literal>target</literal> can be any
-   non-null string, with a maximum of 255 bytes.  The cost parameters
-   specify how much to charge for a character insertion, deletion, or
-   substitution, respectively.  You can omit the cost parameters, as in
-   the second version of the function; in that case they all default to 1.
-   <literal>levenshtein_less_equal</literal> is accelerated version of
-   levenshtein function for low values of distance. If actual distance
-   is less or equal then max_d, then <literal>levenshtein_less_equal</literal>
-   returns accurate value of it. Otherwise this function returns value
-   which is greater than max_d.
-  </para>
-
-  <para>
-   Examples:
-  </para>
-
-<screen>
-test=# SELECT levenshtein('GUMBO', 'GAMBOL');
- levenshtein
--------------
-           2
-(1 row)
-
-test=# SELECT levenshtein('GUMBO', 'GAMBOL', 2,1,1);
- levenshtein
--------------
-           3
-(1 row)
-
-test=# SELECT levenshtein_less_equal('extensive', 'exhaustive',2);
- levenshtein_less_equal
-------------------------
-                      3
-(1 row)
-
-test=# SELECT levenshtein_less_equal('extensive', 'exhaustive',4);
- levenshtein_less_equal
-------------------------
-                      4
-(1 row)
-</screen>
- </sect2>
-
- <sect2>
-  <title>Metaphone</title>
-
-&common;
-
-
-  <para>
-   Metaphone, like Soundex, is based on the idea of constructing a
-   representative code for an input string.  Two strings are then
-   deemed similar if they have the same codes.
-  </para>
-
-  <para>
-   This function calculates the metaphone code of an input string:
-  </para>
-
-<synopsis>
-metaphone(text source, int max_output_length) returns text
-</synopsis>
-
-  <para>
-   <literal>source</literal> has to be a non-null string with a maximum of
-   255 characters.  <literal>max_output_length</literal> sets the maximum
-   length of the output metaphone code; if longer, the output is truncated
-   to this length.
-  </para>
-
-  <para>
-   Example:
-  </para>
-
-<screen>
-test=# SELECT metaphone('GUMBO', 4);
- metaphone
------------
- KM
-(1 row)
-</screen>
- </sect2>
-
- <sect2>
-  <title>Double Metaphone</title>
-
-&common;
-
-
-  <para>
-   The Double Metaphone system computes two <quote>sounds like</> strings
-   for a given input string &mdash; a <quote>primary</> and an
-   <quote>alternate</>.  In most cases they are the same, but for non-English
-   names especially they can be a bit different, depending on pronunciation.
-   These functions compute the primary and alternate codes:
-  </para>
-
-<synopsis>
-dmetaphone(text source) returns text
-dmetaphone_alt(text source) returns text
-</synopsis>
-
-  <para>
-   There is no length limit on the input strings.
-  </para>
-
-  <para>
-   Example:
-  </para>
-
-<screen>
-test=# select dmetaphone('gumbo');
- dmetaphone
-------------
- KMP
-(1 row)
-</screen>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/generate-errcodes-table.pl b/doc-xc/src/sgml/generate-errcodes-table.pl
deleted file mode 100644
index 0ac020ee24..0000000000
--- a/doc-xc/src/sgml/generate-errcodes-table.pl
+++ /dev/null
@@ -1,56 +0,0 @@
-#!/usr/bin/perl
-#
-# Generate the errcodes-table.sgml file from errcodes.txt
-# Copyright (c) 2000-2011, PostgreSQL Global Development Group
-
-use warnings;
-use strict;
-
-print "<!-- autogenerated from src/backend/utils/errcodes.txt, do not edit -->\n";
-
-open my $errcodes, $ARGV[0] or die;
-
-while (<$errcodes>) {
-    chomp;
-
-    # Skip comments
-    next if /^#/;
-    next if /^\s*$/;
-
-    # Emit section headers
-    if (/^Section:/) {
-
-	# Remove the Section: string
-	s/^Section: //;
-	# Escape dashes for SGML
-	s/-/&mdash;/;
-	# Wrap PostgreSQL in <productname/>
-	s/PostgreSQL/<productname>PostgreSQL<\/>/g;
-
-	print "\n\n";
-	print "<row>\n";
-	print "<entry spanname=\"span12\">";
-	print "<emphasis role=\"bold\">$_</></entry>\n";
-	print "</row>\n";
-
-	next;
-    }
-
-    die unless /^([^\s]{5})\s+([EWS])\s+([^\s]+)(?:\s+)?([^\s]+)?/;
-
-    (my $sqlstate,
-     my $type,
-     my $errcode_macro,
-     my $condition_name) = ($1, $2, $3, $4);
-
-    # Skip lines without PL/pgSQL condition names
-    next unless defined($condition_name);
-
-    print "\n";
-    print "<row>\n";
-    print "<entry><literal>$sqlstate</literal></entry>\n";
-    print "<entry><symbol>$condition_name</symbol></entry>\n";
-    print "</row>\n";
-}
-
-close $errcodes;
diff --git a/doc-xc/src/sgml/generate_history.pl b/doc-xc/src/sgml/generate_history.pl
deleted file mode 100644
index a6c0bd77c2..0000000000
--- a/doc-xc/src/sgml/generate_history.pl
+++ /dev/null
@@ -1,58 +0,0 @@
-#! /usr/bin/perl -w
-
-# generate_history.pl -- flatten release notes for use as HISTORY file
-#
-# Usage: generate_history.pl srcdir release.sgml >output.sgml
-#
-# The main point of this script is to strip out <link> references, which
-# generally point into the rest of the documentation and so can't be used
-# in a standalone build of the release notes.  To make sure this is done
-# everywhere, we have to fold in the sub-files of the release notes.
-#
-# doc/src/sgml/generate_history.pl
-
-use strict;
-
-my $srcdir = shift;
-die "$0: missing required argument: srcdir\n" if !defined($srcdir);
-my $infile = shift;
-die "$0: missing required argument: inputfile\n" if !defined($infile);
-
-# Emit DOCTYPE header so that the output is a self-contained SGML document
-print "<!DOCTYPE appendix PUBLIC \"-//OASIS//DTD DocBook V4.2//EN\">\n";
-
-process_file($infile);
-
-exit 0;
-
-sub process_file {
-    my $filename = shift;
-
-    local *FILE;		# need a local filehandle so we can recurse
-
-    my $f = $srcdir . '/' . $filename;
-    open(FILE, $f) || die "could not read $f: $!\n";
-
-    while (<FILE>) {
-	# Recursively expand sub-files of the release notes
-	if (m/^&(release-.*);$/) {
-	    process_file($1 . ".sgml");
-	    next;
-	}
-
-	# Remove <link ...> tags, which might span multiple lines
-	while (m/<link/) {
-	    if (s/<link\s+linkend[^>]*>//) {
-		next;
-	    }
-	    # incomplete tag, so slurp another line
-	    $_ .= <FILE>;
-	}
-
-	# Remove </link> too
-	s|</link>||g;
-
-	print;
-    }
-    close(FILE);
-}
diff --git a/doc-xc/src/sgml/geqo.sgmlin b/doc-xc/src/sgml/geqo.sgmlin
deleted file mode 100644
index 97392658ba..0000000000
--- a/doc-xc/src/sgml/geqo.sgmlin
+++ /dev/null
@@ -1,387 +0,0 @@
-<!-- doc/src/sgml/geqo.sgml -->
-
- <chapter id="geqo">
-  <chapterinfo>
-   <author>
-    <firstname>Martin</firstname>
-    <surname>Utesch</surname>
-    <affiliation>
-     <orgname>
-      University of Mining and Technology
-     </orgname>
-     <orgdiv>
-      Institute of Automatic Control
-     </orgdiv>
-     <address>
-      <city>
-       Freiberg
-      </city>
-      <country>
-       Germany
-      </country>
-     </address>
-    </affiliation>
-   </author>
-   <date>1997-10-02</date>
-  </chapterinfo>
-
-  <title>Genetic Query Optimizer</title>
-
-&common
-
-  <para>
-   <note>
-    <title>Author</title>
-    <para>
-     Written by Martin Utesch (<email>[email protected]</email>)
-     for the Institute of Automatic Control at the University of Mining and Technology in Freiberg, Germany.
-    </para>
-   </note>
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   This chapter describes internals about <productname>PostgreSQL</>'s
-   planner. <productname>Postgres-XC</>'s planner inherited and
-   extended it.  Detailed description of <productname>Postgres-XC</>'s
-   planner will be given elsewhere.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   This chapter describes internals about <productname>PostgreSQL</>'s
-   planner. <productname>Postgres-XL</>'s planner inherited and
-   extended it.  Detailed description of <productname>Postgres-XL</>'s
-   planner will be given elsewhere.
-  </para>
-<!## end>
-
-  <sect1 id="geqo-intro">
-   <title>Query Handling as a Complex Optimization Problem</title>
-
-&common
-   <para>
-    Among all relational operators the most difficult one to process
-    and optimize is the <firstterm>join</firstterm>. The number of
-    possible query plans grows exponentially with the
-    number of joins in the query. Further optimization effort is
-    caused by the support of a variety of <firstterm>join
-    methods</firstterm> (e.g., nested loop, hash join, merge join in
-    <productname>PostgreSQL</productname>) to process individual joins
-    and a diversity of <firstterm>indexes</firstterm> (e.g.,
-    B-tree, hash, GiST and GIN in <productname>PostgreSQL</productname>) as
-    access paths for relations.
-   </para>
-
-   <para>
-    The normal <productname>PostgreSQL</productname> query optimizer
-    performs a <firstterm>near-exhaustive search</firstterm> over the
-    space of alternative strategies. This algorithm, first introduced
-    in IBM's System R database, produces a near-optimal join order,
-    but can take an enormous amount of time and memory space when the
-    number of joins in the query grows large. This makes the ordinary
-    <productname>PostgreSQL</productname> query optimizer
-    inappropriate for queries that join a large number of tables.
-   </para>
-
-   <para>
-    The Institute of Automatic Control at the University of Mining and
-    Technology, in Freiberg, Germany, encountered some problems when
-    it wanted to use <productname>PostgreSQL</productname> as the
-    backend for a decision support knowledge based system for the
-    maintenance of an electrical power grid. The DBMS needed to handle
-    large join queries for the inference machine of the knowledge
-    based system. The number of joins in these queries made using the
-    normal query optimizer infeasible.
-   </para>
-
-   <para>
-    In the following we describe the implementation of a
-    <firstterm>genetic algorithm</firstterm> to solve the join
-    ordering problem in a manner that is efficient for queries
-    involving large numbers of joins.
-   </para>
-  </sect1>
-
-  <sect1 id="geqo-intro2">
-   <title>Genetic Algorithms</title>
-
-&common;
-   <para>
-    The genetic algorithm (<acronym>GA</acronym>) is a heuristic optimization method which
-    operates through randomized search. The set of possible solutions for the
-    optimization problem is considered as a
-    <firstterm>population</firstterm> of <firstterm>individuals</firstterm>.
-    The degree of adaptation of an individual to its environment is specified
-    by its <firstterm>fitness</firstterm>.
-   </para>
-
-   <para>
-    The coordinates of an individual in the search space are represented
-    by <firstterm>chromosomes</firstterm>, in essence a set of character
-    strings. A <firstterm>gene</firstterm> is a
-    subsection of a chromosome which encodes the value of a single parameter
-    being optimized. Typical encodings for a gene could be <firstterm>binary</firstterm> or
-    <firstterm>integer</firstterm>.
-   </para>
-
-   <para>
-    Through simulation of the evolutionary operations <firstterm>recombination</firstterm>,
-    <firstterm>mutation</firstterm>, and
-    <firstterm>selection</firstterm> new generations of search points are found
-    that show a higher average fitness than their ancestors.
-   </para>
-
-   <para>
-    According to the <systemitem class="resource">comp.ai.genetic</> <acronym>FAQ</acronym> it cannot be stressed too
-    strongly that a <acronym>GA</acronym> is not a pure random search for a solution to a
-    problem. A <acronym>GA</acronym> uses stochastic processes, but the result is distinctly
-    non-random (better than random).
-   </para>
-
-   <figure id="geqo-diagram">
-    <title>Structured Diagram of a Genetic Algorithm</title>
-
-    <informaltable frame="none">
-     <tgroup cols="2">
-      <tbody>
-       <row>
-        <entry>P(t)</entry>
-        <entry>generation of ancestors at a time t</entry>
-       </row>
-
-       <row>
-        <entry>P''(t)</entry>
-        <entry>generation of descendants at a time t</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </informaltable>
-
-<literallayout class="monospaced">
-+=========================================+
-|&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;  Algorithm GA  &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;|
-+=========================================+
-| INITIALIZE t := 0                       |
-+=========================================+
-| INITIALIZE P(t)                         |
-+=========================================+
-| evaluate FITNESS of P(t)                |
-+=========================================+
-| while not STOPPING CRITERION do         |
-|   +-------------------------------------+
-|   | P'(t)  := RECOMBINATION{P(t)}       |
-|   +-------------------------------------+
-|   | P''(t) := MUTATION{P'(t)}           |
-|   +-------------------------------------+
-|   | P(t+1) := SELECTION{P''(t) + P(t)}  |
-|   +-------------------------------------+
-|   | evaluate FITNESS of P''(t)          |
-|   +-------------------------------------+
-|   | t := t + 1                          |
-+===+=====================================+
-</literallayout>
-   </figure>
-  </sect1>
-
-  <sect1 id="geqo-pg-intro">
-   <title>Genetic Query Optimization (<acronym>GEQO</acronym>) in PostgreSQL</title>
-
-&common;
-   <para>
-    The <acronym>GEQO</acronym> module approaches the query
-    optimization problem as though it were the well-known traveling salesman
-    problem (<acronym>TSP</acronym>).
-    Possible query plans are encoded as integer strings. Each string
-    represents the join order from one relation of the query to the next.
-    For example, the join tree
-<literallayout class="monospaced">
-   /\
-  /\ 2
- /\ 3
-4  1
-</literallayout>
-    is encoded by the integer string '4-1-3-2',
-    which means, first join relation '4' and '1', then '3', and
-    then '2', where 1, 2, 3, 4 are relation IDs within the
-    <productname>PostgreSQL</productname> optimizer.
-   </para>
-
-   <para>
-    Specific characteristics of the <acronym>GEQO</acronym>
-    implementation in <productname>PostgreSQL</productname>
-    are:
-
-    <itemizedlist spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       Usage of a <firstterm>steady state</firstterm> <acronym>GA</acronym> (replacement of the least fit
-       individuals in a population, not whole-generational replacement)
-       allows fast convergence towards improved query plans. This is
-       essential for query handling with reasonable time;
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Usage of <firstterm>edge recombination crossover</firstterm>
-       which is especially suited to keep edge losses low for the
-       solution of the <acronym>TSP</acronym> by means of a
-       <acronym>GA</acronym>;
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Mutation as genetic operator is deprecated so that no repair
-       mechanisms are needed to generate legal <acronym>TSP</acronym> tours.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    Parts of the <acronym>GEQO</acronym> module are adapted from D. Whitley's
-    Genitor algorithm.
-   </para>
-
-   <para>
-    The <acronym>GEQO</acronym> module allows
-    the <productname>PostgreSQL</productname> query optimizer to
-    support large join queries effectively through
-    non-exhaustive search.
-   </para>
-
-  <sect2>
-   <title>Generating Possible Plans with <acronym>GEQO</acronym></title>
-
-&common;
-   <para>
-    The <acronym>GEQO</acronym> planning process uses the standard planner
-    code to generate plans for scans of individual relations.  Then join
-    plans are developed using the genetic approach.  As shown above, each
-    candidate join plan is represented by a sequence in which to join
-    the base relations.  In the initial stage, the <acronym>GEQO</acronym>
-    code simply generates some possible join sequences at random.  For each
-    join sequence considered, the standard planner code is invoked to
-    estimate the cost of performing the query using that join sequence.
-    (For each step of the join sequence, all three possible join strategies
-    are considered; and all the initially-determined relation scan plans
-    are available.  The estimated cost is the cheapest of these
-    possibilities.)  Join sequences with lower estimated cost are considered
-    <quote>more fit</> than those with higher cost.  The genetic algorithm
-    discards the least fit candidates.  Then new candidates are generated
-    by combining genes of more-fit candidates &mdash; that is, by using
-    randomly-chosen portions of known low-cost join sequences to create
-    new sequences for consideration.  This process is repeated until a
-    preset number of join sequences have been considered; then the best
-    one found at any time during the search is used to generate the finished
-    plan.
-   </para>
-
-   <para>
-    This process is inherently nondeterministic, because of the randomized
-    choices made during both the initial population selection and subsequent
-    <quote>mutation</> of the best candidates.  To avoid surprising changes
-    of the selected plan, each run of the GEQO algorithm restarts its
-    random number generator with the current <xref linkend="guc-geqo-seed">
-    parameter setting.  As long as <varname>geqo_seed</> and the other
-    GEQO parameters are kept fixed, the same plan will be generated for a
-    given query (and other planner inputs such as statistics).  To experiment
-    with different search paths, try changing <varname>geqo_seed</>.
-   </para>
-
-  </sect2>
-
-  <sect2 id="geqo-future">
-   <title>Future Implementation Tasks for
-    <productname>PostgreSQL</> <acronym>GEQO</acronym></title>
-
-&common;
-     <para>
-      Work is still needed to improve the genetic algorithm parameter
-      settings.
-      In file <filename>src/backend/optimizer/geqo/geqo_main.c</filename>,
-      routines
-      <function>gimme_pool_size</function> and <function>gimme_number_generations</function>,
-      we have to find a compromise for the parameter settings
-      to satisfy two competing demands:
-      <itemizedlist spacing="compact">
-       <listitem>
-        <para>
-         Optimality of the query plan
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Computing time
-        </para>
-       </listitem>
-      </itemizedlist>
-     </para>
-
-     <para>
-      In the current implementation, the fitness of each candidate join
-      sequence is estimated by running the standard planner's join selection
-      and cost estimation code from scratch.  To the extent that different
-      candidates use similar sub-sequences of joins, a great deal of work
-      will be repeated.  This could be made significantly faster by retaining
-      cost estimates for sub-joins.  The problem is to avoid expending
-      unreasonable amounts of memory on retaining that state.
-     </para>
-
-     <para>
-      At a more basic level, it is not clear that solving query optimization
-      with a GA algorithm designed for TSP is appropriate.  In the TSP case,
-      the cost associated with any substring (partial tour) is independent
-      of the rest of the tour, but this is certainly not true for query
-      optimization.  Thus it is questionable whether edge recombination
-      crossover is the most effective mutation procedure.
-     </para>
-
-   </sect2>
-  </sect1>
-
- <sect1 id="geqo-biblio">
-  <title>Further Reading</title>
-
-&common;
-  <para>
-   The following resources contain additional information about
-   genetic algorithms:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <ulink url="http://www.aip.de/~ast/EvolCompFAQ/">
-      The Hitch-Hiker's Guide to Evolutionary Computation</ulink>, (FAQ for <ulink
-      url="news://comp.ai.genetic"></ulink>)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <ulink url="http://www.red3d.com/cwr/evolve.html">
-      Evolutionary Computation and its application to art and design</ulink>, by
-      Craig Reynolds
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <xref linkend="ELMA04">
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <xref linkend="FONG">
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/gin.sgmlin b/doc-xc/src/sgml/gin.sgmlin
deleted file mode 100644
index d6d853a192..0000000000
--- a/doc-xc/src/sgml/gin.sgmlin
+++ /dev/null
@@ -1,560 +0,0 @@
-<!-- doc/src/sgml/gin.sgml -->
-
-<chapter id="GIN">
-<title>GIN Indexes</title>
-
-   <indexterm>
-    <primary>index</primary>
-    <secondary>GIN</secondary>
-   </indexterm>
-&common;
-
-<sect1 id="gin-intro">
- <title>Introduction</title>
-
-&common;
- <para>
-  <acronym>GIN</acronym> stands for Generalized Inverted Index.
-  <acronym>GIN</acronym> is designed for handling cases where the items
-  to be indexed are composite values, and the queries to be handled by
-  the index need to search for element values that appear within
-  the composite items.  For example, the items could be documents,
-  and the queries could be searches for documents containing specific words.
- </para>
-
- <para>
-  We use the word <firstterm>item</> to refer to a composite value that
-  is to be indexed, and the word <firstterm>key</> to refer to an element
-  value.  <acronym>GIN</acronym> always stores and searches for keys,
-  not item values per se.
- </para>
-
- <para>
-  A <acronym>GIN</acronym> index stores a set of (key, posting list) pairs,
-  where a <firstterm>posting list</> is a set of row IDs in which the key
-  occurs.  The same row ID can appear in multiple posting lists, since
-  an item can contain more than one key.  Each key value is stored only
-  once, so a <acronym>GIN</acronym> index is very compact for cases
-  where the same key appears many times.
- </para>
-
- <para>
-  <acronym>GIN</acronym> is generalized in the sense that the
-  <acronym>GIN</acronym> access method code does not need to know the
-  specific operations that it accelerates.
-  Instead, it uses custom strategies defined for particular data types.
-  The strategy defines how keys are extracted from indexed items and
-  query conditions, and how to determine whether a row that contains
-  some of the key values in a query actually satisfies the query.
- </para>
-
- <para>
-  One advantage of <acronym>GIN</acronym> is that it allows the development
-  of custom data types with the appropriate access methods, by
-  an expert in the domain of the data type, rather than a database expert.
-  This is much the same advantage as using <acronym>GiST</acronym>.
- </para>
-
- <para>
-  The <acronym>GIN</acronym>
-<!## PG>
-  implementation in <productname>PostgreSQL</productname> is primarily
-<!## end>
-<!## XC>
-  implementation in <productname>Postgres-XC</productname> is inherited from <productname>PostgreSQL</> and is primarily
-<!## end>
-<!## XL>
-  implementation in <productname>Postgres-XL</productname> is inherited from <productname>PostgreSQL</> and is primarily
-<!## end>
-  maintained by Teodor Sigaev and Oleg Bartunov. There is more
-  information about <acronym>GIN</acronym> on their
-  <ulink url="http://www.sai.msu.su/~megera/wiki/Gin">website</ulink>.
- </para>
-</sect1>
-
-<sect1 id="gin-extensibility">
- <title>Extensibility</title>
-
-&common;
- <para>
-   The <acronym>GIN</acronym> interface has a high level of abstraction,
-   requiring the access method implementer only to implement the semantics of
-   the data type being accessed.  The <acronym>GIN</acronym> layer itself
-   takes care of concurrency, logging and searching the tree structure.
- </para>
-
- <para>
-   All it takes to get a <acronym>GIN</acronym> access method working is to
-   implement four (or five) user-defined methods, which define the behavior of
-   keys in the tree and the relationships between keys, indexed items,
-   and indexable queries. In short, <acronym>GIN</acronym> combines
-   extensibility with generality, code reuse, and a clean interface.
- </para>
-
- <para>
-   The four methods that an operator class for
-   <acronym>GIN</acronym> must provide are:
-
- <variablelist>
-    <varlistentry>
-     <term><function>int compare(Datum a, Datum b)</></term>
-     <listitem>
-      <para>
-       Compares two keys (not indexed items!) and returns an integer less than
-       zero, zero, or greater than zero, indicating whether the first key is
-       less than, equal to, or greater than the second.  Null keys are never
-       passed to this function.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>Datum *extractValue(Datum itemValue, int32 *nkeys,
-        bool **nullFlags)</></term>
-     <listitem>
-      <para>
-       Returns a palloc'd array of keys given an item to be indexed.  The
-       number of returned keys must be stored into <literal>*nkeys</>.
-       If any of the keys can be null, also palloc an array of
-       <literal>*nkeys</> booleans, store its address at
-       <literal>*nullFlags</>, and set these null flags as needed.
-       <literal>*nullFlags</> can be left NULL (its initial value)
-       if all keys are non-null.
-       The return value can be NULL if the item contains no keys.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>Datum *extractQuery(Datum query, int32 *nkeys,
-        StrategyNumber n, bool **pmatch, Pointer **extra_data,
-        bool **nullFlags, int32 *searchMode)</></term>
-     <listitem>
-      <para>
-       Returns a palloc'd array of keys given a value to be queried; that is,
-       <literal>query</> is the value on the right-hand side of an
-       indexable operator whose left-hand side is the indexed column.
-       <literal>n</> is the strategy number of the operator within the
-       operator class (see <xref linkend="xindex-strategies">).
-       Often, <function>extractQuery</> will need
-       to consult <literal>n</> to determine the data type of
-       <literal>query</> and the method it should use to extract key values.
-       The number of returned keys must be stored into <literal>*nkeys</>.
-       If any of the keys can be null, also palloc an array of
-       <literal>*nkeys</> booleans, store its address at
-       <literal>*nullFlags</>, and set these null flags as needed.
-       <literal>*nullFlags</> can be left NULL (its initial value)
-       if all keys are non-null.
-       The return value can be NULL if the <literal>query</> contains no keys.
-      </para>
-
-      <para>
-       <literal>searchMode</> is an output argument that allows
-       <function>extractQuery</> to specify details about how the search
-       will be done.
-       If <literal>*searchMode</> is set to
-       <literal>GIN_SEARCH_MODE_DEFAULT</> (which is the value it is
-       initialized to before call), only items that match at least one of
-       the returned keys are considered candidate matches.
-       If <literal>*searchMode</> is set to
-       <literal>GIN_SEARCH_MODE_INCLUDE_EMPTY</>, then in addition to items
-       containing at least one matching key, items that contain no keys at
-       all are considered candidate matches.  (This mode is useful for
-       implementing is-subset-of operators, for example.)
-       If <literal>*searchMode</> is set to <literal>GIN_SEARCH_MODE_ALL</>,
-       then all non-null items in the index are considered candidate
-       matches, whether they match any of the returned keys or not.  (This
-       mode is much slower than the other two choices, since it requires
-       scanning essentially the entire index, but it may be necessary to
-       implement corner cases correctly.  An operator that needs this mode
-       in most cases is probably not a good candidate for a GIN operator
-       class.)
-       The symbols to use for setting this mode are defined in
-       <filename>access/gin.h</>.
-      </para>
-
-      <para>
-       <literal>pmatch</> is an output argument for use when partial match
-       is supported.  To use it, <function>extractQuery</> must allocate
-       an array of <literal>*nkeys</> booleans and store its address at
-       <literal>*pmatch</>.  Each element of the array should be set to TRUE
-       if the corresponding key requires partial match, FALSE if not.
-       If <literal>*pmatch</> is set to NULL then GIN assumes partial match
-       is not required.  The variable is initialized to NULL before call,
-       so this argument can simply be ignored by operator classes that do
-       not support partial match.
-      </para>
-
-      <para>
-       <literal>extra_data</> is an output argument that allows
-       <function>extractQuery</> to pass additional data to the
-       <function>consistent</> and <function>comparePartial</> methods.
-       To use it, <function>extractQuery</> must allocate
-       an array of <literal>*nkeys</> Pointers and store its address at
-       <literal>*extra_data</>, then store whatever it wants to into the
-       individual pointers.  The variable is initialized to NULL before
-       call, so this argument can simply be ignored by operator classes that
-       do not require extra data.  If <literal>*extra_data</> is set, the
-       whole array is passed to the <function>consistent</> method, and
-       the appropriate element to the <function>comparePartial</> method.
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>bool consistent(bool check[], StrategyNumber n, Datum query,
-        int32 nkeys, Pointer extra_data[], bool *recheck,
-        Datum queryKeys[], bool nullFlags[])</></term>
-     <listitem>
-      <para>
-       Returns TRUE if an indexed item satisfies the query operator with
-       strategy number <literal>n</> (or might satisfy it, if the recheck
-       indication is returned).  This function does not have direct access
-       to the indexed item's value, since <acronym>GIN</acronym> does not
-       store items explicitly.  Rather, what is available is knowledge
-       about which key values extracted from the query appear in a given
-       indexed item.  The <literal>check</> array has length
-       <literal>nkeys</>, which is the same as the number of keys previously
-       returned by <function>extractQuery</> for this <literal>query</> datum.
-       Each element of the
-       <literal>check</> array is TRUE if the indexed item contains the
-       corresponding query key, ie, if (check[i] == TRUE) the i-th key of the
-       <function>extractQuery</> result array is present in the indexed item.
-       The original <literal>query</> datum is
-       passed in case the <function>consistent</> method needs to consult it,
-       and so are the <literal>queryKeys[]</> and <literal>nullFlags[]</>
-       arrays previously returned by <function>extractQuery</>.
-       <literal>extra_data</> is the extra-data array returned by
-       <function>extractQuery</>, or NULL if none.
-      </para>
-
-      <para>
-       When <function>extractQuery</> returns a null key in
-       <literal>queryKeys[]</>, the corresponding <literal>check[]</> element
-       is TRUE if the indexed item contains a null key; that is, the
-       semantics of <literal>check[]</> are like <literal>IS NOT DISTINCT
-       FROM</>.  The <function>consistent</> function can examine the
-       corresponding <literal>nullFlags[]</> element if it needs to tell
-       the difference between a regular value match and a null match.
-      </para>
-
-      <para>
-       On success, <literal>*recheck</> should be set to TRUE if the heap
-       tuple needs to be rechecked against the query operator, or FALSE if
-       the index test is exact.  That is, a FALSE return value guarantees
-       that the heap tuple does not match the query; a TRUE return value with
-       <literal>*recheck</> set to FALSE guarantees that the heap tuple does
-       match the query; and a TRUE return value with
-       <literal>*recheck</> set to TRUE means that the heap tuple might match
-       the query, so it needs to be fetched and rechecked by evaluating the
-       query operator directly against the originally indexed item.
-      </para>
-     </listitem>
-    </varlistentry>
-  </variablelist>
-
-  Optionally, an operator class for
-  <acronym>GIN</acronym> can supply a fifth method:
-
-  <variablelist>
-    <varlistentry>
-     <term><function>int comparePartial(Datum partial_key, Datum key, StrategyNumber n,
-                              Pointer extra_data)</></term>
-     <listitem>
-      <para>
-       Compare a partial-match query key to an index key.  Returns an integer
-       whose sign indicates the result: less than zero means the index key
-       does not match the query, but the index scan should continue; zero
-       means that the index key does match the query; greater than zero
-       indicates that the index scan should stop because no more matches
-       are possible.  The strategy number <literal>n</> of the operator
-       that generated the partial match query is provided, in case its
-       semantics are needed to determine when to end the scan.  Also,
-       <literal>extra_data</> is the corresponding element of the extra-data
-       array made by <function>extractQuery</>, or NULL if none.
-       Null keys are never passed to this function.
-      </para>
-     </listitem>
-    </varlistentry>
-  </variablelist>
- </para>
-
- <para>
-  To support <quote>partial match</> queries, an operator class must
-  provide the <function>comparePartial</> method, and its
-  <function>extractQuery</> method must set the <literal>pmatch</>
-  parameter when a partial-match query is encountered.  See
-  <xref linkend="gin-partial-match"> for details.
- </para>
-
- <para>
-  The actual data types of the various <literal>Datum</> values mentioned
-  above vary depending on the operator class.  The item values passed to
-  <function>extractValue</> are always of the operator class's input type, and
-  all key values must be of the class's <literal>STORAGE</> type.  The type of
-  the <literal>query</> argument passed to <function>extractQuery</> and
-  <function>consistent</> is whatever is specified as the right-hand input
-  type of the class member operator identified by the strategy number.
-  This need not be the same as the item type, so long as key values of the
-  correct type can be extracted from it.
- </para>
-
-</sect1>
-
-<sect1 id="gin-implementation">
- <title>Implementation</title>
-
-&common;
- <para>
-  Internally, a <acronym>GIN</acronym> index contains a B-tree index
-  constructed over keys, where each key is an element of one or more indexed
-  items (a member of an array, for example) and where each tuple in a leaf
-  page contains either a pointer to a B-tree of heap pointers (a
-  <quote>posting tree</>), or a simple list of heap pointers (a <quote>posting
-  list</>) when the list is small enough to fit into a single index tuple along
-  with the key value.
- </para>
-
- <para>
-  As of <productname>PostgreSQL</productname> 9.1, NULL key values can be
-  included in the index.  Also, placeholder NULLs are included in the index
-  for indexed items that are NULL or contain no keys according to
-  <function>extractValue</>.  This allows searches that should find empty
-  items to do so.
- </para>
-
- <para>
-  Multi-column <acronym>GIN</acronym> indexes are implemented by building
-  a single B-tree over composite values (column number, key value).  The
-  key values for different columns can be of different types.
- </para>
-
- <sect2 id="gin-fast-update">
-  <title>GIN Fast Update Technique</title>
-
-&common;
-  <para>
-   Updating a <acronym>GIN</acronym> index tends to be slow because of the
-   intrinsic nature of inverted indexes: inserting or updating one heap row
-   can cause many inserts into the index (one for each key extracted
-   from the indexed item). As of <productname>PostgreSQL</productname> 8.4,
-   <acronym>GIN</> is capable of postponing much of this work by inserting
-   new tuples into a temporary, unsorted list of pending entries.
-   When the table is vacuumed, or if the pending list becomes too large
-   (larger than <xref linkend="guc-work-mem">), the entries are moved to the
-   main <acronym>GIN</acronym> data structure using the same bulk insert
-   techniques used during initial index creation.  This greatly improves
-   <acronym>GIN</acronym> index update speed, even counting the additional
-   vacuum overhead.  Moreover the overhead work can be done by a background
-   process instead of in foreground query processing.
-  </para>
-
-  <para>
-   The main disadvantage of this approach is that searches must scan the list
-   of pending entries in addition to searching the regular index, and so
-   a large list of pending entries will slow searches significantly.
-   Another disadvantage is that, while most updates are fast, an update
-   that causes the pending list to become <quote>too large</> will incur an
-   immediate cleanup cycle and thus be much slower than other updates.
-   Proper use of autovacuum can minimize both of these problems.
-  </para>
-
-  <para>
-   If consistent response time is more important than update speed,
-   use of pending entries can be disabled by turning off the
-   <literal>FASTUPDATE</literal> storage parameter for a
-   <acronym>GIN</acronym> index.  See <xref linkend="sql-createindex">
-   for details.
-  </para>
- </sect2>
-
- <sect2 id="gin-partial-match">
-  <title>Partial Match Algorithm</title>
-
-&common;
-  <para>
-   GIN can support <quote>partial match</> queries, in which the query
-   does not determine an exact match for one or more keys, but the possible
-   matches fall within a reasonably narrow range of key values (within the
-   key sorting order determined by the <function>compare</> support method).
-   The <function>extractQuery</> method, instead of returning a key value
-   to be matched exactly, returns a key value that is the lower bound of
-   the range to be searched, and sets the <literal>pmatch</> flag true.
-   The key range is then scanned using the <function>comparePartial</>
-   method.  <function>comparePartial</> must return zero for a matching
-   index key, less than zero for a non-match that is still within the range
-   to be searched, or greater than zero if the index key is past the range
-   that could match.
-  </para>
- </sect2>
-
-</sect1>
-
-<sect1 id="gin-tips">
-<title>GIN Tips and Tricks</title>
-
- <variablelist>
-  <varlistentry>
-   <term>Create vs. insert</term>
-   <listitem>
-&common;
-    <para>
-     Insertion into a <acronym>GIN</acronym> index can be slow
-     due to the likelihood of many keys being inserted for each item.
-     So, for bulk insertions into a table it is advisable to drop the GIN
-     index and recreate it after finishing bulk insertion.
-    </para>
-
-    <para>
-     As of <productname>PostgreSQL</productname> 8.4, this advice is less
-     necessary since delayed indexing is used (see <xref
-     linkend="gin-fast-update"> for details).  But for very large updates
-     it may still be best to drop and recreate the index.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><xref linkend="guc-maintenance-work-mem"></term>
-   <listitem>
-    <para>
-     Build time for a <acronym>GIN</acronym> index is very sensitive to
-     the <varname>maintenance_work_mem</> setting; it doesn't pay to
-     skimp on work memory during index creation.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><xref linkend="guc-work-mem"></term>
-   <listitem>
-    <para>
-     During a series of insertions into an existing <acronym>GIN</acronym>
-     index that has <literal>FASTUPDATE</> enabled, the system will clean up
-     the pending-entry list whenever the list grows larger than
-     <varname>work_mem</>.  To avoid fluctuations in observed response time,
-     it's desirable to have pending-list cleanup occur in the background
-     (i.e., via autovacuum).  Foreground cleanup operations can be avoided by
-     increasing <varname>work_mem</> or making autovacuum more aggressive.
-     However, enlarging <varname>work_mem</> means that if a foreground
-     cleanup does occur, it will take even longer.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><xref linkend="guc-gin-fuzzy-search-limit"></term>
-   <listitem>
-    <para>
-     The primary goal of developing <acronym>GIN</acronym> indexes was
-     to create support for highly scalable full-text search in
-<!## PG>
-     <productname>PostgreSQL</productname>, and there are often situations when
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname>, and there are often situations when
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname>, and there are often situations when
-<!## end>
-     a full-text search returns a very large set of results.  Moreover, this
-     often happens when the query contains very frequent words, so that the
-     large result set is not even useful.  Since reading many
-     tuples from the disk and sorting them could take a lot of time, this is
-     unacceptable for production.  (Note that the index search itself is very
-     fast.)
-    </para>
-    <para>
-     To facilitate controlled execution of such queries,
-     <acronym>GIN</acronym> has a configurable soft upper limit on the
-     number of rows returned: the
-     <varname>gin_fuzzy_search_limit</varname> configuration parameter.
-     It is set to 0 (meaning no limit) by default.
-     If a non-zero limit is set, then the returned set is a subset of
-     the whole result set, chosen at random.
-    </para>
-    <para>
-     <quote>Soft</quote> means that the actual number of returned results
-     could differ somewhat from the specified limit, depending on the query
-     and the quality of the system's random number generator.
-    </para>
-    <para>
-     From experience, values in the thousands (e.g., 5000 &mdash; 20000)
-     work well.
-    </para>
-   </listitem>
-  </varlistentry>
- </variablelist>
-
-</sect1>
-
-<sect1 id="gin-limit">
- <title>Limitations</title>
-
-&common;
- <para>
-  <acronym>GIN</acronym> assumes that indexable operators are strict.  This
-  means that <function>extractValue</> will not be called at all on a NULL
-  item value (instead, a placeholder index entry is created automatically),
-  and <function>extractQuery</function> will not be called on a NULL query
-  value either (instead, the query is presumed to be unsatisfiable).  Note
-  however that NULL key values contained within a non-null composite item
-  or query value are supported.
- </para>
-</sect1>
-
-<sect1 id="gin-examples">
- <title>Examples</title>
-
-&common;
- <para>
-<!## PG>
-  The <productname>PostgreSQL</productname> source distribution includes
-<!## end>
-<!## XC>
-  The <productname>Postgres-XC</productname> source distribution includes
-<!## end>
-<!## XL>
-  The <productname>Postgres-XL</productname> source distribution includes
-<!## end>
-  <acronym>GIN</acronym> operator classes for <type>tsvector</> and
-  for one-dimensional arrays of all internal types.  Prefix searching in
-  <type>tsvector</> is implemented using the <acronym>GIN</> partial match
-  feature.
-  The following <filename>contrib</> modules also contain
-  <acronym>GIN</acronym> operator classes:
-
- <variablelist>
-  <varlistentry>
-   <term><filename>btree_gin</></term>
-   <listitem>
-    <para>B-tree equivalent functionality for several data types</para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><filename>hstore</></term>
-   <listitem>
-    <para>Module for storing (key, value) pairs</para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><filename>intarray</></term>
-   <listitem>
-    <para>Enhanced support for <type>int[]</type></para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><filename>pg_trgm</></term>
-   <listitem>
-    <para>Text similarity using trigram matching</para>
-   </listitem>
-  </varlistentry>
- </variablelist>
- </para>
-</sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/gist.sgmlin b/doc-xc/src/sgml/gist.sgmlin
deleted file mode 100644
index aec788c754..0000000000
--- a/doc-xc/src/sgml/gist.sgmlin
+++ /dev/null
@@ -1,762 +0,0 @@
-<!-- doc/src/sgml/gist.sgml -->
-
-<chapter id="GiST">
-<title>GiST Indexes</title>
-
-   <indexterm>
-    <primary>index</primary>
-    <secondary>GiST</secondary>
-   </indexterm>
-
-&common;
-
-<sect1 id="gist-intro">
- <title>Introduction</title>
-
-&common;
- <para>
-   <acronym>GiST</acronym> stands for Generalized Search Tree.  It is a
-   balanced, tree-structured access method, that acts as a base template in
-   which to implement arbitrary indexing schemes. B-trees, R-trees and many
-   other indexing schemes can be implemented in <acronym>GiST</acronym>.
- </para>
-
- <para>
-  One advantage of <acronym>GiST</acronym> is that it allows the development
-  of custom data types with the appropriate access methods, by
-  an expert in the domain of the data type, rather than a database expert.
- </para>
-
-  <para>
-    Some of the information here is derived from the University of California
-    at Berkeley's GiST Indexing Project
-    <ulink url="http://gist.cs.berkeley.edu/">web site</ulink> and
-    Marcel Kornacker's thesis,
-    <ulink url="http://www.sai.msu.su/~megera/postgres/gist/papers/concurrency/access-methods-for-next-generation.pdf.gz">
-    Access Methods for Next-Generation Database Systems</ulink>.
-    The <acronym>GiST</acronym>
-<!## PG>
-    implementation in <productname>PostgreSQL</productname> is primarily
-<!## end>
-<!## XC>
-    implementation in <productname>PostgreSQL</productname> is inherited from <productname>PostgreSQL</> and is primarily
-<!## end>
-<!## XL>
-    implementation in <productname>PostgreSQL</productname> is inherited from <productname>PostgreSQL</> and is primarily
-<!## end>
-    maintained by Teodor Sigaev and Oleg Bartunov, and there is more
-    information on their
-    <ulink url="http://www.sai.msu.su/~megera/postgres/gist/">web site</ulink>.
-  </para>
-
-</sect1>
-
-<sect1 id="gist-extensibility">
- <title>Extensibility</title>
-
-&common;
- <para>
-   Traditionally, implementing a new index access method meant a lot of
-   difficult work.  It was necessary to understand the inner workings of the
-   database, such as the lock manager and Write-Ahead Log.  The
-   <acronym>GiST</acronym> interface has a high level of abstraction,
-   requiring the access method implementer only to implement the semantics of
-   the data type being accessed.  The <acronym>GiST</acronym> layer itself
-   takes care of concurrency, logging and searching the tree structure.
- </para>
-
- <para>
-   This extensibility should not be confused with the extensibility of the
-   other standard search trees in terms of the data they can handle.  For
-<!## PG>
-   example, <productname>PostgreSQL</productname> supports extensible B-trees
-   and hash indexes. That means that you can use
-   <productname>PostgreSQL</productname> to build a B-tree or hash over any
-<!## end>
-<!## XC>
-   example, <productname>Postgres-XC</productname> supports extensible B-trees
-   and hash indexes. That means that you can use
-   <productname>Postgres-XC</productname> to build a B-tree or hash over any
-<!## end>
-<!## XL>
-   example, <productname>Postgres-XL</productname> supports extensible B-trees
-   and hash indexes. That means that you can use
-   <productname>Postgres-XL</productname> to build a B-tree or hash over any
-<!## end>
-   data type you want. But B-trees only support range predicates
-   (<literal>&lt;</literal>, <literal>=</literal>, <literal>&gt;</literal>),
-   and hash indexes only support equality queries.
- </para>
-
- <para>
-   So if you index, say, an image collection with a
-<!## PG>
-   <productname>PostgreSQL</productname> B-tree, you can only issue queries
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> B-tree, you can only issue queries
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> B-tree, you can only issue queries
-<!## end>
-   such as <quote>is imagex equal to imagey</quote>, <quote>is imagex less
-   than imagey</quote> and <quote>is imagex greater than imagey</quote>.
-   Depending on how you define <quote>equals</quote>, <quote>less than</quote>
-   and <quote>greater than</quote> in this context, this could be useful.
-   However, by using a <acronym>GiST</acronym> based index, you could create
-   ways to ask domain-specific questions, perhaps <quote>find all images of
-   horses</quote> or <quote>find all over-exposed images</quote>.
- </para>
-
- <para>
-   All it takes to get a <acronym>GiST</acronym> access method up and running
-   is to implement several user-defined methods, which define the behavior of
-   keys in the tree. Of course these methods have to be pretty fancy to
-   support fancy queries, but for all the standard queries (B-trees,
-   R-trees, etc.) they're relatively straightforward. In short,
-   <acronym>GiST</acronym> combines extensibility along with generality, code
-   reuse, and a clean interface.
-  </para>
-
-</sect1>
-
-<sect1 id="gist-implementation">
- <title>Implementation</title>
-
-&common;
- <para>
-   There are seven methods that an index operator class for
-   <acronym>GiST</acronym> must provide, and an eighth that is optional.
-   Correctness of the index is ensured
-   by proper implementation of the <function>same</>, <function>consistent</>
-   and <function>union</> methods, while efficiency (size and speed) of the
-   index will depend on the <function>penalty</> and <function>picksplit</>
-   methods.
-   The remaining two basic methods are <function>compress</> and
-   <function>decompress</>, which allow an index to have internal tree data of
-   a different type than the data it indexes. The leaves are to be of the
-   indexed data type, while the other tree nodes can be of any C struct (but
-<!## PG>
-   you still have to follow <productname>PostgreSQL</> data type rules here,
-<!## end>
-<!## XC>
-   you still have to follow <productname>Postgres-XC</> data type rules here,
-<!## end>
-<!## XL>
-   you still have to follow <productname>Postgres-XL</> data type rules here,
-<!## end>
-   see about <literal>varlena</> for variable sized data). If the tree's
-   internal data type exists at the SQL level, the <literal>STORAGE</> option
-   of the <command>CREATE OPERATOR CLASS</> command can be used.
-   The optional eighth method is <function>distance</>, which is needed
-   if the operator class wishes to support ordered scans (nearest-neighbor
-   searches).
- </para>
-
- <variablelist>
-    <varlistentry>
-     <term><function>consistent</></term>
-     <listitem>
-      <para>
-       Given an index entry <literal>p</> and a query value <literal>q</>,
-       this function determines whether the index entry is
-       <quote>consistent</> with the query; that is, could the predicate
-       <quote><replaceable>indexed_column</>
-       <replaceable>indexable_operator</> <literal>q</></quote> be true for
-       any row represented by the index entry?  For a leaf index entry this is
-       equivalent to testing the indexable condition, while for an internal
-       tree node this determines whether it is necessary to scan the subtree
-       of the index represented by the tree node.  When the result is
-       <literal>true</>, a <literal>recheck</> flag must also be returned.
-       This indicates whether the predicate is certainly true or only possibly
-       true.  If <literal>recheck</> = <literal>false</> then the index has
-       tested the predicate condition exactly, whereas if <literal>recheck</>
-       = <literal>true</> the row is only a candidate match.  In that case the
-       system will automatically evaluate the
-       <replaceable>indexable_operator</> against the actual row value to see
-       if it is really a match.  This convention allows
-       <acronym>GiST</acronym> to support both lossless and lossy index
-       structures.
-      </para>
-
-      <para>
-        The <acronym>SQL</> declaration of the function must look like this:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION my_consistent(internal, data_type, smallint, oid, internal)
-RETURNS bool
-AS 'MODULE_PATHNAME'
-LANGUAGE C STRICT;
-</programlisting>
-
-        And the matching code in the C module could then follow this skeleton:
-
-<programlisting>
-Datum       my_consistent(PG_FUNCTION_ARGS);
-PG_FUNCTION_INFO_V1(my_consistent);
-
-Datum
-my_consistent(PG_FUNCTION_ARGS)
-{
-    GISTENTRY  *entry = (GISTENTRY *) PG_GETARG_POINTER(0);
-    data_type  *query = PG_GETARG_DATA_TYPE_P(1);
-    StrategyNumber strategy = (StrategyNumber) PG_GETARG_UINT16(2);
-    /* Oid subtype = PG_GETARG_OID(3); */
-    bool       *recheck = (bool *) PG_GETARG_POINTER(4);
-    data_type  *key = DatumGetDataType(entry-&gt;key);
-    bool        retval;
-
-    /*
-     * determine return value as a function of strategy, key and query.
-     *
-     * Use GIST_LEAF(entry) to know where you're called in the index tree,
-     * which comes handy when supporting the = operator for example (you could
-     * check for non empty union() in non-leaf nodes and equality in leaf
-     * nodes).
-     */
-
-    *recheck = true;        /* or false if check is exact */
-
-    PG_RETURN_BOOL(retval);
-}
-</programlisting>
-
-       Here, <varname>key</> is an element in the index and <varname>query</>
-       the value being looked up in the index. The <literal>StrategyNumber</>
-       parameter indicates which operator of your operator class is being
-       applied &mdash; it matches one of the operator numbers in the
-       <command>CREATE OPERATOR CLASS</> command.  Depending on what operators
-       you have included in the class, the data type of <varname>query</> could
-       vary with the operator, but the above skeleton assumes it doesn't.
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>union</></term>
-     <listitem>
-      <para>
-       This method consolidates information in the tree.  Given a set of
-       entries, this function generates a new index entry that represents
-       all the given entries.
-      </para>
-
-      <para>
-        The <acronym>SQL</> declaration of the function must look like this:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION my_union(internal, internal)
-RETURNS internal
-AS 'MODULE_PATHNAME'
-LANGUAGE C STRICT;
-</programlisting>
-
-        And the matching code in the C module could then follow this skeleton:
-
-<programlisting>
-Datum       my_union(PG_FUNCTION_ARGS);
-PG_FUNCTION_INFO_V1(my_union);
-
-Datum
-my_union(PG_FUNCTION_ARGS)
-{
-    GistEntryVector *entryvec = (GistEntryVector *) PG_GETARG_POINTER(0);
-    GISTENTRY  *ent = entryvec-&gt;vector;
-    data_type  *out,
-               *tmp,
-               *old;
-    int         numranges,
-                i = 0;
-
-    numranges = entryvec-&gt;n;
-    tmp = DatumGetDataType(ent[0].key);
-    out = tmp;
-
-    if (numranges == 1)
-    {
-        out = data_type_deep_copy(tmp);
-
-        PG_RETURN_DATA_TYPE_P(out);
-    }
-
-    for (i = 1; i &lt; numranges; i++)
-    {
-        old = out;
-        tmp = DatumGetDataType(ent[i].key);
-        out = my_union_implementation(out, tmp);
-    }
-
-    PG_RETURN_DATA_TYPE_P(out);
-}
-</programlisting>
-      </para>
-
-      <para>
-        As you can see, in this skeleton we're dealing with a data type
-        where <literal>union(X, Y, Z) = union(union(X, Y), Z)</>. It's easy
-        enough to support data types where this is not the case, by
-        implementing the proper union algorithm in this
-        <acronym>GiST</> support method.
-      </para>
-
-      <para>
-        The <function>union</> implementation function should return a
-        pointer to newly <function>palloc()</>ed memory. You can't just
-        return whatever the input is.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>compress</></term>
-     <listitem>
-      <para>
-       Converts the data item into a format suitable for physical storage in
-       an index page.
-      </para>
-
-      <para>
-        The <acronym>SQL</> declaration of the function must look like this:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION my_compress(internal)
-RETURNS internal
-AS 'MODULE_PATHNAME'
-LANGUAGE C STRICT;
-</programlisting>
-
-        And the matching code in the C module could then follow this skeleton:
-
-<programlisting>
-Datum       my_compress(PG_FUNCTION_ARGS);
-PG_FUNCTION_INFO_V1(my_compress);
-
-Datum
-my_compress(PG_FUNCTION_ARGS)
-{
-    GISTENTRY  *entry = (GISTENTRY *) PG_GETARG_POINTER(0);
-    GISTENTRY  *retval;
-
-    if (entry-&gt;leafkey)
-    {
-        /* replace entry-&gt;key with a compressed version */
-        compressed_data_type *compressed_data = palloc(sizeof(compressed_data_type));
-
-        /* fill *compressed_data from entry-&gt;key ... */
-
-        retval = palloc(sizeof(GISTENTRY));
-        gistentryinit(*retval, PointerGetDatum(compressed_data),
-                      entry-&gt;rel, entry-&gt;page, entry-&gt;offset, FALSE);
-    }
-    else
-    {
-        /* typically we needn't do anything with non-leaf entries */
-        retval = entry;
-    }
-
-    PG_RETURN_POINTER(retval);
-}
-</programlisting>
-      </para>
-
-      <para>
-       You have to adapt <replaceable>compressed_data_type</> to the specific
-       type you're converting to in order to compress your leaf nodes, of
-       course.
-      </para>
-
-      <para>
-        Depending on your needs, you could also need to care about
-        compressing <literal>NULL</> values in there, storing for example
-        <literal>(Datum) 0</> like <literal>gist_circle_compress</> does.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>decompress</></term>
-     <listitem>
-      <para>
-       The reverse of the <function>compress</function> method.  Converts the
-       index representation of the data item into a format that can be
-       manipulated by the database.
-      </para>
-
-      <para>
-        The <acronym>SQL</> declaration of the function must look like this:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION my_decompress(internal)
-RETURNS internal
-AS 'MODULE_PATHNAME'
-LANGUAGE C STRICT;
-</programlisting>
-
-        And the matching code in the C module could then follow this skeleton:
-
-<programlisting>
-Datum       my_decompress(PG_FUNCTION_ARGS);
-PG_FUNCTION_INFO_V1(my_decompress);
-
-Datum
-my_decompress(PG_FUNCTION_ARGS)
-{
-    PG_RETURN_POINTER(PG_GETARG_POINTER(0));
-}
-</programlisting>
-
-        The above skeleton is suitable for the case where no decompression
-        is needed.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>penalty</></term>
-     <listitem>
-      <para>
-       Returns a value indicating the <quote>cost</quote> of inserting the new
-       entry into a particular branch of the tree.  Items will be inserted
-       down the path of least <function>penalty</function> in the tree.
-      </para>
-
-      <para>
-        The <acronym>SQL</> declaration of the function must look like this:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION my_penalty(internal, internal, internal)
-RETURNS internal
-AS 'MODULE_PATHNAME'
-LANGUAGE C STRICT;  -- in some cases penalty functions need not be strict
-</programlisting>
-
-        And the matching code in the C module could then follow this skeleton:
-
-<programlisting>
-Datum       my_penalty(PG_FUNCTION_ARGS);
-PG_FUNCTION_INFO_V1(my_penalty);
-
-Datum
-my_penalty(PG_FUNCTION_ARGS)
-{
-    GISTENTRY  *origentry = (GISTENTRY *) PG_GETARG_POINTER(0);
-    GISTENTRY  *newentry = (GISTENTRY *) PG_GETARG_POINTER(1);
-    float      *penalty = (float *) PG_GETARG_POINTER(2);
-    data_type  *orig = DatumGetDataType(origentry-&gt;key);
-    data_type  *new = DatumGetDataType(newentry-&gt;key);
-
-    *penalty = my_penalty_implementation(orig, new);
-    PG_RETURN_POINTER(penalty);
-}
-</programlisting>
-      </para>
-
-      <para>
-        The <function>penalty</> function is crucial to good performance of
-        the index. It'll get used at insertion time to determine which branch
-        to follow when choosing where to add the new entry in the tree. At
-        query time, the more balanced the index, the quicker the lookup.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>picksplit</></term>
-     <listitem>
-      <para>
-       When an index page split is necessary, this function decides which
-       entries on the page are to stay on the old page, and which are to move
-       to the new page.
-      </para>
-
-      <para>
-        The <acronym>SQL</> declaration of the function must look like this:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION my_picksplit(internal, internal)
-RETURNS internal
-AS 'MODULE_PATHNAME'
-LANGUAGE C STRICT;
-</programlisting>
-
-        And the matching code in the C module could then follow this skeleton:
-
-<programlisting>
-Datum       my_picksplit(PG_FUNCTION_ARGS);
-PG_FUNCTION_INFO_V1(my_picksplit);
-
-Datum
-my_picksplit(PG_FUNCTION_ARGS)
-{
-    GistEntryVector *entryvec = (GistEntryVector *) PG_GETARG_POINTER(0);
-    OffsetNumber maxoff = entryvec-&gt;n - 1;
-    GISTENTRY  *ent = entryvec-&gt;vector;
-    GIST_SPLITVEC *v = (GIST_SPLITVEC *) PG_GETARG_POINTER(1);
-    int         i,
-                nbytes;
-    OffsetNumber *left,
-               *right;
-    data_type  *tmp_union;
-    data_type  *unionL;
-    data_type  *unionR;
-    GISTENTRY **raw_entryvec;
-
-    maxoff = entryvec-&gt;n - 1;
-    nbytes = (maxoff + 1) * sizeof(OffsetNumber);
-
-    v-&gt;spl_left = (OffsetNumber *) palloc(nbytes);
-    left = v-&gt;spl_left;
-    v-&gt;spl_nleft = 0;
-
-    v-&gt;spl_right = (OffsetNumber *) palloc(nbytes);
-    right = v-&gt;spl_right;
-    v-&gt;spl_nright = 0;
-
-    unionL = NULL;
-    unionR = NULL;
-
-    /* Initialize the raw entry vector. */
-    raw_entryvec = (GISTENTRY **) malloc(entryvec-&gt;n * sizeof(void *));
-    for (i = FirstOffsetNumber; i &lt;= maxoff; i = OffsetNumberNext(i))
-        raw_entryvec[i] = &amp;(entryvec-&gt;vector[i]);
-
-    for (i = FirstOffsetNumber; i &lt;= maxoff; i = OffsetNumberNext(i))
-    {
-        int         real_index = raw_entryvec[i] - entryvec-&gt;vector;
-
-        tmp_union = DatumGetDataType(entryvec-&gt;vector[real_index].key);
-        Assert(tmp_union != NULL);
-
-        /*
-         * Choose where to put the index entries and update unionL and unionR
-         * accordingly. Append the entries to either v_spl_left or
-         * v_spl_right, and care about the counters.
-         */
-
-        if (my_choice_is_left(unionL, curl, unionR, curr))
-        {
-            if (unionL == NULL)
-                unionL = tmp_union;
-            else
-                unionL = my_union_implementation(unionL, tmp_union);
-
-            *left = real_index;
-            ++left;
-            ++(v-&gt;spl_nleft);
-        }
-        else
-        {
-            /*
-             * Same on the right
-             */
-        }
-    }
-
-    v-&gt;spl_ldatum = DataTypeGetDatum(unionL);
-    v-&gt;spl_rdatum = DataTypeGetDatum(unionR);
-    PG_RETURN_POINTER(v);
-}
-</programlisting>
-      </para>
-
-      <para>
-        Like <function>penalty</>, the <function>picksplit</> function
-        is crucial to good performance of the index.  Designing suitable
-        <function>penalty</> and <function>picksplit</> implementations
-        is where the challenge of implementing well-performing
-        <acronym>GiST</> indexes lies.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>same</></term>
-     <listitem>
-      <para>
-       Returns true if two index entries are identical, false otherwise.
-      </para>
-
-      <para>
-        The <acronym>SQL</> declaration of the function must look like this:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION my_same(internal, internal, internal)
-RETURNS internal
-AS 'MODULE_PATHNAME'
-LANGUAGE C STRICT;
-</programlisting>
-
-        And the matching code in the C module could then follow this skeleton:
-
-<programlisting>
-Datum       my_same(PG_FUNCTION_ARGS);
-PG_FUNCTION_INFO_V1(my_same);
-
-Datum
-my_same(PG_FUNCTION_ARGS)
-{
-    prefix_range *v1 = PG_GETARG_PREFIX_RANGE_P(0);
-    prefix_range *v2 = PG_GETARG_PREFIX_RANGE_P(1);
-    bool       *result = (bool *) PG_GETARG_POINTER(2);
-
-    *result = my_eq(v1, v2);
-    PG_RETURN_POINTER(result);
-}
-</programlisting>
-
-        For historical reasons, the <function>same</> function doesn't
-        just return a Boolean result; instead it has to store the flag
-        at the location indicated by the third argument.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><function>distance</></term>
-     <listitem>
-      <para>
-       Given an index entry <literal>p</> and a query value <literal>q</>,
-       this function determines the index entry's
-       <quote>distance</> from the query value.  This function must be
-       supplied if the operator class contains any ordering operators.
-       A query using the ordering operator will be implemented by returning
-       index entries with the smallest <quote>distance</> values first,
-       so the results must be consistent with the operator's semantics.
-       For a leaf index entry the result just represents the distance to
-       the index entry; for an internal tree node, the result must be the
-       smallest distance that any child entry could have.
-      </para>
-
-      <para>
-        The <acronym>SQL</> declaration of the function must look like this:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION my_distance(internal, data_type, smallint, oid)
-RETURNS float8
-AS 'MODULE_PATHNAME'
-LANGUAGE C STRICT;
-</programlisting>
-
-        And the matching code in the C module could then follow this skeleton:
-
-<programlisting>
-Datum       my_distance(PG_FUNCTION_ARGS);
-PG_FUNCTION_INFO_V1(my_distance);
-
-Datum
-my_distance(PG_FUNCTION_ARGS)
-{
-    GISTENTRY  *entry = (GISTENTRY *) PG_GETARG_POINTER(0);
-    data_type  *query = PG_GETARG_DATA_TYPE_P(1);
-    StrategyNumber strategy = (StrategyNumber) PG_GETARG_UINT16(2);
-    /* Oid subtype = PG_GETARG_OID(3); */
-    data_type  *key = DatumGetDataType(entry-&gt;key);
-    double      retval;
-
-    /*
-     * determine return value as a function of strategy, key and query.
-     */
-
-    PG_RETURN_FLOAT8(retval);
-}
-</programlisting>
-
-       The arguments to the <function>distance</> function are identical to
-       the arguments of the <function>consistent</> function, except that no
-       recheck flag is used.  The distance to a leaf index entry must always
-       be determined exactly, since there is no way to re-order the tuples
-       once they are returned.  Some approximation is allowed when determining
-       the distance to an internal tree node, so long as the result is never
-       greater than any child's actual distance.  Thus, for example, distance
-       to a bounding box is usually sufficient in geometric applications.  The
-       result value can be any finite <type>float8</> value.  (Infinity and
-       minus infinity are used internally to handle cases such as nulls, so it
-       is not recommended that <function>distance</> functions return these
-       values.)
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-  </variablelist>
-
-</sect1>
-
-<sect1 id="gist-examples">
- <title>Examples</title>
-
-&common;
- <para>
-<!## PG>
-  The <productname>PostgreSQL</productname> source distribution includes
-<!## end>
-<!## XC>
-  The <productname>Postgres-XC</productname> source distribution includes
-<!## end>
-<!## XL>
-  The <productname>Postgres-XL</productname> source distribution includes
-<!## end>
-  several examples of index methods implemented using
-  <acronym>GiST</acronym>.  The core system currently provides text search
-  support (indexing for <type>tsvector</> and <type>tsquery</>) as well as
-  R-Tree equivalent functionality for some of the built-in geometric data types
-  (see <filename>src/backend/access/gist/gistproc.c</>).  The following
-  <filename>contrib</> modules also contain <acronym>GiST</acronym>
-  operator classes:
-
- <variablelist>
-  <varlistentry>
-   <term><filename>btree_gist</></term>
-   <listitem>
-    <para>B-tree equivalent functionality for several data types</para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><filename>cube</></term>
-   <listitem>
-    <para>Indexing for multidimensional cubes</para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><filename>hstore</></term>
-   <listitem>
-    <para>Module for storing (key, value) pairs</para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><filename>intarray</></term>
-   <listitem>
-    <para>RD-Tree for one-dimensional array of int4 values</para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><filename>ltree</></term>
-   <listitem>
-    <para>Indexing for tree-like structures</para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><filename>pg_trgm</></term>
-   <listitem>
-    <para>Text similarity using trigram matching</para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><filename>seg</></term>
-   <listitem>
-    <para>Indexing for <quote>float ranges</quote></para>
-   </listitem>
-  </varlistentry>
- </variablelist>
- </para>
-
-</sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/high-availability.sgmlin b/doc-xc/src/sgml/high-availability.sgmlin
deleted file mode 100644
index e67370110a..0000000000
--- a/doc-xc/src/sgml/high-availability.sgmlin
+++ /dev/null
@@ -1,2183 +0,0 @@
-<!-- doc/src/sgml/high-availability.sgml -->
-
-<chapter id="high-availability">
- <title>High Availability, Load Balancing, and Replication</title>
-
- <indexterm><primary>high availability</></>
- <indexterm><primary>failover</></>
- <indexterm><primary>replication</></>
- <indexterm><primary>load balancing</></>
- <indexterm><primary>clustering</></>
- <indexterm><primary>data partitioning</></>
-
-&common;
- <para>
-  Database servers can work together to allow a second server to
-  take over quickly if the primary server fails (high
-  availability), or to allow several computers to serve the same
-  data (load balancing).  Ideally, database servers could work
-  together seamlessly.  Web servers serving static web pages can
-  be combined quite easily by merely load-balancing web requests
-  to multiple machines.  In fact, read-only database servers can
-  be combined relatively easily too.  Unfortunately, most database
-  servers have a read/write mix of requests, and read/write servers
-  are much harder to combine.  This is because though read-only
-  data needs to be placed on each server only once, a write to any
-  server has to be propagated to all servers so that future read
-  requests to those servers return consistent results.
- </para>
-
- <para>
-  This synchronization problem is the fundamental difficulty for
-  servers working together.  Because there is no single solution
-  that eliminates the impact of the sync problem for all use cases,
-  there are multiple solutions.  Each solution addresses this
-  problem in a different way, and minimizes its impact for a specific
-  workload.
- </para>
-
- <para>
-  Some solutions deal with synchronization by allowing only one
-  server to modify the data.  Servers that can modify data are
-  called read/write, <firstterm>master</> or <firstterm>primary</> servers.
-  Servers that track changes in the master are called <firstterm>standby</>
-  or <firstterm>slave</> servers. A standby server that cannot be connected
-  to until it is promoted to a master server is called a <firstterm>warm
-  standby</> server, and one that can accept connections and serves read-only
-  queries is called a <firstterm>hot standby</> server.
- </para>
-
- <para>
-  Some solutions are synchronous,
-  meaning that a data-modifying transaction is not considered
-  committed until all servers have committed the transaction.  This
-  guarantees that a failover will not lose any data and that all
-  load-balanced servers will return consistent results no matter
-  which server is queried. In contrast, asynchronous solutions allow some
-  delay between the time of a commit and its propagation to the other servers,
-  opening the possibility that some transactions might be lost in
-  the switch to a backup server, and that load balanced servers
-  might return slightly stale results.  Asynchronous communication
-  is used when synchronous would be too slow.
- </para>
-
- <para>
-  Solutions can also be categorized by their granularity.  Some solutions
-  can deal only with an entire database server, while others allow control
-  at the per-table or per-database level.
- </para>
-
- <para>
-  Performance must be considered in any choice.  There is usually a
-  trade-off between functionality and
-  performance.  For example, a fully synchronous solution over a slow
-  network might cut performance by more than half, while an asynchronous
-  one might have a minimal performance impact.
- </para>
-
- <para>
-  The remainder of this section outlines various failover, replication,
-  and load balancing solutions.  A <ulink
-  url="http://www.postgres-r.org/documentation/terms">glossary</ulink> is
-  also available.
- </para>
-
- <sect1 id="different-replication-solutions">
- <title>Comparison of Different Solutions</title>
-
- <variablelist>
-
-  <varlistentry>
-   <term>Shared Disk Failover</term>
-   <listitem>
-&pgnotice;
-
-    <para>
-     Shared disk failover avoids synchronization overhead by having only one
-     copy of the database.  It uses a single disk array that is shared by
-     multiple servers.  If the main database server fails, the standby server
-     is able to mount and start the database as though it were recovering from
-     a database crash.  This allows rapid failover with no data loss.
-    </para>
-
-    <para>
-     Shared hardware functionality is common in network storage devices.
-     Using a network file system is also possible, though care must be
-     taken that the file system has full <acronym>POSIX</> behavior (see <xref
-     linkend="creating-cluster-nfs">).  One significant limitation of this
-     method is that if the shared disk array fails or becomes corrupt, the
-     primary and standby servers are both nonfunctional.  Another issue is
-     that the standby server should never access the shared storage while
-     the primary server is running.
-    </para>
-
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>File System (Block-Device) Replication</term>
-   <listitem>
-
-    <para>
-     A modified version of shared hardware functionality is file system
-     replication, where all changes to a file system are mirrored to a file
-     system residing on another computer.  The only restriction is that
-     the mirroring must be done in a way that ensures the standby server
-     has a consistent copy of the file system &mdash; specifically, writes
-     to the standby must be done in the same order as those on the master.
-     <productname>DRBD</> is a popular file system replication solution
-     for Linux.
-    </para>
-
-<!--
-https://forge.continuent.org/pipermail/sequoia/2006-November/004070.html
-
-Oracle RAC is a shared disk approach and just send cache invalidations
-to other nodes but not actual data. As the disk is shared, data is
-only committed once to disk and there is a distributed locking
-protocol to make nodes agree on a serializable transactional order.
--->
-
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Warm and Hot Standby Using Point-In-Time Recovery (<acronym>PITR</>)</term>
-   <listitem>
-
-    <para>
-     Warm and hot standby servers can be kept current by reading a
-     stream of write-ahead log (<acronym>WAL</>)
-     records.  If the main server fails, the standby contains
-     almost all of the data of the main server, and can be quickly
-     made the new master database server.  This is asynchronous and
-     can only be done for the entire database server.
-    </para>
-    <para>
-     A PITR standby server can be implemented using file-based log shipping
-     (<xref linkend="warm-standby">) or streaming replication (see
-     <xref linkend="streaming-replication">), or a combination of both. For
-     information on hot standby, see <xref linkend="hot-standby">.
-     A PITR standby server can be implemented using file-based log shipping
-     (<xref linkend="warm-standby">).
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Trigger-Based Master-Standby Replication</term>
-   <listitem>
-
-    <para>
-     A master-standby replication setup sends all data modification
-     queries to the master server.  The master server asynchronously
-     sends data changes to the standby server.  The standby can answer
-     read-only queries while the master server is running.  The
-     standby server is ideal for data warehouse queries.
-    </para>
-
-    <para>
-     <productname>Slony-I</> is an example of this type of replication, with per-table
-     granularity, and support for multiple standby servers.  Because it
-     updates the standby server asynchronously (in batches), there is
-     possible data loss during fail over.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Statement-Based Replication Middleware</term>
-   <listitem>
-
-    <para>
-     With statement-based replication middleware, a program intercepts
-     every SQL query and sends it to one or all servers.  Each server
-     operates independently.  Read-write queries must be sent to all servers,
-     so that every server receives any changes.  But read-only queries can be
-     sent to just one server, allowing the read workload to be distributed
-     among them.
-    </para>
-
-    <para>
-     If queries are simply broadcast unmodified, functions like
-     <function>random()</>, <function>CURRENT_TIMESTAMP</>, and
-     sequences can have different values on different servers.
-     This is because each server operates independently, and because
-     SQL queries are broadcast (and not actual modified rows).  If
-     this is unacceptable, either the middleware or the application
-     must query such values from a single server and then use those
-     values in write queries.  Another option is to use this replication
-     option with a traditional master-standby setup, i.e. data modification
-     queries are sent only to the master and are propagated to the
-     standby servers via master-standby replication, not by the replication
-     middleware.  Care must also be taken that all
-     transactions either commit or abort on all servers, perhaps
-     using two-phase commit (<xref linkend="sql-prepare-transaction">
-     and <xref linkend="sql-commit-prepared">.
-     <productname>Pgpool-II</> and <productname>Continuent Tungsten</>
-     are examples of this type of replication.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Asynchronous Multimaster Replication</term>
-   <listitem>
-
-    <para>
-     For servers that are not regularly connected, like laptops or
-     remote servers, keeping data consistent among servers is a
-     challenge.  Using asynchronous multimaster replication, each
-     server works independently, and periodically communicates with
-     the other servers to identify conflicting transactions.  The
-     conflicts can be resolved by users or conflict resolution rules.
-     Bucardo is an example of this type of replication.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Synchronous Multimaster Replication</term>
-   <listitem>
-
-    <para>
-     In synchronous multimaster replication, each server can accept
-     write requests, and modified data is transmitted from the
-     original server to every other server before each transaction
-     commits.  Heavy write activity can cause excessive locking,
-     leading to poor performance.  In fact, write performance is
-     often worse than that of a single server.  Read requests can
-     be sent to any server.  Some implementations use shared disk
-     to reduce the communication overhead.  Synchronous multimaster
-     replication is best for mostly read workloads, though its big
-     advantage is that any server can accept write requests &mdash;
-     there is no need to partition workloads between master and
-     standby servers, and because the data changes are sent from one
-     server to another, there is no problem with non-deterministic
-     functions like <function>random()</>.
-    </para>
-
-    <para>
-     <productname>PostgreSQL</> does not offer this type of replication,
-     though <productname>PostgreSQL</> two-phase commit (<xref
-     linkend="sql-prepare-transaction"> and <xref
-     linkend="sql-commit-prepared">)
-     can be used to implement this in application code or middleware.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Commercial Solutions</term>
-   <listitem>
-
-    <para>
-     Because <productname>PostgreSQL</> is open source and easily
-     extended, a number of companies have taken <productname>PostgreSQL</>
-     and created commercial closed-source solutions with unique
-     failover, replication, and load balancing capabilities.
-    </para>
-   </listitem>
-  </varlistentry>
-
- </variablelist>
-
- <para>
-  <xref linkend="high-availability-matrix"> summarizes
-  the capabilities of the various solutions listed above.
- </para>
-
- <table id="high-availability-matrix">
-  <title>High Availability, Load Balancing, and Replication Feature Matrix</title>
-  <tgroup cols="8">
-   <thead>
-    <row>
-     <entry>Feature</entry>
-     <entry>Shared Disk Failover</entry>
-     <entry>File System Replication</entry>
-     <entry>Hot/Warm Standby Using PITR</entry>
-     <entry>Trigger-Based Master-Standby Replication</entry>
-     <entry>Statement-Based Replication Middleware</entry>
-     <entry>Asynchronous Multimaster Replication</entry>
-     <entry>Synchronous Multimaster Replication</entry>
-    </row>
-   </thead>
-
-   <tbody>
-
-    <row>
-     <entry>Most Common Implementation</entry>
-     <entry align="center">NAS</entry>
-     <entry align="center">DRBD</entry>
-     <entry align="center">PITR</entry>
-     <entry align="center">Slony</entry>
-     <entry align="center">pgpool-II</entry>
-     <entry align="center">Bucardo</entry>
-     <entry align="center"></entry>
-    </row>
-
-    <row>
-     <entry>Communication Method</entry>
-     <entry align="center">shared disk</entry>
-     <entry align="center">disk blocks</entry>
-     <entry align="center">WAL</entry>
-     <entry align="center">table rows</entry>
-     <entry align="center">SQL</entry>
-     <entry align="center">table rows</entry>
-     <entry align="center">table rows and row locks</entry>
-    </row>
-
-    <row>
-     <entry>No special hardware required</entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-    </row>
-
-    <row>
-     <entry>Allows multiple master servers</entry>
-     <entry align="center"></entry>
-     <entry align="center"></entry>
-     <entry align="center"></entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-    </row>
-
-    <row>
-     <entry>No master server overhead</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center"></entry>
-     <entry align="center"></entry>
-    </row>
-
-    <row>
-     <entry>No waiting for multiple servers</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center"></entry>
-    </row>
-
-    <row>
-     <entry>Master failure will never lose data</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center"></entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-    </row>
-
-    <row>
-     <entry>Standby accept read-only queries</entry>
-     <entry align="center"></entry>
-     <entry align="center"></entry>
-     <entry align="center">Hot only</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-    </row>
-
-    <row>
-     <entry>Per-table granularity</entry>
-     <entry align="center"></entry>
-     <entry align="center"></entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-    </row>
-
-    <row>
-     <entry>No conflict resolution necessary</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center">&bull;</entry>
-     <entry align="center"></entry>
-     <entry align="center"></entry>
-     <entry align="center">&bull;</entry>
-    </row>
-
-   </tbody>
-  </tgroup>
- </table>
-
- <para>
-  There are a few solutions that do not fit into the above categories:
- </para>
-
- <variablelist>
-
-  <varlistentry>
-   <term>Data Partitioning</term>
-   <listitem>
-
-    <para>
-     Data partitioning splits tables into data sets.  Each set can
-     be modified by only one server.  For example, data can be
-     partitioned by offices, e.g., London and Paris, with a server
-     in each office.  If queries combining London and Paris data
-     are necessary, an application can query both servers, or
-     master/standby replication can be used to keep a read-only copy
-     of the other office's data on each server.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Multiple-Server Parallel Query Execution</term>
-   <listitem>
-
-    <para>
-     Many of the above solutions allow multiple servers to handle multiple
-     queries, but none allow a single query to use multiple servers to
-     complete faster.  This solution allows multiple servers to work
-     concurrently on a single query.  It is usually accomplished by
-     splitting the data among servers and having each server execute its
-     part of the query and return results to a central server where they
-     are combined and returned to the user.  <productname>Pgpool-II</>
-     has this capability.  Also, this can be implemented using the
-     <productname>PL/Proxy</> tool set.
-    </para>
-
-   </listitem>
-  </varlistentry>
-
- </variablelist>
-
- </sect1>
-
- <sect1 id="warm-standby">
- <title>Log-Shipping Standby Servers</title>
-
-&pgnotice;
-
-  <para>
-   Continuous archiving can be used to create a <firstterm>high
-   availability</> (HA) cluster configuration with one or more
-   <firstterm>standby servers</> ready to take over operations if the
-   primary server fails. This capability is widely referred to as
-   <firstterm>warm standby</> or <firstterm>log shipping</>.
-  </para>
-
-  <para>
-   The primary and standby server work together to provide this capability,
-   though the servers are only loosely coupled. The primary server operates
-   in continuous archiving mode, while each standby server operates in
-   continuous recovery mode, reading the WAL files from the primary. No
-   changes to the database tables are required to enable this capability,
-   so it offers low administration overhead compared to some other
-   replication solutions. This configuration also has relatively low
-   performance impact on the primary server.
-  </para>
-
-  <para>
-   Directly moving WAL records from one database server to another
-   is typically described as log shipping. <productname>PostgreSQL</>
-   implements file-based log shipping by transferring WAL records
-   one file (WAL segment) at a time. WAL files (16MB) can be
-   shipped easily and cheaply over any distance, whether it be to an
-   adjacent system, another system at the same site, or another system on
-   the far side of the globe. The bandwidth required for this technique
-   varies according to the transaction rate of the primary server.
-   Record-based log shipping is more granular and streams WAL changes
-   incrementally over a network connection (see <xref
-   linkend="streaming-replication">).
-  </para>
-
-  <para>
-   It should be noted that log shipping is asynchronous, i.e., the WAL
-   records are shipped after transaction commit. As a result, there is a
-   window for data loss should the primary server suffer a catastrophic
-   failure; transactions not yet shipped will be lost.  The size of the
-   data loss window in file-based log shipping can be limited by use of the
-   <varname>archive_timeout</varname> parameter, which can be set as low
-   as a few seconds.  However such a low setting will
-   substantially increase the bandwidth required for file shipping.
-   Streaming replication (see <xref linkend="streaming-replication">)
-   allows a much smaller window of data loss.
-  </para>
-
-  <para>
-   Recovery performance is sufficiently good that the standby will
-   typically be only moments away from full
-   availability once it has been activated. As a result, this is called
-   a warm standby configuration which offers high
-   availability. Restoring a server from an archived base backup and
-   rollforward will take considerably longer, so that technique only
-   offers a solution for disaster recovery, not high availability.
-   A standby server can also be used for read-only queries, in which case
-   it is called a Hot Standby server. See <xref linkend="hot-standby"> for
-   more information.
-  </para>
-
-  <indexterm zone="high-availability">
-   <primary>warm standby</primary>
-  </indexterm>
-
-  <indexterm zone="high-availability">
-   <primary>PITR standby</primary>
-  </indexterm>
-
-  <indexterm zone="high-availability">
-   <primary>standby server</primary>
-  </indexterm>
-
-  <indexterm zone="high-availability">
-   <primary>log shipping</primary>
-  </indexterm>
-
-  <indexterm zone="high-availability">
-   <primary>witness server</primary>
-  </indexterm>
-
-  <indexterm zone="high-availability">
-   <primary>STONITH</primary>
-  </indexterm>
-
-  <sect2 id="standby-planning">
-   <title>Planning</title>
-&pgnotice;
-
-   <para>
-    It is usually wise to create the primary and standby servers
-    so that they are as similar as possible, at least from the
-    perspective of the database server.  In particular, the path names
-    associated with tablespaces will be passed across unmodified, so both
-    primary and standby servers must have the same mount paths for
-    tablespaces if that feature is used.  Keep in mind that if
-    <xref linkend="sql-createtablespace">
-    is executed on the primary, any new mount point needed for it must
-    be created on the primary and all standby servers before the command
-    is executed. Hardware need not be exactly the same, but experience shows
-    that maintaining two identical systems is easier than maintaining two
-    dissimilar ones over the lifetime of the application and system.
-    In any case the hardware architecture must be the same &mdash; shipping
-    from, say, a 32-bit to a 64-bit system will not work.
-   </para>
-
-   <para>
-    In general, log shipping between servers running different major
-    <productname>PostgreSQL</> release
-    levels is not possible. It is the policy of the PostgreSQL Global
-    Development Group not to make changes to disk formats during minor release
-    upgrades, so it is likely that running different minor release levels
-    on primary and standby servers will work successfully. However, no
-    formal support for that is offered and you are advised to keep primary
-    and standby servers at the same release level as much as possible.
-    When updating to a new minor release, the safest policy is to update
-    the standby servers first &mdash; a new minor release is more likely
-    to be able to read WAL files from a previous minor release than vice
-    versa.
-   </para>
-
-  </sect2>
-
-  <sect2 id="standby-server-operation">
-   <title>Standby Server Operation</title>
-&pgnotice;
-
-   <para>
-    In standby mode, the server continuously applies WAL received from the
-    master server. The standby server can read WAL from a WAL archive
-    (see <xref linkend="restore-command">) or directly from the master
-    over a TCP connection (streaming replication). The standby server will
-    also attempt to restore any WAL found in the standby cluster's
-    <filename>pg_xlog</> directory. That typically happens after a server
-    restart, when the standby replays again WAL that was streamed from the
-    master before the restart, but you can also manually copy files to
-    <filename>pg_xlog</> at any time to have them replayed.
-   </para>
-
-   <para>
-    At startup, the standby begins by restoring all WAL available in the
-    archive location, calling <varname>restore_command</>. Once it
-    reaches the end of WAL available there and <varname>restore_command</>
-    fails, it tries to restore any WAL available in the <filename>pg_xlog</> directory.
-    If that fails, and streaming replication has been configured, the
-    standby tries to connect to the primary server and start streaming WAL
-    from the last valid record found in archive or <filename>pg_xlog</>. If that fails
-    or streaming replication is not configured, or if the connection is
-    later disconnected, the standby goes back to step 1 and tries to
-    restore the file from the archive again. This loop of retries from the
-    archive, <filename>pg_xlog</>, and via streaming replication goes on until the server
-    is stopped or failover is triggered by a trigger file.
-   </para>
-
-   <para>
-    Standby mode is exited and the server switches to normal operation
-    when <command>pg_ctl promote</> is run or a trigger file is found
-    (<varname>trigger_file</>). Before failover,
-    any WAL immediately available in the archive or in <filename>pg_xlog</> will be
-    restored, but no attempt is made to connect to the master.
-   </para>
-  </sect2>
-
-  <sect2 id="preparing-master-for-standby">
-   <title>Preparing the Master for Standby Servers</title>
-&pgnotice;
-
-   <para>
-    Set up continuous archiving on the primary to an archive directory
-    accessible from the standby, as described
-    in <xref linkend="continuous-archiving">. The archive location should be
-    accessible from the standby even when the master is down, i.e. it should
-    reside on the standby server itself or another trusted server, not on
-    the master server.
-   </para>
-
-   <para>
-    If you want to use streaming replication, set up authentication on the
-    primary server to allow replication connections from the standby
-    server(s); that is, create a role and provide a suitable entry or
-    entries in <filename>pg_hba.conf</> with the database field set to
-    <literal>replication</>.  Also ensure <varname>max_wal_senders</> is set
-    to a sufficiently large value in the configuration file of the primary
-    server.
-   </para>
-
-   <para>
-    Take a base backup as described in <xref linkend="backup-base-backup">
-    to bootstrap the standby server.
-   </para>
-  </sect2>
-
-  <sect2 id="standby-server-setup">
-   <title>Setting Up a Standby Server</title>
-&pgnotice;
-
-   <para>
-    To set up the standby server, restore the base backup taken from primary
-    server (see <xref linkend="backup-pitr-recovery">). Create a recovery
-    command file <filename>recovery.conf</> in the standby's cluster data
-    directory, and turn on <varname>standby_mode</>. Set
-    <varname>restore_command</> to a simple command to copy files from
-    the WAL archive. If you plan to have multiple standby servers for high
-    availability purposes, set <varname>recovery_target_timeline</> to
-    <literal>latest</>, to make the standby server follow the timeline change
-    that occurs at failover to another standby.
-   </para>
-
-   <note>
-     <para>
-     Do not use pg_standby or similar tools with the built-in standby mode
-     described here. <varname>restore_command</> should return immediately
-     if the file does not exist; the server will retry the command again if
-     necessary. See <xref linkend="log-shipping-alternative">
-     for using tools like pg_standby.
-    </para>
-   </note>
-
-   <para>
-     If you want to use streaming replication, fill in
-     <varname>primary_conninfo</> with a libpq connection string, including
-     the host name (or IP address) and any additional details needed to
-     connect to the primary server. If the primary needs a password for
-     authentication, the password needs to be specified in
-     <varname>primary_conninfo</> as well.
-   </para>
-
-   <para>
-    If you're setting up the standby server for high availability purposes,
-    set up WAL archiving, connections and authentication like the primary
-    server, because the standby server will work as a primary server after
-    failover.
-   </para>
-
-   <para>
-    If you're using a WAL archive, its size can be minimized using the <xref
-    linkend="archive-cleanup-command"> parameter to remove files that are no
-    longer required by the standby server.
-    The <application>pg_archivecleanup</> utility is designed specifically to
-    be used with <varname>archive_cleanup_command</> in typical single-standby
-    configurations, see <xref linkend="pgarchivecleanup">.
-    Note however, that if you're using the archive for backup purposes, you
-    need to retain files needed to recover from at least the latest base
-    backup, even if they're no longer needed by the standby.
-   </para>
-
-   <para>
-    A simple example of a <filename>recovery.conf</> is:
-<programlisting>
-standby_mode = 'on'
-primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
-restore_command = 'cp /path/to/archive/%f %p'
-archive_cleanup_command = 'pg_archivecleanup /path/to/archive %r'
-</programlisting>
-   </para>
-
-   <para>
-    You can have any number of standby servers, but if you use streaming
-    replication, make sure you set <varname>max_wal_senders</> high enough in
-    the primary to allow them to be connected simultaneously.
-   </para>
-
-  </sect2>
-
-<!-- No streaming replciation for XC so far -->
-  <sect2 id="streaming-replication">
-   <title>Streaming Replication</title>
-
-   <indexterm zone="high-availability">
-    <primary>Streaming Replication</primary>
-   </indexterm>
-&pgnotice;
-
-   <para>
-    Streaming replication allows a standby server to stay more up-to-date
-    than is possible with file-based log shipping. The standby connects
-    to the primary, which streams WAL records to the standby as they're
-    generated, without waiting for the WAL file to be filled.
-   </para>
-
-   <para>
-    Streaming replication is asynchronous, so there is still a small delay
-    between committing a transaction in the primary and for the changes to
-    become visible in the standby. The delay is however much smaller than with
-    file-based log shipping, typically under one second assuming the standby
-    is powerful enough to keep up with the load. With streaming replication,
-    <varname>archive_timeout</> is not required to reduce the data loss
-    window.
-   </para>
-
-   <para>
-    If you use streaming replication without file-based continuous
-    archiving, you have to set <varname>wal_keep_segments</> in the master
-    to a value high enough to ensure that old WAL segments are not recycled
-    too early, while the standby might still need them to catch up. If the
-    standby falls behind too much, it needs to be reinitialized from a new
-    base backup. If you set up a WAL archive that's accessible from the
-    standby, <varname>wal_keep_segments</> is not required as the standby can always
-    use the archive to catch up.
-   </para>
-
-   <para>
-    To use streaming replication, set up a file-based log-shipping standby
-    server as described in <xref linkend="warm-standby">. The step that
-    turns a file-based log-shipping standby into streaming replication
-    standby is setting <varname>primary_conninfo</> setting in the
-    <filename>recovery.conf</> file to point to the primary server. Set
-    <xref linkend="guc-listen-addresses"> and authentication options
-    (see <filename>pg_hba.conf</>) on the primary so that the standby server
-    can connect to the <literal>replication</> pseudo-database on the primary
-    server (see <xref linkend="streaming-replication-authentication">).
-   </para>
-
-   <para>
-    On systems that support the keepalive socket option, setting
-    <xref linkend="guc-tcp-keepalives-idle">,
-    <xref linkend="guc-tcp-keepalives-interval"> and
-    <xref linkend="guc-tcp-keepalives-count"> helps the primary promptly
-    notice a broken connection.
-   </para>
-
-   <para>
-    Set the maximum number of concurrent connections from the standby servers
-    (see <xref linkend="guc-max-wal-senders"> for details).
-   </para>
-
-   <para>
-    When the standby is started and <varname>primary_conninfo</> is set
-    correctly, the standby will connect to the primary after replaying all
-    WAL files available in the archive. If the connection is established
-    successfully, you will see a walreceiver process in the standby, and
-    a corresponding walsender process in the primary.
-   </para>
-
-   <sect3 id="streaming-replication-authentication">
-    <title>Authentication</title>
-&pgnotice;
-    <para>
-     It is very important that the access privileges for replication be set up
-     so that only trusted users can read the WAL stream, because it is
-     easy to extract privileged information from it.  Standby servers must
-     authenticate to the primary as an account that has the
-     <literal>REPLICATION</> privilege. So a role with the
-     <literal>REPLICATION</> and <literal>LOGIN</> privileges needs to be
-     created on the primary.
-    </para>
-
-    <note>
-     <para>
-      It is recommended that a dedicated user account is used for replication.
-      While the <literal>REPLICATION</> privilege is granted to superuser
-      accounts by default, it is not recommended to use superuser accounts
-      for replication. While <literal>REPLICATION</> privilege gives very high
-      permissions, it does not allow the user to modify any data on the
-      primary system, which the <literal>SUPERUSER</> privilege does.
-     </para>
-    </note>
-
-    <para>
-     Client authentication for replication is controlled by a
-     <filename>pg_hba.conf</> record specifying <literal>replication</> in the
-     <replaceable>database</> field. For example, if the standby is running on
-     host IP <literal>192.168.1.100</> and the account name for replication
-     is <literal>foo</>, the administrator can add the following line to the
-     <filename>pg_hba.conf</> file on the primary:
-
-<programlisting>
-# Allow the user "foo" from host 192.168.1.100 to connect to the primary
-# as a replication standby if the user's password is correctly supplied.
-#
-# TYPE  DATABASE        USER            ADDRESS                 METHOD
-host    replication     foo             192.168.1.100/32        md5
-</programlisting>
-    </para>
-    <para>
-     The host name and port number of the primary, connection user name,
-     and password are specified in the <filename>recovery.conf</> file.
-     The password can also be set in the <filename>~/.pgpass</> file on the
-     standby (specify <literal>replication</> in the <replaceable>database</>
-     field).
-     For example, if the primary is running on host IP <literal>192.168.1.50</>,
-     port <literal>5432</literal>, the account name for replication is
-     <literal>foo</>, and the password is <literal>foopass</>, the administrator
-     can add the following line to the <filename>recovery.conf</> file on the
-     standby:
-
-<programlisting>
-# The standby connects to the primary that is running on host 192.168.1.50
-# and port 5432 as the user "foo" whose password is "foopass".
-primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
-</programlisting>
-    </para>
-   </sect3>
-
-   <sect3 id="streaming-replication-monitoring">
-    <title>Monitoring</title>
-&pgnotice;
-    <para>
-     An important health indicator of streaming replication is the amount
-     of WAL records generated in the primary, but not yet applied in the
-     standby. You can calculate this lag by comparing the current WAL write
-     location on the primary with the last WAL location received by the
-     standby. They can be retrieved using
-     <function>pg_current_xlog_location</> on the primary and the
-     <function>pg_last_xlog_receive_location</> on the standby,
-     respectively (see <xref linkend="functions-admin-backup-table"> and
-     <xref linkend="functions-recovery-info-table"> for details).
-     The last WAL receive location in the standby is also displayed in the
-     process status of the WAL receiver process, displayed using the
-     <command>ps</> command (see <xref linkend="monitoring-ps"> for details).
-    </para>
-    <para>
-     You can retrieve a list of WAL sender processes via the
-     <link linkend="monitoring-stats-views-table">
-     <literal>pg_stat_replication</></link> view. Large differences between
-     <function>pg_current_xlog_location</> and <literal>sent_location</> field
-     might indicate that the master server is under heavy load, while
-     differences between <literal>sent_location</> and 
-     <function>pg_last_xlog_receive_location</> on the standby might indicate
-     network delay, or that the standby is under heavy load.
-    </para>
-   </sect3>
-
-  </sect2>
-  <sect2 id="synchronous-replication">
-   <title>Synchronous Replication</title>
-
-   <indexterm zone="high-availability">
-    <primary>Synchronous Replication</primary>
-   </indexterm>
-
-   <para>
-    <productname>PostgreSQL</> streaming replication is asynchronous by
-    default. If the primary server
-    crashes then some transactions that were committed may not have been
-    replicated to the standby server, causing data loss. The amount
-    of data loss is proportional to the replication delay at the time of
-    failover.
-   </para>
-
-   <para>
-    Synchronous replication offers the ability to confirm that all changes
-    made by a transaction have been transferred to one synchronous standby
-    server. This extends the standard level of durability
-    offered by a transaction commit. This level of protection is referred
-    to as 2-safe replication in computer science theory.
-   </para>
-
-   <para>
-    When requesting synchronous replication, each commit of a
-    write transaction will wait until confirmation is
-    received that the commit has been written to the transaction log on disk
-    of both the primary and standby server. The only possibility that data
-    can be lost is if both the primary and the standby suffer crashes at the
-    same time. This can provide a much higher level of durability, though only
-    if the sysadmin is cautious about the placement and management of the two
-    servers.  Waiting for confirmation increases the user's confidence that the
-    changes will not be lost in the event of server crashes but it also
-    necessarily increases the response time for the requesting transaction.
-    The minimum wait time is the roundtrip time between primary to standby.
-   </para>
-
-   <para>
-    Read only transactions and transaction rollbacks need not wait for
-    replies from standby servers. Subtransaction commits do not wait for
-    responses from standby servers, only top-level commits. Long
-    running actions such as data loading or index building do not wait
-    until the very final commit message. All two-phase commit actions
-    require commit waits, including both prepare and commit.
-   </para>
-
-   <sect3 id="synchronous-replication-config">
-    <title>Basic Configuration</title>
-
-   <para>
-    Once streaming replication has been configured, configuring synchronous
-    replication requires only one additional configuration step:
-    <xref linkend="guc-synchronous-standby-names"> must be set to
-    a non-empty value.  <varname>synchronous_commit</> must also be set to
-    <literal>on</>, but since this is the default value, typically no change is
-    required.  This configuration will cause each commit to wait for
-    confirmation that the standby has written the commit record to durable
-    storage, even if that takes a very long time.
-    <varname>synchronous_commit</> can be set by individual
-    users, so can be configured in the configuration file, for particular
-    users or databases, or dynamically by applications, in order to control
-    the durability guarantee on a per-transaction basis.
-   </para>
-
-   <para>
-    After a commit record has been written to disk on the primary, the
-    WAL record is then sent to the standby. The standby sends reply
-    messages each time a new batch of WAL data is written to disk, unless
-    <varname>wal_receiver_status_interval</> is set to zero on the standby.
-    If the standby is the first matching standby, as specified in
-    <varname>synchronous_standby_names</> on the primary, the reply
-    messages from that standby will be used to wake users waiting for
-    confirmation that the commit record has been received. These parameters
-    allow the administrator to specify which standby servers should be
-    synchronous standbys. Note that the configuration of synchronous
-    replication is mainly on the master.
-   </para>
-
-   <para>
-    Users will stop waiting if a fast shutdown is requested.  However, as
-    when using asynchronous replication, the server will does not fully
-    shutdown until all outstanding WAL records are transferred to the currently
-    connected standby servers.
-   </para>
-
-   </sect3>
-
-   <sect3 id="synchronous-replication-performance">
-    <title>Planning for Performance</title>
-
-   <para>
-    Synchronous replication usually requires carefully planned and placed
-    standby servers to ensure applications perform acceptably. Waiting
-    doesn't utilise system resources, but transaction locks continue to be
-    held until the transfer is confirmed. As a result, incautious use of
-    synchronous replication will reduce performance for database
-    applications because of increased response times and higher contention.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</> allows the application developer
-    to specify the durability level required via replication. This can be
-    specified for the system overall, though it can also be specified for
-    specific users or connections, or even individual transactions.
-   </para>
-
-   <para>
-    For example, an application workload might consist of:
-    10% of changes are important customer details, while
-    90% of changes are less important data that the business can more
-    easily survive if it is lost, such as chat messages between users.
-   </para>
-
-   <para>
-    With synchronous replication options specified at the application level
-    (on the primary) we can offer synchronous replication for the most
-    important changes, without slowing down the bulk of the total workload.
-    Application level options are an important and practical tool for allowing
-    the benefits of synchronous replication for high performance applications.
-   </para>
-
-   <para>
-    You should consider that the network bandwidth must be higher than
-    the rate of generation of WAL data.
-   </para>
-
-   </sect3>
-
-   <sect3 id="synchronous-replication-ha">
-    <title>Planning for High Availability</title>
-
-   <para>
-    Commits made when <varname>synchronous_commit</> is set to <literal>on</>
-    will wait until the sync standby responds. The response may never occur
-    if the last, or only, standby should crash.
-   </para>
-
-   <para>
-    The best solution for avoiding data loss is to ensure you don't lose
-    your last remaining sync standby. This can be achieved by naming multiple
-    potential synchronous standbys using <varname>synchronous_standby_names</>.
-    The first named standby will be used as the synchronous standby. Standbys
-    listed after this will take over the role of synchronous standby if the
-    first one should fail.
-   </para>
-
-   <para>
-    When a standby first attaches to the primary, it will not yet be properly
-    synchronized. This is described as <literal>CATCHUP</> mode. Once
-    the lag between standby and primary reaches zero for the first time
-    we move to real-time <literal>STREAMING</> state.
-    The catch-up duration may be long immediately after the standby has
-    been created. If the standby is shut down, then the catch-up period
-    will increase according to the length of time the standby has been down.
-    The standby is only able to become a synchronous standby
-    once it has reached <literal>STREAMING</> state.
-   </para>
-
-   <para>
-    If primary restarts while commits are waiting for acknowledgement, those
-    waiting transactions will be marked fully committed once the primary
-    database recovers.
-    There is no way to be certain that all standbys have received all
-    outstanding WAL data at time of the crash of the primary. Some
-    transactions may not show as committed on the standby, even though
-    they show as committed on the primary. The guarantee we offer is that
-    the application will not receive explicit acknowledgement of the
-    successful commit of a transaction until the WAL data is known to be
-    safely received by the standby.
-   </para>
-
-   <para>
-    If you really do lose your last standby server then you should disable
-    <varname>synchronous_standby_names</> and reload the configuration file
-    on the primary server.
-   </para>
-
-   <para>
-    If the primary is isolated from remaining standby servers you should
-    fail over to the best candidate of those other remaining standby servers.
-   </para>
-
-   <para>
-    If you need to re-create a standby server while transactions are
-    waiting, make sure that the commands to run pg_start_backup() and
-    pg_stop_backup() are run in a session with
-    <varname>synchronous_commit</> = <literal>off</>, otherwise those
-    requests will wait forever for the standby to appear.
-   </para>
-
-   </sect3>
-  </sect2>
-  </sect1>
-
-  <sect1 id="warm-standby-failover">
-   <title>Failover</title>
-&pgnotice;
-
-   <para>
-    If the primary server fails then the standby server should begin
-    failover procedures.
-   </para>
-
-   <para>
-    If the standby server fails then no failover need take place. If the
-    standby server can be restarted, even some time later, then the recovery
-    process can also be restarted immediately, taking advantage of
-    restartable recovery. If the standby server cannot be restarted, then a
-    full new standby server instance should be created.
-   </para>
-
-   <para>
-    If the primary server fails and the standby server becomes the
-    new primary, and then the old primary restarts, you must have
-    a mechanism for informing the old primary that it is no longer the primary. This is
-    sometimes known as <acronym>STONITH</> (Shoot The Other Node In The Head), which is
-    necessary to avoid situations where both systems think they are the
-    primary, which will lead to confusion and ultimately data loss.
-   </para>
-
-   <para>
-    Many failover systems use just two systems, the primary and the standby,
-    connected by some kind of heartbeat mechanism to continually verify the
-    connectivity between the two and the viability of the primary. It is
-    also possible to use a third system (called a witness server) to prevent
-    some cases of inappropriate failover, but the additional complexity
-    might not be worthwhile unless it is set up with sufficient care and
-    rigorous testing.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</productname> does not provide the system
-    software required to identify a failure on the primary and notify
-    the standby database server.  Many such tools exist and are well
-    integrated with the operating system facilities required for
-    successful failover, such as IP address migration.
-   </para>
-
-   <para>
-    Once failover to the standby occurs, there is only a
-    single server in operation. This is known as a degenerate state.
-    The former standby is now the primary, but the former primary is down
-    and might stay down.  To return to normal operation, a standby server
-    must be recreated,
-    either on the former primary system when it comes up, or on a third,
-    possibly new, system. Once complete, the primary and standby can be
-    considered to have switched roles. Some people choose to use a third
-    server to provide backup for the new primary until the new standby
-    server is recreated,
-    though clearly this complicates the system configuration and
-    operational processes.
-   </para>
-
-   <para>
-    So, switching from primary to standby server can be fast but requires
-    some time to re-prepare the failover cluster. Regular switching from
-    primary to standby is useful, since it allows regular downtime on
-    each system for maintenance. This also serves as a test of the
-    failover mechanism to ensure that it will really work when you need it.
-    Written administration procedures are advised.
-   </para>
-
-   <para>
-    To trigger failover of a log-shipping standby server,
-    run <command>pg_ctl promote</> or create a trigger
-    file with the file name and path specified by the <varname>trigger_file</>
-    setting in <filename>recovery.conf</>. If you're planning to use
-    <command>pg_ctl promote</> to fail over, <varname>trigger_file</> is
-    not required. If you're setting up the reporting servers that are
-    only used to offload read-only queries from the primary, not for high
-    availability purposes, you don't need to promote it.
-   </para>
-  </sect1>
-
-  <sect1 id="log-shipping-alternative">
-   <title>Alternative Method for Log Shipping</title>
-
-&pgnotice;
-   <para>
-    An alternative to the built-in standby mode described in the previous
-    sections is to use a <varname>restore_command</> that polls the archive location.
-    This was the only option available in versions 8.4 and below. In this
-    setup, set <varname>standby_mode</> off, because you are implementing
-    the polling required for standby operation yourself. See the
-    <xref linkend="pgstandby"> module for a reference
-    implementation of this.
-   </para>
-
-   <para>
-    Note that in this mode, the server will apply WAL one file at a
-    time, so if you use the standby server for queries (see Hot Standby),
-    there is a delay between an action in the master and when the
-    action becomes visible in the standby, corresponding the time it takes
-    to fill up the WAL file. <varname>archive_timeout</> can be used to make that delay
-    shorter. Also note that you can't combine streaming replication with
-    this method.
-   </para>
-
-   <para>
-    The operations that occur on both primary and standby servers are
-    normal continuous archiving and recovery tasks. The only point of
-    contact between the two database servers is the archive of WAL files
-    that both share: primary writing to the archive, standby reading from
-    the archive. Care must be taken to ensure that WAL archives from separate
-    primary servers do not become mixed together or confused. The archive
-    need not be large if it is only required for standby operation.
-   </para>
-
-   <para>
-    The magic that makes the two loosely coupled servers work together is
-    simply a <varname>restore_command</> used on the standby that,
-    when asked for the next WAL file, waits for it to become available from
-    the primary. The <varname>restore_command</> is specified in the
-    <filename>recovery.conf</> file on the standby server. Normal recovery
-    processing would request a file from the WAL archive, reporting failure
-    if the file was unavailable.  For standby processing it is normal for
-    the next WAL file to be unavailable, so the standby must wait for
-    it to appear. For files ending in <literal>.backup</> or
-    <literal>.history</> there is no need to wait, and a non-zero return
-    code must be returned. A waiting <varname>restore_command</> can be
-    written as a custom script that loops after polling for the existence of
-    the next WAL file. There must also be some way to trigger failover, which
-    should interrupt the <varname>restore_command</>, break the loop and
-    return a file-not-found error to the standby server. This ends recovery
-    and the standby will then come up as a normal server.
-   </para>
-
-   <para>
-    Pseudocode for a suitable <varname>restore_command</> is:
-<programlisting>
-triggered = false;
-while (!NextWALFileReady() &amp;&amp; !triggered)
-{
-    sleep(100000L);         /* wait for ~0.1 sec */
-    if (CheckForExternalTrigger())
-        triggered = true;
-}
-if (!triggered)
-        CopyWALFileForRecovery();
-</programlisting>
-   </para>
-
-   <para>
-    A working example of a waiting <varname>restore_command</> is provided
-    in the <xref linkend="pgstandby"> module. It
-    should be used as a reference on how to correctly implement the logic
-    described above. It can also be extended as needed to support specific
-    configurations and environments.
-   </para>
-
-   <para>
-    The method for triggering failover is an important part of planning
-    and design. One potential option is the <varname>restore_command</>
-    command.  It is executed once for each WAL file, but the process
-    running the <varname>restore_command</> is created and dies for
-    each file, so there is no daemon or server process, and
-    signals or a signal handler cannot be used. Therefore, the
-    <varname>restore_command</> is not suitable to trigger failover.
-    It is possible to use a simple timeout facility, especially if
-    used in conjunction with a known <varname>archive_timeout</>
-    setting on the primary. However, this is somewhat error prone
-    since a network problem or busy primary server might be sufficient
-    to initiate failover. A notification mechanism such as the explicit
-    creation of a trigger file is ideal, if this can be arranged.
-   </para>
-
-  <sect2 id="warm-standby-config">
-   <title>Implementation</title>
-&pgnotice;
-
-   <para>
-    The short procedure for configuring a standby server using this alternative
-    method is as follows. For
-    full details of each step, refer to previous sections as noted.
-    <orderedlist>
-     <listitem>
-      <para>
-       Set up primary and standby systems as nearly identical as
-       possible, including two identical copies of
-       <productname>PostgreSQL</> at the same release level.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Set up continuous archiving from the primary to a WAL archive
-       directory on the standby server. Ensure that
-       <xref linkend="guc-archive-mode">,
-       <xref linkend="guc-archive-command"> and
-       <xref linkend="guc-archive-timeout">
-       are set appropriately on the primary
-       (see <xref linkend="backup-archiving-wal">).
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Make a base backup of the primary server (see <xref
-       linkend="backup-base-backup">), and load this data onto the standby.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Begin recovery on the standby server from the local WAL
-       archive, using a <filename>recovery.conf</> that specifies a
-       <varname>restore_command</> that waits as described
-       previously (see <xref linkend="backup-pitr-recovery">).
-      </para>
-     </listitem>
-    </orderedlist>
-   </para>
-
-   <para>
-    Recovery treats the WAL archive as read-only, so once a WAL file has
-    been copied to the standby system it can be copied to tape at the same
-    time as it is being read by the standby database server.
-    Thus, running a standby server for high availability can be performed at
-    the same time as files are stored for longer term disaster recovery
-    purposes.
-   </para>
-
-   <para>
-    For testing purposes, it is possible to run both primary and standby
-    servers on the same system. This does not provide any worthwhile
-    improvement in server robustness, nor would it be described as HA.
-   </para>
-  </sect2>
-
-  <sect2 id="warm-standby-record">
-   <title>Record-based Log Shipping</title>
-<!## XC>
-&pgonly;
-     <para>
-      Streaming replication has not been tested
-      with <productname>Postgres-XC</productname> yet.  Because this
-      version of streaming replication is based upon asynchronous log shipping,
-      there could be a risk to have the status of Coordinators and
-      Datanodes inconsistent.  The development team leaves the test
-      and the use of this entirely to users.
-     </para>
-<!## end>
-<!## XL>
-&pgonly;
-     <para>
-     </para>
-<!## end>
-
-   <para>
-    It is also possible to implement record-based log shipping using this
-    alternative method, though this requires custom development, and changes
-    will still only become visible to hot standby queries after a full WAL
-    file has been shipped.
-   </para>
-
-   <para>
-    An external program can call the <function>pg_xlogfile_name_offset()</>
-    function (see <xref linkend="functions-admin">)
-    to find out the file name and the exact byte offset within it of
-    the current end of WAL.  It can then access the WAL file directly
-    and copy the data from the last known end of WAL through the current end
-    over to the standby servers.  With this approach, the window for data
-    loss is the polling cycle time of the copying program, which can be very
-    small, and there is no wasted bandwidth from forcing partially-used
-    segment files to be archived.  Note that the standby servers'
-    <varname>restore_command</> scripts can only deal with whole WAL files,
-    so the incrementally copied data is not ordinarily made available to
-    the standby servers.  It is of use only when the primary dies &mdash;
-    then the last partial WAL file is fed to the standby before allowing
-    it to come up.  The correct implementation of this process requires
-    cooperation of the <varname>restore_command</> script with the data
-    copying program.
-   </para>
-
-   <para>
-    Starting with <productname>PostgreSQL</> version 9.0, you can use
-    streaming replication (see <xref linkend="streaming-replication">) to
-    achieve the same benefits with less effort.
-   </para>
-
-
-  </sect2>
- </sect1>
-
- <sect1 id="hot-standby">
-  <title>Hot Standby</title>
-
-  <indexterm zone="high-availability">
-   <primary>Hot Standby</primary>
-  </indexterm>
-
-
-   <para>
-    Hot Standby is the term used to describe the ability to connect to
-    the server and run read-only queries while the server is in archive
-    recovery or standby mode. This
-    is useful both for replication purposes and for restoring a backup
-    to a desired state with great precision.
-    The term Hot Standby also refers to the ability of the server to move
-    from recovery through to normal operation while users continue running
-    queries and/or keep their connections open.
-   </para>
-
-   <para>
-    Running queries in hot standby mode is similar to normal query operation,
-    though there are several usage and administrative differences
-    explained below.
-   </para>
-
-<!## XC>
-&pgonly;
-
-   <para>
-    Hot Standby is not supported by the current version
-    of <productname>Postgres-XC</productname>.
-   </para>
-<!## end>
-<!## XL>
-&pgonly;
-
-   <para>
-    Hot Standby is not supported by the current version
-    of <productname>Postgres-XL</productname>.
-   </para>
-<!## end>
-
-<!## PG>
-  <sect2 id="hot-standby-users">
-   <title>User's Overview</title>
-
-   <para>
-    When the <xref linkend="guc-hot-standby"> parameter is set to true on a
-    standby server, it will begin accepting connections once the recovery has
-    brought the system to a consistent state.  All such connections are
-    strictly read-only; not even temporary tables may be written.
-   </para>
-
-   <para>
-    The data on the standby takes some time to arrive from the primary server
-    so there will be a measurable delay between primary and standby. Running the
-    same query nearly simultaneously on both primary and standby might therefore
-    return differing results. We say that data on the standby is
-    <firstterm>eventually consistent</firstterm> with the primary.  Once the
-    commit record for a transaction is replayed on the standby, the changes
-    made by that transaction will be visible to any new snapshots taken on
-    the standby.  Snapshots may be taken at the start of each query or at the
-    start of each transaction, depending on the current transaction isolation
-    level.  For more details, see <xref linkend="transaction-iso">.
-   </para>
-
-   <para>
-    Transactions started during hot standby may issue the following commands:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Query access - <command>SELECT</>, <command>COPY TO</>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Cursor commands - <command>DECLARE</>, <command>FETCH</>, <command>CLOSE</>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Parameters - <command>SHOW</>, <command>SET</>, <command>RESET</>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Transaction management commands
-        <itemizedlist>
-         <listitem>
-          <para>
-           <command>BEGIN</>, <command>END</>, <command>ABORT</>, <command>START TRANSACTION</>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <command>SAVEPOINT</>, <command>RELEASE</>, <command>ROLLBACK TO SAVEPOINT</>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <command>EXCEPTION</> blocks and other internal subtransactions
-          </para>
-         </listitem>
-        </itemizedlist>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <command>LOCK TABLE</>, though only when explicitly in one of these modes:
-       <literal>ACCESS SHARE</>, <literal>ROW SHARE</> or <literal>ROW EXCLUSIVE</>.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Plans and resources - <command>PREPARE</>, <command>EXECUTE</>,
-       <command>DEALLOCATE</>, <command>DISCARD</>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Plugins and extensions - <command>LOAD</>
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    Transactions started during hot standby will never be assigned a
-    transaction ID and cannot write to the system write-ahead log.
-    Therefore, the following actions will produce error messages:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Data Manipulation Language (DML) - <command>INSERT</>,
-       <command>UPDATE</>, <command>DELETE</>, <command>COPY FROM</>,
-       <command>TRUNCATE</>.
-       Note that there are no allowed actions that result in a trigger
-       being executed during recovery.  This restriction applies even to
-       temporary tables, because table rows cannot be read or written without
-       assigning a transaction ID, which is currently not possible in a
-       Hot Standby environment.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Data Definition Language (DDL) - <command>CREATE</>,
-       <command>DROP</>, <command>ALTER</>, <command>COMMENT</>.
-       This restriction applies even to temporary tables, because carrying
-       out these operations would require updating the system catalog tables.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <command>SELECT ... FOR SHARE | UPDATE</>, because row locks cannot be
-       taken without updating the underlying data files.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Rules on <command>SELECT</> statements that generate DML commands.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <command>LOCK</> that explicitly requests a mode higher than <literal>ROW EXCLUSIVE MODE</>.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <command>LOCK</> in short default form, since it requests <literal>ACCESS EXCLUSIVE MODE</>.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Transaction management commands that explicitly set non-read-only state:
-        <itemizedlist>
-         <listitem>
-          <para>
-            <command>BEGIN READ WRITE</>,
-            <command>START TRANSACTION READ WRITE</>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-            <command>SET TRANSACTION READ WRITE</>,
-            <command>SET SESSION CHARACTERISTICS AS TRANSACTION READ WRITE</>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <command>SET transaction_read_only = off</>
-          </para>
-         </listitem>
-        </itemizedlist>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Two-phase commit commands - <command>PREPARE TRANSACTION</>,
-       <command>COMMIT PREPARED</>, <command>ROLLBACK PREPARED</>
-       because even read-only transactions need to write WAL in the
-       prepare phase (the first phase of two phase commit).
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Sequence updates - <function>nextval()</>, <function>setval()</>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <command>LISTEN</>, <command>UNLISTEN</>, <command>NOTIFY</>
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    In normal operation, <quote>read-only</> transactions are allowed to
-    update sequences and to use <command>LISTEN</>, <command>UNLISTEN</>, and
-    <command>NOTIFY</>, so Hot Standby sessions operate under slightly tighter
-    restrictions than ordinary read-only sessions.  It is possible that some
-    of these restrictions might be loosened in a future release.
-   </para>
-
-   <para>
-    During hot standby, the parameter <varname>transaction_read_only</> is always
-    true and may not be changed.  But as long as no attempt is made to modify
-    the database, connections during hot standby will act much like any other
-    database connection.  If failover or switchover occurs, the database will
-    switch to normal processing mode.  Sessions will remain connected while the
-    server changes mode.  Once hot standby finishes, it will be possible to
-    initiate read-write transactions (even from a session begun during
-    hot standby).
-   </para>
-
-   <para>
-    Users will be able to tell whether their session is read-only by
-    issuing <command>SHOW transaction_read_only</>.  In addition, a set of
-    functions (<xref linkend="functions-recovery-info-table">) allow users to
-    access information about the standby server. These allow you to write
-    programs that are aware of the current state of the database. These
-    can be used to monitor the progress of recovery, or to allow you to
-    write complex programs that restore the database to particular states.
-   </para>
-  </sect2>
-
-  <sect2 id="hot-standby-conflict">
-   <title>Handling Query Conflicts</title>
-
-&pgnotice;
-   <para>
-    The primary and standby servers are in many ways loosely connected. Actions
-    on the primary will have an effect on the standby. As a result, there is
-    potential for negative interactions or conflicts between them. The easiest
-    conflict to understand is performance: if a huge data load is taking place
-    on the primary then this will generate a similar stream of WAL records on the
-    standby, so standby queries may contend for system resources, such as I/O.
-   </para>
-
-   <para>
-    There are also additional types of conflict that can occur with Hot Standby.
-    These conflicts are <emphasis>hard conflicts</> in the sense that queries
-    might need to be cancelled and, in some cases, sessions disconnected to resolve them.
-    The user is provided with several ways to handle these
-    conflicts. Conflict cases include:
-
-      <itemizedlist>
-       <listitem>
-        <para>
-         Access Exclusive locks taken on the primary server, including both
-         explicit <command>LOCK</> commands and various <acronym>DDL</>
-         actions, conflict with table accesses in standby queries.
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Dropping a tablespace on the primary conflicts with standby queries
-         using that tablespace for temporary work files.
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Dropping a database on the primary conflicts with sessions connected
-         to that database on the standby.
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Application of a vacuum cleanup record from WAL conflicts with
-         standby transactions whose snapshots can still <quote>see</> any of
-         the rows to be removed.
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Application of a vacuum cleanup record from WAL conflicts with
-         queries accessing the target page on the standby, whether or not
-         the data to be removed is visible.
-        </para>
-       </listitem>
-      </itemizedlist>
-   </para>
-
-   <para>
-    On the primary server, these cases simply result in waiting; and the
-    user might choose to cancel either of the conflicting actions.  However,
-    on the standby there is no choice: the WAL-logged action already occurred
-    on the primary so the standby must not fail to apply it.  Furthermore,
-    allowing WAL application to wait indefinitely may be very undesirable,
-    because the standby's state will become increasingly far behind the
-    primary's.  Therefore, a mechanism is provided to forcibly cancel standby
-    queries that conflict with to-be-applied WAL records.
-   </para>
-
-   <para>
-    An example of the problem situation is an administrator on the primary
-    server running <command>DROP TABLE</> on a table that is currently being
-    queried on the standby server.  Clearly the standby query cannot continue
-    if the <command>DROP TABLE</> is applied on the standby. If this situation
-    occurred on the primary, the <command>DROP TABLE</> would wait until the
-    other query had finished. But when <command>DROP TABLE</> is run on the
-    primary, the primary doesn't have information about what queries are
-    running on the standby, so it will not wait for any such standby
-    queries. The WAL change records come through to the standby while the
-    standby query is still running, causing a conflict.  The standby server
-    must either delay application of the WAL records (and everything after
-    them, too) or else cancel the conflicting query so that the <command>DROP
-    TABLE</> can be applied.
-   </para>
-
-   <para>
-    When a conflicting query is short, it's typically desirable to allow it to
-    complete by delaying WAL application for a little bit; but a long delay in
-    WAL application is usually not desirable.  So the cancel mechanism has
-    parameters, <xref linkend="guc-max-standby-archive-delay"> and <xref
-    linkend="guc-max-standby-streaming-delay">, that define the maximum
-    allowed delay in WAL application.  Conflicting queries will be canceled
-    once it has taken longer than the relevant delay setting to apply any
-    newly-received WAL data.  There are two parameters so that different delay
-    values can be specified for the case of reading WAL data from an archive
-    (i.e., initial recovery from a base backup or <quote>catching up</> a
-    standby server that has fallen far behind) versus reading WAL data via
-    streaming replication.
-   </para>
-
-   <para>
-    In a standby server that exists primarily for high availability, it's
-    best to set the delay parameters relatively short, so that the server
-    cannot fall far behind the primary due to delays caused by standby
-    queries.  However, if the standby server is meant for executing
-    long-running queries, then a high or even infinite delay value may be
-    preferable.  Keep in mind however that a long-running query could
-    cause other sessions on the standby server to not see recent changes
-    on the primary, if it delays application of WAL records.
-   </para>
-
-   <para>
-    Once the delay specified by <varname>max_standby_archive_delay</> or
-    <varname>max_standby_streaming_delay</> has been exceeded, conflicting
-    queries will be cancelled.  This usually results just in a cancellation
-    error, although in the case of replaying a <command>DROP DATABASE</>
-    the entire conflicting session will be terminated.  Also, if the conflict
-    is over a lock held by an idle transaction, the conflicting session is
-    terminated (this behavior might change in the future).
-   </para>
-
-   <para>
-    Cancelled queries may be retried immediately (after beginning a new
-    transaction, of course).  Since query cancellation depends on
-    the nature of the WAL records being replayed, a query that was
-    cancelled may well succeed if it is executed again.
-   </para>
-
-   <para>
-    Keep in mind that the delay parameters are compared to the elapsed time
-    since the WAL data was received by the standby server.  Thus, the grace
-    period allowed to any one query on the standby is never more than the
-    delay parameter, and could be considerably less if the standby has already
-    fallen behind as a result of waiting for previous queries to complete, or
-    as a result of being unable to keep up with a heavy update load.
-   </para>
-
-   <para>
-    The most common reason for conflict between standby queries and WAL replay
-    is <quote>early cleanup</>.  Normally, <productname>PostgreSQL</> allows
-    cleanup of old row versions when there are no transactions that need to
-    see them to ensure correct visibility of data according to MVCC rules.
-    However, this rule can only be applied for transactions executing on the
-    master.  So it is possible that cleanup on the master will remove row
-    versions that are still visible to a transaction on the standby.
-   </para>
-
-   <para>
-    Experienced users should note that both row version cleanup and row version
-    freezing will potentially conflict with standby queries. Running a manual
-    <command>VACUUM FREEZE</> is likely to cause conflicts even on tables with
-    no updated or deleted rows.
-   </para>
-
-   <para>
-    Users should be clear that tables that are regularly and heavily updated
-    on the primary server will quickly cause cancellation of longer running
-    queries on the standby. In such cases the setting of a finite value for
-    <varname>max_standby_archive_delay</> or
-    <varname>max_standby_streaming_delay</> can be considered similar to
-    setting <varname>statement_timeout</>.
-   </para>
-
-   <para>
-    Remedial possibilities exist if the number of standby-query cancellations
-    is found to be unacceptable.  The first option is to set the parameter
-    <varname>hot_standby_feedback</>, which prevents <command>VACUUM</> from
-    removing recently-dead rows and so cleanup conflicts do not occur.
-    If you do this, you
-    should note that this will delay cleanup of dead rows on the primary,
-    which may result in undesirable table bloat. However, the cleanup
-    situation will be no worse than if the standby queries were running
-    directly on the primary server, and you are still getting the benefit of
-    off-loading execution onto the standby.
-    <varname>max_standby_archive_delay</> must be kept large in this case,
-    because delayed WAL files might already contain entries that conflict with
-    the desired standby queries.
-   </para>
-
-   <para>
-    Another option is to increase <xref linkend="guc-vacuum-defer-cleanup-age">
-    on the primary server, so that dead rows will not be cleaned up as quickly
-    as they normally would be.  This will allow more time for queries to
-    execute before they are cancelled on the standby, without having to set
-    a high <varname>max_standby_streaming_delay</>.  However it is
-    difficult to guarantee any specific execution-time window with this
-    approach, since <varname>vacuum_defer_cleanup_age</> is measured in
-    transactions executed on the primary server.
-   </para>
-
-   <para>
-    The number of query cancels and the reason for them can be viewed using
-    the <structname>pg_stat_database_conflicts</> system view on the standby
-    server. The <structname>pg_stat_database</> system view also contains
-    summary information.
-   </para>
-  </sect2>
-
-  <sect2 id="hot-standby-admin">
-   <title>Administrator's Overview</title>
-&pgnotice;
-
-   <para>
-    If <varname>hot_standby</> is turned <literal>on</> in
-    <filename>postgresql.conf</> and there is a <filename>recovery.conf</>
-    file present, the server will run in Hot Standby mode.
-    However, it may take some time for Hot Standby connections to be allowed,
-    because the server will not accept connections until it has completed
-    sufficient recovery to provide a consistent state against which queries
-    can run.  During this period,
-    clients that attempt to connect will be refused with an error message.
-    To confirm the server has come up, either loop trying to connect from
-    the application, or look for these messages in the server logs:
-
-<programlisting>
-LOG:  entering standby mode
-
-... then some time later ...
-
-LOG:  consistent recovery state reached
-LOG:  database system is ready to accept read only connections
-</programlisting>
-
-    Consistency information is recorded once per checkpoint on the primary.
-    It is not possible to enable hot standby when reading WAL
-    written during a period when <varname>wal_level</> was not set to
-    <literal>hot_standby</> on the primary.  Reaching a consistent state can
-    also be delayed in the presence of both of these conditions:
-
-      <itemizedlist>
-       <listitem>
-        <para>
-         A write transaction has more than 64 subtransactions
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Very long-lived write transactions
-        </para>
-       </listitem>
-      </itemizedlist>
-
-    If you are running file-based log shipping ("warm standby"), you might need
-    to wait until the next WAL file arrives, which could be as long as the
-    <varname>archive_timeout</> setting on the primary.
-   </para>
-
-   <para>
-    The setting of some parameters on the standby will need reconfiguration
-    if they have been changed on the primary. For these parameters,
-    the value on the standby must
-    be equal to or greater than the value on the primary. If these parameters
-    are not set high enough then the standby will refuse to start.
-    Higher values can then be supplied and the server
-    restarted to begin recovery again.  These parameters are:
-
-      <itemizedlist>
-       <listitem>
-        <para>
-         <varname>max_connections</>
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         <varname>max_prepared_transactions</>
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         <varname>max_locks_per_transaction</>
-        </para>
-       </listitem>
-      </itemizedlist>
-   </para>
-
-   <para>
-<!## PG>
-    It is important that the administrator select appropriate settings for
-    <xref linkend="guc-max-standby-archive-delay"> and <xref
-    linkend="guc-max-standby-streaming-delay">.  The best choices vary
-    depending on business priorities.  For example if the server is primarily
-    tasked as a High Availability server, then you will want low delay
-    settings, perhaps even zero, though that is a very aggressive setting. If
-    the standby server is tasked as an additional server for decision support
-    queries then it might be acceptable to set the maximum delay values to
-    many hours, or even -1 which means wait forever for queries to complete.
-<!## end>
-   </para>
-
-   <para>
-    Transaction status "hint bits" written on the primary are not WAL-logged,
-    so data on the standby will likely re-write the hints again on the standby.
-    Thus, the standby server will still perform disk writes even though
-    all users are read-only; no changes occur to the data values
-    themselves.  Users will still write large sort temporary files and
-    re-generate relcache info files, so no part of the database
-    is truly read-only during hot standby mode.
-    Note also that writes to remote databases using
-    <application>dblink</application> module, and other operations outside the
-    database using PL functions will still be possible, even though the
-    transaction is read-only locally.
-   </para>
-
-   <para>
-    The following types of administration commands are not accepted
-    during recovery mode:
-
-      <itemizedlist>
-       <listitem>
-        <para>
-         Data Definition Language (DDL) - e.g. <command>CREATE INDEX</>
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Privilege and Ownership - <command>GRANT</>, <command>REVOKE</>,
-         <command>REASSIGN</>
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Maintenance commands - <command>ANALYZE</>, <command>VACUUM</>,
-         <command>CLUSTER</>, <command>REINDEX</>
-        </para>
-       </listitem>
-      </itemizedlist>
-   </para>
-
-   <para>
-    Again, note that some of these commands are actually allowed during
-    "read only" mode transactions on the primary.
-   </para>
-
-   <para>
-    As a result, you cannot create additional indexes that exist solely
-    on the standby, nor statistics that exist solely on the standby.
-    If these administration commands are needed, they should be executed
-    on the primary, and eventually those changes will propagate to the
-    standby.
-   </para>
-
-   <para>
-    <function>pg_cancel_backend()</> will work on user backends, but not the
-    Startup process, which performs recovery. <structname>pg_stat_activity</structname> does not
-    show an entry for the Startup process, nor do recovering transactions
-    show as active. As a result, <structname>pg_prepared_xacts</structname> is always empty during
-    recovery. If you wish to resolve in-doubt prepared transactions,
-    view <literal>pg_prepared_xacts</> on the primary and issue commands to
-    resolve transactions there.
-   </para>
-
-   <para>
-    <structname>pg_locks</structname> will show locks held by backends,
-    as normal. <structname>pg_locks</structname> also shows
-    a virtual transaction managed by the Startup process that owns all
-    <literal>AccessExclusiveLocks</> held by transactions being replayed by recovery.
-    Note that the Startup process does not acquire locks to
-    make database changes, and thus locks other than <literal>AccessExclusiveLocks</>
-    do not show in <structname>pg_locks</structname> for the Startup
-    process; they are just presumed to exist.
-   </para>
-
-   <para>
-    The <productname>Nagios</> plugin <productname>check_pgsql</> will
-    work, because the simple information it checks for exists.
-    The <productname>check_postgres</> monitoring script will also work,
-    though some reported values could give different or confusing results.
-    For example, last vacuum time will not be maintained, since no
-    vacuum occurs on the standby.  Vacuums running on the primary
-    do still send their changes to the standby.
-   </para>
-
-   <para>
-    WAL file control commands will not work during recovery,
-    e.g. <function>pg_start_backup</>, <function>pg_switch_xlog</> etc.
-   </para>
-
-   <para>
-    Dynamically loadable modules work, including <structname>pg_stat_statements</>.
-   </para>
-
-   <para>
-    Advisory locks work normally in recovery, including deadlock detection.
-    Note that advisory locks are never WAL logged, so it is impossible for
-    an advisory lock on either the primary or the standby to conflict with WAL
-    replay. Nor is it possible to acquire an advisory lock on the primary
-    and have it initiate a similar advisory lock on the standby. Advisory
-    locks relate only to the server on which they are acquired.
-   </para>
-
-   <para>
-    Trigger-based replication systems such as <productname>Slony</>,
-    <productname>Londiste</> and <productname>Bucardo</> won't run on the
-    standby at all, though they will run happily on the primary server as
-    long as the changes are not sent to standby servers to be applied.
-    WAL replay is not trigger-based so you cannot relay from the
-    standby to any system that requires additional database writes or
-    relies on the use of triggers.
-   </para>
-
-   <para>
-    New OIDs cannot be assigned, though some <acronym>UUID</> generators may still
-    work as long as they do not rely on writing new status to the database.
-   </para>
-
-   <para>
-    Currently, temporary table creation is not allowed during read only
-    transactions, so in some cases existing scripts will not run correctly.
-    This restriction might be relaxed in a later release. This is
-    both a SQL Standard compliance issue and a technical issue.
-   </para>
-
-   <para>
-    <command>DROP TABLESPACE</> can only succeed if the tablespace is empty.
-    Some standby users may be actively using the tablespace via their
-    <varname>temp_tablespaces</> parameter. If there are temporary files in the
-    tablespace, all active queries are cancelled to ensure that temporary
-    files are removed, so the tablespace can be removed and WAL replay
-    can continue.
-   </para>
-
-   <para>
-    Running <command>DROP DATABASE</> or <command>ALTER DATABASE ... SET
-    TABLESPACE</> on the primary
-    will generate a WAL entry that will cause all users connected to that
-    database on the standby to be forcibly disconnected. This action occurs
-    immediately, whatever the setting of
-    <varname>max_standby_streaming_delay</>. Note that
-    <command>ALTER DATABASE ... RENAME</> does not disconnect users, which
-    in most cases will go unnoticed, though might in some cases cause a
-    program confusion if it depends in some way upon database name.
-   </para>
-
-   <para>
-    In normal (non-recovery) mode, if you issue <command>DROP USER</> or <command>DROP ROLE</>
-    for a role with login capability while that user is still connected then
-    nothing happens to the connected user - they remain connected. The user cannot
-    reconnect however. This behavior applies in recovery also, so a
-    <command>DROP USER</> on the primary does not disconnect that user on the standby.
-   </para>
-
-   <para>
-    The statistics collector is active during recovery. All scans, reads, blocks,
-    index usage, etc., will be recorded normally on the standby. Replayed
-    actions will not duplicate their effects on primary, so replaying an
-    insert will not increment the Inserts column of pg_stat_user_tables.
-    The stats file is deleted at the start of recovery, so stats from primary
-    and standby will differ; this is considered a feature, not a bug.
-   </para>
-
-   <para>
-    Autovacuum is not active during recovery.  It will start normally at the
-    end of recovery.
-   </para>
-
-   <para>
-    The background writer is active during recovery and will perform
-    restartpoints (similar to checkpoints on the primary) and normal block
-    cleaning activities. This can include updates of the hint bit
-    information stored on the standby server.
-    The <command>CHECKPOINT</> command is accepted during recovery,
-    though it performs a restartpoint rather than a new checkpoint.
-   </para>
-  </sect2>
-
-  <sect2 id="hot-standby-parameters">
-   <title>Hot Standby Parameter Reference</title>
-
-   <para>
-    Various parameters have been mentioned above in
-    <xref linkend="hot-standby-conflict"> and
-    <xref linkend="hot-standby-admin">.
-   </para>
-
-   <para>
-    On the primary, parameters <xref linkend="guc-wal-level"> and
-    <xref linkend="guc-vacuum-defer-cleanup-age"> can be used.
-    <xref linkend="guc-max-standby-archive-delay"> and
-    <xref linkend="guc-max-standby-streaming-delay"> have no effect if set on
-    the primary.
-   </para>
-
-   <para>
-    On the standby, parameters <xref linkend="guc-hot-standby">,
-    <xref linkend="guc-max-standby-archive-delay"> and
-    <xref linkend="guc-max-standby-streaming-delay"> can be used.
-    <xref linkend="guc-vacuum-defer-cleanup-age"> has no effect
-    as long as the server remains in standby mode, though it will
-    become relevant if the standby becomes primary.
-   </para>
-  </sect2>
-
-  <sect2 id="hot-standby-caveats">
-   <title>Caveats</title>
-
-   <para>
-    There are several limitations of Hot Standby.
-    These can and probably will be fixed in future releases:
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Operations on hash indexes are not presently WAL-logged, so
-     replay will not update these indexes.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Full knowledge of running transactions is required before snapshots
-     can be taken. Transactions that use large numbers of subtransactions
-     (currently greater than 64) will delay the start of read only
-     connections until the completion of the longest running write transaction.
-     If this situation occurs, explanatory messages will be sent to the server log.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Valid starting points for standby queries are generated at each
-     checkpoint on the master. If the standby is shut down while the master
-     is in a shutdown state, it might not be possible to re-enter Hot Standby
-     until the primary is started up, so that it generates further starting
-     points in the WAL logs.  This situation isn't a problem in the most
-     common situations where it might happen. Generally, if the primary is
-     shut down and not available anymore, that's likely due to a serious
-     failure that requires the standby being converted to operate as
-     the new primary anyway.  And in situations where the primary is
-     being intentionally taken down, coordinating to make sure the standby
-     becomes the new primary smoothly is also standard procedure.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     At the end of recovery, <literal>AccessExclusiveLocks</> held by prepared transactions
-     will require twice the normal number of lock table entries. If you plan
-     on running either a large number of concurrent prepared transactions
-     that normally take <literal>AccessExclusiveLocks</>, or you plan on having one
-     large transaction that takes many <literal>AccessExclusiveLocks</>, you are
-     advised to select a larger value of <varname>max_locks_per_transaction</>,
-     perhaps as much as twice the value of the parameter on
-     the primary server. You need not consider this at all if
-     your setting of <varname>max_prepared_transactions</> is 0.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     The Serializable transaction isolation level is not yet available in hot
-     standby.  (See <xref linkend="xact-serializable"> and
-     <xref linkend="serializable-consistency"> for details.)
-     An attempt to set a transaction to the serializable isolation level in
-     hot standby mode will generate an error.
-    </para>
-   </listitem>
-  </itemizedlist>
-
-   </para>
-  </sect2>
-<!## end>
-
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/history.sgmlin b/doc-xc/src/sgml/history.sgmlin
deleted file mode 100644
index 38e366e625..0000000000
--- a/doc-xc/src/sgml/history.sgmlin
+++ /dev/null
@@ -1,340 +0,0 @@
-<!-- doc/src/sgml/history.sgml -->
-
-<sect1 id="history">
-<!## PG>
- <title>A Brief History of <productname>PostgreSQL</productname></title>
-<!## end>
-<!## XC>
- <title>A Brief History of <productname>PostgreSQL</productname> and <productname>Postgres-XC</productname></title>
-<!## end>
-<!## XL>
- <title>A Brief History of <productname>PostgreSQL</productname> and <productname>Postgres-XL</productname></title>
-<!## end>
-
- <indexterm zone="history">
-  <primary>history</primary>
-  <secondary>of PostgreSQL</secondary>
- </indexterm>
-&common;
- <para>
-  The object-relational database management system now known as
-  <productname>PostgreSQL</productname> is derived from the
-  <productname>POSTGRES</productname> package written at the
-  University of California at Berkeley.  With over two decades of
-  development behind it, <productname>PostgreSQL</productname> is now
-  the most advanced open-source database available anywhere.
- </para>
-
- <sect2 id="history-berkeley">
-  <title>The Berkeley <productname>POSTGRES</productname> Project</title>
-
-  <indexterm zone="history-berkeley">
-   <primary>POSTGRES</primary>
-  </indexterm>
-
-  <para>
-   The <productname>POSTGRES</productname> project, led by Professor
-   Michael Stonebraker, was sponsored by the Defense Advanced Research
-   Projects Agency (<acronym>DARPA</acronym>), the Army Research
-   Office (<acronym>ARO</acronym>), the National Science Foundation
-   (<acronym>NSF</acronym>), and ESL, Inc.  The implementation of
-   <productname>POSTGRES</productname> began in 1986.  The initial
-   concepts for the system were presented in <xref linkend="STON86">,
-   and the definition of the initial data model appeared in <xref
-   linkend="ROWE87">.  The design of the rule system at that time was
-   described in <xref linkend="STON87a">.  The rationale and
-   architecture of the storage manager were detailed in <xref
-   linkend="STON87b">.
-  </para>
-
-  <para>
-   <productname>POSTGRES</productname> has undergone several major
-   releases since then.  The first <quote>demoware</quote> system
-   became operational in 1987 and was shown at the 1988
-   <acronym>ACM-SIGMOD</acronym> Conference.  Version 1, described in
-   <xref linkend="STON90a">, was released to a few external users in
-   June 1989.  In response to a critique of the first rule system
-   (<xref linkend="STON89">), the rule system was redesigned (<xref
-   linkend="STON90b">), and Version 2 was released in June 1990 with
-   the new rule system.  Version 3 appeared in 1991 and added support
-   for multiple storage managers, an improved query executor, and a
-   rewritten rule system.  For the most part, subsequent releases
-   until <productname>Postgres95</productname> (see below) focused on
-   portability and reliability.
-  </para>
-
-  <para>
-   <productname>POSTGRES</productname> has been used to implement many
-   different research and production applications.  These include: a
-   financial data analysis system, a jet engine performance monitoring
-   package, an asteroid tracking database, a medical information
-   database, and several geographic information systems.
-   <productname>POSTGRES</productname> has also been used as an
-   educational tool at several universities.  Finally, Illustra
-   Information Technologies (later merged into
-   <ulink url="http://www.informix.com/"><productname>Informix</productname></ulink>,
-   which is now owned by <ulink
-   url="http://www.ibm.com/">IBM</ulink>) picked up the code and
-   commercialized it.  In late 1992,
-   <productname>POSTGRES</productname> became the primary data manager
-   for the
-   <ulink url="http://meteora.ucsd.edu/s2k/s2k_home.html">
-   Sequoia 2000 scientific computing project</ulink>.
-  </para>
-
-  <para>
-   The size of the external user community nearly doubled during 1993.
-   It became increasingly obvious that maintenance of the prototype
-   code and support was taking up large amounts of time that should
-   have been devoted to database research.  In an effort to reduce
-   this support burden, the Berkeley
-   <productname>POSTGRES</productname> project officially ended with
-   Version 4.2.
-  </para>
- </sect2>
-
- <sect2 id="history-postgres95">
-  <title><productname>Postgres95</productname></title>
-
-  <indexterm zone="history-postgres95">
-   <primary>Postgres95</primary>
-  </indexterm>
-
-  <para>
-   In 1994, Andrew Yu and Jolly Chen added an SQL language interpreter
-   to <productname>POSTGRES</productname>.  Under a new name,
-   <productname>Postgres95</productname> was subsequently released to
-   the web to find its own way in the world as an open-source
-   descendant of the original <productname>POSTGRES</productname>
-   Berkeley code.
-  </para>
-
-  <para>
-   <productname>Postgres95</productname> code was completely ANSI C
-   and trimmed in size by 25%. Many internal changes improved
-   performance and
-   maintainability. <productname>Postgres95</productname> release
-   1.0.x ran about 30-50% faster on the Wisconsin Benchmark compared
-   to <productname>POSTGRES</productname>, Version 4.2.  Apart from
-   bug fixes, the following were the major enhancements:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      The query language PostQUEL was replaced with
-      <acronym>SQL</acronym> (implemented in the server).  Subqueries
-      were not supported until <productname>PostgreSQL</productname>
-      (see below), but they could be imitated in
-      <productname>Postgres95</productname> with user-defined
-      <acronym>SQL</acronym> functions. Aggregate functions were
-      re-implemented.  Support for the <literal>GROUP BY</literal>
-      query clause was also added.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A new program
-      (<application>psql</application>) was provided for interactive
-      SQL queries, which used <acronym>GNU</acronym>
-      <application>Readline</application>.  This largely superseded
-      the old <application>monitor</> program.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A new front-end library, <filename>libpgtcl</filename>,
-      supported <acronym>Tcl</acronym>-based clients.  A sample shell,
-      <command>pgtclsh</command>, provided new Tcl commands to
-      interface <application>Tcl</application> programs with the
-      <productname>Postgres95</productname> server.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The large-object interface was overhauled. The inversion large
-      objects were the only mechanism for storing large objects.  (The
-      inversion file system was removed.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The instance-level rule system was removed.  Rules were still
-      available as rewrite rules.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A short tutorial introducing regular <acronym>SQL</acronym>
-      features as well as those of
-      <productname>Postgres95</productname> was distributed with the
-      source code
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <acronym>GNU</acronym> make (instead of <acronym>BSD</acronym>
-      make) was used for the build.  Also,
-      <productname>Postgres95</productname> could be compiled with an
-      unpatched <productname>GCC</productname> (data alignment of
-      doubles was fixed).
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
- </sect2>
-
- <sect2>
-  <title><productname>PostgreSQL</productname></title>
-
-  <para>
-   By 1996, it became clear that the name <quote>Postgres95</quote>
-   would not stand the test of time. We chose a new name,
-   <productname>PostgreSQL</productname>, to reflect the relationship
-   between the original <productname>POSTGRES</productname> and the
-   more recent versions with <acronym>SQL</acronym> capability.  At
-   the same time, we set the version numbering to start at 6.0,
-   putting the numbers back into the sequence originally begun by the
-   Berkeley <productname>POSTGRES</productname> project.
-  </para>
-
-  <para>
-   Many people continue to refer to
-   <productname>PostgreSQL</productname> as <quote>Postgres</quote>
-   (now rarely in all capital letters) because of tradition or because
-   it is easier to pronounce.  This usage is widely accepted as a
-   nickname or alias.
-  </para>
-
-  <para>
-   The emphasis during development of
-   <productname>Postgres95</productname> was on identifying and
-   understanding existing problems in the server code.  With
-   <productname>PostgreSQL</productname>, the emphasis has shifted to
-   augmenting features and capabilities, although work continues in
-   all areas.
-  </para>
-
-<!## PG>
-  <para>
-   Details about what has happened in <productname>PostgreSQL</> since
-   then can be found in <xref linkend="release">.
-  </para>
-<!## end>
-<!## XC>
-  <para>
-   Details about what has happened in <productname>PostgreSQL</> since
-   then can be found in release notes.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   Details about what has happened in <productname>PostgreSQL</> since
-   then can be found in release notes.
-  </para>
-<!## end>
- </sect2>
-<!## XC>
-
-<sect2 id="rita-db">
- <title>NTT DATA <productname>Rita-DB</productname> Project</title>
-
- <indexterm zone="rita-db">
-  <primary>history</primary>
-  <secondary>of Rita-DB</secondary>
- </indexterm>
-&xconly;
- <para>
-  In 2001, NTT DATA began a research project
-  called <productname>Rita-DB</productname> which aimed to provide
-  both read and write scalability
-  of <productname>PostgreSQL</productname>.   The architecture was
-  very similar to current <productname>Postgres-XC</productname>.
-  After three years effort, it
-  was successful to provide globally transparent transaction
-  capability among database servers involved.
- </para>
-
- <para>
-  However, <productname>Rita-DB</productname> was not successful to
-  show that the architecture scales.  It scaled to some extent but the
-  result was not attractive to prospect users.
- </para>
-
- <para>
-  The result was presented in PostgreSQL anniversary summit in
-  Toronto.
- </para>
-
-</sect2>
-
-<sect2 id="pgxc-history">
- <title><productname>Postgres-XC</productname> from PostgreSQL</title>
-
- <indexterm zone="pgxc-history">
- <primary>history</primary>
- <secondary>of Postgres-XC</secondary>
- </indexterm>
-&xconly;
-
- <para>
-  In 2010, <productname>Rita-DB</productname> was carried over to
-  NTT's Open Source Software Center as Postgres-XC project.
-  EnterpriseDB Inc., joined the project. After six month effort,
-  they were successful to show
-  that multiple <productname>PostgreSQL</productname> can be
-  integrated into database cluster and they can provide transparent
-  global transaction management feature. Benchmark showed both read and
-  write scalability.
- </para>
-
- <para>
-  These outcome was presented in PGCon2010, CHAR(10) and JPUG
-  conference.
- </para>
-
- <para>
-  After then, the development and core teams decided to expand statement
-  capability of <productname>Postgres-XC</productname> to
-  full <productname>PostgreSQL</productname> as much as possible.
-  They're working hard to this goal.
- </para>
-
- <para>
-  <productname>Postgres-XC</productname> is under copyright of Postgres-XC Development
-  Group since 2012. More details about this legal entity can be found
-  <ulink url="https://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=Charter">here.</ulink>
- </para>
-<!## end>
-<!## XL>
-<sect2 id="pgxc-history">
- <title><productname>Postgres-XL</productname></title>
-
- <indexterm zone="pgxc-history">
- <primary>history</primary>
- <secondary>of Postgres-XL</secondary>
- </indexterm>
-&xlonly;
-
- <para>
-  In 2010, NTT's Open Source Software Center approached EnterpriseDB
-  to build off of NTT OSSC's experience with a project called RitaDB
-  and EnterpriseDB's experience with a project called GridSQL,
-  and the result was a new project, Postgres-XC.
- </para>
- <para>
-  In 2012, a company called StormDB was formed with some of the original key Postgres-XC developers. StormDB added enhancements, including MPP parallelism for performance and multi-tenant security.
- </para>
- <para>
-  In 2013, TransLattice acquired StormDB, and in 2014, open sourced it as Postgres-XL.
- </para>
-
-</sect2>
-<!## end>
-
-</sect1>
diff --git a/doc-xc/src/sgml/hstore.sgmlin b/doc-xc/src/sgml/hstore.sgmlin
deleted file mode 100644
index c711816a91..0000000000
--- a/doc-xc/src/sgml/hstore.sgmlin
+++ /dev/null
@@ -1,625 +0,0 @@
-<!-- doc/src/sgml/hstore.sgml -->
-
-<sect1 id="hstore" xreflabel="hstore">
- <title>hstore</title>
-
- <indexterm zone="hstore">
-  <primary>hstore</primary>
- </indexterm>
-&pgonly;
- <para>
-  This module implements the <type>hstore</> data type for storing sets of
-  key/value pairs within a single <productname>PostgreSQL</> value.
-  This can be useful in various scenarios, such as rows with many attributes
-  that are rarely examined, or semi-structured data.  Keys and values are
-  simply text strings.
- </para>
-
- <sect2>
-  <title><type>hstore</> External Representation</title>
-
-&pgonly;
-
-
-  <para>
-
-   The text representation of an <type>hstore</>, used for input and output,
-   includes zero or more <replaceable>key</> <literal>=&gt;</>
-   <replaceable>value</> pairs separated by commas. Some examples:
-
-<synopsis>
-k =&gt; v
-foo =&gt; bar, baz =&gt; whatever
-"1-a" =&gt; "anything at all"
-</synopsis>
-
-   The order of the pairs is not significant (and may not be reproduced on
-   output). Whitespace between pairs or around the <literal>=&gt;</> sign is
-   ignored. Double-quote keys and values that include whitespace, commas,
-   <literal>=</>s or <literal>&gt;</>s. To include a double quote or a
-   backslash in a key or value, escape it with a backslash.
-  </para>
-
-  <para>
-   Each key in an <type>hstore</> is unique. If you declare an <type>hstore</>
-   with duplicate keys, only one will be stored in the <type>hstore</> and
-   there is no guarantee as to which will be kept:
-
-<programlisting>
-SELECT 'a=&gt;1,a=&gt;2'::hstore;
-  hstore
-----------
- "a"=&gt;"1"
-</programlisting>
-  </para>
-
-  <para>
-   A value (but not a key) can be an SQL <literal>NULL</>. For example:
-
-<programlisting>
-key =&gt; NULL
-</programlisting>
-
-   The <literal>NULL</> keyword is case-insensitive. Double-quote the
-   <literal>NULL</> to treat it as the ordinary string <quote>NULL</quote>.
-  </para>
-
-  <note>
-  <para>
-   Keep in mind that the <type>hstore</> text format, when used for input,
-   applies <emphasis>before</> any required quoting or escaping. If you are
-   passing an <type>hstore</> literal via a parameter, then no additional
-   processing is needed. But if you're passing it as a quoted literal
-   constant, then any single-quote characters and (depending on the setting of
-   the <varname>standard_conforming_strings</> configuration parameter)
-   backslash characters need to be escaped correctly. See
-   <xref linkend="sql-syntax-strings"> for more on the handling of string
-   constants.
-  </para>
-  </note>
-
-  <para>
-   On output, double quotes always surround keys and values, even when it's
-   not strictly necessary.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title><type>hstore</> Operators and Functions</title>
-&pgonly;
-
-
-  <para>
-   The operators provided by the <literal>hstore</literal> module are
-   shown in <xref linkend="hstore-op-table">, the functions
-   in <xref linkend="hstore-func-table">.
-  </para>
-
-  <table id="hstore-op-table">
-   <title><type>hstore</> Operators</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Operator</entry>
-      <entry>Description</entry>
-      <entry>Example</entry>
-      <entry>Result</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><type>hstore</> <literal>-&gt;</> <type>text</></entry>
-      <entry>get value for key (<literal>NULL</> if not present)</entry>
-      <entry><literal>'a=&gt;x, b=&gt;y'::hstore -&gt; 'a'</literal></entry>
-      <entry><literal>x</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>hstore</> <literal>-&gt;</> <type>text[]</></entry>
-      <entry>get values for keys (<literal>NULL</> if not present)</entry>
-      <entry><literal>'a=&gt;x, b=&gt;y, c=&gt;z'::hstore -&gt; ARRAY['c','a']</literal></entry>
-      <entry><literal>{"z","x"}</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>text</> <literal>=&gt;</> <type>text</></entry>
-      <entry>make single-pair <type>hstore</></entry>
-      <entry><literal>'a' =&gt; 'b'</literal></entry>
-      <entry><literal>"a"=&gt;"b"</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>hstore</> <literal>||</> <type>hstore</></entry>
-      <entry>concatenate <type>hstore</>s</entry>
-      <entry><literal>'a=&gt;b, c=&gt;d'::hstore || 'c=&gt;x, d=&gt;q'::hstore</literal></entry>
-      <entry><literal>"a"=&gt;"b", "c"=&gt;"x", "d"=&gt;"q"</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>hstore</> <literal>?</> <type>text</></entry>
-      <entry>does <type>hstore</> contain key?</entry>
-      <entry><literal>'a=&gt;1'::hstore ? 'a'</literal></entry>
-      <entry><literal>t</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>hstore</> <literal>?&amp;</> <type>text[]</></entry>
-      <entry>does <type>hstore</> contain all specified keys?</entry>
-      <entry><literal>'a=&gt;1,b=&gt;2'::hstore ?&amp; ARRAY['a','b']</literal></entry>
-      <entry><literal>t</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>hstore</> <literal>?|</> <type>text[]</></entry>
-      <entry>does <type>hstore</> contain any of the specified keys?</entry>
-      <entry><literal>'a=&gt;1,b=&gt;2'::hstore ?| ARRAY['b','c']</literal></entry>
-      <entry><literal>t</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>hstore</> <literal>@&gt;</> <type>hstore</></entry>
-      <entry>does left operand contain right?</entry>
-      <entry><literal>'a=&gt;b, b=&gt;1, c=&gt;NULL'::hstore @&gt; 'b=&gt;1'</literal></entry>
-      <entry><literal>t</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>hstore</> <literal>&lt;@</> <type>hstore</></entry>
-      <entry>is left operand contained in right?</entry>
-      <entry><literal>'a=&gt;c'::hstore &lt;@ 'a=&gt;b, b=&gt;1, c=&gt;NULL'</literal></entry>
-      <entry><literal>f</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>hstore</> <literal>-</> <type>text</></entry>
-      <entry>delete key from left operand</entry>
-      <entry><literal>'a=&gt;1, b=&gt;2, c=&gt;3'::hstore - 'b'::text</literal></entry>
-      <entry><literal>"a"=&gt;"1", "c"=&gt;"3"</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>hstore</> <literal>-</> <type>text[]</></entry>
-      <entry>delete keys from left operand</entry>
-      <entry><literal>'a=&gt;1, b=&gt;2, c=&gt;3'::hstore - ARRAY['a','b']</literal></entry>
-      <entry><literal>"c"=&gt;"3"</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>hstore</> <literal>-</> <type>hstore</></entry>
-      <entry>delete matching pairs from left operand</entry>
-      <entry><literal>'a=&gt;1, b=&gt;2, c=&gt;3'::hstore - 'a=&gt;4, b=&gt;2'::hstore</literal></entry>
-      <entry><literal>"a"=&gt;"1", "c"=&gt;"3"</literal></entry>
-     </row>
-
-     <row>
-      <entry><type>record</> <literal>#=</> <type>hstore</></entry>
-      <entry>replace fields in <type>record</> with matching values from <type>hstore</></entry>
-      <entry>see Examples section</entry>
-      <entry></entry>
-     </row>
-
-     <row>
-      <entry><literal>%%</> <type>hstore</></entry>
-      <entry>convert <type>hstore</> to array of alternating keys and values</entry>
-      <entry><literal>%% 'a=&gt;foo, b=&gt;bar'::hstore</literal></entry>
-      <entry><literal>{a,foo,b,bar}</literal></entry>
-     </row>
-
-     <row>
-      <entry><literal>%#</> <type>hstore</></entry>
-      <entry>convert <type>hstore</> to two-dimensional key/value array</entry>
-      <entry><literal>%# 'a=&gt;foo, b=&gt;bar'::hstore</literal></entry>
-      <entry><literal>{{a,foo},{b,bar}}</literal></entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <note>
-  <para>
-   Prior to PostgreSQL 8.2, the containment operators <literal>@&gt;</>
-   and <literal>&lt;@</> were called <literal>@</> and <literal>~</>,
-   respectively. These names are still available, but are deprecated and will
-   eventually be removed. Notice that the old names are reversed from the
-   convention formerly followed by the core geometric data types!
-   </para>
-  </note>
-
-  <note>
-  <para>
-   The <literal>=&gt;</> operator is deprecated and may be removed in a
-   future release.  Use the <literal>hstore(text, text)</literal> function
-   instead.
-   </para>
-  </note>
-
-  <table id="hstore-func-table">
-   <title><type>hstore</> Functions</title>
-
-   <tgroup cols="5">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Return Type</entry>
-      <entry>Description</entry>
-      <entry>Example</entry>
-      <entry>Result</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><function>hstore(record)</function></entry>
-      <entry><type>hstore</type></entry>
-      <entry>construct an <type>hstore</> from a record or row</entry>
-      <entry><literal>hstore(ROW(1,2))</literal></entry>
-      <entry><literal>f1=&gt;1,f2=&gt;2</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>hstore(text[])</function></entry>
-      <entry><type>hstore</type></entry>
-      <entry>construct an <type>hstore</> from an array, which may be either
-       a key/value array, or a two-dimensional array</entry>
-      <entry><literal>hstore(ARRAY['a','1','b','2']) || hstore(ARRAY[['c','3'],['d','4']])</literal></entry>
-      <entry><literal>a=&gt;1, b=&gt;2, c=&gt;3, d=&gt;4</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>hstore(text[], text[])</function></entry>
-      <entry><type>hstore</type></entry>
-      <entry>construct an <type>hstore</> from separate key and value arrays</entry>
-      <entry><literal>hstore(ARRAY['a','b'], ARRAY['1','2'])</literal></entry>
-      <entry><literal>"a"=&gt;"1","b"=&gt;"2"</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>hstore(text, text)</function></entry>
-      <entry><type>hstore</type></entry>
-      <entry>make single-item <type>hstore</></entry>
-      <entry><literal>hstore('a', 'b')</literal></entry>
-      <entry><literal>"a"=&gt;"b"</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>akeys(hstore)</function></entry>
-      <entry><type>text[]</type></entry>
-      <entry>get <type>hstore</>'s keys as an array</entry>
-      <entry><literal>akeys('a=&gt;1,b=&gt;2')</literal></entry>
-      <entry><literal>{a,b}</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>skeys(hstore)</function></entry>
-      <entry><type>setof text</type></entry>
-      <entry>get <type>hstore</>'s keys as a set</entry>
-      <entry><literal>skeys('a=&gt;1,b=&gt;2')</literal></entry>
-      <entry>
-<programlisting>
-a
-b
-</programlisting></entry>
-     </row>
-
-     <row>
-      <entry><function>avals(hstore)</function></entry>
-      <entry><type>text[]</type></entry>
-      <entry>get <type>hstore</>'s values as an array</entry>
-      <entry><literal>avals('a=&gt;1,b=&gt;2')</literal></entry>
-      <entry><literal>{1,2}</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>svals(hstore)</function></entry>
-      <entry><type>setof text</type></entry>
-      <entry>get <type>hstore</>'s values as a set</entry>
-      <entry><literal>svals('a=&gt;1,b=&gt;2')</literal></entry>
-      <entry>
-<programlisting>
-1
-2
-</programlisting></entry>
-     </row>
-
-     <row>
-      <entry><function>hstore_to_array(hstore)</function></entry>
-      <entry><type>text[]</type></entry>
-      <entry>get <type>hstore</>'s keys and values as an array of alternating
-       keys and values</entry>
-      <entry><literal>hstore_to_array('a=&gt;1,b=&gt;2')</literal></entry>
-      <entry><literal>{a,1,b,2}</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>hstore_to_matrix(hstore)</function></entry>
-      <entry><type>text[]</type></entry>
-      <entry>get <type>hstore</>'s keys and values as a two-dimensional array</entry>
-      <entry><literal>hstore_to_matrix('a=&gt;1,b=&gt;2')</literal></entry>
-      <entry><literal>{{a,1},{b,2}}</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>slice(hstore, text[])</function></entry>
-      <entry><type>hstore</type></entry>
-      <entry>extract a subset of an <type>hstore</></entry>
-      <entry><literal>slice('a=&gt;1,b=&gt;2,c=&gt;3'::hstore, ARRAY['b','c','x'])</literal></entry>
-      <entry><literal>"b"=&gt;"2", "c"=&gt;"3"</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>each(hstore)</function></entry>
-      <entry><type>setof(key text, value text)</type></entry>
-      <entry>get <type>hstore</>'s keys and values as a set</entry>
-      <entry><literal>select * from each('a=&gt;1,b=&gt;2')</literal></entry>
-      <entry>
-<programlisting>
- key | value
------+-------
- a   | 1
- b   | 2
-</programlisting></entry>
-     </row>
-
-     <row>
-      <entry><function>exist(hstore,text)</function></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does <type>hstore</> contain key?</entry>
-      <entry><literal>exist('a=&gt;1','a')</literal></entry>
-      <entry><literal>t</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>defined(hstore,text)</function></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does <type>hstore</> contain non-<literal>NULL</> value for key?</entry>
-      <entry><literal>defined('a=&gt;NULL','a')</literal></entry>
-      <entry><literal>f</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>delete(hstore,text)</function></entry>
-      <entry><type>hstore</type></entry>
-      <entry>delete pair with matching key</entry>
-      <entry><literal>delete('a=&gt;1,b=&gt;2','b')</literal></entry>
-      <entry><literal>"a"=>"1"</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>delete(hstore,text[])</function></entry>
-      <entry><type>hstore</type></entry>
-      <entry>delete pairs with matching keys</entry>
-      <entry><literal>delete('a=&gt;1,b=&gt;2,c=&gt;3',ARRAY['a','b'])</literal></entry>
-      <entry><literal>"c"=>"3"</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>delete(hstore,hstore)</function></entry>
-      <entry><type>hstore</type></entry>
-      <entry>delete pairs matching those in the second argument</entry>
-      <entry><literal>delete('a=&gt;1,b=&gt;2','a=&gt;4,b=&gt;2'::hstore)</literal></entry>
-      <entry><literal>"a"=>"1"</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>populate_record(record,hstore)</function></entry>
-      <entry><type>record</type></entry>
-      <entry>replace fields in <type>record</> with matching values from <type>hstore</></entry>
-      <entry>see Examples section</entry>
-      <entry></entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <note>
-   <para>
-    The function <function>populate_record</function> is actually declared
-    with <type>anyelement</>, not <type>record</>, as its first argument,
-    but it will reject non-record types with a run-time error.
-   </para>
-  </note>
- </sect2>
-
- <sect2>
-  <title>Indexes</title>
-
-&pgonly;
-
-
-  <para>
-   <type>hstore</> has GiST and GIN index support for the <literal>@&gt;</>,
-   <literal>?</>, <literal>?&amp;</> and <literal>?|</> operators. For example:
-  </para>
-<programlisting>
-CREATE INDEX hidx ON testhstore USING GIST (h);
-
-CREATE INDEX hidx ON testhstore USING GIN (h);
-</programlisting>
-
-  <para>
-   <type>hstore</> also supports <type>btree</> or <type>hash</> indexes for
-   the <literal>=</> operator. This allows <type>hstore</> columns to be
-   declared <literal>UNIQUE</>, or to be used in <literal>GROUP BY</>,
-   <literal>ORDER BY</> or <literal>DISTINCT</> expressions. The sort ordering
-   for <type>hstore</> values is not particularly useful, but these indexes
-   may be useful for equivalence lookups. Create indexes for <literal>=</>
-   comparisons as follows:
-  </para>
-<programlisting>
-CREATE INDEX hidx ON testhstore USING BTREE (h);
-
-CREATE INDEX hidx ON testhstore USING HASH (h);
-</programlisting>
- </sect2>
-
- <sect2>
-  <title>Examples</title>
-
-&pgonly;
-
-
-  <para>
-   Add a key, or update an existing key with a new value:
-<programlisting>
-UPDATE tab SET h = h || ('c' =&gt; '3');
-</programlisting>
-  </para>
-
-  <para>
-   Delete a key:
-<programlisting>
-UPDATE tab SET h = delete(h, 'k1');
-</programlisting>
-  </para>
-
-  <para>
-   Convert a <type>record</> to an <type>hstore</>:
-<programlisting>
-CREATE TABLE test (col1 integer, col2 text, col3 text);
-INSERT INTO test VALUES (123, 'foo', 'bar');
-
-SELECT hstore(t) FROM test AS t;
-                   hstore                    
----------------------------------------------
- "col1"=&gt;"123", "col2"=&gt;"foo", "col3"=&gt;"bar"
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-   Convert an <type>hstore</> to a predefined <type>record</> type:
-<programlisting>
-CREATE TABLE test (col1 integer, col2 text, col3 text);
-
-SELECT * FROM populate_record(null::test,
-                              '"col1"=&gt;"456", "col2"=&gt;"zzz"');
- col1 | col2 | col3 
-------+------+------
-  456 | zzz  | 
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-   Modify an existing record using the values from an <type>hstore</>:
-<programlisting>
-CREATE TABLE test (col1 integer, col2 text, col3 text);
-INSERT INTO test VALUES (123, 'foo', 'bar');
-
-SELECT (r).* FROM (SELECT t #= '"col3"=&gt;"baz"' AS r FROM test t) s;
- col1 | col2 | col3 
-------+------+------
-  123 | foo  | baz
-(1 row)
-</programlisting>
-  </para>
- </sect2>
-
- <sect2>
-  <title>Statistics</title>
-
-&pgonly;
-
-
-  <para>
-   The <type>hstore</> type, because of its intrinsic liberality, could
-   contain a lot of different keys. Checking for valid keys is the task of the
-   application. The following examples demonstrate several techniques for
-   checking keys and obtaining statistics.
-  </para>
-
-  <para>
-   Simple example:
-<programlisting>
-SELECT * FROM each('aaa=&gt;bq, b=&gt;NULL, ""=&gt;1');
-</programlisting>
-  </para>
-
-  <para>
-   Using a table:
-<programlisting>
-SELECT (each(h)).key, (each(h)).value INTO stat FROM testhstore;
-</programlisting>
-  </para>
-
-  <para>
-   Online statistics:
-<programlisting>
-SELECT key, count(*) FROM
-  (SELECT (each(h)).key FROM testhstore) AS stat
-  GROUP BY key
-  ORDER BY count DESC, key;
-    key    | count
------------+-------
- line      |   883
- query     |   207
- pos       |   203
- node      |   202
- space     |   197
- status    |   195
- public    |   194
- title     |   190
- org       |   189
-...................
-</programlisting>
-  </para>
- </sect2>
-
- <sect2>
-  <title>Compatibility</title>
-
-&pgonly;
-
-
-  <para>
-   As of PostgreSQL 9.0, <type>hstore</> uses a different internal
-   representation than previous versions. This presents no obstacle for
-   dump/restore upgrades since the text representation (used in the dump) is
-   unchanged.
-  </para>
-
-  <para>
-   In the event of a binary upgrade, upward compatibility is maintained by
-   having the new code recognize old-format data. This will entail a slight
-   performance penalty when processing data that has not yet been modified by
-   the new code. It is possible to force an upgrade of all values in a table
-   column by doing an <literal>UPDATE</> statement as follows:
-<programlisting>
-UPDATE tablename SET hstorecol = hstorecol || '';
-</programlisting>
-  </para>
-
-  <para>
-   Another way to do it is:
-<programlisting>
-ALTER TABLE tablename ALTER hstorecol TYPE hstore USING hstorecol || '';
-</programlisting>
-   The <command>ALTER TABLE</> method requires an exclusive lock on the table,
-   but does not result in bloating the table with old row versions.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>Authors</title>
-
-  <para>
-   Oleg Bartunov <email>[email protected]</email>, Moscow, Moscow University, Russia
-  </para>
-
-  <para>
-   Teodor Sigaev <email>[email protected]</email>, Moscow, Delta-Soft Ltd., Russia
-  </para>
-
-  <para>
-   Additional enhancements by Andrew Gierth <email>[email protected]</email>,
-   United Kingdom
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/indexam.sgmlin b/doc-xc/src/sgml/indexam.sgmlin
deleted file mode 100644
index e5dcf45032..0000000000
--- a/doc-xc/src/sgml/indexam.sgmlin
+++ /dev/null
@@ -1,1133 +0,0 @@
-<!-- doc/src/sgml/indexam.sgml -->
-
-<chapter id="indexam">
- <title>Index Access Method Interface Definition</title>
-
-&common;
-
-  <para>
-   This chapter defines the interface between the core
-   <productname>PostgreSQL</productname> system and <firstterm>index access
-   methods</>, which manage individual index types.  The core system
-   knows nothing about indexes beyond what is specified here, so it is
-   possible to develop entirely new index types by writing add-on code.
-  </para>
-
-  <para>
-   All indexes in <productname>PostgreSQL</productname> are what are known
-   technically as <firstterm>secondary indexes</>; that is, the index is
-   physically separate from the table file that it describes.  Each index
-   is stored as its own physical <firstterm>relation</> and so is described
-   by an entry in the <structname>pg_class</> catalog.  The contents of an
-   index are entirely under the control of its index access method.  In
-   practice, all index access methods divide indexes into standard-size
-   pages so that they can use the regular storage manager and buffer manager
-   to access the index contents.  (All the existing index access methods
-   furthermore use the standard page layout described in <xref
-   linkend="storage-page-layout">, and they all use the same format for index
-   tuple headers; but these decisions are not forced on an access method.)
-  </para>
-
-  <para>
-   An index is effectively a mapping from some data key values to
-   <firstterm>tuple identifiers</>, or <acronym>TIDs</>, of row versions
-   (tuples) in the index's parent table.  A TID consists of a
-   block number and an item number within that block (see <xref
-   linkend="storage-page-layout">).  This is sufficient
-   information to fetch a particular row version from the table.
-   Indexes are not directly aware that under MVCC, there might be multiple
-   extant versions of the same logical row; to an index, each tuple is
-   an independent object that needs its own index entry.  Thus, an
-   update of a row always creates all-new index entries for the row, even if
-   the key values did not change.  (HOT tuples are an exception to this
-   statement; but indexes do not deal with those, either.)  Index entries for
-   dead tuples are reclaimed (by vacuuming) when the dead tuples themselves
-   are reclaimed.
-  </para>
-
- <sect1 id="index-catalog">
-  <title>Catalog Entries for Indexes</title>
-
-&common;
-  <para>
-   Each index access method is described by a row in the
-   <structname>pg_am</structname> system catalog (see
-   <xref linkend="catalog-pg-am">).  The principal contents of a
-   <structname>pg_am</structname> row are references to
-   <link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>
-   entries that identify the index access
-   functions supplied by the access method.  The APIs for these functions
-   are defined later in this chapter.  In addition, the
-   <structname>pg_am</structname> row specifies a few fixed properties of
-   the access method, such as whether it can support multicolumn indexes.
-   There is not currently any special support
-   for creating or deleting <structname>pg_am</structname> entries;
-   anyone able to write a new access method is expected to be competent
-   to insert an appropriate row for themselves.
-  </para>
-
-  <para>
-   To be useful, an index access method must also have one or more
-   <firstterm>operator families</> and
-   <firstterm>operator classes</> defined in
-   <link linkend="catalog-pg-opfamily"><structname>pg_opfamily</structname></link>,
-   <link linkend="catalog-pg-opclass"><structname>pg_opclass</structname></link>,
-   <link linkend="catalog-pg-amop"><structname>pg_amop</structname></link>, and
-   <link linkend="catalog-pg-amproc"><structname>pg_amproc</structname></link>.
-   These entries allow the planner
-   to determine what kinds of query qualifications can be used with
-   indexes of this access method.  Operator families and classes are described
-   in <xref linkend="xindex">, which is prerequisite material for reading
-   this chapter.
-  </para>
-
-  <para>
-   An individual index is defined by a
-   <link linkend="catalog-pg-class"><structname>pg_class</structname></link>
-   entry that describes it as a physical relation, plus a
-   <link linkend="catalog-pg-index"><structname>pg_index</structname></link>
-   entry that shows the logical content of the index &mdash; that is, the set
-   of index columns it has and the semantics of those columns, as captured by
-   the associated operator classes.  The index columns (key values) can be
-   either simple columns of the underlying table or expressions over the table
-   rows.  The index access method normally has no interest in where the index
-   key values come from (it is always handed precomputed key values) but it
-   will be very interested in the operator class information in
-   <structname>pg_index</structname>.  Both of these catalog entries can be
-   accessed as part of the <structname>Relation</> data structure that is
-   passed to all operations on the index.
-  </para>
-
-  <para>
-   Some of the flag columns of <structname>pg_am</structname> have nonobvious
-   implications.  The requirements of <structfield>amcanunique</structfield>
-   are discussed in <xref linkend="index-unique-checks">.
-   The <structfield>amcanmulticol</structfield> flag asserts that the
-   access method supports multicolumn indexes, while
-   <structfield>amoptionalkey</structfield> asserts that it allows scans
-   where no indexable restriction clause is given for the first index column.
-   When <structfield>amcanmulticol</structfield> is false,
-   <structfield>amoptionalkey</structfield> essentially says whether the
-   access method supports full-index scans without any restriction clause.
-   Access methods that support multiple index columns <emphasis>must</>
-   support scans that omit restrictions on any or all of the columns after
-   the first; however they are permitted to require some restriction to
-   appear for the first index column, and this is signaled by setting
-   <structfield>amoptionalkey</structfield> false.
-   One reason that an index AM might set
-   <structfield>amoptionalkey</structfield> false is if it doesn't index
-   NULLs.  Since most indexable operators are
-   strict and hence cannot return TRUE for NULL inputs,
-   it is at first sight attractive to not store index entries for null values:
-   they could never be returned by an index scan anyway.  However, this
-   argument fails when an index scan has no restriction clause for a given
-   index column.  In practice this means that
-   indexes that have <structfield>amoptionalkey</structfield> true must
-   index nulls, since the planner might decide to use such an index
-   with no scan keys at all.  A related restriction is that an index
-   access method that supports multiple index columns <emphasis>must</>
-   support indexing null values in columns after the first, because the planner
-   will assume the index can be used for queries that do not restrict
-   these columns.  For example, consider an index on (a,b) and a query with
-   <literal>WHERE a = 4</literal>.  The system will assume the index can be
-   used to scan for rows with <literal>a = 4</literal>, which is wrong if the
-   index omits rows where <literal>b</> is null.
-   It is, however, OK to omit rows where the first indexed column is null.
-   An index access method that does index nulls may also set
-   <structfield>amsearchnulls</structfield>, indicating that it supports
-   <literal>IS NULL</> and <literal>IS NOT NULL</> clauses as search
-   conditions.
-  </para>
-
- </sect1>
-
- <sect1 id="index-functions">
-  <title>Index Access Method Functions</title>
-
-&common;
-  <para>
-   The index construction and maintenance functions that an index access
-   method must provide are:
-  </para>
-
-  <para>
-<programlisting>
-IndexBuildResult *
-ambuild (Relation heapRelation,
-         Relation indexRelation,
-         IndexInfo *indexInfo);
-</programlisting>
-   Build a new index.  The index relation has been physically created,
-   but is empty.  It must be filled in with whatever fixed data the
-   access method requires, plus entries for all tuples already existing
-   in the table.  Ordinarily the <function>ambuild</> function will call
-   <function>IndexBuildHeapScan()</> to scan the table for existing tuples
-   and compute the keys that need to be inserted into the index.
-   The function must return a palloc'd struct containing statistics about
-   the new index.
-  </para>
-
-  <para>
-<programlisting>
-void
-ambuildempty (Relation indexRelation);
-</programlisting>
-   Build an empty index, and write it to the initialization fork (INIT_FORKNUM)
-   of the given relation.  This method is called only for unlogged tables; the
-   empty index written to the initialization fork will be copied over the main
-   relation fork on each server restart.
-  </para>
-
-  <para>
-<programlisting>
-bool
-aminsert (Relation indexRelation,
-          Datum *values,
-          bool *isnull,
-          ItemPointer heap_tid,
-          Relation heapRelation,
-          IndexUniqueCheck checkUnique);
-</programlisting>
-   Insert a new tuple into an existing index.  The <literal>values</> and
-   <literal>isnull</> arrays give the key values to be indexed, and
-   <literal>heap_tid</> is the TID to be indexed.
-   If the access method supports unique indexes (its
-   <structname>pg_am</>.<structfield>amcanunique</> flag is true) then
-   <literal>checkUnique</> indicates the type of uniqueness check to
-   perform.  This varies depending on whether the unique constraint is
-   deferrable; see <xref linkend="index-unique-checks"> for details.
-   Normally the access method only needs the <literal>heapRelation</>
-   parameter when performing uniqueness checking (since then it will have to
-   look into the heap to verify tuple liveness).
-  </para>
-
-  <para>
-   The function's Boolean result value is significant only when
-   <literal>checkUnique</> is <literal>UNIQUE_CHECK_PARTIAL</>.
-   In this case a TRUE result means the new entry is known unique, whereas
-   FALSE means it might be non-unique (and a deferred uniqueness check must
-   be scheduled).  For other cases a constant FALSE result is recommended.
-  </para>
-
-  <para>
-   Some indexes might not index all tuples.  If the tuple is not to be
-   indexed, <function>aminsert</> should just return without doing anything.
-  </para>
-
-  <para>
-<programlisting>
-IndexBulkDeleteResult *
-ambulkdelete (IndexVacuumInfo *info,
-              IndexBulkDeleteResult *stats,
-              IndexBulkDeleteCallback callback,
-              void *callback_state);
-</programlisting>
-   Delete tuple(s) from the index.  This is a <quote>bulk delete</> operation
-   that is intended to be implemented by scanning the whole index and checking
-   each entry to see if it should be deleted.
-   The passed-in <literal>callback</> function must be called, in the style
-   <literal>callback(<replaceable>TID</>, callback_state) returns bool</literal>,
-   to determine whether any particular index entry, as identified by its
-   referenced TID, is to be deleted.  Must return either NULL or a palloc'd
-   struct containing statistics about the effects of the deletion operation.
-   It is OK to return NULL if no information needs to be passed on to
-   <function>amvacuumcleanup</>.
-  </para>
-
-  <para>
-   Because of limited <varname>maintenance_work_mem</>,
-   <function>ambulkdelete</> might need to be called more than once when many
-   tuples are to be deleted.  The <literal>stats</> argument is the result
-   of the previous call for this index (it is NULL for the first call within a
-   <command>VACUUM</> operation).  This allows the AM to accumulate statistics
-   across the whole operation.  Typically, <function>ambulkdelete</> will
-   modify and return the same struct if the passed <literal>stats</> is not
-   null.
-  </para>
-
-  <para>
-<programlisting>
-IndexBulkDeleteResult *
-amvacuumcleanup (IndexVacuumInfo *info,
-                 IndexBulkDeleteResult *stats);
-</programlisting>
-   Clean up after a <command>VACUUM</command> operation (zero or more
-   <function>ambulkdelete</> calls).  This does not have to do anything
-   beyond returning index statistics, but it might perform bulk cleanup
-   such as reclaiming empty index pages.  <literal>stats</> is whatever the
-   last <function>ambulkdelete</> call returned, or NULL if
-   <function>ambulkdelete</> was not called because no tuples needed to be
-   deleted.  If the result is not NULL it must be a palloc'd struct.
-   The statistics it contains will be used to update <structname>pg_class</>,
-   and will be reported by <command>VACUUM</> if <literal>VERBOSE</> is given.
-   It is OK to return NULL if the index was not changed at all during the
-   <command>VACUUM</command> operation, but otherwise correct stats should
-   be returned.
-  </para>
-
-  <para>
-   As of <productname>PostgreSQL</productname> 8.4,
-   <function>amvacuumcleanup</> will also be called at completion of an
-   <command>ANALYZE</> operation.  In this case <literal>stats</> is always
-   NULL and any return value will be ignored.  This case can be distinguished
-   by checking <literal>info-&gt;analyze_only</literal>.  It is recommended
-   that the access method do nothing except post-insert cleanup in such a
-   call, and that only in an autovacuum worker process.
-  </para>
-
-  <para>
-<programlisting>
-void
-amcostestimate (PlannerInfo *root,
-                IndexOptInfo *index,
-                List *indexQuals,
-                List *indexOrderBys,
-                RelOptInfo *outer_rel,
-                Cost *indexStartupCost,
-                Cost *indexTotalCost,
-                Selectivity *indexSelectivity,
-                double *indexCorrelation);
-</programlisting>
-   Estimate the costs of an index scan.  This function is described fully
-   in <xref linkend="index-cost-estimation">, below.
-  </para>
-
-  <para>
-<programlisting>
-bytea *
-amoptions (ArrayType *reloptions,
-           bool validate);
-</programlisting>
-   Parse and validate the reloptions array for an index.  This is called only
-   when a non-null reloptions array exists for the index.
-   <parameter>reloptions</> is a <type>text</> array containing entries of the
-   form <replaceable>name</><literal>=</><replaceable>value</>.
-   The function should construct a <type>bytea</> value, which will be copied
-   into the <structfield>rd_options</> field of the index's relcache entry.
-   The data contents of the <type>bytea</> value are open for the access
-   method to define; most of the standard access methods use struct
-   <structname>StdRdOptions</>.
-   When <parameter>validate</> is true, the function should report a suitable
-   error message if any of the options are unrecognized or have invalid
-   values; when <parameter>validate</> is false, invalid entries should be
-   silently ignored.  (<parameter>validate</> is false when loading options
-   already stored in <structname>pg_catalog</>; an invalid entry could only
-   be found if the access method has changed its rules for options, and in
-   that case ignoring obsolete entries is appropriate.)
-   It is OK to return NULL if default behavior is wanted.
-  </para>
-
-  <para>
-   The purpose of an index, of course, is to support scans for tuples matching
-   an indexable <literal>WHERE</> condition, often called a
-   <firstterm>qualifier</> or <firstterm>scan key</>.  The semantics of
-   index scanning are described more fully in <xref linkend="index-scanning">,
-   below.  An index access method can support <quote>plain</> index scans,
-   <quote>bitmap</> index scans, or both.  The scan-related functions that an
-   index access method must or may provide are:
-  </para>
-
-  <para>
-<programlisting>
-IndexScanDesc
-ambeginscan (Relation indexRelation,
-             int nkeys,
-             int norderbys);
-</programlisting>
-   Prepare for an index scan.  The <literal>nkeys</> and <literal>norderbys</>
-   parameters indicate the number of quals and ordering operators that will be
-   used in the scan; these may be useful for space allocation purposes.
-   Note that the actual values of the scan keys aren't provided yet.
-   The result must be a palloc'd struct.
-   For implementation reasons the index access method
-   <emphasis>must</> create this struct by calling
-   <function>RelationGetIndexScan()</>.  In most cases
-   <function>ambeginscan</> does little beyond making that call and perhaps
-   acquiring locks;
-   the interesting parts of index-scan startup are in <function>amrescan</>.
-  </para>
-
-  <para>
-<programlisting>
-void
-amrescan (IndexScanDesc scan,
-          ScanKey keys,
-          int nkeys,
-          ScanKey orderbys,
-          int norderbys);
-</programlisting>
-   Start or restart an indexscan, possibly with new scan keys.  (To restart
-   using previously-passed keys, NULL is passed for <literal>keys</> and/or
-   <literal>orderbys</>.)  Note that it is not allowed for
-   the number of keys or order-by operators to be larger than
-   what was passed to <function>ambeginscan</>.  In practice the restart
-   feature is used when a new outer tuple is selected by a nested-loop join
-   and so a new key comparison value is needed, but the scan key structure
-   remains the same.
-  </para>
-
-  <para>
-<programlisting>
-boolean
-amgettuple (IndexScanDesc scan,
-            ScanDirection direction);
-</programlisting>
-   Fetch the next tuple in the given scan, moving in the given
-   direction (forward or backward in the index).  Returns TRUE if a tuple was
-   obtained, FALSE if no matching tuples remain.  In the TRUE case the tuple
-   TID is stored into the <literal>scan</> structure.  Note that
-   <quote>success</> means only that the index contains an entry that matches
-   the scan keys, not that the tuple necessarily still exists in the heap or
-   will pass the caller's snapshot test.  On success, <function>amgettuple</>
-   must also set <literal>scan-&gt;xs_recheck</> to TRUE or FALSE.
-   FALSE means it is certain that the index entry matches the scan keys.
-   TRUE means this is not certain, and the conditions represented by the
-   scan keys must be rechecked against the heap tuple after fetching it.
-   This provision supports <quote>lossy</> index operators.
-   Note that rechecking will extend only to the scan conditions; a partial
-   index predicate (if any) is never rechecked by <function>amgettuple</>
-   callers.
-  </para>
-
-  <para>
-   The <function>amgettuple</> function need only be provided if the access
-   method supports <quote>plain</> index scans.  If it doesn't, the
-   <structfield>amgettuple</> field in its <structname>pg_am</> row must
-   be set to zero.
-  </para>
-
-  <para>
-<programlisting>
-int64
-amgetbitmap (IndexScanDesc scan,
-             TIDBitmap *tbm);
-</programlisting>
-   Fetch all tuples in the given scan and add them to the caller-supplied
-   <type>TIDBitmap</type> (that is, OR the set of tuple IDs into whatever set is already
-   in the bitmap).  The number of tuples fetched is returned (this might be
-   just an approximate count, for instance some AMs do not detect duplicates).
-   While inserting tuple IDs into the bitmap, <function>amgetbitmap</> can
-   indicate that rechecking of the scan conditions is required for specific
-   tuple IDs.  This is analogous to the <literal>xs_recheck</> output parameter
-   of <function>amgettuple</>.  Note: in the current implementation, support
-   for this feature is conflated with support for lossy storage of the bitmap
-   itself, and therefore callers recheck both the scan conditions and the
-   partial index predicate (if any) for recheckable tuples.  That might not
-   always be true, however.
-   <function>amgetbitmap</> and
-   <function>amgettuple</> cannot be used in the same index scan; there
-   are other restrictions too when using <function>amgetbitmap</>, as explained
-   in <xref linkend="index-scanning">.
-  </para>
-
-  <para>
-   The <function>amgetbitmap</> function need only be provided if the access
-   method supports <quote>bitmap</> index scans.  If it doesn't, the
-   <structfield>amgetbitmap</> field in its <structname>pg_am</> row must
-   be set to zero.
-  </para>
-
-  <para>
-<programlisting>
-void
-amendscan (IndexScanDesc scan);
-</programlisting>
-   End a scan and release resources.  The <literal>scan</> struct itself
-   should not be freed, but any locks or pins taken internally by the
-   access method must be released.
-  </para>
-
-  <para>
-<programlisting>
-void
-ammarkpos (IndexScanDesc scan);
-</programlisting>
-   Mark current scan position.  The access method need only support one
-   remembered scan position per scan.
-  </para>
-
-  <para>
-<programlisting>
-void
-amrestrpos (IndexScanDesc scan);
-</programlisting>
-   Restore the scan to the most recently marked position.
-  </para>
-
-  <para>
-   By convention, the <literal>pg_proc</literal> entry for an index
-   access method function should show the correct number of arguments,
-   but declare them all as type <type>internal</> (since most of the arguments
-   have types that are not known to SQL, and we don't want users calling
-   the functions directly anyway).  The return type is declared as
-   <type>void</>, <type>internal</>, or <type>boolean</> as appropriate.
-   The only exception is <function>amoptions</>, which should be correctly
-   declared as taking <type>text[]</> and <type>bool</> and returning
-   <type>bytea</>.  This provision allows client code to execute
-   <function>amoptions</> to test validity of options settings.
-  </para>
-
- </sect1>
-
- <sect1 id="index-scanning">
-  <title>Index Scanning</title>
-
-&common;
-  <para>
-   In an index scan, the index access method is responsible for regurgitating
-   the TIDs of all the tuples it has been told about that match the
-   <firstterm>scan keys</>.  The access method is <emphasis>not</> involved in
-   actually fetching those tuples from the index's parent table, nor in
-   determining whether they pass the scan's time qualification test or other
-   conditions.
-  </para>
-
-  <para>
-   A scan key is the internal representation of a <literal>WHERE</> clause of
-   the form <replaceable>index_key</> <replaceable>operator</>
-   <replaceable>constant</>, where the index key is one of the columns of the
-   index and the operator is one of the members of the operator family
-   associated with that index column.  An index scan has zero or more scan
-   keys, which are implicitly ANDed &mdash; the returned tuples are expected
-   to satisfy all the indicated conditions.
-  </para>
-
-  <para>
-   The access method can report that the index is <firstterm>lossy</>, or
-   requires rechecks, for a particular query.  This implies that the index
-   scan will return all the entries that pass the scan key, plus possibly
-   additional entries that do not.  The core system's index-scan machinery
-   will then apply the index conditions again to the heap tuple to verify
-   whether or not it really should be selected.  If the recheck option is not
-   specified, the index scan must return exactly the set of matching entries.
-  </para>
-
-  <para>
-   Note that it is entirely up to the access method to ensure that it
-   correctly finds all and only the entries passing all the given scan keys.
-   Also, the core system will simply hand off all the <literal>WHERE</>
-   clauses that match the index keys and operator families, without any
-   semantic analysis to determine whether they are redundant or
-   contradictory.  As an example, given
-   <literal>WHERE x &gt; 4 AND x &gt; 14</> where <literal>x</> is a b-tree
-   indexed column, it is left to the b-tree <function>amrescan</> function
-   to realize that the first scan key is redundant and can be discarded.
-   The extent of preprocessing needed during <function>amrescan</> will
-   depend on the extent to which the index access method needs to reduce
-   the scan keys to a <quote>normalized</> form.
-  </para>
-
-  <para>
-   Some access methods return index entries in a well-defined order, others
-   do not.  There are actually two different ways that an access method can
-   support sorted output:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Access methods that always return entries in the natural ordering
-       of their data (such as btree) should set
-       <structname>pg_am</>.<structfield>amcanorder</> to true.
-       Currently, such access methods must use btree-compatible strategy
-       numbers for their equality and ordering operators.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Access methods that support ordering operators should set
-       <structname>pg_am</>.<structfield>amcanorderbyop</> to true.
-       This indicates that the index is capable of returning entries in
-       an order satisfying <literal>ORDER BY</> <replaceable>index_key</>
-       <replaceable>operator</> <replaceable>constant</>.  Scan modifiers
-       of that form can be passed to <function>amrescan</> as described
-       previously.
-      </para>
-     </listitem>
-    </itemizedlist>
-  </para>
-
-  <para>
-   The <function>amgettuple</> function has a <literal>direction</> argument,
-   which can be either <literal>ForwardScanDirection</> (the normal case)
-   or  <literal>BackwardScanDirection</>.  If the first call after
-   <function>amrescan</> specifies <literal>BackwardScanDirection</>, then the
-   set of matching index entries is to be scanned back-to-front rather than in
-   the normal front-to-back direction, so <function>amgettuple</> must return
-   the last matching tuple in the index, rather than the first one as it
-   normally would.  (This will only occur for access
-   methods that set <structfield>amcanorder</> to true.)  After the
-   first call, <function>amgettuple</> must be prepared to advance the scan in
-   either direction from the most recently returned entry.  (But if
-   <structname>pg_am</>.<structfield>amcanbackward</> is false, all subsequent
-   calls will have the same direction as the first one.)
-  </para>
-
-  <para>
-   Access methods that support ordered scans must support <quote>marking</> a
-   position in a scan and later returning to the marked position.  The same
-   position might be restored multiple times.  However, only one position need
-   be remembered per scan; a new <function>ammarkpos</> call overrides the
-   previously marked position.  An access method that does not support
-   ordered scans should still provide mark and restore functions in
-   <structname>pg_am</>, but it is sufficient to have them throw errors if
-   called.
-  </para>
-
-  <para>
-   Both the scan position and the mark position (if any) must be maintained
-   consistently in the face of concurrent insertions or deletions in the
-   index.  It is OK if a freshly-inserted entry is not returned by a scan that
-   would have found the entry if it had existed when the scan started, or for
-   the scan to return such an entry upon rescanning or backing
-   up even though it had not been returned the first time through.  Similarly,
-   a concurrent delete might or might not be reflected in the results of a scan.
-   What is important is that insertions or deletions not cause the scan to
-   miss or multiply return entries that were not themselves being inserted or
-   deleted.
-  </para>
-
-  <para>
-   Instead of using <function>amgettuple</>, an index scan can be done with
-   <function>amgetbitmap</> to fetch all tuples in one call.  This can be
-   noticeably more efficient than <function>amgettuple</> because it allows
-   avoiding lock/unlock cycles within the access method.  In principle
-   <function>amgetbitmap</> should have the same effects as repeated
-   <function>amgettuple</> calls, but we impose several restrictions to
-   simplify matters.  First of all, <function>amgetbitmap</> returns all
-   tuples at once and marking or restoring scan positions isn't
-   supported. Secondly, the tuples are returned in a bitmap which doesn't
-   have any specific ordering, which is why <function>amgetbitmap</> doesn't
-   take a <literal>direction</> argument.  (Ordering operators will never be
-   supplied for such a scan, either.)  Finally, <function>amgetbitmap</>
-   does not guarantee any locking of the returned tuples, with implications
-   spelled out in <xref linkend="index-locking">.
-  </para>
-
-  <para>
-   Note that it is permitted for an access method to implement only
-   <function>amgetbitmap</> and not <function>amgettuple</>, or vice versa,
-   if its internal implementation is unsuited to one API or the other.
-  </para>
-
- </sect1>
-
- <sect1 id="index-locking">
-  <title>Index Locking Considerations</title>
-
-&common;
-  <para>
-   Index access methods must handle concurrent updates
-   of the index by multiple processes.
-   The core <productname>PostgreSQL</productname> system obtains
-   <literal>AccessShareLock</> on the index during an index scan, and
-   <literal>RowExclusiveLock</> when updating the index (including plain
-   <command>VACUUM</>).  Since these lock types do not conflict, the access
-   method is responsible for handling any fine-grained locking it might need.
-   An exclusive lock on the index as a whole will be taken only during index
-   creation, destruction, or <command>REINDEX</>.
-  </para>
-
-  <para>
-   Building an index type that supports concurrent updates usually requires
-   extensive and subtle analysis of the required behavior.  For the b-tree
-   and hash index types, you can read about the design decisions involved in
-   <filename>src/backend/access/nbtree/README</> and
-   <filename>src/backend/access/hash/README</>.
-  </para>
-
-  <para>
-   Aside from the index's own internal consistency requirements, concurrent
-   updates create issues about consistency between the parent table (the
-   <firstterm>heap</>) and the index.  Because
-   <productname>PostgreSQL</productname> separates accesses
-   and updates of the heap from those of the index, there are windows in
-   which the index might be inconsistent with the heap.  We handle this problem
-   with the following rules:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       A new heap entry is made before making its index entries.  (Therefore
-       a concurrent index scan is likely to fail to see the heap entry.
-       This is okay because the index reader would be uninterested in an
-       uncommitted row anyway.  But see <xref linkend="index-unique-checks">.)
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       When a heap entry is to be deleted (by <command>VACUUM</>), all its
-       index entries must be removed first.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       An index scan must maintain a pin
-       on the index page holding the item last returned by
-       <function>amgettuple</>, and <function>ambulkdelete</> cannot delete
-       entries from pages that are pinned by other backends.  The need
-       for this rule is explained below.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-   Without the third rule, it is possible for an index reader to
-   see an index entry just before it is removed by <command>VACUUM</>, and
-   then to arrive at the corresponding heap entry after that was removed by
-   <command>VACUUM</>.
-   This creates no serious problems if that item
-   number is still unused when the reader reaches it, since an empty
-   item slot will be ignored by <function>heap_fetch()</>.  But what if a
-   third backend has already re-used the item slot for something else?
-   When using an MVCC-compliant snapshot, there is no problem because
-   the new occupant of the slot is certain to be too new to pass the
-   snapshot test.  However, with a non-MVCC-compliant snapshot (such as
-   <literal>SnapshotNow</>), it would be possible to accept and return
-   a row that does not in fact match the scan keys.  We could defend
-   against this scenario by requiring the scan keys to be rechecked
-   against the heap row in all cases, but that is too expensive.  Instead,
-   we use a pin on an index page as a proxy to indicate that the reader
-   might still be <quote>in flight</> from the index entry to the matching
-   heap entry.  Making <function>ambulkdelete</> block on such a pin ensures
-   that <command>VACUUM</> cannot delete the heap entry before the reader
-   is done with it.  This solution costs little in run time, and adds blocking
-   overhead only in the rare cases where there actually is a conflict.
-  </para>
-
-  <para>
-   This solution requires that index scans be <quote>synchronous</>: we have
-   to fetch each heap tuple immediately after scanning the corresponding index
-   entry.  This is expensive for a number of reasons.  An
-   <quote>asynchronous</> scan in which we collect many TIDs from the index,
-   and only visit the heap tuples sometime later, requires much less index
-   locking overhead and can allow a more efficient heap access pattern.
-   Per the above analysis, we must use the synchronous approach for
-   non-MVCC-compliant snapshots, but an asynchronous scan is workable
-   for a query using an MVCC snapshot.
-  </para>
-
-  <para>
-   In an <function>amgetbitmap</> index scan, the access method does not
-   keep an index pin on any of the returned tuples.  Therefore
-   it is only safe to use such scans with MVCC-compliant snapshots.
-  </para>
-
-  <para>
-   When the <structfield>ampredlocks</> flag is not set, any scan using that
-   index access method within a serializable transaction will acquire a
-   non-blocking predicate lock on the full index.  This will generate a
-   read-write conflict with the insert of any tuple into that index by a
-   concurrent serializable transaction.  If certain patterns of read-write
-   conflicts are detected among a set of concurrent serializable
-   transactions, one of those transactions may be cancelled to protect data
-   integrity.  When the flag is set, it indicates that the index access
-   method implements finer-grained predicate locking, which will tend to
-   reduce the frequency of such transaction cancellations.
-  </para>
-
- </sect1>
-
- <sect1 id="index-unique-checks">
-  <title>Index Uniqueness Checks</title>
-
-&common;
-  <para>
-   <productname>PostgreSQL</productname> enforces SQL uniqueness constraints
-   using <firstterm>unique indexes</>, which are indexes that disallow
-   multiple entries with identical keys.  An access method that supports this
-   feature sets <structname>pg_am</>.<structfield>amcanunique</> true.
-   (At present, only b-tree supports it.)
-  </para>
-
-  <para>
-   Because of MVCC, it is always necessary to allow duplicate entries to
-   exist physically in an index: the entries might refer to successive
-   versions of a single logical row.  The behavior we actually want to
-   enforce is that no MVCC snapshot could include two rows with equal
-   index keys.  This breaks down into the following cases that must be
-   checked when inserting a new row into a unique index:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       If a conflicting valid row has been deleted by the current transaction,
-       it's okay.  (In particular, since an UPDATE always deletes the old row
-       version before inserting the new version, this will allow an UPDATE on
-       a row without changing the key.)
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       If a conflicting row has been inserted by an as-yet-uncommitted
-       transaction, the would-be inserter must wait to see if that transaction
-       commits.  If it rolls back then there is no conflict.  If it commits
-       without deleting the conflicting row again, there is a uniqueness
-       violation.  (In practice we just wait for the other transaction to
-       end and then redo the visibility check in toto.)
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Similarly, if a conflicting valid row has been deleted by an
-       as-yet-uncommitted transaction, the would-be inserter must wait
-       for that transaction to commit or abort, and then repeat the test.
-      </para>
-     </listitem>
-    </itemizedlist>
-  </para>
-
-  <para>
-   Furthermore, immediately before reporting a uniqueness violation
-   according to the above rules, the access method must recheck the
-   liveness of the row being inserted.  If it is committed dead then
-   no violation should be reported.  (This case cannot occur during the
-   ordinary scenario of inserting a row that's just been created by
-   the current transaction.  It can happen during
-   <command>CREATE UNIQUE INDEX CONCURRENTLY</>, however.)
-  </para>
-
-  <para>
-   We require the index access method to apply these tests itself, which
-   means that it must reach into the heap to check the commit status of
-   any row that is shown to have a duplicate key according to the index
-   contents.  This is without a doubt ugly and non-modular, but it saves
-   redundant work: if we did a separate probe then the index lookup for
-   a conflicting row would be essentially repeated while finding the place to
-   insert the new row's index entry.  What's more, there is no obvious way
-   to avoid race conditions unless the conflict check is an integral part
-   of insertion of the new index entry.
-  </para>
-
-  <para>
-   If the unique constraint is deferrable, there is additional complexity:
-   we need to be able to insert an index entry for a new row, but defer any
-   uniqueness-violation error until end of statement or even later.  To
-   avoid unnecessary repeat searches of the index, the index access method
-   should do a preliminary uniqueness check during the initial insertion.
-   If this shows that there is definitely no conflicting live tuple, we
-   are done.  Otherwise, we schedule a recheck to occur when it is time to
-   enforce the constraint.  If, at the time of the recheck, both the inserted
-   tuple and some other tuple with the same key are live, then the error
-   must be reported.  (Note that for this purpose, <quote>live</> actually
-   means <quote>any tuple in the index entry's HOT chain is live</>.)
-   To implement this, the <function>aminsert</> function is passed a
-   <literal>checkUnique</> parameter having one of the following values:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       <literal>UNIQUE_CHECK_NO</> indicates that no uniqueness checking
-       should be done (this is not a unique index).
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <literal>UNIQUE_CHECK_YES</> indicates that this is a non-deferrable
-       unique index, and the uniqueness check must be done immediately, as
-       described above.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <literal>UNIQUE_CHECK_PARTIAL</> indicates that the unique
-       constraint is deferrable. <productname>PostgreSQL</productname>
-       will use this mode to insert each row's index entry.  The access
-       method must allow duplicate entries into the index, and report any
-       potential duplicates by returning FALSE from <function>aminsert</>.
-       For each row for which FALSE is returned, a deferred recheck will
-       be scheduled.
-      </para>
-
-      <para>
-       The access method must identify any rows which might violate the
-       unique constraint, but it is not an error for it to report false
-       positives. This allows the check to be done without waiting for other
-       transactions to finish; conflicts reported here are not treated as
-       errors and will be rechecked later, by which time they may no longer
-       be conflicts.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <literal>UNIQUE_CHECK_EXISTING</> indicates that this is a deferred
-       recheck of a row that was reported as a potential uniqueness violation.
-       Although this is implemented by calling <function>aminsert</>, the
-       access method must <emphasis>not</> insert a new index entry in this
-       case.  The index entry is already present.  Rather, the access method
-       must check to see if there is another live index entry.  If so, and
-       if the target row is also still live, report error.
-      </para>
-
-      <para>
-       It is recommended that in a <literal>UNIQUE_CHECK_EXISTING</> call,
-       the access method further verify that the target row actually does
-       have an existing entry in the index, and report error if not.  This
-       is a good idea because the index tuple values passed to
-       <function>aminsert</> will have been recomputed.  If the index
-       definition involves functions that are not really immutable, we
-       might be checking the wrong area of the index.  Checking that the
-       target row is found in the recheck verifies that we are scanning
-       for the same tuple values as were used in the original insertion.
-      </para>
-     </listitem>
-    </itemizedlist>
-  </para>
-
- </sect1>
-
- <sect1 id="index-cost-estimation">
-  <title>Index Cost Estimation Functions</title>
-
-&common;
-  <para>
-   The <function>amcostestimate</> function is given information describing
-   a possible index scan, including lists of WHERE and ORDER BY clauses that
-   have been determined to be usable with the index.  It must return estimates
-   of the cost of accessing the index and the selectivity of the WHERE
-   clauses (that is, the fraction of parent-table rows that will be
-   retrieved during the index scan).  For simple cases, nearly all the
-   work of the cost estimator can be done by calling standard routines
-   in the optimizer; the point of having an <function>amcostestimate</> function is
-   to allow index access methods to provide index-type-specific knowledge,
-   in case it is possible to improve on the standard estimates.
-  </para>
-
-  <para>
-   Each <function>amcostestimate</> function must have the signature:
-
-<programlisting>
-void
-amcostestimate (PlannerInfo *root,
-                IndexOptInfo *index,
-                List *indexQuals,
-                List *indexOrderBys,
-                RelOptInfo *outer_rel,
-                Cost *indexStartupCost,
-                Cost *indexTotalCost,
-                Selectivity *indexSelectivity,
-                double *indexCorrelation);
-</programlisting>
-
-   The first five parameters are inputs:
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>root</></term>
-     <listitem>
-      <para>
-       The planner's information about the query being processed.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>index</></term>
-     <listitem>
-      <para>
-       The index being considered.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>indexQuals</></term>
-     <listitem>
-      <para>
-       List of index qual clauses (implicitly ANDed);
-       a <symbol>NIL</> list indicates no qualifiers are available.
-       Note that the list contains expression trees with RestrictInfo nodes
-       at the top, not ScanKeys.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>indexOrderBys</></term>
-     <listitem>
-      <para>
-       List of indexable ORDER BY operators, or <symbol>NIL</> if none.
-       Note that the list contains expression trees, not ScanKeys.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>outer_rel</></term>
-     <listitem>
-      <para>
-       If the index is being considered for use in a join inner indexscan,
-       the planner's information about the outer side of the join.  Otherwise
-       <symbol>NULL</>.  When non-<symbol>NULL</>, some of the qual clauses will be join clauses
-       with this rel rather than being simple restriction clauses.  Also,
-       the cost estimator should expect that the index scan will be repeated
-       for each row of the outer rel.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   The last four parameters are pass-by-reference outputs:
-
-   <variablelist>
-    <varlistentry>
-     <term><parameter>*indexStartupCost</></term>
-     <listitem>
-      <para>
-       Set to cost of index start-up processing
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>*indexTotalCost</></term>
-     <listitem>
-      <para>
-       Set to total cost of index processing
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>*indexSelectivity</></term>
-     <listitem>
-      <para>
-       Set to index selectivity
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><parameter>*indexCorrelation</></term>
-     <listitem>
-      <para>
-       Set to correlation coefficient between index scan order and
-       underlying table's order
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   Note that cost estimate functions must be written in C, not in SQL or
-   any available procedural language, because they must access internal
-   data structures of the planner/optimizer.
-  </para>
-
-  <para>
-   The index access costs should be computed using the parameters used by
-   <filename>src/backend/optimizer/path/costsize.c</filename>: a sequential
-   disk block fetch has cost <varname>seq_page_cost</>, a nonsequential fetch
-   has cost <varname>random_page_cost</>, and the cost of processing one index
-   row should usually be taken as <varname>cpu_index_tuple_cost</>.  In
-   addition, an appropriate multiple of <varname>cpu_operator_cost</> should
-   be charged for any comparison operators invoked during index processing
-   (especially evaluation of the <literal>indexQuals</> themselves).
-  </para>
-
-  <para>
-   The access costs should include all disk and CPU costs associated with
-   scanning the index itself, but <emphasis>not</> the costs of retrieving or
-   processing the parent-table rows that are identified by the index.
-  </para>
-
-  <para>
-   The <quote>start-up cost</quote> is the part of the total scan cost that
-   must be expended before we can begin to fetch the first row.  For most
-   indexes this can be taken as zero, but an index type with a high start-up
-   cost might want to set it nonzero.
-  </para>
-
-  <para>
-   The <parameter>indexSelectivity</> should be set to the estimated fraction of the parent
-   table rows that will be retrieved during the index scan.  In the case
-   of a lossy query, this will typically be higher than the fraction of
-   rows that actually pass the given qual conditions.
-  </para>
-
-  <para>
-   The <parameter>indexCorrelation</> should be set to the correlation (ranging between
-   -1.0 and 1.0) between the index order and the table order.  This is used
-   to adjust the estimate for the cost of fetching rows from the parent
-   table.
-  </para>
-
-  <para>
-   In the join case, the returned numbers should be averages expected for
-   any one scan of the index.
-  </para>
-
-  <procedure>
-   <title>Cost Estimation</title>
-   <para>
-    A typical cost estimator will proceed as follows:
-   </para>
-
-   <step>
-    <para>
-     Estimate and return the fraction of parent-table rows that will be visited
-     based on the given qual conditions.  In the absence of any index-type-specific
-     knowledge, use the standard optimizer function <function>clauselist_selectivity()</function>:
-
-<programlisting>
-*indexSelectivity = clauselist_selectivity(root, indexQuals,
-                                           index-&gt;rel-&gt;relid,
-                                           JOIN_INNER, NULL);
-</programlisting>
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Estimate the number of index rows that will be visited during the
-     scan.  For many index types this is the same as <parameter>indexSelectivity</> times
-     the number of rows in the index, but it might be more.  (Note that the
-     index's size in pages and rows is available from the <structname>IndexOptInfo</> struct.)
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Estimate the number of index pages that will be retrieved during the scan.
-     This might be just <parameter>indexSelectivity</> times the index's size in pages.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Compute the index access cost.  A generic estimator might do this:
-
-<programlisting>
-/*
- * Our generic assumption is that the index pages will be read
- * sequentially, so they cost seq_page_cost each, not random_page_cost.
- * Also, we charge for evaluation of the indexquals at each index row.
- * All the costs are assumed to be paid incrementally during the scan.
- */
-cost_qual_eval(&amp;index_qual_cost, indexQuals, root);
-*indexStartupCost = index_qual_cost.startup;
-*indexTotalCost = seq_page_cost * numIndexPages +
-    (cpu_index_tuple_cost + index_qual_cost.per_tuple) * numIndexTuples;
-</programlisting>
-
-     However, the above does not account for amortization of index reads
-     across repeated index scans in the join case.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Estimate the index correlation.  For a simple ordered index on a single
-     field, this can be retrieved from pg_statistic.  If the correlation
-     is not known, the conservative estimate is zero (no correlation).
-    </para>
-   </step>
-  </procedure>
-
-  <para>
-   Examples of cost estimator functions can be found in
-   <filename>src/backend/utils/adt/selfuncs.c</filename>.
-  </para>
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/indices.sgmlin b/doc-xc/src/sgml/indices.sgmlin
deleted file mode 100644
index a1789e0ce2..0000000000
--- a/doc-xc/src/sgml/indices.sgmlin
+++ /dev/null
@@ -1,1323 +0,0 @@
-<!-- doc/src/sgml/indices.sgml -->
-
-<chapter id="indexes">
- <title>Indexes</title>
-
- <indexterm zone="indexes">
-  <primary>index</primary>
- </indexterm>
-&common;
- <para>
-  Indexes are a common way to enhance database performance.  An index
-  allows the database server to find and retrieve specific rows much
-  faster than it could do without an index.  But indexes also add
-  overhead to the database system as a whole, so they should be used
-  sensibly.
- </para>
-
-<!## XC>
-&xconly;
-   <para>
-    Each index is maintained locally in Coordinator and Datanode
-    in <productname>Postgres-XC</>.
-    Cross validation of index entries among Coordinators and Datanodes is
-    not performed in the current implementation.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Each index is maintained locally in Coordinator and Datanode
-    in <productname>Postgres-XL</>.
-    Cross validation of index entries among Coordinators and Datanodes is
-    not performed in the current implementation.
-   </para>
-<!## end>
-
-
- <sect1 id="indexes-intro">
-  <title>Introduction</title>
-&common;
-  <para>
-   Suppose we have a table similar to this:
-<programlisting>
-CREATE TABLE test1 (
-    id integer,
-    content varchar
-);
-</programlisting>
-   and the application issues many queries of the form:
-<programlisting>
-SELECT content FROM test1 WHERE id = <replaceable>constant</replaceable>;
-</programlisting>
-   With no advance preparation, the system would have to scan the entire
-   <structname>test1</structname> table, row by row, to find all
-   matching entries.  If there are many rows in
-   <structname>test1</structname> and only a few rows (perhaps zero
-   or one) that would be returned by such a query, this is clearly an
-   inefficient method.  But if the system has been instructed to maintain an
-   index on the <structfield>id</structfield> column, it can use a more
-   efficient method for locating matching rows.  For instance, it
-   might only have to walk a few levels deep into a search tree.
-  </para>
-
-  <para>
-   A similar approach is used in most non-fiction books:  terms and
-   concepts that are frequently looked up by readers are collected in
-   an alphabetic index at the end of the book.  The interested reader
-   can scan the index relatively quickly and flip to the appropriate
-   page(s), rather than having to read the entire book to find the
-   material of interest.  Just as it is the task of the author to
-   anticipate the items that readers are likely to look up,
-   it is the task of the database programmer to foresee which indexes
-   will be useful.
-  </para>
-
-  <para>
-   The following command can be used to create an index on the
-   <structfield>id</structfield> column, as discussed:
-<programlisting>
-CREATE INDEX test1_id_index ON test1 (id);
-</programlisting>
-   The name <structname>test1_id_index</structname> can be chosen
-   freely, but you should pick something that enables you to remember
-   later what the index was for.
-  </para>
-
-  <para>
-   To remove an index, use the <command>DROP INDEX</command> command.
-   Indexes can be added to and removed from tables at any time.
-  </para>
-
-  <para>
-   Once an index is created, no further intervention is required: the
-   system will update the index when the table is modified, and it will
-   use the index in queries when it thinks doing so would be more efficient
-   than a sequential table scan.  But you might have to run the
-   <command>ANALYZE</command> command regularly to update
-   statistics to allow the query planner to make educated decisions.
-   See <xref linkend="performance-tips"> for information about
-   how to find out whether an index is used and when and why the
-   planner might choose <emphasis>not</emphasis> to use an index.
-  </para>
-
-  <para>
-   Indexes can also benefit <command>UPDATE</command> and
-   <command>DELETE</command> commands with search conditions.
-   Indexes can moreover be used in join searches.  Thus,
-   an index defined on a column that is part of a join condition can
-   also significantly speed up queries with joins.
-  </para>
-
-  <para>
-   Creating an index on a large table can take a long time.  By default,
-<!## PG>
-   <productname>PostgreSQL</productname> allows reads (<command>SELECT</command> statements) to occur
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> allows reads (<command>SELECT</command> statements) to occur
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> allows reads (<command>SELECT</command> statements) to occur
-<!## end>
-   on the table in parallel with index creation, but writes (<command>INSERT</command>,
-   <command>UPDATE</command>, <command>DELETE</command>) are blocked until the index build is finished.
-   In production environments this is often unacceptable.
-   It is possible to allow writes to occur in parallel with index
-   creation, but there are several caveats to be aware of &mdash;
-   for more information see <xref linkend="SQL-CREATEINDEX-CONCURRENTLY"
-   endterm="SQL-CREATEINDEX-CONCURRENTLY-title">.
-  </para>
-
-  <para>
-   After an index is created, the system has to keep it synchronized with the
-   table.  This adds overhead to data manipulation operations.
-   Therefore indexes that are seldom or never used in queries
-   should be removed.
-  </para>
- </sect1>
-
-
- <sect1 id="indexes-types">
-  <title>Index Types</title>
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> provides several index types:
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> provides several index types:
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> provides several index types:
-<!## end>
-   B-tree, Hash, GiST and GIN.  Each index type uses a different
-   algorithm that is best suited to different types of queries.
-   By default, the <command>CREATE INDEX</command> command creates
-   B-tree indexes, which fit the most common situations.
-  </para>
-
-  <para>
-   <indexterm>
-    <primary>index</primary>
-    <secondary>B-tree</secondary>
-   </indexterm>
-   <indexterm>
-    <primary>B-tree</primary>
-    <see>index</see>
-   </indexterm>
-   B-trees can handle equality and range queries on data that can be sorted
-   into some ordering.
-<!## PG>
-   In particular, the <productname>PostgreSQL</productname> query planner
-<!## end>
-<!## XC>
-   In particular, the <productname>Postgres-XC</productname> query planner
-<!## end>
-<!## XL>
-   In particular, the <productname>Postgres-XL</productname> query planner
-<!## end>
-   will consider using a B-tree index whenever an indexed column is
-   involved in a comparison using one of these operators:
-
-   <simplelist>
-    <member><literal>&lt;</literal></member>
-    <member><literal>&lt;=</literal></member>
-    <member><literal>=</literal></member>
-    <member><literal>&gt;=</literal></member>
-    <member><literal>&gt;</literal></member>
-   </simplelist>
-
-   Constructs equivalent to combinations of these operators, such as
-   <literal>BETWEEN</> and <literal>IN</>, can also be implemented with
-   a B-tree index search.  Also, an <literal>IS NULL</> or <literal>IS NOT
-   NULL</> condition on an index column can be used with a B-tree index.
-  </para>
-
-  <para>
-   The optimizer can also use a B-tree index for queries involving the
-   pattern matching operators <literal>LIKE</> and <literal>~</literal>
-   <emphasis>if</emphasis> the pattern is a constant and is anchored to
-   the beginning of the string &mdash; for example, <literal>col LIKE
-   'foo%'</literal> or <literal>col ~ '^foo'</literal>, but not
-   <literal>col LIKE '%bar'</literal>. However, if your database does not
-   use the C locale you will need to create the index with a special
-   operator class to support indexing of pattern-matching queries; see
-   <xref linkend="indexes-opclass"> below. It is also possible to use
-   B-tree indexes for <literal>ILIKE</literal> and
-   <literal>~*</literal>, but only if the pattern starts with
-   non-alphabetic characters, i.e., characters that are not affected by
-   upper/lower case conversion.
-  </para>
-
-  <para>
-   B-tree indexes can also be used to retrieve data in sorted order.
-   This is not always faster than a simple scan and sort, but it is
-   often helpful.
-  </para>
-
-  <para>
-   <indexterm>
-    <primary>index</primary>
-    <secondary>hash</secondary>
-   </indexterm>
-   <indexterm>
-    <primary>hash</primary>
-    <see>index</see>
-   </indexterm>
-   Hash indexes can only handle simple equality comparisons.
-   The query planner will consider using a hash index whenever an
-   indexed column is involved in a comparison using the
-   <literal>=</literal> operator.
-   The following command is used to create a hash index:
-<synopsis>
-CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable> USING hash (<replaceable>column</replaceable>);
-</synopsis>
-  </para>
-
-  <caution>
-   <para>
-    Hash index operations are not presently WAL-logged,
-    so hash indexes might need to be rebuilt with <command>REINDEX</>
-    after a database crash. They are also not replicated over streaming or
-    file-based replication.
-    For these reasons, hash index use is presently discouraged.
-   </para>
-  </caution>
-
-  <para>
-   <indexterm>
-    <primary>index</primary>
-    <secondary>GiST</secondary>
-   </indexterm>
-   <indexterm>
-    <primary>GiST</primary>
-    <see>index</see>
-   </indexterm>
-   GiST indexes are not a single kind of index, but rather an infrastructure
-   within which many different indexing strategies can be implemented.
-   Accordingly, the particular operators with which a GiST index can be
-   used vary depending on the indexing strategy (the <firstterm>operator
-   class</>).  As an example, the standard distribution of
-<!## PG>
-   <productname>PostgreSQL</productname> includes GiST operator classes
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> includes GiST operator classes
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> includes GiST operator classes
-<!## end>
-   for several two-dimensional geometric data types, which support indexed
-   queries using these operators:
-
-   <simplelist>
-    <member><literal>&lt;&lt;</literal></member>
-    <member><literal>&amp;&lt;</literal></member>
-    <member><literal>&amp;&gt;</literal></member>
-    <member><literal>&gt;&gt;</literal></member>
-    <member><literal>&lt;&lt;|</literal></member>
-    <member><literal>&amp;&lt;|</literal></member>
-    <member><literal>|&amp;&gt;</literal></member>
-    <member><literal>|&gt;&gt;</literal></member>
-    <member><literal>@&gt;</literal></member>
-    <member><literal>&lt;@</literal></member>
-    <member><literal>~=</literal></member>
-    <member><literal>&amp;&amp;</literal></member>
-   </simplelist>
-
-   (See <xref linkend="functions-geometry"> for the meaning of
-   these operators.)
-   Many other GiST operator
-   classes are available in the <literal>contrib</> collection or as separate
-   projects.  For more information see <xref linkend="GiST">.
-  </para>
-
-  <para>
-   GiST indexes are also capable of optimizing <quote>nearest-neighbor</>
-   searches, such as
-<programlisting><![CDATA[
-SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
-]]>
-</programlisting>
-   which finds the ten places closest to a given target point.  The ability
-   to do this is again dependent on the particular operator class being used.
-  </para>
-
-  <para>
-   <indexterm>
-    <primary>index</primary>
-    <secondary>GIN</secondary>
-   </indexterm>
-   <indexterm>
-    <primary>GIN</primary>
-    <see>index</see>
-   </indexterm>
-   GIN indexes are inverted indexes which can handle values that contain more
-   than one key, arrays for example. Like GiST, GIN can support
-   many different user-defined indexing strategies and the particular
-   operators with which a GIN index can be used vary depending on the
-   indexing strategy.
-   As an example, the standard distribution of
-<!## PG>
-   <productname>PostgreSQL</productname> includes GIN operator classes
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> includes GIN operator classes
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> includes GIN operator classes
-<!## end>
-   for one-dimensional arrays, which support indexed
-   queries using these operators:
-
-   <simplelist>
-    <member><literal>&lt;@</literal></member>
-    <member><literal>@&gt;</literal></member>
-    <member><literal>=</literal></member>
-    <member><literal>&amp;&amp;</literal></member>
-   </simplelist>
-
-   (See <xref linkend="functions-array"> for the meaning of
-   these operators.)
-   Many other GIN operator
-   classes are available in the <literal>contrib</> collection or as separate
-   projects.  For more information see <xref linkend="GIN">.
-  </para>
- </sect1>
-
-
- <sect1 id="indexes-multicolumn">
-  <title>Multicolumn Indexes</title>
-
-  <indexterm zone="indexes-multicolumn">
-   <primary>index</primary>
-   <secondary>multicolumn</secondary>
-  </indexterm>
-&common;
-  <para>
-   An index can be defined on more than one column of a table.  For example, if
-   you have a table of this form:
-<programlisting>
-CREATE TABLE test2 (
-  major int,
-  minor int,
-  name varchar
-);
-</programlisting>
-   (say, you keep your <filename class="directory">/dev</filename>
-   directory in a database...) and you frequently issue queries like:
-<programlisting>
-SELECT name FROM test2 WHERE major = <replaceable>constant</replaceable> AND minor = <replaceable>constant</replaceable>;
-</programlisting>
-   then it might be appropriate to define an index on the columns
-   <structfield>major</structfield> and
-   <structfield>minor</structfield> together, e.g.:
-<programlisting>
-CREATE INDEX test2_mm_idx ON test2 (major, minor);
-</programlisting>
-  </para>
-
-  <para>
-   Currently, only the B-tree, GiST and GIN index types support multicolumn
-   indexes.  Up to 32 columns can be specified.  (This limit can be
-<!## PG>
-   altered when building <productname>PostgreSQL</productname>; see the
-<!## end>
-<!## XC>
-   altered when building <productname>Postgres-XC</productname>; see the
-<!## end>
-<!## XL>
-   altered when building <productname>Postgres-XL</productname>; see the
-<!## end>
-   file <filename>pg_config_manual.h</filename>.)
-  </para>
-
-  <para>
-   A multicolumn B-tree index can be used with query conditions that
-   involve any subset of the index's columns, but the index is most
-   efficient when there are constraints on the leading (leftmost) columns.
-   The exact rule is that equality constraints on leading columns, plus
-   any inequality constraints on the first column that does not have an
-   equality constraint, will be used to limit the portion of the index
-   that is scanned.  Constraints on columns to the right of these columns
-   are checked in the index, so they save visits to the table proper, but
-   they do not reduce the portion of the index that has to be scanned.
-   For example, given an index on <literal>(a, b, c)</literal> and a
-   query condition <literal>WHERE a = 5 AND b &gt;= 42 AND c &lt; 77</>,
-   the index would have to be scanned from the first entry with
-   <literal>a</> = 5 and <literal>b</> = 42 up through the last entry with
-   <literal>a</> = 5.  Index entries with <literal>c</> &gt;= 77 would be
-   skipped, but they'd still have to be scanned through.
-   This index could in principle be used for queries that have constraints
-   on <literal>b</> and/or <literal>c</> with no constraint on <literal>a</>
-   &mdash; but the entire index would have to be scanned, so in most cases
-   the planner would prefer a sequential table scan over using the index.
-  </para>
-
-  <para>
-   A multicolumn GiST index can be used with query conditions that
-   involve any subset of the index's columns. Conditions on additional
-   columns restrict the entries returned by the index, but the condition on
-   the first column is the most important one for determining how much of
-   the index needs to be scanned.  A GiST index will be relatively
-   ineffective if its first column has only a few distinct values, even if
-   there are many distinct values in additional columns.
-  </para>
-
-  <para>
-   A multicolumn GIN index can be used with query conditions that
-   involve any subset of the index's columns. Unlike B-tree or GiST,
-   index search effectiveness is the same regardless of which index column(s)
-   the query conditions use.
-  </para>
-
-  <para>
-   Of course, each column must be used with operators appropriate to the index
-   type; clauses that involve other operators will not be considered.
-  </para>
-
-  <para>
-   Multicolumn indexes should be used sparingly.  In most situations,
-   an index on a single column is sufficient and saves space and time.
-   Indexes with more than three columns are unlikely to be helpful
-   unless the usage of the table is extremely stylized.  See also
-   <xref linkend="indexes-bitmap-scans"> for some discussion of the
-   merits of different index configurations.
-  </para>
- </sect1>
-
-
- <sect1 id="indexes-ordering">
-  <title>Indexes and <literal>ORDER BY</></title>
-
-  <indexterm zone="indexes-ordering">
-   <primary>index</primary>
-   <secondary>and <literal>ORDER BY</></secondary>
-  </indexterm>
-&common;
-  <para>
-   In addition to simply finding the rows to be returned by a query,
-   an index may be able to deliver them in a specific sorted order.
-   This allows a query's <literal>ORDER BY</> specification to be honored
-   without a separate sorting step.  Of the index types currently
-<!## PG>
-   supported by <productname>PostgreSQL</productname>, only B-tree
-<!## end>
-<!## XC>
-   supported by <productname>Postgres-XC</productname>, only B-tree
-<!## end>
-<!## XL>
-   supported by <productname>Postgres-XL</productname>, only B-tree
-<!## end>
-   can produce sorted output &mdash; the other index types return
-   matching rows in an unspecified, implementation-dependent order.
-  </para>
-
-  <para>
-   The planner will consider satisfying an <literal>ORDER BY</> specification
-   either by scanning an available index that matches the specification,
-   or by scanning the table in physical order and doing an explicit
-   sort.  For a query that requires scanning a large fraction of the
-   table, an explicit sort is likely to be faster than using an index
-   because it requires
-   less disk I/O due to following a sequential access pattern.  Indexes are
-   more useful when only a few rows need be fetched.  An important
-   special case is <literal>ORDER BY</> in combination with
-   <literal>LIMIT</> <replaceable>n</>: an explicit sort will have to process
-   all the data to identify the first <replaceable>n</> rows, but if there is
-   an index matching the <literal>ORDER BY</>, the first <replaceable>n</>
-   rows can be retrieved directly, without scanning the remainder at all.
-  </para>
-
-  <para>
-   By default, B-tree indexes store their entries in ascending order
-   with nulls last.  This means that a forward scan of an index on
-   column <literal>x</> produces output satisfying <literal>ORDER BY x</>
-   (or more verbosely, <literal>ORDER BY x ASC NULLS LAST</>).  The
-   index can also be scanned backward, producing output satisfying
-   <literal>ORDER BY x DESC</>
-   (or more verbosely, <literal>ORDER BY x DESC NULLS FIRST</>, since
-   <literal>NULLS FIRST</> is the default for <literal>ORDER BY DESC</>).
-  </para>
-
-  <para>
-   You can adjust the ordering of a B-tree index by including the
-   options <literal>ASC</>, <literal>DESC</>, <literal>NULLS FIRST</>,
-   and/or <literal>NULLS LAST</> when creating the index; for example:
-<programlisting>
-CREATE INDEX test2_info_nulls_low ON test2 (info NULLS FIRST);
-CREATE INDEX test3_desc_index ON test3 (id DESC NULLS LAST);
-</programlisting>
-   An index stored in ascending order with nulls first can satisfy
-   either <literal>ORDER BY x ASC NULLS FIRST</> or
-   <literal>ORDER BY x DESC NULLS LAST</> depending on which direction
-   it is scanned in.
-  </para>
-
-  <para>
-   You might wonder why bother providing all four options, when two
-   options together with the possibility of backward scan would cover
-   all the variants of <literal>ORDER BY</>.  In single-column indexes
-   the options are indeed redundant, but in multicolumn indexes they can be
-   useful.  Consider a two-column index on <literal>(x, y)</>: this can
-   satisfy <literal>ORDER BY x, y</> if we scan forward, or
-   <literal>ORDER BY x DESC, y DESC</> if we scan backward.
-   But it might be that the application frequently needs to use
-   <literal>ORDER BY x ASC, y DESC</>.  There is no way to get that
-   ordering from a plain index, but it is possible if the index is defined
-   as <literal>(x ASC, y DESC)</> or <literal>(x DESC, y ASC)</>.
-  </para>
-
-  <para>
-   Obviously, indexes with non-default sort orderings are a fairly
-   specialized feature, but sometimes they can produce tremendous
-   speedups for certain queries.  Whether it's worth maintaining such an
-   index depends on how often you use queries that require a special
-   sort ordering.
-  </para>
- </sect1>
-
-
- <sect1 id="indexes-bitmap-scans">
-  <title>Combining Multiple Indexes</title>
-
-  <indexterm zone="indexes-bitmap-scans">
-   <primary>index</primary>
-   <secondary>combining multiple indexes</secondary>
-  </indexterm>
-
-  <indexterm zone="indexes-bitmap-scans">
-   <primary>bitmap scan</primary>
-  </indexterm>
-&common;
-  <para>
-   A single index scan can only use query clauses that use the index's
-   columns with operators of its operator class and are joined with
-   <literal>AND</>.  For example, given an index on <literal>(a, b)</literal>
-   a query condition like <literal>WHERE a = 5 AND b = 6</> could
-   use the index, but a query like <literal>WHERE a = 5 OR b = 6</> could not
-   directly use the index.
-  </para>
-
-  <para>
-   Fortunately,
-<!## PG>
-   <productname>PostgreSQL</> has the ability to combine multiple indexes
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> has the ability to combine multiple indexes
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> has the ability to combine multiple indexes
-<!## end>
-   (including multiple uses of the same index) to handle cases that cannot
-   be implemented by single index scans.  The system can form <literal>AND</>
-   and <literal>OR</> conditions across several index scans.  For example,
-   a query like <literal>WHERE x = 42 OR x = 47 OR x = 53 OR x = 99</>
-   could be broken down into four separate scans of an index on <literal>x</>,
-   each scan using one of the query clauses.  The results of these scans are
-   then ORed together to produce the result.  Another example is that if we
-   have separate indexes on <literal>x</> and <literal>y</>, one possible
-   implementation of a query like <literal>WHERE x = 5 AND y = 6</> is to
-   use each index with the appropriate query clause and then AND together
-   the index results to identify the result rows.
-  </para>
-
-  <para>
-   To combine multiple indexes, the system scans each needed index and
-   prepares a <firstterm>bitmap</> in memory giving the locations of
-   table rows that are reported as matching that index's conditions.
-   The bitmaps are then ANDed and ORed together as needed by the query.
-   Finally, the actual table rows are visited and returned.  The table rows
-   are visited in physical order, because that is how the bitmap is laid
-   out; this means that any ordering of the original indexes is lost, and
-   so a separate sort step will be needed if the query has an <literal>ORDER
-   BY</> clause.  For this reason, and because each additional index scan
-   adds extra time, the planner will sometimes choose to use a simple index
-   scan even though additional indexes are available that could have been
-   used as well.
-  </para>
-
-  <para>
-   In all but the simplest applications, there are various combinations of
-   indexes that might be useful, and the database developer must make
-   trade-offs to decide which indexes to provide.  Sometimes multicolumn
-   indexes are best, but sometimes it's better to create separate indexes
-   and rely on the index-combination feature.  For example, if your
-   workload includes a mix of queries that sometimes involve only column
-   <literal>x</>, sometimes only column <literal>y</>, and sometimes both
-   columns, you might choose to create two separate indexes on
-   <literal>x</> and <literal>y</>, relying on index combination to
-   process the queries that use both columns.  You could also create a
-   multicolumn index on <literal>(x, y)</>.  This index would typically be
-   more efficient than index combination for queries involving both
-   columns, but as discussed in <xref linkend="indexes-multicolumn">, it
-   would be almost useless for queries involving only <literal>y</>, so it
-   should not be the only index.  A combination of the multicolumn index
-   and a separate index on <literal>y</> would serve reasonably well.  For
-   queries involving only <literal>x</>, the multicolumn index could be
-   used, though it would be larger and hence slower than an index on
-   <literal>x</> alone.  The last alternative is to create all three
-   indexes, but this is probably only reasonable if the table is searched
-   much more often than it is updated and all three types of query are
-   common.  If one of the types of query is much less common than the
-   others, you'd probably settle for creating just the two indexes that
-   best match the common types.
-  </para>
-
- </sect1>
-
-
- <sect1 id="indexes-unique">
-  <title>Unique Indexes</title>
-
-  <indexterm zone="indexes-unique">
-   <primary>index</primary>
-   <secondary>unique</secondary>
-  </indexterm>
-
-<!## XC>
-&xconly;
-  <para>
-   In <productname>Postgres-XC</>, for distributed table, unique index
-   is allowed only for the distribution column.  For replicated
-   tables, there's no such restriction.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   In <productname>Postgres-XL</>, unique indexes on distributed tables
-   must contain the distribution column.  For replicated
-   tables, there's no such restriction.
-  </para>
-<!## end>
-&common;
-  <para>
-   Indexes can also be used to enforce uniqueness of a column's value,
-   or the uniqueness of the combined values of more than one column.
-<synopsis>
-CREATE UNIQUE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable> (<replaceable>column</replaceable> <optional>, ...</optional>);
-</synopsis>
-   Currently, only B-tree indexes can be declared unique.
-  </para>
-
-  <para>
-   When an index is declared unique, multiple table rows with equal
-   indexed values are not allowed.  Null values are not considered
-   equal.  A multicolumn unique index will only reject cases where all
-   indexed columns are equal in multiple rows.
-  </para>
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> automatically creates a unique
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> automatically creates a unique
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> automatically creates a unique
-<!## end>
-   index when a unique constraint or primary key is defined for a table.
-   The index covers the columns that make up the primary key or unique
-   constraint (a multicolumn index, if appropriate), and is the mechanism
-   that enforces the constraint.
-  </para>
-
-  <note>
-   <para>
-    The preferred way to add a unique constraint to a table is
-    <literal>ALTER TABLE ... ADD CONSTRAINT</literal>.  The use of
-    indexes to enforce unique constraints could be considered an
-    implementation detail that should not be accessed directly.
-    One should, however, be aware that there's no need to manually
-    create indexes on unique columns; doing so would just duplicate
-    the automatically-created index.
-   </para>
-  </note>
-&xc-constraint;
- </sect1>
-
-
- <sect1 id="indexes-expressional">
-  <title>Indexes on Expressions</title>
-
-  <indexterm zone="indexes-expressional">
-   <primary>index</primary>
-   <secondary sortas="expressions">on expressions</secondary>
-  </indexterm>
-&common;
-  <para>
-   An index column need not be just a column of the underlying table,
-   but can be a function or scalar expression computed from one or
-   more columns of the table.  This feature is useful to obtain fast
-   access to tables based on the results of computations.
-  </para>
-
-  <para>
-   For example, a common way to do case-insensitive comparisons is to
-   use the <function>lower</function> function:
-<programlisting>
-SELECT * FROM test1 WHERE lower(col1) = 'value';
-</programlisting>
-   This query can use an index if one has been
-   defined on the result of the <literal>lower(col1)</literal>
-   function:
-<programlisting>
-CREATE INDEX test1_lower_col1_idx ON test1 (lower(col1));
-</programlisting>
-  </para>
-
-  <para>
-   If we were to declare this index <literal>UNIQUE</>, it would prevent
-   creation of rows whose <literal>col1</> values differ only in case,
-   as well as rows whose <literal>col1</> values are actually identical.
-   Thus, indexes on expressions can be used to enforce constraints that
-   are not definable as simple unique constraints.
-  </para>
-  <para>
-   As another example, if one often does queries like:
-<programlisting>
-SELECT * FROM people WHERE (first_name || ' ' || last_name) = 'John Smith';
-</programlisting>
-   then it might be worth creating an index like this:
-<programlisting>
-CREATE INDEX people_names ON people ((first_name || ' ' || last_name));
-</programlisting>
-  </para>
-
-  <para>
-   The syntax of the <command>CREATE INDEX</> command normally requires
-   writing parentheses around index expressions, as shown in the second
-   example.  The parentheses can be omitted when the expression is just
-   a function call, as in the first example.
-  </para>
-
-  <para>
-   Index expressions are relatively expensive to maintain, because the
-   derived expression(s) must be computed for each row upon insertion
-   and whenever it is updated.  However, the index expressions are
-   <emphasis>not</> recomputed during an indexed search, since they are
-   already stored in the index.  In both examples above, the system
-   sees the query as just <literal>WHERE indexedcolumn = 'constant'</>
-   and so the speed of the search is equivalent to any other simple index
-   query.  Thus, indexes on expressions are useful when retrieval speed
-   is more important than insertion and update speed.
-  </para>
-&xc-constraint;
- </sect1>
-
-
- <sect1 id="indexes-partial">
-  <title>Partial Indexes</title>
-
-  <indexterm zone="indexes-partial">
-   <primary>index</primary>
-   <secondary>partial</secondary>
-  </indexterm>
-&common;
-  <para>
-   A <firstterm>partial index</firstterm> is an index built over a
-   subset of a table; the subset is defined by a conditional
-   expression (called the <firstterm>predicate</firstterm> of the
-   partial index).  The index contains entries only for those table
-   rows that satisfy the predicate.  Partial indexes are a specialized
-   feature, but there are several situations in which they are useful.
-  </para>
-
-  <para>
-   One major reason for using a partial index is to avoid indexing common
-   values.  Since a query searching for a common value (one that
-   accounts for more than a few percent of all the table rows) will not
-   use the index anyway, there is no point in keeping those rows in the
-   index at all.  This reduces the size of the index, which will speed
-   up those queries that do use the index.  It will also speed up many table
-   update operations because the index does not need to be
-   updated in all cases.  <xref linkend="indexes-partial-ex1"> shows a
-   possible application of this idea.
-  </para>
-
-  <example id="indexes-partial-ex1">
-   <title>Setting up a Partial Index to Exclude Common Values</title>
-
-   <para>
-    Suppose you are storing web server access logs in a database.
-    Most accesses originate from the IP address range of your organization but
-    some are from elsewhere (say, employees on dial-up connections).
-    If your searches by IP are primarily for outside accesses,
-    you probably do not need to index the IP range that corresponds to your
-    organization's subnet.
-   </para>
-
-   <para>
-    Assume a table like this:
-<programlisting>
-CREATE TABLE access_log (
-    url varchar,
-    client_ip inet,
-    ...
-);
-</programlisting>
-   </para>
-
-   <para>
-    To create a partial index that suits our example, use a command
-    such as this:
-<programlisting>
-CREATE INDEX access_log_client_ip_ix ON access_log (client_ip)
-WHERE NOT (client_ip &gt; inet '192.168.100.0' AND
-           client_ip &lt; inet '192.168.100.255');
-</programlisting>
-   </para>
-
-   <para>
-    A typical query that can use this index would be:
-<programlisting>
-SELECT *
-FROM access_log
-WHERE url = '/index.html' AND client_ip = inet '212.78.10.32';
-</programlisting>
-    A query that cannot use this index is:
-<programlisting>
-SELECT *
-FROM access_log
-WHERE client_ip = inet '192.168.100.23';
-</programlisting>
-   </para>
-
-   <para>
-    Observe that this kind of partial index requires that the common
-    values be predetermined, so such partial indexes are best used for
-    data distributions that do not change.  The indexes can be recreated
-    occasionally to adjust for new data distributions, but this adds
-    maintenance effort.
-   </para>
-  </example>
-
-  <para>
-   Another possible use for a partial index is to exclude values from the
-   index that the
-   typical query workload is not interested in; this is shown in <xref
-   linkend="indexes-partial-ex2">.  This results in the same
-   advantages as listed above, but it prevents the
-   <quote>uninteresting</quote> values from being accessed via that
-   index, even if an index scan might be profitable in that
-   case.  Obviously, setting up partial indexes for this kind of
-   scenario will require a lot of care and experimentation.
-  </para>
-
-  <example id="indexes-partial-ex2">
-   <title>Setting up a Partial Index to Exclude Uninteresting Values</title>
-
-   <para>
-    If you have a table that contains both billed and unbilled orders,
-    where the unbilled orders take up a small fraction of the total
-    table and yet those are the most-accessed rows, you can improve
-    performance by creating an index on just the unbilled rows.  The
-    command to create the index would look like this:
-<programlisting>
-CREATE INDEX orders_unbilled_index ON orders (order_nr)
-    WHERE billed is not true;
-</programlisting>
-   </para>
-
-   <para>
-    A possible query to use this index would be:
-<programlisting>
-SELECT * FROM orders WHERE billed is not true AND order_nr &lt; 10000;
-</programlisting>
-    However, the index can also be used in queries that do not involve
-    <structfield>order_nr</> at all, e.g.:
-<programlisting>
-SELECT * FROM orders WHERE billed is not true AND amount &gt; 5000.00;
-</programlisting>
-    This is not as efficient as a partial index on the
-    <structfield>amount</> column would be, since the system has to
-    scan the entire index.  Yet, if there are relatively few unbilled
-    orders, using this partial index just to find the unbilled orders
-    could be a win.
-   </para>
-
-   <para>
-    Note that this query cannot use this index:
-<programlisting>
-SELECT * FROM orders WHERE order_nr = 3501;
-</programlisting>
-    The order 3501 might be among the billed or unbilled
-    orders.
-   </para>
-  </example>
-
-  <para>
-   <xref linkend="indexes-partial-ex2"> also illustrates that the
-   indexed column and the column used in the predicate do not need to
-<!## PG>
-   match.  <productname>PostgreSQL</productname> supports partial
-<!## end>
-<!## XC>
-   match.  <productname>Postgres-XC</productname> supports partial
-<!## end>
-<!## XL>
-   match.  <productname>Postgres-XL</productname> supports partial
-<!## end>
-   indexes with arbitrary predicates, so long as only columns of the
-   table being indexed are involved.  However, keep in mind that the
-   predicate must match the conditions used in the queries that
-   are supposed to benefit from the index.  To be precise, a partial
-   index can be used in a query only if the system can recognize that
-   the <literal>WHERE</> condition of the query mathematically implies
-   the predicate of the index.
-<!## PG>
-   <productname>PostgreSQL</productname> does not have a sophisticated
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> does not have a sophisticated
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> does not have a sophisticated
-<!## end>
-   theorem prover that can recognize mathematically equivalent
-   expressions that are written in different forms.  (Not
-   only is such a general theorem prover extremely difficult to
-   create, it would probably be too slow to be of any real use.)
-   The system can recognize simple inequality implications, for example
-   <quote>x &lt; 1</quote> implies <quote>x &lt; 2</quote>; otherwise
-   the predicate condition must exactly match part of the query's
-   <literal>WHERE</> condition
-   or the index will not be recognized as usable. Matching takes
-   place at query planning time, not at run time. As a result,
-   parameterized query clauses do not work with a partial index. For
-   example a prepared query with a parameter might specify
-   <quote>x &lt; ?</quote> which will never imply
-   <quote>x &lt; 2</quote> for all possible values of the parameter.
-  </para>
-
-  <para>
-   A third possible use for partial indexes does not require the
-   index to be used in queries at all.  The idea here is to create
-   a unique index over a subset of a table, as in <xref
-   linkend="indexes-partial-ex3">.  This enforces uniqueness
-   among the rows that satisfy the index predicate, without constraining
-   those that do not.
-  </para>
-
-  <example id="indexes-partial-ex3">
-   <title>Setting up a Partial Unique Index</title>
-
-   <para>
-    Suppose that we have a table describing test outcomes.  We wish
-    to ensure that there is only one <quote>successful</> entry for
-    a given subject and target combination, but there might be any number of
-    <quote>unsuccessful</> entries.  Here is one way to do it:
-<programlisting>
-CREATE TABLE tests (
-    subject text,
-    target text,
-    success boolean,
-    ...
-);
-
-CREATE UNIQUE INDEX tests_success_constraint ON tests (subject, target)
-    WHERE success;
-</programlisting>
-    This is a particularly efficient approach when there are few
-    successful tests and many unsuccessful ones.
-   </para>
-  </example>
-
-  <para>
-   Finally, a partial index can also be used to override the system's
-   query plan choices.  Also, data sets with peculiar
-   distributions might cause the system to use an index when it really
-   should not.  In that case the index can be set up so that it is not
-   available for the offending query.  Normally,
-<!## PG>
-   <productname>PostgreSQL</> makes reasonable choices about index
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> makes reasonable choices about index
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> makes reasonable choices about index
-<!## end>
-   usage (e.g., it avoids them when retrieving common values, so the
-   earlier example really only saves index size, it is not required to
-   avoid index usage), and grossly incorrect plan choices are cause
-   for a bug report.
-  </para>
-
-  <para>
-   Keep in mind that setting up a partial index indicates that you
-   know at least as much as the query planner knows, in particular you
-   know when an index might be profitable.  Forming this knowledge
-   requires experience and understanding of how indexes in
-<!## PG>
-   <productname>PostgreSQL</> work.  In most cases, the advantage of a
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> work.  In most cases, the advantage of a
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> work.  In most cases, the advantage of a
-<!## end>
-   partial index over a regular index will be minimal.
-  </para>
-
-  <para>
-   More information about partial indexes can be found in <xref
-   linkend="STON89b">, <xref linkend="OLSON93">, and <xref
-   linkend="SESHADRI95">.
-  </para>
-&xc-constraint;
- </sect1>
-
-
- <sect1 id="indexes-opclass">
-  <title>Operator Classes and Operator Families</title>
-
-  <indexterm zone="indexes-opclass">
-   <primary>operator class</primary>
-  </indexterm>
-
-  <indexterm zone="indexes-opclass">
-   <primary>operator family</primary>
-  </indexterm>
-&common;
-  <para>
-   An index definition can specify an <firstterm>operator
-   class</firstterm> for each column of an index.
-<synopsis>
-CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable> (<replaceable>column</replaceable> <replaceable>opclass</replaceable> <optional><replaceable>sort options</replaceable></optional> <optional>, ...</optional>);
-</synopsis>
-   The operator class identifies the operators to be used by the index
-   for that column.  For example, a B-tree index on the type <type>int4</type>
-   would use the <literal>int4_ops</literal> class; this operator
-   class includes comparison functions for values of type <type>int4</type>.
-   In practice the default operator class for the column's data type is
-   usually sufficient.  The main reason for having operator classes is
-   that for some data types, there could be more than one meaningful
-   index behavior.  For example, we might want to sort a complex-number data
-   type either by absolute value or by real part.  We could do this by
-   defining two operator classes for the data type and then selecting
-   the proper class when making an index.  The operator class determines
-   the basic sort ordering (which can then be modified by adding sort options
-   <literal>COLLATE</literal>,
-   <literal>ASC</>/<literal>DESC</> and/or
-   <literal>NULLS FIRST</>/<literal>NULLS LAST</>).
-  </para>
-
-  <para>
-   There are also some built-in operator classes besides the default ones:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      The operator classes <literal>text_pattern_ops</literal>,
-      <literal>varchar_pattern_ops</literal>, and
-      <literal>bpchar_pattern_ops</literal> support B-tree indexes on
-      the types <type>text</type>, <type>varchar</type>, and
-      <type>char</type> respectively.  The
-      difference from the default operator classes is that the values
-      are compared strictly character by character rather than
-      according to the locale-specific collation rules.  This makes
-      these operator classes suitable for use by queries involving
-      pattern matching expressions (<literal>LIKE</literal> or POSIX
-      regular expressions) when the database does not use the standard
-      <quote>C</quote> locale.  As an example, you might index a
-      <type>varchar</type> column like this:
-<programlisting>
-CREATE INDEX test_index ON test_table (col varchar_pattern_ops);
-</programlisting>
-      Note that you should also create an index with the default operator
-      class if you want queries involving ordinary <literal>&lt;</>,
-      <literal>&lt;=</>, <literal>&gt;</>, or <literal>&gt;=</> comparisons
-      to use an index.  Such queries cannot use the
-      <literal><replaceable>xxx</replaceable>_pattern_ops</literal>
-      operator classes.  (Ordinary equality comparisons can use these
-      operator classes, however.)  It is possible to create multiple
-      indexes on the same column with different operator classes.
-      If you do use the C locale, you do not need the
-      <literal><replaceable>xxx</replaceable>_pattern_ops</literal>
-      operator classes, because an index with the default operator class
-      is usable for pattern-matching queries in the C locale.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-    The following query shows all defined operator classes:
-
-<programlisting>
-SELECT am.amname AS index_method,
-       opc.opcname AS opclass_name
-    FROM pg_am am, pg_opclass opc
-    WHERE opc.opcmethod = am.oid
-    ORDER BY index_method, opclass_name;
-</programlisting>
-  </para>
-
-  <para>
-   An operator class is actually just a subset of a larger structure called an
-   <firstterm>operator family</>.  In cases where several data types have
-   similar behaviors, it is frequently useful to define cross-data-type
-   operators and allow these to work with indexes.  To do this, the operator
-   classes for each of the types must be grouped into the same operator
-   family.  The cross-type operators are members of the family, but are not
-   associated with any single class within the family.
-  </para>
-
-  <para>
-    This query shows all defined operator families and all
-    the operators included in each family:
-<programlisting>
-SELECT am.amname AS index_method,
-       opf.opfname AS opfamily_name,
-       amop.amopopr::regoperator AS opfamily_operator
-    FROM pg_am am, pg_opfamily opf, pg_amop amop
-    WHERE opf.opfmethod = am.oid AND
-          amop.amopfamily = opf.oid
-    ORDER BY index_method, opfamily_name, opfamily_operator;
-</programlisting>
-  </para>
- </sect1>
-
-
- <sect1 id="indexes-collations">
-  <title>Indexes and Collations</title>
-
-  <para>
-   An index can support only one collation per index column.
-   If multiple collations are of interest, multiple indexes may be needed.
-  </para>
-
-  <para>
-   Consider these statements:
-<programlisting>
-CREATE TABLE test1c (
-    id integer,
-    content varchar COLLATE "x"
-);
-
-CREATE INDEX test1c_content_index ON test1c (content);
-</programlisting>
-   The index automatically uses the collation of the
-   underlying column.  So a query of the form
-<programlisting>
-SELECT * FROM test1c WHERE content &gt; <replaceable>constant</replaceable>;
-</programlisting>
-   could use the index, because the comparison will by default use the
-   collation of the column.  However, this index cannot accelerate queries
-   that involve some other collation.  So if queries of the form, say,
-<programlisting>
-SELECT * FROM test1c WHERE content &gt; <replaceable>constant</replaceable> COLLATE "y";
-</programlisting>
-   are also of interest, an additional index could be created that supports
-   the <literal>"y"</literal> collation, like this:
-<programlisting>
-CREATE INDEX test1c_content_y_index ON test1c (content COLLATE "y");
-</programlisting>
-  </para>
- </sect1>
-
-
- <sect1 id="indexes-examine">
-  <title>Examining Index Usage</title>
-
-  <indexterm zone="indexes-examine">
-   <primary>index</primary>
-   <secondary>examining usage</secondary>
-  </indexterm>
-&common;
-  <para>
-<!## PG>
-   Although indexes in <productname>PostgreSQL</> do not need
-<!## end>
-<!## XC>
-   Although indexes in <productname>Postgres-XC</> do not need
-<!## end>
-<!## XL>
-   Although indexes in <productname>Postgres-XL</> do not need
-<!## end>
-   maintenance or tuning, it is still important to check
-   which indexes are actually used by the real-life query workload.
-   Examining index usage for an individual query is done with the
-   <xref linkend="sql-explain">
-   command; its application for this purpose is
-   illustrated in <xref linkend="using-explain">.
-   It is also possible to gather overall statistics about index usage
-   in a running server, as described in <xref linkend="monitoring-stats">.
-  </para>
-
-  <para>
-   It is difficult to formulate a general procedure for determining
-   which indexes to create.  There are a number of typical cases that
-   have been shown in the examples throughout the previous sections.
-   A good deal of experimentation is often necessary.
-   The rest of this section gives some tips for that:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Always run <xref linkend="sql-analyze">
-     first.  This command
-     collects statistics about the distribution of the values in the
-     table.  This information is required to estimate the number of rows
-     returned by a query, which is needed by the planner to assign
-     realistic costs to each possible query plan.  In absence of any
-     real statistics, some default values are assumed, which are
-     almost certain to be inaccurate.  Examining an application's
-     index usage without having run <command>ANALYZE</command> is
-     therefore a lost cause.
-     See <xref linkend="vacuum-for-statistics">
-     and <xref linkend="autovacuum"> for more information.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Use real data for experimentation.  Using test data for setting
-     up indexes will tell you what indexes you need for the test data,
-     but that is all.
-    </para>
-
-    <para>
-     It is especially fatal to use very small test data sets.
-     While selecting 1000 out of 100000 rows could be a candidate for
-     an index, selecting 1 out of 100 rows will hardly be, because the
-     100 rows probably fit within a single disk page, and there
-     is no plan that can beat sequentially fetching 1 disk page.
-    </para>
-
-    <para>
-     Also be careful when making up test data, which is often
-     unavoidable when the application is not yet in production.
-     Values that are very similar, completely random, or inserted in
-     sorted order will skew the statistics away from the distribution
-     that real data would have.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     When indexes are not used, it can be useful for testing to force
-     their use.  There are run-time parameters that can turn off
-     various plan types (see <xref linkend="runtime-config-query-enable">).
-     For instance, turning off sequential scans
-     (<varname>enable_seqscan</>) and nested-loop joins
-     (<varname>enable_nestloop</>), which are the most basic plans,
-     will force the system to use a different plan.  If the system
-     still chooses a sequential scan or nested-loop join then there is
-     probably a more fundamental reason why the index is not being
-     used; for example, the query condition does not match the index.
-     (What kind of query can use what kind of index is explained in
-     the previous sections.)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     If forcing index usage does use the index, then there are two
-     possibilities: Either the system is right and using the index is
-     indeed not appropriate, or the cost estimates of the query plans
-     are not reflecting reality.  So you should time your query with
-     and without indexes.  The <command>EXPLAIN ANALYZE</command>
-     command can be useful here.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     If it turns out that the cost estimates are wrong, there are,
-     again, two possibilities.  The total cost is computed from the
-     per-row costs of each plan node times the selectivity estimate of
-     the plan node.  The costs estimated for the plan nodes can be adjusted
-     via run-time parameters (described in <xref
-     linkend="runtime-config-query-constants">).
-     An inaccurate selectivity estimate is due to
-     insufficient statistics.  It might be possible to improve this by
-     tuning the statistics-gathering parameters (see
-     <xref linkend="sql-altertable">).
-    </para>
-
-    <para>
-     If you do not succeed in adjusting the costs to be more
-     appropriate, then you might have to resort to forcing index usage
-     explicitly.  You might also want to contact the
-<!## PG>
-     <productname>PostgreSQL</> developers to examine the issue.
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</> developers to examine the issue.
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</> developers to examine the issue.
-<!## end>
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/info.sgmlin b/doc-xc/src/sgml/info.sgmlin
deleted file mode 100644
index e919a40942..0000000000
--- a/doc-xc/src/sgml/info.sgmlin
+++ /dev/null
@@ -1,145 +0,0 @@
-<!-- doc/src/sgml/info.sgml -->
-
-<sect1 id="resources">
- <title>Further Information</title>
-
- <para>
-  Besides the documentation, that is, this book, there are other
-<!## PG>
-  resources about <productname>PostgreSQL</productname>:
-<!## end>
-<!## XC>
-&xconly;
-  resources about <productname>Postgres-XC</productname>:
-<!## end>
-<!## XL>
-  resources about <productname>Postgres-XL</productname>:
-<!## end>
-
-  <variablelist>
-
-   <varlistentry>
-    <term>Wiki</term>
-    <listitem>
-     <para>
-<!## PG>
-      The <productname>PostgreSQL</productname> <ulink
-      url="http://wiki.postgresql.org">wiki</ulink> contains the project's <ulink
-      url="http://wiki.postgresql.org/wiki/Frequently_Asked_Questions">FAQ</>
-      (Frequently Asked Questions) list, <ulink
-      url="http://wiki.postgresql.org/wiki/Todo">TODO</> list, and
-      detailed information about many more topics.
-<!## end>
-<!## XC>
-      The <productname>Postgres-XC</productname> <ulink
-      url="https://sourceforge.net/apps/mediawiki/postgres-xc/">wiki</ulink> contains the project's 
-	  information, links to related pages and <ulink
-      url="https://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=Developers"> various development information</>.
-<!## end>
-<!## XL>
-      The <productname>Postgres-XL</productname> <ulink
-      url="http://sourceforge.net/p/postgres-xl/wiki/Home/">wiki</ulink> contains the project's 
-	  information, links to related pages and various development information.
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Web Site</term>
-    <listitem>
-     <para>
-<!## PG>
-      The <productname>PostgreSQL</productname>
-      <ulink url="http://www.postgresql.org">web site</ulink>
-      carries details on the latest release and other
-      information to make your work or play with
-      <productname>PostgreSQL</productname> more productive.
-<!## end>
-<!## XC>
-      The <productname>Postgres-XC</productname> 
-      <ulink url="http://postgres-xc.sourceforge.net/">web site</ulink>
-      carries details on the latest release and other
-      information to make your work or play with
-      <productname>Postgres-XC</productname> more productive.
-<!## end>
-<!## XL>
-      The <productname>Postgres-XL</productname> 
-      <ulink url="http://postgres-xl.sourceforge.net/">web site</ulink>
-      carries details on the latest release and other
-      information to make your work or play with
-      <productname>Postgres-XL</productname> more productive.
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Mailing Lists</term>
-    <listitem>
-     <para>
-<!## PG>
-      The mailing lists are a good place to have your questions
-      answered, to share experiences with other users, and to contact
-      the developers.  Consult the <productname>PostgreSQL</> web site
-      for details.
-<!## end>
-<!## XC>
-      The mailing lists are a good place to have your questions
-      answered, to share experiences with other users, and to contact
-      the developers.  Consult the <productname>Postgres-XC</> web site
-      for details.
-<!## end>
-<!## XL>
-      The mailing lists are a good place to have your questions
-      answered, to share experiences with other users, and to contact
-      the developers.  Consult the <productname>Postgres-XL</> web site
-      for details.
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Yourself!</term>
-    <listitem>
-     <para>
-<!## PG>
-      <productname>PostgreSQL</productname> is an open-source project.
-      As such, it depends on the user community for ongoing support.
-      As you begin to use <productname>PostgreSQL</productname>, you
-      will rely on others for help, either through the documentation
-      or through the mailing lists.  Consider contributing your
-      knowledge back. Read the mailing lists and answer questions.  If
-      you learn something which is not in the documentation, write it
-      up and contribute it.  If you add features to the code,
-      contribute them.
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname> is an open-source project.
-      As such, it depends on the user community for ongoing support.
-      As you begin to use <productname>Postgres-XC</productname>, you
-      will rely on others for help, either through the documentation
-      or through the mailing lists.  Consider contributing your
-      knowledge back. Read the mailing lists and answer questions.  If
-      you learn something which is not in the documentation, write it
-      up and contribute it.  If you add features to the code,
-      contribute them.
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname> is an open-source project.
-      As such, it depends on the user community for ongoing support.
-      As you begin to use <productname>Postgres-XL</productname>, you
-      will rely on others for help, either through the documentation
-      or through the mailing lists.  Consider contributing your
-      knowledge back. Read the mailing lists and answer questions.  If
-      you learn something which is not in the documentation, write it
-      up and contribute it.  If you add features to the code,
-      contribute them.
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </para>
-</sect1>
diff --git a/doc-xc/src/sgml/information_schema.sgmlin b/doc-xc/src/sgml/information_schema.sgmlin
deleted file mode 100644
index 2e76ef05cf..0000000000
--- a/doc-xc/src/sgml/information_schema.sgmlin
+++ /dev/null
@@ -1,7490 +0,0 @@
-<!-- doc/src/sgml/information_schema.sgml -->
-
-<chapter id="information-schema">
- <title>The Information Schema</title>
-
- <indexterm zone="information-schema">
-  <primary>information schema</primary>
- </indexterm>
-
-&common;
- <para>
-  The information schema consists of a set of views that contain
-  information about the objects defined in the current database.  The
-  information schema is defined in the SQL standard and can therefore
-  be expected to be portable and remain stable &mdash; unlike the system
-  catalogs, which are specific to
-<!## PG>
-  <productname>PostgreSQL</productname> and are modelled after
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> and are modelled after
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> and are modelled after
-<!## end>
-  implementation concerns.  The information schema views do not,
-  however, contain information about
-<!## PG>
-  <productname>PostgreSQL</productname>-specific features; to inquire
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname>-specific features; to inquire
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname>-specific features; to inquire
-<!## end>
-  about those you need to query the system catalogs or other
-  <productname>PostgreSQL</productname>-specific views.
- </para>
-
- <note>
-  <para>
-   When querying the database for constraint information, it is possible
-   for a standard-compliant query that expects to return one row to
-   return several.  This is because the SQL standard requires constraint
-   names to be unique within a schema, but
-<!## PG>
-   <productname>PostgreSQL</productname> does not enforce this
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> does not enforce this
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> does not enforce this
-<!## end>
-   restriction.  <productname>PostgreSQL</productname>
-   automatically-generated constraint names avoid duplicates in the
-   same schema, but users can specify such duplicate names.
-  </para>
-
-  <para>
-   This problem can appear when querying information schema views such
-   as <literal>check_constraint_routine_usage</>,
-   <literal>check_constraints</>, <literal>domain_constraints</>, and
-   <literal>referential_constraints</>.  Some other views have similar
-   issues but contain the table name to help distinguish duplicate
-   rows, e.g., <literal>constraint_column_usage</>,
-   <literal>constraint_table_usage</>, <literal>table_constraints</>.
-  </para>
- </note>
-
-
- <sect1 id="infoschema-schema">
-  <title>The Schema</title>
-
-&common;
-  <para>
-   The information schema itself is a schema named
-   <literal>information_schema</literal>.  This schema automatically
-   exists in all databases.  The owner of this schema is the initial
-   database user in the cluster, and that user naturally has all the
-   privileges on this schema, including the ability to drop it (but
-   the space savings achieved by that are minuscule).
-  </para>
-
-  <para>
-   By default, the information schema is not in the schema search
-   path, so you need to access all objects in it through qualified
-   names.  Since the names of some of the objects in the information
-   schema are generic names that might occur in user applications, you
-   should be careful if you want to put the information schema in the
-   path.
-  </para>
- </sect1>
-
- <sect1 id="infoschema-datatypes">
-  <title>Data Types</title>
-&common;
-  <para>
-   The columns of the information schema views use special data types
-   that are defined in the information schema.  These are defined as
-   simple domains over ordinary built-in types.  You should not use
-   these types for work outside the information schema, but your
-   applications must be prepared for them if they select from the
-   information schema.
-  </para>
-
-  <para>
-   These types are:
-
-   <variablelist>
-    <varlistentry>
-     <term><type>cardinal_number</type></term>
-     <listitem>
-      <para>
-       A nonnegative integer.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><type>character_data</type></term>
-     <listitem>
-      <para>
-       A character string (without specific maximum length).
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><type>sql_identifier</type></term>
-     <listitem>
-      <para>
-       A character string.  This type is used for SQL identifiers, the
-       type <type>character_data</type> is used for any other kind of
-       text data.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><type>time_stamp</type></term>
-     <listitem>
-      <para>
-       A domain over the type <type>timestamp with time zone</type>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><type>yes_or_no</type></term>
-     <listitem>
-      <para>
-       A character string domain that contains
-       either <literal>YES</literal> or <literal>NO</literal>.  This
-       is used to represent Boolean (true/false) data in the
-       information schema.  (The information schema was invented
-       before the type <type>boolean</type> was added to the SQL
-       standard, so this convention is necessary to keep the
-       information schema backward compatible.)
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-   Every column in the information schema has one of these five types.
-  </para>
- </sect1>
-
- <sect1 id="infoschema-information-schema-catalog-name">
-  <title><literal>information_schema_catalog_name</literal></title>
-&common;
-  <para>
-   <literal>information_schema_catalog_name</literal> is a table that
-   always contains one row and one column containing the name of the
-   current database (current catalog, in SQL terminology).
-  </para>
-
-  <table>
-   <title><literal>information_schema_catalog_name</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>catalog_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains this information schema</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-administrable-role-authorizations">
-  <title><literal>administrable_role_authorizations</literal></title>
-&common;
-  <para>
-   The view <literal>administrable_role_authorizations</literal>
-   identifies all roles that the current user has the admin option
-   for.
-  </para>
-
-  <table>
-   <title><literal>administrable_role_authorizations</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>grantee</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the role to which this role membership was granted (can
-       be the current user, or a different role in case of nested role
-       memberships)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>role_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of a role</entry>
-     </row>
-
-     <row>
-      <entry><literal>is_grantable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>Always <literal>YES</literal></entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-applicable-roles">
-  <title><literal>applicable_roles</literal></title>
-&common;
-  <para>
-   The view <literal>applicable_roles</literal> identifies all roles
-   whose privileges the current user can use.  This means there is
-   some chain of role grants from the current user to the role in
-   question.  The current user itself is also an applicable role.  The
-   set of applicable roles is generally used for permission checking.
-   <indexterm><primary>applicable role</primary></indexterm>
-   <indexterm><primary>role</primary><secondary>applicable</secondary></indexterm>
-  </para>
-
-  <table>
-   <title><literal>applicable_roles</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>grantee</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the role to which this role membership was granted (can
-       be the current user, or a different role in case of nested role
-       memberships)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>role_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of a role</entry>
-     </row>
-
-     <row>
-      <entry><literal>is_grantable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</literal> if the grantee has the admin option on
-       the role, <literal>NO</literal> if not
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-attributes">
-  <title><literal>attributes</literal></title>
-&common;
-  <para>
-   The view <literal>attributes</literal> contains information about
-   the attributes of composite data types defined in the database.
-   (Note that the view does not give information about table columns,
-<!## PG>
-   which are sometimes called attributes in PostgreSQL contexts.)
-<!## end>
-<!## XC>
-   which are sometimes called attributes in Postgres-XC contexts.)
-<!## end>
-<!## XL>
-   which are sometimes called attributes in Postgres-XL contexts.)
-<!## end>
-  </para>
-
-  <table>
-   <title><literal>attributes</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the data type (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the data type</entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the data type</entry>
-     </row>
-
-     <row>
-      <entry><literal>attribute_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the attribute</entry>
-     </row>
-
-     <row>
-      <entry><literal>ordinal_position</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>Ordinal position of the attribute within the data type (count starts at 1)</entry>
-     </row>
-
-     <row>
-      <entry><literal>attribute_default</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Default expression of the attribute</entry>
-     </row>
-
-     <row>
-      <entry><literal>is_nullable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</literal> if the attribute is possibly nullable,
-       <literal>NO</literal> if it is known not nullable.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>data_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Data type of the attribute, if it is a built-in type, or
-       <literal>ARRAY</literal> if it is some array (in that case, see
-       the view <literal>element_types</literal>), else
-       <literal>USER-DEFINED</literal> (in that case, the type is
-       identified in <literal>attribute_udt_name</literal> and
-       associated columns).
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_maximum_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a character or bit
-       string type, the declared maximum length; null for all other
-       data types or if no maximum length was declared.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_octet_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a character type,
-       the maximum possible length in octets (bytes) of a datum; null
-       for all other data types.  The maximum octet length depends on
-       the declared character maximum length (see above) and the
-       server encoding.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a numeric type, this
-       column contains the (declared or implicit) precision of the
-       type for this attribute.  The precision indicates the number of
-       significant digits.  It can be expressed in decimal (base 10)
-       or binary (base 2) terms, as specified in the column
-       <literal>numeric_precision_radix</literal>.  For all other data
-       types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision_radix</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a numeric type, this
-       column indicates in which base the values in the columns
-       <literal>numeric_precision</literal> and
-       <literal>numeric_scale</literal> are expressed.  The value is
-       either 2 or 10.  For all other data types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_scale</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies an exact numeric
-       type, this column contains the (declared or implicit) scale of
-       the type for this attribute.  The scale indicates the number of
-       significant digits to the right of the decimal point.  It can
-       be expressed in decimal (base 10) or binary (base 2) terms, as
-       specified in the column
-       <literal>numeric_precision_radix</literal>.  For all other data
-       types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>datetime_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a date, time,
-       timestamp, or interval type, this column contains the (declared
-       or implicit) fractional seconds precision of the type for this
-       attribute, that is, the number of decimal digits maintained
-       following the decimal point in the seconds value.  For all
-       other data types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>interval_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Not yet implemented</entry>
-     </row>
-
-     <row>
-      <entry><literal>interval_precision</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Not yet implemented</entry>
-     </row>
-
-     <row>
-      <entry><literal>attribute_udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that the attribute data type is defined in
-       (always the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>attribute_udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that the attribute data type is defined in
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>attribute_udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the attribute data type
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>scope_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>maximum_cardinality</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>dtd_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       An identifier of the data type descriptor of the column, unique
-       among the data type descriptors pertaining to the table.  This
-       is mainly useful for joining with other instances of such
-       identifiers.  (The specific format of the identifier is not
-       defined and not guaranteed to remain the same in future
-       versions.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_derived_reference_attribute</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   See also under <xref linkend="infoschema-columns">, a similarly
-   structured view, for further information on some of the columns.
-  </para>
- </sect1>
-
- <sect1 id="infoschema-character-sets">
-  <title><literal>character_sets</literal></title>
-
-  <para>
-   The view <literal>character_sets</literal> identifies the character
-<!## PG>
-   sets available in the current database.  Since PostgreSQL does not
-<!## end>
-<!## XC>
-   sets available in the current database.  Since Postgres-XC does not
-<!## end>
-<!## XL>
-   sets available in the current database.  Since Postgres-XL does not
-<!## end>
-   support multiple character sets within one database, this view only
-   shows one, which is the database encoding.
-  </para>
-
-  <para>
-   Take note of how the following terms are used in the SQL standard:
-   <variablelist>
-    <varlistentry>
-     <term>character repertoire</term>
-     <listitem>
-      <para>
-       An abstract collection of characters, for
-       example <literal>UNICODE</literal>, <literal>UCS</literal>, or
-       <literal>LATIN1</literal>.  Not exposed as an SQL object, but
-       visible in this view.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>character encoding form</term>
-     <listitem>
-      <para>
-       An encoding of some character repertoire.  Most older character
-       repertoires only use one encoding form, and so there are no
-       separate names for them (e.g., <literal>LATIN1</literal> is an
-       encoding form applicable to the <literal>LATIN1</literal>
-       repertoire).  But for example Unicode has the encoding forms
-       <literal>UTF8</literal>, <literal>UTF16</literal>, etc. (not
-<!## PG>
-       all supported by PostgreSQL).  Encoding forms are not exposed
-<!## end>
-<!## XC>
-       all supported by Postgres-XC).  Encoding forms are not exposed
-<!## end>
-<!## XL>
-       all supported by Postgres-XL).  Encoding forms are not exposed
-<!## end>
-       as an SQL object, but are visible in this view.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>character set</term>
-     <listitem>
-      <para>
-       A named SQL object that identifies a character repertoire, a
-       character encoding, and a default collation.  A predefined
-       character set would typically have the same name as an encoding
-       form, but users could define other names.  For example, the
-       character set <literal>UTF8</literal> would typically identify
-       the character repertoire <literal>UCS</literal>, encoding
-       form <literal>UTF8</literal>, and some default collation.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-<!## PG>
-   You can think of an <quote>encoding</quote> in PostgreSQL either as
-<!## end>
-<!## XC>
-   You can think of an <quote>encoding</quote> in Postgres-XC either as
-<!## end>
-<!## XL>
-   You can think of an <quote>encoding</quote> in Postgres-XL either as
-<!## end>
-   a character set or a character encoding form.  They will have the
-   same name, and there can only be one in one database.
-  </para>
-
-  <table>
-   <title><literal>character_sets</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>character_set_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Character sets are currently not implemented as schema objects, so this column is null.</entry>
-     </row>
-
-     <row>
-      <entry><literal>character_set_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Character sets are currently not implemented as schema objects, so this column is null.</entry>
-     </row>
-
-     <row>
-      <entry><literal>character_set_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the character set, currently implemented as showing the name of the database encoding</entry>
-     </row>
-
-     <row>
-      <entry><literal>character_repertoire</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Character repertoire, showing <literal>UCS</literal> if the encoding is <literal>UTF8</literal>, else just the encoding name</entry>
-     </row>
-
-     <row>
-      <entry><literal>form_of_use</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Character encoding form, same as the database encoding</entry>
-     </row>
-
-     <row>
-      <entry><literal>default_collate_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the database containing the default collation (always the current database, if any collation is identified)</entry>
-     </row>
-
-     <row>
-      <entry><literal>default_collate_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the schema containing the default collation</entry>
-     </row>
-
-     <row>
-      <entry><literal>default_collate_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>
-       Name of the default collation.  The default collation is
-       identified as the collation that matches
-       the <literal>COLLATE</literal> and <literal>CTYPE</literal>
-       settings of the current database.  If there is no such
-       collation, then this column and the associated schema and
-       catalog columns are null.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-check-constraint-routine-usage">
-  <title><literal>check_constraint_routine_usage</literal></title>
-&common;
-  <para>
-   The view <literal>check_constraint_routine_usage</literal>
-   identifies routines (functions and procedures) that are used by a
-   check constraint.  Only those routines are shown that are owned by
-   a currently enabled role.
-  </para>
-
-  <table>
-   <title><literal>check_constraint_routine_usage</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>constraint_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the database containing the constraint (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the schema containing the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the database containing the function (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the schema containing the function</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>
-       The <quote>specific name</quote> of the function.  See <xref
-       linkend="infoschema-routines"> for more information.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-check-constraints">
-  <title><literal>check_constraints</literal></title>
-&common;
-  <para>
-   The view <literal>check_constraints</literal> contains all check
-   constraints, either defined on a table or on a domain, that are
-   owned by a currently enabled role.  (The owner of the table or
-   domain is the owner of the constraint.)
-  </para>
-
-  <table>
-   <title><literal>check_constraints</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>constraint_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the database containing the constraint (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the schema containing the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>check_clause</literal></entry>
-      <entry><literal>character_data</literal></entry>
-      <entry>The check expression of the check constraint</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-collations">
-  <title><literal>collations</literal></title>
-
-  <para>
-   The view <literal>collations</literal> contains the collations
-   available in the current database.
-  </para>
-
-  <table>
-   <title><literal>collations</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>collation_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the database containing the collation (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>collation_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the schema containing the collation</entry>
-     </row>
-
-     <row>
-      <entry><literal>collation_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the default collation</entry>
-     </row>
-
-     <row>
-      <entry><literal>pad_attribute</literal></entry>
-      <entry><literal>character_data</literal></entry>
-      <entry>
-       Always <literal>NO PAD</literal> (The alternative <literal>PAD
-<!## PG>
-       SPACE</literal> is not supported by PostgreSQL.)
-<!## end>
-<!## XC>
-       SPACE</literal> is not supported by Postgres-XC.)
-<!## end>
-<!## XL>
-       SPACE</literal> is not supported by Postgres-XL.)
-<!## end>
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-collation-character-set-applicab"> <!-- max 44 characters -->
-  <title><literal>collation_character_set_applicability</literal></title>
-
-  <para>
-   The view <literal>collation_character_set_applicability</literal>
-   identifies which character set the available collations are
-<!## PG>
-   applicable to.  In PostgreSQL, there is only one character set per
-<!## end>
-<!## XC>
-   applicable to.  In Postgres-XC, there is only one character set per
-<!## end>
-<!## XL>
-   applicable to.  In Postgres-XL, there is only one character set per
-<!## end>
-   database (see explanation
-   in <xref linkend="infoschema-character-sets">), so this view does
-   not provide much useful information.
-  </para>
-
-  <table>
-   <title><literal>collation_character_set_applicability</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>collation_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the database containing the collation (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>collation_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the schema containing the collation</entry>
-     </row>
-
-     <row>
-      <entry><literal>collation_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the default collation</entry>
-     </row>
-
-     <row>
-      <entry><literal>character_set_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Character sets are currently not implemented as schema objects, so this column is null</entry>
-     </row>
-
-     <row>
-      <entry><literal>character_set_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Character sets are currently not implemented as schema objects, so this column is null</entry>
-     </row>
-
-     <row>
-      <entry><literal>character_set_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the character set</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-column-domain-usage">
-  <title><literal>column_domain_usage</literal></title>
-&common;
-  <para>
-   The view <literal>column_domain_usage</literal> identifies all
-   columns (of a table or a view) that make use of some domain defined
-   in the current database and owned by a currently enabled role.
-  </para>
-
-  <table>
-   <title><literal>column_domain_usage</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>domain_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the domain (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the domain</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the domain</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the table (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>column_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the column</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-column-privileges">
-  <title><literal>column_privileges</literal></title>
-&common;
-  <para>
-   The view <literal>column_privileges</literal> identifies all
-   privileges granted on columns to a currently enabled role or by a
-   currently enabled role.  There is one row for each combination of
-   column, grantor, and grantee.
-  </para>
-
-  <para>
-   If a privilege has been granted on an entire table, it will show up in
-   this view as a grant for each column, but only for the
-   privilege types where column granularity is possible:
-   <literal>SELECT</literal>, <literal>INSERT</literal>,
-   <literal>UPDATE</literal>, <literal>REFERENCES</literal>.
-  </para>
-
-  <table>
-   <title><literal>column_privileges</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>grantor</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that granted the privilege</entry>
-     </row>
-
-     <row>
-      <entry><literal>grantee</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that the privilege was granted to</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the table that contains the column (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the table that contains the column</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table that contains the column</entry>
-     </row>
-
-     <row>
-      <entry><literal>column_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the column</entry>
-     </row>
-
-     <row>
-      <entry><literal>privilege_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Type of the privilege: <literal>SELECT</literal>,
-       <literal>INSERT</literal>, <literal>UPDATE</literal>, or
-       <literal>REFERENCES</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_grantable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the privilege is grantable, <literal>NO</literal> if not</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-column-udt-usage">
-  <title><literal>column_udt_usage</literal></title>
-&common;
-  <para>
-   The view <literal>column_udt_usage</literal> identifies all columns
-   that use data types owned by a currently enabled role.  Note that in
-<!## PG>
-   <productname>PostgreSQL</productname>, built-in data types behave
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>, built-in data types behave
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>, built-in data types behave
-<!## end>
-   like user-defined types, so they are included here as well.  See
-   also <xref linkend="infoschema-columns"> for details.
-  </para>
-
-  <table>
-   <title><literal>column_udt_usage</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that the column data type (the underlying
-       type of the domain, if applicable) is defined in (always the
-       current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that the column data type (the underlying
-       type of the domain, if applicable) is defined in
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the column data type (the underlying type of the
-       domain, if applicable)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the table (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>column_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the column</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-columns">
-  <title><literal>columns</literal></title>
-&common;
-  <para>
-   The view <literal>columns</literal> contains information about all
-   table columns (or view columns) in the database.  System columns
-   (<literal>oid</>, etc.) are not included.  Only those columns are
-   shown that the current user has access to (by way of being the
-   owner or having some privilege).
-  </para>
-
-  <table>
-   <title><literal>columns</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the table (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>column_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the column</entry>
-     </row>
-
-     <row>
-      <entry><literal>ordinal_position</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>Ordinal position of the column within the table (count starts at 1)</entry>
-     </row>
-
-     <row>
-      <entry><literal>column_default</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Default expression of the column</entry>
-     </row>
-
-     <row>
-      <entry><literal>is_nullable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</literal> if the column is possibly nullable,
-       <literal>NO</literal> if it is known not nullable.  A not-null
-       constraint is one way a column can be known not nullable, but
-       there can be others.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>data_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Data type of the column, if it is a built-in type, or
-       <literal>ARRAY</literal> if it is some array (in that case, see
-       the view <literal>element_types</literal>), else
-       <literal>USER-DEFINED</literal> (in that case, the type is
-       identified in <literal>udt_name</literal> and associated
-       columns).  If the column is based on a domain, this column
-       refers to the type underlying the domain (and the domain is
-       identified in <literal>domain_name</literal> and associated
-       columns).
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_maximum_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a character or bit
-       string type, the declared maximum length; null for all other
-       data types or if no maximum length was declared.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_octet_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a character type,
-       the maximum possible length in octets (bytes) of a datum; null
-       for all other data types.  The maximum octet length depends on
-       the declared character maximum length (see above) and the
-       server encoding.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a numeric type, this
-       column contains the (declared or implicit) precision of the
-       type for this column.  The precision indicates the number of
-       significant digits.  It can be expressed in decimal (base 10)
-       or binary (base 2) terms, as specified in the column
-       <literal>numeric_precision_radix</literal>.  For all other data
-       types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision_radix</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a numeric type, this
-       column indicates in which base the values in the columns
-       <literal>numeric_precision</literal> and
-       <literal>numeric_scale</literal> are expressed.  The value is
-       either 2 or 10.  For all other data types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_scale</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies an exact numeric
-       type, this column contains the (declared or implicit) scale of
-       the type for this column.  The scale indicates the number of
-       significant digits to the right of the decimal point.  It can
-       be expressed in decimal (base 10) or binary (base 2) terms, as
-       specified in the column
-       <literal>numeric_precision_radix</literal>.  For all other data
-       types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>datetime_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a date, time,
-       timestamp, or interval type, this column contains the (declared
-       or implicit) fractional seconds precision of the type for this
-       column, that is, the number of decimal digits maintained
-       following the decimal point in the seconds value.  For all
-       other data types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>interval_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Not yet implemented</entry>
-     </row>
-
-     <row>
-      <entry><literal>interval_precision</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Not yet implemented</entry>
-     </row>
-
-     <row>
-      <entry><literal>character_set_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>domain_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       If the column has a domain type, the name of the database that
-       the domain is defined in (always the current database), else
-       null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       If the column has a domain type, the name of the schema that
-       the domain is defined in, else null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>If the column has a domain type, the name of the domain, else null.</entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that the column data type (the underlying
-       type of the domain, if applicable) is defined in (always the
-       current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that the column data type (the underlying
-       type of the domain, if applicable) is defined in
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the column data type (the underlying type of the
-       domain, if applicable)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>scope_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>maximum_cardinality</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>dtd_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       An identifier of the data type descriptor of the column, unique
-       among the data type descriptors pertaining to the table.  This
-       is mainly useful for joining with other instances of such
-       identifiers.  (The specific format of the identifier is not
-       defined and not guaranteed to remain the same in future
-       versions.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_self_referencing</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>is_identity</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>identity_generation</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>identity_start</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>identity_increment</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>identity_maximum</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>identity_minimum</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>identity_cycle</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>is_generated</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>generation_expression</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>is_updatable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</literal> if the column is updatable,
-       <literal>NO</literal> if not (Columns in base tables are always
-       updatable, columns in views not necessarily)
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Since data types can be defined in a variety of ways in SQL, and
-<!## PG>
-   <productname>PostgreSQL</productname> contains additional ways to
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> contains additional ways to
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> contains additional ways to
-<!## end>
-   define data types, their representation in the information schema
-   can be somewhat difficult.  The column <literal>data_type</literal>
-   is supposed to identify the underlying built-in type of the column.
-<!## PG>
-   In <productname>PostgreSQL</productname>, this means that the type
-<!## end>
-<!## XC>
-   In <productname>Postgres-XC</productname>, this means that the type
-<!## end>
-<!## XL>
-   In <productname>Postgres-XL</productname>, this means that the type
-<!## end>
-   is defined in the system catalog schema
-   <literal>pg_catalog</literal>.  This column might be useful if the
-   application can handle the well-known built-in types specially (for
-   example, format the numeric types differently or use the data in
-   the precision columns).  The columns <literal>udt_name</literal>,
-   <literal>udt_schema</literal>, and <literal>udt_catalog</literal>
-   always identify the underlying data type of the column, even if the
-   column is based on a domain.  (Since
-<!## PG>
-   <productname>PostgreSQL</productname> treats built-in types like
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> treats built-in types like
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> treats built-in types like
-<!## end>
-   user-defined types, built-in types appear here as well.  This is an
-   extension of the SQL standard.)  These columns should be used if an
-   application wants to process data differently according to the
-   type, because in that case it wouldn't matter if the column is
-   really based on a domain.  If the column is based on a domain, the
-   identity of the domain is stored in the columns
-   <literal>domain_name</literal>, <literal>domain_schema</literal>,
-   and <literal>domain_catalog</literal>.  If you want to pair up
-   columns with their associated data types and treat domains as
-   separate types, you could write <literal>coalesce(domain_name,
-   udt_name)</literal>, etc.
-  </para>
- </sect1>
-
- <sect1 id="infoschema-constraint-column-usage">
-  <title><literal>constraint_column_usage</literal></title>
-&common;
-  <para>
-   The view <literal>constraint_column_usage</literal> identifies all
-   columns in the current database that are used by some constraint.
-   Only those columns are shown that are contained in a table owned by
-   a currently enabled role.  For a check constraint, this view
-   identifies the columns that are used in the check expression.  For
-   a foreign key constraint, this view identifies the columns that the
-   foreign key references.  For a unique or primary key constraint,
-   this view identifies the constrained columns.
-  </para>
-
-  <table>
-   <title><literal>constraint_column_usage</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that contains the table that contains the
-       column that is used by some constraint (always the current
-       database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that contains the table that contains the
-       column that is used by some constraint
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the table that contains the column that is used by some
-       constraint
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>column_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the column that is used by some constraint
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the constraint (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the constraint</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-constraint-table-usage">
-  <title><literal>constraint_table_usage</literal></title>
-&common;
-  <para>
-   The view <literal>constraint_table_usage</literal> identifies all
-   tables in the current database that are used by some constraint and
-   are owned by a currently enabled role.  (This is different from the
-   view <literal>table_constraints</literal>, which identifies all
-   table constraints along with the table they are defined on.)  For a
-   foreign key constraint, this view identifies the table that the
-   foreign key references.  For a unique or primary key constraint,
-   this view simply identifies the table the constraint belongs to.
-   Check constraints and not-null constraints are not included in this
-   view.
-  </para>
-
-  <table>
-   <title><literal>constraint_table_usage</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that contains the table that is used by
-       some constraint (always the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that contains the table that is used by some
-       constraint
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table that is used by some constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the constraint (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the constraint</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-data-type-privileges">
-  <title><literal>data_type_privileges</literal></title>
-&common;
-  <para>
-   The view <literal>data_type_privileges</literal> identifies all
-   data type descriptors that the current user has access to, by way
-   of being the owner of the described object or having some privilege
-   for it.  A data type descriptor is generated whenever a data type
-   is used in the definition of a table column, a domain, or a
-   function (as parameter or return type) and stores some information
-   about how the data type is used in that instance (for example, the
-   declared maximum length, if applicable).  Each data type
-   descriptor is assigned an arbitrary identifier that is unique
-   among the data type descriptor identifiers assigned for one object
-   (table, domain, function).  This view is probably not useful for
-   applications, but it is used to define some other views in the
-   information schema.
-  </para>
-
-  <table>
-   <title><literal>data_type_privileges</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>object_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the described object (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the described object</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the described object</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       The type of the described object: one of
-       <literal>TABLE</literal> (the data type descriptor pertains to
-       a column of that table), <literal>DOMAIN</literal> (the data
-       type descriptors pertains to that domain),
-       <literal>ROUTINE</literal> (the data type descriptor pertains
-       to a parameter or the return data type of that function).
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>dtd_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       The identifier of the data type descriptor, which is unique
-       among the data type descriptors for that same object.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-domain-constraints">
-  <title><literal>domain_constraints</literal></title>
-&common;
-  <para>
-   The view <literal>domain_constraints</literal> contains all
-   constraints belonging to domains defined in the current database.
-  </para>
-
-  <table>
-   <title><literal>domain_constraints</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>constraint_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the constraint (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the domain (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the domain</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the domain</entry>
-     </row>
-
-     <row>
-      <entry><literal>is_deferrable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the constraint is deferrable, <literal>NO</literal> if not</entry>
-     </row>
-
-     <row>
-      <entry><literal>initially_deferred</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the constraint is deferrable and initially deferred, <literal>NO</literal> if not</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-domain-udt-usage">
-  <title><literal>domain_udt_usage</literal></title>
-&common;
-  <para>
-   The view <literal>domain_udt_usage</literal> identifies all domains
-   that are based on data types owned by a currently enabled role.
-<!## PG>
-   Note that in <productname>PostgreSQL</productname>, built-in data
-<!## end>
-<!## XC>
-   Note that in <productname>Postgres-XC</productname>, built-in data
-<!## end>
-<!## XL>
-   Note that in <productname>Postgres-XL</productname>, built-in data
-<!## end>
-   types behave like user-defined types, so they are included here as
-   well.
-  </para>
-
-  <table>
-   <title><literal>domain_udt_usage</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the domain data type is defined in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that the domain data type is defined in</entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the domain data type</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the domain (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the domain</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the domain</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-domains">
-  <title><literal>domains</literal></title>
-&common;
-  <para>
-   The view <literal>domains</literal> contains all domains defined in
-   the current database.
-  </para>
-
-  <table>
-   <title><literal>domains</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>domain_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the domain (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the domain</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the domain</entry>
-     </row>
-
-     <row>
-      <entry><literal>data_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Data type of the domain, if it is a built-in type, or
-       <literal>ARRAY</literal> if it is some array (in that case, see
-       the view <literal>element_types</literal>), else
-       <literal>USER-DEFINED</literal> (in that case, the type is
-       identified in <literal>udt_name</literal> and associated
-       columns).
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_maximum_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If the domain has a character or bit string type, the declared
-       maximum length; null for all other data types or if no maximum
-       length was declared.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_octet_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If the domain has a character type, the maximum possible length
-       in octets (bytes) of a datum; null for all other data types.
-       The maximum octet length depends on the declared character
-       maximum length (see above) and the server encoding.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_set_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If the domain has a numeric type, this column contains the
-       (declared or implicit) precision of the type for this domain.
-       The precision indicates the number of significant digits.  It
-       can be expressed in decimal (base 10) or binary (base 2) terms,
-       as specified in the column
-       <literal>numeric_precision_radix</literal>.  For all other data
-       types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision_radix</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If the domain has a numeric type, this column indicates in
-       which base the values in the columns
-       <literal>numeric_precision</literal> and
-       <literal>numeric_scale</literal> are expressed.  The value is
-       either 2 or 10.  For all other data types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_scale</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If the domain has an exact numeric type, this column contains
-       the (declared or implicit) scale of the type for this domain.
-       The scale indicates the number of significant digits to the
-       right of the decimal point.  It can be expressed in decimal
-       (base 10) or binary (base 2) terms, as specified in the column
-       <literal>numeric_precision_radix</literal>.  For all other data
-       types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>datetime_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       If <literal>data_type</literal> identifies a date, time,
-       timestamp, or interval type, this column contains the (declared
-       or implicit) fractional seconds precision of the type for this
-       domain, that is, the number of decimal digits maintained
-       following the decimal point in the seconds value.  For all
-       other data types, this column is null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>interval_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Not yet implemented</entry>
-     </row>
-
-     <row>
-      <entry><literal>interval_precision</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Not yet implemented</entry>
-     </row>
-
-     <row>
-      <entry><literal>domain_default</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Default expression of the domain</entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the domain data type is defined in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that the domain data type is defined in</entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the domain data type</entry>
-     </row>
-
-     <row>
-      <entry><literal>scope_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>maximum_cardinality</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>dtd_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       An identifier of the data type descriptor of the domain, unique
-       among the data type descriptors pertaining to the domain (which
-       is trivial, because a domain only contains one data type
-       descriptor).  This is mainly useful for joining with other
-       instances of such identifiers.  (The specific format of the
-       identifier is not defined and not guaranteed to remain the same
-       in future versions.)
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-element-types">
-  <title><literal>element_types</literal></title>
-&common;
-  <para>
-   The view <literal>element_types</literal> contains the data type
-   descriptors of the elements of arrays.  When a table column,
-   domain, function parameter, or function return value is defined to
-   be of an array type, the respective information schema view only
-   contains <literal>ARRAY</literal> in the column
-   <literal>data_type</literal>.  To obtain information on the element
-   type of the array, you can join the respective view with this view.
-   For example, to show the columns of a table with data types and
-   array element types, if applicable, you could do:
-<programlisting>
-SELECT c.column_name, c.data_type, e.data_type AS element_type
-FROM information_schema.columns c LEFT JOIN information_schema.element_types e
-     ON ((c.table_catalog, c.table_schema, c.table_name, 'TABLE', c.dtd_identifier)
-       = (e.object_catalog, e.object_schema, e.object_name, e.object_type, e.dtd_identifier))
-WHERE c.table_schema = '...' AND c.table_name = '...'
-ORDER BY c.ordinal_position;
-</programlisting>
-   This view only includes objects that the current user has access
-   to, by way of being the owner or having some privilege.
-  </para>
-
-  <table>
-   <title><literal>element_types</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>object_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that contains the object that uses the
-       array being described (always the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>object_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that contains the object that uses the array
-       being described
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>object_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the object that uses the array being described
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>object_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       The type of the object that uses the array being described: one
-       of <literal>TABLE</literal> (the array is used by a column of
-       that table), <literal>DOMAIN</literal> (the array is used by
-       that domain), <literal>ROUTINE</literal> (the array is used by
-       a parameter or the return data type of that function).
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>dtd_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       The identifier of the data type descriptor of the array being
-       described
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>data_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Data type of the array elements, if it is a built-in type, else
-       <literal>USER-DEFINED</literal> (in that case, the type is
-       identified in <literal>udt_name</literal> and associated
-       columns).
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_maximum_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_octet_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision_radix</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>numeric_scale</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>datetime_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>interval_type</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>interval_precision</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to array element data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>domain_default</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Not yet implemented</entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that the data type of the elements is
-       defined in (always the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that the data type of the elements is
-       defined in
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the data type of the elements
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>scope_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>maximum_cardinality</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-enabled-roles">
-  <title><literal>enabled_roles</literal></title>
-&common;
-  <para>
-   The view <literal>enabled_roles</literal> identifies the currently
-   <quote>enabled roles</quote>.  The enabled roles are recursively
-   defined as the current user together with all roles that have been
-   granted to the enabled roles with automatic inheritance.  In other
-   words, these are all roles that the current user has direct or
-   indirect, automatically inheriting membership in.
-   <indexterm><primary>enabled role</primary></indexterm>
-   <indexterm><primary>role</primary><secondary>enabled</secondary></indexterm>
-  </para>
-
-  <para>
-   For permission checking, the set of <quote>applicable roles</quote>
-   is applied, which can be broader than the set of enabled roles.  So
-   generally, it is better to use the view
-   <literal>applicable_roles</literal> instead of this one; see also
-   there.
-  </para>
-
-  <table>
-   <title><literal>enabled_roles</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>role_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of a role</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-foreign-data-wrapper-options">
-  <title><literal>foreign_data_wrapper_options</literal></title>
-&common;
-  <para>
-   The view <literal>foreign_data_wrapper_options</literal> contains
-   all the options defined for foreign-data wrappers in the current
-   database.  Only those foreign-data wrappers are shown that the
-   current user has access to (by way of being the owner or having
-   some privilege).
-  </para>
-
-  <table>
-   <title><literal>foreign_data_wrapper_options</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>foreign_data_wrapper_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the foreign-data wrapper is defined in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_data_wrapper_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign-data wrapper</entry>
-     </row>
-
-     <row>
-      <entry><literal>option_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of an option</entry>
-     </row>
-
-     <row>
-      <entry><literal>option_value</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Value of the option</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-foreign-data-wrappers">
-  <title><literal>foreign_data_wrappers</literal></title>
-&common;
-  <para>
-   The view <literal>foreign_data_wrappers</literal> contains all
-   foreign-data wrappers defined in the current database.  Only those
-   foreign-data wrappers are shown that the current user has access to
-   (by way of being the owner or having some privilege).
-  </para>
-
-  <table>
-   <title><literal>foreign_data_wrappers</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>foreign_data_wrapper_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the foreign-data
-      wrapper (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_data_wrapper_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign-data wrapper</entry>
-     </row>
-
-     <row>
-      <entry><literal>authorization_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the owner of the foreign server</entry>
-     </row>
-
-     <row>
-      <entry><literal>library_name</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>File name of the library that implementing this foreign-data wrapper</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_data_wrapper_language</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Language used to implement this foreign-data wrapper</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-foreign-server-options">
-  <title><literal>foreign_server_options</literal></title>
-&common;
-  <para>
-   The view <literal>foreign_server_options</literal> contains all the
-   options defined for foreign servers in the current database.  Only
-   those foreign servers are shown that the current user has access to
-   (by way of being the owner or having some privilege).
-  </para>
-
-  <table>
-   <title><literal>foreign_server_options</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>foreign_server_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the foreign server is defined in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign server</entry>
-     </row>
-
-     <row>
-      <entry><literal>option_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of an option</entry>
-     </row>
-
-     <row>
-      <entry><literal>option_value</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Value of the option</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-foreign-servers">
-  <title><literal>foreign_servers</literal></title>
-&common;
-  <para>
-   The view <literal>foreign_servers</literal> contains all foreign
-   servers defined in the current database.  Only those foreign
-   servers are shown that the current user has access to (by way of
-   being the owner or having some privilege).
-  </para>
-
-  <table>
-   <title><literal>foreign_servers</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>foreign_server_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the foreign server is defined in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign server</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_data_wrapper_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the foreign-data
-      wrapper used by the foreign server (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_data_wrapper_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign-data wrapper used by the foreign server</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Foreign server type information, if specified upon creation</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_version</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Foreign server version information, if specified upon creation</entry>
-     </row>
-
-     <row>
-      <entry><literal>authorization_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the owner of the foreign server</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-foreign-table-options">
-  <title><literal>foreign_table_options</literal></title>
-
-  <para>
-   The view <literal>foreign_table_options</literal> contains all the
-   options defined for foreign tables in the current database.  Only
-   those foreign tables are shown that the current user has access to
-   (by way of being the owner or having some privilege).
-  </para>
-
-  <table>
-   <title><literal>foreign_table_options</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>foreign_table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the foreign table (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the foreign table</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign table</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the foreign server is defined in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign server</entry>
-     </row>
-
-     <row>
-      <entry><literal>option_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of an option</entry>
-     </row>
-
-     <row>
-      <entry><literal>option_value</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Value of the option</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-foreign-tables">
-  <title><literal>foreign_tables</literal></title>
-
-  <para>
-   The view <literal>foreign_tables</literal> contains all foreign
-   tables defined in the current database.  Only those foreign
-   tables are shown that the current user has access to (by way of
-   being the owner or having some privilege).
-  </para>
-
-  <table>
-   <title><literal>foreign_tables</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>foreign_table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the foreign table is defined in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the foreign table</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign table</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the foreign server is defined in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign server</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-key-column-usage">
-  <title><literal>key_column_usage</literal></title>
-&common;
-  <para>
-   The view <literal>key_column_usage</literal> identifies all columns
-   in the current database that are restricted by some unique, primary
-   key, or foreign key constraint.  Check constraints are not included
-   in this view.  Only those columns are shown that the current user
-   has access to, by way of being the owner or having some privilege.
-  </para>
-
-  <table>
-   <title><literal>key_column_usage</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>constraint_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the constraint (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that contains the table that contains the
-       column that is restricted by this constraint (always the
-       current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that contains the table that contains the
-       column that is restricted by this constraint
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the table that contains the column that is restricted
-       by this constraint
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>column_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the column that is restricted by this constraint
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>ordinal_position</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       Ordinal position of the column within the constraint key (count
-       starts at 1)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>position_in_unique_constraint</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       For a foreign-key constraint, ordinal position of the referenced
-       column within its unique constraint (count starts at 1);
-       otherwise null
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-parameters">
-  <title><literal>parameters</literal></title>
-&common;
-  <para>
-   The view <literal>parameters</literal> contains information about
-   the parameters (arguments) of all functions in the current database.
-   Only those functions are shown that the current user has access to
-   (by way of being the owner or having some privilege).
-  </para>
-
-  <table>
-   <title><literal>parameters</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>specific_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the function (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the function</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       The <quote>specific name</quote> of the function.  See <xref
-       linkend="infoschema-routines"> for more information.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>ordinal_position</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       Ordinal position of the parameter in the argument list of the
-       function (count starts at 1)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>parameter_mode</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       <literal>IN</literal> for input parameter,
-       <literal>OUT</literal> for output parameter,
-       and <literal>INOUT</literal> for input/output parameter.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_result</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>as_locator</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>parameter_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the parameter, or null if the parameter has no name</entry>
-     </row>
-
-     <row>
-      <entry><literal>data_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Data type of the parameter, if it is a built-in type, or
-       <literal>ARRAY</literal> if it is some array (in that case, see
-       the view <literal>element_types</literal>), else
-       <literal>USER-DEFINED</literal> (in that case, the type is
-       identified in <literal>udt_name</literal> and associated
-       columns).
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_maximum_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_octet_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision_radix</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>numeric_scale</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>datetime_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>interval_type</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>interval_precision</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to parameter data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that the data type of the parameter is
-       defined in (always the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that the data type of the parameter is
-       defined in
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the data type of the parameter
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>scope_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>maximum_cardinality</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>dtd_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       An identifier of the data type descriptor of the parameter,
-       unique among the data type descriptors pertaining to the
-       function.  This is mainly useful for joining with other
-       instances of such identifiers.  (The specific format of the
-       identifier is not defined and not guaranteed to remain the same
-       in future versions.)
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-referential-constraints">
-  <title><literal>referential_constraints</literal></title>
-&common;
-  <para>
-   The view <literal>referential_constraints</literal> contains all
-   referential (foreign key) constraints in the current database.
-   Only those constraints are shown for which the current user has
-   write access to the referencing table (by way of being the
-   owner or having some privilege other than SELECT).
-  </para>
-
-  <table>
-   <title><literal>referential_constraints</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>constraint_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the database containing the constraint (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the schema containing the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>unique_constraint_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>
-       Name of the database that contains the unique or primary key
-       constraint that the foreign key constraint references (always
-       the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>unique_constraint_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>
-       Name of the schema that contains the unique or primary key
-       constraint that the foreign key constraint references
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>unique_constraint_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>
-       Name of the unique or primary key constraint that the foreign
-       key constraint references
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>match_option</literal></entry>
-      <entry><literal>character_data</literal></entry>
-      <entry>
-       Match option of the foreign key constraint:
-       <literal>FULL</literal>, <literal>PARTIAL</literal>, or
-       <literal>NONE</literal>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>update_rule</literal></entry>
-      <entry><literal>character_data</literal></entry>
-      <entry>
-       Update rule of the foreign key constraint:
-       <literal>CASCADE</literal>, <literal>SET NULL</literal>,
-       <literal>SET DEFAULT</literal>, <literal>RESTRICT</literal>, or
-       <literal>NO ACTION</literal>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>delete_rule</literal></entry>
-      <entry><literal>character_data</literal></entry>
-      <entry>
-       Delete rule of the foreign key constraint:
-       <literal>CASCADE</literal>, <literal>SET NULL</literal>,
-       <literal>SET DEFAULT</literal>, <literal>RESTRICT</literal>, or
-       <literal>NO ACTION</literal>.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
- <sect1 id="infoschema-role-column-grants">
-  <title><literal>role_column_grants</literal></title>
-&common;
-  <para>
-   The view <literal>role_column_grants</literal> identifies all
-   privileges granted on columns where the grantor or grantee is a
-   currently enabled role.  Further information can be found under
-   <literal>column_privileges</literal>.  The only effective
-   difference between this view
-   and <literal>column_privileges</literal> is that this view omits
-   columns that have been made accessible to the current user by way
-   of a grant to public.
-  </para>
-
-  <table>
-   <title><literal>role_column_grants</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>grantor</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that granted the privilege</entry>
-     </row>
-
-     <row>
-      <entry><literal>grantee</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that the privilege was granted to</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the table that contains the column (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the table that contains the column</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table that contains the column</entry>
-     </row>
-
-     <row>
-      <entry><literal>column_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the column</entry>
-     </row>
-
-     <row>
-      <entry><literal>privilege_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Type of the privilege: <literal>SELECT</literal>,
-       <literal>INSERT</literal>, <literal>UPDATE</literal>, or
-       <literal>REFERENCES</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_grantable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the privilege is grantable, <literal>NO</literal> if not</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-role-routine-grants">
-  <title><literal>role_routine_grants</literal></title>
-
-&common;
-  <para>
-   The view <literal>role_routine_grants</literal> identifies all
-   privileges granted on functions where the grantor or grantee is a
-   currently enabled role.  Further information can be found under
-   <literal>routine_privileges</literal>.  The only effective
-   difference between this view
-   and <literal>routine_privileges</literal> is that this view omits
-   functions that have been made accessible to the current user by way
-   of a grant to public.
-  </para>
-
-  <table>
-   <title><literal>role_routine_grants</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>grantor</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that granted the privilege</entry>
-     </row>
-
-     <row>
-      <entry><literal>grantee</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that the privilege was granted to</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the function (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the function</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       The <quote>specific name</quote> of the function.  See <xref
-       linkend="infoschema-routines"> for more information.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the function (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the function</entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the function (might be duplicated in case of overloading)</entry>
-     </row>
-
-     <row>
-      <entry><literal>privilege_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Always <literal>EXECUTE</literal> (the only privilege type for functions)</entry>
-     </row>
-
-     <row>
-      <entry><literal>is_grantable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the privilege is grantable, <literal>NO</literal> if not</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-role-table-grants">
-  <title><literal>role_table_grants</literal></title>
-
-&common;
-  <para>
-   The view <literal>role_table_grants</literal> identifies all
-   privileges granted on tables or views where the grantor or grantee
-   is a currently enabled role.  Further information can be found
-   under <literal>table_privileges</literal>.  The only effective
-   difference between this view
-   and <literal>table_privileges</literal> is that this view omits
-   tables that have been made accessible to the current user by way of
-   a grant to public.
-  </para>
-
-  <table>
-   <title><literal>role_table_grants</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>grantor</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that granted the privilege</entry>
-     </row>
-
-     <row>
-      <entry><literal>grantee</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that the privilege was granted to</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the table (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>privilege_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Type of the privilege: <literal>SELECT</literal>,
-       <literal>INSERT</literal>, <literal>UPDATE</literal>,
-       <literal>DELETE</literal>, <literal>TRUNCATE</literal>,
-       <literal>REFERENCES</literal>, or <literal>TRIGGER</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_grantable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the privilege is grantable, <literal>NO</literal> if not</entry>
-     </row>
-
-     <row>
-      <entry><literal>with_hierarchy</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-role-usage-grants">
-  <title><literal>role_usage_grants</literal></title>
-
-&common;
-  <para>
-   The view <literal>role_usage_grants</literal> identifies
-   <literal>USAGE</literal> privileges granted on various kinds of
-   objects where the grantor or grantee is a currently enabled role.
-   Further information can be found under
-   <literal>usage_privileges</literal>.  The only effective difference
-   between this view and <literal>usage_privileges</literal> is that
-   this view omits objects that have been made accessible to the
-   current user by way of a grant to public.
-  </para>
-
-  <table>
-   <title><literal>role_usage_grants</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>grantor</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>The name of the role that granted the privilege</entry>
-     </row>
-
-     <row>
-      <entry><literal>grantee</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>The name of the role that the privilege was granted to</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the object (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the object, if applicable,
-      else an empty string</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the object</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry><literal>COLLATION</literal> or <literal>DOMAIN</literal> or <literal>FOREIGN DATA WRAPPER</literal> or <literal>FOREIGN SERVER</literal></entry>
-     </row>
-
-     <row>
-      <entry><literal>privilege_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Always <literal>USAGE</literal></entry>
-     </row>
-
-     <row>
-      <entry><literal>is_grantable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the privilege is grantable, <literal>NO</literal> if not</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-routine-privileges">
-  <title><literal>routine_privileges</literal></title>
-
-&common;
-  <para>
-   The view <literal>routine_privileges</literal> identifies all
-   privileges granted on functions to a currently enabled role or by a
-   currently enabled role.  There is one row for each combination of function,
-   grantor, and grantee.
-  </para>
-
-  <table>
-   <title><literal>routine_privileges</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>grantor</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that granted the privilege</entry>
-     </row>
-
-     <row>
-      <entry><literal>grantee</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that the privilege was granted to</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the function (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the function</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       The <quote>specific name</quote> of the function.  See <xref
-       linkend="infoschema-routines"> for more information.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the function (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the function</entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the function (might be duplicated in case of overloading)</entry>
-     </row>
-
-     <row>
-      <entry><literal>privilege_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Always <literal>EXECUTE</literal> (the only privilege type for functions)</entry>
-     </row>
-
-     <row>
-      <entry><literal>is_grantable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the privilege is grantable, <literal>NO</literal> if not</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-routines">
-  <title><literal>routines</literal></title>
-
-&common;
-  <para>
-   The view <literal>routines</literal> contains all functions in the
-   current database.  Only those functions are shown that the current
-   user has access to (by way of being the owner or having some
-   privilege).
-  </para>
-
-  <table>
-   <title><literal>routines</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>specific_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the function (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the function</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       The <quote>specific name</quote> of the function.  This is a
-       name that uniquely identifies the function in the schema, even
-       if the real name of the function is overloaded.  The format of
-       the specific name is not defined, it should only be used to
-       compare it to other instances of specific routine names.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the function (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the function</entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the function (might be duplicated in case of overloading)</entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Always <literal>FUNCTION</literal> (In the future there might
-       be other types of routines.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>module_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>module_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>module_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>data_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Return data type of the function, if it is a built-in type, or
-       <literal>ARRAY</literal> if it is some array (in that case, see
-       the view <literal>element_types</literal>), else
-       <literal>USER-DEFINED</literal> (in that case, the type is
-       identified in <literal>type_udt_name</literal> and associated
-       columns).
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_maximum_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_octet_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>character_set_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>collation_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision_radix</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>numeric_scale</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>datetime_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>interval_type</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>interval_precision</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, since this information is not applied to return data types in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>type_udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that the return data type of the function
-       is defined in (always the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>type_udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that the return data type of the function is
-       defined in
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>type_udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the return data type of the function
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>scope_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>scope_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>maximum_cardinality</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>dtd_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       An identifier of the data type descriptor of the return data
-       type of this function, unique among the data type descriptors
-       pertaining to the function.  This is mainly useful for joining
-       with other instances of such identifiers.  (The specific format
-       of the identifier is not defined and not guaranteed to remain
-       the same in future versions.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_body</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       If the function is an SQL function, then
-       <literal>SQL</literal>, else <literal>EXTERNAL</literal>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>routine_definition</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       The source text of the function (null if the function is not
-       owned by a currently enabled role).  (According to the SQL
-       standard, this column is only applicable if
-       <literal>routine_body</literal> is <literal>SQL</literal>, but
-<!## PG>
-       in <productname>PostgreSQL</productname> it will contain
-<!## end>
-<!## XC>
-       in <productname>Postgres-XC</productname> it will contain
-<!## end>
-<!## XL>
-       in <productname>Postgres-XL</productname> it will contain
-<!## end>
-       whatever source text was specified when the function was
-       created.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>external_name</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       If this function is a C function, then the external name (link
-       symbol) of the function; else null.  (This works out to be the
-       same value that is shown in
-       <literal>routine_definition</literal>.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>external_language</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>The language the function is written in</entry>
-     </row>
-
-     <row>
-      <entry><literal>parameter_style</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Always <literal>GENERAL</literal> (The SQL standard defines
-<!## PG>
-       other parameter styles, which are not available in <productname>PostgreSQL</>.)
-<!## end>
-<!## XC>
-       other parameter styles, which are not available in <productname>Postgres-XC</>.)
-<!## end>
-<!## XL>
-       other parameter styles, which are not available in <productname>Postgres-XL</>.)
-<!## end>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_deterministic</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       If the function is declared immutable (called deterministic in
-       the SQL standard), then <literal>YES</literal>, else
-       <literal>NO</literal>.  (You cannot query the other volatility
-<!## PG>
-       levels available in <productname>PostgreSQL</> through the information schema.)
-<!## end>
-<!## XC>
-       levels available in <productname>Postgres-XC</> through the information schema.)
-<!## end>
-<!## XL>
-       levels available in <productname>Postgres-XL</> through the information schema.)
-<!## end>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>sql_data_access</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Always <literal>MODIFIES</literal>, meaning that the function
-       possibly modifies SQL data.  This information is not useful for
-<!## PG>
-       <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</>.
-<!## end>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_null_call</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       If the function automatically returns null if any of its
-       arguments are null, then <literal>YES</literal>, else
-       <literal>NO</literal>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>sql_path</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>schema_level_routine</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       Always <literal>YES</literal> (The opposite would be a method
-       of a user-defined type, which is a feature not available in
-<!## PG>
-       <productname>PostgreSQL</>.)
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</>.)
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</>.)
-<!## end>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>max_dynamic_result_sets</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>is_user_defined_cast</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>is_implicitly_invocable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>security_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       If the function runs with the privileges of the current user,
-       then <literal>INVOKER</literal>, if the function runs with the
-       privileges of the user who defined it, then
-       <literal>DEFINER</literal>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>to_sql_specific_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>to_sql_specific_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>to_sql_specific_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>as_locator</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>created</literal></entry>
-      <entry><type>time_stamp</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>last_altered</literal></entry>
-      <entry><type>time_stamp</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>new_savepoint_level</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>is_udt_dependent</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_from_data_type</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_as_locator</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_char_max_length</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_char_octet_length</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_char_set_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_char_set_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_char_set_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_collation_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_collation_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_collation_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_numeric_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_numeric_precision_radix</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_numeric_scale</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_datetime_precision</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_interval_type</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_interval_precision</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_type_udt_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_type_udt_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_type_udt_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_scope_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_scope_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_scope_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_maximum_cardinality</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>result_cast_dtd_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-schemata">
-  <title><literal>schemata</literal></title>
-
-&common;
-  <para>
-   The view <literal>schemata</literal> contains all schemas in the
-   current database that are owned by a currently enabled role.
-  </para>
-
-  <table>
-   <title><literal>schemata</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>catalog_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the schema is contained in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>schema_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema</entry>
-     </row>
-
-     <row>
-      <entry><literal>schema_owner</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the owner of the schema</entry>
-     </row>
-
-     <row>
-      <entry><literal>default_character_set_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>default_character_set_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>default_character_set_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>sql_path</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-sequences">
-  <title><literal>sequences</literal></title>
-
-&common;
-  <para>
-   The view <literal>sequences</literal> contains all sequences
-   defined in the current database.  Only those sequences are shown
-   that the current user has access to (by way of being the owner or
-   having some privilege).
-  </para>
-
-  <table>
-   <title><literal>sequences</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>sequence_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the sequence (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>sequence_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the sequence</entry>
-     </row>
-
-     <row>
-      <entry><literal>sequence_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the sequence</entry>
-     </row>
-
-     <row>
-      <entry><literal>data_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       The data type of the sequence.  In
-<!## PG>
-       <productname>PostgreSQL</productname>, this is currently always
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</productname>, this is currently always
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</productname>, this is currently always
-<!## end>
-       <literal>bigint</literal>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       This column contains the (declared or implicit) precision of
-       the sequence data type (see above).  The precision indicates
-       the number of significant digits.  It can be expressed in
-       decimal (base 10) or binary (base 2) terms, as specified in the
-       column <literal>numeric_precision_radix</literal>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_precision_radix</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       This column indicates in which base the values in the columns
-       <literal>numeric_precision</literal> and
-       <literal>numeric_scale</literal> are expressed.  The value is
-       either 2 or 10.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>numeric_scale</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       This column contains the (declared or implicit) scale of the
-       sequence data type (see above).  The scale indicates the number
-       of significant digits to the right of the decimal point.  It
-       can be expressed in decimal (base 10) or binary (base 2) terms,
-       as specified in the column
-       <literal>numeric_precision_radix</literal>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>start_value</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>The start value of the sequence</entry>
-     </row>
-
-     <row>
-      <entry><literal>minimum_value</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>The minimum value of the sequence</entry>
-     </row>
-
-     <row>
-      <entry><literal>maximum_value</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>The maximum value of the sequence</entry>
-     </row>
-
-     <row>
-      <entry><literal>increment</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>The increment of the sequence</entry>
-     </row>
-
-     <row>
-      <entry><literal>cycle_option</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the sequence cycles, else <literal>NO</literal></entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Note that in accordance with the SQL standard, the start, minimum,
-   maximum, and increment values are returned as character strings.
-  </para>
- </sect1>
-
- <sect1 id="infoschema-sql-features">
-  <title><literal>sql_features</literal></title>
-
-&common;
-  <para>
-   The table <literal>sql_features</literal> contains information
-   about which formal features defined in the SQL standard are
-<!## PG>
-   supported by <productname>PostgreSQL</productname>.  This is the
-<!## end>
-<!## XC>
-   supported by <productname>Postgres-XC</productname>.  This is the
-<!## end>
-<!## XL>
-   supported by <productname>Postgres-XL</productname>.  This is the
-<!## end>
-   same information that is presented in <xref linkend="features">.
-   There you can also find some additional background information.
-  </para>
-
-  <table>
-   <title><literal>sql_features</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>feature_id</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Identifier string of the feature</entry>
-     </row>
-
-     <row>
-      <entry><literal>feature_name</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Descriptive name of the feature</entry>
-     </row>
-
-     <row>
-      <entry><literal>sub_feature_id</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Identifier string of the subfeature, or a zero-length string if not a subfeature</entry>
-     </row>
-
-     <row>
-      <entry><literal>sub_feature_name</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Descriptive name of the subfeature, or a zero-length string if not a subfeature</entry>
-     </row>
-
-     <row>
-      <entry><literal>is_supported</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</literal> if the feature is fully supported by the
-<!## PG>
-       current version of <productname>PostgreSQL</>, <literal>NO</literal> if not
-<!## end>
-<!## XC>
-       current version of <productname>Postgres-XC</>, <literal>NO</literal> if not
-<!## end>
-<!## XL>
-       current version of <productname>Postgres-XL</>, <literal>NO</literal> if not
-<!## end>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_verified_by</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-<!## PG>
-       Always null, since the <productname>PostgreSQL</> development group does not
-<!## end>
-<!## XC>
-       Always null, since the <productname>Postgres-XC</> development group does not
-<!## end>
-<!## XL>
-       Always null, since the <productname>Postgres-XL</> development group does not
-<!## end>
-       perform formal testing of feature conformance
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>comments</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Possibly a comment about the supported status of the feature</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-sql-implementation-info">
-  <title><literal>sql_implementation_info</literal></title>
-
-&common;
-  <para>
-   The table <literal>sql_implementation_info</literal> contains
-   information about various aspects that are left
-   implementation-defined by the SQL standard.  This information is
-   primarily intended for use in the context of the ODBC interface;
-   users of other interfaces will probably find this information to be
-   of little use.  For this reason, the individual implementation
-   information items are not described here; you will find them in the
-   description of the ODBC interface.
-  </para>
-
-  <table>
-   <title><literal>sql_implementation_info</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>implementation_info_id</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Identifier string of the implementation information item</entry>
-     </row>
-
-     <row>
-      <entry><literal>implementation_info_name</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Descriptive name of the implementation information item</entry>
-     </row>
-
-     <row>
-      <entry><literal>integer_value</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       Value of the implementation information item, or null if the
-       value is contained in the column
-       <literal>character_value</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>character_value</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Value of the implementation information item, or null if the
-       value is contained in the column
-       <literal>integer_value</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>comments</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Possibly a comment pertaining to the implementation information item</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-sql-languages">
-  <title><literal>sql_languages</literal></title>
-
-&common;
-  <para>
-   The table <literal>sql_languages</literal> contains one row for
-   each SQL language binding that is supported by
-<!## PG>
-   <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>.
-<!## end>
-<!## PG>
-   <productname>PostgreSQL</productname> supports direct SQL and
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> supports direct SQL and
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> supports direct SQL and
-<!## end>
-   embedded SQL in C; that is all you will learn from this table.
-  </para>
-
-  <table>
-   <title><literal>sql_languages</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>sql_language_source</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       The name of the source of the language definition; always
-       <literal>ISO 9075</literal>, that is, the SQL standard
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>sql_language_year</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       The year the standard referenced in
-       <literal>sql_language_source</literal> was approved; currently
-       <literal>2003</>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>sql_language_conformance</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       The standard conformance level for the language binding.  For
-       ISO 9075:2003 this is always <literal>CORE</literal>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>sql_language_integrity</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Always null (This value is relevant to an earlier version of the SQL standard.)</entry>
-     </row>
-
-     <row>
-      <entry><literal>sql_language_implementation</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Always null</entry>
-     </row>
-
-     <row>
-      <entry><literal>sql_language_binding_style</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       The language binding style, either <literal>DIRECT</literal> or
-       <literal>EMBEDDED</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>sql_language_programming_language</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       The programming language, if the binding style is
-<!## PG>
-       <literal>EMBEDDED</literal>, else null.  <productname>PostgreSQL</> only
-<!## end>
-<!## XC>
-       <literal>EMBEDDED</literal>, else null.  <productname>Postgres-XC</> only
-<!## end>
-<!## XL>
-       <literal>EMBEDDED</literal>, else null.  <productname>Postgres-XL</> only
-<!## end>
-       supports the language C.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-sql-packages">
-  <title><literal>sql_packages</literal></title>
-
-&common;
-  <para>
-   The table <literal>sql_packages</literal> contains information
-   about which feature packages defined in the SQL standard are
-<!## PG>
-   supported by <productname>PostgreSQL</productname>.  Refer to <xref
-<!## end>
-<!## XC>
-   supported by <productname>Postgres-XC</productname>.  Refer to <xref
-<!## end>
-<!## XL>
-   supported by <productname>Postgres-XL</productname>.  Refer to <xref
-<!## end>
-   linkend="features"> for background information on feature packages.
-  </para>
-
-  <table>
-   <title><literal>sql_packages</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>feature_id</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Identifier string of the package</entry>
-     </row>
-
-     <row>
-      <entry><literal>feature_name</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Descriptive name of the package</entry>
-     </row>
-
-     <row>
-      <entry><literal>is_supported</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</literal> if the package is fully supported by the
-<!## PG>
-       current version of <productname>PostgreSQL</>, <literal>NO</literal> if not
-<!## end>
-<!## XC>
-       current version of <productname>Postgres-XC</>, <literal>NO</literal> if not
-<!## end>
-<!## XL>
-       current version of <productname>Postgres-XL</>, <literal>NO</literal> if not
-<!## end>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_verified_by</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-<!## PG>
-       Always null, since the <productname>PostgreSQL</> development group does not
-<!## end>
-<!## XC>
-       Always null, since the <productname>Postgres-XC</> development group does not
-<!## end>
-<!## XL>
-       Always null, since the <productname>Postgres-XL</> development group does not
-<!## end>
-       perform formal testing of feature conformance
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>comments</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Possibly a comment about the supported status of the package</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-sql-parts">
-  <title><literal>sql_parts</literal></title>
-
-&common;
-  <para>
-   The table <literal>sql_parts</literal> contains information about
-   which of the several parts of the SQL standard are supported by
-<!## PG>
-   <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>.
-<!## end>
-  </para>
-
-  <table>
-   <title><literal>sql_parts</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>feature_id</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>An identifier string containing the number of the part</entry>
-     </row>
-
-     <row>
-      <entry><literal>feature_name</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Descriptive name of the part</entry>
-     </row>
-
-     <row>
-      <entry><literal>is_supported</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</literal> if the part is fully supported by the
-<!## PG>
-       current version of <productname>PostgreSQL</>,
-<!## end>
-<!## XC>
-       current version of <productname>Postgres-XC</>,
-<!## end>
-<!## XL>
-       current version of <productname>Postgres-XL</>,
-<!## end>
-       <literal>NO</literal> if not
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_verified_by</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-<!## PG>
-       Always null, since the <productname>PostgreSQL</> development group does not
-<!## end>
-<!## XC>
-       Always null, since the <productname>Postgres-XC</> development group does not
-<!## end>
-<!## XL>
-       Always null, since the <productname>Postgres-XL</> development group does not
-<!## end>
-       perform formal testing of feature conformance
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>comments</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Possibly a comment about the supported status of the part</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-sql-sizing">
-  <title><literal>sql_sizing</literal></title>
-
-&common;
-  <para>
-   The table <literal>sql_sizing</literal> contains information about
-   various size limits and maximum values in
-<!## PG>
-   <productname>PostgreSQL</productname>.  This information is
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>.  This information is
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>.  This information is
-<!## end>
-   primarily intended for use in the context of the ODBC interface;
-   users of other interfaces will probably find this information to be
-   of little use.  For this reason, the individual sizing items are
-   not described here; you will find them in the description of the
-   ODBC interface.
-  </para>
-
-  <table>
-   <title><literal>sql_sizing</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>sizing_id</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>Identifier of the sizing item</entry>
-     </row>
-
-     <row>
-      <entry><literal>sizing_name</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Descriptive name of the sizing item</entry>
-     </row>
-
-     <row>
-      <entry><literal>supported_value</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       Value of the sizing item, or 0 if the size is unlimited or
-       cannot be determined, or null if the features for which the
-       sizing item is applicable are not supported
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>comments</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Possibly a comment pertaining to the sizing item</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-sql-sizing-profiles">
-  <title><literal>sql_sizing_profiles</literal></title>
-
-&common;
-  <para>
-   The table <literal>sql_sizing_profiles</literal> contains
-   information about the <literal>sql_sizing</literal> values that are
-<!## PG>
-   required by various profiles of the SQL standard.  <productname>PostgreSQL</> does
-<!## end>
-<!## XC>
-   required by various profiles of the SQL standard.  <productname>Postgres-XC</> does
-<!## end>
-<!## XL>
-   required by various profiles of the SQL standard.  <productname>Postgres-XL</> does
-<!## end>
-   not track any SQL profiles, so this table is empty.
-  </para>
-
-  <table>
-   <title><literal>sql_sizing_profiles</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>sizing_id</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>Identifier of the sizing item</entry>
-     </row>
-
-     <row>
-      <entry><literal>sizing_name</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Descriptive name of the sizing item</entry>
-     </row>
-
-     <row>
-      <entry><literal>profile_id</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Identifier string of a profile</entry>
-     </row>
-
-     <row>
-      <entry><literal>required_value</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>
-       The value required by the SQL profile for the sizing item, or 0
-       if the profile places no limit on the sizing item, or null if
-       the profile does not require any of the features for which the
-       sizing item is applicable
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>comments</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Possibly a comment pertaining to the sizing item within the profile</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-table-constraints">
-  <title><literal>table_constraints</literal></title>
-
-&common;
-  <para>
-   The view <literal>table_constraints</literal> contains all
-   constraints belonging to tables that the current user owns or has
-   some non-SELECT privilege on.
-  </para>
-
-  <table>
-   <title><literal>table_constraints</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>constraint_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the constraint (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the constraint</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the table (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>constraint_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Type of the constraint: <literal>CHECK</literal>,
-       <literal>FOREIGN KEY</literal>, <literal>PRIMARY KEY</literal>,
-       or <literal>UNIQUE</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_deferrable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the constraint is deferrable, <literal>NO</literal> if not</entry>
-     </row>
-
-     <row>
-      <entry><literal>initially_deferred</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the constraint is deferrable and initially deferred, <literal>NO</literal> if not</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-table-privileges">
-  <title><literal>table_privileges</literal></title>
-
-&common;
-  <para>
-   The view <literal>table_privileges</literal> identifies all
-   privileges granted on tables or views to a currently enabled role
-   or by a currently enabled role.  There is one row for each
-   combination of table, grantor, and grantee.
-  </para>
-
-  <table>
-   <title><literal>table_privileges</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>grantor</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that granted the privilege</entry>
-     </row>
-
-     <row>
-      <entry><literal>grantee</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that the privilege was granted to</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the table (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>privilege_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Type of the privilege: <literal>SELECT</literal>,
-       <literal>INSERT</literal>, <literal>UPDATE</literal>,
-       <literal>DELETE</literal>, <literal>TRUNCATE</literal>,
-       <literal>REFERENCES</literal>, or <literal>TRIGGER</literal>
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_grantable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the privilege is grantable, <literal>NO</literal> if not</entry>
-     </row>
-
-     <row>
-      <entry><literal>with_hierarchy</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-tables">
-  <title><literal>tables</literal></title>
-
-&common;
-  <para>
-   The view <literal>tables</literal> contains all tables and views
-   defined in the current database.  Only those tables and views are
-   shown that the current user has access to (by way of being the
-   owner or having some privilege).
-  </para>
-
-  <table>
-   <title><literal>tables</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the table (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Type of the table: <literal>BASE TABLE</literal> for a
-       persistent base table (the normal table type),
-       <literal>VIEW</literal> for a view, <literal>FOREIGN TABLE</literal>
-       for a foreign table, or
-       <literal>LOCAL TEMPORARY</literal> for a temporary table
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>self_referencing_column_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>reference_generation</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>user_defined_type_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       If the table is a typed table, the name of the database that
-       contains the underlying data type (always the current
-       database), else null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>user_defined_type_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       If the table is a typed table, the name of the schema that
-       contains the underlying data type, else null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>user_defined_type_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       If the table is a typed table, the name of the underlying data
-       type, else null.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_insertable_into</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</literal> if the table is insertable into,
-       <literal>NO</literal> if not (Base tables are always insertable
-       into, views not necessarily.)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_typed</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the table is a typed table, <literal>NO</literal> if not</entry>
-     </row>
-
-     <row>
-      <entry><literal>commit_action</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       If the table is a temporary table, then
-       <literal>PRESERVE</literal>, else null.  (The SQL standard
-       defines other commit actions for temporary tables, which are
-<!## PG>
-       not supported by <productname>PostgreSQL</>.)
-<!## end>
-<!## XC>
-       not supported by <productname>Postgres-XC</>.)
-<!## end>
-<!## XL>
-       not supported by <productname>Postgres-XL</>.)
-<!## end>
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-triggered-update-columns">
-  <title><literal>triggered_update_columns</literal></title>
-
-&common;
-  <para>
-   For triggers in the current database that specify a column list
-   (like <literal>UPDATE OF column1, column2</literal>), the
-   view <literal>triggered_update_columns</literal> identifies these
-   columns.  Triggers that do not specify a column list are not
-   included in this view.  Only those columns are shown that the
-   current user owns or has some non-SELECT privilege on.
-  </para>
-
-  <table>
-   <title><literal>triggered_update_columns</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>trigger_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the trigger (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>trigger_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the trigger</entry>
-     </row>
-
-     <row>
-      <entry><literal>trigger_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the trigger</entry>
-     </row>
-
-     <row>
-      <entry><literal>event_object_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that contains the table that the trigger
-       is defined on (always the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>event_object_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the table that the trigger is defined on</entry>
-     </row>
-
-     <row>
-      <entry><literal>event_object_table</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table that the trigger is defined on</entry>
-     </row>
-
-     <row>
-      <entry><literal>event_object_column</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the column that the trigger is defined on</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-triggers">
-  <title><literal>triggers</literal></title>
-
-&common;
-  <para>
-   The view <literal>triggers</literal> contains all triggers defined
-   in the current database on tables and views that the current user owns
-   or has some non-SELECT privilege on.
-  </para>
-
-  <table>
-   <title><literal>triggers</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>trigger_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the trigger (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>trigger_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the trigger</entry>
-     </row>
-
-     <row>
-      <entry><literal>trigger_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the trigger</entry>
-     </row>
-
-     <row>
-      <entry><literal>event_manipulation</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Event that fires the trigger (<literal>INSERT</literal>,
-       <literal>UPDATE</literal>, or <literal>DELETE</literal>)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>event_object_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that contains the table that the trigger
-       is defined on (always the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>event_object_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the table that the trigger is defined on</entry>
-     </row>
-
-     <row>
-      <entry><literal>event_object_table</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the table that the trigger is defined on</entry>
-     </row>
-
-     <row>
-      <entry><literal>action_order</literal></entry>
-      <entry><type>cardinal_number</type></entry>
-      <entry>Not yet implemented</entry>
-     </row>
-
-     <row>
-      <entry><literal>action_condition</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       <literal>WHEN</literal> condition of the trigger, null if none
-       (also null if the table is not owned by a currently enabled
-       role)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>action_statement</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Statement that is executed by the trigger (currently always
-       <literal>EXECUTE PROCEDURE
-       <replaceable>function</replaceable>(...)</literal>)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>action_orientation</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Identifies whether the trigger fires once for each processed
-       row or once for each statement (<literal>ROW</literal> or
-       <literal>STATEMENT</literal>)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>action_timing</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Time at which the trigger fires (<literal>BEFORE</literal>,
-       <literal>AFTER</literal>, or <literal>INSTEAD OF</literal>)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>action_reference_old_table</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-     </row>
-
-     <row>
-      <entry><literal>action_reference_new_table</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-     </row>
-
-     <row>
-      <entry><literal>action_reference_old_row</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-     </row>
-
-     <row>
-      <entry><literal>action_reference_new_row</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-     </row>
-
-     <row>
-      <entry><literal>created</literal></entry>
-      <entry><type>time_stamp</type></entry>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-<!## PG>
-<!-- NOTICE: No TRIGGER suport yet!
--->
-  <para>
-   Triggers in <productname>PostgreSQL</productname> have two
-   incompatibilities with the SQL standard that affect the
-   representation in the information schema.  First, trigger names are
-   local to each table in <productname>PostgreSQL</productname>, rather
-   than being independent schema objects.  Therefore there can be duplicate
-   trigger names defined in one schema, so long as they belong to
-   different tables.  (<literal>trigger_catalog</literal> and
-   <literal>trigger_schema</literal> are really the values pertaining
-   to the table that the trigger is defined on.)  Second, triggers can
-   be defined to fire on multiple events in
-   <productname>PostgreSQL</productname> (e.g., <literal>ON INSERT OR
-   UPDATE</literal>), whereas the SQL standard only allows one.  If a
-   trigger is defined to fire on multiple events, it is represented as
-   multiple rows in the information schema, one for each type of
-   event.  As a consequence of these two issues, the primary key of
-   the view <literal>triggers</literal> is really
-   <literal>(trigger_catalog, trigger_schema, event_object_table,
-   trigger_name, event_manipulation)</literal> instead of
-   <literal>(trigger_catalog, trigger_schema, trigger_name)</literal>,
-   which is what the SQL standard specifies.  Nonetheless, if you
-   define your triggers in a manner that conforms with the SQL
-   standard (trigger names unique in the schema and only one event
-   type per trigger), this will not affect you.
-  </para>
-<!## end>
-
-  <note>
-   <para>
-    Prior to <productname>PostgreSQL</> 9.1, this view's columns
-    <structfield>action_timing</structfield>,
-    <structfield>action_reference_old_table</structfield>,
-    <structfield>action_reference_new_table</structfield>,
-    <structfield>action_reference_old_row</structfield>, and
-    <structfield>action_reference_new_row</structfield>
-    were named
-    <structfield>condition_timing</structfield>,
-    <structfield>condition_reference_old_table</structfield>,
-    <structfield>condition_reference_new_table</structfield>,
-    <structfield>condition_reference_old_row</structfield>, and
-    <structfield>condition_reference_new_row</structfield>
-    respectively.
-    That was how they were named in the SQL:1999 standard.
-    The new naming conforms to SQL:2003 and later.
-   </para>
-  </note>
- </sect1>
-
- <sect1 id="infoschema-usage-privileges">
-  <title><literal>usage_privileges</literal></title>
-
-  <para>
-   The view <literal>usage_privileges</literal> identifies
-   <literal>USAGE</literal> privileges granted on various kinds of
-   objects to a currently enabled role or by a currently enabled role.
-<!## PG>
-   In <productname>PostgreSQL</productname>, this currently applies to
-<!## end>
-<!## XC>
-   In <productname>Postgres-XC</productname>, this currently applies to
-<!## end>
-<!## XL>
-   In <productname>Postgres-XL</productname>, this currently applies to
-<!## end>
-   collations, domains, foreign-data wrappers, and foreign servers.  There is one
-   row for each combination of object, grantor, and grantee.
-  </para>
-
-  <para>
-   Since collations and domains do not have real privileges
-<!## PG>
-   in <productname>PostgreSQL</productname>, this view shows implicit
-<!## end>
-<!## XC>
-   in <productname>Postgres-XC</productname>, this view shows implicit
-<!## end>
-<!## XL>
-   in <productname>Postgres-XL</productname>, this view shows implicit
-<!## end>
-   non-grantable <literal>USAGE</literal> privileges granted by the
-   owner to <literal>PUBLIC</literal> for all collations and domains.  The other
-   object types, however, show real privileges.
-  </para>
-
-  <table>
-   <title><literal>usage_privileges</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>grantor</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that granted the privilege</entry>
-     </row>
-
-     <row>
-      <entry><literal>grantee</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the role that the privilege was granted to</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database containing the object (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema containing the object, if applicable,
-      else an empty string</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the object</entry>
-     </row>
-
-     <row>
-      <entry><literal>object_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry><literal>COLLATION</literal> or <literal>DOMAIN</literal> or <literal>FOREIGN DATA WRAPPER</literal> or <literal>FOREIGN SERVER</literal></entry>
-     </row>
-
-     <row>
-      <entry><literal>privilege_type</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Always <literal>USAGE</literal></entry>
-     </row>
-
-     <row>
-      <entry><literal>is_grantable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry><literal>YES</literal> if the privilege is grantable, <literal>NO</literal> if not</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-user-mapping-options">
-  <title><literal>user_mapping_options</literal></title>
-
-&common;
-  <para>
-   The view <literal>user_mapping_options</literal> contains all the
-   options defined for user mappings in the current database.  Only
-   those user mappings are shown where the current user has access to
-   the corresponding foreign server (by way of being the owner or
-   having some privilege).
-  </para>
-
-  <table>
-   <title><literal>user_mapping_options</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>authorization_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the user being mapped,
-      or <literal>PUBLIC</literal> if the mapping is public</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the foreign server used by this
-      mapping is defined in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign server used by this mapping</entry>
-     </row>
-
-     <row>
-      <entry><literal>option_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of an option</entry>
-     </row>
-
-     <row>
-      <entry><literal>option_value</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>Value of the option.  This column will show as null
-      unless the current user is the user being mapped, or the mapping
-      is for <literal>PUBLIC</literal> and the current user is the
-      server owner, or the current user is a superuser.  The intent is
-      to protect password information stored as user mapping
-      option.</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-user-mappings">
-  <title><literal>user_mappings</literal></title>
-
-&common;
-  <para>
-   The view <literal>user_mappings</literal> contains all user
-   mappings defined in the current database.  Only those user mappings
-   are shown where the current user has access to the corresponding
-   foreign server (by way of being the owner or having some
-   privilege).
-  </para>
-
-  <table>
-   <title><literal>user_mappings</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>authorization_identifier</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the user being mapped,
-      or <literal>PUBLIC</literal> if the mapping is public</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that the foreign server used by this
-      mapping is defined in (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>foreign_server_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the foreign server used by this mapping</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-view-column-usage">
-  <title><literal>view_column_usage</literal></title>
-
-&common;
-  <para>
-   The view <literal>view_column_usage</literal> identifies all
-   columns that are used in the query expression of a view (the
-   <command>SELECT</command> statement that defines the view).  A
-   column is only included if the table that contains the column is
-   owned by a currently enabled role.
-  </para>
-
-  <note>
-   <para>
-    Columns of system tables are not included.  This should be fixed
-    sometime.
-   </para>
-  </note>
-
-  <table>
-   <title><literal>view_column_usage</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>view_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the view (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>view_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the view</entry>
-     </row>
-
-     <row>
-      <entry><literal>view_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the view</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that contains the table that contains the
-       column that is used by the view (always the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that contains the table that contains the
-       column that is used by the view
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the table that contains the column that is used by the
-       view
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>column_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the column that is used by the view</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-view-routine-usage">
-  <title><literal>view_routine_usage</literal></title>
-
-&common;
-  <para>
-   The view <literal>view_routine_usage</literal> identifies all
-   routines (functions and procedures) that are used in the query
-   expression of a view (the <command>SELECT</command> statement that
-   defines the view).  A routine is only included if that routine is
-   owned by a currently enabled role.
-  </para>
-
-  <table>
-   <title><literal>view_routine_usage</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the database containing the view (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the schema containing the view</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the view</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_catalog</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the database containing the function (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_schema</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>Name of the schema containing the function</entry>
-     </row>
-
-     <row>
-      <entry><literal>specific_name</literal></entry>
-      <entry><literal>sql_identifier</literal></entry>
-      <entry>
-       The <quote>specific name</quote> of the function.  See <xref
-       linkend="infoschema-routines"> for more information.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-view-table-usage">
-  <title><literal>view_table_usage</literal></title>
-
-&common;
-  <para>
-   The view <literal>view_table_usage</literal> identifies all tables
-   that are used in the query expression of a view (the
-   <command>SELECT</command> statement that defines the view).  A
-   table is only included if that table is owned by a currently
-   enabled role.
-  </para>
-
-  <note>
-   <para>
-    System tables are not included.  This should be fixed sometime.
-   </para>
-  </note>
-
-  <table>
-   <title><literal>view_table_usage</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>view_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the view (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>view_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the view</entry>
-     </row>
-
-     <row>
-      <entry><literal>view_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the view</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the database that contains the table that is
-       used by the view (always the current database)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the schema that contains the table that is used by the
-       view
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>
-       Name of the table that is used by the view
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
- <sect1 id="infoschema-views">
-  <title><literal>views</literal></title>
-
-&common;
-  <para>
-   The view <literal>views</literal> contains all views defined in the
-   current database.  Only those views are shown that the current user
-   has access to (by way of being the owner or having some privilege).
-  </para>
-
-  <table>
-   <title><literal>views</literal> Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>table_catalog</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the database that contains the view (always the current database)</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_schema</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the schema that contains the view</entry>
-     </row>
-
-     <row>
-      <entry><literal>table_name</literal></entry>
-      <entry><type>sql_identifier</type></entry>
-      <entry>Name of the view</entry>
-     </row>
-
-     <row>
-      <entry><literal>view_definition</literal></entry>
-      <entry><type>character_data</type></entry>
-      <entry>
-       Query expression defining the view (null if the view is not
-       owned by a currently enabled role)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>check_option</literal></entry>
-      <entry><type>character_data</type></entry>
-<!## PG>
-      <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
-<!## end>
-<!## XC>
-      <entry>Applies to a feature not available in <productname>Postgres-XC</></entry>
-<!## end>
-<!## XL>
-      <entry>Applies to a feature not available in <productname>Postgres-XL</></entry>
-<!## end>
-     </row>
-
-     <row>
-      <entry><literal>is_updatable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</literal> if the view is updatable (allows
-       <command>UPDATE</command> and <command>DELETE</command>),
-       <literal>NO</literal> if not
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_insertable_into</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</literal> if the view is insertable into (allows
-       <command>INSERT</command>), <literal>NO</literal> if not
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_trigger_updatable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</> if the view has an <literal>INSTEAD OF</>
-       <command>UPDATE</> trigger defined on it, <literal>NO</> if not
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_trigger_deletable</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</> if the view has an <literal>INSTEAD OF</>
-       <command>DELETE</> trigger defined on it, <literal>NO</> if not
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>is_trigger_insertable_into</literal></entry>
-      <entry><type>yes_or_no</type></entry>
-      <entry>
-       <literal>YES</> if the view has an <literal>INSTEAD OF</>
-       <command>INSERT</> trigger defined on it, <literal>NO</> if not
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/install-windows.sgmlin b/doc-xc/src/sgml/install-windows.sgmlin
deleted file mode 100644
index cb8bca9c63..0000000000
--- a/doc-xc/src/sgml/install-windows.sgmlin
+++ /dev/null
@@ -1,578 +0,0 @@
-<!-- doc/src/sgml/install-windows.sgml -->
-
-<chapter id="install-windows">
- <title>Installation from Source Code on <productname>Windows</productname></title>
-
- <indexterm>
-  <primary>installation</primary>
-  <secondary>on Windows</secondary>
- </indexterm>
-
- <para>
-  It is recommended that most users download the binary distribution for
-  Windows, available as a one-click installer package
-  from the <productname>PostgreSQL</productname> website. Building from source
-  is only intended for people developing <productname>PostgreSQL</productname>
-  or extensions.
- </para>
-
- <para>
-  There are several different ways of building PostgreSQL on
-  <productname>Windows</productname>. The simplest way to build with
-  Microsoft tools is to install a supported version of the
-  <productname>Microsoft Platform SDK</productname> and use use the included
-  compiler. It is also possible to build with the full
-  <productname>Microsoft Visual C++ 2005 or 2008</productname>. In some cases
-  that requires the installation of the <productname>Platform SDK</productname>
-  in addition to the compiler.
- </para>
-
- <para>
-  It is also possible to build PostgreSQL using the GNU compiler tools
-  provided by <productname>MinGW</productname>, or using
-  <productname>Cygwin</productname> for older versions of
-  <productname>Windows</productname>.
- </para>
-
- <para>
-  Finally, the client access library
-  (<application>libpq</application>) can be built using
-  <productname>Visual C++ 7.1</productname> or
-  <productname>Borland C++</productname> for compatibility with statically
-  linked applications built using these tools.
- </para>
-
- <para>
-  Building using <productname>MinGW</productname> or
-  <productname>Cygwin</productname> uses the normal build system, see
-  <xref linkend="installation"> and the specific notes in
-  <xref linkend="installation-notes-mingw"> and <xref linkend="installation-notes-cygwin">.
-  To produce native 64 bit binaries in these environments, use the tools from
-  <productname>MinGW-w64</productname>. These tools can also be used to
-  cross-compile for 32 bit and 64 bit <productname>Windows</productname> 
-  targets on other hosts, such as <productname>Linux</productname> and 
-  <productname>Darwin</productname>.
-  <productname>Cygwin</productname> is not recommended for running a
-  production server, and it should only be used for running on
-  older versions of <productname>Windows</productname> where
-  the native build does not work, such as
-  <productname>Windows 98</productname>. The official
-  binaries are built using <productname>Visual Studio</productname>.
- </para>
-
- <para>
-  Native builds of <application>psql</application> don't support command 
-  line editing. The <productname>Cygwin</productname> build does support
-  command line editing, so it should be used where psql is needed for
-  interactive use on  <productname>Windows</productname>.
- </para>
-
- <sect1 id="install-windows-full">
-  <title>Building with <productname>Visual C++</productname> or the
-  <productname>Platform SDK</productname></title>
-
- <para>
-  PostgreSQL can be built using the Visual C++ compiler suite from Microsoft.
-  These compilers can be either from <productname>Visual Studio</productname>,
-  <productname>Visual Studio Express</productname> or some versions of the
-  <productname>Platform SDK</productname>. If you do not already have a
-  <productname>Visual Studio</productname> environment set up, the easiest
-  way us to use the compilers in the <productname>Platform SDK</productname>,
-  which is a free download from Microsoft.
- </para>
-
- <para>
-  PostgreSQL supports the compilers from
-  <productname>Visual Studio 2005</productname> and
-  <productname>Visual Studio 2008</productname>. When using the Platform SDK
-  only, or when building for 64-bit Windows, only
-  <productname>Visual Studio 2008</productname> is supported.
-  <productname>Visual Studio 2010</productname> is not yet supported.
- </para>
-
- <para>
-  When building using the <productname>Platform SDK</productname>, versions
-  6.0 to 7.0 of the SDK are supported. Older or newer versions will not work.
-  In particular, versions from 7.0a and later will not work, since
-  they include compilers from <productname>Visual Studio 2010</productname>.
- </para>
-
- <para>
-  The tools for building using <productname>Visual C++</productname>,
-  are in the <filename>src/tools/msvc</filename> directory. When building,
-  make sure there are no tools from <productname>MinGW</productname> or
-  <productname>Cygwin</productname> present in your system PATH. Also, make
-  sure you have all the required Visual C++ tools available in the PATH. In
-  <productname>Visual Studio</productname>, start the
-  <application>Visual Studio Command Prompt</application>. In the
-  <productname>Platform SDK</productname>, start the
-  <application>CMD shell</application> listed under the SDK on the Start Menu.
-  If you wish to build a 64-bit version, you must use the 64-bit version of
-  the command, and vice versa.
-  All commands should be run from the <filename>src\tools\msvc</filename>
-  directory.
- </para>
-
- <para>
-  Before you build, you may need to edit the file <filename>config.pl</filename>
-  to reflect any configuration options you want to change, or the paths to
-  any third party libraries to use. The complete configuration is determined
-  by first reading and parsing the file <filename>config_default.pl</filename>,
-  and then apply any changes from <filename>config.pl</filename>. For example,
-  to specify the location of your <productname>Python</productname> installation,
-  put the following in <filename>config.pl</filename>:
-<programlisting>
-$config->{python} = 'c:\python26';
-</programlisting>
-  You only need to specify those parameters that are different from what's in
-  <filename>config_default.pl</filename>.
- </para>
-
- <para>
-  If you need to set any other environment variables, create a file called
-  <filename>buildenv.pl</filename> and put the required commands there. For
-  example, to add the path for bison when it's not in the PATH, create a file
-  containing:
-<programlisting>
-$ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
-</programlisting>
- </para>
-
- <sect2>
-  <title>Requirements</title>
-  <para>
-   The following additional products are required to build
-   <productname>PostgreSQL</productname>. Use the
-   <filename>config.pl</filename> file to specify which directories the libraries
-   are available in.
-
-   <variablelist>
-    <varlistentry>
-     <term><productname>Microsoft Platform SDK</productname></term>
-     <listitem><para>
-      It is recommended that you upgrade to the latest supported version
-      of the <productname>Microsoft Platform SDK</productname> (currently
-      version 7.0), available for download from
-      <ulink url="http://www.microsoft.com/downloads/"></>.
-     </para>
-     <para>
-      You must always include the
-      <application>Windows Headers and Libraries</application> part of the SDK.
-      If you install the <productname>Platform SDK</productname>
-      including the <application>Visual C++ Compilers</application>,
-      you don't need <productname>Visual Studio</productname> to build.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><productname>ActiveState Perl</productname></term>
-     <listitem><para>
-      ActiveState Perl is required to run the build generation scripts. MinGW
-      or Cygwin Perl will not work. It must also be present in the PATH.
-      Binaries can be downloaded from
-      <ulink url="http://www.activestate.com"></> (Note: version 5.8 is required,
-      the free Standard Distribution is sufficient).
-     </para></listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-  <para>
-   The following additional products are not required to get started,
-   but are required to build the complete package. Use the
-   <filename>config.pl</filename> file to specify which directories the libraries
-   are available in.
-
-   <variablelist>
-    <varlistentry>
-     <term><productname>ActiveState TCL</productname></term>
-     <listitem><para>
-      Required for building <application>PL/TCL</application> (Note: version
-      8.4 is required, the free Standard Distribution is sufficient).
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><productname>Bison</productname> and
-      <productname>Flex</productname></term>
-     <listitem><para>
-      Bison and Flex are required to build from Git, but not required when
-      building from a release file. Note that only Bison 1.875 or versions
-      2.2 and later will work. Also, Flex version 2.5.31 or later is required.
-      Bison can be downloaded from <ulink url="http://gnuwin32.sourceforge.net"></>.
-      Flex can be downloaded from
-      <ulink url="http://www.postgresql.org/ftp/misc/winflex/"></>.
-     </para>
-
-     <note>
-      <para>
-        The Bison distribution from GnuWin32 appears to have a bug that
-        causes Bison to malfunction when installed in a directory with
-        spaces in the name, such as the default location on English
-        installations <filename>C:\Program Files\GnuWin32</filename>.
-        Consider installing into <filename>C:\GnuWin32</filename> instead.
-       </para>
-     </note>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><productname>Diff</productname></term>
-     <listitem><para>
-      Diff is required to run the regression tests, and can be downloaded
-      from <ulink url="http://gnuwin32.sourceforge.net"></>.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><productname>Gettext</productname></term>
-     <listitem><para>
-      Gettext is required to build with NLS support, and can be downloaded
-      from <ulink url="http://gnuwin32.sourceforge.net"></>. Note that binaries,
-      dependencies and developer files are all needed.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><productname>MIT Kerberos</productname></term>
-     <listitem><para>
-      Required for Kerberos authentication support. MIT Kerberos can be
-      downloaded from
-      <ulink url="http://web.mit.edu/Kerberos/dist/index.html"></>.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><productname>libxml2</productname> and
-      <productname>libxslt</productname></term>
-     <listitem><para>
-      Required for XML support. Binaries can be downloaded from
-      <ulink url="http://zlatkovic.com/pub/libxml"></> or source from
-      <ulink url="http://xmlsoft.org"></>. Note that libxml2 requires iconv,
-      which is available from the same download location.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><productname>openssl</productname></term>
-     <listitem><para>
-      Required for SSL support. Binaries can be downloaded from
-      <ulink url="http://www.slproweb.com/products/Win32OpenSSL.html"></>
-      or source from <ulink url="http://www.openssl.org"></>.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><productname>ossp-uuid</productname></term>
-     <listitem><para>
-      Required for UUID-OSSP support (contrib only). Source can be
-      downloaded from
-      <ulink url="http://www.ossp.org/pkg/lib/uuid/"></>.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><productname>Python</productname></term>
-     <listitem><para>
-      Required for building <application>PL/Python</application>. Binaries can
-      be downloaded from <ulink url="http://www.python.org"></>.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><productname>zlib</productname></term>
-     <listitem><para>
-      Required for compression support in <application>pg_dump</application>
-      and <application>pg_restore</application>. Binaries can be downloaded
-      from <ulink url="http://www.zlib.net"></>.
-     </para></listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
- </sect2>
-
- <sect2>
-  <title>Special Considerations for 64-bit Windows</title>
-
-  <para>
-   PostgreSQL will only build for the x64 architecture on 64-bit Windows, there
-   is no support for Itanium processors.
-  </para>
-
-  <para>
-   Mixing 32- and 64-bit versions in the same build tree is not supported.
-   The build system will automatically detect if it's running in a 32- or
-   64-bit environment, and build PostgreSQL accordingly. For this reason, it
-   is important to start the correct command prompt before building.
-  </para>
-
-  <para>
-   To use a server-side third party library such as <productname>python</> or
-   <productname>openssl</>, this library <emphasis>must</emphasis> also be
-   64-bit. There is no support for loading a 32-bit library in a 64-bit
-   server. Several of the third party libraries that PostgreSQL supports may
-   only be available in 32-bit versions, in which case they cannot be used with
-   64-bit PostgreSQL.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Building</title>
-
-  <para>
-   To build all of PostgreSQL in release configuration (the default), run the
-   command:
-<screen>
-<userinput>build</userinput>
-</screen>
-   To build all of PostgreSQL in debug configuration, run the command:
-<screen>
-<userinput>build DEBUG</userinput>
-</screen>
-   To build just a single project, for example psql, run the commands:
-<screen>
-<userinput>build psql</userinput>
-<userinput>build DEBUG psql</userinput>
-</screen>
-   To change the default build configuration to debug, put the following
-   in the <filename>buildenv.pl</filename> file:
-<programlisting>
-$ENV{CONFIG}="Debug";
-</programlisting>
-  </para>
-
-  <para>
-   It is also possible to build from inside the Visual Studio GUI. In this
-   case, you need to run:
-<screen>
-<userinput>perl mkvcbuild.pl</userinput>
-</screen>
-   from the command prompt, and then open the generated
-   <filename>pgsql.sln</filename> (in the root directory of the source tree)
-   in Visual Studio.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Cleaning and Installing</title>
-
-  <para>
-   Most of the time, the automatic dependency tracking in Visual Studio will
-   handle changed files. But if there have been large changes, you may need
-   to clean the installation. To do this, simply run the
-   <filename>clean.bat</filename> command, which will automatically clean out
-   all generated files. You can also run it with the
-   <parameter>dist</parameter> parameter, in which case it will behave like
-   <userinput>make distclean</userinput> and remove the flex/bison output files
-   as well.
-  </para>
-
-  <para>
-   By default, all files are written into a subdirectory of the
-   <filename>debug</filename> or <filename>release</filename> directories. To
-   install these files using the standard layout, and also generate the files
-   required to initialize and use the database, run the command:
-<screen>
-<userinput>install c:\destination\directory</userinput>
-</screen>
-  </para>
- </sect2>
-
- <sect2>
-  <title>Running the Regression Tests</title>
-
-  <para>
-   To run the regression tests, make sure you have completed the build of all
-   required parts first. Also, make sure that the DLLs required to load all
-   parts of the system (such as the Perl and Python DLLs for the procedural
-   languages) are present in the system path. If they are not, set it through
-   the <filename>buildenv.pl</filename> file. To run the tests, run one of
-   the following commands from the <filename>src\tools\msvc</filename>
-   directory:
-<screen>
-<userinput>vcregress check</userinput>
-<userinput>vcregress installcheck</userinput>
-<userinput>vcregress plcheck</userinput>
-<userinput>vcregress contribcheck</userinput>
-</screen>
-
-   To change the schedule used (default is parallel), append it to the
-   command line like:
-<screen>
-<userinput>vcregress check serial</userinput>
-</screen>
-
-   For more information about the regression tests, see
-   <xref linkend="regress">.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Building the Documentation</title>
-
-  <para>
-   Building the PostgreSQL documentation in HTML format requires several tools
-   and files. Create a root directory for all these files, and store them
-   in the subdirectories in the list below.
-   <variablelist>
-    <varlistentry>
-     <term>OpenJade 1.3.1-2</term>
-     <listitem><para>
-      Download from
-      <ulink url="http://sourceforge.net/projects/openjade/files/openjade/1.3.1/openjade-1_3_1-2-bin.zip/download"></>
-      and uncompress in the subdirectory <filename>openjade-1.3.1</filename>.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>DocBook DTD 4.2</term>
-     <listitem><para>
-      Download from
-      <ulink url="http://www.oasis-open.org/docbook/sgml/4.2/docbook-4.2.zip"></>
-      and uncompress in the subdirectory <filename>docbook</filename>.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>DocBook DSSSL 1.79</term>
-     <listitem><para>
-      Download from
-      <ulink url="http://sourceforge.net/projects/docbook/files/docbook-dsssl/1.79/docbook-dsssl-1.79.zip/download"></>
-      and uncompress in the subdirectory
-      <filename>docbook-dsssl-1.79</filename>.
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>ISO character entities</term>
-     <listitem><para>
-      Download from
-      <ulink url="http://www.oasis-open.org/cover/ISOEnts.zip"></> and
-      uncompress in the subdirectory <filename>docbook</filename>.
-     </para></listitem>
-    </varlistentry>
-   </variablelist>
-   Edit the <filename>buildenv.pl</filename> file, and add a variable for the
-   location of the root directory, for example:
-<programlisting>
-$ENV{DOCROOT}='c:\docbook';
-</programlisting>
-   To build the documentation, run the command
-   <filename>builddoc.bat</filename>. Note that this will actually run the
-   build twice, in order to generate the indexes. The generated HTML files
-   will be in <filename>doc\src\sgml</filename>.
-  </para>
- </sect2>
-
- </sect1>
-
- <sect1 id="install-windows-libpq">
-  <title>Building <application>libpq</application> with
-  <productname>Visual C++</productname> or
-  <productname>Borland C++</productname></title>
-
- <para>
-  Using <productname>Visual C++ 7.1-9.0</productname> or
-  <productname>Borland C++</productname> to build libpq is only recommended
-  if you need a version with different debug/release flags, or if you need a
-  static library to link into an application. For normal use the
-  <productname>MinGW</productname> or
-  <productname>Visual Studio</productname> or
-  <productname>Platform SDK</productname> method is recommended.
- </para>
-
- <para>
-  To build the <application>libpq</application> client library using
-  <productname>Visual Studio 7.1 or later</productname>, change into the
-  <filename>src</filename> directory and type the command:
-<screen>
-<userinput>nmake /f win32.mak</userinput>
-</screen>
- </para>
- <para>
- To build a 64-bit version of the <application>libpq</application>
- client library using <productname>Visual Studio 8.0 or
- later</productname>, change into the <filename>src</filename>
- directory and type in the command:
-<screen>
-<userinput>nmake /f win32.mak CPU=AMD64</userinput>
-</screen>
- See the <filename>win32.mak</filename> file for further details
- about supported variables.
- </para>
-
- <para>
-  To build the <application>libpq</application> client library using
-  <productname>Borland C++</productname>, change into the
-  <filename>src</filename> directory and type the command:
-<screen>
-<userinput>make -N -DCFG=Release /f bcc32.mak</userinput>
-</screen>
- </para>
-
- <sect2>
- <title>Generated Files</title>
- <para>
-  The following files will be built:
-
-  <variablelist>
-   <varlistentry>
-    <term><filename>interfaces\libpq\Release\libpq.dll</filename></term>
-    <listitem>
-     <para>
-      The dynamically linkable frontend library
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><filename>interfaces\libpq\Release\libpqdll.lib</filename></term>
-    <listitem>
-     <para>
-      Import library to link your programs to <filename>libpq.dll</filename>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><filename>interfaces\libpq\Release\libpq.lib</filename></term>
-    <listitem>
-     <para>
-      Static version of the frontend library
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </para>
-
- <para>
-  Normally you do not need to install any of the client files. You should
-  place the <filename>libpq.dll</filename> file in the same directory
-  as your applications executable file. Do not install
-  <filename>libpq.dll</filename> into your <filename>Windows</>,
-  <filename>System</> or <filename>System32</> directory unless
-  absolutely necessary.
-  If this file is installed using a setup program, then it should
-  be installed with version checking using the
-  <symbol>VERSIONINFO</symbol> resource included in the file, to
-  ensure that a newer version of the library is not overwritten.
- </para>
-
- <para>
-  If you are planning to do development using <application>libpq</application>
-  on this machine, you will have to add the
-  <filename>src\include</filename> and
-  <filename>src\interfaces\libpq</filename> subdirectories of the source
-  tree to the include path in your compiler's settings.
- </para>
-
- <para>
-  To use the library, you must add the
-  <filename>libpqdll.lib</filename> file to your project.  (In Visual
-  C++, just right-click on the project and choose to add it.)
- </para>
- </sect2>
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/installation.sgmlin b/doc-xc/src/sgml/installation.sgmlin
deleted file mode 100644
index c5dfeebfc8..0000000000
--- a/doc-xc/src/sgml/installation.sgmlin
+++ /dev/null
@@ -1,4740 +0,0 @@
-<!-- doc/src/sgml/installation.sgml -->
-<!--
-
-Use </link> not just </> so INSTALL.html can be created without links
-to the main documentation.  Don't use <xref>.
-
--->
-
-<chapter id="installation">
-<!## PG>
- <title><![%standalone-include[<productname>PostgreSQL</>]]>
-<!## end>
-<!## XC>
- <title><![%standalone-include[<productname>Postgres-XC</>]]>
-<!## end>
-<!## XL>
- <title><![%standalone-include[<productname>Postgres-XL</>]]>
-<!## end>
-  Installation from Source Code</title>
-
- <indexterm zone="installation">
-  <primary>installation</primary>
- </indexterm>
-
-<!## PG>
- <para>
-  This <![%standalone-include;[document]]>
-  <![%standalone-ignore;[chapter]]> describes the installation of
-  <productname>PostgreSQL</productname> using the source code
-  distribution.  (If you are installing a pre-packaged distribution,
-  such as an RPM or Debian package, ignore this
-  <![%standalone-include;[document]]>
-  <![%standalone-ignore;[chapter]]>
-  and read the packager's instructions instead.)
- </para>
-<!## end>
-<!## XC>
-&xconly;
- <para>
-  This <![%standalone-include;[document]]>
-  <![%standalone-ignore;[chapter]]> describes the installation of
-  <productname>Postgres-XC</productname> using the source code
-  distribution.  (If you are installing a pre-packaged distribution,
-  such as an RPM or Debian package, ignore this
-  <![%standalone-include;[document]]>
-  <![%standalone-ignore;[chapter]]>
-  and read the packager's instructions instead.)
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  This <![%standalone-include;[document]]>
-  <![%standalone-ignore;[chapter]]> describes the installation of
-  <productname>Postgres-XL</productname> using the source code
-  distribution.  (If you are installing a pre-packaged distribution,
-  such as an RPM or Debian package, ignore this
-  <![%standalone-include;[document]]>
-  <![%standalone-ignore;[chapter]]>
-  and read the packager's instructions instead.)
- </para>
-<!## end>
-
- <sect1 id="install-short">
-  <title>Short Version</title>
-
-<!## PG>
-  <para>
-<synopsis>
-./configure
-gmake
-su
-gmake install
-adduser postgres
-mkdir /usr/local/pgsql/data
-chown postgres /usr/local/pgsql/data
-su - postgres
-/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
-/usr/local/pgsql/bin/postgres -D /usr/local/pgsql/data &gt;logfile 2&gt;&amp;1 &amp;
-/usr/local/pgsql/bin/createdb test
-/usr/local/pgsql/bin/psql test
-</synopsis>
-  </para>
-<!## end>
-<!## XC>
-  <para>
-    The following short installation allows to install a simple cluster on a local machine with
-    1 Coordinator, 2 Datanodes and 1 GTM. When installing a more complex cluster, you might
-    change the number of Coordinators and Datanodes, and might have to start nodes on different
-    servers.
-  </para>
-<synopsis>
-./configure
-gmake
-su
-gmake install
-adduser postgres
-mkdir /usr/local/pgsql/data_coord1
-mkdir /usr/local/pgsql/data_datanode1
-mkdir /usr/local/pgsql/data_datanode2
-mkdir /usr/local/pgsql/data_gtm
-chown postgres /usr/local/pgsql/data_coord1
-chown postgres /usr/local/pgsql/data_datanode1
-chown postgres /usr/local/pgsql/data_datanode2
-chown postgres /usr/local/pgsql/data_gtm
-su - postgres
-/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data_coord1 --nodename coord1
-/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data_datanode1 --nodename datanode1
-/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data_datanode2 --nodename datanode2
-/usr/local/pgsql/bin/initgtm -D /usr/local/pgsql/data_gtm -Z gtm
-/usr/local/pgsql/bin/gtm -D /usr/local/pgsql/data_gtm &gt;logfile 2&gt;&amp;1 &amp;
-/usr/local/pgsql/bin/postgres --datanode -p 15432 -D /usr/local/pgsql/data_datanode1 &gt;logfile 2&gt;&amp;1 &amp;
-/usr/local/pgsql/bin/postgres --datanode -p 15433 -D /usr/local/pgsql/data_datanode2 &gt;logfile 2&gt;&amp;1 &amp;
-/usr/local/pgsql/bin/postgres --coordinator -D /usr/local/pgsql/data_coord1 &gt;logfile 2&gt;&amp;1 &amp;
-/usr/local/pgsql/bin/psql -c "ALTER NODE coord1 WITH (TYPE = 'coordinator', PORT = 5432)" postgres
-/usr/local/pgsql/bin/psql -c "CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432)" postgres
-/usr/local/pgsql/bin/psql -c "CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433)" postgres
-/usr/local/pgsql/bin/psql -c "EXECUTE DIRECT ON (datanode1) 'ALTER NODE datanode1 WITH (TYPE = ''datanode'', PORT = 15432)'" postgres
-/usr/local/pgsql/bin/psql -c "EXECUTE DIRECT ON (datanode1) 'CREATE NODE datanode2 WITH (TYPE = ''datanode'', PORT = 15433)'" postgres
-/usr/local/pgsql/bin/psql -c "EXECUTE DIRECT ON (datanode2) 'ALTER NODE datanode2 WITH (TYPE = ''datanode'', PORT = 15433)'" postgres
-/usr/local/pgsql/bin/psql -c "EXECUTE DIRECT ON (datanode2) 'CREATE NODE datanode1 WITH (TYPE = ''datanode'', PORT = 15432)'" postgres
-/usr/local/pgsql/bin/psql -c "SELECT pgxc_pool_reload()" postgres
-/usr/local/pgsql/bin/createdb test
-/usr/local/pgsql/bin/psql test
-</synopsis>
-<!## end>
-<!## XL>
-  <para>
-    The following short installation allows to install a simple cluster on a local machine with
-    1 Coordinator, 2 Datanodes and 1 GTM. When installing a more complex cluster, you might
-    change the number of Coordinators and Datanodes, and might have to start nodes on different
-    servers.
-    Also, you can instead use the pgxc_ctl utility, which simplifies the installation and configuration process.
-  </para>
-<synopsis>
-./configure
-gmake
-su
-gmake install
-adduser postgres
-mkdir /usr/local/pgsql/data_coord1
-mkdir /usr/local/pgsql/data_datanode1
-mkdir /usr/local/pgsql/data_datanode2
-mkdir /usr/local/pgsql/data_gtm
-chown postgres /usr/local/pgsql/data_coord1
-chown postgres /usr/local/pgsql/data_datanode1
-chown postgres /usr/local/pgsql/data_datanode2
-chown postgres /usr/local/pgsql/data_gtm
-su - postgres
-/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data_coord1 --nodename coord1
-/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data_datanode1 --nodename datanode1
-/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data_datanode2 --nodename datanode2
-/usr/local/pgsql/bin/initgtm -D /usr/local/pgsql/data_gtm -Z gtm
-/usr/local/pgsql/bin/gtm -D /usr/local/pgsql/data_gtm &gt;logfile 2&gt;&amp;1 &amp;
-/usr/local/pgsql/bin/postgres --datanode -p 15432 -D /usr/local/pgsql/data_datanode1 &gt;logfile 2&gt;&amp;1 &amp;
-/usr/local/pgsql/bin/postgres --datanode -p 15433 -D /usr/local/pgsql/data_datanode2 &gt;logfile 2&gt;&amp;1 &amp;
-/usr/local/pgsql/bin/postgres --coordinator -D /usr/local/pgsql/data_coord1 &gt;logfile 2&gt;&amp;1 &amp;
-/usr/local/pgsql/bin/psql -c "ALTER NODE coord1 WITH (TYPE = 'coordinator', PORT = 5432)" postgres
-/usr/local/pgsql/bin/psql -c "CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432)" postgres
-/usr/local/pgsql/bin/psql -c "CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433)" postgres
-/usr/local/pgsql/bin/psql -c "EXECUTE DIRECT ON (datanode1) 'ALTER NODE datanode1 WITH (TYPE = ''datanode'', PORT = 15432)'" postgres
-/usr/local/pgsql/bin/psql -c "EXECUTE DIRECT ON (datanode1) 'CREATE NODE datanode2 WITH (TYPE = ''datanode'', PORT = 15433)'" postgres
-/usr/local/pgsql/bin/psql -c "EXECUTE DIRECT ON (datanode2) 'ALTER NODE datanode2 WITH (TYPE = ''datanode'', PORT = 15433)'" postgres
-/usr/local/pgsql/bin/psql -c "EXECUTE DIRECT ON (datanode2) 'CREATE NODE datanode1 WITH (TYPE = ''datanode'', PORT = 15432)'" postgres
-/usr/local/pgsql/bin/psql -c "SELECT pgxc_pool_reload()" postgres
-/usr/local/pgsql/bin/createdb test
-/usr/local/pgsql/bin/psql test
-</synopsis>
-<!## end>
-<para>
-
-   The long version is the rest of this
-   <![%standalone-include;[document.]]>
-   <![%standalone-ignore;[chapter.]]>
-  </para>
- </sect1>
-
-
- <sect1 id="install-requirements">
-  <title>Requirements</title>
-
-<!## PG>
-  <para>
-   In general, a modern Unix-compatible platform should be able to run
-   <productname>PostgreSQL</>.
-   The platforms that had received specific testing at the
-   time of release are listed in <xref linkend="supported-platforms">
-   below. In the <filename>doc</> subdirectory of the distribution
-   there are several platform-specific <acronym>FAQ</> documents you
-   might wish to consult if you are having trouble.
-  </para>
-<!## end>
-<!## XC>
-&xconly;
-  <para>
-   In general, a Linux-Unix platform should be able to run <productname>Postgres-XC</>.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   In general, a Linux-Unix platform should be able to run <productname>Postgres-XL</>.
-  </para>
-<!## end>
-
-  <para>
-   The following software packages are required for building
-<!## PG>
-   <productname>PostgreSQL</>:
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</>:
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</>:
-<!## end>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <indexterm>
-       <primary>make</primary>
-      </indexterm>
-
-      <acronym>GNU</> <application>make</> version 3.80 or newer is required; other
-      <application>make</> programs or older <acronym>GNU</> <application>make</> versions will <emphasis>not</> work.
-      <acronym>GNU</> <application>make</> is often installed under
-      the name <filename>gmake</filename>; this document will always
-      refer to it by that name. (On some systems
-      <acronym>GNU</acronym> <application>make</> is the default tool with the name
-      <filename>make</>.) To test for <acronym>GNU</acronym>
-      <application>make</application> enter:
-<screen>
-<userinput>gmake --version</userinput>
-</screen>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      You need an <acronym>ISO</>/<acronym>ANSI</> C compiler (at least
-      C89-compliant). Recent
-      versions of <productname>GCC</> are recommendable, but
-<!## PG>
-      <productname>PostgreSQL</> is known to build using a wide variety
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</> is known to build using a wide variety
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</> is known to build using a wide variety
-<!## end>
-      of compilers from different vendors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <application>tar</> is required to unpack the source
-      distribution, in addition to either
-      <application>gzip</> or <application>bzip2</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary>readline</primary>
-      </indexterm>
-      <indexterm>
-       <primary>libedit</primary>
-      </indexterm>
-
-<!## PG>
-      The <acronym>GNU</> <productname>Readline</> library is used by
-      default.  It allows <application>psql</application> (the
-      PostgreSQL command line SQL interpreter) to remember each
-      command you type, and allows you to use arrow keys to recall and
-      edit previous commands.  This is very helpful and is strongly
-      recommended.  If you don't want to use it then you must specify
-      the <option>--without-readline</option> option to
-      <filename>configure</>. As an alternative, you can often use the
-      BSD-licensed <filename>libedit</filename> library, originally
-      developed on <productname>NetBSD</productname>. The
-      <filename>libedit</filename> library is
-      GNU <productname>Readline</productname>-compatible and is used if
-      <filename>libreadline</filename> is not found, or if
-      <option>--with-libedit-preferred</option> is used as an
-      option to <filename>configure</>. If you are using a package-based
-      Linux distribution, be aware that you need both the
-      <literal>readline</> and <literal>readline-devel</> packages, if
-      those are separate in your distribution.
-<!## end>
-<!## XC>
-      The <acronym>GNU</> <productname>Readline</> library is used by
-      default.  It allows <application>psql</application> (the
-      Postgres-XC command line SQL interpreter) to remember each
-      command you type, and allows you to use arrow keys to recall and
-      edit previous commands.  This is very helpful and is strongly
-      recommended.  If you don't want to use it then you must specify
-      the <option>--without-readline</option> option to
-      <filename>configure</>. As an alternative, you can often use the
-      BSD-licensed <filename>libedit</filename> library, originally
-      developed on <productname>NetBSD</productname>. The
-      <filename>libedit</filename> library is
-      GNU <productname>Readline</productname>-compatible and is used if
-      <filename>libreadline</filename> is not found, or if
-      <option>--with-libedit-preferred</option> is used as an
-      option to <filename>configure</>. If you are using a package-based
-      Linux distribution, be aware that you need both the
-      <literal>readline</> and <literal>readline-devel</> packages, if
-      those are separate in your distribution.
-<!## end>
-<!## XL>
-      The <acronym>GNU</> <productname>Readline</> library is used by
-      default.  It allows <application>psql</application> (the
-      Postgres-XL command line SQL interpreter) to remember each
-      command you type, and allows you to use arrow keys to recall and
-      edit previous commands.  This is very helpful and is strongly
-      recommended.  If you don't want to use it then you must specify
-      the <option>--without-readline</option> option to
-      <filename>configure</>. As an alternative, you can often use the
-      BSD-licensed <filename>libedit</filename> library, originally
-      developed on <productname>NetBSD</productname>. The
-      <filename>libedit</filename> library is
-      GNU <productname>Readline</productname>-compatible and is used if
-      <filename>libreadline</filename> is not found, or if
-      <option>--with-libedit-preferred</option> is used as an
-      option to <filename>configure</>. If you are using a package-based
-      Linux distribution, be aware that you need both the
-      <literal>readline</> and <literal>readline-devel</> packages, if
-      those are separate in your distribution.
-<!## end>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary>zlib</primary>
-      </indexterm>
-
-      The <productname>zlib</productname> compression library is
-      used by default. If you don't want to use it then you must
-      specify the <option>--without-zlib</option> option to
-      <filename>configure</filename>. Using this option disables
-      support for compressed archives in <application>pg_dump</> and
-      <application>pg_restore</>.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   The following packages are optional.  They are not required in the
-   default configuration, but they are needed when certain build
-   options are enabled, as explained below:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      To build the server programming language
-      <application>PL/Perl</application> you need a full
-      <productname>Perl</productname> installation, including the
-      <filename>libperl</filename> library and the header files.
-      Since <application>PL/Perl</application> will be a shared
-      library, the <indexterm><primary>libperl</primary></indexterm>
-      <filename>libperl</filename> library must be a shared library
-      also on most platforms.  This appears to be the default in
-      recent <productname>Perl</productname> versions, but it was not
-      in earlier versions, and in any case it is the choice of whomever
-      installed Perl at your site.
-      If you intend to make more than incidental use of
-      <application>PL/Perl</application>, you should ensure that the
-      <productname>Perl</productname> installation was built with the
-      <literal>usemultiplicity</> option enabled (<literal>perl -V</>
-      will show whether this is the case).
-     </para>
-
-     <para>
-<!## PG>
-      If you don't have the shared library but you need one, a message
-      like this will appear during the <productname>PostgreSQL</>
-      build to point out this fact:
-<!## end>
-<!## XC>
-      If you don't have the shared library but you need one, a message
-      like this will appear during the <productname>Postgres-XC</>
-      build to point out this fact:
-<!## end>
-<!## XL>
-      If you don't have the shared library but you need one, a message
-      like this will appear during the <productname>Postgres-XL</>
-      build to point out this fact:
-<!## end>
-
-<screen>
-*** Cannot build PL/Perl because libperl is not a shared library.
-*** You might have to rebuild your Perl installation.  Refer to
-*** the documentation for details.
-</screen>
-      (If you don't follow the on-screen output you will merely notice
-      that the <application>PL/Perl</application> library object,
-      <filename>plperl.so</filename> or similar, will not be
-      installed.)  If you see this, you will have to rebuild and
-      install <productname>Perl</productname> manually to be able to
-      build <application>PL/Perl</application>.  During the
-      configuration process for <productname>Perl</productname>,
-      request a shared library.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      To build the <application>PL/Python</> server programming
-      language, you need a <productname>Python</productname>
-      installation with the header files and
-      the <application>distutils</application> module.  The minimum
-      required version is <productname>Python</productname>
-      2.2.  <productname>Python 3</productname> is supported if it's
-      version 3.1 or later; but see
-      <![%standalone-include[the <application>PL/Python</> documentation]]>
-      <![%standalone-ignore[<xref linkend="plpython-python23">]]>
-      when using Python 3.
-     </para>
-
-     <para>
-      Since <application>PL/Python</application> will be a shared
-      library, the <indexterm><primary>libpython</primary></indexterm>
-      <filename>libpython</filename> library must be a shared library
-      also on most platforms.  This is not the case in a default
-      <productname>Python</productname> installation.  If after
-      building and installing <productname>PostgreSQL</> you have a file called
-      <filename>plpython.so</filename> (possibly a different
-      extension), then everything went well.  Otherwise you should
-      have seen a notice like this flying by:
-<screen>
-*** Cannot build PL/Python because libpython is not a shared library.
-*** You might have to rebuild your Python installation.  Refer to
-*** the documentation for details.
-</screen>
-      That means you have to rebuild (part of) your
-      <productname>Python</productname> installation to create this
-      shared library.
-     </para>
-
-     <para>
-<!## PG>
-      If you have problems, run <productname>Python</> 2.3 or later's
-      configure using the <literal>--enable-shared</> flag.  On some
-      operating systems you don't have to build a shared library, but
-      you will have to convince the <productname>PostgreSQL</> build
-      system of this.  Consult the <filename>Makefile</filename> in
-      the <filename>src/pl/plpython</filename> directory for details.
-<!## end>
-<!## XC>
-      If you have problems, run <productname>Python</> 2.3 or later's
-      configure using the <literal>--enable-shared</> flag.  On some
-      operating systems you don't have to build a shared library, but
-      you will have to convince the <productname>Postgres-XC</> build
-      system of this.  Consult the <filename>Makefile</filename> in
-      the <filename>src/pl/plpython</filename> directory for details.
-<!## end>
-<!## XL>
-      If you have problems, run <productname>Python</> 2.3 or later's
-      configure using the <literal>--enable-shared</> flag.  On some
-      operating systems you don't have to build a shared library, but
-      you will have to convince the <productname>Postgres-XL</> build
-      system of this.  Consult the <filename>Makefile</filename> in
-      the <filename>src/pl/plpython</filename> directory for details.
-<!## end>
-
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      To build the <application>PL/Tcl</application>
-      procedural language, you of course need a <productname>Tcl</>
-      installation.  If you are using a pre-8.4 release of
-      <productname>Tcl</>, ensure that it was built without multithreading
-      support.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      To enable Native Language Support (<acronym>NLS</acronym>), that
-      is, the ability to display a program's messages in a language
-      other than English, you need an implementation of the
-      <application>Gettext</> <acronym>API</acronym>.  Some operating
-      systems have this built-in (e.g., <systemitem
-      class="osname">Linux</>, <systemitem class="osname">NetBSD</>,
-      <systemitem class="osname">Solaris</>), for other systems you
-      can download an add-on package from <ulink
-      url="http://www.gnu.org/software/gettext/"></ulink>.
-      If you are using the <application>Gettext</> implementation in
-      the <acronym>GNU</acronym> C library then you will additionally
-      need the <productname>GNU Gettext</productname> package for some
-      utility programs.  For any of the other implementations you will
-      not need it.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      You need <application>Kerberos</>, <productname>OpenSSL</>,
-      <productname>OpenLDAP</>, and/or
-      <application>PAM</>, if you want to support authentication or
-      encryption using those services.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   If you are building from a <productname>Git</productname> tree instead of
-   using a released source package, or if you want to do server development,
-   you also need the following packages:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <indexterm>
-       <primary>flex</primary>
-      </indexterm>
-      <indexterm>
-       <primary>lex</primary>
-      </indexterm>
-      <indexterm>
-       <primary>bison</primary>
-      </indexterm>
-      <indexterm>
-       <primary>yacc</primary>
-      </indexterm>
-
-      GNU <application>Flex</> and <application>Bison</>
-      are needed to build from a Git checkout, or if you changed the actual
-      scanner and parser definition files. If you need them, be sure
-      to get <application>Flex</> 2.5.31 or later and
-      <application>Bison</> 1.875 or later. Other <application>lex</>
-      and <application>yacc</> programs cannot be used.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <indexterm>
-       <primary>perl</primary>
-      </indexterm>
-
-      <application>Perl</> 5.8 or later is needed to build from a Git checkout,
-      or if you changed the input files for any of the build steps that
-      use Perl scripts.  If building on Windows you will need
-      <application>Perl</> in any case.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   If you need to get a <acronym>GNU</acronym> package, you can find
-   it at your local <acronym>GNU</acronym> mirror site (see <ulink
-   url="http://www.gnu.org/order/ftp.html"></>
-   for a list) or at <ulink
-   url="ftp://ftp.gnu.org/gnu/"></ulink>.
-  </para>
-
-  <para>
-   Also check that you have sufficient disk space. You will need about
-   100 MB for the source tree during compilation and about 20 MB for
-   the installation directory. An empty database cluster takes about
-   35 MB; databases take about five times the amount of space that a
-   flat text file with the same data would take. If you are going to
-   run the regression tests you will temporarily need up to an extra
-   150 MB. Use the <command>df</command> command to check free disk
-   space.
-  </para>
- </sect1>
-
-<![%standalone-ignore;[
- <sect1 id="install-getsource">
-  <title>Getting The Source</title>
-
-<!## PG>
-  <para>
-   The <productname>PostgreSQL</> &version; sources can be obtained by
-   anonymous FTP from <ulink
-   url="ftp://ftp.postgresql.org/pub/source/v&version;/postgresql-&version;.tar.gz"></ulink>.
-   Other download options can be found on our website:
-   <ulink url="http://www.postgresql.org/download/"></ulink>. After you
-   have obtained the file, unpack it:
-<screen>
-<userinput>gunzip postgresql-&version;.tar.gz</userinput>
-<userinput>tar xf postgresql-&version;.tar</userinput>
-</screen>
-   This will create a directory
-   <filename>postgresql-&version;</filename> under the current directory
-   with the <productname>PostgreSQL</> sources.
-   Change into that directory for the rest
-   of the installation procedure.
-  </para>
-<!## end>
-<!## XC>
-&xconly;
-  <para>
-   The <productname>Postgres-XC</> &version; sources can be obtained from
-   its <ulink url="http://postgres-xc.sourceforge.net/">Web site</ulink> or 
-   <ulink url="http://sourceforge.net/projects/postgres-xc/">development site</ulink>.
-   After you have obtained the file, unpack it:
-<screen>
-<userinput>gunzip pgxc-v&version;.tar.gz</userinput>
-<userinput>tar xf pgxc-v&version;.tar</userinput>
-</screen>
-   This will create a directory
-   <filename>pgxc</filename> under the current directory
-   with the <productname>Postgres-XC</> sources.
-   Change into that directory for the rest
-   of the installation procedure.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   The <productname>Postgres-XL</> &version; sources can be obtained from
-   its <ulink url="http://postgres-xl.sourceforge.net/">Web site</ulink> or 
-   <ulink url="http://sourceforge.net/projects/postgres-xl/">development site</ulink>.
-   After you have obtained the file, unpack it:
-<screen>
-<userinput>gunzip pgxl-v&version;.tar.gz</userinput>
-<userinput>tar xf pgxl-v&version;.tar</userinput>
-</screen>
-   This will create a directory
-   <filename>pgxl</filename> under the current directory
-   with the <productname>Postgres-XL</> sources.
-   Change into that directory for the rest
-   of the installation procedure.
-  </para>
-<!## end>
-
-  <para>
-   You can also get the source directly from the version control repository, see
-   <xref linkend="sourcerepo">.
-  </para>
- </sect1>
-]]>
-
- <sect1 id="install-procedure">
-  <title>Installation Procedure</title>
-
-  <procedure>
-
-  <step id="configure">
-   <title>Configuration</title>
-
-   <indexterm zone="configure">
-    <primary>configure</primary>
-   </indexterm>
-
-   <para>
-    The first step of the installation procedure is to configure the
-    source tree for your system and choose the options you would like.
-    This is done by running the <filename>configure</> script. For a
-    default installation simply enter:
-<screen>
-<userinput>./configure</userinput>
-</screen>
-    This script will run a number of tests to determine values for various
-    system dependent variables and detect any quirks of your
-    operating system, and finally will create several files in the
-    build tree to record what it found.  You can also run
-    <filename>configure</filename> in a directory outside the source
-    tree, if you want to keep the build directory separate.  This
-    procedure is also called a
-    <indexterm><primary>VPATH</primary></indexterm><firstterm>VPATH</firstterm>
-    build.  Here's how:
-<screen>
-<userinput>mkdir build_dir</userinput>
-<userinput>cd build_dir</userinput>
-<userinput>/path/to/source/tree/configure [options go here]</userinput>
-<userinput>gmake</userinput>
-</screen>
-   </para>
-
-   <para>
-    The default configuration will build the server and utilities, as
-    well as all client applications and interfaces that require only a
-    C compiler. All files will be installed under
-    <filename>/usr/local/pgsql</> by default.
-   </para>
-
-   <para>
-    You can customize the build and installation process by supplying one
-    or more of the following command line options to
-    <filename>configure</filename>:
-
-     <variablelist>
-      <varlistentry>
-       <term><option>--prefix=<replaceable>PREFIX</></option></term>
-       <listitem>
-        <para>
-         Install all files under the directory <replaceable>PREFIX</>
-         instead of <filename>/usr/local/pgsql</filename>. The actual
-         files will be installed into various subdirectories; no files
-         will ever be installed directly into the
-         <replaceable>PREFIX</> directory.
-        </para>
-
-        <para>
-         If you have special needs, you can also customize the
-         individual subdirectories with the following options. However,
-         if you leave these with their defaults, the installation will be
-         relocatable, meaning you can move the directory after
-         installation. (The <literal>man</> and <literal>doc</>
-         locations are not affected by this.)
-        </para>
-
-        <para>
-         For relocatable installs, you might want to use
-         <filename>configure</filename>'s <literal>--disable-rpath</>
-         option.  Also, you will need to tell the operating system how
-         to find the shared libraries.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--exec-prefix=<replaceable>EXEC-PREFIX</></option></term>
-       <listitem>
-        <para>
-         You can install architecture-dependent files under a
-         different prefix, <replaceable>EXEC-PREFIX</>, than what
-         <replaceable>PREFIX</> was set to. This can be useful to
-         share architecture-independent files between hosts. If you
-         omit this, then <replaceable>EXEC-PREFIX</> is set equal to
-         <replaceable>PREFIX</> and both architecture-dependent and
-         independent files will be installed under the same tree,
-         which is probably what you want.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--bindir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         Specifies the directory for executable programs. The default
-         is <filename><replaceable>EXEC-PREFIX</>/bin</>, which
-         normally means <filename>/usr/local/pgsql/bin</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--sysconfdir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         Sets the directory for various configuration files,
-         <filename><replaceable>PREFIX</>/etc</> by default.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--libdir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         Sets the location to install libraries and dynamically loadable
-         modules. The default is
-         <filename><replaceable>EXEC-PREFIX</>/lib</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--includedir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         Sets the directory for installing C and C++ header files. The
-         default is <filename><replaceable>PREFIX</>/include</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--datarootdir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         Sets the root directory for various types of read-only data
-         files.  This only sets the default for some of the following
-         options.  The default is
-         <filename><replaceable>PREFIX</>/share</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--datadir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         Sets the directory for read-only data files used by the
-         installed programs. The default is
-         <filename><replaceable>DATAROOTDIR</></>. Note that this has
-         nothing to do with where your database files will be placed.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--localedir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         Sets the directory for installing locale data, in particular
-         message translation catalog files.  The default is
-         <filename><replaceable>DATAROOTDIR</>/locale</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--mandir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-<!## PG>
-         The man pages that come with <productname>PostgreSQL</> will be installed under
-<!## end>
-<!## XC>
-         The man pages that come with <productname>Postgres-XC</> will be installed under
-<!## end>
-<!## XL>
-         The man pages that come with <productname>Postgres-XL</> will be installed under
-<!## end>
-         this directory, in their respective
-         <filename>man<replaceable>x</></> subdirectories.
-         The default is <filename><replaceable>DATAROOTDIR</>/man</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--docdir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         Sets the root directory for installing documentation files,
-         except <quote>man</> pages.  This only sets the default for
-         the following options.  The default value for this option is
-         <filename><replaceable>DATAROOTDIR</>/doc/postgresql</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--htmldir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         The HTML-formatted documentation for
-<!## PG>
-         <productname>PostgreSQL</productname> will be installed under
-<!## end>
-<!## XC>
-         <productname>Postgres-XC</productname> will be installed under
-<!## end>
-<!## XL>
-         <productname>Postgres-XL</productname> will be installed under
-<!## end>
-         this directory.  The default is
-         <filename><replaceable>DATAROOTDIR</></>.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-
-     <note>
-      <para>
-       Care has been taken to make it possible to install
-<!## PG>
-       <productname>PostgreSQL</> into shared installation locations
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</> into shared installation locations
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</> into shared installation locations
-<!## end>
-       (such as <filename>/usr/local/include</filename>) without
-       interfering with the namespace of the rest of the system. First,
-       the string <quote><literal>/postgresql</literal></quote> is
-       automatically appended to <varname>datadir</varname>,
-       <varname>sysconfdir</varname>, and <varname>docdir</varname>,
-       unless the fully expanded directory name already contains the
-       string <quote><literal>postgres</></quote> or
-       <quote><literal>pgsql</></quote>. For example, if you choose
-       <filename>/usr/local</filename> as prefix, the documentation will
-       be installed in <filename>/usr/local/doc/postgresql</filename>,
-       but if the prefix is <filename>/opt/postgres</filename>, then it
-       will be in <filename>/opt/postgres/doc</filename>. The public C
-       header files of the client interfaces are installed into
-       <varname>includedir</varname> and are namespace-clean. The
-       internal header files and the server header files are installed
-       into private directories under <varname>includedir</varname>. See
-       the documentation of each interface for information about how to
-       access its header files. Finally, a private subdirectory will
-       also be created, if appropriate, under <varname>libdir</varname>
-       for dynamically loadable modules.
-      </para>
-     </note>
-    </para>
-
-    <para>
-     <variablelist>
-      <varlistentry>
-       <term><option>--with-includes=<replaceable>DIRECTORIES</></option></term>
-       <listitem>
-        <para>
-         <replaceable>DIRECTORIES</> is a colon-separated list of
-         directories that will be added to the list the compiler
-         searches for header files. If you have optional packages
-         (such as GNU <application>Readline</>) installed in a non-standard
-         location,
-         you have to use this option and probably also the corresponding
-         <option>--with-libraries</> option.
-        </para>
-        <para>
-         Example: <literal>--with-includes=/opt/gnu/include:/usr/sup/include</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-libraries=<replaceable>DIRECTORIES</></option></term>
-       <listitem>
-        <para>
-         <replaceable>DIRECTORIES</> is a colon-separated list of
-         directories to search for libraries. You will probably have
-         to use this option (and the corresponding
-         <option>--with-includes</> option) if you have packages
-         installed in non-standard locations.
-        </para>
-        <para>
-         Example: <literal>--with-libraries=/opt/gnu/lib:/usr/sup/lib</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--enable-nls<optional>=<replaceable>LANGUAGES</replaceable></optional></option></term>
-       <listitem>
-        <para>
-         Enables Native Language Support (<acronym>NLS</acronym>),
-         that is, the ability to display a program's messages in a
-         language other than English.
-         <replaceable>LANGUAGES</replaceable> is an optional space-separated
-         list of codes of the languages that you want supported, for
-         example <literal>--enable-nls='de fr'</>.  (The intersection
-         between your list and the set of actually provided
-         translations will be computed automatically.)  If you do not
-         specify a list, then all available translations are
-         installed.
-        </para>
-
-        <para>
-         To use this option, you will need an implementation of the
-         <application>Gettext</> API; see above.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-pgport=<replaceable>NUMBER</></option></term>
-       <listitem>
-        <para>
-         Set <replaceable>NUMBER</> as the default port number for
-         server and clients. The default is 5432. The port can always
-         be changed later on, but if you specify it here then both
-         server and clients will have the same default compiled in,
-         which can be very convenient.  Usually the only good reason
-         to select a non-default value is if you intend to run multiple
-<!## PG>
-         <productname>PostgreSQL</> servers on the same machine.
-<!## end>
-<!## XC>
-         <productname>Postgres-XC</> servers on the same machine.
-<!## end>
-<!## XL>
-         <productname>Postgres-XL</> servers on the same machine.
-<!## end>
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-perl</option></term>
-       <listitem>
-        <para>
-         Build the <application>PL/Perl</> server-side language.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-python</option></term>
-       <listitem>
-        <para>
-         Build the <application>PL/Python</> server-side language.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-tcl</option></term>
-       <listitem>
-        <para>
-         Build the <application>PL/Tcl</> server-side language.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-tclconfig=<replaceable>DIRECTORY</replaceable></option></term>
-       <listitem>
-        <para>
-         Tcl installs the file <filename>tclConfig.sh</filename>, which
-         contains configuration information needed to build modules
-         interfacing to Tcl. This file is normally found automatically
-         at a well-known location, but if you want to use a different
-         version of Tcl you can specify the directory in which to look
-         for it.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-gssapi</option></term>
-       <listitem>
-        <para>
-         Build with support for GSSAPI authentication. On many
-         systems, the GSSAPI (usually a part of the Kerberos installation)
-         system is not installed in a location
-         that is searched by default (e.g., <filename>/usr/include</>,
-         <filename>/usr/lib</>), so you must use the options
-         <option>--with-includes</> and <option>--with-libraries</> in
-         addition to this option.  <filename>configure</> will check
-         for the required header files and libraries to make sure that
-         your GSSAPI installation is sufficient before proceeding.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-krb5</option></term>
-       <listitem>
-        <para>
-         Build with support for Kerberos 5 authentication. On many
-         systems, the Kerberos system is not installed in a location
-         that is searched by default (e.g., <filename>/usr/include</>,
-         <filename>/usr/lib</>), so you must use the options
-         <option>--with-includes</> and <option>--with-libraries</> in
-         addition to this option.  <filename>configure</> will check
-         for the required header files and libraries to make sure that
-         your Kerberos installation is sufficient before proceeding.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-krb-srvnam=<replaceable>NAME</></option></term>
-       <listitem>
-        <para>
-         The default name of the Kerberos service principal (also used
-         by GSSAPI).
-         <literal>postgres</literal> is the default. There's usually no
-         reason to change this unless you have a Windows environment,
-         in which case it must be set to upper case
-         <literal>POSTGRES</literal>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <indexterm>
-        <primary>OpenSSL</primary>
-        <seealso>SSL</seealso>
-       </indexterm>
-
-       <term><option>--with-openssl</option></term>
-       <listitem>
-        <para>
-         Build with support for <acronym>SSL</> (encrypted)
-         connections. This requires the <productname>OpenSSL</>
-         package to be installed.  <filename>configure</> will check
-         for the required header files and libraries to make sure that
-         your <productname>OpenSSL</> installation is sufficient
-         before proceeding.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-pam</option></term>
-       <listitem>
-        <para>
-         Build with <acronym>PAM</><indexterm><primary>PAM</></>
-         (Pluggable Authentication Modules) support.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-ldap</option></term>
-       <listitem>
-        <para>
-         Build with <acronym>LDAP</><indexterm><primary>LDAP</></>
-         support for authentication and connection parameter lookup (see
-         <![%standalone-include[the documentation about client authentication
-         and libpq]]><![%standalone-ignore[<xref linkend="libpq-ldap"> and
-         <xref linkend="auth-ldap">]]> for more information). On Unix,
-         this requires the <productname>OpenLDAP</> package to be
-         installed. On Windows, the default <productname>WinLDAP</>
-         library is used.  <filename>configure</> will check for the required
-         header files and libraries to make sure that your
-         <productname>OpenLDAP</> installation is sufficient before
-         proceeding.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--without-readline</option></term>
-       <listitem>
-        <para>
-         Prevents use of the <application>Readline</> library
-         (and <application>libedit</> as well).  This option disables
-         command-line editing and history in
-         <application>psql</application>, so it is not recommended.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-libedit-preferred</option></term>
-       <listitem>
-        <para>
-         Favors the use of the BSD-licensed <application>libedit</> library
-         rather than GPL-licensed <application>Readline</>.  This option
-         is significant only if you have both libraries installed; the
-         default in that case is to use <application>Readline</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-bonjour</option></term>
-       <listitem>
-        <para>
-         Build with Bonjour support.  This requires Bonjour support
-         in your operating system.  Recommended on Mac OS X.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-ossp-uuid</option></term>
-       <listitem>
-        <para>
-         Build components using the <ulink
-         url="http://www.ossp.org/pkg/lib/uuid/">OSSP UUID
-         library</ulink>.  Specifically, build the
-         <![%standalone-include[uuid-ossp]]>
-         <![%standalone-ignore[<xref linkend="uuid-ossp">]]> module,
-         which provides functions to generate
-         UUIDs.<indexterm><primary>UUID</primary></indexterm>
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-libxml</option></term>
-       <listitem>
-        <para>
-         Build with libxml (enables SQL/XML support).  Libxml version 2.6.23 or
-         later is required for this feature.
-        </para>
-
-        <para>
-         Libxml installs a program <command>xml2-config</command> that
-         can be used to detect the required compiler and linker
-<!## PG>
-         options.  PostgreSQL will use it automatically if found.  To
-<!## end>
-<!## XC>
-         options.  Postgres-XC will use it automatically if found.  To
-<!## end>
-<!## XL>
-         options.  Postgres-XL will use it automatically if found.  To
-<!## end>
-         specify a libxml installation at an unusual location, you can
-         either set the environment variable
-         <envar>XML2_CONFIG</envar> to point to the
-         <command>xml2-config</command> program belonging to the
-         installation, or use the options
-         <option>--with-includes</option> and
-         <option>--with-libraries</option>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-libxslt</option></term>
-       <listitem>
-        <para>
-         Use libxslt when building the
-         <![%standalone-include[xml2]]>
-         <![%standalone-ignore[<xref linkend="xml2">]]>
-         module.  <application>xml2</> relies on this library
-         to perform XSL transformations of XML.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--disable-integer-datetimes</option></term>
-       <listitem>
-        <para>
-         Disable support for 64-bit integer storage for timestamps and
-         intervals, and store datetime values as floating-point
-         numbers instead. Floating-point datetime storage was the
-<!## PG>
-         default in <productname>PostgreSQL</productname> releases
-<!## end>
-<!## XC>
-         default in <productname>Postgres-XC</productname> releases
-<!## end>
-<!## XL>
-         default in <productname>Postgres-XL</productname> releases
-<!## end>
-         prior to 8.4, but it is now deprecated, because it does not
-         support microsecond precision for the full range of
-         <type>timestamp</type> values. However, integer-based
-         datetime storage requires a 64-bit integer type. Therefore,
-         this option can be used when no such type is available, or
-         for compatibility with applications written for prior
-<!## PG>
-         versions of <productname>PostgreSQL</productname>. See
-<!## end>
-<!## XC>
-         versions of <productname>Postgres-XC</productname>. See
-<!## end>
-<!## XL>
-         versions of <productname>Postgres-XL</productname>. See
-<!## end>
-         <![%standalone-include[the documentation about datetime datatypes]]>
-         <![%standalone-ignore[<xref linkend="datatype-datetime">]]>
-         for more information.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--disable-float4-byval</option></term>
-       <listitem>
-        <para>
-         Disable passing float4 values <quote>by value</>, causing them
-         to be passed <quote>by reference</> instead.  This option costs
-         performance, but may be needed for compatibility with old
-         user-defined functions that are written in C and use the
-         <quote>version 0</> calling convention.  A better long-term
-         solution is to update any such functions to use the
-         <quote>version 1</> calling convention.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--disable-float8-byval</option></term>
-       <listitem>
-        <para>
-         Disable passing float8 values <quote>by value</>, causing them
-         to be passed <quote>by reference</> instead.  This option costs
-         performance, but may be needed for compatibility with old
-         user-defined functions that are written in C and use the
-         <quote>version 0</> calling convention.  A better long-term
-         solution is to update any such functions to use the
-         <quote>version 1</> calling convention.
-         Note that this option affects not only float8, but also int8 and some
-         related types such as timestamp.
-         On 32-bit platforms, <option>--disable-float8-byval</> is the default
-         and it is not allowed to select <option>--enable-float8-byval</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-segsize=<replaceable>SEGSIZE</replaceable></option></term>
-       <listitem>
-        <para>
-         Set the <firstterm>segment size</>, in gigabytes.  Large tables are
-         divided into multiple operating-system files, each of size equal
-         to the segment size.  This avoids problems with file size limits
-         that exist on many platforms.  The default segment size, 1 gigabyte,
-         is safe on all supported platforms.  If your operating system has
-         <quote>largefile</> support (which most do, nowadays), you can use
-         a larger segment size.  This can be helpful to reduce the number of
-         file descriptors consumed when working with very large tables.
-         But be careful not to select a value larger than is supported
-         by your platform and the file systems you intend to use.  Other
-         tools you might wish to use, such as <application>tar</>, could
-         also set limits on the usable file size.
-         It is recommended, though not absolutely required, that this value
-         be a power of 2.
-         Note that changing this value requires an initdb.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-blocksize=<replaceable>BLOCKSIZE</replaceable></option></term>
-       <listitem>
-        <para>
-         Set the <firstterm>block size</>, in kilobytes.  This is the unit
-         of storage and I/O within tables.  The default, 8 kilobytes,
-         is suitable for most situations; but other values may be useful
-         in special cases.
-         The value must be a power of 2 between 1 and 32 (kilobytes).
-         Note that changing this value requires an initdb.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-wal-segsize=<replaceable>SEGSIZE</replaceable></option></term>
-       <listitem>
-        <para>
-         Set the <firstterm>WAL segment size</>, in megabytes.  This is
-         the size of each individual file in the WAL log.  It may be useful
-         to adjust this size to control the granularity of WAL log shipping.
-         The default size is 16 megabytes.
-         The value must be a power of 2 between 1 and 64 (megabytes).
-         Note that changing this value requires an initdb.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-wal-blocksize=<replaceable>BLOCKSIZE</replaceable></option></term>
-       <listitem>
-        <para>
-         Set the <firstterm>WAL block size</>, in kilobytes.  This is the unit
-         of storage and I/O within the WAL log.  The default, 8 kilobytes,
-         is suitable for most situations; but other values may be useful
-         in special cases.
-         The value must be a power of 2 between 1 and 64 (kilobytes).
-         Note that changing this value requires an initdb.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--disable-spinlocks</option></term>
-       <listitem>
-        <para>
-<!## PG>
-         Allow the build to succeed even if <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-         Allow the build to succeed even if <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-         Allow the build to succeed even if <productname>Postgres-XL</>
-<!## end>
-         has no CPU spinlock support for the platform.  The lack of
-         spinlock support will result in poor performance; therefore,
-         this option should only be used if the build aborts and
-         informs you that the platform lacks spinlock support. If this
-<!## PG>
-         option is required to build <productname>PostgreSQL</> on
-<!## end>
-<!## XC>
-         option is required to build <productname>Postgres-XC</> on
-<!## end>
-<!## XL>
-         option is required to build <productname>Postgres-XL</> on
-<!## end>
-         your platform, please report the problem to the
-<!## PG>
-         <productname>PostgreSQL</> developers.
-<!## end>
-<!## XC>
-         <productname>Postgres-XC</> developers.
-<!## end>
-<!## XL>
-         <productname>Postgres-XL</> developers.
-<!## end>
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--disable-thread-safety</option></term>
-       <listitem>
-        <para>
-         Disable the thread-safety of client libraries.  This prevents
-         concurrent threads in <application>libpq</application> and
-         <application>ECPG</application> programs from safely controlling
-         their private connection handles.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-system-tzdata=<replaceable>DIRECTORY</replaceable></option></term>
-       <indexterm>
-        <primary>time zone data</primary>
-       </indexterm>
-       <listitem>
-        <para>
-<!## PG>
-         <productname>PostgreSQL</> includes its own time zone database,
-<!## end>
-<!## XC>
-         <productname>Postgres-XC</> includes its own time zone database,
-<!## end>
-<!## XL>
-         <productname>Postgres-XL</> includes its own time zone database,
-<!## end>
-         which it requires for date and time operations.  This time zone
-         database is in fact compatible with the <quote>zoneinfo</> time zone
-         database provided by many operating systems such as FreeBSD,
-         Linux, and Solaris, so it would be redundant to install it again.
-         When this option is used, the system-supplied time zone database
-         in <replaceable>DIRECTORY</replaceable> is used instead of the one
-         included in the PostgreSQL source distribution.
-         <replaceable>DIRECTORY</replaceable> must be specified as an
-         absolute path.  <filename>/usr/share/zoneinfo</filename> is a
-         likely directory on some operating systems.  Note that the
-         installation routine will not detect mismatching or erroneous time
-         zone data.  If you use this option, you are advised to run the
-         regression tests to verify that the time zone data you have
-<!## PG>
-         pointed to works correctly with <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-         pointed to works correctly with <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-         pointed to works correctly with <productname>Postgres-XL</>.
-<!## end>
-        </para>
-
-        <indexterm><primary>cross compilation</primary></indexterm>
-
-        <para>
-         This option is mainly aimed at binary package distributors
-         who know their target operating system well.  The main
-<!## PG>
-         advantage of using this option is that the PostgreSQL package
-<!## end>
-<!## XC>
-         advantage of using this option is that the Postgres-XC package
-<!## end>
-<!## XL>
-         advantage of using this option is that the Postgres-XL package
-<!## end>
-         won't need to be upgraded whenever any of the many local
-         daylight-saving time rules change.  Another advantage is that
-<!## PG>
-         PostgreSQL can be cross-compiled more straightforwardly if the
-<!## end>
-<!## XC>
-         Postgres-XC can be cross-compiled more straightforwardly if the
-<!## end>
-<!## XL>
-         Postgres-XL can be cross-compiled more straightforwardly if the
-<!## end>
-         time zone database files do not need to be built during the
-         installation.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--without-zlib</option></term>
-       <listitem>
-        <para>
-         <indexterm>
-          <primary>zlib</primary>
-         </indexterm>
-         Prevents use of the <application>Zlib</> library.  This disables
-         support for compressed archives in <application>pg_dump</application>
-         and <application>pg_restore</application>.
-         This option is only intended for those rare systems where this
-         library is not available.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--enable-debug</option></term>
-       <listitem>
-        <para>
-         Compiles all programs and libraries with debugging symbols.
-         This means that you can run the programs in a debugger
-         to analyze problems. This enlarges the size of the installed
-         executables considerably, and on non-GCC compilers it usually
-         also disables compiler optimization, causing slowdowns. However,
-         having the symbols available is extremely helpful for dealing
-         with any problems that might arise.  Currently, this option is
-         recommended for production installations only if you use GCC.
-         But you should always have it on if you are doing development work
-         or running a beta version.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--enable-coverage</option></term>
-       <listitem>
-        <para>
-<!## PG>
-         If using GCC, all programs and libraries are compiled with
-         code coverage testing instrumentation.  When run, they
-         generate files in the build directory with code coverage
-         metrics.
-         <![%standalone-ignore[See <xref linkend="regress-coverage">
-         for more information.]]> This option is for use only with GCC
-         and when doing development work.
-<!## end>
-<!## XC>
-         <!-- regress-coverage is not included in XC reference -->
-         If using GCC, all programs and libraries are compiled with
-         code coverage testing instrumentation.  When run, they
-         generate files in the build directory with code coverage
-         metrics.
-         This option is for use only with GCC
-         and when doing development work.
-<!## end>
-<!## XL>
-         <!-- regress-coverage is not included in XL reference -->
-         If using GCC, all programs and libraries are compiled with
-         code coverage testing instrumentation.  When run, they
-         generate files in the build directory with code coverage
-         metrics.
-         This option is for use only with GCC
-         and when doing development work.
-<!## end>
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--enable-profiling</option></term>
-       <listitem>
-        <para>
-         If using GCC, all programs and libraries are compiled so they
-         can be profiled.  On backend exit, a subdirectory will be created
-         that contains the <filename>gmon.out</> file for use in profiling.
-         This option is for use only with GCC and when doing development work.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--enable-cassert</option></term>
-       <listitem>
-        <para>
-         Enables <firstterm>assertion</> checks in the server, which test for
-         many <quote>cannot happen</> conditions.  This is invaluable for
-         code development purposes, but the tests can slow down the
-         server significantly.
-         Also, having the tests turned on won't necessarily enhance the
-         stability of your server!  The assertion checks are not categorized
-         for severity, and so what might be a relatively harmless bug will
-         still lead to server restarts if it triggers an assertion
-         failure.  This option is not recommended for production use, but
-         you should have it on for development work or when running a beta
-         version.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--enable-depend</option></term>
-       <listitem>
-        <para>
-         Enables automatic dependency tracking.  With this option, the
-         makefiles are set up so that all affected object files will
-         be rebuilt when any header file is changed.  This is useful
-         if you are doing development work, but is just wasted overhead
-         if you intend only to compile once and install.  At present,
-         this option only works with GCC.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--enable-dtrace</option></term>
-       <listitem>
-        <para>
-         <indexterm>
-          <primary>DTrace</primary>
-         </indexterm>
-<!## PG>
-         Compiles <productname>PostgreSQL</productname> with support for the
-<!## end>
-<!## XC>
-         Compiles <productname>Postgres-XC</productname> with support for the
-<!## end>
-<!## XL>
-         Compiles <productname>Postgres-XL</productname> with support for the
-<!## end>
-         dynamic tracing tool DTrace.
-         <![%standalone-ignore[See <xref linkend="dynamic-trace">
-         for more information.]]>
-        </para>
-
-        <para>
-         To point to the <command>dtrace</command> program, the
-         environment variable <envar>DTRACE</envar> can be set.  This
-         will often be necessary because <command>dtrace</command> is
-         typically installed under <filename>/usr/sbin</filename>,
-         which might not be in the path.
-        </para>
-
-        <para>
-         Extra command-line options for the <command>dtrace</command> program
-         can be specified in the environment variable
-         <envar>DTRACEFLAGS</envar>.  On Solaris,
-         to include DTrace support in a 64-bit binary, you must specify
-         <literal>DTRACEFLAGS="-64"</> to configure.  For example,
-         using the GCC compiler:
-<screen>
-./configure CC='gcc -m64' --enable-dtrace DTRACEFLAGS='-64' ...
-</screen>
-         Using Sun's compiler:
-<screen>
-./configure CC='/opt/SUNWspro/bin/cc -xtarget=native64' --enable-dtrace DTRACEFLAGS='-64' ...
-</screen>
-        </para>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-    </para>
-
-    <para>
-     If you prefer a C compiler different from the one
-     <filename>configure</filename> picks, you can set the
-     environment variable <envar>CC</> to the program of your choice.
-     By default, <filename>configure</filename> will pick
-     <filename>gcc</filename> if available, else the platform's
-     default (usually <filename>cc</>).  Similarly, you can override the
-     default compiler flags if needed with the <envar>CFLAGS</envar> variable.
-    </para>
-
-    <para>
-     You can specify environment variables on the
-     <filename>configure</filename> command line, for example:
-<!## PG>
-<screen>
-<userinput>./configure CC=/opt/bin/gcc CFLAGS='-O2 -pipe'</>
-</screen>
-<!## end>
-<!## XC>
-<screen>
-<userinput>./configure CC=/opt/bin/gcc CFLAGS='-O2 -pipe -DPGXC'</>
-</screen>
-     Please note that you need to specify <filename>-DPGXC</>
-     explicitly to specify <filename>CFLAGS</> option.
-<!## end>
-<!## XL>
-<screen>
-<userinput>./configure CC=/opt/bin/gcc CFLAGS='-O2 -pipe -DPGXL'</>
-</screen>
-     Please note that you need to specify <filename>-DPGXL</>
-     explicitly to specify <filename>CFLAGS</> option.
-<!## end>
-    </para>
-
-    <para>
-     Here is a list of the significant variables that can be set in
-     this manner:
-
-     <variablelist>
-      <varlistentry>
-       <term><envar>BISON</envar></term>
-       <listitem>
-        <para>
-         Bison program
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>CC</envar></term>
-       <listitem>
-        <para>
-         C compiler
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>CFLAGS</envar></term>
-       <listitem>
-        <para>
-         options to pass to the C compiler
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>CPP</envar></term>
-       <listitem>
-        <para>
-         C preprocessor
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>CPPFLAGS</envar></term>
-       <listitem>
-        <para>
-         options to pass to the C preprocessor
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>DTRACE</envar></term>
-       <listitem>
-        <para>
-         location of the <command>dtrace</command> program
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>DTRACEFLAGS</envar></term>
-       <listitem>
-        <para>
-         options to pass to the <command>dtrace</command> program
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>FLEX</envar></term>
-       <listitem>
-        <para>
-         Flex program
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>LDFLAGS</envar></term>
-       <listitem>
-        <para>
-         options to use when linking either executables or shared libraries
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>LDFLAGS_EX</envar></term>
-       <listitem>
-        <para>
-         additional options for linking executables only
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>LDFLAGS_SL</envar></term>
-       <listitem>
-        <para>
-         additional options for linking shared libraries only
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>MSGFMT</envar></term>
-       <listitem>
-        <para>
-         <command>msgfmt</command> program for native language support
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>PERL</envar></term>
-       <listitem>
-        <para>
-         Full path to the Perl interpreter.  This will be used to
-         determine the dependencies for building PL/Perl.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>PYTHON</envar></term>
-       <listitem>
-        <para>
-         Full path to the Python interpreter.  This will be used to
-         determine the dependencies for building PL/Python.  Also,
-         whether Python 2 or 3 is specified here (or otherwise
-         implicitly chosen) determines which variant of the PL/Python
-         language becomes available.  See
-         <![%standalone-include[the <application>PL/Python</>
-         documentation]]>
-         <![%standalone-ignore[<xref linkend="plpython-python23">]]>
-         for more information.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>TCLSH</envar></term>
-       <listitem>
-        <para>
-         Full path to the Tcl interpreter.  This will be used to
-         determine the dependencies for building PL/Tcl, and it will
-         be substituted into Tcl scripts.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><envar>XML2_CONFIG</envar></term>
-       <listitem>
-        <para>
-         <command>xml2-config</command> program used to locate the
-         libxml installation.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-   </step>
-
-  <step id="build">
-   <title>Build</title>
-
-   <para>
-    To start the build, type:
-<screen>
-<userinput>gmake</userinput>
-</screen>
-    (Remember to use <acronym>GNU</> <application>make</>.) The build
-    will take a few minutes depending on your
-    hardware. The last line displayed should be:
-<screen>
-<!## PG>
-All of PostgreSQL is successfully made. Ready to install.
-<!## end>
-<!## XC>
-All of Postgres-XC is successfully made. Ready to install.
-<!## end>
-<!## XL>
-All of Postgres-XL is successfully made. Ready to install.
-<!## end>
-</screen>
-   </para>
-
-  <para>
-   If you want to build everything that can be built, including the
-   documentation (HTML and man pages), and the additional modules
-   (<filename>contrib</filename>), type instead:
-<screen>
-<userinput>gmake world</userinput>
-</screen>
-   The last line displayed should be:
-<!## PG>
-<screen>
-PostgreSQL, contrib and HTML documentation successfully made. Ready to install.
-</screen>
-<!## end>
-<!## XC>
-<screen>
-Postgres-XC, contrib and HTML documentation successfully made. Ready to install.
-</screen>
-<!## end>
-<!## XL>
-<screen>
-Postgres-XL, contrib and HTML documentation successfully made. Ready to install.
-</screen>
-<!## end>
-   </para>
-  </step>
-
-<!## PG>
-
-  <step>
-   <title>Regression Tests</title>
-
-   <indexterm>
-    <primary>regression test</primary>
-   </indexterm>
-
-   <para>
-    If you want to test the newly built server before you install it,
-    you can run the regression tests at this point. The regression
-    tests are a test suite to verify that <productname>PostgreSQL</>
-    runs on your machine in the way the developers expected it
-    to. Type:
-<screen>
-<userinput>gmake check</userinput>
-</screen>
-    (This won't work as root; do it as an unprivileged user.)
-    <![%standalone-include[The file
-    <filename>src/test/regress/README</> and the
-    documentation contain]]>
-    <![%standalone-ignore[<xref linkend="regress"> contains]]>
-    detailed information about interpreting the test results. You can
-    repeat this test at any later time by issuing the same command.
-   </para>
-  </step>
-<!## end>
-
-  <step id="install">
-   <title>Installing the Files</title>
-
-   <note>
-    <para>
-     If you are upgrading an existing system be sure to read
-     <![%standalone-include[the documentation,]]>
-     <![%standalone-ignore[<xref linkend="upgrading">]]>
-     which has instructions about upgrading a
-     cluster.
-    </para>
-   </note>
-<!## XC>
-   <para>
-    Before learning how to install <productname>Postgres-XC</>, you should learn
-    what you are going to install to what server.  The following lists
-    <productname>Postgres-XC</> components you've built and you're going to install.
-
-    <variablelist>
-     <varlistentry>
-      <term><envar>GTM</envar></term>
-      <listitem>
-       <para>
-        GTM stands for global transaction manager.  It provides global transaction ID
-        and snapshot to each transaction in <productname>Postgres-XC</> database cluster.
-        It also provide several global value such as sequence and global timestamp.
-       </para>
-       <para>
-        GTM itself can be configured as a backup of other GTM as
-        GTM-Standby so that GTM can continue to run even if main GTM
-        fails.  You may want to install GTM-Standby to separate
-        server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><envar>GTM-Proxy</envar></term>
-      <listitem>
-      <para>
-       Because GTM has to take care of each transaction, it has to
-       read and write enormous amount of messages which may
-       restrict <productname>Postgres-XC</> scalability.  GTM-Proxy is
-       a proxy of GTM feature which groups requests and response to
-       reduce network read/write by GTM.  Distributing one snapshot to
-       multiple transactions also contributes to reduce GTM network
-       workload.
-      </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><envar>Coordinator</envar></term>
-      <listitem>
-       <para>
-        Coordinator is an entry point to <productname>Postgres-XC</> from applications.
-        You can run more than one Coordinator in parallel.   Each Coordinator behaves
-        as just <productname>PostgreSQL</> database server, while all the Coordinators
-        handles transactions in harmonized way so that any transaction coming into one
-        Coordinator is protected against any other transactions coming into others.
-        Updates by a transaction is visible immediately to others running in other
-        Coordinators.
-        To simplify the load balance of Coordinators and Datanodes, as mentioned
-        below, it is highly advised to install same number of Coordinator and Datanode
-        in a server.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><envar>Datanode</envar></term>
-      <listitem>
-       <para>
-        Datanode 
-       </para>
-       <para>
-        Coordinator and Datanode shares the same binary but their behavior is a little
-        different.   Coordinator decomposes incoming statements into those handled by
-        Datanodes.   If necessary, Coordinator materializes response from Datanodes
-        to calculate final response to applications.
-       </para>
-       <para>
-        Datanode is very close to PostgreSQL itself because it just handles incoming
-        statements locally.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-<!## end>
-<!## XL>
-   <para>
-    Before learning how to install <productname>Postgres-XL</>, you should determine
-    what you are going to install on each server.  The following lists
-    <productname>Postgres-XL</> components you've built and you're going to install.
-
-    <variablelist>
-     <varlistentry>
-      <term><envar>GTM</envar></term>
-      <listitem>
-       <para>
-        GTM stands for Global Transaction Manager.  It provides global transaction ID
-        and snapshot to each transaction in <productname>Postgres-XL</> database cluster.
-        It also provide several global value such as sequence and global timestamp.
-       </para>
-       <para>
-        GTM itself can be configured as a backup of other GTM as
-        GTM-Standby so that GTM can continue to run even if main GTM
-        fails.  You may want to install GTM-Standby to separate
-        server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><envar>GTM-Proxy</envar></term>
-      <listitem>
-      <para>
-       Because GTM has to take care of each transaction, it has to
-       read and write enormous amount of messages which may
-       restrict <productname>Postgres-XL</> scalability.  GTM-Proxy is
-       a proxy of GTM feature which groups requests and response to
-       reduce network read/write by GTM.  Distributing one snapshot to
-       multiple transactions also contributes to reduce GTM network
-       workload.
-      </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><envar>Coordinator</envar></term>
-      <listitem>
-       <para>
-        The Coordinator is an entry point to <productname>Postgres-XL</> from applications.
-        You can run more than one Coordinator simultaneously in the cluster.   Each Coordinator behaves
-        just as a <productname>PostgreSQL</> database server, while all the Coordinators
-        handles transactions in harmonized way so that any transaction coming into one
-        Coordinator is protected against any other transactions coming into others.
-        Updates by a transaction is visible immediately to others running in other
-        Coordinators.
-        To simplify the load balance of Coordinators and Datanodes, as mentioned
-        below, it is highly advised to install same number of Coordinator and Datanode
-        in a server.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><envar>Datanode</envar></term>
-      <listitem>
-       <para>
-        Datanode 
-       </para>
-       <para>
-        The Coordinator and Datanode shares the same binary but their behavior is a little
-        different.  The Coordinator decomposes incoming statements into those handled by
-        Datanodes.  If necessary, the Coordinator materializes response from Datanodes
-        to calculate final response to applications.
-       </para>
-       <para>
-        The Datanode is very close to PostgreSQL itself because it just handles incoming
-        statements locally.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-<!## end>
-
-   <para>
-<!## PG>
-    To install <productname>PostgreSQL</> enter:
-<!## end>
-<!## XC>
-    To install <productname>Postgres-XC</> enter:
-<!## end>
-<!## XL>
-    To install <productname>Postgres-XL</> enter:
-<!## end>
-<screen>
-<userinput>gmake install</userinput>
-</screen>
-    This will install files into the directories that were specified
-    in <xref linkend="configure">. Make sure that you have appropriate
-    permissions to write into that area. Normally you need to do this
-    step as root. Alternatively, you can create the target
-    directories in advance and arrange for appropriate permissions to
-    be granted.
-   </para>
-
-   <para>
-<!## PG>
-    To install the documentation (HTML and man pages), enter:
-<!## end>
-<!## XC>
-    To install the documentation (HTML and man pages), enter:
-<!## end>
-<!## XL>
-    To install the documentation (HTML and man pages), enter:
-<!## end>
-<screen>
-<userinput>gmake install-docs</userinput>
-</screen>
-   </para>
-
-   <para>
-    If you built the world above, type instead:
-<screen>
-<userinput>gmake install-world</userinput>
-</screen>
-    This also installs the documentation.
-   </para>
-
-   <para>
-    You can use <literal>gmake install-strip</literal> instead of
-    <literal>gmake install</literal> to strip the executable files and
-    libraries as they are installed.  This will save some space.  If
-    you built with debugging support, stripping will effectively
-    remove the debugging support, so it should only be done if
-    debugging is no longer needed.  <literal>install-strip</literal>
-    tries to do a reasonable job saving space, but it does not have
-    perfect knowledge of how to strip every unneeded byte from an
-    executable file, so if you want to save all the disk space you
-    possibly can, you will have to do manual work.
-   </para>
-
-   <para>
-    The standard installation provides all the header files needed for client
-    application development as well as for server-side program
-    development, such as custom functions or data types written in C.
-    (Prior to <productname>PostgreSQL</> 8.0, a separate <literal>gmake
-    install-all-headers</> command was needed for the latter, but this
-    step has been folded into the standard install.)
-   </para>
-
-   <formalpara>
-    <title>Client-only installation:</title>
-    <para>
-     If you want to install only the client applications and
-     interface libraries, then you can use these commands:
-<screen>
-<userinput>gmake -C src/bin install</>
-<userinput>gmake -C src/include install</>
-<userinput>gmake -C src/interfaces install</>
-<userinput>gmake -C doc install</>
-</screen>
-    <filename>src/bin</> has a few binaries for server-only use,
-    but they are small.
-    </para>
-   </formalpara>
-  </step>
-  </procedure>
-
-<!## PG>
-  <formalpara>
-   <title>Registering <application>eventlog</> on <systemitem
-   class="osname">Windows</>:</title>
-   <para>
-    To register a <systemitem class="osname">Windows</> <application>eventlog</>
-    library with the operating system, issue this command after installation:
-<screen>
-<userinput>regsvr32 <replaceable>pgsql_library_directory</>/pgevent.dll</>
-</screen>
-    This creates registry entries used by the event viewer.
-   </para>
-  </formalpara>
-<!## end>
-
-  <formalpara>
-   <title>Uninstallation:</title>
-   <para>
-    To undo the installation use the command <command>gmake
-    uninstall</>. However, this will not remove any created directories.
-   </para>
-  </formalpara>
-
-  <formalpara>
-   <title>Cleaning:</title>
-
-   <para>
-    After the installation you can free disk space by removing the built
-    files from the source tree with the command <command>gmake
-    clean</>. This will preserve the files made by the <command>configure</command>
-    program, so that you can rebuild everything with <command>gmake</>
-    later on. To reset the source tree to the state in which it was
-    distributed, use <command>gmake distclean</>. If you are going to
-    build for several platforms within the same source tree you must do
-    this and re-configure for each platform.  (Alternatively, use
-    a separate build tree for each platform, so that the source tree
-    remains unmodified.)
-   </para>
-  </formalpara>
-
-  <para>
-   If you perform a build and then discover that your <command>configure</>
-   options were wrong, or if you change anything that <command>configure</>
-   investigates (for example, software upgrades), then it's a good
-   idea to do <command>gmake distclean</> before reconfiguring and
-   rebuilding.  Without this, your changes in configuration choices
-   might not propagate everywhere they need to.
-  </para>
- </sect1>
-
- <sect1 id="install-post">
-  <title>Post-Installation Setup</title>
-  <sect2>
-   <title>Shared Libraries</title>
-
-   <indexterm>
-    <primary>shared library</primary>
-   </indexterm>
-   <para>
-<!## PG>
-    On some systems with shared libraries
-    you need to tell the system how to find the newly installed
-    shared libraries.  The systems on which this is
-    <emphasis>not</emphasis> necessary include <systemitem
-    class="osname">BSD/OS</>, <systemitem class="osname">FreeBSD</>,
-    <systemitem class="osname">HP-UX</>, <systemitem
-    class="osname">IRIX</>, <systemitem class="osname">Linux</>,
-    <systemitem class="osname">NetBSD</>, <systemitem
-    class="osname">OpenBSD</>, <systemitem class="osname">Tru64
-    UNIX</> (formerly <systemitem class="osname">Digital UNIX</>), and
-    <systemitem class="osname">Solaris</>.
-<!## end>
-<!## XC>
-    On some systems with shared libraries
-    you need to tell the system how to find the newly installed
-    shared libraries.
-    However, <systemitem class="osname">Linux</> does <emphasis>not</> need this.
-<!## end>
-<!## XL>
-    On some systems with shared libraries
-    you need to tell the system how to find the newly installed
-    shared libraries.
-    However, <systemitem class="osname">Linux</> does <emphasis>not</> need this.
-<!## end>
-   </para>
-
-   <para>
-    The method to set the shared library search path varies between
-    platforms, but the most widely-used method is to set the
-    environment variable <envar>LD_LIBRARY_PATH</> like so: In Bourne
-    shells (<command>sh</>, <command>ksh</>, <command>bash</>, <command>zsh</>):
-<programlisting>
-LD_LIBRARY_PATH=/usr/local/pgsql/lib
-export LD_LIBRARY_PATH
-</programlisting>
-    or in <command>csh</> or <command>tcsh</>:
-<programlisting>
-setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
-</programlisting>
-    Replace <literal>/usr/local/pgsql/lib</> with whatever you set
-    <option><literal>--libdir</></> to in <xref linkend="configure">.
-    You should put these commands into a shell start-up file such as
-    <filename>/etc/profile</> or <filename>~/.bash_profile</>.  Some
-    good information about the caveats associated with this method can
-    be found at <ulink
-    url="http://xahlee.org/UnixResource_dir/_/ldpath.html"></ulink>.
-   </para>
-
-   <para>
-    On some systems it might be preferable to set the environment
-    variable <envar>LD_RUN_PATH</envar> <emphasis>before</emphasis>
-    building.
-   </para>
-
-   <para>
-    On <systemitem class="osname">Cygwin</systemitem>, put the library
-    directory in the <envar>PATH</envar> or move the
-    <filename>.dll</filename> files into the <filename>bin</filename>
-    directory.
-   </para>
-
-   <para>
-    If in doubt, refer to the manual pages of your system (perhaps
-    <command>ld.so</command> or <command>rld</command>). If you later
-    get a message like:
-<screen>
-psql: error in loading shared libraries
-libpq.so.2.1: cannot open shared object file: No such file or directory
-</screen>
-    then this step was necessary.  Simply take care of it then.
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>ldconfig</primary>
-    </indexterm>
-<!## PG>
-    If you are on <systemitem class="osname">BSD/OS</>, <systemitem
-    class="osname">Linux</>, or <systemitem class="osname">SunOS 4</>
-    and you have root access you can run:
-<!## end>
-<!## XC>
-    Because you are <systemitem
-    class="osname">Linux</>, 
-    you have root access and you can run:
-<!## end>
-<!## XL>
-    Because you are <systemitem
-    class="osname">Linux</>, 
-    you have root access and you can run:
-<!## end>
-<programlisting>
-/sbin/ldconfig /usr/local/pgsql/lib
-</programlisting>
-<!## PG>
-    (or equivalent directory) after installation to enable the
-    run-time linker to find the shared libraries faster.  Refer to the
-    manual page of <command>ldconfig</> for more information.  On
-    <systemitem class="osname">FreeBSD</>, <systemitem
-    class="osname">NetBSD</>, and <systemitem
-    class="osname">OpenBSD</> the command is:
-<programlisting>
-/sbin/ldconfig -m /usr/local/pgsql/lib
-</programlisting>
-    instead.  Other systems are not known to have an equivalent
-    command.
-<!## end>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Environment Variables</title>
-
-   <indexterm>
-    <primary><envar>PATH</envar></primary>
-   </indexterm>
-
-   <para>
-    If you installed into <filename>/usr/local/pgsql</> or some other
-    location that is not searched for programs by default, you should
-    add <filename>/usr/local/pgsql/bin</> (or whatever you set
-    <option><literal>--bindir</></> to in <xref linkend="configure">)
-    into your <envar>PATH</>.  Strictly speaking, this is not
-<!## PG>
-    necessary, but it will make the use of <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-    necessary, but it will make the use of <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-    necessary, but it will make the use of <productname>Postgres-XL</>
-<!## end>
-    much more convenient.
-   </para>
-
-   <para>
-    To do this, add the following to your shell start-up file, such as
-    <filename>~/.bash_profile</> (or <filename>/etc/profile</>, if you
-    want it to affect all users):
-<programlisting>
-PATH=/usr/local/pgsql/bin:$PATH
-export PATH
-</programlisting>
-    If you are using <command>csh</> or <command>tcsh</>, then use this command:
-<programlisting>
-set path = ( /usr/local/pgsql/bin $path )
-</programlisting>
-   </para>
-
-   <para>
-    <indexterm>
-     <primary><envar>MANPATH</envar></primary>
-    </indexterm>
-    To enable your system to find the <application>man</>
-    documentation, you need to add lines like the following to a
-    shell start-up file unless you installed into a location that is
-    searched by default:
-<programlisting>
-MANPATH=/usr/local/pgsql/man:$MANPATH
-export MANPATH
-</programlisting>
-   </para>
-
-   <para>
-    The environment variables <envar>PGHOST</> and <envar>PGPORT</>
-    specify to client applications the host and port of the database
-    server, overriding the compiled-in defaults. If you are going to
-    run client applications remotely then it is convenient if every
-    user that plans to use the database sets <envar>PGHOST</>.  This
-    is not required, however; the settings can be communicated via command
-    line options to most client programs.
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    When, as typical case, you're configuring both Coordinator and
-    Datanode in a same server, please be careful not to assign same
-    resource, such as listening point (IP address and port number) to
-    different component.  If you apply single set of environment
-    described here to different components, they will conflict
-    and <productname>Postgres-XC</> will not run correctly.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    When, as typical case, you're configuring both Coordinator and
-    Datanode in a same server, please be careful not to assign same
-    resource, such as listening point (IP address and port number) to
-    different component.  If you apply single set of environment
-    described here to different components, they will conflict
-    and <productname>Postgres-XL</> will not run correctly.
-   </para>
-<!## end>
-  </sect2>
- </sect1>
-
-
-<![%standalone-include;[
- <sect1 id="install-getting-started">
-  <title>Getting Started</title>
-
-  <para>
-<!## PG>
-   The following is a quick summary of how to get <productname>PostgreSQL</> up and
-<!## end>
-<!## XC>
-   The following is a quick summary of how to get <productname>Postgres-XC</> up and
-<!## end>
-<!## XL>
-   The following is a quick summary of how to get <productname>Postgres-XL</> up and
-<!## end>
-   running once installed. The main documentation contains more information.
-  </para>
-
-  <procedure>
-   <step>
-    <para>
-<!## PG>
-     Create a user account for the <productname>PostgreSQL</>
-     server. This is the user the server will run as. For production
-     use you should create a separate, unprivileged account
-     (<quote>postgres</> is commonly used). If you do not have root
-     access or just want to play around, your own user account is
-     enough, but running the server as root is a security risk and
-     will not work.
-<!## end>
-<!## XC>
-     Create a user account on all the servers where at least one
-     of <productname>Postgres-XC</> component runs. This is the user
-     the components will run as. For production use you should create a
-     separate, unprivileged account (<quote>postgres</> is commonly
-     used). If you do not have root access or just want to play
-     around, your own user account is enough, but running the server
-     as root is a security risk and will not work.
-<!## end>
-<!## XL>
-     Create a user account on all the servers where at least one
-     of <productname>Postgres-XL</> component runs. This is the user
-     the components will run as. For production use you should create a
-     separate, unprivileged account (<quote>postgres</> is commonly
-     used). If you do not have root access or just want to play
-     around, your own user account is enough, but running the server
-     as root is a security risk and will not work.
-<!## end>
-<screen>
-<userinput>adduser postgres</>
-</screen>
-    </para>
-   </step>
-
-<!## XC>
-
-   <step>
-&xconly;
-    <para>
-     If you follow the previous steps, you will have files ready to
-     distribute to servers where you want to run one or
-     more <productname>Postgres-XC</> components.   
-    </para>
-    <para> 
-     After you've installed your build locally, build target
-     will include the following directories.
-
-<screen>
-bin/  include/  lib/  share/
-</screen>
-
-     <filename>bin</> directory contains executable binaries and
-     scripts.  <filename>include</> contains header files needed to
-     build <productname>Postgres-XC</> applications.  <filename>lib</>
-     contains shared libraries needed to run binaries, as well as
-     static libraries which should be included into your application
-     binaries.  Finally, <productname>share</> contains miscellaneous
-     files <productname>Postgres-XC</> should read at runtime, as well
-     as sample files.
-
-    </para>
-
-    <para>
-
-     If your servers has sufficient file space, you can copy all the
-     files to the target server.  Total size is less than 30mega
-     bytes.  If you want to install minimum files to each servers,
-     please follow the following paragraphs.
-
-    </para>
-
-    <para>
-     For the server to run GTM or GTM-Standby, you need to copy the
-     following files to your path: <filename>bin/gtm</> and <filename>bin/gtm_ctl</>.
-    </para>
-
-    <para>
-     For the server to run GTM-Proxy (the server you run Coordinator and/or Datanode),
-     you need to copy the following files to your path: <filename>bin/gtm_proxy</filename>
-     and <filename>bin/gtm_ctl</>.
-    </para>
-
-    <para>
-     For server to run Coordinator or Datanode, or both, you should
-     copy the following files to your
-     path: <filename>bin/initdb</>.
-     You should also copy everything in <filename>path</> directory to
-     your library search path.
-    </para>
-
-   </step>
-
-<!## end>
-<!## XL>
-
-   <step>
-&xlonly;
-    <para>
-     If you follow the previous steps, you will have files ready to
-     distribute to servers where you want to run one or
-     more <productname>Postgres-XL</> components.   
-    </para>
-    <para> 
-     After you've installed your build locally, build target
-     will include the following directories.
-
-<screen>
-bin/  include/  lib/  share/
-</screen>
-
-     <filename>bin</> directory contains executable binaries and
-     scripts.  <filename>include</> contains header files needed to
-     build <productname>Postgres-XL</> applications.  <filename>lib</>
-     contains shared libraries needed to run binaries, as well as
-     static libraries which should be included into your application
-     binaries.  Finally, <productname>share</> contains miscellaneous
-     files <productname>Postgres-XL</> should read at runtime, as well
-     as sample files.
-
-    </para>
-
-    <para>
-
-     If your servers has sufficient file space, you can copy all the
-     files to the target server.  Total size is less than 30mega
-     bytes.  If you want to install minimum files to each servers,
-     please follow the following paragraphs.
-
-    </para>
-
-    <para>
-     For the server to run GTM or GTM-Standby, you need to copy the
-     following files to your path: <filename>bin/gtm</> and <filename>bin/gtm_ctl</>.
-    </para>
-
-    <para>
-     For the server to run GTM-Proxy (the server you run Coordinator and/or Datanode),
-     you need to copy the following files to your path: <filename>bin/gtm_proxy</filename>
-     and <filename>bin/gtm_ctl</>.
-    </para>
-
-    <para>
-     For server to run Coordinator or Datanode, or both, you should
-     copy the following files to your
-     path: <filename>bin/initdb</>.
-     You should also copy everything in <filename>path</> directory to
-     your library search path.
-    </para>
-
-   </step>
-
-<!## end>
-
-
-   <step>
-&common;
-    <para>
-     Create a database installation with the <command>initdb</>
-     command. To run <command>initdb</> you must be logged in to your
-<!## PG>
-     <productname>PostgreSQL</> server account. It will not work as
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</> server account. It will not work as
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</> server account. It will not work as
-<!## end>
-     root.
-<screen>
-root# <userinput>mkdir /usr/local/pgsql/data</>
-root# <userinput>chown postgres /usr/local/pgsql/data</>
-root# <userinput>su - postgres</>
-postgres$ <userinput>/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data</>
-</screen>
-    </para>
-
-    <para>
-     The <option>-D</> option specifies the location where the data
-     will be stored. You can use any path you want, it does not have
-     to be under the installation directory. Just make sure that the
-     server account can write to the directory (or create it, if it
-     doesn't already exist) before starting <command>initdb</>, as
-     illustrated here.
-    </para>
-<!## XC>
-    <para>
-     If you're configuring both Datanode and Coordinator on the same
-     server, you should specify different <option>-D</> option for
-     each of them.
-    </para>
-<!## end>
-<!## XL>
-    <para>
-     If you're configuring both Datanodes and Coordinators on the same
-     server, you should specify different <option>-D</> values for
-     each of them.
-    </para>
-<!## end>
-   </step>
-
-   <step>
-&common;
-    <para>
-     At this point, if you did not use the <command>initdb</> <literal>-A</>
-     option, you might want to modify <filename>pg_hba.conf</> to control
-     local access to the server before you start it.  The default is to
-     trust all local users.
-    </para>
-   </step>
-
-<!## XC>
-   <step>
-&xconly;
-    <para>
-    You should configure GTM and GTM-Proxy, as well as
-    GTM-Standby if you need high-availability capability for GTM
-    before you really run <productname>Postgres-XC</> database
-    cluster.  You can do the following before you
-    run <command>initdb</>.
-    </para>
-    <para>
-     Each GTM, GTM-Proxy and GTM needs their own working directories.
-     Create them as <productname>Postgres-XC</> owner user.  Please
-     assign port number to each of them, although you don't have to do
-     any configuration work now.
-    </para>
-   </step>
-
-   <step>
-&xconly;
-    <para>
-    Now you should configure each Coordinator and Datanode.  Because
-    they have to communicate each other and number of servers,
-    Datanodes and Coordinators depend upon configurations, we don't
-    provide default configuration file for them.
-    </para>
-    <para>
-     You can configure Datanode and Coordinator by
-     editing <filename>postgresql.conf</> file located under the
-     directory you specified with <option>-D</> option
-     of <command>initdb</>.   The following paragraphs describe what
-     parameter to edit at least for Coordinators.   You can specify
-     any other <filename>postgresql.conf</> parameters as
-     standalone <productname>PostgreSQL</>.
-    </para>
-
-    <variablelist>
-    <varlistentry>
-     <term><envar>max_prepared_transactions</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       <option>max_prepared_transactions</> specifies maximum number
-       of two-phase commit transactions.   Even if you don't use
-       explicit two phase commit operation, Coordinator may issue
-       two-phase commit operation implicitly if a transaction is
-       involved with multiple Datanodes and/or Coordinators. You should
-       specify <option>max_prepared_transactions</> value at 
-       least the number of <option>max_connection</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>min_pool_size</envar><term>
-     <listitem>
-&xconly;
-      <par>
-       Coordinator is associated with a connection pooler which takes
-       care of connection with other Coordinators and Datanodes.  This
-       parameter specifies minimum number of connection to pool.
-       If you're not configuring <productname>XC</> cluster in
-       unbalanced way, you should specify the same value to all the
-       Coordinators.
-      </par>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>max_pool_size</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       This parameter specifies maximum number of the pooled
-       connection.  This value should be at least more than the number
-       of all the Coordinators and Datanodes.   If you specify less
-       value, you will see very frequent close and ope connection
-       which leads to serious performance problem.
-       If you're not configuring <productname>XC</> cluster in
-       unbalanced way, you should specify the same value to all the
-       Coordinators.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>max_coordinators</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       This parameter specifies maximum number of the Coordinators that can
-       be added to the cluster. Cluster would have to be restarted to increase
-       the value.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>max_datanodes</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       This parameter specifies maximum number of the Datanodes that can
-       be added to the cluster. Cluster would have to be restarted to increase
-       the value.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>pgxc_node_name</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       Specify the name of this cluster node. This name index refers to the
-       element of <link linkend="catalog-pgxc-node"><structname>pgxc_node
-       </structname></link>.node_name value, to identify the node self.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>port</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       Specify the port number listened to by this Coordinator.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>pooler_port</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       Connection pooler needs separate port.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>gtm_port</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       Specify the port number of gtm you're connecting to.  This is
-       local to the server and you should specify the port assigned to
-       the GTM-Proxy local to the Coordinator.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    </variablelist>                                                             
-
-   <step>
-&xconly;
-    <para>
-     Now you should configure <filename>postgresql.conf</> for each
-     Datanodes.  Please note, as in the case of Coordinator, you can
-     specify other <filename>postgresql.conf</> parameters as in
-     standalone <productname>PostgreSQL</>.
-    </para>
-
-    <variablelist>
-
-    <varlistentry>
-     <term><envar>max_connections</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       <option>max_connections</> is, in short, a maximum number of
-       background processes of the Datanode.   You should be careful
-       to specify reasonable value to this parameter because each
-       Coordinator backend may have connections to all the Datanodes.
-       You should specify this value as <option>max_connections</> of
-       Coordinator multiplied by the number of Coordinators.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>max_prepared_transactions</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       <option>max_prepared_transactions</> specifies maximum number
-       of two-phase commit transactions.   Even if you don't use
-       explicit two phase commit operation, Coordinator may issue
-       two-phase commit operation implicitly if a transaction is
-       involved with multiple Datanodes and/or Coordinators.   The value
-       of this parameter should be at least the value
-       of <option>max_connections</> of Coordinator multiplied by the number of Coordinators.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>port</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       Specify the port number listened to by the Datanode.
-      </para>
-     </listitem>
-    </varlistentry>
-
-     <term><envar>gtm_port</envar></term>
-     <listitem>
-&xconly;
-      <para>
-       Specify the port number of gtm you're connecting to.  This is
-       local to the server and you should specify the port assigned to
-       the GTM-Proxy local to the Datanode.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    </variablelist>
-   </step>
-
-   <step>
-&xconly;
-    <para>
-     Then you are ready to start <productname>Postgres-XC</> cluster.
-     First, you should start GTM bu something like:
-<programlisting>
-gtm -D /usr/local/pgsql/gtm -h localhost -p 20001 -n 1 -x 1000
-</programlisting>
-     This will start GTM.   <option>-h</> specifies IP address or host
-     name to listen to the connection
-     from <command>gtm_standby</>.   <option>-p</> specifies the port
-     number to listen to.   <option>-n</> specifies the node number
-     within GTM.   This identifies GTM especially when you run
-     GTM-Standby.  <option>-x</> option specifies the value of initial
-     Global Transaction ID.   We need to specify this
-     because <command>initdb</> consumes some of the transaction ID
-     locally and GTM must to begin to provide global transaction ID
-     greater than the consumed one.   So far, value 1000 is believed
-     to be safe.
-    </para>
-   </step>
-
-   <step>
-&xconly;
-    <para>
-     Next, you should start GTM-Proxy on each server you're running
-     Coordinator and/or Datanode like:
-<programlisting>
-gtm_proxy -h localhost -p 20002 -s localhost -t 20001 -i 1 -n 2 -D /usr/local/pgsql/gtm_proxy
-</programlisting>
-     This will start GTM-Proxy.  <option>-h</> option is the host name
-     or IP address which GTM-Proxy listens to.   <option>-p</> option
-     is the port number to listen to.   <option>-s</>
-     and <option>-t</> are IP address or the host
-     name and the port number of GTM as specified
-     above.   <option>-i</> is the node number of GTM-Proxy beginning
-     with 1.   <option>-n</> is the number of worker thread of
-     GTM-Proxy.   Usually, 1 or 2 is advised.  Then <option>-D</>
-     option is the working directory of the GTM-Proxy.
-    </para>
-    <para>
-     Please note that you should start GTM-Proxy on all the servers
-     you run Coordinator/Datanode.
-    </para>
-   </step>
-
-   <step>
-&xconly;
-    <para>
-     Now you can start Datanode on each server like:
-<programlisting>
-postgres --datanode -D /usr/local/pgsql/Datanode
-</programlisting>
-     This will start the Datanode.   <option>--datanode</>
-     specifies <command>postgres</> to start as a
-     Datanode. <option>-D</> specifies the data directory of the
-     Datanode. You can specify other options of standalone <command>postgres</>.
-    </para>
-    <para>
-     Please note that you should issue <command>postgres</> command at
-     all the servers you're running Datanode.
-    </para>
-   </step>
-
-   <para>
-    Finally, you can start Coordinator like:
-<programlisting>
-postgres --coordinator -D /usr/local/pgsql/Coordinator
-</programlisting>
-    This will start the Coordinator.  <option>--coordinator</>
-    specifies <command>postgres</> to start as a
-    Coordinator.  <option>-D</> specifies the data directory of the
-    Coordinator.  You can specify other options of standalone <command>postgres</>.
-   </para>
-   <para>
-    Please note that you should issue <command>postgres</> command at
-    all the servers you're running Coordinators.
-   </para>
-<!## end>
-<!## XL>
-   <step>
-&xlonly;
-    <para>
-    You should configure GTM and GTM-Proxy, as well as
-    GTM-Standby if you need high-availability capability for GTM
-    before you really run <productname>Postgres-XL</> database
-    cluster.  You can do the following before you
-    run <command>initdb</>.
-    </para>
-    <para>
-     Each of GTM, GTM-Proxy and GTM need their own working directories.
-     Create them as <productname>Postgres-XL</> owner user.  Please
-     assign a port number to each of them, although you don't have to do
-     any configuration work now.
-    </para>
-   </step>
-
-   <step>
-&xlonly;
-    <para>
-    Now you should configure each Coordinator and Datanode.  Because
-    they have to communicate each other and number of servers,
-    Datanodes and Coordinators depend upon configurations, we do not
-    provide default configuration files for them.
-    </para>
-    <para>
-     You can configure Datanodes and Coordinators by
-     editing the <filename>postgresql.conf</> file located under the
-     directory you specified with <option>-D</> option
-     of <command>initdb</>.   The following paragraphs describe what
-     parameter to edit at for Coordinators.   You can specify
-     any other <filename>postgresql.conf</> parameters as
-     standalone <productname>PostgreSQL</>.
-    </para>
-
-    <variablelist>
-    <varlistentry>
-     <term><envar>max_prepared_transactions</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       <option>max_prepared_transactions</> specifies maximum number
-       of two-phase commit transactions.   Even if you don't use
-       explicit two phase commit operation, the Coordinator may issue
-       two-phase commit operation implicitly if a transaction is
-       involved with multiple Datanodes and/or Coordinators. You should
-       specify <option>max_prepared_transactions</> value at 
-       least the number of <option>max_connection</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>min_pool_size</envar><term>
-     <listitem>
-&xlonly;
-      <par>
-       Coordinator is associated with a connection pooler which takes
-       care of connection with other Coordinators and Datanodes.  This
-       parameter specifies minimum number of connection to pool.
-       If you're not configuring <productname>XL</> cluster in
-       unbalanced way, you should specify the same value to all the
-       Coordinators.
-      </par>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>max_pool_size</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       This parameter specifies maximum number of the pooled
-       connection.  This value should be at least more than the number
-       of all the Coordinators and Datanodes.   If you specify less
-       value, you will see very frequent close and ope connection
-       which leads to serious performance problem.
-       If you're not configuring <productname>XL</> cluster in
-       unbalanced way, you should specify the same value to all the
-       Coordinators.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>pool_conn_keepalive</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       This parameter specifies how long to keep the connection alive.
-       If older than this amount, the pooler discards the connection.
-       This parameter is useful in multi-tenant environments where
-       many connections to many different databases may be used,
-       so that idle connections may cleaned up. It is also useful
-       for automatically closing connections occasionally in case
-       there is some unknown memory leak so that this memory can be freed. 
-      </para> 
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>pool_maintenance_timeout</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       This parameter specifies how long to wait until pooler
-       maintenance is performed. During such maintenance,
-       old idle connections are discarded.
-       This parameter is useful in multi-tenant environments where
-       many connections to many different databases may be used,
-       so that idle connections may cleaned up. 
-      </para> 
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>remote_query_cost</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       This parameter specifies the cost overhead of setting up
-       a remote query to obtain remote data. It is used by
-       the planner in costing queries.
-      </para> 
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>network_byte_cost</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       This parameter is used in query cost planning to 
-       estimate the cost involved in row shipping and obtaining
-       remote data based on the expected data size.
-       Row shipping is expensive and adds latency, so this
-       setting helps to favor plans that minimizes row shipping.
-      </para> 
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>sequence_range</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       This parameter is used to get several sequence values
-       at once from GTM.  This greatly speeds up COPY and INSERT SELECT
-       operations where the target table uses sequences.
-       <productname>Postgres-XL</productname> will not use this entire
-       amount at once, but will increase the request size over
-       time if many requests are done in a short time frame in
-       the same session.
-       After a short time without any sequence requests, decreases back down to 1.
-       Note that any settings here are overriden if the CACHE clause was
-       used in <xref linkend='sql-createsequence'> or <xref linkend='sql-altersequence'>.
-      </para> 
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>max_coordinators</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       This parameter specifies maximum number of the Coordinators that can
-       be added to the cluster. Cluster would have to be restarted to increase
-       the value.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>max_datanodes</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       This parameter specifies maximum number of the Datanodes that can
-       be added to the cluster. Cluster would have to be restarted to increase
-       the value.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>pgxc_node_name</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       Specify the name of this cluster node. This name index refers to the
-       element of <link linkend="catalog-pgxc-node"><structname>pgxc_node
-       </structname></link>.node_name value, to identify the node self.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>port</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       Specify the port number listened to by this Coordinator.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>pooler_port</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       Connection pooler needs separate port.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>gtm_port</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       Specify the port number of gtm you're connecting to.  This is
-       local to the server and you should specify the port assigned to
-       the GTM-Proxy local to the Coordinator.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    </variablelist>                                                             
-
-   <step>
-&xlonly;
-    <para>
-     Now you should configure <filename>postgresql.conf</> for each
-     Datanodes.  Please note, as in the case of Coordinator, you can
-     specify other <filename>postgresql.conf</> parameters as in
-     standalone <productname>PostgreSQL</>.
-    </para>
-
-    <variablelist>
-
-    <varlistentry>
-     <term><envar>max_connections</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       <option>max_connections</> is, in short, a maximum number of
-       background processes of the Datanode.   You should be careful
-       to specify reasonable value to this parameter because each
-       Coordinator backend may have connections to all the Datanodes.
-       You should specify this value as <option>max_connections</> of
-       Coordinator multiplied by the number of Coordinators.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>max_prepared_transactions</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       <option>max_prepared_transactions</> specifies maximum number
-       of two-phase commit transactions.   Even if you don't use
-       explicit two phase commit operation, Coordinator may issue
-       two-phase commit operation implicitly if a transaction is
-       involved with multiple Datanodes and/or Coordinators.   The value
-       of this parameter should be at least the value
-       of <option>max_connections</> of Coordinator multiplied by the number of Coordinators.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>port</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       Specify the port number listened to by the Datanode.
-      </para>
-     </listitem>
-    </varlistentry>
-
-     <term><envar>gtm_port</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       Specify the port number of gtm you're connecting to.  This is
-       local to the server and you should specify the port assigned to
-       the GTM-Proxy local to the Datanode.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    </variablelist>
-
-    <para>
-     Postgres-XL introduces some additional parameters for the 
-     Datanodes as well
-    </para>
-
-    <variablelist>
-
-    <varlistentry>
-     <term><envar>shared_queues</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       For some joins that occur in queries, data from one Datanode may
-       need to be joined with data from another Datanode.
-       <productname>Postgres-XL</productname> uses shared queues for this purpose.
-       During execution each Datanode knows if it needs to produce or consume
-       tuples, or both. 
-      </para>
-      <para>
-       Note that there may be mulitple shared_queues used even for a single
-       query. So a value should be set taking into account the number of 
-       connections it can accept and expected number of such joins occurring
-       simultaneously.
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><envar>shared_queue_size</envar></term>
-     <listitem>
-&xlonly;
-      <para>
-       This parameter sets the size of each each shared queue allocated.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    </variablelist>
-   </step>
-
-   <step>
-&xlonly;
-    <para>
-     Then you are ready to start the <productname>Postgres-XL</> cluster.
-     First, you should start GTM bu something like:
-<programlisting>
-gtm -D /usr/local/pgsql/gtm -h localhost -p 20001 -n 1 -x 1000
-</programlisting>
-     This will start GTM.   <option>-h</> specifies IP address or host
-     name to listen to the connection
-     from <command>gtm_standby</>.   <option>-p</> specifies the port
-     number to listen to.   <option>-n</> specifies the node number
-     within GTM.   This identifies GTM especially when you run
-     GTM-Standby.  <option>-x</> option specifies the value of initial
-     Global Transaction ID.   We need to specify this
-     because <command>initdb</> consumes some of the transaction ID
-     locally and GTM must to begin to provide global transaction ID
-     greater than the consumed one.   A value of at least 2000 is believed
-     to be safe.
-    </para>
-   </step>
-
-   <step>
-&xlonly;
-    <para>
-     Next, you should start GTM-Proxy on each server you're running
-     Coordinator and/or Datanode like:
-<programlisting>
-gtm_proxy -h localhost -p 20002 -s localhost -t 20001 -i 1 -n 2 -D /usr/local/pgsql/gtm_proxy
-</programlisting>
-     This will start GTM-Proxy.  <option>-h</> option is the host name
-     or IP address which GTM-Proxy listens to.   <option>-p</> option
-     is the port number to listen to.   <option>-s</>
-     and <option>-t</> are IP address or the host
-     name and the port number of GTM as specified
-     above.   <option>-i</> is the node number of GTM-Proxy beginning
-     with 1.   <option>-n</> is the number of worker thread of
-     GTM-Proxy.   Usually, 1 or 2 is advised.  Then <option>-D</>
-     option is the working directory of the GTM-Proxy.
-    </para>
-    <para>
-     Please note that you should start GTM-Proxy on all the servers
-     you run Coordinator/Datanode.
-    </para>
-   </step>
-
-   <step>
-&xlonly;
-    <para>
-     Now you can start Datanode on each server like:
-<programlisting>
-postgres --datanode -D /usr/local/pgsql/Datanode
-</programlisting>
-     This will start the Datanode.   <option>--datanode</>
-     specifies <command>postgres</> to start as a
-     Datanode. <option>-D</> specifies the data directory of the
-     Datanode. You can specify other options of standalone <command>postgres</>.
-    </para>
-    <para>
-     Please note that you should issue <command>postgres</> command at
-     all the servers you're running Datanode.
-    </para>
-   </step>
-
-   <para>
-    Finally, you can start Coordinator like:
-<programlisting>
-postgres --coordinator -D /usr/local/pgsql/Coordinator
-</programlisting>
-    This will start the Coordinator.  <option>--coordinator</>
-    specifies <command>postgres</> to start as a
-    Coordinator.  <option>-D</> specifies the data directory of the
-    Coordinator.  You can specify other options of standalone <command>postgres</>.
-   </para>
-   <para>
-    Please note that you should issue <command>postgres</> command at
-    all the servers you're running Coordinators.
-   </para>
-<!## end>
-
-   <step>
-
-<!## PG>
-    <para>
-     The previous <command>initdb</> step should have told you how to
-     start up the database server. Do so now. The command should look
-     something like:
-<programlisting>
-/usr/local/pgsql/bin/postgres -D /usr/local/pgsql/data
-</programlisting>
-     This will start the server in the foreground. To put the server
-     in the background use something like:
-<programlisting>
-nohup /usr/local/pgsql/bin/postgres -D /usr/local/pgsql/data \
-    &lt;/dev/null &gt;&gt;server.log 2&gt;&amp;1 &lt;/dev/null &amp;
-</programlisting>
-    </para>
-
-    <para>
-     To stop a server running in the background you can type:
-<programlisting>
-kill `cat /usr/local/pgsql/data/postmaster.pid`
-</programlisting>
-    </para>
-<!## end>
-<!## XC>
-&xconly;
-    <para>
-     The previous step should have told you how to
-     start up the whole database cluster. Do so now. The command should look
-     something like:
-<programlisting>
-postgres --datanode -D /usr/local/pgsql/Datanode
-</programlisting>
-     This will start the Datanode in the foreground. To put the Datanode
-     in the background use something like:
-<programlisting>
-nohup postgres --datanode -D /usr/local/pgsql/data \
-    &lt;/dev/null &gt;&gt;server.log 2&gt;&amp;1 &lt;/dev/null &amp;
-</programlisting>
-     You can apply this to all the other components, GTM, GTM-Proxies,
-     and Coordinators.
-    </para>
-
-    <para>
-     To stop a Datanode running in the background you can type:
-<programlisting>
-kill `cat /usr/local/pgsql/Datanode/postmaster.pid`
-</programlisting>
-     You can apply this to stop a Coordinator too.
-    </para>
-    <para>
-     To stop the GTM running in the background you can type
-<programlisting>
-kill `cat /usr/local/pgsql/gtm/gtm.pid`
-</programlisting>
-    </para>
-    <para>
-     To stop a GTM-Proxy running in the background, you can type
-<programlisting>
-kill `cat /usr/local/pgsql/gtm-proxy/gtm_proxy.pid
-</programlisting>
-    </para>
-<!## end>
-<!## XL>
-&xlonly;
-    <para>
-     The previous step should have told you how to
-     start up the whole database cluster. Do so now. The command should look
-     something like:
-<programlisting>
-postgres --datanode -D /usr/local/pgsql/Datanode
-</programlisting>
-     This will start the Datanode in the foreground. To put the Datanode
-     in the background use something like:
-<programlisting>
-nohup postgres --datanode -D /usr/local/pgsql/data \
-    &lt;/dev/null &gt;&gt;server.log 2&gt;&amp;1 &lt;/dev/null &amp;
-</programlisting>
-     You can apply this to all the other components, GTM, GTM-Proxies,
-     and Coordinators.
-    </para>
-
-    <para>
-     To stop a Datanode running in the background you can type:
-<programlisting>
-kill `cat /usr/local/pgsql/Datanode/postmaster.pid`
-</programlisting>
-     You can apply this to stop a Coordinator too.
-    </para>
-    <para>
-     To stop the GTM running in the background you can type
-<programlisting>
-kill `cat /usr/local/pgsql/gtm/gtm.pid`
-</programlisting>
-    </para>
-    <para>
-     To stop a GTM-Proxy running in the background, you can type
-<programlisting>
-kill `cat /usr/local/pgsql/gtm-proxy/gtm_proxy.pid
-</programlisting>
-    </para>
-<!## end>
-
-   </step>
-
-   <step>
-    <para>
-     Create a database:
-<screen>
-<userinput>createdb testdb</>
-</screen>
-     Then enter:
-<!## PG>
-<screen>
-<userinput>psql testdb</>
-</screen>
-<!## end>
-<!## XC>
-&xconly;
-<screen>
-<userinput>psql -p 20004 testdb</>
-</screen>
-<!## end>
-<!## XL>
-&xlonly;
-<screen>
-<userinput>psql -p 20004 testdb</>
-</screen>
-<!## end>
-<!## XC>
-     Please do not forget to give the port number of one of the
-     Coordinators.   Then you are connected to a Coordinator listening
-     to the port you specified.
-<!## end>
-<!## XL>
-     Please do not forget to give the port number of one of the
-     Coordinators.   Then you are connected to a Coordinator listening
-     to the port you specified.
-<!## end>
-<!## PG>
-     to connect to that database. At the prompt you can enter SQL
-     commands and start experimenting.
-<!## end>
-    </para>
-   </step>
-  </procedure>
- </sect1>
-
- <sect1 id="install-whatnow">
-  <title>What Now?</title>
-
-  <para>
-   <itemizedlist>
-    <listitem>
-     <para>
-<!## PG>
-      The <productname>PostgreSQL</> distribution contains a
-<!## end>
-<!## XC>
-      The <productname>Postgres-XC</> distribution contains a
-<!## end>
-<!## XL>
-      The <productname>Postgres-XL</> distribution contains a
-<!## end>
-      comprehensive documentation set, which you should read sometime.
-      After installation, the documentation can be accessed by
-      pointing your browser to
-      <filename>/usr/local/pgsql/doc/html/index.html</>, unless you
-      changed the installation directories.
-     </para>
-
-     <para>
-      The first few chapters of the main documentation are the Tutorial,
-      which should be your first reading if you are completely new to
-      <acronym>SQL</> databases.  If you are familiar with database
-      concepts then you want to proceed with part on server
-      administration, which contains information about how to set up
-      the database server, database users, and authentication.
-     </para>
-    </listitem>
-
-<!## PG>
-    <listitem>
-     <para>
-      Usually, you will want to modify your computer so that it will
-      automatically start the database server whenever it boots. Some
-      suggestions for this are in the documentation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Run the regression tests against the installed server (using
-      <command>gmake installcheck</command>). If you didn't run the
-      tests before installation, you should definitely do it now. This
-      is also explained in the documentation.
-     </para>
-    </listitem>
-<!## end>
-
-    <listitem>
-     <para>
-<!## PG>
-      By default, <productname>PostgreSQL</> is configured to run on
-<!## end>
-<!## XC>
-      By default, <productname>Postgres-XC</> is configured to run on
-<!## end>
-<!## XL>
-      By default, <productname>Postgres-XL</> is configured to run on
-<!## end>
-      minimal hardware.  This allows it to start up with almost any
-      hardware configuration. The default configuration is, however,
-      not designed for optimum performance. To achieve optimum
-      performance, several server parameters must be adjusted, the two
-      most common being <varname>shared_buffers</varname> and
-      <varname>work_mem</varname>.
-      Other parameters mentioned in the documentation also affect
-      performance.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
- </sect1>
-]]>
-
-
- <sect1 id="supported-platforms">
-  <title>Supported Platforms</title>
-
-<!## PG>
-  <para>
-   A platform (that is, a CPU architecture and operating system combination)
-   is considered supported by the <productname>PostgreSQL</> development
-   community if the code contains provisions to work on that platform and
-   it has recently been verified to build and pass its regression tests
-   on that platform.  Currently, most testing of platform compatibility
-   is done automatically by test machines in the
-   <ulink url="http://buildfarm.postgresql.org/">PostgreSQL Build Farm</ulink>.
-   If you are interested in using <productname>PostgreSQL</> on a platform
-   that is not represented in the build farm, but on which the code works
-   or can be made to work, you are strongly encouraged to set up a build
-   farm member machine so that continued compatibility can be assured.
-  </para>
-<!## end>
-
-<!## PG>
-  <para>
-   In general, <productname>PostgreSQL</> can be expected to work on
-   these CPU architectures: x86, x86_64, IA64, PowerPC,
-   PowerPC 64, S/390, S/390x, Sparc, Sparc 64, Alpha, ARM, MIPS, MIPSEL, M68K,
-   and PA-RISC.  Code support exists for M32R, NS32K, and VAX, but these
-   architectures are not known to have been tested recently.  It is often
-   possible to build on an unsupported CPU type by configuring with
-   <option>--disable-spinlocks</option>, but performance will be poor.
-  </para>
-<!## end>
-
-<!## XC>
-&xconly;
-  <para>
-   <productname>Postgres-XC</> has been tested on Intel-based CPU mainly. Other CPU
-    architectures may also work but are not currently being tested.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <productname>Postgres-XL</> has been tested on Intel-based CPU mainly. Other CPU
-    architectures may also work but are not currently being tested.
-  </para>
-<!## end>
-
-<!## PG>
-  <para>
-   <productname>PostgreSQL</> can be expected to work on these operating
-   systems: Linux (all recent distributions), Windows (Win2000 SP4 and later),
-   FreeBSD, OpenBSD, NetBSD, Mac OS X, AIX, HP/UX, IRIX, Solaris, Tru64 Unix,
-   and UnixWare.  Other Unix-like systems may also work but are not currently
-   being tested.  In most cases, all CPU architectures supported by
-   a given operating system will work.  Look in
-   the <xref linkend="installation-platform-notes"> below to see if
-   there is information
-   specific to your operating system, particularly if using an older system.
-  </para>
-<!## end>
-<!## XC>
-&xconly;
-  <para>
-   <productname>Postgres-XC</> can be expected to work on these operating systems:
-   Linux (all recent distributions), FreeBSD and Mac OS X. Other Unix-like systems may
-   also work but are not currently being tested.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   <productname>Postgres-XL</> can be expected to work on these operating systems:
-   Linux (all recent distributions), FreeBSD and Mac OS X. Other Unix-like systems may
-   also work but are not currently being tested.
-  </para>
-<!## end>
-
-  <para>
-<!## PG>
-   If you have installation problems on a platform that is known
-   to be supported according to recent build farm results, please report
-   it to <email>[email protected]</email>.  If you are interested
-   in porting <productname>PostgreSQL</> to a new platform,
-   <email>[email protected]</email> is the appropriate place
-   to discuss that.
-<!## end>
-<!## XC>
-   If you have installation problems on a platform that is known
-   to be supported according to recent build farm results, please report
-   it to <email>[email protected]</email>.  If you are interested
-   in porting <productname>Postgres-XC</> to a new platform,
-   <email>[email protected]</email> is the appropriate place
-   to discuss that.
-<!## end>
-<!## XL>
-   If you have installation problems on a platform that is known
-   to be supported according to recent build farm results, please report
-   it to <email>[email protected]</email>.  If you are interested
-   in porting <productname>Postgres-XL</> to a new platform,
-   <email>[email protected]</email> is the appropriate place
-   to discuss that.
-<!## end>
-
-  </para>
- </sect1>
-
- <sect1 id="installation-platform-notes">
-  <title>Platform-specific Notes</title>
-
-  <para>
-<!## PG>
-   This section documents additional platform-specific issues
-   regarding the installation and setup of PostgreSQL.  Be sure to
-   read the installation instructions, and in
-   particular <xref linkend="install-requirements"> as well.  Also,
-   check <![%standalone-include[the
-   file <filename>src/test/regress/README</> and the documentation]]>
-   <![%standalone-ignore[<xref linkend="regress">]]> regarding the
-   interpretation of regression test results.
-<!## end>
-<!## XC>
-   This section documents additional platform-specific issues
-   regarding the installation and setup of Postgres-XC.  Be sure to
-   read the installation instructions.
-<!## end>
-<!## XL>
-   This section documents additional platform-specific issues
-   regarding the installation and setup of Postgres-XL.  Be sure to
-   read the installation instructions.
-<!## end>
-  </para>
-
-  <para>
-   Platforms that are not covered here have no known platform-specific
-   installation issues.
-  </para>
-
-<!## PG>
-  <sect2 id="installation-notes-aix">
-   <title>AIX</title>
-
-   <indexterm zone="installation-notes-aix">
-    <primary>AIX</primary>
-    <secondary>installation on</secondary>
-   </indexterm>
-
-   <para>
-    PostgreSQL works on AIX, but getting it installed properly can be
-    challenging.  AIX versions from 4.3.3 to 6.1 are considered supported.
-    You can use GCC or the native IBM compiler <command>xlc</command>.  In
-    general, using recent versions of AIX and PostgreSQL helps.  Check
-    the build farm for up to date information about which versions of
-    AIX are known to work.
-   </para>
-
-   <para>
-    The minimum recommended fix levels for supported AIX versions are:
-   </para>
-
-   <variablelist>
-    <varlistentry>
-     <term>AIX 4.3.3</term>
-     <listitem><para>Maintenance Level 11 + post ML11 bundle</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>AIX 5.1</term>
-     <listitem><para>Maintenance Level 9 + post ML9 bundle</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>AIX 5.2</term>
-     <listitem><para>Technology Level 10 Service Pack 3</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>AIX 5.3</term>
-     <listitem><para>Technology Level 7</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>AIX 6.1</term>
-     <listitem><para>Base Level</para></listitem>
-    </varlistentry>
-   </variablelist>
-
-   <para>
-    To check your current fix level, use
-    <command>oslevel -r</command> in AIX 4.3.3 to AIX 5.2 ML 7, or
-    <command>oslevel -s</command> in later versions.
-   </para>
-
-   <para>
-    Use the following <command>configure</command> flags in addition
-    to your own if you have installed Readline or libz in
-    <literal>/usr/local</>:
-    <literal>--with-includes=/usr/local/include
-    --with-libraries=/usr/local/lib</literal>.
-   </para>
-
-   <sect3>
-    <title>GCC Issues</title>
-
-    <para>
-     On AIX 5.3, there have been some problems getting PostgreSQL to
-     compile and run using GCC.
-    </para>
-
-    <para>
-     You will want to use a version of GCC subsequent to 3.3.2,
-     particularly if you use a prepackaged version.  We had good
-     success with 4.0.1.  Problems with earlier versions seem to have
-     more to do with the way IBM packaged GCC than with actual issues
-     with GCC, so that if you compile GCC yourself, you might well
-     have success with an earlier version of GCC.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Unix-Domain Sockets Broken</title>
-
-    <para>
-     AIX 5.3 has a problem
-     where <structname>sockaddr_storage</structname> is not defined to
-     be large enough.  In version 5.3, IBM increased the size of
-     <structname>sockaddr_un</structname>, the address structure for
-     Unix-domain sockets, but did not correspondingly increase the
-     size of <structname>sockaddr_storage</structname>.  The result of
-     this is that attempts to use Unix-domain sockets with PostgreSQL
-     lead to libpq overflowing the data structure.  TCP/IP connections
-     work OK, but not Unix-domain sockets, which prevents the
-     regression tests from working.
-    </para>
-
-    <para>
-     The problem was reported to IBM, and is recorded as bug report
-     PMR29657.  If you upgrade to maintenance level 5300-03 or later,
-     that will include this fix.  A quick workaround
-     is to alter <symbol>_SS_MAXSIZE</symbol> to 1025 in
-     <filename>/usr/include/sys/socket.h</filename>.  In either case,
-     recompile PostgreSQL once you have the corrected header file.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Internet Address Issues</title>
-
-    <para>
-     PostgreSQL relies on the system's <function>getaddrinfo</> function
-     to parse IP addresses in <varname>listen_addresses</>,
-     <filename>pg_hba.conf</>, etc.  Older versions of AIX have assorted
-     bugs in this function.  If you have problems related to these settings,
-     updating to the appropriate AIX fix level shown above
-     should take care of it.
-    </para>
-
-    <!-- http://archives.postgresql.org/message-id/[email protected] -->
-
-    <para>
-     One user reports:
-    </para>
-
-    <para>
-     When implementing PostgreSQL version 8.1 on AIX 5.3, we
-     periodically ran into problems where the statistics collector
-     would <quote>mysteriously</quote> not come up successfully.  This
-     appears to be the result of unexpected behavior in the IPv6
-     implementation.  It looks like PostgreSQL and IPv6 do not play
-     very well together on AIX 5.3.
-    </para>
-
-    <para>
-     Any of the following actions <quote>fix</quote> the problem.
-     <itemizedlist>
-      <listitem>
-       <para>
-        Delete the IPv6 address for localhost:
-<screen>
-(as root)
-# ifconfig lo0 inet6 ::1/0 delete
-</screen>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Remove IPv6 from net services.  The
-        file <filename>/etc/netsvc.conf</filename> on AIX is roughly
-        equivalent to <filename>/etc/nsswitch.conf</filename> on
-        Solaris/Linux.  The default, on AIX, is thus:
-<programlisting>
-hosts=local,bind
-</programlisting>
-        Replace this with:
-<programlisting>
-hosts=local4,bind4
-</programlisting>
-        to deactivate searching for IPv6 addresses.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <warning>
-    <para>
-     This is really a workaround for problems relating
-     to immaturity of IPv6 support, which improved visibly during the
-     course of AIX 5.3 releases.  It has worked with AIX version 5.3,
-     but does not represent an elegant solution to the problem.  It has
-     been reported that this workaround is not only unnecessary, but
-     causes problems on AIX 6.1, where IPv6 support has become more mature.
-    </para>
-    </warning>
-
-   </sect3>
-
-   <sect3>
-    <title>Memory Management</title>
-    <!-- http://archives.postgresql.org/message-id/[email protected] -->
-
-    <para>
-     AIX can be somewhat peculiar with regards to the way it does
-     memory management.  You can have a server with many multiples of
-     gigabytes of RAM free, but still get out of memory or address
-     space errors when running applications.  One example
-     is <command>createlang</command> failing with unusual errors.
-     For example, running as the owner of the PostgreSQL installation:
-<screen>
--bash-3.00$ createlang plperl template1
-createlang: language installation failed: ERROR:  could not load library "/opt/dbs/pgsql748/lib/plperl.so": A memory address is not in the address space for the process.
-</screen>
-    Running as a non-owner in the group possessing the PostgreSQL
-    installation:
-<screen>
--bash-3.00$ createlang plperl template1
-createlang: language installation failed: ERROR:  could not load library "/opt/dbs/pgsql748/lib/plperl.so": Bad address
-</screen>
-     Another example is out of memory errors in the PostgreSQL server
-     logs, with every memory allocation near or greater than 256 MB
-     failing.
-    </para>
-
-    <para>
-     The overall cause of all these problems is the default bittedness
-     and memory model used by the server process.  By default, all
-     binaries built on AIX are 32-bit.  This does not depend upon
-     hardware type or kernel in use.  These 32-bit processes are
-     limited to 4 GB of memory laid out in 256 MB segments using one
-     of a few models.  The default allows for less than 256 MB in the
-     heap as it shares a single segment with the stack.
-    </para>
-
-    <para>
-     In the case of the <command>createlang</command> example, above,
-     check your umask and the permissions of the binaries in your
-     PostgreSQL installation.  The binaries involved in that example
-     were 32-bit and installed as mode 750 instead of 755.  Due to the
-     permissions being set in this fashion, only the owner or a member
-     of the possessing group can load the library.  Since it isn't
-     world-readable, the loader places the object into the process'
-     heap instead of the shared library segments where it would
-     otherwise be placed.
-    </para>
-
-    <para>
-     The <quote>ideal</quote> solution for this is to use a 64-bit
-     build of PostgreSQL, but that is not always practical, because
-     systems with 32-bit processors can build, but not run, 64-bit
-     binaries.
-    </para>
-
-    <para>
-     If a 32-bit binary is desired, set <symbol>LDR_CNTRL</symbol> to
-     <literal>MAXDATA=0x<replaceable>n</replaceable>0000000</literal>,
-     where 1 &lt;= n &lt;= 8, before starting the PostgreSQL server,
-     and try different values and <filename>postgresql.conf</filename>
-     settings to find a configuration that works satisfactorily.  This
-     use of <symbol>LDR_CNTRL</symbol> tells AIX that you want the
-     server to have <symbol>MAXDATA</symbol> bytes set aside for the
-     heap, allocated in 256 MB segments.  When you find a workable
-     configuration,
-     <command>ldedit</command> can be used to modify the binaries so
-     that they default to using the desired heap size.  PostgreSQL can
-     also be rebuilt, passing <literal>configure
-     LDFLAGS="-Wl,-bmaxdata:0x<replaceable>n</replaceable>0000000"</literal>
-     to achieve the same effect.
-    </para>
-
-    <para>
-     For a 64-bit build, set <envar>OBJECT_MODE</envar> to 64 and
-     pass <literal>CC="gcc -maix64"</literal>
-     and <literal>LDFLAGS="-Wl,-bbigtoc"</literal>
-     to <command>configure</command>.  (Options for
-    <command>xlc</command> might differ.)  If you omit the export of
-    <envar>OBJECT_MODE</envar>, your build may fail with linker errors.  When
-    <envar>OBJECT_MODE</envar> is set, it tells AIX's build utilities
-    such as <command>ar</>, <command>as</>, and <command>ld</> what
-    type of objects to default to handling.
-    </para>
-
-    <para>
-     By default, overcommit of paging space can happen.  While we have
-     not seen this occur, AIX will kill processes when it runs out of
-     memory and the overcommit is accessed.  The closest to this that
-     we have seen is fork failing because the system decided that
-     there was not enough memory for another process.  Like many other
-     parts of AIX, the paging space allocation method and
-     out-of-memory kill is configurable on a system- or process-wide
-     basis if this becomes a problem.
-    </para>
-
-    <bibliography>
-     <title>References and Resources</title>
-
-     <biblioentry>
-      <biblioset relation="article">
-       <title><ulink url="http://publib.boulder.ibm.com/infocenter/pseries/topic/com.ibm.aix.doc/aixprggd/genprogc/lrg_prg_support.htm">Large Program Support</ulink></title>
-      </biblioset>
-      <biblioset relation="book">
-       <title>AIX Documentation: General Programming Concepts: Writing and Debugging Programs</title>
-      </biblioset>
-     </biblioentry>
-
-     <biblioentry>
-      <biblioset relation="article">
-       <title><ulink url="http://publib.boulder.ibm.com/infocenter/pseries/topic/com.ibm.aix.doc/aixprggd/genprogc/address_space.htm">Program Address Space Overview</ulink></title>
-      </biblioset>
-      <biblioset relation="book">
-       <title>AIX Documentation: General Programming Concepts: Writing and Debugging Programs</title>
-      </biblioset>
-     </biblioentry>
-
-     <biblioentry>
-      <biblioset relation="article">
-       <title><ulink url="http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.doc/aixbman/prftungd/resmgmt2.htm">Performance Overview of the Virtual Memory Manager (VMM)</ulink></title>
-      </biblioset>
-      <biblioset relation="book">
-       <title>AIX Documentation: Performance Management Guide</title>
-      </biblioset>
-     </biblioentry>
-
-     <biblioentry>
-      <biblioset relation="article">
-       <title><ulink url="http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.doc/aixbman/prftungd/memperf7.htm">Page Space Allocation</ulink></title>
-      </biblioset>
-      <biblioset relation="book">
-       <title>AIX Documentation: Performance Management Guide</title>
-      </biblioset>
-     </biblioentry>
-
-     <biblioentry>
-      <biblioset relation="article">
-       <title><ulink url="http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.doc/aixbman/prftungd/memperf6.htm">Paging-space thresholds tuning</ulink></title>
-      </biblioset>
-      <biblioset relation="book">
-       <title>AIX Documentation: Performance Management Guide</title>
-      </biblioset>
-     </biblioentry>
-
-     <biblioentry>
-       <title><ulink url="  http://www.redbooks.ibm.com/abstracts/sg245674.html?Open">Developing and Porting C and C++ Applications on AIX</ulink></title>
-       <publisher>
-        <publishername>IBM Redbook</publishername>
-       </publisher>
-     </biblioentry>
-    </bibliography>
-   </sect3>
-  </sect2>
-<!## end>
-
-<!## PG>
-  <sect2 id="installation-notes-cygwin">
-   <title>Cygwin</title>
-
-   <indexterm zone="installation-notes-cygwin">
-    <primary>Cygwin</primary>
-    <secondary>installation on</secondary>
-   </indexterm>
-
-   <para>
-    PostgreSQL can be built using Cygwin, a Linux-like environment for
-    Windows, but that method is inferior to the native Windows build
-    <![%standalone-ignore[(see <xref linkend="install-windows">)]]> and
-    running a server under Cygwin is no longer recommended.
-   </para>
-
-   <para>
-    When building from source, proceed according to the normal
-    installation procedure (i.e., <literal>./configure;
-    make</literal>; etc.), noting the following-Cygwin specific
-    differences:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Set your path to use the Cygwin bin directory before the
-       Windows utilities.  This will help prevent problems with
-       compilation.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The GNU make command is called <command>make</command>, not <command>gmake</command>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The <command>adduser</command> command is not supported; use
-       the appropriate user management application on Windows NT,
-       2000, or XP.  Otherwise, skip this step.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The <command>su</command> command is not supported; use ssh to
-       simulate su on Windows NT, 2000, or XP. Otherwise, skip this
-       step.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       OpenSSL is not supported.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Start <command>cygserver</command> for shared memory support.
-       To do this, enter the command <literal>/usr/sbin/cygserver
-       &amp;</literal>.  This program needs to be running anytime you
-       start the PostgreSQL server or initialize a database cluster
-       (<command>initdb</command>).  The
-       default <command>cygserver</command> configuration may need to
-       be changed (e.g., increase <symbol>SEMMNS</symbol>) to prevent
-       PostgreSQL from failing due to a lack of system resources.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Building might fail on some systems where a locale other than
-        C is in use. To fix this, set the locale to C by doing
-        <command>export LANG=C.utf8</command> before building, and then
-        setting it back to the previous setting, after you have installed
-        PostgreSQL.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The parallel regression tests (<literal>make check</literal>)
-       can generate spurious regression test failures due to
-       overflowing the <function>listen()</function> backlog queue
-       which causes connection refused errors or hangs.  You can limit
-       the number of connections using the make
-       variable <varname>MAX_CONNECTIONS</varname> thus:
-<programlisting>
-make MAX_CONNECTIONS=5 check
-</programlisting>
-       (On some systems you can have up to about 10 simultaneous
-       connections).
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    It is possible to install <command>cygserver</command> and the
-    PostgreSQL server as Windows NT services.  For information on how
-    to do this, please refer to the <filename>README</filename>
-    document included with the PostgreSQL binary package on Cygwin.
-    It is installed in the
-    directory <filename>/usr/share/doc/Cygwin</filename>.
-   </para>
-  </sect2>
-<!## end>
-
-<!## PG>
-  <sect2 id="installation-notes-hpux">
-   <title>HP-UX</title>
-
-   <indexterm zone="installation-notes-hpux">
-    <primary>HP-UX</primary>
-    <secondary>installation on</secondary>
-   </indexterm>
-
-   <para>
-    PostgreSQL 7.3+ should work on Series 700/800 PA-RISC machines
-    running HP-UX 10.X or 11.X, given appropriate system patch levels
-    and build tools.  At least one developer routinely tests on HP-UX
-    10.20, and we have reports of successful installations on HP-UX
-    11.00 and 11.11.
-   </para>
-
-   <para>
-    Aside from the PostgreSQL source distribution, you will need GNU
-    make (HP's make will not do), and either GCC or HP's full ANSI C
-    compiler.  If you intend to build from Git sources rather than a
-    distribution tarball, you will also need Flex (GNU lex) and Bison
-    (GNU yacc).  We also recommend making sure you are fairly
-    up-to-date on HP patches.  At a minimum, if you are building 64
-    bit binaries on on HP-UX 11.11 you may need PHSS_30966 (11.11) or a
-    successor patch otherwise <command>initdb</command> may hang:
-<literallayout>
-PHSS_30966  s700_800 ld(1) and linker tools cumulative patch
-</literallayout>
-
-    On general principles you should be current on libc and ld/dld
-    patches, as well as compiler patches if you are using HP's C
-    compiler.  See HP's support sites such
-    as <ulink url="http://itrc.hp.com"></ulink> and
-    <ulink url="ftp://us-ffs.external.hp.com/"></ulink> for free
-    copies of their latest patches.
-   </para>
-
-   <para>
-    If you are building on a PA-RISC 2.0 machine and want to have
-    64-bit binaries using GCC, you must use GCC 64-bit version. GCC
-    binaries for HP-UX PA-RISC and Itanium are available from
-    <ulink url="http://www.hp.com/go/gcc"></ulink>.  Don't forget to
-    get and install binutils at the same time.
-   </para>
-
-   <para>
-    If you are building on a PA-RISC 2.0 machine and want the compiled
-    binaries to run on PA-RISC 1.1 machines you will need to specify
-    <option>+DAportable</option> in <envar>CFLAGS</envar>.
-   </para>
-
-   <para>
-    If you are building on a HP-UX Itanium machine, you will need the
-    latest HP ANSI C compiler with its dependent patch or successor
-    patches:
-<literallayout>
-PHSS_30848  s700_800 HP C Compiler (A.05.57)
-PHSS_30849  s700_800 u2comp/be/plugin library Patch
-</literallayout>
-   </para>
-
-   <para>
-    If you have both HP's C compiler and GCC's, then you might want to
-    explicitly select the compiler to use when you
-    run <command>configure</command>:
-<programlisting>
-./configure CC=cc
-</programlisting>
-    for HP's C compiler, or
-<programlisting>
-./configure CC=gcc
-</programlisting>
-    for GCC.  If you omit this setting, then configure will
-    pick <command>gcc</command> if it has a choice.
-   </para>
-
-   <para>
-    The default install target location
-    is <filename>/usr/local/pgsql</filename>, which you might want to
-    change to something under <filename>/opt</filename>.  If so, use
-    the
-    <option>--prefix</option> switch to <command>configure</command>.
-   </para>
-
-   <para>
-    In the regression tests, there might be some low-order-digit
-    differences in the geometry tests, which vary depending on which
-    compiler and math library versions you use.  Any other error is
-    cause for suspicion.
-   </para>
-  </sect2>
-<!## end>
-
-<!## PG>
-  <sect2 id="installation-notes-irix">
-   <title>IRIX</title>
-
-   <indexterm zone="installation-notes-irix">
-    <primary>IRIX</primary>
-    <secondary>installation on</secondary>
-   </indexterm>
-
-   <para>
-    PostgreSQL has been reported to run successfully on MIPS r8000,
-    r10000 (both ip25 and ip27) and r12000(ip35) processors, running
-    IRIX 6.5.5m, 6.5.12, 6.5.13, and 6.5.26 with MIPSPro compilers
-    version 7.30, 7.3.1.2m, 7.3, and 7.4.4m.
-   </para>
-
-   <para>
-    You will need the MIPSPro full ANSI C compiler.  There are
-    problems trying to build with GCC.  It is a known GCC bug (not
-    fixed as of version 3.0) related to using functions that return
-    certain kinds of structures. This bug affects functions like
-    <function>inet_ntoa</>, <function>inet_lnaof</>, <function>inet_netof</>, <function>inet_makeaddr</>,
-    and <function>semctl</>.  It is supposed to be fixed by forcing
-    code to link those functions with libgcc, but this has not been
-    tested yet.
-   </para>
-
-   <para>
-    It is known that version 7.4.1m of the MIPSPro compiler generates
-    incorrect code.  The symptom is <quote>invalid primary checkpoint
-    record</quote> when trying to start the database.)  Version 7.4.4m
-    is OK; the status of intermediate versions is uncertain.
-   </para>
-
-   <para>
-    There may be a compilation problem like the following:
-<screen>
-cc-1020 cc: ERROR File = pqcomm.c, Line = 427
-  The identifier "TCP_NODELAY" is undefined.
-
-                if (setsockopt(port->sock, IPPROTO_TCP, TCP_NODELAY,
-</screen>
-    Some versions include TCP definitions
-    in <filename>sys/xti.h</filename>, so it is necessary to
-    add <literal>#include &lt;sys/xti.h&gt;</literal>
-    in <filename>src/backend/libpq/pqcomm.c</> and in
-    <filename>src/interfaces/libpq/fe-connect.c</>.  If you encounter
-    this, please let us know so we can develop a proper fix.
-   </para>
-
-   <para>
-    In the regression tests, there might be some low-order-digit
-    differences in the geometry tests, depending on which FPU are you
-    using.  Any other error is cause for suspicion.
-   </para>
-  </sect2>
-<!## end>
-
-<!## PG>
-  <sect2 id="installation-notes-mingw">
-   <title>MinGW/Native Windows</title>
-
-   <indexterm zone="installation-notes-mingw">
-    <primary>MinGW</primary>
-    <secondary>installation on</secondary>
-   </indexterm>
-
-   <para>
-    PostgreSQL for Windows can be built using MinGW, a Unix-like build
-    environment for Microsoft operating systems, or using
-    Microsoft's <productname>Visual C++</productname> compiler suite.
-    The MinGW build variant uses the normal build system described in
-    this chapter; the Visual C++ build works completely differently
-    and is described in <![%standalone-include[the
-    documentation]]><![%standalone-ignore[<xref linkend="install-windows">]]>.
-    It is a fully native build and uses no additional software like
-    MinGW.  A ready-made installer is available on the main
-    PostgreSQL web site.
-   </para>
-
-   <para>
-    The native Windows port requires a 32 or 64-bit version of Windows
-    2000 or later. Earlier operating systems do
-    not have sufficient infrastructure (but Cygwin may be used on
-    those).  MinGW, the Unix-like build tools, and MSYS, a collection
-    of Unix tools required to run shell scripts
-    like <command>configure</command>, can be downloaded
-    from <ulink url="http://www.mingw.org/"></ulink>.  Neither is
-    required to run the resulting binaries; they are needed only for
-    creating the binaries.
-   </para>
-
-   <para>
-     To build 64 bit binaries using MinGW, install the 64 bit tool set
-     from <ulink url="http://mingw-w64.sourceforge.net/"></ulink>, put its bin
-     directory in the <envar>PATH</envar>, and run
-     <command>configure</command> with the
-     <command>--host=x86_64-w64-mingw</command> option.
-   </para>
-
-   <para>
-    After you have everything installed, it is suggested that you
-    run <application>psql</application>
-    under <command>CMD.EXE</command>, as the MSYS console has
-    buffering issues.
-   </para>
-
-   <sect3 id="windows-crash-dumps">
-    <title>Collecting Crash Dumps on Windows</title>
-
-    <para>
-     If PostgreSQL on Windows crashes, it has the ability to generate
-     <productname>minidumps</> that can be used to track down the cause
-     for the crash, similar to core dumps on Unix. These dumps can be
-     read using the <productname>Windows Debugger Tools</> or using
-     <productname>Visual Studio</>. To enable the generation of dumps
-     on Windows, create a subdirectory named <filename>crashdumps</filename>
-     inside the cluster data directory. The dumps will then be written
-     into this directory with a unique name based on the identifier of
-     the crashing process and the current time of the crash.
-    </para>
-   </sect3>
-  </sect2>
-<!## end>
-
-<!## PG>
-  <sect2 id="installation-notes-sco">
-   <title>SCO OpenServer and SCO UnixWare</title>
-
-   <indexterm zone="installation-notes-sco">
-    <primary>SCO</primary>
-    <secondary>installation on</secondary>
-   </indexterm>
-
-   <indexterm zone="installation-notes-sco">
-    <primary>UnixWare</primary>
-    <secondary>installation on</secondary>
-   </indexterm>
-
-   <para>
-    PostgreSQL can be built on SCO UnixWare 7 and SCO OpenServer 5.
-    On OpenServer, you can use either the OpenServer Development Kit
-    or the Universal Development Kit.  However, some tweaking may be
-    needed, as described below.
-   </para>
-
-   <sect3>
-    <title>Skunkware</title>
-
-    <para>
-     You should locate your copy of the SCO Skunkware CD.  The
-     Skunkware CD is included with UnixWare 7 and current versions of
-     OpenServer 5.  Skunkware includes ready-to-install versions of
-     many popular programs that are available on the Internet.  For
-     example, gzip, gunzip, GNU Make, Flex, and Bison are all
-     included.  For UnixWare 7.1, this CD is now labeled "Open License
-     Software Supplement".  If you do not have this CD, the software
-     on it is available
-     from <ulink url="http://www.sco.com/skunkware/"></ulink>.
-    </para>
-
-    <para>
-     Skunkware has different versions for UnixWare and OpenServer.
-     Make sure you install the correct version for your operating
-     system, except as noted below.
-    </para>
-
-    <para>
-     On UnixWare 7.1.3 and beyond, the GCC compiler is included on the
-     UDK CD as is GNU Make.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>GNU Make</title>
-
-    <para>
-     You need to use the GNU Make program, which is on the Skunkware
-     CD.  By default, it installs
-     as <filename>/usr/local/bin/make</filename>.  To avoid confusion
-     with the SCO <filename>make</filename> program, you may want to rename GNU <filename>make</filename> to
-     <filename>gmake</filename>.
-    </para>
-
-    <para>
-     As of UnixWare 7.1.3 and above, the GNU Make program is is the
-     OSTK portion of the UDK CD, and is
-     in <filename>/usr/gnu/bin/gmake</filename>.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Readline</title>
-
-    <para>
-     The Readline library is on the Skunkware CD.  But it is not
-     included on the UnixWare 7.1 Skunkware CD.  If you have the
-     UnixWare 7.0.0 or 7.0.1 Skunkware CDs, you can install it from
-     there.  Otherwise,
-     try <ulink url="http://www.sco.com/skunkware/"></ulink>.
-    </para>
-
-    <para>
-     By default, Readline installs into <filename>/usr/local/lib</> and
-     <filename>/usr/local/include</>.  However, the
-     PostgreSQL <command>configure</command> program will not find it
-     there without help.  If you installed Readline, then use the
-     following options to <command>configure</command>:
-<programlisting>
-./configure --with-libraries=/usr/local/lib --with-includes=/usr/local/include
-</programlisting>
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Using the UDK on OpenServer</title>
-
-    <para>
-     If you are using the new Universal Development Kit (UDK) compiler
-     on OpenServer, you need to specify the locations of the UDK
-     libraries:
-<programlisting>
-./configure --with-libraries=/udk/usr/lib --with-includes=/udk/usr/include
-</programlisting>
-     Putting these together with the Readline options from above:
-<programlisting>
-./configure --with-libraries="/udk/usr/lib /usr/local/lib" --with-includes="/udk/usr/include /usr/local/include"
-</programlisting>
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Reading the PostgreSQL Man Pages</title>
-
-    <para>
-     By default, the PostgreSQL man pages are installed into
-     <filename>/usr/local/pgsql/man</filename>.  By default, UnixWare
-     does not look there for man pages.  To be able to read them you
-     need to modify the
-     <varname>MANPATH</varname> variable
-     in <filename>/etc/default/man</filename>, for example:
-<programlisting>
-MANPATH=/usr/lib/scohelp/%L/man:/usr/dt/man:/usr/man:/usr/share/man:scohelp:/usr/local/man:/usr/local/pgsql/man
-</programlisting>
-    </para>
-
-    <para>
-     On OpenServer, some extra research needs to be invested to make
-     the man pages usable, because the man system is a bit different
-     from other platforms.  Currently, PostgreSQL will not install
-     them at all.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>C99 Issues with the 7.1.1b Feature Supplement</title>
-
-    <para>
-     For compilers earlier than the one released with OpenUNIX 8.0.0
-     (UnixWare 7.1.2), including the 7.1.1b Feature Supplement, you
-     may need to specify <option>-Xb</option>
-     in <varname>CFLAGS</varname> or the <varname>CC</varname>
-     environment variable.  The indication of this is an error in
-     compiling <filename>tuplesort.c</filename> referencing inline
-     functions.  Apparently there was a change in the 7.1.2(8.0.0)
-     compiler and beyond.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Threading on UnixWare</title>
-
-    <para>
-     For threading, you<emphasis>must</emphasis> use <option>-Kpthread</option>
-     on <emphasis>all</emphasis> libpq-using programs.  libpq
-     uses <function>pthread_*</function> calls, which are only
-     available with the
-     <option>-Kpthread</>/<option>-Kthread</> flag.
-    </para>
-   </sect3>
-  </sect2>
-<!## end>
-
-<!## PG>
-  <sect2 id="installation-notes-solaris">
-   <title>Solaris</title>
-
-   <indexterm zone="installation-notes-solaris">
-    <primary>Solaris</primary>
-    <secondary>installation on</secondary>
-   </indexterm>
-
-   <para>
-    PostgreSQL is well-supported on Solaris.  The more up to date your
-    operating system, the fewer issues you will experience; details
-    below.
-   </para>
-
-   <para>
-    Note that PostgreSQL is bundled with Solaris 10 (from update 2).
-    Official packages are also available on
-    <ulink url="http://pgfoundry.org/projects/solarispackages/"></ulink>.
-    Packages for older Solaris versions (8, 9) you can be obtained
-    from <ulink url="http://www.sunfreeware.com/"></ulink> or
-    <ulink url="http://www.blastwave.org/"></ulink>.
-   </para>
-
-   <sect3>
-    <title>Required Tools</title>
-
-    <para>
-     You can build with either GCC or Sun's compiler suite.  For
-     better code optimization, Sun's compiler is strongly recommended
-     on the SPARC architecture.  We have heard reports of problems
-     when using GCC 2.95.1; GCC 2.95.3 or later is recommended.  If
-     you are using Sun's compiler, be careful not to select
-     <filename>/usr/ucb/cc</filename>;
-     use <filename>/opt/SUNWspro/bin/cc</filename>.
-    </para>
-
-    <para>
-     You can download Sun Studio
-     from <ulink url="http://developers.sun.com/sunstudio/downloads/"></ulink>.
-     Many of GNU tools are integrated into Solaris 10, or they are
-     present on the Solaris companion CD.  If you like packages for
-     older version of Solaris, you can find these tools
-     at <ulink url="http://www.sunfreeware.com"></ulink>
-     or <ulink url="http://www.blastwave.org"></ulink>.  If you prefer
-     sources, look
-     at <ulink url="http://www.gnu.org/order/ftp.html"></ulink>.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Problems with OpenSSL</title>
-
-    <para>
-     When you build PostgreSQL with OpenSSL support you might get
-     compilation errors in the following files:
-     <itemizedlist>
-      <listitem><para><filename>src/backend/libpq/crypt.c</filename></para></listitem>
-      <listitem><para><filename>src/backend/libpq/password.c</filename></para></listitem>
-      <listitem><para><filename>src/interfaces/libpq/fe-auth.c</filename></para></listitem>
-      <listitem><para><filename>src/interfaces/libpq/fe-connect.c</filename></para></listitem>
-     </itemizedlist>
-
-     This is because of a namespace conflict between the standard
-     <filename>/usr/include/crypt.h</filename> header and the header
-     files provided by OpenSSL.
-    </para>
-
-    <para>
-     Upgrading your OpenSSL installation to version 0.9.6a fixes this
-     problem.  Solaris 9 and above has a newer version of OpenSSL.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>configure Complains About a Failed Test Program</title>
-
-    <para>
-     If <command>configure</command> complains about a failed test
-     program, this is probably a case of the run-time linker being
-     unable to find some library, probably libz, libreadline or some
-     other non-standard library such as libssl.  To point it to the
-     right location, set the <envar>LDFLAGS</envar> environment
-     variable on the <command>configure</command> command line, e.g.,
-<programlisting>
-configure ... LDFLAGS="-R /usr/sfw/lib:/opt/sfw/lib:/usr/local/lib"
-</programlisting>
-     See
-     the <citerefentry><refentrytitle>ld</><manvolnum>1</></citerefentry>
-     man page for more information.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>64-bit Build Sometimes Crashes</title>
-
-    <para>
-     On Solaris 7 and older, the 64-bit version of libc has a buggy
-     <function>vsnprintf</function> routine, which leads to erratic
-     core dumps in PostgreSQL.  The simplest known workaround is to
-     force PostgreSQL to use its own version of <function>vsnprintf</function> rather than
-     the library copy.  To do this, after you
-     run <command>configure</command> edit a file produced by
-     <command>configure</command>:
-     In <filename>src/Makefile.global</filename>, change the line
-<programlisting>
-LIBOBJS =
-</programlisting>
-     to read
-<programlisting>
-LIBOBJS = snprintf.o
-</programlisting>
-     (There might be other files already listed in this variable.
-     Order does not matter.)  Then build as usual.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Compiling for Optimal Performance</title>
-
-    <para>
-     On the SPARC architecture, Sun Studio is strongly recommended for
-     compilation.  Try using the <option>-xO5</option> optimization
-     flag to generate significantly faster binaries.  Do not use any
-     flags that modify behavior of floating-point operations
-     and <varname>errno</varname> processing (e.g.,
-     <option>-fast</option>).  These flags could raise some
-     nonstandard PostgreSQL behavior for example in the date/time
-     computing.
-    </para>
-
-    <para>
-     If you do not have a reason to use 64-bit binaries on SPARC,
-     prefer the 32-bit version.  The 64-bit operations are slower and
-     64-bit binaries are slower than the 32-bit variants.  And on
-     other hand, 32-bit code on the AMD64 CPU family is not native,
-     and that is why 32-bit code is significant slower on this CPU
-     family.
-    </para>
-
-    <para>
-     Some tricks for tuning PostgreSQL and Solaris for performance can
-     be found
-     at <ulink url="http://www.sun.com/servers/coolthreads/tnb/applications_postgresql.jsp"></ulink>.
-     This article is primary focused on T2000 platform, but many of
-     the recommendations are also useful on other hardware with
-     Solaris.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Using DTrace for Tracing PostgreSQL</title>
-
-    <para>
-     Yes, using DTrace is possible.  See <![%standalone-include[the
-     documentation]]>
-     <![%standalone-ignore[<xref linkend="dynamic-trace">]]> for further
-     information.  You can also find more information in this
-     article: <ulink url="http://blogs.sun.com/robertlor/entry/user_level_dtrace_probes_in"></ulink>.
-    </para>
-
-    <para>
-     If you see the linking of the <command>postgres</command> executable abort with an
-     error message like:
-<screen>
-Undefined                       first referenced
- symbol                             in file
-AbortTransaction                    utils/probes.o
-CommitTransaction                   utils/probes.o
-ld: fatal: Symbol referencing errors. No output written to postgres
-collect2: ld returned 1 exit status
-gmake: *** [postgres] Error 1
-</screen>
-     your DTrace installation is too old to handle probes in static
-     functions.  You need Solaris 10u4 or newer.
-    </para>
-   </sect3>
-  </sect2>
-<!## end>
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/intagg.sgmlin b/doc-xc/src/sgml/intagg.sgmlin
deleted file mode 100644
index 2632d6f2d5..0000000000
--- a/doc-xc/src/sgml/intagg.sgmlin
+++ /dev/null
@@ -1,127 +0,0 @@
-<!-- doc/src/sgml/intagg.sgml -->
-
-<sect1 id="intagg" xreflabel="intagg">
- <title>intagg</title>
-
- <indexterm zone="intagg">
-  <primary>intagg</primary>
- </indexterm>
-
-&pgonly;
-
- <para>
-  The <filename>intagg</filename> module provides an integer aggregator and an
-  enumerator.  <filename>intagg</filename> is now obsolete, because there
-  are built-in functions that provide a superset of its capabilities.
-  However, the module is still provided as a compatibility wrapper around
-  the built-in functions.
- </para>
-
- <sect2>
-  <title>Functions</title>
-
-&pgonly;
-
-
- <para>
-  The aggregator is an aggregate function
-  <function>int_array_aggregate(integer)</>
-  that produces an integer array
-  containing exactly the integers it is fed.
-  This is a wrapper around <function>array_agg</>,
-  which does the same thing for any array type.
- </para>
-
- <para>
-  The enumerator is a function
-  <function>int_array_enum(integer[])</>
-  that returns <type>setof integer</>.  It is essentially the reverse
-  operation of the aggregator: given an array of integers, expand it
-  into a set of rows.  This is a wrapper around <function>unnest</>,
-  which does the same thing for any array type.
- </para>
-
- </sect2>
-
- <sect2>
-  <title>Sample Uses</title>
-
-&pgonly;
-
-
-  <para>
-   Many database systems have the notion of a one to many table. Such a table
-   usually sits between two indexed tables, for example:
-
-<programlisting>
-CREATE TABLE left (id INT PRIMARY KEY, ...);
-CREATE TABLE right (id INT PRIMARY KEY, ...);
-CREATE TABLE one_to_many(left INT REFERENCES left, right INT REFERENCES right);
-</programlisting>
-
-  It is typically used like this:
-
-<programlisting>
-SELECT right.* from right JOIN one_to_many ON (right.id = one_to_many.right)
-  WHERE one_to_many.left = <replaceable>item</>;
-</programlisting>
-
-  This will return all the items in the right hand table for an entry
-  in the left hand table. This is a very common construct in SQL.
- </para>
-
- <para>
-  Now, this methodology can be cumbersome with a very large number of
-  entries in the <structname>one_to_many</> table.  Often,
-  a join like this would result in an index scan
-  and a fetch for each right hand entry in the table for a particular
-  left hand entry. If you have a very dynamic system, there is not much you
-  can do. However, if you have some data which is fairly static, you can
-  create a summary table with the aggregator.
-
-<programlisting>
-CREATE TABLE summary AS
-  SELECT left, int_array_aggregate(right) AS right
-  FROM one_to_many
-  GROUP BY left;
-</programlisting>
-
-  This will create a table with one row per left item, and an array
-  of right items. Now this is pretty useless without some way of using
-  the array; that's why there is an array enumerator.  You can do
-
-<programlisting>
-SELECT left, int_array_enum(right) FROM summary WHERE left = <replaceable>item</>;
-</programlisting>
-
-  The above query using <function>int_array_enum</> produces the same results
-  as
-
-<programlisting>
-SELECT left, right FROM one_to_many WHERE left = <replaceable>item</>;
-</programlisting>
-
-  The difference is that the query against the summary table has to get
-  only one row from the table, whereas the direct query against
-  <structname>one_to_many</> must index scan and fetch a row for each entry.
- </para>
-
- <para>
-  On one system, an <command>EXPLAIN</> showed a query with a cost of 8488 was
-  reduced to a cost of 329.  The original query was a join involving the
-  <structname>one_to_many</> table, which was replaced by:
-
-<programlisting>
-SELECT right, count(right) FROM
-  ( SELECT left, int_array_enum(right) AS right
-    FROM summary JOIN (SELECT left FROM left_table WHERE left = <replaceable>item</>) AS lefts
-         ON (summary.left = lefts.left)
-  ) AS list
-  GROUP BY right
-  ORDER BY count DESC;
-</programlisting>
- </para>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/intarray.sgmlin b/doc-xc/src/sgml/intarray.sgmlin
deleted file mode 100644
index 5eb0ea3af4..0000000000
--- a/doc-xc/src/sgml/intarray.sgmlin
+++ /dev/null
@@ -1,348 +0,0 @@
-<!-- doc/src/sgml/intarray.sgml -->
-
-<sect1 id="intarray" xreflabel="intarray">
- <title>intarray</title>
-
- <indexterm zone="intarray">
-  <primary>intarray</primary>
- </indexterm>
-
-&common;
-
-
- <para>
-  The <filename>intarray</> module provides a number of useful functions
-  and operators for manipulating null-free arrays of integers.
-  There is also support for indexed searches using some of the operators.
- </para>
-
- <para>
-  All of these operations will throw an error if a supplied array contains any
-  NULL elements.
- </para>
-
- <para>
-  Many of these operations are only sensible for one-dimensional arrays.
-  Although they will accept input arrays of more dimensions, the data is
-  treated as though it were a linear array in storage order.
- </para>
-
- <sect2>
-  <title><filename>intarray</> Functions and Operators</title>
-
-&common;
-  <para>
-   The functions provided by the <filename>intarray</filename> module
-   are shown in <xref linkend="intarray-func-table">, the operators
-   in <xref linkend="intarray-op-table">.
-  </para>
-
-  <table id="intarray-func-table">
-   <title><filename>intarray</> Functions</title>
-
-   <tgroup cols="5">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Return Type</entry>
-      <entry>Description</entry>
-      <entry>Example</entry>
-      <entry>Result</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><function>icount(int[])</function></entry>
-      <entry><type>int</type></entry>
-      <entry>number of elements in array</entry>
-      <entry><literal>icount('{1,2,3}'::int[])</literal></entry>
-      <entry><literal>3</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>sort(int[], text dir)</function></entry>
-      <entry><type>int[]</type></entry>
-
-      <entry>sort array &mdash; <parameter>dir</> must be <literal>asc</> or <literal>desc</></entry>
-      <entry><literal>sort('{1,2,3}'::int[], 'desc')</literal></entry>
-      <entry><literal>{3,2,1}</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>sort(int[])</function></entry>
-      <entry><type>int[]</type></entry>
-      <entry>sort in ascending order</entry>
-      <entry><literal>sort(array[11,77,44])</literal></entry>
-      <entry><literal>{11,44,77}</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>sort_asc(int[])</function></entry>
-      <entry><type>int[]</type></entry>
-      <entry>sort in ascending order</entry>
-      <entry><literal></literal></entry>
-      <entry><literal></literal></entry>
-     </row>
-
-     <row>
-      <entry><function>sort_desc(int[])</function></entry>
-      <entry><type>int[]</type></entry>
-      <entry>sort in descending order</entry>
-      <entry><literal></literal></entry>
-      <entry><literal></literal></entry>
-     </row>
-
-     <row>
-      <entry><function>uniq(int[])</function></entry>
-      <entry><type>int[]</type></entry>
-      <entry>remove adjacent duplicates</entry>
-      <entry><literal>uniq(sort('{1,2,3,2,1}'::int[]))</literal></entry>
-      <entry><literal>{1,2,3}</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>idx(int[], int item)</function></entry>
-      <entry><type>int</type></entry>
-      <entry>index of first element matching <parameter>item</> (0 if none)</entry>
-      <entry><literal>idx(array[11,22,33,22,11], 22)</literal></entry>
-      <entry><literal>2</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>subarray(int[], int start, int len)</function></entry>
-      <entry><type>int[]</type></entry>
-      <entry>portion of array starting at position <parameter>start</>, <parameter>len</> elements</entry>
-      <entry><literal>subarray('{1,2,3,2,1}'::int[], 2, 3)</literal></entry>
-      <entry><literal>{2,3,2}</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>subarray(int[], int start)</function></entry>
-      <entry><type>int[]</type></entry>
-      <entry>portion of array starting at position <parameter>start</></entry>
-      <entry><literal>subarray('{1,2,3,2,1}'::int[], 2)</literal></entry>
-      <entry><literal>{2,3,2,1}</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>intset(int)</function></entry>
-      <entry><type>int[]</type></entry>
-      <entry>make single-element array</entry>
-      <entry><literal>intset(42)</literal></entry>
-      <entry><literal>{42}</literal></entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <table id="intarray-op-table">
-   <title><filename>intarray</> Operators</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Operator</entry>
-      <entry>Returns</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>int[] &amp;&amp; int[]</literal></entry>
-      <entry><type>boolean</type></entry>
-      <entry>overlap &mdash; <literal>true</> if arrays have at least one common element</entry>
-     </row>
-     <row>
-      <entry><literal>int[] @&gt; int[]</literal></entry>
-      <entry><type>boolean</type></entry>
-      <entry>contains &mdash; <literal>true</> if left array contains right array</entry>
-     </row>
-     <row>
-      <entry><literal>int[] &lt;@ int[]</literal></entry>
-      <entry><type>boolean</type></entry>
-      <entry>contained &mdash; <literal>true</> if left array is contained in right array</entry>
-     </row>
-     <row>
-      <entry><literal># int[]</literal></entry>
-      <entry><type>int</type></entry>
-      <entry>number of elements in array</entry>
-     </row>
-     <row>
-      <entry><literal>int[] # int</literal></entry>
-      <entry><type>int</type></entry>
-      <entry>index (same as <function>idx</> function)</entry>
-     </row>
-     <row>
-      <entry><literal>int[] + int</literal></entry>
-      <entry><type>int[]</type></entry>
-      <entry>push element onto array (add it to end of array)</entry>
-     </row>
-     <row>
-      <entry><literal>int[] + int[]  </literal></entry>
-      <entry><type>int[]</type></entry>
-      <entry>array concatenation (right array added to the end of left one)</entry>
-     </row>
-     <row>
-      <entry><literal>int[] - int</literal></entry>
-      <entry><type>int[]</type></entry>
-      <entry>remove entries matching right argument from array</entry>
-     </row>
-     <row>
-      <entry><literal>int[] - int[]</literal></entry>
-      <entry><type>int[]</type></entry>
-      <entry>remove elements of right array from left</entry>
-     </row>
-     <row>
-      <entry><literal>int[] | int</literal></entry>
-      <entry><type>int[]</type></entry>
-      <entry>union of arguments</entry>
-     </row>
-     <row>
-      <entry><literal>int[] | int[]</literal></entry>
-      <entry><type>int[]</type></entry>
-      <entry>union of arrays</entry>
-     </row>
-     <row>
-      <entry><literal>int[] &amp; int[]</literal></entry>
-      <entry><type>int[]</type></entry>
-      <entry>intersection of arrays</entry>
-     </row>
-     <row>
-      <entry><literal>int[] @@ query_int</literal></entry>
-      <entry><type>boolean</type></entry>
-      <entry><literal>true</> if array satisfies query (see below)</entry>
-     </row>
-     <row>
-      <entry><literal>query_int ~~ int[]</literal></entry>
-      <entry><type>boolean</type></entry>
-      <entry><literal>true</> if array satisfies query (commutator of <literal>@@</>)</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   (Before PostgreSQL 8.2, the containment operators <literal>@&gt;</> and
-   <literal>&lt;@</> were respectively called <literal>@</> and <literal>~</>.
-   These names are still available, but are deprecated and will eventually be
-   retired.  Notice that the old names are reversed from the convention
-   formerly followed by the core geometric data types!)
-  </para>
-
-  <para>
-   The operators <literal>&amp;&amp;</>, <literal>@&gt;</> and
-   <literal>&lt;@</> are equivalent to <productname>PostgreSQL</>'s built-in
-   operators of the same names, except that they work only on integer arrays
-   that do not contain nulls, while the built-in operators work for any array
-   type.  This restriction makes them faster than the built-in operators
-   in many cases.
-  </para>
-
-  <para>
-   The <literal>@@</> and <literal>~~</> operators test whether an array
-   satisfies a <firstterm>query</>, which is expressed as a value of a
-   specialized data type <type>query_int</>.  A <firstterm>query</>
-   consists of integer values that are checked against the elements of
-   the array, possibly combined using the operators <literal>&amp;</>
-   (AND), <literal>|</> (OR), and <literal>!</> (NOT).  Parentheses
-   can be used as needed.  For example,
-   the query <literal>1&amp;(2|3)</> matches arrays that contain 1
-   and also contain either 2 or 3.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Index Support</title>
-
-&common;
-  <para>
-   <filename>intarray</> provides index support for the
-   <literal>&amp;&amp;</>, <literal>@&gt;</>, <literal>&lt;@</>,
-   and <literal>@@</> operators, as well as regular array equality.
-  </para>
-
-  <para>
-   Two GiST index operator classes are provided:
-   <literal>gist__int_ops</> (used by default) is suitable for
-   small- to medium-size data sets, while
-   <literal>gist__intbig_ops</> uses a larger signature and is more
-   suitable for indexing large data sets (i.e., columns containing
-   a large number of distinct array values).
-   The implementation uses an RD-tree data structure with
-   built-in lossy compression.
-  </para>
-
-  <para>
-   There is also a non-default GIN operator class
-   <literal>gin__int_ops</> supporting the same operators.
-  </para>
-
-  <para>
-   The choice between GiST and GIN indexing depends on the relative
-   performance characteristics of GiST and GIN, which are discussed elsewhere.
-   As a rule of thumb, a GIN index is faster to search than a GiST index, but
-   slower to build or update; so GIN is better suited for static data and GiST
-   for often-updated data.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Example</title>
-
-<programlisting>
--- a message can be in one or more <quote>sections</>
-CREATE TABLE message (mid INT PRIMARY KEY, sections INT[], ...);
-
--- create specialized index
-CREATE INDEX message_rdtree_idx ON message USING GIST (sections gist__int_ops);
-
--- select messages in section 1 OR 2 - OVERLAP operator
-SELECT message.mid FROM message WHERE message.sections &amp;&amp; '{1,2}';
-
--- select messages in sections 1 AND 2 - CONTAINS operator
-SELECT message.mid FROM message WHERE message.sections @&gt; '{1,2}';
-
--- the same, using QUERY operator
-SELECT message.mid FROM message WHERE message.sections @@ '1&amp;2'::query_int;
-</programlisting>
- </sect2>
-
- <sect2>
-  <title>Benchmark</title>
-
-&common;
-  <para>
-   The source directory <filename>contrib/intarray/bench</> contains a
-   benchmark test suite.  To run:
-  </para>
-
-<programlisting>
-cd .../bench
-createdb TEST
-psql TEST &lt; ../_int.sql
-./create_test.pl | psql TEST
-./bench.pl
-</programlisting>
-
-  <para>
-   The <filename>bench.pl</> script has numerous options, which
-   are displayed when it is run without any arguments.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Authors</title>
-
-  <para>
-   All work was done by Teodor Sigaev (<email>[email protected]</email>) and
-   Oleg Bartunov (<email>[email protected]</email>). See
-   <ulink url="http://www.sai.msu.su/~megera/postgres/gist/"></ulink> for
-   additional information. Andrey Oktyabrski did a great work on adding new
-   functions and operations.
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/intro.sgmlin b/doc-xc/src/sgml/intro.sgmlin
deleted file mode 100644
index e265f78d99..0000000000
--- a/doc-xc/src/sgml/intro.sgmlin
+++ /dev/null
@@ -1,821 +0,0 @@
-<!-- doc/src/sgml/intro.sgml -->
-
-<preface id="preface">
- <title>Preface</title>
-
- <para>
-<!## PG>
-  This book is the official documentation of
-  <productname>PostgreSQL</productname>.  It has been written by the
-  <productname>PostgreSQL</productname> developers and other
-  volunteers in parallel to the development of the
-  <productname>PostgreSQL</productname> software.  It describes all
-  the functionality that the current version of
-  <productname>PostgreSQL</productname> officially supports.
-<!## end>
-<!## XC>
-  This book is the official documentation of
-  <productname>Postgres-XC</productname>.  It has been written by the
-  <productname>Postgres-XC</productname> developers and other
-  volunteers in parallel to the development of the
-  <productname>Postgres-XC</productname> software.  It describes all
-  the functionality that the current version of
-  <productname>Postgres-XC</productname> officially supports.
-  </para>
-  <para>
-   <productname>Postgres-XC</> is essentially a collection of multiple
-   <productname>PostgreSQL</> database to provide both read and write
-   performance scalability. It also provides full-featured transaction
-   consistency as <productname>PostgreSQL</> provides, at the exception
-   of SSI which is incomplete.
-  </para>
-  <para>
-   <productname>Postgres-XC</> inherits almost all major features from <productname>PostgreSQL</>.
-   This document is also based upon <productname>PostgreSQL</> reference manual.
-<!## end>
-<!## XL>
-  This book is the official documentation of
-  <productname>Postgres-XL</productname>.  It has been written by the
-  <productname>Postgres-XL</productname> developers and other
-  volunteers in parallel to the development of the
-  <productname>Postgres-XL</productname> software.  It describes all
-  the functionality that the current version of
-  <productname>Postgres-XL</productname> officially supports.
-  </para>
-  <para>
-   <productname>Postgres-XL</> is essentially a collection of multiple
-   <productname>PostgreSQL</> database to provide both read and write
-   performance scalability. It also provides full-featured transaction
-   consistency as <productname>PostgreSQL</> provides, at the exception
-   of SSI which is incomplete.
-  </para>
-  <para>
-   <productname>Postgres-XL</> inherits almost all major features from <productname>PostgreSQL</>.
-   This document is also based upon <productname>PostgreSQL</> reference manual.
-<!## end>
- </para>
-
- <para>
-<!## PG>
-  To make the large amount of information about
-  <productname>PostgreSQL</productname> manageable, this book has been
-  organized in several parts.  Each part is targeted at a different
-  class of users, or at users in different stages of their
-  <productname>PostgreSQL</productname> experience:
-<!## end>
-<!## XC>
-  To make the large amount of information about
-  <productname>Postgres-XC</productname> manageable, this book has been
-  organized in several parts.  Each part is targeted at a different
-  class of users, or at users in different stages of their
-  <productname>Postgres-XC</productname> experience:
-<!## end>
-<!## XL>
-  To make the large amount of information about
-  <productname>Postgres-XL</productname> manageable, this book has been
-  organized in several parts.  Each part is targeted at a different
-  class of users, or at users in different stages of their
-  <productname>Postgres-XL</productname> experience:
-<!## end>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     <xref linkend="tutorial"> is an informal introduction for new users.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <xref linkend="sql"> documents the <acronym>SQL</acronym> query
-     language environment, including data types and functions, as well
-     as user-level performance tuning.  Every
-     <productname>PostgreSQL</> user should read this.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-<!## PG>
-     <xref linkend="admin"> describes the installation and
-     administration of the server.  Everyone who runs a
-     <productname>PostgreSQL</productname> server, be it for private
-     use or for others, should read this part.
-<!## end>
-<!## XC>
-     <xref linkend="admin"> describes the installation and
-     administration of the server.  Everyone who runs
-     <productname>Postgres-XC</productname> servers, be it for private
-     use or for others, should read this part.
-<!## end>
-<!## XL>
-     <xref linkend="admin"> describes the installation and
-     administration of the server.  Everyone who runs
-     <productname>Postgres-XL</productname> servers, be it for private
-     use or for others, should read this part.
-<!## end>
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-<!## PG>
-     <xref linkend="client-interfaces"> describes the programming
-     interfaces for <productname>PostgreSQL</productname> client
-     programs.
-<!## end>
-<!## XC>
-     <xref linkend="client-interfaces"> describes the programming
-     interfaces for <productname>Postgres-XC</productname> client
-     programs.
-<!## end>
-<!## XL>
-     <xref linkend="client-interfaces"> describes the programming
-     interfaces for <productname>Postgres-XL</productname> client
-     programs.
-<!## end>
-    </para>
-   </listitem>
-
-
-   <listitem>
-    <para>
-     <xref linkend="server-programming"> contains information for
-     advanced users about the extensibility capabilities of the
-     server.  Topics include user-defined data types and
-     functions.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <xref linkend="reference"> contains reference information about
-     SQL commands, client and server programs.  This part supports the
-     other parts with structured information sorted by command or
-     program.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-<!## PG>
-     <xref linkend="internals"> contains assorted information that might be of
-     use to <productname>PostgreSQL</> developers.
-<!## end>
-<!## XC>
-     <xref linkend="internals"> contains assorted information that might be of
-     use to <productname>Postgres-XC</> developers.
-<!## end>
-<!## XL>
-     <xref linkend="internals"> contains assorted information that might be of
-     use to <productname>Postgres-XL</> developers.
-<!## end>
-    </para>
-   </listitem>
-  </itemizedlist>
- </para>
-
- <sect1 id="intro-whatis">
-<!## PG>
-  <title> What is <productname>PostgreSQL</productname>?</title>
-<!## end>
-<!## XC>
-  <title> What is <productname>Postgres-XC</productname>?</title>
-
-  <sect2 id="whatis-in-short">
-   <title>In short</title>
-
-   <para>
-    Postgres-XC is an open source project to provide write-scalable,
-    synchronous symmetric, transparent PostgreSQL cluster
-    solution. It is a collection if tightly coupled database
-    components which can be installed in more than one hardware or
-    virtual machines.
-   </para>
-
-   <para>
-    Write-scalable means Postgres-XC can be configured with as many
-    database servers as you want and handle much more writes (updating
-    SQL statements) which single database server cannot
-    do. Symmetric means you can have more than one data base
-    servers which provide single database view. Synchronous means any
-    database update from any database server is immediately visible to
-    any other transactions running in different masters.  Transparent
-    means you don't have to worry about how your data is stored in
-    more than one database servers internally.
-    <footnote>
-     <para>
-      Of course, you should use the information how tables are stored
-      internally when you design the database physically to get most
-      from Postgres-XC.
-     </para>
-    </footnote>
-   </para>
-
-   <para>
-    You can configure Postgres-XC to run on more than one machines. They
-    store your data in a distributed way, that is, partitioned or
-    replicated way at your choice for each table.  
-    <footnote>
-     <para>
-      To distinguish from PostgreSQL's partitioning, we call this as
-      "distributed".  In distributed database textbooks, this is often
-      referred to as "horizontal fragment").
-     </para>
-    </footnote>
-    When you issue queries, Postgres-XC determines where the target
-    data is stored and issue corresponding queries to servers with the
-    target data.
-   </para>
-
-   <para>
-    In typical web systems, you can have as many web servers or
-    application servers to handle your transactions. However, you
-    cannot do this for a database server in general because all the
-    changing data have to be visible to all the transactions. Unlike
-    other database cluster solution, Postgres-XC provides this
-    capability. You can install as many database servers as you
-    like. Each database server provides uniform data view to your
-    applications.  Any database update from any server is immediately
-    visible to applications connecting the database from other
-    servers. This feature is called "synchronous multi master"
-    capability and this is the most significant feature of
-    Postgres-XC.
-   </para>
-  </sect2>
-
-  <sect2 id="whatis-xc-goal">
-   <title>Postgres-XC's Goal</title>
-
-   <para>
-    Ultimate goal of Postgres-XC is to provide synchronous
-    multi-master PostgreSQL cluster with read/write scalability. That
-    is, Postgres-XC should provide the following features:
-    <itemizedlist spacing="compact">
-     <listitem>
-      <para>
-       Postgres-XC should provide multiple servers to accept transactions and statements
-from applications, which is known as "master" server in general. In Postgres-XC, this is called "Coordinator".
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Postgres-XC should provide more than one masters.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Any "master" should provide consistent database view to
-       applications. Any updates from any master must be visible in
-       real time manner as if such updates are done in single
-       PostgreSQL server.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Tables should be able to be stored in the database in
-       replicated or distributed way (known as fragment or
-       partition). Replication and distribution should be transparent
-       to applications, that is, such replicated and distributed table
-       are seen as single table and location or number of copies of
-       each record/tuple is managed by Postgres-XC and is not visible
-       to applications.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Postgres-XC provides compatible PostgreSQL API to applications.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Postgres-XC should provide single and unified view of
-       underlying PostgreSQL database servers so that SQL statements
-       does not depend on how tables are stored in distributed way.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-  </sect2>
-
-  <sect2 id="whatis-xc-key-components">
-   <title>Postgres-XC Key Components</title>
-
-   <para>
-    In this section, we will show main components of Postgres-XC.
-   </para>
-
-   <para>
-    Postgres-XC is composed of three major components, called GTM
-    (Global Transaction Manager), Coordinator and Datanode. Their
-    features are given in the following sections.
-   </para>
-
-   <sect3>
-    <title>GTM (Global Transaction Manager)</title>
-
-    <para>
-     GTM is a key component of Postgres-XC to provide consistent
-     transaction management and tuple visibility control.
-    </para>
-
-    <para>
-     As described later in this
-     manual, <productname>PostgreSQL</productname>'s transaction
-     management is based upon MVCC (Multi-Version Concurrency Control)
-     technology.  <productname>Postgres-XC</productname> extracts this
-     technology into separate component as GTM so that
-     any <productname>Postgres-XC</productname> component's
-     transaction management is based upon single global status.
-     Details will be described in <xref linkend="overview">.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Coordinator</title>
-
-    <para>
-     Coordinator is an interface to applications. It acts like
-     conventional PostgreSQL backend process. However, Coordinator
-     does not store any actual data. Actual data is stored by Datanode
-     as described below. Coordinator receives SQL statements, get Global
-     Transaction Id and Global Snapshot as needed, determine which
-     Datanode is involved and ask them to execute (a part of)
-     statement.  When issuing statement to Datanodes, it is
-     associated with GXID and Global Snapshot so that Datanode is not
-     confused if it receives another statement from another
-     transaction originated by another Coordinator.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Datanode</title>
-
-    <para>
-     Datanode actually stores your data. Tables may be distributed
-     among Datanodes, or replicated to all the Datanodes.
-     Datanode does not have global view of the whole database, it
-     just takes care of locally stored data. Incoming statement is
-     examined by the Coordinator as described next, and rebuilt to
-     execute at each Datanode involved. It is then transferred to
-     each Datanodes involved together with GXID and Global Snapshot
-     as needed. Datanode may receive request from various
-     Coordinators. However, because each the transaction is identified
-     uniquely and associated with consistent (global) snapshot, data
-     node doesn't have to worry what Coordinator each transaction or
-     statement came from.
-    </para>
-
-   </sect3>
-
-  </sect2>
-
-  <sect2 id="whatis-xc-inherits-postgresql">
-   <title><productname>Postgres-XC</productname> Inherits <productname>PostgreSQL</productname></title>
-
-   <para>
-    <productname>Postgres-XC</productname> is an extension
-    to <productname>PostgreSQL</productname> and inherits most of its
-    features.
-   </para>
-
-   <para>
-    It is an open-source descendant of
-    <productname>PostgreSQL</productname> and its
-    original Berkeley code.  It supports a large part of the SQL
-    standard and offers many modern features:
-
-    <itemizedlist spacing="compact">
-     <listitem>
-      <simpara>complex queries</simpara>
-     </listitem>
-     <listitem>
-      <simpara>
-       foreign keys
-       <footnote>
-        <para>
-         <productname>Postgres-XC</productname>'s foreign key usage has some restrictions.  For details, see <xref linkend="SQL-CREATETABLE">.
-        </para>
-       </footnote>
-      </simpara>
-     </listitem>
-     <listitem>
-      <simpara>
-       triggers
-       <footnote>
-        <para>
-         <productname>Postgres-XC</productname> does not support trigger in the current version.  This may be supported in the future releases.
-        </para>
-       </footnote>
-      </simpara>
-     </listitem>
-     <listitem>
-      <simpara>views</simpara>
-     </listitem>
-     <listitem>
-      <simpara>transactional integrity, at the exception of SSI whose support is incomplete</simpara>
-     </listitem>
-     <listitem>
-      <simpara>multiversion concurrency control</simpara>
-     </listitem>
-    </itemizedlist>
-
-    Also, similar to <productname>PostgreSQL</productname>, <productname>Postgres-XC</productname> can be extended by the
-    user in many ways, for example by adding new
-
-    <itemizedlist spacing="compact">
-     <listitem>
-      <simpara>data types</simpara>
-     </listitem>
-     <listitem>
-      <simpara>functions</simpara>
-     </listitem>
-     <listitem>
-      <simpara>operators</simpara>
-     </listitem>
-     <listitem>
-      <simpara>aggregate functions</simpara>
-     </listitem>
-     <listitem>
-      <simpara>index methods</simpara>
-     </listitem>
-     <listitem>
-      <simpara>procedural languages</simpara>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    And because of the liberal license same as
-    <productname>PostgreSQL</productname>, <productname>Postgres-XC</productname>
-    can be used, modified, and distributed by anyone free of charge
-    for any purpose, be it private, commercial, or academic.
-   </para>
-  </sect2>
-
-<!## end>
-<!## XL>
-  <title> What is <productname>Postgres-XL</productname>?</title>
-
-  <sect2 id="whatis-in-short">
-   <title>In short</title>
-
-    <para>
-    Postgres-XL is an open source project to provide both write-scalability
-    massively parallel processing transparently to PostgreSQL.
-    It is a collection of tightly coupled database
-    components which can be installed in more than one hardware or
-    virtual machines.
-   </para>
-
-   <para>
-     Write-scalable means Postgres-XL can be configured with as many
-    database servers as you want and handle many more writes (updating
-    SQL statements) than a single standalone database server could
-    otherwise do. You can have more than one database
-    server which all provide a single database view. Any
-    database update from any database server is immediately visible to
-    any other transactions running on different servers.  Transparent
-    means you do not necessarily need to worry about how your data is stored in
-    more than one database servers internally.
-    <footnote>
-     <para>
-      Of course, you should use the information about how tables are stored
-      internally when you design the database physically to get most
-      from Postgres-XL.
-     </para>
-    </footnote>
-   </para>
-
-   <para>
-    You can configure Postgres-XL to run on more than one machines. It
-    stores your data in a distributed way, that is, partitioned or
-    replicated depending on what is chosen for each table.
-    <footnote>
-     <para>
-      To distinguish from PostgreSQL's native partitioning, we refer to this
-      as "distribution".  In distributed database textbooks, this is often
-      referred to as "horizontal fragment"), and more recently, sharding.
-     </para>
-    </footnote>
-    When you issue queries, Postgres-XL determines where the target
-    data is stored and dispatches corresponding plans to the servers containing the
-    target data.
-   </para>
-
-   <para>
-    In typical web systems, you can have as many web servers or
-    application servers to handle your transactions. However, you
-    cannot do this for a database server in general because all the
-    changing data have to be visible to all the transactions. Unlike
-    other database cluster solution, Postgres-XL provides this
-    capability. You can install as many database servers as you
-    like. Each database server provides uniform data view to your
-    applications.  Any database update from any server is immediately
-    visible to applications connecting the database from other
-    servers. This is on of the most important features of
-    Postgres-XL.
-   </para>
-
-   <para>
-    The other significant feature of Postgres-XL is MPP parallelism.
-    You can use Postgres-XL to handle workloads for Business Intelligence,
-    Data Warehousing, or Big Data. In Postgres-XL, a plan is generated once
-    on a coordinator, and sent down to the individual data nodes. This is
-    then executed, with the data nodes communicating directly with one another,
-    where each understands from where it is expected to receive any tuples
-    that it needs to ship, and where it needs to send to others.
-   </para>
-
-  </sect2>
-
-  <sect2 id="whatis-xc-goal">
-   <title>Postgres-XL's Goal</title>
-
-   <para>
-    The ultimate goal of Postgres-XL is to provide database
-    scalability with ACID consistency across all types of database workloads.
-    That is, Postgres-XL should provide the following features:
-    <itemizedlist spacing="compact">
-     <listitem>
-      <para>
-       Postgres-XL should provide multiple servers to accept transactions and statements
-       from applications, which are known as "Coordinator" processes.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Any Coordinator should provide consistent database view to
-       applications. Any updates from any Coordinator must be visible in
-       real time manner as if such updates are done in single
-       PostgreSQL server.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Postgres-XL should allow Datanodes to communicate directly with one
-       another execute queries in an efficient and parallel manner.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Tables should be able to be stored in the database designated as
-       replicated or distributed (known as fragments or
-       partitions). Replication and distribution should be transparent
-       to applications; that is, such replicated and distributed tables
-       are seen as single tables and the location or number of copies of
-       each record/tuple is managed by Postgres-XL and is not visible
-       to applications.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Postgres-XL provides compatible PostgreSQL API to applications.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Postgres-XL should provide single and unified view of
-       underlying PostgreSQL database servers so that SQL statements
-       do not depend on how the tables are actually stored.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-  </sect2>
-
-
-  <sect2 id="whatis-xc-key-components">
-   <title>Postgres-XL Key Components</title>
-
-   <para>
-    In this section, we will describe the main components of Postgres-XL.
-   </para>
-
-   <para>
-    Postgres-XL is composed of three major components: the GTM
-    (Global Transaction Manager), the Coordinator and the Datanode. Their
-    features are given in the following sections.
-   </para>
-
-   <sect3>
-    <title>GTM (Global Transaction Manager)</title>
-
-    <para>
-     The GTM is a key component of Postgres-XL to provide consistent
-     transaction management and tuple visibility control.
-    </para>
-
-    <para>
-     As described later in this
-     manual, <productname>PostgreSQL</productname>'s transaction
-     management is based upon MVCC (Multi-Version Concurrency Control)
-     technology.  <productname>Postgres-XL</productname> extracts this
-     technology into separate component as GTM so that
-     any <productname>Postgres-XL</productname> component's
-     transaction management is based upon single global status.
-     Details will be described in <xref linkend="overview">.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Coordinator</title>
-
-    <para>
-     The Coordinator is an interface to the database for applications. It acts like
-     conventional PostgreSQL backend process, however the Coordinator
-     does not store any actual data. The actual data is stored by the Datanodes
-     as described below. The Coordinator receives SQL statements, gets Global
-     Transaction Id and Global Snapshots as needed, determines which
-     Datanodes are involved and asks them to execute (a part of)
-     statement.  When issuing statement to Datanodes, it is
-     associated with GXID and Global Snapshot so that Multi-version Concurrency Control
-     (MVCC) properties extend cluster-wide.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Datanode</title>
-
-    <para>
-     The Datanode actually stores user data. Tables may be distributed
-     among Datanodes, or replicated to all the Datanodes.
-     The Datanode does not have global view of the whole database, it
-     just takes care of locally stored data. Incoming statement is
-     examined by the Coordinator as described next, and subplans are
-     made. These are  then transferred to
-     each Datanode involved together with GXID and Global Snapshot
-     as needed. The datanode may receive request from various
-     Coordinators in separate sessions. However, because each the
-     transaction is identified
-     uniquely and associated with consistent (global) snapshot, each Datanode
-     can properly execute in its transaction and snapshot context.
-    </para>
-
-   </sect3>
-
-  </sect2>
-
-  <sect2 id="whatis-xc-inherits-postgresql">
-   <title><productname>Postgres-XL</productname> Inherits From <productname>PostgreSQL</productname></title>
-
-   <para>
-    <productname>Postgres-XL</productname> is an extension
-    to <productname>PostgreSQL</productname> and inherits most of its
-    features.
-   </para>
-
-   <para>
-    It is an open-source descendant of
-    <productname>PostgreSQL</productname> and its
-    original Berkeley code.  It supports a large part of the SQL
-    standard and offers many modern features:
-
-    <itemizedlist spacing="compact">
-     <listitem>
-      <simpara>complex queries</simpara>
-     </listitem>
-     <listitem>
-      <simpara>
-       foreign keys
-       <footnote>
-        <para>
-         <productname>Postgres-XL</productname>'s foreign key usage has some restrictions.  For details, see <xref linkend="SQL-CREATETABLE">.
-        </para>
-       </footnote>
-      </simpara>
-     </listitem>
-     <listitem>
-      <simpara>
-       triggers
-       <footnote>
-        <para>
-         <productname>Postgres-XL</productname> does not support trigger in the current version.  This may be supported in the future releases.
-        </para>
-       </footnote>
-      </simpara>
-     </listitem>
-     <listitem>
-      <simpara>views</simpara>
-     </listitem>
-     <listitem>
-      <simpara>transactional integrity, at the exception of SSI whose support is incomplete</simpara>
-     </listitem>
-     <listitem>
-      <simpara>multiversion concurrency control</simpara>
-     </listitem>
-    </itemizedlist>
-
-    Also, similar to <productname>PostgreSQL</productname>, <productname>Postgres-XL</productname> can be extended by the
-    user in many ways, for example by adding new
-
-    <itemizedlist spacing="compact">
-     <listitem>
-      <simpara>data types</simpara>
-     </listitem>
-     <listitem>
-      <simpara>functions</simpara>
-     </listitem>
-     <listitem>
-      <simpara>operators</simpara>
-     </listitem>
-     <listitem>
-      <simpara>aggregate functions</simpara>
-     </listitem>
-     <listitem>
-      <simpara>index methods</simpara>
-     </listitem>
-     <listitem>
-      <simpara>procedural languages</simpara>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    <productname>Postgres-XL</productname>
-    can be used, modified, and distributed by anyone free of charge
-    for any purpose, be it private, commercial, or academic, provided it
-    adheres to the Mozilla Public License version 2.
-   </para>
-
-  </sect2>
-
-<!## end>
-
-<!## PG>
-  <para>
-   <productname>PostgreSQL</productname> is an object-relational
-   database management system (<acronym>ORDBMS</acronym>) based on
-   <ulink url="http://db.cs.berkeley.edu/postgres.html">
-   <productname>POSTGRES, Version 4.2</productname></ulink>,
-   developed at the University of California at Berkeley Computer Science
-   Department.  POSTGRES pioneered many concepts that only became
-   available in some commercial database systems much later.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname> is an open-source descendant
-   of this original Berkeley code.  It supports a large part of the SQL
-   standard and offers many modern features:
-
-   <itemizedlist spacing="compact">
-    <listitem>
-     <simpara>complex queries</simpara>
-    </listitem>
-    <listitem>
-     <simpara>foreign keys</simpara>
-    </listitem>
-    <listitem>
-     <simpara>triggers</simpara>
-    </listitem>
-    <listitem>
-     <simpara>views</simpara>
-    </listitem>
-    <listitem>
-     <simpara>transactional integrity</simpara>
-    </listitem>
-    <listitem>
-     <simpara>multiversion concurrency control</simpara>
-    </listitem>
-   </itemizedlist>
-
-   Also, <productname>PostgreSQL</productname> can be extended by the
-   user in many ways, for example by adding new
-
-   <itemizedlist spacing="compact">
-    <listitem>
-     <simpara>data types</simpara>
-    </listitem>
-    <listitem>
-     <simpara>functions</simpara>
-    </listitem>
-    <listitem>
-     <simpara>operators</simpara>
-    </listitem>
-    <listitem>
-     <simpara>aggregate functions</simpara>
-    </listitem>
-    <listitem>
-     <simpara>index methods</simpara>
-    </listitem>
-    <listitem>
-     <simpara>procedural languages</simpara>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   And because of the liberal license,
-   <productname>PostgreSQL</productname> can be used, modified, and
-   distributed by anyone free of charge for any purpose, be it
-   private, commercial, or academic.
-  </para>
-<!## end>
- </sect1>
-
- &history;
- &notation;
- &info;
- &problems;
-
-</preface>
diff --git a/doc-xc/src/sgml/isn.sgmlin b/doc-xc/src/sgml/isn.sgmlin
deleted file mode 100644
index 8fce35145c..0000000000
--- a/doc-xc/src/sgml/isn.sgmlin
+++ /dev/null
@@ -1,394 +0,0 @@
-<!-- doc/src/sgml/isn.sgml -->
-
-<sect1 id="isn" xreflabel="isn">
- <title>isn</title>
-
- <indexterm zone="isn">
-  <primary>isn</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>isn</filename> module provides data types for the following
-  international product numbering standards: EAN13, UPC, ISBN (books), ISMN
-  (music), and ISSN (serials).  Numbers are validated on input according to a
-  hard-coded list of prefixes; this list of prefixes is also used to hyphenate
-  numbers on output.  Since new prefixes are assigned from time to time, the
-  list of prefixes may be out of date.  It is hoped that a future version of
-  this module will obtained the prefix list from one or more tables that
-  can be easily updated by users as needed; however, at present, the
-  list can only be updated by modifying the source code and recompiling.
-  Alternatively, prefix validation and hyphenation support may be
-  dropped from a future version of this module.
- </para>
-
- <sect2>
-  <title>Data Types</title>
-
-&pgnotice;
-  <para>
-   <xref linkend="isn-datatypes"> shows the data types provided by
-   the <filename>isn</filename> module.
-  </para>
-
-  <table id="isn-datatypes">
-   <title><filename>isn</filename> Data Types</title>
-   <tgroup cols="2">
-    <thead>
-     <row>
-      <entry>Data Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><type>EAN13</type></entry>
-      <entry>
-       European Article Numbers, always displayed in the EAN13 display format
-      </entry>
-     </row>
-
-     <row>
-      <entry><type>ISBN13</type></entry>
-      <entry>
-       International Standard Book Numbers to be displayed in
-       the new EAN13 display format
-      </entry>
-     </row>
-
-     <row>
-      <entry><type>ISMN13</type></entry>
-      <entry>
-       International Standard Music Numbers to be displayed in
-       the new EAN13 display format
-      </entry>
-     </row>
-     <row>
-      <entry><type>ISSN13</type></entry>
-      <entry>
-       International Standard Serial Numbers to be displayed in the new
-       EAN13 display format
-      </entry>
-     </row>
-     <row>
-      <entry><type>ISBN</type></entry>
-      <entry>
-       International Standard Book Numbers to be displayed in the old
-       short display format
-      </entry>
-     </row>
-     <row>
-      <entry><type>ISMN</type></entry>
-      <entry>
-       International Standard Music Numbers to be displayed in the
-       old short display format
-      </entry>
-     </row>
-     <row>
-      <entry><type>ISSN</type></entry>
-      <entry>
-       International Standard Serial Numbers to be displayed in the
-       old short display format
-      </entry>
-     </row>
-     <row>
-      <entry><type>UPC</type></entry>
-      <entry>
-       Universal Product Codes
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Some notes:
-  </para>
-
-  <orderedlist>
-   <listitem>
-    <para>ISBN13, ISMN13, ISSN13 numbers are all EAN13 numbers.</para>
-   </listitem>
-   <listitem>
-    <para>EAN13 numbers aren't always ISBN13, ISMN13 or ISSN13 (some
-    are).</para>
-   </listitem>
-   <listitem>
-    <para>Some ISBN13 numbers can be displayed as ISBN.</para>
-   </listitem>
-   <listitem>
-    <para>Some ISMN13 numbers can be displayed as ISMN.</para>
-   </listitem>
-   <listitem>
-    <para>Some ISSN13 numbers can be displayed as ISSN.</para>
-   </listitem>
-   <listitem>
-    <para>UPC numbers are a subset of the EAN13 numbers (they are basically
-    EAN13 without the first <literal>0</> digit).</para>
-   </listitem>
-   <listitem>
-    <para>All UPC, ISBN, ISMN and ISSN numbers can be represented as EAN13
-    numbers.</para>
-   </listitem>
-  </orderedlist>
-
-  <para>
-   Internally, all these types use the same representation (a 64-bit
-   integer), and all are interchangeable.  Multiple types are provided
-   to control display formatting and to permit tighter validity checking
-   of input that is supposed to denote one particular type of number.
-  </para>
-
-  <para>
-   The <type>ISBN</>, <type>ISMN</>, and <type>ISSN</> types will display the
-   short version of the number (ISxN 10) whenever it's possible, and will show
-   ISxN 13 format for numbers that do not fit in the short version.
-   The <type>EAN13</type>, <type>ISBN13</type>, <type>ISMN13</type> and
-   <type>ISSN13</type> types will always display the long version of the ISxN
-   (EAN13).
-  </para>
- </sect2>
-
- <sect2>
-  <title>Casts</title>
-
-&common;
-  <para>
-   The <filename>isn</> module provides the following pairs of type casts:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     ISBN13 &lt;=&gt; EAN13
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     ISMN13 &lt;=&gt; EAN13
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     ISSN13 &lt;=&gt; EAN13
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     ISBN &lt;=&gt; EAN13
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     ISMN &lt;=&gt; EAN13
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     ISSN &lt;=&gt; EAN13
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     UPC  &lt;=&gt; EAN13
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     ISBN &lt;=&gt; ISBN13
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     ISMN &lt;=&gt; ISMN13
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     ISSN &lt;=&gt; ISSN13
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   When casting from <type>EAN13</> to another type, there is a run-time
-   check that the value is within the domain of the other type, and an error
-   is thrown if not.  The other casts are simply relabelings that will
-   always succeed.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Functions and Operators</title>
-
-&common;
-  <para>
-   The <filename>isn</> module provides the standard comparison operators,
-   plus B-tree and hash indexing support for all these data types.  In
-   addition there are several specialized functions; shown in <xref linkend="isn-functions">.
-   In this table,
-   <type>isn</> means any one of the module's data types.
-  </para>
-
-  <table id="isn-functions">
-   <title><filename>isn</> Functions</title>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Returns</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><function>isn_weak(boolean)</function></entry>
-      <entry><type>boolean</type></entry>
-      <entry>Sets the weak input mode (returns new setting)</entry>
-     </row>
-     <row>
-      <entry><function>isn_weak()</function></entry>
-      <entry><type>boolean</type></entry>
-      <entry>Gets the current status of the weak mode</entry>
-     </row>
-     <row>
-      <entry><function>make_valid(isn)</function></entry>
-      <entry><type>isn</type></entry>
-      <entry>Validates an invalid number (clears the invalid flag)</entry>
-     </row>
-     <row>
-      <entry><function>is_valid(isn)</function></entry>
-      <entry><type>boolean</type></entry>
-      <entry>Checks for the presence of the invalid flag</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   <firstterm>Weak</firstterm> mode is used to be able to insert invalid data
-   into a table. Invalid means the check digit is wrong, not that there are
-   missing numbers.
-  </para>
-
-  <para>
-   Why would you want to use the weak mode? Well, it could be that
-   you have a huge collection of ISBN numbers, and that there are so many of
-   them that for weird reasons some have the wrong check digit (perhaps the
-   numbers were scanned from a printed list and the OCR got the numbers wrong,
-   perhaps the numbers were manually captured... who knows). Anyway, the point
-   is you might want to clean the mess up, but you still want to be able to
-   have all the numbers in your database and maybe use an external tool to
-   locate the invalid numbers in the database so you can verify the
-   information and validate it more easily; so for example you'd want to
-   select all the invalid numbers in the table.
-  </para>
-
-  <para>
-   When you insert invalid numbers in a table using the weak mode, the number
-   will be inserted with the corrected check digit, but it will be displayed
-   with an exclamation mark (<literal>!</>) at the end, for example
-   <literal>0-11-000322-5!</>.  This invalid marker can be checked with
-   the <function>is_valid</> function and cleared with the
-   <function>make_valid</> function.
-  </para>
-
-  <para>
-   You can also force the insertion of invalid numbers even when not in the
-   weak mode, by appending the <literal>!</> character at the end of the
-   number.
-  </para>
-
-  <para>
-   Another special feature is that during input, you can write
-   <literal>?</> in place of the check digit, and the correct check digit
-   will be inserted automatically.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Examples</title>
-
-<programlisting>
---Using the types directly:
-SELECT isbn('978-0-393-04002-9');
-SELECT isbn13('0901690546');
-SELECT issn('1436-4522');
-
---Casting types:
--- note that you can only cast from ean13 to another type when the
--- number would be valid in the realm of the target type;
--- thus, the following will NOT work: select isbn(ean13('0220356483481'));
--- but these will:
-SELECT upc(ean13('0220356483481'));
-SELECT ean13(upc('220356483481'));
-
---Create a table with a single column to hold ISBN numbers:
-CREATE TABLE test (id isbn);
-INSERT INTO test VALUES('9780393040029');
-
---Automatically calculate check digits (observe the '?'):
-INSERT INTO test VALUES('220500896?');
-INSERT INTO test VALUES('978055215372?');
-
-SELECT issn('3251231?');
-SELECT ismn('979047213542?');
-
---Using the weak mode:
-SELECT isn_weak(true);
-INSERT INTO test VALUES('978-0-11-000533-4');
-INSERT INTO test VALUES('9780141219307');
-INSERT INTO test VALUES('2-205-00876-X');
-SELECT isn_weak(false);
-
-SELECT id FROM test WHERE NOT is_valid(id);
-UPDATE test SET id = make_valid(id) WHERE id = '2-205-00876-X!';
-
-SELECT * FROM test;
-
-SELECT isbn13(id) FROM test;
-</programlisting>
- </sect2>
-
- <sect2>
-  <title>Bibliography</title>
-
-  <para>
-   The information to implement this module was collected from
-   several sites, including:
-   <itemizedlist>
-    <listitem><para><ulink url="http://www.isbn-international.org/"></ulink></para></listitem>
-    <listitem><para><ulink url="http://www.issn.org/"></ulink></para></listitem>
-    <listitem><para><ulink url="http://www.ismn-international.org/"></ulink></para></listitem>
-    <listitem><para><ulink url="http://www.wikipedia.org/"></ulink></para></listitem>
-   </itemizedlist>
-
-   The prefixes used for hyphenation were also compiled from:
-   <itemizedlist>
-    <listitem><para><ulink url="http://www.gs1.org/productssolutions/idkeys/support/prefix_list.html"></ulink></para></listitem>
-    <listitem><para><ulink url="http://www.isbn-international.org/en/identifiers.html"></ulink></para></listitem>
-    <listitem><para><ulink url="http://www.ismn-international.org/ranges.html"></ulink></para></listitem>
-   </itemizedlist>
-
-   Care was taken during the creation of the algorithms and they
-   were meticulously verified against the suggested algorithms
-   in the official ISBN, ISMN, ISSN User Manuals.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-  <para>
-   Germ&aacute;n M&eacute;ndez Bravo (Kronuz), 2004 - 2006
-  </para>
-
-  <para>
-   This module was inspired by Garrett A. Wollman's
-   <filename>isbn_issn</> code.
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/jadetex.cfg b/doc-xc/src/sgml/jadetex.cfg
deleted file mode 100644
index 25b79312eb..0000000000
--- a/doc-xc/src/sgml/jadetex.cfg
+++ /dev/null
@@ -1,30 +0,0 @@
-% doc/src/sgml/jadetex.cfg
-%
-% This file redefines FlowObjectSetup to eliminate one of the two control
-% sequences it normally creates, thereby substantially reducing string usage
-% and permitting the complete Postgres documentation to be built without
-% overflowing a hard-to-expand TeX limit.  The only known penalty is an
-% increased number of TeX warnings about ignoring duplicate definitions.
-%
-% Curiously, we only see the failure when building PDF output --- plain PS
-% output does not come anywhere close to overflowing the string table.
-% There may be another solution hidden in that observation.
-%
-\def\FlowObjectSetup#1{%
-\ifDoFOBSet
-  \ifLabelElements
-     \ifx\Label\@empty\let\Label\Element\fi
-  \fi
-  \ifx\Label\@empty\else
-       \bgroup
-         \ifNestedLink
-         \else
-           \hyper@anchorstart{\Label}\hyper@anchorend
-           \PageLabel{\Label}%
-         \fi
-       \egroup
-       \let\Label\@empty
-       \let\Element\@empty
-  \fi
-\fi
-}
diff --git a/doc-xc/src/sgml/keywords.sgmlin b/doc-xc/src/sgml/keywords.sgmlin
deleted file mode 100644
index 48a30616a6..0000000000
--- a/doc-xc/src/sgml/keywords.sgmlin
+++ /dev/null
@@ -1,6201 +0,0 @@
-<!-- doc/src/sgml/keywords.sgml -->
-
-<appendix id="sql-keywords-appendix">
- <title><acronym>SQL</acronym> Key Words</title>
-
- <indexterm zone="sql-keywords-appendix">
-  <primary>key word</primary>
-  <secondary>list of</secondary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  <xref linkend="keywords-table"> lists all tokens that are key words
-  in the SQL standard and in <productname>PostgreSQL</productname>
-  &version;.  Background information can be found in <xref
-  linkend="sql-syntax-identifiers">.
- </para>
-
- <para>
-  SQL distinguishes between <firstterm>reserved</firstterm> and
-  <firstterm>non-reserved</firstterm> key words.  According to the standard,
-  reserved key words
-  are the only real key words; they are never allowed as identifiers.
-  Non-reserved key words only have a special meaning in particular
-  contexts and can be used as identifiers in other contexts.  Most
-  non-reserved key words are actually the names of built-in tables
-  and functions specified by SQL.  The concept of non-reserved key
-  words essentially only exists to declare that some predefined meaning
-  is attached to a word in some contexts.
- </para>
-
- <para>
-  In the <productname>PostgreSQL</productname> parser life is a bit
-  more complicated. There are several different classes of tokens
-  ranging from those that can never be used as an identifier to those
-  that have absolutely no special status in the parser as compared to
-  an ordinary identifier.  (The latter is usually the case for
-  functions specified by SQL.)  Even reserved key words are not
-  completely reserved in <productname>PostgreSQL</productname>, but
-  can be used as column labels (for example, <literal>SELECT 55 AS
-  CHECK</literal>, even though <token>CHECK</token> is a reserved key
-  word).
- </para>
-
- <para>
-  In <xref linkend="keywords-table"> in the column for
-  <productname>PostgreSQL</productname> we classify as
-  <quote>non-reserved</quote> those key words that are explicitly
-  known to the parser but are allowed as column or table names.
-  Some key words that are otherwise
-  non-reserved cannot be used as function or data type names and are
-  marked accordingly.  (Most of these words represent built-in
-  functions or data types with special syntax.  The function or type
-  is still available but it cannot be redefined by the user.)  Labeled
-  <quote>reserved</quote> are those tokens that are not allowed as
-  column or table names.  Some reserved key words are
-  allowable as names for functions or data types; this is also shown in the
-  table.  If not so marked, a reserved key word is only allowed as an
-  <quote>AS</quote> column label name.
- </para>
-
- <para>
-  As a general rule, if you get spurious parser errors for commands
-  that contain any of the listed key words as an identifier you should
-  try to quote the identifier to see if the problem goes away.
- </para>
-
- <para>
-  It is important to understand before studying <xref
-  linkend="keywords-table"> that the fact that a key word is not
-  reserved in <productname>PostgreSQL</productname> does not mean that
-  the feature related to the word is not implemented.  Conversely, the
-  presence of a key word does not indicate the existence of a feature.
- </para>
-
-
-<!--
- The following table is semi-automatically generated.  You can update it
- manually, but when you have a lot of changes talk to <[email protected]>
- about remaking it.
--->
-
-<table id="keywords-table">
- <title><acronym>SQL</acronym> Key Words</title>
-
- <tgroup cols="5">
-  <thead>
-   <row>
-    <entry>Key Word</entry>
-    <entry><productname>PostgreSQL</productname></entry>
-    <entry>SQL:2008</entry>
-    <entry>SQL:2003</entry>
-    <entry>SQL:1999</entry>
-    <entry>SQL-92</entry>
-   </row>
-  </thead>
-
-  <tbody>
-   <row>
-    <entry><token>A</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ABORT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ABS</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ABSENT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ABSOLUTE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ACCESS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ACCORDING</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ACTION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ADA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>ADD</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ADMIN</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AFTER</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AGGREGATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ALIAS</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ALL</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ALLOCATE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ALSO</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ALTER</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ALWAYS</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ANALYSE</token></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ANALYZE</token></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AND</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ANY</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ARE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ARRAY</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ARRAY_AGG</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AS</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ASC</token></entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ASENSITIVE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ASSERTION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ASSIGNMENT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ASYMMETRIC</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ATOMIC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ATTRIBUTE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ATTRIBUTES</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AUTHORIZATION</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>AVG</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BACKWARD</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## XC>
-   <row>
-    <entry><token>BARRIER</token></entry>
-    <entry>non-reserved (XC only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-<!## XL>
-   <row>
-    <entry><token>BARRIER</token></entry>
-    <entry>non-reserved (XL only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-   <row>
-    <entry><token>BASE64</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BEFORE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BEGIN</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BERNOULLI</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BETWEEN</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BIGINT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BINARY</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BIT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BITVAR</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BIT_LENGTH</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BLOB</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BLOCKED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BOM</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BOOLEAN</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BOTH</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BREADTH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BY</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>C</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CACHE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CALL</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CALLED</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CARDINALITY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CASCADE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CASCADED</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CASE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CAST</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CATALOG</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CATALOG_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CEIL</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CEILING</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CHAIN</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CHAR</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHARACTER</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHARACTERISTICS</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CHARACTERS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CHARACTER_LENGTH</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHARACTER_SET_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHARACTER_SET_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHARACTER_SET_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHAR_LENGTH</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHECK</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHECKED</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CHECKPOINT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CLASS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CLASS_ORIGIN</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-<!## XC>
-   <row>
-    <entry><token>CLEAN</token></entry>
-    <entry>non-reserved (XC only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-<!## XL>
-   <row>
-    <entry><token>CLEAN</token></entry>
-    <entry>non-reserved (XL only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-   <row>
-    <entry><token>CLOB</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CLOSE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CLUSTER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COALESCE</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COBOL</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>COLLATE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COLLATION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COLLATION_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>COLLATION_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>COLLATION_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>COLLECT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COLUMN</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COLUMNS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COLUMN_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>COMMAND_FUNCTION</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>COMMAND_FUNCTION_CODE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COMMENT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COMMENTS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COMMIT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COMMITTED</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>COMPLETION</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONCURRENTLY</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONDITION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONDITION_NUMBER</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONFIGURATION</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONNECT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONNECTION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONNECTION_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONSTRAINT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONSTRAINTS</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONSTRAINT_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONSTRAINT_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONSTRAINT_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONSTRUCTOR</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONTAINS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONTENT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONTINUE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONTROL</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONVERSION</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONVERT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COPY</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CORR</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CORRESPONDING</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COST</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COUNT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COVAR_POP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COVAR_SAMP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CREATE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CROSS</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CSV</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CUBE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CUME_DIST</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CURRENT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_CATALOG</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_DATE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_DEFAULT_TRANSFORM_GROUP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_PATH</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_ROLE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_SCHEMA</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_TIME</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_TIMESTAMP</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_TRANSFORM_GROUP_FOR_TYPE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_USER</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CURSOR</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CURSOR_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CYCLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DATA</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>DATABASE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DATALINK</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DATE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DATETIME_INTERVAL_CODE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>DATETIME_INTERVAL_PRECISION</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>DAY</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DB</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DEALLOCATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DEC</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DECIMAL</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DECLARE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DEFAULT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DEFAULTS</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DEFERRABLE</token></entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DEFERRED</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DEFINED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DEFINER</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DEGREE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DELETE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DELIMITER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DELIMITERS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DENSE_RANK</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DEPTH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DEREF</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DERIVED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DESC</token></entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DESCRIBE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DESCRIPTOR</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DESTROY</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DESTRUCTOR</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DETERMINISTIC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DIAGNOSTICS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DICTIONARY</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DISABLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DISCARD</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DISCONNECT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DISPATCH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DISTINCT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-<!## XC>
-   <row>
-    <entry><token>DISTRIBUTE</token></entry>
-    <entry>non-reserved (XC only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-<!## XL>
-   <row>
-    <entry><token>DISTRIBUTE</token></entry>
-    <entry>non-reserved (XL only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-   <row>
-    <entry><token>DLNEWCOPY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DLPREVIOUSCOPY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DLURLCOMPLETE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DLURLCOMPLETEONLY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DLURLCOMPLETEWRITE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DLURLPATH</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DLURLPATHONLY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DLURLPATHWRITE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DLURLSCHEME</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DLURLSERVER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DLVALUE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DO</token></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DOCUMENT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DOMAIN</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DOUBLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DROP</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DYNAMIC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DYNAMIC_FUNCTION</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>DYNAMIC_FUNCTION_CODE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EACH</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ELEMENT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ELSE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EMPTY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ENABLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ENCODING</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ENCRYPTED</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>END</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>END-EXEC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ENUM</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EQUALS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ESCAPE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EVERY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXCEPT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXCEPTION</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXCLUDE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXCLUDING</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXCLUSIVE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXEC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXECUTE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXISTING</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXISTS</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXPLAIN</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXTENSION</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXTERNAL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXTRACT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FALSE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FAMILY</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FETCH</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FILE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FILTER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FINAL</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FIRST</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FIRST_VALUE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FLAG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FLOAT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FLOOR</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FOLLOWING</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FOR</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FORCE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FOREIGN</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FORTRAN</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>FORWARD</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FOUND</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FREE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FREEZE</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FROM</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FULL</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FUNCTION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FUNCTIONS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FUSION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>G</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>GENERAL</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>GENERATED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>GET</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GLOBAL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GO</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GOTO</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GRANT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GRANTED</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>GREATEST</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>GROUP</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GROUPING</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>HANDLER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## XC>
-   <row>
-    <entry><token>HASH</token></entry>
-    <entry>non-reserved (XC only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-<!## XL>
-   <row>
-    <entry><token>HASH</token></entry>
-    <entry>non-reserved (XL only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-   <row>
-    <entry><token>HAVING</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>HEADER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>HEX</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>HIERARCHY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>HOLD</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>HOST</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>HOUR</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ID</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IDENTITY</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>IF</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IGNORE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ILIKE</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IMMEDIATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>IMMUTABLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IMPLEMENTATION</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IMPLICIT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IMPORT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IN</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INCLUDING</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INCREMENT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INDENT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INDEX</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INDEXES</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INDICATOR</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INFIX</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INHERIT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INHERITS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INITIALIZE</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INITIALLY</token></entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INLINE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INNER</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INOUT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INPUT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INSENSITIVE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INSERT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INSTANCE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INSTANTIABLE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INSTEAD</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INTEGER</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INTEGRITY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INTERSECT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INTERSECTION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INTERVAL</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INTO</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INVOKER</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IS</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ISNULL</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ISOLATION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ITERATE</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>JOIN</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>K</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>KEY</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>KEY_MEMBER</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>KEY_TYPE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LABEL</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LAG</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LANGUAGE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LARGE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LAST</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LAST_VALUE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LATERAL</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LC_COLLATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LC_CTYPE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LEAD</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LEADING</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LEAST</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LEFT</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LENGTH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>LESS</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LEVEL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LIBRARY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LIKE</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LIKE_REGEX</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LIMIT</token></entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LINK</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LISTEN</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LN</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOAD</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOCAL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LOCALTIME</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOCALTIMESTAMP</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOCATION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOCATOR</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOCK</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOWER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>M</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MAP</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MAPPING</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MATCH</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>MATCHED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MAX</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>MAXVALUE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MAX_CARDINALITY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MEMBER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MERGE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MESSAGE_LENGTH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>MESSAGE_OCTET_LENGTH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>MESSAGE_TEXT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>METHOD</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MIN</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>MINUTE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>MINVALUE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MOD</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MODE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MODIFIES</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MODIFY</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MODULE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-<!## XC>
-   <row>
-    <entry><token>MODULO</token></entry>
-    <entry>non-reserved (XC only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-<!## XL>
-   <row>
-    <entry><token>MODULO</token></entry>
-    <entry>non-reserved (XL only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-   <row>
-    <entry><token>MONTH</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>MORE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>MOVE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MULTISET</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MUMPS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>NAME</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>NAMES</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NAMESPACE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NATIONAL</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NATURAL</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NCHAR</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NCLOB</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NESTING</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NEW</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NEXT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NFC</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NFD</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NFKC</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NFKD</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NIL</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NO</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NONE</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NORMALIZE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NORMALIZED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NOT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NOTHING</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NOTIFY</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NOTNULL</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NOWAIT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NTH_VALUE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NTILE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NULL</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NULLABLE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>NULLIF</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NULLS</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NUMBER</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>NUMERIC</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OBJECT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OCCURRENCES_REGEX</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OCTETS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OCTET_LENGTH</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OF</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OFF</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OFFSET</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OIDS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OLD</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ON</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ONLY</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OPEN</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OPERATION</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OPERATOR</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OPTION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OPTIONS</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OR</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ORDER</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ORDERING</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ORDINALITY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OTHERS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OUT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OUTER</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OUTPUT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OVER</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OVERLAPS</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OVERLAY</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OVERRIDING</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OWNED</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OWNER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>P</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PAD</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETERS</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_MODE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_ORDINAL_POSITION</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_SPECIFIC_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_SPECIFIC_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_SPECIFIC_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARSER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARTIAL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PARTITION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PASCAL</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>PASSING</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PASSTHROUGH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PASSWORD</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PATH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PERCENTILE_CONT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PERCENTILE_DISC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PERCENT_RANK</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PERMISSION</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PLACING</token></entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PLANS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PLI</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>POSITION</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>POSITION_REGEX</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>POSTFIX</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>POWER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PRECEDING</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PRECISION</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PREFIX</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PREORDER</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PREPARE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PREPARED</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PRESERVE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PRIMARY</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PRIOR</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PRIVILEGES</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PROCEDURAL</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PROCEDURE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PUBLIC</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>QUOTE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RANGE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RANK</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>READ</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>READS</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REAL</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>REASSIGN</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RECHECK</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RECOVERY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RECURSIVE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REF</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REFERENCES</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>REFERENCING</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REGR_AVGX</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REGR_AVGY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REGR_COUNT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REGR_INTERCEPT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REGR_R2</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REGR_SLOPE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REGR_SXX</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REGR_SXY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REGR_SYY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REINDEX</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RELATIVE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>RELEASE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RENAME</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REPEATABLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>REPLACE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REPLICA</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## XC>
-   <row>
-    <entry><token>REPLICATION</token></entry>
-    <entry>non-reserved (XC only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-<!## XL>
-   <row>
-    <entry><token>REPLICATION</token></entry>
-    <entry>non-reserved (XL only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-   <row>
-    <entry><token>REQUIRING</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RESET</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RESPECT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RESTART</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RESTORE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RESTRICT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>RESULT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RETURN</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RETURNED_CARDINALITY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RETURNED_LENGTH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>RETURNED_OCTET_LENGTH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>RETURNED_SQLSTATE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>RETURNING</token></entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RETURNS</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REVOKE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>RIGHT</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-<!## XC>
-   <row>
-    <entry><token>ROBIN</token></entry>
-    <entry>non-reserved (XC only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-<!## XL>
-   <row>
-    <entry><token>ROBIN</token></entry>
-    <entry>non-reserved (XL only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-   <row>
-    <entry><token>ROLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROLLBACK</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ROLLUP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-<!## XC>
-   <row>
-    <entry><token>ROUNG</token></entry>
-    <entry>non-reserved (XC only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-<!## XL>
-   <row>
-    <entry><token>ROUNG</token></entry>
-    <entry>non-reserved (XL only)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-<!## end>
-   <row>
-    <entry><token>ROUTINE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROUTINE_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROUTINE_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROUTINE_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROW</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROWS</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ROW_COUNT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>ROW_NUMBER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RULE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SAVEPOINT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SCALE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>SCHEMA</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SCHEMA_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>SCOPE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SCOPE_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SCOPE_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SCOPE_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SCROLL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SEARCH</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SECOND</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SECTION</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SECURITY</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SELECT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SELECTIVE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SELF</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SENSITIVE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SEQUENCE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SEQUENCES</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SERIALIZABLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>SERVER</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SERVER_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>SESSION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SESSION_USER</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SET</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SETOF</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SETS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SHARE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SHOW</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SIMILAR</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SIMPLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SIZE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SMALLINT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SOME</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SOURCE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SPACE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SPECIFIC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SPECIFICTYPE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SPECIFIC_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SQL</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SQLCODE</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SQLERROR</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SQLEXCEPTION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SQLSTATE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SQLWARNING</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SQRT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STABLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STANDALONE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>START</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STATE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STATEMENT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STATIC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STATISTICS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STDDEV_POP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STDDEV_SAMP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STDIN</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STDOUT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STORAGE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STRICT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STRIP</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STRUCTURE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STYLE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SUBCLASS_ORIGIN</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>SUBLIST</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SUBMULTISET</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SUBSTRING</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SUBSTRING_REGEX</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SUM</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SYMMETRIC</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SYSID</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SYSTEM</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SYSTEM_USER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>T</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TABLE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TABLES</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TABLESAMPLE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TABLESPACE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TABLE_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>TEMP</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TEMPLATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TEMPORARY</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TERMINATE</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TEXT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>THAN</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>THEN</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TIES</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TIME</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TIMESTAMP</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TIMEZONE_HOUR</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TIMEZONE_MINUTE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TO</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TOKEN</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TOP_LEVEL_COUNT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRAILING</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TRANSACTION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TRANSACTIONS_COMMITTED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRANSACTIONS_ROLLED_BACK</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRANSACTION_ACTIVE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRANSFORM</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRANSFORMS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRANSLATE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TRANSLATE_REGEX</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRANSLATION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TREAT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRIGGER</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRIGGER_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRIGGER_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRIGGER_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRIM</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TRIM_ARRAY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRUE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TRUNCATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRUSTED</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TYPE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>UESCAPE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNBOUNDED</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNCOMMITTED</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>UNDER</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNENCRYPTED</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNION</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>UNIQUE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>UNKNOWN</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>UNLINK</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNLISTEN</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNLOGGED</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNNAMED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>UNNEST</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNTIL</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNTYPED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UPDATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>UPPER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>URI</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>USAGE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>USER</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>USER_DEFINED_TYPE_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>USER_DEFINED_TYPE_CODE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>USER_DEFINED_TYPE_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>USER_DEFINED_TYPE_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>USING</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>VACUUM</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VALID</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VALIDATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VALIDATOR</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VALUE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>VALUES</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>VARBINARY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VARCHAR</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>VARIABLE</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VARIADIC</token></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VARYING</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>VAR_POP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VAR_SAMP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VERBOSE</token></entry>
-    <entry>reserved (can be function or type)</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VERSION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VIEW</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>VOLATILE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>WHEN</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>WHENEVER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>WHERE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>WHITESPACE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>WIDTH_BUCKET</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>WINDOW</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>WITH</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>WITHIN</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>WITHOUT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>WORK</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>WRAPPER</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>WRITE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>XML</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLAGG</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLATTRIBUTES</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLBINARY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLCAST</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLCOMMENT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLCONCAT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLDECLARATION</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLDOCUMENT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLELEMENT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLEXISTS</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLFOREST</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLITERATE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLNAMESPACES</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLPARSE</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLPI</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLQUERY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLROOT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLSCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLSERIALIZE</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLTABLE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLTEXT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>XMLVALIDATE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>YEAR</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>YES</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ZONE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-  </tbody>
- </tgroup>
-</table>
-
-
-</appendix>
diff --git a/doc-xc/src/sgml/legal.sgmlin b/doc-xc/src/sgml/legal.sgmlin
deleted file mode 100644
index a6bec857da..0000000000
--- a/doc-xc/src/sgml/legal.sgmlin
+++ /dev/null
@@ -1,456 +0,0 @@
-<!-- doc/src/sgml/legal.sgml -->
-
-<copyright>
- <year>1996-2011</year>
- <holder>The PostgreSQL Global Development Group</holder>
-</copyright>
-<!## XC>
-<copyright>
- <year>2009-2012</year>
- <holder>Postgres-XC Development Group</holder>
-</copyright>
-<!## end>
-<!## XL>
-<copyright>
- <year>2009-2012</year>
- <holder>Postgres-XC Development Group</holder>
-</copyright>
-<copyright>
- <year>2012-2014</year>
- <holder>TransLattice, Inc.</holder>
-</copyright>
-<!## end>
-
-<legalnotice id="legalnotice">
- <title>Legal Notice</title>
-
- <para>
-<!## PG>
-  <productname>PostgreSQL</productname> is Copyright &copy; 1996-2011
-  by the PostgreSQL Global Development Group and is distributed under
-  the terms of the license of the University of California below.
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> is Copyright &copy; 1996-2011
-  by the PostgreSQL Global Development Group and Copyright &copy;
-  2010-2012 by Postgres-XC Development Group, and is distributed under 
-  the terms of the license of the University of California below.
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> is Copyright &copy; 2012-2014
-  by TransLattice, Inc. and distributed under the terms of the license
-  below.
- </para>
- <screen>
-Mozilla Public License Version 2.0
-==================================
-
-1. Definitions
---------------
-
-1.1. "Contributor"
-    means each individual or legal entity that creates, contributes to
-    the creation of, or owns Covered Software.
-
-1.2. "Contributor Version"
-    means the combination of the Contributions of others (if any) used
-    by a Contributor and that particular Contributor's Contribution.
-
-1.3. "Contribution"
-    means Covered Software of a particular Contributor.
-
-1.4. "Covered Software"
-    means Source Code Form to which the initial Contributor has attached
-    the notice in Exhibit A, the Executable Form of such Source Code
-    Form, and Modifications of such Source Code Form, in each case
-    including portions thereof.
-
-1.5. "Incompatible With Secondary Licenses"
-    means
-
-    (a) that the initial Contributor has attached the notice described
-        in Exhibit B to the Covered Software; or
-
-    (b) that the Covered Software was made available under the terms of
-        version 1.1 or earlier of the License, but not also under the
-        terms of a Secondary License.
-
-1.6. "Executable Form"
-    means any form of the work other than Source Code Form.
-
-1.7. "Larger Work"
-    means a work that combines Covered Software with other material, in 
-    a separate file or files, that is not Covered Software.
-
-1.8. "License"
-    means this document.
-
-1.9. "Licensable"
-    means having the right to grant, to the maximum extent possible,
-    whether at the time of the initial grant or subsequently, any and
-    all of the rights conveyed by this License.
-
-1.10. "Modifications"
-    means any of the following:
-
-    (a) any file in Source Code Form that results from an addition to,
-        deletion from, or modification of the contents of Covered
-        Software; or
-
-    (b) any new file in Source Code Form that contains any Covered
-        Software.
-
-1.11. "Patent Claims" of a Contributor
-    means any patent claim(s), including without limitation, method,
-    process, and apparatus claims, in any patent Licensable by such
-    Contributor that would be infringed, but for the grant of the
-    License, by the making, using, selling, offering for sale, having
-    made, import, or transfer of either its Contributions or its
-    Contributor Version.
-
-1.12. "Secondary License"
-    means either the GNU General Public License, Version 2.0, the GNU
-    Lesser General Public License, Version 2.1, the GNU Affero General
-    Public License, Version 3.0, or any later versions of those
-    licenses.
-
-1.13. "Source Code Form"
-    means the form of the work preferred for making modifications.
-
-1.14. "You" (or "Your")
-    means an individual or a legal entity exercising rights under this
-    License. For legal entities, "You" includes any entity that
-    controls, is controlled by, or is under common control with You. For
-    purposes of this definition, "control" means (a) the power, direct
-    or indirect, to cause the direction or management of such entity,
-    whether by contract or otherwise, or (b) ownership of more than
-    fifty percent (50%) of the outstanding shares or beneficial
-    ownership of such entity.
-
-2. License Grants and Conditions
---------------------------------
-
-2.1. Grants
-
-Each Contributor hereby grants You a world-wide, royalty-free,
-non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark)
-    Licensable by such Contributor to use, reproduce, make available,
-    modify, display, perform, distribute, and otherwise exploit its
-    Contributions, either on an unmodified basis, with Modifications, or
-    as part of a Larger Work; and
-
-(b) under Patent Claims of such Contributor to make, use, sell, offer
-    for sale, have made, import, and otherwise transfer either its
-    Contributions or its Contributor Version.
-
-2.2. Effective Date
-
-The licenses granted in Section 2.1 with respect to any Contribution
-become effective for each Contribution on the date the Contributor first
-distributes such Contribution.
-
-2.3. Limitations on Grant Scope
-
-The licenses granted in this Section 2 are the only rights granted under
-this License. No additional rights or licenses will be implied from the
-distribution or licensing of Covered Software under this License.
-Notwithstanding Section 2.1(b) above, no patent license is granted by a
-Contributor:
-
-(a) for any code that a Contributor has removed from Covered Software;
-    or
-
-(b) for infringements caused by: (i) Your and any other third party's
-    modifications of Covered Software, or (ii) the combination of its
-    Contributions with other software (except as part of its Contributor
-    Version); or
-
-(c) under Patent Claims infringed by Covered Software in the absence of
-    its Contributions.
-
-This License does not grant any rights in the trademarks, service marks,
-or logos of any Contributor (except as may be necessary to comply with
-the notice requirements in Section 3.4).
-
-2.4. Subsequent Licenses
-
-No Contributor makes additional grants as a result of Your choice to
-distribute the Covered Software under a subsequent version of this
-License (see Section 10.2) or under the terms of a Secondary License (if
-permitted under the terms of Section 3.3).
-
-2.5. Representation
-
-Each Contributor represents that the Contributor believes its
-Contributions are its original creation(s) or it has sufficient rights
-to grant the rights to its Contributions conveyed by this License.
-
-2.6. Fair Use
-
-This License is not intended to limit any rights You have under
-applicable copyright doctrines of fair use, fair dealing, or other
-equivalents.
-
-2.7. Conditions
-
-Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
-in Section 2.1.
-
-3. Responsibilities
--------------------
-
-3.1. Distribution of Source Form
-
-All distribution of Covered Software in Source Code Form, including any
-Modifications that You create or to which You contribute, must be under
-the terms of this License. You must inform recipients that the Source
-Code Form of the Covered Software is governed by the terms of this
-License, and how they can obtain a copy of this License. You may not
-attempt to alter or restrict the recipients' rights in the Source Code
-Form.
-
-3.2. Distribution of Executable Form
-
-If You distribute Covered Software in Executable Form then:
-
-(a) such Covered Software must also be made available in Source Code
-    Form, as described in Section 3.1, and You must inform recipients of
-    the Executable Form how they can obtain a copy of such Source Code
-    Form by reasonable means in a timely manner, at a charge no more
-    than the cost of distribution to the recipient; and
-
-(b) You may distribute such Executable Form under the terms of this
-    License, or sublicense it under different terms, provided that the
-    license for the Executable Form does not attempt to limit or alter
-    the recipients' rights in the Source Code Form under this License.
-
-3.3. Distribution of a Larger Work
-
-You may create and distribute a Larger Work under terms of Your choice,
-provided that You also comply with the requirements of this License for
-the Covered Software. If the Larger Work is a combination of Covered
-Software with a work governed by one or more Secondary Licenses, and the
-Covered Software is not Incompatible With Secondary Licenses, this
-License permits You to additionally distribute such Covered Software
-under the terms of such Secondary License(s), so that the recipient of
-the Larger Work may, at their option, further distribute the Covered
-Software under the terms of either this License or such Secondary
-License(s).
-
-3.4. Notices
-
-You may not remove or alter the substance of any license notices
-(including copyright notices, patent notices, disclaimers of warranty,
-or limitations of liability) contained within the Source Code Form of
-the Covered Software, except that You may alter any license notices to
-the extent required to remedy known factual inaccuracies.
-
-3.5. Application of Additional Terms
-
-You may choose to offer, and to charge a fee for, warranty, support,
-indemnity or liability obligations to one or more recipients of Covered
-Software. However, You may do so only on Your own behalf, and not on
-behalf of any Contributor. You must make it absolutely clear that any
-such warranty, support, indemnity, or liability obligation is offered by
-You alone, and You hereby agree to indemnify every Contributor for any
-liability incurred by such Contributor as a result of warranty, support,
-indemnity or liability terms You offer. You may include additional
-disclaimers of warranty and limitations of liability specific to any
-jurisdiction.
-
-4. Inability to Comply Due to Statute or Regulation
----------------------------------------------------
-
-If it is impossible for You to comply with any of the terms of this
-License with respect to some or all of the Covered Software due to
-statute, judicial order, or regulation then You must: (a) comply with
-the terms of this License to the maximum extent possible; and (b)
-describe the limitations and the code they affect. Such description must
-be placed in a text file included with all distributions of the Covered
-Software under this License. Except to the extent prohibited by statute
-or regulation, such description must be sufficiently detailed for a
-recipient of ordinary skill to be able to understand it.
-
-5. Termination
---------------
-
-5.1. The rights granted under this License will terminate automatically
-if You fail to comply with any of its terms. However, if You become
-compliant, then the rights granted under this License from a particular
-Contributor are reinstated (a) provisionally, unless and until such
-Contributor explicitly and finally terminates Your grants, and (b) on an
-ongoing basis, if such Contributor fails to notify You of the
-non-compliance by some reasonable means prior to 60 days after You have
-come back into compliance. Moreover, Your grants from a particular
-Contributor are reinstated on an ongoing basis if such Contributor
-notifies You of the non-compliance by some reasonable means, this is the
-first time You have received notice of non-compliance with this License
-from such Contributor, and You become compliant prior to 30 days after
-Your receipt of the notice.
-
-5.2. If You initiate litigation against any entity by asserting a patent
-infringement claim (excluding declaratory judgment actions,
-counter-claims, and cross-claims) alleging that a Contributor Version
-directly or indirectly infringes any patent, then the rights granted to
-You by any and all Contributors for the Covered Software under Section
-2.1 of this License shall terminate.
-
-5.3. In the event of termination under Sections 5.1 or 5.2 above, all
-end user license agreements (excluding distributors and resellers) which
-have been validly granted by You or Your distributors under this License
-prior to termination shall survive termination.
-
-************************************************************************
-*                                                                      *
-*  6. Disclaimer of Warranty                                           *
-*  -------------------------                                           *
-*                                                                      *
-*  Covered Software is provided under this License on an "as is"       *
-*  basis, without warranty of any kind, either expressed, implied, or  *
-*  statutory, including, without limitation, warranties that the       *
-*  Covered Software is free of defects, merchantable, fit for a        *
-*  particular purpose or non-infringing. The entire risk as to the     *
-*  quality and performance of the Covered Software is with You.        *
-*  Should any Covered Software prove defective in any respect, You     *
-*  (not any Contributor) assume the cost of any necessary servicing,   *
-*  repair, or correction. This disclaimer of warranty constitutes an   *
-*  essential part of this License. No use of any Covered Software is   *
-*  authorized under this License except under this disclaimer.         *
-*                                                                      *
-************************************************************************
-
-************************************************************************
-*                                                                      *
-*  7. Limitation of Liability                                          *
-*  --------------------------                                          *
-*                                                                      *
-*  Under no circumstances and under no legal theory, whether tort      *
-*  (including negligence), contract, or otherwise, shall any           *
-*  Contributor, or anyone who distributes Covered Software as          *
-*  permitted above, be liable to You for any direct, indirect,         *
-*  special, incidental, or consequential damages of any character      *
-*  including, without limitation, damages for lost profits, loss of    *
-*  goodwill, work stoppage, computer failure or malfunction, or any    *
-*  and all other commercial damages or losses, even if such party      *
-*  shall have been informed of the possibility of such damages. This   *
-*  limitation of liability shall not apply to liability for death or   *
-*  personal injury resulting from such party's negligence to the       *
-*  extent applicable law prohibits such limitation. Some               *
-*  jurisdictions do not allow the exclusion or limitation of           *
-*  incidental or consequential damages, so this exclusion and          *
-*  limitation may not apply to You.                                    *
-*                                                                      *
-************************************************************************
-
-8. Litigation
--------------
-
-Any litigation relating to this License may be brought only in the
-courts of a jurisdiction where the defendant maintains its principal
-place of business and such litigation shall be governed by laws of that
-jurisdiction, without reference to its conflict-of-law provisions.
-Nothing in this Section shall prevent a party's ability to bring
-cross-claims or counter-claims.
-
-9. Miscellaneous
-----------------
-
-This License represents the complete agreement concerning the subject
-matter hereof. If any provision of this License is held to be
-unenforceable, such provision shall be reformed only to the extent
-necessary to make it enforceable. Any law or regulation which provides
-that the language of a contract shall be construed against the drafter
-shall not be used to construe this License against a Contributor.
-
-10. Versions of the License
----------------------------
-
-10.1. New Versions
-
-Mozilla Foundation is the license steward. Except as provided in Section
-10.3, no one other than the license steward has the right to modify or
-publish new versions of this License. Each version will be given a
-distinguishing version number.
-
-10.2. Effect of New Versions
-
-You may distribute the Covered Software under the terms of the version
-of the License under which You originally received the Covered Software,
-or under the terms of any subsequent version published by the license
-steward.
-
-10.3. Modified Versions
-
-If you create software not governed by this License, and you want to
-create a new license for such software, you may create and use a
-modified version of this License if you rename the license and remove
-any references to the name of the license steward (except to note that
-such modified license differs from this License).
-
-10.4. Distributing Source Code Form that is Incompatible With Secondary
-Licenses
-
-If You choose to distribute Source Code Form that is Incompatible With
-Secondary Licenses under the terms of this version of the License, the
-notice described in Exhibit B of this License must be attached.
-
-Exhibit A - Source Code Form License Notice
--------------------------------------------
-
-  This Source Code Form is subject to the terms of the Mozilla Public
-  License, v. 2.0. If a copy of the MPL was not distributed with this
-  file, You can obtain one at http://mozilla.org/MPL/2.0/.
-
-If it is not possible or desirable to put the notice in a particular
-file, then You may include the notice in a location (such as a LICENSE
-file in a relevant directory) where a recipient would be likely to look
-for such a notice.
-
-You may add additional accurate notices of copyright ownership.
-
-Exhibit B - "Incompatible With Secondary Licenses" Notice
----------------------------------------------------------
-
-  This Source Code Form is "Incompatible With Secondary Licenses", as
-  defined by the Mozilla Public License, v. 2.0.
-</screen>
- <para>
-
-<!## end>
-
- </para>
-
-<!## PG>
- <para>
-  <productname>Postgres95</productname> is Copyright &copy; 1994-5
-  by the Regents of the University of California.
- </para>
-
- <para>
-  Permission to use, copy, modify, and distribute this software and
-  its documentation for any purpose, without fee, and without a
-  written agreement is hereby granted, provided that the above
-  copyright notice and this paragraph and the following two paragraphs
-  appear in all copies.
- </para>
-
- <para>
-  IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY
-  PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
-  DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS
-  SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA
-  HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- </para>
-
- <para>
-  THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
-  INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE SOFTWARE
-  PROVIDED HEREUNDER IS ON AN <quote>AS-IS</quote> BASIS, AND THE UNIVERSITY OF
-  CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT,
-  UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
- </pre>
-<!## end>
-</legalnotice>
diff --git a/doc-xc/src/sgml/libpq.sgmlin b/doc-xc/src/sgml/libpq.sgmlin
deleted file mode 100644
index 83ae5ab1e9..0000000000
--- a/doc-xc/src/sgml/libpq.sgmlin
+++ /dev/null
@@ -1,8250 +0,0 @@
-<!-- doc/src/sgml/libpq.sgml -->
-
-<chapter id="libpq">
- <title><application>libpq</application> - C Library</title>
-
- <indexterm zone="libpq">
-  <primary>libpq</primary>
- </indexterm>
-
- <indexterm zone="libpq">
-  <primary>C</primary>
- </indexterm>
-&common;
-
-<!## PG>
- <para>
-  <application>libpq</application> is the <acronym>C</acronym>
-  application programmer's interface to <productname>PostgreSQL</>.
-  <application>libpq</> is a set of library functions that allow
-  client programs to pass queries to the <productname>PostgreSQL</>
-  backend server and to receive the results of these queries.
- </para>
-<!## end>
-<!## XC>
- <para>
-  <application>libpq</application> is the <acronym>C</acronym>
-  application programmer's interface to <productname>Postgres-XC</> inherited from <productname>PostgreSQL</>.
-  <application>libpq</> is a set of library functions that allow
-  client programs to pass queries to the <productname>Postgres-XC</>
-  backend server and to receive the results of these queries.
- </para>
-<!## end>
-<!## XL>
- <para>
-  <application>libpq</application> is the <acronym>C</acronym>
-  application programmer's interface to <productname>Postgres-XL</> inherited from <productname>PostgreSQL</>.
-  <application>libpq</> is a set of library functions that allow
-  client programs to pass queries to the <productname>Postgres-XL</>
-  backend server and to receive the results of these queries.
- </para>
-<!## end>
-
- <para>
-  <application>libpq</> is also the underlying engine for several
-<!## PG>
-  other <productname>PostgreSQL</> application interfaces, including
-<!## end>
-<!## XC>
-  other <productname>Postgres-XC</> application interfaces, including
-<!## end>
-<!## XL>
-  other <productname>Postgres-XL</> application interfaces, including
-<!## end>
-  those written for C++, Perl, Python, Tcl and <application>ECPG</>.
-  So some aspects of <application>libpq</>'s behavior will be
-  important to you if you use one of those packages.  In particular,
-  <xref linkend="libpq-envars">,
-  <xref linkend="libpq-pgpass"> and
-  <xref linkend="libpq-ssl">
-  describe behavior that is visible to the user of any application
-  that uses <application>libpq</>.
- </para>
-
- <para>
-  Some short programs are included at the end of this chapter (<xref linkend="libpq-example">) to show how
-  to write programs that use <application>libpq</application>.  There are also several
-  complete examples of <application>libpq</application> applications in the
-  directory <filename>src/test/examples</filename> in the source code distribution.
- </para>
-
- <para>
-  Client programs that use <application>libpq</application> must
-  include the header file
-  <filename>libpq-fe.h</filename><indexterm><primary>libpq-fe.h</></>
-  and must link with the <application>libpq</application> library.
- </para>
-
- <sect1 id="libpq-connect">
-  <title>Database Connection Control Functions</title>
-&common;
-  <para>
-   The following functions deal with making a connection to a
-<!## PG>
-   <productname>PostgreSQL</productname> backend server.  An
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> backend server.  An
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> backend server.  An
-<!## end>
-   application program can have several backend connections open at
-   one time.  (One reason to do that is to access more than one
-   database.)  Each connection is represented by a
-   <structname>PGconn</><indexterm><primary>PGconn</></> object, which
-   is obtained from the function <function>PQconnectdb</>,
-   <function>PQconnectdbParams</>, or
-   <function>PQsetdbLogin</>.  Note that these functions will always
-   return a non-null object pointer, unless perhaps there is too
-   little memory even to allocate the <structname>PGconn</> object.
-   The <function>PQstatus</> function should be called to check
-   whether a connection was successfully made before queries are sent
-   via the connection object.
-
-   <warning>
-    <para>
-     On Unix, forking a process with open libpq connections can lead to
-     unpredictable results because the parent and child processes share
-     the same sockets and operating system resources.  For this reason,
-     such usage is not recommended, though doing an <function>exec</> from
-     the child process to load a new executable is safe.
-    </para>
-   </warning>
-
-   <note>
-    <para>
-     On Windows, there is a way to improve performance if a single
-     database connection is repeatedly started and shutdown.  Internally,
-     libpq calls <function>WSAStartup()</> and <function>WSACleanup()</> for connection startup
-     and shutdown, respectively.  <function>WSAStartup()</> increments an internal
-     Windows library reference count which is decremented by <function>WSACleanup()</>.
-     When the reference count is just one, calling <function>WSACleanup()</> frees
-     all resources and all DLLs are unloaded.  This is an expensive
-     operation.  To avoid this, an application can manually call
-     <function>WSAStartup()</> so resources will not be freed when the last database
-     connection is closed.
-    </para>
-   </note>
-
-   <variablelist>
-    <varlistentry id="libpq-pqconnectdbparams">
-     <term><function>PQconnectdbParams</function><indexterm><primary>PQconnectdbParams</></></term>
-     <listitem>
-      <para>
-       Makes a new connection to the database server.
-
-<synopsis>
-PGconn *PQconnectdbParams(const char **keywords, const char **values, int expand_dbname);
-</synopsis>
-      </para>
-
-      <para>
-       This function opens a new database connection using the parameters taken
-       from two <symbol>NULL</symbol>-terminated arrays. The first,
-       <literal>keywords</literal>, is defined as an array of strings, each one
-       being a key word. The second, <literal>values</literal>, gives the value
-       for each key word. Unlike <function>PQsetdbLogin</> below, the parameter
-       set can be extended without changing the function signature, so use of
-       this function (or its nonblocking analogs <function>PQconnectStartParams</>
-       and <function>PQconnectPoll</function>) is preferred for new application
-       programming.
-      </para>
-
-      <para>
-       When <literal>expand_dbname</literal> is non-zero, the
-       <parameter>dbname</parameter> key word value is allowed to be recognized
-       as a <parameter>conninfo</parameter> string. See below for details.
-      </para>
-
-      <para>
-       The passed arrays can be empty to use all default parameters, or can
-       contain one or more parameter settings. They should be matched in length.
-       Processing will stop with the last non-<symbol>NULL</symbol> element
-       of the <literal>keywords</literal> array.
-      </para>
-
-      <para>
-       The currently recognized parameter key words are:
-
-       <variablelist>
-        <varlistentry id="libpq-connect-host" xreflabel="host">
-         <term><literal>host</literal></term>
-         <listitem>
-          <para>
-           Name of host to connect to.<indexterm><primary>host name</></>
-           If this begins with a slash, it specifies Unix-domain
-           communication rather than TCP/IP communication; the value is the
-           name of the directory in which the socket file is stored.  The
-           default behavior when <literal>host</literal> is not specified
-           is to connect to a Unix-domain
-           socket<indexterm><primary>Unix domain socket</></> in
-           <filename>/tmp</filename> (or whatever socket directory was specified
-<!## PG>
-           when <productname>PostgreSQL</> was built). On machines without
-<!## end>
-<!## XC>
-           when <productname>Postgres-XC</> was built). On machines without
-<!## end>
-<!## XL>
-           when <productname>Postgres-XL</> was built). On machines without
-<!## end>
-           Unix-domain sockets, the default is to connect to <literal>localhost</>.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-hostaddr" xreflabel="hostaddr">
-         <term><literal>hostaddr</literal></term>
-         <listitem>
-          <para>
-           Numeric IP address of host to connect to.  This should be in the
-           standard IPv4 address format, e.g., <literal>172.28.40.9</>.  If
-           your machine supports IPv6, you can also use those addresses.
-           TCP/IP communication is
-           always used when a nonempty string is specified for this parameter.
-          </para>
-
-          <para>
-           Using <literal>hostaddr</> instead of <literal>host</> allows the
-           application to avoid a host name look-up, which might be important
-           in applications with time constraints. However, a host name is
-           required for Kerberos, GSSAPI, or SSPI authentication
-           methods, as well as for <literal>verify-full</> SSL
-           certificate verification.  The following rules are used:
-           <itemizedlist>
-            <listitem>
-             <para>
-              If <literal>host</> is specified without <literal>hostaddr</>,
-              a host name lookup occurs.
-             </para>
-            </listitem>
-            <listitem>
-             <para>
-              If <literal>hostaddr</> is specified without <literal>host</>,
-              the value for <literal>hostaddr</> gives the server network address.
-              The connection attempt will fail if the authentication
-              method requires a host name.
-             </para>
-            </listitem>
-            <listitem>
-             <para>
-              If both <literal>host</> and <literal>hostaddr</> are specified,
-              the value for <literal>hostaddr</> gives the server network address.
-              The value for <literal>host</> is ignored unless the
-              authentication method requires it, in which case it will be
-              used as the host name.
-             </para>
-            </listitem>
-           </itemizedlist>
-           Note that authentication is likely to fail if <literal>host</>
-           is not the name of the server at network address <literal>hostaddr</>.
-           Also, note that <literal>host</> rather than <literal>hostaddr</>
-           is used to identify the connection in <filename>~/.pgpass</> (see
-           <xref linkend="libpq-pgpass">).
-          </para>
-
-          <para>
-           Without either a host name or host address,
-           <application>libpq</application> will connect using a
-           local Unix-domain socket; or on machines without Unix-domain
-           sockets, it will attempt to connect to <literal>localhost</>.
-          </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-connect-port" xreflabel="port">
-          <term><literal>port</literal></term>
-          <listitem>
-          <para>
-           Port number to connect to at the server host, or socket file
-           name extension for Unix-domain
-           connections.<indexterm><primary>port</></>
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-dbname" xreflabel="dbname">
-         <term><literal>dbname</literal></term>
-         <listitem>
-         <para>
-          The database name.  Defaults to be the same as the user name.
-         </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-user" xreflabel="user">
-         <term><literal>user</literal></term>
-         <listitem>
-         <para>
-<!## PG>
-          <productname>PostgreSQL</productname> user name to connect as.
-<!## end>
-<!## XC>
-          <productname>Postgres-XC</productname> user name to connect as.
-<!## end>
-<!## XL>
-          <productname>Postgres-XL</productname> user name to connect as.
-<!## end>
-          Defaults to be the same as the operating system name of the user
-          running the application.
-         </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-password" xreflabel="password">
-         <term><literal>password</literal></term>
-         <listitem>
-         <para>
-          Password to be used if the server demands password authentication.
-         </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-connect-timeout" xreflabel="connect_timeout">
-         <term><literal>connect_timeout</literal></term>
-         <listitem>
-         <para>
-          Maximum wait for connection, in seconds (write as a decimal integer
-          string). Zero or not specified means wait indefinitely.  It is not
-          recommended to use a timeout of less than 2 seconds.
-         </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-client-encoding" xreflabel="client_encoding">
-         <term><literal>client_encoding</literal></term>
-         <listitem>
-         <para>
-          This sets the <varname>client_encoding</varname>
-          configuration parameter for this connection.  In addition to
-          the values accepted by the corresponding server option, you
-          can use <literal>auto</literal> to determine the right
-          encoding from the current locale in the client
-          (<envar>LC_CTYPE</envar> environment variable on Unix
-          systems).
-         </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-options" xreflabel="options">
-         <term><literal>options</literal></term>
-         <listitem>
-          <para>
-           Adds command-line options to send to the server at run-time.
-           For example, setting this to <literal>-c geqo=off</> sets the
-           session's value of the <varname>geqo</> parameter to
-           <literal>off</>.  For a detailed discussion of the available
-           options, consult <xref linkend="runtime-config">.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-application-name" xreflabel="application_name">
-         <term><literal>application_name</literal></term>
-         <listitem>
-          <para>
-           Specifies a value for the <xref linkend="guc-application-name">
-           configuration parameter.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-fallback-application-name" xreflabel="fallback_application_name">
-         <term><literal>fallback_application_name</literal></term>
-         <listitem>
-          <para>
-           Specifies a fallback value for the <xref
-           linkend="guc-application-name"> configuration parameter.
-           This value will be used if no value has been given for
-           <literal>application_name</> via a connection parameter or the
-           <envar>PGAPPNAME</envar> environment variable.  Specifying
-           a fallback name is useful in generic utility programs that
-           wish to set a default application name but allow it to be
-           overridden by the user.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-keepalives" xreflabel="keepalives">
-         <term><literal>keepalives</literal></term>
-         <listitem>
-          <para>
-           Controls whether client-side TCP keepalives are used. The default
-           value is 1, meaning on, but you can change this to 0, meaning off,
-           if keepalives are not wanted.  This parameter is ignored for
-           connections made via a Unix-domain socket.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-keepalives-idle" xreflabel="keepalives_idle">
-         <term><literal>keepalives_idle</literal></term>
-         <listitem>
-          <para>
-           Controls the number of seconds of inactivity after which TCP should
-           send a keepalive message to the server.  A value of zero uses the
-           system default. This parameter is ignored for connections made via a
-           Unix-domain socket, or if keepalives are disabled. It is only supported
-           on systems where the <symbol>TCP_KEEPIDLE</> or <symbol>TCP_KEEPALIVE</>
-           socket option is available, and on Windows; on other systems, it has no
-           effect.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-keepalives-interval" xreflabel="keepalives_interval">
-         <term><literal>keepalives_interval</literal></term>
-         <listitem>
-          <para>
-           Controls the number of seconds after which a TCP keepalive message
-           that is not acknowledged by the server should be retransmitted.  A
-           value of zero uses the system default. This parameter is ignored for
-           connections made via a Unix-domain socket, or if keepalives are disabled.
-           It is only supported on systems where the <symbol>TCP_KEEPINTVL</>
-           socket option is available, and on Windows; on other systems, it has no
-           effect.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-keepalives-count" xreflabel="keepalives_count">
-         <term><literal>keepalives_count</literal></term>
-         <listitem>
-          <para>
-           Controls the number of TCP keepalives that can be lost before the
-           client's connection to the server is considered dead.  A value of
-           zero uses the system default. This parameter is ignored for
-           connections made via a Unix-domain socket, or if keepalives are disabled.
-           It is only supported on systems where the <symbol>TCP_KEEPINTVL</>
-           socket option is available; on other systems, it has no effect.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-tty" xreflabel="tty">
-         <term><literal>tty</literal></term>
-         <listitem>
-         <para>
-          Ignored (formerly, this specified where to send server debug output).
-         </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-sslmode" xreflabel="sslmode">
-         <term><literal>sslmode</literal></term>
-         <listitem>
-          <para>
-           This option determines whether or with what priority a secure
-           <acronym>SSL</> TCP/IP connection will be negotiated with the
-           server. There are six modes:
-
-           <variablelist>
-            <varlistentry>
-             <term><literal>disable</literal></term>
-             <listitem>
-              <para>
-               only try a non-<acronym>SSL</> connection
-              </para>
-             </listitem>
-            </varlistentry>
-
-            <varlistentry>
-             <term><literal>allow</literal></term>
-             <listitem>
-              <para>
-               first try a non-<acronym>SSL</> connection; if that
-               fails, try an <acronym>SSL</> connection
-              </para>
-             </listitem>
-            </varlistentry>
-
-            <varlistentry>
-             <term><literal>prefer</literal> (default)</term>
-             <listitem>
-              <para>
-               first try an <acronym>SSL</> connection; if that fails,
-               try a non-<acronym>SSL</> connection
-              </para>
-             </listitem>
-            </varlistentry>
-
-            <varlistentry>
-             <term><literal>require</literal></term>
-             <listitem>
-              <para>
-               only try an <acronym>SSL</> connection
-              </para>
-             </listitem>
-            </varlistentry>
-
-            <varlistentry>
-             <term><literal>verify-ca</literal></term>
-             <listitem>
-              <para>
-               only try an <acronym>SSL</> connection, and verify that
-               the server certificate is issued by a trusted
-               certificate authority (<acronym>CA</>)
-              </para>
-             </listitem>
-            </varlistentry>
-
-            <varlistentry>
-             <term><literal>verify-full</literal></term>
-             <listitem>
-              <para>
-               only try an <acronym>SSL</> connection, verify that the
-               server certificate is issued by a
-               trusted <acronym>CA</> and that the server host name
-               matches that in the certificate
-              </para>
-             </listitem>
-            </varlistentry>
-           </variablelist>
-
-           See <xref linkend="libpq-ssl"> for a detailed description of how
-           these options work.
-          </para>
-
-          <para>
-           <literal>sslmode</> is ignored for Unix domain socket
-           communication.
-<!## PG>
-           If <productname>PostgreSQL</> is compiled without SSL support,
-<!## end>
-<!## XC>
-           If <productname>Postgres-XC</> is compiled without SSL support,
-<!## end>
-<!## XL>
-           If <productname>Postgres-XL</> is compiled without SSL support,
-<!## end>
-           using options <literal>require</>, <literal>verify-ca</>, or
-           <literal>verify-full</> will cause an error, while
-           options <literal>allow</> and <literal>prefer</> will be
-           accepted but <application>libpq</> will not actually attempt
-           an <acronym>SSL</>
-           connection.<indexterm><primary>SSL</><secondary
-           sortas="libpq">with libpq</></indexterm>
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-requiressl" xreflabel="requiressl">
-         <term><literal>requiressl</literal></term>
-         <listitem>
-          <para>
-           This option is deprecated in favor of the <literal>sslmode</>
-           setting.
-          </para>
-
-          <para>
-           If set to 1, an <acronym>SSL</acronym> connection to the server
-           is required (this is equivalent to <literal>sslmode</>
-           <literal>require</>).  <application>libpq</> will then refuse
-           to connect if the server does not accept an
-           <acronym>SSL</acronym> connection.  If set to 0 (default),
-           <application>libpq</> will negotiate the connection type with
-           the server (equivalent to <literal>sslmode</>
-           <literal>prefer</>).  This option is only available if
-<!## PG>
-           <productname>PostgreSQL</> is compiled with SSL support.
-<!## end>
-<!## XC>
-           <productname>Postgres-XC</> is compiled with SSL support.
-<!## end>
-<!## XL>
-           <productname>Postgres-XL</> is compiled with SSL support.
-<!## end>
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-sslcert" xreflabel="sslcert">
-         <term><literal>sslcert</literal></term>
-         <listitem>
-          <para>
-           This parameter specifies the file name of the client SSL
-           certificate, replacing the default
-           <filename>~/.postgresql/postgresql.crt</>.
-           This parameter is ignored if an SSL connection is not made.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-sslkey" xreflabel="sslkey">
-         <term><literal>sslkey</literal></term>
-         <listitem>
-          <para>
-           This parameter specifies the location for the secret key used for
-           the client certificate. It can either specify a file name that will
-           be used instead of the default
-           <filename>~/.postgresql/postgresql.key</>, or it can specify a key
-           obtained from an external <quote>engine</> (engines are
-           <productname>OpenSSL</> loadable modules).  An external engine
-           specification should consist of a colon-separated engine name and
-           an engine-specific key identifier.  This parameter is ignored if an
-           SSL connection is not made.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-sslrootcert" xreflabel="sslrootcert">
-         <term><literal>sslrootcert</literal></term>
-         <listitem>
-          <para>
-           This parameter specifies the name of a file containing SSL
-           certificate authority (<acronym>CA</>) certificate(s).
-           If the file exists, the server's certificate will be verified
-           to be signed by one of these authorities.  The default is
-           <filename>~/.postgresql/root.crt</>.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-sslcrl" xreflabel="sslcrl">
-         <term><literal>sslcrl</literal></term>
-         <listitem>
-          <para>
-           This parameter specifies the file name of the SSL certificate
-           revocation list (CRL).  Certificates listed in this file, if it
-           exists, will be rejected while attempting to authenticate the
-           server's certificate.  The default is
-           <filename>~/.postgresql/root.crl</>.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-requirepeer" xreflabel="requirepeer">
-         <term><literal>requirepeer</literal></term>
-         <listitem>
-          <para>
-           This parameter specifies the operating-system user name of the
-           server, for example <literal>requirepeer=postgres</literal>.
-           When making a Unix-domain socket connection, if this
-           parameter is set, the client checks at the beginning of the
-           connection that the server process is running under the specified
-           user name; if it is not, the connection is aborted with an error.
-           This parameter can be used to provide server authentication similar
-           to that available with SSL certificates on TCP/IP connections.
-           (Note that if the Unix-domain socket is in
-           <filename>/tmp</filename> or another publicly writable location,
-           any user could start a server listening there.  Use this parameter
-           to ensure that you are connected to a server run by a trusted user.)
-           This option is only supported on platforms for which the
-           <literal>peer</> authentication method is implemented; see
-           <xref linkend="auth-peer">.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-krbsrvname" xreflabel="krbsrvname">
-         <term><literal>krbsrvname</literal></term>
-         <listitem>
-          <para>
-           Kerberos service name to use when authenticating with Kerberos 5
-           or GSSAPI.
-           This must match the service name specified in the server
-           configuration for Kerberos authentication to succeed. (See also
-           <xref linkend="kerberos-auth"> and <xref linkend="gssapi-auth">.)
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-gsslib" xreflabel="gsslib">
-         <term><literal>gsslib</literal></term>
-         <listitem>
-          <para>
-           GSS library to use for GSSAPI authentication. Only used on Windows.
-           Set to <literal>gssapi</literal> to force libpq to use the GSSAPI
-           library for authentication instead of the default SSPI.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connect-service" xreflabel="service">
-         <term><literal>service</literal></term>
-         <listitem>
-          <para>
-           Service name to use for additional parameters.  It specifies a service
-           name in <filename>pg_service.conf</filename> that holds additional connection parameters.
-           This allows applications to specify only a service name so connection parameters
-           can be centrally maintained. See <xref linkend="libpq-pgservice">.
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-
-       If  any  parameter is unspecified, then the corresponding
-       environment variable (see <xref linkend="libpq-envars">)
-       is checked. If the  environment  variable is not set either,
-       then the indicated built-in defaults are used.
-      </para>
-
-      <para>
-        If <literal>expand_dbname</literal> is non-zero and
-        <parameter>dbname</parameter> contains an <symbol>=</symbol> sign, it
-        is taken as a <parameter>conninfo</parameter> string in exactly the same way as
-        if it had been passed to <function>PQconnectdb</function>(see below). Previously
-        processed key words will be overridden by key words in the
-        <parameter>conninfo</parameter> string.
-      </para>
-
-      <para>
-        In general key words are processed from the beginning of these arrays in index
-        order. The effect of this is that when key words are repeated, the last processed
-        value is retained. Therefore, through careful placement of the
-        <parameter>dbname</parameter> key word, it is possible to determine what may
-        be overridden by a <parameter>conninfo</parameter> string, and what may not.
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqconnectdb">
-     <term><function>PQconnectdb</function><indexterm><primary>PQconnectdb</></></term>
-     <listitem>
-      <para>
-       Makes a new connection to the database server.
-
-<synopsis>
-PGconn *PQconnectdb(const char *conninfo);
-</synopsis>
-      </para>
-
-      <para>
-       This function opens a new database connection using the parameters taken
-       from the string <literal>conninfo</literal>.
-      </para>
-
-      <para>
-       The passed string can be empty to use all default parameters, or it can
-       contain one or more parameter settings separated by whitespace.
-       Each parameter setting is in the form <literal>keyword = value</literal>.
-       Spaces around the equal sign are optional. To write an empty value,
-       or a value containing spaces, surround it with single quotes, e.g.,
-       <literal>keyword = 'a value'</literal>. Single quotes and backslashes
-       within the value must be escaped with a backslash, i.e.,
-       <literal>\'</literal> and <literal>\\</literal>.
-      </para>
-
-      <para>
-       The currently recognized parameter key words are the same as above.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqsetdblogin">
-     <term><function>PQsetdbLogin</function><indexterm><primary>PQsetdbLogin</></></term>
-     <listitem>
-      <para>
-       Makes a new connection to the database server.
-<synopsis>
-PGconn *PQsetdbLogin(const char *pghost,
-                     const char *pgport,
-                     const char *pgoptions,
-                     const char *pgtty,
-                     const char *dbName,
-                     const char *login,
-                     const char *pwd);
-</synopsis>
-       </para>
-
-       <para>
-        This is the predecessor of <function>PQconnectdb</function> with a fixed
-        set of parameters.  It has the same functionality except that the
-        missing parameters will always take on default values.  Write <symbol>NULL</symbol> or an
-        empty string for any one of the fixed parameters that is to be defaulted.
-      </para>
-
-      <para>
-        If the <parameter>dbName</parameter> contains an <symbol>=</symbol> sign, it
-        is taken as a <parameter>conninfo</parameter> string in exactly the same way as
-        if it had been passed to <function>PQconnectdb</function>, and the remaining
-        parameters are then applied as above.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqsetdb">
-     <term><function>PQsetdb</function><indexterm><primary>PQsetdb</></></term>
-     <listitem>
-      <para>
-   Makes a new connection to the database server.
-<synopsis>
-PGconn *PQsetdb(char *pghost,
-                char *pgport,
-                char *pgoptions,
-                char *pgtty,
-                char *dbName);
-</synopsis>
-     </para>
-
-     <para>
-      This is a macro that calls <function>PQsetdbLogin</function> with null pointers
-      for the <parameter>login</> and <parameter>pwd</> parameters.  It is provided
-      for backward compatibility with very old programs.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqconnectstartparams">
-     <term><function>PQconnectStartParams</function><indexterm><primary>PQconnectStartParams</></></term>
-     <term><function>PQconnectStart</function><indexterm><primary>PQconnectStart</></></term>
-     <term><function>PQconnectPoll</function><indexterm><primary>PQconnectPoll</></></term>
-     <listitem>
-      <para>
-       <indexterm><primary>nonblocking connection</primary></indexterm>
-       Make a connection to the database server in a nonblocking manner.
-
-<synopsis>
-PGconn *PQconnectStartParams(const char **keywords,
-                             const char **values,
-                             int expand_dbname);
-
-PGconn *PQconnectStart(const char *conninfo);
-
-PostgresPollingStatusType PQconnectPoll(PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       These three functions are used to open a connection to a database server such
-       that your application's thread of execution is not blocked on remote I/O
-       whilst doing so. The point of this approach is that the waits for I/O to
-       complete can occur in the application's main loop, rather than down inside
-       <function>PQconnectdbParams</> or <function>PQconnectdb</>, and so the
-       application can manage this operation in parallel with other activities.
-      </para>
-
-      <para>
-       With <function>PQconnectStartParams</function>, the database connection is made
-       using the parameters taken from the <literal>keywords</literal> and
-       <literal>values</literal> arrays, and controlled by <literal>expand_dbname</literal>,
-       as described above for <function>PQconnectdbParams</function>.
-      </para>
-
-      <para>
-       With <function>PQconnectStart</function>, the database connection is made
-       using the parameters taken from the string <literal>conninfo</literal> as
-       described above for <function>PQconnectdb</function>.
-      </para>
-
-      <para>
-       Neither <function>PQconnectStartParams</function> nor <function>PQconnectStart</function>
-       nor <function>PQconnectPoll</function> will block, so long as a number of
-       restrictions are met:
-       <itemizedlist>
-        <listitem>
-         <para>
-          The <literal>hostaddr</> and <literal>host</> parameters are used appropriately to ensure that
-          name and reverse name queries are not made. See the documentation of
-          these parameters under <function>PQconnectdbParams</function> above for details.
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-          If you call <function>PQtrace</function>, ensure that the stream object
-          into which you trace will not block.
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-          You ensure that the socket is in the appropriate state
-          before calling <function>PQconnectPoll</function>, as described below.
-         </para>
-        </listitem>
-       </itemizedlist>
-      </para>
-
-      <para>
-       Note: use of <function>PQconnectStartParams</> is analogous to
-       <function>PQconnectStart</> shown below.
-      </para>
-
-      <para>
-       To begin a nonblocking connection request, call <literal>conn = PQconnectStart("<replaceable>connection_info_string</>")</literal>.
-       If <varname>conn</varname> is null, then <application>libpq</> has been unable to allocate a new <structname>PGconn</>
-       structure. Otherwise, a valid <structname>PGconn</> pointer is returned (though not yet
-       representing a valid connection to the database). On return from
-       <function>PQconnectStart</function>, call <literal>status = PQstatus(conn)</literal>. If <varname>status</varname> equals
-       <symbol>CONNECTION_BAD</symbol>, <function>PQconnectStart</function> has failed.
-      </para>
-
-      <para>
-       If <function>PQconnectStart</> succeeds, the next stage is to poll
-       <application>libpq</> so that it can proceed with the connection sequence.
-       Use <function>PQsocket(conn)</function> to obtain the descriptor of the
-       socket underlying the database connection.
-       Loop thus: If <function>PQconnectPoll(conn)</function> last returned
-       <symbol>PGRES_POLLING_READING</symbol>, wait until the socket is ready to
-       read (as indicated by <function>select()</>, <function>poll()</>, or
-       similar system function).
-       Then call <function>PQconnectPoll(conn)</function> again.
-       Conversely, if <function>PQconnectPoll(conn)</function> last returned
-       <symbol>PGRES_POLLING_WRITING</symbol>, wait until the socket is ready
-       to write, then call <function>PQconnectPoll(conn)</function> again.
-       If you have yet to call
-       <function>PQconnectPoll</function>, i.e., just after the call to
-       <function>PQconnectStart</function>, behave as if it last returned
-       <symbol>PGRES_POLLING_WRITING</symbol>.  Continue this loop until
-       <function>PQconnectPoll(conn)</function> returns
-       <symbol>PGRES_POLLING_FAILED</symbol>, indicating the connection procedure
-       has failed, or <symbol>PGRES_POLLING_OK</symbol>, indicating the connection
-       has been successfully made.
-      </para>
-
-      <para>
-       At any time during connection, the status of the connection can be
-       checked by calling <function>PQstatus</>. If this call returns <symbol>CONNECTION_BAD</>, then the
-       connection procedure has failed; if the call returns <function>CONNECTION_OK</>, then the
-       connection is ready.  Both of these states are equally detectable
-       from the return value of <function>PQconnectPoll</>, described above. Other states might also occur
-       during (and only during) an asynchronous connection procedure. These
-       indicate the current stage of the connection procedure and might be useful
-       to provide feedback to the user for example. These statuses are:
-
-       <variablelist>
-        <varlistentry id="libpq-connection-started">
-         <term><symbol>CONNECTION_STARTED</symbol></term>
-         <listitem>
-          <para>
-           Waiting for connection to be made.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connection-made">
-         <term><symbol>CONNECTION_MADE</symbol></term>
-         <listitem>
-          <para>
-           Connection OK; waiting to send.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connection-awaiting-response">
-         <term><symbol>CONNECTION_AWAITING_RESPONSE</symbol></term>
-         <listitem>
-          <para>
-           Waiting for a response from the server.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connection-auth-ok">
-         <term><symbol>CONNECTION_AUTH_OK</symbol></term>
-         <listitem>
-          <para>
-           Received authentication; waiting for backend start-up to finish.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connection-ssl-startup">
-         <term><symbol>CONNECTION_SSL_STARTUP</symbol></term>
-         <listitem>
-          <para>
-           Negotiating SSL encryption.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-connection-setenv">
-         <term><symbol>CONNECTION_SETENV</symbol></term>
-         <listitem>
-          <para>
-           Negotiating environment-driven parameter settings.
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-
-       Note that, although these constants will remain (in order to maintain
-       compatibility), an application should never rely upon these occurring in a
-       particular order, or at all, or on the status always being one of these
-       documented values. An application might do something like this:
-<programlisting>
-switch(PQstatus(conn))
-{
-        case CONNECTION_STARTED:
-            feedback = "Connecting...";
-            break;
-
-        case CONNECTION_MADE:
-            feedback = "Connected to server...";
-            break;
-.
-.
-.
-        default:
-            feedback = "Connecting...";
-}
-</programlisting>
-      </para>
-
-      <para>
-       The <literal>connect_timeout</literal> connection parameter is ignored
-       when using <function>PQconnectPoll</function>; it is the application's
-       responsibility to decide whether an excessive amount of time has elapsed.
-       Otherwise, <function>PQconnectStart</function> followed by a
-       <function>PQconnectPoll</function> loop is equivalent to
-       <function>PQconnectdb</function>.
-      </para>
-
-      <para>
-       Note that if <function>PQconnectStart</function> returns a non-null pointer, you must call
-       <function>PQfinish</function> when you are finished with it, in order to dispose of
-       the structure and any associated memory blocks. This must be done even if
-       the connection attempt fails or is abandoned.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqconndefaults">
-     <term><function>PQconndefaults</function><indexterm><primary>PQconndefaults</></></term>
-     <listitem>
-      <para>
-       Returns the default connection options.
-<synopsis>
-PQconninfoOption *PQconndefaults(void);
-
-typedef struct
-{
-    char   *keyword;   /* The keyword of the option */
-    char   *envvar;    /* Fallback environment variable name */
-    char   *compiled;  /* Fallback compiled in default value */
-    char   *val;       /* Option's current value, or NULL */
-    char   *label;     /* Label for field in connect dialog */
-    char   *dispchar;  /* Indicates how to display this field
-                          in a connect dialog. Values are:
-                          ""        Display entered value as is
-                          "*"       Password field - hide value
-                          "D"       Debug option - don't show by default */
-    int     dispsize;  /* Field size in characters for dialog */
-} PQconninfoOption;
-</synopsis>
-      </para>
-
-      <para>
-       Returns a connection options array.  This can be used to determine
-       all possible <function>PQconnectdb</function> options and their
-       current default values.  The return value points to an array of
-       <structname>PQconninfoOption</structname> structures, which ends
-       with an entry having a null <structfield>keyword</> pointer.  The
-       null pointer is returned if memory could not be allocated. Note that
-       the current default values (<structfield>val</structfield> fields)
-       will depend on environment variables and other context.  Callers
-       must treat the connection options data as read-only.
-      </para>
-
-      <para>
-       After processing the options array, free it by passing it to
-       <function>PQconninfoFree</function>.  If this is not done, a small amount of memory
-       is leaked for each call to <function>PQconndefaults</function>.
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqconninfoparse">
-     <term><function>PQconninfoParse</function><indexterm><primary>PQconninfoParse</></></term>
-     <listitem>
-      <para>
-       Returns parsed connection options from the provided connection string.
-
-<synopsis>
-PQconninfoOption *PQconninfoParse(const char *conninfo, char **errmsg);
-</synopsis>
-      </para>
-
-      <para>
-       Parses a connection string and returns the resulting options as an
-       array; or returns <symbol>NULL</> if there is a problem with the connection
-       string.  This function can be used to extract
-       the <function>PQconnectdb</function> options in the provided
-       connection string.  The return value points to an array of
-       <structname>PQconninfoOption</structname> structures, which ends
-       with an entry having a null <structfield>keyword</> pointer.
-      </para>
-
-      <para>
-       Note that only options explicitly specified in the string will have
-       values set in the result array; no defaults are inserted.
-      </para>
-
-      <para>
-       If <literal>errmsg</> is not <symbol>NULL</>, then <literal>*errmsg</> is set
-       to <symbol>NULL</> on success, else to a <function>malloc</>'d error string explaining
-       the problem.  (It is also possible for <literal>*errmsg</> to be
-       set to <symbol>NULL</> and the function to return <symbol>NULL</>;
-       this indicates an out-of-memory condition.)
-      </para>
-
-      <para>
-       After processing the options array, free it by passing it to
-       <function>PQconninfoFree</function>.  If this is not done, some memory
-       is leaked for each call to <function>PQconninfoParse</function>.
-       Conversely, if an error occurs and <literal>errmsg</> is not <symbol>NULL</>,
-       be sure to free the error string using <function>PQfreemem</>.
-      </para>
-
-   </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqfinish">
-     <term><function>PQfinish</function><indexterm><primary>PQfinish</></></term>
-     <listitem>
-      <para>
-       Closes  the  connection to the server.  Also frees
-       memory used by the <structname>PGconn</structname> object.
-<synopsis>
-void PQfinish(PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       Note that even if the server connection attempt fails (as
-       indicated by <function>PQstatus</function>), the application should call <function>PQfinish</function>
-       to free the memory used by the <structname>PGconn</structname> object.
-       The <structname>PGconn</> pointer must not be used again after
-       <function>PQfinish</function> has been called.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqreset">
-     <term><function>PQreset</function><indexterm><primary>PQreset</></></term>
-     <listitem>
-      <para>
-       Resets the communication channel to the server.
-<synopsis>
-void PQreset(PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       This function will close the connection
-       to the server and attempt to  reestablish  a  new
-       connection to the same server, using all the same
-       parameters previously used.  This might be useful for
-       error recovery if a working connection is lost.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqresetstart">
-     <term><function>PQresetStart</function><indexterm><primary>PQresetStart</></></term>
-     <term><function>PQresetPoll</function><indexterm><primary>PQresetPoll</></></term>
-     <listitem>
-      <para>
-       Reset the communication channel to the server, in a nonblocking manner.
-
-<synopsis>
-int PQresetStart(PGconn *conn);
-
-PostgresPollingStatusType PQresetPoll(PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       These functions will close the connection to the server and attempt to
-       reestablish a new connection to the same server, using all the same
-       parameters previously used. This can be useful for error recovery if a
-       working connection is lost. They differ from <function>PQreset</function> (above) in that they
-       act in a nonblocking manner. These functions suffer from the same
-       restrictions as <function>PQconnectStartParams</>, <function>PQconnectStart</>
-       and <function>PQconnectPoll</>.
-      </para>
-
-      <para>
-       To initiate a connection reset, call
-       <function>PQresetStart</function>. If it returns 0, the reset has
-       failed. If it returns 1, poll the reset using
-       <function>PQresetPoll</function> in exactly the same way as you
-       would create the connection using <function>PQconnectPoll</function>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqpingparams">
-     <term><function>PQpingParams</function><indexterm><primary>PQpingParams</></></term>
-     <listitem>
-      <para>
-       <function>PQpingParams</function> reports the status of the
-       server.  It accepts connection parameters identical to those of
-       <function>PQconnectdbParams</>, described above.  It is not, however,
-       necessary to supply correct user name, password, or database name
-       values to obtain the server status.
-
-<synopsis>
-PGPing PQpingParams(const char **keywords, const char **values, int expand_dbname);
-</synopsis>
-
-       The function returns one of the following values:
-
-       <variablelist>
-        <varlistentry id="libpq-pqpingparams-pqping-ok">
-         <term><literal>PQPING_OK</literal></term>
-         <listitem>
-          <para>
-           The server is running and appears to be accepting connections.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-pqpingparams-pqping-reject">
-         <term><literal>PQPING_REJECT</literal></term>
-         <listitem>
-          <para>
-           The server is running but is in a state that disallows connections
-           (startup, shutdown, or crash recovery).
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-pqpingparams-pqping-no-response">
-         <term><literal>PQPING_NO_RESPONSE</literal></term>
-         <listitem>
-          <para>
-           The server could not be contacted.  This might indicate that the
-           server is not running, or that there is something wrong with the
-           given connection parameters (for example, wrong port number), or
-           that there is a network connectivity problem (for example, a
-           firewall blocking the connection request).
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry id="libpq-pqpingparams-pqping-no-attempt">
-         <term><literal>PQPING_NO_ATTEMPT</literal></term>
-         <listitem>
-          <para>
-           No attempt was made to contact the server, because the supplied
-           parameters were obviously incorrect or there was some client-side
-           problem (for example, out of memory).
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqping">
-     <term><function>PQping</function><indexterm><primary>PQping</></></term>
-     <listitem>
-      <para>
-       <function>PQping</function> reports the status of the
-       server.  It accepts connection parameters identical to those of
-       <function>PQconnectdb</>, described above.  It is not, however,
-       necessary to supply correct user name, password, or database name
-       values to obtain the server status.
-
-<synopsis>
-PGPing PQping(const char *conninfo);
-</synopsis>
-      </para>
-
-      <para>
-       The return values are the same as for <function>PQpingParams</>.
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
- </sect1>
-
- <sect1 id="libpq-status">
-  <title>Connection Status Functions</title>
-&common;
-  <para>
-   These functions can be used to interrogate the status
-   of an existing database connection object.
-  </para>
-
-  <tip>
-   <para>
-    <indexterm><primary>libpq-fe.h</></>
-    <indexterm><primary>libpq-int.h</></>
-    <application>libpq</application> application programmers should be careful to
-    maintain the <structname>PGconn</structname> abstraction.  Use the accessor
-    functions described below to get at the contents of <structname>PGconn</structname>.
-    Reference to internal <structname>PGconn</structname> fields using
-    <filename>libpq-int.h</> is not recommended because they are subject to change
-    in the future.
-   </para>
-  </tip>
-
-  <para>
-   The following functions return parameter values established at connection.
-   These values are fixed for the life of the <structname>PGconn</> object.
-
-   <variablelist>
-    <varlistentry id="libpq-pqdb">
-     <term>
-      <function>PQdb</function>
-      <indexterm>
-       <primary>PQdb</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the database name of the connection.
-<synopsis>
-char *PQdb(const PGconn *conn);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pquser">
-     <term>
-      <function>PQuser</function>
-      <indexterm>
-       <primary>PQuser</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the user name of the connection.
-<synopsis>
-char *PQuser(const PGconn *conn);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqpass">
-     <term>
-      <function>PQpass</function>
-      <indexterm>
-       <primary>PQpass</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the password of the connection.
-<synopsis>
-char *PQpass(const PGconn *conn);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqhost">
-     <term>
-      <function>PQhost</function>
-      <indexterm>
-       <primary>PQhost</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the server host name of the connection.
-<synopsis>
-char *PQhost(const PGconn *conn);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqport">
-     <term>
-      <function>PQport</function>
-      <indexterm>
-       <primary>PQport</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the port of the connection.
-
-<synopsis>
-char *PQport(const PGconn *conn);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqtty">
-     <term>
-      <function>PQtty</function>
-      <indexterm>
-       <primary>PQtty</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the debug <acronym>TTY</acronym> of the connection.
-       (This is obsolete, since the server no longer pays attention
-       to the <acronym>TTY</acronym> setting, but the function remains
-       for backward compatibility.)
-
-<synopsis>
-char *PQtty(const PGconn *conn);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqoptions">
-     <term>
-      <function>PQoptions</function>
-      <indexterm>
-       <primary>PQoptions</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the command-line options passed in the connection request.
-<synopsis>
-char *PQoptions(const PGconn *conn);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   The following functions return status data that can change as operations
-   are executed on the <structname>PGconn</> object.
-
-   <variablelist>
-    <varlistentry id="libpq-pqstatus">
-     <term>
-      <function>PQstatus</function>
-      <indexterm>
-       <primary>PQstatus</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the status of the connection.
-<synopsis>
-ConnStatusType PQstatus(const PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       The status can be one of a number of values.  However, only two of
-       these are seen outside of an asynchronous connection procedure:
-       <literal>CONNECTION_OK</literal> and
-       <literal>CONNECTION_BAD</literal>. A good connection to the database
-       has the status <literal>CONNECTION_OK</literal>.  A failed
-       connection attempt is signaled by status
-       <literal>CONNECTION_BAD</literal>.  Ordinarily, an OK status will
-       remain so until <function>PQfinish</function>, but a communications
-       failure might result in the status changing to
-       <literal>CONNECTION_BAD</literal> prematurely.  In that case the
-       application could try to recover by calling
-       <function>PQreset</function>.
-      </para>
-
-      <para>
-       See the entry for <function>PQconnectStartParams</>, <function>PQconnectStart</>
-       and <function>PQconnectPoll</> with regards to other status codes that
-       might be returned.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqtransactionstatus">
-     <term>
-      <function>PQtransactionStatus</function>
-      <indexterm>
-       <primary>PQtransactionStatus</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the current in-transaction status of the server.
-
-<synopsis>
-PGTransactionStatusType PQtransactionStatus(const PGconn *conn);
-</synopsis>
-
-       The status can be <literal>PQTRANS_IDLE</literal> (currently idle),
-       <literal>PQTRANS_ACTIVE</literal> (a command is in progress),
-       <literal>PQTRANS_INTRANS</literal> (idle, in a valid transaction block),
-       or <literal>PQTRANS_INERROR</literal> (idle, in a failed transaction block).
-       <literal>PQTRANS_UNKNOWN</literal> is reported if the connection is bad.
-       <literal>PQTRANS_ACTIVE</literal> is reported only when a query
-       has been sent to the server and not yet completed.
-      </para>
-
-<!## PG>
-      <caution>
-       <para>
-        <function>PQtransactionStatus</> will give incorrect results when using
-        a <productname>PostgreSQL</> 7.3 server that has the parameter <literal>autocommit</>
-        set to off.  The server-side autocommit feature has been
-        deprecated and does not exist in later server versions.
-       </para>
-      </caution>
-<!## end>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqparameterstatus">
-     <term>
-      <function>PQparameterStatus</function>
-      <indexterm>
-       <primary>PQparameterStatus</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Looks up a current parameter setting of the server.
-
-<synopsis>
-const char *PQparameterStatus(const PGconn *conn, const char *paramName);
-</synopsis>
-
-       Certain parameter values are reported by the server automatically at
-       connection startup or whenever their values change.
-       <function>PQparameterStatus</> can be used to interrogate these settings.
-       It returns the current value of a parameter if known, or <symbol>NULL</symbol>
-       if the parameter is not known.
-      </para>
-
-      <para>
-       Parameters reported as of the current release include
-       <varname>server_version</>,
-       <varname>server_encoding</>,
-       <varname>client_encoding</>,
-       <varname>application_name</>,
-       <varname>is_superuser</>,
-       <varname>session_authorization</>,
-       <varname>DateStyle</>,
-       <varname>IntervalStyle</>,
-       <varname>TimeZone</>,
-       <varname>integer_datetimes</>, and
-       <varname>standard_conforming_strings</>.
-       (<varname>server_encoding</>, <varname>TimeZone</>, and
-       <varname>integer_datetimes</> were not reported by releases before 8.0;
-       <varname>standard_conforming_strings</> was not reported by releases
-       before 8.1;
-       <varname>IntervalStyle</> was not reported by releases before 8.4;
-       <varname>application_name</> was not reported by releases before 9.0.)
-       Note that
-       <varname>server_version</>,
-       <varname>server_encoding</> and
-       <varname>integer_datetimes</>
-       cannot change after startup.
-      </para>
-
-      <para>
-       Pre-3.0-protocol servers do not report parameter settings, but
-       <application>libpq</> includes logic to obtain values for
-       <varname>server_version</> and <varname>client_encoding</> anyway.
-       Applications are encouraged to use <function>PQparameterStatus</>
-       rather than <foreignphrase>ad hoc</> code to determine these values.
-       (Beware however that on a pre-3.0 connection, changing
-       <varname>client_encoding</> via <command>SET</> after connection
-       startup will not be reflected by <function>PQparameterStatus</>.)
-       For <varname>server_version</>, see also
-       <function>PQserverVersion</>, which returns the information in a
-       numeric form that is much easier to compare against.
-      </para>
-
-      <para>
-       If no value for <varname>standard_conforming_strings</> is reported,
-       applications can assume it is <literal>off</>, that is, backslashes
-       are treated as escapes in string literals.  Also, the presence of
-       this parameter can be taken as an indication that the escape string
-       syntax (<literal>E'...'</>) is accepted.
-      </para>
-
-      <para>
-       Although the returned pointer is declared <literal>const</>, it in fact
-       points to mutable storage associated with the <literal>PGconn</> structure.
-       It is unwise to assume the pointer will remain valid across queries.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqprotocolversion">
-     <term>
-      <function>PQprotocolVersion</function>
-      <indexterm>
-       <primary>PQprotocolVersion</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Interrogates the frontend/backend protocol being used.
-<synopsis>
-int PQprotocolVersion(const PGconn *conn);
-</synopsis>
-       Applications might wish to use this function to determine whether certain
-       features are supported.  Currently, the possible values are 2 (2.0
-       protocol), 3 (3.0 protocol), or zero (connection bad).  The
-       protocol version will
-       not change after connection startup is complete, but it could
-<!## PG>
-       theoretically change during a connection reset.  The 3.0 protocol
-       will normally be used when communicating with
-       <productname>PostgreSQL</> 7.4 or later servers; pre-7.4 servers
-       support only protocol 2.0.  (Protocol 1.0 is obsolete and not
-       supported by <application>libpq</application>.)
-<!## end>
-<!## XC>
-       theoretically change during a connection reset.
-<!## end>
-<!## XL>
-       theoretically change during a connection reset.
-<!## end>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqserverversion">
-     <term>
-      <function>PQserverVersion</function>
-      <indexterm>
-       <primary>PQserverVersion</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns an integer representing the backend version.
-<synopsis>
-int PQserverVersion(const PGconn *conn);
-</synopsis>
-       Applications might use this function to determine the version of the database
-       server they are connected to. The number is formed by converting
-       the major, minor, and revision numbers into two-decimal-digit
-       numbers and appending them together. For example, version 8.1.5
-       will be returned as 80105, and version 8.2 will be returned as
-       80200 (leading zeroes are not shown).  Zero is returned if the
-       connection is bad.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqerrormessage">
-     <term>
-      <function>PQerrorMessage</function>
-      <indexterm>
-       <primary>PQerrorMessage</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       <indexterm><primary>error message</></> Returns the error message
-       most recently generated by an operation on the connection.
-
-<synopsis>
-char *PQerrorMessage(const PGconn *conn);
-</synopsis>
-
-      </para>
-
-      <para>
-       Nearly all <application>libpq</> functions will set a message for
-       <function>PQerrorMessage</function> if they fail.  Note that by
-       <application>libpq</application> convention, a nonempty
-       <function>PQerrorMessage</function> result can consist of multiple lines,
-       and will include a trailing newline. The caller should not free
-       the result directly. It will be freed when the associated
-       <structname>PGconn</> handle is passed to
-       <function>PQfinish</function>.  The result string should not be
-       expected to remain the same across operations on the
-       <literal>PGconn</> structure.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqsocket">
-     <term><function>PQsocket</function><indexterm><primary>PQsocket</></></term>
-     <listitem>
-      <para>
-       Obtains the file descriptor number of the connection socket to
-       the server.  A valid descriptor will be greater than or equal
-       to 0; a result of -1 indicates that no server connection is
-       currently open.  (This will not change during normal operation,
-       but could change during connection setup or reset.)
-
-<synopsis>
-int PQsocket(const PGconn *conn);
-</synopsis>
-
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqbackendpid">
-     <term><function>PQbackendPID</function><indexterm><primary>PQbackendPID</></></term>
-     <listitem>
-      <para>
-       Returns the process <acronym>ID</acronym> (PID)<indexterm>
-        <primary>PID</>
-        <secondary>determining PID of server process</>
-        <tertiary>in libpq</>
-       </indexterm>
-       of the backend process handling this connection.
-
-<synopsis>
-int PQbackendPID(const PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       The backend <acronym>PID</acronym> is useful for debugging
-       purposes and for comparison to <command>NOTIFY</command>
-       messages (which include the <acronym>PID</acronym> of the
-       notifying backend process).  Note that the
-       <acronym>PID</acronym> belongs to a process executing on the
-       database server host, not the local host!
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqconnectionneedspassword">
-     <term><function>PQconnectionNeedsPassword</function><indexterm><primary>PQconnectionNeedsPassword</></></term>
-     <listitem>
-      <para>
-       Returns true (1) if the connection authentication method
-       required a password, but none was available.
-       Returns false (0) if not.
-
-<synopsis>
-int PQconnectionNeedsPassword(const PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       This function can be applied after a failed connection attempt
-       to decide whether to prompt the user for a password.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqconnectionusedpassword">
-     <term><function>PQconnectionUsedPassword</function><indexterm><primary>PQconnectionUsedPassword</></></term>
-     <listitem>
-      <para>
-       Returns true (1) if the connection authentication method
-       used a password. Returns false (0) if not.
-
-<synopsis>
-int PQconnectionUsedPassword(const PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       This function can be applied after either a failed or successful
-       connection attempt to detect whether the server demanded a password.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqgetssl">
-     <term><function>PQgetssl</function><indexterm><primary>PQgetssl</></></term>
-     <listitem>
-      <para>
-       <indexterm><primary>SSL</><secondary sortas="libpq">in libpq</secondary></indexterm>
-       Returns the SSL structure used in the connection, or null
-       if SSL is not in use.
-
-<synopsis>
-SSL *PQgetssl(const PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       This structure can be used to verify encryption levels, check server
-       certificates, and more. Refer to the <productname>OpenSSL</>
-       documentation for information about this structure.
-      </para>
-
-      <para>
-       You must define <symbol>USE_SSL</symbol> in order to get the
-       correct prototype for this function. Doing so will also
-       automatically include <filename>ssl.h</filename> from
-       <productname>OpenSSL</productname>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-
- </sect1>
-
- <sect1 id="libpq-exec">
-  <title>Command Execution Functions</title>
-&common;
-  <para>
-   Once a connection to a database server has been successfully
-   established, the functions described here are used to perform
-   SQL queries and commands.
-  </para>
-
-  <sect2 id="libpq-exec-main">
-   <title>Main Functions</title>
-&common;
-   <para>
-    <variablelist>
-     <varlistentry id="libpq-pqexec">
-      <term>
-       <function>PQexec</function>
-       <indexterm>
-        <primary>PQexec</primary>
-       </indexterm>
-      </term>
-
-      <listitem>
-       <para>
-        Submits a command to the server and waits for the result.
-
-<synopsis>
-PGresult *PQexec(PGconn *conn, const char *command);
-</synopsis>
-       </para>
-
-       <para>
-        Returns a <structname>PGresult</structname> pointer or possibly a null
-        pointer.  A non-null pointer will generally be returned except in
-        out-of-memory conditions or serious errors such as inability to send
-        the command to the server.  If a null pointer is returned, it should
-        be treated like a <symbol>PGRES_FATAL_ERROR</symbol> result.  Use
-        <function>PQerrorMessage</function> to get more information about such
-        errors.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    The command string can include multiple SQL commands
-    (separated by semicolons).  Multiple queries sent in a single
-    <function>PQexec</> call are processed in a single transaction, unless
-    there are explicit <command>BEGIN</command>/<command>COMMIT</command>
-    commands included in the query string to divide it into multiple
-    transactions.  Note however that the returned
-    <structname>PGresult</structname> structure describes only the result
-    of the last command executed from the string.  Should one of the
-    commands fail, processing of the string stops with it and the returned
-    <structname>PGresult</structname> describes the error condition.
-   </para>
-
-   <para>
-    <variablelist>
-     <varlistentry id="libpq-pqexecparams">
-      <term>
-       <function>PQexecParams</function>
-       <indexterm>
-        <primary>PQexecParams</primary>
-       </indexterm>
-      </term>
-
-      <listitem>
-       <para>
-        Submits a command to the server and waits for the result,
-        with the ability to pass parameters separately from the SQL
-        command text.
-
-<synopsis>
-PGresult *PQexecParams(PGconn *conn,
-                       const char *command,
-                       int nParams,
-                       const Oid *paramTypes,
-                       const char * const *paramValues,
-                       const int *paramLengths,
-                       const int *paramFormats,
-                       int resultFormat);
-</synopsis>
-       </para>
-
-       <para>
-        <function>PQexecParams</> is like <function>PQexec</>, but offers additional
-        functionality: parameter values can be specified separately from the command
-        string proper, and query results can be requested in either text or binary
-        format.  <function>PQexecParams</> is supported only in protocol 3.0 and later
-        connections; it will fail when using protocol 2.0.
-       </para>
-
-       <para>
-        The function arguments are:
-
-        <variablelist>
-         <varlistentry>
-          <term><parameter>conn</parameter></term>
-
-          <listitem>
-           <para>
-            The connection object to send the command through.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><parameter>command</parameter></term>
-          <listitem>
-           <para>
-            The SQL command string to be executed. If parameters are used,
-            they are referred to in the command string as <literal>$1</>,
-            <literal>$2</>, etc.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><parameter>nParams</parameter></term>
-          <listitem>
-           <para>
-            The number of parameters supplied; it is the length of the arrays
-            <parameter>paramTypes[]</>, <parameter>paramValues[]</>,
-            <parameter>paramLengths[]</>, and <parameter>paramFormats[]</>. (The
-            array pointers can be <symbol>NULL</symbol> when <parameter>nParams</>
-            is zero.)
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><parameter>paramTypes[]</parameter></term>
-          <listitem>
-           <para>
-            Specifies, by OID, the data types to be assigned to the
-            parameter symbols.  If <parameter>paramTypes</> is
-            <symbol>NULL</symbol>, or any particular element in the array
-            is zero, the server infers a data type for the parameter symbol
-            in the same way it would do for an untyped literal string.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><parameter>paramValues[]</parameter></term>
-          <listitem>
-           <para>
-            Specifies the actual values of the parameters.  A null pointer
-            in this array means the corresponding parameter is null;
-            otherwise the pointer points to a zero-terminated text string
-            (for text format) or binary data in the format expected by the
-            server (for binary format).
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><parameter>paramLengths[]</parameter></term>
-          <listitem>
-           <para>
-            Specifies the actual data lengths of binary-format parameters.
-            It is ignored for null parameters and text-format parameters.
-            The array pointer can be null when there are no binary parameters.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><parameter>paramFormats[]</parameter></term>
-          <listitem>
-           <para>
-            Specifies whether parameters are text (put a zero in the
-            array entry for the corresponding parameter) or binary (put
-            a one in the array entry for the corresponding parameter).
-            If the array pointer is null then all parameters are presumed
-            to be text strings.
-           </para>
-           <para>
-            Values passed in binary format require knowledge of
-            the internal representation expected by the backend.
-            For example, integers must be passed in network byte
-            order.  Passing <type>numeric</> values requires
-            knowledge of the server storage format, as implemented
-            in
-            <filename>src/backend/utils/adt/numeric.c::numeric_send()</> and
-            <filename>src/backend/utils/adt/numeric.c::numeric_recv()</>.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><parameter>resultFormat</parameter></term>
-          <listitem>
-           <para>
-            Specify zero to obtain results in text format, or one to obtain
-            results in binary format.  (There is not currently a provision
-            to obtain different result columns in different formats,
-            although that is possible in the underlying protocol.)
-           </para>
-          </listitem>
-         </varlistentry>
-        </variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    The primary advantage of <function>PQexecParams</> over
-    <function>PQexec</> is that parameter values can be separated from the
-    command string, thus avoiding the need for tedious and error-prone
-    quoting and escaping.
-   </para>
-
-   <para>
-    Unlike <function>PQexec</>, <function>PQexecParams</> allows at most
-    one SQL command in the given string.  (There can be semicolons in it,
-    but not more than one nonempty command.)  This is a limitation of the
-    underlying protocol, but has some usefulness as an extra defense against
-    SQL-injection attacks.
-   </para>
-
-   <tip>
-    <para>
-     Specifying parameter types via OIDs is tedious, particularly if you prefer
-     not to hard-wire particular OID values into your program.  However, you can
-     avoid doing so even in cases where the server by itself cannot determine the
-     type of the parameter, or chooses a different type than you want.  In the
-     SQL command text, attach an explicit cast to the parameter symbol to show what
-     data type you will send.  For example:
-<programlisting>
-SELECT * FROM mytable WHERE x = $1::bigint;
-</programlisting>
-     This forces parameter <literal>$1</> to be treated as <type>bigint</>, whereas
-     by default it would be assigned the same type as <literal>x</>.  Forcing the
-     parameter type decision, either this way or by specifying a numeric type OID,
-     is strongly recommended when sending parameter values in binary format, because
-     binary format has less redundancy than text format and so there is less chance
-     that the server will detect a type mismatch mistake for you.
-    </para>
-   </tip>
-
-   <para>
-    <variablelist>
-     <varlistentry id="libpq-pqprepare">
-      <term><function>PQprepare</function>
-       <indexterm>
-        <primary>PQprepare</primary>
-       </indexterm>
-      </term>
-
-      <listitem>
-       <para>
-        Submits a request to create a prepared statement with the
-        given parameters, and waits for completion.
-<synopsis>
-PGresult *PQprepare(PGconn *conn,
-                    const char *stmtName,
-                    const char *query,
-                    int nParams,
-                    const Oid *paramTypes);
-</synopsis>
-       </para>
-
-       <para>
-        <function>PQprepare</> creates a prepared statement for later
-        execution with <function>PQexecPrepared</>.  This feature allows
-        commands that will be used repeatedly to be parsed and planned just
-        once, rather than each time they are executed.
-        <function>PQprepare</> is supported only in protocol 3.0 and later
-        connections; it will fail when using protocol 2.0.
-       </para>
-
-       <para>
-        The function creates a prepared statement named
-        <parameter>stmtName</> from the <parameter>query</> string, which
-        must contain a single SQL command.  <parameter>stmtName</> can be
-        <literal>""</> to create an unnamed statement, in which case any
-        pre-existing unnamed statement is automatically replaced; otherwise
-        it is an error if the statement name is already defined in the
-        current session.  If any parameters are used, they are referred
-        to in the query as <literal>$1</>, <literal>$2</>, etc.
-        <parameter>nParams</> is the number of parameters for which types
-        are pre-specified in the array <parameter>paramTypes[]</>.  (The
-        array pointer can be <symbol>NULL</symbol> when
-        <parameter>nParams</> is zero.) <parameter>paramTypes[]</>
-        specifies, by OID, the data types to be assigned to the parameter
-        symbols.  If <parameter>paramTypes</> is <symbol>NULL</symbol>,
-        or any particular element in the array is zero, the server assigns
-        a data type to the parameter symbol in the same way it would do
-        for an untyped literal string.  Also, the query can use parameter
-        symbols with numbers higher than <parameter>nParams</>; data types
-        will be inferred for these symbols as well.  (See
-        <function>PQdescribePrepared</function> for a means to find out
-        what data types were inferred.)
-       </para>
-
-       <para>
-        As with <function>PQexec</>, the result is normally a
-        <structname>PGresult</structname> object whose contents indicate
-        server-side success or failure.  A null result indicates
-        out-of-memory or inability to send the command at all.  Use
-        <function>PQerrorMessage</function> to get more information about
-        such errors.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    Prepared statements for use with <function>PQexecPrepared</> can also
-    be created by executing SQL <xref linkend="sql-prepare">
-    statements.  Also, although there is no <application>libpq</>
-    function for deleting a prepared statement, the SQL <xref
-    linkend="sql-deallocate"> statement
-    can be used for that purpose.
-   </para>
-
-   <para>
-    <variablelist>
-     <varlistentry id="libpq-pqexecprepared">
-      <term>
-       <function>PQexecPrepared</function>
-       <indexterm>
-        <primary>PQexecPrepared</primary>
-       </indexterm>
-      </term>
-
-      <listitem>
-       <para>
-        Sends a request to execute a prepared statement with given
-        parameters, and waits for the result.
-<synopsis>
-PGresult *PQexecPrepared(PGconn *conn,
-                         const char *stmtName,
-                         int nParams,
-                         const char * const *paramValues,
-                         const int *paramLengths,
-                         const int *paramFormats,
-                         int resultFormat);
-</synopsis>
-       </para>
-
-       <para>
-        <function>PQexecPrepared</> is like <function>PQexecParams</>,
-        but the command to be executed is specified by naming a
-        previously-prepared statement, instead of giving a query string.
-        This feature allows commands that will be used repeatedly to be
-        parsed and planned just once, rather than each time they are
-        executed.  The statement must have been prepared previously in
-        the current session.  <function>PQexecPrepared</> is supported
-        only in protocol 3.0 and later connections; it will fail when
-        using protocol 2.0.
-       </para>
-
-       <para>
-        The parameters are identical to <function>PQexecParams</>, except that the
-        name of a prepared statement is given instead of a query string, and the
-        <parameter>paramTypes[]</> parameter is not present (it is not needed since
-        the prepared statement's parameter types were determined when it was created).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="libpq-pqdescribeprepared">
-      <term>
-       <function>PQdescribePrepared</function>
-       <indexterm>
-        <primary>PQdescribePrepared</primary>
-       </indexterm>
-      </term>
-
-      <listitem>
-       <para>
-        Submits a request to obtain information about the specified
-        prepared statement, and waits for completion.
-<synopsis>
-PGresult *PQdescribePrepared(PGconn *conn, const char *stmtName);
-</synopsis>
-       </para>
-
-       <para>
-        <function>PQdescribePrepared</> allows an application to obtain
-        information about a previously prepared statement.
-        <function>PQdescribePrepared</> is supported only in protocol 3.0
-        and later connections; it will fail when using protocol 2.0.
-       </para>
-
-       <para>
-        <parameter>stmtName</> can be <literal>""</> or <symbol>NULL</> to reference
-        the unnamed statement, otherwise it must be the name of an existing
-        prepared statement.  On success, a <structname>PGresult</> with
-        status <literal>PGRES_COMMAND_OK</literal> is returned.  The
-        functions <function>PQnparams</function> and
-        <function>PQparamtype</function> can be applied to this
-        <structname>PGresult</> to obtain information about the parameters
-        of the prepared statement, and the functions
-        <function>PQnfields</function>, <function>PQfname</function>,
-        <function>PQftype</function>, etc provide information about the
-        result columns (if any) of the statement.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="libpq-pqdescribeportal">
-      <term>
-       <function>PQdescribePortal</function>
-       <indexterm>
-        <primary>PQdescribePortal</primary>
-       </indexterm>
-      </term>
-
-      <listitem>
-       <para>
-        Submits a request to obtain information about the specified
-        portal, and waits for completion.
-<synopsis>
-PGresult *PQdescribePortal(PGconn *conn, const char *portalName);
-</synopsis>
-       </para>
-
-       <para>
-        <function>PQdescribePortal</> allows an application to obtain
-        information about a previously created portal.
-        (<application>libpq</> does not provide any direct access to
-        portals, but you can use this function to inspect the properties
-        of a cursor created with a <command>DECLARE CURSOR</> SQL command.)
-        <function>PQdescribePortal</> is supported only in protocol 3.0
-        and later connections; it will fail when using protocol 2.0.
-       </para>
-
-       <para>
-        <parameter>portalName</> can be <literal>""</> or <symbol>NULL</> to reference
-        the unnamed portal, otherwise it must be the name of an existing
-        portal.  On success, a <structname>PGresult</> with status
-        <literal>PGRES_COMMAND_OK</literal> is returned.  The functions
-        <function>PQnfields</function>, <function>PQfname</function>,
-        <function>PQftype</function>, etc can be applied to the
-        <structname>PGresult</> to obtain information about the result
-        columns (if any) of the portal.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    The <structname>PGresult</structname><indexterm><primary>PGresult</></>
-    structure encapsulates the result returned by the server.
-    <application>libpq</application> application programmers should be
-    careful to maintain the <structname>PGresult</structname> abstraction.
-    Use the accessor functions below to get at the contents of
-    <structname>PGresult</structname>.  Avoid directly referencing the
-    fields of the <structname>PGresult</structname> structure because they
-    are subject to change in the future.
-
-    <variablelist>
-     <varlistentry id="libpq-pqresultstatus">
-      <term>
-       <function>PQresultStatus</function>
-       <indexterm>
-        <primary>PQresultStatus</primary>
-       </indexterm>
-      </term>
-
-      <listitem>
-       <para>
-        Returns the result status of the command.
-<synopsis>
-ExecStatusType PQresultStatus(const PGresult *res);
-</synopsis>
-       </para>
-
-       <para>
-        <function>PQresultStatus</function> can return one of the following values:
-
-        <variablelist>
-         <varlistentry id="libpq-pgres-empty-query">
-          <term><literal>PGRES_EMPTY_QUERY</literal></term>
-          <listitem>
-           <para>
-            The string sent to the server was empty.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pgres-command-ok">
-          <term><literal>PGRES_COMMAND_OK</literal></term>
-          <listitem>
-           <para>
-            Successful completion of a command returning no data.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pgres-tuples-ok">
-          <term><literal>PGRES_TUPLES_OK</literal></term>
-          <listitem>
-           <para>
-            Successful completion of a command returning data (such as
-            a <command>SELECT</> or <command>SHOW</>).
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pgres-copy-out">
-          <term><literal>PGRES_COPY_OUT</literal></term>
-          <listitem>
-           <para>
-            Copy Out (from server) data transfer started.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pgres-copy-in">
-          <term><literal>PGRES_COPY_IN</literal></term>
-          <listitem>
-           <para>
-            Copy In (to server) data transfer started.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pgres-bad-response">
-          <term><literal>PGRES_BAD_RESPONSE</literal></term>
-          <listitem>
-           <para>
-            The server's response was not understood.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pgres-nonfatal-error">
-          <term><literal>PGRES_NONFATAL_ERROR</literal></term>
-          <listitem>
-           <para>
-            A nonfatal error (a notice or warning) occurred.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pgres-fatal-error">
-          <term><literal>PGRES_FATAL_ERROR</literal></term>
-          <listitem>
-           <para>
-            A fatal error occurred.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pgres-copy-both">
-          <term><literal>PGRES_COPY_BOTH</literal></term>
-          <listitem>
-           <para>
-            Copy In/Out (to and from server) data transfer started.  This is
-            currently used only for streaming replication.
-           </para>
-          </listitem>
-         </varlistentry>
-        </variablelist>
-
-        If the result status is <literal>PGRES_TUPLES_OK</literal>, then
-        the functions described below can be used to retrieve the rows
-        returned by the query.  Note that a <command>SELECT</command>
-        command that happens to retrieve zero rows still shows
-        <literal>PGRES_TUPLES_OK</literal>.
-        <literal>PGRES_COMMAND_OK</literal> is for commands that can never
-        return rows (<command>INSERT</command>, <command>UPDATE</command>,
-        etc.). A response of <literal>PGRES_EMPTY_QUERY</literal> might
-        indicate a bug in the client software.
-       </para>
-
-       <para>
-        A result of status <symbol>PGRES_NONFATAL_ERROR</symbol> will
-        never be returned directly by <function>PQexec</function> or other
-        query execution functions; results of this kind are instead passed
-        to the notice processor (see <xref
-        linkend="libpq-notice-processing">).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="libpq-pqresstatus">
-      <term>
-       <function>PQresStatus</function>
-       <indexterm>
-        <primary>PQresStatus</primary>
-       </indexterm>
-      </term>
-
-      <listitem>
-       <para>
-        Converts the enumerated type returned by
-        <function>PQresultStatus</> into a string constant describing the
-        status code. The caller should not free the result.
-
-<synopsis>
-char *PQresStatus(ExecStatusType status);
-</synopsis>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="libpq-pqresulterrormessage">
-      <term>
-       <function>PQresultErrorMessage</function>
-       <indexterm>
-        <primary>PQresultErrorMessage</primary>
-       </indexterm>
-      </term>
-
-      <listitem>
-       <para>
-        Returns the error message associated with the command, or an empty string
-        if there was no error.
-<synopsis>
-char *PQresultErrorMessage(const PGresult *res);
-</synopsis>
-        If there was an error, the returned string will include a trailing
-        newline.  The caller should not free the result directly. It will
-        be freed when the associated <structname>PGresult</> handle is
-        passed to <function>PQclear</function>.
-       </para>
-
-       <para>
-        Immediately following a <function>PQexec</function> or
-        <function>PQgetResult</function> call,
-        <function>PQerrorMessage</function> (on the connection) will return
-        the same string as <function>PQresultErrorMessage</function> (on
-        the result).  However, a <structname>PGresult</structname> will
-        retain its error message until destroyed, whereas the connection's
-        error message will change when subsequent operations are done.
-        Use <function>PQresultErrorMessage</function> when you want to
-        know the status associated with a particular
-        <structname>PGresult</structname>; use
-        <function>PQerrorMessage</function> when you want to know the
-        status from the latest operation on the connection.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="libpq-pqresulterrorfield">
-      <term><function>PQresultErrorField</function><indexterm><primary>PQresultErrorField</></></term>
-      <listitem>
-       <para>
-        Returns an individual field of an error report.
-<synopsis>
-char *PQresultErrorField(const PGresult *res, int fieldcode);
-</synopsis>
-        <parameter>fieldcode</> is an error field identifier; see the symbols
-        listed below.  <symbol>NULL</symbol> is returned if the
-        <structname>PGresult</structname> is not an error or warning result,
-        or does not include the specified field.  Field values will normally
-        not include a trailing newline. The caller should not free the
-        result directly. It will be freed when the
-        associated <structname>PGresult</> handle is passed to
-        <function>PQclear</function>.
-       </para>
-
-       <para>
-        The following field codes are available:
-        <variablelist>
-         <varlistentry id="libpq-pg-diag-severity">
-          <term><symbol>PG_DIAG_SEVERITY</></term>
-          <listitem>
-           <para>
-            The severity; the field contents are <literal>ERROR</>,
-            <literal>FATAL</>, or <literal>PANIC</> (in an error message),
-            or <literal>WARNING</>, <literal>NOTICE</>, <literal>DEBUG</>,
-            <literal>INFO</>, or <literal>LOG</> (in a notice message), or
-            a localized translation of one of these.  Always present.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-sqlstate">
-          <indexterm>
-           <primary>error codes</primary>
-           <secondary>libpq</secondary>
-          </indexterm>
-          <term><symbol>PG_DIAG_SQLSTATE</></term>
-          <listitem>
-           <para>
-            The SQLSTATE code for the error. The SQLSTATE code identifies
-            the type of error that has occurred; it can be used by
-            front-end applications to perform specific operations (such
-            as error handling) in response to a particular database error.
-            For a list of the possible SQLSTATE codes, see <xref
-            linkend="errcodes-appendix">. This field is not localizable,
-            and is always present.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-message-primary">
-          <term><symbol>PG_DIAG_MESSAGE_PRIMARY</></term>
-          <listitem>
-           <para>
-            The primary human-readable error message (typically one line).
-            Always present.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-message-detail">
-          <term><symbol>PG_DIAG_MESSAGE_DETAIL</></term>
-          <listitem>
-           <para>
-            Detail: an optional secondary error message carrying more
-            detail about the problem.  Might run to multiple lines.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-message-hint">
-          <term><symbol>PG_DIAG_MESSAGE_HINT</></term>
-          <listitem>
-           <para>
-            Hint: an optional suggestion what to do about the problem.
-            This is intended to differ from detail in that it offers advice
-            (potentially inappropriate) rather than hard facts.  Might
-            run to multiple lines.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-statement-position">
-          <term><symbol>PG_DIAG_STATEMENT_POSITION</></term>
-          <listitem>
-           <para>
-            A string containing a decimal integer indicating an error cursor
-            position as an index into the original statement string.  The
-            first character has index 1, and positions are measured in
-            characters not bytes.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-internal-position">
-          <term><symbol>PG_DIAG_INTERNAL_POSITION</></term>
-          <listitem>
-           <para>
-            This is defined the same as the
-            <symbol>PG_DIAG_STATEMENT_POSITION</> field, but it is used
-            when the cursor position refers to an internally generated
-            command rather than the one submitted by the client.  The
-            <symbol>PG_DIAG_INTERNAL_QUERY</> field will always appear when
-            this field appears.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-internal-query">
-          <term><symbol>PG_DIAG_INTERNAL_QUERY</></term>
-          <listitem>
-           <para>
-            The text of a failed internally-generated command.  This could
-            be, for example, a SQL query issued by a PL/pgSQL function.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-context">
-          <term><symbol>PG_DIAG_CONTEXT</></term>
-          <listitem>
-           <para>
-            An indication of the context in which the error occurred.
-            Presently this includes a call stack traceback of active
-            procedural language functions and internally-generated queries.
-            The trace is one entry per line, most recent first.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-source-file">
-          <term><symbol>PG_DIAG_SOURCE_FILE</></term>
-          <listitem>
-           <para>
-            The file name of the source-code location where the error was
-            reported.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-source-line">
-          <term><symbol>PG_DIAG_SOURCE_LINE</></term>
-          <listitem>
-           <para>
-            The line number of the source-code location where the error
-            was reported.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry id="libpq-pg-diag-source-function">
-          <term><symbol>PG_DIAG_SOURCE_FUNCTION</></term>
-          <listitem>
-           <para>
-            The name of the source-code function reporting the error.
-           </para>
-          </listitem>
-         </varlistentry>
-        </variablelist>
-       </para>
-
-       <para>
-        The client is responsible for formatting displayed information to meet
-        its needs; in particular it should break long lines as needed.
-        Newline characters appearing in the error message fields should be
-        treated as paragraph breaks, not line breaks.
-       </para>
-
-       <para>
-        Errors generated internally by <application>libpq</application> will
-        have severity and primary message, but typically no other fields.
-        Errors returned by a pre-3.0-protocol server will include severity and
-        primary message, and sometimes a detail message, but no other fields.
-       </para>
-
-       <para>
-        Note that error fields are only available from
-        <structname>PGresult</structname> objects, not
-        <structname>PGconn</structname> objects; there is no
-        <function>PQerrorField</function> function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="libpq-pqclear">
-      <term><function>PQclear</function><indexterm><primary>PQclear</></></term>
-      <listitem>
-       <para>
-        Frees  the  storage  associated with a
-        <structname>PGresult</structname>.  Every command result should be
-        freed via <function>PQclear</function> when it  is  no  longer
-        needed.
-
-<synopsis>
-void PQclear(PGresult *res);
-</synopsis>
-       </para>
-
-       <para>
-        You can keep a <structname>PGresult</structname> object around for
-        as long as you need it; it does not go away when you issue a new
-        command, nor even if you close the connection.  To get rid of it,
-        you must call <function>PQclear</function>.  Failure to do this
-        will result in memory leaks in your application.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="libpq-exec-select-info">
-   <title>Retrieving Query Result Information</title>
-&common;
-   <para>
-    These functions are used to extract information from a
-    <structname>PGresult</structname> object that represents a successful
-    query result (that is, one that has status
-    <literal>PGRES_TUPLES_OK</literal>).  They can also be used to extract
-    information from a successful Describe operation: a Describe's result
-    has all the same column information that actual execution of the query
-    would provide, but it has zero rows.  For objects with other status values,
-    these functions will act as though the result has zero rows and zero columns.
-   </para>
-
-   <variablelist>
-    <varlistentry id="libpq-pqntuples">
-     <term>
-      <function>PQntuples</function>
-      <indexterm>
-       <primary>PQntuples</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the number of rows (tuples) in the query result.  Because
-       it returns an integer result, large result sets might overflow the
-       return value on 32-bit operating systems.
-
-<synopsis>
-int PQntuples(const PGresult *res);
-</synopsis>
-
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqnfields">
-     <term>
-      <function>PQnfields</function>
-      <indexterm>
-       <primary>PQnfields</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the number of columns (fields) in each row of the query
-       result.
-
-<synopsis>
-int PQnfields(const PGresult *res);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqfname">
-     <term>
-      <function>PQfname</function>
-      <indexterm>
-       <primary>PQfname</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the column name associated with the given column number.
-       Column numbers start at 0. The caller should not free the result
-       directly. It will be freed when the associated
-       <structname>PGresult</> handle is passed to
-       <function>PQclear</function>.
-<synopsis>
-char *PQfname(const PGresult *res,
-              int column_number);
-</synopsis>
-      </para>
-
-      <para>
-       <symbol>NULL</symbol> is returned if the column number is out of range.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqfnumber">
-     <term>
-      <function>PQfnumber</function>
-      <indexterm>
-       <primary>PQfnumber</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the column number associated with the given column name.
-<synopsis>
-int PQfnumber(const PGresult *res,
-              const char *column_name);
-</synopsis>
-      </para>
-
-      <para>
-       -1 is returned if the given name does not match any column.
-      </para>
-
-      <para>
-       The given name is treated like an identifier in an SQL command,
-       that is, it is downcased unless double-quoted.  For example, given
-       a query result generated from the SQL command:
-<programlisting>
-SELECT 1 AS FOO, 2 AS "BAR";
-</programlisting>
-       we would have the results:
-<programlisting>
-PQfname(res, 0)              <lineannotation>foo</lineannotation>
-PQfname(res, 1)              <lineannotation>BAR</lineannotation>
-PQfnumber(res, "FOO")        <lineannotation>0</lineannotation>
-PQfnumber(res, "foo")        <lineannotation>0</lineannotation>
-PQfnumber(res, "BAR")        <lineannotation>-1</lineannotation>
-PQfnumber(res, "\"BAR\"")    <lineannotation>1</lineannotation>
-</programlisting>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqftable">
-     <term>
-      <function>PQftable</function>
-      <indexterm>
-       <primary>PQftable</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the OID of the table from which the given column was
-       fetched.  Column numbers start at 0.
-<synopsis>
-Oid PQftable(const PGresult *res,
-             int column_number);
-</synopsis>
-      </para>
-
-      <para>
-       <literal>InvalidOid</> is returned if the column number is out of range,
-       or if the specified column is not a simple reference to a table column,
-       or when using pre-3.0 protocol.
-       You can query the system table <literal>pg_class</literal> to determine
-       exactly which table is referenced.
-      </para>
-
-      <para>
-       The type <type>Oid</type> and the constant
-       <literal>InvalidOid</literal> will be defined when you include
-       the <application>libpq</application> header file. They will both
-       be some integer type.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqftablecol">
-     <term>
-      <function>PQftablecol</function>
-      <indexterm>
-       <primary>PQftablecol</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the column number (within its table) of the column making
-       up the specified query result column.  Query-result column numbers
-       start at 0, but table columns have nonzero numbers.
-<synopsis>
-int PQftablecol(const PGresult *res,
-                int column_number);
-</synopsis>
-      </para>
-
-      <para>
-       Zero is returned if the column number is out of range, or if the
-       specified column is not a simple reference to a table column, or
-       when using pre-3.0 protocol.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqfformat">
-     <term>
-      <function>PQfformat</function>
-      <indexterm>
-       <primary>PQfformat</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the format code indicating the format of the given
-       column.  Column numbers start at 0.
-<synopsis>
-int PQfformat(const PGresult *res,
-              int column_number);
-</synopsis>
-      </para>
-
-      <para>
-       Format code zero indicates textual data representation, while format
-       code one indicates binary representation.  (Other codes are reserved
-       for future definition.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqftype">
-     <term>
-      <function>PQftype</function>
-      <indexterm>
-       <primary>PQftype</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the data type associated with the given  column number.
-       The  integer  returned is the internal OID number of the type.
-       Column numbers start at 0.
-<synopsis>
-Oid PQftype(const PGresult *res,
-            int column_number);
-</synopsis>
-      </para>
-
-      <para>
-       You can query the system table <literal>pg_type</literal> to
-       obtain the names and properties of the various data types. The
-       <acronym>OID</acronym>s of the built-in data types are defined
-       in the file <filename>src/include/catalog/pg_type.h</filename>
-       in the source tree.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqfmod">
-     <term>
-      <function>PQfmod</function>
-      <indexterm>
-       <primary>PQfmod</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns  the type modifier of the column associated with the
-       given column number.  Column numbers start at 0.
-<synopsis>
-int PQfmod(const PGresult *res,
-           int column_number);
-</synopsis>
-      </para>
-
-      <para>
-       The interpretation of modifier values is type-specific; they
-       typically indicate precision or size limits.  The value -1 is
-       used to indicate <quote>no information available</>.  Most data
-       types do not use modifiers, in which case the value is always
-       -1.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqfsize">
-     <term>
-      <function>PQfsize</function>
-      <indexterm>
-       <primary>PQfsize</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns  the  size  in bytes of the column associated with the
-       given column number.  Column numbers start at 0.
-<synopsis>
-int PQfsize(const PGresult *res,
-            int column_number);
-</synopsis>
-      </para>
-
-      <para>
-       <function>PQfsize</> returns the space allocated for this column
-       in a database row, in other words the size of the server's
-       internal representation of the data type.  (Accordingly, it is
-       not really very useful to clients.) A negative value indicates
-       the data type is variable-length.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqbinarytuples">
-     <term>
-      <function>PQbinaryTuples</function>
-      <indexterm>
-       <primary>PQbinaryTuples</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns 1 if the <structname>PGresult</> contains binary data
-       and 0 if it contains text data.
-<synopsis>
-int PQbinaryTuples(const PGresult *res);
-</synopsis>
-      </para>
-
-      <para>
-       This function is deprecated (except for its use in connection with
-       <command>COPY</>), because it is possible for a single
-       <structname>PGresult</> to contain text data in some columns and
-       binary data in others.  <function>PQfformat</> is preferred.
-       <function>PQbinaryTuples</> returns 1 only if all columns of the
-       result are binary (format 1).
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqgetvalue">
-     <term>
-      <function>PQgetvalue</function>
-       <indexterm>
-        <primary>PQgetvalue</primary>
-       </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns a single field value of one row of a
-       <structname>PGresult</structname>.  Row and column numbers start
-       at 0.  The caller should not free the result directly.  It will
-       be freed when the associated <structname>PGresult</> handle is
-       passed to <function>PQclear</function>.
-<synopsis>
-char *PQgetvalue(const PGresult *res,
-                 int row_number,
-                 int column_number);
-</synopsis>
-      </para>
-
-      <para>
-       For data in text format, the value returned by
-       <function>PQgetvalue</function> is a null-terminated character
-       string  representation of the field value.  For data in binary
-       format, the value is in the binary representation determined by
-       the data type's <function>typsend</> and <function>typreceive</>
-       functions.  (The value is actually followed by a zero byte in
-       this case too, but that is not ordinarily useful, since the
-       value is likely to contain embedded nulls.)
-      </para>
-
-      <para>
-       An empty string is returned if the field value is null.  See
-       <function>PQgetisnull</> to distinguish null values from
-       empty-string values.
-      </para>
-
-      <para>
-       The pointer returned  by  <function>PQgetvalue</function> points
-       to storage that is part of the <structname>PGresult</structname>
-       structure.  One should not modify the data it points to, and one
-       must explicitly copy the data into other storage if it is to be
-       used past the lifetime of the  <structname>PGresult</structname>
-       structure itself.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqgetisnull">
-     <term>
-      <function>PQgetisnull</function>
-      <indexterm>
-       <primary>PQgetisnull</primary>
-      </indexterm>
-      <indexterm>
-       <primary>null value</primary>
-       <secondary sortas="libpq">in libpq</secondary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Tests a field for a null value.  Row and column numbers start
-       at 0.
-<synopsis>
-int PQgetisnull(const PGresult *res,
-                int row_number,
-                int column_number);
-</synopsis>
-      </para>
-
-      <para>
-       This function returns  1 if the field is null and 0 if it
-       contains a non-null value.  (Note that
-       <function>PQgetvalue</function> will return an empty string,
-       not a null pointer, for a null field.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqgetlength">
-     <term>
-     <function>PQgetlength</function>
-     <indexterm>
-      <primary>PQgetlength</primary>
-     </indexterm></term>
-
-     <listitem>
-      <para>
-       Returns the actual length of a field value in bytes.  Row and
-       column numbers start at 0.
-<synopsis>
-int PQgetlength(const PGresult *res,
-                int row_number,
-                int column_number);
-</synopsis>
-      </para>
-
-      <para>
-       This is the actual data length for the particular data value,
-       that is, the size of the object pointed to by
-       <function>PQgetvalue</function>.  For text data format this is
-       the same as <function>strlen()</>.  For binary format this is
-       essential information.  Note that one should <emphasis>not</>
-       rely on <function>PQfsize</function> to obtain the actual data
-       length.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqnparams">
-     <term>
-      <function>PQnparams</function>
-      <indexterm>
-       <primary>PQnparams</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the number of parameters of a prepared statement.
-<synopsis>
-int PQnparams(const PGresult *res);
-</synopsis>
-      </para>
-
-      <para>
-       This function is only useful when inspecting the result of
-       <function>PQdescribePrepared</>.  For other types of queries it
-       will return zero.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqparamtype">
-     <term>
-      <function>PQparamtype</function>
-      <indexterm>
-       <primary>PQparamtype</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the data type of the indicated statement parameter.
-       Parameter numbers start at 0.
-<synopsis>
-Oid PQparamtype(const PGresult *res, int param_number);
-</synopsis>
-      </para>
-
-      <para>
-       This function is only useful when inspecting the result of
-       <function>PQdescribePrepared</>.  For other types of queries it
-       will return zero.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqprint">
-     <term>
-      <function>PQprint</function>
-      <indexterm>
-       <primary>PQprint</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Prints out all the rows and,  optionally,  the column names  to
-       the specified output stream.
-<synopsis>
-void PQprint(FILE *fout,      /* output stream */
-             const PGresult *res,
-             const PQprintOpt *po);
-typedef struct
-{
-    pqbool  header;      /* print output field headings and row count */
-    pqbool  align;       /* fill align the fields */
-    pqbool  standard;    /* old brain dead format */
-    pqbool  html3;       /* output HTML tables */
-    pqbool  expanded;    /* expand tables */
-    pqbool  pager;       /* use pager for output if needed */
-    char    *fieldSep;   /* field separator */
-    char    *tableOpt;   /* attributes for HTML table element */
-    char    *caption;    /* HTML table caption */
-    char    **fieldName; /* null-terminated array of replacement field names */
-} PQprintOpt;
-</synopsis>
-      </para>
-
-      <para>
-       This function was formerly used by <application>psql</application>
-       to print query results, but this is no longer the case.  Note
-       that it assumes all the data is in text format.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </sect2>
-
-  <sect2 id="libpq-exec-nonselect">
-   <title>Retrieving Other Result Information</title>
-&common;
-   <para>
-    These functions are used to extract other information from
-    <structname>PGresult</structname> objects.
-   </para>
-
-   <variablelist>
-    <varlistentry id="libpq-pqcmdstatus">
-     <term>
-      <function>PQcmdStatus</function>
-      <indexterm>
-       <primary>PQcmdStatus</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the command status tag from the SQL command that generated
-       the <structname>PGresult</structname>.
-<synopsis>
-char *PQcmdStatus(PGresult *res);
-</synopsis>
-      </para>
-
-      <para>
-       Commonly this is just the name of the command, but it might include
-       additional data such as the number of rows processed. The caller
-       should not free the result directly. It will be freed when the
-       associated <structname>PGresult</> handle is passed to
-       <function>PQclear</function>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqcmdtuples">
-     <term>
-      <function>PQcmdTuples</function>
-      <indexterm>
-       <primary>PQcmdTuples</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the number of rows affected by the SQL command.
-<synopsis>
-char *PQcmdTuples(PGresult *res);
-</synopsis>
-      </para>
-
-      <para>
-       This function returns a string containing the number of rows
-       affected by the <acronym>SQL</> statement that generated the
-       <structname>PGresult</>. This function can only be used following
-       the execution of a <command>SELECT</>, <command>CREATE TABLE AS</>,
-       <command>INSERT</>, <command>UPDATE</>, <command>DELETE</>,
-       <command>MOVE</>, <command>FETCH</>, or <command>COPY</> statement,
-       or an <command>EXECUTE</> of a prepared query that contains an
-       <command>INSERT</>, <command>UPDATE</>, or <command>DELETE</> statement.
-       If the command that generated the <structname>PGresult</> was anything
-       else, <function>PQcmdTuples</> returns an empty string. The caller
-       should not free the return value directly. It will be freed when
-       the associated <structname>PGresult</> handle is passed to
-       <function>PQclear</function>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqoidvalue">
-     <term>
-      <function>PQoidValue</function>
-      <indexterm>
-       <primary>PQoidValue</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the OID<indexterm><primary>OID</><secondary>in libpq</></>
-       of the inserted row, if the <acronym>SQL</> command was an
-       <command>INSERT</> that inserted exactly one row into a table that
-       has OIDs, or a <command>EXECUTE</> of a prepared query containing
-       a suitable <command>INSERT</> statement.  Otherwise, this function
-       returns <literal>InvalidOid</literal>. This function will also
-       return <literal>InvalidOid</literal> if the table affected by the
-       <command>INSERT</> statement does not contain OIDs.
-<synopsis>
-Oid PQoidValue(const PGresult *res);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqoidstatus">
-     <term>
-      <function>PQoidStatus</function>
-      <indexterm>
-       <primary>PQoidStatus</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       This function is deprecated in favor of
-       <function>PQoidValue</function> and is not thread-safe.
-       It returns a string with the OID of the inserted row, while
-       <function>PQoidValue</function> returns the OID value.
-<synopsis>
-char *PQoidStatus(const PGresult *res);
-</synopsis>
-      </para>
-
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-  </sect2>
-
-  <sect2 id="libpq-exec-escape-string">
-   <title>Escaping Strings for Inclusion in SQL Commands</title>
-
-   <indexterm zone="libpq-exec-escape-string">
-    <primary>escaping strings</primary>
-    <secondary>in libpq</secondary>
-   </indexterm>
-&common;
-   <variablelist>
-    <varlistentry id="libpq-pqescapeliteral">
-     <term>
-      <function>PQescapeLiteral</function>
-      <indexterm>
-       <primary>PQescapeLiteral</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-     <para>
-<synopsis>
-char *PQescapeLiteral(PGconn *conn, const char *str, size_t length);
-</synopsis>
-     </para>
-
-     <para>
-      <function>PQescapeLiteral</function> escapes a string for
-      use within an SQL command.  This is useful when inserting data
-      values as literal constants in SQL commands.  Certain characters
-      (such as quotes and backslashes) must be escaped to prevent them
-      from being interpreted specially by the SQL parser.
-      <function>PQescapeLiteral</> performs this operation.
-     </para>
-
-     <para>
-      <function>PQescapeLiteral</> returns an escaped version of the
-      <parameter>str</parameter> parameter in memory allocated with
-      <function>malloc()</>.  This memory should be freed using
-      <function>PQfreemem()</> when the result is no longer needed.
-      A terminating zero byte is not required, and should not be
-      counted in <parameter>length</>.  (If a terminating zero byte is found
-      before <parameter>length</> bytes are processed,
-      <function>PQescapeLiteral</> stops at the zero; the behavior is
-      thus rather like <function>strncpy</>.) The
-      return string has all special characters replaced so that they can
-<!## PG>
-      be properly processed by the <productname>PostgreSQL</productname>
-      string literal parser.  A terminating zero byte is also added.  The
-      single quotes that must surround <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-      be properly processed by the <productname>Postgres-XC</productname>
-      string literal parser.  A terminating zero byte is also added.  The
-      single quotes that must surround <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-      be properly processed by the <productname>Postgres-XL</productname>
-      string literal parser.  A terminating zero byte is also added.  The
-      single quotes that must surround <productname>Postgres-XL</productname>
-<!## end>
-      string literals are included in the result string.
-     </para>
-
-     <para>
-      On error, <function>PQescapeLiteral</> returns <symbol>NULL</> and a suitable
-      message is stored in the <parameter>conn</> object.
-     </para>
-
-     <tip>
-      <para>
-       It is especially important to do proper escaping when handling
-       strings that were received from an untrustworthy source.
-       Otherwise there is a security risk: you are vulnerable to
-       <quote>SQL injection</> attacks wherein unwanted SQL commands are
-       fed to your database.
-      </para>
-     </tip>
-
-     <para>
-      Note that it is not necessary nor correct to do escaping when a data
-      value is passed as a separate parameter in <function>PQexecParams</> or
-      its sibling routines.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqescapeidentifier">
-     <term>
-      <function>PQescapeIdentifier</function>
-      <indexterm>
-       <primary>PQescapeIdentifier</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-     <para>
-<synopsis>
-char *PQescapeIdentifier(PGconn *conn, const char *str, size_t length);
-</synopsis>
-     </para>
-
-     <para>
-      <function>PQescapeIdentifier</function> escapes a string for
-      use as an SQL identifier, such as a table, column, or function name.
-      This is useful when a user-supplied identifier might contain
-      special characters that would otherwise not be interpreted as part
-      of the identifier by the SQL parser, or when the identifier might
-      contain upper case characters whose case should be preserved.
-     </para>
-
-     <para>
-      <function>PQescapeIdentifier</> returns a version of the
-      <parameter>str</parameter> parameter escaped as an SQL identifier
-      in memory allocated with <function>malloc()</>.  This memory must be
-      freed using <function>PQfreemem()</> when the result is no longer
-      needed.  A terminating zero byte is not required, and should not be
-      counted in <parameter>length</>.  (If a terminating zero byte is found
-      before <parameter>length</> bytes are processed,
-      <function>PQescapeIdentifier</> stops at the zero; the behavior is
-      thus rather like <function>strncpy</>.) The
-      return string has all special characters replaced so that it
-      will be properly processed as an SQL identifier.  A terminating zero byte
-      is also added.  The return string will also be surrounded by double
-      quotes.
-     </para>
-
-     <para>
-      On error, <function>PQescapeIdentifier</> returns <symbol>NULL</> and a suitable
-      message is stored in the <parameter>conn</> object.
-     </para>
-
-     <tip>
-      <para>
-       As with string literals, to prevent SQL injection attacks,
-       SQL identifiers must be escaped when they are received from an
-       untrustworthy source.
-      </para>
-     </tip>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqescapestringconn">
-     <term>
-      <function>PQescapeStringConn</function>
-      <indexterm>
-       <primary>PQescapeStringConn</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-     <para>
-<synopsis>
-size_t PQescapeStringConn(PGconn *conn,
-                          char *to, const char *from, size_t length,
-                          int *error);
-</synopsis>
-     </para>
-
-     <para>
-      <function>PQescapeStringConn</> escapes string literals, much like
-      <function>PQescapeLiteral</>.  Unlike <function>PQescapeLiteral</>,
-      the caller is responsible for providing an appropriately sized buffer.
-      Furthermore, <function>PQescapeStringConn</> does not generate the
-<!## PG>
-      single quotes that must surround <productname>PostgreSQL</> string
-<!## end>
-<!## XC>
-      single quotes that must surround <productname>Postgres-XC</> string
-<!## end>
-<!## XL>
-      single quotes that must surround <productname>Postgres-XL</> string
-<!## end>
-      literals; they should be provided in the SQL command that the
-      result is inserted into.  The parameter <parameter>from</> points to
-      the first character of the string that is to be escaped, and the
-      <parameter>length</> parameter gives the number of bytes in this
-      string.  A terminating zero byte is not required, and should not be
-      counted in <parameter>length</>.  (If a terminating zero byte is found
-      before <parameter>length</> bytes are processed,
-      <function>PQescapeStringConn</> stops at the zero; the behavior is
-      thus rather like <function>strncpy</>.) <parameter>to</> shall point
-      to a buffer that is able to hold at least one more byte than twice
-      the value of <parameter>length</>, otherwise the behavior is undefined.
-      Behavior is likewise undefined if the <parameter>to</> and
-      <parameter>from</> strings overlap.
-     </para>
-
-     <para>
-      If the <parameter>error</> parameter is not <symbol>NULL</>, then
-      <literal>*error</> is set to zero on success, nonzero on error.
-      Presently the only possible error conditions involve invalid multibyte
-      encoding in the source string.  The output string is still generated
-      on error, but it can be expected that the server will reject it as
-      malformed.  On error, a suitable message is stored in the
-      <parameter>conn</> object, whether or not <parameter>error</> is <symbol>NULL</>.
-     </para>
-
-     <para>
-      <function>PQescapeStringConn</> returns the number of bytes written
-      to <parameter>to</>, not including the terminating zero byte.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqescapestring">
-     <term>
-      <function>PQescapeString</function>
-      <indexterm>
-       <primary>PQescapeString</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-     <para>
-<synopsis>
-size_t PQescapeString (char *to, const char *from, size_t length);
-</synopsis>
-     </para>
-
-     <para>
-      <function>PQescapeString</> is an older, deprecated version of
-      <function>PQescapeStringConn</>; the difference is that it does
-      not take <parameter>conn</> or <parameter>error</> parameters.
-      Because of this, it cannot adjust its behavior depending on the
-      connection properties (such as character encoding) and therefore
-      <emphasis>it might give the wrong results</>.  Also, it has no way
-      to report error conditions.
-     </para>
-
-     <para>
-      <function>PQescapeString</> can be used safely in single-threaded
-<!## PG>
-      client programs that work with only one <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-      client programs that work with only one <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-      client programs that work with only one <productname>Postgres-XL</>
-<!## end>
-      connection at a time (in this case it can find out what it needs to
-      know <quote>behind the scenes</>).  In other contexts it is a security
-      hazard and should be avoided in favor of
-      <function>PQescapeStringConn</>.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqescapebyteaconn">
-     <term>
-      <function>PQescapeByteaConn</function>
-      <indexterm>
-       <primary>PQescapeByteaConn</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-     <para>
-       Escapes binary data for use within an SQL command with the type
-       <type>bytea</type>.  As with <function>PQescapeStringConn</function>,
-       this is only used when inserting data directly into an SQL command string.
-<synopsis>
-unsigned char *PQescapeByteaConn(PGconn *conn,
-                                 const unsigned char *from,
-                                 size_t from_length,
-                                 size_t *to_length);
-</synopsis>
-      </para>
-
-      <para>
-       Certain byte values <emphasis>must</emphasis> be escaped (but all
-       byte values <emphasis>can</emphasis> be escaped) when used as part
-       of a <type>bytea</type> literal in an <acronym>SQL</acronym>
-       statement. In general, to escape a byte, it is converted into the
-       three digit octal number equal to the octet value, and preceded by
-       usually two backslashes. The single quote (<literal>'</>) and backslash
-       (<literal>\</>) characters have special alternative escape
-       sequences. See <xref linkend="datatype-binary"> for more
-       information. <function>PQescapeByteaConn</function> performs this
-       operation, escaping only the minimally required bytes.
-      </para>
-
-      <para>
-       The <parameter>from</parameter> parameter points to the first
-       byte of the string that is to be escaped, and the
-       <parameter>from_length</parameter> parameter gives the number of
-       bytes in this binary string.  (A terminating zero byte is
-       neither necessary nor counted.)  The <parameter>to_length</parameter>
-       parameter points to a variable that will hold the resultant
-       escaped string length. This result string length includes the terminating
-       zero byte of the result.
-      </para>
-
-      <para>
-       <function>PQescapeByteaConn</> returns an escaped version of the
-       <parameter>from</parameter> parameter binary string in memory
-       allocated with <function>malloc()</>.  This memory should be freed using
-       <function>PQfreemem()</> when the result is no longer needed.  The
-       return string has all special characters replaced so that they can
-<!## PG>
-       be properly processed by the <productname>PostgreSQL</productname>
-       string literal parser, and the <type>bytea</type> input function. A
-       terminating zero byte is also added.  The single quotes that must
-       surround <productname>PostgreSQL</productname> string literals are
-<!## end>
-<!## XC>
-       be properly processed by the <productname>Postgres-XC</productname>
-       string literal parser, and the <type>bytea</type> input function. A
-       terminating zero byte is also added.  The single quotes that must
-       surround <productname>Postgres-XC</productname> string literals are
-<!## end>
-<!## XL>
-       be properly processed by the <productname>Postgres-XL</productname>
-       string literal parser, and the <type>bytea</type> input function. A
-       terminating zero byte is also added.  The single quotes that must
-       surround <productname>Postgres-XL</productname> string literals are
-<!## end>
-       not part of the result string.
-      </para>
-
-      <para>
-       On error, a null pointer is returned, and a suitable error message
-       is stored in the <parameter>conn</> object.  Currently, the only
-       possible error is insufficient memory for the result string.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqescapebytea">
-     <term>
-      <function>PQescapeBytea</function>
-      <indexterm>
-       <primary>PQescapeBytea</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       <function>PQescapeBytea</> is an older, deprecated version of
-       <function>PQescapeByteaConn</>.
-<synopsis>
-unsigned char *PQescapeBytea(const unsigned char *from,
-                             size_t from_length,
-                             size_t *to_length);
-</synopsis>
-      </para>
-
-      <para>
-       The only difference from <function>PQescapeByteaConn</> is that
-       <function>PQescapeBytea</> does not take a <structname>PGconn</>
-       parameter.  Because of this, it cannot adjust its behavior
-       depending on the connection properties (in particular, whether
-       standard-conforming strings are enabled) and therefore
-       <emphasis>it might give the wrong results</>.  Also, it has no
-       way to return an error message on failure.
-      </para>
-
-      <para>
-       <function>PQescapeBytea</> can be used safely in single-threaded
-<!## PG>
-       client programs that work with only one <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-       client programs that work with only one <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-       client programs that work with only one <productname>Postgres-XL</>
-<!## end>
-       connection at a time (in this case it can find out what it needs
-       to know <quote>behind the scenes</>).  In other contexts it is
-       a security hazard and should be avoided in favor of
-       <function>PQescapeByteaConn</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqunescapebytea">
-     <term>
-      <function>PQunescapeBytea</function>
-      <indexterm>
-       <primary>PQunescapeBytea</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Converts a string representation of binary data into binary data
-       &mdash; the reverse of <function>PQescapeBytea</function>.  This
-       is needed when retrieving <type>bytea</type> data in text format,
-       but not when retrieving it in binary format.
-
-<synopsis>
-unsigned char *PQunescapeBytea(const unsigned char *from, size_t *to_length);
-</synopsis>
-      </para>
-
-      <para>
-       The <parameter>from</parameter> parameter points to a string
-       such as might be returned by <function>PQgetvalue</function> when applied
-       to a <type>bytea</type> column. <function>PQunescapeBytea</function>
-       converts this string representation into its binary representation.
-       It returns a pointer to a buffer allocated with
-       <function>malloc()</function>, or <symbol>NULL</> on error, and puts the size of
-       the buffer in <parameter>to_length</parameter>. The result must be
-       freed using <function>PQfreemem</> when it is no longer needed.
-      </para>
-
-      <para>
-       This conversion is not exactly the inverse of
-       <function>PQescapeBytea</function>, because the string is not expected
-       to be <quote>escaped</> when received from <function>PQgetvalue</function>.
-       In particular this means there is no need for string quoting considerations,
-       and so no need for a <structname>PGconn</> parameter.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="libpq-async">
-  <title>Asynchronous Command Processing</title>
-
-  <indexterm zone="libpq-async">
-   <primary>nonblocking connection</primary>
-  </indexterm>
-&common;
-  <para>
-   The <function>PQexec</function> function is adequate for submitting
-   commands in normal, synchronous applications.  It has a couple of
-   deficiencies, however, that can be of importance to some users:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <function>PQexec</function> waits for the command to be completed.
-      The application might have other work to do (such as maintaining a
-      user interface), in which case it won't want to block waiting for
-      the response.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Since the execution of the client application is suspended while it
-      waits for the result, it is hard for the application to decide that
-      it would like to try to cancel the ongoing command.  (It can be done
-      from a signal handler, but not otherwise.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>PQexec</function> can return only one
-      <structname>PGresult</structname> structure.  If the submitted command
-      string contains multiple <acronym>SQL</acronym> commands, all but
-      the last <structname>PGresult</structname> are discarded by
-      <function>PQexec</function>.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   Applications that do not like these limitations can instead use the
-   underlying functions that <function>PQexec</function> is built from:
-   <function>PQsendQuery</function> and <function>PQgetResult</function>.
-   There are also
-   <function>PQsendQueryParams</function>,
-   <function>PQsendPrepare</function>,
-   <function>PQsendQueryPrepared</function>,
-   <function>PQsendDescribePrepared</function>, and
-   <function>PQsendDescribePortal</function>,
-   which can be used with <function>PQgetResult</function> to duplicate
-   the functionality of
-   <function>PQexecParams</function>,
-   <function>PQprepare</function>,
-   <function>PQexecPrepared</function>,
-   <function>PQdescribePrepared</function>, and
-   <function>PQdescribePortal</function>
-   respectively.
-
-   <variablelist>
-    <varlistentry id="libpq-pqsendquery">
-     <term>
-      <function>PQsendQuery</function>
-      <indexterm>
-       <primary>PQsendQuery</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Submits a command to the server without waiting for the result(s).
-       1 is returned if the command was successfully dispatched and 0 if
-       not (in which case, use <function>PQerrorMessage</> to get more
-       information about the failure).
-<synopsis>
-int PQsendQuery(PGconn *conn, const char *command);
-</synopsis>
-
-       After successfully calling <function>PQsendQuery</function>, call
-       <function>PQgetResult</function> one or more times to obtain the
-       results.  <function>PQsendQuery</function> cannot be called again
-       (on the same connection) until <function>PQgetResult</function>
-       has returned a null pointer, indicating that the command is done.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqsendqueryparams">
-     <term>
-      <function>PQsendQueryParams</function>
-      <indexterm>
-       <primary>PQsendQueryParams</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Submits a command and separate parameters to the server without
-       waiting for the result(s).
-<synopsis>
-int PQsendQueryParams(PGconn *conn,
-                      const char *command,
-                      int nParams,
-                      const Oid *paramTypes,
-                      const char * const *paramValues,
-                      const int *paramLengths,
-                      const int *paramFormats,
-                      int resultFormat);
-</synopsis>
-
-       This is equivalent to <function>PQsendQuery</function> except that
-       query parameters can be specified separately from the query string.
-       The function's parameters are handled identically to
-       <function>PQexecParams</function>.  Like
-       <function>PQexecParams</function>, it will not work on 2.0-protocol
-       connections, and it allows only one command in the query string.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqsendprepare">
-     <term>
-      <function>PQsendPrepare</>
-      <indexterm>
-       <primary>PQsendPrepare</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Sends a request to create a prepared statement with the given
-       parameters, without waiting for completion.
-<synopsis>
-int PQsendPrepare(PGconn *conn,
-                  const char *stmtName,
-                  const char *query,
-                  int nParams,
-                  const Oid *paramTypes);
-</synopsis>
-
-       This is an asynchronous version of <function>PQprepare</>: it
-       returns 1 if it was able to dispatch the request, and 0 if not.
-       After a successful call, call <function>PQgetResult</function> to
-       determine whether the server successfully created the prepared
-       statement.  The function's parameters are handled identically to
-       <function>PQprepare</function>.  Like
-       <function>PQprepare</function>, it will not work on 2.0-protocol
-       connections.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqsendqueryprepared">
-     <term>
-      <function>PQsendQueryPrepared</function>
-      <indexterm>
-       <primary>PQsendQueryPrepared</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Sends a request to execute a prepared statement with given
-       parameters, without waiting for the result(s).
-<synopsis>
-int PQsendQueryPrepared(PGconn *conn,
-                        const char *stmtName,
-                        int nParams,
-                        const char * const *paramValues,
-                        const int *paramLengths,
-                        const int *paramFormats,
-                        int resultFormat);
-</synopsis>
-
-       This is similar to <function>PQsendQueryParams</function>, but
-       the command to be executed is specified by naming a
-       previously-prepared statement, instead of giving a query string.
-       The function's parameters are handled identically to
-       <function>PQexecPrepared</function>.  Like
-       <function>PQexecPrepared</function>, it will not work on
-       2.0-protocol connections.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqsenddescribeprepared">
-     <term>
-      <function>PQsendDescribePrepared</>
-      <indexterm>
-       <primary>PQsendDescribePrepared</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Submits a request to obtain information about the specified
-       prepared statement, without waiting for completion.
-<synopsis>
-int PQsendDescribePrepared(PGconn *conn, const char *stmtName);
-</synopsis>
-
-       This is an asynchronous version of <function>PQdescribePrepared</>:
-       it returns 1 if it was able to dispatch the request, and 0 if not.
-       After a successful call, call <function>PQgetResult</function> to
-       obtain the results.  The function's parameters are handled
-       identically to <function>PQdescribePrepared</function>.  Like
-       <function>PQdescribePrepared</function>, it will not work on
-       2.0-protocol connections.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqsenddescribeportal">
-     <term>
-      <function>PQsendDescribePortal</>
-      <indexterm>
-       <primary>PQsendDescribePortal</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Submits a request to obtain information about the specified
-       portal, without waiting for completion.
-<synopsis>
-int PQsendDescribePortal(PGconn *conn, const char *portalName);
-</synopsis>
-
-       This is an asynchronous version of <function>PQdescribePortal</>:
-       it returns 1 if it was able to dispatch the request, and 0 if not.
-       After a successful call, call <function>PQgetResult</function> to
-       obtain the results.  The function's parameters are handled
-       identically to <function>PQdescribePortal</function>.  Like
-       <function>PQdescribePortal</function>, it will not work on
-       2.0-protocol connections.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqgetresult">
-     <term>
-      <function>PQgetResult</function>
-      <indexterm>
-       <primary>PQgetResult</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Waits for the next result from a prior
-       <function>PQsendQuery</function>,
-       <function>PQsendQueryParams</function>,
-       <function>PQsendPrepare</function>, or
-       <function>PQsendQueryPrepared</function> call, and returns it.
-       A null pointer is returned when the command is complete and there
-       will be no more results.
-<synopsis>
-PGresult *PQgetResult(PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       <function>PQgetResult</function> must be called repeatedly until
-       it returns a null pointer, indicating that the command is done.
-       (If called when no command is active,
-       <function>PQgetResult</function> will just return a null pointer
-       at once.) Each non-null result from
-       <function>PQgetResult</function> should be processed using the
-       same <structname>PGresult</> accessor functions previously
-       described.  Don't forget to free each result object with
-       <function>PQclear</function> when done with it.  Note that
-       <function>PQgetResult</function> will block only if a command is
-       active and the necessary response data has not yet been read by
-       <function>PQconsumeInput</function>.
-      </para>
-
-      <note>
-       <para>
-        Even when <function>PQresultStatus</function> indicates a fatal
-        error, <function>PQgetResult</function> should be called until it
-        returns a null pointer to allow <application>libpq</> to
-        process the error information completely.
-       </para>
-      </note>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   Using <function>PQsendQuery</function> and
-   <function>PQgetResult</function> solves one of
-   <function>PQexec</function>'s problems:  If a command string contains
-   multiple <acronym>SQL</acronym> commands, the results of those commands
-   can be obtained individually.  (This allows a simple form of overlapped
-   processing, by the way: the client can be handling the results of one
-   command while the server is still working on later queries in the same
-   command string.)  However, calling <function>PQgetResult</function>
-   will still cause the client to block until the server completes the
-   next <acronym>SQL</acronym> command.  This can be avoided by proper
-   use of two more functions:
-
-   <variablelist>
-    <varlistentry id="libpq-pqconsumeinput">
-     <term>
-      <function>PQconsumeInput</function>
-      <indexterm>
-       <primary>PQconsumeInput</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       If input is available from the server, consume it.
-<synopsis>
-int PQconsumeInput(PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       <function>PQconsumeInput</function> normally returns 1 indicating
-       <quote>no error</quote>, but returns 0 if there was some kind of
-       trouble (in which case <function>PQerrorMessage</function> can be
-       consulted).  Note that the result does not say whether any input
-       data was actually collected. After calling
-       <function>PQconsumeInput</function>, the application can check
-       <function>PQisBusy</function> and/or
-       <function>PQnotifies</function> to see if their state has changed.
-      </para>
-
-      <para>
-       <function>PQconsumeInput</function> can be called even if the
-       application is not prepared to deal with a result or notification
-       just yet.  The function will read available data and save it in
-       a buffer, thereby causing a <function>select()</function>
-       read-ready indication to go away.  The application can thus use
-       <function>PQconsumeInput</function> to clear the
-       <function>select()</function> condition immediately, and then
-       examine the results at leisure.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqisbusy">
-     <term>
-      <function>PQisBusy</function>
-      <indexterm>
-       <primary>PQisBusy</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns 1 if a command is busy, that is,
-       <function>PQgetResult</function> would block waiting for input.
-       A 0 return indicates that <function>PQgetResult</function> can be
-       called with assurance of not blocking.
-<synopsis>
-int PQisBusy(PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       <function>PQisBusy</function> will not itself attempt to read data
-       from the server; therefore <function>PQconsumeInput</function>
-       must be invoked first, or the busy state will never end.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   A typical application using these functions will have a main loop that
-   uses <function>select()</function> or <function>poll()</> to wait for
-   all the conditions that it must respond to.  One of the conditions
-   will be input available from the server, which in terms of
-   <function>select()</function> means readable data on the file
-   descriptor identified by <function>PQsocket</function>.  When the main
-   loop detects input ready, it should call
-   <function>PQconsumeInput</function> to read the input.  It can then
-   call <function>PQisBusy</function>, followed by
-   <function>PQgetResult</function> if <function>PQisBusy</function>
-   returns false (0).  It can also call <function>PQnotifies</function>
-   to detect <command>NOTIFY</> messages (see <xref
-   linkend="libpq-notify">).
-  </para>
-
-  <para>
-   A client that uses
-   <function>PQsendQuery</function>/<function>PQgetResult</function>
-   can also attempt to cancel a command that is still being processed
-   by the server; see <xref linkend="libpq-cancel">.  But regardless of
-   the return value of <function>PQcancel</function>, the application
-   must continue with the normal result-reading sequence using
-   <function>PQgetResult</function>.  A successful cancellation will
-   simply cause the command to terminate sooner than it would have
-   otherwise.
-  </para>
-
-  <para>
-   By using the functions described above, it is possible to avoid
-   blocking while waiting for input from the database server.  However,
-   it is still possible that the application will block waiting to send
-   output to the server.  This is relatively uncommon but can happen if
-   very long SQL commands or data values are sent.  (It is much more
-   probable if the application sends data via <command>COPY IN</command>,
-   however.)  To prevent this possibility and achieve completely
-   nonblocking database operation, the following additional functions
-   can be used.
-
-   <variablelist>
-    <varlistentry id="libpq-pqsetnonblocking">
-     <term>
-      <function>PQsetnonblocking</function>
-      <indexterm>
-       <primary>PQsetnonblocking</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Sets the nonblocking status of the connection.
-<synopsis>
-int PQsetnonblocking(PGconn *conn, int arg);
-</synopsis>
-      </para>
-
-      <para>
-       Sets the state of the connection to nonblocking if
-       <parameter>arg</parameter> is 1, or blocking if
-       <parameter>arg</parameter> is 0.  Returns 0 if OK, -1 if error.
-      </para>
-
-      <para>
-       In the nonblocking state, calls to
-       <function>PQsendQuery</function>, <function>PQputline</function>,
-       <function>PQputnbytes</function>, and
-       <function>PQendcopy</function> will not block but instead return
-       an error if they need to be called again.
-      </para>
-
-      <para>
-       Note that <function>PQexec</function> does not honor nonblocking
-       mode; if it is called, it will act in blocking fashion anyway.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqisnonblocking">
-     <term>
-      <function>PQisnonblocking</function>
-      <indexterm>
-       <primary>PQisnonblocking</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the blocking status of the database connection.
-<synopsis>
-int PQisnonblocking(const PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       Returns 1 if the connection is set to nonblocking mode and 0 if
-       blocking.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqflush">
-     <term>
-      <function>PQflush</function>
-       <indexterm>
-        <primary>PQflush</primary>
-       </indexterm>
-      </term>
-
-      <listitem>
-       <para>
-       Attempts to flush any queued output data to the server.  Returns
-       0 if successful (or if the send queue is empty), -1 if it failed
-       for some reason, or 1 if it was unable to send all the data in
-       the send queue yet (this case can only occur if the connection
-       is nonblocking).
-<synopsis>
-int PQflush(PGconn *conn);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   After sending any command or data on a nonblocking connection, call
-   <function>PQflush</function>.  If it returns 1, wait for the socket
-   to be write-ready and call it again; repeat until it returns 0.  Once
-   <function>PQflush</function> returns 0, wait for the socket to be
-   read-ready and then read the response as described above.
-  </para>
-
- </sect1>
-
- <sect1 id="libpq-cancel">
-  <title>Cancelling Queries in Progress</title>
-
-  <indexterm zone="libpq-cancel">
-   <primary>canceling</primary>
-   <secondary>SQL command</secondary>
-  </indexterm>
-&common;
-  <para>
-   A client application can request cancellation of a command that is
-   still being processed by the server, using the functions described in
-   this section.
-
-   <variablelist>
-    <varlistentry id="libpq-pqgetcancel">
-     <term>
-      <function>PQgetCancel</function>
-      <indexterm>
-       <primary>PQgetCancel</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Creates a data structure containing the information needed to cancel
-       a command issued through a particular database connection.
-<synopsis>
-PGcancel *PQgetCancel(PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       <function>PQgetCancel</function> creates a
-       <structname>PGcancel</><indexterm><primary>PGcancel</></> object
-       given a <structname>PGconn</> connection object.  It will return
-       <symbol>NULL</> if the given <parameter>conn</> is <symbol>NULL</> or an invalid
-       connection.  The <structname>PGcancel</> object is an opaque
-       structure that is not meant to be accessed directly by the
-       application; it can only be passed to <function>PQcancel</function>
-       or <function>PQfreeCancel</function>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqfreecancel">
-     <term>
-      <function>PQfreeCancel</function>
-      <indexterm>
-       <primary>PQfreeCancel</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Frees a data structure created by <function>PQgetCancel</function>.
-<synopsis>
-void PQfreeCancel(PGcancel *cancel);
-</synopsis>
-      </para>
-
-      <para>
-       <function>PQfreeCancel</function> frees a data object previously created
-       by <function>PQgetCancel</function>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqcancel">
-     <term>
-      <function>PQcancel</function>
-      <indexterm>
-       <primary>PQcancel</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Requests that the server abandon processing of the current command.
-<synopsis>
-int PQcancel(PGcancel *cancel, char *errbuf, int errbufsize);
-</synopsis>
-      </para>
-
-      <para>
-       The return value is 1 if the cancel request was successfully
-       dispatched and 0 if not.  If not, <parameter>errbuf</> is filled
-       with an explanatory error message.  <parameter>errbuf</>
-       must be a char array of size <parameter>errbufsize</> (the
-       recommended size is 256 bytes).
-      </para>
-
-      <para>
-       Successful dispatch is no guarantee that the request will have
-       any effect, however.  If the cancellation is effective, the current
-       command will terminate early and return an error result.  If the
-       cancellation fails (say, because the server was already done
-       processing the command), then there will be no visible result at
-       all.
-      </para>
-
-      <para>
-       <function>PQcancel</function> can safely be invoked from a signal
-       handler, if the <parameter>errbuf</> is a local variable in the
-       signal handler.  The <structname>PGcancel</> object is read-only
-       as far as <function>PQcancel</function> is concerned, so it can
-       also be invoked from a thread that is separate from the one
-       manipulating the <structname>PGconn</> object.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-   <variablelist>
-    <varlistentry id="libpq-pqrequestcancel">
-     <term>
-      <function>PQrequestCancel</function>
-      <indexterm>
-       <primary>PQrequestCancel</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       <function>PQrequestCancel</function> is a deprecated variant of
-       <function>PQcancel</function>.
-<synopsis>
-int PQrequestCancel(PGconn *conn);
-</synopsis>
-      </para>
-
-      <para>
-       Requests that the server abandon processing of the current
-       command.  It operates directly on the
-       <structname>PGconn</> object, and in case of failure stores the
-       error message in the <structname>PGconn</> object (whence it can
-       be retrieved by <function>PQerrorMessage</function>).  Although
-       the functionality is the same, this approach creates hazards for
-       multiple-thread programs and signal handlers, since it is possible
-       that overwriting the <structname>PGconn</>'s error message will
-       mess up the operation currently in progress on the connection.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
- </sect1>
-
- <sect1 id="libpq-fastpath">
-  <title>The Fast-Path Interface</title>
-
-  <indexterm zone="libpq-fastpath">
-   <primary>fast path</primary>
-  </indexterm>
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> provides a fast-path interface
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> provides a fast-path interface
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> provides a fast-path interface
-<!## end>
-   to send simple function calls to the server.
-  </para>
-
-  <tip>
-   <para>
-    This interface is somewhat obsolete, as one can achieve similar
-    performance and greater functionality by setting up a prepared
-    statement to define the function call.  Then, executing the statement
-    with binary transmission of parameters and results substitutes for a
-    fast-path function call.
-   </para>
-  </tip>
-
-  <para>
-   The function <function>PQfn</function><indexterm><primary>PQfn</></>
-   requests execution of a server function via the fast-path interface:
-<synopsis>
-PGresult *PQfn(PGconn *conn,
-               int fnid,
-               int *result_buf,
-               int *result_len,
-               int result_is_int,
-               const PQArgBlock *args,
-               int nargs);
-
-typedef struct
-{
-    int len;
-    int isint;
-    union
-    {
-        int *ptr;
-        int integer;
-    } u;
-} PQArgBlock;
-</synopsis>
-  </para>
-
-  <para>
-   The <parameter>fnid</> argument is the OID of the function to be
-   executed.  <parameter>args</> and <parameter>nargs</> define the
-   parameters to be passed to the function; they must match the declared
-   function argument list.  When the <parameter>isint</> field of a
-   parameter structure is true, the <parameter>u.integer</> value is sent
-   to the server as an integer of the indicated length (this must be 1,
-   2, or 4 bytes); proper byte-swapping occurs.  When <parameter>isint</>
-   is false, the indicated number of bytes at <parameter>*u.ptr</> are
-   sent with no processing; the data must be in the format expected by
-   the server for binary transmission of the function's argument data
-   type.  <parameter>result_buf</parameter> is the buffer in which to
-   place the return value.  The caller must  have  allocated sufficient
-   space to store the return value.  (There is no check!) The actual result
-   length will be returned in the integer pointed to  by
-   <parameter>result_len</parameter>.  If a 1, 2, or 4-byte integer result
-   is expected, set <parameter>result_is_int</parameter> to 1, otherwise
-   set it to 0.  Setting <parameter>result_is_int</parameter> to 1 causes
-   <application>libpq</> to byte-swap the value if necessary, so that it
-   is delivered as a proper <type>int</type> value for the client machine.
-   When <parameter>result_is_int</> is 0, the binary-format byte string
-   sent by the server is returned unmodified.
-  </para>
-
-  <para>
-   <function>PQfn</function> always returns a valid
-   <structname>PGresult</structname> pointer. The result status should be
-   checked before the result is used.   The caller is responsible for
-   freeing  the  <structname>PGresult</structname>  with
-   <function>PQclear</function> when it is no longer needed.
-  </para>
-
-  <para>
-   Note that it is not possible to handle null arguments, null results,
-   nor set-valued results when using this interface.
-  </para>
-
- </sect1>
-
- <sect1 id="libpq-notify">
-  <title>Asynchronous Notification</title>
-
-  <indexterm zone="libpq-notify">
-   <primary>NOTIFY</primary>
-   <secondary>in libpq</secondary>
-  </indexterm>
-
-<!## XC>
-&xconly;
-  <para>
-   <productname>Postgres-XC</> does not
-   support <command>NOTIFY</>, <command>LISTEN</>
-   and <command>UNLISTEN</> commands yet.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <productname>Postgres-XL</> does not
-   support <command>NOTIFY</>, <command>LISTEN</>
-   and <command>UNLISTEN</> commands yet.
-  </para>
-<!## end>
-<!## PG>
-  <para>
-   <productname>PostgreSQL</productname> offers asynchronous notification
-   via the <command>LISTEN</command> and <command>NOTIFY</command>
-   commands.  A client session registers its interest in a particular
-   notification channel with the <command>LISTEN</command> command (and
-   can stop listening with the <command>UNLISTEN</command> command).  All
-   sessions listening on a particular channel will be notified
-   asynchronously when a <command>NOTIFY</command> command with that
-   channel name is executed by any session. A <quote>payload</> string can
-   be passed to communicate additional data to the listeners.
-  </para>
-
-  <para>
-   <application>libpq</application> applications submit
-   <command>LISTEN</command>, <command>UNLISTEN</command>,
-   and <command>NOTIFY</command> commands as
-   ordinary SQL commands.  The arrival of <command>NOTIFY</command>
-   messages can subsequently be detected by calling
-   <function>PQnotifies</function>.<indexterm><primary>PQnotifies</></>
-  </para>
-
-  <para>
-   The function <function>PQnotifies</function> returns the next notification
-   from a list of unhandled notification messages received from the server.
-   It returns a null pointer if there are no pending notifications.  Once a
-   notification is returned from <function>PQnotifies</>, it is considered
-   handled and will be removed from the list of notifications.
-
-<synopsis>
-PGnotify *PQnotifies(PGconn *conn);
-
-typedef struct pgNotify
-{
-    char *relname;              /* notification channel name */
-    int  be_pid;                /* process ID of notifying server process */
-    char *extra;                /* notification payload string */
-} PGnotify;
-</synopsis>
-
-   After processing a <structname>PGnotify</structname> object returned
-   by <function>PQnotifies</function>, be sure to free it with
-   <function>PQfreemem</function>.  It is sufficient to free the
-   <structname>PGnotify</structname> pointer; the
-   <structfield>relname</structfield> and <structfield>extra</structfield>
-   fields do not represent separate allocations.  (The names of these fields
-   are historical; in particular, channel names need not have anything to
-   do with relation names.)
-  </para>
-
-  <para>
-   <xref linkend="libpq-example-2"> gives a sample program that illustrates
-   the use of asynchronous notification.
-  </para>
-
-  <para>
-   <function>PQnotifies</function> does not actually read data from the
-   server; it just returns messages previously absorbed by another
-   <application>libpq</application> function.  In prior releases of
-   <application>libpq</application>, the only way to ensure timely receipt
-   of <command>NOTIFY</> messages was to constantly submit commands, even
-   empty ones, and then check <function>PQnotifies</function> after each
-   <function>PQexec</function>.  While this still works, it is deprecated
-   as a waste of processing power.
-  </para>
-
-  <para>
-   A better way to check for <command>NOTIFY</> messages when you have no
-   useful commands to execute is to call
-   <function>PQconsumeInput</function>, then check
-   <function>PQnotifies</function>.  You can use
-   <function>select()</function> to wait for data to arrive from the
-   server, thereby using no <acronym>CPU</acronym> power unless there is
-   something to do.  (See <function>PQsocket</function> to obtain the file
-   descriptor number to use with <function>select()</function>.) Note that
-   this will work OK whether you submit commands with
-   <function>PQsendQuery</function>/<function>PQgetResult</function> or
-   simply use <function>PQexec</function>.  You should, however, remember
-   to check <function>PQnotifies</function> after each
-   <function>PQgetResult</function> or <function>PQexec</function>, to
-   see if any notifications came in during the processing of the command.
-  </para>
-
-<!## end>
- </sect1>
-
- <sect1 id="libpq-copy">
-  <title>Functions Associated with the <command>COPY</command> Command</title>
-
-  <indexterm zone="libpq-copy">
-   <primary>COPY</primary>
-   <secondary>with libpq</secondary>
-  </indexterm>
-&common;
-  <para>
-   The <command>COPY</command> command in
-<!## PG>
-   <productname>PostgreSQL</productname> has options to read from or write
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> has options to read from or write
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> has options to read from or write
-<!## end>
-   to the network connection used by <application>libpq</application>.
-   The functions described in this section allow applications to take
-   advantage of this capability by supplying or consuming copied data.
-  </para>
-
-  <para>
-   The overall process is that the application first issues the SQL
-   <command>COPY</command> command via <function>PQexec</function> or one
-   of the equivalent functions.  The response to this (if there is no
-   error in the command) will be a <structname>PGresult</> object bearing
-   a status code of <literal>PGRES_COPY_OUT</literal> or
-   <literal>PGRES_COPY_IN</literal> (depending on the specified copy
-   direction).  The application should then use the functions of this
-   section to receive or transmit data rows.  When the data transfer is
-   complete, another <structname>PGresult</> object is returned to indicate
-   success or failure of the transfer.  Its status will be
-   <literal>PGRES_COMMAND_OK</literal> for success or
-   <literal>PGRES_FATAL_ERROR</literal> if some problem was encountered.
-   At this point further SQL commands can be issued via
-   <function>PQexec</function>.  (It is not possible to execute other SQL
-   commands using the same connection while the <command>COPY</command>
-   operation is in progress.)
-  </para>
-
-  <para>
-   If a <command>COPY</command> command is issued via
-   <function>PQexec</function> in a string that could contain additional
-   commands, the application must continue fetching results via
-   <function>PQgetResult</> after completing the <command>COPY</command>
-   sequence.  Only when <function>PQgetResult</> returns
-   <symbol>NULL</symbol> is it certain that the <function>PQexec</function>
-   command string is done and it is safe to issue more commands.
-  </para>
-
-  <para>
-   The functions of this section should be executed only after obtaining
-   a result status of <literal>PGRES_COPY_OUT</literal> or
-   <literal>PGRES_COPY_IN</literal> from <function>PQexec</function> or
-   <function>PQgetResult</function>.
-  </para>
-
-  <para>
-   A <structname>PGresult</> object bearing one of these status values
-   carries some additional data about the <command>COPY</command> operation
-   that is starting.  This additional data is available using functions
-   that are also used in connection with query results:
-
-   <variablelist>
-    <varlistentry id="libpq-pqnfields-1">
-     <term>
-      <function>PQnfields</function>
-      <indexterm>
-       <primary>PQnfields</primary>
-       <secondary>with COPY</secondary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the number of columns (fields) to be copied.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqbinarytuples-1">
-     <term>
-      <function>PQbinaryTuples</function>
-      <indexterm>
-       <primary>PQbinaryTuples</primary>
-       <secondary>with COPY</secondary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       0 indicates the overall copy format is textual (rows separated by
-       newlines, columns separated by separator characters, etc).  1
-       indicates the overall copy format is binary.  See <xref
-       linkend="sql-copy"> for more information.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqfformat-1">
-     <term>
-      <function>PQfformat</function>
-      <indexterm>
-       <primary>PQfformat</primary>
-       <secondary>with COPY</secondary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the format code (0 for text, 1 for binary) associated with
-       each column of the copy operation.  The per-column format codes
-       will always be zero when the overall copy format is textual, but
-       the binary format can support both text and binary columns.
-       (However, as of the current implementation of <command>COPY</>,
-       only binary columns appear in a binary copy; so the per-column
-       formats always match the overall format at present.)
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <note>
-   <para>
-    These additional data values are only available when using protocol
-    3.0.  When using protocol 2.0, all these functions will return 0.
-   </para>
-  </note>
-
-  <sect2 id="libpq-copy-send">
-   <title>Functions for Sending <command>COPY</command> Data</title>
-&common;
-   <para>
-    These functions are used to send data during <literal>COPY FROM
-    STDIN</>.  They will fail if called when the connection is not in
-    <literal>COPY_IN</> state.
-   </para>
-
-   <variablelist>
-    <varlistentry id="libpq-pqputcopydata">
-     <term>
-      <function>PQputCopyData</function>
-      <indexterm>
-       <primary>PQputCopyData</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Sends data to the server during <literal>COPY_IN</> state.
-<synopsis>
-int PQputCopyData(PGconn *conn,
-                  const char *buffer,
-                  int nbytes);
-</synopsis>
-      </para>
-
-      <para>
-       Transmits the <command>COPY</command> data in the specified
-       <parameter>buffer</>, of length <parameter>nbytes</>, to the server.
-       The result is 1 if the data was sent, zero if it was not sent
-       because the attempt would block (this case is only possible if the
-       connection is in nonblocking mode), or -1 if an error occurred.
-       (Use <function>PQerrorMessage</function> to retrieve details if
-       the return value is -1.  If the value is zero, wait for write-ready
-       and try again.)
-      </para>
-
-      <para>
-       The application can divide the <command>COPY</command> data stream
-       into buffer loads of any convenient size.  Buffer-load boundaries
-       have no semantic significance when sending.  The contents of the
-       data stream must match the data format expected by the
-       <command>COPY</> command; see <xref linkend="sql-copy"> for details.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqputcopyend">
-     <term>
-      <function>PQputCopyEnd</function>
-      <indexterm>
-       <primary>PQputCopyEnd</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Sends end-of-data indication to the server during <literal>COPY_IN</> state.
-<synopsis>
-int PQputCopyEnd(PGconn *conn,
-                 const char *errormsg);
-</synopsis>
-      </para>
-
-      <para>
-       Ends the <literal>COPY_IN</> operation successfully if
-       <parameter>errormsg</> is <symbol>NULL</symbol>.  If
-       <parameter>errormsg</> is not <symbol>NULL</symbol> then the
-       <command>COPY</> is forced to fail, with the string pointed to by
-       <parameter>errormsg</> used as the error message.  (One should not
-       assume that this exact error message will come back from the server,
-       however, as the server might have already failed the
-       <command>COPY</> for its own reasons.  Also note that the option
-       to force failure does not work when using pre-3.0-protocol
-       connections.)
-      </para>
-
-      <para>
-       The result is 1 if the termination data was sent, zero if it was
-       not sent because the attempt would block (this case is only possible
-       if the connection is in nonblocking mode), or -1 if an error
-       occurred.  (Use <function>PQerrorMessage</function> to retrieve
-       details if the return value is -1.  If the value is zero, wait for
-       write-ready and try again.)
-      </para>
-
-      <para>
-       After successfully calling <function>PQputCopyEnd</>, call
-       <function>PQgetResult</> to obtain the final result status of the
-       <command>COPY</> command.  One can wait for this result to be
-       available in the usual way.  Then return to normal operation.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-  </sect2>
-
-  <sect2 id="libpq-copy-receive">
-   <title>Functions for Receiving <command>COPY</command> Data</title>
-&common;
-   <para>
-    These functions are used to receive data during <literal>COPY TO
-    STDOUT</>.  They will fail if called when the connection is not in
-    <literal>COPY_OUT</> state.
-   </para>
-
-   <variablelist>
-    <varlistentry id="libpq-pqgetcopydata">
-     <term>
-      <function>PQgetCopyData</function>
-      <indexterm>
-       <primary>PQgetCopyData</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Receives data from the server during <literal>COPY_OUT</> state.
-<synopsis>
-int PQgetCopyData(PGconn *conn,
-                  char **buffer,
-                  int async);
-</synopsis>
-      </para>
-
-      <para>
-       Attempts to obtain another row of data from the server during a
-       <command>COPY</command>.  Data is always returned one data row at
-       a time; if only a partial row is available, it is not returned.
-       Successful return of a data row involves allocating a chunk of
-       memory to hold the data.  The <parameter>buffer</> parameter must
-       be non-<symbol>NULL</symbol>.  <parameter>*buffer</> is set to
-       point to the allocated memory, or to <symbol>NULL</symbol> in cases
-       where no buffer is returned.  A non-<symbol>NULL</symbol> result
-       buffer should be freed using <function>PQfreemem</> when no longer
-       needed.
-      </para>
-
-      <para>
-       When a row is successfully returned, the return value is the number
-       of data bytes in the row (this will always be greater than zero).
-       The returned string is always null-terminated, though this is
-       probably only useful for textual <command>COPY</command>.  A result
-       of zero indicates that the <command>COPY</command> is still in
-       progress, but no row is yet available (this is only possible when
-       <parameter>async</> is true).  A result of -1 indicates that the
-       <command>COPY</command> is done.  A result of -2 indicates that an
-       error occurred (consult <function>PQerrorMessage</> for the reason).
-      </para>
-
-      <para>
-       When <parameter>async</> is true (not zero),
-       <function>PQgetCopyData</> will not block waiting for input; it
-       will return zero if the <command>COPY</command> is still in progress
-       but no complete row is available.  (In this case wait for read-ready
-       and then call <function>PQconsumeInput</> before calling
-       <function>PQgetCopyData</> again.)  When <parameter>async</> is
-       false (zero), <function>PQgetCopyData</> will block until data is
-       available or the operation completes.
-      </para>
-
-      <para>
-       After <function>PQgetCopyData</> returns -1, call
-       <function>PQgetResult</> to obtain the final result status of the
-       <command>COPY</> command.  One can wait for this result to be
-       available in the usual way.  Then return to normal operation.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-  </sect2>
-
-  <sect2 id="libpq-copy-deprecated">
-   <title>Obsolete Functions for <command>COPY</command></title>
-&common;
-   <para>
-    These functions represent older methods of handling <command>COPY</>.
-    Although they still work, they are deprecated due to poor error handling,
-    inconvenient methods of detecting end-of-data, and lack of support for binary
-    or nonblocking transfers.
-   </para>
-
-   <variablelist>
-    <varlistentry id="libpq-pqgetline">
-     <term>
-      <function>PQgetline</function>
-      <indexterm>
-       <primary>PQgetline</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Reads  a  newline-terminated  line  of  characters (transmitted
-       by the server) into a buffer string of size <parameter>length</>.
-<synopsis>
-int PQgetline(PGconn *conn,
-              char *buffer,
-              int length);
-</synopsis>
-      </para>
-
-      <para>
-       This function copies up to <parameter>length</>-1 characters into
-       the buffer and converts the terminating newline into a zero byte.
-       <function>PQgetline</function> returns <symbol>EOF</symbol> at the
-       end of input, 0 if the entire line has been read, and 1 if the
-       buffer is full but the terminating newline has not yet been read.
-       </para>
-       <para>
-       Note that the application must check to see if a new line consists
-       of  the  two characters  <literal>\.</literal>, which  indicates
-       that the server has finished sending the results  of  the
-       <command>COPY</command> command.  If  the  application might receive
-       lines that are more than <parameter>length</>-1  characters  long,
-       care is needed to be sure it recognizes the <literal>\.</literal>
-       line correctly (and does not, for example, mistake the end of a
-       long data line for a terminator line).
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqgetlineasync">
-     <term>
-      <function>PQgetlineAsync</function>
-      <indexterm>
-       <primary>PQgetlineAsync</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Reads a row of <command>COPY</command> data (transmitted  by the
-       server) into a buffer without blocking.
-<synopsis>
-int PQgetlineAsync(PGconn *conn,
-                   char *buffer,
-                   int bufsize);
-</synopsis>
-      </para>
-
-      <para>
-       This function is similar to <function>PQgetline</function>, but it can be used
-       by applications
-       that must read <command>COPY</command> data asynchronously, that is, without blocking.
-       Having issued the <command>COPY</command> command and gotten a <literal>PGRES_COPY_OUT</literal>
-       response, the
-       application should call <function>PQconsumeInput</function> and
-       <function>PQgetlineAsync</function> until the
-       end-of-data signal is detected.
-       </para>
-       <para>
-       Unlike <function>PQgetline</function>, this function takes
-       responsibility for detecting end-of-data.
-      </para>
-
-      <para>
-       On each call, <function>PQgetlineAsync</function> will return data if a
-       complete data row is available in <application>libpq</>'s input buffer.
-       Otherwise, no data is returned until the rest of the row arrives.
-       The function returns -1 if the end-of-copy-data marker has been recognized,
-       or 0 if no data is available, or a positive number giving the number of
-       bytes of data returned.  If -1 is returned, the caller must next call
-       <function>PQendcopy</function>, and then return to normal processing.
-      </para>
-
-      <para>
-       The data returned will not extend beyond a data-row boundary.  If possible
-       a whole row will be returned at one time.  But if the buffer offered by
-       the caller is too small to hold a row sent by the server, then a partial
-       data row will be returned.  With textual data this can be detected by testing
-       whether the last returned byte is <literal>\n</literal> or not.  (In a binary
-       <command>COPY</>, actual parsing of the <command>COPY</> data format will be needed to make the
-       equivalent determination.)
-       The returned string is not null-terminated.  (If you want to add a
-       terminating null, be sure to pass a <parameter>bufsize</parameter> one smaller
-       than the room actually available.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqputline">
-     <term>
-      <function>PQputline</function>
-      <indexterm>
-       <primary>PQputline</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Sends  a  null-terminated  string  to  the server.  Returns 0 if
-       OK and <symbol>EOF</symbol> if unable to send the string.
-<synopsis>
-int PQputline(PGconn *conn,
-              const char *string);
-</synopsis>
-      </para>
-
-      <para>
-       The <command>COPY</command> data stream sent by a series of calls
-       to <function>PQputline</function> has the same format as that
-       returned by <function>PQgetlineAsync</function>, except that
-       applications are not obliged to send exactly one data row per
-       <function>PQputline</function> call; it is okay to send a partial
-       line or multiple lines per call.
-      </para>
-
-      <note>
-       <para>
-        Before <productname>PostgreSQL</productname> protocol 3.0, it was necessary
-        for the application to explicitly send the two characters
-        <literal>\.</literal> as a final line to indicate to the server that it had
-        finished sending <command>COPY</> data.  While this still works, it is deprecated and the
-        special meaning of <literal>\.</literal> can be expected to be removed in a
-        future release.  It is sufficient to call <function>PQendcopy</function> after
-        having sent the actual data.
-       </para>
-      </note>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqputnbytes">
-     <term>
-      <function>PQputnbytes</function>
-      <indexterm>
-       <primary>PQputnbytes</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Sends  a  non-null-terminated  string  to  the server.  Returns
-       0 if OK and <symbol>EOF</symbol> if unable to send the string.
-<synopsis>
-int PQputnbytes(PGconn *conn,
-                const char *buffer,
-                int nbytes);
-</synopsis>
-      </para>
-
-      <para>
-       This is exactly like <function>PQputline</function>, except that the data
-       buffer need not be null-terminated since the number of bytes to send is
-       specified directly.  Use this procedure when sending binary data.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqendcopy">
-     <term>
-      <function>PQendcopy</function>
-      <indexterm>
-       <primary>PQendcopy</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Synchronizes with the server.
-<synopsis>
-int PQendcopy(PGconn *conn);
-</synopsis>
-       This function waits until the  server  has  finished  the copying.
-       It should either be issued when the  last  string  has  been sent
-       to  the  server using <function>PQputline</function> or when the
-       last string has been  received  from  the  server using
-       <function>PGgetline</function>.  It must be issued or the server
-       will get <quote>out of sync</quote> with  the client.   Upon return
-       from this function, the server is ready to receive the next SQL
-       command.  The return value is 0  on  successful  completion,
-       nonzero otherwise.  (Use <function>PQerrorMessage</function> to
-       retrieve details if the return value is nonzero.)
-      </para>
-
-      <para>
-       When using <function>PQgetResult</function>, the application should
-       respond to a <literal>PGRES_COPY_OUT</literal> result by executing
-       <function>PQgetline</function> repeatedly, followed by
-       <function>PQendcopy</function> after the terminator line is seen.
-       It should then return to the <function>PQgetResult</function> loop
-       until <function>PQgetResult</function> returns a null pointer.
-       Similarly a <literal>PGRES_COPY_IN</literal> result is processed
-       by a series of <function>PQputline</function> calls followed by
-       <function>PQendcopy</function>, then return to the
-       <function>PQgetResult</function> loop.  This arrangement will
-       ensure that a <command>COPY</command> command embedded in a series
-       of <acronym>SQL</acronym> commands will be executed correctly.
-      </para>
-
-      <para>
-       Older applications are likely to submit a <command>COPY</command>
-       via <function>PQexec</function> and assume that the transaction
-       is done after <function>PQendcopy</function>.  This will work
-       correctly only if the <command>COPY</command> is the only
-       <acronym>SQL</acronym> command in the command string.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="libpq-control">
-  <title>Control Functions</title>
-&common;
-  <para>
-   These functions control miscellaneous details of <application>libpq</>'s
-   behavior.
-  </para>
-
-  <variablelist>
-   <varlistentry id="libpq-pqclientencoding">
-    <term>
-     <function>PQclientEncoding</function>
-     <indexterm>
-      <primary>PQclientEncoding</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Returns the client encoding.
-<synopsis>
-int PQclientEncoding(const PGconn *<replaceable>conn</replaceable>);
-</synopsis>
-
-      Note that it returns the encoding ID, not a symbolic string
-      such as <literal>EUC_JP</literal>. To convert an encoding ID to an encoding name, you
-      can use:
-
-<synopsis>
-char *pg_encoding_to_char(int <replaceable>encoding_id</replaceable>);
-</synopsis>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqsetclientencoding">
-    <term>
-     <function>PQsetClientEncoding</function>
-     <indexterm>
-      <primary>PQsetClientEncoding</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Sets the client encoding.
-<synopsis>
-int PQsetClientEncoding(PGconn *<replaceable>conn</replaceable>, const char *<replaceable>encoding</replaceable>);
-</synopsis>
-
-      <replaceable>conn</replaceable> is a connection to the server,
-      and <replaceable>encoding</replaceable> is the encoding you want to
-      use. If the function successfully sets the encoding, it returns 0,
-      otherwise -1. The current encoding for this connection can be
-      determined by using <function>PQclientEncoding</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqseterrorverbosity">
-    <term>
-     <function>PQsetErrorVerbosity</function>
-     <indexterm>
-      <primary>PQsetErrorVerbosity</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Determines the verbosity of messages returned by
-      <function>PQerrorMessage</> and <function>PQresultErrorMessage</>.
-<synopsis>
-typedef enum
-{
-    PQERRORS_TERSE,
-    PQERRORS_DEFAULT,
-    PQERRORS_VERBOSE
-} PGVerbosity;
-
-PGVerbosity PQsetErrorVerbosity(PGconn *conn, PGVerbosity verbosity);
-</synopsis>
-
-      <function>PQsetErrorVerbosity</> sets the verbosity mode, returning
-      the connection's previous setting.  In <firstterm>TERSE</> mode,
-      returned messages include severity, primary text, and position only;
-      this will normally fit on a single line.  The default mode produces
-      messages that include the above plus any detail, hint, or context
-      fields (these might span multiple lines).  The <firstterm>VERBOSE</>
-      mode includes all available fields.  Changing the verbosity does not
-      affect the messages available from already-existing
-      <structname>PGresult</> objects, only subsequently-created ones.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqtrace">
-    <term>
-     <function>PQtrace</function>
-     <indexterm>
-      <primary>PQtrace</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Enables  tracing of the client/server communication to a debugging file stream.
-<synopsis>
-void PQtrace(PGconn *conn, FILE *stream);
-</synopsis>
-     </para>
-
-     <note>
-      <para>
-       On Windows, if the <application>libpq</> library and an application are
-       compiled with different flags, this function call will crash the
-       application because the internal representation of the <literal>FILE</>
-       pointers differ.  Specifically, multithreaded/single-threaded,
-       release/debug, and static/dynamic flags should be the same for the
-       library and all applications using that library.
-      </para>
-     </note>
-
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pquntrace">
-    <term>
-     <function>PQuntrace</function>
-     <indexterm>
-      <primary>PQuntrace</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Disables tracing started by <function>PQtrace</function>.
-<synopsis>
-void PQuntrace(PGconn *conn);
-</synopsis>
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
- </sect1>
-
- <sect1 id="libpq-misc">
-  <title>Miscellaneous Functions</title>
-&common;
-  <para>
-   As always, there are some functions that just don't fit anywhere.
-  </para>
-
-  <variablelist>
-   <varlistentry id="libpq-pqfreemem">
-    <term>
-     <function>PQfreemem</function>
-     <indexterm>
-      <primary>PQfreemem</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Frees memory allocated by <application>libpq</>.
-<synopsis>
-void PQfreemem(void *ptr);
-</synopsis>
-     </para>
-
-     <para>
-      Frees memory allocated by <application>libpq</>, particularly
-      <function>PQescapeByteaConn</function>,
-      <function>PQescapeBytea</function>,
-      <function>PQunescapeBytea</function>,
-      and <function>PQnotifies</function>.
-      It is particularly important that this function, rather than
-      <function>free()</>, be used on Microsoft Windows.  This is because
-      allocating memory in a DLL and releasing it in the application works
-      only if multithreaded/single-threaded, release/debug, and static/dynamic
-      flags are the same for the DLL and the application.  On non-Microsoft
-      Windows platforms, this function is the same as the standard library
-      function <function>free()</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqconninfofree">
-    <term>
-     <function>PQconninfoFree</function>
-     <indexterm>
-      <primary>PQconninfoFree</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Frees the data structures allocated by
-      <function>PQconndefaults</> or <function>PQconninfoParse</>.
-<synopsis>
-void PQconninfoFree(PQconninfoOption *connOptions);
-</synopsis>
-     </para>
-
-     <para>
-      A simple <function>PQfreemem</function> will not do for this, since
-      the array contains references to subsidiary strings.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqencryptpassword">
-    <term>
-     <function>PQencryptPassword</function>
-     <indexterm>
-      <primary>PQencryptPassword</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-<!## PG>
-      Prepares the encrypted form of a <productname>PostgreSQL</> password.
-<!## end>
-<!## XC>
-      Prepares the encrypted form of a <productname>Postgres-XC</> password.
-<!## end>
-<!## XL>
-      Prepares the encrypted form of a <productname>Postgres-XL</> password.
-<!## end>
-<synopsis>
-char * PQencryptPassword(const char *passwd, const char *user);
-</synopsis>
-      This function is intended to be used by client applications that
-      wish to send commands like <literal>ALTER USER OE PASSWORD
-      'pwd'</>.  It is good practice not to send the original cleartext
-      password in such a command, because it might be exposed in command
-      logs, activity displays, and so on.  Instead, use this function to
-      convert the password to encrypted form before it is sent.  The
-      arguments are the cleartext password, and the SQL name of the user
-      it is for.  The return value is a string allocated by
-      <function>malloc</function>, or <symbol>NULL</symbol> if out of
-      memory.  The caller can assume the string doesn't contain any
-      special characters that would require escaping.  Use
-      <function>PQfreemem</> to free the result when done with it.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqmakeemptypgresult">
-    <term>
-     <function>PQmakeEmptyPGresult</function>
-     <indexterm>
-      <primary>PQmakeEmptyPGresult</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Constructs an empty <structname>PGresult</structname> object with the given status.
-<synopsis>
-PGresult *PQmakeEmptyPGresult(PGconn *conn, ExecStatusType status);
-</synopsis>
-     </para>
-
-     <para>
-      This is <application>libpq</>'s internal function to allocate and
-      initialize an empty <structname>PGresult</structname> object.  This
-      function returns <symbol>NULL</> if memory could not be allocated. It is
-      exported because some applications find it useful to generate result
-      objects (particularly objects with error status) themselves.  If
-      <parameter>conn</parameter> is not null and <parameter>status</>
-      indicates an error, the current error message of the specified
-      connection is copied into the <structname>PGresult</structname>.
-      Also, if <parameter>conn</parameter> is not null, any event procedures
-      registered in the connection are copied into the
-      <structname>PGresult</structname>.  (They do not get
-      <literal>PGEVT_RESULTCREATE</> calls, but see
-      <function>PQfireResultCreateEvents</function>.)
-      Note that <function>PQclear</function> should eventually be called
-      on the object, just as with a <structname>PGresult</structname>
-      returned by <application>libpq</application> itself.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqfireresultcreateevents">
-    <term>
-     <function>PQfireResultCreateEvents</function>
-     <indexterm>
-      <primary>PQfireResultCreateEvents</primary>
-     </indexterm>
-    </term>
-    <listitem>
-     <para>
-      Fires a <literal>PGEVT_RESULTCREATE</literal> event (see <xref
-      linkend="libpq-events">) for each event procedure registered in the
-      <structname>PGresult</structname> object.  Returns non-zero for success,
-      zero if any event procedure fails.
-
-<synopsis>
-int PQfireResultCreateEvents(PGconn *conn, PGresult *res);
-</synopsis>
-     </para>
-
-     <para>
-      The <literal>conn</> argument is passed through to event procedures
-      but not used directly.  It can be <symbol>NULL</> if the event
-      procedures won't use it.
-     </para>
-
-     <para>
-      Event procedures that have already received a
-      <literal>PGEVT_RESULTCREATE</> or <literal>PGEVT_RESULTCOPY</> event
-      for this object are not fired again.
-     </para>
-
-     <para>
-      The main reason that this function is separate from
-      <function>PQmakeEmptyPGResult</function> is that it is often appropriate
-      to create a <structname>PGresult</structname> and fill it with data
-      before invoking the event procedures.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqcopyresult">
-    <term>
-     <function>PQcopyResult</function>
-     <indexterm>
-      <primary>PQcopyResult</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Makes a copy of a <structname>PGresult</structname> object.  The copy is
-      not linked to the source result in any way and
-      <function>PQclear</function> must be called when the copy is no longer
-      needed.  If the function fails, <symbol>NULL</> is returned.
-
-<synopsis>
-PGresult *PQcopyResult(const PGresult *src, int flags);
-</synopsis>
-     </para>
-
-     <para>
-      This is not intended to make an exact copy.  The returned result is
-      always put into <literal>PGRES_TUPLES_OK</literal> status, and does not
-      copy any error message in the source.  (It does copy the command status
-      string, however.)  The <parameter>flags</parameter> argument determines
-      what else is copied.  It is a bitwise OR of several flags.
-      <literal>PG_COPYRES_ATTRS</literal> specifies copying the source
-      result's attributes (column definitions).
-      <literal>PG_COPYRES_TUPLES</literal> specifies copying the source
-      result's tuples.  (This implies copying the attributes, too.)
-      <literal>PG_COPYRES_NOTICEHOOKS</literal> specifies
-      copying the source result's notify hooks.
-      <literal>PG_COPYRES_EVENTS</literal> specifies copying the source
-      result's events.  (But any instance data associated with the source
-      is not copied.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqsetresultattrs">
-    <term>
-     <function>PQsetResultAttrs</function>
-     <indexterm>
-      <primary>PQsetResultAttrs</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Sets the attributes of a <structname>PGresult</structname> object.
-<synopsis>
-int PQsetResultAttrs(PGresult *res, int numAttributes, PGresAttDesc *attDescs);
-</synopsis>
-     </para>
-
-     <para>
-      The provided <parameter>attDescs</parameter> are copied into the result.
-      If the <parameter>attDescs</parameter> pointer is <symbol>NULL</> or
-      <parameter>numAttributes</parameter> is less than one, the request is
-      ignored and the function succeeds.  If <parameter>res</parameter>
-      already contains attributes, the function will fail.  If the function
-      fails, the return value is zero.  If the function succeeds, the return
-      value is non-zero.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqsetvalue">
-    <term>
-     <function>PQsetvalue</function>
-     <indexterm>
-      <primary>PQsetvalue</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Sets a tuple field value of a <structname>PGresult</structname> object.
-<synopsis>
-int PQsetvalue(PGresult *res, int tup_num, int field_num, char *value, int len);
-</synopsis>
-     </para>
-
-     <para>
-      The function will automatically grow the result's internal tuples array
-      as needed.  However, the <parameter>tup_num</parameter> argument must be
-      less than or equal to <function>PQntuples</function>, meaning this
-      function can only grow the tuples array one tuple at a time.  But any
-      field of any existing tuple can be modified in any order.  If a value at
-      <parameter>field_num</parameter> already exists, it will be overwritten.
-      If <parameter>len</parameter> is -1 or
-      <parameter>value</parameter> is <symbol>NULL</>, the field value
-      will be set to an SQL null value.  The
-      <parameter>value</parameter> is copied into the result's private storage,
-      thus is no longer needed after the function
-      returns.  If the function fails, the return value is zero.  If the
-      function succeeds, the return value is non-zero.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqresultalloc">
-    <term>
-     <function>PQresultAlloc</function>
-     <indexterm>
-      <primary>PQresultAlloc</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Allocate subsidiary storage for a <structname>PGresult</structname> object.
-<synopsis>
-void *PQresultAlloc(PGresult *res, size_t nBytes);
-</synopsis>
-     </para>
-
-     <para>
-      Any memory allocated with this function will be freed when
-      <parameter>res</parameter> is cleared.  If the function fails,
-      the return value is <symbol>NULL</>.  The result is
-      guaranteed to be adequately aligned for any type of data,
-      just as for <function>malloc</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="libpq-pqlibversion">
-    <term>
-     <function>PQlibVersion</function>
-     <indexterm>
-      <primary>PQlibVersion</primary>
-      <seealso>PQserverVersion</seealso>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Return the version of <productname>libpq</> that is being used.
-<synopsis>
-int PQlibVersion(void);
-</synopsis>
-     </para>
-
-     <para>
-      The result of this function can be used to determine, at
-      run time, if specific functionality is available in the currently
-      loaded version of libpq. The function can be used, for example,
-      to determine which connection options are available for
-      <function>PQconnectdb</> or if the <literal>hex</> <type>bytea</>
-      output added in PostgreSQL 9.0 is supported.
-     </para>
-
-     <para>
-      The number is formed by converting the major, minor, and revision
-      numbers into two-decimal-digit numbers and appending them together.
-      For example, version 9.1 will be returned as 90100, and version
-      9.1.2 will be returned as 90102 (leading zeroes are not shown).
-     </para>
-
-     <note>
-      <para>
-       This function appeared in <productname>PostgreSQL</> version 9.1, so
-       it cannot be used to detect required functionality in earlier
-       versions, since linking to it will create a link dependency
-       on version 9.1.
-      </para>
-     </note>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
- </sect1>
-
- <sect1 id="libpq-notice-processing">
-  <title>Notice Processing</title>
-
-  <indexterm zone="libpq-notice-processing">
-   <primary>notice processing</primary>
-   <secondary>in libpq</secondary>
-  </indexterm>
-&common;
-  <para>
-   Notice and warning messages generated by the server are not returned
-   by the query execution functions, since they do not imply failure of
-   the query.  Instead they are passed to a notice handling function, and
-   execution continues normally after the handler returns.  The default
-   notice handling function prints the message on
-   <filename>stderr</filename>, but the application can override this
-   behavior by supplying its own handling function.
-  </para>
-
-  <para>
-   For historical reasons, there are two levels of notice handling, called
-   the notice receiver and notice processor.  The default behavior is for
-   the notice receiver to format the notice and pass a string to the notice
-   processor for printing.  However, an application that chooses to provide
-   its own notice receiver will typically ignore the notice processor
-   layer and just do all the work in the notice receiver.
-  </para>
-
-  <para>
-   The function <function>PQsetNoticeReceiver</function>
-   <indexterm><primary>notice receiver</></>
-   <indexterm><primary>PQsetNoticeReceiver</></> sets or
-   examines the current notice receiver for a connection object.
-   Similarly, <function>PQsetNoticeProcessor</function>
-   <indexterm><primary>notice processor</></>
-   <indexterm><primary>PQsetNoticeProcessor</></> sets or
-   examines the current notice processor.
-
-<synopsis>
-typedef void (*PQnoticeReceiver) (void *arg, const PGresult *res);
-
-PQnoticeReceiver
-PQsetNoticeReceiver(PGconn *conn,
-                    PQnoticeReceiver proc,
-                    void *arg);
-
-typedef void (*PQnoticeProcessor) (void *arg, const char *message);
-
-PQnoticeProcessor
-PQsetNoticeProcessor(PGconn *conn,
-                     PQnoticeProcessor proc,
-                     void *arg);
-</synopsis>
-
-   Each of these functions returns the previous notice receiver or
-   processor function pointer, and sets the new value.  If you supply a
-   null function pointer, no action is taken, but the current pointer is
-   returned.
-  </para>
-
-  <para>
-   When a notice or warning message is received from the server, or
-   generated internally by <application>libpq</application>, the notice
-   receiver function is called.  It is passed the message in the form of
-   a <symbol>PGRES_NONFATAL_ERROR</symbol>
-   <structname>PGresult</structname>.  (This allows the receiver to extract
-   individual fields using <function>PQresultErrorField</>, or the complete
-   preformatted message using <function>PQresultErrorMessage</>.) The same
-   void pointer passed to <function>PQsetNoticeReceiver</function> is also
-   passed.  (This pointer can be used to access application-specific state
-   if needed.)
-  </para>
-
-  <para>
-   The default notice receiver simply extracts the message (using
-   <function>PQresultErrorMessage</>) and passes it to the notice
-   processor.
-  </para>
-
-  <para>
-   The notice processor is responsible for handling a notice or warning
-   message given in text form.  It is passed the string text of the message
-   (including a trailing newline), plus a void pointer that is the same
-   one passed to <function>PQsetNoticeProcessor</function>.  (This pointer
-   can be used to access application-specific state if needed.)
-  </para>
-
-  <para>
-   The default notice processor is simply:
-<programlisting>
-static void
-defaultNoticeProcessor(void *arg, const char *message)
-{
-    fprintf(stderr, "%s", message);
-}
-</programlisting>
-  </para>
-
-  <para>
-   Once you have set a notice receiver or processor, you should expect
-   that that function could be called as long as either the
-   <structname>PGconn</> object or <structname>PGresult</> objects made
-   from it exist.  At creation of a <structname>PGresult</>, the
-   <structname>PGconn</>'s current notice handling pointers are copied
-   into the <structname>PGresult</> for possible use by functions like
-   <function>PQgetvalue</function>.
-  </para>
-
- </sect1>
-
- <sect1 id="libpq-events">
-  <title>Event System</title>
-&common;
-  <para>
-   <application>libpq</application>'s event system is designed to notify
-   registered event handlers about interesting
-   <application>libpq</application> events, such as the creation or
-   destruction of <structname>PGconn</structname> and
-   <structname>PGresult</structname> objects.  A principal use case is that
-   this allows applications to associate their own data with a
-   <structname>PGconn</structname> or <structname>PGresult</structname>
-   and ensure that that data is freed at an appropriate time.
-  </para>
-
-  <para>
-   Each registered event handler is associated with two pieces of data,
-   known to <application>libpq</application> only as opaque <literal>void *</>
-   pointers.  There is a <firstterm>passthrough</> pointer that is provided
-   by the application when the event handler is registered with a
-   <structname>PGconn</>.  The passthrough pointer never changes for the
-   life of the <structname>PGconn</> and all <structname>PGresult</>s
-   generated from it; so if used, it must point to long-lived data.
-   In addition there is an <firstterm>instance data</> pointer, which starts
-   out <symbol>NULL</> in every <structname>PGconn</> and <structname>PGresult</>.
-   This pointer can be manipulated using the
-   <function>PQinstanceData</function>,
-   <function>PQsetInstanceData</function>,
-   <function>PQresultInstanceData</function> and
-   <function>PQsetResultInstanceData</function> functions.  Note that
-   unlike the passthrough pointer, instance data of a <structname>PGconn</>
-   is not automatically inherited by <structname>PGresult</>s created from
-   it.  <application>libpq</application> does not know what passthrough
-   and instance data pointers point to (if anything) and will never attempt
-   to free them &mdash; that is the responsibility of the event handler.
-  </para>
-
-  <sect2 id="libpq-events-types">
-   <title>Event Types</title>
-&common;
-   <para>
-    The enum <literal>PGEventId</> names the types of events handled by
-    the event system.  All its values have names beginning with
-    <literal>PGEVT</literal>.  For each event type, there is a corresponding
-    event info structure that carries the parameters passed to the event
-    handlers.  The event types are:
-   </para>
-
-   <variablelist>
-    <varlistentry id="libpq-pgevt-register">
-     <term><literal>PGEVT_REGISTER</literal></term>
-     <listitem>
-      <para>
-       The register event occurs when <function>PQregisterEventProc</function>
-       is called.  It is the ideal time to initialize any
-       <literal>instanceData</literal> an event procedure may need.  Only one
-       register event will be fired per event handler per connection.  If the
-       event procedure fails, the registration is aborted.
-
-<synopsis>
-typedef struct
-{
-    PGconn *conn;
-} PGEventRegister;
-</synopsis>
-
-       When a <literal>PGEVT_REGISTER</literal> event is received, the
-       <parameter>evtInfo</parameter> pointer should be cast to a
-       <structname>PGEventRegister *</structname>.  This structure contains a
-       <structname>PGconn</structname> that should be in the
-       <literal>CONNECTION_OK</literal> status; guaranteed if one calls
-       <function>PQregisterEventProc</function> right after obtaining a good
-       <structname>PGconn</structname>.  When returning a failure code, all
-       cleanup must be performed as no <literal>PGEVT_CONNDESTROY</literal>
-       event will be sent.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pgevt-connreset">
-     <term><literal>PGEVT_CONNRESET</literal></term>
-     <listitem>
-      <para>
-       The connection reset event is fired on completion of
-       <function>PQreset</function> or <function>PQresetPoll</function>.  In
-       both cases, the event is only fired if the reset was successful.  If
-       the event procedure fails, the entire connection reset will fail; the
-       <structname>PGconn</structname> is put into
-       <literal>CONNECTION_BAD</literal> status and
-       <function>PQresetPoll</function> will return
-       <literal>PGRES_POLLING_FAILED</literal>.
-
-<synopsis>
-typedef struct
-{
-    PGconn *conn;
-} PGEventConnReset;
-</synopsis>
-
-       When a <literal>PGEVT_CONNRESET</literal> event is received, the
-       <parameter>evtInfo</parameter> pointer should be cast to a
-       <structname>PGEventConnReset *</structname>.  Although the contained
-       <structname>PGconn</structname> was just reset, all event data remains
-       unchanged.  This event should be used to reset/reload/requery any
-       associated <literal>instanceData</literal>.  Note that even if the
-       event procedure fails to process <literal>PGEVT_CONNRESET</>, it will
-       still receive a <literal>PGEVT_CONNDESTROY</> event when the connection
-       is closed.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pgevt-conndestroy">
-     <term><literal>PGEVT_CONNDESTROY</literal></term>
-     <listitem>
-      <para>
-       The connection destroy event is fired in response to
-       <function>PQfinish</function>.  It is the event procedure's
-       responsibility to properly clean up its event data as libpq has no
-       ability to manage this memory.  Failure to clean up will lead
-       to memory leaks.
-
-<synopsis>
-typedef struct
-{
-    PGconn *conn;
-} PGEventConnDestroy;
-</synopsis>
-
-       When a <literal>PGEVT_CONNDESTROY</literal> event is received, the
-       <parameter>evtInfo</parameter> pointer should be cast to a
-       <structname>PGEventConnDestroy *</structname>.  This event is fired
-       prior to <function>PQfinish</function> performing any other cleanup.
-       The return value of the event procedure is ignored since there is no
-       way of indicating a failure from <function>PQfinish</function>.  Also,
-       an event procedure failure should not abort the process of cleaning up
-       unwanted memory.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pgevt-resultcreate">
-     <term><literal>PGEVT_RESULTCREATE</literal></term>
-     <listitem>
-      <para>
-       The result creation event is fired in response to any query execution
-       function that generates a result, including
-       <function>PQgetResult</function>.  This event will only be fired after
-       the result has been created successfully.
-
-<synopsis>
-typedef struct
-{
-    PGconn *conn;
-    PGresult *result;
-} PGEventResultCreate;
-</synopsis>
-
-       When a <literal>PGEVT_RESULTCREATE</literal> event is received, the
-       <parameter>evtInfo</parameter> pointer should be cast to a
-       <structname>PGEventResultCreate *</structname>.  The
-       <parameter>conn</parameter> is the connection used to generate the
-       result.  This is the ideal place to initialize any
-       <literal>instanceData</literal> that needs to be associated with the
-       result.  If the event procedure fails, the result will be cleared and
-       the failure will be propagated.  The event procedure must not try to
-       <function>PQclear</> the result object for itself.  When returning a
-       failure code, all cleanup must be performed as no
-       <literal>PGEVT_RESULTDESTROY</literal> event will be sent.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pgevt-resultcopy">
-     <term><literal>PGEVT_RESULTCOPY</literal></term>
-     <listitem>
-      <para>
-       The result copy event is fired in response to
-       <function>PQcopyResult</function>.  This event will only be fired after
-       the copy is complete.  Only event procedures that have
-       successfully handled the <literal>PGEVT_RESULTCREATE</literal>
-       or <literal>PGEVT_RESULTCOPY</literal> event for the source result
-       will receive <literal>PGEVT_RESULTCOPY</literal> events.
-
-<synopsis>
-typedef struct
-{
-    const PGresult *src;
-    PGresult *dest;
-} PGEventResultCopy;
-</synopsis>
-
-       When a <literal>PGEVT_RESULTCOPY</literal> event is received, the
-       <parameter>evtInfo</parameter> pointer should be cast to a
-       <structname>PGEventResultCopy *</structname>.  The
-       <parameter>src</parameter> result is what was copied while the
-       <parameter>dest</parameter> result is the copy destination.  This event
-       can be used to provide a deep copy of <literal>instanceData</literal>,
-       since <literal>PQcopyResult</literal> cannot do that.  If the event
-       procedure fails, the entire copy operation will fail and the
-       <parameter>dest</parameter> result will be cleared.   When returning a
-       failure code, all cleanup must be performed as no
-       <literal>PGEVT_RESULTDESTROY</literal> event will be sent for the
-       destination result.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pgevt-resultdestroy">
-     <term><literal>PGEVT_RESULTDESTROY</literal></term>
-     <listitem>
-      <para>
-       The result destroy event is fired in response to a
-       <function>PQclear</function>.  It is the event procedure's
-       responsibility to properly clean up its event data as libpq has no
-       ability to manage this memory.  Failure to clean up will lead
-       to memory leaks.
-
-<synopsis>
-typedef struct
-{
-    PGresult *result;
-} PGEventResultDestroy;
-</synopsis>
-
-       When a <literal>PGEVT_RESULTDESTROY</literal> event is received, the
-       <parameter>evtInfo</parameter> pointer should be cast to a
-       <structname>PGEventResultDestroy *</structname>.  This event is fired
-       prior to <function>PQclear</function> performing any other cleanup.
-       The return value of the event procedure is ignored since there is no
-       way of indicating a failure from <function>PQclear</function>.  Also,
-       an event procedure failure should not abort the process of cleaning up
-       unwanted memory.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </sect2>
-
-  <sect2 id="libpq-events-proc">
-   <title>Event Callback Procedure</title>
-&common;
-   <variablelist>
-    <varlistentry id="libpq-pgeventproc">
-     <term>
-      <literal>PGEventProc</literal>
-      <indexterm>
-       <primary>PGEventProc</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       <literal>PGEventProc</literal> is a typedef for a pointer to an
-       event procedure, that is, the user callback function that receives
-       events from libpq.  The signature of an event procedure must be
-
-<synopsis>
-int eventproc(PGEventId evtId, void *evtInfo, void *passThrough)
-</synopsis>
-
-       The <parameter>evtId</parameter> parameter indicates which
-       <literal>PGEVT</literal> event occurred.  The
-       <parameter>evtInfo</parameter> pointer must be cast to the appropriate
-       structure type to obtain further information about the event.
-       The <parameter>passThrough</parameter> parameter is the pointer
-       provided to <function>PQregisterEventProc</function> when the event
-       procedure was registered.  The function should return a non-zero value
-       if it succeeds and zero if it fails.
-      </para>
-
-      <para>
-       A particular event procedure can be registered only once in any
-       <structname>PGconn</>.  This is because the address of the procedure
-       is used as a lookup key to identify the associated instance data.
-      </para>
-
-      <caution>
-       <para>
-        On Windows, functions can have two different addresses: one visible
-        from outside a DLL and another visible from inside the DLL.  One
-        should be careful that only one of these addresses is used with
-        <application>libpq</>'s event-procedure functions, else confusion will
-        result.  The simplest rule for writing code that will work is to
-        ensure that event procedures are declared <literal>static</>.  If the
-        procedure's address must be available outside its own source file,
-        expose a separate function to return the address.
-       </para>
-      </caution>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </sect2>
-
-  <sect2 id="libpq-events-funcs">
-   <title>Event Support Functions</title>
-&common;
-    <variablelist>
-    <varlistentry id="libpq-pqregistereventproc">
-     <term>
-      <function>PQregisterEventProc</function>
-      <indexterm>
-       <primary>PQregisterEventProc</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Registers an event callback procedure with libpq.
-
-<synopsis>
-int PQregisterEventProc(PGconn *conn, PGEventProc proc,
-                        const char *name, void *passThrough);
-</synopsis>
-      </para>
-
-      <para>
-       An event procedure must be registered once on each
-       <structname>PGconn</> you want to receive events about.  There is no
-       limit, other than memory, on the number of event procedures that
-       can be registered with a connection.  The function returns a non-zero
-       value if it succeeds and zero if it fails.
-      </para>
-
-      <para>
-       The <parameter>proc</parameter> argument will be called when a libpq
-       event is fired.  Its memory address is also used to lookup
-       <literal>instanceData</literal>.  The <parameter>name</parameter>
-       argument is used to refer to the event procedure in error messages.
-       This value cannot be <symbol>NULL</> or a zero-length string.  The name string is
-       copied into the <structname>PGconn</>, so what is passed need not be
-       long-lived.  The <parameter>passThrough</parameter> pointer is passed
-       to the <parameter>proc</parameter> whenever an event occurs. This
-       argument can be <symbol>NULL</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqsetinstancedata">
-     <term>
-      <function>PQsetInstanceData</function>
-      <indexterm>
-       <primary>PQsetInstanceData</primary>
-      </indexterm>
-     </term>
-     <listitem>
-      <para>
-       Sets the connection <parameter>conn</>'s <literal>instanceData</>
-       for procedure <parameter>proc</> to <parameter>data</>.  This
-       returns non-zero for success and zero for failure.  (Failure is
-       only possible if <parameter>proc</> has not been properly
-       registered in <parameter>conn</>.)
-
-<synopsis>
-int PQsetInstanceData(PGconn *conn, PGEventProc proc, void *data);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqinstancedata">
-     <term>
-      <function>PQinstanceData</function>
-      <indexterm>
-       <primary>PQinstanceData</primary>
-      </indexterm>
-     </term>
-     <listitem>
-      <para>
-       Returns the
-       connection <parameter>conn</>'s <literal>instanceData</literal>
-       associated with procedure <parameter>proc</>,
-       or <symbol>NULL</symbol> if there is none.
-
-<synopsis>
-void *PQinstanceData(const PGconn *conn, PGEventProc proc);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqresultsetinstancedata">
-     <term>
-      <function>PQresultSetInstanceData</function>
-      <indexterm>
-       <primary>PQresultSetInstanceData</primary>
-      </indexterm>
-     </term>
-     <listitem>
-      <para>
-       Sets the result's <literal>instanceData</>
-       for <parameter>proc</> to <parameter>data</>.  This returns
-       non-zero for success and zero for failure.  (Failure is only
-       possible if <parameter>proc</> has not been properly registered
-       in the result.)
-
-<synopsis>
-int PQresultSetInstanceData(PGresult *res, PGEventProc proc, void *data);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqresultinstancedata">
-     <term>
-      <function>PQresultInstanceData</function>
-      <indexterm>
-       <primary>PQresultInstanceData</primary>
-      </indexterm>
-     </term>
-     <listitem>
-      <para>
-       Returns the result's <literal>instanceData</> associated with <parameter>proc</>, or <symbol>NULL</>
-       if there is none.
-
-<synopsis>
-void *PQresultInstanceData(const PGresult *res, PGEventProc proc);
-</synopsis>
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </sect2>
-
-  <sect2 id="libpq-events-example">
-   <title>Event Example</title>
-&common;
-   <para>
-    Here is a skeleton example of managing private data associated with
-    libpq connections and results.
-   </para>
-
-<programlisting>
-<![CDATA[
-/* required header for libpq events (note: includes libpq-fe.h) */
-#include <libpq-events.h>
-
-/* The instanceData */
-typedef struct
-{
-    int n;
-    char *str;
-} mydata;
-
-/* PGEventProc */
-static int myEventProc(PGEventId evtId, void *evtInfo, void *passThrough);
-
-int
-main(void)
-{
-    mydata *data;
-    PGresult *res;
-    PGconn *conn = PQconnectdb("dbname = postgres");
-
-    if (PQstatus(conn) != CONNECTION_OK)
-    {
-        fprintf(stderr, "Connection to database failed: %s",
-                PQerrorMessage(conn));
-        PQfinish(conn);
-        return 1;
-    }
-
-    /* called once on any connection that should receive events.
-     * Sends a PGEVT_REGISTER to myEventProc.
-     */
-    if (!PQregisterEventProc(conn, myEventProc, "mydata_proc", NULL))
-    {
-        fprintf(stderr, "Cannot register PGEventProc\n");
-        PQfinish(conn);
-        return 1;
-    }
-
-    /* conn instanceData is available */
-    data = PQinstanceData(conn, myEventProc);
-
-    /* Sends a PGEVT_RESULTCREATE to myEventProc */
-    res = PQexec(conn, "SELECT 1 + 1");
-
-    /* result instanceData is available */
-    data = PQresultInstanceData(res, myEventProc);
-
-    /* If PG_COPYRES_EVENTS is used, sends a PGEVT_RESULTCOPY to myEventProc */
-    res_copy = PQcopyResult(res, PG_COPYRES_TUPLES | PG_COPYRES_EVENTS);
-
-    /* result instanceData is available if PG_COPYRES_EVENTS was
-     * used during the PQcopyResult call.
-     */
-    data = PQresultInstanceData(res_copy, myEventProc);
-
-    /* Both clears send a PGEVT_RESULTDESTROY to myEventProc */
-    PQclear(res);
-    PQclear(res_copy);
-
-    /* Sends a PGEVT_CONNDESTROY to myEventProc */
-    PQfinish(conn);
-
-    return 0;
-}
-
-static int
-myEventProc(PGEventId evtId, void *evtInfo, void *passThrough)
-{
-    switch (evtId)
-    {
-        case PGEVT_REGISTER:
-        {
-            PGEventRegister *e = (PGEventRegister *)evtInfo;
-            mydata *data = get_mydata(e->conn);
-
-            /* associate app specific data with connection */
-            PQsetInstanceData(e->conn, myEventProc, data);
-            break;
-        }
-
-        case PGEVT_CONNRESET:
-        {
-            PGEventConnReset *e = (PGEventConnReset *)evtInfo;
-            mydata *data = PQinstanceData(e->conn, myEventProc);
-
-            if (data)
-              memset(data, 0, sizeof(mydata));
-            break;
-        }
-
-        case PGEVT_CONNDESTROY:
-        {
-            PGEventConnDestroy *e = (PGEventConnDestroy *)evtInfo;
-            mydata *data = PQinstanceData(e->conn, myEventProc);
-
-            /* free instance data because the conn is being destroyed */
-            if (data)
-              free_mydata(data);
-            break;
-        }
-
-        case PGEVT_RESULTCREATE:
-        {
-            PGEventResultCreate *e = (PGEventResultCreate *)evtInfo;
-            mydata *conn_data = PQinstanceData(e->conn, myEventProc);
-            mydata *res_data = dup_mydata(conn_data);
-
-            /* associate app specific data with result (copy it from conn) */
-            PQsetResultInstanceData(e->result, myEventProc, res_data);
-            break;
-        }
-
-        case PGEVT_RESULTCOPY:
-        {
-            PGEventResultCopy *e = (PGEventResultCopy *)evtInfo;
-            mydata *src_data = PQresultInstanceData(e->src, myEventProc);
-            mydata *dest_data = dup_mydata(src_data);
-
-            /* associate app specific data with result (copy it from a result) */
-            PQsetResultInstanceData(e->dest, myEventProc, dest_data);
-            break;
-        }
-
-        case PGEVT_RESULTDESTROY:
-        {
-            PGEventResultDestroy *e = (PGEventResultDestroy *)evtInfo;
-            mydata *data = PQresultInstanceData(e->result, myEventProc);
-
-            /* free instance data because the result is being destroyed */
-            if (data)
-              free_mydata(data);
-            break;
-        }
-
-        /* unknown event id, just return TRUE. */
-        default:
-            break;
-    }
-
-    return TRUE; /* event processing succeeded */
-}
-]]>
-</programlisting>
-  </sect2>
- </sect1>
-
- <sect1 id="libpq-envars">
-  <title>Environment Variables</title>
-
-  <indexterm zone="libpq-envars">
-   <primary>environment variable</primary>
-  </indexterm>
-&common;
-  <para>
-   The following environment variables can be used to select default
-   connection parameter values, which will be used by
-   <function>PQconnectdb</>, <function>PQsetdbLogin</> and
-   <function>PQsetdb</> if no value is directly specified by the calling
-   code.  These are useful to avoid hard-coding database connection
-   information into simple client applications, for example.
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGHOST</envar></primary>
-      </indexterm>
-      <envar>PGHOST</envar> behaves the same as the <xref
-      linkend="libpq-connect-host"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGHOSTADDR</envar></primary>
-      </indexterm>
-      <envar>PGHOSTADDR</envar> behaves the same as the <xref
-      linkend="libpq-connect-hostaddr"> connection parameter.
-      This can be set instead of or in addition to <envar>PGHOST</envar>
-      to avoid DNS lookup overhead.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGPORT</envar></primary>
-      </indexterm>
-      <envar>PGPORT</envar> behaves the same as the <xref
-      linkend="libpq-connect-port"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGDATABASE</envar></primary>
-      </indexterm>
-      <envar>PGDATABASE</envar> behaves the same as the <xref
-      linkend="libpq-connect-dbname"> connection parameter.
-      </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGUSER</envar></primary>
-      </indexterm>
-      <envar>PGUSER</envar> behaves the same as the <xref
-      linkend="libpq-connect-user"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGPASSWORD</envar></primary>
-      </indexterm>
-      <envar>PGPASSWORD</envar> behaves the same as the <xref
-      linkend="libpq-connect-password"> connection parameter.
-      Use of this environment variable
-      is not recommended for security reasons, as some operating systems
-      allow non-root users to see process environment variables via
-      <application>ps</>; instead consider using the
-      <filename>~/.pgpass</> file (see <xref linkend="libpq-pgpass">).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGPASSFILE</envar></primary>
-      </indexterm>
-      <envar>PGPASSFILE</envar> specifies the name of the password file to
-      use for lookups.  If not set, it defaults to <filename>~/.pgpass</>
-      (see <xref linkend="libpq-pgpass">).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGSERVICE</envar></primary>
-      </indexterm>
-      <envar>PGSERVICE</envar> behaves the same as the <xref
-      linkend="libpq-connect-service"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGSERVICEFILE</envar></primary>
-      </indexterm>
-      <envar>PGSERVICEFILE</envar> specifies the name of the per-user
-      connection service file.  If not set, it defaults
-      to <filename>~/.pg_service.conf</>
-      (see <xref linkend="libpq-pgservice">).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGREALM</envar></primary>
-      </indexterm>
-      <envar>PGREALM</envar> sets the Kerberos realm to use with
-<!## PG>
-      <productname>PostgreSQL</productname>, if  it is different from the
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname>, if  it is different from the
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname>, if  it is different from the
-<!## end>
-      local realm.  If <envar>PGREALM</envar> is set,
-      <application>libpq</application> applications will attempt
-      authentication  with  servers for this realm and use separate ticket
-      files to avoid conflicts with local ticket files.   This
-      environment  variable is only used if Kerberos authentication is
-      selected by the server.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGOPTIONS</envar></primary>
-      </indexterm>
-      <envar>PGOPTIONS</envar> behaves the same as the <xref
-      linkend="libpq-connect-options"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGAPPNAME</envar></primary>
-      </indexterm>
-      <envar>PGAPPNAME</envar> behaves the same as the <xref
-      linkend="libpq-connect-application-name"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGSSLMODE</envar></primary>
-      </indexterm>
-      <envar>PGSSLMODE</envar> behaves the same as the <xref
-      linkend="libpq-connect-sslmode"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGREQUIRESSL</envar></primary>
-      </indexterm>
-      <envar>PGREQUIRESSL</envar> behaves the same as the <xref
-      linkend="libpq-connect-requiressl"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGSSLCERT</envar></primary>
-      </indexterm>
-      <envar>PGSSLCERT</envar> behaves the same as the <xref
-      linkend="libpq-connect-sslcert"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGSSLKEY</envar></primary>
-      </indexterm>
-      <envar>PGSSLKEY</envar> behaves the same as the <xref
-      linkend="libpq-connect-sslkey"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGSSLROOTCERT</envar></primary>
-      </indexterm>
-      <envar>PGSSLROOTCERT</envar>  behaves the same as the <xref
-      linkend="libpq-connect-sslrootcert"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGSSLCRL</envar></primary>
-      </indexterm>
-      <envar>PGSSLCRL</envar>  behaves the same as the <xref
-      linkend="libpq-connect-sslcrl"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGREQUIREPEER</envar></primary>
-      </indexterm>
-      <envar>PGREQUIREPEER</envar> behaves the same as the <xref
-      linkend="libpq-connect-requirepeer"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGKRBSRVNAME</envar></primary>
-      </indexterm>
-      <envar>PGKRBSRVNAME</envar>  behaves the same as the <xref
-      linkend="libpq-connect-krbsrvname"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGGSSLIB</envar></primary>
-      </indexterm>
-      <envar>PGGSSLIB</envar> behaves the same as the <xref
-      linkend="libpq-connect-gsslib"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGCONNECT_TIMEOUT</envar></primary>
-      </indexterm>
-      <envar>PGCONNECT_TIMEOUT</envar>  behaves the same as the <xref
-      linkend="libpq-connect-connect-timeout"> connection parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGCLIENTENCODING</envar></primary>
-      </indexterm>
-      <envar>PGCLIENTENCODING</envar> behaves the same as the <xref
-      linkend="libpq-connect-client-encoding"> connection parameter.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   The following environment variables can be used to specify default
-   behavior for each <productname>PostgreSQL</productname> session.  (See
-   also the <xref linkend="sql-alterrole">
-   and <xref linkend="sql-alterdatabase">
-   commands for ways to set default behavior on a per-user or per-database
-   basis.)
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGDATESTYLE</envar></primary>
-      </indexterm>
-      <envar>PGDATESTYLE</envar> sets the default style of date/time
-      representation.  (Equivalent to <literal>SET datestyle TO
-      ...</literal>.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGTZ</envar></primary>
-      </indexterm>
-      <envar>PGTZ</envar> sets the default time zone.  (Equivalent to
-      <literal>SET timezone TO ...</literal>.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGGEQO</envar></primary>
-      </indexterm>
-      <envar>PGGEQO</envar> sets the default mode for the genetic query
-      optimizer.  (Equivalent to <literal>SET geqo TO ...</literal>.)
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   Refer to the <acronym>SQL</acronym> command <xref linkend="sql-set">
-   for information on correct values for these
-   environment variables.
-  </para>
-
-  <para>
-   The following environment variables determine internal behavior of
-   <application>libpq</application>; they override compiled-in defaults.
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGSYSCONFDIR</envar></primary>
-      </indexterm>
-      <envar>PGSYSCONFDIR</envar> sets the directory containing the
-      <filename>pg_service.conf</> file and in a future version
-      possibly other system-wide configuration files.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary><envar>PGLOCALEDIR</envar></primary>
-      </indexterm>
-      <envar>PGLOCALEDIR</envar> sets the directory containing the
-      <literal>locale</> files for message internationalization.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
- </sect1>
-
-
- <sect1 id="libpq-pgpass">
-  <title>The Password File</title>
-
-  <indexterm zone="libpq-pgpass">
-   <primary>password file</primary>
-  </indexterm>
-  <indexterm zone="libpq-pgpass">
-   <primary>.pgpass</primary>
-  </indexterm>
-&common;
-  <para>
-   The file <filename>.pgpass</filename> in a user's home directory or the
-   file referenced by <envar>PGPASSFILE</envar> can contain passwords to
-   be used if the connection requires a password (and no password has been
-   specified  otherwise). On Microsoft Windows the file is named
-   <filename>%APPDATA%\postgresql\pgpass.conf</> (where
-   <filename>%APPDATA%</> refers to the Application Data subdirectory in
-   the user's profile).
-  </para>
-
-  <para>
-   This file should contain lines of the following format:
-<synopsis>
-<replaceable>hostname</replaceable>:<replaceable>port</replaceable>:<replaceable>database</replaceable>:<replaceable>username</replaceable>:<replaceable>password</replaceable>
-</synopsis>
-   Each of the first four fields can be a literal value, or
-   <literal>*</literal>, which matches anything.  The password field from
-   the first line that matches the current connection parameters will be
-   used.  (Therefore, put more-specific entries first when you are using
-   wildcards.) If an entry needs to contain <literal>:</literal> or
-   <literal>\</literal>, escape this character with <literal>\</literal>.
-   A host name of <literal>localhost</> matches both TCP (host name
-   <literal>localhost</>) and Unix domain socket (<literal>pghost</> empty
-   or the default socket directory) connections coming from the local
-   machine. In a standby server, a database name of <literal>replication</>
-   matches streaming replication connections made to the master server.
-   The <literal>database</> field is of limited usefulness because
-   users have the same password for all databases in the same cluster.
-  </para>
-
-  <para>
-   On Unix systems, the permissions on <filename>.pgpass</filename> must
-   disallow any access to world or group; achieve this by the command
-   <command>chmod 0600 ~/.pgpass</command>.  If the permissions are less
-   strict than this, the file will be ignored.  On Microsoft Windows, it
-   is assumed that the file is stored in a directory that is secure, so
-   no special permissions check is made.
-  </para>
- </sect1>
-
-
- <sect1 id="libpq-pgservice">
-  <title>The Connection Service File</title>
-
-  <indexterm zone="libpq-pgservice">
-   <primary>connection service file</primary>
-  </indexterm>
-  <indexterm zone="libpq-pgservice">
-   <primary>pg_service.conf</primary>
-  </indexterm>
-  <indexterm zone="libpq-pgservice">
-   <primary>.pg_service.conf</primary>
-  </indexterm>
-&common;
-  <para>
-   The connection service file allows libpq connection parameters to be
-   associated with a single service name. That service name can then be
-   specified by a libpq connection, and the associated settings will be
-   used. This allows connection parameters to be modified without requiring
-   a recompile of the libpq application. The service name can also be
-   specified using the <envar>PGSERVICE</envar> environment variable.
-  </para>
-
-  <para>
-   The connection service file can be a per-user service file
-   at <filename>~/.pg_service.conf</filename> or the location
-   specified by the environment variable <envar>PGSERVICEFILE</envar>,
-   or it can be a system-wide file
-   at <filename>etc/pg_service.conf</filename> or in the directory
-   specified by the environment variable
-   <envar>PGSYSCONFDIR</envar>.  If service definitions with the same
-   name exist in the user and the system file, the user file takes
-   precedence.
-  </para>
-
-  <para>
-   The file uses an <quote>INI file</quote> format where the section
-   name is the service name and the parameters are connection
-   parameters; see <xref linkend="libpq-connect"> for a list.  For
-   example:
-<programlisting>
-# comment
-[mydb]
-host=somehost
-port=5433
-user=admin
-</programlisting>
-   An example file is provided at
-   <filename>share/pg_service.conf.sample</filename>.
-  </para>
- </sect1>
-
-
- <sect1 id="libpq-ldap">
-  <title>LDAP Lookup of Connection Parameters</title>
-
-  <indexterm zone="libpq-ldap">
-   <primary>LDAP connection parameter lookup</primary>
-  </indexterm>
-&common;
-  <para>
-   If <application>libpq</application> has been compiled with LDAP support (option
-   <literal><option>--with-ldap</option></literal> for <command>configure</command>)
-   it is possible to retrieve connection options like <literal>host</literal>
-   or <literal>dbname</literal> via LDAP from a central server.
-   The advantage is that if the connection parameters for a database change,
-   the connection information doesn't have to be updated on all client machines.
-  </para>
-
-  <para>
-   LDAP connection parameter lookup uses the connection service file
-   <filename>pg_service.conf</filename> (see <xref
-   linkend="libpq-pgservice">).  A line in a
-   <filename>pg_service.conf</filename> stanza that starts with
-   <literal>ldap://</literal> will be recognized as an LDAP URL and an
-   LDAP query will be performed. The result must be a list of
-   <literal>keyword = value</literal> pairs which will be used to set
-   connection options.  The URL must conform to RFC 1959 and be of the
-   form
-<synopsis>
-ldap://[<replaceable>hostname</replaceable>[:<replaceable>port</replaceable>]]/<replaceable>search_base</replaceable>?<replaceable>attribute</replaceable>?<replaceable>search_scope</replaceable>?<replaceable>filter</replaceable>
-</synopsis>
-   where <replaceable>hostname</replaceable> defaults to
-   <literal>localhost</literal> and <replaceable>port</replaceable>
-   defaults to 389.
-  </para>
-
-  <para>
-   Processing of <filename>pg_service.conf</filename> is terminated after
-   a successful LDAP lookup, but is continued if the LDAP server cannot
-   be contacted.  This is to provide a fallback with further LDAP URL
-   lines that point to different LDAP servers, classical <literal>keyword
-   = value</literal> pairs, or default connection options.  If you would
-   rather get an error message in this case, add a syntactically incorrect
-   line after the LDAP URL.
-  </para>
-
-  <para>
-   A sample LDAP entry that has been created with the LDIF file
-<programlisting>
-version:1
-dn:cn=mydatabase,dc=mycompany,dc=com
-changetype:add
-objectclass:top
-objectclass:groupOfUniqueNames
-cn:mydatabase
-uniqueMember:host=dbserver.mycompany.com
-uniqueMember:port=5439
-uniqueMember:dbname=mydb
-uniqueMember:user=mydb_user
-uniqueMember:sslmode=require
-</programlisting>
-   might be queried with the following LDAP URL:
-<programlisting>
-ldap://ldap.mycompany.com/dc=mycompany,dc=com?uniqueMember?one?(cn=mydatabase)
-</programlisting>
-  </para>
-
-  <para>
-   You can also mix regular service file entries with LDAP lookups.
-   A complete example for a stanza in <filename>pg_service.conf</filename>
-   would be:
-<programlisting>
-# only host and port are stored in LDAP, specify dbname and user explicitly
-[customerdb]
-dbname=customer
-user=appuser
-ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
-</programlisting>
-  </para>
-
- </sect1>
-
-
- <sect1 id="libpq-ssl">
-  <title>SSL Support</title>
-
-  <indexterm zone="libpq-ssl">
-   <primary>SSL</primary>
-  </indexterm>
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</> has native support for using <acronym>SSL</>
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> has native support for using <acronym>SSL</>
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> has native support for using <acronym>SSL</>
-<!## end>
-   connections to encrypt client/server communications for increased
-   security. See <xref linkend="ssl-tcp"> for details about the server-side
-   <acronym>SSL</> functionality.
-  </para>
-
-  <para>
-   <application>libpq</application> reads the system-wide
-   <productname>OpenSSL</productname> configuration file. By default, this
-   file is named <filename>openssl.cnf</filename> and is located in the
-   directory reported by <literal>openssl version -d</>.  This default
-   can be overridden by setting environment variable
-   <envar>OPENSSL_CONF</envar> to the name of the desired configuration
-   file.
-  </para>
-
- <sect2 id="libq-ssl-certificates">
-  <title>Client Verification of Server Certificates</title>
-
-  <para>
-   By default, <productname>PostgreSQL</> will not perform any verification of
-   the server certificate. This means that it is possible to spoof the server
-   identity (for example by modifying a DNS record or by taking over the server
-   IP address) without the client knowing. In order to prevent spoofing,
-   <acronym>SSL</> certificate verification must be used.
-  </para>
-
-  <para>
-   If the parameter <literal>sslmode</> is set to <literal>verify-ca</>,
-   libpq will verify that the server is trustworthy by checking the
-   certificate chain up to a trusted certificate authority
-   (<acronym>CA</>). If <literal>sslmode</> is set to <literal>verify-full</>,
-   libpq will <emphasis>also</> verify that the server host name matches its
-   certificate. The SSL connection will fail if the server certificate cannot
-   be verified. <literal>verify-full</> is recommended in most
-   security-sensitive environments.
-  </para>
-
-  <para>
-   In <literal>verify-full</> mode, the <literal>cn</> (Common Name) attribute
-   of the certificate is matched against the host name. If the <literal>cn</>
-   attribute starts with an asterisk (<literal>*</>), it will be treated as
-   a wildcard, and will match all characters <emphasis>except</> a dot
-   (<literal>.</>). This means the certificate will not match subdomains.
-   If the connection is made using an IP address instead of a host name, the
-   IP address will be matched (without doing any DNS lookups).
-  </para>
-
-  <para>
-   To allow server certificate verification, the certificate(s) of one or more
-   trusted <acronym>CA</>s must be
-   placed in the file <filename>~/.postgresql/root.crt</> in the user's home
-   directory. (On Microsoft Windows the file is named
-   <filename>%APPDATA%\postgresql\root.crt</filename>.)
-  </para>
-
-  <para>
-   Certificate Revocation List (CRL) entries are also checked
-   if the file <filename>~/.postgresql/root.crl</filename> exists
-   (<filename>%APPDATA%\postgresql\root.crl</filename> on Microsoft
-   Windows).
-  </para>
-
-  <para>
-   The location of the root certificate file and the CRL can be changed by
-   setting
-   the connection parameters <literal>sslrootcert</> and <literal>sslcrl</>
-   or the environment variables <envar>PGSSLROOTCERT</> and <envar>PGSSLCRL</>.
-  </para>
- </sect2>
-
- <sect2 id="libpq-ssl-clientcert">
-  <title>Client Certificates</title>
-
-  <para>
-   If the server requests a trusted client certificate,
-   <application>libpq</application> will send the certificate stored in
-   file <filename>~/.postgresql/postgresql.crt</> in the user's home
-   directory.  The certificate must be signed by one of the certificate
-   authorities (<acronym>CA</acronym>) trusted by the server.  A matching
-   private key file <filename>~/.postgresql/postgresql.key</> must also
-   be present. The private
-   key file must not allow any access to world or group; achieve this by the
-   command <command>chmod 0600 ~/.postgresql/postgresql.key</command>.
-   On Microsoft Windows these files are named
-   <filename>%APPDATA%\postgresql\postgresql.crt</filename> and
-   <filename>%APPDATA%\postgresql\postgresql.key</filename>, and there
-   is no special permissions check since the directory is presumed secure.
-   The location of the certificate and key files can be overridden by the
-   connection parameters <literal>sslcert</> and <literal>sslkey</> or the
-   environment variables <envar>PGSSLCERT</> and <envar>PGSSLKEY</>.
-  </para>
-
-  <para>
-   In some cases, the client certificate might be signed by an
-   <quote>intermediate</> certificate authority, rather than one that is
-   directly trusted by the server.  To use such a certificate, append the
-   certificate of the signing authority to the <filename>postgresql.crt</>
-   file, then its parent authority's certificate, and so on up to a
-   <quote>root</> authority that is trusted by the server.  The root
-   certificate should be included in every case where
-   <filename>postgresql.crt</> contains more than one certificate.
-  </para>
-
-  <para>
-   Note that <filename>root.crt</filename> lists the top-level CAs that are
-   considered trusted for signing server certificates.  In principle it need
-   not list the CA that signed the client's certificate, though in most cases
-   that CA would also be trusted for server certificates.
-  </para>
-
- </sect2>
-
- <sect2 id="libpq-ssl-protection">
-  <title>Protection Provided in Different Modes</title>
-
-  <para>
-   The different values for the <literal>sslmode</> parameter provide different
-   levels of protection. SSL can provide
-   protection against three types of attacks:
-
-   <variablelist>
-    <varlistentry>
-     <term>Eavesdropping</term>
-     <listitem>
-      <para>If a third party can examine the network traffic between the
-       client and the server, it can read both connection information (including
-       the user name and password) and the data that is passed. <acronym>SSL</>
-       uses encryption to prevent this.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Man in the middle (<acronym>MITM</>)</term>
-     <listitem>
-      <para>If a third party can modify the data while passing between the
-       client and server, it can pretend to be the server and therefore see and
-       modify data <emphasis>even if it is encrypted</>. The third party can then
-       forward the connection information and data to the original server,
-       making it impossible to detect this attack. Common vectors to do this
-       include DNS poisoning and address hijacking, whereby the client is directed
-       to a different server than intended. There are also several other
-       attack methods that can accomplish this. <acronym>SSL</> uses certificate
-       verification to prevent this, by authenticating the server to the client.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Impersonation</term>
-     <listitem>
-      <para>If a third party can pretend to be an authorized client, it can
-       simply access data it should not have access to. Typically this can
-       happen through insecure password management. <acronym>SSL</> uses
-       client certificates to prevent this, by making sure that only holders
-       of valid certificates can access the server.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   For a connection to be known secure, SSL usage must be configured
-   on <emphasis>both the client and the server</> before the connection
-   is made. If it is only configured on the server, the client may end up
-   sending sensitive information (e.g. passwords) before
-   it knows that the server requires high security. In libpq, secure
-   connections can be ensured
-   by setting the <literal>sslmode</> parameter to <literal>verify-full</> or
-   <literal>verify-ca</>, and providing the system with a root certificate to
-   verify against. This is analogous to using an <literal>https</>
-   <acronym>URL</> for encrypted web browsing.
-  </para>
-
-  <para>
-   Once the server has been authenticated, the client can pass sensitive data.
-   This means that up until this point, the client does not need to know if
-   certificates will be used for authentication, making it safe to specify that
-   only in the server configuration.
-  </para>
-
-  <para>
-   All <acronym>SSL</> options carry overhead in the form of encryption and
-   key-exchange, so there is a tradeoff that has to be made between performance
-   and security. <xref linkend="libpq-ssl-sslmode-statements">
-   illustrates the risks the different <literal>sslmode</> values
-   protect against, and what statement they make about security and overhead.
-  </para>
-
-  <table id="libpq-ssl-sslmode-statements">
-   <title>SSL Mode Descriptions</title>
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry><literal>sslmode</></entry>
-      <entry>Eavesdropping protection</entry>
-      <entry><acronym>MITM</> protection</entry>
-      <entry>Statement</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>disabled</></entry>
-      <entry>No</entry>
-      <entry>No</entry>
-      <entry>I don't care about security, and I don't want to pay the overhead
-       of encryption.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>allow</></entry>
-      <entry>Maybe</entry>
-      <entry>No</entry>
-      <entry>I don't care about security, but I will pay the overhead of
-       encryption if the server insists on it.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>prefer</></entry>
-      <entry>Maybe</entry>
-      <entry>No</entry>
-      <entry>I don't care about encryption, but I wish to pay the overhead of
-       encryption if the server supports it.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>require</></entry>
-      <entry>Yes</entry>
-      <entry>No</entry>
-      <entry>I want my data to be encrypted, and I accept the overhead. I trust
-       that the network will make sure I always connect to the server I want.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>verify-ca</></entry>
-      <entry>Yes</entry>
-      <entry><literal>Depends on CA</>-policy</entry>
-      <entry>I want my data encrypted, and I accept the overhead. I want to be
-       sure that I connect to a server that I trust.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal>verify-full</></entry>
-       <entry>Yes</entry>
-       <entry>Yes</entry>
-       <entry>I want my data encrypted, and I accept the overhead. I want to be
-        sure that I connect to a server I trust, and that it's the one I
-        specify.
-       </entry>
-      </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The difference between <literal>verify-ca</> and <literal>verify-full</>
-   depends on the policy of the root <acronym>CA</>. If a public
-   <acronym>CA</> is used, <literal>verify-ca</> allows connections to a server
-   that <emphasis>somebody else</> may have registered with the <acronym>CA</>.
-   In this case, <literal>verify-full</> should always be used. If
-   a local <acronym>CA</> is used, or even a self-signed certificate, using
-   <literal>verify-ca</> often provides enough protection.
-  </para>
-
-  <para>
-   The default value for <literal>sslmode</> is <literal>prefer</>. As is shown
-   in the table, this makes no sense from a security point of view, and it only
-   promises performance overhead if possible. It is only provided as the default
-   for backward compatibility, and is not recommended in secure deployments.
-  </para>
-
- </sect2>
-
- <sect2 id="libpq-ssl-fileusage">
-  <title>SSL Client File Usage</title>
-
-  <para>
-   <xref linkend="libpq-ssl-file-usage"> summarizes the files that are
-   relevant to the SSL setup on the client.
-  </para>
-
-  <table id="libpq-ssl-file-usage">
-   <title>Libpq/Client SSL File Usage</title>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>File</entry>
-      <entry>Contents</entry>
-      <entry>Effect</entry>
-     </row>
-    </thead>
-
-    <tbody>
-
-     <row>
-      <entry><filename>~/.postgresql/postgresql.crt</></entry>
-      <entry>client certificate</entry>
-      <entry>requested by server</entry>
-     </row>
-
-     <row>
-      <entry><filename>~/.postgresql/postgresql.key</></entry>
-      <entry>client private key</entry>
-      <entry>proves client certificate sent by owner; does not indicate
-      certificate owner is trustworthy</entry>
-     </row>
-
-     <row>
-      <entry><filename>~/.postgresql/root.crt</></entry>
-      <entry>trusted certificate authorities</entry>
-      <entry>checks that server certificate is signed by a trusted certificate
-      authority</entry>
-     </row>
-
-     <row>
-      <entry><filename>~/.postgresql/root.crl</></entry>
-      <entry>certificates revoked by certificate authorities</entry>
-      <entry>server certificate must not be on this list</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
- </sect2>
-
- <sect2 id="libpq-ssl-initialize">
-  <title>SSL Library Initialization</title>
-
-  <para>
-   If your application initializes <literal>libssl</> and/or
-   <literal>libcrypto</> libraries and <application>libpq</application>
-   is built with <acronym>SSL</> support, you should call
-   <function>PQinitOpenSSL</> to tell <application>libpq</application>
-   that the <literal>libssl</> and/or <literal>libcrypto</> libraries
-   have been initialized by your application, so that
-   <application>libpq</application> will not also initialize those libraries.
-   <!-- If this URL changes replace it with a URL to www.archive.org. -->
-   See <ulink
-   url="http://h71000.www7.hp.com/doc/83final/BA554_90007/ch04.html"></ulink>
-   for details on the SSL API.
-  </para>
-
-  <para>
-   <variablelist>
-    <varlistentry id="libpq-pqinitopenssl">
-     <term>
-      <function>PQinitOpenSSL</function>
-      <indexterm>
-       <primary>PQinitOpenSSL</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Allows applications to select which security libraries to initialize.
-<synopsis>
-void PQinitOpenSSL(int do_ssl, int do_crypto);
-</synopsis>
-      </para>
-
-      <para>
-       When <parameter>do_ssl</> is non-zero, <application>libpq</application>
-       will initialize the <application>OpenSSL</> library before first
-       opening a database connection.  When <parameter>do_crypto</> is
-       non-zero, the <literal>libcrypto</> library will be initialized.  By
-       default (if <function>PQinitOpenSSL</> is not called), both libraries
-       are initialized.  When SSL support is not compiled in, this function is
-       present but does nothing.
-      </para>
-
-      <para>
-       If your application uses and initializes either <application>OpenSSL</>
-       or its underlying <literal>libcrypto</> library, you <emphasis>must</>
-       call this function with zeroes for the appropriate parameter(s)
-       before first opening a database connection.  Also be sure that you
-       have done that initialization before opening a database connection.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry id="libpq-pqinitssl">
-     <term>
-      <function>PQinitSSL</function>
-      <indexterm>
-       <primary>PQinitSSL</primary>
-      </indexterm>
-     </term>
-
-     <listitem>
-      <para>
-       Allows applications to select which security libraries to initialize.
-<synopsis>
-void PQinitSSL(int do_ssl);
-</synopsis>
-      </para>
-
-      <para>
-       This function is equivalent to
-       <literal>PQinitOpenSSL(do_ssl, do_ssl)</>.
-       It is sufficient for applications that initialize both or neither
-       of <application>OpenSSL</> and <literal>libcrypto</>.
-      </para>
-
-      <para>
-       <function>PQinitSSL</> has been present since
-       <productname>PostgreSQL</> 8.0, while <function>PQinitOpenSSL</>
-       was added in <productname>PostgreSQL</> 8.4, so <function>PQinitSSL</>
-       might be preferable for applications that need to work with older
-       versions of <application>libpq</application>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </sect2>
-
- </sect1>
-
-
- <sect1 id="libpq-threading">
-  <title>Behavior in Threaded Programs</title>
-
-  <indexterm zone="libpq-threading">
-   <primary>threads</primary>
-   <secondary>with libpq</secondary>
-  </indexterm>
-&common;
-  <para>
-   <application>libpq</application> is reentrant and thread-safe by default.
-   You might need to use special compiler command-line
-   options when you compile your application code.  Refer to your
-   system's documentation for information about how to build
-   thread-enabled applications, or look in
-   <filename>src/Makefile.global</filename> for <literal>PTHREAD_CFLAGS</>
-   and <literal>PTHREAD_LIBS</>.  This function allows the querying of
-   <application>libpq</application>'s thread-safe status:
-  </para>
-
-  <variablelist>
-   <varlistentry id="libpq-pqisthreadsafe">
-    <term>
-     <function>PQisthreadsafe</function>
-     <indexterm>
-      <primary>PQisthreadsafe</primary>
-     </indexterm>
-    </term>
-
-    <listitem>
-     <para>
-      Returns the thread safety status of the
-      <application>libpq</application> library.
-<synopsis>
-int PQisthreadsafe();
-</synopsis>
-     </para>
-
-     <para>
-      Returns 1 if the <application>libpq</application> is thread-safe
-      and 0 if it is not.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   One thread restriction is that no two threads attempt to manipulate
-   the same <structname>PGconn</> object at the same time. In particular,
-   you cannot issue concurrent commands from different threads through
-   the same connection object. (If you need to run concurrent commands,
-   use multiple connections.)
-  </para>
-
-  <para>
-   <structname>PGresult</> objects are read-only after creation, and so
-   can be passed around freely between threads.
-  </para>
-
-  <para>
-   The deprecated functions <function>PQrequestCancel</function> and
-   <function>PQoidStatus</function> are not thread-safe and should not be
-   used in multithread programs.  <function>PQrequestCancel</function>
-   can be replaced by <function>PQcancel</function>.
-   <function>PQoidStatus</function> can be replaced by
-   <function>PQoidValue</function>.
-  </para>
-
-  <para>
-   If you are using Kerberos inside your application (in addition to inside
-   <application>libpq</application>), you will need to do locking around
-   Kerberos calls because Kerberos functions are not thread-safe.  See
-   function <function>PQregisterThreadLock</> in the
-   <application>libpq</application> source code for a way to do cooperative
-   locking between <application>libpq</application> and your application.
-  </para>
-
-  <para>
-   If you experience problems with threaded applications, run the program
-   in <filename>src/tools/thread</> to see if your platform has
-   thread-unsafe functions.  This program is run by
-   <filename>configure</filename>, but for binary distributions your
-   library might not match the library used to build the binaries.
-  </para>
- </sect1>
-
-
- <sect1 id="libpq-build">
-  <title>Building <application>libpq</application> Programs</title>
-
-  <indexterm zone="libpq-build">
-   <primary>compiling</primary>
-   <secondary>libpq applications</secondary>
-  </indexterm>
-&common;
-  <para>
-   To build (i.e., compile and link) a program using
-   <application>libpq</application> you need to do all of the following
-   things:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Include the <filename>libpq-fe.h</filename> header file:
-<programlisting>
-#include &lt;libpq-fe.h&gt;
-</programlisting>
-      If you failed to do that then you will normally get error messages
-      from your compiler similar to:
-<screen>
-foo.c: In function `main':
-foo.c:34: `PGconn' undeclared (first use in this function)
-foo.c:35: `PGresult' undeclared (first use in this function)
-foo.c:54: `CONNECTION_BAD' undeclared (first use in this function)
-foo.c:68: `PGRES_COMMAND_OK' undeclared (first use in this function)
-foo.c:95: `PGRES_TUPLES_OK' undeclared (first use in this function)
-</screen>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-<!## PG>
-      Point your compiler to the directory where the <productname>PostgreSQL</> header
-<!## end>
-<!## XC>
-      Point your compiler to the directory where the <productname>Postgres-XC</> header
-<!## end>
-<!## XL>
-      Point your compiler to the directory where the <productname>Postgres-XL</> header
-<!## end>
-      files were installed, by supplying the
-      <literal>-I<replaceable>directory</replaceable></literal> option
-      to your compiler.  (In some cases the compiler will look into
-      the directory in question by default, so you can omit this
-      option.)  For instance, your compile command line could look
-      like:
-<programlisting>
-cc -c -I/usr/local/pgsql/include testprog.c
-</programlisting>
-      If you are using makefiles then add the option to the
-      <varname>CPPFLAGS</varname> variable:
-<programlisting>
-CPPFLAGS += -I/usr/local/pgsql/include
-</programlisting>
-     </para>
-
-     <para>
-      If there is any chance that your program might be compiled by
-      other users then you should not hardcode the directory location
-      like that.  Instead, you can run the utility
-      <command>pg_config</command><indexterm><primary>pg_config</><secondary
-      sortas="libpq">with libpq</></> to find out where the header
-      files are on the local system:
-<screen>
-<prompt>$</prompt> pg_config --includedir
-<computeroutput>/usr/local/include</computeroutput>
-</screen>
-     </para>
-
-     <para>
-      Failure to specify the correct option to the compiler will
-      result in an error message such as:
-<screen>
-testlibpq.c:8:22: libpq-fe.h: No such file or directory
-</screen>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      When linking the final program, specify the option
-      <literal>-lpq</literal> so that the <application>libpq</application>
-      library gets pulled in, as well as the option
-      <literal>-L<replaceable>directory</replaceable></literal> to point
-      the compiler to the directory where the
-      <application>libpq</application> library resides.  (Again, the
-      compiler will search some directories by default.)  For maximum
-      portability, put the <option>-L</option> option before the
-      <option>-lpq</option> option.  For example:
-<programlisting>
-cc -o testprog testprog1.o testprog2.o -L/usr/local/pgsql/lib -lpq
-</programlisting>
-     </para>
-
-     <para>
-      You can find out the library directory using
-      <command>pg_config</command> as well:
-<screen>
-<prompt>$</prompt> pg_config --libdir
-<computeroutput>/usr/local/pgsql/lib</computeroutput>
-</screen>
-     </para>
-
-     <para>
-      Error messages that point to problems in this area could look like
-      the following:
-<screen>
-testlibpq.o: In function `main':
-testlibpq.o(.text+0x60): undefined reference to `PQsetdbLogin'
-testlibpq.o(.text+0x71): undefined reference to `PQstatus'
-testlibpq.o(.text+0xa4): undefined reference to `PQerrorMessage'
-</screen>
-      This means you forgot <option>-lpq</option>.
-<screen>
-/usr/bin/ld: cannot find -lpq
-</screen>
-      This means you forgot the <option>-L</option> option or did not
-      specify the right directory.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
- </sect1>
-
-
- <sect1 id="libpq-example">
-  <title>Example Programs</title>
-&common;
-  <para>
-   These examples and others can be found in the
-   directory <filename>src/test/examples</filename> in the source code
-   distribution.
-  </para>
-
-  <example id="libpq-example-1">
-   <title><application>libpq</application> Example Program 1</title>
-
-<!## PG>
-<programlisting>
-<![CDATA[
-/*
- * testlibpq.c
- *
- *      Test the C version of libpq, the PostgreSQL frontend library.
- */
-#include <stdio.h>
-#include <stdlib.h>
-#include <libpq-fe.h>
-
-static void
-exit_nicely(PGconn *conn)
-{
-    PQfinish(conn);
-    exit(1);
-}
-
-int
-main(int argc, char **argv)
-{
-    const char *conninfo;
-    PGconn     *conn;
-    PGresult   *res;
-    int         nFields;
-    int         i,
-                j;
-
-    /*
-     * If the user supplies a parameter on the command line, use it as the
-     * conninfo string; otherwise default to setting dbname=postgres and using
-     * environment variables or defaults for all other connection parameters.
-     */
-    if (argc > 1)
-        conninfo = argv[1];
-    else
-        conninfo = "dbname = postgres";
-
-    /* Make a connection to the database */
-    conn = PQconnectdb(conninfo);
-
-    /* Check to see that the backend connection was successfully made */
-    if (PQstatus(conn) != CONNECTION_OK)
-    {
-        fprintf(stderr, "Connection to database failed: %s",
-                PQerrorMessage(conn));
-        exit_nicely(conn);
-    }
-
-    /*
-     * Our test case here involves using a cursor, for which we must be inside
-     * a transaction block.  We could do the whole thing with a single
-     * PQexec() of "select * from pg_database", but that's too trivial to make
-     * a good example.
-     */
-
-    /* Start a transaction block */
-    res = PQexec(conn, "BEGIN");
-    if (PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "BEGIN command failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /*
-     * Should PQclear PGresult whenever it is no longer needed to avoid memory
-     * leaks
-     */
-    PQclear(res);
-
-    /*
-     * Fetch rows from pg_database, the system catalog of databases
-     */
-    res = PQexec(conn, "DECLARE myportal CURSOR FOR select * from pg_database");
-    if (PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "DECLARE CURSOR failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-    PQclear(res);
-
-    res = PQexec(conn, "FETCH ALL in myportal");
-    if (PQresultStatus(res) != PGRES_TUPLES_OK)
-    {
-        fprintf(stderr, "FETCH ALL failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /* first, print out the attribute names */
-    nFields = PQnfields(res);
-    for (i = 0; i < nFields; i++)
-        printf("%-15s", PQfname(res, i));
-    printf("\n\n");
-
-    /* next, print out the rows */
-    for (i = 0; i < PQntuples(res); i++)
-    {
-        for (j = 0; j < nFields; j++)
-            printf("%-15s", PQgetvalue(res, i, j));
-        printf("\n");
-    }
-
-    PQclear(res);
-
-    /* close the portal ... we don't bother to check for errors ... */
-    res = PQexec(conn, "CLOSE myportal");
-    PQclear(res);
-
-    /* end the transaction */
-    res = PQexec(conn, "END");
-    PQclear(res);
-
-    /* close the connection to the database and cleanup */
-    PQfinish(conn);
-
-    return 0;
-}
-]]>
-</programlisting>
-<!## end>
-<!## XC>
-<programlisting>
-<![CDATA[
-/*
- * testlibpq.c
- *
- *      Test the C version of libpq, the Postgres-XC frontend library.
- */
-#include <stdio.h>
-#include <stdlib.h>
-#include <libpq-fe.h>
-
-static void
-exit_nicely(PGconn *conn)
-{
-    PQfinish(conn);
-    exit(1);
-}
-
-int
-main(int argc, char **argv)
-{
-    const char *conninfo;
-    PGconn     *conn;
-    PGresult   *res;
-    int         nFields;
-    int         i,
-                j;
-
-    /*
-     * If the user supplies a parameter on the command line, use it as the
-     * conninfo string; otherwise default to setting dbname=postgres and using
-     * environment variables or defaults for all other connection parameters.
-     */
-    if (argc > 1)
-        conninfo = argv[1];
-    else
-        conninfo = "dbname = postgres";
-
-    /* Make a connection to the database */
-    conn = PQconnectdb(conninfo);
-
-    /* Check to see that the backend connection was successfully made */
-    if (PQstatus(conn) != CONNECTION_OK)
-    {
-        fprintf(stderr, "Connection to database failed: %s",
-                PQerrorMessage(conn));
-        exit_nicely(conn);
-    }
-
-    /*
-     * Our test case here involves using a cursor, for which we must be inside
-     * a transaction block.  We could do the whole thing with a single
-     * PQexec() of "select * from pg_database", but that's too trivial to make
-     * a good example.
-     */
-
-    /* Start a transaction block */
-    res = PQexec(conn, "BEGIN");
-    if (PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "BEGIN command failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /*
-     * Should PQclear PGresult whenever it is no longer needed to avoid memory
-     * leaks
-     */
-    PQclear(res);
-
-    /*
-     * Fetch rows from pg_database, the system catalog of databases
-     */
-    res = PQexec(conn, "DECLARE myportal CURSOR FOR select * from pg_database");
-    if (PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "DECLARE CURSOR failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-    PQclear(res);
-
-    res = PQexec(conn, "FETCH ALL in myportal");
-    if (PQresultStatus(res) != PGRES_TUPLES_OK)
-    {
-        fprintf(stderr, "FETCH ALL failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /* first, print out the attribute names */
-    nFields = PQnfields(res);
-    for (i = 0; i < nFields; i++)
-        printf("%-15s", PQfname(res, i));
-    printf("\n\n");
-
-    /* next, print out the rows */
-    for (i = 0; i < PQntuples(res); i++)
-    {
-        for (j = 0; j < nFields; j++)
-            printf("%-15s", PQgetvalue(res, i, j));
-        printf("\n");
-    }
-
-    PQclear(res);
-
-    /* close the portal ... we don't bother to check for errors ... */
-    res = PQexec(conn, "CLOSE myportal");
-    PQclear(res);
-
-    /* end the transaction */
-    res = PQexec(conn, "END");
-    PQclear(res);
-
-    /* close the connection to the database and cleanup */
-    PQfinish(conn);
-
-    return 0;
-}
-]]>
-</programlisting>
-<!## end>
-<!## XL>
-<programlisting>
-<![CDATA[
-/*
- * testlibpq.c
- *
- *      Test the C version of libpq, the Postgres-XL frontend library.
- */
-#include <stdio.h>
-#include <stdlib.h>
-#include <libpq-fe.h>
-
-static void
-exit_nicely(PGconn *conn)
-{
-    PQfinish(conn);
-    exit(1);
-}
-
-int
-main(int argc, char **argv)
-{
-    const char *conninfo;
-    PGconn     *conn;
-    PGresult   *res;
-    int         nFields;
-    int         i,
-                j;
-
-    /*
-     * If the user supplies a parameter on the command line, use it as the
-     * conninfo string; otherwise default to setting dbname=postgres and using
-     * environment variables or defaults for all other connection parameters.
-     */
-    if (argc > 1)
-        conninfo = argv[1];
-    else
-        conninfo = "dbname = postgres";
-
-    /* Make a connection to the database */
-    conn = PQconnectdb(conninfo);
-
-    /* Check to see that the backend connection was successfully made */
-    if (PQstatus(conn) != CONNECTION_OK)
-    {
-        fprintf(stderr, "Connection to database failed: %s",
-                PQerrorMessage(conn));
-        exit_nicely(conn);
-    }
-
-    /*
-     * Our test case here involves using a cursor, for which we must be inside
-     * a transaction block.  We could do the whole thing with a single
-     * PQexec() of "select * from pg_database", but that's too trivial to make
-     * a good example.
-     */
-
-    /* Start a transaction block */
-    res = PQexec(conn, "BEGIN");
-    if (PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "BEGIN command failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /*
-     * Should PQclear PGresult whenever it is no longer needed to avoid memory
-     * leaks
-     */
-    PQclear(res);
-
-    /*
-     * Fetch rows from pg_database, the system catalog of databases
-     */
-    res = PQexec(conn, "DECLARE myportal CURSOR FOR select * from pg_database");
-    if (PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "DECLARE CURSOR failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-    PQclear(res);
-
-    res = PQexec(conn, "FETCH ALL in myportal");
-    if (PQresultStatus(res) != PGRES_TUPLES_OK)
-    {
-        fprintf(stderr, "FETCH ALL failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /* first, print out the attribute names */
-    nFields = PQnfields(res);
-    for (i = 0; i < nFields; i++)
-        printf("%-15s", PQfname(res, i));
-    printf("\n\n");
-
-    /* next, print out the rows */
-    for (i = 0; i < PQntuples(res); i++)
-    {
-        for (j = 0; j < nFields; j++)
-            printf("%-15s", PQgetvalue(res, i, j));
-        printf("\n");
-    }
-
-    PQclear(res);
-
-    /* close the portal ... we don't bother to check for errors ... */
-    res = PQexec(conn, "CLOSE myportal");
-    PQclear(res);
-
-    /* end the transaction */
-    res = PQexec(conn, "END");
-    PQclear(res);
-
-    /* close the connection to the database and cleanup */
-    PQfinish(conn);
-
-    return 0;
-}
-]]>
-</programlisting>
-<!## end>
-  </example>
-
-  <example id="libpq-example-2">
-   <title><application>libpq</application> Example Program 2</title>
-
-<programlisting>
-<![CDATA[
-/*
- * testlibpq2.c
- *      Test of the asynchronous notification interface
- *
- * Start this program, then from psql in another window do
- *   NOTIFY TBL2;
- * Repeat four times to get this program to exit.
- *
- * Or, if you want to get fancy, try this:
- * populate a database with the following commands
- * (provided in src/test/examples/testlibpq2.sql):
- *
- *   CREATE TABLE TBL1 (i int4);
- *
- *   CREATE TABLE TBL2 (i int4);
- *
- *   CREATE RULE r1 AS ON INSERT TO TBL1 DO
- *     (INSERT INTO TBL2 VALUES (new.i); NOTIFY TBL2);
- *
- * and do this four times:
- *
- *   INSERT INTO TBL1 VALUES (10);
- */
-#include <stdio.h>
-#include <stdlib.h>
-#include <string.h>
-#include <errno.h>
-#include <sys/time.h>
-#include <libpq-fe.h>
-
-static void
-exit_nicely(PGconn *conn)
-{
-    PQfinish(conn);
-    exit(1);
-}
-
-int
-main(int argc, char **argv)
-{
-    const char *conninfo;
-    PGconn     *conn;
-    PGresult   *res;
-    PGnotify   *notify;
-    int         nnotifies;
-
-    /*
-     * If the user supplies a parameter on the command line, use it as the
-     * conninfo string; otherwise default to setting dbname=postgres and using
-     * environment variables or defaults for all other connection parameters.
-     */
-    if (argc > 1)
-        conninfo = argv[1];
-    else
-        conninfo = "dbname = postgres";
-
-    /* Make a connection to the database */
-    conn = PQconnectdb(conninfo);
-
-    /* Check to see that the backend connection was successfully made */
-    if (PQstatus(conn) != CONNECTION_OK)
-    {
-        fprintf(stderr, "Connection to database failed: %s",
-                PQerrorMessage(conn));
-        exit_nicely(conn);
-    }
-
-    /*
-     * Issue LISTEN command to enable notifications from the rule's NOTIFY.
-     */
-    res = PQexec(conn, "LISTEN TBL2");
-    if (PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "LISTEN command failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /*
-     * should PQclear PGresult whenever it is no longer needed to avoid memory
-     * leaks
-     */
-    PQclear(res);
-
-    /* Quit after four notifies are received. */
-    nnotifies = 0;
-    while (nnotifies < 4)
-    {
-        /*
-         * Sleep until something happens on the connection.  We use select(2)
-         * to wait for input, but you could also use poll() or similar
-         * facilities.
-         */
-        int         sock;
-        fd_set      input_mask;
-
-        sock = PQsocket(conn);
-
-        if (sock < 0)
-            break;              /* shouldn't happen */
-
-        FD_ZERO(&input_mask);
-        FD_SET(sock, &input_mask);
-
-        if (select(sock + 1, &input_mask, NULL, NULL, NULL) < 0)
-        {
-            fprintf(stderr, "select() failed: %s\n", strerror(errno));
-            exit_nicely(conn);
-        }
-
-        /* Now check for input */
-        PQconsumeInput(conn);
-        while ((notify = PQnotifies(conn)) != NULL)
-        {
-            fprintf(stderr,
-                    "ASYNC NOTIFY of '%s' received from backend pid %d\n",
-                    notify->relname, notify->be_pid);
-            PQfreemem(notify);
-            nnotifies++;
-        }
-    }
-
-    fprintf(stderr, "Done.\n");
-
-    /* close the connection to the database and cleanup */
-    PQfinish(conn);
-
-    return 0;
-}
-]]>
-</programlisting>
-  </example>
-
-  <example id="libpq-example-3">
-   <title><application>libpq</application> Example Program 3</title>
-
-<programlisting>
-<![CDATA[
-/*
- * testlibpq3.c
- *      Test out-of-line parameters and binary I/O.
- *
- * Before running this, populate a database with the following commands
- * (provided in src/test/examples/testlibpq3.sql):
- *
- * CREATE TABLE test1 (i int4, t text, b bytea);
- *
- * INSERT INTO test1 values (1, 'joe''s place', '\\000\\001\\002\\003\\004');
- * INSERT INTO test1 values (2, 'ho there', '\\004\\003\\002\\001\\000');
- *
- * The expected output is:
- *
- * tuple 0: got
- *  i = (4 bytes) 1
- *  t = (11 bytes) 'joe's place'
- *  b = (5 bytes) \000\001\002\003\004
- *
- * tuple 0: got
- *  i = (4 bytes) 2
- *  t = (8 bytes) 'ho there'
- *  b = (5 bytes) \004\003\002\001\000
- */
-#include <stdio.h>
-#include <stdlib.h>
-#include <string.h>
-#include <sys/types.h>
-#include <libpq-fe.h>
-
-/* for ntohl/htonl */
-#include <netinet/in.h>
-#include <arpa/inet.h>
-
-
-static void
-exit_nicely(PGconn *conn)
-{
-    PQfinish(conn);
-    exit(1);
-}
-
-/*
- * This function prints a query result that is a binary-format fetch from
- * a table defined as in the comment above.  We split it out because the
- * main() function uses it twice.
- */
-static void
-show_binary_results(PGresult *res)
-{
-    int         i,
-                j;
-    int         i_fnum,
-                t_fnum,
-                b_fnum;
-
-    /* Use PQfnumber to avoid assumptions about field order in result */
-    i_fnum = PQfnumber(res, "i");
-    t_fnum = PQfnumber(res, "t");
-    b_fnum = PQfnumber(res, "b");
-
-    for (i = 0; i < PQntuples(res); i++)
-    {
-        char       *iptr;
-        char       *tptr;
-        char       *bptr;
-        int         blen;
-        int         ival;
-
-        /* Get the field values (we ignore possibility they are null!) */
-        iptr = PQgetvalue(res, i, i_fnum);
-        tptr = PQgetvalue(res, i, t_fnum);
-        bptr = PQgetvalue(res, i, b_fnum);
-
-        /*
-         * The binary representation of INT4 is in network byte order, which
-         * we'd better coerce to the local byte order.
-         */
-        ival = ntohl(*((uint32_t *) iptr));
-
-        /*
-         * The binary representation of TEXT is, well, text, and since libpq
-         * was nice enough to append a zero byte to it, it'll work just fine
-         * as a C string.
-         *
-         * The binary representation of BYTEA is a bunch of bytes, which could
-         * include embedded nulls so we have to pay attention to field length.
-         */
-        blen = PQgetlength(res, i, b_fnum);
-
-        printf("tuple %d: got\n", i);
-        printf(" i = (%d bytes) %d\n",
-               PQgetlength(res, i, i_fnum), ival);
-        printf(" t = (%d bytes) '%s'\n",
-               PQgetlength(res, i, t_fnum), tptr);
-        printf(" b = (%d bytes) ", blen);
-        for (j = 0; j < blen; j++)
-            printf("\\%03o", bptr[j]);
-        printf("\n\n");
-    }
-}
-
-int
-main(int argc, char **argv)
-{
-    const char *conninfo;
-    PGconn     *conn;
-    PGresult   *res;
-    const char *paramValues[1];
-    int         paramLengths[1];
-    int         paramFormats[1];
-    uint32_t    binaryIntVal;
-
-    /*
-     * If the user supplies a parameter on the command line, use it as the
-     * conninfo string; otherwise default to setting dbname=postgres and using
-     * environment variables or defaults for all other connection parameters.
-     */
-    if (argc > 1)
-        conninfo = argv[1];
-    else
-        conninfo = "dbname = postgres";
-
-    /* Make a connection to the database */
-    conn = PQconnectdb(conninfo);
-
-    /* Check to see that the backend connection was successfully made */
-    if (PQstatus(conn) != CONNECTION_OK)
-    {
-        fprintf(stderr, "Connection to database failed: %s",
-                PQerrorMessage(conn));
-        exit_nicely(conn);
-    }
-
-    /*
-     * The point of this program is to illustrate use of PQexecParams() with
-     * out-of-line parameters, as well as binary transmission of data.
-     *
-     * This first example transmits the parameters as text, but receives the
-     * results in binary format.  By using out-of-line parameters we can
-     * avoid a lot of tedious mucking about with quoting and escaping, even
-     * though the data is text.  Notice how we don't have to do anything
-     * special with the quote mark in the parameter value.
-     */
-
-    /* Here is our out-of-line parameter value */
-    paramValues[0] = "joe's place";
-
-    res = PQexecParams(conn,
-                       "SELECT * FROM test1 WHERE t = $1",
-                       1,       /* one param */
-                       NULL,    /* let the backend deduce param type */
-                       paramValues,
-                       NULL,    /* don't need param lengths since text */
-                       NULL,    /* default to all text params */
-                       1);      /* ask for binary results */
-
-    if (PQresultStatus(res) != PGRES_TUPLES_OK)
-    {
-        fprintf(stderr, "SELECT failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    show_binary_results(res);
-
-    PQclear(res);
-
-    /*
-     * In this second example we transmit an integer parameter in binary
-     * form, and again retrieve the results in binary form.
-     *
-     * Although we tell PQexecParams we are letting the backend deduce
-     * parameter type, we really force the decision by casting the parameter
-     * symbol in the query text.  This is a good safety measure when sending
-     * binary parameters.
-     */
-
-    /* Convert integer value "2" to network byte order */
-    binaryIntVal = htonl((uint32_t) 2);
-
-    /* Set up parameter arrays for PQexecParams */
-    paramValues[0] = (char *) &binaryIntVal;
-    paramLengths[0] = sizeof(binaryIntVal);
-    paramFormats[0] = 1;        /* binary */
-
-    res = PQexecParams(conn,
-                       "SELECT * FROM test1 WHERE i = $1::int4",
-                       1,       /* one param */
-                       NULL,    /* let the backend deduce param type */
-                       paramValues,
-                       paramLengths,
-                       paramFormats,
-                       1);      /* ask for binary results */
-
-    if (PQresultStatus(res) != PGRES_TUPLES_OK)
-    {
-        fprintf(stderr, "SELECT failed: %s", PQerrorMessage(conn));
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    show_binary_results(res);
-
-    PQclear(res);
-
-    /* close the connection to the database and cleanup */
-    PQfinish(conn);
-
-    return 0;
-}
-]]>
-</programlisting>
-  </example>
-
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/lo.sgmlin b/doc-xc/src/sgml/lo.sgmlin
deleted file mode 100644
index f21d8a0de5..0000000000
--- a/doc-xc/src/sgml/lo.sgmlin
+++ /dev/null
@@ -1,146 +0,0 @@
-<!-- doc/src/sgml/lo.sgml -->
-
-<sect1 id="lo" xreflabel="lo">
- <title>lo</title>
-
- <indexterm zone="lo">
-  <primary>lo</primary>
- </indexterm>
-
-<!## XC>
-&xconly;
- <para>
-  <productname>Postgres-XC</> doesn't support the
-  module <filename>lo</> because it depends upon
-  consistent <literal>OID</> and triggers.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <productname>Postgres-XL</> doesn't support the
-  module <filename>lo</> because it depends upon
-  consistent <literal>OID</> and triggers.
- </para>
-<!## end>
-
-<!## PG>
-
- <para>
-  The <filename>lo</> module provides support for managing Large Objects
-  (also called LOs or BLOBs).  This includes a data type <type>lo</>
-  and a trigger <function>lo_manage</>.
- </para>
-
- <sect2>
-  <title>Rationale</title>
-
-  <para>
-   One of the problems with the JDBC driver (and this affects the ODBC driver
-   also), is that the specification assumes that references to BLOBs (Binary
-   Large OBjects) are stored within a table, and if that entry is changed, the
-   associated BLOB is deleted from the database.
-  </para>
-
-  <para>
-   As <productname>PostgreSQL</> stands, this doesn't occur.  Large objects
-   are treated as objects in their own right; a table entry can reference a
-   large object by OID, but there can be multiple table entries referencing
-   the same large object OID, so the system doesn't delete the large object
-   just because you change or remove one such entry.
-  </para>
-
-  <para>
-   Now this is fine for <productname>PostgreSQL</>-specific applications, but
-   standard code using JDBC or ODBC won't delete the objects, resulting in
-   orphan objects &mdash; objects that are not referenced by anything, and
-   simply occupy disk space.
-  </para>
-
-  <para>
-   The <filename>lo</> module allows fixing this by attaching a trigger
-   to tables that contain LO reference columns.  The trigger essentially just
-   does a <function>lo_unlink</> whenever you delete or modify a value
-   referencing a large object.  When you use this trigger, you are assuming
-   that there is only one database reference to any large object that is
-   referenced in a trigger-controlled column!
-  </para>
-
-  <para>
-   The module also provides a data type <type>lo</>, which is really just
-   a domain of the <type>oid</> type.  This is useful for differentiating
-   database columns that hold large object references from those that are
-   OIDs of other things.  You don't have to use the <type>lo</> type to
-   use the trigger, but it may be convenient to use it to keep track of which
-   columns in your database represent large objects that you are managing with
-   the trigger.  It is also rumored that the ODBC driver gets confused if you
-   don't use <type>lo</> for BLOB columns.
-  </para>
- </sect2>
-
- <sect2>
-  <title>How to Use It</title>
-
-  <para>
-   Here's a simple example of usage:
-  </para>
-
-<programlisting>
-CREATE TABLE image (title TEXT, raster lo);
-
-CREATE TRIGGER t_raster BEFORE UPDATE OR DELETE ON image
-    FOR EACH ROW EXECUTE PROCEDURE lo_manage(raster);
-</programlisting>
-
-  <para>
-   For each column that will contain unique references to large objects,
-   create a <literal>BEFORE UPDATE OR DELETE</> trigger, and give the column
-   name as the sole trigger argument.  If you need multiple <type>lo</>
-   columns in the same table, create a separate trigger for each one,
-   remembering to give a different name to each trigger on the same table.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Limitations</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Dropping a table will still orphan any objects it contains, as the trigger
-     is not executed.  You can avoid this by preceding the <command>DROP
-     TABLE</> with <command>DELETE FROM <replaceable>table</></command>.
-    </para>
-
-    <para>
-     <command>TRUNCATE</> has the same hazard.
-    </para>
-
-    <para>
-     If you already have, or suspect you have, orphaned large objects, see the
-     <xref linkend="vacuumlo"> module to help
-     you clean them up.  It's a good idea to run <application>vacuumlo</>
-     occasionally as a back-stop to the <function>lo_manage</> trigger.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Some frontends may create their own tables, and will not create the
-     associated trigger(s).  Also, users may not remember (or know) to create
-     the triggers.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Peter Mount <email>[email protected]</email>
-  </para>
- </sect2>
-<!## end>
-
-</sect1>
diff --git a/doc-xc/src/sgml/lobj.sgmlin b/doc-xc/src/sgml/lobj.sgmlin
deleted file mode 100644
index 59fef80e68..0000000000
--- a/doc-xc/src/sgml/lobj.sgmlin
+++ /dev/null
@@ -1,757 +0,0 @@
-<!-- doc/src/sgml/lobj.sgml -->
-
- <chapter id="largeObjects">
-  <title>Large Objects</title>
-
-  <indexterm zone="largeobjects"><primary>large object</></>
-  <indexterm><primary>BLOB</><see>large object</></>
-
-<!## XC>
-<!-- NOTICE:
-     Need API improvement and unique OID throughout the cluster to support large objects
--->
-&xconly;
-   <para>
-    Large objects are not supported by <productname>Postgres-XC</>.
-    <productname>Postgres-XC</> does not provide consistent means
-    to handle the large object as OID is inconsistent among cluster nodes.
-   </para>
-<!## end>
-<!## XL>
-<!-- NOTICE:
-     Need API improvement and unique OID throughout the cluster to support large objects
--->
-&xlonly;
-   <para>
-    Large objects are not supported by <productname>Postgres-XL</>.
-    <productname>Postgres-XL</> does not provide consistent means
-    to handle the large object as OID is inconsistent among cluster nodes.
-   </para>
-<!## end>
-
-<!## PG>
-   <para>
-    <productname>PostgreSQL</productname> has a <firstterm>large object</>
-    facility, which provides stream-style access to user data that is stored
-    in a special large-object structure.  Streaming access is useful
-    when working with data values that are too large to manipulate
-    conveniently as a whole.
-   </para>
-
-   <para>
-    This chapter describes the implementation and the programming and
-    query language interfaces to <productname>PostgreSQL</productname>
-    large object data.  We use the <application>libpq</application> C
-    library for the examples in this chapter, but most programming
-    interfaces native to <productname>PostgreSQL</productname> support
-    equivalent functionality.  Other interfaces might use the large
-    object interface internally to provide generic support for large
-    values.  This is not described here.
-   </para>
-
-  <sect1 id="lo-intro">
-   <title>Introduction</title>
-
-   <indexterm>
-    <primary>TOAST</primary>
-    <secondary>versus large objects</secondary>
-   </indexterm>
-&pgnotice;
-   <para>
-    All large objects are placed in a single system table called
-    <classname>pg_largeobject</classname>.
-    <productname>PostgreSQL</productname> also supports a storage system called
-    <quote><acronym>TOAST</acronym></quote> that automatically stores values
-    larger than a single database page into a secondary storage area per table.
-    This makes the large object facility partially obsolete.  One
-    remaining advantage of the large object facility is that it allows values
-    up to 2 GB in size, whereas <acronym>TOAST</acronym>ed fields can be at
-    most 1 GB.  Also, large objects can be randomly modified using a read/write
-    API that is more efficient than performing such operations using
-    <acronym>TOAST</acronym>.
-   </para>
-
-  </sect1>
-
-  <sect1 id="lo-implementation">
-   <title>Implementation Features</title>
-&pgnotice;
-   <para>
-    The large object implementation breaks large
-    objects up into <quote>chunks</quote> and stores the chunks in
-    rows in the database.  A B-tree index guarantees fast
-    searches for the correct chunk number when doing random
-    access reads and writes.
-   </para>
-
-   <para>
-    As of <productname>PostgreSQL</> 9.0, large objects have an owner
-    and a set of access permissions, which can be managed using
-    <xref linkend="sql-grant"> and
-    <xref linkend="sql-revoke">.
-    For compatibility with prior releases, see
-    <xref linkend="guc-lo-compat-privileges">.
-    <literal>SELECT</literal> privileges are required to read a large
-    object, and
-    <literal>UPDATE</literal> privileges are required to write to or
-    truncate it.
-    Only the large object owner (or the database superuser) can unlink, comment
-    on, or change the owner of a large object.
-   </para>
-  </sect1>
-
-  <sect1 id="lo-interfaces">
-   <title>Client Interfaces</title>
-&pgnotice;
-   <para>
-    This section describes the facilities that
-    <productname>PostgreSQL</productname> client interface libraries
-    provide for accessing large objects.  All large object
-    manipulation using these functions <emphasis>must</emphasis> take
-    place within an SQL transaction block.
-    The  <productname>PostgreSQL</productname>  large  object interface is modeled after
-    the <acronym>Unix</acronym>  file-system  interface,  with  analogues  of
-    <function>open</function>,  <function>read</function>,
-    <function>write</function>,
-    <function>lseek</function>, etc.
-   </para>
-
-   <para>
-    Client applications which use the large object interface in
-    <application>libpq</application> should include the header file
-    <filename>libpq/libpq-fs.h</filename> and link with the
-    <application>libpq</application> library.
-   </para>
-
-   <sect2 id="lo-create">
-    <title>Creating a Large Object</title>
-&pgnotice;
-    <para>
-     The function
-<synopsis>
-Oid lo_creat(PGconn *conn, int mode);
-</synopsis>
-     <indexterm><primary>lo_creat</></>
-     creates a new large object.
-     The return value is the OID that was assigned to the new large object,
-     or <symbol>InvalidOid</symbol> (zero) on failure.
-
-     <replaceable class="parameter">mode</replaceable> is unused and
-     ignored as of <productname>PostgreSQL</productname> 8.1; however, for
-     backward compatibility with earlier releases it is best to
-     set it to <symbol>INV_READ</symbol>, <symbol>INV_WRITE</symbol>,
-     or <symbol>INV_READ</symbol> <literal>|</> <symbol>INV_WRITE</symbol>.
-     (These symbolic constants are defined
-     in the header file <filename>libpq/libpq-fs.h</filename>.)
-    </para>
-
-    <para>
-     An example:
-<programlisting>
-inv_oid = lo_creat(conn, INV_READ|INV_WRITE);
-</programlisting>
-    </para>
-
-    <para>
-     The function
-<synopsis>
-Oid lo_create(PGconn *conn, Oid lobjId);
-</synopsis>
-     <indexterm><primary>lo_create</></>
-     also creates a new large object.  The OID to be assigned can be
-     specified by <replaceable class="parameter">lobjId</replaceable>;
-     if so, failure occurs if that OID is already in use for some large
-     object.  If <replaceable class="parameter">lobjId</replaceable>
-     is <symbol>InvalidOid</symbol> (zero) then <function>lo_create</> assigns an unused
-     OID (this is the same behavior as <function>lo_creat</>).
-     The return value is the OID that was assigned to the new large object,
-     or <symbol>InvalidOid</symbol> (zero) on failure.
-    </para>
-
-    <para>
-     <function>lo_create</> is new as of <productname>PostgreSQL</productname>
-     8.1; if this function is run against an older server version, it will
-     fail and return <symbol>InvalidOid</symbol>.
-    </para>
-
-    <para>
-     An example:
-<programlisting>
-inv_oid = lo_create(conn, desired_oid);
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2 id="lo-import">
-    <title>Importing a Large Object</title>
-&pgnotice;
-    <para>
-     To import an operating system file as a large object, call
-<synopsis>
-Oid lo_import(PGconn *conn, const char *filename);
-</synopsis>
-     <indexterm><primary>lo_import</></>
-     <replaceable class="parameter">filename</replaceable>
-     specifies the operating system name of
-     the file to be imported as a large object.
-     The return value is the OID that was assigned to the new large object,
-     or <symbol>InvalidOid</symbol> (zero) on failure.
-     Note that the file is read by the client interface library, not by
-     the server; so it must exist in the client file system and be readable
-     by the client application.
-    </para>
-
-    <para>
-     The function
-<synopsis>
-Oid lo_import_with_oid(PGconn *conn, const char *filename, Oid lobjId);
-</synopsis>
-     <indexterm><primary>lo_import_with_oid</></>
-     also imports a new large object.  The OID to be assigned can be
-     specified by <replaceable class="parameter">lobjId</replaceable>;
-     if so, failure occurs if that OID is already in use for some large
-     object.  If <replaceable class="parameter">lobjId</replaceable>
-     is <symbol>InvalidOid</symbol> (zero) then <function>lo_import_with_oid</> assigns an unused
-     OID (this is the same behavior as <function>lo_import</>).
-     The return value is the OID that was assigned to the new large object,
-     or <symbol>InvalidOid</symbol> (zero) on failure.
-    </para>
-
-    <para>
-     <function>lo_import_with_oid</> is new as of <productname>PostgreSQL</productname>
-     8.4 and uses <function>lo_create</function> internally which is new in 8.1; if this function is run against 8.0 or before, it will
-     fail and return <symbol>InvalidOid</symbol>.
-    </para>
-   </sect2>
-
-   <sect2 id="lo-export">
-    <title>Exporting a Large Object</title>
-&pgnotice;
-    <para>
-     To export a large object
-     into an operating system file, call
-<synopsis>
-int lo_export(PGconn *conn, Oid lobjId, const char *filename);
-</synopsis>
-     <indexterm><primary>lo_export</></>
-     The <parameter>lobjId</parameter> argument specifies the OID of the large
-     object to export and the <parameter>filename</parameter> argument
-     specifies the operating system name of the file.  Note that the file is
-     written by the client interface library, not by the server.  Returns 1
-     on success, -1 on failure.
-    </para>
-   </sect2>
-
-   <sect2 id="lo-open">
-    <title>Opening an Existing Large Object</title>
-&pgnotice;
-    <para>
-     To open an existing large object for reading or writing, call
-<synopsis>
-int lo_open(PGconn *conn, Oid lobjId, int mode);
-</synopsis>
-     <indexterm><primary>lo_open</></>
-     The <parameter>lobjId</parameter> argument specifies the OID of the large
-     object to open.   The <parameter>mode</parameter> bits control whether the
-     object is opened for reading (<symbol>INV_READ</>), writing
-     (<symbol>INV_WRITE</symbol>), or both.
-     (These symbolic constants are defined
-     in the header file <filename>libpq/libpq-fs.h</filename>.)
-     A large object cannot be opened before it is created.
-     <function>lo_open</function> returns a (non-negative) large object
-     descriptor for later use in <function>lo_read</function>,
-     <function>lo_write</function>, <function>lo_lseek</function>,
-     <function>lo_tell</function>, and <function>lo_close</function>.
-     The descriptor is only valid for
-     the duration of the current transaction.
-     On failure, -1 is returned.
-    </para>
-
-    <para>
-     The server currently does not distinguish between modes
-     <symbol>INV_WRITE</symbol> and <symbol>INV_READ</> <literal>|</>
-     <symbol>INV_WRITE</symbol>: you are allowed to read from the descriptor
-     in either case.  However there is a significant difference between
-     these modes and <symbol>INV_READ</> alone: with <symbol>INV_READ</>
-     you cannot write on the descriptor, and the data read from it will
-     reflect the contents of the large object at the time of the transaction
-     snapshot that was active when <function>lo_open</> was executed,
-     regardless of later writes by this or other transactions.  Reading
-     from a descriptor opened with <symbol>INV_WRITE</symbol> returns
-     data that reflects all writes of other committed transactions as well
-     as writes of the current transaction.  This is similar to the behavior
-     of <literal>REPEATABLE READ</> versus <literal>READ COMMITTED</> transaction
-     modes for ordinary SQL <command>SELECT</> commands.
-    </para>
-
-    <para>
-     An example:
-<programlisting>
-inv_fd = lo_open(conn, inv_oid, INV_READ|INV_WRITE);
-</programlisting>
-    </para>
-</sect2>
-
-<sect2 id="lo-write">
-<title>Writing Data to a Large Object</title>
-&pgnotice;
-<para>
-     The function
-<synopsis>
-int lo_write(PGconn *conn, int fd, const char *buf, size_t len);
-</synopsis>
-     <indexterm><primary>lo_write</></> writes
-     <parameter>len</parameter> bytes from <parameter>buf</parameter>
-     to large object descriptor <parameter>fd</>.  The <parameter>fd</parameter>
-     argument must have been returned by a previous
-     <function>lo_open</function>.  The number of bytes actually
-     written is returned.  In the event of an error, the return value
-     is negative.
-</para>
-</sect2>
-
-<sect2 id="lo-read">
-<title>Reading Data from a Large Object</title>
-&pgnotice;
-<para>
-     The function
-<synopsis>
-int lo_read(PGconn *conn, int fd, char *buf, size_t len);
-</synopsis>
-     <indexterm><primary>lo_read</></> reads
-     <parameter>len</parameter> bytes from large object descriptor
-     <parameter>fd</parameter> into <parameter>buf</parameter>. The
-     <parameter>fd</parameter> argument must have been returned by a
-     previous <function>lo_open</function>.  The number of bytes
-     actually read is returned. In the event of an error, the return
-     value is negative.
-</para>
-</sect2>
-
-<sect2 id="lo-seek">
-<title>Seeking in a Large Object</title>
-&pgnotice;
-<para>
-     To change the current read or write location associated with a
-     large object descriptor, call
-<synopsis>
-int lo_lseek(PGconn *conn, int fd, int offset, int whence);
-</synopsis>
-     <indexterm><primary>lo_lseek</></> This function moves the
-     current location pointer for the large object descriptor identified by
-     <parameter>fd</> to the new location specified by
-     <parameter>offset</>.  The valid values for <parameter>whence</>
-     are <symbol>SEEK_SET</> (seek from object start),
-     <symbol>SEEK_CUR</> (seek from current position), and
-     <symbol>SEEK_END</> (seek from object end).  The return value is
-     the new location pointer, or -1 on error.
-</para>
-</sect2>
-
-<sect2 id="lo-tell">
-<title>Obtaining the Seek Position of a Large Object</title>
-&pgnotice;
-<para>
-     To obtain the current read or write location of a large object descriptor,
-     call
-<synopsis>
-int lo_tell(PGconn *conn, int fd);
-</synopsis>
-     <indexterm><primary>lo_tell</></> If there is an error, the
-     return value is negative.
-</para>
-</sect2>
-
-<sect2 id="lo-truncate">
-<title>Truncating a Large Object</title>
-&pgnotice;
-<para>
-     To truncate a large object to a given length, call
-<synopsis>
-int lo_truncate(PGcon *conn, int fd, size_t len);
-</synopsis>
-     <indexterm><primary>lo_truncate</></> truncates the large object
-     descriptor <parameter>fd</> to length <parameter>len</>.  The
-     <parameter>fd</parameter> argument must have been returned by a
-     previous <function>lo_open</function>.  If <parameter>len</> is
-     greater than the current large object length, the large object
-     is extended with null bytes ('\0').
-</para>
-
-<para>
-     The file offset is not changed.
-</para>
-
-<para>
-     On success <function>lo_truncate</function> returns
-     zero.  On error, the return value is negative.
-</para>
-
-<para>
-     <function>lo_truncate</> is new as of <productname>PostgreSQL</productname>
-     8.3; if this function is run against an older server version, it will
-     fail and return a negative value.
-</para>
-</sect2>
-
-<sect2 id="lo-close">
-<title>Closing a Large Object Descriptor</title>
-&pgnotice;
-<para>
-     A large object descriptor can be closed by calling
-<synopsis>
-int lo_close(PGconn *conn, int fd);
-</synopsis>
-     <indexterm><primary>lo_close</></> where <parameter>fd</> is a
-     large object descriptor returned by <function>lo_open</function>.
-     On success, <function>lo_close</function> returns zero.  On
-     error, the return value is negative.
-</para>
-
-<para>
-     Any large  object  descriptors that remain open at the end of a
-     transaction will be closed automatically.
-</para>
-</sect2>
-
-   <sect2 id="lo-unlink">
-    <title>Removing a Large Object</title>
-&pgnotice;
-    <para>
-     To remove a large object from the database, call
-<synopsis>
-int lo_unlink(PGconn *conn, Oid lobjId);
-</synopsis>
-     <indexterm><primary>lo_unlink</></> The
-     <parameter>lobjId</parameter> argument specifies the OID of the
-     large object to remove.  Returns 1 if successful, -1 on failure.
-    </para>
-   </sect2>
-
-</sect1>
-
-<sect1 id="lo-funcs">
-<title>Server-side Functions</title>
-
-&pgnotice;
-  <para>
-   There are server-side functions callable from SQL that correspond to
-   each of the client-side functions described above; indeed, for the
-   most part the client-side functions are simply interfaces to the
-   equivalent server-side functions.  The ones that are actually useful
-   to call via SQL commands are
-   <function>lo_creat</function><indexterm><primary>lo_creat</></>,
-   <function>lo_create</function><indexterm><primary>lo_create</></>,
-   <function>lo_unlink</function><indexterm><primary>lo_unlink</></>,
-   <function>lo_import</function><indexterm><primary>lo_import</></>, and
-   <function>lo_export</function><indexterm><primary>lo_export</></>.
-   Here are examples of their use:
-
-<programlisting>
-CREATE TABLE image (
-    name            text,
-    raster          oid
-);
-
-SELECT lo_creat(-1);       -- returns OID of new, empty large object
-
-SELECT lo_create(43213);   -- attempts to create large object with OID 43213
-
-SELECT lo_unlink(173454);  -- deletes large object with OID 173454
-
-INSERT INTO image (name, raster)
-    VALUES ('beautiful image', lo_import('/etc/motd'));
-
-INSERT INTO image (name, raster)  -- same as above, but specify OID to use
-    VALUES ('beautiful image', lo_import('/etc/motd', 68583));
-
-SELECT lo_export(image.raster, '/tmp/motd') FROM image
-    WHERE name = 'beautiful image';
-</programlisting>
-  </para>
-
-  <para>
-    The server-side <function>lo_import</function> and
-    <function>lo_export</function> functions behave considerably differently
-    from their client-side analogs.  These two functions read and write files
-    in the server's file system, using the permissions of the database's
-    owning user.  Therefore, their use is restricted to superusers.  In
-    contrast, the client-side import and export functions read and write files
-    in the client's file system, using the permissions of the client program.
-    The client-side functions do not require superuser privilege.
-  </para>
-
-</sect1>
-
-<sect1 id="lo-examplesect">
-<title>Example Program</title>
-&pgnotice;
-<para>
-     <xref linkend="lo-example"> is a sample program which shows how the large object
-     interface
-     in <application>libpq</> can be used.  Parts of the program are
-     commented out but are left in the source for  the  reader's
-     benefit.  This program can also be found in
-     <filename>src/test/examples/testlo.c</filename> in the source distribution.
-</para>
-
-  <example id="lo-example">
-   <title>Large Objects with <application>libpq</application> Example Program</title>
-<programlisting><![CDATA[
-/*--------------------------------------------------------------
- *
- * testlo.c--
- *    test using large objects with libpq
- *
- * Copyright (c) 1994, Regents of the University of California
- *
- *--------------------------------------------------------------
- */
-#include <stdio.h>
-#include "libpq-fe.h"
-#include "libpq/libpq-fs.h"
-
-#define BUFSIZE          1024
-
-/*
- * importFile
- *    import file "in_filename" into database as large object "lobjOid"
- *
- */
-Oid
-importFile(PGconn *conn, char *filename)
-{
-    Oid         lobjId;
-    int         lobj_fd;
-    char        buf[BUFSIZE];
-    int         nbytes,
-                tmp;
-    int         fd;
-
-    /*
-     * open the file to be read in
-     */
-    fd = open(filename, O_RDONLY, 0666);
-    if (fd < 0)
-    {                           /* error */
-        fprintf(stderr, "cannot open unix file %s\n", filename);
-    }
-
-    /*
-     * create the large object
-     */
-    lobjId = lo_creat(conn, INV_READ | INV_WRITE);
-    if (lobjId == 0)
-        fprintf(stderr, "cannot create large object\n");
-
-    lobj_fd = lo_open(conn, lobjId, INV_WRITE);
-
-    /*
-     * read in from the Unix file and write to the inversion file
-     */
-    while ((nbytes = read(fd, buf, BUFSIZE)) > 0)
-    {
-        tmp = lo_write(conn, lobj_fd, buf, nbytes);
-        if (tmp < nbytes)
-            fprintf(stderr, "error while reading large object\n");
-    }
-
-    (void) close(fd);
-    (void) lo_close(conn, lobj_fd);
-
-    return lobjId;
-}
-
-void
-pickout(PGconn *conn, Oid lobjId, int start, int len)
-{
-    int         lobj_fd;
-    char       *buf;
-    int         nbytes;
-    int         nread;
-
-    lobj_fd = lo_open(conn, lobjId, INV_READ);
-    if (lobj_fd < 0)
-    {
-        fprintf(stderr, "cannot open large object %d\n",
-                lobjId);
-    }
-
-    lo_lseek(conn, lobj_fd, start, SEEK_SET);
-    buf = malloc(len + 1);
-
-    nread = 0;
-    while (len - nread > 0)
-    {
-        nbytes = lo_read(conn, lobj_fd, buf, len - nread);
-        buf[nbytes] = ' ';
-        fprintf(stderr, ">>> %s", buf);
-        nread += nbytes;
-    }
-    free(buf);
-    fprintf(stderr, "\n");
-    lo_close(conn, lobj_fd);
-}
-
-void
-overwrite(PGconn *conn, Oid lobjId, int start, int len)
-{
-    int         lobj_fd;
-    char       *buf;
-    int         nbytes;
-    int         nwritten;
-    int         i;
-
-    lobj_fd = lo_open(conn, lobjId, INV_WRITE);
-    if (lobj_fd < 0)
-    {
-        fprintf(stderr, "cannot open large object %d\n",
-                lobjId);
-    }
-
-    lo_lseek(conn, lobj_fd, start, SEEK_SET);
-    buf = malloc(len + 1);
-
-    for (i = 0; i < len; i++)
-        buf[i] = 'X';
-    buf[i] = ' ';
-
-    nwritten = 0;
-    while (len - nwritten > 0)
-    {
-        nbytes = lo_write(conn, lobj_fd, buf + nwritten, len - nwritten);
-        nwritten += nbytes;
-    }
-    free(buf);
-    fprintf(stderr, "\n");
-    lo_close(conn, lobj_fd);
-}
-
-/*
- * exportFile
- *    export large object "lobjOid" to file "out_filename"
- *
- */
-void
-exportFile(PGconn *conn, Oid lobjId, char *filename)
-{
-    int         lobj_fd;
-    char        buf[BUFSIZE];
-    int         nbytes,
-                tmp;
-    int         fd;
-
-    /*
-     * open the large object
-     */
-    lobj_fd = lo_open(conn, lobjId, INV_READ);
-    if (lobj_fd < 0)
-    {
-        fprintf(stderr, "cannot open large object %d\n",
-                lobjId);
-    }
-
-    /*
-     * open the file to be written to
-     */
-    fd = open(filename, O_CREAT | O_WRONLY, 0666);
-    if (fd < 0)
-    {                           /* error */
-        fprintf(stderr, "cannot open unix file %s\n",
-                filename);
-    }
-
-    /*
-     * read in from the inversion file and write to the Unix file
-     */
-    while ((nbytes = lo_read(conn, lobj_fd, buf, BUFSIZE)) > 0)
-    {
-        tmp = write(fd, buf, nbytes);
-        if (tmp < nbytes)
-        {
-            fprintf(stderr, "error while writing %s\n",
-                    filename);
-        }
-    }
-
-    (void) lo_close(conn, lobj_fd);
-    (void) close(fd);
-
-    return;
-}
-
-void
-exit_nicely(PGconn *conn)
-{
-    PQfinish(conn);
-    exit(1);
-}
-
-int
-main(int argc, char **argv)
-{
-    char       *in_filename,
-               *out_filename;
-    char       *database;
-    Oid         lobjOid;
-    PGconn     *conn;
-    PGresult   *res;
-
-    if (argc != 4)
-    {
-        fprintf(stderr, "Usage: %s database_name in_filename out_filename\n",
-                argv[0]);
-        exit(1);
-    }
-
-    database = argv[1];
-    in_filename = argv[2];
-    out_filename = argv[3];
-
-    /*
-     * set up the connection
-     */
-    conn = PQsetdb(NULL, NULL, NULL, NULL, database);
-
-    /* check to see that the backend connection was successfully made */
-    if (PQstatus(conn) == CONNECTION_BAD)
-    {
-        fprintf(stderr, "Connection to database '%s' failed.\n", database);
-        fprintf(stderr, "%s", PQerrorMessage(conn));
-        exit_nicely(conn);
-    }
-
-    res = PQexec(conn, "begin");
-    PQclear(res);
-
-    printf("importing file %s\n", in_filename);
-/*  lobjOid = importFile(conn, in_filename); */
-    lobjOid = lo_import(conn, in_filename);
-/*
-    printf("as large object %d.\n", lobjOid);
-
-    printf("picking out bytes 1000-2000 of the large object\n");
-    pickout(conn, lobjOid, 1000, 1000);
-
-    printf("overwriting bytes 1000-2000 of the large object with X's\n");
-    overwrite(conn, lobjOid, 1000, 1000);
-*/
-
-    printf("exporting large object to file %s\n", out_filename);
-/*    exportFile(conn, lobjOid, out_filename); */
-    lo_export(conn, lobjOid, out_filename);
-
-    res = PQexec(conn, "end");
-    PQclear(res);
-    PQfinish(conn);
-    exit(0);
-}
-]]>
-</programlisting>
-</example>
-
-</sect1>
-
-<!## end>
-
-</chapter>
diff --git a/doc-xc/src/sgml/ltree.sgmlin b/doc-xc/src/sgml/ltree.sgmlin
deleted file mode 100644
index 608eaa9263..0000000000
--- a/doc-xc/src/sgml/ltree.sgmlin
+++ /dev/null
@@ -1,700 +0,0 @@
-<!-- doc/src/sgml/ltree.sgml -->
-
-<sect1 id="ltree" xreflabel="ltree">
- <title>ltree</title>
-
- <indexterm zone="ltree">
-  <primary>ltree</primary>
- </indexterm>
-
-&common;
-
- <para>
-  This module implements a data type <type>ltree</> for representing
-  labels of data stored in a hierarchical tree-like structure.
-  Extensive facilities for searching through label trees are provided.
- </para>
-
-<!## XC>
-&xconly;
- <para>
-  Please note that a column of the type <type>ltree</> cannot be a
-  distribution column.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  Please note that a column of the type <type>ltree</> cannot be a
-  distribution column.
- </para>
-<!## end>
-
- <sect2>
-  <title>Definitions</title>
-
-&common;
-  <para>
-   A <firstterm>label</firstterm> is a sequence of alphanumeric characters
-   and underscores (for example, in C locale the characters
-   <literal>A-Za-z0-9_</> are allowed).  Labels must be less than 256 bytes
-   long.
-  </para>
-
-  <para>
-   Examples: <literal>42</>, <literal>Personal_Services</>
-  </para>
-
-  <para>
-   A <firstterm>label path</firstterm> is a sequence of zero or more
-   labels separated by dots, for example <literal>L1.L2.L3</>, representing
-   a path from the root of a hierarchical tree to a particular node.  The
-   length of a label path must be less than 65Kb, but keeping it under 2Kb is
-   preferable.  In practice this is not a major limitation; for example,
-   the longest label path in the DMOZ catalogue (<ulink
-   url="http://www.dmoz.org"></ulink>) is about 240 bytes.
-  </para>
-
-  <para>
-   Example: <literal>Top.Countries.Europe.Russia</literal>
-  </para>
-
-  <para>
-   The <filename>ltree</> module provides several data types:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     <type>ltree</type> stores a label path.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <type>lquery</type> represents a regular-expression-like pattern
-     for matching <type>ltree</> values.  A simple word matches that
-     label within a path.  A star symbol (<literal>*</>) matches zero
-     or more labels.  For example:
-<synopsis>
-foo         <lineannotation>Match the exact label path <literal>foo</></lineannotation>
-*.foo.*     <lineannotation>Match any label path containing the label <literal>foo</></lineannotation>
-*.foo       <lineannotation>Match any label path whose last label is <literal>foo</></lineannotation>
-</synopsis>
-    </para>
-
-    <para>
-     Star symbols can also be quantified to restrict how many labels
-     they can match:
-<synopsis>
-*{<replaceable>n</>}        <lineannotation>Match exactly <replaceable>n</> labels</lineannotation>
-*{<replaceable>n</>,}       <lineannotation>Match at least <replaceable>n</> labels</lineannotation>
-*{<replaceable>n</>,<replaceable>m</>}      <lineannotation>Match at least <replaceable>n</> but not more than <replaceable>m</> labels</lineannotation>
-*{,<replaceable>m</>}       <lineannotation>Match at most <replaceable>m</> labels &mdash; same as </lineannotation> *{0,<replaceable>m</>}
-</synopsis>
-    </para>
-
-    <para>
-     There are several modifiers that can be put at the end of a non-star
-     label in <type>lquery</> to make it match more than just the exact match:
-<synopsis>
-@           <lineannotation>Match case-insensitively, for example <literal>a@</> matches <literal>A</></lineannotation>
-*           <lineannotation>Match any label with this prefix, for example <literal>foo*</> matches <literal>foobar</></lineannotation>
-%           <lineannotation>Match initial underscore-separated words</lineannotation>
-</synopsis>
-     The behavior of <literal>%</> is a bit complicated.  It tries to match
-     words rather than the entire label.  For example
-     <literal>foo_bar%</> matches <literal>foo_bar_baz</> but not
-     <literal>foo_barbaz</>.  If combined with <literal>*</>, prefix
-     matching applies to each word separately, for example
-     <literal>foo_bar%*</> matches <literal>foo1_bar2_baz</> but
-     not <literal>foo1_br2_baz</>.
-    </para>
-
-    <para>
-     Also, you can write several possibly-modified labels separated with
-     <literal>|</> (OR) to match any of those labels, and you can put
-     <literal>!</> (NOT) at the start to match any label that doesn't
-     match any of the alternatives.
-    </para>
-
-    <para>
-     Here's an annotated example of <type>lquery</type>:
-<programlisting>
-Top.*{0,2}.sport*@.!football|tennis.Russ*|Spain
-a.  b.     c.      d.               e.
-</programlisting>
-     This query will match any label path that:
-    </para>
-    <orderedlist numeration='loweralpha'>
-     <listitem>
-      <para>
-       begins with the label <literal>Top</literal>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       and next has zero to two labels before
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       a label beginning with the case-insensitive prefix <literal>sport</literal>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       then a label not matching <literal>football</literal> nor
-       <literal>tennis</literal>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       and then ends with a label beginning with <literal>Russ</literal> or
-       exactly matching <literal>Spain</literal>.
-      </para>
-     </listitem>
-    </orderedlist>
-   </listitem>
-
-   <listitem>
-    <para><type>ltxtquery</type> represents a full-text-search-like
-    pattern for matching <type>ltree</> values.  An
-    <type>ltxtquery</type> value contains words, possibly with the
-    modifiers <literal>@</>, <literal>*</>, <literal>%</> at the end;
-    the modifiers have the same meanings as in <type>lquery</>.
-    Words can be combined with <literal>&amp;</> (AND),
-    <literal>|</> (OR), <literal>!</> (NOT), and parentheses.
-    The key difference from
-    <type>lquery</> is that <type>ltxtquery</type> matches words without
-    regard to their position in the label path.
-    </para>
-
-    <para>
-     Here's an example <type>ltxtquery</type>:
-<programlisting>
-Europe &amp; Russia*@ &amp; !Transportation
-</programlisting>
-     This will match paths that contain the label <literal>Europe</literal> and
-     any label beginning with <literal>Russia</literal> (case-insensitive),
-     but not paths containing the label <literal>Transportation</literal>.
-     The location of these words within the path is not important.
-     Also, when <literal>%</> is used, the word can be matched to any
-     underscore-separated word within a label, regardless of position.
-    </para>
-   </listitem>
-
-  </itemizedlist>
-
-  <para>
-   Note: <type>ltxtquery</> allows whitespace between symbols, but
-   <type>ltree</> and <type>lquery</> do not.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Operators and Functions</title>
-
-&common;
-  <para>
-   Type <type>ltree</> has the usual comparison operators
-   <literal>=</>, <literal>&lt;&gt;</literal>,
-   <literal>&lt;</>, <literal>&gt;</>, <literal>&lt;=</>, <literal>&gt;=</>.
-   Comparison sorts in the order of a tree traversal, with the children
-   of a node sorted by label text.  In addition, the specialized
-   operators shown in <xref linkend="ltree-op-table"> are available.
-  </para>
-
-  <table id="ltree-op-table">
-   <title><type>ltree</> Operators</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Operator</entry>
-      <entry>Returns</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><type>ltree</> <literal>@&gt;</> <type>ltree</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>is left argument an ancestor of right (or equal)?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree</> <literal>&lt;@</> <type>ltree</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>is left argument a descendant of right (or equal)?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree</> <literal>~</> <type>lquery</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does <type>ltree</> match <type>lquery</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>lquery</> <literal>~</> <type>ltree</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does <type>ltree</> match <type>lquery</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree</> <literal>?</> <type>lquery[]</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does <type>ltree</> match any <type>lquery</> in array?</entry>
-     </row>
-
-     <row>
-      <entry><type>lquery[]</> <literal>?</> <type>ltree</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does <type>ltree</> match any <type>lquery</> in array?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree</> <literal>@</> <type>ltxtquery</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does <type>ltree</> match <type>ltxtquery</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltxtquery</> <literal>@</> <type>ltree</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does <type>ltree</> match <type>ltxtquery</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree</> <literal>||</> <type>ltree</></entry>
-      <entry><type>ltree</type></entry>
-      <entry>concatenate <type>ltree</> paths</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree</> <literal>||</> <type>text</></entry>
-      <entry><type>ltree</type></entry>
-      <entry>convert text to <type>ltree</> and concatenate</entry>
-     </row>
-
-     <row>
-      <entry><type>text</> <literal>||</> <type>ltree</></entry>
-      <entry><type>ltree</type></entry>
-      <entry>convert text to <type>ltree</> and concatenate</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree[]</> <literal>@&gt;</> <type>ltree</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does array contain an ancestor of <type>ltree</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree</> <literal>&lt;@</> <type>ltree[]</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does array contain an ancestor of <type>ltree</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree[]</> <literal>&lt;@</> <type>ltree</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does array contain a descendant of <type>ltree</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree</> <literal>@&gt;</> <type>ltree[]</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does array contain a descendant of <type>ltree</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree[]</> <literal>~</> <type>lquery</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does array contain any path matching <type>lquery</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>lquery</> <literal>~</> <type>ltree[]</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does array contain any path matching <type>lquery</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree[]</> <literal>?</> <type>lquery[]</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does <type>ltree</> array contain any path matching any <type>lquery</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>lquery[]</> <literal>?</> <type>ltree[]</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does <type>ltree</> array contain any path matching any <type>lquery</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree[]</> <literal>@</> <type>ltxtquery</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does array contain any path matching <type>ltxtquery</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltxtquery</> <literal>@</> <type>ltree[]</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>does array contain any path matching <type>ltxtquery</>?</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree[]</> <literal>?@&gt;</> <type>ltree</></entry>
-      <entry><type>ltree</type></entry>
-      <entry>first array entry that is an ancestor of <type>ltree</>; NULL if none</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree[]</> <literal>?&lt;@</> <type>ltree</></entry>
-      <entry><type>ltree</type></entry>
-      <entry>first array entry that is a descendant of <type>ltree</>; NULL if none</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree[]</> <literal>?~</> <type>lquery</></entry>
-      <entry><type>ltree</type></entry>
-      <entry>first array entry that matches <type>lquery</>; NULL if none</entry>
-     </row>
-
-     <row>
-      <entry><type>ltree[]</> <literal>?@</> <type>ltxtquery</></entry>
-      <entry><type>ltree</type></entry>
-      <entry>first array entry that matches <type>ltxtquery</>; NULL if none</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The operators <literal>&lt;@</literal>, <literal>@&gt;</literal>,
-   <literal>@</literal> and <literal>~</literal> have analogues
-   <literal>^&lt;@</>, <literal>^@&gt;</>, <literal>^@</>,
-   <literal>^~</literal>, which are the same except they do not use
-   indexes.  These are useful only for testing purposes.
-  </para>
-
-  <para>
-   The available functions are shown in <xref linkend="ltree-func-table">.
-  </para>
-
-  <table id="ltree-func-table">
-   <title><type>ltree</> Functions</title>
-
-   <tgroup cols="5">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Return Type</entry>
-      <entry>Description</entry>
-      <entry>Example</entry>
-      <entry>Result</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><function>subltree(ltree, int start, int end)</function></entry>
-      <entry><type>ltree</type></entry>
-      <entry>subpath of <type>ltree</> from position <parameter>start</> to
-       position <parameter>end</>-1 (counting from 0)</entry>
-      <entry><literal>subltree('Top.Child1.Child2',1,2)</literal></entry>
-      <entry><literal>Child1</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>subpath(ltree, int offset, int len)</function></entry>
-      <entry><type>ltree</type></entry>
-      <entry>subpath of <type>ltree</> starting at position
-       <parameter>offset</>, length <parameter>len</>.
-       If <parameter>offset</> is negative, subpath starts that far from the
-       end of the path.  If <parameter>len</> is negative, leaves that many
-       labels off the end of the path.</entry>
-      <entry><literal>subpath('Top.Child1.Child2',0,2)</literal></entry>
-      <entry><literal>Top.Child1</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>subpath(ltree, int offset)</function></entry>
-      <entry><type>ltree</type></entry>
-      <entry>subpath of <type>ltree</> starting at position
-       <parameter>offset</>, extending to end of path.
-       If <parameter>offset</> is negative, subpath starts that far from the
-       end of the path.</entry>
-      <entry><literal>subpath('Top.Child1.Child2',1)</literal></entry>
-      <entry><literal>Child1.Child2</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>nlevel(ltree)</function></entry>
-      <entry><type>integer</type></entry>
-      <entry>number of labels in path</entry>
-      <entry><literal>nlevel('Top.Child1.Child2')</literal></entry>
-      <entry><literal>3</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>index(ltree a, ltree b)</function></entry>
-      <entry><type>integer</type></entry>
-      <entry>position of first occurrence of <parameter>b</> in
-       <parameter>a</>; -1 if not found</entry>
-      <entry><literal>index('0.1.2.3.5.4.5.6.8.5.6.8','5.6')</literal></entry>
-      <entry><literal>6</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>index(ltree a, ltree b, int offset)</function></entry>
-      <entry><type>integer</type></entry>
-      <entry>position of first occurrence of <parameter>b</> in
-       <parameter>a</>, searching starting at <parameter>offset</>;
-       negative <parameter>offset</> means start <parameter>-offset</>
-       labels from the end of the path</entry>
-      <entry><literal>index('0.1.2.3.5.4.5.6.8.5.6.8','5.6',-4)</literal></entry>
-      <entry><literal>9</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>text2ltree(text)</function></entry>
-      <entry><type>ltree</type></entry>
-      <entry>cast <type>text</> to <type>ltree</></entry>
-      <entry><literal></literal></entry>
-      <entry><literal></literal></entry>
-     </row>
-
-     <row>
-      <entry><function>ltree2text(ltree)</function></entry>
-      <entry><type>text</type></entry>
-      <entry>cast <type>ltree</> to <type>text</></entry>
-      <entry><literal></literal></entry>
-      <entry><literal></literal></entry>
-     </row>
-
-     <row>
-      <entry><function>lca(ltree, ltree, ...)</function></entry>
-      <entry><type>ltree</type></entry>
-      <entry>lowest common ancestor, i.e., longest common prefix of paths
-       (up to 8 arguments supported)</entry>
-      <entry><literal>lca('1.2.2.3','1.2.3.4.5.6')</literal></entry>
-      <entry><literal>1.2</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>lca(ltree[])</function></entry>
-      <entry><type>ltree</type></entry>
-      <entry>lowest common ancestor, i.e., longest common prefix of paths</entry>
-      <entry><literal>lca(array['1.2.2.3'::ltree,'1.2.3'])</literal></entry>
-      <entry><literal>1.2</literal></entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
- </sect2>
-
- <sect2>
-  <title>Indexes</title>
-&common;
-  <para>
-   <filename>ltree</> supports several types of indexes that can speed
-   up the indicated operators:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     B-tree index over <type>ltree</>:
-     <literal>&lt;</>, <literal>&lt;=</>, <literal>=</>,
-     <literal>&gt;=</>, <literal>&gt;</literal>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     GiST index over <type>ltree</>:
-     <literal>&lt;</>, <literal>&lt;=</>, <literal>=</>,
-     <literal>&gt;=</>, <literal>&gt;</>,
-     <literal>@&gt;</>, <literal>&lt;@</>,
-     <literal>@</>, <literal>~</>, <literal>?</literal>
-    </para>
-    <para>
-     Example of creating such an index:
-    </para>
-<programlisting>
-CREATE INDEX path_gist_idx ON test USING GIST (path);
-</programlisting>
-   </listitem>
-   <listitem>
-    <para>
-     GiST index over <type>ltree[]</>:
-     <literal>ltree[] &lt;@ ltree</>, <literal>ltree @&gt; ltree[]</>,
-     <literal>@</>, <literal>~</>, <literal>?</literal>
-    </para>
-    <para>
-     Example of creating such an index:
-    </para>
-<programlisting>
-CREATE INDEX path_gist_idx ON test USING GIST (array_path);
-</programlisting>
-    <para>
-     Note: This index type is lossy.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect2>
-
- <sect2>
-  <title>Example</title>
-
-&common;
-  <para>
-   This example uses the following data (also available in file
-   <filename>contrib/ltree/ltreetest.sql</> in the source distribution):
-  </para>
-
-<programlisting>
-CREATE TABLE test (path ltree);
-INSERT INTO test VALUES ('Top');
-INSERT INTO test VALUES ('Top.Science');
-INSERT INTO test VALUES ('Top.Science.Astronomy');
-INSERT INTO test VALUES ('Top.Science.Astronomy.Astrophysics');
-INSERT INTO test VALUES ('Top.Science.Astronomy.Cosmology');
-INSERT INTO test VALUES ('Top.Hobbies');
-INSERT INTO test VALUES ('Top.Hobbies.Amateurs_Astronomy');
-INSERT INTO test VALUES ('Top.Collections');
-INSERT INTO test VALUES ('Top.Collections.Pictures');
-INSERT INTO test VALUES ('Top.Collections.Pictures.Astronomy');
-INSERT INTO test VALUES ('Top.Collections.Pictures.Astronomy.Stars');
-INSERT INTO test VALUES ('Top.Collections.Pictures.Astronomy.Galaxies');
-INSERT INTO test VALUES ('Top.Collections.Pictures.Astronomy.Astronauts');
-CREATE INDEX path_gist_idx ON test USING gist(path);
-CREATE INDEX path_idx ON test USING btree(path);
-</programlisting>
-
-  <para>
-   Now, we have a table <structname>test</> populated with data describing
-   the hierarchy shown below:
-  </para>
-
-<literallayout class="monospaced">
-                        Top
-                     /   |  \
-             Science Hobbies Collections
-                 /       |              \
-        Astronomy   Amateurs_Astronomy Pictures
-           /  \                            |
-Astrophysics  Cosmology                Astronomy
-                                        /  |    \
-                                 Galaxies Stars Astronauts
-</literallayout>
-
-  <para>
-   We can do inheritance:
-<screen>
-ltreetest=&gt; SELECT path FROM test WHERE path &lt;@ 'Top.Science';
-                path
-------------------------------------
- Top.Science
- Top.Science.Astronomy
- Top.Science.Astronomy.Astrophysics
- Top.Science.Astronomy.Cosmology
-(4 rows)
-</screen>
-  </para>
-
-  <para>
-   Here are some examples of path matching:
-<screen>
-ltreetest=&gt; SELECT path FROM test WHERE path ~ '*.Astronomy.*';
-                     path
------------------------------------------------
- Top.Science.Astronomy
- Top.Science.Astronomy.Astrophysics
- Top.Science.Astronomy.Cosmology
- Top.Collections.Pictures.Astronomy
- Top.Collections.Pictures.Astronomy.Stars
- Top.Collections.Pictures.Astronomy.Galaxies
- Top.Collections.Pictures.Astronomy.Astronauts
-(7 rows)
-
-ltreetest=&gt; SELECT path FROM test WHERE path ~ '*.!pictures@.*.Astronomy.*';
-                path
-------------------------------------
- Top.Science.Astronomy
- Top.Science.Astronomy.Astrophysics
- Top.Science.Astronomy.Cosmology
-(3 rows)
-</screen>
-  </para>
-
-  <para>
-   Here are some examples of full text search:
-<screen>
-ltreetest=&gt; SELECT path FROM test WHERE path @ 'Astro*% &amp; !pictures@';
-                path
-------------------------------------
- Top.Science.Astronomy
- Top.Science.Astronomy.Astrophysics
- Top.Science.Astronomy.Cosmology
- Top.Hobbies.Amateurs_Astronomy
-(4 rows)
-
-ltreetest=&gt; SELECT path FROM test WHERE path @ 'Astro* &amp; !pictures@';
-                path
-------------------------------------
- Top.Science.Astronomy
- Top.Science.Astronomy.Astrophysics
- Top.Science.Astronomy.Cosmology
-(3 rows)
-</screen>
-  </para>
-
-  <para>
-   Path construction using functions:
-<screen>
-ltreetest=&gt; SELECT subpath(path,0,2)||'Space'||subpath(path,2) FROM test WHERE path &lt;@ 'Top.Science.Astronomy';
-                 ?column?
-------------------------------------------
- Top.Science.Space.Astronomy
- Top.Science.Space.Astronomy.Astrophysics
- Top.Science.Space.Astronomy.Cosmology
-(3 rows)
-</screen>
-  </para>
-
-  <para>
-   We could simplify this by creating a SQL function that inserts a label
-   at a specified position in a path:
-<screen>
-CREATE FUNCTION ins_label(ltree, int, text) RETURNS ltree
-    AS 'select subpath($1,0,$2) || $3 || subpath($1,$2);'
-    LANGUAGE SQL IMMUTABLE;
-
-ltreetest=&gt; SELECT ins_label(path,2,'Space') FROM test WHERE path &lt;@ 'Top.Science.Astronomy';
-                ins_label
-------------------------------------------
- Top.Science.Space.Astronomy
- Top.Science.Space.Astronomy.Astrophysics
- Top.Science.Space.Astronomy.Cosmology
-(3 rows)
-</screen>
-  </para>
- </sect2>
-
- <sect2>
-  <title>Authors</title>
-
-  <para>
-   All work was done by Teodor Sigaev (<email>[email protected]</email>) and
-   Oleg Bartunov (<email>[email protected]</email>). See
-   <ulink url="http://www.sai.msu.su/~megera/postgres/gist/"></ulink> for
-   additional information. Authors would like to thank Eugeny Rodichev for
-   helpful discussions. Comments and bug reports are welcome.
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/maintenance.sgmlin b/doc-xc/src/sgml/maintenance.sgmlin
deleted file mode 100644
index 40d350603c..0000000000
--- a/doc-xc/src/sgml/maintenance.sgmlin
+++ /dev/null
@@ -1,1129 +0,0 @@
-<!-- doc/src/sgml/maintenance.sgml -->
-
-<chapter id="maintenance">
- <title>Routine Database Maintenance Tasks</title>
-
- <indexterm zone="maintenance">
-  <primary>maintenance</primary>
- </indexterm>
-
- <indexterm zone="maintenance">
-  <primary>routine maintenance</primary>
- </indexterm>
-
-<!## XC>
-&xconly;
-  <para>
-   Please note that this chapter describes database maintenance task
-   of individual Coordinator and Datanode.  Please remember that these
-   tasks should be done for each of them.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   This chapter describes database maintenance tasks
-   of individual Coordinators and Datanodes.  
-  </para>
-<!## end>
-
-&common;
-
-<!## PG>
-  <para>
-   <productname>PostgreSQL</>, like any database software, requires that certain tasks
-   be performed regularly to achieve optimum performance. The tasks
-   discussed here are <emphasis>required</emphasis>, but they
-   are repetitive in nature and can easily be automated using standard
-   tools such as <application>cron</application> scripts or
-   Windows' <application>Task Scheduler</>.  It is the database
-   administrator's responsibility to set up appropriate scripts, and to
-   check that they execute successfully.
-  </para>
-<!## end>
-<!## XC>
-  <para>
-   <productname>Postgres-XC</> inherits most of its fundamentals from <productname>PostgreSQL</>.   Like any database software, requires that certain tasks
-   be performed regularly to achieve optimum performance. The tasks
-   discussed here are <emphasis>required</emphasis>, but they
-   are repetitive in nature and can easily be automated using standard
-   tools such as <application>cron</application> scripts or
-   Windows' <application>Task Scheduler</>.  It is the database
-   administrator's responsibility to set up appropriate scripts, and to
-   check that they execute successfully.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   <productname>Postgres-XL</> inherits most of its fundamentals from <productname>PostgreSQL</>.   Like any database software, it requires that certain tasks
-   be performed regularly to achieve optimum performance. The tasks
-   discussed here are <emphasis>required</emphasis>, but they
-   are repetitive in nature and can easily be automated using standard
-   tools such as <application>cron</application> scripts or
-   Windows' <application>Task Scheduler</>.  It is the database
-   administrator's responsibility to set up appropriate scripts, and to
-   check that they execute successfully.
-  </para>
-<!## end>
-
-<!## PG>
-  <para>
-   One obvious maintenance task is the creation of backup copies of the data on a
-   regular schedule.  Without a recent backup, you have no chance of recovery
-   after a catastrophe (disk failure, fire, mistakenly dropping a critical
-   table, etc.).  The backup and recovery mechanisms available in
-   <productname>PostgreSQL</productname> are discussed at length in
-   <xref linkend="backup">.
-  </para>
-<!## end>
-<!## XC>
-  <para>
-   One obvious maintenance task is the creation of backup copies of the data on a
-   regular schedule.  Without a recent backup, you have no chance of recovery
-   after a catastrophe (disk failure, fire, mistakenly dropping a critical
-   table, etc.).  The backup and recovery mechanisms available in
-   <productname>Postgres-XC</productname> are discussed at length in
-   <xref linkend="backup">.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   One obvious maintenance task is the creation of backup copies of the data on a
-   regular schedule.  Without a recent backup, you have no chance of recovery
-   after a catastrophe (disk failure, fire, mistakenly dropping a critical
-   table, etc.).  The backup and recovery mechanisms available in
-   <productname>Postgres-XL</productname> are discussed at length in
-   <xref linkend="backup">.
-  </para>
-<!## end>
-
-  <para>
-   The other main category of maintenance task is periodic <quote>vacuuming</>
-   of the database.  This activity is discussed in
-   <xref linkend="routine-vacuuming">.  Closely related to this is updating
-   the statistics that will be used by the query planner, as discussed in
-   <xref linkend="vacuum-for-statistics">.
-  </para>
-
-  <para>
-   Another task that might need periodic attention is log file management.
-   This is discussed in <xref linkend="logfile-maintenance">.
-  </para>
-
-  <para>
-   <ulink
-   url="http://bucardo.org/wiki/Check_postgres"><application>check_postgres</></ulink>
-   is available for monitoring database health and reporting unusual
-   conditions.  <application>check_postgres</> integrates with
-   Nagios and MRTG, but can be run standalone too.
-  </para>
-
-<!## PG>
-  <para>
-   <productname>PostgreSQL</productname> is low-maintenance compared
-   to some other database management systems.  Nonetheless,
-   appropriate attention to these tasks will go far towards ensuring a
-   pleasant and productive experience with the system.
-  </para>
-<!## end>
-
- <sect1 id="routine-vacuuming">
-  <title>Routine Vacuuming</title>
-
-  <indexterm zone="routine-vacuuming">
-   <primary>vacuum</primary>
-  </indexterm>
-<!## XC>
-&xconly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-
-&common;
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> databases require periodic
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> databases require periodic
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> databases require periodic
-<!## end>
-   maintenance known as <firstterm>vacuuming</>.  For many installations, it
-   is sufficient to let vacuuming be performed by the <firstterm>autovacuum
-   daemon</>, which is described in <xref linkend="autovacuum">.  You might
-   need to adjust the autovacuuming parameters described there to obtain best
-   results for your situation.  Some database administrators will want to
-   supplement or replace the daemon's activities with manually-managed
-   <command>VACUUM</> commands, which typically are executed according to a
-   schedule by <application>cron</application> or <application>Task
-   Scheduler</> scripts.  To set up manually-managed vacuuming properly,
-   it is essential to understand the issues discussed in the next few
-   subsections.  Administrators who rely on autovacuuming may still wish
-   to skim this material to help them understand and adjust autovacuuming.
-  </para>
-
-  <sect2 id="vacuum-basics">
-   <title>Vacuuming Basics</title>
-<!## XC>
-&xconly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-
-&common;
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname>'s
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>'s
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>'s
-<!## end>
-    <xref linkend="sql-vacuum"> command has to
-    process each table on a regular basis for several reasons:
-
-    <orderedlist>
-     <listitem>
-      <simpara>To recover or reuse disk space occupied by updated or deleted
-      rows.</simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>To update data statistics used by the
-<!## PG>
-      <productname>PostgreSQL</productname> query planner.</simpara>
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname> query planner.</simpara>
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname> query planner.</simpara>
-<!## end>
-     </listitem>
-
-     <listitem>
-      <simpara>To protect against loss of very old data due to
-      <firstterm>transaction ID wraparound</>.</simpara>
-     </listitem>
-    </orderedlist>
-
-    Each of these reasons dictates performing <command>VACUUM</> operations
-    of varying frequency and scope, as explained in the following subsections.
-   </para>
-
-   <para>
-    There are two variants of <command>VACUUM</>: standard <command>VACUUM</>
-    and <command>VACUUM FULL</>.  <command>VACUUM FULL</> can reclaim more
-    disk space but runs much more slowly.  Also,
-    the standard form of <command>VACUUM</> can run in parallel with production
-    database operations.  (Commands such as <command>SELECT</command>,
-    <command>INSERT</command>, <command>UPDATE</command>, and
-    <command>DELETE</command> will continue to function normally, though you
-    will not be able to modify the definition of a table with commands such as
-    <command>ALTER TABLE</command> while it is being vacuumed.)
-    <command>VACUUM FULL</> requires exclusive lock on the table it is
-    working on, and therefore cannot be done in parallel with other use
-    of the table.  Generally, therefore,
-    administrators should strive to use standard <command>VACUUM</> and
-    avoid <command>VACUUM FULL</>.
-   </para>
-
-   <para>
-    <command>VACUUM</command> creates a substantial amount of I/O
-    traffic, which can cause poor performance for other active sessions.
-    There are configuration parameters that can be adjusted to reduce the
-    performance impact of background vacuuming &mdash; see
-    <xref linkend="runtime-config-resource-vacuum-cost">.
-   </para>
-  </sect2>
-
-  <sect2 id="vacuum-for-space-recovery">
-   <title>Recovering Disk Space</title>
-
-   <indexterm zone="vacuum-for-space-recovery">
-    <primary>disk space</primary>
-   </indexterm>
-<!## XC>
-&xconly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-
-&common;
-
-   <para>
-<!## PG>
-    In <productname>PostgreSQL</productname>, an
-<!## end>
-<!## XC>
-    In <productname>Postgres-XC</productname>, an
-<!## end>
-<!## XL>
-    In <productname>Postgres-XL</productname>, an
-<!## end>
-    <command>UPDATE</> or <command>DELETE</> of a row does not
-    immediately remove the old version of the row.
-    This approach is necessary to gain the benefits of multiversion
-    concurrency control (<acronym>MVCC</>, see <xref linkend="mvcc">): the row version
-    must not be deleted while it is still potentially visible to other
-    transactions. But eventually, an outdated or deleted row version is no
-    longer of interest to any transaction. The space it occupies must then be
-    reclaimed for reuse by new rows, to avoid unbounded growth of disk
-    space requirements. This is done by running <command>VACUUM</>.
-   </para>
-
-   <para>
-    The standard form of <command>VACUUM</command> removes dead row
-    versions in tables and indexes and marks the space available for
-    future reuse.  However, it will not return the space to the operating
-    system, except in the special case where one or more pages at the
-    end of a table become entirely free and an exclusive table lock can be
-    easily obtained.  In contrast, <command>VACUUM FULL</> actively compacts
-    tables by writing a complete new version of the table file with no dead
-    space.  This minimizes the size of the table, but can take a long time.
-    It also requires extra disk space for the new copy of the table, until
-    the operation completes.
-   </para>
-
-   <para>
-    The usual goal of routine vacuuming is to do standard <command>VACUUM</>s
-    often enough to avoid needing <command>VACUUM FULL</>.  The
-    autovacuum daemon attempts to work this way, and in fact will
-    never issue <command>VACUUM FULL</>.  In this approach, the idea
-    is not to keep tables at their minimum size, but to maintain steady-state
-    usage of disk space: each table occupies space equivalent to its
-    minimum size plus however much space gets used up between vacuumings.
-    Although <command>VACUUM FULL</> can be used to shrink a table back
-    to its minimum size and return the disk space to the operating system,
-    there is not much point in this if the table will just grow again in the
-    future.  Thus, moderately-frequent standard <command>VACUUM</> runs are a
-    better approach than infrequent <command>VACUUM FULL</> runs for
-    maintaining heavily-updated tables.
-   </para>
-
-   <para>
-    Some administrators prefer to schedule vacuuming themselves, for example
-    doing all the work at night when load is low.
-    The difficulty with doing vacuuming according to a fixed schedule
-    is that if a table has an unexpected spike in update activity, it may
-    get bloated to the point that <command>VACUUM FULL</> is really necessary
-    to reclaim space.  Using the autovacuum daemon alleviates this problem,
-    since the daemon schedules vacuuming dynamically in response to update
-    activity.  It is unwise to disable the daemon completely unless you
-    have an extremely predictable workload.  One possible compromise is
-    to set the daemon's parameters so that it will only react to unusually
-    heavy update activity, thus keeping things from getting out of hand,
-    while scheduled <command>VACUUM</>s are expected to do the bulk of the
-    work when the load is typical.
-   </para>
-
-   <para>
-    For those not using autovacuum, a typical approach is to schedule a
-    database-wide <command>VACUUM</> once a day during a low-usage period,
-    supplemented by more frequent vacuuming of heavily-updated tables as
-    necessary. (Some installations with extremely high update rates vacuum
-    their busiest tables as often as once every few minutes.) If you have
-    multiple databases in a cluster, don't forget to
-    <command>VACUUM</command> each one; the program <xref
-    linkend="app-vacuumdb"> might be helpful.
-   </para>
-
-   <tip>
-   <para>
-    Plain <command>VACUUM</> may not be satisfactory when
-    a table contains large numbers of dead row versions as a result of
-    massive update or delete activity.  If you have such a table and
-    you need to reclaim the excess disk space it occupies, you will need
-    to use <command>VACUUM FULL</>, or alternatively
-    <xref linkend="sql-cluster">
-    or one of the table-rewriting variants of
-    <xref linkend="sql-altertable">.
-    These commands rewrite an entire new copy of the table and build
-    new indexes for it.  All these options require exclusive lock.  Note that
-    they also temporarily use extra disk space approximately equal to the size
-    of the table, since the old copies of the table and indexes can't be
-    released until the new ones are complete.
-   </para>
-   </tip>
-
-   <tip>
-   <para>
-    If you have a table whose entire contents are deleted on a periodic
-    basis, consider doing it with
-    <xref linkend="sql-truncate"> rather
-    than using <command>DELETE</command> followed by
-    <command>VACUUM</command>. <command>TRUNCATE</command> removes the
-    entire content of the table immediately, without requiring a
-    subsequent <command>VACUUM</command> or <command>VACUUM
-    FULL</command> to reclaim the now-unused disk space.
-    The disadvantage is that strict MVCC semantics are violated.
-   </para>
-   </tip>
-  </sect2>
-
-  <sect2 id="vacuum-for-statistics">
-   <title>Updating Planner Statistics</title>
-
-   <indexterm zone="vacuum-for-statistics">
-    <primary>statistics</primary>
-    <secondary>of the planner</secondary>
-   </indexterm>
-
-   <indexterm zone="vacuum-for-statistics">
-    <primary>ANALYZE</primary>
-   </indexterm>
-<!## XC>
-&xconly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-
-&common;
-
-   <para>
-<!## PG>
-    The <productname>PostgreSQL</productname> query planner relies on
-<!## end>
-<!## XC>
-    As in <productname>PostgreSQL</>, <productname>Postgres-XC</productname> query planner relies on
-<!## end>
-<!## XL>
-    As in <productname>PostgreSQL</>, <productname>Postgres-XL</productname> query planner relies on
-<!## end>
-    statistical information about the contents of tables in order to
-    generate good plans for queries.  These statistics are gathered by
-    the <xref linkend="sql-analyze"> command,
-    which can be invoked by itself or
-    as an optional step in <command>VACUUM</>.  It is important to have
-    reasonably accurate statistics, otherwise poor choices of plans might
-    degrade database performance.
-   </para>
-
-   <para>
-    The autovacuum daemon, if enabled, will automatically issue
-    <command>ANALYZE</> commands whenever the content of a table has
-    changed sufficiently.  However, administrators might prefer to rely
-    on manually-scheduled <command>ANALYZE</> operations, particularly
-    if it is known that update activity on a table will not affect the
-    statistics of <quote>interesting</> columns.  The daemon schedules
-    <command>ANALYZE</> strictly as a function of the number of rows
-    inserted or updated; it has no knowledge of whether that will lead
-    to meaningful statistical changes.
-   </para>
-
-   <para>
-    As with vacuuming for space recovery, frequent updates of statistics
-    are more useful for heavily-updated tables than for seldom-updated
-    ones. But even for a heavily-updated table, there might be no need for
-    statistics updates if the statistical distribution of the data is
-    not changing much. A simple rule of thumb is to think about how much
-    the minimum and maximum values of the columns in the table change.
-    For example, a <type>timestamp</type> column that contains the time
-    of row update will have a constantly-increasing maximum value as
-    rows are added and updated; such a column will probably need more
-    frequent statistics updates than, say, a column containing URLs for
-    pages accessed on a website. The URL column might receive changes just
-    as often, but the statistical distribution of its values probably
-    changes relatively slowly.
-   </para>
-
-   <para>
-    It is possible to run <command>ANALYZE</> on specific tables and even
-    just specific columns of a table, so the flexibility exists to update some
-    statistics more frequently than others if your application requires it.
-    In practice, however, it is usually best to just analyze the entire
-    database, because it is a fast operation.  <command>ANALYZE</> uses a
-    statistically random sampling of the rows of a table rather than reading
-    every single row.
-   </para>
-
-   <tip>
-    <para>
-     Although per-column tweaking of <command>ANALYZE</> frequency might not be
-     very productive, you might find it worthwhile to do per-column
-     adjustment of the level of detail of the statistics collected by
-     <command>ANALYZE</>.  Columns that are heavily used in <literal>WHERE</>
-     clauses and have highly irregular data distributions might require a
-     finer-grain data histogram than other columns.  See <command>ALTER TABLE
-     SET STATISTICS</>, or change the database-wide default using the <xref
-     linkend="guc-default-statistics-target"> configuration parameter.
-    </para>
-
-    <para>
-     Also, by default there is limited information available about
-     the selectivity of functions.  However, if you create an expression
-     index that uses a function call, useful statistics will be
-     gathered about the function, which can greatly improve query
-     plans that use the expression index.
-    </para>
-   </tip>
-  </sect2>
-
-  <sect2 id="vacuum-for-wraparound">
-   <title>Preventing Transaction ID Wraparound Failures</title>
-
-   <indexterm zone="vacuum-for-wraparound">
-    <primary>transaction ID</primary>
-    <secondary>wraparound</secondary>
-   </indexterm>
-<!## XC>
-&xconly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-
-&common;
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname>'s MVCC transaction semantics
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>'s MVCC transaction semantics
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>'s MVCC transaction semantics
-<!## end>
-    depend on being able to compare transaction ID (<acronym>XID</>)
-    numbers: a row version with an insertion XID greater than the current
-    transaction's XID is <quote>in the future</> and should not be visible
-    to the current transaction.  But since transaction IDs have limited size
-    (32 bits) a cluster that runs for a long time (more
-    than 4 billion transactions) would suffer <firstterm>transaction ID
-    wraparound</>: the XID counter wraps around to zero, and all of a sudden
-    transactions that were in the past appear to be in the future &mdash; which
-    means their output become invisible.  In short, catastrophic data loss.
-    (Actually the data is still there, but that's cold comfort if you cannot
-    get at it.)  To avoid this, it is necessary to vacuum every table
-    in every database at least once every two billion transactions.
-   </para>
-
-<!## XC>
-&xconly;
-   <para>
-    Please note that <productname>Postgres-XC</>'s transaction is
-    called global transaction ID (<acronym>GXID</>) and is supplied by
-    global transaction manager (<acronym>GTM</>).
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Please note that <productname>Postgres-XL</>'s transaction is
-    called global transaction ID (<acronym>GXID</>) and is supplied by
-    global transaction manager (<acronym>GTM</>).
-   </para>
-<!## end>
-&common;
-   <para>
-    The reason that periodic vacuuming solves the problem is that
-<!## PG>
-    <productname>PostgreSQL</productname> reserves a special XID
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> reserves a special XID
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> reserves a special XID
-<!## end>
-    as <literal>FrozenXID</>.  This XID does not follow the normal XID
-    comparison rules and is always considered older
-    than every normal XID. Normal XIDs are
-    compared using modulo-2<superscript>31</> arithmetic. This means
-    that for every normal XID, there are two billion XIDs that are
-    <quote>older</> and two billion that are <quote>newer</>; another
-    way to say it is that the normal XID space is circular with no
-    endpoint. Therefore, once a row version has been created with a particular
-    normal XID, the row version will appear to be <quote>in the past</> for
-    the next two billion transactions, no matter which normal XID we are
-    talking about. If the row version still exists after more than two billion
-    transactions, it will suddenly appear to be in the future. To
-    prevent this, old row versions must be reassigned the XID
-    <literal>FrozenXID</> sometime before they reach the
-    two-billion-transactions-old mark. Once they are assigned this
-    special XID, they will appear to be <quote>in the past</> to all
-    normal transactions regardless of wraparound issues, and so such
-    row versions will be valid until deleted, no matter how long that is.
-    This reassignment of old XIDs is handled by <command>VACUUM</>.
-   </para>
-
-   <para>
-    <xref linkend="guc-vacuum-freeze-min-age">
-    controls how old an XID value has to be before it's replaced with
-    <literal>FrozenXID</>.  Larger values of this setting
-    preserve transactional information longer, while smaller values increase
-    the number of transactions that can elapse before the table must be
-    vacuumed again.
-   </para>
-
-   <para>
-    <command>VACUUM</> normally skips pages that don't have any dead row
-    versions, but those pages might still have row versions with old XID
-    values.  To ensure all old XIDs have been replaced by
-    <literal>FrozenXID</>, a scan of the whole table is needed.
-    <xref linkend="guc-vacuum-freeze-table-age"> controls when
-    <command>VACUUM</> does that: a whole table sweep is forced if
-    the table hasn't been fully scanned for <varname>vacuum_freeze_table_age</>
-    minus <varname>vacuum_freeze_min_age</> transactions. Setting it to 0
-    forces <command>VACUUM</> to always scan all pages, effectively ignoring
-    the visibility map.
-   </para>
-
-   <para>
-    The maximum time that a table can go unvacuumed is two billion
-    transactions minus the <varname>vacuum_freeze_min_age</> value at
-    the time <command>VACUUM</> last scanned the whole table.  If it were to go
-    unvacuumed for longer than
-    that, data loss could result.  To ensure that this does not happen,
-    autovacuum is invoked on any table that might contain XIDs older than the
-    age specified by the configuration parameter <xref
-    linkend="guc-autovacuum-freeze-max-age">.  (This will happen even if
-    autovacuum is disabled.)
-   </para>
-
-   <para>
-    This implies that if a table is not otherwise vacuumed,
-    autovacuum will be invoked on it approximately once every
-    <varname>autovacuum_freeze_max_age</> minus
-    <varname>vacuum_freeze_min_age</> transactions.
-    For tables that are regularly vacuumed for space reclamation purposes,
-    this is of little importance.  However, for static tables
-    (including tables that receive inserts, but no updates or deletes),
-    there is no need to vacuum for space reclamation, so it can
-    be useful to try to maximize the interval between forced autovacuums
-    on very large static tables.  Obviously one can do this either by
-    increasing <varname>autovacuum_freeze_max_age</> or decreasing
-    <varname>vacuum_freeze_min_age</>.
-   </para>
-
-   <para>
-    The effective maximum for <varname>vacuum_freeze_table_age</> is 0.95 *
-    <varname>autovacuum_freeze_max_age</>; a setting higher than that will be
-    capped to the maximum. A value higher than
-    <varname>autovacuum_freeze_max_age</> wouldn't make sense because an
-    anti-wraparound autovacuum would be triggered at that point anyway, and
-    the 0.95 multiplier leaves some breathing room to run a manual
-    <command>VACUUM</> before that happens.  As a rule of thumb,
-    <command>vacuum_freeze_table_age</> should be set to a value somewhat
-    below <varname>autovacuum_freeze_max_age</>, leaving enough gap so that
-    a regularly scheduled <command>VACUUM</> or an autovacuum triggered by
-    normal delete and update activity is run in that window.  Setting it too
-    close could lead to anti-wraparound autovacuums, even though the table
-    was recently vacuumed to reclaim space, whereas lower values lead to more
-    frequent whole-table scans.
-   </para>
-
-   <para>
-    The sole disadvantage of increasing <varname>autovacuum_freeze_max_age</>
-    (and <varname>vacuum_freeze_table_age</> along with it)
-    is that the <filename>pg_clog</> subdirectory of the database cluster
-    will take more space, because it must store the commit status of all
-    transactions back to the <varname>autovacuum_freeze_max_age</> horizon.
-    The commit status uses two bits per transaction, so if
-    <varname>autovacuum_freeze_max_age</> is set to its maximum allowed value of
-    a little less than two billion, <filename>pg_clog</> can be expected to
-    grow to about half a gigabyte.  If this is trivial compared to your
-    total database size, setting <varname>autovacuum_freeze_max_age</> to
-    its maximum allowed value is recommended.  Otherwise, set it depending
-    on what you are willing to allow for <filename>pg_clog</> storage.
-    (The default, 200 million transactions, translates to about 50MB of
-    <filename>pg_clog</> storage.)
-   </para>
-
-   <para>
-    One disadvantage of decreasing <varname>vacuum_freeze_min_age</> is that
-    it might cause <command>VACUUM</> to do useless work: changing a table row's
-    XID to <literal>FrozenXID</> is a waste of time if the row is modified
-    soon thereafter (causing it to acquire a new XID).  So the setting should
-    be large enough that rows are not frozen until they are unlikely to change
-    any more.  Another disadvantage of decreasing this setting is
-    that details about exactly which transaction inserted or modified a
-    row will be lost sooner.  This information sometimes comes in handy,
-    particularly when trying to analyze what went wrong after a database
-    failure.  For these two reasons, decreasing this setting is not
-    recommended except for completely static tables.
-   </para>
-
-   <para>
-    To track the age of the oldest XIDs in a database,
-    <command>VACUUM</> stores XID
-    statistics in the system tables <structname>pg_class</> and
-    <structname>pg_database</>.  In particular,
-    the <structfield>relfrozenxid</> column of a table's
-    <structname>pg_class</> row contains the freeze cutoff XID that was used
-    by the last whole-table <command>VACUUM</> for that table.  All normal
-    XIDs older than this cutoff XID are guaranteed to have been replaced by
-    <literal>FrozenXID</> within the table.  Similarly,
-    the <structfield>datfrozenxid</> column of a database's
-    <structname>pg_database</> row is a lower bound on the normal XIDs
-    appearing in that database &mdash; it is just the minimum of the
-    per-table <structfield>relfrozenxid</> values within the database.
-    A convenient way to
-    examine this information is to execute queries such as:
-
-<programlisting>
-SELECT relname, age(relfrozenxid) FROM pg_class WHERE relkind = 'r';
-SELECT datname, age(datfrozenxid) FROM pg_database;
-</programlisting>
-
-    The <literal>age</> column measures the number of transactions from the
-    cutoff XID to the current transaction's XID.
-   </para>
-
-   <para>
-    <command>VACUUM</> normally
-    only scans pages that have been modified since the last vacuum, but
-    <structfield>relfrozenxid</> can only be advanced when the whole table is
-    scanned. The whole table is scanned when <structfield>relfrozenxid</> is
-    more than <varname>vacuum_freeze_table_age</> transactions old, when
-    <command>VACUUM</>'s <literal>FREEZE</> option is used, or when all pages
-    happen to
-    require vacuuming to remove dead row versions. When <command>VACUUM</>
-    scans the whole table, after it's finished <literal>age(relfrozenxid)</>
-    should be a little more than the <varname>vacuum_freeze_min_age</> setting
-    that was used (more by the number of transactions started since the
-    <command>VACUUM</> started).  If no whole-table-scanning <command>VACUUM</>
-    is issued on the table until <varname>autovacuum_freeze_max_age</> is
-    reached, an autovacuum will soon be forced for the table.
-   </para>
-
-   <para>
-    If for some reason autovacuum fails to clear old XIDs from a table,
-    the system will begin to emit warning messages like this when the
-    database's oldest XIDs reach ten million transactions from the wraparound
-    point:
-
-<programlisting>
-WARNING:  database "mydb" must be vacuumed within 177009986 transactions
-HINT:  To avoid a database shutdown, execute a database-wide VACUUM in "mydb".
-</programlisting>
-
-    (A manual <command>VACUUM</> should fix the problem, as suggested by the
-    hint; but note that the <command>VACUUM</> must be performed by a
-    superuser, else it will fail to process system catalogs and thus not
-    be able to advance the database's <structfield>datfrozenxid</>.)
-    If these warnings are
-    ignored, the system will shut down and refuse to start any new
-    transactions once there are fewer than 1 million transactions left
-    until wraparound:
-
-<programlisting>
-ERROR:  database is not accepting commands to avoid wraparound data loss in database "mydb"
-HINT:  Stop the postmaster and use a standalone backend to VACUUM in "mydb".
-</programlisting>
-
-    The 1-million-transaction safety margin exists to let the
-    administrator recover without data loss, by manually executing the
-    required <command>VACUUM</> commands.  However, since the system will not
-    execute commands once it has gone into the safety shutdown mode,
-    the only way to do this is to stop the server and use a single-user
-    backend to execute <command>VACUUM</>.  The shutdown mode is not enforced
-    by a single-user backend.  See the <xref linkend="app-postgres"> reference
-    page for details about using a single-user backend.
-   </para>
-
-  </sect2>
-
-  <sect2 id="autovacuum">
-   <title>The Autovacuum Daemon</title>
-
-   <indexterm>
-    <primary>autovacuum</primary>
-    <secondary>general information</secondary>
-   </indexterm>
-
-<!## XC>
-&xconly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-
-&common;
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> has an optional but highly
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> has an optional but highly
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> has an optional but highly
-<!## end>
-    recommended feature called <firstterm>autovacuum</firstterm>,
-    whose purpose is to automate the execution of
-    <command>VACUUM</command> and <command>ANALYZE </command> commands.
-    When enabled, autovacuum checks for
-    tables that have had a large number of inserted, updated or deleted
-    tuples.  These checks use the statistics collection facility;
-    therefore, autovacuum cannot be used unless <xref
-    linkend="guc-track-counts"> is set to <literal>true</literal>.
-    In the default configuration, autovacuuming is enabled and the related
-    configuration parameters are appropriately set.
-   </para>
-
-   <para>
-    The <quote>autovacuum daemon</> actually consists of multiple processes.
-    There is a persistent daemon process, called the
-    <firstterm>autovacuum launcher</firstterm>, which is in charge of starting
-    <firstterm>autovacuum worker</firstterm> processes for all databases. The
-    launcher will distribute the work across time, attempting to start one
-    worker within each database every <xref linkend="guc-autovacuum-naptime">
-    seconds.  (Therefore, if the installation has <replaceable>N</> databases,
-    a new worker will be launched every
-    <varname>autovacuum_naptime</>/<replaceable>N</> seconds.)
-    A maximum of <xref linkend="guc-autovacuum-max-workers"> worker processes
-    are allowed to run at the same time. If there are more than
-    <varname>autovacuum_max_workers</> databases to be processed,
-    the next database will be processed as soon as the first worker finishes.
-    Each worker process will check each table within its database and
-    execute <command>VACUUM</> and/or <command>ANALYZE</> as needed.
-   </para>
-
-   <para>
-    If several large tables all become eligible for vacuuming in a short
-    amount of time, all autovacuum workers might become occupied with
-    vacuuming those tables for a long period.  This would result
-    in other tables and databases not being vacuumed until a worker became
-    available. There is no limit on how many workers might be in a
-    single database, but workers do try to avoid repeating work that has
-    already been done by other workers. Note that the number of running
-    workers does not count towards <xref linkend="guc-max-connections"> or
-    <xref linkend="guc-superuser-reserved-connections"> limits.
-   </para>
-
-   <para>
-    Tables whose <structfield>relfrozenxid</> value is more than
-    <xref linkend="guc-autovacuum-freeze-max-age"> transactions old are always
-    vacuumed (this also applies to those tables whose freeze max age has
-    been modified via storage parameters; see below).  Otherwise, if the
-    number of tuples obsoleted since the last
-    <command>VACUUM</command> exceeds the <quote>vacuum threshold</quote>, the
-    table is vacuumed.  The vacuum threshold is defined as:
-<programlisting>
-vacuum threshold = vacuum base threshold + vacuum scale factor * number of tuples
-</programlisting>
-    where the vacuum base threshold is
-    <xref linkend="guc-autovacuum-vacuum-threshold">,
-    the vacuum scale factor is
-    <xref linkend="guc-autovacuum-vacuum-scale-factor">,
-    and the number of tuples is
-    <structname>pg_class</structname>.<structfield>reltuples</structfield>.
-    The number of obsolete tuples is obtained from the statistics
-    collector; it is a semi-accurate count updated by each
-    <command>UPDATE</command> and <command>DELETE</command> operation.  (It
-    is only semi-accurate because some information might be lost under heavy
-    load.)  If the <structfield>relfrozenxid</> value of the table is more
-    than <varname>vacuum_freeze_table_age</> transactions old, the whole
-    table is scanned to freeze old tuples and advance
-    <structfield>relfrozenxid</>, otherwise only pages that have been modified
-    since the last vacuum are scanned.
-   </para>
-
-   <para>
-    For analyze, a similar condition is used: the threshold, defined as:
-<programlisting>
-analyze threshold = analyze base threshold + analyze scale factor * number of tuples
-</programlisting>
-    is compared to the total number of tuples inserted, updated, or deleted
-    since the last <command>ANALYZE</command>.
-   </para>
-
-   <para>
-    Temporary tables cannot be accessed by autovacuum.  Therefore,
-    appropriate vacuum and analyze operations should be performed via
-    session SQL commands.
-   </para>
-
-   <para>
-    The default thresholds and scale factors are taken from
-    <filename>postgresql.conf</filename>, but it is possible to override them
-    on a table-by-table basis; see
-    <xref linkend="sql-createtable-storage-parameters"
-    endterm="sql-createtable-storage-parameters-title"> for more information.
-    If a setting
-    has been changed via storage parameters, that value is used; otherwise the
-    global settings are used. See <xref linkend="runtime-config-autovacuum"> for
-    more details on the global settings.
-   </para>
-
-   <para>
-    Besides the base threshold values and scale factors, there are six
-    more autovacuum parameters that can be set for each table via
-    storage parameters.
-    The first parameter, <literal>autovacuum_enabled</>,
-    can be set to <literal>false</literal> to instruct the autovacuum daemon
-    to skip that particular table entirely.  In this case
-    autovacuum will only touch the table if it must do so
-    to prevent transaction ID wraparound.
-    Another two parameters,
-    <varname>autovacuum_vacuum_cost_delay</> and
-    <varname>autovacuum_vacuum_cost_limit</>, are used to set
-    table-specific values for the cost-based vacuum delay feature
-    (see <xref linkend="runtime-config-resource-vacuum-cost">).
-    <varname>autovacuum_freeze_min_age</>,
-    <varname>autovacuum_freeze_max_age</> and
-    <varname>autovacuum_freeze_table_age</> are used to set
-    values for <xref linkend="guc-vacuum-freeze-min-age">,
-    <xref linkend="guc-autovacuum-freeze-max-age"> and
-    <xref linkend="guc-vacuum-freeze-table-age"> respectively.
-   </para>
-
-   <para>
-    When multiple workers are running, the cost limit is
-    <quote>balanced</quote> among all the running workers, so that the
-    total impact on the system is the same, regardless of the number
-    of workers actually running.
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="routine-reindex">
-  <title>Routine Reindexing</title>
-
-  <indexterm zone="routine-reindex">
-   <primary>reindex</primary>
-  </indexterm>
-<!## XC>
-&xconly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-
-&common;
-
-  <para>
-   In some situations it is worthwhile to rebuild indexes periodically
-   with the <xref linkend="sql-reindex">
-   command.
-  </para>
-
-  <para>
-   B-tree index pages that have become completely empty are reclaimed for
-   re-use.  However, there is still a possibility
-   of inefficient use of space: if all but a few index keys on a page have
-   been deleted, the page remains allocated.  Therefore, a usage
-   pattern in which most, but not all, keys in each range are eventually
-   deleted will see poor use of space.  For such usage patterns,
-   periodic reindexing is recommended.
-  </para>
-
-  <para>
-   The potential for bloat in non-B-tree indexes has not been well
-   researched.  It is a good idea to periodically monitor the index's physical
-   size when using any non-B-tree index type.
-  </para>
-
-  <para>
-   Also, for B-tree indexes, a freshly-constructed index is slightly faster to
-   access than one that has been updated many times because logically
-   adjacent pages are usually also physically adjacent in a newly built index.
-   (This consideration does not apply to non-B-tree indexes.)  It
-   might be worthwhile to reindex periodically just to improve access speed.
-  </para>
- </sect1>
-
-
- <sect1 id="logfile-maintenance">
-  <title>Log File Maintenance</title>
-
-  <indexterm zone="logfile-maintenance">
-   <primary>server log</primary>
-   <secondary>log file maintenance</secondary>
-  </indexterm>
-<!## XC>
-&xconly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that this section describes the task of individual
-   Coordinator and Datanode.  It should be done for each of them.
-  </para>
-<!## end>
-
-&common;
-
-  <para>
-   It is a good idea to save the database server's log output
-   somewhere, rather than just discarding it via <filename>/dev/null</>.
-   The log output is invaluable when diagnosing
-   problems.  However, the log output tends to be voluminous
-   (especially at higher debug levels) so you won't want to save it
-   indefinitely.  You need to <emphasis>rotate</> the log files so that
-   new log files are started and old ones removed after a reasonable
-   period of time.
-  </para>
-
-  <para>
-   If you simply direct the <systemitem>stderr</> of
-   <command>postgres</command> into a
-   file, you will have log output, but
-   the only way to truncate the log file is to stop and restart
-   the server. This might be acceptable if you are using
-<!## PG>
-   <productname>PostgreSQL</productname> in a development environment,
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> in a development environment,
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> in a development environment,
-<!## end>
-   but few production servers would find this behavior acceptable.
-  </para>
-
-  <para>
-   A better approach is to send the server's
-   <systemitem>stderr</> output to some type of log rotation program.
-   There is a built-in log rotation facility, which you can use by
-   setting the configuration parameter <varname>logging_collector</> to
-   <literal>true</> in <filename>postgresql.conf</>.  The control
-   parameters for this program are described in <xref
-   linkend="runtime-config-logging-where">. You can also use this approach
-   to capture the log data in machine readable <acronym>CSV</>
-   (comma-separated values) format.
-  </para>
-
-  <para>
-   Alternatively, you might prefer to use an external log rotation
-   program if you have one that you are already using with other
-   server software. For example, the <application>rotatelogs</application>
-   tool included in the <productname>Apache</productname> distribution
-<!## PG>
-   can be used with <productname>PostgreSQL</productname>.  To do this,
-<!## end>
-<!## XC>
-   can be used with <productname>Postgres-XC</productname>.  To do this,
-<!## end>
-<!## XL>
-   can be used with <productname>Postgres-XL</productname>.  To do this,
-<!## end>
-   just pipe the server's
-   <systemitem>stderr</> output to the desired program.
-   If you start the server with
-   <command>pg_ctl</>, then <systemitem>stderr</>
-   is already redirected to <systemitem>stdout</>, so you just need a
-   pipe command, for example:
-
-<programlisting>
-pg_ctl start | rotatelogs /var/log/pgsql_log 86400
-</programlisting>
-  </para>
-
-  <para>
-   Another production-grade approach to managing log output is to
-   send it to <application>syslog</> and let
-   <application>syslog</> deal with file rotation. To do this, set the
-   configuration parameter <varname>log_destination</> to <literal>syslog</>
-   (to log to <application>syslog</> only) in
-   <filename>postgresql.conf</>. Then you can send a <literal>SIGHUP</literal>
-   signal to the <application>syslog</> daemon whenever you want to force it
-   to start writing a new log file.  If you want to automate log
-   rotation, the <application>logrotate</application> program can be
-   configured to work with log files from
-   <application>syslog</application>.
-  </para>
-
-  <para>
-   On many systems, however, <application>syslog</> is not very reliable,
-   particularly with large log messages; it might truncate or drop messages
-   just when you need them the most.  Also, on <productname>Linux</>,
-   <application>syslog</> will flush each message to disk, yielding poor
-   performance.  (You can use a <quote><literal>-</></> at the start of the file name
-   in the <application>syslog</> configuration file to disable syncing.)
-  </para>
-
-  <para>
-   Note that all the solutions described above take care of starting new
-   log files at configurable intervals, but they do not handle deletion
-   of old, no-longer-useful log files.  You will probably want to set
-   up a batch job to periodically delete old log files.  Another possibility
-   is to configure the rotation program so that old log files are overwritten
-   cyclically.
-  </para>
-
-  <para>
-   <ulink url="http://pgfouine.projects.postgresql.org/">pgFouine</ulink>
-   is an external project that does sophisticated log file analysis.
-   <ulink
-   url="http://bucardo.org/wiki/Check_postgres">check_postgres</ulink>
-   provides Nagios alerts when important messages appear in the log
-   files, as well as detection of many other extraordinary conditions.
-  </para>
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/manage-ag.sgmlin b/doc-xc/src/sgml/manage-ag.sgmlin
deleted file mode 100644
index fc8fc68bb4..0000000000
--- a/doc-xc/src/sgml/manage-ag.sgmlin
+++ /dev/null
@@ -1,613 +0,0 @@
-<!-- doc/src/sgml/manage-ag.sgml -->
-
-<chapter id="managing-databases">
- <title>Managing Databases</title>
-
- <indexterm zone="managing-databases"><primary>database</></>
-
-&common;
- <para>
-<!## PG>
-  Every instance of a running <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-  Every instance of a running <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-  Every instance of a running <productname>Postgres-XL</productname>
-<!## end>
-  server manages one or more databases.  Databases are therefore the
-  topmost hierarchical level for organizing <acronym>SQL</acronym>
-  objects (<quote>database objects</quote>).  This chapter describes
-  the properties of databases, and how to create, manage, and destroy
-  them.
- </para>
-
- <sect1 id="manage-ag-overview">
-  <title>Overview</title>
-
-  <indexterm zone="manage-ag-overview">
-   <primary>schema</primary>
-  </indexterm>
-
-&common;
-  <para>
-   A database is a named collection of <acronym>SQL</acronym> objects
-   (<quote>database objects</quote>).  Generally, every database
-   object (tables, functions, etc.) belongs to one and only one
-   database.  (However there are a few system catalogs, for example
-   <literal>pg_database</>, that belong to a whole cluster and
-   are accessible from each database within the cluster.)  More
-   accurately, a database is a collection of schemas and the schemas
-   contain the tables, functions, etc.  So the full hierarchy is:
-   server, database, schema, table (or some other kind of object,
-   such as a function).
-  </para>
-
-  <para>
-   When connecting to the database server, a client must specify in
-   its connection request the name of the database it wants to connect
-   to. It is not possible to access more than one database per
-   connection. However, an application is not restricted in the number of
-   connections it opens to the same or other databases.  Databases are
-   physically separated and access control is managed at the
-<!## PG>
-   connection level.  If one <productname>PostgreSQL</> server
-<!## end>
-<!## XC>
-   connection level.  If one <productname>Postgres-XC</> server
-<!## end>
-<!## XL>
-   connection level.  If one <productname>Postgres-XL</> server
-<!## end>
-   instance is to house projects or users that should be separate and
-   for the most part unaware of each other, it is therefore
-   recommendable to put them into separate databases.  If the projects
-   or users are interrelated and should be able to use each other's
-   resources, they should be put in the same database but possibly
-   into separate schemas.  Schemas are a purely logical structure and who can
-   access what is managed by the privilege system.  More information about
-   managing schemas is in <xref linkend="ddl-schemas">.
-  </para>
-
-  <para>
-   Databases are created with the <command>CREATE DATABASE</> command
-   (see <xref linkend="manage-ag-createdb">) and destroyed with the
-   <command>DROP DATABASE</> command
-   (see <xref linkend="manage-ag-dropdb">).
-   To determine the set of existing databases, examine the
-   <structname>pg_database</> system catalog, for example
-<synopsis>
-SELECT datname FROM pg_database;
-</synopsis>
-   The <xref linkend="app-psql"> program's <literal>\l</> meta-command
-   and <option>-l</> command-line option are also useful for listing the
-   existing databases.
-  </para>
-
-  <note>
-   <para>
-    The <acronym>SQL</> standard calls databases <quote>catalogs</>, but there
-    is no difference in practice.
-   </para>
-  </note>
- </sect1>
-
- <sect1 id="manage-ag-createdb">
-  <title>Creating a Database</title>
-
-  <indexterm><primary>CREATE DATABASE</></>
-
-  <para>
-<!## PG>
-   In order to create a database, the <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-   In order to create a database, the <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-   In order to create a database, the <productname>Postgres-XL</>
-<!## end>
-   server must be up and running (see <xref
-   linkend="server-start">).
-  </para>
-
-  <para>
-   Databases are created with the SQL command
-   <xref linkend="sql-createdatabase">:
-<synopsis>
-CREATE DATABASE <replaceable>name</>;
-</synopsis>
-   where <replaceable>name</> follows the usual rules for
-   <acronym>SQL</acronym> identifiers.  The current role automatically
-   becomes the owner of the new database. It is the privilege of the
-   owner of a database to remove it later (which also removes all
-   the objects in it, even if they have a different owner).
-  </para>
-
-  <para>
-   The creation of databases is a restricted operation. See <xref
-   linkend="role-attributes"> for how to grant permission.
-  </para>
-
-  <para>
-   Since you need to be connected to the database server in order to
-   execute the <command>CREATE DATABASE</command> command, the
-   question remains how the <emphasis>first</> database at any given
-   site can be created. The first database is always created by the
-   <command>initdb</> command when the data storage area is
-   initialized. (See <xref linkend="creating-cluster">.)  This
-   database is called
-   <literal>postgres</>.<indexterm><primary>postgres</></> So to
-   create the first <quote>ordinary</> database you can connect to
-   <literal>postgres</>.
-  </para>
-
-  <para>
-   A second database,
-   <literal>template1</literal>,<indexterm><primary>template1</></>
-   is also created during database cluster initialization.  Whenever a
-   new database is created within the
-   cluster, <literal>template1</literal> is essentially cloned.
-   This means that any changes you make in <literal>template1</> are
-   propagated to all subsequently created databases. Because of this,
-   avoid creating objects in <literal>template1</> unless you want them
-   propagated to every newly created database.  More details
-   appear in <xref linkend="manage-ag-templatedbs">.
-  </para>
-
-  <para>
-   As a convenience, there is a program you can
-   execute from the shell to create new databases,
-   <command>createdb</>.<indexterm><primary>createdb</></>
-
-<synopsis>
-createdb <replaceable class="parameter">dbname</replaceable>
-</synopsis>
-
-   <command>createdb</> does no magic. It connects to the <literal>postgres</>
-   database and issues the <command>CREATE DATABASE</> command,
-   exactly as described above.
-   The <xref linkend="app-createdb"> reference page contains the invocation
-   details. Note that <command>createdb</> without any arguments will create
-   a database with the current user name.
-  </para>
-
-  <note>
-   <para>
-    <xref linkend="client-authentication"> contains information about
-    how to restrict who can connect to a given database.
-   </para>
-  </note>
-
-  <para>
-   Sometimes you want to create a database for someone else, and have him
-   become the owner of the new database, so he can
-   configure and manage it himself.  To achieve that, use one of the
-   following commands:
-<programlisting>
-CREATE DATABASE <replaceable>dbname</> OWNER <replaceable>rolename</>;
-</programlisting>
-   from the SQL environment, or:
-<programlisting>
-createdb -O <replaceable>rolename</> <replaceable>dbname</>
-</programlisting>
-   from the shell.
-   Only the superuser is allowed to create a database for
-   someone else (that is, for a role you are not a member of).
-  </para>
- </sect1>
-
- <sect1 id="manage-ag-templatedbs">
-  <title>Template Databases</title>
-
-  <para>
-   <command>CREATE DATABASE</> actually works by copying an existing
-   database.  By default, it copies the standard system database named
-   <literal>template1</>.<indexterm><primary>template1</></> Thus that
-   database is the <quote>template</> from which new databases are
-   made.  If you add objects to <literal>template1</>, these objects
-   will be copied into subsequently created user databases.  This
-   behavior allows site-local modifications to the standard set of
-   objects in databases.  For example, if you install the procedural
-   language <application>PL/Perl</> in <literal>template1</>, it will
-   automatically be available in user databases without any extra
-   action being taken when those databases are created.
-  </para>
-
-  <para>
-   There is a second standard system database named
-   <literal>template0</>.<indexterm><primary>template0</></> This
-   database contains the same data as the initial contents of
-   <literal>template1</>, that is, only the standard objects
-   predefined by your version of
-<!## PG>
-   <productname>PostgreSQL</productname>.  <literal>template0</>
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>.  <literal>template0</>
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>.  <literal>template0</>
-<!## end>
-   should never be changed after the database cluster has been
-   initialized.  By instructing
-   <command>CREATE DATABASE</> to copy <literal>template0</> instead
-   of <literal>template1</>, you can create a <quote>virgin</> user
-   database that contains none of the site-local additions in
-   <literal>template1</>.  This is particularly handy when restoring a
-   <literal>pg_dump</> dump: the dump script should be restored in a
-   virgin database to ensure that one recreates the correct contents
-   of the dumped database, without conflicting with objects that
-   might have been added to <literal>template1</> later on.
-  </para>
-
-  <para>
-   Another common reason for copying <literal>template0</> instead
-   of <literal>template1</> is that new encoding and locale settings
-   can be specified when copying <literal>template0</>, whereas a copy
-   of <literal>template1</> must use the same settings it does.
-   This is because <literal>template1</> might contain encoding-specific
-   or locale-specific data, while <literal>template0</> is known not to.
-  </para>
-
-  <para>
-   To create a database by copying <literal>template0</literal>, use:
-<programlisting>
-CREATE DATABASE <replaceable>dbname</> TEMPLATE template0;
-</programlisting>
-   from the SQL environment, or:
-<programlisting>
-createdb -T template0 <replaceable>dbname</>
-</programlisting>
-   from the shell.
-  </para>
-
-  <para>
-   It is possible to create additional template databases, and indeed
-   one can copy any database in a cluster by specifying its name
-   as the template for <command>CREATE DATABASE</>.  It is important to
-   understand, however, that this is not (yet) intended as
-   a general-purpose <quote><command>COPY DATABASE</command></quote> facility.
-   The principal limitation is that no other sessions can be connected to
-   the source database while it is being copied.  <command>CREATE
-   DATABASE</> will fail if any other connection exists when it starts;
-   during the copy operation, new connections to the source database
-   are prevented.
-  </para>
-
-  <para>
-   Two useful flags exist in <literal>pg_database</literal><indexterm><primary>pg_database</></> for each
-   database: the columns <literal>datistemplate</literal> and
-   <literal>datallowconn</literal>.  <literal>datistemplate</literal>
-   can be set to indicate that a database is intended as a template for
-   <command>CREATE DATABASE</>.  If this flag is set, the database can be
-   cloned by any user with <literal>CREATEDB</> privileges; if it is not set,
-   only superusers and the owner of the database can clone it.
-   If <literal>datallowconn</literal> is false, then no new connections
-   to that database will be allowed (but existing sessions are not terminated
-   simply by setting the flag false).  The <literal>template0</literal>
-   database is normally marked <literal>datallowconn = false</> to prevent its modification.
-   Both <literal>template0</literal> and <literal>template1</literal>
-   should always be marked with <literal>datistemplate = true</>.
-  </para>
-
-  <note>
-   <para>
-    <literal>template1</> and <literal>template0</> do not have any special
-    status beyond the fact that the name <literal>template1</> is the default
-    source database name for <command>CREATE DATABASE</>.
-    For example, one could drop <literal>template1</> and recreate it from
-    <literal>template0</> without any ill effects.  This course of action
-    might be advisable if one has carelessly added a bunch of junk in
-    <literal>template1</>. (To delete <literal>template1</literal>,
-    it must have <literal>pg_database.datistemplate = false</>.)
-   </para>
-
-   <para>
-    The <literal>postgres</> database is also created when a database
-    cluster is initialized.  This database is meant as a default database for
-    users and applications to connect to. It is simply a copy of
-    <literal>template1</> and can be dropped and recreated if necessary.
-   </para>
-<!## XC>
-   <para>
-    <emphasis>For Postgres-XC only.</>
-   </para>
-   <para>
-    In <productname>Postgres-XC</>, template databases are hold in
-    each Coordinator and Datanode.  They are locally copied when new
-    database is created.
-   </para>
-<!## end>
-<!## XL>
-   <para>
-    <emphasis>For Postgres-XL only.</>
-   </para>
-   <para>
-    In <productname>Postgres-XL</>, template databases are held in
-    each Coordinator and Datanode.  They are locally copied when new
-    database is created.
-   </para>
-<!## end>
-  </note>
- </sect1>
-
- <sect1 id="manage-ag-config">
-  <title>Database Configuration</title>
-
-  <para>
-   Recall from <xref linkend="runtime-config"> that the
-<!## PG>
-   <productname>PostgreSQL</> server provides a large number of
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> server provides a large number of
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> server provides a large number of
-<!## end>
-   run-time configuration variables.  You can set database-specific
-   default values for many of these settings.
-  </para>
-
-  <para>
-   For example, if for some reason you want to disable the
-   <acronym>GEQO</acronym> optimizer for a given database, you'd
-   ordinarily have to either disable it for all databases or make sure
-   that every connecting client is careful to issue <literal>SET geqo
-   TO off</literal>.  To make this setting the default within a particular
-   database, you can execute the command:
-<programlisting>
-ALTER DATABASE mydb SET geqo TO off;
-</programlisting>
-   This will save the setting (but not set it immediately).  In
-   subsequent connections to this database it will appear as though
-   <literal>SET geqo TO off;</literal> had been executed just before the
-   session started.
-   Note that users can still alter this setting during their sessions; it
-   will only be the default.  To undo any such setting, use
-   <literal>ALTER DATABASE <replaceable>dbname</> RESET
-   <replaceable>varname</></literal>.
-  </para>
- </sect1>
-
- <sect1 id="manage-ag-dropdb">
-  <title>Destroying a Database</title>
-
-&common;
-  <para>
-   Databases are destroyed with the command
-   <xref linkend="sql-dropdatabase">:<indexterm><primary>DROP DATABASE</></>
-<synopsis>
-DROP DATABASE <replaceable>name</>;
-</synopsis>
-   Only the owner of the database, or
-   a superuser, can drop a database. Dropping a database removes all objects
-   that were
-   contained within the database. The destruction of a database cannot
-   be undone.
-  </para>
-
-  <para>
-   You cannot execute the <command>DROP DATABASE</command> command
-   while connected to the victim database. You can, however, be
-   connected to any other database, including the <literal>template1</>
-   database.
-   <literal>template1</> would be the only option for dropping the last user database of a
-   given cluster.
-  </para>
-
-  <para>
-   For convenience, there is also a shell program to drop
-   databases, <xref linkend="app-dropdb">:<indexterm><primary>dropdb</></>
-<synopsis>
-dropdb <replaceable class="parameter">dbname</replaceable>
-</synopsis>
-   (Unlike <command>createdb</>, it is not the default action to drop
-   the database with the current user name.)
-  </para>
- </sect1>
-
- <sect1 id="manage-ag-tablespaces">
-  <title>Tablespaces</title>
-
-  <indexterm zone="manage-ag-tablespaces">
-   <primary>tablespace</primary>
-  </indexterm>
-
-&common;
-  <para>
-<!## PG>
-   Tablespaces in <productname>PostgreSQL</> allow database administrators to
-<!## end>
-<!## XC>
-   Tablespaces in <productname>Postgres-XC</> allow database administrators to
-<!## end>
-<!## XL>
-   Tablespaces in <productname>Postgres-XL</> allow database administrators to
-<!## end>
-   define locations in the file system where the files representing
-   database objects can be stored. Once created, a tablespace can be referred
-   to by name when creating database objects.
-  </para>
-
-  <para>
-   By using tablespaces, an administrator can control the disk layout
-<!## PG>
-   of a <productname>PostgreSQL</> installation. This is useful in at
-<!## end>
-<!## XC>
-   of a <productname>Postgres-XC</> installation. This is useful in at
-<!## end>
-<!## XL>
-   of a <productname>Postgres-XL</> installation. This is useful in at
-<!## end>
-   least two ways. First, if the partition or volume on which the
-   cluster was initialized runs out of space and cannot be extended,
-   a tablespace can be created on a different partition and used
-   until the system can be reconfigured.
-  </para>
-
-  <para>
-   Second, tablespaces allow an administrator to use knowledge of the
-   usage pattern of database objects to optimize performance. For
-   example, an index which is very heavily used can be placed on a
-   very fast, highly available disk, such as an expensive solid state
-   device. At the same time a table storing archived data which is
-   rarely used or not performance critical could be stored on a less
-   expensive, slower disk system.
-  </para>
-
-  <para>
-   To define a tablespace, use the <xref
-   linkend="sql-createtablespace">
-   command, for example:<indexterm><primary>CREATE TABLESPACE</></>:
-<programlisting>
-CREATE TABLESPACE fastspace LOCATION '/mnt/sda1/postgresql/data';
-</programlisting>
-   The location must be an existing, empty directory that is owned by
-<!## PG>
-   the <productname>PostgreSQL</> operating system user.  All objects subsequently
-<!## end>
-<!## XC>
-   the <productname>Postgres-XC</> operating system user.  All objects subsequently
-<!## end>
-<!## XL>
-   the <productname>Postgres-XL</> operating system user.  All objects subsequently
-<!## end>
-   created within the tablespace will be stored in files underneath this
-   directory.
-  </para>
-
-  <note>
-   <para>
-    There is usually not much point in making more than one
-    tablespace per logical file system, since you cannot control the location
-    of individual files within a logical file system.  However,
-<!## PG>
-    <productname>PostgreSQL</> does not enforce any such limitation, and
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> does not enforce any such limitation, and
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> does not enforce any such limitation, and
-<!## end>
-    indeed it is not directly aware of the file system boundaries on your
-    system.  It just stores files in the directories you tell it to use.
-   </para>
-  </note>
-
-  <para>
-   Creation of the tablespace itself must be done as a database superuser,
-   but after that you can allow ordinary database users to use it.
-   To do that, grant them the <literal>CREATE</> privilege on it.
-  </para>
-
-  <para>
-   Tables, indexes, and entire databases can be assigned to
-   particular tablespaces. To do so, a user with the <literal>CREATE</>
-   privilege on a given tablespace must pass the tablespace name as a
-   parameter to the relevant command. For example, the following creates
-   a table in the tablespace <literal>space1</>:
-<programlisting>
-CREATE TABLE foo(i int) TABLESPACE space1;
-</programlisting>
-  </para>
-
-  <para>
-   Alternatively, use the <xref linkend="guc-default-tablespace"> parameter:
-<programlisting>
-SET default_tablespace = space1;
-CREATE TABLE foo(i int);
-</programlisting>
-   When <varname>default_tablespace</> is set to anything but an empty
-   string, it supplies an implicit <literal>TABLESPACE</> clause for
-   <command>CREATE TABLE</> and <command>CREATE INDEX</> commands that
-   do not have an explicit one.
-  </para>
-
-  <para>
-   There is also a <xref linkend="guc-temp-tablespaces"> parameter, which
-   determines the placement of temporary tables and indexes, as well as
-   temporary files that are used for purposes such as sorting large data
-   sets.  This can be a list of tablespace names, rather than only one,
-   so that the load associated with temporary objects can be spread over
-   multiple tablespaces.  A random member of the list is picked each time
-   a temporary object is to be created.
-  </para>
-
-  <para>
-   The tablespace associated with a database is used to store the system
-   catalogs of that database.  Furthermore, it is the default tablespace
-   used for tables, indexes, and temporary files created within the database,
-   if no <literal>TABLESPACE</> clause is given and no other selection is
-   specified by <varname>default_tablespace</> or
-   <varname>temp_tablespaces</> (as appropriate).
-   If a database is created without specifying a tablespace for it,
-   it uses the same tablespace as the template database it is copied from.
-  </para>
-
-  <para>
-   Two tablespaces are automatically created when the database cluster
-   is initialized.  The
-   <literal>pg_global</> tablespace is used for shared system catalogs. The
-   <literal>pg_default</> tablespace is the default tablespace of the
-   <literal>template1</> and <literal>template0</> databases (and, therefore,
-   will be the default tablespace for other databases as well, unless
-   overridden by a <literal>TABLESPACE</> clause in <command>CREATE
-   DATABASE</>).
-  </para>
-
-  <para>
-   Once created, a tablespace can be used from any database, provided
-   the requesting user has sufficient privilege. This means that a tablespace
-   cannot be dropped until all objects in all databases using the tablespace
-   have been removed.
-  </para>
-
-  <para>
-   To remove an empty tablespace, use the <xref
-   linkend="sql-droptablespace">
-   command.
-  </para>
-
-  <para>
-   To determine the set of existing tablespaces, examine the
-   <structname>pg_tablespace</> system catalog, for example
-<synopsis>
-SELECT spcname FROM pg_tablespace;
-</synopsis>
-   The <xref linkend="app-psql"> program's <literal>\db</> meta-command
-   is also useful for listing the existing tablespaces.
-  </para>
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</> makes use of symbolic links
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> makes use of symbolic links
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> makes use of symbolic links
-<!## end>
-   to simplify the implementation of tablespaces. This
-   means that tablespaces can be used <emphasis>only</> on systems
-   that support symbolic links.
-  </para>
-
-  <para>
-   The directory <filename>$PGDATA/pg_tblspc</> contains symbolic links that
-   point to each of the non-built-in tablespaces defined in the cluster.
-   Although not recommended, it is possible to adjust the tablespace
-   layout by hand by redefining these links.  Two warnings: do not do so
-   while the server is running; and after you restart the server,
-   update the <structname>pg_tablespace</> catalog with the new
-   locations.  (If you do not, <literal>pg_dump</> will continue to output
-   the old tablespace locations.)
-  </para>
-
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/mk_feature_tables.pl b/doc-xc/src/sgml/mk_feature_tables.pl
deleted file mode 100644
index 7c78e0e3aa..0000000000
--- a/doc-xc/src/sgml/mk_feature_tables.pl
+++ /dev/null
@@ -1,58 +0,0 @@
-# /usr/bin/perl -w
-
-# doc/src/sgml/mk_feature_tables.pl
-
-my $yesno = $ARGV[0];
-
-open PACK, $ARGV[1] or die;
-
-my %feature_packages;
-
-while (<PACK>) {
-    chomp;
-    my ($fid, $pname) = split /\t/;
-    if ($feature_packages{$fid}) {
-	$feature_packages{$fid} .= ", $pname";
-    } else {
-	$feature_packages{$fid} = $pname;
-    }
-}
-
-close PACK;
-
-open FEAT, $ARGV[2] or die;
-
-print "<tbody>\n";
-
-while (<FEAT>) {
-    chomp;
-    my ($feature_id, $feature_name, $subfeature_id, $subfeature_name, $is_supported, $comments) = split /\t/;
-
-    $is_supported eq $yesno || next;
-
-    $feature_name =~ s/</&lt;/g;
-    $feature_name =~ s/>/&gt;/g;
-    $subfeature_name =~ s/</&lt;/g;
-    $subfeature_name =~ s/>/&gt;/g;
-
-    print " <row>\n";
-
-    if ($subfeature_id) {
-	print "  <entry>$feature_id-$subfeature_id</entry>\n";
-    } else {
-	print "  <entry>$feature_id</entry>\n";
-    }
-    print "  <entry>" . $feature_packages{$feature_id} . "</entry>\n";
-    if ($subfeature_id) {
-	print "  <entry>$subfeature_name</entry>\n";
-    } else {
-	print "  <entry>$feature_name</entry>\n";
-    }
-    print "  <entry>$comments</entry>\n";
-
-    print " </row>\n";
-}
-
-print "</tbody>\n";
-
-close FEAT;
diff --git a/doc-xc/src/sgml/monitoring.sgmlin b/doc-xc/src/sgml/monitoring.sgmlin
deleted file mode 100644
index 9cc1ede3c9..0000000000
--- a/doc-xc/src/sgml/monitoring.sgmlin
+++ /dev/null
@@ -1,2067 +0,0 @@
-<!-- doc/src/sgml/monitoring.sgml -->
-
-<chapter id="monitoring">
- <title>Monitoring Database Activity</title>
-
- <indexterm zone="monitoring">
-  <primary>monitoring</primary>
-  <secondary>database activity</secondary>
- </indexterm>
-
- <indexterm zone="monitoring">
-  <primary>database activity</primary>
-  <secondary>monitoring</secondary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  A database administrator frequently wonders, <quote>What is the system
-  doing right now?</quote>
-  This chapter discusses how to find that out.
- </para>
-
-  <para>
-   Several tools are available for monitoring database activity and
-   analyzing performance.  Most of this chapter is devoted to describing
-   <productname>PostgreSQL</productname>'s statistics collector,
-   but one should not neglect regular Unix monitoring programs such as
-   <command>ps</>, <command>top</>, <command>iostat</>, and <command>vmstat</>.
-   Also, once one has identified a
-   poorly-performing query, further investigation might be needed using
-   <productname>PostgreSQL</productname>'s <xref linkend="sql-explain"> command.
-   <xref linkend="using-explain"> discusses <command>EXPLAIN</>
-   and other methods for understanding the behavior of an individual
-   query.
-  </para>
-
- <sect1 id="monitoring-ps">
-  <title>Standard Unix Tools</title>
-
-  <indexterm zone="monitoring-ps">
-   <primary>ps</primary>
-   <secondary>to monitor activity</secondary>
-  </indexterm>
-&pgnotice;
-
-  <para>
-   On most Unix platforms, <productname>PostgreSQL</productname> modifies its
-   command title as reported by <command>ps</>, so that individual server
-   processes can readily be identified.  A sample display is
-
-<screen>
-$ ps auxww | grep ^postgres
-postgres   960  0.0  1.1  6104 1480 pts/1    SN   13:17   0:00 postgres -i
-postgres   963  0.0  1.1  7084 1472 pts/1    SN   13:17   0:00 postgres: writer process
-postgres   965  0.0  1.1  6152 1512 pts/1    SN   13:17   0:00 postgres: stats collector process
-postgres   998  0.0  2.3  6532 2992 pts/1    SN   13:18   0:00 postgres: tgl runbug 127.0.0.1 idle
-postgres  1003  0.0  2.4  6532 3128 pts/1    SN   13:19   0:00 postgres: tgl regression [local] SELECT waiting
-postgres  1016  0.1  2.4  6532 3080 pts/1    SN   13:19   0:00 postgres: tgl regression [local] idle in transaction
-</screen>
-
-   (The appropriate invocation of <command>ps</> varies across different
-   platforms, as do the details of what is shown.  This example is from a
-   recent Linux system.)  The first process listed here is the
-   master server process.  The command arguments
-   shown for it are the same ones used when it was launched.  The next two
-   processes are background worker processes automatically launched by the
-   master process.  (The <quote>stats collector</> process will not be present
-   if you have set
-   the system not to start the statistics collector.)  Each of the remaining
-   processes is a server process handling one client connection.  Each such
-   process sets its command line display in the form
-
-<screen>
-postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <replaceable>activity</>
-</screen>
-
-  The user, database, and (client) host items remain the same for
-  the life of the client connection, but the activity indicator changes.
-  The activity can be <literal>idle</> (i.e., waiting for a client command),
-  <literal>idle in transaction</> (waiting for client inside a <command>BEGIN</> block),
-  or a command type name such as <literal>SELECT</>.  Also,
-  <literal>waiting</> is appended if the server process is presently waiting
-  on a lock held by another session.  In the above example we can infer
-  that process 1003 is waiting for process 1016 to complete its transaction and
-  thereby release some lock.
-  </para>
-
-  <para>
-   If you have turned off <xref linkend="guc-update-process-title"> then the
-   activity indicator is not updated; the process title is set only once
-   when a new process is launched.  On some platforms this saves a measurable
-   amount of per-command overhead;  on others it's insignificant.
-  </para>
-
-  <tip>
-  <para>
-  <productname>Solaris</productname> requires special handling. You must
-  use <command>/usr/ucb/ps</command>, rather than
-  <command>/bin/ps</command>. You also must use two <option>w</option>
-  flags, not just one. In addition, your original invocation of the
-  <command>postgres</command> command must have a shorter
-  <command>ps</command> status display than that provided by each
-  server process.  If you fail to do all three things, the <command>ps</>
-  output for each server process will be the original <command>postgres</>
-  command line.
-  </para>
-  </tip>
- </sect1>
-
- <sect1 id="monitoring-stats">
-  <title>The Statistics Collector</title>
-
-  <indexterm zone="monitoring-stats">
-   <primary>statistics</primary>
-  </indexterm>
-&pgnotice;
-
-  <para>
-   <productname>PostgreSQL</productname>'s <firstterm>statistics collector</>
-   is a subsystem that supports collection and reporting of information about
-   server activity.  Presently, the collector can count accesses to tables
-   and indexes in both disk-block and individual-row terms.  It also tracks
-   the total number of rows in each table, and information about vacuum and
-   analyze actions for each table.  It can also count calls to user-defined
-   functions and the total time spent in each one.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname> also supports reporting of the exact
-   command currently being executed by other server processes.  This
-   facility is independent of the collector process.
-  </para>
-
- <sect2 id="monitoring-stats-setup">
-  <title>Statistics Collection Configuration</title>
-
-&pgnotice;
-  <para>
-   Since collection of statistics adds some overhead to query execution,
-   the system can be configured to collect or not collect information.
-   This is controlled by configuration parameters that are normally set in
-   <filename>postgresql.conf</>.  (See <xref linkend="runtime-config"> for
-   details about setting configuration parameters.)
-  </para>
-
-  <para>
-   The parameter <xref linkend="guc-track-counts"> controls whether
-   statistics are collected about table and index accesses.
-  </para>
-
-  <para>
-   The parameter <xref linkend="guc-track-functions"> enables tracking of
-   usage of user-defined functions.
-  </para>
-
-  <para>
-   The parameter <xref linkend="guc-track-activities"> enables monitoring
-   of the current command being executed by any server process.
-  </para>
-
-  <para>
-   Normally these parameters are set in <filename>postgresql.conf</> so
-   that they apply to all server processes, but it is possible to turn
-   them on or off in individual sessions using the <xref
-   linkend="sql-set"> command. (To prevent
-   ordinary users from hiding their activity from the administrator,
-   only superusers are allowed to change these parameters with
-   <command>SET</>.)
-  </para>
-
-  <para>
-   The statistics collector transmits the collected
-   information to backends (including autovacuum) through temporary files.
-   These files are stored in the <filename>pg_stat_tmp</filename> subdirectory.
-   When the postmaster shuts down, a permanent copy of the statistics
-   data is stored in the <filename>global</filename> subdirectory. For increased
-   performance, the parameter <xref linkend="guc-stats-temp-directory"> can
-   be pointed at a RAM-based file system, decreasing physical I/O requirements.
-  </para>
-
- </sect2>
-
- <sect2 id="monitoring-stats-views">
-  <title>Viewing Collected Statistics</title>
-
-&pgnotice;
-  <para>
-   Several predefined views, listed in <xref
-   linkend="monitoring-stats-views-table">, are available to show the results
-   of statistics collection.  Alternatively, one can
-   build custom views using the underlying statistics functions.
-  </para>
-
-  <para>
-   When using the statistics to monitor current activity, it is important
-   to realize that the information does not update instantaneously.
-   Each individual server process transmits new statistical counts to
-   the collector just before going idle; so a query or transaction still in
-   progress does not affect the displayed totals.  Also, the collector itself
-   emits a new report at most once per <varname>PGSTAT_STAT_INTERVAL</varname>
-   milliseconds (500 unless altered while building the server).  So the
-   displayed information lags behind actual activity.  However, current-query
-   information collected by <varname>track_activities</varname> is
-   always up-to-date.
-  </para>
-
-  <para>
-   Another important point is that when a server process is asked to display
-   any of these statistics, it first fetches the most recent report emitted by
-   the collector process and then continues to use this snapshot for all
-   statistical views and functions until the end of its current transaction.
-   So the statistics will show static information as long as you continue the
-   current transaction.  Similarly, information about the current queries of
-   all sessions is collected when any such information is first requested
-   within a transaction, and the same information will be displayed throughout
-   the transaction.
-   This is a feature, not a bug, because it allows you to perform several
-   queries on the statistics and correlate the results without worrying that
-   the numbers are changing underneath you.  But if you want to see new
-   results with each query, be sure to do the queries outside any transaction
-   block.  Alternatively, you can invoke
-   <function>pg_stat_clear_snapshot</function>(), which will discard the
-   current transaction's statistics snapshot (if any).  The next use of
-   statistical information will cause a new snapshot to be fetched.
-  </para>
-
-  <para>
-   A transaction can also see its own statistics (as yet untransmitted to the
-   collector) in the views <structname>pg_stat_xact_all_tables</>,
-   <structname>pg_stat_xact_sys_tables</>,
-   <structname>pg_stat_xact_user_tables</>, and
-   <structname>pg_stat_xact_user_functions</>, or via these views' underlying
-   functions.  These numbers do not act as stated above; instead they update
-   continuously throughout the transaction.
-  </para>
-
-  <table id="monitoring-stats-views-table">
-   <title>Standard Statistics Views</title>
-
-   <tgroup cols="2">
-    <thead>
-     <row>
-      <entry>View Name</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><structname>pg_stat_activity</><indexterm><primary>pg_stat_activity</primary></indexterm></entry>
-      <entry>One row per server process, showing database OID, database
-      name, process <acronym>ID</>, user OID, user name, application name,
-      client's address, host name (if available), and port number, times at
-      which the server process, current transaction, and current query began
-      execution, process's waiting status, and text of the current query.
-      The columns that report data on the current query are available unless
-      the parameter <varname>track_activities</varname> has been turned off.
-      Furthermore, these columns are only visible if the user examining
-      the view is a superuser or the same as the user owning the process
-      being reported on.  The client's host name will be available only if
-      <xref linkend="guc-log-hostname"> is set or if the user's host name
-      needed to be looked up during <filename>pg_hba.conf</filename>
-      processing.
-     </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_bgwriter</><indexterm><primary>pg_stat_bgwriter</primary></indexterm></entry>
-      <entry>One row only, showing cluster-wide statistics from the
-      background writer: number of scheduled checkpoints, requested
-      checkpoints, buffers written by checkpoints and cleaning scans,
-      and the number of times the background writer stopped a cleaning scan
-      because it had written too many buffers.  Also includes
-      statistics about the shared buffer pool, including buffers written
-      by backends (that is, not by the background writer), how many times
-      those backends had to execute their own fsync calls (normally the
-      background writer handles those even when the backend does its own
-      write), total buffers allocated, and time of last statistics reset.
-     </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_database</><indexterm><primary>pg_stat_database</primary></indexterm></entry>
-      <entry>One row per database, showing database OID, database name,
-      number of active server processes connected to that database,
-      number of transactions committed and rolled back in that database,
-      total disk blocks read, total buffer hits (i.e., block
-      read requests avoided by finding the block already in buffer cache),
-      number of rows returned, fetched, inserted, updated and deleted, the
-      total number of queries cancelled due to conflict with recovery (on
-      standby servers), and time of last statistics reset.
-     </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_database_conflicts</><indexterm><primary>pg_stat_database_conflicts</primary></indexterm></entry>
-      <entry>One row per database, showing database OID, database name and
-      the number of queries that have been cancelled in this database due to
-      dropped tablespaces, lock timeouts, old snapshots, pinned buffers and
-      deadlocks. Will only contain information on standby servers, since
-      conflicts do not occur on master servers.
-     </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_replication</><indexterm><primary>pg_stat_replication</primary></indexterm></entry>
-      <entry>One row per WAL sender process, showing process <acronym>ID</>,
-      user OID, user name, application name, client's address, host name
-      (if available) and port number, time at which the server process began
-      execution, and the current WAL sender state and transaction log
-      location.  In addition, the standby reports the last transaction log
-      position it received and wrote, the last position it flushed to disk,
-      and the last position it replayed, and this information is also
-      displayed here. If the standby's application names matches one of the
-      settings in <varname>synchronous_standby_names</> then the sync_priority
-      is shown here also, that is the order in which standbys will become
-      the synchronous standby. The columns detailing what exactly the connection
-      is doing are only visible if the user examining the view is a superuser.
-      The client's host name will be available only if
-      <xref linkend="guc-log-hostname"> is set or if the user's host name
-      needed to be looked up during <filename>pg_hba.conf</filename>
-      processing.
-     </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_all_tables</><indexterm><primary>pg_stat_all_tables</primary></indexterm></entry>
-      <entry>For each table in the current database (including TOAST tables),
-      the table OID, schema and table name, number of sequential
-      scans initiated, number of live rows fetched by sequential
-      scans, number of index scans initiated (over all indexes
-      belonging to the table), number of live rows fetched by index
-      scans, numbers of row insertions, updates, and deletions,
-      number of row updates that were HOT (i.e., no separate index update),
-      numbers of live and dead rows,
-      the last time the table was non-<option>FULL</> vacuumed manually,
-      the last time it was vacuumed by the autovacuum daemon,
-      the last time it was analyzed manually,
-      the last time it was analyzed by the autovacuum daemon,
-      number of times it has been non-<option>FULL</> vacuumed manually,
-      number of times it has been vacuumed by the autovacuum daemon,
-      number of times it has been analyzed manually,
-      and the number of times it has been analyzed by the autovacuum daemon.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_sys_tables</><indexterm><primary>pg_stat_sys_tables</primary></indexterm></entry>
-      <entry>Same as <structname>pg_stat_all_tables</>, except that only
-      system tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_user_tables</><indexterm><primary>pg_stat_user_tables</primary></indexterm></entry>
-      <entry>Same as <structname>pg_stat_all_tables</>, except that only user
-      tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_xact_all_tables</><indexterm><primary>pg_stat_xact_all_tables</primary></indexterm></entry>
-      <entry>Similar to <structname>pg_stat_all_tables</>, but counts actions
-      taken so far within the current transaction (which are <emphasis>not</>
-      yet included in <structname>pg_stat_all_tables</> and related views).
-      The columns for numbers of live and dead rows and vacuum and
-      analyze actions are not present in this view.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_xact_sys_tables</><indexterm><primary>pg_stat_xact_sys_tables</primary></indexterm></entry>
-      <entry>Same as <structname>pg_stat_xact_all_tables</>, except that only
-      system tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_xact_user_tables</><indexterm><primary>pg_stat_xact_user_tables</primary></indexterm></entry>
-      <entry>Same as <structname>pg_stat_xact_all_tables</>, except that only
-      user tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_all_indexes</><indexterm><primary>pg_stat_all_indexes</primary></indexterm></entry>
-      <entry>For each index in the current database,
-      the table and index OID, schema, table and index name,
-      number of index scans initiated on that index, number of
-      index entries returned by index scans, and number of live table rows
-      fetched by simple index scans using that index.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_sys_indexes</><indexterm><primary>pg_stat_sys_indexes</primary></indexterm></entry>
-      <entry>Same as <structname>pg_stat_all_indexes</>, except that only
-      indexes on system tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_user_indexes</><indexterm><primary>pg_stat_user_indexes</primary></indexterm></entry>
-      <entry>Same as <structname>pg_stat_all_indexes</>, except that only
-      indexes on user tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_all_tables</><indexterm><primary>pg_statio_all_tables</primary></indexterm></entry>
-      <entry>For each table in the current database (including TOAST tables),
-      the table OID, schema and table name, number of disk
-      blocks read from that table, number of buffer hits, numbers of
-      disk blocks read and buffer hits in all indexes of that table,
-      numbers of disk blocks read and buffer hits from that table's
-      auxiliary TOAST table (if any), and numbers of disk blocks read
-      and buffer hits for the TOAST table's index.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_sys_tables</><indexterm><primary>pg_statio_sys_tables</primary></indexterm></entry>
-      <entry>Same as <structname>pg_statio_all_tables</>, except that only
-      system tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_user_tables</><indexterm><primary>pg_statio_user_tables</primary></indexterm></entry>
-      <entry>Same as <structname>pg_statio_all_tables</>, except that only
-      user tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_all_indexes</><indexterm><primary>pg_statio_all_indexes</primary></indexterm></entry>
-      <entry>For each index in the current database,
-      the table and index OID, schema, table and index name,
-      numbers of disk blocks read and buffer hits in that index.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_sys_indexes</><indexterm><primary>pg_statio_sys_indexes</primary></indexterm></entry>
-      <entry>Same as <structname>pg_statio_all_indexes</>, except that only
-      indexes on system tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_user_indexes</><indexterm><primary>pg_statio_user_indexes</primary></indexterm></entry>
-      <entry>Same as <structname>pg_statio_all_indexes</>, except that only
-      indexes on user tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_all_sequences</><indexterm><primary>pg_statio_all_sequences</primary></indexterm></entry>
-      <entry>For each sequence object in the current database,
-      the sequence OID, schema and sequence name,
-      numbers of disk blocks read and buffer hits in that sequence.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_sys_sequences</><indexterm><primary>pg_statio_sys_sequences</primary></indexterm></entry>
-      <entry>Same as <structname>pg_statio_all_sequences</>, except that only
-      system sequences are shown.  (Presently, no system sequences are defined,
-      so this view is always empty.)</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_user_sequences</><indexterm><primary>pg_statio_user_sequences</primary></indexterm></entry>
-      <entry>Same as <structname>pg_statio_all_sequences</>, except that only
-      user sequences are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_user_functions</><indexterm><primary>pg_stat_user_functions</primary></indexterm></entry>
-      <entry>For all tracked functions, function OID, schema, name, number
-      of calls, total time, and self time.  Self time is the
-      amount of time spent in the function itself, total time includes the
-      time spent in functions it called. Time values are in milliseconds.
-     </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_xact_user_functions</><indexterm><primary>pg_stat_xact_user_functions</primary></indexterm></entry>
-      <entry>Similar to <structname>pg_stat_user_functions</>, but counts only
-      calls during the current transaction (which are <emphasis>not</>
-      yet included in <structname>pg_stat_user_functions</>).</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   The per-index statistics are particularly useful to determine which
-   indexes are being used and how effective they are.
-  </para>
-
-  <para>
-   Indexes can be
-   used either directly or via <quote>bitmap scans</>.  In a bitmap scan
-   the output of several indexes can be combined via AND or OR rules;
-   so it is difficult to associate individual heap row fetches
-   with specific indexes when a bitmap scan is used.  Therefore, a bitmap
-   scan increments the
-   <structname>pg_stat_all_indexes</>.<structfield>idx_tup_read</>
-   count(s) for the index(es) it uses, and it increments the
-   <structname>pg_stat_all_tables</>.<structfield>idx_tup_fetch</>
-   count for the table, but it does not affect
-   <structname>pg_stat_all_indexes</>.<structfield>idx_tup_fetch</>.
-  </para>
-
-  <note>
-   <para>
-    Before <productname>PostgreSQL</productname> 8.1, the
-    <structfield>idx_tup_read</> and <structfield>idx_tup_fetch</> counts
-    were essentially always equal.  Now they can be different even without
-    considering bitmap scans, because <structfield>idx_tup_read</> counts
-    index entries retrieved from the index while <structfield>idx_tup_fetch</>
-    counts live rows fetched from the table; the latter will be less if any
-    dead or not-yet-committed rows are fetched using the index.
-   </para>
-  </note>
-
-  <para>
-   The <structname>pg_statio_</> views are primarily useful to
-   determine the effectiveness of the buffer cache.  When the number
-   of actual disk reads is much smaller than the number of buffer
-   hits, then the cache is satisfying most read requests without
-   invoking a kernel call. However, these statistics do not give the
-   entire story: due to the way in which <productname>PostgreSQL</>
-   handles disk I/O, data that is not in the
-   <productname>PostgreSQL</> buffer cache might still reside in the
-   kernel's I/O cache, and might therefore still be fetched without
-   requiring a physical read. Users interested in obtaining more
-   detailed information on <productname>PostgreSQL</> I/O behavior are
-   advised to use the <productname>PostgreSQL</> statistics collector
-   in combination with operating system utilities that allow insight
-   into the kernel's handling of I/O.
-  </para>
-
-  <para>
-   Other ways of looking at the statistics can be set up by writing
-   queries that use the same underlying statistics access functions as
-   these standard views do.  These functions are listed in <xref
-   linkend="monitoring-stats-funcs-table">.  The per-database access
-   functions take a database OID as argument to identify which
-   database to report on.  The per-table and per-index functions take
-   a table or index OID.  The functions for function-call statistics
-   take a function OID.  (Note that only tables, indexes, and functions
-   in the current database can be seen with these functions.)  The
-   per-server-process access functions take a server process
-   number, which ranges from one to the number of currently active
-   server processes.
-  </para>
-
-  <table id="monitoring-stats-funcs-table">
-   <title>Statistics Access Functions</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Return Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal><function>pg_stat_get_db_numbackends</function>(<type>oid</type>)</literal></entry>
-      <entry><type>integer</type></entry>
-      <entry>
-       Number of active server processes for database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_xact_commit</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of transactions committed in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_xact_rollback</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of transactions rolled back in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_blocks_fetched</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of disk block fetch requests for database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_blocks_hit</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of disk block fetch requests found in cache for database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_tuples_returned</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of tuples returned for database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_tuples_fetched</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of tuples fetched for database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_tuples_inserted</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of tuples inserted in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_tuples_updated</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of tuples updated in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_tuples_deleted</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of tuples deleted in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_conflict_tablespace</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of queries cancelled because of recovery conflict with dropped tablespaces in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_conflict_lock</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of queries cancelled because of recovery conflict with locks in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_conflict_snapshot</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of queries cancelled because of recovery conflict with old snapshots in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_conflict_bufferpin</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of queries cancelled because of recovery conflict with pinned buffers in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_conflict_startup_deadlock</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of queries cancelled because of recovery conflict with deadlocks in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_db_stat_reset_time</function>(<type>oid</type>)</literal></entry>
-      <entry><type>timestamptz</type></entry>
-      <entry>
-       Time of the last statistics reset for the database.  Initialized to the
-       system time during the first connection to each database.  The reset time
-       is updated when you call <function>pg_stat_reset</function> on the
-       database, as well as upon execution of
-       <function>pg_stat_reset_single_table_counters</function> against any
-       table or index in it.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_numscans</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of sequential scans done when argument is a table,
-       or number of index scans done when argument is an index
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_tuples_returned</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of rows read by sequential scans when argument is a table,
-       or number of index entries returned when argument is an index
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_tuples_fetched</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of table rows fetched by bitmap scans when argument is a table,
-       or table rows fetched by simple index scans using the index
-       when argument is an index
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_tuples_inserted</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of rows inserted into table
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_tuples_updated</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of rows updated in table (includes HOT updates)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_tuples_deleted</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of rows deleted from table
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_tuples_hot_updated</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of rows HOT-updated in table
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_live_tuples</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of live rows in table
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_dead_tuples</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of dead rows in table
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_blocks_fetched</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of disk block fetch requests for table or index
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_blocks_hit</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of disk block requests found in cache for table or index
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_last_vacuum_time</function>(<type>oid</type>)</literal></entry>
-      <entry><type>timestamptz</type></entry>
-      <entry>
-       Time of the last non-<option>FULL</option> vacuum initiated by the user on this table
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_last_autovacuum_time</function>(<type>oid</type>)</literal></entry>
-      <entry><type>timestamptz</type></entry>
-      <entry>
-       Time of the last vacuum initiated by the autovacuum daemon on this table
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_last_analyze_time</function>(<type>oid</type>)</literal></entry>
-      <entry><type>timestamptz</type></entry>
-      <entry>
-       Time of the last analyze initiated by the user on this table
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_last_autoanalyze_time</function>(<type>oid</type>)</literal></entry>
-      <entry><type>timestamptz</type></entry>
-      <entry>
-       Time of the last analyze initiated by the autovacuum daemon on this
-       table
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_vacuum_count</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       The number of times this table has been non-<option>FULL</> vacuumed manually
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_autovacuum_count</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       The number of times this table has been vacuumed by the autovacuum daemon
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_analyze_count</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       The number of times this table has been analyzed manually
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_autoanalyze_count</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       The number of times this table has been analyzed by the autovacuum daemon
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_numscans</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of sequential scans done when argument is a table,
-       or number of index scans done when argument is an index, in the current transaction
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_tuples_returned</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of rows read by sequential scans when argument is a table,
-       or number of index entries returned when argument is an index, in the current transaction
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_tuples_fetched</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of table rows fetched by bitmap scans when argument is a table,
-       or table rows fetched by simple index scans using the index
-       when argument is an index, in the current transaction
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_tuples_inserted</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of rows inserted into table, in the current transaction
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_tuples_updated</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of rows updated in table (includes HOT updates), in the current transaction
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_tuples_deleted</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of rows deleted from table, in the current transaction
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_tuples_hot_updated</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of rows HOT-updated in table, in the current transaction
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_blocks_fetched</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of disk block fetch requests for table or index, in the current transaction
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_blocks_hit</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of disk block requests found in cache for table or index, in the current transaction
-      </entry>
-     </row>
-
-     <row>
-       <!-- See also the entry for this in func.sgml -->
-      <entry><literal><function>pg_backend_pid()</function></literal></entry>
-      <entry><type>integer</type></entry>
-      <entry>
-       Process ID of the server process attached to the current session
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_activity</function>(<type>integer</type>)</literal></entry>
-      <entry><type>setof record</type></entry>
-      <entry>
-       Returns a record of information about the backend with the specified PID, or
-       one record for each active backend in the system if <symbol>NULL</symbol> is
-       specified. The fields returned are a subset of those in the
-       <structname>pg_stat_activity</structname> view.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_function_calls</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of times the function has been called
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_function_time</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Total wall clock time spent in the function, in microseconds.  Includes
-       the time spent in functions called by this one.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_function_self_time</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Time spent in only this function. Time spent in called functions
-       is excluded.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_function_calls</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of times the function has been called, in the current transaction.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_function_time</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Total wall clock time spent in the function, in microseconds, in the
-       current transaction.  Includes the time spent in functions called by
-       this one.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_xact_function_self_time</function>(<type>oid</type>)</literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Time spent in only this function, in the current transaction. Time
-       spent in called functions is excluded.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_idset()</function></literal></entry>
-      <entry><type>setof integer</type></entry>
-      <entry>
-       Set of currently active server process numbers (from 1 to the
-       number of active server processes).  See usage example in the text.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_pid</function>(<type>integer</type>)</literal></entry>
-      <entry><type>integer</type></entry>
-      <entry>
-       Process ID of the given server process
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_dbid</function>(<type>integer</type>)</literal></entry>
-      <entry><type>oid</type></entry>
-      <entry>
-       Database ID of the given server process
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_userid</function>(<type>integer</type>)</literal></entry>
-      <entry><type>oid</type></entry>
-      <entry>
-       User ID of the given server process
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_activity</function>(<type>integer</type>)</literal></entry>
-      <entry><type>text</type></entry>
-      <entry>
-       Active command of the given server process, but only if the
-       current user is a superuser or the same user as that of
-       the session being queried (and
-       <varname>track_activities</varname> is on)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_waiting</function>(<type>integer</type>)</literal></entry>
-      <entry><type>boolean</type></entry>
-      <entry>
-       True if the given server process is waiting for a lock,
-       but only if the current user is a superuser or the same user as that of
-       the session being queried (and
-       <varname>track_activities</varname> is on)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_activity_start</function>(<type>integer</type>)</literal></entry>
-      <entry><type>timestamp with time zone</type></entry>
-      <entry>
-       The time at which the given server process' currently
-       executing query was started, but only if the
-       current user is a superuser or the same user as that of
-       the session being queried (and
-       <varname>track_activities</varname> is on)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_xact_start</function>(<type>integer</type>)</literal></entry>
-      <entry><type>timestamp with time zone</type></entry>
-      <entry>
-       The time at which the given server process' currently
-       executing transaction was started, but only if the
-       current user is a superuser or the same user as that of
-       the session being queried (and
-       <varname>track_activities</varname> is on)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_start</function>(<type>integer</type>)</literal></entry>
-      <entry><type>timestamp with time zone</type></entry>
-      <entry>
-       The time at which the given server process was started, or
-       null if the current user is not a superuser nor the same user
-       as that of the session being queried
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_client_addr</function>(<type>integer</type>)</literal></entry>
-      <entry><type>inet</type></entry>
-      <entry>
-       The IP address of the client connected to the given
-       server process; null if the connection is over a Unix domain
-       socket, also null if the current user is not a superuser nor
-       the same user as that of the session being queried
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_backend_client_port</function>(<type>integer</type>)</literal></entry>
-      <entry><type>integer</type></entry>
-      <entry>
-       The TCP port number of the client connected to the given
-       server process; -1 if the connection is over a Unix domain
-       socket, null if the current user is not a superuser nor the
-       same user as that of the session being queried
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_bgwriter_timed_checkpoints()</function></literal></entry>
-       <entry><type>bigint</type></entry>
-       <entry>
-        Number of times the background writer has started timed checkpoints
-        (because the <varname>checkpoint_timeout</varname> time has expired)
-       </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_bgwriter_requested_checkpoints()</function></literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of times the background writer has started checkpoints based
-       on requests from backends because the <varname>checkpoint_segments</varname>
-       has been exceeded or because the <command>CHECKPOINT</command>
-       command has been issued
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_bgwriter_buf_written_checkpoints()</function></literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of buffers written by the background writer during checkpoints
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_bgwriter_buf_written_clean()</function></literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of buffers written by the background writer for routine cleaning of
-       dirty pages
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_bgwriter_maxwritten_clean()</function></literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of times the background writer has stopped its cleaning scan because
-       it has written more buffers than specified in the
-       <varname>bgwriter_lru_maxpages</varname> parameter
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_bgwriter_stat_reset_time()</function></literal></entry>
-      <entry><type>timestamptz</type></entry>
-      <entry>
-        Time of the last statistics reset for the background writer, updated
-        when executing <function>pg_stat_reset_shared('bgwriter')</function>
-        on the database cluster.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_buf_written_backend()</function></literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of buffers written by backends because they needed
-       to allocate a new buffer
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_get_buf_alloc()</function></literal></entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Total number of buffer allocations
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_clear_snapshot()</function></literal></entry>
-      <entry><type>void</type></entry>
-      <entry>
-       Discard the current statistics snapshot
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_reset()</function></literal></entry>
-      <entry><type>void</type></entry>
-      <entry>
-       Reset all statistics counters for the current database to zero
-       (requires superuser privileges)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_reset_shared</function>(text)</literal></entry>
-      <entry><type>void</type></entry>
-      <entry>
-       Reset some of the shared statistics counters for the database cluster to
-       zero (requires superuser privileges).  Calling
-       <literal>pg_stat_reset_shared('bgwriter')</> will zero all the values shown by
-       <structname>pg_stat_bgwriter</>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_reset_single_table_counters</function>(oid)</literal></entry>
-      <entry><type>void</type></entry>
-      <entry>
-       Reset statistics for a single table or index in the current database to
-       zero (requires superuser privileges)
-      </entry>
-     </row>
-
-     <row>
-      <entry><literal><function>pg_stat_reset_single_function_counters</function>(oid)</literal></entry>
-      <entry><type>void</type></entry>
-      <entry>
-       Reset statistics for a single function in the current database to
-       zero (requires superuser privileges)
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-   <note>
-    <para>
-     <function>pg_stat_get_blocks_fetched</function> minus
-     <function>pg_stat_get_blocks_hit</function> gives the number of kernel
-     <function>read()</> calls issued for the table, index, or
-     database; the number of actual physical reads is usually
-     lower due to kernel-level buffering.  The <literal>*_blks_read</>
-     statistics columns use this subtraction, i.e., fetched minus hit.
-    </para>
-   </note>
-
-  <para>
-   All functions to access information about backends are indexed by backend id
-   number, except <function>pg_stat_get_activity</function> which is indexed by PID.
-   The function <function>pg_stat_get_backend_idset</function> provides
-   a convenient way to generate one row for each active server process.  For
-   example, to show the <acronym>PID</>s and current queries of all server processes:
-
-<programlisting>
-SELECT pg_stat_get_backend_pid(s.backendid) AS procpid,
-       pg_stat_get_backend_activity(s.backendid) AS current_query
-    FROM (SELECT pg_stat_get_backend_idset() AS backendid) AS s;
-</programlisting>
-  </para>
-
- </sect2>
- </sect1>
-
- <sect1 id="monitoring-locks">
-  <title>Viewing Locks</title>
-
-  <indexterm zone="monitoring-locks">
-   <primary>lock</primary>
-   <secondary>monitoring</secondary>
-  </indexterm>
-&pgnotice;
-
-  <para>
-   Another useful tool for monitoring database activity is the
-   <structname>pg_locks</structname> system table.  It allows the
-   database administrator to view information about the outstanding
-   locks in the lock manager. For example, this capability can be used
-   to:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      View all the locks currently outstanding, all the locks on
-      relations in a particular database, all the locks on a
-      particular relation, or all the locks held by a particular
-      <productname>PostgreSQL</productname> session.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Determine the relation in the current database with the most
-      ungranted locks (which might be a source of contention among
-      database clients).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Determine the effect of lock contention on overall database
-      performance, as well as the extent to which contention varies
-      with overall database traffic.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   Details of the <structname>pg_locks</structname> view appear in
-   <xref linkend="view-pg-locks">.
-   For more information on locking and managing concurrency with
-   <productname>PostgreSQL</productname>, refer to <xref linkend="mvcc">.
-  </para>
- </sect1>
-
- <sect1 id="dynamic-trace">
-  <title>Dynamic Tracing</title>
-
- <indexterm zone="dynamic-trace">
-  <primary>DTrace</primary>
- </indexterm>
-&pgnotice;
-
-  <para>
-   <productname>PostgreSQL</productname> provides facilities to support
-   dynamic tracing of the database server. This allows an external
-   utility to be called at specific points in the code and thereby trace
-   execution.
-  </para>
-
-  <para>
-   A number of probes or trace points are already inserted into the source
-   code. These probes are intended to be used by database developers and
-   administrators. By default the probes are not compiled into
-   <productname>PostgreSQL</productname>; the user needs to explicitly tell
-   the configure script to make the probes available.
-  </para>
-
-  <para>
-   Currently, only the
-   <ulink url="http://opensolaris.org/os/community/dtrace/">DTrace</ulink>
-   utility is supported, which is available
-   on OpenSolaris, Solaris 10, and Mac OS X Leopard. It is expected that
-   DTrace will be available in the future on FreeBSD and possibly other
-   operating systems.  The
-   <ulink url="http://sourceware.org/systemtap/">SystemTap</ulink> project
-   for Linux also provides a DTrace equivalent.  Supporting other dynamic
-   tracing utilities is theoretically possible by changing the definitions for
-   the macros in <filename>src/include/utils/probes.h</>.
-  </para>
-
-  <sect2 id="compiling-for-trace">
-   <title>Compiling for Dynamic Tracing</title>
-&pgnotice;
-
-  <para>
-   By default, probes are not available, so you will need to
-   explicitly tell the configure script to make the probes available
-   in <productname>PostgreSQL</productname>. To include DTrace support
-   specify <option>--enable-dtrace</> to configure.  See <xref
-   linkend="install-procedure"> for further information.
-  </para>
-  </sect2>
-
-  <sect2 id="trace-points">
-   <title>Built-in Probes</title>
-&pgnotice;
-
-  <para>
-   A number of standard probes are provided in the source code,
-   as shown in <xref linkend="dtrace-probe-point-table">;
-   <xref linkend="typedefs-table">
-   shows the types used in the probes.  More probes can certainly be
-   added to enhance <productname>PostgreSQL</>'s observability.
-  </para>
-
- <table id="dtrace-probe-point-table">
-  <title>Built-in DTrace Probes</title>
-  <tgroup cols="3">
-   <thead>
-    <row>
-     <entry>Name</entry>
-     <entry>Parameters</entry>
-     <entry>Description</entry>
-    </row>
-   </thead>
-
-   <tbody>
-
-    <row>
-     <entry>transaction-start</entry>
-     <entry>(LocalTransactionId)</entry>
-     <entry>Probe that fires at the start of a new transaction.
-      arg0 is the transaction ID.</entry>
-    </row>
-    <row>
-     <entry>transaction-commit</entry>
-     <entry>(LocalTransactionId)</entry>
-     <entry>Probe that fires when a transaction completes successfully.
-      arg0 is the transaction ID.</entry>
-    </row>
-    <row>
-     <entry>transaction-abort</entry>
-     <entry>(LocalTransactionId)</entry>
-     <entry>Probe that fires when a transaction completes unsuccessfully.
-      arg0 is the transaction ID.</entry>
-    </row>
-    <row>
-     <entry>query-start</entry>
-     <entry>(const char *)</entry>
-     <entry>Probe that fires when the processing of a query is started.
-      arg0 is the query string.</entry>
-    </row>
-    <row>
-     <entry>query-done</entry>
-     <entry>(const char *)</entry>
-     <entry>Probe that fires when the processing of a query is complete.
-      arg0 is the query string.</entry>
-    </row>
-    <row>
-     <entry>query-parse-start</entry>
-     <entry>(const char *)</entry>
-     <entry>Probe that fires when the parsing of a query is started.
-      arg0 is the query string.</entry>
-    </row>
-    <row>
-     <entry>query-parse-done</entry>
-     <entry>(const char *)</entry>
-     <entry>Probe that fires when the parsing of a query is complete.
-      arg0 is the query string.</entry>
-    </row>
-    <row>
-     <entry>query-rewrite-start</entry>
-     <entry>(const char *)</entry>
-     <entry>Probe that fires when the rewriting of a query is started.
-      arg0 is the query string.</entry>
-    </row>
-    <row>
-     <entry>query-rewrite-done</entry>
-     <entry>(const char *)</entry>
-     <entry>Probe that fires when the rewriting of a query is complete.
-      arg0 is the query string.</entry>
-    </row>
-    <row>
-     <entry>query-plan-start</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when the planning of a query is started.</entry>
-    </row>
-    <row>
-     <entry>query-plan-done</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when the planning of a query is complete.</entry>
-    </row>
-    <row>
-     <entry>query-execute-start</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when the execution of a query is started.</entry>
-    </row>
-    <row>
-     <entry>query-execute-done</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when the execution of a query is complete.</entry>
-    </row>
-    <row>
-     <entry>statement-status</entry>
-     <entry>(const char *)</entry>
-     <entry>Probe that fires anytime the server process updates its
-      <structname>pg_stat_activity</>.<structfield>current_query</> status.
-      arg0 is the new status string.</entry>
-    </row>
-    <row>
-     <entry>checkpoint-start</entry>
-     <entry>(int)</entry>
-     <entry>Probe that fires when a checkpoint is started.
-      arg0 holds the bitwise flags used to distinguish different checkpoint
-      types, such as shutdown, immediate or force.</entry>
-    </row>
-    <row>
-     <entry>checkpoint-done</entry>
-     <entry>(int, int, int, int, int)</entry>
-     <entry>Probe that fires when a checkpoint is complete.
-      (The probes listed next fire in sequence during checkpoint processing.)
-      arg0 is the number of buffers written. arg1 is the total number of
-      buffers. arg2, arg3 and arg4 contain the number of xlog file(s) added,
-      removed and recycled respectively.</entry>
-    </row>
-    <row>
-     <entry>clog-checkpoint-start</entry>
-     <entry>(bool)</entry>
-     <entry>Probe that fires when the CLOG portion of a checkpoint is started.
-      arg0 is true for normal checkpoint, false for shutdown
-      checkpoint.</entry>
-    </row>
-    <row>
-     <entry>clog-checkpoint-done</entry>
-     <entry>(bool)</entry>
-     <entry>Probe that fires when the CLOG portion of a checkpoint is
-      complete. arg0 has the same meaning as for clog-checkpoint-start.</entry>
-    </row>
-    <row>
-     <entry>subtrans-checkpoint-start</entry>
-     <entry>(bool)</entry>
-     <entry>Probe that fires when the SUBTRANS portion of a checkpoint is
-      started.
-      arg0 is true for normal checkpoint, false for shutdown
-      checkpoint.</entry>
-    </row>
-    <row>
-     <entry>subtrans-checkpoint-done</entry>
-     <entry>(bool)</entry>
-     <entry>Probe that fires when the SUBTRANS portion of a checkpoint is
-      complete. arg0 has the same meaning as for
-      subtrans-checkpoint-start.</entry>
-    </row>
-    <row>
-     <entry>multixact-checkpoint-start</entry>
-     <entry>(bool)</entry>
-     <entry>Probe that fires when the MultiXact portion of a checkpoint is
-      started.
-      arg0 is true for normal checkpoint, false for shutdown
-      checkpoint.</entry>
-    </row>
-    <row>
-     <entry>multixact-checkpoint-done</entry>
-     <entry>(bool)</entry>
-     <entry>Probe that fires when the MultiXact portion of a checkpoint is
-      complete. arg0 has the same meaning as for
-      multixact-checkpoint-start.</entry>
-    </row>
-    <row>
-     <entry>buffer-checkpoint-start</entry>
-     <entry>(int)</entry>
-     <entry>Probe that fires when the buffer-writing portion of a checkpoint
-      is started.
-      arg0 holds the bitwise flags used to distinguish different checkpoint
-      types, such as shutdown, immediate or force.</entry>
-    </row>
-    <row>
-     <entry>buffer-sync-start</entry>
-     <entry>(int, int)</entry>
-     <entry>Probe that fires when we begin to write dirty buffers during
-      checkpoint (after identifying which buffers must be written).
-      arg0 is the total number of buffers.
-      arg1 is the number that are currently dirty and need to be written.</entry>
-    </row>
-    <row>
-     <entry>buffer-sync-written</entry>
-     <entry>(int)</entry>
-     <entry>Probe that fires after each buffer is written during checkpoint.
-      arg0 is the ID number of the buffer.</entry>
-    </row>
-    <row>
-     <entry>buffer-sync-done</entry>
-     <entry>(int, int, int)</entry>
-     <entry>Probe that fires when all dirty buffers have been written.
-      arg0 is the total number of buffers.
-      arg1 is the number of buffers actually written by the checkpoint process.
-      arg2 is the number that were expected to be written (arg1 of
-      buffer-sync-start); any difference reflects other processes flushing
-      buffers during the checkpoint.</entry>
-    </row>
-    <row>
-     <entry>buffer-checkpoint-sync-start</entry>
-     <entry>()</entry>
-     <entry>Probe that fires after dirty buffers have been written to the
-      kernel, and before starting to issue fsync requests.</entry>
-    </row>
-    <row>
-     <entry>buffer-checkpoint-done</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when syncing of buffers to disk is
-      complete.</entry>
-    </row>
-    <row>
-     <entry>twophase-checkpoint-start</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when the two-phase portion of a checkpoint is
-      started.</entry>
-    </row>
-    <row>
-     <entry>twophase-checkpoint-done</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when the two-phase portion of a checkpoint is
-      complete.</entry>
-    </row>
-    <row>
-     <entry>buffer-read-start</entry>
-     <entry>(ForkNumber, BlockNumber, Oid, Oid, Oid, int, bool)</entry>
-     <entry>Probe that fires when a buffer read is started.
-      arg0 and arg1 contain the fork and block numbers of the page (but
-      arg1 will be -1 if this is a relation extension request).
-      arg2, arg3, and arg4 contain the tablespace, database, and relation OIDs
-      identifying the relation.
-      arg5 is the ID of the backend which created the temporary relation for a
-      local buffer, or InvalidBackendId (-1) for a shared buffer.
-      arg6 is true for a relation extension request, false for normal
-      read.</entry>
-    </row>
-    <row>
-     <entry>buffer-read-done</entry>
-     <entry>(ForkNumber, BlockNumber, Oid, Oid, Oid, int, bool, bool)</entry>
-     <entry>Probe that fires when a buffer read is complete.
-      arg0 and arg1 contain the fork and block numbers of the page (if this
-      is a relation extension request, arg1 now contains the block number
-      of the newly added block).
-      arg2, arg3, and arg4 contain the tablespace, database, and relation OIDs
-      identifying the relation.
-      arg5 is the ID of the backend which created the temporary relation for a
-      local buffer, or InvalidBackendId (-1) for a shared buffer.
-      arg6 is true for a relation extension request, false for normal
-      read.
-      arg7 is true if the buffer was found in the pool, false if not.</entry>
-    </row>
-    <row>
-     <entry>buffer-flush-start</entry>
-     <entry>(ForkNumber, BlockNumber, Oid, Oid, Oid)</entry>
-     <entry>Probe that fires before issuing any write request for a shared
-      buffer.
-      arg0 and arg1 contain the fork and block numbers of the page.
-      arg2, arg3, and arg4 contain the tablespace, database, and relation OIDs
-      identifying the relation.</entry>
-    </row>
-    <row>
-     <entry>buffer-flush-done</entry>
-     <entry>(ForkNumber, BlockNumber, Oid, Oid, Oid)</entry>
-     <entry>Probe that fires when a write request is complete.  (Note
-      that this just reflects the time to pass the data to the kernel;
-      it's typically not actually been written to disk yet.)
-      The arguments are the same as for buffer-flush-start.</entry>
-    </row>
-    <row>
-     <entry>buffer-write-dirty-start</entry>
-     <entry>(ForkNumber, BlockNumber, Oid, Oid, Oid)</entry>
-     <entry>Probe that fires when a server process begins to write a dirty
-      buffer.  (If this happens often, it implies that
-      <xref linkend="guc-shared-buffers"> is too
-      small or the bgwriter control parameters need adjustment.)
-      arg0 and arg1 contain the fork and block numbers of the page.
-      arg2, arg3, and arg4 contain the tablespace, database, and relation OIDs
-      identifying the relation.</entry>
-    </row>
-    <row>
-     <entry>buffer-write-dirty-done</entry>
-     <entry>(ForkNumber, BlockNumber, Oid, Oid, Oid)</entry>
-     <entry>Probe that fires when a dirty-buffer write is complete.
-      The arguments are the same as for buffer-write-dirty-start.</entry>
-    </row>
-    <row>
-     <entry>wal-buffer-write-dirty-start</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when when a server process begins to write a
-      dirty WAL buffer because no more WAL buffer space is available.
-      (If this happens often, it implies that
-      <xref linkend="guc-wal-buffers"> is too small.)</entry>
-    </row>
-    <row>
-     <entry>wal-buffer-write-dirty-done</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when a dirty WAL buffer write is complete.</entry>
-    </row>
-    <row>
-     <entry>xlog-insert</entry>
-     <entry>(unsigned char, unsigned char)</entry>
-     <entry>Probe that fires when a WAL record is inserted.
-      arg0 is the resource manager (rmid) for the record.
-      arg1 contains the info flags.</entry>
-    </row>
-    <row>
-     <entry>xlog-switch</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when a WAL segment switch is requested.</entry>
-    </row>
-    <row>
-     <entry>smgr-md-read-start</entry>
-     <entry>(ForkNumber, BlockNumber, Oid, Oid, Oid, int)</entry>
-     <entry>Probe that fires when beginning to read a block from a relation.
-      arg0 and arg1 contain the fork and block numbers of the page.
-      arg2, arg3, and arg4 contain the tablespace, database, and relation OIDs
-      identifying the relation.
-      arg5 is the ID of the backend which created the temporary relation for a
-      local buffer, or InvalidBackendId (-1) for a shared buffer.</entry>
-    </row>
-    <row>
-     <entry>smgr-md-read-done</entry>
-     <entry>(ForkNumber, BlockNumber, Oid, Oid, Oid, int, int, int)</entry>
-     <entry>Probe that fires when a block read is complete.
-      arg0 and arg1 contain the fork and block numbers of the page.
-      arg2, arg3, and arg4 contain the tablespace, database, and relation OIDs
-      identifying the relation.
-      arg5 is the ID of the backend which created the temporary relation for a
-      local buffer, or InvalidBackendId (-1) for a shared buffer.
-      arg6 is the number of bytes actually read, while arg7 is the number
-      requested (if these are different it indicates trouble).</entry>
-    </row>
-    <row>
-     <entry>smgr-md-write-start</entry>
-     <entry>(ForkNumber, BlockNumber, Oid, Oid, Oid, int)</entry>
-     <entry>Probe that fires when beginning to write a block to a relation.
-      arg0 and arg1 contain the fork and block numbers of the page.
-      arg2, arg3, and arg4 contain the tablespace, database, and relation OIDs
-      identifying the relation.
-      arg5 is the ID of the backend which created the temporary relation for a
-      local buffer, or InvalidBackendId (-1) for a shared buffer.</entry>
-    </row>
-    <row>
-     <entry>smgr-md-write-done</entry>
-     <entry>(ForkNumber, BlockNumber, Oid, Oid, Oid, int, int, int)</entry>
-     <entry>Probe that fires when a block write is complete.
-      arg0 and arg1 contain the fork and block numbers of the page.
-      arg2, arg3, and arg4 contain the tablespace, database, and relation OIDs
-      identifying the relation.
-      arg5 is the ID of the backend which created the temporary relation for a
-      local buffer, or InvalidBackendId (-1) for a shared buffer.
-      arg6 is the number of bytes actually written, while arg7 is the number
-      requested (if these are different it indicates trouble).</entry>
-    </row>
-    <row>
-     <entry>sort-start</entry>
-     <entry>(int, bool, int, int, bool)</entry>
-     <entry>Probe that fires when a sort operation is started.
-      arg0 indicates heap, index or datum sort.
-      arg1 is true for unique-value enforcement.
-      arg2 is the number of key columns.
-      arg3 is the number of kilobytes of work memory allowed.
-      arg4 is true if random access to the sort result is required.</entry>
-    </row>
-    <row>
-     <entry>sort-done</entry>
-     <entry>(bool, long)</entry>
-     <entry>Probe that fires when a sort is complete.
-      arg0 is true for external sort, false for internal sort.
-      arg1 is the number of disk blocks used for an external sort,
-      or kilobytes of memory used for an internal sort.</entry>
-    </row>
-    <row>
-     <entry>lwlock-acquire</entry>
-     <entry>(LWLockId, LWLockMode)</entry>
-     <entry>Probe that fires when an LWLock has been acquired.
-      arg0 is the LWLock's ID.
-      arg1 is the requested lock mode, either exclusive or shared.</entry>
-    </row>
-    <row>
-     <entry>lwlock-release</entry>
-     <entry>(LWLockId)</entry>
-     <entry>Probe that fires when an LWLock has been released (but note
-      that any released waiters have not yet been awakened).
-      arg0 is the LWLock's ID.</entry>
-    </row>
-    <row>
-     <entry>lwlock-wait-start</entry>
-     <entry>(LWLockId, LWLockMode)</entry>
-     <entry>Probe that fires when an LWLock was not immediately available and
-      a server process has begun to wait for the lock to become available.
-      arg0 is the LWLock's ID.
-      arg1 is the requested lock mode, either exclusive or shared.</entry>
-    </row>
-    <row>
-     <entry>lwlock-wait-done</entry>
-     <entry>(LWLockId, LWLockMode)</entry>
-     <entry>Probe that fires when a server process has been released from its
-      wait for an LWLock (it does not actually have the lock yet).
-      arg0 is the LWLock's ID.
-      arg1 is the requested lock mode, either exclusive or shared.</entry>
-    </row>
-    <row>
-     <entry>lwlock-condacquire</entry>
-     <entry>(LWLockId, LWLockMode)</entry>
-     <entry>Probe that fires when an LWLock was successfully acquired when the
-      caller specified no waiting.
-      arg0 is the LWLock's ID.
-      arg1 is the requested lock mode, either exclusive or shared.</entry>
-    </row>
-    <row>
-     <entry>lwlock-condacquire-fail</entry>
-     <entry>(LWLockId, LWLockMode)</entry>
-     <entry>Probe that fires when an LWLock was not successfully acquired when
-      the caller specified no waiting.
-      arg0 is the LWLock's ID.
-      arg1 is the requested lock mode, either exclusive or shared.</entry>
-    </row>
-    <row>
-     <entry>lock-wait-start</entry>
-     <entry>(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, LOCKMODE)</entry>
-     <entry>Probe that fires when a request for a heavyweight lock (lmgr lock)
-      has begun to wait because the lock is not available.
-      arg0 through arg3 are the tag fields identifying the object being
-      locked.  arg4 indicates the type of object being locked.
-      arg5 indicates the lock type being requested.</entry>
-    </row>
-    <row>
-     <entry>lock-wait-done</entry>
-     <entry>(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, LOCKMODE)</entry>
-     <entry>Probe that fires when a request for a heavyweight lock (lmgr lock)
-      has finished waiting (i.e., has acquired the lock).
-      The arguments are the same as for lock-wait-start.</entry>
-    </row>
-    <row>
-     <entry>deadlock-found</entry>
-     <entry>()</entry>
-     <entry>Probe that fires when a deadlock is found by the deadlock
-      detector.</entry>
-    </row>
-
-   </tbody>
-   </tgroup>
-  </table>
-
- <table id="typedefs-table">
-  <title>Defined Types Used in Probe Parameters</title>
-  <tgroup cols="2">
-   <thead>
-    <row>
-     <entry>Type</entry>
-     <entry>Definition</entry>
-    </row>
-   </thead>
-
-   <tbody>
-
-    <row>
-     <entry>LocalTransactionId</entry>
-     <entry>unsigned int</entry>
-    </row>
-    <row>
-     <entry>LWLockId</entry>
-     <entry>int</entry>
-    </row>
-    <row>
-     <entry>LWLockMode</entry>
-     <entry>int</entry>
-    </row>
-    <row>
-     <entry>LOCKMODE</entry>
-     <entry>int</entry>
-    </row>
-    <row>
-     <entry>BlockNumber</entry>
-     <entry>unsigned int</entry>
-    </row>
-    <row>
-     <entry>Oid</entry>
-     <entry>unsigned int</entry>
-    </row>
-    <row>
-     <entry>ForkNumber</entry>
-     <entry>int</entry>
-    </row>
-    <row>
-     <entry>bool</entry>
-     <entry>char</entry>
-    </row>
-
-   </tbody>
-   </tgroup>
-  </table>
-
-
-  </sect2>
-
-  <sect2 id="using-trace-points">
-   <title>Using Probes</title>
-&pgnotice;
-
-  <para>
-   The example below shows a DTrace script for analyzing transaction
-   counts in the system, as an alternative to snapshotting
-   <structname>pg_stat_database</> before and after a performance test:
-<programlisting>
-#!/usr/sbin/dtrace -qs
-
-postgresql$1:::transaction-start
-{
-      @start["Start"] = count();
-      self->ts  = timestamp;
-}
-
-postgresql$1:::transaction-abort
-{
-      @abort["Abort"] = count();
-}
-
-postgresql$1:::transaction-commit
-/self->ts/
-{
-      @commit["Commit"] = count();
-      @time["Total time (ns)"] = sum(timestamp - self->ts);
-      self->ts=0;
-}
-</programlisting>
-   When executed, the example D script gives output such as:
-<screen>
-# ./txn_count.d `pgrep -n postgres` or ./txn_count.d &lt;PID&gt;
-^C
-
-Start                                          71
-Commit                                         70
-Total time (ns)                        2312105013
-</screen>
-  </para>
-
-  <note>
-   <para>
-    SystemTap uses a different notation for trace scripts than DTrace does,
-    even though the underlying trace points are compatible.  One point worth
-    noting is that at this writing, SystemTap scripts must reference probe
-    names using double underscores in place of hyphens.  This is expected to
-    be fixed in future SystemTap releases.
-   </para>
-  </note>
-
-  <para>
-   You should remember that DTrace scripts need to be carefully written and
-   debugged, otherwise the trace information collected might
-   be meaningless. In most cases where problems are found it is the
-   instrumentation that is at fault, not the underlying system. When
-   discussing information found using dynamic tracing, be sure to enclose
-   the script used to allow that too to be checked and discussed.
-  </para>
-
-  <para>
-   More example scripts can be found in the PgFoundry
-   <ulink url="http://pgfoundry.org/projects/dtrace/">dtrace project</ulink>.
-  </para>
-  </sect2>
-
-  <sect2 id="defining-trace-points">
-   <title>Defining New Probes</title>
-&pgnotice;
-
-  <para>
-   New probes can be defined within the code wherever the developer
-   desires, though this will require a recompilation. Below are the steps
-   for inserting new probes:
-  </para>
-
-  <procedure>
-   <step>
-    <para>
-     Decide on probe names and data to be made available through the probes
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Add the probe definitions to <filename>src/backend/utils/probes.d</>
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Include <filename>pg_trace.h</> if it is not already present in the
-     module(s) containing the probe points, and insert
-     <literal>TRACE_POSTGRESQL</> probe macros at the desired locations
-     in the source code
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Recompile and verify that the new probes are available
-    </para>
-   </step>
-  </procedure>
-
-  <formalpara>
-   <title>Example:</title>
-   <para>
-    Here is an example of how you would add a probe to trace all new
-    transactions by transaction ID.
-   </para>
-  </formalpara>
-
-  <procedure>
-   <step>
-    <para>
-     Decide that the probe will be named <literal>transaction-start</> and
-     requires a parameter of type LocalTransactionId
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Add the probe definition to <filename>src/backend/utils/probes.d</>:
-<programlisting>
-probe transaction__start(LocalTransactionId);
-</programlisting>
-     Note the use of the double underline in the probe name. In a DTrace
-     script using the probe, the double underline needs to be replaced with a
-     hyphen, so <literal>transaction-start</> is the name to document for
-     users.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     At compile time, <literal>transaction__start</> is converted to a macro
-     called <literal>TRACE_POSTGRESQL_TRANSACTION_START</> (notice the
-     underscores are single here), which is available by including
-     <filename>pg_trace.h</>.  Add the macro call to the appropriate location
-     in the source code.  In this case, it looks like the following:
-
-<programlisting>
-TRACE_POSTGRESQL_TRANSACTION_START(vxid.localTransactionId);
-</programlisting>
-    </para>
-   </step>
-
-   <step>
-    <para>
-     After recompiling and running the new binary, check that your newly added
-     probe is available by executing the following DTrace command.  You
-     should see similar output:
-<screen>
-# dtrace -ln transaction-start
-   ID    PROVIDER          MODULE           FUNCTION NAME
-18705 postgresql49878     postgres     StartTransactionCommand transaction-start
-18755 postgresql49877     postgres     StartTransactionCommand transaction-start
-18805 postgresql49876     postgres     StartTransactionCommand transaction-start
-18855 postgresql49875     postgres     StartTransactionCommand transaction-start
-18986 postgresql49873     postgres     StartTransactionCommand transaction-start
-</screen>
-    </para>
-   </step>
-  </procedure>
-
-  <para>
-   There are a few things to be careful about when adding trace macros
-   to the C code:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      You should take care that the data types specified for a probe's
-      parameters match the data types of the variables used in the macro.
-      Otherwise, you will get compilation errors.
-     </para>
-    </listitem>
-
-
-    <listitem>
-     <para>
-      On most platforms, if <productname>PostgreSQL</productname> is
-      built with <option>--enable-dtrace</>, the arguments to a trace
-      macro will be evaluated whenever control passes through the
-      macro, <emphasis>even if no tracing is being done</>.  This is
-      usually not worth worrying about if you are just reporting the
-      values of a few local variables.  But beware of putting expensive
-      function calls into the arguments.  If you need to do that,
-      consider protecting the macro with a check to see if the trace
-      is actually enabled:
-
-<programlisting>
-if (TRACE_POSTGRESQL_TRANSACTION_START_ENABLED())
-    TRACE_POSTGRESQL_TRANSACTION_START(some_function(...));
-</programlisting>
-
-      Each trace macro has a corresponding <literal>ENABLED</> macro.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-  </para>
-
-  </sect2>
-
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/mvcc.sgmlin b/doc-xc/src/sgml/mvcc.sgmlin
deleted file mode 100644
index cfd47dee30..0000000000
--- a/doc-xc/src/sgml/mvcc.sgmlin
+++ /dev/null
@@ -1,1872 +0,0 @@
-<!-- doc/src/sgml/mvcc.sgml -->
-
- <chapter id="mvcc">
-  <title>Concurrency Control</title>
-
-  <indexterm>
-   <primary>concurrency</primary>
-  </indexterm>
-
-<!## PG>
-  <para>
-   This chapter describes the behavior of the
-   <productname>PostgreSQL</productname> database system when two or
-   more sessions try to access the same data at the same time.  The
-   goals in that situation are to allow efficient access for all
-   sessions while maintaining strict data integrity.  Every developer
-   of database applications should be familiar with the topics covered
-   in this chapter.
-  </para>
-<!## end>
-<!## XC>
-&xconly;
-  <para>
-   This chapter describes the behavior of the
-   <productname>Postgres-XC</productname> database system when two or
-   more sessions try to access the same data at the same time.  The
-   goals in that situation are to allow efficient access for all
-   sessions while maintaining strict data integrity.  Every developer
-   of database applications should be familiar with the topics covered
-   in this chapter.
-  </para>
-  <para>
-   <productname>Postgres-XC</> inherited concurrency control
-   of <productname>PostgreSQL</> and extended it globally to whole
-   Coordinators and Datanodes involved.  Regardless of what
-   Coordinator to connect to, all the transactions
-   in <productname>Postgres-XC</> database cluster behaves in
-   consistent way as if they are running in single database.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   This chapter describes the behavior of the
-   <productname>Postgres-XL</productname> database system when two or
-   more sessions try to access the same data at the same time.  The
-   goals in that situation are to allow efficient access for all
-   sessions while maintaining strict data integrity.  Every developer
-   of database applications should be familiar with the topics covered
-   in this chapter.
-  </para>
-  <para>
-   <productname>Postgres-XL</> inherited concurrency control
-   from <productname>PostgreSQL</> and extended it globally to all of the
-   Coordinators and Datanodes involved.  Regardless of what
-   Coordinator is connected to, all of the transactions
-   in the <productname>Postgres-XL</> database cluster behaves in
-   a consistent way as if they are running in single database.
-  </para>
-<!## end>
-
-  <sect1 id="mvcc-intro">
-   <title>Introduction</title>
-
-   <indexterm>
-    <primary>Multiversion Concurrency Control</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>MVCC</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>Serializable Snapshot Isolation</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>SSI</primary>
-   </indexterm>
-
-<!## PG>
-   <para>
-    <productname>PostgreSQL</productname> provides a rich set of tools
-    for developers to manage concurrent access to data.  Internally,
-    data consistency is maintained by using a multiversion
-    model (Multiversion Concurrency Control, <acronym>MVCC</acronym>).
-    This means that while querying a database each transaction sees
-    a snapshot of data (a <firstterm>database version</firstterm>)
-    as it was some
-    time ago, regardless of the current state of the underlying data.
-    This protects the transaction from viewing inconsistent data that
-    could be caused by (other) concurrent transaction updates on the same
-    data rows, providing <firstterm>transaction isolation</firstterm>
-    for each database session.  <acronym>MVCC</acronym>, by eschewing
-    the locking methodologies of traditional database systems,
-    minimizes lock contention in order to allow for reasonable
-    performance in multiuser environments.
-   </para>
-<!## end>
-<!## XC>
-   <para>
-    <productname>Postgres-XC</productname> inherits a rich set of tools 
-    for developers to manage concurrent access to data from <productname>PostgreSQL</>.  Internally,
-    data consistency is maintained by using a multiversion 
-    model (Multiversion Concurrency Control, <acronym>MVCC</acronym>). 
-    This means that while querying a database each transaction sees
-    a snapshot of data (a <firstterm>database version</firstterm>)
-    as it was some
-    time ago, regardless of the current state of the underlying data.
-    This protects the transaction from viewing inconsistent data that
-    could be caused by (other) concurrent transaction updates on the same
-    data rows, providing <firstterm>transaction isolation</firstterm>
-    for each database session.  <acronym>MVCC</acronym>, by eschewing
-    explicit locking methodologies of traditional database systems,
-    minimizes lock contention in order to allow for reasonable 
-    performance in multiuser environments.
-   </para>
-<!## end>
-<!## XL>
-   <para>
-    <productname>Postgres-XL</productname> inherits a rich set of tools 
-    for developers to manage concurrent access to data from <productname>PostgreSQL</>.  Internally,
-    data consistency is maintained by using a multiversion 
-    model (Multiversion Concurrency Control, <acronym>MVCC</acronym>). 
-    This means that while querying a database each transaction sees
-    a snapshot of data (a <firstterm>database version</firstterm>)
-    as it was some
-    time ago, regardless of the current state of the underlying data.
-    This protects the transaction from viewing inconsistent data that
-    could be caused by (other) concurrent transaction updates on the same
-    data rows, providing <firstterm>transaction isolation</firstterm>
-    for each database session.  <acronym>MVCC</acronym>, by eschewing
-    explicit locking methodologies of traditional database systems,
-    minimizes lock contention in order to allow for reasonable 
-    performance in multiuser environments.
-   </para>
-<!## end>
-
-   <para>
-    The main advantage of using the <acronym>MVCC</acronym> model of
-    concurrency control rather than locking is that in
-    <acronym>MVCC</acronym> locks acquired for querying (reading) data
-    do not conflict with locks acquired for writing data, and so
-    reading never blocks writing and writing never blocks reading.
-    <productname>PostgreSQL</productname> maintains this guarantee
-    even when providing the strictest level of transaction
-    isolation through the use of an innovative <firstterm>Serializable
-    Snapshot Isolation</firstterm> (<acronym>SSI</acronym>) level.
-   </para>
-
-   <para>
-<!## PG>
-    Table- and row-level locking facilities are also available in
-    <productname>PostgreSQL</productname> for applications which don't
-    generally need full transaction isolation and prefer to explicitly
-    manage particular points of conflict.  However, proper
-    use of <acronym>MVCC</acronym> will generally provide better
-    performance than locks.  In addition, application-defined advisory
-    locks provide a mechanism for acquiring locks that are not tied
-    to a single transaction.
-<!## end>
-<!## XC>
-    As in <productname>PostgreSQL</>, table- and row-level locking facilities are also available in
-    <productname>Postgres-XC</productname> for applications that cannot
-    adapt easily to <acronym>MVCC</acronym> behavior.  However, proper
-    use of <acronym>MVCC</acronym> will generally provide better
-    performance than locks.  In addition, application-defined advisory
-    locks provide a mechanism for acquiring locks that are not tied
-    to a single transaction.
-<!## end>
-<!## XL>
-    As in <productname>PostgreSQL</>, table- and row-level locking facilities are also available in
-    <productname>Postgres-XL</productname> for applications that cannot
-    adapt easily to <acronym>MVCC</acronym> behavior.  However, proper
-    use of <acronym>MVCC</acronym> will generally provide better
-    performance than locks.  In addition, application-defined advisory
-    locks provide a mechanism for acquiring locks that are not tied
-    to a single transaction.
-<!## end>
-   </para>
-  </sect1>
-
-  <sect1 id="transaction-iso">
-   <title>Transaction Isolation</title>
-
-   <indexterm>
-    <primary>transaction isolation</primary>
-   </indexterm>
-
-&common;
-   <para>
-    The <acronym>SQL</acronym> standard defines four levels of
-    transaction isolation.  The most strict is Serializable,
-    which is defined by the standard in a paragraph which says that any
-    concurrent execution of a set of Serializable transactions is guaranteed
-    to produce the same effect as running them one at a time in some order.
-    The other three levels are defined in terms of phenomena, resulting from
-    interaction between concurrent transactions, which must not occur at
-    each level.  The standard notes that due to the definition of
-    Serializable, none of these phenomena are possible at that level.  (This
-    is hardly surprising -- if the effect of the transactions must be
-    consistent with having been run one at a time, how could you see any
-    phenomena caused by interactions?)
-   </para>
-
-   <para>
-    The phenomena which are prohibited are various levels are:
-
-    <variablelist>
-     <varlistentry>
-      <term>
-       dirty read
-       <indexterm><primary>dirty read</primary></indexterm>
-      </term>
-     <listitem>
-      <para>
-        A transaction reads data written by a concurrent uncommitted transaction.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       nonrepeatable read
-       <indexterm><primary>nonrepeatable read</primary></indexterm>
-      </term>
-     <listitem>
-      <para>
-        A transaction re-reads data it has previously read and finds that data
-        has been modified by another transaction (that committed since the
-        initial read).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       phantom read
-       <indexterm><primary>phantom read</primary></indexterm>
-      </term>
-     <listitem>
-      <para>
-        A transaction re-executes a query returning a set of rows that satisfy a
-        search condition and finds that the set of rows satisfying the condition
-        has changed due to another recently-committed transaction.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>transaction isolation level</primary>
-    </indexterm>
-    The four transaction isolation levels and the corresponding
-    behaviors are described in <xref linkend="mvcc-isolevel-table">.
-   </para>
-
-    <table tocentry="1" id="mvcc-isolevel-table">
-     <title><acronym>SQL</acronym> Transaction Isolation Levels</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>
-         Isolation Level
-        </entry>
-        <entry>
-         Dirty Read
-        </entry>
-        <entry>
-         Nonrepeatable Read
-        </entry>
-        <entry>
-         Phantom Read
-        </entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>
-         Read uncommitted
-        </entry>
-        <entry>
-         Possible
-        </entry>
-        <entry>
-         Possible
-        </entry>
-        <entry>
-         Possible
-        </entry>
-       </row>
-
-       <row>
-        <entry>
-         Read committed
-        </entry>
-        <entry>
-         Not possible
-        </entry>
-        <entry>
-         Possible
-        </entry>
-        <entry>
-         Possible
-        </entry>
-       </row>
-
-       <row>
-        <entry>
-         Repeatable read
-        </entry>
-        <entry>
-         Not possible
-        </entry>
-        <entry>
-         Not possible
-        </entry>
-        <entry>
-         Possible
-        </entry>
-       </row>
-
-       <row>
-        <entry>
-         Serializable
-        </entry>
-        <entry>
-         Not possible
-        </entry>
-        <entry>
-         Not possible
-        </entry>
-        <entry>
-         Not possible
-        </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-<!## PG>
-    In <productname>PostgreSQL</productname>, you can request any of the
-<!## end>
-<!## XC>
-    In <productname>Postgres-XC</productname>, you can request any of the
-<!## end>
-<!## XL>
-    In <productname>Postgres-XL</productname>, you can request any of the
-<!## end>
-    four standard transaction isolation levels.  But internally, there are
-    only three distinct isolation levels, which correspond to the levels Read
-    Committed, Repeatable Read, and Serializable.  When you select the level Read
-    Uncommitted you really get Read Committed, and phantom reads are not possible
-    in the <productname>PostgreSQL</productname> implementation of Repeatable
-    Read, so the actual
-    isolation level might be stricter than what you select.  This is
-    permitted by the SQL standard: the four isolation levels only
-    define which phenomena must not happen, they do not define which
-<!## PG>
-    phenomena must happen.  The reason that <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-    phenomena must happen.  The reason that <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-    phenomena must happen.  The reason that <productname>Postgres-XL</>
-<!## end>
-    only provides three isolation levels is that this is the only
-    sensible way to map the standard isolation levels to the multiversion
-    concurrency control architecture.  The behavior of the available
-    isolation levels is detailed in the following subsections.
-   </para>
-
-   <para>
-    To set the transaction isolation level of a transaction, use the
-    command <xref linkend="sql-set-transaction">.
-   </para>
-
-  <sect2 id="xact-read-committed">
-   <title>Read Committed Isolation Level</title>
-
-   <indexterm>
-    <primary>transaction isolation level</primary>
-    <secondary>read committed</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>read committed</primary>
-   </indexterm>
-
-&common;
-   <para>
-    <firstterm>Read Committed</firstterm> is the default isolation
-    level in <productname>PostgreSQL</productname>.  When a transaction
-    uses this isolation level, a <command>SELECT</command> query
-    (without a <literal>FOR UPDATE/SHARE</> clause) sees only data
-    committed before the query began; it never sees either uncommitted
-    data or changes committed during query execution by concurrent
-    transactions.  In effect, a <command>SELECT</command> query sees
-    a snapshot of the database as of the instant the query begins to
-    run.   However, <command>SELECT</command> does see the effects
-    of previous updates executed within its own transaction, even
-    though they are not yet committed.  Also note that two successive
-    <command>SELECT</command> commands can see different data, even
-    though they are within a single transaction, if other transactions
-    commit changes during execution of the first <command>SELECT</command>.
-   </para>
-
-   <para>
-    <command>UPDATE</command>, <command>DELETE</command>, <command>SELECT
-    FOR UPDATE</command>, and <command>SELECT FOR SHARE</command> commands
-    behave the same as <command>SELECT</command>
-    in terms of searching for target rows: they will only find target rows
-    that were committed as of the command start time.  However, such a target
-    row might have already been updated (or deleted or locked) by
-    another concurrent transaction by the time it is found.  In this case, the
-    would-be updater will wait for the first updating transaction to commit or
-    roll back (if it is still in progress).  If the first updater rolls back,
-    then its effects are negated and the second updater can proceed with
-    updating the originally found row.  If the first updater commits, the
-    second updater will ignore the row if the first updater deleted it,
-    otherwise it will attempt to apply its operation to the updated version of
-    the row.  The search condition of the command (the <literal>WHERE</> clause) is
-    re-evaluated to see if the updated version of the row still matches the
-    search condition.  If so, the second updater proceeds with its operation
-    using the updated version of the row.  In the case of
-    <command>SELECT FOR UPDATE</command> and <command>SELECT FOR
-    SHARE</command>, this means it is the updated version of the row that is
-    locked and returned to the client.
-   </para>
-
-   <para>
-    Because of the above rule, it is possible for an updating command to see an
-    inconsistent snapshot: it can see the effects of concurrent updating
-    commands on the same rows it is trying to update, but it
-    does not see effects of those commands on other rows in the database.
-    This behavior makes Read Committed mode unsuitable for commands that
-    involve complex search conditions; however, it is just right for simpler
-    cases.  For example, consider updating bank balances with transactions
-    like:
-
-<screen>
-BEGIN;
-UPDATE accounts SET balance = balance + 100.00 WHERE acctnum = 12345;
-UPDATE accounts SET balance = balance - 100.00 WHERE acctnum = 7534;
-COMMIT;
-</screen>
-
-    If two such transactions concurrently try to change the balance of account
-    12345, we clearly want the second transaction to start with the updated
-    version of the account's row.  Because each command is affecting only a
-    predetermined row, letting it see the updated version of the row does
-    not create any troublesome inconsistency.
-   </para>
-
-   <para>
-    More complex usage can produce undesirable results in Read Committed
-    mode.  For example, consider a <command>DELETE</command> command
-    operating on data that is being both added and removed from its
-    restriction criteria by another command, e.g., assume
-    <literal>website</literal> is a two-row table with
-    <literal>website.hits</literal> equaling <literal>9</literal> and
-    <literal>10</literal>:
-
-<screen>
-BEGIN;
-UPDATE website SET hits = hits + 1;
--- run from another session:  DELETE FROM website WHERE hits = 10;
-COMMIT;
-</screen>
-
-    The <command>DELETE</command> will have no effect even though
-    there is a <literal>website.hits = 10</literal> row before and
-    after the <command>UPDATE</command>. This occurs because the
-    pre-update row value <literal>9</> is skipped, and when the
-    <command>UPDATE</command> completes and <command>DELETE</command>
-    obtains a lock, the new row value is no longer <literal>10</> but
-    <literal>11</>, which no longer matches the criteria.
-   </para>
-
-   <para>
-    Because Read Committed mode starts each command with a new snapshot
-    that includes all transactions committed up to that instant,
-    subsequent commands in the same transaction will see the effects
-    of the committed concurrent transaction in any case.  The point
-    at issue above is whether or not a <emphasis>single</> command
-    sees an absolutely consistent view of the database.
-   </para>
-
-   <para>
-    The partial transaction isolation provided by Read Committed mode
-    is adequate for many applications, and this mode is fast and simple
-    to use;  however, it is not sufficient for all cases.  Applications
-    that do complex queries and updates might require a more rigorously
-    consistent view of the database than Read Committed mode provides.
-   </para>
-  </sect2>
-
-  <sect2 id="xact-repeatable-read">
-   <title>Repeatable Read Isolation Level</title>
-
-   <indexterm>
-    <primary>transaction isolation level</primary>
-    <secondary>repeatable read</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>repeatable read</primary>
-   </indexterm>
-
-   <para>
-    The <firstterm>Repeatable Read</firstterm> isolation level only sees
-    data committed before the transaction began; it never sees either
-    uncommitted data or changes committed during transaction execution
-    by concurrent transactions.  (However, the query does see the
-    effects of previous updates executed within its own transaction,
-    even though they are not yet committed.)  This is a stronger
-    guarantee than is required by the <acronym>SQL</acronym> standard
-    for this isolation level, and prevents all of the phenomena described
-    in <xref linkend="mvcc-isolevel-table">.  As mentioned above, this is
-    specifically allowed by the standard, which only describes the
-    <emphasis>minimum</emphasis> protections each isolation level must
-    provide.
-   </para>
-
-   <para>
-    This level is different from Read Committed in that a query in a
-    repeatable read transaction sees a snapshot as of the start of the
-    <emphasis>transaction</>, not as of the start
-    of the current query within the transaction.  Thus, successive
-    <command>SELECT</command> commands within a <emphasis>single</>
-    transaction see the same data, i.e., they do not see changes made by
-    other transactions that committed after their own transaction started.
-   </para>
-
-   <para>
-    Applications using this level must be prepared to retry transactions
-    due to serialization failures.
-   </para>
-
-   <para>
-    <command>UPDATE</command>, <command>DELETE</command>, <command>SELECT
-    FOR UPDATE</command>, and <command>SELECT FOR SHARE</command> commands
-    behave the same as <command>SELECT</command>
-    in terms of searching for target rows: they will only find target rows
-    that were committed as of the transaction start time.  However, such a
-    target row might have already been updated (or deleted or locked) by
-    another concurrent transaction by the time it is found.  In this case, the
-    repeatable read transaction will wait for the first updating transaction to commit or
-    roll back (if it is still in progress).  If the first updater rolls back,
-    then its effects are negated and the repeatable read transaction can proceed
-    with updating the originally found row.  But if the first updater commits
-    (and actually updated or deleted the row, not just locked it)
-    then the repeatable read transaction will be rolled back with the message
-
-<screen>
-ERROR:  could not serialize access due to concurrent update
-</screen>
-
-    because a repeatable read transaction cannot modify or lock rows changed by
-    other transactions after the repeatable read transaction began.
-   </para>
-
-   <para>
-    When an application receives this error message, it should abort
-    the current transaction and retry the whole transaction from
-    the beginning.  The second time through, the transaction will see the
-    previously-committed change as part of its initial view of the database,
-    so there is no logical conflict in using the new version of the row
-    as the starting point for the new transaction's update.
-   </para>
-
-   <para>
-    Note that only updating transactions might need to be retried; read-only
-    transactions will never have serialization conflicts.
-   </para>
-
-   <para>
-    The Repeatable Read mode provides a rigorous guarantee that each
-    transaction sees a completely stable view of the database.  However,
-    this view will not necessarily always be consistent with some serial
-    (one at a time) execution of concurrent transactions of the same level.
-    For example, even a read only transaction at this level may see a
-    control record updated to show that a batch has been completed but
-    <emphasis>not</emphasis> see one of the detail records which is logically
-    part of the batch because it read an earlier revision of the control
-    record.  Attempts to enforce business rules by transactions running at
-    this isolation level are not likely to work correctly without careful use
-    of explicit locks to block conflicting transactions.
-   </para>
-
-   <note>
-    <para>
-     Prior to <productname>PostgreSQL</productname> version 9.1, a request
-     for the Serializable transaction isolation level provided exactly the
-     same behavior described here.  To retain the legacy Serializable
-     behavior, Repeatable Read should now be requested.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2 id="xact-serializable">
-   <title>Serializable Isolation Level</title>
-
-   <indexterm>
-    <primary>transaction isolation level</primary>
-    <secondary>serializable</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>serializable</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>predicate locking</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>serialization anomaly</primary>
-   </indexterm>
-
-&common;
-   <para>
-    The <firstterm>Serializable</firstterm> isolation level provides the strictest transaction
-    isolation.  This level emulates serial transaction execution,
-    as if transactions had been executed one after another, serially,
-    rather than concurrently.  However, like the Repeatable Read level,
-    applications using this level must
-    be prepared to retry transactions due to serialization failures.
-    In fact, this isolation level works exactly the same as Repeatable
-    Read except that it monitors for conditions which could make
-    execution of a concurrent set of serializable transactions behave
-    in a manner inconsistent with all possible serial (one at a time)
-    executions of those transactions.  This monitoring does not
-    introduce any blocking beyond that present in repeatable read, but
-    there is some overhead to the monitoring, and detection of the
-    conditions which could cause a
-    <firstterm>serialization anomaly</firstterm> will trigger a
-    <firstterm>serialization failure</firstterm>.
-   </para>
-
-   <para>
-    As an example,
-    consider a table <structname>mytab</>, initially containing:
-<screen>
- class | value 
--------+-------
-     1 |    10
-     1 |    20
-     2 |   100
-     2 |   200
-</screen>
-    Suppose that serializable transaction A computes:
-<screen>
-SELECT SUM(value) FROM mytab WHERE class = 1;
-</screen>
-    and then inserts the result (30) as the <structfield>value</> in a
-    new row with <structfield>class</><literal> = 2</>.  Concurrently, serializable
-    transaction B computes:
-<screen>
-SELECT SUM(value) FROM mytab WHERE class = 2;
-</screen>
-    and obtains the result 300, which it inserts in a new row with
-    <structfield>class</><literal> = 1</>.  Then both transactions try to commit.
-    If either transaction were running at the Repeatable Read isolation level,
-    both would be allowed to commit; but since there is no serial order of execution
-    consistent with the result, using Serializable transactions will allow one
-    transaction to commit and and will roll the other back with this message:
-
-<screen>
-ERROR:  could not serialize access due to read/write dependencies among transactions
-</screen>
-
-    This is because if A had
-    executed before B, B would have computed the sum 330, not 300, and
-    similarly the other order would have resulted in a different sum
-    computed by A.
-   </para>
-
-   <para>
-    To guarantee true serializability <productname>PostgreSQL</productname>
-    uses <firstterm>predicate locking</>, which means that it keeps locks
-    which allow it to determine when a write would have had an impact on
-    the result of a previous read from a concurrent transaction, had it run
-    first.  In <productname>PostgreSQL</productname> these locks do not
-    cause any blocking and therefore can <emphasis>not</> play any part in
-    causing a deadlock.  They are used to identify and flag dependencies
-    among concurrent serializable transactions which in certain combinations
-    can lead to serialization anomalies.  In contrast, a Read Committed or
-    Repeatable Read transaction which wants to ensure data consistency may
-    need to take out a lock on an entire table, which could block other
-    users attempting to use that table, or it may use <literal>SELECT FOR
-    UPDATE</literal> or <literal>SELECT FOR SHARE</literal> which not only
-    can block other transactions but cause disk access.
-   </para>
-
-   <para>
-    Predicate locks in <productname>PostgreSQL</productname>, like in most
-    other database systems, are based on data actually accessed by a
-    transaction.  These will show up in the
-    <link linkend="view-pg-locks"><structname>pg_locks</structname></link>
-    system view with a <literal>mode</> of <literal>SIReadLock</>.  The
-    particular locks
-    acquired during execution of a query will depend on the plan used by
-    the query, and multiple finer-grained locks (e.g., tuple locks) may be
-    combined into fewer coarser-grained locks (e.g., page locks) during the
-    course of the transaction to prevent exhaustion of the memory used to
-    track the locks.  A <literal>READ ONLY</> transaction may be able to
-    release its SIRead locks before completion, if it detects that no
-    conflicts can still occur which could lead to a serialization anomaly.
-    In fact, <literal>READ ONLY</> transactions will often be able to
-    establish that fact at startup and avoid taking any predicate locks.
-    If you explicitly request a <literal>SERIALIZABLE READ ONLY DEFERRABLE</>
-    transaction, it will block until it can establish this fact.  (This is
-    the <emphasis>only</> case where Serializable transactions block but
-    Repeatable Read transactions don't.)  On the other hand, SIRead locks
-    often need to be kept past transaction commit, until overlapping read
-    write transactions complete.
-   </para>
-
-&common;
-   <para>
-    Consistent use of Serializable transactions can simplify development.
-    The guarantee that any set of concurrent serializable transactions will
-    have the same effect as if they were run one at a time means that if
-    you can demonstrate that a single transaction, as written, will do the
-    right thing when run by itself, you can have confidence that it will
-    do the right thing in any mix of serializable transactions, even without
-    any information about what those other transactions might do.  It is
-    important that an environment which uses this technique have a
-    generalized way of handling serialization failures (which always return
-    with a SQLSTATE value of '40001'), because it will be very hard to
-    predict exactly which transactions might contribute to the read/write
-    dependencies and need to be rolled back to prevent serialization
-    anomalies.  The monitoring of read/write dependencies has a cost, as does
-    the restart of transactions which are terminated with a serialization
-    failure, but balanced against the cost and blocking involved in use of
-    explicit locks and <literal>SELECT FOR UPDATE</> or <literal>SELECT FOR
-    SHARE</>, Serializable transactions are the best performance choice
-    for some environments.
-   </para>
-
-   <para>
-    For optimal performance when relying on Serializable transactions for
-    concurrency control, these issues should be considered:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Declare transactions as <literal>READ ONLY</> when possible.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Control the number of active connections, using a connection pool if
-       needed.  This is always an important performance consideration, but
-       it can be particularly important in a busy system using Serializable
-       transactions.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Don't put more into a single transaction than needed for integrity
-       purposes.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Don't leave connections dangling <quote>idle in transaction</quote>
-       longer than necessary.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Eliminate explicit locks, <literal>SELECT FOR UPDATE</>, and
-       <literal>SELECT FOR SHARE</> where no longer needed due to the
-       protections automatically provided by Serializable transactions.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <warning>
-    <para>
-     Support for the Serializable transaction isolation level has not yet
-     been added to Hot Standby replication targets (described in
-     <xref linkend="hot-standby">).  The strictest isolation level currently
-     supported in hot standby mode is Repeatable Read.  While performing all
-     permanent database writes within Serializable transactions on the
-     master will ensure that all standbys will eventually reach a consistent
-     state, a Repeatable Read transaction run on the standby can sometimes
-     see a transient state which is inconsistent with any serial execution
-     of serializable transactions on the master.
-    </para>
-   </warning>
-  </sect2>
- </sect1>
-
-  <sect1 id="explicit-locking">
-   <title>Explicit Locking</title>
-
-   <indexterm>
-    <primary>lock</primary>
-   </indexterm>
-
-&common;
-   <para>
-    <productname>PostgreSQL</productname> provides various lock modes
-    to control concurrent access to data in tables.  These modes can
-    be used for application-controlled locking in situations where
-    <acronym>MVCC</acronym> does not give the desired behavior.  Also,
-    most <productname>PostgreSQL</productname> commands automatically
-    acquire locks of appropriate modes to ensure that referenced
-    tables are not dropped or modified in incompatible ways while the
-    command executes.  (For example, <command>TRUNCATE</> cannot safely be
-    executed concurrently with other operations on the same table, so it
-    obtains an exclusive lock on the table to enforce that.)
-   </para>
-
-   <para>
-    To examine a list of the currently outstanding locks in a database
-    server, use the
-    <link linkend="view-pg-locks"><structname>pg_locks</structname></link>
-    system view. For more information on monitoring the status of the lock
-    manager subsystem, refer to <xref linkend="monitoring">.
-   </para>
-
-  <sect2 id="locking-tables">
-   <title>Table-level Locks</title>
-
-   <indexterm zone="locking-tables">
-    <primary>LOCK</primary>
-   </indexterm>
-
-&common;
-   <para>
-    The list below shows the available lock modes and the contexts in
-    which they are used automatically by
-    <productname>PostgreSQL</productname>.  You can also acquire any
-    of these locks explicitly with the command <xref
-    linkend="sql-lock">.
-    Remember that all of these lock modes are table-level locks,
-    even if the name contains the word
-    <quote>row</quote>; the names of the lock modes are historical.
-    To some extent the names reflect the typical usage of each lock
-    mode &mdash; but the semantics are all the same.  The only real difference
-    between one lock mode and another is the set of lock modes with
-    which each conflicts (see <xref linkend="table-lock-compatibility">).
-    Two transactions cannot hold locks of conflicting
-    modes on the same table at the same time.  (However, a transaction
-    never conflicts with itself.  For example, it might acquire
-    <literal>ACCESS EXCLUSIVE</literal> lock and later acquire
-    <literal>ACCESS SHARE</literal> lock on the same table.)  Non-conflicting
-    lock modes can be held concurrently by many transactions.  Notice in
-    particular that some lock modes are self-conflicting (for example,
-    an <literal>ACCESS EXCLUSIVE</literal> lock cannot be held by more than one
-    transaction at a time) while others are not self-conflicting (for example,
-    an <literal>ACCESS SHARE</literal> lock can be held by multiple transactions).
-   </para>
-
-     <variablelist>
-      <title>Table-level Lock Modes</title>
-      <varlistentry>
-       <term>
-        <literal>ACCESS SHARE</literal>
-       </term>
-       <listitem>
-        <para>
-         Conflicts with the <literal>ACCESS EXCLUSIVE</literal> lock
-         mode only.
-        </para>
-
-        <para>
-         The <command>SELECT</command> command acquires a lock of this mode on
-         referenced tables.  In general, any query that only <emphasis>reads</> a table
-         and does not modify it will acquire this lock mode.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>
-        <literal>ROW SHARE</literal>
-       </term>
-       <listitem>
-        <para>
-         Conflicts with the <literal>EXCLUSIVE</literal> and
-         <literal>ACCESS EXCLUSIVE</literal> lock modes.
-        </para>
-
-        <para>
-         The <command>SELECT FOR UPDATE</command> and
-         <command>SELECT FOR SHARE</command> commands acquire a
-         lock of this mode on the target table(s) (in addition to
-         <literal>ACCESS SHARE</literal> locks on any other tables
-         that are referenced but not selected
-         <option>FOR UPDATE/FOR SHARE</option>).
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>
-        <literal>ROW EXCLUSIVE</literal>
-       </term>
-       <listitem>
-        <para>
-         Conflicts with the <literal>SHARE</literal>, <literal>SHARE ROW
-         EXCLUSIVE</literal>, <literal>EXCLUSIVE</literal>, and
-         <literal>ACCESS EXCLUSIVE</literal> lock modes.
-        </para>
-
-        <para>
-         The commands <command>UPDATE</command>,
-         <command>DELETE</command>, and <command>INSERT</command>
-         acquire this lock mode on the target table (in addition to
-         <literal>ACCESS SHARE</literal> locks on any other referenced
-         tables).  In general, this lock mode will be acquired by any
-         command that <emphasis>modifies data</> in a table.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>
-        <literal>SHARE UPDATE EXCLUSIVE</literal>
-       </term>
-       <listitem>
-        <para>
-         Conflicts with the <literal>SHARE UPDATE EXCLUSIVE</literal>,
-         <literal>SHARE</literal>, <literal>SHARE ROW
-         EXCLUSIVE</literal>, <literal>EXCLUSIVE</literal>, and
-         <literal>ACCESS EXCLUSIVE</literal> lock modes.
-         This mode protects a table against
-         concurrent schema changes and <command>VACUUM</> runs.
-        </para>
-
-        <para>
-         Acquired by <command>VACUUM</command> (without <option>FULL</option>),
-         <command>ANALYZE</>, <command>CREATE INDEX CONCURRENTLY</>, and
-         some forms of <command>ALTER TABLE</command>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>
-        <literal>SHARE</literal>
-       </term>
-       <listitem>
-        <para>
-         Conflicts with the <literal>ROW EXCLUSIVE</literal>,
-         <literal>SHARE UPDATE EXCLUSIVE</literal>, <literal>SHARE ROW
-         EXCLUSIVE</literal>, <literal>EXCLUSIVE</literal>, and
-         <literal>ACCESS EXCLUSIVE</literal> lock modes.
-         This mode protects a table against concurrent data changes.
-        </para>
-
-        <para>
-         Acquired by <command>CREATE INDEX</command>
-         (without <option>CONCURRENTLY</option>).
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>
-        <literal>SHARE ROW EXCLUSIVE</literal>
-       </term>
-       <listitem>
-        <para>
-         Conflicts with the <literal>ROW EXCLUSIVE</literal>,
-         <literal>SHARE UPDATE EXCLUSIVE</literal>,
-         <literal>SHARE</literal>, <literal>SHARE ROW
-         EXCLUSIVE</literal>, <literal>EXCLUSIVE</literal>, and
-         <literal>ACCESS EXCLUSIVE</literal> lock modes.
-         This mode protects a table against concurrent data changes, and
-         is self-exclusive so that only one session can hold it at a time.
-        </para>
-
-        <para>
-         Acquired by <command>CREATE TRIGGER</command>,
-         <command>CREATE RULE</command> (except for <literal>ON SELECT</>
-         rules) and some forms of <command>ALTER TABLE</command>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>
-        <literal>EXCLUSIVE</literal>
-       </term>
-       <listitem>
-        <para>
-         Conflicts with the <literal>ROW SHARE</literal>, <literal>ROW
-         EXCLUSIVE</literal>, <literal>SHARE UPDATE
-         EXCLUSIVE</literal>, <literal>SHARE</literal>, <literal>SHARE
-         ROW EXCLUSIVE</literal>, <literal>EXCLUSIVE</literal>, and
-         <literal>ACCESS EXCLUSIVE</literal> lock modes.
-         This mode allows only concurrent <literal>ACCESS SHARE</literal> locks,
-         i.e., only reads from the table can proceed in parallel with a
-         transaction holding this lock mode.
-        </para>
-
-        <para>
-         This lock mode is not automatically acquired on tables by any
-         <productname>PostgreSQL</productname> command.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>
-        <literal>ACCESS EXCLUSIVE</literal>
-       </term>
-       <listitem>
-        <para>
-         Conflicts with locks of all modes (<literal>ACCESS
-         SHARE</literal>, <literal>ROW SHARE</literal>, <literal>ROW
-         EXCLUSIVE</literal>, <literal>SHARE UPDATE
-         EXCLUSIVE</literal>, <literal>SHARE</literal>, <literal>SHARE
-         ROW EXCLUSIVE</literal>, <literal>EXCLUSIVE</literal>, and
-         <literal>ACCESS EXCLUSIVE</literal>).
-         This mode guarantees that the
-         holder is the only transaction accessing the table in any way.
-        </para>
-
-        <para>
-         Acquired by the <command>DROP TABLE</command>,
-         <command>TRUNCATE</command>, <command>REINDEX</command>,
-         <command>CLUSTER</command>, and <command>VACUUM FULL</command>
-         commands, and some forms of <command>ALTER TABLE</>.
-         This is also the default lock mode for <command>LOCK TABLE</command>
-         statements that do not specify a mode explicitly.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-
-     <tip>
-      <para>
-       Only an <literal>ACCESS EXCLUSIVE</literal> lock blocks a
-       <command>SELECT</command> (without <option>FOR UPDATE/SHARE</option>)
-       statement.
-      </para>
-     </tip>
-
-   <para>
-    Once acquired, a lock is normally held till end of transaction.  But if a
-    lock is acquired after establishing a savepoint, the lock is released
-    immediately if the savepoint is rolled back to.  This is consistent with
-    the principle that <command>ROLLBACK</> cancels all effects of the
-    commands since the savepoint.  The same holds for locks acquired within a
-    <application>PL/pgSQL</> exception block: an error escape from the block
-    releases locks acquired within it.
-   </para>
-
-
-
-    <table tocentry="1" id="table-lock-compatibility">
-     <title> Conflicting Lock Modes</title>
-     <tgroup cols="9">
-      <colspec colnum="2" colname="lockst">
-      <colspec colnum="9" colname="lockend">
-      <spanspec namest="lockst" nameend="lockend" spanname="lockreq">
-      <thead>
-       <row>
-        <entry morerows="1">Requested Lock Mode</entry>
-        <entry spanname="lockreq">Current Lock Mode</entry>
-       </row>
-       <row>
-        <entry>ACCESS SHARE</entry>
-        <entry>ROW SHARE</entry>
-        <entry>ROW EXCLUSIVE</entry>
-        <entry>SHARE UPDATE EXCLUSIVE</entry>
-        <entry>SHARE</entry>
-        <entry>SHARE ROW EXCLUSIVE</entry>
-        <entry>EXCLUSIVE</entry>
-        <entry>ACCESS EXCLUSIVE</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>ACCESS SHARE</entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center">X</entry>
-       </row>
-       <row>
-        <entry>ROW SHARE</entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-       </row>
-       <row>
-        <entry>ROW EXCLUSIVE</entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-       </row>
-       <row>
-        <entry>SHARE UPDATE EXCLUSIVE</entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-       </row>
-       <row>
-        <entry>SHARE</entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center"></entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-       </row>
-       <row>
-        <entry>SHARE ROW EXCLUSIVE</entry>
-        <entry align="center"></entry>
-        <entry align="center"></entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-       </row>
-       <row>
-        <entry>EXCLUSIVE</entry>
-        <entry align="center"></entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-       </row>
-       <row>
-        <entry>ACCESS EXCLUSIVE</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-        <entry align="center">X</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </sect2>
-
-   <sect2 id="locking-rows">
-    <title>Row-level Locks</title>
-
-&common;
-    <para>
-     In addition to table-level locks, there are row-level locks, which
-     can be exclusive or shared locks.  An exclusive row-level lock on a
-     specific row is automatically acquired when the row is updated or
-     deleted.  The lock is held until the transaction commits or rolls
-     back, just like table-level locks.  Row-level locks do
-     not affect data querying; they block only <emphasis>writers to the same
-     row</emphasis>.
-    </para>
-
-    <para>
-     To acquire an exclusive row-level lock on a row without actually
-     modifying the row, select the row with <command>SELECT FOR
-     UPDATE</command>.  Note that once the row-level lock is acquired,
-     the transaction can update the row multiple times without
-     fear of conflicts.
-    </para>
-
-    <para>
-     To acquire a shared row-level lock on a row, select the row with
-     <command>SELECT FOR SHARE</command>.  A shared lock does not prevent
-     other transactions from acquiring the same shared lock.  However,
-     no transaction is allowed to update, delete, or exclusively lock a
-     row on which any other transaction holds a shared lock.  Any attempt
-     to do so will block until the shared lock(s) have been released.
-    </para>
-
-    <para>
-     <productname>PostgreSQL</productname> doesn't remember any
-     information about modified rows in memory, so there is no limit on
-     the number of rows locked at one time.  However, locking a row
-     might cause a disk write, e.g., <command>SELECT FOR
-     UPDATE</command> modifies selected rows to mark them locked, and so
-     will result in disk writes.
-    </para>
-
-    <para>
-     In addition to table and row locks, page-level share/exclusive locks are
-     used to control read/write access to table pages in the shared buffer
-     pool.  These locks are released immediately after a row is fetched or
-     updated.  Application developers normally need not be concerned with
-     page-level locks, but they are mentioned here for completeness.
-    </para>
-
-   </sect2>
-
-   <sect2 id="locking-deadlocks">
-    <title>Deadlocks</title>
-
-    <indexterm zone="locking-deadlocks">
-     <primary>deadlock</primary>
-    </indexterm>
-
-&common;
-    <para>
-     The use of explicit locking can increase the likelihood of
-     <firstterm>deadlocks</>, wherein two (or more) transactions each
-     hold locks that the other wants.  For example, if transaction 1
-     acquires an exclusive lock on table A and then tries to acquire
-     an exclusive lock on table B, while transaction 2 has already
-     exclusive-locked table B and now wants an exclusive lock on table
-     A, then neither one can proceed.
-     <productname>PostgreSQL</productname> automatically detects
-     deadlock situations and resolves them by aborting one of the
-     transactions involved, allowing the other(s) to complete.
-     (Exactly which transaction will be aborted is difficult to
-     predict and should not be relied upon.)
-    </para>
-
-    <para>
-     Note that deadlocks can also occur as the result of row-level
-     locks (and thus, they can occur even if explicit locking is not
-     used). Consider the case in which two concurrent
-     transactions modify a table. The first transaction executes:
-
-<screen>
-UPDATE accounts SET balance = balance + 100.00 WHERE acctnum = 11111;
-</screen>
-
-     This acquires a row-level lock on the row with the specified
-     account number. Then, the second transaction executes:
-
-<screen>
-UPDATE accounts SET balance = balance + 100.00 WHERE acctnum = 22222;
-UPDATE accounts SET balance = balance - 100.00 WHERE acctnum = 11111;
-</screen>
-
-     The first <command>UPDATE</command> statement successfully
-     acquires a row-level lock on the specified row, so it succeeds in
-     updating that row. However, the second <command>UPDATE</command>
-     statement finds that the row it is attempting to update has
-     already been locked, so it waits for the transaction that
-     acquired the lock to complete. Transaction two is now waiting on
-     transaction one to complete before it continues execution. Now,
-     transaction one executes:
-
-<screen>
-UPDATE accounts SET balance = balance - 100.00 WHERE acctnum = 22222;
-</screen>
-
-     Transaction one attempts to acquire a row-level lock on the
-     specified row, but it cannot: transaction two already holds such
-     a lock. So it waits for transaction two to complete. Thus,
-     transaction one is blocked on transaction two, and transaction
-     two is blocked on transaction one: a deadlock
-     condition. <productname>PostgreSQL</productname> will detect this
-     situation and abort one of the transactions.
-    </para>
-
-    <para>
-     The best defense against deadlocks is generally to avoid them by
-     being certain that all applications using a database acquire
-     locks on multiple objects in a consistent order. In the example
-     above, if both transactions
-     had updated the rows in the same order, no deadlock would have
-     occurred. One should also ensure that the first lock acquired on
-     an object in a transaction is the most restrictive mode that will be
-     needed for that object.  If it is not feasible to verify this in
-     advance, then deadlocks can be handled on-the-fly by retrying
-     transactions that abort due to deadlocks.
-    </para>
-
-    <para>
-     So long as no deadlock situation is detected, a transaction seeking
-     either a table-level or row-level lock will wait indefinitely for
-     conflicting locks to be released.  This means it is a bad idea for
-     applications to hold transactions open for long periods of time
-     (e.g., while waiting for user input).
-    </para>
-
-<!## XC>
-&xconly;
-    <para>
-     Please note that <productname>Postgres-XC</> does not detect
-     deadlocks which spreads among multiple Coordinators and/or
-     Datanodes, know as global deadlocks.  There are many discussions
-     whether global deadlocks should be detected or not, mainly
-     because of the cost of the detection.  So
-     far, <productname>Postgres-XC</> leave global deadlock detection
-     to timeout.
-    </para>
-<!## end>
-<!## XL>
-&xlonly;
-    <para>
-     Please note that <productname>Postgres-XL</> does not detect
-     deadlocks which are spread  among multiple Coordinators and/or
-     Datanodes, known as global deadlocks. 
-     Until this is implemented in
-     <productname>Postgres-XL</>, global deadlocks can be 
-     detected based on statement_timeout.
-    </para>
-<!## end>
-
-   </sect2>
-
-   <sect2 id="advisory-locks">
-    <title>Advisory Locks</title>
-
-    <indexterm zone="advisory-locks">
-     <primary>lock</primary>
-     <secondary>advisory</secondary>
-    </indexterm>
-
-&pgnotice;
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> provides a means for
-     creating locks that have application-defined meanings.  These are
-     called <firstterm>advisory locks</>, because the system does not
-     enforce their use &mdash; it is up to the application to use them
-     correctly.  Advisory locks can be useful for locking strategies
-     that are an awkward fit for the MVCC model.</para>
-
-    <para>
-     There are two different types of advisory locks in
-     <productname>PostgreSQL</productname>: session level and transaction level.
-     Once acquired, a session level advisory lock is held until explicitly
-     released or the session ends.  Unlike standard locks, session level
-     advisory locks do not honor transaction semantics: a lock acquired during
-     a transaction that is later rolled back will still be held following the
-     rollback, and likewise an unlock is effective even if the calling
-     transaction fails later.  The same session level lock can be acquired
-     multiple times by its owning process: for each lock request there must be
-     a corresponding unlock request before the lock is actually released.  (If a
-     session already holds a given lock, additional requests will always succeed,
-     even if other sessions are awaiting the lock.)  Transaction level locks on
-     the other hand behave more like regular locks; they are automatically
-     released at the end of the transaction, and can not be explicitly unlocked.
-     Session and transaction level locks share the same lock space, which means
-     that a transaction level lock will prevent another session from obtaining
-     a session level lock on that same resource and vice versa.
-     Like all locks in <productname>PostgreSQL</productname>, a complete list of
-     advisory locks currently held by any session can be found in the
-     <link linkend="view-pg-locks"><structname>pg_locks</structname></link>
-     system view.
-<!## end>
-<!## XC>
-     As in <productname>PostgreSQL</productname>, <productname>Postgres-XC</>  provides a means for
-     creating locks that have application-defined meanings.  These are
-     called <firstterm>advisory locks</>, because the system does not
-     enforce their use &mdash; it is up to the application to use them
-     correctly.  Advisory locks can be useful for locking strategies
-     that are an awkward fit for the MVCC model.  Once acquired, an
-     advisory lock is held until explicitly released or the session ends.
-     Unlike standard locks, advisory locks do not
-     honor transaction semantics: a lock acquired during a
-     transaction that is later rolled back will still be held following the
-     rollback, and likewise an unlock is effective even if the calling
-     transaction fails later.  The same lock can be acquired multiple times by
-     its owning process: for each lock request there must be a corresponding
-     unlock request before the lock is actually released.  (If a session
-     already holds a given lock, additional requests will always succeed, even
-     if other sessions are awaiting the lock.)  Like all locks in
-     <productname>PostgreSQL</productname>, a complete list of advisory
-     locks currently held by any session can be found in the
-     <link linkend="view-pg-locks"><structname>pg_locks</structname></link>
-     system view.
-<!## end>
-<!## XL>
-     As in <productname>PostgreSQL</productname>, <productname>Postgres-XL</>  provides a means for
-     creating locks that have application-defined meanings.  These are
-     called <firstterm>advisory locks</>, because the system does not
-     enforce their use &mdash; it is up to the application to use them
-     correctly.  Advisory locks can be useful for locking strategies
-     that are an awkward fit for the MVCC model.  Once acquired, an
-     advisory lock is held until explicitly released or the session ends.
-     Unlike standard locks, advisory locks do not
-     honor transaction semantics: a lock acquired during a
-     transaction that is later rolled back will still be held following the
-     rollback, and likewise an unlock is effective even if the calling
-     transaction fails later.  The same lock can be acquired multiple times by
-     its owning process: for each lock request there must be a corresponding
-     unlock request before the lock is actually released.  (If a session
-     already holds a given lock, additional requests will always succeed, even
-     if other sessions are awaiting the lock.)  Like all locks in
-     <productname>PostgreSQL</productname>, a complete list of advisory
-     locks currently held by any session can be found in the
-     <link linkend="view-pg-locks"><structname>pg_locks</structname></link>
-     system view.
-<!## end>
-    </para>
-
-    <para>
-     Advisory locks are allocated out of a shared memory pool whose size
-     is defined by the configuration variables
-     <xref linkend="guc-max-locks-per-transaction"> and
-     <xref linkend="guc-max-connections">.
-     Care must be taken not to exhaust this
-     memory or the server will be unable to grant any locks at all.
-     This imposes an upper limit on the number of advisory locks
-     grantable by the server, typically in the tens to hundreds of thousands
-     depending on how the server is configured.
-    </para>
-
-<!## XC>
-&xconly;
-    <para>
-     Please note that <productname>Postgres-XC</>'s advisory lock is
-     local to Coordinator or Datanode.  If you wish to acquire
-     advisory locks on different Coordinator, you should do it manually
-     using <type>EXECUTE DIRECT</> statement.
-    </para>
-<!## end>
-<!## XL>
-&xlonly;
-    <para>
-     Please note that <productname>Postgres-XL</>'s advisory lock is
-     local to each Coordinator or Datanode.  If you wish to acquire
-     advisory locks on different Coordinator, you should do it manually
-     using <type>EXECUTE DIRECT</> statement.
-    </para>
-<!## end>
-
-    <para>
-     A common use of advisory locks is to emulate pessimistic locking
-     strategies typical of so called <quote>flat file</> data management
-     systems.
-     While a flag stored in a table could be used for the same purpose,
-     advisory locks are faster, avoid MVCC bloat, and can be automatically
-     cleaned up by the server at the end of the session.
-     In certain cases using this advisory locking method, especially in queries
-     involving explicit ordering and <literal>LIMIT</> clauses, care must be
-     taken to control the locks acquired because of the order in which SQL
-     expressions are evaluated.  For example:
-<screen>
-SELECT pg_advisory_lock(id) FROM foo WHERE id = 12345; -- ok
-SELECT pg_advisory_lock(id) FROM foo WHERE id &gt; 12345 LIMIT 100; -- danger!
-SELECT pg_advisory_lock(q.id) FROM
-(
-  SELECT id FROM foo WHERE id &gt; 12345 LIMIT 100
-) q; -- ok
-</screen>
-     In the above queries, the second form is dangerous because the
-     <literal>LIMIT</> is not guaranteed to be applied before the locking
-     function is executed.  This might cause some locks to be acquired
-     that the application was not expecting, and hence would fail to release
-     (until it ends the session).
-     From the point of view of the application, such locks
-     would be dangling, although still viewable in
-     <structname>pg_locks</structname>.
-    </para>
-
-    <para>
-     The functions provided to manipulate advisory locks are described in
-     <xref linkend="functions-advisory-locks">.
-    </para>
-   </sect2>
-
-  </sect1>
-
-  <sect1 id="applevel-consistency">
-   <title>Data Consistency Checks at the Application Level</title>
-<!-- WIP: 23rd June, K.Suzuki -->
-<!-- NOTICE:
-  Need to check how locks associated with SELECT FOR UPDATE and SELECT FOR SHARE propagates for replicated tables.
--->
-
-&pgnotice;
-   <para>
-    It is very difficult to enforce business rules regarding data integrity
-    using Read Committed transactions because the view of the data is
-    shifting with each statement, and even a single statement may not
-    restrict itself to the statement's snapshot if a write conflict occurs.
-   </para>
-
-   <para>
-    While a Repeatable Read transaction has a stable view of the data
-    throughout its execution, there is a subtle issue with using
-    <acronym>MVCC</acronym> snapshots for data consistency checks, involving
-    something known as <firstterm>read/write conflicts</firstterm>.
-    If one transaction writes data and a concurrent transaction attempts
-    to read the same data (whether before or after the write), it cannot
-    see the work of the other transaction.  The reader then appears to have
-    executed first regardless of which started first or which committed
-    first.  If that is as far as it goes, there is no problem, but
-    if the reader also writes data which is read by a concurrent transaction
-    there is now a transaction which appears to have run before either of
-    the previously mentioned transactions.  If the transaction which appears
-    to have executed last actually commits first, it is very easy for a
-    cycle to appear in a graph of the order of execution of the transactions.
-    When such a cycle appears, integrity checks will not work correctly
-    without some help.
-   </para>
-
-   <para>
-    As mentioned in <xref linkend="xact-serializable">, Serializable
-    transactions are just Repeatable Read transactions which add
-    non-blocking monitoring for dangerous patterns of read/write conflicts.
-    When a pattern is detected which could cause a cycle in the apparent
-    order of execution, one of the transactions involved is rolled back to
-    break the cycle.
-   </para>
-
-   <sect2 id="serializable-consistency">
-    <title>Enforcing Consistency With Serializable Transactions</title>
-
-    <para>
-     If the Serializable transaction isolation level is used for all writes
-     and for all reads which need a consistent view of the data, no other
-     effort is required to ensure consistency.  Software from other
-     environments which is written to use serializable transactions to
-     ensure consistency should <quote>just work</quote> in this regard in
-     <productname>PostgreSQL</productname>.
-    </para>
-
-    <para>
-     When using this technique, it will avoid creating an unnecessary burden
-     for application programmers if the application software goes through a
-     framework which automatically retries transactions which are rolled
-     back with a serialization failure.  It may be a good idea to set
-     <literal>default_transaction_isolation</> to <literal>serializable</>.
-     It would also be wise to take some action to ensure that no other
-     transaction isolation level is used, either inadvertently or to
-     subvert integrity checks, through checks of the transaction isolation
-     level in triggers.
-    </para>
-
-    <para>
-     See <xref linkend="xact-serializable"> for performance suggestions.
-    </para>
-
-    <warning>
-     <para>
-      This level of integrity protection using Serializable transactions
-      does not yet extend to hot standby mode (<xref linkend="hot-standby">).
-      Because of that, those using hot standby may want to use Repeatable
-      Read and explicit locking.on the master.
-     </para>
-    </warning>
-   </sect2>
-
-   <sect2 id="non-serializable-consistency">
-    <title>Enforcing Consistency With Explicit Blocking Locks</title>
-
-    <para>
-     When non-serializable writes are possible,
-     to ensure the current validity of a row and protect it against
-     concurrent updates one must use <command>SELECT FOR UPDATE</command>,
-     <command>SELECT FOR SHARE</command>, or an appropriate <command>LOCK
-     TABLE</command> statement.  (<command>SELECT FOR UPDATE</command>
-     and <command>SELECT FOR SHARE</command> lock just the
-     returned rows against concurrent updates, while <command>LOCK
-     TABLE</command> locks the whole table.)  This should be taken into
-     account when porting applications to
-     <productname>PostgreSQL</productname> from other environments.
-    </para>
-
-    <para>
-     Also of note to those converting from other environments is the fact
-     that <command>SELECT FOR UPDATE</command> does not ensure that a
-     concurrent transaction will not update or delete a selected row.
-     To do that in <productname>PostgreSQL</productname> you must actually
-     update the row, even if no values need to be changed.
-     <command>SELECT FOR UPDATE</command> <emphasis>temporarily blocks</emphasis>
-     other transactions from acquiring the same lock or executing an
-     <command>UPDATE</command> or <command>DELETE</command> which would
-     affect the locked row, but once the transaction holding this lock
-     commits or rolls back, a blocked transaction will proceed with the
-     conflicting operation unless an actual <command>UPDATE</command> of
-     the row was performed while the lock was held.
-    </para>
-
-    <para>
-     Global validity checks require extra thought under
-     non-serializable <acronym>MVCC</acronym>.
-     For example, a banking application might wish to check that the sum of
-     all credits in one table equals the sum of debits in another table,
-     when both tables are being actively updated.  Comparing the results of two
-     successive <literal>SELECT sum(...)</literal> commands will not work reliably in
-     Read Committed mode, since the second query will likely include the results
-     of transactions not counted by the first.  Doing the two sums in a
-     single repeatable read transaction will give an accurate picture of only the
-     effects of transactions that committed before the repeatable read transaction
-     started &mdash; but one might legitimately wonder whether the answer is still
-     relevant by the time it is delivered.  If the repeatable read transaction
-     itself applied some changes before trying to make the consistency check,
-     the usefulness of the check becomes even more debatable, since now it
-     includes some but not all post-transaction-start changes.  In such cases
-     a careful person might wish to lock all tables needed for the check,
-     in order to get an indisputable picture of current reality.  A
-     <literal>SHARE</> mode (or higher) lock guarantees that there are no
-     uncommitted changes in the locked table, other than those of the current
-     transaction.
-    </para>
-
-    <para>
-     Note also that if one is relying on explicit locking to prevent concurrent
-     changes, one should either use Read Committed mode, or in Repeatable Read
-     mode be careful to obtain
-     locks before performing queries.  A lock obtained by a
-     repeatable read transaction guarantees that no other transactions modifying
-     the table are still running, but if the snapshot seen by the
-     transaction predates obtaining the lock, it might predate some now-committed
-     changes in the table.  A repeatable read transaction's snapshot is actually
-     frozen at the start of its first query or data-modification command
-     (<literal>SELECT</>, <literal>INSERT</>,
-     <literal>UPDATE</>, or <literal>DELETE</>), so
-     it is possible to obtain locks explicitly before the snapshot is
-     frozen.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="locking-indexes">
-   <title>Locking and Indexes</title>
-
-   <indexterm zone="locking-indexes">
-    <primary>index</primary>
-    <secondary>locks</secondary>
-   </indexterm>
-
-&common;
-   <para>
-    Though <productname>PostgreSQL</productname>
-    provides nonblocking read/write access to table
-    data, nonblocking read/write access is not currently offered for every
-    index access method implemented
-    in <productname>PostgreSQL</productname>.
-    The various index types are handled as follows:
-
-    <variablelist>
-     <varlistentry>
-      <term>
-       B-tree and <acronym>GiST</acronym> indexes
-      </term>
-      <listitem>
-       <para>
-        Short-term share/exclusive page-level locks are used for
-        read/write access. Locks are released immediately after each
-        index row is fetched or inserted.  These index types provide
-        the highest concurrency without deadlock conditions.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       Hash indexes
-      </term>
-      <listitem>
-       <para>
-        Share/exclusive hash-bucket-level locks are used for read/write
-        access.  Locks are released after the whole bucket is processed.
-        Bucket-level locks provide better concurrency than index-level
-        ones, but deadlock is possible since the locks are held longer
-        than one index operation.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       <acronym>GIN</acronym> indexes
-      </term>
-      <listitem>
-       <para>
-        Short-term share/exclusive page-level locks are used for
-        read/write access. Locks are released immediately after each
-        index row is fetched or inserted. But note that insertion of a
-        GIN-indexed value usually produces several index key insertions
-        per row, so GIN might do substantial work for a single value's
-        insertion.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    Currently, B-tree indexes offer the best performance for concurrent
-    applications; since they also have more features than hash
-    indexes, they are the recommended index type for concurrent
-    applications that need to index scalar data. When dealing with
-    non-scalar data, B-trees are not useful, and GiST or GIN indexes should
-    be used instead.
-   </para>
-  </sect1>
-
-<!## XC>
-  <sect1 id="global-transaction-management">
-   <title><productname>Postgres-XC</productname>'s Global Transaction Management</title>
-
-   <indexterm>
-    <primary>Global Transaction Management</primary>
-   </indexterm>
-
-&xconly;
-
-   <para>
-    The above sections
-    described <productname>Postgres-XC</productname>'s concurrency
-    control and MVCC common to <productname>PostgreSQL</productname>.
-    This section describes how <productname>Postgres-XC</productname>
-    implements global concurrency control and MVCC among multiple
-    Coordinators and Datanodes.
-   </para>
-
-   <para>
-    In conventional replication clusters, you can run read
-    transactions in parallel in multiple standby, or slave
-    servers. Replication servers provide read scalability. However,
-    you cannot issue write transactions to standby servers because
-    they don't have means to propagate changes safely. They cannot
-    maintain consistent view of database to applications for write
-    operations, unless you issue write transactions to single master
-    server.
-   </para>
-
-   <para>
-    Postgres-XC is different.
-   </para>
-
-   <para>
-    As described
-    in <xref linkend="intro-whatis">, <productname>Postgres-XC</productname>
-    is composed of GTM (Global Transaction Manager), Coordinators and
-    Datanodes.
-   </para>
-
-   <para>
-    In <productname>Postgres-XC</productname>, any Coordinator can
-    accept any transaction, regardless whether it is read only or
-    read/write.  Transaction integrity is enforced by GTM (global
-    transaction manager).  Because we have multiple Coordinators, each
-    of them can handle incoming transactions and statements in
-    parallel.
-   </para>
-
-   <para>
-    Analyzed statements are converted into internal plans, which
-    include SQL statements targeted to Datanodes.  They're proxied to
-    each target Datanode, handled and the result will be sent back to
-    originating Coordinator where all the results from target
-    Datanodes will be combined into the result to be sent back to the
-    application.
-   </para>
-
-   <para>
-    Each table can be distributed or replicated as described
-    in <xref linkend="intro-whatis">.  If you design each table's
-    distribution carefully, most of the statements may need to target
-    to just one Datanode.  In this way, Coordinators and Datanodes
-    runs transactions in parallel which scales out both read and write
-    operations.
-   </para>
-
-   <para>
-    More detailed internals
-    about <productname>Postgres-XC</productname>'s transaction
-    management will be found in <xref linkend="overview">.
-   </para>
-  </sect1>
-<!## end>
-<!## XL>
-  <sect1 id="global-transaction-management">
-   <title><productname>Postgres-XL</productname>'s Global Transaction Management</title>
-
-   <indexterm>
-    <primary>Global Transaction Management</primary>
-   </indexterm>
-
-&xlonly;
-
-   <para>
-    The above sections
-    described <productname>Postgres-XL</productname>'s concurrency
-    control and MVCC common to <productname>PostgreSQL</productname>.
-    This section describes how <productname>Postgres-XL</productname>
-    implements global concurrency control and MVCC among multiple
-    Coordinators and Datanodes.
-   </para>
-
-   <para>
-    In conventional replication clusters, you can run read
-    transactions concurrently in multiple standby, or slave
-    servers. Replication servers provide read scalability. However,
-    you cannot issue write transactions to standby servers because
-    they don't have means to propagate changes safely. They cannot
-    maintain consistent view of database to applications for write
-    operations, unless you issue write transactions to single master
-    server.
-   </para>
-
-   <para>
-    Postgres-XL is different.
-   </para>
-
-   <para>
-    As described
-    in <xref linkend="intro-whatis">, <productname>Postgres-XL</productname>
-    is composed of a GTM (Global Transaction Manager), Coordinators and
-    Datanodes.
-   </para>
-
-   <para>
-    In <productname>Postgres-XL</productname>, any Coordinator can
-    accept any transaction, regardless whether it is read only or
-    read/write.  Transaction integrity is enforced by GTM (Global
-    Transaction Manager).  Because we have multiple Coordinators, each
-    of them can handle incoming transactions and statements in
-    parallel.
-   </para>
-
-   <para>
-    Analyzed statements are converted into internal plans, which
-    include SQL statements targeted to Datanodes.  Plans are sent on to
-    each target Datanode, handled, and the result is sent back to
-    the originating Coordinator where all the results from target
-    Datanodes will be combined into the result to be sent back to the
-    application.
-   </para>
-
-   <para>
-    Each table can be distributed or replicated as described
-    in <xref linkend="intro-whatis">.  If you design each table's
-    distribution carefully, most of the statements may end up targeting
-    just one Datanode, which is most effecient.  In this way, Coordinators and Datanodes
-    runs transactions in parallel which scales out both read and write
-    operations.
-   </para>
-
-   <para>
-    More detailed internals
-    about <productname>Postgres-XL</productname>'s transaction
-    management will be found in <xref linkend="overview">.
-   </para>
-  </sect1>
-<!## end>
- </chapter>
diff --git a/doc-xc/src/sgml/nls.sgmlin b/doc-xc/src/sgml/nls.sgmlin
deleted file mode 100644
index 05ae697604..0000000000
--- a/doc-xc/src/sgml/nls.sgmlin
+++ /dev/null
@@ -1,570 +0,0 @@
-<!-- doc/src/sgml/nls.sgml -->
-
-<chapter id="nls">
- <chapterinfo>
-  <author>
-   <firstname>Peter</firstname>
-   <surname>Eisentraut</surname>
-  </author>
- </chapterinfo>
-
- <title>Native Language Support</title>
-
- <sect1 id="nls-translator">
-  <title>For the Translator</title>
-
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</>
-<!## end>
-   programs (server and client) can issue their messages in
-   your favorite language &mdash; if the messages have been translated.
-   Creating and maintaining translated message sets needs the help of
-   people who speak their own language well and want to contribute to
-<!## PG>
-   the <productname>PostgreSQL</> effort.  You do not have to be a
-<!## end>
-<!## XC>
-   the <productname>Postgres-XC</> effort.  You do not have to be a
-<!## end>
-<!## XL>
-   the <productname>Postgres-XL</> effort.  You do not have to be a
-<!## end>
-   programmer at all
-   to do this.  This section explains how to help.
-  </para>
-
-  <sect2>
-   <title>Requirements</title>
-
-&common;
-   <para>
-    We won't judge your language skills &mdash; this section is about
-    software tools.  Theoretically, you only need a text editor.  But
-    this is only in the unlikely event that you do not want to try out
-    your translated messages.  When you configure your source tree, be
-    sure to use the <option>--enable-nls</option> option.  This will
-    also check for the <application>libintl</application> library and the
-    <filename>msgfmt</filename> program, which all end users will need
-    anyway.  To try out your work, follow the applicable portions of
-    the installation instructions.
-   </para>
-
-   <para>
-    If you want to start a new translation effort or want to do a
-    message catalog merge (described later), you will need the
-    programs <filename>xgettext</filename> and
-    <filename>msgmerge</filename>, respectively, in a GNU-compatible
-    implementation.  Later, we will try to arrange it so that if you
-    use a packaged source distribution, you won't need
-    <filename>xgettext</filename>.  (If working from Git, you will still need
-    it.)  <application>GNU Gettext 0.10.36</application> or later is currently recommended.
-   </para>
-
-   <para>
-    Your local gettext implementation should come with its own
-    documentation.  Some of that is probably duplicated in what
-    follows, but for additional details you should look there.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Concepts</title>
-
-&common;
-   <para>
-    The pairs of original (English) messages and their (possibly)
-    translated equivalents are kept in <firstterm>message
-    catalogs</firstterm>, one for each program (although related
-    programs can share a message catalog) and for each target
-    language.  There are two file formats for message catalogs:  The
-    first is the <quote>PO</quote> file (for Portable Object), which
-    is a plain text file with special syntax that translators edit.
-    The second is the <quote>MO</quote> file (for Machine Object),
-    which is a binary file generated from the respective PO file and
-    is used while the internationalized program is run.  Translators
-    do not deal with MO files; in fact hardly anyone does.
-   </para>
-
-   <para>
-    The extension of the message catalog file is to no surprise either
-    <filename>.po</filename> or <filename>.mo</filename>.  The base
-    name is either the name of the program it accompanies, or the
-    language the file is for, depending on the situation.  This is a
-    bit confusing.  Examples are <filename>psql.po</filename> (PO file
-    for psql) or <filename>fr.mo</filename> (MO file in French).
-   </para>
-
-   <para>
-    The file format of the PO files is illustrated here:
-<programlisting>
-# comment
-
-msgid "original string"
-msgstr "translated string"
-
-msgid "more original"
-msgstr "another translated"
-"string can be broken up like this"
-
-...
-</programlisting>
-    The msgid's are extracted from the program source.  (They need not
-    be, but this is the most common way.)  The msgstr lines are
-    initially empty and are filled in with useful strings by the
-    translator.  The strings can contain C-style escape characters and
-    can be continued across lines as illustrated.  (The next line must
-    start at the beginning of the line.)
-   </para>
-
-   <para>
-    The # character introduces a comment.  If whitespace immediately
-    follows the # character, then this is a comment maintained by the
-    translator.  There can also be automatic comments, which have a
-    non-whitespace character immediately following the #.  These are
-    maintained by the various tools that operate on the PO files and
-    are intended to aid the translator.
-<programlisting>
-#. automatic comment
-#: filename.c:1023
-#, flags, flags
-</programlisting>
-    The #. style comments are extracted from the source file where the
-    message is used.  Possibly the programmer has inserted information
-    for the translator, such as about expected alignment.  The #:
-    comment indicates the exact location(s) where the message is used
-    in the source.  The translator need not look at the program
-    source, but he can if there is doubt about the correct
-    translation.  The #, comments contain flags that describe the
-    message in some way.  There are currently two flags:
-    <literal>fuzzy</literal> is set if the message has possibly been
-    outdated because of changes in the program source.  The translator
-    can then verify this and possibly remove the fuzzy flag.  Note
-    that fuzzy messages are not made available to the end user.  The
-    other flag is <literal>c-format</literal>, which indicates that
-    the message is a <function>printf</function>-style format
-    template.  This means that the translation should also be a format
-    string with the same number and type of placeholders.  There are
-    tools that can verify this, which key off the c-format flag.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Creating and Maintaining Message Catalogs</title>
-
-&common;
-   <para>
-    OK, so how does one create a <quote>blank</quote> message
-    catalog?  First, go into the directory that contains the program
-    whose messages you want to translate.  If there is a file
-    <filename>nls.mk</filename>, then this program has been prepared
-    for translation.
-   </para>
-
-   <para>
-    If there are already some <filename>.po</filename> files, then
-    someone has already done some translation work.  The files are
-    named <filename><replaceable>language</replaceable>.po</filename>,
-    where <replaceable>language</replaceable> is the
-    <ulink url="http://www.loc.gov/standards/iso639-2/php/English_list.php">
-    ISO 639-1 two-letter language code (in lower case)</ulink>, e.g.,
-    <filename>fr.po</filename> for French.  If there is really a need
-    for more than one translation effort per language then the files
-    can also be named
-    <filename><replaceable>language</replaceable>_<replaceable>region</replaceable>.po</filename>
-    where <replaceable>region</replaceable> is the
-    <ulink url="http://www.iso.org/iso/english_country_names_and_code_elements">
-    ISO 3166-1 two-letter country code (in upper case)</ulink>,
-    e.g.,
-    <filename>pt_BR.po</filename> for Portuguese in Brazil.  If you
-    find the language you wanted you can just start working on that
-    file.
-   </para>
-
-   <para>
-    If you need to start a new translation effort, then first run the
-    command:
-<programlisting>
-gmake init-po
-</programlisting>
-    This will create a file
-    <filename><replaceable>progname</replaceable>.pot</filename>.
-    (<filename>.pot</filename> to distinguish it from PO files that
-    are <quote>in production</quote>. The <literal>T</> stands for
-    <quote>template</>.)
-    Copy this file to
-    <filename><replaceable>language</replaceable>.po</filename> and
-    edit it.  To make it known that the new language is available,
-    also edit the file <filename>nls.mk</filename> and add the
-    language (or language and country) code to the line that looks like:
-<programlisting>
-AVAIL_LANGUAGES := de fr
-</programlisting>
-    (Other languages can appear, of course.)
-   </para>
-
-   <para>
-    As the underlying program or library changes, messages might be
-    changed or added by the programmers.  In this case you do not need
-    to start from scratch.  Instead, run the command:
-<programlisting>
-gmake update-po
-</programlisting>
-    which will create a new blank message catalog file (the pot file
-    you started with) and will merge it with the existing PO files.
-    If the merge algorithm is not sure about a particular message it
-    marks it <quote>fuzzy</quote> as explained above.  The new PO file
-    is saved with a <filename>.po.new</filename> extension.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Editing the PO Files</title>
-
-&common;
-   <para>
-    The PO files can be edited with a regular text editor.  The
-    translator should only change the area between the quotes after
-    the msgstr directive, add comments, and alter the fuzzy flag.
-    There is (unsurprisingly) a PO mode for Emacs, which I find quite
-    useful.
-   </para>
-
-   <para>
-    The PO files need not be completely filled in.  The software will
-    automatically fall back to the original string if no translation
-    (or an empty translation) is available.  It is no problem to
-    submit incomplete translations for inclusions in the source tree;
-    that gives room for other people to pick up your work.  However,
-    you are encouraged to give priority to removing fuzzy entries
-    after doing a merge.  Remember that fuzzy entries will not be
-    installed; they only serve as reference for what might be the right
-    translation.
-   </para>
-
-   <para>
-    Here are some things to keep in mind while editing the
-    translations:
-    <itemizedlist>
-     <listitem>
-      <para>
-       Make sure that if the original ends with a newline, the
-       translation does, too.  Similarly for tabs, etc.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If the original is a <function>printf</> format string, the translation
-       also needs to be.  The translation also needs to have the same
-       format specifiers in the same order.  Sometimes the natural
-       rules of the language make this impossible or at least awkward.
-       In that case you can modify the format specifiers like this:
-<programlisting>
-msgstr "Die Datei %2$s hat %1$u Zeichen."
-</programlisting>
-       Then the first placeholder will actually use the second
-       argument from the list.  The
-       <literal><replaceable>digits</replaceable>$</literal> needs to
-       follow the % immediately, before any other format manipulators.
-       (This feature really exists in the <function>printf</function>
-       family of functions.  You might not have heard of it before because
-       there is little use for it outside of message
-       internationalization.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If the original string contains a linguistic mistake, report
-       that (or fix it yourself in the program source) and translate
-       normally.  The corrected string can be merged in when the
-       program sources have been updated.  If the original string
-       contains a factual mistake, report that (or fix it yourself)
-       and do not translate it.  Instead, you can mark the string with
-       a comment in the PO file.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Maintain the style and tone of the original string.
-       Specifically, messages that are not sentences (<literal>cannot
-       open file %s</literal>) should probably not start with a
-       capital letter (if your language distinguishes letter case) or
-       end with a period (if your language uses punctuation marks).
-       It might help to read <xref linkend="error-style-guide">.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If you don't know what a message means, or if it is ambiguous,
-       ask on the developers' mailing list.  Chances are that English
-       speaking end users might also not understand it or find it
-       ambiguous, so it's best to improve the message.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </para>
-  </sect2>
-
- </sect1>
-
-
- <sect1 id="nls-programmer">
-  <title>For the Programmer</title>
-
-  <sect2 id="nls-mechanics">
-   <title>Mechanics</title>
-
-&common;
-  <para>
-   This section describes how to implement native language support in a
-   program or library that is part of the
-<!## PG>
-   <productname>PostgreSQL</> distribution.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> distribution.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> distribution.
-<!## end>
-   Currently, it only applies to C programs.
-  </para>
-
-  <procedure>
-   <title>Adding NLS Support to a Program</title>
-
-   <step>
-    <para>
-     Insert this code into the start-up sequence of the program:
-<programlisting>
-#ifdef ENABLE_NLS
-#include &lt;locale.h&gt;
-#endif
-
-...
-
-#ifdef ENABLE_NLS
-setlocale(LC_ALL, "");
-bindtextdomain("<replaceable>progname</replaceable>", LOCALEDIR);
-textdomain("<replaceable>progname</replaceable>");
-#endif
-</programlisting>
-     (The <replaceable>progname</replaceable> can actually be chosen
-     freely.)
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Wherever a message that is a candidate for translation is found,
-     a call to <function>gettext()</function> needs to be inserted.  E.g.:
-<programlisting>
-fprintf(stderr, "panic level %d\n", lvl);
-</programlisting>
-     would be changed to:
-<programlisting>
-fprintf(stderr, gettext("panic level %d\n"), lvl);
-</programlisting>
-     (<symbol>gettext</symbol> is defined as a no-op if NLS support is
-     not configured.)
-    </para>
-
-    <para>
-     This tends to add a lot of clutter.  One common shortcut is to use:
-<programlisting>
-#define _(x) gettext(x)
-</programlisting>
-     Another solution is feasible if the program does much of its
-     communication through one or a few functions, such as
-     <function>ereport()</function> in the backend.  Then you make this
-     function call <function>gettext</function> internally on all
-     input strings.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Add a file <filename>nls.mk</filename> in the directory with the
-     program sources.  This file will be read as a makefile.  The
-     following variable assignments need to be made here:
-
-     <variablelist>
-      <varlistentry>
-       <term><varname>CATALOG_NAME</varname></term>
-
-       <listitem>
-        <para>
-         The program name, as provided in the
-         <function>textdomain()</function> call.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>AVAIL_LANGUAGES</varname></term>
-
-       <listitem>
-        <para>
-         List of provided translations &mdash; initially empty.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>GETTEXT_FILES</varname></term>
-
-       <listitem>
-        <para>
-         List of files that contain translatable strings, i.e., those
-         marked with <function>gettext</function> or an alternative
-         solution.  Eventually, this will include nearly all source
-         files of the program.  If this list gets too long you can
-         make the first <quote>file</quote> be a <literal>+</literal>
-         and the second word be a file that contains one file name per
-         line.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>GETTEXT_TRIGGERS</varname></term>
-
-       <listitem>
-        <para>
-         The tools that generate message catalogs for the translators
-         to work on need to know what function calls contain
-         translatable strings.  By default, only
-         <function>gettext()</function> calls are known.  If you used
-         <function>_</function> or other identifiers you need to list
-         them here.  If the translatable string is not the first
-         argument, the item needs to be of the form
-         <literal>func:2</literal> (for the second argument).
-         If you have a function that supports pluralized messages,
-         the item should look like <literal>func:1,2</literal>
-         (identifying the singular and plural message arguments).
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-   </step>
-
-  </procedure>
-
-  <para>
-   The build system will automatically take care of building and
-   installing the message catalogs.
-  </para>
-  </sect2>
-
-  <sect2 id="nls-guidelines">
-   <title>Message-writing Guidelines</title>
-
-&common;
-  <para>
-   Here are some guidelines for writing messages that are easily
-   translatable.
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Do not construct sentences at run-time, like:
-<programlisting>
-printf("Files were %s.\n", flag ? "copied" : "removed");
-</programlisting>
-      The word order within the sentence might be different in other
-      languages.  Also, even if you remember to call <function>gettext()</> on
-      each fragment, the fragments might not translate well separately.  It's
-      better to duplicate a little code so that each message to be
-      translated is a coherent whole.  Only numbers, file names, and
-      such-like run-time variables should be inserted at run time into
-      a message text.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      For similar reasons, this won't work:
-<programlisting>
-printf("copied %d file%s", n, n!=1 ? "s" : "");
-</programlisting>
-      because it assumes how the plural is formed.  If you figured you
-      could solve it like this:
-<programlisting>
-if (n==1)
-    printf("copied 1 file");
-else
-    printf("copied %d files", n):
-</programlisting>
-      then be disappointed.  Some languages have more than two forms,
-      with some peculiar rules.  It's often best to design the message
-      to avoid the issue altogether, for instance like this:
-<programlisting>
-printf("number of copied files: %d", n);
-</programlisting>
-     </para>
-
-     <para>
-      If you really want to construct a properly pluralized message,
-      there is support for this, but it's a bit awkward.  When generating
-      a primary or detail error message in <function>ereport()</>, you can
-      write something like this:
-<programlisting>
-errmsg_plural("copied %d file",
-              "copied %d files",
-              n,
-              n)
-</programlisting>
-      The first argument is the format string appropriate for English
-      singular form, the second is the format string appropriate for
-      English plural form, and the third is the integer control value
-      that determines which plural form to use.  Subsequent arguments
-      are formatted per the format string as usual.  (Normally, the
-      pluralization control value will also be one of the values to be
-      formatted, so it has to be written twice.)  In English it only
-      matters whether <replaceable>n</> is 1 or not 1, but in other
-      languages there can be many different plural forms.  The translator
-      sees the two English forms as a group and has the opportunity to
-      supply multiple substitute strings, with the appropriate one being
-      selected based on the run-time value of <replaceable>n</>.
-     </para>
-
-     <para>
-      If you need to pluralize a message that isn't going directly to an
-      <function>errmsg</> or <function>errdetail</> report, you have to use
-      the underlying function <function>ngettext</>.  See the gettext
-      documentation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      If you want to communicate something to the translator, such as
-      about how a message is intended to line up with other output,
-      precede the occurrence of the string with a comment that starts
-      with <literal>translator</literal>, e.g.:
-<programlisting>
-/* translator: This message is not what it seems to be. */
-</programlisting>
-      These comments are copied to the message catalog files so that
-      the translators can see them.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-  </sect2>
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/notation.sgmlin b/doc-xc/src/sgml/notation.sgmlin
deleted file mode 100644
index 1b059c552d..0000000000
--- a/doc-xc/src/sgml/notation.sgmlin
+++ /dev/null
@@ -1,114 +0,0 @@
-<!-- doc/src/sgml/notation.sgml -->
-
-<sect1 id="notation">
- <title>Conventions</title>
-&common;
- <para>
-  This book uses the following typographical conventions to mark
-  certain portions of text: new terms, foreign phrases, and other
-  important passages are emphasized in <emphasis>italics</>.
-  Everything that represents input or output of the computer, in
-  particular commands, program code, and screen output, is shown in a
-  monospaced font (<literal>example</literal>).  Within such
-  passages, italics (<replaceable>example</replaceable>) indicate
-  placeholders; you must insert an actual value instead of the placeholder.
-  On occasion, parts of program code are emphasized in bold face
-  (<emphasis role="bold"><literal>example</></>), if they have been
-  added or changed since the preceding example.
- </para>
-
-<!## XC>
- <para>
-  This manual is based upon SGML source file
-  of <productname>PostgreSQL</productname> documentation.
-  Because <productname>Postgres-XC</productname> is an extension
-  to <productname>PostgreSQL</productname>, they share most of the
-  feature.  To specify following sections or paragraphs are common to
-  both, the following notice will be used.
- </para>
-
-&common;
-
- <para>
-  To specify the following sections or paragraphs are specific
-  to <productname>Postgres-XC</productname>, the following notice will
-  be used.
- </para>
-
-&xconly;
-
- <para>
-  If some <productname>PostgreSQL</productname> features are missing
-  or it is not applicable to <productname>Postgres-XC</productname>
-  but important to understand the backgrounds, it will be noticed as
-  follows:
- </para>
-
-&pgonly;
-
-<!## end>
-<!## XL>
- <para>
-  This manual is based upon SGML source file
-  of <productname>PostgreSQL</productname> documentation.
-  Because <productname>Postgres-XL</productname> is an extension
-  to <productname>PostgreSQL</productname>, they share most of the
-  feature.  To specify following sections or paragraphs are common to
-  both, the following notice will be used.
- </para>
-
-&common;
-
- <para>
-  To specify the following sections or paragraphs are specific
-  to <productname>Postgres-XL</productname>, the following notice will
-  be used.
- </para>
-
-&xlonly;
-
- <para>
-  If some <productname>PostgreSQL</productname> features are missing
-  or it is not applicable to <productname>Postgres-XL</productname>
-  but important to understand the background, it will be noticed as
-  follows:
- </para>
-
-&pgonly;
-
-<!## end>
-
- <para>
-  The following conventions are used in the synopsis of a command:
-  brackets (<literal>[</literal> and <literal>]</literal>) indicate
-  optional parts.  (In the synopsis of a Tcl command, question marks
-  (<literal>?</>) are used instead, as is usual in Tcl.)  Braces
-  (<literal>{</literal> and <literal>}</literal>) and vertical lines
-  (<literal>|</literal>) indicate that you must choose one
-  alternative.  Dots (<literal>...</>) mean that the preceding element
-  can be repeated.
- </para>
-
- <para>
-  Where it enhances the clarity, SQL commands are preceded by the
-  prompt <literal>=&gt;</>, and shell commands are preceded by the
-  prompt <literal>$</>.  Normally, prompts are not shown, though.
- </para>
-
- <para>
-  An <firstterm>administrator</firstterm> is generally a person who is
-  in charge of installing and running the server.  A <firstterm>user</firstterm>
-  could be anyone who is using, or wants to use, any part of the
-<!## PG>
-  <productname>PostgreSQL</productname> system.  These terms should not
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> system.  These terms should not
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> system.  These terms should not
-<!## end>
-  be interpreted too narrowly; this book does not have fixed
-  presumptions about system administration procedures.
- </para>
-</sect1>
diff --git a/doc-xc/src/sgml/oid2name.sgmlin b/doc-xc/src/sgml/oid2name.sgmlin
deleted file mode 100644
index a490629663..0000000000
--- a/doc-xc/src/sgml/oid2name.sgmlin
+++ /dev/null
@@ -1,310 +0,0 @@
-<!-- doc/src/sgml/oid2name.sgml -->
-
-<sect1 id="oid2name" xreflabel="oid2name">
- <title>oid2name</title>
-
- <indexterm zone="oid2name">
-  <primary>oid2name</primary>
- </indexterm>
-
-&common;
-
- <para>
-  <application>oid2name</> is a utility program that helps administrators to
-  examine the file structure used by PostgreSQL.  To make use of it, you need
-  to be familiar with the database file structure, which is described in
-  <xref linkend="storage">.
- </para>
-
- <note>
-  <para>
-   The name <quote>oid2name</> is historical, and is actually rather
-   misleading, since most of the time when you use it, you will really
-   be concerned with tables' filenode numbers (which are the file names
-   visible in the database directories).  Be sure you understand the
-   difference between table OIDs and table filenodes!
-  </para>
- </note>
-
-<!## XC>
-&xconly;
-  <para>
-   Please note that you can issue this command to each Datanode or
-   Coordinator.  The result is the information local to Datanode or
-   Coordinator specified.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that you can issue this command to each Datanode or
-   Coordinator.  The result is the information local to Datanode or
-   Coordinator specified.
-  </para>
-<!## end>
-
- <sect2>
-  <title>Overview</title>
-
-&common;
-  <para>
-   <application>oid2name</application> connects to a target database and
-   extracts OID, filenode, and/or table name information.  You can also have
-   it show database OIDs or tablespace OIDs.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title><application>oid2name</> Options</title>
-
-&common;
-  <para>
-   <application>oid2name</application> accepts the following command-line arguments:
-
-   <variablelist>
-
-    <varlistentry>
-     <term><option>-o</option> <replaceable>oid</></term>
-     <listitem><para>show info for table with OID <replaceable>oid</></para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-f</option> <replaceable>filenode</></term>
-     <listitem><para>show info for table with filenode <replaceable>filenode</></para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-t</option> <replaceable>tablename_pattern</></term>
-     <listitem><para>show info for table(s) matching <replaceable>tablename_pattern</></para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-s</option></term>
-     <listitem><para>show tablespace OIDs</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-S</option></term>
-     <listitem><para>include system objects (those in
-      <option>information_schema</option>, <option>pg_toast</option>
-      and <option>pg_catalog</option> schemas)
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-i</option></term>
-     <listitem><para>include indexes and sequences in the listing</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-x</option></term>
-     <listitem><para>display more information about each object shown: tablespace name,
-      schema name, and OID
-     </para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-q</option></term>
-     <listitem><para>omit headers (useful for scripting)</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-d</option> <replaceable>database</></term>
-     <listitem><para>database to connect to</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-H</option> <replaceable>host</></term>
-     <listitem><para>database server's host</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-p</option> <replaceable>port</></term>
-     <listitem><para>database server's port</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-U</option> <replaceable>username</></term>
-     <listitem><para>user name to connect as</para></listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-P</option> <replaceable>password</></term>
-     <listitem><para>password (deprecated &mdash; putting this on the command line
-      is a security hazard)</para></listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-
-  <para>
-   To display specific tables, select which tables to show by
-   using <option>-o</>, <option>-f</> and/or <option>-t</>.
-   <option>-o</> takes an OID,
-   <option>-f</> takes a filenode,
-   and <option>-t</> takes a table name (actually, it's a <literal>LIKE</>
-   pattern, so you can use things like <literal>foo%</>).
-   You can use as many
-   of these options as you like, and the listing will include all objects
-   matched by any of the options.  But note that these options can only
-   show objects in the database given by <option>-d</>.
-  </para>
-
-  <para>
-   If you don't give any of <option>-o</>, <option>-f</> or <option>-t</>,
-   but do give <option>-d</>, it will list all tables in the database
-   named by <option>-d</>.  In this mode, the <option>-S</> and
-   <option>-i</> options control what gets listed.
-  </para>
-
-  <para>
-   If you don't give <option>-d</> either, it will show a listing of database
-   OIDs.  Alternatively you can give <option>-s</> to get a tablespace
-   listing.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Examples</title>
-
-<screen>
-$ # what's in this database server, anyway?
-$ oid2name
-All databases:
-    Oid  Database Name  Tablespace
-----------------------------------
-  17228       alvherre  pg_default
-  17255     regression  pg_default
-  17227      template0  pg_default
-      1      template1  pg_default
-
-$ oid2name -s
-All tablespaces:
-     Oid  Tablespace Name
--------------------------
-    1663       pg_default
-    1664        pg_global
-  155151         fastdisk
-  155152          bigdisk
-
-$ # OK, let's look into database alvherre
-$ cd $PGDATA/base/17228
-
-$ # get top 10 db objects in the default tablespace, ordered by size
-$ ls -lS * | head -10
--rw-------  1 alvherre alvherre 136536064 sep 14 09:51 155173
--rw-------  1 alvherre alvherre  17965056 sep 14 09:51 1155291
--rw-------  1 alvherre alvherre   1204224 sep 14 09:51 16717
--rw-------  1 alvherre alvherre    581632 sep  6 17:51 1255
--rw-------  1 alvherre alvherre    237568 sep 14 09:50 16674
--rw-------  1 alvherre alvherre    212992 sep 14 09:51 1249
--rw-------  1 alvherre alvherre    204800 sep 14 09:51 16684
--rw-------  1 alvherre alvherre    196608 sep 14 09:50 16700
--rw-------  1 alvherre alvherre    163840 sep 14 09:50 16699
--rw-------  1 alvherre alvherre    122880 sep  6 17:51 16751
-
-$ # I wonder what file 155173 is ...
-$ oid2name -d alvherre -f 155173
-From database "alvherre":
-  Filenode  Table Name
-----------------------
-    155173    accounts
-
-$ # you can ask for more than one object
-$ oid2name -d alvherre -f 155173 -f 1155291
-From database "alvherre":
-  Filenode     Table Name
--------------------------
-    155173       accounts
-   1155291  accounts_pkey
-
-$ # you can mix the options, and get more details with -x
-$ oid2name -d alvherre -t accounts -f 1155291 -x
-From database "alvherre":
-  Filenode     Table Name      Oid  Schema  Tablespace
-------------------------------------------------------
-    155173       accounts   155173  public  pg_default
-   1155291  accounts_pkey  1155291  public  pg_default
-
-$ # show disk space for every db object
-$ du [0-9]* |
-> while read SIZE FILENODE
-> do
->   echo "$SIZE       `oid2name -q -d alvherre -i -f $FILENODE`"
-> done
-16            1155287  branches_pkey
-16            1155289  tellers_pkey
-17561            1155291  accounts_pkey
-...
-
-$ # same, but sort by size
-$ du [0-9]* | sort -rn | while read SIZE FN
-> do
->   echo "$SIZE   `oid2name -q -d alvherre -f $FN`"
-> done
-133466             155173    accounts
-17561            1155291  accounts_pkey
-1177              16717  pg_proc_proname_args_nsp_index
-...
-
-$ # If you want to see what's in tablespaces, use the pg_tblspc directory
-$ cd $PGDATA/pg_tblspc
-$ oid2name -s
-All tablespaces:
-     Oid  Tablespace Name
--------------------------
-    1663       pg_default
-    1664        pg_global
-  155151         fastdisk
-  155152          bigdisk
-
-$ # what databases have objects in tablespace "fastdisk"?
-$ ls -d 155151/*
-155151/17228/  155151/PG_VERSION
-
-$ # Oh, what was database 17228 again?
-$ oid2name
-All databases:
-    Oid  Database Name  Tablespace
-----------------------------------
-  17228       alvherre  pg_default
-  17255     regression  pg_default
-  17227      template0  pg_default
-      1      template1  pg_default
-
-$ # Let's see what objects does this database have in the tablespace.
-$ cd 155151/17228
-$ ls -l
-total 0
--rw-------  1 postgres postgres 0 sep 13 23:20 155156
-
-$ # OK, this is a pretty small table ... but which one is it?
-$ oid2name -d alvherre -f 155156
-From database "alvherre":
-  Filenode  Table Name
-----------------------
-    155156         foo
-</screen>
- </sect2>
-
- <sect2>
-  <title>Limitations</title>
-
-&common;
-  <para>
-   <application>oid2name</> requires a running database server with
-   non-corrupt system catalogs.  It is therefore of only limited use
-   for recovering from catastrophic database corruption situations.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   B. Palmer <email>[email protected]</email>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pageinspect.sgmlin b/doc-xc/src/sgml/pageinspect.sgmlin
deleted file mode 100644
index bec79894c6..0000000000
--- a/doc-xc/src/sgml/pageinspect.sgmlin
+++ /dev/null
@@ -1,224 +0,0 @@
-<!-- doc/src/sgml/pageinspect.sgml -->
-
-<sect1 id="pageinspect" xreflabel="pageinspect">
- <title>pageinspect</title>
-
- <indexterm zone="pageinspect">
-  <primary>pageinspect</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>pageinspect</> module provides functions that allow you to
-  inspect the contents of database pages at a low level, which is useful for
-  debugging purposes.  All of these functions may be used only by superusers.
- </para>
-
-<!## XC>
-&xconly; 
- <para>
-  Functions of this module returns information about connecting
-  Coordinators locally.  To get information of a Datanode, you can
-  connect to the Datanode using psql directly.  In this case,
-  statements will be handled by local transaction control without GTM,
-  you will have warnings and the visibility could be somewhat
-  inconsistent.
- </para>
-<!## end>
-<!## XL>
-&xlonly; 
- <para>
-  Functions of this module returns information about connecting
-  Coordinators locally.  To get information of a Datanode, you can
-  use EXECUTE DIRECT from a Coordinator. 
- </para>
-<!## end>
-
- <sect2>
-  <title>Functions</title>
-&common;
-  <variablelist>
-   <varlistentry>
-    <term>
-     <function>get_raw_page(relname text, fork text, blkno int) returns bytea</function>
-    </term>
-
-    <listitem>
-     <para>
-      <function>get_raw_page</function> reads the specified block of the named
-      table and returns a copy as a <type>bytea</> value.  This allows a
-      single time-consistent copy of the block to be obtained.
-      <replaceable>fork</replaceable> should be <literal>'main'</literal> for
-      the main data fork, or <literal>'fsm'</literal> for the free space map,
-      or <literal>'vm'</literal> for the visibility map.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <function>get_raw_page(relname text, blkno int) returns bytea</function>
-    </term>
-
-    <listitem>
-     <para>
-      A shorthand version of <function>get_raw_page</function>, for reading
-      from the main fork.  Equivalent to
-      <literal>get_raw_page(relname, 'main', blkno)</literal>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <function>page_header(page bytea) returns record</function>
-    </term>
-
-    <listitem>
-     <para>
-      <function>page_header</function> shows fields that are common to all
-      <productname>PostgreSQL</> heap and index pages.
-     </para>
-
-     <para>
-      A page image obtained with <function>get_raw_page</function> should be
-      passed as argument.  For example:
-<screen>
-test=# SELECT * FROM page_header(get_raw_page('pg_class', 0));
-    lsn    | tli | flags | lower | upper | special | pagesize | version | prune_xid
------------+-----+-------+-------+-------+---------+----------+---------+-----------
- 0/24A1B50 |   1 |     1 |   232 |   368 |    8192 |     8192 |       4 |         0
-</screen>
-      The returned columns correspond to the fields in the
-      <structname>PageHeaderData</> struct.
-      See <filename>src/include/storage/bufpage.h</> for details.
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <function>heap_page_items(page bytea) returns setof record</function>
-    </term>
-
-    <listitem>
-     <para>
-      <function>heap_page_items</function> shows all line pointers on a heap
-      page.  For those line pointers that are in use, tuple headers are also
-      shown. All tuples are shown, whether or not the tuples were visible to
-      an MVCC snapshot at the time the raw page was copied.
-     </para>
-     <para>
-      A heap page image obtained with <function>get_raw_page</function> should
-      be passed as argument.  For example:
-<screen>
-test=# SELECT * FROM heap_page_items(get_raw_page('pg_class', 0));
-</screen>
-      See <filename>src/include/storage/itemid.h</> and
-      <filename>src/include/access/htup.h</> for explanations of the fields
-      returned.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <function>bt_metap(relname text) returns record</function>
-    </term>
-
-    <listitem>
-     <para>
-      <function>bt_metap</function> returns information about a B-tree
-      index's metapage.  For example:
-<screen>
-test=# SELECT * FROM bt_metap('pg_cast_oid_index');
--[ RECORD 1 ]-----
-magic     | 340322
-version   | 2
-root      | 1
-level     | 0
-fastroot  | 1
-fastlevel | 0
-</screen>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <function>bt_page_stats(relname text, blkno int) returns record</function>
-    </term>
-
-    <listitem>
-     <para>
-      <function>bt_page_stats</function> returns summary information about
-      single pages of B-tree indexes.  For example:
-<screen>
-test=# SELECT * FROM bt_page_stats('pg_cast_oid_index', 1);
--[ RECORD 1 ]-+-----
-blkno         | 1
-type          | l
-live_items    | 256
-dead_items    | 0
-avg_item_size | 12
-page_size     | 8192
-free_size     | 4056
-btpo_prev     | 0
-btpo_next     | 0
-btpo          | 0
-btpo_flags    | 3
-</screen>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <function>bt_page_items(relname text, blkno int) returns setof record</function>
-    </term>
-
-    <listitem>
-     <para>
-      <function>bt_page_items</function> returns detailed information about
-      all of the items on a B-tree index page.  For example:
-<screen>
-test=# SELECT * FROM bt_page_items('pg_cast_oid_index', 1);
- itemoffset |  ctid   | itemlen | nulls | vars |    data
-------------+---------+---------+-------+------+-------------
-          1 | (0,1)   |      12 | f     | f    | 23 27 00 00
-          2 | (0,2)   |      12 | f     | f    | 24 27 00 00
-          3 | (0,3)   |      12 | f     | f    | 25 27 00 00
-          4 | (0,4)   |      12 | f     | f    | 26 27 00 00
-          5 | (0,5)   |      12 | f     | f    | 27 27 00 00
-          6 | (0,6)   |      12 | f     | f    | 28 27 00 00
-          7 | (0,7)   |      12 | f     | f    | 29 27 00 00
-          8 | (0,8)   |      12 | f     | f    | 2a 27 00 00
-</screen>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <function>fsm_page_contents(page bytea) returns text</function>
-    </term>
-
-    <listitem>
-     <para>
-      <function>fsm_page_contents</function> shows the internal node structure
-      of a FSM page. The output is a multiline string, with one line per
-      node in the binary tree within the page. Only those nodes that are not
-      zero are printed. The so-called "next" pointer, which points to the
-      next slot to be returned from the page, is also printed.
-     </para>
-     <para>
-      See <filename>src/backend/storage/freespace/README</> for more
-      information on the structure of an FSM page.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/passwordcheck.sgmlin b/doc-xc/src/sgml/passwordcheck.sgmlin
deleted file mode 100644
index d162c1f6dd..0000000000
--- a/doc-xc/src/sgml/passwordcheck.sgmlin
+++ /dev/null
@@ -1,64 +0,0 @@
-<!-- doc/src/sgml/passwordcheck.sgml -->
-
-<sect1 id="passwordcheck" xreflabel="passwordcheck">
- <title>passwordcheck</title>
-
- <indexterm zone="passwordcheck">
-  <primary>passwordcheck</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>passwordcheck</filename> module checks users' passwords
-  whenever they are set with
-  <xref linkend="SQL-CREATEROLE"> or
-  <xref linkend="SQL-ALTERROLE">.
-  If a password is considered too weak, it will be rejected and
-  the command will terminate with an error.
- </para>
-
- <para>
-  To enable this module, add <literal>'$libdir/passwordcheck'</literal>
-  to <xref linkend="guc-shared-preload-libraries"> in
-  <filename>postgresql.conf</filename>, then restart the server.
- </para>
-
- <para>
-  You can adapt this module to your needs by changing the source code.
-  For example, you can use
-  <ulink url="http://sourceforge.net/projects/cracklib/">CrackLib</ulink>
-  to check passwords &mdash; this only requires uncommenting
-  two lines in the <filename>Makefile</filename> and rebuilding the
-  module.  (We cannot include <productname>CrackLib</productname>
-  by default for license reasons.)
-  Without <productname>CrackLib</productname>, the module enforces a few
-  simple rules for password strength, which you can modify or extend
-  as you see fit.
- </para>
-
- <caution>
-  <para>
-   To prevent unencrypted passwords from being sent across the network,
-   written to the server log or otherwise stolen by a database administrator,
-   <productname>PostgreSQL</productname> allows the user to supply
-   pre-encrypted passwords. Many client programs make use of this
-   functionality and encrypt the password before sending it to the server.
-  </para>
-  <para>
-   This limits the usefulness of the <filename>passwordcheck</filename>
-   module, because in that case it can only try to guess the password.
-   For this reason, <filename>passwordcheck</filename> is not
-   recommendable if your security requirements are high.
-   It is more secure to use an external authentication method such as Kerberos
-   (see <xref linkend="client-authentication">) than to rely on
-   passwords within the database.
-  </para>
-  <para>
-   Alternatively, you could modify <filename>passwordcheck</filename>
-   to reject pre-encrypted passwords, but forcing users to set their
-   passwords in clear text carries its own security risks.
-  </para>
- </caution>
-
-</sect1>
diff --git a/doc-xc/src/sgml/perform.sgmlin b/doc-xc/src/sgml/perform.sgmlin
deleted file mode 100644
index 66b15d8bcb..0000000000
--- a/doc-xc/src/sgml/perform.sgmlin
+++ /dev/null
@@ -1,1382 +0,0 @@
-<!-- doc/src/sgml/perform.sgml -->
-
- <chapter id="performance-tips">
-  <title>Performance Tips</title>
-
-  <indexterm zone="performance-tips">
-   <primary>performance</primary>
-  </indexterm>
-
-<!## PG>
-  <para>
-   Query performance can be affected by many things. Some of these can
-   be controlled by the user, while others are fundamental to the underlying
-   design of the system.  This chapter provides some hints about understanding
-   and tuning <productname>PostgreSQL</productname> performance.
-  </para>
-<!## end>
-<!## XC>
-&xconly;
-  <para>
-   Query performance can be affected by many things. Some of these can
-   be controlled by the user, while others are fundamental to the underlying
-   design of the system.  This chapter's goal is to provide some hints about understanding
-   and tuning <productname>Postgres-XC</productname> performance.
-   Because <productname>Postgres-XC</> performance tuning is now under evaluation
-   and will be supplied in the future.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Query performance can be affected by many things. Some of these can
-   be controlled by the user, while others are fundamental to the underlying
-   design of the system.  This chapter's goal is to provide some hints about understanding
-   and tuning <productname>Postgres-XL</productname> performance.
-  </para>
-<!## end>
-
-  <sect1 id="using-explain">
-   <title>Using <command>EXPLAIN</command></title>
-
-   <indexterm zone="using-explain">
-    <primary>EXPLAIN</primary>
-   </indexterm>
-
-   <indexterm zone="using-explain">
-    <primary>query plan</primary>
-   </indexterm>
-
-<!## XC>
-&xconly;
-   <para>
-    This section will be supplied in the future version.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    <productname>Postgres-XL</productname> specific information will supplied in a future version.
-    For this version we include general <productname>PostgreSQL</productname> information.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</productname> devises a <firstterm>query
-    plan</firstterm> for each query it receives.  Choosing the right
-    plan to match the query structure and the properties of the data
-    is absolutely critical for good performance, so the system includes
-    a complex <firstterm>planner</> that tries to choose good plans.
-    You can use the
-    <xref linkend="sql-explain"> command
-    to see what query plan the planner creates for any query.
-    Plan-reading is an art that deserves an extensive tutorial, which
-    this is not; but here is some basic information.
-   </para>
-
-   <para>
-    The structure of a query plan is a tree of <firstterm>plan nodes</>.
-    Nodes at the bottom level of the tree are table scan nodes: they return raw rows
-    from a table.  There are different types of scan nodes for different
-    table access methods: sequential scans, index scans, and bitmap index
-    scans.  If the query requires joining, aggregation, sorting, or other
-    operations on the raw rows, then there will be additional nodes
-    above the scan nodes to perform these operations.  Again,
-    there is usually more than one possible way to do these operations,
-    so different node types can appear here too.  The output
-    of <command>EXPLAIN</command> has one line for each node in the plan
-    tree, showing the basic node type plus the cost estimates that the planner
-    made for the execution of that plan node.  The first line (topmost node)
-    has the estimated total execution cost for the plan; it is this number
-    that the planner seeks to minimize.
-   </para>
-
-   <para>
-    Here is a trivial example, just to show what the output looks like:
-    <footnote>
-     <para>
-      Examples in this section are drawn from the regression test database
-      after doing a <command>VACUUM ANALYZE</>, using 8.2 development sources.
-      You should be able to get similar results if you try the examples yourself,
-      but your estimated costs and row counts might vary slightly
-      because <command>ANALYZE</>'s statistics are random samples rather
-      than exact.
-     </para>
-    </footnote>
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1;
-
-                         QUERY PLAN
--------------------------------------------------------------
- Seq Scan on tenk1  (cost=0.00..458.00 rows=10000 width=244)
-</programlisting>
-   </para>
-
-   <para>
-    The numbers that are quoted by <command>EXPLAIN</command> are (left
-    to right):
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Estimated start-up cost (time expended before the output scan can start,
-       e.g., time to do the sorting in a sort node)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Estimated total cost (if all rows are retrieved, though they might
-       not be; e.g., a query with a <literal>LIMIT</> clause will stop
-       short of paying the total cost of the <literal>Limit</> plan node's
-       input node)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Estimated number of rows output by this plan node (again, only if
-       executed to completion)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Estimated average width (in bytes) of rows output by this plan
-       node
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    The costs are measured in arbitrary units determined by the planner's
-    cost parameters (see <xref linkend="runtime-config-query-constants">).
-    Traditional practice is to measure the costs in units of disk page
-    fetches; that is, <xref linkend="guc-seq-page-cost"> is conventionally
-    set to <literal>1.0</> and the other cost parameters are set relative
-    to that.  (The examples in this section are run with the default cost
-    parameters.)
-   </para>
-
-   <para>
-    It's important to note that the cost of an upper-level node includes
-    the cost of all its child nodes.  It's also important to realize that
-    the cost only reflects things that the planner cares about.
-    In particular, the cost does not consider the time spent transmitting
-    result rows to the client, which could be an important
-    factor in the real elapsed time; but the planner ignores it because
-    it cannot change it by altering the plan.  (Every correct plan will
-    output the same row set, we trust.)
-   </para>
-
-   <para>
-    The <literal>rows</> value is a little tricky
-    because it is <emphasis>not</emphasis> the
-    number of rows processed or scanned by the plan node.  It is usually less,
-    reflecting the estimated selectivity of any <literal>WHERE</>-clause
-    conditions that are being
-    applied at the node.  Ideally the top-level rows estimate will
-    approximate the number of rows actually returned, updated, or deleted
-    by the query.
-   </para>
-
-   <para>
-    Returning to our example:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1;
-
-                         QUERY PLAN
--------------------------------------------------------------
- Seq Scan on tenk1  (cost=0.00..458.00 rows=10000 width=244)
-</programlisting>
-   </para>
-
-   <para>
-    This is about as straightforward as it gets.  If you do:
-
-<programlisting>
-SELECT relpages, reltuples FROM pg_class WHERE relname = 'tenk1';
-</programlisting>
-
-    you will find that <classname>tenk1</classname> has 358 disk
-    pages and 10000 rows.  The estimated cost is computed as (disk pages read *
-    <xref linkend="guc-seq-page-cost">) + (rows scanned *
-    <xref linkend="guc-cpu-tuple-cost">).  By default,
-    <varname>seq_page_cost</> is 1.0 and <varname>cpu_tuple_cost</> is 0.01,
-    so the estimated cost is (358 * 1.0) + (10000 * 0.01) = 458.
-   </para>
-
-   <para>
-    Now let's modify the original query to add a <literal>WHERE</> condition:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 WHERE unique1 &lt; 7000;
-
-                         QUERY PLAN
-------------------------------------------------------------
- Seq Scan on tenk1  (cost=0.00..483.00 rows=7033 width=244)
-   Filter: (unique1 &lt; 7000)
-</programlisting>
-
-    Notice that the <command>EXPLAIN</> output shows the <literal>WHERE</>
-    clause being applied as a <quote>filter</> condition; this means that
-    the plan node checks the condition for each row it scans, and outputs
-    only the ones that pass the condition.
-    The estimate of output rows has been reduced because of the <literal>WHERE</>
-    clause.
-    However, the scan will still have to visit all 10000 rows, so the cost
-    hasn't decreased; in fact it has gone up a bit (by 10000 * <xref
-    linkend="guc-cpu-operator-cost">, to be exact) to reflect the extra CPU
-    time spent checking the <literal>WHERE</> condition.
-   </para>
-
-   <para>
-    The actual number of rows this query would select is 7000, but the <literal>rows</>
-    estimate is only approximate.  If you try to duplicate this experiment,
-    you will probably get a slightly different estimate; moreover, it will
-    change after each <command>ANALYZE</command> command, because the
-    statistics produced by <command>ANALYZE</command> are taken from a
-    randomized sample of the table.
-   </para>
-
-   <para>
-    Now, let's make the condition more restrictive:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 WHERE unique1 &lt; 100;
-
-                                  QUERY PLAN
-------------------------------------------------------------------------------
- Bitmap Heap Scan on tenk1  (cost=2.37..232.35 rows=106 width=244)
-   Recheck Cond: (unique1 &lt; 100)
-   ->  Bitmap Index Scan on tenk1_unique1  (cost=0.00..2.37 rows=106 width=0)
-         Index Cond: (unique1 &lt; 100)
-</programlisting>
-
-    Here the planner has decided to use a two-step plan: the bottom plan
-    node visits an index to find the locations of rows matching the index
-    condition, and then the upper plan node actually fetches those rows
-    from the table itself.  Fetching the rows separately is much more
-    expensive than sequentially reading them, but because not all the pages
-    of the table have to be visited, this is still cheaper than a sequential
-    scan.  (The reason for using two plan levels is that the upper plan
-    node sorts the row locations identified by the index into physical order
-    before reading them, to minimize the cost of separate fetches.
-    The <quote>bitmap</> mentioned in the node names is the mechanism that
-    does the sorting.)
-   </para>
-
-   <para>
-    If the <literal>WHERE</> condition is selective enough, the planner might
-    switch to a <quote>simple</> index scan plan:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 WHERE unique1 &lt; 3;
-
-                                  QUERY PLAN
-------------------------------------------------------------------------------
- Index Scan using tenk1_unique1 on tenk1  (cost=0.00..10.00 rows=2 width=244)
-   Index Cond: (unique1 &lt; 3)
-</programlisting>
-
-    In this case the table rows are fetched in index order, which makes them
-    even more expensive to read, but there are so few that the extra cost
-    of sorting the row locations is not worth it.  You'll most often see
-    this plan type for queries that fetch just a single row, and for queries
-    that have an <literal>ORDER BY</> condition that matches the index
-    order.
-   </para>
-
-   <para>
-    Add another condition to the <literal>WHERE</> clause:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 WHERE unique1 &lt; 3 AND stringu1 = 'xxx';
-
-                                  QUERY PLAN
-------------------------------------------------------------------------------
- Index Scan using tenk1_unique1 on tenk1  (cost=0.00..10.01 rows=1 width=244)
-   Index Cond: (unique1 &lt; 3)
-   Filter: (stringu1 = 'xxx'::name)
-</programlisting>
-
-    The added condition <literal>stringu1 = 'xxx'</literal> reduces the
-    output-rows estimate, but not the cost because we still have to visit the
-    same set of rows.  Notice that the <literal>stringu1</> clause
-    cannot be applied as an index condition (since this index is only on
-    the <literal>unique1</> column).  Instead it is applied as a filter on
-    the rows retrieved by the index.  Thus the cost has actually gone up
-    slightly to reflect this extra checking.
-   </para>
-
-   <para>
-    If there are indexes on several columns referenced in <literal>WHERE</>, the
-    planner might choose to use an AND or OR combination of the indexes:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 WHERE unique1 &lt; 100 AND unique2 &gt; 9000;
-
-                                     QUERY PLAN
--------------------------------------------------------------------------------------
- Bitmap Heap Scan on tenk1  (cost=11.27..49.11 rows=11 width=244)
-   Recheck Cond: ((unique1 &lt; 100) AND (unique2 &gt; 9000))
-   -&gt;  BitmapAnd  (cost=11.27..11.27 rows=11 width=0)
-         -&gt;  Bitmap Index Scan on tenk1_unique1  (cost=0.00..2.37 rows=106 width=0)
-               Index Cond: (unique1 &lt; 100)
-         -&gt;  Bitmap Index Scan on tenk1_unique2  (cost=0.00..8.65 rows=1042 width=0)
-               Index Cond: (unique2 &gt; 9000)
-</programlisting>
-
-    But this requires visiting both indexes, so it's not necessarily a win
-    compared to using just one index and treating the other condition as
-    a filter.  If you vary the ranges involved you'll see the plan change
-    accordingly.
-   </para>
-
-   <para>
-    Let's try joining two tables, using the columns we have been discussing:
-
-<programlisting>
-EXPLAIN SELECT *
-FROM tenk1 t1, tenk2 t2
-WHERE t1.unique1 &lt; 100 AND t1.unique2 = t2.unique2;
-
-                                      QUERY PLAN
---------------------------------------------------------------------------------------
- Nested Loop  (cost=2.37..553.11 rows=106 width=488)
-   -&gt;  Bitmap Heap Scan on tenk1 t1  (cost=2.37..232.35 rows=106 width=244)
-         Recheck Cond: (unique1 &lt; 100)
-         -&gt;  Bitmap Index Scan on tenk1_unique1  (cost=0.00..2.37 rows=106 width=0)
-               Index Cond: (unique1 &lt; 100)
-   -&gt;  Index Scan using tenk2_unique2 on tenk2 t2  (cost=0.00..3.01 rows=1 width=244)
-         Index Cond: (unique2 = t1.unique2)
-</programlisting>
-   </para>
-
-   <para>
-    In this nested-loop join, the outer (upper) scan is the same bitmap index scan we
-    saw earlier, and so its cost and row count are the same because we are
-    applying the <literal>WHERE</> clause <literal>unique1 &lt; 100</literal>
-    at that node.
-    The <literal>t1.unique2 = t2.unique2</literal> clause is not relevant yet,
-    so it doesn't affect the row count of the outer scan.  For the inner (lower) scan, the
-    <literal>unique2</> value of the current outer-scan row is plugged into
-    the inner index scan to produce an index condition like
-    <literal>unique2 = <replaceable>constant</replaceable></literal>.
-    So we get the same inner-scan plan and costs that we'd get from, say,
-    <literal>EXPLAIN SELECT * FROM tenk2 WHERE unique2 = 42</literal>.  The
-    costs of the loop node are then set on the basis of the cost of the outer
-    scan, plus one repetition of the inner scan for each outer row (106 * 3.01,
-    here), plus a little CPU time for join processing.
-   </para>
-
-   <para>
-    In this example the join's output row count is the same as the product
-    of the two scans' row counts, but that's not true in all cases because
-    you can have <literal>WHERE</> clauses that mention both tables
-    and so can only be applied at the join point, not to either input scan.
-    For example, if we added
-    <literal>WHERE ... AND t1.hundred &lt; t2.hundred</literal>,
-    that would decrease the output row count of the join node, but not change
-    either input scan.
-   </para>
-
-   <para>
-    One way to look at variant plans is to force the planner to disregard
-    whatever strategy it thought was the cheapest, using the enable/disable
-    flags described in <xref linkend="runtime-config-query-enable">.
-    (This is a crude tool, but useful.  See
-    also <xref linkend="explicit-joins">.)
-
-<programlisting>
-SET enable_nestloop = off;
-EXPLAIN SELECT *
-FROM tenk1 t1, tenk2 t2
-WHERE t1.unique1 &lt; 100 AND t1.unique2 = t2.unique2;
-
-                                        QUERY PLAN
-------------------------------------------------------------------------------------------
- Hash Join  (cost=232.61..741.67 rows=106 width=488)
-   Hash Cond: (t2.unique2 = t1.unique2)
-   -&gt;  Seq Scan on tenk2 t2  (cost=0.00..458.00 rows=10000 width=244)
-   -&gt;  Hash  (cost=232.35..232.35 rows=106 width=244)
-         -&gt;  Bitmap Heap Scan on tenk1 t1  (cost=2.37..232.35 rows=106 width=244)
-               Recheck Cond: (unique1 &lt; 100)
-               -&gt;  Bitmap Index Scan on tenk1_unique1  (cost=0.00..2.37 rows=106 width=0)
-                     Index Cond: (unique1 &lt; 100)
-</programlisting>
-
-    This plan proposes to extract the 100 interesting rows of <classname>tenk1</classname>
-    using that same old index scan, stash them into an in-memory hash table,
-    and then do a sequential scan of <classname>tenk2</classname>, probing into the hash table
-    for possible matches of <literal>t1.unique2 = t2.unique2</literal> for each <classname>tenk2</classname> row.
-    The cost to read <classname>tenk1</classname> and set up the hash table is a start-up
-    cost for the hash join, since there will be no output until we can
-    start reading <classname>tenk2</classname>.  The total time estimate for the join also
-    includes a hefty charge for the CPU time to probe the hash table
-    10000 times.  Note, however, that we are <emphasis>not</emphasis> charging 10000 times 232.35;
-    the hash table setup is only done once in this plan type.
-   </para>
-
-   <para>
-    It is possible to check the accuracy of the planner's estimated costs
-    by using <command>EXPLAIN ANALYZE</>.  This command actually executes the query,
-    and then displays the true run time accumulated within each plan node
-    along with the same estimated costs that a plain <command>EXPLAIN</command> shows.
-    For example, we might get a result like this:
-
-<screen>
-EXPLAIN ANALYZE SELECT *
-FROM tenk1 t1, tenk2 t2
-WHERE t1.unique1 &lt; 100 AND t1.unique2 = t2.unique2;
-
-                                                            QUERY PLAN
-----------------------------------------------------------------------------------------------------------------------------------
- Nested Loop  (cost=2.37..553.11 rows=106 width=488) (actual time=1.392..12.700 rows=100 loops=1)
-   -&gt;  Bitmap Heap Scan on tenk1 t1  (cost=2.37..232.35 rows=106 width=244) (actual time=0.878..2.367 rows=100 loops=1)
-         Recheck Cond: (unique1 &lt; 100)
-         -&gt;  Bitmap Index Scan on tenk1_unique1  (cost=0.00..2.37 rows=106 width=0) (actual time=0.546..0.546 rows=100 loops=1)
-               Index Cond: (unique1 &lt; 100)
-   -&gt;  Index Scan using tenk2_unique2 on tenk2 t2  (cost=0.00..3.01 rows=1 width=244) (actual time=0.067..0.078 rows=1 loops=100)
-         Index Cond: (unique2 = t1.unique2)
- Total runtime: 14.452 ms
-</screen>
-
-    Note that the <quote>actual time</quote> values are in milliseconds of
-    real time, whereas the <literal>cost</> estimates are expressed in
-    arbitrary units; so they are unlikely to match up.
-    The thing to pay attention to is whether the ratios of actual time and
-    estimated costs are consistent.
-   </para>
-
-   <para>
-    In some query plans, it is possible for a subplan node to be executed more
-    than once.  For example, the inner index scan is executed once per outer
-    row in the above nested-loop plan.  In such cases, the
-    <literal>loops</> value reports the
-    total number of executions of the node, and the actual time and rows
-    values shown are averages per-execution.  This is done to make the numbers
-    comparable with the way that the cost estimates are shown.  Multiply by
-    the <literal>loops</> value to get the total time actually spent in
-    the node.
-   </para>
-
-   <para>
-    The <literal>Total runtime</literal> shown by <command>EXPLAIN
-    ANALYZE</command> includes executor start-up and shut-down time, but not
-    parsing, rewriting, or planning time.  For <command>INSERT</>,
-    <command>UPDATE</>, and <command>DELETE</> commands, the time spent
-    applying the table changes is charged to a top-level Insert, Update,
-    or Delete plan node.  (The plan nodes underneath this node represent
-    the work of locating the old rows and/or computing the new ones.)
-    Time spent executing <literal>BEFORE</> triggers, if any, is charged to
-    the related Insert, Update, or Delete node, although time spent executing
-    <literal>AFTER</> triggers is not.  The time spent in each trigger
-    (either <literal>BEFORE</> or <literal>AFTER</>) is also shown separately
-    and is included in total run time.
-    Note, however, that deferred constraint triggers will not be executed
-    until end of transaction and are thus not shown by
-    <command>EXPLAIN ANALYZE</command>.
-   </para>
-
-   <para>
-    There are two significant ways in which run times measured by
-    <command>EXPLAIN ANALYZE</command> can deviate from normal execution of
-    the same query.  First, since no output rows are delivered to the client,
-    network transmission costs and I/O formatting costs are not included.
-    Second, the overhead added by <command>EXPLAIN ANALYZE</command> can be
-    significant, especially on machines with slow <function>gettimeofday()</>
-    kernel calls.
-   </para>
-
-   <para>
-    It is worth noting that <command>EXPLAIN</> results should not be extrapolated
-    to situations other than the one you are actually testing; for example,
-    results on a toy-sized table cannot be assumed to apply to large tables.
-    The planner's cost estimates are not linear and so it might choose
-    a different plan for a larger or smaller table.  An extreme example
-    is that on a table that only occupies one disk page, you'll nearly
-    always get a sequential scan plan whether indexes are available or not.
-    The planner realizes that it's going to take one disk page read to
-    process the table in any case, so there's no value in expending additional
-    page reads to look at an index.
-   </para>
-
-  </sect1>
-
- <sect1 id="planner-stats">
-  <title>Statistics Used by the Planner</title>
-
-  <indexterm zone="planner-stats">
-   <primary>statistics</primary>
-   <secondary>of the planner</secondary>
-  </indexterm>
-
-<!## XC>
-&xconly;
-  <para>
-   This section will be supplied in the future version.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-    <productname>Postgres-XL</productname> pulls up statistics 
-   from the Datanodes and stores it in each of the Coordinator's catalog
-   table to help make query planning decisions.
-  </para>
-  <para>
-   Traditional PostgreSQL costing applies, but <productname>Postgres-XL</productname>
-   also tries to take into consideration the cost of shipping rows around the
-   network for internode joins, which is an expensive operation.
-   Below general PostgreSQL handling is described.
-  </para>
-<!## end>
-  <para>
-   As we saw in the previous section, the query planner needs to estimate
-   the number of rows retrieved by a query in order to make good choices
-   of query plans.  This section provides a quick look at the statistics
-   that the system uses for these estimates.
-  </para>
-
-  <para>
-   One component of the statistics is the total number of entries in
-   each table and index, as well as the number of disk blocks occupied
-   by each table and index.  This information is kept in the table
-   <link linkend="catalog-pg-class"><structname>pg_class</structname></link>,
-   in the columns <structfield>reltuples</structfield> and
-   <structfield>relpages</structfield>.  We can look at it with
-   queries similar to this one:
-
-<screen>
-SELECT relname, relkind, reltuples, relpages
-FROM pg_class
-WHERE relname LIKE 'tenk1%';
-
-       relname        | relkind | reltuples | relpages
-----------------------+---------+-----------+----------
- tenk1                | r       |     10000 |      358
- tenk1_hundred        | i       |     10000 |       30
- tenk1_thous_tenthous | i       |     10000 |       30
- tenk1_unique1        | i       |     10000 |       30
- tenk1_unique2        | i       |     10000 |       30
-(5 rows)
-</screen>
-
-   Here we can see that <structname>tenk1</structname> contains 10000
-   rows, as do its indexes, but the indexes are (unsurprisingly) much
-   smaller than the table.
-  </para>
-
-  <para>
-   For efficiency reasons, <structfield>reltuples</structfield>
-   and <structfield>relpages</structfield> are not updated on-the-fly,
-   and so they usually contain somewhat out-of-date values.
-   They are updated by <command>VACUUM</>, <command>ANALYZE</>, and a
-   few DDL commands such as <command>CREATE INDEX</>.  A stand-alone
-   <command>ANALYZE</>, that is one not part of <command>VACUUM</>,
-   generates an approximate <structfield>reltuples</structfield> value
-   since it does not read every row of the table.  The planner
-   will scale the values it finds in <structname>pg_class</structname>
-   to match the current physical table size, thus obtaining a closer
-   approximation.
-  </para>
-
-  <indexterm>
-   <primary>pg_statistic</primary>
-  </indexterm>
-
-  <para>
-   Most queries retrieve only a fraction of the rows in a table, due
-   to <literal>WHERE</> clauses that restrict the rows to be
-   examined.  The planner thus needs to make an estimate of the
-   <firstterm>selectivity</> of <literal>WHERE</> clauses, that is,
-   the fraction of rows that match each condition in the
-   <literal>WHERE</> clause.  The information used for this task is
-   stored in the
-   <link linkend="catalog-pg-statistic"><structname>pg_statistic</structname></link>
-   system catalog.  Entries in <structname>pg_statistic</structname>
-   are updated by the <command>ANALYZE</> and <command>VACUUM
-   ANALYZE</> commands, and are always approximate even when freshly
-   updated.
-  </para>
-
-  <indexterm>
-   <primary>pg_stats</primary>
-  </indexterm>
-
-  <para>
-   Rather than look at <structname>pg_statistic</structname> directly,
-   it's better to look at its view
-   <link linkend="view-pg-stats"><structname>pg_stats</structname></link>
-   when examining the statistics manually.  <structname>pg_stats</structname>
-   is designed to be more easily readable.  Furthermore,
-   <structname>pg_stats</structname> is readable by all, whereas
-   <structname>pg_statistic</structname> is only readable by a superuser.
-   (This prevents unprivileged users from learning something about
-   the contents of other people's tables from the statistics.  The
-   <structname>pg_stats</structname> view is restricted to show only
-   rows about tables that the current user can read.)
-   For example, we might do:
-
-<screen>
-SELECT attname, inherited, n_distinct,
-       array_to_string(most_common_vals, E'\n') as most_common_vals
-FROM pg_stats
-WHERE tablename = 'road';
-
- attname | inherited | n_distinct |          most_common_vals          
----------+-----------+------------+------------------------------------
- name    | f         |  -0.363388 | I- 580                        Ramp+
-         |           |            | I- 880                        Ramp+
-         |           |            | Sp Railroad                       +
-         |           |            | I- 580                            +
-         |           |            | I- 680                        Ramp
- name    | t         |  -0.284859 | I- 880                        Ramp+
-         |           |            | I- 580                        Ramp+
-         |           |            | I- 680                        Ramp+
-         |           |            | I- 580                            +
-         |           |            | State Hwy 13                  Ramp
-(2 rows)
-</screen>
-
-   Note that two rows are displayed for the same column, one corresponding
-   to the complete inheritance hierarchy starting at the
-   <literal>road</literal> table (<literal>inherited</>=<literal>t</>),
-   and another one including only the <literal>road</literal> table itself
-   (<literal>inherited</>=<literal>f</>).
-  </para>
-
-  <para>
-   The amount of information stored in <structname>pg_statistic</structname>
-   by <command>ANALYZE</>, in particular the maximum number of entries in the
-   <structfield>most_common_vals</> and <structfield>histogram_bounds</>
-   arrays for each column, can be set on a
-   column-by-column basis using the <command>ALTER TABLE SET STATISTICS</>
-   command, or globally by setting the
-   <xref linkend="guc-default-statistics-target"> configuration variable.
-   The default limit is presently 100 entries.  Raising the limit
-   might allow more accurate planner estimates to be made, particularly for
-   columns with irregular data distributions, at the price of consuming
-   more space in <structname>pg_statistic</structname> and slightly more
-   time to compute the estimates.  Conversely, a lower limit might be
-   sufficient for columns with simple data distributions.
-  </para>
-
-  <para>
-   Further details about the planner's use of statistics can be found in
-   <xref linkend="planner-stats-details">.
-  </para>
-
- </sect1>
-
- <sect1 id="explicit-joins">
-  <title>Controlling the Planner with Explicit <literal>JOIN</> Clauses</title>
-
-  <indexterm zone="explicit-joins">
-   <primary>join</primary>
-   <secondary>controlling the order</secondary>
-  </indexterm>
-&common;
-  <para>
-   It is possible
-   to control the query planner to some extent by using the explicit <literal>JOIN</>
-   syntax.  To see why this matters, we first need some background.
-  </para>
-
-  <para>
-   In a simple join query, such as:
-<programlisting>
-SELECT * FROM a, b, c WHERE a.id = b.id AND b.ref = c.id;
-</programlisting>
-   the planner is free to join the given tables in any order.  For
-   example, it could generate a query plan that joins A to B, using
-   the <literal>WHERE</> condition <literal>a.id = b.id</>, and then
-   joins C to this joined table, using the other <literal>WHERE</>
-   condition.  Or it could join B to C and then join A to that result.
-   Or it could join A to C and then join them with B &mdash; but that
-   would be inefficient, since the full Cartesian product of A and C
-   would have to be formed, there being no applicable condition in the
-   <literal>WHERE</> clause to allow optimization of the join.  (All
-<!## PG>
-   joins in the <productname>PostgreSQL</productname> executor happen
-<!## end>
-<!## XC>
-   joins in the <productname>Postgres-XC</productname> executor happen
-<!## end>
-<!## XL>
-   joins in the <productname>Postgres-XL</productname> executor happen
-<!## end>
-   between two input tables, so it's necessary to build up the result
-   in one or another of these fashions.)  The important point is that
-   these different join possibilities give semantically equivalent
-   results but might have hugely different execution costs.  Therefore,
-   the planner will explore all of them to try to find the most
-   efficient query plan.
-  </para>
-<!## XC>
-  <para>
-   <productname>Postgres-XC</> stores table data in a distributed or
-   replicated fashion.  To leverage this, the planner tries to find
-   the best way to use as much of Datanode power as possible.  If the
-   equi-join is done by distribution columns and they share the
-   distribution method (hash/modulo), the Coordinator can tell
-   Datanode to perform join.  If not, the Coordinator collects rows to
-   join from Datanodes and perform the join locally.  In this case,
-   the Coordinator tries to push other predicate as much as possible
-   to the Datanode to reduce the amount of rows to receive.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   <productname>Postgres-XL</> stores table data in a distributed or
-   replicated fashion.  To leverage this, the planner tries to find
-   the best way to use as much of Datanode power as possible.  If the
-   equi-join is done by distribution columns and they share the
-   distribution method (hash/modulo), the Coordinator can tell
-   the Datanode to perform join.  
-   If not, it may tell Datanodes to ship rows to other Datanodes
-   and expect rows from other Datanodes to be shipped to it.
-  </para>
-<!## end>
-&common;
-  <para>
-   When a query only involves two or three tables, there aren't many join
-   orders to worry about.  But the number of possible join orders grows
-   exponentially as the number of tables expands.  Beyond ten or so input
-   tables it's no longer practical to do an exhaustive search of all the
-   possibilities, and even for six or seven tables planning might take an
-   annoyingly long time.  When there are too many input tables, the
-<!## PG>
-   <productname>PostgreSQL</productname> planner will switch from exhaustive
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> planner will switch from exhaustive
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> planner will switch from exhaustive
-<!## end>
-   search to a <firstterm>genetic</firstterm> probabilistic search
-   through a limited number of possibilities.  (The switch-over threshold is
-   set by the <xref linkend="guc-geqo-threshold"> run-time
-   parameter.)
-   The genetic search takes less time, but it won't
-   necessarily find the best possible plan.
-  </para>
-
-  <para>
-   When the query involves outer joins, the planner has less freedom
-   than it does for plain (inner) joins. For example, consider:
-<programlisting>
-SELECT * FROM a LEFT JOIN (b JOIN c ON (b.ref = c.id)) ON (a.id = b.id);
-</programlisting>
-   Although this query's restrictions are superficially similar to the
-   previous example, the semantics are different because a row must be
-   emitted for each row of A that has no matching row in the join of B and C.
-   Therefore the planner has no choice of join order here: it must join
-   B to C and then join A to that result.  Accordingly, this query takes
-   less time to plan than the previous query.  In other cases, the planner
-   might be able to determine that more than one join order is safe.
-   For example, given:
-<programlisting>
-SELECT * FROM a LEFT JOIN b ON (a.bid = b.id) LEFT JOIN c ON (a.cid = c.id);
-</programlisting>
-   it is valid to join A to either B or C first.  Currently, only
-   <literal>FULL JOIN</> completely constrains the join order.  Most
-   practical cases involving <literal>LEFT JOIN</> or <literal>RIGHT JOIN</>
-   can be rearranged to some extent.
-  </para>
-
-  <para>
-   Explicit inner join syntax (<literal>INNER JOIN</>, <literal>CROSS
-   JOIN</>, or unadorned <literal>JOIN</>) is semantically the same as
-   listing the input relations in <literal>FROM</>, so it does not
-   constrain the join order.
-  </para>
-
-  <para>
-   Even though most kinds of <literal>JOIN</> don't completely constrain
-   the join order, it is possible to instruct the
-<!## PG>
-   <productname>PostgreSQL</productname> query planner to treat all
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> query planner to treat all
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> query planner to treat all
-<!## end>
-   <literal>JOIN</> clauses as constraining the join order anyway.
-   For example, these three queries are logically equivalent:
-<programlisting>
-SELECT * FROM a, b, c WHERE a.id = b.id AND b.ref = c.id;
-SELECT * FROM a CROSS JOIN b CROSS JOIN c WHERE a.id = b.id AND b.ref = c.id;
-SELECT * FROM a JOIN (b JOIN c ON (b.ref = c.id)) ON (a.id = b.id);
-</programlisting>
-   But if we tell the planner to honor the <literal>JOIN</> order,
-   the second and third take less time to plan than the first.  This effect
-   is not worth worrying about for only three tables, but it can be a
-   lifesaver with many tables.
-  </para>
-
-  <para>
-   To force the planner to follow the join order laid out by explicit
-   <literal>JOIN</>s,
-   set the <xref linkend="guc-join-collapse-limit"> run-time parameter to 1.
-   (Other possible values are discussed below.)
-  </para>
-
-  <para>
-   You do not need to constrain the join order completely in order to
-   cut search time, because it's OK to use <literal>JOIN</> operators
-   within items of a plain <literal>FROM</> list.  For example, consider:
-<programlisting>
-SELECT * FROM a CROSS JOIN b, c, d, e WHERE ...;
-</programlisting>
-   With <varname>join_collapse_limit</> = 1, this
-   forces the planner to join A to B before joining them to other tables,
-   but doesn't constrain its choices otherwise.  In this example, the
-   number of possible join orders is reduced by a factor of 5.
-  </para>
-
-  <para>
-   Constraining the planner's search in this way is a useful technique
-   both for reducing planning time and for directing the planner to a
-   good query plan.  If the planner chooses a bad join order by default,
-   you can force it to choose a better order via <literal>JOIN</> syntax
-   &mdash; assuming that you know of a better order, that is.  Experimentation
-   is recommended.
-  </para>
-
-  <para>
-   A closely related issue that affects planning time is collapsing of
-   subqueries into their parent query.  For example, consider:
-<programlisting>
-SELECT *
-FROM x, y,
-    (SELECT * FROM a, b, c WHERE something) AS ss
-WHERE somethingelse;
-</programlisting>
-   This situation might arise from use of a view that contains a join;
-   the view's <literal>SELECT</> rule will be inserted in place of the view
-   reference, yielding a query much like the above.  Normally, the planner
-   will try to collapse the subquery into the parent, yielding:
-<programlisting>
-SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
-</programlisting>
-   This usually results in a better plan than planning the subquery
-   separately.  (For example, the outer <literal>WHERE</> conditions might be such that
-   joining X to A first eliminates many rows of A, thus avoiding the need to
-   form the full logical output of the subquery.)  But at the same time,
-   we have increased the planning time; here, we have a five-way join
-   problem replacing two separate three-way join problems.  Because of the
-   exponential growth of the number of possibilities, this makes a big
-   difference.  The planner tries to avoid getting stuck in huge join search
-   problems by not collapsing a subquery if more than <varname>from_collapse_limit</>
-   <literal>FROM</> items would result in the parent
-   query.  You can trade off planning time against quality of plan by
-   adjusting this run-time parameter up or down.
-  </para>
-
-  <para>
-   <xref linkend="guc-from-collapse-limit"> and <xref
-   linkend="guc-join-collapse-limit">
-   are similarly named because they do almost the same thing: one controls
-   when the planner will <quote>flatten out</> subqueries, and the
-   other controls when it will flatten out explicit joins.  Typically
-   you would either set <varname>join_collapse_limit</> equal to
-   <varname>from_collapse_limit</> (so that explicit joins and subqueries
-   act similarly) or set <varname>join_collapse_limit</> to 1 (if you want
-   to control join order with explicit joins).  But you might set them
-   differently if you are trying to fine-tune the trade-off between planning
-   time and run time.
-  </para>
- </sect1>
-
- <sect1 id="populate">
-  <title>Populating a Database</title>
-&common;
-  <para>
-   One might need to insert a large amount of data when first populating
-   a database. This section contains some suggestions on how to make
-   this process as efficient as possible.
-  </para>
-
-  <sect2 id="disable-autocommit">
-   <title>Disable Autocommit</title>
-
-   <indexterm>
-    <primary>autocommit</primary>
-    <secondary>bulk-loading data</secondary>
-   </indexterm>
-
-   <para>
-    When using multiple <command>INSERT</>s, turn off autocommit and just do
-    one commit at the end.  (In plain
-    SQL, this means issuing <command>BEGIN</command> at the start and
-    <command>COMMIT</command> at the end.  Some client libraries might
-    do this behind your back, in which case you need to make sure the
-    library does it when you want it done.)  If you allow each
-    insertion to be committed separately,
-<!## PG>
-    <productname>PostgreSQL</productname> is doing a lot of work for
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> is doing a lot of work for
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> is doing a lot of work for
-<!## end>
-    each row that is added.  An additional benefit of doing all
-    insertions in one transaction is that if the insertion of one row
-    were to fail then the insertion of all rows inserted up to that
-    point would be rolled back, so you won't be stuck with partially
-    loaded data.
-   </para>
-  </sect2>
-
-  <sect2 id="populate-copy-from">
-   <title>Use <command>COPY</command></title>
-&common;
-   <para>
-    Use <xref linkend="sql-copy"> to load
-    all the rows in one command, instead of using a series of
-    <command>INSERT</command> commands.  The <command>COPY</command>
-    command is optimized for loading large numbers of rows; it is less
-    flexible than <command>INSERT</command>, but incurs significantly
-    less overhead for large data loads. Since <command>COPY</command>
-    is a single command, there is no need to disable autocommit if you
-    use this method to populate a table.
-   </para>
-
-   <para>
-    If you cannot use <command>COPY</command>, it might help to use <xref
-    linkend="sql-prepare"> to create a
-    prepared <command>INSERT</command> statement, and then use
-    <command>EXECUTE</command> as many times as required.  This avoids
-    some of the overhead of repeatedly parsing and planning
-    <command>INSERT</command>. Different interfaces provide this facility
-    in different ways; look for <quote>prepared statements</> in the interface
-    documentation.
-   </para>
-
-   <para>
-    Note that loading a large number of rows using
-    <command>COPY</command> is almost always faster than using
-    <command>INSERT</command>, even if <command>PREPARE</> is used and
-    multiple insertions are batched into a single transaction.
-   </para>
-
-   <para>
-    <command>COPY</command> is fastest when used within the same
-    transaction as an earlier <command>CREATE TABLE</command> or
-    <command>TRUNCATE</command> command. In such cases no WAL
-    needs to be written, because in case of an error, the files
-    containing the newly loaded data will be removed anyway.
-    However, this consideration only applies when
-    <xref linkend="guc-wal-level"> is <literal>minimal</> as all commands
-    must write WAL otherwise.
-   </para>
-
-  </sect2>
-
-  <sect2 id="populate-rm-indexes">
-   <title>Remove Indexes</title>
-
-&common;
-   <para>
-    If you are loading a freshly created table, the fastest method is to
-    create the table, bulk load the table's data using
-    <command>COPY</command>, then create any indexes needed for the
-    table.  Creating an index on pre-existing data is quicker than
-    updating it incrementally as each row is loaded.
-   </para>
-
-   <para>
-    If you are adding large amounts of data to an existing table,
-    it might be a win to drop the indexes,
-    load the table, and then recreate the indexes.  Of course, the
-    database performance for other users might suffer
-    during the time the indexes are missing.  One should also think
-    twice before dropping a unique index, since the error checking
-    afforded by the unique constraint will be lost while the index is
-    missing.
-   </para>
-  </sect2>
-
-  <sect2 id="populate-rm-fkeys">
-   <title>Remove Foreign Key Constraints</title>
-
-&common;
-   <para>
-    Just as with indexes, a foreign key constraint can be checked
-    <quote>in bulk</> more efficiently than row-by-row.  So it might be
-    useful to drop foreign key constraints, load data, and re-create
-    the constraints.  Again, there is a trade-off between data load
-    speed and loss of error checking while the constraint is missing.
-   </para>
-
-   <para>
-    What's more, when you load data into a table with existing foreign key
-    constraints, each new row requires an entry in the server's list of
-    pending trigger events (since it is the firing of a trigger that checks
-    the row's foreign key constraint).  Loading many millions of rows can
-    cause the trigger event queue to overflow available memory, leading to
-    intolerable swapping or even outright failure of the command.  Therefore
-    it may be <emphasis>necessary</>, not just desirable, to drop and re-apply
-    foreign keys when loading large amounts of data.  If temporarily removing
-    the constraint isn't acceptable, the only other recourse may be to split
-    up the load operation into smaller transactions.
-   </para>
-  </sect2>
-
-  <sect2 id="populate-work-mem">
-   <title>Increase <varname>maintenance_work_mem</varname></title>
-
-&common;
-   <para>
-    Temporarily increasing the <xref linkend="guc-maintenance-work-mem">
-    configuration variable when loading large amounts of data can
-    lead to improved performance.  This will help to speed up <command>CREATE
-    INDEX</> commands and <command>ALTER TABLE ADD FOREIGN KEY</> commands.
-    It won't do much for <command>COPY</> itself, so this advice is
-    only useful when you are using one or both of the above techniques.
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    In <productname>Postgres-XC</>, only the distribution column can have foreign key
-    constraint.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    In <productname>Postgres-XL</>, only the distribution column can have foreign key
-    constraint.
-   </para>
-<!## end>
-  </sect2>
-
-  <sect2 id="populate-checkpoint-segments">
-   <title>Increase <varname>checkpoint_segments</varname></title>
-
-&common;
-   <para>
-    Temporarily increasing the <xref
-    linkend="guc-checkpoint-segments"> configuration variable can also
-    make large data loads faster.  This is because loading a large
-<!## PG>
-    amount of data into <productname>PostgreSQL</productname> will
-<!## end>
-<!## XC>
-    amount of data into <productname>Postgres-XC</productname> will
-<!## end>
-<!## XL>
-    amount of data into <productname>Postgres-XL</productname> will
-<!## end>
-    cause checkpoints to occur more often than the normal checkpoint
-    frequency (specified by the <varname>checkpoint_timeout</varname>
-    configuration variable). Whenever a checkpoint occurs, all dirty
-    pages must be flushed to disk. By increasing
-    <varname>checkpoint_segments</varname> temporarily during bulk
-    data loads, the number of checkpoints that are required can be
-    reduced.
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    Please note that you should tune the configuration variables in
-    all the nodes involved.  Maybe you need to tune this just for
-    Datanodes.  Coordinator's database will be updated almost only
-    by <acronym>DDL</>s.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    Please note that you should tune the configuration variables in
-    all the nodes involved.  Keep in mind that the Datanodes
-    are more important and will need more resources than Coordinators.
-    by <acronym>DDL</>s.
-   </para>
-<!## end>
-  </sect2>
-
-  <sect2 id="populate-pitr">
-   <title>Disable WAL Archival and Streaming Replication</title>
-
-<!## XC>
-&xconly;
-   <para>
-    Use of streaming replication will be added in the future release of <productname>Postgres-XC</>;
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-   </para>
-<!## end>
-<!## PG>
-   <para>
-    When loading large amounts of data into an installation that uses
-    WAL archiving or streaming replication, it might be faster to take a
-    new base backup after the load has completed than to process a large
-    amount of incremental WAL data.  To prevent incremental WAL logging
-    while loading, disable archiving and streaming replication, by setting
-    <xref linkend="guc-wal-level"> to <literal>minimal</>,
-    <xref linkend="guc-archive-mode"> to <literal>off</>, and
-    <xref linkend="guc-max-wal-senders"> to zero.
-    But note that changing these settings requires a server restart.
-   </para>
-
-   <para>
-    Aside from avoiding the time for the archiver or WAL sender to
-    process the WAL data,
-    doing this will actually make certain commands faster, because they
-    are designed not to write WAL at all if <varname>wal_level</varname>
-    is <literal>minimal</>.  (They can guarantee crash safety more cheaply
-    by doing an <function>fsync</> at the end than by writing WAL.)
-    This applies to the following commands:
-    <itemizedlist>
-     <listitem>
-      <para>
-       <command>CREATE TABLE AS SELECT</command>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <command>CREATE INDEX</command> (and variants such as
-       <command>ALTER TABLE ADD PRIMARY KEY</command>)
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <command>ALTER TABLE SET TABLESPACE</command>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <command>CLUSTER</command>
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <command>COPY FROM</command>, when the target table has been
-       created or truncated earlier in the same transaction
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-<!## end>
-
-  </sect2>
-
-  <sect2 id="populate-analyze">
-   <title>Run <command>ANALYZE</command> Afterwards</title>
-&common;
-   <para>
-    Whenever you have significantly altered the distribution of data
-    within a table, running <xref linkend="sql-analyze"> is strongly recommended. This
-    includes bulk loading large amounts of data into the table.  Running
-    <command>ANALYZE</command> (or <command>VACUUM ANALYZE</command>)
-    ensures that the planner has up-to-date statistics about the
-    table.  With no statistics or obsolete statistics, the planner might
-    make poor decisions during query planning, leading to poor
-    performance on any tables with inaccurate or nonexistent
-    statistics.  Note that if the autovacuum daemon is enabled, it might
-    run <command>ANALYZE</command> automatically; see
-    <xref linkend="vacuum-for-statistics">
-    and <xref linkend="autovacuum"> for more information.
-   </para>
-
-<!## XC>
-&xconly;
-   <para>
-    In <productname>Postgres-XC</>, manual <command>VACUUM</> will be
-    populated to all the Datanodes as well.  However, you should
-    configure autovacuum for each Coordinator and Datanodes.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    In <productname>Postgres-XL</>, a manual <command>VACUUM</> will be
-    pushed down to all the Datanodes as well.  
-    Depending on your workload, if you have a highly loaded cluster,
-    you may wish to disable autovacuum and vacuum at specific times.
-   </para>
-<!## end>
-  </sect2>
-
-  <sect2 id="populate-pg-dump">
-   <title>Some Notes About <application>pg_dump</></title>
-
-&common;
-   <para>
-    Dump scripts generated by <application>pg_dump</> automatically apply
-    several, but not all, of the above guidelines.  To reload a
-    <application>pg_dump</> dump as quickly as possible, you need to
-    do a few extra things manually.  (Note that these points apply while
-    <emphasis>restoring</> a dump, not while <emphasis>creating</> it.
-    The same points apply whether loading a text dump with
-    <application>psql</> or using <application>pg_restore</> to load
-    from a <application>pg_dump</> archive file.)
-   </para>
-
-   <para>
-    By default, <application>pg_dump</> uses <command>COPY</>, and when
-    it is generating a complete schema-and-data dump, it is careful to
-    load data before creating indexes and foreign keys.  So in this case
-    several guidelines are handled automatically.  What is left
-    for you to do is to:
-    <itemizedlist>
-     <listitem>
-      <para>
-       Set appropriate (i.e., larger than normal) values for
-       <varname>maintenance_work_mem</varname> and
-       <varname>checkpoint_segments</varname>.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       If using WAL archiving or streaming replication, consider disabling
-       them during the restore. To do that, set <varname>archive_mode</>
-       to <literal>off</>,
-       <varname>wal_level</varname> to <literal>minimal</>, and
-       <varname>max_wal_senders</> to zero before loading the dump.
-       Afterwards, set them back to the right values and take a fresh
-       base backup.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Consider whether the whole dump should be restored as a single
-       transaction.  To do that, pass the <option>-1</> or
-       <option>--single-transaction</> command-line option to
-       <application>psql</> or <application>pg_restore</>. When using this
-       mode, even the smallest of errors will rollback the entire restore,
-       possibly discarding many hours of processing.  Depending on how
-       interrelated the data is, that might seem preferable to manual cleanup,
-       or not.  <command>COPY</> commands will run fastest if you use a single
-       transaction and have WAL archiving turned off.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       If multiple CPUs are available in the database server, consider using
-       <application>pg_restore</>'s <option>--jobs</> option.  This
-       allows concurrent data loading and index creation.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Run <command>ANALYZE</> afterwards.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    A data-only dump will still use <command>COPY</>, but it does not
-    drop or recreate indexes, and it does not normally touch foreign
-    keys.
-
-     <footnote>
-      <para>
-       You can get the effect of disabling foreign keys by using
-       the <option>--disable-triggers</> option &mdash; but realize that
-       that eliminates, rather than just postponing, foreign key
-       validation, and so it is possible to insert bad data if you use it.
-      </para>
-     </footnote>
-
-    So when loading a data-only dump, it is up to you to drop and recreate
-    indexes and foreign keys if you wish to use those techniques.
-    It's still useful to increase <varname>checkpoint_segments</varname>
-    while loading the data, but don't bother increasing
-    <varname>maintenance_work_mem</varname>; rather, you'd do that while
-    manually recreating indexes and foreign keys afterwards.
-    And don't forget to <command>ANALYZE</> when you're done; see
-    <xref linkend="vacuum-for-statistics">
-    and <xref linkend="autovacuum"> for more information.
-   </para>
-  </sect2>
-  </sect1>
-
-  <sect1 id="non-durability">
-   <title>Non-Durable Settings</title>
-
-   <indexterm zone="non-durability">
-    <primary>non-durable</primary>
-   </indexterm>
-
-&common;
-   <para>
-    Durability is a database feature that guarantees the recording of
-    committed transactions even if the server crashes or loses
-    power.  However, durability adds significant database overhead,
-    so if your site does not require such a guarantee,
-<!## PG>
-    <productname>PostgreSQL</productname> can be configured to run
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> can be configured to run
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> can be configured to run
-<!## end>
-    much faster.  The following are configuration changes you can make
-    to improve performance in such cases.  Except as noted below, durability
-    is still guaranteed in case of a crash of the database software;
-    only abrupt operating system stoppage creates a risk of data loss
-    or corruption when these settings are used.
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Place the database cluster's data directory in a memory-backed
-       file system (i.e. <acronym>RAM</> disk).  This eliminates all
-       database disk I/O, but limits data storage to the amount of
-       available memory (and perhaps swap).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Turn off <xref linkend="guc-fsync">;  there is no need to flush
-       data to disk.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Turn off <xref linkend="guc-full-page-writes">;  there is no need
-       to guard against partial page writes.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Increase <xref linkend="guc-checkpoint-segments"> and <xref
-       linkend="guc-checkpoint-timeout"> ; this reduces the frequency
-       of checkpoints, but increases the storage requirements of
-       <filename>/pg_xlog</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Turn off <xref linkend="guc-synchronous-commit">;  there might be no
-       need to write the <acronym>WAL</acronym> to disk on every
-       commit.  This setting does risk transaction loss (though not data
-       corruption) in case of a crash of the <emphasis>database</> alone.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-  </sect1>
-
- </chapter>
diff --git a/doc-xc/src/sgml/pgarchivecleanup.sgmlin b/doc-xc/src/sgml/pgarchivecleanup.sgmlin
deleted file mode 100644
index e02b00df88..0000000000
--- a/doc-xc/src/sgml/pgarchivecleanup.sgmlin
+++ /dev/null
@@ -1,187 +0,0 @@
-<!-- doc/src/sgml/pgarchivecleanup.sgml -->
-
-<sect1 id="pgarchivecleanup" xreflabel="pg_archivecleanup">
- <title>pg_archivecleanup</title>
-
- <indexterm zone="pgarchivecleanup">
-  <primary>pg_archivecleanup</primary>
- </indexterm>
-
-&common;
-
- <para>
-  <application>pg_archivecleanup</> is designed to be used as an
-  <literal>archive_cleanup_command</literal> to clean up WAL file archives when
-<!## PG>
-  running as a standby server (see <xref linkend="warm-standby">).
-<!## end>
-<!## XC>
-  running as a standby server.
-<!## end>
-<!## XL>
-  running as a standby server.
-<!## end>
-  <application>pg_archivecleanup</> can also be used as a standalone program to
-  clean WAL file archives.
- </para>
-
-<!## XC>
- <para>
-  Please note that this command takes care of each Datanode or
-  Coordinator.  You should configure each of them manually.
- </para>
-<!## end>
-<!## XL>
- <para>
-  Please note that this command takes care of each Datanode or
-  Coordinator.  You should configure each of them manually.
- </para>
-<!## end>
-
- <para>
-  <application>pg_archivecleanup</application> features include:
- </para>
- <itemizedlist>
-  <listitem>
-   <para>
-    Written in C, so very portable and easy to install
-   </para>
-  </listitem>
-  <listitem>
-   <para>
-    Easy-to-modify source code, with specifically designated
-    sections to modify for your own needs
-   </para>
-  </listitem>
- </itemizedlist>
-
- <sect2>
-  <title>Usage</title>
-
-&common;
-  <para>
-   To configure a standby
-   server to use <application>pg_archivecleanup</>, put this into its
-   <filename>recovery.conf</filename> configuration file:
-<programlisting>
-archive_cleanup_command = 'pg_archivecleanup <replaceable>archivelocation</> %r'
-</programlisting>
-   where <replaceable>archivelocation</> is the directory from which WAL segment
-   files should be removed.
-  </para>
-  <para>
-<!## PG>
-   When used within <xref linkend="archive-cleanup-command">, all WAL files
-<!## end>
-<!## XC>
-   When used within archive-cleanup-command, all WAL files
-<!## end>
-<!## XL>
-   When used within archive-cleanup-command, all WAL files
-<!## end>
-   logically preceding the value of the <literal>%r</> argument will be removed
-   from <replaceable>archivelocation</>. This minimizes the number of files
-   that need to be retained, while preserving crash-restart capability.  Use of
-   this parameter is appropriate if the <replaceable>archivelocation</> is a
-   transient staging area for this particular standby server, but
-   <emphasis>not</> when the <replaceable>archivelocation</> is intended as a
-   long-term WAL archive area, or when multiple standby servers are recovering
-   from the same archive location.
-  </para>
-  <para>
-   The full syntax of <application>pg_archivecleanup</>'s command line is
-<synopsis>
-pg_archivecleanup <optional> <replaceable>option</> ... </optional> <replaceable>archivelocation</> <replaceable>restartwalfile</>
-</synopsis>
-   When used as a standalone program all WAL files logically preceding the
-   <literal>restartwalfile</> will be removed <replaceable>archivelocation</>.
-   In this mode, if you specify a <filename>.backup</> file name, then only the file prefix
-   will be used as the <literal>restartwalfile</>. This allows you to remove
-   all WAL files archived prior to a specific base backup without error.
-   For example, the following example will remove all files older than
-   WAL file name <filename>000000010000003700000010</>:
-<programlisting>
-pg_archivecleanup -d archive 000000010000003700000010.00000020.backup
-
-pg_archivecleanup:  keep WAL file "archive/000000010000003700000010" and later
-pg_archivecleanup:  removing file "archive/00000001000000370000000F"
-pg_archivecleanup:  removing file "archive/00000001000000370000000E"
-</programlisting>
-   <application>pg_archivecleanup</application> assumes that
-   <replaceable>archivelocation</> is a directory readable and writable by the
-   server-owning user.
-  </para>
- </sect2>
-
- <sect2>
-  <title><application>pg_archivecleanup</> Options</title>
-
-&common;
-   <para>
-    <application>pg_archivecleanup</application> accepts the following command-line arguments:
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>-d</option></term>
-      <listitem>
-       <para>
-        Print lots of debug logging output on <filename>stderr</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
- </sect2>
-
- <sect2>
-  <title>Examples</title>
-
-&common;
-  <para>On Linux or Unix systems, you might use:
-<programlisting>
-archive_cleanup_command = 'pg_archivecleanup -d /mnt/standby/archive %r 2>>cleanup.log'
-</programlisting>
-   where the archive directory is physically located on the standby server,
-   so that the <varname>archive_command</> is accessing it across NFS,
-   but the files are local to the standby.
-   This will:
-  </para>
-  <itemizedlist>
-   <listitem>
-    <para>
-     produce debugging output in <filename>cleanup.log</>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     remove no-longer-needed files from the archive directory
-    </para>
-   </listitem>
-  </itemizedlist>
-
- </sect2>
-
- <sect2>
-  <title>Supported Server Versions</title>
-
-&common;
-  <para>
-   <application>pg_archivecleanup</application> is designed to work with
-   <productname>PostgreSQL</> 8.0 and later when used as a standalone utility,
-   or with <productname>PostgreSQL</> 9.0 and later when used as an
-   archive cleanup command.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Simon Riggs <email>[email protected]</email>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgbench.sgmlin b/doc-xc/src/sgml/pgbench.sgmlin
deleted file mode 100644
index c3f031a88f..0000000000
--- a/doc-xc/src/sgml/pgbench.sgmlin
+++ /dev/null
@@ -1,832 +0,0 @@
-<!-- doc/src/sgml/pgbench.sgml -->
-
-<sect1 id="pgbench" xreflabel="pgbench">
- <title>pgbench</title>
-
- <indexterm zone="pgbench">
-  <primary>pgbench</primary>
- </indexterm>
-
-&common;
-
- <para>
-  <application>pgbench</application> is a simple program for running benchmark
-  tests on <productname>PostgreSQL</>.  It runs the same sequence of SQL
-  commands over and over, possibly in multiple concurrent database sessions,
-  and then calculates the average transaction rate (transactions per second).
-  By default, <application>pgbench</application> tests a scenario that is
-  loosely based on TPC-B, involving five <command>SELECT</>,
-  <command>UPDATE</>, and <command>INSERT</> commands per transaction.
-  However, it is easy to test other cases by writing your own transaction
-  script files.
- </para>
-
- <para>
-  Typical output from pgbench looks like:
-
-<screen>
-transaction type: TPC-B (sort of)
-scaling factor: 10
-query mode: simple
-number of clients: 10
-number of threads: 1
-number of transactions per client: 1000
-number of transactions actually processed: 10000/10000
-tps = 85.184871 (including connections establishing)
-tps = 85.296346 (excluding connections establishing)
-</screen>
-
-  The first six lines report some of the most important parameter
-  settings.  The next line reports the number of transactions completed
-  and intended (the latter being just the product of number of clients
-  and number of transactions per client); these will be equal unless the run
-  failed before completion.  (In <literal>-T</> mode, only the actual
-  number of transactions is printed.)
-  The last two lines report the number of transactions per second,
-  figured with and without counting the time to start database sessions.
- </para>
-
- <sect2>
-  <title>Overview</title>
-
-  <para>
-   The default TPC-B-like transaction test requires specific tables to be
-   set up beforehand.  <application>pgbench</> should be invoked with
-   the <literal>-i</> (initialize) option to create and populate these
-   tables.  (When you are testing a custom script, you don't need this
-   step, but will instead need to do whatever setup your test needs.)
-   Initialization looks like:
-
-<programlisting>
-pgbench -i <optional> <replaceable>other-options</> </optional> <replaceable>dbname</>
-</programlisting>
-
-   where <replaceable>dbname</> is the name of the already-created
-   database to test in.  (You may also need <literal>-h</>,
-   <literal>-p</>, and/or <literal>-U</> options to specify how to
-   connect to the database server.)
-  </para>
-
-  <caution>
-   <para>
-    <literal>pgbench -i</> creates four tables <structname>pgbench_accounts</>,
-    <structname>pgbench_branches</>, <structname>pgbench_history</>, and
-    <structname>pgbench_tellers</>,
-    destroying any existing tables of these names.
-    Be very careful to use another database if you have tables having these
-    names!
-   </para>
-  </caution>
-
-  <para>
-   At the default <quote>scale factor</> of 1, the tables initially
-   contain this many rows:
-<screen>
-table                   # of rows
----------------------------------
-pgbench_branches        1
-pgbench_tellers         10
-pgbench_accounts        100000
-pgbench_history         0
-</screen>
-   You can (and, for most purposes, probably should) increase the number
-   of rows by using the <literal>-s</> (scale factor) option.  The
-   <literal>-F</> (fillfactor) option might also be used at this point.
-  </para>
-
-  <para>
-   Once you have done the necessary setup, you can run your benchmark
-   with a command that doesn't include <literal>-i</>, that is
-
-<programlisting>
-pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</>
-</programlisting>
-
-   In nearly all cases, you'll need some options to make a useful test.
-   The most important options are <literal>-c</> (number of clients),
-   <literal>-t</> (number of transactions), <literal>-T</> (time limit),
-   and <literal>-f</> (specify a custom script file).
-   See below for a full list.
-  </para>
-
-  <para>
-   <xref linkend="pgbench-init-options"> shows options that are used
-   during database initialization, while
-   <xref linkend="pgbench-run-options"> shows options that are used
-   while running benchmarks, and
-   <xref linkend="pgbench-common-options"> shows options that are useful
-   in both cases.
-  </para>
-
- </sect2>
-
- <sect2 id="pgbench-init-options">
-  <title><application>pgbench</> Initialization Options</title>
-
-   <para>
-    <application>pgbench</application> accepts the following command-line
-    initialization arguments:
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>-i</option></term>
-      <listitem>
-       <para>
-        Required to invoke initialization mode.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-F</option> <replaceable>fillfactor</></term>
-      <listitem>
-       <para>
-        Create the <structname>pgbench_accounts</>,
-        <structname>pgbench_tellers</> and
-        <structname>pgbench_branches</> tables with the given fillfactor.
-        Default is 100.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option> <replaceable>scale_factor</></term>
-      <listitem>
-       <para>
-        Multiply the number of rows generated by the scale factor.
-        For example, <literal>-s 100</> will create 10,000,000 rows
-        in the <structname>pgbench_accounts</> table. Default is 1.
-       </para>
-      </listitem>
-     </varlistentry>
-
-<!## XC>
-     <varlistentry>
-      <term><option>-k</option></term>
-      <listitem>
-       <para>
-        Use column <structname>bid</> as hash distribution key for tables
-        <structname>pgbench_accounts</>, <structname>pgbench_tellers</>,
-        <structname>pgbench_branches</>. This limits the selectivity of
-        remote nodes to a single node for each transaction as all the tables
-        are distributed respecting the same key.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-<!## XL>
-     <varlistentry>
-      <term><option>-k</option></term>
-      <listitem>
-       <para>
-        Use column <structname>bid</> as hash distribution key for tables
-        <structname>pgbench_accounts</>, <structname>pgbench_tellers</>,
-        <structname>pgbench_branches</>. This limits the selectivity of
-        remote nodes to a single node for each transaction as all the tables
-        are distributed respecting the same key.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-
-    </variablelist>
-   </para>
-
- </sect2>
-
- <sect2 id="pgbench-run-options">
-  <title><application>pgbench</> Benchmarking Options</title>
-
-   <para>
-    <application>pgbench</application> accepts the following command-line
-    benchmarking arguments:
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>-c</option> <replaceable>clients</></term>
-      <listitem>
-       <para>
-        Number of clients simulated, that is, number of concurrent database
-        sessions.  Default is 1.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-C</option></term>
-      <listitem>
-       <para>
-        Establish a new connection for each transaction, rather than
-        doing it just once per client session.
-        This is useful to measure the connection overhead.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-d</option></term>
-      <listitem>
-       <para>
-        Print debugging output.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-D</option> <replaceable>varname</><literal>=</><replaceable>value</></term>
-      <listitem>
-       <para>
-        Define a variable for use by a custom script (see below).
-        Multiple <literal>-D</> options are allowed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-f</option> <replaceable>filename</></term>
-      <listitem>
-       <para>
-        Read transaction script from <replaceable>filename</>.
-        See below for details.
-        <literal>-N</literal>, <literal>-S</literal>, and <literal>-f</literal>
-        are mutually exclusive.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-j</option> <replaceable>threads</></term>
-      <listitem>
-       <para>
-        Number of worker threads within <application>pgbench</application>.
-        Using more than one thread can be helpful on multi-CPU machines.
-        The number of clients must be a multiple of the number of threads,
-        since each thread is given the same number of client sessions to manage.
-        Default is 1.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l</option></term>
-      <listitem>
-       <para>
-        Write the time taken by each transaction to a log file.
-        See below for details.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-M</option> <replaceable>querymode</></term>
-      <listitem>
-       <para>
-        Protocol to use for submitting queries to the server:
-          <itemizedlist>
-           <listitem>
-            <para><literal>simple</>: use simple query protocol.</para>
-           </listitem>
-           <listitem>
-            <para><literal>extended</>: use extended query protocol.</para>
-           </listitem>
-           <listitem>
-            <para><literal>prepared</>: use extended query protocol with prepared statements.</para>
-           </listitem>
-          </itemizedlist>
-        The default is simple query protocol.  (See <xref linkend="protocol">
-        for more information.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-n</option></term>
-      <listitem>
-       <para>
-        Perform no vacuuming before running the test.
-        This option is <emphasis>necessary</>
-        if you are running a custom test scenario that does not include
-        the standard tables <structname>pgbench_accounts</>,
-        <structname>pgbench_branches</>, <structname>pgbench_history</>, and
-        <structname>pgbench_tellers</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-N</option></term>
-      <listitem>
-       <para>
-        Do not update <structname>pgbench_tellers</> and
-        <structname>pgbench_branches</>.
-        This will avoid update contention on these tables, but
-        it makes the test case even less like TPC-B.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-r</option></term>
-      <listitem>
-       <para>
-        Report the average per-statement latency (execution time from the
-        perspective of the client) of each command after the benchmark
-        finishes.  See below for details.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option> <replaceable>scale_factor</></term>
-      <listitem>
-       <para>
-        Report the specified scale factor in <application>pgbench</>'s
-        output.  With the built-in tests, this is not necessary; the
-        correct scale factor will be detected by counting the number of
-        rows in the <structname>pgbench_branches</> table.  However, when testing
-        custom benchmarks (<literal>-f</> option), the scale factor
-        will be reported as 1 unless this option is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-S</option></term>
-      <listitem>
-       <para>
-        Perform select-only transactions instead of TPC-B-like test.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t</option> <replaceable>transactions</></term>
-      <listitem>
-       <para>
-        Number of transactions each client runs.  Default is 10.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-T</option> <replaceable>seconds</></term>
-      <listitem>
-       <para>
-        Run the test for this many seconds, rather than a fixed number of
-        transactions per client. <literal>-t</literal> and
-        <literal>-T</literal> are mutually exclusive.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-v</option></term>
-      <listitem>
-       <para>
-        Vacuum all four standard tables before running the test.
-        With neither <literal>-n</> nor <literal>-v</>, pgbench will vacuum the
-        <structname>pgbench_tellers</> and <structname>pgbench_branches</>
-        tables, and will truncate <structname>pgbench_history</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-<!## XC>
-     <varlistentry>
-      <term><option>-k</option></term>
-      <listitem>
-       <para>
-        Add an additional condition based on column <structname>bid</> based
-        on its values as a hash key to enforce selectivity of all write queries
-        to a single remote node. This functionality permits to check the
-        write-scalability performance of the system by distributing data among cluster nodes.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-<!## XL>
-     <varlistentry>
-      <term><option>-k</option></term>
-      <listitem>
-       <para>
-        Add an additional condition based on column <structname>bid</> based
-        on its values as a hash key to enforce selectivity of all write queries
-        to a single remote node. This functionality permits to check the
-        write-scalability performance of the system by distributing data among cluster nodes.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-
-    </variablelist>
-   </para>
-
- </sect2>
-
- <sect2 id="pgbench-common-options">
-  <title><application>pgbench</> Common Options</title>
-
-   <para>
-    <application>pgbench</application> accepts the following command-line
-    common arguments:
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>-h</option> <replaceable>hostname</></term>
-      <listitem>
-       <para>
-        The database server's host name
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p</option> <replaceable>port</></term>
-      <listitem>
-       <para>
-        The database server's port number
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U</option> <replaceable>login</></term>
-      <listitem>
-       <para>
-        The user name to connect as
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
- </sect2>
-
- <sect2>
-  <title>What is the <quote>Transaction</> Actually Performed in pgbench?</title>
-
-  <para>
-   The default transaction script issues seven commands per transaction:
-  </para>
-
-  <orderedlist>
-   <listitem><para><literal>BEGIN;</literal></para></listitem>
-   <listitem><para><literal>UPDATE pgbench_accounts SET abalance = abalance + :delta WHERE aid = :aid;</literal></para></listitem>
-   <listitem><para><literal>SELECT abalance FROM pgbench_accounts WHERE aid = :aid;</literal></para></listitem>
-   <listitem><para><literal>UPDATE pgbench_tellers SET tbalance = tbalance + :delta WHERE tid = :tid;</literal></para></listitem>
-   <listitem><para><literal>UPDATE pgbench_branches SET bbalance = bbalance + :delta WHERE bid = :bid;</literal></para></listitem>
-   <listitem><para><literal>INSERT INTO pgbench_history (tid, bid, aid, delta, mtime) VALUES (:tid, :bid, :aid, :delta, CURRENT_TIMESTAMP);</literal></para></listitem>
-   <listitem><para><literal>END;</literal></para></listitem>
-  </orderedlist>
-
-  <para>
-   If you specify <literal>-N</>, steps 4 and 5 aren't included in the
-   transaction.  If you specify <literal>-S</>, only the <command>SELECT</> is
-   issued.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Custom Scripts</title>
-
-  <para>
-   <application>pgbench</application> has support for running custom
-   benchmark scenarios by replacing the default transaction script
-   (described above) with a transaction script read from a file
-   (<literal>-f</literal> option).  In this case a <quote>transaction</>
-   counts as one execution of a script file.  You can even specify
-   multiple scripts (multiple <literal>-f</literal> options), in which
-   case a random one of the scripts is chosen each time a client session
-   starts a new transaction.
-  </para>
-
-  <para>
-   The format of a script file is one SQL command per line; multiline
-   SQL commands are not supported.  Empty lines and lines beginning with
-   <literal>--</> are ignored.  Script file lines can also be
-   <quote>meta commands</>, which are interpreted by <application>pgbench</>
-   itself, as described below.
-  </para>
-
-  <para>
-   There is a simple variable-substitution facility for script files.
-   Variables can be set by the command-line <literal>-D</> option,
-   explained above, or by the meta commands explained below.
-   In addition to any variables preset by <literal>-D</> command-line options,
-   the variable <literal>scale</> is preset to the current scale factor.
-   Once set, a variable's
-   value can be inserted into a SQL command by writing
-   <literal>:</><replaceable>variablename</>.  When running more than
-   one client session, each session has its own set of variables.
-  </para>
-
-  <para>
-   Script file meta commands begin with a backslash (<literal>\</>).
-   Arguments to a meta command are separated by white space.
-   These meta commands are supported:
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term>
-     <literal>\set <replaceable>varname</> <replaceable>operand1</> [ <replaceable>operator</> <replaceable>operand2</> ]</literal>
-    </term>
-
-    <listitem>
-     <para>
-      Sets variable <replaceable>varname</> to a calculated integer value.
-      Each <replaceable>operand</> is either an integer constant or a
-      <literal>:</><replaceable>variablename</> reference to a variable
-      having an integer value.  The <replaceable>operator</> can be
-      <literal>+</>, <literal>-</>, <literal>*</>, or <literal>/</>.
-     </para>
-
-     <para>
-      Example:
-<programlisting>
-\set ntellers 10 * :scale
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <literal>\setrandom <replaceable>varname</> <replaceable>min</> <replaceable>max</></literal>
-    </term>
-
-    <listitem>
-     <para>
-      Sets variable <replaceable>varname</> to a random integer value
-      between the limits <replaceable>min</> and <replaceable>max</> inclusive.
-      Each limit can be either an integer constant or a
-      <literal>:</><replaceable>variablename</> reference to a variable
-      having an integer value.
-     </para>
-
-     <para>
-      Example:
-<programlisting>
-\setrandom aid 1 :naccounts
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <literal>\sleep <replaceable>number</> [ us | ms | s ]</literal>
-    </term>
-
-    <listitem>
-     <para>
-      Causes script execution to sleep for the specified duration in
-      microseconds (<literal>us</>), milliseconds (<literal>ms</>) or seconds
-      (<literal>s</>).  If the unit is omitted then seconds are the default.
-      <replaceable>number</> can be either an integer constant or a
-      <literal>:</><replaceable>variablename</> reference to a variable
-      having an integer value.
-     </para>
-
-     <para>
-      Example:
-<programlisting>
-\sleep 10 ms
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <literal>\setshell <replaceable>varname</> <replaceable>command</> [ <replaceable>argument</> ... ]</literal>
-    </term>
-
-    <listitem>
-     <para>
-      Sets variable <replaceable>varname</> to the result of the shell command
-      <replaceable>command</>. The command must return an integer value
-      through its standard output.
-     </para>
-
-     <para>
-      <replaceable>argument</> can be either a text constant or a
-      <literal>:</><replaceable>variablename</> reference to a variable of
-      any types. If you want to use <replaceable>argument</> starting with
-      colons, you need to add an additional colon at the beginning of
-      <replaceable>argument</>.
-     </para>
-
-     <para>
-      Example:
-<programlisting>
-\setshell variable_to_be_assigned command literal_argument :variable ::literal_starting_with_colon
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <literal>\shell <replaceable>command</> [ <replaceable>argument</> ... ]</literal>
-    </term>
-
-    <listitem>
-     <para>
-      Same as <literal>\setshell</literal>, but the result is ignored.
-     </para>
-
-     <para>
-      Example:
-<programlisting>
-\shell command literal_argument :variable ::literal_starting_with_colon
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   As an example, the full definition of the built-in TPC-B-like
-   transaction is:
-
-<programlisting>
-\set nbranches :scale
-\set ntellers 10 * :scale
-\set naccounts 100000 * :scale
-\setrandom aid 1 :naccounts
-\setrandom bid 1 :nbranches
-\setrandom tid 1 :ntellers
-\setrandom delta -5000 5000
-BEGIN;
-UPDATE pgbench_accounts SET abalance = abalance + :delta WHERE aid = :aid;
-SELECT abalance FROM pgbench_accounts WHERE aid = :aid;
-UPDATE pgbench_tellers SET tbalance = tbalance + :delta WHERE tid = :tid;
-UPDATE pgbench_branches SET bbalance = bbalance + :delta WHERE bid = :bid;
-INSERT INTO pgbench_history (tid, bid, aid, delta, mtime) VALUES (:tid, :bid, :aid, :delta, CURRENT_TIMESTAMP);
-END;
-</programlisting>
-
-   This script allows each iteration of the transaction to reference
-   different, randomly-chosen rows.  (This example also shows why it's
-   important for each client session to have its own variables &mdash;
-   otherwise they'd not be independently touching different rows.)
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>Per-Transaction Logging</title>
-
-  <para>
-   With the <literal>-l</> option, <application>pgbench</> writes the time
-   taken by each transaction to a log file.  The log file will be named
-   <filename>pgbench_log.<replaceable>nnn</></filename>, where
-   <replaceable>nnn</> is the PID of the pgbench process.
-   If the <literal>-j</> option is 2 or higher, creating multiple worker
-   threads, each will have its own log file. The first worker will use the
-   same name for its log file as in the standard single worker case.
-   The additional log files for the other workers will be named
-   <filename>pgbench_log.<replaceable>nnn</>.<replaceable>mmm</></filename>,
-   where <replaceable>mmm</> is a sequential number for each worker starting
-   with 1.
-  </para>
-
-  <para>
-   The format of the log is:
-
-<synopsis>
-<replaceable>client_id</> <replaceable>transaction_no</> <replaceable>time</> <replaceable>file_no</> <replaceable>time_epoch</> <replaceable>time_us</>
-</synopsis>
-
-   where <replaceable>time</> is the total elapsed transaction time in microseconds,
-   <replaceable>file_no</> identifies which script file was used
-   (useful when multiple scripts were specified with <literal>-f</>),
-   and <replaceable>time_epoch</>/<replaceable>time_us</> are a
-   UNIX epoch format timestamp and an offset
-   in microseconds (suitable for creating a ISO 8601
-   timestamp with fractional seconds) showing when
-   the transaction completed.
-  </para>
-
-  <para>
-   Here are example outputs:
-<screen>
- 0 199 2241 0 1175850568 995598
- 0 200 2465 0 1175850568 998079
- 0 201 2513 0 1175850569 608
- 0 202 2038 0 1175850569 2663
-</screen>
-  </para>
- </sect2>
-
- <sect2>
-  <title>Per-Statement Latencies</title>
-
-  <para>
-   With the <literal>-r</> option, <application>pgbench</> collects
-   the elapsed transaction time of each statement executed by every
-   client.  It then reports an average of those values, referred to
-   as the latency for each statement, after the benchmark has finished.
-  </para>
-
-  <para>
-   For the default script, the output will look similar to this:
-<screen>
-starting vacuum...end.
-transaction type: TPC-B (sort of)
-scaling factor: 1
-query mode: simple
-number of clients: 10
-number of threads: 1
-number of transactions per client: 1000
-number of transactions actually processed: 10000/10000
-tps = 618.764555 (including connections establishing)
-tps = 622.977698 (excluding connections establishing)
-statement latencies in milliseconds:
-        0.004386        \set nbranches 1 * :scale
-        0.001343        \set ntellers 10 * :scale
-        0.001212        \set naccounts 100000 * :scale
-        0.001310        \setrandom aid 1 :naccounts
-        0.001073        \setrandom bid 1 :nbranches
-        0.001005        \setrandom tid 1 :ntellers
-        0.001078        \setrandom delta -5000 5000
-        0.326152        BEGIN;
-        0.603376        UPDATE pgbench_accounts SET abalance = abalance + :delta WHERE aid = :aid;
-        0.454643        SELECT abalance FROM pgbench_accounts WHERE aid = :aid;
-        5.528491        UPDATE pgbench_tellers SET tbalance = tbalance + :delta WHERE tid = :tid;
-        7.335435        UPDATE pgbench_branches SET bbalance = bbalance + :delta WHERE bid = :bid;
-        0.371851        INSERT INTO pgbench_history (tid, bid, aid, delta, mtime) VALUES (:tid, :bid, :aid, :delta, CURRENT_TIMESTAMP);
-        1.212976        END;
-</screen>
-  </para>
-
-  <para>
-   If multiple script files are specified, the averages are reported
-   separately for each script file.
-  </para>
-
-  <para>
-   Note that collecting the additional timing information needed for
-   per-statement latency computation adds some overhead.  This will slow
-   average execution speed and lower the computed TPS.  The amount
-   of slowdown varies significantly depending on platform and hardware.
-   Comparing average TPS values with and without latency reporting enabled
-   is a good way to measure if the timing overhead is significant.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Good Practices</title>
-
-  <para>
-   It is very easy to use <application>pgbench</> to produce completely
-   meaningless numbers.  Here are some guidelines to help you get useful
-   results.
-  </para>
-
-  <para>
-   In the first place, <emphasis>never</> believe any test that runs
-   for only a few seconds.  Use the <literal>-t</> or <literal>-T</> option
-   to make the run last at least a few minutes, so as to average out noise.
-   In some cases you could need hours to get numbers that are reproducible.
-   It's a good idea to try the test run a few times, to find out if your
-   numbers are reproducible or not.
-  </para>
-
-  <para>
-   For the default TPC-B-like test scenario, the initialization scale factor
-   (<literal>-s</>) should be at least as large as the largest number of
-   clients you intend to test (<literal>-c</>); else you'll mostly be
-   measuring update contention.  There are only <literal>-s</> rows in
-   the <structname>pgbench_branches</> table, and every transaction wants to
-   update one of them, so <literal>-c</> values in excess of <literal>-s</>
-   will undoubtedly result in lots of transactions blocked waiting for
-   other transactions.
-  </para>
-
-  <para>
-   The default test scenario is also quite sensitive to how long it's been
-   since the tables were initialized: accumulation of dead rows and dead space
-   in the tables changes the results.  To understand the results you must keep
-   track of the total number of updates and when vacuuming happens.  If
-   autovacuum is enabled it can result in unpredictable changes in measured
-   performance.
-  </para>
-
-  <para>
-   A limitation of <application>pgbench</> is that it can itself become
-   the bottleneck when trying to test a large number of client sessions.
-   This can be alleviated by running <application>pgbench</> on a different
-   machine from the database server, although low network latency will be
-   essential.  It might even be useful to run several <application>pgbench</>
-   instances concurrently, on several client machines, against the same
-   database server.
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgbuffercache.sgmlin b/doc-xc/src/sgml/pgbuffercache.sgmlin
deleted file mode 100644
index f2a516fef0..0000000000
--- a/doc-xc/src/sgml/pgbuffercache.sgmlin
+++ /dev/null
@@ -1,199 +0,0 @@
-<!-- doc/src/sgml/pgbuffercache.sgml -->
-
-<sect1 id="pgbuffercache" xreflabel="pg_buffercache">
- <title>pg_buffercache</title>
-
- <indexterm zone="pgbuffercache">
-  <primary>pg_buffercache</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>pg_buffercache</filename> module provides a means for
-  examining what's happening in the shared buffer cache in real time.
- </para>
-
- <para>
-  The module provides a C function <function>pg_buffercache_pages</function>
-  that returns a set of records, plus a view
-  <structname>pg_buffercache</structname> that wraps the function for
-  convenient use.
- </para>
-
- <para>
-  By default public access is revoked from both of these, just in case there
-  are security issues lurking.
- </para>
-
-<!## XC>
-&xconly;
- <para>
-  <filename>pg_buffercache</filename> returns information local to the
-  connecting Coordinator.  To inquire information local to other node,
-  use <command>EXECUTE DIRECT</command>.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <filename>pg_buffercache</filename> returns information local to the
-  connecting Coordinator.  To inquire information local to other node,
-  use <command>EXECUTE DIRECT</command>.
- </para>
-<!## end>
-
- <sect2>
-  <title>The <structname>pg_buffercache</structname> View</title>
-
-&common;
-  <para>
-   The definitions of the columns exposed by the view are shown in <xref linkend="pgbuffercache-columns">.
-  </para>
-
-  <table id="pgbuffercache-columns">
-   <title><structname>pg_buffercache</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-
-     <row>
-      <entry><structfield>bufferid</structfield></entry>
-      <entry><type>integer</type></entry>
-      <entry></entry>
-      <entry>ID, in the range 1..<varname>shared_buffers</></entry>
-     </row>
-
-     <row>
-      <entry><structfield>relfilenode</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal>pg_class.relfilenode</literal></entry>
-      <entry>Filenode number of the relation</entry>
-     </row>
-
-     <row>
-      <entry><structfield>reltablespace</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal>pg_tablespace.oid</literal></entry>
-      <entry>Tablespace OID of the relation</entry>
-     </row>
-
-     <row>
-      <entry><structfield>reldatabase</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal>pg_database.oid</literal></entry>
-      <entry>Database OID of the relation</entry>
-     </row>
-
-     <row>
-      <entry><structfield>relblocknumber</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Page number within the relation</entry>
-     </row>
-
-     <row>
-      <entry><structfield>relforknumber</structfield></entry>
-      <entry><type>smallint</type></entry>
-      <entry></entry>
-      <entry>Fork number within the relation</entry>
-     </row>
-
-     <row>
-      <entry><structfield>isdirty</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry></entry>
-      <entry>Is the page dirty?</entry>
-     </row>
-
-     <row>
-      <entry><structfield>usagecount</structfield></entry>
-      <entry><type>smallint</type></entry>
-      <entry></entry>
-      <entry>Page LRU count</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   There is one row for each buffer in the shared cache. Unused buffers are
-   shown with all fields null except <structfield>bufferid</>.  Shared system
-   catalogs are shown as belonging to database zero.
-  </para>
-
-  <para>
-   Because the cache is shared by all the databases, there will normally be
-   pages from relations not belonging to the current database.  This means
-   that there may not be matching join rows in <structname>pg_class</> for
-   some rows, or that there could even be incorrect joins.  If you are
-   trying to join against <structname>pg_class</>, it's a good idea to
-   restrict the join to rows having <structfield>reldatabase</> equal to
-   the current database's OID or zero.
-  </para>
-
-  <para>
-   When the <structname>pg_buffercache</> view is accessed, internal buffer
-   manager locks are taken for long enough to copy all the buffer state
-   data that the view will display.
-   This ensures that the view produces a consistent set of results, while not
-   blocking normal buffer activity longer than necessary.  Nonetheless there
-   could be some impact on database performance if this view is read often.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Sample Output</title>
-
-<screen>
-regression=# SELECT c.relname, count(*) AS buffers
-             FROM pg_buffercache b INNER JOIN pg_class c
-             ON b.relfilenode = pg_relation_filenode(c.oid) AND
-                b.reldatabase IN (0, (SELECT oid FROM pg_database
-                                      WHERE datname = current_database()))
-             GROUP BY c.relname
-             ORDER BY 2 DESC
-             LIMIT 10;
-
-             relname             | buffers
----------------------------------+---------
- tenk2                           |     345
- tenk1                           |     141
- pg_proc                         |      46
- pg_class                        |      45
- pg_attribute                    |      43
- pg_class_relname_nsp_index      |      30
- pg_proc_proname_args_nsp_index  |      28
- pg_attribute_relid_attnam_index |      26
- pg_depend                       |      22
- pg_depend_reference_index       |      20
-(10 rows)
-</screen>
- </sect2>
-
- <sect2>
-  <title>Authors</title>
-
-  <para>
-   Mark Kirkwood <email>[email protected]</email>
-  </para>
-
-  <para>
-   Design suggestions: Neil Conway <email>[email protected]</email>
-  </para>
-
-  <para>
-   Debugging advice: Tom Lane <email>[email protected]</email>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgcrypto.sgmlin b/doc-xc/src/sgml/pgcrypto.sgmlin
deleted file mode 100644
index f46dd54ede..0000000000
--- a/doc-xc/src/sgml/pgcrypto.sgmlin
+++ /dev/null
@@ -1,1320 +0,0 @@
-<!-- doc/src/sgml/pgcrypto.sgml -->
-
-<sect1 id="pgcrypto" xreflabel="pgcrypto">
- <title>pgcrypto</title>
-
- <indexterm zone="pgcrypto">
-  <primary>pgcrypto</primary>
- </indexterm>
-
- <indexterm zone="pgcrypto">
-  <primary>encryption</primary>
-  <secondary>for specific columns</secondary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>pgcrypto</> module provides cryptographic functions for
-  <productname>PostgreSQL</>.
- </para>
-
- <sect2>
-  <title>General Hashing Functions</title>
-
-  <sect3>
-   <title><function>digest()</function></title>
-
-<synopsis>
-digest(data text, type text) returns bytea
-digest(data bytea, type text) returns bytea
-</synopsis>
-
-&common;
-   <para>
-    Computes a binary hash of the given <parameter>data</>.
-    <parameter>type</> is the algorithm to use.
-    Standard algorithms are <literal>md5</literal>, <literal>sha1</literal>,
-    <literal>sha224</literal>, <literal>sha256</literal>,
-    <literal>sha384</literal> and <literal>sha512</literal>.
-    If <filename>pgcrypto</> was built with
-    OpenSSL, more algorithms are available, as detailed in
-    <xref linkend="pgcrypto-with-without-openssl">.
-   </para>
-
-   <para>
-    If you want the digest as a hexadecimal string, use
-    <function>encode()</> on the result.  For example:
-<programlisting>
-CREATE OR REPLACE FUNCTION sha1(bytea) returns text AS $$
-    SELECT encode(digest($1, 'sha1'), 'hex')
-$$ LANGUAGE SQL STRICT IMMUTABLE;
-</programlisting>
-   </para>
-  </sect3>
-
-  <sect3>
-   <title><function>hmac()</function></title>
-
-<synopsis>
-hmac(data text, key text, type text) returns bytea
-hmac(data bytea, key text, type text) returns bytea
-</synopsis>
-
-&common;
-   <para>
-    Calculates hashed MAC for <parameter>data</> with key <parameter>key</>.
-    <parameter>type</> is the same as in <function>digest()</>.
-   </para>
-
-   <para>
-    This is similar to <function>digest()</> but the hash can only be
-    recalculated knowing the key.  This prevents the scenario of someone
-    altering data and also changing the hash to match.
-   </para>
-
-   <para>
-    If the key is larger than the hash block size it will first be hashed and
-    the result will be used as key.
-   </para>
-  </sect3>
- </sect2>
-
- <sect2>
-  <title>Password Hashing Functions</title>
-
-&common;
-  <para>
-   The functions <function>crypt()</> and <function>gen_salt()</>
-   are specifically designed for hashing passwords.
-   <function>crypt()</> does the hashing and <function>gen_salt()</>
-   prepares algorithm parameters for it.
-  </para>
-
-  <para>
-   The algorithms in <function>crypt()</> differ from usual hashing algorithms
-   like MD5 or SHA1 in the following respects:
-  </para>
-
-  <orderedlist>
-   <listitem>
-    <para>
-     They are slow.  As the amount of data is so small, this is the only
-     way to make brute-forcing passwords hard.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     They use a random value, called the <firstterm>salt</>, so that users
-     having the same password will have different encrypted passwords.
-     This is also an additional defense against reversing the algorithm.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     They include the algorithm type in the result, so passwords hashed with
-     different algorithms can co-exist.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Some of them are adaptive &mdash; that means when computers get
-     faster, you can tune the algorithm to be slower, without
-     introducing incompatibility with existing passwords.
-    </para>
-   </listitem>
-  </orderedlist>
-
-  <para>
-   <xref linkend="pgcrypto-crypt-algorithms"> lists the algorithms
-   supported by the <function>crypt()</function> function.
-  </para>
-
-  <table id="pgcrypto-crypt-algorithms">
-   <title>Supported Algorithms for <function>crypt()</></title>
-   <tgroup cols="5">
-    <thead>
-     <row>
-      <entry>Algorithm</entry>
-      <entry>Max Password Length</entry>
-      <entry>Adaptive?</entry>
-      <entry>Salt Bits</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><literal>bf</></entry>
-      <entry>72</entry>
-      <entry>yes</entry>
-      <entry>128</entry>
-      <entry>Blowfish-based, variant 2a</entry>
-     </row>
-     <row>
-      <entry><literal>md5</></entry>
-      <entry>unlimited</entry>
-      <entry>no</entry>
-      <entry>48</entry>
-      <entry>MD5-based crypt</entry>
-     </row>
-     <row>
-      <entry><literal>xdes</></entry>
-      <entry>8</entry>
-      <entry>yes</entry>
-      <entry>24</entry>
-      <entry>Extended DES</entry>
-     </row>
-     <row>
-      <entry><literal>des</></entry>
-      <entry>8</entry>
-      <entry>no</entry>
-      <entry>12</entry>
-      <entry>Original UNIX crypt</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <sect3>
-   <title><function>crypt()</></title>
-
-<synopsis>
-crypt(password text, salt text) returns text
-</synopsis>
-
-&common;
-   <para>
-    Calculates a crypt(3)-style hash of <parameter>password</>.
-    When storing a new password, you need to use
-    <function>gen_salt()</> to generate a new <parameter>salt</> value.
-    To check a password, pass the stored hash value as <parameter>salt</>,
-    and test whether the result matches the stored value.
-   </para>
-   <para>
-    Example of setting a new password:
-<programlisting>
-UPDATE ... SET pswhash = crypt('new password', gen_salt('md5'));
-</programlisting>
-   </para>
-   <para>
-    Example of authentication:
-<programlisting>
-SELECT pswhash = crypt('entered password', pswhash) FROM ... ;
-</programlisting>
-    This returns <literal>true</> if the entered password is correct.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title><function>gen_salt()</></title>
-
-<synopsis>
-gen_salt(type text [, iter_count integer ]) returns text
-</synopsis>
-
-&common;
-   <para>
-    Generates a new random salt string for use in <function>crypt()</>.
-    The salt string also tells <function>crypt()</> which algorithm to use.
-   </para>
-
-   <para>
-    The <parameter>type</> parameter specifies the hashing algorithm.
-    The accepted types are: <literal>des</literal>, <literal>xdes</literal>,
-    <literal>md5</literal> and <literal>bf</literal>.
-   </para>
-
-   <para>
-    The <parameter>iter_count</> parameter lets the user specify the iteration
-    count, for algorithms that have one.
-    The higher the count, the more time it takes to hash
-    the password and therefore the more time to break it.  Although with
-    too high a count the time to calculate a hash may be several years
-    &mdash; which is somewhat impractical.  If the <parameter>iter_count</>
-    parameter is omitted, the default iteration count is used.
-    Allowed values for <parameter>iter_count</> depend on the algorithm and
-    are shown in <xref linkend="pgcrypto-icfc-table">.
-   </para>
-
-   <table id="pgcrypto-icfc-table">
-    <title>Iteration Counts for <function>crypt()</></title>
-    <tgroup cols="4">
-     <thead>
-      <row>
-       <entry>Algorithm</entry>
-       <entry>Default</entry>
-       <entry>Min</entry>
-       <entry>Max</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry><literal>xdes</></entry>
-       <entry>725</entry>
-       <entry>1</entry>
-       <entry>16777215</entry>
-      </row>
-      <row>
-       <entry><literal>bf</></entry>
-       <entry>6</entry>
-       <entry>4</entry>
-       <entry>31</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    For <literal>xdes</literal> there is an additional limitation that the
-    iteration count must be an odd number.
-   </para>
-
-   <para>
-    To pick an appropriate iteration count, consider that
-    the original DES crypt was designed to have the speed of 4 hashes per
-    second on the hardware of that time.
-    Slower than 4 hashes per second would probably dampen usability.
-    Faster than 100 hashes per second is probably too fast.
-   </para>
-
-   <para>
-    <xref linkend="pgcrypto-hash-speed-table"> gives an overview of the relative slowness
-    of different hashing algorithms.
-    The table shows how much time it would take to try all
-    combinations of characters in an 8-character password, assuming
-    that the password contains either only lower case letters, or
-    upper- and lower-case letters and numbers.
-    In the <literal>crypt-bf</literal> entries, the number after a slash is
-    the <parameter>iter_count</parameter> parameter of
-    <function>gen_salt</function>.
-   </para>
-
-   <table id="pgcrypto-hash-speed-table">
-    <title>Hash Algorithm Speeds</title>
-    <tgroup cols="4">
-     <thead>
-      <row>
-       <entry>Algorithm</entry>
-       <entry>Hashes/sec</entry>
-       <entry>For <literal>[a-z]</></entry>
-       <entry>For <literal>[A-Za-z0-9]</></entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry><literal>crypt-bf/8</></entry>
-       <entry>28</entry>
-       <entry>246 years</entry>
-       <entry>251322 years</entry>
-      </row>
-      <row>
-       <entry><literal>crypt-bf/7</></entry>
-       <entry>57</entry>
-       <entry>121 years</entry>
-       <entry>123457 years</entry>
-      </row>
-      <row>
-       <entry><literal>crypt-bf/6</></entry>
-       <entry>112</entry>
-       <entry>62 years</entry>
-       <entry>62831 years</entry>
-      </row>
-      <row>
-       <entry><literal>crypt-bf/5</></entry>
-       <entry>211</entry>
-       <entry>33 years</entry>
-       <entry>33351 years</entry>
-      </row>
-      <row>
-       <entry><literal>crypt-md5</></entry>
-       <entry>2681</entry>
-       <entry>2.6 years</entry>
-       <entry>2625 years</entry>
-      </row>
-      <row>
-       <entry><literal>crypt-des</></entry>
-       <entry>362837</entry>
-       <entry>7 days</entry>
-       <entry>19 years</entry>
-      </row>
-      <row>
-       <entry><literal>sha1</></entry>
-       <entry>590223</entry>
-       <entry>4 days</entry>
-       <entry>12 years</entry>
-      </row>
-      <row>
-       <entry><literal>md5</></entry>
-       <entry>2345086</entry>
-       <entry>1 day</entry>
-       <entry>3 years</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    Notes:
-   </para>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-     The machine used is a 1.5GHz Pentium 4.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>crypt-des</> and <literal>crypt-md5</> algorithm numbers are
-      taken from John the Ripper v1.6.38 <literal>-test</> output.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>md5</> numbers are from mdcrack 1.2.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>sha1</> numbers are from lcrack-20031130-beta.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>crypt-bf</literal> numbers are taken using a simple program that
-      loops over 1000 8-character passwords.  That way I can show the speed
-      with different numbers of iterations.  For reference: <literal>john
-      -test</literal> shows 213 loops/sec for <literal>crypt-bf/5</>.
-      (The very small
-      difference in results is in accordance with the fact that the
-      <literal>crypt-bf</literal> implementation in <filename>pgcrypto</>
-      is the same one used in John the Ripper.)
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   <para>
-    Note that <quote>try all combinations</quote> is not a realistic exercise.
-    Usually password cracking is done with the help of dictionaries, which
-    contain both regular words and various mutations of them.  So, even
-    somewhat word-like passwords could be cracked much faster than the above
-    numbers suggest, while a 6-character non-word-like password may escape
-    cracking.  Or not.
-   </para>
-  </sect3>
- </sect2>
-
- <sect2>
-  <title>PGP Encryption Functions</title>
-
-&common;
-  <para>
-   The functions here implement the encryption part of the OpenPGP (RFC 4880)
-   standard.  Supported are both symmetric-key and public-key encryption.
-  </para>
-
-  <para>
-   An encrypted PGP message consists of 2 parts, or <firstterm>packets</>:
-  </para>
-  <itemizedlist>
-   <listitem>
-    <para>
-     Packet containing a session key &mdash; either symmetric-key or public-key
-     encrypted.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     Packet containing data encrypted with the session key.
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   When encrypting with a symmetric key (i.e., a password):
-  </para>
-  <orderedlist>
-   <listitem>
-    <para>
-     The given password is hashed using a String2Key (S2K) algorithm.  This is
-     rather similar to <function>crypt()</> algorithms &mdash; purposefully
-     slow and with random salt &mdash; but it produces a full-length binary
-     key.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     If a separate session key is requested, a new random key will be
-     generated.  Otherwise the S2K key will be used directly as the session
-     key.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     If the S2K key is to be used directly, then only S2K settings will be put
-     into the session key packet.  Otherwise the session key will be encrypted
-     with the S2K key and put into the session key packet.
-    </para>
-   </listitem>
-  </orderedlist>
-
-  <para>
-   When encrypting with a public key:
-  </para>
-  <orderedlist>
-   <listitem>
-    <para>
-     A new random session key is generated.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     It is encrypted using the public key and put into the session key packet.
-    </para>
-   </listitem>
-  </orderedlist>
-
-  <para>
-   In either case the data to be encrypted is processed as follows:
-  </para>
-  <orderedlist>
-   <listitem>
-    <para>
-     Optional data-manipulation: compression, conversion to UTF-8,
-     and/or conversion of line-endings.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     The data is prefixed with a block of random bytes.  This is equivalent
-     to using a random IV.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     An SHA1 hash of the random prefix and data is appended.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     All this is encrypted with the session key and placed in the data packet.
-    </para>
-   </listitem>
-  </orderedlist>
-
-  <sect3>
-   <title><function>pgp_sym_encrypt()</function></title>
-
-<synopsis>
-pgp_sym_encrypt(data text, psw text [, options text ]) returns bytea
-pgp_sym_encrypt_bytea(data bytea, psw text [, options text ]) returns bytea
-</synopsis>
-&common;
-   <para>
-    Encrypt <parameter>data</> with a symmetric PGP key <parameter>psw</>.
-    The <parameter>options</> parameter can contain option settings,
-    as described below.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title><function>pgp_sym_decrypt()</function></title>
-
-<synopsis>
-pgp_sym_decrypt(msg bytea, psw text [, options text ]) returns text
-pgp_sym_decrypt_bytea(msg bytea, psw text [, options text ]) returns bytea
-</synopsis>
-&common;
-   <para>
-    Decrypt a symmetric-key-encrypted PGP message.
-   </para>
-   <para>
-    Decrypting <type>bytea</> data with <function>pgp_sym_decrypt</> is disallowed.
-    This is to avoid outputting invalid character data.  Decrypting
-    originally textual data with <function>pgp_sym_decrypt_bytea</> is fine.
-   </para>
-   <para>
-    The <parameter>options</> parameter can contain option settings,
-    as described below.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title><function>pgp_pub_encrypt()</function></title>
-
-<synopsis>
-pgp_pub_encrypt(data text, key bytea [, options text ]) returns bytea
-pgp_pub_encrypt_bytea(data bytea, key bytea [, options text ]) returns bytea
-</synopsis>
-&common;
-   <para>
-    Encrypt <parameter>data</> with a public PGP key <parameter>key</>.
-    Giving this function a secret key will produce a error.
-   </para>
-   <para>
-    The <parameter>options</> parameter can contain option settings,
-    as described below.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title><function>pgp_pub_decrypt()</function></title>
-
-<synopsis>
-pgp_pub_decrypt(msg bytea, key bytea [, psw text [, options text ]]) returns text
-pgp_pub_decrypt_bytea(msg bytea, key bytea [, psw text [, options text ]]) returns bytea
-</synopsis>
-&common;
-   <para>
-    Decrypt a public-key-encrypted message.  <parameter>key</> must be the
-    secret key corresponding to the public key that was used to encrypt.
-    If the secret key is password-protected, you must give the password in
-    <parameter>psw</>.  If there is no password, but you want to specify
-    options, you need to give an empty password.
-   </para>
-   <para>
-    Decrypting <type>bytea</> data with <function>pgp_pub_decrypt</> is disallowed.
-    This is to avoid outputting invalid character data.  Decrypting
-    originally textual data with <function>pgp_pub_decrypt_bytea</> is fine.
-   </para>
-   <para>
-    The <parameter>options</> parameter can contain option settings,
-    as described below.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title><function>pgp_key_id()</function></title>
-
-<synopsis>
-pgp_key_id(bytea) returns text
-</synopsis>
-&common;
-   <para>
-    <function>pgp_key_id</> extracts the key ID of a PGP public or secret key.
-    Or it gives the key ID that was used for encrypting the data, if given
-    an encrypted message.
-   </para>
-   <para>
-    It can return 2 special key IDs:
-   </para>
-   <itemizedlist>
-    <listitem>
-     <para>
-      <literal>SYMKEY</>
-     </para>
-     <para>
-      The message is encrypted with a symmetric key.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>ANYKEY</>
-     </para>
-     <para>
-      The message is public-key encrypted, but the key ID has been removed.
-      That means you will need to try all your secret keys on it to see
-      which one decrypts it.  <filename>pgcrypto</> itself does not produce
-      such messages.
-     </para>
-    </listitem>
-   </itemizedlist>
-   <para>
-    Note that different keys may have the same ID.   This is rare but a normal
-    event. The client application should then try to decrypt with each one,
-    to see which fits &mdash; like handling <literal>ANYKEY</>.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title><function>armor()</function>, <function>dearmor()</function></title>
-
-<synopsis>
-armor(data bytea) returns text
-dearmor(data text) returns bytea
-</synopsis>
-&common;
-   <para>
-    These functions wrap/unwrap binary data into PGP ASCII-armor format,
-    which is basically Base64 with CRC and additional formatting.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title>Options for PGP Functions</title>
-
-&common;
-   <para>
-    Options are named to be similar to GnuPG.  An option's value should be
-    given after an equal sign; separate options from each other with commas.
-    For example:
-<programlisting>
-pgp_sym_encrypt(data, psw, 'compress-algo=1, cipher-algo=aes256')
-</programlisting>
-   </para>
-
-   <para>
-    All of the options except <literal>convert-crlf</literal> apply only to
-    encrypt functions.  Decrypt functions get the parameters from the PGP
-    data.
-   </para>
-
-   <para>
-    The most interesting options are probably
-    <literal>compress-algo</literal> and <literal>unicode-mode</literal>.
-    The rest should have reasonable defaults.
-   </para>
-
-  <sect4>
-   <title>cipher-algo</title>
-
-&common;
-   <para>
-    Which cipher algorithm to use.
-   </para>
-<literallayout>
-Values: bf, aes128, aes192, aes256 (OpenSSL-only: <literal>3des</literal>, <literal>cast5</literal>)
-Default: aes128
-Applies to: pgp_sym_encrypt, pgp_pub_encrypt
-</literallayout>
-  </sect4>
-
-  <sect4>
-   <title>compress-algo</title>
-
-&common;
-   <para>
-    Which compression algorithm to use.  Only available if
-    <productname>PostgreSQL</productname> was built with zlib.
-   </para>
-<literallayout>
-Values:
-  0 - no compression
-  1 - ZIP compression
-  2 - ZLIB compression (= ZIP plus meta-data and block CRCs)
-Default: 0
-Applies to: pgp_sym_encrypt, pgp_pub_encrypt
-</literallayout>
-  </sect4>
-
-  <sect4>
-   <title>compress-level</title>
-
-&common;
-   <para>
-    How much to compress.  Higher levels compress smaller but are slower.
-    0 disables compression.
-   </para>
-<literallayout>
-Values: 0, 1-9
-Default: 6
-Applies to: pgp_sym_encrypt, pgp_pub_encrypt
-</literallayout>
-  </sect4>
-
-  <sect4>
-   <title>convert-crlf</title>
-
-&common;
-   <para>
-    Whether to convert <literal>\n</literal> into <literal>\r\n</literal> when
-    encrypting and <literal>\r\n</literal> to <literal>\n</literal> when
-    decrypting.  RFC 4880 specifies that text data should be stored using
-    <literal>\r\n</literal> line-feeds.  Use this to get fully RFC-compliant
-    behavior.
-   </para>
-<literallayout>
-Values: 0, 1
-Default: 0
-Applies to: pgp_sym_encrypt, pgp_pub_encrypt, pgp_sym_decrypt, pgp_pub_decrypt
-</literallayout>
-  </sect4>
-
-  <sect4>
-   <title>disable-mdc</title>
-
-&common;
-   <para>
-    Do not protect data with SHA-1.  The only good reason to use this
-    option is to achieve compatibility with ancient PGP products, predating
-    the addition of SHA-1 protected packets to RFC 4880.
-    Recent gnupg.org and pgp.com software supports it fine.
-   </para>
-<literallayout>
-Values: 0, 1
-Default: 0
-Applies to: pgp_sym_encrypt, pgp_pub_encrypt
-</literallayout>
-  </sect4>
-
-  <sect4>
-   <title>enable-session-key</title>
-
-&common;
-   <para>
-    Use separate session key.  Public-key encryption always uses a separate
-    session key; this is for symmetric-key encryption, which by default
-    uses the S2K key directly.
-   </para>
-<literallayout>
-Values: 0, 1
-Default: 0
-Applies to: pgp_sym_encrypt
-</literallayout>
-  </sect4>
-
-  <sect4>
-   <title>s2k-mode</title>
-
-&common;
-   <para>
-    Which S2K algorithm to use.
-   </para>
-<literallayout>
-Values:
-  0 - Without salt.  Dangerous!
-  1 - With salt but with fixed iteration count.
-  3 - Variable iteration count.
-Default: 3
-Applies to: pgp_sym_encrypt
-</literallayout>
-  </sect4>
-
-  <sect4>
-   <title>s2k-digest-algo</title>
-
-&common;
-   <para>
-    Which digest algorithm to use in S2K calculation.
-   </para>
-<literallayout>
-Values: md5, sha1
-Default: sha1
-Applies to: pgp_sym_encrypt
-</literallayout>
-  </sect4>
-
-  <sect4>
-   <title>s2k-cipher-algo</title>
-
-&common;
-   <para>
-    Which cipher to use for encrypting separate session key.
-   </para>
-<literallayout>
-Values: bf, aes, aes128, aes192, aes256
-Default: use cipher-algo
-Applies to: pgp_sym_encrypt
-</literallayout>
-  </sect4>
-
-  <sect4>
-   <title>unicode-mode</title>
-
-&common;
-   <para>
-    Whether to convert textual data from database internal encoding to
-    UTF-8 and back.  If your database already is UTF-8, no conversion will
-    be done, but the message will be tagged as UTF-8.  Without this option
-    it will not be.
-   </para>
-<literallayout>
-Values: 0, 1
-Default: 0
-Applies to: pgp_sym_encrypt, pgp_pub_encrypt
-</literallayout>
-  </sect4>
-  </sect3>
-
- <sect3>
-  <title>Generating PGP Keys with GnuPG</title>
-
-&common;
-  <para>
-   To generate a new key:
-<programlisting>
-gpg --gen-key
-</programlisting>
-  </para>
-  <para>
-   The preferred key type is <quote>DSA and Elgamal</>.
-  </para>
-  <para>
-   For RSA encryption you must create either DSA or RSA sign-only key
-   as master and then add an RSA encryption subkey with
-   <literal>gpg --edit-key</literal>.
-  </para>
-  <para>
-   To list keys:
-<programlisting>
-gpg --list-secret-keys
-</programlisting>
-  </para>
-  <para>
-   To export a public key in ASCII-armor format:
-<programlisting>
-gpg -a --export KEYID > public.key
-</programlisting>
-  </para>
-  <para>
-   To export a secret key in ASCII-armor format:
-<programlisting>
-gpg -a --export-secret-keys KEYID > secret.key
-</programlisting>
-  </para>
-  <para>
-   You need to use <function>dearmor()</> on these keys before giving them to
-   the PGP functions.  Or if you can handle binary data, you can drop
-   <literal>-a</literal> from the command.
-  </para>
-  <para>
-   For more details see <literal>man gpg</literal>,
-   <ulink url="http://www.gnupg.org/gph/en/manual.html">The GNU
-   Privacy Handbook</ulink> and other documentation on
-   <ulink url="http://www.gnupg.org"></ulink>.
-  </para>
- </sect3>
-
- <sect3>
-  <title>Limitations of PGP Code</title>
-
-&common;
-  <itemizedlist>
-   <listitem>
-    <para>
-    No support for signing.  That also means that it is not checked
-    whether the encryption subkey belongs to the master key.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-    No support for encryption key as master key.  As such practice
-    is generally discouraged, this should not be a problem.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-    No support for several subkeys.  This may seem like a problem, as this
-    is common practice.  On the other hand, you should not use your regular
-    GPG/PGP keys with <filename>pgcrypto</>, but create new ones,
-    as the usage scenario is rather different.
-    </para>
-   </listitem>
-  </itemizedlist>
-  </sect3>
- </sect2>
-
- <sect2>
-  <title>Raw Encryption Functions</title>
-
-&common;
-  <para>
-   These functions only run a cipher over data; they don't have any advanced
-   features of PGP encryption.  Therefore they have some major problems:
-  </para>
-  <orderedlist>
-   <listitem>
-    <para>
-    They use user key directly as cipher key.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-    They don't provide any integrity checking, to see
-    if the encrypted data was modified.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-    They expect that users manage all encryption parameters
-    themselves, even IV.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-    They don't handle text.
-    </para>
-   </listitem>
-  </orderedlist>
-  <para>
-   So, with the introduction of PGP encryption, usage of raw
-   encryption functions is discouraged.
-  </para>
-
-<synopsis>
-encrypt(data bytea, key bytea, type text) returns bytea
-decrypt(data bytea, key bytea, type text) returns bytea
-
-encrypt_iv(data bytea, key bytea, iv bytea, type text) returns bytea
-decrypt_iv(data bytea, key bytea, iv bytea, type text) returns bytea
-</synopsis>
-
-  <para>
-   Encrypt/decrypt data using the cipher method specified by
-   <parameter>type</parameter>.  The syntax of the
-   <parameter>type</parameter> string is:
-
-<synopsis>
-<replaceable>algorithm</> <optional> <literal>-</> <replaceable>mode</> </optional> <optional> <literal>/pad:</> <replaceable>padding</> </optional>
-</synopsis>
-   where <replaceable>algorithm</> is one of:
-
-  <itemizedlist>
-   <listitem><para><literal>bf</literal> &mdash; Blowfish</para></listitem>
-   <listitem><para><literal>aes</literal> &mdash; AES (Rijndael-128)</para></listitem>
-  </itemizedlist>
-   and <replaceable>mode</> is one of:
-  <itemizedlist>
-   <listitem>
-    <para>
-    <literal>cbc</literal> &mdash; next block depends on previous (default)
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-    <literal>ecb</literal> &mdash; each block is encrypted separately (for
-    testing only)
-    </para>
-   </listitem>
-  </itemizedlist>
-   and <replaceable>padding</> is one of:
-  <itemizedlist>
-   <listitem>
-    <para>
-    <literal>pkcs</literal> &mdash; data may be any length (default)
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-    <literal>none</literal> &mdash; data must be multiple of cipher block size
-    </para>
-   </listitem>
-  </itemizedlist>
-  </para>
-  <para>
-   So, for example, these are equivalent:
-<programlisting>
-encrypt(data, 'fooz', 'bf')
-encrypt(data, 'fooz', 'bf-cbc/pad:pkcs')
-</programlisting>
-  </para>
-  <para>
-   In <function>encrypt_iv</> and <function>decrypt_iv</>, the
-   <parameter>iv</> parameter is the initial value for the CBC mode;
-   it is ignored for ECB.
-   It is clipped or padded with zeroes if not exactly block size.
-   It defaults to all zeroes in the functions without this parameter.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Random-Data Functions</title>
-
-<synopsis>
-gen_random_bytes(count integer) returns bytea
-</synopsis>
-&common;
-  <para>
-   Returns <parameter>count</> cryptographically strong random bytes.
-   At most 1024 bytes can be extracted at a time.  This is to avoid
-   draining the randomness generator pool.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Notes</title>
-
-  <sect3>
-   <title>Configuration</title>
-
-&common;
-   <para>
-    <filename>pgcrypto</> configures itself according to the findings of the
-    main PostgreSQL <literal>configure</literal> script.  The options that
-    affect it are <literal>--with-zlib</literal> and
-    <literal>--with-openssl</literal>.
-   </para>
-
-   <para>
-    When compiled with zlib, PGP encryption functions are able to
-    compress data before encrypting.
-   </para>
-
-   <para>
-    When compiled with OpenSSL, there will be more algorithms available.
-    Also public-key encryption functions will be faster as OpenSSL
-    has more optimized BIGNUM functions.
-   </para>
-
-   <table id="pgcrypto-with-without-openssl">
-    <title>Summary of Functionality with and without OpenSSL</title>
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Functionality</entry>
-       <entry>Built-in</entry>
-       <entry>With OpenSSL</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>MD5</entry>
-       <entry>yes</entry>
-       <entry>yes</entry>
-      </row>
-      <row>
-       <entry>SHA1</entry>
-       <entry>yes</entry>
-       <entry>yes</entry>
-      </row>
-      <row>
-       <entry>SHA224/256/384/512</entry>
-       <entry>yes</entry>
-       <entry>yes (Note 1)</entry>
-      </row>
-      <row>
-       <entry>Other digest algorithms</entry>
-       <entry>no</entry>
-       <entry>yes (Note 2)</entry>
-      </row>
-      <row>
-       <entry>Blowfish</entry>
-       <entry>yes</entry>
-       <entry>yes</entry>
-      </row>
-      <row>
-       <entry>AES</entry>
-       <entry>yes</entry>
-       <entry>yes (Note 3)</entry>
-      </row>
-      <row>
-       <entry>DES/3DES/CAST5</entry>
-       <entry>no</entry>
-       <entry>yes</entry>
-      </row>
-      <row>
-       <entry>Raw encryption</entry>
-       <entry>yes</entry>
-       <entry>yes</entry>
-      </row>
-      <row>
-       <entry>PGP Symmetric encryption</entry>
-       <entry>yes</entry>
-       <entry>yes</entry>
-      </row>
-      <row>
-       <entry>PGP Public-Key encryption</entry>
-       <entry>yes</entry>
-       <entry>yes</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    Notes:
-   </para>
-
-   <orderedlist>
-    <listitem>
-     <para>
-      SHA2 algorithms were added to OpenSSL in version 0.9.8.  For
-      older versions, <filename>pgcrypto</> will use built-in code.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Any digest algorithm OpenSSL supports is automatically picked up.
-      This is not possible with ciphers, which need to be supported
-      explicitly.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      AES is included in OpenSSL since version 0.9.7.  For
-      older versions, <filename>pgcrypto</> will use built-in code.
-     </para>
-    </listitem>
-   </orderedlist>
-  </sect3>
-
-  <sect3>
-   <title>NULL Handling</title>
-
-&common;
-   <para>
-    As is standard in SQL, all functions return NULL, if any of the arguments
-    are NULL.  This may create security risks on careless usage.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title>Security Limitations</title>
-
-&common;
-   <para>
-    All <filename>pgcrypto</> functions run inside the database server.
-    That means that all
-    the data and passwords move between <filename>pgcrypto</> and client
-    applications in clear text.  Thus you must:
-   </para>
-
-   <orderedlist>
-    <listitem>
-     <para>Connect locally or use SSL connections.</para>
-    </listitem>
-    <listitem>
-     <para>Trust both system and database administrator.</para>
-    </listitem>
-   </orderedlist>
-
-   <para>
-    If you cannot, then better do crypto inside client application.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title>Useful Reading</title>
-
-&common;
-   <itemizedlist>
-    <listitem>
-     <para><ulink url="http://www.gnupg.org/gph/en/manual.html"></ulink></para>
-     <para>The GNU Privacy Handbook.</para>
-    </listitem>
-    <listitem>
-     <para><ulink url="http://www.openwall.com/crypt/"></ulink></para>
-     <para>Describes the crypt-blowfish algorithm.</para>
-    </listitem>
-    <listitem>
-     <para>
-      <ulink url="http://www.stack.nl/~galactus/remailers/passphrase-faq.html"></ulink>
-     </para>
-     <para>How to choose a good password.</para>
-    </listitem>
-    <listitem>
-     <para><ulink url="http://world.std.com/~reinhold/diceware.html"></ulink></para>
-     <para>Interesting idea for picking passwords.</para>
-    </listitem>
-    <listitem>
-     <para>
-      <ulink url="http://www.interhack.net/people/cmcurtin/snake-oil-faq.html"></ulink>
-     </para>
-     <para>Describes good and bad cryptography.</para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Technical References</title>
-
-&common;
-   <itemizedlist>
-    <listitem>
-     <para><ulink url="http://www.ietf.org/rfc/rfc4880.txt"></ulink></para>
-     <para>OpenPGP message format.</para>
-    </listitem>
-    <listitem>
-     <para><ulink url="http://www.ietf.org/rfc/rfc1321.txt"></ulink></para>
-     <para>The MD5 Message-Digest Algorithm.</para>
-    </listitem>
-    <listitem>
-     <para><ulink url="http://www.ietf.org/rfc/rfc2104.txt"></ulink></para>
-     <para>HMAC: Keyed-Hashing for Message Authentication.</para>
-    </listitem>
-    <listitem>
-     <para>
-      <ulink url="http://www.usenix.org/events/usenix99/provos.html"></ulink>
-     </para>
-     <para>Comparison of crypt-des, crypt-md5 and bcrypt algorithms.</para>
-    </listitem>
-    <listitem>
-     <para><ulink url="http://csrc.nist.gov/cryptval/des.htm"></ulink></para>
-     <para>Standards for DES, 3DES and AES.</para>
-    </listitem>
-    <listitem>
-     <para>
-      <ulink url="http://en.wikipedia.org/wiki/Fortuna_(PRNG)"></ulink>
-     </para>
-     <para>Description of Fortuna CSPRNG.</para>
-    </listitem>
-    <listitem>
-     <para><ulink url="http://jlcooke.ca/random/"></ulink></para>
-     <para>Jean-Luc Cooke Fortuna-based <filename>/dev/random</> driver for Linux.</para>
-    </listitem>
-    <listitem>
-     <para><ulink url="http://research.cyber.ee/~lipmaa/crypto/"></ulink></para>
-     <para>Collection of cryptology pointers.</para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-&common;
-  <para>
-   Marko Kreen <email>[email protected]</email>
-  </para>
-
-  <para>
-   <filename>pgcrypto</filename> uses code from the following sources:
-  </para>
-
-  <informaltable>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Algorithm</entry>
-      <entry>Author</entry>
-      <entry>Source origin</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry>DES crypt</entry>
-      <entry>David Burren and others</entry>
-      <entry>FreeBSD libcrypt</entry>
-     </row>
-     <row>
-      <entry>MD5 crypt</entry>
-      <entry>Poul-Henning Kamp</entry>
-      <entry>FreeBSD libcrypt</entry>
-     </row>
-     <row>
-      <entry>Blowfish crypt</entry>
-      <entry>Solar Designer</entry>
-      <entry>www.openwall.com</entry>
-     </row>
-     <row>
-      <entry>Blowfish cipher</entry>
-      <entry>Simon Tatham</entry>
-      <entry>PuTTY</entry>
-     </row>
-     <row>
-      <entry>Rijndael cipher</entry>
-      <entry>Brian Gladman</entry>
-      <entry>OpenBSD sys/crypto</entry>
-     </row>
-     <row>
-      <entry>MD5 and SHA1</entry>
-      <entry>WIDE Project</entry>
-      <entry>KAME kame/sys/crypto</entry>
-     </row>
-     <row>
-      <entry>SHA256/384/512 </entry>
-      <entry>Aaron D. Gifford</entry>
-      <entry>OpenBSD sys/crypto</entry>
-     </row>
-     <row>
-      <entry>BIGNUM math</entry>
-      <entry>Michael J. Fromberger</entry>
-      <entry>dartmouth.edu/~sting/sw/imath</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </informaltable>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgfreespacemap.sgmlin b/doc-xc/src/sgml/pgfreespacemap.sgmlin
deleted file mode 100644
index b8209e989f..0000000000
--- a/doc-xc/src/sgml/pgfreespacemap.sgmlin
+++ /dev/null
@@ -1,146 +0,0 @@
-<!-- doc/src/sgml/pgfreespacemap.sgml -->
-
-<sect1 id="pgfreespacemap" xreflabel="pg_freespacemap">
- <title>pg_freespacemap</title>
-
- <indexterm zone="pgfreespacemap">
-  <primary>pg_freespacemap</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>pg_freespacemap</> module provides a means for examining the
-  free space map (FSM). It provides a function called
-  <function>pg_freespace</function>, or two overloaded functions, to be
-  precise. The functions show the value recorded in the free space map for
-  a given page, or for all pages in the relation.
- </para>
-
- <para>
-  By default public access is revoked from the functions, just in case
-  there are security issues lurking.
- </para>
-
-
-<!## XC>
-&xconly; 
- <para>
-  Functions of this module returns information about connecting
-  Coordinators locally.  To get information of a Datanode, you can
-  connect to the Datanode using psql directly.  In this case,
-  statements will be handled by local transaction control without GTM,
-  you will have warnings and the visibility could be somewhat
-  inconsistent.
- </para>
-<!## end>
-<!## XL>
-&xlonly; 
- <para>
-  Functions of this module return information from the 
-  Coordinator that the session is currently connect to.  
-  To get information about a Datanode, you can
-  use <command>EXECUTE DIRECT</command>.
- </para>
-<!## end>
-
- <sect2>
-  <title>Functions</title>
-
-  <variablelist>
-   <varlistentry>
-    <term>
-     <function>pg_freespace(rel regclass IN, blkno bigint IN) returns int2</function>
-    </term>
-
-    <listitem>
-&common;
-     <para>
-      Returns the amount of free space on the page of the relation, specified
-      by <literal>blkno</>, according to the FSM.
-     </para>
-    </listitem>
-   </varlistentry>
-
-
-   <varlistentry>
-    <term>
-     <function>pg_freespace(rel regclass IN, blkno OUT bigint, avail OUT int2)</function>
-    </term>
-
-    <listitem>
-     <para>
-      Displays the amount of free space on each page of the relation,
-      according to the FSM. A set of <literal>(blkno bigint, avail int2)</>
-      tuples is returned, one tuple for each page in the relation.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   The values stored in the free space map are not exact. They're rounded
-   to precision of 1/256th of <symbol>BLCKSZ</> (32 bytes with default <symbol>BLCKSZ</>), and
-   they're not kept fully up-to-date as tuples are inserted and updated.
-  </para>
-
-  <para>
-   For indexes, what is tracked is entirely-unused pages, rather than free
-   space within pages.  Therefore, the values are not meaningful, just
-   whether a page is full or empty.
-  </para>
-
-  <para>
-   NOTE: The interface was changed in version 8.4, to reflect the new FSM
-   implementation introduced in the same version.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Sample Output</title>
-
-<screen>
-postgres=# SELECT * FROM pg_freespace('foo');
- blkno | avail 
--------+-------
-     0 |     0
-     1 |     0
-     2 |     0
-     3 |    32
-     4 |   704
-     5 |   704
-     6 |   704
-     7 |  1216
-     8 |   704
-     9 |   704
-    10 |   704
-    11 |   704
-    12 |   704
-    13 |   704
-    14 |   704
-    15 |   704
-    16 |   704
-    17 |   704
-    18 |   704
-    19 |  3648
-(20 rows)
-
-postgres=# SELECT * FROM pg_freespace('foo', 7);
- pg_freespace 
---------------
-         1216
-(1 row)
-</screen>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Original version by Mark Kirkwood <email>[email protected]</email>.
-   Rewritten in version 8.4 to suit new FSM implementation by Heikki
-   Linnakangas <email>[email protected]</email>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgnotice.sgmlin b/doc-xc/src/sgml/pgnotice.sgmlin
deleted file mode 100644
index 263b8196d3..0000000000
--- a/doc-xc/src/sgml/pgnotice.sgmlin
+++ /dev/null
@@ -1,16 +0,0 @@
-<!## XC>
-<note>
-<para>
-At present, this section is just taken from PostgreSQL documentation
-and is subject to revision for Postgres-XC.
-</para>
-</note>
-<!## end>
-<!## XL>
-<note>
-<para>
-At present, this section is just taken from PostgreSQL documentation
-and is subject to revision for Postgres-XL.
-</para>
-</note>
-<!## end>
diff --git a/doc-xc/src/sgml/pgonly.sgmlin b/doc-xc/src/sgml/pgonly.sgmlin
deleted file mode 100644
index 302bb0383b..0000000000
--- a/doc-xc/src/sgml/pgonly.sgmlin
+++ /dev/null
@@ -1,14 +0,0 @@
-<!## XC>
-<note>
-<para>
-The following description applies only to <productname>PostgreSQL</>
-</para>
-</note>
-<!## end>
-<!## XL>
-<note>
-<para>
-The following description applies only to <productname>PostgreSQL</>
-</para>
-</note>
-<!## end>
diff --git a/doc-xc/src/sgml/pgrowlocks.sgmlin b/doc-xc/src/sgml/pgrowlocks.sgmlin
deleted file mode 100644
index 4f11a4a321..0000000000
--- a/doc-xc/src/sgml/pgrowlocks.sgmlin
+++ /dev/null
@@ -1,161 +0,0 @@
-<!-- doc/src/sgml/pgrowlocks.sgml -->
-
-<sect1 id="pgrowlocks" xreflabel="pgrowlocks">
- <title>pgrowlocks</title>
-
- <indexterm zone="pgrowlocks">
-  <primary>pgrowlocks</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>pgrowlocks</filename> module provides a function to show row
-  locking information for a specified table.
- </para>
-
-<!## XC>
-&xconly; 
- <para>
-  Functions of this module returns information about connecting
-  Coordinators locally.  To get information of a Datanode, you can
-  connect to the Datanode using psql directly.  In this case,
-  statements will be handled by local transaction control without GTM,
-  you will have warnings and the visibility could be somewhat
-  inconsistent.
- </para>
-<!## end>
-<!## XL>
-&xlonly; 
- <para>
-  Functions of this module return information from the 
-  Coordinator that the session is currently connect to.  
-  To get information about a Datanode, you can
-  use <command>EXECUTE DIRECT</command>.
- </para>
-<!## end>
-
- <sect2>
-  <title>Overview</title>
-
-<synopsis>
-pgrowlocks(text) returns setof record
-</synopsis>
-
-&common;
-  <para>
-   The parameter is the name of a table.  The result is a set of records,
-   with one row for each locked row within the table.  The output columns
-   are shown in <xref linkend="pgrowlocks-columns">.
-  </para>
-
-  <table id="pgrowlocks-columns">
-   <title><function>pgrowlocks</> Output Columns</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-
-     <row>
-      <entry><structfield>locked_row</structfield></entry>
-      <entry><type>tid</type></entry>
-      <entry>Tuple ID (TID) of locked row</entry>
-     </row>
-     <row>
-      <entry><structfield>lock_type</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry><literal>Shared</> for shared lock, or
-             <literal>Exclusive</> for exclusive lock</entry>
-     </row>
-     <row>
-      <entry><structfield>locker</structfield></entry>
-      <entry><type>xid</type></entry>
-      <entry>Transaction ID of locker, or multixact ID if multi-transaction</entry>
-     </row>
-     <row>
-      <entry><structfield>multi</structfield></entry>
-      <entry><type>boolean</type></entry>
-      <entry>True if locker is a multi-transaction</entry>
-     </row>
-     <row>
-      <entry><structfield>xids</structfield></entry>
-      <entry><type>xid[]</type></entry>
-      <entry>Transaction IDs of lockers (more than one if multi-transaction)</entry>
-     </row>
-     <row>
-      <entry><structfield>pids</structfield></entry>
-      <entry><type>integer[]</type></entry>
-      <entry>Process IDs of locking backends (more than one if multi-transaction)</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   <function>pgrowlocks</function> takes <literal>AccessShareLock</> for the
-   target table and reads each row one by one to collect the row locking
-   information.  This is not very speedy for a large table.  Note that:
-  </para>
-
-  <orderedlist>
-   <listitem>
-    <para>
-    If the table as a whole is exclusive-locked by someone else,
-    <function>pgrowlocks</function> will be blocked.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>pgrowlocks</function> is not guaranteed to produce a
-     self-consistent snapshot.  It is possible that a new row lock is taken,
-     or an old lock is freed, during its execution.
-    </para>
-   </listitem>
-  </orderedlist>
-
-  <para>
-   <function>pgrowlocks</function> does not show the contents of locked
-   rows. If you want to take a look at the row contents at the same time, you
-   could do something like this:
-
-<programlisting>
-SELECT * FROM accounts AS a, pgrowlocks('accounts') AS p
-  WHERE p.locked_row = a.ctid;
-</programlisting>
-
-   Be aware however that (as of <productname>PostgreSQL</> 8.3) such a
-   query will be very inefficient.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Sample Output</title>
-
-<screen>
-test=# SELECT * FROM pgrowlocks('t1');
- locked_row | lock_type | locker | multi |   xids    |     pids
-------------+-----------+--------+-------+-----------+---------------
-      (0,1) | Shared    |     19 | t     | {804,805} | {29066,29068}
-      (0,2) | Shared    |     19 | t     | {804,805} | {29066,29068}
-      (0,3) | Exclusive |    804 | f     | {804}     | {29066}
-      (0,4) | Exclusive |    804 | f     | {804}     | {29066}
-(4 rows)
-</screen>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Tatsuo Ishii
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgstandby.sgmlin b/doc-xc/src/sgml/pgstandby.sgmlin
deleted file mode 100644
index 4f86f5b487..0000000000
--- a/doc-xc/src/sgml/pgstandby.sgmlin
+++ /dev/null
@@ -1,403 +0,0 @@
-<!-- doc/src/sgml/pgstandby.sgml -->
-
-<sect1 id="pgstandby" xreflabel="pg_standby">
- <title>pg_standby</title>
-
- <indexterm zone="pgstandby">
-  <primary>pg_standby</primary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  <application>pg_standby</> supports creation of a <quote>warm standby</>
-  database server.  It is designed to be a production-ready program, as well
-  as a customizable template should you require specific modifications.
- </para>
-
- <para>
-  <application>pg_standby</> is designed to be a waiting
-  <varname>restore_command</>, which is needed to turn a standard
-  archive recovery into a warm standby operation.  Other
-  configuration is required as well, all of which is described in the main
-<!## PG>
-  server manual (see <xref linkend="warm-standby">).
-<!## end>
-<!## XC>
-  server manual.
-<!## end>
-<!## XL>
-  server manual.
-<!## end>
- </para>
-
- <para>
-  <application>pg_standby</application> features include:
- </para>
- <itemizedlist>
-  <listitem>
-   <para>
-    Written in C, so very portable and easy to install
-   </para>
-  </listitem>
-  <listitem>
-   <para>
-    Easy-to-modify source code, with specifically designated
-    sections to modify for your own needs
-   </para>
-  </listitem>
-  <listitem>
-   <para>
-    Already tested on Linux and Windows
-   </para>
-  </listitem>
- </itemizedlist>
-
- <sect2>
-  <title>Usage</title>
-
-&pgnotice;
-  <para>
-   To configure a standby
-   server to use <application>pg_standby</>, put this into its
-   <filename>recovery.conf</filename> configuration file:
-<programlisting>
-restore_command = 'pg_standby <replaceable>archiveDir</> %f %p %r'
-</programlisting>
-   where <replaceable>archiveDir</> is the directory from which WAL segment
-   files should be restored.
-  </para>
-  <para>
-   The full syntax of <application>pg_standby</>'s command line is
-<synopsis>
-pg_standby <optional> <replaceable>option</> ... </optional> <replaceable>archivelocation</> <replaceable>nextwalfile</> <replaceable>xlogfilepath</> <optional> <replaceable>restartwalfile</> </optional>
-</synopsis>
-   When used within <varname>restore_command</>, the <literal>%f</> and
-   <literal>%p</> macros should be specified for <replaceable>nextwalfile</>
-   and <replaceable>xlogfilepath</> respectively, to provide the actual file
-   and path required for the restore.
-  </para>
-  <para>
-   If <replaceable>restartwalfile</> is specified, normally by using the
-   <literal>%r</literal> macro, then all WAL files logically preceding this
-   file will be removed from <replaceable>archivelocation</>. This minimizes
-   the number of files that need to be retained, while preserving
-   crash-restart capability.  Use of this parameter is appropriate if the
-   <replaceable>archivelocation</> is a transient staging area for this
-   particular standby server, but <emphasis>not</> when the
-   <replaceable>archivelocation</> is intended as a long-term WAL archive area.
-  </para>
-  <para>
-   <application>pg_standby</application> assumes that
-   <replaceable>archivelocation</> is a directory readable by the
-   server-owning user.  If <replaceable>restartwalfile</> (or <literal>-k</>)
-   is specified,
-   the <replaceable>archivelocation</> directory must be writable too.
-  </para>
-  <para>
-   There are two ways to fail over to a <quote>warm standby</> database server
-   when the master server fails:
-
-   <variablelist>
-    <varlistentry>
-     <term>Smart Failover</term>
-     <listitem>
-      <para>
-       In smart failover, the server is brought up after applying all WAL
-       files available in the archive. This results in zero data loss, even if
-       the standby server has fallen behind, but if there is a lot of
-       unapplied WAL it can be a long time before the standby server becomes
-       ready. To trigger a smart failover, create a trigger file containing
-       the word <literal>smart</>, or just create it and leave it empty.
-      </para>
-     </listitem>
-    </varlistentry>
-    <varlistentry>
-     <term>Fast Failover</term>
-     <listitem>
-      <para>
-       In fast failover, the server is brought up immediately. Any WAL files
-       in the archive that have not yet been applied will be ignored, and
-       all transactions in those files are lost. To trigger a fast failover,
-       create a trigger file and write the word <literal>fast</> into it.
-       <application>pg_standby</> can also be configured to execute a fast
-       failover automatically if no new WAL file appears within a defined
-       interval.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
- </sect2>
-
- <sect2>
-  <title><application>pg_standby</> Options</title>
-
-&pgnotice;
-   <para>
-    <application>pg_standby</application> accepts the following command-line arguments:
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>-c</option></term>
-      <listitem>
-       <para>
-        Use <literal>cp</> or <literal>copy</> command to restore WAL files
-        from archive.  This is the only supported behavior so this option is useless.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-d</option></term>
-      <listitem>
-       <para>
-        Print lots of debug logging output on <filename>stderr</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-k</option></term>
-      <listitem>
-       <para>
-        Remove files from <replaceable>archivelocation</replaceable> so that
-        no more than this many WAL files before the current one are kept in the
-        archive.  Zero (the default) means not to remove any files from
-        <replaceable>archivelocation</replaceable>.
-        This parameter will be silently ignored if
-        <replaceable>restartwalfile</replaceable> is specified, since that
-        specification method is more accurate in determining the correct
-        archive cut-off point.
-        Use of this parameter is <emphasis>deprecated</> as of
-        <productname>PostgreSQL</> 8.3; it is safer and more efficient to
-        specify a <replaceable>restartwalfile</replaceable> parameter.  A too
-        small setting could result in removal of files that are still needed
-        for a restart of the standby server, while a too large setting wastes
-        archive space.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-r</option> <replaceable>maxretries</></term>
-      <listitem>
-       <para>
-        Set the maximum number of times to retry the copy command if
-        it fails (default 3). After each failure, we wait for
-        <replaceable>sleeptime</> * <replaceable>num_retries</>
-        so that the wait time increases progressively.  So by default,
-        we will wait 5 secs, 10 secs, then 15 secs before reporting
-        the failure back to the standby server. This will be
-        interpreted as end of recovery and the standby will come
-        up fully as a result.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option> <replaceable>sleeptime</></term>
-      <listitem>
-       <para>
-        Set the number of seconds (up to 60, default 5) to sleep between
-        tests to see if the WAL file to be restored is available in
-        the archive yet.  The default setting is not necessarily
-<!## PG>
-        recommended; consult <xref linkend="warm-standby"> for discussion.
-<!## end>
-<!## XC>
-        recommended.
-<!## end>
-<!## XL>
-        recommended.
-<!## end>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t</option> <replaceable>triggerfile</></term>
-      <listitem>
-       <para>
-        Specify a trigger file whose presence should cause failover.
-        It is recommended that you use a structured file name to
-        avoid confusion as to which server is being triggered
-        when multiple servers exist on the same system; for example
-        <filename>/tmp/pgsql.trigger.5432</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</option> <replaceable>maxwaittime</></term>
-      <listitem>
-       <para>
-        Set the maximum number of seconds to wait for the next WAL file,
-        after which a fast failover will be performed.
-        A setting of zero (the default) means wait forever.
-<!## PG>
-        The default setting is not necessarily recommended;
-        consult <xref linkend="warm-standby"> for discussion.
-<!## end>
-<!## XC>
-        The default setting is not necessarily recommended.
-<!## end>
-<!## XL>
-        The default setting is not necessarily recommended.
-<!## end>
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
- </sect2>
-
- <sect2>
-  <title>Examples</title>
-
-&pgnotice;
-  <para>On Linux or Unix systems, you might use:
-
-<programlisting>
-archive_command = 'cp %p .../archive/%f'
-
-restore_command = 'pg_standby -d -s 2 -t /tmp/pgsql.trigger.5442 .../archive %f %p %r 2>>standby.log'
-
-recovery_end_command = 'rm -f /tmp/pgsql.trigger.5442'
-</programlisting>
-   where the archive directory is physically located on the standby server,
-   so that the <varname>archive_command</> is accessing it across NFS,
-   but the files are local to the standby (enabling use of <literal>ln</>).
-   This will:
-  <itemizedlist>
-   <listitem>
-    <para>
-     produce debugging output in <filename>standby.log</>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     sleep for 2 seconds between checks for next WAL file availability
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     stop waiting only when a trigger file called
-     <filename>/tmp/pgsql.trigger.5442</> appears,
-     and perform failover according to its content
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     remove the trigger file when recovery ends
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     remove no-longer-needed files from the archive directory
-    </para>
-   </listitem>
-  </itemizedlist>
-  </para>
-
-  <para>On Windows, you might use:
-
-<programlisting>
-archive_command = 'copy %p ...\\archive\\%f'
-
-restore_command = 'pg_standby -d -s 5 -t C:\pgsql.trigger.5442 ...\archive %f %p %r 2>>standby.log'
-
-recovery_end_command = 'del C:\pgsql.trigger.5442'
-</programlisting>
-   Note that backslashes need to be doubled in the
-   <varname>archive_command</>, but <emphasis>not</emphasis> in the
-   <varname>restore_command</> or <varname>recovery_end_command</>.
-   This will:
-  <itemizedlist>
-   <listitem>
-    <para>
-     use the <literal>copy</> command to restore WAL files from archive
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     produce debugging output in <filename>standby.log</>
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     sleep for 5 seconds between checks for next WAL file availability
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     stop waiting only when a trigger file called
-     <filename>C:\pgsql.trigger.5442</> appears,
-     and perform failover according to its content
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     remove the trigger file when recovery ends
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     remove no-longer-needed files from the archive directory
-    </para>
-   </listitem>
-  </itemizedlist>
-  </para>
-
-  <para>
-   The <literal>copy</> command on Windows sets the final file size
-   before the file is completely copied, which would ordinarily confuse
-   <application>pg_standby</application>.  Therefore
-   <application>pg_standby</application> waits <literal>sleeptime</>
-   seconds once it sees the proper file size.  GNUWin32's <literal>cp</>
-   sets the file size only after the file copy is complete.
-  </para>
-
-  <para>
-   Since the Windows example uses <literal>copy</> at both ends, either
-   or both servers might be accessing the archive directory across the
-   network.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>Supported Server Versions</title>
-
-&pgnotice;
-  <para>
-   <application>pg_standby</application> is designed to work with
-   <productname>PostgreSQL</> 8.2 and later.
-  </para>
-  <para>
-   <productname>PostgreSQL</> 8.3 provides the <literal>%r</literal> macro,
-   which is designed to let <application>pg_standby</application> know the
-   last file it needs to keep.  With <productname>PostgreSQL</> 8.2, the
-   <literal>-k</literal> option must be used if archive cleanup is
-   required.  This option remains available in 8.3, but its use is deprecated.
-  </para>
-  <para>
-   <productname>PostgreSQL</> 8.4 provides the
-   <varname>recovery_end_command</> option.  Without this option
-   a leftover trigger file can be hazardous.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Simon Riggs <email>[email protected]</email>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgstatstatements.sgmlin b/doc-xc/src/sgml/pgstatstatements.sgmlin
deleted file mode 100644
index c7d5614e02..0000000000
--- a/doc-xc/src/sgml/pgstatstatements.sgmlin
+++ /dev/null
@@ -1,368 +0,0 @@
-<!-- doc/src/sgml/pgstatstatements.sgml -->
-
-<sect1 id="pgstatstatements" xreflabel="pg_stat_statements">
- <title>pg_stat_statements</title>
-
- <indexterm zone="pgstatstatements">
-  <primary>pg_stat_statements</primary>
- </indexterm>
-
-<!## XC>
-&xconly;
- <para>
-  The module <filename>pg_stat_statments</filename> does not work
-  correctly with <productname>Postgres-XC</productname>.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  The module <filename>pg_stat_statments</filename> does not work
-  correctly with <productname>Postgres-XL</productname>.
- </para>
-<!## end>
-
-<!## PG>
-&pgonly;
-
- <para>
-  The <filename>pg_stat_statements</filename> module provides a means for
-  tracking execution statistics of all SQL statements executed by a server.
- </para>
-
- <para>
-  The module must be loaded by adding <literal>pg_stat_statements</> to
-  <xref linkend="guc-shared-preload-libraries"> in
-  <filename>postgresql.conf</>, because it requires additional shared memory.
-  This means that a server restart is needed to add or remove the module.
- </para>
-
- <sect2>
-  <title>The <structname>pg_stat_statements</structname> View</title>
-
-&pgonly;
-  <para>
-   The statistics gathered by the module are made available via a system view
-   named <structname>pg_stat_statements</>.  This view contains one row for
-   each distinct query text, database ID, and user ID (up to the maximum
-   number of distinct statements that the module can track).  The columns
-   of the view are shown in <xref linkend="pgstatstatements-columns">.
-  </para>
-
-  <table id="pgstatstatements-columns">
-   <title><structname>pg_stat_statements</> Columns</title>
-
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><structfield>userid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-authid"><structname>pg_authid</structname></link>.oid</literal></entry>
-      <entry>OID of user who executed the statement</entry>
-     </row>
-
-     <row>
-      <entry><structfield>dbid</structfield></entry>
-      <entry><type>oid</type></entry>
-      <entry><literal><link linkend="catalog-pg-database"><structname>pg_database</structname></link>.oid</literal></entry>
-      <entry>OID of database in which the statement was executed</entry>
-     </row>
-
-    <row>
-      <entry><structfield>query</structfield></entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Text of the statement (up to <xref linkend="guc-track-activity-query-size"> bytes)</entry>
-     </row>
-
-     <row>
-      <entry><structfield>calls</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Number of times executed</entry>
-     </row>
-
-     <row>
-      <entry><structfield>total_time</structfield></entry>
-      <entry><type>double precision</type></entry>
-      <entry></entry>
-      <entry>Total time spent in the statement, in seconds</entry>
-     </row>
-
-     <row>
-      <entry><structfield>rows</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Total number of rows retrieved or affected by the statement</entry>
-     </row>
-
-     <row>
-      <entry><structfield>shared_blks_hit</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Total number of shared blocks hits by the statement</entry>
-     </row>
-
-     <row>
-      <entry><structfield>shared_blks_read</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Total number of shared blocks reads by the statement</entry>
-     </row>
-
-     <row>
-      <entry><structfield>shared_blks_written</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Total number of shared blocks writes by the statement</entry>
-     </row>
-
-     <row>
-      <entry><structfield>local_blks_hit</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Total number of local blocks hits by the statement</entry>
-     </row>
-
-     <row>
-      <entry><structfield>local_blks_read</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Total number of local blocks reads by the statement</entry>
-     </row>
-
-     <row>
-      <entry><structfield>local_blks_written</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Total number of local blocks writes by the statement</entry>
-     </row>
-
-     <row>
-      <entry><structfield>temp_blks_read</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Total number of temp blocks reads by the statement</entry>
-     </row>
-
-     <row>
-      <entry><structfield>temp_blks_written</structfield></entry>
-      <entry><type>bigint</type></entry>
-      <entry></entry>
-      <entry>Total number of temp blocks writes by the statement</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   This view, and the function <function>pg_stat_statements_reset</>,
-   are available only in databases they have been specifically installed into
-   by installing the <literal>pg_stat_statements</> extension.
-   However, statistics are tracked across all databases of the server
-   whenever the <filename>pg_stat_statements</filename> module is loaded
-   into the server, regardless of presence of the view.
-  </para>
-
-  <para>
-   For security reasons, non-superusers are not allowed to see the text of
-   queries executed by other users.  They can see the statistics, however,
-   if the view has been installed in their database.
-  </para>
-
-  <para>
-   Note that statements are considered the same if they have the same text,
-   regardless of the values of any out-of-line parameters used in the
-   statement.  Using out-of-line parameters will help to group statements
-   together and may make the statistics more useful.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Functions</title>
-&pgonly;
-  <variablelist>
-   <varlistentry>
-    <term>
-     <function>pg_stat_statements_reset() returns void</function>
-    </term>
-
-    <listitem>
-     <para>
-      <function>pg_stat_statements_reset</function> discards all statistics
-      gathered so far by <filename>pg_stat_statements</>.
-      By default, this function can only be executed by superusers.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </sect2>
-
- <sect2>
-  <title>Configuration Parameters</title>
-
-&pgonly;
-  <variablelist>
-   <varlistentry>
-    <term>
-     <varname>pg_stat_statements.max</varname> (<type>integer</type>)
-    </term>
-
-    <listitem>
-     <para>
-      <varname>pg_stat_statements.max</varname> is the maximum number of
-      statements tracked by the module (i.e., the maximum number of rows
-      in the <structname>pg_stat_statements</> view).  If more distinct
-      statements than that are observed, information about the least-executed
-      statements is discarded.
-      The default value is 1000.
-      This parameter can only be set at server start.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <varname>pg_stat_statements.track</varname> (<type>enum</type>)
-    </term>
-
-    <listitem>
-     <para>
-      <varname>pg_stat_statements.track</varname> controls which statements
-      are counted by the module.
-      Specify <literal>top</> to track top-level statements (those issued
-      directly by clients), <literal>all</> to also track nested statements
-      (such as statements invoked within functions), or <literal>none</> to
-      disable.
-      The default value is <literal>top</>.
-      Only superusers can change this setting.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <varname>pg_stat_statements.track_utility</varname> (<type>boolean</type>)
-    </term>
-
-    <listitem>
-     <para>
-      <varname>pg_stat_statements.track_utility</varname> controls whether
-      utility commands are tracked by the module.  Utility commands are
-      all those other than <command>SELECT</>, <command>INSERT</>,
-      <command>UPDATE</> and <command>DELETE</>.
-      The default value is <literal>on</>.
-      Only superusers can change this setting.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <varname>pg_stat_statements.save</varname> (<type>boolean</type>)
-    </term>
-
-    <listitem>
-     <para>
-      <varname>pg_stat_statements.save</varname> specifies whether to
-      save statement statistics across server shutdowns.
-      If it is <literal>off</> then statistics are not saved at
-      shutdown nor reloaded at server start.
-      The default value is <literal>on</>.
-      This parameter can only be set in the <filename>postgresql.conf</>
-      file or on the server command line.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   The module requires additional shared memory amounting to about
-   <varname>pg_stat_statements.max</varname> <literal>*</>
-   <xref linkend="guc-track-activity-query-size"> bytes.  Note that this
-   memory is consumed whenever the module is loaded, even if
-   <varname>pg_stat_statements.track</> is set to <literal>none</>.
-  </para>
-
-  <para>
-   In order to set any of these parameters in your
-   <filename>postgresql.conf</> file,
-   you will need to add <literal>pg_stat_statements</> to
-   <xref linkend="guc-custom-variable-classes">.  Typical usage might be:
-
-<programlisting>
-# postgresql.conf
-shared_preload_libraries = 'pg_stat_statements'
-
-custom_variable_classes = 'pg_stat_statements'
-pg_stat_statements.max = 10000
-pg_stat_statements.track = all
-</programlisting>
-  </para>
- </sect2>
-
- <sect2>
-  <title>Sample Output</title>
-
-<screen>
-bench=# SELECT pg_stat_statements_reset();
-
-$ pgbench -i bench
-$ pgbench -c10 -t300 -M prepared bench
-
-bench=# \x
-bench=# SELECT query, calls, total_time, rows, 100.0 * shared_blks_hit /
-               nullif(shared_blks_hit + shared_blks_read, 0) AS hit_percent
-          FROM pg_stat_statements ORDER BY total_time DESC LIMIT 5;
--[ RECORD 1 ]---------------------------------------------------------------------
-query       | UPDATE pgbench_branches SET bbalance = bbalance + $1 WHERE bid = $2;
-calls       | 3000
-total_time  | 9.60900100000002
-rows        | 2836
-hit_percent | 99.9778970000200936
--[ RECORD 2 ]---------------------------------------------------------------------
-query       | UPDATE pgbench_tellers SET tbalance = tbalance + $1 WHERE tid = $2;
-calls       | 3000
-total_time  | 8.015156
-rows        | 2990
-hit_percent | 99.9731126579631345
--[ RECORD 3 ]---------------------------------------------------------------------
-query       | copy pgbench_accounts from stdin
-calls       | 1
-total_time  | 0.310624
-rows        | 100000
-hit_percent | 0.30395136778115501520
--[ RECORD 4 ]---------------------------------------------------------------------
-query       | UPDATE pgbench_accounts SET abalance = abalance + $1 WHERE aid = $2;
-calls       | 3000
-total_time  | 0.271741999999997
-rows        | 3000
-hit_percent | 93.7968855088209426
--[ RECORD 5 ]---------------------------------------------------------------------
-query       | alter table pgbench_accounts add primary key (aid)
-calls       | 1
-total_time  | 0.08142
-rows        | 0
-hit_percent | 34.4947735191637631
-</screen>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Takahiro Itagaki <email>[email protected]</email>
-  </para>
- </sect2>
-<!## end>
-</sect1>
diff --git a/doc-xc/src/sgml/pgstattuple.sgmlin b/doc-xc/src/sgml/pgstattuple.sgmlin
deleted file mode 100644
index 7f534d9436..0000000000
--- a/doc-xc/src/sgml/pgstattuple.sgmlin
+++ /dev/null
@@ -1,295 +0,0 @@
-<!-- doc/src/sgml/pgstattuple.sgml -->
-
-<sect1 id="pgstattuple" xreflabel="pgstattuple">
- <title>pgstattuple</title>
-
- <indexterm zone="pgstattuple">
-  <primary>pgstattuple</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>pgstattuple</filename> module provides various functions to
-  obtain tuple-level statistics.
- </para>
-
-<!## XC>
-&xconly; 
- <para>
-  Functions of this module returns information about connecting
-  Coordinators locally.  To get information of a Datanode, you can
-  connect to the Datanode using psql directly.  In this case,
-  statements will be handled by local transaction control without GTM,
-  you will have warnings and the visibility could be somewhat
-  inconsistent.
- </para>
-<!## end>
-<!## XL>
-&xlonly; 
- <para>
-  Functions of this module return information from the 
-  Coordinator that the session is currently connect to.  
-  To get information about a Datanode, you can
-  use <command>EXECUTE DIRECT</command>.
- </para>
-<!## end>
-
-
- <sect2>
-  <title>Functions</title>
-
-  <variablelist>
-   <varlistentry>
-    <term>
-     <function>pgstattuple(text) returns record</>
-    </term>
-
-    <listitem>
-&common;
-     <para>
-      <function>pgstattuple</function> returns a relation's physical length,
-      percentage of <quote>dead</> tuples, and other info. This may help users
-      to determine whether vacuum is necessary or not.  The argument is the
-      target relation's name (optionally schema-qualified).
-      For example:
-<programlisting>
-test=> SELECT * FROM pgstattuple('pg_catalog.pg_proc');
--[ RECORD 1 ]------+-------
-table_len          | 458752
-tuple_count        | 1470
-tuple_len          | 438896
-tuple_percent      | 95.67
-dead_tuple_count   | 11
-dead_tuple_len     | 3157
-dead_tuple_percent | 0.69
-free_space         | 8932
-free_percent       | 1.95
-</programlisting>
-     The output columns are described in <xref linkend="pgstattuple-columns">.
-    </para>
-
-    <table id="pgstattuple-columns">
-     <title><function>pgstattuple</function> Output Columns</title>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Column</entry>
-        <entry>Type</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry><structfield>table_len</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Physical relation length in bytes</entry>
-       </row>
-       <row>
-        <entry><structfield>tuple_count</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Number of live tuples</entry>
-       </row>
-       <row>
-        <entry><structfield>tuple_len</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Total length of live tuples in bytes</entry>
-       </row>
-       <row>
-        <entry><structfield>tuple_percent</structfield></entry>
-        <entry><type>float8</type></entry>
-        <entry>Percentage of live tuples</entry>
-       </row>
-       <row>
-        <entry><structfield>dead_tuple_count</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Number of dead tuples</entry>
-       </row>
-       <row>
-        <entry><structfield>dead_tuple_len</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Total length of dead tuples in bytes</entry>
-       </row>
-       <row>
-        <entry><structfield>dead_tuple_percent</structfield></entry>
-        <entry><type>float8</type></entry>
-        <entry>Percentage of dead tuples</entry>
-       </row>
-       <row>
-        <entry><structfield>free_space</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Total free space in bytes</entry>
-       </row>
-       <row>
-        <entry><structfield>free_percent</structfield></entry>
-        <entry><type>float8</type></entry>
-        <entry>Percentage of free space</entry>
-       </row>
-
-      </tbody>
-     </tgroup>
-    </table>
-
-    <para>
-     <function>pgstattuple</function> acquires only a read lock on the
-     relation. So the results do not reflect an instantaneous snapshot;
-     concurrent updates will affect them.
-    </para>
-
-    <para>
-     <function>pgstattuple</function> judges a tuple is <quote>dead</> if
-     <function>HeapTupleSatisfiesNow</> returns false.
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <function>pgstattuple(oid) returns record</>
-    </term>
-
-    <listitem>
-     <para>
-      This is the same as <function>pgstattuple(text)</function>, except
-      that the target relation is specified by OID.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <function>pgstatindex(text) returns record</>
-    </term>
-
-    <listitem>
-     <para>
-      <function>pgstatindex</function> returns a record showing information
-      about a B-tree index.  For example:
-<programlisting>
-test=> SELECT * FROM pgstatindex('pg_cast_oid_index');
--[ RECORD 1 ]------+------
-version            | 2
-tree_level         | 0
-index_size         | 8192
-root_block_no      | 1
-internal_pages     | 0
-leaf_pages         | 1
-empty_pages        | 0
-deleted_pages      | 0
-avg_leaf_density   | 50.27
-leaf_fragmentation | 0
-</programlisting>
-     </para>
-
-    <para>
-     The output columns are:
-
-    <informaltable>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Column</entry>
-        <entry>Type</entry>
-        <entry>Description</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry><structfield>version</structfield></entry>
-        <entry><type>integer</type></entry>
-        <entry>B-tree version number</entry>
-       </row>
-
-       <row>
-        <entry><structfield>tree_level</structfield></entry>
-        <entry><type>integer</type></entry>
-        <entry>Tree level of the root page</entry>
-       </row>
-
-       <row>
-        <entry><structfield>index_size</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Total number of pages in index</entry>
-       </row>
-
-       <row>
-        <entry><structfield>root_block_no</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Location of root block</entry>
-       </row>
-
-       <row>
-        <entry><structfield>internal_pages</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Number of <quote>internal</> (upper-level) pages</entry>
-       </row>
-
-       <row>
-        <entry><structfield>leaf_pages</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Number of leaf pages</entry>
-       </row>
-
-       <row>
-        <entry><structfield>empty_pages</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Number of empty pages</entry>
-       </row>
-
-       <row>
-        <entry><structfield>deleted_pages</structfield></entry>
-        <entry><type>bigint</type></entry>
-        <entry>Number of deleted pages</entry>
-       </row>
-
-       <row>
-        <entry><structfield>avg_leaf_density</structfield></entry>
-        <entry><type>float8</type></entry>
-        <entry>Average density of leaf pages</entry>
-       </row>
-
-       <row>
-        <entry><structfield>leaf_fragmentation</structfield></entry>
-        <entry><type>float8</type></entry>
-        <entry>Leaf page fragmentation</entry>
-       </row>
-
-      </tbody>
-     </tgroup>
-    </informaltable>
-    </para>
-
-    <para>
-     As with <function>pgstattuple</>, the results are accumulated
-     page-by-page, and should not be expected to represent an
-     instantaneous snapshot of the whole index.
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <function>pg_relpages(text) returns bigint</>
-    </term>
-
-    <listitem>
-     <para>
-      <function>pg_relpages</function> returns the number of pages in the
-      relation.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </sect2>
-
- <sect2>
-  <title>Authors</title>
-
-  <para>
-   Tatsuo Ishii and Satoshi Nagayasu
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgtestfsync.sgmlin b/doc-xc/src/sgml/pgtestfsync.sgmlin
deleted file mode 100644
index 2889059c82..0000000000
--- a/doc-xc/src/sgml/pgtestfsync.sgmlin
+++ /dev/null
@@ -1,74 +0,0 @@
-<!-- doc/src/sgml/pgtestfsync.sgml -->
-
-<sect1 id="pgtestfsync" xreflabel="pg_test_fsync">
- <title>pg_test_fsync</title>
-
- <indexterm zone="pgtestfsync">
-  <primary>pg_test_fsync</primary>
- </indexterm>
-
- <para>
-  <application>pg_test_fsync</> is intended to give you a reasonable
-  idea of what the fastest <xref linkend="guc-wal-sync-method"> is on your
-  specific system,
-  as well as supplying diagnostic information in the event of an
-  identified I/O problem.  However, differences shown by pg_test_fsync
-  might not make any difference in real database throughput, especially
-  since many database servers are not speed-limited by their transaction
-  logs.
- </para>
-
- <sect2>
-  <title>Usage</title>
-
-<synopsis>
-pg_test_fsync [options]
-</synopsis>
-
-   <para>
-    <application>pg_test_fsync</application> accepts the following
-    command-line options:
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>-f</option></term>
-      <term><option>--filename</option></term>
-      <listitem>
-       <para>
-        Specifies the file name to write test data in.
-        This file should be in the same file system that the
-        <filename>pg_xlog</> directory is or will be placed in.
-        (<filename>pg_xlog</> contains the <acronym>WAL</> files.)
-        The default is <filename>pg_test_fsync.out</> in the current
-        directory.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o</option></term>
-      <term><option>--ops-per-test</option></term>
-      <listitem>
-       <para>
-        Specifies the number of operations per test.  The more operations
-        per test, the greater the test's accuracy, but the longer it takes
-        to run.  The default is 2000.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Bruce Momjian <email>[email protected]</email>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgtrgm.sgmlin b/doc-xc/src/sgml/pgtrgm.sgmlin
deleted file mode 100644
index 2f1eae67fa..0000000000
--- a/doc-xc/src/sgml/pgtrgm.sgmlin
+++ /dev/null
@@ -1,297 +0,0 @@
-<!-- doc/src/sgml/pgtrgm.sgml -->
-
-<sect1 id="pgtrgm" xreflabel="pg_trgm">
- <title>pg_trgm</title>
-
- <indexterm zone="pgtrgm">
-  <primary>pg_trgm</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>pg_trgm</filename> module provides functions and operators
-  for determining the similarity of text based on trigram matching, as
-  well as index operator classes that support fast searching for similar
-  strings.
- </para>
-
- <sect2>
-  <title>Trigram (or Trigraph) Concepts</title>
-
-&common;
-  <para>
-   A trigram is a group of three consecutive characters taken
-   from a string.  We can measure the similarity of two strings by
-   counting the number of trigrams they share.  This simple idea
-   turns out to be very effective for measuring the similarity of
-   words in many natural languages.
-  </para>
-
-  <note>
-   <para>
-    A string is considered to have two spaces
-    prefixed and one space suffixed when determining the set
-    of trigrams contained in the string.
-    For example, the set of trigrams in the string
-    <quote><literal>cat</literal></quote> is
-    <quote><literal>  c</literal></quote>,
-    <quote><literal> ca</literal></quote>,
-    <quote><literal>cat</literal></quote>, and
-    <quote><literal>at </literal></quote>.
-   </para>
-  </note>
- </sect2>
-
- <sect2>
-  <title>Functions and Operators</title>
-
-  <para>
-   The functions provided by the <filename>pg_trgm</filename> module
-   are shown in <xref linkend="pgtrgm-func-table">, the operators
-   in <xref linkend="pgtrgm-op-table">.
-  </para>
-
-  <table id="pgtrgm-func-table">
-   <title><filename>pg_trgm</filename> Functions</title>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Returns</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><function>similarity(text, text)</function></entry>
-      <entry><type>real</type></entry>
-      <entry>
-       Returns a number that indicates how similar the two arguments are.
-       The range of the result is zero (indicating that the two strings are
-       completely dissimilar) to one (indicating that the two strings are
-       identical).
-      </entry>
-     </row>
-     <row>
-      <entry><function>show_trgm(text)</function></entry>
-      <entry><type>text[]</type></entry>
-      <entry>
-       Returns an array of all the trigrams in the given string.
-       (In practice this is seldom useful except for debugging.)
-      </entry>
-     </row>
-     <row>
-      <entry><function>show_limit()</function></entry>
-      <entry><type>real</type></entry>
-      <entry>
-       Returns the current similarity threshold used by the <literal>%</>
-       operator.  This sets the minimum similarity between
-       two words for them to be considered similar enough to
-       be misspellings of each other, for example.
-      </entry>
-     </row>
-     <row>
-      <entry><function>set_limit(real)</function></entry>
-      <entry><type>real</type></entry>
-      <entry>
-       Sets the current similarity threshold that is used by the <literal>%</>
-       operator.  The threshold must be between 0 and 1 (default is 0.3).
-       Returns the same value passed in.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <table id="pgtrgm-op-table">
-   <title><filename>pg_trgm</filename> Operators</title>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Operator</entry>
-      <entry>Returns</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><type>text</> <literal>%</literal> <type>text</></entry>
-      <entry><type>boolean</type></entry>
-      <entry>
-       Returns <literal>true</> if its arguments have a similarity that is
-       greater than the current similarity threshold set by
-       <function>set_limit</>.
-      </entry>
-     </row>
-     <row>
-      <entry><type>text</> <literal>&lt;-&gt;</literal> <type>text</></entry>
-      <entry><type>real</type></entry>
-      <entry>
-       Returns the <quote>distance</> between the arguments, that is
-       one minus the <function>similarity()</> value.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect2>
-
- <sect2>
-  <title>Index Support</title>
-
-&common;
-  <para>
-   The <filename>pg_trgm</filename> module provides GiST and GIN index
-   operator classes that allow you to create an index over a text column for
-   the purpose of very fast similarity searches.  These index types support
-   the above-described similarity operators, and additionally support
-   trigram-based index searches for <literal>LIKE</> and <literal>ILIKE</>
-   queries.  (These indexes do not support equality nor simple comparison
-   operators, so you may need a regular B-tree index too.)
-  </para>
-
-  <para>
-   Example:
-
-<programlisting>
-CREATE TABLE test_trgm (t text);
-CREATE INDEX trgm_idx ON test_trgm USING gist (t gist_trgm_ops);
-</programlisting>
-or
-<programlisting>
-CREATE INDEX trgm_idx ON test_trgm USING gin (t gin_trgm_ops);
-</programlisting>
-  </para>
-
-  <para>
-   At this point, you will have an index on the <structfield>t</> column that
-   you can use for similarity searching.  A typical query is
-<programlisting>
-SELECT t, similarity(t, '<replaceable>word</>') AS sml
-  FROM test_trgm
-  WHERE t % '<replaceable>word</>'
-  ORDER BY sml DESC, t;
-</programlisting>
-   This will return all values in the text column that are sufficiently
-   similar to <replaceable>word</>, sorted from best match to worst.  The
-   index will be used to make this a fast operation even over very large data
-   sets.
-  </para>
-
-  <para>
-   A variant of the above query is
-<programlisting>
-SELECT t, t &lt;-&gt; '<replaceable>word</>' AS dist
-  FROM test_trgm
-  ORDER BY dist LIMIT 10;
-</programlisting>
-   This can be implemented quite efficiently by GiST indexes, but not
-   by GIN indexes.  It will usually beat the first formulation when only
-   a small number of the closest matches is wanted.
-  </para>
-
-  <para>
-   Beginning in <productname>PostgreSQL</> 9.1, these index types also support
-   index searches for <literal>LIKE</> and <literal>ILIKE</>, for example
-<programlisting>
-SELECT * FROM test_trgm WHERE t LIKE '%foo%bar';
-</programlisting>
-   The index search works by extracting trigrams from the search string
-   and then looking these up in the index.  The more trigrams in the search
-   string, the more effective the index search is.  Unlike B-tree based
-   searches, the search string need not be left-anchored.
-  </para>
-
-  <para>
-   The choice between GiST and GIN indexing depends on the relative
-   performance characteristics of GiST and GIN, which are discussed elsewhere.
-   As a rule of thumb, a GIN index is faster to search than a GiST index, but
-   slower to build or update; so GIN is better suited for static data and GiST
-   for often-updated data.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Text Search Integration</title>
-
-&common;
-  <para>
-   Trigram matching is a very useful tool when used in conjunction
-   with a full text index.  In particular it can help to recognize
-   misspelled input words that will not be matched directly by the
-   full text search mechanism.
-  </para>
-
-  <para>
-   The first step is to generate an auxiliary table containing all
-   the unique words in the documents:
-
-<programlisting>
-CREATE TABLE words AS SELECT word FROM
-        ts_stat('SELECT to_tsvector(''simple'', bodytext) FROM documents');
-</programlisting>
-
-   where <structname>documents</> is a table that has a text field
-   <structfield>bodytext</> that we wish to search.  The reason for using
-   the <literal>simple</> configuration with the <function>to_tsvector</>
-   function, instead of using a language-specific configuration,
-   is that we want a list of the original (unstemmed) words.
-  </para>
-
-  <para>
-   Next, create a trigram index on the word column:
-
-<programlisting>
-CREATE INDEX words_idx ON words USING gin(word gin_trgm_ops);
-</programlisting>
-
-   Now, a <command>SELECT</command> query similar to the previous example can
-   be used to suggest spellings for misspelled words in user search terms.
-   A useful extra test is to require that the selected words are also of
-   similar length to the misspelled word.
-  </para>
-
-  <note>
-   <para>
-    Since the <structname>words</> table has been generated as a separate,
-    static table, it will need to be periodically regenerated so that
-    it remains reasonably up-to-date with the document collection.
-    Keeping it exactly current is usually unnecessary.
-   </para>
-  </note>
- </sect2>
-
- <sect2>
-  <title>References</title>
-
-  <para>
-   GiST Development Site
-   <ulink url="http://www.sai.msu.su/~megera/postgres/gist/"></ulink>
-  </para>
-  <para>
-   Tsearch2 Development Site
-   <ulink url="http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/"></ulink>
-  </para>
- </sect2>
-
- <sect2>
-  <title>Authors</title>
-
-  <para>
-   Oleg Bartunov <email>[email protected]</email>, Moscow, Moscow University, Russia
-  </para>
-  <para>
-   Teodor Sigaev <email>[email protected]</email>, Moscow, Delta-Soft Ltd.,Russia
-  </para>
-  <para>
-   Documentation: Christopher Kings-Lynne
-  </para>
-  <para>
-   This module is sponsored by Delta-Soft Ltd., Moscow, Russia.
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgupgrade.sgmlin b/doc-xc/src/sgml/pgupgrade.sgmlin
deleted file mode 100644
index 5a93fbd219..0000000000
--- a/doc-xc/src/sgml/pgupgrade.sgmlin
+++ /dev/null
@@ -1,577 +0,0 @@
-<!-- doc/src/sgml/pgupgrade.sgml -->
-
-<sect1 id="pgupgrade" xreflabel="pg_upgrade">
- <title>pg_upgrade</title>
-
- <indexterm zone="pgupgrade">
-  <primary>pg_upgrade</primary>
- </indexterm>
-
-<!## XC>
-&xconly;
- <para>
-  <application>pg_updrade</> is not compatible
-  with <productname>Postgres-XC</> due to the difference of internal
-  catalog.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  <application>pg_updrade</> is not compatible
-  with <productname>Postgres-XL</> due to the difference of internal
-  catalog.
- </para>
-<!## end>
-
-<!## PG>
- <para>
-  <application>pg_upgrade</> (formerly called <application>pg_migrator</>) allows data
-  stored in <productname>PostgreSQL</> data files to be upgraded to a later <productname>PostgreSQL</>
-  major version without the data dump/reload typically required for
-  major version upgrades, e.g. from 8.4.7 to the current major release
-  of <productname>PostgreSQL</>.  It is not required for minor version upgrades, e.g. from
-  9.0.1 to 9.0.4.
- </para>
-
- <para>
-  Major PostgreSQL releases regularly add new features that often
-  change the layout of the system tables, but the internal data storage
-  format rarely changes.  <application>pg_upgrade</> uses this fact
-  to perform rapid upgrades by creating new system tables and simply
-  reusing the old user data files.  If a future major release ever
-  changes the data storage format in a way that makes the old data
-  format unreadable, <application>pg_upgrade</> will not be usable
-  for such upgrades.  (The community will attempt to avoid such
-  situations.)
- </para>
-
- <para>
-  <application>pg_upgrade</> does its best to
-  make sure the old and new clusters are binary-compatible, e.g.  by
-  checking for compatible compile-time settings, including 32/64-bit
-  binaries.  It is important that
-  any external modules are also binary compatible, though this cannot
-  be checked by <application>pg_upgrade</>.
- </para>
-
- <sect2>
-  <title>Supported Versions</title>
-
-  <para>
-   pg_upgrade supports upgrades from 8.3.X and later to the current
-   major release of <productname>PostgreSQL</>, including snapshot and alpha releases.
-
-  </para>
-
- </sect2>
-
- <sect2>
-  <title><application>pg_upgrade</> Options</title>
-
-   <para>
-    <application>pg_upgrade</application> accepts the following command-line arguments:
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>-b</option> <replaceable>old_bindir</></term>
-      <term><option>--old-bindir=</option><replaceable>old_bindir</></term>
-      <listitem><para>the old cluster executable directory;
-      environment variable <envar>OLDBINDIR</></para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-B</option> <replaceable>new_bindir</></term>
-      <term><option>--new-bindir=</option><replaceable>new_bindir</></term>
-      <listitem><para>the new cluster executable directory;
-      environment variable <envar>NEWBINDIR</></para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-c</option></term>
-      <term><option>--check</option></term>
-      <listitem><para>check clusters only, don't change any data</para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-d</option> <replaceable>old_datadir</></term>
-      <term><option>--old-datadir=</option><replaceable>old_datadir</></term>
-      <listitem><para>the old cluster data directory; environment
-      variable <envar>OLDDATADIR</></para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-D</option> <replaceable>new_datadir</></term>
-      <term><option>--new-datadir=</option><replaceable>new_datadir</></term>
-      <listitem><para>the new cluster data directory; environment
-      variable <envar>NEWDATADIR</></para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-g</option></term>
-      <term><option>--debug</option></term>
-      <listitem><para>enable debugging</para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-G</option> <replaceable>debug_filename</></term>
-      <term><option>--debugfile=</option><replaceable>debug_filename</></term>
-      <listitem><para>output debugging activity to file</para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-k</option></term>
-      <term><option>--link</option></term>
-      <listitem><para>link instead of copying files to new cluster</para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l</option> <replaceable>log_filename</></term>
-      <term><option>--logfile=</option><replaceable>log_filename</></term>
-      <listitem><para>log session activity to file</para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p</option> <replaceable>old_port_number</></term>
-      <term><option>--old-port=</option><replaceable>old_portnum</></term>
-      <listitem><para>the old cluster port number; environment
-      variable <envar>PGPORT</></para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-P</option> <replaceable>new_port_number</></term>
-      <term><option>--new-port=</option><replaceable>new_portnum</></term>
-      <listitem><para>the new cluster port number; environment
-      variable <envar>PGPORT</></para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-u</option> <replaceable>user_name</></term>
-      <term><option>--user=</option><replaceable>user_name</></term>
-      <listitem><para>cluster's super user name; environment
-      variable <envar>PGUSER</></para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-v</option></term>
-      <term><option>--verbose</option></term>
-      <listitem><para>enable verbose output</para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-V</option></term>
-      <term><option>--version</option></term>
-      <listitem><para>display version information, then exit</para></listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-?</option></term>
-      <term><option>-h</option></term>
-      <term><option>--help</option></term>
-      <listitem><para>show help, then exit</para></listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
- </sect2>
-
- <sect2>
-  <title>Upgrade Steps</title>
-
-  <procedure>
-   <step performance="optional">
-    <title>Optionally move the old cluster</title>
-
-    <para>
-     If you are using a version-specific installation directory, e.g.
-     <filename>/opt/PostgreSQL/8.4</>, you do not need to move the old cluster. The
-     one-click installers all use version-specific installation directories.
-    </para>
-
-    <para>
-     If your installation directory is not version-specific, e.g.
-     <filename>/usr/local/pgsql</>, it is necessary to move the current PostgreSQL install
-     directory so it does not interfere with the new <productname>PostgreSQL</> installation.
-     Once the current <productname>PostgreSQL</> server is shut down, it is safe to rename the
-     PostgreSQL installation directory; assuming the old directory is
-     <filename>/usr/local/pgsql</>, you can do:
-
-<programlisting>
-mv /usr/local/pgsql /usr/local/pgsql.old
-</programlisting>
-     to rename the directory.
-    </para>
-   </step>
-
-   <step>
-    <title>For source installs, build the new version</title>
-
-    <para>
-     Build the new PostgreSQL source with <command>configure</> flags that are compatible
-     with the old cluster. <application>pg_upgrade</> will check <command>pg_controldata</> to make
-     sure all settings are compatible before starting the upgrade.
-    </para>
-   </step>
-
-   <step>
-    <title>Install the new PostgreSQL binaries</title>
-
-    <para>
-     Install the new server's binaries and support files. You can use the
-     same port numbers for both clusters, typically 5432, because the old and
-     new clusters will not be running at the same time.
-    </para>
-
-    <para>
-     For source installs, if you wish to install the new server in a custom
-     location, use the <literal>prefix</literal> variable:
-
-<programlisting>
-gmake prefix=/usr/local/pgsql.new install
-</programlisting>
-    </para>
-   </step>
-
-   <step>
-    <title>Install pg_upgrade and pg_upgrade_support</title>
-
-    <para>
-     Install the <application>pg_upgrade</> binary and
-     <application>pg_upgrade_support</> library in the new PostgreSQL cluster.
-    </para>
-   </step>
-
-   <step>
-    <title>Initialize the new PostgreSQL cluster</title>
-
-    <para>
-     Initialize the new cluster using <command>initdb</command>.
-     Again, use compatible <command>initdb</command>
-     flags that match the old cluster. Many
-     prebuilt installers do this step automatically. There is no need to
-     start the new cluster.
-    </para>
-   </step>
-
-   <step>
-    <title>Install custom shared object files</title>
-
-    <para>
-     Install any custom shared object files (or DLLs) used by the old cluster
-     into the new cluster, e.g. <filename>pgcrypto.so</filename>, whether they are from <filename>contrib</filename>
-     or some other source. Do not install the schema definitions, e.g.
-     <filename>pgcrypto.sql</>, because these will be upgraded from the old cluster.
-    </para>
-   </step>
-
-   <step>
-    <title>Adjust authentication</title>
-
-    <para>
-     <command>pg_upgrade</> will connect to the old and new servers several times,
-     so you might want to set authentication to <literal>trust</> in
-     <filename>pg_hba.conf</>, or if using <literal>md5</> authentication,
-     use a <filename>~/.pgpass</> file (see <xref linkend="libpq-pgpass">)
-     to avoid being prompted repeatedly for a password.
-    </para>
-   </step>
-
-   <step>
-    <title>Stop both servers</title>
-
-    <para>
-     Make sure both database servers are stopped using, on Unix, e.g.:
-
-<programlisting>
-pg_ctl -D /opt/PostgreSQL/8.4 stop
-pg_ctl -D /opt/PostgreSQL/9.0 stop
-</programlisting>
-
-     or on Windows, using the proper service names:
-
-<programlisting>
-NET STOP postgresql-8.4
-NET STOP postgresql-9.0
-</programlisting>
-
-     or
-
-<programlisting>
-NET STOP pgsql-8.3  (<productname>PostgreSQL</> 8.3 and older used a different service name)
-</programlisting>
-    </para>
-   </step>
-
-   <step>
-    <title>Run <application>pg_upgrade</></title>
-
-    <para>
-     Always run the <application>pg_upgrade</> binary of the new server, not the old one.
-     <application>pg_upgrade</> requires the specification of the old and new cluster's
-     data and executable (<filename>bin</>) directories. You can also specify separate
-     user and port values, and whether you want the data linked instead of
-     copied (the default). If you use linking, the upgrade will be much
-     faster (no data copying), but you will no longer be able to access your
-     old cluster once you start the new cluster after the upgrade. See
-     <literal>pg_upgrade --help</> for a full list of options.
-    </para>
-
-    <para>
-     For Windows users, you must be logged into an administrative account, and
-     then start a shell as the <literal>postgres</> user and set the proper path:
-
-<programlisting>
-RUNAS /USER:postgres "CMD.EXE"
-SET PATH=%PATH%;C:\Program Files\PostgreSQL\9.0\bin;
-</programlisting>
-
-     and then run <application>pg_upgrade</> with quoted directories, e.g.:
-
-<programlisting>
-pg_upgrade.exe
-        --old-datadir "C:/Program Files/PostgreSQL/8.4/data"
-        --new-datadir "C:/Program Files/PostgreSQL/9.0/data"
-        --old-bindir "C:/Program Files/PostgreSQL/8.4/bin"
-        --new-bindir "C:/Program Files/PostgreSQL/9.0/bin"
-</programlisting>
-
-     Once started, <command>pg_upgrade</> will verify the two clusters are compatible
-     and then do the upgrade. You can use <command>pg_upgrade --check</>
-     to perform only the checks, even if the old server is still
-     running. <command>pg_upgrade --check</> will also outline any
-     manual adjustments you will need to make after the upgrade.
-     <command>pg_upgrade</> requires write permission in the current directory.
-    </para>
-
-    <para>
-     Obviously, no one should be accessing the clusters during the upgrade.
-    </para>
-
-    <para>
-     If an error occurs while restoring the database schema, <command>pg_upgrade</> will
-     exit and you will have to revert to the old cluster as outlined in <xref linkend="pgupgrade-step-revert">
-     below. To try <command>pg_upgrade</command> again, you will need to modify the old
-     cluster so the pg_upgrade schema restore succeeds. If the problem is a
-     contrib module, you might need to uninstall the contrib module from
-     the old cluster and install it in the new cluster after the upgrade,
-     assuming the module is not being used to store user data.
-    </para>
-   </step>
-
-   <step>
-    <title>Restore <filename>pg_hba.conf</></title>
-
-    <para>
-     If you modified <filename>pg_hba.conf</> to use <literal>trust</>,
-     restore its original authentication settings.
-    </para>
-   </step>
-
-   <step>
-    <title>Post-Upgrade processing</title>
-
-    <para>
-     If any post-upgrade processing is required, pg_upgrade will issue
-     warnings as it completes. It will also generate script files that must
-     be run by the administrator. The script files will connect to each
-     database that needs post-upgrade processing. Each script should be
-     run using:
-
-<programlisting>
-psql --username postgres --file script.sql postgres
-</programlisting>
-
-     The scripts can be run in any order and can be deleted once they have
-     been run.
-    </para>
-
-    <caution>
-    <para>
-     In general it is unsafe to access tables referenced in rebuild scripts
-     until the rebuild scripts have run to completion; doing so could yield
-     incorrect results or poor performance. Tables not referenced in rebuild
-     scripts can be accessed immediately.
-    </para>
-    </caution>
-   </step>
-
-   <step>
-    <title>Statistics</title>
-
-    <para>
-     Because optimizer statistics are not transferred by <command>pg_upgrade</>, you will
-     be instructed to run a command to regenerate that information at the end
-     of the upgrade.
-    </para>
-   </step>
-
-   <step>
-    <title>Delete old cluster</title>
-
-    <para>
-     Once you are satisfied with the upgrade, you can delete the old
-     cluster's data directories by running the script mentioned when
-     <command>pg_upgrade</command> completes. You can also delete the
-     old installation directories
-     (e.g. <filename>bin</>, <filename>share</>).
-    </para>
-   </step>
-
-   <step id="pgupgrade-step-revert" performance="optional">
-    <title>Reverting to old cluster</title>
-
-    <para>
-     If, after running <command>pg_upgrade</command>, you wish to revert to the old cluster,
-     there are several options:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        If you ran <command>pg_upgrade</command>
-        with <option>--check</>, no modifications were made to the old
-        cluster and you can re-use it anytime.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        If you ran <command>pg_upgrade</command>
-        with <option>--link</>, the data files are shared between the
-        old and new cluster. If you started the new cluster, the new
-        server has written to those shared files and it is unsafe to
-        use the old cluster.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        If you
-        ran <command>pg_upgrade</command> <emphasis>without</> <option>--link</>
-        or did not start the new server, the old cluster was not
-        modified except that an <literal>.old</> suffix was appended
-        to <filename>$PGDATA/global/pg_control</> and perhaps
-        tablespace directories. To reuse the old cluster, remove
-        the <filename>.old</> suffix
-        from <filename>$PGDATA/global/pg_control</>. and, if upgrading
-        to 8.4 or earlier, remove the tablespace directories created
-        by the upgrade and remove the <filename>.old</> suffix from
-        the tablespace directory names; then you can restart the old
-        cluster.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </step>
-  </procedure>
-
- </sect2>
-
- <sect2>
-  <title>Limitations in Upgrading <emphasis>from</> PostgreSQL 8.3</title>
-
-  <para>
-   Upgrading from PostgreSQL 8.3 has additional restrictions not present
-   when upgrading from later PostgreSQL releases.  For example,
-   pg_upgrade will not work for upgrading from 8.3 if a user column
-   is defined as:
-   <itemizedlist>
-    <listitem>
-     <para>
-      a <type>tsquery</> data type
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      data type <type>name</> and is not the first column
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   You must drop any such columns and upgrade them manually.
-  </para>
-
-  <para>
-   pg_upgrade will require a table rebuild if:
-   <itemizedlist>
-    <listitem>
-     <para>
-      a user column is of data type <type>tsvector</type>
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   pg_upgrade will require a reindex if:
-   <itemizedlist>
-    <listitem>
-     <para>
-      an index is of type hash or GIN
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      an index uses <function>bpchar_pattern_ops</>
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   Also, the default datetime storage format changed to integer after
-   <productname>PostgreSQL</> 8.3. pg_upgrade will check that the datetime storage format
-   used by the old and new clusters match. Make sure your new cluster is
-   built with the configure flag <option>--disable-integer-datetimes</>.
-  </para>
-
-  <para>
-   For Windows users, note that due to different integer datetimes settings
-   used by the one-click installer and the MSI installer, it is only
-   possible to upgrade from version 8.3 of the one-click distribution to
-   version 8.4 or later of the one-click distribution. It is not
-   possible to upgrade from the MSI installer to the one-click installer.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>Notes</title>
-
-  <para>
-   <application>pg_upgrade</> does not support upgrading of databases
-   containing these <type>reg*</> OID-referencing system data types:
-   <type>regproc</>, <type>regprocedure</>, <type>regoper</>,
-   <type>regoperator</>, <type>regclass</>, <type>regconfig</>, and
-   <type>regdictionary</>.  (<type>regtype</> can be upgraded.)
-  </para>
-
-  <para>
-   All failure, rebuild, and reindex cases will be reported by
-   <application>pg_upgrade</> if they affect your installation;
-   post-upgrade scripts to rebuild tables and indexes will be
-   generated automatically.
-  </para>
-
-  <para>
-   For deployment testing, create a schema-only copy of the old cluster,
-   insert dummy data, and upgrade that.
-  </para>
-
-  <para>
-   If you want to use link mode and you don't want your old cluster
-   to be modified when the new cluster is started, make a copy of the
-   old cluster and upgrade that with link mode. To make a valid copy
-   of the old cluster, use <command>rsync</> to create a dirty
-   copy of the old cluster while the server is running, then shut down
-   the old server and run <command>rsync</> again to update the copy with any
-   changes to make it consistent.
-  </para>
-
- </sect2>
-
-<!## end>
-</sect1>
diff --git a/doc-xc/src/sgml/pgxc_ctl-ref.sgmlin b/doc-xc/src/sgml/pgxc_ctl-ref.sgmlin
deleted file mode 100644
index 0e1679e418..0000000000
--- a/doc-xc/src/sgml/pgxc_ctl-ref.sgmlin
+++ /dev/null
@@ -1,1911 +0,0 @@
-<!--
-doc/src/sgml/ref/pgxc_ctl-ref.sgml
-PostgreSQL documentation
--->
-
-<sect1 id="pgxc-ctl" xreflabel="pgxc-ctl">
-
-<title>pgxc_ctl</title>
-
-<indexterm zone="pgxc-ctl">
- <primary>pgxc_ctl</primary>
-</indexterm>
-
- <sect2>
-  <title>Description</title>
-
-&xlonly;
-
-    <para>
-     The manual configuration of the individual components of a Postgres-XL cluster 
-     can be cumbersome and error prone.
-     The Postgres-XL Cluster Control utility, <application>pgxc_ctl</application>, simplifies this by allowing for the configuration,
-     initialization, starting, stoping, monitoring and failover of Postgres-XL
-     components.  
-     This section describes how to use
-     <application>pgxc_ctl</application>. 
-    </para>
- </sect2>
-
- <sect2 id="R1-APP-PGXC-CTL-1">
-  <title>Building and installing pgxc_ctl</title>
-
-  <para>
-   You should build pgxc_ctl using your Postgres-XL build environment.
-   <application>pgxc_ctl</application> source code comes with Postgres-XL source code tarball.
-   The latest version of the source code will be available at its home repository,
-<programlisting>
-http://  pgxc_ctl
-</programlisting>
-   If you would like to use the latest version from pgxc_ctl home repository,
-   get the source code tarball and expand it in the source's contrib
-   directory of your Postgres-XL build environment.  
-   If you are using pgxc_ctl in Postgres-XL tarball, you don't have to do this.
-  </para>
-
-  <para>
-   Before building pgxc_ctl, you should build Postgres-XL binary, like
-<programlisting>
-$ cd <replaceable>your Postgres-XL build directory</replaceable>
-$ ./configure <replaceable>your configuration option</replaceable>
-$ make
-</programlisting>
-
-   Please note that you dont'have to install the
-   <application>Postgres-XL</application> binary to build
-   <application>pgxc_ctl</application>.  
-   Also please note that <application>Postgres-XL</application> top
-   level make and make install command does not take care of pgxc_ctl.
-   You should build and install it separately.
-  </para>
-
-  <para>
-   Then you can build pgxc_ctl as follows:
-<programlisting>
-$ cd contrib/pgxc_ctl
-$ make
-$ make install
-</programlisting>
-   The <application>pgxc_ctl</application> binary will be installed in the
-   same directory as <application>Postgres-XL</application> binaries. 
-  </para>
-
-  <para>
-   <application>Postgres-XL</application> consists of many components
-   (or called "nodes") running in various physical or virtual
-   machines.
-   Because pgxc_ctl relies on ssh connections between the machines where
-   <application>pgxc_ctl</application> and other nodes are running,
-   you should setup ssh-agent authentication to avoid typing password
-   each time pgcx_ctl issues ssh.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>pgxc_ctl home directory</title>
-
-  <para>
-   <application>pgxc_ctl</application> uses its own work directory,
-   where it stores configuration files and logs, as well as other
-   resources. 
-   The default value is <literal>$HOME/pgxc_ctl</literal> and you can
-   specify this by the <literal>--home</literal> option.
-  </para>
-
-  <para>
-   The <application>pgxc_ctl</application> home directory may be referred
-   to as <literal>$PGXC_CTL_HOME</literal> through this manual.
-  </para>
-
-  <para>
-   You do not have to create this directory manually.   
-   <application>pgxc_ctl</application> will create the directory when
-   it is invoked for the first time. 
-   Please note that you need appropriate privilege to create
-   <literal>$PGXC_CTL_HOME</literal>. 
-   You can create this manually, of course.
-
-   For details, please refer to later sections.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>pgxc_ctl configuration file</title>
-
-  <para>
-   pgxc_ctl uses configuration file.  
-   The default name and the location is
-   <literal>$PGXC_CTL_HOME/pgxc_ctl.conf</literal>. 
-   When you change Postgres-XL cluster configuration using pgxc_ctl
-   commands, this file will be updated.
-   Depending upon your configuration,
-   <application>pgxc_ctl</application> will back up this file
-   according to your configuration.
-  </para>
-
-  <para>
-   <application>pgxc_ctl</application> provides the command "prepare" to
-   setup the prototype of this file. 
-   For details, please refer to command syntax of
-   <application>pgxc_ctl</application>.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>pgxc_ctl initialization file</title>
-
-  <para>
-   You can specify your preferred parameters of pgxc_ctl behavior. 
-   You can specify parameters in <literal>/etc/pgxc_ctl</literal>
-   and/or <literal>$HOME/.pgxc_ctl</literal> file.
-   Setups in <literal>$HOME/.pgxc_ctl</literal> have higher priority
-   so you can specify system-wide setups at
-   <literal>/etc/pgxc_ctl</literal> and then your personal preferences
-   in <literal>$HOME/.pgxc_ctl</literal>.
-  </para>
-
-  <para>
-   The format of this file will be described in a later section.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>Running pgxc_ctl for the first time</title>
-
-  <para>
-   Unless you build $PGXC_CTL_HOME and the configuration file from the
-   scratch, you should run pgxc_ctl to build your $PGXC_CTL_HOME and
-   get a prototype of configuration file.
-   From your shell prompt, simply type
-   <application>pgxc_ctl</application>.
-   You will have the following prompt:
-<programlisting>
-$ pgxc_ctl
-PGXC$ 
-</programlisting>
-   You will get the default prompt, which you can modify at any time
-   through initialization files.
-  </para>
-
-  <para>
-   Try to type <literal>pwd</literal>.
-   You will see what your <literal>$PGXC_CTL_HOME</literal> is.
-<programlisting>
-$ pgxc_ctl
-PGXC$ pwd
-/home/postgres-xl/pgxc_ctl
-PGXC$
-</programlisting>
-   If you specify <option>--home</option> option with another
-   directory, <application>pgxc_ctl</application> will start at this
-   directory, after building it if needed.
-<programlisting>
-$ pgxc_ctl --home /home/postgres-xl/my_pgxc_ctl
-PGXC$ pwd
-/home/postgres-xl/my_pgxc_ctl
-PGXC$
-</programlisting>
-   You can specify your pgxc_ctl_home as environment variable
-   <literal>PGXC_CTL_HOME</literal>, or you can specify this as
-   variable <literal>pgxc_ctl_home</literal> in your initialization
-   files.
-  </para>
-
-  <para>
-   The command line option has the highest priority, then the environment,
-   <literal>$HOME/.pgxc_ctl</literal> and
-   <literal>/etc/pgxc_ctl</literal>. 
-  </para>
-
-  <para>
-   Type prepare or prepare config to get a configuration template file
-   <filename>pgxc_ctl.conf</filename> at
-   <literal>$PGXC_CTL_HOME</literal>.
-   You may add file name as an option to get configuration template in
-   your favorite file.  For example:
-<programlisting>
-PGXC$ prepare
-PGXC$
-</programlisting>
-or 
-<programlisting>
-PGXC$ prepare config my_pgxc.conf
-PGXC$
-</programlisting>
-
-You may also generate a template configuration file suitable for testing
-<application>Postgres-XL</application> on the localhost. Use option
-<literal>minimal</literal> to generate a such a template configuration file.
-<programlisting>
-PGXC$ prepare config minimal
-PGXC$ prepare config minimal my_minimal_pgxc.conf
-</programlisting>
-
-   A more detailed syntax of the command will be described in a later section.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>Make your configuration</title>
-
-  <para>
-   Please take a look at the template of the configuration file you
-   created in the previous section.
-   This file is actually a bash script file to setup various bash
-   script variables which are passed to pgxc_ctl next time you run
-   it.
-  </para>
-
-  <para>
-   The <application>Postgres-XL</application> configuration needs to
-   specify same or similar values to each node configuration, for
-   example, work directory, port, etc.
-   To avoid trivial errors, you can specify the same value as defaults
-   for variables and refer to them later in each variable setups.
-  </para>
-
-  <para>
-   For example, a part of your template may look like this:
-<programlisting>
-#---- Shortcuts ------
-gtmProxyDir=$HOME/pgxc/nodes/gtm_pxy
-
-#---- Overall -------
-gtmProxy=y              # Specify y if you configure at least one GTM 
-                        # proxy.
-                        # You may not configure gtm proxies only when
-                        # you dont' configure GTM slaves. 
-						# If you specify this value not to y, the
-                        # following parameters will be set to default
-                        # empty values.  
-						# If we find there're no valid Proxy server
-                        # names (means, every servers are specified 
-						# as none), then gtmProxy value will be set to
-                        # "n" and all the entries will be set to empty
-                        # values. 
-gtmProxyNames=(gtm_pxy1 gtm_pxy2 gtm_pxy3 gtm_pxy4)	# No used if it is not configured
-gtmProxyServers=(node06 node07 node08 node09)       # Specify none if you dont' configure it.
-gtmProxyPorts=(20001 20001 20001 20001)             # Not used if it is not configured.
-gtmProxyDirs=($gtmProxyDir $gtmProxyDir $gtmProxyDir $gtmProxyDir)	# Not used if it is not configured.
-</programlisting>
-   This section specifies the gtm proxy configuration.
-   We have four <literal>gtm proxies</literal> in each of the server.
-   They share working directory path and is specified as a shortcut
-   which is referred to later.
-  </para>
-
-  <para>
-   You can do all these in any part of the configuration file.
-  </para>
-
-  <para>
-   Please note that the working directory of this script is
-   <filename>$PGXC_CTL_HOME</filename>, unless you change it explicitly
-   in this configuration file. 
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>pgxc_ctl invocation options</title>
-
-  <para>
-   When you invoke pgxc_cmd from your shell,
-   <application>pgxc_ctl</application> accepts several options to
-   control its behavior.
-   <application>pgxc_ctl</application> command format is as follows:
-<programlisting>
-pgxc [options ... ] [pgxc_command]
-</programlisting>
-  </para>
-  
-  <para>
-   Options are as follows:
-  </para>
-
-  <variablelist>
-    <varlistentry>
-      <term><option>-c <replaceable class="parameter">configuration_file</replaceable></></term>
-      <term><option>--configuration <replaceable class="parameter">configuration_file</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies configuration file.
-       The default is <filename>pgxc_ctl_conf</filename>, or the value
-       of <literal>configFile</literal> option
-       found in the initialization file.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>--home <replaceable class="parameter">home_directory</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies <filename>$PGXC_CTL_HOME</filename> directory.
-       You can specify this as <literal>pgxc_ctl_home</literal>
-       variable in the initialization file.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-i <replaceable class="parameter">file</replaceable></></term>
-      <term><option>--infile <replaceable class="parameter">file</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies where to read pgxc_ctl commands.
-       There's no corresponding variable in the initialization file.
-       Default is the standard input.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-L <replaceable class="parameter">logfile</replaceable></></term>
-      <term><option>--logfile <replaceable class="parameter">logfile</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies where to write the log.
-       The path is relative to <filename>$PGXC_CTL_HOME</filename> or
-       the value of log directory specified as <option>-l</option>
-       option or <literal>logDir</literal> variable in the
-       initialization file, if specified.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-l <replaceable class="parameter">logdir</replaceable></option></term>
-      <term><option>--logdir <replaceable class="parameter">logdir</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies the directory of the log file.
-       Default is <filename>$PGXC_HOME/pgxc_log/</filename>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-o <replaceable class="parameter">outfile</replaceable></option></term>
-      <term><option>--out-file <replaceable class="parameter">outfile</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies where to write <application>pgxc_ctl</application> output.
-       Default is the standard output.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>--silent</option></term>
-      <listitem>
-      <para>
-       Specifies to run <application>pgxc_ctl</application> without
-       printing many messages.
-       This value can also be set as variable
-       <literal>verbose</literal> in the initialization file.
-       You can setup level of messages <literal>logMessage</literal>
-       and <literal>printMessage</literal> variables in the
-       initialization file as well.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-V</option></term>
-      <term><option>--version</option></term>
-      <listitem>
-      <para>
-       Prints <application>pgxc_ctl</application> version and exits.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-v</option></term>
-      <term><option>--verbose</option></term>
-      <listitem>
-      <para>
-       Specifies to run pgxc_ctl to print as many messages as
-       possible.
-      </para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
- </sect2>
-
-
- <sect2>
-  <title>pgxc_ctl initialization file</title>
-
-  <para>
-   As described in previous sections, pgxc_ctl behavior, as specified
-   in the command line options, can be specified in advance in the
-   initialization file <filename>/etc/pgxc_ctl</filename> or
-   <filename>$HOME/.pgxc_ctl</filename>.
-  </para>
-  <para>
-   The syntax is as follows:
-<programlisting>
-name value [ value ... ] # comment
-</programlisting>
-  </para>
-  <para>
-   Blank lines or lines beginning with '#' are simply ignored.  If
-   you'd like to include space or tab in the variable name, enclose
-   the name with <literal>'...'</literal> or <literal>"..."</literal>.
-  </para>
-  <para>
-   Please note that this file is not a bash script.
-  </para>
-  <para>
-   List of the name and their value is as follows:
-  </para>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><option>configFile <replaceable>filename</replaceable></option></term>
-    <listitem>
-     <para>
-      Specify the configuration file name.
-      Default is <filename>pgxc_ctl.conf</filename>.
-      This option can be overridden by <option>-c</option> command
-      line option.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>localTmpDir <replaceable>dirname</replaceable></option></term>
-    <listitem>
-     <para>
-      Specify remote temporary directory, default is <filename>/tmp</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>logDir <replaceable>dirname</replaceable></option></term>
-    <listitem>
-     <para>
-      Specifies the directory to write log.  Can be overridden by
-      <option>-l</option> command line option.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>logFile <replaceable>filename</replaceable></option></term>
-    <listitem>
-     <para>
-      Specifies the log file name, which is relative to
-      <filename>$PGXC_CTL_HOME/pgxc_log</filename> or value of
-      <literal>logDir</literal> variable.
-      Can be overridden by <option>-L,</option> command line option.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>logMessage <replaceable>msglevel</replaceable></option></term>
-     <listitem>
-      <para>
-       Specifies the message level to print to the terminal or output
-       file.
-       Valid value is <literal>MANDATORY</literal>,
-       <literal>PANIC</literal>, <literal>ERROR</literal>,
-       <literal>WARNING</literal>, <literal>NOTICE</literal>,
-       <literal>NOTICE2</literal>, <literal>INFO</literal>,
-       <literal>DEBUG1</literal>, <literal>DEBUG2</literal>, or
-       <literal>DEBUG3</literal>. Default is
-       <literal>NOTICE</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>pgxc_ctl_home <replaceable>dirname</replaceable></option></term>
-     <listitem>
-      <para>
-       Specifies <filename>$PGXC_CTL_HOME</filename>.
-       Default is <filename>$HOME/pgxc_ctl</filename> or environment
-       variable <literal>$PGXC_CTL_HOME</literal>.
-       Can be overriden by <option>--home</option> command line option.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>printMessage <replaceable>msglevel</replaceable></option></term>
-     <listitem>
-      <para>
-       Specifies the message level to print to the log file.
-       Valid value is <literal>MANDATORY</literal>,
-       <literal>PANIC</literal>, <literal>ERROR</literal>,
-       <literal>WARNING</literal>, <literal>NOTICE</literal>,
-       <literal>NOTICE2</literal>, <literal>INFO</literal>,
-       <literal>DEBUG1</literal>, <literal>DEBUG2</literal>, or
-       <literal>DEBUG3</literal>. Default is
-       <literal>NOTICE</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>tmpDir <replaceable>dirname</replaceable></option></term>
-     <listitem>
-      <para>
-       Specify local temporary directory, default is <filename>/tmp</filename>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>verbose <replaceable>value</replaceable></option></term>
-     <listitem>
-      <para>
-       Specifies verbose message output from
-       <application>pgxc_ctl</application>.
-       Value should be <literal>y</literal> or <literal>n</literal>.
-       Can be overridedn by <option>-v</option> or
-        <option>--silent</option> command line option.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>xc_prompt <replaceable>prompt</replaceable></option></term>
-     <listitem>
-      <para>
-       Specifies pgxc_prompt.  Default is <literal>'PGXC$ '</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-  </variablelist>
-
-  <para>
-    Typical example of this initialization file will be as follows:
-<programlisting>
-$ cat ~/.pgxc_ctl
-xc_prompt 'PGXC$ '
-verbose y
-logMessage 'DEBUG3'
-printMessage 'DEBUG1'
-printLocation y
-$
-</programlisting>
-
-  </para>
-
- </sect2>
-
-
- <sect2>
-  <title>Postgres-XL basics and its resources</title>
-
-  <sect3 id="R2-APP-PGXC-CTL-configuration">
-   <title>Postgres-XL components</title>
-
-   <para>
-    Postgres-XL consists of the following components.  Each component may
-    be called <option>node</option>, which may not necessarily refer
-    to physical or virtual server because you can configure more
-    than one node to one physical/virtual server.  
-    You should consider how many of them to configure.
-    Hereafter, we call such physical/virtual server as
-    <option>host</option>.
-   </para>
-
-   <variablelist>
-
-    <varlistentry>
-     <term>GTM</term>
-     <listitem>
-      <para>
-       GTM stands for global transaction manager.
-       You must have one in the cluster.
-       For production, GTM should be configured in a separate server.
-       GTM can have a slave which can fail over when GTM fails.
-       GTM slave can be installed (hopefully) in a separate server but
-       can be installed in one of the others where you have gtm_proxy,
-       coordinators and datanodes.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>GTM-Proxy</term>
-     <listitem>
-      <para>
-       GTM proxy reduces the communication load between coordinator and
-       GTM and helps GTM failover.
-       You should configure one gtm_proxy in each server where you have
-       coordinator or datanode as described below.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Coordinator</term>
-     <listitem>
-      <para>
-       Coordinator handles application connection and statement
-       handling.
-       For simplicity and load balancing, it is a good idea to
-       install coordinator to each server other than where GTM (and GTM
-       slave) are configured.  Coordinator can have a slave.  Slave can
-       be configured in one of the servers where other coordinator
-       master is installed.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Datanode</term>
-     <listitem>
-      <para>
-       Datanode stores the data and run local SQL statement supplied by
-       a coordinator.  Datanode should also be configured in all the
-       servers except those for GTM (and GTM slave).
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </sect3>
-
-  <sect3>
-   <title>Common resource assignment and configuration practice</title>
-   <para>
-    Each component requires the following resources:
-     
-    <itemizedlist>
-     <listitem>
-      <para>
-       hostname, IP address or host name you can refer through DNS,
-       <filename>/etc/hosts</filename> or by equivalent means. 
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       port
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       work directory
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    Also, coordinator and datanode needs additional port for connection pooling to
-    other nodes.
-   </para>
-
-   <para>
-    In the same host, you must not assign the same port and the same
-    work directory to nodes.
-    <application>pgxc_ctl</application> checks this.
-   </para>
-
-   <para>
-    When assign the port, you should be careful not to assign already
-    assigned one to other service. 
-   </para>
-
-   <para>
-    Also, please note the following:
-    <itemizedlist>
-     <listitem>
-      <para>
-       You should not assign the same port to GTM master and GTM
-       slave. 
-      </para>
-     </listitem>
-     
-    </itemizedlist>
-   </para>
-
-   <para>
-    GTM, coordinators and datanodes can configure their slave.
-    <application>pgxc_ctl</application> does not support cascaded
-    slave or more than one slave for coordinator and datanode.
-    It is not a restriction of <application>postgres-XL</application>,
-    it is a restriction of <application>pgxc_ctl</application>.
-   </para>
-
-   <para>
-    At present, coordinator and datanode slaves are connected using
-    synchronous replication in pgxc_ctl.  
-    This is not a <application>Posgres-XL</application> restriction
-    either.
-    In the future, asynchronous, cascaded and multiple slaves may be
-    supported.
-   </para>
-
-  </sect3>
-
- </sect2>
- <sect2>
-  <title>Configuration</title>
-
-  <para>
-   As described in the previous section, you can configure your
-   <application>Postgres-XL</application> cluster by editing
-   <filename>pgxc_ctl.conf</filename> or other configuration files
-   manually.
-   But editing the file from the scratch can be a mess.
-   It is much better to have separate configuration file.
-   You can create configuration file template by typing
-
-<programlisting>
-PGXC$ prepare config
-PGXC$ 
-</programlisting>
-  </para>
-
-  <para>
-   You have your <filename>pgxc_ctl.conf</filename> file at
-   <filename>$HOME/pgxc_ctl</filename>.
-   You can edit it to configure your
-   <application>Postgres-XL</application> cluster.
-   When it messes up, you can again create the template with
-   <command>prepare config</command> command.
-   If you want to use other file name, specify the names
-   <command>prepare config</command> command option like:
-
-<programlisting>
-PGXC$ prepare config my_config.conf
-</programlisting>
-  </para>
-  <para>
-   Then you can edit this file to configure you
-   <application>postgres-XL</application> cluster. 
-   This file is actually a bash script file defining many variables
-   to define the cluster configuration.
-   With template values and comments, it will be easy to understand
-   what they mean.
-   </para>
-   <para>
-   You can also generate a minimal configuration file, god enough to test
-<application>Postgres-XL</application> on the localhost by specifying
-<literal>minimal</literal>. For example:
-<programlisting>
-PGXC$ prepare config minimal
-PGXC$ prepare config minimal my_minimal_config.conf
-</programlisting>
-
-   The following describes each variable in the order you find in the
-   configuration template. 
-  </para>
-
-  <sect3>
-   <title>Overall</title>
-
-   <variablelist>
-
-    <varlistentry>
-     <term><option>configBackup</option></term>
-     <listitem>
-      <para>
-       Option if you backup the configuration file to a remote
-       server. Specify <literal>y</literal> if you'd like to backup the
-       configuration file.   <literal>n</literal> otherwise.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>configBackupFile</option></term>
-     <listitem>
-      <para>
-       Name of the configuration backup file.
-       Effective when configuration file backup is enabled.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>configBackupHost</option></term>
-     <listitem>
-      <para>
-       Host name (or IP address) where you backup the
-       configuration file.   Effective when configuration file
-       backup is enabled.
-      </para>
-     </listitem>
-    </varlistentry>
-    
-    <varlistentry>
-     <term><option>localTmpDir</option></term>
-     <listitem>
-      <para>
-       Local directory used by pgxc_ctl itself.
-       You need full access to this directory.
-      </para>
-      <para>
-       This parameter was left here to make it compatible with
-       bash-version.
-       It is recommended to configure this parameter in
-       initialization file.
-      </para>
-     </listitem>
-    </varlistentry>
-    
-    <varlistentry>
-     <term><option>pgxcInstallDir</option></term>
-     <listitem>
-      <para>
-         <application>Postgres-XL</application> should at least be
-        installed in the server you are running
-        <application>pgxc_ctl</application>.
-        This variable specifies this installation directory, as you
-        specify with <option>--prefix=</option> option of configure
-        command when you build it.
-        All the installation will be copied to the same directory at
-        each servers and you should give appropriate privilege to this
-        directory in advance.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>pgxcOwner</option></term>
-      <listitem>
-       <para>
-        Name of the database user who owns whole
-        <application>Postgres-XL</application> database.
-        This can be different from $pgxcUser.
-        In the present version, we assume these two should be the same
-        though.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>pgxcUser</option></term>
-      <listitem>
-       <para>
-        Name of the operating system user you are logging in as
-        Postgres-XL owner.   At present, this should be the same as
-        <literal>$pgxcOwner</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>tmpDir</option></term>
-      <listitem>
-       <para>
-        Directory used for work at each server except for the one
-        pgxc_ctl runs.  You need full access to this directory at 
-        all the servers.
-       </para>
-       <para>
-        This parameter was left here to make it compatible with
-        bash-version.
-        It is recommended to configure this parameter in
-        initialization file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   
-   </sect3>
-
-   <sect3>
-    <title>GTM</title>
-    
-    <variablelist>
-
-     <varlistentry>
-      <term><option>gtmName</option></term>
-      <listitem>
-       <para>
-        Node name of GTM master.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>gtmExtraConfig</option></term>
-      <listitem>
-       <para>
-        If you'd like to add specific configuration to both GTM master
-        and slave, specify the file which contains such lines for
-        gtm.config file.
-        Otherwise, specify <literal>none</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmMasterDir</option></term>
-      <listitem>
-       <para>
-        Work directory for GTM master.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmMasterPort</option></term>
-      <listitem>
-       <para>
-        Listening port number of GTM master.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmMasterServer</option></term>
-      <listitem>
-       <para>
-        Host name where GTM master runs.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmMasterSpecificExtraConfig</option></term>
-      <listitem>
-       <para>
-        If you'd like to add specific configuration only to GTM
-        master, specify the file which contains such lines for
-        <filename>gtm.config</filename> file.
-        Otherwise, specify <literal>none</literal>
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmSlave</option></term>
-      <listitem>
-       <para>
-        Option to enable GTM slave.
-        Specify <literal>y</literal> to enable, <literal>n</literal>
-        otherwise.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>gtmSlaveName</option></term>
-      <listitem>
-       <para>
-        Node name of GTM slave.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>gtmSlaveDir</option></term>
-      <listitem>
-       <para>
-        Work directory for GTM slave.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmSlavePort</option></term>
-      <listitem>
-       <para>
-        Listening port number of GTM slave.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmSlaveServer</option></term>
-      <listitem>
-       <para>
-        Host name where GTM slave runs.  Effective only when GTM slave is effective.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmSlaveSpecificExtraConfig</option></term>
-      <listitem>
-       <para>
-        If you'd like to add specific configuration only to GTM slave,
-        specify the file which contains such lines for
-        <filename>gtm.config</filename> file.
-        Otherwise, specify <literal>none</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-    </variablelist>
-
-   </sect3>
-
-   <sect3>
-    <title>GTM Proxy</title>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>gtmProxy</option></term>
-      <listitem>
-       <para>
-        This specifies if you configure any GTM proxy in your
-        <application>Postgres-XL</application> cluster.
-        Specify the value <literal>y</literal> if you configure gtm
-        proxy in your <application>Postgres-XL</application> cluster.
-        Otherwise specify <literal>n</literal>.
-        If you specify <literal>n</literal>, all the other parameters
-        for gtm_proxy will be ignored.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmProxyDir</option></term>
-      <listitem>
-       <para>
-        This is a shortcut used to assign same work directory to all
-        the GTM proxies.
-        You don't have to worry about it when you specify these values
-        manually.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmProxyDirs</option></term>
-      <listitem>
-       <para>
-        Specify work directory for each GTM proxy.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmPxyExtraConfig</option></term>
-      <listitem>
-       <para>
-        If you'd like to add configuration value to all the GTM proxy,
-        specify the file name which contains such lines for
-        <filename>gtm_proxy.conf</filename>.
-        Otherwise specify <literal>none</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmProxyNames</option></term>
-      <listitem>
-       <para>
-        Specify unique name for each GTM proxy.
-        This is an array.
-        In the template, we have four servers for coordinator and
-        datanode and we have four gtm proxy as well.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmProxyPorts</option></term>
-      <listitem>
-       <para>
-        Specify listening port number for each GTM proxy.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmProxyServers</option></term>
-      <listitem>
-       <para>
-        Specify host name where each of the GTM Proxy runs.
-        Specify server name as the same order as <literal>$gtmProxyNames</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>gtmPxySpecificExtraConfig</option></term>
-      <listitem>
-       <para>
-        If you'd like to add specific configuration value to each GTM
-        proxy, specify file names with  such lines for
-        <filename>gtm_proxy.conf</filename>.
-        Otherwise specify <literal>none</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-    </variablelist>
-
-   </sect3>
-
-   <sect3>
-    <title>Coordinators</title>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>coordArchLogDir</option></term>
-      <listitem>
-       <para>
-        Shortcut to assign the same WAL archive directory to all the
-        coordinator slaves.
-        Not needed if you specify these manually.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordArchLogDirs</option></term>
-      <listitem>
-       <para>
-        Array of WAL archive log directory for each datanode slave.
-        If you don't configure coordinator slaves and specify
-        coordSlave variable value to <literal>n</literal>, you don't
-        have to worry about this variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>coordExtraConfig</option></term>
-      <listitem>
-       <para>
-        If you would like to add extra configuration value for all the
-        coordinators, specify the file name containing such lines for
-        <filename>postgresql.conf</filename>.
-        Specify <literal>none</literal> otherwise.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordExtraPgHba</option></term>
-      <listitem>
-       <para>
-        File name which contains entries of
-        <filename>pg_hba.conf</filename> file for all the
-        coordinators.
-        Specify <literal>none</literal> if you do not have such file.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordMasterDir</option></term>
-      <listitem>
-       <para>
-        Shortcut to assign the same work directory to all the
-        coordinator masters.
-        Not needed if you specify these manually.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordMasterDirs</option></term>
-      <listitem>
-       <para>
-        Array of coordinator master work directory.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>coordMasterServers</option></term>
-      <listitem>
-       <para>
-        Array of the host name where each coordinator master runs.
-        Specify in the order of <option>coordNames</option> above.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordMaxWalSender</option></term>
-      <listitem>
-       <para>
-        Shortcut to assign the same value to each member of
-        <option>coordMaxWalSenders</option>.  Not needed if you assign the value
-          manually.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordMaxWalSenders</option></term>
-      <listitem>
-       <para>
-        Array of coordinator max_wal_senders value.
-        Note that a master and the slave shares the same value of this
-        variable. 
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordNames</option></term>
-      <listitem>
-       <para>
-        Array to specify coordinator names.
-        Coordinator slave uses the same name as the master.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordPgHbaEntries</option></term>
-      <listitem>
-       <para>
-        Array of CIDR addresses to be added to
-        <filename>pg_hba.conf</filename>.  
-        Will create pg_hba.conf file entry with
-        <option>pgxcOwner</option> user.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordPorts</option></term>
-      <listitem>
-       <para>
-        Array of the listening port number for each coordinator.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>poolerPorts</option></term>
-      <listitem>
-       <para>
-        Array of the port number for each pooler.  Pooler takes
-          care of the connection between coordinator and datanode and
-          needs separate port.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordSlave</option></term>
-      <listitem>
-       <para>
-        Specify <literal>y</literal> if you configure coordinator
-        slave.
-        <literal>n</literal> otherwise.   If you specify
-        <literal>n</literal>, then all the other variables for
-        coordinator slave will be ignored.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordSlaveDir</option></term>
-      <listitem>
-       <para>
-        Shortcut to assign the same work directory to all the
-          coordinator slaves.  Not needed if you specify these
-          manually.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>coordSlaveDirs</option></term>
-      <listitem>
-       <para>
-        Array of work directory for each coordinator slaves.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordSlaveServers</option></term>
-      <listitem>
-       <para>
-        Array of the hostname where slave of each
-          coordinator runs.  Specify <literal>none</literal> if you don't configure the
-          slave for specific coordinator.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordSlavePorts</option></term>
-      <listitem>
-       <para>
-        Array of the listening port number for each coordinator slave.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>coordSlavePoolerPorts</option></term>
-      <listitem>
-       <para>
-        Array of the port number for each pooler.  Pooler takes
-          care of the connection between coordinator and datanode and
-          needs separate port.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>coordSpecificExtraConfig</option></term>
-      <listitem>
-       <para>
-        Array of the filename which contains extra
-          configuration values for each coordinator.   Specify <literal>none</literal>
-          if you don't have such file.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-    </variablelist>
-
-   </sect3>
-
-   <sect3>
-    <title>Datanodes</title>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>datanodeArchLogDir</option></term>
-      <listitem>
-       <para>
-        Shortcut to assign the same WAL archive directory
-          to all the datanode slaves.  Not needed if you specify these
-          manually.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeArchLogDirs</option></term>
-      <listitem>
-       <para>
-        Array of WAL archive log directory for each datanode
-          slave.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeExtraConfig</option></term>
-      <listitem>
-       <para>
-        If you would like to add extra configuration value
-          for all the datanodes, specify the file name containing
-          such lines for postgresql.conf.  Specify <literal>none</literal> otherwise.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeExtraPgHba</option></term>
-      <listitem>
-       <para>
-        File name which contains entries for all the
-          datanodes' pg_hba.conf file.  Specify <literal>none</literal> if you don't
-          have such file.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeMasterDir</option></term>
-      <listitem>
-       <para>
-        Shortcut to assign the same work directory to all
-          the datanode masters.  Not needed if you specify these
-          manually.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeMasterDirs</option></term>
-      <listitem>
-       <para>
-        Array of datanode master work directory.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeMaterServers</option></term>
-      <listitem>
-       <para>
-        Array of the host name where each datanode master runs.
-          Specify in the order of $coordNames above.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeMaxWalSender</option></term>
-      <listitem>
-       <para>
-        shortcut to assign the same value to each member of
-          datanodeMaxWalSenders.  Not needed if you assign the value
-          manually.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeMaxWalSenders</option></term>
-      <listitem>
-       <para>
-        Array of datanode max_wal_senders value.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeNames</option></term>
-      <listitem>
-       <para>
-        Array to specify coordinator names.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodePgHbaEntries</option></term>
-      <listitem>
-       <para>
-        Array of CIDR addresses to be added to
-          pg_hba.conf.  Will create pg_hba.conf file entry with
-          $pgxcOwner user.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodePorts</option></term>
-      <listitem>
-       <para>
-        Array of the listening port number for each datanode.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>datanodePoolerPorts</option></term>
-      <listitem>
-       <para>
-        Array of the port number for each pooler.  Pooler takes
-          care of the connection between datanode and datanode and
-          needs separate port.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeSlave</option></term>
-      <listitem>
-       <para>
-        Specify <literal>y</literal> if you configure datanode slaves.  <literal>n</literal>
-          otherwise.   If you specify <literal>n</literal>, all the other variables for
-          datanode slaves will be ignored.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeSlaveDir</option></term>
-      <listitem>
-       <para>
-        Shortcut to assign the same work directory to all
-          the datanode slaves.  Not needed if you specify these
-          manually.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeSlaveDirs</option></term>
-      <listitem>
-       <para>
-        Array of work directory for each datanode slave.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeSlaveServers</option></term>
-      <listitem>
-       <para>
-        Array of the hostname where slave of each 
-          datanode runs.  Specify <literal>none</literal> if you don't configure the
-          slave for specific coordinator.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeSlavePorts</option></term>
-      <listitem>
-       <para>
-        Array of the listening port number for each datanode slave.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>datanodeSlavePoolerPorts</option></term>
-      <listitem>
-       <para>
-        Array of the port number for each pooler.  Pooler takes
-          care of the connection between datanode and datanode and
-          needs separate port.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeSpecificExtraConfig</option></term>
-      <listitem>
-       <para>
-        Array of the filename which contains extra
-          configuration values for each datanode.   Specify <literal>none</literal>
-          if you don't have such file.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>datanodeSpecificExtraPgHba</option></term>
-      <listitem>
-       <para>
-        Array of file names which contain specific
-          extra pg_hba.conf entry for each datanode.  Specify <literal>none</literal>
-          if you don't have such file.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><option>primaryDataode</option></term>
-      <listitem>
-       <para>
-        Specify name of the primary node.  This must be one of
-          the name in $datanodeNames.  If you don't want the primary
-          node, specify <literal>N/A</literal> or <literal>none</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-    </variablelist>
-
-   </sect3>
-
- 
- </sect2>
-
- <sect2>
-
-   <title>pgxc_ctl commands</title>
-
-   <para>
-    <application>pgxc_ctl</application> command names and literal options are case-insensitive.
-    Other options are case-sensitive.
-   </para>
-
-   <para>
-    If other command is given, it will be passed to your shell.
-    When the shell stops, then the control returns to <application>pgxc_ctl</application>.
-   </para>
-
-   <variablelist>
-
-   <varlistentry>
-    <term><literal>add gtm slave <replaceable class="parameter">name</replaceable> <replaceable class="parameter">host</replaceable> <replaceable class="parameter">port</replaceable> <replaceable class="parameter">dir</replaceable></literal></term>
-    <term><literal>add gtm_proxy <replaceable class="parameter">name</replaceable> <replaceable class="parameter">host</replaceable> <replaceable class="parameter">port</replaceable> <replaceable class="parameter">dir</replaceable></literal></term>
-    <term><literal>add coordinator master <replaceable class="parameter">name</replaceable> <replaceable class="parameter">host</replaceable> <replaceable class="parameter">port</replaceable> <replaceable class="parameter">pooler</replaceable> <replaceable class="parameter">dir</replaceable>< <replaceable class="parameter">extraServerConf</replaceable> <replaceable class="parameter">extraPgHbaConf</replaceable></literal></term>
-    <term><literal>add coordinator slave <replaceable class="parameter">name</replaceable> <replaceable class="parameter">host</replaceable> <replaceable class="parameter">port</replaceable> <replaceable class="parameter">pooler</replaceable> <replaceable class="parameter">dir</replaceable> <replaceable class="parameter">archDir</replaceable></literal></term>
-    <term><literal>add datanode master <replaceable class="parameter">name</replaceable> <replaceable class="parameter">host</replaceable>  <replaceable class="parameter">port</replaceable> <replaceable class="parameter">pooler</replaceable> <replaceable class="parameter">dir</replaceable>  <replaceable class="parameter">restoreDatanode</replaceable> <replaceable class="parameter">extraServerConf</replaceable> <replaceable class="parameter">extraPgHbaConf</replaceable></literal></term>
-    <term><literal>add datanode slave <replaceable class="parameter">name</replaceable> <replaceable class="parameter">host</replaceable>  <replaceable class="parameter">port</replaceable> <replaceable class="parameter">pooler</replaceable> <replaceable class="parameter">dir</replaceable> <replaceable class="parameter">archDir</replaceable></literal></term>
-    <listitem>
-     <para>
-      Add the specified node to your Postgres-XL cluster.
-      Each node need host name and its work directory.  gtm slave,
-      gtm_proxy, coordinator master/slave and datanode master/slave need its own port
-      to listen to.  Coordinator and datanode also need pooler port to pool
-	  connections to datanodes.  Coordinator and datanode slave need a
-	  directory to receive WAL segments from their master. While adding coordinator
-	  master and datanode master, extra server configuration and extra pg_hba
-	  configuration can be specified in a file.
-     </para>
-     <para>
-      When you add coordinator and datanode master, node information at
-      all the coordinators will be updated with the new one and gtm_proxy
-      will be selected automatically based upon where the new node runs.
-     </para>
-     <para>
-      You cannot add slaves without master.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Createdb [ - <replaceable class="parameter">coordinator</replaceable> ] <replaceable class="parameter"> createdb_option ... </replaceable></literal></term>
-    <listitem>
-     <para>
-   Invokes createdb utility to create a new database using specified
-   coordinator.  If no coordinator is specified, pgxc_ctl chooses one
-   of the available ones.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Createuser[ - <replaceable class="parameter">coordinator</replaceable> ] <replaceable class="parameter"> createuser_option ... </replaceable></literal></term>
-    <listitem>
-     <para>
-      Invokes createuser utility to create a new user using specified
-      coordinator.   Of coordinator is not specified, <application>pgxc_ctl</application> chooses
-      one of the available ones.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>deploy [ all | <replaceable class="parameter">host ...</replaceable> ]</literal></term>
-    <listitem>
-     <para>
-      Deploys Postgres-XL binaries and other installation material to
-      specified hosts.  If "all" is specified, they will be deployed to
-      all the hosts found in the configuration file.  If list of the host
-      is specifies, deployment will be done to all the specified hosts,
-      regardless if they are found in the configuration file or not.
-      Target directory is taken from the variable <option>pgxcInstallDir</option>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>failover [ gtm | coordinator <replaceable class="parameter">nodename</replaceable> | datanode <replaceable class="parameter">nodename</replaceable>  | <replaceable class="parameter">nodename</replaceable> ]</literal></term>
-    <listitem>
-     <para>
-      Failover specified node to its master.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>init [force] all</literal></term>
-    <term><literal>init [force] <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>init [force] gtm [ master | slave | all ]</literal></term>
-    <term><literal>init [force] gtm_proxy [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <term><literal>init [force] coordinator <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>init [force] coordinator [ master | slave ] [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <term><literal>init [force] datanode <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>init [force] datanode [ master | slave ] [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <listitem>
-     <para>
-   Initializes specified nodes.
-     </para>
-     <para>
-   At initialization, all the working directories of each component
-   will be created if it does not exist.  If it does and
-<literal>force</literal> is specified, then all the
-   contents under the working directory will be removed. Without
-<literal>force</literal> option, existing non-empty directories will not be
-cleaned and the server will start with the existing data.
-     </para>
-     <para>
-   When "all" option is specified, then node information at each
-   coordinator will be set up.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>kill all</literal></term>
-    <term><literal>kill <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>kill gtm [ master | slave | all ]</literal></term>
-    <term><literal>kill gtm_proxy [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <term><literal>kill coordinator <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>kill coordinator [ master | slave ] [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <term><literal>kill datanode <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>kill datanode [ master | slave ] [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <listitem>
-     <para>
-   Kills specified node.   If nodename is specified and it has both
-   master and slave, then both master and slave will be chosen.
-     </para>
-     <para>
-   When killing components, their ports will be cleaned too.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>log [ variable | var ] <replaceable class="parameter">varname</replaceable></literal></term>
-    <term><literal>log [ message | msg ] <replaceable class="parameter">message_body</replaceable></literal></term>
-    <listitem>
-     <para>
-   Prints the specified contents to the log file.
-   variable or var option writes specified variable name and its
-   value.
-   message or msg option writes specified message.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>monitor all</literal></term>
-    <term><literal>monitor <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>monitor gtm [ master | slave | all ]</literal></term>
-    <term><literal>monitor gtm_proxy [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <term><literal>monitor coordinator <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>monitor coordinator [ master | slave ] [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <term><literal>monitor datanode <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>monitor datanode [ master | slave ] [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <listitem>
-     <para>
- Monitors if specified nodes are running.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>prepare [ <replaceable class="parameter">path</replaceable> ]</literal></term>
-    <listitem>
-     <para>
-   Write pgxc_ctl configuration file template to the specified file.
-   If path option is not specified, target file will be default
-   configuration file, or the file specified by configFile option in
-   <filename>/etc/pgxc_ctl</filename> or <filename>~/.pgxc_ctl</filename>.   If you specify relative path, it
-   will be against <filename>pgxc_ctl_home</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>psql [ - <replaceable class="parameter">coordinator</replaceable> ] <replaceable class="parameter"> psql_option ... </replaceable></literal></term>
-    <term><literal></literal></term>
-    <listitem>
-     <para>
-   Invokes psql targetted to specified coordinator.   If no
-   coordinator is specifies, <application>pgxc_ctl</application> will choose one of the available
-   ones.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>q | quit | exit</literal></term>
-    <listitem>
-     <para>
-   Exits pgxc_ctl.  This command has no option.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>reconnect gtm_proxy [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <listitem>
-     <para>
-   Reconnects specified gtm_proxy to new gtm.   This is needed after
-   you failover gtm to its slave.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>remove gtm slave</literal></term>
-    <term><literal>remove gtm_proxy <replaceable class="parameter">nodename</replaceable> [ clean ]</literal></term>
-    <term><literal>remove coordinator [ master| slave ] <replaceable class="parameter">nodename</replaceable> [ clean ]</literal></term>
-    <term><literal>remove datanode [ master| slave ] <replaceable class="parameter">nodename</replaceable> [ clean ]</literal></term>
-    <listitem>
-     <para>
-   Removes the specified node from the cluster.
-   If clean option is specified, then the work directory and listening socket will be cleared.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>set <replaceable class="parameter">varname value ...</replaceable></literal></term>
-    <listitem>
-     <para>
-   Set variable value.  You can specify multiple values to a
-   variable.   In this case simply specify these values as separated
-   value.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>show [ variable | var ] [ all | <replaceable class="parameter">varname ...</replaceable> ]</literal></term>
-    <listitem>
-     <para>
-   Displays configuration or variable name and its value.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>start all</literal></term>
-    <term><literal>start <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>start gtm [ master | slave | all ]</literal></term>
-    <term><literal>start gtm_proxy [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <term><literal>start coordinator <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>start coordinator [ master | slave ] [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <term><literal>start datanode <replaceable class="parameter">nodename ...</replaceable></literal></term>
-    <term><literal>start datanode [ master | slave ] [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <listitem>
-     <para>
-   Starts specified node.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>stop [ -m smart | fast | immediate ] all</literal></term>
-    <term><literal>stop gtm [ master | slave | all ]</literal></term>
-    <term><literal>stop gtm_proxy [ all | <replaceable class="parameter">nodename ...</replaceable> ]</literal></term>
-    <term><literal>stop [ -m smart | fast | immediate ] coordinator <replaceable class="parameter">nodename ...</replaceable> </literal></term>
-    <term><literal>stop [ -m smart | fast | immediate ] coordinator [ master | slave ] [ all | <replaceable class="parameter">nodename ...</replaceable> ]  </literal></term>
-    <term><literal>stop [ -m smart | fast | immediate ] datanode <replaceable class="parameter">nodename ...</replaceable>  </literal></term>
-    <term><literal>stop [ -m smart | fast | immediate ] datanode [ master | slave ] [ all | <replaceable class="parameter">nodename ...</replaceable> ]  </literal></term>
-    <listitem>
-     <para>
-      Stops specified node.  For datanode and coordinator, you can
-      specify stop mode as in "pg_ctl stop" command.
-     </para>
-     <para>
-      When you stop coordinator or datanode slave, the master will be
-      reconfigured to remove synchronous replication.
-     </para>
-     <para>
-   When you stop coordinator or datanode slave, the master will be
-   reconfigurated to remove synchronous replication.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>unregister <replaceable class="parameter">unregister_option ...</replaceable></literal></term>
-    <listitem>
-     <para>
-   Unregisteres specified node from the gtm.  This could be needed
-   when some node crashes and would like to start new one.
-   
-     </para>
-     <para>
-   unregister_option is one of the following:
-   
-     </para>
-     <para>
-   <option>-n</option> <replaceable class="parameter">name</replaceable>: Specifies node name to unregister. 
-     </para>
-     <para>
-   <option>-Z</option> <literal>{ gtm | gtm_proxy | gtm_proxy_postmaster | coordinator | datanode }</literal>: 
-        Specifies the category of the specified node.
-
-     </para>
-    </listitem>
-   </varlistentry>
-
-   </variablelist>
- </sect2>
-</sect1>
diff --git a/doc-xc/src/sgml/pgxcclean.sgmlin b/doc-xc/src/sgml/pgxcclean.sgmlin
deleted file mode 100644
index 253b89a308..0000000000
--- a/doc-xc/src/sgml/pgxcclean.sgmlin
+++ /dev/null
@@ -1,211 +0,0 @@
-<!-- doc/src/sgml/pgxcclean.sgml -->
-
-<sect1 id="pgxcclean" xreflabel="pgxcclean">
-
-<title>pgxc_clean</title>
-
- <indexterm zone="pgxcclean">
-  <primary>pgxc_clean</primary>
- </indexterm>
-
- <sect2>
-  <title>Overview</title>
-
-&xlonly;
-    <para>
-      pgxc_clean has the following syntax.
-<programlisting>
-pgxc_clean <optional> <replaceable>option</> </optional> <optional><replaceable>dbname</><optional><replaceable>username</></optional></optional>
-</programlisting>
-    </para>
-
-    <para>
-     <application>pgxc_clean</application> is a Postgres-XL utility to maintain transaction status after a crash.
-     When a Postgres-XL node crashes and recovers or fails over, the commit status of such node may be inconsistent
-     with other nodes.   <application>pgxc_clean</application> checks transaction commit status and corrects them.
-    </para>
-
-    <para>
-     You should run this utility against one of the available Coordinators. The tool cleans up transaction status
-     of all the nodes automatically.
-    </para>
- </sect2>
-
- <sect2>
-  <title>Options</title>
-
-  <variablelist>
-    <varlistentry>
-      <term><option>-a</></term>
-      <term><option>--all</></term>
-      <listitem>
-      <para>
-       Cleanup all the database available.
-      <literal>all</literal>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-d<replaceable class="parameter">databasename</replaceable></option></term>
-      <term><option>--dbname=<replaceable class="parameter">databasename</replaceable></option></term>
-      <listitem>
-      <para>
-       Database name to clean up.  This option can be specified multiple times for more than one database.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-h<replaceable class="parameter">hostname</replaceable></></term>
-      <term><option>--command=<replaceable class="parameter">hostname</replaceable></></term>
-      <listitem>
-      <para>
-      Hostname of the Coordinator to connect to.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-N</></term>
-      <term><option>--no-clean</></term>
-      <listitem>
-      <para>
-       If this option is specified, <application>pgxc_clean</> will
-       not perform the cleanup.  It just investigates transaction status.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-o <replaceable class="parameter">filename</replaceable></></term>
-      <term><option>--output=<replaceable class="parameter">filename</replaceable></></term>
-      <listitem>
-      <para>
-       Name of the file where <application>pgxc_clean</> output will
-       be written.  If not specified, stdout and stderr will be used.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-p <replaceable class="parameter">port_number</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port_number</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies the port number of the Coordinator.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-q</></term>
-      <term><option>--quiet</></term>
-      <listitem>
-      <para>
-       Surpress messages as much as possible.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-s</></term>
-      <term><option>--status</></term>
-      <listitem>
-      <para>
-       Prints investigated two phase commit status.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-      <para>
-       User name to use.   You must be a superuser of the database.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-v</></term>
-      <term><option>--verbose</></term>
-      <listitem>
-      <para>
-       Write as much information as possible.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-V</></term>
-      <term><option>--version</></term>
-      <listitem>
-      <para>
-       Writes the version of the utility and exits.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-w</></term>
-     <term><option>--no-password</></term>
-     <listitem>
-      <para>
-       Never issue a password prompt.  If the server requires password
-       authentication and a password is not available by other means
-       such as a <filename>.pgpass</filename> file, the connection
-       attempt will fail.  This option can be useful in batch jobs and
-       scripts where no user is present to enter a password.
-      </para>
-
-      <para>
-       Note that this option will remain set for the entire session,
-       and so it affects uses of the meta-command
-       <command>\connect</command> as well as the initial connection attempt.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-      <para>
-       Force <application>psql</application> to prompt for a
-       password before connecting to a database.
-      </para>
-
-      <para>
-       This option is never essential, since <application>psql</application>
-       will automatically prompt for a password if the server demands
-       password authentication.  However, <application>psql</application>
-       will waste a connection attempt finding out that the server wants a
-       password.  In some cases it is worth typing <option>-W</> to avoid
-       the extra connection attempt.
-      </para>
-
-      <para>
-       Note that this option will remain set for the entire session,
-       and so it affects uses of the meta-command
-       <command>\connect</command> as well as the initial connection attempt.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-?</></term>
-      <term><option>--help</></term>
-      <listitem>
-      <para>
-      Show help about <application>psql</application> command line
-      arguments, and exit.
-      </para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/pgxcddl.sgmlin b/doc-xc/src/sgml/pgxcddl.sgmlin
deleted file mode 100644
index 70f268c56a..0000000000
--- a/doc-xc/src/sgml/pgxcddl.sgmlin
+++ /dev/null
@@ -1,189 +0,0 @@
-<!-- doc/src/sgml/pgxcddl.sgml -->
-
-<sect1 id="pgxcddl" xreflabel="pgxcddl">
-
-<title>pgxc_ddl</title>
-
- <indexterm zone="pgxcddl">
-  <primary>pgxc_ddl</primary>
- </indexterm>
-
- <sect2>
-  <title>
-   Overview
-  </title>
-&xlonly
-
-  <para>
-   pgxc_ddl is a module for Coordinator catalog table synchronization.
-   It has the following syntax.
-
-<programlisting>
-pgxc_ddl <optional> <replaceable>option</> </optional>
-</programlisting>
-  </para>
-
-  <para>
-   pgxc_ddl is used to synchronize all Coordinator catalog tables from
-   one chosen by a user. It is also possible to launch a DDL on one
-   Coordinator, and then to synchronize all the Coordinator catalog
-   tables from the catalog table of the Coordinator having received the
-   DDL. The copy method is "cold". All the Coordinators are stopped,
-   catalog files are copied, then all the Coordinators are restarted.
-  </para>
-
-  <para>
-   This utility is not really needed in  <productname>Postgres-XL</productname>; DDL is
-   synchronized automatically on all the nodes of the
-   cluster. 
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>Options</title>
-
-  <para>
-   Options are specified with preceding '<literal>-</literal>', each
-   option may be associated with a value.
-  </para>
-
-  <para>
-   Options are as follows:
-  </para>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><option>-D</option></term>
-     <listitem>
-      <para>
-       Specify <filename>pgxc.conf</filename> folder, for
-       characteristics of all the Coordinators.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-l</option></term>
-     <listitem>
-      <para>
-       Specify application folder, in case <varname>PATH</varname> is not defined.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-f</option></term>
-     <listitem>
-      <para>
-       Specify DDL file location.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-d</option></term>
-     <listitem>
-      <para>
-       Database name.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-n</option></term>
-     <listitem>
-      <para>
-       Coordinator number. Coordinator chosen corresponds to the one
-       defined in <filename>pgxc.conf</filename> at the nth place.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-t</option></term>
-     <listitem>
-      <para>
-       Specify temporary folder where to copy the configuration files
-       <filename>postgresql.conf</filename> and <filename>pg_hba.conf</filename>
-       for each Coordinator.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-
-  <para>
-   Because <command>pgxc_ddl</command> requires access to Coordinator
-   configuration file and data folders, the following parameters have
-   to be set in <filename>pgxc.conf</filename>:
-  </para>
-
-  <table>
-   <title><filename>pgxc.conf</filename> entries</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><varname>coordinator_ports</varname></entry>
-      <entry>string</entry>
-      <entry>
-       Specify the port number of all the Coordinators. Maintain the
-       order of the value same as those in coordinator_hosts. It is
-       necessary to specify a number of ports equal to the number of
-       hosts. A comma separator is also necessary.
-      </entry>
-     </row>
-
-     <row>
-      <entry><varname>coordinator_folders</varname></entry>
-      <entry>string</entry>
-      <entry>
-       Specify the data folders of all the Coordinators. Maintain the
-       order of the value same as those in coordinator_hosts. It is
-       necessary to specify a number of data folders equal to the
-       number of hosts. A comma separator is also necessary.
-      </entry>
-     </row>
-
-     <row>
-      <entry><varname>coordinator_hosts</varname></entry>
-      <entry>string</entry>
-      <entry>
-       Specify the host name or IP address of Coordinator. Separate
-       each value with comma.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <note>
-   <para>
-    About the temporary folder, this one has the name chosen by the
-    user. As an extension name, the PID of the shell script is
-    added. This folder is by default in <filename>/tmp</filename>. The user can choose
-    the name freely.
-   </para>
-  </note>
-
-  <note>
-   <para>
-    Configuration files of Coordinators that have their catalog files
-    changed are defined with an extension name postgresql.conf.number,
-    "number" being the number of t Coordinator in the order defined
-    in <filename>pgxc.conf</filename>.
-   </para>
-  </note>
- </sect2>
-</sect1>
diff --git a/doc-xc/src/sgml/pgxcmonitor.sgmlin b/doc-xc/src/sgml/pgxcmonitor.sgmlin
deleted file mode 100644
index f05fa7dfc9..0000000000
--- a/doc-xc/src/sgml/pgxcmonitor.sgmlin
+++ /dev/null
@@ -1,165 +0,0 @@
-<!-- doc/src/sgml/pgxcmonitor.sgml -->
-
-<sect1 id="pgxcmonitor" xreflabel="pgxcmonitor">
-
-<title>pgxc_monitor</title>
-
- <indexterm zone="pgxcmonitor">
-  <primary>pgxc_monitor</primary>
- </indexterm>
-
- <sect2>
-  <title>Overview</title>
-
-&xlonly;
-    <para>
-      pgxc_monitor has the following synopsis.
-<programlisting>
-pgxc_monitor <optional> <replaceable>option</> </optional>
-</programlisting>
-    </para>
-
-    <para>
-     <application>pgxc_monitor</application> is a <productname>Postgres-XL</> utility to test if
-     the target node is running.
-    </para>
-
-    <para>
-     The target node is specified by option.
-    </para>
-
-    <para>
-     If the target node is running, it exits with exit code zero.
-     If not, it exits with non-zero exit code.
-    </para>
-
-    <para>
-     If invalid options are specified, it exits with exit code 3.
-    </para>
- </sect2>
-
- <sect2>
-  <title>Options</title>
-
-  <variablelist>
-
-    <varlistentry>
-      <term><option>-Z <replaceable class="parameter">nodetype</replaceable></option></term>
-      <listitem>
-      <para>
-       Type of node type to test. Specify <literal>gtm</> as <replaceable>nodetype</replaceable>
-       for gtm and gtm_proxy and <literal>node</> as <replaceable>nodetype</replaceable> for a
-       Coordinator or a Datanode.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-h <replaceable class="parameter">hostname</replaceable></></term>
-      <listitem>
-      <para>
-      Hostname of the test target.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-n <replaceable class="parameter">nodename</replaceable></></term>
-      <listitem>
-      <para>
-      Node name to use when testing gtm or gtm_proxy.
-      Default value is <literal>pgxc_monitor</literal>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-p <replaceable class="parameter">port_number</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies the port number to test target.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies the database username to connect as.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-d <replaceable class="parameter">database</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies the database name to connect to. Default is "postgres".
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-q</></term>
-      <listitem>
-      <para>
-       Quiet mode. Supress messages as much as possible.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-v</></term>
-      <listitem>
-      <para>
-       Verbose mode. Prints as many messages as possible.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>--help</></term>
-      <listitem>
-      <para>
-      Show help about <application>pgxc_monitor</application> command line
-      arguments, and exit.
-      </para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
- </sect2>
-
- <sect2>
-  <title>Options</title>
-
-  <para>
-   When monitoring Coordinator or Datanode, <option>-p</option> and
-   <option>-h</option> options can be supplied using
-   <literal>.pgpass</literal> file.
-   If you use non-default target database name, and username, as well as
-   password, 
-   they must also be supplied using <option>.pgpass</option> file.
-  </para>
-  <para>
-   If password is needed, it must also be supplied using 
-   <option>.pgpass</option> file too.
-  </para>
-  <para>
-   Monitoring Coordinator and Datanode uses system(3) function.  
-   Therefore,you should not use set-userid bit or set-groupid bit.
-   Also, because this uses psql command, psql must be in your PATH.
-  </para>
-  <para>
-   The username and database name can be specified via command line
-   options too. If password is needed, it must be supplied via
-   <option>.pgpass</option> file though.
-  </para>
-  <para>
-   If invalid parameters are given, 
-   error message will be printed even if <option>-q</option> is specified.
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/planstats.sgmlin b/doc-xc/src/sgml/planstats.sgmlin
deleted file mode 100644
index afdecaca4e..0000000000
--- a/doc-xc/src/sgml/planstats.sgmlin
+++ /dev/null
@@ -1,454 +0,0 @@
-<!-- doc/src/sgml/planstats.sgml -->
-
-<chapter id="planner-stats-details">
- <title>How the Planner Uses Statistics</title>
-
-&pgnotice;
-
-  <para>
-   This chapter builds on the material covered in <xref
-   linkend="using-explain"> and <xref linkend="planner-stats"> to show some
-   additional details about how the planner uses the
-   system statistics to estimate the number of rows each part of a query might
-   return. This is a significant part of the planning process,
-   providing much of the raw material for cost calculation.
-  </para>
-
-  <para>
-   The intent of this chapter is not to document the code in detail,
-   but to present an overview of how it works.
-   This will perhaps ease the learning curve for someone who subsequently
-   wishes to read the code.
-  </para>
-
- <sect1 id="row-estimation-examples">
-  <title>Row Estimation Examples</title>
-
-  <indexterm zone="row-estimation-examples">
-   <primary>row estimation</primary>
-   <secondary>planner</secondary>
-  </indexterm>
-
-&pgnotice;
-  <para>
-   The examples shown below use tables in the <productname>PostgreSQL</>
-   regression test database.
-   The outputs shown are taken from version 8.3.
-   The behavior of earlier (or later) versions might vary.
-   Note also that since <command>ANALYZE</> uses random sampling
-   while producing statistics, the results will change slightly after
-   any new <command>ANALYZE</>.
-  </para>
-
-  <para>
-   Let's start with a very simple query:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1;
-
-                         QUERY PLAN
--------------------------------------------------------------
- Seq Scan on tenk1  (cost=0.00..458.00 rows=10000 width=244)
-</programlisting>
-
-   How the planner determines the cardinality of <structname>tenk1</structname>
-   is covered in <xref linkend="planner-stats">, but is repeated here for
-   completeness. The number of pages and rows is looked up in
-   <structname>pg_class</structname>:
-
-<programlisting>
-SELECT relpages, reltuples FROM pg_class WHERE relname = 'tenk1';
-
- relpages | reltuples
-----------+-----------
-      358 |     10000
-</programlisting>
-
-    These numbers are current as of the last <command>VACUUM</> or
-    <command>ANALYZE</> on the table.  The planner then fetches the
-    actual current number of pages in the table (this is a cheap operation,
-    not requiring a table scan).  If that is different from
-    <structfield>relpages</structfield> then
-    <structfield>reltuples</structfield> is scaled accordingly to
-    arrive at a current number-of-rows estimate.  In this case the values
-    are correct so the rows estimate is the same as
-    <structfield>reltuples</structfield>.
-  </para>
-
-  <para>
-   Let's move on to an example with a range condition in its
-   <literal>WHERE</literal> clause:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 WHERE unique1 &lt; 1000;
-
-                                   QUERY PLAN
---------------------------------------------------------------------------------
- Bitmap Heap Scan on tenk1  (cost=24.06..394.64 rows=1007 width=244)
-   Recheck Cond: (unique1 &lt; 1000)
-   -&gt;  Bitmap Index Scan on tenk1_unique1  (cost=0.00..23.80 rows=1007 width=0)
-         Index Cond: (unique1 &lt; 1000)
-</programlisting>
-
-   The planner examines the <literal>WHERE</literal> clause condition
-   and looks up the selectivity function for the operator
-   <literal>&lt;</literal> in <structname>pg_operator</structname>.
-   This is held in the column <structfield>oprrest</structfield>,
-   and the entry in this case is <function>scalarltsel</function>.
-   The <function>scalarltsel</function> function retrieves the histogram for
-   <structfield>unique1</structfield> from
-   <structname>pg_statistics</structname>.  For manual queries it is more
-   convenient to look in the simpler <structname>pg_stats</structname>
-   view:
-
-<programlisting>
-SELECT histogram_bounds FROM pg_stats
-WHERE tablename='tenk1' AND attname='unique1';
-
-                   histogram_bounds
-------------------------------------------------------
- {0,993,1997,3050,4040,5036,5957,7057,8029,9016,9995}
-</programlisting>
-
-   Next the fraction of the histogram occupied by <quote>&lt; 1000</quote>
-   is worked out. This is the selectivity. The histogram divides the range
-   into equal frequency buckets, so all we have to do is locate the bucket
-   that our value is in and count <emphasis>part</emphasis> of it and
-   <emphasis>all</emphasis> of the ones before. The value 1000 is clearly in
-   the second bucket (993-1997).  Assuming a linear distribution of
-   values inside each bucket, we can calculate the selectivity as:
-
-<programlisting>
-selectivity = (1 + (1000 - bucket[2].min)/(bucket[2].max - bucket[2].min))/num_buckets
-            = (1 + (1000 - 993)/(1997 - 993))/10
-            = 0.100697
-</programlisting>
-
-   that is, one whole bucket plus a linear fraction of the second, divided by
-   the number of buckets. The estimated number of rows can now be calculated as
-   the product of the selectivity and the cardinality of
-   <structname>tenk1</structname>:
-
-<programlisting>
-rows = rel_cardinality * selectivity
-     = 10000 * 0.100697
-     = 1007  (rounding off)
-</programlisting>
-  </para>
-
-  <para>
-   Next let's consider an example with an equality condition in its
-   <literal>WHERE</literal> clause:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 WHERE stringu1 = 'CRAAAA';
-
-                        QUERY PLAN
-----------------------------------------------------------
- Seq Scan on tenk1  (cost=0.00..483.00 rows=30 width=244)
-   Filter: (stringu1 = 'CRAAAA'::name)
-</programlisting>
-
-   Again the planner examines the <literal>WHERE</literal> clause condition
-   and looks up the selectivity function for <literal>=</literal>, which is
-   <function>eqsel</function>.  For equality estimation the histogram is
-   not useful; instead the list of <firstterm>most
-   common values</> (<acronym>MCV</acronym>s) is used to determine the
-   selectivity. Let's have a look at the MCVs, with some additional columns
-   that will be useful later:
-
-<programlisting>
-SELECT null_frac, n_distinct, most_common_vals, most_common_freqs FROM pg_stats
-WHERE tablename='tenk1' AND attname='stringu1';
-
-null_frac         | 0
-n_distinct        | 676
-most_common_vals  | {EJAAAA,BBAAAA,CRAAAA,FCAAAA,FEAAAA,GSAAAA,JOAAAA,MCAAAA,NAAAAA,WGAAAA}
-most_common_freqs | {0.00333333,0.003,0.003,0.003,0.003,0.003,0.003,0.003,0.003,0.003}
-
-</programlisting>
-
-   Since <literal>CRAAAA</> appears in the list of MCVs, the selectivity is
-   merely the corresponding entry in the list of most common frequencies
-   (<acronym>MCF</acronym>s):
-
-<programlisting>
-selectivity = mcf[3]
-            = 0.003
-</programlisting>
-
-   As before, the estimated number of rows is just the product of this with the
-   cardinality of <structname>tenk1</structname>:
-
-<programlisting>
-rows = 10000 * 0.003
-     = 30
-</programlisting>
-  </para>
-
-  <para>
-   Now consider the same query, but with a constant that is not in the
-   <acronym>MCV</acronym> list:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 WHERE stringu1 = 'xxx';
-
-                        QUERY PLAN
-----------------------------------------------------------
- Seq Scan on tenk1  (cost=0.00..483.00 rows=15 width=244)
-   Filter: (stringu1 = 'xxx'::name)
-</programlisting>
-
-   This is quite a different problem: how to estimate the selectivity when the
-   value is <emphasis>not</emphasis> in the <acronym>MCV</acronym> list.
-   The approach is to use the fact that the value is not in the list,
-   combined with the knowledge of the frequencies for all of the
-   <acronym>MCV</acronym>s:
-
-<programlisting>
-selectivity = (1 - sum(mvf))/(num_distinct - num_mcv)
-            = (1 - (0.00333333 + 0.003 + 0.003 + 0.003 + 0.003 + 0.003 +
-                    0.003 + 0.003 + 0.003 + 0.003))/(676 - 10)
-            = 0.0014559
-</programlisting>
-
-   That is, add up all the frequencies for the <acronym>MCV</acronym>s and
-   subtract them from one, then
-   divide by the number of <emphasis>other</emphasis> distinct values.
-   This amounts to assuming that the fraction of the column that is not any
-   of the MCVs is evenly distributed among all the other distinct values.
-   Notice that there are no null values so we don't have to worry about those
-   (otherwise we'd subtract the null fraction from the numerator as well).
-   The estimated number of rows is then calculated as usual:
-
-<programlisting>
-rows = 10000 * 0.0014559
-     = 15  (rounding off)
-</programlisting>
-  </para>
-
-  <para>
-   The previous example with <literal>unique1 &lt; 1000</> was an
-   oversimplification of what <function>scalarltsel</function> really does;
-   now that we have seen an example of the use of MCVs, we can fill in some
-   more detail.  The example was correct as far as it went, because since
-   <structfield>unique1</> is a unique column it has no MCVs (obviously, no
-   value is any more common than any other value).  For a non-unique
-   column, there will normally be both a histogram and an MCV list, and
-   <emphasis>the histogram does not include the portion of the column
-   population represented by the MCVs</>.  We do things this way because
-   it allows more precise estimation.  In this situation
-   <function>scalarltsel</function> directly applies the condition (e.g.,
-   <quote>&lt; 1000</>) to each value of the MCV list, and adds up the
-   frequencies of the MCVs for which the condition is true.  This gives
-   an exact estimate of the selectivity within the portion of the table
-   that is MCVs.  The histogram is then used in the same way as above
-   to estimate the selectivity in the portion of the table that is not
-   MCVs, and then the two numbers are combined to estimate the overall
-   selectivity.  For example, consider
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 WHERE stringu1 &lt; 'IAAAAA';
-
-                         QUERY PLAN
-------------------------------------------------------------
- Seq Scan on tenk1  (cost=0.00..483.00 rows=3077 width=244)
-   Filter: (stringu1 &lt; 'IAAAAA'::name)
-</programlisting>
-
-   We already saw the MCV information for <structfield>stringu1</>,
-   and here is its histogram:
-
-<programlisting>
-SELECT histogram_bounds FROM pg_stats
-WHERE tablename='tenk1' AND attname='stringu1';
-
-                                histogram_bounds
---------------------------------------------------------------------------------
- {AAAAAA,CQAAAA,FRAAAA,IBAAAA,KRAAAA,NFAAAA,PSAAAA,SGAAAA,VAAAAA,XLAAAA,ZZAAAA}
-</programlisting>
-
-   Checking the MCV list, we find that the condition <literal>stringu1 &lt;
-   'IAAAAA'</> is satisfied by the first six entries and not the last four,
-   so the selectivity within the MCV part of the population is
-
-<programlisting>
-selectivity = sum(relevant mvfs)
-            = 0.00333333 + 0.003 + 0.003 + 0.003 + 0.003 + 0.003
-            = 0.01833333
-</programlisting>
-
-   Summing all the MCFs also tells us that the total fraction of the
-   population represented by MCVs is 0.03033333, and therefore the
-   fraction represented by the histogram is 0.96966667 (again, there
-   are no nulls, else we'd have to exclude them here).  We can see
-   that the value <literal>IAAAAA</> falls nearly at the end of the
-   third histogram bucket.  Using some rather cheesy assumptions
-   about the frequency of different characters, the planner arrives
-   at the estimate 0.298387 for the portion of the histogram population
-   that is less than <literal>IAAAAA</>.  We then combine the estimates
-   for the MCV and non-MCV populations:
-
-<programlisting>
-selectivity = mcv_selectivity + histogram_selectivity * histogram_fraction
-            = 0.01833333 + 0.298387 * 0.96966667
-            = 0.307669
-
-rows        = 10000 * 0.307669
-            = 3077  (rounding off)
-</programlisting>
-
-   In this particular example, the correction from the MCV list is fairly
-   small, because the column distribution is actually quite flat (the
-   statistics showing these particular values as being more common than
-   others are mostly due to sampling error).  In a more typical case where
-   some values are significantly more common than others, this complicated
-   process gives a useful improvement in accuracy because the selectivity
-   for the most common values is found exactly.
-  </para>
-
-  <para>
-   Now let's consider a case with more than one
-   condition in the <literal>WHERE</literal> clause:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 WHERE unique1 &lt; 1000 AND stringu1 = 'xxx';
-
-                                   QUERY PLAN
---------------------------------------------------------------------------------
- Bitmap Heap Scan on tenk1  (cost=23.80..396.91 rows=1 width=244)
-   Recheck Cond: (unique1 &lt; 1000)
-   Filter: (stringu1 = 'xxx'::name)
-   -&gt;  Bitmap Index Scan on tenk1_unique1  (cost=0.00..23.80 rows=1007 width=0)
-         Index Cond: (unique1 &lt; 1000)
-</programlisting>
-
-   The planner assumes that the two conditions are independent, so that
-   the individual selectivities of the clauses can be multiplied together:
-
-<programlisting>
-selectivity = selectivity(unique1 &lt; 1000) * selectivity(stringu1 = 'xxx')
-            = 0.100697 * 0.0014559
-            = 0.0001466
-
-rows        = 10000 * 0.0001466
-            = 1  (rounding off)
-</programlisting>
-
-   Notice that the number of rows estimated to be returned from the bitmap
-   index scan reflects only the condition used with the index; this is
-   important since it affects the cost estimate for the subsequent heap
-   fetches.
-  </para>
-
-  <para>
-   Finally we will examine a query that involves a join:
-
-<programlisting>
-EXPLAIN SELECT * FROM tenk1 t1, tenk2 t2
-WHERE t1.unique1 &lt; 50 AND t1.unique2 = t2.unique2;
-
-                                      QUERY PLAN
---------------------------------------------------------------------------------------
- Nested Loop  (cost=4.64..456.23 rows=50 width=488)
-   -&gt;  Bitmap Heap Scan on tenk1 t1  (cost=4.64..142.17 rows=50 width=244)
-         Recheck Cond: (unique1 &lt; 50)
-         -&gt;  Bitmap Index Scan on tenk1_unique1  (cost=0.00..4.63 rows=50 width=0)
-               Index Cond: (unique1 &lt; 50)
-   -&gt;  Index Scan using tenk2_unique2 on tenk2 t2  (cost=0.00..6.27 rows=1 width=244)
-         Index Cond: (unique2 = t1.unique2)
-</programlisting>
-
-   The restriction on <structname>tenk1</structname>,
-   <literal>unique1 &lt; 50</literal>,
-   is evaluated before the nested-loop join.
-   This is handled analogously to the previous range example.  This time the
-   value 50 falls into the first bucket of the
-   <structfield>unique1</structfield> histogram:
-
-<programlisting>
-selectivity = (0 + (50 - bucket[1].min)/(bucket[1].max - bucket[1].min))/num_buckets
-            = (0 + (50 - 0)/(993 - 0))/10
-            = 0.005035
-
-rows        = 10000 * 0.005035
-            = 50  (rounding off)
-</programlisting>
-
-   The restriction for the join is <literal>t2.unique2 = t1.unique2</>.
-   The operator is just
-   our familiar <literal>=</literal>, however the selectivity function is
-   obtained from the <structfield>oprjoin</structfield> column of
-   <structname>pg_operator</structname>, and is <function>eqjoinsel</function>.
-   <function>eqjoinsel</function> looks up the statistical information for both
-   <structname>tenk2</structname> and <structname>tenk1</structname>:
-
-<programlisting>
-SELECT tablename, null_frac,n_distinct, most_common_vals FROM pg_stats
-WHERE tablename IN ('tenk1', 'tenk2') AND attname='unique2';
-
-tablename  | null_frac | n_distinct | most_common_vals
------------+-----------+------------+------------------
- tenk1     |         0 |         -1 |
- tenk2     |         0 |         -1 |
-</programlisting>
-
-   In this case there is no <acronym>MCV</acronym> information for
-   <structfield>unique2</structfield> because all the values appear to be
-   unique, so we use an algorithm that relies only on the number of
-   distinct values for both relations together with their null fractions:
-
-<programlisting>
-selectivity = (1 - null_frac1) * (1 - null_frac2) * min(1/num_distinct1, 1/num_distinct2)
-            = (1 - 0) * (1 - 0) / max(10000, 10000)
-            = 0.0001
-</programlisting>
-
-   This is, subtract the null fraction from one for each of the relations,
-   and divide by the maximum of the numbers of distinct values.
-   The number of rows
-   that the join is likely to emit is calculated as the cardinality of the
-   Cartesian product of the two inputs, multiplied by the
-   selectivity:
-
-<programlisting>
-rows = (outer_cardinality * inner_cardinality) * selectivity
-     = (50 * 10000) * 0.0001
-     = 50
-</programlisting>
-  </para>
-
-  <para>
-   Had there been MCV lists for the two columns,
-   <function>eqjoinsel</function> would have used direct comparison of the MCV
-   lists to determine the join selectivity within the part of the column
-   populations represented by the MCVs.  The estimate for the remainder of the
-   populations follows the same approach shown here.
-  </para>
-
-  <para>
-   Notice that we showed <literal>inner_cardinality</> as 10000, that is,
-   the unmodified size of <structname>tenk2</>.  It might appear from
-   inspection of the <command>EXPLAIN</> output that the estimate of
-   join rows comes from 50 * 1, that is, the number of outer rows times
-   the estimated number of rows obtained by each inner index scan on
-   <structname>tenk2</>.  But this is not the case: the join relation size
-   is estimated before any particular join plan has been considered.  If
-   everything is working well then the two ways of estimating the join
-   size will produce about the same answer, but due to roundoff error and
-   other factors they sometimes diverge significantly.
-  </para>
-
-  <para>
-   For those interested in further details, estimation of the size of
-   a table (before any <literal>WHERE</> clauses) is done in
-   <filename>src/backend/optimizer/util/plancat.c</filename>. The generic
-   logic for clause selectivities is in
-   <filename>src/backend/optimizer/path/clausesel.c</filename>.  The
-   operator-specific selectivity functions are mostly found
-   in <filename>src/backend/utils/adt/selfuncs.c</filename>.
-  </para>
-
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/plhandler.sgmlin b/doc-xc/src/sgml/plhandler.sgmlin
deleted file mode 100644
index fc0bf66053..0000000000
--- a/doc-xc/src/sgml/plhandler.sgmlin
+++ /dev/null
@@ -1,238 +0,0 @@
-<!-- doc/src/sgml/plhandler.sgml -->
-
- <chapter id="plhandler">
-   <title>Writing A Procedural Language Handler</title>
-
-   <indexterm zone="plhandler">
-    <primary>procedural language</primary>
-    <secondary>handler for</secondary>
-   </indexterm>
-
-&pgnotice;
-
-   <para>
-    All calls to functions that are written in a language other than
-    the current <quote>version 1</quote> interface for compiled
-    languages (this includes functions in user-defined procedural languages,
-    functions written in SQL, and functions using the version 0 compiled
-    language interface) go through a <firstterm>call handler</firstterm>
-    function for the specific language.  It is the responsibility of
-    the call handler to execute the function in a meaningful way, such
-    as by interpreting the supplied source text.  This chapter outlines
-    how a new procedural language's call handler can be written.
-   </para>
-
-   <para>
-    The call handler for a procedural language is a
-    <quote>normal</quote> function that must be written in a compiled
-    language such as C, using the version-1 interface, and registered
-    with <productname>PostgreSQL</productname> as taking no arguments
-    and returning the type <type>language_handler</type>.  This
-    special pseudotype identifies the function as a call handler and
-    prevents it from being called directly in SQL commands.
-    For more details on C language calling conventions and dynamic loading,
-    see <xref linkend="xfunc-c">.
-   </para>
-
-   <para>
-    The call handler is called in the same way as any other function:
-    It receives a pointer to a
-    <structname>FunctionCallInfoData</structname> <type>struct</> containing
-    argument values and information about the called function, and it
-    is expected to return a <type>Datum</type> result (and possibly
-    set the <structfield>isnull</structfield> field of the
-    <structname>FunctionCallInfoData</structname> structure, if it wishes
-    to return an SQL null result).  The difference between a call
-    handler and an ordinary callee function is that the
-    <structfield>flinfo-&gt;fn_oid</structfield> field of the
-    <structname>FunctionCallInfoData</structname> structure will contain
-    the OID of the actual function to be called, not of the call
-    handler itself.  The call handler must use this field to determine
-    which function to execute.  Also, the passed argument list has
-    been set up according to the declaration of the target function,
-    not of the call handler.
-   </para>
-
-   <para>
-    It's up to the call handler to fetch the entry of the function from the
-    <classname>pg_proc</classname> system catalog and to analyze the argument
-    and return types of the called function. The <literal>AS</> clause from the
-    <command>CREATE FUNCTION</command> command for the function will be found
-    in the <literal>prosrc</literal> column of the
-    <classname>pg_proc</classname> row. This is commonly source
-    text in the procedural language, but in theory it could be something else,
-    such as a path name to a file, or anything else that tells the call handler
-    what to do in detail.
-   </para>
-
-   <para>
-    Often, the same function is called many times per SQL statement.
-    A call handler can avoid repeated lookups of information about the
-    called function by using the
-    <structfield>flinfo-&gt;fn_extra</structfield> field.  This will
-    initially be <symbol>NULL</>, but can be set by the call handler to point at
-    information about the called function.  On subsequent calls, if
-    <structfield>flinfo-&gt;fn_extra</structfield> is already non-<symbol>NULL</>
-    then it can be used and the information lookup step skipped.  The
-    call handler must make sure that
-    <structfield>flinfo-&gt;fn_extra</structfield> is made to point at
-    memory that will live at least until the end of the current query,
-    since an <structname>FmgrInfo</structname> data structure could be
-    kept that long.  One way to do this is to allocate the extra data
-    in the memory context specified by
-    <structfield>flinfo-&gt;fn_mcxt</structfield>; such data will
-    normally have the same lifespan as the
-    <structname>FmgrInfo</structname> itself.  But the handler could
-    also choose to use a longer-lived memory context so that it can cache
-    function definition information across queries.
-   </para>
-
-   <para>
-    When a procedural-language function is invoked as a trigger, no arguments
-    are passed in the usual way, but the
-    <structname>FunctionCallInfoData</structname>'s
-    <structfield>context</structfield> field points at a
-    <structname>TriggerData</structname> structure, rather than being <symbol>NULL</>
-    as it is in a plain function call.  A language handler should
-    provide mechanisms for procedural-language functions to get at the trigger
-    information.
-   </para>
-
-   <para>
-    This is a template for a procedural-language handler written in C:
-<programlisting>
-#include "postgres.h"
-#include "executor/spi.h"
-#include "commands/trigger.h"
-#include "fmgr.h"
-#include "access/heapam.h"
-#include "utils/syscache.h"
-#include "catalog/pg_proc.h"
-#include "catalog/pg_type.h"
-
-#ifdef PG_MODULE_MAGIC
-PG_MODULE_MAGIC;
-#endif
-
-PG_FUNCTION_INFO_V1(plsample_call_handler);
-
-Datum
-plsample_call_handler(PG_FUNCTION_ARGS)
-{
-    Datum          retval;
-
-    if (CALLED_AS_TRIGGER(fcinfo))
-    {
-        /*
-         * Called as a trigger procedure
-         */
-        TriggerData    *trigdata = (TriggerData *) fcinfo-&gt;context;
-
-        retval = ...
-    }
-    else
-    {
-        /*
-         * Called as a function
-         */
-
-        retval = ...
-    }
-
-    return retval;
-}
-</programlisting>
-    Only a few thousand lines of code have to be added instead of the
-    dots to complete the call handler.
-   </para>
-
-   <para>
-    After having compiled the handler function into a loadable module
-    (see <xref linkend="dfunc">), the following commands then
-    register the sample procedural language:
-<programlisting>
-CREATE FUNCTION plsample_call_handler() RETURNS language_handler
-    AS '<replaceable>filename</replaceable>'
-    LANGUAGE C;
-CREATE LANGUAGE plsample
-    HANDLER plsample_call_handler;
-</programlisting>
-   </para>
-
-   <para>
-    Although providing a call handler is sufficient to create a minimal
-    procedural language, there are two other functions that can optionally
-    be provided to make the language more convenient to use.  These
-    are a <firstterm>validator</firstterm> and an
-    <firstterm>inline handler</firstterm>.  A validator can be provided
-    to allow language-specific checking to be done during
-    <xref linkend="sql-createfunction">.
-    An inline handler can be provided to allow the language to support
-    anonymous code blocks executed via the <xref linkend="sql-do"
-   > command.
-   </para>
-
-   <para>
-    If a validator is provided by a procedural language, it
-    must be declared as a function taking a single parameter of type
-    <type>oid</>.  The validator's result is ignored, so it is customarily
-    declared to return <type>void</>.  The validator will be called at
-    the end of a <command>CREATE FUNCTION</> command that has created
-    or updated a function written in the procedural language.
-    The passed-in OID is the OID of the function's <classname>pg_proc</>
-    row.  The validator must fetch this row in the usual way, and do
-    whatever checking is appropriate.  Typical checks include verifying
-    that the function's argument and result types are supported by the
-    language, and that the function's body is syntactically correct
-    in the language.  If the validator finds the function to be okay,
-    it should just return.  If it finds an error, it should report that
-    via the normal <function>ereport()</> error reporting mechanism.
-    Throwing an error will force a transaction rollback and thus prevent
-    the incorrect function definition from being committed.
-   </para>
-
-   <para>
-    Validator functions should typically honor the <xref
-    linkend="guc-check-function-bodies"> parameter: if it is turned off then
-    any expensive or context-sensitive checking should be skipped.
-    In particular, this parameter is turned off by <application>pg_dump</>
-    so that it can load procedural language functions without worrying
-    about possible dependencies of the function bodies on other database
-    objects.  (Because of this requirement, the call handler should avoid
-    assuming that the validator has fully checked the function.  The point
-    of having a validator is not to let the call handler omit checks, but
-    to notify the user immediately if there are obvious errors in a
-    <command>CREATE FUNCTION</> command.)
-   </para>
-
-   <para>
-    If an inline handler is provided by a procedural language, it
-    must be declared as a function taking a single parameter of type
-    <type>internal</>.  The inline handler's result is ignored, so it is
-    customarily declared to return <type>void</>.  The inline handler
-    will be called when a <command>DO</> statement is executed specifying
-    the procedural language.  The parameter actually passed is a pointer
-    to an <structname>InlineCodeBlock</> struct, which contains information
-    about the <command>DO</> statement's parameters, in particular the
-    text of the anonymous code block to be executed.  The inline handler
-    should execute this code and return.
-   </para>
-
-   <para>
-    It's recommended that you wrap all these function declarations,
-    as well as the <command>CREATE LANGUAGE</> command itself, into
-    an <firstterm>extension</> so that a simple <command>CREATE EXTENSION</>
-    command is sufficient to install the language.  See
-    <xref linkend="extend-extensions"> for information about writing
-    extensions.
-   </para>
-
-   <para>
-    The procedural languages included in the standard distribution
-    are good references when trying to write your own language handler.
-    Look into the <filename>src/pl</> subdirectory of the source tree.
-    The <xref linkend="sql-createlanguage">
-    reference page also has some useful details.
-   </para>
-
- </chapter>
diff --git a/doc-xc/src/sgml/plperl.sgmlin b/doc-xc/src/sgml/plperl.sgmlin
deleted file mode 100644
index 9698cdf6b1..0000000000
--- a/doc-xc/src/sgml/plperl.sgmlin
+++ /dev/null
@@ -1,1425 +0,0 @@
-<!-- doc/src/sgml/plperl.sgml -->
-
- <chapter id="plperl">
-  <title>PL/Perl - Perl Procedural Language</title>
-
-  <indexterm zone="plperl">
-   <primary>PL/Perl</primary>
-  </indexterm>
-
-  <indexterm zone="plperl">
-   <primary>Perl</primary>
-  </indexterm>
-
-&common;
-
-  <para>
-   PL/Perl is a loadable procedural language that enables you to write
-   <productname>PostgreSQL</productname> functions in the
-   <ulink url="http://www.perl.org">Perl programming language</ulink>.
-  </para>
-
-  <para>
-   The main advantage to using PL/Perl is that this allows use,
-   within stored functions, of the manyfold <quote>string
-   munging</quote> operators and functions available for Perl.  Parsing
-   complex strings might be easier using Perl than it is with the
-   string functions and control structures provided in PL/pgSQL.
-  </para>
-
-  <para>
-   To install PL/Perl in a particular database, use
-   <literal>CREATE EXTENSION plperl</>, or from the shell command line use
-   <literal>createlang plperl <replaceable>dbname</></literal>.
-  </para>
-
-  <tip>
-   <para>
-    If a language is installed into <literal>template1</>, all subsequently
-    created databases will have the language installed automatically.
-   </para>
-  </tip>
-
-  <note>
-   <para>
-    Users of source packages must specially enable the build of
-    PL/Perl during the installation process.  (Refer to <xref
-    linkend="installation"> for more information.)  Users of
-    binary packages might find PL/Perl in a separate subpackage.
-   </para>
-  </note>
-
- <sect1 id="plperl-funcs">
-  <title>PL/Perl Functions and Arguments</title>
-
-&common;
-  <para>
-   To create a function in the PL/Perl language, use the standard
-   <xref linkend="sql-createfunction">
-   syntax:
-
-<programlisting>
-CREATE FUNCTION <replaceable>funcname</replaceable> (<replaceable>argument-types</replaceable>) RETURNS <replaceable>return-type</replaceable> AS $$
-    # PL/Perl function body
-$$ LANGUAGE plperl;
-</programlisting>
-
-   The body of the function is ordinary Perl code. In fact, the PL/Perl
-   glue code wraps it inside a Perl subroutine.  A PL/Perl function is
-   called in a scalar context, so it can't return a list.  You can return
-   non-scalar values (arrays, records, and sets) by returning a reference,
-   as discussed below.
-  </para>
-
-  <para>
-   PL/Perl also supports anonymous code blocks called with the
-   <xref linkend="sql-do"> statement:
-
-<programlisting>
-DO $$
-    # PL/Perl code
-$$ LANGUAGE plperl;
-</programlisting>
-
-   An anonymous code block receives no arguments, and whatever value it
-   might return is discarded.  Otherwise it behaves just like a function.
-  </para>
-
-  <note>
-   <para>
-    The use of named nested subroutines is dangerous in Perl, especially if
-    they refer to lexical variables in the enclosing scope. Because a PL/Perl
-    function is wrapped in a subroutine, any named subroutine you place inside
-    one will be nested. In general, it is far safer to create anonymous
-    subroutines which you call via a coderef. For more information, see the
-    entries for <literal>Variable "%s" will not stay shared</literal> and
-    <literal>Variable "%s" is not available</literal> in the
-    <citerefentry><refentrytitle>perldiag</></citerefentry> man page, or
-    search the Internet for <quote>perl nested named subroutine</>.
-   </para>
-  </note>
-
-  <para>
-   The syntax of the <command>CREATE FUNCTION</command> command requires
-   the function body to be written as a string constant.  It is usually
-   most convenient to use dollar quoting (see <xref
-   linkend="sql-syntax-dollar-quoting">) for the string constant.
-   If you choose to use escape string syntax <literal>E''</>,
-   you must double any single quote marks (<literal>'</>) and backslashes
-   (<literal>\</>) used in the body of the function
-   (see <xref linkend="sql-syntax-strings">).
-  </para>
-
-  <para>
-   Arguments and results are handled as in any other Perl subroutine:
-   arguments are passed in <varname>@_</varname>, and a result value
-   is returned with <literal>return</> or as the last expression
-   evaluated in the function.
-  </para>
-
-  <para>
-   For example, a function returning the greater of two integer values
-   could be defined as:
-
-<programlisting>
-CREATE FUNCTION perl_max (integer, integer) RETURNS integer AS $$
-    if ($_[0] &gt; $_[1]) { return $_[0]; }
-    return $_[1];
-$$ LANGUAGE plperl;
-</programlisting>
-  </para>
-
-  <note>
-    <para>
-      Arguments will be converted from the database's encoding to UTF-8
-      for use inside PL/Perl, and then converted from UTF-8 back to the
-      database encoding upon return.
-    </para>
-  </note>
-
-  <para>
-   If an SQL null value<indexterm><primary>null value</><secondary
-   sortas="PL/Perl">in PL/Perl</></indexterm> is passed to a function,
-   the argument value will appear as <quote>undefined</> in Perl.  The
-   above function definition will not behave very nicely with null
-   inputs (in fact, it will act as though they are zeroes).  We could
-   add <literal>STRICT</> to the function definition to make
-   <productname>PostgreSQL</productname> do something more reasonable:
-   if a null value is passed, the function will not be called at all,
-   but will just return a null result automatically.  Alternatively,
-   we could check for undefined inputs in the function body.  For
-   example, suppose that we wanted <function>perl_max</function> with
-   one null and one nonnull argument to return the nonnull argument,
-   rather than a null value:
-
-<programlisting>
-CREATE FUNCTION perl_max (integer, integer) RETURNS integer AS $$
-    my ($x, $y) = @_;
-    if (not defined $x) {
-        return undef if not defined $y;
-        return $y;
-    }
-    return $x if not defined $y;
-    return $x if $x &gt; $y;
-    return $y;
-$$ LANGUAGE plperl;
-</programlisting>
-   As shown above, to return an SQL null value from a PL/Perl
-   function, return an undefined value.  This can be done whether the
-   function is strict or not.
-  </para>
-
-  <para>
-   Anything in a function argument that is not a reference is
-   a string, which is in the standard <productname>PostgreSQL</productname>
-   external text representation for the relevant data type. In the case of
-   ordinary numeric or text types, Perl will just do the right thing and
-   the programmer will normally not have to worry about it. However, in
-   other cases the argument will need to be converted into a form that is
-   more usable in Perl. For example, the <function>decode_bytea</function>
-   function can be used to convert an argument of
-   type <type>bytea</> into unescaped binary.
-  </para>
-
-  <para>
-   Similarly, values passed back to <productname>PostgreSQL</productname>
-   must be in the external text representation format. For example, the
-   <function>encode_bytea</function> function can be used to
-   escape binary data for a return value of type <type>bytea</>.
-  </para>
-
-  <para>
-   Perl can return <productname>PostgreSQL</productname> arrays as
-   references to Perl arrays.  Here is an example:
-
-<programlisting>
-CREATE OR REPLACE function returns_array()
-RETURNS text[][] AS $$
-    return [['a&quot;b','c,d'],['e\\f','g']];
-$$ LANGUAGE plperl;
-
-select returns_array();
-</programlisting>
-  </para>
-
-  <para>
-   Perl passes <productname>PostgreSQL</productname> arrays as a blessed
-   PostgreSQL::InServer::ARRAY object. This object may be treated as an array
-   reference or a string, allowing for backward compatibility with Perl
-   code written for <productname>PostgreSQL</productname> versions below 9.1 to
-   run.  For example:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION concat_array_elements(text[]) RETURNS TEXT AS $$
-    my $arg = shift;
-    my $result = "";
-    return undef if (!defined $arg);
-
-    # as an array reference
-    for (@$arg) {
-        $result .= $_;
-    }
-
-    # also works as a string
-    $result .= $arg;
-
-    return $result;
-$$ LANGUAGE plperl;
-
-SELECT concat_array_elements(ARRAY['PL','/','Perl']);
-</programlisting>
-
-  <note>
-   <para>
-    Multi-dimensional arrays are represented as references to
-    lower-dimensional arrays of references in a way common to every Perl
-    programmer.
-   </para>
-  </note>
-  </para>
-
-  <para>
-   Composite-type arguments are passed to the function as references
-   to hashes.  The keys of the hash are the attribute names of the
-   composite type.  Here is an example:
-
-<programlisting>
-CREATE TABLE employee (
-    name text,
-    basesalary integer,
-    bonus integer
-);
-
-CREATE FUNCTION empcomp(employee) RETURNS integer AS $$
-    my ($emp) = @_;
-    return $emp-&gt;{basesalary} + $emp-&gt;{bonus};
-$$ LANGUAGE plperl;
-
-SELECT name, empcomp(employee.*) FROM employee;
-</programlisting>
-  </para>
-
-  <para>
-   A PL/Perl function can return a composite-type result using the same
-   approach: return a reference to a hash that has the required attributes.
-   For example:
-
-<programlisting>
-CREATE TYPE testrowperl AS (f1 integer, f2 text, f3 text);
-
-CREATE OR REPLACE FUNCTION perl_row() RETURNS testrowperl AS $$
-    return {f2 =&gt; 'hello', f1 =&gt; 1, f3 =&gt; 'world'};
-$$ LANGUAGE plperl;
-
-SELECT * FROM perl_row();
-</programlisting>
-
-   Any columns in the declared result data type that are not present in the
-   hash will be returned as null values.
-  </para>
-
-  <para>
-    PL/Perl functions can also return sets of either scalar or
-    composite types.  Usually you'll want to return rows one at a
-    time, both to speed up startup time and to keep from queueing up
-    the entire result set in memory.  You can do this with
-    <function>return_next</function> as illustrated below.  Note that
-    after the last <function>return_next</function>, you must put
-    either <literal>return</literal> or (better) <literal>return
-    undef</literal>.
-
-<programlisting>
-CREATE OR REPLACE FUNCTION perl_set_int(int)
-RETURNS SETOF INTEGER AS $$
-    foreach (0..$_[0]) {
-        return_next($_);
-    }
-    return undef;
-$$ LANGUAGE plperl;
-
-SELECT * FROM perl_set_int(5);
-
-CREATE OR REPLACE FUNCTION perl_set()
-RETURNS SETOF testrowperl AS $$
-    return_next({ f1 =&gt; 1, f2 =&gt; 'Hello', f3 =&gt; 'World' });
-    return_next({ f1 =&gt; 2, f2 =&gt; 'Hello', f3 =&gt; 'PostgreSQL' });
-    return_next({ f1 =&gt; 3, f2 =&gt; 'Hello', f3 =&gt; 'PL/Perl' });
-    return undef;
-$$ LANGUAGE plperl;
-</programlisting>
-
-    For small result sets, you can return a reference to an array that
-    contains either scalars, references to arrays, or references to
-    hashes for simple types, array types, and composite types,
-    respectively.  Here are some simple examples of returning the entire
-    result set as an array reference:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION perl_set_int(int) RETURNS SETOF INTEGER AS $$
-    return [0..$_[0]];
-$$ LANGUAGE plperl;
-
-SELECT * FROM perl_set_int(5);
-
-CREATE OR REPLACE FUNCTION perl_set() RETURNS SETOF testrowperl AS $$
-    return [
-        { f1 =&gt; 1, f2 =&gt; 'Hello', f3 =&gt; 'World' },
-        { f1 =&gt; 2, f2 =&gt; 'Hello', f3 =&gt; 'PostgreSQL' },
-        { f1 =&gt; 3, f2 =&gt; 'Hello', f3 =&gt; 'PL/Perl' }
-    ];
-$$ LANGUAGE plperl;
-
-SELECT * FROM perl_set();
-</programlisting>
-  </para>
-
-  <para>
-   If you wish to use the <literal>strict</> pragma with your code you
-   have a few options. For temporary global use you can <command>SET</>
-   <literal>plperl.use_strict</literal> to true.
-   This will affect subsequent compilations of <application>PL/Perl</>
-   functions, but not functions already compiled in the current session.
-   For permanent global use you can set <literal>plperl.use_strict</literal>
-   to true in the <filename>postgresql.conf</filename> file.
-  </para>
-
-  <para>
-   For permanent use in specific functions you can simply put:
-<programlisting>
-use strict;
-</programlisting>
-   at the top of the function body.
-  </para>
-
-  <para>
-  The <literal>feature</> pragma is also available to <function>use</> if your Perl is version 5.10.0 or higher.
-  </para>
-
- </sect1>
-
- <sect1 id="plperl-data">
-  <title>Data Values in PL/Perl</title>
-
-&pgnotice;
-  <para>
-   The argument values supplied to a PL/Perl function's code are
-   simply the input arguments converted to text form (just as if they
-   had been displayed by a <command>SELECT</command> statement).
-   Conversely, the <function>return</function> and <function>return_next</function>
-   commands will accept any string that is acceptable input format
-   for the function's declared return type.
-  </para>
- </sect1>
-
- <sect1 id="plperl-builtins">
-  <title>Built-in Functions</title>
-
- <sect2 id="plperl-database">
-  <title>Database Access from PL/Perl</title>
-
-&pgnotice;
-  <para>
-   Access to the database itself from your Perl function can be done
-   via the following functions:
-  </para>
-
-   <variablelist>
-    <varlistentry>
-     <indexterm>
-      <primary>spi_exec_query</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-     <indexterm>
-      <primary>spi_query</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-     <indexterm>
-      <primary>spi_fetchrow</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-     <indexterm>
-      <primary>spi_prepare</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-     <indexterm>
-      <primary>spi_exec_prepared</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-     <indexterm>
-      <primary>spi_query_prepared</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-     <indexterm>
-      <primary>spi_cursor_close</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-     <indexterm>
-      <primary>spi_freeplan</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>spi_exec_query</>(<replaceable>query</replaceable> [, <replaceable>max-rows</replaceable>])</literal></term>
-     <listitem>
-      <para>
-       <literal>spi_exec_query</literal> executes an SQL command and
-returns the entire row set as a reference to an array of hash
-references.  <emphasis>You should only use this command when you know
-that the result set will be relatively small.</emphasis>  Here is an
-example of a query (<command>SELECT</command> command) with the
-optional maximum number of rows:
-
-<programlisting>
-$rv = spi_exec_query('SELECT * FROM my_table', 5);
-</programlisting>
-        This returns up to 5 rows from the table
-        <literal>my_table</literal>.  If <literal>my_table</literal>
-        has a column <literal>my_column</literal>, you can get that
-        value from row <literal>$i</literal> of the result like this:
-<programlisting>
-$foo = $rv-&gt;{rows}[$i]-&gt;{my_column};
-</programlisting>
-       The total number of rows returned from a <command>SELECT</command>
-       query can be accessed like this:
-<programlisting>
-$nrows = $rv-&gt;{processed}
-</programlisting>
-      </para>
-
-      <para>
-       Here is an example using a different command type:
-<programlisting>
-$query = "INSERT INTO my_table VALUES (1, 'test')";
-$rv = spi_exec_query($query);
-</programlisting>
-       You can then access the command status (e.g.,
-       <literal>SPI_OK_INSERT</literal>) like this:
-<programlisting>
-$res = $rv-&gt;{status};
-</programlisting>
-       To get the number of rows affected, do:
-<programlisting>
-$nrows = $rv-&gt;{processed};
-</programlisting>
-      </para>
-
-      <para>
-       Here is a complete example:
-<programlisting>
-CREATE TABLE test (
-    i int,
-    v varchar
-);
-
-INSERT INTO test (i, v) VALUES (1, 'first line');
-INSERT INTO test (i, v) VALUES (2, 'second line');
-INSERT INTO test (i, v) VALUES (3, 'third line');
-INSERT INTO test (i, v) VALUES (4, 'immortal');
-
-CREATE OR REPLACE FUNCTION test_munge() RETURNS SETOF test AS $$
-    my $rv = spi_exec_query('select i, v from test;');
-    my $status = $rv-&gt;{status};
-    my $nrows = $rv-&gt;{processed};
-    foreach my $rn (0 .. $nrows - 1) {
-        my $row = $rv-&gt;{rows}[$rn];
-        $row-&gt;{i} += 200 if defined($row-&gt;{i});
-        $row-&gt;{v} =~ tr/A-Za-z/a-zA-Z/ if (defined($row-&gt;{v}));
-        return_next($row);
-    }
-    return undef;
-$$ LANGUAGE plperl;
-
-SELECT * FROM test_munge();
-</programlisting>
-    </para>
-    </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal><function>spi_query(<replaceable>command</replaceable>)</function></literal></term>
-     <term><literal><function>spi_fetchrow(<replaceable>cursor</replaceable>)</function></literal></term>
-     <term><literal><function>spi_cursor_close(<replaceable>cursor</replaceable>)</function></literal></term>
-
-    <listitem>
-    <para>
-    <literal>spi_query</literal> and <literal>spi_fetchrow</literal>
-    work together as a pair for row sets which might be large, or for cases
-    where you wish to return rows as they arrive.
-    <literal>spi_fetchrow</literal> works <emphasis>only</emphasis> with
-    <literal>spi_query</literal>. The following example illustrates how
-    you use them together:
-
-<programlisting>
-CREATE TYPE foo_type AS (the_num INTEGER, the_text TEXT);
-
-CREATE OR REPLACE FUNCTION lotsa_md5 (INTEGER) RETURNS SETOF foo_type AS $$
-    use Digest::MD5 qw(md5_hex);
-    my $file = '/usr/share/dict/words';
-    my $t = localtime;
-    elog(NOTICE, "opening file $file at $t" );
-    open my $fh, '&lt;', $file # ooh, it's a file access!
-        or elog(ERROR, "cannot open $file for reading: $!");
-    my @words = &lt;$fh&gt;;
-    close $fh;
-    $t = localtime;
-    elog(NOTICE, "closed file $file at $t");
-    chomp(@words);
-    my $row;
-    my $sth = spi_query("SELECT * FROM generate_series(1,$_[0]) AS b(a)");
-    while (defined ($row = spi_fetchrow($sth))) {
-        return_next({
-            the_num =&gt; $row-&gt;{a},
-            the_text =&gt; md5_hex($words[rand @words])
-        });
-    }
-    return;
-$$ LANGUAGE plperlu;
-
-SELECT * from lotsa_md5(500);
-</programlisting>
-    </para>
-
-    <para>
-     Normally, <function>spi_fetchrow</> should be repeated until it
-     returns <literal>undef</literal>, indicating that there are no more
-     rows to read.  The cursor returned by <literal>spi_query</literal>
-     is automatically freed when
-     <function>spi_fetchrow</> returns <literal>undef</literal>.
-     If you do not wish to read all the rows, instead call
-     <function>spi_cursor_close</> to free the cursor.
-     Failure to do so will result in memory leaks.
-    </para>
-
-    </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal><function>spi_prepare(<replaceable>command</replaceable>, <replaceable>argument types</replaceable>)</function></literal></term>
-     <term><literal><function>spi_query_prepared(<replaceable>plan</replaceable>, <replaceable>arguments</replaceable>)</function></literal></term>
-     <term><literal><function>spi_exec_prepared(<replaceable>plan</replaceable> [, <replaceable>attributes</replaceable>], <replaceable>arguments</replaceable>)</function></literal></term>
-     <term><literal><function>spi_freeplan(<replaceable>plan</replaceable>)</function></literal></term>
-
-    <listitem>
-<!## PG>
-<!-- NOTICE:
-     No prepare support yet.
--->
-    <para>
-    <literal>spi_prepare</literal>, <literal>spi_query_prepared</literal>, <literal>spi_exec_prepared</literal>,
-    and <literal>spi_freeplan</literal> implement the same functionality but for prepared queries.
-    <literal>spi_prepare</literal> accepts a query string with numbered argument placeholders ($1, $2, etc)
-    and a string list of argument types:
-<programlisting>
-$plan = spi_prepare('SELECT * FROM test WHERE id &gt; $1 AND name = $2',
-                                                     'INTEGER', 'TEXT');
-</programlisting>
-    Once a query plan is prepared by a call to <literal>spi_prepare</literal>, the plan can be used instead
-    of the string query, either in <literal>spi_exec_prepared</literal>, where the result is the same as returned
-    by <literal>spi_exec_query</literal>, or in <literal>spi_query_prepared</literal> which returns a cursor
-    exactly as <literal>spi_query</literal> does, which can be later passed to <literal>spi_fetchrow</literal>.
-    The optional second parameter to <literal>spi_exec_prepared</literal> is a hash reference of attributes;
-    the only attribute currently supported is <literal>limit</literal>, which sets the maximum number of rows returned by a query.
-    </para>
-
-    <para>
-    The advantage of prepared queries is that is it possible to use one prepared plan for more
-    than one query execution. After the plan is not needed anymore, it can be freed with
-    <literal>spi_freeplan</literal>:
-<programlisting>
-CREATE OR REPLACE FUNCTION init() RETURNS VOID AS $$
-        $_SHARED{my_plan} = spi_prepare('SELECT (now() + $1)::date AS now',
-                                        'INTERVAL');
-$$ LANGUAGE plperl;
-
-CREATE OR REPLACE FUNCTION add_time( INTERVAL ) RETURNS TEXT AS $$
-        return spi_exec_prepared(
-                $_SHARED{my_plan},
-                $_[0]
-        )->{rows}->[0]->{now};
-$$ LANGUAGE plperl;
-
-CREATE OR REPLACE FUNCTION done() RETURNS VOID AS $$
-        spi_freeplan( $_SHARED{my_plan});
-        undef $_SHARED{my_plan};
-$$ LANGUAGE plperl;
-
-SELECT init();
-SELECT add_time('1 day'), add_time('2 days'), add_time('3 days');
-SELECT done();
-
-  add_time  |  add_time  |  add_time
-------------+------------+------------
- 2005-12-10 | 2005-12-11 | 2005-12-12
-</programlisting>
-    Note that the parameter subscript in <literal>spi_prepare</literal> is defined via
-    $1, $2, $3, etc, so avoid declaring query strings in double quotes that might easily
-    lead to hard-to-catch bugs.
-    </para>
-
-    <para>
-    Another example illustrates usage of an optional parameter in <literal>spi_exec_prepared</literal>:
-<programlisting>
-CREATE TABLE hosts AS SELECT id, ('192.168.1.'||id)::inet AS address
-                      FROM generate_series(1,3) AS id;
-
-CREATE OR REPLACE FUNCTION init_hosts_query() RETURNS VOID AS $$
-        $_SHARED{plan} = spi_prepare('SELECT * FROM hosts
-                                      WHERE address &lt;&lt; $1', 'inet');
-$$ LANGUAGE plperl;
-
-CREATE OR REPLACE FUNCTION query_hosts(inet) RETURNS SETOF hosts AS $$
-        return spi_exec_prepared(
-                $_SHARED{plan},
-                {limit =&gt; 2},
-                $_[0]
-        )->{rows};
-$$ LANGUAGE plperl;
-
-CREATE OR REPLACE FUNCTION release_hosts_query() RETURNS VOID AS $$
-        spi_freeplan($_SHARED{plan});
-        undef $_SHARED{plan};
-$$ LANGUAGE plperl;
-
-SELECT init_hosts_query();
-SELECT query_hosts('192.168.1.0/30');
-SELECT release_hosts_query();
-
-    query_hosts    
------------------
- (1,192.168.1.1)
- (2,192.168.1.2)
-(2 rows)
-</programlisting>
-    </para>
-<!## end>
-<!## XC>
-&xconly;
-     <para>
-      <command>PREPARE</> is not supported in the current release
-      of <productname>Postgres-XC</>.  This may be supported in the
-      future releases.
-     </para>
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      <command>PREPARE</> is not supported in the current release
-      of <productname>Postgres-XL</>.  This may be supported in the
-      future releases.
-     </para>
-<!## end>
-    </listitem>
-    </varlistentry>
-   </variablelist>
- </sect2>
-
- <sect2 id="plperl-utility-functions">
-  <title>Utility Functions in PL/Perl</title>
-
-   <variablelist>
-    <varlistentry>
-     <indexterm>
-      <primary>elog</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>elog(<replaceable>level</replaceable>, <replaceable>msg</replaceable>)</function></literal></term>
-     <listitem>
-&pgnotice;
-      <para>
-       Emit a log or error message. Possible levels are
-       <literal>DEBUG</>, <literal>LOG</>, <literal>INFO</>,
-       <literal>NOTICE</>, <literal>WARNING</>, and <literal>ERROR</>.
-       <literal>ERROR</>
-        raises an error condition; if this is not trapped by the surrounding
-        Perl code, the error propagates out to the calling query, causing
-        the current transaction or subtransaction to be aborted.  This
-        is effectively the same as the Perl <literal>die</> command.
-        The other levels only generate messages of different
-        priority levels.
-        Whether messages of a particular priority are reported to the client,
-        written to the server log, or both is controlled by the
-        <xref linkend="guc-log-min-messages"> and
-        <xref linkend="guc-client-min-messages"> configuration
-        variables. See <xref linkend="runtime-config"> for more
-        information.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>quote_literal</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>quote_literal(<replaceable>string</replaceable>)</function></literal></term>
-     <listitem>
-      <para>
-        Return the given string suitably quoted to be used as a string literal in an SQL
-        statement string. Embedded single-quotes and backslashes are properly doubled.
-        Note that <function>quote_literal</> returns undef on undef input; if the argument
-        might be undef, <function>quote_nullable</> is often more suitable.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>quote_nullable</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>quote_nullable(<replaceable>string</replaceable>)</function></literal></term>
-     <listitem>
-      <para>
-        Return the given string suitably quoted to be used as a string literal in an SQL
-        statement string; or, if the argument is undef, return the unquoted string "NULL".
-        Embedded single-quotes and backslashes are properly doubled.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>quote_ident</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>quote_ident(<replaceable>string</replaceable>)</function></literal></term>
-     <listitem>
-      <para>
-        Return the given string suitably quoted to be used as an identifier in
-        an SQL statement string. Quotes are added only if necessary (i.e., if
-        the string contains non-identifier characters or would be case-folded).
-        Embedded quotes are properly doubled.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>decode_bytea</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>decode_bytea(<replaceable>string</replaceable>)</function></literal></term>
-     <listitem>
-      <para>
-        Return the unescaped binary data represented by the contents of the given string,
-        which should be <type>bytea</type> encoded.
-        </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>encode_bytea</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>encode_bytea(<replaceable>string</replaceable>)</function></literal></term>
-     <listitem>
-      <para>
-        Return the <type>bytea</type> encoded form of the binary data contents of the given string.
-        </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>encode_array_literal</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>encode_array_literal(<replaceable>array</replaceable>)</function></literal></term>
-     <term><literal><function>encode_array_literal(<replaceable>array</replaceable>, <replaceable>delimiter</replaceable>)</function></literal></term>
-     <listitem>
-      <para>
-        Returns the contents of the referenced array as a string in array literal format
-        (see <xref linkend="arrays-input">).
-        Returns the argument value unaltered if it's not a reference to an array.
-        The delimiter used between elements of the array literal defaults to "<literal>, </literal>"
-        if a delimiter is not specified or is undef.
-        </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>encode_typed_literal</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>encode_typed_literal(<replaceable>value</replaceable>, <replaceable>typename</replaceable>)</function></literal></term>
-      <listitem>
-       <para>
-         Converts a Perl variable to the value of the data type passed as a
-         second argument and returns a string representation of this value.
-         Correctly handles nested arrays and values of composite types.
-       </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>encode_array_constructor</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>encode_array_constructor(<replaceable>array</replaceable>)</function></literal></term>
-     <listitem>
-      <para>
-        Returns the contents of the referenced array as a string in array constructor format
-        (see <xref linkend="sql-syntax-array-constructors">).
-        Individual values are quoted using <function>quote_nullable</function>.
-        Returns the argument value, quoted using <function>quote_nullable</function>,
-        if it's not a reference to an array.
-        </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>looks_like_number</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>looks_like_number(<replaceable>string</replaceable>)</function></literal></term>
-     <listitem>
-      <para>
-        Returns a true value if the content of the given string looks like a
-        number, according to Perl, returns false otherwise.
-        Returns undef if the argument is undef.  Leading and trailing space is
-        ignored. <literal>Inf</> and <literal>Infinity</> are regarded as numbers.
-        </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>is_array_ref</primary>
-      <secondary>in PL/Perl</secondary>
-     </indexterm>
-
-     <term><literal><function>is_array_ref(<replaceable>argument</replaceable>)</function></literal></term>
-     <listitem>
-      <para>
-        Returns a true value if the given argument may be treated as an
-        array reference, that is, if ref of the argument is <literal>ARRAY</> or
-        <literal>PostgreSQL::InServer::ARRAY</>.  Returns false otherwise.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </sect2>
- </sect1>
-
- <sect1 id="plperl-global">
-  <title>Global Values in PL/Perl</title>
-
-&pgnotice;
-  <para>
-    You can use the global hash <varname>%_SHARED</varname> to store
-    data, including code references, between function calls for the
-    lifetime of the current session.
-  </para>
-
-  <para>
-    Here is a simple example for shared data:
-<programlisting>
-CREATE OR REPLACE FUNCTION set_var(name text, val text) RETURNS text AS $$
-    if ($_SHARED{$_[0]} = $_[1]) {
-        return 'ok';
-    } else {
-        return "cannot set shared variable $_[0] to $_[1]";
-    }
-$$ LANGUAGE plperl;
-
-CREATE OR REPLACE FUNCTION get_var(name text) RETURNS text AS $$
-    return $_SHARED{$_[0]};
-$$ LANGUAGE plperl;
-
-SELECT set_var('sample', 'Hello, PL/Perl!  How''s tricks?');
-SELECT get_var('sample');
-</programlisting>
-  </para>
-
-  <para>
-   Here is a slightly more complicated example using a code reference:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION myfuncs() RETURNS void AS $$
-    $_SHARED{myquote} = sub {
-        my $arg = shift;
-        $arg =~ s/(['\\])/\\$1/g;
-        return "'$arg'";
-    };
-$$ LANGUAGE plperl;
-
-SELECT myfuncs(); /* initializes the function */
-
-/* Set up a function that uses the quote function */
-
-CREATE OR REPLACE FUNCTION use_quote(TEXT) RETURNS text AS $$
-    my $text_to_quote = shift;
-    my $qfunc = $_SHARED{myquote};
-    return &amp;$qfunc($text_to_quote);
-$$ LANGUAGE plperl;
-</programlisting>
-
-   (You could have replaced the above with the one-liner
-   <literal>return $_SHARED{myquote}-&gt;($_[0]);</literal>
-   at the expense of readability.)
-  </para>
-
-  <para>
-   For security reasons, PL/Perl executes functions called by any one SQL role
-   in a separate Perl interpreter for that role.  This prevents accidental or
-   malicious interference by one user with the behavior of another user's
-   PL/Perl functions.  Each such interpreter has its own value of the
-   <varname>%_SHARED</varname> variable and other global state.  Thus, two
-   PL/Perl functions will share the same value of <varname>%_SHARED</varname>
-   if and only if they are executed by the same SQL role.  In an application
-   wherein a single session executes code under multiple SQL roles (via
-   <literal>SECURITY DEFINER</> functions, use of <command>SET ROLE</>, etc)
-   you may need to take explicit steps to ensure that PL/Perl functions can
-   share data via <varname>%_SHARED</varname>.  To do that, make sure that
-   functions that should communicate are owned by the same user, and mark
-   them <literal>SECURITY DEFINER</>.  You must of course take care that
-   such functions can't be used to do anything unintended.
-  </para>
- </sect1>
-
- <sect1 id="plperl-trusted">
-  <title>Trusted and Untrusted PL/Perl</title>
-
-  <indexterm zone="plperl-trusted">
-   <primary>trusted</primary>
-   <secondary>PL/Perl</secondary>
-  </indexterm>
-
-&pgnotice;
-  <para>
-   Normally, PL/Perl is installed as a <quote>trusted</> programming
-   language named <literal>plperl</>.  In this setup, certain Perl
-   operations are disabled to preserve security.  In general, the
-   operations that are restricted are those that interact with the
-   environment. This includes file handle operations,
-   <literal>require</literal>, and <literal>use</literal> (for
-   external modules).  There is no way to access internals of the
-   database server process or to gain OS-level access with the
-   permissions of the server process,
-   as a C function can do.  Thus, any unprivileged database user can
-   be permitted to use this language.
-  </para>
-
-  <para>
-   Here is an example of a function that will not work because file
-   system operations are not allowed for security reasons:
-<programlisting>
-CREATE FUNCTION badfunc() RETURNS integer AS $$
-    my $tmpfile = "/tmp/badfile";
-    open my $fh, '&gt;', $tmpfile
-        or elog(ERROR, qq{could not open the file "$tmpfile": $!});
-    print $fh "Testing writing to a file\n";
-    close $fh or elog(ERROR, qq{could not close the file "$tmpfile": $!});
-    return 1;
-$$ LANGUAGE plperl;
-</programlisting>
-    The creation of this function will fail as its use of a forbidden
-    operation will be caught by the validator.
-  </para>
-
-  <para>
-   Sometimes it is desirable to write Perl functions that are not
-   restricted.  For example, one might want a Perl function that sends
-   mail.  To handle these cases, PL/Perl can also be installed as an
-   <quote>untrusted</> language (usually called
-   <application>PL/PerlU</application><indexterm><primary>PL/PerlU</></indexterm>).
-   In this case the full Perl language is available.  When installing the
-   language, the language name <literal>plperlu</literal> will select
-   the untrusted PL/Perl variant.
-  </para>
-
-  <para>
-   The writer of a <application>PL/PerlU</> function must take care that the function
-   cannot be used to do anything unwanted, since it will be able to do
-   anything that could be done by a user logged in as the database
-   administrator.  Note that the database system allows only database
-   superusers to create functions in untrusted languages.
-  </para>
-
-  <para>
-   If the above function was created by a superuser using the language
-   <literal>plperlu</>, execution would succeed.
-  </para>
-
-  <para>
-   In the same way, anonymous code blocks written in Perl can use
-   restricted operations if the language is specified as
-   <literal>plperlu</> rather than <literal>plperl</>, but the caller
-   must be a superuser.
-  </para>
-
-  <note>
-   <para>
-    While <application>PL/Perl</> functions run in a separate Perl
-    interpreter for each SQL role, all <application>PL/PerlU</> functions
-    executed in a given session run in a single Perl interpreter (which is
-    not any of the ones used for <application>PL/Perl</> functions).
-    This allows <application>PL/PerlU</> functions to share data freely,
-    but no communication can occur between <application>PL/Perl</> and
-    <application>PL/PerlU</> functions.
-   </para>
-  </note>
-
-  <note>
-   <para>
-    Perl cannot support multiple interpreters within one process unless
-    it was built with the appropriate flags, namely either
-    <literal>usemultiplicity</> or <literal>useithreads</>.
-    (<literal>usemultiplicity</> is preferred unless you actually need
-    to use threads.  For more details, see the
-    <citerefentry><refentrytitle>perlembed</></citerefentry> man page.)
-    If <application>PL/Perl</> is used with a copy of Perl that was not built
-    this way, then it is only possible to have one Perl interpreter per
-    session, and so any one session can only execute either
-    <application>PL/PerlU</> functions, or <application>PL/Perl</> functions
-    that are all called by the same SQL role.
-   </para>
-  </note>
-
- </sect1>
-
- <sect1 id="plperl-triggers">
-  <title>PL/Perl Triggers</title>
-
-&pgnotice;
-  <para>
-   PL/Perl can be used to write trigger functions.  In a trigger function,
-   the hash reference <varname>$_TD</varname> contains information about the
-   current trigger event. <varname>$_TD</> is a global variable,
-   which gets a separate local value for each invocation of the trigger.
-   The fields of the <varname>$_TD</varname> hash reference are:
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>$_TD-&gt;{new}{foo}</literal></term>
-     <listitem>
-      <para>
-       <literal>NEW</literal> value of column <literal>foo</literal>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>$_TD-&gt;{old}{foo}</literal></term>
-     <listitem>
-      <para>
-       <literal>OLD</literal> value of column <literal>foo</literal>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>$_TD-&gt;{name}</literal></term>
-     <listitem>
-      <para>
-       Name of the trigger being called
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>$_TD-&gt;{event}</literal></term>
-     <listitem>
-      <para>
-       Trigger event: <literal>INSERT</>, <literal>UPDATE</>,
-       <literal>DELETE</>, <literal>TRUNCATE</>, or <literal>UNKNOWN</>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>$_TD-&gt;{when}</literal></term>
-     <listitem>
-      <para>
-       When the trigger was called: <literal>BEFORE</literal>,
-       <literal>AFTER</literal>, <literal>INSTEAD OF</literal>, or
-       <literal>UNKNOWN</literal>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>$_TD-&gt;{level}</literal></term>
-     <listitem>
-      <para>
-       The trigger level: <literal>ROW</literal>, <literal>STATEMENT</literal>, or <literal>UNKNOWN</literal>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>$_TD-&gt;{relid}</literal></term>
-     <listitem>
-      <para>
-       OID of the table on which the trigger fired
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>$_TD-&gt;{table_name}</literal></term>
-     <listitem>
-      <para>
-       Name of the table on which the trigger fired
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>$_TD-&gt;{relname}</literal></term>
-     <listitem>
-      <para>
-       Name of the table on which the trigger fired. This has been deprecated,
-       and could be removed in a future release.
-       Please use $_TD-&gt;{table_name} instead.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>$_TD-&gt;{table_schema}</literal></term>
-     <listitem>
-      <para>
-       Name of the schema in which the table on which the trigger fired, is
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>$_TD-&gt;{argc}</literal></term>
-     <listitem>
-      <para>
-       Number of arguments of the trigger function
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>@{$_TD-&gt;{args}}</literal></term>
-     <listitem>
-      <para>
-       Arguments of the trigger function.  Does not exist if <literal>$_TD-&gt;{argc}</literal> is 0.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-
-  <para>
-   Row-level triggers can return one of the following:
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>return;</literal></term>
-     <listitem>
-      <para>
-       Execute the operation
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>"SKIP"</literal></term>
-     <listitem>
-      <para>
-       Don't execute the operation
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>"MODIFY"</literal></term>
-     <listitem>
-      <para>
-       Indicates that the <literal>NEW</literal> row was modified by
-       the trigger function
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   Here is an example of a trigger function, illustrating some of the
-   above:
-<programlisting>
-CREATE TABLE test (
-    i int,
-    v varchar
-);
-
-CREATE OR REPLACE FUNCTION valid_id() RETURNS trigger AS $$
-    if (($_TD-&gt;{new}{i} &gt;= 100) || ($_TD-&gt;{new}{i} &lt;= 0)) {
-        return "SKIP";    # skip INSERT/UPDATE command
-    } elsif ($_TD-&gt;{new}{v} ne "immortal") {
-        $_TD-&gt;{new}{v} .= "(modified by trigger)";
-        return "MODIFY";  # modify row and execute INSERT/UPDATE command
-    } else {
-        return;           # execute INSERT/UPDATE command
-    }
-$$ LANGUAGE plperl;
-
-CREATE TRIGGER test_valid_id_trig
-    BEFORE INSERT OR UPDATE ON test
-    FOR EACH ROW EXECUTE PROCEDURE valid_id();
-</programlisting>
-  </para>
- </sect1>
-
- <sect1 id="plperl-under-the-hood">
-  <title>PL/Perl Under the Hood</title>
-
- <sect2 id="plperl-config">
-  <title>Configuration</title>
-
-&pgnotice;
-  <para>
-  This section lists configuration parameters that affect <application>PL/Perl</>.
-  To set any of these parameters before <application>PL/Perl</> has been loaded,
-  it is necessary to have added <quote><literal>plperl</></> to the
-  <xref linkend="guc-custom-variable-classes"> list in
-  <filename>postgresql.conf</filename>.
-  </para>
-
-  <variablelist>
-
-     <varlistentry id="guc-plperl-on-init" xreflabel="plperl.on_init">
-      <term><varname>plperl.on_init</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>plperl.on_init</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies Perl code to be executed when a Perl interpreter is first
-        initialized, before it is specialized for use by <literal>plperl</> or
-        <literal>plperlu</>.
-        The SPI functions are not available when this code is executed.
-        If the code fails with an error it will abort the initialization of
-        the interpreter and propagate out to the calling query, causing the
-        current transaction or subtransaction to be aborted.
-       </para>
-       <para>
-       The Perl code is limited to a single string. Longer code can be placed
-       into a module and loaded by the <literal>on_init</> string.
-       Examples:
-<programlisting>
-plperl.on_init = 'require "plperlinit.pl"'
-plperl.on_init = 'use lib "/my/app"; use MyApp::PgInit;'
-</programlisting>
-       </para>
-       <para>
-       Any modules loaded by <literal>plperl.on_init</>, either directly or
-       indirectly, will be available for use by <literal>plperl</>.  This may
-       create a security risk. To see what modules have been loaded you can use:
-<programlisting>
-DO 'elog(WARNING, join ", ", sort keys %INC)' language plperl;
-</programlisting>
-       </para>
-       <para>
-        Initialization will happen in the postmaster if the plperl library is
-        included in <xref linkend="guc-shared-preload-libraries">, in which
-        case extra consideration should be given to the risk of destabilizing
-        the postmaster.  The principal reason for making use of this feature
-        is that Perl modules loaded by <literal>plperl.on_init</> need be
-        loaded only at postmaster start, and will be instantly available
-        without loading overhead in individual database sessions.  However,
-        keep in mind that the overhead is avoided only for the first Perl
-        interpreter used by a database session &mdash; either PL/PerlU, or
-        PL/Perl for the first SQL role that calls a PL/Perl function.  Any
-        additional Perl interpreters created in a database session will have
-        to execute <literal>plperl.on_init</> afresh.  Also, on Windows there
-        will be no savings whatsoever from preloading, since the Perl
-        interpreter created in the postmaster process does not propagate to
-        child processes.
-       </para>
-       <para>
-       This parameter can only be set in the <filename>postgresql.conf</filename> file or on the server command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-plperl-on-plperl-init" xreflabel="plperl.on_plperl_init">
-      <term><varname>plperl.on_plperl_init</varname> (<type>string</type>)</term>
-      <term><varname>plperl.on_plperlu_init</varname> (<type>string</type>)</term>
-      <indexterm>
-       <primary><varname>plperl.on_plperl_init</> configuration parameter</primary>
-      </indexterm>
-      <indexterm>
-       <primary><varname>plperl.on_plperlu_init</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        These parameters specify Perl code to be executed when a Perl
-        interpreter is specialized for <literal>plperl</> or
-        <literal>plperlu</> respectively.  This will happen when a PL/Perl or
-        PL/PerlU function is first executed in a database session, or when
-        an additional interpreter has to be created because the other language
-        is called or a PL/Perl function is called by a new SQL role.  This
-        follows any initialization done by <literal>plperl.on_init</>.
-        The SPI functions are not available when this code is executed.
-        The Perl code in <literal>plperl.on_plperl_init</> is executed after
-        <quote>locking down</> the interpreter, and thus it can only perform
-        trusted operations.
-       </para>
-       <para>
-        If the code fails with an error it will abort the initialization and
-        propagate out to the calling query, causing the current transaction or
-        subtransaction to be aborted.  Any actions already done within Perl
-        won't be undone; however, that interpreter won't be used again.
-        If the language is used again the initialization will be attempted
-        again within a fresh Perl interpreter.
-       </para>
-       <para>
-        Only superusers can change these settings.  Although these settings
-        can be changed within a session, such changes will not affect Perl
-        interpreters that have already been used to execute functions.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="guc-plperl-use-strict" xreflabel="plperl.use_strict">
-      <term><varname>plperl.use_strict</varname> (<type>boolean</type>)</term>
-      <indexterm>
-       <primary><varname>plperl.use_strict</> configuration parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        When set true subsequent compilations of PL/Perl functions will have
-        the <literal>strict</> pragma enabled.  This parameter does not affect
-        functions already compiled in the current session.
-       </para>
-      </listitem>
-     </varlistentry>
-
-  </variablelist>
-</sect2>
-
- <sect2 id="plperl-missing">
-  <title>Limitations and Missing Features</title>
-
-&pgnotice;
-  <para>
-   The following features are currently missing from PL/Perl, but they
-   would make welcome contributions.
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      PL/Perl functions cannot call each other directly.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      SPI is not yet fully implemented.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      If you are fetching very large data sets using
-      <literal>spi_exec_query</literal>, you should be aware that
-      these will all go into memory.  You can avoid this by using
-      <literal>spi_query</literal>/<literal>spi_fetchrow</literal> as
-      illustrated earlier.
-     </para>
-     <para>
-        A similar problem occurs if a set-returning function passes a
-        large set of rows back to PostgreSQL via <literal>return</literal>. You
-        can avoid this problem too by instead using
-        <literal>return_next</literal> for each row returned, as shown
-        previously.
-     </para>
-    </listitem>
-
-     <listitem>
-      <para>
-        When a session ends normally, not due to a fatal error, any
-        <literal>END</> blocks that have been defined are executed.
-        Currently no other actions are performed. Specifically,
-        file handles are not automatically flushed and objects are
-        not automatically destroyed.
-      </para>
-     </listitem>
-   </itemizedlist>
-  </para>
- </sect2>
-
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/plpgsql.sgmlin b/doc-xc/src/sgml/plpgsql.sgmlin
deleted file mode 100644
index 8b489b9fba..0000000000
--- a/doc-xc/src/sgml/plpgsql.sgmlin
+++ /dev/null
@@ -1,5358 +0,0 @@
-<!-- doc/src/sgml/plpgsql.sgml -->
-
-<chapter id="plpgsql">
-  <title><application>PL/pgSQL</application> - <acronym>SQL</acronym> Procedural Language</title>
-
- <indexterm zone="plpgsql">
-  <primary>PL/pgSQL</primary>
- </indexterm>
-
- <sect1 id="plpgsql-overview">
-  <title>Overview</title>
-
-&common;
-
- <para>
-  <application>PL/pgSQL</application> is a loadable procedural
-<!## PG>
-  language for the <productname>PostgreSQL</productname> database
-  system.  The design goals of <application>PL/pgSQL</> were to create
-  a loadable procedural language that
-<!## end>
-<!## XC>
-  language for the <productname>Postgres-XC</productname> database
-  system inherited from <productname>PostgreSQL</>.  The design goals of <application>PL/pgSQL</> were to create
-  a loadable procedural language that
-<!## end>
-<!## XL>
-  language for the <productname>Postgres-XL</productname> database
-  system inherited from <productname>PostgreSQL</>.  The design goals of <application>PL/pgSQL</> were to create
-  a loadable procedural language that
-<!## end>
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       can be used to create functions and trigger procedures,
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       adds control structures to the <acronym>SQL</acronym> language,
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       can perform complex computations,
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       inherits all user-defined types, functions, and operators,
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       can be defined to be trusted by the server,
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       is easy to use.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    Functions created with <application>PL/pgSQL</application> can be
-    used anywhere that built-in functions could be used.
-    For example, it is possible to
-    create complex conditional computation functions and later use
-    them to define operators or use them in index expressions.
-   </para>
-
-   <para>
-    In <productname>PostgreSQL</> 9.0 and later,
-    <application>PL/pgSQL</application> is installed by default.
-    However it is still a loadable module, so especially security-conscious
-    administrators could choose to remove it.
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    At present, in <productname>Postgres-XC</>, only one SQL statment
-    can be handled in a function.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    At present, in <productname>Postgres-XL</>, only one SQL statment
-    can be handled in a function.
-   </para>
-<!## end>
-
-  <sect2 id="plpgsql-advantages">
-   <title>Advantages of Using <application>PL/pgSQL</application></title>
-
-&common;
-    <para>
-<!## PG>
-     <acronym>SQL</acronym> is the language <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-     <acronym>SQL</acronym> is the language <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-     <acronym>SQL</acronym> is the language <productname>Postgres-XL</>
-<!## end>
-     and most other relational databases use as query language. It's
-     portable and easy to learn. But every <acronym>SQL</acronym>
-     statement must be executed individually by the database server.
-    </para>
-
-    <para>
-     That means that your client application must send each query to
-     the database server, wait for it to be processed, receive and
-     process the results, do some computation, then send further
-     queries to the server.  All this incurs interprocess
-     communication and will also incur network overhead if your client
-     is on a different machine than the database server.
-    </para>
-
-    <para>
-     With <application>PL/pgSQL</application> you can group a block of
-     computation and a series of queries <emphasis>inside</emphasis>
-     the database server, thus having the power of a procedural
-     language and the ease of use of SQL, but with considerable
-     savings of client/server communication overhead.
-    </para>
-    <itemizedlist>
-
-     <listitem><para> Extra round trips between
-     client and server are eliminated </para></listitem>
-
-     <listitem><para> Intermediate results that the client does not
-     need do not have to be marshaled or transferred between server
-     and client </para></listitem>
-
-     <listitem><para> Multiple rounds of query
-     parsing can be avoided </para></listitem>
-
-    </itemizedlist>
-    <para> This can result in a considerable performance increase as
-    compared to an application that does not use stored functions.
-    </para>
-
-    <para>
-     Also, with <application>PL/pgSQL</application> you can use all
-     the data types, operators and functions of SQL.
-    </para>
-  </sect2>
-
-  <sect2 id="plpgsql-args-results">
-   <title>Supported Argument and Result Data Types</title>
-
-&common;
-    <para>
-     Functions written in <application>PL/pgSQL</application> can accept
-     as arguments any scalar or array data type supported by the server,
-     and they can return a result of any of these types.  They can also
-     accept or return any composite type (row type) specified by name.
-     It is also possible to declare a <application>PL/pgSQL</application>
-     function as returning <type>record</>, which means that the result
-     is a row type whose columns are determined by specification in the
-     calling query, as discussed in <xref linkend="queries-tablefunctions">.
-    </para>
-
-    <para>
-     <application>PL/pgSQL</> functions can be declared to accept a variable
-     number of arguments by using the <literal>VARIADIC</> marker.  This
-     works exactly the same way as for SQL functions, as discussed in
-     <xref linkend="xfunc-sql-variadic-functions">.
-    </para>
-
-    <para>
-     <application>PL/pgSQL</> functions can also be declared to accept
-     and return the polymorphic types
-     <type>anyelement</type>, <type>anyarray</type>, <type>anynonarray</type>,
-     and <type>anyenum</>.  The actual
-     data types handled by a polymorphic function can vary from call to
-     call, as discussed in <xref linkend="extend-types-polymorphic">.
-     An example is shown in <xref linkend="plpgsql-declaration-parameters">.
-    </para>
-
-    <para>
-     <application>PL/pgSQL</> functions can also be declared to return
-     a <quote>set</> (or table) of any data type that can be returned as
-     a single instance.  Such a function generates its output by executing
-     <command>RETURN NEXT</> for each desired element of the result
-     set, or by using <command>RETURN QUERY</> to output the result of
-     evaluating a query.
-    </para>
-
-    <para>
-     Finally, a <application>PL/pgSQL</> function can be declared to return
-     <type>void</> if it has no useful return value.
-    </para>
-
-    <para>
-     <application>PL/pgSQL</> functions can also be declared with output
-     parameters in place of an explicit specification of the return type.
-     This does not add any fundamental capability to the language, but
-     it is often convenient, especially for returning multiple values.
-     The <literal>RETURNS TABLE</> notation can also be used in place
-     of <literal>RETURNS SETOF</>.
-    </para>
-
-    <para>
-     Specific examples appear in
-     <xref linkend="plpgsql-declaration-parameters"> and
-     <xref linkend="plpgsql-statements-returning">.
-    </para>
-  </sect2>
- </sect1>
-
- <sect1 id="plpgsql-structure">
-  <title>Structure of <application>PL/pgSQL</application></title>
-
-&common;
-  <para>
-   <application>PL/pgSQL</application> is a block-structured language.
-   The complete text of a function definition must be a
-   <firstterm>block</>. A block is defined as:
-
-<synopsis>
-<optional> &lt;&lt;<replaceable>label</replaceable>&gt;&gt; </optional>
-<optional> DECLARE
-    <replaceable>declarations</replaceable> </optional>
-BEGIN
-    <replaceable>statements</replaceable>
-END <optional> <replaceable>label</replaceable> </optional>;
-</synopsis>
-    </para>
-
-    <para>
-     Each declaration and each statement within a block is terminated
-     by a semicolon.  A block that appears within another block must
-     have a semicolon after <literal>END</literal>, as shown above;
-     however the final <literal>END</literal> that
-     concludes a function body does not require a semicolon.
-    </para>
-
-    <tip>
-     <para>
-      A common mistake is to write a semicolon immediately after
-      <literal>BEGIN</>.  This is incorrect and will result in a syntax error.
-     </para>
-    </tip>
-
-    <para>
-     A <replaceable>label</replaceable> is only needed if you want to
-     identify the block for use
-     in an <literal>EXIT</> statement, or to qualify the names of the
-     variables declared in the block.  If a label is given after
-     <literal>END</>, it must match the label at the block's beginning.
-    </para>
-
-    <para>
-     All key words are case-insensitive.
-     Identifiers are implicitly converted to lower case
-     unless double-quoted, just as they are in ordinary SQL commands.
-    </para>
-
-    <para>
-     Comments work the same way in <application>PL/pgSQL</> code as in
-     ordinary SQL.  A double dash (<literal>--</literal>) starts a comment
-     that extends to the end of the line. A <literal>/*</literal> starts a
-     block comment that extends to the matching occurrence of
-     <literal>*/</literal>.  Block comments nest.
-    </para>
-
-    <para>
-     Any statement in the statement section of a block
-     can be a <firstterm>subblock</>.  Subblocks can be used for
-     logical grouping or to localize variables to a small group
-     of statements.  Variables declared in a subblock mask any
-     similarly-named variables of outer blocks for the duration
-     of the subblock; but you can access the outer variables anyway
-     if you qualify their names with their block's label. For example:
-<programlisting>
-CREATE FUNCTION somefunc() RETURNS integer AS $$
-&lt;&lt; outerblock &gt;&gt;
-DECLARE
-    quantity integer := 30;
-BEGIN
-    RAISE NOTICE 'Quantity here is %', quantity;  -- Prints 30
-    quantity := 50;
-    --
-    -- Create a subblock
-    --
-    DECLARE
-        quantity integer := 80;
-    BEGIN
-        RAISE NOTICE 'Quantity here is %', quantity;  -- Prints 80
-        RAISE NOTICE 'Outer quantity here is %', outerblock.quantity;  -- Prints 50
-    END;
-
-    RAISE NOTICE 'Quantity here is %', quantity;  -- Prints 50
-
-    RETURN quantity;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-    </para>
-
-    <note>
-     <para>
-      There is actually a hidden <quote>outer block</> surrounding the body
-      of any <application>PL/pgSQL</> function.  This block provides the
-      declarations of the function's parameters (if any), as well as some
-      special variables such as <literal>FOUND</literal> (see
-      <xref linkend="plpgsql-statements-diagnostics">).  The outer block is
-      labeled with the function's name, meaning that parameters and special
-      variables can be qualified with the function's name.
-     </para>
-    </note>
-
-    <para>
-     It is important not to confuse the use of
-     <command>BEGIN</>/<command>END</> for grouping statements in
-     <application>PL/pgSQL</> with the similarly-named SQL commands
-     for transaction
-     control.  <application>PL/pgSQL</>'s <command>BEGIN</>/<command>END</>
-     are only for grouping; they do not start or end a transaction.
-     Functions and trigger procedures are always executed within a transaction
-     established by an outer query &mdash; they cannot start or commit that
-     transaction, since there would be no context for them to execute in.
-     However, a block containing an <literal>EXCEPTION</> clause effectively
-     forms a subtransaction that can be rolled back without affecting the
-     outer transaction.  For more about that see <xref
-     linkend="plpgsql-error-trapping">.
-    </para>
-  </sect1>
-
-  <sect1 id="plpgsql-declarations">
-    <title>Declarations</title>
-
-&common;
-    <para>
-     All variables used in a block must be declared in the
-     declarations section of the block.
-     (The only exceptions are that the loop variable of a <literal>FOR</> loop
-     iterating over a range of integer values is automatically declared as an
-     integer variable, and likewise the loop variable of a <literal>FOR</> loop
-     iterating over a cursor's result is automatically declared as a
-     record variable.)
-    </para>
-
-    <para>
-     <application>PL/pgSQL</> variables can have any SQL data type, such as
-     <type>integer</type>, <type>varchar</type>, and
-     <type>char</type>.
-    </para>
-
-    <para>
-     Here are some examples of variable declarations:
-<programlisting>
-user_id integer;
-quantity numeric(5);
-url varchar;
-myrow tablename%ROWTYPE;
-myfield tablename.columnname%TYPE;
-arow RECORD;
-</programlisting>
-    </para>
-
-    <para>
-     The general syntax of a variable declaration is:
-<synopsis>
-<replaceable>name</replaceable> <optional> CONSTANT </optional> <replaceable>type</replaceable> <optional> COLLATE <replaceable>collation_name</replaceable> </optional> <optional> NOT NULL </optional> <optional> { DEFAULT | := } <replaceable>expression</replaceable> </optional>;
-</synopsis>
-      The <literal>DEFAULT</> clause, if given, specifies the initial value assigned
-      to the variable when the block is entered.  If the <literal>DEFAULT</> clause
-      is not given then the variable is initialized to the
-      <acronym>SQL</acronym> null value.
-      The <literal>CONSTANT</> option prevents the variable from being
-      assigned to after initialization, so that its value will remain constant
-      for the duration of the block.
-      The <literal>COLLATE</> option specifies a collation to use for the
-      variable (see <xref linkend="plpgsql-declaration-collation">).
-      If <literal>NOT NULL</>
-      is specified, an assignment of a null value results in a run-time
-      error. All variables declared as <literal>NOT NULL</>
-      must have a nonnull default value specified.
-     </para>
-
-     <para>
-      A variable's default value is evaluated and assigned to the variable
-      each time the block is entered (not just once per function call).
-      So, for example, assigning <literal>now()</literal> to a variable of type
-      <type>timestamp</type> causes the variable to have the
-      time of the current function call, not the time when the function was
-      precompiled.
-     </para>
-
-     <para>
-      Examples:
-<programlisting>
-quantity integer DEFAULT 32;
-url varchar := 'http://mysite.com';
-user_id CONSTANT integer := 10;
-</programlisting>
-     </para>
-
-    <sect2 id="plpgsql-declaration-parameters">
-     <title>Declaring Function Parameters</title>
-
-&common;
-     <para>
-      Parameters passed to functions are named with the identifiers
-      <literal>$1</literal>, <literal>$2</literal>,
-      etc.  Optionally, aliases can be declared for
-      <literal>$<replaceable>n</replaceable></literal>
-      parameter names for increased readability.  Either the alias or the
-      numeric identifier can then be used to refer to the parameter value.
-     </para>
-
-     <para>
-      There are two ways to create an alias.  The preferred way is to give a
-      name to the parameter in the <command>CREATE FUNCTION</command> command,
-      for example:
-<programlisting>
-CREATE FUNCTION sales_tax(subtotal real) RETURNS real AS $$
-BEGIN
-    RETURN subtotal * 0.06;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-      The other way, which was the only way available before
-      <productname>PostgreSQL</productname> 8.0, is to explicitly
-      declare an alias, using the declaration syntax
-
-<synopsis>
-<replaceable>name</replaceable> ALIAS FOR $<replaceable>n</replaceable>;
-</synopsis>
-
-      The same example in this style looks like:
-<programlisting>
-CREATE FUNCTION sales_tax(real) RETURNS real AS $$
-DECLARE
-    subtotal ALIAS FOR $1;
-BEGIN
-    RETURN subtotal * 0.06;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-     </para>
-
-    <note>
-     <para>
-      These two examples are not perfectly equivalent.  In the first case,
-      <literal>subtotal</> could be referenced as
-      <literal>sales_tax.subtotal</>, but in the second case it could not.
-      (Had we attached a label to the inner block, <literal>subtotal</> could
-      be qualified with that label, instead.)
-     </para>
-    </note>
-
-     <para>
-      Some more examples:
-<programlisting>
-CREATE FUNCTION instr(varchar, integer) RETURNS integer AS $$
-DECLARE
-    v_string ALIAS FOR $1;
-    index ALIAS FOR $2;
-BEGIN
-    -- some computations using v_string and index here
-END;
-$$ LANGUAGE plpgsql;
-
-
-CREATE FUNCTION concat_selected_fields(in_t sometablename) RETURNS text AS $$
-BEGIN
-    RETURN in_t.f1 || in_t.f3 || in_t.f5 || in_t.f7;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-     </para>
-
-     <para>
-      When a <application>PL/pgSQL</application> function is declared
-      with output parameters, the output parameters are given
-      <literal>$<replaceable>n</replaceable></literal> names and optional
-      aliases in just the same way as the normal input parameters.  An
-      output parameter is effectively a variable that starts out NULL;
-      it should be assigned to during the execution of the function.
-      The final value of the parameter is what is returned.  For instance,
-      the sales-tax example could also be done this way:
-
-<programlisting>
-CREATE FUNCTION sales_tax(subtotal real, OUT tax real) AS $$
-BEGIN
-    tax := subtotal * 0.06;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-
-      Notice that we omitted <literal>RETURNS real</> &mdash; we could have
-      included it, but it would be redundant.
-     </para>
-
-     <para>
-      Output parameters are most useful when returning multiple values.
-      A trivial example is:
-
-<programlisting>
-CREATE FUNCTION sum_n_product(x int, y int, OUT sum int, OUT prod int) AS $$
-BEGIN
-    sum := x + y;
-    prod := x * y;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-
-      As discussed in <xref linkend="xfunc-output-parameters">, this
-      effectively creates an anonymous record type for the function's
-      results.  If a <literal>RETURNS</> clause is given, it must say
-      <literal>RETURNS record</>.
-     </para>
-
-     <para>
-      Another way to declare a <application>PL/pgSQL</application> function
-      is with <literal>RETURNS TABLE</>, for example:
-
-<programlisting>
-CREATE FUNCTION extended_sales(p_itemno int)
-RETURNS TABLE(quantity int, total numeric) AS $$
-BEGIN
-    RETURN QUERY SELECT quantity, quantity * price FROM sales
-                 WHERE itemno = p_itemno;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-
-      This is exactly equivalent to declaring one or more <literal>OUT</>
-      parameters and specifying <literal>RETURNS SETOF
-      <replaceable>sometype</></literal>.
-     </para>
-
-     <para>
-      When the return type of a <application>PL/pgSQL</application>
-      function is declared as a polymorphic type (<type>anyelement</type>,
-      <type>anyarray</type>, <type>anynonarray</type>, or <type>anyenum</>),
-      a special parameter <literal>$0</literal>
-      is created.  Its data type is the actual return type of the function,
-      as deduced from the actual input types (see <xref
-      linkend="extend-types-polymorphic">).
-      This allows the function to access its actual return type
-      as shown in <xref linkend="plpgsql-declaration-type">.
-      <literal>$0</literal> is initialized to null and can be modified by
-      the function, so it can be used to hold the return value if desired,
-      though that is not required.  <literal>$0</literal> can also be
-      given an alias.  For example, this function works on any data type
-      that has a <literal>+</> operator:
-
-<programlisting>
-CREATE FUNCTION add_three_values(v1 anyelement, v2 anyelement, v3 anyelement)
-RETURNS anyelement AS $$
-DECLARE
-    result ALIAS FOR $0;
-BEGIN
-    result := v1 + v2 + v3;
-    RETURN result;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-     </para>
-
-     <para>
-      The same effect can be had by declaring one or more output parameters as
-      polymorphic types.  In this case the
-      special <literal>$0</literal> parameter is not used; the output
-      parameters themselves serve the same purpose.  For example:
-
-<programlisting>
-CREATE FUNCTION add_three_values(v1 anyelement, v2 anyelement, v3 anyelement,
-                                 OUT sum anyelement)
-AS $$
-BEGIN
-    sum := v1 + v2 + v3;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-     </para>
-    </sect2>
-
-  <sect2 id="plpgsql-declaration-alias">
-   <title><literal>ALIAS</></title>
-
-<synopsis>
-<replaceable>newname</> ALIAS FOR <replaceable>oldname</>;
-</synopsis>
-
-&common;
-   <para>
-    The <literal>ALIAS</> syntax is more general than is suggested in the
-    previous section: you can declare an alias for any variable, not just
-    function parameters.  The main practical use for this is to assign
-    a different name for variables with predetermined names, such as
-    <varname>NEW</varname> or <varname>OLD</varname> within
-    a trigger procedure.
-   </para>
-
-   <para>
-    Examples:
-<programlisting>
-DECLARE
-  prior ALIAS FOR old;
-  updated ALIAS FOR new;
-</programlisting>
-   </para>
-
-   <para>
-    Since <literal>ALIAS</> creates two different ways to name the same
-    object, unrestricted use can be confusing.  It's best to use it only
-    for the purpose of overriding predetermined names.
-   </para>
-   </sect2>
-
-  <sect2 id="plpgsql-declaration-type">
-   <title>Copying Types</title>
-
-<synopsis>
-<replaceable>variable</replaceable>%TYPE
-</synopsis>
-
-&common;
-   <para>
-    <literal>%TYPE</literal> provides the data type of a variable or
-    table column. You can use this to declare variables that will hold
-    database values. For example, let's say you have a column named
-    <literal>user_id</literal> in your <literal>users</literal>
-    table. To declare a variable with the same data type as
-    <literal>users.user_id</> you write:
-<programlisting>
-user_id users.user_id%TYPE;
-</programlisting>
-   </para>
-
-   <para>
-    By using <literal>%TYPE</literal> you don't need to know the data
-    type of the structure you are referencing, and most importantly,
-    if the data type of the referenced item changes in the future (for
-    instance: you change the type of <literal>user_id</>
-    from <type>integer</type> to <type>real</type>), you might not need
-    to change your function definition.
-   </para>
-
-   <para>
-    <literal>%TYPE</literal> is particularly valuable in polymorphic
-    functions, since the data types needed for internal variables can
-    change from one call to the next.  Appropriate variables can be
-    created by applying <literal>%TYPE</literal> to the function's
-    arguments or result placeholders.
-   </para>
-
-  </sect2>
-
-    <sect2 id="plpgsql-declaration-rowtypes">
-     <title>Row Types</title>
-
-<synopsis>
-<replaceable>name</replaceable> <replaceable>table_name</replaceable><literal>%ROWTYPE</literal>;
-<replaceable>name</replaceable> <replaceable>composite_type_name</replaceable>;
-</synopsis>
-
-&common;
-   <para>
-    A variable of a composite type is called a <firstterm>row</>
-    variable (or <firstterm>row-type</> variable).  Such a variable
-    can hold a whole row of a <command>SELECT</> or <command>FOR</>
-    query result, so long as that query's column set matches the
-    declared type of the variable.
-    The individual fields of the row value
-    are accessed using the usual dot notation, for example
-    <literal>rowvar.field</literal>.
-   </para>
-
-   <para>
-    A row variable can be declared to have the same type as the rows of
-    an existing table or view, by using the
-    <replaceable>table_name</replaceable><literal>%ROWTYPE</literal>
-    notation; or it can be declared by giving a composite type's name.
-    (Since every table has an associated composite type of the same name,
-<!## PG>
-    it actually does not matter in <productname>PostgreSQL</> whether you
-<!## end>
-<!## XC>
-    it actually does not matter in <productname>Postgres-XC</> whether you
-<!## end>
-<!## XL>
-    it actually does not matter in <productname>Postgres-XL</> whether you
-<!## end>
-    write <literal>%ROWTYPE</literal> or not.  But the form with
-    <literal>%ROWTYPE</literal> is more portable.)
-   </para>
-
-   <para>
-    Parameters to a function can be
-    composite types (complete table rows). In that case, the
-    corresponding identifier <literal>$<replaceable>n</replaceable></> will be a row variable, and fields can
-    be selected from it, for example <literal>$1.user_id</literal>.
-   </para>
-
-   <para>
-    Only the user-defined columns of a table row are accessible in a
-    row-type variable, not the OID or other system columns (because the
-    row could be from a view).  The fields of the row type inherit the
-    table's field size or precision for data types such as
-    <type>char(<replaceable>n</>)</type>.
-   </para>
-
-   <para>
-    Here is an example of using composite types.  <structname>table1</>
-    and <structname>table2</> are existing tables having at least the
-    mentioned fields:
-
-<programlisting>
-CREATE FUNCTION merge_fields(t_row table1) RETURNS text AS $$
-DECLARE
-    t2_row table2%ROWTYPE;
-BEGIN
-    SELECT * INTO t2_row FROM table2 WHERE ... ;
-    RETURN t_row.f1 || t2_row.f3 || t_row.f5 || t2_row.f7;
-END;
-$$ LANGUAGE plpgsql;
-
-SELECT merge_fields(t.*) FROM table1 t WHERE ... ;
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="plpgsql-declaration-records">
-   <title>Record Types</title>
-
-<synopsis>
-<replaceable>name</replaceable> RECORD;
-</synopsis>
-
-&common;
-   <para>
-    Record variables are similar to row-type variables, but they have no
-    predefined structure.  They take on the actual row structure of the
-    row they are assigned during a <command>SELECT</> or <command>FOR</> command.  The substructure
-    of a record variable can change each time it is assigned to.
-    A consequence of this is that until a record variable is first assigned
-    to, it has no substructure, and any attempt to access a
-    field in it will draw a run-time error.
-   </para>
-
-   <para>
-    Note that <literal>RECORD</> is not a true data type, only a placeholder.
-    One should also realize that when a <application>PL/pgSQL</application>
-    function is declared to return type <type>record</>, this is not quite the
-    same concept as a record variable, even though such a function might
-    use a record variable to hold its result.  In both cases the actual row
-    structure is unknown when the function is written, but for a function
-    returning <type>record</> the actual structure is determined when the
-    calling query is parsed, whereas a record variable can change its row
-    structure on-the-fly.
-   </para>
-  </sect2>
-
-  <sect2 id="plpgsql-declaration-collation">
-   <title>Collation of <application>PL/pgSQL</application> Variables</title>
-
-   <indexterm>
-    <primary>collation</>
-    <secondary>in PL/pgSQL</>
-   </indexterm>
-
-   <para>
-    When a <application>PL/pgSQL</application> function has one or more
-    parameters of collatable data types, a collation is identified for each
-    function call depending on the collations assigned to the actual
-    arguments, as described in <xref linkend="collation">.  If a collation is
-    successfully identified (i.e., there are no conflicts of implicit
-    collations among the arguments) then all the collatable parameters are
-    treated as having that collation implicitly.  This will affect the
-    behavior of collation-sensitive operations within the function.
-    For example, consider
-
-<programlisting>
-CREATE FUNCTION less_than(a text, b text) RETURNS boolean AS $$
-BEGIN
-    RETURN a &lt; b;
-END;
-$$ LANGUAGE plpgsql;
-
-SELECT less_than(text_field_1, text_field_2) FROM table1;
-SELECT less_than(text_field_1, text_field_2 COLLATE "C") FROM table1;
-</programlisting>
-
-    The first use of <function>less_than</> will use the common collation
-    of <structfield>text_field_1</> and <structfield>text_field_2</> for
-    the comparison, while the second use will use <literal>C</> collation.
-   </para>
-
-   <para>
-    Furthermore, the identified collation is also assumed as the collation of
-    any local variables that are of collatable types.  Thus this function
-    would not work any differently if it were written as
-
-<programlisting>
-CREATE FUNCTION less_than(a text, b text) RETURNS boolean AS $$
-DECLARE
-    local_a text := a;
-    local_b text := b;
-BEGIN
-    RETURN local_a &lt; local_b;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-   </para>
-
-   <para>
-    If there are no parameters of collatable data types, or no common
-    collation can be identified for them, then parameters and local variables
-    use the default collation of their data type (which is usually the
-    database's default collation, but could be different for variables of
-    domain types).
-   </para>
-
-   <para>
-    A local variable of a collatable data type can have a different collation
-    associated with it by including the <literal>COLLATE</> option in its
-    declaration, for example
-
-<programlisting>
-DECLARE
-    local_a text COLLATE "en_US";
-</programlisting>
-
-    This option overrides the collation that would otherwise be
-    given to the variable according to the rules above.
-   </para>
-
-   <para>
-    Also, of course explicit <literal>COLLATE</> clauses can be written inside
-    a function if it is desired to force a particular collation to be used in
-    a particular operation.  For example,
-
-<programlisting>
-CREATE FUNCTION less_than_c(a text, b text) RETURNS boolean AS $$
-BEGIN
-    RETURN a &lt; b COLLATE "C";
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-
-    This overrides the collations associated with the table columns,
-    parameters, or local variables used in the expression, just as would
-    happen in a plain SQL command.
-   </para>
-  </sect2>
-  </sect1>
-
-  <sect1 id="plpgsql-expressions">
-  <title>Expressions</title>
-
-&common;
-    <para>
-     All expressions used in <application>PL/pgSQL</application>
-     statements are processed using the server's main
-     <acronym>SQL</acronym> executor.  For example, when you write
-     a <application>PL/pgSQL</application> statement like
-<synopsis>
-IF <replaceable>expression</replaceable> THEN ...
-</synopsis>
-     <application>PL/pgSQL</application> will evaluate the expression by
-     feeding a query like
-<synopsis>
-SELECT <replaceable>expression</replaceable>
-</synopsis>
-     to the main SQL engine.  While forming the <command>SELECT</> command,
-     any occurrences of <application>PL/pgSQL</application> variable names
-     are replaced by parameters, as discussed in detail in
-     <xref linkend="plpgsql-var-subst">.
-     This allows the query plan for the <command>SELECT</command> to
-     be prepared just once and then reused for subsequent
-     evaluations with different values of the variables.  Thus, what
-     really happens on first use of an expression is essentially a
-     <command>PREPARE</> command.  For example, if we have declared
-     two integer variables <literal>x</> and <literal>y</>, and we write
-<programlisting>
-IF x &lt; y THEN ...
-</programlisting>
-     what happens behind the scenes is equivalent to
-<programlisting>
-PREPARE <replaceable>statement_name</>(integer, integer) AS SELECT $1 &lt; $2;
-</programlisting>
-     and then this prepared statement is <command>EXECUTE</>d for each
-     execution of the <command>IF</> statement, with the current values
-     of the <application>PL/pgSQL</application> variables supplied as
-     parameter values.
-     The query plan prepared in this way is saved for the life of the database
-     connection, as described in
-     <xref linkend="plpgsql-plan-caching">.  Normally these details are
-     not important to a <application>PL/pgSQL</application> user, but
-     they are useful to know when trying to diagnose a problem.
-    </para>
-  </sect1>
-
-  <sect1 id="plpgsql-statements">
-  <title>Basic Statements</title>
-
-&common;
-   <para>
-    In this section and the following ones, we describe all the statement
-    types that are explicitly understood by
-    <application>PL/pgSQL</application>.
-    Anything not recognized as one of these statement types is presumed
-    to be an SQL command and is sent to the main database engine to execute,
-    as described in <xref linkend="plpgsql-statements-sql-noresult">
-    and <xref linkend="plpgsql-statements-sql-onerow">.
-   </para>
-
-   <sect2 id="plpgsql-statements-assignment">
-    <title>Assignment</title>
-
-&common;
-    <para>
-     An assignment of a value to a <application>PL/pgSQL</application>
-     variable is written as:
-<synopsis>
-<replaceable>variable</replaceable> := <replaceable>expression</replaceable>;
-</synopsis>
-     As explained previously, the expression in such a statement is evaluated
-     by means of an SQL <command>SELECT</> command sent to the main
-     database engine.  The expression must yield a single value (possibly
-     a row value, if the variable is a row or record variable).  The target
-     variable can be a simple variable (optionally qualified with a block
-     name), a field of a row or record variable, or an element of an array
-     that is a simple variable or field.
-    </para>
-
-    <para>
-     If the expression's result data type doesn't match the variable's
-     data type, or the variable has a specific size/precision
-     (like <type>char(20)</type>), the result value will be implicitly
-     converted by the <application>PL/pgSQL</application> interpreter using
-     the result type's output-function and
-     the variable type's input-function. Note that this could potentially
-     result in run-time errors generated by the input function, if the
-     string form of the result value is not acceptable to the input function.
-    </para>
-
-    <para>
-     Examples:
-<programlisting>
-tax := subtotal * 0.06;
-my_record.user_id := 20;
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2 id="plpgsql-statements-sql-noresult">
-    <title>Executing a Command With No Result</title>
-
-&common;
-    <para>
-     For any SQL command that does not return rows, for example
-     <command>INSERT</> without a <literal>RETURNING</> clause, you can
-     execute the command within a <application>PL/pgSQL</application> function
-     just by writing the command.
-    </para>
-
-    <para>
-     Any <application>PL/pgSQL</application> variable name appearing
-     in the command text is treated as a parameter, and then the
-     current value of the variable is provided as the parameter value
-     at run time.  This is exactly like the processing described earlier
-     for expressions; for details see <xref linkend="plpgsql-var-subst">.
-    </para>
-
-    <para>
-     When executing a SQL command in this way,
-     <application>PL/pgSQL</application> plans the command just once
-     and re-uses the plan on subsequent executions, for the life of
-     the database connection.  The implications of this are discussed
-     in detail in <xref linkend="plpgsql-plan-caching">.
-    </para>
-
-    <para>
-     Sometimes it is useful to evaluate an expression or <command>SELECT</>
-     query but discard the result, for example when calling a function
-     that has side-effects but no useful result value.  To do
-     this in <application>PL/pgSQL</application>, use the
-     <command>PERFORM</command> statement:
-
-<synopsis>
-PERFORM <replaceable>query</replaceable>;
-</synopsis>
-
-     This executes <replaceable>query</replaceable> and discards the
-     result.  Write the <replaceable>query</replaceable> the same
-     way you would write an SQL <command>SELECT</> command, but replace the
-     initial keyword <command>SELECT</> with <command>PERFORM</command>.
-     <application>PL/pgSQL</application> variables will be
-     substituted into the query just as for commands that return no result,
-     and the plan is cached in the same way.  Also, the special variable
-     <literal>FOUND</literal> is set to true if the query produced at
-     least one row, or false if it produced no rows (see
-     <xref linkend="plpgsql-statements-diagnostics">).
-    </para>
-
-    <note>
-     <para>
-      One might expect that writing <command>SELECT</command> directly
-      would accomplish this result, but at
-      present the only accepted way to do it is
-      <command>PERFORM</command>.  A SQL command that can return rows,
-      such as <command>SELECT</command>, will be rejected as an error
-      unless it has an <literal>INTO</> clause as discussed in the
-      next section.
-     </para>
-    </note>
-
-    <para>
-     An example:
-<programlisting>
-PERFORM create_mv('cs_session_page_requests_mv', my_query);
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2 id="plpgsql-statements-sql-onerow">
-    <title>Executing a Query with a Single-row Result</title>
-
-    <indexterm zone="plpgsql-statements-sql-onerow">
-     <primary>SELECT INTO</primary>
-     <secondary>in PL/pgSQL</secondary>
-    </indexterm>
-
-    <indexterm zone="plpgsql-statements-sql-onerow">
-     <primary>RETURNING INTO</primary>
-     <secondary>in PL/pgSQL</secondary>
-    </indexterm>
-
-&common;
-    <para>
-     The result of a SQL command yielding a single row (possibly of multiple
-     columns) can be assigned to a record variable, row-type variable, or list
-     of scalar variables.  This is done by writing the base SQL command and
-     adding an <literal>INTO</> clause.  For example,
-
-<synopsis>
-SELECT <replaceable>select_expressions</replaceable> INTO <optional>STRICT</optional> <replaceable>target</replaceable> FROM ...;
-INSERT ... RETURNING <replaceable>expressions</replaceable> INTO <optional>STRICT</optional> <replaceable>target</replaceable>;
-UPDATE ... RETURNING <replaceable>expressions</replaceable> INTO <optional>STRICT</optional> <replaceable>target</replaceable>;
-DELETE ... RETURNING <replaceable>expressions</replaceable> INTO <optional>STRICT</optional> <replaceable>target</replaceable>;
-</synopsis>
-
-     where <replaceable>target</replaceable> can be a record variable, a row
-     variable, or a comma-separated list of simple variables and
-     record/row fields.
-     <application>PL/pgSQL</application> variables will be
-     substituted into the rest of the query, and the plan is cached,
-     just as described above for commands that do not return rows.
-     This works for <command>SELECT</>,
-     <command>INSERT</>/<command>UPDATE</>/<command>DELETE</> with
-     <literal>RETURNING</>, and utility commands that return row-set
-     results (such as <command>EXPLAIN</>).
-     Except for the <literal>INTO</> clause, the SQL command is the same
-     as it would be written outside <application>PL/pgSQL</application>.
-    </para>
-
-   <tip>
-<!## PG>
-    <para>
-     Note that this interpretation of <command>SELECT</> with <literal>INTO</>
-     is quite different from <productname>PostgreSQL</>'s regular
-     <command>SELECT INTO</command> command, wherein the <literal>INTO</>
-     target is a newly created table.  If you want to create a table from a
-     <command>SELECT</> result inside a
-     <application>PL/pgSQL</application> function, use the syntax
-     <command>CREATE TABLE ... AS SELECT</command>.
-    </para>
-<!## end>
-<!## XC>
-    <para>
-     This paragraph originally describes internal behavior
-     of <command>SELECT INTO</> command of <productname>PostgerSQL</>,
-     which has not been supported by <productname>Postgres-XC</> yet.
-     THis feature may be supported in the future releases.
-    </para>
-<!## end>
-<!## XL>
-    <para>
-     This paragraph originally describes internal behavior
-     of <command>SELECT INTO</> command of <productname>PostgerSQL</>,
-     which has not been supported by <productname>Postgres-XL</> yet.
-     THis feature may be supported in the future releases.
-    </para>
-<!## end>
-   </tip>
-
-    <para>
-     If a row or a variable list is used as target, the query's result columns
-     must exactly match the structure of the target as to number and data
-     types, or else a run-time error
-     occurs.  When a record variable is the target, it automatically
-     configures itself to the row type of the query result columns.
-    </para>
-
-    <para>
-     The <literal>INTO</> clause can appear almost anywhere in the SQL
-     command.  Customarily it is written either just before or just after
-     the list of <replaceable>select_expressions</replaceable> in a
-     <command>SELECT</> command, or at the end of the command for other
-     command types.  It is recommended that you follow this convention
-     in case the <application>PL/pgSQL</application> parser becomes
-     stricter in future versions.
-    </para>
-
-    <para>
-     If <literal>STRICT</literal> is not specified in the <literal>INTO</>
-     clause, then <replaceable>target</replaceable> will be set to the first
-     row returned by the query, or to nulls if the query returned no rows.
-     (Note that <quote>the first row</> is not
-     well-defined unless you've used <literal>ORDER BY</>.)  Any result rows
-     after the first row are discarded.
-     You can check the special <literal>FOUND</literal> variable (see
-     <xref linkend="plpgsql-statements-diagnostics">) to
-     determine whether a row was returned:
-
-<programlisting>
-SELECT * INTO myrec FROM emp WHERE empname = myname;
-IF NOT FOUND THEN
-    RAISE EXCEPTION 'employee % not found', myname;
-END IF;
-</programlisting>
-
-     If the <literal>STRICT</literal> option is specified, the query must
-     return exactly one row or a run-time error will be reported, either
-     <literal>NO_DATA_FOUND</> (no rows) or <literal>TOO_MANY_ROWS</>
-     (more than one row). You can use an exception block if you wish
-     to catch the error, for example:
-
-<programlisting>
-BEGIN
-    SELECT * INTO STRICT myrec FROM emp WHERE empname = myname;
-    EXCEPTION
-        WHEN NO_DATA_FOUND THEN
-            RAISE EXCEPTION 'employee % not found', myname;
-        WHEN TOO_MANY_ROWS THEN
-            RAISE EXCEPTION 'employee % not unique', myname;
-END;
-</programlisting>
-     Successful execution of a command with <literal>STRICT</>
-     always sets <literal>FOUND</literal> to true.
-    </para>
-
-    <para>
-     For <command>INSERT</>/<command>UPDATE</>/<command>DELETE</> with
-     <literal>RETURNING</>, <application>PL/pgSQL</application> reports
-     an error for more than one returned row, even when
-     <literal>STRICT</literal> is not specified.  This is because there
-     is no option such as <literal>ORDER BY</> with which to determine
-     which affected row should be returned.
-    </para>
-
-    <note>
-     <para>
-      The <literal>STRICT</> option matches the behavior of
-      Oracle PL/SQL's <command>SELECT INTO</command> and related statements.
-     </para>
-    </note>
-
-    <para>
-     To handle cases where you need to process multiple result rows
-     from a SQL query, see <xref linkend="plpgsql-records-iterating">.
-    </para>
-
-   </sect2>
-
-   <sect2 id="plpgsql-statements-executing-dyn">
-    <title>Executing Dynamic Commands</title>
-
-&common;
-    <para>
-     Oftentimes you will want to generate dynamic commands inside your
-     <application>PL/pgSQL</application> functions, that is, commands
-     that will involve different tables or different data types each
-     time they are executed.  <application>PL/pgSQL</application>'s
-     normal attempts to cache plans for commands (as discussed in
-     <xref linkend="plpgsql-plan-caching">) will not work in such
-     scenarios.  To handle this sort of problem, the
-     <command>EXECUTE</command> statement is provided:
-
-<synopsis>
-EXECUTE <replaceable class="command">command-string</replaceable> <optional> INTO <optional>STRICT</optional> <replaceable>target</replaceable> </optional> <optional> USING <replaceable>expression</replaceable> <optional>, ... </optional> </optional>;
-</synopsis>
-
-     where <replaceable>command-string</replaceable> is an expression
-     yielding a string (of type <type>text</type>) containing the
-     command to be executed.  The optional <replaceable>target</replaceable>
-     is a record variable, a row variable, or a comma-separated list of
-     simple variables and record/row fields, into which the results of
-     the command will be stored.  The optional <literal>USING</> expressions
-     supply values to be inserted into the command.
-    </para>
-
-    <para>
-     No substitution of <application>PL/pgSQL</> variables is done on the
-     computed command string.  Any required variable values must be inserted
-     in the command string as it is constructed; or you can use parameters
-     as described below.
-    </para>
-
-    <para>
-     Also, there is no plan caching for commands executed via
-     <command>EXECUTE</command>.  Instead, the
-     command is prepared each time the statement is run. Thus the command
-     string can be dynamically created within the function to perform
-     actions on different tables and columns.
-    </para>
-
-    <para>
-     The <literal>INTO</literal> clause specifies where the results of
-     a SQL command returning rows should be assigned. If a row
-     or variable list is provided, it must exactly match the structure
-     of the query's results (when a
-     record variable is used, it will configure itself to match the
-     result structure automatically). If multiple rows are returned,
-     only the first will be assigned to the <literal>INTO</literal>
-     variable. If no rows are returned, NULL is assigned to the
-     <literal>INTO</literal> variable(s). If no <literal>INTO</literal>
-     clause is specified, the query results are discarded.
-    </para>
-
-    <para>
-     If the <literal>STRICT</> option is given, an error is reported
-     unless the query produces exactly one row.
-    </para>
-
-    <para>
-     The command string can use parameter values, which are referenced
-     in the command as <literal>$1</>, <literal>$2</>, etc.
-     These symbols refer to values supplied in the <literal>USING</>
-     clause.  This method is often preferable to inserting data values
-     into the command string as text: it avoids run-time overhead of
-     converting the values to text and back, and it is much less prone
-     to SQL-injection attacks since there is no need for quoting or escaping.
-     An example is:
-<programlisting>
-EXECUTE 'SELECT count(*) FROM mytable WHERE inserted_by = $1 AND inserted &lt;= $2'
-   INTO c
-   USING checked_user, checked_date;
-</programlisting>
-    </para>
-
-    <para>
-     Note that parameter symbols can only be used for data values
-     &mdash; if you want to use dynamically determined table or column
-     names, you must insert them into the command string textually.
-     For example, if the preceding query needed to be done against a
-     dynamically selected table, you could do this:
-<programlisting>
-EXECUTE 'SELECT count(*) FROM '
-    || tabname::regclass
-    || ' WHERE inserted_by = $1 AND inserted &lt;= $2'
-   INTO c
-   USING checked_user, checked_date;
-</programlisting>
-     Another restriction on parameter symbols is that they only work in
-     <command>SELECT</>, <command>INSERT</>, <command>UPDATE</>, and
-     <command>DELETE</> commands.  In other statement
-     types (generically called utility statements), you must insert
-     values textually even if they are just data values.
-    </para>
-
-    <para>
-     An <command>EXECUTE</> with a simple constant command string and some
-     <literal>USING</> parameters, as in the first example above, is
-     functionally equivalent to just writing the command directly in
-     <application>PL/pgSQL</application> and allowing replacement of
-     <application>PL/pgSQL</application> variables to happen automatically.
-     The important difference is that <command>EXECUTE</> will re-plan
-     the command on each execution, generating a plan that is specific
-     to the current parameter values; whereas
-     <application>PL/pgSQL</application> normally creates a generic plan
-     and caches it for re-use.  In situations where the best plan depends
-     strongly on the parameter values, <command>EXECUTE</> can be
-     significantly faster; while when the plan is not sensitive to parameter
-     values, re-planning will be a waste.
-    </para>
-
-    <para>
-     <command>SELECT INTO</command> is not currently supported within
-     <command>EXECUTE</command>; instead, execute a plain <command>SELECT</>
-     command and specify <literal>INTO</> as part of the <command>EXECUTE</>
-     itself.
-    </para>
-
-   <note>
-    <para>
-     The <application>PL/pgSQL</application>
-     <command>EXECUTE</command> statement is not related to the
-     <xref linkend="sql-execute"> SQL
-     statement supported by the
-<!## PG>
-     <productname>PostgreSQL</productname> server. The server's
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> server. The server's
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> server. The server's
-<!## end>
-     <command>EXECUTE</command> statement cannot be used directly within
-     <application>PL/pgSQL</> functions (and is not needed).
-    </para>
-   </note>
-
-   <example id="plpgsql-quote-literal-example">
-   <title>Quoting Values In Dynamic Queries</title>
-
-    <indexterm>
-     <primary>quote_ident</primary>
-     <secondary>use in PL/pgSQL</secondary>
-    </indexterm>
-
-    <indexterm>
-     <primary>quote_literal</primary>
-     <secondary>use in PL/pgSQL</secondary>
-    </indexterm>
-
-    <indexterm>
-     <primary>quote_nullable</primary>
-     <secondary>use in PL/pgSQL</secondary>
-    </indexterm>
-
-    <indexterm>
-     <primary>format</primary>
-     <secondary>use in PL/pgSQL</secondary>
-    </indexterm>
-
-    <para>
-     When working with dynamic commands you will often have to handle escaping
-     of single quotes.  The recommended method for quoting fixed text in your
-     function body is dollar quoting.  (If you have legacy code that does
-     not use dollar quoting, please refer to the
-     overview in <xref linkend="plpgsql-quote-tips">, which can save you
-     some effort when translating said code to a more reasonable scheme.)
-    </para>
-
-    <para>
-     Dynamic values that are to be inserted into the constructed
-     query require careful handling since they might themselves contain
-     quote characters.
-     An example (this assumes that you are using dollar quoting for the
-     function as a whole, so the quote marks need not be doubled):
-<programlisting>
-EXECUTE 'UPDATE tbl SET '
-        || quote_ident(colname)
-        || ' = '
-        || quote_literal(newvalue)
-        || ' WHERE key = '
-        || quote_literal(keyvalue);
-</programlisting>
-    </para>
-
-    <para>
-     This example demonstrates the use of the
-     <function>quote_ident</function> and
-     <function>quote_literal</function> functions (see <xref
-     linkend="functions-string">).  For safety, expressions containing column
-     or table identifiers should be passed through
-     <function>quote_ident</function> before insertion in a dynamic query.
-     Expressions containing values that should be literal strings in the
-     constructed command should be passed through <function>quote_literal</>.
-     These functions take the appropriate steps to return the input text
-     enclosed in double or single quotes respectively, with any embedded
-     special characters properly escaped.
-    </para>
-
-    <para>
-     Because <function>quote_literal</function> is labelled
-     <literal>STRICT</literal>, it will always return null when called with a
-     null argument.  In the above example, if <literal>newvalue</> or
-     <literal>keyvalue</> were null, the entire dynamic query string would
-     become null, leading to an error from <command>EXECUTE</command>.
-     You can avoid this problem by using the <function>quote_nullable</>
-     function, which works the same as <function>quote_literal</> except that
-     when called with a null argument it returns the string <literal>NULL</>.
-     For example,
-<programlisting>
-EXECUTE 'UPDATE tbl SET '
-        || quote_ident(colname)
-        || ' = '
-        || quote_nullable(newvalue)
-        || ' WHERE key = '
-        || quote_nullable(keyvalue);
-</programlisting>
-     If you are dealing with values that might be null, you should usually
-     use <function>quote_nullable</> in place of <function>quote_literal</>.
-    </para>
-
-    <para>
-     As always, care must be taken to ensure that null values in a query do
-     not deliver unintended results.  For example the <literal>WHERE</> clause
-<programlisting>
-'WHERE key = ' || quote_nullable(keyvalue)
-</programlisting>
-     will never succeed if <literal>keyvalue</> is null, because the
-     result of using the equality operator <literal>=</> with a null operand
-     is always null.  If you wish null to work like an ordinary key value,
-     you would need to rewrite the above as
-<programlisting>
-'WHERE key IS NOT DISTINCT FROM ' || quote_nullable(keyvalue)
-</programlisting>
-     (At present, <literal>IS NOT DISTINCT FROM</> is handled much less
-     efficiently than <literal>=</>, so don't do this unless you must.
-     See <xref linkend="functions-comparison"> for
-     more information on nulls and <literal>IS DISTINCT</>.)
-    </para>
-
-    <para>
-     Note that dollar quoting is only useful for quoting fixed text.
-     It would be a very bad idea to try to write this example as:
-<programlisting>
-EXECUTE 'UPDATE tbl SET '
-        || quote_ident(colname)
-        || ' = $$'
-        || newvalue
-        || '$$ WHERE key = '
-        || quote_literal(keyvalue);
-</programlisting>
-     because it would break if the contents of <literal>newvalue</>
-     happened to contain <literal>$$</>.  The same objection would
-     apply to any other dollar-quoting delimiter you might pick.
-     So, to safely quote text that is not known in advance, you
-     <emphasis>must</> use <function>quote_literal</>,
-     <function>quote_nullable</>, or <function>quote_ident</>, as appropriate.
-    </para>
-
-    <para>
-     Dynamic SQL statements can also be safely constructed using the
-     <function>format</function> function (see <xref
-     linkend="functions-string">). For example:
-<programlisting>
-EXECUTE format('UPDATE tbl SET %I = %L WHERE key = %L', colname, newvalue, keyvalue);
-</programlisting>
-     The <function>format</function> function can be used in conjunction with
-     the <literal>USING</literal> clause:
-<programlisting>
-EXECUTE format('UPDATE tbl SET %I = $1 WHERE key = $2', colname)
-   USING newvalue, keyvalue;
-</programlisting>
-     This form is more efficient, because the parameters
-     <literal>newvalue</literal> and <literal>keyvalue</literal> are not
-     converted to text.
-    </para>
-   </example>
-
-    <para>
-     A much larger example of a dynamic command and
-     <command>EXECUTE</command> can be seen in <xref
-     linkend="plpgsql-porting-ex2">, which builds and executes a
-     <command>CREATE FUNCTION</> command to define a new function.
-    </para>
-   </sect2>
-
-   <sect2 id="plpgsql-statements-diagnostics">
-    <title>Obtaining the Result Status</title>
-
-&common;
-    <para>
-     There are several ways to determine the effect of a command. The
-     first method is to use the <command>GET DIAGNOSTICS</command>
-     command, which has the form:
-
-<synopsis>
-GET DIAGNOSTICS <replaceable>variable</replaceable> = <replaceable>item</replaceable> <optional> , ... </optional>;
-</synopsis>
-
-     This command allows retrieval of system status indicators.  Each
-     <replaceable>item</replaceable> is a key word identifying a state
-     value to be assigned to the specified variable (which should be
-     of the right data type to receive it).  The currently available
-     status items are <varname>ROW_COUNT</>, the number of rows
-     processed by the last <acronym>SQL</acronym> command sent to
-     the <acronym>SQL</acronym> engine, and <varname>RESULT_OID</>,
-     the OID of the last row inserted by the most recent
-     <acronym>SQL</acronym> command.  Note that <varname>RESULT_OID</>
-     is only useful after an <command>INSERT</command> command into a
-     table containing OIDs.
-    </para>
-
-    <para>
-     An example:
-<programlisting>
-GET DIAGNOSTICS integer_var = ROW_COUNT;
-</programlisting>
-    </para>
-
-    <para>
-     The second method to determine the effects of a command is to check the
-     special variable named <literal>FOUND</literal>, which is of
-     type <type>boolean</type>.  <literal>FOUND</literal> starts out
-     false within each <application>PL/pgSQL</application> function call.
-     It is set by each of the following types of statements:
-
-         <itemizedlist>
-          <listitem>
-           <para>
-            A <command>SELECT INTO</command> statement sets
-            <literal>FOUND</literal> true if a row is assigned, false if no
-            row is returned.
-           </para>
-          </listitem>
-          <listitem>
-           <para>
-            A <command>PERFORM</> statement sets <literal>FOUND</literal>
-            true if it produces (and discards) one or more rows, false if
-            no row is produced.
-           </para>
-          </listitem>
-          <listitem>
-           <para>
-            <command>UPDATE</>, <command>INSERT</>, and <command>DELETE</>
-            statements set <literal>FOUND</literal> true if at least one
-            row is affected, false if no row is affected.
-           </para>
-          </listitem>
-          <listitem>
-           <para>
-            A <command>FETCH</> statement sets <literal>FOUND</literal>
-            true if it returns a row, false if no row is returned.
-           </para>
-          </listitem>
-          <listitem>
-           <para>
-            A <command>MOVE</> statement sets <literal>FOUND</literal>
-            true if it successfully repositions the cursor, false otherwise.
-           </para>
-          </listitem>
-          <listitem>
-           <para>
-            A <command>FOR</> or <command>FOREACH</> statement sets
-            <literal>FOUND</literal> true
-            if it iterates one or more times, else false.
-            <literal>FOUND</literal> is set this way when the
-            loop exits; inside the execution of the loop,
-            <literal>FOUND</literal> is not modified by the
-            loop statement, although it might be changed by the
-            execution of other statements within the loop body.
-           </para>
-          </listitem>
-          <listitem>
-           <para>
-            <command>RETURN QUERY</command> and <command>RETURN QUERY
-            EXECUTE</command> statements set <literal>FOUND</literal>
-            true if the query returns at least one row, false if no row
-            is returned.
-           </para>
-          </listitem>
-         </itemizedlist>
-
-     Other <application>PL/pgSQL</application> statements do not change
-     the state of <literal>FOUND</literal>.
-     Note in particular that <command>EXECUTE</command>
-     changes the output of <command>GET DIAGNOSTICS</command>, but
-     does not change <literal>FOUND</literal>.
-    </para>
-
-    <para>
-     <literal>FOUND</literal> is a local variable within each
-     <application>PL/pgSQL</application> function; any changes to it
-     affect only the current function.
-    </para>
-
-   </sect2>
-
-   <sect2 id="plpgsql-statements-null">
-    <title>Doing Nothing At All</title>
-
-&common;
-    <para>
-     Sometimes a placeholder statement that does nothing is useful.
-     For example, it can indicate that one arm of an if/then/else
-     chain is deliberately empty.  For this purpose, use the
-     <command>NULL</command> statement:
-
-<synopsis>
-NULL;
-</synopsis>
-    </para>
-
-    <para>
-     For example, the following two fragments of code are equivalent:
-<programlisting>
-BEGIN
-    y := x / 0;
-EXCEPTION
-    WHEN division_by_zero THEN
-        NULL;  -- ignore the error
-END;
-</programlisting>
-
-<programlisting>
-BEGIN
-    y := x / 0;
-EXCEPTION
-    WHEN division_by_zero THEN  -- ignore the error
-END;
-</programlisting>
-     Which is preferable is a matter of taste.
-    </para>
-
-    <note>
-     <para>
-      In Oracle's PL/SQL, empty statement lists are not allowed, and so
-      <command>NULL</> statements are <emphasis>required</> for situations
-      such as this.  <application>PL/pgSQL</application> allows you to
-      just write nothing, instead.
-     </para>
-    </note>
-
-   </sect2>
-  </sect1>
-
-  <sect1 id="plpgsql-control-structures">
-   <title>Control Structures</title>
-
-&common;
-   <para>
-    Control structures are probably the most useful (and
-    important) part of <application>PL/pgSQL</>. With
-    <application>PL/pgSQL</>'s control structures,
-<!## PG>
-    you can manipulate <productname>PostgreSQL</> data in a very
-<!## end>
-<!## XC>
-    you can manipulate <productname>Postgres-XC</> data in a very
-<!## end>
-<!## XL>
-    you can manipulate <productname>Postgres-XL</> data in a very
-<!## end>
-    flexible and powerful way.
-   </para>
-
-   <sect2 id="plpgsql-statements-returning">
-    <title>Returning From a Function</title>
-
-&common;
-    <para>
-     There are two commands available that allow you to return data
-     from a function: <command>RETURN</command> and <command>RETURN
-     NEXT</command>.
-    </para>
-
-    <sect3>
-     <title><command>RETURN</></title>
-
-<synopsis>
-RETURN <replaceable>expression</replaceable>;
-</synopsis>
-
-&common;
-     <para>
-      <command>RETURN</command> with an expression terminates the
-      function and returns the value of
-      <replaceable>expression</replaceable> to the caller.  This form
-      is used for <application>PL/pgSQL</> functions that do
-      not return a set.
-     </para>
-
-     <para>
-      When returning a scalar type, any expression can be used. The
-      expression's result will be automatically cast into the
-      function's return type as described for assignments. To return a
-      composite (row) value, you must write a record or row variable
-      as the <replaceable>expression</replaceable>.
-     </para>
-
-     <para>
-      If you declared the function with output parameters, write just
-      <command>RETURN</command> with no expression.  The current values
-      of the output parameter variables will be returned.
-     </para>
-
-     <para>
-      If you declared the function to return <type>void</type>, a
-      <command>RETURN</command> statement can be used to exit the function
-      early; but do not write an expression following
-      <command>RETURN</command>.
-     </para>
-
-     <para>
-      The return value of a function cannot be left undefined. If
-      control reaches the end of the top-level block of the function
-      without hitting a <command>RETURN</command> statement, a run-time
-      error will occur.  This restriction does not apply to functions
-      with output parameters and functions returning <type>void</type>,
-      however.  In those cases a <command>RETURN</command> statement is
-      automatically executed if the top-level block finishes.
-     </para>
-    </sect3>
-
-    <sect3>
-     <title><command>RETURN NEXT</> and <command>RETURN QUERY</command></title>
-    <indexterm>
-     <primary>RETURN NEXT</primary>
-     <secondary>in PL/pgSQL</secondary>
-    </indexterm>
-    <indexterm>
-     <primary>RETURN QUERY</primary>
-     <secondary>in PL/pgSQL</secondary>
-    </indexterm>
-
-<synopsis>
-RETURN NEXT <replaceable>expression</replaceable>;
-RETURN QUERY <replaceable>query</replaceable>;
-RETURN QUERY EXECUTE <replaceable class="command">command-string</replaceable> <optional> USING <replaceable>expression</replaceable> <optional>, ... </optional> </optional>;
-</synopsis>
-
-&common;
-     <para>
-      When a <application>PL/pgSQL</> function is declared to return
-      <literal>SETOF <replaceable>sometype</></literal>, the procedure
-      to follow is slightly different.  In that case, the individual
-      items to return are specified by a sequence of <command>RETURN
-      NEXT</command> or <command>RETURN QUERY</command> commands, and
-      then a final <command>RETURN</command> command with no argument
-      is used to indicate that the function has finished executing.
-      <command>RETURN NEXT</command> can be used with both scalar and
-      composite data types; with a composite result type, an entire
-      <quote>table</quote> of results will be returned.
-      <command>RETURN QUERY</command> appends the results of executing
-      a query to the function's result set. <command>RETURN
-      NEXT</command> and <command>RETURN QUERY</command> can be freely
-      intermixed in a single set-returning function, in which case
-      their results will be concatenated.
-     </para>
-
-     <para>
-      <command>RETURN NEXT</command> and <command>RETURN
-      QUERY</command> do not actually return from the function &mdash;
-      they simply append zero or more rows to the function's result
-      set.  Execution then continues with the next statement in the
-      <application>PL/pgSQL</> function.  As successive
-      <command>RETURN NEXT</command> or <command>RETURN
-      QUERY</command> commands are executed, the result set is built
-      up.  A final <command>RETURN</command>, which should have no
-      argument, causes control to exit the function (or you can just
-      let control reach the end of the function).
-     </para>
-
-     <para>
-      <command>RETURN QUERY</command> has a variant
-      <command>RETURN QUERY EXECUTE</command>, which specifies the
-      query to be executed dynamically.  Parameter expressions can
-      be inserted into the computed query string via <literal>USING</>,
-      in just the same way as in the <command>EXECUTE</> command.
-     </para>
-
-     <para>
-      If you declared the function with output parameters, write just
-      <command>RETURN NEXT</command> with no expression.  On each
-      execution, the current values of the output parameter
-      variable(s) will be saved for eventual return as a row of the
-      result.  Note that you must declare the function as returning
-      <literal>SETOF record</literal> when there are multiple output
-      parameters, or <literal>SETOF <replaceable>sometype</></literal>
-      when there is just one output parameter of type
-      <replaceable>sometype</>, in order to create a set-returning
-      function with output parameters.
-     </para>
-
-     <para>
-      Here is an example of a function using <command>RETURN
-      NEXT</command>:
-
-<programlisting>
-CREATE TABLE foo (fooid INT, foosubid INT, fooname TEXT);
-INSERT INTO foo VALUES (1, 2, 'three');
-INSERT INTO foo VALUES (4, 5, 'six');
-
-CREATE OR REPLACE FUNCTION getAllFoo() RETURNS SETOF foo AS
-$BODY$
-DECLARE
-    r foo%rowtype;
-BEGIN
-    FOR r IN SELECT * FROM foo
-    WHERE fooid &gt; 0
-    LOOP
-        -- can do some processing here
-        RETURN NEXT r; -- return current row of SELECT
-    END LOOP;
-    RETURN;
-END
-$BODY$
-LANGUAGE 'plpgsql' ;
-
-SELECT * FROM getallfoo();
-</programlisting>
-     </para>
-
-     <note>
-      <para>
-       The current implementation of <command>RETURN NEXT</command>
-       and <command>RETURN QUERY</command> stores the entire result set
-       before returning from the function, as discussed above.  That
-       means that if a <application>PL/pgSQL</> function produces a
-       very large result set, performance might be poor: data will be
-       written to disk to avoid memory exhaustion, but the function
-       itself will not return until the entire result set has been
-       generated.  A future version of <application>PL/pgSQL</> might
-       allow users to define set-returning functions
-       that do not have this limitation.  Currently, the point at
-       which data begins being written to disk is controlled by the
-       <xref linkend="guc-work-mem">
-       configuration variable.  Administrators who have sufficient
-       memory to store larger result sets in memory should consider
-       increasing this parameter.
-      </para>
-     </note>
-    </sect3>
-   </sect2>
-
-   <sect2 id="plpgsql-conditionals">
-    <title>Conditionals</title>
-
-&common;
-    <para>
-     <command>IF</> and <command>CASE</> statements let you execute
-     alternative commands based on certain conditions.
-     <application>PL/pgSQL</> has three forms of <command>IF</>:
-    <itemizedlist>
-     <listitem>
-      <para><literal>IF ... THEN</></>
-     </listitem>
-     <listitem>
-      <para><literal>IF ... THEN ... ELSE</></>
-     </listitem>
-     <listitem>
-      <para><literal>IF ... THEN ... ELSIF ... THEN ... ELSE</></>
-     </listitem>
-    </itemizedlist>
-
-    and two forms of <command>CASE</>:
-    <itemizedlist>
-     <listitem>
-      <para><literal>CASE ... WHEN ... THEN ... ELSE ... END CASE</></>
-     </listitem>
-     <listitem>
-      <para><literal>CASE WHEN ... THEN ... ELSE ... END CASE</></>
-     </listitem>
-    </itemizedlist>
-    </para>
-
-    <sect3>
-     <title><literal>IF-THEN</></title>
-
-<synopsis>
-IF <replaceable>boolean-expression</replaceable> THEN
-    <replaceable>statements</replaceable>
-END IF;
-</synopsis>
-
-&common;
-       <para>
-        <literal>IF-THEN</literal> statements are the simplest form of
-        <literal>IF</literal>. The statements between
-        <literal>THEN</literal> and <literal>END IF</literal> will be
-        executed if the condition is true. Otherwise, they are
-        skipped.
-       </para>
-
-       <para>
-        Example:
-<programlisting>
-IF v_user_id &lt;&gt; 0 THEN
-    UPDATE users SET email = v_email WHERE user_id = v_user_id;
-END IF;
-</programlisting>
-       </para>
-     </sect3>
-
-     <sect3>
-      <title><literal>IF-THEN-ELSE</></title>
-
-<synopsis>
-IF <replaceable>boolean-expression</replaceable> THEN
-    <replaceable>statements</replaceable>
-ELSE
-    <replaceable>statements</replaceable>
-END IF;
-</synopsis>
-
-&common;
-       <para>
-        <literal>IF-THEN-ELSE</literal> statements add to
-        <literal>IF-THEN</literal> by letting you specify an
-        alternative set of statements that should be executed if the
-        condition is not true.  (Note this includes the case where the
-        condition evaluates to NULL.)
-       </para>
-
-       <para>
-        Examples:
-<programlisting>
-IF parentid IS NULL OR parentid = ''
-THEN
-    RETURN fullname;
-ELSE
-    RETURN hp_true_filename(parentid) || '/' || fullname;
-END IF;
-</programlisting>
-
-<programlisting>
-IF v_count &gt; 0 THEN
-    INSERT INTO users_count (count) VALUES (v_count);
-    RETURN 't';
-ELSE
-    RETURN 'f';
-END IF;
-</programlisting>
-     </para>
-    </sect3>
-
-     <sect3>
-      <title><literal>IF-THEN-ELSIF</></title>
-
-<synopsis>
-IF <replaceable>boolean-expression</replaceable> THEN
-    <replaceable>statements</replaceable>
-<optional> ELSIF <replaceable>boolean-expression</replaceable> THEN
-    <replaceable>statements</replaceable>
-<optional> ELSIF <replaceable>boolean-expression</replaceable> THEN
-    <replaceable>statements</replaceable>
-    ...
-</optional>
-</optional>
-<optional> ELSE
-    <replaceable>statements</replaceable> </optional>
-END IF;
-</synopsis>
-
-&common;
-       <para>
-        Sometimes there are more than just two alternatives.
-        <literal>IF-THEN-ELSIF</> provides a convenient
-        method of checking several alternatives in turn.
-        The <literal>IF</> conditions are tested successively
-        until the first one that is true is found.  Then the
-        associated statement(s) are executed, after which control
-        passes to the next statement after <literal>END IF</>.
-        (Any subsequent <literal>IF</> conditions are <emphasis>not</>
-        tested.)  If none of the <literal>IF</> conditions is true,
-        then the <literal>ELSE</> block (if any) is executed.
-       </para>
-
-       <para>
-        Here is an example:
-
-<programlisting>
-IF number = 0 THEN
-    result := 'zero';
-ELSIF number &gt; 0 THEN
-    result := 'positive';
-ELSIF number &lt; 0 THEN
-    result := 'negative';
-ELSE
-    -- hmm, the only other possibility is that number is null
-    result := 'NULL';
-END IF;
-</programlisting>
-       </para>
-
-       <para>
-        The key word <literal>ELSIF</> can also be spelled
-        <literal>ELSEIF</>.
-       </para>
-
-       <para>
-        An alternative way of accomplishing the same task is to nest
-        <literal>IF-THEN-ELSE</literal> statements, as in the
-        following example:
-
-<programlisting>
-IF demo_row.sex = 'm' THEN
-    pretty_sex := 'man';
-ELSE
-    IF demo_row.sex = 'f' THEN
-        pretty_sex := 'woman';
-    END IF;
-END IF;
-</programlisting>
-       </para>
-
-       <para>
-        However, this method requires writing a matching <literal>END IF</>
-        for each <literal>IF</>, so it is much more cumbersome than
-        using <literal>ELSIF</> when there are many alternatives.
-       </para>
-     </sect3>
-
-     <sect3>
-      <title>Simple <literal>CASE</></title>
-
-<synopsis>
-CASE <replaceable>search-expression</replaceable>
-    WHEN <replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> <optional> ... </optional></optional> THEN
-      <replaceable>statements</replaceable>
-  <optional> WHEN <replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> <optional> ... </optional></optional> THEN
-      <replaceable>statements</replaceable>
-    ... </optional>
-  <optional> ELSE
-      <replaceable>statements</replaceable> </optional>
-END CASE;
-</synopsis>
-
-&common;
-      <para>
-       The simple form of <command>CASE</> provides conditional execution
-       based on equality of operands.  The <replaceable>search-expression</>
-       is evaluated (once) and successively compared to each
-       <replaceable>expression</> in the <literal>WHEN</> clauses.
-       If a match is found, then the corresponding
-       <replaceable>statements</replaceable> are executed, and then control
-       passes to the next statement after <literal>END CASE</>.  (Subsequent
-       <literal>WHEN</> expressions are not evaluated.)  If no match is
-       found, the <literal>ELSE</> <replaceable>statements</replaceable> are
-       executed; but if <literal>ELSE</> is not present, then a
-       <literal>CASE_NOT_FOUND</literal> exception is raised.
-      </para>
-
-      <para>
-       Here is a simple example:
-
-<programlisting>
-CASE x
-    WHEN 1, 2 THEN
-        msg := 'one or two';
-    ELSE
-        msg := 'other value than one or two';
-END CASE;
-</programlisting>
-      </para>
-     </sect3>
-
-     <sect3>
-      <title>Searched <literal>CASE</></title>
-
-<synopsis>
-CASE
-    WHEN <replaceable>boolean-expression</replaceable> THEN
-      <replaceable>statements</replaceable>
-  <optional> WHEN <replaceable>boolean-expression</replaceable> THEN
-      <replaceable>statements</replaceable>
-    ... </optional>
-  <optional> ELSE
-      <replaceable>statements</replaceable> </optional>
-END CASE;
-</synopsis>
-
-&common;
-      <para>
-       The searched form of <command>CASE</> provides conditional execution
-       based on truth of Boolean expressions.  Each <literal>WHEN</> clause's
-       <replaceable>boolean-expression</replaceable> is evaluated in turn,
-       until one is found that yields <literal>true</>.  Then the
-       corresponding <replaceable>statements</replaceable> are executed, and
-       then control passes to the next statement after <literal>END CASE</>.
-       (Subsequent <literal>WHEN</> expressions are not evaluated.)
-       If no true result is found, the <literal>ELSE</>
-       <replaceable>statements</replaceable> are executed;
-       but if <literal>ELSE</> is not present, then a
-       <literal>CASE_NOT_FOUND</literal> exception is raised.
-      </para>
-
-      <para>
-       Here is an example:
-
-<programlisting>
-CASE
-    WHEN x BETWEEN 0 AND 10 THEN
-        msg := 'value is between zero and ten';
-    WHEN x BETWEEN 11 AND 20 THEN
-        msg := 'value is between eleven and twenty';
-END CASE;
-</programlisting>
-      </para>
-
-      <para>
-       This form of <command>CASE</> is entirely equivalent to
-       <literal>IF-THEN-ELSIF</>, except for the rule that reaching
-       an omitted <literal>ELSE</> clause results in an error rather
-       than doing nothing.
-      </para>
-
-     </sect3>
-   </sect2>
-
-   <sect2 id="plpgsql-control-structures-loops">
-    <title>Simple Loops</title>
-
-    <indexterm zone="plpgsql-control-structures-loops">
-     <primary>loop</primary>
-     <secondary>in PL/pgSQL</secondary>
-    </indexterm>
-
-&common;
-    <para>
-     With the <literal>LOOP</>, <literal>EXIT</>,
-     <literal>CONTINUE</>, <literal>WHILE</>, <literal>FOR</>,
-     and <literal>FOREACH</> statements, you can arrange for your
-     <application>PL/pgSQL</> function to repeat a series of commands.
-    </para>
-
-    <sect3>
-     <title><literal>LOOP</></title>
-
-<synopsis>
-<optional> &lt;&lt;<replaceable>label</replaceable>&gt;&gt; </optional>
-LOOP
-    <replaceable>statements</replaceable>
-END LOOP <optional> <replaceable>label</replaceable> </optional>;
-</synopsis>
-
-&common;
-     <para>
-      <literal>LOOP</> defines an unconditional loop that is repeated
-      indefinitely until terminated by an <literal>EXIT</> or
-      <command>RETURN</command> statement.  The optional
-      <replaceable>label</replaceable> can be used by <literal>EXIT</>
-      and <literal>CONTINUE</literal> statements within nested loops to
-      specify which loop those statements refer to.
-     </para>
-    </sect3>
-
-     <sect3>
-      <title><literal>EXIT</></title>
-
-     <indexterm>
-      <primary>EXIT</primary>
-      <secondary>in PL/pgSQL</secondary>
-     </indexterm>
-
-<synopsis>
-EXIT <optional> <replaceable>label</replaceable> </optional> <optional> WHEN <replaceable>boolean-expression</replaceable> </optional>;
-</synopsis>
-
-&common;
-       <para>
-        If no <replaceable>label</replaceable> is given, the innermost
-        loop is terminated and the statement following <literal>END
-        LOOP</> is executed next.  If <replaceable>label</replaceable>
-        is given, it must be the label of the current or some outer
-        level of nested loop or block. Then the named loop or block is
-        terminated and control continues with the statement after the
-        loop's/block's corresponding <literal>END</>.
-       </para>
-
-       <para>
-        If <literal>WHEN</> is specified, the loop exit occurs only if
-        <replaceable>boolean-expression</> is true. Otherwise, control passes
-        to the statement after <literal>EXIT</>.
-       </para>
-
-       <para>
-        <literal>EXIT</> can be used with all types of loops; it is
-        not limited to use with unconditional loops.
-       </para>
-
-       <para>
-        When used with a
-        <literal>BEGIN</literal> block, <literal>EXIT</literal> passes
-        control to the next statement after the end of the block.
-        Note that a label must be used for this purpose; an unlabelled
-        <literal>EXIT</literal> is never considered to match a
-        <literal>BEGIN</literal> block.  (This is a change from
-        pre-8.4 releases of <productname>PostgreSQL</productname>, which
-        would allow an unlabelled <literal>EXIT</literal> to match
-        a <literal>BEGIN</literal> block.)
-       </para>
-
-       <para>
-        Examples:
-<programlisting>
-LOOP
-    -- some computations
-    IF count &gt; 0 THEN
-        EXIT;  -- exit loop
-    END IF;
-END LOOP;
-
-LOOP
-    -- some computations
-    EXIT WHEN count &gt; 0;  -- same result as previous example
-END LOOP;
-
-&lt;&lt;ablock&gt;&gt;
-BEGIN
-    -- some computations
-    IF stocks &gt; 100000 THEN
-        EXIT ablock;  -- causes exit from the BEGIN block
-    END IF;
-    -- computations here will be skipped when stocks &gt; 100000
-END;
-</programlisting>
-       </para>
-     </sect3>
-
-     <sect3>
-      <title><literal>CONTINUE</></title>
-
-     <indexterm>
-      <primary>CONTINUE</primary>
-      <secondary>in PL/pgSQL</secondary>
-     </indexterm>
-
-<synopsis>
-CONTINUE <optional> <replaceable>label</replaceable> </optional> <optional> WHEN <replaceable>boolean-expression</replaceable> </optional>;
-</synopsis>
-
-&common;
-       <para>
-        If no <replaceable>label</> is given, the next iteration of
-        the innermost loop is begun. That is, all statements remaining
-        in the loop body are skipped, and control returns
-        to the loop control expression (if any) to determine whether
-        another loop iteration is needed.
-        If <replaceable>label</> is present, it
-        specifies the label of the loop whose execution will be
-        continued.
-       </para>
-
-       <para>
-        If <literal>WHEN</> is specified, the next iteration of the
-        loop is begun only if <replaceable>boolean-expression</> is
-        true. Otherwise, control passes to the statement after
-        <literal>CONTINUE</>.
-       </para>
-
-       <para>
-        <literal>CONTINUE</> can be used with all types of loops; it
-        is not limited to use with unconditional loops.
-       </para>
-
-       <para>
-        Examples:
-<programlisting>
-LOOP
-    -- some computations
-    EXIT WHEN count &gt; 100;
-    CONTINUE WHEN count &lt; 50;
-    -- some computations for count IN [50 .. 100]
-END LOOP;
-</programlisting>
-       </para>
-     </sect3>
-
-
-     <sect3>
-      <title><literal>WHILE</></title>
-
-     <indexterm>
-      <primary>WHILE</primary>
-      <secondary>in PL/pgSQL</secondary>
-     </indexterm>
-
-<synopsis>
-<optional> &lt;&lt;<replaceable>label</replaceable>&gt;&gt; </optional>
-WHILE <replaceable>boolean-expression</replaceable> LOOP
-    <replaceable>statements</replaceable>
-END LOOP <optional> <replaceable>label</replaceable> </optional>;
-</synopsis>
-
-&common;
-       <para>
-        The <literal>WHILE</> statement repeats a
-        sequence of statements so long as the
-        <replaceable>boolean-expression</replaceable>
-        evaluates to true.  The expression is checked just before
-        each entry to the loop body.
-       </para>
-
-       <para>
-        For example:
-<programlisting>
-WHILE amount_owed &gt; 0 AND gift_certificate_balance &gt; 0 LOOP
-    -- some computations here
-END LOOP;
-
-WHILE NOT done LOOP
-    -- some computations here
-END LOOP;
-</programlisting>
-       </para>
-     </sect3>
-
-     <sect3 id="plpgsql-integer-for">
-      <title><literal>FOR</> (Integer Variant)</title>
-
-<synopsis>
-<optional> &lt;&lt;<replaceable>label</replaceable>&gt;&gt; </optional>
-FOR <replaceable>name</replaceable> IN <optional> REVERSE </optional> <replaceable>expression</replaceable> .. <replaceable>expression</replaceable> <optional> BY <replaceable>expression</replaceable> </optional> LOOP
-    <replaceable>statements</replaceable>
-END LOOP <optional> <replaceable>label</replaceable> </optional>;
-</synopsis>
-
-&common;
-       <para>
-        This form of <literal>FOR</> creates a loop that iterates over a range
-        of integer values. The variable
-        <replaceable>name</replaceable> is automatically defined as type
-        <type>integer</> and exists only inside the loop (any existing
-        definition of the variable name is ignored within the loop).
-        The two expressions giving
-        the lower and upper bound of the range are evaluated once when entering
-        the loop. If the <literal>BY</> clause isn't specified the iteration
-        step is 1, otherwise it's the value specified in the <literal>BY</>
-        clause, which again is evaluated once on loop entry.
-        If <literal>REVERSE</> is specified then the step value is
-        subtracted, rather than added, after each iteration.
-       </para>
-
-       <para>
-        Some examples of integer <literal>FOR</> loops:
-<programlisting>
-FOR i IN 1..10 LOOP
-    -- i will take on the values 1,2,3,4,5,6,7,8,9,10 within the loop
-END LOOP;
-
-FOR i IN REVERSE 10..1 LOOP
-    -- i will take on the values 10,9,8,7,6,5,4,3,2,1 within the loop
-END LOOP;
-
-FOR i IN REVERSE 10..1 BY 2 LOOP
-    -- i will take on the values 10,8,6,4,2 within the loop
-END LOOP;
-</programlisting>
-       </para>
-
-       <para>
-        If the lower bound is greater than the upper bound (or less than,
-        in the <literal>REVERSE</> case), the loop body is not
-        executed at all.  No error is raised.
-       </para>
-
-       <para>
-        If a <replaceable>label</replaceable> is attached to the
-        <literal>FOR</> loop then the integer loop variable can be
-        referenced with a qualified name, using that
-        <replaceable>label</replaceable>.
-       </para>
-     </sect3>
-   </sect2>
-
-   <sect2 id="plpgsql-records-iterating">
-    <title>Looping Through Query Results</title>
-
-&common;
-    <para>
-     Using a different type of <literal>FOR</> loop, you can iterate through
-     the results of a query and manipulate that data
-     accordingly. The syntax is:
-<synopsis>
-<optional> &lt;&lt;<replaceable>label</replaceable>&gt;&gt; </optional>
-FOR <replaceable>target</replaceable> IN <replaceable>query</replaceable> LOOP
-    <replaceable>statements</replaceable>
-END LOOP <optional> <replaceable>label</replaceable> </optional>;
-</synopsis>
-     The <replaceable>target</replaceable> is a record variable, row variable,
-     or comma-separated list of scalar variables.
-     The <replaceable>target</replaceable> is successively assigned each row
-     resulting from the <replaceable>query</replaceable> and the loop body is
-     executed for each row. Here is an example:
-<programlisting>
-CREATE FUNCTION cs_refresh_mviews() RETURNS integer AS $$
-DECLARE
-    mviews RECORD;
-BEGIN
-    RAISE NOTICE 'Refreshing materialized views...';
-
-    FOR mviews IN SELECT * FROM cs_materialized_views ORDER BY sort_key LOOP
-
-        -- Now "mviews" has one record from cs_materialized_views
-
-        RAISE NOTICE 'Refreshing materialized view %s ...', quote_ident(mviews.mv_name);
-        EXECUTE 'TRUNCATE TABLE ' || quote_ident(mviews.mv_name);
-        EXECUTE 'INSERT INTO '
-                   || quote_ident(mviews.mv_name) || ' '
-                   || mviews.mv_query;
-    END LOOP;
-
-    RAISE NOTICE 'Done refreshing materialized views.';
-    RETURN 1;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-
-     If the loop is terminated by an <literal>EXIT</> statement, the last
-     assigned row value is still accessible after the loop.
-    </para>
-
-    <para>
-     The <replaceable>query</replaceable> used in this type of <literal>FOR</>
-     statement can be any SQL command that returns rows to the caller:
-     <command>SELECT</> is the most common case,
-     but you can also use <command>INSERT</>, <command>UPDATE</>, or
-     <command>DELETE</> with a <literal>RETURNING</> clause.  Some utility
-     commands such as <command>EXPLAIN</> will work too.
-    </para>
-
-    <para>
-     <application>PL/pgSQL</> variables are substituted into the query text,
-     and the query plan is cached for possible re-use, as discussed in
-     detail in <xref linkend="plpgsql-var-subst"> and
-     <xref linkend="plpgsql-plan-caching">.
-    </para>
-
-    <para>
-     The <literal>FOR-IN-EXECUTE</> statement is another way to iterate over
-     rows:
-<synopsis>
-<optional> &lt;&lt;<replaceable>label</replaceable>&gt;&gt; </optional>
-FOR <replaceable>target</replaceable> IN EXECUTE <replaceable>text_expression</replaceable> <optional> USING <replaceable>expression</replaceable> <optional>, ... </optional> </optional> LOOP
-    <replaceable>statements</replaceable>
-END LOOP <optional> <replaceable>label</replaceable> </optional>;
-</synopsis>
-     This is like the previous form, except that the source query
-     is specified as a string expression, which is evaluated and replanned
-     on each entry to the <literal>FOR</> loop.  This allows the programmer to
-     choose the speed of a preplanned query or the flexibility of a dynamic
-     query, just as with a plain <command>EXECUTE</command> statement.
-     As with <command>EXECUTE</command>, parameter values can be inserted
-     into the dynamic command via <literal>USING</>.
-    </para>
-
-    <para>
-     Another way to specify the query whose results should be iterated
-     through is to declare it as a cursor.  This is described in
-     <xref linkend="plpgsql-cursor-for-loop">.
-    </para>
-   </sect2>
-
-   <sect2 id="plpgsql-foreach-array">
-    <title>Looping Through Arrays</title>
-
-    <para>
-     The <literal>FOREACH</> loop is much like a <literal>FOR</> loop,
-     but instead of iterating through the rows returned by a SQL query,
-     it iterates through the elements of an array value.
-     (In general, <literal>FOREACH</> is meant for looping through
-     components of a composite-valued expression; variants for looping
-     through composites besides arrays may be added in future.)
-     The <literal>FOREACH</> statement to loop over an array is:
-
-<synopsis>
-<optional> &lt;&lt;<replaceable>label</replaceable>&gt;&gt; </optional>
-FOREACH <replaceable>target</replaceable> <optional> SLICE <replaceable>number</replaceable> </optional> IN ARRAY <replaceable>expression</replaceable> LOOP
-    <replaceable>statements</replaceable>
-END LOOP <optional> <replaceable>label</replaceable> </optional>;
-</synopsis>
-    </para>
-
-    <para>
-     Without <literal>SLICE</>, or if <literal>SLICE 0</> is specified,
-     the loop iterates through individual elements of the array produced
-     by evaluating the <replaceable>expression</replaceable>.
-     The <replaceable>target</replaceable> variable is assigned each
-     element value in sequence, and the loop body is executed for each element.
-     Here is an example of looping through the elements of an integer
-     array:
-
-<programlisting>
-CREATE FUNCTION sum(int[]) RETURNS int8 AS $$
-DECLARE
-  s int8 := 0;
-  x int;
-BEGIN
-  FOREACH x IN ARRAY $1
-  LOOP
-    s := s + x;
-  END LOOP;
-  RETURN s;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-
-     The elements are visited in storage order, regardless of the number of
-     array dimensions.  Although the <replaceable>target</replaceable> is
-     usually just a single variable, it can be a list of variables when
-     looping through an array of composite values (records).  In that case,
-     for each array element, the variables are assigned from successive
-     columns of the composite value.
-    </para>
-
-    <para>
-     With a positive <literal>SLICE</> value, <literal>FOREACH</>
-     iterates through slices of the array rather than single elements.
-     The <literal>SLICE</> value must be an integer constant not larger
-     than the number of dimensions of the array.  The
-     <replaceable>target</replaceable> variable must be an array,
-     and it receives successive slices of the array value, where each slice
-     is of the number of dimensions specified by <literal>SLICE</>.
-     Here is an example of iterating through one-dimensional slices:
-
-<programlisting>
-CREATE FUNCTION scan_rows(int[]) RETURNS void AS $$
-DECLARE
-  x int[];
-BEGIN
-  FOREACH x SLICE 1 IN ARRAY $1
-  LOOP
-    RAISE NOTICE 'row = %', x;
-  END LOOP;
-END;
-$$ LANGUAGE plpgsql;
-
-SELECT scan_rows(ARRAY[[1,2,3],[4,5,6],[7,8,9],[10,11,12]]);
-
-NOTICE:  row = {1,2,3}
-NOTICE:  row = {4,5,6}
-NOTICE:  row = {7,8,9}
-NOTICE:  row = {10,11,12}
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2 id="plpgsql-error-trapping">
-    <title>Trapping Errors</title>
-
-    <indexterm>
-     <primary>exceptions</primary>
-     <secondary>in PL/pgSQL</secondary>
-    </indexterm>
-
-&common;
-    <para>
-     By default, any error occurring in a <application>PL/pgSQL</>
-     function aborts execution of the function, and indeed of the
-     surrounding transaction as well.  You can trap errors and recover
-     from them by using a <command>BEGIN</> block with an
-     <literal>EXCEPTION</> clause.  The syntax is an extension of the
-     normal syntax for a <command>BEGIN</> block:
-
-<synopsis>
-<optional> &lt;&lt;<replaceable>label</replaceable>&gt;&gt; </optional>
-<optional> DECLARE
-    <replaceable>declarations</replaceable> </optional>
-BEGIN
-    <replaceable>statements</replaceable>
-EXCEPTION
-    WHEN <replaceable>condition</replaceable> <optional> OR <replaceable>condition</replaceable> ... </optional> THEN
-        <replaceable>handler_statements</replaceable>
-    <optional> WHEN <replaceable>condition</replaceable> <optional> OR <replaceable>condition</replaceable> ... </optional> THEN
-          <replaceable>handler_statements</replaceable>
-      ... </optional>
-END;
-</synopsis>
-    </para>
-
-    <para>
-     If no error occurs, this form of block simply executes all the
-     <replaceable>statements</replaceable>, and then control passes
-     to the next statement after <literal>END</>.  But if an error
-     occurs within the <replaceable>statements</replaceable>, further
-     processing of the <replaceable>statements</replaceable> is
-     abandoned, and control passes to the <literal>EXCEPTION</> list.
-     The list is searched for the first <replaceable>condition</replaceable>
-     matching the error that occurred.  If a match is found, the
-     corresponding <replaceable>handler_statements</replaceable> are
-     executed, and then control passes to the next statement after
-     <literal>END</>.  If no match is found, the error propagates out
-     as though the <literal>EXCEPTION</> clause were not there at all:
-     the error can be caught by an enclosing block with
-     <literal>EXCEPTION</>, or if there is none it aborts processing
-     of the function.
-    </para>
-
-    <para>
-     The <replaceable>condition</replaceable> names can be any of
-     those shown in <xref linkend="errcodes-appendix">.  A category
-     name matches any error within its category.  The special
-     condition name <literal>OTHERS</> matches every error type except
-     <literal>QUERY_CANCELED</>.  (It is possible, but often unwise,
-     to trap <literal>QUERY_CANCELED</> by name.)  Condition names are
-     not case-sensitive.  Also, an error condition can be specified
-     by <literal>SQLSTATE</> code; for example these are equivalent:
-<programlisting>
-WHEN division_by_zero THEN ...
-WHEN SQLSTATE '22012' THEN ...
-</programlisting>
-    </para>
-
-    <para>
-     If a new error occurs within the selected
-     <replaceable>handler_statements</replaceable>, it cannot be caught
-     by this <literal>EXCEPTION</> clause, but is propagated out.
-     A surrounding <literal>EXCEPTION</> clause could catch it.
-    </para>
-
-    <para>
-     When an error is caught by an <literal>EXCEPTION</> clause,
-     the local variables of the <application>PL/pgSQL</> function
-     remain as they were when the error occurred, but all changes
-     to persistent database state within the block are rolled back.
-     As an example, consider this fragment:
-
-<programlisting>
-INSERT INTO mytab(firstname, lastname) VALUES('Tom', 'Jones');
-BEGIN
-    UPDATE mytab SET firstname = 'Joe' WHERE lastname = 'Jones';
-    x := x + 1;
-    y := x / 0;
-EXCEPTION
-    WHEN division_by_zero THEN
-        RAISE NOTICE 'caught division_by_zero';
-        RETURN x;
-END;
-</programlisting>
-
-     When control reaches the assignment to <literal>y</>, it will
-     fail with a <literal>division_by_zero</> error.  This will be caught by
-     the <literal>EXCEPTION</> clause.  The value returned in the
-     <command>RETURN</> statement will be the incremented value of
-     <literal>x</>, but the effects of the <command>UPDATE</> command will
-     have been rolled back.  The <command>INSERT</> command preceding the
-     block is not rolled back, however, so the end result is that the database
-     contains <literal>Tom Jones</> not <literal>Joe Jones</>.
-    </para>
-
-    <tip>
-     <para>
-      A block containing an <literal>EXCEPTION</> clause is significantly
-      more expensive to enter and exit than a block without one.  Therefore,
-      don't use <literal>EXCEPTION</> without need.
-     </para>
-    </tip>
-
-    <para>
-     Within an exception handler, the <varname>SQLSTATE</varname>
-     variable contains the error code that corresponds to the
-     exception that was raised (refer to <xref
-     linkend="errcodes-table"> for a list of possible error
-     codes). The <varname>SQLERRM</varname> variable contains the
-     error message associated with the exception. These variables are
-     undefined outside exception handlers.
-    </para>
-
-    <example id="plpgsql-upsert-example">
-    <title>Exceptions with <command>UPDATE</>/<command>INSERT</></title>
-    <para>
-
-    This example uses exception handling to perform either
-    <command>UPDATE</> or <command>INSERT</>, as appropriate:
-
-<programlisting>
-CREATE TABLE db (a INT PRIMARY KEY, b TEXT);
-
-CREATE FUNCTION merge_db(key INT, data TEXT) RETURNS VOID AS
-$$
-BEGIN
-    LOOP
-        -- first try to update the key
-        UPDATE db SET b = data WHERE a = key;
-        IF found THEN
-            RETURN;
-        END IF;
-        -- not there, so try to insert the key
-        -- if someone else inserts the same key concurrently,
-        -- we could get a unique-key failure
-        BEGIN
-            INSERT INTO db(a,b) VALUES (key, data);
-            RETURN;
-        EXCEPTION WHEN unique_violation THEN
-            -- Do nothing, and loop to try the UPDATE again.
-        END;
-    END LOOP;
-END;
-$$
-LANGUAGE plpgsql;
-
-SELECT merge_db(1, 'david');
-SELECT merge_db(1, 'dennis');
-</programlisting>
-     This example assumes the <literal>unique_violation</> error is caused by
-     the <command>INSERT</>, and not by an <command>INSERT</> trigger function
-     on the table.
-    </para>
-    </example>
-  </sect2>
-  </sect1>
-
-  <sect1 id="plpgsql-cursors">
-   <title>Cursors</title>
-
-   <indexterm zone="plpgsql-cursors">
-    <primary>cursor</primary>
-    <secondary>in PL/pgSQL</secondary>
-   </indexterm>
-
-&common;
-   <para>
-    Rather than executing a whole query at once, it is possible to set
-    up a <firstterm>cursor</> that encapsulates the query, and then read
-    the query result a few rows at a time. One reason for doing this is
-    to avoid memory overrun when the result contains a large number of
-    rows. (However, <application>PL/pgSQL</> users do not normally need
-    to worry about that, since <literal>FOR</> loops automatically use a cursor
-    internally to avoid memory problems.) A more interesting usage is to
-    return a reference to a cursor that a function has created, allowing the
-    caller to read the rows. This provides an efficient way to return
-    large row sets from functions.
-   </para>
-
-   <sect2 id="plpgsql-cursor-declarations">
-    <title>Declaring Cursor Variables</title>
-
-&common;
-    <para>
-     All access to cursors in <application>PL/pgSQL</> goes through
-     cursor variables, which are always of the special data type
-     <type>refcursor</>.  One way to create a cursor variable
-     is just to declare it as a variable of type <type>refcursor</>.
-     Another way is to use the cursor declaration syntax,
-     which in general is:
-<synopsis>
-<replaceable>name</replaceable> <optional> <optional> NO </optional> SCROLL </optional> CURSOR <optional> ( <replaceable>arguments</replaceable> ) </optional> FOR <replaceable>query</replaceable>;
-</synopsis>
-     (<literal>FOR</> can be replaced by <literal>IS</> for
-     <productname>Oracle</productname> compatibility.)
-     If <literal>SCROLL</> is specified, the cursor will be capable of
-     scrolling backward; if <literal>NO SCROLL</> is specified, backward
-     fetches will be rejected; if neither specification appears, it is
-     query-dependent whether backward fetches will be allowed.
-     <replaceable>arguments</replaceable>, if specified, is a
-     comma-separated list of pairs <literal><replaceable>name</replaceable>
-     <replaceable>datatype</replaceable></literal> that define names to be
-     replaced by parameter values in the given query.  The actual
-     values to substitute for these names will be specified later,
-     when the cursor is opened.
-    </para>
-    <para>
-     Some examples:
-<programlisting>
-DECLARE
-    curs1 refcursor;
-    curs2 CURSOR FOR SELECT * FROM tenk1;
-    curs3 CURSOR (key integer) IS SELECT * FROM tenk1 WHERE unique1 = key;
-</programlisting>
-     All three of these variables have the data type <type>refcursor</>,
-     but the first can be used with any query, while the second has
-     a fully specified query already <firstterm>bound</> to it, and the last
-     has a parameterized query bound to it.  (<literal>key</> will be
-     replaced by an integer parameter value when the cursor is opened.)
-     The variable <literal>curs1</>
-     is said to be <firstterm>unbound</> since it is not bound to
-     any particular query.
-    </para>
-   </sect2>
-
-   <sect2 id="plpgsql-cursor-opening">
-    <title>Opening Cursors</title>
-
-&common;
-    <para>
-     Before a cursor can be used to retrieve rows, it must be
-     <firstterm>opened</>. (This is the equivalent action to the SQL
-     command <command>DECLARE CURSOR</>.) <application>PL/pgSQL</> has
-     three forms of the <command>OPEN</> statement, two of which use unbound
-     cursor variables while the third uses a bound cursor variable.
-    </para>
-
-    <note>
-     <para>
-      Bound cursor variables can also be used without explicitly opening the cursor,
-      via the <command>FOR</> statement described in
-      <xref linkend="plpgsql-cursor-for-loop">.
-     </para>
-    </note>
-
-    <sect3>
-     <title><command>OPEN FOR</command> <replaceable>query</replaceable></title>
-
-<synopsis>
-OPEN <replaceable>unbound_cursorvar</replaceable> <optional> <optional> NO </optional> SCROLL </optional> FOR <replaceable>query</replaceable>;
-</synopsis>
-
-&common;
-       <para>
-        The cursor variable is opened and given the specified query to
-        execute.  The cursor cannot be open already, and it must have been
-        declared as an unbound cursor variable (that is, as a simple
-        <type>refcursor</> variable).  The query must be a
-        <command>SELECT</command>, or something else that returns rows
-        (such as <command>EXPLAIN</>).  The query
-        is treated in the same way as other SQL commands in
-        <application>PL/pgSQL</>: <application>PL/pgSQL</>
-        variable names are substituted, and the query plan is cached for
-        possible reuse.  When a <application>PL/pgSQL</>
-        variable is substituted into the cursor query, the value that is
-        substituted is the one it has at the time of the <command>OPEN</>;
-        subsequent changes to the variable will not affect the cursor's
-        behavior.
-        The <literal>SCROLL</> and <literal>NO SCROLL</>
-        options have the same meanings as for a bound cursor.
-       </para>
-
-       <para>
-        An example:
-<programlisting>
-OPEN curs1 FOR SELECT * FROM foo WHERE key = mykey;
-</programlisting>
-       </para>
-     </sect3>
-
-    <sect3>
-     <title><command>OPEN FOR EXECUTE</command></title>
-
-<synopsis>
-OPEN <replaceable>unbound_cursorvar</replaceable> <optional> <optional> NO </optional> SCROLL </optional> FOR EXECUTE <replaceable class="command">query_string</replaceable>
-                                     <optional> USING <replaceable>expression</replaceable> <optional>, ... </optional> </optional>;
-</synopsis>
-
-&common;
-         <para>
-          The cursor variable is opened and given the specified query to
-          execute.  The cursor cannot be open already, and it must have been
-          declared as an unbound cursor variable (that is, as a simple
-          <type>refcursor</> variable).  The query is specified as a string
-          expression, in the same way as in the <command>EXECUTE</command>
-          command.  As usual, this gives flexibility so the query plan can vary
-          from one run to the next (see <xref linkend="plpgsql-plan-caching">),
-          and it also means that variable substitution is not done on the
-          command string. As with <command>EXECUTE</command>, parameter values
-          can be inserted into the dynamic command via <literal>USING</>.
-          The <literal>SCROLL</> and
-          <literal>NO SCROLL</> options have the same meanings as for a bound
-          cursor.
-         </para>
-
-       <para>
-        An example:
-<programlisting>
-OPEN curs1 FOR EXECUTE 'SELECT * FROM ' || quote_ident(tabname)
-                                        || ' WHERE col1 = $1' USING keyvalue;
-</programlisting>
-        In this example, the table name is inserted into the query textually,
-        so use of <function>quote_ident()</> is recommended to guard against
-        SQL injection.  The comparison value for <literal>col1</> is inserted
-        via a <literal>USING</> parameter, so it needs no quoting.
-       </para>
-     </sect3>
-
-    <sect3>
-     <title>Opening a Bound Cursor</title>
-
-<synopsis>
-OPEN <replaceable>bound_cursorvar</replaceable> <optional> ( <replaceable>argument_values</replaceable> ) </optional>;
-</synopsis>
-
-&common;
-         <para>
-          This form of <command>OPEN</command> is used to open a cursor
-          variable whose query was bound to it when it was declared.  The
-          cursor cannot be open already.  A list of actual argument value
-          expressions must appear if and only if the cursor was declared to
-          take arguments.  These values will be substituted in the query.
-          The query plan for a bound cursor is always considered cacheable;
-          there is no equivalent of <command>EXECUTE</command> in this case.
-          Notice that <literal>SCROLL</> and
-          <literal>NO SCROLL</> cannot be specified, as the cursor's scrolling
-          behavior was already determined.
-         </para>
-
-         <para>
-          Note that because variable substitution is done on the bound
-          cursor's query, there are two ways to pass values into the cursor:
-          either with an explicit argument to <command>OPEN</>, or
-          implicitly by referencing a <application>PL/pgSQL</> variable
-          in the query.  However, only variables declared before the bound
-          cursor was declared will be substituted into it.  In either case
-          the value to be passed is determined at the time of the
-          <command>OPEN</>.
-         </para>
-
-    <para>
-     Examples:
-<programlisting>
-OPEN curs2;
-OPEN curs3(42);
-</programlisting>
-       </para>
-     </sect3>
-   </sect2>
-
-   <sect2 id="plpgsql-cursor-using">
-    <title>Using Cursors</title>
-
-&common;
-    <para>
-     Once a cursor has been opened, it can be manipulated with the
-     statements described here.
-    </para>
-
-    <para>
-     These manipulations need not occur in the same function that
-     opened the cursor to begin with.  You can return a <type>refcursor</>
-     value out of a function and let the caller operate on the cursor.
-     (Internally, a <type>refcursor</> value is simply the string name
-     of a so-called portal containing the active query for the cursor.  This name
-     can be passed around, assigned to other <type>refcursor</> variables,
-     and so on, without disturbing the portal.)
-    </para>
-
-    <para>
-     All portals are implicitly closed at transaction end.  Therefore
-     a <type>refcursor</> value is usable to reference an open cursor
-     only until the end of the transaction.
-    </para>
-
-    <sect3>
-     <title><literal>FETCH</></title>
-
-<synopsis>
-FETCH <optional> <replaceable>direction</replaceable> { FROM | IN } </optional> <replaceable>cursor</replaceable> INTO <replaceable>target</replaceable>;
-</synopsis>
-
-&common;
-    <para>
-     <command>FETCH</command> retrieves the next row from the
-     cursor into a target, which might be a row variable, a record
-     variable, or a comma-separated list of simple variables, just like
-     <command>SELECT INTO</command>.  If there is no next row, the
-     target is set to NULL(s).  As with <command>SELECT
-     INTO</command>, the special variable <literal>FOUND</literal> can
-     be checked to see whether a row was obtained or not.
-    </para>
-
-    <para>
-     The <replaceable>direction</replaceable> clause can be any of the
-     variants allowed in the SQL <xref linkend="sql-fetch">
-     command except the ones that can fetch
-     more than one row; namely, it can be
-     <literal>NEXT</>,
-     <literal>PRIOR</>,
-     <literal>FIRST</>,
-     <literal>LAST</>,
-     <literal>ABSOLUTE</> <replaceable>count</replaceable>,
-     <literal>RELATIVE</> <replaceable>count</replaceable>,
-     <literal>FORWARD</>, or
-     <literal>BACKWARD</>.
-     Omitting <replaceable>direction</replaceable> is the same
-     as specifying <literal>NEXT</>.
-     <replaceable>direction</replaceable> values that require moving
-     backward are likely to fail unless the cursor was declared or opened
-     with the <literal>SCROLL</> option.
-    </para>
-
-    <para>
-     <replaceable>cursor</replaceable> must be the name of a <type>refcursor</>
-     variable that references an open cursor portal.
-    </para>
-
-    <para>
-     Examples:
-<programlisting>
-FETCH curs1 INTO rowvar;
-FETCH curs2 INTO foo, bar, baz;
-FETCH LAST FROM curs3 INTO x, y;
-FETCH RELATIVE -2 FROM curs4 INTO x;
-</programlisting>
-       </para>
-     </sect3>
-
-    <sect3>
-     <title><literal>MOVE</></title>
-
-<synopsis>
-MOVE <optional> <replaceable>direction</replaceable> { FROM | IN } </optional> <replaceable>cursor</replaceable>;
-</synopsis>
-
-&common;
-    <para>
-     <command>MOVE</command> repositions a cursor without retrieving
-     any data. <command>MOVE</command> works exactly like the
-     <command>FETCH</command> command, except it only repositions the
-     cursor and does not return the row moved to. As with <command>SELECT
-     INTO</command>, the special variable <literal>FOUND</literal> can
-     be checked to see whether there was a next row to move to.
-    </para>
-
-    <para>
-     The <replaceable>direction</replaceable> clause can be any of the
-     variants allowed in the SQL <xref linkend="sql-fetch">
-     command, namely
-     <literal>NEXT</>,
-     <literal>PRIOR</>,
-     <literal>FIRST</>,
-     <literal>LAST</>,
-     <literal>ABSOLUTE</> <replaceable>count</replaceable>,
-     <literal>RELATIVE</> <replaceable>count</replaceable>,
-     <literal>ALL</>,
-     <literal>FORWARD</> <optional> <replaceable>count</replaceable> | <literal>ALL</> </optional>, or
-     <literal>BACKWARD</> <optional> <replaceable>count</replaceable> | <literal>ALL</> </optional>.
-     Omitting <replaceable>direction</replaceable> is the same
-     as specifying <literal>NEXT</>.
-     <replaceable>direction</replaceable> values that require moving
-     backward are likely to fail unless the cursor was declared or opened
-     with the <literal>SCROLL</> option.
-    </para>
-
-    <para>
-     Examples:
-<programlisting>
-MOVE curs1;
-MOVE LAST FROM curs3;
-MOVE RELATIVE -2 FROM curs4;
-MOVE FORWARD 2 FROM curs4;
-</programlisting>
-       </para>
-     </sect3>
-
-    <sect3>
-     <title><literal>UPDATE/DELETE WHERE CURRENT OF</></title>
-
-<synopsis>
-UPDATE <replaceable>table</replaceable> SET ... WHERE CURRENT OF <replaceable>cursor</replaceable>;
-DELETE FROM <replaceable>table</replaceable> WHERE CURRENT OF <replaceable>cursor</replaceable>;
-</synopsis>
-
-&common;
-       <para>
-        When a cursor is positioned on a table row, that row can be updated
-        or deleted using the cursor to identify the row.  There are
-        restrictions on what the cursor's query can be (in particular,
-        no grouping) and it's best to use <literal>FOR UPDATE</> in the
-        cursor.  For more information see the
-        <xref linkend="sql-declare">
-        reference page.
-       </para>
-
-       <para>
-        An example:
-<programlisting>
-UPDATE foo SET dataval = myval WHERE CURRENT OF curs1;
-</programlisting>
-       </para>
-     </sect3>
-
-    <sect3>
-     <title><literal>CLOSE</></title>
-
-<synopsis>
-CLOSE <replaceable>cursor</replaceable>;
-</synopsis>
-
-&common;
-       <para>
-        <command>CLOSE</command> closes the portal underlying an open
-        cursor.  This can be used to release resources earlier than end of
-        transaction, or to free up the cursor variable to be opened again.
-       </para>
-
-       <para>
-        An example:
-<programlisting>
-CLOSE curs1;
-</programlisting>
-       </para>
-     </sect3>
-
-    <sect3>
-     <title>Returning Cursors</title>
-
-&common;
-       <para>
-        <application>PL/pgSQL</> functions can return cursors to the
-        caller. This is useful to return multiple rows or columns,
-        especially with very large result sets.  To do this, the function
-        opens the cursor and returns the cursor name to the caller (or simply
-        opens the cursor using a portal name specified by or otherwise known
-        to the caller).  The caller can then fetch rows from the cursor. The
-        cursor can be closed by the caller, or it will be closed automatically
-        when the transaction closes.
-       </para>
-
-       <para>
-        The portal name used for a cursor can be specified by the
-        programmer or automatically generated.  To specify a portal name,
-        simply assign a string to the <type>refcursor</> variable before
-        opening it.  The string value of the <type>refcursor</> variable
-        will be used by <command>OPEN</> as the name of the underlying portal.
-        However, if the <type>refcursor</> variable is null,
-        <command>OPEN</> automatically generates a name that does not
-        conflict with any existing portal, and assigns it to the
-        <type>refcursor</> variable.
-       </para>
-
-       <note>
-        <para>
-         A bound cursor variable is initialized to the string value
-         representing its name, so that the portal name is the same as
-         the cursor variable name, unless the programmer overrides it
-         by assignment before opening the cursor.  But an unbound cursor
-         variable defaults to the null value initially, so it will receive
-         an automatically-generated unique name, unless overridden.
-        </para>
-       </note>
-
-       <para>
-        The following example shows one way a cursor name can be supplied by
-        the caller:
-
-<programlisting>
-CREATE TABLE test (col text);
-INSERT INTO test VALUES ('123');
-
-CREATE FUNCTION reffunc(refcursor) RETURNS refcursor AS '
-BEGIN
-    OPEN $1 FOR SELECT col FROM test;
-    RETURN $1;
-END;
-' LANGUAGE plpgsql;
-
-BEGIN;
-SELECT reffunc('funccursor');
-FETCH ALL IN funccursor;
-COMMIT;
-</programlisting>
-       </para>
-
-       <para>
-        The following example uses automatic cursor name generation:
-
-<programlisting>
-CREATE FUNCTION reffunc2() RETURNS refcursor AS '
-DECLARE
-    ref refcursor;
-BEGIN
-    OPEN ref FOR SELECT col FROM test;
-    RETURN ref;
-END;
-' LANGUAGE plpgsql;
-
--- need to be in a transaction to use cursors.
-BEGIN;
-SELECT reffunc2();
-
-      reffunc2
---------------------
- &lt;unnamed cursor 1&gt;
-(1 row)
-
-FETCH ALL IN "&lt;unnamed cursor 1&gt;";
-COMMIT;
-</programlisting>
-       </para>
-
-       <para>
-        The following example shows one way to return multiple cursors
-        from a single function:
-
-<programlisting>
-CREATE FUNCTION myfunc(refcursor, refcursor) RETURNS SETOF refcursor AS $$
-BEGIN
-    OPEN $1 FOR SELECT * FROM table_1;
-    RETURN NEXT $1;
-    OPEN $2 FOR SELECT * FROM table_2;
-    RETURN NEXT $2;
-END;
-$$ LANGUAGE plpgsql;
-
--- need to be in a transaction to use cursors.
-BEGIN;
-
-SELECT * FROM myfunc('a', 'b');
-
-FETCH ALL FROM a;
-FETCH ALL FROM b;
-COMMIT;
-</programlisting>
-       </para>
-     </sect3>
-   </sect2>
-
-   <sect2 id="plpgsql-cursor-for-loop">
-    <title>Looping Through a Cursor's Result</title>
-
-&common;
-    <para>
-     There is a variant of the <command>FOR</> statement that allows
-     iterating through the rows returned by a cursor.  The syntax is:
-
-<synopsis>
-<optional> &lt;&lt;<replaceable>label</replaceable>&gt;&gt; </optional>
-FOR <replaceable>recordvar</replaceable> IN <replaceable>bound_cursorvar</replaceable> <optional> ( <replaceable>argument_values</replaceable> ) </optional> LOOP
-    <replaceable>statements</replaceable>
-END LOOP <optional> <replaceable>label</replaceable> </optional>;
-</synopsis>
-
-     The cursor variable must have been bound to some query when it was
-     declared, and it <emphasis>cannot</> be open already.  The
-     <command>FOR</> statement automatically opens the cursor, and it closes
-     the cursor again when the loop exits.  A list of actual argument value
-     expressions must appear if and only if the cursor was declared to take
-     arguments.  These values will be substituted in the query, in just
-     the same way as during an <command>OPEN</>.
-     The variable <replaceable>recordvar</replaceable> is automatically
-     defined as type <type>record</> and exists only inside the loop (any
-     existing definition of the variable name is ignored within the loop).
-     Each row returned by the cursor is successively assigned to this
-     record variable and the loop body is executed.
-    </para>
-   </sect2>
-
-  </sect1>
-
-  <sect1 id="plpgsql-errors-and-messages">
-   <title>Errors and Messages</title>
-
-   <indexterm>
-    <primary>RAISE</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>reporting errors</primary>
-    <secondary>in PL/pgSQL</secondary>
-   </indexterm>
-
-&common;
-   <para>
-    Use the <command>RAISE</command> statement to report messages and
-    raise errors.
-
-<synopsis>
-RAISE <optional> <replaceable class="parameter">level</replaceable> </optional> '<replaceable class="parameter">format</replaceable>' <optional>, <replaceable class="parameter">expression</replaceable> <optional>, ... </optional></optional> <optional> USING <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">expression</replaceable> <optional>, ... </optional> </optional>;
-RAISE <optional> <replaceable class="parameter">level</replaceable> </optional> <replaceable class="parameter">condition_name</> <optional> USING <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">expression</replaceable> <optional>, ... </optional> </optional>;
-RAISE <optional> <replaceable class="parameter">level</replaceable> </optional> SQLSTATE '<replaceable class="parameter">sqlstate</>' <optional> USING <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">expression</replaceable> <optional>, ... </optional> </optional>;
-RAISE <optional> <replaceable class="parameter">level</replaceable> </optional> USING <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">expression</replaceable> <optional>, ... </optional>;
-RAISE ;
-</synopsis>
-
-    The <replaceable class="parameter">level</replaceable> option specifies
-    the error severity.  Allowed levels are <literal>DEBUG</literal>,
-    <literal>LOG</literal>, <literal>INFO</literal>,
-    <literal>NOTICE</literal>, <literal>WARNING</literal>,
-    and <literal>EXCEPTION</literal>, with <literal>EXCEPTION</literal>
-    being the default.
-    <literal>EXCEPTION</literal> raises an error (which normally aborts the
-    current transaction); the other levels only generate messages of different
-    priority levels.
-    Whether messages of a particular priority are reported to the client,
-    written to the server log, or both is controlled by the
-    <xref linkend="guc-log-min-messages"> and
-    <xref linkend="guc-client-min-messages"> configuration
-    variables. See <xref linkend="runtime-config"> for more
-    information.
-   </para>
-
-   <para>
-    After <replaceable class="parameter">level</replaceable> if any,
-    you can write a <replaceable class="parameter">format</replaceable>
-    (which must be a simple string literal, not an expression).  The
-    format string specifies the error message text to be reported.
-    The format string can be followed
-    by optional argument expressions to be inserted into the message.
-    Inside the format string, <literal>%</literal> is replaced by the
-    string representation of the next optional argument's value. Write
-    <literal>%%</literal> to emit a literal <literal>%</literal>.
-   </para>
-
-   <para>
-    In this example, the value of <literal>v_job_id</> will replace the
-    <literal>%</literal> in the string:
-<programlisting>
-RAISE NOTICE 'Calling cs_create_job(%)', v_job_id;
-</programlisting>
-   </para>
-
-   <para>
-    You can attach additional information to the error report by writing
-    <literal>USING</> followed by <replaceable
-    class="parameter">option</replaceable> = <replaceable
-    class="parameter">expression</replaceable> items.  The allowed
-    <replaceable class="parameter">option</replaceable> keywords are
-    <literal>MESSAGE</>, <literal>DETAIL</>, <literal>HINT</>, and
-    <literal>ERRCODE</>, while each <replaceable
-    class="parameter">expression</replaceable> can be any string-valued
-    expression.
-    <literal>MESSAGE</> sets the error message text (this option can't
-    be used in the form of <command>RAISE</> that includes a format
-    string before <literal>USING</>).
-    <literal>DETAIL</> supplies an error detail message, while
-    <literal>HINT</> supplies a hint message.
-    <literal>ERRCODE</> specifies the error code (SQLSTATE) to report,
-    either by condition name as shown in <xref linkend="errcodes-appendix">,
-    or directly as a five-character SQLSTATE code.
-   </para>
-
-   <para>
-    This example will abort the transaction with the given error message
-    and hint:
-<programlisting>
-RAISE EXCEPTION 'Nonexistent ID --> %', user_id
-      USING HINT = 'Please check your user id';
-</programlisting>
-   </para>
-
-   <para>
-    These two examples show equivalent ways of setting the SQLSTATE:
-<programlisting>
-RAISE 'Duplicate user ID: %', user_id USING ERRCODE = 'unique_violation';
-RAISE 'Duplicate user ID: %', user_id USING ERRCODE = '23505';
-</programlisting>
-   </para>
-
-   <para>
-    There is a second <command>RAISE</> syntax in which the main argument
-    is the condition name or SQLSTATE to be reported, for example:
-<programlisting>
-RAISE division_by_zero;
-RAISE SQLSTATE '22012';
-</programlisting>
-    In this syntax, <literal>USING</> can be used to supply a custom
-    error message, detail, or hint.  Another way to do the earlier
-    example is
-<programlisting>
-RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
-</programlisting>
-   </para>
-
-   <para>
-    Still another variant is to write <literal>RAISE USING</> or <literal>RAISE
-    <replaceable class="parameter">level</replaceable> USING</> and put
-    everything else into the <literal>USING</> list.
-   </para>
-
-   <para>
-    The last variant of <command>RAISE</> has no parameters at all.
-    This form can only be used inside a <literal>BEGIN</> block's
-    <literal>EXCEPTION</> clause;
-    it causes the error currently being handled to be re-thrown.
-   </para>
-
-   <note>
-    <para>
-     Before <productname>PostgreSQL</> 9.1, <command>RAISE</> without
-     parameters was interpreted as re-throwing the error from the block
-     containing the active exception handler.  Thus an <literal>EXCEPTION</>
-     clause nested within that handler could not catch it, even if the
-     <command>RAISE</> was within the nested <literal>EXCEPTION</> clause's
-     block. This was deemed surprising as well as being incompatible with
-     Oracle's PL/SQL.
-    </para>
-   </note>
-
-   <para>
-    If no condition name nor SQLSTATE is specified in a
-    <command>RAISE EXCEPTION</command> command, the default is to use
-    <literal>RAISE_EXCEPTION</> (<literal>P0001</>).  If no message
-    text is specified, the default is to use the condition name or
-    SQLSTATE as message text.
-   </para>
-
-   <note>
-    <para>
-     When specifying an error code by SQLSTATE code, you are not
-     limited to the predefined error codes, but can select any
-     error code consisting of five digits and/or upper-case ASCII
-     letters, other than <literal>00000</>.  It is recommended that
-     you avoid throwing error codes that end in three zeroes, because
-     these are category codes and can only be trapped by trapping
-     the whole category.
-    </para>
-   </note>
-
- </sect1>
-
- <sect1 id="plpgsql-trigger">
-  <title>Trigger Procedures</title>
-
-  <indexterm zone="plpgsql-trigger">
-   <primary>trigger</primary>
-   <secondary>in PL/pgSQL</secondary>
-  </indexterm>
-
-&common;
-  <para>
-    <application>PL/pgSQL</application> can be used to define trigger
-    procedures. A trigger procedure is created with the
-    <command>CREATE FUNCTION</> command, declaring it as a function with
-    no arguments and a return type of <type>trigger</type>.  Note that
-    the function must be declared with no arguments even if it expects
-    to receive arguments specified in <command>CREATE TRIGGER</> &mdash;
-    trigger arguments are passed via <varname>TG_ARGV</>, as described
-    below.
-  </para>
-
-  <para>
-   When a <application>PL/pgSQL</application> function is called as a
-   trigger, several special variables are created automatically in the
-   top-level block. They are:
-
-   <variablelist>
-    <varlistentry>
-     <term><varname>NEW</varname></term>
-     <listitem>
-      <para>
-       Data type <type>RECORD</type>; variable holding the new
-       database row for <command>INSERT</>/<command>UPDATE</> operations in row-level
-       triggers. This variable is <symbol>NULL</symbol> in statement-level triggers
-       and for <command>DELETE</command> operations.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>OLD</varname></term>
-     <listitem>
-      <para>
-       Data type <type>RECORD</type>; variable holding the old
-       database row for <command>UPDATE</>/<command>DELETE</> operations in row-level
-       triggers. This variable is <symbol>NULL</symbol> in statement-level triggers
-       and for <command>INSERT</command> operations.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>TG_NAME</varname></term>
-     <listitem>
-      <para>
-       Data type <type>name</type>; variable that contains the name of the trigger actually
-       fired.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>TG_WHEN</varname></term>
-     <listitem>
-      <para>
-       Data type <type>text</type>; a string of
-       <literal>BEFORE</literal>, <literal>AFTER</literal>, or
-       <literal>INSTEAD OF</literal>, depending on the trigger's definition.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>TG_LEVEL</varname></term>
-     <listitem>
-      <para>
-       Data type <type>text</type>; a string of either
-       <literal>ROW</literal> or <literal>STATEMENT</literal>
-       depending on the trigger's definition.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>TG_OP</varname></term>
-     <listitem>
-      <para>
-       Data type <type>text</type>; a string of
-       <literal>INSERT</literal>, <literal>UPDATE</literal>,
-       <literal>DELETE</literal>, or <literal>TRUNCATE</>
-       telling for which operation the trigger was fired.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>TG_RELID</varname></term>
-     <listitem>
-      <para>
-       Data type <type>oid</type>; the object ID of the table that caused the
-       trigger invocation.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>TG_RELNAME</varname></term>
-     <listitem>
-      <para>
-       Data type <type>name</type>; the name of the table that caused the trigger
-       invocation. This is now deprecated, and could disappear in a future
-       release. Use <literal>TG_TABLE_NAME</> instead.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>TG_TABLE_NAME</varname></term>
-     <listitem>
-      <para>
-       Data type <type>name</type>; the name of the table that
-       caused the trigger invocation.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>TG_TABLE_SCHEMA</varname></term>
-     <listitem>
-      <para>
-       Data type <type>name</type>; the name of the schema of the
-       table that caused the trigger invocation.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>TG_NARGS</varname></term>
-     <listitem>
-      <para>
-       Data type <type>integer</type>; the number of arguments given to the trigger
-       procedure in the <command>CREATE TRIGGER</command> statement.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>TG_ARGV[]</varname></term>
-     <listitem>
-      <para>
-       Data type array of <type>text</type>; the arguments from
-       the <command>CREATE TRIGGER</command> statement.
-       The index counts from 0. Invalid
-       indexes (less than 0 or greater than or equal to <varname>tg_nargs</>)
-       result in a null value.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-   <para>
-    A trigger function must return either <symbol>NULL</symbol> or a
-    record/row value having exactly the structure of the table the
-    trigger was fired for.
-   </para>
-
-   <para>
-    Row-level triggers fired <literal>BEFORE</> can return null to signal the
-    trigger manager to skip the rest of the operation for this row
-    (i.e., subsequent triggers are not fired, and the
-    <command>INSERT</>/<command>UPDATE</>/<command>DELETE</> does not occur
-    for this row).  If a nonnull
-    value is returned then the operation proceeds with that row value.
-    Returning a row value different from the original value
-    of <varname>NEW</> alters the row that will be inserted or
-    updated.  Thus, if the trigger function wants the triggering
-    action to succeed normally without altering the row
-    value, <varname>NEW</varname> (or a value equal thereto) has to be
-    returned.  To alter the row to be stored, it is possible to
-    replace single values directly in <varname>NEW</> and return the
-    modified <varname>NEW</>, or to build a complete new record/row to
-    return.  In the case of a before-trigger
-    on <command>DELETE</command>, the returned value has no direct
-    effect, but it has to be nonnull to allow the trigger action to
-    proceed.  Note that <varname>NEW</varname> is null
-    in <command>DELETE</command> triggers, so returning that is
-    usually not sensible.  The usual idiom in <command>DELETE</command>
-    triggers is to return <varname>OLD</varname>.
-   </para>
-
-   <para>
-    <literal>INSTEAD OF</> triggers (which are always row-level triggers,
-    and may only be used on views) can return null to signal that they did
-    not perform any updates, and that the rest of the operation for this
-    row should be skipped (i.e., subsequent triggers are not fired, and the
-    row is not counted in the rows-affected status for the surrounding
-    <command>INSERT</>/<command>UPDATE</>/<command>DELETE</>).
-    Otherwise a nonnull value should be returned, to signal
-    that the trigger performed the requested operation. For
-    <command>INSERT</> and <command>UPDATE</> operations, the return value
-    should be <varname>NEW</>, which the trigger function may modify to
-    support <command>INSERT RETURNING</> and <command>UPDATE RETURNING</>
-    (this will also affect the row value passed to any subsequent triggers).
-    For <command>DELETE</> operations, the return value should be
-    <varname>OLD</>.
-   </para>
-
-   <para>
-    The return value of a row-level trigger
-    fired <literal>AFTER</literal> or a statement-level trigger
-    fired <literal>BEFORE</> or <literal>AFTER</> is
-    always ignored; it might as well be null. However, any of these types of
-    triggers might still abort the entire operation by raising an error.
-   </para>
-
-   <para>
-    <xref linkend="plpgsql-trigger-example"> shows an example of a
-    trigger procedure in <application>PL/pgSQL</application>.
-   </para>
-
-   <example id="plpgsql-trigger-example">
-    <title>A <application>PL/pgSQL</application> Trigger Procedure</title>
-
-    <para>
-     This example trigger ensures that any time a row is inserted or updated
-     in the table, the current user name and time are stamped into the
-     row. And it checks that an employee's name is given and that the
-     salary is a positive value.
-    </para>
-
-<programlisting>
-CREATE TABLE emp (
-    empname text,
-    salary integer,
-    last_date timestamp,
-    last_user text
-);
-
-CREATE FUNCTION emp_stamp() RETURNS trigger AS $emp_stamp$
-    BEGIN
-        -- Check that empname and salary are given
-        IF NEW.empname IS NULL THEN
-            RAISE EXCEPTION 'empname cannot be null';
-        END IF;
-        IF NEW.salary IS NULL THEN
-            RAISE EXCEPTION '% cannot have null salary', NEW.empname;
-        END IF;
-
-        -- Who works for us when she must pay for it?
-        IF NEW.salary &lt; 0 THEN
-            RAISE EXCEPTION '% cannot have a negative salary', NEW.empname;
-        END IF;
-
-        -- Remember who changed the payroll when
-        NEW.last_date := current_timestamp;
-        NEW.last_user := current_user;
-        RETURN NEW;
-    END;
-$emp_stamp$ LANGUAGE plpgsql;
-
-CREATE TRIGGER emp_stamp BEFORE INSERT OR UPDATE ON emp
-    FOR EACH ROW EXECUTE PROCEDURE emp_stamp();
-</programlisting>
-   </example>
-
-   <para>
-    Another way to log changes to a table involves creating a new table that
-    holds a row for each insert, update, or delete that occurs. This approach
-    can be thought of as auditing changes to a table.
-    <xref linkend="plpgsql-trigger-audit-example"> shows an example of an
-    audit trigger procedure in <application>PL/pgSQL</application>.
-   </para>
-
-   <example id="plpgsql-trigger-audit-example">
-    <title>A <application>PL/pgSQL</application> Trigger Procedure For Auditing</title>
-
-    <para>
-     This example trigger ensures that any insert, update or delete of a row
-     in the <literal>emp</literal> table is recorded (i.e., audited) in the <literal>emp_audit</literal> table.
-     The current time and user name are stamped into the row, together with
-     the type of operation performed on it.
-    </para>
-
-<programlisting>
-CREATE TABLE emp (
-    empname           text NOT NULL,
-    salary            integer
-);
-
-CREATE TABLE emp_audit(
-    operation         char(1)   NOT NULL,
-    stamp             timestamp NOT NULL,
-    userid            text      NOT NULL,
-    empname           text      NOT NULL,
-    salary integer
-);
-
-CREATE OR REPLACE FUNCTION process_emp_audit() RETURNS TRIGGER AS $emp_audit$
-    BEGIN
-        --
-        -- Create a row in emp_audit to reflect the operation performed on emp,
-        -- make use of the special variable TG_OP to work out the operation.
-        --
-        IF (TG_OP = 'DELETE') THEN
-            INSERT INTO emp_audit SELECT 'D', now(), user, OLD.*;
-            RETURN OLD;
-        ELSIF (TG_OP = 'UPDATE') THEN
-            INSERT INTO emp_audit SELECT 'U', now(), user, NEW.*;
-            RETURN NEW;
-        ELSIF (TG_OP = 'INSERT') THEN
-            INSERT INTO emp_audit SELECT 'I', now(), user, NEW.*;
-            RETURN NEW;
-        END IF;
-        RETURN NULL; -- result is ignored since this is an AFTER trigger
-    END;
-$emp_audit$ LANGUAGE plpgsql;
-
-CREATE TRIGGER emp_audit
-AFTER INSERT OR UPDATE OR DELETE ON emp
-    FOR EACH ROW EXECUTE PROCEDURE process_emp_audit();
-</programlisting>
-   </example>
-
-   <para>
-    A variation of the previous example uses a view joining the main table
-    to the audit table, to show when each entry was last modified. This
-    approach still records the full audit trail of changes to the table,
-    but also presents a simplified view of the audit trail, showing just
-    the last modified timestamp derived from the audit trail for each entry.
-    <xref linkend="plpgsql-view-trigger-audit-example"> shows an example
-    of an audit trigger on a view in <application>PL/pgSQL</application>.
-   </para>
-
-   <example id="plpgsql-view-trigger-audit-example">
-    <title>A <application>PL/pgSQL</application> View Trigger Procedure For Auditing</title>
-
-    <para>
-     This example uses a trigger on the view to make it updatable, and
-     ensure that any insert, update or delete of a row in the view is
-     recorded (i.e., audited) in the <literal>emp_audit</literal> table. The current time
-     and user name are recorded, together with the type of operation
-     performed, and the view displays the last modified time of each row.
-    </para>
-
-<programlisting>
-CREATE TABLE emp (
-    empname           text PRIMARY KEY,
-    salary            integer
-);
-
-CREATE TABLE emp_audit(
-    operation         char(1)   NOT NULL,
-    userid            text      NOT NULL,
-    empname           text      NOT NULL,
-    salary            integer,
-    stamp             timestamp NOT NULL
-);
-
-CREATE VIEW emp_view AS
-    SELECT e.empname,
-           e.salary,
-           max(ea.stamp) AS last_updated
-      FROM emp e
-      LEFT JOIN emp_audit ea ON ea.empname = e.empname
-     GROUP BY 1, 2;
-
-CREATE OR REPLACE FUNCTION update_emp_view() RETURNS TRIGGER AS $$
-    BEGIN
-        --
-        -- Perform the required operation on emp, and create a row in emp_audit
-        -- to reflect the change made to emp.
-        --
-        IF (TG_OP = 'DELETE') THEN
-            DELETE FROM emp WHERE empname = OLD.empname;
-            IF NOT FOUND THEN RETURN NULL; END IF;
-
-            OLD.last_updated = now();
-            INSERT INTO emp_audit VALUES('D', user, OLD.*);
-            RETURN OLD;
-        ELSIF (TG_OP = 'UPDATE') THEN
-            UPDATE emp SET salary = NEW.salary WHERE empname = OLD.empname;
-            IF NOT FOUND THEN RETURN NULL; END IF;
-
-            NEW.last_updated = now();
-            INSERT INTO emp_audit VALUES('U', user, NEW.*);
-            RETURN NEW;
-        ELSIF (TG_OP = 'INSERT') THEN
-            INSERT INTO emp VALUES(NEW.empname, NEW.salary);
-
-            NEW.last_updated = now();
-            INSERT INTO emp_audit VALUES('I', user, NEW.*);
-            RETURN NEW;
-        END IF;
-    END;
-$$ LANGUAGE plpgsql;
-
-CREATE TRIGGER emp_audit
-INSTEAD OF INSERT OR UPDATE OR DELETE ON emp_view
-    FOR EACH ROW EXECUTE PROCEDURE update_emp_view();
-</programlisting>
-   </example>
-
-   <para>
-    One use of triggers is to maintain a summary table
-    of another table. The resulting summary can be used in place of the
-    original table for certain queries &mdash; often with vastly reduced run
-    times.
-    This technique is commonly used in Data Warehousing, where the tables
-    of measured or observed data (called fact tables) might be extremely large.
-    <xref linkend="plpgsql-trigger-summary-example"> shows an example of a
-    trigger procedure in <application>PL/pgSQL</application> that maintains
-    a summary table for a fact table in a data warehouse.
-   </para>
-
-
-   <example id="plpgsql-trigger-summary-example">
-    <title>A <application>PL/pgSQL</application> Trigger Procedure For Maintaining A Summary Table</title>
-
-    <para>
-     The schema detailed here is partly based on the <emphasis>Grocery Store
-     </emphasis> example from <emphasis>The Data Warehouse Toolkit</emphasis>
-     by Ralph Kimball.
-    </para>
-
-<programlisting>
---
--- Main tables - time dimension and sales fact.
---
-CREATE TABLE time_dimension (
-    time_key                    integer NOT NULL,
-    day_of_week                 integer NOT NULL,
-    day_of_month                integer NOT NULL,
-    month                       integer NOT NULL,
-    quarter                     integer NOT NULL,
-    year                        integer NOT NULL
-);
-CREATE UNIQUE INDEX time_dimension_key ON time_dimension(time_key);
-
-CREATE TABLE sales_fact (
-    time_key                    integer NOT NULL,
-    product_key                 integer NOT NULL,
-    store_key                   integer NOT NULL,
-    amount_sold                 numeric(12,2) NOT NULL,
-    units_sold                  integer NOT NULL,
-    amount_cost                 numeric(12,2) NOT NULL
-);
-CREATE INDEX sales_fact_time ON sales_fact(time_key);
-
---
--- Summary table - sales by time.
---
-CREATE TABLE sales_summary_bytime (
-    time_key                    integer NOT NULL,
-    amount_sold                 numeric(15,2) NOT NULL,
-    units_sold                  numeric(12) NOT NULL,
-    amount_cost                 numeric(15,2) NOT NULL
-);
-CREATE UNIQUE INDEX sales_summary_bytime_key ON sales_summary_bytime(time_key);
-
---
--- Function and trigger to amend summarized column(s) on UPDATE, INSERT, DELETE.
---
-CREATE OR REPLACE FUNCTION maint_sales_summary_bytime() RETURNS TRIGGER
-AS $maint_sales_summary_bytime$
-    DECLARE
-        delta_time_key          integer;
-        delta_amount_sold       numeric(15,2);
-        delta_units_sold        numeric(12);
-        delta_amount_cost       numeric(15,2);
-    BEGIN
-
-        -- Work out the increment/decrement amount(s).
-        IF (TG_OP = 'DELETE') THEN
-
-            delta_time_key = OLD.time_key;
-            delta_amount_sold = -1 * OLD.amount_sold;
-            delta_units_sold = -1 * OLD.units_sold;
-            delta_amount_cost = -1 * OLD.amount_cost;
-
-        ELSIF (TG_OP = 'UPDATE') THEN
-
-            -- forbid updates that change the time_key -
-            -- (probably not too onerous, as DELETE + INSERT is how most
-            -- changes will be made).
-            IF ( OLD.time_key != NEW.time_key) THEN
-                RAISE EXCEPTION 'Update of time_key : % -&gt; % not allowed',
-                                                      OLD.time_key, NEW.time_key;
-            END IF;
-
-            delta_time_key = OLD.time_key;
-            delta_amount_sold = NEW.amount_sold - OLD.amount_sold;
-            delta_units_sold = NEW.units_sold - OLD.units_sold;
-            delta_amount_cost = NEW.amount_cost - OLD.amount_cost;
-
-        ELSIF (TG_OP = 'INSERT') THEN
-
-            delta_time_key = NEW.time_key;
-            delta_amount_sold = NEW.amount_sold;
-            delta_units_sold = NEW.units_sold;
-            delta_amount_cost = NEW.amount_cost;
-
-        END IF;
-
-
-        -- Insert or update the summary row with the new values.
-        &lt;&lt;insert_update&gt;&gt;
-        LOOP
-            UPDATE sales_summary_bytime
-                SET amount_sold = amount_sold + delta_amount_sold,
-                    units_sold = units_sold + delta_units_sold,
-                    amount_cost = amount_cost + delta_amount_cost
-                WHERE time_key = delta_time_key;
-
-            EXIT insert_update WHEN found;
-
-            BEGIN
-                INSERT INTO sales_summary_bytime (
-                            time_key,
-                            amount_sold,
-                            units_sold,
-                            amount_cost)
-                    VALUES (
-                            delta_time_key,
-                            delta_amount_sold,
-                            delta_units_sold,
-                            delta_amount_cost
-                           );
-
-                EXIT insert_update;
-
-            EXCEPTION
-                WHEN UNIQUE_VIOLATION THEN
-                    -- do nothing
-            END;
-        END LOOP insert_update;
-
-        RETURN NULL;
-
-    END;
-$maint_sales_summary_bytime$ LANGUAGE plpgsql;
-
-CREATE TRIGGER maint_sales_summary_bytime
-AFTER INSERT OR UPDATE OR DELETE ON sales_fact
-    FOR EACH ROW EXECUTE PROCEDURE maint_sales_summary_bytime();
-
-INSERT INTO sales_fact VALUES(1,1,1,10,3,15);
-INSERT INTO sales_fact VALUES(1,2,1,20,5,35);
-INSERT INTO sales_fact VALUES(2,2,1,40,15,135);
-INSERT INTO sales_fact VALUES(2,3,1,10,1,13);
-SELECT * FROM sales_summary_bytime;
-DELETE FROM sales_fact WHERE product_key = 1;
-SELECT * FROM sales_summary_bytime;
-UPDATE sales_fact SET units_sold = units_sold * 2;
-SELECT * FROM sales_summary_bytime;
-</programlisting>
-   </example>
-
-  </sect1>
-
-  <sect1 id="plpgsql-implementation">
-   <title><application>PL/pgSQL</> Under the Hood</title>
-
-&common;
-   <para>
-    This section discusses some implementation details that are
-    frequently important for <application>PL/pgSQL</> users to know.
-   </para>
-
-  <sect2 id="plpgsql-var-subst">
-   <title>Variable Substitution</title>
-
-&common;
-   <para>
-    SQL statements and expressions within a <application>PL/pgSQL</> function
-    can refer to variables and parameters of the function.  Behind the scenes,
-    <application>PL/pgSQL</> substitutes query parameters for such references.
-    Parameters will only be substituted in places where a parameter or
-    column reference is syntactically allowed.  As an extreme case, consider
-    this example of poor programming style:
-<programlisting>
-INSERT INTO foo (foo) VALUES (foo);
-</programlisting>
-    The first occurrence of <literal>foo</> must syntactically be a table
-    name, so it will not be substituted, even if the function has a variable
-    named <literal>foo</>.  The second occurrence must be the name of a
-    column of the table, so it will not be substituted either.  Only the
-    third occurrence is a candidate to be a reference to the function's
-    variable.
-   </para>
-
-   <note>
-    <para>
-     <productname>PostgreSQL</productname> versions before 9.0 would try
-     to substitute the variable in all three cases, leading to syntax errors.
-    </para>
-   </note>
-
-   <para>
-    Since the names of variables are syntactically no different from the names
-    of table columns, there can be ambiguity in statements that also refer to
-    tables: is a given name meant to refer to a table column, or a variable?
-    Let's change the previous example to
-<programlisting>
-INSERT INTO dest (col) SELECT foo + bar FROM src;
-</programlisting>
-    Here, <literal>dest</> and <literal>src</> must be table names, and
-    <literal>col</> must be a column of <literal>dest</>, but <literal>foo</>
-    and <literal>bar</> might reasonably be either variables of the function
-    or columns of <literal>src</>.
-   </para>
-
-   <para>
-    By default, <application>PL/pgSQL</> will report an error if a name
-    in a SQL statement could refer to either a variable or a table column.
-    You can fix such a problem by renaming the variable or column,
-    or by qualifying the ambiguous reference, or by telling
-    <application>PL/pgSQL</> which interpretation to prefer.
-   </para>
-
-   <para>
-    The simplest solution is to rename the variable or column.
-    A common coding rule is to use a
-    different naming convention for <application>PL/pgSQL</application>
-    variables than you use for column names.  For example,
-    if you consistently name function variables
-    <literal>v_<replaceable>something</></literal> while none of your
-    column names start with <literal>v_</>, no conflicts will occur.
-   </para>
-
-   <para>
-    Alternatively you can qualify ambiguous references to make them clear.
-    In the above example, <literal>src.foo</> would be an unambiguous reference
-    to the table column.  To create an unambiguous reference to a variable,
-    declare it in a labeled block and use the block's label
-    (see <xref linkend="plpgsql-structure">).  For example,
-<programlisting>
-&lt;&lt;block&gt;&gt;
-DECLARE
-    foo int;
-BEGIN
-    foo := ...;
-    INSERT INTO dest (col) SELECT block.foo + bar FROM src;
-</programlisting>
-    Here <literal>block.foo</> means the variable even if there is a column
-    <literal>foo</> in <literal>src</>.  Function parameters, as well as
-    special variables such as <literal>FOUND</>, can be qualified by the
-    function's name, because they are implicitly declared in an outer block
-    labeled with the function's name.
-   </para>
-
-   <para>
-    Sometimes it is impractical to fix all the ambiguous references in a
-    large body of <application>PL/pgSQL</> code.  In such cases you can
-    specify that <application>PL/pgSQL</> should resolve ambiguous references
-    as the variable (which is compatible with <application>PL/pgSQL</>'s
-    behavior before <productname>PostgreSQL</productname> 9.0), or as the
-    table column (which is compatible with some other systems such as
-    <productname>Oracle</productname>).
-   </para>
-
-   <indexterm>
-     <primary><varname>plpgsql.variable_conflict</> configuration parameter</primary>
-   </indexterm>
-
-   <para>
-    To change this behavior on a system-wide basis, set the configuration
-    parameter <literal>plpgsql.variable_conflict</> to one of
-    <literal>error</>, <literal>use_variable</>, or
-    <literal>use_column</> (where <literal>error</> is the factory default).
-    This parameter affects subsequent compilations
-    of statements in <application>PL/pgSQL</> functions, but not statements
-    already compiled in the current session.  To set the parameter before
-    <application>PL/pgSQL</> has been loaded, it is necessary to have added
-    <quote><literal>plpgsql</></> to the <xref
-    linkend="guc-custom-variable-classes"> list in
-    <filename>postgresql.conf</filename>.  Because changing this setting
-    can cause unexpected changes in the behavior of <application>PL/pgSQL</>
-    functions, it can only be changed by a superuser.
-   </para>
-
-   <para>
-    You can also set the behavior on a function-by-function basis, by
-    inserting one of these special commands at the start of the function
-    text:
-<programlisting>
-#variable_conflict error
-#variable_conflict use_variable
-#variable_conflict use_column
-</programlisting>
-    These commands affect only the function they are written in, and override
-    the setting of <literal>plpgsql.variable_conflict</>.  An example is
-<programlisting>
-CREATE FUNCTION stamp_user(id int, comment text) RETURNS void AS $$
-    #variable_conflict use_variable
-    DECLARE
-        curtime timestamp := now();
-    BEGIN
-        UPDATE users SET last_modified = curtime, comment = comment
-          WHERE users.id = id;
-    END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-    In the <literal>UPDATE</> command, <literal>curtime</>, <literal>comment</>,
-    and <literal>id</> will refer to the function's variable and parameters
-    whether or not <literal>users</> has columns of those names.  Notice
-    that we had to qualify the reference to <literal>users.id</> in the
-    <literal>WHERE</> clause to make it refer to the table column.
-    But we did not have to qualify the reference to <literal>comment</>
-    as a target in the <literal>UPDATE</> list, because syntactically
-    that must be a column of <literal>users</>.  We could write the same
-    function without depending on the <literal>variable_conflict</> setting
-    in this way:
-<programlisting>
-CREATE FUNCTION stamp_user(id int, comment text) RETURNS void AS $$
-    &lt;&lt;fn&gt;&gt;
-    DECLARE
-        curtime timestamp := now();
-    BEGIN
-        UPDATE users SET last_modified = fn.curtime, comment = stamp_user.comment
-          WHERE users.id = stamp_user.id;
-    END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-   </para>
-
-   <para>
-    Variable substitution does not happen in the command string given
-    to <command>EXECUTE</> or one of its variants.  If you need to
-    insert a varying value into such a command, do so as part of
-    constructing the string value, or use <literal>USING</>, as illustrated in
-    <xref linkend="plpgsql-statements-executing-dyn">.
-   </para>
-
-   <para>
-    Variable substitution currently works only in <command>SELECT</>,
-    <command>INSERT</>, <command>UPDATE</>, and <command>DELETE</> commands,
-    because the main SQL engine allows query parameters only in these
-    commands.  To use a non-constant name or value in other statement
-    types (generically called utility statements), you must construct
-    the utility statement as a string and <command>EXECUTE</> it.
-   </para>
-
-  </sect2>
-
-  <sect2 id="plpgsql-plan-caching">
-   <title>Plan Caching</title>
-
-&common;
-   <para>
-    The <application>PL/pgSQL</> interpreter parses the function's source
-    text and produces an internal binary instruction tree the first time the
-    function is called (within each session).  The instruction tree
-    fully translates the
-    <application>PL/pgSQL</> statement structure, but individual
-    <acronym>SQL</acronym> expressions and <acronym>SQL</acronym> commands
-    used in the function are not translated immediately.
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>preparing a query</>
-     <secondary>in PL/pgSQL</>
-    </indexterm>
-    As each expression and <acronym>SQL</acronym> command is first
-    executed in the function, the <application>PL/pgSQL</> interpreter
-    creates a prepared execution plan (using the
-    <acronym>SPI</acronym> manager's <function>SPI_prepare</function>
-    and <function>SPI_saveplan</function> functions).
-    Subsequent visits to that expression or command
-    reuse the prepared plan.  Thus, a function with conditional code
-    that contains many statements for which execution plans might be
-    required will only prepare and save those plans that are really
-    used during the lifetime of the database connection.  This can
-    substantially reduce the total amount of time required to parse
-    and generate execution plans for the statements in a
-    <application>PL/pgSQL</> function. A disadvantage is that errors
-    in a specific expression or command cannot be detected until that
-    part of the function is reached in execution.  (Trivial syntax
-    errors will be detected during the initial parsing pass, but
-    anything deeper will not be detected until execution.)
-   </para>
-
-   <para>
-    A saved plan will be re-planned automatically if there is any schema
-    change to any table used in the query, or if any user-defined function
-    used in the query is redefined.  This makes the re-use of prepared plans
-    transparent in most cases, but there are corner cases where a stale plan
-    might be re-used.  An example is that dropping and re-creating a
-    user-defined operator won't affect already-cached plans; they'll continue
-    to call the original operator's underlying function, if that has not been
-    changed.  When necessary, the cache can be flushed by starting a fresh
-    database session.
-   </para>
-
-   <para>
-    Because <application>PL/pgSQL</application> saves execution plans
-    in this way, SQL commands that appear directly in a
-    <application>PL/pgSQL</application> function must refer to the
-    same tables and columns on every execution; that is, you cannot use
-    a parameter as the name of a table or column in an SQL command.  To get
-    around this restriction, you can construct dynamic commands using
-    the <application>PL/pgSQL</application> <command>EXECUTE</command>
-    statement &mdash; at the price of constructing a new execution plan on
-    every execution.
-   </para>
-
-   <para>
-    Another important point is that the prepared plans are parameterized
-    to allow the values of <application>PL/pgSQL</application> variables
-    to change from one use to the next, as discussed in detail above.
-    Sometimes this means that a plan is less efficient than it would be
-    if generated for a specific variable value.  As an example, consider
-<programlisting>
-SELECT * INTO myrec FROM dictionary WHERE word LIKE search_term;
-</programlisting>
-    where <literal>search_term</> is a <application>PL/pgSQL</application>
-    variable.  The cached plan for this query will never use an index on
-    <structfield>word</>, since the planner cannot assume that the
-    <literal>LIKE</> pattern will be left-anchored at run time.  To use
-    an index the query must be planned with a specific constant
-    <literal>LIKE</> pattern provided.  This is another situation where
-    <command>EXECUTE</command> can be used to force a new plan to be
-    generated for each execution.
-   </para>
-
-    <para>
-     The mutable nature of record variables presents another problem in this
-     connection.  When fields of a record variable are used in
-     expressions or statements, the data types of the fields must not
-     change from one call of the function to the next, since each
-     expression will be planned using the data type that is present
-     when the expression is first reached.  <command>EXECUTE</command> can be
-     used to get around this problem when necessary.
-    </para>
-
-    <para>
-     If the same function is used as a trigger for more than one table,
-     <application>PL/pgSQL</application> prepares and caches plans
-     independently for each such table &mdash; that is, there is a cache
-     for each trigger function and table combination, not just for each
-     function.  This alleviates some of the problems with varying
-     data types; for instance, a trigger function will be able to work
-     successfully with a column named <literal>key</> even if it happens
-     to have different types in different tables.
-    </para>
-
-    <para>
-     Likewise, functions having polymorphic argument types have a separate
-     plan cache for each combination of actual argument types they have been
-     invoked for, so that data type differences do not cause unexpected
-     failures.
-    </para>
-
-   <para>
-    Plan caching can sometimes have surprising effects on the interpretation
-    of time-sensitive values.  For example there
-    is a difference between what these two functions do:
-
-<programlisting>
-CREATE FUNCTION logfunc1(logtxt text) RETURNS void AS $$
-    BEGIN
-        INSERT INTO logtable VALUES (logtxt, 'now');
-    END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-
-     and:
-
-<programlisting>
-CREATE FUNCTION logfunc2(logtxt text) RETURNS void AS $$
-    DECLARE
-        curtime timestamp;
-    BEGIN
-        curtime := 'now';
-        INSERT INTO logtable VALUES (logtxt, curtime);
-    END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-    </para>
-
-    <para>
-     In the case of <function>logfunc1</function>, the
-<!## PG>
-     <productname>PostgreSQL</productname> main parser knows when
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> main parser knows when
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> main parser knows when
-<!## end>
-     preparing the plan for the <command>INSERT</command> that the
-     string <literal>'now'</literal> should be interpreted as
-     <type>timestamp</type>, because the target column of
-     <classname>logtable</classname> is of that type. Thus,
-     <literal>'now'</literal> will be converted to a constant when the
-     <command>INSERT</command> is planned, and then used in all
-     invocations of <function>logfunc1</function> during the lifetime
-     of the session. Needless to say, this isn't what the programmer
-     wanted.
-    </para>
-
-    <para>
-     In the case of <function>logfunc2</function>, the
-<!## PG>
-     <productname>PostgreSQL</productname> main parser does not know
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> main parser does not know
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> main parser does not know
-<!## end>
-     what type <literal>'now'</literal> should become and therefore
-     it returns a data value of type <type>text</type> containing the string
-     <literal>now</literal>. During the ensuing assignment
-     to the local variable <varname>curtime</varname>, the
-     <application>PL/pgSQL</application> interpreter casts this
-     string to the <type>timestamp</type> type by calling the
-     <function>text_out</function> and <function>timestamp_in</function>
-     functions for the conversion.  So, the computed time stamp is updated
-     on each execution as the programmer expects.
-    </para>
-
-  </sect2>
-
-  </sect1>
-
- <sect1 id="plpgsql-development-tips">
-  <title>Tips for Developing in <application>PL/pgSQL</application></title>
-
-&common;
-   <para>
-    One good way to develop in
-    <application>PL/pgSQL</> is to use the text editor of your
-    choice to create your functions, and in another window, use
-    <application>psql</application> to load and test those functions.
-    If you are doing it this way, it
-    is a good idea to write the function using <command>CREATE OR
-    REPLACE FUNCTION</>. That way you can just reload the file to update
-    the function definition.  For example:
-<programlisting>
-CREATE OR REPLACE FUNCTION testfunc(integer) RETURNS integer AS $$
-          ....
-$$ LANGUAGE plpgsql;
-</programlisting>
-   </para>
-
-   <para>
-    While running <application>psql</application>, you can load or reload such
-    a function definition file with:
-<programlisting>
-\i filename.sql
-</programlisting>
-    and then immediately issue SQL commands to test the function.
-   </para>
-
-   <para>
-    Another good way to develop in <application>PL/pgSQL</> is with a
-    GUI database access tool that facilitates development in a
-    procedural language. One example of such a tool is
-    <application>pgAdmin</>, although others exist. These tools often
-    provide convenient features such as escaping single quotes and
-    making it easier to recreate and debug functions.
-   </para>
-
-  <sect2 id="plpgsql-quote-tips">
-   <title>Handling of Quotation Marks</title>
-
-&common;
-   <para>
-    The code of a <application>PL/pgSQL</> function is specified in
-    <command>CREATE FUNCTION</command> as a string literal.  If you
-    write the string literal in the ordinary way with surrounding
-    single quotes, then any single quotes inside the function body
-    must be doubled; likewise any backslashes must be doubled (assuming
-    escape string syntax is used).
-    Doubling quotes is at best tedious, and in more complicated cases
-    the code can become downright incomprehensible, because you can
-    easily find yourself needing half a dozen or more adjacent quote marks.
-    It's recommended that you instead write the function body as a
-    <quote>dollar-quoted</> string literal (see <xref
-    linkend="sql-syntax-dollar-quoting">).  In the dollar-quoting
-    approach, you never double any quote marks, but instead take care to
-    choose a different dollar-quoting delimiter for each level of
-    nesting you need.  For example, you might write the <command>CREATE
-    FUNCTION</command> command as:
-<programlisting>
-CREATE OR REPLACE FUNCTION testfunc(integer) RETURNS integer AS $PROC$
-          ....
-$PROC$ LANGUAGE plpgsql;
-</programlisting>
-    Within this, you might use quote marks for simple literal strings in
-    SQL commands and <literal>$$</> to delimit fragments of SQL commands
-    that you are assembling as strings.  If you need to quote text that
-    includes <literal>$$</>, you could use <literal>$Q$</>, and so on.
-   </para>
-
-   <para>
-    The following chart shows what you have to do when writing quote
-    marks without dollar quoting.  It might be useful when translating
-    pre-dollar quoting code into something more comprehensible.
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term>1 quotation mark</term>
-    <listitem>
-     <para>
-      To begin and end the function body, for example:
-<programlisting>
-CREATE FUNCTION foo() RETURNS integer AS '
-          ....
-' LANGUAGE plpgsql;
-</programlisting>
-      Anywhere within a single-quoted function body, quote marks
-      <emphasis>must</> appear in pairs.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>2 quotation marks</term>
-    <listitem>
-     <para>
-      For string literals inside the function body, for example:
-<programlisting>
-a_output := ''Blah'';
-SELECT * FROM users WHERE f_name=''foobar'';
-</programlisting>
-      In the dollar-quoting approach, you'd just write:
-<programlisting>
-a_output := 'Blah';
-SELECT * FROM users WHERE f_name='foobar';
-</programlisting>
-      which is exactly what the <application>PL/pgSQL</> parser would see
-      in either case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>4 quotation marks</term>
-    <listitem>
-     <para>
-      When you need a single quotation mark in a string constant inside the
-      function body, for example:
-<programlisting>
-a_output := a_output || '' AND name LIKE ''''foobar'''' AND xyz''
-</programlisting>
-      The value actually appended to <literal>a_output</literal> would be:
-      <literal> AND name LIKE 'foobar' AND xyz</literal>.
-     </para>
-     <para>
-      In the dollar-quoting approach, you'd write:
-<programlisting>
-a_output := a_output || $$ AND name LIKE 'foobar' AND xyz$$
-</programlisting>
-      being careful that any dollar-quote delimiters around this are not
-      just <literal>$$</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>6 quotation marks</term>
-    <listitem>
-     <para>
-      When a single quotation mark in a string inside the function body is
-      adjacent to the end of that string constant, for example:
-<programlisting>
-a_output := a_output || '' AND name LIKE ''''foobar''''''
-</programlisting>
-      The value appended to <literal>a_output</literal> would then be:
-      <literal> AND name LIKE 'foobar'</literal>.
-     </para>
-     <para>
-      In the dollar-quoting approach, this becomes:
-<programlisting>
-a_output := a_output || $$ AND name LIKE 'foobar'$$
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>10 quotation marks</term>
-    <listitem>
-     <para>
-      When you want two single quotation marks in a string constant (which
-      accounts for 8 quotation marks) and this is adjacent to the end of that
-      string constant (2 more).  You will probably only need that if
-      you are writing a function that generates other functions, as in
-      <xref linkend="plpgsql-porting-ex2">.
-      For example:
-<programlisting>
-a_output := a_output || '' if v_'' ||
-    referrer_keys.kind || '' like ''''''''''
-    || referrer_keys.key_string || ''''''''''
-    then return ''''''  || referrer_keys.referrer_type
-    || ''''''; end if;'';
-</programlisting>
-      The value of <literal>a_output</literal> would then be:
-<programlisting>
-if v_... like ''...'' then return ''...''; end if;
-</programlisting>
-     </para>
-     <para>
-      In the dollar-quoting approach, this becomes:
-<programlisting>
-a_output := a_output || $$ if v_$$ || referrer_keys.kind || $$ like '$$
-    || referrer_keys.key_string || $$'
-    then return '$$  || referrer_keys.referrer_type
-    || $$'; end if;$$;
-</programlisting>
-      where we assume we only need to put single quote marks into
-      <literal>a_output</literal>, because it will be re-quoted before use.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  </sect2>
- </sect1>
-
-  <!-- **** Porting from Oracle PL/SQL **** -->
-
- <sect1 id="plpgsql-porting">
-  <title>Porting from <productname>Oracle</productname> PL/SQL</title>
-
-  <indexterm zone="plpgsql-porting">
-   <primary>Oracle</primary>
-   <secondary>porting from PL/SQL to PL/pgSQL</secondary>
-  </indexterm>
-
-  <indexterm zone="plpgsql-porting">
-   <primary>PL/SQL (Oracle)</primary>
-   <secondary>porting to PL/pgSQL</secondary>
-  </indexterm>
-
-&common;
-  <para>
-   This section explains differences between
-<!## PG>
-   <productname>PostgreSQL</>'s <application>PL/pgSQL</application>
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</>'s <application>PL/pgSQL</application>
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</>'s <application>PL/pgSQL</application>
-<!## end>
-   language and Oracle's <application>PL/SQL</application> language,
-   to help developers who port applications from
-<!## PG>
-   <trademark class="registered">Oracle</> to <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-   <trademark class="registered">Oracle</> to <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-   <trademark class="registered">Oracle</> to <productname>Postgres-XL</>.
-<!## end>
-  </para>
-
-  <para>
-   <application>PL/pgSQL</application> is similar to PL/SQL in many
-   aspects. It is a block-structured, imperative language, and all
-   variables have to be declared.  Assignments, loops, conditionals
-   are similar.  The main differences you should keep in mind when
-   porting from <application>PL/SQL</> to
-   <application>PL/pgSQL</application> are:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       If a name used in a SQL command could be either a column name of a
-       table or a reference to a variable of the function,
-       <application>PL/SQL</> treats it as a column name.  This corresponds
-       to <application>PL/pgSQL</>'s
-       <literal>plpgsql.variable_conflict</> = <literal>use_column</>
-       behavior, which is not the default,
-       as explained in <xref linkend="plpgsql-var-subst">.
-       It's often best to avoid such ambiguities in the first place,
-       but if you have to port a large amount of code that depends on
-       this behavior, setting <literal>variable_conflict</> may be the
-       best solution.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-<!## PG>
-       In <productname>PostgreSQL</> the function body must be written as
-<!## end>
-<!## XC>
-       In <productname>Postgres-XC</> the function body must be written as
-<!## end>
-<!## XL>
-       In <productname>Postgres-XL</> the function body must be written as
-<!## end>
-       a string literal.  Therefore you need to use dollar quoting or escape
-       single quotes in the function body. (See <xref
-       linkend="plpgsql-quote-tips">.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Instead of packages, use schemas to organize your functions
-       into groups.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Since there are no packages, there are no package-level variables
-       either. This is somewhat annoying.  You can keep per-session state
-       in temporary tables instead.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Integer <command>FOR</> loops with <literal>REVERSE</> work
-       differently: <application>PL/SQL</> counts down from the second
-       number to the first, while <application>PL/pgSQL</> counts down
-       from the first number to the second, requiring the loop bounds
-       to be swapped when porting.  This incompatibility is unfortunate
-       but is unlikely to be changed. (See <xref
-       linkend="plpgsql-integer-for">.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <command>FOR</> loops over queries (other than cursors) also work
-       differently: the target variable(s) must have been declared,
-       whereas <application>PL/SQL</> always declares them implicitly.
-       An advantage of this is that the variable values are still accessible
-       after the loop exits.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       There are various notational differences for the use of cursor
-       variables.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </para>
-
-  <sect2>
-   <title>Porting Examples</title>
-
-&common;
-   <para>
-    <xref linkend="pgsql-porting-ex1"> shows how to port a simple
-    function from <application>PL/SQL</> to <application>PL/pgSQL</>.
-   </para>
-
-   <example id="pgsql-porting-ex1">
-    <title>Porting a Simple Function from <application>PL/SQL</> to <application>PL/pgSQL</></title>
-
-    <para>
-     Here is an <productname>Oracle</productname> <application>PL/SQL</> function:
-<programlisting>
-CREATE OR REPLACE FUNCTION cs_fmt_browser_version(v_name varchar,
-                                                  v_version varchar)
-RETURN varchar IS
-BEGIN
-    IF v_version IS NULL THEN
-        RETURN v_name;
-    END IF;
-    RETURN v_name || '/' || v_version;
-END;
-/
-show errors;
-</programlisting>
-    </para>
-
-    <para>
-     Let's go through this function and see the differences compared to
-     <application>PL/pgSQL</>:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        The <literal>RETURN</literal> key word in the function
-        prototype (not the function body) becomes
-        <literal>RETURNS</literal> in
-<!## PG>
-        <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname>.
-<!## end>
-        Also, <literal>IS</> becomes <literal>AS</>, and you need to
-        add a <literal>LANGUAGE</> clause because <application>PL/pgSQL</>
-        is not the only possible function language.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-<!## PG>
-        In <productname>PostgreSQL</>, the function body is considered
-<!## end>
-<!## XC>
-        In <productname>Postgres-XC</>, the function body is considered
-<!## end>
-<!## XL>
-        In <productname>Postgres-XL</>, the function body is considered
-<!## end>
-        to be a string literal, so you need to use quote marks or dollar
-        quotes around it.  This substitutes for the terminating <literal>/</>
-        in the Oracle approach.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The <literal>show errors</literal> command does not exist in
-<!## PG>
-        <productname>PostgreSQL</>, and is not needed since errors are
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</>, and is not needed since errors are
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</>, and is not needed since errors are
-<!## end>
-        reported automatically.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     This is how this function would look when ported to
-<!## PG>
-     <productname>PostgreSQL</>:
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</>:
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</>:
-<!## end>
-
-<programlisting>
-CREATE OR REPLACE FUNCTION cs_fmt_browser_version(v_name varchar,
-                                                  v_version varchar)
-RETURNS varchar AS $$
-BEGIN
-    IF v_version IS NULL THEN
-        RETURN v_name;
-    END IF;
-    RETURN v_name || '/' || v_version;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-    </para>
-   </example>
-
-   <para>
-    <xref linkend="plpgsql-porting-ex2"> shows how to port a
-    function that creates another function and how to handle the
-    ensuing quoting problems.
-   </para>
-
-   <example id="plpgsql-porting-ex2">
-    <title>Porting a Function that Creates Another Function from <application>PL/SQL</> to <application>PL/pgSQL</></title>
-
-    <para>
-     The following procedure grabs rows from a
-     <command>SELECT</command> statement and builds a large function
-     with the results in <literal>IF</literal> statements, for the
-     sake of efficiency.
-    </para>
-
-    <para>
-     This is the Oracle version:
-<programlisting>
-CREATE OR REPLACE PROCEDURE cs_update_referrer_type_proc IS
-    CURSOR referrer_keys IS
-        SELECT * FROM cs_referrer_keys
-        ORDER BY try_order;
-    func_cmd VARCHAR(4000);
-BEGIN
-    func_cmd := 'CREATE OR REPLACE FUNCTION cs_find_referrer_type(v_host IN VARCHAR,
-                 v_domain IN VARCHAR, v_url IN VARCHAR) RETURN VARCHAR IS BEGIN';
-
-    FOR referrer_key IN referrer_keys LOOP
-        func_cmd := func_cmd ||
-          ' IF v_' || referrer_key.kind
-          || ' LIKE ''' || referrer_key.key_string
-          || ''' THEN RETURN ''' || referrer_key.referrer_type
-          || '''; END IF;';
-    END LOOP;
-
-    func_cmd := func_cmd || ' RETURN NULL; END;';
-
-    EXECUTE IMMEDIATE func_cmd;
-END;
-/
-show errors;
-</programlisting>
-    </para>
-
-    <para>
-<!## PG>
-     Here is how this function would end up in <productname>PostgreSQL</>:
-<!## end>
-<!## XC>
-     Here is how this function would end up in <productname>Postgres-XC</>:
-<!## end>
-<!## XL>
-     Here is how this function would end up in <productname>Postgres-XL</>:
-<!## end>
-<programlisting>
-CREATE OR REPLACE FUNCTION cs_update_referrer_type_proc() RETURNS void AS $func$
-DECLARE
-    referrer_keys CURSOR IS
-        SELECT * FROM cs_referrer_keys
-        ORDER BY try_order;
-    func_body text;
-    func_cmd text;
-BEGIN
-    func_body := 'BEGIN';
-
-    FOR referrer_key IN referrer_keys LOOP
-        func_body := func_body ||
-          ' IF v_' || referrer_key.kind
-          || ' LIKE ' || quote_literal(referrer_key.key_string)
-          || ' THEN RETURN ' || quote_literal(referrer_key.referrer_type)
-          || '; END IF;' ;
-    END LOOP;
-
-    func_body := func_body || ' RETURN NULL; END;';
-
-    func_cmd :=
-      'CREATE OR REPLACE FUNCTION cs_find_referrer_type(v_host varchar,
-                                                        v_domain varchar,
-                                                        v_url varchar)
-        RETURNS varchar AS '
-      || quote_literal(func_body)
-      || ' LANGUAGE plpgsql;' ;
-
-    EXECUTE func_cmd;
-END;
-$func$ LANGUAGE plpgsql;
-</programlisting>
-     Notice how the body of the function is built separately and passed
-     through <literal>quote_literal</> to double any quote marks in it.  This
-     technique is needed because we cannot safely use dollar quoting for
-     defining the new function: we do not know for sure what strings will
-     be interpolated from the <structfield>referrer_key.key_string</> field.
-     (We are assuming here that <structfield>referrer_key.kind</> can be
-     trusted to always be <literal>host</>, <literal>domain</>, or
-     <literal>url</>, but <structfield>referrer_key.key_string</> might be
-     anything, in particular it might contain dollar signs.) This function
-     is actually an improvement on the Oracle original, because it will
-     not generate broken code when <structfield>referrer_key.key_string</> or
-     <structfield>referrer_key.referrer_type</> contain quote marks.
-    </para>
-   </example>
-
-   <para>
-    <xref linkend="plpgsql-porting-ex3"> shows how to port a function
-    with <literal>OUT</> parameters and string manipulation.
-<!## PG>
-    <productname>PostgreSQL</> does not have a built-in
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> does not have a built-in
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> does not have a built-in
-<!## end>
-    <function>instr</function> function, but you can create one
-    using a combination of other
-    functions.<indexterm><primary>instr</></indexterm> In <xref
-    linkend="plpgsql-porting-appendix"> there is a
-    <application>PL/pgSQL</application> implementation of
-    <function>instr</function> that you can use to make your porting
-    easier.
-   </para>
-
-   <example id="plpgsql-porting-ex3">
-    <title>Porting a Procedure With String Manipulation and
-    <literal>OUT</> Parameters from <application>PL/SQL</> to
-    <application>PL/pgSQL</></title>
-
-    <para>
-     The following <productname>Oracle</productname> PL/SQL procedure is used
-     to parse a URL and return several elements (host, path, and query).
-    </para>
-
-    <para>
-     This is the Oracle version:
-<programlisting>
-CREATE OR REPLACE PROCEDURE cs_parse_url(
-    v_url IN VARCHAR,
-    v_host OUT VARCHAR,  -- This will be passed back
-    v_path OUT VARCHAR,  -- This one too
-    v_query OUT VARCHAR) -- And this one
-IS
-    a_pos1 INTEGER;
-    a_pos2 INTEGER;
-BEGIN
-    v_host := NULL;
-    v_path := NULL;
-    v_query := NULL;
-    a_pos1 := instr(v_url, '//');
-
-    IF a_pos1 = 0 THEN
-        RETURN;
-    END IF;
-    a_pos2 := instr(v_url, '/', a_pos1 + 2);
-    IF a_pos2 = 0 THEN
-        v_host := substr(v_url, a_pos1 + 2);
-        v_path := '/';
-        RETURN;
-    END IF;
-
-    v_host := substr(v_url, a_pos1 + 2, a_pos2 - a_pos1 - 2);
-    a_pos1 := instr(v_url, '?', a_pos2 + 1);
-
-    IF a_pos1 = 0 THEN
-        v_path := substr(v_url, a_pos2);
-        RETURN;
-    END IF;
-
-    v_path := substr(v_url, a_pos2, a_pos1 - a_pos2);
-    v_query := substr(v_url, a_pos1 + 1);
-END;
-/
-show errors;
-</programlisting>
-    </para>
-
-    <para>
-     Here is a possible translation into <application>PL/pgSQL</>:
-<programlisting>
-CREATE OR REPLACE FUNCTION cs_parse_url(
-    v_url IN VARCHAR,
-    v_host OUT VARCHAR,  -- This will be passed back
-    v_path OUT VARCHAR,  -- This one too
-    v_query OUT VARCHAR) -- And this one
-AS $$
-DECLARE
-    a_pos1 INTEGER;
-    a_pos2 INTEGER;
-BEGIN
-    v_host := NULL;
-    v_path := NULL;
-    v_query := NULL;
-    a_pos1 := instr(v_url, '//');
-
-    IF a_pos1 = 0 THEN
-        RETURN;
-    END IF;
-    a_pos2 := instr(v_url, '/', a_pos1 + 2);
-    IF a_pos2 = 0 THEN
-        v_host := substr(v_url, a_pos1 + 2);
-        v_path := '/';
-        RETURN;
-    END IF;
-
-    v_host := substr(v_url, a_pos1 + 2, a_pos2 - a_pos1 - 2);
-    a_pos1 := instr(v_url, '?', a_pos2 + 1);
-
-    IF a_pos1 = 0 THEN
-        v_path := substr(v_url, a_pos2);
-        RETURN;
-    END IF;
-
-    v_path := substr(v_url, a_pos2, a_pos1 - a_pos2);
-    v_query := substr(v_url, a_pos1 + 1);
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-
-     This function could be used like this:
-<programlisting>
-SELECT * FROM cs_parse_url('http://foobar.com/query.cgi?baz');
-</programlisting>
-    </para>
-   </example>
-
-   <para>
-    <xref linkend="plpgsql-porting-ex4"> shows how to port a procedure
-    that uses numerous features that are specific to Oracle.
-   </para>
-
-   <example id="plpgsql-porting-ex4">
-    <title>Porting a Procedure from <application>PL/SQL</> to <application>PL/pgSQL</></title>
-
-    <para>
-     The Oracle version:
-
-<programlisting>
-CREATE OR REPLACE PROCEDURE cs_create_job(v_job_id IN INTEGER) IS
-    a_running_job_count INTEGER;
-    PRAGMA AUTONOMOUS_TRANSACTION;<co id="co.plpgsql-porting-pragma">
-BEGIN
-    LOCK TABLE cs_jobs IN EXCLUSIVE MODE;<co id="co.plpgsql-porting-locktable">
-
-    SELECT count(*) INTO a_running_job_count FROM cs_jobs WHERE end_stamp IS NULL;
-
-    IF a_running_job_count &gt; 0 THEN
-        COMMIT; -- free lock<co id="co.plpgsql-porting-commit">
-        raise_application_error(-20000,
-                 'Unable to create a new job: a job is currently running.');
-    END IF;
-
-    DELETE FROM cs_active_job;
-    INSERT INTO cs_active_job(job_id) VALUES (v_job_id);
-
-    BEGIN
-        INSERT INTO cs_jobs (job_id, start_stamp) VALUES (v_job_id, sysdate);
-    EXCEPTION
-        WHEN dup_val_on_index THEN NULL; -- don't worry if it already exists
-    END;
-    COMMIT;
-END;
-/
-show errors
-</programlisting>
-   </para>
-
-   <para>
-<!## PG>
-    Procedures like this can easily be converted into <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-    Procedures like this can easily be converted into <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-    Procedures like this can easily be converted into <productname>Postgres-XL</>
-<!## end>
-    functions returning <type>void</type>. This procedure in
-    particular is interesting because it can teach us some things:
-
-    <calloutlist>
-     <callout arearefs="co.plpgsql-porting-pragma">
-      <para>
-<!## PG>
-       There is no <literal>PRAGMA</literal> statement in <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-       There is no <literal>PRAGMA</literal> statement in <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-       There is no <literal>PRAGMA</literal> statement in <productname>Postgres-XL</>.
-<!## end>
-      </para>
-     </callout>
-
-     <callout arearefs="co.plpgsql-porting-locktable">
-      <para>
-       If you do a <command>LOCK TABLE</command> in <application>PL/pgSQL</>,
-       the lock will not be released until the calling transaction is
-       finished.
-      </para>
-     </callout>
-
-     <callout arearefs="co.plpgsql-porting-commit">
-      <para>
-       You cannot issue <command>COMMIT</> in a
-       <application>PL/pgSQL</application> function.  The function is
-       running within some outer transaction and so <command>COMMIT</>
-       would imply terminating the function's execution.  However, in
-       this particular case it is not necessary anyway, because the lock
-       obtained by the <command>LOCK TABLE</command> will be released when
-       we raise an error.
-      </para>
-     </callout>
-    </calloutlist>
-   </para>
-
-   <para>
-    This is how we could port this procedure to <application>PL/pgSQL</>:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION cs_create_job(v_job_id integer) RETURNS void AS $$
-DECLARE
-    a_running_job_count integer;
-BEGIN
-    LOCK TABLE cs_jobs IN EXCLUSIVE MODE;
-
-    SELECT count(*) INTO a_running_job_count FROM cs_jobs WHERE end_stamp IS NULL;
-
-    IF a_running_job_count &gt; 0 THEN
-        RAISE EXCEPTION 'Unable to create a new job: a job is currently running';<co id="co.plpgsql-porting-raise">
-    END IF;
-
-    DELETE FROM cs_active_job;
-    INSERT INTO cs_active_job(job_id) VALUES (v_job_id);
-
-    BEGIN
-        INSERT INTO cs_jobs (job_id, start_stamp) VALUES (v_job_id, now());
-    EXCEPTION
-        WHEN unique_violation THEN <co id="co.plpgsql-porting-exception">
-            -- don't worry if it already exists
-    END;
-END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-
-    <calloutlist>
-     <callout arearefs="co.plpgsql-porting-raise">
-      <para>
-       The syntax of <literal>RAISE</> is considerably different from
-       Oracle's statement, although the basic case <literal>RAISE</>
-       <replaceable class="parameter">exception_name</replaceable> works
-       similarly.
-      </para>
-     </callout>
-     <callout arearefs="co.plpgsql-porting-exception">
-      <para>
-       The exception names supported by <application>PL/pgSQL</> are
-       different from Oracle's.  The set of built-in exception names
-       is much larger (see <xref linkend="errcodes-appendix">).  There
-       is not currently a way to declare user-defined exception names,
-       although you can throw user-chosen SQLSTATE values instead.
-      </para>
-     </callout>
-    </calloutlist>
-
-    The main functional difference between this procedure and the
-    Oracle equivalent is that the exclusive lock on the <literal>cs_jobs</>
-    table will be held until the calling transaction completes.  Also, if
-    the caller later aborts (for example due to an error), the effects of
-    this procedure will be rolled back.
-   </para>
-   </example>
-  </sect2>
-
-  <sect2 id="plpgsql-porting-other">
-   <title>Other Things to Watch For</title>
-
-&common;
-   <para>
-    This section explains a few other things to watch for when porting
-    Oracle <application>PL/SQL</> functions to
-<!## PG>
-    <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>.
-<!## end>
-   </para>
-
-   <sect3 id="plpgsql-porting-exceptions">
-    <title>Implicit Rollback after Exceptions</title>
-
-&common;
-    <para>
-     In <application>PL/pgSQL</>, when an exception is caught by an
-     <literal>EXCEPTION</> clause, all database changes since the block's
-     <literal>BEGIN</> are automatically rolled back.  That is, the behavior
-     is equivalent to what you'd get in Oracle with:
-
-<programlisting>
-BEGIN
-    SAVEPOINT s1;
-    ... code here ...
-EXCEPTION
-    WHEN ... THEN
-        ROLLBACK TO s1;
-        ... code here ...
-    WHEN ... THEN
-        ROLLBACK TO s1;
-        ... code here ...
-END;
-</programlisting>
-
-     If you are translating an Oracle procedure that uses
-     <command>SAVEPOINT</> and <command>ROLLBACK TO</> in this style,
-     your task is easy: just omit the <command>SAVEPOINT</> and
-     <command>ROLLBACK TO</>.  If you have a procedure that uses
-     <command>SAVEPOINT</> and <command>ROLLBACK TO</> in a different way
-     then some actual thought will be required.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title><command>EXECUTE</command></title>
-
-&common;
-    <para>
-     The <application>PL/pgSQL</> version of
-     <command>EXECUTE</command> works similarly to the
-     <application>PL/SQL</> version, but you have to remember to use
-     <function>quote_literal</function> and
-     <function>quote_ident</function> as described in <xref
-     linkend="plpgsql-statements-executing-dyn">.  Constructs of the
-     type <literal>EXECUTE 'SELECT * FROM $1';</literal> will not work
-     reliably unless you use these functions.
-    </para>
-   </sect3>
-
-   <sect3 id="plpgsql-porting-optimization">
-    <title>Optimizing <application>PL/pgSQL</application> Functions</title>
-
-&common;
-    <para>
-<!## PG>
-     <productname>PostgreSQL</> gives you two function creation
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</> gives you two function creation
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</> gives you two function creation
-<!## end>
-     modifiers to optimize execution: <quote>volatility</> (whether
-     the function always returns the same result when given the same
-     arguments) and <quote>strictness</quote> (whether the function
-     returns null if any argument is null).  Consult the <xref
-     linkend="sql-createfunction">
-     reference page for details.
-    </para>
-
-    <para>
-     When making use of these optimization attributes, your
-     <command>CREATE FUNCTION</command> statement might look something
-     like this:
-
-<programlisting>
-CREATE FUNCTION foo(...) RETURNS integer AS $$
-...
-$$ LANGUAGE plpgsql STRICT IMMUTABLE;
-</programlisting>
-    </para>
-   </sect3>
-  </sect2>
-
-  <sect2 id="plpgsql-porting-appendix">
-   <title>Appendix</title>
-
-&common;
-   <para>
-    This section contains the code for a set of Oracle-compatible
-    <function>instr</function> functions that you can use to simplify
-    your porting efforts.
-   </para>
-
-<programlisting>
---
--- instr functions that mimic Oracle's counterpart
--- Syntax: instr(string1, string2, [n], [m]) where [] denotes optional parameters.
---
--- Searches string1 beginning at the nth character for the mth occurrence
--- of string2.  If n is negative, search backwards.  If m is not passed,
--- assume 1 (search starts at first character).
---
-
-CREATE FUNCTION instr(varchar, varchar) RETURNS integer AS $$
-DECLARE
-    pos integer;
-BEGIN
-    pos:= instr($1, $2, 1);
-    RETURN pos;
-END;
-$$ LANGUAGE plpgsql STRICT IMMUTABLE;
-
-
-CREATE FUNCTION instr(string varchar, string_to_search varchar, beg_index integer)
-RETURNS integer AS $$
-DECLARE
-    pos integer NOT NULL DEFAULT 0;
-    temp_str varchar;
-    beg integer;
-    length integer;
-    ss_length integer;
-BEGIN
-    IF beg_index &gt; 0 THEN
-        temp_str := substring(string FROM beg_index);
-        pos := position(string_to_search IN temp_str);
-
-        IF pos = 0 THEN
-            RETURN 0;
-        ELSE
-            RETURN pos + beg_index - 1;
-        END IF;
-    ELSE
-        ss_length := char_length(string_to_search);
-        length := char_length(string);
-        beg := length + beg_index - ss_length + 2;
-
-        WHILE beg &gt; 0 LOOP
-            temp_str := substring(string FROM beg FOR ss_length);
-            pos := position(string_to_search IN temp_str);
-
-            IF pos &gt; 0 THEN
-                RETURN beg;
-            END IF;
-
-            beg := beg - 1;
-        END LOOP;
-
-        RETURN 0;
-    END IF;
-END;
-$$ LANGUAGE plpgsql STRICT IMMUTABLE;
-
-
-CREATE FUNCTION instr(string varchar, string_to_search varchar,
-                      beg_index integer, occur_index integer)
-RETURNS integer AS $$
-DECLARE
-    pos integer NOT NULL DEFAULT 0;
-    occur_number integer NOT NULL DEFAULT 0;
-    temp_str varchar;
-    beg integer;
-    i integer;
-    length integer;
-    ss_length integer;
-BEGIN
-    IF beg_index &gt; 0 THEN
-        beg := beg_index;
-        temp_str := substring(string FROM beg_index);
-
-        FOR i IN 1..occur_index LOOP
-            pos := position(string_to_search IN temp_str);
-
-            IF i = 1 THEN
-                beg := beg + pos - 1;
-            ELSE
-                beg := beg + pos;
-            END IF;
-
-            temp_str := substring(string FROM beg + 1);
-        END LOOP;
-
-        IF pos = 0 THEN
-            RETURN 0;
-        ELSE
-            RETURN beg;
-        END IF;
-    ELSE
-        ss_length := char_length(string_to_search);
-        length := char_length(string);
-        beg := length + beg_index - ss_length + 2;
-
-        WHILE beg &gt; 0 LOOP
-            temp_str := substring(string FROM beg FOR ss_length);
-            pos := position(string_to_search IN temp_str);
-
-            IF pos &gt; 0 THEN
-                occur_number := occur_number + 1;
-
-                IF occur_number = occur_index THEN
-                    RETURN beg;
-                END IF;
-            END IF;
-
-            beg := beg - 1;
-        END LOOP;
-
-        RETURN 0;
-    END IF;
-END;
-$$ LANGUAGE plpgsql STRICT IMMUTABLE;
-</programlisting>
-  </sect2>
-
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/plpython.sgmlin b/doc-xc/src/sgml/plpython.sgmlin
deleted file mode 100644
index 076cc54c99..0000000000
--- a/doc-xc/src/sgml/plpython.sgmlin
+++ /dev/null
@@ -1,1287 +0,0 @@
-<!-- doc/src/sgml/plpython.sgml -->
-
-<chapter id="plpython">
- <title>PL/Python - Python Procedural Language</title>
-
- <indexterm zone="plpython"><primary>PL/Python</></>
- <indexterm zone="plpython"><primary>Python</></>
-
-&pgnotice;
-
- <para>
-  The <application>PL/Python</application> procedural language allows
-  <productname>PostgreSQL</productname> functions to be written in the
-  <ulink url="http://www.python.org">Python language</ulink>.
- </para>
-
- <para>
-  To install PL/Python in a particular database, use
-  <literal>CREATE EXTENSION plpythonu</>, or from the shell command line use
-  <literal>createlang plpythonu <replaceable>dbname</></literal> (but
-  see also <xref linkend="plpython-python23">).
- </para>
-
-  <tip>
-   <para>
-    If a language is installed into <literal>template1</>, all subsequently
-    created databases will have the language installed automatically.
-   </para>
-  </tip>
-
- <para>
-  As of <productname>PostgreSQL</productname> 7.4, PL/Python is only
-  available as an <quote>untrusted</> language, meaning it does not
-  offer any way of restricting what users can do in it.  It has
-  therefore been renamed to <literal>plpythonu</>.  The trusted
-  variant <literal>plpython</> might become available again in future,
-  if a new secure execution mechanism is developed in Python.  The
-  writer of a function in untrusted PL/Python must take care that the
-  function cannot be used to do anything unwanted, since it will be
-  able to do anything that could be done by a user logged in as the
-  database administrator.  Only superusers can create functions in
-  untrusted languages such as <literal>plpythonu</literal>.
- </para>
-
- <note>
-  <para>
-   Users of source packages must specially enable the build of
-   PL/Python during the installation process.  (Refer to the
-   installation instructions for more information.)  Users of binary
-   packages might find PL/Python in a separate subpackage.
-  </para>
- </note>
-
- <sect1 id="plpython-python23">
-  <title>Python 2 vs. Python 3</title>
-
-&pgnotice;
-  <para>
-   PL/Python supports both the Python 2 and Python 3 language
-   variants.  (The PostgreSQL installation instructions might contain
-   more precise information about the exact supported minor versions
-   of Python.)  Because the Python 2 and Python 3 language variants
-   are incompatible in some important aspects, the following naming
-   and transitioning scheme is used by PL/Python to avoid mixing them:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      The PostgreSQL language named <literal>plpython2u</literal>
-      implements PL/Python based on the Python 2 language variant.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The PostgreSQL language named <literal>plpython3u</literal>
-      implements PL/Python based on the Python 3 language variant.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The language named <literal>plpythonu</literal> implements
-      PL/Python based on the default Python language variant, which is
-      currently Python 2.  (This default is independent of what any
-      local Python installations might consider to be
-      their <quote>default</quote>, for example,
-      what <filename>/usr/bin/python</filename> might be.)  The
-      default will probably be changed to Python 3 in a distant future
-      release of PostgreSQL, depending on the progress of the
-      migration to Python 3 in the Python community.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   It depends on the build configuration or the installed packages
-   whether PL/Python for Python 2 or Python 3 or both are available.
-  </para>
-
-  <tip>
-   <para>
-    The built variant depends on which Python version was found during
-    the installation or which version was explicitly set using
-    the <envar>PYTHON</envar> environment variable;
-    see <xref linkend="install-procedure">.  To make both variants of
-    PL/Python available in one installation, the source tree has to be
-    configured and built twice.
-   </para>
-  </tip>
-
-  <para>
-   This results in the following usage and migration strategy:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Existing users and users who are currently not interested in
-      Python 3 use the language name <literal>plpythonu</literal> and
-      don't have to change anything for the foreseeable future.  It is
-      recommended to gradually <quote>future-proof</quote> the code
-      via migration to Python 2.6/2.7 to simplify the eventual
-      migration to Python 3.
-     </para>
-
-     <para>
-      In practice, many PL/Python functions will migrate to Python 3
-      with few or no changes.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Users who know that they have heavily Python 2 dependent code
-      and don't plan to ever change it can make use of
-      the <literal>plpython2u</literal> language name.  This will
-      continue to work into the very distant future, until Python 2
-      support might be completely dropped by PostgreSQL.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Users who want to dive into Python 3 can use
-      the <literal>plpython3u</literal> language name, which will keep
-      working forever by today's standards.  In the distant future,
-      when Python 3 might become the default, they might like to
-      remove the <quote>3</quote> for aesthetic reasons.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Daredevils, who want to build a Python-3-only operating system
-      environment, can change the contents of
-      <link linkend="catalog-pg-pltemplate"><structname>pg_pltemplate</structname></link>
-      to make <literal>plpythonu</literal> be equivalent
-      to <literal>plpython3u</literal>, keeping in mind that this
-      would make their installation incompatible with most of the rest
-      of the world.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   See also the
-   document <ulink url="http://docs.python.org/py3k/whatsnew/3.0.html">What's
-   New In Python 3.0</ulink> for more information about porting to
-   Python 3.
-  </para>
-
-  <para>
-   It is not allowed to use PL/Python based on Python 2 and PL/Python
-   based on Python 3 in the same session, because the symbols in the
-   dynamic modules would clash, which could result in crashes of the
-   PostgreSQL server process.  There is a check that prevents mixing
-   Python major versions in a session, which will abort the session if
-   a mismatch is detected.  It is possible, however, to use both
-   PL/Python variants in the same database, from separate sessions.
-  </para>
- </sect1>
-
- <sect1 id="plpython-funcs">
-  <title>PL/Python Functions</title>
-
-&pgnotice;
-  <para>
-   Functions in PL/Python are declared via the
-   standard <xref linkend="sql-createfunction"> syntax:
-
-<programlisting>
-CREATE FUNCTION <replaceable>funcname</replaceable> (<replaceable>argument-list</replaceable>)
-  RETURNS <replaceable>return-type</replaceable>
-AS $$
-  # PL/Python function body
-$$ LANGUAGE plpythonu;
-</programlisting>
-  </para>
-
-  <para>
-   The body of a function is simply a Python script. When the function
-   is called, its arguments are passed as elements of the list
-   <varname>args</varname>; named arguments are also passed as
-   ordinary variables to the Python script.  Use of named arguments is
-   usually more readable.  The result is returned from the Python code
-   in the usual way, with <literal>return</literal> or
-   <literal>yield</literal> (in case of a result-set statement).  If
-   you do not provide a return value, Python returns the default
-   <symbol>None</symbol>. <application>PL/Python</application> translates
-   Python's <symbol>None</symbol> into the SQL null value.
-  </para>
-
-  <para>
-   For example, a function to return the greater of two integers can be
-   defined as:
-
-<programlisting>
-CREATE FUNCTION pymax (a integer, b integer)
-  RETURNS integer
-AS $$
-  if a &gt; b:
-    return a
-  return b
-$$ LANGUAGE plpythonu;
-</programlisting>
-
-   The Python code that is given as the body of the function definition
-   is transformed into a Python function. For example, the above results in:
-
-<programlisting>
-def __plpython_procedure_pymax_23456():
-  if a &gt; b:
-    return a
-  return b
-</programlisting>
-
-   assuming that 23456 is the OID assigned to the function by
-   <productname>PostgreSQL</productname>.
-  </para>
-
-  <para>
-   The arguments are set as global variables.  Because of the scoping
-   rules of Python, this has the subtle consequence that an argument
-   variable cannot be reassigned inside the function to the value of
-   an expression that involves the variable name itself, unless the
-   variable is redeclared as global in the block.  For example, the
-   following won't work:
-<programlisting>
-CREATE FUNCTION pystrip(x text)
-  RETURNS text
-AS $$
-  x = x.strip()  # error
-  return x
-$$ LANGUAGE plpythonu;
-</programlisting>
-   because assigning to <varname>x</varname>
-   makes <varname>x</varname> a local variable for the entire block,
-   and so the <varname>x</varname> on the right-hand side of the
-   assignment refers to a not-yet-assigned local
-   variable <varname>x</varname>, not the PL/Python function
-   parameter.  Using the <literal>global</literal> statement, this can
-   be made to work:
-<programlisting>
-CREATE FUNCTION pystrip(x text)
-  RETURNS text
-AS $$
-  global x
-  x = x.strip()  # ok now
-  return x
-$$ LANGUAGE plpythonu;
-</programlisting>
-   But it is advisable not to rely on this implementation detail of
-   PL/Python.  It is better to treat the function parameters as
-   read-only.
-  </para>
- </sect1>
-
- <sect1 id="plpython-data">
-  <title>Data Values</title>
-&pgnotice;
-  <para>
-   Generally speaking, the aim of PL/Python is to provide
-   a <quote>natural</quote> mapping between the PostgreSQL and the
-   Python worlds.  This informs the data mapping rules described
-   below.
-  </para>
-
-  <sect2>
-   <title>Data Type Mapping</title>
-&pgnotice;
-   <para>
-    Function arguments are converted from their PostgreSQL type to a
-    corresponding Python type:
-    <itemizedlist>
-     <listitem>
-      <para>
-       PostgreSQL <type>boolean</type> is converted to Python <type>bool</type>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       PostgreSQL <type>smallint</type> and <type>int</type> are
-       converted to Python <type>int</type>.
-       PostgreSQL <type>bigint</type> is converted
-       to <type>long</type> in Python 2 and to <type>int</type> in
-       Python 3.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       PostgreSQL <type>real</type>, <type>double</type>,
-       and <type>numeric</type> are converted to
-       Python <type>float</type>.  Note that for
-       the <type>numeric</type> this loses information and can lead to
-       incorrect results.  This might be fixed in a future
-       release.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       PostgreSQL <type>bytea</type> is converted to
-       Python <type>str</type> in Python 2 and to <type>bytes</type>
-       in Python 3.  In Python 2, the string should be treated as a
-       byte sequence without any character encoding.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       All other data types, including the PostgreSQL character string
-       types, are converted to a Python <type>str</type>.  In Python
-       2, this string will be in the PostgreSQL server encoding; in
-       Python 3, it will be a Unicode string like all strings.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       For nonscalar data types, see below.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    Function return values are converted to the declared PostgreSQL
-    return data type as follows:
-    <itemizedlist>
-     <listitem>
-      <para>
-       When the PostgreSQL return type is <type>boolean</type>, the
-       return value will be evaluated for truth according to the
-       <emphasis>Python</emphasis> rules.  That is, 0 and empty string
-       are false, but notably <literal>'f'</literal> is true.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       When the PostgreSQL return type is <type>bytea</type>, the
-       return value will be converted to a string (Python 2) or bytes
-       (Python 3) using the respective Python built-ins, with the
-       result being converted <type>bytea</type>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       For all other PostgreSQL return types, the returned Python
-       value is converted to a string using the Python
-       built-in <literal>str</literal>, and the result is passed to the
-       input function of the PostgreSQL data type.
-      </para>
-
-      <para>
-       Strings in Python 2 are required to be in the PostgreSQL server
-       encoding when they are passed to PostgreSQL.  Strings that are
-       not valid in the current server encoding will raise an error,
-       but not all encoding mismatches can be detected, so garbage
-       data can still result when this is not done correctly.  Unicode
-       strings are converted to the correct encoding automatically, so
-       it can be safer and more convenient to use those.  In Python 3,
-       all strings are Unicode strings.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       For nonscalar data types, see below.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    Note that logical mismatches between the declared PostgreSQL
-    return type and the Python data type of the actual return object
-    are not flagged; the value will be converted in any case.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Null, None</title>
-&pgnotice;
-  <para>
-   If an SQL null value<indexterm><primary>null value</primary><secondary
-   sortas="PL/Python">in PL/Python</secondary></indexterm> is passed to a
-   function, the argument value will appear as <symbol>None</symbol> in
-   Python. For example, the function definition of <function>pymax</function>
-   shown in <xref linkend="plpython-funcs"> will return the wrong answer for null
-   inputs. We could add <literal>STRICT</literal> to the function definition
-   to make <productname>PostgreSQL</productname> do something more reasonable:
-   if a null value is passed, the function will not be called at all,
-   but will just return a null result automatically. Alternatively,
-   we could check for null inputs in the function body:
-
-<programlisting>
-CREATE FUNCTION pymax (a integer, b integer)
-  RETURNS integer
-AS $$
-  if (a is None) or (b is None):
-    return None
-  if a &gt; b:
-    return a
-  return b
-$$ LANGUAGE plpythonu;
-</programlisting>
-
-   As shown above, to return an SQL null value from a PL/Python
-   function, return the value <symbol>None</symbol>. This can be done whether the
-   function is strict or not.
-  </para>
-  </sect2>
-
-  <sect2 id="plpython-arrays">
-   <title>Arrays, Lists</title>
-&pgnotice;
-  <para>
-   SQL array values are passed into PL/Python as a Python list.  To
-   return an SQL array value out of a PL/Python function, return a
-   Python sequence, for example a list or tuple:
-
-<programlisting>
-CREATE FUNCTION return_arr()
-  RETURNS int[]
-AS $$
-return (1, 2, 3, 4, 5)
-$$ LANGUAGE plpythonu;
-
-SELECT return_arr();
- return_arr  
--------------
- {1,2,3,4,5}
-(1 row)
-</programlisting>
-
-   Note that in Python, strings are sequences, which can have
-   undesirable effects that might be familiar to Python programmers:
-
-<programlisting>
-CREATE FUNCTION return_str_arr()
-  RETURNS varchar[]
-AS $$
-return "hello"
-$$ LANGUAGE plpythonu;
-
-SELECT return_str_arr();
- return_str_arr
-----------------
- {h,e,l,l,o}
-(1 row)
-</programlisting>
-  </para>
-  </sect2>
-
-  <sect2>
-   <title>Composite Types</title>
-&pgnotice;
-  <para>
-   Composite-type arguments are passed to the function as Python mappings. The
-   element names of the mapping are the attribute names of the composite type.
-   If an attribute in the passed row has the null value, it has the value
-   <symbol>None</symbol> in the mapping. Here is an example:
-
-<programlisting>
-CREATE TABLE employee (
-  name text,
-  salary integer,
-  age integer
-);
-
-CREATE FUNCTION overpaid (e employee)
-  RETURNS boolean
-AS $$
-  if e["salary"] &gt; 200000:
-    return True
-  if (e["age"] &lt; 30) and (e["salary"] &gt; 100000):
-    return True
-  return False
-$$ LANGUAGE plpythonu;
-</programlisting>
-  </para>
-
-  <para>
-   There are multiple ways to return row or composite types from a Python
-   function. The following examples assume we have:
-
-<programlisting>
-CREATE TYPE named_value AS (
-  name   text,
-  value  integer
-);
-</programlisting>
-
-   A composite result can be returned as a:
-
-   <variablelist>
-    <varlistentry>
-     <term>Sequence type (a tuple or list, but not a set because
-     it is not indexable)</term>
-     <listitem>
-      <para>
-       Returned sequence objects must have the same number of items as the
-       composite result type has fields. The item with index 0 is assigned to
-       the first field of the composite type, 1 to the second and so on. For
-       example:
-
-<programlisting>
-CREATE FUNCTION make_pair (name text, value integer)
-  RETURNS named_value
-AS $$
-  return [ name, value ]
-  # or alternatively, as tuple: return ( name, value )
-$$ LANGUAGE plpythonu;
-</programlisting>
-
-       To return a SQL null for any column, insert <symbol>None</symbol> at
-       the corresponding position.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Mapping (dictionary)</term>
-     <listitem>
-      <para>
-       The value for each result type column is retrieved from the mapping
-       with the column name as key. Example:
-
-<programlisting>
-CREATE FUNCTION make_pair (name text, value integer)
-  RETURNS named_value
-AS $$
-  return { "name": name, "value": value }
-$$ LANGUAGE plpythonu;
-</programlisting>
-
-       Any extra dictionary key/value pairs are ignored. Missing keys are
-       treated as errors.
-       To return a SQL null value for any column, insert
-       <symbol>None</symbol> with the corresponding column name as the key.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Object (any object providing method <literal>__getattr__</literal>)</term>
-     <listitem>
-      <para>
-       This works the same as a mapping.
-       Example:
-
-<programlisting>
-CREATE FUNCTION make_pair (name text, value integer)
-  RETURNS named_value
-AS $$
-  class named_value:
-    def __init__ (self, n, v):
-      self.name = n
-      self.value = v
-  return named_value(name, value)
-
-  # or simply
-  class nv: pass
-  nv.name = name
-  nv.value = value
-  return nv
-$$ LANGUAGE plpythonu;
-</programlisting>
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-   <para>
-    Functions with <literal>OUT</literal> parameters are also supported.  For example:
-<programlisting>
-CREATE FUNCTION multiout_simple(OUT i integer, OUT j integer) AS $$
-return (1, 2)
-$$ LANGUAGE plpythonu;
-
-SELECT * FROM multiout_simple();
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Set-returning Functions</title>
-&pgnotice;
-  <para>
-   A <application>PL/Python</application> function can also return sets of
-   scalar or composite types. There are several ways to achieve this because
-   the returned object is internally turned into an iterator. The following
-   examples assume we have composite type:
-
-<programlisting>
-CREATE TYPE greeting AS (
-  how text,
-  who text
-);
-</programlisting>
-
-   A set result can be returned from a:
-
-   <variablelist>
-    <varlistentry>
-     <term>Sequence type (tuple, list, set)</term>
-     <listitem>
-      <para>
-<programlisting>
-CREATE FUNCTION greet (how text)
-  RETURNS SETOF greeting
-AS $$
-  # return tuple containing lists as composite types
-  # all other combinations work also
-  return ( [ how, "World" ], [ how, "PostgreSQL" ], [ how, "PL/Python" ] )
-$$ LANGUAGE plpythonu;
-</programlisting>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Iterator (any object providing <symbol>__iter__</symbol> and
-      <symbol>next</symbol> methods)</term>
-     <listitem>
-      <para>
-<programlisting>
-CREATE FUNCTION greet (how text)
-  RETURNS SETOF greeting
-AS $$
-  class producer:
-    def __init__ (self, how, who):
-      self.how = how
-      self.who = who
-      self.ndx = -1
-
-    def __iter__ (self):
-      return self
-
-    def next (self):
-      self.ndx += 1
-      if self.ndx == len(self.who):
-        raise StopIteration
-      return ( self.how, self.who[self.ndx] )
-
-  return producer(how, [ "World", "PostgreSQL", "PL/Python" ])
-$$ LANGUAGE plpythonu;
-</programlisting>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Generator (<literal>yield</literal>)</term>
-     <listitem>
-      <para>
-<programlisting>
-CREATE FUNCTION greet (how text)
-  RETURNS SETOF greeting
-AS $$
-  for who in [ "World", "PostgreSQL", "PL/Python" ]:
-    yield ( how, who )
-$$ LANGUAGE plpythonu;
-</programlisting>
-
-       <warning>
-        <para>
-         Due to Python
-         <ulink url="http://bugs.python.org/issue1483133">bug #1483133</ulink>,
-         some debug versions of Python 2.4
-         (configured and compiled with option <literal>--with-pydebug</literal>)
-         are known to crash the <productname>PostgreSQL</productname> server
-         when using an iterator to return a set result.
-         Unpatched versions of Fedora 4 contain this bug.
-         It does not happen in production versions of Python or on patched
-         versions of Fedora 4.
-        </para>
-       </warning>
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-   <para>
-    Set-returning functions with <literal>OUT</literal> parameters
-    (using <literal>RETURNS SETOF record</literal>) are also
-    supported.  For example:
-<programlisting>
-CREATE FUNCTION multiout_simple_setof(n integer, OUT integer, OUT integer) RETURNS SETOF record AS $$
-return [(1, 2)] * n
-$$ LANGUAGE plpythonu;
-
-SELECT * FROM multiout_simple_setof(3);
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="plpython-sharing">
-  <title>Sharing Data</title>
-&pgnotice;
-  <para>
-   The global dictionary <varname>SD</varname> is available to store
-   data between function calls.  This variable is private static data.
-   The global dictionary <varname>GD</varname> is public data,
-   available to all Python functions within a session.  Use with
-   care.<indexterm><primary>global data</>
-   <secondary>in PL/Python</></indexterm>
-  </para>
-
-  <para>
-   Each function gets its own execution environment in the
-   Python interpreter, so that global data and function arguments from
-   <function>myfunc</function> are not available to
-   <function>myfunc2</function>.  The exception is the data in the
-   <varname>GD</varname> dictionary, as mentioned above.
-  </para>
- </sect1>
-
- <sect1 id="plpython-do">
-  <title>Anonymous Code Blocks</title>
-
-&pgnotice;
-  <para>
-   PL/Python also supports anonymous code blocks called with the
-   <xref linkend="sql-do"> statement:
-
-<programlisting>
-DO $$
-    # PL/Python code
-$$ LANGUAGE plpythonu;
-</programlisting>
-
-   An anonymous code block receives no arguments, and whatever value it
-   might return is discarded.  Otherwise it behaves just like a function.
-  </para>
- </sect1>
-
- <sect1 id="plpython-trigger">
-  <title>Trigger Functions</title>
-
-  <indexterm zone="plpython-trigger">
-   <primary>trigger</primary>
-   <secondary>in PL/Python</secondary>
-  </indexterm>
-
-&pgnotice;
-  <para>
-   When a function is used as a trigger, the dictionary
-   <literal>TD</literal> contains trigger-related values:
-   <variablelist>
-    <varlistentry>
-     <term><literal>TD["event"]</></term>
-     <listitem>
-      <para>
-       contains the event as a string:
-       <literal>INSERT</>, <literal>UPDATE</>,
-       <literal>DELETE</>, or <literal>TRUNCATE</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>TD["when"]</></term>
-     <listitem>
-      <para>
-       contains one of <literal>BEFORE</>, <literal>AFTER</>, or
-       <literal>INSTEAD OF</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>TD["level"]</></term>
-     <listitem>
-      <para>
-       contains <literal>ROW</> or <literal>STATEMENT</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>TD["new"]</></term>
-     <term><literal>TD["old"]</></term>
-     <listitem>
-      <para>
-       For a row-level trigger, one or both of these fields contain
-       the respective trigger rows, depending on the trigger event.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>TD["name"]</></term>
-     <listitem>
-      <para>
-       contains the trigger name.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>TD["table_name"]</></term>
-     <listitem>
-      <para>
-       contains the name of the table on which the trigger occurred.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>TD["table_schema"]</></term>
-     <listitem>
-      <para>
-       contains the schema of the table on which the trigger occurred.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>TD["relid"]</></term>
-     <listitem>
-      <para>
-       contains the OID of the table on which the trigger occurred.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>TD["args"]</></term>
-     <listitem>
-      <para>
-       If the <command>CREATE TRIGGER</> command
-       included arguments, they are available in <literal>TD["args"][0]</> to
-       <literal>TD["args"][<replaceable>n</>-1]</>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   If <literal>TD["when"]</literal> is <literal>BEFORE</> or
-   <literal>INSTEAD OF</> and
-   <literal>TD["level"]</literal> is <literal>ROW</>, you can
-   return <literal>None</literal> or <literal>"OK"</literal> from the
-   Python function to indicate the row is unmodified,
-   <literal>"SKIP"</> to abort the event, or if <literal>TD["event"]</>
-   is <command>INSERT</> or <command>UPDATE</> you can return
-   <literal>"MODIFY"</> to indicate you've modified the new row.
-   Otherwise the return value is ignored.
-  </para>
- </sect1>
-
- <sect1 id="plpython-database">
-  <title>Database Access</title>
-
-&pgnotice;
-  <para>
-   The PL/Python language module automatically imports a Python module
-   called <literal>plpy</literal>.  The functions and constants in
-   this module are available to you in the Python code as
-   <literal>plpy.<replaceable>foo</replaceable></literal>.
-  </para>
-
-  <sect2>
-    <title>Database Access Functions</title>
-
-  <para>
-   The <literal>plpy</literal> module provides two
-   functions called <function>execute</function> and
-   <function>prepare</function>.  Calling
-   <function>plpy.execute</function> with a query string and an
-   optional limit argument causes that query to be run and the result
-   to be returned in a result object.  The result object emulates a
-   list or dictionary object.  The result object can be accessed by
-   row number and column name.  It has these additional methods:
-   <function>nrows</function> which returns the number of rows
-   returned by the query, and <function>status</function> which is the
-   <function>SPI_execute()</function> return value.  The result object
-   can be modified.
-  </para>
-
-  <para>
-   For example:
-<programlisting>
-rv = plpy.execute("SELECT * FROM my_table", 5)
-</programlisting>
-   returns up to 5 rows from <literal>my_table</literal>.  If
-   <literal>my_table</literal> has a column
-   <literal>my_column</literal>, it would be accessed as:
-<programlisting>
-foo = rv[i]["my_column"]
-</programlisting>
-  </para>
-
-  <para>
-   <indexterm><primary>preparing a query</><secondary>in PL/Python</></indexterm>
-   The second function, <function>plpy.prepare</function>, prepares
-   the execution plan for a query.  It is called with a query string
-   and a list of parameter types, if you have parameter references in
-   the query.  For example:
-<programlisting>
-plan = plpy.prepare("SELECT last_name FROM my_users WHERE first_name = $1", [ "text" ])
-</programlisting>
-   <literal>text</literal> is the type of the variable you will be
-   passing for <literal>$1</literal>.  After preparing a statement, you
-   use the function <function>plpy.execute</function> to run it:
-<programlisting>
-rv = plpy.execute(plan, [ "name" ], 5)
-</programlisting>
-   The third argument is the limit and is optional.
-  </para>
-
-  <para>
-   Query parameters and result row fields are converted between
-   PostgreSQL and Python data types as described
-   in <xref linkend="plpython-data">.  The exception is that composite
-   types are currently not supported: They will be rejected as query
-   parameters and are converted to strings when appearing in a query
-   result.  As a workaround for the latter problem, the query can
-   sometimes be rewritten so that the composite type result appears as
-   a result row rather than as a field of the result row.
-   Alternatively, the resulting string could be parsed apart by hand,
-   but this approach is not recommended because it is not
-   future-proof.
-  </para>
-
-  <para>
-   When you prepare a plan using the PL/Python module it is
-   automatically saved.  Read the SPI documentation (<xref
-   linkend="spi">) for a description of what this means.
-   In order to make effective use of this across function calls
-   one needs to use one of the persistent storage dictionaries
-   <literal>SD</literal> or <literal>GD</literal> (see
-   <xref linkend="plpython-sharing">). For example:
-<programlisting>
-CREATE FUNCTION usesavedplan() RETURNS trigger AS $$
-    if SD.has_key("plan"):
-        plan = SD["plan"]
-    else:
-        plan = plpy.prepare("SELECT 1")
-        SD["plan"] = plan
-    # rest of function
-$$ LANGUAGE plpythonu;
-</programlisting>
-  </para>
-
-  </sect2>
-
-  <sect2 id="plpython-trapping">
-   <title>Trapping Errors</title>
-
-   <para>
-    Functions accessing the database might encounter errors, which
-    will cause them to abort and raise an exception.  Both
-    <function>plpy.execute</function> and
-    <function>plpy.prepare</function> can raise an instance of a subclass of
-    <literal>plpy.SPIError</literal>, which by default will terminate
-    the function.  This error can be handled just like any other
-    Python exception, by using the <literal>try/except</literal>
-    construct.  For example:
-<programlisting>
-CREATE FUNCTION try_adding_joe() RETURNS text AS $$
-    try:
-        plpy.execute("INSERT INTO users(username) VALUES ('joe')")
-    except plpy.SPIError:
-        return "something went wrong"
-    else:
-        return "Joe added"
-$$ LANGUAGE plpythonu;
-</programlisting>
-   </para>
-
-   <para>
-    The actual class of the exception being raised corresponds to the
-    specific condition that caused the error.  Refer
-    to <xref linkend="errcodes-table"> for a list of possible
-    conditions.  The module
-    <literal>plpy.spiexceptions</literal> defines an exception class
-    for each <productname>PostgreSQL</productname> condition, deriving
-    their names from the condition name.  For
-    instance, <literal>division_by_zero</literal>
-    becomes <literal>DivisionByZero</literal>, <literal>unique_violation</literal>
-    becomes <literal>UniqueViolation</literal>, <literal>fdw_error</literal>
-    becomes <literal>FdwError</literal>, and so on.  Each of these
-    exception classes inherits from <literal>SPIError</literal>.  This
-    separation makes it easier to handle specific errors, for
-    instance:
-<programlisting>
-CREATE FUNCTION insert_fraction(numerator int, denominator int) RETURNS text AS $$
-from plpy import spiexceptions
-try:
-    plan = plpy.prepare("INSERT INTO fractions (frac) VALUES ($1 / $2)", ["int", "int"])
-    plpy.execute(plan, [numerator, denominator])
-except spiexceptions.DivisionByZero:
-    return "denominator cannot equal zero"
-except spiexceptions.UniqueViolation:
-    return "already have that fraction"
-except plpy.SPIError, e:
-    return "other error, SQLSTATE %s" % e.sqlstate
-else:
-    return "fraction inserted"
-$$ LANGUAGE plpythonu;
-</programlisting>
-    Note that because all exceptions from
-    the <literal>plpy.spiexceptions</literal> module inherit
-    from <literal>SPIError</literal>, an <literal>except</literal>
-    clause handling it will catch any database access error.
-   </para>
-
-   <para>
-    As an alternative way of handling different error conditions, you
-    can catch the <literal>SPIError</literal> exception and determine
-    the specific error condition inside the <literal>except</literal>
-    block by looking at the <literal>sqlstate</literal> attribute of
-    the exception object.  This attribute is a string value containing
-    the <quote>SQLSTATE</quote> error code.  This approach provides
-    approximately the same functionality
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="plpython-subtransaction">
-  <title>Explicit Subtransactions</title>
-
-  <para>
-   Recovering from errors caused by database access as described in
-   <xref linkend="plpython-trapping"> can lead to an undesirable
-   situation where some operations succeed before one of them fails,
-   and after recovering from that error the data is left in an
-   inconsistent state.  PL/Python offers a solution to this problem in
-   the form of explicit subtransactions.
-  </para>
-
-  <sect2>
-   <title>Subtransaction Context Managers</title>
-
-   <para>
-    Consider a function that implements a transfer between two
-    accounts:
-<programlisting>
-CREATE FUNCTION transfer_funds() RETURNS void AS $$
-try:
-    plpy.execute("UPDATE accounts SET balance = balance - 100 WHERE account_name = 'joe'")
-    plpy.execute("UPDATE accounts SET balance = balance + 100 WHERE account_name = 'mary'")
-except plpy.SPIError, e:
-    result = "error transferring funds: %s" % e.args
-else:
-    result = "funds transferred correctly"
-plan = plpy.prepare("INSERT INTO operations (result) VALUES ($1)", ["text"])
-plpy.execute(plan, [result])
-$$ LANGUAGE plpythonu;
-</programlisting>
-    If the second <literal>UPDATE</literal> statement results in an
-    exception being raised, this function will report the error, but
-    the result of the first <literal>UPDATE</literal> will
-    nevertheless be committed.  In other words, the funds will be
-    withdrawn from Joe's account, but will not be transferred to
-    Mary's account.
-   </para>
-
-   <para>
-    To avoid such issues, you can wrap your
-    <literal>plpy.execute</literal> calls in an explicit
-    subtransaction.  The <literal>plpy</literal> module provides a
-    helper object to manage explicit subtransactions that gets created
-    with the <literal>plpy.subtransaction()</literal> function.
-    Objects created by this function implement the
-    <ulink url="http://docs.python.org/library/stdtypes.html#context-manager-types">
-    context manager interface</ulink>.  Using explicit subtransactions
-    we can rewrite our function as:
-<programlisting>
-CREATE FUNCTION transfer_funds2() RETURNS void AS $$
-try:
-    with plpy.subtransaction():
-        plpy.execute("UPDATE accounts SET balance = balance - 100 WHERE account_name = 'joe'")
-        plpy.execute("UPDATE accounts SET balance = balance + 100 WHERE account_name = 'mary'")
-except plpy.SPIError, e:
-    result = "error transferring funds: %s" % e.args
-else:
-    result = "funds transferred correctly"
-plan = plpy.prepare("INSERT INTO operations (result) VALUES ($1)", ["text"])
-plpy.execute(plan, [result])
-$$ LANGUAGE plpythonu;
-</programlisting>
-    Note that the use of <literal>try/catch</literal> is still
-    required.  Otherwise the exception would propagate to the top of
-    the Python stack and would cause the whole function to abort with
-    a <productname>PostgreSQL</productname> error, so that the
-    <literal>operations</literal> table would not have any row
-    inserted into it.  The subtransaction context manager does not
-    trap errors, it only assures that all database operations executed
-    inside its scope will be atomically committed or rolled back.  A
-    rollback of the subtransaction block occurs on any kind of
-    exception exit, not only ones caused by errors originating from
-    database access.  A regular Python exception raised inside an
-    explicit subtransaction block would also cause the subtransaction
-    to be rolled back.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Older Python Versions</title>
-
-   <para>
-    Context managers syntax using the <literal>with</literal> keyword
-    is available by default in Python 2.6.  If using PL/Python with an
-    older Python version, it is still possible to use explicit
-    subtransactions, although not as transparently.  You can call the
-    subtransaction manager's <literal>__enter__</literal> and
-    <literal>__exit__</literal> functions using the
-    <literal>enter</literal> and <literal>exit</literal> convenience
-    aliases.  The example function that transfers funds could be
-    written as:
-<programlisting>
-CREATE FUNCTION transfer_funds_old() RETURNS void AS $$
-try:
-    subxact = plpy.subtransaction()
-    subxact.enter()
-    try:
-        plpy.execute("UPDATE accounts SET balance = balance - 100 WHERE account_name = 'joe'")
-        plpy.execute("UPDATE accounts SET balance = balance + 100 WHERE account_name = 'mary'")
-    except:
-        import sys
-        subxact.exit(*sys.exc_info())
-        raise
-    else:
-        subxact.exit(None, None, None)
-except plpy.SPIError, e:
-    result = "error transferring funds: %s" % e.args
-else:
-    result = "funds transferred correctly"
-
-plan = plpy.prepare("INSERT INTO operations (result) VALUES ($1)", ["text"])
-plpy.execute(plan, [result])
-$$ LANGUAGE plpythonu;
-</programlisting>
-   </para>
-
-   <note>
-    <para>
-     Although context managers were implemented in Python 2.5, to use
-     the <literal>with</literal> syntax in that version you need to
-     use a <ulink
-     url="http://docs.python.org/release/2.5/ref/future.html">future
-     statement</ulink>.  Because of implementation details, however,
-     you cannot use future statements in PL/Python functions.
-    </para>
-   </note>
-  </sect2>
- </sect1>
-
- <sect1 id="plpython-util">
-  <title>Utility Functions</title>
-&pgnotice;
-  <para>
-   The <literal>plpy</literal> module also provides the functions
-   <literal>plpy.debug(<replaceable>msg</>)</literal>,
-   <literal>plpy.log(<replaceable>msg</>)</literal>,
-   <literal>plpy.info(<replaceable>msg</>)</literal>,
-   <literal>plpy.notice(<replaceable>msg</>)</literal>,
-   <literal>plpy.warning(<replaceable>msg</>)</literal>,
-   <literal>plpy.error(<replaceable>msg</>)</literal>, and
-   <literal>plpy.fatal(<replaceable>msg</>)</literal>.<indexterm><primary>elog</><secondary>in PL/Python</></indexterm>
-   <function>plpy.error</function> and
-   <function>plpy.fatal</function> actually raise a Python exception
-   which, if uncaught, propagates out to the calling query, causing
-   the current transaction or subtransaction to be aborted.
-   <literal>raise plpy.Error(<replaceable>msg</>)</literal> and
-   <literal>raise plpy.Fatal(<replaceable>msg</>)</literal> are
-   equivalent to calling
-   <function>plpy.error</function> and
-   <function>plpy.fatal</function>, respectively.
-   The other functions only generate messages of different
-   priority levels.
-   Whether messages of a particular priority are reported to the client,
-   written to the server log, or both is controlled by the
-   <xref linkend="guc-log-min-messages"> and
-   <xref linkend="guc-client-min-messages"> configuration
-   variables. See <xref linkend="runtime-config"> for more information.
-  </para>
-
-  <para>
-   Another set of utility functions are
-   <literal>plpy.quote_literal(<replaceable>string</>)</literal>,
-   <literal>plpy.quote_nullable(<replaceable>string</>)</literal>, and
-   <literal>plpy.quote_ident(<replaceable>string</>)</literal>.  They
-   are equivalent to the built-in quoting functions described in <xref
-   linkend="functions-string">.  They are useful when constructing
-   ad-hoc queries.  A PL/Python equivalent of dynamic SQL from <xref
-   linkend="plpgsql-quote-literal-example"> would be:
-<programlisting>
-plpy.execute("UPDATE tbl SET %s = %s WHERE key = %s" % (
-    plpy.quote_ident(colname),
-    plpy.quote_nullable(newvalue),
-    plpy.quote_literal(keyvalue)))
-</programlisting>
-  </para>
- </sect1>
-
- <sect1 id="plpython-envar">
-  <title>Environment Variables</title>
-
-&pgnotice;
-  <para>
-   Some of the environment variables that are accepted by the Python
-   interpreter can also be used to affect PL/Python behavior.  They
-   would need to be set in the environment of the main PostgreSQL
-   server process, for example in a start script.  The available
-   environment variables depend on the version of Python; see the
-   Python documentation for details.  At the time of this writing, the
-   following environment variables have an affect on PL/Python,
-   assuming an adequate Python version:
-   <itemizedlist>
-    <listitem>
-     <para><envar>PYTHONHOME</envar></para>
-    </listitem>
-
-    <listitem>
-     <para><envar>PYTHONPATH</envar></para>
-    </listitem>
-
-    <listitem>
-     <para><envar>PYTHONY2K</envar></para>
-    </listitem>
-
-    <listitem>
-     <para><envar>PYTHONOPTIMIZE</envar></para>
-    </listitem>
-
-    <listitem>
-     <para><envar>PYTHONDEBUG</envar></para>
-    </listitem>
-
-    <listitem>
-     <para><envar>PYTHONVERBOSE</envar></para>
-    </listitem>
-
-    <listitem>
-     <para><envar>PYTHONCASEOK</envar></para>
-    </listitem>
-
-    <listitem>
-     <para><envar>PYTHONDONTWRITEBYTECODE</envar></para>
-    </listitem>
-
-    <listitem>
-     <para><envar>PYTHONIOENCODING</envar></para>
-    </listitem>
-
-    <listitem>
-     <para><envar>PYTHONUSERBASE</envar></para>
-    </listitem>
-   </itemizedlist>
-
-   (It appears to be a Python implementation detail beyond the control
-   of PL/Python that some of the environment variables listed on
-   the <command>python</command> man page are only effective in a
-   command-line interpreter and not an embedded Python interpreter.)
-  </para>
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/pltcl.sgmlin b/doc-xc/src/sgml/pltcl.sgmlin
deleted file mode 100644
index c64b9fdb41..0000000000
--- a/doc-xc/src/sgml/pltcl.sgmlin
+++ /dev/null
@@ -1,937 +0,0 @@
-<!-- doc/src/sgml/pltcl.sgml -->
-
- <chapter id="pltcl">
-  <title>PL/Tcl - Tcl Procedural Language</title>
-
-  <indexterm zone="pltcl">
-   <primary>PL/Tcl</primary>
-  </indexterm>
-
-  <indexterm zone="pltcl">
-   <primary>Tcl</primary>
-  </indexterm>
-
-&common;
-
-  <para>
-   PL/Tcl is a loadable procedural language for the
-<!## PG>
-   <productname>PostgreSQL</productname> database system
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> database system inherited from <productname>PostgreSQL</>
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> database system inherited from <productname>PostgreSQL</>
-<!## end>
-   that enables the <ulink url="http://www.tcl.tk/">
-   Tcl language</ulink> to be used to write functions and
-   trigger procedures.
-  </para>
-
-<!## XC>
-  <para>
-   You can use PL/Tcl in <productname>Postgres-XC</> too.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   You can use PL/Tcl in <productname>Postgres-XL</> too.
-  </para>
-<!## end>
-
-  <!-- **** PL/Tcl overview **** -->
-
-  <sect1 id="pltcl-overview">
-   <title>Overview</title>
-
-&common;
-   <para>
-    PL/Tcl offers most of the capabilities a function writer has in
-    the C language, with a few restrictions, and with the addition of
-    the powerful string processing libraries that are available for
-    Tcl.
-   </para>
-   <para>
-    One compelling <emphasis>good</emphasis> restriction is that
-    everything is executed from within the safety of the context of a
-    Tcl interpreter.  In addition to the limited command set of safe
-    Tcl, only a few commands are available to access the database via
-    SPI and to raise messages via <function>elog()</>.  PL/Tcl
-    provides no way to access internals of the database server or to
-    gain OS-level access under the permissions of the
-<!## PG>
-    <productname>PostgreSQL</productname> server process, as a C
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> server process, as a C
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> server process, as a C
-<!## end>
-    function can do.  Thus, unprivileged database users can be trusted
-    to use this language; it does not give them unlimited authority.
-   </para>
-   <para>
-    The other notable implementation restriction is that Tcl functions
-    cannot be used to create input/output functions for new data
-    types.
-   </para>
-   <para>
-    Sometimes it is desirable to write Tcl functions that are not restricted
-    to safe Tcl.  For example, one might want a Tcl function that sends
-    email.  To handle these cases, there is a variant of <application>PL/Tcl</> called <literal>PL/TclU</>
-    (for untrusted Tcl).  This is the exact same language except that a full
-    Tcl interpreter is used.  <emphasis>If <application>PL/TclU</> is used, it must be
-    installed as an untrusted procedural language</emphasis> so that only
-    database superusers can create functions in it.  The writer of a <application>PL/TclU</>
-    function must take care that the function cannot be used to do anything
-    unwanted, since it will be able to do anything that could be done by
-    a user logged in as the database administrator.
-   </para>
-   <para>
-    The shared object code for the <application>PL/Tcl</> and
-    <application>PL/TclU</> call handlers is automatically built and
-<!## PG>
-    installed in the <productname>PostgreSQL</productname> library
-<!## end>
-<!## XC>
-    installed in the <productname>Postgres-XC</productname> library
-<!## end>
-<!## XL>
-    installed in the <productname>Postgres-XL</productname> library
-<!## end>
-    directory if Tcl support is specified in the configuration step of
-    the installation procedure.  To install <application>PL/Tcl</>
-    and/or <application>PL/TclU</> in a particular database, use the
-    <command>CREATE EXTENSION</> command or the
-    <command>createlang</command> program, for example
-    <literal>createlang pltcl <replaceable>dbname</></literal> or
-    <literal>createlang pltclu <replaceable>dbname</></literal>.
-   </para>
-  </sect1>
-
-  <!-- **** PL/Tcl description **** -->
-
-   <sect1 id="pltcl-functions">
-    <title>PL/Tcl Functions and Arguments</title>
-
-&common;
-    <para>
-     To create a function in the <application>PL/Tcl</> language, use
-     the standard <xref linkend="sql-createfunction"> syntax:
-
-<programlisting>
-CREATE FUNCTION <replaceable>funcname</replaceable> (<replaceable>argument-types</replaceable>) RETURNS <replaceable>return-type</replaceable> AS $$
-    # PL/Tcl function body
-$$ LANGUAGE pltcl;
-</programlisting>
-
-     <application>PL/TclU</> is the same, except that the language has to be specified as
-     <literal>pltclu</>.
-    </para>
-
-    <para>
-     The body of the function is simply a piece of Tcl script.
-     When the function is called, the argument values are passed as
-     variables <literal>$1</literal> ... <literal>$<replaceable>n</replaceable></literal> to the
-     Tcl script.  The result is returned
-     from the Tcl code in the usual way, with a <literal>return</literal>
-     statement.
-    </para>
-
-    <para>
-     For example, a function
-     returning the greater of two integer values could be defined as:
-
-<programlisting>
-CREATE FUNCTION tcl_max(integer, integer) RETURNS integer AS $$
-    if {$1 &gt; $2} {return $1}
-    return $2
-$$ LANGUAGE pltcl STRICT;
-</programlisting>
-
-     Note the clause <literal>STRICT</>, which saves us from
-     having to think about null input values: if a null value is passed, the
-     function will not be called at all, but will just return a null
-     result automatically.
-    </para>
-
-    <para>
-     In a nonstrict function,
-     if the actual value of an argument is null, the corresponding
-     <literal>$<replaceable>n</replaceable></literal> variable will be set to an empty string.
-     To detect whether a particular argument is null, use the function
-     <literal>argisnull</>.  For example, suppose that we wanted <function>tcl_max</function>
-     with one null and one nonnull argument to return the nonnull
-     argument, rather than null:
-
-<programlisting>
-CREATE FUNCTION tcl_max(integer, integer) RETURNS integer AS $$
-    if {[argisnull 1]} {
-        if {[argisnull 2]} { return_null }
-        return $2
-    }
-    if {[argisnull 2]} { return $1 }
-    if {$1 &gt; $2} {return $1}
-    return $2
-$$ LANGUAGE pltcl;
-</programlisting>
-    </para>
-
-    <para>
-     As shown above,
-     to return a null value from a PL/Tcl function, execute
-     <literal>return_null</literal>.  This can be done whether the
-     function is strict or not.
-    </para>
-
-    <para>
-     Composite-type arguments are passed to the function as Tcl
-     arrays.  The element names of the array are the attribute names
-     of the composite type. If an attribute in the passed row has the
-     null value, it will not appear in the array. Here is an example:
-
-<programlisting>
-CREATE TABLE employee (
-    name text,
-    salary integer,
-    age integer
-);
-
-CREATE FUNCTION overpaid(employee) RETURNS boolean AS $$
-    if {200000.0 &lt; $1(salary)} {
-        return "t"
-    }
-    if {$1(age) &lt; 30 &amp;&amp; 100000.0 &lt; $1(salary)} {
-        return "t"
-    }
-    return "f"
-$$ LANGUAGE pltcl;
-</programlisting>
-    </para>
-
-    <para>
-     There is currently no support for returning a composite-type
-     result value, nor for returning sets.
-    </para>
-
-    <para>
-     <application>PL/Tcl</> does not currently have full support for
-     domain types: it treats a domain the same as the underlying scalar
-     type.  This means that constraints associated with the domain will
-     not be enforced.  This is not an issue for function arguments, but
-     it is a hazard if you declare a <application>PL/Tcl</> function
-     as returning a domain type.
-    </para>
-
-   </sect1>
-
-   <sect1 id="pltcl-data">
-    <title>Data Values in PL/Tcl</title>
-
-&common;
-    <para>
-     The argument values supplied to a PL/Tcl function's code are simply
-     the input arguments converted to text form (just as if they had been
-     displayed by a <command>SELECT</> statement).  Conversely, the
-     <literal>return</>
-     command will accept any string that is acceptable input format for
-     the function's declared return type.  So, within the PL/Tcl function,
-     all values are just text strings.
-    </para>
-
-   </sect1>
-
-   <sect1 id="pltcl-global">
-    <title>Global Data in PL/Tcl</title>
-
-    <indexterm zone="pltcl-global">
-     <primary>global data</primary>
-     <secondary>in PL/Tcl</secondary>
-    </indexterm>
-
-&common;
-    <para>
-     Sometimes it
-     is useful to have some global data that is held between two
-     calls to a function or is shared between different functions.
-     This is easily done in PL/Tcl, but there are some restrictions that
-     must be understood.
-    </para>
-
-    <para>
-     For security reasons, PL/Tcl executes functions called by any one SQL
-     role in a separate Tcl interpreter for that role.  This prevents
-     accidental or malicious interference by one user with the behavior of
-     another user's PL/Tcl functions.  Each such interpreter will have its own
-     values for any <quote>global</> Tcl variables.  Thus, two PL/Tcl
-     functions will share the same global variables if and only if they are
-     executed by the same SQL role.  In an application wherein a single
-     session executes code under multiple SQL roles (via <literal>SECURITY
-     DEFINER</> functions, use of <command>SET ROLE</>, etc) you may need to
-     take explicit steps to ensure that PL/Tcl functions can share data.  To
-     do that, make sure that functions that should communicate are owned by
-     the same user, and mark them <literal>SECURITY DEFINER</>.  You must of
-     course take care that such functions can't be used to do anything
-     unintended.
-    </para>
-
-    <para>
-     All PL/TclU functions used in a session execute in the same Tcl
-     interpreter, which of course is distinct from the interpreter(s)
-     used for PL/Tcl functions.  So global data is automatically shared
-     between PL/TclU functions.  This is not considered a security risk
-     because all PL/TclU functions execute at the same trust level,
-     namely that of a database superuser.
-    </para>
-
-    <para>
-     To help protect PL/Tcl functions from unintentionally interfering
-     with each other, a global
-     array is made available to each function via the <function>upvar</>
-     command. The global name of this variable is the function's internal
-     name, and the local name is <literal>GD</>.  It is recommended that
-     <literal>GD</> be used
-     for persistent private data of a function.  Use regular Tcl global
-     variables only for values that you specifically intend to be shared among
-     multiple functions.  (Note that the <literal>GD</> arrays are only
-     global within a particular interpreter, so they do not bypass the
-     security restrictions mentioned above.)
-    </para>
-
-    <para>
-     An example of using <literal>GD</> appears in the
-     <function>spi_execp</function> example below.
-    </para>
-   </sect1>
-
-   <sect1 id="pltcl-dbaccess">
-    <title>Database Access from PL/Tcl</title>
-
-&common;
-    <para>
-     The following commands are available to access the database from
-     the body of a PL/Tcl function:
-
-    <variablelist>
-
-     <varlistentry>
-      <term><literal><function>spi_exec</function> <optional role="tcl">-count <replaceable>n</replaceable></optional> <optional role="tcl">-array <replaceable>name</replaceable></optional> <replaceable>command</replaceable> <optional role="tcl"><replaceable>loop-body</replaceable></optional></literal></term>
-      <listitem>
-       <para>
-        Executes an SQL command given as a string.  An error in the command
-        causes an error to be raised.  Otherwise, the return value of <function>spi_exec</function>
-        is the number of rows processed (selected, inserted, updated, or
-        deleted) by the command, or zero if the command is a utility
-        statement.  In addition, if the command is a <command>SELECT</> statement, the
-        values of the selected columns are placed in Tcl variables as
-        described below.
-       </para>
-       <para>
-        The optional <literal>-count</> value tells
-        <function>spi_exec</function> the maximum number of rows
-        to process in the command.  The effect of this is comparable to
-        setting up a query as a cursor and then saying <literal>FETCH <replaceable>n</></>.
-       </para>
-       <para>
-        If the command is a <command>SELECT</> statement, the values of the
-        result columns are placed into Tcl variables named after the columns.
-        If the <literal>-array</> option is given, the column values are
-        instead stored into the named associative array, with the
-        column names used as array indexes.
-       </para>
-       <para>
-        If the command is a <command>SELECT</> statement and no <replaceable>loop-body</>
-        script is given, then only the first row of results are stored into
-        Tcl variables; remaining rows, if any, are ignored.  No storing occurs
-        if the
-        query returns no rows.  (This case can be detected by checking the
-        result of <function>spi_exec</function>.)  For example:
-<programlisting>
-spi_exec "SELECT count(*) AS cnt FROM pg_proc"
-</programlisting>
-
-        will set the Tcl variable <literal>$cnt</> to the number of rows in
-        the <structname>pg_proc</> system catalog.
-       </para>
-       <para>
-        If the optional <replaceable>loop-body</> argument is given, it is
-        a piece of Tcl script that is executed once for each row in the
-        query result.  (<replaceable>loop-body</> is ignored if the given
-        command is not a <command>SELECT</>.)  The values of the current row's columns
-        are stored into Tcl variables before each iteration.  For example:
-
-<programlisting>
-spi_exec -array C "SELECT * FROM pg_class" {
-    elog DEBUG "have table $C(relname)"
-}
-</programlisting>
-
-        will print a log message for every row of <literal>pg_class</>.  This
-        feature works similarly to other Tcl looping constructs; in
-        particular <literal>continue</> and <literal>break</> work in the
-        usual way inside the loop body.
-       </para>
-       <para>
-        If a column of a query result is null, the target
-        variable for it is <quote>unset</> rather than being set.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>spi_prepare</function> <replaceable>query</replaceable> <replaceable>typelist</replaceable></term>
-<!## PG>
-<!-- NOTICE:
-     PREPARE not supported yet
--->
-      <listitem>
-       <para>
-        Prepares and saves a query plan for later execution.  The
-        saved plan will be retained for the life of the current
-        session.<indexterm><primary>preparing a query</>
-        <secondary>in PL/Tcl</></>
-       </para>
-       <para>
-        The query can use parameters, that is, placeholders for
-        values to be supplied whenever the plan is actually executed.
-        In the query string, refer to parameters
-        by the symbols <literal>$1</literal> ... <literal>$<replaceable>n</replaceable></literal>.
-        If the query uses parameters, the names of the parameter types
-        must be given as a Tcl list.  (Write an empty list for
-        <replaceable>typelist</replaceable> if no parameters are used.)
-       </para>
-       <para>
-        The return value from <function>spi_prepare</function> is a query ID
-        to be used in subsequent calls to <function>spi_execp</function>. See
-        <function>spi_execp</function> for an example.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-<!## XC>
-      <listitem>
-       <para>
-        <productname>Postgres-XC</> does not
-        support <command>PREPARE</> reature yet.  This will be
-        supported in the future releases.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-<!## XL>
-      <listitem>
-       <para>
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-
-     <varlistentry>
-      <term><literal><function>spi_execp</> <optional role="tcl">-count <replaceable>n</replaceable></optional> <optional role="tcl">-array <replaceable>name</replaceable></optional> <optional role="tcl">-nulls <replaceable>string</replaceable></optional> <replaceable>queryid</replaceable> <optional role="tcl"><replaceable>value-list</replaceable></optional> <optional role="tcl"><replaceable>loop-body</replaceable></optional></literal></term>
-<!## PG>
-<!-- NOTICE:
-     Prepare not supported yet.
--->
-      <listitem>
-       <para>
-        Executes a query previously prepared with <function>spi_prepare</>.
-        <replaceable>queryid</replaceable> is the ID returned by
-        <function>spi_prepare</>.  If the query references parameters,
-        a <replaceable>value-list</replaceable> must be supplied.  This
-        is a Tcl list of actual values for the parameters.  The list must be
-        the same length as the parameter type list previously given to
-        <function>spi_prepare</>.  Omit <replaceable>value-list</replaceable>
-        if the query has no parameters.
-       </para>
-       <para>
-        The optional value for <literal>-nulls</> is a string of spaces and
-        <literal>'n'</> characters telling <function>spi_execp</function>
-        which of the parameters are null values. If given, it must have exactly the
-        same length as the <replaceable>value-list</replaceable>.  If it
-        is not given, all the parameter values are nonnull.
-       </para>
-       <para>
-        Except for the way in which the query and its parameters are specified,
-        <function>spi_execp</> works just like <function>spi_exec</>.
-        The <literal>-count</>, <literal>-array</>, and
-        <replaceable>loop-body</replaceable> options are the same,
-        and so is the result value.
-       </para>
-       <para>
-        Here's an example of a PL/Tcl function using a prepared plan:
-
-<programlisting>
-CREATE FUNCTION t1_count(integer, integer) RETURNS integer AS $$
-    if {![ info exists GD(plan) ]} {
-        # prepare the saved plan on the first call
-        set GD(plan) [ spi_prepare \
-                "SELECT count(*) AS cnt FROM t1 WHERE num &gt;= \$1 AND num &lt;= \$2" \
-                [ list int4 int4 ] ]
-    }
-    spi_execp -count 1 $GD(plan) [ list $1 $2 ]
-    return $cnt
-$$ LANGUAGE pltcl;
-</programlisting>
-
-        We need backslashes inside the query string given to
-        <function>spi_prepare</> to ensure that the
-        <literal>$<replaceable>n</replaceable></> markers will be passed
-        through to <function>spi_prepare</> as-is, and not replaced by Tcl
-        variable substitution.
-
-       </para>
-      </listitem>
-<!## end>
-<!## XC>
-      <listitem>
-&xconly;
-       <para>
-        <productname>Postgres-XC</> does not
-        support <command>PREPARE</> in the current release.  This may
-        be supported in the future releases.
-       </para>
-      </listitem>
-<!## end>
-<!## XL>
-      <listitem>
-       <para>
-       </para>
-      </listitem>
-<!## end>
-     </varlistentry>
-
-     <varlistentry>
-      <indexterm>
-       <primary>spi_lastoid</primary>
-      </indexterm>
-      <term><function>spi_lastoid</></term>
-      <listitem>
-       <para>
-        Returns the OID of the row inserted by the last
-        <function>spi_exec</> or <function>spi_execp</>, if the
-        command was a single-row <command>INSERT</> and the modified
-        table contained OIDs.  (If not, you get zero.)
-       </para>
-<!## XC>
-&xconly;
-       <para>
-        Please note that OID is maintained locally at each Datanode
-        and Coordinator.
-       </para>
-<!## end>
-<!## XL>
-&xlonly;
-       <para>
-        Please note that OID is maintained locally at each Datanode
-        and Coordinator, and cannot be used globally throughout the cluster.
-       </para>
-<!## end>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>quote</> <replaceable>string</replaceable></term>
-      <listitem>
-       <para>
-        Doubles all occurrences of single quote and backslash characters
-        in the given string.  This can be used to safely quote strings
-        that are to be inserted into SQL commands given
-        to <function>spi_exec</function> or
-        <function>spi_prepare</function>.
-        For example, think about an SQL command string like:
-
-<programlisting>
-"SELECT '$val' AS ret"
-</programlisting>
-
-        where the Tcl variable <literal>val</> actually contains
-        <literal>doesn't</literal>. This would result
-        in the final command string:
-
-<programlisting>
-SELECT 'doesn't' AS ret
-</programlisting>
-
-        which would cause a parse error during
-        <function>spi_exec</function> or
-        <function>spi_prepare</function>.
-        To work properly, the submitted command should contain:
-
-<programlisting>
-SELECT 'doesn''t' AS ret
-</programlisting>
-
-        which can be formed in PL/Tcl using:
-
-<programlisting>
-"SELECT '[ quote $val ]' AS ret"
-</programlisting>
-
-        One advantage of <function>spi_execp</function> is that you don't
-        have to quote parameter values like this, since the parameters are never
-        parsed as part of an SQL command string.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <indexterm>
-       <primary>elog</primary>
-       <secondary>in PL/Tcl</secondary>
-      </indexterm>
-      <term><function>elog</> <replaceable>level</replaceable> <replaceable>msg</replaceable></term>
-      <listitem>
-       <para>
-        Emits a log or error message. Possible levels are
-        <literal>DEBUG</>, <literal>LOG</>, <literal>INFO</>,
-        <literal>NOTICE</>, <literal>WARNING</>, <literal>ERROR</>, and
-        <literal>FATAL</>. <literal>ERROR</>
-        raises an error condition; if this is not trapped by the surrounding
-        Tcl code, the error propagates out to the calling query, causing
-        the current transaction or subtransaction to be aborted.  This
-        is effectively the same as the Tcl <literal>error</> command.
-        <literal>FATAL</> aborts the transaction and causes the current
-        session to shut down.  (There is probably no good reason to use
-        this error level in PL/Tcl functions, but it's provided for
-        completeness.)  The other levels only generate messages of different
-        priority levels.
-        Whether messages of a particular priority are reported to the client,
-        written to the server log, or both is controlled by the
-        <xref linkend="guc-log-min-messages"> and
-        <xref linkend="guc-client-min-messages"> configuration
-        variables. See <xref linkend="runtime-config"> for more
-        information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-    </para>
-
-   </sect1>
-
-   <sect1 id="pltcl-trigger">
-    <title>Trigger Procedures in PL/Tcl</title>
-
-    <indexterm>
-     <primary>trigger</primary>
-     <secondary>in PL/Tcl</secondary>
-    </indexterm>
-<!## PG>
-<!-- NOTICE:
-     No Trigger yet!
--->
-    <para>
-     Trigger procedures can be written in PL/Tcl.
-<!## PG>
-     <productname>PostgreSQL</productname> requires that a procedure that is to be called
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> requires that a procedure that is to be called
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> requires that a procedure that is to be called
-<!## end>
-     as a trigger must be declared as a function with no arguments
-     and a return type of <literal>trigger</>.
-    </para>
-    <para>
-     The information from the trigger manager is passed to the procedure body
-     in the following variables:
-
-     <variablelist>
-
-      <varlistentry>
-       <term><varname>$TG_name</varname></term>
-       <listitem>
-        <para>
-         The name of the trigger from the <command>CREATE TRIGGER</command> statement.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>$TG_relid</varname></term>
-       <listitem>
-        <para>
-         The object ID of the table that caused the trigger procedure
-         to be invoked.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>$TG_table_name</varname></term>
-       <listitem>
-        <para>
-         The name of the table that caused the trigger procedure
-         to be invoked.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>$TG_table_schema</varname></term>
-       <listitem>
-        <para>
-         The schema of the table that caused the trigger procedure
-         to be invoked.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>$TG_relatts</varname></term>
-       <listitem>
-        <para>
-         A Tcl list of the table column names, prefixed with an empty list
-         element. So looking up a column name in the list with <application>Tcl</>'s
-         <function>lsearch</> command returns the element's number starting
-         with 1 for the first column, the same way the columns are customarily
-<!## PG>
-         numbered in <productname>PostgreSQL</productname>.  (Empty list
-<!## end>
-<!## XC>
-         numbered in <productname>Postgres-XC</productname>.  (Empty list
-<!## end>
-<!## XL>
-         numbered in <productname>Postgres-XL</productname>.  (Empty list
-<!## end>
-         elements also appear in the positions of columns that have been
-         dropped, so that the attribute numbering is correct for columns
-         to their right.)
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>$TG_when</varname></term>
-       <listitem>
-        <para>
-         The string <literal>BEFORE</>, <literal>AFTER</>, or
-         <literal>INSTEAD OF</>, depending on the type of trigger event.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>$TG_level</varname></term>
-       <listitem>
-        <para>
-         The string <literal>ROW</> or <literal>STATEMENT</> depending on the
-         type of trigger event.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>$TG_op</varname></term>
-       <listitem>
-        <para>
-         The string <literal>INSERT</>, <literal>UPDATE</>,
-         <literal>DELETE</>, or <literal>TRUNCATE</> depending on the type of
-         trigger event.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>$NEW</varname></term>
-       <listitem>
-        <para>
-         An associative array containing the values of the new table
-         row for <command>INSERT</> or <command>UPDATE</> actions, or
-         empty for <command>DELETE</>.  The array is indexed by column
-         name.  Columns that are null will not appear in the array.
-         This is not set for statement-level triggers.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>$OLD</varname></term>
-       <listitem>
-        <para>
-         An associative array containing the values of the old table
-         row for <command>UPDATE</> or <command>DELETE</> actions, or
-         empty for <command>INSERT</>.  The array is indexed by column
-         name.  Columns that are null will not appear in the array.
-         This is not set for statement-level triggers.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><varname>$args</varname></term>
-       <listitem>
-        <para>
-         A Tcl list of the arguments to the procedure as given in the
-         <command>CREATE TRIGGER</command> statement. These arguments are also accessible as
-         <literal>$1</literal> ... <literal>$<replaceable>n</replaceable></literal> in the procedure body.
-        </para>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-    </para>
-
-    <para>
-     The return value from a trigger procedure can be one of the strings
-     <literal>OK</> or <literal>SKIP</>, or a list as returned by the
-     <literal>array get</> Tcl command. If the return value is <literal>OK</>,
-     the operation (<command>INSERT</>/<command>UPDATE</>/<command>DELETE</>) that fired the trigger will proceed
-     normally. <literal>SKIP</> tells the trigger manager to silently suppress
-     the operation for this row. If a list is returned, it tells PL/Tcl to
-     return a modified row to the trigger manager. This is only meaningful
-     for row-level <literal>BEFORE</> <command>INSERT</> or <command>UPDATE</>
-     triggers for which the modified row will be inserted instead of the one
-     given in <varname>$NEW</>; or for row-level <literal>INSTEAD OF</>
-     <command>INSERT</> or <command>UPDATE</> triggers where the returned row
-     is used to support <command>INSERT RETURNING</> and
-     <command>UPDATE RETURNING</> commands. The return value is ignored for
-     other types of triggers.
-    </para>
-
-    <para>
-     Here's a little example trigger procedure that forces an integer value
-     in a table to keep track of the number of updates that are performed on the
-     row. For new rows inserted, the value is initialized to 0 and then
-     incremented on every update operation.
-
-<programlisting>
-CREATE FUNCTION trigfunc_modcount() RETURNS trigger AS $$
-    switch $TG_op {
-        INSERT {
-            set NEW($1) 0
-        }
-        UPDATE {
-            set NEW($1) $OLD($1)
-            incr NEW($1)
-        }
-        default {
-            return OK
-        }
-    }
-    return [array get NEW]
-$$ LANGUAGE pltcl;
-
-CREATE TABLE mytab (num integer, description text, modcnt integer);
-
-CREATE TRIGGER trig_mytab_modcount BEFORE INSERT OR UPDATE ON mytab
-    FOR EACH ROW EXECUTE PROCEDURE trigfunc_modcount('modcnt');
-</programlisting>
-
-     Notice that the trigger procedure itself does not know the column
-     name; that's supplied from the trigger arguments.  This lets the
-     trigger procedure be reused with different tables.
-    </para>
-<!## end>
-<!## XC>
-&xconly;
-    <para>
-     Trigger is not supported in the current release
-     of <productname>Postgres-XC</>.  This may be supported in the
-     future releases.
-    </para>
-<!## end>
-<!## XL>
-&xlonly;
-    <para>
-     Trigger is not supported in the current release
-     of <productname>Postgres-XL</>.  This may be supported in the
-     future releases.
-    </para>
-<!## end>
-   </sect1>
-
-   <sect1 id="pltcl-unknown">
-       <title>Modules and the <function>unknown</> Command</title>
-&common;
-       <para>
-        PL/Tcl has support for autoloading Tcl code when used.
-        It recognizes a special table, <literal>pltcl_modules</>, which
-        is presumed to contain modules of Tcl code.  If this table
-        exists, the module <literal>unknown</> is fetched from the table
-        and loaded into the Tcl interpreter immediately before the first
-        execution of a PL/Tcl function in a database session.  (This
-        happens separately for each Tcl interpreter, if more than one is
-        used in a session; see <xref linkend="pltcl-global">.)
-       </para>
-       <para>
-        While the <literal>unknown</> module could actually contain any
-        initialization script you need, it normally defines a Tcl
-        <function>unknown</> procedure that is invoked whenever Tcl does
-        not recognize an invoked procedure name.  <application>PL/Tcl</>'s standard version
-        of this procedure tries to find a module in <literal>pltcl_modules</>
-        that will define the required procedure.  If one is found, it is
-        loaded into the interpreter, and then execution is allowed to
-        proceed with the originally attempted procedure call.  A
-        secondary table <literal>pltcl_modfuncs</> provides an index of
-        which functions are defined by which modules, so that the lookup
-        is reasonably quick.
-       </para>
-       <para>
-<!## PG>
-        The <productname>PostgreSQL</productname> distribution includes
-<!## end>
-<!## XC>
-        The <productname>Postgres-XC</productname> distribution includes
-<!## end>
-<!## XL>
-        The <productname>Postgres-XL</productname> distribution includes
-<!## end>
-        support scripts to maintain these tables:
-        <command>pltcl_loadmod</>, <command>pltcl_listmod</>,
-        <command>pltcl_delmod</>, as well as source for the standard
-        <literal>unknown</> module in <filename>share/unknown.pltcl</>.  This module
-        must be loaded
-        into each database initially to support the autoloading mechanism.
-       </para>
-       <para>
-        The tables <literal>pltcl_modules</> and <literal>pltcl_modfuncs</>
-        must be readable by all, but it is wise to make them owned and
-        writable only by the database administrator.  As a security
-        precaution, PL/Tcl will ignore <literal>pltcl_modules</> (and thus,
-        not attempt to load the <literal>unknown</> module) unless it is
-        owned by a superuser.  But update privileges on this table can be
-        granted to other users, if you trust them sufficiently.
-       </para>
-   </sect1>
-
-   <sect1 id="pltcl-procnames">
-    <title>Tcl Procedure Names</title>
-
-&common;
-    <para>
-<!## PG>
-     In <productname>PostgreSQL</productname>, the same function name can be used for
-<!## end>
-<!## XC>
-     In <productname>Postgres-XC</productname>, the same function name can be used for
-<!## end>
-<!## XL>
-     In <productname>Postgres-XL</productname>, the same function name can be used for
-<!## end>
-     different function definitions as long as the number of arguments or their types
-     differ. Tcl, however, requires all procedure names to be distinct.
-     PL/Tcl deals with this by making the internal Tcl procedure names contain
-     the object
-     ID of the function from the system table <structname>pg_proc</> as part of their name. Thus,
-<!## PG>
-     <productname>PostgreSQL</productname> functions with the same name
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> functions with the same name
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> functions with the same name
-<!## end>
-     and different argument types will be different Tcl procedures, too.  This
-     is not normally a concern for a PL/Tcl programmer, but it might be visible
-     when debugging.
-    </para>
-
-   </sect1>
- </chapter>
diff --git a/doc-xc/src/sgml/postgres.sgmlin b/doc-xc/src/sgml/postgres.sgmlin
deleted file mode 100644
index b82f37657a..0000000000
--- a/doc-xc/src/sgml/postgres.sgmlin
+++ /dev/null
@@ -1,425 +0,0 @@
-<!-- doc/src/sgml/postgres.sgml -->
-
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.2//EN" [
-
-<!ENTITY % version SYSTEM "version.sgml">
-%version;
-<!ENTITY % filelist SYSTEM "filelist.sgml">
-%filelist;
-
-<!ENTITY reference  SYSTEM "reference.sgml">
-
-]>
-
-<book id="postgres">
-<!## PG>
- <title>PostgreSQL &version; Documentation</title>
-<!## end>
-<!## XC>
- <title>Postgres-XC &version; Documentation</title>
-<!## end>
-<!## XL>
- <title>Postgres-XL &version; Documentation</title>
-<!## end>
-
- <bookinfo>
-<!## PG>
-  <corpauthor>The PostgreSQL Global Development Group</corpauthor>
-  <productname>PostgreSQL</productname>
-  <productnumber>&version;</productnumber>
-<!## end>
-<!## XC>
-  <corpauthor>The Postgres-XC Development Group</corpauthor>
-  <productname>Postgres-XC</productname>
-  <productnumber>&version;</productnumber>
-<!## end>
-<!## XL>
-  <corpauthor>The Postgres-XL Development Group</corpauthor>
-  <productname>Postgres-XL</productname>
-  <productnumber>&version;</productnumber>
-<!## end>
-  &legal;
- </bookinfo>
-
- &intro;
-
- <part id="tutorial">
-  <title>Tutorial</title>
-
-  <partintro>
-
-
-   <para>
-<!## PG>
-    Welcome to the <productname>PostgreSQL</productname> Tutorial.  The
-    following few chapters are intended to give a simple introduction
-    to <productname>PostgreSQL</productname>, relational database
-    concepts, and the SQL language to those who are new to any one of
-    these aspects.  We only assume some general knowledge about how to
-    use computers.  No particular Unix or programming experience is
-    required.  This part is mainly intended to give you some hands-on
-    experience with important aspects of the
-    <productname>PostgreSQL</productname> system.  It makes no attempt
-    to be a complete or thorough treatment of the topics it covers.
-<!## end>
-<!## XC>
-&common;
-    Welcome to the <productname>Postgres-XC</productname> Tutorial.  The
-    following few chapters are intended to give a simple introduction
-    to <productname>Postgres-XC</productname>, relational database
-    concepts, and the SQL language to those who are new to any one of
-    these aspects.  We only assume some general knowledge about how to
-    use computers.  No particular Unix or programming experience is
-    required.  This part is mainly intended to give you some hands-on
-    experience with important aspects of the
-    <productname>Postgres-XC</productname> system.  It makes no attempt
-    to be a complete or thorough treatment of the topics it covers.
-<!## end>
-<!## XL>
-&common;
-    Welcome to the <productname>Postgres-XL</productname> Tutorial.  The
-    following few chapters are intended to give a simple introduction
-    to <productname>Postgres-XL</productname>, relational database
-    concepts, and the SQL language to those who are new to any one of
-    these aspects.  We only assume some general knowledge about how to
-    use computers.  No particular Unix or programming experience is
-    required.  This part is mainly intended to give you some hands-on
-    experience with important aspects of the
-    <productname>Postgres-XL</productname> system.  It makes no attempt
-    to be a complete or thorough treatment of the topics it covers.
-<!## end>
-   </para>
-
-   <para>
-<!## PG>
-    After you have worked through this tutorial you might want to move
-    on to reading <xref linkend="sql"> to gain a more formal knowledge
-    of the SQL language, or <xref linkend="client-interfaces"> for
-    information about developing applications for
-    <productname>PostgreSQL</productname>.  Those who set up and
-    manage their own server should also read <xref linkend="admin">.
-<!## end>
-<!## XC>
-    After you have worked through this tutorial you might want to move
-    on to reading <xref linkend="sql"> to gain a more formal knowledge
-    of the SQL language, or <xref linkend="client-interfaces"> for
-    information about developing applications for
-    <productname>Postgres-XC</productname>.  Those who set up and
-    manage their own server should also read <xref linkend="admin">.
-<!## end>
-<!## XL>
-    After you have worked through this tutorial you might want to move
-    on to reading <xref linkend="sql"> to gain a more formal knowledge
-    of the SQL language, or <xref linkend="client-interfaces"> for
-    information about developing applications for
-    <productname>Postgres-XL</productname>.  Those who set up and
-    manage their own server should also read <xref linkend="admin">.
-<!## end>
-   </para>
-  </partintro>
-
-  &start;
-  &query;
-  &advanced;
-
- </part>
-
- <part id="sql">
-  <title>The SQL Language</title>
-
-  <partintro>
-
-&common;
-   <para>
-<!## PG>
-    This part describes the use of the <acronym>SQL</acronym> language
-    in <productname>PostgreSQL</productname>.  We start with
-    describing the general syntax of <acronym>SQL</acronym>, then
-    explain how to create the structures to hold data, how to populate
-    the database, and how to query it.  The middle part lists the
-    available data types and functions for use in
-    <acronym>SQL</acronym> commands.  The rest treats several
-    aspects that are important for tuning a database for optimal
-    performance.
-<!## end>
-<!## XC>
-    This part describes the use of the <acronym>SQL</acronym> language
-    in <productname>Postgres-XC</productname>, inherited from <productname>PostgreSQL</>.  We start with
-    describing the general syntax of <acronym>SQL</acronym>, then
-    explain how to create the structures to hold data, how to populate
-    the database, and how to query it.  The middle part lists the
-    available data types and functions for use in
-    <acronym>SQL</acronym> commands.  The rest treats several
-    aspects that are important for tuning a database for optimal
-    performance.
-<!## end>
-<!## XL>
-    This part describes the use of the <acronym>SQL</acronym> language
-    in <productname>Postgres-XL</productname>, inherited from <productname>PostgreSQL</>.  We start with
-    describing the general syntax of <acronym>SQL</acronym>, then
-    explain how to create the structures to hold data, how to populate
-    the database, and how to query it.  The middle part lists the
-    available data types and functions for use in
-    <acronym>SQL</acronym> commands.  The rest treats several
-    aspects that are important for tuning a database for optimal
-    performance.
-<!## end>
-   </para>
-
-   <para>
-    The information in this part is arranged so that a novice user can
-    follow it start to end to gain a full understanding of the topics
-    without having to refer forward too many times.  The chapters are
-    intended to be self-contained, so that advanced users can read the
-    chapters individually as they choose.  The information in this
-    part is presented in a narrative fashion in topical units.
-    Readers looking for a complete description of a particular command
-    should see <xref linkend="reference">.
-   </para>
-
-   <para>
-<!## PG>
-    Readers of this part should know how to connect to a
-    <productname>PostgreSQL</> database and issue
-    <acronym>SQL</acronym> commands.  Readers that are unfamiliar with
-    these issues are encouraged to read <xref linkend="tutorial">
-    first.  <acronym>SQL</acronym> commands are typically entered
-    using the <productname>PostgreSQL</> interactive terminal
-    <application>psql</application>, but other programs that have
-    similar functionality can be used as well.
-<!## end>
-<!## XC>
-    Readers of this part should know how to connect to a
-    <productname>Postgres-XC</> database and issue
-    <acronym>SQL</acronym> commands.  Readers that are unfamiliar with
-    these issues are encouraged to read <xref linkend="tutorial">
-    first.  <acronym>SQL</acronym> commands are typically entered
-    using the <productname>Postgres-XC</> interactive terminal
-    <application>psql</application>, but other programs that have
-    similar functionality can be used as well.
-<!## end>
-<!## XL>
-    Readers of this part should know how to connect to a
-    <productname>Postgres-XL</> database and issue
-    <acronym>SQL</acronym> commands.  Readers that are unfamiliar with
-    these issues are encouraged to read <xref linkend="tutorial">
-    first.  <acronym>SQL</acronym> commands are typically entered
-    using the <productname>Postgres-XL</> interactive terminal
-    <application>psql</application>, but other programs that have
-    similar functionality can be used as well.
-<!## end>
-   </para>
-  </partintro>
-
-  &syntax;
-  &ddl;
-  &dml;
-  &queries;
-  &datatype;
-  &func;
-  &typeconv;
-  &indices;
-  &textsearch;
-  &mvcc;
-  &perform;
-
- </part>
-
- <part id="admin">
-  <title>Server Administration</title>
-
-  <partintro>
-
-<!## PG>
-   <para>
-    This part covers topics that are of interest to a
-    <productname>PostgreSQL</> database administrator.  This includes
-    installation of the software, set up and configuration of the
-    server, management of users and databases, and maintenance tasks.
-    Anyone who runs a <productname>PostgreSQL</> server, even for
-    personal use, but especially in production, should be familiar
-    with the topics covered in this part.
-   </para>
-<!## end>
-<!## XC>
-&xconly;
-   <para>
-    This part covers topics that are of interest to a
-    <productname>Postgres-XC</> database administrator.  This includes
-    installation of the software, set up and configuration of the
-    servers, management of users and databases, and maintenance tasks.
-    Anyone who runs a <productname>Postgres-XC</> servers, even for
-    personal use, but especially in production, should be familiar
-    with the topics covered in this part.
-   </para>
-<!## end>
-<!## XL>
-   <para>
-    This part covers topics that are of interest to a
-    <productname>Postgres-XL</> database administrator.  This includes
-    installation of the software, set up and configuration of the
-    servers, management of users and databases, and maintenance tasks.
-    Anyone who runs a <productname>Postgres-XL</> servers, even for
-    personal use, but especially in production, should be familiar
-    with the topics covered in this part.
-   </para>
-<!## end>
-
-   <para>
-    The information in this part is arranged approximately in the
-    order in which a new user should read it.  But the chapters are
-    self-contained and can be read individually as desired.  The
-    information in this part is presented in a narrative fashion in
-    topical units.  Readers looking for a complete description of a
-    particular command should see <xref linkend="reference">.
-   </para>
-
-   <para>
-    The first few chapters are written so they can be understood
-    without prerequisite knowledge, so new users who need to set
-    up their own server can begin their exploration with this part.
-    The rest of this part is about tuning and management; that material
-    assumes that the reader is familiar with the general use of
-    the <productname>PostgreSQL</> database system.  Readers are
-    encouraged to look at <xref linkend="tutorial"> and <xref
-    linkend="sql"> for additional information.
-   </para>
-  </partintro>
-
-  &installation;
-<!## PG>
-  &installw;
-<!## end>
-  &runtime;
-  &config;
-  &client-auth;
-  &user-manag;
-  &manage-ag;
-  &charset;
-  &maintenance;
-  &backup;
-  &high-availability;
-  &recovery-config;
-  &monitoring;
-  &diskusage;
-  &wal;
-  &regress;
-  &add-node;
-  &remove-node;
- </part>
-
- <part id="client-interfaces">
-  <title>Client Interfaces</title>
-
-  <partintro>
-
-&pgnotice;
-
-   <para>
-    This part describes the client programming interfaces distributed
-    with <productname>PostgreSQL</>.  Each of these chapters can be
-    read independently.  Note that there are many other programming
-    interfaces for client programs that are distributed separately and
-    contain their own documentation (<xref linkend="external-projects">
-    lists some of the more popular ones).  Readers of this part should be
-    familiar with using <acronym>SQL</acronym> commands to manipulate
-    and query the database (see <xref linkend="sql">) and of course
-    with the programming language that the interface uses.
-   </para>
-  </partintro>
-
-  &libpq;
-  &lobj;
-  &ecpg;
-  &infoschema;
-
- </part>
-
- <part id="server-programming">
-  <title>Server Programming</title>
-
-  <partintro>
-
-&pgnotice;
-
-   <para>
-    This part is about extending the server functionality with
-    user-defined functions, data types, triggers, etc.  These are
-    advanced topics which should probably be approached only after all
-    the other user documentation about <productname>PostgreSQL</> has
-    been understood.  Later chapters in this part describe the server-side
-    programming languages available in the
-    <productname>PostgreSQL</productname> distribution as well as
-    general issues concerning server-side programming languages.  It
-    is essential to read at least the earlier sections of <xref
-    linkend="extend"> (covering functions) before diving into the
-    material about server-side programming languages.
-   </para>
-  </partintro>
-
-  &extend;
-  &trigger;
-  &rules;
-
-  &xplang;
-  &plsql;
-  &pltcl;
-  &plperl;
-  &plpython;
-
-  &spi;
-
- </part>
-
- &reference;
-
- <part id="internals">
-  <title>Internals</title>
-
-  <partintro>
-
-&pgnotice;
-
-   <para>
-    This part contains assorted information that might be of use to
-    <productname>PostgreSQL</> developers.
-   </para>
-  </partintro>
-
-  &arch-dev;
-  &catalogs;
-  &protocol;
-  &sources;
-  &nls;
-  &plhandler;
-  &fdwhandler;
-  &geqo;
-  &indexam;
-  &gist;
-  &gin;
-  &storage;
-  &bki;
-  &planstats;
-
- </part>
-
- <part id="appendixes">
-  <title>Appendixes</title>
-
-  &errcodes;
-  &datetime;
-  &keywords;
-  &features;
-  &release;
-  &contrib;
-  &external-projects;
-  &sourcerepo;
-  &docguide;
-  &acronyms;
-
- </part>
-
- &biblio;
- <![%include-index;[&bookindex;]]>
-
-</book>
diff --git a/doc-xc/src/sgml/problems.sgmlin b/doc-xc/src/sgml/problems.sgmlin
deleted file mode 100644
index 65bb6f0498..0000000000
--- a/doc-xc/src/sgml/problems.sgmlin
+++ /dev/null
@@ -1,603 +0,0 @@
-<!-- doc/src/sgml/problems.sgml -->
-
-<sect1 id="bug-reporting">
- <title>Bug Reporting Guidelines</title>
-
- <para>
-<!## PG>
-  When you find a bug in <productname>PostgreSQL</productname> we want to
-  hear about it. Your bug reports play an important part in making
-  <productname>PostgreSQL</productname> more reliable because even the utmost
-  care cannot guarantee that every part of
-  <productname>PostgreSQL</productname>
-  will work on every platform under every circumstance.
-<!## end>
-<!## XC>
-&xconly;
-  When you find a bug in <productname>Postgres-XC</productname> we want to
-  hear about it. Your bug reports play an important part in making
-  <productname>Postgres-XC</productname> more reliable because even the utmost
-  care cannot guarantee that every part of
-  <productname>Postgres-XC</productname> 
-  will work on every platform under every circumstance.
-<!## end>
-<!## XL>
-&xlonly;
-  When you find a bug in <productname>Postgres-XL</productname> we want to
-  hear about it. Your bug reports play an important part in making
-  <productname>Postgres-XL</productname> more reliable because even the utmost
-  care cannot guarantee that every part of
-  <productname>Postgres-XL</productname> 
-  will work on every platform under every circumstance.
-<!## end>
- </para>
-
- <para>
-  The following suggestions are intended to assist you in forming bug reports
-  that can be handled in an effective fashion. No one is required to follow
-  them but doing so tends to be to everyone's advantage.
- </para>
-
- <para>
-  We cannot promise to fix every bug right away. If the bug is obvious, critical,
-  or affects a lot of users, chances are good that someone will look into it. It
-  could also happen that we tell you to update to a newer version to see if the
-  bug happens there. Or we might decide that the bug
-  cannot be fixed before some major rewrite we might be planning is done. Or
-  perhaps it is simply too hard and there are more important things on the agenda.
-  If you need help immediately, consider obtaining a commercial support contract.
- </para>
-
- <sect2>
-  <title>Identifying Bugs</title>
-  <para>
-   Before you report a bug, please read and re-read the
-   documentation to verify that you can really do whatever it is you are
-   trying. If it is not clear from the documentation whether you can do
-   something or not, please report that too; it is a bug in the documentation.
-   If it turns out that a program does something different from what the
-   documentation says, that is a bug. That might include, but is not limited to,
-   the following circumstances:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      A program terminates with a fatal signal or an operating system
-      error message that would point to a problem in the program. (A
-      counterexample might be a <quote>disk full</quote> message,
-      since you have to fix that yourself.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A program produces the wrong output for any given input.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A program refuses to accept valid input (as defined in the documentation).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A program accepts invalid input without a notice or error message.
-      But keep in mind that your idea of invalid input might be our idea of
-      an extension or compatibility with traditional practice.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-<!## PG>
-      <productname>PostgreSQL</productname> fails to compile, build, or
-      install according to the instructions on supported platforms.
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname> fails to compile, build, or
-      install according to the instructions on supported platforms.
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname> fails to compile, build, or
-      install according to the instructions on supported platforms.
-<!## end>
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   Here <quote>program</quote> refers to any executable, not only the backend process.
-  </para>
-
-  <para>
-   Being slow or resource-hogging is not necessarily a bug. Read the
-   documentation or ask on one of the mailing lists for help in tuning your
-   applications. Failing to comply to the <acronym>SQL</acronym> standard is
-   not necessarily a bug either, unless compliance for the
-   specific feature is explicitly claimed.
-  </para>
-
-<!## PG>
-  <para>
-   Before you continue, check on the TODO list and in the FAQ to see if your bug is
-   already known. If you cannot decode the information on the TODO list, report your
-   problem. The least we can do is make the TODO list clearer.
-  </para>
-<!## end>
- </sect2>
-
- <sect2>
-  <title>What to Report</title>
-
-  <para>
-   The most important thing to remember about bug reporting is to state all
-   the facts and only facts. Do not speculate what you think went wrong, what
-   <quote>it seemed to do</quote>, or which part of the program has a fault.
-   If you are not familiar with the implementation you would probably guess
-   wrong and not help us a bit. And even if you are, educated explanations are
-   a great supplement to but no substitute for facts. If we are going to fix
-   the bug we still have to see it happen for ourselves first.
-   Reporting the bare facts
-   is relatively straightforward (you can probably copy and paste them from the
-   screen) but all too often important details are left out because someone
-   thought it does not matter or the report would be understood
-   anyway.
-  </para>
-
-  <para>
-   The following items should be contained in every bug report:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      The exact sequence of steps <emphasis>from program
-      start-up</emphasis> necessary to reproduce the problem. This
-      should be self-contained; it is not enough to send in a bare
-      <command>SELECT</command> statement without the preceding
-      <command>CREATE TABLE</command> and <command>INSERT</command>
-      statements, if the output should depend on the data in the
-      tables. We do not have the time to reverse-engineer your
-      database schema, and if we are supposed to make up our own data
-      we would probably miss the problem.
-     </para>
-
-     <para>
-      The best format for a test case for SQL-related problems is a
-      file that can be run through the <application>psql</application>
-      frontend that shows the problem. (Be sure to not have anything
-      in your <filename>~/.psqlrc</filename> start-up file.)  An easy
-      way to create this file is to use <application>pg_dump</application>
-      to dump out the table declarations and data needed to set the
-      scene, then add the problem query.  You are encouraged to
-      minimize the size of your example, but this is not absolutely
-      necessary.  If the bug is reproducible, we will find it either
-      way.
-     </para>
-
-     <para>
-      If your application uses some other client interface, such as <application>PHP</>, then
-      please try to isolate the offending queries. We will probably not set up a
-      web server to reproduce your problem. In any case remember to provide
-      the exact input files; do not guess that the problem happens for
-      <quote>large files</quote> or <quote>midsize databases</quote>, etc. since this
-      information is too inexact to be of use.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The output you got. Please do not say that it <quote>didn't work</quote> or
-      <quote>crashed</quote>. If there is an error message,
-      show it, even if you do not understand it. If the program terminates with
-      an operating system error, say which. If nothing at all happens, say so.
-      Even if the result of your test case is a program crash or otherwise obvious
-      it might not happen on our platform. The easiest thing is to copy the output
-      from the terminal, if possible.
-     </para>
-     <note>
-      <para>
-       If you are reporting an error message, please obtain the most verbose
-       form of the message.  In <application>psql</>, say <literal>\set
-       VERBOSITY verbose</> beforehand.  If you are extracting the message
-       from the server log, set the run-time parameter
-       <xref linkend="guc-log-error-verbosity"> to <literal>verbose</> so that all
-       details are logged.
-      </para>
-     </note>
-     <note>
-      <para>
-       In case of fatal errors, the error message reported by the client might
-       not contain all the information available. Please also look at the
-       log output of the database server. If you do not keep your server's log
-       output, this would be a good time to start doing so.
-      </para>
-     </note>
-    </listitem>
-
-    <listitem>
-     <para>
-      The output you expected is very important to state. If you just write
-      <quote>This command gives me that output.</quote> or <quote>This is not
-      what I expected.</quote>, we might run it ourselves, scan the output, and
-      think it looks OK and is exactly what we expected. We should not have to
-      spend the time to decode the exact semantics behind your commands.
-      Especially refrain from merely saying that <quote>This is not what SQL says/Oracle
-      does.</quote> Digging out the correct behavior from <acronym>SQL</acronym>
-      is not a fun undertaking, nor do we all know how all the other relational
-      databases out there behave. (If your problem is a program crash, you can
-      obviously omit this item.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Any command line options and other start-up options, including
-      any relevant environment variables or configuration files that
-      you changed from the default. Again, please provide exact
-      information. If you are using a prepackaged distribution that
-      starts the database server at boot time, you should try to find
-      out how that is done.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Anything you did at all differently from the installation
-      instructions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-<!## PG>
-      The <productname>PostgreSQL</productname> version. You can run the command
-<!## end>
-<!## XC>
-      The <productname>Postgres-XC</productname> version. You can run the command
-<!## end>
-<!## XL>
-      The <productname>Postgres-XL</productname> version. You can run the command
-<!## end>
-      <literal>SELECT version();</literal> to
-      find out the version of the server you are connected to.  Most executable
-      programs also support a <option>--version</option> option; at least
-      <literal>postgres --version</literal> and <literal>psql --version</literal>
-      should work.
-      If the function or the options do not exist then your version is
-      more than old enough to warrant an upgrade.
-      If you run a prepackaged version, such as RPMs, say so, including any
-      subversion the package might have. If you are talking about a Git
-      snapshot, mention that, including the commit hash.
-     </para>
-
-     <para>
-<!## PG>
-      If your version is older than &version; we will almost certainly
-      tell you to upgrade. There are many bug fixes and improvements
-      in each new release, so it is quite possible that a bug you have
-      encountered in an older release of <productname>PostgreSQL</>
-      has already been fixed. We can only provide limited support for
-      sites using older releases of <productname>PostgreSQL</>; if you
-      require more than we can provide, consider acquiring a
-      commercial support contract.
-<!## end>
-<!## XC>
-      If your version is older than &version; we will almost certainly
-      tell you to upgrade. There are many bug fixes and improvements
-      in each new release, so it is quite possible that a bug you have
-      encountered in an older release of <productname>Postgres-XC</>
-      has already been fixed. We can only provide limited support for
-      sites using older releases of <productname>Postgres-XC</>; if you
-      require more than we can provide, consider acquiring a
-      commercial support contract.
-<!## end>
-<!## XL>
-      If your version is older than &version; we will almost certainly
-      tell you to upgrade. There are many bug fixes and improvements
-      in each new release, so it is quite possible that a bug you have
-      encountered in an older release of <productname>Postgres-XL</>
-      has already been fixed. We can only provide limited support for
-      sites using older releases of <productname>Postgres-XL</>; if you
-      require more than we can provide, consider acquiring a
-      commercial support contract.
-<!## end>
-     </para>
-     <para>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Platform information. This includes the kernel name and version,
-      C library, processor, memory information, and so on. In most
-      cases it is sufficient to report the vendor and version, but do
-      not assume everyone knows what exactly <quote>Debian</quote>
-      contains or that everyone runs on i386s. If you have
-      installation problems then information about the toolchain on
-      your machine (compiler, <application>make</application>, and so
-      on) is also necessary.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-<!## PG>
-   Do not be afraid if your bug report becomes rather lengthy. That is a fact of life.
-   It is better to report everything the first time than us having to squeeze the
-   facts out of you. On the other hand, if your input files are huge, it is
-   fair to ask first whether somebody is interested in looking into it.  Here is
-   an <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">article</ulink>
-   that outlines some more tips on reporting bugs.
-<!## end>
-<!## XC>
-   Do not be afraid if your bug report becomes rather lengthy. That is a fact of life.
-   It is better to report everything the first time than us having to squeeze the
-   facts out of you. On the other hand, if your input files are huge, it is
-   fair to ask first whether somebody is interested in looking into it.
-<!## end>
-<!## XL>
-   Do not be afraid if your bug report becomes rather lengthy. That is a fact of life.
-   It is better to report everything the first time than us having to squeeze the
-   facts out of you. On the other hand, if your input files are huge, it is
-   fair to ask first whether somebody is interested in looking into it.
-<!## end>
-  </para>
-
-  <para>
-   Do not spend all your time to figure out which changes in the input make
-   the problem go away. This will probably not help solving it. If it turns
-   out that the bug cannot be fixed right away, you will still have time to
-   find and share your work-around. Also, once again, do not waste your time
-   guessing why the bug exists. We will find that out soon enough.
-  </para>
-
-<!## PG>
-  <para>
-   When writing a bug report, please avoid confusing terminology.
-   The software package in total is called <quote>PostgreSQL</quote>,
-   sometimes <quote>Postgres</quote> for short. If you
-   are specifically talking about the backend process, mention that, do not
-   just say <quote>PostgreSQL crashes</quote>.  A crash of a single
-   backend process is quite different from crash of the parent
-   <quote>postgres</> process; please don't say <quote>the server
-   crashed</> when you mean a single backend process went down, nor vice versa.
-   Also, client programs such as the interactive frontend <quote><application>psql</application></quote>
-   are completely separate from the backend.  Please try to be specific
-   about whether the problem is on the client or server side.
-  </para>
-<!## end>
-<!## XC>
-  <para>
-   When writing a bug report, please avoid confusing terminology.
-   The software package in total is called <quote>Postgres-XC</quote>.
-                                                            If you
-   are specifically talking about the backend server, mention that, do not
-   just say <quote>Postgres-XC crashes</quote>.  
-   <quote>Postgres-XC</> consists of several separate component.   Please
-   write which component crashes.
-   A crash of a single
-   backend server process is quite different from crash of the parent
-   <quote>postgres</> process; please don't say <quote>the server
-   crashed</> when you mean a single backend process went down, nor vice versa.
-   Also, client programs such as the interactive frontend <quote><application>psql</application></quote>
-   are completely separate from the backend.  Please try to be specific
-   about whether the problem is on the client or server side.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   When writing a bug report, please avoid confusing terminology.
-   The software package in total is called <quote>Postgres-XL</quote>.
-                                                            If you
-   are specifically talking about the backend server, mention that, do not
-   just say <quote>Postgres-XL crashes</quote>.  
-   <quote>Postgres-XL</> consists of several separate component.   Please
-   write which component crashes.
-   A crash of a single
-   backend server process is quite different from crash of the parent
-   <quote>postgres</> process; please don't say <quote>the server
-   crashed</> when you mean a single backend process went down, nor vice versa.
-   Also, client programs such as the interactive frontend <quote><application>psql</application></quote>
-   are completely separate from the backend.  Please try to be specific
-   about whether the problem is on the client or server side.
-  </para>
-<!## end>
-
- </sect2>
-
- <sect2>
-  <title>Where to Report Bugs</title>
-
-  <para>
-<!## PG>
-   In general, send bug reports to the bug report mailing list at
-   <email>[email protected]</email>.
-   You are requested to use a descriptive subject for your email
-   message, perhaps parts of the error message.
-<!## end>
-<!## XC>
-&xconly;
-   In general, send bug reports to the bug report mailing list.
-  <footnote>
-   <para>
-   <email>[email protected]</email>
-   </para>
-   </footnote>
-   You are requested to use a descriptive subject for your email
-   message, perhaps parts of the error message.
-<!## end>
-<!## XL>
-&xlonly;
-   In general, send bug reports to the bug report mailing list.
-  <footnote>
-   <para>
-   <email>[email protected]</email>
-   </para>
-   </footnote>
-   You are requested to use a descriptive subject for your email
-   message, perhaps parts of the error message.
-<!## end>
-  </para>
-
-<!## PG>
-<!-- XC does not provide web-based bug reporting forms -->
-  <para>
-   Another method is to fill in the bug report web-form available
-   at the project's
-   <ulink url="http://www.postgresql.org/">web site</ulink>.
-   Entering a bug report this way causes it to be mailed to the
-   <email>[email protected]</email> mailing list.
-  </para>
-<!## end>
-
-<!## PG>
-<!-- XC does not have security bug entry point either -->
-  <para>
-   If your bug report has security implications and you'd prefer that it
-   not become immediately visible in public archives, don't send it to
-   <literal>pgsql-bugs</literal>.  Security issues can be
-   reported privately to <email>[email protected]</email>.
-  </para>
-<!## end>
-
-  <para>
-<!## PG>
-   Do not send bug reports to any of the user mailing lists, such as
-   <email>[email protected]</email> or
-   <email>[email protected]</email>.
-   These mailing lists are for answering
-   user questions, and their subscribers normally do not wish to receive
-   bug reports. More importantly, they are unlikely to fix them.
-<!## end>
-<!## XC>
-   Do not send bug reports to any of the user mailing lists.
-   <footnote>
-    <para>
-     <email>[email protected]</email>
-    </para>
-   </footnote>
-   These mailing lists are for answering
-   user questions, and their subscribers normally do not wish to receive
-   bug reports. More importantly, they are unlikely to fix them.
-<!## end>
-<!## XL>
-   Do not send bug reports to any of the user mailing lists.
-   <footnote>
-    <para>
-     <email>[email protected]</email>
-    </para>
-   </footnote>
-   These mailing lists are for answering
-   user questions, and their subscribers normally do not wish to receive
-   bug reports. More importantly, they are unlikely to fix them.
-<!## end>
-  </para>
-
-<!## PG>
-<!-- XC developers mailing list does not discourage to report bugs -->
-  <para>
-   Also, please do <emphasis>not</emphasis> send reports to
-   the developers' mailing list <email>[email protected]</email>.
-   This list is for discussing the
-   development of <productname>PostgreSQL</productname>, and it would be nice
-   if we could keep the bug reports separate. We might choose to take up a
-   discussion about your bug report on <literal>pgsql-hackers</literal>,
-   if the problem needs more review.
-  </para>
-<!## end>
-
-  <para>
-<!## PG>
-   If you have a problem with the documentation, the best place to report it
-   is the documentation mailing list <email>[email protected]</email>.
-   Please be specific about what part of the documentation you are unhappy
-   with.
-<!## end>
-<!## XC>
-   If you have a problem with the documentation, the best place to report it
-   is the documentation mailing list.
-   <footnote>
-    <para>
-     <email>[email protected]</email>
-    </para>
-   </footnote>
-   Please be specific about what part of the documentation you are unhappy
-   with.
-<!## end>
-<!## XL>
-   If you have a problem with the documentation, the best place to report it
-   is the documentation mailing list.
-   <footnote>
-    <para>
-     <email>[email protected]</email>
-    </para>
-   </footnote>
-   Please be specific about what part of the documentation you are unhappy
-   with.
-<!## end>
-  </para>
-
-  <para>
-<!## PG>
-   If your bug is a portability problem on a non-supported platform,
-   send mail to <email>[email protected]</email>,
-   so we (and you) can work on
-   porting <productname>PostgreSQL</productname> to your platform.
-<!## end>
-<!## XC>
-   If your bug is a portability problem on a non-supported platform,
-   send mail to the developers mailing list,
-   <footnote>
-    <para>
-     <email>[email protected]</email>
-    </para>
-   </footnote>
-   so we (and you) can work on
-   porting <productname>Postgres-XC</productname> to your platform.
-<!## end>
-<!## XL>
-   If your bug is a portability problem on a non-supported platform,
-   send mail to the developers mailing list,
-   <footnote>
-    <para>
-     <email>[email protected]</email>
-    </para>
-   </footnote>
-   so we (and you) can work on
-   porting <productname>Postgres-XL</productname> to your platform.
-<!## end>
-  </para>
-
-  <note>
-   <para>
-<!## PG>
-    Due to the unfortunate amount of spam going around, all of the above
-    email addresses are closed mailing lists. That is, you need to be
-    subscribed to a list to be allowed to post on it.  (You need not be
-    subscribed to use the bug-report web form, however.)
-    If you would like to send mail but do not want to receive list traffic,
-    you can subscribe and set your subscription option to <literal>nomail</>.
-    For more information send mail to
-    <email>[email protected]</email>
-    with the single word <literal>help</> in the body of the message.
-<!## end>
-<!## XC>
-    Due to the unfortunate amount of spam going around, all of the above
-    email addresses are closed mailing lists. That is, you need to be
-    subscribed to a list to be allowed to post on it.  (You need not be
-    subscribed to use the bug-report web form, however.)
-    If you would like to send mail but do not want to receive list traffic,
-    you can subscribe and set your subscription option to <literal>nomail</>.
-<!## end>
-<!## XL>
-    Due to the unfortunate amount of spam going around, all of the above
-    email addresses are closed mailing lists. That is, you need to be
-    subscribed to a list to be allowed to post on it.  (You need not be
-    subscribed to use the bug-report web form, however.)
-    If you would like to send mail but do not want to receive list traffic,
-    you can subscribe and set your subscription option to <literal>nomail</>.
-<!## end>
-   </para>
-  </note>
- </sect2>
-</sect1>
diff --git a/doc-xc/src/sgml/protocol.sgmlin b/doc-xc/src/sgml/protocol.sgmlin
deleted file mode 100644
index d7fa220f72..0000000000
--- a/doc-xc/src/sgml/protocol.sgmlin
+++ /dev/null
@@ -1,4821 +0,0 @@
-<!-- doc/src/sgml/protocol.sgml -->
-
-<chapter id="protocol">
- <title>Frontend/Backend Protocol</title>
-
- <indexterm zone="protocol">
-  <primary>protocol</primary>
-  <secondary>frontend-backend</secondary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  <productname>PostgreSQL</productname> uses a message-based protocol
-  for communication between frontends and backends (clients and servers).
-  The protocol is supported over <acronym>TCP/IP</acronym> and also over
-  Unix-domain sockets.  Port number 5432 has been registered with IANA as
-  the customary TCP port number for servers supporting this protocol, but
-  in practice any non-privileged port number can be used.
- </para>
-
- <para>
-  This document describes version 3.0 of the protocol, implemented in
-  <productname>PostgreSQL</productname> 7.4 and later.  For descriptions
-  of the earlier protocol versions, see previous releases of the
-  <productname>PostgreSQL</productname> documentation.  A single server
-  can support multiple protocol versions.  The initial
-  startup-request message tells the server which protocol version the
-  client is attempting to use, and then the server follows that protocol
-  if it is able.
- </para>
-
-  <para>
-   In order to serve multiple clients efficiently, the server launches
-   a new <quote>backend</> process for each client.
-   In the current implementation, a new child
-   process is created immediately after an incoming connection is detected.
-   This is transparent to the protocol, however.  For purposes of the
-   protocol, the terms <quote>backend</> and <quote>server</> are
-   interchangeable; likewise <quote>frontend</> and <quote>client</>
-   are interchangeable.
-  </para>
-
- <sect1 id="protocol-overview">
-  <title>Overview</title>
-
-&pgnotice;
-  <para>
-   The protocol has separate phases for startup and normal operation.
-   In the startup phase, the frontend opens a connection to the server
-   and authenticates itself to the satisfaction of the server.  (This might
-   involve a single message, or multiple messages depending on the
-   authentication method being used.)  If all goes well, the server then sends
-   status information to the frontend, and finally enters normal operation.
-   Except for the initial startup-request message, this part of the
-   protocol is driven by the server.
-  </para>
-
-  <para>
-   During normal operation, the frontend sends queries and
-   other commands to the backend, and the backend sends back query results
-   and other responses.  There are a few cases (such as <command>NOTIFY</>)
-   wherein the
-   backend will send unsolicited messages, but for the most part this portion
-   of a session is driven by frontend requests.
-  </para>
-
-  <para>
-   Termination of the session is normally by frontend choice, but can be
-   forced by the backend in certain cases.  In any case, when the backend
-   closes the connection, it will roll back any open (incomplete) transaction
-   before exiting.
-  </para>
-
-  <para>
-   Within normal operation, SQL commands can be executed through either of
-   two sub-protocols.  In the <quote>simple query</> protocol, the frontend
-   just sends a textual query string, which is parsed and immediately
-   executed by the backend.  In the <quote>extended query</> protocol,
-   processing of queries is separated into multiple steps: parsing,
-   binding of parameter values, and execution.  This offers flexibility
-   and performance benefits, at the cost of extra complexity.
-  </para>
-
-  <para>
-   Normal operation has additional sub-protocols for special operations
-   such as <command>COPY</>.
-  </para>
-
- <sect2 id="protocol-message-concepts">
-  <title>Messaging Overview</title>
-
-&pgnotice;
-  <para>
-   All communication is through a stream of messages.  The first byte of a
-   message identifies the message type, and the next four bytes specify the
-   length of the rest of the message (this length count includes itself, but
-   not the message-type byte).  The remaining contents of the message are
-   determined by the message type.  For historical reasons, the very first
-   message sent by the client (the startup message) has no initial
-   message-type byte.
-  </para>
-
-  <para>
-   To avoid losing synchronization with the message stream, both servers and
-   clients typically read an entire message into a buffer (using the byte
-   count) before attempting to process its contents.  This allows easy
-   recovery if an error is detected while processing the contents.  In
-   extreme situations (such as not having enough memory to buffer the
-   message), the receiver can use the byte count to determine how much
-   input to skip before it resumes reading messages.
-  </para>
-
-  <para>
-   Conversely, both servers and clients must take care never to send an
-   incomplete message.  This is commonly done by marshaling the entire message
-   in a buffer before beginning to send it.  If a communications failure
-   occurs partway through sending or receiving a message, the only sensible
-   response is to abandon the connection, since there is little hope of
-   recovering message-boundary synchronization.
-  </para>
- </sect2>
-
-  <sect2 id="protocol-query-concepts">
-   <title>Extended Query Overview</title>
-
-&pgnotice;
-   <para>
-    In the extended-query protocol, execution of SQL commands is divided
-    into multiple steps.  The state retained between steps is represented
-    by two types of objects: <firstterm>prepared statements</> and
-    <firstterm>portals</>.  A prepared statement represents the result of
-    parsing, semantic analysis, and (optionally) planning of a textual query
-    string.
-    A prepared statement is not necessarily ready to execute, because it might
-    lack specific values for <firstterm>parameters</>.  A portal represents
-    a ready-to-execute or already-partially-executed statement, with any
-    missing parameter values filled in.  (For <command>SELECT</> statements,
-    a portal is equivalent to an open cursor, but we choose to use a different
-    term since cursors don't handle non-<command>SELECT</> statements.)
-   </para>
-
-   <para>
-    The overall execution cycle consists of a <firstterm>parse</> step,
-    which creates a prepared statement from a textual query string; a
-    <firstterm>bind</> step, which creates a portal given a prepared
-    statement and values for any needed parameters; and an
-    <firstterm>execute</> step that runs a portal's query.  In the case of
-    a query that returns rows (<command>SELECT</>, <command>SHOW</>, etc),
-    the execute step can be told to fetch only
-    a limited number of rows, so that multiple execute steps might be needed
-    to complete the operation.
-   </para>
-
-   <para>
-    The backend can keep track of multiple prepared statements and portals
-    (but note that these exist only within a session, and are never shared
-    across sessions).  Existing prepared statements and portals are
-    referenced by names assigned when they were created.  In addition,
-    an <quote>unnamed</> prepared statement and portal exist.  Although these
-    behave largely the same as named objects, operations on them are optimized
-    for the case of executing a query only once and then discarding it,
-    whereas operations on named objects are optimized on the expectation
-    of multiple uses.
-   </para>
-  </sect2>
-
-  <sect2 id="protocol-format-codes">
-   <title>Formats and Format Codes</title>
-
-&pgnotice;
-   <para>
-    Data of a particular data type might be transmitted in any of several
-    different <firstterm>formats</>.  As of <productname>PostgreSQL</> 7.4
-    the only supported formats are <quote>text</> and <quote>binary</>,
-    but the protocol makes provision for future extensions.  The desired
-    format for any value is specified by a <firstterm>format code</>.
-    Clients can specify a format code for each transmitted parameter value
-    and for each column of a query result.  Text has format code zero,
-    binary has format code one, and all other format codes are reserved
-    for future definition.
-   </para>
-
-   <para>
-    The text representation of values is whatever strings are produced
-    and accepted by the input/output conversion functions for the
-    particular data type.  In the transmitted representation, there is
-    no trailing null character; the frontend must add one to received
-    values if it wants to process them as C strings.
-    (The text format does not allow embedded nulls, by the way.)
-   </para>
-
-   <para>
-    Binary representations for integers use network byte order (most
-    significant byte first).  For other data types consult the documentation
-    or source code to learn about the binary representation.  Keep in mind
-    that binary representations for complex data types might change across
-    server versions; the text format is usually the more portable choice.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="protocol-flow">
-  <title>Message Flow</title>
-
-&pgnotice;
-  <para>
-   This section describes the message flow and the semantics of each
-   message type.  (Details of the exact representation of each message
-   appear in <xref linkend="protocol-message-formats">.)  There are
-   several different sub-protocols depending on the state of the
-   connection: start-up, query, function call,
-   <command>COPY</command>, and termination.  There are also special
-   provisions for asynchronous operations (including notification
-   responses and command cancellation), which can occur at any time
-   after the start-up phase.
-  </para>
-
-  <sect2>
-   <title>Start-up</title>
-
-&pgnotice;
-   <para>
-    To begin a session, a frontend opens a connection to the server and sends
-    a startup message.  This message includes the names of the user and of the
-    database the user wants to connect to; it also identifies the particular
-    protocol version to be used.  (Optionally, the startup message can include
-    additional settings for run-time parameters.)
-    The server then uses this information and
-    the contents of its configuration files (such as
-    <filename>pg_hba.conf</filename>) to determine
-    whether the connection is provisionally acceptable, and what additional
-    authentication is required (if any).
-   </para>
-
-   <para>
-    The server then sends an appropriate authentication request message,
-    to which the frontend must reply with an appropriate authentication
-    response message (such as a password).
-    For all authentication methods except GSSAPI and SSPI, there is at most
-    one request and one response. In some methods, no response
-    at all is needed from the frontend, and so no authentication request
-    occurs. For GSSAPI and SSPI, multiple exchanges of packets may be needed
-    to complete the authentication.
-   </para>
-
-   <para>
-    The authentication cycle ends with the server either rejecting the
-    connection attempt (ErrorResponse), or sending AuthenticationOk.
-   </para>
-
-   <para>
-    The possible messages from the server in this phase are:
-
-    <variablelist>
-     <varlistentry>
-      <term>ErrorResponse</term>
-      <listitem>
-       <para>
-        The connection attempt has been rejected.
-        The server then immediately closes the connection.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>AuthenticationOk</term>
-      <listitem>
-       <para>
-        The authentication exchange is successfully completed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>AuthenticationKerberosV5</term>
-      <listitem>
-       <para>
-        The frontend must now take part in a Kerberos V5
-        authentication dialog (not described here, part of the
-        Kerberos specification) with the server.  If this is
-        successful, the server responds with an AuthenticationOk,
-        otherwise it responds with an ErrorResponse.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>AuthenticationCleartextPassword</term>
-      <listitem>
-       <para>
-        The frontend must now send a PasswordMessage containing the
-        password in clear-text form.  If
-        this is the correct password, the server responds with an
-        AuthenticationOk, otherwise it responds with an ErrorResponse.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>AuthenticationMD5Password</term>
-      <listitem>
-       <para>
-        The frontend must now send a PasswordMessage containing the
-        password encrypted via MD5, using the 4-character salt
-        specified in the AuthenticationMD5Password message.  If
-        this is the correct password, the server responds with an
-        AuthenticationOk, otherwise it responds with an ErrorResponse.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>AuthenticationSCMCredential</term>
-      <listitem>
-       <para>
-        This response is only possible for local Unix-domain connections
-        on platforms that support SCM credential messages.  The frontend
-        must issue an SCM credential message and then send a single data
-        byte.  (The contents of the data byte are uninteresting; it's
-        only used to ensure that the server waits long enough to receive
-        the credential message.)  If the credential is acceptable,
-        the server responds with an
-        AuthenticationOk, otherwise it responds with an ErrorResponse.
-        (This message type is only issued by pre-9.1 servers.  It may
-        eventually be removed from the protocol specification.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>AuthenticationGSS</term>
-      <listitem>
-       <para>
-        The frontend must now initiate a GSSAPI negotiation. The frontend
-        will send a PasswordMessage with the first part of the GSSAPI
-        data stream in response to this. If further messages are needed,
-        the server will respond with AuthenticationGSSContinue.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>AuthenticationSSPI</term>
-      <listitem>
-       <para>
-        The frontend must now initiate a SSPI negotiation. The frontend
-        will send a PasswordMessage with the first part of the SSPI
-        data stream in response to this. If further messages are needed,
-        the server will respond with AuthenticationGSSContinue.
-       </para>
-      </listitem>
-
-     </varlistentry>
-     <varlistentry>
-      <term>AuthenticationGSSContinue</term>
-      <listitem>
-       <para>
-        This message contains the response data from the previous step
-        of GSSAPI or SSPI negotiation (AuthenticationGSS, AuthenticationSSPI
-        or a previous AuthenticationGSSContinue). If the GSSAPI
-        or SSPI data in this message
-        indicates more data is needed to complete the authentication,
-        the frontend must send that data as another PasswordMessage. If
-        GSSAPI or SSPI authentication is completed by this message, the server
-        will next send AuthenticationOk to indicate successful authentication
-        or ErrorResponse to indicate failure.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    If the frontend does not support the authentication method
-    requested by the server, then it should immediately close the
-    connection.
-   </para>
-
-   <para>
-    After having received AuthenticationOk, the frontend must wait
-    for further messages from the server.  In this phase a backend process
-    is being started, and the frontend is just an interested bystander.
-    It is still possible for the startup attempt
-    to fail (ErrorResponse), but in the normal case the backend will send
-    some ParameterStatus messages, BackendKeyData, and finally ReadyForQuery.
-   </para>
-
-   <para>
-    During this phase the backend will attempt to apply any additional
-    run-time parameter settings that were given in the startup message.
-    If successful, these values become session defaults.  An error causes
-    ErrorResponse and exit.
-   </para>
-
-   <para>
-    The possible messages from the backend in this phase are:
-
-    <variablelist>
-     <varlistentry>
-      <term>BackendKeyData</term>
-      <listitem>
-       <para>
-        This message provides secret-key data that the frontend must
-        save if it wants to be able to issue cancel requests later.
-        The frontend should not respond to this message, but should
-        continue listening for a ReadyForQuery message.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ParameterStatus</term>
-      <listitem>
-       <para>
-        This message informs the frontend about the current (initial)
-         setting of backend parameters, such as <xref
-         linkend="guc-client-encoding"> or <xref linkend="guc-datestyle">.
-         The frontend can ignore this message, or record the settings
-         for its future use; see <xref linkend="protocol-async"> for
-         more details.  The frontend should not respond to this
-         message, but should continue listening for a ReadyForQuery
-         message.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ReadyForQuery</term>
-      <listitem>
-       <para>
-        Start-up is completed.  The frontend can now issue commands.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ErrorResponse</term>
-      <listitem>
-       <para>
-        Start-up failed.  The connection is closed after sending this
-        message.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>NoticeResponse</term>
-      <listitem>
-       <para>
-        A warning message has been issued.  The frontend should
-        display the message but continue listening for ReadyForQuery
-        or ErrorResponse.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    The ReadyForQuery message is the same one that the backend will
-    issue after each command cycle.  Depending on the coding needs of
-    the frontend, it is reasonable to consider ReadyForQuery as
-    starting a command cycle, or to consider ReadyForQuery as ending the
-    start-up phase and each subsequent command cycle.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Simple Query</title>
-
-&pgnotice;
-   <para>
-    A simple query cycle is initiated by the frontend sending a Query message
-    to the backend.  The message includes an SQL command (or commands)
-    expressed as a text string.
-    The backend then sends one or more response
-    messages depending on the contents of the query command string,
-    and finally a ReadyForQuery response message.  ReadyForQuery
-    informs the frontend that it can safely send a new command.
-    (It is not actually necessary for the frontend to wait for
-    ReadyForQuery before issuing another command, but the frontend must
-    then take responsibility for figuring out what happens if the earlier
-    command fails and already-issued later commands succeed.)
-   </para>
-
-   <para>
-    The possible response messages from the backend are:
-
-    <variablelist>
-     <varlistentry>
-      <term>CommandComplete</term>
-      <listitem>
-       <para>
-        An SQL command completed normally.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>CopyInResponse</term>
-      <listitem>
-       <para>
-        The backend is ready to copy data from the frontend to a
-        table; see <xref linkend="protocol-copy">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>CopyOutResponse</term>
-      <listitem>
-       <para>
-        The backend is ready to copy data from a table to the
-        frontend; see <xref linkend="protocol-copy">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>RowDescription</term>
-      <listitem>
-       <para>
-        Indicates that rows are about to be returned in response to
-        a <command>SELECT</command>, <command>FETCH</command>, etc query.
-        The contents of this message describe the column layout of the rows.
-        This will be followed by a DataRow message for each row being returned
-        to the frontend.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>DataRow</term>
-      <listitem>
-       <para>
-        One of the set of rows returned by
-        a <command>SELECT</command>, <command>FETCH</command>, etc query.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>EmptyQueryResponse</term>
-      <listitem>
-       <para>
-        An empty query string was recognized.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ErrorResponse</term>
-      <listitem>
-       <para>
-        An error has occurred.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ReadyForQuery</term>
-      <listitem>
-       <para>
-        Processing of the query string is complete.  A separate
-        message is sent to indicate this because the query string might
-        contain multiple SQL commands.  (CommandComplete marks the
-        end of processing one SQL command, not the whole string.)
-        ReadyForQuery will always be sent, whether processing
-        terminates successfully or with an error.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>NoticeResponse</term>
-      <listitem>
-       <para>
-        A warning message has been issued in relation to the query.
-        Notices are in addition to other responses, i.e., the backend
-        will continue processing the command.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    The response to a <command>SELECT</> query (or other queries that
-    return row sets, such as <command>EXPLAIN</> or <command>SHOW</>)
-    normally consists of RowDescription, zero or more
-    DataRow messages, and then CommandComplete.
-    <command>COPY</> to or from the frontend invokes special protocol
-    as described in <xref linkend="protocol-copy">.
-    All other query types normally produce only
-    a CommandComplete message.
-   </para>
-
-   <para>
-    Since a query string could contain several queries (separated by
-    semicolons), there might be several such response sequences before the
-    backend finishes processing the query string.  ReadyForQuery is issued
-    when the entire string has been processed and the backend is ready to
-    accept a new query string.
-   </para>
-
-   <para>
-    If a completely empty (no contents other than whitespace) query string
-    is received, the response is EmptyQueryResponse followed by ReadyForQuery.
-   </para>
-
-   <para>
-    In the event of an error, ErrorResponse is issued followed by
-    ReadyForQuery.  All further processing of the query string is aborted by
-    ErrorResponse (even if more queries remained in it).  Note that this
-    might occur partway through the sequence of messages generated by an
-    individual query.
-   </para>
-
-   <para>
-    In simple Query mode, the format of retrieved values is always text,
-    except when the given command is a <command>FETCH</> from a cursor
-    declared with the <literal>BINARY</> option.  In that case, the
-    retrieved values are in binary format.  The format codes given in
-    the RowDescription message tell which format is being used.
-   </para>
-
-   <para>
-    A frontend must be prepared to accept ErrorResponse and
-    NoticeResponse messages whenever it is expecting any other type of
-    message.  See also <xref linkend="protocol-async"> concerning messages
-    that the backend might generate due to outside events.
-   </para>
-
-   <para>
-    Recommended practice is to code frontends in a state-machine style
-    that will accept any message type at any time that it could make sense,
-    rather than wiring in assumptions about the exact sequence of messages.
-   </para>
-  </sect2>
-
-  <sect2 id="protocol-flow-ext-query">
-   <title>Extended Query</title>
-
-&pgnotice;
-   <para>
-    The extended query protocol breaks down the above-described simple
-    query protocol into multiple steps.  The results of preparatory
-    steps can be re-used multiple times for improved efficiency.
-    Furthermore, additional features are available, such as the possibility
-    of supplying data values as separate parameters instead of having to
-    insert them directly into a query string.
-   </para>
-
-   <para>
-    In the extended protocol, the frontend first sends a Parse message,
-    which contains a textual query string, optionally some information
-    about data types of parameter placeholders, and the
-    name of a destination prepared-statement object (an empty string
-    selects the unnamed prepared statement).  The response is
-    either ParseComplete or ErrorResponse.  Parameter data types can be
-    specified by OID; if not given, the parser attempts to infer the
-    data types in the same way as it would do for untyped literal string
-    constants.
-   </para>
-
-   <note>
-    <para>
-     A parameter data type can be left unspecified by setting it to zero,
-     or by making the array of parameter type OIDs shorter than the
-     number of parameter symbols (<literal>$</><replaceable>n</>)
-     used in the query string.  Another special case is that a parameter's
-     type can be specified as <type>void</> (that is, the OID of the
-     <type>void</> pseudotype).  This is meant to allow parameter symbols
-     to be used for function parameters that are actually OUT parameters.
-     Ordinarily there is no context in which a <type>void</> parameter
-     could be used, but if such a parameter symbol appears in a function's
-     parameter list, it is effectively ignored.  For example, a function
-     call such as <literal>foo($1,$2,$3,$4)</> could match a function with
-     two IN and two OUT arguments, if <literal>$3</> and <literal>$4</>
-     are specified as having type <type>void</>.
-    </para>
-   </note>
-
-   <note>
-    <para>
-     The query string contained in a Parse message cannot include more
-     than one SQL statement; else a syntax error is reported.  This
-     restriction does not exist in the simple-query protocol, but it
-     does exist in the extended protocol, because allowing prepared
-     statements or portals to contain multiple commands would complicate
-     the protocol unduly.
-    </para>
-   </note>
-
-   <para>
-    If successfully created, a named prepared-statement object lasts till
-    the end of the current session, unless explicitly destroyed.  An unnamed
-    prepared statement lasts only until the next Parse statement specifying
-    the unnamed statement as destination is issued.  (Note that a simple
-    Query message also destroys the unnamed statement.)  Named prepared
-    statements must be explicitly closed before they can be redefined by
-    a Parse message, but this is not required for the unnamed statement.
-    Named prepared statements can also be created and accessed at the SQL
-    command level, using <command>PREPARE</> and <command>EXECUTE</>.
-   </para>
-
-   <para>
-    Once a prepared statement exists, it can be readied for execution using a
-    Bind message.  The Bind message gives the name of the source prepared
-    statement (empty string denotes the unnamed prepared statement), the name
-    of the destination portal (empty string denotes the unnamed portal), and
-    the values to use for any parameter placeholders present in the prepared
-    statement.  The
-    supplied parameter set must match those needed by the prepared statement.
-    (If you declared any <type>void</> parameters in the Parse message,
-    pass NULL values for them in the Bind message.)
-    Bind also specifies the format to use for any data returned
-    by the query; the format can be specified overall, or per-column.
-    The response is either BindComplete or ErrorResponse.
-   </para>
-
-   <note>
-    <para>
-     The choice between text and binary output is determined by the format
-     codes given in Bind, regardless of the SQL command involved.  The
-     <literal>BINARY</> attribute in cursor declarations is irrelevant when
-     using extended query protocol.
-    </para>
-   </note>
-
-   <para>
-    Query planning for named prepared-statement objects occurs when the Parse
-    message is processed. If a query will be repeatedly executed with
-    different parameters, it might be beneficial to send a single Parse message
-    containing a parameterized query, followed by multiple Bind
-    and Execute messages. This will avoid replanning the query on each
-    execution.
-   </para>
-
-   <para>
-    The unnamed prepared statement is likewise planned during Parse processing
-    if the Parse message defines no parameters.  But if there are parameters,
-    query planning occurs every time Bind parameters are supplied.  This allows the
-    planner to make use of the actual values of the parameters provided by
-    each Bind message, rather than use generic estimates.
-   </para>
-
-   <note>
-    <para>
-     Query plans generated from a parameterized query might be less
-     efficient than query plans generated from an equivalent query with actual
-     parameter values substituted. The query planner cannot make decisions
-     based on actual parameter values (for example, index selectivity) when
-     planning a parameterized query assigned to a named prepared-statement
-     object.  This possible penalty is avoided when using the unnamed
-     statement, since it is not planned until actual parameter values are
-     available.  The cost is that planning must occur afresh for each Bind,
-     even if the query stays the same.
-    </para>
-   </note>
-
-   <para>
-    If successfully created, a named portal object lasts till the end of the
-    current transaction, unless explicitly destroyed.  An unnamed portal is
-    destroyed at the end of the transaction, or as soon as the next Bind
-    statement specifying the unnamed portal as destination is issued.  (Note
-    that a simple Query message also destroys the unnamed portal.)  Named
-    portals must be explicitly closed before they can be redefined by a Bind
-    message, but this is not required for the unnamed portal.
-    Named portals can also be created and accessed at the SQL
-    command level, using <command>DECLARE CURSOR</> and <command>FETCH</>.
-   </para>
-
-   <para>
-    Once a portal exists, it can be executed using an Execute message.
-    The Execute message specifies the portal name (empty string denotes the
-    unnamed portal) and
-    a maximum result-row count (zero meaning <quote>fetch all rows</>).
-    The result-row count is only meaningful for portals
-    containing commands that return row sets; in other cases the command is
-    always executed to completion, and the row count is ignored.
-    The possible
-    responses to Execute are the same as those described above for queries
-    issued via simple query protocol, except that Execute doesn't cause
-    ReadyForQuery or RowDescription to be issued.
-   </para>
-
-   <para>
-    If Execute terminates before completing the execution of a portal
-    (due to reaching a nonzero result-row count), it will send a
-    PortalSuspended message; the appearance of this message tells the frontend
-    that another Execute should be issued against the same portal to
-    complete the operation.  The CommandComplete message indicating
-    completion of the source SQL command is not sent until
-    the portal's execution is completed.  Therefore, an Execute phase is
-    always terminated by the appearance of exactly one of these messages:
-    CommandComplete, EmptyQueryResponse (if the portal was created from
-    an empty query string), ErrorResponse, or PortalSuspended.
-   </para>
-
-   <para>
-    At completion of each series of extended-query messages, the frontend
-    should issue a Sync message.  This parameterless message causes the
-    backend to close the current transaction if it's not inside a
-    <command>BEGIN</>/<command>COMMIT</> transaction block (<quote>close</>
-    meaning to commit if no error, or roll back if error).  Then a
-    ReadyForQuery response is issued.  The purpose of Sync is to provide
-    a resynchronization point for error recovery.  When an error is detected
-    while processing any extended-query message, the backend issues
-    ErrorResponse, then reads and discards messages until a Sync is reached,
-    then issues ReadyForQuery and returns to normal message processing.
-    (But note that no skipping occurs if an error is detected
-    <emphasis>while</> processing Sync &mdash; this ensures that there is one
-    and only one ReadyForQuery sent for each Sync.)
-   </para>
-
-   <note>
-    <para>
-     Sync does not cause a transaction block opened with <command>BEGIN</>
-     to be closed.  It is possible to detect this situation since the
-     ReadyForQuery message includes transaction status information.
-    </para>
-   </note>
-
-   <para>
-    In addition to these fundamental, required operations, there are several
-    optional operations that can be used with extended-query protocol.
-   </para>
-
-   <para>
-    The Describe message (portal variant) specifies the name of an existing
-    portal (or an empty string for the unnamed portal).  The response is a
-    RowDescription message describing the rows that will be returned by
-    executing the portal; or a NoData message if the portal does not contain a
-    query that will return rows; or ErrorResponse if there is no such portal.
-   </para>
-
-   <para>
-    The Describe message (statement variant) specifies the name of an existing
-    prepared statement (or an empty string for the unnamed prepared
-    statement).  The response is a ParameterDescription message describing the
-    parameters needed by the statement, followed by a RowDescription message
-    describing the rows that will be returned when the statement is eventually
-    executed (or a NoData message if the statement will not return rows).
-    ErrorResponse is issued if there is no such prepared statement.  Note that
-    since Bind has not yet been issued, the formats to be used for returned
-    columns are not yet known to the backend; the format code fields in the
-    RowDescription message will be zeroes in this case.
-   </para>
-
-   <tip>
-    <para>
-     In most scenarios the frontend should issue one or the other variant
-     of Describe before issuing Execute, to ensure that it knows how to
-     interpret the results it will get back.
-    </para>
-   </tip>
-
-   <para>
-    The Close message closes an existing prepared statement or portal
-    and releases resources.  It is not an error to issue Close against
-    a nonexistent statement or portal name.  The response is normally
-    CloseComplete, but could be ErrorResponse if some difficulty is
-    encountered while releasing resources.  Note that closing a prepared
-    statement implicitly closes any open portals that were constructed
-    from that statement.
-   </para>
-
-   <para>
-    The Flush message does not cause any specific output to be generated,
-    but forces the backend to deliver any data pending in its output
-    buffers.  A Flush must be sent after any extended-query command except
-    Sync, if the frontend wishes to examine the results of that command before
-    issuing more commands.  Without Flush, messages returned by the backend
-    will be combined into the minimum possible number of packets to minimize
-    network overhead.
-   </para>
-
-   <note>
-    <para>
-     The simple Query message is approximately equivalent to the series Parse,
-     Bind, portal Describe, Execute, Close, Sync, using the unnamed prepared
-     statement and portal objects and no parameters.  One difference is that
-     it will accept multiple SQL statements in the query string, automatically
-     performing the bind/describe/execute sequence for each one in succession.
-     Another difference is that it will not return ParseComplete, BindComplete,
-     CloseComplete, or NoData messages.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2>
-   <title>Function Call</title>
-
-&pgnotice;
-   <para>
-    The Function Call sub-protocol allows the client to request a direct
-    call of any function that exists in the database's
-    <structname>pg_proc</structname> system catalog.  The client must have
-    execute permission for the function.
-   </para>
-
-   <note>
-    <para>
-     The Function Call sub-protocol is a legacy feature that is probably best
-     avoided in new code.  Similar results can be accomplished by setting up
-     a prepared statement that does <literal>SELECT function($1, ...)</>.
-     The Function Call cycle can then be replaced with Bind/Execute.
-    </para>
-   </note>
-
-   <para>
-    A Function Call cycle is initiated by the frontend sending a
-    FunctionCall message to the backend.  The backend then sends one
-    or more response messages depending on the results of the function
-    call, and finally a ReadyForQuery response message.  ReadyForQuery
-    informs the frontend that it can safely send a new query or
-    function call.
-   </para>
-
-   <para>
-    The possible response messages from the backend are:
-
-    <variablelist>
-     <varlistentry>
-      <term>ErrorResponse</term>
-      <listitem>
-       <para>
-        An error has occurred.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>FunctionCallResponse</term>
-      <listitem>
-       <para>
-        The function call was completed and returned the result given
-        in the message.
-        (Note that the Function Call protocol can only handle a single
-        scalar result, not a row type or set of results.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ReadyForQuery</term>
-      <listitem>
-       <para>
-        Processing of the function call is complete.  ReadyForQuery
-        will always be sent, whether processing terminates
-        successfully or with an error.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>NoticeResponse</term>
-      <listitem>
-       <para>
-        A warning message has been issued in relation to the function
-        call.  Notices are in addition to other responses, i.e., the
-        backend will continue processing the command.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
-
-  <sect2 id="protocol-copy">
-   <title>COPY Operations</title>
-
-&pgnotice;
-   <para>
-    The <command>COPY</> command allows high-speed bulk data transfer
-    to or from the server.  Copy-in and copy-out operations each switch
-    the connection into a distinct sub-protocol, which lasts until the
-    operation is completed.
-   </para>
-
-   <para>
-    Copy-in mode (data transfer to the server) is initiated when the
-    backend executes a <command>COPY FROM STDIN</> SQL statement.  The backend
-    sends a CopyInResponse message to the frontend.  The frontend should
-    then send zero or more CopyData messages, forming a stream of input
-    data.  (The message boundaries are not required to have anything to do
-    with row boundaries, although that is often a reasonable choice.)
-    The frontend can terminate the copy-in mode by sending either a CopyDone
-    message (allowing successful termination) or a CopyFail message (which
-    will cause the <command>COPY</> SQL statement to fail with an
-    error).  The backend then reverts to the command-processing mode it was
-    in before the <command>COPY</> started, which will be either simple or
-    extended query protocol.  It will next send either CommandComplete
-    (if successful) or ErrorResponse (if not).
-   </para>
-
-   <para>
-    In the event of a backend-detected error during copy-in mode (including
-    receipt of a CopyFail message), the backend will issue an ErrorResponse
-    message.  If the <command>COPY</> command was issued via an extended-query
-    message, the backend will now discard frontend messages until a Sync
-    message is received, then it will issue ReadyForQuery and return to normal
-    processing.  If the <command>COPY</> command was issued in a simple
-    Query message, the rest of that message is discarded and ReadyForQuery
-    is issued.  In either case, any subsequent CopyData, CopyDone, or CopyFail
-    messages issued by the frontend will simply be dropped.
-   </para>
-
-   <para>
-    The backend will ignore Flush and Sync messages received during copy-in
-    mode.  Receipt of any other non-copy message type constitutes an error
-    that will abort the copy-in state as described above.  (The exception for
-    Flush and Sync is for the convenience of client libraries that always
-    send Flush or Sync after an Execute message, without checking whether
-    the command to be executed is a <command>COPY FROM STDIN</>.)
-   </para>
-
-   <para>
-    Copy-out mode (data transfer from the server) is initiated when the
-    backend executes a <command>COPY TO STDOUT</> SQL statement.  The backend
-    sends a CopyOutResponse message to the frontend, followed by
-    zero or more CopyData messages (always one per row), followed by CopyDone.
-    The backend then reverts to the command-processing mode it was
-    in before the <command>COPY</> started, and sends CommandComplete.
-    The frontend cannot abort the transfer (except by closing the connection
-    or issuing a Cancel request),
-    but it can discard unwanted CopyData and CopyDone messages.
-   </para>
-
-   <para>
-    In the event of a backend-detected error during copy-out mode,
-    the backend will issue an ErrorResponse message and revert to normal
-    processing.  The frontend should treat receipt of ErrorResponse as
-    terminating the copy-out mode.
-   </para>
-
-   <para>
-    It is possible for NoticeResponse and ParameterStatus messages to be
-    interspersed between CopyData messages; frontends must handle these cases,
-    and should be prepared for other asynchronous message types as well (see
-    <xref linkend="protocol-async">).  Otherwise, any message type other than
-    CopyData or CopyDone may be treated as terminating copy-out mode.
-   </para>
-
-   <para>
-    There is another Copy-related mode called Copy-both, which allows
-    high-speed bulk data transfer to <emphasis>and</> from the server.
-    Copy-both mode is initiated when a backend in walsender mode
-    executes a <command>START_REPLICATION</command> statement.  The
-    backend sends a CopyBothResponse message to the frontend.  Both
-    the backend and the frontend may then send CopyData messages
-    until the connection is terminated.  See <xref
-    linkend="protocol-replication">.
-   </para>
-
-   <para>
-    The CopyInResponse, CopyOutResponse and CopyBothResponse messages
-    include fields that inform the frontend of the number of columns
-    per row and the format codes being used for each column.  (As of
-    the present implementation, all columns in a given <command>COPY</>
-    operation will use the same format, but the message design does not
-    assume this.)
-   </para>
-
-  </sect2>
-
-  <sect2 id="protocol-async">
-   <title>Asynchronous Operations</title>
-
-&pgnotice;
-   <para>
-    There are several cases in which the backend will send messages that
-    are not specifically prompted by the frontend's command stream.
-    Frontends must be prepared to deal with these messages at any time,
-    even when not engaged in a query.
-    At minimum, one should check for these cases before beginning to
-    read a query response.
-   </para>
-
-   <para>
-    It is possible for NoticeResponse messages to be generated due to
-    outside activity; for example, if the database administrator commands
-    a <quote>fast</> database shutdown, the backend will send a NoticeResponse
-    indicating this fact before closing the connection.  Accordingly,
-    frontends should always be prepared to accept and display NoticeResponse
-    messages, even when the connection is nominally idle.
-   </para>
-
-   <para>
-    ParameterStatus messages will be generated whenever the active
-    value changes for any of the parameters the backend believes the
-    frontend should know about.  Most commonly this occurs in response
-    to a <command>SET</> SQL command executed by the frontend, and
-    this case is effectively synchronous &mdash; but it is also possible
-    for parameter status changes to occur because the administrator
-    changed a configuration file and then sent the
-    <systemitem>SIGHUP</systemitem> signal to the server.  Also,
-    if a <command>SET</command> command is rolled back, an appropriate
-    ParameterStatus message will be generated to report the current
-    effective value.
-   </para>
-
-   <para>
-    At present there is a hard-wired set of parameters for which
-    ParameterStatus will be generated: they are
-    <varname>server_version</>,
-    <varname>server_encoding</>,
-    <varname>client_encoding</>,
-    <varname>application_name</>,
-    <varname>is_superuser</>,
-    <varname>session_authorization</>,
-    <varname>DateStyle</>,
-    <varname>IntervalStyle</>,
-    <varname>TimeZone</>,
-    <varname>integer_datetimes</>, and
-    <varname>standard_conforming_strings</>.
-    (<varname>server_encoding</>, <varname>TimeZone</>, and
-    <varname>integer_datetimes</> were not reported by releases before 8.0;
-    <varname>standard_conforming_strings</> was not reported by releases
-    before 8.1;
-    <varname>IntervalStyle</> was not reported by releases before 8.4;
-    <varname>application_name</> was not reported by releases before 9.0.)
-    Note that
-    <varname>server_version</>,
-    <varname>server_encoding</> and
-    <varname>integer_datetimes</>
-    are pseudo-parameters that cannot change after startup.
-    This set might change in the future, or even become configurable.
-    Accordingly, a frontend should simply ignore ParameterStatus for
-    parameters that it does not understand or care about.
-   </para>
-
-   <para>
-    If a frontend issues a <command>LISTEN</command> command, then the
-    backend will send a NotificationResponse message (not to be
-    confused with NoticeResponse!)  whenever a
-    <command>NOTIFY</command> command is executed for the same
-    channel name.
-   </para>
-
-   <note>
-    <para>
-     At present, NotificationResponse can only be sent outside a
-     transaction, and thus it will not occur in the middle of a
-     command-response series, though it might occur just before ReadyForQuery.
-     It is unwise to design frontend logic that assumes that, however.
-     Good practice is to be able to accept NotificationResponse at any
-     point in the protocol.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2>
-   <title>Cancelling Requests in Progress</title>
-
-&pgnotice;
-   <para>
-    During the processing of a query, the frontend might request
-    cancellation of the query.  The cancel request is not sent
-    directly on the open connection to the backend for reasons of
-    implementation efficiency: we don't want to have the backend
-    constantly checking for new input from the frontend during query
-    processing.  Cancel requests should be relatively infrequent, so
-    we make them slightly cumbersome in order to avoid a penalty in
-    the normal case.
-   </para>
-
-   <para>
-    To issue a cancel request, the frontend opens a new connection to
-    the server and sends a CancelRequest message, rather than the
-    StartupMessage message that would ordinarily be sent across a new
-    connection.  The server will process this request and then close
-    the connection.  For security reasons, no direct reply is made to
-    the cancel request message.
-   </para>
-
-   <para>
-    A CancelRequest message will be ignored unless it contains the
-    same key data (PID and secret key) passed to the frontend during
-    connection start-up.  If the request matches the PID and secret
-    key for a currently executing backend, the processing of the
-    current query is aborted.  (In the existing implementation, this is
-    done by sending a special signal to the backend process that is
-    processing the query.)
-   </para>
-
-   <para>
-    The cancellation signal might or might not have any effect &mdash; for
-    example, if it arrives after the backend has finished processing
-    the query, then it will have no effect.  If the cancellation is
-    effective, it results in the current command being terminated
-    early with an error message.
-   </para>
-
-   <para>
-    The upshot of all this is that for reasons of both security and
-    efficiency, the frontend has no direct way to tell whether a
-    cancel request has succeeded.  It must continue to wait for the
-    backend to respond to the query.  Issuing a cancel simply improves
-    the odds that the current query will finish soon, and improves the
-    odds that it will fail with an error message instead of
-    succeeding.
-   </para>
-
-   <para>
-    Since the cancel request is sent across a new connection to the
-    server and not across the regular frontend/backend communication
-    link, it is possible for the cancel request to be issued by any
-    process, not just the frontend whose query is to be canceled.
-    This might provide additional flexibility when building
-    multiple-process applications.  It also introduces a security
-    risk, in that unauthorized persons might try to cancel queries.
-    The security risk is addressed by requiring a dynamically
-    generated secret key to be supplied in cancel requests.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Termination</title>
-
-&pgnotice;
-   <para>
-    The normal, graceful termination procedure is that the frontend
-    sends a Terminate message and immediately closes the connection.
-    On receipt of this message, the backend closes the connection and
-    terminates.
-   </para>
-
-   <para>
-    In rare cases (such as an administrator-commanded database shutdown)
-    the backend might disconnect without any frontend request to do so.
-    In such cases the backend will attempt to send an error or notice message
-    giving the reason for the disconnection before it closes the connection.
-   </para>
-
-   <para>
-    Other termination scenarios arise from various failure cases, such as core
-    dump at one end or the other, loss of the communications link, loss of
-    message-boundary synchronization, etc.  If either frontend or backend sees
-    an unexpected closure of the connection, it should clean
-    up and terminate.  The frontend has the option of launching a new backend
-    by recontacting the server if it doesn't want to terminate itself.
-    Closing the connection is also advisable if an unrecognizable message type
-    is received, since this probably indicates loss of message-boundary sync.
-   </para>
-
-   <para>
-    For either normal or abnormal termination, any open transaction is
-    rolled back, not committed.  One should note however that if a
-    frontend disconnects while a non-<command>SELECT</command> query
-    is being processed, the backend will probably finish the query
-    before noticing the disconnection.  If the query is outside any
-    transaction block (<command>BEGIN</> ... <command>COMMIT</>
-    sequence) then its results might be committed before the
-    disconnection is recognized.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title><acronym>SSL</acronym> Session Encryption</title>
-
-&pgnotice;
-   <para>
-    If <productname>PostgreSQL</> was built with
-    <acronym>SSL</acronym> support, frontend/backend communications
-    can be encrypted using <acronym>SSL</acronym>.  This provides
-    communication security in environments where attackers might be
-    able to capture the session traffic. For more information on
-    encrypting <productname>PostgreSQL</productname> sessions with
-    <acronym>SSL</acronym>, see <xref linkend="ssl-tcp">.
-   </para>
-
-   <para>
-    To initiate an <acronym>SSL</acronym>-encrypted connection, the
-    frontend initially sends an SSLRequest message rather than a
-    StartupMessage.  The server then responds with a single byte
-    containing <literal>S</> or <literal>N</>, indicating that it is
-    willing or unwilling to perform <acronym>SSL</acronym>,
-    respectively.  The frontend might close the connection at this point
-    if it is dissatisfied with the response.  To continue after
-    <literal>S</>, perform an <acronym>SSL</acronym> startup handshake
-    (not described here, part of the <acronym>SSL</acronym>
-    specification) with the server.  If this is successful, continue
-    with sending the usual StartupMessage.  In this case the
-    StartupMessage and all subsequent data will be
-    <acronym>SSL</acronym>-encrypted.  To continue after
-    <literal>N</>, send the usual StartupMessage and proceed without
-    encryption.
-   </para>
-
-   <para>
-    The frontend should also be prepared to handle an ErrorMessage
-    response to SSLRequest from the server.  This would only occur if
-    the server predates the addition of <acronym>SSL</acronym> support
-    to <productname>PostgreSQL</>.  In this case the connection must
-    be closed, but the frontend might choose to open a fresh connection
-    and proceed without requesting <acronym>SSL</acronym>.
-   </para>
-
-   <para>
-    An initial SSLRequest can also be used in a connection that is being
-    opened to send a CancelRequest message.
-   </para>
-
-   <para>
-    While the protocol itself does not provide a way for the server to
-    force <acronym>SSL</acronym> encryption, the administrator can
-    configure the server to reject unencrypted sessions as a byproduct
-    of authentication checking.
-   </para>
-  </sect2>
- </sect1>
-
-<sect1 id="protocol-replication">
-<title>Streaming Replication Protocol</title>
-
-&pgnotice;
-<para>
-To initiate streaming replication, the frontend sends the
-<literal>replication</> parameter in the startup message. This tells the
-backend to go into walsender mode, wherein a small set of replication commands
-can be issued instead of SQL statements. Only the simple query protocol can be
-used in walsender mode.
-
-The commands accepted in walsender mode are:
-
-<variablelist>
-  <varlistentry>
-    <term>IDENTIFY_SYSTEM</term>
-    <listitem>
-     <para>
-      Requests the server to identify itself. Server replies with a result
-      set of a single row, containing three fields:
-     </para>
-
-     <para>
-      <variablelist>
-      <varlistentry>
-      <term>
-       systemid
-      </term>
-      <listitem>
-      <para>
-       The unique system identifier identifying the cluster. This
-       can be used to check that the base backup used to initialize the
-       standby came from the same cluster.
-      </para>
-      </listitem>
-      </varlistentry>
-
-      <varlistentry>
-      <term>
-       timeline
-      </term>
-      <listitem>
-      <para>
-       Current TimelineID. Also useful to check that the standby is
-       consistent with the master.
-      </para>
-      </listitem>
-      </varlistentry>
-
-      <varlistentry>
-      <term>
-       xlogpos
-      </term>
-      <listitem>
-      <para>
-       Current xlog write location. Useful to get a known location in the
-       transaction log where streaming can start.
-      </para>
-      </listitem>
-      </varlistentry>
-
-      </variablelist>
-     </para>
-    </listitem>
-  </varlistentry>
-
-  <varlistentry>
-    <term>START_REPLICATION <replaceable>XXX</>/<replaceable>XXX</></term>
-    <listitem>
-     <para>
-      Instructs server to start streaming WAL, starting at
-      WAL position <replaceable>XXX</>/<replaceable>XXX</>.
-      The server can reply with an error, e.g. if the requested section of WAL
-      has already been recycled. On success, server responds with a
-      CopyBothResponse message, and then starts to stream WAL to the frontend.
-      WAL will continue to be streamed until the connection is broken;
-      no further commands will be accepted.
-     </para>
-
-     <para>
-      WAL data is sent as a series of CopyData messages.  (This allows
-      other information to be intermixed; in particular the server can send
-      an ErrorResponse message if it encounters a failure after beginning
-      to stream.)  The payload in each CopyData message follows this format:
-     </para>
-
-     <para>
-      <variablelist>
-      <varlistentry>
-      <term>
-          XLogData (B)
-      </term>
-      <listitem>
-      <para>
-      <variablelist>
-      <varlistentry>
-      <term>
-          Byte1('w')
-      </term>
-      <listitem>
-      <para>
-          Identifies the message as WAL data.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte8
-      </term>
-      <listitem>
-      <para>
-          The starting point of the WAL data in this message, given in
-          XLogRecPtr format.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte8
-      </term>
-      <listitem>
-      <para>
-          The current end of WAL on the server, given in
-          XLogRecPtr format.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte8
-      </term>
-      <listitem>
-      <para>
-          The server's system clock at the time of transmission,
-          given in TimestampTz format.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte<replaceable>n</replaceable>
-      </term>
-      <listitem>
-      <para>
-          A section of the WAL data stream.
-      </para>
-      </listitem>
-      </varlistentry>
-      </variablelist>
-      </para>
-      </listitem>
-      </varlistentry>
-      </variablelist>
-     </para>
-     <para>
-       A single WAL record is never split across two CopyData messages.
-       When a WAL record crosses a WAL page boundary, and is therefore
-       already split using continuation records, it can be split at the page
-       boundary. In other words, the first main WAL record and its
-       continuation records can be sent in different CopyData messages.
-     </para>
-     <para>
-       Note that all fields within the WAL data and the above-described header
-       will be in the sending server's native format.  Endianness, and the
-       format for the timestamp, are unpredictable unless the receiver has
-       verified that the sender's system identifier matches its own
-       <filename>pg_control</> contents.
-     </para>
-     <para>
-       If the WAL sender process is terminated normally (during postmaster
-       shutdown), it will send a CommandComplete message before exiting.
-       This might not happen during an abnormal shutdown, of course.
-     </para>
-
-     <para>
-       The receiving process can send replies back to the sender at any time,
-       using one of the following message formats (also in the payload of a
-       CopyData message):
-     </para>
-
-     <para>
-      <variablelist>
-      <varlistentry>
-      <term>
-          Standby status update (F)
-      </term>
-      <listitem>
-      <para>
-      <variablelist>
-      <varlistentry>
-      <term>
-          Byte1('r')
-      </term>
-      <listitem>
-      <para>
-          Identifies the message as a receiver status update.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte8
-      </term>
-      <listitem>
-      <para>
-          The location of the last WAL byte + 1 received and written to disk
-          in the standby, in XLogRecPtr format.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte8
-      </term>
-      <listitem>
-      <para>
-          The location of the last WAL byte + 1 flushed to disk in
-          the standby, in XLogRecPtr format.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte8
-      </term>
-      <listitem>
-      <para>
-          The location of the last WAL byte + 1 applied in the standby, in
-          XLogRecPtr format.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte8
-      </term>
-      <listitem>
-      <para>
-          The server's system clock at the time of transmission,
-          given in TimestampTz format.
-      </para>
-      </listitem>
-      </varlistentry>
-      </variablelist>
-      </para>
-      </listitem>
-      </varlistentry>
-      </variablelist>
-     </para>
-
-     <para>
-      <variablelist>
-      <varlistentry>
-      <term>
-          Hot Standby feedback message (F)
-      </term>
-      <listitem>
-      <para>
-      <variablelist>
-      <varlistentry>
-      <term>
-          Byte1('h')
-      </term>
-      <listitem>
-      <para>
-          Identifies the message as a Hot Standby feedback message.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte8
-      </term>
-      <listitem>
-      <para>
-          The server's system clock at the time of transmission,
-          given in TimestampTz format.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte4
-      </term>
-      <listitem>
-      <para>
-          The standby's current xmin.
-      </para>
-      </listitem>
-      </varlistentry>
-      <varlistentry>
-      <term>
-          Byte4
-      </term>
-      <listitem>
-      <para>
-          The standby's current epoch.
-      </para>
-      </listitem>
-      </varlistentry>
-      </variablelist>
-      </para>
-      </listitem>
-      </varlistentry>
-      </variablelist>
-     </para>
-    </listitem>
-  </varlistentry>
-
-  <varlistentry>
-    <term>BASE_BACKUP [<literal>LABEL</literal> <replaceable>'label'</replaceable>] [<literal>PROGRESS</literal>] [<literal>FAST</literal>] [<literal>WAL</literal>] [<literal>NOWAIT</literal>]</term>
-    <listitem>
-     <para>
-      Instructs the server to start streaming a base backup.
-      The system will automatically be put in backup mode before the backup
-      is started, and taken out of it when the backup is complete. The
-      following options are accepted:
-      <variablelist>
-       <varlistentry>
-        <term><literal>LABEL</literal> <replaceable>'label'</replaceable></term>
-        <listitem>
-         <para>
-          Sets the label of the backup. If none is specified, a backup label
-          of <literal>base backup</literal> will be used. The quoting rules
-          for the label are the same as a standard SQL string with
-          <xref linkend="guc-standard-conforming-strings"> turned on.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>PROGRESS</></term>
-        <listitem>
-         <para>
-          Request information required to generate a progress report. This will
-          send back an approximate size in the header of each tablespace, which
-          can be used to calculate how far along the stream is done. This is
-          calculated by enumerating all the file sizes once before the transfer
-          is even started, and may as such have a negative impact on the
-          performance - in particular it may take longer before the first data
-          is streamed. Since the database files can change during the backup,
-          the size is only approximate and may both grow and shrink between
-          the time of approximation and the sending of the actual files.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>FAST</></term>
-        <listitem>
-         <para>
-          Request a fast checkpoint.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>WAL</literal></term>
-        <listitem>
-         <para>
-          Include the necessary WAL segments in the backup. This will include
-          all the files between start and stop backup in the
-          <filename>pg_xlog</filename> directory of the base directory tar
-          file.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>NOWAIT</literal></term>
-        <listitem>
-         <para>
-          By default, the backup will wait until the last required xlog
-          segment has been archived, or emit a warning if log archiving is
-          not enabled. Specifying <literal>NOWAIT</literal> disables both
-          the waiting and the warning, leaving the client responsible for
-          ensuring the required log is available.
-         </para>
-         </listitem>
-       </varlistentry>
-      </variablelist>
-     </para>
-     <para>
-      When the backup is started, the server will first send two
-      ordinary result sets, followed by one or more CopyResponse
-      results.
-     </para>
-     <para>
-      The first ordinary result set contains the starting position of the
-      backup, given in XLogRecPtr format as a single column in a single row.
-     </para>
-     <para>
-      The second ordinary result set has one row for each tablespace.
-      The fields in this row are:
-      <variablelist>
-       <varlistentry>
-        <term>spcoid</term>
-        <listitem>
-         <para>
-          The oid of the tablespace, or <literal>NULL</> if it's the base
-          directory.
-         </para>
-        </listitem>
-       </varlistentry>
-       <varlistentry>
-        <term>spclocation</term>
-        <listitem>
-         <para>
-          The full path of the tablespace directory, or <literal>NULL</>
-          if it's the base directory.
-         </para>
-        </listitem>
-       </varlistentry>
-       <varlistentry>
-        <term>size</term>
-        <listitem>
-         <para>
-          The approximate size of the tablespace, if progress report has
-          been requested; otherwise it's <literal>NULL</>.
-         </para>
-        </listitem>
-       </varlistentry>
-      </variablelist>
-     </para>
-     <para>
-      After the second regular result set, one or more CopyResponse results
-      will be sent, one for PGDATA and one for each additional tablespace other
-      than <literal>pg_default</> and <literal>pg_global</>. The data in
-      the CopyResponse results will be a tar format (using ustar00
-      extensions) dump of the tablespace contents. After the tar data is
-      complete, a final ordinary result set will be sent.
-     </para>
-
-     <para>
-      The tar archive for the data directory and each tablespace will contain
-      all files in the directories, regardless of whether they are
-      <productname>PostgreSQL</> files or other files added to the same
-      directory. The only excluded files are:
-      <itemizedlist spacing="compact" mark="bullet">
-       <listitem>
-        <para>
-         <filename>postmaster.pid</>
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         <filename>pg_xlog</>, including subdirectories. If the backup is run
-         with wal files included, a synthesized version of pg_xlog will be
-         included, but it will only contain the files necessary for the
-         backup to work, not the rest of the contents.
-        </para>
-       </listitem>
-      </itemizedlist>
-      Owner, group and file mode are set if the underlying filesystem on
-      the server supports it.
-     </para>
-     <para>
-      Once all tablespaces have been sent, a final regular result set will
-      be sent. This result set contains the end position of the
-      backup, given in XLogRecPtr format as a single column in a single row.
-     </para>
-    </listitem>
-  </varlistentry>
-</variablelist>
-
-</para>
-
-</sect1>
-
-<sect1 id="protocol-message-types">
-<title>Message Data Types</title>
-
-&pgnotice;
-<para>
-This section describes the base data types used in messages.
-
-<variablelist>
-
-<varlistentry>
-<term>
-        Int<replaceable>n</replaceable>(<replaceable>i</replaceable>)
-</term>
-<listitem>
-<para>
-                An <replaceable>n</replaceable>-bit integer in network byte
-                order (most significant byte first).
-                If <replaceable>i</replaceable> is specified it
-                is the exact value that will appear, otherwise the value
-                is variable.  Eg. Int16, Int32(42).
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-        Int<replaceable>n</replaceable>[<replaceable>k</replaceable>]
-</term>
-<listitem>
-<para>
-                An array of <replaceable>k</replaceable>
-                <replaceable>n</replaceable>-bit integers, each in network
-                byte order.  The array length <replaceable>k</replaceable>
-                is always determined by an earlier field in the message.
-                Eg. Int16[M].
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-        String(<replaceable>s</replaceable>)
-</term>
-<listitem>
-<para>
-                A null-terminated string (C-style string).  There is no
-                specific length limitation on strings.
-                If <replaceable>s</replaceable> is specified it is the exact
-                value that will appear, otherwise the value is variable.
-                Eg. String, String("user").
-</para>
-
-<note>
-<para>
-<emphasis>There is no predefined limit</emphasis> on the length of a string
-that can be returned by the backend.  Good coding strategy for a frontend
-is to use an expandable buffer so that anything that fits in memory can be
-accepted.  If that's not feasible, read the full string and discard trailing
-characters that don't fit into your fixed-size buffer.
-</para>
-</note>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-        Byte<replaceable>n</replaceable>(<replaceable>c</replaceable>)
-</term>
-<listitem>
-<para>
-                Exactly <replaceable>n</replaceable> bytes.  If the field
-                width <replaceable>n</replaceable> is not a constant, it is
-                always determinable from an earlier field in the message.
-                If <replaceable>c</replaceable> is specified it is the exact
-                value.  Eg. Byte2, Byte1('\n').
-</para>
-</listitem>
-</varlistentry>
-
-</variablelist>
-</para>
-</sect1>
-
-<sect1 id="protocol-message-formats">
-<title>Message Formats</title>
-
-&pgnotice;
-<para>
-This section describes the detailed format of each message.  Each is marked to
-indicate that it can be sent by a frontend (F), a backend (B), or both
-(F &amp; B).
-Notice that although each message includes a byte count at the beginning,
-the message format is defined so that the message end can be found without
-reference to the byte count.  This aids validity checking.  (The CopyData
-message is an exception, because it forms part of a data stream; the contents
-of any individual CopyData message cannot be interpretable on their own.)
-</para>
-
-<variablelist>
-
-
-<varlistentry>
-<term>
-AuthenticationOk (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('R')
-</term>
-<listitem>
-<para>
-                Identifies the message as an authentication request.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(8)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(0)
-</term>
-<listitem>
-<para>
-                Specifies that the authentication was successful.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-AuthenticationKerberosV5 (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('R')
-</term>
-<listitem>
-<para>
-                Identifies the message as an authentication request.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(8)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(2)
-</term>
-<listitem>
-<para>
-                Specifies that Kerberos V5 authentication is required.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-AuthenticationCleartextPassword (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('R')
-</term>
-<listitem>
-<para>
-                Identifies the message as an authentication request.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(8)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(3)
-</term>
-<listitem>
-<para>
-                Specifies that a clear-text password is required.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-AuthenticationMD5Password (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('R')
-</term>
-<listitem>
-<para>
-                Identifies the message as an authentication request.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(12)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(5)
-</term>
-<listitem>
-<para>
-                Specifies that an MD5-encrypted password is required.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Byte4
-</term>
-<listitem>
-<para>
-                The salt to use when encrypting the password.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-AuthenticationSCMCredential (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('R')
-</term>
-<listitem>
-<para>
-                Identifies the message as an authentication request.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(8)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(6)
-</term>
-<listitem>
-<para>
-                Specifies that an SCM credentials message is required.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-AuthenticationGSS (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('R')
-</term>
-<listitem>
-<para>
-                Identifies the message as an authentication request.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(8)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(7)
-</term>
-<listitem>
-<para>
-                Specifies that GSSAPI authentication is required.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-AuthenticationSSPI (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('R')
-</term>
-<listitem>
-<para>
-                Identifies the message as an authentication request.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(8)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(9)
-</term>
-<listitem>
-<para>
-                Specifies that SSPI authentication is required.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-AuthenticationGSSContinue (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('R')
-</term>
-<listitem>
-<para>
-                Identifies the message as an authentication request.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(8)
-</term>
-<listitem>
-<para>
-                Specifies that this message contains GSSAPI or SSPI data.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Byte<replaceable>n</replaceable>
-</term>
-<listitem>
-<para>
-                GSSAPI or SSPI authentication data.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-BackendKeyData (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('K')
-</term>
-<listitem>
-<para>
-                Identifies the message as cancellation key data.
-                The frontend must save these values if it wishes to be
-                able to issue CancelRequest messages later.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(12)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The process ID of this backend.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The secret key of this backend.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-Bind (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('B')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Bind command.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The name of the destination portal
-                (an empty string selects the unnamed portal).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The name of the source prepared statement
-                (an empty string selects the unnamed prepared statement).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The number of parameter format codes that follow
-                (denoted <replaceable>C</> below).
-                This can be zero to indicate that there are no parameters
-                or that the parameters all use the default format (text);
-                or one, in which case the specified format code is applied
-                to all parameters; or it can equal the actual number of
-                parameters.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16[<replaceable>C</>]
-</term>
-<listitem>
-<para>
-                The parameter format codes.  Each must presently be
-                zero (text) or one (binary).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The number of parameter values that follow (possibly zero).
-                This must match the number of parameters needed by the query.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        Next, the following pair of fields appear for each parameter:
-<variablelist>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The length of the parameter value, in bytes (this count
-                does not include itself).  Can be zero.
-                As a special case, -1 indicates a NULL parameter value.
-                No value bytes follow in the NULL case.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Byte<replaceable>n</replaceable>
-</term>
-<listitem>
-<para>
-                The value of the parameter, in the format indicated by the
-                associated format code.
-                <replaceable>n</replaceable> is the above length.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        After the last parameter, the following fields appear:
-<variablelist>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The number of result-column format codes that follow
-                (denoted <replaceable>R</> below).
-                This can be zero to indicate that there are no result columns
-                or that the result columns should all use the default format
-                (text);
-                or one, in which case the specified format code is applied
-                to all result columns (if any); or it can equal the actual
-                number of result columns of the query.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16[<replaceable>R</>]
-</term>
-<listitem>
-<para>
-                The result-column format codes.  Each must presently be
-                zero (text) or one (binary).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-BindComplete (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('2')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Bind-complete indicator.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(4)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-CancelRequest (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Int32(16)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(80877102)
-</term>
-<listitem>
-<para>
-                The cancel request code.  The value is chosen to contain
-                <literal>1234</> in the most significant 16 bits, and <literal>5678</> in the
-                least 16 significant bits.  (To avoid confusion, this code
-                must not be the same as any protocol version number.)
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The process ID of the target backend.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The secret key for the target backend.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-Close (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('C')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Close command.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Byte1
-</term>
-<listitem>
-<para>
-                '<literal>S</>' to close a prepared statement; or
-                '<literal>P</>' to close a portal.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The name of the prepared statement or portal to close
-                (an empty string selects the unnamed prepared statement
-                or portal).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-CloseComplete (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('3')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Close-complete indicator.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(4)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-CommandComplete (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('C')
-</term>
-<listitem>
-<para>
-                Identifies the message as a command-completed response.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-       <para>
-        The command tag.  This is usually a single
-        word that identifies which SQL command was completed.
-       </para>
-
-       <para>
-        For an <command>INSERT</command> command, the tag is
-        <literal>INSERT <replaceable>oid</replaceable>
-        <replaceable>rows</replaceable></literal>, where
-        <replaceable>rows</replaceable> is the number of rows
-        inserted. <replaceable>oid</replaceable> is the object ID
-        of the inserted row if <replaceable>rows</replaceable> is 1
-        and the target table has OIDs;
-        otherwise <replaceable>oid</replaceable> is 0.
-       </para>
-
-       <para>
-        For a <command>DELETE</command> command, the tag is
-        <literal>DELETE <replaceable>rows</replaceable></literal> where
-        <replaceable>rows</replaceable> is the number of rows deleted.
-       </para>
-
-       <para>
-        For an <command>UPDATE</command> command, the tag is
-        <literal>UPDATE <replaceable>rows</replaceable></literal> where
-        <replaceable>rows</replaceable> is the number of rows updated.
-       </para>
-
-       <para>
-        For a <command>SELECT</command> or <command>CREATE TABLE AS</command>
-        command, the tag is <literal>SELECT <replaceable>rows</replaceable></literal>
-        where <replaceable>rows</replaceable> is the number of rows retrieved.
-       </para>
-
-       <para>
-        For a <command>MOVE</command> command, the tag is
-        <literal>MOVE <replaceable>rows</replaceable></literal> where
-        <replaceable>rows</replaceable> is the number of rows the
-        cursor's position has been changed by.
-       </para>
-
-       <para>
-        For a <command>FETCH</command> command, the tag is
-        <literal>FETCH <replaceable>rows</replaceable></literal> where
-        <replaceable>rows</replaceable> is the number of rows that
-        have been retrieved from the cursor.
-       </para>
-
-       <para>
-        For a <command>COPY</command> command, the tag is
-        <literal>COPY <replaceable>rows</replaceable></literal> where
-        <replaceable>rows</replaceable> is the number of rows copied.
-        (Note: the row count appears only in
-        <productname>PostgreSQL</productname> 8.2 and later.)
-       </para>
-
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-CopyData (F &amp; B)
-</term>
-<listitem>
-<para>
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('d')
-</term>
-<listitem>
-<para>
-                Identifies the message as <command>COPY</command> data.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Byte<replaceable>n</replaceable>
-</term>
-<listitem>
-<para>
-                Data that forms part of a <command>COPY</command> data stream.  Messages sent
-                from the backend will always correspond to single data rows,
-                but messages sent by frontends might divide the data stream
-                arbitrarily.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-CopyDone (F &amp; B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('c')
-</term>
-<listitem>
-<para>
-                Identifies the message as a <command>COPY</command>-complete indicator.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(4)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-CopyFail (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('f')
-</term>
-<listitem>
-<para>
-                Identifies the message as a <command>COPY</command>-failure indicator.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                An error message to report as the cause of failure.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-CopyInResponse (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('G')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Start Copy In response.
-                The frontend must now send copy-in data (if not
-                prepared to do so, send a CopyFail message).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int8
-</term>
-<listitem>
-<para>
-                0 indicates the overall <command>COPY</command> format is textual (rows
-                separated by newlines, columns separated by separator
-                characters, etc).
-                1 indicates the overall copy format is binary (similar
-                to DataRow format).
-                See <xref linkend="sql-copy">
-                for more information.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The number of columns in the data to be copied
-                (denoted <replaceable>N</> below).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16[<replaceable>N</>]
-</term>
-<listitem>
-<para>
-                The format codes to be used for each column.
-                Each must presently be zero (text) or one (binary).
-                All must be zero if the overall copy format is textual.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-CopyOutResponse (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('H')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Start Copy Out response.
-                This message will be followed by copy-out data.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int8
-</term>
-<listitem>
-<para>
-                0 indicates the overall <command>COPY</command> format
-                is textual (rows separated by newlines, columns
-                separated by separator characters, etc). 1 indicates
-                the overall copy format is binary (similar to DataRow
-                format). See <xref linkend="sql-copy"> for more information.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The number of columns in the data to be copied
-                (denoted <replaceable>N</> below).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16[<replaceable>N</>]
-</term>
-<listitem>
-<para>
-                The format codes to be used for each column.
-                Each must presently be zero (text) or one (binary).
-                All must be zero if the overall copy format is textual.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-CopyBothResponse (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('W')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Start Copy Both response.
-                This message is used only for Streaming Replication.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int8
-</term>
-<listitem>
-<para>
-                0 indicates the overall <command>COPY</command> format
-                is textual (rows separated by newlines, columns
-                separated by separator characters, etc). 1 indicates
-                the overall copy format is binary (similar to DataRow
-                format). See <xref linkend="sql-copy"> for more information.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The number of columns in the data to be copied
-                (denoted <replaceable>N</> below).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16[<replaceable>N</>]
-</term>
-<listitem>
-<para>
-                The format codes to be used for each column.
-                Each must presently be zero (text) or one (binary).
-                All must be zero if the overall copy format is textual.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-DataRow (B)
-</term>
-<listitem>
-<para>
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('D')
-</term>
-<listitem>
-<para>
-                Identifies the message as a data row.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The number of column values that follow (possibly zero).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        Next, the following pair of fields appear for each column:
-<variablelist>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The length of the column value, in bytes (this count
-                does not include itself).  Can be zero.
-                As a special case, -1 indicates a NULL column value.
-                No value bytes follow in the NULL case.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Byte<replaceable>n</replaceable>
-</term>
-<listitem>
-<para>
-                The value of the column, in the format indicated by the
-                associated format code.
-                <replaceable>n</replaceable> is the above length.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-Describe (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('D')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Describe command.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Byte1
-</term>
-<listitem>
-<para>
-                '<literal>S</>' to describe a prepared statement; or
-                '<literal>P</>' to describe a portal.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The name of the prepared statement or portal to describe
-                (an empty string selects the unnamed prepared statement
-                or portal).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-EmptyQueryResponse (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('I')
-</term>
-<listitem>
-<para>
-                Identifies the message as a response to an empty query string.
-                (This substitutes for CommandComplete.)
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(4)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-ErrorResponse (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('E')
-</term>
-<listitem>
-<para>
-                Identifies the message as an error.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        The message body consists of one or more identified fields,
-        followed by a zero byte as a terminator.  Fields can appear in
-        any order.  For each field there is the following:
-<variablelist>
-<varlistentry>
-<term>
-        Byte1
-</term>
-<listitem>
-<para>
-                A code identifying the field type; if zero, this is
-                the message terminator and no string follows.
-                The presently defined field types are listed in
-                <xref linkend="protocol-error-fields">.
-                Since more field types might be added in future,
-                frontends should silently ignore fields of unrecognized
-                type.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The field value.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-Execute (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('E')
-</term>
-<listitem>
-<para>
-                Identifies the message as an Execute command.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The name of the portal to execute
-                (an empty string selects the unnamed portal).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Maximum number of rows to return, if portal contains
-                a query that returns rows (ignored otherwise).  Zero
-                denotes <quote>no limit</>.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-Flush (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('H')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Flush command.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(4)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-FunctionCall (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('F')
-</term>
-<listitem>
-<para>
-                Identifies the message as a function call.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Specifies the object ID of the function to call.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The number of argument format codes that follow
-                (denoted <replaceable>C</> below).
-                This can be zero to indicate that there are no arguments
-                or that the arguments all use the default format (text);
-                or one, in which case the specified format code is applied
-                to all arguments; or it can equal the actual number of
-                arguments.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16[<replaceable>C</>]
-</term>
-<listitem>
-<para>
-                The argument format codes.  Each must presently be
-                zero (text) or one (binary).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                Specifies the number of arguments being supplied to the
-                function.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        Next, the following pair of fields appear for each argument:
-<variablelist>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The length of the argument value, in bytes (this count
-                does not include itself).  Can be zero.
-                As a special case, -1 indicates a NULL argument value.
-                No value bytes follow in the NULL case.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Byte<replaceable>n</replaceable>
-</term>
-<listitem>
-<para>
-                The value of the argument, in the format indicated by the
-                associated format code.
-                <replaceable>n</replaceable> is the above length.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        After the last argument, the following field appears:
-<variablelist>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The format code for the function result. Must presently be
-                zero (text) or one (binary).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-FunctionCallResponse (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('V')
-</term>
-<listitem>
-<para>
-                Identifies the message as a function call result.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The length of the function result value, in bytes (this count
-                does not include itself).  Can be zero.
-                As a special case, -1 indicates a NULL function result.
-                No value bytes follow in the NULL case.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Byte<replaceable>n</replaceable>
-</term>
-<listitem>
-<para>
-                The value of the function result, in the format indicated by
-                the associated format code.
-                <replaceable>n</replaceable> is the above length.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-NoData (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('n')
-</term>
-<listitem>
-<para>
-                Identifies the message as a no-data indicator.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(4)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-NoticeResponse (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('N')
-</term>
-<listitem>
-<para>
-                Identifies the message as a notice.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        The message body consists of one or more identified fields,
-        followed by a zero byte as a terminator.  Fields can appear in
-        any order.  For each field there is the following:
-<variablelist>
-<varlistentry>
-<term>
-        Byte1
-</term>
-<listitem>
-<para>
-                A code identifying the field type; if zero, this is
-                the message terminator and no string follows.
-                The presently defined field types are listed in
-                <xref linkend="protocol-error-fields">.
-                Since more field types might be added in future,
-                frontends should silently ignore fields of unrecognized
-                type.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The field value.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-NotificationResponse (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('A')
-</term>
-<listitem>
-<para>
-                Identifies the message as a notification response.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The process ID of the notifying backend process.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The name of the channel that the notify has been raised on.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The <quote>payload</> string passed from the notifying process.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-ParameterDescription (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('t')
-</term>
-<listitem>
-<para>
-                Identifies the message as a parameter description.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The number of parameters used by the statement
-                (can be zero).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        Then, for each parameter, there is the following:
-<variablelist>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Specifies the object ID of the parameter data type.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-ParameterStatus (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('S')
-</term>
-<listitem>
-<para>
-                Identifies the message as a run-time parameter status report.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The name of the run-time parameter being reported.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The current value of the parameter.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-Parse (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('P')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Parse command.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The name of the destination prepared statement
-                (an empty string selects the unnamed prepared statement).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The query string to be parsed.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The number of parameter data types specified
-                (can be zero).  Note that this is not an indication of
-                the number of parameters that might appear in the
-                query string, only the number that the frontend wants to
-                prespecify types for.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        Then, for each parameter, there is the following:
-<variablelist>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Specifies the object ID of the parameter data type.
-                Placing a zero here is equivalent to leaving the type
-                unspecified.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-ParseComplete (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('1')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Parse-complete indicator.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(4)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-PasswordMessage (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('p')
-</term>
-<listitem>
-<para>
-                Identifies the message as a password response. Note that
-                this is also used for GSSAPI and SSPI response messages
-                (which is really a design error, since the contained data
-                is not a null-terminated string in that case, but can be
-                arbitrary binary data).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The password (encrypted, if requested).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-PortalSuspended (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('s')
-</term>
-<listitem>
-<para>
-                Identifies the message as a portal-suspended indicator.
-                Note this only appears if an Execute message's row-count limit
-                was reached.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(4)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-Query (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('Q')
-</term>
-<listitem>
-<para>
-                Identifies the message as a simple query.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The query string itself.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-ReadyForQuery (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('Z')
-</term>
-<listitem>
-<para>
-                Identifies the message type.  ReadyForQuery is sent
-                whenever the backend is ready for a new query cycle.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(5)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Byte1
-</term>
-<listitem>
-<para>
-                Current backend transaction status indicator.
-                Possible values are '<literal>I</>' if idle (not in
-                a transaction block); '<literal>T</>' if in a transaction
-                block; or '<literal>E</>' if in a failed transaction
-                block (queries will be rejected until block is ended).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-RowDescription (B)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('T')
-</term>
-<listitem>
-<para>
-                Identifies the message as a row description.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                Specifies the number of fields in a row (can be zero).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        Then, for each field, there is the following:
-<variablelist>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The field name.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                If the field can be identified as a column of a specific
-                table, the object ID of the table; otherwise zero.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                If the field can be identified as a column of a specific
-                table, the attribute number of the column; otherwise zero.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The object ID of the field's data type.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The data type size (see <varname>pg_type.typlen</>).
-                Note that negative values denote variable-width types.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                The type modifier (see <varname>pg_attribute.atttypmod</>).
-                The meaning of the modifier is type-specific.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int16
-</term>
-<listitem>
-<para>
-                The format code being used for the field.  Currently will
-                be zero (text) or one (binary).  In a RowDescription
-                returned from the statement variant of Describe, the
-                format code is not yet known and will always be zero.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-SSLRequest (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Int32(8)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(80877103)
-</term>
-<listitem>
-<para>
-                The <acronym>SSL</acronym> request code.  The value is chosen to contain
-                <literal>1234</> in the most significant 16 bits, and <literal>5679</> in the
-                least 16 significant bits.  (To avoid confusion, this code
-                must not be the same as any protocol version number.)
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-StartupMessage (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Int32
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(196608)
-</term>
-<listitem>
-<para>
-                The protocol version number.  The most significant 16 bits are
-                the major version number (3 for the protocol described here).
-                The least significant 16 bits are the minor version number
-                (0 for the protocol described here).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-        The protocol version number is followed by one or more pairs of
-        parameter name and value strings.  A zero byte is required as a
-        terminator after the last name/value pair.
-        Parameters can appear in any
-        order.  <literal>user</> is required, others are optional.
-        Each parameter is specified as:
-<variablelist>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The parameter name.  Currently recognized names are:
-
-<variablelist>
-<varlistentry>
-<term>
-                <literal>user</>
-</term>
-<listitem>
-<para>
-                        The database user name to connect as.  Required;
-                        there is no default.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-                <literal>database</>
-</term>
-<listitem>
-<para>
-                        The database to connect to.  Defaults to the user name.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-                <literal>options</>
-</term>
-<listitem>
-<para>
-                        Command-line arguments for the backend.  (This is
-                        deprecated in favor of setting individual run-time
-                        parameters.)
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-                In addition to the above, any run-time parameter that can be
-                set at backend start time might be listed.  Such settings
-                will be applied during backend start (after parsing the
-                command-line options if any).  The values will act as
-                session defaults.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        String
-</term>
-<listitem>
-<para>
-                The parameter value.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-Sync (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('S')
-</term>
-<listitem>
-<para>
-                Identifies the message as a Sync command.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(4)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>
-Terminate (F)
-</term>
-<listitem>
-<para>
-
-<variablelist>
-<varlistentry>
-<term>
-        Byte1('X')
-</term>
-<listitem>
-<para>
-                Identifies the message as a termination.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-        Int32(4)
-</term>
-<listitem>
-<para>
-                Length of message contents in bytes, including self.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</para>
-</listitem>
-</varlistentry>
-
-
-</variablelist>
-
-</sect1>
-
-
-<sect1 id="protocol-error-fields">
-<title>Error and Notice Message Fields</title>
-
-&pgnotice;
-<para>
-This section describes the fields that can appear in ErrorResponse and
-NoticeResponse messages.  Each field type has a single-byte identification
-token.  Note that any given field type should appear at most once per
-message.
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term>
-<literal>S</>
-</term>
-<listitem>
-<para>
-        Severity: the field contents are
-        <literal>ERROR</>, <literal>FATAL</>, or
-        <literal>PANIC</> (in an error message), or
-        <literal>WARNING</>, <literal>NOTICE</>, <literal>DEBUG</>,
-        <literal>INFO</>, or <literal>LOG</> (in a notice message),
-        or a localized translation of one of these.  Always present.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>C</>
-</term>
-<listitem>
-<para>
-        Code: the SQLSTATE code for the error (see <xref
-        linkend="errcodes-appendix">).  Not localizable.  Always present.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>M</>
-</term>
-<listitem>
-<para>
-        Message: the primary human-readable error message.
-        This should be accurate but terse (typically one line).
-        Always present.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>D</>
-</term>
-<listitem>
-<para>
-        Detail: an optional secondary error message carrying more
-        detail about the problem.  Might run to multiple lines.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>H</>
-</term>
-<listitem>
-<para>
-        Hint: an optional suggestion what to do about the problem.
-        This is intended to differ from Detail in that it offers advice
-        (potentially inappropriate) rather than hard facts.
-        Might run to multiple lines.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>P</>
-</term>
-<listitem>
-<para>
-        Position: the field value is a decimal ASCII integer, indicating
-        an error cursor position as an index into the original query string.
-        The first character has index 1, and positions are measured in
-        characters not bytes.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>p</>
-</term>
-<listitem>
-<para>
-        Internal position: this is defined the same as the <literal>P</>
-        field, but it is used when the cursor position refers to an internally
-        generated command rather than the one submitted by the client.
-        The <literal>q</> field will always appear when this field appears.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>q</>
-</term>
-<listitem>
-<para>
-        Internal query: the text of a failed internally-generated command.
-        This could be, for example, a SQL query issued by a PL/pgSQL function.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>W</>
-</term>
-<listitem>
-<para>
-        Where: an indication of the context in which the error occurred.
-        Presently this includes a call stack traceback of active
-        procedural language functions and internally-generated queries.
-        The trace is one entry per line, most recent first.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>F</>
-</term>
-<listitem>
-<para>
-        File: the file name of the source-code location where the error
-        was reported.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>L</>
-</term>
-<listitem>
-<para>
-        Line: the line number of the source-code location where the error
-        was reported.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal>R</>
-</term>
-<listitem>
-<para>
-        Routine: the name of the source-code routine reporting the error.
-</para>
-</listitem>
-</varlistentry>
-
-</variablelist>
-
-<para>
-The client is responsible for formatting displayed information to meet its
-needs; in particular it should break long lines as needed.  Newline characters
-appearing in the error message fields should be treated as paragraph breaks,
-not line breaks.
-</para>
-
-</sect1>
-
-<sect1 id="protocol-changes">
-<title>Summary of Changes since Protocol 2.0</title>
-
-&pgnotice;
-<para>
-This section provides a quick checklist of changes, for the benefit of
-developers trying to update existing client libraries to protocol 3.0.
-</para>
-
-<para>
-The initial startup packet uses a flexible list-of-strings format
-instead of a fixed format.  Notice that session default values for run-time
-parameters can now be specified directly in the startup packet.  (Actually,
-you could do that before using the <literal>options</> field, but given the
-limited width of <literal>options</> and the lack of any way to quote
-whitespace in the values, it wasn't a very safe technique.)
-</para>
-
-<para>
-All messages now have a length count immediately following the message type
-byte (except for startup packets, which have no type byte).  Also note that
-PasswordMessage now has a type byte.
-</para>
-
-<para>
-ErrorResponse and NoticeResponse ('<literal>E</>' and '<literal>N</>')
-messages now contain multiple fields, from which the client code can
-assemble an error message of the desired level of verbosity.  Note that
-individual fields will typically not end with a newline, whereas the single
-string sent in the older protocol always did.
-</para>
-
-<para>
-The ReadyForQuery ('<literal>Z</>') message includes a transaction status
-indicator.
-</para>
-
-<para>
-The distinction between BinaryRow and DataRow message types is gone; the
-single DataRow message type serves for returning data in all formats.
-Note that the layout of DataRow has changed to make it easier to parse.
-Also, the representation of binary values has changed: it is no longer
-directly tied to the server's internal representation.
-</para>
-
-<para>
-There is a new <quote>extended query</> sub-protocol, which adds the frontend
-message types Parse, Bind, Execute, Describe, Close, Flush, and Sync, and the
-backend message types ParseComplete, BindComplete, PortalSuspended,
-ParameterDescription, NoData, and CloseComplete.  Existing clients do not
-have to concern themselves with this sub-protocol, but making use of it
-might allow improvements in performance or functionality.
-</para>
-
-<para>
-<command>COPY</command> data is now encapsulated into CopyData and CopyDone messages.  There
-is a well-defined way to recover from errors during <command>COPY</command>.  The special
-<quote><literal>\.</></quote> last line is not needed anymore, and is not sent
-during <command>COPY OUT</command>.
-(It is still recognized as a terminator during <command>COPY IN</command>, but its use is
-deprecated and will eventually be removed.)  Binary <command>COPY</command> is supported.
-The CopyInResponse and CopyOutResponse messages include fields indicating
-the number of columns and the format of each column.
-</para>
-
-<para>
-The layout of FunctionCall and FunctionCallResponse messages has changed.
-FunctionCall can now support passing NULL arguments to functions.  It also
-can handle passing parameters and retrieving results in either text or
-binary format.  There is no longer any reason to consider FunctionCall a
-potential security hole, since it does not offer direct access to internal
-server data representations.
-</para>
-
-<para>
-The backend sends ParameterStatus ('<literal>S</>') messages during connection
-startup for all parameters it considers interesting to the client library.
-Subsequently, a ParameterStatus message is sent whenever the active value
-changes for any of these parameters.
-</para>
-
-<para>
-The RowDescription ('<literal>T</>') message carries new table OID and column
-number fields for each column of the described row.  It also shows the format
-code for each column.
-</para>
-
-<para>
-The CursorResponse ('<literal>P</>') message is no longer generated by
-the backend.
-</para>
-
-<para>
-The NotificationResponse ('<literal>A</>') message has an additional string
-field, which can carry a <quote>payload</> string passed
-from the <command>NOTIFY</command> event sender.
-</para>
-
-<para>
-The EmptyQueryResponse ('<literal>I</>') message used to include an empty
-string parameter; this has been removed.
-</para>
-
-</sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/queries.sgmlin b/doc-xc/src/sgml/queries.sgmlin
deleted file mode 100644
index 73973d9bf3..0000000000
--- a/doc-xc/src/sgml/queries.sgmlin
+++ /dev/null
@@ -1,2019 +0,0 @@
-<!-- doc/src/sgml/queries.sgml -->
-
-<chapter id="queries">
- <title>Queries</title>
-
- <indexterm zone="queries">
-  <primary>query</primary>
- </indexterm>
-
- <indexterm zone="queries">
-  <primary>SELECT</primary>
- </indexterm>
-
- <para>
-  The previous chapters explained how to create tables, how to fill
-  them with data, and how to manipulate that data.  Now we finally
-  discuss how to retrieve the data from the database.
- </para>
-
-
- <sect1 id="queries-overview">
-  <title>Overview</title>
-
-  <para>
-   The process of retrieving or the command to retrieve data from a
-   database is called a <firstterm>query</firstterm>.  In SQL the
-   <xref linkend="sql-select"> command is
-   used to specify queries.  The general syntax of the
-   <command>SELECT</command> command is
-<synopsis>
-<optional>WITH <replaceable>with_queries</replaceable></optional> SELECT <replaceable>select_list</replaceable> FROM <replaceable>table_expression</replaceable> <optional><replaceable>sort_specification</replaceable></optional>
-</synopsis>
-   The following sections describe the details of the select list, the
-   table expression, and the sort specification.  <literal>WITH</>
-   queries are treated last since they are an advanced feature.
-  </para>
-
-  <para>
-   A simple kind of query has the form:
-<programlisting>
-SELECT * FROM table1;
-</programlisting>
-  Assuming that there is a table called <literal>table1</literal>,
-  this command would retrieve all rows and all columns from
-  <literal>table1</literal>.  (The method of retrieval depends on the
-  client application.  For example, the
-  <application>psql</application> program will display an ASCII-art
-  table on the screen, while client libraries will offer functions to
-  extract individual values from the query result.)  The select list
-  specification <literal>*</literal> means all columns that the table
-  expression happens to provide.  A select list can also select a
-  subset of the available columns or make calculations using the
-  columns.  For example, if
-  <literal>table1</literal> has columns named <literal>a</>,
-  <literal>b</>, and <literal>c</> (and perhaps others) you can make
-  the following query:
-<programlisting>
-SELECT a, b + c FROM table1;
-</programlisting>
-  (assuming that <literal>b</> and <literal>c</> are of a numerical
-  data type).
-  See <xref linkend="queries-select-lists"> for more details.
- </para>
-
- <para>
-  <literal>FROM table1</literal> is a simple kind of
-  table expression: it reads just one table.  In general, table
-  expressions can be complex constructs of base tables, joins, and
-  subqueries.  But you can also omit the table expression entirely and
-  use the <command>SELECT</command> command as a calculator:
-<programlisting>
-SELECT 3 * 4;
-</programlisting>
-  This is more useful if the expressions in the select list return
-  varying results.  For example, you could call a function this way:
-<programlisting>
-SELECT random();
-</programlisting>
-  </para>
- </sect1>
-
-
- <sect1 id="queries-table-expressions">
-  <title>Table Expressions</title>
-
-  <indexterm zone="queries-table-expressions">
-   <primary>table expression</primary>
-  </indexterm>
-  <para>
-   A <firstterm>table expression</firstterm> computes a table.  The
-   table expression contains a <literal>FROM</> clause that is
-   optionally followed by <literal>WHERE</>, <literal>GROUP BY</>, and
-   <literal>HAVING</> clauses.  Trivial table expressions simply refer
-   to a table on disk, a so-called base table, but more complex
-   expressions can be used to modify or combine base tables in various
-   ways.
-  </para>
-
-  <para>
-   The optional <literal>WHERE</>, <literal>GROUP BY</>, and
-   <literal>HAVING</> clauses in the table expression specify a
-   pipeline of successive transformations performed on the table
-   derived in the <literal>FROM</> clause.  All these transformations
-   produce a virtual table that provides the rows that are passed to
-   the select list to compute the output rows of the query.
-  </para>
-
-  <sect2 id="queries-from">
-   <title>The <literal>FROM</literal> Clause</title>
-
-   <para>
-    The <xref linkend="sql-from" endterm="sql-from-title"> derives a
-    table from one or more other tables given in a comma-separated
-    table reference list.
-<synopsis>
-FROM <replaceable>table_reference</replaceable> <optional>, <replaceable>table_reference</replaceable> <optional>, ...</optional></optional>
-</synopsis>
-    A table reference can be a table name (possibly schema-qualified),
-    or a derived table such as a subquery, a table join, or complex
-    combinations of these.  If more than one table reference is listed
-    in the <literal>FROM</> clause they are cross-joined (see below)
-    to form the intermediate virtual table that can then be subject to
-    transformations by the <literal>WHERE</>, <literal>GROUP BY</>,
-    and <literal>HAVING</> clauses and is finally the result of the
-    overall table expression.
-   </para>
-
-   <indexterm>
-    <primary>ONLY</primary>
-   </indexterm>
-
-   <para>
-    When a table reference names a table that is the parent of a
-    table inheritance hierarchy, the table reference produces rows of
-    not only that table but all of its descendant tables, unless the
-    key word <literal>ONLY</> precedes the table name.  However, the
-    reference produces only the columns that appear in the named table
-    &mdash; any columns added in subtables are ignored.
-   </para>
-
-   <sect3 id="queries-join">
-    <title>Joined Tables</title>
-
-    <indexterm zone="queries-join">
-     <primary>join</primary>
-    </indexterm>
-&common;
-    <para>
-     A joined table is a table derived from two other (real or
-     derived) tables according to the rules of the particular join
-     type.  Inner, outer, and cross-joins are available.
-    </para>
-
-    <variablelist>
-     <title>Join Types</title>
-
-     <varlistentry>
-      <term>Cross join</term>
-
-      <indexterm>
-       <primary>join</primary>
-       <secondary>cross</secondary>
-      </indexterm>
-
-      <indexterm>
-       <primary>cross join</primary>
-      </indexterm>
-
-      <listitem>
-<synopsis>
-<replaceable>T1</replaceable> CROSS JOIN <replaceable>T2</replaceable>
-</synopsis>
-
-       <para>
-        For every possible combination of rows from
-        <replaceable>T1</replaceable> and
-        <replaceable>T2</replaceable> (i.e., a Cartesian product),
-        the joined table will contain a
-        row consisting of all columns in <replaceable>T1</replaceable>
-        followed by all columns in <replaceable>T2</replaceable>.  If
-        the tables have N and M rows respectively, the joined
-        table will have N * M rows.
-       </para>
-
-       <para>
-        <literal>FROM <replaceable>T1</replaceable> CROSS JOIN
-        <replaceable>T2</replaceable></literal> is equivalent to
-        <literal>FROM <replaceable>T1</replaceable>,
-        <replaceable>T2</replaceable></literal>.  It is also equivalent to
-        <literal>FROM <replaceable>T1</replaceable> INNER JOIN
-        <replaceable>T2</replaceable> ON TRUE</literal> (see below).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Qualified joins</term>
-
-      <indexterm>
-       <primary>join</primary>
-       <secondary>outer</secondary>
-      </indexterm>
-
-      <indexterm>
-       <primary>outer join</primary>
-      </indexterm>
-
-      <listitem>
-<synopsis>
-<replaceable>T1</replaceable> { <optional>INNER</optional> | { LEFT | RIGHT | FULL } <optional>OUTER</optional> } JOIN <replaceable>T2</replaceable> ON <replaceable>boolean_expression</replaceable>
-<replaceable>T1</replaceable> { <optional>INNER</optional> | { LEFT | RIGHT | FULL } <optional>OUTER</optional> } JOIN <replaceable>T2</replaceable> USING ( <replaceable>join column list</replaceable> )
-<replaceable>T1</replaceable> NATURAL { <optional>INNER</optional> | { LEFT | RIGHT | FULL } <optional>OUTER</optional> } JOIN <replaceable>T2</replaceable>
-</synopsis>
-
-       <para>
-        The words <literal>INNER</literal> and
-        <literal>OUTER</literal> are optional in all forms.
-        <literal>INNER</literal> is the default;
-        <literal>LEFT</literal>, <literal>RIGHT</literal>, and
-        <literal>FULL</literal> imply an outer join.
-       </para>
-
-       <para>
-        The <firstterm>join condition</firstterm> is specified in the
-        <literal>ON</> or <literal>USING</> clause, or implicitly by
-        the word <literal>NATURAL</>.  The join condition determines
-        which rows from the two source tables are considered to
-        <quote>match</quote>, as explained in detail below.
-       </para>
-
-       <para>
-        The <literal>ON</> clause is the most general kind of join
-        condition: it takes a Boolean value expression of the same
-        kind as is used in a <literal>WHERE</> clause.  A pair of rows
-        from <replaceable>T1</> and <replaceable>T2</> match if the
-        <literal>ON</> expression evaluates to true for them.
-       </para>
-
-       <para>
-        <literal>USING</> is a shorthand notation: it takes a
-        comma-separated list of column names, which the joined tables
-        must have in common, and forms a join condition specifying
-        equality of each of these pairs of columns.  Furthermore, the
-        output of <literal>JOIN USING</> has one column for each of
-        the equated pairs of input columns, followed by the
-        remaining columns from each table.  Thus, <literal>USING (a, b,
-        c)</literal> is equivalent to <literal>ON (t1.a = t2.a AND
-        t1.b = t2.b AND t1.c = t2.c)</literal> with the exception that
-        if <literal>ON</> is used there will be two columns
-        <literal>a</>, <literal>b</>, and <literal>c</> in the result,
-        whereas with <literal>USING</> there will be only one of each
-        (and they will appear first if <command>SELECT *</> is used).
-       </para>
-
-       <para>
-        <indexterm>
-         <primary>join</primary>
-         <secondary>natural</secondary>
-        </indexterm>
-        <indexterm>
-         <primary>natural join</primary>
-        </indexterm>
-        Finally, <literal>NATURAL</> is a shorthand form of
-        <literal>USING</>: it forms a <literal>USING</> list
-        consisting of all column names that appear in both
-        input tables.  As with <literal>USING</>, these columns appear
-        only once in the output table.
-       </para>
-
-       <para>
-        The possible types of qualified join are:
-
-       <variablelist>
-        <varlistentry>
-         <term><literal>INNER JOIN</></term>
-
-         <listitem>
-          <para>
-           For each row R1 of T1, the joined table has a row for each
-           row in T2 that satisfies the join condition with R1.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term><literal>LEFT OUTER JOIN</></term>
-
-         <indexterm>
-          <primary>join</primary>
-          <secondary>left</secondary>
-         </indexterm>
-
-         <indexterm>
-          <primary>left join</primary>
-         </indexterm>
-
-         <listitem>
-          <para>
-           First, an inner join is performed.  Then, for each row in
-           T1 that does not satisfy the join condition with any row in
-           T2, a joined row is added with null values in columns of
-           T2.  Thus, the joined table always has at least
-           one row for each row in T1.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term><literal>RIGHT OUTER JOIN</></term>
-
-         <indexterm>
-          <primary>join</primary>
-          <secondary>right</secondary>
-         </indexterm>
-
-         <indexterm>
-          <primary>right join</primary>
-         </indexterm>
-
-         <listitem>
-          <para>
-           First, an inner join is performed.  Then, for each row in
-           T2 that does not satisfy the join condition with any row in
-           T1, a joined row is added with null values in columns of
-           T1.  This is the converse of a left join: the result table
-           will always have a row for each row in T2.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term><literal>FULL OUTER JOIN</></term>
-
-         <listitem>
-          <para>
-           First, an inner join is performed.  Then, for each row in
-           T1 that does not satisfy the join condition with any row in
-           T2, a joined row is added with null values in columns of
-           T2.  Also, for each row of T2 that does not satisfy the
-           join condition with any row in T1, a joined row with null
-           values in the columns of T1 is added.
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    <para>
-     Joins of all types can be chained together or nested: either or
-     both <replaceable>T1</replaceable> and
-     <replaceable>T2</replaceable> can be joined tables.  Parentheses
-     can be used around <literal>JOIN</> clauses to control the join
-     order.  In the absence of parentheses, <literal>JOIN</> clauses
-     nest left-to-right.
-    </para>
-
-    <para>
-     To put this together, assume we have tables <literal>t1</literal>:
-<programlisting>
- num | name
------+------
-   1 | a
-   2 | b
-   3 | c
-</programlisting>
-     and <literal>t2</literal>:
-<programlisting>
- num | value
------+-------
-   1 | xxx
-   3 | yyy
-   5 | zzz
-</programlisting>
-     then we get the following results for the various joins:
-<screen>
-<prompt>=&gt;</> <userinput>SELECT * FROM t1 CROSS JOIN t2;</>
- num | name | num | value
------+------+-----+-------
-   1 | a    |   1 | xxx
-   1 | a    |   3 | yyy
-   1 | a    |   5 | zzz
-   2 | b    |   1 | xxx
-   2 | b    |   3 | yyy
-   2 | b    |   5 | zzz
-   3 | c    |   1 | xxx
-   3 | c    |   3 | yyy
-   3 | c    |   5 | zzz
-(9 rows)
-
-<prompt>=&gt;</> <userinput>SELECT * FROM t1 INNER JOIN t2 ON t1.num = t2.num;</>
- num | name | num | value
------+------+-----+-------
-   1 | a    |   1 | xxx
-   3 | c    |   3 | yyy
-(2 rows)
-
-<prompt>=&gt;</> <userinput>SELECT * FROM t1 INNER JOIN t2 USING (num);</>
- num | name | value
------+------+-------
-   1 | a    | xxx
-   3 | c    | yyy
-(2 rows)
-
-<prompt>=&gt;</> <userinput>SELECT * FROM t1 NATURAL INNER JOIN t2;</>
- num | name | value
------+------+-------
-   1 | a    | xxx
-   3 | c    | yyy
-(2 rows)
-
-<prompt>=&gt;</> <userinput>SELECT * FROM t1 LEFT JOIN t2 ON t1.num = t2.num;</>
- num | name | num | value
------+------+-----+-------
-   1 | a    |   1 | xxx
-   2 | b    |     |
-   3 | c    |   3 | yyy
-(3 rows)
-
-<prompt>=&gt;</> <userinput>SELECT * FROM t1 LEFT JOIN t2 USING (num);</>
- num | name | value
------+------+-------
-   1 | a    | xxx
-   2 | b    |
-   3 | c    | yyy
-(3 rows)
-
-<prompt>=&gt;</> <userinput>SELECT * FROM t1 RIGHT JOIN t2 ON t1.num = t2.num;</>
- num | name | num | value
------+------+-----+-------
-   1 | a    |   1 | xxx
-   3 | c    |   3 | yyy
-     |      |   5 | zzz
-(3 rows)
-
-<prompt>=&gt;</> <userinput>SELECT * FROM t1 FULL JOIN t2 ON t1.num = t2.num;</>
- num | name | num | value
------+------+-----+-------
-   1 | a    |   1 | xxx
-   2 | b    |     |
-   3 | c    |   3 | yyy
-     |      |   5 | zzz
-(4 rows)
-</screen>
-    </para>
-
-    <para>
-     The join condition specified with <literal>ON</> can also contain
-     conditions that do not relate directly to the join.  This can
-     prove useful for some queries but needs to be thought out
-     carefully.  For example:
-<screen>
-<prompt>=&gt;</> <userinput>SELECT * FROM t1 LEFT JOIN t2 ON t1.num = t2.num AND t2.value = 'xxx';</>
- num | name | num | value
------+------+-----+-------
-   1 | a    |   1 | xxx
-   2 | b    |     |
-   3 | c    |     |
-(3 rows)
-</screen>
-     Notice that placing the restriction in the <literal>WHERE</> clause
-     produces a different result:
-<screen>
-<prompt>=&gt;</> <userinput>SELECT * FROM t1 LEFT JOIN t2 ON t1.num = t2.num WHERE t2.value = 'xxx';</>
- num | name | num | value
------+------+-----+-------
-   1 | a    |   1 | xxx
-(1 row)
-</screen>
-     This is because a restriction placed in the <literal>ON</>
-     clause is processed <emphasis>before</> the join, while
-     a restriction placed in the <literal>WHERE</> clause is processed
-     <emphasis>after</> the join.
-    </para>
-   </sect3>
-
-   <sect3 id="queries-table-aliases">
-    <title>Table and Column Aliases</title>
-
-    <indexterm zone="queries-table-aliases">
-     <primary>alias</primary>
-     <secondary>in the FROM clause</secondary>
-    </indexterm>
-
-    <indexterm>
-     <primary>label</primary>
-     <see>alias</see>
-    </indexterm>
-&common;
-    <para>
-     A temporary name can be given to tables and complex table
-     references to be used for references to the derived table in
-     the rest of the query.  This is called a <firstterm>table
-     alias</firstterm>.
-    </para>
-
-    <para>
-     To create a table alias, write
-<synopsis>
-FROM <replaceable>table_reference</replaceable> AS <replaceable>alias</replaceable>
-</synopsis>
-     or
-<synopsis>
-FROM <replaceable>table_reference</replaceable> <replaceable>alias</replaceable>
-</synopsis>
-     The <literal>AS</literal> key word is optional noise.
-     <replaceable>alias</replaceable> can be any identifier.
-    </para>
-
-    <para>
-     A typical application of table aliases is to assign short
-     identifiers to long table names to keep the join clauses
-     readable.  For example:
-<programlisting>
-SELECT * FROM some_very_long_table_name s JOIN another_fairly_long_name a ON s.id = a.num;
-</programlisting>
-    </para>
-
-    <para>
-     The alias becomes the new name of the table reference so far as the
-     current query is concerned &mdash; it is not allowed to refer to the
-     table by the original name elsewhere in the query.  Thus, this is not
-     valid:
-<programlisting>
-SELECT * FROM my_table AS m WHERE my_table.a &gt; 5;    -- wrong
-</programlisting>
-    </para>
-
-    <para>
-     Table aliases are mainly for notational convenience, but it is
-     necessary to use them when joining a table to itself, e.g.:
-<programlisting>
-SELECT * FROM people AS mother JOIN people AS child ON mother.id = child.mother_id;
-</programlisting>
-     Additionally, an alias is required if the table reference is a
-     subquery (see <xref linkend="queries-subqueries">).
-    </para>
-
-    <para>
-     Parentheses are used to resolve ambiguities.  In the following example,
-     the first statement assigns the alias <literal>b</literal> to the second
-     instance of <literal>my_table</>, but the second statement assigns the
-     alias to the result of the join:
-<programlisting>
-SELECT * FROM my_table AS a CROSS JOIN my_table AS b ...
-SELECT * FROM (my_table AS a CROSS JOIN my_table) AS b ...
-</programlisting>
-    </para>
-
-    <para>
-     Another form of table aliasing gives temporary names to the columns of
-     the table, as well as the table itself:
-<synopsis>
-FROM <replaceable>table_reference</replaceable> <optional>AS</optional> <replaceable>alias</replaceable> ( <replaceable>column1</replaceable> <optional>, <replaceable>column2</replaceable> <optional>, ...</optional></optional> )
-</synopsis>
-     If fewer column aliases are specified than the actual table has
-     columns, the remaining columns are not renamed.  This syntax is
-     especially useful for self-joins or subqueries.
-    </para>
-
-    <para>
-     When an alias is applied to the output of a <literal>JOIN</>
-     clause, the alias hides the original
-     name(s) within the <literal>JOIN</>.  For example:
-<programlisting>
-SELECT a.* FROM my_table AS a JOIN your_table AS b ON ...
-</programlisting>
-     is valid SQL, but:
-<programlisting>
-SELECT a.* FROM (my_table AS a JOIN your_table AS b ON ...) AS c
-</programlisting>
-     is not valid; the table alias <literal>a</> is not visible
-     outside the alias <literal>c</>.
-    </para>
-   </sect3>
-
-   <sect3 id="queries-subqueries">
-    <title>Subqueries</title>
-
-    <indexterm zone="queries-subqueries">
-     <primary>subquery</primary>
-    </indexterm>
-&common;
-    <para>
-     Subqueries specifying a derived table must be enclosed in
-     parentheses and <emphasis>must</emphasis> be assigned a table
-     alias name.  (See <xref linkend="queries-table-aliases">.)  For
-     example:
-<programlisting>
-FROM (SELECT * FROM table1) AS alias_name
-</programlisting>
-    </para>
-
-    <para>
-     This example is equivalent to <literal>FROM table1 AS
-     alias_name</literal>.  More interesting cases, which cannot be
-     reduced to a plain join, arise when the subquery involves
-     grouping or aggregation.
-    </para>
-
-    <para>
-     A subquery can also be a <command>VALUES</> list:
-<programlisting>
-FROM (VALUES ('anne', 'smith'), ('bob', 'jones'), ('joe', 'blow'))
-     AS names(first, last)
-</programlisting>
-     Again, a table alias is required.  Assigning alias names to the columns
-     of the <command>VALUES</> list is optional, but is good practice.
-     For more information see <xref linkend="queries-values">.
-    </para>
-   </sect3>
-
-   <sect3 id="queries-tablefunctions">
-    <title>Table Functions</title>
-
-    <indexterm zone="queries-tablefunctions"><primary>table function</></>
-
-    <indexterm zone="queries-tablefunctions">
-     <primary>function</>
-     <secondary>in the FROM clause</>
-    </indexterm>
-
-    <para>
-     Table functions are functions that produce a set of rows, made up
-     of either base data types (scalar types) or composite data types
-     (table rows).  They are used like a table, view, or subquery in
-     the <literal>FROM</> clause of a query. Columns returned by table
-     functions can be included in <literal>SELECT</>,
-     <literal>JOIN</>, or <literal>WHERE</> clauses in the same manner
-     as a table, view, or subquery column.
-    </para>
-
-    <para>
-     If a table function returns a base data type, the single result
-     column name matches the function name. If the function returns a
-     composite type, the result columns get the same names as the
-     individual attributes of the type.
-    </para>
-
-    <para>
-     A table function can be aliased in the <literal>FROM</> clause,
-     but it also can be left unaliased. If a function is used in the
-     <literal>FROM</> clause with no alias, the function name is used
-     as the resulting table name.
-    </para>
-
-    <para>
-     Some examples:
-<programlisting>
-CREATE TABLE foo (fooid int, foosubid int, fooname text);
-
-CREATE FUNCTION getfoo(int) RETURNS SETOF foo AS $$
-    SELECT * FROM foo WHERE fooid = $1;
-$$ LANGUAGE SQL;
-
-SELECT * FROM getfoo(1) AS t1;
-
-SELECT * FROM foo
-    WHERE foosubid IN (
-                        SELECT foosubid
-                        FROM getfoo(foo.fooid) z
-                        WHERE z.fooid = foo.fooid
-                      );
-
-CREATE VIEW vw_getfoo AS SELECT * FROM getfoo(1);
-
-SELECT * FROM vw_getfoo;
-</programlisting>
-    </para>
-
-    <para>
-     In some cases it is useful to define table functions that can
-     return different column sets depending on how they are invoked.
-     To support this, the table function can be declared as returning
-     the pseudotype <type>record</>.  When such a function is used in
-     a query, the expected row structure must be specified in the
-     query itself, so that the system can know how to parse and plan
-     the query.  Consider this example:
-<programlisting>
-SELECT *
-    FROM dblink('dbname=mydb', 'SELECT proname, prosrc FROM pg_proc')
-      AS t1(proname name, prosrc text)
-    WHERE proname LIKE 'bytea%';
-</programlisting>
-     The <xref linkend="CONTRIB-DBLINK-FUNCTION"> function
-     (part of the <xref linkend="dblink"> module>) executes
-     a remote query.  It is declared to return
-     <type>record</> since it might be used for any kind of query.
-     The actual column set must be specified in the calling query so
-     that the parser knows, for example, what <literal>*</> should
-     expand to.
-    </para>
-   </sect3>
-  </sect2>
-
-  <sect2 id="queries-where">
-   <title>The <literal>WHERE</literal> Clause</title>
-
-   <indexterm zone="queries-where">
-    <primary>WHERE</primary>
-   </indexterm>
-
-   <para>
-    The syntax of the <xref linkend="sql-where"
-    endterm="sql-where-title"> is
-<synopsis>
-WHERE <replaceable>search_condition</replaceable>
-</synopsis>
-    where <replaceable>search_condition</replaceable> is any value
-    expression (see <xref linkend="sql-expressions">) that
-    returns a value of type <type>boolean</type>.
-   </para>
-
-   <para>
-    After the processing of the <literal>FROM</> clause is done, each
-    row of the derived virtual table is checked against the search
-    condition.  If the result of the condition is true, the row is
-    kept in the output table, otherwise (i.e., if the result is
-    false or null) it is discarded.  The search condition typically
-    references at least one column of the table generated in the
-    <literal>FROM</> clause; this is not required, but otherwise the
-    <literal>WHERE</> clause will be fairly useless.
-   </para>
-
-   <note>
-    <para>
-     The join condition of an inner join can be written either in
-     the <literal>WHERE</> clause or in the <literal>JOIN</> clause.
-     For example, these table expressions are equivalent:
-<programlisting>
-FROM a, b WHERE a.id = b.id AND b.val &gt; 5
-</programlisting>
-     and:
-<programlisting>
-FROM a INNER JOIN b ON (a.id = b.id) WHERE b.val &gt; 5
-</programlisting>
-     or perhaps even:
-<programlisting>
-FROM a NATURAL JOIN b WHERE b.val &gt; 5
-</programlisting>
-     Which one of these you use is mainly a matter of style.  The
-     <literal>JOIN</> syntax in the <literal>FROM</> clause is
-     probably not as portable to other SQL database management systems,
-     even though it is in the SQL standard.  For
-     outer joins there is no choice:  they must be done in
-     the <literal>FROM</> clause.  The <literal>ON</> or <literal>USING</>
-     clause of an outer join is <emphasis>not</> equivalent to a
-     <literal>WHERE</> condition, because it results in the addition
-     of rows (for unmatched input rows) as well as the removal of rows
-     in the final result.
-    </para>
-   </note>
-
-   <para>
-    Here are some examples of <literal>WHERE</literal> clauses:
-<programlisting>
-SELECT ... FROM fdt WHERE c1 &gt; 5
-
-SELECT ... FROM fdt WHERE c1 IN (1, 2, 3)
-
-SELECT ... FROM fdt WHERE c1 IN (SELECT c1 FROM t2)
-
-SELECT ... FROM fdt WHERE c1 IN (SELECT c3 FROM t2 WHERE c2 = fdt.c1 + 10)
-
-SELECT ... FROM fdt WHERE c1 BETWEEN (SELECT c3 FROM t2 WHERE c2 = fdt.c1 + 10) AND 100
-
-SELECT ... FROM fdt WHERE EXISTS (SELECT c1 FROM t2 WHERE c2 &gt; fdt.c1)
-</programlisting>
-    <literal>fdt</literal> is the table derived in the
-    <literal>FROM</> clause. Rows that do not meet the search
-    condition of the <literal>WHERE</> clause are eliminated from
-    <literal>fdt</literal>. Notice the use of scalar subqueries as
-    value expressions.  Just like any other query, the subqueries can
-    employ complex table expressions.  Notice also how
-    <literal>fdt</literal> is referenced in the subqueries.
-    Qualifying <literal>c1</> as <literal>fdt.c1</> is only necessary
-    if <literal>c1</> is also the name of a column in the derived
-    input table of the subquery.  But qualifying the column name adds
-    clarity even when it is not needed.  This example shows how the column
-    naming scope of an outer query extends into its inner queries.
-   </para>
-  </sect2>
-
-
-  <sect2 id="queries-group">
-   <title>The <literal>GROUP BY</literal> and <literal>HAVING</literal> Clauses</title>
-
-   <indexterm zone="queries-group">
-    <primary>GROUP BY</primary>
-   </indexterm>
-
-   <indexterm zone="queries-group">
-    <primary>grouping</primary>
-   </indexterm>
-
-   <para>
-    After passing the <literal>WHERE</> filter, the derived input
-    table might be subject to grouping, using the <literal>GROUP BY</>
-    clause, and elimination of group rows using the <literal>HAVING</>
-    clause.
-   </para>
-
-<synopsis>
-SELECT <replaceable>select_list</replaceable>
-    FROM ...
-    <optional>WHERE ...</optional>
-    GROUP BY <replaceable>grouping_column_reference</replaceable> <optional>, <replaceable>grouping_column_reference</replaceable></optional>...
-</synopsis>
-&common;
-   <para>
-    The <xref linkend="sql-groupby" endterm="sql-groupby-title"> is
-    used to group together those rows in a table that have the same
-    values in all the columns listed. The order in which the columns
-    are listed does not matter.  The effect is to combine each set
-    of rows having common values into one group row that
-    represents all rows in the group.  This is done to
-    eliminate redundancy in the output and/or compute aggregates that
-    apply to these groups.  For instance:
-<screen>
-<prompt>=&gt;</> <userinput>SELECT * FROM test1;</>
- x | y
----+---
- a | 3
- c | 2
- b | 5
- a | 1
-(4 rows)
-
-<prompt>=&gt;</> <userinput>SELECT x FROM test1 GROUP BY x;</>
- x
----
- a
- b
- c
-(3 rows)
-</screen>
-   </para>
-
-   <para>
-    In the second query, we could not have written <literal>SELECT *
-    FROM test1 GROUP BY x</literal>, because there is no single value
-    for the column <literal>y</> that could be associated with each
-    group.  The grouped-by columns can be referenced in the select list since
-    they have a single value in each group.
-   </para>
-
-   <para>
-    In general, if a table is grouped, columns that are not
-    listed in <literal>GROUP BY</> cannot be referenced except in aggregate
-    expressions.  An example with aggregate expressions is:
-<screen>
-<prompt>=&gt;</> <userinput>SELECT x, sum(y) FROM test1 GROUP BY x;</>
- x | sum
----+-----
- a |   4
- b |   5
- c |   2
-(3 rows)
-</screen>
-    Here <literal>sum</literal> is an aggregate function that
-    computes a single value over the entire group.  More information
-    about the available aggregate functions can be found in <xref
-    linkend="functions-aggregate">.
-   </para>
-
-   <tip>
-    <para>
-     Grouping without aggregate expressions effectively calculates the
-     set of distinct values in a column.  This can also be achieved
-     using the <literal>DISTINCT</> clause (see <xref
-     linkend="queries-distinct">).
-    </para>
-   </tip>
-
-   <para>
-    Here is another example:  it calculates the total sales for each
-    product (rather than the total sales of all products):
-<programlisting>
-SELECT product_id, p.name, (sum(s.units) * p.price) AS sales
-    FROM products p LEFT JOIN sales s USING (product_id)
-    GROUP BY product_id, p.name, p.price;
-</programlisting>
-    In this example, the columns <literal>product_id</literal>,
-    <literal>p.name</literal>, and <literal>p.price</literal> must be
-    in the <literal>GROUP BY</> clause since they are referenced in
-    the query select list (but see below).  The column
-    <literal>s.units</> does not have to be in the <literal>GROUP
-    BY</> list since it is only used in an aggregate expression
-    (<literal>sum(...)</literal>), which represents the sales
-    of a product.  For each product, the query returns a summary row about
-    all sales of the product.
-   </para>
-
-   <indexterm><primary>functional dependency</primary></indexterm>
-
-   <para>
-    If the products table is set up so that, say,
-    <literal>product_id</literal> is the primary key, then it would be
-    enough to group by <literal>product_id</literal> in the above example,
-    since name and price would be <firstterm>functionally
-    dependent</firstterm> on the product ID, and so there would be no
-    ambiguity about which name and price value to return for each product
-    ID group.
-   </para>
-
-   <para>
-    In strict SQL, <literal>GROUP BY</> can only group by columns of
-<!## PG>
-    the source table but <productname>PostgreSQL</productname> extends
-<!## end>
-<!## XC>
-    the source table but <productname>Postgres-XC</productname> extends
-<!## end>
-<!## XL>
-    the source table but <productname>Postgres-XL</productname> extends
-<!## end>
-    this to also allow <literal>GROUP BY</> to group by columns in the
-    select list.  Grouping by value expressions instead of simple
-    column names is also allowed.
-   </para>
-
-   <indexterm>
-    <primary>HAVING</primary>
-   </indexterm>
-
-   <para>
-    If a table has been grouped using <literal>GROUP BY</literal>,
-    but only certain groups are of interest, the
-    <literal>HAVING</literal> clause can be used, much like a
-    <literal>WHERE</> clause, to eliminate groups from the result.
-    The syntax is:
-<synopsis>
-SELECT <replaceable>select_list</replaceable> FROM ... <optional>WHERE ...</optional> GROUP BY ... HAVING <replaceable>boolean_expression</replaceable>
-</synopsis>
-    Expressions in the <literal>HAVING</> clause can refer both to
-    grouped expressions and to ungrouped expressions (which necessarily
-    involve an aggregate function).
-   </para>
-
-   <para>
-    Example:
-<screen>
-<prompt>=&gt;</> <userinput>SELECT x, sum(y) FROM test1 GROUP BY x HAVING sum(y) &gt; 3;</>
- x | sum
----+-----
- a |   4
- b |   5
-(2 rows)
-
-<prompt>=&gt;</> <userinput>SELECT x, sum(y) FROM test1 GROUP BY x HAVING x &lt; 'c';</>
- x | sum
----+-----
- a |   4
- b |   5
-(2 rows)
-</screen>
-   </para>
-
-   <para>
-    Again, a more realistic example:
-<programlisting>
-SELECT product_id, p.name, (sum(s.units) * (p.price - p.cost)) AS profit
-    FROM products p LEFT JOIN sales s USING (product_id)
-    WHERE s.date &gt; CURRENT_DATE - INTERVAL '4 weeks'
-    GROUP BY product_id, p.name, p.price, p.cost
-    HAVING sum(p.price * s.units) &gt; 5000;
-</programlisting>
-    In the example above, the <literal>WHERE</> clause is selecting
-    rows by a column that is not grouped (the expression is only true for
-    sales during the last four weeks), while the <literal>HAVING</>
-    clause restricts the output to groups with total gross sales over
-    5000.  Note that the aggregate expressions do not necessarily need
-    to be the same in all parts of the query.
-   </para>
-
-   <para>
-    If a query contains aggregate function calls, but no <literal>GROUP BY</>
-    clause, grouping still occurs: the result is a single group row (or
-    perhaps no rows at all, if the single row is then eliminated by
-    <literal>HAVING</>).
-    The same is true if it contains a <literal>HAVING</> clause, even
-    without any aggregate function calls or <literal>GROUP BY</> clause.
-   </para>
-  </sect2>
-
-  <sect2 id="queries-window">
-   <title>Window Function Processing</title>
-
-   <indexterm zone="queries-window">
-    <primary>window function</primary>
-    <secondary>order of execution</>
-   </indexterm>
-
-   <para>
-    If the query contains any window functions (see
-    <xref linkend="tutorial-window">,
-    <xref linkend="functions-window"> and
-    <xref linkend="syntax-window-functions">), these functions are evaluated
-    after any grouping, aggregation, and <literal>HAVING</> filtering is
-    performed.  That is, if the query uses any aggregates, <literal>GROUP
-    BY</>, or <literal>HAVING</>, then the rows seen by the window functions
-    are the group rows instead of the original table rows from
-    <literal>FROM</>/<literal>WHERE</>.
-   </para>
-
-   <para>
-    When multiple window functions are used, all the window functions having
-    syntactically equivalent <literal>PARTITION BY</> and <literal>ORDER BY</>
-    clauses in their window definitions are guaranteed to be evaluated in a
-    single pass over the data. Therefore they will see the same sort ordering,
-    even if the <literal>ORDER BY</> does not uniquely determine an ordering.
-    However, no guarantees are made about the evaluation of functions having
-    different <literal>PARTITION BY</> or <literal>ORDER BY</> specifications.
-    (In such cases a sort step is typically required between the passes of
-    window function evaluations, and the sort is not guaranteed to preserve
-    ordering of rows that its <literal>ORDER BY</> sees as equivalent.)
-   </para>
-
-   <para>
-    Currently, window functions always require presorted data, and so the
-    query output will be ordered according to one or another of the window
-    functions' <literal>PARTITION BY</>/<literal>ORDER BY</> clauses.
-    It is not recommendable to rely on this, however.  Use an explicit
-    top-level <literal>ORDER BY</> clause if you want to be sure the
-    results are sorted in a particular way.
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="queries-select-lists">
-  <title>Select Lists</title>
-
-  <indexterm>
-   <primary>SELECT</primary>
-   <secondary>select list</secondary>
-  </indexterm>
-&common;
-  <para>
-   As shown in the previous section,
-   the table expression in the <command>SELECT</command> command
-   constructs an intermediate virtual table by possibly combining
-   tables, views, eliminating rows, grouping, etc.  This table is
-   finally passed on to processing by the <firstterm>select list</firstterm>.  The select
-   list determines which <emphasis>columns</emphasis> of the
-   intermediate table are actually output.
-  </para>
-
-  <sect2 id="queries-select-list-items">
-   <title>Select-List Items</title>
-
-   <indexterm>
-    <primary>*</primary>
-   </indexterm>
-&common;
-   <para>
-    The simplest kind of select list is <literal>*</literal> which
-    emits all columns that the table expression produces.  Otherwise,
-    a select list is a comma-separated list of value expressions (as
-    defined in <xref linkend="sql-expressions">).  For instance, it
-    could be a list of column names:
-<programlisting>
-SELECT a, b, c FROM ...
-</programlisting>
-     The columns names <literal>a</>, <literal>b</>, and <literal>c</>
-     are either the actual names of the columns of tables referenced
-     in the <literal>FROM</> clause, or the aliases given to them as
-     explained in <xref linkend="queries-table-aliases">.  The name
-     space available in the select list is the same as in the
-     <literal>WHERE</> clause, unless grouping is used, in which case
-     it is the same as in the <literal>HAVING</> clause.
-   </para>
-
-   <para>
-    If more than one table has a column of the same name, the table
-    name must also be given, as in:
-<programlisting>
-SELECT tbl1.a, tbl2.a, tbl1.b FROM ...
-</programlisting>
-    When working with multiple tables, it can also be useful to ask for
-    all the columns of a particular table:
-<programlisting>
-SELECT tbl1.*, tbl2.a FROM ...
-</programlisting>
-    (See also <xref linkend="queries-where">.)
-   </para>
-
-   <para>
-    If an arbitrary value expression is used in the select list, it
-    conceptually adds a new virtual column to the returned table.  The
-    value expression is evaluated once for each result row, with
-    the row's values substituted for any column references.  But the
-    expressions in the select list do not have to reference any
-    columns in the table expression of the <literal>FROM</> clause;
-    they can be constant arithmetic expressions, for instance.
-   </para>
-  </sect2>
-
-  <sect2 id="queries-column-labels">
-   <title>Column Labels</title>
-
-   <indexterm zone="queries-column-labels">
-    <primary>alias</primary>
-    <secondary>in the select list</secondary>
-   </indexterm>
-&common;
-   <para>
-    The entries in the select list can be assigned names for subsequent
-    processing, such as for use in an <literal>ORDER BY</> clause
-    or for display by the client application.  For example:
-<programlisting>
-SELECT a AS value, b + c AS sum FROM ...
-</programlisting>
-   </para>
-
-   <para>
-    If no output column name is specified using <literal>AS</>,
-    the system assigns a default column name.  For simple column references,
-    this is the name of the referenced column.  For function
-    calls, this is the name of the function.  For complex expressions,
-    the system will generate a generic name.
-   </para>
-
-   <para>
-    The <literal>AS</> keyword is optional, but only if the new column
-    name does not match any
-<!## PG>
-    <productname>PostgreSQL</productname> keyword (see <xref
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> keyword (see <xref
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> keyword (see <xref
-<!## end>
-    linkend="sql-keywords-appendix">).  To avoid an accidental match to
-    a keyword, you can double-quote the column name.  For example,
-    <literal>VALUE</> is a keyword, so this does not work:
-<programlisting>
-SELECT a value, b + c AS sum FROM ...
-</programlisting>
-    but this does:
-<programlisting>
-SELECT a "value", b + c AS sum FROM ...
-</programlisting>
-    For protection against possible
-    future keyword additions, it is recommended that you always either
-    write <literal>AS</literal> or double-quote the output column name.
-   </para>
-
-   <note>
-    <para>
-     The naming of output columns here is different from that done in
-     the <literal>FROM</> clause (see <xref
-     linkend="queries-table-aliases">).  It is possible
-     to rename the same column twice, but the name assigned in
-     the select list is the one that will be passed on.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2 id="queries-distinct">
-   <title><literal>DISTINCT</literal></title>
-
-   <indexterm zone="queries-distinct">
-    <primary>DISTINCT</primary>
-   </indexterm>
-
-   <indexterm zone="queries-distinct">
-    <primary>duplicates</primary>
-   </indexterm>
-&common;
-   <para>
-    After the select list has been processed, the result table can
-    optionally be subject to the elimination of duplicate rows.  The
-    <literal>DISTINCT</literal> key word is written directly after
-    <literal>SELECT</literal> to specify this:
-<synopsis>
-SELECT DISTINCT <replaceable>select_list</replaceable> ...
-</synopsis>
-    (Instead of <literal>DISTINCT</> the key word <literal>ALL</literal>
-    can be used to specify the default behavior of retaining all rows.)
-   </para>
-
-   <indexterm>
-    <primary>null value</>
-    <secondary sortas="DISTINCT">in DISTINCT</>
-   </indexterm>
-
-   <para>
-    Obviously, two rows are considered distinct if they differ in at
-    least one column value.  Null values are considered equal in this
-    comparison.
-   </para>
-
-   <para>
-    Alternatively, an arbitrary expression can determine what rows are
-    to be considered distinct:
-<synopsis>
-SELECT DISTINCT ON (<replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ...</optional>) <replaceable>select_list</replaceable> ...
-</synopsis>
-    Here <replaceable>expression</replaceable> is an arbitrary value
-    expression that is evaluated for all rows.  A set of rows for
-    which all the expressions are equal are considered duplicates, and
-    only the first row of the set is kept in the output.  Note that
-    the <quote>first row</quote> of a set is unpredictable unless the
-    query is sorted on enough columns to guarantee a unique ordering
-    of the rows arriving at the <literal>DISTINCT</> filter.
-    (<literal>DISTINCT ON</> processing occurs after <literal>ORDER
-    BY</> sorting.)
-   </para>
-
-   <para>
-    The <literal>DISTINCT ON</> clause is not part of the SQL standard
-    and is sometimes considered bad style because of the potentially
-    indeterminate nature of its results.  With judicious use of
-    <literal>GROUP BY</> and subqueries in <literal>FROM</>, this
-    construct can be avoided, but it is often the most convenient
-    alternative.
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="queries-union">
-  <title>Combining Queries</title>
-
-  <indexterm zone="queries-union">
-   <primary>UNION</primary>
-  </indexterm>
-  <indexterm zone="queries-union">
-   <primary>INTERSECT</primary>
-  </indexterm>
-  <indexterm zone="queries-union">
-   <primary>EXCEPT</primary>
-  </indexterm>
-  <indexterm zone="queries-union">
-   <primary>set union</primary>
-  </indexterm>
-  <indexterm zone="queries-union">
-   <primary>set intersection</primary>
-  </indexterm>
-  <indexterm zone="queries-union">
-   <primary>set difference</primary>
-  </indexterm>
-  <indexterm zone="queries-union">
-   <primary>set operation</primary>
-  </indexterm>
-&common;
-  <para>
-   The results of two queries can be combined using the set operations
-   union, intersection, and difference.  The syntax is
-<synopsis>
-<replaceable>query1</replaceable> UNION <optional>ALL</optional> <replaceable>query2</replaceable>
-<replaceable>query1</replaceable> INTERSECT <optional>ALL</optional> <replaceable>query2</replaceable>
-<replaceable>query1</replaceable> EXCEPT <optional>ALL</optional> <replaceable>query2</replaceable>
-</synopsis>
-   <replaceable>query1</replaceable> and
-   <replaceable>query2</replaceable> are queries that can use any of
-   the features discussed up to this point.  Set operations can also
-   be nested and chained, for example
-<synopsis>
-<replaceable>query1</replaceable> UNION <replaceable>query2</replaceable> UNION <replaceable>query3</replaceable>
-</synopsis>
-   which is executed as:
-<synopsis>
-(<replaceable>query1</replaceable> UNION <replaceable>query2</replaceable>) UNION <replaceable>query3</replaceable>
-</synopsis>
-  </para>
-
-  <para>
-   <literal>UNION</> effectively appends the result of
-   <replaceable>query2</replaceable> to the result of
-   <replaceable>query1</replaceable> (although there is no guarantee
-   that this is the order in which the rows are actually returned).
-   Furthermore, it eliminates duplicate rows from its result, in the same
-   way as <literal>DISTINCT</>, unless <literal>UNION ALL</> is used.
-  </para>
-
-  <para>
-   <literal>INTERSECT</> returns all rows that are both in the result
-   of <replaceable>query1</replaceable> and in the result of
-   <replaceable>query2</replaceable>.  Duplicate rows are eliminated
-   unless <literal>INTERSECT ALL</> is used.
-  </para>
-
-  <para>
-   <literal>EXCEPT</> returns all rows that are in the result of
-   <replaceable>query1</replaceable> but not in the result of
-   <replaceable>query2</replaceable>.  (This is sometimes called the
-   <firstterm>difference</> between two queries.)  Again, duplicates
-   are eliminated unless <literal>EXCEPT ALL</> is used.
-  </para>
-
-  <para>
-   In order to calculate the union, intersection, or difference of two
-   queries, the two queries must be <quote>union compatible</quote>,
-   which means that they return the same number of columns and
-   the corresponding columns have compatible data types, as
-   described in <xref linkend="typeconv-union-case">.
-  </para>
- </sect1>
-
-
- <sect1 id="queries-order">
-  <title>Sorting Rows</title>
-
-  <indexterm zone="queries-order">
-   <primary>sorting</primary>
-  </indexterm>
-
-  <indexterm zone="queries-order">
-   <primary>ORDER BY</primary>
-  </indexterm>
-&common;
-  <para>
-   After a query has produced an output table (after the select list
-   has been processed) it can optionally be sorted.  If sorting is not
-   chosen, the rows will be returned in an unspecified order.  The actual
-   order in that case will depend on the scan and join plan types and
-   the order on disk, but it must not be relied on.  A particular
-   output ordering can only be guaranteed if the sort step is explicitly
-   chosen.
-  </para>
-
-  <para>
-   The <literal>ORDER BY</> clause specifies the sort order:
-<synopsis>
-SELECT <replaceable>select_list</replaceable>
-    FROM <replaceable>table_expression</replaceable>
-    ORDER BY <replaceable>sort_expression1</replaceable> <optional>ASC | DESC</optional> <optional>NULLS { FIRST | LAST }</optional>
-             <optional>, <replaceable>sort_expression2</replaceable> <optional>ASC | DESC</optional> <optional>NULLS { FIRST | LAST }</optional> ...</optional>
-</synopsis>
-   The sort expression(s) can be any expression that would be valid in the
-   query's select list.  An example is:
-<programlisting>
-SELECT a, b FROM table1 ORDER BY a + b, c;
-</programlisting>
-   When more than one expression is specified,
-   the later values are used to sort rows that are equal according to the
-   earlier values.  Each expression can be followed by an optional
-   <literal>ASC</> or <literal>DESC</> keyword to set the sort direction to
-   ascending or descending.  <literal>ASC</> order is the default.
-   Ascending order puts smaller values first, where
-   <quote>smaller</quote> is defined in terms of the
-   <literal>&lt;</literal> operator.  Similarly, descending order is
-   determined with the <literal>&gt;</literal> operator.
-    <footnote>
-     <para>
-<!## PG>
-      Actually, <productname>PostgreSQL</> uses the <firstterm>default B-tree
-<!## end>
-<!## XC>
-      Actually, <productname>Postgres-XC</> uses the <firstterm>default B-tree
-<!## end>
-<!## XL>
-      Actually, <productname>Postgres-XL</> uses the <firstterm>default B-tree
-<!## end>
-      operator class</> for the expression's data type to determine the sort
-      ordering for <literal>ASC</> and <literal>DESC</>.  Conventionally,
-      data types will be set up so that the <literal>&lt;</literal> and
-      <literal>&gt;</literal> operators correspond to this sort ordering,
-      but a user-defined data type's designer could choose to do something
-      different.
-     </para>
-    </footnote>
-  </para>
-
-  <para>
-   The <literal>NULLS FIRST</> and <literal>NULLS LAST</> options can be
-   used to determine whether nulls appear before or after non-null values
-   in the sort ordering.  By default, null values sort as if larger than any
-   non-null value; that is, <literal>NULLS FIRST</> is the default for
-   <literal>DESC</> order, and <literal>NULLS LAST</> otherwise.
-  </para>
-
-  <para>
-   Note that the ordering options are considered independently for each
-   sort column.  For example <literal>ORDER BY x, y DESC</> means
-   <literal>ORDER BY x ASC, y DESC</>, which is not the same as
-   <literal>ORDER BY x DESC, y DESC</>.
-  </para>
-
-  <para>
-   A <replaceable>sort_expression</> can also be the column label or number
-   of an output column, as in:
-<programlisting>
-SELECT a + b AS sum, c FROM table1 ORDER BY sum;
-SELECT a, max(b) FROM table1 GROUP BY a ORDER BY 1;
-</programlisting>
-   both of which sort by the first output column.  Note that an output
-   column name has to stand alone, that is, it cannot be used in an expression
-   &mdash; for example, this is <emphasis>not</> correct:
-<programlisting>
-SELECT a + b AS sum, c FROM table1 ORDER BY sum + c;          -- wrong
-</programlisting>
-   This restriction is made to reduce ambiguity.  There is still
-   ambiguity if an <literal>ORDER BY</> item is a simple name that
-   could match either an output column name or a column from the table
-   expression.  The output column is used in such cases.  This would
-   only cause confusion if you use <literal>AS</> to rename an output
-   column to match some other table column's name.
-  </para>
-
-  <para>
-   <literal>ORDER BY</> can be applied to the result of a
-   <literal>UNION</>, <literal>INTERSECT</>, or <literal>EXCEPT</>
-   combination, but in this case it is only permitted to sort by
-   output column names or numbers, not by expressions.
-  </para>
- </sect1>
-
-
- <sect1 id="queries-limit">
-  <title><literal>LIMIT</literal> and <literal>OFFSET</literal></title>
-
-  <indexterm zone="queries-limit">
-   <primary>LIMIT</primary>
-  </indexterm>
-
-  <indexterm zone="queries-limit">
-   <primary>OFFSET</primary>
-  </indexterm>
-&common;
-  <para>
-   <literal>LIMIT</> and <literal>OFFSET</> allow you to retrieve just
-   a portion of the rows that are generated by the rest of the query:
-<synopsis>
-SELECT <replaceable>select_list</replaceable>
-    FROM <replaceable>table_expression</replaceable>
-    <optional> ORDER BY ... </optional>
-    <optional> LIMIT { <replaceable>number</replaceable> | ALL } </optional> <optional> OFFSET <replaceable>number</replaceable> </optional>
-</synopsis>
-  </para>
-
-  <para>
-   If a limit count is given, no more than that many rows will be
-   returned (but possibly less, if the query itself yields less rows).
-   <literal>LIMIT ALL</> is the same as omitting the <literal>LIMIT</>
-   clause.
-  </para>
-
-  <para>
-   <literal>OFFSET</> says to skip that many rows before beginning to
-   return rows.  <literal>OFFSET 0</> is the same as omitting the
-   <literal>OFFSET</> clause, and <literal>LIMIT NULL</> is the same
-   as omitting the <literal>LIMIT</> clause.  If both <literal>OFFSET</>
-   and <literal>LIMIT</> appear, then <literal>OFFSET</> rows are
-   skipped before starting to count the <literal>LIMIT</> rows that
-   are returned.
-  </para>
-
-  <para>
-   When using <literal>LIMIT</>, it is important to use an
-   <literal>ORDER BY</> clause that constrains the result rows into a
-   unique order.  Otherwise you will get an unpredictable subset of
-   the query's rows. You might be asking for the tenth through
-   twentieth rows, but tenth through twentieth in what ordering? The
-   ordering is unknown, unless you specified <literal>ORDER BY</>.
-  </para>
-
-  <para>
-   The query optimizer takes <literal>LIMIT</> into account when
-   generating query plans, so you are very likely to get different
-   plans (yielding different row orders) depending on what you give
-   for <literal>LIMIT</> and <literal>OFFSET</>.  Thus, using
-   different <literal>LIMIT</>/<literal>OFFSET</> values to select
-   different subsets of a query result <emphasis>will give
-   inconsistent results</emphasis> unless you enforce a predictable
-   result ordering with <literal>ORDER BY</>.  This is not a bug; it
-   is an inherent consequence of the fact that SQL does not promise to
-   deliver the results of a query in any particular order unless
-   <literal>ORDER BY</> is used to constrain the order.
-  </para>
-
-  <para>
-   The rows skipped by an <literal>OFFSET</> clause still have to be
-   computed inside the server; therefore a large <literal>OFFSET</>
-   might be inefficient.
-  </para>
- </sect1>
-
-
- <sect1 id="queries-values">
-  <title><literal>VALUES</literal> Lists</title>
-
-  <indexterm zone="queries-values">
-   <primary>VALUES</primary>
-  </indexterm>
-&common;
-  <para>
-   <literal>VALUES</> provides a way to generate a <quote>constant table</>
-   that can be used in a query without having to actually create and populate
-   a table on-disk.  The syntax is
-<synopsis>
-VALUES ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) [, ...]
-</synopsis>
-   Each parenthesized list of expressions generates a row in the table.
-   The lists must all have the same number of elements (i.e., the number
-   of columns in the table), and corresponding entries in each list must
-   have compatible data types.  The actual data type assigned to each column
-   of the result is determined using the same rules as for <literal>UNION</>
-   (see <xref linkend="typeconv-union-case">).
-  </para>
-
-  <para>
-   As an example:
-<programlisting>
-VALUES (1, 'one'), (2, 'two'), (3, 'three');
-</programlisting>
-
-   will return a table of two columns and three rows.  It's effectively
-   equivalent to:
-<programlisting>
-SELECT 1 AS column1, 'one' AS column2
-UNION ALL
-SELECT 2, 'two'
-UNION ALL
-SELECT 3, 'three';
-</programlisting>
-
-<!## PG>
-   By default, <productname>PostgreSQL</productname> assigns the names
-<!## end>
-<!## XC>
-   By default, <productname>Postgres-XC</productname> assigns the names
-<!## end>
-<!## XL>
-   By default, <productname>Postgres-XL</productname> assigns the names
-<!## end>
-   <literal>column1</>, <literal>column2</>, etc. to the columns of a
-   <literal>VALUES</> table.  The column names are not specified by the
-   SQL standard and different database systems do it differently, so
-   it's usually better to override the default names with a table alias
-   list.
-  </para>
-
-  <para>
-   Syntactically, <literal>VALUES</> followed by expression lists is
-   treated as equivalent to:
-<synopsis>
-SELECT <replaceable>select_list</replaceable> FROM <replaceable>table_expression</replaceable>
-</synopsis>
-   and can appear anywhere a <literal>SELECT</> can.  For example, you can
-   use it as part of a <literal>UNION</>, or attach a
-   <replaceable>sort_specification</replaceable> (<literal>ORDER BY</>,
-   <literal>LIMIT</>, and/or <literal>OFFSET</>) to it.  <literal>VALUES</>
-   is most commonly used as the data source in an <command>INSERT</> command,
-   and next most commonly as a subquery.
-  </para>
-
-  <para>
-   For more information see <xref linkend="sql-values">.
-  </para>
-
- </sect1>
-
- <sect1 id="queries-with">
-  <title><literal>WITH</literal> Queries (Common Table Expressions)</title>
-
-  <indexterm zone="queries-with">
-   <primary>WITH</primary>
-   <secondary>in SELECT</secondary>
-  </indexterm>
-
-  <indexterm>
-   <primary>common table expression</primary>
-   <see>WITH</see>
-  </indexterm>
-
-  <para>
-   <literal>WITH</> provides a way to write auxiliary statements for use in a
-   larger query.  These statements, which are often referred to as Common
-   Table Expressions or <acronym>CTE</acronym>s, can be thought of as defining
-   temporary tables that exist just for one query.  Each auxiliary statement
-   in a <literal>WITH</> clause can be a <command>SELECT</>,
-   <command>INSERT</>, <command>UPDATE</>, or <command>DELETE</>; and the
-   <literal>WITH</> clause itself is attached to a primary statement that can
-   also be a <command>SELECT</>, <command>INSERT</>, <command>UPDATE</>, or
-   <command>DELETE</>.
-  </para>
-
- <sect2 id="queries-with-select">
-   <title><command>SELECT</> in <literal>WITH</></title>
-
-  <para>
-   The basic value of <command>SELECT</> in <literal>WITH</> is to
-   break down complicated queries into simpler parts.  An example is:
-
-<programlisting>
-WITH regional_sales AS (
-        SELECT region, SUM(amount) AS total_sales
-        FROM orders
-        GROUP BY region
-     ), top_regions AS (
-        SELECT region
-        FROM regional_sales
-        WHERE total_sales &gt; (SELECT SUM(total_sales)/10 FROM regional_sales)
-     )
-SELECT region,
-       product,
-       SUM(quantity) AS product_units,
-       SUM(amount) AS product_sales
-FROM orders
-WHERE region IN (SELECT region FROM top_regions)
-GROUP BY region, product;
-</programlisting>
-
-   which displays per-product sales totals in only the top sales regions.
-   The <literal>WITH</> clause defines two auxiliary statements named
-   <structname>regional_sales</> and <structname>top_regions</>,
-   where the output of <structname>regional_sales</> is used in
-   <structname>top_regions</> and the output of <structname>top_regions</>
-   is used in the primary <command>SELECT</> query.
-   This example could have been written without <literal>WITH</>,
-   but we'd have needed two levels of nested sub-<command>SELECT</command>s.  It's a bit
-   easier to follow this way.
-  </para>
-
-  <para>
-   The optional <literal>RECURSIVE</> modifier changes <literal>WITH</>
-   from a mere syntactic convenience into a feature that accomplishes
-   things not otherwise possible in standard SQL.  Using
-   <literal>RECURSIVE</>, a <literal>WITH</> query can refer to its own
-   output.  A very simple example is this query to sum the integers from 1
-   through 100:
-
-<programlisting>
-WITH RECURSIVE t(n) AS (
-    VALUES (1)
-  UNION ALL
-    SELECT n+1 FROM t WHERE n &lt; 100
-)
-SELECT sum(n) FROM t;
-</programlisting>
-
-   The general form of a recursive <literal>WITH</> query is always a
-   <firstterm>non-recursive term</>, then <literal>UNION</> (or
-   <literal>UNION ALL</>), then a
-   <firstterm>recursive term</>, where only the recursive term can contain
-   a reference to the query's own output.  Such a query is executed as
-   follows:
-  </para>
-
-  <procedure>
-   <title>Recursive Query Evaluation</title>
-
-   <step performance="required">
-    <para>
-     Evaluate the non-recursive term.  For <literal>UNION</> (but not
-     <literal>UNION ALL</>), discard duplicate rows.  Include all remaining
-     rows in the result of the recursive query, and also place them in a
-     temporary <firstterm>working table</>.
-    </para>
-   </step>
-
-   <step performance="required">
-    <para>
-     So long as the working table is not empty, repeat these steps:
-    </para>
-    <substeps>
-     <step performance="required">
-      <para>
-       Evaluate the recursive term, substituting the current contents of
-       the working table for the recursive self-reference.
-       For <literal>UNION</> (but not <literal>UNION ALL</>), discard
-       duplicate rows and rows that duplicate any previous result row.
-       Include all remaining rows in the result of the recursive query, and
-       also place them in a temporary <firstterm>intermediate table</>.
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       Replace the contents of the working table with the contents of the
-       intermediate table, then empty the intermediate table.
-      </para>
-     </step>
-    </substeps>
-   </step>
-  </procedure>
-
-  <note>
-   <para>
-    Strictly speaking, this process is iteration not recursion, but
-    <literal>RECURSIVE</> is the terminology chosen by the SQL standards
-    committee.
-   </para>
-  </note>
-
-  <para>
-   In the example above, the working table has just a single row in each step,
-   and it takes on the values from 1 through 100 in successive steps.  In
-   the 100th step, there is no output because of the <literal>WHERE</>
-   clause, and so the query terminates.
-  </para>
-
-  <para>
-   Recursive queries are typically used to deal with hierarchical or
-   tree-structured data.  A useful example is this query to find all the
-   direct and indirect sub-parts of a product, given only a table that
-   shows immediate inclusions:
-
-<programlisting>
-WITH RECURSIVE included_parts(sub_part, part, quantity) AS (
-    SELECT sub_part, part, quantity FROM parts WHERE part = 'our_product'
-  UNION ALL
-    SELECT p.sub_part, p.part, p.quantity
-    FROM included_parts pr, parts p
-    WHERE p.part = pr.sub_part
-  )
-SELECT sub_part, SUM(quantity) as total_quantity
-FROM included_parts
-GROUP BY sub_part
-</programlisting>
-  </para>
-
-  <para>
-   When working with recursive queries it is important to be sure that
-   the recursive part of the query will eventually return no tuples,
-   or else the query will loop indefinitely.  Sometimes, using
-   <literal>UNION</> instead of <literal>UNION ALL</> can accomplish this
-   by discarding rows that duplicate previous output rows.  However, often a
-   cycle does not involve output rows that are completely duplicate: it may be
-   necessary to check just one or a few fields to see if the same point has
-   been reached before.  The standard method for handling such situations is
-   to compute an array of the already-visited values.  For example, consider
-   the following query that searches a table <structname>graph</> using a
-   <structfield>link</> field:
-
-<programlisting>
-WITH RECURSIVE search_graph(id, link, data, depth) AS (
-        SELECT g.id, g.link, g.data, 1
-        FROM graph g
-      UNION ALL
-        SELECT g.id, g.link, g.data, sg.depth + 1
-        FROM graph g, search_graph sg
-        WHERE g.id = sg.link
-)
-SELECT * FROM search_graph;
-</programlisting>
-
-   This query will loop if the <structfield>link</> relationships contain
-   cycles.  Because we require a <quote>depth</> output, just changing
-   <literal>UNION ALL</> to <literal>UNION</> would not eliminate the looping.
-   Instead we need to recognize whether we have reached the same row again
-   while following a particular path of links.  We add two columns
-   <structfield>path</> and <structfield>cycle</> to the loop-prone query:
-
-<programlisting>
-WITH RECURSIVE search_graph(id, link, data, depth, path, cycle) AS (
-        SELECT g.id, g.link, g.data, 1,
-          ARRAY[g.id],
-          false
-        FROM graph g
-      UNION ALL
-        SELECT g.id, g.link, g.data, sg.depth + 1,
-          path || g.id,
-          g.id = ANY(path)
-        FROM graph g, search_graph sg
-        WHERE g.id = sg.link AND NOT cycle
-)
-SELECT * FROM search_graph;
-</programlisting>
-
-   Aside from preventing cycles, the array value is often useful in its own
-   right as representing the <quote>path</> taken to reach any particular row.
-  </para>
-
-  <para>
-   In the general case where more than one field needs to be checked to
-   recognize a cycle, use an array of rows.  For example, if we needed to
-   compare fields <structfield>f1</> and <structfield>f2</>:
-
-<programlisting>
-WITH RECURSIVE search_graph(id, link, data, depth, path, cycle) AS (
-        SELECT g.id, g.link, g.data, 1,
-          ARRAY[ROW(g.f1, g.f2)],
-          false
-        FROM graph g
-      UNION ALL
-        SELECT g.id, g.link, g.data, sg.depth + 1,
-          path || ROW(g.f1, g.f2),
-          ROW(g.f1, g.f2) = ANY(path)
-        FROM graph g, search_graph sg
-        WHERE sg.link AND NOT cycle
-)
-SELECT * FROM search_graph;
-</programlisting>
-  </para>
-
-  <tip>
-   <para>
-    Omit the <literal>ROW()</> syntax in the common case where only one field
-    needs to be checked to recognize a cycle.  This allows a simple array
-    rather than a composite-type array to be used, gaining efficiency.
-   </para>
-  </tip>
-
-  <tip>
-   <para>
-    The recursive query evaluation algorithm produces its output in
-    breadth-first search order.  You can display the results in depth-first
-    search order by making the outer query <literal>ORDER BY</> a
-    <quote>path</> column constructed in this way.
-   </para>
-  </tip>
-
-  <para>
-   A helpful trick for testing queries
-   when you are not certain if they might loop is to place a <literal>LIMIT</>
-   in the parent query.  For example, this query would loop forever without
-   the <literal>LIMIT</>:
-
-<programlisting>
-WITH RECURSIVE t(n) AS (
-    SELECT 1
-  UNION ALL
-    SELECT n+1 FROM t
-)
-SELECT n FROM t LIMIT 100;
-</programlisting>
-
-<!## PG>
-   This works because <productname>PostgreSQL</productname>'s implementation
-<!## end>
-<!## XC>
-   This works because <productname>Postgres-XC</productname>'s implementation
-<!## end>
-<!## XL>
-   This works because <productname>Postgres-XL</productname>'s implementation
-<!## end>
-   evaluates only as many rows of a <literal>WITH</> query as are actually
-   fetched by the parent query.  Using this trick in production is not
-   recommended, because other systems might work differently.  Also, it
-   usually won't work if you make the outer query sort the recursive query's
-   results or join them to some other table, because in such cases the
-   outer query will usually try to fetch all of the <literal>WITH</> query's
-   output anyway.
-  </para>
-
-  <para>
-   A useful property of <literal>WITH</> queries is that they are evaluated
-   only once per execution of the parent query, even if they are referred to
-   more than once by the parent query or sibling <literal>WITH</> queries.
-   Thus, expensive calculations that are needed in multiple places can be
-   placed within a <literal>WITH</> query to avoid redundant work.  Another
-   possible application is to prevent unwanted multiple evaluations of
-   functions with side-effects.
-   However, the other side of this coin is that the optimizer is less able to
-   push restrictions from the parent query down into a <literal>WITH</> query
-   than an ordinary sub-query.  The <literal>WITH</> query will generally be
-   evaluated as written, without suppression of rows that the parent query
-   might discard afterwards.  (But, as mentioned above, evaluation might stop
-   early if the reference(s) to the query demand only a limited number of
-   rows.)
-  </para>
-
-
-  <para>
-   The examples above only show <literal>WITH</> being used with
-   <command>SELECT</>, but it can be attached in the same way to
-   <command>INSERT</>, <command>UPDATE</>, or <command>DELETE</>.
-   In each case it effectively provides temporary table(s) that can
-   be referred to in the main command.
-  </para>
-
- </sect2>
-
- <sect2 id="queries-with-modifying">
-   <title>Data-Modifying Statements in <literal>WITH</></title>
-
-   <para>
-    You can use data-modifying statements (<command>INSERT</>,
-    <command>UPDATE</>, or <command>DELETE</>) in <literal>WITH</>.  This
-    allows you to perform several different operations in the same query.
-    An example is:
-
-<programlisting>
-WITH moved_rows AS (
-    DELETE FROM products
-    WHERE
-        "date" &gt;= '2010-10-01' AND
-        "date" &lt; '2010-11-01'
-    RETURNING *
-)
-INSERT INTO products_log
-SELECT * FROM moved_rows;
-</programlisting>
-
-    This query effectively moves rows from <structname>products</> to
-    <structname>products_log</>.  The <command>DELETE</> in <literal>WITH</>
-    deletes the specified rows from <structname>products</>, returning their
-    contents by means of its <literal>RETURNING</> clause; and then the
-    primary query reads that output and inserts it into
-    <structname>products_log</>.
-   </para>
-
-   <para>
-    A fine point of the above example is that the <literal>WITH</> clause is
-    attached to the <command>INSERT</>, not the sub-<command>SELECT</> within
-    the <command>INSERT</>.  This is necessary because data-modifying
-    statements are only allowed in <literal>WITH</> clauses that are attached
-    to the top-level statement.  However, normal <literal>WITH</> visibility
-    rules apply, so it is possible to refer to the <literal>WITH</>
-    statement's output from the sub-<command>SELECT</>.
-   </para>
-
-   <para>
-    Data-modifying statements in <literal>WITH</> usually have
-    <literal>RETURNING</> clauses, as seen in the example above.
-    It is the output of the <literal>RETURNING</> clause, <emphasis>not</> the
-    target table of the data-modifying statement, that forms the temporary
-    table that can be referred to by the rest of the query.  If a
-    data-modifying statement in <literal>WITH</> lacks a <literal>RETURNING</>
-    clause, then it forms no temporary table and cannot be referred to in
-    the rest of the query.  Such a statement will be executed nonetheless.
-    A not-particularly-useful example is:
-
-<programlisting>
-WITH t AS (
-    DELETE FROM foo
-)
-DELETE FROM bar;
-</programlisting>
-
-    This example would remove all rows from tables <structname>foo</> and
-    <structname>bar</>.  The number of affected rows reported to the client
-    would only include rows removed from <structname>bar</>.
-   </para>
-
-   <para>
-    Recursive self-references in data-modifying statements are not
-    allowed.  In some cases it is possible to work around this limitation by
-    referring to the output of a recursive <literal>WITH</>, for example:
-
-<programlisting>
-WITH RECURSIVE included_parts(sub_part, part) AS (
-    SELECT sub_part, part FROM parts WHERE part = 'our_product'
-  UNION ALL
-    SELECT p.sub_part, p.part
-    FROM included_parts pr, parts p
-    WHERE p.part = pr.sub_part
-  )
-DELETE FROM parts
-  WHERE part IN (SELECT part FROM included_parts);
-</programlisting>
-
-    This query would remove all direct and indirect subparts of a product.
-   </para>
-
-   <para>
-    Data-modifying statements in <literal>WITH</> are executed exactly once,
-    and always to completion, independently of whether the primary query
-    reads all (or indeed any) of their output.  Notice that this is different
-    from the rule for <command>SELECT</> in <literal>WITH</>: as stated in the
-    previous section, execution of a <command>SELECT</> is carried only as far
-    as the primary query demands its output.
-   </para>
-
-   <para>
-    The sub-statements in <literal>WITH</> are executed concurrently with
-    each other and with the main query.  Therefore, when using data-modifying
-    statements in <literal>WITH</>, the order in which the specified updates
-    actually happen is unpredictable.  All the statements are executed with
-    the same <firstterm>snapshot</> (see <xref linkend="mvcc">), so they
-    cannot <quote>see</> each others' effects on the target tables.  This
-    alleviates the effects of the unpredictability of the actual order of row
-    updates, and means that <literal>RETURNING</> data is the only way to
-    communicate changes between different <literal>WITH</> sub-statements and
-    the main query.  An example of this is that in
-
-<programlisting>
-WITH t AS (
-    UPDATE products SET price = price * 1.05
-    RETURNING *
-)
-SELECT * FROM products;
-</programlisting>
-
-    the outer <command>SELECT</> would return the original prices before the
-    action of the <command>UPDATE</>, while in
-
-<programlisting>
-WITH t AS (
-    UPDATE products SET price = price * 1.05
-    RETURNING *
-)
-SELECT * FROM t;
-</programlisting>
-
-    the outer <command>SELECT</> would return the updated data.
-   </para>
-
-   <para>
-    Trying to update the same row twice in a single statement is not
-    supported.  Only one of the modifications takes place, but it is not easy
-    (and sometimes not possible) to reliably predict which one.  This also
-    applies to deleting a row that was already updated in the same statement:
-    only the update is performed.  Therefore you should generally avoid trying
-    to modify a single row twice in a single statement.  In particular avoid
-    writing <literal>WITH</> sub-statements that could affect the same rows
-    changed by the main statement or a sibling sub-statement.  The effects
-    of such a statement will not be predictable.
-   </para>
-
-   <para>
-    At present, any table used as the target of a data-modifying statement in
-    <literal>WITH</> must not have a conditional rule, nor an <literal>ALSO</>
-    rule, nor an <literal>INSTEAD</> rule that expands to multiple statements.
-   </para>
-
-  </sect2>
-
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/query.sgmlin b/doc-xc/src/sgml/query.sgmlin
deleted file mode 100644
index 785f11e08b..0000000000
--- a/doc-xc/src/sgml/query.sgmlin
+++ /dev/null
@@ -1,1036 +0,0 @@
-<!-- doc/src/sgml/query.sgml -->
-
- <chapter id="tutorial-sql">
-  <title>The <acronym>SQL</acronym> Language</title>
-
-  <sect1 id="tutorial-sql-intro">
-   <title>Introduction</title>
-&common;
-   <para>
-    This chapter provides an overview of how to use
-    <acronym>SQL</acronym> to perform simple operations.  This
-    tutorial is only intended to give you an introduction and is in no
-    way a complete tutorial on <acronym>SQL</acronym>.  Numerous books
-    have been written on <acronym>SQL</acronym>, including <xref
-    linkend="MELT93"> and <xref linkend="DATE97">.
-<!## PG>
-    You should be aware that some <productname>PostgreSQL</productname>
-    language features are extensions to the standard.
-<!## end>
-<!## XC>
-    You should be aware that some <productname>Postgres-XC</productname>
-    language features are extensions to the standard.
-<!## end>
-<!## XL>
-    You should be aware that some <productname>Postgres-XL</productname>
-    language features are extensions to the standard.
-<!## end>
-   </para>
-
-   <para>
-    In the examples that follow, we assume that you have created a
-    database named <literal>mydb</literal>, as described in the previous
-    chapter, and have been able to start <application>psql</application>.
-   </para>
-
-   <para>
-<!## PG>
-    Examples in this manual can also be found in the
-    <productname>PostgreSQL</productname> source distribution
-    in the directory <filename>src/tutorial/</filename>.  (Binary
-    distributions of <productname>PostgreSQL</productname> might not
-    compile these files.)  To use those
-    files, first change to that directory and run <application>make</>:
-<!## end>
-<!## XC>
-    Examples in this manual can also be found in the
-    <productname>Postgres-XC</productname> source distribution
-    in the directory <filename>src/tutorial/</filename>.  (Binary
-    distributions of <productname>Postgres-XC</productname> might not
-    compile these files.)  To use those
-    files, first change to that directory and run <application>make</>:
-<!## end>
-<!## XL>
-    Examples in this manual can also be found in the
-    <productname>Postgres-XL</productname> source distribution
-    in the directory <filename>src/tutorial/</filename>.  (Binary
-    distributions of <productname>Postgres-XL</productname> might not
-    compile these files.)  To use those
-    files, first change to that directory and run <application>make</>:
-<!## end>
-
-<screen>
-<prompt>$</prompt> <userinput>cd <replaceable>../..</replaceable>/src/tutorial</userinput>
-<prompt>$</prompt> <userinput>make</userinput>
-</screen>
-
-    This creates the scripts and compiles the C files containing user-defined
-    functions and types.  Then, to start the tutorial, do the following:
-
-<screen>
-<prompt>$</prompt> <userinput>cd <replaceable>....</replaceable>/tutorial</userinput>
-<prompt>$</prompt> <userinput>psql -s mydb</userinput>
-<computeroutput>
-...
-</computeroutput>
-
-<!-- 
-  TODO:  K.Suzuki, 13th June, 2011.
-    basics.sql is named basics.source in the original.  Rename it.
--->
-
-<prompt>mydb=&gt;</prompt> <userinput>\i basics.sql</userinput>
-</screen>
-
-    The <literal>\i</literal> command reads in commands from the
-    specified file. <command>psql</command>'s <literal>-s</> option puts you in
-    single step mode which pauses before sending each statement to the
-    server.  The commands used in this section are in the file
-    <filename>basics.sql</filename>.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-concepts">
-   <title>Concepts</title>
-
-   <para>
-    <indexterm><primary>relational database</primary></indexterm>
-    <indexterm><primary>hierarchical database</primary></indexterm>
-    <indexterm><primary>object-oriented database</primary></indexterm>
-    <indexterm><primary>relation</primary></indexterm>
-    <indexterm><primary>table</primary></indexterm>
-
-&common;
-<!## PG>
-    <productname>PostgreSQL</productname> is a <firstterm>relational
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> is a <firstterm>relational
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> is a <firstterm>relational
-<!## end>
-    database management system</firstterm> (<acronym>RDBMS</acronym>).
-    That means it is a system for managing data stored in
-    <firstterm>relations</firstterm>.  Relation is essentially a
-    mathematical term for <firstterm>table</firstterm>.  The notion of
-    storing data in tables is so commonplace today that it might
-    seem inherently obvious, but there are a number of other ways of
-    organizing databases.  Files and directories on Unix-like
-    operating systems form an example of a hierarchical database.  A
-    more modern development is the object-oriented database.
-   </para>
-
-   <para>
-    <indexterm><primary>row</primary></indexterm>
-    <indexterm><primary>column</primary></indexterm>
-
-    Each table is a named collection of <firstterm>rows</firstterm>.
-    Each row of a given table has the same set of named
-    <firstterm>columns</firstterm>,
-    and each column is of a specific data type.  Whereas columns have
-    a fixed order in each row, it is important to remember that SQL
-    does not guarantee the order of the rows within the table in any
-    way (although they can be explicitly sorted for display).
-   </para>
-
-   <para>
-    <indexterm><primary>database cluster</primary></indexterm>
-    <indexterm><primary>cluster</primary><secondary>of databases</secondary><see>database cluster</see></indexterm>
-
-<!## PG>
-    Tables are grouped into databases, and a collection of databases
-    managed by a single <productname>PostgreSQL</productname> server
-    instance constitutes a database <firstterm>cluster</firstterm>.
-<!## end>
-
-<!## XC>
-    Tables are grouped into databases, and a collection of databases
-    managed by a single <productname>Postgres-XC</productname> server
-    instance constitutes a database <firstterm>cluster</firstterm>.
-   </para>
-   <para>
-&xconly;
-    In <productname>Postgres-XC</> these databases can be distributed into more than one Datanodes.
-    This will not affect how tables and rows are seen from applications point of view, but will be
-    important for Database Administrator (DBA).
-    Table distribution will be described later.
-<!--
-    TODO:
-    Add reference point of the above.
--->
-   </para>
-<!## end>
-<!## XL>
-    Tables are grouped into databases, and a collection of databases
-    managed by a single <productname>Postgres-XL</productname> 
-    <firstterm>cluster</firstterm>.
-   </para>
-   <para>
-&xlonly;
-    In <productname>Postgres-XL</> these databases can be distributed onto more than one Datanodes.
-    This will not affect how tables and rows are seen from applications' point of view, but will be
-    important for Database Administrator (DBA).
-    Table distribution will be described later.
-<!--
-    TODO:
-    Add reference point of the above.
--->
-   </para>
-<!## end>
-  </sect1>
-
-
-  <sect1 id="tutorial-table">
-   <title>Creating a New Table</title>
-
-   <indexterm zone="tutorial-table">
-    <primary>CREATE TABLE</primary>
-   </indexterm>
-
-&common;
-   <para>
-    You  can  create  a  new  table by specifying the table
-    name, along with all column names and their types:
-
-<programlisting>
-CREATE TABLE weather (
-    city            varchar(80),
-    temp_lo         int,           -- low temperature
-    temp_hi         int,           -- high temperature
-    prcp            real,          -- precipitation
-    date            date
-);
-</programlisting>
-
-    You can enter this into <command>psql</command> with the line
-    breaks.  <command>psql</command> will recognize that the command
-    is not terminated until the semicolon.
-   </para>
-
-   <para>
-    White space (i.e., spaces, tabs, and newlines) can be used freely
-    in SQL commands.  That means you can type the command aligned
-    differently than above, or even all on one line.  Two dashes
-    (<quote><literal>--</literal></quote>) introduce comments.
-    Whatever follows them is ignored up to the end of the line.  SQL
-    is case insensitive about key words and identifiers, except
-    when identifiers are double-quoted to preserve the case (not done
-    above).
-   </para>
-
-   <para>
-    <type>varchar(80)</type> specifies a data type that can store
-    arbitrary character strings up to 80 characters in length.
-    <type>int</type> is the normal integer type.  <type>real</type> is
-    a type for storing single precision floating-point numbers.
-    <type>date</type> should be self-explanatory.  (Yes, the column of
-    type <type>date</type> is also named <structfield>date</structfield>.
-    This might be convenient or confusing &mdash; you choose.)
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> supports the standard
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> supports the standard
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> supports the standard
-<!## end>
-    <acronym>SQL</acronym> types <type>int</type>,
-    <type>smallint</type>, <type>real</type>, <type>double
-    precision</type>, <type>char(<replaceable>N</>)</type>,
-    <type>varchar(<replaceable>N</>)</type>, <type>date</type>,
-    <type>time</type>, <type>timestamp</type>, and
-    <type>interval</type>, as well as other types of general utility
-    and a rich set of geometric types.
-<!## PG>
-    <productname>PostgreSQL</productname> can be customized with an
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> can be customized with an
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> can be customized with an
-<!## end>
-    arbitrary number of user-defined data types.  Consequently, type
-    names are not key words in the syntax, except where required to
-    support special cases in the <acronym>SQL</acronym> standard.
-   </para>
-
-   <para>
-    The second example will store cities and their associated
-    geographical location:
-<programlisting>
-CREATE TABLE cities (
-    name            varchar(80),
-    location        point
-);
-</programlisting>
-    The <type>point</type> type is an example of a
-<!## PG>
-    <productname>PostgreSQL</productname>-specific data type.
-<!## end>
-   </para>
-<!## XL>
-	<para>
- 	<productname>Postgres-XL</productname> distributes every table by one of
-the supported distribution mechanisms such as <type>HASH</type>,
-<type>ROUNDROBIN</type>,<type>MODULO</type> and <type>REPLICATION</type>. By
-default <productname>Postgres-XL</productname> will choose a distribution
-strategy based on the column definition, but most often user will specify a
-specific distribution strategy using the <type>DISTRIBUTE BY</type> option. The
-following example shows that.
-
-<programlisting>
-CREATE TABLE my_distributed_table (
-	tab_key		integer,
-	tab_value	text
-) DISTRIBUTE BY HASH(tab_key);
-</programlisting>
-	In this case the table will be distributed to all nodes in the cluster
-based on the hash computed value of the column <type>tab_key</type>.
-
-	</para>
-<!## end>
-
-   <para>
-    <indexterm>
-     <primary>DROP TABLE</primary>
-    </indexterm>
-
-    Finally, it should be mentioned that if you don't need a table any
-    longer or want to recreate it differently you can remove it using
-    the following command:
-<synopsis>
-DROP TABLE <replaceable>tablename</replaceable>;
-</synopsis>
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-populate">
-   <title>Populating a Table With Rows</title>
-
-   <indexterm zone="tutorial-populate">
-    <primary>INSERT</primary>
-   </indexterm>
-&common;
-   <para>
-    The <command>INSERT</command> statement is used to populate a table  with
-    rows:
-
-<programlisting>
-INSERT INTO weather VALUES ('San Francisco', 46, 50, 0.25, '1994-11-27');
-</programlisting>
-
-    Note that all data types use rather obvious input formats.
-    Constants that are not simple numeric values usually must be
-    surrounded by single quotes (<literal>'</>), as in the example.
-    The
-    <type>date</type> type is actually quite flexible in what it
-    accepts, but for this tutorial we will stick to the unambiguous
-    format shown here.
-   </para>
-
-   <para>
-    The <type>point</type> type requires a coordinate pair as input,
-    as shown here:
-<programlisting>
-INSERT INTO cities VALUES ('San Francisco', '(-194.0, 53.0)');
-</programlisting>
-   </para>
-
-   <para>
-    The syntax used so far requires you to remember the order of the
-    columns.  An alternative syntax allows you to list the columns
-    explicitly:
-<programlisting>
-INSERT INTO weather (city, temp_lo, temp_hi, prcp, date)
-    VALUES ('San Francisco', 43, 57, 0.0, '1994-11-29');
-</programlisting>
-    You can list the columns in a different order if you wish or
-    even omit some columns, e.g., if the precipitation is unknown:
-<programlisting>
-INSERT INTO weather (date, city, temp_hi, temp_lo)
-    VALUES ('1994-11-29', 'Hayward', 54, 37);
-</programlisting>
-    Many developers consider explicitly listing the columns better
-    style than relying on the order implicitly.
-   </para>
-
-   <para>
-    Please enter all the commands shown above so you have some data to
-    work with in the following sections.
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>COPY</primary>
-    </indexterm>
-&common;
-    You could also have used <command>COPY</command> to load large
-    amounts of data from flat-text files.  This is usually faster
-    because the <command>COPY</command> command is optimized for this
-    application while allowing less flexibility than
-    <command>INSERT</command>.  An example would be:
-
-<programlisting>
-COPY weather FROM '/home/user/weather.txt';
-</programlisting>
-
-    where the file name for the source file must be available on the
-    machine running the backend process, not the client, since the backend process
-    reads the file directly.  You can read more about the
-    <command>COPY</command> command in <xref linkend="sql-copy">.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-select">
-   <title>Querying a Table</title>
-
-   <para>
-    <indexterm><primary>query</primary></indexterm>
-    <indexterm><primary>SELECT</primary></indexterm>
-&common;
-    To retrieve data from a table, the table is
-    <firstterm>queried</firstterm>.  An <acronym>SQL</acronym>
-    <command>SELECT</command> statement is used to do this.  The
-    statement is divided into a select list (the part that lists the
-    columns to be returned), a table list (the part that lists the
-    tables from which to retrieve the data), and an optional
-    qualification (the part that specifies any restrictions).  For
-    example, to retrieve all the rows of table
-    <structname>weather</structname>, type:
-<programlisting>
-SELECT * FROM weather;
-</programlisting>
-    Here <literal>*</literal> is a shorthand for <quote>all columns</quote>.
-     <footnote>
-      <para>
-       While <literal>SELECT *</literal> is useful for off-the-cuff
-       queries, it is widely considered bad style in production code,
-       since adding a column to the table would change the results.
-      </para>
-     </footnote>
-    So the same result would be had with:
-<programlisting>
-SELECT city, temp_lo, temp_hi, prcp, date FROM weather;
-</programlisting>
-
-    The output should be:
-
-<screen>
-     city      | temp_lo | temp_hi | prcp |    date
----------------+---------+---------+------+------------
- San Francisco |      46 |      50 | 0.25 | 1994-11-27
- San Francisco |      43 |      57 |    0 | 1994-11-29
- Hayward       |      37 |      54 |      | 1994-11-29
-(3 rows)
-</screen>
-   </para>
-
-   <para>
-    You can write expressions, not just simple column references, in the
-    select list.  For example, you can do:
-<programlisting>
-SELECT city, (temp_hi+temp_lo)/2 AS temp_avg, date FROM weather;
-</programlisting>
-    This should give:
-<screen>
-     city      | temp_avg |    date
----------------+----------+------------
- San Francisco |       48 | 1994-11-27
- San Francisco |       50 | 1994-11-29
- Hayward       |       45 | 1994-11-29
-(3 rows)
-</screen>
-    Notice how the <literal>AS</literal> clause is used to relabel the
-    output column.  (The <literal>AS</literal> clause is optional.)
-   </para>
-
-   <para>
-    A query can be <quote>qualified</> by adding a <literal>WHERE</>
-    clause that specifies which rows are wanted.  The <literal>WHERE</>
-    clause contains a Boolean (truth value) expression, and only rows for
-    which the Boolean expression is true are returned.  The usual
-    Boolean operators (<literal>AND</literal>,
-    <literal>OR</literal>, and <literal>NOT</literal>) are allowed in
-    the qualification.  For example, the following
-    retrieves the weather of San Francisco on rainy days:
-
-<programlisting>
-SELECT * FROM weather
-    WHERE city = 'San Francisco' AND prcp &gt; 0.0;
-</programlisting>
-    Result:
-<screen>
-     city      | temp_lo | temp_hi | prcp |    date
----------------+---------+---------+------+------------
- San Francisco |      46 |      50 | 0.25 | 1994-11-27
-(1 row)
-</screen>
-   </para>
-
-   <para>
-    <indexterm><primary>ORDER BY</primary></indexterm>
-
-    You can request that the results of a query
-    be returned in sorted order:
-
-<programlisting>
-SELECT * FROM weather
-    ORDER BY city;
-</programlisting>
-
-<screen>
-     city      | temp_lo | temp_hi | prcp |    date
----------------+---------+---------+------+------------
- Hayward       |      37 |      54 |      | 1994-11-29
- San Francisco |      43 |      57 |    0 | 1994-11-29
- San Francisco |      46 |      50 | 0.25 | 1994-11-27
-</screen>
-
-    In this example, the sort order isn't fully specified, and so you
-    might get the San Francisco rows in either order.  But you'd always
-    get the results shown above if you do:
-
-<programlisting>
-SELECT * FROM weather
-    ORDER BY city, temp_lo;
-</programlisting>
-   </para>
-
-   <para>
-    <indexterm><primary>DISTINCT</primary></indexterm>
-    <indexterm><primary>duplicate</primary></indexterm>
-
-    You can request that duplicate rows be removed from the result of
-    a query:
-
-<programlisting>
-SELECT DISTINCT city
-    FROM weather;
-</programlisting>
-
-<screen>
-     city
----------------
- Hayward
- San Francisco
-(2 rows)
-</screen>
-
-    Here again, the result row ordering might vary.
-    You can ensure consistent results by using <literal>DISTINCT</literal> and
-    <literal>ORDER BY</literal> together:
-     <footnote>
-      <para>
-       In some database systems, including older versions of
-<!## PG>
-       <productname>PostgreSQL</productname>, the implementation of
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</productname>, the implementation of
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</productname>, the implementation of
-<!## end>
-       <literal>DISTINCT</literal> automatically orders the rows and
-       so <literal>ORDER BY</literal> is unnecessary.  But this is not
-       required by the SQL standard, and current
-<!## PG>
-       <productname>PostgreSQL</productname> does not guarantee that
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</productname> does not guarantee that
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</productname> does not guarantee that
-<!## end>
-       <literal>DISTINCT</literal> causes the rows to be ordered.
-      </para>
-     </footnote>
-
-<programlisting>
-SELECT DISTINCT city
-    FROM weather
-    ORDER BY city;
-</programlisting>
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-join">
-   <title>Joins Between Tables</title>
-
-   <indexterm zone="tutorial-join">
-    <primary>join</primary>
-   </indexterm>
-&common;
-   <para>
-    Thus far, our queries have only accessed one table at a time.
-    Queries can access multiple tables at once, or access the same
-    table in such a way that multiple rows of the table are being
-    processed at the same time.  A query that accesses multiple rows
-    of the same or different tables at one time is called a
-    <firstterm>join</firstterm> query.  As an example, say you wish to
-    list all the weather records together with the location of the
-    associated city.  To do that, we need to compare the <structfield>city</>
-    column of each row of the <structname>weather</> table with the
-    <structfield>name</> column of all rows in the <structname>cities</>
-    table, and select the pairs of rows where these values match.
-    <note>
-     <para>
-      This  is only a conceptual model.  The join is usually performed
-      in a more efficient manner than actually comparing each possible
-      pair of rows, but this is invisible to the user.
-     </para>
-    </note>
-    This would be accomplished by the following query:
-
-<programlisting>
-SELECT *
-    FROM weather, cities
-    WHERE city = name;
-</programlisting>
-
-<screen>
-     city      | temp_lo | temp_hi | prcp |    date    |     name      | location
----------------+---------+---------+------+------------+---------------+-----------
- San Francisco |      46 |      50 | 0.25 | 1994-11-27 | San Francisco | (-194,53)
- San Francisco |      43 |      57 |    0 | 1994-11-29 | San Francisco | (-194,53)
-(2 rows)
-</screen>
-
-   </para>
-
-   <para>
-    Observe two things about the result set:
-    <itemizedlist>
-     <listitem>
-      <para>
-       There is no result row for the city of Hayward.  This is
-       because there is no matching entry in the
-       <structname>cities</structname> table for Hayward, so the join
-       ignores the unmatched rows in the <structname>weather</> table.  We will see
-       shortly how this can be fixed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       There are two columns containing the city name.  This is
-       correct because the lists of columns from the
-       <structname>weather</structname> and
-       <structname>cities</structname> tables are concatenated.  In
-       practice this is undesirable, though, so you will probably want
-       to list the output columns explicitly rather than using
-       <literal>*</literal>:
-<programlisting>
-SELECT city, temp_lo, temp_hi, prcp, date, location
-    FROM weather, cities
-    WHERE city = name;
-</programlisting>
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <formalpara>
-    <title>Exercise:</title>
-
-    <para>
-     Attempt to determine the semantics of this query when the
-     <literal>WHERE</literal> clause is omitted.
-    </para>
-   </formalpara>
-
-   <para>
-    Since the columns all had different names, the parser
-    automatically found which table they belong to.  If there
-    were duplicate column names in the two tables you'd need to
-    <firstterm>qualify</> the column names to show which one you
-    meant, as in:
-
-<programlisting>
-SELECT weather.city, weather.temp_lo, weather.temp_hi,
-       weather.prcp, weather.date, cities.location
-    FROM weather, cities
-    WHERE cities.name = weather.city;
-</programlisting>
-
-    It is widely considered good style to qualify all column names
-    in a join query, so that the query won't fail if a duplicate
-    column name is later added to one of the tables.
-   </para>
-
-   <para>
-    Join queries of the kind seen thus far can also be written in this
-    alternative form:
-
-<programlisting>
-SELECT *
-    FROM weather INNER JOIN cities ON (weather.city = cities.name);
-</programlisting>
-
-    This syntax is not as commonly used as the one above, but we show
-    it here to help you understand the following topics.
-   </para>
-
-   <para>
-    <indexterm><primary>join</primary><secondary>outer</secondary></indexterm>
-
-    Now we will figure out how we can get the Hayward records back in.
-    What we want the query to do is to scan the
-    <structname>weather</structname> table and for each row to find the
-    matching <structname>cities</structname> row(s).  If no matching row is
-    found we want some <quote>empty values</quote> to be substituted
-    for the <structname>cities</structname> table's columns.  This kind
-    of query is called an <firstterm>outer join</firstterm>.  (The
-    joins we have seen so far are inner joins.)  The command looks
-    like this:
-
-<programlisting>
-SELECT *
-    FROM weather LEFT OUTER JOIN cities ON (weather.city = cities.name);
-
-     city      | temp_lo | temp_hi | prcp |    date    |     name      | location
----------------+---------+---------+------+------------+---------------+-----------
- Hayward       |      37 |      54 |      | 1994-11-29 |               |
- San Francisco |      46 |      50 | 0.25 | 1994-11-27 | San Francisco | (-194,53)
- San Francisco |      43 |      57 |    0 | 1994-11-29 | San Francisco | (-194,53)
-(3 rows)
-</programlisting>
-
-    This query is called a <firstterm>left outer
-    join</firstterm> because the table mentioned on the left of the
-    join operator will have each of its rows in the output at least
-    once, whereas the table on the right will only have those rows
-    output that match some row of the left table.  When outputting a
-    left-table row for which there is no right-table match, empty (null)
-    values are substituted for the right-table columns.
-   </para>
-
-   <formalpara>
-    <title>Exercise:</title>
-
-    <para>
-     There are also right outer joins and full outer joins.  Try to
-     find out what those do.
-    </para>
-   </formalpara>
-
-   <para>
-    <indexterm><primary>join</primary><secondary>self</secondary></indexterm>
-    <indexterm><primary>alias</primary><secondary>for table name in query</secondary></indexterm>
-
-    We can also join a table against itself.  This is called a
-    <firstterm>self join</firstterm>.  As an example, suppose we wish
-    to find all the weather records that are in the temperature range
-    of other weather records.  So we need to compare the
-    <structfield>temp_lo</> and <structfield>temp_hi</> columns of
-    each <structname>weather</structname> row to the
-    <structfield>temp_lo</structfield> and
-    <structfield>temp_hi</structfield> columns of all other
-    <structname>weather</structname> rows.  We can do this with the
-    following query:
-
-<programlisting>
-SELECT W1.city, W1.temp_lo AS low, W1.temp_hi AS high,
-    W2.city, W2.temp_lo AS low, W2.temp_hi AS high
-    FROM weather W1, weather W2
-    WHERE W1.temp_lo &lt; W2.temp_lo
-    AND W1.temp_hi &gt; W2.temp_hi;
-
-     city      | low | high |     city      | low | high
----------------+-----+------+---------------+-----+------
- San Francisco |  43 |   57 | San Francisco |  46 |   50
- Hayward       |  37 |   54 | San Francisco |  46 |   50
-(2 rows)
-</programlisting>
-
-    Here we have relabeled the weather table as <literal>W1</> and
-    <literal>W2</> to be able to distinguish the left and right side
-    of the join.  You can also use these kinds of aliases in other
-    queries to save some typing, e.g.:
-<programlisting>
-SELECT *
-    FROM weather w, cities c
-    WHERE w.city = c.name;
-</programlisting>
-    You will encounter this style of abbreviating quite frequently.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-agg">
-   <title>Aggregate Functions</title>
-
-   <indexterm zone="tutorial-agg">
-    <primary>aggregate function</primary>
-   </indexterm>
-&common;
-   <para>
-    Like  most  other relational database products,
-<!## PG>
-    <productname>PostgreSQL</productname> supports
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> supports
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> supports
-<!## end>
-    <firstterm>aggregate functions</>.
-    An aggregate function computes a single result from multiple input rows.
-    For example, there are aggregates to compute the
-    <function>count</function>, <function>sum</function>,
-    <function>avg</function> (average), <function>max</function> (maximum) and
-    <function>min</function> (minimum) over a set of rows.
-   </para>
-
-   <para>
-    As an example, we can find the highest low-temperature reading anywhere
-    with:
-
-<programlisting>
-SELECT max(temp_lo) FROM weather;
-</programlisting>
-
-<screen>
- max
------
-  46
-(1 row)
-</screen>
-   </para>
-
-<!## PG>
-<!-- NOTE:
-     XC does not support subquery correctly yet.
--->
-   <para>
-    <indexterm><primary>subquery</primary></indexterm>
-
-    If we wanted to know what city (or cities) that reading occurred in,
-    we might try:
-
-<programlisting>
-SELECT city FROM weather WHERE temp_lo = max(temp_lo);     <lineannotation>WRONG</lineannotation>
-</programlisting>
-
-    but this will not work since the aggregate
-    <function>max</function> cannot be used in the
-    <literal>WHERE</literal> clause.  (This restriction exists because
-    the <literal>WHERE</literal> clause determines which rows will be
-    included in the aggregate calculation; so obviously it has to be evaluated
-    before aggregate functions are computed.)
-    However, as is often the case
-    the query can be restated to accomplish the desired result, here
-    by using a <firstterm>subquery</firstterm>:
-
-<programlisting>
-SELECT city FROM weather
-    WHERE temp_lo = (SELECT max(temp_lo) FROM weather);
-</programlisting>
-
-<screen>
-     city
----------------
- San Francisco
-(1 row)
-</screen>
-
-    This is OK because the subquery is an independent computation
-    that computes its own aggregate separately from what is happening
-    in the outer query.
-   </para>
-
-<!## end>
-
-   <para>
-    <indexterm><primary>GROUP BY</primary></indexterm>
-    <indexterm><primary>HAVING</primary></indexterm>
-
-    Aggregates are also very useful in combination with <literal>GROUP
-    BY</literal> clauses.  For example, we can get the maximum low
-    temperature observed in each city with:
-
-<programlisting>
-SELECT city, max(temp_lo)
-    FROM weather
-    GROUP BY city;
-</programlisting>
-
-<screen>
-     city      | max
----------------+-----
- Hayward       |  37
- San Francisco |  46
-(2 rows)
-</screen>
-
-    which gives us one output row per city.  Each aggregate result is
-    computed over the table rows matching that city.
-
-<!## PG>
-<!-- NOTE
-     We don't have HAVING yet.
--->
-
-    We can filter these grouped
-    rows using <literal>HAVING</literal>:
-
-<programlisting>
-SELECT city, max(temp_lo)
-    FROM weather
-    GROUP BY city
-    HAVING max(temp_lo) &lt; 40;
-</programlisting>
-
-<screen>
-  city   | max
----------+-----
- Hayward |  37
-(1 row)
-</screen>
-
-    which gives us the same results for only the cities that have all
-    <structfield>temp_lo</> values below 40.  Finally, if we only care about
-    cities whose
-    names begin with <quote><literal>S</literal></quote>, we might do:
-
-<programlisting>
-SELECT city, max(temp_lo)
-    FROM weather
-    WHERE city LIKE 'S%'<co id="co.tutorial-agg-like">
-    GROUP BY city
-    HAVING max(temp_lo) &lt; 40;
-</programlisting>
-   <calloutlist>
-    <callout arearefs="co.tutorial-agg-like">
-     <para>
-      The <literal>LIKE</literal> operator does pattern matching and
-      is explained in <xref linkend="functions-matching">.
-     </para>
-    </callout>
-   </calloutlist>
-   </para>
-
-   <para>
-    It is important to understand the interaction between aggregates and
-    <acronym>SQL</acronym>'s <literal>WHERE</literal> and <literal>HAVING</literal> clauses.
-    The fundamental difference between <literal>WHERE</literal> and
-    <literal>HAVING</literal> is this: <literal>WHERE</literal> selects
-    input rows before groups and aggregates are computed (thus, it controls
-    which rows go into the aggregate computation), whereas
-    <literal>HAVING</literal> selects group rows after groups and
-    aggregates are computed.  Thus, the
-    <literal>WHERE</literal> clause must not contain aggregate functions;
-    it makes no sense to try to use an aggregate to determine which rows
-    will be inputs to the aggregates.  On the other hand, the
-    <literal>HAVING</literal> clause always contains aggregate functions.
-    (Strictly speaking, you are allowed to write a <literal>HAVING</literal>
-    clause that doesn't use aggregates, but it's seldom useful. The same
-    condition could be used more efficiently at the <literal>WHERE</literal>
-    stage.)
-   </para>
-
-   <para>
-    In the previous example, we can apply the city name restriction in
-    <literal>WHERE</literal>, since it needs no aggregate.  This is
-    more efficient than adding the restriction to <literal>HAVING</literal>,
-    because we avoid doing the grouping and aggregate calculations
-    for all rows that fail the <literal>WHERE</literal> check.
-<!## end>
-   </para>
-
-  </sect1>
-
-
-  <sect1 id="tutorial-update">
-   <title>Updates</title>
-
-   <indexterm zone="tutorial-update">
-    <primary>UPDATE</primary>
-   </indexterm>
-&common;
-   <para>
-    You can update existing rows using the
-    <command>UPDATE</command> command.
-    Suppose you discover the temperature readings are
-    all off by 2 degrees after November 28.  You can correct the
-    data as follows:
-
-<programlisting>
-UPDATE weather
-    SET temp_hi = temp_hi - 2,  temp_lo = temp_lo - 2
-    WHERE date &gt; '1994-11-28';
-</programlisting>
-   </para>
-
-   <para>
-    Look at the new state of the data:
-<programlisting>
-SELECT * FROM weather;
-
-     city      | temp_lo | temp_hi | prcp |    date
----------------+---------+---------+------+------------
- San Francisco |      46 |      50 | 0.25 | 1994-11-27
- San Francisco |      41 |      55 |    0 | 1994-11-29
- Hayward       |      35 |      52 |      | 1994-11-29
-(3 rows)
-</programlisting>
-   </para>
-  </sect1>
-
-  <sect1 id="tutorial-delete">
-   <title>Deletions</title>
-
-   <indexterm zone="tutorial-delete">
-    <primary>DELETE</primary>
-   </indexterm>
-&common;
-   <para>
-    Rows can be removed from a table using the <command>DELETE</command>
-    command.
-    Suppose you are no longer interested in the weather of Hayward.
-    Then you can do the following to delete those rows from the table:
-<programlisting>
-DELETE FROM weather WHERE city = 'Hayward';
-</programlisting>
-
-    All weather records belonging to Hayward are removed.
-
-<programlisting>
-SELECT * FROM weather;
-</programlisting>
-
-<screen>
-     city      | temp_lo | temp_hi | prcp |    date
----------------+---------+---------+------+------------
- San Francisco |      46 |      50 | 0.25 | 1994-11-27
- San Francisco |      41 |      55 |    0 | 1994-11-29
-(2 rows)
-</screen>
-   </para>
-
-   <para>
-    One should be wary of statements of the form
-<synopsis>
-DELETE FROM <replaceable>tablename</replaceable>;
-</synopsis>
-
-    Without a qualification, <command>DELETE</command> will
-    remove  <emphasis>all</>  rows from the given table, leaving it
-    empty.  The system will not request confirmation before
-    doing this!
-   </para>
-  </sect1>
-
- </chapter>
diff --git a/doc-xc/src/sgml/recovery-config.sgmlin b/doc-xc/src/sgml/recovery-config.sgmlin
deleted file mode 100644
index 9c2b405ff7..0000000000
--- a/doc-xc/src/sgml/recovery-config.sgmlin
+++ /dev/null
@@ -1,493 +0,0 @@
-<!-- doc/src/sgml/recovery-config.sgml -->
-
-<chapter id="recovery-config">
-  <title>Recovery Configuration</title>
-
-  <indexterm>
-   <primary>configuration</primary>
-   <secondary>of recovery</secondary>
-   <tertiary>of a standby server</tertiary>
-  </indexterm>
-
-   <para>
-    This chapter describes the settings available in the
-    <filename>recovery.conf</> file. They apply only for the duration of the
-    recovery.  They must be reset for any subsequent recovery you wish to
-    perform.  They cannot be changed once recovery has begun.
-   </para>
-
-   <para>
-     Settings in <filename>recovery.conf</> are specified in the format
-     <literal>name = 'value'</>. One parameter is specified per line.
-     Hash marks (<literal>#</literal>) designate the rest of the
-     line as a comment.  To embed a single quote in a parameter
-     value, write two quotes (<literal>''</>).
-   </para>
-
-   <para>
-    A sample file, <filename>share/recovery.conf.sample</>,
-    is provided in the installation's <filename>share/</> directory.
-   </para>
-
-  <sect1 id="archive-recovery-settings">
-
-    <title>Archive Recovery Settings</title>
-&common;
-     <variablelist>
-
-     <varlistentry id="restore-command" xreflabel="restore_command">
-      <term><varname>restore_command</varname> (<type>string</type>)</term>
-      <indexterm>
-        <primary><varname>restore_command</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        The shell command to execute to retrieve an archived segment of
-        the WAL file series. This parameter is required for archive recovery,
-        but optional for streaming replication.
-        Any <literal>%f</> in the string is
-        replaced by the name of the file to retrieve from the archive,
-        and any <literal>%p</> is replaced by the copy destination path name
-        on the server.
-        (The path name is relative to the current working directory,
-        i.e., the cluster's data directory.)
-        Any <literal>%r</> is replaced by the name of the file containing the
-        last valid restart point. That is the earliest file that must be kept
-        to allow a restore to be restartable, so this information can be used
-        to truncate the archive to just the minimum required to support
-        restarting from the current restore. <literal>%r</> is typically only
-        used by warm-standby configurations
-<!## PG>
-        (see <xref linkend="warm-standby">).
-<!## end>
-<!## XC>
-.
-<!## end>
-<!## XL>
-.
-<!## end>
-<!## XC>
-        <footnote>
-         <para>
-         Although <productname>Postgres-XC</productname> does not
-          prohibit to use warm-standby, in either Coordinators or
-          Datanodes (see <xref linkend="xc-overview">), there's no
-          guarantee that warm-standbys are synchronized.  If you use
-          warm standby for high availability feature, there's a risk
-          that data in Coordinators and Datanodes are inconsistent.
-          It is highly recommended to use <command>BARRIER</command>.
-         </para>
-        </footnote>
-<!## end>
-<!## XL>
-        <footnote>
-         <para>
-         Although <productname>Postgres-XL</productname> does not
-          prohibit to use warm-standby, in either Coordinators or
-          Datanodes (see <xref linkend="xc-overview">), there's no
-          guarantee that warm-standbys are synchronized.  If you use
-          warm standby for high availability feature, there's a risk
-          that data in Coordinators and Datanodes are inconsistent.
-          It is highly recommended to use <command>BARRIER</command>.
-         </para>
-        </footnote>
-<!## end>
-        Write <literal>%%</> to embed an actual <literal>%</> character.
-       </para>
-
-       <para>
-        It is important for the command to return a zero exit status
-        only if it succeeds.  The command <emphasis>will</> be asked for file
-        names that are not present in the archive; it must return nonzero
-        when so asked.  Examples:
-<programlisting>
-restore_command = 'cp /mnt/server/archivedir/%f "%p"'
-restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"'  # Windows
-</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="archive-cleanup-command" xreflabel="archive_cleanup_command">
-      <term><varname>archive_cleanup_command</varname> (<type>string</type>)</term>
-      <indexterm>
-        <primary><varname>archive_cleanup_command</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This optional parameter specifies a shell command that will be executed
-        at every restartpoint.  The purpose of
-        <varname>archive_cleanup_command</> is to provide a mechanism for
-        cleaning up old archived WAL files that are no longer needed by the
-        standby server.
-        Any <literal>%r</> is replaced by the name of the file containing the
-        last valid restart point.
-        That is the earliest file that must be <emphasis>kept</> to allow a
-        restore to be restartable, and so all files earlier than <literal>%r</>
-        may be safely removed.
-        This information can be used to truncate the archive to just the
-        minimum required to support restart from the current restore.
-        The <xref linkend="pgarchivecleanup"> module
-        is often used in <varname>archive_cleanup_command</> for
-        single-standby configurations, for example:
-<programlisting>archive_cleanup_command = 'pg_archivecleanup /mnt/server/archivedir %r'</programlisting>
-        Note however that if multiple standby servers are restoring from the
-        same archive directory, you will need to ensure that you do not delete
-        WAL files until they are no longer needed by any of the servers.
-        <varname>archive_cleanup_command</> would typically be used in a
-<!## PG>
-        warm-standby configuration (see <xref linkend="warm-standby">).
-<!## end>
-<!## XC>
-        warm-standby configuration.
-<!## end>
-<!## XL>
-        warm-standby configuration.
-<!## end>
-        Write <literal>%%</> to embed an actual <literal>%</> character in the
-        command.
-       </para>
-       <para>
-        If the command returns a non-zero exit status then a WARNING log
-        message will be written.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="recovery-end-command" xreflabel="recovery_end_command">
-      <term><varname>recovery_end_command</varname> (<type>string</type>)</term>
-      <indexterm>
-        <primary><varname>recovery_end_command</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This parameter specifies a shell command that will be executed once only
-        at the end of recovery. This parameter is optional. The purpose of the
-        <varname>recovery_end_command</> is to provide a mechanism for cleanup
-        following replication or recovery.
-        Any <literal>%r</> is replaced by the name of the file containing the
-        last valid restart point, like in <xref linkend="archive-cleanup-command">.
-       </para>
-       <para>
-        If the command returns a non-zero exit status then a WARNING log
-        message will be written and the database will proceed to start up
-        anyway.  An exception is that if the command was terminated by a
-        signal, the database will not proceed with startup.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-  </sect1>
-
-  <sect1 id="recovery-target-settings">
-
-    <title>Recovery Target Settings</title>
-&common;
-     <variablelist>
-
-     <varlistentry id="recovery-target-name" xreflabel="recovery_target_name">
-      <term><varname>recovery_target_name</varname>
-           (<type>string</type>)
-      </term>
-      <indexterm>
-        <primary><varname>recovery_target_name</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This parameter specifies the named restore point, created with
-        <function>pg_create_restore_point()</> to which recovery will proceed.
-        At most one of <varname>recovery_target_name</>,
-        <xref linkend="recovery-target-time"> or
-        <xref linkend="recovery-target-xid"> can be specified.  The default is to
-        recover to the end of the WAL log.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="recovery-target-time" xreflabel="recovery_target_time">
-      <term><varname>recovery_target_time</varname>
-           (<type>timestamp</type>)
-      </term>
-      <indexterm>
-        <primary><varname>recovery_target_time</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This parameter specifies the time stamp up to which recovery
-        will proceed.
-<!## PG>
-        At most one of <varname>recovery_target_time</>,
-        <xref linkend="recovery-target-name"> or
-        <xref linkend="recovery-target-xid"> can be specified.
-<!## end>
-<!## XC>
-&xconly;
-        At most one of <varname>recovery_target_time</>,
-        <xref linkend="recovery-target-name">,
-        <xref linkend="recovery-target-xid"> or
-        <xref linkend="recovery-target-barrier"> can be specified.
-<!## end>
-<!## XL>
-&xlonly;
-        At most one of <varname>recovery_target_time</>,
-        <xref linkend="recovery-target-name">,
-        <xref linkend="recovery-target-xid"> or
-        <xref linkend="recovery-target-barrier"> can be specified.
-<!## end>
-        The default is to recover to the end of the WAL log.
-        The precise stopping point is also influenced by
-        <xref linkend="recovery-target-inclusive">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="recovery-target-xid" xreflabel="recovery_target_xid">
-      <term><varname>recovery_target_xid</varname> (<type>string</type>)</term>
-      <indexterm>
-        <primary><varname>recovery_target_xid</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        This parameter specifies the transaction ID up to which recovery
-        will proceed. Keep in mind
-        that while transaction IDs are assigned sequentially at transaction
-        start, transactions can complete in a different numeric order.
-        The transactions that will be recovered are those that committed
-        before (and optionally including) the specified one.
-<!## PG>
-        At most one of <varname>recovery_target_xid</>,
-        <xref linkend="recovery-target-name"> or
-        <xref linkend="recovery-target-time"> can be specified.
-<!## end>
-<!## XC>
-        At most one of <varname>recovery_target_xid</>,
-        <xref linkend="recovery-target-name">,
-        <xref linkend="recovery-target-time"> or
-        <xref linkend="recovery-target-barrier"> can be specified.
-
-        The default is to recover to the end of the WAL log.
-        The precise stopping point is also influenced by
-        <xref linkend="recovery-target-inclusive">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="recovery-target-barrier" xreflabel="recovery_target_barrier">
-      <term><varname>recovery_target_barrier</varname> (<type>string</type>)</term>
-      <indexterm>
-        <primary><varname>recovery_target_barrier</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-&xconly;
-       <para>
-        This parameter specifies the barrier ID up to which recovery
-        will proceed. A global consistency is guaranteed when recovery is
-        stopped at a previously successfully completed barrier. At most
-        one of <varname>recovery_target_xid</>,
-        <xref linkend="recovery-target-time"> and 
-        <varname>recovery_target_barrier</> can be specified.
-<!## end>
-<!## XL>
-        At most one of <varname>recovery_target_xid</>,
-        <xref linkend="recovery-target-name">,
-        <xref linkend="recovery-target-time"> or
-        <xref linkend="recovery-target-barrier"> can be specified.
-
-        The default is to recover to the end of the WAL log.
-        The precise stopping point is also influenced by
-        <xref linkend="recovery-target-inclusive">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="recovery-target-barrier" xreflabel="recovery_target_barrier">
-      <term><varname>recovery_target_barrier</varname> (<type>string</type>)</term>
-      <indexterm>
-        <primary><varname>recovery_target_barrier</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-&xlonly;
-       <para>
-        This parameter specifies the barrier ID up to which recovery
-        will proceed. A global consistency is guaranteed when recovery is
-        stopped at a previously successfully completed barrier. At most
-        one of <varname>recovery_target_xid</>,
-        <xref linkend="recovery-target-time"> and 
-        <varname>recovery_target_barrier</> can be specified.
-<!## end>
-        The default is to recover to the end of the WAL log.
-        The precise stopping point is also influenced by
-        <xref linkend="recovery-target-inclusive">.
-       </para>
-
-       <para>
-        A barrier ID, to which recovery will proceed, has to be specified with
-        <xref linkend="SQL-CREATEBARRIER">. Refer to this command for syntax details.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="recovery-target-inclusive"
-                   xreflabel="recovery_target_inclusive">
-      <term><varname>recovery_target_inclusive</varname>
-        (<type>boolean</type>)
-      </term>
-      <indexterm>
-        <primary><varname>recovery_target_inclusive</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-&common;
-       <para>
-        Specifies whether we stop just after the specified recovery target
-        (<literal>true</literal>), or just before the recovery target
-        (<literal>false</literal>).
-        Applies to both <xref linkend="recovery-target-time">
-        and <xref linkend="recovery-target-xid">, whichever one is
-        specified for this recovery.  This indicates whether transactions
-        having exactly the target commit time or ID, respectively, will
-        be included in the recovery.  Default is <literal>true</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="recovery-target-timeline"
-                   xreflabel="recovery_target_timeline">
-      <term><varname>recovery_target_timeline</varname>
-        (<type>string</type>)
-      </term>
-      <indexterm>
-        <primary><varname>recovery_target_timeline</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies recovering into a particular timeline.  The default is
-        to recover along the same timeline that was current when the
-        base backup was taken. Setting this to <literal>latest</> recovers
-        to the latest timeline found in the archive, which is useful in
-        a standby server. Other than that you only need to set this parameter
-        in complex re-recovery situations, where you need to return to
-        a state that itself was reached after a point-in-time recovery.
-        See <xref linkend="backup-timelines"> for discussion.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry id="pause-at-recovery-target"
-                   xreflabel="pause_at_recovery_target">
-      <term><varname>pause_at_recovery_target</varname>
-        (<type>boolean</type>)
-      </term>
-      <indexterm>
-        <primary><varname>pause_at_recovery_target</> recovery parameter</primary>
-      </indexterm>
-      <listitem>
-       <para>
-        Specifies whether recovery should pause when the recovery target
-        is reached. The default is true.
-        This is intended to allow queries to be executed against the
-        database to check if this recovery target is the most desirable
-        point for recovery. The paused state can be resumed by using
-        <function>pg_xlog_replay_resume()</> (See
-        <xref linkend="functions-recovery-control-table">), which then
-        causes recovery to end. If this recovery target is not the
-        desired stopping point, then shutdown the server, change the
-        recovery target settings to a later target and restart to
-        continue recovery.
-       </para>
-<!## PG>
-       <!-- XC does not support hot-standby at present -->
-       <para>
-        This setting has no effect if <xref linkend="guc-hot-standby"> is not
-        enabled, or if no recovery target is set.
-       </para>
-<!## end>
-      </listitem>
-     </varlistentry>
-
-     </variablelist>
-   </sect1>
-
-  <sect1 id="standby-settings">
-
-    <title>Standby Server Settings</title>
-
-&common;
-     <variablelist>
-
-       <varlistentry id="standby-mode" xreflabel="standby_mode">
-        <term><varname>standby_mode</varname> (<type>boolean</type>)</term>
-        <indexterm>
-          <primary><varname>standby_mode</> recovery parameter</primary>
-        </indexterm>
-        <listitem>
-         <para>
-          Specifies whether to start the <productname>PostgreSQL</> server as
-          a standby. If this parameter is <literal>on</>, the server will
-          not stop recovery when the end of archived WAL is reached, but
-          will keep trying to continue recovery by fetching new WAL segments
-          using <varname>restore_command</>
-          and/or by connecting to the primary server as specified by the
-          <varname>primary_conninfo</> setting.
-         </para>
-        </listitem>
-       </varlistentry>
-       <varlistentry id="primary-conninfo" xreflabel="primary_conninfo">
-        <term><varname>primary_conninfo</varname> (<type>string</type>)</term>
-        <indexterm>
-          <primary><varname>primary_conninfo</> recovery parameter</primary>
-        </indexterm>
-        <listitem>
-         <para>
-          Specifies a connection string to be used for the standby server
-          to connect with the primary. This string is in the format
-          accepted by the libpq <function>PQconnectdb</function> function,
-          described in <xref linkend="libpq-connect">. If any option is
-          unspecified in this string, then the corresponding environment
-          variable (see <xref linkend="libpq-envars">) is checked. If the
-          environment variable is not set either, then
-          defaults are used.
-         </para>
-
-         <para>
-          The connection string should specify the host name (or address)
-          of the primary server, as well as the port number if it is not
-          the same as the standby server's default.
-          Also specify a user name corresponding to a role that has the
-          <literal>SUPERUSER</> and <literal>LOGIN</> privileges on the
-          primary (see
-          <xref linkend="streaming-replication-authentication">).
-          A password needs to be provided too, if the primary demands password
-          authentication.  It can be provided in the
-          <varname>primary_conninfo</varname> string, or in a separate
-          <filename>~/.pgpass</> file on the standby server (use
-          <literal>replication</> as the database name).
-          Do not specify a database name in the
-          <varname>primary_conninfo</varname> string.
-         </para>
-
-         <para>
-          This setting has no effect if <varname>standby_mode</> is <literal>off</>.
-         </para>
-        </listitem>
-       </varlistentry>
-       <varlistentry id="trigger-file" xreflabel="trigger_file">
-        <term><varname>trigger_file</varname> (<type>string</type>)</term>
-        <indexterm>
-          <primary><varname>trigger_file</> recovery parameter</primary>
-        </indexterm>
-        <listitem>
-         <para>
-          Specifies a trigger file whose presence ends recovery in the
-          standby.  Even if this value is not set, you can still promote
-          the standby using <command>pg_ctl promote</>.
-          This setting has no effect if <varname>standby_mode</> is <literal>off</>.
-         </para>
-        </listitem>
-       </varlistentry>
-
-     </variablelist>
-   </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/ref/abort.sgmlin b/doc-xc/src/sgml/ref/abort.sgmlin
deleted file mode 100644
index 6996f62af7..0000000000
--- a/doc-xc/src/sgml/ref/abort.sgmlin
+++ /dev/null
@@ -1,111 +0,0 @@
-<!--
-doc/src/sgml/ref/abort.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ABORT">
- <refmeta>
-  <refentrytitle>ABORT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ABORT</refname>
-  <refpurpose>abort the current transaction</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-abort">
-  <primary>ABORT</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ABORT [ WORK | TRANSACTION ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ABORT</command> rolls back the current transaction and causes
-   all the updates made by the transaction to be discarded.
-   This command is identical
-   in behavior to the standard <acronym>SQL</acronym> command
-   <xref linkend="SQL-ROLLBACK">,
-   and is present only for historical reasons.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>WORK</literal></term>
-    <term><literal>TRANSACTION</literal></term>
-    <listitem>
-     <para>
-      Optional key words. They have no effect.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-COMMIT"> to
-   successfully terminate a transaction.
-  </para>
-
-  <para>
-   Issuing <command>ABORT</> when not inside a transaction does
-   no harm, but it will provoke a warning message.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To abort all changes:
-<programlisting>
-ABORT;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-<!## PG>
-   This command is a <productname>PostgreSQL</productname> extension
-<!## end>
-<!## XC>
-   This command is a <productname>Postgres-XC</productname> extension
-<!## end>
-<!## XL>
-   This command is a <productname>Postgres-XL</productname> extension
-<!## end>
-   present for historical reasons. <command>ROLLBACK</command> is the
-   equivalent standard SQL command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-begin"></member>
-   <member><xref linkend="sql-commit"></member>
-   <member><xref linkend="sql-rollback"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/allfiles.sgmlin b/doc-xc/src/sgml/ref/allfiles.sgmlin
deleted file mode 100644
index cefefc5fef..0000000000
--- a/doc-xc/src/sgml/ref/allfiles.sgmlin
+++ /dev/null
@@ -1,243 +0,0 @@
-<!--
-doc/src/sgml/ref/allfiles.sgml
-PostgreSQL documentation
-Complete list of usable sgml source files in this directory.
--->
-
-<!-- SQL commands -->
-<!ENTITY abort              SYSTEM "abort.sgml">
-<!ENTITY alterAggregate     SYSTEM "alter_aggregate.sgml">
-<!ENTITY alterCollation     SYSTEM "alter_collation.sgml">
-<!ENTITY alterConversion    SYSTEM "alter_conversion.sgml">
-<!ENTITY alterDatabase      SYSTEM "alter_database.sgml">
-<!ENTITY alterDefaultPrivileges SYSTEM "alter_default_privileges.sgml">
-<!ENTITY alterDomain        SYSTEM "alter_domain.sgml">
-<!ENTITY alterExtension     SYSTEM "alter_extension.sgml">
-<!ENTITY alterForeignDataWrapper SYSTEM "alter_foreign_data_wrapper.sgml">
-<!ENTITY alterForeignTable  SYSTEM "alter_foreign_table.sgml">
-<!ENTITY alterFunction      SYSTEM "alter_function.sgml">
-<!ENTITY alterGroup         SYSTEM "alter_group.sgml">
-<!ENTITY alterIndex         SYSTEM "alter_index.sgml">
-<!ENTITY alterLanguage      SYSTEM "alter_language.sgml">
-<!ENTITY alterLargeObject   SYSTEM "alter_large_object.sgml">
-<!## XC>
-<!entity alterNode          SYSTEM "alter_node.sgml">
-<!## end>
-<!## XL>
-<!entity alterNode          SYSTEM "alter_node.sgml">
-<!## end>
-<!ENTITY alterOperator      SYSTEM "alter_operator.sgml">
-<!ENTITY alterOperatorClass SYSTEM "alter_opclass.sgml">
-<!ENTITY alterOperatorFamily SYSTEM "alter_opfamily.sgml">
-<!ENTITY alterRole          SYSTEM "alter_role.sgml">
-<!ENTITY alterSchema        SYSTEM "alter_schema.sgml">
-<!ENTITY alterServer        SYSTEM "alter_server.sgml">
-<!ENTITY alterSequence      SYSTEM "alter_sequence.sgml">
-<!ENTITY alterTable         SYSTEM "alter_table.sgml">
-<!ENTITY alterTableSpace    SYSTEM "alter_tablespace.sgml">
-<!ENTITY alterTSConfig      SYSTEM "alter_tsconfig.sgml">
-<!ENTITY alterTSDictionary  SYSTEM "alter_tsdictionary.sgml">
-<!ENTITY alterTSParser      SYSTEM "alter_tsparser.sgml">
-<!ENTITY alterTSTemplate    SYSTEM "alter_tstemplate.sgml">
-<!ENTITY alterTrigger       SYSTEM "alter_trigger.sgml">
-<!ENTITY alterType          SYSTEM "alter_type.sgml">
-<!ENTITY alterUser          SYSTEM "alter_user.sgml">
-<!ENTITY alterUserMapping   SYSTEM "alter_user_mapping.sgml">
-<!ENTITY alterView          SYSTEM "alter_view.sgml">
-<!ENTITY analyze            SYSTEM "analyze.sgml">
-<!ENTITY begin              SYSTEM "begin.sgml">
-<!## XC>
-<!entity cleanConnection    system "clean_connection.sgml">
-<!## end>
-<!## XL>
-<!entity cleanConnection    system "clean_connection.sgml">
-<!## end>
-<!ENTITY checkpoint         SYSTEM "checkpoint.sgml">
-<!ENTITY close              SYSTEM "close.sgml">
-<!ENTITY cluster            SYSTEM "cluster.sgml">
-<!ENTITY commentOn          SYSTEM "comment.sgml">
-<!ENTITY commit             SYSTEM "commit.sgml">
-<!ENTITY commitPrepared     SYSTEM "commit_prepared.sgml">
-<!ENTITY copyTable          SYSTEM "copy.sgml">
-<!ENTITY createAggregate    SYSTEM "create_aggregate.sgml">
-<!## XC>
-<!entity createBarrier      system "create_barrier.sgml">
-<!## end>
-<!## XL>
-<!entity createBarrier      system "create_barrier.sgml">
-<!## end>
-<!ENTITY createCast         SYSTEM "create_cast.sgml">
-<!ENTITY createCollation    SYSTEM "create_collation.sgml">
-<!ENTITY createConversion   SYSTEM "create_conversion.sgml">
-<!ENTITY createDatabase     SYSTEM "create_database.sgml">
-<!ENTITY createDomain       SYSTEM "create_domain.sgml">
-<!ENTITY createExtension    SYSTEM "create_extension.sgml">
-<!ENTITY createForeignDataWrapper SYSTEM "create_foreign_data_wrapper.sgml">
-<!ENTITY createForeignTable SYSTEM "create_foreign_table.sgml">
-<!ENTITY createFunction     SYSTEM "create_function.sgml">
-<!ENTITY createGroup        SYSTEM "create_group.sgml">
-<!ENTITY createIndex        SYSTEM "create_index.sgml">
-<!ENTITY createLanguage     SYSTEM "create_language.sgml">
-<!## XC>
-<!entity createNode         SYSTEM "create_node.sgml">
-<!entity createNodeGroup    SYSTEM "create_nodegroup.sgml">
-<!## end>
-<!## XL>
-<!entity createNode         SYSTEM "create_node.sgml">
-<!entity createNodeGroup    SYSTEM "create_nodegroup.sgml">
-<!## end>
-<!ENTITY createOperator     SYSTEM "create_operator.sgml">
-<!ENTITY createOperatorClass SYSTEM "create_opclass.sgml">
-<!ENTITY createOperatorFamily SYSTEM "create_opfamily.sgml">
-<!ENTITY createRole         SYSTEM "create_role.sgml">
-<!ENTITY createRule         SYSTEM "create_rule.sgml">
-<!ENTITY createSchema       SYSTEM "create_schema.sgml">
-<!ENTITY createSequence     SYSTEM "create_sequence.sgml">
-<!ENTITY createServer       SYSTEM "create_server.sgml">
-<!ENTITY createTable        SYSTEM "create_table.sgml">
-<!ENTITY createTableAs      SYSTEM "create_table_as.sgml">
-<!ENTITY createTableSpace   SYSTEM "create_tablespace.sgml">
-<!ENTITY createTrigger      SYSTEM "create_trigger.sgml">
-<!ENTITY createTSConfig     SYSTEM "create_tsconfig.sgml">
-<!ENTITY createTSDictionary SYSTEM "create_tsdictionary.sgml">
-<!ENTITY createTSParser     SYSTEM "create_tsparser.sgml">
-<!ENTITY createTSTemplate   SYSTEM "create_tstemplate.sgml">
-<!ENTITY createType         SYSTEM "create_type.sgml">
-<!ENTITY createUser         SYSTEM "create_user.sgml">
-<!ENTITY createUserMapping  SYSTEM "create_user_mapping.sgml">
-<!ENTITY createView         SYSTEM "create_view.sgml">
-<!ENTITY deallocate         SYSTEM "deallocate.sgml">
-<!ENTITY declare            SYSTEM "declare.sgml">
-<!ENTITY delete             SYSTEM "delete.sgml">
-<!ENTITY discard            SYSTEM "discard.sgml">
-<!ENTITY do                 SYSTEM "do.sgml">
-<!ENTITY dropAggregate      SYSTEM "drop_aggregate.sgml">
-<!ENTITY dropCast           SYSTEM "drop_cast.sgml">
-<!ENTITY dropCollation      SYSTEM "drop_collation.sgml">
-<!ENTITY dropConversion     SYSTEM "drop_conversion.sgml">
-<!ENTITY dropDatabase       SYSTEM "drop_database.sgml">
-<!ENTITY dropDomain         SYSTEM "drop_domain.sgml">
-<!ENTITY dropExtension      SYSTEM "drop_extension.sgml">
-<!ENTITY dropForeignDataWrapper SYSTEM "drop_foreign_data_wrapper.sgml">
-<!ENTITY dropForeignTable   SYSTEM "drop_foreign_table.sgml">
-<!ENTITY dropFunction       SYSTEM "drop_function.sgml">
-<!ENTITY dropGroup          SYSTEM "drop_group.sgml">
-<!ENTITY dropIndex          SYSTEM "drop_index.sgml">
-<!ENTITY dropLanguage       SYSTEM "drop_language.sgml">
-<!## XC>
-<!entity dropNode           SYSTEM "drop_node.sgml">
-<!entity dropNodeGroup      SYSTEM "drop_nodegroup.sgml">
-<!## end>
-<!## XL>
-<!entity dropNode           SYSTEM "drop_node.sgml">
-<!entity dropNodeGroup      SYSTEM "drop_nodegroup.sgml">
-<!## end>
-<!ENTITY dropOperator       SYSTEM "drop_operator.sgml">
-<!ENTITY dropOperatorClass  SYSTEM "drop_opclass.sgml">
-<!ENTITY dropOperatorFamily  SYSTEM "drop_opfamily.sgml">
-<!ENTITY dropOwned          SYSTEM "drop_owned.sgml">
-<!ENTITY dropRole           SYSTEM "drop_role.sgml">
-<!ENTITY dropRule           SYSTEM "drop_rule.sgml">
-<!ENTITY dropSchema         SYSTEM "drop_schema.sgml">
-<!ENTITY dropSequence       SYSTEM "drop_sequence.sgml">
-<!ENTITY dropServer         SYSTEM "drop_server.sgml">
-<!ENTITY dropTable          SYSTEM "drop_table.sgml">
-<!ENTITY dropTableSpace     SYSTEM "drop_tablespace.sgml">
-<!ENTITY dropTrigger        SYSTEM "drop_trigger.sgml">
-<!ENTITY dropTSConfig       SYSTEM "drop_tsconfig.sgml">
-<!ENTITY dropTSDictionary   SYSTEM "drop_tsdictionary.sgml">
-<!ENTITY dropTSParser       SYSTEM "drop_tsparser.sgml">
-<!ENTITY dropTSTemplate     SYSTEM "drop_tstemplate.sgml">
-<!ENTITY dropType           SYSTEM "drop_type.sgml">
-<!ENTITY dropUser           SYSTEM "drop_user.sgml">
-<!ENTITY dropUserMapping    SYSTEM "drop_user_mapping.sgml">
-<!ENTITY dropView           SYSTEM "drop_view.sgml">
-<!ENTITY end                SYSTEM "end.sgml">
-<!ENTITY execute            SYSTEM "execute.sgml">
-<!## XC>
-<!entity executeDirect      system "execute_direct.sgml">
-<!## end>
-<!## XL>
-<!entity executeDirect      system "execute_direct.sgml">
-<!## end>
-<!ENTITY explain            SYSTEM "explain.sgml">
-<!ENTITY fetch              SYSTEM "fetch.sgml">
-<!ENTITY grant              SYSTEM "grant.sgml">
-<!ENTITY insert             SYSTEM "insert.sgml">
-<!ENTITY listen             SYSTEM "listen.sgml">
-<!ENTITY load               SYSTEM "load.sgml">
-<!ENTITY lock               SYSTEM "lock.sgml">
-<!ENTITY move               SYSTEM "move.sgml">
-<!ENTITY notify             SYSTEM "notify.sgml">
-<!## XL>
-<!ENTITY pauseCluster       SYSTEM "pause_cluster.sgml">
-<!## end>
-<!ENTITY prepare            SYSTEM "prepare.sgml">
-<!ENTITY prepareTransaction SYSTEM "prepare_transaction.sgml">
-<!ENTITY reassignOwned      SYSTEM "reassign_owned.sgml">
-<!ENTITY reindex            SYSTEM "reindex.sgml">
-<!ENTITY releaseSavepoint   SYSTEM "release_savepoint.sgml">
-<!ENTITY reset              SYSTEM "reset.sgml">
-<!ENTITY revoke             SYSTEM "revoke.sgml">
-<!ENTITY rollback           SYSTEM "rollback.sgml">
-<!ENTITY rollbackPrepared   SYSTEM "rollback_prepared.sgml">
-<!ENTITY rollbackTo         SYSTEM "rollback_to.sgml">
-<!ENTITY savepoint          SYSTEM "savepoint.sgml">
-<!ENTITY securityLabel      SYSTEM "security_label.sgml">
-<!ENTITY select             SYSTEM "select.sgml">
-<!ENTITY selectInto         SYSTEM "select_into.sgml">
-<!ENTITY set                SYSTEM "set.sgml">
-<!ENTITY setConstraints     SYSTEM "set_constraints.sgml">
-<!ENTITY setRole            SYSTEM "set_role.sgml">
-<!ENTITY setSessionAuth     SYSTEM "set_session_auth.sgml">
-<!ENTITY setTransaction     SYSTEM "set_transaction.sgml">
-<!ENTITY show               SYSTEM "show.sgml">
-<!ENTITY startTransaction   SYSTEM "start_transaction.sgml">
-<!ENTITY truncate           SYSTEM "truncate.sgml">
-<!ENTITY unlisten           SYSTEM "unlisten.sgml">
-<!## XL>
-<!ENTITY unpauseCluster     SYSTEM "unpause_cluster.sgml">
-<!## end>
-<!ENTITY update             SYSTEM "update.sgml">
-<!ENTITY vacuum             SYSTEM "vacuum.sgml">
-<!ENTITY values             SYSTEM "values.sgml">
-
-<!-- applications and utilities -->
-<!## XC>
-<!entity gtm                system "gtm.sgml">
-<!entity gtmPxy             system "gtm_proxy.sgml">
-<!entity gtmCtl             system "gtm_ctl.sgml">
-<!## end>
-<!## XL>
-<!entity gtm                system "gtm.sgml">
-<!entity gtmPxy             system "gtm_proxy.sgml">
-<!entity gtmCtl             system "gtm_ctl.sgml">
-<!## end>
-<!ENTITY clusterdb          SYSTEM "clusterdb.sgml">
-<!ENTITY createdb           SYSTEM "createdb.sgml">
-<!ENTITY createlang         SYSTEM "createlang.sgml">
-<!ENTITY createuser         SYSTEM "createuser.sgml">
-<!ENTITY dropdb             SYSTEM "dropdb.sgml">
-<!ENTITY droplang           SYSTEM "droplang.sgml">
-<!ENTITY dropuser           SYSTEM "dropuser.sgml">
-<!ENTITY ecpgRef            SYSTEM "ecpg-ref.sgml">
-<!ENTITY initdb             SYSTEM "initdb.sgml">
-<!## XC>
-<!ENTITY initgtm            SYSTEM "initgtm.sgml">
-<!## end>
-<!## XL>
-<!ENTITY initgtm            SYSTEM "initgtm.sgml">
-<!## end>
-<!ENTITY pgBasebackup       SYSTEM "pg_basebackup.sgml">
-<!ENTITY pgConfig           SYSTEM "pg_config-ref.sgml">
-<!ENTITY pgControldata      SYSTEM "pg_controldata.sgml">
-<!ENTITY pgCtl              SYSTEM "pg_ctl-ref.sgml">
-<!ENTITY pgDump             SYSTEM "pg_dump.sgml">
-<!ENTITY pgDumpall          SYSTEM "pg_dumpall.sgml">
-<!ENTITY pgResetxlog        SYSTEM "pg_resetxlog.sgml">
-<!ENTITY pgRestore          SYSTEM "pg_restore.sgml">
-<!ENTITY postgres           SYSTEM "postgres-ref.sgml">
-<!ENTITY postmaster         SYSTEM "postmaster.sgml">
-<!ENTITY psqlRef            SYSTEM "psql-ref.sgml">
-<!ENTITY reindexdb          SYSTEM "reindexdb.sgml">
-<!ENTITY vacuumdb           SYSTEM "vacuumdb.sgml">
diff --git a/doc-xc/src/sgml/ref/alter_aggregate.sgmlin b/doc-xc/src/sgml/ref/alter_aggregate.sgmlin
deleted file mode 100644
index 0e7ae160ff..0000000000
--- a/doc-xc/src/sgml/ref/alter_aggregate.sgmlin
+++ /dev/null
@@ -1,151 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_aggregate.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERAGGREGATE">
- <refmeta>
-  <refentrytitle>ALTER AGGREGATE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER AGGREGATE</refname>
-  <refpurpose>change the definition of an aggregate function</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alteraggregate">
-  <primary>ALTER AGGREGATE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER AGGREGATE <replaceable>name</replaceable> ( <replaceable>type</replaceable> [ , ... ] ) RENAME TO <replaceable>new_name</replaceable>
-ALTER AGGREGATE <replaceable>name</replaceable> ( <replaceable>type</replaceable> [ , ... ] ) OWNER TO <replaceable>new_owner</replaceable>
-ALTER AGGREGATE <replaceable>name</replaceable> ( <replaceable>type</replaceable> [ , ... ] ) SET SCHEMA <replaceable>new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER AGGREGATE</command> changes the definition of an
-   aggregate function.
-  </para>
-
-  <para>
-   You must own the aggregate function to use <command>ALTER AGGREGATE</>.
-   To change the schema of an aggregate function, you must also have
-   <literal>CREATE</literal> privilege on the new schema.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the aggregate function's schema.  (These restrictions enforce that altering
-   the owner doesn't do anything you couldn't do by dropping and recreating
-   the aggregate function.  However, a superuser can alter ownership of any
-   aggregate function anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-&common;
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing aggregate function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">type</replaceable></term>
-    <listitem>
-     <para>
-      An input data type on which the aggregate function operates.
-      To reference a zero-argument aggregate function, write <literal>*</>
-      in place of the list of input data types.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the aggregate function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the aggregate function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the aggregate function.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-&common;
-  <para>
-   To rename the aggregate function <literal>myavg</literal> for type
-   <type>integer</type> to <literal>my_average</literal>:
-<programlisting>
-ALTER AGGREGATE myavg(integer) RENAME TO my_average;
-</programlisting>
-  </para>
-
-  <para>
-   To change the owner of the aggregate function <literal>myavg</literal> for type
-   <type>integer</type> to <literal>joe</literal>:
-<programlisting>
-ALTER AGGREGATE myavg(integer) OWNER TO joe;
-</programlisting>
-  </para>
-
-  <para>
-   To move the aggregate function <literal>myavg</literal> for type
-   <type>integer</type> into schema <literal>myschema</literal>:
-<programlisting>
-ALTER AGGREGATE myavg(integer) SET SCHEMA myschema;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-&common;
-  <para>
-   There is no <command>ALTER AGGREGATE</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createaggregate"></member>
-   <member><xref linkend="sql-dropaggregate"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_collation.sgmlin b/doc-xc/src/sgml/ref/alter_collation.sgmlin
deleted file mode 100644
index 3aef656a0e..0000000000
--- a/doc-xc/src/sgml/ref/alter_collation.sgmlin
+++ /dev/null
@@ -1,128 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_collation.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERCOLLATION">
- <refmeta>
-  <refentrytitle>ALTER COLLATION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER COLLATION</refname>
-  <refpurpose>change the definition of a collation</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altercollation">
-  <primary>ALTER COLLATION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER COLLATION <replaceable>name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER COLLATION <replaceable>name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-ALTER COLLATION <replaceable>name</replaceable> SET SCHEMA <replaceable>new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>ALTER COLLATION</command> changes the definition of a
-   collation.
-  </para>
-
-  <para>
-   You must own the collation to use <command>ALTER COLLATION</>.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the collation's schema.  (These restrictions enforce that altering the
-   owner doesn't do anything you couldn't do by dropping and recreating the
-   collation. However, a superuser can alter ownership of any collation
-   anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing collation.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the collation.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the collation.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the collation.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To rename the collation <literal>de_DE</literal> to
-   <literal>german</literal>:
-<programlisting>
-ALTER COLLATION "de_DE" RENAME TO german;
-</programlisting>
-  </para>
-
-  <para>
-   To change the owner of the collation <literal>en_US</literal> to
-   <literal>joe</literal>:
-<programlisting>
-ALTER COLLATION "en_US" OWNER TO joe;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER COLLATION</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createcollation"></member>
-   <member><xref linkend="sql-dropcollation"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_conversion.sgmlin b/doc-xc/src/sgml/ref/alter_conversion.sgmlin
deleted file mode 100644
index 0d35a1bf14..0000000000
--- a/doc-xc/src/sgml/ref/alter_conversion.sgmlin
+++ /dev/null
@@ -1,130 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_conversion.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERCONVERSION">
- <refmeta>
-  <refentrytitle>ALTER CONVERSION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER CONVERSION</refname>
-  <refpurpose>change the definition of a conversion</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterconversion">
-  <primary>ALTER CONVERSION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER CONVERSION <replaceable>name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER CONVERSION <replaceable>name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-ALTER CONVERSION <replaceable>name</replaceable> SET SCHEMA <replaceable>new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER CONVERSION</command> changes the definition of a
-   conversion.
-  </para>
-
-  <para>
-   You must own the conversion to use <command>ALTER CONVERSION</>.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the conversion's schema.  (These restrictions enforce that altering the
-   owner doesn't do anything you couldn't do by dropping and recreating the
-   conversion. However, a superuser can alter ownership of any conversion
-   anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing conversion.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the conversion.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the conversion.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the conversion.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To rename the conversion <literal>iso_8859_1_to_utf8</literal> to
-   <literal>latin1_to_unicode</literal>:
-<programlisting>
-ALTER CONVERSION iso_8859_1_to_utf8 RENAME TO latin1_to_unicode;
-</programlisting>
-  </para>
-
-  <para>
-   To change the owner of the conversion <literal>iso_8859_1_to_utf8</literal> to
-   <literal>joe</literal>:
-<programlisting>
-ALTER CONVERSION iso_8859_1_to_utf8 OWNER TO joe;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER CONVERSION</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createconversion"></member>
-   <member><xref linkend="sql-dropconversion"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_database.sgmlin b/doc-xc/src/sgml/ref/alter_database.sgmlin
deleted file mode 100644
index 72f169642b..0000000000
--- a/doc-xc/src/sgml/ref/alter_database.sgmlin
+++ /dev/null
@@ -1,252 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_database.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERDATABASE">
- <refmeta>
-  <refentrytitle>ALTER DATABASE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER DATABASE</refname>
-  <refpurpose>change a database</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterdatabase">
-  <primary>ALTER DATABASE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replaceable class="PARAMETER">option</replaceable> [ ... ] ]
-
-<phrase>where <replaceable class="PARAMETER">option</replaceable> can be:</phrase>
-
-    CONNECTION LIMIT <replaceable class="PARAMETER">connlimit</replaceable>
-
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> SET TABLESPACE <replaceable class="PARAMETER">new_tablespace</replaceable>
-
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> SET <replaceable>configuration_parameter</replaceable> { TO | = } { <replaceable>value</replaceable> | DEFAULT }
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> SET <replaceable>configuration_parameter</replaceable> FROM CURRENT
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> RESET <replaceable>configuration_parameter</replaceable>
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> RESET ALL
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER DATABASE</command> changes the attributes
-   of a database.
-  </para>
-
-  <para>
-   The first form changes certain per-database settings.  (See below for
-   details.)  Only the database owner or a superuser can change these settings.
-  </para>
-
-  <para>
-   The second form changes the name of the database.  Only the database
-   owner or a superuser can rename a database; non-superuser owners must
-   also have the
-   <literal>CREATEDB</literal> privilege.  The current database cannot
-   be renamed.  (Connect to a different database if you need to do
-   that.)
-  </para>
-
-  <para>
-   The third form changes the owner of the database.
-   To alter the owner, you must own the database and also be a direct or
-   indirect member of the new owning role, and you must have the
-   <literal>CREATEDB</literal> privilege.
-   (Note that superusers have all these privileges automatically.)
-  </para>
-
-  <para>
-   The fourth form changes the default tablespace of the database.
-   Only the database owner or a superuser can do this; you must also have
-   create privilege for the new tablespace.
-   This command physically moves any tables or indexes in the database's old
-   default tablespace to the new tablespace.  Note that tables and indexes
-   in non-default tablespaces are not affected.
-  </para>
-
-  <para>
-   The remaining forms change the session default for a run-time
-<!## PG>
-   configuration variable for a <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   configuration variable for a <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   configuration variable for a <productname>Postgres-XL</productname>
-<!## end>
-   database. Whenever a new session is subsequently started in that
-   database, the specified value becomes the session default value.
-   The database-specific default overrides whatever setting is present
-   in <filename>postgresql.conf</> or has been received from the
-   <command>postgres</command> command line.  Only the database
-   owner or a superuser can change the session defaults for a
-   database.  Certain variables cannot be set this way, or can only be
-   set by a superuser.
-  </para>
-<!## XC>
-&xconly;
-   <para>
-    If there's any live connection to any of the template database in
-    Coordinator or Datanode, you will have an error message.  In this
-    case, you should clean these connections using <command>CLEAN
-    CONNECITON</> statement.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    If there are any live connections to any of the template databases in
-    one of the Coordinators or Datanodes, you will have an error message.  In this
-    case, you should clean these connections using <command>CLEAN
-    CONNECITON</> statement.
-   </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the database whose attributes are to be altered.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">connlimit</replaceable></term>
-      <listitem>
-       <para>
-        How many concurrent connections can be made
-        to this database.  -1 means no limit.
-       </para>
-      </listitem>
-     </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the database.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the database.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_tablespace</replaceable></term>
-    <listitem>
-     <para>
-      The new default tablespace of the database.
-     </para>
-    </listitem>
-   </varlistentry>
-
-     <varlistentry>
-      <term><replaceable>configuration_parameter</replaceable></term>
-      <term><replaceable>value</replaceable></term>
-      <listitem>
-       <para>
-        Set this database's session default for the specified configuration
-        parameter to the given value.  If
-        <replaceable>value</replaceable> is <literal>DEFAULT</literal>
-        or, equivalently, <literal>RESET</literal> is used, the
-        database-specific setting is removed, so the system-wide default
-        setting will be inherited in new sessions.  Use <literal>RESET
-        ALL</literal> to clear all database-specific settings.
-        <literal>SET FROM CURRENT</> saves the session's current value of
-        the parameter as the database-specific value.
-       </para>
-
-       <para>
-        See <xref linkend="sql-set"> and <xref linkend="runtime-config">
-        for more information about allowed parameter names
-        and values.
-       </para>
-      </listitem>
-     </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   It is also possible to tie a session default to a specific role
-   rather than to a database; see
-   <xref linkend="sql-alterrole">.
-   Role-specific settings override database-specific
-   ones if there is a conflict.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To disable index scans by default in the database
-   <literal>test</literal>:
-
-<programlisting>
-ALTER DATABASE test SET enable_indexscan TO off;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The <command>ALTER DATABASE</command> statement is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createdatabase"></member>
-   <member><xref linkend="sql-dropdatabase"></member>
-   <member><xref linkend="sql-set"></member>
-   <member><xref linkend="sql-createtablespace"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_default_privileges.sgmlin b/doc-xc/src/sgml/ref/alter_default_privileges.sgmlin
deleted file mode 100644
index 772c3a61ef..0000000000
--- a/doc-xc/src/sgml/ref/alter_default_privileges.sgmlin
+++ /dev/null
@@ -1,214 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_default_privileges.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERDEFAULTPRIVILEGES">
- <refmeta>
-  <refentrytitle>ALTER DEFAULT PRIVILEGES</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER DEFAULT PRIVILEGES</refname>
-  <refpurpose>define default access privileges</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterdefaultprivileges">
-  <primary>ALTER DEFAULT PRIVILEGES</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER DEFAULT PRIVILEGES
-    [ FOR { ROLE | USER } <replaceable>target_role</replaceable> [, ...] ]
-    [ IN SCHEMA <replaceable>schema_name</replaceable> [, ...] ]
-    <replaceable class="parameter">abbreviated_grant_or_revoke</replaceable>
-
-<phrase>where <replaceable class="parameter">abbreviated_grant_or_revoke</replaceable> is one of:</phrase>
-
-GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER }
-    [, ...] | ALL [ PRIVILEGES ] }
-    ON TABLES
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { { USAGE | SELECT | UPDATE }
-    [, ...] | ALL [ PRIVILEGES ] }
-    ON SEQUENCES
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { EXECUTE | ALL [ PRIVILEGES ] }
-    ON FUNCTIONS
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER }
-    [, ...] | ALL [ PRIVILEGES ] }
-    ON TABLES
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { { USAGE | SELECT | UPDATE }
-    [, ...] | ALL [ PRIVILEGES ] }
-    ON SEQUENCES
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { EXECUTE | ALL [ PRIVILEGES ] }
-    ON FUNCTIONS
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-alterdefaultprivileges-description">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER DEFAULT PRIVILEGES</> allows you to set the privileges
-   that will be applied to objects created in the future.  (It does not
-   affect privileges assigned to already-existing objects.)  Currently,
-   only the privileges for tables (including views and foreign tables),
-   sequences, and functions can be altered.
-  </para>
-
-  <para>
-   You can change default privileges only for objects that will be created by
-   yourself or by roles that you are a member of.  The privileges can be set
-   globally (i.e., for all objects created in the current database),
-   or just for objects created in specified schemas.  Default privileges
-   that are specified per-schema are added to whatever the global default
-   privileges are for the particular object type.
-  </para>
-
-  <para>
-   As explained under <xref linkend="sql-grant">,
-   the default privileges for any object type normally grant all grantable
-   permissions to the object owner, and may grant some privileges to
-   <literal>PUBLIC</> as well.  However, this behavior can be changed by
-   altering the global default privileges with
-   <command>ALTER DEFAULT PRIVILEGES</>.
-  </para>
-
- <refsect2>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable>target_role</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing role of which the current role is a member.
-      If <literal>FOR ROLE</> is omitted, the current role is assumed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>schema_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing schema.  Each <replaceable>target_role</>
-      must have <literal>CREATE</> privileges for each specified schema.
-      If <literal>IN SCHEMA</> is omitted, the global default privileges
-      are altered.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>role_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing role to grant or revoke privileges for.
-      This parameter, and all the other parameters in
-      <replaceable class="parameter">abbreviated_grant_or_revoke</>,
-      act as described under
-      <xref linkend="sql-grant"> or
-      <xref linkend="sql-revoke">,
-      except that one is setting permissions for a whole class of objects
-      rather than specific named objects.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect2>
- </refsect1>
-
- <refsect1 id="sql-alterdefaultprivileges-notes">
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="app-psql">'s <command>\ddp</command> command
-   to obtain information about existing assignments of default privileges.
-   The meaning of the privilege values is the same as explained for
-   <command>\dp</command> under
-   <xref linkend="sql-grant">.
-  </para>
-
-  <para>
-   If you wish to drop a role for which the default privileges have been
-   altered, it is necessary to reverse the changes in its default privileges
-   or use <command>DROP OWNED BY</> to get rid of the default privileges entry
-   for the role.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-alterdefaultprivileges-examples">
-  <title>Examples</title>
-
-  <para>
-   Grant SELECT privilege to everyone for all tables (and views) you
-   subsequently create in schema <literal>myschema</literal>, and allow
-   role <literal>webuser</> to INSERT into them too:
-
-<programlisting>
-ALTER DEFAULT PRIVILEGES IN SCHEMA myschema GRANT SELECT ON TABLES TO PUBLIC;
-ALTER DEFAULT PRIVILEGES IN SCHEMA myschema GRANT INSERT ON TABLES TO webuser;
-</programlisting>
-  </para>
-
-  <para>
-   Undo the above, so that subsequently-created tables won't have any
-   more permissions than normal:
-
-<programlisting>
-ALTER DEFAULT PRIVILEGES IN SCHEMA myschema REVOKE SELECT ON TABLES FROM PUBLIC;
-ALTER DEFAULT PRIVILEGES IN SCHEMA myschema REVOKE INSERT ON TABLES FROM webuser;
-</programlisting>
-  </para>
-
-  <para>
-   Remove the public EXECUTE permission that is normally granted on functions,
-   for all functions subsequently created by role <literal>admin</>:
-
-<programlisting>
-ALTER DEFAULT PRIVILEGES FOR ROLE admin REVOKE EXECUTE ON FUNCTIONS FROM PUBLIC;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER DEFAULT PRIVILEGES</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-grant"></member>
-   <member><xref linkend="sql-revoke"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_domain.sgmlin b/doc-xc/src/sgml/ref/alter_domain.sgmlin
deleted file mode 100644
index 284ba8f771..0000000000
--- a/doc-xc/src/sgml/ref/alter_domain.sgmlin
+++ /dev/null
@@ -1,279 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_domain.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERDOMAIN">
- <refmeta>
-  <refentrytitle>ALTER DOMAIN</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER DOMAIN</refname>
-  <refpurpose>
-   change the definition of a domain
-  </refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterdomain">
-  <primary>ALTER DOMAIN</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
-    { SET DEFAULT <replaceable class="PARAMETER">expression</replaceable> | DROP DEFAULT }
-ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
-    { SET | DROP } NOT NULL
-ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
-    ADD <replaceable class="PARAMETER">domain_constraint</replaceable>
-ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
-    DROP CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> [ RESTRICT | CASCADE ]
-ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
-    OWNER TO <replaceable class="PARAMETER">new_owner</replaceable>
-ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
-    SET SCHEMA <replaceable class="PARAMETER">new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common
-
-  <para>
-   <command>ALTER DOMAIN</command> changes the definition of an existing domain.
-   There are several sub-forms:
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term>SET/DROP DEFAULT</term>
-    <listitem>
-     <para>
-      These forms set or remove the default value for a domain. Note
-      that defaults only apply to subsequent <command>INSERT</command>
-      commands; they do not affect rows already in a table using the domain.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>SET/DROP NOT NULL</term>
-    <listitem>
-     <para>
-      These forms change whether a domain is marked to allow NULL
-      values or to reject NULL values.  You can only <literal>SET NOT NULL</>
-      when the columns using the domain contain no null values.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>ADD <replaceable class="PARAMETER">domain_constraint</replaceable></term>
-    <listitem>
-     <para>
-      This form adds a new constraint to a domain using the same syntax as
-      <xref linkend="SQL-CREATEDOMAIN">.
-      This will only succeed if all columns using the domain satisfy the
-      new constraint.
-     </para>
-&xc-constraint;
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>DROP CONSTRAINT</term>
-    <listitem>
-     <para>
-      This form drops constraints on a domain.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>OWNER</term>
-    <listitem>
-     <para>
-      This form changes the owner of the domain to the specified user.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>SET SCHEMA</term>
-    <listitem>
-     <para>
-      This form changes the schema of the domain.  Any constraints
-      associated with the domain are moved into the new schema as well.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   You must own the domain to use <command>ALTER DOMAIN</>.
-   To change the schema of a domain, you must also have
-   <literal>CREATE</literal> privilege on the new schema.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the domain's schema.  (These restrictions enforce that altering the owner
-   doesn't do anything you couldn't do by dropping and recreating the domain.
-   However, a superuser can alter ownership of any domain anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-        The name (possibly schema-qualified) of an existing domain to
-        alter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">domain_constraint</replaceable></term>
-      <listitem>
-       <para>
-        New domain constraint for the domain.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">constraint_name</replaceable></term>
-      <listitem>
-       <para>
-        Name of an existing constraint to drop.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CASCADE</literal></term>
-      <listitem>
-       <para>
-        Automatically drop objects that depend on the constraint.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>RESTRICT</literal></term>
-      <listitem>
-       <para>
-        Refuse to drop the constraint if there are any dependent
-        objects. This is the default behavior.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_owner</replaceable></term>
-      <listitem>
-       <para>
-        The user name of the new owner of the domain.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_schema</replaceable></term>
-      <listitem>
-       <para>
-        The new schema for the domain.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Currently, <command>ALTER DOMAIN ADD CONSTRAINT</> and
-   <command>ALTER DOMAIN SET NOT NULL</> will fail if the named domain or
-   any derived domain is used within a composite-type column of any
-   table in the database.  They should eventually be improved to be
-   able to verify the new constraint for such nested columns.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To add a <literal>NOT NULL</literal> constraint to a domain:
-<programlisting>
-ALTER DOMAIN zipcode SET NOT NULL;
-</programlisting>
-   To remove a <literal>NOT NULL</literal> constraint from a domain:
-<programlisting>
-ALTER DOMAIN zipcode DROP NOT NULL;
-</programlisting>
-  </para>
-
-  <para>
-   To add a check constraint to a domain:
-<programlisting>
-ALTER DOMAIN zipcode ADD CONSTRAINT zipchk CHECK (char_length(VALUE) = 5);
-</programlisting>
-  </para>
-
-  <para>
-   To remove a check constraint from a domain:
-<programlisting>
-ALTER DOMAIN zipcode DROP CONSTRAINT zipchk;
-</programlisting>
-  </para>
-
-  <para>
-   To move the domain into a different schema:
-<programlisting>
-ALTER DOMAIN zipcode SET SCHEMA customers;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-ALTERDOMAIN-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   <command>ALTER DOMAIN</command> conforms to the <acronym>SQL</acronym>
-   standard,
-   except for the <literal>OWNER</> and <literal>SET SCHEMA</> variants,
-<!## PG>
-   which are <productname>PostgreSQL</productname> extensions.
-<!## end>
-<!## XC>
-   which are <productname>Postgres-XC</productname> extensions.
-<!## end>
-<!## XL>
-   which are <productname>Postgres-XL</productname> extensions.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-ALTERDOMAIN-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createdomain"></member>
-   <member><xref linkend="sql-dropdomain"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_extension.sgmlin b/doc-xc/src/sgml/ref/alter_extension.sgmlin
deleted file mode 100644
index e8c9608666..0000000000
--- a/doc-xc/src/sgml/ref/alter_extension.sgmlin
+++ /dev/null
@@ -1,291 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_extension.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTEREXTENSION">
- <refmeta>
-  <refentrytitle>ALTER EXTENSION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER EXTENSION</refname>
-  <refpurpose>
-   change the definition of an extension
-  </refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterextension">
-  <primary>ALTER EXTENSION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER EXTENSION <replaceable class="PARAMETER">extension_name</replaceable> UPDATE [ TO <replaceable class="PARAMETER">new_version</replaceable> ]
-ALTER EXTENSION <replaceable class="PARAMETER">extension_name</replaceable> SET SCHEMA <replaceable class="PARAMETER">new_schema</replaceable>
-ALTER EXTENSION <replaceable class="PARAMETER">extension_name</replaceable> ADD <replaceable class="PARAMETER">member_object</replaceable>
-ALTER EXTENSION <replaceable class="PARAMETER">extension_name</replaceable> DROP <replaceable class="PARAMETER">member_object</replaceable>
-
-<phrase>where <replaceable class="PARAMETER">member_object</replaceable> is:</phrase>
-
-  AGGREGATE <replaceable class="PARAMETER">agg_name</replaceable> (<replaceable class="PARAMETER">agg_type</replaceable> [, ...] ) |
-  CAST (<replaceable>source_type</replaceable> AS <replaceable>target_type</replaceable>) |
-  COLLATION <replaceable class="PARAMETER">object_name</replaceable> |
-  CONVERSION <replaceable class="PARAMETER">object_name</replaceable> |
-  DOMAIN <replaceable class="PARAMETER">object_name</replaceable> |
-  FOREIGN DATA WRAPPER <replaceable class="PARAMETER">object_name</replaceable> |
-  FOREIGN TABLE <replaceable class="PARAMETER">object_name</replaceable> |
-  FUNCTION <replaceable class="PARAMETER">function_name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">argname</replaceable> ] <replaceable class="parameter">argtype</replaceable> [, ...] ] ) |
-  OPERATOR <replaceable class="PARAMETER">operator_name</replaceable> (<replaceable class="PARAMETER">left_type</replaceable>, <replaceable class="PARAMETER">right_type</replaceable>) |
-  OPERATOR CLASS <replaceable class="PARAMETER">object_name</replaceable> USING <replaceable class="parameter">index_method</replaceable> |
-  OPERATOR FAMILY <replaceable class="PARAMETER">object_name</replaceable> USING <replaceable class="parameter">index_method</replaceable> |
-  [ PROCEDURAL ] LANGUAGE <replaceable class="PARAMETER">object_name</replaceable> |
-  SCHEMA <replaceable class="PARAMETER">object_name</replaceable> |
-  SEQUENCE <replaceable class="PARAMETER">object_name</replaceable> |
-  SERVER <replaceable class="PARAMETER">object_name</replaceable> |
-  TABLE <replaceable class="PARAMETER">object_name</replaceable> |
-  TEXT SEARCH CONFIGURATION <replaceable class="PARAMETER">object_name</replaceable> |
-  TEXT SEARCH DICTIONARY <replaceable class="PARAMETER">object_name</replaceable> |
-  TEXT SEARCH PARSER <replaceable class="PARAMETER">object_name</replaceable> |
-  TEXT SEARCH TEMPLATE <replaceable class="PARAMETER">object_name</replaceable> |
-  TYPE <replaceable class="PARAMETER">object_name</replaceable> |
-  VIEW <replaceable class="PARAMETER">object_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>ALTER EXTENSION</command> changes the definition of an installed
-   extension.  There are several subforms:
-
-   <variablelist>
-   <varlistentry>
-    <term><literal>UPDATE</literal></term>
-    <listitem>
-     <para>
-      This form updates the extension to a newer version.  The extension
-      must supply a suitable update script (or series of scripts) that can
-      modify the currently-installed version into the requested version.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET SCHEMA</literal></term>
-    <listitem>
-     <para>
-      This form moves the extension's objects into another schema. The
-      extension has to be <firstterm>relocatable</> for this command to
-      succeed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ADD <replaceable class="PARAMETER">member_object</replaceable></literal></term>
-    <listitem>
-     <para>
-      This form adds an existing object to the extension.  This is mainly
-      useful in extension update scripts.  The object will subsequently
-      be treated as a member of the extension; notably, it can only be
-      dropped by dropping the extension.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DROP <replaceable class="PARAMETER">member_object</replaceable></literal></term>
-    <listitem>
-     <para>
-      This form removes a member object from the extension.  This is mainly
-      useful in extension update scripts.  The object is not dropped, only
-      disassociated from the extension.
-     </para>
-    </listitem>
-   </varlistentry>
-   </variablelist>
-
-   See <xref linkend="extend-extensions"> for more information about these
-   operations.
-  </para>
-
-  <para>
-   You must own the extension to use <command>ALTER EXTENSION</command>.
-   The <literal>ADD</>/<literal>DROP</> forms require ownership of the
-   added/dropped object as well.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><replaceable class="PARAMETER">extension_name</replaceable></term>
-     <listitem>
-      <para>
-       The name of an installed extension.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="PARAMETER">new_version</replaceable></term>
-     <listitem>
-      <para>
-       The desired new version of the extension.  This can be written as
-       either an identifier or a string literal.  If not specified,
-       <command>ALTER EXTENSION UPDATE</> attempts to update to whatever is
-       shown as the default version in the extension's control file.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="PARAMETER">new_schema</replaceable></term>
-     <listitem>
-      <para>
-       The new schema for the extension.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">object_name</replaceable></term>
-     <term><replaceable class="parameter">agg_name</replaceable></term>
-     <term><replaceable class="parameter">function_name</replaceable></term>
-     <term><replaceable class="parameter">operator_name</replaceable></term>
-     <listitem>
-      <para>
-       The name of an object to be added to or removed from the extension.
-       Names of tables,
-       aggregates, domains, foreign tables, functions, operators,
-       operator classes, operator families, sequences, text search objects,
-       types, and views can be schema-qualified.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">agg_type</replaceable></term>
-     <listitem>
-      <para>
-       An input data type on which the aggregate function operates.
-       To reference a zero-argument aggregate function, write <literal>*</>
-       in place of the list of input data types.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>source_type</replaceable></term>
-     <listitem>
-      <para>
-       The name of the source data type of the cast.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>target_type</replaceable></term>
-     <listitem>
-      <para>
-       The name of the target data type of the cast.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">argmode</replaceable></term>
-
-     <listitem>
-      <para>
-       The mode of a function argument: <literal>IN</>, <literal>OUT</>,
-       <literal>INOUT</>, or <literal>VARIADIC</>.
-       If omitted, the default is <literal>IN</>.
-       Note that <command>ALTER EXTENSION</command> does not actually pay
-       any attention to <literal>OUT</> arguments, since only the input
-       arguments are needed to determine the function's identity.
-       So it is sufficient to list the <literal>IN</>, <literal>INOUT</>,
-       and <literal>VARIADIC</> arguments.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">argname</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of a function argument.
-       Note that <command>ALTER EXTENSION</command> does not actually pay
-       any attention to argument names, since only the argument data
-       types are needed to determine the function's identity.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">argtype</replaceable></term>
-
-     <listitem>
-      <para>
-       The data type(s) of the function's arguments (optionally
-       schema-qualified), if any.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>PROCEDURAL</literal></term>
-
-     <listitem>
-      <para>
-       This is a noise word.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To update the <literal>hstore</literal> extension to version 2.0:
-<programlisting>
-ALTER EXTENSION hstore UPDATE TO '2.0';
-</programlisting>
-  </para>
-
-  <para>
-   To change the schema of the <literal>hstore</literal> extension
-   to <literal>utils</literal>:
-<programlisting>
-ALTER EXTENSION hstore SET SCHEMA utils;
-</programlisting>
-  </para>
-
-  <para>
-   To add an existing function to the <literal>hstore</literal> extension:
-<programlisting>
-ALTER EXTENSION hstore ADD FUNCTION populate_record(anyelement, hstore);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-ALTEREXTENSION-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createextension"></member>
-   <member><xref linkend="sql-dropextension"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_foreign_data_wrapper.sgmlin b/doc-xc/src/sgml/ref/alter_foreign_data_wrapper.sgmlin
deleted file mode 100644
index 1eb9e8ef39..0000000000
--- a/doc-xc/src/sgml/ref/alter_foreign_data_wrapper.sgmlin
+++ /dev/null
@@ -1,187 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_foreign_data_wrapper.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERFOREIGNDATAWRAPPER">
- <refmeta>
-  <refentrytitle>ALTER FOREIGN DATA WRAPPER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER FOREIGN DATA WRAPPER</refname>
-  <refpurpose>change the definition of a foreign-data wrapper</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterforeigndatawrapper">
-  <primary>ALTER FOREIGN DATA WRAPPER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER FOREIGN DATA WRAPPER <replaceable class="parameter">name</replaceable>
-    [ HANDLER <replaceable class="parameter">handler_function</replaceable> | NO HANDLER ]
-    [ VALIDATOR <replaceable class="parameter">validator_function</replaceable> | NO VALIDATOR ]
-    [ OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">value</replaceable>'] [, ... ]) ]
-ALTER FOREIGN DATA WRAPPER <replaceable class="parameter">name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-<!## XC>
-&xconly;
-  <para>
-   <command>FOREIGN DATA WRAPPER</> has not been supported
-   by <productname>Postgres-XC</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>FOREIGN DATA WRAPPER</> is not yet supported
-   in <productname>Postgres-XL</>.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-&pgonly;
-
-  <para>
-   <command>ALTER FOREIGN DATA WRAPPER</command> changes the
-   definition of a foreign-data wrapper.  The first form of the
-   command changes the support functions or the generic options of the
-   foreign-data wrapper (at least one clause is required).  The second
-   form changes the owner of the foreign-data wrapper.
-  </para>
-
-  <para>
-   Only superusers can alter foreign-data wrappers.  Additionally,
-   only superusers can own foreign-data wrappers.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing foreign-data wrapper.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>HANDLER <replaceable class="parameter">handler_function</replaceable></literal></term>
-    <listitem>
-     <para>
-      Specifies a new handler function for the foreign-data wrapper.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NO HANDLER</literal></term>
-    <listitem>
-     <para>
-      This is used to specify that the foreign-data wrapper should no
-      longer have a handler function.
-     </para>
-     <para>
-      Note that foreign tables that use a foreign-data wrapper with no
-      handler cannot be accessed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>VALIDATOR <replaceable class="parameter">validator_function</replaceable></literal></term>
-    <listitem>
-     <para>
-      Specifies a new validator function for the foreign-data wrapper.
-     </para>
-
-     <para>
-      Note that it is possible that after changing the validator the
-      options to the foreign-data wrapper, servers, and user mappings
-      have become invalid.   It is up to the user to make sure that
-      these options are correct before using the foreign-data
-      wrapper.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NO VALIDATOR</literal></term>
-    <listitem>
-     <para>
-      This is used to specify that the foreign-data wrapper should no
-      longer have a validator function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">value</replaceable>'] [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      Change options for the foreign-data
-      wrapper.  <literal>ADD</>, <literal>SET</>, and <literal>DROP</>
-      specify the action to be performed.  <literal>ADD</> is assumed
-      if no operation is explicitly specified.  Option names must be
-      unique; names and values are also validated using the foreign
-      data wrapper's validator function, if any.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Change a foreign-data wrapper <literal>dbi</>, add
-   option <literal>foo</>, drop <literal>bar</>:
-<programlisting>
-ALTER FOREIGN DATA WRAPPER dbi OPTIONS (ADD foo '1', DROP 'bar');
-</programlisting>
-  </para>
-
-  <para>
-   Change the foreign-data wrapper <literal>dbi</> validator
-   to <literal>bob.myvalidator</>:
-<programlisting>
-ALTER FOREIGN DATA WRAPPER dbi VALIDATOR bob.myvalidator;
-</programlisting>
-  </para>
-
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>ALTER FOREIGN DATA WRAPPER</command> conforms to ISO/IEC
-   9075-9 (SQL/MED), except that the <literal>HANDLER</literal>,
-   <literal>VALIDATOR</> and <literal>OWNER TO</> clauses are extensions.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createforeigndatawrapper"></member>
-   <member><xref linkend="sql-dropforeigndatawrapper"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_foreign_table.sgmlin b/doc-xc/src/sgml/ref/alter_foreign_table.sgmlin
deleted file mode 100644
index c2ebdac847..0000000000
--- a/doc-xc/src/sgml/ref/alter_foreign_table.sgmlin
+++ /dev/null
@@ -1,315 +0,0 @@
-<!--
-doc/src/sgml/rel/alter_foreign_table.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERFOREIGNTABLE">
- <refmeta>
-  <refentrytitle>ALTER FOREIGN TABLE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER FOREIGN TABLE</refname>
-  <refpurpose>change the definition of a foreign table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterforeigntable">
-  <primary>ALTER FOREIGN TABLE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER FOREIGN TABLE <replaceable class="PARAMETER">name</replaceable>
-    <replaceable class="PARAMETER">action</replaceable> [, ... ]
-ALTER FOREIGN TABLE <replaceable class="PARAMETER">name</replaceable>
-    RENAME [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> TO <replaceable class="PARAMETER">new_column</replaceable>
-ALTER FOREIGN TABLE <replaceable class="PARAMETER">name</replaceable>
-    RENAME TO <replaceable class="PARAMETER">new_name</replaceable>
-ALTER FOREIGN TABLE <replaceable class="PARAMETER">name</replaceable>
-    SET SCHEMA <replaceable class="PARAMETER">new_schema</replaceable>
-
-<phrase>where <replaceable class="PARAMETER">action</replaceable> is one of:</phrase>
-
-    ADD [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> <replaceable class="PARAMETER">type</replaceable>
-    DROP [ COLUMN ] [ IF EXISTS ] <replaceable class="PARAMETER">column</replaceable> [ RESTRICT | CASCADE ]
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> [ SET DATA ] TYPE <replaceable class="PARAMETER">type</replaceable>
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> { SET | DROP } NOT NULL
-    OWNER TO <replaceable class="PARAMETER">new_owner</replaceable>
-    OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">value</replaceable>'] [, ... ])
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>ALTER FOREIGN TABLE</command> changes the definition of an
-   existing foreign table.  There are several subforms:
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>ADD COLUMN</literal></term>
-    <listitem>
-     <para>
-      This form adds a new column to the foreign table, using the same syntax as
-      <xref linkend="SQL-CREATEFOREIGNTABLE">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DROP COLUMN [ IF EXISTS ]</literal></term>
-    <listitem>
-     <para>
-      This form drops a column from a foreign table.
-      You will need to say <literal>CASCADE</> if
-      anything outside the table depends on the column; for example,
-      views.
-      If <literal>IF EXISTS</literal> is specified and the column
-      does not exist, no error is thrown. In this case a notice
-      is issued instead.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET DATA TYPE</literal></term>
-    <listitem>
-     <para>
-      This form changes the type of a column of a foreign table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET</literal>/<literal>DROP NOT NULL</literal></term>
-    <listitem>
-     <para>
-      Mark a column as allowing, or not allowing, null values.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OWNER</literal></term>
-    <listitem>
-     <para>
-      This form changes the owner of the foreign table to the
-      specified user.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RENAME</literal></term>
-    <listitem>
-     <para>
-      The <literal>RENAME</literal> forms change the name of a foreign table
-      or the name of an individual column in a foreign table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET SCHEMA</literal></term>
-    <listitem>
-     <para>
-      This form moves the foreign table into another schema.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">value</replaceable>'] [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      Change options for the foreign table or the column of the foreign table.
-      <literal>ADD</>, <literal>SET</>, and <literal>DROP</>
-      specify the action to be performed.  <literal>ADD</> is assumed
-      if no operation is explicitly specified.  Option names must be
-      unique; names and values are also validated using the foreign
-      data wrapper library.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-  </para>
-
-  <para>
-   All the actions except <literal>RENAME</literal> and <literal>SET SCHEMA</>
-   can be combined into
-   a list of multiple alterations to apply in parallel.  For example, it
-   is possible to add several columns and/or alter the type of several
-   columns in a single command.
-  </para>
-
-  <para>
-   You must own the table to use <command>ALTER FOREIGN TABLE</>.
-   To change the schema of a foreign table, you must also have
-   <literal>CREATE</literal> privilege on the new schema.
-   To add the table as a new child of a parent table, you must own the
-   parent table as well.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the table's schema.  (These restrictions enforce that altering the owner
-   doesn't do anything you couldn't do by dropping and recreating the table.
-   However, a superuser can alter ownership of any table anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-        The name (possibly schema-qualified) of an existing foreign table to
-        alter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">column</replaceable></term>
-      <listitem>
-       <para>
-        Name of a new or existing column.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_column</replaceable></term>
-      <listitem>
-       <para>
-        New name for an existing column.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_name</replaceable></term>
-      <listitem>
-       <para>
-        New name for the table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">type</replaceable></term>
-      <listitem>
-       <para>
-        Data type of the new column, or new data type for an existing
-        column.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CASCADE</literal></term>
-      <listitem>
-       <para>
-        Automatically drop objects that depend on the dropped column
-        (for example, views referencing the column).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>RESTRICT</literal></term>
-      <listitem>
-       <para>
-        Refuse to drop the column if there are any dependent
-        objects. This is the default behavior.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_owner</replaceable></term>
-      <listitem>
-       <para>
-        The user name of the new owner of the table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_schema</replaceable></term>
-      <listitem>
-       <para>
-        The name of the schema to which the table will be moved.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    The key word <literal>COLUMN</literal> is noise and can be omitted.
-   </para>
-
-   <para>
-    Consistency with the foreign server is not checked when a column is
-    added or removed with <literal>ADD COLUMN</literal> or
-    <literal>DROP COLUMN</literal>, a system <literal>oid</> column is added
-    or removed, a <literal>CHECK</> or <literal>NOT NULL</> constraint is
-    added, or column type is changed with <literal>SET DATA TYPE</>.  It is the
-    user's responsibility to ensure that the table definition matches the
-    remote side.
-   </para>
-
-   <para>
-    Refer to <xref linkend="sql-createforeigntable"> for a further description of valid
-    parameters.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To mark a column as not-null:
-<programlisting>
-ALTER FOREIGN TABLE distributors ALTER COLUMN street SET NOT NULL;
-</programlisting>
-  </para>
-
-  <para>
-   To change options of a foreign table:
-<programlisting>
-ALTER FOREIGN TABLE myschema.distributors OPTIONS (ADD opt1 'value', SET opt2, 'value2', DROP opt3 'value3');
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The forms <literal>ADD</literal>, <literal>DROP</>,
-   and <literal>SET DATA TYPE</literal>
-   conform with the SQL standard.  The other forms are
-   <productname>PostgreSQL</productname> extensions of the SQL standard.
-   Also, the ability to specify more than one manipulation in a single
-   <command>ALTER FOREIGN TABLE</> command is an extension.
-  </para>
-
-  <para>
-   <command>ALTER FOREIGN TABLE DROP COLUMN</> can be used to drop the only
-   column of a foreign table, leaving a zero-column table.  This is an
-   extension of SQL, which disallows zero-column foreign tables.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_function.sgmlin b/doc-xc/src/sgml/ref/alter_function.sgmlin
deleted file mode 100644
index 2d974f2b8b..0000000000
--- a/doc-xc/src/sgml/ref/alter_function.sgmlin
+++ /dev/null
@@ -1,330 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_function.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERFUNCTION">
- <refmeta>
-  <refentrytitle>ALTER FUNCTION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER FUNCTION</refname>
-  <refpurpose>change the definition of a function</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterfunction">
-  <primary>ALTER FUNCTION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER FUNCTION <replaceable>name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">argname</replaceable> ] <replaceable class="parameter">argtype</replaceable> [, ...] ] )
-    <replaceable class="PARAMETER">action</replaceable> [ ... ] [ RESTRICT ]
-ALTER FUNCTION <replaceable>name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">argname</replaceable> ] <replaceable class="parameter">argtype</replaceable> [, ...] ] )
-    RENAME TO <replaceable>new_name</replaceable>
-ALTER FUNCTION <replaceable>name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">argname</replaceable> ] <replaceable class="parameter">argtype</replaceable> [, ...] ] )
-    OWNER TO <replaceable>new_owner</replaceable>
-ALTER FUNCTION <replaceable>name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">argname</replaceable> ] <replaceable class="parameter">argtype</replaceable> [, ...] ] )
-    SET SCHEMA <replaceable>new_schema</replaceable>
-
-<phrase>where <replaceable class="PARAMETER">action</replaceable> is one of:</phrase>
-
-    CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT
-    IMMUTABLE | STABLE | VOLATILE
-    [ EXTERNAL ] SECURITY INVOKER | [ EXTERNAL ] SECURITY DEFINER
-    COST <replaceable class="parameter">execution_cost</replaceable>
-    ROWS <replaceable class="parameter">result_rows</replaceable>
-    SET <replaceable class="parameter">configuration_parameter</replaceable> { TO | = } { <replaceable class="parameter">value</replaceable> | DEFAULT }
-    SET <replaceable class="parameter">configuration_parameter</replaceable> FROM CURRENT
-    RESET <replaceable class="parameter">configuration_parameter</replaceable>
-    RESET ALL
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>ALTER FUNCTION</command> changes the definition of a
-   function.
-  </para>
-
-  <para>
-   You must own the function to use <command>ALTER FUNCTION</>.
-   To change a function's schema, you must also have <literal>CREATE</>
-   privilege on the new schema.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the function's schema.  (These restrictions enforce that altering the owner
-   doesn't do anything you couldn't do by dropping and recreating the function.
-   However, a superuser can alter ownership of any function anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argmode</replaceable></term>
-
-    <listitem>
-     <para>
-      The mode of an argument: <literal>IN</>, <literal>OUT</>,
-      <literal>INOUT</>, or <literal>VARIADIC</>.
-      If omitted, the default is <literal>IN</>.
-      Note that <command>ALTER FUNCTION</command> does not actually pay
-      any attention to <literal>OUT</> arguments, since only the input
-      arguments are needed to determine the function's identity.
-      So it is sufficient to list the <literal>IN</>, <literal>INOUT</>,
-      and <literal>VARIADIC</> arguments.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argname</replaceable></term>
-
-    <listitem>
-     <para>
-      The name of an argument.
-      Note that <command>ALTER FUNCTION</command> does not actually pay
-      any attention to argument names, since only the argument data
-      types are needed to determine the function's identity.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argtype</replaceable></term>
-
-    <listitem>
-     <para>
-      The data type(s) of the function's arguments (optionally
-      schema-qualified), if any.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the function.  Note that if the function is
-      marked <literal>SECURITY DEFINER</literal>, it will subsequently
-      execute as the new owner.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-    <varlistentry>
-     <term><literal>CALLED ON NULL INPUT</literal></term>
-     <term><literal>RETURNS NULL ON NULL INPUT</literal></term>
-     <term><literal>STRICT</literal></term>
-
-     <listitem>
-      <para>
-       <literal>CALLED ON NULL INPUT</literal> changes the function so
-       that it will be invoked when some or all of its arguments are
-       null. <literal>RETURNS NULL ON NULL INPUT</literal> or
-       <literal>STRICT</literal> changes the function so that it is not
-       invoked if any of its arguments are null; instead, a null result
-       is assumed automatically.  See <xref linkend="sql-createfunction">
-       for more information.
-      </para>
-     </listitem>
-   </varlistentry>
-
-    <varlistentry>
-     <term><literal>IMMUTABLE</literal></term>
-     <term><literal>STABLE</literal></term>
-     <term><literal>VOLATILE</literal></term>
-
-     <listitem>
-      <para>
-       Change the volatility of the function to the specified setting.
-       See <xref linkend="sql-createfunction"> for details.
-      </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal><optional> EXTERNAL </optional> SECURITY INVOKER</literal></term>
-    <term><literal><optional> EXTERNAL </optional> SECURITY DEFINER</literal></term>
-
-    <listitem>
-     <para>
-      Change whether the function is a security definer or not. The
-      key word <literal>EXTERNAL</literal> is ignored for SQL
-      conformance. See <xref linkend="sql-createfunction"> for more information about
-      this capability.
-     </para>
-    </listitem>
-   </varlistentry>
-
-    <varlistentry>
-     <term><literal>COST</literal> <replaceable class="parameter">execution_cost</replaceable></term>
-
-     <listitem>
-      <para>
-       Change the estimated execution cost of the function.
-       See <xref linkend="sql-createfunction"> for more information.
-      </para>
-     </listitem>
-   </varlistentry>
-
-    <varlistentry>
-     <term><literal>ROWS</literal> <replaceable class="parameter">result_rows</replaceable></term>
-
-     <listitem>
-      <para>
-       Change the estimated number of rows returned by a set-returning
-       function.  See <xref linkend="sql-createfunction"> for more information.
-      </para>
-     </listitem>
-   </varlistentry>
-
-     <varlistentry>
-      <term><replaceable>configuration_parameter</replaceable></term>
-      <term><replaceable>value</replaceable></term>
-      <listitem>
-       <para>
-        Add or change the assignment to be made to a configuration parameter
-        when the function is called.  If
-        <replaceable>value</replaceable> is <literal>DEFAULT</literal>
-        or, equivalently, <literal>RESET</literal> is used, the function-local
-        setting is removed, so that the function executes with the value
-        present in its environment.  Use <literal>RESET
-        ALL</literal> to clear all function-local settings.
-        <literal>SET FROM CURRENT</> saves the session's current value of
-        the parameter as the value to be applied when the function is entered.
-       </para>
-
-       <para>
-        See <xref linkend="sql-set"> and
-        <xref linkend="runtime-config">
-        for more information about allowed parameter names and values.
-       </para>
-      </listitem>
-     </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-
-    <listitem>
-     <para>
-      Ignored for conformance with the SQL standard.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To rename the function <literal>sqrt</literal> for type
-   <type>integer</type> to <literal>square_root</literal>:
-<programlisting>
-ALTER FUNCTION sqrt(integer) RENAME TO square_root;
-</programlisting>
-  </para>
-
-  <para>
-   To change the owner of the function <literal>sqrt</literal> for type
-   <type>integer</type> to <literal>joe</literal>:
-<programlisting>
-ALTER FUNCTION sqrt(integer) OWNER TO joe;
-</programlisting>
-  </para>
-
-  <para>
-   To change the schema of the function <literal>sqrt</literal> for type
-   <type>integer</type> to <literal>maths</literal>:
-<programlisting>
-ALTER FUNCTION sqrt(integer) SET SCHEMA maths;
-</programlisting>
-  </para>
-
-  <para>
-   To adjust the search path that is automatically set for a function:
-<programlisting>
-ALTER FUNCTION check_password(text) SET search_path = admin, pg_temp;
-</programlisting>
-  </para>
-
-  <para>
-   To disable automatic setting of <varname>search_path</> for a function:
-<programlisting>
-ALTER FUNCTION check_password(text) RESET search_path;
-</programlisting>
-   The function will now execute with whatever search path is used by its
-   caller.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   This statement is partially compatible with the <command>ALTER
-   FUNCTION</> statement in the SQL standard. The standard allows more
-   properties of a function to be modified, but does not provide the
-   ability to rename a function, make a function a security definer,
-   attach configuration parameter values to a function,
-   or change the owner, schema, or volatility of a function. The standard also
-   requires the <literal>RESTRICT</> key word, which is optional in
-<!## PG>
-   <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</>.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createfunction"></member>
-   <member><xref linkend="sql-dropfunction"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_group.sgmlin b/doc-xc/src/sgml/ref/alter_group.sgmlin
deleted file mode 100644
index b2cfa0ce8c..0000000000
--- a/doc-xc/src/sgml/ref/alter_group.sgmlin
+++ /dev/null
@@ -1,132 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_group.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERGROUP">
- <refmeta>
-  <refentrytitle>ALTER GROUP</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER GROUP</refname>
-  <refpurpose>change role name or membership</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altergroup">
-  <primary>ALTER GROUP</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER GROUP <replaceable class="PARAMETER">group_name</replaceable> ADD USER <replaceable class="PARAMETER">user_name</replaceable> [, ... ]
-ALTER GROUP <replaceable class="PARAMETER">group_name</replaceable> DROP USER <replaceable class="PARAMETER">user_name</replaceable> [, ... ]
-
-ALTER GROUP <replaceable class="PARAMETER">group_name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>ALTER GROUP</command> changes the attributes of a user group.
-   This is an obsolete command, though still accepted for backwards
-   compatibility, because groups (and users too) have been superseded by the
-   more general concept of roles.
-  </para>
-
-  <para>
-   The first two variants add users to a group or remove them from a group.
-   (Any role can play the part of either a <quote>user</> or a
-   <quote>group</> for this purpose.)  These variants are effectively
-   equivalent to granting or revoking membership in the role named as the
-   <quote>group</>; so the preferred way to do this is to use
-   <xref linkend="SQL-GRANT"> or
-   <xref linkend="SQL-REVOKE">.
-  </para>
-
-  <para>
-   The third variant changes the name of the group.  This is exactly
-   equivalent to renaming the role with
-   <xref linkend="sql-alterrole">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">group_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the group (role) to modify.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">user_name</replaceable></term>
-    <listitem>
-     <para>
-      Users (roles) that are to be added to or removed from the group.
-      The users must already exist; <command>ALTER GROUP</> does not
-      create or drop users.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the group.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-  <para>
-   Add users to a group:
-
-<programlisting>
-ALTER GROUP staff ADD USER karl, john;
-</programlisting>
-
-   Remove a user from a group:
-
-<programlisting>
-ALTER GROUP workers DROP USER beth;
-</programlisting>
-
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER GROUP</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-grant"></member>
-   <member><xref linkend="sql-revoke"></member>
-   <member><xref linkend="sql-alterrole"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_index.sgmlin b/doc-xc/src/sgml/ref/alter_index.sgmlin
deleted file mode 100644
index b0f3cfc805..0000000000
--- a/doc-xc/src/sgml/ref/alter_index.sgmlin
+++ /dev/null
@@ -1,226 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_index.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERINDEX">
- <refmeta>
-  <refentrytitle>ALTER INDEX</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER INDEX</refname>
-  <refpurpose>change the definition of an index</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterindex">
-  <primary>ALTER INDEX</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER INDEX <replaceable class="PARAMETER">name</replaceable> RENAME TO <replaceable class="PARAMETER">new_name</replaceable>
-ALTER INDEX <replaceable class="PARAMETER">name</replaceable> SET TABLESPACE <replaceable class="PARAMETER">tablespace_name</replaceable>
-ALTER INDEX <replaceable class="PARAMETER">name</replaceable> SET ( <replaceable class="PARAMETER">storage_parameter</replaceable> = <replaceable class="PARAMETER">value</replaceable> [, ... ] )
-ALTER INDEX <replaceable class="PARAMETER">name</replaceable> RESET ( <replaceable class="PARAMETER">storage_parameter</replaceable> [, ... ] )
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER INDEX</command> changes the definition of an existing index.
-   There are several subforms:
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>RENAME</literal></term>
-    <listitem>
-     <para>
-      The <literal>RENAME</literal> form changes the name of the index.
-      There is no effect on the stored data.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET TABLESPACE</literal></term>
-    <listitem>
-     <para>
-      This form changes the index's tablespace to the specified tablespace and
-      moves the data file(s) associated with the index to the new tablespace.
-      See also
-      <xref linkend="SQL-CREATETABLESPACE">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET ( <replaceable class="PARAMETER">storage_parameter</replaceable> = <replaceable class="PARAMETER">value</replaceable> [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      This form changes one or more index-method-specific storage parameters
-      for the index.  See
-      <xref linkend="SQL-CREATEINDEX">
-      for details on the available parameters.  Note that the index contents
-      will not be modified immediately by this command; depending on the
-      parameter you might need to rebuild the index with
-      <xref linkend="SQL-REINDEX">
-      to get the desired effects.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESET ( <replaceable class="PARAMETER">storage_parameter</replaceable> [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      This form resets one or more index-method-specific storage parameters to
-      their defaults.  As with <literal>SET</>, a <literal>REINDEX</literal>
-      might be needed to update the index entirely.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-        The name (possibly schema-qualified) of an existing index to
-        alter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_name</replaceable></term>
-      <listitem>
-       <para>
-        The new name for the index.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">tablespace_name</replaceable></term>
-      <listitem>
-       <para>
-        The tablespace to which the index will be moved.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">storage_parameter</replaceable></term>
-      <listitem>
-       <para>
-        The name of an index-method-specific storage parameter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">value</replaceable></term>
-      <listitem>
-       <para>
-        The new value for an index-method-specific storage parameter.
-        This might be a number or a word depending on the parameter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    These operations are also possible using
-    <xref linkend="SQL-ALTERTABLE">.
-    <command>ALTER INDEX</> is in fact just an alias for the forms
-    of <command>ALTER TABLE</> that apply to indexes.
-   </para>
-
-   <para>
-    There was formerly an <command>ALTER INDEX OWNER</> variant, but
-    this is now ignored (with a warning).  An index cannot have an owner
-    different from its table's owner.  Changing the table's owner
-    automatically changes the index as well.
-   </para>
-
-   <para>
-    Changing any part of a system catalog index is not permitted.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-  <para>
-   To rename an existing index:
-<programlisting>
-ALTER INDEX distributors RENAME TO suppliers;
-</programlisting>
-  </para>
-
-  <para>
-   To move an index to a different tablespace:
-<programlisting>
-ALTER INDEX distributors SET TABLESPACE fasttablespace;
-</programlisting>
-  </para>
-
-  <para>
-   To change an index's fill factor (assuming that the index method
-   supports it):
-<programlisting>
-ALTER INDEX distributors SET (fillfactor = 75);
-REINDEX INDEX distributors;
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-<!## PG>
-   <command>ALTER INDEX</> is a <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   <command>ALTER INDEX</> is a <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   <command>ALTER INDEX</> is a <productname>Postgres-XL</productname>
-<!## end>
-   extension.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createindex"></member>
-   <member><xref linkend="sql-reindex"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_language.sgmlin b/doc-xc/src/sgml/ref/alter_language.sgmlin
deleted file mode 100644
index 443c50558a..0000000000
--- a/doc-xc/src/sgml/ref/alter_language.sgmlin
+++ /dev/null
@@ -1,93 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_language.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERLANGUAGE">
- <refmeta>
-  <refentrytitle>ALTER LANGUAGE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER LANGUAGE</refname>
-  <refpurpose>change the definition of a procedural language</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterlanguage">
-  <primary>ALTER LANGUAGE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER [ PROCEDURAL ] LANGUAGE <replaceable>name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER [ PROCEDURAL ] LANGUAGE <replaceable>name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER LANGUAGE</command> changes the definition of a
-   procedural language.  The only functionality is to rename the language or
-   assign a new owner.  You must be superuser or owner of the language to
-   use <command>ALTER LANGUAGE</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable>name</replaceable></term>
-    <listitem>
-     <para>
-      Name of a language
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the language
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the language
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER LANGUAGE</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createlanguage"></member>
-   <member><xref linkend="sql-droplanguage"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_large_object.sgmlin b/doc-xc/src/sgml/ref/alter_large_object.sgmlin
deleted file mode 100644
index 82c3dfef1e..0000000000
--- a/doc-xc/src/sgml/ref/alter_large_object.sgmlin
+++ /dev/null
@@ -1,100 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_large_object.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERLARGEOBJECT">
- <refmeta>
-  <refentrytitle>ALTER LARGE OBJECT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER LARGE OBJECT</refname>
-  <refpurpose>change the definition of a large object</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterlargeobject">
-  <primary>ALTER LARGE OBJECT</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER LARGE OBJECT <replaceable class="PARAMETER">large_object_oid</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-<!## XC>
-&xconly;
-  <para>
-   <command>LARGE OBJECT</> has not been supported
-   by <productname>Postgres-XC</> yet. This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>LARGE OBJECT</> has not been supported
-   by <productname>Postgres-XL</> yet. This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-&pgnotice;
-
-  <para>
-   <command>ALTER LARGE OBJECT</command> changes the definition of a
-   large object. The only functionality is to assign a new owner.
-   You must be superuser or owner of the large object to use
-   <command>ALTER LARGE OBJECT</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable>large_object_oid</replaceable></term>
-    <listitem>
-     <para>
-      OID of the large object to be altered
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the large object
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER LARGE OBJECT</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="largeobjects"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_node.sgmlin b/doc-xc/src/sgml/ref/alter_node.sgmlin
deleted file mode 100644
index 7ebd3a14d0..0000000000
--- a/doc-xc/src/sgml/ref/alter_node.sgmlin
+++ /dev/null
@@ -1,330 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_node.sgml,v 1.54 2010/04/03 07:22:58 petere Exp $
-PostgreSQL documentation
--->
-<!## XC>
-<refentry id="SQL-ALTERNODE">
- <refmeta>
-  <refentrytitle>ALTER NODE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER NODE</refname>
-  <refpurpose>alter a cluster node</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alternode">
-  <primary>ALTER NODE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER NODE <replaceable class="parameter">nodename</replaceable> WITH
-  (
-    [ TYPE = <replaceable class="parameter">nodetype</replaceable>,]
-    [ HOST = <replaceable class="parameter">hostname</replaceable>,]
-    [ PORT = <replaceable class="parameter">portnum</replaceable>,]
-    [ PRIMARY [ = <replaceable class="parameter">boolean</replaceable>],]
-    [ PREFERRED [ = <replaceable class="parameter">boolean</replaceable> ] ]
-  )
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xconly;
-
-  <para>
-   <command>ALTER NODE</command> is new SQL query specific
-   to <productname>Postgres-XC</productname> since 0.9.7 that modifies
-   cluster node information in catalog pgxc_node.
-  </para>
-  <para>
-   Node connection that has been modified does not guaranty that connection
-   information cached in pooler is updated accordingly.
-  </para>
-  <para>
-   <command>ALTER NODE</command> only runs on the local node where it is launched.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">nodename</replaceable></term>
-      <listitem>
-       <para>
-        The name of the selected cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>TYPE</literal></term>
-      <listitem>
-       <para>
-        The type of the cluster node. It is possible to specify
-        a Coordinator node or a Datanode node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PRIMARY</literal></term>
-      <listitem>
-       <para>
-        Defines if the cluster node is used as a primary node for replicated
-        write operations. A <replaceable class="parameter">boolean</replaceable>
-        value can be specified. In case no value is specified, <literal>PRIMARY</literal>
-        acts like <literal>true</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PREFERRED</literal></term>
-      <listitem>
-       <para>
-        Defines if the cluster node is used as a preferred node for replicated
-        read operations. A <replaceable class="parameter">boolean</replaceable>
-        value can be specified. In case no value is specified, <literal>PREFERRED</literal>
-        acts like <literal>true</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">nodetype</replaceable></term>
-      <listitem>
-       <para>
-        The node type for given cluster node. Possible values are:
-        'coordinator' for a Coordinator node and 'datanode' for a
-        Datanode node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">hostname</replaceable></term>
-      <listitem>
-       <para>
-        The hostname or IP used to connect to the cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">portnum</replaceable></term>
-      <listitem>
-       <para>
-        The port number used to connect to the cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-  <para>
-    A Datanode can be modified as <literal>PRIMARY</literal> and
-    as <literal>PREFERRED</literal> as many times as necessary.
-  </para>
-
-  <para>
-    A node type cannot be modified.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-  <para>
-   Modify a Coordinator node located on local machine to use port 6543.
-<programlisting>
-ALTER NODE coord_node WITH (PORT = 6543, HOST = 'localhost');
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>ALTER NODE</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XC specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
-<!## XL>
-<refentry id="SQL-ALTERNODE">
- <refmeta>
-  <refentrytitle>ALTER NODE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER NODE</refname>
-  <refpurpose>alter a cluster node</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alternode">
-  <primary>ALTER NODE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER NODE <replaceable class="parameter">nodename</replaceable> WITH
-  (
-    [ TYPE = <replaceable class="parameter">nodetype</replaceable>,]
-    [ HOST = <replaceable class="parameter">hostname</replaceable>,]
-    [ PORT = <replaceable class="parameter">portnum</replaceable>,]
-    [ PRIMARY [ = <replaceable class="parameter">boolean</replaceable>],]
-    [ PREFERRED [ = <replaceable class="parameter">boolean</replaceable> ] ]
-  )
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xlonly;
-
-  <para>
-   <command>ALTER NODE</command> is a new SQL command specific
-   to <productname>Postgres-XL</productname> that modifies
-   cluster node information in catalog pgxc_node.
-  </para>
-  <para>
-   Node connection that has been modified does not guaranty that connection
-   information cached in pooler is updated accordingly.
-  </para>
-  <para>
-   <command>ALTER NODE</command> only runs on the local node where it is launched.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">nodename</replaceable></term>
-      <listitem>
-       <para>
-        The name of the selected cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>TYPE</literal></term>
-      <listitem>
-       <para>
-        The type of the cluster node. It is possible to specify
-        a Coordinator node or a Datanode node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PRIMARY</literal></term>
-      <listitem>
-       <para>
-        Defines if the cluster node is used as a primary node for replicated
-        write operations. A <replaceable class="parameter">boolean</replaceable>
-        value can be specified. In case no value is specified, <literal>PRIMARY</literal>
-        acts like <literal>true</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PREFERRED</literal></term>
-      <listitem>
-       <para>
-        Defines if the cluster node is used as a preferred node for replicated
-        read operations. A <replaceable class="parameter">boolean</replaceable>
-        value can be specified. In case no value is specified, <literal>PREFERRED</literal>
-        acts like <literal>true</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">nodetype</replaceable></term>
-      <listitem>
-       <para>
-        The node type for given cluster node. Possible values are:
-        'coordinator' for a Coordinator node and 'datanode' for a
-        Datanode node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">hostname</replaceable></term>
-      <listitem>
-       <para>
-        The hostname or IP used to connect to the cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">portnum</replaceable></term>
-      <listitem>
-       <para>
-        The port number used to connect to the cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-  <para>
-    A Datanode can be modified as <literal>PRIMARY</literal> and
-    as <literal>PREFERRED</literal> as many times as necessary.
-  </para>
-
-  <para>
-    A node type cannot be modified.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-  <para>
-   Modify a Coordinator node located on local machine to use port 6543.
-<programlisting>
-ALTER NODE coord_node WITH (PORT = 6543, HOST = 'localhost');
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>ALTER NODE</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XL specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
diff --git a/doc-xc/src/sgml/ref/alter_opclass.sgmlin b/doc-xc/src/sgml/ref/alter_opclass.sgmlin
deleted file mode 100644
index d32af65c34..0000000000
--- a/doc-xc/src/sgml/ref/alter_opclass.sgmlin
+++ /dev/null
@@ -1,121 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_opclass.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTEROPCLASS">
- <refmeta>
-  <refentrytitle>ALTER OPERATOR CLASS</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER OPERATOR CLASS</refname>
-  <refpurpose>change the definition of an operator class</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alteropclass">
-  <primary>ALTER OPERATOR CLASS</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER OPERATOR CLASS <replaceable>name</replaceable> USING <replaceable class="parameter">index_method</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER OPERATOR CLASS <replaceable>name</replaceable> USING <replaceable class="parameter">index_method</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-ALTER OPERATOR CLASS <replaceable>name</replaceable> USING <replaceable class="parameter">index_method</replaceable> SET SCHEMA <replaceable>new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER OPERATOR CLASS</command> changes the definition of
-   an operator class.
-  </para>
-
-  <para>
-   You must own the operator class to use <command>ALTER OPERATOR CLASS</>.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the operator class's schema.  (These restrictions enforce that altering the
-   owner doesn't do anything you couldn't do by dropping and recreating the
-   operator class.  However, a superuser can alter ownership of any operator
-   class anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing operator
-      class.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">index_method</replaceable></term>
-    <listitem>
-     <para>
-      The name of the index method this operator class is for.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the operator class.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the operator class.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the operator class.
-     </para>
-    </listitem>
-   </varlistentry>
- </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER OPERATOR CLASS</command> statement in
-   the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createopclass"></member>
-   <member><xref linkend="sql-dropopclass"></member>
-   <member><xref linkend="sql-alteropfamily"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_operator.sgmlin b/doc-xc/src/sgml/ref/alter_operator.sgmlin
deleted file mode 100644
index ca85472181..0000000000
--- a/doc-xc/src/sgml/ref/alter_operator.sgmlin
+++ /dev/null
@@ -1,131 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_operator.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTEROPERATOR">
- <refmeta>
-  <refentrytitle>ALTER OPERATOR</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER OPERATOR</refname>
-  <refpurpose>change the definition of an operator</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alteroperator">
-  <primary>ALTER OPERATOR</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER OPERATOR <replaceable>name</replaceable> ( { <replaceable>left_type</replaceable> | NONE } , { <replaceable>right_type</replaceable> | NONE } ) OWNER TO <replaceable>new_owner</replaceable>
-ALTER OPERATOR <replaceable>name</replaceable> ( { <replaceable>left_type</replaceable> | NONE } , { <replaceable>right_type</replaceable> | NONE } ) SET SCHEMA <replaceable>new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER OPERATOR</command> changes the definition of
-   an operator.  The only currently available functionality is to change the
-   owner of the operator.
-  </para>
-
-  <para>
-   You must own the operator to use <command>ALTER OPERATOR</>.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the operator's schema.  (These restrictions enforce that altering the owner
-   doesn't do anything you couldn't do by dropping and recreating the operator.
-   However, a superuser can alter ownership of any operator anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing operator.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">left_type</replaceable></term>
-    <listitem>
-     <para>
-      The data type of the operator's left operand; write
-      <literal>NONE</literal> if the operator has no left operand.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">right_type</replaceable></term>
-    <listitem>
-     <para>
-      The data type of the operator's right operand; write
-      <literal>NONE</literal> if the operator has no right operand.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the operator.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the operator.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Change the owner of a custom operator <literal>a @@ b</literal> for type <type>text</type>:
-<programlisting>
-ALTER OPERATOR @@ (text, text) OWNER TO joe;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER OPERATOR</command> statement in
-   the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createoperator"></member>
-   <member><xref linkend="sql-dropoperator"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_opfamily.sgmlin b/doc-xc/src/sgml/ref/alter_opfamily.sgmlin
deleted file mode 100644
index 217396e58a..0000000000
--- a/doc-xc/src/sgml/ref/alter_opfamily.sgmlin
+++ /dev/null
@@ -1,358 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_opfamily.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTEROPFAMILY">
- <refmeta>
-  <refentrytitle>ALTER OPERATOR FAMILY</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER OPERATOR FAMILY</refname>
-  <refpurpose>change the definition of an operator family</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alteropfamily">
-  <primary>ALTER OPERATOR FAMILY</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER OPERATOR FAMILY <replaceable>name</replaceable> USING <replaceable class="parameter">index_method</replaceable> ADD
-  {  OPERATOR <replaceable class="parameter">strategy_number</replaceable> <replaceable class="parameter">operator_name</replaceable> ( <replaceable class="parameter">op_type</replaceable>, <replaceable class="parameter">op_type</replaceable> ) [ FOR SEARCH | FOR ORDER BY <replaceable class="parameter">sort_family_name</replaceable> ]
-   | FUNCTION <replaceable class="parameter">support_number</replaceable> [ ( <replaceable class="parameter">op_type</replaceable> [ , <replaceable class="parameter">op_type</replaceable> ] ) ] <replaceable class="parameter">function_name</replaceable> ( <replaceable class="parameter">argument_type</replaceable> [, ...] )
-  } [, ... ]
-ALTER OPERATOR FAMILY <replaceable>name</replaceable> USING <replaceable class="parameter">index_method</replaceable> DROP
-  {  OPERATOR <replaceable class="parameter">strategy_number</replaceable> ( <replaceable class="parameter">op_type</replaceable> [ , <replaceable class="parameter">op_type</replaceable> ] )
-   | FUNCTION <replaceable class="parameter">support_number</replaceable> ( <replaceable class="parameter">op_type</replaceable> [ , <replaceable class="parameter">op_type</replaceable> ] )
-  } [, ... ]
-ALTER OPERATOR FAMILY <replaceable>name</replaceable> USING <replaceable class="parameter">index_method</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER OPERATOR FAMILY <replaceable>name</replaceable> USING <replaceable class="parameter">index_method</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-ALTER OPERATOR FAMILY <replaceable>name</replaceable> USING <replaceable class="parameter">index_method</replaceable> SET SCHEMA <replaceable>new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER OPERATOR FAMILY</command> changes the definition of
-   an operator family.  You can add operators and support functions
-   to the family, remove them from the family,
-   or change the family's name or owner.
-  </para>
-
-  <para>
-   When operators and support functions are added to a family with
-   <command>ALTER OPERATOR FAMILY</command>, they are not part of any
-   specific operator class within the family, but are just <quote>loose</>
-   within the family.  This indicates that these operators and functions
-   are compatible with the family's semantics, but are not required for
-   correct functioning of any specific index.  (Operators and functions
-   that are so required should be declared as part of an operator class,
-   instead; see <xref linkend="sql-createopclass">.)
-<!## PG>
-   <productname>PostgreSQL</productname> will allow loose members of a
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> will allow loose members of a
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> will allow loose members of a
-<!## end>
-   family to be dropped from the family at any time, but members of an
-   operator class cannot be dropped without dropping the whole class and
-   any indexes that depend on it.
-   Typically, single-data-type operators
-   and functions are part of operator classes because they are needed to
-   support an index on that specific data type, while cross-data-type
-   operators and functions are made loose members of the family.
-  </para>
-
-  <para>
-   You must be a superuser to use <command>ALTER OPERATOR FAMILY</>.
-   (This restriction is made because an erroneous operator family definition
-   could confuse or even crash the server.)
-  </para>
-
-  <para>
-   <command>ALTER OPERATOR FAMILY</command> does not presently check
-   whether the operator family definition includes all the operators and
-   functions required by the index method, nor whether the operators and
-   functions form a self-consistent set.  It is the user's
-   responsibility to define a valid operator family.
-  </para>
-
-  <para>
-   Refer to <xref linkend="xindex"> for further information.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing operator
-      family.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">index_method</replaceable></term>
-    <listitem>
-     <para>
-      The name of the index method this operator family is for.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">strategy_number</replaceable></term>
-    <listitem>
-     <para>
-      The index method's strategy number for an operator
-      associated with the operator family.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">operator_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an operator associated
-      with the operator family.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">op_type</replaceable></term>
-    <listitem>
-     <para>
-      In an <literal>OPERATOR</> clause,
-      the operand data type(s) of the operator, or <literal>NONE</> to
-      signify a left-unary or right-unary operator.  Unlike the comparable
-      syntax in <command>CREATE OPERATOR CLASS</>, the operand data types
-      must always be specified.
-     </para>
-
-     <para>
-      In an <literal>ADD FUNCTION</> clause, the operand data type(s) the
-      function is intended to support, if different from
-      the input data type(s) of the function.  For B-tree and hash indexes
-      it is not necessary to specify <replaceable
-      class="parameter">op_type</replaceable> since the function's input
-      data type(s) are always the correct ones to use.  For GIN and GiST
-      indexes it is necessary to specify the input data type the function
-      is to be used with.
-     </para>
-
-     <para>
-      In a <literal>DROP FUNCTION</> clause, the operand data type(s) the
-      function is intended to support must be specified.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">sort_family_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing <literal>btree</literal> operator
-      family that describes the sort ordering associated with an ordering
-      operator.
-     </para>
-
-     <para>
-      If neither <literal>FOR SEARCH</> nor <literal>FOR ORDER BY</> is
-      specified, <literal>FOR SEARCH</> is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">support_number</replaceable></term>
-    <listitem>
-     <para>
-      The index method's support procedure number for a
-      function associated with the operator family.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">function_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of a function that is an
-      index method support procedure for the operator family.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argument_type</replaceable></term>
-    <listitem>
-     <para>
-      The parameter data type(s) of the function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the operator family.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the operator family.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the operator family.
-     </para>
-    </listitem>
-   </varlistentry>
- </variablelist>
-
-  <para>
-   The <literal>OPERATOR</> and <literal>FUNCTION</>
-   clauses can appear in any order.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Notice that the <literal>DROP</> syntax only specifies the <quote>slot</>
-   in the operator family, by strategy or support number and input data
-   type(s).  The name of the operator or function occupying the slot is not
-   mentioned.  Also, for <literal>DROP FUNCTION</> the type(s) to specify
-   are the input data type(s) the function is intended to support; for
-   GIN and GiST indexes this might have nothing to do with the actual input
-   argument types of the function.
-  </para>
-
-  <para>
-   Because the index machinery does not check access permissions on functions
-   before using them, including a function or operator in an operator family
-   is tantamount to granting public execute permission on it.  This is usually
-   not an issue for the sorts of functions that are useful in an operator
-   family.
-  </para>
-
-  <para>
-   The operators should not be defined by SQL functions.  A SQL function
-   is likely to be inlined into the calling query, which will prevent
-   the optimizer from recognizing that the query matches an index.
-  </para>
-
-  <para>
-   Before <productname>PostgreSQL</productname> 8.4, the <literal>OPERATOR</>
-   clause could include a <literal>RECHECK</> option.  This is no longer
-   supported because whether an index operator is <quote>lossy</> is now
-   determined on-the-fly at run time.  This allows efficient handling of
-   cases where an operator might or might not be lossy.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   The following example command adds cross-data-type operators and
-   support functions to an operator family that already contains B-tree
-   operator classes for data types <type>int4</> and <type>int2</>.
-  </para>
-
-<programlisting>
-ALTER OPERATOR FAMILY integer_ops USING btree ADD
-
-  -- int4 vs int2
-  OPERATOR 1 &lt; (int4, int2) ,
-  OPERATOR 2 &lt;= (int4, int2) ,
-  OPERATOR 3 = (int4, int2) ,
-  OPERATOR 4 &gt;= (int4, int2) ,
-  OPERATOR 5 &gt; (int4, int2) ,
-  FUNCTION 1 btint42cmp(int4, int2) ,
-
-  -- int2 vs int4
-  OPERATOR 1 &lt; (int2, int4) ,
-  OPERATOR 2 &lt;= (int2, int4) ,
-  OPERATOR 3 = (int2, int4) ,
-  OPERATOR 4 &gt;= (int2, int4) ,
-  OPERATOR 5 &gt; (int2, int4) ,
-  FUNCTION 1 btint24cmp(int2, int4) ;
-</programlisting>
-
-  <para>
-   To remove these entries again:
-  </para>
-
-<programlisting>
-ALTER OPERATOR FAMILY integer_ops USING btree DROP
-
-  -- int4 vs int2
-  OPERATOR 1 (int4, int2) ,
-  OPERATOR 2 (int4, int2) ,
-  OPERATOR 3 (int4, int2) ,
-  OPERATOR 4 (int4, int2) ,
-  OPERATOR 5 (int4, int2) ,
-  FUNCTION 1 (int4, int2) ,
-
-  -- int2 vs int4
-  OPERATOR 1 (int2, int4) ,
-  OPERATOR 2 (int2, int4) ,
-  OPERATOR 3 (int2, int4) ,
-  OPERATOR 4 (int2, int4) ,
-  OPERATOR 5 (int2, int4) ,
-  FUNCTION 1 (int2, int4) ;
-</programlisting>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER OPERATOR FAMILY</command> statement in
-   the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createopfamily"></member>
-   <member><xref linkend="sql-dropopfamily"></member>
-   <member><xref linkend="sql-createopclass"></member>
-   <member><xref linkend="sql-alteropclass"></member>
-   <member><xref linkend="sql-dropopclass"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_role.sgmlin b/doc-xc/src/sgml/ref/alter_role.sgmlin
deleted file mode 100644
index 5e9dbbbd64..0000000000
--- a/doc-xc/src/sgml/ref/alter_role.sgmlin
+++ /dev/null
@@ -1,332 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_role.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERROLE">
- <refmeta>
-  <refentrytitle>ALTER ROLE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER ROLE</refname>
-  <refpurpose>change a database role</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterrole">
-  <primary>ALTER ROLE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER ROLE <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replaceable class="PARAMETER">option</replaceable> [ ... ] ]
-
-<phrase>where <replaceable class="PARAMETER">option</replaceable> can be:</phrase>
-
-      SUPERUSER | NOSUPERUSER
-    | CREATEDB | NOCREATEDB
-    | CREATEROLE | NOCREATEROLE
-    | CREATEUSER | NOCREATEUSER
-    | INHERIT | NOINHERIT
-    | LOGIN | NOLOGIN
-    | REPLICATION | NOREPLICATION
-    | CONNECTION LIMIT <replaceable class="PARAMETER">connlimit</replaceable>
-    | [ ENCRYPTED | UNENCRYPTED ] PASSWORD '<replaceable class="PARAMETER">password</replaceable>'
-    | VALID UNTIL '<replaceable class="PARAMETER">timestamp</replaceable>'
-
-ALTER ROLE <replaceable class="PARAMETER">name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-
-ALTER ROLE <replaceable class="PARAMETER">name</replaceable> [ IN DATABASE <replaceable class="PARAMETER">database_name</replaceable> ] SET <replaceable>configuration_parameter</replaceable> { TO | = } { <replaceable>value</replaceable> | DEFAULT }
-ALTER ROLE <replaceable class="PARAMETER">name</replaceable> [ IN DATABASE <replaceable class="PARAMETER">database_name</replaceable> ] SET <replaceable>configuration_parameter</replaceable> FROM CURRENT
-ALTER ROLE <replaceable class="PARAMETER">name</replaceable> [ IN DATABASE <replaceable class="PARAMETER">database_name</replaceable> ] RESET <replaceable>configuration_parameter</replaceable>
-ALTER ROLE <replaceable class="PARAMETER">name</replaceable> [ IN DATABASE <replaceable class="PARAMETER">database_name</replaceable> ] RESET ALL
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER ROLE</command> changes the attributes of a
-<!## PG>
-   <productname>PostgreSQL</productname> role.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> role.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> role.
-<!## end>
-  </para>
-
-  <para>
-   The first variant of this command listed in the synopsis can change
-   many of the role attributes that can be specified in
-   <xref linkend="sql-createrole">.
-   (All the possible attributes are covered,
-   except that there are no options for adding or removing memberships; use
-   <xref linkend="SQL-GRANT"> and
-   <xref linkend="SQL-REVOKE"> for that.)
-   Attributes not mentioned in the command retain their previous settings.
-   Database superusers can change any of these settings for any role.
-   Roles having <literal>CREATEROLE</> privilege can change any of these
-   settings, but only for non-superuser and non-replication roles.
-   Ordinary roles can only change their own password.
-  </para>
-
-  <para>
-   The second variant changes the name of the role.
-   Database superusers can rename any role.
-   Roles having <literal>CREATEROLE</> privilege can rename non-superuser
-   roles.
-   The current session user cannot be renamed.
-   (Connect as a different user if you need to do that.)
-   Because <literal>MD5</>-encrypted passwords use the role name as
-   cryptographic salt, renaming a role clears its password if the
-   password is <literal>MD5</>-encrypted.
-  </para>
-
-  <para>
-   The remaining variants change a role's session default for a configuration
-   variable, either for all databases or, when the <literal>IN
-   DATABASE</literal> clause is specified, only for sessions in
-   the named database. Whenever the role subsequently
-   starts a new session, the specified value becomes the session
-   default, overriding whatever setting is present in
-   <filename>postgresql.conf</> or has been received from the <command>postgres</command>
-   command line. This only happens at login time; executing
-   <xref linkend="sql-set-role"> or
-   <xref linkend="sql-set-session-authorization"> does not cause new
-   configuration values to be set.
-   Settings set for all databases are overridden by database-specific settings
-   attached to a role.
-   Superusers can change anyone's session defaults. Roles having
-   <literal>CREATEROLE</> privilege can change defaults for non-superuser
-   roles. Ordinary roles can only set defaults for themselves.
-   Certain configuration variables cannot be set this way, or can only be
-   set if a superuser issues the command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the role whose attributes are to be altered.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>SUPERUSER</literal></term>
-      <term><literal>NOSUPERUSER</literal></term>
-      <term><literal>CREATEDB</></term>
-      <term><literal>NOCREATEDB</></term>
-      <term><literal>CREATEROLE</literal></term>
-      <term><literal>NOCREATEROLE</literal></term>
-      <term><literal>CREATEUSER</literal></term>
-      <term><literal>NOCREATEUSER</literal></term>
-      <term><literal>INHERIT</literal></term>
-      <term><literal>NOINHERIT</literal></term>
-      <term><literal>LOGIN</literal></term>
-      <term><literal>NOLOGIN</literal></term>
-      <term><literal>REPLICATION</literal></term>
-      <term><literal>NOREPLICATION</literal></term>
-      <term><literal>CONNECTION LIMIT</literal> <replaceable class="parameter">connlimit</replaceable></term>
-      <term><literal>PASSWORD</> <replaceable class="parameter">password</replaceable></term>
-      <term><literal>ENCRYPTED</></term>
-      <term><literal>UNENCRYPTED</></term>
-      <term><literal>VALID UNTIL</literal> '<replaceable class="parameter">timestamp</replaceable>'</term>
-      <listitem>
-       <para>
-        These clauses alter attributes originally set by
-        <xref linkend="SQL-CREATEROLE">. For more information, see the
-        <command>CREATE ROLE</command> reference page.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable>new_name</replaceable></term>
-      <listitem>
-       <para>
-        The new name of the role.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><replaceable>database_name</replaceable></term>
-       <listitem>
-         <para>
-           The name of the database the configuration variable should be set in.
-         </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable>configuration_parameter</replaceable></term>
-      <term><replaceable>value</replaceable></term>
-      <listitem>
-       <para>
-        Set this role's session default for the specified configuration
-        parameter to the given value.  If
-        <replaceable>value</replaceable> is <literal>DEFAULT</literal>
-        or, equivalently, <literal>RESET</literal> is used, the
-        role-specific variable setting is removed, so the role will
-        inherit the system-wide default setting in new sessions.  Use
-        <literal>RESET ALL</literal> to clear all role-specific settings.
-        <literal>SET FROM CURRENT</> saves the session's current value of
-        the parameter as the role-specific value.
-        If <literal>IN DATABASE</literal> is specified, the configuration
-        parameter is set or removed for the given role and database only.
-       </para>
-
-       <para>
-        Role-specific variable settings take effect only at login;
-        <xref linkend="sql-set-role"> and
-        <xref linkend="sql-set-session-authorization">
-        do not process role-specific variable settings.
-       </para>
-
-       <para>
-        See <xref linkend="sql-set"> and <xref
-        linkend="runtime-config"> for more information about allowed
-        parameter names and values.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-CREATEROLE">
-   to add new roles, and <xref linkend="SQL-DROPROLE"> to remove a role.
-  </para>
-
-  <para>
-   <command>ALTER ROLE</command> cannot change a role's memberships.
-   Use <xref linkend="SQL-GRANT"> and
-   <xref linkend="SQL-REVOKE">
-   to do that.
-  </para>
-
-  <para>
-   Caution must be exercised when specifying an unencrypted password
-   with this command.  The password will be transmitted to the server
-   in cleartext, and it might also be logged in the client's command
-   history or the server log.  <xref linkend="app-psql">
-   contains a command
-   <command>\password</command> that can be used to change a
-   role's password without exposing the cleartext password.
-  </para>
-
-  <para>
-   It is also possible to tie a
-   session default to a specific database rather than to a role; see
-   <xref linkend="sql-alterdatabase">.
-   If there is a conflict, database-role-specific settings override role-specific
-   ones, which in turn override database-specific ones.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Change a role's password:
-
-<programlisting>
-ALTER ROLE davide WITH PASSWORD 'hu8jmn3';
-</programlisting>
-  </para>
-
-  <para>
-   Remove a role's password:
-
-<programlisting>
-ALTER ROLE davide WITH PASSWORD NULL;
-</programlisting>
-  </para>
-
-  <para>
-   Change a password expiration date, specifying that the password
-   should expire at midday on 4th May 2015 using
-   the time zone which is one hour ahead of <acronym>UTC</>:
-<programlisting>
-ALTER ROLE chris VALID UNTIL 'May 4 12:00:00 2015 +1';
-</programlisting>
-  </para>
-
-  <para>
-   Make a password valid forever:
-<programlisting>
-ALTER ROLE fred VALID UNTIL 'infinity';
-</programlisting>
-  </para>
-
-  <para>
-   Give a role the ability to create other roles and new databases:
-
-<programlisting>
-ALTER ROLE miriam CREATEROLE CREATEDB;
-</programlisting>
-  </para>
-
-  <para>
-   Give a role a non-default setting of the
-   <xref linkend="guc-maintenance-work-mem"> parameter:
-
-<programlisting>
-ALTER ROLE worker_bee SET maintenance_work_mem = 100000;
-</programlisting>
-  </para>
-
-  <para>
-   Give a role a non-default, database-specific setting of the
-   <xref linkend="guc-client-min-messages"> parameter:
-
-<programlisting>
-ALTER ROLE fred IN DATABASE devel SET client_min_messages = DEBUG;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The <command>ALTER ROLE</command> statement is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createrole"></member>
-   <member><xref linkend="sql-droprole"></member>
-   <member><xref linkend="sql-set"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_schema.sgmlin b/doc-xc/src/sgml/ref/alter_schema.sgmlin
deleted file mode 100644
index dc58376713..0000000000
--- a/doc-xc/src/sgml/ref/alter_schema.sgmlin
+++ /dev/null
@@ -1,102 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_schema.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERSCHEMA">
- <refmeta>
-  <refentrytitle>ALTER SCHEMA</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER SCHEMA</refname>
-  <refpurpose>change the definition of a schema</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterschema">
-  <primary>ALTER SCHEMA</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER SCHEMA <replaceable>name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER SCHEMA <replaceable>name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER SCHEMA</command> changes the definition of a schema.
-  </para>
-
-  <para>
-   You must own the schema to use <command>ALTER SCHEMA</>.
-   To rename a schema you must also have the
-   <literal>CREATE</literal> privilege for the database.
-   To alter the owner, you must also be a direct or
-   indirect member of the new owning role, and you must have the
-   <literal>CREATE</literal> privilege for the database.
-   (Note that superusers have all these privileges automatically.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable>name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing schema.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the schema.  The new name cannot
-      begin with <literal>pg_</literal>, as such names
-      are reserved for system schemas.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the schema.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER SCHEMA</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createschema"></member>
-   <member><xref linkend="sql-dropschema"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_sequence.sgmlin b/doc-xc/src/sgml/ref/alter_sequence.sgmlin
deleted file mode 100644
index 4c7bc6c60f..0000000000
--- a/doc-xc/src/sgml/ref/alter_sequence.sgmlin
+++ /dev/null
@@ -1,312 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_sequence.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERSEQUENCE">
- <refmeta>
-  <refentrytitle>ALTER SEQUENCE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER SEQUENCE</refname>
-  <refpurpose>
-   change the definition of a sequence generator
-  </refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altersequence">
-  <primary>ALTER SEQUENCE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER SEQUENCE <replaceable class="parameter">name</replaceable> [ INCREMENT [ BY ] <replaceable class="parameter">increment</replaceable> ]
-    [ MINVALUE <replaceable class="parameter">minvalue</replaceable> | NO MINVALUE ] [ MAXVALUE <replaceable class="parameter">maxvalue</replaceable> | NO MAXVALUE ]
-    [ START [ WITH ] <replaceable class="parameter">start</replaceable> ]
-    [ RESTART [ [ WITH ] <replaceable class="parameter">restart</replaceable> ] ]
-    [ CACHE <replaceable class="parameter">cache</replaceable> ] [ [ NO ] CYCLE ]
-    [ OWNED BY { <replaceable class="parameter">table</replaceable>.<replaceable class="parameter">column</replaceable> | NONE } ]
-ALTER SEQUENCE <replaceable class="parameter">name</replaceable> OWNER TO <replaceable class="PARAMETER">new_owner</replaceable>
-ALTER SEQUENCE <replaceable class="parameter">name</replaceable> RENAME TO <replaceable class="parameter">new_name</replaceable>
-ALTER SEQUENCE <replaceable class="parameter">name</replaceable> SET SCHEMA <replaceable class="parameter">new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>ALTER SEQUENCE</command> changes the parameters of an existing
-   sequence generator.  Any parameters not specifically set in the
-   <command>ALTER SEQUENCE</command> command retain their prior settings.
-  </para>
-
-  <para>
-   You must own the sequence to use <command>ALTER SEQUENCE</>.
-   To change a sequence's schema, you must also have <literal>CREATE</>
-   privilege on the new schema.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the sequence's schema.  (These restrictions enforce that altering the owner
-   doesn't do anything you couldn't do by dropping and recreating the sequence.
-   However, a superuser can alter ownership of any sequence anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">name</replaceable></term>
-      <listitem>
-       <para>
-        The name (optionally schema-qualified) of a sequence to be altered.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">increment</replaceable></term>
-      <listitem>
-       <para>
-        The clause <literal>INCREMENT BY <replaceable
-        class="parameter">increment</replaceable></literal> is
-        optional. A positive value will make an ascending sequence, a
-        negative one a descending sequence.  If unspecified, the old
-        increment value will be maintained.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">minvalue</replaceable></term>
-      <term><literal>NO MINVALUE</literal></term>
-      <listitem>
-       <para>
-        The optional clause <literal>MINVALUE <replaceable
-        class="parameter">minvalue</replaceable></literal> determines
-        the minimum value a sequence can generate. If <literal>NO
-        MINVALUE</literal> is specified, the defaults of 1 and
-        -2<superscript>63</>-1 for ascending and descending sequences,
-        respectively, will be used.  If neither option is specified,
-        the current minimum value will be maintained.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">maxvalue</replaceable></term>
-      <term><literal>NO MAXVALUE</literal></term>
-      <listitem>
-       <para>
-        The optional clause <literal>MAXVALUE <replaceable
-        class="parameter">maxvalue</replaceable></literal> determines
-        the maximum value for the sequence. If <literal>NO
-        MAXVALUE</literal> is specified, the defaults are
-        2<superscript>63</>-1 and -1 for ascending and descending
-        sequences, respectively, will be used.  If neither option is
-        specified, the current maximum value will be maintained.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">start</replaceable></term>
-      <listitem>
-       <para>
-        The optional clause <literal>START WITH <replaceable
-        class="parameter">start</replaceable></literal> changes the
-        recorded start value of the sequence.  This has no effect on the
-        <emphasis>current</> sequence value; it simply sets the value
-        that future <command>ALTER SEQUENCE RESTART</> commands will use.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">restart</replaceable></term>
-      <listitem>
-       <para>
-        The optional clause <literal>RESTART [ WITH <replaceable
-        class="parameter">restart</replaceable> ]</literal> changes the
-        current value of the sequence.  This is equivalent to calling the
-        <function>setval</> function with <literal>is_called</literal> =
-        <literal>false</>: the specified value will be returned by the
-        <emphasis>next</> call of <function>nextval</>.
-        Writing <literal>RESTART</> with no <replaceable
-        class="parameter">restart</> value is equivalent to supplying
-        the start value that was recorded by <command>CREATE SEQUENCE</>
-        or last set by <command>ALTER SEQUENCE START WITH</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">cache</replaceable></term>
-      <listitem>
-       <para>
-        The clause <literal>CACHE <replaceable
-        class="parameter">cache</replaceable></literal> enables
-        sequence numbers to be preallocated and stored in memory for
-        faster access. The minimum value is 1 (only one value can be
-        generated at a time, i.e., no cache).  If unspecified, the old
-        cache value will be maintained.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CYCLE</literal></term>
-      <listitem>
-       <para>
-        The optional <literal>CYCLE</literal> key word can be used to enable
-        the sequence to wrap around when the
-        <replaceable class="parameter">maxvalue</replaceable> or
-        <replaceable class="parameter">minvalue</replaceable> has been
-        reached by
-        an ascending or descending sequence respectively. If the limit is
-        reached, the next number generated will be the
-        <replaceable class="parameter">minvalue</replaceable> or
-        <replaceable class="parameter">maxvalue</replaceable>,
-        respectively.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>NO CYCLE</literal></term>
-      <listitem>
-       <para>
-        If the optional <literal>NO CYCLE</literal> key word is
-        specified, any calls to <function>nextval</function> after the
-        sequence has reached its maximum value will return an error.
-        If neither <literal>CYCLE</literal> or <literal>NO
-        CYCLE</literal> are specified, the old cycle behavior will be
-        maintained.
-       </para>
-      </listitem>
-     </varlistentry>
-
-   <varlistentry>
-    <term><literal>OWNED BY</literal> <replaceable class="parameter">table</replaceable>.<replaceable class="parameter">column</replaceable></term>
-    <term><literal>OWNED BY NONE</literal></term>
-    <listitem>
-     <para>
-      The <literal>OWNED BY</literal> option causes the sequence to be
-      associated with a specific table column, such that if that column
-      (or its whole table) is dropped, the sequence will be automatically
-      dropped as well.  If specified, this association replaces any
-      previously specified association for the sequence.  The specified
-      table must have the same owner and be in the same schema as the
-      sequence.
-      Specifying <literal>OWNED BY NONE</literal> removes any existing
-      association, making the sequence <quote>free-standing</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The user name of the new owner of the sequence.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name for the sequence.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the sequence.
-     </para>
-    </listitem>
-   </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   To avoid blocking of concurrent transactions that obtain numbers from the
-   same sequence, <command>ALTER SEQUENCE</command>'s effects on the sequence
-   generation parameters are never rolled back; those changes take effect
-   immediately and are not reversible.  However, the <literal>OWNED BY</>,
-   <literal>OWNER TO</>, <literal>RENAME TO</>, and <literal>SET SCHEMA</>
-   clauses cause ordinary catalog updates that can be rolled back.
-  </para>
-
-  <para>
-   <command>ALTER SEQUENCE</command> will not immediately affect
-   <function>nextval</> results in backends,
-   other than the current one, that have preallocated (cached) sequence
-   values. They will use up all cached values prior to noticing the changed
-   sequence generation parameters.  The current backend will be affected
-   immediately.
-  </para>
-
-  <para>
-   <command>ALTER SEQUENCE</command> does not affect the <function>currval</>
-   status for the sequence.  (Before <productname>PostgreSQL</productname>
-   8.3, it sometimes did.)
-  </para>
-
-  <para>
-   For historical reasons, <command>ALTER TABLE</command> can be used with
-   sequences too; but the only variants of <command>ALTER TABLE</command>
-   that are allowed with sequences are equivalent to the forms shown above.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Restart a sequence called <literal>serial</literal>, at 105:
-<programlisting>
-ALTER SEQUENCE serial RESTART WITH 105;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>ALTER SEQUENCE</command> conforms to the <acronym>SQL</acronym>
-   standard, except for the <literal>START WITH</>,
-   <literal>OWNED BY</>, <literal>OWNER TO</>, <literal>RENAME TO</>, and
-   <literal>SET SCHEMA</literal> clauses, which are
-   <productname>PostgreSQL</productname> extensions.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createsequence"></member>
-   <member><xref linkend="sql-dropsequence"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_server.sgmlin b/doc-xc/src/sgml/ref/alter_server.sgmlin
deleted file mode 100644
index 0a60d34c6a..0000000000
--- a/doc-xc/src/sgml/ref/alter_server.sgmlin
+++ /dev/null
@@ -1,144 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_server.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERSERVER">
- <refmeta>
-  <refentrytitle>ALTER SERVER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER SERVER</refname>
-  <refpurpose>change the definition of a foreign server</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterserver">
-  <primary>ALTER SERVER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER SERVER <replaceable class="parameter">server_name</replaceable> [ VERSION '<replaceable class="parameter">new_version</replaceable>' ]
-    [ OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">value</replaceable>'] [, ... ] ) ]
-ALTER SERVER <replaceable class="PARAMETER">server_name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-<!## XC>
-&xconly;
-  <para>
-   <command>SERVER</> has not been supported
-   by <productname>Postgres-XC</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>SERVER</> is not yet supported
-   in <productname>Postgres-XL</>.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-&pgonly;
-
-  <para>
-   <command>ALTER SERVER</command> changes the definition of a foreign
-   server.  The first form changes the server version string or the
-   generic options of the server (at least one clause is required).
-   The second form changes the owner of the server.
-  </para>
-
-  <para>
-   To alter the server you must be the owner of the server.
-   Additionally to alter the owner, you must own the server and also
-   be a direct or indirect member of the new owning role, and you must
-   have <literal>USAGE</> privilege on the server's foreign-data
-   wrapper.  (Note that superusers satisfy all these criteria
-   automatically.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">server_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing server.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_version</replaceable></term>
-    <listitem>
-     <para>
-      New server version.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">value</replaceable>'] [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      Change options for the
-      server.  <literal>ADD</>, <literal>SET</>, and <literal>DROP</>
-      specify the action to be performed.  <literal>ADD</> is assumed
-      if no operation is explicitly specified.  Option names must be
-      unique; names and values are also validated using the server's
-      foreign-data wrapper library.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Alter server <literal>foo</>, add connection options:
-<programlisting>
-ALTER SERVER foo OPTIONS (host 'foo', dbname 'foodb');
-</programlisting>
-  </para>
-
-  <para>
-   Alter server <literal>foo</>, change version,
-   change <literal>host</> option:
-<programlisting>
-ALTER SERVER foo VERSION '8.4' OPTIONS (SET host 'baz');
-</programlisting>
-  </para>
-
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>ALTER SERVER</command> conforms to ISO/IEC 9075-9 (SQL/MED).
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createserver"></member>
-   <member><xref linkend="sql-dropserver"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_table.sgmlin b/doc-xc/src/sgml/ref/alter_table.sgmlin
deleted file mode 100644
index eaf8675ede..0000000000
--- a/doc-xc/src/sgml/ref/alter_table.sgmlin
+++ /dev/null
@@ -1,1531 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_table.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERTABLE">
- <refmeta>
-  <refentrytitle>ALTER TABLE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER TABLE</refname>
-  <refpurpose>change the definition of a table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altertable">
-  <primary>ALTER TABLE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER TABLE [ ONLY ] <replaceable class="PARAMETER">name</replaceable> [ * ]
-    <replaceable class="PARAMETER">action</replaceable> [, ... ]
-ALTER TABLE [ ONLY ] <replaceable class="PARAMETER">name</replaceable> [ * ]
-    RENAME [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> TO <replaceable class="PARAMETER">new_column</replaceable>
-ALTER TABLE <replaceable class="PARAMETER">name</replaceable>
-    RENAME TO <replaceable class="PARAMETER">new_name</replaceable>
-ALTER TABLE <replaceable class="PARAMETER">name</replaceable>
-    SET SCHEMA <replaceable class="PARAMETER">new_schema</replaceable>
-
-<phrase>where <replaceable class="PARAMETER">action</replaceable> is one of:</phrase>
-
-    ADD [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> <replaceable class="PARAMETER">data_type</replaceable> [ COLLATE <replaceable class="PARAMETER">collation</replaceable> ] [ <replaceable class="PARAMETER">column_constraint</replaceable> [ ... ] ]
-    DROP [ COLUMN ] [ IF EXISTS ] <replaceable class="PARAMETER">column</replaceable> [ RESTRICT | CASCADE ]
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> [ SET DATA ] TYPE <replaceable class="PARAMETER">data_type</replaceable> [ COLLATE <replaceable class="PARAMETER">collation</replaceable> ] [ USING <replaceable class="PARAMETER">expression</replaceable> ]
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> SET DEFAULT <replaceable class="PARAMETER">expression</replaceable>
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> DROP DEFAULT
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> { SET | DROP } NOT NULL
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> SET STATISTICS <replaceable class="PARAMETER">integer</replaceable>
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> SET ( <replaceable class="PARAMETER">attribute_option</replaceable> = <replaceable class="PARAMETER">value</replaceable> [, ... ] )
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> RESET ( <replaceable class="PARAMETER">attribute_option</replaceable> [, ... ] )
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> SET STORAGE { PLAIN | EXTERNAL | EXTENDED | MAIN }
-    ADD <replaceable class="PARAMETER">table_constraint</replaceable>
-    ADD <replaceable class="PARAMETER">table_constraint_using_index</replaceable>
-    ADD <replaceable class="PARAMETER">table_constraint</replaceable> [ NOT VALID ]
-    VALIDATE CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable>
-    DROP CONSTRAINT [ IF EXISTS ]  <replaceable class="PARAMETER">constraint_name</replaceable> [ RESTRICT | CASCADE ]
-    DISABLE TRIGGER [ <replaceable class="PARAMETER">trigger_name</replaceable> | ALL | USER ]
-    ENABLE TRIGGER [ <replaceable class="PARAMETER">trigger_name</replaceable> | ALL | USER ]
-    ENABLE REPLICA TRIGGER <replaceable class="PARAMETER">trigger_name</replaceable>
-    ENABLE ALWAYS TRIGGER <replaceable class="PARAMETER">trigger_name</replaceable>
-    DISABLE RULE <replaceable class="PARAMETER">rewrite_rule_name</replaceable>
-    ENABLE RULE <replaceable class="PARAMETER">rewrite_rule_name</replaceable>
-    ENABLE REPLICA RULE <replaceable class="PARAMETER">rewrite_rule_name</replaceable>
-    ENABLE ALWAYS RULE <replaceable class="PARAMETER">rewrite_rule_name</replaceable>
-    CLUSTER ON <replaceable class="PARAMETER">index_name</replaceable>
-    SET WITHOUT CLUSTER
-    SET WITH OIDS
-    SET WITHOUT OIDS
-    SET ( <replaceable class="PARAMETER">storage_parameter</replaceable> = <replaceable class="PARAMETER">value</replaceable> [, ... ] )
-    RESET ( <replaceable class="PARAMETER">storage_parameter</replaceable> [, ... ] )
-    INHERIT <replaceable class="PARAMETER">parent_table</replaceable>
-    NO INHERIT <replaceable class="PARAMETER">parent_table</replaceable>
-    OF <replaceable class="PARAMETER">type_name</replaceable>
-    NOT OF
-    OWNER TO <replaceable class="PARAMETER">new_owner</replaceable>
-    SET TABLESPACE <replaceable class="PARAMETER">new_tablespace</replaceable>
-    DISTRIBUTE BY { REPLICATION | ROUNDROBIN | { [HASH | MODULO ] ( <replaceable class="PARAMETER">column_name</replaceable> ) } }
-    TO { GROUP <replaceable class="PARAMETER">groupname</replaceable> | NODE ( <replaceable class="PARAMETER">nodename</replaceable> [, ... ] ) }
-    ADD NODE ( <replaceable class="PARAMETER">nodename</replaceable> [, ... ] )
-    DELETE NODE ( <replaceable class="PARAMETER">nodename</replaceable> [, ... ] )
-
-<phrase>and <replaceable class="PARAMETER">table_constraint_using_index</replaceable> is:</phrase>
-
-    [ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-    { UNIQUE | PRIMARY KEY } USING INDEX <replaceable class="PARAMETER">index_name</replaceable>
-    [ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER TABLE</command> changes the definition of an existing table.
-   There are several subforms:
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>ADD COLUMN</literal></term>
-    <listitem>
-     <para>
-      This form adds a new column to the table, using the same syntax as
-      <xref linkend="SQL-CREATETABLE">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DROP COLUMN [ IF EXISTS ]</literal></term>
-    <listitem>
-     <para>
-      This form drops a column from a table.  Indexes and
-      table constraints involving the column will be automatically
-      dropped as well.  You will need to say <literal>CASCADE</> if
-      anything outside the table depends on the column, for example,
-      foreign key references or views.
-      If <literal>IF EXISTS</literal> is specified and the column
-      does not exist, no error is thrown. In this case a notice
-      is issued instead.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET DATA TYPE</literal></term>
-    <listitem>
-     <para>
-      This form changes the type of a column of a table. Indexes and
-      simple table constraints involving the column will be automatically
-      converted to use the new column type by reparsing the originally
-      supplied expression.
-      The optional <literal>COLLATE</literal> clause specifies a collation
-      for the new column; if omitted, the collation is the default for the
-      new column type.
-      The optional <literal>USING</literal>
-      clause specifies how to compute the new column value from the old;
-      if omitted, the default conversion is the same as an assignment
-      cast from old data type to new.  A  <literal>USING</literal>
-      clause must be provided if there is no implicit or assignment
-      cast from old to new type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET</literal>/<literal>DROP DEFAULT</literal></term>
-    <listitem>
-     <para>
-      These forms set or remove the default value for a column.
-      The default values only apply to subsequent <command>INSERT</command>
-      commands; they do not cause rows already in the table to change.
-      Defaults can also be created for views, in which case they are
-      inserted into <command>INSERT</> statements on the view before
-      the view's <literal>ON INSERT</literal> rule is applied.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET</literal>/<literal>DROP NOT NULL</literal></term>
-    <listitem>
-     <para>
-      These forms change whether a column is marked to allow null
-      values or to reject null values.  You can only use <literal>SET
-      NOT NULL</> when the column contains no null values.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET STATISTICS</literal></term>
-    <listitem>
-     <para>
-      This form
-      sets the per-column statistics-gathering target for subsequent
-      <xref linkend="sql-analyze"> operations.
-      The target can be set in the range 0 to 10000; alternatively, set it
-      to -1 to revert to using the system default statistics
-      target (<xref linkend="guc-default-statistics-target">).
-      For more information on the use of statistics by the
-<!## PG>
-      <productname>PostgreSQL</productname> query planner, refer to
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname> query planner, refer to
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname> query planner, refer to
-<!## end>
-      <xref linkend="planner-stats">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET ( <replaceable class="PARAMETER">attribute_option</replaceable> = <replaceable class="PARAMETER">value</replaceable> [, ... ] )</literal></term>
-    <term><literal>RESET ( <replaceable class="PARAMETER">attribute_option</replaceable> [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      This form sets or resets per-attribute options.  Currently, the only
-      defined per-attribute options are <literal>n_distinct</> and
-      <literal>n_distinct_inherited</>, which override the
-      number-of-distinct-values estimates made by subsequent
-      <xref linkend="sql-analyze">
-      operations.  <literal>n_distinct</> affects the statistics for the table
-      itself, while <literal>n_distinct_inherited</> affects the statistics
-      gathered for the table plus its inheritance children.  When set to a
-      positive value, <command>ANALYZE</> will assume that the column contains
-      exactly the specified number of distinct nonnull values.  When set to a
-      negative value, which must be greater
-      than or equal to -1, <command>ANALYZE</> will assume that the number of
-      distinct nonnull values in the column is linear in the size of the
-      table; the exact count is to be computed by multiplying the estimated
-      table size by the absolute value of the given number.  For example,
-      a value of -1 implies that all values in the column are distinct, while
-      a value of -0.5 implies that each value appears twice on the average.
-      This can be useful when the size of the table changes over time, since
-      the multiplication by the number of rows in the table is not performed
-      until query planning time.  Specify a value of 0 to revert to estimating
-      the number of distinct values normally.  For more information on the use
-<!## PG>
-      of statistics by the <productname>PostgreSQL</productname> query
-<!## end>
-<!## XC>
-      of statistics by the <productname>Postgres-XC</productname> query
-<!## end>
-<!## XL>
-      of statistics by the <productname>Postgres-XL</productname> query
-<!## end>
-      planner, refer to <xref linkend="planner-stats">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <indexterm>
-     <primary>TOAST</primary>
-     <secondary>per-column storage settings</secondary>
-    </indexterm>
-
-    <term><literal>SET STORAGE</literal></term>
-    <listitem>
-     <para>
-      This form sets the storage mode for a column. This controls whether this
-      column is held inline or in a secondary <acronym>TOAST</> table, and
-      whether the data
-      should be compressed or not. <literal>PLAIN</literal> must be used
-      for fixed-length values such as <type>integer</type> and is
-      inline, uncompressed. <literal>MAIN</literal> is for inline,
-      compressible data. <literal>EXTERNAL</literal> is for external,
-      uncompressed data, and <literal>EXTENDED</literal> is for external,
-      compressed data.  <literal>EXTENDED</literal> is the default for most
-      data types that support non-<literal>PLAIN</literal> storage.
-      Use of <literal>EXTERNAL</literal> will make substring operations on
-      very large <type>text</type> and <type>bytea</type> values run faster,
-      at the penalty of increased storage space.  Note that
-      <literal>SET STORAGE</> doesn't itself change anything in the table,
-      it just sets the strategy to be pursued during future table updates.
-      See <xref linkend="storage-toast"> for more information.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ADD <replaceable class="PARAMETER">table_constraint</replaceable>
-          [ NOT VALID ]</literal></term>
-    <listitem>
-     <para>
-      This form adds a new constraint to a table using the same syntax as
-      <xref linkend="SQL-CREATETABLE">. Newly added foreign key constraints can
-      also be defined as <literal>NOT VALID</literal> to avoid the
-      potentially lengthy initial check that must otherwise be performed.
-      Constraint checks are skipped at create table time, so
-      <xref linkend="SQL-CREATETABLE"> does not contain this option.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>VALIDATE CONSTRAINT</literal></term>
-    <listitem>
-     <para>
-      This form validates a foreign key constraint that was previously created
-      as <literal>NOT VALID</literal>. Constraints already marked valid do not
-      cause an error response.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ADD <replaceable class="PARAMETER">table_constraint_using_index</replaceable></literal></term>
-    <listitem>
-     <para>
-      This form adds a new <literal>PRIMARY KEY</> or <literal>UNIQUE</>
-      constraint to a table based on an existing unique index.  All the
-      columns of the index will be included in the constraint.
-     </para>
-
-     <para>
-      The index cannot have expression columns nor be a partial index.
-      Also, it must be a b-tree index with default sort ordering.  These
-      restrictions ensure that the index is equivalent to one that would be
-      built by a regular <literal>ADD PRIMARY KEY</> or <literal>ADD UNIQUE</>
-      command.
-     </para>
-
-     <para>
-      If <literal>PRIMARY KEY</> is specified, and the index's columns are not
-      already marked <literal>NOT NULL</>, then this command will attempt to
-      do <literal>ALTER COLUMN SET NOT NULL</> against each such column.
-      That requires a full table scan to verify the column(s) contain no
-      nulls.  In all other cases, this is a fast operation.
-     </para>
-
-     <para>
-      If a constraint name is provided then the index will be renamed to match
-      the constraint name.  Otherwise the constraint will be named the same as
-      the index.
-     </para>
-
-     <para>
-      After this command is executed, the index is <quote>owned</> by the
-      constraint, in the same way as if the index had been built by
-      a regular <literal>ADD PRIMARY KEY</> or <literal>ADD UNIQUE</>
-      command.  In particular, dropping the constraint will make the index
-      disappear too.
-     </para>
-
-     <note>
-      <para>
-       Adding a constraint using an existing index can be helpful in
-       situations where a new constraint needs to be added without blocking
-       table updates for a long time.  To do that, create the index using
-       <command>CREATE INDEX CONCURRENTLY</>, and then install it as an
-       official constraint using this syntax.  See the example below.
-      </para>
-     </note>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DROP CONSTRAINT [ IF EXISTS ]</literal></term>
-    <listitem>
-     <para>
-      This form drops the specified constraint on a table.
-      If <literal>IF EXISTS</literal> is specified and the constraint
-      does not exist, no error is thrown. In this case a notice is issued instead.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DISABLE</literal>/<literal>ENABLE [ REPLICA | ALWAYS ] TRIGGER</literal></term>
-    <listitem>
-     <para>
-      These forms configure the firing of trigger(s) belonging to the table.
-      A disabled trigger is still known to the system, but is not executed
-      when its triggering event occurs.  For a deferred trigger, the enable
-      status is checked when the event occurs, not when the trigger function
-      is actually executed.  One can disable or enable a single
-      trigger specified by name, or all triggers on the table, or only
-      user triggers (this option excludes internally generated constraint
-      triggers such as those that are used to implement foreign key
-      constraints or deferrable uniqueness and exclusion constraints).
-      Disabling or enabling internally generated constraint triggers
-      requires superuser privileges; it should be done with caution since
-      of course the integrity of the constraint cannot be guaranteed if the
-      triggers are not executed.
-      The trigger firing mechanism is also affected by the configuration
-      variable <xref linkend="guc-session-replication-role">. Simply enabled
-      triggers will fire when the replication role is <quote>origin</>
-      (the default) or <quote>local</>. Triggers configured as <literal>ENABLE
-      REPLICA</literal> will only fire if the session is in <quote>replica</>
-      mode, and triggers configured as <literal>ENABLE ALWAYS</literal> will
-      fire regardless of the current replication mode.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DISABLE</literal>/<literal>ENABLE [ REPLICA | ALWAYS ] RULE</literal></term>
-    <listitem>
-     <para>
-      These forms configure the firing of rewrite rules belonging to the table.
-      A disabled rule is still known to the system, but is not applied
-      during query rewriting. The semantics are as for disabled/enabled
-      triggers. This configuration is ignored for <literal>ON SELECT</literal> rules, which
-      are always applied in order to keep views working even if the current
-      session is in a non-default replication role.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CLUSTER</literal></term>
-    <listitem>
-     <para>
-      This form selects the default index for future
-      <xref linkend="SQL-CLUSTER">
-      operations.  It does not actually re-cluster the table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET WITHOUT CLUSTER</literal></term>
-    <listitem>
-     <para>
-      This form removes the most recently used
-      <xref linkend="SQL-CLUSTER">
-      index specification from the table.  This affects
-      future cluster operations that don't specify an index.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET WITH OIDS</literal></term>
-    <listitem>
-     <para>
-      This form adds an <literal>oid</literal> system column to the
-      table (see <xref linkend="ddl-system-columns">).
-      It does nothing if the table already has OIDs.
-     </para>
-
-     <para>
-      Note that this is not equivalent to <literal>ADD COLUMN oid oid</>;
-      that would add a normal column that happened to be named
-      <literal>oid</>, not a system column.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET WITHOUT OIDS</literal></term>
-    <listitem>
-     <para>
-      This form removes the <literal>oid</literal> system column from the
-      table.  This is exactly equivalent to
-      <literal>DROP COLUMN oid RESTRICT</literal>,
-      except that it will not complain if there is already no
-      <literal>oid</literal> column.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET ( <replaceable class="PARAMETER">storage_parameter</replaceable> = <replaceable class="PARAMETER">value</replaceable> [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      This form changes one or more storage parameters for the table.  See
-      <xref linkend="SQL-CREATETABLE-storage-parameters"
-      endterm="SQL-CREATETABLE-storage-parameters-title">
-      for details on the available parameters.  Note that the table contents
-      will not be modified immediately by this command; depending on the
-      parameter you might need to rewrite the table to get the desired effects.
-      That can be done with <link linkend="SQL-VACUUM">VACUUM
-      FULL</>, <xref linkend="SQL-CLUSTER"> or one of the forms
-      of <command>ALTER TABLE</> that forces a table rewrite.
-     </para>
-
-     <note>
-      <para>
-       While <command>CREATE TABLE</> allows <literal>OIDS</> to be specified
-       in the <literal>WITH (<replaceable
-       class="PARAMETER">storage_parameter</>)</literal> syntax,
-       <command>ALTER TABLE</> does not treat <literal>OIDS</> as a
-       storage parameter.  Instead use the <literal>SET WITH OIDS</>
-       and <literal>SET WITHOUT OIDS</> forms to change OID status.
-      </para>
-     </note>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESET ( <replaceable class="PARAMETER">storage_parameter</replaceable> [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      This form resets one or more storage parameters to their
-      defaults.  As with <literal>SET</>, a table rewrite might be
-      needed to update the table entirely.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>INHERIT <replaceable class="PARAMETER">parent_table</replaceable></literal></term>
-    <listitem>
-     <para>
-      This form adds the target table as a new child of the specified parent
-      table.  Subsequently, queries against the parent will include records
-      of the target table.  To be added as a child, the target table must
-      already contain all the same columns as the parent (it could have
-      additional columns, too).  The columns must have matching data types,
-      and if they have <literal>NOT NULL</literal> constraints in the parent
-      then they must also have <literal>NOT NULL</literal> constraints in the
-      child.
-     </para>
-
-     <para>
-      There must also be matching child-table constraints for all
-      <literal>CHECK</literal> constraints of the parent. Currently
-      <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and
-      <literal>FOREIGN KEY</literal> constraints are not considered, but
-      this might change in the future.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NO INHERIT <replaceable class="PARAMETER">parent_table</replaceable></literal></term>
-    <listitem>
-     <para>
-      This form removes the target table from the list of children of the
-      specified parent table.
-      Queries against the parent table will no longer include records drawn
-      from the target table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OF <replaceable class="PARAMETER">type_name</replaceable></literal></term>
-    <listitem>
-     <para>
-      This form links the table to a composite type as though <command>CREATE
-      TABLE OF</> had formed it.  The table's list of column names and types
-      must precisely match that of the composite type; the presence of
-      an <literal>oid</> system column is permitted to differ.  The table must
-      not inherit from any other table.  These restrictions ensure
-      that <command>CREATE TABLE OF</> would permit an equivalent table
-      definition.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NOT OF</literal></term>
-    <listitem>
-     <para>
-      This form dissociates a typed table from its type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OWNER</literal></term>
-    <listitem>
-     <para>
-      This form changes the owner of the table, sequence, or view to the
-      specified user.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET TABLESPACE</literal></term>
-    <listitem>
-     <para>
-      This form changes the table's tablespace to the specified tablespace and
-      moves the data file(s) associated with the table to the new tablespace.
-      Indexes on the table, if any, are not moved; but they can be moved
-      separately with additional <literal>SET TABLESPACE</literal> commands.
-      See also
-      <xref linkend="SQL-CREATETABLESPACE">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RENAME</literal></term>
-    <listitem>
-     <para>
-      The <literal>RENAME</literal> forms change the name of a table
-      (or an index, sequence, or view) or the name of an individual column in
-      a table. There is no effect on the stored data.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET SCHEMA</literal></term>
-    <listitem>
-     <para>
-      This form moves the table into another schema.  Associated indexes,
-      constraints, and sequences owned by table columns are moved as well.
-     </para>
-    </listitem>
-   </varlistentry>
-
-<!## XC>
-   <varlistentry>
-    <term><literal>DISTRIBUTE BY</literal></term>
-    <listitem>
-&xconly;
-     <para>
-      This clause specifies how the table is distributed or replicated among Datanodes.
-     </para>
-
-     <variablelist>
-
-      <varlistentry>
-       <term><literal>REPLICATION</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be replicated into all the
-         Datanode of the <productname>Postgres-XC</> database
-         cluster.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>ROUNDROBIN</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed in one of the Datanodes
-         by round-robin manner.  The value of the row will not be
-         needed to determine what Datanode to go.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>HASH ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the hash value
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>MODULO ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the modulo
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TO GROUP</literal></term>
-    <term><literal>TO NODE</literal></term>
-      <listitem>
-       <para>
-        This defines the list of nodes on which table data exists.
-       </para>
-      </listitem>
-   </varlistentry>
-
-   <varlistentry>
-     <term><literal>ADD NODE</literal></term>
-       <listitem>
-        <para>
-         This adds a list of nodes where data of table is distributed
-         to the existing list. If the list of nodes added contains nodes
-         already used by table, an error is returned.
-        </para>
-       </listitem>
-   </varlistentry>
-
-   <varlistentry>
-     <term><literal>DELETE NODE</literal></term>
-       <listitem>
-        <para>
-         This deletes a list of nodes where data of table is distributed
-         to the existing list. If the list of nodes deleted contains nodes
-         not used by table, an error is returned.
-        </para>
-       </listitem>
-   </varlistentry>
-<!## end>
-<!## XL>
-   <varlistentry>
-    <term><literal>DISTRIBUTE BY</literal></term>
-    <listitem>
-&xlonly;
-     <para>
-      This clause specifies how the table is distributed or replicated among Datanodes.
-     </para>
-
-     <variablelist>
-
-      <varlistentry>
-       <term><literal>REPLICATION</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be replicated into all the
-         Datanodes of the <productname>Postgres-XL</> database
-         cluster.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>ROUNDROBIN</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed in one of the Datanodes
-         by round-robin manner.  The value of the row will not be
-         needed to determine what Datanode to go.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>HASH ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the hash value
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>MODULO ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the modulo
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TO GROUP</literal></term>
-    <term><literal>TO NODE</literal></term>
-      <listitem>
-       <para>
-        This defines the list of nodes on which table data exists.
-       </para>
-      </listitem>
-   </varlistentry>
-
-   <varlistentry>
-     <term><literal>ADD NODE</literal></term>
-       <listitem>
-        <para>
-         This adds a list of nodes where data of table is distributed
-         to the existing list. If the list of nodes added contains nodes
-         already used by table, an error is returned.
-        </para>
-       </listitem>
-   </varlistentry>
-
-   <varlistentry>
-     <term><literal>DELETE NODE</literal></term>
-       <listitem>
-        <para>
-         This deletes a list of nodes where data of table is distributed
-         to the existing list. If the list of nodes deleted contains nodes
-         not used by table, an error is returned.
-        </para>
-       </listitem>
-   </varlistentry>
-<!## end>
-
-  </variablelist>
-  </para>
-
-  <para>
-   All the actions except <literal>RENAME</literal> and <literal>SET SCHEMA</>
-   can be combined into
-   a list of multiple alterations to apply in parallel.  For example, it
-   is possible to add several columns and/or alter the type of several
-   columns in a single command.  This is particularly useful with large
-   tables, since only one pass over the table need be made.
-  </para>
-
-  <para>
-   You must own the table to use <command>ALTER TABLE</>.
-   To change the schema of a table, you must also have
-   <literal>CREATE</literal> privilege on the new schema.
-   To add the table as a new child of a parent table, you must own the
-   parent table as well.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the table's schema.  (These restrictions enforce that altering the owner
-   doesn't do anything you couldn't do by dropping and recreating the table.
-   However, a superuser can alter ownership of any table anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-        The name (possibly schema-qualified) of an existing table to
-        alter. If <literal>ONLY</> is specified, only that table is
-        altered. If <literal>ONLY</> is not specified, the table and any
-        descendant tables are altered.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">column</replaceable></term>
-      <listitem>
-       <para>
-        Name of a new or existing column.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_column</replaceable></term>
-      <listitem>
-       <para>
-        New name for an existing column.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_name</replaceable></term>
-      <listitem>
-       <para>
-        New name for the table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">type</replaceable></term>
-      <listitem>
-       <para>
-        Data type of the new column, or new data type for an existing
-        column.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">table_constraint</replaceable></term>
-      <listitem>
-       <para>
-        New table constraint for the table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">constraint_name</replaceable></term>
-      <listitem>
-       <para>
-        Name of an existing constraint to drop.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CASCADE</literal></term>
-      <listitem>
-       <para>
-        Automatically drop objects that depend on the dropped column
-        or constraint (for example, views referencing the column).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>RESTRICT</literal></term>
-      <listitem>
-       <para>
-        Refuse to drop the column or constraint if there are any dependent
-        objects. This is the default behavior.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">trigger_name</replaceable></term>
-      <listitem>
-       <para>
-        Name of a single trigger to disable or enable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ALL</literal></term>
-      <listitem>
-       <para>
-        Disable or enable all triggers belonging to the table.
-        (This requires superuser privilege if any of the triggers are
-        internally generated constraint triggers such as those that are used
-        to implement foreign key constraints or deferrable uniqueness and
-        exclusion constraints.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>USER</literal></term>
-      <listitem>
-       <para>
-        Disable or enable all triggers belonging to the table except for
-        internally generated constraint triggers such as those that are used
-        to implement foreign key constraints or deferrable uniqueness and
-        exclusion constraints.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">index_name</replaceable></term>
-      <listitem>
-       <para>
-        The index name on which the table should be marked for clustering.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">storage_parameter</replaceable></term>
-      <listitem>
-       <para>
-        The name of a table storage parameter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">value</replaceable></term>
-      <listitem>
-       <para>
-        The new value for a table storage parameter.
-        This might be a number or a word depending on the parameter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">parent_table</replaceable></term>
-      <listitem>
-       <para>
-        A parent table to associate or de-associate with this table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_owner</replaceable></term>
-      <listitem>
-       <para>
-        The user name of the new owner of the table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_tablespace</replaceable></term>
-      <listitem>
-       <para>
-        The name of the tablespace to which the table will be moved.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_schema</replaceable></term>
-      <listitem>
-       <para>
-        The name of the schema to which the table will be moved.
-       </para>
-      </listitem>
-     </varlistentry>
-
-<!## XC>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">nodename</replaceable></term>
-        <listitem>
-         <para>
-          It defines a <productname>Postgres-XC</productname> node of catalog pgxc_node.
-         </para>
-        </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">groupname</replaceable></term>
-        <listitem>
-         <para>
-          It defines a <productname>Postgres-XC</productname> node group in catalog pgxc_group.
-         </para>
-        </listitem>
-     </varlistentry>
-    </variablelist>
-<!## end>
-<!## XL>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">nodename</replaceable></term>
-        <listitem>
-         <para>
-          It defines a <productname>Postgres-XL</productname> node of catalog pgxc_node.
-         </para>
-        </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">groupname</replaceable></term>
-        <listitem>
-         <para>
-          It defines a <productname>Postgres-XL</productname> node group in catalog pgxc_group.
-         </para>
-        </listitem>
-     </varlistentry>
-    </variablelist>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    The key word <literal>COLUMN</literal> is noise and can be omitted.
-   </para>
-
-   <para>
-    When a column is added with <literal>ADD COLUMN</literal>, all existing
-    rows in the table are initialized with the column's default value
-    (NULL if no <literal>DEFAULT</> clause is specified).
-   </para>
-
-   <para>
-    Adding a column with a non-null default or changing the type of an
-    existing column will require the entire table and indexes to be rewritten.
-    As an exception, if the <literal>USING</> clause does not change the column
-    contents and the old type is either binary coercible to the new type or
-    an unconstrained domain over the new type, a table rewrite is not needed,
-    but any indexes on the affected columns must still be rebuilt.  Adding or
-    removing a system <literal>oid</> column also requires rewriting the entire
-    table.  Table and/or index rebuilds may take a significant amount of time
-    for a large table; and will temporarily require as much as double the disk
-    space.
-   </para>
-
-   <para>
-    Adding a <literal>CHECK</> or <literal>NOT NULL</> constraint requires
-    scanning the table to verify that existing rows meet the constraint.
-   </para>
-
-   <para>
-    The main reason for providing the option to specify multiple changes
-    in a single <command>ALTER TABLE</> is that multiple table scans or
-    rewrites can thereby be combined into a single pass over the table.
-   </para>
-
-   <para>
-    The <literal>DROP COLUMN</literal> form does not physically remove
-    the column, but simply makes it invisible to SQL operations.  Subsequent
-    insert and update operations in the table will store a null value for the
-    column. Thus, dropping a column is quick but it will not immediately
-    reduce the on-disk size of your table, as the space occupied
-    by the dropped column is not reclaimed.  The space will be
-    reclaimed over time as existing rows are updated.  (These statements do
-    not apply when dropping the system <literal>oid</> column; that is done
-    with an immediate rewrite.)
-   </para>
-
-   <para>
-    To force an immediate rewrite of the table, you can use
-    <link linkend="SQL-VACUUM">VACUUM FULL</>, <xref linkend="SQL-CLUSTER">
-    or one of the forms of ALTER TABLE that forces a rewrite.  This results in
-    no semantically-visible change in the table, but gets rid of
-    no-longer-useful data.
-   </para>
-
-   <para>
-    The <literal>USING</literal> option of <literal>SET DATA TYPE</> can actually
-    specify any expression involving the old values of the row; that is, it
-    can refer to other columns as well as the one being converted.  This allows
-    very general conversions to be done with the <literal>SET DATA TYPE</>
-    syntax.  Because of this flexibility, the <literal>USING</literal>
-    expression is not applied to the column's default value (if any); the
-    result might not be a constant expression as required for a default.
-    This means that when there is no implicit or assignment cast from old to
-    new type, <literal>SET DATA TYPE</> might fail to convert the default even
-    though a <literal>USING</literal> clause is supplied.  In such cases,
-    drop the default with <literal>DROP DEFAULT</>, perform the <literal>ALTER
-    TYPE</>, and then use <literal>SET DEFAULT</> to add a suitable new
-    default.  Similar considerations apply to indexes and constraints involving
-    the column.
-   </para>
-
-   <para>
-    If a table has any descendant tables, it is not permitted to add,
-    rename, or change the type of a column in the parent table without doing
-    the same to the descendants.  That is, <command>ALTER TABLE ONLY</command>
-    will be rejected.  This ensures that the descendants always have
-    columns matching the parent.
-   </para>
-
-   <para>
-    A recursive <literal>DROP COLUMN</literal> operation will remove a
-    descendant table's column only if the descendant does not inherit
-    that column from any other parents and never had an independent
-    definition of the column.  A nonrecursive <literal>DROP
-    COLUMN</literal> (i.e., <command>ALTER TABLE ONLY ... DROP
-    COLUMN</command>) never removes any descendant columns, but
-    instead marks them as independently defined rather than inherited.
-   </para>
-
-   <para>
-    The <literal>TRIGGER</>, <literal>CLUSTER</>, <literal>OWNER</>,
-    and <literal>TABLESPACE</> actions never recurse to descendant tables;
-    that is, they always act as though <literal>ONLY</> were specified.
-    Adding a constraint can recurse only for <literal>CHECK</> constraints,
-    and is required to do so for such constraints.
-   </para>
-
-   <para>
-    Changing any part of a system catalog table is not permitted.
-   </para>
-
-   <para>
-    Refer to <xref linkend="sql-createtable"> for a further description of valid
-    parameters. <xref linkend="ddl"> has further information on
-    inheritance.
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    <command>ALTER TABLE</> with clauses <literal>DISTRIBUTE BY</>, <literal>ADD NODE</>,
-    <literal>DELETE NODE</>, <literal>TO NODE</> or <literal>TO GROUP</> is used for data
-    redistribution among nodes specific to <productname>Postgres-XC</>. Those clauses cannot be
-    used with other commands.
-   </para>
-
-   <para>
-    Multiple redistribution scenarios are possible depending on modifications done:
-    <variablelist>
-     <varlistentry>
-      <term>Default redistribution:</term>
-      <listitem>
-       <para>
-        This is the slowest scenario possible. It is done in 3 or 4 steps. Data is firstly
-        saved on Coordinator by fetching all the data with <command>COPY TO</> command. At
-        this point all the tuples are saved using tuple store. The amount of cache allowed for
-        tuple store operation can be controlled with <varname>work_mem</>. Then the table is
-        truncated on all the nodes. Then catalogs are updated. Finally data inside tuple store
-        is redistributed using an internal <command>COPY FROM</> mechanism. <command>REINDEX</>
-        is issued if necessary. The overall performance of this scenario is close to the
-        time necessary to run consecutively <command>COPY TO</> and <command>COPY FROM</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Redistribution from replicated to replicated table:</term>
-      <listitem>
-       <para>
-        The node list of a table can have new nodes as well as removed nodes.
-        If nodes are only removed, <command>TRUNCATE</> is launched to remote nodes that are
-        removed. If new nodes are added, then table data is fetch on Coordinator with <command>
-        COPY TO</> and stored inside a tuplestore controlled with <varname>work_mem</>, then
-        data stored is only sent to the new nodes using <command>COPY FROM</> with data stored
-        inside the tuplestore. <command>REINDEX</> is issued if necessary.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Redistribution from replicated to distributed table:</term>
-      <listitem>
-       <para>
-        If the relation node list contains new nodes, the default redistribution
-        mechanism is used. However, if the node list of relation after redistribution is
-        included in node list of relation after redistribution, as all the tuples are already
-        located on remote nodes, it is not necessary to fetch any data on Coordinator. Hence,
-        <command>DELETE</> is used to remove on remote nodes only the necessary tuples. This
-        query uses selects tuples to remove with conditions based on the number of nodes in node
-        list of relation after redistribution, the <literal>HASH</> or <literal>MODULO</> value
-        used for new distribution and the remote node itself where <command>DELETE</> is launched..
-        <command>REINDEX</> is issued if necessary.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Redistribution from distributed to replicated table:</term>
-      <listitem>
-       <para>
-        In this case the default redistribution mechanism is used.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    <command>ALTER TABLE</> with clauses <literal>DISTRIBUTE BY</>, <literal>ADD NODE</>,
-    <literal>DELETE NODE</>, <literal>TO NODE</> or <literal>TO GROUP</> is used for data
-    redistribution among nodes specific to <productname>Postgres-XL</>. Those clauses cannot be
-    used with other commands.
-   </para>
-
-   <para>
-    Multiple redistribution scenarios are possible depending on modifications done:
-    <variablelist>
-     <varlistentry>
-      <term>Default redistribution:</term>
-      <listitem>
-       <para>
-        This is the slowest scenario possible. It is done in 3 or 4 steps. Data is firstly
-        saved on Coordinator by fetching all the data with <command>COPY TO</> command. At
-        this point all the tuples are saved using tuple store. The amount of cache allowed for
-        tuple store operation can be controlled with <varname>work_mem</>. Then the table is
-        truncated on all the nodes. Then catalogs are updated. Finally data inside tuple store
-        is redistributed using an internal <command>COPY FROM</> mechanism. <command>REINDEX</>
-        is issued if necessary. The overall performance of this scenario is close to the
-        time necessary to run consecutively <command>COPY TO</> and <command>COPY FROM</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Redistribution from replicated to replicated table:</term>
-      <listitem>
-       <para>
-        The node list of a table can have new nodes as well as removed nodes.
-        If nodes are only removed, <command>TRUNCATE</> is launched to remote nodes that are
-        removed. If new nodes are added, then table data is fetch on Coordinator with <command>
-        COPY TO</> and stored inside a tuplestore controlled with <varname>work_mem</>, then
-        data stored is only sent to the new nodes using <command>COPY FROM</> with data stored
-        inside the tuplestore. <command>REINDEX</> is issued if necessary.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Redistribution from replicated to distributed table:</term>
-      <listitem>
-       <para>
-        If the relation node list contains new nodes, the default redistribution
-        mechanism is used. However, if the node list of relation after redistribution is
-        included in node list of relation after redistribution, as all the tuples are already
-        located on remote nodes, it is not necessary to fetch any data on Coordinator. Hence,
-        <command>DELETE</> is used to remove on remote nodes only the necessary tuples. This
-        query uses selects tuples to remove with conditions based on the number of nodes in node
-        list of relation after redistribution, the <literal>HASH</> or <literal>MODULO</> value
-        used for new distribution and the remote node itself where <command>DELETE</> is launched..
-        <command>REINDEX</> is issued if necessary.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Redistribution from distributed to replicated table:</term>
-      <listitem>
-       <para>
-        In this case the default redistribution mechanism is used.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To add a column of type <type>varchar</type> to a table:
-<programlisting>
-ALTER TABLE distributors ADD COLUMN address varchar(30);
-</programlisting>
-  </para>
-
-  <para>
-   To drop a column from a table:
-<programlisting>
-ALTER TABLE distributors DROP COLUMN address RESTRICT;
-</programlisting>
-  </para>
-
-  <para>
-   To change the types of two existing columns in one operation:
-<programlisting>
-ALTER TABLE distributors
-    ALTER COLUMN address TYPE varchar(80),
-    ALTER COLUMN name TYPE varchar(100);
-</programlisting>
-  </para>
-
-  <para>
-   To change an integer column containing UNIX timestamps to <type>timestamp
-   with time zone</type> via a <literal>USING</literal> clause:
-<programlisting>
-ALTER TABLE foo
-    ALTER COLUMN foo_timestamp SET DATA TYPE timestamp with time zone
-    USING
-        timestamp with time zone 'epoch' + foo_timestamp * interval '1 second';
-</programlisting>
-  </para>
-
-  <para>
-   The same, when the column has a default expression that won't automatically
-   cast to the new data type:
-<programlisting>
-ALTER TABLE foo
-    ALTER COLUMN foo_timestamp DROP DEFAULT,
-    ALTER COLUMN foo_timestamp TYPE timestamp with time zone
-    USING
-        timestamp with time zone 'epoch' + foo_timestamp * interval '1 second',
-    ALTER COLUMN foo_timestamp SET DEFAULT now();
-</programlisting>
-  </para>
-
-  <para>
-   To rename an existing column:
-<programlisting>
-ALTER TABLE distributors RENAME COLUMN address TO city;
-</programlisting>
-  </para>
-
-  <para>
-   To rename an existing table:
-<programlisting>
-ALTER TABLE distributors RENAME TO suppliers;
-</programlisting>
-  </para>
-
-  <para>
-   To add a not-null constraint to a column:
-<programlisting>
-ALTER TABLE distributors ALTER COLUMN street SET NOT NULL;
-</programlisting>
-   To remove a not-null constraint from a column:
-<programlisting>
-ALTER TABLE distributors ALTER COLUMN street DROP NOT NULL;
-</programlisting>
-  </para>
-
-  <para>
-   To add a check constraint to a table and all its children:
-<programlisting>
-ALTER TABLE distributors ADD CONSTRAINT zipchk CHECK (char_length(zipcode) = 5);
-</programlisting>
-  </para>
-
-  <para>
-   To remove a check constraint from a table and all its children:
-<programlisting>
-ALTER TABLE distributors DROP CONSTRAINT zipchk;
-</programlisting>
-  </para>
-
-  <para>
-   To remove a check constraint from a table only:
-<programlisting>
-ALTER TABLE ONLY distributors DROP CONSTRAINT zipchk;
-</programlisting>
-   (The check constraint remains in place for any child tables.)
-  </para>
-
-  <para>
-   To add a foreign key constraint to a table:
-<programlisting>
-ALTER TABLE distributors ADD CONSTRAINT distfk FOREIGN KEY (address) REFERENCES addresses (address) MATCH FULL;
-</programlisting>
-  </para>
-
-  <para>
-   To add a (multicolumn) unique constraint to a table:
-<programlisting>
-ALTER TABLE distributors ADD CONSTRAINT dist_id_zipcode_key UNIQUE (dist_id, zipcode);
-</programlisting>
-  </para>
-
-  <para>
-   To add an automatically named primary key constraint to a table, noting
-   that a table can only ever have one primary key:
-<programlisting>
-ALTER TABLE distributors ADD PRIMARY KEY (dist_id);
-</programlisting>
-  </para>
-
-  <para>
-   To move a table to a different tablespace:
-<programlisting>
-ALTER TABLE distributors SET TABLESPACE fasttablespace;
-</programlisting>
-  </para>
-
-  <para>
-   To move a table to a different schema:
-<programlisting>
-ALTER TABLE myschema.distributors SET SCHEMA yourschema;
-</programlisting>
-  </para>
-
-  <para>
-   To recreate a primary key constraint, without blocking updates while the
-   index is rebuilt:
-<programlisting>
-CREATE UNIQUE INDEX CONCURRENTLY dist_id_temp_idx ON distributors (dist_id);
-ALTER TABLE distributors DROP CONSTRAINT distributors_pkey,
-    ADD CONSTRAINT distributors_pkey PRIMARY KEY USING INDEX dist_id_temp_idx;
-</programlisting>
-  </para>
-
-<!## XC>
-  <para>
-    To change the distribution type and the list of nodes where table data
-    is located:
-<programlisting>
-ALTER TABLE distributors TO NODE (dn1, dn7), DISTRIBUTE BY HASH(dist_id);
-</programlisting>
-  </para>
-
-  <para>
-    To add a node where data of table is distributed:
-<programlisting>
-ALTER TABLE distributors ADD NODE (dn9, dn14);
-</programlisting>
-  </para>
-
-  <para>
-    To remove a node where data of table is distributed:
-<programlisting>
-ALTER TABLE distributors DELETE NODE (dn4, dn0);
-</programlisting>
-  </para>
-<!## end>
-<!## XL>
-  <para>
-    To change the distribution type and the list of nodes where table data
-    is located:
-<programlisting>
-ALTER TABLE distributors TO NODE (dn1, dn7), DISTRIBUTE BY HASH(dist_id);
-</programlisting>
-  </para>
-
-  <para>
-    To add a node where data of table is distributed:
-<programlisting>
-ALTER TABLE distributors ADD NODE (dn9, dn14);
-</programlisting>
-  </para>
-
-  <para>
-    To remove a node where data of table is distributed:
-<programlisting>
-ALTER TABLE distributors DELETE NODE (dn4, dn0);
-</programlisting>
-  </para>
-<!## end>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The forms <literal>ADD</literal> (without <literal>USING INDEX</literal>),
-   <literal>DROP</>, <literal>SET DEFAULT</>,
-   and <literal>SET DATA TYPE</literal> (without <literal>USING</literal>)
-   conform with the SQL standard.  The other forms are
-<!## PG>
-   <productname>PostgreSQL</productname> extensions of the SQL standard.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extensions of the SQL standard.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extensions of the SQL standard.
-<!## end>
-   Also, the ability to specify more than one manipulation in a single
-   <command>ALTER TABLE</> command is an extension.
-  </para>
-
-  <para>
-   <command>ALTER TABLE DROP COLUMN</> can be used to drop the only
-   column of a table, leaving a zero-column table.  This is an
-   extension of SQL, which disallows zero-column tables.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtable"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_tablespace.sgmlin b/doc-xc/src/sgml/ref/alter_tablespace.sgmlin
deleted file mode 100644
index 720dec1e84..0000000000
--- a/doc-xc/src/sgml/ref/alter_tablespace.sgmlin
+++ /dev/null
@@ -1,137 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_tablespace.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERTABLESPACE">
- <refmeta>
-  <refentrytitle>ALTER TABLESPACE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER TABLESPACE</refname>
-  <refpurpose>change the definition of a tablespace</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altertablespace">
-  <primary>ALTER TABLESPACE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER TABLESPACE <replaceable>name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER TABLESPACE <replaceable>name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-ALTER TABLESPACE <replaceable>name</replaceable> SET ( <replaceable class="PARAMETER">tablespace_option</replaceable> = <replaceable class="PARAMETER">value</replaceable> [, ... ] )
-ALTER TABLESPACE <replaceable>name</replaceable> RESET ( <replaceable class="PARAMETER">tablespace_option</replaceable> [, ... ] )
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER TABLESPACE</command> changes the definition of
-   a tablespace.
-  </para>
-
-  <para>
-   You must own the tablespace to use <command>ALTER TABLESPACE</>.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role.
-   (Note that superusers have these privileges automatically.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing tablespace.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the tablespace.  The new name cannot
-      begin with <literal>pg_</literal>, as such names
-      are reserved for system tablespaces.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the tablespace.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">tablespace_parameter</replaceable></term>
-    <listitem>
-     <para>
-      A tablespace parameter to be set or reset.  Currently, the only
-      available parameters are <varname>seq_page_cost</> and
-      <varname>random_page_cost</>.  Setting either value for a particular
-      tablespace will override the planner's usual estimate of the cost of
-      reading pages from tables in that tablespace, as established by
-      the configuration parameters of the same name (see
-      <xref linkend="guc-seq-page-cost">,
-      <xref linkend="guc-random-page-cost">).  This may be useful if one
-      tablespace is located on a disk which is faster or slower than the
-      remainder of the I/O subsystem.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Rename tablespace <literal>index_space</literal> to <literal>fast_raid</literal>:
-<programlisting>
-ALTER TABLESPACE index_space RENAME TO fast_raid;
-</programlisting>
-  </para>
-
-  <para>
-   Change the owner of tablespace <literal>index_space</literal>:
-<programlisting>
-ALTER TABLESPACE index_space OWNER TO mary;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER TABLESPACE</command> statement in
-   the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtablespace"></member>
-   <member><xref linkend="sql-droptablespace"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_trigger.sgmlin b/doc-xc/src/sgml/ref/alter_trigger.sgmlin
deleted file mode 100644
index 36a9de3096..0000000000
--- a/doc-xc/src/sgml/ref/alter_trigger.sgmlin
+++ /dev/null
@@ -1,133 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_trigger.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERTRIGGER">
- <refmeta>
-  <refentrytitle>ALTER TRIGGER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER TRIGGER</refname>
-  <refpurpose>change the definition of a trigger</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altertrigger">
-  <primary>ALTER TRIGGER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER TRIGGER <replaceable class="PARAMETER">name</replaceable> ON <replaceable class="PARAMETER">table</replaceable> RENAME TO <replaceable class="PARAMETER">new_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>ALTER TRIGGERXS</> statement has not been supported
-   in <productname>Postgres-XC</> yet.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   The <command>ALTER TRIGGER</> statement is not yet supported
-   in <productname>Postgres-XL</>.
-  </para>
-<!## end>
-
-<!## PG>
-
-  <para>
-   <command>ALTER TRIGGER</command> changes properties of an existing
-   trigger.  The <literal>RENAME</literal> clause changes the name of
-   the given trigger without otherwise changing the trigger
-   definition.
-  </para>
-
-  <para>
-   You must own the table on which the trigger acts to be allowed to change its properties.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing trigger to alter.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">table</replaceable></term>
-    <listitem>
-     <para>
-      The name of the table on which this trigger acts.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name for the trigger.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    The ability to temporarily enable or disable a trigger is provided by
-    <xref linkend="SQL-ALTERTABLE">, not by
-    <command>ALTER TRIGGER</>, because <command>ALTER TRIGGER</> has no
-    convenient way to express the option of enabling or disabling all of
-    a table's triggers at once.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To rename an existing trigger:
-<programlisting>
-ALTER TRIGGER emp_stamp ON emp RENAME TO emp_track_chgs;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>ALTER TRIGGER</command> is a <productname>PostgreSQL</>
-   extension of the SQL standard.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertable"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_tsconfig.sgmlin b/doc-xc/src/sgml/ref/alter_tsconfig.sgmlin
deleted file mode 100644
index 25977b731d..0000000000
--- a/doc-xc/src/sgml/ref/alter_tsconfig.sgmlin
+++ /dev/null
@@ -1,191 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_tsconfig.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERTSCONFIG">
- <refmeta>
-  <refentrytitle>ALTER TEXT SEARCH CONFIGURATION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER TEXT SEARCH CONFIGURATION</refname>
-  <refpurpose>change the definition of a text search configuration</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altertsconfig">
-  <primary>ALTER TEXT SEARCH CONFIGURATION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER TEXT SEARCH CONFIGURATION <replaceable>name</replaceable>
-    ADD MAPPING FOR <replaceable class="parameter">token_type</replaceable> [, ... ] WITH <replaceable class="parameter">dictionary_name</replaceable> [, ... ]
-ALTER TEXT SEARCH CONFIGURATION <replaceable>name</replaceable>
-    ALTER MAPPING FOR <replaceable class="parameter">token_type</replaceable> [, ... ] WITH <replaceable class="parameter">dictionary_name</replaceable> [, ... ]
-ALTER TEXT SEARCH CONFIGURATION <replaceable>name</replaceable>
-    ALTER MAPPING REPLACE <replaceable class="parameter">old_dictionary</replaceable> WITH <replaceable class="parameter">new_dictionary</replaceable>
-ALTER TEXT SEARCH CONFIGURATION <replaceable>name</replaceable>
-    ALTER MAPPING FOR <replaceable class="parameter">token_type</replaceable> [, ... ] REPLACE <replaceable class="parameter">old_dictionary</replaceable> WITH <replaceable class="parameter">new_dictionary</replaceable>
-ALTER TEXT SEARCH CONFIGURATION <replaceable>name</replaceable>
-    DROP MAPPING [ IF EXISTS ] FOR <replaceable class="parameter">token_type</replaceable> [, ... ]
-ALTER TEXT SEARCH CONFIGURATION <replaceable>name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER TEXT SEARCH CONFIGURATION <replaceable>name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-ALTER TEXT SEARCH CONFIGURATION <replaceable>name</replaceable> SET SCHEMA <replaceable>new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER TEXT SEARCH CONFIGURATION</command> changes the definition of
-   a text search configuration.  You can modify
-   its mappings from token types to dictionaries,
-   or change the configuration's name or owner.
-  </para>
-
-  <para>
-   You must be the owner of the configuration to use
-   <command>ALTER TEXT SEARCH CONFIGURATION</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing text search
-      configuration.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">token_type</replaceable></term>
-    <listitem>
-     <para>
-      The name of a token type that is emitted by the configuration's
-      parser.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">dictionary_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of a text search dictionary to be consulted for the
-      specified token type(s).  If multiple dictionaries are listed,
-      they are consulted in the specified order.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">old_dictionary</replaceable></term>
-    <listitem>
-     <para>
-      The name of a text search dictionary to be replaced in the mapping.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_dictionary</replaceable></term>
-    <listitem>
-     <para>
-      The name of a text search dictionary to be substituted for
-      <replaceable class="parameter">old_dictionary</replaceable>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the text search configuration.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the text search configuration.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the text search configuration.
-     </para>
-    </listitem>
-   </varlistentry>
- </variablelist>
-
-  <para>
-   The <literal>ADD MAPPING FOR</> form installs a list of dictionaries to be
-   consulted for the specified token type(s); it is an error if there is
-   already a mapping for any of the token types.
-   The <literal>ALTER MAPPING FOR</> form does the same, but first removing
-   any existing mapping for those token types.
-   The <literal>ALTER MAPPING REPLACE</> forms substitute <replaceable
-   class="parameter">new_dictionary</replaceable> for <replaceable
-   class="parameter">old_dictionary</replaceable> anywhere the latter appears.
-   This is done for only the specified token types when <literal>FOR</>
-   appears, or for all mappings of the configuration when it doesn't.
-   The <literal>DROP MAPPING</> form removes all dictionaries for the
-   specified token type(s), causing tokens of those types to be ignored
-   by the text search configuration.  It is an error if there is no mapping
-   for the token types, unless <literal>IF EXISTS</> appears.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   The following example replaces the <literal>english</> dictionary
-   with the <literal>swedish</> dictionary anywhere that <literal>english</>
-   is used within <literal>my_config</>.
-  </para>
-
-<programlisting>
-ALTER TEXT SEARCH CONFIGURATION my_config
-  ALTER MAPPING REPLACE english WITH swedish;
-</programlisting>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER TEXT SEARCH CONFIGURATION</command> statement in
-   the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtsconfig"></member>
-   <member><xref linkend="sql-droptsconfig"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_tsdictionary.sgmlin b/doc-xc/src/sgml/ref/alter_tsdictionary.sgmlin
deleted file mode 100644
index 91046dcae5..0000000000
--- a/doc-xc/src/sgml/ref/alter_tsdictionary.sgmlin
+++ /dev/null
@@ -1,172 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_tsdictionary.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERTSDICTIONARY">
- <refmeta>
-  <refentrytitle>ALTER TEXT SEARCH DICTIONARY</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER TEXT SEARCH DICTIONARY</refname>
-  <refpurpose>change the definition of a text search dictionary</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altertsdictionary">
-  <primary>ALTER TEXT SEARCH DICTIONARY</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER TEXT SEARCH DICTIONARY <replaceable>name</replaceable> (
-    <replaceable class="parameter">option</replaceable> [ = <replaceable class="parameter">value</replaceable> ] [, ... ]
-)
-ALTER TEXT SEARCH DICTIONARY <replaceable>name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER TEXT SEARCH DICTIONARY <replaceable>name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
-ALTER TEXT SEARCH DICTIONARY <replaceable>name</replaceable> SET SCHEMA <replaceable>new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER TEXT SEARCH DICTIONARY</command> changes the definition of
-   a text search dictionary.  You can change the dictionary's
-   template-specific options, or change the dictionary's name or owner.
-  </para>
-
-  <para>
-   You must be the owner of the dictionary to use
-   <command>ALTER TEXT SEARCH DICTIONARY</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing text search
-      dictionary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">option</replaceable></term>
-    <listitem>
-     <para>
-      The name of a template-specific option to be set for this dictionary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">value</replaceable></term>
-    <listitem>
-     <para>
-      The new value to use for a template-specific option.
-      If the equal sign and value are omitted, then any previous
-      setting for the option is removed from the dictionary,
-      allowing the default to be used.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the text search dictionary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The new owner of the text search dictionary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the text search dictionary.
-     </para>
-    </listitem>
-   </varlistentry>
- </variablelist>
-
-  <para>
-   Template-specific options can appear in any order.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   The following example command changes the stopword list
-   for a Snowball-based dictionary.  Other parameters remain unchanged.
-  </para>
-
-<programlisting>
-ALTER TEXT SEARCH DICTIONARY my_dict ( StopWords = newrussian );
-</programlisting>
-
-  <para>
-   The following example command changes the language option to dutch,
-   and removes the stopword option entirely.
-  </para>
-
-<programlisting>
-ALTER TEXT SEARCH DICTIONARY my_dict ( language = dutch, StopWords );
-</programlisting>
-
-  <para>
-   The following example command <quote>updates</> the dictionary's
-   definition without actually changing anything.
-
-<programlisting>
-ALTER TEXT SEARCH DICTIONARY my_dict ( dummy );
-</programlisting>
-
-   (The reason this works is that the option removal code doesn't complain
-   if there is no such option.)  This trick is useful when changing
-   configuration files for the dictionary: the <command>ALTER</> will
-   force existing database sessions to re-read the configuration files,
-   which otherwise they would never do if they had read them earlier.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER TEXT SEARCH DICTIONARY</command> statement in
-   the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtsdictionary"></member>
-   <member><xref linkend="sql-droptsdictionary"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_tsparser.sgmlin b/doc-xc/src/sgml/ref/alter_tsparser.sgmlin
deleted file mode 100644
index 7119c4553e..0000000000
--- a/doc-xc/src/sgml/ref/alter_tsparser.sgmlin
+++ /dev/null
@@ -1,95 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_tsparser.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERTSPARSER">
- <refmeta>
-  <refentrytitle>ALTER TEXT SEARCH PARSER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER TEXT SEARCH PARSER</refname>
-  <refpurpose>change the definition of a text search parser</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altertsparser">
-  <primary>ALTER TEXT SEARCH PARSER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER TEXT SEARCH PARSER <replaceable>name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER TEXT SEARCH PARSER <replaceable>name</replaceable> SET SCHEMA <replaceable>new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER TEXT SEARCH PARSER</command> changes the definition of
-   a text search parser.  Currently, the only supported functionality
-   is to change the parser's name.
-  </para>
-
-  <para>
-   You must be a superuser to use <command>ALTER TEXT SEARCH PARSER</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing text search parser.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the text search parser.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the text search parser.
-     </para>
-    </listitem>
-   </varlistentry>
- </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER TEXT SEARCH PARSER</command> statement in
-   the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtsparser"></member>
-   <member><xref linkend="sql-droptsparser"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_tstemplate.sgmlin b/doc-xc/src/sgml/ref/alter_tstemplate.sgmlin
deleted file mode 100644
index 9267042d5c..0000000000
--- a/doc-xc/src/sgml/ref/alter_tstemplate.sgmlin
+++ /dev/null
@@ -1,93 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_tstemplate.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERTSTEMPLATE">
- <refmeta>
-  <refentrytitle>ALTER TEXT SEARCH TEMPLATE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER TEXT SEARCH TEMPLATE</refname>
-  <refpurpose>change the definition of a text search template</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altertstemplate">
-  <primary>ALTER TEXT SEARCH TEMPLATE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER TEXT SEARCH TEMPLATE <replaceable>name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-ALTER TEXT SEARCH TEMPLATE <replaceable>name</replaceable> SET SCHEMA <replaceable>new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-&common;
-  <para>
-   <command>ALTER TEXT SEARCH TEMPLATE</command> changes the definition of
-   a text search template.  Currently, the only supported functionality
-   is to change the template's name.
-  </para>
-
-  <para>
-   You must be a superuser to use <command>ALTER TEXT SEARCH TEMPLATE</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing text search template.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name of the text search template.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the text search template.
-     </para>
-    </listitem>
-   </varlistentry>
- </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ALTER TEXT SEARCH TEMPLATE</command> statement in
-   the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtstemplate"></member>
-   <member><xref linkend="sql-droptstemplate"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_type.sgmlin b/doc-xc/src/sgml/ref/alter_type.sgmlin
deleted file mode 100644
index 16a2060709..0000000000
--- a/doc-xc/src/sgml/ref/alter_type.sgmlin
+++ /dev/null
@@ -1,339 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_type.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERTYPE">
- <refmeta>
-  <refentrytitle>ALTER TYPE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER TYPE</refname>
-  <refpurpose>
-   change the definition of a type
-  </refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-altertype">
-  <primary>ALTER TYPE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER TYPE <replaceable class="PARAMETER">name</replaceable> <replaceable class="PARAMETER">action</replaceable> [, ... ]
-ALTER TYPE <replaceable class="PARAMETER">name</replaceable> OWNER TO <replaceable class="PARAMETER">new_owner</replaceable>
-ALTER TYPE <replaceable class="PARAMETER">name</replaceable> RENAME ATTRIBUTE <replaceable class="PARAMETER">attribute_name</replaceable> TO <replaceable class="PARAMETER">new_attribute_name</replaceable>
-ALTER TYPE <replaceable class="PARAMETER">name</replaceable> RENAME TO <replaceable class="PARAMETER">new_name</replaceable> [ CASCADE | RESTRICT ]
-ALTER TYPE <replaceable class="PARAMETER">name</replaceable> SET SCHEMA <replaceable class="PARAMETER">new_schema</replaceable>
-ALTER TYPE <replaceable class="PARAMETER">name</replaceable> ADD VALUE <replaceable class="PARAMETER">new_enum_value</replaceable> [ { BEFORE | AFTER } <replaceable class="PARAMETER">existing_enum_value</replaceable> ]
-
-<phrase>where <replaceable class="PARAMETER">action</replaceable> is one of:</phrase>
-
-    ADD ATTRIBUTE <replaceable class="PARAMETER">attribute_name</replaceable> <replaceable class="PARAMETER">data_type</replaceable> [ COLLATE <replaceable class="PARAMETER">collation</replaceable> ] [ CASCADE | RESTRICT ]
-    DROP ATTRIBUTE [ IF EXISTS ] <replaceable class="PARAMETER">attribute_name</replaceable> [ CASCADE | RESTRICT ]
-    ALTER ATTRIBUTE <replaceable class="PARAMETER">attribute_name</replaceable> [ SET DATA ] TYPE <replaceable class="PARAMETER">data_type</replaceable> [ COLLATE <replaceable class="PARAMETER">collation</replaceable> ] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER TYPE</command> changes the definition of an existing type.
-   There are several subforms:
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>ADD ATTRIBUTE</literal></term>
-    <listitem>
-     <para>
-      This form adds a new attribute to a composite type, using the same syntax as
-      <xref linkend="SQL-CREATETYPE">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DROP ATTRIBUTE [ IF EXISTS ]</literal></term>
-    <listitem>
-     <para>
-      This form drops an attribute from a composite type.
-      If <literal>IF EXISTS</literal> is specified and the attribute
-      does not exist, no error is thrown. In this case a notice
-      is issued instead.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET DATA TYPE</literal></term>
-    <listitem>
-     <para>
-      This form changes the type of an attribute of a composite type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OWNER</literal></term>
-    <listitem>
-     <para>
-      This form changes the owner of the type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RENAME</literal></term>
-    <listitem>
-     <para>
-      This form changes the name of the type or the name of an
-      individual attribute of a composite type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET SCHEMA</literal></term>
-    <listitem>
-     <para>
-      This form moves the type into another schema.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ADD VALUE [ BEFORE | AFTER ]</literal></term>
-    <listitem>
-     <para>
-      This form adds a new value to an enum type. If the new value's place in
-      the enum's ordering is not specified using <literal>BEFORE</literal> or
-      <literal>AFTER</literal>, then the new item is placed at the end of the
-      list of values.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically propagate the operation to typed tables of the
-      type being altered, and their descendants.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse the operation if the type being altered is the type of a
-      typed table.  This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-  </para>
-
-  <para>
-   The <literal>ADD ATTRIBUTE</literal>, <literal>DROP
-   ATTRIBUTE</literal>, and <literal>ALTER ATTRIBUTE</literal> actions
-   can be combined into a list of multiple alterations to apply in
-   parallel.  For example, it is possible to add several attributes
-   and/or alter the type of several attributes in a single command.
-  </para>
-
-  <para>
-   You must own the type to use <command>ALTER TYPE</>.
-   To change the schema of a type, you must also have
-   <literal>CREATE</literal> privilege on the new schema.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the type's schema.  (These restrictions enforce that altering the owner
-   doesn't do anything you couldn't do by dropping and recreating the type.
-   However, a superuser can alter ownership of any type anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-        The name (possibly schema-qualified) of an existing type to
-        alter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_name</replaceable></term>
-      <listitem>
-       <para>
-        The new name for the type.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_owner</replaceable></term>
-      <listitem>
-       <para>
-        The user name of the new owner of the type.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_schema</replaceable></term>
-      <listitem>
-       <para>
-        The new schema for the type.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">attribute_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the attribute to add, alter, or drop.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_attribute_name</replaceable></term>
-      <listitem>
-       <para>
-        The new name of the attribute to be renamed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">data_type</replaceable></term>
-      <listitem>
-       <para>
-        The data type of the attribute to add, or the new type of the
-        attribute to alter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">new_enum_value</replaceable></term>
-      <listitem>
-       <para>
-        The new value to be added to an enum type's list of values.
-        Like all enum literals, it needs to be quoted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">existing_enum_value</replaceable></term>
-      <listitem>
-       <para>
-        The existing enum value that the new value should be added immediately
-        before or after in the enum type's sort ordering.
-        Like all enum literals, it needs to be quoted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <command>ALTER TYPE ... ADD VALUE</> (the form that adds a new value to an
-   enum type) cannot be executed inside a transaction block.
-  </para>
-
-  <para>
-   Comparisons involving an added enum value will sometimes be slower than
-   comparisons involving only original members of the enum type.  This will
-   usually only occur if <literal>BEFORE</literal> or <literal>AFTER</literal>
-   is used to set the new value's sort position somewhere other than at the
-   end of the list.  However, sometimes it will happen even though the new
-   value is added at the end (this occurs if the OID counter <quote>wrapped
-   around</> since the original creation of the enum type).  The slowdown is
-   usually insignificant; but if it matters, optimal performance can be
-   regained by dropping and recreating the enum type, or by dumping and
-   reloading the database.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To rename a data type:
-<programlisting>
-ALTER TYPE electronic_mail RENAME TO email;
-</programlisting>
-  </para>
-
-  <para>
-   To change the owner of the type <literal>email</literal>
-   to <literal>joe</literal>:
-<programlisting>
-ALTER TYPE email OWNER TO joe;
-</programlisting>
-  </para>
-
-  <para>
-   To change the schema of the type <literal>email</literal>
-   to <literal>customers</literal>:
-<programlisting>
-ALTER TYPE email SET SCHEMA customers;
-</programlisting>
-  </para>
-
-  <para>
-   To add a new attribute to a type:
-<programlisting>
-ALTER TYPE compfoo ADD ATTRIBUTE f3 int;
-</programlisting>
-  </para>
-
-  <para>
-   To add a new value to an enum type in a particular sort position:
-<programlisting>
-ALTER TYPE colors ADD VALUE 'orange' AFTER 'red';
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The variants to add and drop attributes are part of the SQL
-   standard; the other variants are PostgreSQL extensions.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-ALTERTYPE-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtype"></member>
-   <member><xref linkend="sql-droptype"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_user.sgmlin b/doc-xc/src/sgml/ref/alter_user.sgmlin
deleted file mode 100644
index 2ffd166ddb..0000000000
--- a/doc-xc/src/sgml/ref/alter_user.sgmlin
+++ /dev/null
@@ -1,84 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_user.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERUSER">
- <refmeta>
-  <refentrytitle>ALTER USER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER USER</refname>
-  <refpurpose>change a database role</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alteruser">
-  <primary>ALTER USER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER USER <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replaceable class="PARAMETER">option</replaceable> [ ... ] ]
-
-<phrase>where <replaceable class="PARAMETER">option</replaceable> can be:</phrase>
-
-      SUPERUSER | NOSUPERUSER
-    | CREATEDB | NOCREATEDB
-    | CREATEROLE | NOCREATEROLE
-    | CREATEUSER | NOCREATEUSER
-    | INHERIT | NOINHERIT
-    | LOGIN | NOLOGIN
-    | REPLICATION | NOREPLICATION
-    | CONNECTION LIMIT <replaceable class="PARAMETER">connlimit</replaceable>
-    | [ ENCRYPTED | UNENCRYPTED ] PASSWORD '<replaceable class="PARAMETER">password</replaceable>'
-    | VALID UNTIL '<replaceable class="PARAMETER">timestamp</replaceable>'
-
-ALTER USER <replaceable class="PARAMETER">name</replaceable> RENAME TO <replaceable>new_name</replaceable>
-
-ALTER USER <replaceable class="PARAMETER">name</replaceable> SET <replaceable>configuration_parameter</replaceable> { TO | = } { <replaceable>value</replaceable> | DEFAULT }
-ALTER USER <replaceable class="PARAMETER">name</replaceable> SET <replaceable>configuration_parameter</replaceable> FROM CURRENT
-ALTER USER <replaceable class="PARAMETER">name</replaceable> RESET <replaceable>configuration_parameter</replaceable>
-ALTER USER <replaceable class="PARAMETER">name</replaceable> RESET ALL
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER USER</command> is now an alias for
-   <xref linkend="sql-alterrole">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The <command>ALTER USER</command> statement is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.  The SQL standard
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.  The SQL standard
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.  The SQL standard
-<!## end>
-   leaves the definition of users to the implementation.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterrole"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_user_mapping.sgmlin b/doc-xc/src/sgml/ref/alter_user_mapping.sgmlin
deleted file mode 100644
index 936041b64d..0000000000
--- a/doc-xc/src/sgml/ref/alter_user_mapping.sgmlin
+++ /dev/null
@@ -1,145 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_user_mapping.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERUSERMAPPING">
- <refmeta>
-  <refentrytitle>ALTER USER MAPPING</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER USER MAPPING</refname>
-  <refpurpose>change the definition of a user mapping</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterusermapping">
-  <primary>ALTER USER MAPPING</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER USER MAPPING FOR { <replaceable class="parameter">user_name</replaceable> | USER | CURRENT_USER | PUBLIC }
-    SERVER <replaceable class="parameter">server_name</replaceable>
-    OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">value</replaceable>'] [, ... ] )
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-<!## XC>
-&xconly;
-  <para>
-   <command>USER MAPPING</> has not been supported
-   by <productname>Postgres-XC</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>USER MAPPING</> is not yet supported
-   in <productname>Postgres-XL</>.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-&pgonly;
-
-  <para>
-   <command>ALTER USER MAPPING</command> changes the definition of a
-   user mapping.
-  </para>
-
-  <para>
-   The owner of a foreign server can alter user mappings for that
-   server for any user.  Also, a user can alter a user mapping for
-   his own user name if <literal>USAGE</> privilege on the server has
-   been granted to the user.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">user_name</replaceable></term>
-    <listitem>
-     <para>
-      User name of the mapping. <literal>CURRENT_USER</>
-      and <literal>USER</> match the name of the current
-      user. <literal>PUBLIC</> is used to match all present and future
-      user names in the system.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">server_name</replaceable></term>
-    <listitem>
-     <para>
-      Server name of the user mapping.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">value</replaceable>'] [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      Change options for the user mapping. The new options override
-      any previously specified
-      options.  <literal>ADD</>, <literal>SET</>, and <literal>DROP</>
-      specify the action to be performed.  <literal>ADD</> is assumed
-      if no operation is explicitly specified.  Option names must be
-      unique; options are also validated by the server's foreign-data
-      wrapper.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Change the password for user mapping <literal>bob</>, server<literal> foo</>:
-<programlisting>
-ALTER USER MAPPING FOR bob SERVER foo OPTIONS (user 'bob', password 'public');
-</programlisting>
-  </para>
-
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>ALTER USER MAPPING</command> conforms to ISO/IEC 9075-9
-   (SQL/MED).  There is a subtle syntax issue: The standard omits
-   the <literal>FOR</literal> key word.  Since both <literal>CREATE
-   USER MAPPING</literal> and <literal>DROP USER MAPPING</literal> use
-   <literal>FOR</literal> in analogous positions, and IBM DB2 (being
-   the other major SQL/MED implementation) also requires it
-   for <literal>ALTER USER MAPPING</literal>, PostgreSQL diverges from
-   the standard here in the interest of consistency and
-   interoperability.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createusermapping"></member>
-   <member><xref linkend="sql-dropusermapping"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/alter_view.sgmlin b/doc-xc/src/sgml/ref/alter_view.sgmlin
deleted file mode 100644
index 8c19671265..0000000000
--- a/doc-xc/src/sgml/ref/alter_view.sgmlin
+++ /dev/null
@@ -1,157 +0,0 @@
-<!--
-doc/src/sgml/ref/alter_view.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERVIEW">
- <refmeta>
-  <refentrytitle>ALTER VIEW</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER VIEW</refname>
-  <refpurpose>change the definition of a view</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-alterview">
-  <primary>ALTER VIEW</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER VIEW <replaceable class="parameter">name</replaceable> ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> SET DEFAULT <replaceable class="PARAMETER">expression</replaceable>
-ALTER VIEW <replaceable class="parameter">name</replaceable> ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> DROP DEFAULT
-ALTER VIEW <replaceable class="parameter">name</replaceable> OWNER TO <replaceable class="PARAMETER">new_owner</replaceable>
-ALTER VIEW <replaceable class="parameter">name</replaceable> RENAME TO <replaceable class="parameter">new_name</replaceable>
-ALTER VIEW <replaceable class="parameter">name</replaceable> SET SCHEMA <replaceable class="parameter">new_schema</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ALTER VIEW</command> changes various auxiliary properties
-   of a view.  (If you want to modify the view's defining query,
-   use <command>CREATE OR REPLACE VIEW</>.)
-  </para>
-
-  <para>
-   You must own the view to use <command>ALTER VIEW</>.
-   To change a view's schema, you must also have <literal>CREATE</>
-   privilege on the new schema.
-   To alter the owner, you must also be a direct or indirect member of the new
-   owning role, and that role must have <literal>CREATE</literal> privilege on
-   the view's schema.  (These restrictions enforce that altering the owner
-   doesn't do anything you couldn't do by dropping and recreating the view.
-   However, a superuser can alter ownership of any view anyway.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing view.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SET</literal>/<literal>DROP DEFAULT</literal></term>
-    <listitem>
-     <para>
-      These forms set or remove the default value for a column.
-      A default value associated with a view column is
-      inserted into <command>INSERT</> statements on the view before
-      the view's <literal>ON INSERT</literal> rule is applied, if
-      the <command>INSERT</> does not specify a value for the column.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">new_owner</replaceable></term>
-    <listitem>
-     <para>
-      The user name of the new owner of the view.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_name</replaceable></term>
-    <listitem>
-     <para>
-      The new name for the view.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">new_schema</replaceable></term>
-    <listitem>
-     <para>
-      The new schema for the view.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   For historical reasons, <command>ALTER TABLE</command> can be used with
-   views too; but the only variants of <command>ALTER TABLE</command>
-   that are allowed with views are equivalent to the ones shown above.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To rename the view <literal>foo</literal> to
-   <literal>bar</literal>:
-<programlisting>
-ALTER VIEW foo RENAME TO bar;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-<!## PG>
-   <command>ALTER VIEW</command> is a <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-   <command>ALTER VIEW</command> is a <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-   <command>ALTER VIEW</command> is a <productname>Postgres-XL</>
-<!## end>
-   extension of the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createview"></member>
-   <member><xref linkend="sql-dropview"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/analyze.sgmlin b/doc-xc/src/sgml/ref/analyze.sgmlin
deleted file mode 100644
index fd27fd0935..0000000000
--- a/doc-xc/src/sgml/ref/analyze.sgmlin
+++ /dev/null
@@ -1,212 +0,0 @@
-<!--
-doc/src/sgml/ref/analyze.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ANALYZE">
- <refmeta>
-  <refentrytitle>ANALYZE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ANALYZE</refname>
-  <refpurpose>collect statistics about a database</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-analyze">
-  <primary>ANALYZE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ ( <replaceable class="PARAMETER">column</replaceable> [, ...] ) ] ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>ANALYZE</command> collects statistics about the contents
-   of tables in the database, and stores the results in the <link
-   linkend="catalog-pg-statistic"><structname>pg_statistic</></>
-   system catalog.  Subsequently, the query planner uses these
-   statistics to help determine the most efficient execution plans for
-   queries.
-  </para>
-
-  <para>
-   With no parameter, <command>ANALYZE</command> examines every table in the
-   current database.  With a parameter, <command>ANALYZE</command> examines
-   only that table.  It is further possible to give a list of column names,
-   in which case only the statistics for those columns are collected.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>VERBOSE</literal></term>
-    <listitem>
-     <para>
-      Enables display of progress messages.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">table</replaceable></term>
-    <listitem>
-     <para>
-      The name (possibly schema-qualified) of a specific table to
-      analyze. Defaults to all tables in the current database.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">column</replaceable></term>
-    <listitem>
-     <para>
-      The name of a specific column to analyze. Defaults to all columns.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Outputs</title>
-
-   <para>
-    When <literal>VERBOSE</> is specified, <command>ANALYZE</> emits
-    progress messages to indicate which table is currently being
-    processed.  Various statistics about the tables are printed as well.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   In the default <productname>PostgreSQL</productname> configuration,
-   the autovacuum daemon (see <xref linkend="autovacuum">)
-   takes care of automatic analyzing of tables when they are first loaded
-   with data, and as they change throughout regular operation.
-   When autovacuum is disabled,
-   it is a good idea to run <command>ANALYZE</command> periodically, or
-   just after making major changes in the contents of a table.  Accurate
-   statistics will help the planner to choose the most appropriate query
-   plan, and thereby improve the speed of query processing.  A common
-   strategy is to run <xref linkend="sql-vacuum">
-   and <command>ANALYZE</command> once a day during a low-usage time of day.
-  </para>
-
-  <para>
-   <command>ANALYZE</command>
-   requires only a read lock on the target table, so it can run in
-   parallel with other activity on the table.
-  </para>
-
-  <para>
-   The statistics collected by <command>ANALYZE</command> usually
-   include a list of some of the most common values in each column and
-   a histogram showing the approximate data distribution in each
-   column.  One or both of these can be omitted if
-   <command>ANALYZE</command> deems them uninteresting (for example,
-   in a unique-key column, there are no common values) or if the
-   column data type does not support the appropriate operators.  There
-   is more information about the statistics in <xref
-   linkend="maintenance">.
-  </para>
-
-  <para>
-   For large tables, <command>ANALYZE</command> takes a random sample
-   of the table contents, rather than examining every row.  This
-   allows even very large tables to be analyzed in a small amount of
-   time.  Note, however, that the statistics are only approximate, and
-   will change slightly each time <command>ANALYZE</command> is run,
-   even if the actual table contents did not change.  This might result
-   in small changes in the planner's estimated costs shown by
-   <xref linkend="sql-explain">.
-   In rare situations, this non-determinism will cause the planner's
-   choices of query plans to change after <command>ANALYZE</command> is run.
-   To avoid this, raise the amount of statistics collected by
-   <command>ANALYZE</command>, as described below.
-  </para>
-
-  <para>
-   The extent of analysis can be controlled by adjusting the
-   <xref linkend="guc-default-statistics-target"> configuration variable, or
-   on a column-by-column basis by setting the per-column statistics
-   target with <command>ALTER TABLE ... ALTER COLUMN ... SET
-   STATISTICS</command> (see <xref linkend="sql-altertable">).
-   The target value sets the
-   maximum number of entries in the most-common-value list and the
-   maximum number of bins in the histogram.  The default target value
-   is 100, but this can be adjusted up or down to trade off accuracy of
-   planner estimates against the time taken for
-   <command>ANALYZE</command> and the amount of space occupied in
-   <literal>pg_statistic</literal>.  In particular, setting the
-   statistics target to zero disables collection of statistics for
-   that column.  It might be useful to do that for columns that are
-   never used as part of the <literal>WHERE</>, <literal>GROUP BY</>,
-   or <literal>ORDER BY</> clauses of queries, since the planner will
-   have no use for statistics on such columns.
-  </para>
-
-  <para>
-   The largest statistics target among the columns being analyzed determines
-   the number of table rows sampled to prepare the statistics.  Increasing
-   the target causes a proportional increase in the time and space needed
-   to do <command>ANALYZE</command>.
-  </para>
-
-  <para>
-   One of the values estimated by <command>ANALYZE</command> is the number of
-   distinct values that appear in each column.  Because only a subset of the
-   rows are examined, this estimate can sometimes be quite inaccurate, even
-   with the largest possible statistics target.  If this inaccuracy leads to
-   bad query plans, a more accurate value can be determined manually and then
-   installed with
-   <command>ALTER TABLE ... ALTER COLUMN ... SET (n_distinct = ...)</>
-   (see <xref linkend="sql-altertable">).
-  </para>
-
-  <para>
-    If the table being analyzed has one or more children,
-    <command>ANALYZE</command> will gather statistics twice: once on the
-    rows of the parent table only, and a second time on the rows of the
-    parent table with all of its children.  The autovacuum daemon, however,
-    will only consider inserts or updates on the parent table when deciding
-    whether to trigger an automatic analyze.  If that table is rarely
-    inserted into or updated, the inheritance statistics will not be up to date
-    unless you run <command>ANALYZE</command> manually.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>ANALYZE</command> statement in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-vacuum"></member>
-   <member><xref linkend="app-vacuumdb"></member>
-   <member><xref linkend="runtime-config-resource-vacuum-cost"></member>
-   <member><xref linkend="autovacuum"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/begin.sgmlin b/doc-xc/src/sgml/ref/begin.sgmlin
deleted file mode 100644
index e4581503b5..0000000000
--- a/doc-xc/src/sgml/ref/begin.sgmlin
+++ /dev/null
@@ -1,178 +0,0 @@
-<!--
-doc/src/sgml/ref/begin.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-BEGIN">
- <refmeta>
-  <refentrytitle>BEGIN</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>BEGIN</refname>
-  <refpurpose>start a transaction block</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-begin">
-  <primary>BEGIN</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-BEGIN [ WORK | TRANSACTION ] [ <replaceable class="parameter">transaction_mode</replaceable> [, ...] ]
-
-<phrase>where <replaceable class="parameter">transaction_mode</replaceable> is one of:</phrase>
-
-    ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED }
-    READ WRITE | READ ONLY
-    [ NOT ] DEFERRABLE
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-&common;
-  <para>
-   <command>BEGIN</command> initiates a transaction block, that is,
-   all statements after a <command>BEGIN</command> command will be
-   executed in a single transaction until an explicit <xref
-   linkend="sql-commit"> or <xref
-   linkend="sql-rollback"> is given.
-   By default (without <command>BEGIN</command>),
-<!## PG>
-   <productname>PostgreSQL</productname> executes
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> executes
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> executes
-<!## end>
-   transactions in <quote>autocommit</quote> mode, that is, each
-   statement is executed in its own transaction and a commit is
-   implicitly performed at the end of the statement (if execution was
-   successful, otherwise a rollback is done).
-  </para>
-
-  <para>
-   Statements are executed more quickly in a transaction block, because
-   transaction start/commit requires significant CPU and disk
-   activity. Execution of multiple statements inside a transaction is
-   also useful to ensure consistency when making several related changes:
-   other sessions will be unable to see the intermediate states
-   wherein not all the related updates have been done.
-  </para>
-
-  <para>
-   If the isolation level, read/write mode, or deferrable mode is specified, the new
-   transaction has those characteristics, as if
-   <xref linkend="sql-set-transaction">
-   was executed.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>WORK</literal></term>
-    <term><literal>TRANSACTION</literal></term>
-    <listitem>
-     <para>
-      Optional key words. They have no effect.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   Refer to <xref linkend="sql-set-transaction"> for information on the meaning
-   of the other parameters to this statement.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <xref linkend="sql-start-transaction"> has the same functionality
-   as <command>BEGIN</>.
-  </para>
-
-  <para>
-   Use <xref linkend="SQL-COMMIT"> or
-   <xref linkend="SQL-ROLLBACK">
-   to terminate a transaction block.
-  </para>
-
-  <para>
-   Issuing <command>BEGIN</> when already inside a transaction block will
-   provoke a warning message.  The state of the transaction is not affected.
-   To nest transactions within a transaction block, use savepoints
-   (see <xref linkend="sql-savepoint">).
-  </para>
-
-  <para>
-   For reasons of backwards compatibility, the commas between successive
-   <replaceable class="parameter">transaction_modes</replaceable> can be
-   omitted.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To begin a transaction block:
-
-<programlisting>
-BEGIN;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-<!## PG>
-   <command>BEGIN</command> is a <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   <command>BEGIN</command> is a <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   <command>BEGIN</command> is a <productname>Postgres-XL</productname>
-<!## end>
-   language extension.  It is equivalent to the SQL-standard command
-   <xref linkend="sql-start-transaction">, whose reference page
-   contains additional compatibility information.
-  </para>
-
-  <para>
-   The <literal>DEFERRABLE</literal>
-   <replaceable class="parameter">transaction_mode</replaceable>
-   is a <productname>PostgreSQL</productname> language extension.
-  </para>
-
-  <para>
-   Incidentally, the <literal>BEGIN</literal> key word is used for a
-   different purpose in embedded SQL. You are advised to be careful
-   about the transaction semantics when porting database applications.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-commit"></member>
-   <member><xref linkend="sql-rollback"></member>
-   <member><xref linkend="sql-start-transaction"></member>
-   <member><xref linkend="sql-savepoint"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/checkpoint.sgmlin b/doc-xc/src/sgml/ref/checkpoint.sgmlin
deleted file mode 100644
index e673147f48..0000000000
--- a/doc-xc/src/sgml/ref/checkpoint.sgmlin
+++ /dev/null
@@ -1,80 +0,0 @@
-<!-- doc/src/sgml/ref/checkpoint.sgml -->
-
-<refentry id="sql-checkpoint">
- <refmeta>
-  <refentrytitle>CHECKPOINT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CHECKPOINT</refname>
-  <refpurpose>force a transaction log checkpoint</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-checkpoint">
-  <primary>CHECKPOINT</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CHECKPOINT
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   Write-Ahead Logging (WAL) puts a checkpoint in the transaction log
-   every so often. (To adjust the automatic checkpoint interval, see
-   the run-time configuration options <xref linkend="guc-checkpoint-segments">
-   and <xref linkend="guc-checkpoint-timeout">.)  The
-   <command>CHECKPOINT</command> command forces an immediate
-   checkpoint when the command is issued, without waiting for a
-   scheduled checkpoint.
-  </para>
-
-  <para>
-   A checkpoint is a point in the transaction log sequence at which
-   all data files have been updated to reflect the information in the
-   log.  All data files will be flushed to disk.  Refer to
-   <xref linkend="wal"> for more information about the WAL system.
-  </para>
-
-  <para>
-   If executed during recovery, the <command>CHECKPOINT</command> command
-   will force a restartpoint rather than writing a new checkpoint.
-  </para>
-
-  <para>
-   Only superusers can call <command>CHECKPOINT</command>.  The command is
-   not intended for use during normal operation.
-  </para>
-<!## XC>
-&xconly;
-  <para>
-   In <productname>Postrgres-XC</>, <command>CHECKPOINT</> is
-   performed at local Coordinator and allthe underlying Datanodes.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   In <productname>Postrgres-XL</>, <command>CHECKPOINT</> is
-   performed at local Coordinator and all of the underlying Datanodes.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The <command>CHECKPOINT</command> command is a
-   <productname>PostgreSQL</productname> language extension.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/clean_connection.sgmlin b/doc-xc/src/sgml/ref/clean_connection.sgmlin
deleted file mode 100644
index f2c75ef17d..0000000000
--- a/doc-xc/src/sgml/ref/clean_connection.sgmlin
+++ /dev/null
@@ -1,144 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/clean_connection.sgml,v 1.50 2010/04/03 07:22:59 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CLEANCONNECTION">
- <refmeta>
-  <refentrytitle>CLEAN CONNECTION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CLEAN CONNECTION</refname>
-  <refpurpose>Clean up pooler connections in a cluster</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-cleanconnection">
-  <primary>CLEAN CONNECTION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CLEAN CONNECTION TO { COORDINATOR ( <replaceable class="parameter">nodename</replaceable> [, ... ] ) | NODE ( <replaceable class="parameter">nodename</replaceable> [, ... ] ) | ALL {FORCE} }
-    [ FOR DATABASE <replaceable class="parameter">dbname</replaceable> ]
-    [ TO USER <replaceable class="parameter">username</replaceable> ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-&xlonly;
-  <para>
-   <command>CLEAN CONNECTION</command> cleans pooler connections in
-   a Postgres-XL cluster.  This can be done for a given database or
-   role. This command's usage is restricted to superusers.  It is
-   possible to clean connections to a list of Postgres-XL Coordinators
-   or Datanodes.  If TO ALL is specified, connections to all the nodes
-   are cleaned.  A <replaceable class="parameter">username</replaceable>
-   or a <replaceable class="parameter">dbname</replaceable> has to be
-   specified to perform <command>CLEAN CONNECTION</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>FORCE</literal></term>
-    <listitem>
-     <para>
-      It can only be specified with the clause <literal>TO ALL</literal>.
-      If specified, all the backends connected to the specified node(s)
-      are closed by sending to them a signal SIGTERM.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">dbname</replaceable></term>
-    <listitem>
-     <para>
-      If specified in the optional clause <literal>FOR DATABASE</literal>,
-      pooler connections are cleaned for given database.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">username</replaceable></term>
-    <listitem>
-     <para>
-      If specified in the optional clause <literal>TO USER</literal>,
-      pooler connections are cleaned for given role.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">nodename</replaceable></term>
-    <listitem>
-     <para>
-      In the case of cleaning connections to a given list of
-      Coordinator, <replaceable class="parameter">nodename</replaceable>
-      has to be specified with the clause <literal>TO COORDINATOR
-      </literal>.
-     </para>
-     <para>
-       In the case of cleaning connections to a given list of
-       Datanodes, <replaceable class="parameter">nodename</replaceable>
-       has to be specified with the clause <literal>TO NODE
-       </literal>.
-     </para>
-     <para>
-       <replaceable class="parameter">num</replaceable> can contain
-       a list of nodes like in the query:
-
-<programlisting>
-CLEAN CONNECTION TO COORDINATOR coord1,coord2 FOR DATABASE<replaceable>name</replaceable>;
-</programlisting>
-       to clean connections to Coordinators coord1 and coord2.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Cleaning connection to Datanodes dn1 and dn2 for database template1:
-<programlisting>
-CLEAN CONNECTION TO NODE dn1,dn2 FOR DATABASE template1;
-</programlisting>
-  </para>
-
-  <para>
-   Cleaning connection to Datanode dn3 for role postgres:
-<programlisting>
-CLEAN CONNECTION TO NODE dn3 TO USER postgres;
-</programlisting>
-  </para>
-
-  <para>
-   Cleaning connection to all nodes on database postgres for
-   role admin and cut connections to backends.
-<programlisting>
-CLEAN CONNECTION TO ALL FORCE FOR DATABASE postgres TO USER admin;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>CLEAN CONNECTION</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XL specific command.
-  </para>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/close.sgmlin b/doc-xc/src/sgml/ref/close.sgmlin
deleted file mode 100644
index cf77aa87f2..0000000000
--- a/doc-xc/src/sgml/ref/close.sgmlin
+++ /dev/null
@@ -1,135 +0,0 @@
-<!--
-doc/src/sgml/ref/close.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CLOSE">
- <refmeta>
-  <refentrytitle>CLOSE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CLOSE</refname>
-  <refpurpose>close a cursor</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-close">
-  <primary>CLOSE</primary>
- </indexterm>
-
- <indexterm zone="sql-close">
-  <primary>cursor</primary>
-  <secondary>CLOSE</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CLOSE { <replaceable class="PARAMETER">name</replaceable> | ALL }
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>CLOSE</command> frees the resources associated with an open cursor.
-   After the cursor is closed, no subsequent operations
-   are allowed on it. A cursor should be closed when it is
-   no longer needed.
-  </para>
-
-  <para>
-   Every non-holdable open cursor is implicitly closed when a
-   transaction is terminated by <command>COMMIT</command> or
-   <command>ROLLBACK</command>.  A holdable cursor is implicitly
-   closed if the transaction that created it aborts via
-   <command>ROLLBACK</command>.  If the creating transaction
-   successfully commits, the holdable cursor remains open until an
-   explicit <command>CLOSE</command> is executed, or the client
-   disconnects.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an open cursor to close.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ALL</literal></term>
-    <listitem>
-     <para>
-      Close all open cursors.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <productname>PostgreSQL</productname> does not have an explicit
-   <command>OPEN</command> cursor statement; a cursor is considered
-   open when it is declared.  Use the
-   <xref linkend="sql-declare">
-   statement to declare a cursor.
-  </para>
-
-  <para>
-   You can see all available cursors by querying the <link
-   linkend="view-pg-cursors"><structname>pg_cursors</></> system view.
-  </para>
-
-  <para>
-   If a cursor is closed after a savepoint which is later rolled back,
-   the <command>CLOSE</command> is not rolled back; that is, the cursor
-   remains closed.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Close the cursor <literal>liahona</literal>:
-<programlisting>
-CLOSE liahona;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CLOSE</command> is fully conforming with the SQL
-   standard. <command>CLOSE ALL</> is a <productname>PostgreSQL</>
-   extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-declare"></member>
-   <member><xref linkend="sql-fetch"></member>
-   <member><xref linkend="sql-move"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/cluster.sgmlin b/doc-xc/src/sgml/ref/cluster.sgmlin
deleted file mode 100644
index a754a0503c..0000000000
--- a/doc-xc/src/sgml/ref/cluster.sgmlin
+++ /dev/null
@@ -1,260 +0,0 @@
-<!--
-doc/src/sgml/ref/cluster.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CLUSTER">
- <refmeta>
-  <refentrytitle>CLUSTER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CLUSTER</refname>
-  <refpurpose>cluster a table according to an index</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-cluster">
-  <primary>CLUSTER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CLUSTER [VERBOSE] <replaceable class="PARAMETER">table_name</replaceable> [ USING <replaceable class="PARAMETER">index_name</replaceable> ]
-CLUSTER [VERBOSE]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-  <para>
-<!## PG>
-   <command>CLUSTER</command> instructs <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   <command>CLUSTER</command> instructs <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   <command>CLUSTER</command> instructs <productname>Postgres-XL</productname>
-<!## end>
-   to cluster the table specified
-   by <replaceable class="parameter">table_name</replaceable>
-   based on the index specified by
-   <replaceable class="parameter">index_name</replaceable>. The index must
-   already have been defined on
-   <replaceable class="parameter">table_name</replaceable>.
-  </para>
-
-  <para>
-   When a table is clustered, it is physically reordered
-   based on the index information. Clustering is a one-time operation:
-   when the table is subsequently updated, the changes are
-   not clustered.  That is, no attempt is made to store new or
-   updated rows according to their index order.  (If one wishes, one can
-   periodically recluster by issuing the command again.  Also, setting
-   the table's <literal>FILLFACTOR</literal> storage parameter to less than
-   100% can aid in preserving cluster ordering during updates, since updated
-   rows are kept on the same page if enough space is available there.)
-  </para>
-
-  <para>
-<!## PG>
-   When a table is clustered, <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   When a table is clustered, <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   When a table is clustered, <productname>Postgres-XL</productname>
-<!## end>
-   remembers which index it was clustered by.  The form
-   <command>CLUSTER <replaceable class="parameter">table_name</replaceable></command>
-   reclusters the table using the same index as before.  You can also
-   use the <literal>CLUSTER</literal> or <literal>SET WITHOUT CLUSTER</literal>
-   forms of <xref linkend="SQL-ALTERTABLE"> to set the index to be used for
-   future cluster operations, or to clear any previous setting.
-  </para>
-
-  <para>
-   <command>CLUSTER</command> without any parameter reclusters all the
-   previously-clustered tables in the current database that the calling user
-   owns, or all such tables if called by a superuser.  This
-   form of <command>CLUSTER</command> cannot be executed inside a transaction
-   block.
-  </para>
-
-  <para>
-   When a table is being clustered, an <literal>ACCESS
-   EXCLUSIVE</literal> lock is acquired on it. This prevents any other
-   database operations (both reads and writes) from operating on the
-   table until the <command>CLUSTER</command> is finished.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   In <productname>Postgres-XC</>, <command>CLUSTER</> will be
-   executed on all the Datanodes as well.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   In <productname>Postgres-XL</>, <command>CLUSTER</> will be
-   executed on all the Datanodes as well.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-&common;
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">table_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (possibly schema-qualified) of a table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">index_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an index.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>VERBOSE</literal></term>
-    <listitem>
-     <para>
-      Prints a progress report as each table is clustered.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    In cases where you are accessing single rows randomly
-    within a table, the actual order of the data in the
-    table is unimportant. However, if you tend to access some
-    data more than others, and there is an index that groups
-    them together, you will benefit from using <command>CLUSTER</command>.
-    If you are requesting a range of indexed values from a table, or a
-    single indexed value that has multiple rows that match,
-    <command>CLUSTER</command> will help because once the index identifies the
-    table page for the first row that matches, all other rows
-    that match are probably already on the same table page,
-    and so you save disk accesses and speed up the query.
-   </para>
-
-   <para>
-    <command>CLUSTER</> can re-sort the table using either an index scan
-    on the specified index, or (if the index is a b-tree) a sequential
-    scan followed by sorting.  It will attempt to choose the method that
-    will be faster, based on planner cost parameters and available statistical
-    information.
-   </para>
-
-   <para>
-    When an index scan is used, a temporary copy of the table is created that
-    contains the table data in the index order.  Temporary copies of each
-    index on the table are created as well.  Therefore, you need free space on
-    disk at least equal to the sum of the table size and the index sizes.
-   </para>
-
-   <para>
-    When a sequential scan and sort is used, a temporary sort file is
-    also created, so that the peak temporary space requirement is as much
-    as double the table size, plus the index sizes.  This method is often
-    faster than the index scan method, but if the disk space requirement is
-    intolerable, you can disable this choice by temporarily setting <xref
-    linkend="guc-enable-sort"> to <literal>off</>.
-   </para>
-
-   <para>
-    It is advisable to set <xref linkend="guc-maintenance-work-mem"> to
-    a reasonably large value (but not more than the amount of RAM you can
-    dedicate to the <command>CLUSTER</> operation) before clustering.
-   </para>
-
-   <para>
-    Because the planner records statistics about the ordering of
-    tables, it is advisable to run <xref linkend="sql-analyze">
-    on the newly clustered table.
-    Otherwise, the planner might make poor choices of query plans.
-   </para>
-
-   <para>
-    Because <command>CLUSTER</command> remembers which indexes are clustered,
-    one can cluster the tables one wants clustered manually the first time,
-    then set up a periodic maintenance script that executes
-    <command>CLUSTER</> without any parameters, so that the desired tables
-    are periodically reclustered.
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Cluster the table <literal>employees</literal> on the basis of
-   its index <literal>employees_ind</literal>:
-<programlisting>
-CLUSTER employees USING employees_ind;
-</programlisting>
-  </para>
-
-  <para>
-   Cluster the <literal>employees</literal> table using the same
-   index that was used before:
-<programlisting>
-CLUSTER employees;
-</programlisting>
-  </para>
-
-  <para>
-   Cluster all tables in the database that have previously been clustered:
-<programlisting>
-CLUSTER;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>CLUSTER</command> statement in the SQL standard.
-  </para>
-
-  <para>
-   The syntax
-<synopsis>
-CLUSTER <replaceable class="PARAMETER">index_name</replaceable> ON <replaceable class="PARAMETER">table_name</replaceable>
-</synopsis>
-  is also supported for compatibility with pre-8.3 <productname>PostgreSQL</>
-  versions.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-clusterdb"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/clusterdb.sgmlin b/doc-xc/src/sgml/ref/clusterdb.sgmlin
deleted file mode 100644
index 44377b39e0..0000000000
--- a/doc-xc/src/sgml/ref/clusterdb.sgmlin
+++ /dev/null
@@ -1,311 +0,0 @@
-<!--
-doc/src/sgml/ref/clusterdb.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-CLUSTERDB">
- <refmeta>
-  <refentrytitle><application>clusterdb</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname id="clusterdb">clusterdb</refname>
-  <refpurpose>cluster a <productname>PostgreSQL</productname> database</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-clusterdb">
-  <primary>clusterdb</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>clusterdb</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <group><arg>--verbose</arg><arg>-v</arg></group>
-   <arg>--table | -t <replaceable>table</replaceable> </arg>
-   <arg><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>clusterdb</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <group><arg>--verbose</arg><arg>-v</arg></group>
-   <group><arg>--all</arg><arg>-a</arg></group>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <application>clusterdb</application> is a utility for reclustering tables
-   in a <productname>PostgreSQL</productname> database.  It finds tables
-   that have previously been clustered, and clusters them again on the same
-   index that was last used.  Tables that have never been clustered are not
-   affected.
-  </para>
-
-  <para>
-   <application>clusterdb</application> is a wrapper around the SQL
-   command <xref linkend="SQL-CLUSTER">.
-   There is no effective difference between clustering databases via
-   this utility and via other methods for accessing the server.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-
-   <para>
-    <application>clusterdb</application> accepts the following command-line arguments:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-a</></term>
-      <term><option>--all</></term>
-      <listitem>
-       <para>
-        Cluster all databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option><optional>-d</> <replaceable class="parameter">dbname</replaceable></></term>
-      <term><option><optional>--dbname=</><replaceable class="parameter">dbname</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the name of the database to be clustered.
-        If this is not specified and <option>-a</option> (or
-        <option>--all</option>) is not used, the database name is read
-        from the environment variable <envar>PGDATABASE</envar>.  If
-        that is not set, the user name specified for the connection is
-        used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</></term>
-      <term><option>--echo</></term>
-      <listitem>
-       <para>
-        Echo the commands that <application>clusterdb</application> generates
-        and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-q</></term>
-      <term><option>--quiet</></term>
-      <listitem>
-       <para>
-        Do not display progress messages.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t <replaceable class="parameter">table</replaceable></></term>
-      <term><option>--table=<replaceable class="parameter">table</replaceable></></term>
-      <listitem>
-       <para>
-        Cluster <replaceable class="parameter">table</replaceable> only.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-v</></term>
-      <term><option>--verbose</></term>
-      <listitem>
-       <para>
-        Print detailed information during processing.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    <varlistentry>
-      <term><option>-V</></term>
-      <term><option>--version</></term>
-      <listitem>
-      <para>
-      Print the <application>clusterdb</application> version and exit.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-?</></term>
-      <term><option>--help</></term>
-      <listitem>
-      <para>
-      Show help about <application>clusterdb</application> command line
-      arguments, and exit.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    <application>clusterdb</application> also accepts
-    the following command-line arguments for connection parameters:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the server is
-        running.  If the value begins with a slash, it is used as the
-        directory for the Unix domain socket.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server
-        is listening for connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-       <para>
-        Force <application>clusterdb</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>clusterdb</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>clusterdb</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATABASE</envar></term>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Diagnostics</title>
-
-  <para>
-   In case of difficulty, see <xref linkend="SQL-CLUSTER">
-   and <xref linkend="APP-PSQL"> for
-   discussions of potential problems and error messages.
-   The database server must be running at the
-   targeted host.  Also, any default connection settings and environment
-   variables used by the <application>libpq</application> front-end
-   library will apply.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Examples</title>
-
-   <para>
-    To cluster the database <literal>test</literal>:
-<screen>
-<prompt>$ </prompt><userinput>clusterdb test</userinput>
-</screen>
-   </para>
-
-   <para>
-    To cluster a single table
-    <literal>foo</literal> in a database named
-    <literal>xyzzy</literal>:
-<screen>
-<prompt>$ </prompt><userinput>clusterdb --table foo xyzzy</userinput>
-</screen>
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-cluster"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/comment.sgmlin b/doc-xc/src/sgml/ref/comment.sgmlin
deleted file mode 100644
index 6aa448dc9e..0000000000
--- a/doc-xc/src/sgml/ref/comment.sgmlin
+++ /dev/null
@@ -1,309 +0,0 @@
-<!--
-doc/src/sgml/ref/comment.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-COMMENT">
- <refmeta>
-  <refentrytitle>COMMENT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>COMMENT</refname>
-  <refpurpose>define or change the comment of an object</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-comment">
-  <primary>COMMENT</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-COMMENT ON
-{
-  AGGREGATE <replaceable class="PARAMETER">agg_name</replaceable> (<replaceable class="PARAMETER">agg_type</replaceable> [, ...] ) |
-  CAST (<replaceable>source_type</replaceable> AS <replaceable>target_type</replaceable>) |
-  COLLATION <replaceable class="PARAMETER">object_name</replaceable> |
-  COLUMN <replaceable class="PARAMETER">table_name</replaceable>.<replaceable class="PARAMETER">column_name</replaceable> |
-  CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ON <replaceable class="PARAMETER">table_name</replaceable> |
-  CONVERSION <replaceable class="PARAMETER">object_name</replaceable> |
-  DATABASE <replaceable class="PARAMETER">object_name</replaceable> |
-  DOMAIN <replaceable class="PARAMETER">object_name</replaceable> |
-  EXTENSION <replaceable class="PARAMETER">object_name</replaceable> |
-  FOREIGN DATA WRAPPER <replaceable class="PARAMETER">object_name</replaceable> |
-  FOREIGN TABLE <replaceable class="PARAMETER">object_name</replaceable> |
-  FUNCTION <replaceable class="PARAMETER">function_name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">argname</replaceable> ] <replaceable class="parameter">argtype</replaceable> [, ...] ] ) |
-  INDEX <replaceable class="PARAMETER">object_name</replaceable> |
-  LARGE OBJECT <replaceable class="PARAMETER">large_object_oid</replaceable> |
-  OPERATOR <replaceable class="PARAMETER">operator_name</replaceable> (<replaceable class="PARAMETER">left_type</replaceable>, <replaceable class="PARAMETER">right_type</replaceable>) |
-  OPERATOR CLASS <replaceable class="PARAMETER">object_name</replaceable> USING <replaceable class="parameter">index_method</replaceable> |
-  OPERATOR FAMILY <replaceable class="PARAMETER">object_name</replaceable> USING <replaceable class="parameter">index_method</replaceable> |
-  [ PROCEDURAL ] LANGUAGE <replaceable class="PARAMETER">object_name</replaceable> |
-  ROLE <replaceable class="PARAMETER">object_name</replaceable> |
-  RULE <replaceable class="PARAMETER">rule_name</replaceable> ON <replaceable class="PARAMETER">table_name</replaceable> |
-  SCHEMA <replaceable class="PARAMETER">object_name</replaceable> |
-  SEQUENCE <replaceable class="PARAMETER">object_name</replaceable> |
-  SERVER <replaceable class="PARAMETER">object_name</replaceable> |
-  TABLE <replaceable class="PARAMETER">object_name</replaceable> |
-  TABLESPACE <replaceable class="PARAMETER">object_name</replaceable> |
-  TEXT SEARCH CONFIGURATION <replaceable class="PARAMETER">object_name</replaceable> |
-  TEXT SEARCH DICTIONARY <replaceable class="PARAMETER">object_name</replaceable> |
-  TEXT SEARCH PARSER <replaceable class="PARAMETER">object_name</replaceable> |
-  TEXT SEARCH TEMPLATE <replaceable class="PARAMETER">object_name</replaceable> |
-  TRIGGER <replaceable class="PARAMETER">trigger_name</replaceable> ON <replaceable class="PARAMETER">table_name</replaceable> |
-  TYPE <replaceable class="PARAMETER">object_name</replaceable> |
-  VIEW <replaceable class="PARAMETER">object_name</replaceable>
-} IS '<replaceable class="PARAMETER">text</replaceable>'
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>COMMENT</command> stores a comment about a database object.
-  </para>
-
-  <para>
-   Only one comment string is stored for each object, so to modify a comment,
-   issue a new <command>COMMENT</> command for the same object.  To remove a
-   comment, write <literal>NULL</literal> in place of the text string.
-   Comments are automatically dropped when their object is dropped.
-  </para>
-
-  <para>
-   For most kinds of object, only the object's owner can set the comment.
-   Roles don't have owners, so the rule for <literal>COMMENT ON ROLE</> is
-   that you must be superuser to comment on a superuser role, or have the
-   <literal>CREATEROLE</> privilege to comment on non-superuser roles.
-   Of course, a superuser can comment on anything.
-  </para>
-
-  <para>
-    Comments can be viewed using <application>psql</application>'s
-    <command>\d</command> family of commands.
-    Other user interfaces to retrieve comments can be built atop
-    the same built-in functions that <application>psql</application> uses, namely
-    <function>obj_description</>, <function>col_description</>,
-    and <function>shobj_description</>
-    (see <xref linkend="functions-info-comment-table">).
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">object_name</replaceable></term>
-    <term><replaceable class="parameter">table_name.column_name</replaceable></term>
-    <term><replaceable class="parameter">agg_name</replaceable></term>
-    <term><replaceable class="parameter">constraint_name</replaceable></term>
-    <term><replaceable class="parameter">function_name</replaceable></term>
-    <term><replaceable class="parameter">operator_name</replaceable></term>
-    <term><replaceable class="parameter">rule_name</replaceable></term>
-    <term><replaceable class="parameter">trigger_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the object to be commented.  Names of tables,
-      aggregates, collations, conversions, domains, foreign tables, functions,
-      indexes, operators, operator classes, operator families, sequences,
-      text search objects, types, and views can be schema-qualified.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">agg_type</replaceable></term>
-    <listitem>
-     <para>
-      An input data type on which the aggregate function operates.
-      To reference a zero-argument aggregate function, write <literal>*</>
-      in place of the list of input data types.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-     <term><replaceable>source_type</replaceable></term>
-     <listitem>
-      <para>
-       The name of the source data type of the cast.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>target_type</replaceable></term>
-     <listitem>
-      <para>
-       The name of the target data type of the cast.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argmode</replaceable></term>
-    <listitem>
-     <para>
-      The mode of a function argument: <literal>IN</>, <literal>OUT</>,
-      <literal>INOUT</>, or <literal>VARIADIC</>.
-      If omitted, the default is <literal>IN</>.
-      Note that <command>COMMENT ON FUNCTION</command> does not actually pay
-      any attention to <literal>OUT</> arguments, since only the input
-      arguments are needed to determine the function's identity.
-      So it is sufficient to list the <literal>IN</>, <literal>INOUT</>,
-      and <literal>VARIADIC</> arguments.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argname</replaceable></term>
-    <listitem>
-     <para>
-      The name of a function argument.
-      Note that <command>COMMENT ON FUNCTION</command> does not actually pay
-      any attention to argument names, since only the argument data
-      types are needed to determine the function's identity.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argtype</replaceable></term>
-    <listitem>
-     <para>
-      The data type(s) of the function's arguments (optionally
-      schema-qualified), if any.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">large_object_oid</replaceable></term>
-    <listitem>
-     <para>
-      The OID of the large object.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">left_type</replaceable></term>
-    <term><replaceable class="parameter">right_type</replaceable></term>
-    <listitem>
-     <para>
-      The data type(s) of the operator's arguments (optionally
-      schema-qualified).  Write <literal>NONE</> for the missing argument
-      of a prefix or postfix operator.
-     </para>
-    </listitem>
-   </varlistentry>
-
-    <varlistentry>
-     <term><literal>PROCEDURAL</literal></term>
-     <listitem>
-      <para>
-       This is a noise word.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">text</replaceable></term>
-    <listitem>
-     <para>
-      The new comment, written as a string literal; or <literal>NULL</>
-      to drop the comment.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   There is presently no security mechanism for viewing comments: any user
-   connected to a database can see all the comments for objects in
-   that database.  For shared objects such as
-   databases, roles, and tablespaces, comments are stored globally so any
-   user connected to any database in the cluster can see all the comments
-   for shared objects.  Therefore, don't put security-critical
-   information in comments.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Attach a comment to the table <literal>mytable</literal>:
-
-<programlisting>
-COMMENT ON TABLE mytable IS 'This is my table.';
-</programlisting>
-
-   Remove it again:
-
-<programlisting>
-COMMENT ON TABLE mytable IS NULL;
-</programlisting>
-  </para>
-
-  <para>
-   Some more examples:
-
-<programlisting>
-COMMENT ON AGGREGATE my_aggregate (double precision) IS 'Computes sample variance';
-COMMENT ON CAST (text AS int4) IS 'Allow casts from text to int4';
-COMMENT ON COLLATION "fr_CA" IS 'Canadian French';
-COMMENT ON COLUMN my_table.my_column IS 'Employee ID number';
-COMMENT ON CONVERSION my_conv IS 'Conversion to UTF8';
-COMMENT ON CONSTRAINT bar_col_cons ON bar IS 'Constrains column col';
-COMMENT ON DATABASE my_database IS 'Development Database';
-COMMENT ON DOMAIN my_domain IS 'Email Address Domain';
-COMMENT ON EXTENSION hstore IS 'implements the hstore data type';
-COMMENT ON FOREIGN DATA WRAPPER mywrapper IS 'my foreign data wrapper';
-COMMENT ON FOREIGN TABLE my_foreign_table IS 'Employee Information in other database';
-COMMENT ON FUNCTION my_function (timestamp) IS 'Returns Roman Numeral';
-COMMENT ON INDEX my_index IS 'Enforces uniqueness on employee ID';
-COMMENT ON LANGUAGE plpython IS 'Python support for stored procedures';
-COMMENT ON LARGE OBJECT 346344 IS 'Planning document';
-COMMENT ON OPERATOR ^ (text, text) IS 'Performs intersection of two texts';
-COMMENT ON OPERATOR - (NONE, integer) IS 'Unary minus';
-COMMENT ON OPERATOR CLASS int4ops USING btree IS '4 byte integer operators for btrees';
-COMMENT ON OPERATOR FAMILY integer_ops USING btree IS 'all integer operators for btrees';
-COMMENT ON ROLE my_role IS 'Administration group for finance tables';
-COMMENT ON RULE my_rule ON my_table IS 'Logs updates of employee records';
-COMMENT ON SCHEMA my_schema IS 'Departmental data';
-COMMENT ON SEQUENCE my_sequence IS 'Used to generate primary keys';
-COMMENT ON SERVER myserver IS 'my foreign server';
-COMMENT ON TABLE my_schema.my_table IS 'Employee Information';
-COMMENT ON TABLESPACE my_tablespace IS 'Tablespace for indexes';
-COMMENT ON TEXT SEARCH CONFIGURATION my_config IS 'Special word filtering';
-COMMENT ON TEXT SEARCH DICTIONARY swedish IS 'Snowball stemmer for swedish language';
-COMMENT ON TEXT SEARCH PARSER my_parser IS 'Splits text into words';
-COMMENT ON TEXT SEARCH TEMPLATE snowball IS 'Snowball stemmer';
-COMMENT ON TRIGGER my_trigger ON my_table IS 'Used for RI';
-COMMENT ON TYPE complex IS 'Complex number data type';
-COMMENT ON VIEW my_view IS 'View of departmental costs';
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>COMMENT</command> command in the SQL standard.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/commit.sgmlin b/doc-xc/src/sgml/ref/commit.sgmlin
deleted file mode 100644
index c3cb71a9fa..0000000000
--- a/doc-xc/src/sgml/ref/commit.sgmlin
+++ /dev/null
@@ -1,97 +0,0 @@
-<!--
-doc/src/sgml/ref/commit.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-COMMIT">
- <refmeta>
-  <refentrytitle>COMMIT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>COMMIT</refname>
-  <refpurpose>commit the current transaction</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-commit">
-  <primary>COMMIT</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-COMMIT [ WORK | TRANSACTION ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-&common;
-  <para>
-   <command>COMMIT</command> commits the current transaction. All
-   changes made by the transaction become visible to others
-   and are guaranteed to be durable if a crash occurs.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>WORK</literal></term>
-    <term><literal>TRANSACTION</literal></term>
-    <listitem>
-     <para>
-      Optional key words. They have no effect.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-ROLLBACK"> to
-   abort a transaction.
-  </para>
-
-  <para>
-   Issuing <command>COMMIT</> when not inside a transaction does
-   no harm, but it will provoke a warning message.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To commit the current transaction and make all changes permanent:
-<programlisting>
-COMMIT;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard only specifies the two forms
-   <literal>COMMIT</literal> and <literal>COMMIT
-   WORK</literal>. Otherwise, this command is fully conforming.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-begin"></member>
-   <member><xref linkend="sql-rollback"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/commit_prepared.sgmlin b/doc-xc/src/sgml/ref/commit_prepared.sgmlin
deleted file mode 100644
index cdbf7bf754..0000000000
--- a/doc-xc/src/sgml/ref/commit_prepared.sgmlin
+++ /dev/null
@@ -1,126 +0,0 @@
-<!--
-doc/src/sgml/ref/commit_prepared.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-COMMIT-PREPARED">
- <refmeta>
-  <refentrytitle>COMMIT PREPARED</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>COMMIT PREPARED</refname>
-  <refpurpose>commit a transaction that was earlier prepared for two-phase commit</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-commit-prepared">
-  <primary>COMMIT PREPARED</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-COMMIT PREPARED <replaceable class="PARAMETER">transaction_id</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-&common;
-  <para>
-   <command>COMMIT PREPARED</command> commits a transaction that is in
-   prepared state.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">transaction_id</replaceable></term>
-    <listitem>
-     <para>
-      The transaction identifier of the transaction that is to be
-      committed.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   To commit a prepared transaction, you must be either the same user that
-   executed the transaction originally, or a superuser.  But you do not
-   have to be in the same session that executed the transaction.
-  </para>
-
-  <para>
-   This command cannot be executed inside a transaction block. The prepared
-   transaction is committed immediately.
-  </para>
-
-  <para>
-   All currently available prepared transactions are listed in the
-   <link linkend="view-pg-prepared-xacts"><structname>pg_prepared_xacts</structname></link>
-   system view.
-  </para>
-<!## XC>
-&xconly;
-  <para>
-   If more than one Datanode and/or Coordinator are involved in the
-   transaction, <command>COMMIT PREPARED</> command will propagate to
-   all these nodes.
-  </para>
-&xconly;
-  <para>
-   If <literal>xc_maintenance_mode</literal> GUC parameter is set to <literal>ON</literal>, <command>COMMIT PREPARED</command> will not propagate to other nodes.   It just runs locally and report the result to <literal>GTM</literal>.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   If more than one Datanode and/or Coordinator are involved in the
-   transaction, <command>COMMIT PREPARED</> command will propagate to
-   all these nodes.
-  </para>
-&xlonly;
-  <para>
-   If <literal>xc_maintenance_mode</literal> GUC parameter is set to <literal>ON</literal>, <command>COMMIT PREPARED</command> will not propagate to other nodes.   It just runs locally and report the result to <literal>GTM</literal>.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1 id="sql-commit-prepared-examples">
-  <title id="sql-commit-prepared-examples-title">Examples</title>
-  <para>
-   Commit the transaction identified by the transaction
-   identifier <literal>foobar</>:
-
-<programlisting>
-COMMIT PREPARED 'foobar';
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-prepare-transaction"></member>
-   <member><xref linkend="sql-rollback-prepared"></member>
-<!## XC>
-   <member><xref linkend="guc-xc-maintenance-mode"></member>
-<!## end>
-<!## XL>
-   <member><xref linkend="guc-xc-maintenance-mode"></member>
-<!## end>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/copy.sgmlin b/doc-xc/src/sgml/ref/copy.sgmlin
deleted file mode 100644
index 14f9df52ec..0000000000
--- a/doc-xc/src/sgml/ref/copy.sgmlin
+++ /dev/null
@@ -1,1006 +0,0 @@
-<!--
-doc/src/sgml/ref/copy.sgml
-PostgreSQL documentation
--->
-
-
-<refentry id="SQL-COPY">
- <refmeta>
-  <refentrytitle>COPY</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>COPY</refname>
-  <refpurpose>copy data between a file and a table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-copy">
-  <primary>COPY</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-COPY <replaceable class="parameter">table_name</replaceable> [ ( <replaceable class="parameter">column</replaceable> [, ...] ) ]
-    FROM { '<replaceable class="parameter">filename</replaceable>' | STDIN }
-    [ [ WITH ] ( <replaceable class="parameter">option</replaceable> [, ...] ) ]
-
-COPY { <replaceable class="parameter">table_name</replaceable> [ ( <replaceable class="parameter">column</replaceable> [, ...] ) ] | ( <replaceable class="parameter">query</replaceable> ) }
-    TO { '<replaceable class="parameter">filename</replaceable>' | STDOUT }
-    [ [ WITH ] ( <replaceable class="parameter">option</replaceable> [, ...] ) ]
-
-<phrase>where <replaceable class="parameter">option</replaceable> can be one of:</phrase>
-
-    FORMAT <replaceable class="parameter">format_name</replaceable>
-    OIDS [ <replaceable class="parameter">boolean</replaceable> ]
-    DELIMITER '<replaceable class="parameter">delimiter_character</replaceable>'
-    NULL '<replaceable class="parameter">null_string</replaceable>'
-    HEADER [ <replaceable class="parameter">boolean</replaceable> ]
-    QUOTE '<replaceable class="parameter">quote_character</replaceable>'
-    ESCAPE '<replaceable class="parameter">escape_character</replaceable>'
-    FORCE_QUOTE { ( <replaceable class="parameter">column</replaceable> [, ...] ) | * }
-    FORCE_NOT_NULL ( <replaceable class="parameter">column</replaceable> [, ...] ) |
-    ENCODING '<replaceable class="parameter">encoding_name</replaceable>'
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>COPY</command> moves data between
-<!## PG>
-   <productname>PostgreSQL</productname> tables and standard file-system
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> tables and standard file-system
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> tables and standard file-system
-<!## end>
-   files. <command>COPY TO</command> copies the contents of a table
-   <emphasis>to</> a file, while <command>COPY FROM</command> copies
-   data <emphasis>from</> a file to a table (appending the data to
-   whatever is in the table already).  <command>COPY TO</command>
-   can also copy the results of a <command>SELECT</> query.
-  </para>
-
-  <para>
-   If a list of columns is specified, <command>COPY</command> will
-   only copy the data in the specified columns to or from the file.
-   If there are any columns in the table that are not in the column list,
-   <command>COPY FROM</command> will insert the default values for
-   those columns.
-  </para>
-
-  <para>
-   <command>COPY</command> with a file name instructs the
-<!## PG>
-   <productname>PostgreSQL</productname> server to directly read from
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> server to directly read from
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> server to directly read from
-<!## end>
-   or write to a file. The file must be accessible to the server and
-   the name must be specified from the viewpoint of the server. When
-   <literal>STDIN</literal> or <literal>STDOUT</literal> is
-   specified, data is transmitted via the connection between the
-   client and the server.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">table_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">column</replaceable></term>
-     <listitem>
-     <para>
-      An optional list of columns to be copied.  If no column list is
-      specified, all columns of the table will be copied.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">query</replaceable></term>
-    <listitem>
-     <para>
-      A <xref linkend="sql-select"> or
-      <xref linkend="sql-values"> command
-      whose results are to be copied.
-      Note that parentheses are required around the query.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">filename</replaceable></term>
-    <listitem>
-     <para>
-      The absolute path name of the input or output file.  Windows users
-      might need to use an <literal>E''</> string and double any backslashes
-      used in the path name.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>STDIN</literal></term>
-    <listitem>
-     <para>
-      Specifies that input comes from the client application.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>STDOUT</literal></term>
-    <listitem>
-     <para>
-      Specifies that output goes to the client application.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">boolean</replaceable></term>
-    <listitem>
-     <para>
-      Specifies whether the selected option should be turned on or off.
-      You can write <literal>TRUE</literal>, <literal>ON</>, or
-      <literal>1</literal> to enable the option, and <literal>FALSE</literal>,
-      <literal>OFF</>, or <literal>0</literal> to disable it.  The
-      <replaceable class="parameter">boolean</replaceable> value can also
-      be omitted, in which case <literal>TRUE</literal> is assumed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>FORMAT</literal></term>
-    <listitem>
-     <para>
-      Selects the data format to be read or written:
-      <literal>text</>,
-      <literal>csv</> (Comma Separated Values),
-      or <literal>binary</>.
-      The default is <literal>text</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OIDS</literal></term>
-    <listitem>
-     <para>
-      Specifies copying the OID for each row.  (An error is raised if
-      <literal>OIDS</literal> is specified for a table that does not
-      have OIDs, or in the case of copying a <replaceable
-      class="parameter">query</replaceable>.)
-     </para>
-<!## XC>
-&xconly;
-     <para>
-      In <productname>Postgres-XC</>, OIDs are only maintained locally
-      in Coordinators and Datanodes.  The value of <literal>OIDs</>
-      may conflict if you copy this value to another table.
-     </para>
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      In <productname>Postgres-XL</>, OIDs are only maintained locally
-      in Coordinators and Datanodes.  The value of <literal>OIDs</>
-      may conflict if you copy this value to another table.
-     </para>
-<!## end>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DELIMITER</literal></term>
-    <listitem>
-     <para>
-      Specifies the character that separates columns within each row
-      (line) of the file.  The default is a tab character in text format,
-      a comma in <literal>CSV</> format.
-      This must be a single one-byte character.
-      This option is not allowed when using <literal>binary</> format.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NULL</literal></term>
-    <listitem>
-     <para>
-      Specifies the string that represents a null value. The default is
-      <literal>\N</literal> (backslash-N) in text format, and an unquoted empty
-      string in <literal>CSV</> format. You might prefer an
-      empty string even in text format for cases where you don't want to
-      distinguish nulls from empty strings.
-      This option is not allowed when using <literal>binary</> format.
-     </para>
-
-     <note>
-      <para>
-       When using <command>COPY FROM</command>, any data item that matches
-       this string will be stored as a null value, so you should make
-       sure that you use the same string as you used with
-       <command>COPY TO</command>.
-      </para>
-     </note>
-
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>HEADER</literal></term>
-    <listitem>
-     <para>
-      Specifies that the file contains a header line with the names of each
-      column in the file.  On output, the first line contains the column
-      names from the table, and on input, the first line is ignored.
-      This option is allowed only when using <literal>CSV</> format.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>QUOTE</literal></term>
-    <listitem>
-     <para>
-      Specifies the quoting character to be used when a data value is quoted.
-      The default is double-quote.
-      This must be a single one-byte character.
-      This option is allowed only when using <literal>CSV</> format.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ESCAPE</literal></term>
-    <listitem>
-     <para>
-      Specifies the character that should appear before a
-      data character that matches the <literal>QUOTE</> value.
-      The default is the same as the <literal>QUOTE</> value (so that
-      the quoting character is doubled if it appears in the data).
-      This must be a single one-byte character.
-      This option is allowed only when using <literal>CSV</> format.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>FORCE_QUOTE</></term>
-    <listitem>
-     <para>
-      Forces quoting to be
-      used for all non-<literal>NULL</> values in each specified column.
-      <literal>NULL</> output is never quoted. If <literal>*</> is specified,
-      non-<literal>NULL</> values will be quoted in all columns.
-      This option is allowed only in <command>COPY TO</>, and only when
-      using <literal>CSV</> format.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>FORCE_NOT_NULL</></term>
-    <listitem>
-     <para>
-      Do not match the specified columns' values against the null string.
-      In the default case where the null string is empty, this means that
-      empty values will be read as zero-length strings rather than nulls,
-      even when they are not quoted.
-      This option is allowed only in <command>COPY FROM</>, and only when
-      using <literal>CSV</> format.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ENCODING</></term>
-    <listitem>
-     <para>
-      Specifies that the file is encoded in the <replaceable
-      class="parameter">encoding_name</replaceable>.  If this option is
-      omitted, the current client encoding is used. See the Notes below
-      for more details.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Outputs</title>
-
-  <para>
-   On successful completion, a <command>COPY</> command returns a command
-   tag of the form
-<screen>
-COPY <replaceable class="parameter">count</replaceable>
-</screen>
-   The <replaceable class="parameter">count</replaceable> is the number
-   of rows copied.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    <command>COPY</command> can only be used with plain tables, not
-    with views.  However, you can write <literal>COPY (SELECT * FROM
-    <replaceable class="parameter">viewname</replaceable>) TO ...</literal>.
-   </para>
-
-   <para>
-    <command>COPY</command> only deals with the specific table named;
-    it does not copy data to or from child tables.  Thus for example
-    <literal>COPY <replaceable class="parameter">table</> TO</literal>
-    shows the same data as <literal>SELECT * FROM ONLY <replaceable
-    class="parameter">table</></literal>.  But <literal>COPY
-    (SELECT * FROM <replaceable class="parameter">table</>) TO ...</literal>
-    can be used to dump all of the data in an inheritance hierarchy.
-   </para>
-
-   <para>
-    You must have select privilege on the table
-    whose values are read by <command>COPY TO</command>, and
-    insert privilege on the table into which values
-    are inserted by <command>COPY FROM</command>.  It is sufficient
-    to have column privileges on the column(s) listed in the command.
-   </para>
-
-   <para>
-    Files named in a <command>COPY</command> command are read or written
-    directly by the server, not by the client application. Therefore,
-    they must reside on or be accessible to the database server machine,
-    not the client. They must be accessible to and readable or writable
-<!## PG>
-    by the <productname>PostgreSQL</productname> user (the user ID the
-<!## end>
-<!## XC>
-    by the <productname>Postgres-XC</productname> user (the user ID the
-<!## end>
-<!## XL>
-    by the <productname>Postgres-XL</productname> user (the user ID the
-<!## end>
-    server runs as), not the client. <command>COPY</command> naming a
-    file is only allowed to database superusers, since it allows reading
-    or writing any file that the server has privileges to access.
-   </para>
-
-   <para>
-    Do not confuse <command>COPY</command> with the
-    <application>psql</application> instruction
-    <command>\copy</command>. <command>\copy</command> invokes
-    <command>COPY FROM STDIN</command> or <command>COPY TO
-    STDOUT</command>, and then fetches/stores the data in a file
-    accessible to the <application>psql</application> client. Thus,
-    file accessibility and access rights depend on the client rather
-    than the server when <command>\copy</command> is used.
-   </para>
-
-   <para>
-    It is recommended that the file name used in <command>COPY</command>
-    always be specified as an absolute path. This is enforced by the
-    server in the case of <command>COPY TO</command>, but for
-    <command>COPY FROM</command> you do have the option of reading from
-    a file specified by a relative path. The path will be interpreted
-    relative to the working directory of the server process (normally
-    the cluster's data directory), not the client's working directory.
-   </para>
-
-   <para>
-    <command>COPY FROM</command> will invoke any triggers and check
-    constraints on the destination table. However, it will not invoke rules.
-   </para>
-
-   <para>
-    <command>COPY</command> input and output is affected by
-    <varname>DateStyle</varname>. To ensure portability to other
-<!## PG>
-    <productname>PostgreSQL</productname> installations that might use
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> installations that might use
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> installations that might use
-<!## end>
-    non-default <varname>DateStyle</varname> settings,
-    <varname>DateStyle</varname> should be set to <literal>ISO</> before
-    using <command>COPY TO</>.  It is also a good idea to avoid dumping
-    data with <varname>IntervalStyle</varname> set to
-    <literal>sql_standard</>, because negative interval values might be
-    misinterpreted by a server that has a different setting for
-    <varname>IntervalStyle</varname>.
-   </para>
-
-   <para>
-    Input data is interpreted according to <literal>ENCODING</literal>
-    option or the current client encoding, and output data is encoded
-    in <literal>ENCODING</literal> or the current client encoding, even
-    if the data does not pass through the client but is read from or
-    written to a file directly by the server.
-   </para>
-
-   <para>
-    <command>COPY</command> stops operation at the first error. This
-    should not lead to problems in the event of a <command>COPY
-    TO</command>, but the target table will already have received
-    earlier rows in a <command>COPY FROM</command>. These rows will not
-    be visible or accessible, but they still occupy disk space. This might
-    amount to a considerable amount of wasted disk space if the failure
-    happened well into a large copy operation. You might wish to invoke
-    <command>VACUUM</command> to recover the wasted space.
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>File Formats</title>
-
-  <refsect2>
-   <title>Text Format</title>
-
-   <para>
-    When the <literal>text</> format is used,
-    the data read or written is a text file with one line per table row.
-    Columns in a row are separated by the delimiter character.
-    The column values themselves are strings generated by the
-    output function, or acceptable to the input function, of each
-    attribute's data type.  The specified null string is used in
-    place of columns that are null.
-    <command>COPY FROM</command> will raise an error if any line of the
-    input file contains more or fewer columns than are expected.
-    If <literal>OIDS</literal> is specified, the OID is read or written as the first column,
-    preceding the user data columns.
-   </para>
-
-   <para>
-    End of data can be represented by a single line containing just
-    backslash-period (<literal>\.</>).  An end-of-data marker is
-    not necessary when reading from a file, since the end of file
-    serves perfectly well; it is needed only when copying data to or from
-    client applications using pre-3.0 client protocol.
-   </para>
-
-   <para>
-    Backslash characters (<literal>\</>) can be used in the
-    <command>COPY</command> data to quote data characters that might
-    otherwise be taken as row or column delimiters. In particular, the
-    following characters <emphasis>must</> be preceded by a backslash if
-    they appear as part of a column value: backslash itself,
-    newline, carriage return, and the current delimiter character.
-   </para>
-
-   <para>
-    The specified null string is sent by <command>COPY TO</command> without
-    adding any backslashes; conversely, <command>COPY FROM</command> matches
-    the input against the null string before removing backslashes.  Therefore,
-    a null string such as <literal>\N</literal> cannot be confused with
-    the actual data value <literal>\N</literal> (which would be represented
-    as <literal>\\N</literal>).
-   </para>
-
-   <para>
-    The following special backslash sequences are recognized by
-    <command>COPY FROM</command>:
-
-   <informaltable>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Sequence</entry>
-       <entry>Represents</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal>\b</></entry>
-       <entry>Backspace (ASCII 8)</entry>
-      </row>
-      <row>
-       <entry><literal>\f</></entry>
-       <entry>Form feed (ASCII 12)</entry>
-      </row>
-      <row>
-       <entry><literal>\n</></entry>
-       <entry>Newline (ASCII 10)</entry>
-      </row>
-      <row>
-       <entry><literal>\r</></entry>
-       <entry>Carriage return (ASCII 13)</entry>
-      </row>
-      <row>
-       <entry><literal>\t</></entry>
-       <entry>Tab (ASCII 9)</entry>
-      </row>
-      <row>
-       <entry><literal>\v</></entry>
-       <entry>Vertical tab (ASCII 11)</entry>
-      </row>
-      <row>
-       <entry><literal>\</><replaceable>digits</></entry>
-       <entry>Backslash followed by one to three octal digits specifies
-       the character with that numeric code</entry>
-      </row>
-      <row>
-       <entry><literal>\x</><replaceable>digits</></entry>
-       <entry>Backslash <literal>x</> followed by one or two hex digits specifies
-       the character with that numeric code</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </informaltable>
-
-    Presently, <command>COPY TO</command> will never emit an octal or
-    hex-digits backslash sequence, but it does use the other sequences
-    listed above for those control characters.
-   </para>
-
-   <para>
-    Any other backslashed character that is not mentioned in the above table
-    will be taken to represent itself.  However, beware of adding backslashes
-    unnecessarily, since that might accidentally produce a string matching the
-    end-of-data marker (<literal>\.</>) or the null string (<literal>\N</> by
-    default).  These strings will be recognized before any other backslash
-    processing is done.
-   </para>
-
-   <para>
-    It is strongly recommended that applications generating <command>COPY</command> data convert
-    data newlines and carriage returns to the <literal>\n</> and
-    <literal>\r</> sequences respectively.  At present it is
-    possible to represent a data carriage return by a backslash and carriage
-    return, and to represent a data newline by a backslash and newline.
-    However, these representations might not be accepted in future releases.
-    They are also highly vulnerable to corruption if the <command>COPY</command> file is
-    transferred across different machines (for example, from Unix to Windows
-    or vice versa).
-   </para>
-
-   <para>
-    <command>COPY TO</command> will terminate each row with a Unix-style
-    newline (<quote><literal>\n</></>).  Servers running on Microsoft Windows instead
-    output carriage return/newline (<quote><literal>\r\n</></>), but only for
-    <command>COPY</> to a server file; for consistency across platforms,
-    <command>COPY TO STDOUT</> always sends <quote><literal>\n</></>
-    regardless of server platform.
-    <command>COPY FROM</command> can handle lines ending with newlines,
-    carriage returns, or carriage return/newlines.  To reduce the risk of
-    error due to un-backslashed newlines or carriage returns that were
-    meant as data, <command>COPY FROM</command> will complain if the line
-    endings in the input are not all alike.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>CSV Format</title>
-
-   <para>
-    This format option is used for importing and exporting the Comma
-    Separated Value (<literal>CSV</>) file format used by many other
-    programs, such as spreadsheets. Instead of the escaping rules used by
-<!## PG>
-    <productname>PostgreSQL</productname>'s standard text format, it
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>'s standard text format, it
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>'s standard text format, it
-<!## end>
-    produces and recognizes the common CSV escaping mechanism.
-   </para>
-
-   <para>
-    The values in each record are separated by the <literal>DELIMITER</>
-    character. If the value contains the delimiter character, the
-    <literal>QUOTE</> character, the <literal>NULL</> string, a carriage
-    return, or line feed character, then the whole value is prefixed and
-    suffixed by the <literal>QUOTE</> character, and any occurrence
-    within the value of a <literal>QUOTE</> character or the
-    <literal>ESCAPE</> character is preceded by the escape character.
-    You can also use <literal>FORCE_QUOTE</> to force quotes when outputting
-    non-<literal>NULL</> values in specific columns.
-   </para>
-
-   <para>
-    The <literal>CSV</> format has no standard way to distinguish a
-    <literal>NULL</> value from an empty string.
-<!## PG>
-    <productname>PostgreSQL</>'s <command>COPY</> handles this by quoting.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</>'s <command>COPY</> handles this by quoting.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</>'s <command>COPY</> handles this by quoting.
-<!## end>
-    A <literal>NULL</> is output as the <literal>NULL</> parameter string
-    and is not quoted, while a non-<literal>NULL</> value matching the
-    <literal>NULL</> parameter string is quoted.  For example, with the
-    default settings, a <literal>NULL</> is written as an unquoted empty
-    string, while an empty string data value is written with double quotes
-    (<literal>""</>). Reading values follows similar rules. You can
-    use <literal>FORCE_NOT_NULL</> to prevent <literal>NULL</> input
-    comparisons for specific columns.
-   </para>
-
-   <para>
-    Because backslash is not a special character in the <literal>CSV</>
-    format, <literal>\.</>, the end-of-data marker, could also appear
-    as a data value.  To avoid any misinterpretation, a <literal>\.</>
-    data value appearing as a lone entry on a line is automatically
-    quoted on output, and on input, if quoted, is not interpreted as the
-    end-of-data marker.  If you are loading a file created by another
-    application that has a single unquoted column and might have a
-    value of <literal>\.</>, you might need to quote that value in the
-    input file.
-   </para>
-
-   <note>
-    <para>
-     In <literal>CSV</> format, all characters are significant. A quoted value
-     surrounded by white space, or any characters other than
-     <literal>DELIMITER</>, will include those characters. This can cause
-     errors if you import data from a system that pads <literal>CSV</>
-     lines with white space out to some fixed width. If such a situation
-     arises you might need to preprocess the <literal>CSV</> file to remove
-     the trailing white space, before importing the data into
-<!## PG>
-     <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</>.
-<!## end>
-    </para>
-   </note>
-
-   <note>
-    <para>
-     CSV format will both recognize and produce CSV files with quoted
-     values containing embedded carriage returns and line feeds. Thus
-     the files are not strictly one line per table row like text-format
-     files.
-    </para>
-   </note>
-
-   <note>
-    <para>
-     Many programs produce strange and occasionally perverse CSV files,
-     so the file format is more a convention than a standard. Thus you
-     might encounter some files that cannot be imported using this
-     mechanism, and <command>COPY</> might produce files that other
-     programs cannot process.
-    </para>
-   </note>
-
-  </refsect2>
-
-  <refsect2>
-   <title>Binary Format</title>
-
-   <para>
-    The <literal>binary</literal> format option causes all data to be
-    stored/read as binary format rather than as text.  It is
-    somewhat faster than the text and <literal>CSV</> formats,
-    but a binary-format file is less portable across machine architectures and
-<!## PG>
-    <productname>PostgreSQL</productname> versions.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> versions.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> versions.
-<!## end>
-    Also, the binary format is very data type specific; for example
-    it will not work to output binary data from a <type>smallint</> column
-    and read it into an <type>integer</> column, even though that would work
-    fine in text format.
-   </para>
-
-   <para>
-    The <literal>binary</> file format consists
-    of a file header, zero or more tuples containing the row data, and
-    a file trailer.  Headers and data are in network byte order.
-   </para>
-
-   <note>
-    <para>
-     <productname>PostgreSQL</productname> releases before 7.4 used a
-     different binary file format.
-    </para>
-   </note>
-
-   <refsect3>
-    <title>File Header</title>
-
-    <para>
-     The file header consists of 15 bytes of fixed fields, followed
-     by a variable-length header extension area.  The fixed fields are:
-
-    <variablelist>
-     <varlistentry>
-      <term>Signature</term>
-      <listitem>
-       <para>
-11-byte sequence <literal>PGCOPY\n\377\r\n\0</> &mdash; note that the zero byte
-is a required part of the signature.  (The signature is designed to allow
-easy identification of files that have been munged by a non-8-bit-clean
-transfer.  This signature will be changed by end-of-line-translation
-filters, dropped zero bytes, dropped high bits, or parity changes.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Flags field</term>
-      <listitem>
-       <para>
-32-bit integer bit mask to denote important aspects of the file format. Bits
-are numbered from 0 (<acronym>LSB</>) to 31 (<acronym>MSB</>).  Note that
-this field is stored in network byte order (most significant byte first),
-as are all the integer fields used in the file format.  Bits
-16-31 are reserved to denote critical file format issues; a reader
-should abort if it finds an unexpected bit set in this range. Bits 0-15
-are reserved to signal backwards-compatible format issues; a reader
-should simply ignore any unexpected bits set in this range. Currently
-only one flag bit is defined, and the rest must be zero:
-        <variablelist>
-         <varlistentry>
-          <term>Bit 16</term>
-          <listitem>
-           <para>
-            if 1, OIDs are included in the data; if 0, not
-           </para>
-          </listitem>
-         </varlistentry>
-        </variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Header extension area length</term>
-      <listitem>
-       <para>
-32-bit integer, length in bytes of remainder of header, not including self.
-Currently, this is zero, and the first tuple follows
-immediately.  Future changes to the format might allow additional data
-to be present in the header.  A reader should silently skip over any header
-extension data it does not know what to do with.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-    </para>
-
-    <para>
-The header extension area is envisioned to contain a sequence of
-self-identifying chunks.  The flags field is not intended to tell readers
-what is in the extension area.  Specific design of header extension contents
-is left for a later release.
-    </para>
-
-    <para>
-     This design allows for both backwards-compatible header additions (add
-     header extension chunks, or set low-order flag bits) and
-     non-backwards-compatible changes (set high-order flag bits to signal such
-     changes, and add supporting data to the extension area if needed).
-    </para>
-   </refsect3>
-
-   <refsect3>
-    <title>Tuples</title>
-    <para>
-Each tuple begins with a 16-bit integer count of the number of fields in the
-tuple.  (Presently, all tuples in a table will have the same count, but that
-might not always be true.)  Then, repeated for each field in the tuple, there
-is a 32-bit length word followed by that many bytes of field data.  (The
-length word does not include itself, and can be zero.)  As a special case,
--1 indicates a NULL field value.  No value bytes follow in the NULL case.
-    </para>
-
-    <para>
-There is no alignment padding or any other extra data between fields.
-    </para>
-
-    <para>
-Presently, all data values in a binary-format file are
-assumed to be in binary format (format code one).  It is anticipated that a
-future extension might add a header field that allows per-column format codes
-to be specified.
-    </para>
-
-    <para>
-To determine the appropriate binary format for the actual tuple data you
-<!## PG>
-should consult the <productname>PostgreSQL</productname> source, in
-<!## end>
-<!## XC>
-should consult the <productname>Postgres-XC</productname> source, in
-<!## end>
-<!## XL>
-should consult the <productname>Postgres-XL</productname> source, in
-<!## end>
-particular the <function>*send</> and <function>*recv</> functions for
-each column's data type (typically these functions are found in the
-<filename>src/backend/utils/adt/</filename> directory of the source
-distribution).
-    </para>
-
-    <para>
-If OIDs are included in the file, the OID field immediately follows the
-field-count word.  It is a normal field except that it's not included
-in the field-count.  In particular it has a length word &mdash; this will allow
-handling of 4-byte vs. 8-byte OIDs without too much pain, and will allow
-OIDs to be shown as null if that ever proves desirable.
-    </para>
-   </refsect3>
-
-   <refsect3>
-    <title>File Trailer</title>
-
-    <para>
-     The file trailer consists of a 16-bit integer word containing -1.  This
-     is easily distinguished from a tuple's field-count word.
-    </para>
-
-    <para>
-     A reader should report an error if a field-count word is neither -1
-     nor the expected number of columns.  This provides an extra
-     check against somehow getting out of sync with the data.
-    </para>
-   </refsect3>
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   The following example copies a table to the client
-   using the vertical bar (<literal>|</literal>) as the field delimiter:
-<programlisting>
-COPY country TO STDOUT (DELIMITER '|');
-</programlisting>
-  </para>
-
-  <para>
-   To copy data from a file into the <literal>country</> table:
-<programlisting>
-COPY country FROM '/usr1/proj/bray/sql/country_data';
-</programlisting>
-  </para>
-
-  <para>
-   To copy into a file just the countries whose names start with 'A':
-<programlisting>
-COPY (SELECT * FROM country WHERE country_name LIKE 'A%') TO '/usr1/proj/bray/sql/a_list_countries.copy';
-</programlisting>
-  </para>
-
-  <para>
-   Here is a sample of data suitable for copying into a table from
-   <literal>STDIN</literal>:
-<programlisting>
-AF      AFGHANISTAN
-AL      ALBANIA
-DZ      ALGERIA
-ZM      ZAMBIA
-ZW      ZIMBABWE
-</programlisting>
-   Note that the white space on each line is actually a tab character.
-  </para>
-
-  <para>
-   The following is the same data, output in binary format.
-   The data is shown after filtering through the
-   Unix utility <command>od -c</command>. The table has three columns;
-   the first has type <type>char(2)</type>, the second has type <type>text</type>,
-   and the third has type <type>integer</type>. All the rows have a null value
-   in the third column.
-<programlisting>
-0000000   P   G   C   O   P   Y  \n 377  \r  \n  \0  \0  \0  \0  \0  \0
-0000020  \0  \0  \0  \0 003  \0  \0  \0 002   A   F  \0  \0  \0 013   A
-0000040   F   G   H   A   N   I   S   T   A   N 377 377 377 377  \0 003
-0000060  \0  \0  \0 002   A   L  \0  \0  \0 007   A   L   B   A   N   I
-0000100   A 377 377 377 377  \0 003  \0  \0  \0 002   D   Z  \0  \0  \0
-0000120 007   A   L   G   E   R   I   A 377 377 377 377  \0 003  \0  \0
-0000140  \0 002   Z   M  \0  \0  \0 006   Z   A   M   B   I   A 377 377
-0000160 377 377  \0 003  \0  \0  \0 002   Z   W  \0  \0  \0  \b   Z   I
-0000200   M   B   A   B   W   E 377 377 377 377 377 377
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>COPY</command> statement in the SQL standard.
-  </para>
-
-  <para>
-   The following syntax was used before <productname>PostgreSQL</>
-   version 9.0 and is still supported:
-
-<synopsis>
-COPY <replaceable class="parameter">table_name</replaceable> [ ( <replaceable class="parameter">column</replaceable> [, ...] ) ]
-    FROM { '<replaceable class="parameter">filename</replaceable>' | STDIN }
-    [ [ WITH ]
-          [ BINARY ]
-          [ OIDS ]
-          [ DELIMITER [ AS ] '<replaceable class="parameter">delimiter</replaceable>' ]
-          [ NULL [ AS ] '<replaceable class="parameter">null string</replaceable>' ]
-          [ CSV [ HEADER ]
-                [ QUOTE [ AS ] '<replaceable class="parameter">quote</replaceable>' ]
-                [ ESCAPE [ AS ] '<replaceable class="parameter">escape</replaceable>' ]
-                [ FORCE NOT NULL <replaceable class="parameter">column</replaceable> [, ...] ] ] ]
-
-COPY { <replaceable class="parameter">table_name</replaceable> [ ( <replaceable class="parameter">column</replaceable> [, ...] ) ] | ( <replaceable class="parameter">query</replaceable> ) }
-    TO { '<replaceable class="parameter">filename</replaceable>' | STDOUT }
-    [ [ WITH ]
-          [ BINARY ]
-          [ OIDS ]
-          [ DELIMITER [ AS ] '<replaceable class="parameter">delimiter</replaceable>' ]
-          [ NULL [ AS ] '<replaceable class="parameter">null string</replaceable>' ]
-          [ CSV [ HEADER ]
-                [ QUOTE [ AS ] '<replaceable class="parameter">quote</replaceable>' ]
-                [ ESCAPE [ AS ] '<replaceable class="parameter">escape</replaceable>' ]
-                [ FORCE QUOTE { <replaceable class="parameter">column</replaceable> [, ...] | * } ] ] ]
-</synopsis>
-
-   Note that in this syntax, <literal>BINARY</> and <literal>CSV</> are
-   treated as independent keywords, not as arguments of a <literal>FORMAT</>
-   option.
-  </para>
-
-  <para>
-   The following syntax was used before <productname>PostgreSQL</>
-   version 7.3 and is still supported:
-
-<synopsis>
-COPY [ BINARY ] <replaceable class="parameter">table_name</replaceable> [ WITH OIDS ]
-    FROM { '<replaceable class="parameter">filename</replaceable>' | STDIN }
-    [ [USING] DELIMITERS '<replaceable class="parameter">delimiter</replaceable>' ]
-    [ WITH NULL AS '<replaceable class="parameter">null string</replaceable>' ]
-
-COPY [ BINARY ] <replaceable class="parameter">table_name</replaceable> [ WITH OIDS ]
-    TO { '<replaceable class="parameter">filename</replaceable>' | STDOUT }
-    [ [USING] DELIMITERS '<replaceable class="parameter">delimiter</replaceable>' ]
-    [ WITH NULL AS '<replaceable class="parameter">null string</replaceable>' ]
-</synopsis>
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_aggregate.sgmlin b/doc-xc/src/sgml/ref/create_aggregate.sgmlin
deleted file mode 100644
index 4346596e54..0000000000
--- a/doc-xc/src/sgml/ref/create_aggregate.sgmlin
+++ /dev/null
@@ -1,675 +0,0 @@
-<!--
-doc/src/sgml/ref/create_aggregate.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEAGGREGATE">
- <refmeta>
-  <refentrytitle>CREATE AGGREGATE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE AGGREGATE</refname>
-  <refpurpose>define a new aggregate function</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createaggregate">
-  <primary>CREATE AGGREGATE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<!## PG>
-<synopsis>
-CREATE AGGREGATE <replaceable class="PARAMETER">name</replaceable> ( <replaceable class="PARAMETER">input_data_type</replaceable> [ , ... ] ) (
-    SFUNC = <replaceable class="PARAMETER">sfunc</replaceable>,
-    STYPE = <replaceable class="PARAMETER">state_data_type</replaceable>
-    [ , FINALFUNC = <replaceable class="PARAMETER">ffunc</replaceable> ]
-    [ , INITCOND = <replaceable class="PARAMETER">initial_condition</replaceable> ]
-    [ , SORTOP = <replaceable class="PARAMETER">sort_operator</replaceable> ]
-)
-
-<phrase>or the old syntax</phrase>
-
-CREATE AGGREGATE <replaceable class="PARAMETER">name</replaceable> (
-    BASETYPE = <replaceable class="PARAMETER">base_type</replaceable>,
-    SFUNC = <replaceable class="PARAMETER">sfunc</replaceable>,
-    STYPE = <replaceable class="PARAMETER">state_data_type</replaceable>
-    [ , FINALFUNC = <replaceable class="PARAMETER">ffunc</replaceable> ]
-    [ , INITCOND = <replaceable class="PARAMETER">initial_condition</replaceable> ]
-    [ , SORTOP = <replaceable class="PARAMETER">sort_operator</replaceable> ]
-)
-</synopsis>
-<!## end>
-<!## XC>
-<synopsis>
-CREATE AGGREGATE <replaceable class="PARAMETER">name</replaceable> ( <replaceable class="PARAMETER">input_data_type</replaceable> [ , ... ] ) (
-    SFUNC = <replaceable class="PARAMETER">sfunc</replaceable>,
-    STYPE = <replaceable class="PARAMETER">state_data_type</replaceable>
-    [ , CFUNC = <replaceable class="PARAMETER">cfunc</replaceable> ]
-    [ , FINALFUNC = <replaceable class="PARAMETER">ffunc</replaceable> ]
-    [ , INITCOND = <replaceable class="PARAMETER">initial_condition</replaceable> ]
-    [ , INITCOLLECT = <replaceable class="PARAMETER">initial_collection_condition</replaceable> ]
-    [ , SORTOP = <replaceable class="PARAMETER">sort_operator</replaceable> ]
-)
-
-<phrase>or the old syntax</phrase>
-
-CREATE AGGREGATE <replaceable class="PARAMETER">name</replaceable> (
-    BASETYPE = <replaceable class="PARAMETER">base_type</replaceable>,
-    SFUNC = <replaceable class="PARAMETER">sfunc</replaceable>,
-    STYPE = <replaceable class="PARAMETER">state_data_type</replaceable>
-    [ , FINALFUNC = <replaceable class="PARAMETER">ffunc</replaceable> ]
-    [ , INITCOND = <replaceable class="PARAMETER">initial_condition</replaceable> ]
-    [ , SORTOP = <replaceable class="PARAMETER">sort_operator</replaceable> ]
-)
-</synopsis>
-<!## end>
-<!## XL>
-<synopsis>
-CREATE AGGREGATE <replaceable class="PARAMETER">name</replaceable> ( <replaceable class="PARAMETER">input_data_type</replaceable> [ , ... ] ) (
-    SFUNC = <replaceable class="PARAMETER">sfunc</replaceable>,
-    STYPE = <replaceable class="PARAMETER">state_data_type</replaceable>
-    [ , CFUNC = <replaceable class="PARAMETER">cfunc</replaceable> ]
-    [ , FINALFUNC = <replaceable class="PARAMETER">ffunc</replaceable> ]
-    [ , INITCOND = <replaceable class="PARAMETER">initial_condition</replaceable> ]
-    [ , INITCOLLECT = <replaceable class="PARAMETER">initial_collection_condition</replaceable> ]
-    [ , SORTOP = <replaceable class="PARAMETER">sort_operator</replaceable> ]
-)
-
-<phrase>or the old syntax</phrase>
-
-CREATE AGGREGATE <replaceable class="PARAMETER">name</replaceable> (
-    BASETYPE = <replaceable class="PARAMETER">base_type</replaceable>,
-    SFUNC = <replaceable class="PARAMETER">sfunc</replaceable>,
-    STYPE = <replaceable class="PARAMETER">state_data_type</replaceable>
-    [ , FINALFUNC = <replaceable class="PARAMETER">ffunc</replaceable> ]
-    [ , INITCOND = <replaceable class="PARAMETER">initial_condition</replaceable> ]
-    [ , SORTOP = <replaceable class="PARAMETER">sort_operator</replaceable> ]
-)
-</synopsis>
-<!## end>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>CREATE AGGREGATE</command> defines a new aggregate
-   function. Some basic and commonly-used aggregate functions are
-   included with the distribution; they are documented in <xref
-   linkend="functions-aggregate">. If one defines new types or needs
-   an aggregate function not already provided, then <command>CREATE
-   AGGREGATE</command> can be used to provide the desired features.
-  </para>
-
-  <para>
-   If a schema name is given (for example, <literal>CREATE AGGREGATE
-   myschema.myagg ...</>) then the aggregate function is created in the
-   specified schema.  Otherwise it is created in the current schema.
-  </para>
-
-  <para>
-   An aggregate function is identified by its name and input data type(s).
-   Two aggregates in the same schema can have the same name if they operate on
-   different input types.  The
-   name and input data type(s) of an aggregate must also be distinct from
-   the name and input data type(s) of every ordinary function in the same
-   schema.
-  </para>
-
-  <para>
-<!## PG>
-   An aggregate function is made from one or two ordinary
-<!## end>
-<!## XC>
-&xconly;
-   An aggregate function is made from one to maximum 3 ordinary
-<!## end>
-<!## XL>
-   An aggregate function is made from one to maximum 3 ordinary
-<!## end>
-   functions:
-   a state transition function
-   <replaceable class="PARAMETER">sfunc</replaceable>,
-<!## XC>
-   an optional collection function
-   <replaceable class="PARAMETER">cfunc</replaceable>,
-<!## end>
-<!## XL>
-   an optional collection function
-   <replaceable class="PARAMETER">cfunc</replaceable>,
-<!## end>
-   and an optional final calculation function
-   <replaceable class="PARAMETER">ffunc</replaceable>.
-   These are used as follows:
-<!## PG>
-<programlisting>
-<replaceable class="PARAMETER">sfunc</replaceable>( internal-state, next-data-values ) ---> next-internal-state
-<replaceable class="PARAMETER">ffunc</replaceable>( internal-state ) ---> aggregate-value
-</programlisting>
-<!## end>
-<!## XC>
-<programlisting>
-<replaceable class="PARAMETER">sfunc</replaceable>( internal-state, next-data-values ) ---> next-internal-state
-<replaceable class="PARAMETER">cfunc</replaceable>( internal-state, internal-state ) ---> next-internal-state
-<replaceable class="PARAMETER">ffunc</replaceable>( internal-state ) ---> aggregate-value
-</programlisting>
-<!## end>
-<!## XL>
-<programlisting>
-<replaceable class="PARAMETER">sfunc</replaceable>( internal-state, next-data-values ) ---> next-internal-state
-<replaceable class="PARAMETER">cfunc</replaceable>( internal-state, internal-state ) ---> next-internal-state
-<replaceable class="PARAMETER">ffunc</replaceable>( internal-state ) ---> aggregate-value
-</programlisting>
-<!## end>
-  </para>
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> creates a temporary variable
-<!## end>
-<!## XC>
-   In <productname>Postgres-XC</productname> the aggregation works in two
-   different modes. 
-   <itemizedlist>
-   <listitem>
-   <para>
-   Two phased aggregation - is used when the entire aggregation takes place on
-   the Coordinator node. In first phase called transition phase,
-   <productname>Postgres-XC</productname> creates a temporary variable
-<!## end>
-<!## XL>
-   In <productname>Postgres-XL</productname> the aggregation works in two
-   different modes. 
-   <itemizedlist>
-   <listitem>
-   <para>
-   Two phased aggregation - is used when the entire aggregation takes place on
-   the Coordinator node. In first phase called transition phase,
-   <productname>Postgres-XL</productname> creates a temporary variable
-<!## end>
-   of data type <replaceable class="PARAMETER">stype</replaceable>
-   to hold the current internal state of the aggregate.  At each input row,
-   the aggregate argument value(s) are calculated and
-   the state transition function is invoked with the current state value
-   and the new argument value(s) to calculate a new
-<!## PG>
-   internal state value.  After all the rows have been processed,
-   the final function is invoked once to calculate the aggregate's return
-   value.  If there is no final function then the ending state value
-   is returned as-is.
-<!## end>
-<!## XC>
-   internal state value.  After all the rows have been processed, in the second
-   phase or finalization phase the final function is invoked once to calculate
-   the aggregate's return value.  If there is no final function then the ending
-   state value is returned as-is.
-   </para>
-   </listitem>
-   <listitem>
-   <para>
-   Three phased aggregation - is used when the process of aggregation is divided
-   between Coordinator and Datanodes. In this mode, each 
-   <productname>Postgres-XC</productname> Datanode involved in the query carries
-   out the first phase named transition phase. This phase is similar to the first
-   phase in the two phased aggregation mode discussed above, except that, every
-   Datanode applies this phase on the rows available at the Datanode. The
-   result of transition phase is then transferred to the Coordinator node.
-   Second phase called collection phase takes place on the Coordinator.
-   <productname>Postgres-XC</productname> Coordinator node creates a temporary variable
-   of data type <replaceable class="PARAMETER">stype</replaceable>
-   to hold the current internal state of the collection phase.  For every input
-   from the Datanode (result of transition phase on that node), the collection
-   function is invoked with the current collection state value and the new
-   transition value (obtained from the Datanode) to calculate a new
-   internal collection state value.  After all the transition values from data
-   nodes have been processed, in the third or finalization phase the final
-   function is invoked once to calculate the aggregate's return
-   value.  If there is no final function then the ending collection state value
-   is returned as-is.
-   </para>
-   </listitem>
-   </itemizedlist>
-   Irrespective of the mode used for aggregation, the result of aggregation
-   should be same if the same set of data rows is participating in the
-   aggregate. <productname>Postgres-XC</productname> planner chooses the cheapest
-   feasible mode of the above two, during planning.
-<!## end>
-<!## XL>
-   internal state value.  After all the rows have been processed, in the second
-   phase or finalization phase the final function is invoked once to calculate
-   the aggregate's return value.  If there is no final function then the ending
-   state value is returned as-is.
-   </para>
-   </listitem>
-   <listitem>
-   <para>
-   Three phased aggregation - is used when the process of aggregation is divided
-   between Coordinator and Datanodes. In this mode, each 
-   <productname>Postgres-XL</productname> Datanode involved in the query carries
-   out the first phase named transition phase. This phase is similar to the first
-   phase in the two phased aggregation mode discussed above, except that, every
-   Datanode applies this phase on the rows available at the Datanode. The
-   result of transition phase is then transferred to the Coordinator node.
-   Second phase called collection phase takes place on the Coordinator.
-   <productname>Postgres-XL</productname> Coordinator node creates a temporary variable
-   of data type <replaceable class="PARAMETER">stype</replaceable>
-   to hold the current internal state of the collection phase.  For every input
-   from the Datanode (result of transition phase on that node), the collection
-   function is invoked with the current collection state value and the new
-   transition value (obtained from the Datanode) to calculate a new
-   internal collection state value.  After all the transition values from data
-   nodes have been processed, in the third or finalization phase the final
-   function is invoked once to calculate the aggregate's return
-   value.  If there is no final function then the ending collection state value
-   is returned as-is.
-   </para>
-   </listitem>
-   </itemizedlist>
-   Irrespective of the mode used for aggregation, the result of aggregation
-   should be same if the same set of data rows is participating in the
-   aggregate. <productname>Postgres-XL</productname> planner chooses the cheapest
-   feasible mode of the above two, during planning.
-<!## end>
-
-  </para>
-
-  <para>
-   An aggregate function can provide an initial condition,
-<!## PG>
-   that is, an initial value for the internal state value.
-   This is specified and stored in the database as a value of type
-<!## end>
-<!## XC>
-   that is, an initial value for the internal transition or collection state
-   value. This is specified and stored in the database as a value of type
-<!## end>
-<!## XL>
-&xlonly;
-   that is, an initial value for the internal transition or collection state
-   value. This is specified and stored in the database as a value of type
-<!## end>
-   <type>text</type>, but it must be a valid external representation
-   of a constant of the state value data type.  If it is not supplied
-   then the state value starts out null.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   If the collection function is declared <quote>strict</quote>,
-   then it cannot be called with null inputs.  With such a collection 
-   function, aggregate execution behaves as follows.  Null state transition
-   results are ignored (the function is not called and the previous collection
-   state value is retained).  If the initial state value is null, then at the
-   first non-null state transition result replaces the collection state
-   value, and the collection function is invoked at subsequent rows with
-   all-nonnull transition values.
-   This is handy for implementing aggregates like <function>max</function>.
-  </para>
-<!## end>  
-
-  <para>
-   If the state transition function is declared <quote>strict</quote>,
-   then it cannot be called with null inputs.  With such a transition
-   function, aggregate execution behaves as follows.  Rows with any null input
-   values are ignored (the function is not called and the previous state value
-   is retained).  If the initial state value is null, then at the first row
-   with all-nonnull input values, the first argument value replaces the state
-   value, and the transition function is invoked at subsequent rows with
-   all-nonnull input values.
-   This is handy for implementing aggregates like <function>max</function>.
-   Note that this behavior is only available when
-   <replaceable class="PARAMETER">state_data_type</replaceable>
-   is the same as the first
-   <replaceable class="PARAMETER">input_data_type</replaceable>.
-   When these types are different, you must supply a nonnull initial
-   condition or use a nonstrict transition function.
-  </para>
-
-<!## PG>
-  <para>
-   If the state transition function is not strict, then it will be called
-   unconditionally at each input row, and must deal with null inputs
-   and null transition values for itself.  This allows the aggregate
-   author to have full control over the aggregate's handling of null values.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   If the collection function is declared <quote>strict</quote>,
-   then it cannot be called with null inputs.  With such a collection 
-   function, aggregate execution behaves as follows.  Null state transition
-   results are ignored (the function is not called and the previous collection
-   state value is retained).  If the initial state value is null, then at the
-   first non-null state transition result replaces the collection state
-   value, and the collection function is invoked at subsequent rows with
-   all-nonnull transition values.
-   This is handy for implementing aggregates like <function>max</function>.
-  </para>
-<!## end>  
-
-  <para>
-   If the state transition function is declared <quote>strict</quote>,
-   then it cannot be called with null inputs.  With such a transition
-   function, aggregate execution behaves as follows.  Rows with any null input
-   values are ignored (the function is not called and the previous state value
-   is retained).  If the initial state value is null, then at the first row
-   with all-nonnull input values, the first argument value replaces the state
-   value, and the transition function is invoked at subsequent rows with
-   all-nonnull input values.
-   This is handy for implementing aggregates like <function>max</function>.
-   Note that this behavior is only available when
-   <replaceable class="PARAMETER">state_data_type</replaceable>
-   is the same as the first
-   <replaceable class="PARAMETER">input_data_type</replaceable>.
-   When these types are different, you must supply a nonnull initial
-   condition or use a nonstrict transition function.
-  </para>
-
-<!## PG>
-  <para>
-   If the state transition function is not strict, then it will be called
-   unconditionally at each input row, and must deal with null inputs
-   and null transition values for itself.  This allows the aggregate
-   author to have full control over the aggregate's handling of null values.
-  </para>
-<!## end>
-<!## XC>
-&xconly;
-  <para>
-   If the state transition and/or collection function is not strict, then it
-   will be called unconditionally at each input row, and must deal with null
-   inputs and null transition/collection values for itself.  This allows the
-   aggregate author to have full control over the aggregate's handling of null
-   values.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   If the state transition and/or collection function is not strict, then it
-   will be called unconditionally at each input row, and must deal with null
-   inputs and null transition/collection values for itself.  This allows the
-   aggregate author to have full control over the aggregate's handling of null
-   values.
-  </para>
-<!## end>
-
-  <para>
-   If the final function is declared <quote>strict</quote>, then it will not
-   be called when the ending state value is null; instead a null result
-   will be returned automatically.  (Of course this is just the normal
-   behavior of strict functions.)  In any case the final function has
-   the option of returning a null value.  For example, the final function for
-   <function>avg</function> returns null when it sees there were zero
-   input rows.
-  </para>
-
-  <para>
-   Aggregates that behave like <function>MIN</> or <function>MAX</> can
-   sometimes be optimized by looking into an index instead of scanning every
-   input row.  If this aggregate can be so optimized, indicate it by
-   specifying a <firstterm>sort operator</>.  The basic requirement is that
-   the aggregate must yield the first element in the sort ordering induced by
-   the operator; in other words:
-<programlisting>
-SELECT agg(col) FROM tab;
-</programlisting>
-   must be equivalent to:
-<programlisting>
-SELECT col FROM tab ORDER BY col USING sortop LIMIT 1;
-</programlisting>
-   Further assumptions are that the aggregate ignores null inputs, and that
-   it delivers a null result if and only if there were no non-null inputs.
-   Ordinarily, a data type's <literal>&lt;</> operator is the proper sort
-   operator for <function>MIN</>, and <literal>&gt;</> is the proper sort
-   operator for <function>MAX</>.  Note that the optimization will never
-   actually take effect unless the specified operator is the <quote>less
-   than</quote> or <quote>greater than</quote> strategy member of a B-tree
-   index operator class.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the aggregate function
-      to create.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">input_data_type</replaceable></term>
-    <listitem>
-&common;
-     <para>
-      An input data type on which this aggregate function operates.
-      To create a zero-argument aggregate function, write <literal>*</>
-      in place of the list of input data types.  (An example of such an
-      aggregate is <function>count(*)</function>.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">base_type</replaceable></term>
-    <listitem>
-&common;
-     <para>
-      In the old syntax for <command>CREATE AGGREGATE</>, the input data type
-      is specified by a <literal>basetype</> parameter rather than being
-      written next to the aggregate name.  Note that this syntax allows
-      only one input parameter.  To define a zero-argument aggregate function,
-      specify the <literal>basetype</> as
-      <literal>"ANY"</> (not <literal>*</>).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">sfunc</replaceable></term>
-    <listitem>
-&common;
-     <para>
-      The name of the state transition function to be called for each
-      input row.  For an <replaceable class="PARAMETER">N</>-argument
-      aggregate function, the <replaceable class="PARAMETER">sfunc</>
-      must take <replaceable class="PARAMETER">N</>+1 arguments,
-      the first being of type <replaceable
-      class="PARAMETER">state_data_type</replaceable> and the rest
-      matching the declared input data type(s) of the aggregate.
-      The function must return a value of type <replaceable
-      class="PARAMETER">state_data_type</replaceable>.  This function
-      takes the current state value and the current input data value(s),
-      and returns the next state value.
-     </para>
-    </listitem>
-   </varlistentry>
-
-<!## XC>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">cfunc</replaceable></term>
-    <listitem>
-&xconly;     
-     <para>
-      The name of the state collection function to be called for each
-      input row.  The <replaceable class="PARAMETER">sfunc</> must
-      take <replaceable class="PARAMETER">2 arguments</replaceable>, both of them
-      being of
-      type <replaceable class="PARAMETER">state_data_type</replaceable>.
-      The function must return a value of
-      type <replaceable class="PARAMETER">state_data_type</replaceable>.
-      This function takes the current collection state value and the
-      current transition value, and returns the next collection state
-      value.  If cfunc is omitted for an aggregate, the two phase
-      aggregation mode is used for that aggregate. All the aggregates
-      involed in a query use the same aggregation mode.
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-<!## XL>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">cfunc</replaceable></term>
-    <listitem>
-&xlonly;     
-     <para>
-      The name of the state collection function to be called for each
-      input row.  The <replaceable class="PARAMETER">sfunc</> must
-      take <replaceable class="PARAMETER">2 arguments</replaceable>, both of them
-      being of
-      type <replaceable class="PARAMETER">state_data_type</replaceable>.
-      The function must return a value of
-      type <replaceable class="PARAMETER">state_data_type</replaceable>.
-      This function takes the current collection state value and the
-      current transition value, and returns the next collection state
-      value.  If cfunc is omitted for an aggregate, the two phase
-      aggregation mode is used for that aggregate. All the aggregates
-      involed in a query use the same aggregation mode.
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">state_data_type</replaceable></term>
-    <listitem>
-     <para>
-      The data type for the aggregate's state value.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">ffunc</replaceable></term>
-    <listitem>
-&common;
-     <para>
-      The name of the final function called to compute the aggregate's
-      result after all input rows have been traversed.  The function
-      must take a single argument of type <replaceable
-      class="PARAMETER">state_data_type</replaceable>.  The return
-      data type of the aggregate is defined as the return type of this
-      function.  If <replaceable class="PARAMETER">ffunc</replaceable>
-      is not specified, then the ending state value is used as the
-      aggregate's result, and the return type is <replaceable
-      class="PARAMETER">state_data_type</replaceable>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">initial_condition</replaceable></term>
-    <listitem>
-&common;
-     <para>
-      The initial setting for the state value.  This must be a string
-      constant in the form accepted for the data type <replaceable
-      class="PARAMETER">state_data_type</replaceable>.  If not
-      specified, the state value starts out null.
-     </para>
-    </listitem>
-   </varlistentry>
-
-<!## XC>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">initial_collection_condition</replaceable></term>
-    <listitem>
-&xconly;
-     <para>
-      The initial setting for the state collection value.  This must
-      be a string constant in the form accepted for the data
-      type <replaceable class="PARAMETER">state_data_type</replaceable>.
-      If not specified, the collection state value starts out null. If
-      the collection
-      function <replaceable class="PARAMETER">cfunc</replaceable> is
-      not supplied, this parameter is stored but not used.
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-<!## XL>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">initial_collection_condition</replaceable></term>
-    <listitem>
-&xlonly;
-     <para>
-      The initial setting for the state collection value.  This must
-      be a string constant in the form accepted for the data
-      type <replaceable class="PARAMETER">state_data_type</replaceable>.
-      If not specified, the collection state value starts out null. If
-      the collection
-      function <replaceable class="PARAMETER">cfunc</replaceable> is
-      not supplied, this parameter is stored but not used.
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">sort_operator</replaceable></term>
-    <listitem>
-&common;
-     <para>
-      The associated sort operator for a <function>MIN</>- or
-      <function>MAX</>-like aggregate.
-      This is just an operator name (possibly schema-qualified).
-      The operator is assumed to have the same input data types as
-      the aggregate (which must be a single-argument aggregate).
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   The parameters of <command>CREATE AGGREGATE</command> can be
-   written in any order, not just the order illustrated above.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   See <xref linkend="xaggr">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-&common;
-  <para>
-   <command>CREATE AGGREGATE</command> is a
-<!## PG>
-   <productname>PostgreSQL</productname> language extension.  The SQL
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> language extension.  The SQL
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> language extension.  The SQL
-<!## end>
-   standard does not provide for user-defined aggregate functions.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alteraggregate"></member>
-   <member><xref linkend="sql-dropaggregate"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_barrier.sgmlin b/doc-xc/src/sgml/ref/create_barrier.sgmlin
deleted file mode 100644
index 8e23be536b..0000000000
--- a/doc-xc/src/sgml/ref/create_barrier.sgmlin
+++ /dev/null
@@ -1,113 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_barrier.sgml,v 1.54 2010/04/03 07:22:58 petere Exp $
-PostgreSQL documentation
--->
-<!## XC>
-<refentry id="SQL-CREATEBARRIER">
- <refmeta>
-  <refentrytitle>CREATE BARRIER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE BARRIER</refname>
-  <refpurpose>create a new barrier</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createbarrier">
-  <primary>CREATE BARRIER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE BARRIER <replaceable class="PARAMETER">barrier_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xconly;
-
-  <para>
-   <command>CREATE BARRIER</command> is new SQL query specific
-   to <productname>Postgres-XC</productname> since 0.9.5 that creates
-   a new XLOG record on each node of the cluster consistently. Barrier
-   is created via a 2PC like mechanism from a remote Coordinator in 3
-   phases with a prepare, execute and ending phases.  A new recovery
-   parameter called recovery_target_barrier has been added in
-   recovery.conf. In order to perform a complete PITR recovery, it is
-   necessary to set recovery_target_barrier to the value of a barrier
-   already created. Then distribute recovery.conf to each data folder
-   of each node, and then to restart the nodes one by one.
-  </para>
-
-  <para>
-   Default barrier name is <literal>dummy_barrier_id</literal>. It is
-   used when no barrier name is specified when using <command>CREATE
-   BARRIER</command>.
-  </para>
-  
- </refsect1>
-
-</refentry>
-<!## end>
-<!## XL>
-<refentry id="SQL-CREATEBARRIER">
- <refmeta>
-  <refentrytitle>CREATE BARRIER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE BARRIER</refname>
-  <refpurpose>create a new barrier</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createbarrier">
-  <primary>CREATE BARRIER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE BARRIER <replaceable class="PARAMETER">barrier_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xlonly;
-
-  <para>
-   <command>CREATE BARRIER</command> is new SQL command specific
-   to <productname>Postgres-XL</productname> that creates
-   a new XLOG record on each node of the cluster consistently. 
-   Essentially a barrier is a consistent point in the cluster that
-   you can recover to. Note that these are currently created manually,
-   not autoatically. Without barriers, if you recover an individual 
-   component, it may be possible that it is not consistent with the
-   other nodes depending on when it was committed.
-  </para>
-  <para>A barrier
-   is created via a 2PC-like mechanism from a remote Coordinator in 3
-   phases with a prepare, execute and ending phases.  A new recovery
-   parameter called recovery_target_barrier has been added in
-   recovery.conf. In order to perform a complete PITR recovery, it is
-   necessary to set recovery_target_barrier to the value of a barrier
-   already created. Then distribute recovery.conf to each data folder
-   of each node, and then to restart the nodes one by one.
-  </para>
-
-  <para>
-   The default barrier name is <literal>dummy_barrier_id</literal>. It is
-   used when no barrier name is specified when using <command>CREATE
-   BARRIER</command>.
-  </para>
-  
- </refsect1>
-
-</refentry>
-<!## end>
diff --git a/doc-xc/src/sgml/ref/create_cast.sgmlin b/doc-xc/src/sgml/ref/create_cast.sgmlin
deleted file mode 100644
index f7293498ea..0000000000
--- a/doc-xc/src/sgml/ref/create_cast.sgmlin
+++ /dev/null
@@ -1,458 +0,0 @@
-<!-- doc/src/sgml/ref/create_cast.sgml -->
-
-<refentry id="SQL-CREATECAST">
- <refmeta>
-  <refentrytitle>CREATE CAST</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE CAST</refname>
-  <refpurpose>define a new cast</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createcast">
-  <primary>CREATE CAST</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE CAST (<replaceable>source_type</replaceable> AS <replaceable>target_type</replaceable>)
-    WITH FUNCTION <replaceable>function_name</replaceable> (<replaceable>argument_type</replaceable> [, ...])
-    [ AS ASSIGNMENT | AS IMPLICIT ]
-
-CREATE CAST (<replaceable>source_type</replaceable> AS <replaceable>target_type</replaceable>)
-    WITHOUT FUNCTION
-    [ AS ASSIGNMENT | AS IMPLICIT ]
-
-CREATE CAST (<replaceable>source_type</replaceable> AS <replaceable>target_type</replaceable>)
-    WITH INOUT
-    [ AS ASSIGNMENT | AS IMPLICIT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-createcast-description">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE CAST</command> defines a new cast.  A cast
-   specifies how to perform a conversion between
-   two data types.  For example,
-<programlisting>
-SELECT CAST(42 AS float8);
-</programlisting>
-   converts the integer constant 42 to type <type>float8</type> by
-   invoking a previously specified function, in this case
-   <literal>float8(int4)</>. (If no suitable cast has been defined, the
-   conversion fails.)
-  </para>
-
-  <para>
-   Two types can be <firstterm>binary coercible</firstterm>, which
-   means that the conversion can be performed <quote>for free</quote>
-   without invoking any function.  This requires that corresponding
-   values use the same internal representation.  For instance, the
-   types <type>text</type> and <type>varchar</type> are binary
-   coercible both ways.  Binary coercibility is not necessarily a
-   symmetric relationship.  For example, the cast
-   from <type>xml</type> to <type>text</type> can be performed for
-   free in the present implementation, but the reverse direction
-   requires a function that performs at least a syntax check.  (Two
-   types that are binary coercible both ways are also referred to as
-   binary compatible.)
-  </para>
-
-  <para>
-   You can define a cast as an <firstterm>I/O conversion cast</> by using
-   the <literal>WITH INOUT</literal> syntax. An I/O conversion cast is
-   performed by invoking the output function of the source data type, and
-   passing the resulting string to the input function of the target data type.
-   In many common cases, this feature avoids the need to write a separate
-   cast function for conversion. An I/O conversion cast acts the same as
-   a regular function-based cast; only the implementation is different.
-  </para>
-
-  <para>
-   By default, a cast can be invoked only by an explicit cast request,
-   that is an explicit <literal>CAST(<replaceable>x</> AS
-   <replaceable>typename</>)</literal> or
-   <replaceable>x</><literal>::</><replaceable>typename</>
-   construct.
-  </para>
-
-  <para>
-   If the cast is marked <literal>AS ASSIGNMENT</> then it can be invoked
-   implicitly when assigning a value to a column of the target data type.
-   For example, supposing that <literal>foo.f1</literal> is a column of
-   type <type>text</type>, then:
-<programlisting>
-INSERT INTO foo (f1) VALUES (42);
-</programlisting>
-   will be allowed if the cast from type <type>integer</type> to type
-   <type>text</type> is marked <literal>AS ASSIGNMENT</>, otherwise not.
-   (We generally use the term <firstterm>assignment
-   cast</firstterm> to describe this kind of cast.)
-  </para>
-
-  <para>
-   If the cast is marked <literal>AS IMPLICIT</> then it can be invoked
-   implicitly in any context, whether assignment or internally in an
-   expression.  (We generally use the term <firstterm>implicit
-   cast</firstterm> to describe this kind of cast.)
-   For example, consider this query:
-<programlisting>
-SELECT 2 + 4.0;
-</programlisting>
-   The parser initially marks the constants as being of type <type>integer</>
-   and <type>numeric</> respectively.  There is no <type>integer</>
-   <literal>+</> <type>numeric</> operator in the system catalogs,
-   but there is a <type>numeric</> <literal>+</> <type>numeric</> operator.
-   The query will therefore succeed if a cast from <type>integer</> to
-   <type>numeric</> is available and is marked <literal>AS IMPLICIT</> &mdash;
-   which in fact it is.  The parser will apply the implicit cast and resolve
-   the query as if it had been written
-<programlisting>
-SELECT CAST ( 2 AS numeric ) + 4.0;
-</programlisting>
-  </para>
-
-  <para>
-   Now, the catalogs also provide a cast from <type>numeric</> to
-   <type>integer</>.  If that cast were marked <literal>AS IMPLICIT</> &mdash;
-   which it is not &mdash; then the parser would be faced with choosing
-   between the above interpretation and the alternative of casting the
-   <type>numeric</> constant to <type>integer</> and applying the
-   <type>integer</> <literal>+</> <type>integer</> operator.  Lacking any
-   knowledge of which choice to prefer, it would give up and declare the
-   query ambiguous.  The fact that only one of the two casts is
-   implicit is the way in which we teach the parser to prefer resolution
-   of a mixed <type>numeric</>-and-<type>integer</> expression as
-   <type>numeric</>; there is no built-in knowledge about that.
-  </para>
-
-  <para>
-   It is wise to be conservative about marking casts as implicit.  An
-   overabundance of implicit casting paths can cause
-<!## PG>
-   <productname>PostgreSQL</productname> to choose surprising
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> to choose surprising
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> to choose surprising
-<!## end>
-   interpretations of commands, or to be unable to resolve commands at
-   all because there are multiple possible interpretations.  A good
-   rule of thumb is to make a cast implicitly invokable only for
-   information-preserving transformations between types in the same
-   general type category.  For example, the cast from <type>int2</type> to
-   <type>int4</type> can reasonably be implicit, but the cast from
-   <type>float8</type> to <type>int4</type> should probably be
-   assignment-only.  Cross-type-category casts, such as <type>text</>
-   to <type>int4</>, are best made explicit-only.
-  </para>
-
-  <note>
-   <para>
-    Sometimes it is necessary for usability or standards-compliance reasons
-    to provide multiple implicit casts among a set of types, resulting in
-    ambiguity that cannot be avoided as above.  The parser has a fallback
-    heuristic based on <firstterm>type categories</> and <firstterm>preferred
-    types</> that can help to provide desired behavior in such cases.  See
-    <xref linkend="sql-createtype"> for
-    more information.
-   </para>
-  </note>
-
-  <para>
-   To be able to create a cast, you must own the source or the target
-   data type.  To create a binary-coercible cast, you must be superuser.
-   (This restriction is made because an erroneous binary-coercible cast
-   conversion can easily crash the server.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><replaceable>source_type</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the source data type of the cast.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>target_type</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the target data type of the cast.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>function_name</replaceable>(<replaceable>argument_type</replaceable> [, ...])</term>
-
-     <listitem>
-      <para>
-       The function used to perform the cast.  The function name can
-       be schema-qualified.  If it is not, the function will be looked
-       up in the schema search path.  The function's result data type must
-       match the target type of the cast.   Its arguments are discussed below.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>WITHOUT FUNCTION</literal></term>
-
-     <listitem>
-      <para>
-       Indicates that the source type is binary-coercible to the target type,
-       so no function is required to perform the cast.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>WITH INOUT</literal></term>
-
-     <listitem>
-      <para>
-       Indicates that the cast is an I/O conversion cast, performed by
-       invoking the output function of the source data type, and passing the
-       resulting string to the input function of the target data type.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>AS ASSIGNMENT</literal></term>
-
-     <listitem>
-      <para>
-       Indicates that the cast can be invoked implicitly in assignment
-       contexts.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>AS IMPLICIT</literal></term>
-
-     <listitem>
-      <para>
-       Indicates that the cast can be invoked implicitly in any context.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-  <para>
-   Cast implementation functions can have one to three arguments.
-   The first argument type must be identical to or binary-coercible from
-   the cast's source type.  The second argument,
-   if present, must be type <type>integer</>; it receives the type
-   modifier associated with the destination type, or <literal>-1</>
-   if there is none.  The third argument,
-   if present, must be type <type>boolean</>; it receives <literal>true</>
-   if the cast is an explicit cast, <literal>false</> otherwise.
-   (Bizarrely, the SQL standard demands different behaviors for explicit and
-   implicit casts in some cases.  This argument is supplied for functions
-   that must implement such casts.  It is not recommended that you design
-   your own data types so that this matters.)
-  </para>
-
-  <para>
-   The return type of a cast function must be identical to or
-   binary-coercible to the cast's target type.
-  </para>
-
-  <para>
-   Ordinarily a cast must have different source and target data types.
-   However, it is allowed to declare a cast with identical source and
-   target types if it has a cast implementation function with more than one
-   argument.  This is used to represent type-specific length coercion
-   functions in the system catalogs.  The named function is used to
-   coerce a value of the type to the type modifier value given by its
-   second argument.
-  </para>
-
-  <para>
-   When a cast has different source and
-   target types and a function that takes more than one argument, it
-   supports converting from one type to another and applying a length
-   coercion in a single step.  When no such entry is available, coercion
-   to a type that uses a type modifier involves two cast steps, one to
-   convert between data types and a second to apply the modifier.
-  </para>
-
- </refsect1>
-
- <refsect1 id="sql-createcast-notes">
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="sql-dropcast"> to remove user-defined casts.
-  </para>
-
-  <para>
-   Remember that if you want to be able to convert types both ways you
-   need to declare casts both ways explicitly.
-  </para>
-
- <indexterm zone="sql-createcast">
-  <primary>cast</primary>
-  <secondary>I/O conversion</secondary>
- </indexterm>
-
-  <para>
-   It is normally not necessary to create casts between user-defined types
-   and the standard string types (<type>text</>, <type>varchar</>, and
-   <type>char(<replaceable>n</>)</type>, as well as user-defined types that
-<!## PG>
-   are defined to be in the string category).  <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-   are defined to be in the string category).  <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-   are defined to be in the string category).  <productname>Postgres-XL</>
-<!## end>
-   provides automatic I/O conversion casts for that. The automatic casts to
-   string types are treated as assignment casts, while the automatic casts
-   from string types are
-   explicit-only.  You can override this behavior by declaring your own
-   cast to replace an automatic cast, but usually the only reason to
-   do so is if you want the conversion to be more easily invokable than the
-   standard assignment-only or explicit-only setting.  Another possible
-   reason is that you want the conversion to behave differently from the
-   type's I/O function; but that is sufficiently surprising that you
-   should think twice about whether it's a good idea.  (A small number of
-   the built-in types do indeed have different behaviors for conversions,
-   mostly because of requirements of the SQL standard.)
-  </para>
-
-  <para>
-   Prior to <productname>PostgreSQL</> 7.3, every function that had
-   the same name as a data type, returned that data type, and took one
-   argument of a different type was automatically a cast function.
-   This convention has been abandoned in face of the introduction of
-   schemas and to be able to represent binary-coercible casts in the
-   system catalogs.  The built-in cast functions still follow this naming
-   scheme, but they have to be shown as casts in the system catalog
-   <structname>pg_cast</> as well.
-  </para>
-
-  <para>
-   While not required, it is recommended that you continue to follow this old
-   convention of naming cast implementation functions after the target data
-   type.  Many users are used to being able to cast data types using a
-   function-style notation, that is
-   <replaceable>typename</>(<replaceable>x</>).  This notation is in fact
-   nothing more nor less than a call of the cast implementation function; it
-   is not specially treated as a cast.  If your conversion functions are not
-   named to support this convention then you will have surprised users.
-<!## PG>
-   Since <productname>PostgreSQL</> allows overloading of the same function
-<!## end>
-<!## XC>
-   Since <productname>Postgres-XC</> allows overloading of the same function
-<!## end>
-<!## XL>
-   Since <productname>Postgres-XL</> allows overloading of the same function
-<!## end>
-   name with different argument types, there is no difficulty in having
-   multiple conversion functions from different types that all use the
-   target type's name.
-  </para>
-
-  <note>
-   <para>
-    Actually the preceding paragraph is an oversimplification: there are
-    two cases in which a function-call construct will be treated as a cast
-    request without having matched it to an actual function.
-    If a function call <replaceable>name</>(<replaceable>x</>) does not
-    exactly match any existing function, but <replaceable>name</> is the name
-    of a data type and <structname>pg_cast</> provides a binary-coercible cast
-    to this type from the type of <replaceable>x</>, then the call will be
-    construed as a binary-coercible cast.  This exception is made so that
-    binary-coercible casts can be invoked using functional syntax, even
-    though they lack any function.  Likewise, if there is no
-    <structname>pg_cast</> entry but the cast would be to or from a string
-    type, the call will be construed as an I/O conversion cast.  This
-    exception allows I/O conversion casts to be invoked using functional
-    syntax.
-   </para>
-  </note>
-
-  <note>
-   <para>
-    There is also an exception to the exception: I/O conversion casts from
-    composite types to string types cannot be invoked using functional
-    syntax, but must be written in explicit cast syntax (either
-    <literal>CAST</> or <literal>::</> notation).  This exception was added
-    because after the introduction of automatically-provided I/O conversion
-    casts, it was found too easy to accidentally invoke such a cast when
-    a function or column reference was intended.
-   </para>
-  </note>
- </refsect1>
-
-
- <refsect1 id="sql-createcast-examples">
-  <title>Examples</title>
-
-  <para>
-   To create an assignment cast from type <type>bigint</type> to type
-   <type>int4</type> using the function <literal>int4(bigint)</literal>:
-<programlisting>
-CREATE CAST (bigint AS int4) WITH FUNCTION int4(bigint) AS ASSIGNMENT;
-</programlisting>
-   (This cast is already predefined in the system.)
-  </para>
- </refsect1>
-
- <refsect1 id="sql-createcast-compat">
-  <title>Compatibility</title>
-
-  <para>
-   The <command>CREATE CAST</command> command conforms to the
-   <acronym>SQL</acronym> standard,
-   except that SQL does not make provisions for binary-coercible
-   types or extra arguments to implementation functions.
-<!## PG>
-   <literal>AS IMPLICIT</> is a <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   <literal>AS IMPLICIT</> is a <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   <literal>AS IMPLICIT</> is a <productname>Postgres-XL</productname>
-<!## end>
-   extension, too.
-  </para>
- </refsect1>
-
-
- <refsect1 id="sql-createcast-seealso">
-  <title>See Also</title>
-
-  <para>
-   <xref linkend="sql-createfunction">,
-   <xref linkend="sql-createtype">,
-   <xref linkend="sql-dropcast">
-  </para>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_collation.sgmlin b/doc-xc/src/sgml/ref/create_collation.sgmlin
deleted file mode 100644
index c853576814..0000000000
--- a/doc-xc/src/sgml/ref/create_collation.sgmlin
+++ /dev/null
@@ -1,177 +0,0 @@
-<!-- doc/src/sgml/ref/create_collation.sgml -->
-
-<refentry id="SQL-CREATECOLLATION">
- <refmeta>
-  <refentrytitle>CREATE COLLATION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE COLLATION</refname>
-  <refpurpose>define a new collation</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createcollation">
-  <primary>CREATE COLLATION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE COLLATION <replaceable>name</replaceable> (
-    [ LOCALE = <replaceable>locale</replaceable>, ]
-    [ LC_COLLATE = <replaceable>lc_collate</replaceable>, ]
-    [ LC_CTYPE = <replaceable>lc_ctype</replaceable> ]
-)
-CREATE COLLATION <replaceable>name</replaceable> FROM <replaceable>existing_collation</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-createcollation-description">
-  <title>Description</title>
-
-  <para>
-   <command>CREATE COLLATION</command> defines a new collation using
-   the specified operating system locale settings,
-   or by copying an existing collation.
- </para>
-
-  <para>
-   To be able to create a collation, you must
-   have <literal>CREATE</literal> privilege on the destination schema.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Parameters</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><replaceable>name</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the collation. The collation name can be
-       schema-qualified. If it is not, the collation is defined in the
-       current schema. The collation name must be unique within that
-       schema.  (The system catalogs can contain collations with the
-       same name for other encodings, but these are ignored if the
-       database encoding does not match.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>locale</replaceable></term>
-
-     <listitem>
-      <para>
-       This is a shortcut for setting <symbol>LC_COLLATE</symbol>
-       and <symbol>LC_CTYPE</symbol> at once.  If you specify this,
-       you cannot specify either of those parameters.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>lc_collate</replaceable></term>
-
-     <listitem>
-      <para>
-       Use the specified operating system locale for
-       the <symbol>LC_COLLATE</symbol> locale category.  The locale
-       must be applicable to the current database encoding.
-       (See <xref linkend="sql-createdatabase"> for the precise
-       rules.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>lc_ctype</replaceable></term>
-
-     <listitem>
-      <para>
-       Use the specified operating system locale for
-       the <symbol>LC_CTYPE</symbol> locale category.  The locale
-       must be applicable to the current database encoding.
-       (See <xref linkend="sql-createdatabase"> for the precise
-       rules.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>existing_collation</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of an existing collation to copy.  The new collation
-       will have the same properties as the existing one, but it
-       will be an independent object.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
- </refsect1>
-
-
- <refsect1 id="sql-createcollation-notes">
-  <title>Notes</title>
-
-  <para>
-   Use <command>DROP COLLATION</command> to remove user-defined collations.
-  </para>
-
-  <para>
-   See <xref linkend="collation"> for more information about collation
-   support in PostgreSQL.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-createcollation-examples">
-  <title>Examples</title>
-
-  <para>
-   To create a collation from the operating system locale
-   <literal>fr_FR.utf8</literal>
-   (assuming the current database encoding is <literal>UTF8</literal>):
-<programlisting>
-CREATE COLLATION french (LOCALE = 'fr_FR.utf8');
-</programlisting>
-  </para>
-
-  <para>
-   To create a collation from an existing collation:
-<programlisting>
-CREATE COLLATION german FROM "de_DE";
-</programlisting>
-   This can be convenient to be able to use operating-system-independent
-   collation names in applications.
-  </para>
- </refsect1>
-
-
- <refsect1 id="sql-createcollation-compat">
-  <title>Compatibility</title>
-
-  <para>
-   There is a <command>CREATE COLLATION</command> statement in the SQL
-   standard, but it is limited to copying an existing collation.  The
-   syntax to create a new collation is
-   a <productname>PostgreSQL</productname> extension.
-  </para>
- </refsect1>
-
-
- <refsect1 id="sql-createcollation-seealso">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altercollation"></member>
-   <member><xref linkend="sql-dropcollation"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_conversion.sgmlin b/doc-xc/src/sgml/ref/create_conversion.sgmlin
deleted file mode 100644
index 59fa1bcd53..0000000000
--- a/doc-xc/src/sgml/ref/create_conversion.sgmlin
+++ /dev/null
@@ -1,182 +0,0 @@
-<!-- doc/src/sgml/ref/create_conversion.sgml -->
-
-<refentry id="SQL-CREATECONVERSION">
- <refmeta>
-  <refentrytitle>CREATE CONVERSION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE CONVERSION</refname>
-  <refpurpose>define a new encoding conversion</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createconversion">
-  <primary>CREATE CONVERSION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE [ DEFAULT ] CONVERSION <replaceable>name</replaceable>
-    FOR <replaceable>source_encoding</replaceable> TO <replaceable>dest_encoding</replaceable> FROM <replaceable>function_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-createconversion-description">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE CONVERSION</command> defines a new conversion between
-   character set encodings.  Also, conversions that
-   are marked <literal>DEFAULT</> can be used for automatic encoding
-   conversion between
-   client and server. For this purpose, two conversions, from encoding A to
-   B <emphasis>and</emphasis> from encoding B to A, must be defined.
- </para>
-
-  <para>
-   To be able to create a conversion, you must have <literal>EXECUTE</literal> privilege
-   on the function and <literal>CREATE</literal> privilege on the destination schema.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Parameters</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>DEFAULT</literal></term>
-
-     <listitem>
-      <para>
-       The <literal>DEFAULT</> clause indicates that this conversion
-       is the default for this particular source to destination
-       encoding. There should be only one default encoding in a schema
-       for the encoding pair.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>name</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the conversion. The conversion name can be
-       schema-qualified. If it is not, the conversion is defined in the
-       current schema. The conversion name must be unique within a
-       schema.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>source_encoding</replaceable></term>
-
-     <listitem>
-      <para>
-       The source encoding name.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>dest_encoding</replaceable></term>
-
-     <listitem>
-      <para>
-       The destination encoding name.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>function_name</replaceable></term>
-
-     <listitem>
-      <para>
-       The function used to perform the conversion.  The function name can
-       be schema-qualified.  If it is not, the function will be looked
-       up in the path.
-      </para>
-
-      <para>
-       The function must have the following signature:
-
-<programlisting>
-conv_proc(
-    integer,  -- source encoding ID
-    integer,  -- destination encoding ID
-    cstring,  -- source string (null terminated C string)
-    internal, -- destination (fill with a null terminated C string)
-    integer   -- source string length
-) RETURNS void;
-</programlisting>
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
- </refsect1>
-
- <refsect1 id="sql-createconversion-notes">
-  <title>Notes</title>
-
-  <para>
-   Use <command>DROP CONVERSION</command> to remove user-defined conversions.
-  </para>
-
-  <para>
-   The privileges required to create a conversion might be changed in a future
-   release.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-createconversion-examples">
-  <title>Examples</title>
-
-  <para>
-   To create a conversion from encoding <literal>UTF8</literal> to
-   <literal>LATIN1</literal> using <function>myfunc</>:
-<programlisting>
-CREATE CONVERSION myconv FOR 'UTF8' TO 'LATIN1' FROM myfunc;
-</programlisting>
-  </para>
- </refsect1>
-
-
- <refsect1 id="sql-createconversion-compat">
-  <title>Compatibility</title>
-
-  <para>
-    <command>CREATE CONVERSION</command>
-<!## PG>
-    is a <productname>PostgreSQL</productname> extension.
-<!## end>
-<!## XC>
-    is a <productname>Postgres-XC</productname> extension.
-<!## end>
-<!## XL>
-    is a <productname>Postgres-XL</productname> extension.
-<!## end>
-    There is no <command>CREATE CONVERSION</command>
-    statement in the SQL standard, but a <command>CREATE TRANSLATION</command>
-    statement that is very similar in purpose and syntax.
-  </para>
- </refsect1>
-
-
- <refsect1 id="sql-createconversion-seealso">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterconversion"></member>
-   <member><xref linkend="sql-createfunction"></member>
-   <member><xref linkend="sql-dropconversion"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_database.sgmlin b/doc-xc/src/sgml/ref/create_database.sgmlin
deleted file mode 100644
index 99a2a75693..0000000000
--- a/doc-xc/src/sgml/ref/create_database.sgmlin
+++ /dev/null
@@ -1,340 +0,0 @@
-<!--
-doc/src/sgml/ref/create_database.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEDATABASE">
- <refmeta>
-  <refentrytitle>CREATE DATABASE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE DATABASE</refname>
-  <refpurpose>create a new database</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createdatabase">
-  <primary>CREATE DATABASE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
-    [ [ WITH ] [ OWNER [=] <replaceable class="parameter">user_name</replaceable> ]
-           [ TEMPLATE [=] <replaceable class="parameter">template</replaceable> ]
-           [ ENCODING [=] <replaceable class="parameter">encoding</replaceable> ]
-           [ LC_COLLATE [=] <replaceable class="parameter">lc_collate</replaceable> ]
-           [ LC_CTYPE [=] <replaceable class="parameter">lc_ctype</replaceable> ]
-           [ TABLESPACE [=] <replaceable class="parameter">tablespace</replaceable> ]
-           [ CONNECTION LIMIT [=] <replaceable class="parameter">connlimit</replaceable> ] ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE DATABASE</command> creates a new
-<!## PG>
-   <productname>PostgreSQL</productname> database.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> database.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> database.
-<!## end>
-  </para>
-
-  <para>
-   To create a database, you must be a superuser or have the special
-   <literal>CREATEDB</> privilege.
-   See <xref linkend="SQL-CREATEUSER">.
-  </para>
-
-  <para>
-   Normally, the creator becomes the owner of the new database.
-   Superusers can create databases owned by other users, by using the
-   <literal>OWNER</> clause. They can even create databases owned by
-   users with no special privileges. Non-superusers with <literal>CREATEDB</>
-   privilege can only create databases owned by themselves.
-  </para>
-
-  <para>
-   By default, the new database will be created by cloning the standard
-   system database <literal>template1</>.  A different template can be
-   specified by writing <literal>TEMPLATE
-   <replaceable class="parameter">name</replaceable></literal>.  In particular,
-   by writing <literal>TEMPLATE template0</>, you can create a virgin
-   database containing only the standard objects predefined by your
-<!## PG>
-   version of <productname>PostgreSQL</productname>.  This is useful
-<!## end>
-<!## XC>
-   version of <productname>Postgres-XC</productname>.  This is useful
-<!## end>
-<!## XL>
-   version of <productname>Postgres-XL</productname>.  This is useful
-<!## end>
-   if you wish to avoid copying
-   any installation-local objects that might have been added to
-   <literal>template1</>.
-  </para>
-
-<!## XC>
-&xconly;
-   <para>
-    If there's any live connection to any of the template database in
-    Coordinator or Datanode, you will have an error message.  In this
-    case, you should clean these connections using <command>CLEAN
-    CONNECTION</> statement.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    If there are any live connections to any one of the template databases in
-    a Coordinator or Datanode, you will receive an error message.  In this
-    case, you should clean these connections using <command>CLEAN
-    CONNECTION</> statement.
-   </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">name</replaceable></term>
-      <listitem>
-       <para>
-        The name of a database to create.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">use_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the database user who will own the new database,
-        or <literal>DEFAULT</literal> to use the default (namely, the
-        user executing the command).
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">template</replaceable></term>
-      <listitem>
-       <para>
-        The name of the template from which to create the new database,
-        or <literal>DEFAULT</literal> to use the default template
-        (<literal>template1</literal>).
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">encoding</replaceable></term>
-      <listitem>
-       <para>
-        Character set encoding to use in the new database.  Specify
-        a string constant (e.g., <literal>'SQL_ASCII'</literal>),
-        or an integer encoding number, or <literal>DEFAULT</literal>
-        to use the default encoding (namely, the encoding of the
-        template database). The character sets supported by the
-<!## PG>
-        <productname>PostgreSQL</productname> server are described in
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> server are described in
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> server are described in
-<!## end>
-        <xref linkend="multibyte-charset-supported">. See below for
-        additional restrictions.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">lc_collate</replaceable></term>
-      <listitem>
-       <para>
-        Collation order (<literal>LC_COLLATE</>) to use in the new database.
-        This affects the sort order applied to strings, e.g. in queries with
-        ORDER BY, as well as the order used in indexes on text columns.
-        The default is to use the collation order of the template database.
-        See below for additional restrictions.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">lc_ctype</replaceable></term>
-      <listitem>
-       <para>
-        Character classification (<literal>LC_CTYPE</>) to use in the new
-        database. This affects the categorization of characters, e.g. lower,
-        upper and digit. The default is to use the character classification of
-        the template database. See below for additional restrictions.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">tablespace</replaceable></term>
-      <listitem>
-       <para>
-        The name of the tablespace that will be associated with the
-        new database, or <literal>DEFAULT</literal> to use the
-        template database's tablespace. This
-        tablespace will be the default tablespace used for objects
-        created in this database. See
-        <xref linkend="sql-createtablespace">
-        for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">connlimit</replaceable></term>
-      <listitem>
-       <para>
-        How many concurrent connections can be made
-        to this database.  -1 (the default) means no limit.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-  <para>
-   Optional parameters can be written in any order, not only the order
-   illustrated above.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    <command>CREATE DATABASE</> cannot be executed inside a transaction
-    block.
-   </para>
-
-   <para>
-    Errors along the line of <quote>could not initialize database directory</>
-    are most likely related to insufficient permissions on the data
-    directory, a full disk, or other file system problems.
-   </para>
-
-   <para>
-    Use <xref linkend="SQL-DROPDATABASE"> to remove a database.
-   </para>
-
-   <para>
-    The program <xref linkend="APP-CREATEDB"> is a
-    wrapper program around this command, provided for convenience.
-   </para>
-
-  <para>
-   Although it is possible to copy a database other than <literal>template1</>
-   by specifying its name as the template, this is not (yet) intended as
-   a general-purpose <quote><command>COPY DATABASE</command></quote> facility.
-   The principal limitation is that no other sessions can be connected to
-   the template database while it is being copied.  <command>CREATE
-   DATABASE</> will fail if any other connection exists when it starts;
-   otherwise, new connections to the template database are locked out
-   until <command>CREATE DATABASE</> completes.
-   See <xref linkend="manage-ag-templatedbs"> for more information.
-  </para>
-
-  <para>
-   The character set encoding specified for the new database must be
-   compatible with the chosen locale settings (<literal>LC_COLLATE</> and
-   <literal>LC_CTYPE</>).  If the locale is <literal>C</> (or equivalently
-   <literal>POSIX</>), then all encodings are allowed, but for other
-   locale settings there is only one encoding that will work properly.
-   (On Windows, however, UTF-8 encoding can be used with any locale.)
-   <command>CREATE DATABASE</> will allow superusers to specify
-   <literal>SQL_ASCII</> encoding regardless of the locale settings,
-   but this choice is deprecated and may result in misbehavior of
-   character-string functions if data that is not encoding-compatible
-   with the locale is stored in the database.
-  </para>
-
-  <para>
-   The encoding and locale settings must match those of the template database,
-   except when <literal>template0</> is used as template.  This is because
-   other databases might contain data that does not match the specified
-   encoding, or might contain indexes whose sort ordering is affected by
-   <literal>LC_COLLATE</> and <literal>LC_CTYPE</>.  Copying such data would
-   result in a database that is corrupt according to the new settings.
-   <literal>template0</literal>, however, is known to not contain any data or
-   indexes that would be affected.
-  </para>
-
-  <para>
-   The <literal>CONNECTION LIMIT</> option is only enforced approximately;
-   if two new sessions start at about the same time when just one
-   connection <quote>slot</> remains for the database, it is possible that
-   both will fail.  Also, the limit is not enforced against superusers.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To create a new database:
-
-<programlisting>
-CREATE DATABASE lusiadas;
-</programlisting>
-  </para>
-
-  <para>
-   To create a database <literal>sales</> owned by user <literal>salesapp</>
-   with a default tablespace of <literal>salesspace</>:
-
-<programlisting>
-CREATE DATABASE sales OWNER salesapp TABLESPACE salesspace;
-</programlisting>
-  </para>
-
-  <para>
-   To create a database <literal>music</> which supports the ISO-8859-1
-   character set:
-
-<programlisting>
-CREATE DATABASE music ENCODING 'LATIN1' TEMPLATE template0;
-</programlisting>
-
-   In this example, the <literal>TEMPLATE template0</> clause would only
-   be required if <literal>template1</>'s encoding is not ISO-8859-1.
-   Note that changing encoding might require selecting new
-   <literal>LC_COLLATE</> and <literal>LC_CTYPE</> settings as well.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>CREATE DATABASE</command> statement in the SQL
-   standard.  Databases are equivalent to catalogs, whose creation is
-   implementation-defined.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterdatabase"></member>
-   <member><xref linkend="sql-dropdatabase"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_domain.sgmlin b/doc-xc/src/sgml/ref/create_domain.sgmlin
deleted file mode 100644
index 17a8095d78..0000000000
--- a/doc-xc/src/sgml/ref/create_domain.sgmlin
+++ /dev/null
@@ -1,230 +0,0 @@
-<!--
-doc/src/sgml/ref/create_domain.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEDOMAIN">
- <refmeta>
-  <refentrytitle>CREATE DOMAIN</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE DOMAIN</refname>
-  <refpurpose>define a new domain</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createdomain">
-  <primary>CREATE DOMAIN</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE DOMAIN <replaceable class="parameter">name</replaceable> [ AS ] <replaceable class="parameter">data_type</replaceable>
-    [ COLLATE <replaceable>collation</replaceable> ]
-    [ DEFAULT <replaceable>expression</replaceable> ]
-    [ <replaceable class="PARAMETER">constraint</replaceable> [ ... ] ]
-
-<phrase>where <replaceable class="PARAMETER">constraint</replaceable> is:</phrase>
-
-[ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-{ NOT NULL | NULL | CHECK (<replaceable class="PARAMETER">expression</replaceable>) }
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE DOMAIN</command> creates a new domain.  A domain is
-   essentially a data type with optional constraints (restrictions on
-   the allowed set of values).
-   The user who defines a domain becomes its owner.
-  </para>
-
-  <para>
-   If a schema name is given (for example, <literal>CREATE DOMAIN
-   myschema.mydomain ...</>) then the domain is created in the
-   specified schema.  Otherwise it is created in the current schema.
-   The domain name must be unique among the types and domains existing
-   in its schema.
-  </para>
-
-  <para>
-   Domains are useful for abstracting common constraints on fields into
-   a single location for maintenance.  For example, several tables might
-   contain email address columns, all requiring the same CHECK constraint
-   to verify the address syntax.
-   Define a domain rather than setting up each table's constraint
-   individually.
-  </para>
-&xc-constraint;
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">name</replaceable></term>
-      <listitem>
-       <para>
-        The name (optionally schema-qualified) of a domain to be created.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">data_type</replaceable></term>
-      <listitem>
-       <para>
-        The underlying data type of the domain. This can include array
-        specifiers.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable>collation</replaceable></term>
-      <listitem>
-       <para>
-        An optional collation for the domain.  If no collation is
-        specified, the underlying data type's default collation is used.
-        The underlying type must be collatable if <literal>COLLATE</>
-        is specified.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>DEFAULT <replaceable>expression</replaceable></literal></term>
-
-      <listitem>
-       <para>
-        The <literal>DEFAULT</> clause specifies a default value for
-        columns of the domain data type.  The value is any
-        variable-free expression (but subqueries are not allowed).
-        The data type of the default expression must match the data
-        type of the domain.  If no default value is specified, then
-        the default value is the null value.
-       </para>
-
-       <para>
-        The default expression will be used in any insert operation
-        that does not specify a value for the column.  If a default
-        value is defined for a particular column, it overrides any
-        default associated with the domain.  In turn, the domain
-        default overrides any default value associated with the
-        underlying data type.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable></literal></term>
-      <listitem>
-       <para>
-        An optional name for a constraint.  If not specified,
-        the system generates a name.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>NOT NULL</></term>
-      <listitem>
-       <para>
-        Values of this domain are normally prevented from being null.
-        However, it is still possible for a domain with this constraint
-        to take a null value if it is assigned a matching domain type
-        that has become null, e.g. via a LEFT OUTER JOIN, or
-        <command>INSERT INTO tab (domcol) VALUES ((SELECT domcol FROM
-        tab WHERE false))</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>NULL</></term>
-      <listitem>
-       <para>
-        Values of this domain are allowed to be null.  This is the default.
-       </para>
-
-       <para>
-        This clause is only intended for compatibility with
-        nonstandard SQL databases.  Its use is discouraged in new
-        applications.
-       </para>
-      </listitem>
-     </varlistentry>
-
-   <varlistentry>
-    <term><literal>CHECK (<replaceable class="PARAMETER">expression</replaceable>)</literal></term>
-    <listitem>
-     <para>
-      <literal>CHECK</> clauses specify integrity constraints or tests
-      which values of the domain must satisfy.
-      Each constraint must be an expression
-      producing a Boolean result.  It should use the key word <literal>VALUE</>
-      to refer to the value being tested.
-     </para>
-
-     <para>
-      Currently, <literal>CHECK</literal> expressions cannot contain
-      subqueries nor refer to variables other than <literal>VALUE</>.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   This example creates the <type>us_postal_code</type> data type and
-   then uses the type in a table definition.  A regular expression test
-   is used to verify that the value looks like a valid US postal code:
-
-<programlisting>
-CREATE DOMAIN us_postal_code AS TEXT
-CHECK(
-   VALUE ~ '^\\d{5}$'
-OR VALUE ~ '^\\d{5}-\\d{4}$'
-);
-
-CREATE TABLE us_snail_addy (
-  address_id SERIAL PRIMARY KEY,
-  street1 TEXT NOT NULL,
-  street2 TEXT,
-  street3 TEXT,
-  city TEXT NOT NULL,
-  postal us_postal_code NOT NULL
-);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATEDOMAIN-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   The command <command>CREATE DOMAIN</command> conforms to the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATEDOMAIN-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterdomain"></member>
-   <member><xref linkend="sql-dropdomain"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_extension.sgmlin b/doc-xc/src/sgml/ref/create_extension.sgmlin
deleted file mode 100644
index 7670d76f89..0000000000
--- a/doc-xc/src/sgml/ref/create_extension.sgmlin
+++ /dev/null
@@ -1,205 +0,0 @@
-<!--
-doc/src/sgml/ref/create_extension.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEEXTENSION">
- <refmeta>
-  <refentrytitle>CREATE EXTENSION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE EXTENSION</refname>
-  <refpurpose>install an extension</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createextension">
-  <primary>CREATE EXTENSION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE EXTENSION [ IF NOT EXISTS ] <replaceable class="parameter">extension_name</replaceable>
-    [ WITH ] [ SCHEMA <replaceable class="parameter">schema</replaceable> ]
-             [ VERSION <replaceable class="parameter">version</replaceable> ]
-             [ FROM <replaceable class="parameter">old_version</replaceable> ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>CREATE EXTENSION</command> loads a new extension into the current
-   database.  There must not be an extension of the same name already loaded.
-  </para>
-
-  <para>
-   Loading an extension essentially amounts to running the extension's script
-   file.  The script will typically create new <acronym>SQL</> objects such as
-   functions, data types, operators and index support methods.
-   <command>CREATE EXTENSION</command> additionally records the identities
-   of all the created objects, so that they can be dropped again if
-   <command>DROP EXTENSION</command> is issued.
-  </para>
-
-  <para>
-   Loading an extension requires the same privileges that would be
-   required to create its component objects.  For most extensions this
-   means superuser or database owner privileges are needed.
-   The user who runs <command>CREATE EXTENSION</command> becomes the
-   owner of the extension for purposes of later privilege checks, as well
-   as the owner of any objects created by the extension's script.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><literal>IF NOT EXISTS</></term>
-      <listitem>
-       <para>
-        Do not throw an error if an extension with the same name already
-        exists.  A notice is issued in this case.  Note that there is no
-        guarantee that the existing extension is anything like the one that
-        would have been created from the currently-available script file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">extension_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the extension to be
-        installed. <productname>PostgreSQL</productname> will create the
-        extension using details from the file
-        <literal>SHAREDIR/extension/</literal><replaceable class="parameter">extension_name</replaceable><literal>.control</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">schema</replaceable></term>
-      <listitem>
-       <para>
-        The name of the schema in which to install the extension's
-        objects, given that the extension allows its contents to be
-        relocated.  The named schema must already exist.
-        If not specified, and the extension's control file does not specify a
-        schema either, the current default object creation schema is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">version</replaceable></term>
-      <listitem>
-       <para>
-        The version of the extension to install.  This can be written as
-        either an identifier or a string literal.  The default version is
-        whatever is specified in the extension's control file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">old_version</replaceable></term>
-      <listitem>
-       <para>
-        <literal>FROM</> <replaceable class="parameter">old_version</>
-        must be specified when, and only when, you are attempting to install
-        an extension that replaces an <quote>old style</> module that is just
-        a collection of objects not packaged into an extension.  This option
-        causes <command>CREATE EXTENSION</> to run an alternative installation
-        script that absorbs the existing objects into the extension, instead
-        of creating new objects.  Be careful that <literal>SCHEMA</> specifies
-        the schema containing these pre-existing objects.
-       </para>
-
-       <para>
-        The value to use for <replaceable
-        class="parameter">old_version</replaceable> is determined by the
-        extension's author, and might vary if there is more than one version
-        of the old-style module that can be upgraded into an extension.
-        For the standard additional modules supplied with pre-9.1
-        <productname>PostgreSQL</productname>, use <literal>unpackaged</>
-        for <replaceable class="parameter">old_version</replaceable> when
-        updating a module to extension style.
-       </para>
-      </listitem>
-     </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Before you can use <command>CREATE EXTENSION</> to load an extension
-   into a database, the extension's supporting files must be installed.
-   Information about installing the extensions supplied with
-   <productname>PostgreSQL</productname> can be found in
-   <link linkend="contrib">Additional Supplied Modules</link>.
-  </para>
-
-  <para>
-   The extensions currently available for loading can be identified from the
-   <link linkend="view-pg-available-extensions"><structname>pg_available_extensions</structname></link>
-   or
-   <link linkend="view-pg-available-extension-versions"><structname>pg_available_extension_versions</structname></link>
-   system views.
-  </para>
-
-  <para>
-   For information about writing new extensions, see
-   <xref linkend="extend-extensions">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Install the <link linkend="hstore">hstore</link> extension into the
-   current database:
-<programlisting>
-CREATE EXTENSION hstore;
-</programlisting>
-  </para>
-
-  <para>
-   Update a pre-9.1 installation of <literal>hstore</> into
-   extension style:
-<programlisting>
-CREATE EXTENSION hstore SCHEMA public FROM unpackaged;
-</programlisting>
-   Be careful to specify the schema in which you installed the existing
-   <literal>hstore</> objects.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE EXTENSION</command> is a <productname>PostgreSQL</>
-   extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterextension"></member>
-   <member><xref linkend="sql-dropextension"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_foreign_data_wrapper.sgmlin b/doc-xc/src/sgml/ref/create_foreign_data_wrapper.sgmlin
deleted file mode 100644
index 42c26bd840..0000000000
--- a/doc-xc/src/sgml/ref/create_foreign_data_wrapper.sgmlin
+++ /dev/null
@@ -1,211 +0,0 @@
-<!--
-doc/src/sgml/ref/create_foreign_data_wrapper.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEFOREIGNDATAWRAPPER">
- <refmeta>
-  <refentrytitle>CREATE FOREIGN DATA WRAPPER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE FOREIGN DATA WRAPPER</refname>
-  <refpurpose>define a new foreign-data wrapper</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createforeigndatawrapper">
-  <primary>CREATE FOREIGN DATA WRAPPER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE FOREIGN DATA WRAPPER <replaceable class="parameter">name</replaceable>
-    [ HANDLER <replaceable class="parameter">handler_function</replaceable> | NO HANDLER ]
-    [ VALIDATOR <replaceable class="parameter">validator_function</replaceable> | NO VALIDATOR ]
-    [ OPTIONS ( <replaceable class="PARAMETER">option</replaceable> '<replaceable class="PARAMETER">value</replaceable>' [, ... ] ) ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-<!## XC>
-&xconly;
-  <para>
-   <command>FOREIGN DATA WRAPPER</> has not been supported
-   by <productname>Postgres-XC</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>FOREIGN DATA WRAPPER</> has not been supported
-   by <productname>Postgres-XL</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-&pgonly;
-
-  <para>
-   <command>CREATE FOREIGN DATA WRAPPER</command> creates a new
-   foreign-data wrapper.  The user who defines a foreign-data wrapper
-   becomes its owner.
-  </para>
-
-  <para>
-   The foreign-data wrapper name must be unique within the database.
-  </para>
-
-  <para>
-   Only superusers can create foreign-data wrappers.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the foreign-data wrapper to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>HANDLER <replaceable class="parameter">handler_function</replaceable></literal></term>
-    <listitem>
-     <para>
-      <replaceable class="parameter">handler_function</replaceable> is the
-      name of a previously registered function that will be called to
-      retrieve the execution functions for foreign tables.
-      The handler function must take no arguments, and
-      its return type must be <type>fdw_handler</type>.
-     </para>
-
-     <para>
-      It is possible to create a foreign-data wrapper with no handler
-      function, but foreign tables using such a wrapper can only be declared,
-      not accessed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>VALIDATOR <replaceable class="parameter">validator_function</replaceable></literal></term>
-    <listitem>
-     <para>
-      <replaceable class="parameter">validator_function</replaceable> is the
-      name of a previously registered function that will be called to
-      check the generic options given to the foreign-data wrapper, as
-      well as options for foreign servers and user mappings using the
-      foreign-data wrapper.  If no validator function or <literal>NO
-      VALIDATOR</literal> is specified, then options will not be
-      checked at creation time.  (Foreign-data wrappers will possibly
-      ignore or reject invalid option specifications at run time,
-      depending on the implementation.)  The validator function must
-      take two arguments: one of type <type>text[]</type>, which will
-      contain the array of options as stored in the system catalogs,
-      and one of type <type>oid</type>, which will be the OID of the
-      system catalog containing the options. The return type is ignored;
-      the function should report invalid options using the
-      <function>ereport(ERROR)</function> function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OPTIONS ( <replaceable class="PARAMETER">option</replaceable> '<replaceable class="PARAMETER">value</replaceable>' [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      This clause specifies options for the new foreign-data wrapper.
-      The allowed option names and values are specific to each foreign
-      data wrapper and are validated using the foreign-data wrapper's
-      validator function.  Option names must be unique.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   At the moment, the foreign-data wrapper functionality is rudimentary.
-   There is no support for updating a foreign table, and optimization of
-   queries is primitive (and mostly left to the wrapper, too).
-  </para>
-
-  <para>
-   There is one built-in foreign-data wrapper validator function
-   provided:
-   <filename>postgresql_fdw_validator</filename>, which accepts
-   options corresponding to <application>libpq</> connection
-   parameters.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a useless foreign-data wrapper <literal>dummy</>:
-<programlisting>
-CREATE FOREIGN DATA WRAPPER dummy;
-</programlisting>
-  </para>
-
-  <para>
-   Create a foreign-data wrapper <literal>file</> with
-   handler function <literal>file_fdw_handler</>:
-<programlisting>
-CREATE FOREIGN DATA WRAPPER file HANDLER file_fdw_handler;
-</programlisting>
-  </para>
-
-  <para>
-   Create a foreign-data wrapper <literal>mywrapper</> with some
-   options:
-<programlisting>
-CREATE FOREIGN DATA WRAPPER mywrapper
-    OPTIONS (debug 'true');
-</programlisting>
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE FOREIGN DATA WRAPPER</command> conforms to ISO/IEC
-   9075-9 (SQL/MED), with the exception that the <literal>HANDLER</literal>
-   and <literal>VALIDATOR</literal> clauses are extensions and the standard
-   clauses <literal>LIBRARY</literal> and <literal>LANGUAGE</literal>
-   are not implemented in PostgreSQL.
-  </para>
-
-  <para>
-   Note, however, that the SQL/MED functionality as a whole is not yet
-   conforming.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterforeigndatawrapper"></member>
-   <member><xref linkend="sql-dropforeigndatawrapper"></member>
-   <member><xref linkend="sql-createserver"></member>
-   <member><xref linkend="sql-createusermapping"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_foreign_table.sgmlin b/doc-xc/src/sgml/ref/create_foreign_table.sgmlin
deleted file mode 100644
index ad91072bd1..0000000000
--- a/doc-xc/src/sgml/ref/create_foreign_table.sgmlin
+++ /dev/null
@@ -1,197 +0,0 @@
-<!-- doc/src/sgml/ref/create_foreign_table.sgml -->
-
-<refentry id="SQL-CREATEFOREIGNTABLE">
- <refmeta>
-  <refentrytitle>CREATE FOREIGN TABLE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE FOREIGN TABLE</refname>
-  <refpurpose>define a new foreign table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createforeigntable">
-  <primary>CREATE FOREIGN TABLE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE FOREIGN TABLE [ IF NOT EXISTS ] <replaceable class="PARAMETER">table_name</replaceable> ( [
-  { <replaceable class="PARAMETER">column_name</replaceable> <replaceable class="PARAMETER">data_type</replaceable> [ NULL | NOT NULL ] }
-    [, ... ]
-] )
-  SERVER <replaceable class="parameter">server_name</replaceable>
-[ OPTIONS ( <replaceable class="PARAMETER">option</replaceable> '<replaceable class="PARAMETER">value</replaceable>' [, ... ] ) ]
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="SQL-CREATEFOREIGNTABLE-description">
-  <title>Description</title>
-
-  <para>
-   <command>CREATE FOREIGN TABLE</command> will create a new foreign table
-   in the current database. The table will be owned by the user issuing the
-   command.
-  </para>
-
-  <para>
-   If a schema name is given (for example, <literal>CREATE FOREIGN TABLE
-   myschema.mytable ...</>) then the table is created in the specified
-   schema.  Otherwise it is created in the current schema.
-   The name of the foreign table must be
-   distinct from the name of any other foreign table, table, sequence, index,
-   or view in the same schema.
-  </para>
-
-  <para>
-   <command>CREATE FOREIGN TABLE</command> also automatically creates a data
-   type that represents the composite type corresponding to one row of
-   the foreign table.  Therefore, foreign tables cannot have the same
-   name as any existing data type in the same schema.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF NOT EXISTS</></term>
-    <listitem>
-     <para>
-      Do not throw an error if a relation with the same name already exists.
-      A notice is issued in this case.  Note that there is no guarantee that
-      the existing relation is anything like the one that would have been
-      created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">table_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the table to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">column_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of a column to be created in the new table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">data_type</replaceable></term>
-    <listitem>
-     <para>
-      The data type of the column. This can include array
-      specifiers. For more information on the data types supported by
-      <productname>PostgreSQL</productname>, refer to <xref
-      linkend="datatype">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NOT NULL</></term>
-    <listitem>
-     <para>
-      The column is not allowed to contain null values.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NULL</></term>
-    <listitem>
-     <para>
-      The column is allowed to contain null values. This is the default.
-     </para>
-
-     <para>
-      This clause is only provided for compatibility with
-      non-standard SQL databases.  Its use is discouraged in new
-      applications.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">server_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing server for the foreign table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OPTIONS ( <replaceable class="PARAMETER">option</replaceable> '<replaceable class="PARAMETER">value</replaceable>' [, ...] )</literal></term>
-    <listitem>
-     <para>
-      Options to be associated with the new foreign table.
-      The allowed option names and values are specific to each foreign
-      data wrapper and are validated using the foreign-data wrapper's
-      validator function. Option names must be unique.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
- </refsect1>
-
-
- <refsect1 id="SQL-CREATEFOREIGNTABLE-examples">
-  <title>Examples</title>
-
-  <para>
-   Create foreign table <structname>films</> with <structname>film_server</>:
-
-<programlisting>
-CREATE FOREIGN TABLE films (
-    code        char(5) NOT NULL,
-    title       varchar(40) NOT NULL,
-    did         integer NOT NULL,
-    date_prod   date,
-    kind        varchar(10),
-    len         interval hour to minute
-)
-SERVER film_server;
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1 id="SQL-CREATEFOREIGNTABLE-compatibility">
-  <title id="SQL-CREATEFOREIGNTABLE-compatibility-title">Compatibility</title>
-
-  <para>
-   The <command>CREATE FOREIGN TABLE</command> command largely conforms to the
-   <acronym>SQL</acronym> standard; however, much as with
-   <link linkend="sql-createtable"><command>CREATE TABLE</></link>,
-   <literal>NULL</> constraints and zero-column foreign tables are permitted.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterforeigntable"></member>
-   <member><xref linkend="sql-dropforeigntable"></member>
-   <member><xref linkend="sql-createtable"></member>
-   <member><xref linkend="sql-createserver"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_function.sgmlin b/doc-xc/src/sgml/ref/create_function.sgmlin
deleted file mode 100644
index 0c60183020..0000000000
--- a/doc-xc/src/sgml/ref/create_function.sgmlin
+++ /dev/null
@@ -1,837 +0,0 @@
-<!--
-doc/src/sgml/ref/create_function.sgml
--->
-
-<refentry id="SQL-CREATEFUNCTION">
- <refmeta>
-  <refentrytitle>CREATE FUNCTION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE FUNCTION</refname>
-  <refpurpose>define a new function</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createfunction">
-  <primary>CREATE FUNCTION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE [ OR REPLACE ] FUNCTION
-    <replaceable class="parameter">name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">argname</replaceable> ] <replaceable class="parameter">argtype</replaceable> [ { DEFAULT | = } <replaceable class="parameter">default_expr</replaceable> ] [, ...] ] )
-    [ RETURNS <replaceable class="parameter">rettype</replaceable>
-      | RETURNS TABLE ( <replaceable class="parameter">column_name</replaceable> <replaceable class="parameter">column_type</replaceable> [, ...] ) ]
-  { LANGUAGE <replaceable class="parameter">lang_name</replaceable>
-    | WINDOW
-    | IMMUTABLE | STABLE | VOLATILE
-    | CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT
-    | [ EXTERNAL ] SECURITY INVOKER | [ EXTERNAL ] SECURITY DEFINER
-    | COST <replaceable class="parameter">execution_cost</replaceable>
-    | ROWS <replaceable class="parameter">result_rows</replaceable>
-    | SET <replaceable class="parameter">configuration_parameter</replaceable> { TO <replaceable class="parameter">value</replaceable> | = <replaceable class="parameter">value</replaceable> | FROM CURRENT }
-    | AS '<replaceable class="parameter">definition</replaceable>'
-    | AS '<replaceable class="parameter">obj_file</replaceable>', '<replaceable class="parameter">link_symbol</replaceable>'
-  } ...
-    [ WITH ( <replaceable class="parameter">attribute</replaceable> [, ...] ) ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-createfunction-description">
-  <title>Description</title>
-
-<!## XC>
-  <note>
-   <para>
-    <productname>Postgres-XC</> currently does not support creation of SQL functions 
-    containing utility statements. This limitation is however enforced only when the 
-    GUC <varname>check_function_bodies</varname> is <literal>on</>. 
-    If SQL functions are created after setting <varname>check_function_bodies</varname> to <literal>off</>, 
-    the behaviour of the function when executed is un-defined. 
-    Other than this limitation the following description applies both to 
-    <productname>Postgres-XC</> and <productname>PostgreSQL</> if not described explicitly.
-   </para>
-  </note>
-<!## end>
-<!## XL>
-  <note>
-   <para>
-    <productname>Postgres-XL</> function usage currently requires a lot of care,
-    otherwise unexepected results may occur, and you may bring your data in an inconsistent state. 
-    This behavior may change in a future version to make it safer.
-   </para>
-
-   <para>
-    A call such as <literal>SELECT my_function(1,2);</>, without any FROM clause,
-     will execute on a local coordinator, and 
-    may involve other datanodes and behave as expected, being driven from a coordinator.
-   </para>
-
-   <para>
-    A call such as <literal>SELECT col1, my_table_function(col2) FROM mytable</> will be
-    pushed down to the datanodes involved. If <literal>my_table_function</> happens to 
-    do a SELECT, it will only be from data local to that node. Similarly, if it
-    executes an UPDATE, it will only update data local to that node. 
-    If the UPDATE writes to a replicated table for example, it would mean that 
-    the tables would be out of sync.
-   </para>
-
-   <para>
-    In summary, one should be very careful in creating and using functions in Postgres-XL.
-   </para>
-  </note>
-<!## end>
-
-
-  <para>
-   <command>CREATE FUNCTION</command> defines a new function.
-   <command>CREATE OR REPLACE FUNCTION</command> will either create a
-   new function, or replace an existing definition.
-   To be able to define a function, the user must have the
-   <literal>USAGE</literal> privilege on the language.
-  </para>
-
-  <para>
-   If a schema name is included, then the function is created in the
-   specified schema.  Otherwise it is created in the current schema.
-   The name of the new function must not match any existing function
-   with the same input argument types in the same schema.  However,
-   functions of different argument types can share a name (this is
-   called <firstterm>overloading</>).
-  </para>
-
-  <para>
-   To replace the current definition of an existing function, use
-   <command>CREATE OR REPLACE FUNCTION</command>.  It is not possible
-   to change the name or argument types of a function this way (if you
-   tried, you would actually be creating a new, distinct function).
-   Also, <command>CREATE OR REPLACE FUNCTION</command> will not let
-   you change the return type of an existing function.  To do that,
-   you must drop and recreate the function.  (When using <literal>OUT</>
-   parameters, that means you cannot change the types of any
-   <literal>OUT</> parameters except by dropping the function.)
-  </para>
-
-  <para>
-   When <command>CREATE OR REPLACE FUNCTION</> is used to replace an
-   existing function, the ownership and permissions of the function
-   do not change.  All other function properties are assigned the
-   values specified or implied in the command.  You must own the function
-   to replace it (this includes being a member of the owning role).
-  </para>
-
-  <para>
-   If you drop and then recreate a function, the new function is not
-   the same entity as the old; you will have to drop existing rules, views,
-   triggers, etc. that refer to the old function.  Use
-   <command>CREATE OR REPLACE FUNCTION</command> to change a function
-   definition without breaking objects that refer to the function.
-   Also, <command>ALTER FUNCTION</> can be used to change most of the
-   auxiliary properties of an existing function.
-  </para>
-
-  <para>
-   The user that creates the function becomes the owner of the function.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-   <variablelist>
-
-    <varlistentry>
-     <term><replaceable class="parameter">name</replaceable></term>
-
-     <listitem>
-      <para>
-       The name (optionally schema-qualified) of the function to create.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">argmode</replaceable></term>
-
-     <listitem>
-      <para>
-       The mode of an argument: <literal>IN</>, <literal>OUT</>,
-       <literal>INOUT</>, or <literal>VARIADIC</>.
-       If omitted, the default is <literal>IN</>.
-       Only <literal>OUT</> arguments can follow a <literal>VARIADIC</> one.
-       Also, <literal>OUT</> and <literal>INOUT</> arguments cannot be used
-       together with the <literal>RETURNS TABLE</> notation.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">argname</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of an argument. Some languages (currently only PL/pgSQL) let
-       you use the name in the function body.  For other languages the
-       name of an input argument is just extra documentation, so far as
-       the function itself is concerned; but you can use input argument names
-       when calling a function to improve readability (see <xref
-       linkend="sql-syntax-calling-funcs">).  In any case, the name
-       of an output argument is significant, because it defines the column
-       name in the result row type.  (If you omit the name for an output
-       argument, the system will choose a default column name.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">argtype</replaceable></term>
-
-     <listitem>
-      <para>
-       The data type(s) of the function's arguments (optionally
-       schema-qualified), if any. The argument types can be base, composite,
-       or domain types, or can reference the type of a table column.
-      </para>
-      <para>
-       Depending on the implementation language it might also be allowed
-       to specify <quote>pseudotypes</> such as <type>cstring</>.
-       Pseudotypes indicate that the actual argument type is either
-       incompletely specified, or outside the set of ordinary SQL data types.
-      </para>
-      <para>
-       The type of a column is referenced by writing
-       <literal><replaceable
-       class="parameter">table_name</replaceable>.<replaceable
-       class="parameter">column_name</replaceable>%TYPE</literal>.
-       Using this feature can sometimes help make a function independent of
-       changes to the definition of a table.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">default_expr</replaceable></term>
-
-     <listitem>
-      <para>
-       An expression to be used as default value if the parameter is
-       not specified.  The expression has to be coercible to the
-       argument type of the parameter.
-       Only input (including <literal>INOUT</>) parameters can have a default
-        value.  All input parameters following a
-       parameter with a default value must have default values as well.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">rettype</replaceable></term>
-
-     <listitem>
-      <para>
-       The return data type (optionally schema-qualified). The return type
-       can be a base, composite, or domain type,
-       or can reference the type of a table column.
-       Depending on the implementation language it might also be allowed
-       to specify <quote>pseudotypes</> such as <type>cstring</>.
-       If the function is not supposed to return a value, specify
-       <type>void</> as the return type.
-      </para>
-      <para>
-       When there are <literal>OUT</> or <literal>INOUT</> parameters,
-       the <literal>RETURNS</> clause can be omitted.  If present, it
-       must agree with the result type implied by the output parameters:
-       <literal>RECORD</> if there are multiple output parameters, or
-       the same type as the single output parameter.
-      </para>
-      <para>
-       The <literal>SETOF</literal>
-       modifier indicates that the function will return a set of
-       items, rather than a single item.
-      </para>
-      <para>
-       The type of a column is referenced by writing
-       <literal><replaceable
-       class="parameter">table_name</replaceable>.<replaceable
-       class="parameter">column_name</replaceable>%TYPE</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">column_name</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of an output column in the <literal>RETURNS TABLE</>
-       syntax.  This is effectively another way of declaring a named
-       <literal>OUT</> parameter, except that <literal>RETURNS TABLE</>
-       also implies <literal>RETURNS SETOF</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">column_type</replaceable></term>
-
-     <listitem>
-      <para>
-       The data type of an output column in the <literal>RETURNS TABLE</>
-       syntax.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">lang_name</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the language that the function is implemented in.
-       Can be <literal>SQL</literal>, <literal>C</literal>,
-       <literal>internal</literal>, or the name of a user-defined
-       procedural language.  For backward compatibility,
-       the name can be enclosed by single quotes.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>WINDOW</literal></term>
-
-     <listitem>
-      <para>
-       <literal>WINDOW</literal> indicates that the function is a
-       <firstterm>window function</> rather than a plain function.
-       This is currently only useful for functions written in C.
-       The <literal>WINDOW</> attribute cannot be changed when
-       replacing an existing function definition.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>IMMUTABLE</literal></term>
-     <term><literal>STABLE</literal></term>
-     <term><literal>VOLATILE</literal></term>
-
-     <listitem>
-      <para>
-       These attributes inform the query optimizer about the behavior
-       of the function.  At most one choice
-       can be specified.  If none of these appear,
-       <literal>VOLATILE</literal> is the default assumption.
-      </para>
-
-      <para>
-       <literal>IMMUTABLE</literal> indicates that the function
-       cannot modify the database and always
-       returns the same result when given the same argument values; that
-       is, it does not do database lookups or otherwise use information not
-       directly present in its argument list.  If this option is given,
-       any call of the function with all-constant arguments can be
-       immediately replaced with the function value.
-      </para>
-
-      <para>
-       <literal>STABLE</literal> indicates that the function
-       cannot modify the database,
-       and that within a single table scan it will consistently
-       return the same result for the same argument values, but that its
-       result could change across SQL statements.  This is the appropriate
-       selection for functions whose results depend on database lookups,
-       parameter variables (such as the current time zone), etc.  (It is
-       inappropriate for <literal>AFTER</> triggers that wish to
-       query rows modified by the current command.)  Also note
-       that the <function>current_timestamp</> family of functions qualify
-       as stable, since their values do not change within a transaction.
-      </para>
-
-      <para>
-       <literal>VOLATILE</literal> indicates that the function value can
-       change even within a single table scan, so no optimizations can be
-       made.  Relatively few database functions are volatile in this sense;
-       some examples are <literal>random()</>, <literal>currval()</>,
-       <literal>timeofday()</>.  But note that any function that has
-       side-effects must be classified volatile, even if its result is quite
-       predictable, to prevent calls from being optimized away; an example is
-       <literal>setval()</>.
-      </para>
-
-      <para>
-       For additional details see <xref linkend="xfunc-volatility">.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>CALLED ON NULL INPUT</literal></term>
-     <term><literal>RETURNS NULL ON NULL INPUT</literal></term>
-     <term><literal>STRICT</literal></term>
-
-     <listitem>
-      <para>
-       <literal>CALLED ON NULL INPUT</literal> (the default) indicates
-       that the function will be called normally when some of its
-       arguments are null.  It is then the function author's
-       responsibility to check for null values if necessary and respond
-       appropriately.
-      </para>
-
-      <para>
-       <literal>RETURNS NULL ON NULL INPUT</literal> or
-       <literal>STRICT</literal> indicates that the function always
-       returns null whenever any of its arguments are null.  If this
-       parameter is specified, the function is not executed when there
-       are null arguments; instead a null result is assumed
-       automatically.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   <varlistentry>
-    <term><literal><optional>EXTERNAL</optional> SECURITY INVOKER</literal></term>
-    <term><literal><optional>EXTERNAL</optional> SECURITY DEFINER</literal></term>
-
-    <listitem>
-     <para>
-      <literal>SECURITY INVOKER</literal> indicates that the function
-      is to be executed with the privileges of the user that calls it.
-      That is the default.  <literal>SECURITY DEFINER</literal>
-      specifies that the function is to be executed with the
-      privileges of the user that created it.
-     </para>
-
-     <para>
-      The key word <literal>EXTERNAL</literal> is allowed for SQL
-      conformance, but it is optional since, unlike in SQL, this feature
-      applies to all functions not only external ones.
-     </para>
-    </listitem>
-   </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">execution_cost</replaceable></term>
-
-     <listitem>
-      <para>
-       A positive number giving the estimated execution cost for the function,
-       in units of <xref linkend="guc-cpu-operator-cost">.  If the function
-       returns a set, this is the cost per returned row.  If the cost is
-       not specified, 1 unit is assumed for C-language and internal functions,
-       and 100 units for functions in all other languages.  Larger values
-       cause the planner to try to avoid evaluating the function more often
-       than necessary.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">result_rows</replaceable></term>
-
-     <listitem>
-      <para>
-       A positive number giving the estimated number of rows that the planner
-       should expect the function to return.  This is only allowed when the
-       function is declared to return a set.  The default assumption is
-       1000 rows.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>configuration_parameter</replaceable></term>
-     <term><replaceable>value</replaceable></term>
-     <listitem>
-      <para>
-       The <literal>SET</> clause causes the specified configuration
-       parameter to be set to the specified value when the function is
-       entered, and then restored to its prior value when the function exits.
-       <literal>SET FROM CURRENT</> saves the session's current value of
-       the parameter as the value to be applied when the function is entered.
-      </para>
-
-      <para>
-       If a <literal>SET</> clause is attached to a function, then
-       the effects of a <command>SET LOCAL</> command executed inside the
-       function for the same variable are restricted to the function: the
-       configuration parameter's prior value is still restored at function exit.
-       However, an ordinary
-       <command>SET</> command (without <literal>LOCAL</>) overrides the
-       <literal>SET</> clause, much as it would do for a previous <command>SET
-       LOCAL</> command: the effects of such a command will persist after
-       function exit, unless the current transaction is rolled back.
-      </para>
-
-      <para>
-       See <xref linkend="sql-set"> and
-       <xref linkend="runtime-config">
-       for more information about allowed parameter names and values.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">definition</replaceable></term>
-
-     <listitem>
-      <para>
-       A string constant defining the function; the meaning depends on the
-       language.  It can be an internal function name, the path to an
-       object file, an SQL command, or text in a procedural language.
-      </para>
-
-      <para>
-       It is often helpful to use dollar quoting (see <xref
-       linkend="sql-syntax-dollar-quoting">) to write the function definition
-       string, rather than the normal single quote syntax.  Without dollar
-       quoting, any single quotes or backslashes in the function definition must
-       be escaped by doubling them.
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal><replaceable class="parameter">obj_file</replaceable>, <replaceable class="parameter">link_symbol</replaceable></literal></term>
-
-     <listitem>
-      <para>
-       This form of the <literal>AS</literal> clause is used for
-       dynamically loadable C language functions when the function name
-       in the C language source code is not the same as the name of
-       the SQL function. The string <replaceable
-       class="parameter">obj_file</replaceable> is the name of the
-       file containing the dynamically loadable object, and
-       <replaceable class="parameter">link_symbol</replaceable> is the
-       function's link symbol, that is, the name of the function in the C
-       language source code.  If the link symbol is omitted, it is assumed
-       to be the same as the name of the SQL function being defined.
-      </para>
-
-      <para>
-       When repeated <command>CREATE FUNCTION</command> calls refer to
-       the same object file, the file is only loaded once per session.
-       To unload and
-       reload the file (perhaps during development), start a new session.
-      </para>
-<!## XC>
-&xconly;
-      <para>
-       It is user's responsibility to deploy the file to all the
-       servers where Coordinator or Datanode may run.
-      </para>
-<!## end>
-<!## XL>
-&xlonly;
-      <para>
-       It is user's responsibility to deploy the file to all the
-       servers where Coordinator or Datanode may run.
-      </para>
-<!## end>
-
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">attribute</replaceable></term>
-
-     <listitem>
-      <para>
-       The historical way to specify optional pieces of information
-       about the function.  The following attributes can appear here:
-
-      <variablelist>
-       <varlistentry>
-        <term><literal>isStrict</></term>
-        <listitem>
-         <para>
-          Equivalent to <literal>STRICT</literal> or <literal>RETURNS NULL ON NULL INPUT</literal>.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>isCachable</></term>
-        <listitem>
-         <para>
-          <literal>isCachable</literal> is an obsolete equivalent of
-          <literal>IMMUTABLE</literal>; it's still accepted for
-          backwards-compatibility reasons.
-         </para>
-        </listitem>
-       </varlistentry>
-
-      </variablelist>
-
-      Attribute names are not case-sensitive.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   </variablelist>
-
-   <para>
-    Refer to <xref linkend="xfunc"> for further information on writing
-    functions.
-   </para>
-
- </refsect1>
-
- <refsect1 id="sql-createfunction-overloading">
-  <title>Overloading</title>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> allows function
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> allows function
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> allows function
-<!## end>
-    <firstterm>overloading</firstterm>; that is, the same name can be
-    used for several different functions so long as they have distinct
-    input argument types.  However, the C names of all functions must be
-    different, so you must give overloaded C functions different C
-    names (for example, use the argument types as part of the C
-    names).
-   </para>
-
-   <para>
-    Two functions are considered the same if they have the same names and
-    <emphasis>input</> argument types, ignoring any <literal>OUT</>
-    parameters.  Thus for example these declarations conflict:
-<programlisting>
-CREATE FUNCTION foo(int) ...
-CREATE FUNCTION foo(int, out text) ...
-</programlisting>
-   </para>
-
-   <para>
-    Functions that have different argument type lists will not be considered
-    to conflict at creation time, but if defaults are provided they might
-    conflict in use.  For example, consider
-<programlisting>
-CREATE FUNCTION foo(int) ...
-CREATE FUNCTION foo(int, int default 42) ...
-</programlisting>
-    A call <literal>foo(10)</> will fail due to the ambiguity about which
-    function should be called.
-   </para>
-
- </refsect1>
-
- <refsect1 id="sql-createfunction-notes">
-  <title>Notes</title>
-
-   <para>
-    The full <acronym>SQL</acronym> type syntax is allowed for
-    input arguments and return value. However, some details of the
-    type specification (e.g., the precision field for
-    type <type>numeric</type>) are the responsibility of the
-    underlying function implementation and are silently swallowed
-    (i.e., not recognized or
-    enforced) by the <command>CREATE FUNCTION</command> command.
-   </para>
-
-   <para>
-    When replacing an existing function with <command>CREATE OR REPLACE
-    FUNCTION</>, there are restrictions on changing parameter names.
-    You cannot change the name already assigned to any input parameter
-    (although you can add names to parameters that had none before).
-    If there is more than one output parameter, you cannot change the
-    names of the output parameters, because that would change the
-    column names of the anonymous composite type that describes the
-    function's result.  These restrictions are made to ensure that
-    existing calls of the function do not stop working when it is replaced.
-   </para>
-
-   <para>
-    If a function is declared <literal>STRICT</> with a <literal>VARIADIC</>
-    argument, the strictness check tests that the variadic array <emphasis>as
-    a whole</> is non-null.  The function will still be called if the
-    array has null elements.
-   </para>
-
- </refsect1>
-
- <refsect1 id="sql-createfunction-examples">
-  <title>Examples</title>
-
-  <para>
-   Here are some trivial examples to help you get started.  For more
-   information and examples, see <xref linkend="xfunc">.
-<programlisting>
-CREATE FUNCTION add(integer, integer) RETURNS integer
-    AS 'select $1 + $2;'
-    LANGUAGE SQL
-    IMMUTABLE
-    RETURNS NULL ON NULL INPUT;
-</programlisting>
-  </para>
-
-  <para>
-   Increment an integer, making use of an argument name, in
-   <application>PL/pgSQL</application>:
-<programlisting>
-CREATE OR REPLACE FUNCTION increment(i integer) RETURNS integer AS $$
-        BEGIN
-                RETURN i + 1;
-        END;
-$$ LANGUAGE plpgsql;
-</programlisting>
-  </para>
-
-  <para>
-   Return a record containing multiple output parameters:
-<programlisting>
-CREATE FUNCTION dup(in int, out f1 int, out f2 text)
-    AS $$ SELECT $1, CAST($1 AS text) || ' is text' $$
-    LANGUAGE SQL;
-
-SELECT * FROM dup(42);
-</programlisting>
-   You can do the same thing more verbosely with an explicitly named
-   composite type:
-<programlisting>
-CREATE TYPE dup_result AS (f1 int, f2 text);
-
-CREATE FUNCTION dup(int) RETURNS dup_result
-    AS $$ SELECT $1, CAST($1 AS text) || ' is text' $$
-    LANGUAGE SQL;
-
-SELECT * FROM dup(42);
-</programlisting>
-   Another way to return multiple columns is to use a <literal>TABLE</>
-   function:
-<programlisting>
-CREATE FUNCTION dup(int) RETURNS TABLE(f1 int, f2 text)
-    AS $$ SELECT $1, CAST($1 AS text) || ' is text' $$
-    LANGUAGE SQL;
-
-SELECT * FROM dup(42);
-</programlisting>
-   However, a <literal>TABLE</> function is different from the
-   preceding examples, because it actually returns a <emphasis>set</>
-   of records, not just one record.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-createfunction-security">
-  <title>Writing <literal>SECURITY DEFINER</literal> Functions Safely</title>
-
-   <para>
-    Because a <literal>SECURITY DEFINER</literal> function is executed
-    with the privileges of the user that created it, care is needed to
-    ensure that the function cannot be misused.  For security,
-    <xref linkend="guc-search-path"> should be set to exclude any schemas
-    writable by untrusted users.  This prevents
-    malicious users from creating objects that mask objects used by the
-    function.  Particularly important in this regard is the
-    temporary-table schema, which is searched first by default, and
-    is normally writable by anyone.  A secure arrangement can be had
-    by forcing the temporary schema to be searched last.  To do this,
-    write <literal>pg_temp</> as the last entry in <varname>search_path</>.
-    This function illustrates safe usage:
-   </para>
-
-<programlisting>
-CREATE FUNCTION check_password(uname TEXT, pass TEXT)
-RETURNS BOOLEAN AS $$
-DECLARE passed BOOLEAN;
-BEGIN
-        SELECT  (pwd = $2) INTO passed
-        FROM    pwds
-        WHERE   username = $1;
-
-        RETURN passed;
-END;
-$$  LANGUAGE plpgsql
-    SECURITY DEFINER
-    -- Set a secure search_path: trusted schema(s), then 'pg_temp'.
-    SET search_path = admin, pg_temp;
-</programlisting>
-
-   <para>
-    Before <productname>PostgreSQL</productname> version 8.3, the
-    <literal>SET</> option was not available, and so older functions may
-    contain rather complicated logic to save, set, and restore
-    <varname>search_path</>.  The <literal>SET</> option is far easier
-    to use for this purpose.
-   </para>
-
-   <para>
-    Another point to keep in mind is that by default, execute privilege
-    is granted to <literal>PUBLIC</> for newly created functions
-    (see <xref linkend="sql-grant"> for more
-    information).  Frequently you will wish to restrict use of a security
-    definer function to only some users.  To do that, you must revoke
-    the default <literal>PUBLIC</> privileges and then grant execute
-    privilege selectively.  To avoid having a window where the new function
-    is accessible to all, create it and set the privileges within a single
-    transaction.  For example:
-   </para>
-
-<programlisting>
-BEGIN;
-CREATE FUNCTION check_password(uname TEXT, pass TEXT) ... SECURITY DEFINER;
-REVOKE ALL ON FUNCTION check_password(uname TEXT, pass TEXT) FROM PUBLIC;
-GRANT EXECUTE ON FUNCTION check_password(uname TEXT, pass TEXT) TO admins;
-COMMIT;
-</programlisting>
-
- </refsect1>
-
- <refsect1 id="sql-createfunction-compat">
-  <title>Compatibility</title>
-
-  <para>
-   A <command>CREATE FUNCTION</command> command is defined in SQL:1999 and later.
-<!## PG>
-   The <productname>PostgreSQL</productname> version is similar but
-<!## end>
-<!## XC>
-   The <productname>Postgres-XC</productname> version is similar but
-<!## end>
-<!## XL>
-   The <productname>Postgres-XL</productname> version is similar but
-<!## end>
-   not fully compatible.  The attributes are not portable, neither are the
-   different available languages.
-  </para>
-
-  <para>
-   For compatibility with some other database systems,
-   <replaceable class="parameter">argmode</replaceable> can be written
-   either before or after <replaceable class="parameter">argname</replaceable>.
-   But only the first way is standard-compliant.
-  </para>
-
-  <para>
-   The SQL standard does not specify parameter defaults.  The syntax
-   with the <literal>DEFAULT</literal> key word is from Oracle, and it
-   is somewhat in the spirit of the standard: SQL/PSM uses it for
-   variable default values.  The syntax with <literal>=</literal> is
-   used in T-SQL and Firebird.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterfunction"></member>
-   <member><xref linkend="sql-dropfunction"></member>
-   <member><xref linkend="sql-grant"></member>
-   <member><xref linkend="sql-load"></member>
-   <member><xref linkend="sql-revoke"></member>
-   <member><xref linkend="app-createlang"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_group.sgmlin b/doc-xc/src/sgml/ref/create_group.sgmlin
deleted file mode 100644
index 9d9182f802..0000000000
--- a/doc-xc/src/sgml/ref/create_group.sgmlin
+++ /dev/null
@@ -1,72 +0,0 @@
-<!--
-doc/src/sgml/ref/create_group.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEGROUP">
- <refmeta>
-  <refentrytitle>CREATE GROUP</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE GROUP</refname>
-  <refpurpose>define a new database role</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-creategroup">
-  <primary>CREATE GROUP</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE GROUP <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replaceable class="PARAMETER">option</replaceable> [ ... ] ]
-
-<phrase>where <replaceable class="PARAMETER">option</replaceable> can be:</phrase>
-
-      SUPERUSER | NOSUPERUSER
-    | CREATEDB | NOCREATEDB
-    | CREATEROLE | NOCREATEROLE
-    | CREATEUSER | NOCREATEUSER
-    | INHERIT | NOINHERIT
-    | LOGIN | NOLOGIN
-    | [ ENCRYPTED | UNENCRYPTED ] PASSWORD '<replaceable class="PARAMETER">password</replaceable>'
-    | VALID UNTIL '<replaceable class="PARAMETER">timestamp</replaceable>'
-    | IN ROLE <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | IN GROUP <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | ROLE <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | ADMIN <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | USER <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | SYSID <replaceable class="PARAMETER">uid</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE GROUP</command> is now an alias for
-   <xref linkend="sql-createrole">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>CREATE GROUP</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createrole"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_index.sgmlin b/doc-xc/src/sgml/ref/create_index.sgmlin
deleted file mode 100644
index 6106032f12..0000000000
--- a/doc-xc/src/sgml/ref/create_index.sgmlin
+++ /dev/null
@@ -1,775 +0,0 @@
-<!--
-doc/src/sgml/ref/create_index.sgml
-PostgreSQL documentation
--->
-<!## XC>
-<!-- NOTICE:
-     CONCURRENTLY not supported yet.
--->
-<!## end>
-<!## XL>
-<!-- NOTICE:
-     CONCURRENTLY not supported yet.
--->
-<!## end>
-
-<refentry id="SQL-CREATEINDEX">
- <refmeta>
-  <refentrytitle>CREATE INDEX</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE INDEX</refname>
-  <refpurpose>define a new index</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createindex">
-  <primary>CREATE INDEX</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<!## PG>
-<synopsis>
-CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ <replaceable class="parameter">name</replaceable> ] ON <replaceable class="parameter">table</replaceable> [ USING <replaceable class="parameter">method</replaceable> ]
-    ( { <replaceable class="parameter">column</replaceable> | ( <replaceable class="parameter">expression</replaceable> ) } [ COLLATE <replaceable class="parameter">collation</replaceable> ] [ <replaceable class="parameter">opclass</replaceable> ] [ ASC | DESC ] [ NULLS { FIRST | LAST } ] [, ...] )
-    [ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> = <replaceable class="PARAMETER">value</replaceable> [, ... ] ) ]
-    [ TABLESPACE <replaceable class="parameter">tablespace</replaceable> ]
-    [ WHERE <replaceable class="parameter">predicate</replaceable> ]
-</synopsis>
-<!## end>
-<!## XC>
-<synopsis>
-CREATE [ UNIQUE ] INDEX [ <replaceable class="parameter">name</replaceable> ] ON <replaceable class="parameter">table</replaceable> [ USING <replaceable class="parameter">method</replaceable> ]
-    ( { <replaceable class="parameter">column</replaceable> | ( <replaceable class="parameter">expression</replaceable> ) } [ <replaceable class="parameter">opclass</replaceable> ] [ ASC | DESC ] [ NULLS { FIRST | LAST } ] [, ...] )
-    [ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> = <replaceable class="PARAMETER">value</replaceable> [, ... ] ) ]
-    [ TABLESPACE <replaceable class="parameter">tablespace</replaceable> ]
-    [ WHERE <replaceable class="parameter">predicate</replaceable> ]
-</synopsis>
-<!## end>
-<!## XL>
-<synopsis>
-CREATE [ UNIQUE ] INDEX [ <replaceable class="parameter">name</replaceable> ] ON <replaceable class="parameter">table</replaceable> [ USING <replaceable class="parameter">method</replaceable> ]
-    ( { <replaceable class="parameter">column</replaceable> | ( <replaceable class="parameter">expression</replaceable> ) } [ <replaceable class="parameter">opclass</replaceable> ] [ ASC | DESC ] [ NULLS { FIRST | LAST } ] [, ...] )
-    [ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> = <replaceable class="PARAMETER">value</replaceable> [, ... ] ) ]
-    [ TABLESPACE <replaceable class="parameter">tablespace</replaceable> ]
-    [ WHERE <replaceable class="parameter">predicate</replaceable> ]
-</synopsis>
-<!## end>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE INDEX</command> constructs an index
-   on the specified column(s) of the specified table.
-   Indexes are primarily used to enhance database performance (though
-   inappropriate use can result in slower performance).
-  </para>
-
-  <para>
-   The key field(s) for the index are specified as column names,
-   or alternatively as expressions written in parentheses.
-   Multiple fields can be specified if the index method supports
-   multicolumn indexes.
-  </para>
-
-  <para>
-   An index field can be an expression computed from the values of
-   one or more columns of the table row.  This feature can be used
-   to obtain fast access to data based on some transformation of
-   the basic data. For example, an index computed on
-   <literal>upper(col)</> would allow the clause
-   <literal>WHERE upper(col) = 'JIM'</> to use an index.
-  </para>
-
-<!## PG>
-  <para>
-   <productname>PostgreSQL</productname> provides the index methods
-   B-tree, hash, GiST, and GIN.  Users can also define their own index
-   methods, but that is fairly complicated.
-  </para>
-<!## end>
-<!## XC>
-  <para>
-   <productname>Postgres-XC</productname> inherits the index methods
-   B-tree, hash, GiST, and GIN from <productname>PostgreSQL</>.  Users can also define their own index
-   methods, but that is fairly complicated.
-  </para>
-&xconly;
-  <para>
-   Please note that indexes are maintained only locally in each
-   Coordinator and/or Datanodes.  They do not have any information on
-   the column value outside Coordinator or Datanode.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   <productname>Postgres-XL</productname> inherits the index methods
-   B-tree, hash, GiST, and GIN from <productname>PostgreSQL</>.  Users can also define their own index
-   methods, but that is fairly complicated.
-  </para>
-&xlonly;
-  <para>
-   Please note that indexes are maintained only locally in each
-   Coordinator and/or Datanodes.  They do not have any information on
-   the column value outside Coordinator or Datanode.
-  </para>
-<!## end>
-
-  <para>
-    When the <literal>WHERE</literal> clause is present, a
-    <firstterm>partial index</firstterm> is created.
-    A partial index is an index that contains entries for only a portion of
-    a table, usually a portion that is more useful for indexing than the
-    rest of the table. For example, if you have a table that contains both
-    billed and unbilled orders where the unbilled orders take up a small
-    fraction of the total table and yet that is an often used section, you
-    can improve performance by creating an index on just that portion.
-    Another possible application is to use <literal>WHERE</literal> with
-    <literal>UNIQUE</literal> to enforce uniqueness over a subset of a
-    table.  See <xref linkend="indexes-partial"> for more discussion.
-  </para>
-
-  <para>
-    The expression used in the <literal>WHERE</literal> clause can refer
-    only to columns of the underlying table, but it can use all columns,
-    not just the ones being indexed.  Presently, subqueries and
-    aggregate expressions are also forbidden in <literal>WHERE</literal>.
-    The same restrictions apply to index fields that are expressions.
-  </para>
-
-  <para>
-   All functions and operators used in an index definition must be
-   <quote>immutable</>, that is, their results must depend only on
-   their arguments and never on any outside influence (such as
-   the contents of another table or the current time).  This restriction
-   ensures that the behavior of the index is well-defined.  To use a
-   user-defined function in an index expression or <literal>WHERE</literal>
-   clause, remember to mark the function immutable when you create it.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-&common;
-    <variablelist>
-     <varlistentry>
-      <term><literal>UNIQUE</literal></term>
-      <listitem>
-       <para>
-        Causes the system to check for
-        duplicate values in the table when the index is created (if data
-        already exist) and each time data is added. Attempts to
-        insert or update data which would result in duplicate entries
-        will generate an error.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CONCURRENTLY</literal></term>
-      <listitem>
-
-<!## XC>
-&xconly;
-      <para>
-       <productname>Postgres-XC</productname> does not
-       support <literal>CONCURRENTLY</literal> in the current release.
-      </para>
-<!## end>
-<!## XL>
-&xlonly;
-      <para>
-       <productname>Postgres-XL</productname> does not
-       support <literal>CONCURRENTLY</literal> in the current release.
-      </para>
-<!## end>
-<!## PG>
-       <para>
-        When this option is used, <productname>PostgreSQL</> will build the
-        index without taking any locks that prevent concurrent inserts,
-        updates, or deletes on the table; whereas a standard index build
-        locks out writes (but not reads) on the table until it's done.
-        There are several caveats to be aware of when using this option
-        &mdash; see <xref linkend="SQL-CREATEINDEX-CONCURRENTLY"
-        endterm="SQL-CREATEINDEX-CONCURRENTLY-title">.
-       </para>
-<!## end>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the index to be created.  No schema name can be included
-        here; the index is always created in the same schema as its parent
-<!## PG>
-        table.  If the name is omitted, <productname>PostgreSQL</> chooses a
-<!## end>
-<!## XC>
-        table.  If the name is omitted, <productname>Postgres-XC</> chooses a
-<!## end>
-<!## XL>
-        table.  If the name is omitted, <productname>Postgres-XL</> chooses a
-<!## end>
-        suitable name based on the parent table's name and the indexed column
-        name(s).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">table</replaceable></term>
-      <listitem>
-       <para>
-        The name (possibly schema-qualified) of the table to be indexed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">method</replaceable></term>
-      <listitem>
-       <para>
-        The name of the index method to be used.  Choices are
-        <literal>btree</literal>, <literal>hash</literal>,
-        <literal>gist</literal>, and <literal>gin</>.  The
-        default method is <literal>btree</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">column</replaceable></term>
-      <listitem>
-       <para>
-        The name of a column of the table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">expression</replaceable></term>
-      <listitem>
-       <para>
-        An expression based on one or more columns of the table.  The
-        expression usually must be written with surrounding parentheses,
-        as shown in the syntax.  However, the parentheses can be omitted
-        if the expression has the form of a function call.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">collation</replaceable></term>
-      <listitem>
-       <para>
-        The name of the collation to use for the index.  By default,
-        the index uses the collation declared for the column to be
-        indexed or the result collation of the expression to be
-        indexed.  Indexes with non-default collations can be useful for
-        queries that involve expressions using non-default collations.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">opclass</replaceable></term>
-      <listitem>
-       <para>
-        The name of an operator class. See below for details.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ASC</></term>
-      <listitem>
-       <para>
-        Specifies ascending sort order (which is the default).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>DESC</></term>
-      <listitem>
-       <para>
-        Specifies descending sort order.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>NULLS FIRST</></term>
-      <listitem>
-       <para>
-        Specifies that nulls sort before non-nulls.  This is the default
-        when <literal>DESC</> is specified.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>NULLS LAST</></term>
-      <listitem>
-       <para>
-        Specifies that nulls sort after non-nulls.  This is the default
-        when <literal>DESC</> is not specified.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">storage_parameter</replaceable></term>
-      <listitem>
-       <para>
-        The name of an index-method-specific storage parameter.  See
-        <xref linkend="sql-createindex-storage-parameters" endterm="sql-createindex-storage-parameters-title">
-        for details.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">tablespace</replaceable></term>
-      <listitem>
-       <para>
-        The tablespace in which to create the index.  If not specified,
-        <xref linkend="guc-default-tablespace"> is consulted, or
-        <xref linkend="guc-temp-tablespaces"> for indexes on temporary
-        tables.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">predicate</replaceable></term>
-      <listitem>
-       <para>
-        The constraint expression for a partial index.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-  <refsect2 id="SQL-CREATEINDEX-storage-parameters">
-   <title id="SQL-CREATEINDEX-storage-parameters-title">Index Storage Parameters</title>
-
-   <para>
-    The optional <literal>WITH</> clause specifies <firstterm>storage
-    parameters</> for the index.  Each index method has its own set of allowed
-    storage parameters.  The B-tree, hash and GiST index methods all accept a
-    single parameter:
-   </para>
-
-   <variablelist>
-
-   <varlistentry>
-    <term><literal>FILLFACTOR</></term>
-    <listitem>
-     <para>
-      The fillfactor for an index is a percentage that determines how full
-      the index method will try to pack index pages.  For B-trees, leaf pages
-      are filled to this percentage during initial index build, and also
-      when extending the index at the right (adding new largest key values).
-      If pages
-      subsequently become completely full, they will be split, leading to
-      gradual degradation in the index's efficiency.  B-trees use a default
-      fillfactor of 90, but any integer value from 10 to 100 can be selected.
-      If the table is static then fillfactor 100 is best to minimize the
-      index's physical size, but for heavily updated tables a smaller
-      fillfactor is better to minimize the need for page splits.  The
-      other index methods use fillfactor in different but roughly analogous
-      ways; the default fillfactor varies between methods.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   </variablelist>
-
-   <para>
-    GIN indexes accept a different parameter:
-   </para>
-
-   <variablelist>
-
-   <varlistentry>
-    <term><literal>FASTUPDATE</></term>
-    <listitem>
-    <para>
-     This setting controls usage of the fast update technique described in
-     <xref linkend="gin-fast-update">.  It is a Boolean parameter:
-     <literal>ON</> enables fast update, <literal>OFF</> disables it.
-     (Alternative spellings of <literal>ON</> and <literal>OFF</> are
-     allowed as described in <xref linkend="config-setting">.)  The
-     default is <literal>ON</>.
-    </para>
-
-    <note>
-     <para>
-      Turning <literal>FASTUPDATE</> off via <command>ALTER INDEX</> prevents
-      future insertions from going into the list of pending index entries,
-      but does not in itself flush previous entries.  You might want to
-      <command>VACUUM</> the table afterward to ensure the pending list is
-      emptied.
-     </para>
-    </note>
-    </listitem>
-   </varlistentry>
-
-   </variablelist>
-  </refsect2>
-
-  <refsect2 id="SQL-CREATEINDEX-CONCURRENTLY">
-   <title id="SQL-CREATEINDEX-CONCURRENTLY-title">Building Indexes Concurrently</title>
-
-   <indexterm zone="SQL-CREATEINDEX-CONCURRENTLY">
-   <primary>index</primary>
-   <secondary>building concurrently</secondary>
-   </indexterm>
-
-   <para>
-    Creating an index can interfere with regular operation of a database.
-<!## PG>
-    Normally <productname>PostgreSQL</> locks the table to be indexed against
-<!## end>
-<!## XC>
-    Normally <productname>Postgres-XC</> locks the table to be indexed against
-<!## end>
-<!## XL>
-    Normally <productname>Postgres-XL</> locks the table to be indexed against
-<!## end>
-    writes and performs the entire index build with a single scan of the
-    table. Other transactions can still read the table, but if they try to
-    insert, update, or delete rows in the table they will block until the
-    index build is finished. This could have a severe effect if the system is
-    a live production database.  Very large tables can take many hours to be
-    indexed, and even for smaller tables, an index build can lock out writers
-    for periods that are unacceptably long for a production system.
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</> supports building indexes without locking
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> supports building indexes without locking
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> supports building indexes without locking
-<!## end>
-    out writes.  This method is invoked by specifying the
-    <literal>CONCURRENTLY</> option of <command>CREATE INDEX</>.
-    When this option is used,
-<!## PG>
-    <productname>PostgreSQL</> must perform two scans of the table, and in
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> must perform two scans of the table, and in
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> must perform two scans of the table, and in
-<!## end>
-    addition it must wait for all existing transactions that could potentially
-    use the index to terminate.  Thus
-    this method requires more total work than a standard index build and takes
-    significantly longer to complete.  However, since it allows normal
-    operations to continue while the index is built, this method is useful for
-    adding new indexes in a production environment.  Of course, the extra CPU
-    and I/O load imposed by the index creation might slow other operations.
-   </para>
-
-   <para>
-    In a concurrent index build, the index is actually entered into the
-    system catalogs in one transaction, then the two table scans occur in a
-    second and third transaction.
-    If a problem arises while scanning the table, such as a
-    uniqueness violation in a unique index, the <command>CREATE INDEX</>
-    command will fail but leave behind an <quote>invalid</> index. This index
-    will be ignored for querying purposes because it might be incomplete;
-    however it will still consume update overhead. The <application>psql</>
-    <command>\d</> command will report such an index as <literal>INVALID</>:
-
-<programlisting>
-postgres=# \d tab
-       Table "public.tab"
- Column |  Type   | Modifiers 
---------+---------+-----------
- col    | integer | 
-Indexes:
-    "idx" btree (col) INVALID
-</programlisting>
-
-    The recommended recovery
-    method in such cases is to drop the index and try again to perform
-    <command>CREATE INDEX CONCURRENTLY</>.  (Another possibility is to rebuild
-    the index with <command>REINDEX</>.  However, since <command>REINDEX</>
-    does not support concurrent builds, this option is unlikely to seem
-    attractive.)
-   </para>
-
-   <para>
-    Another caveat when building a unique index concurrently is that the
-    uniqueness constraint is already being enforced against other transactions
-    when the second table scan begins.  This means that constraint violations
-    could be reported in other queries prior to the index becoming available
-    for use, or even in cases where the index build eventually fails.  Also,
-    if a failure does occur in the second scan, the <quote>invalid</> index
-    continues to enforce its uniqueness constraint afterwards.
-   </para>
-
-   <para>
-    Concurrent builds of expression indexes and partial indexes are supported.
-    Errors occurring in the evaluation of these expressions could cause
-    behavior similar to that described above for unique constraint violations.
-   </para>
-
-   <para>
-    Regular index builds permit other regular index builds on the
-    same table to occur in parallel, but only one concurrent index build
-    can occur on a table at a time.  In both cases, no other types of schema
-    modification on the table are allowed meanwhile.  Another difference
-    is that a regular <command>CREATE INDEX</> command can be performed within
-    a transaction block, but <command>CREATE INDEX CONCURRENTLY</> cannot.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   See <xref linkend="indexes"> for information about when indexes can
-   be used, when they are not used, and in which particular situations
-   they can be useful.
-  </para>
-
-  <para>
-   Currently, only the B-tree, GiST and GIN index methods support
-   multicolumn indexes. Up to 32 fields can be specified by default.
-   (This limit can be altered when building
-<!## PG>
-   <productname>PostgreSQL</productname>.)  Only B-tree currently
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>.)  Only B-tree currently
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>.)  Only B-tree currently
-<!## end>
-   supports unique indexes.
-  </para>
-
-  <para>
-   An <firstterm>operator class</firstterm> can be specified for each
-   column of an index. The operator class identifies the operators to be
-   used by the index for that column. For example, a B-tree index on
-   four-byte integers would use the <literal>int4_ops</literal> class;
-   this operator class includes comparison functions for four-byte
-   integers. In practice the default operator class for the column's data
-   type is usually sufficient. The main point of having operator classes
-   is that for some data types, there could be more than one meaningful
-   ordering. For example, we might want to sort a complex-number data
-   type either by absolute value or by real part. We could do this by
-   defining two operator classes for the data type and then selecting
-   the proper class when making an index.  More information about
-   operator classes is in <xref linkend="indexes-opclass"> and in <xref
-   linkend="xindex">.
-  </para>
-
-  <para>
-   For index methods that support ordered scans (currently, only B-tree),
-   the optional clauses <literal>ASC</>, <literal>DESC</>, <literal>NULLS
-   FIRST</>, and/or <literal>NULLS LAST</> can be specified to modify
-   the sort ordering of the index.  Since an ordered index can be
-   scanned either forward or backward, it is not normally useful to create a
-   single-column <literal>DESC</> index &mdash; that sort ordering is already
-   available with a regular index.  The value of these options is that
-   multicolumn indexes can be created that match the sort ordering requested
-   by a mixed-ordering query, such as <literal>SELECT ... ORDER BY x ASC, y
-   DESC</>.  The <literal>NULLS</> options are useful if you need to support
-   <quote>nulls sort low</> behavior, rather than the default <quote>nulls
-   sort high</>, in queries that depend on indexes to avoid sorting steps.
-  </para>
-
-  <para>
-   For most index methods, the speed of creating an index is
-   dependent on the setting of <xref linkend="guc-maintenance-work-mem">.
-   Larger values will reduce the time needed for index creation, so long
-   as you don't make it larger than the amount of memory really available,
-   which would drive the machine into swapping.  For hash indexes, the
-   value of <xref linkend="guc-effective-cache-size"> is also relevant to
-<!## PG>
-   index creation time: <productname>PostgreSQL</productname> will use one
-<!## end>
-<!## XC>
-   index creation time: <productname>Postgres-XC</productname> will use one
-<!## end>
-<!## XL>
-   index creation time: <productname>Postgres-XL</productname> will use one
-<!## end>
-   of two different hash index creation methods depending on whether the
-   estimated index size is more or less than <varname>effective_cache_size</>.
-   For best results, make sure that this parameter is also set to something
-   reflective of available memory, and be careful that the sum of
-   <varname>maintenance_work_mem</> and <varname>effective_cache_size</> is
-   less than the machine's RAM less whatever space is needed by other
-   programs.
-  </para>
-
-  <para>
-   Use <xref linkend="sql-dropindex">
-   to remove an index.
-  </para>
-
-  <para>
-<!## PG>
-   Prior releases of <productname>PostgreSQL</productname> also had an
-<!## end>
-<!## XC>
-   Prior releases of <productname>Postgres-XC</productname> also had an
-<!## end>
-<!## XL>
-   Prior releases of <productname>Postgres-XL</productname> also had an
-<!## end>
-   R-tree index method.  This method has been removed because
-   it had no significant advantages over the GiST method.
-   If <literal>USING rtree</> is specified, <command>CREATE INDEX</>
-   will interpret it as <literal>USING gist</>, to simplify conversion
-   of old databases to GiST.
-  </para>
-
-<!## XC>
-&xconly;
-   <para>
-    With a hash or a round-robin table, it is forbidden to create an unique index.
-   </para>
-   <para>
-    It is not possible to create concurrent index.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    With a hash or a round-robin table, it is forbidden to create an unique index.
-   </para>
-   <para>
-    It is not possible to create concurrent index.
-   </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-&common;
-  <para>
-   To create a B-tree index on the column <literal>title</literal> in
-   the table <literal>films</literal>:
-<programlisting>
-CREATE UNIQUE INDEX title_idx ON films (title);
-</programlisting>
-  </para>
-
-  <para>
-   To create an index on the expression <literal>lower(title)</>,
-   allowing efficient case-insensitive searches:
-<programlisting>
-CREATE INDEX ON films ((lower(title)));
-</programlisting>
-   (In this example we have chosen to omit the index name, so the system
-   will choose a name, typically <literal>films_lower_idx</>.)
-  </para>
-
-  <para>
-   To create an index with non-default collation:
-<programlisting>
-CREATE INDEX title_idx_german ON films (title COLLATE "de_DE");
-</programlisting>
-  </para>
-
-  <para>
-   To create an index with non-default sort ordering of nulls:
-<programlisting>
-CREATE INDEX title_idx_nulls_low ON films (title NULLS FIRST);
-</programlisting>
-  </para>
-
-  <para>
-   To create an index with non-default fill factor:
-<programlisting>
-CREATE UNIQUE INDEX title_idx ON films (title) WITH (fillfactor = 70);
-</programlisting>
-  </para>
-
-  <para>
-   To create a <acronym>GIN</> index with fast updates disabled:
-<programlisting>
-CREATE INDEX gin_idx ON documents_table USING gin (locations) WITH (fastupdate = off);
-</programlisting>
-  </para>
-
-  <para>
-   To create an index on the column <literal>code</> in the table
-   <literal>films</> and have the index reside in the tablespace
-   <literal>indexspace</>:
-<programlisting>
-CREATE INDEX code_idx ON films (code) TABLESPACE indexspace;
-</programlisting>
-  </para>
-
-  <para>
-   To create a GiST index on a point attribute so that we
-   can efficiently use box operators on the result of the
-   conversion function:
-<programlisting>
-CREATE INDEX pointloc
-    ON points USING gist (box(location,location));
-SELECT * FROM points
-    WHERE box(location,location) &amp;&amp; '(0,0),(1,1)'::box;
-</programlisting>
-  </para>
-
-  <para>
-   To create an index without locking out writes to the table:
-<programlisting>
-CREATE INDEX CONCURRENTLY sales_quantity_index ON sales_table (quantity);
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE INDEX</command> is a
-<!## PG>
-   <productname>PostgreSQL</productname> language extension.  There
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> language extension.  There
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> language extension.  There
-<!## end>
-   are no provisions for indexes in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterindex"></member>
-   <member><xref linkend="sql-dropindex"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_language.sgmlin b/doc-xc/src/sgml/ref/create_language.sgmlin
deleted file mode 100644
index 0ec3e84b01..0000000000
--- a/doc-xc/src/sgml/ref/create_language.sgmlin
+++ /dev/null
@@ -1,388 +0,0 @@
-<!--
-doc/src/sgml/ref/create_language.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATELANGUAGE">
- <refmeta>
-  <refentrytitle>CREATE LANGUAGE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE LANGUAGE</refname>
-  <refpurpose>define a new procedural language</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createlanguage">
-  <primary>CREATE LANGUAGE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE [ OR REPLACE ] [ PROCEDURAL ] LANGUAGE <replaceable class="parameter">name</replaceable>
-CREATE [ OR REPLACE ] [ TRUSTED ] [ PROCEDURAL ] LANGUAGE <replaceable class="parameter">name</replaceable>
-    HANDLER <replaceable class="parameter">call_handler</replaceable> [ INLINE <replaceable class="parameter">inline_handler</replaceable> ] [ VALIDATOR <replaceable>valfunction</replaceable> ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-createlanguage-description">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE LANGUAGE</command> registers a new
-<!## PG>
-   procedural language with a <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   procedural language with a <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   procedural language with a <productname>Postgres-XL</productname>
-<!## end>
-   database.  Subsequently, functions and trigger procedures can be
-   defined in this new language.
-  </para>
-
-  <note>
-   <para>
-    As of <productname>PostgreSQL</productname> 9.1, most procedural
-    languages have been made into <quote>extensions</>, and should
-    therefore be installed with <xref linkend="sql-createextension">
-    not <command>CREATE LANGUAGE</command>.  Direct use of
-    <command>CREATE LANGUAGE</command> should now be confined to
-    extension installation scripts.  If you have a <quote>bare</>
-    language in your database, perhaps as a result of an upgrade,
-    you can convert it to an extension using
-    <literal>CREATE EXTENSION <replaceable>langname</> FROM
-    unpackaged</literal>.
-   </para>
-  </note>
-
-  <para>
-   <command>CREATE LANGUAGE</command> effectively associates the
-   language name with handler function(s) that are responsible for executing
-   functions written in the language.  Refer to <xref linkend="plhandler">
-   for more information about language handlers.
-  </para>
-
-  <para>
-   There are two forms of the <command>CREATE LANGUAGE</command> command.
-   In the first form, the user supplies just the name of the desired
-<!## PG>
-   language, and the <productname>PostgreSQL</productname> server consults
-<!## end>
-<!## XC>
-   language, and the <productname>Postgres-XC</productname> servers consult
-<!## end>
-<!## XL>
-   language, and the <productname>Postgres-XL</productname> servers consult
-<!## end>
-   the <link linkend="catalog-pg-pltemplate"><structname>pg_pltemplate</structname></link>
-   system catalog to determine the correct parameters.  In the second form,
-   the user supplies the language parameters along with the language name.
-   The second form can be used to create a language that is not defined in
-   <structname>pg_pltemplate</>, but this approach is considered obsolescent.
-  </para>
-
-  <para>
-   When the server finds an entry in the <structname>pg_pltemplate</> catalog
-   for the given language name, it will use the catalog data even if the
-   command includes language parameters.  This behavior simplifies loading of
-   old dump files, which are likely to contain out-of-date information
-   about language support functions.
-  </para>
-
-  <para>
-   Ordinarily, the user must have the
-<!## PG>
-   <productname>PostgreSQL</productname> superuser privilege to
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> superuser privilege to
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> superuser privilege to
-<!## end>
-   register a new language.  However, the owner of a database can register
-   a new language within that database if the language is listed in
-   the <structname>pg_pltemplate</structname> catalog and is marked
-   as allowed to be created by database owners (<structfield>tmpldbacreate</>
-   is true).  The default is that trusted languages can be created
-   by database owners, but this can be adjusted by superusers by modifying
-   the contents of <structname>pg_pltemplate</structname>.
-   The creator of a language becomes its owner and can later
-   drop it, rename it, or assign it to a new owner.
-  </para>
-
-  <para>
-   <command>CREATE OR REPLACE LANGUAGE</command> will either create a
-   new language, or replace an existing definition.  If the language
-   already exists, its parameters are updated according to the values
-   specified or taken from <structname>pg_pltemplate</structname>,
-   but the language's ownership and permissions settings do not change,
-   and any existing functions written in the language are assumed to still
-   be valid.  In addition to the normal privilege requirements for creating
-   a language, the user must be superuser or owner of the existing language.
-   The <literal>REPLACE</> case is mainly meant to be used to
-   ensure that the language exists.  If the language has a
-   <structname>pg_pltemplate</structname> entry then <literal>REPLACE</>
-   will not actually change anything about an existing definition, except in
-   the unusual case where the <structname>pg_pltemplate</structname> entry
-   has been modified since the language was created.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-createlanguage-parameters">
-  <title>Parameters</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>TRUSTED</literal></term>
-
-     <listitem>
-      <para>
-       <literal>TRUSTED</literal> specifies that the language does
-       not grant access to data that the user would not otherwise
-       have.  If this key word is omitted
-       when registering the language, only users with the
-<!## PG>
-       <productname>PostgreSQL</productname> superuser privilege can
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</productname> superuser privilege can
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</productname> superuser privilege can
-<!## end>
-       use this language to create new functions.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>PROCEDURAL</literal></term>
-
-     <listitem>
-      <para>
-       This is a noise word.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">name</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the new procedural language.  The language name is
-       case insensitive. The name must be unique among the languages
-       in the database.
-      </para>
-
-      <para>
-       For backward compatibility, the name can be enclosed by single
-       quotes.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>HANDLER</literal> <replaceable class="parameter">call_handler</replaceable></term>
-
-     <listitem>
-      <para>
-       <replaceable class="parameter">call_handler</replaceable> is
-       the name of a previously registered function that will be
-       called to execute the procedural language's functions.  The call
-       handler for a procedural language must be written in a compiled
-       language such as C with version 1 call convention and
-<!## PG>
-       registered with <productname>PostgreSQL</productname> as a
-<!## end>
-<!## XC>
-       registered with <productname>Postgres-XC</productname> as a
-<!## end>
-<!## XL>
-       registered with <productname>Postgres-XL</productname> as a
-<!## end>
-       function taking no arguments and returning the
-       <type>language_handler</type> type, a placeholder type that is
-       simply used to identify the function as a call handler.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>INLINE</literal> <replaceable class="parameter">inline_handler</replaceable></term>
-
-     <listitem>
-      <para>
-       <replaceable class="parameter">inline_handler</replaceable> is the
-       name of a previously registered function that will be called
-       to execute an anonymous code block
-       (<xref linkend="sql-do"> command)
-       in this language.
-       If no <replaceable class="parameter">inline_handler</replaceable>
-       function is specified, the language does not support anonymous code
-       blocks.
-       The handler function must take one argument of
-       type <type>internal</type>, which will be the <command>DO</> command's
-       internal representation, and it will typically return
-       <type>void</>.  The return value of the handler is ignored.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>VALIDATOR</literal> <replaceable class="parameter">valfunction</replaceable></term>
-
-     <listitem>
-      <para>
-       <replaceable class="parameter">valfunction</replaceable> is the
-       name of a previously registered function that will be called
-       when a new function in the language is created, to validate the
-       new function.
-       If no
-       validator function is specified, then a new function will not
-       be checked when it is created.
-       The validator function must take one argument of
-       type <type>oid</type>, which will be the OID of the
-       to-be-created function, and will typically return <type>void</>.
-      </para>
-
-      <para>
-       A validator function would typically inspect the function body
-       for syntactical correctness, but it can also look at other
-       properties of the function, for example if the language cannot
-       handle certain argument types.  To signal an error, the
-       validator function should use the <function>ereport()</function>
-       function.  The return value of the function is ignored.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-  <para>
-   The <literal>TRUSTED</> option and the support function name(s) are
-   ignored if the server has an entry for the specified language
-   name in <structname>pg_pltemplate</>.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-createlanguage-notes">
-  <title>Notes</title>
-
-  <para>
-   The <xref linkend="app-createlang"> program is a simple wrapper around
-   the <command>CREATE LANGUAGE</> command.  It eases
-   installation of procedural languages from the shell command line.
-  </para>
-
-  <para>
-   Use <xref linkend="sql-droplanguage">, or better yet the <xref
-   linkend="app-droplang"> program, to drop procedural languages.
-  </para>
-
-  <para>
-   The system catalog <classname>pg_language</classname> (see <xref
-   linkend="catalog-pg-language">) records information about the
-   currently installed languages.  Also, <command>createlang</command>
-   has an option to list the installed languages.
-  </para>
-
-  <para>
-   To create functions in a procedural language, a user must have the
-   <literal>USAGE</literal> privilege for the language.  By default,
-   <literal>USAGE</> is granted to <literal>PUBLIC</> (i.e., everyone)
-   for trusted languages.  This can be revoked if desired.
-  </para>
-
-  <para>
-   Procedural languages are local to individual databases.
-   However, a language can be installed into the <literal>template1</literal>
-   database, which will cause it to be available automatically in
-   all subsequently-created databases.
-  </para>
-
-  <para>
-   The call handler function, the inline handler function (if any),
-   and the validator function (if any)
-   must already exist if the server does not have an entry for the language
-   in <structname>pg_pltemplate</>.  But when there is an entry,
-   the functions need not already exist;
-   they will be automatically defined if not present in the database.
-   (This might result in <command>CREATE LANGUAGE</> failing, if the
-   shared library that implements the language is not available in
-   the installation.)
-  </para>
-
-  <para>
-   In <productname>PostgreSQL</productname> versions before 7.3, it was
-   necessary to declare handler functions as returning the placeholder
-   type <type>opaque</>, rather than <type>language_handler</>.
-   To support loading
-   of old dump files, <command>CREATE LANGUAGE</> will accept a function
-   declared as returning <type>opaque</>, but it will issue a notice and
-   change the function's declared return type to <type>language_handler</>.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-createlanguage-examples">
-  <title>Examples</title>
-
-  <para>
-   The preferred way of creating any of the standard procedural languages
-   is just:
-<programlisting>
-CREATE LANGUAGE plperl;
-</programlisting>
-  </para>
-
-  <para>
-   For a language not known in the <structname>pg_pltemplate</> catalog, a
-   sequence such as this is needed:
-<programlisting>
-CREATE FUNCTION plsample_call_handler() RETURNS language_handler
-    AS '$libdir/plsample'
-    LANGUAGE C;
-CREATE LANGUAGE plsample
-    HANDLER plsample_call_handler;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="sql-createlanguage-compat">
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE LANGUAGE</command> is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterlanguage"></member>
-   <member><xref linkend="sql-createfunction"></member>
-   <member><xref linkend="sql-droplanguage"></member>
-   <member><xref linkend="sql-grant"></member>
-   <member><xref linkend="sql-revoke"></member>
-   <member><xref linkend="app-createlang"></member>
-   <member><xref linkend="app-droplang"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_node.sgmlin b/doc-xc/src/sgml/ref/create_node.sgmlin
deleted file mode 100644
index 0b7e9fa993..0000000000
--- a/doc-xc/src/sgml/ref/create_node.sgmlin
+++ /dev/null
@@ -1,393 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_node.sgml,v 1.54 2010/04/03 07:22:58 petere Exp $
-PostgreSQL documentation
--->
-<!## XC>
-<refentry id="SQL-CREATENODE">
- <refmeta>
-  <refentrytitle>CREATE NODE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE NODE</refname>
-  <refpurpose>create a new cluster node</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createnode">
-  <primary>CREATE NODE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE NODE <replaceable class="parameter">nodename</replaceable> WITH
-  (
-    [ TYPE = <replaceable class="parameter">nodetype</replaceable>,]
-    [ HOST = <replaceable class="parameter">hostname</replaceable>,]
-    [ PORT = <replaceable class="parameter">portnum</replaceable>,]
-    [ PRIMARY [ = <replaceable class="parameter">boolean</replaceable> ],]
-    [ PREFERRED [ = <replaceable class="parameter">boolean</replaceable> ] ]
-  )
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xconly;
-
-  <para>
-   <command>CREATE NODE</command> is new SQL query specific
-   to <productname>Postgres-XC</productname> since 0.9.7 that creates
-   a new entry in catalog table pgxc_node with node data.
-  </para>
-  <para>
-   This node data is directly used by a Coordinator session when connecting
-   to build connection data to cluster nodes through <productname>Postgres-XC
-   </productname> pooler.
-  </para>
-  <para>
-   Node connection information is created on pooler only if it has not been
-   the case yet on Coordinator connected at the moment of connection.
-  </para>
-  <para>
-   <command>CREATE NODE</command> only runs on the local node where it is launched.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">nodename</replaceable></term>
-      <listitem>
-       <para>
-        The name of the selected cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>TYPE</literal></term>
-      <listitem>
-       <para>
-        The type of the cluster node. It is possible to specify
-        a Coordinator node or a Datanode node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PRIMARY</literal></term>
-      <listitem>
-       <para>
-        Defines if the cluster node is used as a primary node for replicated
-        write operations. A <replaceable class="parameter">boolean</replaceable>
-        value can be specified. In case no value is specified, <literal>PRIMARY</literal>
-        acts like <literal>false</>.
-       </para>
-	   <para>
-        To avoid deadlock and make update consistetnt, you should specify the same <literal>PRIMARY</literal>
-        node at all the nodes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PREFERRED</literal></term>
-      <listitem>
-       <para>
-        Defines if the cluster node is used as a preferred node for replicated
-        read operations if no node is determined. A <replaceable class="parameter">boolean</replaceable>
-        value can be specified. In case no value is specified, <literal>PREFERRED</literal>
-        acts like <literal>false</>.
-       </para>
-	   <para>
-        You can specify different <literal>PREFERRED</literal> node at different coordinator.
-        This parameter affects performance of your <literal>Postgres-XC</literal> cluster.
-        If you configure a datanode where you configure a coordinator, 
-        you should specify <literal>PREFERRED</literal> for the coordinator to such a local datanode.
-        This will save network communication and improve cluster-wide performance.
-       </para>
-        
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">nodetype</replaceable></term>
-      <listitem>
-       <para>
-        The node type for given cluster node. Possible values are:
-        'coordinator' for a Coordinator node and 'datanode' for a
-        Datanode node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">hostname</replaceable></term>
-      <listitem>
-       <para>
-        The hostname or IP used to connect to the cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">portnum</replaceable></term>
-      <listitem>
-       <para>
-        The port number used to connect to the cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-  <para>
-    <replaceable class="parameter">nodename</replaceable> remains constant
-    as long as it is in use.
-  </para>
-
-  <para>
-    When using a cluster with 1 Coordinator and 1 Datanode on each server,
-    Defining the local Datanode as <literal>PREFERRED</literal> can greatly
-    improve the performance of a system by avoiding any network overhead for
-    replicated reads, as in this case a local socket is used for communication
-    between nodes. This has even more effects when the application uses heavily
-    replicated table for remote join operations and that those operations can
-    be operated on the local <literal>PREFERRED</literal> node.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-  <para>
-   Create a Coordinator node located on local machine using port 6543
-<programlisting>
-CREATE NODE node2 WITH (TYPE = 'coordinator', HOST = 'localhost', PORT = 6543);
-</programlisting>
-  </para>
-
-  <para>
-   Create a Datanode which is a preferred and primary node
-   located on remote machine with IP '192.168.0.3' on port 8888.
-<programlisting>
-CREATE NODE node2 WITH (TYPE = 'datanode', HOST = '192.168.0.3', PORT = 8888, PRIMARY, PREFERRED);
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>CREATE NODE</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XC specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
-<!## XL>
-<refentry id="SQL-CREATENODE">
- <refmeta>
-  <refentrytitle>CREATE NODE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE NODE</refname>
-  <refpurpose>create a new cluster node</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createnode">
-  <primary>CREATE NODE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE NODE <replaceable class="parameter">nodename</replaceable> WITH
-  (
-    [ TYPE = <replaceable class="parameter">nodetype</replaceable>,]
-    [ HOST = <replaceable class="parameter">hostname</replaceable>,]
-    [ PORT = <replaceable class="parameter">portnum</replaceable>,]
-    [ PRIMARY [ = <replaceable class="parameter">boolean</replaceable> ],]
-    [ PREFERRED [ = <replaceable class="parameter">boolean</replaceable> ] ]
-  )
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xlonly;
-
-  <para>
-   <command>CREATE NODE</command> is a SQL command specific
-   to <productname>Postgres-XL</productname> that creates
-   a new entry in catalog table pgxc_node with node data.
-  </para>
-  <para>
-   This node data is directly used by a Coordinator session and its
-   corresponding Datanode sessions when connecting
-   to build connection data to cluster nodes through <productname>Postgres-XL
-   </productname> pooler.
-  </para>
-  <para>
-   Node connection information is created on pooler only if it has not been
-   the case yet on Coordinator connected at the moment of connection.
-  </para>
-  <para>
-   <command>CREATE NODE</command> only runs on the local node where it is launched.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">nodename</replaceable></term>
-      <listitem>
-       <para>
-        The name of the selected cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>TYPE</literal></term>
-      <listitem>
-       <para>
-        The type of the cluster node. It is possible to specify
-        a Coordinator node or a Datanode node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PRIMARY</literal></term>
-      <listitem>
-       <para>
-        Defines if the cluster node is used as a primary node for replicated
-        write operations. A <replaceable class="parameter">boolean</replaceable>
-        value can be specified. In case no value is specified, <literal>PRIMARY</literal>
-        acts like <literal>false</>.
-       </para>
-	   <para>
-        To avoid deadlocks and make update consistent, you should specify the same <literal>PRIMARY</literal>
-        node at all the nodes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PREFERRED</literal></term>
-      <listitem>
-       <para>
-        Defines if the cluster node is used as a preferred node for replicated
-        read operations if no node is determined. A <replaceable class="parameter">boolean</replaceable>
-        value can be specified. In case no value is specified, <literal>PREFERRED</literal>
-        acts like <literal>false</>.
-       </para>
-	   <para>
-        You can specify different <literal>PREFERRED</literal> node at different coordinator.
-        This parameter affects performance of your <literal>Postgres-XL</literal> cluster.
-        If you configure a datanode where you configure a coordinator, 
-        you should specify <literal>PREFERRED</literal> for the coordinator to such a local datanode.
-        This will save network communication and improve cluster-wide performance.
-       </para>
-        
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">nodetype</replaceable></term>
-      <listitem>
-       <para>
-        The node type for given cluster node. Possible values are:
-        'coordinator' for a Coordinator node and 'datanode' for a
-        Datanode node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">hostname</replaceable></term>
-      <listitem>
-       <para>
-        The hostname or IP used to connect to the cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">portnum</replaceable></term>
-      <listitem>
-       <para>
-        The port number used to connect to the cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-  <para>
-    <replaceable class="parameter">nodename</replaceable> remains constant
-    as long as it is in use.
-  </para>
-
-  <para>
-    When using a cluster with 1 Coordinator and 1 Datanode on each server,
-    defining the local Datanode as <literal>PREFERRED</literal> can greatly
-    improve the performance of a system by avoiding any network overhead for
-    replicated reads, as in this case a local socket is used for communication
-    between nodes. This has even more effects when the application frequently uses 
-    replicated tables for remote join operations and that those operations can
-    be operated on the local <literal>PREFERRED</literal> node.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-  <para>
-   Create a Coordinator node located on local machine using port 6543
-<programlisting>
-CREATE NODE node2 WITH (TYPE = 'coordinator', HOST = 'localhost', PORT = 6543);
-</programlisting>
-  </para>
-
-  <para>
-   Create a Datanode which is a preferred and primary node
-   located on remote machine with IP '192.168.0.3' on port 8888.
-<programlisting>
-CREATE NODE node2 WITH (TYPE = 'datanode', HOST = '192.168.0.3', PORT = 8888, PRIMARY, PREFERRED);
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>CREATE NODE</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XL specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
diff --git a/doc-xc/src/sgml/ref/create_nodegroup.sgmlin b/doc-xc/src/sgml/ref/create_nodegroup.sgmlin
deleted file mode 100644
index d24bbccadf..0000000000
--- a/doc-xc/src/sgml/ref/create_nodegroup.sgmlin
+++ /dev/null
@@ -1,196 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_nodegroup.sgml,v 1.54 2010/04/03 07:22:58 petere Exp $
-PostgreSQL documentation
--->
-<!## XC>
-<refentry id="SQL-CREATENODEGROUP">
- <refmeta>
-  <refentrytitle>CREATE NODE GROUP</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE NODE GROUP</refname>
-  <refpurpose>create a group of cluster nodes</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createnodegroup">
-  <primary>CREATE NODE GROUP</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE NODE GROUP <replaceable class="parameter">groupname</replaceable>
-WITH ( <replaceable class="parameter">nodename</replaceable> [, ... ] )
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xconly;
-
-  <para>
-   <command>CREATE NODE GROUP</command> is new SQL query specific
-   to <productname>Postgres-XC</productname> since 0.9.7 that creates
-   node group information in catalog pgxc_group.
-  </para>
-
-  <para>
-   <command>CREATE NODE</command> only runs on the local node where it is launched.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">groupname</replaceable></term>
-      <listitem>
-       <para>
-        The name of the selected cluster node group.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">nodename</replaceable></term>
-      <listitem>
-       <para>
-        The name of a cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-  <para>
-   A group of nodes works as an alias for node lists when defining tables
-   on sub-clusters. Only Datanode can be included in node groups.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a cluster node group made of nodes called Datanode1, Datanode2.
-<programlisting>
-CREATE NODE GROUP cluster_group WITH Datanode1, Datanode2;
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>CREATE NODE GROUP</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XC specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
-<!## XL>
-<refentry id="SQL-CREATENODEGROUP">
- <refmeta>
-  <refentrytitle>CREATE NODE GROUP</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE NODE GROUP</refname>
-  <refpurpose>create a group of cluster nodes</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createnodegroup">
-  <primary>CREATE NODE GROUP</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE NODE GROUP <replaceable class="parameter">groupname</replaceable>
-WITH ( <replaceable class="parameter">nodename</replaceable> [, ... ] )
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xlonly;
-
-  <para>
-   <command>CREATE NODE GROUP</command> is a SQL command specific
-   to <productname>Postgres-XL</productname> that creates
-   node group information in catalog pgxc_group.
-  </para>
-
-  <para>
-   <command>CREATE NODE</command> only runs on the local node where it is launched.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">groupname</replaceable></term>
-      <listitem>
-       <para>
-        The name of the selected cluster node group.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">nodename</replaceable></term>
-      <listitem>
-       <para>
-        The name of a cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-  <para>
-   A group of nodes works as an alias for node lists when defining tables
-   on sub-clusters. Only Datanode can be included in node groups.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a cluster node group made of nodes called Datanode1, Datanode2.
-<programlisting>
-CREATE NODE GROUP cluster_group WITH Datanode1, Datanode2;
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>CREATE NODE GROUP</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a <productname>Postgres-XL</productname> specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
diff --git a/doc-xc/src/sgml/ref/create_opclass.sgmlin b/doc-xc/src/sgml/ref/create_opclass.sgmlin
deleted file mode 100644
index 4b60a0f609..0000000000
--- a/doc-xc/src/sgml/ref/create_opclass.sgmlin
+++ /dev/null
@@ -1,332 +0,0 @@
-<!--
-doc/src/sgml/ref/create_opclass.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEOPCLASS">
- <refmeta>
-  <refentrytitle>CREATE OPERATOR CLASS</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE OPERATOR CLASS</refname>
-  <refpurpose>define a new operator class</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createopclass">
-  <primary>CREATE OPERATOR CLASS</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE OPERATOR CLASS <replaceable class="parameter">name</replaceable> [ DEFAULT ] FOR TYPE <replaceable class="parameter">data_type</replaceable>
-  USING <replaceable class="parameter">index_method</replaceable> [ FAMILY <replaceable class="parameter">family_name</replaceable> ] AS
-  {  OPERATOR <replaceable class="parameter">strategy_number</replaceable> <replaceable class="parameter">operator_name</replaceable> [ ( <replaceable class="parameter">op_type</replaceable>, <replaceable class="parameter">op_type</replaceable> ) ] [ FOR SEARCH | FOR ORDER BY <replaceable class="parameter">sort_family_name</replaceable> ]
-   | FUNCTION <replaceable class="parameter">support_number</replaceable> [ ( <replaceable class="parameter">op_type</replaceable> [ , <replaceable class="parameter">op_type</replaceable> ] ) ] <replaceable class="parameter">function_name</replaceable> ( <replaceable class="parameter">argument_type</replaceable> [, ...] )
-   | STORAGE <replaceable class="parameter">storage_type</replaceable>
-  } [, ... ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE OPERATOR CLASS</command> creates a new operator class.
-   An operator class defines how a particular data type can be used with
-   an index.  The operator class specifies that certain operators will fill
-   particular roles or <quote>strategies</> for this data type and this
-   index method.  The operator class also specifies the support procedures to
-   be used by
-   the index method when the operator class is selected for an
-   index column.  All the operators and functions used by an operator
-   class must be defined before the operator class can be created.
-  </para>
-
-  <para>
-   If a schema name is given then the operator class is created in the
-   specified schema.  Otherwise it is created in the current schema.
-   Two operator classes in the same schema can have the same name only if they
-   are for different index methods.
-  </para>
-
-  <para>
-   The user who defines an operator class becomes its owner.  Presently,
-   the creating user must be a superuser.  (This restriction is made because
-   an erroneous operator class definition could confuse or even crash the
-   server.)
-  </para>
-
-  <para>
-   <command>CREATE OPERATOR CLASS</command> does not presently check
-   whether the operator class definition includes all the operators and
-   functions required by the index method, nor whether the operators and
-   functions form a self-consistent set.  It is the user's
-   responsibility to define a valid operator class.
-  </para>
-
-  <para>
-   Related operator classes can be grouped into <firstterm>operator
-   families</>.  To add a new operator class to an existing family,
-   specify the <literal>FAMILY</> option in <command>CREATE OPERATOR
-   CLASS</command>.  Without this option, the new class is placed into
-   a family named the same as the new class (creating that family if
-   it doesn't already exist).
-  </para>
-
-  <para>
-   Refer to <xref linkend="xindex"> for further information.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the operator class to be created.  The name can be
-      schema-qualified.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DEFAULT</></term>
-    <listitem>
-     <para>
-      If present, the operator class will become the default
-      operator class for its data type.  At most one operator class
-      can be the default for a specific data type and index method.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">data_type</replaceable></term>
-    <listitem>
-     <para>
-      The column data type that this operator class is for.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">index_method</replaceable></term>
-    <listitem>
-     <para>
-      The name of the index method this operator class is for.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">family_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the existing operator family to add this operator class to.
-      If not specified, a family named the same as the operator class is
-      used (creating it, if it doesn't already exist).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">strategy_number</replaceable></term>
-    <listitem>
-     <para>
-      The index method's strategy number for an operator
-      associated with the operator class.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">operator_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an operator associated
-      with the operator class.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">op_type</replaceable></term>
-    <listitem>
-     <para>
-      In an <literal>OPERATOR</> clause,
-      the operand data type(s) of the operator, or <literal>NONE</> to
-      signify a left-unary or right-unary operator.  The operand data
-      types can be omitted in the normal case where they are the same
-      as the operator class's data type.
-     </para>
-
-     <para>
-      In a <literal>FUNCTION</> clause, the operand data type(s) the
-      function is intended to support, if different from
-      the input data type(s) of the function (for B-tree and hash indexes)
-      or the class's data type (for GIN and GiST indexes).  These defaults
-      are always correct, so there is no point in specifying <replaceable
-      class="parameter">op_type</replaceable> in a <literal>FUNCTION</> clause
-      in <command>CREATE OPERATOR CLASS</>, but the option is provided
-      for consistency with the comparable syntax in
-      <command>ALTER OPERATOR FAMILY</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">sort_family_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing <literal>btree</literal> operator
-      family that describes the sort ordering associated with an ordering
-      operator.
-     </para>
-
-     <para>
-      If neither <literal>FOR SEARCH</> nor <literal>FOR ORDER BY</> is
-      specified, <literal>FOR SEARCH</> is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">support_number</replaceable></term>
-    <listitem>
-     <para>
-      The index method's support procedure number for a
-      function associated with the operator class.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">function_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of a function that is an
-      index method support procedure for the operator class.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argument_type</replaceable></term>
-    <listitem>
-     <para>
-      The parameter data type(s) of the function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">storage_type</replaceable></term>
-    <listitem>
-     <para>
-      The data type actually stored in the index.  Normally this is
-      the same as the column data type, but some index methods
-      (currently GIN and GiST) allow it to be different.  The
-      <literal>STORAGE</> clause must be omitted unless the index
-      method allows a different type to be used.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   The <literal>OPERATOR</>, <literal>FUNCTION</>, and <literal>STORAGE</>
-   clauses can appear in any order.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Because the index machinery does not check access permissions on functions
-   before using them, including a function or operator in an operator class
-   is tantamount to granting public execute permission on it.  This is usually
-   not an issue for the sorts of functions that are useful in an operator
-   class.
-  </para>
-
-  <para>
-   The operators should not be defined by SQL functions.  A SQL function
-   is likely to be inlined into the calling query, which will prevent
-   the optimizer from recognizing that the query matches an index.
-  </para>
-
-  <para>
-   Before <productname>PostgreSQL</productname> 8.4, the <literal>OPERATOR</>
-   clause could include a <literal>RECHECK</> option.  This is no longer
-   supported because whether an index operator is <quote>lossy</> is now
-   determined on-the-fly at run time.  This allows efficient handling of
-   cases where an operator might or might not be lossy.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   The following example command defines a GiST index operator class
-   for the data type <literal>_int4</> (array of <type>int4</type>).  See the
-   <xref linkend="intarray"> module for the complete example.
-  </para>
-
-<programlisting>
-CREATE OPERATOR CLASS gist__int_ops
-    DEFAULT FOR TYPE _int4 USING gist AS
-        OPERATOR        3       &amp;&amp;,
-        OPERATOR        6       = (anyarray, anyarray),
-        OPERATOR        7       @&gt;,
-        OPERATOR        8       &lt;@,
-        OPERATOR        20      @@ (_int4, query_int),
-        FUNCTION        1       g_int_consistent (internal, _int4, int, oid, internal),
-        FUNCTION        2       g_int_union (internal, internal),
-        FUNCTION        3       g_int_compress (internal),
-        FUNCTION        4       g_int_decompress (internal),
-        FUNCTION        5       g_int_penalty (internal, internal, internal),
-        FUNCTION        6       g_int_picksplit (internal, internal),
-        FUNCTION        7       g_int_same (_int4, _int4, internal);
-</programlisting>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE OPERATOR CLASS</command> is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.  There is no
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.  There is no
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.  There is no
-<!## end>
-   <command>CREATE OPERATOR CLASS</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alteropclass"></member>
-   <member><xref linkend="sql-dropopclass"></member>
-   <member><xref linkend="sql-createopfamily"></member>
-   <member><xref linkend="sql-alteropfamily"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_operator.sgmlin b/doc-xc/src/sgml/ref/create_operator.sgmlin
deleted file mode 100644
index 0182130de7..0000000000
--- a/doc-xc/src/sgml/ref/create_operator.sgmlin
+++ /dev/null
@@ -1,310 +0,0 @@
-<!--
-doc/src/sgml/ref/create_operator.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEOPERATOR">
- <refmeta>
-  <refentrytitle>CREATE OPERATOR</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE OPERATOR</refname>
-  <refpurpose>define a new operator</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createoperator">
-  <primary>CREATE OPERATOR</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE OPERATOR <replaceable>name</replaceable> (
-    PROCEDURE = <replaceable class="parameter">function_name</replaceable>
-    [, LEFTARG = <replaceable class="parameter">left_type</replaceable> ] [, RIGHTARG = <replaceable class="parameter">right_type</replaceable> ]
-    [, COMMUTATOR = <replaceable class="parameter">com_op</replaceable> ] [, NEGATOR = <replaceable class="parameter">neg_op</replaceable> ]
-    [, RESTRICT = <replaceable class="parameter">res_proc</replaceable> ] [, JOIN = <replaceable class="parameter">join_proc</replaceable> ]
-    [, HASHES ] [, MERGES ]
-)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE OPERATOR</command> defines a new operator,
-   <replaceable class="parameter">name</replaceable>.  The user who
-   defines an operator becomes its owner.  If a schema name is given
-   then the operator is created in the specified schema.  Otherwise it
-   is created in the current schema.
-  </para>
-
-  <para>
-   The operator name is a sequence of up to <symbol>NAMEDATALEN</>-1
-   (63 by default) characters from the following list:
-<literallayout>
-+ - * / &lt; &gt; = ~ ! @ # % ^ &amp; | ` ?
-</literallayout>
-
-   There are a few restrictions on your choice of name:
-   <itemizedlist>
-    <listitem>
-     <para>
-     <literal>--</literal> and <literal>/*</literal> cannot appear anywhere in an operator name,
-     since they will be taken as the start of a comment.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-     A multicharacter operator name cannot end in <literal>+</literal> or
-     <literal>-</literal>,
-     unless the name also contains at least one of these characters:
-<literallayout>
-~ ! @ # % ^ &amp; | ` ?
-</literallayout>
-     For example, <literal>@-</literal> is an allowed operator name,
-     but <literal>*-</literal> is not.
-<!## PG>
-     This restriction allows <productname>PostgreSQL</productname> to
-<!## end>
-<!## XC>
-     This restriction allows <productname>Postgres-XC</productname> to
-<!## end>
-<!## XL>
-     This restriction allows <productname>Postgres-XL</productname> to
-<!## end>
-     parse SQL-compliant commands without requiring spaces between tokens.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-     The use of <literal>=&gt;</> as an operator name is deprecated.  It may
-     be disallowed altogether in a future release.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   The operator <literal>!=</literal> is mapped to
-   <literal>&lt;&gt;</literal> on input, so these two names are always
-   equivalent.
-  </para>
-
-  <para>
-   At least one of <literal>LEFTARG</> and <literal>RIGHTARG</> must be defined.  For
-   binary operators, both must be defined. For right  unary
-   operators, only <literal>LEFTARG</> should be defined, while for left
-   unary operators only <literal>RIGHTARG</> should be defined.
-  </para>
-
-  <para>
-   The <replaceable class="parameter">function_name</replaceable>
-   procedure must have been previously defined using <command>CREATE
-   FUNCTION</command> and must be defined to accept the correct number
-   of arguments (either one or two) of the indicated types.
-  </para>
-
-  <para>
-   The other clauses specify optional operator optimization clauses.
-   Their meaning is detailed in <xref linkend="xoper-optimization">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the operator to be defined. See above for allowable
-        characters.  The name can be schema-qualified, for example
-        <literal>CREATE OPERATOR myschema.+ (...)</>.  If not, then
-        the operator is created in the current schema.  Two operators
-        in the same schema can have the same name if they operate on
-        different data types.  This is called
-        <firstterm>overloading</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">function_name</replaceable></term>
-      <listitem>
-       <para>
-        The function used to implement this operator.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">left_type</replaceable></term>
-      <listitem>
-       <para>
-        The data type of the operator's left operand, if any.
-        This option would be omitted for a left-unary operator.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">right_type</replaceable></term>
-      <listitem>
-       <para>
-        The data type of the operator's right operand, if any.
-        This option would be omitted for a right-unary operator.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">com_op</replaceable></term>
-      <listitem>
-       <para>
-        The commutator of this operator.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">neg_op</replaceable></term>
-      <listitem>
-       <para>
-        The negator of this operator.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">res_proc</replaceable></term>
-      <listitem>
-       <para>
-        The restriction selectivity estimator function for this operator.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">join_proc</replaceable></term>
-      <listitem>
-       <para>
-        The join selectivity estimator function for this operator.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>HASHES</literal></term>
-      <listitem>
-       <para>
-       Indicates this operator can support a hash join.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>MERGES</literal></term>
-      <listitem>
-       <para>
-       Indicates this operator can support a merge join.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-  <para>
-   To give a schema-qualified operator name in <replaceable
-   class="parameter">com_op</replaceable> or the other optional
-   arguments, use the <literal>OPERATOR()</> syntax, for example:
-<programlisting>
-COMMUTATOR = OPERATOR(myschema.===) ,
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Refer to <xref linkend="xoper"> for further information.
-  </para>
-
-  <para>
-   It is not possible to specify an operator's lexical precedence in
-   <command>CREATE OPERATOR</>, because the parser's precedence behavior
-   is hard-wired.  See <xref linkend="sql-precedence"> for precedence details.
-  </para>
-
-  <para>
-   The obsolete options <literal>SORT1</>, <literal>SORT2</>,
-   <literal>LTCMP</>, and <literal>GTCMP</> were formerly used to
-   specify the names of sort operators associated with a merge-joinable
-   operator.  This is no longer necessary, since information about
-   associated operators is found by looking at B-tree operator families
-   instead.  If one of these options is given, it is ignored except
-   for implicitly setting <literal>MERGES</> true.
-  </para>
-
-  <para>
-   Use <xref linkend="sql-dropoperator"> to delete user-defined operators
-   from a database.  Use <xref linkend="sql-alteroperator"> to modify operators in a
-   database.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   The following command defines a new operator, area-equality, for
-   the data type <type>box</type>:
-<programlisting>
-CREATE OPERATOR === (
-    LEFTARG = box,
-    RIGHTARG = box,
-    PROCEDURE = area_equal_procedure,
-    COMMUTATOR = ===,
-    NEGATOR = !==,
-    RESTRICT = area_restriction_procedure,
-    JOIN = area_join_procedure,
-    HASHES, MERGES
-);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE OPERATOR</command> is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.  There are no
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.  There are no
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.  There are no
-<!## end>
-   provisions for user-defined operators in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alteroperator"></member>
-   <member><xref linkend="sql-createopclass"></member>
-   <member><xref linkend="sql-dropoperator"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_opfamily.sgmlin b/doc-xc/src/sgml/ref/create_opfamily.sgmlin
deleted file mode 100644
index d30e8e904c..0000000000
--- a/doc-xc/src/sgml/ref/create_opfamily.sgmlin
+++ /dev/null
@@ -1,128 +0,0 @@
-<!--
-doc/src/sgml/ref/create_opfamily.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEOPFAMILY">
- <refmeta>
-  <refentrytitle>CREATE OPERATOR FAMILY</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE OPERATOR FAMILY</refname>
-  <refpurpose>define a new operator family</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createopfamily">
-  <primary>CREATE OPERATOR FAMILY</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE OPERATOR FAMILY <replaceable class="parameter">name</replaceable> USING <replaceable class="parameter">index_method</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE OPERATOR FAMILY</command> creates a new operator family.
-   An operator family defines a collection of related operator classes,
-   and perhaps some additional operators and support functions that are
-   compatible with these operator classes but not essential for the
-   functioning of any individual index.  (Operators and functions that
-   are essential to indexes should be grouped within the relevant operator
-   class, rather than being <quote>loose</> in the operator family.
-   Typically, single-data-type operators are bound to operator classes,
-   while cross-data-type operators can be loose in an operator family
-   containing operator classes for both data types.)
-  </para>
-
-  <para>
-   The new operator family is initially empty.  It should be populated
-   by issuing subsequent <command>CREATE OPERATOR CLASS</command> commands
-   to add contained operator classes, and optionally
-   <command>ALTER OPERATOR FAMILY</command> commands to add <quote>loose</>
-   operators and their corresponding support functions.
-  </para>
-
-  <para>
-   If a schema name is given then the operator family is created in the
-   specified schema.  Otherwise it is created in the current schema.
-   Two operator families in the same schema can have the same name only if they
-   are for different index methods.
-  </para>
-
-  <para>
-   The user who defines an operator family becomes its owner.  Presently,
-   the creating user must be a superuser.  (This restriction is made because
-   an erroneous operator family definition could confuse or even crash the
-   server.)
-  </para>
-
-  <para>
-   Refer to <xref linkend="xindex"> for further information.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the operator family to be created.  The name can be
-      schema-qualified.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">index_method</replaceable></term>
-    <listitem>
-     <para>
-      The name of the index method this operator family is for.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE OPERATOR FAMILY</command> is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.  There is no
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.  There is no
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.  There is no
-<!## end>
-   <command>CREATE OPERATOR FAMILY</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alteropfamily"></member>
-   <member><xref linkend="sql-dropopfamily"></member>
-   <member><xref linkend="sql-createopclass"></member>
-   <member><xref linkend="sql-alteropclass"></member>
-   <member><xref linkend="sql-dropopclass"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_role.sgmlin b/doc-xc/src/sgml/ref/create_role.sgmlin
deleted file mode 100644
index cfab8ce2db..0000000000
--- a/doc-xc/src/sgml/ref/create_role.sgmlin
+++ /dev/null
@@ -1,529 +0,0 @@
-<!--
-doc/src/sgml/ref/create_role.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEROLE">
- <refmeta>
-  <refentrytitle>CREATE ROLE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE ROLE</refname>
-  <refpurpose>define a new database role</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createrole">
-  <primary>CREATE ROLE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE ROLE <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replaceable class="PARAMETER">option</replaceable> [ ... ] ]
-
-<phrase>where <replaceable class="PARAMETER">option</replaceable> can be:</phrase>
-
-      SUPERUSER | NOSUPERUSER
-    | CREATEDB | NOCREATEDB
-    | CREATEROLE | NOCREATEROLE
-    | CREATEUSER | NOCREATEUSER
-    | INHERIT | NOINHERIT
-    | LOGIN | NOLOGIN
-    | REPLICATION | NOREPLICATION
-    | CONNECTION LIMIT <replaceable class="PARAMETER">connlimit</replaceable>
-    | [ ENCRYPTED | UNENCRYPTED ] PASSWORD '<replaceable class="PARAMETER">password</replaceable>'
-    | VALID UNTIL '<replaceable class="PARAMETER">timestamp</replaceable>'
-    | IN ROLE <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | IN GROUP <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | ROLE <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | ADMIN <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | USER <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | SYSID <replaceable class="PARAMETER">uid</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE ROLE</command> adds a new role to a
-<!## PG>
-   <productname>PostgreSQL</productname> database cluster.  A role is
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> database cluster.  A role is
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> database cluster.  A role is
-<!## end>
-   an entity that can own database objects and have database privileges;
-   a role can be considered a <quote>user</>, a <quote>group</>, or both
-   depending on how it is used.  Refer to
-   <xref linkend="user-manag"> and <xref
-   linkend="client-authentication"> for information about managing
-   users and authentication.  You must have <literal>CREATEROLE</>
-   privilege or be a database superuser to use this command.
-  </para>
-
-  <para>
-   Note that roles are defined at the database cluster
-   level, and so are valid in all databases in the cluster.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the new role.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>SUPERUSER</literal></term>
-      <term><literal>NOSUPERUSER</literal></term>
-      <listitem>
-       <para>
-        These clauses determine whether the new role is a <quote>superuser</>,
-        who can override all access restrictions within the database.
-        Superuser status is dangerous and should be used only when really
-        needed.  You must yourself be a superuser to create a new superuser.
-        If not specified,
-        <literal>NOSUPERUSER</literal> is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CREATEDB</></term>
-      <term><literal>NOCREATEDB</></term>
-      <listitem>
-       <para>
-        These clauses define a role's ability to create databases.  If
-        <literal>CREATEDB</literal> is specified, the role being
-        defined will be allowed to create new databases. Specifying
-        <literal>NOCREATEDB</literal> will deny a role the ability to
-        create databases. If not specified,
-        <literal>NOCREATEDB</literal> is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CREATEROLE</literal></term>
-      <term><literal>NOCREATEROLE</literal></term>
-      <listitem>
-       <para>
-        These clauses determine whether a role will be permitted to
-        create new roles (that is, execute <command>CREATE ROLE</command>).
-        A role with <literal>CREATEROLE</literal> privilege can also alter
-        and drop other roles.
-        If not specified,
-        <literal>NOCREATEROLE</literal> is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CREATEUSER</literal></term>
-      <term><literal>NOCREATEUSER</literal></term>
-      <listitem>
-       <para>
-        These clauses are an obsolete, but still accepted, spelling of
-        <literal>SUPERUSER</literal> and <literal>NOSUPERUSER</literal>.
-        Note that they are <emphasis>not</> equivalent to
-        <literal>CREATEROLE</literal> as one might naively expect!
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>INHERIT</literal></term>
-      <term><literal>NOINHERIT</literal></term>
-      <listitem>
-       <para>
-        These clauses determine whether a role <quote>inherits</> the
-        privileges of roles it is a member of.
-        A role with the <literal>INHERIT</literal> attribute can automatically
-        use whatever database privileges have been granted to all roles
-        it is directly or indirectly a member of.
-        Without <literal>INHERIT</literal>, membership in another role
-        only grants the ability to <command>SET ROLE</> to that other role;
-        the privileges of the other role are only available after having
-        done so.
-        If not specified,
-        <literal>INHERIT</literal> is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>LOGIN</literal></term>
-      <term><literal>NOLOGIN</literal></term>
-      <listitem>
-       <para>
-        These clauses determine whether a role is allowed to log in;
-        that is, whether the role can be given as the initial session
-        authorization name during client connection.  A role having
-        the <literal>LOGIN</literal> attribute can be thought of as a user.
-        Roles without this attribute are useful for managing database
-        privileges, but are not users in the usual sense of the word.
-        If not specified,
-        <literal>NOLOGIN</literal> is the default, except when
-        <command>CREATE ROLE</> is invoked through its alternative spelling
-        <command>CREATE USER</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>REPLICATION</literal></term>
-      <term><literal>NOREPLICATION</literal></term>
-      <listitem>
-       <para>
-        These clauses determine whether a role is allowed to initiate
-        streaming replication or put the system in and out of backup mode.
-        A role having the <literal>REPLICATION</> attribute is a very
-        highly privileged role, and should only be used on roles actually
-        used for replication. If not specified,
-        <literal>NOREPLICATION</literal> is the default for all roles except
-        superusers.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CONNECTION LIMIT</literal> <replaceable class="parameter">connlimit</replaceable></term>
-      <listitem>
-       <para>
-        If role can log in, this specifies how many concurrent connections
-        the role can make.  -1 (the default) means no limit.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>PASSWORD</> <replaceable class="parameter">password</replaceable></term>
-      <listitem>
-       <para>
-        Sets the role's password.  (A password is only of use for
-        roles having the <literal>LOGIN</literal> attribute, but you
-        can nonetheless define one for roles without it.)  If you do
-        not plan to use password authentication you can omit this
-        option.  If no password is specified, the password will be set
-        to null and password authentication will always fail for that
-        user.  A null password can optionally be written explicitly as
-        <literal>PASSWORD NULL</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ENCRYPTED</></term>
-      <term><literal>UNENCRYPTED</></term>
-      <listitem>
-       <para>
-        These key words control whether the password is stored
-        encrypted in the system catalogs.  (If neither is specified,
-        the default behavior is determined by the configuration
-        parameter <xref linkend="guc-password-encryption">.)  If the
-        presented password string is already in MD5-encrypted format,
-        then it is stored encrypted as-is, regardless of whether
-        <literal>ENCRYPTED</> or <literal>UNENCRYPTED</> is specified
-        (since the system cannot decrypt the specified encrypted
-        password string).  This allows reloading of encrypted
-        passwords during dump/restore.
-       </para>
-
-       <para>
-        Note that older clients might lack support for the MD5
-        authentication mechanism that is needed to work with passwords
-        that are stored encrypted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>VALID UNTIL</literal> '<replaceable class="parameter">timestamp</replaceable>'</term>
-      <listitem>
-       <para>
-        The <literal>VALID UNTIL</literal> clause sets a date and
-        time after which the role's password is no longer valid.  If
-        this clause is omitted the password will be valid for all time.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>IN ROLE</> <replaceable class="parameter">role_name</replaceable></term>
-      <listitem>
-       <para>
-        The <literal>IN ROLE</literal> clause lists one or more existing
-        roles to which the new role will be immediately added as a new
-        member.  (Note that there is no option to add the new role as an
-        administrator; use a separate <command>GRANT</> command to do that.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>IN GROUP</> <replaceable class="parameter">role_name</replaceable></term>
-      <listitem>
-       <para>
-        <literal>IN GROUP</literal> is an obsolete spelling of
-        <literal>IN ROLE</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ROLE</> <replaceable class="parameter">role_name</replaceable></term>
-      <listitem>
-       <para>
-        The <literal>ROLE</literal> clause lists one or more existing
-        roles which are automatically added as members of the new role.
-        (This in effect makes the new role a <quote>group</>.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ADMIN</> <replaceable class="parameter">role_name</replaceable></term>
-      <listitem>
-       <para>
-        The <literal>ADMIN</literal> clause is like <literal>ROLE</literal>,
-        but the named roles are added to the new role <literal>WITH ADMIN
-        OPTION</>, giving them the right to grant membership in this role
-        to others.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>USER</> <replaceable class="parameter">role_name</replaceable></term>
-      <listitem>
-       <para>
-        The <literal>USER</literal> clause is an obsolete spelling of
-        the <literal>ROLE</> clause.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>SYSID</> <replaceable class="parameter">uid</replaceable></term>
-      <listitem>
-       <para>
-        The <literal>SYSID</literal> clause is ignored, but is accepted
-        for backwards compatibility.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-ALTERROLE"> to
-   change the attributes of a role, and <xref linkend="SQL-DROPROLE">
-   to remove a role.  All the attributes
-   specified by <command>CREATE ROLE</> can be modified by later
-   <command>ALTER ROLE</> commands.
-  </para>
-
-  <para>
-   The preferred way to add and remove members of roles that are being
-   used as groups is to use
-   <xref linkend="SQL-GRANT"> and
-   <xref linkend="SQL-REVOKE">.
-  </para>
-
-  <para>
-   The <literal>VALID UNTIL</> clause defines an expiration time for a
-   password only, not for the role <foreignphrase>per se</>.  In
-   particular, the expiration time is not enforced when logging in using
-   a non-password-based authentication method.
-  </para>
-
-  <para>
-   The <literal>INHERIT</> attribute governs inheritance of grantable
-   privileges (that is, access privileges for database objects and role
-   memberships).  It does not apply to the special role attributes set by
-   <command>CREATE ROLE</> and <command>ALTER ROLE</>.  For example, being
-   a member of a role with <literal>CREATEDB</> privilege does not immediately
-   grant the ability to create databases, even if <literal>INHERIT</> is set;
-   it would be necessary to become that role via
-   <xref linkend="SQL-SET-ROLE"> before
-   creating a database.
-  </para>
-
-  <para>
-   The <literal>INHERIT</> attribute is the default for reasons of backwards
-<!## PG>
-   compatibility: in prior releases of <productname>PostgreSQL</productname>,
-<!## end>
-<!## XC>
-   compatibility: in prior releases of <productname>Postgres-XC</productname>,
-<!## end>
-<!## XL>
-   compatibility: in prior releases of <productname>Postgres-XL</productname>,
-<!## end>
-   users always had access to all privileges of groups they were members of.
-   However, <literal>NOINHERIT</> provides a closer match to the semantics
-   specified in the SQL standard.
-  </para>
-
-  <para>
-   Be careful with the <literal>CREATEROLE</> privilege. There is no concept of
-   inheritance for the privileges of a <literal>CREATEROLE</>-role. That
-   means that even if a role does not have a certain privilege but is allowed
-   to create other roles, it can easily create another role with different
-   privileges than its own (except for creating roles with superuser
-   privileges). For example, if the role <quote>user</> has the
-   <literal>CREATEROLE</> privilege but not the <literal>CREATEDB</> privilege,
-   nonetheless it can create a new role with the <literal>CREATEDB</>
-   privilege. Therefore, regard roles that have the <literal>CREATEROLE</>
-   privilege as almost-superuser-roles.
-  </para>
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> includes a program <xref
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> includes a program <xref
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> includes a program <xref
-<!## end>
-   linkend="APP-CREATEUSER"> that has
-   the same functionality as <command>CREATE ROLE</command> (in fact,
-   it calls this command) but can be run from the command shell.
-  </para>
-
-  <para>
-   The <literal>CONNECTION LIMIT</> option is only enforced approximately;
-   if two new sessions start at about the same time when just one
-   connection <quote>slot</> remains for the role, it is possible that
-   both will fail.  Also, the limit is never enforced for superusers.
-  </para>
-
-  <para>
-   Caution must be exercised when specifying an unencrypted password
-   with this command.  The password will be transmitted to the server
-   in cleartext, and it might also be logged in the client's command
-   history or the server log.  The command <xref
-   linkend="APP-CREATEUSER">, however, transmits
-   the password encrypted.  Also, <xref linkend="app-psql">
-   contains a command
-   <command>\password</command> that can be used to safely change the
-   password later.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a role that can log in, but don't give it a password:
-<programlisting>
-CREATE ROLE jonathan LOGIN;
-</programlisting>
-  </para>
-
-  <para>
-   Create a role with a password:
-<programlisting>
-CREATE USER davide WITH PASSWORD 'jw8s0F4';
-</programlisting>
-   (<command>CREATE USER</> is the same as <command>CREATE ROLE</> except
-   that it implies <literal>LOGIN</>.)
-  </para>
-
-  <para>
-   Create a role with a password that is valid until the end of 2004.
-   After one second has ticked in 2005, the password is no longer
-   valid.
-
-<programlisting>
-CREATE ROLE miriam WITH LOGIN PASSWORD 'jw8s0F4' VALID UNTIL '2005-01-01';
-</programlisting>
-  </para>
-
-  <para>
-   Create a role that can create databases and manage roles:
-<programlisting>
-CREATE ROLE admin WITH CREATEDB CREATEROLE;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The <command>CREATE ROLE</command> statement is in the SQL standard,
-   but the standard only requires the syntax
-<synopsis>
-CREATE ROLE <replaceable class="PARAMETER">name</> [ WITH ADMIN <replaceable class="PARAMETER">role_name</> ]
-</synopsis>
-   Multiple initial administrators, and all the other options of
-   <command>CREATE ROLE</command>, are
-<!## PG>
-   <productname>PostgreSQL</productname> extensions.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extensions.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extensions.
-<!## end>
-  </para>
-
-  <para>
-   The SQL standard defines the concepts of users and roles, but it
-   regards them as distinct concepts and leaves all commands defining
-   users to be specified by each database implementation.  In
-<!## PG>
-   <productname>PostgreSQL</productname> we have chosen to unify
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> we have chosen to unify
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> we have chosen to unify
-<!## end>
-   users and roles into a single kind of entity.  Roles therefore
-   have many more optional attributes than they do in the standard.
-  </para>
-
-  <para>
-   The behavior specified by the SQL standard is most closely approximated
-   by giving users the <literal>NOINHERIT</> attribute, while roles are
-   given the <literal>INHERIT</> attribute.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-set-role"></member>
-   <member><xref linkend="sql-alterrole"></member>
-   <member><xref linkend="sql-droprole"></member>
-   <member><xref linkend="sql-grant"></member>
-   <member><xref linkend="sql-revoke"></member>
-   <member><xref linkend="app-createuser"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_rule.sgmlin b/doc-xc/src/sgml/ref/create_rule.sgmlin
deleted file mode 100644
index 5100e71ae0..0000000000
--- a/doc-xc/src/sgml/ref/create_rule.sgmlin
+++ /dev/null
@@ -1,310 +0,0 @@
-<!--
-doc/src/sgml/ref/create_rule.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATERULE">
- <refmeta>
-  <refentrytitle>CREATE RULE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE RULE</refname>
-  <refpurpose>define a new rewrite rule</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createrule">
-  <primary>CREATE RULE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE [ OR REPLACE ] RULE <replaceable class="parameter">name</replaceable> AS ON <replaceable class="parameter">event</replaceable>
-    TO <replaceable class="parameter">table</replaceable> [ WHERE <replaceable class="parameter">condition</replaceable> ]
-    DO [ ALSO | INSTEAD ] { NOTHING | <replaceable class="parameter">command</replaceable> | ( <replaceable class="parameter">command</replaceable> ; <replaceable class="parameter">command</replaceable> ... ) }
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE RULE</command> defines a new rule applying to a specified
-   table or view.
-   <command>CREATE OR REPLACE RULE</command> will either create a
-   new rule, or replace an existing rule of the same name for the same
-   table.
-  </para>
-
-  <para>
-<!## PG>
-   The <productname>PostgreSQL</productname> rule system allows one to
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> inherits the rule system from <productname>PostgreSQL</productname> which allows one to
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> inherits the rule system from <productname>PostgreSQL</productname> which allows one to
-<!## end>
-   define an alternative action to be performed on insertions, updates,
-   or deletions in database tables.  Roughly speaking, a rule causes
-   additional commands to be executed when a given command on a given
-   table is executed.  Alternatively, an <literal>INSTEAD</literal>
-   rule can replace a given command by another, or cause a command
-   not to be executed at all.  Rules are used to implement table
-   views as well.  It is important to realize that a rule is really
-   a command transformation mechanism, or command macro.  The
-   transformation happens before the execution of the commands starts.
-   If you actually want an operation that fires independently for each
-   physical row, you probably want to use a trigger, not a rule.
-   More information about the rules system is in <xref linkend="rules">.
-  </para>
-
-  <para>
-   Presently, <literal>ON SELECT</literal> rules must be unconditional
-   <literal>INSTEAD</literal> rules and must have actions that consist
-   of a single <command>SELECT</command> command.  Thus, an
-   <literal>ON SELECT</literal> rule effectively turns the table into
-   a view, whose visible contents are the rows returned by the rule's
-   <command>SELECT</command> command rather than whatever had been
-   stored in the table (if anything).  It is considered better style
-   to write a <command>CREATE VIEW</command> command than to create a
-   real table and define an <literal>ON SELECT</literal> rule for it.
-  </para>
-
-  <para>
-   You can create the illusion of an updatable view by defining
-   <literal>ON INSERT</literal>, <literal>ON UPDATE</literal>, and
-   <literal>ON DELETE</literal> rules (or any subset of those that's
-   sufficient for your purposes) to replace update actions on the view
-   with appropriate updates on other tables.  If you want to support
-   <command>INSERT RETURNING</> and so on, then be sure to put a suitable
-   <literal>RETURNING</> clause into each of these rules.  Alternatively,
-   an updatable view can be implemented using <literal>INSTEAD OF</>
-   triggers (see <xref linkend="sql-createtrigger">).
-  </para>
-
-  <para>
-   There is a catch if you try to use conditional rules for view
-   updates: there <emphasis>must</> be an unconditional
-   <literal>INSTEAD</literal> rule for each action you wish to allow
-   on the view.  If the rule is conditional, or is not
-   <literal>INSTEAD</literal>, then the system will still reject
-   attempts to perform the update action, because it thinks it might
-   end up trying to perform the action on the dummy table of the view
-   in some cases.  If you want to handle all the useful cases in
-   conditional rules, add an unconditional <literal>DO
-   INSTEAD NOTHING</literal> rule to ensure that the system
-   understands it will never be called on to update the dummy table.
-   Then make the conditional rules non-<literal>INSTEAD</literal>; in
-   the cases where they are applied, they add to the default
-   <literal>INSTEAD NOTHING</literal> action.  (This method does not
-   currently work to support <literal>RETURNING</> queries, however.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of a rule to create.  This must be distinct from the
-      name of any other rule for the same table.  Multiple rules on
-      the same table and same event type are applied in alphabetical
-      name order.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">event</replaceable></term>
-    <listitem>
-     <para>
-      The event is one of <literal>SELECT</literal>,
-      <literal>INSERT</literal>, <literal>UPDATE</literal>, or
-      <literal>DELETE</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">table</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the table or view the
-      rule applies to.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">condition</replaceable></term>
-    <listitem>
-     <para>
-      Any <acronym>SQL</acronym> conditional expression (returning
-      <type>boolean</type>).  The condition expression cannot refer
-      to any tables except <literal>NEW</> and <literal>OLD</>, and
-      cannot contain aggregate functions.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>INSTEAD</option></term>
-    <listitem>
-     <para>
-      <literal>INSTEAD</literal> indicates that the commands should be
-      executed <emphasis>instead of</> the original command.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>ALSO</option></term>
-    <listitem>
-     <para>
-      <literal>ALSO</literal> indicates that the commands should be
-      executed <emphasis>in addition to</emphasis> the original
-      command.
-     </para>
-
-     <para>
-      If neither <literal>ALSO</literal> nor
-      <literal>INSTEAD</literal> is specified, <literal>ALSO</literal>
-      is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">command</replaceable></term>
-    <listitem>
-     <para>
-      The command or commands that make up the rule action.  Valid
-      commands are <command>SELECT</command>,
-      <command>INSERT</command>, <command>UPDATE</command>,
-      <command>DELETE</command>, or <command>NOTIFY</command>.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   Within <replaceable class="parameter">condition</replaceable> and
-   <replaceable class="parameter">command</replaceable>, the special
-   table names <literal>NEW</literal> and <literal>OLD</literal> can
-   be used to refer to values in the referenced table.
-   <literal>NEW</literal> is valid in <literal>ON INSERT</literal> and
-   <literal>ON UPDATE</literal> rules to refer to the new row being
-   inserted or updated.  <literal>OLD</literal> is valid in
-   <literal>ON UPDATE</literal> and <literal>ON DELETE</literal> rules
-   to refer to the existing row being updated or deleted.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   You must be the owner of a table to create or change rules for it.
-  </para>
-
-  <para>
-   In a rule for <literal>INSERT</literal>, <literal>UPDATE</literal>, or
-   <literal>DELETE</literal> on a view, you can add a <literal>RETURNING</>
-   clause that emits the view's columns.  This clause will be used to compute
-   the outputs if the rule is triggered by an <command>INSERT RETURNING</>,
-   <command>UPDATE RETURNING</>, or <command>DELETE RETURNING</> command
-   respectively.  When the rule is triggered by a command without
-   <literal>RETURNING</>, the rule's <literal>RETURNING</> clause will be
-   ignored.  The current implementation allows only unconditional
-   <literal>INSTEAD</> rules to contain <literal>RETURNING</>; furthermore
-   there can be at most one <literal>RETURNING</> clause among all the rules
-   for the same event.  (This ensures that there is only one candidate
-   <literal>RETURNING</> clause to be used to compute the results.)
-   <literal>RETURNING</> queries on the view will be rejected if
-   there is no <literal>RETURNING</> clause in any available rule.
-  </para>
-
-  <para>
-   It is very important to take care to avoid circular rules.  For
-   example, though each of the following two rule definitions are
-<!## PG>
-   accepted by <productname>PostgreSQL</productname>, the
-<!## end>
-<!## XC>
-   accepted by <productname>Postgres-XC</productname>, the
-<!## end>
-<!## XL>
-   accepted by <productname>Postgres-XL</productname>, the
-<!## end>
-   <command>SELECT</command> command would cause
-<!## PG>
-   <productname>PostgreSQL</productname> to report an error because
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> to report an error because
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> to report an error because
-<!## end>
-   of recursive expansion of a rule:
-
-<programlisting>
-CREATE RULE "_RETURN" AS
-    ON SELECT TO t1
-    DO INSTEAD
-        SELECT * FROM t2;
-
-CREATE RULE "_RETURN" AS
-    ON SELECT TO t2
-    DO INSTEAD
-        SELECT * FROM t1;
-
-SELECT * FROM t1;
-</programlisting>
-  </para>
-
-  <para>
-   Presently, if a rule action contains a <command>NOTIFY</command>
-   command, the <command>NOTIFY</command> command will be executed
-   unconditionally, that is, the <command>NOTIFY</command> will be
-   issued even if there are not any rows that the rule should apply
-   to.  For example, in:
-<programlisting>
-CREATE RULE notify_me AS ON UPDATE TO mytable DO ALSO NOTIFY mytable;
-
-UPDATE mytable SET name = 'foo' WHERE id = 42;
-</programlisting>
-   one <command>NOTIFY</command> event will be sent during the
-   <command>UPDATE</command>, whether or not there are any rows that
-   match the condition <literal>id = 42</literal>.  This is an
-   implementation restriction that might be fixed in future releases.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE RULE</command> is a
-<!## PG>
-   <productname>PostgreSQL</productname> language extension, as is the
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> language extension, as is the
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> language extension, as is the
-<!## end>
-   entire query rewrite system.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_schema.sgmlin b/doc-xc/src/sgml/ref/create_schema.sgmlin
deleted file mode 100644
index 356f19e404..0000000000
--- a/doc-xc/src/sgml/ref/create_schema.sgmlin
+++ /dev/null
@@ -1,218 +0,0 @@
-<!--
-doc/src/sgml/ref/create_schema.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATESCHEMA">
- <refmeta>
-  <refentrytitle>CREATE SCHEMA</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE SCHEMA</refname>
-  <refpurpose>define a new schema</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createschema">
-  <primary>CREATE SCHEMA</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE SCHEMA <replaceable class="parameter">schema_name</replaceable> [ AUTHORIZATION <replaceable class="parameter">user_name</replaceable> ] [ <replaceable class="parameter">schema_element</replaceable> [ ... ] ]
-CREATE SCHEMA AUTHORIZATION <replaceable class="parameter">user_name</replaceable> [ <replaceable class="parameter">schema_element</replaceable> [ ... ] ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE SCHEMA</command> enters a new schema
-   into the current database.
-   The schema name must be distinct from the name of any existing schema
-   in the current database.
-  </para>
-
-  <para>
-   A schema is essentially a namespace:
-   it contains named objects (tables, data types, functions, and operators)
-   whose names can duplicate those of other objects existing in other
-   schemas.  Named objects are accessed either by <quote>qualifying</>
-   their names with the schema name as a prefix, or by setting a search
-   path that includes the desired schema(s).  A <literal>CREATE</> command
-   specifying an unqualified object name creates the object
-   in the current schema (the one at the front of the search path,
-   which can be determined with the function <function>current_schema</function>).
-  </para>
-
-  <para>
-   Optionally, <command>CREATE SCHEMA</command> can include subcommands
-   to create objects within the new schema.  The subcommands are treated
-   essentially the same as separate commands issued after creating the
-   schema, except that if the <literal>AUTHORIZATION</> clause is used,
-   all the created objects will be owned by that user.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">schema_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of a schema to be created.  If this is omitted, the user name
-        is used as the schema name.  The name cannot
-        begin with <literal>pg_</literal>, as such names
-        are reserved for system schemas.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">user_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the user who will own the schema.  If omitted,
-        defaults to the user executing the command.  Only superusers
-        can create schemas owned by users other than themselves.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">schema_element</replaceable></term>
-      <listitem>
-       <para>
-        An SQL statement defining an object to be created within the
-        schema. Currently, only <command>CREATE
-        TABLE</>, <command>CREATE VIEW</>, <command>CREATE
-        INDEX</>, <command>CREATE SEQUENCE</>, <command>CREATE
-        TRIGGER</> and <command>GRANT</> are accepted as clauses
-        within <command>CREATE SCHEMA</>. Other kinds of objects may
-        be created in separate commands after the schema is created.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   To create a schema, the invoking user must have the
-   <literal>CREATE</> privilege for the current database.
-   (Of course, superusers bypass this check.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a schema:
-<programlisting>
-CREATE SCHEMA myschema;
-</programlisting>
-  </para>
-
-  <para>
-   Create a schema for user <literal>joe</>; the schema will also be
-   named <literal>joe</>:
-<programlisting>
-CREATE SCHEMA AUTHORIZATION joe;
-</programlisting>
-  </para>
-
-  <para>
-   Create a schema and create a table and view within it:
-<programlisting>
-CREATE SCHEMA hollywood
-    CREATE TABLE films (title text, release date, awards text[])
-    CREATE VIEW winners AS
-        SELECT title, release FROM films WHERE awards IS NOT NULL;
-</programlisting>
-   Notice that the individual subcommands do not end with semicolons.
-  </para>
-
-  <para>
-   The following is an equivalent way of accomplishing the same result:
-<programlisting>
-CREATE SCHEMA hollywood;
-CREATE TABLE hollywood.films (title text, release date, awards text[]);
-CREATE VIEW hollywood.winners AS
-    SELECT title, release FROM hollywood.films WHERE awards IS NOT NULL;
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard allows a <literal>DEFAULT CHARACTER SET</> clause
-   in <command>CREATE SCHEMA</command>, as well as more subcommand
-   types than are presently accepted by
-<!## PG>
-   <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>.
-<!## end>
-  </para>
-
-  <para>
-   The SQL standard specifies that the subcommands in <command>CREATE
-   SCHEMA</command> can appear in any order.  The present
-<!## PG>
-   <productname>PostgreSQL</productname> implementation does not
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> implementation, inherited from <productname>PostgreSQL</>, does not
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> implementation, inherited from <productname>PostgreSQL</>, does not
-<!## end>
-   handle all cases of forward references in subcommands; it might
-   sometimes be necessary to reorder the subcommands in order to avoid
-   forward references.
-  </para>
-
-  <para>
-   According to the SQL standard, the owner of a schema always owns
-<!## PG>
-   all objects within it.  <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   all objects within it.  <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   all objects within it.  <productname>Postgres-XL</productname>
-<!## end>
-   allows schemas to contain objects owned by users other than the
-   schema owner.  This can happen only if the schema owner grants the
-   <literal>CREATE</> privilege on his schema to someone else.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterschema"></member>
-   <member><xref linkend="sql-dropschema"></member>
- </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_sequence.sgmlin b/doc-xc/src/sgml/ref/create_sequence.sgmlin
deleted file mode 100644
index 458e86d256..0000000000
--- a/doc-xc/src/sgml/ref/create_sequence.sgmlin
+++ /dev/null
@@ -1,366 +0,0 @@
-<!--
-doc/src/sgml/ref/create_sequence.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATESEQUENCE">
- <refmeta>
-  <refentrytitle>CREATE SEQUENCE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE SEQUENCE</refname>
-  <refpurpose>define a new sequence generator</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createsequence">
-  <primary>CREATE SEQUENCE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE [ TEMPORARY | TEMP ] SEQUENCE <replaceable class="parameter">name</replaceable> [ INCREMENT [ BY ] <replaceable class="parameter">increment</replaceable> ]
-    [ MINVALUE <replaceable class="parameter">minvalue</replaceable> | NO MINVALUE ] [ MAXVALUE <replaceable class="parameter">maxvalue</replaceable> | NO MAXVALUE ]
-    [ START [ WITH ] <replaceable class="parameter">start</replaceable> ] [ CACHE <replaceable class="parameter">cache</replaceable> ] [ [ NO ] CYCLE ]
-    [ OWNED BY { <replaceable class="parameter">table</replaceable>.<replaceable class="parameter">column</replaceable> | NONE } ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>CREATE SEQUENCE</command> creates a new sequence number
-   generator.  This involves creating and initializing a new special
-   single-row table with the name <replaceable
-   class="parameter">name</replaceable>.  The generator will be
-   owned by the user issuing the command.
-  </para>
-
-  <para>
-   If a schema name is given then the sequence is created in the
-   specified schema.  Otherwise it is created in the current schema.
-   Temporary sequences exist in a special schema, so a schema name cannot be
-   given when creating a temporary sequence.
-   The sequence name must be distinct from the name of any other sequence,
-   table, index, view, or foreign table in the same schema.
-  </para>
-
-  <para>
-   After a sequence is created, you use the functions
-   <function>nextval</function>,
-   <function>currval</function>, and
-   <function>setval</function>
-   to operate on the sequence.  These functions are documented in
-   <xref linkend="functions-sequence">.
-  </para>
-
-  <para>
-   Although you cannot update a sequence directly, you can use a query like:
-
-<programlisting>
-SELECT * FROM <replaceable>name</replaceable>;
-</programlisting>
-
-   to examine the parameters and current state of a sequence.  In particular,
-   the <literal>last_value</> field of the sequence shows the last value
-   allocated by any session.  (Of course, this value might be obsolete
-   by the time it's printed, if other sessions are actively doing
-   <function>nextval</> calls.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>TEMPORARY</literal> or <literal>TEMP</literal></term>
-    <listitem>
-     <para>
-      If specified, the sequence object is created only for this
-      session, and is automatically dropped on session exit.  Existing
-      permanent sequences with the same name are not visible (in this
-      session) while the temporary sequence exists, unless they are
-      referenced with schema-qualified names.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the sequence to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">increment</replaceable></term>
-    <listitem>
-     <para>
-      The optional clause <literal>INCREMENT BY <replaceable
-      class="parameter">increment</replaceable></literal> specifies
-      which value is added to the current sequence value to create a
-      new value.  A positive value will make an ascending sequence, a
-      negative one a descending sequence.  The default value is 1.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">minvalue</replaceable></term>
-    <term><literal>NO MINVALUE</literal></term>
-    <listitem>
-     <para>
-      The optional clause <literal>MINVALUE <replaceable
-      class="parameter">minvalue</replaceable></literal> determines
-      the minimum value a sequence can generate. If this clause is not
-      supplied or <option>NO MINVALUE</option> is specified, then
-      defaults will be used.  The defaults are 1 and
-      -2<superscript>63</>-1 for ascending and descending sequences,
-      respectively.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">maxvalue</replaceable></term>
-    <term><literal>NO MAXVALUE</literal></term>
-    <listitem>
-     <para>
-      The optional clause <literal>MAXVALUE <replaceable
-      class="parameter">maxvalue</replaceable></literal> determines
-      the maximum value for the sequence. If this clause is not
-      supplied or <option>NO MAXVALUE</option> is specified, then
-      default values will be used.  The defaults are
-      2<superscript>63</>-1 and -1 for ascending and descending
-      sequences, respectively.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">start</replaceable></term>
-    <listitem>
-     <para>
-      The optional clause <literal>START WITH <replaceable
-      class="parameter">start</replaceable> </literal> allows the
-      sequence to begin anywhere.  The default starting value is
-      <replaceable class="parameter">minvalue</replaceable> for
-      ascending sequences and <replaceable
-      class="parameter">maxvalue</replaceable> for descending ones.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">cache</replaceable></term>
-    <listitem>
-     <para>
-      The optional clause <literal>CACHE <replaceable
-      class="parameter">cache</replaceable></literal> specifies how
-      many sequence numbers are to be preallocated and stored in
-      memory for faster access. The minimum value is 1 (only one value
-      can be generated at a time, i.e., no cache), and this is also the
-      default.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CYCLE</literal></term>
-    <term><literal>NO CYCLE</literal></term>
-    <listitem>
-     <para>
-      The <literal>CYCLE</literal> option allows the sequence to wrap
-      around when the <replaceable
-      class="parameter">maxvalue</replaceable> or <replaceable
-      class="parameter">minvalue</replaceable> has been reached by an
-      ascending or descending sequence respectively. If the limit is
-      reached, the next number generated will be the <replaceable
-      class="parameter">minvalue</replaceable> or <replaceable
-      class="parameter">maxvalue</replaceable>, respectively.
-     </para>
-
-     <para>
-      If <literal>NO CYCLE</literal> is specified, any calls to
-      <function>nextval</function> after the sequence has reached its
-      maximum value will return an error.  If neither
-      <literal>CYCLE</literal> or <literal>NO CYCLE</literal> are
-      specified, <literal>NO CYCLE</literal> is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OWNED BY</literal> <replaceable class="parameter">table</replaceable>.<replaceable class="parameter">column</replaceable></term>
-    <term><literal>OWNED BY NONE</literal></term>
-    <listitem>
-     <para>
-      The <literal>OWNED BY</literal> option causes the sequence to be
-      associated with a specific table column, such that if that column
-      (or its whole table) is dropped, the sequence will be automatically
-      dropped as well.  The specified table must have the same owner and be in
-      the same schema as the sequence.
-      <literal>OWNED BY NONE</literal>, the default, specifies that there
-      is no such association.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <command>DROP SEQUENCE</command> to remove a sequence.
-  </para>
-
-  <para>
-   Sequences are based on <type>bigint</> arithmetic, so the range
-   cannot exceed the range of an eight-byte integer
-   (-9223372036854775808 to 9223372036854775807).  On some older
-   platforms, there might be no compiler support for eight-byte
-   integers, in which case sequences use regular <type>integer</>
-   arithmetic (range -2147483648 to +2147483647).
-  </para>
-
-  <para>
-   Unexpected results might be obtained if a <replaceable
-   class="parameter">cache</replaceable> setting greater than one is
-   used for a sequence object that will be used concurrently by
-   multiple sessions.  Each session will allocate and cache successive
-   sequence values during one access to the sequence object and
-   increase the sequence object's <literal>last_value</> accordingly.
-   Then, the next <replaceable class="parameter">cache</replaceable>-1
-   uses of <function>nextval</> within that session simply return the
-   preallocated values without touching the sequence object.  So, any
-   numbers allocated but not used within a session will be lost when
-   that session ends, resulting in <quote>holes</quote> in the
-   sequence.
-  </para>
-
-  <para>
-   Furthermore, although multiple sessions are guaranteed to allocate
-   distinct sequence values, the values might be generated out of
-   sequence when all the sessions are considered.  For example, with
-   a <replaceable class="parameter">cache</replaceable> setting of 10,
-   session A might reserve values 1..10 and return
-   <function>nextval</function>=1, then session B might reserve values
-   11..20 and return <function>nextval</function>=11 before session A
-   has generated <literal>nextval</literal>=2.  Thus, with a
-   <replaceable class="parameter">cache</replaceable> setting of one
-   it is safe to assume that <function>nextval</> values are generated
-   sequentially; with a <replaceable
-   class="parameter">cache</replaceable> setting greater than one you
-   should only assume that the <function>nextval</> values are all
-   distinct, not that they are generated purely sequentially.  Also,
-   <literal>last_value</> will reflect the latest value reserved by
-   any session, whether or not it has yet been returned by
-   <function>nextval</>.
-  </para>
-
-  <para>
-   Another consideration is that a <function>setval</> executed on
-   such a sequence will not be noticed by other sessions until they
-   have used up any preallocated values they have cached.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create an ascending sequence called <literal>serial</literal>, starting at 101:
-<programlisting>
-CREATE SEQUENCE serial START 101;
-</programlisting>
-  </para>
-
-  <para>
-   Select the next number from this sequence:
-<programlisting>
-SELECT nextval('serial');
-
- nextval
----------
-     101
-</programlisting>
-  </para>
-
-  <para>
-   Select the next number from this sequence:
-<programlisting>
-SELECT nextval('serial');
-
- nextval
----------
-     102
-</programlisting>
-  </para>
-
-  <para>
-   Use this sequence in an <command>INSERT</command> command:
-<programlisting>
-INSERT INTO distributors VALUES (nextval('serial'), 'nothing');
-</programlisting>
-  </para>
-
-  <para>
-   Update the sequence value after a <command>COPY FROM</command>:
-<programlisting>
-BEGIN;
-COPY distributors FROM 'input_file';
-SELECT setval('serial', max(id)) FROM distributors;
-END;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE SEQUENCE</command> conforms to the <acronym>SQL</acronym>
-   standard, with the following exceptions:
-   <itemizedlist>
-    <listitem>
-     <para>
-      The standard's <literal>AS &lt;data type&gt;</literal> expression is not
-      supported.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Obtaining the next value is done using the <function>nextval()</>
-      function instead of the standard's <command>NEXT VALUE FOR</command>
-      expression.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      The <literal>OWNED BY</> clause is a <productname>PostgreSQL</>
-      extension.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altersequence"></member>
-   <member><xref linkend="sql-dropsequence"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_server.sgmlin b/doc-xc/src/sgml/ref/create_server.sgmlin
deleted file mode 100644
index 71e2aac86d..0000000000
--- a/doc-xc/src/sgml/ref/create_server.sgmlin
+++ /dev/null
@@ -1,182 +0,0 @@
-<!--
-doc/src/sgml/ref/create_server.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATESERVER">
- <refmeta>
-  <refentrytitle>CREATE SERVER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE SERVER</refname>
-  <refpurpose>define a new foreign server</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createserver">
-  <primary>CREATE SERVER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE SERVER <replaceable class="parameter">server_name</replaceable> [ TYPE '<replaceable class="parameter">server_type</replaceable>' ] [ VERSION '<replaceable class="parameter">server_version</replaceable>' ]
-    FOREIGN DATA WRAPPER <replaceable class="parameter">fdw_name</replaceable>
-    [ OPTIONS ( <replaceable class="PARAMETER">option</replaceable> '<replaceable class="PARAMETER">value</replaceable>' [, ... ] ) ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-<!## XC>
-&xconly;
-  <para>
-   <command>SERVER</> has not been supported
-   by <productname>Postgres-XC</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>SERVER</> is not yet supported
-   in <productname>Postgres-XL</>.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-&pgonly;
-
-  <para>
-   <command>CREATE SERVER</command> defines a new foreign server.  The
-   user who defines the server becomes its owner.
-  </para>
-
-  <para>
-   A foreign server typically encapsulates connection information that
-   a foreign-data wrapper uses to access an external data resource.
-   Additional user-specific connection information may be specified by
-   means of user mappings.
-  </para>
-
-  <para>
-   The server name must be unique within the database.
-  </para>
-
-  <para>
-   Creating a server requires <literal>USAGE</> privilege on the
-   foreign-data wrapper being used.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">server_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the foreign server to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">server_type</replaceable></term>
-    <listitem>
-     <para>
-      Optional server type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">server_version</replaceable></term>
-    <listitem>
-     <para>
-      Optional server version.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">fdw_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the foreign-data wrapper that manages the server.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OPTIONS ( <replaceable class="PARAMETER">option</replaceable> '<replaceable class="PARAMETER">value</replaceable>' [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      This clause specifies the options for the server.  The options
-      typically define the connection details of the server, but the
-      actual names and values are dependent on the server's
-      foreign-data wrapper.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   When using the <application>dblink</application> module
-   (see <xref linkend="dblink">), the foreign server name can be used
-   as an argument of the <xref linkend="contrib-dblink-connect">
-   function to indicate the connection parameters.  See also there for
-   more examples.  It is necessary to have
-   the <literal>USAGE</literal> privilege on the foreign server to be
-   able to use it in this way.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a server <literal>foo</> that uses the built-in foreign-data
-   wrapper <literal>default</>:
-<programlisting>
-CREATE SERVER foo FOREIGN DATA WRAPPER "default";
-</programlisting>
-  </para>
-
-  <para>
-   Create a server <literal>myserver</> that uses the
-   foreign-data wrapper <literal>pgsql</>:
-<programlisting>
-CREATE SERVER myserver FOREIGN DATA WRAPPER pgsql OPTIONS (host 'foo', dbname 'foodb', port '5432');
-</programlisting>
-  </para>
-
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE SERVER</command> conforms to ISO/IEC 9075-9 (SQL/MED).
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterserver"></member>
-   <member><xref linkend="sql-dropserver"></member>
-   <member><xref linkend="sql-createforeigndatawrapper"></member>
-   <member><xref linkend="sql-createusermapping"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_table.sgmlin b/doc-xc/src/sgml/ref/create_table.sgmlin
deleted file mode 100644
index 6ac0dd5793..0000000000
--- a/doc-xc/src/sgml/ref/create_table.sgmlin
+++ /dev/null
@@ -1,2117 +0,0 @@
-<!--
-doc/src/sgml/ref/create_table.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETABLE">
- <refmeta>
-  <refentrytitle>CREATE TABLE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TABLE</refname>
-  <refpurpose>define a new table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createtable">
-  <primary>CREATE TABLE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<!## PG>
-<synopsis>
-CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] <replaceable class="PARAMETER">table_name</replaceable> ( [
-  { <replaceable class="PARAMETER">column_name</replaceable> <replaceable class="PARAMETER">data_type</replaceable> [ COLLATE <replaceable>collation</replaceable> ] [ <replaceable class="PARAMETER">column_constraint</replaceable> [ ... ] ]
-    | <replaceable>table_constraint</replaceable>
-    | LIKE <replaceable>parent_table</replaceable> [ <replaceable>like_option</replaceable> ... ] }
-    [, ... ]
-] )
-[ INHERITS ( <replaceable>parent_table</replaceable> [, ... ] ) ]
-[ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
-[ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
-[ TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-
-CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] <replaceable class="PARAMETER">table_name</replaceable>
-    OF <replaceable class="PARAMETER">type_name</replaceable> [ (
-  { <replaceable class="PARAMETER">column_name</replaceable> WITH OPTIONS [ <replaceable class="PARAMETER">column_constraint</replaceable> [ ... ] ]
-    | <replaceable>table_constraint</replaceable> }
-    [, ... ]
-) ]
-[ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
-[ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
-[ TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-
-<phrase>where <replaceable class="PARAMETER">column_constraint</replaceable> is:</phrase>
-
-[ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-{ NOT NULL |
-  NULL |
-  CHECK ( <replaceable class="PARAMETER">expression</replaceable> ) |
-  DEFAULT <replaceable>default_expr</replaceable> |
-  UNIQUE <replaceable class="PARAMETER">index_parameters</replaceable> |
-  PRIMARY KEY <replaceable class="PARAMETER">index_parameters</replaceable> |
-  REFERENCES <replaceable class="PARAMETER">reftable</replaceable> [ ( <replaceable class="PARAMETER">refcolumn</replaceable> ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
-    [ ON DELETE <replaceable class="parameter">action</replaceable> ] [ ON UPDATE <replaceable class="parameter">action</replaceable> ] }
-[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
-
-<phrase>and <replaceable class="PARAMETER">table_constraint</replaceable> is:</phrase>
-
-[ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-{ CHECK ( <replaceable class="PARAMETER">expression</replaceable> ) |
-  UNIQUE ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) <replaceable class="PARAMETER">index_parameters</replaceable> |
-  PRIMARY KEY ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) <replaceable class="PARAMETER">index_parameters</replaceable> |
-  EXCLUDE [ USING <replaceable class="parameter">index_method</replaceable> ] ( <replaceable class="parameter">exclude_element</replaceable> WITH <replaceable class="parameter">operator</replaceable> [, ... ] ) <replaceable class="parameter">index_parameters</replaceable> [ WHERE ( <replaceable class="parameter">predicate</replaceable> ) ] |
-  FOREIGN KEY ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) REFERENCES <replaceable class="PARAMETER">reftable</replaceable> [ ( <replaceable class="PARAMETER">refcolumn</replaceable> [, ... ] ) ]
-    [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE <replaceable class="parameter">action</replaceable> ] [ ON UPDATE <replaceable class="parameter">action</replaceable> ] }
-[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
-
-<phrase>and <replaceable class="PARAMETER">like_option</replaceable> is:</phrase>
-
-{ INCLUDING | EXCLUDING } { DEFAULTS | CONSTRAINTS | INDEXES | STORAGE | COMMENTS | ALL }
-
-<phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase>
-
-[ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) ]
-[ USING INDEX TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-
-<phrase><replaceable class="PARAMETER">exclude_element</replaceable> in an <literal>EXCLUDE</literal> constraint is:</phrase>
-
-{ <replaceable class="parameter">column</replaceable> | ( <replaceable class="parameter">expression</replaceable> ) } [ <replaceable class="parameter">opclass</replaceable> ] [ ASC | DESC ] [ NULLS { FIRST | LAST } ]
-</synopsis>
-<!## end>
-<!## XC>
-<synopsis>
-CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] <replaceable class="PARAMETER">table_name</replaceable> ( [
-  { <replaceable class="PARAMETER">column_name</replaceable> <replaceable class="PARAMETER">data_type</replaceable> [ DEFAULT <replaceable>default_expr</replaceable> ] [ <replaceable class="PARAMETER">column_constraint</replaceable> [ ... ] ]
-    | <replaceable>table_constraint</replaceable>
-    | LIKE <replaceable>parent_table</replaceable> [ <replaceable>like_option</replaceable> ... ] }
-    [, ... ]
-] )
-[ INHERITS ( <replaceable>parent_table</replaceable> [, ... ] ) ]
-[ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
-[ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
-[ TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-[ DISTRIBUTE BY { REPLICATION | ROUNDROBIN | { [HASH | MODULO ] ( <replaceable class="PARAMETER">column_name</replaceable> ) } } ]
-[ TO { GROUP <replaceable class="PARAMETER">groupname</replaceable> | NODE ( <replaceable class="PARAMETER">nodename</replaceable> [, ... ] ) } ]
-
-CREATE TABLE <replaceable class="PARAMETER">table_name</replaceable>
-    OF <replaceable class="PARAMETER">type_name</replaceable> [ (
-  { <replaceable class="PARAMETER">column_name</replaceable> WITH OPTIONS [ DEFAULT <replaceable>default_expr</replaceable> ] [ <replaceable class="PARAMETER">column_constraint</replaceable> [ ... ] ]
-    | <replaceable>table_constraint</replaceable> }
-    [, ... ]
-) ]
-[ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
-[ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
-[ TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-[ DISTRIBUTE BY { REPLICATION | ROUNDROBIN | { [HASH | MODULO ] ( <replaceable class="PARAMETER">column_name</replaceable> ) } } ]
-[ TO { GROUP <replaceable class="PARAMETER">groupname</replaceable> | NODE ( <replaceable class="PARAMETER">nodename</replaceable> [, ... ] ) } ]
-
-<phrase>where <replaceable class="PARAMETER">column_constraint</replaceable> is:</phrase>
-
-[ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-{ NOT NULL |
-  NULL |
-  CHECK ( <replaceable class="PARAMETER">expression</replaceable> ) |
-  UNIQUE <replaceable class="PARAMETER">index_parameters</replaceable> |
-  PRIMARY KEY <replaceable class="PARAMETER">index_parameters</replaceable> |
-  REFERENCES <replaceable class="PARAMETER">reftable</replaceable> [ ( <replaceable class="PARAMETER">refcolumn</replaceable> ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
-    [ ON DELETE <replaceable class="parameter">action</replaceable> ] [ ON UPDATE <replaceable class="parameter">action</replaceable> ] }
-[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
-
-<phrase>and <replaceable class="PARAMETER">table_constraint</replaceable> is:</phrase>
-
-[ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-{ CHECK ( <replaceable class="PARAMETER">expression</replaceable> ) |
-  UNIQUE ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) <replaceable class="PARAMETER">index_parameters</replaceable> |
-  PRIMARY KEY ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) <replaceable class="PARAMETER">index_parameters</replaceable> |
-  FOREIGN KEY ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) REFERENCES <replaceable class="PARAMETER">reftable</replaceable> [ ( <replaceable class="PARAMETER">refcolumn</replaceable> [, ... ] ) ]
-    [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE <replaceable class="parameter">action</replaceable> ] [ ON UPDATE <replaceable class="parameter">action</replaceable> ] }
-[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
-
-<phrase>and <replaceable class="PARAMETER">like_option</replaceable> is:</phrase>
-
-{ INCLUDING | EXCLUDING } { DEFAULTS | CONSTRAINTS | INDEXES | STORAGE | COMMENTS | ALL }
-
-<phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal> and <literal>PRIMARY KEY</literal> constraints are:</phrase>
-
-[ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) ]
-[ USING INDEX TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-
-</synopsis>
-<!## end>
-<!## XL>
-<synopsis>
-CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] <replaceable class="PARAMETER">table_name</replaceable> ( [
-  { <replaceable class="PARAMETER">column_name</replaceable> <replaceable class="PARAMETER">data_type</replaceable> [ DEFAULT <replaceable>default_expr</replaceable> ] [ <replaceable class="PARAMETER">column_constraint</replaceable> [ ... ] ]
-    | <replaceable>table_constraint</replaceable>
-    | LIKE <replaceable>parent_table</replaceable> [ <replaceable>like_option</replaceable> ... ] }
-    [, ... ]
-] )
-[ INHERITS ( <replaceable>parent_table</replaceable> [, ... ] ) ]
-[ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
-[ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
-[ TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-[ DISTRIBUTE BY { REPLICATION | ROUNDROBIN | { [HASH | MODULO ] ( <replaceable class="PARAMETER">column_name</replaceable> ) } } ]
-[ TO { GROUP <replaceable class="PARAMETER">groupname</replaceable> | NODE ( <replaceable class="PARAMETER">nodename</replaceable> [, ... ] ) } ]
-
-CREATE TABLE <replaceable class="PARAMETER">table_name</replaceable>
-    OF <replaceable class="PARAMETER">type_name</replaceable> [ (
-  { <replaceable class="PARAMETER">column_name</replaceable> WITH OPTIONS [ DEFAULT <replaceable>default_expr</replaceable> ] [ <replaceable class="PARAMETER">column_constraint</replaceable> [ ... ] ]
-    | <replaceable>table_constraint</replaceable> }
-    [, ... ]
-) ]
-[ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
-[ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
-[ TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-[ DISTRIBUTE BY { REPLICATION | ROUNDROBIN | { [HASH | MODULO ] ( <replaceable class="PARAMETER">column_name</replaceable> ) } } ]
-[ TO { GROUP <replaceable class="PARAMETER">groupname</replaceable> | NODE ( <replaceable class="PARAMETER">nodename</replaceable> [, ... ] ) } ]
-
-<phrase>where <replaceable class="PARAMETER">column_constraint</replaceable> is:</phrase>
-
-[ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-{ NOT NULL |
-  NULL |
-  CHECK ( <replaceable class="PARAMETER">expression</replaceable> ) |
-  UNIQUE <replaceable class="PARAMETER">index_parameters</replaceable> |
-  PRIMARY KEY <replaceable class="PARAMETER">index_parameters</replaceable> |
-  REFERENCES <replaceable class="PARAMETER">reftable</replaceable> [ ( <replaceable class="PARAMETER">refcolumn</replaceable> ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
-    [ ON DELETE <replaceable class="parameter">action</replaceable> ] [ ON UPDATE <replaceable class="parameter">action</replaceable> ] }
-[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
-
-<phrase>and <replaceable class="PARAMETER">table_constraint</replaceable> is:</phrase>
-
-[ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-{ CHECK ( <replaceable class="PARAMETER">expression</replaceable> ) |
-  UNIQUE ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) <replaceable class="PARAMETER">index_parameters</replaceable> |
-  PRIMARY KEY ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) <replaceable class="PARAMETER">index_parameters</replaceable> |
-  FOREIGN KEY ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) REFERENCES <replaceable class="PARAMETER">reftable</replaceable> [ ( <replaceable class="PARAMETER">refcolumn</replaceable> [, ... ] ) ]
-    [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE <replaceable class="parameter">action</replaceable> ] [ ON UPDATE <replaceable class="parameter">action</replaceable> ] }
-[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
-
-<phrase>and <replaceable class="PARAMETER">like_option</replaceable> is:</phrase>
-
-{ INCLUDING | EXLLUDING } { DEFAULTS | CONSTRAINTS | INDEXES | STORAGE | COMMENTS | ALL }
-
-<phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal> and <literal>PRIMARY KEY</literal> constraints are:</phrase>
-
-[ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) ]
-[ USING INDEX TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-
-</synopsis>
-<!## end>
-
- </refsynopsisdiv>
-
- <refsect1 id="SQL-CREATETABLE-description">
-  <title>Description</title>
-
-<!## XC>
-  <note>
-   <para>
-    The syntax of <command>CREATE TABLE</> applies only to <productname>Postgres-XC</>.
-   </para>
-  </note>
-<!## end>
-<!## XL>
-  <note>
-   <para>
-    The syntax of <command>CREATE TABLE</> applies only to <productname>Postgres-XL</>.
-   </para>
-  </note>
-<!## end>
-
-  <para>
-   <command>CREATE TABLE</command> will create a new, initially empty table
-   in the current database. The table will be owned by the user issuing the
-   command.
-  </para>
-
-  <para>
-   If a schema name is given (for example, <literal>CREATE TABLE
-   myschema.mytable ...</>) then the table is created in the specified
-   schema.  Otherwise it is created in the current schema.  Temporary
-   tables exist in a special schema, so a schema name cannot be given
-   when creating a temporary table.  The name of the table must be
-   distinct from the name of any other table, sequence, index, view,
-   or foreign table in the same schema.
-  </para>
-
-  <para>
-   <command>CREATE TABLE</command> also automatically creates a data
-   type that represents the composite type corresponding
-   to one row of the table.  Therefore, tables cannot have the same
-   name as any existing data type in the same schema.
-  </para>
-
-  <para>
-   The optional constraint clauses specify constraints (tests) that
-   new or updated rows must satisfy for an insert or update operation
-   to succeed.  A constraint is an SQL object that helps define the
-   set of valid values in the table in various ways.
-  </para>
-
-  <para>
-   There are two ways to define constraints: table constraints and
-   column constraints.  A column constraint is defined as part of a
-   column definition.  A table constraint definition is not tied to a
-   particular column, and it can encompass more than one column.
-   Every column constraint can also be written as a table constraint;
-   a column constraint is only a notational convenience for use when the
-   constraint only affects one column.
-  </para>
-&xc-constraint;
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>TEMPORARY</> or <literal>TEMP</></term>
-    <listitem>
-     <para>
-      If specified, the table is created as a temporary table.
-      Temporary tables are automatically dropped at the end of a
-      session, or optionally at the end of the current transaction
-      (see <literal>ON COMMIT</literal> below).  Existing permanent
-      tables with the same name are not visible to the current session
-      while the temporary table exists, unless they are referenced
-      with schema-qualified names. Any indexes created on a temporary
-      table are automatically temporary as well.
-     </para>
-
-     <para>
-      The <link linkend="autovacuum">autovacuum daemon</link> cannot
-      access and therefore cannot vacuum or analyze temporary tables.
-      For this reason, appropriate vacuum and analyze operations should be
-      performed via session SQL commands.  For example, if a temporary
-      table is going to be used in complex queries, it is wise to run
-      <command>ANALYZE</> on the temporary table after it is populated.
-     </para>
-
-     <para>
-      Optionally, <literal>GLOBAL</literal> or <literal>LOCAL</literal>
-      can be written before <literal>TEMPORARY</> or <literal>TEMP</>.
-      This makes no difference in <productname>PostgreSQL</>, but see
-      <xref linkend="sql-createtable-compatibility"
-      endterm="sql-createtable-compatibility-title">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>UNLOGGED</></term>
-    <listitem>
-     <para>
-      If specified, the table is created as an unlogged table.  Data written
-      to unlogged tables is not written to the write-ahead log (see <xref
-      linkend="wal">), which makes them considerably faster than ordinary
-      tables.  However, they are not crash-safe: an unlogged table is
-      automatically truncated after a crash or unclean shutdown.  The contents
-      of an unlogged table are also not replicated to standby servers.
-      Any indexes created on an unlogged table are automatically unlogged as
-      well; however, unlogged <link linkend="GiST">GiST indexes</link> are
-      currently not supported and cannot be created on an unlogged table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>IF NOT EXISTS</></term>
-    <listitem>
-     <para>
-      Do not throw an error if a relation with the same name already exists.
-      A notice is issued in this case.  Note that there is no guarantee that
-      the existing relation is anything like the one that would have been
-      created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">table_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the table to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OF <replaceable class="PARAMETER">type_name</replaceable></literal></term>
-    <listitem>
-     <para>
-      Creates a <firstterm>typed table</firstterm>, which takes its
-      structure from the specified composite type (name optionally
-      schema-qualified).  A typed table is tied to its type; for
-      example the table will be dropped if the type is dropped
-      (with <literal>DROP TYPE ... CASCADE</literal>).
-     </para>
-
-     <para>
-      When a typed table is created, then the data types of the
-      columns are determined by the underlying composite type and are
-      not specified by the <literal>CREATE TABLE</literal> command.
-      But the <literal>CREATE TABLE</literal> command can add defaults
-      and constraints to the table and can specify storage parameters.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">column_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of a column to be created in the new table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">data_type</replaceable></term>
-    <listitem>
-     <para>
-      The data type of the column. This can include array
-      specifiers. For more information on the data types supported by
-<!## PG>
-      <productname>PostgreSQL</productname>, refer to <xref
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname>, refer to <xref
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname>, refer to <xref
-<!## end>
-      linkend="datatype">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>COLLATE <replaceable>collation</replaceable></literal></term>
-    <listitem>
-     <para>
-      The <literal>COLLATE</> clause assigns a collation to
-      the column (which must be of a collatable data type).
-      If not specified, the column data type's default collation is used.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>INHERITS ( <replaceable>parent_table</replaceable> [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      The optional <literal>INHERITS</> clause specifies a list of
-      tables from which the new table automatically inherits all
-      columns.
-     </para>
-
-     <para>
-      Use of <literal>INHERITS</> creates a persistent relationship
-      between the new child table and its parent table(s).  Schema
-      modifications to the parent(s) normally propagate to children
-      as well, and by default the data of the child table is included in
-      scans of the parent(s).
-     </para>
-
-     <para>
-      If the same column name exists in more than one parent
-      table, an error is reported unless the data types of the columns
-      match in each of the parent tables.  If there is no conflict,
-      then the duplicate columns are merged to form a single column in
-      the new table.  If the column name list of the new table
-      contains a column name that is also inherited, the data type must
-      likewise match the inherited column(s), and the column
-      definitions are merged into one.  If the
-      new table explicitly specifies a default value for the column,
-      this default overrides any defaults from inherited declarations
-      of the column.  Otherwise, any parents that specify default
-      values for the column must all specify the same default, or an
-      error will be reported.
-     </para>
-
-<!## XC>
-&xconly;
-     <para>
-      It is currently not possible to distribute a table with more than one parent.
-     </para>
-&common;
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      It is currently not possible to distribute a table with more than one parent.
-     </para>
-&common;
-<!## end>
-
-     <para>
-      <literal>CHECK</> constraints are merged in essentially the same way as
-      columns: if multiple parent tables and/or the new table definition
-      contain identically-named <literal>CHECK</> constraints, these
-      constraints must all have the same check expression, or an error will be
-      reported.  Constraints having the same name and expression will
-      be merged into one copy.  Notice that an unnamed <literal>CHECK</>
-      constraint in the new table will never be merged, since a unique name
-      will always be chosen for it.
-     </para>
-
-     <para>
-      Column <literal>STORAGE</> settings are also copied from parent tables.
-     </para>
-
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>LIKE <replaceable>parent_table</replaceable> [ <replaceable>like_option</replaceable> ... ]</literal></term>
-    <listitem>
-     <para>
-      The <literal>LIKE</literal> clause specifies a table from which
-      the new table automatically copies all column names, their data types,
-      and their not-null constraints.
-     </para>
-     <para>
-      Unlike <literal>INHERITS</literal>, the new table and original table
-      are completely decoupled after creation is complete.  Changes to the
-      original table will not be applied to the new table, and it is not
-      possible to include data of the new table in scans of the original
-      table.
-     </para>
-     <para>
-      Default expressions for the copied column definitions will only be
-      copied if <literal>INCLUDING DEFAULTS</literal> is specified.  The
-      default behavior is to exclude default expressions, resulting in the
-      copied columns in the new table having null defaults.
-     </para>
-     <para>
-      Not-null constraints are always copied to the new table.
-      <literal>CHECK</literal> constraints will only be copied if
-      <literal>INCLUDING CONSTRAINTS</literal> is specified; other types of
-      constraints will never be copied. Also, no distinction is made between
-      column constraints and table constraints &mdash; when constraints are
-      requested, all check constraints are copied.
-     </para>
-     <para>
-      Any indexes on the original table will not be created on the new
-      table, unless the <literal>INCLUDING INDEXES</literal> clause is
-      specified.
-     </para>
-     <para>
-      <literal>STORAGE</> settings for the copied column definitions will only
-      be copied if <literal>INCLUDING STORAGE</literal> is specified.  The
-      default behavior is to exclude <literal>STORAGE</> settings, resulting
-      in the copied columns in the new table having type-specific default
-      settings.  For more on <literal>STORAGE</> settings, see
-      <xref linkend="storage-toast">.
-     </para>
-     <para>
-      Comments for the copied columns, constraints, and indexes
-      will only be copied if <literal>INCLUDING COMMENTS</literal>
-      is specified. The default behavior is to exclude comments, resulting in
-      the copied columns and constraints in the new table having no comments.
-     </para>
-     <para>
-      <literal>INCLUDING ALL</literal> is an abbreviated form of
-      <literal>INCLUDING DEFAULTS INCLUDING CONSTRAINTS INCLUDING INDEXES INCLUDING STORAGE INCLUDING COMMENTS</literal>.
-     </para>
-     <para>
-      Note also that unlike <literal>INHERITS</literal>, columns and
-      constraints copied by <literal>LIKE</> are not merged with similarly
-      named columns and constraints.
-      If the same name is specified explicitly or in another
-      <literal>LIKE</literal> clause, an error is signalled.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable></literal></term>
-    <listitem>
-     <para>
-      An optional name for a column or table constraint.  If the
-      constraint is violated, the constraint name is present in error messages,
-      so constraint names like <literal>col must be positive</> can be used
-      to communicate helpful constraint information to client applications.
-      (Double-quotes are needed to specify constraint names that contain spaces.)
-      If a constraint name is not specified, the system generates a name.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NOT NULL</></term>
-    <listitem>
-     <para>
-      The column is not allowed to contain null values.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NULL</></term>
-    <listitem>
-     <para>
-      The column is allowed to contain null values. This is the default.
-     </para>
-
-     <para>
-      This clause is only provided for compatibility with
-      non-standard SQL databases.  Its use is discouraged in new
-      applications.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CHECK ( <replaceable class="PARAMETER">expression</replaceable> )</literal></term>
-    <listitem>
-     <para>
-      The <literal>CHECK</> clause specifies an expression producing a
-      Boolean result which new or updated rows must satisfy for an
-      insert or update operation to succeed.  Expressions evaluating
-      to TRUE or UNKNOWN succeed.  Should any row of an insert or
-      update operation produce a FALSE result an error exception is
-      raised and the insert or update does not alter the database.  A
-      check constraint specified as a column constraint should
-      reference that column's value only, while an expression
-      appearing in a table constraint can reference multiple columns.
-     </para>
-
-     <para>
-      Currently, <literal>CHECK</literal> expressions cannot contain
-      subqueries nor refer to variables other than columns of the
-      current row.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DEFAULT
-    <replaceable>default_expr</replaceable></literal></term>
-    <listitem>
-     <para>
-      The <literal>DEFAULT</> clause assigns a default data value for
-      the column whose column definition it appears within.  The value
-      is any variable-free expression (subqueries and cross-references
-      to other columns in the current table are not allowed).  The
-      data type of the default expression must match the data type of the
-      column.
-     </para>
-
-     <para>
-      The default expression will be used in any insert operation that
-      does not specify a value for the column.  If there is no default
-      for a column, then the default is null.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>UNIQUE</> (column constraint)</term>
-    <term><literal>UNIQUE ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] )</> (table constraint)</term>
-
-    <listitem>
-     <para>
-      The <literal>UNIQUE</literal> constraint specifies that a
-      group of one or more columns of a table can contain
-      only unique values. The behavior of the unique table constraint
-      is the same as that for column constraints, with the additional
-      capability to span multiple columns.
-     </para>
-
-     <para>
-      For the purpose of a unique constraint, null values are not
-      considered equal.
-     </para>
-
-<!## XC>
-&xconly;
-     <para>
-      In <productname>Postgres-XC</>, if <command>DISTRIBUTE BY
-      REPLICATION</> is not specified, only the distribution key is
-      allowed to have this constraint.
-     </para>
-
-&common;
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      In <productname>Postgres-XL</>, if <command>DISTRIBUTE BY
-      REPLICATION</> is not specified, only the distribution key is
-      allowed to have this constraint.
-     </para>
-
-&common;
-<!## end>
-
-     <para>
-      Each unique table constraint must name a set of columns that is
-      different from the set of columns named by any other unique or
-      primary key constraint defined for the table.  (Otherwise it
-      would just be the same constraint listed twice.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>PRIMARY KEY</> (column constraint)</term>
-    <term><literal>PRIMARY KEY ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] )</> (table constraint)</term>
-    <listitem>
-     <para>
-      The primary key constraint specifies that a column or columns of a table
-      can contain only unique (non-duplicate), nonnull values.
-      Technically, <literal>PRIMARY KEY</literal> is merely a
-      combination of <literal>UNIQUE</> and <literal>NOT NULL</>, but
-      identifying a set of columns as primary key also provides
-      metadata about the design of the schema, as a primary key
-      implies that other tables
-      can rely on this set of columns as a unique identifier for rows.
-     </para>
-
-     <para>
-      Only one primary key can be specified for a table, whether as a
-      column constraint or a table constraint.
-     </para>
-
-<!## PG>
-     <para>
-      The primary key constraint should name a set of columns that is
-      different from other sets of columns named by any unique
-      constraint defined for the same table.
-     </para>
-<!## end>
-<!## XC>
-     <para>
-      The primary key constraint should name a set of columns that is
-      different from other sets of columns named by any unique
-      constraint defined for the same table.
-     </para>
-
-     <para>
-      If <command>DISTRIBUTE BY REPLICATION</> is not specified, the
-      distribution key must be included in the set of primary key
-      columns.
-     </para>
-<!## end>
-<!## XL>
-     <para>
-      The primary key constraint should name a set of columns that is
-      different from other sets of columns named by any unique
-      constraint defined for the same table.
-     </para>
-
-     <para>
-      If <command>DISTRIBUTE BY REPLICATION</> is not specified, the
-      distribution key must be included in the set of primary key
-      columns.
-     </para>
-<!## end>
-
-    </listitem>
-   </varlistentry>
-
-<!## PG>
-<!-- NOTICE:
-     No exclude constraints yet.
--->
-   <varlistentry id="SQL-CREATETABLE-EXCLUDE">
-    <term><literal>EXCLUDE [ USING <replaceable class="parameter">index_method</replaceable> ] ( <replaceable class="parameter">exclude_element</replaceable> WITH <replaceable class="parameter">operator</replaceable> [, ... ] ) <replaceable class="parameter">index_parameters</replaceable> [ WHERE ( <replaceable class="parameter">predicate</replaceable> ) ]</literal></term>
-    <listitem>
-     <para>
-      The <literal>EXCLUDE</> clause defines an exclusion
-      constraint, which guarantees that if
-      any two rows are compared on the specified column(s) or
-      expression(s) using the specified operator(s), not all of these
-      comparisons will return <literal>TRUE</>.  If all of the
-      specified operators test for equality, this is equivalent to a
-      <literal>UNIQUE</> constraint, although an ordinary unique constraint
-      will be faster.  However, exclusion constraints can specify
-      constraints that are more general than simple equality.
-      For example, you can specify a constraint that
-      no two rows in the table contain overlapping circles
-      (see <xref linkend="datatype-geometric">) by using the
-      <literal>&amp;&amp;</> operator.
-     </para>
-
-     <para>
-      Exclusion constraints are implemented using
-      an index, so each specified operator must be associated with an
-      appropriate operator class
-      (see <xref linkend="indexes-opclass">) for the index access
-      method <replaceable>index_method</>.
-      The operators are required to be commutative.
-      Each <replaceable class="parameter">exclude_element</replaceable>
-      can optionally specify an operator class and/or ordering options;
-      these are described fully under
-      <xref linkend="sql-createindex">.
-     </para>
-
-     <para>
-      The access method must support <literal>amgettuple</> (see <xref
-      linkend="indexam">); at present this means <acronym>GIN</>
-      cannot be used.  Although it's allowed, there is little point in using
-      B-tree or hash indexes with an exclusion constraint, because this
-      does nothing that an ordinary unique constraint doesn't do better.
-      So in practice the access method will always be <acronym>GiST</>.
-     </para>
-
-     <para>
-      The <replaceable class="parameter">predicate</> allows you to specify an
-      exclusion constraint on a subset of the table; internally this creates a
-      partial index. Note that parentheses are required around the predicate.
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-   <varlistentry>
-    <term><literal>REFERENCES <replaceable class="parameter">reftable</replaceable> [ ( <replaceable class="parameter">refcolumn</replaceable> ) ] [ MATCH <replaceable class="parameter">matchtype</replaceable> ] [ ON DELETE <replaceable class="parameter">action</replaceable> ] [ ON UPDATE <replaceable class="parameter">action</replaceable> ]</literal> (column constraint)</term>
-
-   <term><literal>FOREIGN KEY ( <replaceable class="parameter">column</replaceable> [, ... ] )
-    REFERENCES <replaceable class="parameter">reftable</replaceable> [ ( <replaceable class="parameter">refcolumn</replaceable> [, ... ] ) ]
-    [ MATCH <replaceable class="parameter">matchtype</replaceable> ]
-    [ ON DELETE <replaceable class="parameter">action</replaceable> ]
-    [ ON UPDATE <replaceable class="parameter">action</replaceable> ]</literal>
-    (table constraint)</term>
-
-    <listitem>
-     <para>
-      These clauses specify a foreign key constraint, which requires
-      that a group of one or more columns of the new table must only
-      contain values that match values in the referenced
-      column(s) of some row of the referenced table.  If <replaceable
-      class="parameter">refcolumn</replaceable> is omitted, the
-      primary key of the <replaceable class="parameter">reftable</replaceable>
-      is used.  The referenced columns must be the columns of a non-deferrable
-      unique or primary key constraint in the referenced table.  Note that
-      foreign key constraints cannot be defined between temporary tables and
-      permanent tables.
-     </para>
-
-     <para>
-      A value inserted into the referencing column(s) is matched against the
-      values of the referenced table and referenced columns using the
-      given match type.  There are three match types: <literal>MATCH
-      FULL</>, <literal>MATCH PARTIAL</>, and <literal>MATCH
-      SIMPLE</literal>, which is also the default.  <literal>MATCH
-      FULL</> will not allow one column of a multicolumn foreign key
-      to be null unless all foreign key columns are null.
-      <literal>MATCH SIMPLE</literal> allows some foreign key columns
-      to be null while other parts of the foreign key are not
-      null. <literal>MATCH PARTIAL</> is not yet implemented.
-     </para>
-
-     <para>
-      In addition, when the data in the referenced columns is changed,
-      certain actions are performed on the data in this table's
-      columns.  The <literal>ON DELETE</literal> clause specifies the
-      action to perform when a referenced row in the referenced table is
-      being deleted.  Likewise, the <literal>ON UPDATE</literal>
-      clause specifies the action to perform when a referenced column
-      in the referenced table is being updated to a new value. If the
-      row is updated, but the referenced column is not actually
-      changed, no action is done. Referential actions other than the
-      <literal>NO ACTION</literal> check cannot be deferred, even if
-      the constraint is declared deferrable. There are the following possible
-      actions for each clause:
-
-      <variablelist>
-       <varlistentry>
-        <term><literal>NO ACTION</literal></term>
-        <listitem>
-         <para>
-          Produce an error indicating that the deletion or update
-          would create a foreign key constraint violation.
-          If the constraint is deferred, this
-          error will be produced at constraint check time if there still
-          exist any referencing rows.  This is the default action.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>RESTRICT</literal></term>
-        <listitem>
-         <para>
-          Produce an error indicating that the deletion or update
-          would create a foreign key constraint violation.
-          This is the same as <literal>NO ACTION</literal> except that
-          the check is not deferrable.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>CASCADE</literal></term>
-        <listitem>
-         <para>
-          Delete any rows referencing the deleted row, or update the
-          value of the referencing column to the new value of the
-          referenced column, respectively.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>SET NULL</literal></term>
-        <listitem>
-         <para>
-          Set the referencing column(s) to null.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>SET DEFAULT</literal></term>
-        <listitem>
-         <para>
-          Set the referencing column(s) to their default values.
-         </para>
-        </listitem>
-       </varlistentry>
-      </variablelist>
-     </para>
-
-     <para>
-      If the referenced column(s) are changed frequently, it might be wise to
-      add an index to the foreign key column so that referential actions
-      associated with the foreign key column can be performed more
-      efficiently.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DEFERRABLE</literal></term>
-    <term><literal>NOT DEFERRABLE</literal></term>
-    <listitem>
-     <para>
-      This controls whether the constraint can be deferred.  A
-      constraint that is not deferrable will be checked immediately
-      after every command.  Checking of constraints that are
-      deferrable can be postponed until the end of the transaction
-      (using the <xref linkend="sql-set-constraints"> command).
-      <literal>NOT DEFERRABLE</literal> is the default.
-      Currently, only <literal>UNIQUE</>, <literal>PRIMARY KEY</>,
-      <literal>EXCLUDE</>, and
-      <literal>REFERENCES</> (foreign key) constraints accept this
-      clause.  <literal>NOT NULL</> and <literal>CHECK</> constraints are not
-      deferrable.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>INITIALLY IMMEDIATE</literal></term>
-    <term><literal>INITIALLY DEFERRED</literal></term>
-    <listitem>
-     <para>
-      If a constraint is deferrable, this clause specifies the default
-      time to check the constraint.  If the constraint is
-      <literal>INITIALLY IMMEDIATE</literal>, it is checked after each
-      statement. This is the default.  If the constraint is
-      <literal>INITIALLY DEFERRED</literal>, it is checked only at the
-      end of the transaction.  The constraint check time can be
-      altered with the <xref linkend="sql-set-constraints"> command.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      This clause specifies optional storage parameters for a table or index;
-      see <xref linkend="sql-createtable-storage-parameters"
-      endterm="sql-createtable-storage-parameters-title"> for more
-      information.  The <literal>WITH</> clause for a
-      table can also include <literal>OIDS=TRUE</> (or just <literal>OIDS</>)
-      to specify that rows of the new table
-      should have OIDs (object identifiers) assigned to them, or
-      <literal>OIDS=FALSE</> to specify that the rows should not have OIDs.
-      If <literal>OIDS</> is not specified, the default setting depends upon
-      the <xref linkend="guc-default-with-oids"> configuration parameter.
-      (If the new table inherits from any tables that have OIDs, then
-      <literal>OIDS=TRUE</> is forced even if the command says
-      <literal>OIDS=FALSE</>.)
-     </para>
-
-     <para>
-      If <literal>OIDS=FALSE</literal> is specified or implied, the new
-      table does not store OIDs and no OID will be assigned for a row inserted
-      into it. This is generally considered worthwhile, since it
-      will reduce OID consumption and thereby postpone the wraparound
-      of the 32-bit OID counter. Once the counter wraps around, OIDs
-      can no longer be assumed to be unique, which makes them
-      considerably less useful. In addition, excluding OIDs from a
-      table reduces the space required to store the table on disk by
-      4 bytes per row (on most machines), slightly improving performance.
-     </para>
-
-     <para>
-      To remove OIDs from a table after it has been created, use <xref
-      linkend="sql-altertable">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>WITH OIDS</></term>
-    <term><literal>WITHOUT OIDS</></term>
-    <listitem>
-     <para>
-      These are obsolescent syntaxes equivalent to <literal>WITH (OIDS)</>
-      and <literal>WITH (OIDS=FALSE)</>, respectively.  If you wish to give
-      both an <literal>OIDS</> setting and storage parameters, you must use
-      the <literal>WITH ( ... )</> syntax; see above.
-     </para>
-<!## XC>
-&xconly;
-     <para>
-      In <productname>Postgres-XC</>, OID is kept locally in each
-      Datanode and Coordinator.  The OID value may inconsistent for
-      rows stored in different Datanodes.
-     </para>
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      In <productname>Postgres-XL</>, OID is managed locally in each
-      Datanode and Coordinator.  The OID value may be inconsistent for
-      rows stored in different Datanodes.
-     </para>
-<!## end>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ON COMMIT</literal></term>
-    <listitem>
-     <para>
-      The behavior of temporary tables at the end of a transaction
-      block can be controlled using <literal>ON COMMIT</literal>.
-      The three options are:
-
-      <variablelist>
-       <varlistentry>
-        <term><literal>PRESERVE ROWS</literal></term>
-        <listitem>
-         <para>
-          No special action is taken at the ends of transactions.
-          This is the default behavior.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>DELETE ROWS</literal></term>
-        <listitem>
-         <para>
-          All rows in the temporary table will be deleted at the end
-          of each transaction block.  Essentially, an automatic <xref
-          linkend="sql-truncate"> is done
-          at each commit.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>DROP</literal></term>
-        <listitem>
-         <para>
-          The temporary table will be dropped at the end of the current
-          transaction block.
-         </para>
-        </listitem>
-       </varlistentry>
-      </variablelist>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable></literal></term>
-    <listitem>
-     <para>
-      The <replaceable class="PARAMETER">tablespace</replaceable> is the name
-      of the tablespace in which the new table is to be created.
-      If not specified,
-      <xref linkend="guc-default-tablespace"> is consulted, or
-      <xref linkend="guc-temp-tablespaces"> if the table is temporary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>USING INDEX TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable></literal></term>
-    <listitem>
-     <para>
-      This clause allows selection of the tablespace in which the index
-      associated with a <literal>UNIQUE</literal>, <literal>PRIMARY
-      KEY</literal>, or <literal>EXCLUDE</> constraint will be created.
-      If not specified,
-      <xref linkend="guc-default-tablespace"> is consulted, or
-      <xref linkend="guc-temp-tablespaces"> if the table is temporary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-<!## XC>
-   <varlistentry>
-    <term><literal>DISTRIBUTE BY</literal></term>
-    <listitem>
-&xconly;
-     <para>
-      This clause specifies how the table is distributed or replicated among Datanodes.
-     </para>
-
-      <variablelist>
-
-       <varlistentry>
-        <term><literal>REPLICATION</literal></term>
-        <listitem>
-         <para>
-          Each row of the table will be replicated into all the
-          Datanode of the <productname>Postgres-XC</> database
-          cluster.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>ROUNDROBIN</literal></term>
-        <listitem>
-         <para>
-          Each row of the table will be placed in one of the Datanodes
-          by round-robin manner.  The value of the row will not be
-          needed to determine what Datanode to go.
-         </para>
-        </listitem>
-       </varlistentry>
-
-      <varlistentry>
-       <term><literal>HASH ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the hash value
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>MODULO ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the modulo
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-    <para>
-     If <literal>DISTRIBUTE BY</> is not specified, columns with
-     UNIQUE constraint will be chosen as the distribution key.  If no
-     such column is specified, distribution column is the first
-     eligible column in the definition.  If no such column is found,
-     then the table will be distributed by <literal>ROUNDROBIN</>.
-    </para>
-
-   </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TO GROUP</literal></term>
-    <term><literal>TO NODE</literal></term>
-      <listitem>
-       <para>
-        This defines on the list of nodes on which table data exists.
-        If this is not specified table data is present on all Datanodes.
-       </para>
-      </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">nodename</replaceable></term>
-      <listitem>
-       <para>
-        Associated with <literal>TO NODE</literal>, it defines a <productname>
-        Postgres-XC</productname> node of catalog pgxc_node.
-       </para>
-      </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">groupname</replaceable></term>
-      <listitem>
-       <para>
-        Associated with <literal>TO GROUP</literal>, it defines a <productname>
-        Postgres-XC</productname> node group in catalog pgxc_group.
-       </para>
-      </listitem>
-   </varlistentry>
-<!## end>
-<!## XL>
-   <varlistentry>
-    <term><literal>DISTRIBUTE BY</literal></term>
-    <listitem>
-&xlonly;
-     <para>
-      This clause specifies how the table is distributed or replicated among Datanodes.
-     </para>
-
-      <variablelist>
-
-       <varlistentry>
-        <term><literal>REPLICATION</literal></term>
-        <listitem>
-         <para>
-          Each row of the table will be replicated to all the
-          Datanode of the <productname>Postgres-XL</> database
-          cluster.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>ROUNDROBIN</literal></term>
-        <listitem>
-         <para>
-          Each row of the table will be placed in one of the Datanodes
-          in a round-robin manner.  The value of the row will not be
-          needed to determine what Datanode to go.
-         </para>
-        </listitem>
-       </varlistentry>
-
-      <varlistentry>
-       <term><literal>HASH ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the hash value
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>MODULO ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the modulo
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-    <para>
-     If <literal>DISTRIBUTE BY</> is not specified, columns with
-     UNIQUE constraint will be chosen as the distribution key.  If no
-     such column is specified, distribution column is the first
-     eligible column in the definition.  If no such column is found,
-     then the table will be distributed by <literal>ROUNDROBIN</>.
-    </para>
-
-   </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TO GROUP</literal></term>
-    <term><literal>TO NODE</literal></term>
-      <listitem>
-       <para>
-        This defines on the list of nodes on which table data exists.
-        If this is not specified table data is present on all Datanodes.
-       </para>
-      </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">nodename</replaceable></term>
-      <listitem>
-       <para>
-        Associated with <literal>TO NODE</literal>, it defines a <productname>
-        Postgres-XL</productname> node of catalog pgxc_node.
-       </para>
-      </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">groupname</replaceable></term>
-      <listitem>
-       <para>
-        Associated with <literal>TO GROUP</literal>, it defines a <productname>
-        Postgres-XL</productname> node group in catalog pgxc_group.
-       </para>
-      </listitem>
-   </varlistentry>
-<!## end>
-
-  </variablelist>
-
-  <refsect2 id="SQL-CREATETABLE-storage-parameters">
-   <title id="SQL-CREATETABLE-storage-parameters-title">Storage Parameters</title>
-
- <indexterm zone="sql-createtable-storage-parameters">
-  <primary>storage parameters</primary>
- </indexterm>
-
-   <para>
-    The <literal>WITH</> clause can specify <firstterm>storage parameters</>
-    for tables, and for indexes associated with a <literal>UNIQUE</literal>,
-    <literal>PRIMARY KEY</literal>, or <literal>EXCLUDE</> constraint.
-    Storage parameters for
-    indexes are documented in <xref linkend="SQL-CREATEINDEX">.
-    The storage parameters currently
-    available for tables are listed below.  For each parameter, unless noted,
-    there is an additional parameter with the same name prefixed with
-    <literal>toast.</literal>, which can be used to control the behavior of the
-    table's secondary <acronym>TOAST</> table, if any
-    (see <xref linkend="storage-toast"> for more information about TOAST).
-    Note that the TOAST table inherits the
-    <literal>autovacuum_*</literal> values from its parent table, if there are
-    no <literal>toast.autovacuum_*</literal> settings set.
-   </para>
-
-   <variablelist>
-
-   <varlistentry>
-    <term><literal>fillfactor</> (<type>integer</>)</term>
-    <listitem>
-     <para>
-      The fillfactor for a table is a percentage between 10 and 100.
-      100 (complete packing) is the default.  When a smaller fillfactor
-      is specified, <command>INSERT</> operations pack table pages only
-      to the indicated percentage; the remaining space on each page is
-      reserved for updating rows on that page.  This gives <command>UPDATE</>
-      a chance to place the updated copy of a row on the same page as the
-      original, which is more efficient than placing it on a different page.
-      For a table whose entries are never updated, complete packing is the
-      best choice, but in heavily updated tables smaller fillfactors are
-      appropriate.  This parameter cannot be set for TOAST tables.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>autovacuum_enabled</>, <literal>toast.autovacuum_enabled</literal> (<type>boolean</>)</term>
-    <listitem>
-     <para>
-     Enables or disables the autovacuum daemon on a particular table.
-     If true, the autovacuum daemon will initiate a <command>VACUUM</> operation
-     on a particular table when the number of updated or deleted tuples exceeds
-     <literal>autovacuum_vacuum_threshold</> plus
-     <literal>autovacuum_vacuum_scale_factor</> times the number of live tuples
-     currently estimated to be in the relation.
-     Similarly, it will initiate an <command>ANALYZE</> operation when the
-     number of inserted, updated or deleted tuples exceeds
-     <literal>autovacuum_analyze_threshold</> plus
-     <literal>autovacuum_analyze_scale_factor</> times the number of live tuples
-     currently estimated to be in the relation.
-     If false, this table will not be autovacuumed, except to prevent
-     transaction Id wraparound. See <xref linkend="vacuum-for-wraparound"> for
-     more about wraparound prevention.
-     Observe that this variable inherits its value from the <xref
-     linkend="guc-autovacuum"> setting.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>autovacuum_vacuum_threshold</>, <literal>toast.autovacuum_vacuum_threshold</literal> (<type>integer</>)</term>
-    <listitem>
-     <para>
-     Minimum number of updated or deleted tuples before initiate a
-     <command>VACUUM</> operation on a particular table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>autovacuum_vacuum_scale_factor</>, <literal>toast.autovacuum_vacuum_scale_factor</literal> (<type>float4</>)</term>
-    <listitem>
-     <para>
-     Multiplier for <structfield>reltuples</> to add to
-     <literal>autovacuum_vacuum_threshold</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>autovacuum_analyze_threshold</> (<type>integer</>)</term>
-    <listitem>
-     <para>
-     Minimum number of inserted, updated, or deleted tuples before initiate an
-     <command>ANALYZE</> operation on a particular table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>autovacuum_analyze_scale_factor</> (<type>float4</>)</term>
-    <listitem>
-     <para>
-     Multiplier for <structfield>reltuples</> to add to
-     <literal>autovacuum_analyze_threshold</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>autovacuum_vacuum_cost_delay</>, <literal>toast.autovacuum_vacuum_cost_delay</literal> (<type>integer</>)</term>
-    <listitem>
-     <para>
-     Custom <xref linkend="guc-autovacuum-vacuum-cost-delay"> parameter.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>autovacuum_vacuum_cost_limit</>, <literal>toast.autovacuum_vacuum_cost_limit</literal> (<type>integer</>)</term>
-    <listitem>
-     <para>
-     Custom <xref linkend="guc-autovacuum-vacuum-cost-limit"> parameter.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>autovacuum_freeze_min_age</>, <literal>toast.autovacuum_freeze_min_age</literal> (<type>integer</>)</term>
-    <listitem>
-     <para>
-     Custom <xref linkend="guc-vacuum-freeze-min-age"> parameter. Note that
-     autovacuum will ignore attempts to set a per-table
-     <literal>autovacuum_freeze_min_age</> larger than the half system-wide
-     <xref linkend="guc-autovacuum-freeze-max-age"> setting.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>autovacuum_freeze_max_age</>, <literal>toast.autovacuum_freeze_max_age</literal> (<type>integer</>)</term>
-    <listitem>
-     <para>
-     Custom <xref linkend="guc-autovacuum-freeze-max-age"> parameter. Note that
-     autovacuum will ignore attempts to set a per-table
-     <literal>autovacuum_freeze_max_age</> larger than the system-wide setting
-     (it can only be set smaller). Note that while you can set
-     <literal>autovacuum_freeze_max_age</> very small, or even zero, this is
-     usually unwise since it will force frequent vacuuming.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>autovacuum_freeze_table_age</literal>, <literal>toast.autovacuum_freeze_table_age</literal> (<type>integer</type>)</term>
-    <listitem>
-     <para>
-      Custom <xref linkend="guc-vacuum-freeze-table-age"> parameter.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   </variablelist>
-
-  </refsect2>
- </refsect1>
-
- <refsect1 id="SQL-CREATETABLE-notes">
-  <title>Notes</title>
-
-<!## PG>
-    <para>
-     Using OIDs in new applications is not recommended: where
-     possible, using a <literal>SERIAL</literal> or other sequence
-     generator as the table's primary key is preferred. However, if
-     your application does make use of OIDs to identify specific
-     rows of a table, it is recommended to create a unique constraint
-     on the <structfield>oid</> column of that table, to ensure that
-     OIDs in the table will indeed uniquely identify rows even after
-     counter wraparound.  Avoid assuming that OIDs are unique across
-     tables; if you need a database-wide unique identifier, use the
-     combination of <structfield>tableoid</> and row OID for the
-     purpose.
-    </para>
-<!## end>
-<!## XC>
-    <para>
-     Using OIDs in new applications is not recommended: where
-     possible.
-    </para>
-<!## end>
-<!## XL>
-    <para>
-     Using OIDs in new applications is not recommended: where
-     possible.
-    </para>
-<!## end>
-
-    <tip>
-     <para>
-      The use of <literal>OIDS=FALSE</literal> is not recommended
-      for tables with no primary key, since without either an OID or a
-      unique data key, it is difficult to identify specific rows.
-     </para>
-    </tip>
-
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> automatically creates an
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> automatically creates an
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> automatically creates an
-<!## end>
-     index for each unique constraint and primary key constraint to
-     enforce uniqueness.  Thus, it is not necessary to create an
-     index explicitly for primary key columns.  (See <xref
-     linkend="sql-createindex"> for more information.)
-    </para>
-
-    <para>
-     Unique constraints and primary keys are not inherited in the
-     current implementation.  This makes the combination of
-     inheritance and unique constraints rather dysfunctional.
-    </para>
-
-    <para>
-     A table cannot have more than 1600 columns.  (In practice, the
-     effective limit is usually lower because of tuple-length constraints.)
-    </para>
-
- </refsect1>
-
-
- <refsect1 id="SQL-CREATETABLE-examples">
-  <title>Examples</title>
-
-  <para>
-   Create table <structname>films</> and table
-   <structname>distributors</>:
-
-<programlisting>
-CREATE TABLE films (
-    code        char(5) CONSTRAINT firstkey PRIMARY KEY,
-    title       varchar(40) NOT NULL,
-    did         integer NOT NULL,
-    date_prod   date,
-    kind        varchar(10),
-    len         interval hour to minute
-);
-</programlisting>
-
-<!## PG>
-<programlisting>
-CREATE TABLE distributors (
-     did    integer PRIMARY KEY DEFAULT nextval('serial'),
-     name   varchar(40) NOT NULL CHECK (name &lt;&gt; '')
-);
-</programlisting>
-<!## end>
-<!## XC>
-<!-- NOTICE:
-     XC does not support immutable function here.
--->
-<programlisting>
-CREATE TABLE distributors (
-     did    integer PRIMARY KEY,
-     name   varchar(40) NOT NULL CHECK (name &lt;&gt; '')
-);
-</programlisting>
-<!## end>
-<!## XL>
-<!-- NOTICE:
-     XL does not support immutable function here.
--->
-<programlisting>
-CREATE TABLE distributors (
-     did    integer PRIMARY KEY,
-     name   varchar(40) NOT NULL CHECK (name &lt;&gt; '')
-);
-</programlisting>
-<!## end>
-  </para>
-
-  <para>
-   Create a table with a 2-dimensional array:
-
-<programlisting>
-CREATE TABLE array_int (
-    vector  int[][]
-);
-</programlisting>
-  </para>
-
-  <para>
-   Define a unique table constraint for the table
-   <literal>films</literal>.  Unique table constraints can be defined
-   on one or more columns of the table:
-
-<programlisting>
-CREATE TABLE films (
-    code        char(5),
-    title       varchar(40),
-    did         integer,
-    date_prod   date,
-    kind        varchar(10),
-    len         interval hour to minute,
-    CONSTRAINT production UNIQUE(date_prod)
-);
-</programlisting>
-  </para>
-
-  <para>
-   Define a check column constraint:
-
-<programlisting>
-CREATE TABLE distributors (
-    did     integer CHECK (did &gt; 100),
-    name    varchar(40)
-);
-</programlisting>
-  </para>
-
-  <para>
-   Define a check table constraint:
-
-<programlisting>
-CREATE TABLE distributors (
-    did     integer,
-    name    varchar(40)
-    CONSTRAINT con1 CHECK (did &gt; 100 AND name &lt;&gt; '')
-);
-</programlisting>
-  </para>
-
-  <para>
-   Define a primary key table constraint for the table
-   <structname>films</>:
-
-<programlisting>
-CREATE TABLE films (
-    code        char(5),
-    title       varchar(40),
-    did         integer,
-    date_prod   date,
-    kind        varchar(10),
-    len         interval hour to minute,
-    CONSTRAINT code_title PRIMARY KEY(code,title)
-);
-</programlisting>
-  </para>
-
-  <para>
-   Define a primary key constraint for table
-   <structname>distributors</>.  The following two examples are
-   equivalent, the first using the table constraint syntax, the second
-   the column constraint syntax:
-
-<programlisting>
-CREATE TABLE distributors (
-    did     integer,
-    name    varchar(40),
-    PRIMARY KEY(did)
-);
-</programlisting>
-
-<programlisting>
-CREATE TABLE distributors (
-    did     integer PRIMARY KEY,
-    name    varchar(40)
-);
-</programlisting>
-  </para>
-
-<!## PG>
-<!-- NOTICE:
-     current XC does not support DAFAULT with non-immutable functions.
--->
-  <para>
-   Assign a literal constant default value for the column
-   <literal>name</literal>, arrange for the default value of column
-   <literal>did</literal> to be generated by selecting the next value
-   of a sequence object, and make the default value of
-   <literal>modtime</literal> be the time at which the row is
-   inserted:
-
-<programlisting>
-CREATE TABLE distributors (
-    name      varchar(40) DEFAULT 'Luso Films',
-    did       integer DEFAULT nextval('distributors_serial'),
-    modtime   timestamp DEFAULT current_timestamp
-);
-</programlisting>
-  </para>
-<!## end>
-
-  <para>
-   Define two <literal>NOT NULL</> column constraints on the table
-   <classname>distributors</classname>, one of which is explicitly
-   given a name:
-
-<programlisting>
-CREATE TABLE distributors (
-    did     integer CONSTRAINT no_null NOT NULL,
-    name    varchar(40) NOT NULL
-);
-</programlisting>
-    </para>
-
-    <para>
-     Define a unique constraint for the <literal>name</literal> column:
-
-<programlisting>
-CREATE TABLE distributors (
-    did     integer,
-    name    varchar(40) UNIQUE
-);
-</programlisting>
-
-     The same, specified as a table constraint:
-
-<programlisting>
-CREATE TABLE distributors (
-    did     integer,
-    name    varchar(40),
-    UNIQUE(name)
-);
-</programlisting>
-  </para>
-
-  <para>
-   Create the same table, specifying 70% fill factor for both the table
-   and its unique index:
-
-<programlisting>
-CREATE TABLE distributors (
-    did     integer,
-    name    varchar(40),
-    UNIQUE(name) WITH (fillfactor=70)
-)
-WITH (fillfactor=70);
-</programlisting>
-  </para>
-
-  <para>
-   Create table <structname>circles</> with an exclusion
-   constraint that prevents any two circles from overlapping:
-
-<programlisting>
-CREATE TABLE circles (
-    c circle,
-    EXCLUDE USING gist (c WITH &amp;&amp;)
-);
-</programlisting>
-  </para>
-
-  <para>
-   Create table <structname>cinemas</> in tablespace <structname>diskvol1</>:
-
-<!## PG>
-<programlisting>
-CREATE TABLE cinemas (
-        id serial,
-        name text,
-        location text
-) TABLESPACE diskvol1;
-</programlisting>
-<!## end>
-<!## XC>
-<programlisting>
-CREATE TABLE cinemas (
-        id integer,
-        name text,
-        location text
-) TABLESPACE diskvol1;
-</programlisting>
-<!## end>
-<!## XL>
-<programlisting>
-CREATE TABLE cinemas (
-        id integer,
-        name text,
-        location text
-) TABLESPACE diskvol1;
-</programlisting>
-<!## end>
-  </para>
-
-  <para>
-   Create a composite type and a typed table:
-<programlisting>
-CREATE TYPE employee_type AS (name text, salary numeric);
-
-CREATE TABLE employees OF employee_type (
-    PRIMARY KEY (name),
-    salary WITH OPTIONS DEFAULT 1000
-);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATETABLE-compatibility">
-  <title id="SQL-CREATETABLE-compatibility-title">Compatibility</title>
-
-  <para>
-   The <command>CREATE TABLE</command> command conforms to the
-   <acronym>SQL</acronym> standard, with exceptions listed below.
-  </para>
-
-  <refsect2>
-   <title>Temporary Tables</title>
-
-   <para>
-    Although the syntax of <literal>CREATE TEMPORARY TABLE</literal>
-    resembles that of the SQL standard, the effect is not the same.  In the
-    standard,
-    temporary tables are defined just once and automatically exist (starting
-    with empty contents) in every session that needs them.
-<!## PG>
-    <productname>PostgreSQL</productname> instead
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> instead
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> instead
-<!## end>
-    requires each session to issue its own <literal>CREATE TEMPORARY
-    TABLE</literal> command for each temporary table to be used.  This allows
-    different sessions to use the same temporary table name for different
-    purposes, whereas the standard's approach constrains all instances of a
-    given temporary table name to have the same table structure.
-   </para>
-
-<!## PG>
-<!-- NOTICE:
-     Temporary table has not been supported yet!
--->
-   <para>
-    The standard's definition of the behavior of temporary tables is
-    widely ignored.  <productname>PostgreSQL</productname>'s behavior
-    on this point is similar to that of several other SQL databases.
-   </para>
-
-   <para>
-    The standard's distinction between global and local temporary tables
-    is not in <productname>PostgreSQL</productname>, since that distinction
-    depends on the concept of modules, which
-    <productname>PostgreSQL</productname> does not have.
-    For compatibility's sake, <productname>PostgreSQL</productname> will
-    accept the <literal>GLOBAL</literal> and <literal>LOCAL</literal> keywords
-    in a temporary table declaration, but they have no effect.
-   </para>
-<!## end>
-
-   <para>
-    The <literal>ON COMMIT</literal> clause for temporary tables
-    also resembles the SQL standard, but has some differences.
-    If the <literal>ON COMMIT</> clause is omitted, SQL specifies that the
-    default behavior is <literal>ON COMMIT DELETE ROWS</>.  However, the
-    default behavior in <productname>PostgreSQL</productname> is
-    <literal>ON COMMIT PRESERVE ROWS</literal>.  The <literal>ON COMMIT
-    DROP</literal> option does not exist in SQL.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Non-deferred Uniqueness Constraints</title>
-
-   <para>
-    When a <literal>UNIQUE</> or <literal>PRIMARY KEY</> constraint is
-<!## PG>
-    not deferrable, <productname>PostgreSQL</productname> checks for
-<!## end>
-<!## XC>
-    not deferrable, <productname>Postgres-XC</productname> checks for
-<!## end>
-<!## XL>
-    not deferrable, <productname>Postgres-XL</productname> checks for
-<!## end>
-    uniqueness immediately whenever a row is inserted or modified.
-    The SQL standard says that uniqueness should be enforced only at
-    the end of the statement; this makes a difference when, for example,
-    a single command updates multiple key values.  To obtain
-    standard-compliant behavior, declare the constraint as
-    <literal>DEFERRABLE</> but not deferred (i.e., <literal>INITIALLY
-    IMMEDIATE</>).  Be aware that this can be significantly slower than
-    immediate uniqueness checking.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Column Check Constraints</title>
-
-   <para>
-    The SQL standard says that <literal>CHECK</> column constraints
-    can only refer to the column they apply to; only <literal>CHECK</>
-    table constraints can refer to multiple columns.
-<!## PG>
-    <productname>PostgreSQL</productname> does not enforce this
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> does not enforce this
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> does not enforce this
-<!## end>
-    restriction; it treats column and table check constraints alike.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title><literal>EXCLUDE</literal> Constraint</title>
-
-   <para>
-    The <literal>EXCLUDE</> constraint type is a
-<!## PG>
-    <productname>PostgreSQL</productname> extension.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> extension.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> extension.
-<!## end>
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title><literal>NULL</literal> <quote>Constraint</quote></title>
-
-   <para>
-    The <literal>NULL</> <quote>constraint</quote> (actually a
-<!## PG>
-    non-constraint) is a <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-    non-constraint) is a <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-    non-constraint) is a <productname>Postgres-XL</productname>
-<!## end>
-    extension to the SQL standard that is included for compatibility with some
-    other database systems (and for symmetry with the <literal>NOT
-    NULL</literal> constraint).  Since it is the default for any
-    column, its presence is simply noise.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Inheritance</title>
-
-   <para>
-    Multiple inheritance via the <literal>INHERITS</literal> clause is
-<!## PG>
-    a <productname>PostgreSQL</productname> language extension.
-<!## end>
-<!## XC>
-    a <productname>Postgres-XC</productname> language extension.
-<!## end>
-<!## XL>
-    a <productname>Postgres-XL</productname> language extension.
-<!## end>
-    SQL:1999 and later define single inheritance using a
-    different syntax and different semantics.  SQL:1999-style
-    inheritance is not yet supported by
-<!## PG>
-    <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>.
-<!## end>
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Zero-column Tables</title>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> allows a table of no columns
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> allows a table of no columns
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> allows a table of no columns
-<!## end>
-    to be created (for example, <literal>CREATE TABLE foo();</>).  This
-    is an extension from the SQL standard, which does not allow zero-column
-    tables.  Zero-column tables are not in themselves very useful, but
-    disallowing them creates odd special cases for <command>ALTER TABLE
-    DROP COLUMN</>, so it seems cleaner to ignore this spec restriction.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title><literal>WITH</> Clause</title>
-
-   <para>
-<!## PG>
-    The <literal>WITH</> clause is a <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-    The <literal>WITH</> clause is a <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-    The <literal>WITH</> clause is a <productname>Postgres-XL</productname>
-<!## end>
-    extension; neither storage parameters nor OIDs are in the standard.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Tablespaces</title>
-
-   <para>
-<!## PG>
-    The <productname>PostgreSQL</productname> concept of tablespaces is not
-<!## end>
-<!## XC>
-    The <productname>Postgres-XC</productname> concept of tablespaces is not
-<!## end>
-<!## XL>
-    The <productname>Postgres-XL</productname> concept of tablespaces is not
-<!## end>
-    part of the standard.  Hence, the clauses <literal>TABLESPACE</literal>
-    and <literal>USING INDEX TABLESPACE</literal> are extensions.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Typed Tables</title>
-
-   <para>
-    Typed tables implement a subset of the SQL standard.  According to
-    the standard, a typed table has columns corresponding to the
-    underlying composite type as well as one other column that is
-<!## PG>
-    the <quote>self-referencing column</quote>.  PostgreSQL does not
-<!## end>
-<!## XC>
-    the <quote>self-referencing column</quote>.  Postgres-XC does not
-<!## end>
-<!## XL>
-    the <quote>self-referencing column</quote>.  Postgres-XL does not
-<!## end>
-    support these self-referencing columns explicitly, but the same
-    effect can be had using the OID feature.
-   </para>
-  </refsect2>
-
-<!## XC>
-  <refsect2>
-   <title><productname>Postgres-XC</> Specifics</title>
-
-&xconly;
-   <para>
-    So far, non-immutable functions are not allowed
-    as <literal>DEFAULT</> values.
-   </para>
-   <para>
-    <literal>PRIMARY KEY</> and foreign key must include the
-    distribution column.
-   </para>
-   <para>
-    <literal>TEMP</> tables and exclusion constraint are not supported
-    yet.
-   </para>
-   <para>
-   </para>
-   <para>
-    In <productname>Postgres-XC</>, OID is kept locally in each
-    Datanode and Coordinator.  The OID value may inconsistent for rows
-    stored in different Datanodes.
-   </para>
-
-  </refsect2>
-    
-<!## end>
-<!## XL>
-  <refsect2>
-   <title><productname>Postgres-XL</> Specifics</title>
-
-&xlonly;
-   <para>
-    Currently, non-immutable functions are not allowed
-    as <literal>DEFAULT</> values.
-   </para>
-   <para>
-    <literal>PRIMARY KEY</> and foreign key must include the
-    distribution column.
-   </para>
-   <para>
-    <literal>TEMP</> tables and exclusion constraint are not supported
-    yet.
-   </para>
-   <para>
-   </para>
-   <para>
-    In <productname>Postgres-XL</>, OID is maintained locally in each
-    Datanode and Coordinator.  The OID value may be inconsistent for rows
-    stored in different Datanodes.
-   </para>
-
-  </refsect2>
-    
-<!## end>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertable"></member>
-   <member><xref linkend="sql-droptable"></member>
-   <member><xref linkend="sql-createtablespace"></member>
-   <member><xref linkend="sql-createtype"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_table_as.sgmlin b/doc-xc/src/sgml/ref/create_table_as.sgmlin
deleted file mode 100644
index 780ee3aea0..0000000000
--- a/doc-xc/src/sgml/ref/create_table_as.sgmlin
+++ /dev/null
@@ -1,613 +0,0 @@
-<!--
-doc/src/sgml/ref/create_table_as.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETABLEAS">
- <refmeta>
-  <refentrytitle>CREATE TABLE AS</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TABLE AS</refname>
-  <refpurpose>define a new table from the results of a query</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createtableas">
-  <primary>CREATE TABLE AS</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<!## PG>
-<synopsis>
-CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE <replaceable>table_name</replaceable>
-    [ (<replaceable>column_name</replaceable> [, ...] ) ]
-    [ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
-    [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
-    [ TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-    AS <replaceable>query</replaceable>
-    [ WITH [ NO ] DATA ]
-</synopsis>
-<!## end>
-<!## XC>
-<synopsis>
-CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE <replaceable>table_name</replaceable>
-    [ (<replaceable>column_name</replaceable> [, ...] ) ]
-    [ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
-    [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
-    [ TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-    [ DISTRIBUTE BY { REPLICATION | ROUNDROBIN | { [HASH | MODULO ] ( <replaceable class="PARAMETER">column_name</replaceable> ) } } ]
-    [ TO { GROUP <replaceable class="PARAMETER">groupname</replaceable> | NODE ( <replaceable class="PARAMETER">nodename</replaceable> [, ... ] ) } ]
-    AS <replaceable>query</replaceable>
-    [ WITH [ NO ] DATA ]
-</synopsis>
-<!## end>
-<!## XL>
-<synopsis>
-CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE <replaceable>table_name</replaceable>
-    [ (<replaceable>column_name</replaceable> [, ...] ) ]
-    [ WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
-    [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
-    [ TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable> ]
-    [ DISTRIBUTE BY { REPLICATION | ROUNDROBIN | { [HASH | MODULO ] ( <replaceable class="PARAMETER">column_name</replaceable> ) } } ]
-    [ TO { GROUP <replaceable class="PARAMETER">groupname</replaceable> | NODE ( <replaceable class="PARAMETER">nodename</replaceable> [, ... ] ) } ]
-    AS <replaceable>query</replaceable>
-    [ WITH [ NO ] DATA ]
-</synopsis>
-<!## end>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>CREATE TABLE AS</command> creates a table and fills it
-   with data computed by a <command>SELECT</command> command.
-   The table columns have the
-   names and data types associated with the output columns of the
-   <command>SELECT</command> (except that you can override the column
-   names by giving an explicit list of new column names).
-  </para>
-
-  <para>
-   <command>CREATE TABLE AS</command> bears some resemblance to
-   creating a view, but it is really quite different: it creates a new
-   table and evaluates the query just once to fill the new table
-   initially.  The new table will not track subsequent changes to the
-   source tables of the query.  In contrast, a view re-evaluates its
-   defining <command>SELECT</command> statement whenever it is
-   queried.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>GLOBAL</literal> or <literal>LOCAL</literal></term>
-    <listitem>
-     <para>
-      Ignored for compatibility. Refer to <xref
-      linkend="sql-createtable"> for
-      details.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>TEMPORARY</> or <literal>TEMP</></term>
-    <listitem>
-     <para>
-      If specified, the table is created as a temporary table.
-      Refer to <xref linkend="sql-createtable"> for details.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>UNLOGGED</></term>
-    <listitem>
-     <para>
-      If specified, the table is created as an unlogged table.
-      Refer to <xref linkend="sql-createtable"> for details.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>table_name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the table to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>column_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of a column in the new table.  If column names are not
-      provided, they are taken from the output column names of the
-      query.  If the table is created from an
-      <command>EXECUTE</command> command, a column name list cannot be
-      specified.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>WITH ( <replaceable class="PARAMETER">storage_parameter</replaceable> [= <replaceable class="PARAMETER">value</replaceable>] [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      This clause specifies optional storage parameters for the new table;
-      see <xref linkend="sql-createtable-storage-parameters"
-      endterm="sql-createtable-storage-parameters-title"> for more
-      information.  The <literal>WITH</> clause
-      can also include <literal>OIDS=TRUE</> (or just <literal>OIDS</>)
-      to specify that rows of the new table
-      should have OIDs (object identifiers) assigned to them, or
-      <literal>OIDS=FALSE</> to specify that the rows should not have OIDs.
-      See <xref linkend="sql-createtable"> for more information.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>WITH OIDS</></term>
-    <term><literal>WITHOUT OIDS</></term>
-    <listitem>
-     <para>
-      These are obsolescent syntaxes equivalent to <literal>WITH (OIDS)</>
-      and <literal>WITH (OIDS=FALSE)</>, respectively.  If you wish to give
-      both an <literal>OIDS</> setting and storage parameters, you must use
-      the <literal>WITH ( ... )</> syntax; see above.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ON COMMIT</literal></term>
-    <listitem>
-     <para>
-      The behavior of temporary tables at the end of a transaction
-      block can be controlled using <literal>ON COMMIT</literal>.
-      The three options are:
-
-      <variablelist>
-       <varlistentry>
-        <term><literal>PRESERVE ROWS</literal></term>
-        <listitem>
-         <para>
-          No special action is taken at the ends of transactions.
-          This is the default behavior.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>DELETE ROWS</literal></term>
-        <listitem>
-         <para>
-          All rows in the temporary table will be deleted at the end
-          of each transaction block.  Essentially, an automatic <xref
-          linkend="sql-truncate"> is done
-          at each commit.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>DROP</literal></term>
-        <listitem>
-         <para>
-          The temporary table will be dropped at the end of the current
-          transaction block.
-         </para>
-        </listitem>
-       </varlistentry>
-      </variablelist>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TABLESPACE <replaceable class="PARAMETER">tablespace</replaceable></literal></term>
-    <listitem>
-     <para>
-      The <replaceable class="PARAMETER">tablespace</replaceable> is the name
-      of the tablespace in which the new table is to be created.
-      If not specified,
-      <xref linkend="guc-default-tablespace"> is consulted, or
-      <xref linkend="guc-temp-tablespaces"> if the table is temporary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-<!## XC>
-   <varlistentry>
-    <term><literal>DISTRIBUTE BY</literal></term>
-    <listitem>
-&xconly;
-     <para>
-      This clause specifies how the table is distributed or replicated among Datanodes.
-     </para>
-
-      <variablelist>
-
-       <varlistentry>
-        <term><literal>REPLICATION</literal></term>
-        <listitem>
-         <para>
-          Each row of the table will be replicated into all the
-          Datanode of the <productname>Postgres-XC</> database
-          cluster.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>ROUNDROBIN</literal></term>
-        <listitem>
-         <para>
-          Each row of the table will be placed in one of the Datanodes
-          by round-robin manner.  The value of the row will not be
-          needed to determine what Datanode to go.
-         </para>
-        </listitem>
-       </varlistentry>
-
-      <varlistentry>
-       <term><literal>HASH ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the hash value
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>MODULO ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the modulo
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-    <para>
-     If <literal>DISTRIBUTE BY</> is not specified, columns with
-     UNIQUE constraint will be chosen as the distribution key.  If no
-     such column is specified, distribution column is the first
-     eligible column in the definition.  If no such column is found,
-     then the table will be distributed by <literal>ROUNDROBIN</>.
-    </para>
-
-   </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TO GROUP</literal></term>
-    <term><literal>TO NODE</literal></term>
-      <listitem>
-       <para>
-        This defines on the list of nodes on which table data exists.
-        If this is not specified table data is present on all Datanodes.
-       </para>
-      </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">nodename</replaceable></term>
-      <listitem>
-       <para>
-        Associated with <literal>TO NODE</literal>, it defines a <productname>
-        Postgres-XC</productname> node of catalog pgxc_node.
-       </para>
-      </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">groupname</replaceable></term>
-      <listitem>
-       <para>
-        Associated with <literal>TO GROUP</literal>, it defines a <productname>
-        Postgres-XC</productname> node group in catalog pgxc_group.
-       </para>
-      </listitem>
-   </varlistentry>
-<!## end>
-<!## XL>
-   <varlistentry>
-    <term><literal>DISTRIBUTE BY</literal></term>
-    <listitem>
-&xlonly;
-     <para>
-      This clause specifies how the table is distributed or replicated among Datanodes.
-     </para>
-
-      <variablelist>
-
-       <varlistentry>
-        <term><literal>REPLICATION</literal></term>
-        <listitem>
-         <para>
-          Each row of the table will be replicated into all the
-          Datanode of the <productname>Postgres-XL</> database
-          cluster.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>ROUNDROBIN</literal></term>
-        <listitem>
-         <para>
-          Each row of the table will be placed in one of the Datanodes
-          by round-robin manner.  The value of the row will not be
-          needed to determine what Datanode to go.
-         </para>
-        </listitem>
-       </varlistentry>
-
-      <varlistentry>
-       <term><literal>HASH ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the hash value
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>MODULO ( <replaceable class="PARAMETER">column_name</> )</literal></term>
-       <listitem>
-        <para>
-         Each row of the table will be placed based on the modulo
-         of the specified column.  Following type is allowed as
-         distribution column: INT8, INT2, OID, INT4, BOOL, INT2VECTOR,
-         OIDVECTOR, CHAR, NAME, TEXT, BPCHAR, BYTEA, VARCHAR, FLOAT4,
-         FLOAT8, NUMERIC, CASH, ABSTIME, RELTIME, DATE, TIME,
-         TIMESTAMP, TIMESTAMPTZ, INTERVAL, and TIMETZ.
-        </para>
-        <para>
-         Please note that floating point is not allowed as a basis of
-         the distribution column.
-        </para>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-    <para>
-     If <literal>DISTRIBUTE BY</> is not specified, columns with
-     UNIQUE constraint will be chosen as the distribution key.  If no
-     such column is specified, distribution column is the first
-     eligible column in the definition.  If no such column is found,
-     then the table will be distributed by <literal>ROUNDROBIN</>.
-    </para>
-
-   </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TO GROUP</literal></term>
-    <term><literal>TO NODE</literal></term>
-      <listitem>
-       <para>
-        This defines on the list of nodes on which table data exists.
-        If this is not specified table data is present on all Datanodes.
-       </para>
-      </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">nodename</replaceable></term>
-      <listitem>
-       <para>
-        Associated with <literal>TO NODE</literal>, it defines a <productname>
-        Postgres-XL</productname> node of catalog pgxc_node.
-       </para>
-      </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">groupname</replaceable></term>
-      <listitem>
-       <para>
-        Associated with <literal>TO GROUP</literal>, it defines a <productname>
-        Postgres-XL</productname> node group in catalog pgxc_group.
-       </para>
-      </listitem>
-   </varlistentry>
-<!## end>
-
-   <varlistentry>
-    <term><replaceable>query</replaceable></term>
-    <listitem>
-     <para>
-      A <xref linkend="sql-select"
-     >, <link linkend="sql-table">TABLE</link>,
-      or
-      <xref linkend="sql-values"> command,
-      or an <xref linkend="sql-execute"> command
-      that runs a prepared <command>SELECT</>, <command>TABLE</>, or <command>VALUES</> query.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>WITH [ NO ] DATA</></term>
-    <listitem>
-     <para>
-      This clause specifies whether or not the data produced by the query
-      should be copied into the new table.  If not, only the table structure
-      is copied.  The default is to copy the data.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   This command is functionally similar to <xref
-   linkend="sql-selectinto">, but it is
-   preferred since it is less likely to be confused with other uses of
-   the <command>SELECT INTO</> syntax. Furthermore, <command>CREATE
-   TABLE AS</command> offers a superset of the functionality offered
-   by <command>SELECT INTO</command>.
-  </para>
-
-  <para>
-   Prior to <productname>PostgreSQL</productname> 8.0, <command>CREATE
-   TABLE AS</command> always included OIDs in the table it
-   created.  As of <productname>PostgreSQL</productname> 8.0,
-   the <command>CREATE TABLE AS</command> command allows the user to
-   explicitly specify whether OIDs should be included. If the
-   presence of OIDs is not explicitly specified,
-   the <xref linkend="guc-default-with-oids"> configuration variable is
-   used.  As of <productname>PostgreSQL</productname> 8.1,
-   this variable is false by default, so the default behavior is not
-   identical to pre-8.0 releases.  Applications that
-   require OIDs in the table created by <command>CREATE TABLE
-   AS</command> should explicitly specify <literal>WITH (OIDS)</literal>
-   to ensure proper behavior.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a new table <literal>films_recent</literal> consisting of only
-   recent entries from the table <literal>films</literal>:
-
-<programlisting>
-CREATE TABLE films_recent AS
-  SELECT * FROM films WHERE date_prod &gt;= '2002-01-01';
-</programlisting>
-  </para>
-
-  <para>
-   To copy a table completely, the short form using
-   the <literal>TABLE</literal> command can also be used:
-
-<programlisting>
-CREATE TABLE films2 AS
-  TABLE films;
-</programlisting>
-  </para>
-
-  <para>
-   Create a new temporary table <literal>films_recent</literal>, consisting of
-   only recent entries from the table <literal>films</literal>, using a
-   prepared statement.  The new table has OIDs and will be dropped at commit:
-
-<programlisting>
-PREPARE recentfilms(date) AS
-  SELECT * FROM films WHERE date_prod &gt; $1;
-CREATE TEMP TABLE films_recent WITH (OIDS) ON COMMIT DROP AS
-  EXECUTE recentfilms('2002-01-01');
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE TABLE AS</command> conforms to the <acronym>SQL</acronym>
-   standard.  The following are nonstandard extensions:
-
-   <itemizedlist spacing="compact">
-    <listitem>
-     <para>
-      The standard requires parentheses around the subquery clause; in
-      <productname>PostgreSQL</productname>, these parentheses are
-      optional.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In the standard, the <literal>WITH [ NO ] DATA</literal> clause
-      is required; in PostgreSQL it is optional.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <productname>PostgreSQL</> handles temporary tables in a way
-      rather different from the standard; see
-      <xref linkend="sql-createtable">
-      for details.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The <literal>WITH</> clause is a <productname>PostgreSQL</productname>
-      extension; neither storage parameters nor OIDs are in the standard.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The <productname>PostgreSQL</productname> concept of tablespaces is not
-      part of the standard.  Hence, the clause <literal>TABLESPACE</literal>
-      is an extension.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtable"></member>
-   <member><xref linkend="sql-execute"></member>
-   <member><xref linkend="sql-select"></member>
-   <member><xref linkend="sql-selectinto"></member>
-   <member><xref linkend="sql-values"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_tablespace.sgmlin b/doc-xc/src/sgml/ref/create_tablespace.sgmlin
deleted file mode 100644
index 9a3a08ec3a..0000000000
--- a/doc-xc/src/sgml/ref/create_tablespace.sgmlin
+++ /dev/null
@@ -1,196 +0,0 @@
-<!--
-doc/src/sgml/ref/create_tablespace.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETABLESPACE">
- <refmeta>
-  <refentrytitle>CREATE TABLESPACE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TABLESPACE</refname>
-  <refpurpose>define a new tablespace</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createtablespace">
-  <primary>CREATE TABLESPACE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE TABLESPACE <replaceable class="parameter">tablespace_name</replaceable> [ OWNER <replaceable class="parameter">user_name</replaceable> ] LOCATION '<replaceable class="parameter">directory</replaceable>'
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE TABLESPACE</command> registers a new cluster-wide
-   tablespace.  The tablespace name must be distinct from the name of any
-   existing tablespace in the database cluster.
-  </para>
-
-  <para>
-   A tablespace allows superusers to define an alternative location on
-   the file system where the data files containing database objects
-   (such as tables and indexes) can reside.
-  </para>
-
-  <para>
-   A user with appropriate privileges can pass
-   <replaceable class="parameter">tablespace_name</> to
-   <command>CREATE DATABASE</>, <command>CREATE TABLE</>,
-   <command>CREATE INDEX</> or <command>ADD CONSTRAINT</> to have the data
-   files for these objects stored within the specified tablespace.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">tablespace_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of a tablespace to be created.  The name cannot
-        begin with <literal>pg_</literal>, as such names
-        are reserved for system tablespaces.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">user_name</replaceable></term>
-      <listitem>
-       <para>
-        The name of the user who will own the tablespace.  If omitted,
-        defaults to the user executing the command.  Only superusers
-        can create tablespaces, but they can assign ownership of tablespaces
-        to non-superusers.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">directory</replaceable></term>
-      <listitem>
-       <para>
-        The directory that will be used for the tablespace. The directory
-        should be empty and must be owned by the
-<!## PG>
-        <productname>PostgreSQL</> system user.  The directory must be
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</> system user.  The directory must be
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</> system user.  The directory must be
-<!## end>
-        specified by an absolute path name.
-       </para>
-      </listitem>
-     </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Tablespaces are only supported on systems that support symbolic links.
-  </para>
-
-   <para>
-    <command>CREATE TABLESPACE</> cannot be executed inside a transaction
-    block.
-   </para>
-<!## XC>
-&xconly;
-   <para>
-    <productname>Postgres-XC</> assigns the same path to a tablespace
-    for all the Coordinators and Datanodes.  So when creating a tablespace,
-    user needs to have permission to the same location path on all the servers
-    involved in the cluster.
-   </para>
-
-   <para>
-    <command>CREATE TABLESPACE</> can be run with EXECUTE DIRECT to control
-    tablespace existence on remote nodes. This works for both remote Coordinators
-    and Datanodes but not on this operation is not authorized on node where
-    application client is connected.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    <productname>Postgres-XL</> assigns the same path to a tablespace
-    for all the Coordinators and Datanodes.  So when creating a tablespace,
-    user needs to have permission to the same location path on all the servers
-    involved in the cluster.
-   </para>
-
-   <para>
-    <command>CREATE TABLESPACE</> can be run with EXECUTE DIRECT to control
-    tablespace existence on remote nodes. This works for both remote Coordinators
-    and Datanodes but not on this operation is not authorized on node where
-    application client is connected.
-   </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a tablespace <literal>dbspace</> at <literal>/data/dbs</>:
-<programlisting>
-CREATE TABLESPACE dbspace LOCATION '/data/dbs';
-</programlisting>
-  </para>
-
-  <para>
-   Create a tablespace <literal>indexspace</> at <literal>/data/indexes</>
-   owned by user <literal>genevieve</>:
-<programlisting>
-CREATE TABLESPACE indexspace OWNER genevieve LOCATION '/data/indexes';
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-<!## PG>
-   <command>CREATE TABLESPACE</command> is a <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-   <command>CREATE TABLESPACE</command> is a <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-   <command>CREATE TABLESPACE</command> is a <productname>Postgres-XL</>
-<!## end>
-   extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createdatabase"></member>
-   <member><xref linkend="sql-createtable"></member>
-   <member><xref linkend="sql-createindex"></member>
-   <member><xref linkend="sql-droptablespace"></member>
-   <member><xref linkend="sql-altertablespace"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_trigger.sgmlin b/doc-xc/src/sgml/ref/create_trigger.sgmlin
deleted file mode 100644
index abc277cfb9..0000000000
--- a/doc-xc/src/sgml/ref/create_trigger.sgmlin
+++ /dev/null
@@ -1,583 +0,0 @@
-<!--
-doc/src/sgml/ref/create_trigger.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETRIGGER">
- <refmeta>
-  <refentrytitle>CREATE TRIGGER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TRIGGER</refname>
-  <refpurpose>define a new trigger</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createtrigger">
-  <primary>CREATE TRIGGER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE [ CONSTRAINT ] TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTER | INSTEAD OF } { <replaceable class="PARAMETER">event</replaceable> [ OR ... ] }
-    ON <replaceable class="PARAMETER">table</replaceable>
-    [ FROM <replaceable class="parameter">referenced_table_name</replaceable> ]
-    { NOT DEFERRABLE | [ DEFERRABLE ] { INITIALLY IMMEDIATE | INITIALLY DEFERRED } }
-    [ FOR [ EACH ] { ROW | STATEMENT } ]
-    [ WHEN ( <replaceable class="parameter">condition</replaceable> ) ]
-    EXECUTE PROCEDURE <replaceable class="PARAMETER">function_name</replaceable> ( <replaceable class="PARAMETER">arguments</replaceable> )
-
-<phrase>where <replaceable class="parameter">event</replaceable> can be one of:</phrase>
-
-    INSERT
-    UPDATE [ OF <replaceable class="parameter">column_name</replaceable> [, ... ] ]
-    DELETE
-    TRUNCATE
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>CREATE TRIGGER</> statement has not been supported
-   in <productname>Postgres-XC</> yet.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   The <command>CREATE TRIGGER</> statement is not yet supported
-   in <productname>Postgres-XL</>.
-  </para>
-<!## end>
-
-<!## PG>
-
-  <para>
-   <command>CREATE TRIGGER</command> creates a new trigger.  The
-   trigger will be associated with the specified table or view and will
-   execute the specified function <replaceable
-   class="parameter">function_name</replaceable> when certain events occur.
-  </para>
-
-  <para>
-   The trigger can be specified to fire before the
-   operation is attempted on a row (before constraints are checked and
-   the <command>INSERT</command>, <command>UPDATE</command>, or
-   <command>DELETE</command> is attempted); or after the operation has
-   completed (after constraints are checked and the
-   <command>INSERT</command>, <command>UPDATE</command>, or
-   <command>DELETE</command> has completed); or instead of the operation
-   (in the case of inserts, updates or deletes on a view).
-   If the trigger fires before or instead of the event, the trigger can skip
-   the operation for the current row, or change the row being inserted (for
-   <command>INSERT</command> and <command>UPDATE</command> operations
-   only). If the trigger fires after the event, all changes, including
-   the effects of other triggers, are <quote>visible</quote>
-   to the trigger.
-  </para>
-
-  <para>
-   A trigger that is marked <literal>FOR EACH ROW</literal> is called
-   once for every row that the operation modifies. For example, a
-   <command>DELETE</command> that affects 10 rows will cause any
-   <literal>ON DELETE</literal> triggers on the target relation to be
-   called 10 separate times, once for each deleted row. In contrast, a
-   trigger that is marked <literal>FOR EACH STATEMENT</literal> only
-   executes once for any given operation, regardless of how many rows
-   it modifies (in particular, an operation that modifies zero rows
-   will still result in the execution of any applicable <literal>FOR
-   EACH STATEMENT</literal> triggers).
-  </para>
-
-  <para>
-   Triggers that are specified to fire <literal>INSTEAD OF</> the trigger
-   event must be marked <literal>FOR EACH ROW</>, and can only be defined
-   on views. <literal>BEFORE</> and <literal>AFTER</> triggers on a view
-   must be marked as <literal>FOR EACH STATEMENT</>.
-  </para>
-
-  <para>
-   In addition, triggers may be defined to fire for
-   <command>TRUNCATE</command>, though only
-   <literal>FOR EACH STATEMENT</literal>.
-  </para>
-
-  <para>
-   The following table summarizes which types of triggers may be used on
-   tables and views:
-  </para>
-
-  <informaltable id="supported-trigger-types">
-   <tgroup cols="4">
-    <thead>
-     <row>
-      <entry>When</entry>
-      <entry>Event</entry>
-      <entry>Row-level</entry>
-      <entry>Statement-level</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry align="center" morerows="1"><literal>BEFORE</></entry>
-      <entry align="center"><command>INSERT</>/<command>UPDATE</>/<command>DELETE</></entry>
-      <entry align="center">Tables</entry>
-      <entry align="center">Tables and views</entry>
-     </row>
-     <row>
-      <entry align="center"><command>TRUNCATE</></entry>
-      <entry align="center">&mdash;</entry>
-      <entry align="center">Tables</entry>
-     </row>
-     <row>
-      <entry align="center" morerows="1"><literal>AFTER</></entry>
-      <entry align="center"><command>INSERT</>/<command>UPDATE</>/<command>DELETE</></entry>
-      <entry align="center">Tables</entry>
-      <entry align="center">Tables and views</entry>
-     </row>
-     <row>
-      <entry align="center"><command>TRUNCATE</></entry>
-      <entry align="center">&mdash;</entry>
-      <entry align="center">Tables</entry>
-     </row>
-     <row>
-      <entry align="center" morerows="1"><literal>INSTEAD OF</></entry>
-      <entry align="center"><command>INSERT</>/<command>UPDATE</>/<command>DELETE</></entry>
-      <entry align="center">Views</entry>
-      <entry align="center">&mdash;</entry>
-     </row>
-     <row>
-      <entry align="center"><command>TRUNCATE</></entry>
-      <entry align="center">&mdash;</entry>
-      <entry align="center">&mdash;</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </informaltable>
-
-  <para>
-   Also, a trigger definition can specify a Boolean <literal>WHEN</>
-   condition, which will be tested to see whether the trigger should
-   be fired.  In row-level triggers the <literal>WHEN</> condition can
-   examine the old and/or new values of columns of the row.  Statement-level
-   triggers can also have <literal>WHEN</> conditions, although the feature
-   is not so useful for them since the condition cannot refer to any values
-   in the table.
-  </para>
-
-  <para>
-   If multiple triggers of the same kind are defined for the same event,
-   they will be fired in alphabetical order by name.
-  </para>
-
-  <para>
-   When the <literal>CONSTRAINT</> option is specified, this command creates a
-   <firstterm>constraint trigger</>.  This is the same as a regular trigger
-   except that the timing of the trigger firing can be adjusted using
-   <xref linkend="SQL-SET-CONSTRAINTS">.
-   Constraint triggers must be <literal>AFTER ROW</> triggers.  They can
-   be fired either at the end of the statement causing the triggering event,
-   or at the end of the containing transaction; in the latter case they are
-   said to be <firstterm>deferred</>.  A pending deferred-trigger firing can
-   also be forced to happen immediately by using <command>SET CONSTRAINTS</>.
-   Constraint triggers are expected to raise an exception when the constraints
-   they implement are violated.
-  </para>
-
-  <para>
-   <command>SELECT</command> does not modify any rows so you cannot
-   create <command>SELECT</command> triggers. Rules and views are more
-   appropriate in such cases.
-  </para>
-
-  <para>
-   Refer to <xref linkend="triggers"> for more information about triggers.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name to give the new trigger.  This must be distinct from
-      the name of any other trigger for the same table.
-      The name cannot be schema-qualified &mdash; the trigger inherits the
-      schema of its table.  For a constraint trigger, this is also the name to
-      use when modifying the trigger's behavior using
-      <command>SET CONSTRAINTS</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>BEFORE</literal></term>
-    <term><literal>AFTER</literal></term>
-    <term><literal>INSTEAD OF</literal></term>
-    <listitem>
-     <para>
-      Determines whether the function is called before, after, or instead of
-      the event.  A constraint trigger can only be specified as
-      <literal>AFTER</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">event</replaceable></term>
-    <listitem>
-     <para>
-      One of <literal>INSERT</literal>, <literal>UPDATE</literal>,
-      <literal>DELETE</literal>, or <literal>TRUNCATE</literal>;
-      this specifies the event that will fire the trigger. Multiple
-      events can be specified using <literal>OR</literal>.
-     </para>
-
-     <para>
-      For <literal>UPDATE</literal> events, it is possible to
-      specify a list of columns using this syntax:
-<synopsis>
-UPDATE OF <replaceable>column_name1</replaceable> [, <replaceable>column_name2</replaceable> ... ]
-</synopsis>
-      The trigger will only fire if at least one of the listed columns
-      is mentioned as a target of the <command>UPDATE</> command.
-     </para>
-
-     <para>
-      <literal>INSTEAD OF UPDATE</> events do not support lists of columns.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">table</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the table or view the trigger
-      is for.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">referenced_table_name</replaceable></term>
-    <listitem>
-     <para>
-      The (possibly schema-qualified) name of another table referenced by the
-      constraint.  This option is used for foreign-key constraints and is not
-      recommended for general use.  This can only be specified for
-      constraint triggers.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DEFERRABLE</literal></term>
-    <term><literal>NOT DEFERRABLE</literal></term>
-    <term><literal>INITIALLY IMMEDIATE</literal></term>
-    <term><literal>INITIALLY DEFERRED</literal></term>
-    <listitem>
-     <para>
-      The default timing of the trigger.
-      See the <xref linkend="SQL-CREATETABLE"> documentation for details of
-      these constraint options.  This can only be specified for constraint
-      triggers.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>FOR EACH ROW</literal></term>
-    <term><literal>FOR EACH STATEMENT</literal></term>
-
-    <listitem>
-     <para>
-      This specifies whether the trigger procedure should be fired
-      once for every row affected by the trigger event, or just once
-      per SQL statement. If neither is specified, <literal>FOR EACH
-      STATEMENT</literal> is the default.  Constraint triggers can only
-      be specified <literal>FOR EACH ROW</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">condition</replaceable></term>
-    <listitem>
-     <para>
-      A Boolean expression that determines whether the trigger function
-      will actually be executed.  If <literal>WHEN</> is specified, the
-      function will only be called if the <replaceable
-      class="parameter">condition</replaceable> returns <literal>true</>.
-      In <literal>FOR EACH ROW</literal> triggers, the <literal>WHEN</>
-      condition can refer to columns of the old and/or new row values
-      by writing <literal>OLD.<replaceable
-      class="parameter">column_name</replaceable></literal> or
-      <literal>NEW.<replaceable
-      class="parameter">column_name</replaceable></literal> respectively.
-      Of course, <literal>INSERT</> triggers cannot refer to <literal>OLD</>
-      and <literal>DELETE</> triggers cannot refer to <literal>NEW</>.
-     </para>
-
-     <para>
-      <literal>INSTEAD OF</> triggers do not support <literal>WHEN</>
-      conditions.
-     </para>
-
-     <para>
-      Currently, <literal>WHEN</literal> expressions cannot contain
-      subqueries.
-     </para>
-
-     <para>
-      Note that for constraint triggers, evaluation of the <literal>WHEN</>
-      condition is not deferred, but occurs immediately after the row update
-      operation is performed. If the condition does not evaluate to true then
-      the trigger is not queued for deferred execution.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">function_name</replaceable></term>
-    <listitem>
-     <para>
-      A user-supplied function that is declared as taking no arguments
-      and returning type <literal>trigger</>, which is executed when
-      the trigger fires.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">arguments</replaceable></term>
-    <listitem>
-     <para>
-      An optional comma-separated list of arguments to be provided to
-      the function when the trigger is executed.  The arguments are
-      literal string constants.  Simple names and numeric constants
-      can be written here, too, but they will all be converted to
-      strings.  Please check the description of the implementation
-      language of the trigger function to find out how these arguments
-      can be accessed within the function; it might be different from
-      normal function arguments.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1 id="SQL-CREATETRIGGER-notes">
-  <title>Notes</title>
-
-  <para>
-   To create a trigger on a table, the user must have the
-   <literal>TRIGGER</literal> privilege on the table.
-  </para>
-
-  <para>
-   Use <xref linkend="sql-droptrigger"> to remove a trigger.
-  </para>
-
-  <para>
-   A column-specific trigger (one defined using the <literal>UPDATE OF
-   <replaceable>column_name</replaceable></literal> syntax) will fire when any
-   of its columns are listed as targets in the <command>UPDATE</>
-   command's <literal>SET</> list.  It is possible for a column's value
-   to change even when the trigger is not fired, because changes made to the
-   row's contents by <literal>BEFORE UPDATE</> triggers are not considered.
-   Conversely, a command such as <literal>UPDATE ... SET x = x ...</>
-   will fire a trigger on column <literal>x</>, even though the column's
-   value did not change.
-  </para>
-
-  <para>
-   In a <literal>BEFORE</> trigger, the <literal>WHEN</> condition is
-   evaluated just before the function is or would be executed, so using
-   <literal>WHEN</> is not materially different from testing the same
-   condition at the beginning of the trigger function.  Note in particular
-   that the <literal>NEW</> row seen by the condition is the current value,
-   as possibly modified by earlier triggers.  Also, a <literal>BEFORE</>
-   trigger's <literal>WHEN</> condition is not allowed to examine the
-   system columns of the <literal>NEW</> row (such as <literal>oid</>),
-   because those won't have been set yet.
-  </para>
-
-  <para>
-   In an <literal>AFTER</> trigger, the <literal>WHEN</> condition is
-   evaluated just after the row update occurs, and it determines whether an
-   event is queued to fire the trigger at the end of statement.  So when an
-   <literal>AFTER</> trigger's <literal>WHEN</> condition does not return
-   true, it is not necessary to queue an event nor to re-fetch the row at end
-   of statement.  This can result in significant speedups in statements that
-   modify many rows, if the trigger only needs to be fired for a few of the
-   rows.
-  </para>
-
-  <para>
-   In <productname>PostgreSQL</productname> versions before 7.3, it was
-   necessary to declare trigger functions as returning the placeholder
-   type <type>opaque</>, rather than <type>trigger</>.  To support loading
-   of old dump files, <command>CREATE TRIGGER</> will accept a function
-   declared as returning <type>opaque</>, but it will issue a notice and
-   change the function's declared return type to <type>trigger</>.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATETRIGGER-examples">
-  <title>Examples</title>
-
-  <para>
-   Execute the function <function>check_account_update</> whenever
-   a row of the table <literal>accounts</> is about to be updated:
-
-<programlisting>
-CREATE TRIGGER check_update
-    BEFORE UPDATE ON accounts
-    FOR EACH ROW
-    EXECUTE PROCEDURE check_account_update();
-</programlisting>
-
-   The same, but only execute the function if column <literal>balance</>
-   is specified as a target in the <command>UPDATE</> command:
-
-<programlisting>
-CREATE TRIGGER check_update
-    BEFORE UPDATE OF balance ON accounts
-    FOR EACH ROW
-    EXECUTE PROCEDURE check_account_update();
-</programlisting>
-
-   This form only executes the function if column <literal>balance</>
-   has in fact changed value:
-
-<programlisting>
-CREATE TRIGGER check_update
-    BEFORE UPDATE ON accounts
-    FOR EACH ROW
-    WHEN (OLD.balance IS DISTINCT FROM NEW.balance)
-    EXECUTE PROCEDURE check_account_update();
-</programlisting>
-
-   Call a function to log updates of <literal>accounts</>, but only if
-   something changed:
-
-<programlisting>
-CREATE TRIGGER log_update
-    AFTER UPDATE ON accounts
-    FOR EACH ROW
-    WHEN (OLD.* IS DISTINCT FROM NEW.*)
-    EXECUTE PROCEDURE log_account_update();
-</programlisting>
-
-   Execute the function <function>view_insert_row</> for each row to insert
-   rows into the tables underlying a view:
-
-<programlisting>
-CREATE TRIGGER view_insert
-    INSTEAD OF INSERT ON my_view
-    FOR EACH ROW
-    EXECUTE PROCEDURE view_insert_row();
-</programlisting>
-  </para>
-
-  <para>
-   <xref linkend="trigger-example"> contains a complete example of a trigger
-   function written in C.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATETRIGGER-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   The <command>CREATE TRIGGER</command> statement in
-   <productname>PostgreSQL</productname> implements a subset of the
-   <acronym>SQL</> standard. The following functionality is currently missing:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      SQL allows you to define aliases for the <quote>old</quote>
-      and <quote>new</quote> rows or tables for use in the definition
-      of the triggered action (e.g., <literal>CREATE TRIGGER ... ON
-      tablename REFERENCING OLD ROW AS somename NEW ROW AS othername
-      ...</literal>).  Since <productname>PostgreSQL</productname>
-      allows trigger procedures to be written in any number of
-      user-defined languages, access to the data is handled in a
-      language-specific way.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <productname>PostgreSQL</productname> only allows the execution
-      of a user-defined function for the triggered action.  The standard
-      allows the execution of a number of other SQL commands, such as
-      <command>CREATE TABLE</command>, as the triggered action.  This
-      limitation is not hard to work around by creating a user-defined
-      function that executes the desired commands.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-  </para>
-
-  <para>
-   SQL specifies that multiple triggers should be fired in
-   time-of-creation order.  <productname>PostgreSQL</productname> uses
-   name order, which was judged to be more convenient.
-  </para>
-
-  <para>
-   SQL specifies that <literal>BEFORE DELETE</literal> triggers on cascaded
-   deletes fire <emphasis>after</> the cascaded <literal>DELETE</> completes.
-   The <productname>PostgreSQL</productname> behavior is for <literal>BEFORE
-   DELETE</literal> to always fire before the delete action, even a cascading
-   one.  This is considered more consistent.  There is also nonstandard
-   behavior if <literal>BEFORE</literal> triggers modify rows or prevent
-   updates during an update that is caused by a referential action.  This can
-   lead to constraint violations or stored data that does not honor the
-   referential constraint.
-  </para>
-
-  <para>
-   The ability to specify multiple actions for a single trigger using
-   <literal>OR</literal> is a <productname>PostgreSQL</> extension of
-   the SQL standard.
-  </para>
-
-  <para>
-   The ability to fire triggers for <command>TRUNCATE</command> is a
-   <productname>PostgreSQL</> extension of the SQL standard, as is the
-   ability to define statement-level triggers on views.
-  </para>
-
-  <para>
-   <command>CREATE CONSTRAINT TRIGGER</command> is a
-   <productname>PostgreSQL</productname> extension of the <acronym>SQL</>
-   standard.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createfunction"></member>
-   <member><xref linkend="sql-altertrigger"></member>
-   <member><xref linkend="sql-droptrigger"></member>
-   <member><xref linkend="sql-set-constraints"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_tsconfig.sgmlin b/doc-xc/src/sgml/ref/create_tsconfig.sgmlin
deleted file mode 100644
index fe7a21f25c..0000000000
--- a/doc-xc/src/sgml/ref/create_tsconfig.sgmlin
+++ /dev/null
@@ -1,128 +0,0 @@
-<!--
-doc/src/sgml/ref/create_tsconfig.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETSCONFIG">
- <refmeta>
-  <refentrytitle>CREATE TEXT SEARCH CONFIGURATION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TEXT SEARCH CONFIGURATION</refname>
-  <refpurpose>define a new text search configuration</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createtsconfig">
-  <primary>CREATE TEXT SEARCH CONFIGURATION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE TEXT SEARCH CONFIGURATION <replaceable class="parameter">name</replaceable> (
-    PARSER = <replaceable class="parameter">parser_name</replaceable> |
-    COPY = <replaceable class="parameter">source_config</replaceable>
-)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE TEXT SEARCH CONFIGURATION</command> creates a new text
-   search configuration.  A text search configuration specifies a text
-   search parser that can divide a string into tokens, plus dictionaries
-   that can be used to determine which tokens are of interest for searching.
-  </para>
-
-  <para>
-   If only the parser is specified, then the new text search configuration
-   initially has no mappings from token types to dictionaries, and therefore
-   will ignore all words.  Subsequent <command>ALTER TEXT SEARCH
-   CONFIGURATION</command> commands must be used to create mappings to
-   make the configuration useful.  Alternatively, an existing text search
-   configuration can be copied.
-  </para>
-
-  <para>
-   If a schema name is given then the text search configuration is created in
-   the specified schema.  Otherwise it is created in the current schema.
-  </para>
-
-  <para>
-   The user who defines a text search configuration becomes its owner.
-  </para>
-
-  <para>
-   Refer to <xref linkend="textsearch"> for further information.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the text search configuration to be created.  The name can be
-      schema-qualified.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">parser_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the text search parser to use for this configuration.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">source_config</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing text search configuration to copy.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   The <literal>PARSER</> and <literal>COPY</> options are mutually
-   exclusive, because when an existing configuration is copied, its
-   parser selection is copied too.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>CREATE TEXT SEARCH CONFIGURATION</command> statement
-   in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertsconfig"></member>
-   <member><xref linkend="sql-droptsconfig"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_tsdictionary.sgmlin b/doc-xc/src/sgml/ref/create_tsdictionary.sgmlin
deleted file mode 100644
index b006b707f6..0000000000
--- a/doc-xc/src/sgml/ref/create_tsdictionary.sgmlin
+++ /dev/null
@@ -1,143 +0,0 @@
-<!--
-doc/src/sgml/ref/create_tsdictionary.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETSDICTIONARY">
- <refmeta>
-  <refentrytitle>CREATE TEXT SEARCH DICTIONARY</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TEXT SEARCH DICTIONARY</refname>
-  <refpurpose>define a new text search dictionary</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createtsdictionary">
-  <primary>CREATE TEXT SEARCH DICTIONARY</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE TEXT SEARCH DICTIONARY <replaceable class="parameter">name</replaceable> (
-    TEMPLATE = <replaceable class="parameter">template</replaceable>
-    [, <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">value</replaceable> [, ... ]]
-)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE TEXT SEARCH DICTIONARY</command> creates a new text search
-   dictionary.  A text search dictionary specifies a way of recognizing
-   interesting or uninteresting words for searching.  A dictionary depends
-   on a text search template, which specifies the functions that actually
-   perform the work.  Typically the dictionary provides some options that
-   control the detailed behavior of the template's functions.
-  </para>
-
-  <para>
-   If a schema name is given then the text search dictionary is created in the
-   specified schema.  Otherwise it is created in the current schema.
-  </para>
-
-  <para>
-   The user who defines a text search dictionary becomes its owner.
-  </para>
-
-  <para>
-   Refer to <xref linkend="textsearch"> for further information.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the text search dictionary to be created.  The name can be
-      schema-qualified.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">template</replaceable></term>
-    <listitem>
-     <para>
-      The name of the text search template that will define the basic
-      behavior of this dictionary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">option</replaceable></term>
-    <listitem>
-     <para>
-      The name of a template-specific option to be set for this dictionary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">value</replaceable></term>
-    <listitem>
-     <para>
-      The value to use for a template-specific option.  If the value
-      is not a simple identifier or number, it must be quoted (but you can
-      always quote it, if you wish).
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   The options can appear in any order.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   The following example command creates a Snowball-based dictionary
-   with a nonstandard list of stop words.
-  </para>
-
-<programlisting>
-CREATE TEXT SEARCH DICTIONARY my_russian (
-    template = snowball,
-    language = russian,
-    stopwords = myrussian
-);
-</programlisting>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>CREATE TEXT SEARCH DICTIONARY</command> statement in
-   the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertsdictionary"></member>
-   <member><xref linkend="sql-droptsdictionary"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_tsparser.sgmlin b/doc-xc/src/sgml/ref/create_tsparser.sgmlin
deleted file mode 100644
index 19c878ea5e..0000000000
--- a/doc-xc/src/sgml/ref/create_tsparser.sgmlin
+++ /dev/null
@@ -1,155 +0,0 @@
-<!--
-doc/src/sgml/ref/create_tsparser.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETSPARSER">
- <refmeta>
-  <refentrytitle>CREATE TEXT SEARCH PARSER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TEXT SEARCH PARSER</refname>
-  <refpurpose>define a new text search parser</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createtsparser">
-  <primary>CREATE TEXT SEARCH PARSER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE TEXT SEARCH PARSER <replaceable class="parameter">name</replaceable> (
-    START = <replaceable class="parameter">start_function</replaceable> ,
-    GETTOKEN = <replaceable class="parameter">gettoken_function</replaceable> ,
-    END = <replaceable class="parameter">end_function</replaceable> ,
-    LEXTYPES = <replaceable class="parameter">lextypes_function</replaceable>
-    [, HEADLINE = <replaceable class="parameter">headline_function</replaceable> ]
-)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE TEXT SEARCH PARSER</command> creates a new text search
-   parser.  A text search parser defines a method for splitting a text
-   string into tokens and assigning types (categories) to the tokens.
-   A parser is not particularly useful by itself, but must be bound into a
-   text search configuration along with some text search dictionaries
-   to be used for searching.
-  </para>
-
-  <para>
-   If a schema name is given then the text search parser is created in the
-   specified schema.  Otherwise it is created in the current schema.
-  </para>
-
-  <para>
-   You must be a superuser to use <command>CREATE TEXT SEARCH PARSER</command>.
-   (This restriction is made because an erroneous text search parser
-   definition could confuse or even crash the server.)
-  </para>
-
-  <para>
-   Refer to <xref linkend="textsearch"> for further information.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the text search parser to be created.  The name can be
-      schema-qualified.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">start_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of the start function for the parser.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">gettoken_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of the get-next-token function for the parser.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">end_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of the end function for the parser.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">lextypes_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of the lextypes function for the parser (a function that
-      returns information about the set of token types it produces).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">headline_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of the headline function for the parser (a function that
-      summarizes a set of tokens).
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   The function names can be schema-qualified if necessary.  Argument types
-   are not given, since the argument list for each type of function is
-   predetermined.  All except the headline function are required.
-  </para>
-
-  <para>
-   The arguments can appear in any order, not only the one shown above.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no
-   <command>CREATE TEXT SEARCH PARSER</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertsparser"></member>
-   <member><xref linkend="sql-droptsparser"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_tstemplate.sgmlin b/doc-xc/src/sgml/ref/create_tstemplate.sgmlin
deleted file mode 100644
index cb2422b7f2..0000000000
--- a/doc-xc/src/sgml/ref/create_tstemplate.sgmlin
+++ /dev/null
@@ -1,128 +0,0 @@
-<!--
-doc/src/sgml/ref/create_tstemplate.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETSTEMPLATE">
- <refmeta>
-  <refentrytitle>CREATE TEXT SEARCH TEMPLATE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TEXT SEARCH TEMPLATE</refname>
-  <refpurpose>define a new text search template</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createtstemplate">
-  <primary>CREATE TEXT SEARCH TEMPLATE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE TEXT SEARCH TEMPLATE <replaceable class="parameter">name</replaceable> (
-    [ INIT = <replaceable class="parameter">init_function</replaceable> , ]
-    LEXIZE = <replaceable class="parameter">lexize_function</replaceable>
-)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE TEXT SEARCH TEMPLATE</command> creates a new text search
-   template.  Text search templates define the functions that implement
-   text search dictionaries.  A template is not useful by itself, but must
-   be instantiated as a dictionary to be used.  The dictionary typically
-   specifies parameters to be given to the template functions.
-  </para>
-
-  <para>
-   If a schema name is given then the text search template is created in the
-   specified schema.  Otherwise it is created in the current schema.
-  </para>
-
-  <para>
-   You must be a superuser to use <command>CREATE TEXT SEARCH
-   TEMPLATE</command>.  This restriction is made because an erroneous text
-   search template definition could confuse or even crash the server.
-   The reason for separating templates from dictionaries is that a template
-   encapsulates the <quote>unsafe</> aspects of defining a dictionary.
-   The parameters that can be set when defining a dictionary are safe for
-   unprivileged users to set, and so creating a dictionary need not be a
-   privileged operation.
-  </para>
-
-  <para>
-   Refer to <xref linkend="textsearch"> for further information.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the text search template to be created.  The name can be
-      schema-qualified.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">init_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of the init function for the template.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">lexize_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of the lexize function for the template.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   The function names can be schema-qualified if necessary.  Argument types
-   are not given, since the argument list for each type of function is
-   predetermined.  The lexize function is required, but the init function
-   is optional.
-  </para>
-
-  <para>
-   The arguments can appear in any order, not only the one shown above.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no
-   <command>CREATE TEXT SEARCH TEMPLATE</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertstemplate"></member>
-   <member><xref linkend="sql-droptstemplate"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_type.sgmlin b/doc-xc/src/sgml/ref/create_type.sgmlin
deleted file mode 100644
index 22d594d20c..0000000000
--- a/doc-xc/src/sgml/ref/create_type.sgmlin
+++ /dev/null
@@ -1,887 +0,0 @@
-<!--
-doc/src/sgml/ref/create_type.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETYPE">
- <refmeta>
-  <refentrytitle>CREATE TYPE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TYPE</refname>
-  <refpurpose>define a new data type</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createtype">
-  <primary>CREATE TYPE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE TYPE <replaceable class="parameter">name</replaceable> AS
-    ( [ <replaceable class="PARAMETER">attribute_name</replaceable> <replaceable class="PARAMETER">data_type</replaceable> [ COLLATE <replaceable>collation</replaceable> ] [, ... ] ] )
-
-CREATE TYPE <replaceable class="parameter">name</replaceable> AS ENUM
-    ( [ '<replaceable class="parameter">label</replaceable>' [, ... ] ] )
-
-CREATE TYPE <replaceable class="parameter">name</replaceable> (
-    INPUT = <replaceable class="parameter">input_function</replaceable>,
-    OUTPUT = <replaceable class="parameter">output_function</replaceable>
-    [ , RECEIVE = <replaceable class="parameter">receive_function</replaceable> ]
-    [ , SEND = <replaceable class="parameter">send_function</replaceable> ]
-    [ , TYPMOD_IN = <replaceable class="parameter">type_modifier_input_function</replaceable> ]
-    [ , TYPMOD_OUT = <replaceable class="parameter">type_modifier_output_function</replaceable> ]
-    [ , ANALYZE = <replaceable class="parameter">analyze_function</replaceable> ]
-    [ , INTERNALLENGTH = { <replaceable class="parameter">internallength</replaceable> | VARIABLE } ]
-    [ , PASSEDBYVALUE ]
-    [ , ALIGNMENT = <replaceable class="parameter">alignment</replaceable> ]
-    [ , STORAGE = <replaceable class="parameter">storage</replaceable> ]
-    [ , LIKE = <replaceable class="parameter">like_type</replaceable> ]
-    [ , CATEGORY = <replaceable class="parameter">category</replaceable> ]
-    [ , PREFERRED = <replaceable class="parameter">preferred</replaceable> ]
-    [ , DEFAULT = <replaceable class="parameter">default</replaceable> ]
-    [ , ELEMENT = <replaceable class="parameter">element</replaceable> ]
-    [ , DELIMITER = <replaceable class="parameter">delimiter</replaceable> ]
-    [ , COLLATABLE = <replaceable class="parameter">collatable</replaceable> ]
-)
-
-CREATE TYPE <replaceable class="parameter">name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE TYPE</command> registers a new data type for use in
-   the current database.  The user who defines a type becomes its
-   owner.
-  </para>
-
-  <para>
-   If a schema name is given then the type is created in the specified
-   schema.  Otherwise it is created in the current schema.  The type
-   name must be distinct from the name of any existing type or domain
-   in the same schema.  (Because tables have associated data types,
-   the type name must also be distinct from the name of any existing
-   table in the same schema.)
-  </para>
-
-  <refsect2>
-   <title>Composite Types</title>
-
-  <para>
-   The first form of <command>CREATE TYPE</command>
-   creates a composite type.
-   The composite type is specified by a list of attribute names and data types.
-   An attribute's collation can be specified too, if its data type is
-   collatable.  A composite type is essentially the same as the row type
-   of a table, but using <command>CREATE TYPE</command> avoids the need to
-   create an actual table when all that is wanted is to define a type.
-   A stand-alone composite type is useful, for example, as the argument or
-   return type of a function.
-  </para>
-  </refsect2>
-
-  <refsect2 id="SQL-CREATETYPE-enum">
-   <title>Enumerated Types</title>
-
-   <para>
-    The second form of <command>CREATE TYPE</command> creates an enumerated
-    (enum) type, as described in <xref linkend="datatype-enum">.
-    Enum types take a list of one or more quoted labels, each of which
-    must be less than <symbol>NAMEDATALEN</symbol> bytes long (64 in a standard
-<!## PG>
-    <productname>PostgreSQL</productname> build).
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> build).
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> build).
-<!## end>
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Base Types</title>
-
-  <para>
-   The third form of <command>CREATE TYPE</command> creates a new base type
-   (scalar type).  To create a new base type, you must be a superuser.
-   (This restriction is made because an erroneous type definition could
-   confuse or even crash the server.)
-  </para>
-
-  <para>
-   The parameters can appear in any order, not only that
-   illustrated above, and most are optional.  You must register
-   two or more functions (using <command>CREATE FUNCTION</command>) before
-   defining the type.  The support functions
-   <replaceable class="parameter">input_function</replaceable> and
-   <replaceable class="parameter">output_function</replaceable>
-   are required, while the functions
-   <replaceable class="parameter">receive_function</replaceable>,
-   <replaceable class="parameter">send_function</replaceable>,
-   <replaceable class="parameter">type_modifier_input_function</replaceable>,
-   <replaceable class="parameter">type_modifier_output_function</replaceable> and
-   <replaceable class="parameter">analyze_function</replaceable>
-   are optional.  Generally these functions have to be coded in C
-   or another low-level language.
-  </para>
-
-  <para>
-   The <replaceable class="parameter">input_function</replaceable>
-   converts the type's external textual representation to the internal
-   representation used by the operators and functions defined for the type.
-   <replaceable class="parameter">output_function</replaceable>
-   performs the reverse transformation.  The input function can be
-   declared as taking one argument of type <type>cstring</type>,
-   or as taking three arguments of types
-   <type>cstring</type>, <type>oid</type>, <type>integer</type>.
-   The first argument is the input text as a C string, the second
-   argument is the type's own OID (except for array types, which instead
-   receive their element type's OID),
-   and the third is the <literal>typmod</> of the destination column, if known
-   (-1 will be passed if not).
-   The input function must return a value of the data type itself.
-   Usually, an input function should be declared STRICT; if it is not,
-   it will be called with a NULL first parameter when reading a NULL
-   input value.  The function must still return NULL in this case, unless
-   it raises an error.
-   (This case is mainly meant to support domain input functions, which
-   might need to reject NULL inputs.)
-   The output function must be
-   declared as taking one argument of the new data type.
-   The output function must return type <type>cstring</type>.
-   Output functions are not invoked for NULL values.
-  </para>
-
-  <para>
-   The optional <replaceable class="parameter">receive_function</replaceable>
-   converts the type's external binary representation to the internal
-   representation.  If this function is not supplied, the type cannot
-   participate in binary input.  The binary representation should be
-   chosen to be cheap to convert to internal form, while being reasonably
-   portable.  (For example, the standard integer data types use network
-   byte order as the external binary representation, while the internal
-   representation is in the machine's native byte order.)  The receive
-   function should perform adequate checking to ensure that the value is
-   valid.
-   The receive function can be declared as taking one argument of type
-   <type>internal</type>, or as taking three arguments of types
-   <type>internal</type>, <type>oid</type>, <type>integer</type>.
-   The first argument is a pointer to a <type>StringInfo</type> buffer
-   holding the received byte string; the optional arguments are the
-   same as for the text input function.
-   The receive function must return a value of the data type itself.
-   Usually, a receive function should be declared STRICT; if it is not,
-   it will be called with a NULL first parameter when reading a NULL
-   input value.  The function must still return NULL in this case, unless
-   it raises an error.
-   (This case is mainly meant to support domain receive functions, which
-   might need to reject NULL inputs.)
-   Similarly, the optional
-   <replaceable class="parameter">send_function</replaceable> converts
-   from the internal representation to the external binary representation.
-   If this function is not supplied, the type cannot participate in binary
-   output.  The send function must be
-   declared as taking one argument of the new data type.
-   The send function must return type <type>bytea</type>.
-   Send functions are not invoked for NULL values.
-  </para>
-
-  <para>
-   You should at this point be wondering how the input and output functions
-   can be declared to have results or arguments of the new type, when they
-   have to be created before the new type can be created.  The answer is that
-   the type should first be defined as a <firstterm>shell type</>, which is a
-   placeholder type that has no properties except a name and an owner.  This
-   is done by issuing the command <literal>CREATE TYPE
-   <replaceable>name</></literal>, with no additional parameters.  Then the
-   I/O functions can be defined referencing the shell type.  Finally,
-   <command>CREATE TYPE</> with a full definition replaces the shell entry
-   with a complete, valid type definition, after which the new type can be
-   used normally.
-  </para>
-
-  <para>
-   The optional
-   <replaceable class="parameter">type_modifier_input_function</replaceable>
-   and <replaceable class="parameter">type_modifier_output_function</replaceable>
-   are needed if the type supports modifiers, that is optional constraints
-   attached to a type declaration, such as <literal>char(5)</> or
-<!## PG>
-   <literal>numeric(30,2)</>.  <productname>PostgreSQL</productname> allows
-<!## end>
-<!## XC>
-   <literal>numeric(30,2)</>.  <productname>Postgres-Xc</productname> allows
-<!## end>
-<!## XL>
-   <literal>numeric(30,2)</>.  <productname>Postgres-XL</productname> allows
-<!## end>
-   user-defined types to take one or more simple constants or identifiers as
-   modifiers.  However, this information must be capable of being packed into a
-   single non-negative integer value for storage in the system catalogs.  The
-   <replaceable class="parameter">type_modifier_input_function</replaceable>
-   is passed the declared modifier(s) in the form of a <type>cstring</>
-   array.  It must check the values for validity (throwing an error if they
-   are wrong), and if they are correct, return a single non-negative
-   <type>integer</> value that will be stored as the column <quote>typmod</>.
-   Type modifiers will be rejected if the type does not have a
-   <replaceable class="parameter">type_modifier_input_function</replaceable>.
-   The <replaceable class="parameter">type_modifier_output_function</replaceable>
-   converts the internal integer typmod value back to the correct form for
-   user display.  It must return a <type>cstring</> value that is the exact
-   string to append to the type name; for example <type>numeric</>'s
-   function might return <literal>(30,2)</>.
-   It is allowed to omit the
-   <replaceable class="parameter">type_modifier_output_function</replaceable>,
-   in which case the default display format is just the stored typmod integer
-   value enclosed in parentheses.
-  </para>
-
-  <para>
-   The optional <replaceable class="parameter">analyze_function</replaceable>
-   performs type-specific statistics collection for columns of the data type.
-   By default, <command>ANALYZE</> will attempt to gather statistics using
-   the type's <quote>equals</> and <quote>less-than</> operators, if there
-   is a default b-tree operator class for the type.  For non-scalar types
-   this behavior is likely to be unsuitable, so it can be overridden by
-   specifying a custom analysis function.  The analysis function must be
-   declared to take a single argument of type <type>internal</>, and return
-   a <type>boolean</> result.  The detailed API for analysis functions appears
-   in <filename>src/include/commands/vacuum.h</>.
-  </para>
-
-  <para>
-   While the details of the new type's internal representation are only
-   known to the I/O functions and other functions you create to work with
-   the type, there are several properties of the internal representation
-<!## PG>
-   that must be declared to <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-   that must be declared to <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-   that must be declared to <productname>Postgres-XL</productname>.
-<!## end>
-   Foremost of these is
-   <replaceable class="parameter">internallength</replaceable>.
-   Base data types can be fixed-length, in which case
-   <replaceable class="parameter">internallength</replaceable> is a
-   positive integer, or variable  length, indicated by setting
-   <replaceable class="parameter">internallength</replaceable>
-   to <literal>VARIABLE</literal>.  (Internally, this is represented
-   by setting <literal>typlen</> to -1.)  The internal representation of all
-   variable-length types must start with a 4-byte integer giving the total
-   length of this value of the type.
-  </para>
-
-  <para>
-   The optional flag <literal>PASSEDBYVALUE</literal> indicates that
-   values of this data type are passed by value, rather than by
-   reference.  You cannot pass by value types whose internal
-   representation is larger than the size of the <type>Datum</> type
-   (4 bytes on most machines, 8 bytes on a few).
-  </para>
-
-  <para>
-   The <replaceable class="parameter">alignment</replaceable> parameter
-   specifies the storage alignment required for the data type.  The
-   allowed values equate to alignment on 1, 2, 4, or 8 byte boundaries.
-   Note that variable-length types must have an alignment of at least
-   4, since they necessarily contain an <type>int4</> as their first component.
-  </para>
-
-  <para>
-   The <replaceable class="parameter">storage</replaceable> parameter
-   allows selection of storage strategies for variable-length data
-   types.  (Only <literal>plain</literal> is allowed for fixed-length
-   types.)  <literal>plain</literal> specifies that data of the type
-   will always be stored in-line and not compressed.
-   <literal>extended</literal> specifies that the system will first
-   try to compress a long data value, and will move the value out of
-   the main table row if it's still too long.
-   <literal>external</literal> allows the value to be moved out of the
-   main table, but the system will not try to compress it.
-   <literal>main</literal> allows compression, but discourages moving
-   the value out of the main table.  (Data items with this storage
-   strategy might still be moved out of the main table if there is no
-   other way to make a row fit, but they will be kept in the main
-   table preferentially over <literal>extended</literal> and
-   <literal>external</literal> items.)
-  </para>
-
-  <para>
-   The <replaceable class="parameter">like_type</replaceable> parameter
-   provides an alternative method for specifying the basic representation
-   properties of a data type: copy them from some existing type. The values of
-   <replaceable class="parameter">internallength</replaceable>,
-   <replaceable class="parameter">passedbyvalue</replaceable>,
-   <replaceable class="parameter">alignment</replaceable>, and
-   <replaceable class="parameter">storage</replaceable> are copied from the
-   named type.  (It is possible, though usually undesirable, to override
-   some of these values by specifying them along with the <literal>LIKE</>
-   clause.)  Specifying representation this way is especially useful when
-   the low-level implementation of the new type <quote>piggybacks</> on an
-   existing type in some fashion.
-  </para>
-
-  <para>
-   The <replaceable class="parameter">category</replaceable> and
-   <replaceable class="parameter">preferred</replaceable> parameters can be
-   used to help control which implicit cast will be applied in ambiguous
-   situations.  Each data type belongs to a category named by a single ASCII
-   character, and each type is either <quote>preferred</> or not within its
-   category.  The parser will prefer casting to preferred types (but only from
-   other types within the same category) when this rule is helpful in
-   resolving overloaded functions or operators.  For more details see <xref
-   linkend="typeconv">.  For types that have no implicit casts to or from any
-   other types, it is sufficient to leave these settings at the defaults.
-   However, for a group of related types that have implicit casts, it is often
-   helpful to mark them all as belonging to a category and select one or two
-   of the <quote>most general</> types as being preferred within the category.
-   The <replaceable class="parameter">category</replaceable> parameter is
-   especially useful when adding a user-defined type to an existing built-in
-   category, such as the numeric or string types.  However, it is also
-   possible to create new entirely-user-defined type categories.  Select any
-   ASCII character other than an upper-case letter to name such a category.
-  </para>
-
-  <para>
-   A default value can be specified, in case a user wants columns of the
-   data type to default to something other than the null value.
-   Specify the default with the <literal>DEFAULT</literal> key word.
-   (Such a default can be overridden by an explicit <literal>DEFAULT</literal>
-   clause attached to a particular column.)
-  </para>
-
-  <para>
-   To indicate that a type is an array, specify the type of the array
-   elements using the <literal>ELEMENT</> key word.  For example, to
-   define an array of 4-byte integers (<type>int4</type>), specify
-   <literal>ELEMENT = int4</literal>. More details about array types
-   appear below.
-  </para>
-
-  <para>
-   To indicate the delimiter to be used between values in the external
-   representation of arrays of this type, <replaceable
-   class="parameter">delimiter</replaceable> can be
-   set to a specific character.  The default delimiter is the comma
-   (<literal>,</literal>).  Note that the delimiter is associated
-   with the array element type, not the array type itself.
-  </para>
-
-  <para>
-   If the optional Boolean
-   parameter <replaceable class="parameter">collatable</replaceable>
-   is true, column definitions and expressions of the type may carry
-   collation information through use of
-   the <literal>COLLATE</literal> clause.  It is up to the
-   implementations of the functions operating on the type to actually
-   make use of the collation information; this does not happen
-   automatically merely by marking the type collatable.
-  </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Array Types</title>
-
-   <para>
-    Whenever a user-defined type is created,
-<!## PG>
-    <productname>PostgreSQL</productname> automatically creates an
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> automatically creates an
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> automatically creates an
-<!## end>
-    associated array type, whose name consists of the base type's
-    name prepended with an underscore, and truncated if necessary to keep
-    it less than <symbol>NAMEDATALEN</symbol> bytes long.  (If the name
-    so generated collides with an existing type name, the process is
-    repeated until a non-colliding name is found.)
-    This implicitly-created array type is variable length and uses the
-    built-in input and output functions <literal>array_in</> and
-    <literal>array_out</>.  The array type tracks any changes in its
-    element type's owner or schema, and is dropped if the element type is.
-   </para>
-
-   <para>
-    You might reasonably ask why there is an <option>ELEMENT</>
-    option, if the system makes the correct array type automatically.
-    The only case where it's useful to use <option>ELEMENT</> is when you are
-    making a fixed-length type that happens to be internally an array of a number of
-    identical things, and you want to allow these things to be accessed
-    directly by subscripting, in addition to whatever operations you plan
-    to provide for the type as a whole.  For example, type <type>point</>
-    is represented as just two floating-point numbers, which it allows to be
-    accessed as <literal>point[0]</> and <literal>point[1]</>.
-    Note that
-    this facility only works for fixed-length types whose internal form
-    is exactly a sequence of identical fixed-length fields.  A subscriptable
-    variable-length type must have the generalized internal representation
-    used by <literal>array_in</> and <literal>array_out</>.
-    For historical reasons (i.e., this is clearly wrong but it's far too
-    late to change it), subscripting of fixed-length array types starts from
-    zero, rather than from one as for variable-length arrays.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of a type to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">attribute_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an attribute (column) for the composite type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">data_type</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing data type to become a column of the
-      composite type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">label</replaceable></term>
-    <listitem>
-     <para>
-      A string literal representing the textual label associated with
-      one value of an enum type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">input_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of a function that converts data from the type's
-      external textual form to its internal form.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">output_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of a function that converts data from the type's
-      internal form to its external textual form.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">receive_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of a function that converts data from the type's
-      external binary form to its internal form.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">send_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of a function that converts data from the type's
-      internal form to its external binary form.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">type_modifier_input_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of a function that converts an array of modifier(s) for the type
-      into internal form.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">type_modifier_output_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of a function that converts the internal form of the type's
-      modifier(s) to external textual form.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">analyze_function</replaceable></term>
-    <listitem>
-     <para>
-      The name of a function that performs statistical analysis for the
-      data type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">internallength</replaceable></term>
-    <listitem>
-     <para>
-      A numeric constant that specifies the length in bytes of the new
-      type's internal representation.  The default assumption is that
-      it is variable-length.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">alignment</replaceable></term>
-    <listitem>
-     <para>
-      The storage alignment requirement of the data type.  If specified,
-      it must be <literal>char</literal>, <literal>int2</literal>,
-      <literal>int4</literal>, or <literal>double</literal>; the
-      default is <literal>int4</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">storage</replaceable></term>
-    <listitem>
-     <para>
-      The storage strategy for the data type.  If specified, must be
-      <literal>plain</literal>, <literal>external</literal>,
-      <literal>extended</literal>, or <literal>main</literal>; the
-      default is <literal>plain</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">like_type</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing data type that the new type will have the
-      same representation as.  The values of
-      <replaceable class="parameter">internallength</replaceable>,
-      <replaceable class="parameter">passedbyvalue</replaceable>,
-      <replaceable class="parameter">alignment</replaceable>, and
-      <replaceable class="parameter">storage</replaceable>
-      are copied from that type, unless overridden by explicit
-      specification elsewhere in this <command>CREATE TYPE</> command.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">category</replaceable></term>
-    <listitem>
-     <para>
-      The category code (a single ASCII character) for this type.
-      The default is <literal>'U'</> for <quote>user-defined type</>.
-      Other standard category codes can be found in
-      <xref linkend="catalog-typcategory-table">.  You may also choose
-      other ASCII characters in order to create custom categories.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">preferred</replaceable></term>
-    <listitem>
-     <para>
-      True if this type is a preferred type within its type category,
-      else false.  The default is false.  Be very careful about creating
-      a new preferred type within an existing type category, as this
-      could cause surprising changes in behavior.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">default</replaceable></term>
-    <listitem>
-     <para>
-      The default value for the data type.  If this is omitted, the
-      default is null.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">element</replaceable></term>
-    <listitem>
-     <para>
-      The type being created is an array; this specifies the type of
-      the array elements.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">delimiter</replaceable></term>
-    <listitem>
-     <para>
-      The delimiter character to be used between values in arrays made
-      of this type.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">collatable</replaceable></term>
-    <listitem>
-     <para>
-      True if this type's operations can use collation information.
-      The default is false.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1 id="SQL-CREATETYPE-notes">
-  <title>Notes</title>
-
-  <para>
-   Because there are no restrictions on use of a data type once it's been
-   created, creating a base type is tantamount to granting public execute
-   permission on the functions mentioned in the type definition.
-   This is usually
-   not an issue for the sorts of functions that are useful in a type
-   definition.  But you might want to think twice before designing a type
-   in a way that would require <quote>secret</> information to be used
-   while converting it to or from external form.
-  </para>
-
-  <para>
-   Before <productname>PostgreSQL</productname> version 8.3, the name of
-   a generated array type was always exactly the element type's name with one
-   underscore character (<literal>_</literal>) prepended.  (Type names were
-   therefore restricted in length to one less character than other names.)
-   While this is still usually the case, the array type name may vary from
-   this in case of maximum-length names or collisions with user type names
-   that begin with underscore.  Writing code that depends on this convention
-   is therefore deprecated.  Instead, use
-   <structname>pg_type</>.<structfield>typarray</> to locate the array type
-   associated with a given type.
-  </para>
-
-  <para>
-   It may be advisable to avoid using type and table names that begin with
-   underscore.  While the server will change generated array type names to
-   avoid collisions with user-given names, there is still risk of confusion,
-   particularly with old client software that may assume that type names
-   beginning with underscores always represent arrays.
-  </para>
-
-  <para>
-   Before <productname>PostgreSQL</productname> version 8.2, the syntax
-   <literal>CREATE TYPE <replaceable>name</></literal> did not exist.
-   The way to create a new base type was to create its input function first.
-<!## PG>
-   In this approach, <productname>PostgreSQL</productname> will first see
-<!## end>
-<!## XC>
-   In this approach, <productname>Postgres-XC</productname> will first see
-<!## end>
-<!## XL>
-   In this approach, <productname>Postgres-XL</productname> will first see
-<!## end>
-   the name of the new data type as the return type of the input function.
-   The shell type is implicitly created in this situation, and then it
-   can be referenced in the definitions of the remaining I/O functions.
-   This approach still works, but is deprecated and might be disallowed in
-   some future release.  Also, to avoid accidentally cluttering
-   the catalogs with shell types as a result of simple typos in function
-   definitions, a shell type will only be made this way when the input
-   function is written in C.
-  </para>
-
-  <para>
-   In <productname>PostgreSQL</productname> versions before 7.3, it
-   was customary to avoid creating a shell type at all, by replacing the
-   functions' forward references to the type name with the placeholder
-   pseudotype <type>opaque</>.  The <type>cstring</> arguments and
-   results also had to be declared as <type>opaque</> before 7.3.  To
-   support loading of old dump files, <command>CREATE TYPE</> will
-   accept I/O functions declared using <type>opaque</>, but it will issue
-   a notice and change the function declarations to use the correct
-   types.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   This example creates a composite type and uses it in
-   a function definition:
-<programlisting>
-CREATE TYPE compfoo AS (f1 int, f2 text);
-
-CREATE FUNCTION getfoo() RETURNS SETOF compfoo AS $$
-    SELECT fooid, fooname FROM foo
-$$ LANGUAGE SQL;
-</programlisting>
-  </para>
-
-  <para>
-   This example creates an enumerated type and uses it in
-   a table definition:
-<programlisting>
-CREATE TYPE bug_status AS ENUM ('new', 'open', 'closed');
-
-CREATE TABLE bug (
-    id serial,
-    description text,
-    status bug_status
-);
-</programlisting>
-  </para>
-
-  <para>
-   This example creates the base data type <type>box</type> and then uses the
-   type in a table definition:
-<programlisting>
-CREATE TYPE box;
-
-CREATE FUNCTION my_box_in_function(cstring) RETURNS box AS ... ;
-CREATE FUNCTION my_box_out_function(box) RETURNS cstring AS ... ;
-
-CREATE TYPE box (
-    INTERNALLENGTH = 16,
-    INPUT = my_box_in_function,
-    OUTPUT = my_box_out_function
-);
-
-CREATE TABLE myboxes (
-    id integer,
-    description box
-);
-</programlisting>
-  </para>
-
-  <para>
-   If the internal structure of <type>box</type> were an array of four
-   <type>float4</> elements, we might instead use:
-<programlisting>
-CREATE TYPE box (
-    INTERNALLENGTH = 16,
-    INPUT = my_box_in_function,
-    OUTPUT = my_box_out_function,
-    ELEMENT = float4
-);
-</programlisting>
-   which would allow a box value's component numbers to be accessed
-   by subscripting.  Otherwise the type behaves the same as before.
-  </para>
-
-  <para>
-   This example creates a large object type and uses it in
-   a table definition:
-<programlisting>
-CREATE TYPE bigobj (
-    INPUT = lo_filein, OUTPUT = lo_fileout,
-    INTERNALLENGTH = VARIABLE
-);
-CREATE TABLE big_objs (
-    id integer,
-    obj bigobj
-);
-</programlisting>
-  </para>
-
-  <para>
-   More examples, including suitable input and output functions, are
-   in <xref linkend="xtypes">.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATETYPE-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   The first form of the <command>CREATE TYPE</command> command, which
-   creates a composite type, conforms to the <acronym>SQL</> standard.
-<!## PG>
-   The other forms are <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   The other forms are <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   The other forms are <productname>Postgres-XL</productname>
-<!## end>
-   extensions.  The <command>CREATE TYPE</command> statement in
-   the <acronym>SQL</> standard also defines other forms that are not
-<!## PG>
-   implemented in <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-   implemented in <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-   implemented in <productname>Postgres-XL</>.
-<!## end>
-  </para>
-
-  <para>
-   The ability to create a composite type with zero attributes is
-<!## PG>
-   a <productname>PostgreSQL</productname>-specific deviation from the
-   standard (analogous to <command>CREATE TABLE</command>).
-<!## end>
-<!## XC>
-   a <productname>Postgres-XC</productname>-specific deviation from the
-   standard (analogous to <command>CREATE TABLE</command>), inherited from <productname>PostgreSQL</>.
-<!## end>
-<!## XL>
-   a <productname>Postgres-XL</productname>-specific deviation from the
-   standard (analogous to <command>CREATE TABLE</command>), inherited from <productname>PostgreSQL</>.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATETYPE-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertype"></member>
-   <member><xref linkend="sql-createdomain"></member>
-   <member><xref linkend="sql-createfunction"></member>
-   <member><xref linkend="sql-droptype"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_user.sgmlin b/doc-xc/src/sgml/ref/create_user.sgmlin
deleted file mode 100644
index 7cefb23c9c..0000000000
--- a/doc-xc/src/sgml/ref/create_user.sgmlin
+++ /dev/null
@@ -1,88 +0,0 @@
-<!--
-doc/src/sgml/ref/create_user.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEUSER">
- <refmeta>
-  <refentrytitle>CREATE USER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE USER</refname>
-  <refpurpose>define a new database role</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createuser">
-  <primary>CREATE USER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE USER <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replaceable class="PARAMETER">option</replaceable> [ ... ] ]
-
-<phrase>where <replaceable class="PARAMETER">option</replaceable> can be:</phrase>
-
-      SUPERUSER | NOSUPERUSER
-    | CREATEDB | NOCREATEDB
-    | CREATEROLE | NOCREATEROLE
-    | CREATEUSER | NOCREATEUSER
-    | INHERIT | NOINHERIT
-    | LOGIN | NOLOGIN
-    | REPLICATION | NOREPLICATION
-    | CONNECTION LIMIT <replaceable class="PARAMETER">connlimit</replaceable>
-    | [ ENCRYPTED | UNENCRYPTED ] PASSWORD '<replaceable class="PARAMETER">password</replaceable>'
-    | VALID UNTIL '<replaceable class="PARAMETER">timestamp</replaceable>'
-    | IN ROLE <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | IN GROUP <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | ROLE <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | ADMIN <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | USER <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    | SYSID <replaceable class="PARAMETER">uid</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>CREATE USER</command> is now an alias for
-   <xref linkend="sql-createrole">.
-   The only difference is that when the command is spelled
-   <command>CREATE USER</command>, <literal>LOGIN</> is assumed
-   by default, whereas <literal>NOLOGIN</> is assumed when
-   the command is spelled
-   <command>CREATE ROLE</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The <command>CREATE USER</command> statement is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.  The SQL standard
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.  The SQL standard
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.  The SQL standard
-<!## end>
-   leaves the definition of users to the implementation.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createrole"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_user_mapping.sgmlin b/doc-xc/src/sgml/ref/create_user_mapping.sgmlin
deleted file mode 100644
index 5cc2ebfafe..0000000000
--- a/doc-xc/src/sgml/ref/create_user_mapping.sgmlin
+++ /dev/null
@@ -1,140 +0,0 @@
-<!--
-doc/src/sgml/ref/create_user_mapping.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEUSERMAPPING">
- <refmeta>
-  <refentrytitle>CREATE USER MAPPING</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE USER MAPPING</refname>
-  <refpurpose>define a new mapping of a user to a foreign server</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createusermapping">
-  <primary>CREATE USER MAPPING</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE USER MAPPING FOR { <replaceable class="parameter">user_name</replaceable> | USER | CURRENT_USER | PUBLIC }
-    SERVER <replaceable class="parameter">server_name</replaceable>
-    [ OPTIONS ( <replaceable class="PARAMETER">option</replaceable> '<replaceable class="PARAMETER">value</replaceable>' [ , ... ] ) ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-<!## XC>
-&xconly;
-  <para>
-   <command>USER MAPPING</> has not been supported
-   by <productname>Postgres-XC</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>USER MAPPING</> is not yet supported
-   in <productname>Postgres-XL</>.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-&pgonly;
-
-  <para>
-   <command>CREATE USER MAPPING</command> defines a mapping of a user
-   to a foreign server.  A user mapping typically encapsulates
-   connection information that a foreign-data wrapper uses together
-   with the information encapsulated be a foreign server to access an
-   external data resource.
-  </para>
-
-  <para>
-   The owner of a foreign server can create user mappings for that
-   server for any user.  Also, a user can create a user mapping for
-   his own user name if <literal>USAGE</> privilege on the server has
-   been granted to the user.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">user_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing user that is mapped to foreign server.
-      <literal>CURRENT_USER</> and <literal>USER</> match the name of
-      the current user.  When <literal>PUBLIC</> is specified, a
-      so-called public mapping is created that is used when no
-      user-specific mapping is applicable.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">server_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing server for which the user mapping is
-      to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>OPTIONS ( <replaceable class="PARAMETER">option</replaceable> '<replaceable class="PARAMETER">value</replaceable>' [, ... ] )</literal></term>
-    <listitem>
-     <para>
-      This clause specifies the options of the user mapping.  The
-      options typically define the actual user name and password of
-      the mapping.  Option names must be unique.  The allowed option
-      names and values are specific to the server's foreign-data wrapper.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a user mapping for user <literal>bob</>, server <literal>foo</>:
-<programlisting>
-CREATE USER MAPPING FOR bob SERVER foo OPTIONS (user 'bob', password 'secret');
-</programlisting>
-  </para>
-
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>CREATE USER MAPPING</command> conforms to ISO/IEC 9075-9 (SQL/MED).
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterusermapping"></member>
-   <member><xref linkend="sql-dropusermapping"></member>
-   <member><xref linkend="sql-createforeigndatawrapper"></member>
-   <member><xref linkend="sql-createserver"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/create_view.sgmlin b/doc-xc/src/sgml/ref/create_view.sgmlin
deleted file mode 100644
index 3e9de6707b..0000000000
--- a/doc-xc/src/sgml/ref/create_view.sgmlin
+++ /dev/null
@@ -1,311 +0,0 @@
-<!--
-doc/src/sgml/ref/create_view.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEVIEW">
- <refmeta>
-  <refentrytitle>CREATE VIEW</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE VIEW</refname>
-  <refpurpose>define a new view</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-createview">
-  <primary>CREATE VIEW</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<!## PG>
-<synopsis>
-CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] VIEW <replaceable class="PARAMETER">name</replaceable> [ ( <replaceable class="PARAMETER">column_name</replaceable> [, ...] ) ]
-    AS <replaceable class="PARAMETER">query</replaceable>
-</synopsis>
-<!## end>
-<!## XC>
-<synopsis>
-CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] VIEW <replaceable class="PARAMETER">name</replaceable> [ ( <replaceable class="PARAMETER">column_name</replaceable> [, ...] ) ]
-    AS <replaceable class="PARAMETER">query</replaceable>
-</synopsis>
-<!## end>
-<!## XL>
-<synopsis>
-CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] VIEW <replaceable class="PARAMETER">name</replaceable> [ ( <replaceable class="PARAMETER">column_name</replaceable> [, ...] ) ]
-    AS <replaceable class="PARAMETER">query</replaceable>
-</synopsis>
-<!## end>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-&common;
-  <para>
-   <command>CREATE VIEW</command> defines a view of a query.  The view
-   is not physically materialized. Instead, the query is run every time
-   the view is referenced in a query.
-  </para>
-
-  <para>
-   <command>CREATE OR REPLACE VIEW</command> is similar, but if a view
-   of the same name already exists, it is replaced.  The new query must
-   generate the same columns that were generated by the existing view query
-   (that is, the same column names in the same order and with the same data
-   types), but it may add additional columns to the end of the list.  The
-   calculations giving rise to the output columns may be completely different.
-  </para>
-
-<!## PG>
-  <para>
-   If a schema name is given (for example, <literal>CREATE VIEW
-   myschema.myview ...</>) then the view is created in the specified
-   schema.  Otherwise it is created in the current schema.  Temporary
-   views exist in a special schema, so a schema name cannot be given
-   when creating a temporary view. The name of the view must be
-   distinct from the name of any other view, table, sequence, index or foreign table
-   in the same schema.
-  </para>
-<!## end>
-<!## XC>
-  <para>
-   If a schema name is given (for example, <literal>CREATE VIEW
-   myschema.myview ...</>) then the view is created in the specified
-   schema.  Otherwise it is created in the current schema.
-   The name of the view must be
-   distinct from the name of any other view, table, sequence, or index
-   in the same schema.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   If a schema name is given (for example, <literal>CREATE VIEW
-   myschema.myview ...</>) then the view is created in the specified
-   schema.  Otherwise it is created in the current schema.
-   The name of the view must be
-   distinct from the name of any other view, table, sequence, or index
-   in the same schema.
-  </para>
-<!## end>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>TEMPORARY</> or <literal>TEMP</></term>
-    <listitem>
-<!## XC>
-     <para>
-      <literal>TEMPORARY</> views have not been supported
-      by <productname>Postgres-XC</>.  This may be supported by the
-      future releases.
-     </para>
-<!## end>
-<!## XL>
-     <para>
-      <literal>TEMPORARY</> are not yet supported
-      in <productname>Postgres-XL</>.  This may be supported by the
-      future releases.
-     </para>
-<!## end>
-<!## PG>
-     <para>
-      If specified, the view is created as a temporary view.
-      Temporary views are automatically dropped at the end of the
-      current session.  Existing
-      permanent relations with the same name are not visible to the
-      current session while the temporary view exists, unless they are
-      referenced with schema-qualified names.
-     </para>
-
-     <para>
-      If any of the tables referenced by the view are temporary,
-      the view is created as a temporary view (whether
-      <literal>TEMPORARY</literal> is specified or not).
-     </para>
-<!## end>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of a view to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">column_name</replaceable></term>
-    <listitem>
-     <para>
-      An optional list of names to be used for columns of the view.
-      If not given, the column names are deduced from the query.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">query</replaceable></term>
-    <listitem>
-     <para>
-      A <xref linkend="sql-select"> or
-      <xref linkend="sql-values"> command
-      which will provide the columns and rows of the view.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    Currently, views are read only: the system will not allow an insert,
-    update, or delete on a view.  You can get the effect of an updatable
-    view by creating rules that rewrite inserts, etc. on the view into
-    appropriate actions on other tables.  For more information see
-    <xref linkend="sql-createrule">.
-   </para>
-
-   <para>
-    Use the <xref linkend="sql-dropview">
-    statement to drop views.
-   </para>
-
-   <para>
-    Be careful that the names and types of the view's columns will be
-    assigned the way you want.  For example:
-<programlisting>
-CREATE VIEW vista AS SELECT 'Hello World';
-</programlisting>
-    is bad form in two ways: the column name defaults to <literal>?column?</>,
-    and the column data type defaults to <type>unknown</>.  If you want a
-    string literal in a view's result, use something like:
-<programlisting>
-CREATE VIEW vista AS SELECT text 'Hello World' AS hello;
-</programlisting>
-   </para>
-
-   <para>
-    Access to tables referenced in the view is determined by permissions of
-    the view owner.  In some cases, this can be used to provide secure but
-    restricted access to the underlying tables.  However, not all views are
-    secure against tampering; see <xref linkend="rules-privileges"> for
-    details.  Functions called in the view are treated the same as if they had
-    been called directly from the query using the view.  Therefore the user of
-    a view must have permissions to call all functions used by the view.
-   </para>
-
-   <para>
-    When <command>CREATE OR REPLACE VIEW</> is used on an
-    existing view, only the view's defining SELECT rule is changed.
-    Other view properties, including ownership, permissions, and non-SELECT
-    rules, remain unchanged.  You must own the view
-    to replace it (this includes being a member of the owning role).
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a view consisting of all comedy films:
-
-<programlisting>
-CREATE VIEW comedies AS
-    SELECT *
-    FROM films
-    WHERE kind = 'Comedy';
-</programlisting>
-   This will create a view containing the columns that are in the
-   <literal>film</> table at the time of view creation.  Though
-   <literal>*</> was used to create the view, columns added later to
-   the table will not be part of the view.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard specifies some additional capabilities for the
-   <command>CREATE VIEW</command> statement:
-<synopsis>
-CREATE VIEW <replaceable class="parameter">name</replaceable> [ ( <replaceable class="parameter">column_name</replaceable> [, ...] ) ]
-    AS <replaceable class="PARAMETER">query</replaceable>
-    [ WITH [ CASCADED | LOCAL ] CHECK OPTION ]
-</synopsis>
-  </para>
-
-  <para>
-   The optional clauses for the full SQL command are:
-
-   <variablelist>
-     <varlistentry>
-      <term><literal>CHECK OPTION</literal></term>
-      <listitem>
-       <para>
-        This option has to do with updatable views.  All
-        <command>INSERT</> and <command>UPDATE</> commands on the view
-        will be checked to ensure data satisfy the view-defining
-        condition (that is, the new data would be visible through the
-        view). If they do not, the update will be rejected.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>LOCAL</literal></term>
-      <listitem>
-       <para>
-        Check for integrity on this view.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CASCADED</literal></term>
-      <listitem>
-       <para>
-        Check for integrity on this view and on any dependent
-        view. <literal>CASCADED</> is assumed if neither
-        <literal>CASCADED</> nor <literal>LOCAL</> is specified.
-       </para>
-      </listitem>
-     </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   <command>CREATE OR REPLACE VIEW</command> is a
-<!## PG>
-   <productname>PostgreSQL</productname> language extension.
-   So is the concept of a temporary view.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> language extension.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> language extension.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterview"></member>
-   <member><xref linkend="sql-dropview"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/createdb.sgmlin b/doc-xc/src/sgml/ref/createdb.sgmlin
deleted file mode 100644
index f4e8e0677d..0000000000
--- a/doc-xc/src/sgml/ref/createdb.sgmlin
+++ /dev/null
@@ -1,412 +0,0 @@
-<!--
-doc/src/sgml/ref/createdb.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-CREATEDB">
- <refmeta>
-  <refentrytitle><application>createdb</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>createdb</refname>
-<!## PG>
-  <refpurpose>create a new <productname>PostgreSQL</productname> database</refpurpose>
-<!## end>
-<!## XC>
-  <refpurpose>create a new <productname>Postgres-XC</productname> database</refpurpose>
-<!## end>
-<!## XL>
-  <refpurpose>create a new <productname>Postgres-XL</productname> database</refpurpose>
-<!## end>
- </refnamediv>
-
- <indexterm zone="app-createdb">
-  <primary>createdb</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>createdb</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-   <arg><replaceable>dbname</replaceable></arg>
-   <arg><replaceable>description</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1 id="R1-APP-CREATEDB-1">
-  <title>
-   Description
-  </title>
-
-&common;
-
-  <para>
-<!## PG>
-   <application>createdb</application> creates a new <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   <application>createdb</application> creates a new <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   <application>createdb</application> creates a new <productname>Postgres-XL</productname>
-<!## end>
-   database.
-  </para>
-
-  <para>
-   Normally, the database user who executes this command becomes the owner of
-   the new database.
-   However, a different owner can be specified via the <option>-O</option>
-   option, if the executing user has appropriate privileges.
-  </para>
-
-  <para>
-   <application>createdb</application> is a wrapper around the
-   <acronym>SQL</acronym> command <xref linkend="SQL-CREATEDATABASE">.
-   There is no effective difference between creating databases via
-   this utility and via other methods for accessing the server.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-
-  <para>
-   <application>createdb</application> accepts the following command-line arguments:
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">dbname</replaceable></term>
-      <listitem>
-       <para>
-        Specifies the name of the database to be created.  The name must be
-<!## PG>
-        unique among all <productname>PostgreSQL</productname> databases in this cluster.
-<!## end>
-<!## XC>
-        unique among all <productname>Postgres-XC</productname> databases in this cluster.
-<!## end>
-<!## XL>
-        unique among all <productname>Postgres-XL</productname> databases in this cluster.
-<!## end>
-        The default is to create a database with the same name as the
-        current system user.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">description</replaceable></term>
-      <listitem>
-       <para>
-        Specifies a comment to be associated with the newly created
-        database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-D <replaceable class="parameter">tablespace</replaceable></></term>
-      <term><option>--tablespace=<replaceable class="parameter">tablespace</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the default tablespace for the database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</></term>
-      <term><option>--echo</></term>
-      <listitem>
-       <para>
-        Echo the commands that <application>createdb</application> generates
-        and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-E <replaceable class="parameter">encoding</replaceable></></term>
-      <term><option>--encoding=<replaceable class="parameter">encoding</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the character encoding scheme to be used in this
-        database. The character sets supported by the
-<!## PG>
-        <productname>PostgreSQL</productname> server are described in
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> servers are described in
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> servers are described in
-<!## end>
-        <xref linkend="multibyte-charset-supported">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l <replaceable class="parameter">locale</replaceable></></term>
-      <term><option>--locale=<replaceable class="parameter">locale</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the locale to be used in this database.  This is equivalent
-        to specifying both <option>--lc-collate</option> and <option>--lc-ctype</option>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--lc-collate=<replaceable class="parameter">locale</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the LC_COLLATE setting to be used in this database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--lc-ctype=<replaceable class="parameter">locale</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the LC_CTYPE setting to be used in this database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-O <replaceable class="parameter">owner</replaceable></></term>
-      <term><option>--owner=<replaceable class="parameter">owner</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the database user who will own the new database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-T <replaceable class="parameter">template</replaceable></></term>
-      <term><option>--template=<replaceable class="parameter">template</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the template database from which to build this database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>createdb</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    <varlistentry>
-      <term><option>-?</></term>
-      <term><option>--help</></term>
-      <listitem>
-      <para>
-      Show help about <application>createdb</application> command line
-      arguments, and exit.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    The options <option>-D</option>, <option>-l</option>, <option>-E</option>,
-    <option>-O</option>, and
-    <option>-T</option> correspond to options of the underlying
-    SQL command <xref linkend="SQL-CREATEDATABASE">; see there for more information
-    about them.
-   </para>
-
-   <para>
-    <application>createdb</application> also accepts the following
-    command-line arguments for connection parameters:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the
-        server is running.  If the value begins with a slash, it is used
-        as the directory for the Unix domain socket.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or the local Unix domain socket file
-        extension on which the server is listening for connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-       <para>
-        Force <application>createdb</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>createdb</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>createdb</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATABASE</envar></term>
-    <listitem>
-     <para>
-      If set, the name of the database to create, unless overridden on
-      the command line.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters.  <envar>PGUSER</envar> also
-      determines the name of the database to create, if it is not
-      specified on the command line or by <envar>PGDATABASE</envar>.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-<!## PG>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-<!## end>
-<!## XC>
-   This utility, like most other <productname>Postgres-XC</> utilities,
-<!## end>
-<!## XL>
-   This utility, like most other <productname>Postgres-XL</> utilities,
-<!## end>
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Diagnostics</title>
-
-  <para>
-   In case of difficulty, see <xref linkend="SQL-CREATEDATABASE">
-   and <xref linkend="APP-PSQL"> for
-   discussions of potential problems and error messages.
-   The database server must be running at the
-   targeted host.  Also, any default connection settings and environment
-   variables used by the <application>libpq</application> front-end
-   library will apply.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Examples</title>
-
-   <para>
-    To create the database <literal>demo</literal> using the default
-    database server:
-<screen>
-<prompt>$ </prompt><userinput>createdb demo</userinput>
-</screen>
-   </para>
-
-   <para>
-    To create the database <literal>demo</literal> using the
-    server on host <literal>eden</>, port 5000, using the
-    <literal>LATIN1</literal> encoding scheme with a look at the
-    underlying command:
-<screen>
-<prompt>$ </prompt><userinput>createdb -p 5000 -h eden -E LATIN1 -e demo</userinput>
-<computeroutput>CREATE DATABASE demo ENCODING 'LATIN1';</computeroutput>
-</screen>
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-dropdb"></member>
-   <member><xref linkend="sql-createdatabase"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/createlang.sgmlin b/doc-xc/src/sgml/ref/createlang.sgmlin
deleted file mode 100644
index 8d30171c22..0000000000
--- a/doc-xc/src/sgml/ref/createlang.sgmlin
+++ /dev/null
@@ -1,322 +0,0 @@
-<!--
-doc/src/sgml/ref/createlang.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-CREATELANG">
- <refmeta>
-  <refentrytitle><application>createlang</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>createlang</refname>
-<!## PG>
-  <refpurpose>install a <productname>PostgreSQL</productname> procedural language</refpurpose>
-<!## end>
-<!## XC>
-  <refpurpose>install a <productname>Postgres-XC</productname> procedural language</refpurpose>
-<!## end>
-<!## XL>
-  <refpurpose>install a <productname>Postgres-XL</productname> procedural language</refpurpose>
-<!## end>
- </refnamediv>
-
- <indexterm zone="app-createlang">
-  <primary>createlang</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>createlang</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg choice="plain"><replaceable>langname</replaceable></arg>
-   <arg><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>createlang</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <group choice="plain"><arg>--list</arg><arg>-l</arg></group>
-   <arg choice="plain"><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <application>createlang</application> is a utility for adding a
-<!## PG>
-   procedural language to a <productname>PostgreSQL</productname> database.
-<!## end>
-<!## XC>
-   procedural language to a <productname>Postgres-XC</productname> database.
-<!## end>
-<!## XL>
-   procedural language to a <productname>Postgres-XL</productname> database.
-<!## end>
-  </para>
-
-  <para>
-   <application>createlang</application> is just a wrapper around the
-   <xref linkend="sql-createextension"> SQL command.
-  </para>
-
-  <caution>
-   <para>
-    <application>createlang</application> is deprecated and may be removed
-<!## PG>
-    in a future <productname>PostgreSQL</productname> release.  Direct use
-<!## end>
-<!## XC>
-    in a future <productname>Postgres-XC</productname> release.  Direct use
-<!## end>
-<!## XL>
-    in a future <productname>Postgres-XL</productname> release.  Direct use
-<!## end>
-    of the <command>CREATE EXTENSION</> command is recommended instead.
-   </para>
-  </caution>
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-
-   <para>
-    <application>createlang</application> accepts the following command-line arguments:
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">langname</replaceable></term>
-      <listitem>
-       <para>
-        Specifies the name of the procedural language to be installed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option><optional>-d</> <replaceable class="parameter">dbname</replaceable></></term>
-      <term><option><optional>--dbname=</><replaceable class="parameter">dbname</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the database to which the language should be added.
-        The default is to use the database with the same name as the
-        current system user.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</></term>
-      <term><option>--echo</></term>
-      <listitem>
-       <para>
-        Display SQL commands as they are executed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l</></term>
-      <term><option>--list</></term>
-      <listitem>
-       <para>
-        Show a list of already installed languages in the target database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>createlang</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    <varlistentry>
-      <term><option>-?</></term>
-      <term><option>--help</></term>
-      <listitem>
-      <para>
-      Show help about <application>createlang</application> command line
-      arguments, and exit.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    <application>createlang</application> also accepts
-    the following command-line arguments for connection parameters:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the
-        server
-        is running.  If the value begins with a slash, it is used
-        as the directory for the Unix domain socket.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server
-        is listening for connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-       <para>
-        Force <application>createlang</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>createlang</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>createlang</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATABASE</envar></term>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-<!## PG>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-<!## end>
-<!## XC>
-   This utility, like most other <productname>Postgres-XC</> utilities,
-<!## end>
-<!## XL>
-   This utility, like most other <productname>Postgres-XL</> utilities,
-<!## end>
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Diagnostics</title>
-
-   <para>
-    Most error messages are self-explanatory. If not, run
-    <application>createlang</application> with the <option>--echo</option>
-    option and see the respective <acronym>SQL</acronym> command
-    for details.  Also, any default connection settings and environment
-    variables used by the <application>libpq</application> front-end
-    library will apply.
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="app-droplang"> to remove a language.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Examples</title>
-
-   <para>
-    To install the language <literal>pltcl</literal> into the database
-    <literal>template1</literal>:
-<screen>
-<prompt>$ </prompt><userinput>createlang pltcl template1</userinput>
-</screen>
-    Note that installing the language into <literal>template1</literal>
-    will cause it to be automatically installed into subsequently-created
-    databases as well.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-droplang"></member>
-   <member><xref linkend="sql-createextension"></member>
-   <member><xref linkend="sql-createlanguage"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/createuser.sgmlin b/doc-xc/src/sgml/ref/createuser.sgmlin
deleted file mode 100644
index a1be3cdd65..0000000000
--- a/doc-xc/src/sgml/ref/createuser.sgmlin
+++ /dev/null
@@ -1,488 +0,0 @@
-<!--
-doc/src/sgml/ref/createuser.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-CREATEUSER">
- <refmeta>
-  <refentrytitle><application>createuser</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>createuser</refname>
-<!## PG>
-  <refpurpose>define a new <productname>PostgreSQL</productname> user account</refpurpose>
-<!## end>
-<!## XC>
-  <refpurpose>define a new <productname>Postgres-XC</productname> user account</refpurpose>
-<!## end>
-<!## XL>
-  <refpurpose>define a new <productname>Postgres-XL</productname> user account</refpurpose>
-<!## end>
- </refnamediv>
-
- <indexterm zone="app-createuser">
-  <primary>createuser</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>createuser</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-   <arg><replaceable>username</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1>
-  <title>Description</title>
-  <para>
-   <application>createuser</application> creates a
-<!## PG>
-   new <productname>PostgreSQL</productname> user (or more precisely, a role).
-<!## end>
-<!## XC>
-   new <productname>Postgres-XC</productname> user (or more precisely, a role).
-<!## end>
-<!## XL>
-   new <productname>Postgres-XL</productname> user (or more precisely, a role).
-<!## end>
-   Only superusers and users with <literal>CREATEROLE</> privilege can create
-   new users, so <application>createuser</application> must be
-   invoked by someone who can connect as a superuser or a user with
-   <literal>CREATEROLE</> privilege.
-  </para>
-
-  <para>
-   If you wish to create a new superuser, you must connect as a
-   superuser, not merely with <literal>CREATEROLE</> privilege.
-   Being a superuser implies the ability to bypass all access permission
-   checks within the database, so superuserdom should not be granted lightly.
-  </para>
-
-  <para>
-   <application>createuser</application> is a wrapper around the
-   <acronym>SQL</acronym> command <xref linkend="SQL-CREATEROLE">.
-   There is no effective difference between creating users via
-   this utility and via other methods for accessing the server.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-
-  <para>
-   <application>createuser</> accepts the following command-line arguments:
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-<!## PG>
-        Specifies the name of the <productname>PostgreSQL</productname> user
-<!## end>
-<!## XC>
-        Specifies the name of the <productname>Postgres-XC</productname> user
-<!## end>
-<!## XL>
-        Specifies the name of the <productname>Postgres-XL</productname> user
-<!## end>
-        to be created.
-        This name must be different from all existing roles in this
-<!## PG>
-        <productname>PostgreSQL</productname> installation.
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> installation.
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> installation.
-<!## end>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-c <replaceable class="parameter">number</replaceable></></term>
-      <term><option>--connection-limit=<replaceable class="parameter">number</replaceable></></term>
-      <listitem>
-       <para>
-        Set a maximum number of connections for the new user.
-        The default is to set no limit.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-d</></term>
-      <term><option>--createdb</></term>
-      <listitem>
-       <para>
-        The new user will be allowed to create databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-D</></term>
-      <term><option>--no-createdb</></term>
-      <listitem>
-       <para>
-        The new user will not be allowed to create databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</></term>
-      <term><option>--echo</></term>
-      <listitem>
-       <para>
-        Echo the commands that <application>createuser</application> generates
-        and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-E</></term>
-      <term><option>--encrypted</></term>
-      <listitem>
-       <para>
-        Encrypts the user's password stored in the database. If not
-        specified, the default password behavior is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-i</></term>
-      <term><option>--inherit</></term>
-      <listitem>
-       <para>
-        The new role will automatically inherit privileges of roles
-        it is a member of.
-        This is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-I</></term>
-      <term><option>--no-inherit</></term>
-      <listitem>
-       <para>
-        The new role will not automatically inherit privileges of roles
-        it is a member of.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l</></term>
-      <term><option>--login</></term>
-      <listitem>
-       <para>
-        The new user will be allowed to log in (that is, the user name
-        can be used as the initial session user identifier).
-        This is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-L</></term>
-      <term><option>--no-login</></term>
-      <listitem>
-       <para>
-        The new user will not be allowed to log in.
-        (A role without login privilege is still useful as a means of
-        managing database permissions.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-N</></term>
-      <term><option>--unencrypted</></term>
-      <listitem>
-       <para>
-        Does not encrypt the user's password stored in the database. If
-        not specified, the default password behavior is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-P</></term>
-      <term><option>--pwprompt</></term>
-      <listitem>
-       <para>
-       If given, <application>createuser</application> will issue a prompt for
-       the password of the new user. This is not necessary if you do not plan
-       on using password authentication.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-r</></term>
-      <term><option>--createrole</></term>
-      <listitem>
-       <para>
-        The new user will be allowed to create new roles (that is,
-        this user will have <literal>CREATEROLE</> privilege).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-R</></term>
-      <term><option>--no-createrole</></term>
-      <listitem>
-       <para>
-        The new user will not be allowed to create new roles.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</></term>
-      <term><option>--superuser</></term>
-      <listitem>
-       <para>
-        The new user will be a superuser.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-S</></term>
-      <term><option>--no-superuser</></term>
-      <listitem>
-       <para>
-        The new user will not be a superuser.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>createuser</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>createuser</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-  </para>
-
-  <para>
-   You will be prompted for a name and other missing information if it
-   is not specified on the command line.
-  </para>
-
-  <para>
-   <application>createuser</application> also accepts the following
-   command-line arguments for connection parameters:
-
-   <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the
-        server
-        is running.  If the value begins with a slash, it is used
-        as the directory for the Unix domain socket.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server
-        is listening for connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-       <para>
-        User name to connect as (not the user name to create).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-       <para>
-        Force <application>createuser</application> to prompt for a
-        password (for connecting to the server, not for the
-        password of the new user).
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>createuser</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>createuser</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-<!## PG>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-<!## end>
-<!## XC>
-   This utility, like most other <productname>Postgres-XC</> utilities,
-<!## end>
-<!## XL>
-   This utility, like most other <productname>Postgres-XL</> utilities,
-<!## end>
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Diagnostics</title>
-
-  <para>
-   In case of difficulty, see <xref linkend="SQL-CREATEROLE">
-   and <xref linkend="APP-PSQL"> for
-   discussions of potential problems and error messages.
-   The database server must be running at the
-   targeted host.  Also, any default connection settings and environment
-   variables used by the <application>libpq</application> front-end
-   library will apply.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Examples</title>
-
-   <para>
-    To create a user <literal>joe</literal> on the default database
-    server:
-<screen>
-<prompt>$ </prompt><userinput>createuser joe</userinput>
-<computeroutput>Shall the new role be a superuser? (y/n) </computeroutput><userinput>n</userinput>
-<computeroutput>Shall the new role be allowed to create databases? (y/n) </computeroutput><userinput>n</userinput>
-<computeroutput>Shall the new role be allowed to create more new roles? (y/n) </computeroutput><userinput>n</userinput>
-</screen>
-   </para>
-
-   <para>
-    To create the same user <literal>joe</literal> using the
-    server on host <literal>eden</>, port 5000, avoiding the prompts and
-    taking a look at the underlying command:
-<screen>
-<prompt>$ </prompt><userinput>createuser -h eden -p 5000 -S -D -R -e joe</userinput>
-<computeroutput>CREATE ROLE joe NOSUPERUSER NOCREATEDB NOCREATEROLE INHERIT LOGIN;</computeroutput>
-</screen>
-   </para>
-
-   <para>
-    To create the user <literal>joe</literal> as a superuser,
-    and assign a password immediately:
-<screen>
-<prompt>$ </prompt><userinput>createuser -P -s -e joe</userinput>
-<computeroutput>Enter password for new role: </computeroutput><userinput>xyzzy</userinput>
-<computeroutput>Enter it again: </computeroutput><userinput>xyzzy</userinput>
-<computeroutput>CREATE ROLE joe PASSWORD 'md5b5f5ba1a423792b526f799ae4eb3d59e' SUPERUSER CREATEDB CREATEROLE INHERIT LOGIN;</computeroutput>
-</screen>
-    In the above example, the new password isn't actually echoed when typed,
-    but we show what was typed for clarity.  As you see, the password is
-    encrypted before it is sent to the client.  If the option <option>--unencrypted</option>
-    is used, the password <emphasis>will</> appear in the echoed command
-    (and possibly also in the server log and elsewhere),
-    so you don't want to use <option>-e</> in that case, if
-    anyone else can see your screen.
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-dropuser"></member>
-   <member><xref linkend="sql-createrole"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/deallocate.sgmlin b/doc-xc/src/sgml/ref/deallocate.sgmlin
deleted file mode 100644
index e496efb744..0000000000
--- a/doc-xc/src/sgml/ref/deallocate.sgmlin
+++ /dev/null
@@ -1,99 +0,0 @@
-<!--
-doc/src/sgml/ref/deallocate.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DEALLOCATE">
- <refmeta>
-  <refentrytitle>DEALLOCATE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DEALLOCATE</refname>
-  <refpurpose>deallocate a prepared statement</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-deallocate">
-  <primary>DEALLOCATE</primary>
- </indexterm>
-
- <indexterm zone="sql-deallocate">
-  <primary>prepared statements</primary>
-  <secondary>removing</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DEALLOCATE [ PREPARE ] { <replaceable class="parameter">name</replaceable> | ALL }
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-  <para>
-   <command>DEALLOCATE</command> is used to deallocate a previously
-   prepared SQL statement. If you do not explicitly deallocate a
-   prepared statement, it is deallocated when the session ends.
-  </para>
-
-  <para>
-   For more information on prepared statements, see <xref
-   linkend="sql-prepare">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>PREPARE</literal></term>
-    <listitem>
-     <para>
-      This key word is ignored.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the prepared statement to deallocate.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ALL</literal></term>
-    <listitem>
-     <para>
-      Deallocate all prepared statements.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard includes a <command>DEALLOCATE</command>
-   statement, but it is only for use in embedded SQL.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-execute"></member>
-   <member><xref linkend="sql-prepare"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/declare.sgmlin b/doc-xc/src/sgml/ref/declare.sgmlin
deleted file mode 100644
index dab62fbec1..0000000000
--- a/doc-xc/src/sgml/ref/declare.sgmlin
+++ /dev/null
@@ -1,411 +0,0 @@
-<!--
-doc/src/sgml/ref/declare.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DECLARE">
- <refmeta>
-  <refentrytitle>DECLARE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DECLARE</refname>
-  <refpurpose>define a cursor</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-declare">
-  <primary>DECLARE</primary>
- </indexterm>
-
- <indexterm zone="sql-declare">
-  <primary>cursor</primary>
-  <secondary>DECLARE</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<!## PG>
-<synopsis>
-DECLARE <replaceable class="parameter">name</replaceable> [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ]
-    CURSOR [ { WITH | WITHOUT } HOLD ] FOR <replaceable class="parameter">query</replaceable>
-</synopsis>
-<!## end>
-<!## XC>
-<synopsis>
-DECLARE <replaceable class="parameter">name</replaceable> [ BINARY ] [ NO SCROLL ]
-    CURSOR [ WITHOUT HOLD ] FOR <replaceable class="parameter">query</replaceable>
-</synopsis>
-<!## end>
-<!## XL>
-<synopsis>
-DECLARE <replaceable class="parameter">name</replaceable> [ BINARY ] [ NO SCROLL ]
-    CURSOR [ WITHOUT HOLD ] FOR <replaceable class="parameter">query</replaceable>
-</synopsis>
-<!## end>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DECLARE</command> allows a user to create cursors, which
-   can be used to retrieve
-   a small number of rows at a time out of a larger query.
-   After the cursor is created, rows are fetched from it using
-   <xref linkend="sql-fetch">.
-  </para>
-
-  <note>
-   <para>
-    This page describes usage of cursors at the SQL command level.
-    If you are trying to use cursors inside a <application>PL/pgSQL</>
-    function, the rules are different &mdash;
-    see <xref linkend="plpgsql-cursors">.
-   </para>
-  </note>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the cursor to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>BINARY</literal></term>
-    <listitem>
-     <para>
-      Causes the cursor to return data in binary rather than in text format.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>INSENSITIVE</literal></term>
-    <listitem>
-<!## XC>
-&xconly;
-     <para>
-      Current release of <productname>Postgres-XC</> does not
-      support <literal>INSENSITIVE</literal> cursor.
-     </para>
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      Current release of <productname>Postgres-XL</> does not
-      support <literal>INSENSITIVE</literal> cursor.
-     </para>
-<!## end>
-<!## PG>
-     <para>
-      Indicates that data retrieved from the cursor should be
-      unaffected by updates to the table(s) underlying the cursor that occur
-      after the cursor is created.  In <productname>PostgreSQL</productname>,
-      this is the default behavior; so this key word has no
-      effect and is only accepted for compatibility with the SQL standard.
-     </para>
-<!## end>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SCROLL</literal></term>
-    <term><literal>NO SCROLL</literal></term>
-    <listitem>
-     <para>
-      <literal>SCROLL</literal> specifies that the cursor can be used
-      to retrieve rows in a nonsequential fashion (e.g.,
-      backward). Depending upon the complexity of the query's
-      execution plan, specifying <literal>SCROLL</literal> might impose
-      a performance penalty on the query's execution time.
-      <literal>NO SCROLL</literal> specifies that the cursor cannot be
-      used to retrieve rows in a nonsequential fashion.  The default is to
-      allow scrolling in some cases; this is not the same as specifying
-      <literal>SCROLL</literal>. See <xref linkend="sql-declare-notes"
-      endterm="sql-declare-notes-title"> for details.
-     </para>
-<!## XC>
-&xconly;
-     <para>
-      Current release of <productname>Postgres-XC</> does not
-      support <literal>SCROLL</> cursor.
-     </para>
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      The current release of <productname>Postgres-XL</> does not
-      support <literal>SCROLL</> cursor.
-     </para>
-<!## end>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>WITH HOLD</literal></term>
-    <term><literal>WITHOUT HOLD</literal></term>
-    <listitem>
-     <para>
-      <literal>WITH HOLD</literal> specifies that the cursor can
-      continue to be used after the transaction that created it
-      successfully commits.  <literal>WITHOUT HOLD</literal> specifies
-      that the cursor cannot be used outside of the transaction that
-      created it. If neither <literal>WITHOUT HOLD</literal> nor
-      <literal>WITH HOLD</literal> is specified, <literal>WITHOUT
-      HOLD</literal> is the default.
-     </para>
-<!## XC>
-&xconly;
-     <para>
-      Current release of <productname>Postgres-XC</> does ot
-      support <literal>WITH HOLD</> cursor.
-     </para>
-<!## end>
-<!## XL>
-&xlonly;
-     <para>
-      Current release of <productname>Postgres-XL</> does not
-      support <literal>WITH HOLD</> cursor.
-     </para>
-<!## end>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">query</replaceable></term>
-    <listitem>
-     <para>
-      A <xref linkend="sql-select"> or
-      <xref linkend="sql-values"> command
-      which will provide the rows to be returned by the cursor.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   The key words <literal>BINARY</literal>,
-   <literal>INSENSITIVE</literal>, and <literal>SCROLL</literal> can
-   appear in any order.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-declare-notes">
-  <title id="sql-declare-notes-title">Notes</title>
-
-  <para>
-   Normal cursors return data in text format, the same as a
-   <command>SELECT</> would produce.  The <literal>BINARY</> option
-   specifies that the cursor should return data in binary format.
-   This reduces conversion effort for both the server and client,
-   at the cost of more programmer effort to deal with platform-dependent
-   binary data formats.
-   As an example, if a query returns a value of one from an integer column,
-   you would get a string of <literal>1</> with a default cursor,
-   whereas with a binary cursor you would get
-   a 4-byte field containing the internal representation of the value
-   (in big-endian byte order).
-  </para>
-
-  <para>
-   Binary cursors should be used carefully.  Many applications,
-   including <application>psql</application>, are not prepared to
-   handle binary cursors and expect data to come back in the text
-   format.
-  </para>
-
-  <note>
-   <para>
-    When the client application uses the <quote>extended query</> protocol
-    to issue a <command>FETCH</> command, the Bind protocol message
-    specifies whether data is to be retrieved in text or binary format.
-    This choice overrides the way that the cursor is defined.  The concept
-    of a binary cursor as such is thus obsolete when using extended query
-    protocol &mdash; any cursor can be treated as either text or binary.
-   </para>
-  </note>
-
-   <para>
-    Unless <literal>WITH HOLD</literal> is specified, the cursor
-    created by this command can only be used within the current
-    transaction.  Thus, <command>DECLARE</> without <literal>WITH
-    HOLD</literal> is useless outside a transaction block: the cursor would
-    survive only to the completion of the statement.  Therefore
-    <productname>PostgreSQL</productname> reports an error if such a
-    command is used outside a transaction block.
-    Use
-    <xref linkend="sql-begin"> and
-    <xref linkend="sql-commit">
-    (or <xref linkend="sql-rollback">)
-    to define a transaction block.
-   </para>
-
-   <para>
-    If <literal>WITH HOLD</literal> is specified and the transaction
-    that created the cursor successfully commits, the cursor can
-    continue to be accessed by subsequent transactions in the same
-    session.  (But if the creating transaction is aborted, the cursor
-    is removed.)  A cursor created with <literal>WITH HOLD</literal>
-    is closed when an explicit <command>CLOSE</command> command is
-    issued on it, or the session ends.  In the current implementation,
-    the rows represented by a held cursor are copied into a temporary
-    file or memory area so that they remain available for subsequent
-    transactions.
-   </para>
-
-   <para>
-    <literal>WITH HOLD</literal> may not be specified when the query
-    includes <literal>FOR UPDATE</> or <literal>FOR SHARE</>.
-   </para>
-
-   <para>
-    The <literal>SCROLL</> option should be specified when defining a
-    cursor that will be used to fetch backwards.  This is required by
-    the SQL standard.  However, for compatibility with earlier
-    versions, <productname>PostgreSQL</productname> will allow
-    backward fetches without <literal>SCROLL</>, if the cursor's query
-    plan is simple enough that no extra overhead is needed to support
-    it. However, application developers are advised not to rely on
-    using backward fetches from a cursor that has not been created
-    with <literal>SCROLL</literal>.  If <literal>NO SCROLL</> is
-    specified, then backward fetches are disallowed in any case.
-   </para>
-
-   <para>
-    Backward fetches are also disallowed when the query
-    includes <literal>FOR UPDATE</> or <literal>FOR SHARE</>; therefore
-    <literal>SCROLL</literal> may not be specified in this case.
-   </para>
-
-   <caution>
-    <para>
-     Scrollable and <literal>WITH HOLD</literal> cursors may give unexpected
-     results if they invoke any volatile functions (see <xref
-     linkend="xfunc-volatility">).  When a previously fetched row is
-     re-fetched, the functions might be re-executed, perhaps leading to
-     results different from the first time.  One workaround for such cases
-     is to declare the cursor <literal>WITH HOLD</literal> and commit the
-     transaction before reading any rows from it.  This will force the
-     entire output of the cursor to be materialized in temporary storage,
-     so that volatile functions are executed exactly once for each row.
-    </para>
-   </caution>
-
-   <para>
-    If the cursor's query includes <literal>FOR UPDATE</> or <literal>FOR
-    SHARE</>, then returned rows are locked at the time they are first
-    fetched, in the same way as for a regular
-    <xref linkend="sql-select"> command with
-    these options.
-    In addition, the returned rows will be the most up-to-date versions;
-    therefore these options provide the equivalent of what the SQL standard
-    calls a <quote>sensitive cursor</>.  (Specifying <literal>INSENSITIVE</>
-    together with <literal>FOR UPDATE</> or <literal>FOR SHARE</> is an error.)
-   </para>
-
-   <caution>
-    <para>
-     It is generally recommended to use <literal>FOR UPDATE</> if the cursor
-     is intended to be used with <command>UPDATE ... WHERE CURRENT OF</> or
-     <command>DELETE ... WHERE CURRENT OF</>.  Using <literal>FOR UPDATE</>
-     prevents other sessions from changing the rows between the time they are
-     fetched and the time they are updated.  Without <literal>FOR UPDATE</>,
-     a subsequent <literal>WHERE CURRENT OF</> command will have no effect if
-     the row was changed since the cursor was created.
-    </para>
-
-    <para>
-     Another reason to use <literal>FOR UPDATE</> is that without it, a
-     subsequent <literal>WHERE CURRENT OF</> might fail if the cursor query
-     does not meet the SQL standard's rules for being <quote>simply
-     updatable</> (in particular, the cursor must reference just one table
-     and not use grouping or <literal>ORDER BY</>).  Cursors
-     that are not simply updatable might work, or might not, depending on plan
-     choice details; so in the worst case, an application might work in testing
-     and then fail in production.
-    </para>
-
-    <para>
-     The main reason not to use <literal>FOR UPDATE</> with <literal>WHERE
-     CURRENT OF</> is if you need the cursor to be scrollable, or to be
-     insensitive to the subsequent updates (that is, continue to show the old
-     data).  If this is a requirement, pay close heed to the caveats shown
-     above.
-    </para>
-   </caution>
-
-   <para>
-    The SQL standard only makes provisions for cursors in embedded
-    <acronym>SQL</acronym>.  The <productname>PostgreSQL</productname>
-    server does not implement an <command>OPEN</command> statement for
-    cursors; a cursor is considered to be open when it is declared.
-    However, <application>ECPG</application>, the embedded SQL
-    preprocessor for <productname>PostgreSQL</productname>, supports
-    the standard SQL cursor conventions, including those involving
-    <command>DECLARE</command> and <command>OPEN</command> statements.
-   </para>
-
-   <para>
-    You can see all available cursors by querying the <link
-    linkend="view-pg-cursors"><structname>pg_cursors</structname></link>
-    system view.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To declare a cursor:
-<programlisting>
-DECLARE liahona CURSOR FOR SELECT * FROM films;
-</programlisting>
-   See <xref linkend="sql-fetch"> for more
-   examples of cursor usage.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard says that it is implementation-dependent whether cursors
-   are sensitive to concurrent updates of the underlying data by default.  In
-   <productname>PostgreSQL</productname>, cursors are insensitive by default,
-   and can be made sensitive by specifying <literal>FOR UPDATE</>.  Other
-   products may work differently.
-  </para>
-
-  <para>
-   The SQL standard allows cursors only in embedded
-   <acronym>SQL</acronym> and in modules. <productname>PostgreSQL</>
-   permits cursors to be used interactively.
-  </para>
-
-  <para>
-   Binary cursors are a <productname>PostgreSQL</productname>
-   extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-close"></member>
-   <member><xref linkend="sql-fetch"></member>
-   <member><xref linkend="sql-move"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/delete.sgmlin b/doc-xc/src/sgml/ref/delete.sgmlin
deleted file mode 100644
index 626097d24d..0000000000
--- a/doc-xc/src/sgml/ref/delete.sgmlin
+++ /dev/null
@@ -1,361 +0,0 @@
-<!--
-doc/src/sgml/ref/delete.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DELETE">
- <refmeta>
-  <refentrytitle>DELETE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DELETE</refname>
-  <refpurpose>delete rows of a table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-delete">
-  <primary>DELETE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<!## PG>
-<synopsis>
-[ WITH [ RECURSIVE ] <replaceable class="parameter">with_query</replaceable> [, ...] ]
-DELETE FROM [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ [ AS ] <replaceable class="parameter">alias</replaceable> ]
-    [ USING <replaceable class="PARAMETER">using_list</replaceable> ]
-    [ WHERE <replaceable class="PARAMETER">condition</replaceable> | WHERE CURRENT OF <replaceable class="PARAMETER">cursor_name</replaceable> ]
-    [ RETURNING * | <replaceable class="parameter">output_expression</replaceable> [ [ AS ] <replaceable class="parameter">output_name</replaceable> ] [, ...] ]
-</synopsis>
-<!## end>
-<!## XC>
-<synopsis>
-DELETE FROM [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ [ AS ] <replaceable class="parameter">alias</replaceable> ]
-    [ WHERE <replaceable class="PARAMETER">condition</replaceable> ]
-    [ RETURNING * | <replaceable class="parameter">output_expression</replaceable> [ [ AS ] <replaceable class="parameter">output_name</replaceable> ] [, ...] ]
-</synopsis>
-<!## end>
-<!## XL>
-<synopsis>
-DELETE FROM [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ [ AS ] <replaceable class="parameter">alias</replaceable> ]
-    [ WHERE <replaceable class="PARAMETER">condition</replaceable> ]
-    [ RETURNING * | <replaceable class="parameter">output_expression</replaceable> [ [ AS ] <replaceable class="parameter">output_name</replaceable> ] [, ...] ]
-</synopsis>
-<!## end>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-  <para>
-   <command>DELETE</command> deletes rows that satisfy the
-   <literal>WHERE</literal> clause from the specified table.  If the
-   <literal>WHERE</literal> clause is absent, the effect is to delete
-   all rows in the table.  The result is a valid, but empty table.
-  </para>
-
-   <tip>
-    <para>
-     <xref linkend="sql-truncate"> is a
-<!## PG>
-     <productname>PostgreSQL</productname> extension that provides a
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> extension that provides a
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> extension that provides a
-<!## end>
-     faster mechanism to remove all rows from a table.
-    </para>
-   </tip>
-
-  <para>
-   By default, <command>DELETE</command> will delete rows in the
-   specified table and all its child tables. If you wish to delete only
-   from the specific table mentioned, you must use the
-   <literal>ONLY</literal> clause.
-  </para>
-
-  <para>
-   There are two ways to delete rows in a table using information
-   contained in other tables in the database: using sub-selects, or
-   specifying additional tables in the <literal>USING</literal> clause.
-   Which technique is more appropriate depends on the specific
-   circumstances.
-  </para>
-
-  <para>
-   The optional <literal>RETURNING</> clause causes <command>DELETE</>
-   to compute and return value(s) based on each row actually deleted.
-   Any expression using the table's columns, and/or columns of other
-   tables mentioned in <literal>USING</literal>, can be computed.
-   The syntax of the <literal>RETURNING</> list is identical to that of the
-   output list of <command>SELECT</>.
-  </para>
-
-  <para>
-   You must have the <literal>DELETE</literal> privilege on the table
-   to delete from it, as well as the <literal>SELECT</literal>
-   privilege for any table in the <literal>USING</literal> clause or
-   whose values are read in the <replaceable
-   class="parameter">condition</replaceable>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">with_query</replaceable></term>
-    <listitem>
-<!## XC>
-     <para>
-      <replaceable class="parameter">with_query</replaceable> is not
-      supported by current release of <productname>Postgres-XC</>.
-     </para>
-<!## end>
-<!## XL>
-     <para>
-      <replaceable class="parameter">with_query</replaceable> is not
-      supported by current release of <productname>Postgres-XL</>.
-     </para>
-<!## end>
-<!## PG>
-     <para>
-      The <literal>WITH</literal> clause allows you to specify one or more
-      subqueries that can be referenced by name in the <command>DELETE</>
-      query. See <xref linkend="queries-with"> and <xref linkend="sql-select">
-      for details.
-     </para>
-<!## end>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ONLY</></term>
-    <listitem>
-     <para>
-      If specified, delete rows from the named table only.  When not
-      specified, any tables inheriting from the named table are also processed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">table</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">alias</replaceable></term>
-    <listitem>
-     <para>
-      A substitute name for the target table. When an alias is
-      provided, it completely hides the actual name of the table.  For
-      example, given <literal>DELETE FROM foo AS f</>, the remainder
-      of the <command>DELETE</command> statement must refer to this
-      table as <literal>f</> not <literal>foo</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">using_list</replaceable></term>
-    <listitem>
-     <para>
-      A list of table expressions, allowing columns from other tables
-      to appear in the <literal>WHERE</> condition.  This is similar
-      to the list of tables that can be specified in the <xref
-      linkend="sql-from" endterm="sql-from-title"> of a
-      <command>SELECT</command> statement; for example, an alias for
-      the table name can be specified.  Do not repeat the target table
-      in the <replaceable class="PARAMETER">using_list</replaceable>,
-      unless you wish to set up a self-join.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">condition</replaceable></term>
-    <listitem>
-     <para>
-      An expression that returns a value of type <type>boolean</type>.
-      Only rows for which this expression returns <literal>true</>
-      will be deleted.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">cursor_name</replaceable></term>
-    <listitem>
-     <para>
-&pgonly;
-      The name of the cursor to use in a <literal>WHERE CURRENT OF</>
-      condition.  The row to be deleted is the one most recently fetched
-      from this cursor.  The cursor must be a non-grouping
-      query on the <command>DELETE</>'s target table.
-      Note that <literal>WHERE CURRENT OF</> cannot be
-      specified together with a Boolean condition.  See
-      <xref linkend="sql-declare">
-      for more information about using cursors with
-      <literal>WHERE CURRENT OF</>.
-<!## XC>
-      <footnote>
-       <para>
-        <literal>WHERE CURRENT OF</literal> is not supported in the
-        current version of <productname>Postgres-XC</productname>.
-       </para>
-      </footnote>
-<!## end>
-<!## XL>
-      <footnote>
-       <para>
-        <literal>WHERE CURRENT OF</literal> is not supported in the
-        current version of <productname>Postgres-XL</productname>.
-       </para>
-      </footnote>
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">output_expression</replaceable></term>
-    <listitem>
-     <para>
-      An expression to be computed and returned by the <command>DELETE</>
-      command after each row is deleted.  The expression can use any
-      column names of the <replaceable class="PARAMETER">table</replaceable>
-      or table(s) listed in <literal>USING</>.
-      Write <literal>*</> to return all columns.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">output_name</replaceable></term>
-    <listitem>
-     <para>
-      A name to use for a returned column.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Outputs</title>
-
-  <para>
-   On successful completion, a <command>DELETE</> command returns a command
-   tag of the form
-<screen>
-DELETE <replaceable class="parameter">count</replaceable>
-</screen>
-   The <replaceable class="parameter">count</replaceable> is the number
-   of rows deleted.  If <replaceable class="parameter">count</replaceable> is
-   0, no rows matched the <replaceable
-   class="parameter">condition</replaceable> (this is not considered
-   an error).
-  </para>
-
-  <para>
-   If the <command>DELETE</> command contains a <literal>RETURNING</>
-   clause, the result will be similar to that of a <command>SELECT</>
-   statement containing the columns and values defined in the
-   <literal>RETURNING</> list, computed over the row(s) deleted by the
-   command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> lets you reference columns of
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> lets you reference columns of
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> lets you reference columns of
-<!## end>
-   other tables in the <literal>WHERE</> condition by specifying the
-   other tables in the <literal>USING</literal> clause.  For example,
-   to delete all films produced by a given producer, one can do:
-<programlisting>
-DELETE FROM films USING producers
-  WHERE producer_id = producers.id AND producers.name = 'foo';
-</programlisting>
-   What is essentially happening here is a join between <structname>films</>
-   and <structname>producers</>, with all successfully joined
-   <structname>films</> rows being marked for deletion.
-   This syntax is not standard.  A more standard way to do it is:
-<programlisting>
-DELETE FROM films
-  WHERE producer_id IN (SELECT id FROM producers WHERE name = 'foo');
-</programlisting>
-   In some cases the join style is easier to write or faster to
-   execute than the sub-select style.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Delete all films but musicals:
-<programlisting>
-DELETE FROM films WHERE kind &lt;&gt; 'Musical';
-</programlisting>
-  </para>
-
-  <para>
-   Clear the table <literal>films</literal>:
-<programlisting>
-DELETE FROM films;
-</programlisting>
-  </para>
-
-  <para>
-   Delete completed tasks, returning full details of the deleted rows:
-<programlisting>
-DELETE FROM tasks WHERE status = 'DONE' RETURNING *;
-</programlisting>
-  </para>
-
-<!## PG>
-<!-- NOTICE:
-     CURRENT OF not supported yet
--->
-   <para>
-   Delete the row of <structname>tasks</> on which the cursor
-   <literal>c_tasks</> is currently positioned:
-<programlisting>
-DELETE FROM tasks WHERE CURRENT OF c_tasks;
-</programlisting>
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   This command conforms to the <acronym>SQL</acronym> standard, except
-   that the <literal>USING</literal> and <literal>RETURNING</> clauses
-   are <productname>PostgreSQL</productname> extensions, as is the ability
-   to use <literal>WITH</> with <command>DELETE</>.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/discard.sgmlin b/doc-xc/src/sgml/ref/discard.sgmlin
deleted file mode 100644
index 2c90034dc3..0000000000
--- a/doc-xc/src/sgml/ref/discard.sgmlin
+++ /dev/null
@@ -1,111 +0,0 @@
-<!--
-doc/src/sgml/ref/discard.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DISCARD">
- <refmeta>
-  <refentrytitle>DISCARD</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DISCARD</refname>
-  <refpurpose>discard session state</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-discard">
-  <primary>DISCARD</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DISCARD { ALL | PLANS | TEMPORARY | TEMP }
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DISCARD</> releases internal resources associated with a
-   database session. These resources are normally released at the end
-   of the session.
-  </para>
-
-  <para>
-   <command>DISCARD TEMP</> drops all temporary tables created in the
-   current session.  <command>DISCARD PLANS</> releases all internally
-   cached query plans.  <command>DISCARD ALL</> resets a session to
-   its original state, discarding temporary resources and resetting
-   session-local configuration changes.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>TEMPORARY</literal> or <literal>TEMP</literal></term>
-    <listitem>
-     <para>
-      Drops all temporary tables created in the current session.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>PLANS</literal></term>
-    <listitem>
-     <para>
-      Releases all cached query plans.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ALL</literal></term>
-    <listitem>
-     <para>
-      Releases all temporary resources associated with the current
-      session and resets the session to its initial state.
-      Currently, this has the same effect as executing the following sequence
-      of statements:
-<programlisting>
-SET SESSION AUTHORIZATION DEFAULT;
-RESET ALL;
-DEALLOCATE ALL;
-CLOSE ALL;
-UNLISTEN *;
-SELECT pg_advisory_unlock_all();
-DISCARD PLANS;
-DISCARD TEMP;
-</programlisting>
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    <command>DISCARD ALL</> cannot be executed inside a transaction block.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>DISCARD</command> is a <productname>PostgreSQL</productname> extension.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/do.sgmlin b/doc-xc/src/sgml/ref/do.sgmlin
deleted file mode 100644
index 089276c6e1..0000000000
--- a/doc-xc/src/sgml/ref/do.sgmlin
+++ /dev/null
@@ -1,130 +0,0 @@
-<!--
-doc/src/sgml/ref/do.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DO">
- <refmeta>
-  <refentrytitle>DO</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DO</refname>
-  <refpurpose>execute an anonymous code block</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-do">
-  <primary>DO</primary>
- </indexterm>
-
- <indexterm zone="sql-do">
-  <primary>anonymous code blocks</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DO [ LANGUAGE <replaceable class="PARAMETER">lang_name</replaceable> ] <replaceable class="PARAMETER">code</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>DO</command> executes an anonymous code block, or in other
-   words a transient anonymous function in a procedural language.
-  </para>
-
-  <para>
-   The code block is treated as though it were the body of a function
-   with no parameters, returning <type>void</>.  It is parsed and
-   executed a single time.
-  </para>
-
-  <para>
-   The optional <literal>LANGUAGE</> clause can be written either
-   before or after the code block.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">code</replaceable></term>
-    <listitem>
-     <para>
-      The procedural language code to be executed.  This must be specified
-      as a string literal, just as in <command>CREATE FUNCTION</>.
-      Use of a dollar-quoted literal is recommended.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">lang_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the procedural language the code is written in.
-      If omitted, the default is <literal>plpgsql</>.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   The procedural language to be used must already have been installed
-   into the current database by means of <command>CREATE LANGUAGE</>.
-   <literal>plpgsql</> is installed by default, but other languages are not.
-  </para>
-
-  <para>
-   The user must have <literal>USAGE</> privilege for the procedural
-   language, or must be a superuser if the language is untrusted.
-   This is the same privilege requirement as for creating a function
-   in the language.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-do-examples">
-  <title id="sql-do-examples-title">Examples</title>
-  <para>
-   Grant all privileges on all views in schema <literal>public</> to
-   role <literal>webuser</>:
-<programlisting>
-DO $$DECLARE r record;
-BEGIN
-    FOR r IN SELECT table_schema, table_name FROM information_schema.tables
-             WHERE table_type = 'VIEW' AND table_schema = 'public'
-    LOOP
-        EXECUTE 'GRANT ALL ON ' || quote_ident(r.table_schema) || '.' || quote_ident(r.table_name) || ' TO webuser';
-    END LOOP;
-END$$;
-</programlisting>
-  </para>
- </refsect1>
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DO</command> statement in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createlanguage"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_aggregate.sgmlin b/doc-xc/src/sgml/ref/drop_aggregate.sgmlin
deleted file mode 100644
index 2c843382e8..0000000000
--- a/doc-xc/src/sgml/ref/drop_aggregate.sgmlin
+++ /dev/null
@@ -1,126 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_aggregate.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPAGGREGATE">
- <refmeta>
-  <refentrytitle>DROP AGGREGATE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP AGGREGATE</refname>
-  <refpurpose>remove an aggregate function</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropaggregate">
-  <primary>DROP AGGREGATE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP AGGREGATE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> ( <replaceable class="PARAMETER">type</replaceable> [ , ... ] ) [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP AGGREGATE</command> removes an existing
-   aggregate function. To execute this command the current
-   user must be the owner of the aggregate function.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-&common;
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the aggregate does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing aggregate function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">type</replaceable></term>
-    <listitem>
-     <para>
-      An input data type on which the aggregate function operates.
-      To reference a zero-argument aggregate function, write <literal>*</>
-      in place of the list of input data types.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the aggregate function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the aggregate function if any objects depend on
-      it.  This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-&common;
-  <para>
-   To remove the aggregate function <literal>myavg</literal> for type
-   <type>integer</type>:
-<programlisting>
-DROP AGGREGATE myavg(integer);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP AGGREGATE</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alteraggregate"></member>
-   <member><xref linkend="sql-createaggregate"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_cast.sgmlin b/doc-xc/src/sgml/ref/drop_cast.sgmlin
deleted file mode 100644
index 49e0133686..0000000000
--- a/doc-xc/src/sgml/ref/drop_cast.sgmlin
+++ /dev/null
@@ -1,117 +0,0 @@
-<!-- doc/src/sgml/ref/drop_cast.sgml -->
-
-<refentry id="SQL-DROPCAST">
- <refmeta>
-  <refentrytitle>DROP CAST</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP CAST</refname>
-  <refpurpose>remove a cast</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropcast">
-  <primary>DROP CAST</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP CAST [ IF EXISTS ] (<replaceable>source_type</replaceable> AS <replaceable>target_type</replaceable>) [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-dropcast-description">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP CAST</command> removes a previously defined cast.
-  </para>
-
-  <para>
-   To be able to drop a cast, you must own the source or the target
-   data type.  These are the same privileges that are required to
-   create a cast.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-   <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the cast does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>source_type</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the source data type of the cast.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>target_type</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the target data type of the cast.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>CASCADE</literal></term>
-     <term><literal>RESTRICT</literal></term>
-
-     <listitem>
-      <para>
-       These key words do not have any effect, since there are no
-       dependencies on casts.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
- </refsect1>
-
- <refsect1 id="sql-dropcast-examples">
-  <title>Examples</title>
-
-  <para>
-   To drop the cast from type <type>text</type> to type <type>int</type>:
-<programlisting>
-DROP CAST (text AS int);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="sql-dropcast-compat">
-  <title>Compatibility</title>
-
-  <para>
-   The <command>DROP CAST</command> command conforms to the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createcast"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_collation.sgmlin b/doc-xc/src/sgml/ref/drop_collation.sgmlin
deleted file mode 100644
index 0afcaaf2de..0000000000
--- a/doc-xc/src/sgml/ref/drop_collation.sgmlin
+++ /dev/null
@@ -1,110 +0,0 @@
-<!-- doc/src/sgml/ref/drop_collation.sgml -->
-
-<refentry id="SQL-DROPCOLLATION">
- <refmeta>
-  <refentrytitle>DROP COLLATION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP COLLATION</refname>
-  <refpurpose>remove a collation</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropcollation">
-  <primary>DROP COLLATION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP COLLATION [ IF EXISTS ] <replaceable>name</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-dropcollation-description">
-  <title>Description</title>
-
-  <para>
-   <command>DROP COLLATION</command> removes a previously defined collation.
-   To be able to drop a collation, you must own the collation.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>IF EXISTS</literal></term>
-     <listitem>
-      <para>
-       Do not throw an error if the collation does not exist.
-       A notice is issued in this case.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>name</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the collation. The collation name can be
-       schema-qualified.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>CASCADE</literal></term>
-     <listitem>
-      <para>
-       Automatically drop objects that depend on the collation.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>RESTRICT</literal></term>
-     <listitem>
-      <para>
-       Refuse to drop the collation if any objects depend on it.  This
-       is the default.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
- </refsect1>
-
- <refsect1 id="sql-dropcollation-examples">
-  <title>Examples</title>
-
-  <para>
-   To drop the collation named <literal>german</>:
-<programlisting>
-DROP COLLATION german;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="sql-dropcollation-compat">
-  <title>Compatibility</title>
-
-  <para>
-   The <command>DROP COLLATION</command> command conforms to the
-   <acronym>SQL</acronym> standard, apart from the <literal>IF
-   EXISTS</> option, which is a <productname>PostgreSQL</> extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altercollation"></member>
-   <member><xref linkend="sql-createcollation"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_conversion.sgmlin b/doc-xc/src/sgml/ref/drop_conversion.sgmlin
deleted file mode 100644
index 8079234d2d..0000000000
--- a/doc-xc/src/sgml/ref/drop_conversion.sgmlin
+++ /dev/null
@@ -1,115 +0,0 @@
-<!-- doc/src/sgml/ref/drop_conversion.sgml -->
-
-<refentry id="SQL-DROPCONVERSION">
- <refmeta>
-  <refentrytitle>DROP CONVERSION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP CONVERSION</refname>
-  <refpurpose>remove a conversion</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropconversion">
-  <primary>DROP CONVERSION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP CONVERSION [ IF EXISTS ] <replaceable>name</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-dropconversion-description">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP CONVERSION</command> removes a previously defined conversion.
-   To be able to drop a conversion, you must own the conversion.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>IF EXISTS</literal></term>
-     <listitem>
-      <para>
-       Do not throw an error if the conversion does not exist.
-       A notice is issued in this case.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>name</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the conversion. The conversion name can be
-       schema-qualified.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>CASCADE</literal></term>
-     <term><literal>RESTRICT</literal></term>
-
-     <listitem>
-      <para>
-       These key words do not have any effect, since there are no
-       dependencies on conversions.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
- </refsect1>
-
- <refsect1 id="sql-dropconversion-examples">
-  <title>Examples</title>
-
-  <para>
-   To drop the conversion named <literal>myname</>:
-<programlisting>
-DROP CONVERSION myname;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="sql-dropconversion-compat">
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP CONVERSION</command> statement in the SQL
-   standard, but a <command>DROP TRANSLATION</command> statement that
-   goes along with the <command>CREATE TRANSLATION</command> statement
-   that is similar to the <command>CREATE CONVERSION</command>
-<!## PG>
-   statement in PostgreSQL.
-<!## end>
-<!## XC>
-   statement in Postgres-XC.
-<!## end>
-<!## XL>
-   statement in Postgres-XL.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterconversion"></member>
-   <member><xref linkend="sql-createconversion"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_database.sgmlin b/doc-xc/src/sgml/ref/drop_database.sgmlin
deleted file mode 100644
index 5cc2d6b5ba..0000000000
--- a/doc-xc/src/sgml/ref/drop_database.sgmlin
+++ /dev/null
@@ -1,123 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_database.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPDATABASE">
- <refmeta>
-  <refentrytitle>DROP DATABASE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP DATABASE</refname>
-  <refpurpose>remove a database</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropdatabase">
-  <primary>DROP DATABASE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP DATABASE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP DATABASE</command> drops a database. It removes the
-   catalog entries for the database and deletes the directory
-   containing the data.  It can only be executed by the database owner.
-   Also, it cannot be executed while you or anyone else are connected
-   to the target database.  (Connect to <literal>postgres</literal> or any
-   other database to issue this command.)
-  </para>
-
-  <para>
-   <command>DROP DATABASE</command> cannot be undone.  Use it with care!
-  </para>
-
-<!## XC>
-&xconly;
-   <para>
-    If there's any live connection to any of the template database in
-    Coordinator or Datanode, you will have an error message.  In this
-    case, you should clean these connections using <command>CLEAN
-    CONNECITON</> statement.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    If there are any live connections to any of the template databases in
-    a Coordinator or Datanode, you will receive an error message.  In this
-    case, you should clean these connections using <command>CLEAN
-    CONNECITON</> statement.
-   </para>
-<!## end>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the database does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the database to remove.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    <command>DROP DATABASE</> cannot be executed inside a transaction
-    block.
-   </para>
-
-  <para>
-   This command cannot be executed while connected to the target
-   database. Thus, it might be more convenient to use the program
-   <xref linkend="app-dropdb"> instead,
-   which is a wrapper around this command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP DATABASE</command> statement in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createdatabase"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_domain.sgmlin b/doc-xc/src/sgml/ref/drop_domain.sgmlin
deleted file mode 100644
index e1e70f0dd5..0000000000
--- a/doc-xc/src/sgml/ref/drop_domain.sgmlin
+++ /dev/null
@@ -1,125 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_domain.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPDOMAIN">
- <refmeta>
-  <refentrytitle>DROP DOMAIN</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP DOMAIN</refname>
-  <refpurpose>remove a domain</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropdomain">
-  <primary>DROP DOMAIN</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP DOMAIN [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP DOMAIN</command> removes a domain.  Only the owner of
-   a domain can remove it.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the domain does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing domain.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the domain (such as
-      table columns).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</></term>
-    <listitem>
-     <para>
-      Refuse to drop the domain if any objects depend on it.  This is
-      the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1 id="SQL-DROPDOMAIN-examples">
-  <title>Examples</title>
-
-  <para>
-   To remove the domain <type>box</type>:
-
-<programlisting>
-DROP DOMAIN box;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPDOMAIN-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   This command conforms to the SQL standard, except for the
-<!## PG>
-   <literal>IF EXISTS</> option, which is a <productname>PostgreSQL</>
-   extension.
-<!## end>
-<!## XC>
-   <literal>IF EXISTS</> option, which is a <productname>Postgres-XC</>
-   extension inheritedofrm <productname>PostgreSQL</>.
-<!## end>
-<!## XL>
-   <literal>IF EXISTS</> option, which is a <productname>Postgres-XL</>
-   extension inheritedofrm <productname>PostgreSQL</>.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPDOMAIN-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createdomain"></member>
-   <member><xref linkend="sql-alterdomain"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_extension.sgmlin b/doc-xc/src/sgml/ref/drop_extension.sgmlin
deleted file mode 100644
index 979a6ebc15..0000000000
--- a/doc-xc/src/sgml/ref/drop_extension.sgmlin
+++ /dev/null
@@ -1,121 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_extension.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPEXTENSION">
- <refmeta>
-  <refentrytitle>DROP EXTENSION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP EXTENSION</refname>
-  <refpurpose>remove an extension</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropextension">
-  <primary>DROP EXTENSION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP EXTENSION [ IF EXISTS ] <replaceable class="PARAMETER">extension_name</replaceable> [, ...] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>DROP EXTENSION</command> removes extensions from the database.
-   Dropping an extension causes its component objects to be dropped as well.
-  </para>
-
-  <para>
-   You must own the extension to use <command>DROP EXTENSION</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the extension does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">extension_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an installed extension.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the extension.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the extension if any objects depend on it (other than
-      its own member objects and other extensions listed in the same
-      <command>DROP</> command).  This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To remove the extension <literal>hstore</literal> from the current
-   database:
-<programlisting>
-DROP EXTENSION hstore;
-</programlisting>
-   This command will fail if any of <literal>hstore</literal>'s objects
-   are in use in the database, for example if any tables have columns
-   of the <type>hstore</> type.  Add the <literal>CASCADE</> option to
-   forcibly remove those dependent objects as well.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>DROP EXTENSION</command> is a <productname>PostgreSQL</>
-   extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createextension"></member>
-   <member><xref linkend="sql-alterextension"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_foreign_data_wrapper.sgmlin b/doc-xc/src/sgml/ref/drop_foreign_data_wrapper.sgmlin
deleted file mode 100644
index fd1efe30b4..0000000000
--- a/doc-xc/src/sgml/ref/drop_foreign_data_wrapper.sgmlin
+++ /dev/null
@@ -1,133 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_foreign_data_wrapper.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPFOREIGNDATAWRAPPER">
- <refmeta>
-  <refentrytitle>DROP FOREIGN DATA WRAPPER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP FOREIGN DATA WRAPPER</refname>
-  <refpurpose>remove a foreign-data wrapper</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropforeigndatawrapper">
-  <primary>DROP FOREIGN DATA WRAPPER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP FOREIGN DATA WRAPPER [ IF EXISTS ] <replaceable class="parameter">name</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-<!## XC>
-&xconly;
-  <para>
-   <command>FOREIGN DATA WRAPPER</> has not been supported
-   by <productname>Postgres-XC</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>FOREIGN DATA WRAPPER</> is not yet supported
-   in <productname>Postgres-XL</>.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-&pgonly;
-
-  <para>
-   <command>DROP FOREIGN DATA WRAPPER</command> removes an existing
-   foreign-data wrapper.  To execute this command, the current user
-   must be the owner of the foreign-data wrapper.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the foreign-data wrapper does not
-      exist.  A notice is issued in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing foreign-data wrapper.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the foreign-data
-      wrapper (such as servers).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the foreign-data wrappers if any objects depend
-      on it.  This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Drop the foreign-data wrapper <literal>dbi</>:
-<programlisting>
-DROP FOREIGN DATA WRAPPER dbi;
-</programlisting>
-  </para>
-
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>DROP FOREIGN DATA WRAPPER</command> conforms to ISO/IEC
-   9075-9 (SQL/MED).  The <literal>IF EXISTS</> clause is
-   a <productname>PostgreSQL</> extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createforeigndatawrapper"></member>
-   <member><xref linkend="sql-alterforeigndatawrapper"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_foreign_table.sgmlin b/doc-xc/src/sgml/ref/drop_foreign_table.sgmlin
deleted file mode 100644
index 71f26465bb..0000000000
--- a/doc-xc/src/sgml/ref/drop_foreign_table.sgmlin
+++ /dev/null
@@ -1,112 +0,0 @@
-<!-- doc/src/sggml/ref/drop_foreign_table.sgml -->
-
-<refentry id="SQL-DROPFOREIGNTABLE">
- <refmeta>
-  <refentrytitle>DROP FOREIGN TABLE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP FOREIGN TABLE</refname>
-  <refpurpose>remove a foreign table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropforeigntable">
-  <primary>DROP FOREIGN TABLE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP FOREIGN TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
- 
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>DROP FOREIGN TABLE</command> removes a foreign table.
-   Only the owner of a foreign table can remove it.
-  </para>
- </refsect1>
-  
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the foreign table does not exist.
-      A notice is issued in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the foreign table to drop.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the foreign table (such as
-      views).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the foreign table if any objects depend on it.  This is
-      the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To destroy two foreign tables, <literal>films</literal> and 
-   <literal>distributors</literal>:
-
-<programlisting>
-DROP FOREIGN TABLE films, distributors;
-</programlisting>
-  </para>
- </refsect1>
- 
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   This command conforms to the ISO/IEC 9075-9 (SQL/MED), except that the
-   standard only allows one foreign table to be dropped per command, and apart
-   from the <literal>IF EXISTS</> option, which is a <productname>PostgreSQL</>
-   extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterforeigntable"></member>
-   <member><xref linkend="sql-createforeigntable"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_function.sgmlin b/doc-xc/src/sgml/ref/drop_function.sgmlin
deleted file mode 100644
index 18c4443cb2..0000000000
--- a/doc-xc/src/sgml/ref/drop_function.sgmlin
+++ /dev/null
@@ -1,159 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_function.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPFUNCTION">
- <refmeta>
-  <refentrytitle>DROP FUNCTION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP FUNCTION</refname>
-  <refpurpose>remove a function</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropfunction">
-  <primary>DROP FUNCTION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP FUNCTION [ IF EXISTS ] <replaceable class="parameter">name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">argname</replaceable> ] <replaceable class="parameter">argtype</replaceable> [, ...] ] )
-    [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>DROP FUNCTION</command> removes the definition of an existing
-   function. To execute this command the user must be the
-   owner of the function. The argument types to the
-   function must be specified, since several different functions
-   can exist with the same name and different argument lists.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-    <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the function does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing function.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argmode</replaceable></term>
-
-    <listitem>
-     <para>
-      The mode of an argument: <literal>IN</>, <literal>OUT</>,
-      <literal>INOUT</>, or <literal>VARIADIC</>.
-      If omitted, the default is <literal>IN</>.
-      Note that <command>DROP FUNCTION</command> does not actually pay
-      any attention to <literal>OUT</> arguments, since only the input
-      arguments are needed to determine the function's identity.
-      So it is sufficient to list the <literal>IN</>, <literal>INOUT</>,
-      and <literal>VARIADIC</> arguments.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argname</replaceable></term>
-
-    <listitem>
-     <para>
-      The name of an argument.
-      Note that <command>DROP FUNCTION</command> does not actually pay
-      any attention to argument names, since only the argument data
-      types are needed to determine the function's identity.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argtype</replaceable></term>
-
-    <listitem>
-     <para>
-      The data type(s) of the function's arguments (optionally
-      schema-qualified), if any.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the function (such as
-      operators or triggers).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the function if any objects depend on it.  This
-      is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1 id="SQL-DROPFUNCTION-examples">
-  <title>Examples</title>
-
-  <para>
-   This command removes the square root function:
-
-<programlisting>
-DROP FUNCTION sqrt(integer);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPFUNCTION-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   A <command>DROP FUNCTION</command> statement is defined in the SQL
-   standard, but it is not compatible with this command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createfunction"></member>
-   <member><xref linkend="sql-alterfunction"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_group.sgmlin b/doc-xc/src/sgml/ref/drop_group.sgmlin
deleted file mode 100644
index efbdb6194d..0000000000
--- a/doc-xc/src/sgml/ref/drop_group.sgmlin
+++ /dev/null
@@ -1,55 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_group.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPGROUP">
- <refmeta>
-  <refentrytitle>DROP GROUP</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP GROUP</refname>
-  <refpurpose>remove a database role</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropgroup">
-  <primary>DROP GROUP</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP GROUP [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>DROP GROUP</command> is now an alias for
-   <xref linkend="sql-droprole">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP GROUP</command> statement in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-droprole"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_index.sgmlin b/doc-xc/src/sgml/ref/drop_index.sgmlin
deleted file mode 100644
index 85b5449d8b..0000000000
--- a/doc-xc/src/sgml/ref/drop_index.sgmlin
+++ /dev/null
@@ -1,122 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_index.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPINDEX">
- <refmeta>
-  <refentrytitle>DROP INDEX</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP INDEX</refname>
-  <refpurpose>remove an index</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropindex">
-  <primary>DROP INDEX</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP INDEX [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP INDEX</command> drops an existing index from the database
-   system. To execute this command you must be the owner of
-   the index.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the index does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an index to remove.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the index.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the index if any objects depend on it.  This is
-      the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   This command will remove the index <literal>title_idx</literal>:
-
-<programlisting>
-DROP INDEX title_idx;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>DROP INDEX</command> is a
-<!## PG>
-   <productname>PostgreSQL</productname> language extension.  There
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> language extension.  There
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> language extension.  There
-<!## end>
-   are no provisions for indexes in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createindex"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_language.sgmlin b/doc-xc/src/sgml/ref/drop_language.sgmlin
deleted file mode 100644
index c81e70cbab..0000000000
--- a/doc-xc/src/sgml/ref/drop_language.sgmlin
+++ /dev/null
@@ -1,128 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_language.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPLANGUAGE">
- <refmeta>
-  <refentrytitle>DROP LANGUAGE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP LANGUAGE</refname>
-  <refpurpose>remove a procedural language</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droplanguage">
-  <primary>DROP LANGUAGE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP [ PROCEDURAL ] LANGUAGE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP LANGUAGE</command> removes the definition of a
-   previously registered procedural language.  You must be a superuser
-   or the owner of the language to use <command>DROP LANGUAGE</>.
-  </para>
-
-  <note>
-   <para>
-    As of <productname>PostgreSQL</productname> 9.1, most procedural
-    languages have been made into <quote>extensions</>, and should
-    therefore be removed with <xref linkend="sql-dropextension">
-    not <command>DROP LANGUAGE</command>.
-   </para>
-  </note>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the language does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing procedural language.  For backward
-      compatibility, the name can be enclosed by single quotes.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the language (such as
-      functions in the language).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the language if any objects depend on it.  This
-      is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   This command removes the procedural language
-   <literal>plsample</literal>:
-
-<programlisting>
-DROP LANGUAGE plsample;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP LANGUAGE</command> statement in the SQL
-   standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterlanguage"></member>
-   <member><xref linkend="sql-createlanguage"></member>
-   <member><xref linkend="app-droplang"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_node.sgmlin b/doc-xc/src/sgml/ref/drop_node.sgmlin
deleted file mode 100644
index 3b9e9adad1..0000000000
--- a/doc-xc/src/sgml/ref/drop_node.sgmlin
+++ /dev/null
@@ -1,168 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/drop_node.sgml,v 1.54 2010/04/03 07:22:58 petere Exp $
-PostgreSQL documentation
--->
-<!## XC>
-<refentry id="SQL-DROPNODE">
- <refmeta>
-  <refentrytitle>DROP NODE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP NODE</refname>
-  <refpurpose>drop a cluster node</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropnode">
-  <primary>DROP NODE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP NODE <replaceable class="parameter">nodename</replaceable>
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xconly;
-
-  <para>
-   <command>DROP NODE</command> is new SQL query specific
-   to <productname>Postgres-XC</productname> since 0.9.7 that deletes
-   cluster node information in catalog pgxc_node.
-  </para>
-  <para>
-   Node connection that has been deleted does not guarranty that connection
-   information cached in pooler is updated accordingly.
-  </para>
-  <para>
-   <command>DROP NODE</command> only runs on the local node where it is launched.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">nodename</replaceable></term>
-      <listitem>
-       <para>
-        The name of the selected cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Drop a cluster node.
-<programlisting>
-DROP NODE cluster_node;
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>DROP NODE</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XC specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
-<!## XL>
-<refentry id="SQL-DROPNODE">
- <refmeta>
-  <refentrytitle>DROP NODE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP NODE</refname>
-  <refpurpose>drop a cluster node</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropnode">
-  <primary>DROP NODE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP NODE <replaceable class="parameter">nodename</replaceable>
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xlonly;
-
-  <para>
-   <command>DROP NODE</command> is new SQL command specific
-   to <productname>Postgres-XL</productname> that deletes
-   cluster node information in catalog pgxc_node.
-  </para>
-  <para>
-   Node connection that has been deleted does not guarantee that connection
-   information cached in pooler is updated accordingly.
-  </para>
-  <para>
-   <command>DROP NODE</command> only runs on the local node where it is launched.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">nodename</replaceable></term>
-      <listitem>
-       <para>
-        The name of the selected cluster node.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Drop a cluster node.
-<programlisting>
-DROP NODE cluster_node;
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>DROP NODE</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XL specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
diff --git a/doc-xc/src/sgml/ref/drop_nodegroup.sgmlin b/doc-xc/src/sgml/ref/drop_nodegroup.sgmlin
deleted file mode 100644
index c3906bb796..0000000000
--- a/doc-xc/src/sgml/ref/drop_nodegroup.sgmlin
+++ /dev/null
@@ -1,162 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/drop_nodegroup.sgml,v 1.54 2010/04/03 07:22:58 petere Exp $
-PostgreSQL documentation
--->
-<!## XC>
-<refentry id="SQL-DROPNODEGROUP">
- <refmeta>
-  <refentrytitle>DROP NODE GROUP</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP NODE GROUP</refname>
-  <refpurpose>drop a group of cluster nodes</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropnodegroup">
-  <primary>DROP NODE GROUP</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP NODE GROUP <replaceable class="parameter">groupname</replaceable>
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xconly;
-
-  <para>
-   <command>DROP NODE GROUP</command> is new SQL query specific
-   to <productname>Postgres-XC</productname> since 0.9.7 that deletes
-   node group information in catalog pgxc_group.
-  </para>
-  <para>
-   A group of nodes works as an alias for node lists when defining tables
-   on sub-clusters.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">groupname</replaceable></term>
-      <listitem>
-       <para>
-        The name of the selected cluster node group.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Drop a cluster node group.
-<programlisting>
-DROP NODE GROUP cluster_group;
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>DROP NODE GROUP</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XC specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
-<!## XL>
-<refentry id="SQL-DROPNODEGROUP">
- <refmeta>
-  <refentrytitle>DROP NODE GROUP</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP NODE GROUP</refname>
-  <refpurpose>drop a group of cluster nodes</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropnodegroup">
-  <primary>DROP NODE GROUP</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP NODE GROUP <replaceable class="parameter">groupname</replaceable>
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xlonly;
-
-  <para>
-   <command>DROP NODE GROUP</command> is SQL command specific
-   to <productname>Postgres-XL</productname> that deletes
-   node group information in catalog pgxc_group.
-  </para>
-  <para>
-   A group of nodes works as an alias for node lists when defining tables
-   on sub-clusters.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">groupname</replaceable></term>
-      <listitem>
-       <para>
-        The name of the selected cluster node group.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Drop a cluster node group.
-<programlisting>
-DROP NODE GROUP cluster_group;
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>DROP NODE GROUP</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XL specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
diff --git a/doc-xc/src/sgml/ref/drop_opclass.sgmlin b/doc-xc/src/sgml/ref/drop_opclass.sgmlin
deleted file mode 100644
index 2af1ff30c8..0000000000
--- a/doc-xc/src/sgml/ref/drop_opclass.sgmlin
+++ /dev/null
@@ -1,149 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_opclass.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPOPCLASS">
- <refmeta>
-  <refentrytitle>DROP OPERATOR CLASS</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP OPERATOR CLASS</refname>
-  <refpurpose>remove an operator class</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropopclass">
-  <primary>DROP OPERATOR CLASS</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP OPERATOR CLASS [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> USING <replaceable class="PARAMETER">index_method</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP OPERATOR CLASS</command> drops an existing operator class.
-   To execute this command you must be the owner of the operator class.
-  </para>
-
-  <para>
-   <command>DROP OPERATOR CLASS</command> does not drop any of the operators
-   or functions referenced by the class.  If there are any indexes depending
-   on the operator class, you will need to specify
-   <literal>CASCADE</> for the drop to complete.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the operator class does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing operator class.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">index_method</replaceable></term>
-    <listitem>
-     <para>
-      The name of the index access method the operator class is for.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the operator class.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the operator class if any objects depend on it.
-      This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <command>DROP OPERATOR CLASS</> will not drop the operator family
-   containing the class, even if there is nothing else left in the
-   family (in particular, in the case where the family was implicitly
-   created by <command>CREATE OPERATOR CLASS</>).  An empty operator
-   family is harmless, but for the sake of tidiness you might wish to
-   remove the family with <command>DROP OPERATOR FAMILY</>; or perhaps
-   better, use <command>DROP OPERATOR FAMILY</> in the first place.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Remove the B-tree operator class <literal>widget_ops</literal>:
-
-<programlisting>
-DROP OPERATOR CLASS widget_ops USING btree;
-</programlisting>
-
-   This command will not succeed if there are any existing indexes
-   that use the operator class.  Add <literal>CASCADE</> to drop
-   such indexes along with the operator class.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP OPERATOR CLASS</command> statement in the
-   SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alteropclass"></member>
-   <member><xref linkend="sql-createopclass"></member>
-   <member><xref linkend="sql-dropopfamily"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_operator.sgmlin b/doc-xc/src/sgml/ref/drop_operator.sgmlin
deleted file mode 100644
index a6511cebcb..0000000000
--- a/doc-xc/src/sgml/ref/drop_operator.sgmlin
+++ /dev/null
@@ -1,149 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_operator.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPOPERATOR">
- <refmeta>
-  <refentrytitle>DROP OPERATOR</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP OPERATOR</refname>
-  <refpurpose>remove an operator</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropoperator">
-  <primary>DROP OPERATOR</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP OPERATOR [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> ( { <replaceable class="PARAMETER">left_type</replaceable> | NONE } , { <replaceable class="PARAMETER">right_type</replaceable> | NONE } ) [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP OPERATOR</command> drops an existing operator from
-   the database system.  To execute this command you must be the owner
-   of the operator.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the operator does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing operator.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">left_type</replaceable></term>
-    <listitem>
-     <para>
-      The data type of the operator's left operand; write
-      <literal>NONE</literal> if the operator has no left operand.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">right_type</replaceable></term>
-    <listitem>
-     <para>
-      The data type of the operator's right operand; write
-      <literal>NONE</literal> if the operator has no right operand.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the operator.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the operator if any objects depend on it.  This
-      is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Remove the power operator <literal>a^b</literal> for type <type>integer</type>:
-<programlisting>
-DROP OPERATOR ^ (integer, integer);
-</programlisting>
-  </para>
-
-  <para>
-   Remove the left unary bitwise complement operator
-   <literal>~b</literal> for type <type>bit</type>:
-<programlisting>
-DROP OPERATOR ~ (none, bit);
-</programlisting>
-  </para>
-
-  <para>
-   Remove the right unary factorial operator <literal>x!</literal>
-   for type <type>bigint</type>:
-<programlisting>
-DROP OPERATOR ! (bigint, none);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP OPERATOR</command> statement in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createoperator"></member>
-   <member><xref linkend="sql-alteroperator"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_opfamily.sgmlin b/doc-xc/src/sgml/ref/drop_opfamily.sgmlin
deleted file mode 100644
index f89bc1acc1..0000000000
--- a/doc-xc/src/sgml/ref/drop_opfamily.sgmlin
+++ /dev/null
@@ -1,138 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_opfamily.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPOPFAMILY">
- <refmeta>
-  <refentrytitle>DROP OPERATOR FAMILY</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP OPERATOR FAMILY</refname>
-  <refpurpose>remove an operator family</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropopfamily">
-  <primary>DROP OPERATOR FAMILY</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP OPERATOR FAMILY [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> USING <replaceable class="PARAMETER">index_method</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP OPERATOR FAMILY</command> drops an existing operator family.
-   To execute this command you must be the owner of the operator family.
-  </para>
-
-  <para>
-   <command>DROP OPERATOR FAMILY</command> includes dropping any operator
-   classes contained in the family, but it does not drop any of the operators
-   or functions referenced by the family.  If there are any indexes depending
-   on operator classes within the family, you will need to specify
-   <literal>CASCADE</> for the drop to complete.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the operator family does not exist.
-      A notice is issued in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing operator family.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">index_method</replaceable></term>
-    <listitem>
-     <para>
-      The name of the index access method the operator family is for.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the operator family.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the operator family if any objects depend on it.
-      This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Remove the B-tree operator family <literal>float_ops</literal>:
-
-<programlisting>
-DROP OPERATOR FAMILY float_ops USING btree;
-</programlisting>
-
-   This command will not succeed if there are any existing indexes
-   that use operator classes within the family.  Add <literal>CASCADE</> to
-   drop such indexes along with the operator family.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP OPERATOR FAMILY</command> statement in the
-   SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alteropfamily"></member>
-   <member><xref linkend="sql-createopfamily"></member>
-   <member><xref linkend="sql-alteropclass"></member>
-   <member><xref linkend="sql-createopclass"></member>
-   <member><xref linkend="sql-dropopclass"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_owned.sgmlin b/doc-xc/src/sgml/ref/drop_owned.sgmlin
deleted file mode 100644
index 562854d995..0000000000
--- a/doc-xc/src/sgml/ref/drop_owned.sgmlin
+++ /dev/null
@@ -1,128 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_owned.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROP-OWNED">
- <refmeta>
-  <refentrytitle>DROP OWNED</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP OWNED</refname>
-  <refpurpose>remove database objects owned by a database role</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-drop-owned">
-  <primary>DROP OWNED</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP OWNED BY <replaceable class="PARAMETER">name</replaceable> [, ...] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP OWNED</command> drops all the objects in the current
-   database that are owned by one of the specified roles. Any
-   privileges granted to the given roles on objects in the current
-   database will also be revoked.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of a role whose objects will be dropped, and whose
-      privileges will be revoked.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the affected objects.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the objects owned by a role if any other database
-      objects depend on one of the affected objects. This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-  <para>
-   <command>DROP OWNED</command> is often used to prepare for the
-   removal of one or more roles. Because <command>DROP OWNED</command>
-   only affects the objects in the current database, it is usually
-   necessary to execute this command in each database that contains
-   objects owned by a role that is to be removed.
-  </para>
-
-  <para>
-   Using the <literal>CASCADE</literal> option might make the command
-   recurse to objects owned by other users.
-  </para>
-
-  <para>
-   The <xref linkend="sql-reassign-owned"> command is an alternative that
-   reassigns the ownership of all the database objects owned by one or
-   more roles.
-  </para>
-
-  <para>
-   Databases owned by the role(s) will not be removed.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The <command>DROP OWNED</command> statement is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-reassign-owned"></member>
-   <member><xref linkend="sql-droprole"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_role.sgmlin b/doc-xc/src/sgml/ref/drop_role.sgmlin
deleted file mode 100644
index 12f967a7db..0000000000
--- a/doc-xc/src/sgml/ref/drop_role.sgmlin
+++ /dev/null
@@ -1,141 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_role.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPROLE">
- <refmeta>
-  <refentrytitle>DROP ROLE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP ROLE</refname>
-  <refpurpose>remove a database role</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droprole">
-  <primary>DROP ROLE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP ROLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP ROLE</command> removes the specified role(s).
-   To drop a superuser role, you must be a superuser yourself;
-   to drop non-superuser roles, you must have <literal>CREATEROLE</>
-   privilege.
-  </para>
-
-  <para>
-   A role cannot be removed if it is still referenced in any database
-   of the cluster; an error will be raised if so.  Before dropping the role,
-   you must drop all the objects it owns (or reassign their ownership)
-   and revoke any privileges the role has been granted. The <xref
-   linkend="sql-reassign-owned">
-   and <xref linkend="sql-drop-owned">
-   commands can be useful for this purpose.
-  </para>
-
-  <para>
-   However, it is not necessary to remove role memberships involving
-   the role; <command>DROP ROLE</> automatically revokes any memberships
-   of the target role in other roles, and of other roles in the target role.
-   The other roles are not dropped nor otherwise affected.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the role does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the role to remove.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> includes a program <xref
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> includes a program <xref
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> includes a program <xref
-<!## end>
-   linkend="APP-DROPUSER"> that has the
-   same functionality as this command (in fact, it calls this command)
-   but can be run from the command shell.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To drop a role:
-<programlisting>
-DROP ROLE jonathan;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard defines <command>DROP ROLE</command>, but it allows
-   only one role to be dropped at a time, and it specifies different
-<!## PG>
-   privilege requirements than <productname>PostgreSQL</productname> uses.
-<!## end>
-<!## XC>
-   privilege requirements than <productname>Postgres-XC</productname> uses.
-<!## end>
-<!## XL>
-   privilege requirements than <productname>Postgres-XL</productname> uses.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createrole"></member>
-   <member><xref linkend="sql-alterrole"></member>
-   <member><xref linkend="sql-set-role"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_rule.sgmlin b/doc-xc/src/sgml/ref/drop_rule.sgmlin
deleted file mode 100644
index f7d4221d36..0000000000
--- a/doc-xc/src/sgml/ref/drop_rule.sgmlin
+++ /dev/null
@@ -1,121 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_rule.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPRULE">
- <refmeta>
-  <refentrytitle>DROP RULE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP RULE</refname>
-  <refpurpose>remove a rewrite rule</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droprule">
-  <primary>DROP RULE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP RULE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> ON <replaceable class="PARAMETER">table</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP RULE</command> drops a rewrite rule.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the rule does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the rule to drop.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">table</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the table or view that
-      the rule applies to.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the rule.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the rule if any objects depend on it.  This is
-      the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To drop the rewrite rule <literal>newrule</literal>:
-
-<programlisting>
-DROP RULE newrule ON mytable;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP RULE</command> statement in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createrule"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_schema.sgmlin b/doc-xc/src/sgml/ref/drop_schema.sgmlin
deleted file mode 100644
index c68f3ea822..0000000000
--- a/doc-xc/src/sgml/ref/drop_schema.sgmlin
+++ /dev/null
@@ -1,133 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_schema.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPSCHEMA">
- <refmeta>
-  <refentrytitle>DROP SCHEMA</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP SCHEMA</refname>
-  <refpurpose>remove a schema</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropschema">
-  <primary>DROP SCHEMA</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP SCHEMA [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP SCHEMA</command> removes schemas from the database.
-  </para>
-
-  <para>
-   A schema can only be dropped by its owner or a superuser.  Note that
-   the owner can drop the schema (and thereby all contained objects)
-   even if he does not own some of the objects within the schema.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the schema does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of a schema.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects (tables, functions, etc.) that are
-      contained in the schema.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the schema if it contains any objects.  This is
-      the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To remove schema <literal>mystuff</literal> from the database,
-   along with everything it contains:
-
-<programlisting>
-DROP SCHEMA mystuff CASCADE;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>DROP SCHEMA</command> is fully conforming with the SQL
-   standard, except that the standard only allows one schema to be
-   dropped per command, and apart from the
-<!## PG>
-   <literal>IF EXISTS</> option, which is a <productname>PostgreSQL</>
-   extension.
-<!## end>
-<!## XC>
-   <literal>IF EXISTS</> option, which is a <productname>Postgres-XC</>
-   extension inherited from <productname>PostgreSQL</>.
-<!## end>
-<!## XL>
-   <literal>IF EXISTS</> option, which is a <productname>Postgres-XL</>
-   extension inherited from <productname>PostgreSQL</>.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterschema"></member>
-   <member><xref linkend="sql-createschema"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_sequence.sgmlin b/doc-xc/src/sgml/ref/drop_sequence.sgmlin
deleted file mode 100644
index 23b78da612..0000000000
--- a/doc-xc/src/sgml/ref/drop_sequence.sgmlin
+++ /dev/null
@@ -1,116 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_sequence.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPSEQUENCE">
- <refmeta>
-  <refentrytitle>DROP SEQUENCE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP SEQUENCE</refname>
-  <refpurpose>remove a sequence</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropsequence">
-  <primary>DROP SEQUENCE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP SEQUENCE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>DROP SEQUENCE</command> removes sequence number
-   generators. A sequence can only be dropped by its owner or a superuser.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the sequence does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of a sequence.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the sequence.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the sequence if any objects depend on it.  This
-      is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To remove the sequence <literal>serial</literal>:
-
-<programlisting>
-DROP SEQUENCE serial;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>DROP SEQUENCE</command> conforms to the <acronym>SQL</acronym>
-   standard, except that the standard only allows one
-   sequence to be dropped per command, and apart from the
-   <literal>IF EXISTS</> option, which is a <productname>PostgreSQL</>
-   extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createsequence"></member>
-   <member><xref linkend="sql-altersequence"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_server.sgmlin b/doc-xc/src/sgml/ref/drop_server.sgmlin
deleted file mode 100644
index af9de0c1d3..0000000000
--- a/doc-xc/src/sgml/ref/drop_server.sgmlin
+++ /dev/null
@@ -1,133 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_server.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPSERVER">
- <refmeta>
-  <refentrytitle>DROP SERVER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP SERVER</refname>
-  <refpurpose>remove a foreign server descriptor</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropserver">
-  <primary>DROP SERVER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP SERVER [ IF EXISTS ] <replaceable class="parameter">server_name</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-<!## XC>
-&xconly;
-  <para>
-   <command>SERVER</> has not been supported
-   by <productname>Postgres-XC</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>SERVER</> is not yet supported
-   in <productname>Postgres-XL</>.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-&pgonly;
-
-  <para>
-   <command>DROP SERVER</command> removes an existing foreign server
-   descriptor.  To execute this command, the current user must be the
-   owner of the server.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the server does not exist.  A notice is
-      issued in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">server_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of an existing server.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the server (such as
-      user mappings).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the server if any objects depend on it.  This is
-      the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Drop a server <literal>foo</> if it exists:
-<programlisting>
-DROP SERVER IF EXISTS foo;
-</programlisting>
-  </para>
-
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>DROP SERVER</command> conforms to ISO/IEC 9075-9
-   (SQL/MED).  The <literal>IF EXISTS</> clause is
-   a <productname>PostgreSQL</> extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createserver"></member>
-   <member><xref linkend="sql-alterserver"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_table.sgmlin b/doc-xc/src/sgml/ref/drop_table.sgmlin
deleted file mode 100644
index 6373a952de..0000000000
--- a/doc-xc/src/sgml/ref/drop_table.sgmlin
+++ /dev/null
@@ -1,139 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_table.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTABLE">
- <refmeta>
-  <refentrytitle>DROP TABLE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP TABLE</refname>
-  <refpurpose>remove a table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droptable">
-  <primary>DROP TABLE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP TABLE</command> removes tables from the database.
-   Only its owner can drop a table.  To empty a table of rows
-   without destroying the table, use <xref linkend="sql-delete">
-   or <xref linkend="sql-truncate">.
-  </para>
-
-  <para>
-   <command>DROP TABLE</command> always removes any indexes, rules,
-   triggers, and constraints that exist for the target table.
-   However, to drop a table that is referenced by a view or a foreign-key
-   constraint of another table, <literal>CASCADE</> must be
-   specified. (<literal>CASCADE</> will remove a dependent view entirely,
-   but in the foreign-key case it will only remove the foreign-key
-   constraint, not the other table entirely.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the table does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the table to drop.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the table (such as
-      views).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the table if any objects depend on it.  This is
-      the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To destroy two tables, <literal>films</literal> and
-   <literal>distributors</literal>:
-
-<programlisting>
-DROP TABLE films, distributors;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   This command conforms to the SQL standard, except that the standard only
-   allows one table to be dropped per command, and apart from the
-<!## PG>
-   <literal>IF EXISTS</> option, which is a <productname>PostgreSQL</>
-   extension.
-<!## end>
-<!## XC>
-   <literal>IF EXISTS</> option, which is a <productname>Postgres-XC</>
-   extension inherited from <productname>PosrgreSQL</>.
-<!## end>
-<!## XL>
-   <literal>IF EXISTS</> option, which is a <productname>Postgres-XL</>
-   extension inherited from <productname>PostgreSQL</>.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertable"></member>
-   <member><xref linkend="sql-createtable"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_tablespace.sgmlin b/doc-xc/src/sgml/ref/drop_tablespace.sgmlin
deleted file mode 100644
index e0fb21754b..0000000000
--- a/doc-xc/src/sgml/ref/drop_tablespace.sgmlin
+++ /dev/null
@@ -1,134 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_tablespace.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTABLESPACE">
- <refmeta>
-  <refentrytitle>DROP TABLESPACE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP TABLESPACE</refname>
-  <refpurpose>remove a tablespace</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droptablespace">
-  <primary>DROP TABLESPACE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP TABLESPACE [ IF EXISTS ] <replaceable class="PARAMETER">tablespace_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP TABLESPACE</command> removes a tablespace from the system.
-  </para>
-
-  <para>
-   A tablespace can only be dropped by its owner or a superuser.
-   The tablespace must be empty of all database objects before it can be
-   dropped. It is possible that objects in other databases might still reside
-   in the tablespace even if no objects in the current database are using
-   the tablespace.  Also, if the tablespace is listed in the <xref
-   linkend="guc-temp-tablespaces"> setting of any active session, the
-   <command>DROP</> might fail due to temporary files residing in the
-   tablespace.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the tablespace does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">tablespace_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of a tablespace.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    <command>DROP TABLESPACE</> cannot be executed inside a transaction block.
-   </para>
-
-<!## XC>
-   <para>
-    <command>DROP TABLESPACE</> can be run with EXECUTE DIRECT to control
-    tablespace existence on remote nodes. This works for both remote Coordinators
-    and	Datanodes but not on this operation is not authorized on node where
-    application client is connected.
-   </para>
-<!## end>
-<!## XL>
-   <para>
-   </para>
-<!## end>
- </refsect1>
-
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To remove tablespace <literal>mystuff</literal> from the system:
-<programlisting>
-DROP TABLESPACE mystuff;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-<!## PG>
-   <command>DROP TABLESPACE</command> is a <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-   <command>DROP TABLESPACE</command> is a <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-   <command>DROP TABLESPACE</command> is a <productname>Postgres-XL</>
-<!## end>
-   extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtablespace"></member>
-   <member><xref linkend="sql-altertablespace"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_trigger.sgmlin b/doc-xc/src/sgml/ref/drop_trigger.sgmlin
deleted file mode 100644
index 58b5897814..0000000000
--- a/doc-xc/src/sgml/ref/drop_trigger.sgmlin
+++ /dev/null
@@ -1,145 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_trigger.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTRIGGER">
- <refmeta>
-  <refentrytitle>DROP TRIGGER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP TRIGGER</refname>
-  <refpurpose>remove a trigger</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droptrigger">
-  <primary>DROP TRIGGER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP TRIGGER [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> ON <replaceable class="PARAMETER">table</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>DROP TRIGGER</> statement has not been supported
-   in <productname>Postgres-XC</> yet.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   The <command>DROP TRIGGER</> statement is not yet supported
-   in <productname>Postgres-XL</>.
-  </para>
-<!## end>
-
-<!## PG>
-
-  <para>
-   <command>DROP TRIGGER</command> removes an existing
-   trigger definition. To execute this command, the current
-   user must be the owner of the table for which the trigger is defined.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the trigger does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the trigger to remove.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">table</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the table for which
-      the trigger is defined.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the trigger.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the trigger if any objects depend on it.  This is
-      the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1 id="SQL-DROPTRIGGER-examples">
-  <title>Examples</title>
-
-  <para>
-   Destroy the trigger <literal>if_dist_exists</literal> on the table
-   <literal>films</literal>:
-
-<programlisting>
-DROP TRIGGER if_dist_exists ON films;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPTRIGGER-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   The <command>DROP TRIGGER</command> statement in
-   <productname>PostgreSQL</productname> is incompatible with the SQL
-   standard.  In the SQL standard, trigger names are not local to
-   tables, so the command is simply <literal>DROP TRIGGER
-   <replaceable>name</replaceable></literal>.
-  </para>
-
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtrigger"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_tsconfig.sgmlin b/doc-xc/src/sgml/ref/drop_tsconfig.sgmlin
deleted file mode 100644
index 39a404e068..0000000000
--- a/doc-xc/src/sgml/ref/drop_tsconfig.sgmlin
+++ /dev/null
@@ -1,121 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_tsconfig.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTSCONFIG">
- <refmeta>
-  <refentrytitle>DROP TEXT SEARCH CONFIGURATION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP TEXT SEARCH CONFIGURATION</refname>
-  <refpurpose>remove a text search configuration</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droptsconfig">
-  <primary>DROP TEXT SEARCH CONFIGURATION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP TEXT SEARCH CONFIGURATION [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP TEXT SEARCH CONFIGURATION</command> drops an existing text
-   search configuration.  To execute this command you must be the owner of the
-   configuration.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the text search configuration does not exist.
-      A notice is issued in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing text search
-      configuration.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the text search configuration.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the text search configuration if any objects depend on it.
-      This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Remove the text search configuration <literal>my_english</literal>:
-
-<programlisting>
-DROP TEXT SEARCH CONFIGURATION my_english;
-</programlisting>
-
-   This command will not succeed if there are any existing indexes
-   that reference the configuration in <function>to_tsvector</> calls.
-   Add <literal>CASCADE</> to
-   drop such indexes along with the text search configuration.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP TEXT SEARCH CONFIGURATION</command> statement in
-   the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertsconfig"></member>
-   <member><xref linkend="sql-createtsconfig"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_tsdictionary.sgmlin b/doc-xc/src/sgml/ref/drop_tsdictionary.sgmlin
deleted file mode 100644
index 3ab2d85e8c..0000000000
--- a/doc-xc/src/sgml/ref/drop_tsdictionary.sgmlin
+++ /dev/null
@@ -1,120 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_tsdictionary.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTSDICTIONARY">
- <refmeta>
-  <refentrytitle>DROP TEXT SEARCH DICTIONARY</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP TEXT SEARCH DICTIONARY</refname>
-  <refpurpose>remove a text search dictionary</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droptsdictionary">
-  <primary>DROP TEXT SEARCH DICTIONARY</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP TEXT SEARCH DICTIONARY [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP TEXT SEARCH DICTIONARY</command> drops an existing text
-   search dictionary.  To execute this command you must be the owner of the
-   dictionary.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the text search dictionary does not exist.
-      A notice is issued in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing text search
-      dictionary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the text search dictionary.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the text search dictionary if any objects depend on it.
-      This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Remove the text search dictionary <literal>english</literal>:
-
-<programlisting>
-DROP TEXT SEARCH DICTIONARY english;
-</programlisting>
-
-   This command will not succeed if there are any existing text search
-   configurations that use the dictionary.  Add <literal>CASCADE</> to
-   drop such configurations along with the dictionary.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP TEXT SEARCH DICTIONARY</command> statement in the
-   SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertsdictionary"></member>
-   <member><xref linkend="sql-createtsdictionary"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_tsparser.sgmlin b/doc-xc/src/sgml/ref/drop_tsparser.sgmlin
deleted file mode 100644
index b949eca41f..0000000000
--- a/doc-xc/src/sgml/ref/drop_tsparser.sgmlin
+++ /dev/null
@@ -1,118 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_tsparser.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTSPARSER">
- <refmeta>
-  <refentrytitle>DROP TEXT SEARCH PARSER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP TEXT SEARCH PARSER</refname>
-  <refpurpose>remove a text search parser</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droptsparser">
-  <primary>DROP TEXT SEARCH PARSER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP TEXT SEARCH PARSER [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP TEXT SEARCH PARSER</command> drops an existing text search
-   parser.  You must be a superuser to use this command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the text search parser does not exist.
-      A notice is issued in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing text search parser.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the text search parser.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the text search parser if any objects depend on it.
-      This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Remove the text search parser <literal>my_parser</literal>:
-
-<programlisting>
-DROP TEXT SEARCH PARSER my_parser;
-</programlisting>
-
-   This command will not succeed if there are any existing text search
-   configurations that use the parser.  Add <literal>CASCADE</> to
-   drop such configurations along with the parser.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP TEXT SEARCH PARSER</command> statement in the
-   SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertsparser"></member>
-   <member><xref linkend="sql-createtsparser"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_tstemplate.sgmlin b/doc-xc/src/sgml/ref/drop_tstemplate.sgmlin
deleted file mode 100644
index 63d4386571..0000000000
--- a/doc-xc/src/sgml/ref/drop_tstemplate.sgmlin
+++ /dev/null
@@ -1,117 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_tstemplate.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTSTEMPLATE">
- <refmeta>
-  <refentrytitle>DROP TEXT SEARCH TEMPLATE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP TEXT SEARCH TEMPLATE</refname>
-  <refpurpose>remove a text search template</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droptstemplate">
-  <primary>DROP TEXT SEARCH TEMPLATE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP TEXT SEARCH TEMPLATE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-&common;
-  <para>
-   <command>DROP TEXT SEARCH TEMPLATE</command> drops an existing text search
-   template.  You must be a superuser to use this command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the text search template does not exist.
-      A notice is issued in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing text search
-      template.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the text search template.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the text search template if any objects depend on it.
-      This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Remove the text search template <literal>thesaurus</literal>:
-
-<programlisting>
-DROP TEXT SEARCH TEMPLATE thesaurus;
-</programlisting>
-
-   This command will not succeed if there are any existing text search
-   dictionaries that use the template.  Add <literal>CASCADE</> to
-   drop such dictionaries along with the template.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>DROP TEXT SEARCH TEMPLATE</command> statement in the
-   SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertstemplate"></member>
-   <member><xref linkend="sql-createtstemplate"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_type.sgmlin b/doc-xc/src/sgml/ref/drop_type.sgmlin
deleted file mode 100644
index 63ba9d7708..0000000000
--- a/doc-xc/src/sgml/ref/drop_type.sgmlin
+++ /dev/null
@@ -1,133 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_type.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTYPE">
- <refmeta>
-  <refentrytitle>DROP TYPE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP TYPE</refname>
-  <refpurpose>remove a data type</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-droptype">
-  <primary>DROP TYPE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP TYPE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP TYPE</command> removes a user-defined data type.
-   Only the owner of a type can remove it.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the type does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the data type to remove.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the type (such as
-      table columns, functions, operators).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the type if any objects depend on it.  This is
-      the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1 id="SQL-DROPTYPE-examples">
-  <title>Examples</title>
-
-  <para>
-   To remove the data type <type>box</type>:
-<programlisting>
-DROP TYPE box;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPTYPE-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   This command is similar to the corresponding command in the SQL
-   standard, apart from the <literal>IF EXISTS</>
-<!## PG>
-   option, which is a <productname>PostgreSQL</> extension.
-<!## end>
-<!## XC>
-   option, which is a <productname>Postgres-XC</> extension inherited from <productname>PostgreSQL</>.
-<!## end>
-<!## XL>
-   option, which is a <productname>Postgres-XL</> extension inherited from <productname>PostgreSQL</>.
-<!## end>
-   But note that much of the <command>CREATE TYPE</command> command
-   and the data type extension mechanisms in
-<!## PG>
-   <productname>PostgreSQL</productname> differ from the SQL standard.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> differ from the SQL standard.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> differ from the SQL standard.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPTYPE-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertype"></member>
-   <member><xref linkend="sql-createtype"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_user.sgmlin b/doc-xc/src/sgml/ref/drop_user.sgmlin
deleted file mode 100644
index 32c940bc9c..0000000000
--- a/doc-xc/src/sgml/ref/drop_user.sgmlin
+++ /dev/null
@@ -1,65 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_user.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPUSER">
- <refmeta>
-  <refentrytitle>DROP USER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP USER</refname>
-  <refpurpose>remove a database role</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropuser">
-  <primary>DROP USER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP USER [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP USER</command> is now an alias for
-   <xref linkend="sql-droprole">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The <command>DROP USER</command> statement is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.  The SQL standard
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.  The SQL standard
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.  The SQL standard
-<!## end>
-   leaves the definition of users to the implementation.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-droprole"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_user_mapping.sgmlin b/doc-xc/src/sgml/ref/drop_user_mapping.sgmlin
deleted file mode 100644
index e6f1f6af19..0000000000
--- a/doc-xc/src/sgml/ref/drop_user_mapping.sgmlin
+++ /dev/null
@@ -1,131 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_user_mapping.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPUSERMAPPING">
- <refmeta>
-  <refentrytitle>DROP USER MAPPING</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP USER MAPPING</refname>
-  <refpurpose>remove a user mapping for a foreign server</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropusermapping">
-  <primary>DROP USER MAPPING</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP USER MAPPING [ IF EXISTS ] FOR { <replaceable class="parameter">user_name</replaceable> | USER | CURRENT_USER | PUBLIC } SERVER <replaceable class="parameter">server_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-<!## XC>
-&xconly;
-  <para>
-   <command>USER MAPPING</> has not been supported
-   by <productname>Postgres-XC</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>USER MAPPING</> has not been supported
-   by <productname>Postgres-XL</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-&pgonly;
-
-  <para>
-   <command>DROP USER MAPPING</command> removes an existing user
-   mapping from foreign server.
-  </para>
-
-  <para>
-   The owner of a foreign server can drop user mappings for that server
-   for any user.  Also, a user can drop a user mapping for his own
-   user name if <literal>USAGE</> privilege on the server has been
-   granted to the user.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the user mapping does not exist.  A
-      notice is issued in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">user_name</replaceable></term>
-    <listitem>
-     <para>
-      User name of the mapping.  <literal>CURRENT_USER</>
-      and <literal>USER</> match the name of the current
-      user.  <literal>PUBLIC</> is used to match all present and
-      future user names in the system.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">server_name</replaceable></term>
-    <listitem>
-     <para>
-      Server name of the user mapping.
-     </para>
-    </listitem>
-   </varlistentry>
-    </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Drop a user mapping <literal>bob</>, server <literal>foo</> if it exists:
-<programlisting>
-DROP USER MAPPING IF EXISTS FOR bob SERVER foo;
-</programlisting>
-  </para>
-
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>DROP USER MAPPING</command> conforms to ISO/IEC 9075-9
-   (SQL/MED).  The <literal>IF EXISTS</> clause is
-   a <productname>PostgreSQL</> extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createusermapping"></member>
-   <member><xref linkend="sql-alterusermapping"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/drop_view.sgmlin b/doc-xc/src/sgml/ref/drop_view.sgmlin
deleted file mode 100644
index 8785293ce2..0000000000
--- a/doc-xc/src/sgml/ref/drop_view.sgmlin
+++ /dev/null
@@ -1,125 +0,0 @@
-<!--
-doc/src/sgml/ref/drop_view.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPVIEW">
- <refmeta>
-  <refentrytitle>DROP VIEW</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>DROP VIEW</refname>
-  <refpurpose>remove a view</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-dropview">
-  <primary>DROP VIEW</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-DROP VIEW [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>DROP VIEW</command> drops an existing view.  To execute
-   this command you must be the owner of the view.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>IF EXISTS</literal></term>
-    <listitem>
-     <para>
-      Do not throw an error if the view does not exist. A notice is issued
-      in this case.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the view to remove.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically drop objects that depend on the view (such as
-      other views).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to drop the view if any objects depend on it.  This is
-      the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   This command will remove the view called <literal>kinds</literal>:
-<programlisting>
-DROP VIEW kinds;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   This command conforms to the SQL standard, except that the standard only
-   allows one view to be dropped per command, and apart from the
-<!## PG>
-   <literal>IF EXISTS</> option, which is a <productname>PostgreSQL</>
-   extension.
-<!## end>
-<!## XC>
-   <literal>IF EXISTS</> option, which is a <productname>Postgres-XC</>
-   extension inherited from <productname>PostgreSQL</>.
-<!## end>
-<!## XL>
-   <literal>IF EXISTS</> option, which is a <productname>Postgres-XL</>
-   extension inherited from <productname>PostgreSQL</>.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alterview"></member>
-   <member><xref linkend="sql-createview"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/dropdb.sgmlin b/doc-xc/src/sgml/ref/dropdb.sgmlin
deleted file mode 100644
index 831a84f5cc..0000000000
--- a/doc-xc/src/sgml/ref/dropdb.sgmlin
+++ /dev/null
@@ -1,272 +0,0 @@
-<!--
-doc/src/sgml/ref/dropdb.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-DROPDB">
- <refmeta>
-  <refentrytitle><application>dropdb</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>dropdb</refname>
-  <refpurpose>remove a <productname>PostgreSQL</productname> database</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-dropdb">
-  <primary>dropdb</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>dropdb</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-   <arg choice="plain"><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <application>dropdb</application> destroys an existing
-   <productname>PostgreSQL</productname> database.
-   The user who executes this command must be a database
-   superuser or the owner of the database.
-  </para>
-
-  <para>
-   <application>dropdb</application> is a wrapper around the
-   <acronym>SQL</acronym> command <xref linkend="SQL-DROPDATABASE">.
-   There is no effective difference between dropping databases via
-   this utility and via other methods for accessing the server.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-
-  <para>
-   <application>dropdb</> accepts the following command-line arguments:
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">dbname</replaceable></term>
-      <listitem>
-       <para>
-        Specifies the name of the database to be removed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</></term>
-      <term><option>--echo</></term>
-      <listitem>
-       <para>
-        Echo the commands that <application>dropdb</application> generates
-        and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-i</></term>
-      <term><option>--interactive</></term>
-      <listitem>
-       <para>
-       Issues a verification prompt before doing anything destructive.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>dropdb</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>dropdb</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-  </para>
-
-  <para>
-   <application>dropdb</application> also accepts the following
-   command-line arguments for connection parameters:
-
-   <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the
-        server
-        is running.  If the value begins with a slash, it is used
-        as the directory for the Unix domain socket.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server
-        is listening for connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-       <para>
-        Force <application>dropdb</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>dropdb</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>dropdb</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Diagnostics</title>
-
-  <para>
-   In case of difficulty, see <xref linkend="SQL-DROPDATABASE">
-   and <xref linkend="APP-PSQL"> for
-   discussions of potential problems and error messages.
-   The database server must be running at the
-   targeted host.  Also, any default connection settings and environment
-   variables used by the <application>libpq</application> front-end
-   library will apply.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Examples</title>
-
-   <para>
-    To destroy the database <literal>demo</literal> on the default
-    database server:
-<screen>
-<prompt>$ </prompt><userinput>dropdb demo</userinput>
-</screen>
-   </para>
-
-   <para>
-    To destroy the database <literal>demo</literal> using the
-    server on host <literal>eden</literal>, port 5000, with verification and a peek
-    at the underlying command:
-<screen>
-<prompt>$ </prompt><userinput>dropdb -p 5000 -h eden -i -e demo</userinput>
-<computeroutput>Database "demo" will be permanently deleted.
-Are you sure? (y/n) </computeroutput><userinput>y</userinput>
-<computeroutput>DROP DATABASE demo;</computeroutput>
-</screen>
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-createdb"></member>
-   <member><xref linkend="sql-dropdatabase"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/droplang.sgmlin b/doc-xc/src/sgml/ref/droplang.sgmlin
deleted file mode 100644
index 38cdfea6c3..0000000000
--- a/doc-xc/src/sgml/ref/droplang.sgmlin
+++ /dev/null
@@ -1,320 +0,0 @@
-<!--
-doc/src/sgml/ref/droplang.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-DROPLANG">
- <refmeta>
-  <refentrytitle><application>droplang</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>droplang</refname>
-<!## PG>
-  <refpurpose>remove a <productname>PostgreSQL</productname> procedural language</refpurpose>
-<!## end>
-<!## XC>
-  <refpurpose>remove a <productname>Postgres-XC</productname> procedural language</refpurpose>
-<!## end>
-<!## XL>
-  <refpurpose>remove a <productname>Postgres-XL</productname> procedural language</refpurpose>
-<!## end>
- </refnamediv>
-
- <indexterm zone="app-droplang">
-  <primary>droplang</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>droplang</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg choice="plain"><replaceable>langname</replaceable></arg>
-   <arg><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>droplang</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <group choice="plain"><arg>--list</arg><arg>-l</arg></group>
-   <arg choice="plain"><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-DROPLANG-1">
-  <title>
-   Description
-  </title>
-
-  <para>
-   <application>droplang</application> is a utility for removing an
-   existing procedural language from a
-<!## PG>
-   <productname>PostgreSQL</productname> database.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> database.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> database.
-<!## end>
-  </para>
-
-  <para>
-   <application>droplang</application> is just a wrapper around the
-   <xref linkend="sql-dropextension"> SQL command.
-  </para>
-
-  <caution>
-   <para>
-    <application>droplang</application> is deprecated and may be removed
-<!## PG>
-    in a future <productname>PostgreSQL</productname> release.  Direct use
-<!## end>
-<!## XC>
-    in a future <productname>Postgres-XC</productname> release.  Direct use
-<!## end>
-<!## XL>
-    in a future <productname>Postgres-XL</productname> release.  Direct use
-<!## end>
-    of the <command>DROP EXTENSION</> command is recommended instead.
-   </para>
-  </caution>
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-
-   <para>
-    <application>droplang</application> accepts the following command line arguments:
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">langname</replaceable></term>
-      <listitem>
-       <para>
-        Specifies the name of the procedural language to be removed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option><optional>-d</> <replaceable class="parameter">dbname</replaceable></></term>
-      <term><option><optional>--dbname=</><replaceable class="parameter">dbname</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies from which database the language should be removed.
-        The default is to use the database with the same name as the
-        current system user.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</></term>
-      <term><option>--echo</></term>
-      <listitem>
-       <para>
-        Display SQL commands as they are executed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l</></term>
-      <term><option>--list</></term>
-      <listitem>
-       <para>
-        Show a list of already installed languages in the target database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>droplang</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>droplang</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    <application>droplang</application> also accepts
-    the following command line arguments for connection parameters:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the
-        server
-        is running.  If host begins with a slash, it is used
-        as the directory for the Unix domain socket.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the Internet TCP/IP port or local Unix domain socket file
-        extension on which the server
-        is listening for connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-       <para>
-        Force <application>droplang</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>droplang</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>droplang</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATABASE</envar></term>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-<!## PG>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-<!## end>
-<!## XC>
-   This utility, like most other <productname>Postgres-XC</> utilities,
-<!## end>
-<!## XL>
-   This utility, like most other <productname>Postgres-XL</> utilities,
-<!## end>
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-   <title>Diagnostics</title>
-
-   <para>
-    Most error messages are self-explanatory. If not, run
-    <application>droplang</application> with the <option>--echo</option>
-    option and see under the respective <acronym>SQL</acronym> command
-    for details.  Also, any default connection settings and environment
-    variables used by the <application>libpq</application> front-end
-    library will apply.
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="app-createlang"> to add a language.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Examples</title>
-
-   <para>
-    To remove the language <literal>pltcl</literal>:
-<screen>
-<prompt>$ </prompt><userinput>droplang pltcl dbname</userinput>
-</screen>
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-createlang"></member>
-   <member><xref linkend="sql-dropextension"></member>
-   <member><xref linkend="sql-droplanguage"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/dropuser.sgmlin b/doc-xc/src/sgml/ref/dropuser.sgmlin
deleted file mode 100644
index d239ffcd34..0000000000
--- a/doc-xc/src/sgml/ref/dropuser.sgmlin
+++ /dev/null
@@ -1,313 +0,0 @@
-<!--
-doc/src/sgml/ref/dropuser.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-DROPUSER">
- <refmeta>
-  <refentrytitle><application>dropuser</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>dropuser</refname>
-<!## PG>
-  <refpurpose>remove a <productname>PostgreSQL</productname> user account</refpurpose>
-<!## end>
-<!## XC>
-  <refpurpose>remove a <productname>Postgres-XC</productname> user account</refpurpose>
-<!## end>
-<!## XL>
-  <refpurpose>remove a <productname>Postgres-XL</productname> user account</refpurpose>
-<!## end>
- </refnamediv>
-
- <indexterm zone="app-dropuser">
-  <primary>dropuser</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>dropuser</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-   <arg><replaceable>username</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <application>dropuser</application> removes an existing
-<!## PG>
-   <productname>PostgreSQL</productname> user.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> user.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> user.
-<!## end>
-   Only superusers and users with the <literal>CREATEROLE</> privilege can
-<!## PG>
-   remove <productname>PostgreSQL</productname> users.  (To remove a
-<!## end>
-<!## XC>
-   remove <productname>Postgres-XC</productname> users.  (To remove a
-<!## end>
-<!## XL>
-   remove <productname>Postgres-XL</productname> users.  (To remove a
-<!## end>
-   superuser, you must yourself be a superuser.)
-  </para>
-
-  <para>
-   <application>dropuser</application> is a wrapper around the
-   <acronym>SQL</acronym> command <xref linkend="SQL-DROPROLE">.
-   There is no effective difference between dropping users via
-   this utility and via other methods for accessing the server.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-
-  <para>
-   <application>dropuser</application> accepts the following command-line arguments:
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-<!## PG>
-        Specifies the name of the <productname>PostgreSQL</productname> user to be removed.
-<!## end>
-<!## XC>
-        Specifies the name of the <productname>Postgres-XC</productname> user to be removed.
-<!## end>
-<!## XL>
-        Specifies the name of the <productname>Postgres-XL</productname> user to be removed.
-<!## end>
-        You will be prompted for a name if none is specified on the command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</></term>
-      <term><option>--echo</></term>
-      <listitem>
-       <para>
-        Echo the commands that <application>dropuser</application> generates
-        and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-i</></term>
-      <term><option>--interactive</></term>
-      <listitem>
-       <para>
-        Prompt for confirmation before actually removing the user.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>dropuser</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>dropuser</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-  </para>
-
-  <para>
-   <application>dropuser</application> also accepts the following
-   command-line arguments for connection parameters:
-
-   <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the
-        server
-        is running.  If the value begins with a slash, it is used
-        as the directory for the Unix domain socket.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server
-        is listening for connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-       <para>
-        User name to connect as (not the user name to drop).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-       <para>
-        Force <application>dropuser</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>dropuser</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>dropuser</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-<!## PG>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-<!## end>
-<!## XC>
-   This utility, like most other <productname>Postgres-XC</> utilities,
-<!## end>
-<!## XL>
-   This utility, like most other <productname>Postgres-XL</> utilities,
-<!## end>
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Diagnostics</title>
-
-  <para>
-   In case of difficulty, see <xref linkend="SQL-DROPROLE">
-   and <xref linkend="APP-PSQL"> for
-   discussions of potential problems and error messages.
-   The database server must be running at the
-   targeted host.  Also, any default connection settings and environment
-   variables used by the <application>libpq</application> front-end
-   library will apply.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Examples</title>
-
-   <para>
-    To remove user <literal>joe</literal> from the default database
-    server:
-<screen>
-<prompt>$ </prompt><userinput>dropuser joe</userinput>
-</screen>
-   </para>
-
-   <para>
-    To remove user <literal>joe</literal> using the server on host
-    <literal>eden</literal>, port 5000, with verification and a peek at the underlying
-    command:
-<screen>
-<prompt>$ </prompt><userinput>dropuser -p 5000 -h eden -i -e joe</userinput>
-<computeroutput>Role "joe" will be permanently removed.
-Are you sure? (y/n) </computeroutput><userinput>y</userinput>
-<computeroutput>DROP ROLE joe;</computeroutput>
-</screen>
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-createuser"></member>
-   <member><xref linkend="sql-droprole"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/ecpg-ref.sgmlin b/doc-xc/src/sgml/ref/ecpg-ref.sgmlin
deleted file mode 100644
index 856d196646..0000000000
--- a/doc-xc/src/sgml/ref/ecpg-ref.sgmlin
+++ /dev/null
@@ -1,265 +0,0 @@
-<!--
-doc/src/sgml/ref/ecpg-ref.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-ECPG">
- <refmeta>
-  <refentrytitle><application>ecpg</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname><application>ecpg</application></refname>
-  <refpurpose>embedded SQL C preprocessor</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-ecpg">
-  <primary>ecpg</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>ecpg</command>
-   <arg choice="opt" rep="repeat"><replaceable>option</replaceable></arg>
-   <arg choice="plain" rep="repeat"><replaceable>file</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1 id="APP-ECPG-description">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ecpg</command> is the embedded SQL preprocessor for C
-   programs.  It converts C programs with embedded SQL statements to
-   normal C code by replacing the SQL invocations with special
-   function calls.  The output files can then be processed with any C
-   compiler tool chain.
-  </para>
-
-  <para>
-   <command>ecpg</command> will convert each input file given on the
-   command line to the corresponding C output file.  Input files
-   preferably have the extension <filename>.pgc</filename>, in which
-   case the extension will be replaced by <filename>.c</filename> to
-   determine the output file name.  If the extension of the input file
-   is not <filename>.pgc</filename>, then the output file name is
-   computed by appending <literal>.c</literal> to the full file name.
-   The output file name can also be overridden using the
-   <option>-o</option> option.
-  </para>
-
-  <para>
-   This reference page does not describe the embedded SQL language.
-   See <xref linkend="ecpg"> for more information on that topic.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-&common;
-
-  <para>
-   <command>ecpg</command> accepts the following command-line
-   arguments:
-
-   <variablelist>
-    <varlistentry>
-     <term><option>-c</option></term>
-     <listitem>
-      <para>
-       Automatically generate certain C code from SQL code.  Currently, this
-       works for <literal>EXEC SQL TYPE</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-C <replaceable>mode</replaceable></option></term>
-     <listitem>
-      <para>
-       Set a compatibility mode.  <replaceable>mode</replaceable> can
-       be <literal>INFORMIX</literal> or
-       <literal>INFORMIX_SE</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-D <replaceable>symbol</replaceable></option></term>
-     <listitem>
-      <para>
-       Define a C preprocessor symbol.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-i</option></term>
-     <listitem>
-      <para>
-       Parse system include files as well.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-I <replaceable class="parameter">directory</replaceable></option></term>
-     <listitem>
-      <para>
-       Specify an additional include path, used to find files included
-       via <literal>EXEC SQL INCLUDE</literal>.  Defaults are
-       <filename>.</filename> (current directory),
-       <filename>/usr/local/include</filename>, the
-       <productname>PostgreSQL</productname> include directory which
-       is defined at compile time (default:
-       <filename>/usr/local/pgsql/include</filename>), and
-       <filename>/usr/include</filename>, in that order.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-o <replaceable>filename</replaceable></option></term>
-     <listitem>
-      <para>
-       Specifies that <command>ecpg</command> should write all
-       its output to the given <replaceable>filename</replaceable>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-r <replaceable>option</replaceable></option></term>
-     <listitem>
-      <para>
-       Selects run-time behavior.  <replaceable>Option</replaceable> can be
-       one of the following:
-       <variablelist>
-        <varlistentry>
-         <term><option>no_indicator</option></term>
-         <listitem>
-         <para>
-         Do not use indicators but instead use special values to represent
-         null values. Historically there have been databases using this approach.
-         </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term><option>prepare</option></term>
-         <listitem>
-         <para>
-         Prepare all statements before using them. Libecpg will keep a cache of
-         prepared statements and reuse a statement if it gets executed again. If the
-         cache runs full, libecpg will free the least used statement.
-         </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term><option>questionmarks</option></term>
-         <listitem>
-         <para>
-         Allow question mark as placeholder for compatibility reasons.
-         This used to be the default long ago.
-         </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-t</option></term>
-     <listitem>
-      <para>
-       Turn on autocommit of transactions. In this mode, each SQL command is
-       automatically committed unless it is inside an explicit
-       transaction block. In the default mode, commands are committed
-       only when <command>EXEC SQL COMMIT</command> is issued.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-v</option></term>
-     <listitem>
-      <para>
-       Print additional information including the version and the
-       "include" path.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--version</option></term>
-     <listitem>
-      <para>
-       Print the <application>ecpg</application> version and exit.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--help</option></term>
-     <listitem>
-      <para>
-       Show help about <application>ecpg</application> command line
-       arguments, and exit.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-&common;
-
-  <para>
-   When compiling the preprocessed C code files, the compiler needs to
-   be able to find the <application>ECPG</> header files in the
-   <productname>PostgreSQL</> include directory.  Therefore, you might
-   have to use the <option>-I</> option when invoking the compiler
-   (e.g., <literal>-I/usr/local/pgsql/include</literal>).
-  </para>
-
-  <para>
-   Programs using C code with embedded SQL have to be linked against
-   the <filename>libecpg</filename> library, for example using the
-   linker options <literal>-L/usr/local/pgsql/lib -lecpg</literal>.
-  </para>
-
-  <para>
-   The value of either of these directories that is appropriate for
-   the installation can be found out using <xref
-   linkend="app-pgconfig">.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Examples</title>
-&common;
-
-  <para>
-   If you have an embedded SQL C source file named
-   <filename>prog1.pgc</filename>, you can create an executable
-   program using the following sequence of commands:
-<programlisting>
-ecpg prog1.pgc
-cc -I/usr/local/pgsql/include -c prog1.c
-cc -o prog1 prog1.o -L/usr/local/pgsql/lib -lecpg
-</programlisting>
-  </para>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/end.sgmlin b/doc-xc/src/sgml/ref/end.sgmlin
deleted file mode 100644
index 85248b4c2f..0000000000
--- a/doc-xc/src/sgml/ref/end.sgmlin
+++ /dev/null
@@ -1,101 +0,0 @@
-<!--
-doc/src/sgml/ref/end.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-END">
- <refmeta>
-  <refentrytitle>END</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>END</refname>
-  <refpurpose>commit the current transaction</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-end">
-  <primary>END</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-END [ WORK | TRANSACTION ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>END</command> commits the current transaction. All changes
-   made by the transaction become visible to others and are guaranteed
-   to be durable if a crash occurs.  This command is a
-   <productname>PostgreSQL</productname> extension
-   that is equivalent to <xref linkend="sql-commit">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>WORK</literal></term>
-    <term><literal>TRANSACTION</literal></term>
-    <listitem>
-     <para>
-      Optional key words. They have no effect.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-ROLLBACK"> to
-   abort a transaction.
-  </para>
-
-  <para>
-   Issuing <command>END</> when not inside a transaction does
-   no harm, but it will provoke a warning message.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To commit the current transaction and make all changes permanent:
-<programlisting>
-END;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>END</command> is a <productname>PostgreSQL</productname>
-   extension that provides functionality equivalent to <xref
-   linkend="sql-commit">, which is
-   specified in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-begin"></member>
-   <member><xref linkend="sql-commit"></member>
-   <member><xref linkend="sql-rollback"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/execute.sgmlin b/doc-xc/src/sgml/ref/execute.sgmlin
deleted file mode 100644
index 8130fb04a0..0000000000
--- a/doc-xc/src/sgml/ref/execute.sgmlin
+++ /dev/null
@@ -1,122 +0,0 @@
-<!--
-doc/src/sgml/ref/execute.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-EXECUTE">
- <refmeta>
-  <refentrytitle>EXECUTE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>EXECUTE</refname>
-  <refpurpose>execute a prepared statement</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-execute">
-  <primary>EXECUTE</primary>
- </indexterm>
-
- <indexterm zone="sql-execute">
-  <primary>prepared statements</primary>
-  <secondary>executing</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-EXECUTE <replaceable class="PARAMETER">name</replaceable> [ ( <replaceable class="PARAMETER">parameter</replaceable> [, ...] ) ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-&common;
-  <para>
-   <command>EXECUTE</command> is used to execute a previously prepared
-   statement. Since prepared statements only exist for the duration of a
-   session, the prepared statement must have been created by a
-   <command>PREPARE</command> statement executed earlier in the
-   current session.
-  </para>
-
-  <para>
-   If the <command>PREPARE</command> statement that created the statement
-   specified some parameters, a compatible set of parameters must be
-   passed to the <command>EXECUTE</command> statement, or else an
-   error is raised. Note that (unlike functions) prepared statements are
-   not overloaded based on the type or number of their parameters; the
-   name of a prepared statement must be unique within a database session.
-  </para>
-
-  <para>
-   For more information on the creation and usage of prepared statements,
-   see <xref linkend="sql-prepare">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the prepared statement to execute.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">parameter</replaceable></term>
-    <listitem>
-     <para>
-      The actual value of a parameter to the prepared statement.  This
-      must be an expression yielding a value that is compatible with
-      the data type of this parameter, as was determined when the
-      prepared statement was created.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Outputs</title>
-   <para>
-   The command tag returned by <command>EXECUTE</command>
-   is that of the prepared statement, and not <literal>EXECUTE</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</>
-  <para>
-    Examples are given in the <xref linkend="sql-prepare-examples"
-    endterm="sql-prepare-examples-title"> section of the <xref
-    linkend="sql-prepare"> documentation.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard includes an <command>EXECUTE</command> statement,
-   but it is only for use in embedded SQL.  This version of the
-   <command>EXECUTE</command> statement also uses a somewhat different
-   syntax.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-deallocate"></member>
-   <member><xref linkend="sql-prepare"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/execute_direct.sgmlin b/doc-xc/src/sgml/ref/execute_direct.sgmlin
deleted file mode 100644
index 314ac97308..0000000000
--- a/doc-xc/src/sgml/ref/execute_direct.sgmlin
+++ /dev/null
@@ -1,121 +0,0 @@
-<!--
-doc/src/sgml/ref/execute_direct.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-EXECUTEDIRECT">
- <refmeta>
-  <refentrytitle>EXECUTE DIRECT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>EXECUTE DIRECT</refname>
-  <refpurpose>Launch queries directly to dedicated nodes</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-executedirect">
-  <primary>EXECUTE DIRECT</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-EXECUTE DIRECT ON ( <replaceable class="parameter">nodename</replaceable> [, ... ] )
-    <replaceable class="parameter">query</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xlonly;
-  <para>
-   <command>EXECUTE DIRECT</command> is a SQL command specially created
-   for <productname>Postgres-XL</productname> to allow to launch queries directly to dedicated
-   nodes determined by a list of nodes <replaceable class="parameter">
-   nodelist</replaceable>. 
-  </para>
-
-  <para>
-   EXECUTE DIRECT is currenlty limited to be used on 1 node at a time
-   only. 
-   The usage of transaction queries
-   (<literal>BEGIN</literal>, <literal>COMMIT</literal>...), DDL, and DML
-   (<literal>INSERT</literal>, <literal>UPDATE</literal>, <literal>DELETE
-   </literal>) is forbidden to avoid data inconsistency among nodes
-   in the cluster. EXECUTE DIRECT usage is also limited to superusers.
-  </para>
-
-  <para>
-    Either a Coordinator or Datanode can be selected by its node name.
-  </para>
-
-  <para>
-   <command>EXECUTE DIRECT</> allows the usage of the following utility commands
-   on remote nodes: <command>CREATE TABLESPACE</>, <command>DROP TABLESPACE</>.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">nodename</replaceable></term>
-    <listitem>
-     <para>
-      This mandatory clause specifies the node name on where to launch
-      <replaceable class="parameter">query</replaceable>. When specifying
-      multiple nodes, node names have to be separated by a comma.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">query</replaceable></term>
-    <listitem>
-     <para>
-      This mandatory clause specifies the raw query to launch
-      on specified node list <replaceable class="parameter">nodelist</replaceable>.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Select some data in a given table tenk1 on remote Datanode named dn1:
-<programlisting>
-EXECUTE DIRECT ON NODE dn1 'SELECT * FROM tenk1 WHERE col_char = ''foo''';
-</programlisting>
-  </para>
-
-  <para>
-   Select local timestamp of a remote node named coord2:
-<programlisting>
-EXECUTE DIRECT ON coord2 'select clock_timestamp()';
-</programlisting>
-  </para>
-
-  <para>
-   Select list of tables of a remote node named dn50:
-<programlisting>
-EXECUTE DIRECT ON dn50 'select tablename from pg_tables';
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>EXECUTE DIRECT</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XL specific command.
-  </para>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/explain.sgmlin b/doc-xc/src/sgml/ref/explain.sgmlin
deleted file mode 100644
index 9525388b61..0000000000
--- a/doc-xc/src/sgml/ref/explain.sgmlin
+++ /dev/null
@@ -1,468 +0,0 @@
-<!--
-doc/src/sgml/ref/explain.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-EXPLAIN">
- <refmeta>
-  <refentrytitle>EXPLAIN</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>EXPLAIN</refname>
-  <refpurpose>show the execution plan of a statement</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-explain">
-  <primary>EXPLAIN</primary>
- </indexterm>
-
- <indexterm zone="sql-explain">
-  <primary>prepared statements</primary>
-  <secondary>showing the query plan</secondary>
- </indexterm>
-
- <indexterm zone="sql-explain">
-  <primary>cursor</primary>
-  <secondary>showing the query plan</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-EXPLAIN [ ( <replaceable class="parameter">option</replaceable> [, ...] ) ] <replaceable class="parameter">statement</replaceable>
-EXPLAIN [ ANALYZE ] [ VERBOSE ] <replaceable class="parameter">statement</replaceable>
-
-<phrase>where <replaceable class="parameter">option</replaceable> can be one of:</phrase>
-
-    ANALYZE [ <replaceable class="parameter">boolean</replaceable> ]
-    VERBOSE [ <replaceable class="parameter">boolean</replaceable> ]
-    COSTS [ <replaceable class="parameter">boolean</replaceable> ]
-    BUFFERS [ <replaceable class="parameter">boolean</replaceable> ]
-    NODES [ <replaceable class="parameter">boolean</replaceable> ]
-    NUM_NODES [ <replaceable class="parameter">boolean</replaceable> ]
-    FORMAT { TEXT | XML | JSON | YAML }
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   This command displays the execution plan that the
-   <productname>PostgreSQL</productname> planner generates for the
-   supplied statement.  The execution plan shows how the table(s)
-   referenced by the statement will be scanned &mdash; by plain sequential scan,
-   index scan, etc. &mdash; and if multiple tables are referenced, what join
-   algorithms will be used to bring together the required rows from
-   each input table.
-  </para>
-
-  <para>
-   The most critical part of the display is the estimated statement execution
-   cost, which is the planner's guess at how long it will take to run the
-   statement (measured in units of disk page fetches).  Actually two numbers
-   are shown: the start-up time before the first row can be returned, and
-   the total time to return all the rows.  For most queries the total time
-   is what matters, but in contexts such as a subquery in <literal>EXISTS</literal>, the planner
-   will choose the smallest start-up time instead of the smallest total time
-   (since the executor will stop after getting one row, anyway).
-   Also, if you limit the number of rows to return with a <literal>LIMIT</literal> clause,
-   the planner makes an appropriate interpolation between the endpoint
-   costs to estimate which plan is really the cheapest.
-  </para>
-
-  <para>
-   The <literal>ANALYZE</literal> option causes the statement to be actually executed, not only
-   planned.  The total elapsed time expended within each plan node (in
-   milliseconds) and total number of rows it actually returned are added to
-   the display.  This is useful for seeing whether the planner's estimates
-   are close to reality.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   Please note that <command>explain</command> explains local plan at
-   the Coordinator only.  If you'd like to see remote plan at
-   Datanodes, use <filename>auto_explain</filename> package
-   at <xref linkend="auto-explain">
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   In <productname>Postgres-XL</productname>, EXPLAIN provides the cluster-wide 
-   execution plan that will be executed, and provides insight into the inner
-   workings of how queries are processed in parallel.
-  </para>
-<!## end>
-
-
-  <important>
-   <para>
-    Keep in mind that the statement is actually executed when
-    the <literal>ANALYZE</literal> option is used.  Although
-    <command>EXPLAIN</command> will discard any output that a
-    <command>SELECT</command> would return, other side effects of the
-    statement will happen as usual.  If you wish to use
-    <command>EXPLAIN ANALYZE</command> on an
-    <command>INSERT</command>, <command>UPDATE</command>,
-    <command>DELETE</command>, <command>CREATE TABLE AS</command>,
-    or <command>EXECUTE</command> statement
-    without letting the command affect your data, use this approach:
-<programlisting>
-BEGIN;
-EXPLAIN ANALYZE ...;
-ROLLBACK;
-</programlisting>
-   </para>
-  </important>
-
-  <para>
-   Only the <literal>ANALYZE</literal> and <literal>VERBOSE</literal> options
-   can be specified, and only in that order, without surrounding the option
-   list in parentheses.  Prior to <productname>PostgreSQL</productname> 9.0,
-   the unparenthesized syntax was the only one supported.  It is expected that
-   all new options will be supported only in the parenthesized syntax.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>ANALYZE</literal></term>
-    <listitem>
-     <para>
-      Carry out the command and show the actual run times.  This
-      parameter defaults to <literal>FALSE</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>VERBOSE</literal></term>
-    <listitem>
-     <para>
-      Display additional information regarding the plan.  Specifically, include
-      the output column list for each node in the plan tree, schema-qualify
-      table and function names, always label variables in expressions with
-      their range table alias, and always print the name of each trigger for
-      which statistics are displayed.  This parameter defaults to
-      <literal>FALSE</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>COSTS</literal></term>
-    <listitem>
-     <para>
-      Include information on the estimated startup and total cost of each
-      plan node, as well as the estimated number of rows and the estimated
-      width of each row.  This parameter defaults to <literal>TRUE</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>BUFFERS</literal></term>
-    <listitem>
-     <para>
-      Include information on buffer usage. Specifically, include the number of
-      shared blocks hits, reads, and writes, the number of local blocks hits,
-      reads, and writes, and the number of temp blocks reads and writes.
-      Shared blocks, local blocks, and temp blocks contain tables and indexes,
-      temporary tables and temporary indexes, and disk blocks used in sort and
-      materialized plans, respectively. The number of blocks shown for an
-      upper-level node includes those used by all its child nodes.  In text
-      format, only non-zero values are printed.  This parameter may only be
-      used with <literal>ANALYZE</literal> parameter.  It defaults to
-      <literal>FALSE</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-<!## XC>
-   <varlistentry>
-    <term><literal>NODES</literal></term>
-    <listitem>
-     <para>
-      Include information on the Datanodes involved in the execution of Data
-	  Scan Node. This parameter defaults to <literal>TRUE</literal>. This option
-	  is available in <productname>Postgres-XC</productname>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NUM_NODES</literal></term>
-    <listitem>
-     <para>
-      Include information on the number of nodes involved in the execution of
-	  Data Node Scan node.  This parameter defaults to <literal>FALSE</literal>.
-	  This option is available in <productname>Postgres-XC</productname>.
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-<!## XL>
-   <varlistentry>
-    <term><literal>NODES</literal></term>
-    <listitem>
-     <para>
-      Include information on the Datanodes involved in the execution of Data
-	  Scan Node. This parameter defaults to <literal>TRUE</literal>. This option
-	  is available in <productname>Postgres-XL</productname>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NUM_NODES</literal></term>
-    <listitem>
-     <para>
-      Include information on the number of nodes involved in the execution of
-	  Data Node Scan node.  This parameter defaults to <literal>FALSE</literal>.
-	  This option is available in <productname>Postgres-XL</productname>.
-     </para>
-    </listitem>
-   </varlistentry>
-<!## end>
-
-   <varlistentry>
-    <term><literal>FORMAT</literal></term>
-    <listitem>
-     <para>
-      Specify the output format, which can be TEXT, XML, JSON, or YAML.
-      Non-text output contains the same information as the text output
-      format, but is easier for programs to parse.  This parameter defaults to
-      <literal>TEXT</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">boolean</replaceable></term>
-    <listitem>
-     <para>
-      Specifies whether the selected option should be turned on or off.
-      You can write <literal>TRUE</literal>, <literal>ON</>, or
-      <literal>1</literal> to enable the option, and <literal>FALSE</literal>,
-      <literal>OFF</>, or <literal>0</literal> to disable it.  The
-      <replaceable class="parameter">boolean</replaceable> value can also
-      be omitted, in which case <literal>TRUE</literal> is assumed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">statement</replaceable></term>
-    <listitem>
-     <para>
-      Any <command>SELECT</>, <command>INSERT</>, <command>UPDATE</>,
-      <command>DELETE</>, <command>VALUES</>, <command>EXECUTE</>,
-      <command>DECLARE</>, or <command>CREATE TABLE AS</command>
-      statement, whose execution plan you wish to see.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   There is only sparse documentation on the optimizer's use of cost
-   information in <productname>PostgreSQL</productname>.  Refer to
-   <xref linkend="using-explain"> for more information.
-  </para>
-
-  <para>
-   In order to allow the <productname>PostgreSQL</productname> query
-   planner to make reasonably informed decisions when optimizing
-   queries, the <xref linkend="sql-analyze">
-   statement should be run to record statistics about the distribution
-   of data within the table. If you have not done this (or if the
-   statistical distribution of the data in the table has changed
-   significantly since the last time <command>ANALYZE</command> was
-   run), the estimated costs are unlikely to conform to the real
-   properties of the query, and consequently an inferior query plan
-   might be chosen.
-  </para>
-
-  <para>
-   In order to measure the run-time cost of each node in the execution
-   plan, the current implementation of <command>EXPLAIN
-   ANALYZE</command> can add considerable profiling overhead to query
-   execution. As a result, running <command>EXPLAIN ANALYZE</command>
-   on a query can sometimes take significantly longer than executing
-   the query normally. The amount of overhead depends on the nature of
-   the query.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To show the plan for a simple query on a table with a single
-   <type>integer</type> column and 10000 rows:
-
-<programlisting>
-EXPLAIN SELECT * FROM foo;
-
-                       QUERY PLAN
----------------------------------------------------------
- Seq Scan on foo  (cost=0.00..155.00 rows=10000 width=4)
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-  Here is the same query, with JSON formatting:
-<programlisting>
-EXPLAIN (FORMAT JSON) SELECT * FROM foo;
-           QUERY PLAN           
---------------------------------
- [                             +
-   {                           +
-     "Plan": {                 +
-       "Node Type": "Seq Scan",+
-       "Relation Name": "foo", +
-       "Alias": "foo",         +
-       "Startup Cost": 0.00,   +
-       "Total Cost": 155.00,   +
-       "Plan Rows": 10000,     +
-       "Plan Width": 4         +
-     }                         +
-   }                           +
- ]
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-   If there is an index and we use a query with an indexable
-   <literal>WHERE</literal> condition, <command>EXPLAIN</command>
-   might show a different plan:
-
-<programlisting>
-EXPLAIN SELECT * FROM foo WHERE i = 4;
-
-                         QUERY PLAN
---------------------------------------------------------------
- Index Scan using fi on foo  (cost=0.00..5.98 rows=1 width=4)
-   Index Cond: (i = 4)
-(2 rows)
-</programlisting>
-  </para>
-
-  <para>
-  Here is the same query, but in YAML output:
-<programlisting>
-EXPLAIN (FORMAT YAML) SELECT * FROM foo WHERE i='4';
-          QUERY PLAN           
--------------------------------
- - Plan:                      +
-     Node Type: "Index Scan"  +
-     Scan Direction: "Forward"+
-     Index Name: "fi"         +
-     Relation Name: "foo"     +
-     Alias: "foo"             +
-     Startup Cost: 0.00       +
-     Total Cost: 5.98         +
-     Plan Rows: 1             +
-     Plan Width: 4            +
-     Index Cond: "(i = 4)"
-(1 row)
-</programlisting>
-
-    XML output is left as an exercise to the reader.
-  </para>
-  <para>
-   Here is the same plan with costs suppressed:
-
-<programlisting>
-EXPLAIN (COSTS FALSE) SELECT * FROM foo WHERE i = 4;
-
-        QUERY PLAN
-----------------------------
- Index Scan using fi on foo
-   Index Cond: (i = 4)
-(2 rows)
-</programlisting>
-  </para>
-
-  <para>
-   Here is an example of a query plan for a query using an aggregate
-   function:
-
-<programlisting>
-EXPLAIN SELECT sum(i) FROM foo WHERE i &lt; 10;
-
-                             QUERY PLAN
----------------------------------------------------------------------
- Aggregate  (cost=23.93..23.93 rows=1 width=4)
-   -&gt;  Index Scan using fi on foo  (cost=0.00..23.92 rows=6 width=4)
-         Index Cond: (i &lt; 10)
-(3 rows)
-</programlisting>
-  </para>
-
-  <para>
-   Here is an example of using <command>EXPLAIN EXECUTE</command> to
-   display the execution plan for a prepared query:
-
-<programlisting>
-PREPARE query(int, int) AS SELECT sum(bar) FROM test
-    WHERE id &gt; $1 AND id &lt; $2
-    GROUP BY foo;
-
-EXPLAIN ANALYZE EXECUTE query(100, 200);
-
-                                                       QUERY PLAN                                                        
--------------------------------------------------------------------------------------------------------------------------
- HashAggregate  (cost=39.53..39.53 rows=1 width=8) (actual time=0.661..0.672 rows=7 loops=1)
-   -&gt;  Index Scan using test_pkey on test  (cost=0.00..32.97 rows=1311 width=8) (actual time=0.050..0.395 rows=99 loops=1)
-         Index Cond: ((id &gt; $1) AND (id &lt; $2))
- Total runtime: 0.851 ms
-(4 rows)
-</programlisting>
-  </para>
-
-  <para>
-   Of course, the specific numbers shown here depend on the actual
-   contents of the tables involved.  Also note that the numbers, and
-   even the selected query strategy, might vary between
-   <productname>PostgreSQL</productname> releases due to planner
-   improvements. In addition, the <command>ANALYZE</command> command
-   uses random sampling to estimate data statistics; therefore, it is
-   possible for cost estimates to change after a fresh run of
-   <command>ANALYZE</command>, even if the actual distribution of data
-   in the table has not changed.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>EXPLAIN</command> statement defined in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-analyze"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/fetch.sgmlin b/doc-xc/src/sgml/ref/fetch.sgmlin
deleted file mode 100644
index 628cdce89b..0000000000
--- a/doc-xc/src/sgml/ref/fetch.sgmlin
+++ /dev/null
@@ -1,583 +0,0 @@
-<!--
-doc/src/sgml/ref/fetch.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-FETCH">
- <refmeta>
-  <refentrytitle>FETCH</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>FETCH</refname>
-  <refpurpose>retrieve rows from a query using a cursor</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-fetch">
-  <primary>FETCH</primary>
- </indexterm>
-
- <indexterm zone="sql-fetch">
-  <primary>cursor</primary>
-  <secondary>FETCH</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<!-- Note the "direction" bit is also in ref/move.sgml -->
-<!## PG>
-<synopsis>
-FETCH [ <replaceable class="PARAMETER">direction</replaceable> [ FROM | IN ] ] <replaceable class="PARAMETER">cursor_name</replaceable>
-
-<phrase>where <replaceable class="PARAMETER">direction</replaceable> can be empty or one of:</phrase>
-
-    NEXT
-    PRIOR
-    FIRST
-    LAST
-    ABSOLUTE <replaceable class="PARAMETER">count</replaceable>
-    RELATIVE <replaceable class="PARAMETER">count</replaceable>
-    <replaceable class="PARAMETER">count</replaceable>
-    ALL
-    FORWARD
-    FORWARD <replaceable class="PARAMETER">count</replaceable>
-    FORWARD ALL
-    BACKWARD
-    BACKWARD <replaceable class="PARAMETER">count</replaceable>
-    BACKWARD ALL
-</synopsis>
-<!## end>
-<!## XC>
-<synopsis>
-FETCH [ <replaceable class="PARAMETER">direction</replaceable> [ FROM | IN ] ] <replaceable class="PARAMETER">cursor_name</replaceable>
-
-<phrase>where <replaceable class="PARAMETER">direction</replaceable> can be empty or one of:</phrase>
-
-    NEXT
-    RELATIVE <replaceable class="PARAMETER">count</replaceable>
-    <replaceable class="PARAMETER">count</replaceable>
-    FORWARD
-    FORWARD <replaceable class="PARAMETER">count</replaceable>
-    FORWARD ALL
-</synopsis>
-<!## end>
-<!## XL>
-<synopsis>
-FETCH [ <replaceable class="PARAMETER">direction</replaceable> [ FROM | IN ] ] <replaceable class="PARAMETER">cursor_name</replaceable>
-
-<phrase>where <replaceable class="PARAMETER">direction</replaceable> can be empty or one of:</phrase>
-
-    NEXT
-    RELATIVE <replaceable class="PARAMETER">count</replaceable>
-    <replaceable class="PARAMETER">count</replaceable>
-    FORWARD
-    FORWARD <replaceable class="PARAMETER">count</replaceable>
-    FORWARD ALL
-</synopsis>
-<!## end>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>FETCH</command> retrieves rows using a previously-created cursor.
-  </para>
-
-  <para>
-   A cursor has an associated position, which is used by
-   <command>FETCH</>.  The cursor position can be before the first row of the
-   query result, on any particular row of the result, or after the last row
-   of the result.  When created, a cursor is positioned before the first row.
-   After fetching some rows, the cursor is positioned on the row most recently
-   retrieved.  If <command>FETCH</> runs off the end of the available rows
-   then the cursor is left positioned after the last row, or before the first
-   row if fetching backward.  <command>FETCH ALL</> or <command>FETCH BACKWARD
-   ALL</> will always leave the cursor positioned after the last row or before
-   the first row.
-  </para>
-
-  <para>
-   The forms <literal>NEXT</>, <literal>PRIOR</>, <literal>FIRST</>,
-   <literal>LAST</>, <literal>ABSOLUTE</>, <literal>RELATIVE</> fetch
-   a single row after moving the cursor appropriately.  If there is no
-   such row, an empty result is returned, and the cursor is left
-   positioned before the first row or after the last row as
-   appropriate.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   The forms <literal>PRIOR</>, <literal>FIRST</>, <literal>LAST</>
-   and <literal>ABSOLUTE</> are not supported by the current release
-   of <productname>Postgres-XC</>
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   The forms <literal>PRIOR</>, <literal>FIRST</>, <literal>LAST</>
-   and <literal>ABSOLUTE</> are not supported by the current release
-   of <productname>Postgres-XL</>
-  </para>
-<!## end>
-
-  <para>
-   The forms using <literal>FORWARD</> and <literal>BACKWARD</>
-   retrieve the indicated number of rows moving in the forward or
-   backward direction, leaving the cursor positioned on the
-   last-returned row (or after/before all rows, if the <replaceable
-   class="PARAMETER">count</replaceable> exceeds the number of rows
-   available).
-  </para>
-<!## XC>
-&xconly;
-  <para>
-   The form using <literal>BACKWARD</> is not supported by the current
-   release of <productname>Postgres-XC</>.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   The form using <literal>BACKWARD</> is not supported in the current
-   release of <productname>Postgres-XL</>.
-  </para>
-<!## end>
-
-  <para>
-   <literal>RELATIVE 0</>, <literal>FORWARD 0</>, and
-   <literal>BACKWARD 0</> all request fetching the current row without
-   moving the cursor, that is, re-fetching the most recently fetched
-   row.  This will succeed unless the cursor is positioned before the
-   first row or after the last row; in which case, no row is returned.
-  </para>
-<!## XC>
-&xconly;
-  <para>
-   The form using <literal>BACKWARD</> is not supported by the current
-   release of <productname>Postgres-XC</>.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   The form using <literal>BACKWARD</> is not supported in the current
-   release of <productname>Postgres-XL</>.
-  </para>
-<!## end>
-
-  <note>
-   <para>
-    This page describes usage of cursors at the SQL command level.
-    If you are trying to use cursors inside a <application>PL/pgSQL</>
-    function, the rules are different &mdash;
-    see <xref linkend="plpgsql-cursors">.
-   </para>
-  </note>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">direction</replaceable></term>
-    <listitem>
-     <para>
-      <replaceable class="PARAMETER">direction</replaceable> defines
-      the fetch direction and number of rows to fetch.  It can be one
-      of the following:
-
-      <variablelist>
-       <varlistentry>
-        <term><literal>NEXT</literal></term>
-        <listitem>
-         <para>
-          Fetch the next row. This is the default if <replaceable
-          class="PARAMETER">direction</replaceable> is omitted.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>PRIOR</literal></term>
-        <listitem>
-         <para>
-          Fetch the prior row.
-         </para>
-<!## XC>
-&xconly;
-        <para>
-         <literal>PRIOR</literal> is not supported by the current
-         release of <productname>Postgres-XC</>.
-        </para>
-<!## end>
-<!## XL>
-&xlonly;
-        <para>
-         <literal>PRIOR</literal> is not supported by the current
-         release of <productname>Postgres-XL</>.
-        </para>
-<!## end>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>FIRST</literal></term>
-        <listitem>
-         <para>
-          Fetch the first row of the query (same as <literal>ABSOLUTE 1</literal>).
-         </para>
-<!## XC>
-&xconly;
-        <para>
-         <literal>FIRST</literal> is not supported by the current
-         release of <productname>Postgres-XC</>.
-        </para>
-<!## end>
-<!## XL>
-&xlonly;
-        <para>
-         <literal>FIRST</literal> is not supported by the current
-         release of <productname>Postgres-XL</>.
-        </para>
-<!## end>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>LAST</literal></term>
-        <listitem>
-         <para>
-          Fetch the last row of the query (same as <literal>ABSOLUTE -1</literal>).
-         </para>
-<!## XC>
-&xconly;
-        <para>
-         <literal>LAST</literal> is not supported by the current
-         release of <productname>Postgres-XC</>.
-        </para>
-<!## end>
-<!## XL>
-&xlonly;
-        <para>
-         <literal>LAST</literal> is not supported by the current
-         release of <productname>Postgres-XL</>.
-        </para>
-<!## end>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>ABSOLUTE <replaceable class="PARAMETER">count</replaceable></literal></term>
-        <listitem>
-         <para>
-          Fetch the <replaceable
-          class="PARAMETER">count</replaceable>'th row of the query,
-          or the <literal>abs(<replaceable
-          class="PARAMETER">count</replaceable>)</literal>'th row from
-          the end if <replaceable
-          class="PARAMETER">count</replaceable> is negative.  Position
-          before first row or after last row if <replaceable
-          class="PARAMETER">count</replaceable> is out of range; in
-          particular, <literal>ABSOLUTE 0</literal> positions before
-          the first row.
-         </para>
-<!## XC>
-&xconly;
-        <para>
-         <literal>ABSOLUTE</literal> is not supported by the current
-         release of <productname>Postgres-XC</>.
-        </para>
-<!## end>
-<!## XL>
-&xlonly;
-        <para>
-         <literal>ABSOLUTE</literal> is not supported by the current
-         release of <productname>Postgres-XL</>.
-        </para>
-<!## end>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>RELATIVE <replaceable class="PARAMETER">count</replaceable></literal></term>
-        <listitem>
-         <para>
-          Fetch the <replaceable
-          class="PARAMETER">count</replaceable>'th succeeding row, or
-          the <literal>abs(<replaceable
-          class="PARAMETER">count</replaceable>)</literal>'th prior
-          row if <replaceable class="PARAMETER">count</replaceable> is
-          negative.  <literal>RELATIVE 0</literal> re-fetches the
-          current row, if any.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><replaceable class="PARAMETER">count</replaceable></term>
-        <listitem>
-         <para>
-          Fetch the next <replaceable
-          class="PARAMETER">count</replaceable> rows (same as
-          <literal>FORWARD <replaceable
-          class="PARAMETER">count</replaceable></literal>).
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>ALL</literal></term>
-        <listitem>
-         <para>
-          Fetch all remaining rows (same as <literal>FORWARD ALL</literal>).
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>FORWARD</literal></term>
-        <listitem>
-         <para>
-          Fetch the next row (same as <literal>NEXT</literal>).
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>FORWARD <replaceable class="PARAMETER">count</replaceable></literal></term>
-        <listitem>
-         <para>
-          Fetch the next <replaceable
-          class="PARAMETER">count</replaceable> rows.
-          <literal>FORWARD 0</literal> re-fetches the current row.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>FORWARD ALL</literal></term>
-        <listitem>
-         <para>
-          Fetch all remaining rows.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>BACKWARD</literal></term>
-        <listitem>
-         <para>
-          Fetch the prior row (same as <literal>PRIOR</literal>).
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>BACKWARD <replaceable class="PARAMETER">count</replaceable></literal></term>
-        <listitem>
-         <para>
-          Fetch the prior <replaceable
-          class="PARAMETER">count</replaceable> rows (scanning
-          backwards).  <literal>BACKWARD 0</literal> re-fetches the
-          current row.
-         </para>
-<!## XC>
-&xconly;
-        <para>
-         <literal>BACKWARD</literal> is not supported by the current
-         release of <productname>Postgres-XC</>.
-        </para>
-<!## end>
-<!## XL>
-&xlonly;
-        <para>
-         <literal>BACKWARD</literal> is not supported by the current
-         release of <productname>Postgres-XL</>.
-        </para>
-<!## end>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>BACKWARD ALL</literal></term>
-        <listitem>
-         <para>
-          Fetch all prior rows (scanning backwards).
-         </para>
-<!## XC>
-&xconly;
-        <para>
-         <literal>BACKWARD ALL</literal> is not supported by the current
-         release of <productname>Postgres-XC</>.
-        </para>
-<!## end>
-<!## XL>
-&xlonly;
-        <para>
-         <literal>BACKWARD ALL</literal> is not supported by the current
-         release of <productname>Postgres-XL</>.
-        </para>
-<!## end>
-        </listitem>
-       </varlistentry>
-      </variablelist>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">count</replaceable></term>
-    <listitem>
-     <para>
-      <replaceable class="PARAMETER">count</replaceable> is a
-      possibly-signed integer constant, determining the location or
-      number of rows to fetch.  For <literal>FORWARD</> and
-      <literal>BACKWARD</> cases, specifying a negative <replaceable
-      class="PARAMETER">count</replaceable> is equivalent to changing
-      the sense of <literal>FORWARD</> and <literal>BACKWARD</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">cursor_name</replaceable></term>
-    <listitem>
-     <para>
-      An open cursor's name.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Outputs</title>
-
-  <para>
-   On successful completion, a <command>FETCH</> command returns a command
-   tag of the form
-<screen>
-FETCH <replaceable class="parameter">count</replaceable>
-</screen>
-   The <replaceable class="parameter">count</replaceable> is the number
-   of rows fetched (possibly zero).  Note that in
-   <application>psql</application>, the command tag will not actually be
-   displayed, since <application>psql</application> displays the fetched
-   rows instead.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   The cursor should be declared with the <literal>SCROLL</literal>
-   option if one intends to use any variants of <command>FETCH</>
-   other than <command>FETCH NEXT</> or <command>FETCH FORWARD</> with
-   a positive count.  For simple queries
-   <productname>PostgreSQL</productname> will allow backwards fetch
-   from cursors not declared with <literal>SCROLL</literal>, but this
-   behavior is best not relied on. If the cursor is declared with
-   <literal>NO SCROLL</literal>, no backward fetches are allowed.
-  </para>
-
-  <para>
-   <literal>ABSOLUTE</literal> fetches are not any faster than
-   navigating to the desired row with a relative move: the underlying
-   implementation must traverse all the intermediate rows anyway.
-   Negative absolute fetches are even worse: the query must be read to
-   the end to find the last row, and then traversed backward from
-   there.  However, rewinding to the start of the query (as with
-   <literal>FETCH ABSOLUTE 0</literal>) is fast.
-  </para>
-
-  <para>
-   <xref linkend="sql-declare">
-   is used to define a cursor.  Use
-   <xref linkend="sql-move">
-   to change cursor position without retrieving data.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   The following example traverses a table using a cursor:
-
-<programlisting>
-BEGIN WORK;
-
--- Set up a cursor:
-DECLARE liahona SCROLL CURSOR FOR SELECT * FROM films;
-
--- Fetch the first 5 rows in the cursor liahona:
-FETCH FORWARD 5 FROM liahona;
-
- code  |          title          | did | date_prod  |   kind   |  len
--------+-------------------------+-----+------------+----------+-------
- BL101 | The Third Man           | 101 | 1949-12-23 | Drama    | 01:44
- BL102 | The African Queen       | 101 | 1951-08-11 | Romantic | 01:43
- JL201 | Une Femme est une Femme | 102 | 1961-03-12 | Romantic | 01:25
- P_301 | Vertigo                 | 103 | 1958-11-14 | Action   | 02:08
- P_302 | Becket                  | 103 | 1964-02-03 | Drama    | 02:28
-
--- Fetch the previous row:
-FETCH PRIOR FROM liahona;
-
- code  |  title  | did | date_prod  |  kind  |  len
--------+---------+-----+------------+--------+-------
- P_301 | Vertigo | 103 | 1958-11-14 | Action | 02:08
-
--- Close the cursor and end the transaction:
-CLOSE liahona;
-COMMIT WORK;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard defines <command>FETCH</command> for use in
-   embedded SQL only.  The variant of <command>FETCH</command>
-   described here returns the data as if it were a
-   <command>SELECT</command> result rather than placing it in host
-   variables.  Other than this point, <command>FETCH</command> is
-   fully upward-compatible with the SQL standard.
-  </para>
-
-  <para>
-   The <command>FETCH</command> forms involving
-   <literal>FORWARD</literal> and <literal>BACKWARD</literal>, as well
-   as the forms <literal>FETCH <replaceable
-   class="PARAMETER">count</replaceable></literal> and <literal>FETCH
-   ALL</literal>, in which <literal>FORWARD</literal> is implicit, are
-   <productname>PostgreSQL</productname> extensions.
-  </para>
-
-  <para>
-   The SQL standard allows only <literal>FROM</> preceding the cursor
-   name; the option to use <literal>IN</>, or to leave them out altogether, is
-   an extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-close"></member>
-   <member><xref linkend="sql-declare"></member>
-   <member><xref linkend="sql-move"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/grant.sgmlin b/doc-xc/src/sgml/ref/grant.sgmlin
deleted file mode 100644
index 0d45e29ab3..0000000000
--- a/doc-xc/src/sgml/ref/grant.sgmlin
+++ /dev/null
@@ -1,672 +0,0 @@
-<!--
-doc/src/sgml/ref/grant.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-GRANT">
- <refmeta>
-  <refentrytitle>GRANT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>GRANT</refname>
-  <refpurpose>define access privileges</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-grant">
-  <primary>GRANT</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER }
-    [, ...] | ALL [ PRIVILEGES ] }
-    ON { [ TABLE ] <replaceable class="PARAMETER">table_name</replaceable> [, ...]
-         | ALL TABLES IN SCHEMA <replaceable class="PARAMETER">schema_name</replaceable> [, ...] }
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { { SELECT | INSERT | UPDATE | REFERENCES } ( <replaceable class="PARAMETER">column</replaceable> [, ...] )
-    [, ...] | ALL [ PRIVILEGES ] ( <replaceable class="PARAMETER">column</replaceable> [, ...] ) }
-    ON [ TABLE ] <replaceable class="PARAMETER">table_name</replaceable> [, ...]
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { { USAGE | SELECT | UPDATE }
-    [, ...] | ALL [ PRIVILEGES ] }
-    ON { SEQUENCE <replaceable class="PARAMETER">sequence_name</replaceable> [, ...]
-         | ALL SEQUENCES IN SCHEMA <replaceable class="PARAMETER">schema_name</replaceable> [, ...] }
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { { CREATE | CONNECT | TEMPORARY | TEMP } [, ...] | ALL [ PRIVILEGES ] }
-    ON DATABASE <replaceable>database_name</replaceable> [, ...]
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { USAGE | ALL [ PRIVILEGES ] }
-    ON FOREIGN DATA WRAPPER <replaceable>fdw_name</replaceable> [, ...]
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { USAGE | ALL [ PRIVILEGES ] }
-    ON FOREIGN SERVER <replaceable>server_name</replaceable> [, ...]
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { EXECUTE | ALL [ PRIVILEGES ] }
-    ON { FUNCTION <replaceable>function_name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">arg_name</replaceable> ] <replaceable class="parameter">arg_type</replaceable> [, ...] ] ) [, ...]
-         | ALL FUNCTIONS IN SCHEMA <replaceable class="PARAMETER">schema_name</replaceable> [, ...] }
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { USAGE | ALL [ PRIVILEGES ] }
-    ON LANGUAGE <replaceable>lang_name</replaceable> [, ...]
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { { SELECT | UPDATE } [, ...] | ALL [ PRIVILEGES ] }
-    ON LARGE OBJECT <replaceable class="PARAMETER">loid</replaceable> [, ...]
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { { CREATE | USAGE } [, ...] | ALL [ PRIVILEGES ] }
-    ON SCHEMA <replaceable>schema_name</replaceable> [, ...]
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT { CREATE | ALL [ PRIVILEGES ] }
-    ON TABLESPACE <replaceable>tablespace_name</replaceable> [, ...]
-    TO { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
-
-GRANT <replaceable class="PARAMETER">role_name</replaceable> [, ...] TO <replaceable class="PARAMETER">role_name</replaceable> [, ...] [ WITH ADMIN OPTION ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-grant-description">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   The <command>GRANT</command> command has two basic variants: one
-   that grants privileges on a database object (table, column, view, foreign
-   table, sequence, database, foreign-data wrapper, foreign server, function,
-   procedural language, schema, or tablespace), and one that grants
-   membership in a role.  These variants are similar in many ways, but
-   they are different enough to be described separately.
-  </para>
-
- <refsect2 id="sql-grant-description-objects">
-  <title>GRANT on Database Objects</title>
-
-  <para>
-   This variant of the <command>GRANT</command> command gives specific
-   privileges on a database object to
-   one or more roles.  These privileges are added
-   to those already granted, if any.
-  </para>
-
-  <para>
-   There is also an option to grant privileges on all objects of the same
-   type within one or more schemas.  This functionality is currently supported
-   only for tables, sequences, and functions (but note that <literal>ALL
-   TABLES</> is considered to include views and foreign tables).
-  </para>
-
-  <para>
-   The key word <literal>PUBLIC</literal> indicates that the
-   privileges are to be granted to all roles, including those that might
-   be created later.  <literal>PUBLIC</literal> can be thought of as an
-   implicitly defined group that always includes all roles.
-   Any particular role will have the sum
-   of privileges granted directly to it, privileges granted to any role it
-   is presently a member of, and privileges granted to
-   <literal>PUBLIC</literal>.
-  </para>
-
-  <para>
-   If <literal>WITH GRANT OPTION</literal> is specified, the recipient
-   of the privilege can in turn grant it to others.  Without a grant
-   option, the recipient cannot do that.  Grant options cannot be granted
-   to <literal>PUBLIC</literal>.
-  </para>
-
-  <para>
-   There is no need to grant privileges to the owner of an object
-   (usually the user that created it),
-   as the owner has all privileges by default.  (The owner could,
-   however, choose to revoke some of his own privileges for safety.)
-  </para>
-
-  <para>
-   The right to drop an object, or to alter its definition in any way, is
-   not treated as a grantable privilege; it is inherent in the owner,
-   and cannot be granted or revoked.  (However, a similar effect can be
-   obtained by granting or revoking membership in the role that owns
-   the object; see below.)  The owner implicitly has all grant
-   options for the object, too.
-  </para>
-
-  <para>
-   Depending on the type of object, the initial default privileges might
-   include granting some privileges to <literal>PUBLIC</literal>.
-   The default is no public access for tables, columns, schemas, and
-   tablespaces;
-   <literal>CONNECT</> privilege and <literal>TEMP</> table creation privilege
-   for databases;
-   <literal>EXECUTE</> privilege for functions; and
-   <literal>USAGE</> privilege for languages.
-   The object owner can of course revoke these privileges.  (For maximum
-   security, issue the <command>REVOKE</> in the same transaction that
-   creates the object; then there is no window in which another user
-   can use the object.)
-   Also, these initial default privilege settings can be changed using the
-   <xref linkend="sql-alterdefaultprivileges">
-   command.
-  </para>
-
-  <para>
-   The possible privileges are:
-
-   <variablelist>
-    <varlistentry>
-     <term>SELECT</term>
-     <listitem>
-      <para>
-       Allows <xref linkend="sql-select"> from
-       any column, or the specific columns listed, of the specified table,
-       view, or sequence.
-       Also allows the use of
-       <xref linkend="sql-copy"> TO.
-       This privilege is also needed to reference existing column values in
-       <xref linkend="sql-update"> or
-       <xref linkend="sql-delete">.
-       For sequences, this privilege also allows the use of the
-       <function>currval</function> function.
-       For large objects, this privilege allows the object to be read.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>INSERT</term>
-     <listitem>
-      <para>
-       Allows <xref linkend="sql-insert"> of a new
-       row into the specified table.  If specific columns are listed,
-       only those columns may be assigned to in the <command>INSERT</>
-       command (other columns will therefore receive default values).
-       Also allows <xref linkend="sql-copy"> FROM.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>UPDATE</term>
-     <listitem>
-      <para>
-       Allows <xref linkend="sql-update"> of any
-       column, or the specific columns listed, of the specified table.
-       (In practice, any nontrivial <command>UPDATE</> command will require
-       <literal>SELECT</> privilege as well, since it must reference table
-       columns to determine which rows to update, and/or to compute new
-       values for columns.)
-       <literal>SELECT ... FOR UPDATE</literal>
-       and <literal>SELECT ... FOR SHARE</literal>
-       also require this privilege on at least one column, in addition to the
-       <literal>SELECT</literal> privilege.  For sequences, this
-       privilege allows the use of the <function>nextval</function> and
-       <function>setval</function> functions.
-       For large objects, this privilege allows writing or truncating the
-       object.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>DELETE</term>
-     <listitem>
-      <para>
-       Allows <xref linkend="sql-delete"> of a row
-       from the specified table.
-       (In practice, any nontrivial <command>DELETE</> command will require
-       <literal>SELECT</> privilege as well, since it must reference table
-       columns to determine which rows to delete.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>TRUNCATE</term>
-     <listitem>
-      <para>
-       Allows <xref linkend="sql-truncate"> on
-       the specified table.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>REFERENCES</term>
-     <listitem>
-      <para>
-       To create a foreign key constraint, it is
-       necessary to have this privilege on both the referencing and
-       referenced columns.  The privilege may be granted for all columns
-       of a table, or just specific columns.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>TRIGGER</term>
-     <listitem>
-      <para>
-       Allows the creation of a trigger on the specified table.  (See the
-       <xref linkend="sql-createtrigger"> statement.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>CREATE</term>
-     <listitem>
-      <para>
-       For databases, allows new schemas to be created within the database.
-      </para>
-      <para>
-       For schemas, allows new objects to be created within the schema.
-       To rename an existing object, you must own the object <emphasis>and</>
-       have this privilege for the containing schema.
-      </para>
-      <para>
-       For tablespaces, allows tables, indexes, and temporary files to be
-       created within the tablespace, and allows databases to be created that
-       have the tablespace as their default tablespace.  (Note that revoking
-       this privilege will not alter the placement of existing objects.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>CONNECT</term>
-     <listitem>
-      <para>
-       Allows the user to connect to the specified database.  This
-       privilege is checked at connection startup (in addition to checking
-       any restrictions imposed by <filename>pg_hba.conf</>).
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>TEMPORARY</term>
-     <term>TEMP</term>
-     <listitem>
-      <para>
-       Allows temporary tables to be created while using the specified database.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>EXECUTE</term>
-     <listitem>
-      <para>
-       Allows the use of the specified function and the use of any
-       operators that are implemented on top of the function.  This is
-       the only type of privilege that is applicable to functions.
-       (This syntax works for aggregate functions, as well.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>USAGE</term>
-     <listitem>
-      <para>
-       For procedural languages, allows the use of the specified language for
-       the creation of functions in that language.  This is the only type
-       of privilege that is applicable to procedural languages.
-      </para>
-      <para>
-       For schemas, allows access to objects contained in the specified
-       schema (assuming that the objects' own privilege requirements are
-       also met).  Essentially this allows the grantee to <quote>look up</>
-       objects within the schema.  Without this permission, it is still
-       possible to see the object names, e.g. by querying the system tables.
-       Also, after revoking this permission, existing backends might have
-       statements that have previously performed this lookup, so this is not
-       a completely secure way to prevent object access.
-      </para>
-      <para>
-       For sequences, this privilege allows the use of the
-       <function>currval</function> and <function>nextval</function> functions.
-      </para>
-      <para>
-       For foreign-data wrappers, this privilege enables the grantee
-       to create new servers using that foreign-data wrapper.
-      </para>
-      <para>
-       For servers, this privilege enables the grantee to create,
-       alter, and drop his own user's user mappings associated with
-       that server.  Also, it enables the grantee to query the options
-       of the server and associated user mappings.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>ALL PRIVILEGES</term>
-     <listitem>
-      <para>
-       Grant all of the available privileges at once.
-       The <literal>PRIVILEGES</literal> key word is optional in
-<!## PG>
-       <productname>PostgreSQL</productname>, though it is required by
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</productname>, though it is required by
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</productname>, though it is required by
-<!## end>
-       strict SQL.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-   The privileges required by other commands are listed on the
-   reference page of the respective command.
-  </para>
- </refsect2>
-
- <refsect2 id="sql-grant-description-roles">
-  <title>GRANT on Roles</title>
-
-  <para>
-   This variant of the <command>GRANT</command> command grants membership
-   in a role to one or more other roles.  Membership in a role is significant
-   because it conveys the privileges granted to a role to each of its
-   members.
-  </para>
-
-  <para>
-   If <literal>WITH ADMIN OPTION</literal> is specified, the member can
-   in turn grant membership in the role to others, and revoke membership
-   in the role as well.  Without the admin option, ordinary users cannot do
-   that.  However,
-   database superusers can grant or revoke membership in any role to anyone.
-   Roles having <literal>CREATEROLE</> privilege can grant or revoke
-   membership in any role that is not a superuser.
-  </para>
-
-  <para>
-   Unlike the case with privileges, membership in a role cannot be granted
-   to <literal>PUBLIC</>.  Note also that this form of the command does not
-   allow the noise word <literal>GROUP</>.
-  </para>
- </refsect2>
- </refsect1>
-
-
- <refsect1 id="SQL-GRANT-notes">
-  <title>Notes</title>
-
-   <para>
-    The <xref linkend="sql-revoke"> command is used
-    to revoke access privileges.
-   </para>
-
-   <para>
-    Since <productname>PostgreSQL</productname> 8.1, the concepts of users and
-    groups have been unified into a single kind of entity called a role.
-    It is therefore no longer necessary to use the keyword <literal>GROUP</>
-    to identify whether a grantee is a user or a group.  <literal>GROUP</>
-    is still allowed in the command, but it is a noise word.
-   </para>
-
-   <para>
-    A user may perform <command>SELECT</>, <command>INSERT</>, etc. on a
-    column if he holds that privilege for either the specific column or
-    its whole table.  Granting the privilege at the table level and then
-    revoking it for one column will not do what you might wish: the
-    table-level grant is unaffected by a column-level operation.
-   </para>
-
-   <para>
-    When a non-owner of an object attempts to <command>GRANT</> privileges
-    on the object, the command will fail outright if the user has no
-    privileges whatsoever on the object.  As long as some privilege is
-    available, the command will proceed, but it will grant only those
-    privileges for which the user has grant options.  The <command>GRANT ALL
-    PRIVILEGES</> forms will issue a warning message if no grant options are
-    held, while the other forms will issue a warning if grant options for
-    any of the privileges specifically named in the command are not held.
-    (In principle these statements apply to the object owner as well, but
-    since the owner is always treated as holding all grant options, the
-    cases can never occur.)
-   </para>
-
-   <para>
-    It should be noted that database superusers can access
-    all objects regardless of object privilege settings.  This
-    is comparable to the rights of <literal>root</> in a Unix system.
-    As with <literal>root</>, it's unwise to operate as a superuser
-    except when absolutely necessary.
-   </para>
-
-   <para>
-    If a superuser chooses to issue a <command>GRANT</> or <command>REVOKE</>
-    command, the command is performed as though it were issued by the
-    owner of the affected object.  In particular, privileges granted via
-    such a command will appear to have been granted by the object owner.
-    (For role membership, the membership appears to have been granted
-    by the containing role itself.)
-   </para>
-
-   <para>
-    <command>GRANT</> and <command>REVOKE</> can also be done by a role
-    that is not the owner of the affected object, but is a member of the role
-    that owns the object, or is a member of a role that holds privileges
-    <literal>WITH GRANT OPTION</literal> on the object.  In this case the
-    privileges will be recorded as having been granted by the role that
-    actually owns the object or holds the privileges
-    <literal>WITH GRANT OPTION</literal>.  For example, if table
-    <literal>t1</> is owned by role <literal>g1</>, of which role
-    <literal>u1</> is a member, then <literal>u1</> can grant privileges
-    on <literal>t1</> to <literal>u2</>, but those privileges will appear
-    to have been granted directly by <literal>g1</>.  Any other member
-    of role <literal>g1</> could revoke them later.
-   </para>
-
-   <para>
-    If the role executing <command>GRANT</> holds the required privileges
-    indirectly via more than one role membership path, it is unspecified
-    which containing role will be recorded as having done the grant.  In such
-    cases it is best practice to use <command>SET ROLE</> to become the
-    specific role you want to do the <command>GRANT</> as.
-   </para>
-
-   <para>
-    Granting permission on a table does not automatically extend
-    permissions to any sequences used by the table, including
-    sequences tied to <type>SERIAL</> columns.  Permissions on
-    sequences must be set separately.
-   </para>
-
-   <para>
-    Use <xref linkend="app-psql">'s <command>\dp</command> command
-    to obtain information about existing privileges for tables and
-    columns.  For example:
-<programlisting>
-=&gt; \dp mytable
-                              Access privileges
- Schema |  Name   | Type  |   Access privileges   | Column access privileges 
---------+---------+-------+-----------------------+--------------------------
- public | mytable | table | miriam=arwdDxt/miriam | col1:
-                          : =r/miriam             :   miriam_rw=rw/miriam
-                          : admin=arw/miriam        
-(1 row)
-</programlisting>
-    The entries shown by <command>\dp</command> are interpreted thus:
-<literallayout class="monospaced">
-rolename=xxxx -- privileges granted to a role
-        =xxxx -- privileges granted to PUBLIC
-
-            r -- SELECT ("read")
-            w -- UPDATE ("write")
-            a -- INSERT ("append")
-            d -- DELETE
-            D -- TRUNCATE
-            x -- REFERENCES
-            t -- TRIGGER
-            X -- EXECUTE
-            U -- USAGE
-            C -- CREATE
-            c -- CONNECT
-            T -- TEMPORARY
-      arwdDxt -- ALL PRIVILEGES (for tables, varies for other objects)
-            * -- grant option for preceding privilege
-
-        /yyyy -- role that granted this privilege
-</literallayout>
-
-    The above example display would be seen by user <literal>miriam</> after
-    creating table <literal>mytable</> and doing:
-
-<programlisting>
-GRANT SELECT ON mytable TO PUBLIC;
-GRANT SELECT, UPDATE, INSERT ON mytable TO admin;
-GRANT SELECT (col1), UPDATE (col1) ON mytable TO miriam_rw;
-</programlisting>
-   </para>
-
-   <para>
-    For non-table objects there are other <command>\d</> commands
-    that can display their privileges.
-   </para>
-
-   <para>
-    If the <quote>Access privileges</> column is empty for a given object,
-    it means the object has default privileges (that is, its privileges column
-    is null).  Default privileges always include all privileges for the owner,
-    and can include some privileges for <literal>PUBLIC</> depending on the
-    object type, as explained above.  The first <command>GRANT</> or
-    <command>REVOKE</> on an object
-    will instantiate the default privileges (producing, for example,
-    <literal>{miriam=arwdDxt/miriam}</>) and then modify them per the
-    specified request.  Similarly, entries are shown in <quote>Column access
-    privileges</> only for columns with nondefault privileges.
-    (Note: for this purpose, <quote>default privileges</> always means the
-    built-in default privileges for the object's type.  An object whose
-    privileges have been affected by an <command>ALTER DEFAULT PRIVILEGES</>
-    command will always be shown with an explicit privilege entry that
-    includes the effects of the <command>ALTER</>.)
-   </para>
-
-   <para>
-    Notice that the owner's implicit grant options are not marked in the
-    access privileges display.  A <literal>*</> will appear only when
-    grant options have been explicitly granted to someone.
-   </para>
- </refsect1>
-
- <refsect1 id="sql-grant-examples">
-  <title>Examples</title>
-
-  <para>
-   Grant insert privilege to all users on table <literal>films</literal>:
-
-<programlisting>
-GRANT INSERT ON films TO PUBLIC;
-</programlisting>
-  </para>
-
-  <para>
-   Grant all available privileges to user <literal>manuel</literal> on view
-   <literal>kinds</literal>:
-
-<programlisting>
-GRANT ALL PRIVILEGES ON kinds TO manuel;
-</programlisting>
-
-   Note that while the above will indeed grant all privileges if executed by a
-   superuser or the owner of <literal>kinds</literal>, when executed by someone
-   else it will only grant those permissions for which the someone else has
-   grant options.
-  </para>
-
-  <para>
-   Grant membership in role <literal>admins</> to user <literal>joe</>:
-
-<programlisting>
-GRANT admins TO joe;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="sql-grant-compatibility">
-  <title>Compatibility</title>
-
-   <para>
-    According to the SQL standard, the <literal>PRIVILEGES</literal>
-    key word in <literal>ALL PRIVILEGES</literal> is required.  The
-    SQL standard does not support setting the privileges on more than
-    one object per command.
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> allows an object owner to revoke his
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> allows an object owner to revoke his
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> allows an object owner to revoke his
-<!## end>
-    own ordinary privileges: for example, a table owner can make the table
-    read-only to himself by revoking his own <literal>INSERT</>,
-    <literal>UPDATE</>, <literal>DELETE</>, and <literal>TRUNCATE</>
-    privileges.  This is not possible according to the SQL standard.  The
-<!## PG>
-    reason is that <productname>PostgreSQL</productname> treats the owner's
-<!## end>
-<!## XC>
-    reason is that <productname>Postgres-XC</productname> treats the owner's
-<!## end>
-<!## XL>
-    reason is that <productname>Postgres-XL</productname> treats the owner's
-<!## end>
-    privileges as having been granted by the owner to himself; therefore he
-    can revoke them too.  In the SQL standard, the owner's privileges are
-    granted by an assumed entity <quote>_SYSTEM</>.  Not being
-    <quote>_SYSTEM</>, the owner cannot revoke these rights.
-   </para>
-
-   <para>
-    The SQL standard provides for a <literal>USAGE</literal> privilege
-    on other kinds of objects: character sets, collations,
-    translations, domains.
-   </para>
-
-   <para>
-    Privileges on databases, tablespaces, schemas, and languages are
-<!## PG>
-    <productname>PostgreSQL</productname> extensions.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> extensions.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> extensions.
-<!## end>
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-revoke"></member>
-   <member><xref linkend="sql-alterdefaultprivileges"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/gtm.sgmlin b/doc-xc/src/sgml/ref/gtm.sgmlin
deleted file mode 100644
index 2694a04259..0000000000
--- a/doc-xc/src/sgml/ref/gtm.sgmlin
+++ /dev/null
@@ -1,420 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/initdb.sgml,v 1.47 2010/04/03 07:23:01 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-GTM">
- <refmeta>
-  <refentrytitle>gtm</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>gtm</refname>
-  <refpurpose>
-   provides global transaction management for the <productname>Postgres-XL</productname>
-   across the entire cluster.
-  </refpurpose>
- </refnamediv>
-
- <indexterm zone="app-gtm">
-  <primary>gtm</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>gtm</command>
-   <arg rep="repeat"><replaceable>option</></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-GTM-1">
-  <title>
-   Description
-  </title>
-&xlonly
-  <para>
-   gtm provides consistent transaction management fully compatible with
-   vanilla PostgreSQL. It is highly advised to start and stop gtm
-   using gtm_ctl(8).
-  </para>
-
-  <para>
-   You must provide a gtm configuration
-   file <filename>gtm.conf</filename> placed in the gtm working directory
-   as specified by <literal>-D</literal> command line option. The
-   configuration file specifies gtm running environment and resources.
-  </para>
-
-  <para>
-   Some of the parameters specified in the control file can be overridden by 
-   command line options.
-  </para>
-
-  <para>
-   As with other cluster components, the recommended method of
-   configuring and managing them is with the <xref linkend="pgxc-ctl"> utility.
- </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Configuration File</title>
-
-&xlonly
-  <para>
-   <literal>GTM</literal> configuration parameters are specified in the configuration file 
-   <filename>gtm.conf</filename><indexterm><primary>gtm.conf</></> placed in the working directory
-   specified as <literal>-D</literal> option
-   of <application>gtm</application> command line option as described
-   in the next section.
-  </para>
-  <para>
-   The format of the configuration file is patterned after the <filename>postgresql.conf</filename>.
-   The options are as follows.
-  </para>
-
-<!-- Add description of each gtm.conf entry -->
-<!-- Notice
-   The following options are found in the source code (gtm_opt.c) but is only for
-   internal use and will not be presented in the following list.
-
-    1. data_di
-    2. config_file
-
-   Also the following options are for high-availability hook.  This will be
-   documented later.
-
-   1. error_reporter
-   2. status_reader
--->
-  <variablelist>
-
-   <varlistentry id="gtm-opt-active-host" xreflabel="gtm_opt_active_host">
-    <term><varname>active_host</varname> (<type>string</type>)</term>
-    <indexterm>
-     <primary><varname>active_host</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies the listen addresses (host name or IP address) of active <application>gtm</application>.  This
-      parameter is effective only when this <application>gtm</application>
-      is specified as a standby.  There is no default value for this parameter.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-active-port" xreflabel="gtm_opt_active_port">
-    <term><varname>active_port</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>active_port</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies the port number of active <application>gtm</application>.  This
-      parameter is effective only when this <application>gtm</application>
-      is specified as a GTM standby. The standby connects to the primary gtm
-      to obtain a stream of updates of transaction status values.
-      There is no default value for this parameter.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-keepalives-count" xreflabel="gtm_opt_keepalives_count">
-    <term><varname>keepalives_count</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>keepalives_count</varname> (<type>integer</type>)</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies <literal>keepalives_count</literal> option for the
-      connection to <application>gtm</application>.  This option is
-      effective only when it runs as GTM Standby.
-      The default value is zero and keepalives feature is disabled.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-keepalives-idle" xreflabel="gtm_opt_keepalives_idle">
-    <term><varname>keepalives_idle</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>keepalives_idle</varname> (<type>integer</type>)</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies <literal>keepalives_idle</literal> option for the
-      connection to <application>gtm</application>.  This option is
-      effective only when it runs as GTM Standby.
-      The default value is zero and keepalives feature is disabled.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-keepalives-interval" xreflabel="gtm_opt_keepalives_interval">
-    <term><varname>keepalives_interval</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>keepalives_interval</varname> (<type>integer</type>)</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies <literal>keepalives_interval</literal> option for the
-      connection to <application>gtm</application>.  This option is
-      effective only when it runs as GTM Standby.
-      The default value is zero and keepalives feature is disabled.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-listen-addresses" xreflabel="gtm_opt_listen_addresses">
-    <term><varname>listen_addresses</varname> (<type>string</type>)</term>
-    <indexterm>
-     <primary><varname>listen_addresses</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies listen addresses (host name or IP address) of
-      this <application>gtm</application>
-      or <application>gtm</application> standby.
-      Default value is '*'.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-log-file" xreflabel="gtm_opt_log_file">
-    <term><varname>log_file</varname> (<type>string</type>)</term>
-    <indexterm>
-     <primary><varname>log_file</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies <filename>log</filename> file name.  This file will be
-      created in the working directory of
-      this <application>gtm</application> as specified
-      by <literal>-D</literal> command line option.
-      The default is <filename>gtm.log</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-log-min-messages" xreflabel="gtm_opt_log_min_messages">
-    <term><varname>log_min_messages</varname> (<type>enum</type>)</term>
-    <indexterm>
-     <primary><varname>log_min_messages</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Controls which message levels are written to the log. 
-      Valid values are <literal>DEBUG</literal>, <literal>DEBUG5</literal>, 
-      <literal>DEBUG4</literal>, <literal>DEBUG3</literal>, <literal>DEBUG2</literal>, 
-      <literal>DEBUG1</literal>, <literal>INFO</literal>, <literal>NOTICE</literal>, 
-      <literal>WARNING</literal>, <literal>ERROR</literal>, <literal>LOG</literal>, 
-      <literal>FATAL</literal> and <literal>PANIC</literal>.  
-      Each level includes all the levels that follow it.   
-      The later the level, the fewer messages are sent.   
-      The default is <literal>WARNING</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-nodename" xreflabel="gtm_opt_nodename">
-    <term><varname>nodename</varname> (<type>string</type>)</term>
-    <indexterm>
-     <primary><varname>nodename</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies the name of this <application>gtm</application> or <application>gtm</application> standby.
-      There is no default value for this parameter.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-port" xreflabel="gtm_opt_port">
-    <term><varname>port</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>port</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies the port number of <application>gtm</application> or <application>gtm</application> standby.
-      Default value is 6666.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-startup" xreflabel="gtm_opt_startup">
-    <term><varname>startup</varname> (<type>enum</type>)</term>
-    <indexterm>
-     <primary><varname>startup</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies the startup mode of this <application>gtm</application>.
-      Valied values are <literal>act</literal> or <literal>standby</literal>.
-      <literal>act</literal> means to start up
-      this <application>gtm</application> as usual so
-      that <application>gtm</application> clients (Coordinators, data
-      nodes or gtm-proxies) can connect for transaction
-      management.  <literal>standby</literal> means
-      this <application>gtm</application> starts up as a backup
-      of <literal>act</literal>
-      gtm.  <literal>standby</literal> <literal>gtm</literal> can be
-      promoted to <literal>act</literal> when <literal>act</literal>
-      fails.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-opt-synchronous-backup" xreflabel="gtm_opt_synchronous_backup">
-    <term><varname>synchronous-backup</varname> (<type>boolean</type>)</term>
-    <indexterm>
-     <primary><varname>synchronous-backup</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies if the backup to GTM-Standby is taken synchronously.   If this is turned on,
-      GTM will send and receive synchronize message to make sure that all the backups
-      reached to the standby.
-     </para>
-     <para>
-      If it is turned off, all the backup information will be sent without checking they
-      reached to GTM-Standby.
-     </para>
-     <para>
-      Default value is off.
-     </para>
-    </listitem>
-   </varlistentry>
-
-
-  </variablelist>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-
-  <para>
-   Options are specified with preceding '<literal>-</literal>', each
-   option may be associated with a value. They can be specified
-   in <literal>-o</literal> option of gtm_ctl(8).
-  </para>
-
-  <para>
-   Parameters specified as command line options override these specified in the configuration file described
-   in the previous section.
-  </para>
-
-  <para>
-   Options are as follows:
-  </para>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><option>D</option></term>
-     <listitem>
-      <para>
-       Specify a directory which holds data for gtm or gtm_proxy
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>l</option></term>
-     <listitem>
-      <para>
-       Specify a log file for gtm_ctl.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>x</option></term>
-     <listitem>
-      <para>
-       Specify the global transaction ID to start with. This is needed
-       when you start gtm for the first time
-       because <command>initdb</command> consumes XID locally and gtm
-       should start to give GXID greater than the last one
-       each <command>initdb</command> consumed locally. If gtm has
-       been shut down gracefully, then this value will be taken from
-       the last run.
-      </para>
-      <para>
-       If <literal>-x</literal> option is not specified at the first
-       run, initial global transaction ID value will be set to a
-       default initial value which is considered to be safe enough (in
-       version &version;, it is 10000).  If many statements are
-       involved in initdb, you should consider to increasing this
-       value.
-      </para>
-      <para>
-       To find the precise value to start with, you should
-       run <application>pg_controldata</application> to
-       find <literal>Latest checkpoint's NextXID</literal> of all the
-       Coordinators and Datanodes and choose the value larger than or
-       equals to the maximum value found.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>h</option></term>
-     <listitem>
-      <para>
-       Specify host name or IP address used.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>p</option></term>
-     <listitem>
-      <para>
-       Specify port number to listen.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-
-  <para>
-    When starting GTM as a standby instance, the following options can also be provided.
-  </para>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><option>s</option></term>
-     <listitem>
-      <para>
-       Specify if GTM starts as a standby
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>i</option></term>
-     <listitem>
-      <para>
-       Specify host name or IP address of active GTM instance to connect to
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>q</option></term>
-     <listitem>
-      <para>
-       Specify port number of active GTM instance to connect to
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/gtm_ctl.sgmlin b/doc-xc/src/sgml/ref/gtm_ctl.sgmlin
deleted file mode 100644
index 4353b8f486..0000000000
--- a/doc-xc/src/sgml/ref/gtm_ctl.sgmlin
+++ /dev/null
@@ -1,241 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/initdb.sgml,v 1.47 2010/04/03 07:23:01 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-GTM-CTL">
- <refmeta>
-  <refentrytitle>gtm_ctl</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>gtm_ctl</refname>
-  <refpurpose>
-   <productname>Postgres-XL</productname> GTM operation module
-  </refpurpose>
- </refnamediv>
-
- <indexterm zone="app-gtm-ctl">
-  <primary>gtm_proxy</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>gtm_proxy</command>
-   <arg rep="repeat"><replaceable>option</></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-GTM-CTL-1">
-  <title>
-   Description
-  </title>
-&xlonly
-  <para>
-   <command>gtm_ctl</command> starts/stops <command>gtm</command>
-   or <command>gtm_proxy</command>. The options specify the GTM
-   configuration.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Options</title>
-
-  <para>
-   Options are specified with preceding '<literal>-</literal>', each
-   option may be associated with a value.
-  </para>
-
-  <para>
-   Options are as follows:
-  </para>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><option>D</option></term>
-     <listitem>
-      <para>
-       Specify a directory which holds data
-       for <command>gtm</command> or <command>gtm_proxy</command>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>l</option></term>
-     <listitem>
-      <para>
-       Specify a log file for <command>gtm_ctl</command>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>m</option></term>
-     <listitem>
-      <para>
-       Set mode.  Value can
-       be <literal>smart</literal>, <literal>fast</literal>
-       or <literal>immediate</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>o</option></term>
-     <listitem>
-      <para>
-       Option method. This parameter will be passed down
-       to <command>gtm</command> or <command>gtm_proxy</command>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>p</option></term>
-     <listitem>
-      <para>
-       Set up postgres bin repository.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>S</option></term>
-     <listitem>
-      <para>
-       Specify which to start, gtm or gtm_proxy. The value can be
-       specified as <literal>gtm</literal>
-       or <literal>gtm_proxy</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>t</option></term>
-     <listitem>
-      <para>
-       Specify the wait time in seconds.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>W</option> or <option>w</option></term>
-     <listitem>
-      <para>
-       Wait option.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   <command>gtm_ctl</command> issues the following keywords to select
-   operations on <command>gtm</command>
-   and <command>gtm_proxy</command>.
-  </para>
-
-  <para>
-   <variablelist>
-
-    <varlistentry>
-     <term><option>start</option></term>
-     <listitem>
-      <para>
-       Start a GTM/GTM proxy instance.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>restart</option></term>
-     <listitem>
-      <para>
-       Restart a GTM/GTM proxy instance.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>stop</option></term>
-     <listitem>
-      <para>
-       Stop a GTM/GTM proxy instance.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>status</option></term>
-     <listitem>
-      <para>
-       Look at the status of GTM instance. If active, 1 is printed. If
-       standby, 0 is printed.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>promote</option></term>
-     <listitem>
-      <para>
-       Promote a GTM instance as active.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>reconnect</option></term>
-     <listitem>
-      <para>
-       Reconnect a GTM Proxy to another GTM instance.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-
-  <para>
-   Typically, you can issue the following command to start <command>gtm</command>/
-<programlisting>
-gtm_ctl start -Z gtm -D datafolder
-</programlisting>
-  </para>
-
-  <para>
-   Or <command>gtm_proxy</command>:
-<programlisting>
-gtm_ctl start -Z gtm_proxy -D datafolder_proxy
-</programlisting>
-  </para>
-
-  <para>
-   Promote a GTM as active:
-<programlisting>
-gtm_ctl promote -Z gtm -D datafolder
-</programlisting>
-  </para>
-
-  <para>
-   Reconnect a GTM proxy to another GTM instance:
-<programlisting>
-gtm_ctl reconnect -Z gtm_proxy -D datafolder_proxy -o '-s hostname -t port_number'
-</programlisting>
-  </para>
-
-  <para>
-   Look at the status of a GTM server:
-<programlisting>
-gtm_ctl status -Z gtm -D datafolder
-</programlisting>
-  </para>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/gtm_proxy.sgmlin b/doc-xc/src/sgml/ref/gtm_proxy.sgmlin
deleted file mode 100644
index 20a4e45b4b..0000000000
--- a/doc-xc/src/sgml/ref/gtm_proxy.sgmlin
+++ /dev/null
@@ -1,360 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/initdb.sgml,v 1.47 2010/04/03 07:23:01 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-GTM-PROXY">
- <refmeta>
-  <refentrytitle>gtm_proxy</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>gtm_proxy</refname>
-  <refpurpose>
-   Proxy to <command>gtm</command>, <productname>Postgres-XL</productname> Global Transaction Manager
-  </refpurpose>
- </refnamediv>
-
- <indexterm zone="app-gtm-proxy">
-  <primary>gtm_proxy</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>gtm_proxy</command>
-   <arg rep="repeat"><replaceable>option</></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-GTM-PROXY-1">
-  <title>
-   Description
-  </title>
-&xlonly
-  <para>
-   The Gtm proxy provides proxy feature from Postgres-XL Coordinator and
-   Datanode to gtm. Gtm proxy groups connections and interactions
-   between gtm and other Postgres-XL components to reduce both the
-   number of interactions and the size of messages. Performance tests
-   have shown greater performance with high concurrency workloads as a result.
-  </para>
-
-  <para>
-   It is highly advised to start and stop gtm_proxy with gtm_ctl(8).
-  </para>
-
-  <para>
-   You must provide a gtm configuration
-   file <filename>gtm_proxy.conf</filename> placed at the gtm working directory
-   as specified by <literal>-D</literal> command line option.  The
-   configuration file specifies gtm running environment and resources.
-  </para>
-
-  <para>
-   Some of the parameters specified in the control file can be overridden by 
-   command line options.
-  </para>
-
- </refsect1>
-
-<refsect1>
-  <title>Configuration File</title>
-
-&xlonly
-  <para>
-   <literal>GTM-Proxy</literal> configuration parameters are specified in the configuration file
-   <filename>gtm_proxy.conf</filename><indexterm><primary>gtm_proxy.conf</></> placed in the working directory
-   specified as <literal>-D</literal> option
-   of <application>gtm_proxy</application> command line option as described
-   in the next section.
-  </para>
-
-  <para>
-   The format of the configuration file is the same as <filename>postgresql.conf</filename>.
-   Options are as follows.
-  </para>
-
-<!-- Add description of each gtm.conf entry -->
-<!-- Notice                                                                                                           
-   The following options are found in the source code (gtm_opt.c) but is only for                                     
-   internal use and will not be presented in the following list.                                                      
-                                                                                                                      
-    1. data_dir
-    2. config_file
-
-   Also the following options are for high-availability hook.  This will be
-   documented later.
-   1. error_reporter
-   2. status_reader
--->
-  <variablelist>
-
-   <varlistentry id="gtm-proxy-opt-gtm-connect-retry-interval" xreflabel="gtm_proxy_opt_gtm_connect_retry_interval">
-    <term><varname>gtm_connect_retry_interval</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>gtm_connect_retry_interval</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies how long in seconds GTM-Proxy waits between each retry to connect to GTM when
-      communication error with GTM is detected.
-      Default value is 60.
-      Refer to <varname>gtm_connect_retry_count</varname> and <varname>gtm_connect_retry_idle</varname>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-gtm-host" xreflabel="gtm_proxy_opt_gtm_host">
-    <term><varname>gtm_host</varname> (<type>string</type>)</term>
-    <indexterm>
-     <primary><varname>gtm_host</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies listen addresses (host name or IP address) of <application>gtm</application>.
-      There is no default value for this parameter.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-gtm-port" xreflabel="gtm_proxy_opt_gtm_port">
-    <term><varname>gtm_port</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>gtm_port</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies the port number of <application>gtm</application>.
-      There is no default value for this parameter.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-keepalives-count" xreflabel="gtm_proxy_opt_keepalives_count">
-    <term><varname>keepalives_count</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>keepalives_count</varname> (<type>integer</type>)</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies <literal>keepalives_count</literal> option for the
-      connection to <application>gtm</application>.
-      Default value is zero and keepalives feature is disabled.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-keepalives-idle" xreflabel="gtm_proxy_opt_keepalives_idle">
-    <term><varname>keepalives_idle</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>keepalives_idle</varname> (<type>integer</type>)</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies <literal>keepalives_idle</literal> option for the
-      connection to <application>gtm</application>.
-      Default value is zero and keepalives feature is disabled.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-keepalives-interval" xreflabel="gtm_proxy_opt_keepalives_interval">
-    <term><varname>keepalives_interval</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>keepalives_interval</varname> (<type>integer</type>)</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies <literal>keepalives_interval</literal> option for the
-      connection to <application>gtm</application>.
-      Default value is zero and keepalives feature is disabled.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-log-file" xreflabel="gtm_proxy_opt_log_file">
-    <term><varname>log_file</varname> (<type>string</type>)</term>
-    <indexterm>
-     <primary><varname>log_file</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies <filename>log</filename> file name.  This file will be
-      created in the working directory of
-      this <application>gtm_proxy</application> as specified
-      by <literal>-D</literal> command line option.
-      The default is <filename>gtm_proxy.log</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-log-min-messages" xreflabel="gtm_proxy_opt_log_min_messages">
-    <term><varname>log_min_messages</varname> (<type>enum</type>)</term>
-    <indexterm>
-     <primary><varname>log_min_messages</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Controls which message levels are written to the log.
-      Valid values are <literal>DEBUG</literal>, <literal>DEBUG5</literal>,
-      <literal>DEBUG4</literal>, <literal>DEBUG3</literal>, <literal>DEBUG2</literal>,
-      <literal>DEBUG1</literal>, <literal>INFO</literal>, <literal>NOTICE</literal>,
-      <literal>WARNING</literal>, <literal>ERROR</literal>, <literal>LOG</literal>,
-      <literal>FATAL</literal> and <literal>PANIC</literal>.
-      Each level includes all the levels that follow it.
-      The later the level, the fewer messages are sent.
-      The default is <literal>WARNING</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-listen-addresses" xreflabel="gtm_proxy_opt_listen_addresses">
-    <term><varname>listen_addresses</varname> (<type>string</type>)</term>
-    <indexterm>
-     <primary><varname>listen_addresses</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies listen addresses (host name or IP address) of
-      this <application>gtm_proxy</application>.
-      Default value is '*'.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-nodename" xreflabel="gtm_proxy_opt_nodename">
-    <term><varname>nodename</varname> (<type>string</type>)</term>
-    <indexterm>
-     <primary><varname>nodename</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies the name of this <application>gtm_proxy</application>.
-      There is no default value for this parameter.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-port" xreflabel="gtm_proxy_opt_port">
-    <term><varname>port</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>port</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies the port number of this <application>gtm_proxy</application>.
-      The default port value is 6666.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="gtm-proxy-opt-worker-threads" xreflabel="gtm_proxy_opt_worker_threads">
-    <term><varname>worker_threads</varname> (<type>integer</type>)</term>
-    <indexterm>
-     <primary><varname>worker_threads</varname> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      Specifies the number of worker threads for this <literal>gtm_proxy</literal>.
-      The default value is 1.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
- </refsect1>
-
- <refsect1>
-  <title>Options</title>
-
-  <para>
-   Options are specified with preceding '<literal>-</literal>', each
-   option may be associated with a value. They can be specified
-   in <literal>-o</literal> option of gtm_ctl(8).
-  </para>
-
-  <para>
-   Options are as follows:
-  </para>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><option>D</option></term>
-     <listitem>
-      <para>
-       Specify a directory which holds data for <command>gtm_proxy</command>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>l</option></term>
-     <listitem>
-      <para>
-       Specify a log file for <command>gtm_ctl</command>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>h</option></term>
-     <listitem>
-      <para>
-       Specify host name or IP address used by the <command>gtm_proxy</command>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>p</option></term>
-     <listitem>
-      <para>
-       Specify port number to listen on.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>i</option></term>
-     <listitem>
-      <para>
-       Specify gtm_proxy id, which is registered to gtm.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>n</option></term>
-     <listitem>
-      <para>
-       Specify number of worker threads of gtm_proxy.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>s</option></term>
-     <listitem>
-      <para>
-       Specify host name or IP address of target gtm.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>t</option></term>
-     <listitem>
-      <para>
-       Specify port number of target gtm.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/initdb.sgmlin b/doc-xc/src/sgml/ref/initdb.sgmlin
deleted file mode 100644
index 476d1ab3eb..0000000000
--- a/doc-xc/src/sgml/ref/initdb.sgmlin
+++ /dev/null
@@ -1,443 +0,0 @@
-<!--
-doc/src/sgml/ref/initdb.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-INITDB">
- <refmeta>
-  <refentrytitle>initdb</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>initdb</refname>
-<!## PG>
-  <refpurpose>create a new <productname>PostgreSQL</productname> database cluster</refpurpose>
-<!## end>
-<!## XC>
-  <refpurpose>create a new <productname>Postgres-XC</productname> Coordinator or Datanode database cluster</refpurpose>
-<!## end>
-<!## XL>
-  <refpurpose>create a new <productname>Postgres-XL</productname> Coordinator or Datanode database cluster</refpurpose>
-<!## end>
- </refnamediv>
-
- <indexterm zone="app-initdb">
-  <primary>initdb</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>initdb</command>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-   <arg>--nodename <replaceable>nodename</replaceable></arg>
-   <group choice="plain">
-    <arg>--pgdata</arg>
-    <arg>-D </arg>
-    <replaceable>directory</replaceable>
-   </group>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-INITDB-1">
-  <title>
-   Description
-  </title>
-&common;
-  <para>
-   <command>initdb</command> creates a new
-<!## PG>
-   <productname>PostgreSQL</productname> database cluster.  A database
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> database cluster for Coordinator or Datanode.  A database
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> database cluster for Coordinator or Datanode.  A database
-<!## end>
-   cluster is a collection of databases that are managed by a single
-   server instance.
-  </para>
-
-  <para>
-   Creating a database cluster consists of creating the directories in
-   which the database data will live, generating the shared catalog
-   tables (tables that belong to the whole cluster rather than to any
-   particular database), and creating the <literal>template1</literal>
-   and <literal>postgres</literal> databases. When you later create a
-   new database, everything in the <literal>template1</literal> database is
-   copied.  (Therefore, anything installed in <literal>template1</literal>
-   is automatically copied into each database created later.)
-   The <literal>postgres</literal> database is a default database meant
-   for use by users, utilities and third party applications.
-  </para>
-
-  <para>
-   Although <command>initdb</command> will attempt to create the
-   specified data directory, it might not have permission if the parent
-   directory of the desired data directory is root-owned. To initialize
-   in such a setup, create an empty data directory as root, then use
-   <command>chown</command> to assign ownership of that directory to the
-   database user account, then <command>su</command> to become the
-   database user to run <command>initdb</command>.
-  </para>
-
-  <para>
-   <command>initdb</command> must be run as the user that will own the
-   server process, because the server needs to have access to the
-   files and directories that <command>initdb</command> creates.
-   Since the server cannot be run as root, you must not run
-   <command>initdb</command> as root either.  (It will in fact refuse
-   to do so.)
-  </para>
-
-  <para>
-   <command>initdb</command> initializes the database cluster's default
-   locale and character set encoding. The character set encoding,
-   collation order (<literal>LC_COLLATE</>) and character set classes
-   (<literal>LC_CTYPE</>, e.g. upper, lower, digit) can be set separately
-   for a database when it is created. <command>initdb</command> determines
-   those settings for the <literal>template1</literal> database, which will
-   serve as the default for all other databases.
-  </para>
-
-  <para>
-   To alter the default collation order or character set classes, use the
-   <option>--lc-collate</option> and <option>--lc-ctype</option> options.
-   Collation orders other than <literal>C</> or <literal>POSIX</> also have
-   a performance penalty.  For these reasons it is important to choose the
-   right locale when running <command>initdb</command>.
-  </para>
-
-  <para>
-   The remaining locale categories can be changed later when the server
-   is started.  You can also use <option>--locale</option> to set the
-   default for all locale categories, including collation order and
-   character set classes. All server locale values (<literal>lc_*</>) can
-   be displayed via <command>SHOW ALL</>.
-   More details can be found in <xref linkend="locale">.
-  </para>
-
-  <para>
-   To alter the default encoding, use the <option>--encoding</option>.
-   More details can be found in <xref linkend="multibyte">.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>initdb</> will be performed locally.  This has to be
-   performed for each Coordinators and Datanodes manually.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>initdb</> will be performed locally.  This has to be
-   performed for each Coordinators and Datanodes manually.
-  </para>
-<!## end>
-
- </refsect1>
-
- <refsect1>
-  <title>Options</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><option>-A <replaceable class="parameter">authmethod</replaceable></option></term>
-      <term><option>--auth=<replaceable class="parameter">authmethod</replaceable></option></term>
-      <listitem>
-       <para>
-        This option specifies the authentication method for local users
-        used in <filename>pg_hba.conf</>.  Do not use <literal>trust</>
-        unless you trust all local users on your system.  <literal>Trust</>
-        is the default for ease of installation.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-D <replaceable class="parameter">directory</replaceable></option></term>
-      <term><option>--pgdata=<replaceable class="parameter">directory</replaceable></option></term>
-      <listitem>
-       <para>
-        This option specifies the directory where the database cluster
-        should be stored. This is the only information required by
-        <command>initdb</command>, but you can avoid writing it by
-        setting the <envar>PGDATA</envar> environment variable, which
-        can be convenient since the database server
-        (<command>postgres</command>) can find the database
-        directory later by the same variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-<!## XC>
-     <varlistentry>
-       <term><option>--nodename=<replaceable class="parameter">nodename</replaceable></option></term>
-       <listitem>
-       <para>
-       Set the name of Postgres-XC node initialized. This option is mandatory when setting a node.
-       It permits one to define the node itself in cluster node catalog
-       <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>. The node name
-       specified is also added in <filename>postgresql.conf</> as value of <varname>pgxc_node_name</>.
-       </para>
-       </listitem>
-     </varlistentry>
-<!## end>
-<!## XL>
-     <varlistentry>
-       <term><option>--nodename=<replaceable class="parameter">nodename</replaceable></option></term>
-       <listitem>
-       <para>
-       Set the name of Postgres-XL node initialized. This option is mandatory when setting a node.
-       It permits one to define the node itself in cluster node catalog
-       <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>. The node name
-       specified is also added in <filename>postgresql.conf</> as value of <varname>pgxc_node_name</>.
-       </para>
-       </listitem>
-     </varlistentry>
-<!## end>
-
-     <varlistentry>
-      <term><option>-E <replaceable class="parameter">encoding</replaceable></option></term>
-      <term><option>--encoding=<replaceable class="parameter">encoding</replaceable></option></term>
-      <listitem>
-       <para>
-        Selects the encoding of the template database. This will also
-        be the default encoding of any database you create later,
-        unless you override it there.  The default is derived from the locale, or
-        <literal>SQL_ASCII</literal> if that does not work. The character sets supported by
-<!## PG>
-        the <productname>PostgreSQL</productname> server are described
-<!## end>
-<!## XC>
-        the <productname>Postgres-XC</productname> server are described
-<!## end>
-<!## XL>
-        the <productname>Postgres-XL</productname> server are described
-<!## end>
-        in <xref linkend="multibyte-charset-supported">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--locale=<replaceable>locale</replaceable></option></term>
-      <listitem>
-       <para>
-        Sets the default locale for the database cluster.  If this
-        option is not specified, the locale is inherited from the
-        environment that <command>initdb</command> runs in. Locale
-        support is described in <xref linkend="locale">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--lc-collate=<replaceable>locale</replaceable></option></term>
-      <term><option>--lc-ctype=<replaceable>locale</replaceable></option></term>
-      <term><option>--lc-messages=<replaceable>locale</replaceable></option></term>
-      <term><option>--lc-monetary=<replaceable>locale</replaceable></option></term>
-      <term><option>--lc-numeric=<replaceable>locale</replaceable></option></term>
-      <term><option>--lc-time=<replaceable>locale</replaceable></option></term>
-
-      <listitem>
-       <para>
-        Like <option>--locale</option>, but only sets the locale in
-        the specified category.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--pwfile=<replaceable>filename</></option></term>
-      <listitem>
-       <para>
-        Makes <command>initdb</command> read the database superuser's password
-        from a file.  The first line of the file is taken as the password.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></option></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></option></term>
-      <listitem>
-       <para>
-        Selects the user name of the database superuser. This defaults
-        to the name of the effective user running
-        <command>initdb</command>. It is really not important what the
-        superuser's name is, but one might choose to keep the
-        customary name <systemitem>postgres</systemitem>, even if the operating
-        system user's name is different.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option></term>
-      <term><option>--pwprompt</option></term>
-      <listitem>
-       <para>
-        Makes <command>initdb</command> prompt for a password
-        to give the database superuser. If you don't plan on using password
-        authentication, this is not important.  Otherwise you won't be
-        able to use password authentication until you have a password
-        set up.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-X <replaceable class="parameter">directory</replaceable></option></term>
-      <term><option>--xlogdir=<replaceable class="parameter">directory</replaceable></option></term>
-      <listitem>
-       <para>
-        This option specifies the directory where the transaction log
-        should be stored.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    Other, less commonly used, parameters are also available:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-d</option></term>
-      <term><option>--debug</option></term>
-      <listitem>
-       <para>
-        Print debugging output from the bootstrap backend and a few other
-        messages of lesser interest for the general public.
-        The bootstrap backend is the program <command>initdb</command>
-        uses to create the catalog tables.  This option generates a tremendous
-        amount of extremely boring output.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-L <replaceable class="parameter">directory</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies where <command>initdb</command> should find
-        its input files to initialize the database cluster.  This is
-        normally not necessary.  You will be told if you need to
-        specify their location explicitly.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-n</option></term>
-      <term><option>--noclean</option></term>
-      <listitem>
-       <para>
-        By default, when <command>initdb</command>
-        determines that an error prevented it from completely creating the database
-        cluster, it removes any files it might have created before discovering
-        that it cannot finish the job. This option inhibits tidying-up and is
-        thus useful for debugging.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>initdb</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>initdb</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATA</envar></term>
-
-    <listitem>
-     <para>
-      Specifies the directory where the database cluster is to be
-      stored; can be overridden using the <option>-D</option> option.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-<!## PG>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-<!## end>
-<!## XC>
-   This utility, like most other <productname>Postgres-XC</> utilities,
-<!## end>
-<!## XL>
-   This utility, like most other <productname>Postgres-XL</> utilities,
-<!## end>
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>initdb</> runs only locally.  You should
-   run <command>initdb</> for each Coordinator and Datanode.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>initdb</> runs only locally.  You should
-   run <command>initdb</> for each Coordinator and Datanode.
-  </para>
-<!## end>
-&common;
-  <para>
-   <command>initdb</command> can also be invoked via
-   <command>pg_ctl initdb</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-pg-ctl"></member>
-   <member><xref linkend="app-postgres"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/initgtm.sgmlin b/doc-xc/src/sgml/ref/initgtm.sgmlin
deleted file mode 100644
index 0679da8ce9..0000000000
--- a/doc-xc/src/sgml/ref/initgtm.sgmlin
+++ /dev/null
@@ -1,405 +0,0 @@
-<!--
-doc/src/sgml/ref/initgtm.sgml
-Postgres-XC documentation
--->
-
-<!## XC>
-<refentry id="APP-INITGTM">
- <refmeta>
-  <refentrytitle>initgtm</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>initgtm</refname>
-  <refpurpose>create a new <productname>Postgres-XC</productname> GTM or GTM-Proxy for database cluster</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-initgtm">
-  <primary>initgtm</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>initgtm</command>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-   <group choice="plain">
-    <arg>--pgdata</arg>
-    <arg>-D </arg>
-    <replaceable>directory</replaceable>
-   </group>
-   <arg choice="plain">-Z <replaceable>nodetype</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-INITGTM-1">
-  <title>
-   Description
-  </title>
-&common;
-  <para>
-   <command>initgtm</command> creates a new GTM or GTM-Proxy node for a
-   <productname>Postgres-XC</productname> database cluster.  A database
-   cluster has a unique GTM. A GTM-Proxy acts as an intermediate component
-   between GTM and Postgres-XC nodes to group request messages. Each Coordinator
-   and Datanode of the cluster need to register to GTM when starting up.
-  </para>
-
-  <para>
-   Creating a GTM for cluster consists of creating the directories and files in
-   which the GTM data will live.
-  </para>
-
-  <para>
-   Although <command>initgtm</command> will attempt to create the
-   specified data directory, it might not have permission if the parent
-   directory of the desired data directory is root-owned. To initialize
-   in such a setup, create an empty data directory as root, then use
-   <command>chown</command> to assign ownership of that directory to the
-   database user account, then <command>su</command> to become the
-   database user to run <command>initgtm</command>.
-  </para>
-
-  <para>
-   <command>initgtm</command> must be run as the user that will own the
-   server process, because the server needs to have access to the
-   files and directories that <command>initgtm</command> creates.
-   Since the server cannot be run as root, you must not run
-   <command>initgtm</command> as root either.  (It will in fact refuse
-   to do so.)
-  </para>
-
-&xconly;
-  <para>
-   <command>initgtm</> will be performed locally.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Options</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><option>-D <replaceable class="parameter">directory</replaceable></option></term>
-      <term><option>--pgdata=<replaceable class="parameter">directory</replaceable></option></term>
-      <listitem>
-       <para>
-        This option specifies the directory where the GTM data
-        should be stored. Data folder and node type are the only information
-        required by <command>initgtm</command>. You can avoid writing it by
-        setting the <envar>PGDATA</envar> environment variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-Z <replaceable class="parameter">nodetype</replaceable></option></term>
-      <listitem>
-       <para>
-        This option specifies the node type which is initialized. It is possible to
-        specify gtm to set up a GTM node, or gtm_proxy to set up a GTM-Proxy.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    Other, less commonly used, parameters are also available:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-d</option></term>
-      <term><option>--debug</option></term>
-      <listitem>
-       <para>
-        Print debugging output from the bootstrap backend and a few other
-        messages of lesser interest for the general public.
-        The bootstrap backend is the program <command>initgtm</command>
-        uses to create the catalog tables.  This option generates a tremendous
-        amount of extremely boring output.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-n</option></term>
-      <term><option>--noclean</option></term>
-      <listitem>
-       <para>
-        By default, when <command>initgtm</command>
-        determines that an error prevented it from completely creating GTM data
-        it removes any files it might have created before discovering
-        that it cannot finish the job. This option inhibits tidying-up and is
-        thus useful for debugging.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>initgtm</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>initgtm</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATA</envar></term>
-
-    <listitem>
-     <para>
-      Specifies the directory where the GTM data is to be
-      stored; can be overridden using the <option>-D</option> option.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-&xconly;
-  <para>
-   <command>initgtm</> runs only locally.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-gtm-ctl"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
-<!## end>
-<!## XL>
-<refentry id="APP-INITGTM">
- <refmeta>
-  <refentrytitle>initgtm</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>initgtm</refname>
-  <refpurpose>create a new <productname>Postgres-XL</productname> GTM or GTM-Proxy for database cluster</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-initgtm">
-  <primary>initgtm</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>initgtm</command>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-   <group choice="plain">
-    <arg>--pgdata</arg>
-    <arg>-D </arg>
-    <replaceable>directory</replaceable>
-   </group>
-   <arg choice="plain">-Z <replaceable>nodetype</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-INITGTM-1">
-  <title>
-   Description
-  </title>
-&common;
-  <para>
-   <command>initgtm</command> creates a new GTM or GTM-Proxy node for a
-   <productname>Postgres-XL</productname> database cluster.  A database
-   cluster has a unique GTM. A GTM-Proxy acts as an intermediate component
-   between GTM and Postgres-XL nodes to group request messages. Each Coordinator
-   and Datanode of the cluster need to register to GTM when starting up.
-  </para>
-
-  <para>
-   Creating a GTM for cluster consists of creating the directories and files in
-   which the GTM data will live.
-  </para>
-
-  <para>
-   Although <command>initgtm</command> will attempt to create the
-   specified data directory, it might not have permission if the parent
-   directory of the desired data directory is root-owned. To initialize
-   in such a setup, create an empty data directory as root, then use
-   <command>chown</command> to assign ownership of that directory to the
-   database user account, then <command>su</command> to become the
-   database user to run <command>initgtm</command>.
-  </para>
-
-  <para>
-   <command>initgtm</command> must be run as the user that will own the
-   server process, because the server needs to have access to the
-   files and directories that <command>initgtm</command> creates.
-   Since the server cannot be run as root, you must not run
-   <command>initgtm</command> as root either.  (It will in fact refuse
-   to do so.)
-  </para>
-
-&xlonly;
-  <para>
-   <command>initgtm</> will be performed locally.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Options</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><option>-D <replaceable class="parameter">directory</replaceable></option></term>
-      <term><option>--pgdata=<replaceable class="parameter">directory</replaceable></option></term>
-      <listitem>
-       <para>
-        This option specifies the directory where the GTM data
-        should be stored. Data folder and node type are the only information
-        required by <command>initgtm</command>. You can avoid writing it by
-        setting the <envar>PGDATA</envar> environment variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-Z <replaceable class="parameter">nodetype</replaceable></option></term>
-      <listitem>
-       <para>
-        This option specifies the node type which is initialized. It is possible to
-        specify gtm to set up a GTM node, or gtm_proxy to set up a GTM-Proxy.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    Other, less commonly used, parameters are also available:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-d</option></term>
-      <term><option>--debug</option></term>
-      <listitem>
-       <para>
-        Print debugging output from the bootstrap backend and a few other
-        messages of lesser interest for the general public.
-        The bootstrap backend is the program <command>initgtm</command>
-        uses to create the catalog tables.  This option generates a tremendous
-        amount of extremely boring output.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-n</option></term>
-      <term><option>--noclean</option></term>
-      <listitem>
-       <para>
-        By default, when <command>initgtm</command>
-        determines that an error prevented it from completely creating GTM data
-        it removes any files it might have created before discovering
-        that it cannot finish the job. This option inhibits tidying-up and is
-        thus useful for debugging.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>initgtm</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>initgtm</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATA</envar></term>
-
-    <listitem>
-     <para>
-      Specifies the directory where the GTM data is to be
-      stored; can be overridden using the <option>-D</option> option.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-&xlonly;
-  <para>
-   <command>initgtm</> runs only locally.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-gtm-ctl"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
-<!## end>
diff --git a/doc-xc/src/sgml/ref/insert.sgmlin b/doc-xc/src/sgml/ref/insert.sgmlin
deleted file mode 100644
index 726b0e5d80..0000000000
--- a/doc-xc/src/sgml/ref/insert.sgmlin
+++ /dev/null
@@ -1,328 +0,0 @@
-<!--
-doc/src/sgml/ref/insert.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-INSERT">
- <refmeta>
-  <refentrytitle>INSERT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>INSERT</refname>
-  <refpurpose>create new rows in a table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-insert">
-  <primary>INSERT</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-[ WITH [ RECURSIVE ] <replaceable class="parameter">with_query</replaceable> [, ...] ]
-INSERT INTO <replaceable class="PARAMETER">table</replaceable> [ ( <replaceable class="PARAMETER">column</replaceable> [, ...] ) ]
-    { DEFAULT VALUES | VALUES ( { <replaceable class="PARAMETER">expression</replaceable> | DEFAULT } [, ...] ) [, ...] | <replaceable class="PARAMETER">query</replaceable> }
-    [ RETURNING * | <replaceable class="parameter">output_expression</replaceable> [ [ AS ] <replaceable class="parameter">output_name</replaceable> ] [, ...] ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>INSERT</command> inserts new rows into a table.
-   One can insert one or more rows specified by value expressions,
-   or zero or more rows resulting from a query.
-  </para>
-
-  <para>
-   Each column not present in the explicit or implicit column list will be
-   filled with a default value, either its declared default value
-   or null if there is none.
-  </para>
-
-  <para>
-   If the expression for any column is not of the correct data type,
-   automatic type conversion will be attempted.
-  </para>
-
-  <para>
-   The optional <literal>RETURNING</> clause causes <command>INSERT</>
-   to compute and return value(s) based on each row actually inserted.
-   This is primarily useful for obtaining values that were supplied by
-   defaults, such as a serial sequence number.  However, any expression
-   using the table's columns is allowed.  The syntax of the
-   <literal>RETURNING</> list is identical to that of the output list
-   of <command>SELECT</>.
-  </para>
-
-  <para>
-   You must have <literal>INSERT</literal> privilege on a table in
-   order to insert into it.  If a column list is specified, you only
-   need <literal>INSERT</literal> privilege on the listed columns.
-   Use of the <literal>RETURNING</> clause requires <literal>SELECT</>
-   privilege on all columns mentioned in <literal>RETURNING</>.
-   If you use the <replaceable
-   class="PARAMETER">query</replaceable> clause to insert rows from a
-   query, you of course need to have <literal>SELECT</literal> privilege on
-   any table or column used in the query.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-&common;
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">with_query</replaceable></term>
-    <listitem>
-     <para>
-      The <literal>WITH</literal> clause allows you to specify one or more
-      subqueries that can be referenced by name in the <command>INSERT</>
-      query. See <xref linkend="queries-with"> and <xref linkend="sql-select">
-      for details.
-     </para>
-     <para>
-      It is possible for the <replaceable class="parameter">query</replaceable>
-      (<command>SELECT</command> statement)
-      to also contain a <literal>WITH</literal> clause.  In such a case both
-      sets of <replaceable>with_query</replaceable> can be referenced within
-      the <replaceable class="parameter">query</replaceable>, but the
-      second one takes precedence since it is more closely nested.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">table</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">column</replaceable></term>
-    <listitem>
-     <para>
-      The name of a column in <replaceable class="PARAMETER">table</replaceable>.
-      The column name can be qualified with a subfield name or array
-      subscript, if needed.  (Inserting into only some fields of a
-      composite column leaves the other fields null.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DEFAULT VALUES</literal></term>
-    <listitem>
-     <para>
-      All columns will be filled with their default values.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">expression</replaceable></term>
-    <listitem>
-     <para>
-      An expression or value to assign to the corresponding <replaceable
-      class="PARAMETER">column</replaceable>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DEFAULT</literal></term>
-    <listitem>
-     <para>
-      The corresponding <replaceable>column</replaceable> will be filled with
-      its default value.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">query</replaceable></term>
-    <listitem>
-     <para>
-      A query (<command>SELECT</command> statement) that supplies the
-      rows to be inserted.  Refer to the
-      <xref linkend="sql-select">
-      statement for a description of the syntax.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">output_expression</replaceable></term>
-    <listitem>
-     <para>
-      An expression to be computed and returned by the <command>INSERT</>
-      command after each row is inserted.  The expression can use any
-      column names of the <replaceable class="PARAMETER">table</replaceable>.
-      Write <literal>*</> to return all columns of the inserted row(s).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">output_name</replaceable></term>
-    <listitem>
-     <para>
-      A name to use for a returned column.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Outputs</title>
-&common;
-  <para>
-   On successful completion, an <command>INSERT</> command returns a command
-   tag of the form
-<screen>
-INSERT <replaceable>oid</replaceable> <replaceable class="parameter">count</replaceable>
-</screen>
-   The <replaceable class="parameter">count</replaceable> is the number
-   of rows inserted.  If <replaceable class="parameter">count</replaceable>
-   is exactly one, and the target table has OIDs, then
-   <replaceable class="parameter">oid</replaceable> is the
-   <acronym>OID</acronym> assigned to the inserted row.  Otherwise
-   <replaceable class="parameter">oid</replaceable> is zero.
-  </para>
-
-  <para>
-   If the <command>INSERT</> command contains a <literal>RETURNING</>
-   clause, the result will be similar to that of a <command>SELECT</>
-   statement containing the columns and values defined in the
-   <literal>RETURNING</> list, computed over the row(s) inserted by the
-   command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-&common;
-  <para>
-   Insert a single row into table <literal>films</literal>:
-
-<programlisting>
-INSERT INTO films VALUES
-    ('UA502', 'Bananas', 105, '1971-07-13', 'Comedy', '82 minutes');
-</programlisting>
-  </para>
-
-  <para>
-   In this example, the <literal>len</literal> column is
-   omitted and therefore it will have the default value:
-
-<programlisting>
-INSERT INTO films (code, title, did, date_prod, kind)
-    VALUES ('T_601', 'Yojimbo', 106, '1961-06-16', 'Drama');
-</programlisting>
-  </para>
-
-  <para>
-   This example uses the <literal>DEFAULT</literal> clause for
-   the date columns rather than specifying a value:
-
-<programlisting>
-INSERT INTO films VALUES
-    ('UA502', 'Bananas', 105, DEFAULT, 'Comedy', '82 minutes');
-INSERT INTO films (code, title, did, date_prod, kind)
-    VALUES ('T_601', 'Yojimbo', 106, DEFAULT, 'Drama');
-</programlisting>
-  </para>
-
-  <para>
-   To insert a row consisting entirely of default values:
-
-<programlisting>
-INSERT INTO films DEFAULT VALUES;
-</programlisting>
-  </para>
-
-  <para>
-   To insert multiple rows using the multirow <command>VALUES</> syntax:
-
-<programlisting>
-INSERT INTO films (code, title, did, date_prod, kind) VALUES
-    ('B6717', 'Tampopo', 110, '1985-02-10', 'Comedy'),
-    ('HG120', 'The Dinner Game', 140, DEFAULT, 'Comedy');
-</programlisting>
-  </para>
-
-  <para>
-   This example inserts some rows into table
-   <literal>films</literal> from a table <literal>tmp_films</literal>
-   with the same column layout as <literal>films</literal>:
-
-<programlisting>
-INSERT INTO films SELECT * FROM tmp_films WHERE date_prod &lt; '2004-05-07';
-</programlisting>
-  </para>
-
-  <para>
-   This example inserts into array columns:
-
-<programlisting>
--- Create an empty 3x3 gameboard for noughts-and-crosses
-INSERT INTO tictactoe (game, board[1:3][1:3])
-    VALUES (1, '{{" "," "," "},{" "," "," "},{" "," "," "}}');
--- The subscripts in the above example aren't really needed
-INSERT INTO tictactoe (game, board)
-    VALUES (2, '{{X," "," "},{" ",O," "},{" ",X," "}}');
-</programlisting>
-  </para>
-
-  <para>
-   Insert a single row into table <literal>distributors</literal>, returning
-   the sequence number generated by the <literal>DEFAULT</literal> clause:
-
-<programlisting>
-INSERT INTO distributors (did, dname) VALUES (DEFAULT, 'XYZ Widgets')
-   RETURNING did;
-</programlisting>
-  </para>
-
-  <para>
-   Increment the sales count of the salesperson who manages the
-   account for Acme Corporation, and record the whole updated row
-   along with current time in a log table:
-<programlisting>
-WITH upd AS (
-  UPDATE employees SET sales_count = sales_count + 1 WHERE id =
-    (SELECT sales_person FROM accounts WHERE name = 'Acme Corporation')
-    RETURNING *
-)
-INSERT INTO employees_log SELECT *, current_timestamp FROM upd;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>INSERT</> conforms to the <acronym>SQL</acronym> standard, except
-   that the <literal>RETURNING</> clause is a <productname>PostgreSQL</productname>
-   extension, as is the ability to use <literal>WITH</> with <command>INSERT</>.
-   Also, the case in which a column name list is omitted, but not all the columns
-   are filled from the <command>VALUES</> clause or query, is disallowed by the standard.
-  </para>
-
-  <para>
-   Possible limitations of the <replaceable
-   class="PARAMETER">query</replaceable> clause are documented under
-   <xref linkend="sql-select">.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/listen.sgmlin b/doc-xc/src/sgml/ref/listen.sgmlin
deleted file mode 100644
index 24802b26f6..0000000000
--- a/doc-xc/src/sgml/ref/listen.sgmlin
+++ /dev/null
@@ -1,154 +0,0 @@
-<!--
-doc/src/sgml/ref/listen.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-LISTEN">
- <refmeta>
-  <refentrytitle>LISTEN</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>LISTEN</refname>
-  <refpurpose>listen for a notification</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-listen">
-  <primary>LISTEN</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-LISTEN <replaceable class="PARAMETER">channel</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>LISTEN</> statement has not been supported
-   in <productname>Postgres-XC</> yet.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   The <command>LISTEN</> statement is not yet supported
-   in <productname>Postgres-XL</>.
-  </para>
-<!## end>
-
-<!## PG>
-  <para>
-   <command>LISTEN</command> registers the current session as a
-   listener on the notification channel named <replaceable
-   class="PARAMETER">channel</replaceable>.
-   If the current session is already registered as a listener for
-   this notification channel, nothing is done.
-  </para>
-
-  <para>
-   Whenever the command <command>NOTIFY <replaceable
-   class="PARAMETER">channel</replaceable></command> is invoked, either
-   by this session or another one connected to the same database, all
-   the sessions currently listening on that notification channel are
-   notified, and each will in turn notify its connected client
-   application.
-  </para>
-
-  <para>
-   A session can be unregistered for a given notification channel with the
-   <command>UNLISTEN</command> command.  A session's listen
-   registrations are automatically cleared when the session ends.
-  </para>
-
-  <para>
-   The method a client application must use to detect notification events depends on
-   which <productname>PostgreSQL</productname> application programming interface it
-   uses.  With the <application>libpq</> library, the application issues
-   <command>LISTEN</command> as an ordinary SQL command, and then must
-   periodically call the function <function>PQnotifies</function> to find out
-   whether any notification events have been received.  Other interfaces such as
-   <application>libpgtcl</> provide higher-level methods for handling notify events; indeed,
-   with <application>libpgtcl</> the application programmer should not even issue
-   <command>LISTEN</command> or <command>UNLISTEN</command> directly.  See the
-   documentation for the interface you are using for more details.
-  </para>
-
-  <para>
-   <xref linkend="sql-notify">
-   contains a more extensive
-   discussion of the use of <command>LISTEN</command> and
-   <command>NOTIFY</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">channel</replaceable></term>
-    <listitem>
-     <para>
-      Name of a notification channel (any identifier).
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <command>LISTEN</command> takes effect at transaction commit.
-   If <command>LISTEN</command> or <command>UNLISTEN</command> is executed
-   within a transaction that later rolls back, the set of notification
-   channels being listened to is unchanged.
-  </para>
-  <para>
-   A transaction that has executed <command>LISTEN</command> cannot be
-   prepared for two-phase commit.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Configure and execute a listen/notify sequence from
-   <application>psql</application>:
-
-<programlisting>
-LISTEN virtual;
-NOTIFY virtual;
-Asynchronous notification "virtual" received from server process with PID 8448.
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>LISTEN</command> statement in the SQL
-   standard.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-notify"></member>
-   <member><xref linkend="sql-unlisten"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/load.sgmlin b/doc-xc/src/sgml/ref/load.sgmlin
deleted file mode 100644
index 881b95800a..0000000000
--- a/doc-xc/src/sgml/ref/load.sgmlin
+++ /dev/null
@@ -1,103 +0,0 @@
-<!--
-doc/src/sgml/ref/load.sgml
--->
-
-<refentry id="SQL-LOAD">
- <refmeta>
-  <refentrytitle>LOAD</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>LOAD</refname>
-  <refpurpose>load a shared library file</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-load">
-  <primary>LOAD</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-LOAD '<replaceable class="PARAMETER">filename</replaceable>'
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-load-description">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   This command loads a shared library file into the <productname>PostgreSQL</>
-   server's address space.  If the file has been loaded already,
-   the command does nothing.  Shared library files that contain C functions
-   are automatically loaded whenever one of their functions is called.
-   Therefore, an explicit <command>LOAD</> is usually only needed to
-   load a library that modifies the server's behavior through <quote>hooks</>
-   rather than providing a set of functions.
-  </para>
-
-  <para>
-   The file name is specified in the same way as for shared library
-   names in <xref linkend="sql-createfunction">; in particular, one
-   can rely on a search path and automatic addition of the system's standard
-   shared library file name extension.  See <xref linkend="xfunc-c"> for
-   more information on this topic.
-  </para>
-
-  <indexterm>
-   <primary><filename>$libdir/plugins</></primary>
-  </indexterm>
-
-  <para>
-   Non-superusers can only apply <command>LOAD</> to library files
-   located in <filename>$libdir/plugins/</> &mdash; the specified
-   <replaceable class="PARAMETER">filename</replaceable> must begin
-   with exactly that string.  (It is the database administrator's
-   responsibility to ensure that only <quote>safe</> libraries
-   are installed there.)
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   Please note that <command>LOAD</command> command loads library only
-   locally.  You should load library manually in each Datanode and
-   Coordinator (you can use psql directly to Datanodes for this
-   puupose), or <filename>edit postgresql.conf</filename> for all the
-   Datanodes and Coordinators.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Please note that <command>LOAD</command> command loads the library only
-   locally.  You should load library manually on each Datanode and
-   Coordinator (you can use psql directly to Datanodes for this
-   puupose), or <filename>edit postgresql.conf</filename> for all the
-   Datanodes and Coordinators.
-  </para>
-<!## end>
-
- </refsect1>
-
- <refsect1 id="sql-load-compat">
-  <title>Compatibility</title>
-&common;
-  <para>
-   <command>LOAD</command> is a <productname>PostgreSQL</productname>
-   extension.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <para>
-   <xref linkend="sql-createfunction">
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/lock.sgmlin b/doc-xc/src/sgml/ref/lock.sgmlin
deleted file mode 100644
index 2459df81e8..0000000000
--- a/doc-xc/src/sgml/ref/lock.sgmlin
+++ /dev/null
@@ -1,249 +0,0 @@
-<!--
-doc/src/sgml/ref/lock.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-LOCK">
- <refmeta>
-  <refentrytitle>LOCK</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>LOCK</refname>
-  <refpurpose>lock a table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-lock">
-  <primary>LOCK</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-LOCK [ TABLE ] [ ONLY ] <replaceable class="PARAMETER">name</replaceable> [, ...] [ IN <replaceable class="PARAMETER">lockmode</replaceable> MODE ] [ NOWAIT ]
-
-<phrase>where <replaceable class="PARAMETER">lockmode</replaceable> is one of:</phrase>
-
-    ACCESS SHARE | ROW SHARE | ROW EXCLUSIVE | SHARE UPDATE EXCLUSIVE
-    | SHARE | SHARE ROW EXCLUSIVE | EXCLUSIVE | ACCESS EXCLUSIVE
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>LOCK TABLE</command> obtains a table-level lock, waiting
-   if necessary for any conflicting locks to be released.  If
-   <literal>NOWAIT</literal> is specified, <command>LOCK
-   TABLE</command> does not wait to acquire the desired lock: if it
-   cannot be acquired immediately, the command is aborted and an
-   error is emitted.  Once obtained, the lock is held for the
-   remainder of the current transaction.  (There is no <command>UNLOCK
-   TABLE</command> command; locks are always released at transaction
-   end.)
-  </para>
-
-  <para>
-   When acquiring locks automatically for commands that reference
-   tables, <productname>PostgreSQL</productname> always uses the least
-   restrictive lock mode possible. <command>LOCK TABLE</command>
-   provides for cases when you might need more restrictive locking.
-   For example, suppose an application runs a transaction at the
-   Read Committed isolation level and needs to ensure that data in a
-   table remains stable for the duration of the transaction. To
-   achieve this you could obtain <literal>SHARE</> lock mode over the
-   table before querying. This will prevent concurrent data changes
-   and ensure subsequent reads of the table see a stable view of
-   committed data, because <literal>SHARE</> lock mode conflicts with
-   the <literal>ROW EXCLUSIVE</> lock acquired by writers, and your
-   <command>LOCK TABLE <replaceable
-   class="PARAMETER">name</replaceable> IN SHARE MODE</command>
-   statement will wait until any concurrent holders of <literal>ROW
-   EXCLUSIVE</literal> mode locks commit or roll back. Thus, once you
-   obtain the lock, there are no uncommitted writes outstanding;
-   furthermore none can begin until you release the lock.
-  </para>
-
-  <para>
-   To achieve a similar effect when running a transaction at the
-   <literal>REPEATABLE READ</> or <literal>SERIALIZABLE</>
-   isolation level, you have to execute the <command>LOCK TABLE</> statement
-   before executing any <command>SELECT</> or data modification statement.
-   A <literal>REPEATABLE READ</> or <literal>SERIALIZABLE</> transaction's
-   view of data will be frozen when its first
-   <command>SELECT</> or data modification statement begins.  A <command>LOCK
-   TABLE</> later in the transaction will still prevent concurrent writes
-   &mdash; but it won't ensure that what the transaction reads corresponds to
-   the latest committed values.
-  </para>
-
-  <para>
-   If a transaction of this sort is going to change the data in the
-   table, then it should use <literal>SHARE ROW EXCLUSIVE</> lock mode
-   instead of <literal>SHARE</> mode.  This ensures that only one
-   transaction of this type runs at a time.  Without this, a deadlock
-   is possible: two transactions might both acquire <literal>SHARE</>
-   mode, and then be unable to also acquire <literal>ROW EXCLUSIVE</>
-   mode to actually perform their updates.  (Note that a transaction's
-   own locks never conflict, so a transaction can acquire <literal>ROW
-   EXCLUSIVE</> mode when it holds <literal>SHARE</> mode &mdash; but not
-   if anyone else holds <literal>SHARE</> mode.)  To avoid deadlocks,
-   make sure all transactions acquire locks on the same objects in the
-   same order, and if multiple lock modes are involved for a single
-   object, then transactions should always acquire the most
-   restrictive mode first.
-  </para>
-
-  <para>
-   More information about the lock modes and locking strategies can be
-   found in <xref linkend="explicit-locking">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of an existing table to
-      lock.  If <literal>ONLY</> is specified, only that table is
-      locked.  If <literal>ONLY</> is not specified, the table and all
-      its descendant tables (if any) are locked.
-     </para>
-
-     <para>
-      The command <literal>LOCK TABLE a, b;</> is equivalent to
-      <literal>LOCK TABLE a; LOCK TABLE b;</>. The tables are locked
-      one-by-one in the order specified in the <command>LOCK
-      TABLE</command> command.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">lockmode</replaceable></term>
-    <listitem>
-     <para>
-      The lock mode specifies which locks this lock conflicts with.
-      Lock modes are described in <xref linkend="explicit-locking">.
-     </para>
-
-     <para>
-      If no lock mode is specified, then <literal>ACCESS
-      EXCLUSIVE</literal>, the most restrictive mode, is used.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>NOWAIT</literal></term>
-    <listitem>
-     <para>
-      Specifies that <command>LOCK TABLE</command> should not wait for
-      any conflicting locks to be released: if the specified lock(s)
-      cannot be acquired immediately without waiting, the transaction
-      is aborted.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    <literal>LOCK TABLE ... IN ACCESS SHARE MODE</> requires <literal>SELECT</>
-    privileges on the target table.  All other forms of <command>LOCK</>
-    require table-level <literal>UPDATE</>, <literal>DELETE</>, or
-    <literal>TRUNCATE</> privileges.
-   </para>
-
-   <para>
-    <command>LOCK TABLE</> is useless outside a transaction block: the lock
-    would remain held only to the completion of the statement.  Therefore
-    <productname>PostgreSQL</productname> reports an error if <command>LOCK</>
-    is used outside a transaction block.
-    Use
-    <xref linkend="sql-begin"> and
-    <xref linkend="sql-commit">
-    (or <xref linkend="sql-rollback">)
-    to define a transaction block.
-   </para>
-
-  <para>
-   <command>LOCK TABLE</> only deals with table-level locks, and so
-   the mode names involving <literal>ROW</> are all misnomers.  These
-   mode names should generally be read as indicating the intention of
-   the user to acquire row-level locks within the locked table.  Also,
-   <literal>ROW EXCLUSIVE</> mode is a sharable table lock.  Keep in
-   mind that all the lock modes have identical semantics so far as
-   <command>LOCK TABLE</> is concerned, differing only in the rules
-   about which modes conflict with which. For information on how to
-   acquire an actual row-level lock, see <xref linkend="locking-rows">
-   and the <xref linkend="sql-for-update-share"
-   endterm="sql-for-update-share-title"> in the <command>SELECT</command>
-   reference documentation.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Obtain a <literal>SHARE</> lock on a primary key table when going to perform
-   inserts into a foreign key table:
-
-<programlisting>
-BEGIN WORK;
-LOCK TABLE films IN SHARE MODE;
-SELECT id FROM films
-    WHERE name = 'Star Wars: Episode I - The Phantom Menace';
--- Do ROLLBACK if record was not returned
-INSERT INTO films_user_comments VALUES
-    (_id_, 'GREAT! I was waiting for it for so long!');
-COMMIT WORK;
-</programlisting>
-  </para>
-
-  <para>
-   Take a <literal>SHARE ROW EXCLUSIVE</> lock on a primary key table when going to perform
-   a delete operation:
-
-<programlisting>
-BEGIN WORK;
-LOCK TABLE films IN SHARE ROW EXCLUSIVE MODE;
-DELETE FROM films_user_comments WHERE id IN
-    (SELECT id FROM films WHERE rating &lt; 5);
-DELETE FROM films WHERE rating &lt; 5;
-COMMIT WORK;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>LOCK TABLE</command> in the SQL standard,
-   which instead uses <command>SET TRANSACTION</command> to specify
-   concurrency levels on transactions.  <productname>PostgreSQL</productname> supports that too;
-   see <xref linkend="SQL-SET-TRANSACTION"> for details.
-  </para>
-
-  <para>
-   Except for <literal>ACCESS SHARE</>, <literal>ACCESS EXCLUSIVE</>,
-   and <literal>SHARE UPDATE EXCLUSIVE</> lock modes, the
-   <productname>PostgreSQL</productname> lock modes and the
-   <command>LOCK TABLE</command> syntax are compatible with those
-   present in <productname>Oracle</productname>.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/move.sgmlin b/doc-xc/src/sgml/ref/move.sgmlin
deleted file mode 100644
index 96dd30669c..0000000000
--- a/doc-xc/src/sgml/ref/move.sgmlin
+++ /dev/null
@@ -1,126 +0,0 @@
-<!--
-doc/src/sgml/ref/move.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-MOVE">
- <refmeta>
-  <refentrytitle>MOVE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>MOVE</refname>
-  <refpurpose>position a cursor</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-move">
-  <primary>MOVE</primary>
- </indexterm>
-
- <indexterm zone="sql-move">
-  <primary>cursor</primary>
-  <secondary>MOVE</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<!-- Note the "direction" bit is also in ref/fetch.sgml -->
-<synopsis>
-MOVE [ <replaceable class="PARAMETER">direction</replaceable> [ FROM | IN ] ] <replaceable class="PARAMETER">cursor_name</replaceable>
-
-<phrase>where <replaceable class="PARAMETER">direction</replaceable> can be empty or one of:</phrase>
-
-    NEXT
-    PRIOR
-    FIRST
-    LAST
-    ABSOLUTE <replaceable class="PARAMETER">count</replaceable>
-    RELATIVE <replaceable class="PARAMETER">count</replaceable>
-    <replaceable class="PARAMETER">count</replaceable>
-    ALL
-    FORWARD
-    FORWARD <replaceable class="PARAMETER">count</replaceable>
-    FORWARD ALL
-    BACKWARD
-    BACKWARD <replaceable class="PARAMETER">count</replaceable>
-    BACKWARD ALL
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>MOVE</command> repositions a cursor without retrieving any data.
-   <command>MOVE</command> works exactly like the <command>FETCH</command>
-   command, except it only positions the cursor and does not return rows.
-  </para>
-
-  <para>
-   The parameters for the <command>MOVE</command> command are identical to
-   those of the <command>FETCH</command> command; refer to
-   <xref linkend="sql-fetch">
-   for details on syntax and usage.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Outputs</title>
-
-  <para>
-   On successful completion, a <command>MOVE</> command returns a command
-   tag of the form
-<screen>
-MOVE <replaceable class="parameter">count</replaceable>
-</screen>
-   The <replaceable class="parameter">count</replaceable> is the number
-   of rows that a <command>FETCH</command> command with the same parameters
-   would have returned (possibly zero).
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-<programlisting>
-BEGIN WORK;
-DECLARE liahona CURSOR FOR SELECT * FROM films;
-
--- Skip the first 5 rows:
-MOVE FORWARD 5 IN liahona;
-MOVE 5
-
--- Fetch the 6th row from the cursor liahona:
-FETCH 1 FROM liahona;
- code  | title  | did | date_prod  |  kind  |  len
--------+--------+-----+------------+--------+-------
- P_303 | 48 Hrs | 103 | 1982-10-22 | Action | 01:37
-(1 row)
-
--- Close the cursor liahona and end the transaction:
-CLOSE liahona;
-COMMIT WORK;
-</programlisting>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>MOVE</command> statement in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-close"></member>
-   <member><xref linkend="sql-declare"></member>
-   <member><xref linkend="sql-fetch"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/notify.sgmlin b/doc-xc/src/sgml/ref/notify.sgmlin
deleted file mode 100644
index 700690e0e3..0000000000
--- a/doc-xc/src/sgml/ref/notify.sgmlin
+++ /dev/null
@@ -1,247 +0,0 @@
-<!--
-doc/src/sgml/ref/notify.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-NOTIFY">
- <refmeta>
-  <refentrytitle>NOTIFY</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>NOTIFY</refname>
-  <refpurpose>generate a notification</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-notify">
-  <primary>NOTIFY</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-NOTIFY <replaceable class="PARAMETER">channel</replaceable> [ , <replaceable class="PARAMETER">payload</replaceable> ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>NOTIFY</> statement has not been supported
-   in <productname>Postgres-XC</> yet.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>The NOTIFY</> statement is not yet supported
-   in <productname>Postgres-XL</>.
-  </para>
-<!## end>
-
-<!## PG>
-
-  <para>
-   The <command>NOTIFY</command> command sends a notification event together
-   with an optional <quote>payload</> string to each client application that
-   has previously executed
-   <command>LISTEN <replaceable class="parameter">channel</></command>
-   for the specified channel name in the current database.
-  </para>
-
-  <para>
-   <command>NOTIFY</command> provides a simple
-   interprocess communication mechanism for a collection of processes
-   accessing the same <productname>PostgreSQL</productname> database.
-   A payload string can be sent along with the notification, and
-   higher-level mechanisms for passing structured data can be built by using
-   tables in the database to pass additional data from notifier to listener(s).
-  </para>
-
-  <para>
-   The information passed to the client for a notification event includes the
-   notification channel
-   name, the notifying session's server process <acronym>PID</>, and the
-   payload string, which is an empty string if it has not been specified.
-  </para>
-
-  <para>
-   It is up to the database designer to define the channel names that will
-   be used in a given database and what each one means.
-   Commonly, the channel name is the same as the name of some table in
-   the database, and the notify event essentially means, <quote>I changed this table,
-   take a look at it to see what's new</quote>.  But no such association is enforced by
-   the <command>NOTIFY</command> and <command>LISTEN</command> commands.  For
-   example, a database designer could use several different channel names
-   to signal different sorts of changes to a single table.  Alternatively,
-   the payload string could be used to differentiate various cases.
-  </para>
-
-  <para>
-   When <command>NOTIFY</command> is used to signal the occurrence of changes
-   to a particular table, a useful programming technique is to put the
-   <command>NOTIFY</command> in a rule that is triggered by table updates.
-   In this way, notification happens automatically when the table is changed,
-   and the application programmer cannot accidentally forget to do it.
-  </para>
-
-  <para>
-   <command>NOTIFY</command> interacts with SQL transactions in some important
-   ways.  Firstly, if a <command>NOTIFY</command> is executed inside a
-   transaction, the notify events are not delivered until and unless the
-   transaction is committed.  This is appropriate, since if the transaction
-   is aborted, all the commands within it have had no
-   effect, including <command>NOTIFY</command>.  But it can be disconcerting if one
-   is expecting the notification events to be delivered immediately.  Secondly, if
-   a listening session receives a notification signal while it is within a transaction,
-   the notification event will not be delivered to its connected client until just
-   after the transaction is completed (either committed or aborted).  Again, the
-   reasoning is that if a notification were delivered within a transaction that was
-   later aborted, one would want the notification to be undone somehow &mdash;
-   but
-   the server cannot <quote>take back</quote> a notification once it has sent it to the client.
-   So notification events are only delivered between transactions.  The upshot of this
-   is that applications using <command>NOTIFY</command> for real-time signaling
-   should try to keep their transactions short.
-  </para>
-
-  <para>
-   If the same channel name is signaled multiple times from the same
-   transaction with identical payload strings, the
-   database server can decide to deliver a single notification only.
-   On the other hand, notifications with distinct payload strings will
-   always be delivered as distinct notifications. Similarly, notifications from
-   different transactions will never get folded into one notification.
-   Except for dropping later instances of duplicate notifications,
-   <command>NOTIFY</command> guarantees that notifications from the same
-   transaction get delivered in the order they were sent.  It is also
-   guaranteed that messages from different transactions are delivered in
-   the order in which the transactions committed.
-  </para>
-
-  <para>
-   It is common for a client that executes <command>NOTIFY</command>
-   to be listening on the same notification channel itself.  In that case
-   it will get back a notification event, just like all the other
-   listening sessions.  Depending on the application logic, this could
-   result in useless work, for example, reading a database table to
-   find the same updates that that session just wrote out.  It is
-   possible to avoid such extra work by noticing whether the notifying
-   session's server process <acronym>PID</> (supplied in the
-   notification event message) is the same as one's own session's
-   <acronym>PID</> (available from <application>libpq</>).  When they
-   are the same, the notification event is one's own work bouncing
-   back, and can be ignored.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">channel</replaceable></term>
-    <listitem>
-     <para>
-      Name of the notification channel to be signaled (any identifier).
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">payload</replaceable></term>
-    <listitem>
-     <para>
-      The <quote>payload</> string to be communicated along with the
-      notification.  This must be specified as a simple string literal.
-      In the default configuration it must be shorter than 8000 bytes.
-      (If binary data or large amounts of information need to be communicated,
-      it's best to put it in a database table and send the key of the record.)
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   There is a queue that holds notifications that have been sent but not
-   yet processed by all listening sessions.  If this queue becomes full,
-   transactions calling <command>NOTIFY</command> will fail at commit.
-   The queue is quite large (8GB in a standard installation) and should be
-   sufficiently sized for almost every use case. However, no cleanup can take
-   place if a session executes <command>LISTEN</command> and then enters a
-   transaction for a very long time. Once the queue is half full you will see
-   warnings in the log file pointing you to the session that is preventing
-   cleanup. In this case you should make sure that this session ends its
-   current transaction so that cleanup can proceed.
-  </para>
-  <para>
-   A transaction that has executed <command>NOTIFY</command> cannot be
-   prepared for two-phase commit.
-  </para>
-
-  <refsect2>
-   <title>pg_notify</title>
-
-   <indexterm>
-    <primary>pg_notify</primary>
-   </indexterm>
-
-   <para>
-    To send a notification you can also use the function
-    <literal><function>pg_notify</function>(<type>text</type>,
-    <type>text</type>)</literal>. The function takes the channel name as the
-    first argument and the payload as the second. The function is much easier
-    to use than the <command>NOTIFY</command> command if you need to work with
-    non-constant channel names and payloads.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Configure and execute a listen/notify sequence from
-   <application>psql</application>:
-
-<programlisting>
-LISTEN virtual;
-NOTIFY virtual;
-Asynchronous notification "virtual" received from server process with PID 8448.
-NOTIFY virtual, 'This is the payload';
-Asynchronous notification "virtual" with payload "This is the payload" received from server process with PID 8448.
-
-LISTEN foo;
-SELECT pg_notify('fo' || 'o', 'pay' || 'load');
-Asynchronous notification "foo" with payload "payload" received from server process with PID 14728.
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>NOTIFY</command> statement in the SQL
-   standard.
-  </para>
-<!## end>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-listen"></member>
-   <member><xref linkend="sql-unlisten"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pause_cluster.sgmlin b/doc-xc/src/sgml/ref/pause_cluster.sgmlin
deleted file mode 100644
index 6d0e31e705..0000000000
--- a/doc-xc/src/sgml/ref/pause_cluster.sgmlin
+++ /dev/null
@@ -1,70 +0,0 @@
-<!--
-doc/src/sgml/ref/pause_cluster.sgml
-PostgreSQL documentation
--->
-<!## XL>
-<refentry id="SQL-PAUSECLUSTER">
- <refmeta>
-  <refentrytitle>PAUSE CLUSTER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>PAUSE CLUSTER</refname>
-  <refpurpose>pause the <productname>Postgres-XL</productname> cluster</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-pausecluster">
-  <primary>PAUSE CLUSTER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-PAUSE CLUSTER
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xlonly;
-
-  <para>
-   <command>PAUSE CLUSTER </command> is a SQL command specific
-   to <productname>Postgres-XL</productname> that pauses 
-   cluster operation.
-  </para>
-  <para>
-   Pause blocks any new transactions from starting and waits until
-   existing transactions complete, then returns. Existing sessions 
-   are still connected to Coordinators, it is just that any new statements
-   will be held up and not be executed. 
-   </para>
-
-   <para>
-   The session that paused the cluster can perform tasks exclusively on the 
-   cluster. This is useful for maintenance tasks to resolve a problem, 
-   restart a Datanode, manually failover a Datanode, etc. Applications will
-   not receive error messages unless they themselves timeout, statement execution
-   will just be briefly suspended.
-   </para>
-    
-  <para>
-   Once the DBA has completed whatever tasks were needed, the command <xref linkend="sql-unpausecluster"> can be used.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>PAUSE CLUSTER</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XL specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
-
diff --git a/doc-xc/src/sgml/ref/pg_basebackup.sgmlin b/doc-xc/src/sgml/ref/pg_basebackup.sgmlin
deleted file mode 100644
index 47dce43b19..0000000000
--- a/doc-xc/src/sgml/ref/pg_basebackup.sgmlin
+++ /dev/null
@@ -1,437 +0,0 @@
-<!--
-doc/src/sgml/ref/pg_basebackup.sgml
-PostgreSQL documentation
--->
-
-<refentry id="app-pgbasebackup">
- <refmeta>
-  <refentrytitle>pg_basebackup</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_basebackup</refname>
-  <refpurpose>take a base backup of a <productname>PostgreSQL</productname> cluster</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-pgbasebackup">
-  <primary>pg_basebackup</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_basebackup</command>
-   <arg rep="repeat"><replaceable>option</></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>
-   Description
-  </title>
-  <para>
-   <application>pg_basebackup</application> is used to take base backups of
-   a running <productname>PostgreSQL</productname> database cluster. These
-   are taken without affecting other clients to the database, and can be used
-   both for point-in-time recovery (see <xref linkend="continuous-archiving">)
-   and as the starting point for a log shipping or streaming replication standby
-   servers (see <xref linkend="warm-standby">).
-  </para>
-
-  <para>
-   <application>pg_basebackup</application> makes a binary copy of the database
-   cluster files, while making sure the system is automatically put in and
-   out of backup mode automatically. Backups are always taken of the entire
-   database cluster, it is not possible to back up individual databases or
-   database objects. For individual database backups, a tool such as
-   <xref linkend="APP-PGDUMP"> must be used.
-  </para>
-
-  <para>
-   The backup is made over a regular <productname>PostgreSQL</productname>
-   connection, and uses the replication protocol. The connection must be
-   made with a user having <literal>REPLICATION</literal> permissions (see
-   <xref linkend="role-attributes">), and the user must be granted explicit
-   permissions in <filename>pg_hba.conf</filename>. The server must also
-   be configured with <xref linkend="guc-max-wal-senders"> set high enough
-   to leave at least one session available for the backup.
-  </para>
-
-  <para>
-   There can be multiple <command>pg_basebackup</command>s running at the same time, but it is
-   better from a performance point of view to take only one backup, and copy
-   the result.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Options</title>
-
-   <para>
-    The following command-line options control the location and format of the
-    output.
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-D <replaceable class="parameter">directory</replaceable></option></term>
-      <term><option>--pgdata=<replaceable class="parameter">directory</replaceable></option></term>
-      <listitem>
-       <para>
-        Directory to write the output to.
-       </para>
-       <para>
-        When the backup is in tar mode, and the directory is specified as
-        <literal>-</literal> (dash), the tar file will be written to
-        <literal>stdout</literal>.
-       </para>
-       <para>
-        This parameter is required.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-F <replaceable class="parameter">format</replaceable></option></term>
-      <term><option>--format=<replaceable class="parameter">format</replaceable></option></term>
-      <listitem>
-       <para>
-        Selects the format for the output. <replaceable>format</replaceable>
-        can be one of the following:
-
-        <variablelist>
-         <varlistentry>
-          <term><literal>p</literal></term>
-          <term><literal>plain</literal></term>
-          <listitem>
-           <para>
-            Write the output as plain files, with the same layout as the
-            current data directory and tablespaces. When the cluster has
-            no additional tablespaces, the whole database will be placed in
-            the target directory. If the cluster contains additional
-            tablespaces, the main data directory will be placed in the
-            target directory, but all other tablespaces will be placed
-            in the same absolute path as they have on the server.
-           </para>
-           <para>
-            This is the default format.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>t</literal></term>
-          <term><literal>tar</literal></term>
-          <listitem>
-           <para>
-            Write the output as tar files in the target directory. The main
-            data directory will be written to a file named
-            <filename>base.tar</filename>, and all other tablespaces will
-            be named after the tablespace OID.
-            </para>
-           <para>
-            If the value <literal>-</literal> (dash) is specified as
-            target directory, the tar contents will be written to
-            standard output, suitable for piping to for example
-            <productname>gzip</productname>. This is only possible if
-            the cluster has no additional tablespaces.
-           </para>
-           </listitem>
-         </varlistentry>
-        </variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-x</option></term>
-      <term><option>--xlog</option></term>
-      <listitem>
-       <para>
-        Includes the required transaction log files (WAL files) in the
-        backup. This will include all transaction logs generated during
-        the backup. If this option is specified, it is possible to start
-        a postmaster directly in the extracted directory without the need
-        to consult the log archive, thus making this a completely standalone
-        backup.
-       </para>
-       <note>
-        <para>
-         The transaction log files are collected at the end of the backup.
-         Therefore, it is necessary for the
-         <xref linkend="guc-wal-keep-segments"> parameter to be set high
-         enough that the log is not removed before the end of the backup.
-         If the log has been rotated when it's time to transfer it, the
-         backup will fail and be unusable.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-z</option></term>
-      <term><option>--gzip</option></term>
-      <listitem>
-       <para>
-        Enables gzip compression of tar file output, with the default
-        compression level. Compression is only available when using
-        the tar format.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-Z <replaceable class="parameter">level</replaceable></option></term>
-      <term><option>--compress=<replaceable class="parameter">level</replaceable></option></term>
-      <listitem>
-       <para>
-        Enables gzip compression of tar file output, and specifies the
-        compression level (1 through 9, 9 being best
-        compression). Compression is only available when using the tar
-        format.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-   <para>
-    The following command-line options control the generation of the
-    backup and the running of the program.
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-c <replaceable class="parameter">fast|spread</replaceable></option></term>
-      <term><option>--checkpoint=<replaceable class="parameter">fast|spread</replaceable></option></term>
-      <listitem>
-       <para>
-        Sets checkpoint mode to fast or spread (default).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l <replaceable class="parameter">label</replaceable></option></term>
-      <term><option>--label=<replaceable class="parameter">label</replaceable></option></term>
-      <listitem>
-       <para>
-        Sets the label for the backup. If none is specified, a default value of
-        <literal>pg_basebackup base backup</literal> will be used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-P</option></term>
-      <term><option>--progress</option></term>
-      <listitem>
-       <para>
-        Enables progress reporting. Turning this on will deliver an approximate
-        progress report during the backup. Since the database may change during
-        the backup, this is only an approximation and may not end at exactly
-        <literal>100%</literal>. In particular, when WAL log is included in the
-        backup, the total amount of data cannot be estimated in advance, and
-        in this case the progress report will only count towards the total
-        amount of data without WAL.
-       </para>
-       <para>
-        When this is enabled, the backup will start by enumerating the size of
-        the entire database, and then go back and send the actual contents.
-        This may make the backup take slightly longer, and in particular it
-        will take longer before the first data is sent.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-v</option></term>
-      <term><option>--verbose</option></term>
-      <listitem>
-       <para>
-        Enables verbose mode. Will output some extra steps during startup and
-        shutdown, as well as show the exact file name that is currently being
-        processed if progress reporting is also enabled.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    The following command-line options control the database connection parameters.
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></option></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the server is
-        running.  If the value begins with a slash, it is used as the
-        directory for the Unix domain socket. The default is taken
-        from the <envar>PGHOST</envar> environment variable, if set,
-        else a Unix domain socket connection is attempted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></option></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server is listening for connections.
-        Defaults to the <envar>PGPORT</envar> environment variable, if
-        set, or a compiled-in default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable>username</replaceable></option></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></option></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option></term>
-      <term><option>--password</option></term>
-      <listitem>
-       <para>
-        Force <application>pg_basebackup</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>pg_bsaebackup</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>pg_basebackup</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    Other, less commonly used, parameters are also available:
-
-    <variablelist>
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>pg_basebackup</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>pg_basebackup</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Environment</title>
-
-  <para>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-   uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   The backup will include all files in the data directory and tablespaces,
-   including the configuration files and any additional files placed in the
-   directory by third parties. Only regular files and directories are allowed
-   in the data directory, no symbolic links or special device files.
-  </para>
-
-  <para>
-   The way <productname>PostgreSQL</productname> manages tablespaces, the path
-   for all additional tablespaces must be identical whenever a backup is
-   restored. The main data directory, however, is relocatable to any location.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To create a base backup of the server at <literal>mydbserver</literal>
-   and store it in the local directory
-   <filename>/usr/local/pgsql/data</filename>:
-<screen>
-<prompt>$</prompt> <userinput>pg_basebackup -h mydbserver -D /usr/local/pgsql/data</userinput>
-</screen>
-  </para>
-
-  <para>
-   To create a backup of the local server with one compressed
-   tar file for each tablespace, and store it in the directory
-   <filename>backup</filename>, showing a progress report while running:
-<screen>
-<prompt>$</prompt> <userinput>pg_basebackup -D backup -Ft -z -P</userinput>
-</screen>
-  </para>
-
-  <para>
-   To create a backup of a single-tablespace local database and compress
-   this with <productname>bzip2</productname>:
-<screen>
-<prompt>$</prompt> <userinput>pg_basebackup -D - -Ft | bzip2 &gt; backup.tar.bz2</userinput>
-</screen>
-   (This command will fail if there are multiple tablespaces in the
-   database.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="APP-PGDUMP"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pg_config-ref.sgmlin b/doc-xc/src/sgml/ref/pg_config-ref.sgmlin
deleted file mode 100644
index 39c8a05d5e..0000000000
--- a/doc-xc/src/sgml/ref/pg_config-ref.sgmlin
+++ /dev/null
@@ -1,458 +0,0 @@
-<!-- doc/src/sgml/ref/pg_config-ref.sgml -->
-
-<refentry id="app-pgconfig">
- <refmeta>
-  <refentrytitle>pg_config</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_config</refname>
-<!## PG>
-  <refpurpose>retrieve information about the installed version of <productname>PostgreSQL</></refpurpose>
-<!## end>
-<!## XC>
-  <refpurpose>retrieve information about the installed version of <productname>Postgres-XC</></refpurpose>
-<!## end>
-<!## XL>
-  <refpurpose>retrieve information about the installed version of <productname>Postgres-XL</></refpurpose>
-<!## end>
- </refnamediv>
-
- <indexterm zone="app-pgconfig">
-  <primary>pg_config</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_config</command>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</>
-
-&common;
-
-  <para>
-   The <application>pg_config</> utility prints configuration parameters
-<!## PG>
-   of the currently installed version of <productname>PostgreSQL</>. It is
-<!## end>
-<!## XC>
-   of the currently installed version of <productname>Postgres-XC</>. It is
-<!## end>
-<!## XL>
-   of the currently installed version of <productname>Postgres-XL</>. It is
-<!## end>
-   intended, for example, to be used by software packages that want to interface
-<!## PG>
-   to <productname>PostgreSQL</> to facilitate finding the required header files
-<!## end>
-<!## XC>
-   to <productname>Postgres-XC</> to facilitate finding the required header files
-<!## end>
-<!## XL>
-   to <productname>Postgres-XL</> to facilitate finding the required header files
-<!## end>
-   and libraries.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-&common;
-  <para>
-   To use <application>pg_config</>, supply one or more of the following
-   options:
-   <variablelist>
-    <varlistentry>
-     <term><option>--bindir</option></>
-     <listitem>
-      <para>
-       Print the location of user executables. Use this, for example, to find
-       the <command>psql</> program. This is normally also the location
-       where the <filename>pg_config</> program resides.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--docdir</option></>
-     <listitem>
-      <para>
-       Print the location of documentation files.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--htmldir</option></>
-     <listitem>
-      <para>
-       Print the location of HTML documentation files.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--includedir</option></>
-     <listitem>
-      <para>
-       Print the location of C header files of the client interfaces.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--pkgincludedir</option></>
-     <listitem>
-      <para>
-       Print the location of other C header files.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--includedir-server</option></>
-     <listitem>
-      <para>
-       Print the location of C header files for server programming.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--libdir</option></>
-     <listitem>
-      <para>
-       Print the location of object code libraries.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--pkglibdir</option></>
-     <listitem>
-      <para>
-       Print the location of dynamically loadable modules, or where
-       the server would search for them.  (Other
-       architecture-dependent data files might also be installed in this
-       directory.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--localedir</option></>
-     <listitem>
-      <para>
-       Print the location of locale support files.  (This will be an empty
-       string if locale support was not configured when
-<!## PG>
-       <productname>PostgreSQL</> was built.)
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</> was built.)
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</> was built.)
-<!## end>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--mandir</option></>
-     <listitem>
-      <para>
-       Print the location of manual pages.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--sharedir</option></>
-     <listitem>
-      <para>
-       Print the location of architecture-independent support files.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--sysconfdir</option></>
-     <listitem>
-      <para>
-       Print the location of system-wide configuration files.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--pgxs</option></>
-     <listitem>
-      <para>
-       Print the location of extension makefiles.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--configure</option></>
-     <listitem>
-      <para>
-       Print the options that were given to the <filename>configure</>
-<!## PG>
-       script when <productname>PostgreSQL</> was configured for building.
-<!## end>
-<!## XC>
-       script when <productname>Postgres-XC</> was configured for building.
-<!## end>
-<!## XL>
-       script when <productname>Postgres-XL</> was configured for building.
-<!## end>
-       This can be used to reproduce the identical configuration, or
-       to find out with what options a binary package was built. (Note
-       however that binary packages often contain vendor-specific custom
-       patches.)  See also the examples below.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--cc</option></>
-     <listitem>
-      <para>
-       Print the value of the <varname>CC</varname> variable that was used for building
-<!## PG>
-       <productname>PostgreSQL</>.  This shows the C compiler used.
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</>.  This shows the C compiler used.
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</>.  This shows the C compiler used.
-<!## end>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--cppflags</option></>
-     <listitem>
-      <para>
-       Print the value of the <varname>CPPFLAGS</varname> variable that was used for building
-<!## PG>
-       <productname>PostgreSQL</>.  This shows C compiler switches needed
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</>.  This shows C compiler switches needed
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</>.  This shows C compiler switches needed
-<!## end>
-       at preprocessing time (typically, <literal>-I</> switches).
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--cflags</option></>
-     <listitem>
-      <para>
-       Print the value of the <varname>CFLAGS</varname> variable that was used for building
-<!## PG>
-       <productname>PostgreSQL</>.  This shows C compiler switches.
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</>.  This shows C compiler switches.
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</>.  This shows C compiler switches.
-<!## end>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--cflags_sl</option></>
-     <listitem>
-      <para>
-       Print the value of the <varname>CFLAGS_SL</varname> variable that was used for building
-<!## PG>
-       <productname>PostgreSQL</>.  This shows extra C compiler switches
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</>.  This shows extra C compiler switches
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</>.  This shows extra C compiler switches
-<!## end>
-       used for building shared libraries.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--ldflags</option></>
-     <listitem>
-      <para>
-       Print the value of the <varname>LDFLAGS</varname> variable that was used for building
-<!## PG>
-       <productname>PostgreSQL</>.  This shows linker switches.
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</>.  This shows linker switches.
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</>.  This shows linker switches.
-<!## end>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--ldflags_ex</option></>
-     <listitem>
-      <para>
-       Print the value of the <varname>LDFLAGS_EX</varname> variable that was used for building
-<!## PG>
-       <productname>PostgreSQL</>.  This shows linker switches
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</>.  This shows linker switches
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</>.  This shows linker switches
-<!## end>
-       used for building executables only.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--ldflags_sl</option></>
-     <listitem>
-      <para>
-       Print the value of the <varname>LDFLAGS_SL</varname> variable that was used for building
-<!## PG>
-       <productname>PostgreSQL</>.  This shows linker switches
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</>.  This shows linker switches
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</>.  This shows linker switches
-<!## end>
-       used for building shared libraries only.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--libs</option></>
-     <listitem>
-      <para>
-       Print the value of the <varname>LIBS</varname> variable that was used for building
-<!## PG>
-       <productname>PostgreSQL</>.  This normally contains <literal>-l</>
-       switches for external libraries linked into <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</>.  This normally contains <literal>-l</>
-       switches for external libraries linked into <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</>.  This normally contains <literal>-l</>
-       switches for external libraries linked into <productname>Postgres-XL</>.
-<!## end>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--version</option></>
-     <listitem>
-      <para>
-<!## PG>
-       Print the version of <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-       Print the version of <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-       Print the version of <productname>Postgres-XL</>.
-<!## end>
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-   If more than one option is given, the information is printed in that order,
-   one item per line.  If no options are given, all available information
-   is printed, with labels.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-&common;
-  <para>
-   The option <option>--includedir-server</option> was added in
-   <productname>PostgreSQL</> 7.2.  In prior releases, the server include files were
-   installed in the same location as the client headers, which could
-   be queried with the option <option>--includedir</option>.  To make your
-   package handle both cases, try the newer option first and test the
-   exit status to see whether it succeeded.
-  </para>
-
-  <para>
-   The options <option>--docdir</option>, <option>--pkgincludedir</option>,
-   <option>--localedir</option>, <option>--mandir</option>,
-   <option>--sharedir</option>, <option>--sysconfdir</option>,
-   <option>--cc</option>, <option>--cppflags</option>,
-   <option>--cflags</option>, <option>--cflags_sl</option>,
-   <option>--ldflags</option>, <option>--ldflags_sl</option>,
-   and <option>--libs</option> were added in <productname>PostgreSQL</> 8.1.
-   The option <option>--htmldir</option> was added in <productname>PostgreSQL</> 8.4.
-   The option <option>--ldflags_ex</option> was added in <productname>PostgreSQL</> 9.0.
-  </para>
-
-  <para>
-   In releases prior to <productname>PostgreSQL</> 7.1, before
-   <command>pg_config</command> came to be, a method for finding the
-   equivalent configuration information did not exist.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Example</title>
-&common;
-  <para>
-<!## PG>
-   To reproduce the build configuration of the current PostgreSQL
-<!## end>
-<!## XC>
-   To reproduce the build configuration of the current Postgres-XC
-<!## end>
-<!## XL>
-   To reproduce the build configuration of the current Postgres-XL
-<!## end>
-   installation, run the following command:
-<programlisting>
-eval ./configure `pg_config --configure`
-</programlisting>
-   The output of <literal>pg_config --configure</literal> contains
-   shell quotation marks so arguments with spaces are represented
-   correctly.  Therefore, using <literal>eval</literal> is required
-   for proper results.
-  </para>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pg_controldata.sgmlin b/doc-xc/src/sgml/ref/pg_controldata.sgmlin
deleted file mode 100644
index 9a507017f4..0000000000
--- a/doc-xc/src/sgml/ref/pg_controldata.sgmlin
+++ /dev/null
@@ -1,92 +0,0 @@
-<!--
-doc/src/sgml/ref/pg_controldata.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-PGCONTROLDATA">
- <refmeta>
-  <refentrytitle><application>pg_controldata</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_controldata</refname>
-<!## PG>
-  <refpurpose>display control information of a <productname>PostgreSQL</productname> database cluster</refpurpose>
-<!## end>
-<!## XC>
-  <refpurpose>display control information of a Coordinator or Datanode  database cluster of <productname>Postgres-XC</productname></refpurpose>
-<!## end>
-<!## XL>
-  <refpurpose>display control information of a Coordinator or Datanode  database cluster of <productname>Postgres-XL</productname></refpurpose>
-<!## end>
- </refnamediv>
-
- <indexterm zone="app-pgcontroldata">
-  <primary>pg_controldata</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_controldata</command>
-   <arg><replaceable class="parameter">option</replaceable></arg>
-   <arg><replaceable class="parameter">datadir</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-PGCONTROLDATA-1">
-  <title>Description</title>
-&common;
-
-  <para>
-   <command>pg_controldata</command> prints information initialized during
-   <command>initdb</>, such as the catalog version.
-   It also shows information about write-ahead logging and checkpoint
-   processing.  This information is cluster-wide, and not specific to any one
-   database.
-  </para>
-
-  <para>
-   This utility can only be run by the user who initialized the cluster because
-   it requires read access to the data directory.
-   You can specify the data directory on the command line, or use
-   the environment variable <envar>PGDATA</>.  This utility supports the options
-   <literal>-V</> and <literal>--version</>, which print the
-   <application>pg_controldata</application> version and exit.  It also
-   supports options <literal>-?</> and <literal>--help</>, which output the
-   supported arguments.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   To print information of each Datanode and Coordinator, you should
-   issue <command>pg_controldata</> against each of them.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   To print information of each Datanode and Coordinator, you should
-   issue <command>pg_controldata</> against each of them.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATA</envar></term>
-
-    <listitem>
-     <para>
-      Default data directory location
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pg_ctl-ref.sgml.jp b/doc-xc/src/sgml/ref/pg_ctl-ref.sgml.jp
deleted file mode 100644
index 02287d890d..0000000000
--- a/doc-xc/src/sgml/ref/pg_ctl-ref.sgml.jp
+++ /dev/null
@@ -1,596 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.51.2.1 2010/08/17 04:37:19 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="app-pg-ctl">
- <refmeta>
-  <refentrytitle><application>pg_ctl</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_ctl</refname>
-  <refpurpose>initialize, start, stop, or restart a <productname>PostgreSQL</productname> server</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-pg-ctl">
-  <primary>pg_ctl</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">init[db]</arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">start</arg>
-   <arg>-w</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-l <replaceable>filename</replaceable></arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-   <arg>-p <replaceable>path</replaceable></arg>
-   <arg>-c</arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">stop</arg>
-   <arg>-W</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-m
-     <group choice="plain">
-       <arg>s[mart]</arg>
-       <arg>f[ast]</arg>
-       <arg>i[mmediate]</arg>
-     </group>
-   </arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">restart</arg>
-   <arg>-w</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-c</arg>
-   <arg>-m
-     <group choice="plain">
-       <arg>s[mart]</arg>
-       <arg>f[ast]</arg>
-       <arg>i[mmediate]</arg>
-     </group>
-   </arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">reload</arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">status</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">kill</arg>
-   <arg><replaceable>signal_name</replaceable></arg>
-   <arg><replaceable>process_id</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">register</arg>
-   <arg>-N <replaceable>servicename</replaceable></arg>
-   <arg>-U <replaceable>username</replaceable></arg>
-   <arg>-P <replaceable>password</replaceable></arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-w</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">unregister</arg>
-   <arg>-N <replaceable>servicename</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1 id="app-pg-ctl-description">
-  <title>説明</title>
-  <para>
-   <application>pg_ctl</application> は
-   <productname>PostgreSQL</productname> database cluster を初期化し、
-   <productname>PostgreSQL</productname> バックエンドサーバの起動・停
-   止あるいは実行中のサーバの状態表示を行うツールである。サーバは手動
-   できどうすることもできるが、<application>pg_ctl</application> はロ
-   グ出力のリダイレクトや端末・プロセスグループからの適切な切り離しと
-   言った仕事をユーザに代わって実行してくれる。このツールはシャットダ
-   ウンを制御下で行なうための便利なオプションも提供してくれる。
-  </para>
-
-  <para>
-   The <option>init</option> or <option>initdb</option> mode creates a
-   new
-   <productname>PostgreSQL</productname> database cluster.  A database
-   cluster is a collection of databases that are managed by a single
-   server instance.  This mode invokes the <command>initdb</command>
-   command.  See <xref linkend="app-initdb"> for details.
-  </para>
-
-  <para>
-   In <option>start</option> mode, a new server is launched.  The
-   server is started in the background, and standard input is attached
-   to <filename>/dev/null</filename> (or <literal>nul</> on Windows).
-   On Unix-like systems, by default, the server's standard output and
-   standard error are send to <application>pg_ctl</application>'s
-   standard output (not standard error).  The standard output of
-   <application>pg_ctl</application> should then be redirected to a
-   file or piped to another process such as a log rotating program
-   like <application>rotatelogs</>; otherwise <command>postgres</command>
-   will write its output to the controlling terminal (from the
-   background) and will not leave the shell's process group.  On
-   Windows, by default the server's standard output and standard error
-   are sent to the terminal.  These default  behaviors can be changed
-   by using <option>-l</option> to append server output to a log file.
-  </para>
-
-  <para>
-   In <option>stop</option> mode, the server that is running in
-   the specified data directory is shut down.  Three different
-   shutdown methods can be selected with the <option>-m</option>
-   option: <quote>Smart</quote> mode waits for online backup mode
-   to finish and all the clients to disconnect.  This is the default.
-   If the server is in recovery, recovery and streaming replication
-   will be terminated once all clients have disconnected.
-   <quote>Fast</quote> mode does not wait for clients to disconnect and
-   will terminate an online backup in progress.  All active transactions are
-   rolled back and clients are forcibly disconnected, then the
-   server is shut down.  <quote>Immediate</quote> mode will abort
-   all server processes without a clean shutdown.  This will lead to 
-   a recovery run on restart.
-  </para>
-
-  <para>
-   <option>restart</option> mode effectively executes a stop followed
-   by a start.  This allows changing the <command>postgres</command>
-   command-line options.
-  </para>
-
-  <para>
-   <option>reload</option> mode simply sends the
-   <command>postgres</command> process a <systemitem>SIGHUP</>
-   signal, causing it to reread its configuration files
-   (<filename>postgresql.conf</filename>,
-   <filename>pg_hba.conf</filename>, etc.).  This allows changing of
-   configuration-file options that do not require a complete restart
-   to take effect.
-  </para>
-
-  <para>
-   <option>status</option> mode checks whether a server is running in
-   the specified data directory. If it is, the <acronym>PID</acronym>
-   and the command line options that were used to invoke it are
-   displayed.
-  </para>
-
-  <para>
-   <option>kill</option> mode allows you to send a signal to a specified
-    process.  This is particularly valuable for <productname>Microsoft Windows</>
-    which does not have a <application>kill</> command.  Use 
-    <literal>--help</> to see a list of supported signal names.
-  </para>
-
-  <para>
-   <option>register</option> mode allows you to register a system service
-   on <productname>Microsoft Windows</>.
-  </para>
-
-  <para>
-   <option>unregister</option> mode allows you to unregister a system service
-   on <productname>Microsoft Windows</>, previously registered with the
-   <option>register</option> command.
-  </para>
- </refsect1>
-
- <refsect1 id="app-pg-ctl-options">
-  <title>Options</title>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>-c</option></term>
-      <listitem>
-       <para>
-        Attempt to allow server crashes to produce core files, on platforms
-        where this available, by lifting any soft resource limit placed on 
-        them. 
-        This is useful in debugging or diagnosing problems by allowing a 
-        stack trace to be obtained from a failed server process.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-D <replaceable class="parameter">datadir</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the file system location of the database files.  If
-        this is omitted, the environment variable
-        <envar>PGDATA</envar> is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l <replaceable class="parameter">filename</replaceable></option></term>
-      <listitem>
-       <para>
-        Append the server log output to
-        <replaceable>filename</replaceable>.  If the file does not
-        exist, it is created.  The <systemitem>umask</> is set to 077, so access to
-        the log file from other users is disallowed by default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-m <replaceable class="parameter">mode</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the shutdown mode.  <replaceable>mode</replaceable>
-        can be <literal>smart</literal>, <literal>fast</literal>, or
-        <literal>immediate</literal>, or the first letter of one of
-        these three.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o <replaceable class="parameter">options</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies options to be passed directly to the
-        <command>postgres</command> command.
-       </para>
-       <para>
-        The options are usually surrounded by single or double
-        quotes to ensure that they are passed through as a group.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">path</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the location of the <filename>postgres</filename>
-        executable.  By default the <filename>postgres</filename> executable is taken from the same
-        directory as <command>pg_ctl</command>, or failing that, the hard-wired
-        installation directory.  It is not necessary to use this
-        option unless you are doing something unusual and get errors
-        that the <filename>postgres</filename> executable was not found.
-       </para>
-
-       <para>
-        In <literal>init</literal> mode, this option analogously
-        specifies the location of the <filename>initdb</filename>
-        executable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option></term>
-      <listitem>
-       <para>
-        Only print errors, no informational messages.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t</option></term>
-      <listitem>
-       <para>
-        The number of seconds to wait when waiting for start or shutdown
-        to complete.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</option></term>
-      <listitem>
-       <para>
-        Wait for the start or shutdown to complete.  The default wait time
-        is 60 seconds.  This is the default option for shutdowns. A successful 
-        shutdown is indicated by removal of the <acronym>PID</acronym> 
-        file. For starting up, a successful <command>psql -l</command> 
-        indicates success. <command>pg_ctl</command> will attempt to 
-        use the proper port for <application>psql</>. If the environment variable 
-        <envar>PGPORT</envar> exists, that is used. Otherwise, it will see if a port 
-        has been set in the <filename>postgresql.conf</filename> file. 
-        If neither of those is used, it will use the default port that 
-        <productname>PostgreSQL</productname> was compiled with 
-        (5432 by default). When waiting, <command>pg_ctl</command> will
-        return an accurate exit code based on the success of the startup 
-        or shutdown.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option></term>
-      <listitem>
-       <para>
-        Do not wait for start or shutdown to complete.  This is the
-        default for starts and restarts.
-       </para>
-      </listitem>
-     </varlistentry>
-   </variablelist>
-
-  <refsect2 id="app-pg-ctl-windows-options">
-   <title>Options for Windows</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><option>-N <replaceable class="parameter">servicename</replaceable></option></term>
-     <listitem>
-      <para>
-       Name of the system service to register. The name will be used
-       as both the service name and the display name.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-P <replaceable class="parameter">password</replaceable></option></term>
-     <listitem>
-      <para>
-       Password for the user to start the service.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-U <replaceable class="parameter">username</replaceable></option></term>
-     <listitem>
-      <para>
-       User name for the user to start the service. For domain users, use the
-       format <literal>DOMAIN\username</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect2>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATA</envar></term>
-
-    <listitem>
-     <para>
-      Default data directory location.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PGHOST</envar></term>
-
-    <listitem>
-     <para>
-      Default host name or Unix-domain socket location for <xref
-      linkend="app-psql"> (used by the <option>-w</option> option).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PGPORT</envar></term>
-
-    <listitem>
-     <para>
-      Default port number for <xref linkend="app-psql"> (used by the <option>-w</option> option).
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
-  <para>
-   For additional server variables, see <xref linkend="app-postgres">.
-   This utility, like most other <productname>PostgreSQL</> utilities,
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Files</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><filename>postmaster.pid</filename></term>
-
-    <listitem>
-     <para>
-      The existence of this file in the data directory is used to help
-      <application>pg_ctl</application> determine if the server is
-      currently running or not.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><filename>postmaster.opts</filename></term>
-
-    <listitem>
-     <para>If this file exists in the data directory,
-      <application>pg_ctl</application> (in <option>restart</option> mode) 
-      will pass the contents of the file as options to
-      <application>postgres</application>, unless overridden 
-      by the <option>-o</option> option. The contents of this file 
-      are also displayed in <option>status</option> mode.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><filename>postgresql.conf</filename></term>
-
-    <listitem>
-     <para>
-      This file, located in the data directory, is parsed to find the
-      proper port to use with <application>psql</application> when the
-      <option>-w</option> is given in <option>start</option> mode.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Waiting for complete start is not a well-defined operation and might
-   fail if access control is set up so that a local client cannot
-   connect without manual interaction (e.g., password authentication).  For
-   additional connection variables, see <xref linkend="libpq-envars">,
-   and for passwords, also see <xref linkend="libpq-pgpass">.
-  </para>
- </refsect1>
-
-
- <refsect1 id="R1-APP-PGCTL-2">
-  <title>Examples</title>
-
-  <refsect2 id="R2-APP-PGCTL-3">
-   <title>Starting the Server</title>
-
-   <para>
-    To start up a server:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl start</userinput>
-</screen>
-   </para>
-
-   <para>
-    An example of starting the server, blocking until the server has
-    come up is:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -w start</userinput>
-</screen>
-   </para>
-
-   <para>
-    For a server using port 5433, and
-    running without <function>fsync</function>, use:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -o "-F -p 5433" start</userinput>
-</screen>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PGCTL-4">
-   <title>Stopping the Server</title>
-   <para>
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl stop</userinput>
-</screen>
-    stops the server. Using the <option>-m</option> switch allows one
-    to control <emphasis>how</emphasis> the backend shuts down.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PGCTL-5">
-   <title>Restarting the Server</title>
-
-   <para>
-    Restarting the server is almost equivalent to stopping the
-    server and starting it again
-    except that <command>pg_ctl</command> saves and reuses the command line options that
-    were passed to the previously running instance.  To restart
-    the server in the simplest form, use:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl restart</userinput>
-</screen>
-   </para>
-
-   <para>
-    To restart server,
-    waiting for it to shut down and to come up:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -w restart</userinput>
-</screen>
-   </para>
-
-   <para>
-    To restart using port 5433 and disabling <function>fsync</> after restarting:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -o "-F -p 5433" restart</userinput>
-</screen>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PGCTL-6">
-   <title>Showing the Server Status</title>
-
-   <para>
-    Here is a sample status output from
-    <application>pg_ctl</application>:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl status</userinput>
-<computeroutput>
-pg_ctl: server is running (pid: 13718)
-Command line was:
-/usr/local/pgsql/bin/postgres '-D' '/usr/local/pgsql/data' '-p' '5433' '-B' '128'
-</computeroutput>
-</screen>
-    This is the command line that would be invoked in restart mode.
-   </para>
-  </refsect2>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-initdb"></member>
-   <member><xref linkend="app-postgres"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pg_ctl-ref.sgml.org b/doc-xc/src/sgml/ref/pg_ctl-ref.sgml.org
deleted file mode 100644
index 196f08fa5f..0000000000
--- a/doc-xc/src/sgml/ref/pg_ctl-ref.sgml.org
+++ /dev/null
@@ -1,597 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.51.2.1 2010/08/17 04:37:19 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="app-pg-ctl">
- <refmeta>
-  <refentrytitle><application>pg_ctl</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_ctl</refname>
-  <refpurpose>initialize, start, stop, or restart a <productname>PostgreSQL</productname> server</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-pg-ctl">
-  <primary>pg_ctl</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">init[db]</arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">start</arg>
-   <arg>-w</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-l <replaceable>filename</replaceable></arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-   <arg>-p <replaceable>path</replaceable></arg>
-   <arg>-c</arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">stop</arg>
-   <arg>-W</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-m
-     <group choice="plain">
-       <arg>s[mart]</arg>
-       <arg>f[ast]</arg>
-       <arg>i[mmediate]</arg>
-     </group>
-   </arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">restart</arg>
-   <arg>-w</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-c</arg>
-   <arg>-m
-     <group choice="plain">
-       <arg>s[mart]</arg>
-       <arg>f[ast]</arg>
-       <arg>i[mmediate]</arg>
-     </group>
-   </arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">reload</arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">status</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">kill</arg>
-   <arg><replaceable>signal_name</replaceable></arg>
-   <arg><replaceable>process_id</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">register</arg>
-   <arg>-N <replaceable>servicename</replaceable></arg>
-   <arg>-U <replaceable>username</replaceable></arg>
-   <arg>-P <replaceable>password</replaceable></arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-w</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">unregister</arg>
-   <arg>-N <replaceable>servicename</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1 id="app-pg-ctl-description">
-  <title>Description</title>
-  <para>
-   <application>pg_ctl</application> is a utility for initializing a
-   <productname>PostgreSQL</productname> database cluster, starting,
-   stopping, or restarting the <productname>PostgreSQL</productname>
-   backend server (<xref linkend="app-postgres">), or displaying the
-   status of a running server.  Although the server can be started
-   manually, <application>pg_ctl</application> encapsulates tasks such
-   as redirecting log output and properly detaching from the terminal
-   and process group. It also provides convenient options for
-   controlled shutdown.
-  </para>
-
-  <para>
-   The <option>init</option> or <option>initdb</option> mode creates a
-   new
-   <productname>PostgreSQL</productname> database cluster.  A database
-   cluster is a collection of databases that are managed by a single
-   server instance.  This mode invokes the <command>initdb</command>
-   command.  See <xref linkend="app-initdb"> for details.
-  </para>
-
-  <para>
-   In <option>start</option> mode, a new server is launched.  The
-   server is started in the background, and standard input is attached
-   to <filename>/dev/null</filename> (or <literal>nul</> on Windows).
-   On Unix-like systems, by default, the server's standard output and
-   standard error are send to <application>pg_ctl</application>'s
-   standard output (not standard error).  The standard output of
-   <application>pg_ctl</application> should then be redirected to a
-   file or piped to another process such as a log rotating program
-   like <application>rotatelogs</>; otherwise <command>postgres</command>
-   will write its output to the controlling terminal (from the
-   background) and will not leave the shell's process group.  On
-   Windows, by default the server's standard output and standard error
-   are sent to the terminal.  These default  behaviors can be changed
-   by using <option>-l</option> to append server output to a log file.
-  </para>
-
-  <para>
-   In <option>stop</option> mode, the server that is running in
-   the specified data directory is shut down.  Three different
-   shutdown methods can be selected with the <option>-m</option>
-   option: <quote>Smart</quote> mode waits for online backup mode
-   to finish and all the clients to disconnect.  This is the default.
-   If the server is in recovery, recovery and streaming replication
-   will be terminated once all clients have disconnected.
-   <quote>Fast</quote> mode does not wait for clients to disconnect and
-   will terminate an online backup in progress.  All active transactions are
-   rolled back and clients are forcibly disconnected, then the
-   server is shut down.  <quote>Immediate</quote> mode will abort
-   all server processes without a clean shutdown.  This will lead to 
-   a recovery run on restart.
-  </para>
-
-  <para>
-   <option>restart</option> mode effectively executes a stop followed
-   by a start.  This allows changing the <command>postgres</command>
-   command-line options.
-  </para>
-
-  <para>
-   <option>reload</option> mode simply sends the
-   <command>postgres</command> process a <systemitem>SIGHUP</>
-   signal, causing it to reread its configuration files
-   (<filename>postgresql.conf</filename>,
-   <filename>pg_hba.conf</filename>, etc.).  This allows changing of
-   configuration-file options that do not require a complete restart
-   to take effect.
-  </para>
-
-  <para>
-   <option>status</option> mode checks whether a server is running in
-   the specified data directory. If it is, the <acronym>PID</acronym>
-   and the command line options that were used to invoke it are
-   displayed.
-  </para>
-
-  <para>
-   <option>kill</option> mode allows you to send a signal to a specified
-    process.  This is particularly valuable for <productname>Microsoft Windows</>
-    which does not have a <application>kill</> command.  Use 
-    <literal>--help</> to see a list of supported signal names.
-  </para>
-
-  <para>
-   <option>register</option> mode allows you to register a system service
-   on <productname>Microsoft Windows</>.
-  </para>
-
-  <para>
-   <option>unregister</option> mode allows you to unregister a system service
-   on <productname>Microsoft Windows</>, previously registered with the
-   <option>register</option> command.
-  </para>
- </refsect1>
-
- <refsect1 id="app-pg-ctl-options">
-  <title>Options</title>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>-c</option></term>
-      <listitem>
-       <para>
-        Attempt to allow server crashes to produce core files, on platforms
-        where this available, by lifting any soft resource limit placed on 
-        them. 
-        This is useful in debugging or diagnosing problems by allowing a 
-        stack trace to be obtained from a failed server process.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-D <replaceable class="parameter">datadir</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the file system location of the database files.  If
-        this is omitted, the environment variable
-        <envar>PGDATA</envar> is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l <replaceable class="parameter">filename</replaceable></option></term>
-      <listitem>
-       <para>
-        Append the server log output to
-        <replaceable>filename</replaceable>.  If the file does not
-        exist, it is created.  The <systemitem>umask</> is set to 077, so access to
-        the log file from other users is disallowed by default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-m <replaceable class="parameter">mode</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the shutdown mode.  <replaceable>mode</replaceable>
-        can be <literal>smart</literal>, <literal>fast</literal>, or
-        <literal>immediate</literal>, or the first letter of one of
-        these three.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o <replaceable class="parameter">options</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies options to be passed directly to the
-        <command>postgres</command> command.
-       </para>
-       <para>
-        The options are usually surrounded by single or double
-        quotes to ensure that they are passed through as a group.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">path</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the location of the <filename>postgres</filename>
-        executable.  By default the <filename>postgres</filename> executable is taken from the same
-        directory as <command>pg_ctl</command>, or failing that, the hard-wired
-        installation directory.  It is not necessary to use this
-        option unless you are doing something unusual and get errors
-        that the <filename>postgres</filename> executable was not found.
-       </para>
-
-       <para>
-        In <literal>init</literal> mode, this option analogously
-        specifies the location of the <filename>initdb</filename>
-        executable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option></term>
-      <listitem>
-       <para>
-        Only print errors, no informational messages.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t</option></term>
-      <listitem>
-       <para>
-        The number of seconds to wait when waiting for start or shutdown
-        to complete.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</option></term>
-      <listitem>
-       <para>
-        Wait for the start or shutdown to complete.  The default wait time
-        is 60 seconds.  This is the default option for shutdowns. A successful 
-        shutdown is indicated by removal of the <acronym>PID</acronym> 
-        file. For starting up, a successful <command>psql -l</command> 
-        indicates success. <command>pg_ctl</command> will attempt to 
-        use the proper port for <application>psql</>. If the environment variable 
-        <envar>PGPORT</envar> exists, that is used. Otherwise, it will see if a port 
-        has been set in the <filename>postgresql.conf</filename> file. 
-        If neither of those is used, it will use the default port that 
-        <productname>PostgreSQL</productname> was compiled with 
-        (5432 by default). When waiting, <command>pg_ctl</command> will
-        return an accurate exit code based on the success of the startup 
-        or shutdown.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option></term>
-      <listitem>
-       <para>
-        Do not wait for start or shutdown to complete.  This is the
-        default for starts and restarts.
-       </para>
-      </listitem>
-     </varlistentry>
-   </variablelist>
-
-  <refsect2 id="app-pg-ctl-windows-options">
-   <title>Options for Windows</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><option>-N <replaceable class="parameter">servicename</replaceable></option></term>
-     <listitem>
-      <para>
-       Name of the system service to register. The name will be used
-       as both the service name and the display name.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-P <replaceable class="parameter">password</replaceable></option></term>
-     <listitem>
-      <para>
-       Password for the user to start the service.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-U <replaceable class="parameter">username</replaceable></option></term>
-     <listitem>
-      <para>
-       User name for the user to start the service. For domain users, use the
-       format <literal>DOMAIN\username</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect2>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATA</envar></term>
-
-    <listitem>
-     <para>
-      Default data directory location.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PGHOST</envar></term>
-
-    <listitem>
-     <para>
-      Default host name or Unix-domain socket location for <xref
-      linkend="app-psql"> (used by the <option>-w</option> option).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PGPORT</envar></term>
-
-    <listitem>
-     <para>
-      Default port number for <xref linkend="app-psql"> (used by the <option>-w</option> option).
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
-  <para>
-   For additional server variables, see <xref linkend="app-postgres">.
-   This utility, like most other <productname>PostgreSQL</> utilities,
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Files</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><filename>postmaster.pid</filename></term>
-
-    <listitem>
-     <para>
-      The existence of this file in the data directory is used to help
-      <application>pg_ctl</application> determine if the server is
-      currently running or not.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><filename>postmaster.opts</filename></term>
-
-    <listitem>
-     <para>If this file exists in the data directory,
-      <application>pg_ctl</application> (in <option>restart</option> mode) 
-      will pass the contents of the file as options to
-      <application>postgres</application>, unless overridden 
-      by the <option>-o</option> option. The contents of this file 
-      are also displayed in <option>status</option> mode.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><filename>postgresql.conf</filename></term>
-
-    <listitem>
-     <para>
-      This file, located in the data directory, is parsed to find the
-      proper port to use with <application>psql</application> when the
-      <option>-w</option> is given in <option>start</option> mode.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Waiting for complete start is not a well-defined operation and might
-   fail if access control is set up so that a local client cannot
-   connect without manual interaction (e.g., password authentication).  For
-   additional connection variables, see <xref linkend="libpq-envars">,
-   and for passwords, also see <xref linkend="libpq-pgpass">.
-  </para>
- </refsect1>
-
-
- <refsect1 id="R1-APP-PGCTL-2">
-  <title>Examples</title>
-
-  <refsect2 id="R2-APP-PGCTL-3">
-   <title>Starting the Server</title>
-
-   <para>
-    To start up a server:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl start</userinput>
-</screen>
-   </para>
-
-   <para>
-    An example of starting the server, blocking until the server has
-    come up is:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -w start</userinput>
-</screen>
-   </para>
-
-   <para>
-    For a server using port 5433, and
-    running without <function>fsync</function>, use:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -o "-F -p 5433" start</userinput>
-</screen>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PGCTL-4">
-   <title>Stopping the Server</title>
-   <para>
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl stop</userinput>
-</screen>
-    stops the server. Using the <option>-m</option> switch allows one
-    to control <emphasis>how</emphasis> the backend shuts down.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PGCTL-5">
-   <title>Restarting the Server</title>
-
-   <para>
-    Restarting the server is almost equivalent to stopping the
-    server and starting it again
-    except that <command>pg_ctl</command> saves and reuses the command line options that
-    were passed to the previously running instance.  To restart
-    the server in the simplest form, use:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl restart</userinput>
-</screen>
-   </para>
-
-   <para>
-    To restart server,
-    waiting for it to shut down and to come up:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -w restart</userinput>
-</screen>
-   </para>
-
-   <para>
-    To restart using port 5433 and disabling <function>fsync</> after restarting:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -o "-F -p 5433" restart</userinput>
-</screen>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PGCTL-6">
-   <title>Showing the Server Status</title>
-
-   <para>
-    Here is a sample status output from
-    <application>pg_ctl</application>:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl status</userinput>
-<computeroutput>
-pg_ctl: server is running (pid: 13718)
-Command line was:
-/usr/local/pgsql/bin/postgres '-D' '/usr/local/pgsql/data' '-p' '5433' '-B' '128'
-</computeroutput>
-</screen>
-    This is the command line that would be invoked in restart mode.
-   </para>
-  </refsect2>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-initdb"></member>
-   <member><xref linkend="app-postgres"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pg_ctl-ref.sgmlin b/doc-xc/src/sgml/ref/pg_ctl-ref.sgmlin
deleted file mode 100644
index 10f418199e..0000000000
--- a/doc-xc/src/sgml/ref/pg_ctl-ref.sgmlin
+++ /dev/null
@@ -1,663 +0,0 @@
-<!--
-doc/src/sgml/ref/pg_ctl-ref.sgml
-PostgreSQL documentation
--->
-
-<refentry id="app-pg-ctl">
- <refmeta>
-  <refentrytitle><application>pg_ctl</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_ctl</refname>
-  <refpurpose>initialize, start, stop, or control a <productname>PostgreSQL</productname> server</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-pg-ctl">
-  <primary>pg_ctl</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">init[db]</arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-o <replaceable>initdb-options</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">start</arg>
-   <arg>-w</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-l <replaceable>filename</replaceable></arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-   <arg>-p <replaceable>path</replaceable></arg>
-   <arg>-c</arg>
-<!## XC>
-   <arg>-Z <replaceable>nodeopt</replaceable></arg>
-<!## end>
-<!## XL>
-   <arg>-Z <replaceable>nodeopt</replaceable></arg>
-<!## end>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">stop</arg>
-   <arg>-W</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-m
-     <group choice="plain">
-       <arg>s[mart]</arg>
-       <arg>f[ast]</arg>
-       <arg>i[mmediate]</arg>
-     </group>
-   </arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">restart</arg>
-   <arg>-w</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-c</arg>
-   <arg>-m
-     <group choice="plain">
-       <arg>s[mart]</arg>
-       <arg>f[ast]</arg>
-       <arg>i[mmediate]</arg>
-     </group>
-   </arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-<!## XC>
-   <arg>-Z <replaceable>nodeopt</replaceable></arg>
-<!## end>
-<!## XL>
-   <arg>-Z <replaceable>nodeopt</replaceable></arg>
-<!## end>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">reload</arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">status</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">promote</arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">kill</arg>
-   <arg><replaceable>signal_name</replaceable></arg>
-   <arg><replaceable>process_id</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">register</arg>
-   <arg>-N <replaceable>servicename</replaceable></arg>
-   <arg>-U <replaceable>username</replaceable></arg>
-   <arg>-P <replaceable>password</replaceable></arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-S
-     <group choice="plain">
-       <arg>a[uto]</arg>
-       <arg>d[emand]</arg>
-     </group>
-   </arg>
-   <arg>-w</arg>
-   <arg>-t <replaceable>seconds</replaceable></arg>
-   <arg>-o <replaceable>options</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">unregister</arg>
-   <arg>-N <replaceable>servicename</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1 id="app-pg-ctl-description">
-  <title>Description</title>
-&common;
-  <para>
-   <application>pg_ctl</application> is a utility for initializing a
-   <productname>PostgreSQL</productname> database cluster, starting,
-   stopping, or restarting the <productname>PostgreSQL</productname>
-   database server (<xref linkend="app-postgres">), or displaying the
-   status of a running server.  Although the server can be started
-   manually, <application>pg_ctl</application> encapsulates tasks such
-   as redirecting log output and properly detaching from the terminal
-   and process group. It also provides convenient options for
-   controlled shutdown.
-  </para>
-
-  <para>
-   The <option>init</option> or <option>initdb</option> mode creates a new
-   <productname>PostgreSQL</productname> database cluster.  A database
-   cluster is a collection of databases that are managed by a single
-   server instance.  This mode invokes the <command>initdb</command>
-   command.  See <xref linkend="app-initdb"> for details.
-  </para>
-
-  <para>
-   In <option>start</option> mode, a new server is launched.  The
-   server is started in the background, and its standard input is attached
-   to <filename>/dev/null</filename> (or <literal>nul</> on Windows).
-   On Unix-like systems, by default, the server's standard output and
-   standard error are sent to <application>pg_ctl</application>'s
-   standard output (not standard error).  The standard output of
-   <application>pg_ctl</application> should then be redirected to a
-   file or piped to another process such as a log rotating program
-   like <application>rotatelogs</>; otherwise <command>postgres</command>
-   will write its output to the controlling terminal (from the
-   background) and will not leave the shell's process group.  On
-   Windows, by default the server's standard output and standard error
-   are sent to the terminal.  These default behaviors can be changed
-   by using <option>-l</option> to append the server's output to a log file.
-   Use of either <option>-l</option> or output redirection is recommended.
-  </para>
-
-  <para>
-   In <option>stop</option> mode, the server that is running in
-   the specified data directory is shut down.  Three different
-   shutdown methods can be selected with the <option>-m</option>
-   option.  <quote>Smart</quote> mode (the default) waits for all active
-   clients to disconnect and any online backup to finish.
-   If the server is in hot standby, recovery and streaming replication
-   will be terminated once all clients have disconnected.
-   <quote>Fast</quote> mode does not wait for clients to disconnect and
-   will terminate an online backup in progress.  All active transactions are
-   rolled back and clients are forcibly disconnected, then the
-   server is shut down.  <quote>Immediate</quote> mode will abort
-   all server processes immediately, without a clean shutdown.
-   This will lead to a crash-recovery run on the next restart.
-  </para>
-
-  <para>
-   <option>restart</option> mode effectively executes a stop followed
-   by a start.  This allows changing the <command>postgres</command>
-   command-line options.
-  </para>
-
-  <para>
-   <option>reload</option> mode simply sends the
-   <command>postgres</command> process a <systemitem>SIGHUP</>
-   signal, causing it to reread its configuration files
-   (<filename>postgresql.conf</filename>,
-   <filename>pg_hba.conf</filename>, etc.).  This allows changing of
-   configuration-file options that do not require a complete restart
-   to take effect.
-  </para>
-
-  <para>
-   <option>status</option> mode checks whether a server is running in
-   the specified data directory. If it is, the <acronym>PID</acronym>
-   and the command line options that were used to invoke it are
-   displayed.
-  </para>
-
-  <para>
-   In <option>promote</option> mode, the standby server that is
-   running in the specified data directory is commanded to exit
-   recovery and begin read-write operations.
-  </para>
-
-  <para>
-   <option>kill</option> mode allows you to send a signal to a specified
-    process.  This is particularly valuable for <productname>Microsoft Windows</>
-    which does not have a <application>kill</> command.  Use
-    <literal>--help</> to see a list of supported signal names.
-  </para>
-
-  <para>
-   <option>register</option> mode allows you to register a system service
-   on <productname>Microsoft Windows</>.  The <option>-S</option> option
-   allows selection of service start type, either <quote>auto</quote> (start
-   service automatically on system startup) or <quote>demand</quote> (start
-   service on demand).
-  </para>
-
-  <para>
-   <option>unregister</option> mode allows you to unregister a system service
-   on <productname>Microsoft Windows</>.  This undoes the effects of the
-   <option>register</option> command.
-  </para>
- </refsect1>
-
- <refsect1 id="app-pg-ctl-options">
-  <title>Options</title>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><option>-c</option></term>
-      <listitem>
-       <para>
-        Attempt to allow server crashes to produce core files, on platforms
-        where this is possible, by lifting any soft resource limit placed on
-        core files.
-        This is useful in debugging or diagnosing problems by allowing a
-        stack trace to be obtained from a failed server process.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-D <replaceable class="parameter">datadir</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the file system location of the database files.  If
-        this is omitted, the environment variable
-        <envar>PGDATA</envar> is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l <replaceable class="parameter">filename</replaceable></option></term>
-      <listitem>
-       <para>
-        Append the server log output to
-        <replaceable>filename</replaceable>.  If the file does not
-        exist, it is created.  The <systemitem>umask</> is set to 077,
-        so access to the log file is disallowed to other users by default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-m <replaceable class="parameter">mode</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the shutdown mode.  <replaceable>mode</replaceable>
-        can be <literal>smart</literal>, <literal>fast</literal>, or
-        <literal>immediate</literal>, or the first letter of one of
-        these three.  If this is omitted, <literal>smart</literal> is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o <replaceable class="parameter">options</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies options to be passed directly to the
-        <command>postgres</command> command.
-       </para>
-       <para>
-        The options should usually be surrounded by single or double
-        quotes to ensure that they are passed through as a group.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o <replaceable class="parameter">initdb-options</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies options to be passed directly to the
-        <command>initdb</command> command.
-       </para>
-       <para>
-        The options should usually be surrounded by single or double
-        quotes to ensure that they are passed through as a group.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">path</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the location of the <filename>postgres</filename>
-        executable.  By default the <filename>postgres</filename> executable is taken from the same
-        directory as <command>pg_ctl</command>, or failing that, the hard-wired
-        installation directory.  It is not necessary to use this
-        option unless you are doing something unusual and get errors
-        that the <filename>postgres</filename> executable was not found.
-       </para>
-
-       <para>
-        In <literal>init</literal> mode, this option analogously
-        specifies the location of the <filename>initdb</filename>
-        executable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-<!## XC>
-     <varlistentry>
-      <term><option>-Z <replaceable class="parameter">nodeopt</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies to run node as a Coordinator, as a Datanode or in restore mode.
-        <replaceable>nodeopt</replaceable> can be respectively
-        <literal>coordinator</literal>,  <literal>datanode</literal> or
-        <literal>restoremode</literal>.
-       </para>
-       <para>
-        With restore mode, you can import Postgres-XC's catalog data from other coordinator
-        or datanode
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-<!## XL>
-     <varlistentry>
-      <term><option>-Z <replaceable class="parameter">nodeopt</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies to run node as a Coordinator, as a Datanode or in restore mode.
-        <replaceable>nodeopt</replaceable> can be respectively
-        <literal>coordinator</literal>,  <literal>datanode</literal> or
-        <literal>restoremode</literal>.
-       </para>
-       <para>
-        With restore mode, you can import Postgres-XL's catalog data from other coordinator
-        or datanode
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-
-     <varlistentry>
-      <term><option>-s</option></term>
-      <listitem>
-       <para>
-        Print only errors, no informational messages.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t</option></term>
-      <listitem>
-       <para>
-        The maximum number of seconds to wait when waiting for startup or
-        shutdown to complete.  The default is 60 seconds.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</option></term>
-      <listitem>
-       <para>
-        Wait for the startup or shutdown to complete.
-        Waiting is the default option for shutdowns, but not startups.
-        When waiting for startup, <command>pg_ctl</command> repeatedly
-        attempts to connect to the server.
-        When waiting for shutdown, <command>pg_ctl</command> waits for
-        the server to remove its <acronym>PID</acronym> file.
-        <command>pg_ctl</command> returns an exit code based on the
-        success of the startup or shutdown.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option></term>
-      <listitem>
-       <para>
-        Do not wait for startup or shutdown to complete.  This is the
-        default for start and restart modes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-   </variablelist>
-
-<!## PG>
-<!-- NOTICE:
-     No Windows support yet
--->
-  <refsect2 id="app-pg-ctl-windows-options">
-   <title>Options for Windows</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><option>-N <replaceable class="parameter">servicename</replaceable></option></term>
-     <listitem>
-      <para>
-       Name of the system service to register. The name will be used
-       as both the service name and the display name.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-P <replaceable class="parameter">password</replaceable></option></term>
-     <listitem>
-      <para>
-       Password for the user to start the service.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-S <replaceable class="parameter">start-type</replaceable></option></term>
-     <listitem>
-      <para>
-       Start type of the system service to register.  start-type can
-       be <literal>auto</literal>, or <literal>demand</literal>, or
-       the first letter of one of these two. If this is omitted,
-       <literal>auto</literal> is used.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-U <replaceable class="parameter">username</replaceable></option></term>
-     <listitem>
-      <para>
-       User name for the user to start the service. For domain users, use the
-       format <literal>DOMAIN\username</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect2>
-<!## end>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATA</envar></term>
-
-    <listitem>
-     <para>
-      Default data directory location.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
-  <para>
-   <command>pg_ctl</command>, like most other <productname>PostgreSQL</>
-   utilities,
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-   For additional server variables, see <xref linkend="app-postgres">.
-  </para>
-
-<!## XC>
-  <para>
-   This command controls individual Coordinator or Datanode.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   This command controls individual Coordinator or Datanode.
-  </para>
-<!## end>
- </refsect1>
-
-
- <refsect1>
-  <title>Files</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><filename>postmaster.pid</filename></term>
-
-    <listitem>
-     <para>
-      The existence of this file in the data directory is used to help
-      <application>pg_ctl</application> determine if the server is
-      currently running.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><filename>postmaster.opts</filename></term>
-
-    <listitem>
-     <para>If this file exists in the data directory,
-      <application>pg_ctl</application> (in <option>restart</option> mode)
-      will pass the contents of the file as options to
-      <application>postgres</application>, unless overridden
-      by the <option>-o</option> option. The contents of this file
-      are also displayed in <option>status</option> mode.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </refsect1>
-
-
- <refsect1 id="R1-APP-PGCTL-2">
-  <title>Examples</title>
-
-  <refsect2 id="R2-APP-PGCTL-3">
-   <title>Starting the Server</title>
-
-   <para>
-    To start the server:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl start</userinput>
-</screen>
-   </para>
-
-   <para>
-    To start the server, waiting until the server is
-    accepting connections:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -w start</userinput>
-</screen>
-   </para>
-
-   <para>
-    To start the server using port 5433, and
-    running without <function>fsync</function>, use:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -o "-F -p 5433" start</userinput>
-</screen>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PGCTL-4">
-   <title>Stopping the Server</title>
-   <para>
-    To stop the server, use:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl stop</userinput>
-</screen>
-    The <option>-m</option> option allows control over
-    <emphasis>how</emphasis> the server shuts down:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl stop -m fast</userinput>
-</screen>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PGCTL-5">
-   <title>Restarting the Server</title>
-
-   <para>
-    Restarting the server is almost equivalent to stopping the
-    server and starting it again,
-    except that <command>pg_ctl</command> saves and reuses the command line options that
-    were passed to the previously running instance.  To restart
-    the server in the simplest form, use:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl restart</userinput>
-</screen>
-   </para>
-
-   <para>
-    To restart the server,
-    waiting for it to shut down and restart:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -w restart</userinput>
-</screen>
-   </para>
-
-   <para>
-    To restart using port 5433, disabling <function>fsync</> upon restart:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -o "-F -p 5433" restart</userinput>
-</screen>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PGCTL-6">
-   <title>Showing the Server Status</title>
-
-   <para>
-    Here is sample status output from
-    <application>pg_ctl</application>:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl status</userinput>
-<computeroutput>
-pg_ctl: server is running (PID: 13718)
-/usr/local/pgsql/bin/postgres "-D" "/usr/local/pgsql/data" "-p" "5433" "-B" "128"
-</computeroutput>
-</screen>
-    This is the command line that would be invoked in restart mode.
-   </para>
-  </refsect2>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-initdb"></member>
-   <member><xref linkend="app-postgres"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pg_dump.sgmlin b/doc-xc/src/sgml/ref/pg_dump.sgmlin
deleted file mode 100644
index 7ffe2ba114..0000000000
--- a/doc-xc/src/sgml/ref/pg_dump.sgmlin
+++ /dev/null
@@ -1,1108 +0,0 @@
-<!--
-doc/src/sgml/ref/pg_dump.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-PGDUMP">
- <refmeta>
-  <refentrytitle>pg_dump</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_dump</refname>
-
-  <refpurpose>
-   extract a <productname>PostgreSQL</productname> database into a script file or other archive file
-  </refpurpose>
- </refnamediv>
-
- <indexterm zone="app-pgdump">
-  <primary>pg_dump</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_dump</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-   <arg><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1 id="pg-dump-description">
-  <title>
-   Description
-  </title>
-
-&pgnotice;
-
-  <para>
-   <application>pg_dump</application> is a utility for backing up a
-   <productname>PostgreSQL</productname> database. It makes consistent
-   backups even if the database is being used concurrently.
-   <application>pg_dump</application> does not block other users
-   accessing the database (readers or writers).
-  </para>
-
-  <para>
-   Dumps can be output in script or archive file formats. Script
-   dumps are plain-text files containing the SQL commands required
-   to reconstruct the database to the state it was in at the time it was
-   saved. To restore from such a script, feed it to <xref
-   linkend="app-psql">. Script files
-   can be used to reconstruct the database even on other machines and
-   other architectures; with some modifications, even on other SQL
-   database products.
-  </para>
-
-  <para>
-   The alternative archive file formats must be used with
-   <xref linkend="app-pgrestore"> to rebuild the database.  They
-   allow <application>pg_restore</application> to be selective about
-   what is restored, or even to reorder the items prior to being
-   restored.
-   The archive file formats are designed to be portable across
-   architectures.
-  </para>
-
-  <para>
-   When used with one of the archive file formats and combined with
-   <application>pg_restore</application>,
-   <application>pg_dump</application> provides a flexible archival and
-   transfer mechanism. <application>pg_dump</application> can be used to
-   backup an entire database, then <application>pg_restore</application>
-   can be used to examine the archive and/or select which parts of the
-   database are to be restored. The most flexible output file format is
-   the <quote>custom</quote> format (<option>-Fc</option>). It allows
-   for selection and reordering of all archived items, and is compressed
-   by default.
-  </para>
-
-  <para>
-   While running <application>pg_dump</application>, one should examine the
-   output for any warnings (printed on standard error), especially in
-   light of the limitations listed below.
-  </para>
-
- </refsect1>
-
- <refsect1 id="pg-dump-options">
-  <title>Options</title>
-
-  <para>
-    The following command-line options control the content and
-    format of the output.
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">dbname</replaceable></term>
-      <listitem>
-       <para>
-        Specifies the name of the database to be dumped.  If this is
-        not specified, the environment variable
-        <envar>PGDATABASE</envar> is used.  If that is not set, the
-        user name specified for the connection is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-a</></term>
-      <term><option>--data-only</></term>
-      <listitem>
-       <para>
-        Dump only the data, not the schema (data definitions).
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the archive formats, you can specify the option when you
-        call <command>pg_restore</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-b</></term>
-      <term><option>--blobs</></term>
-      <listitem>
-       <para>
-        Include large objects in the dump.  This is the default behavior
-        except when <option>--schema</>, <option>--table</>, or
-        <option>--schema-only</> is specified, so the <option>-b</>
-        switch is only useful to add large objects to selective dumps.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-c</option></term>
-      <term><option>--clean</option></term>
-      <listitem>
-       <para>
-        Output commands to clean (drop)
-        database objects prior to outputting the commands for creating them.
-        (Restore might generate some harmless errors.)
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the archive formats, you can specify the option when you
-        call <command>pg_restore</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-C</></term>
-      <term><option>--create</></term>
-      <listitem>
-       <para>
-        Begin the output with a command to create the
-        database itself and reconnect to the created database.  (With a
-        script of this form, it doesn't matter which database you connect
-        to before running the script.)
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the archive formats, you can specify the option when you
-        call <command>pg_restore</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-E <replaceable class="parameter">encoding</replaceable></option></term>
-      <term><option>--encoding=<replaceable class="parameter">encoding</replaceable></option></term>
-      <listitem>
-       <para>
-        Create the dump in the specified character set encoding. By default,
-        the dump is created in the database encoding.  (Another way to get the
-        same result is to set the <envar>PGCLIENTENCODING</envar> environment
-        variable to the desired dump encoding.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-f <replaceable class="parameter">file</replaceable></option></term>
-      <term><option>--file=<replaceable class="parameter">file</replaceable></option></term>
-      <listitem>
-       <para>
-        Send output to the specified file. This parameter can be omitted for
-        file based output formats, in which case the standard output is used.
-        It must be given for the directory output format however, where it
-        specifies the target directory instead of a file. In this case the
-        directory is created by <command>pg_dump</command> and must not exist
-        before.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-F <replaceable class="parameter">format</replaceable></option></term>
-      <term><option>--format=<replaceable class="parameter">format</replaceable></option></term>
-      <listitem>
-       <para>
-        Selects the format of the output.
-        <replaceable>format</replaceable> can be one of the following:
-
-       <variablelist>
-        <varlistentry>
-         <term><literal>p</></term>
-         <term><literal>plain</></term>
-         <listitem>
-          <para>
-           Output a plain-text <acronym>SQL</acronym> script file (the default).
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term><literal>c</></term>
-         <term><literal>custom</></term>
-         <listitem>
-          <para>
-           Output a custom-format archive suitable for input into
-           <application>pg_restore</application>.
-           Together with the directory output format, this is the most flexible
-           output format in that it allows manual selection and reordering of
-           archived items during restore. This format is also compressed by
-           default.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term><literal>d</></term>
-         <term><literal>directory</></term>
-         <listitem>
-          <para>
-           Output a directory-format archive suitable for input into
-           <application>pg_restore</application>. This will create a directory
-           with one file for each table and blob being dumped, plus a
-           so-called Table of Contents file describing the dumped objects in a
-           machine-readable format that <application>pg_restore</application>
-           can read. A directory format archive can be manipulated with
-           standard Unix tools; for example, files in an uncompressed archive
-           can be compressed with the <application>gzip</application> tool.
-           This format is compressed by default.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term><literal>t</></term>
-         <term><literal>tar</></term>
-         <listitem>
-          <para>
-           Output a <command>tar</command>-format archive suitable for input
-           into <application>pg_restore</application>. The tar-format is
-           compatible with the directory-format; extracting a tar-format
-           archive produces a valid directory-format archive.
-           However, the tar-format does not support compression and has a
-           limit of 8 GB on the size of individual tables. Also, the relative
-           order of table data items cannot be changed during restore.
-          </para>
-         </listitem>
-        </varlistentry>
-
-       </variablelist>
-       </para>
-
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-i</></term>
-      <term><option>--ignore-version</></term>
-      <listitem>
-       <para>
-        A deprecated option that is now ignored.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-n <replaceable class="parameter">schema</replaceable></option></term>
-      <term><option>--schema=<replaceable class="parameter">schema</replaceable></option></term>
-      <listitem>
-       <para>
-        Dump only schemas matching <replaceable
-        class="parameter">schema</replaceable>; this selects both the
-        schema itself, and all its contained objects.  When this option is
-        not specified, all non-system schemas in the target database will be
-        dumped.  Multiple schemas can be
-        selected by writing multiple <option>-n</> switches.  Also, the
-        <replaceable class="parameter">schema</replaceable> parameter is
-        interpreted as a pattern according to the same rules used by
-        <application>psql</>'s <literal>\d</> commands (see <xref
-        linkend="APP-PSQL-patterns" endterm="APP-PSQL-patterns-title">),
-        so multiple schemas can also be selected by writing wildcard characters
-        in the pattern.  When using wildcards, be careful to quote the pattern
-        if needed to prevent the shell from expanding the wildcards;  see
-        <xref linkend="pg-dump-examples" endterm="pg-dump-examples-title">.
-       </para>
-
-       <note>
-        <para>
-         When <option>-n</> is specified, <application>pg_dump</application>
-         makes no attempt to dump any other database objects that the selected
-         schema(s) might depend upon. Therefore, there is no guarantee
-         that the results of a specific-schema dump can be successfully
-         restored by themselves into a clean database.
-        </para>
-       </note>
-
-       <note>
-        <para>
-         Non-schema objects such as blobs are not dumped when <option>-n</> is
-         specified.  You can add blobs back to the dump with the
-         <option>--blobs</> switch.
-        </para>
-       </note>
-
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-N <replaceable class="parameter">schema</replaceable></option></term>
-      <term><option>--exclude-schema=<replaceable class="parameter">schema</replaceable></option></term>
-      <listitem>
-       <para>
-        Do not dump any schemas matching the <replaceable
-        class="parameter">schema</replaceable> pattern.  The pattern is
-        interpreted according to the same rules as for <option>-n</>.
-        <option>-N</> can be given more than once to exclude schemas
-        matching any of several patterns.
-       </para>
-
-       <para>
-        When both <option>-n</> and <option>-N</> are given, the behavior
-        is to dump just the schemas that match at least one <option>-n</>
-        switch but no <option>-N</> switches.  If <option>-N</> appears
-        without <option>-n</>, then schemas matching <option>-N</> are
-        excluded from what is otherwise a normal dump.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o</></term>
-      <term><option>--oids</></term>
-      <listitem>
-       <para>
-        Dump object identifiers (<acronym>OID</acronym>s) as part of the
-        data for every table.  Use this option if your application references
-        the <acronym>OID</>
-        columns in some way (e.g., in a foreign key constraint).
-        Otherwise, this option should not be used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-O</></term>
-      <term><option>--no-owner</option></term>
-      <listitem>
-       <para>
-        Do not output commands to set
-        ownership of objects to match the original database.
-        By default, <application>pg_dump</application> issues
-        <command>ALTER OWNER</> or
-        <command>SET SESSION AUTHORIZATION</command>
-        statements to set ownership of created database objects.
-        These statements
-        will fail when the script is run unless it is started by a superuser
-        (or the same user that owns all of the objects in the script).
-        To make a script that can be restored by any user, but will give
-        that user ownership of all the objects, specify <option>-O</>.
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the archive formats, you can specify the option when you
-        call <command>pg_restore</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-R</option></term>
-      <term><option>--no-reconnect</option></term>
-      <listitem>
-       <para>
-        This option is obsolete but still accepted for backwards
-        compatibility.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option></term>
-      <term><option>--schema-only</option></term>
-      <listitem>
-       <para>
-        Dump only the object definitions (schema), not data.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-S <replaceable class="parameter">username</replaceable></option></term>
-      <term><option>--superuser=<replaceable class="parameter">username</replaceable></option></term>
-      <listitem>
-       <para>
-        Specify the superuser user name to use when disabling triggers.
-        This is only relevant if <option>--disable-triggers</> is used.
-        (Usually, it's better to leave this out, and instead start the
-        resulting script as superuser.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t <replaceable class="parameter">table</replaceable></option></term>
-      <term><option>--table=<replaceable class="parameter">table</replaceable></option></term>
-      <listitem>
-       <para>
-        Dump only tables (or views or sequences or foreign tables) matching
-        <replaceable class="parameter">table</replaceable>.  Multiple tables
-        can be selected by writing multiple <option>-t</> switches.  Also, the
-        <replaceable class="parameter">table</replaceable> parameter is
-        interpreted as a pattern according to the same rules used by
-        <application>psql</>'s <literal>\d</> commands (see <xref
-        linkend="APP-PSQL-patterns" endterm="APP-PSQL-patterns-title">),
-        so multiple tables can also be selected by writing wildcard characters
-        in the pattern.  When using wildcards, be careful to quote the pattern
-        if needed to prevent the shell from expanding the wildcards;  see
-        <xref linkend="pg-dump-examples" endterm="pg-dump-examples-title">.
-       </para>
-
-       <para>
-        The <option>-n</> and <option>-N</> switches have no effect when
-        <option>-t</> is used, because tables selected by <option>-t</> will
-        be dumped regardless of those switches, and non-table objects will not
-        be dumped.
-       </para>
-
-       <note>
-        <para>
-         When <option>-t</> is specified, <application>pg_dump</application>
-         makes no attempt to dump any other database objects that the selected
-         table(s) might depend upon. Therefore, there is no guarantee
-         that the results of a specific-table dump can be successfully
-         restored by themselves into a clean database.
-        </para>
-       </note>
-
-       <note>
-        <para>
-         The behavior of the <option>-t</> switch is not entirely upward
-         compatible with pre-8.2 <productname>PostgreSQL</productname>
-         versions.  Formerly, writing <literal>-t tab</> would dump all
-         tables named <literal>tab</>, but now it just dumps whichever one
-         is visible in your default search path.  To get the old behavior
-         you can write <literal>-t '*.tab'</>.  Also, you must write something
-         like <literal>-t sch.tab</> to select a table in a particular schema,
-         rather than the old locution of <literal>-n sch -t tab</>.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-T <replaceable class="parameter">table</replaceable></option></term>
-      <term><option>--exclude-table=<replaceable class="parameter">table</replaceable></option></term>
-      <listitem>
-       <para>
-        Do not dump any tables matching the <replaceable
-        class="parameter">table</replaceable> pattern.  The pattern is
-        interpreted according to the same rules as for <option>-t</>.
-        <option>-T</> can be given more than once to exclude tables
-        matching any of several patterns.
-       </para>
-
-       <para>
-        When both <option>-t</> and <option>-T</> are given, the behavior
-        is to dump just the tables that match at least one <option>-t</>
-        switch but no <option>-T</> switches.  If <option>-T</> appears
-        without <option>-t</>, then tables matching <option>-T</> are
-        excluded from what is otherwise a normal dump.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-v</></term>
-      <term><option>--verbose</></term>
-      <listitem>
-       <para>
-        Specifies verbose mode.  This will cause
-        <application>pg_dump</application> to output detailed object
-        comments and start/stop times to the dump file, and progress
-        messages to standard error.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>pg_dump</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-x</></term>
-      <term><option>--no-privileges</></term>
-      <term><option>--no-acl</></term>
-      <listitem>
-       <para>
-        Prevent dumping of access privileges (grant/revoke commands).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-Z <replaceable class="parameter">0..9</replaceable></option></term>
-      <term><option>--compress=<replaceable class="parameter">0..9</replaceable></option></term>
-      <listitem>
-       <para>
-        Specify the compression level to use.  Zero means no compression.
-        For the custom archive format, this specifies compression of
-        individual table-data segments, and the default is to compress
-        at a moderate level.
-        For plain text output, setting a nonzero compression level causes
-        the entire output file to be compressed, as though it had been
-        fed through <application>gzip</>; but the default is not to compress.
-        The tar archive format currently does not support compression at all.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--binary-upgrade</option></term>
-      <listitem>
-       <para>
-        This option is for use by in-place upgrade utilities.  Its use
-        for other purposes is not recommended or supported.  The
-        behavior of the option may change in future releases without
-        notice.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--column-inserts</option></term>
-      <term><option>--attribute-inserts</option></term>
-      <listitem>
-       <para>
-        Dump data as <command>INSERT</command> commands with explicit
-        column names (<literal>INSERT INTO
-        <replaceable>table</replaceable>
-        (<replaceable>column</replaceable>, ...) VALUES
-        ...</literal>).  This will make restoration very slow; it is mainly
-        useful for making dumps that can be loaded into
-        non-<productname>PostgreSQL</productname> databases.
-        However, since this option generates a separate command for each row,
-        an error in reloading a row causes only that row to be lost rather
-        than the entire table contents.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--disable-dollar-quoting</></term>
-      <listitem>
-       <para>
-        This option disables the use of dollar quoting for function bodies,
-        and forces them to be quoted using SQL standard string syntax.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--disable-triggers</></term>
-      <listitem>
-       <para>
-        This option is only relevant when creating a data-only dump.
-        It instructs <application>pg_dump</application> to include commands
-        to temporarily disable triggers on the target tables while
-        the data is reloaded.  Use this if you have referential
-        integrity checks or other triggers on the tables that you
-        do not want to invoke during data reload.
-       </para>
-
-       <para>
-        Presently, the commands emitted for <option>--disable-triggers</>
-        must be done as superuser.  So, you should also specify
-        a superuser name with <option>-S</>, or preferably be careful to
-        start the resulting script as a superuser.
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the archive formats, you can specify the option when you
-        call <command>pg_restore</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--inserts</option></term>
-      <listitem>
-       <para>
-        Dump data as <command>INSERT</command> commands (rather
-        than <command>COPY</command>).  This will make restoration very slow;
-        it is mainly useful for making dumps that can be loaded into
-        non-<productname>PostgreSQL</productname> databases.
-        However, since this option generates a separate command for each row,
-        an error in reloading a row causes only that row to be lost rather
-        than the entire table contents.
-        Note that
-        the restore might fail altogether if you have rearranged column order.
-        The <option>--column-inserts</option> option is safe against column
-        order changes, though even slower.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--lock-wait-timeout=<replaceable class="parameter">timeout</replaceable></option></term>
-      <listitem>
-       <para>
-        Do not wait forever to acquire shared table locks at the beginning of
-        the dump. Instead fail if unable to lock a table within the specified
-        <replaceable class="parameter">timeout</>. The timeout may be
-        specified in any of the formats accepted by <command>SET
-        statement_timeout</>.  (Allowed values vary depending on the server
-        version you are dumping from, but an integer number of milliseconds
-        is accepted by all versions since 7.3.  This option is ignored when
-        dumping from a pre-7.3 server.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--no-security-labels</option></term>
-      <listitem>
-       <para>
-        Do not dump security labels.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--no-tablespaces</option></term>
-      <listitem>
-       <para>
-        Do not output commands to select tablespaces.
-        With this option, all objects will be created in whichever
-        tablespace is the default during restore.
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the archive formats, you can specify the option when you
-        call <command>pg_restore</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--no-unlogged-table-data</option></term>
-      <listitem>
-       <para>
-        Do not dump the contents of unlogged tables.  This option has no
-        effect on whether or not the table definitions (schema) are dumped;
-        it only suppresses dumping the table data.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--quote-all-identifiers</></term>
-      <listitem>
-       <para>
-        Force quoting of all identifiers.  This may be useful when dumping a
-        database for migration to a future version that may have introduced
-        additional keywords.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--serializable-deferrable</option></term>
-      <listitem>
-       <para>
-        Use a <literal>serializable</literal> transaction for the dump, to
-        ensure that the snapshot used is consistent with later database
-        states; but do this by waiting for a point in the transaction stream
-        at which no anomalies can be present, so that there isn't a risk of
-        the dump failing or causing other transactions to roll back with a
-        <literal>serialization_failure</literal>.  See <xref linkend="mvcc">
-        for more information about transaction isolation and concurrency
-        control.
-       </para>
-
-       <para>
-        This option is not beneficial for a dump which is intended only for
-        disaster recovery.  It could be useful for a dump used to load a
-        copy of the database for reporting or other read-only load sharing
-        while the original database continues to be updated.  Without it the
-        dump may reflect a state which is not consistent with any serial
-        execution of the transactions eventually committed.  For example, if
-        batch processing techniques are used, a batch may show as closed in
-        the dump without all of the items which are in the batch appearing.
-       </para>
-
-       <para>
-        This option will make no difference if there are no read-write
-        transactions active when pg_dump is started.  If read-write
-        transactions are active, the start of the dump may be delayed for an
-        indeterminate length of time.  Once running, performance with or
-        without the switch is the same.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--use-set-session-authorization</></term>
-      <listitem>
-       <para>
-        Output SQL-standard <command>SET SESSION AUTHORIZATION</> commands
-        instead of <command>ALTER OWNER</> commands to determine object
-        ownership.  This makes the dump more standards-compatible, but
-        depending on the history of the objects in the dump, might not restore
-        properly.  Also, a dump using <command>SET SESSION AUTHORIZATION</>
-        will certainly require superuser privileges to restore correctly,
-        whereas <command>ALTER OWNER</> requires lesser privileges.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>pg_dump</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    The following command-line options control the database connection parameters.
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></option></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the server is
-        running.  If the value begins with a slash, it is used as the
-        directory for the Unix domain socket. The default is taken
-        from the <envar>PGHOST</envar> environment variable, if set,
-        else a Unix domain socket connection is attempted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></option></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server is listening for connections.
-        Defaults to the <envar>PGPORT</envar> environment variable, if
-        set, or a compiled-in default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable>username</replaceable></option></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></option></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option></term>
-      <term><option>--password</option></term>
-      <listitem>
-       <para>
-        Force <application>pg_dump</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>pg_dump</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>pg_dump</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--role=<replaceable class="parameter">rolename</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies a role name to be used to create the dump.
-        This option causes <application>pg_dump</> to issue a
-        <command>SET ROLE</> <replaceable class="parameter">rolename</>
-        command after connecting to the database. It is useful when the
-        authenticated user (specified by <option>-U</>) lacks privileges
-        needed by <application>pg_dump</>, but can switch to a role with
-        the required rights.  Some installations have a policy against
-        logging in directly as a superuser, and use of this option allows
-        dumps to be made without violating the policy.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--include-nodes</></term>
-      <listitem>
-       <para>
-        &xlonly;
-        Include <command>TO NODE</> clause in the <command>CREATE TABLE</>
-        command when producing the dump. When used while taking the dump
-        from a datanode, the option does nothing.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATABASE</envar></term>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGOPTIONS</envar></term>
-    <term><envar>PGPORT</envar></term>
-
-    <term><envar>PGUSER</envar></term>
-    <listitem>
-     <para>
-      Default connection parameters.
-     </para>
-    </listitem>
-
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
- <refsect1 id="app-pgdump-diagnostics">
-  <title>Diagnostics</title>
-
-  <para>
-   <application>pg_dump</application> internally executes
-   <command>SELECT</command> statements. If you have problems running
-   <application>pg_dump</application>, make sure you are able to
-   select information from the database using, for example, <xref
-   linkend="app-psql">.  Also, any default connection settings and environment
-   variables used by the <application>libpq</application> front-end
-   library will apply.
-  </para>
-
-  <para>
-   The database activity of <application>pg_dump</application> is
-   normally collected by the statistics collector.  If this is
-   undesirable, you can set parameter <varname>track_counts</>
-   to false via <envar>PGOPTIONS</envar> or the <literal>ALTER
-   USER</literal> command.
-  </para>
-
- </refsect1>
-
-
- <refsect1 id="pg-dump-notes">
-  <title>Notes</title>
-
-  <para>
-   If your database cluster has any local additions to the <literal>template1</> database,
-   be careful to restore the output of <application>pg_dump</application> into a
-   truly empty database; otherwise you are likely to get errors due to
-   duplicate definitions of the added objects.  To make an empty database
-   without any local additions, copy from <literal>template0</> not <literal>template1</>,
-   for example:
-<programlisting>
-CREATE DATABASE foo WITH TEMPLATE template0;
-</programlisting>
-  </para>
-
-  <para>
-   When a data-only dump is chosen and the option <option>--disable-triggers</>
-   is used, <application>pg_dump</application> emits commands
-   to disable triggers on user tables before inserting the data,
-   and then commands to re-enable them after the data has been
-   inserted.  If the restore is stopped in the middle, the system
-   catalogs might be left in the wrong state.
-  </para>
-
-  <para>
-   Members of tar archives are limited to a size less than 8 GB.
-   (This is an inherent limitation of the tar file format.)  Therefore
-   this format cannot be used if the textual representation of any one table
-   exceeds that size.  The total size of a tar archive and any of the
-   other output formats is not limited, except possibly by the
-   operating system.
-  </para>
-
-  <para>
-   The dump file produced by <application>pg_dump</application>
-   does not contain the statistics used by the optimizer to make
-   query planning decisions.  Therefore, it is wise to run
-   <command>ANALYZE</command> after restoring from a dump file
-   to ensure optimal performance; see <xref linkend="vacuum-for-statistics">
-   and <xref linkend="autovacuum"> for more information.
-   The dump file also does not
-   contain any <command>ALTER DATABASE ... SET</> commands;
-   these settings are dumped by <xref linkend="app-pg-dumpall">,
-   along with database users and other installation-wide settings.
-  </para>
-
-  <para>
-   Because <application>pg_dump</application> is used to transfer data
-   to newer versions of <productname>PostgreSQL</>, the output of
-   <application>pg_dump</application> can be expected to load into
-   <productname>PostgreSQL</> server versions newer than
-   <application>pg_dump</>'s version.  <application>pg_dump</> can also
-   dump from <productname>PostgreSQL</> servers older than its own version.
-   (Currently, servers back to version 7.0 are supported.)
-   However, <application>pg_dump</> cannot dump from
-   <productname>PostgreSQL</> servers newer than its own major version;
-   it will refuse to even try, rather than risk making an invalid dump.
-   Also, it is not guaranteed that <application>pg_dump</>'s output can
-   be loaded into a server of an older major version &mdash; not even if the
-   dump was taken from a server of that version.  Loading a dump file
-   into an older server may require manual editing of the dump file
-   to remove syntax not understood by the older server.
-  </para>
- </refsect1>
-
- <refsect1 id="pg-dump-examples">
-  <title id="pg-dump-examples-title">Examples</title>
-
-  <para>
-   To dump a database called <literal>mydb</> into a SQL-script file:
-<screen>
-<prompt>$</prompt> <userinput>pg_dump mydb &gt; db.sql</userinput>
-</screen>
-  </para>
-
-  <para>
-   To reload such a script into a (freshly created) database named
-   <literal>newdb</>:
-
-<screen>
-<prompt>$</prompt> <userinput>psql -d newdb -f db.sql</userinput>
-</screen>
-  </para>
-
-  <para>
-   To dump a database into a custom-format archive file:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -Fc mydb &gt; db.dump</userinput>
-</screen>
-  </para>
-
-  <para>
-   To dump a database into a directory-format archive:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -Fd mydb -f dumpdir</userinput>
-</screen>
-  </para>
-
-  <para>
-   To reload an archive file into a (freshly created) database named
-   <literal>newdb</>:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_restore -d newdb db.dump</userinput>
-</screen>
-  </para>
-
-  <para>
-   To dump a single table named <literal>mytab</>:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -t mytab mydb &gt; db.sql</userinput>
-</screen>
-  </para>
-
-  <para>
-   To dump all tables whose names start with <literal>emp</> in the
-   <literal>detroit</> schema, except for the table named
-   <literal>employee_log</literal>:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -t 'detroit.emp*' -T detroit.employee_log mydb &gt; db.sql</userinput>
-</screen>
-  </para>
-
-  <para>
-   To dump all schemas whose names start with <literal>east</> or
-   <literal>west</> and end in <literal>gsm</>, excluding any schemas whose
-   names contain the word <literal>test</>:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -n 'east*gsm' -n 'west*gsm' -N '*test*' mydb &gt; db.sql</userinput>
-</screen>
-  </para>
-
-  <para>
-   The same, using regular expression notation to consolidate the switches:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -n '(east|west)*gsm' -N '*test*' mydb &gt; db.sql</userinput>
-</screen>
-  </para>
-
-  <para>
-   To dump all database objects except for tables whose names begin with
-   <literal>ts_</literal>:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -T 'ts_*' mydb &gt; db.sql</userinput>
-</screen>
-  </para>
-
-  <para>
-   To specify an upper-case or mixed-case name in <option>-t</> and related
-   switches, you need to double-quote the name; else it will be folded to
-   lower case (see <xref
-   linkend="APP-PSQL-patterns" endterm="APP-PSQL-patterns-title">).  But
-   double quotes are special to the shell, so in turn they must be quoted.
-   Thus, to dump a single table with a mixed-case name, you need something
-   like
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -t '"MixedCaseName"' mydb &gt; mytab.sql</userinput>
-</screen>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-pg-dumpall"></member>
-   <member><xref linkend="app-pgrestore"></member>
-   <member><xref linkend="app-psql"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pg_dumpall.sgmlin b/doc-xc/src/sgml/ref/pg_dumpall.sgmlin
deleted file mode 100644
index 8eb33944f2..0000000000
--- a/doc-xc/src/sgml/ref/pg_dumpall.sgmlin
+++ /dev/null
@@ -1,617 +0,0 @@
-<!--
-doc/src/sgml/ref/pg_dumpall.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-PG-DUMPALL">
- <refmeta>
-  <refentrytitle><application>pg_dumpall</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_dumpall</refname>
-  <refpurpose>extract a <productname>PostgreSQL</productname> database cluster into a script file</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-pg-dumpall">
-  <primary>pg_dumpall</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_dumpall</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="app-pg-dumpall-description">
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <application>pg_dumpall</application> is a utility for writing out
-   (<quote>dumping</quote>) all <productname>PostgreSQL</> databases
-   of a cluster into one script file.  The script file contains
-   <acronym>SQL</acronym> commands that can be used as input to <xref
-   linkend="app-psql"> to restore the databases.  It does this by
-   calling <xref linkend="app-pgdump"> for each database in a cluster.
-   <application>pg_dumpall</application> also dumps global objects
-   that are common to all databases.
-   (<application>pg_dump</application> does not save these objects.)
-   This currently includes information about database users and
-   groups, tablespaces, and properties such as access permissions
-   that apply to databases as a whole.
-  </para>
-
-  <para>
-   Since <application>pg_dumpall</application> reads tables from all
-   databases you will most likely have to connect as a database
-   superuser in order to produce a complete dump.  Also you will need
-   superuser privileges to execute the saved script in order to be
-   allowed to add users and groups, and to create databases.
-  </para>
-
-  <para>
-   The SQL script will be written to the standard output.  Use the
-   [-f|file] option or shell operators to redirect it into a file.
-  </para>
-
-  <para>
-  <application>pg_dumpall</application> needs to connect several
-  times to the <productname>PostgreSQL</productname> server (once per
-  database).  If you use password authentication it will ask for
-  a password each time. It is convenient to have a
-  <filename>~/.pgpass</> file in such cases. See <xref
-  linkend="libpq-pgpass"> for more information.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Options</title>
-
-   <para>
-    The following command-line options control the content and
-    format of the output.
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-a</></term>
-      <term><option>--data-only</></term>
-      <listitem>
-       <para>
-        Dump only the data, not the schema (data definitions).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-c</option></term>
-      <term><option>--clean</option></term>
-      <listitem>
-       <para>
-        Include SQL commands to clean (drop) databases before
-        recreating them.  <command>DROP</> commands for roles and
-        tablespaces are added as well.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-f <replaceable class="parameter">filename</replaceable></option></term>
-      <term><option>--file=<replaceable class="parameter">filename</replaceable></option></term>
-      <listitem>
-       <para>
-        Send output to the specified file.  If this is omitted, the
-        standard output is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-g</option></term>
-      <term><option>--globals-only</option></term>
-      <listitem>
-       <para>
-        Dump only global objects (roles and tablespaces), no databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-i</></term>
-      <term><option>--ignore-version</></term>
-      <listitem>
-       <para>
-        A deprecated option that is now ignored.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o</></term>
-      <term><option>--oids</></term>
-      <listitem>
-       <para>
-        Dump object identifiers (<acronym>OID</acronym>s) as part of the
-        data for every table.  Use this option if your application references
-        the <acronym>OID</>
-        columns in some way (e.g., in a foreign key constraint).
-        Otherwise, this option should not be used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-O</></term>
-      <term><option>--no-owner</option></term>
-      <listitem>
-       <para>
-        Do not output commands to set
-        ownership of objects to match the original database.
-        By default, <application>pg_dumpall</application> issues
-        <command>ALTER OWNER</> or
-        <command>SET SESSION AUTHORIZATION</command>
-        statements to set ownership of created schema elements.
-        These statements
-        will fail when the script is run unless it is started by a superuser
-        (or the same user that owns all of the objects in the script).
-        To make a script that can be restored by any user, but will give
-        that user ownership of all the objects, specify <option>-O</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-r</option></term>
-      <term><option>--roles-only</option></term>
-      <listitem>
-       <para>
-        Dump only roles, no databases or tablespaces.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option></term>
-      <term><option>--schema-only</option></term>
-      <listitem>
-       <para>
-        Dump only the object definitions (schema), not data.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-S <replaceable class="parameter">username</replaceable></option></term>
-      <term><option>--superuser=<replaceable class="parameter">username</replaceable></option></term>
-      <listitem>
-       <para>
-        Specify the superuser user name to use when disabling triggers.
-        This is only relevant if <option>--disable-triggers</> is used.
-        (Usually, it's better to leave this out, and instead start the
-        resulting script as superuser.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t</option></term>
-      <term><option>--tablespaces-only</option></term>
-      <listitem>
-       <para>
-        Dump only tablespaces, no databases or roles.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-v</></term>
-      <term><option>--verbose</></term>
-      <listitem>
-       <para>
-        Specifies verbose mode.  This will cause
-        <application>pg_dumpall</application> to output start/stop
-        times to the dump file, and progress messages to standard error.
-        It will also enable verbose output in <application>pg_dump</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>pg_dumpall</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-x</></term>
-      <term><option>--no-privileges</></term>
-      <term><option>--no-acl</></term>
-      <listitem>
-       <para>
-        Prevent dumping of access privileges (grant/revoke commands).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--binary-upgrade</option></term>
-      <listitem>
-       <para>
-        This option is for use by in-place upgrade utilities.  Its use
-        for other purposes is not recommended or supported.  The
-        behavior of the option may change in future releases without
-        notice.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--column-inserts</option></term>
-      <term><option>--attribute-inserts</option></term>
-      <listitem>
-       <para>
-        Dump data as <command>INSERT</command> commands with explicit
-        column names (<literal>INSERT INTO
-        <replaceable>table</replaceable>
-        (<replaceable>column</replaceable>, ...) VALUES
-        ...</literal>).  This will make restoration very slow; it is mainly
-        useful for making dumps that can be loaded into
-        non-<productname>PostgreSQL</productname> databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--disable-dollar-quoting</></term>
-      <listitem>
-       <para>
-        This option disables the use of dollar quoting for function bodies,
-        and forces them to be quoted using SQL standard string syntax.
-       </para>
-     </listitem>
-    </varlistentry>
-
-     <varlistentry>
-      <term><option>--disable-triggers</></term>
-      <listitem>
-       <para>
-        This option is only relevant when creating a data-only dump.
-        It instructs <application>pg_dumpall</application> to include commands
-        to temporarily disable triggers on the target tables while
-        the data is reloaded.  Use this if you have referential
-        integrity checks or other triggers on the tables that you
-        do not want to invoke during data reload.
-       </para>
-
-       <para>
-        Presently, the commands emitted for <option>--disable-triggers</>
-        must be done as superuser.  So, you should also specify
-        a superuser name with <option>-S</>, or preferably be careful to
-        start the resulting script as a superuser.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--inserts</option></term>
-      <listitem>
-       <para>
-        Dump data as <command>INSERT</command> commands (rather
-        than <command>COPY</command>).  This will make restoration very slow;
-        it is mainly useful for making dumps that can be loaded into
-        non-<productname>PostgreSQL</productname> databases.  Note that
-        the restore might fail altogether if you have rearranged column order.
-        The <option>--column-inserts</option> option is safer, though even
-        slower.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--lock-wait-timeout=<replaceable class="parameter">timeout</replaceable></option></term>
-      <listitem>
-       <para>
-        Do not wait forever to acquire shared table locks at the beginning of
-        the dump. Instead, fail if unable to lock a table within the specified
-        <replaceable class="parameter">timeout</>. The timeout may be
-        specified in any of the formats accepted by <command>SET
-        statement_timeout</>.  Allowed values vary depending on the server
-        version you are dumping from, but an integer number of milliseconds
-        is accepted by all versions since 7.3.  This option is ignored when
-        dumping from a pre-7.3 server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--no-security-labels</option></term>
-      <listitem>
-       <para>
-        Do not dump security labels.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--no-tablespaces</option></term>
-      <listitem>
-       <para>
-        Do not output commands to create tablespaces nor select tablespaces
-        for objects.
-        With this option, all objects will be created in whichever
-        tablespace is the default during restore.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--no-unlogged-table-data</option></term>
-      <listitem>
-       <para>
-        Do not dump the contents of unlogged tables.  This option has no
-        effect on whether or not the table definitions (schema) are dumped;
-        it only suppresses dumping the table data.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--quote-all-identifiers</></term>
-      <listitem>
-       <para>
-        Force quoting of all identifiers.  This may be useful when dumping a
-        database for migration to a future version that may have introduced
-        additional keywords.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--use-set-session-authorization</></term>
-      <listitem>
-       <para>
-        Output SQL-standard <command>SET SESSION AUTHORIZATION</> commands
-        instead of <command>ALTER OWNER</> commands to determine object
-        ownership.  This makes the dump more standards compatible, but
-        depending on the history of the objects in the dump, might not restore
-        properly.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--dump-nodes</></term>
-      <listitem>
-       <para>
-        &xlonly;
-        Output commands to create nodes and node groups. This option may be used
-		 while adding a new coordinator to an existing <productname>Postgres-XL</> cluster.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>pg_dumpall</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-  <para>
-   The following command-line options control the database connection parameters.
-
-   <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable>host</replaceable></option></term>
-      <term><option>--host=<replaceable>host</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the database
-        server is running.  If the value begins with a slash, it is
-        used as the directory for the Unix domain socket.  The default
-        is taken from the <envar>PGHOST</envar> environment variable,
-        if set, else a Unix domain socket connection is attempted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l <replaceable>dbname</replaceable></option></term>
-      <term><option>--database=<replaceable>dbname</replaceable></option></term>
-      <listitem>
-       <para>
-         Specifies the name of the database to connect to to dump global
-         objects and discover what other databases should be dumped. If
-         not specified, the <literal>postgres</literal> database will be used,
-         and if that does not exist, <literal>template1</literal> will be used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable>port</replaceable></option></term>
-      <term><option>--port=<replaceable>port</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server is listening for connections.
-        Defaults to the <envar>PGPORT</envar> environment variable, if
-        set, or a compiled-in default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable>username</replaceable></option></term>
-      <term><option>--username=<replaceable>username</replaceable></option></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option></term>
-      <term><option>--password</option></term>
-      <listitem>
-       <para>
-        Force <application>pg_dumpall</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>pg_dumpall</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>pg_dumpall</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-
-       <para>
-        Note that the password prompt will occur again for each database
-        to be dumped.  Usually, it's better to set up a
-        <filename>~/.pgpass</> file than to rely on manual password entry.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--role=<replaceable class="parameter">rolename</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies a role name to be used to create the dump.
-        This option causes <application>pg_dumpall</> to issue a
-        <command>SET ROLE</> <replaceable class="parameter">rolename</>
-        command after connecting to the database. It is useful when the
-        authenticated user (specified by <option>-U</>) lacks privileges
-        needed by <application>pg_dumpall</>, but can switch to a role with
-        the required rights.  Some installations have a policy against
-        logging in directly as a superuser, and use of this option allows
-        dumps to be made without violating the policy.
-       </para>
-      </listitem>
-     </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGOPTIONS</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Since <application>pg_dumpall</application> calls
-   <application>pg_dump</application> internally, some diagnostic
-   messages will refer to <application>pg_dump</application>.
-  </para>
-
-  <para>
-   Once restored, it is wise to run <command>ANALYZE</> on each
-   database so the optimizer has useful statistics. You
-   can also run <command>vacuumdb -a -z</> to analyze all
-   databases.
-  </para>
-
-  <para>
-   <application>pg_dumpall</application> requires all needed
-   tablespace directories to exist before the restore;  otherwise,
-   database creation will fail for databases in non-default
-   locations.
-  </para>
- </refsect1>
-
-
- <refsect1 id="app-pg-dumpall-ex">
-  <title>Examples</title>
-  <para>
-   To dump all databases:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dumpall &gt; db.out</userinput>
-</screen>
-  </para>
-
-  <para>
-   To reload database(s) from this file, you can use:
-<screen>
-<prompt>$</prompt> <userinput>psql -f db.out postgres</userinput>
-</screen>
-   (It is not important to which database you connect here since the
-   script file created by <application>pg_dumpall</application> will
-   contain the appropriate commands to create and connect to the saved
-   databases.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <para>
-    Check <xref linkend="app-pgdump"> for details on possible
-    error conditions.
-  </para>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pg_resetxlog.sgmlin b/doc-xc/src/sgml/ref/pg_resetxlog.sgmlin
deleted file mode 100644
index 8ea005357b..0000000000
--- a/doc-xc/src/sgml/ref/pg_resetxlog.sgmlin
+++ /dev/null
@@ -1,226 +0,0 @@
-<!--
-doc/src/sgml/ref/pg_resetxlog.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-PGRESETXLOG">
- <refmeta>
-  <refentrytitle><application>pg_resetxlog</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_resetxlog</refname>
-  <refpurpose>reset the write-ahead log and other control information of a <productname>PostgreSQL</productname> database cluster</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_resetxlog</command>
-   <arg>-f</arg>
-   <arg>-n</arg>
-   <arg>-o<replaceable class="parameter">oid</replaceable> </arg>
-   <arg>-x <replaceable class="parameter">xid</replaceable> </arg>
-   <arg>-e <replaceable class="parameter">xid_epoch</replaceable> </arg>
-   <arg>-m <replaceable class="parameter">mxid</replaceable> </arg>
-   <arg>-O <replaceable class="parameter">mxoff</replaceable> </arg>
-   <arg>-l <replaceable class="parameter">timelineid</replaceable>,<replaceable class="parameter">fileid</replaceable>,<replaceable class="parameter">seg</replaceable> </arg>
-   <arg choice="plain"><replaceable>datadir</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-PGRESETXLOG-1">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>pg_resetxlog</command> clears the write-ahead log (WAL) and
-   optionally resets some other control information stored in the
-   <filename>pg_control</> file.  This function is sometimes needed
-   if these files have become corrupted.  It should be used only as a
-   last resort, when the server will not start due to such corruption.
-  </para>
-
-  <para>
-   After running this command, it should be possible to start the server,
-   but bear in mind that the database might contain inconsistent data due to
-   partially-committed transactions.  You should immediately dump your data,
-   run <command>initdb</>, and reload.  After reload, check for
-   inconsistencies and repair as needed.
-  </para>
-
-  <para>
-   This utility can only be run by the user who installed the server, because
-   it requires read/write access to the data directory.
-   For safety reasons, you must specify the data directory on the command line.
-   <command>pg_resetxlog</command> does not use the environment variable
-   <envar>PGDATA</>.
-  </para>
-
-  <para>
-   If <command>pg_resetxlog</command> complains that it cannot determine
-   valid data for <filename>pg_control</>, you can force it to proceed anyway
-   by specifying the <literal>-f</> (force) switch.  In this case plausible
-   values will be substituted for the missing data.  Most of the fields can be
-   expected to match, but manual assistance might be needed for the next OID,
-   next transaction ID and epoch, next multitransaction ID and offset, and
-   WAL starting address fields. These fields can be set using the switches
-   discussed below. If you are not able to determine correct values for all
-   these fields, <literal>-f</> can still be used, but
-   the recovered database must be treated with even more suspicion than
-   usual: an immediate dump and reload is imperative.  <emphasis>Do not</>
-   execute any data-modifying operations in the database before you dump,
-   as any such action is likely to make the corruption worse.
-  </para>
-
-  <para>
-   The <literal>-o</>, <literal>-x</>, <literal>-e</>,
-   <literal>-m</>, <literal>-O</>,
-   and <literal>-l</>
-   switches allow the next OID, next transaction ID, next transaction ID's
-   epoch, next multitransaction ID, next multitransaction offset, and WAL
-   starting address values to be set manually.  These are only needed when
-   <command>pg_resetxlog</command> is unable to determine appropriate values
-   by reading <filename>pg_control</>.  Safe values can be determined as
-   follows:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      A safe value for the next transaction ID (<literal>-x</>)
-      can be determined by looking for the numerically largest
-      file name in the directory <filename>pg_clog</> under the data directory,
-      adding one,
-      and then multiplying by 1048576.  Note that the file names are in
-      hexadecimal.  It is usually easiest to specify the switch value in
-      hexadecimal too. For example, if <filename>0011</> is the largest entry
-      in <filename>pg_clog</>, <literal>-x 0x1200000</> will work (five
-      trailing zeroes provide the proper multiplier).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A safe value for the next multitransaction ID (<literal>-m</>)
-      can be determined by looking for the numerically largest
-      file name in the directory <filename>pg_multixact/offsets</> under the
-      data directory, adding one, and then multiplying by 65536.  As above,
-      the file names are in hexadecimal, so the easiest way to do this is to
-      specify the switch value in hexadecimal and add four zeroes.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A safe value for the next multitransaction offset (<literal>-O</>)
-      can be determined by looking for the numerically largest
-      file name in the directory <filename>pg_multixact/members</> under the
-      data directory, adding one, and then multiplying by 65536.  As above,
-      the file names are in hexadecimal, so the easiest way to do this is to
-      specify the switch value in hexadecimal and add four zeroes.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The WAL starting address (<literal>-l</>) should be
-      larger than any WAL segment file name currently existing in
-      the directory <filename>pg_xlog</> under the data directory.
-      These names are also in hexadecimal and have three parts.  The first
-      part is the <quote>timeline ID</> and should usually be kept the same.
-      Do not choose a value larger than 255 (<literal>0xFF</>) for the third
-      part; instead increment the second part and reset the third part to 0.
-      For example, if <filename>00000001000000320000004A</> is the
-      largest entry in <filename>pg_xlog</>, <literal>-l 0x1,0x32,0x4B</> will
-      work; but if the largest entry is
-      <filename>000000010000003A000000FF</>, choose <literal>-l 0x1,0x3B,0x0</>
-      or more.
-     </para>
-
-     <note>
-      <para>
-       <command>pg_resetxlog</command> itself looks at the files in
-       <filename>pg_xlog</> and chooses a default <literal>-l</> setting
-       beyond the last existing file name.  Therefore, manual adjustment of
-       <literal>-l</> should only be needed if you are aware of WAL segment
-       files that are not currently present in <filename>pg_xlog</>, such as
-       entries in an offline archive; or if the contents of
-       <filename>pg_xlog</> have been lost entirely.
-      </para>
-     </note>
-    </listitem>
-
-    <listitem>
-     <para>
-      There is no comparably easy way to determine a next OID that's beyond
-      the largest one in the database, but fortunately it is not critical to
-      get the next-OID setting right.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The transaction ID epoch is not actually stored anywhere in the database
-      except in the field that is set by <command>pg_resetxlog</command>,
-      so any value will work so far as the database itself is concerned.
-      You might need to adjust this value to ensure that replication
-      systems such as <application>Slony-I</> work correctly &mdash;
-      if so, an appropriate value should be obtainable from the state of
-      the downstream replicated database.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   The <literal>-n</> (no operation) switch instructs
-   <command>pg_resetxlog</command> to print the values reconstructed from
-   <filename>pg_control</> and then exit without modifying anything.
-   This is mainly a debugging tool, but can be useful as a sanity check
-   before allowing <command>pg_resetxlog</command> to proceed for real.
-  </para>
-
-  <para>
-   The <literal>-V</> and <literal>--version</> options print
-   the <application>pg_resetxlog</application> version and exit.  The
-   options <literal>-?</> and <literal>--help</> show supported arguments,
-   and exit.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   This command must not be used when the server is
-   running.  <command>pg_resetxlog</command> will refuse to start up if
-   it finds a server lock file in the data directory.  If the
-   server crashed then a lock file might have been left
-   behind; in that case you can remove the lock file to allow
-   <command>pg_resetxlog</command> to run.  But before you do
-   so, make doubly certain that there is no server process still alive.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   In <productname>Postgres-XC</>, <command>pg_resetxlog</command>
-   will run only for local Coordinator or Datanode.  You should run it
-   for each Coordinator or Datanode manually.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   In <productname>Postgres-XL</>, <command>pg_resetxlog</command>
-   will only run locally for Coordinators and Datanodes.  You should run it
-   for each Coordinator or Datanode manually.
-  </para>
-<!## end>
-
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pg_restore.sgmlin b/doc-xc/src/sgml/ref/pg_restore.sgmlin
deleted file mode 100644
index be4851b657..0000000000
--- a/doc-xc/src/sgml/ref/pg_restore.sgmlin
+++ /dev/null
@@ -1,838 +0,0 @@
-<!-- doc/src/sgml/ref/pg_restore.sgml -->
-
-<refentry id="APP-PGRESTORE">
- <refmeta>
-  <refentrytitle>pg_restore</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_restore</refname>
-
-  <refpurpose>
-   restore a <productname>PostgreSQL</productname> database from an
-   archive file created by <application>pg_dump</application>
-  </refpurpose>
- </refnamediv>
-
- <indexterm zone="app-pgrestore">
-  <primary>pg_restore</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_restore</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg rep="repeat"><replaceable>option</replaceable></arg>
-   <arg><replaceable>filename</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1 id="app-pgrestore-description">
-  <title>Description</title>
-
-  <para>
-   <application>pg_restore</application> is a utility for restoring a
-   <productname>PostgreSQL</productname> database from an archive
-   created by <xref linkend="app-pgdump"> in one of the non-plain-text
-   formats.  It will issue the commands necessary to reconstruct the
-   database to the state it was in at the time it was saved.  The
-   archive files also allow <application>pg_restore</application> to
-   be selective about what is restored, or even to reorder the items
-   prior to being restored. The archive files are designed to be
-   portable across architectures.
-  </para>
-
-  <para>
-   <application>pg_restore</application> can operate in two modes.
-   If a database name is specified, <application>pg_restore</application>
-   connects to that database and restores archive contents directly into
-   the database.  Otherwise, a script containing the SQL
-   commands necessary to rebuild the database is created and written
-   to a file or standard output.  This script output is equivalent to
-   the plain text output format of <application>pg_dump</application>.
-   Some of the options controlling the output are therefore analogous to
-   <application>pg_dump</application> options.
-  </para>
-
-  <para>
-   Obviously, <application>pg_restore</application> cannot restore information
-   that is not present in the archive file.  For instance, if the
-   archive was made using the <quote>dump data as
-   <command>INSERT</command> commands</quote> option,
-   <application>pg_restore</application> will not be able to load the data
-   using <command>COPY</command> statements.
-  </para>
- </refsect1>
-
- <refsect1 id="app-pgrestore-options">
-  <title>Options</title>
-
-   <para>
-    <application>pg_restore</application> accepts the following command
-    line arguments.
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">filename</replaceable></term>
-      <listitem>
-       <para>
-       Specifies the location of the archive file (or directory, for a
-       directory-format archive) to be restored.
-       If not specified, the standard input is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-a</option></term>
-      <term><option>--data-only</option></term>
-      <listitem>
-       <para>
-        Restore only the data, not the schema (data definitions).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-c</option></term>
-      <term><option>--clean</option></term>
-      <listitem>
-       <para>
-        Clean (drop) database objects before recreating them.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-C</option></term>
-      <term><option>--create</option></term>
-      <listitem>
-       <para>
-        Create the database before restoring into it.  (When this
-        option is used, the database named with <option>-d</option> is
-        used only to issue the initial <command>CREATE DATABASE</>
-        command.  All data is restored into the database name that
-        appears in the archive.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-d <replaceable class="parameter">dbname</replaceable></option></term>
-      <term><option>--dbname=<replaceable class="parameter">dbname</replaceable></option></term>
-      <listitem>
-       <para>
-        Connect to database <replaceable
-        class="parameter">dbname</replaceable> and restore directly
-        into the database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</option></term>
-      <term><option>--exit-on-error</option></term>
-      <listitem>
-       <para>
-        Exit if an error is encountered while sending SQL commands to
-        the database. The default is to continue and to display a count of
-        errors at the end of the restoration.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-f <replaceable>filename</replaceable></option></term>
-      <term><option>--file=<replaceable>filename</replaceable></option></term>
-      <listitem>
-       <para>
-        Specify output file for generated script, or for the listing
-        when used with <option>-l</option>. Default is the standard
-        output.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-F <replaceable class="parameter">format</replaceable></option></term>
-      <term><option>--format=<replaceable class="parameter">format</replaceable></option></term>
-      <listitem>
-       <para>
-        Specify format of the archive.  It is not necessary to specify
-        the format, since <application>pg_restore</application> will
-        determine the format automatically. If specified, it can be
-        one of the following:
-
-       <variablelist>
-        <varlistentry>
-         <term><literal>c</></term>
-         <term><literal>custom</></term>
-         <listitem>
-          <para>
-           The archive is in the custom format of
-           <application>pg_dump</application>.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term><literal>d</></term>
-         <term><literal>directory</></term>
-         <listitem>
-          <para>
-           The archive is a directory archive.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term><literal>t</></term>
-         <term><literal>tar</></term>
-         <listitem>
-          <para>
-           The archive is a <command>tar</command> archive.
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-i</option></term>
-      <term><option>--ignore-version</option></term>
-      <listitem>
-       <para>
-        A deprecated option that is now ignored.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-I <replaceable class="parameter">index</replaceable></option></term>
-      <term><option>--index=<replaceable class="parameter">index</replaceable></option></term>
-      <listitem>
-       <para>
-        Restore definition of named index only.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-j <replaceable class="parameter">number-of-jobs</replaceable></option></term>
-      <term><option>--jobs=<replaceable class="parameter">number-of-jobs</replaceable></option></term>
-      <listitem>
-       <para>
-        Run the most time-consuming parts
-        of <application>pg_restore</> &mdash; those which load data,
-        create indexes, or create constraints &mdash; using multiple
-        concurrent jobs.  This option can dramatically reduce the time
-        to restore a large database to a server running on a
-        multiprocessor machine.
-       </para>
-
-       <para>
-        Each job is one process or one thread, depending on the
-        operating system, and uses a separate connection to the
-        server.
-       </para>
-
-       <para>
-        The optimal value for this option depends on the hardware
-        setup of the server, of the client, and of the network.
-        Factors include the number of CPU cores and the disk setup.  A
-        good place to start is the number of CPU cores on the server,
-        but values larger than that can also lead to faster restore
-        times in many cases.  Of course, values that are too high will
-        lead to decreased performance because of thrashing.
-       </para>
-
-       <para>
-        Only the custom archive format is supported with this option.
-        The input file must be a regular file (not, for example, a
-        pipe).  This option is ignored when emitting a script rather
-        than connecting directly to a database server.  Also, multiple
-        jobs cannot be used together with the
-        option <option>--single-transaction</option>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l</option></term>
-      <term><option>--list</option></term>
-      <listitem>
-       <para>
-        List the contents of the archive. The output of this operation
-        can be used as input to the <option>-L</option> option.  Note that
-        if filtering switches such as <option>-n</> or <option>-t</> are
-        used with <option>-l</>, they will restrict the items listed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-L <replaceable class="parameter">list-file</replaceable></option></term>
-      <term><option>--use-list=<replaceable class="parameter">list-file</replaceable></option></term>
-      <listitem>
-       <para>
-        Restore only those archive elements that are listed in <replaceable
-        class="PARAMETER">list-file</replaceable>, and restore them in the
-        order they appear in the file.  Note that
-        if filtering switches such as <option>-n</> or <option>-t</> are
-        used with <option>-L</>, they will further restrict the items restored.
-       </para>
-       <para>
-        <replaceable class="PARAMETER">list-file</> is normally created by
-        editing the output of a previous <option>-l</> operation.
-        Lines can be moved or removed, and can also
-        be commented out by placing a semicolon (<literal>;</literal>) at the
-        start of the line.  See below for examples.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-n <replaceable class="parameter">namespace</replaceable></option></term>
-      <term><option>--schema=<replaceable class="parameter">schema</replaceable></option></term>
-      <listitem>
-       <para>
-        Restore only objects that are in the named schema.  This can be
-        combined with the <option>-t</option> option to restore just a
-        specific table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-O</option></term>
-      <term><option>--no-owner</option></term>
-      <listitem>
-       <para>
-        Do not output commands to set
-        ownership of objects to match the original database.
-        By default, <application>pg_restore</application> issues
-        <command>ALTER OWNER</> or
-        <command>SET SESSION AUTHORIZATION</command>
-        statements to set ownership of created schema elements.
-        These statements will fail unless the initial connection to the
-        database is made by a superuser
-        (or the same user that owns all of the objects in the script).
-        With <option>-O</option>, any user name can be used for the
-        initial connection, and this user will own all the created objects.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-P <replaceable class="parameter">function-name(argtype [, ...])</replaceable></option></term>
-      <term><option>--function=<replaceable class="parameter">function-name(argtype [, ...])</replaceable></option></term>
-      <listitem>
-       <para>
-        Restore the named function only.  Be careful to spell the function
-        name and arguments exactly as they appear in the dump file's table
-        of contents.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-R</option></term>
-      <term><option>--no-reconnect</option></term>
-      <listitem>
-       <para>
-        This option is obsolete but still accepted for backwards
-        compatibility.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option></term>
-      <term><option>--schema-only</option></term>
-      <listitem>
-       <para>
-        Restore only the schema (data definitions), not the data (table
-        contents).  Current sequence values will not be restored, either.
-        (Do not confuse this with the <option>--schema</> option, which
-        uses the word <quote>schema</> in a different meaning.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-S <replaceable class="parameter">username</replaceable></option></term>
-      <term><option>--superuser=<replaceable class="parameter">username</replaceable></option></term>
-      <listitem>
-       <para>
-        Specify the superuser user name to use when disabling triggers.
-        This is only relevant if <option>--disable-triggers</> is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t <replaceable class="parameter">table</replaceable></option></term>
-      <term><option>--table=<replaceable class="parameter">table</replaceable></option></term>
-      <listitem>
-       <para>
-        Restore definition and/or data of named table only.  This can be
-        combined with the <option>-n</option> option to specify a schema.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-T <replaceable class="parameter">trigger</replaceable></option></term>
-      <term><option>--trigger=<replaceable class="parameter">trigger</replaceable></option></term>
-      <listitem>
-       <para>
-        Restore named trigger only.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-v</option></term>
-      <term><option>--verbose</option></term>
-      <listitem>
-       <para>
-        Specifies verbose mode.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>pg_restore</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-x</option></term>
-      <term><option>--no-privileges</option></term>
-      <term><option>--no-acl</option></term>
-      <listitem>
-       <para>
-        Prevent restoration of access privileges (grant/revoke commands).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-1</option></term>
-      <term><option>--single-transaction</option></term>
-      <listitem>
-       <para>
-        Execute the restore as a single transaction (that is, wrap the
-        emitted commands in <command>BEGIN</>/<command>COMMIT</>).  This
-        ensures that either all the commands complete successfully, or no
-        changes are applied. This option implies
-        <option>--exit-on-error</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--disable-triggers</></term>
-      <listitem>
-       <para>
-        This option is only relevant when performing a data-only restore.
-        It instructs <application>pg_restore</application> to execute commands
-        to temporarily disable triggers on the target tables while
-        the data is reloaded.  Use this if you have referential
-        integrity checks or other triggers on the tables that you
-        do not want to invoke during data reload.
-       </para>
-
-       <para>
-        Presently, the commands emitted for
-        <option>--disable-triggers</> must be done as superuser.  So, you
-        should also specify a superuser name with <option>-S</>, or
-        preferably run <application>pg_restore</application> as a
-        <productname>PostgreSQL</> superuser.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--no-data-for-failed-tables</option></term>
-      <listitem>
-       <para>
-        By default, table data is restored even if the creation command
-        for the table failed (e.g., because it already exists).
-        With this option, data for such a table is skipped.
-        This behavior is useful if the target database already
-        contains the desired table contents.  For example,
-        auxiliary tables for <productname>PostgreSQL</> extensions
-        such as <productname>PostGIS</> might already be loaded in
-        the target database; specifying this option prevents duplicate
-        or obsolete data from being loaded into them.
-       </para>
-
-       <para>
-        This option is effective only when restoring directly into a
-        database, not when producing SQL script output.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--no-security-labels</option></term>
-      <listitem>
-       <para>
-        Do not output commands to restore security labels,
-        even if the archive contains them.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--no-tablespaces</option></term>
-      <listitem>
-       <para>
-        Do not output commands to select tablespaces.
-        With this option, all objects will be created in whichever
-        tablespace is the default during restore.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--use-set-session-authorization</option></term>
-      <listitem>
-       <para>
-        Output SQL-standard <command>SET SESSION AUTHORIZATION</> commands
-        instead of <command>ALTER OWNER</> commands to determine object
-        ownership.  This makes the dump more standards-compatible, but
-        depending on the history of the objects in the dump, might not restore
-        properly.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>pg_restore</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    <application>pg_restore</application> also accepts
-    the following command line arguments for connection parameters:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></option></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the server is
-        running.  If the value begins with a slash, it is used as the
-        directory for the Unix domain socket. The default is taken
-        from the <envar>PGHOST</envar> environment variable, if set,
-        else a Unix domain socket connection is attempted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></option></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server is listening for connections.
-        Defaults to the <envar>PGPORT</envar> environment variable, if
-        set, or a compiled-in default.
-        </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable>username</replaceable></option></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></option></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option></term>
-      <term><option>--password</option></term>
-      <listitem>
-       <para>
-        Force <application>pg_restore</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>pg_restore</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>pg_restore</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--role=<replaceable class="parameter">rolename</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies a role name to be used to perform the restore.
-        This option causes <application>pg_restore</> to issue a
-        <command>SET ROLE</> <replaceable class="parameter">rolename</>
-        command after connecting to the database. It is useful when the
-        authenticated user (specified by <option>-U</>) lacks privileges
-        needed by <application>pg_restore</>, but can switch to a role with
-        the required rights.  Some installations have a policy against
-        logging in directly as a superuser, and use of this option allows
-        restores to be performed without violating the policy.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGOPTIONS</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1 id="app-pgrestore-diagnostics">
-  <title>Diagnostics</title>
-
-  <para>
-   When a direct database connection is specified using the
-   <option>-d</option> option, <application>pg_restore</application>
-   internally executes <acronym>SQL</acronym> statements. If you have
-   problems running <application>pg_restore</application>, make sure
-   you are able to select information from the database using, for
-   example, <xref linkend="app-psql">.  Also, any default connection
-   settings and environment variables used by the
-   <application>libpq</application> front-end library will apply.
-  </para>
- </refsect1>
-
-
- <refsect1 id="app-pgrestore-notes">
-  <title>Notes</title>
-
-  <para>
-   If your installation has any local additions to the
-   <literal>template1</> database, be careful to load the output of
-   <application>pg_restore</application> into a truly empty database;
-   otherwise you are likely to get errors due to duplicate definitions
-   of the added objects.  To make an empty database without any local
-   additions, copy from <literal>template0</> not <literal>template1</>, for example:
-<programlisting>
-CREATE DATABASE foo WITH TEMPLATE template0;
-</programlisting>
-  </para>
-
-  <para>
-   The limitations of <application>pg_restore</application> are detailed below.
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      When restoring data to a pre-existing table and the option
-      <option>--disable-triggers</> is used,
-      <application>pg_restore</application> emits commands
-      to disable triggers on user tables before inserting the data, then emits commands to
-      re-enable them after the data has been inserted.  If the restore is stopped in the
-      middle, the system catalogs might be left in the wrong state.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <application>pg_restore</application> cannot restore large objects
-      selectively;  for instance, only those for a specific table.  If
-      an archive contains large objects, then all large objects will be
-      restored, or none of them if they are excluded via <option>-L</option>,
-      <option>-t</option>, or other options.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-  </para>
-
-  <para>
-   See also the <xref linkend="app-pgdump"> documentation for details on
-   limitations of <application>pg_dump</application>.
-  </para>
-
-  <para>
-   Once restored, it is wise to run <command>ANALYZE</> on each
-   restored table so the optimizer has useful statistics; see
-   <xref linkend="vacuum-for-statistics"> and
-   <xref linkend="autovacuum"> for more information.
-  </para>
-
- </refsect1>
-
-
- <refsect1 id="app-pgrestore-examples">
-  <title>Examples</title>
-
-  <para>
-   Assume we have dumped a database called <literal>mydb</> into a
-   custom-format dump file:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -Fc mydb &gt; db.dump</userinput>
-</screen>
-  </para>
-
-  <para>
-   To drop the database and recreate it from the dump:
-
-<screen>
-<prompt>$</prompt> <userinput>dropdb mydb</userinput>
-<prompt>$</prompt> <userinput>pg_restore -C -d postgres db.dump</userinput>
-</screen>
-
-   The database named in the <option>-d</> switch can be any database existing
-   in the cluster; <application>pg_restore</> only uses it to issue the
-   <command>CREATE DATABASE</> command for <literal>mydb</>.  With
-   <option>-C</>, data is always restored into the database name that appears
-   in the dump file.
-  </para>
-
-  <para>
-   To reload the dump into a new database called <literal>newdb</>:
-
-<screen>
-<prompt>$</prompt> <userinput>createdb -T template0 newdb</userinput>
-<prompt>$</prompt> <userinput>pg_restore -d newdb db.dump</userinput>
-</screen>
-
-   Notice we don't use <option>-C</>, and instead connect directly to the
-   database to be restored into.  Also note that we clone the new database
-   from <literal>template0</> not <literal>template1</>, to ensure it is
-   initially empty.
-  </para>
-
-  <para>
-   To reorder database items, it is first necessary to dump the table of
-   contents of the archive:
-<screen>
-<prompt>$</prompt> <userinput>pg_restore -l db.dump &gt; db.list</userinput>
-</screen>
-   The listing file consists of a header and one line for each item, e.g.:
-<programlisting>
-;
-; Archive created at Mon Sep 14 13:55:39 2009
-;     dbname: DBDEMOS
-;     TOC Entries: 81
-;     Compression: 9
-;     Dump Version: 1.10-0
-;     Format: CUSTOM
-;     Integer: 4 bytes
-;     Offset: 8 bytes
-;     Dumped from database version: 8.3.5
-;     Dumped by pg_dump version: 8.3.8
-;
-;
-; Selected TOC Entries:
-;
-3; 2615 2200 SCHEMA - public pasha
-1861; 0 0 COMMENT - SCHEMA public pasha
-1862; 0 0 ACL - public pasha
-317; 1247 17715 TYPE public composite pasha
-319; 1247 25899 DOMAIN public domain0 pasha
-</programlisting>
-   Semicolons start a comment, and the numbers at the start of lines refer to the
-   internal archive ID assigned to each item.
-  </para>
-
-  <para>
-   Lines in the file can be commented out, deleted, and reordered. For example:
-<programlisting>
-10; 145433 TABLE map_resolutions postgres
-;2; 145344 TABLE species postgres
-;4; 145359 TABLE nt_header postgres
-6; 145402 TABLE species_records postgres
-;8; 145416 TABLE ss_old postgres
-</programlisting>
-   could be used as input to <application>pg_restore</application> and would only restore
-   items 10 and 6, in that order:
-<screen>
-<prompt>$</prompt> <userinput>pg_restore -L db.list db.dump</userinput>
-</screen>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-pgdump"></member>
-   <member><xref linkend="app-pg-dumpall"></member>
-   <member><xref linkend="app-psql"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pgxc_clean-ref.sgmlin b/doc-xc/src/sgml/ref/pgxc_clean-ref.sgmlin
deleted file mode 100644
index 577633e2d2..0000000000
--- a/doc-xc/src/sgml/ref/pgxc_clean-ref.sgmlin
+++ /dev/null
@@ -1,226 +0,0 @@
-<!--
-doc/src/sgml/ref/psql-ref.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-PGXC-CLEAN">
-  <refmeta>
-    <refentrytitle><application>pgxc_clean</application></refentrytitle>
-    <manvolnum>1</manvolnum>
-    <refmiscinfo>Application</refmiscinfo>
-  </refmeta>
-
-  <refnamediv>
-    <refname><application>pgxc_clean</application></refname>
-    <refpurpose>
-      <productname>Postgres-XC</productname> interactive terminal
-    </refpurpose>
-  </refnamediv>
-
- <indexterm zone="app-pgxc-clean">
-  <primary>pgxc_clean</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pgxc_clean</command>
-   <arg rep="repeat"><replaceable class="parameter">option</replaceable></arg>
-   <arg><replaceable class="parameter">dbname</replaceable>
-   <arg><replaceable class="parameter">username</replaceable></arg></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xconly;
-
-    <para>
-     <application>pgxc_clean</application> is Postgres-XC utility to maintain transaction status after a crash.
-     When some Postgres-XC node crashes and recovers or fails over, commit status of such node may be inconsistent
-     with other nodes.   <application>pgxc_clean</application> checks transaction commit status and corrects them.
-    </para>
-    <para>
-     You should run this utility against one of the available coordinators.   THe tool cleans up transaction status
-     of all the nodes automatically.
-    </para>
- </refsect1>
-
- <refsect1 id="R1-APP-PGXC-CLEAN-3">
-  <title>Options</title>
-
-  <variablelist>
-    <varlistentry>
-      <term><option>-a</></term>
-      <term><option>--all</></term>
-      <listitem>
-      <para>
-       Cleanup all the database available.
-      <literal>all</literal>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-d<replaceable class="parameter">databasename</replaceable></option></term>
-      <term><option>--dbname=<replaceable class="parameter">databasename</replaceable></option></term>
-      <listitem>
-      <para>
-       Database name to clean up.  This option can be specified multiple times for more than one database.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-h<replaceable class="parameter">hostname</replaceable></></term>
-      <term><option>--command=<replaceable class="parameter">hostname</replaceable></></term>
-      <listitem>
-      <para>
-      Hostname of the coordinator to connect to.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-N</></term>
-      <term><option>--no-clean</></term>
-      <listitem>
-      <para>
-       If this option is specified, <application>pgxc_clean</> will
-       not perform the cleanup.  It just investigates transaction status.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-o <replaceable class="parameter">filename</replaceable></></term>
-      <term><option>--output=<replaceable class="parameter">filename</replaceable></></term>
-      <listitem>
-      <para>
-       Name of the file where <application>pgxc_clean</> output will
-       be written.  If not specified, stdout and stderr will be used.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-p <replaceable class="parameter">port_number</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port_number</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies the port number of the coordinator.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-q</></term>
-      <term><option>--quiet</></term>
-      <listitem>
-      <para>
-       Surpress messages as much as possible.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-s</></term>
-      <term><option>--status</></term>
-      <listitem>
-      <para>
-       Prints investigated two phase commit status.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-      <para>
-       User name to use.   You must be a superuser of the database.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-v</></term>
-      <term><option>--verbose</></term>
-      <listitem>
-      <para>
-       Write as much information as possible.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-V</></term>
-      <term><option>--version</></term>
-      <listitem>
-      <para>
-       Writes the version of the utility and exits.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-w</></term>
-     <term><option>--no-password</></term>
-     <listitem>
-      <para>
-       Never issue a password prompt.  If the server requires password
-       authentication and a password is not available by other means
-       such as a <filename>.pgpass</filename> file, the connection
-       attempt will fail.  This option can be useful in batch jobs and
-       scripts where no user is present to enter a password.
-      </para>
-
-      <para>
-       Note that this option will remain set for the entire session,
-       and so it affects uses of the meta-command
-       <command>\connect</command> as well as the initial connection attempt.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-      <para>
-       Force <application>psql</application> to prompt for a
-       password before connecting to a database.
-      </para>
-
-      <para>
-       This option is never essential, since <application>psql</application>
-       will automatically prompt for a password if the server demands
-       password authentication.  However, <application>psql</application>
-       will waste a connection attempt finding out that the server wants a
-       password.  In some cases it is worth typing <option>-W</> to avoid
-       the extra connection attempt.
-      </para>
-
-      <para>
-       Note that this option will remain set for the entire session,
-       and so it affects uses of the meta-command
-       <command>\connect</command> as well as the initial connection attempt.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-?</></term>
-      <term><option>--help</></term>
-      <listitem>
-      <para>
-      Show help about <application>psql</application> command line
-      arguments, and exit.
-      </para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/pgxc_ddl.sgmlin b/doc-xc/src/sgml/ref/pgxc_ddl.sgmlin
deleted file mode 100644
index 4397805dee..0000000000
--- a/doc-xc/src/sgml/ref/pgxc_ddl.sgmlin
+++ /dev/null
@@ -1,313 +0,0 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/initdb.sgml,v 1.47 2010/04/03 07:23:01 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-PGXC-DDL">
- <refmeta>
-  <refentrytitle>pgxc_ddl</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pgxc_ddl</refname>
-  <refpurpose>
-   Coordinator catalog table synchronization and DDL treatment module
-  </refpurpose>
- </refnamediv>
-
- <indexterm zone="app-pgxc-ddl">
-  <primary>pgxc_ddl</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pgxc_ddl</command>
-   <arg rep="repeat"><replaceable>option</></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-PGXC-DDL-1">
-  <title>
-   Description
-  </title>
-&xconly
-  <para>
-   pgxc_ddl is used to synchronize all coordinator catalog tables from
-one chosen by a user. It is also possible to launch a DDL on one
-coordinator, and then to synchronize all the coordinator catalog
-tables from the catalog table of the coordinator having received the
-DDL.  Copy method is cold-based. All the coordinators are stopped,
-catalog files are copied, then all the coordinators are restarted.
-  </para>
-
-  <para>
-   Since <productname>Postgres-XC</productname> 0.9.3, DDL are
-   synchronized automatically on all the nodes of the
-   cluster, <command>pgxc_ddl</command> is let on purpose of future
-   feature development.
-  </para>
-
-  <para>
-   Since <productname>Postgres-XC</productname> 0.9.4, pgxc_ddl and
-   pgxc.conf are not anymore installed by default.  Scripts are saved
-   in the folder <filename>src/pgxc/bin/pgxc_ddl</filename>.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Options</title>
-
-  <para>
-   Options are specified with preceding '<literal>-</literal>', each
-   option may be associated with a value.
-  </para>
-
-  <para>
-   Options are as follows:
-  </para>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><option>D</option></term>
-     <listitem>
-      <para>
-       Specify <filename>pgxc.conf</filename> folder, for
-       characteristics of all the coordinators.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>l</option></term>
-     <listitem>
-      <para>
-       Specify application folder, in case <varname>PATH</varname> is not defined.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>f</option></term>
-     <listitem>
-      <para>
-       Specify DDL file location.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>d</option></term>
-     <listitem>
-      <para>
-       Database name.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>n</option></term>
-     <listitem>
-      <para>
-       Coordinator number. Coordinator chosen corresponds to the one
-       defined in <filename>pgxc.conf</filename> at the nth place.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>t</option></term>
-     <listitem>
-      <para>
-       Specify temporary folder where to copy the configuration files
-       postgresql.conf and pg_hba.conf for each coordinator.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-
-  <para>
-   <command>gtm_ctl</command> issues the following keywords to select
-   operations on <command>gtm</command>
-   and <command>gtm_proxy</command>.
-  </para>
-
-  <para>
-   <variablelist>
-
-    <varlistentry>
-     <term><option>start</option></term>
-     <listitem>
-      <para>
-       Start a GTM/GTM proxy instance.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>restart</option></term>
-     <listitem>
-      <para>
-       Restart a GTM/GTM proxy instance.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>stop</option></term>
-     <listitem>
-      <para>
-       Stop a GTM/GTM proxy instance.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>status</option></term>
-     <listitem>
-      <para>
-       Look at the status of GTM instance. If active, 1 is printed. If
-       standby, 0 is printed.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>promote</option></term>
-     <listitem>
-      <para>
-       Promote a GTM instance as active.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>reconnect</option></term>
-     <listitem>
-      <para>
-       Reconnect a GTM Proxy to another GTM instance.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-
-  <para>
-   Typically, you can issue the following command to start <command>gtm</command>/
-<programlisting>
-gtm_ctl start -S gtm -D datafolder
-</programlisting>
-  </para>
-
-  <para>
-   Or <command>gtm_proxy</command>:
-<programlisting>
-gtm_ctl start -S gtm_proxy -D datafolder_proxy
-</programlisting>
-  </para>
-
-  <para>
-   Promote a GTM as active:
-<programlisting>
-gtm_ctl promote -S gtm -D datafolder
-</programlisting>
-  </para>
-
-  <para>
-   Reconnect a GTM proxy to another GTM instance:
-<programlisting>
-gtm_ctl reconnect -S gtm_proxy -D datafolder_proxy -o '-s hostname -t port_number'
-</programlisting>
-  </para>
-
-  <para>
-   Look at the status of a GTM server:
-<programlisting>
-gtm_ctl status -S gtm -D datafolder
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-APP-PGXC-DDL-2">
-  <title>
-   Configuration
-  </title>
-&xconly
-  <para>
-   Because <command>pgxc_ddl</command> requires access to coordinator
-   configuration file and data folders, the following parameters have
-   to be set in <filename>pgxc.conf</filename>:
-  </para>
-
-  <table>
-   <title><filename>pgxc.conf</filename> entries</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><varname>coordinator_ports</varname></entry>
-      <entry>string</entry>
-      <entry>
-       Specify the port number of all the coordinators. Maintain the
-       order of the value same as those in coordinator_hosts. It is
-       necessary to specify a number of ports equal to the number of
-       hosts. A comma separator is also necessary.
-      </entry>
-     </row>
-
-     <row>
-      <entry><varname>coordinator_folders</varname></entry>
-      <entry>string</entry>
-      <entry>
-       Specify the data folders of all the coordinators. Maintain the
-       order of the value same as those in coordinator_hosts. It is
-       necessary to specify a number of data folders equal to the
-       number of hosts. A comma separator is also necessary.
-      </entry>
-     </row>
-
-     <row>
-      <entry><varname>coordinator_hosts</varname></entry>
-      <entry>string</entry>
-      <entry>
-       Specify the host name or IP address of coordinator. Separate
-       each value with comma.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <note>
-   <para>
-    About the temporary folder, this one has the name chosen by the
-    user. As an extension name, the PID of the shell script is
-    added. This folder is by definition in /tmp. The user can choose
-    the name freely.
-   </para>
-  </note>
-
-  <note>
-   <para>
-    Configuration files of coordinators that have their catalog files
-    changed are defined with an extension name postgresql.conf.number,
-    "number" being the number of t coordinator in the order defined
-    in <filename>pgxc.conf</filename>.
-   </para>
-  </note>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/postgres-ref.sgmlin b/doc-xc/src/sgml/ref/postgres-ref.sgmlin
deleted file mode 100644
index 835bddca14..0000000000
--- a/doc-xc/src/sgml/ref/postgres-ref.sgmlin
+++ /dev/null
@@ -1,1014 +0,0 @@
-<!--
-doc/src/sgml/ref/postgres-ref.sgml
-PostgreSQL documentation
--->
-
-<refentry id="app-postgres">
- <refmeta>
-  <refentrytitle><application>postgres</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
-<!## PG>
- <refnamediv>
-  <refname>postgres</refname>
-  <refpurpose><productname>PostgreSQL</productname> database server</refpurpose>
- </refnamediv>
-<!## end>
-<!## XC>
- <refnamediv>
-  <refname>postgres</refname>
-  <refpurpose><productname>Postgres-XC</productname> database server</refpurpose>
- </refnamediv>
-<!## end>
-<!## XL>
- <refnamediv>
-  <refname>postgres</refname>
-  <refpurpose><productname>Postgres-XL</productname> database server</refpurpose>
- </refnamediv>
-<!## end>
-
- <indexterm zone="app-postgres">
-  <primary>postgres</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>postgres</command>
-   <arg rep="repeat"><replaceable>option</></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>postgres</command> is the
-<!## PG>
-   <productname>PostgreSQL</productname> database server.  In order
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> database server.  In order
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> database server.  In order
-<!## end>
-   for a client application to access a database it connects (over a
-   network or locally) to a running <command>postgres</command> instance.
-   The <command>postgres</command> instance then starts a separate server
-   process to handle the connection.
-  </para>
-
-  <para>
-   One <command>postgres</command> instance always manages the data of
-   exactly one database cluster.  A database cluster is a collection
-   of databases that is stored at a common file system location (the
-   <quote>data area</quote>).  More than one
-   <command>postgres</command> instance can run on a system at one
-   time, so long as they use different data areas and different
-   communication ports (see below).  When
-   <command>postgres</command> starts it needs to know the location
-   of the data area.  The location must be specified by the
-   <option>-D</option> option or the <envar>PGDATA</envar> environment
-   variable; there is no default.  Typically, <option>-D</option> or
-   <envar>PGDATA</envar> points directly to the data area directory
-   created by <xref linkend="app-initdb">.  Other possible file layouts are
-   discussed in <xref linkend="runtime-config-file-locations">.
-  </para>
-
-  <para>
-   By default <command>postgres</command> starts in the
-   foreground and prints log messages to the standard error stream.  In
-   practical applications <command>postgres</command>
-   should be started as a background process, perhaps at boot time.
-  </para>
-
-  <para>
-   The <command>postgres</command> command can also be called in
-   single-user mode.  The primary use for this mode is during
-   bootstrapping by <xref linkend="app-initdb">.  Sometimes it is used
-   for debugging or disaster recovery;  note that running a single-user
-   server is not truly suitable for debugging the server, since no
-   realistic interprocess communication and locking will happen.
-   When invoked in single-user
-   mode from the shell, the user can enter queries and the results
-   will be printed to the screen, but in a form that is more useful
-   for developers than end users.  In the single-user mode,
-   the session user will be set to the user with ID 1, and implicit
-   superuser powers are granted to this user.
-   This user does not actually have to exist, so the single-user mode
-   can be used to manually recover from certain
-   kinds of accidental damage to the system catalogs.
-  </para>
- </refsect1>
-
- <refsect1 id="app-postgres-options">
-  <title>Options</title>
-&common;
-   <para>
-    <command>postgres</command> accepts the following command-line
-    arguments.  For a detailed discussion of the options consult <xref
-    linkend="runtime-config">.  You can save typing most of these
-    options by setting up a configuration file.  Some (safe) options
-    can also be set from the connecting client in an
-    application-dependent way to apply only for that session.  For
-    example, if the environment variable <envar>PGOPTIONS</envar> is
-    set, then <application>libpq</>-based clients will pass that
-    string to the server, which will interpret it as
-    <command>postgres</command> command-line options.
-   </para>
-
-   <refsect2>
-    <title>General Purpose</title>
-
-&common;
-    <variablelist>
-     <varlistentry>
-      <term><option>-A 0|1</option></term>
-      <listitem>
-       <para>
-        Enables run-time assertion checks, which is a debugging aid to
-        detect programming mistakes.  This option is only available if
-<!## PG>
-        assertions were enabled when <productname>PostgreSQL</> was
-<!## end>
-<!## XC>
-        assertions were enabled when <productname>Postgres-XC</> was
-<!## end>
-<!## XL>
-        assertions were enabled when <productname>Postgres-XL</> was
-<!## end>
-        compiled. If so, the default is on.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-B <replaceable class="parameter">nbuffers</replaceable></option></term>
-      <listitem>
-       <para>
-        Sets the number of shared buffers for use by the server
-        processes.  The default value of this parameter is chosen
-        automatically by <application>initdb</application>.
-        Specifying this option is equivalent to setting the
-        <xref linkend="guc-shared-buffers"> configuration parameter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-<!## XC>
-     <varlistentry>
-      <term><option>--coordinator</option></term>
-      <listitem>
-&xconly;
-       <para>
-        Specifies postgres server should run as a Coordinator.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-<!## XL>
-     <varlistentry>
-      <term><option>--coordinator</option></term>
-      <listitem>
-&xlonly;
-       <para>
-        Specifies postgres server should run as a Coordinator.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-
-     <varlistentry>
-      <term><option>-c <replaceable>name</replaceable>=<replaceable>value</replaceable></option></term>
-      <listitem>
-       <para>
-        Sets a named run-time parameter. The configuration parameters
-<!## PG>
-        supported by <productname>PostgreSQL</productname> are
-<!## end>
-<!## XC>
-        supported by <productname>Postgres-XC</productname> are
-<!## end>
-<!## XL>
-        supported by <productname>Postgres-XL</productname> are
-<!## end>
-        described in <xref linkend="runtime-config">. Most of the
-        other command line options are in fact short forms of such a
-        parameter assignment.  <option>-c</> can appear multiple times
-        to set multiple parameters.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-d <replaceable>debug-level</replaceable></option></term>
-      <listitem>
-       <para>
-        Sets the debug level.  The higher this value is set, the more
-        debugging output is written to the server log.  Values are
-        from 1 to 5.  It is also possible to pass <literal>-d
-        0</literal> for a specific session, which will prevent the
-        server log level of the parent <command>postgres</> process from being
-        propagated to this session.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-D <replaceable class="parameter">datadir</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the file system location of the data directory or
-        configuration file(s).  See
-        <xref linkend="runtime-config-file-locations"> for details.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</option></term>
-      <listitem>
-       <para>
-        Sets the default date style to <quote>European</quote>, that is
-        <literal>DMY</> ordering of input date fields.  This also causes
-        the day to be printed before the month in certain date output formats.
-        See <xref linkend="datatype-datetime"> for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-F</option></term>
-      <listitem>
-       <para>
-        Disables <function>fsync</function> calls for improved
-        performance, at the risk of data corruption in the event of a
-        system crash.  Specifying this option is equivalent to
-        disabling the <xref linkend="guc-fsync"> configuration
-        parameter. Read the detailed documentation before using this!
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">hostname</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the IP host name or address on which
-        <command>postgres</command> is to listen for TCP/IP
-        connections from client applications.  The value can also be a
-        comma-separated list of addresses, or <literal>*</> to specify
-        listening on all available interfaces.  An empty value
-        specifies not listening on any IP addresses, in which case
-        only Unix-domain sockets can be used to connect to the
-        server.  Defaults to listening only on
-        <systemitem class="systemname">localhost</systemitem>.
-        Specifying this option is equivalent to setting the <xref
-        linkend="guc-listen-addresses"> configuration parameter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-i</option></term>
-      <listitem>
-       <para>
-        Allows remote clients to connect via TCP/IP (Internet domain)
-        connections.  Without this option, only local connections are
-        accepted.  This option is equivalent to setting
-        <varname>listen_addresses</> to <literal>*</> in
-        <filename>postgresql.conf</> or via <option>-h</>.
-       </para>
-       <para>
-        This option is deprecated since it does not allow access to the
-        full functionality of <xref linkend="guc-listen-addresses">.
-        It's usually better to set <varname>listen_addresses</> directly.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-k <replaceable class="parameter">directory</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the directory of the Unix-domain socket on which
-        <command>postgres</command> is to listen for
-        connections from client applications.  The default is normally
-        <filename>/tmp</filename>, but can be changed at build time.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-l</option></term>
-      <listitem>
-       <para>
-        Enables secure connections using <acronym>SSL</acronym>.
-<!## PG>
-        <productname>PostgreSQL</productname> must have been compiled with
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> must have been compiled with
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> must have been compiled with
-<!## end>
-        support for <acronym>SSL</acronym> for this option to be
-        available. For more information on using <acronym>SSL</acronym>,
-        refer to <xref linkend="ssl-tcp">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-N <replaceable class="parameter">max-connections</replaceable></option></term>
-      <listitem>
-       <para>
-        Sets the maximum number of client connections that this
-        server will accept.  The default value of this parameter is chosen
-        automatically by <application>initdb</application>.
-        Specifying this option is equivalent to setting the
-        <xref linkend="guc-max-connections"> configuration parameter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o <replaceable class="parameter">extra-options</replaceable></option></term>
-      <listitem>
-       <para>
-        The command-line-style options specified in <replaceable
-        class="parameter">extra-options</replaceable> are passed to
-        all server processes started by this
-        <command>postgres</command> process.  If the option string contains
-        any spaces, the entire string must be quoted.
-       </para>
-
-       <para>
-        The use of this option is obsolete; all command-line options
-        for server processes can be specified directly on the
-        <command>postgres</command> command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the TCP/IP port or local Unix domain socket file
-        extension on which <command>postgres</command>
-        is to listen for connections from client applications.
-        Defaults to the value of the <envar>PGPORT</envar> environment
-        variable, or if <envar>PGPORT</envar> is not set, then
-        defaults to the value established during compilation (normally
-        5432).  If you specify a port other than the default port,
-        then all client applications must specify the same port using
-        either command-line options or <envar>PGPORT</envar>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option></term>
-      <listitem>
-       <para>
-        Print time information and other statistics at the end of each command.
-        This is useful for benchmarking or for use in tuning the number of
-        buffers.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-S</option> <replaceable class="parameter">work-mem</replaceable></term>
-      <listitem>
-       <para>
-        Specifies the amount of memory to be used by internal sorts and hashes
-        before resorting to temporary disk files.  See the description of the
-        <varname>work_mem</> configuration parameter in <xref
-        linkend="runtime-config-resource-memory">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-<!## XC>
-     <varlistentry>
-      <term><option>--datanode</option></term>
-      <listitem>
-&xconly;
-       <para>
-        Specifies postgres server should run as a Datanode.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-<!## XL>
-     <varlistentry>
-      <term><option>--datanode</option></term>
-      <listitem>
-&xlonly;
-       <para>
-        Specifies postgres server should run as a Datanode.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-
-     <varlistentry>
-      <term><option>--<replaceable>name</replaceable>=<replaceable>value</replaceable></option></term>
-      <listitem>
-       <para>
-        Sets a named run-time parameter; a shorter form of
-        <option>-c</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>--describe-config</option></term>
-      <listitem>
-       <para>
-        This option dumps out the server's internal configuration variables,
-        descriptions, and defaults in tab-delimited <command>COPY</> format.
-        It is designed primarily for use by administration tools.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect2>
-
-   <refsect2>
-    <title>Semi-internal Options</title>
-&common;
-    <para>
-     The options described here are used
-     mainly for debugging purposes, and in some cases to assist with
-     recovery of severely damaged databases. There should be no reason
-     to use them in a production database setup.  They are listed
-<!## PG>
-     here only for use by <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-     here only for use by <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-     here only for use by <productname>Postgres-XL</productname>
-<!## end>
-     system developers.  Furthermore, these options might
-     change or be removed in a future release without notice.
-    </para>
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-f</option> <literal>{ s | i | m | n | h }</literal></term>
-      <listitem>
-       <para>
-        Forbids the use of particular scan and join methods:
-        <literal>s</literal> and <literal>i</literal>
-        disable sequential and index scans respectively, while
-        <literal>n</literal>, <literal>m</literal>, and <literal>h</literal>
-        disable nested-loop, merge and hash joins respectively.
-       </para>
-
-       <para>
-        Neither sequential scans nor nested-loop joins can be disabled
-        completely; the <literal>-fs</literal> and
-        <literal>-fn</literal> options simply discourage the optimizer
-        from using those plan types if it has any other alternative.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-n</option></term>
-      <listitem>
-       <para>
-        This option is for debugging problems that cause a server
-        process to die abnormally.  The ordinary strategy in this
-        situation is to notify all other server processes that they
-        must terminate and then reinitialize the shared memory and
-        semaphores.  This is because an errant server process could
-        have corrupted some shared state before terminating.  This
-        option specifies that <command>postgres</command> will
-        not reinitialize shared data structures.  A knowledgeable
-        system programmer can then use a debugger to examine shared
-        memory and semaphore state.
-       </para>
-     </listitem>
-    </varlistentry>
-
-     <varlistentry>
-      <term><option>-O</option></term>
-      <listitem>
-       <para>
-        Allows the structure of system tables to be modified.  This is
-        used by <command>initdb</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-P</option></term>
-      <listitem>
-       <para>
-        Ignore system indexes when reading system tables, but still update
-        the indexes when modifying the tables.  This is useful when
-        recovering from damaged system indexes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t</option> <literal>pa[rser] | pl[anner] | e[xecutor]</literal></term>
-      <listitem>
-       <para>
-        Print timing statistics for each query relating to each of the
-        major system modules.  This option cannot be used together
-        with the <option>-s</option> option.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-T</option></term>
-      <listitem>
-       <para>
-        This option is for debugging problems that cause a server
-        process to die abnormally.  The ordinary strategy in this
-        situation is to notify all other server processes that they
-        must terminate and then reinitialize the shared memory and
-        semaphores.  This is because an errant server process could
-        have corrupted some shared state before terminating.  This
-        option specifies that <command>postgres</command> will
-        stop all other server processes by sending the signal
-        <literal>SIGSTOP</literal>, but will not cause them to
-        terminate.  This permits system programmers to collect core
-        dumps from all server processes by hand.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-v</option> <replaceable class="parameter">protocol</replaceable></term>
-      <listitem>
-       <para>
-        Specifies the version number of the frontend/backend protocol
-        to be used for a particular session.  This option is for
-        internal use only.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option> <replaceable class="parameter">seconds</replaceable></term>
-      <listitem>
-       <para>
-        A delay of this many seconds occurs when a new server process
-        is started, after it conducts the authentication procedure.
-        This is intended to give an opportunity to attach to the
-        server process with a debugger.
-       </para>
-      </listitem>
-     </varlistentry>
-
-<!## XC>
-     <varlistentry>
-      <term><option>--localxid</option></term>
-      <listitem>
-       &xconly;
-       <para>
-        Use local transaction IDs rather than GXID. This option applies
-        only to <productname>Postgres-XC</productname>. It is only
-        used by initdb. Explicit use of this option may cause
-        database inconsistency.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-<!## XL>
-     <varlistentry>
-      <term><option>--localxid</option></term>
-      <listitem>
-       &xlonly;
-       <para>
-        Use local transaction IDs rather than GXID. This option applies
-        only to <productname>Postgres-XL</productname>. It is only
-        used by initdb. Explicit use of this option may cause
-        database inconsistency.
-       </para>
-      </listitem>
-     </varlistentry>
-<!## end>
-    </variablelist>
-   </refsect2>
-
-   <refsect2>
-    <title>Options for Single-User Mode</title>
-
-    <para>
-     The following options only apply to the single-user mode.
-    </para>
-
-    <variablelist>
-     <varlistentry>
-      <term><option>--single</option></term>
-      <listitem>
-       <para>
-        Selects the single-user mode.  This must be the first argument
-        on the command line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">database</replaceable></term>
-      <listitem>
-       <para>
-        Specifies the name of the database to be accessed.  This must be
-        the last argument on the command line.  If it is
-        omitted it defaults to the user name.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-E</option></term>
-      <listitem>
-       <para>
-        Echo all commands.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-j</option></term>
-      <listitem>
-       <para>
-        Disables use of newline as a statement delimiter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-r</option> <replaceable class="parameter">filename</replaceable></term>
-      <listitem>
-       <para>
-        Send all server log output to <replaceable
-        class="parameter">filename</replaceable>.  In normal multiuser
-        mode, this option is ignored, and <systemitem>stderr</> is
-        used by all processes.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Environment</title>
-&common;
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGCLIENTENCODING</envar></term>
-
-    <listitem>
-     <para>
-      Default character encoding used by clients.  (The clients can
-      override this individually.)  This value can also be set in the
-      configuration file.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PGDATA</envar></term>
-
-    <listitem>
-     <para>
-      Default data directory location
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PGDATESTYLE</envar></term>
-
-    <listitem>
-     <para>
-      Default value of the <xref linkend="guc-datestyle"> run-time
-      parameter.  (The use of this environment variable is deprecated.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PGPORT</envar></term>
-
-    <listitem>
-     <para>
-      Default port number (preferably set in the configuration file)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>TZ</envar></term>
-
-    <listitem>
-     <para>
-      Server time zone
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </refsect1>
-
- <refsect1>
-   <title>Diagnostics</title>
-&common;
-   <para>
-    A failure message mentioning <literal>semget</> or
-    <literal>shmget</> probably indicates you need to configure your
-    kernel to provide adequate shared memory and semaphores.  For more
-    discussion see <xref linkend="kernel-resources">.  You might be able
-    to postpone reconfiguring your kernel by decreasing <xref
-    linkend="guc-shared-buffers"> to reduce the shared memory
-<!## PG>
-    consumption of <productname>PostgreSQL</>, and/or by reducing
-<!## end>
-<!## XC>
-    consumption of <productname>Postgres-XC</>, and/or by reducing
-<!## end>
-<!## XL>
-    consumption of <productname>Postgres-XL</>, and/or by reducing
-<!## end>
-    <xref linkend="guc-max-connections"> to reduce the semaphore
-    consumption.
-   </para>
-
-   <para>
-    A failure message suggesting that another server is already running
-    should be checked carefully, for example by using the command
-<screen>
-<prompt>$</prompt> <userinput>ps ax | grep postgres</userinput>
-</screen>
-        or
-<screen>
-<prompt>$</prompt> <userinput>ps -ef | grep postgres</userinput>
-</screen>
-    depending on your system.  If you are certain that no conflicting
-    server is running, you can remove the lock file mentioned in the
-    message and try again.
-   </para>
-
-   <para>
-    A failure message indicating inability to bind to a port might
-    indicate that that port is already in use by some
-<!## PG>
-    non-<productname>PostgreSQL</productname> process.  You might also
-<!## end>
-<!## XC>
-    non-<productname>Postgres-XC</productname> process.  You might also
-<!## end>
-<!## XL>
-    non-<productname>Postgres-XL</productname> process.  You might also
-<!## end>
-    get this error if you terminate <command>postgres</command>
-    and immediately restart it using the same port; in this case, you
-    must simply wait a few seconds until the operating system closes
-    the port before trying again.  Finally, you might get this error if
-    you specify a port number that your operating system considers to
-    be reserved.  For example, many versions of Unix consider port
-    numbers under 1024 to be <quote>trusted</quote> and only permit
-    the Unix superuser to access them.
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-&common;
-  <para>
-   The utility command <xref linkend="app-pg-ctl"> can be used to
-   start and shut down the <command>postgres</command> server
-   safely and comfortably.
-  </para>
-
-  <para>
-   If at all possible, <emphasis>do not</emphasis> use
-   <literal>SIGKILL</literal> to kill the main
-   <command>postgres</command> server.  Doing so will prevent
-   <command>postgres</command> from freeing the system
-   resources (e.g., shared memory and semaphores) that it holds before
-   terminating.  This might cause problems for starting a fresh
-   <command>postgres</command> run.
-  </para>
-
-  <para>
-   To terminate the <command>postgres</command> server normally, the
-   signals <literal>SIGTERM</literal>, <literal>SIGINT</literal>, or
-   <literal>SIGQUIT</literal> can be used.  The first will wait for
-   all clients to terminate before quitting, the second will
-   forcefully disconnect all clients, and the third will quit
-   immediately without proper shutdown, resulting in a recovery run
-   during restart.
-  </para>
-
-  <para>
-   The <literal>SIGHUP</literal> signal will reload
-   the server configuration files.  It is also possible to send
-   <literal>SIGHUP</literal> to an individual server process, but that
-   is usually not sensible.
-  </para>
-
-  <para>
-   To cancel a running query, send the <literal>SIGINT</literal> signal
-   to the process running that command.
-  </para>
-
-  <para>
-   The <command>postgres</command> server uses <literal>SIGTERM</literal>
-   to tell subordinate server processes to quit normally and
-   <literal>SIGQUIT</literal> to terminate without the normal cleanup.
-   These signals <emphasis>should not</emphasis> be used by users.  It
-   is also unwise to send <literal>SIGKILL</literal> to a server
-   process &mdash; the main <command>postgres</command> process will
-   interpret this as a crash and will force all the sibling processes
-   to quit as part of its standard crash-recovery procedure.
-  </para>
- </refsect1>
-
-<!## PG>
- <refsect1 id="app-postgres-bugs">
-  <title>Bugs</title>
-  <para>
-   The <option>--</> options will not work on <systemitem
-   class="osname">FreeBSD</> or <systemitem class="osname">OpenBSD</>.
-   Use <option>-c</> instead. This is a bug in the affected operating
-   systems; a future release of <productname>PostgreSQL</productname>
-   will provide a workaround if this is not fixed.
-  </para>
- </refsect1>
-<!## end>
-
- <refsect1>
-  <title>Usage</title>
-&common;
-   <para>
-    To start a single-user mode server, use a command like
-<screen>
-<userinput>postgres --single -D /usr/local/pgsql/data <replaceable>other-options</> my_database</userinput>
-</screen>
-    Provide the correct path to the database directory with <option>-D</>, or
-    make sure that the environment variable <envar>PGDATA</> is set.
-    Also specify the name of the particular database you want to work in.
-   </para>
-
-   <para>
-    Normally, the single-user mode server treats newline as the command
-    entry terminator; there is no intelligence about semicolons,
-    as there is in <application>psql</>.  To continue a command
-    across multiple lines, you must type backslash just before each
-    newline except the last one.
-   </para>
-
-   <para>
-    But if you use the <option>-j</> command line switch, then newline does
-    not terminate command entry.  In this case, the server will read the standard input
-    until the end-of-file (<acronym>EOF</>) marker, then
-    process the input as a single command string.  Backslash-newline is not
-    treated specially in this case.
-   </para>
-
-   <para>
-    To quit the session, type <acronym>EOF</acronym>
-    (<keycombo action="simul"><keycap>Control</><keycap>D</></>, usually).
-    If you've
-    used <option>-j</>, two consecutive <acronym>EOF</>s are needed to exit.
-   </para>
-
-   <para>
-    Note that the single-user mode server does not provide sophisticated
-    line-editing features (no command history, for example). 
-    Single-User mode also does not do any background processing, like
-    automatic checkpoints.
-
-   </para>
- </refsect1>
-
- <refsect1 id="app-postgres-examples">
-  <title>Examples</title>
-
-  <para>
-<!## PG>
-   To start <command>postgres</command> in the background
-<!## end>
-<!## XC>
-&xconly;
-   To start <command>postgres</command> as a Datanode in the background
-<!## end>
-<!## XL>
-&xlonly;
-   To start <command>postgres</command> as a Datanode in the background
-<!## end>
-   using default values, type:
-
-<!## PG>
-<screen>
-<prompt>$</prompt> <userinput>nohup postgres &gt;logfile 2&gt;&amp;1 &lt;/dev/null &amp;</userinput>
-</screen>
-<!## end>
-<!## XC>
-<screen>
-<prompt>$</prompt> <userinput>nohup postgres --datanode &gt;logfile 2&gt;&amp;1 &lt;/dev/null &amp;</userinput>
-</screen>
-<!## end>
-<!## XL>
-<screen>
-<prompt>$</prompt> <userinput>nohup postgres --datanode &gt;logfile 2&gt;&amp;1 &lt;/dev/null &amp;</userinput>
-</screen>
-<!## end>
-  </para>
-
-  <para>
-<!## PG>
-   To start <command>postgres</command> with a specific
-<!## end>
-<!## XC>
-   To start <command>postgres</command> as a Coordinator with a specific
-<!## end>
-<!## XL>
-   To start <command>postgres</command> as a Coordinator with a specific
-<!## end>
-   port, e.g. 1234:
-<!## PG>
-<screen>
-<prompt>$</prompt> <userinput>postgres -p 1234</userinput>
-</screen>
-<!## end>
-<!## XC>
-<screen>
-<prompt>$</prompt> <userinput>postgres --coordinator -p 1234</userinput>
-</screen>
-<!## end>
-<!## XL>
-<screen>
-<prompt>$</prompt> <userinput>postgres --coordinator -p 1234</userinput>
-</screen>
-<!## end>
-   To connect to this server using <application>psql</>, specify this port with the -p option:
-<screen>
-<prompt>$</prompt> <userinput>psql -p 1234</userinput>
-</screen>
-   or set the environment variable <envar>PGPORT</envar>:
-<screen>
-<prompt>$</prompt> <userinput>export PGPORT=1234</userinput>
-<prompt>$</prompt> <userinput>psql</userinput>
-</screen>
-  </para>
-
-  <para>
-   Named run-time parameters can be set in either of these styles:
-<!## PG>
-<screen>
-<prompt>$</prompt> <userinput>postgres -c work_mem=1234</userinput>
-<prompt>$</prompt> <userinput>postgres --work-mem=1234</userinput>
-</screen>
-<!## end>
-<!## XC>
-<screen>
-<prompt>$</prompt> <userinput>postgres --coordinator -c work_mem=1234</userinput>
-<prompt>$</prompt> <userinput>postgres --coordinator --work-mem=1234</userinput>
-</screen>
-<!## end>
-<!## XL>
-<screen>
-<prompt>$</prompt> <userinput>postgres --coordinator -c work_mem=1234</userinput>
-<prompt>$</prompt> <userinput>postgres --coordinator --work-mem=1234</userinput>
-</screen>
-<!## end>
-   Either form overrides whatever setting might exist for
-   <varname>work_mem</> in <filename>postgresql.conf</>.  Notice that
-   underscores in parameter names can be written as either underscore
-   or dash on the command line.  Except for short-term experiments,
-   it's probably better practice to edit the setting in
-   <filename>postgresql.conf</> than to rely on a command-line switch
-   to set a parameter.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <para>
-   <xref linkend="app-initdb">,
-   <xref linkend="app-pg-ctl">
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/postmaster.sgmlin b/doc-xc/src/sgml/ref/postmaster.sgmlin
deleted file mode 100644
index 1de541d00e..0000000000
--- a/doc-xc/src/sgml/ref/postmaster.sgmlin
+++ /dev/null
@@ -1,54 +0,0 @@
-<!--
-doc/src/sgml/ref/postmaster.sgml
-PostgreSQL documentation
--->
-
-<refentry id="app-postmaster">
- <refmeta>
-  <refentrytitle><application>postmaster</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname id="postmaster-ref">postmaster</refname>
-<!## PG>
-  <refpurpose><productname>PostgreSQL</productname> database server</refpurpose>
-<!## end>
-<!## XC>
-  <refpurpose><productname>Postgres-XC</productname> database server for Coordinator or Datanode</refpurpose>
-<!## end>
-<!## XL>
-  <refpurpose><productname>Postgres-XL</productname> database server for Coordinator or Datanode</refpurpose>
-<!## end>
- </refnamediv>
-
- <indexterm zone="app-postmaster">
-  <primary>postmaster</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>postmaster</command>
-   <arg rep="repeat"><replaceable>option</></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>postmaster</command> is a deprecated alias of <command>postgres</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <para>
-   <xref linkend="app-postgres">
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/prepare.sgmlin b/doc-xc/src/sgml/ref/prepare.sgmlin
deleted file mode 100644
index 731c5bb231..0000000000
--- a/doc-xc/src/sgml/ref/prepare.sgmlin
+++ /dev/null
@@ -1,205 +0,0 @@
-<!--
-doc/src/sgml/ref/prepare.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-PREPARE">
- <refmeta>
-  <refentrytitle>PREPARE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>PREPARE</refname>
-  <refpurpose>prepare a statement for execution</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-prepare">
-  <primary>PREPARE</primary>
- </indexterm>
-
- <indexterm zone="sql-prepare">
-  <primary>prepared statements</primary>
-  <secondary>creating</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-PREPARE <replaceable class="PARAMETER">name</replaceable> [ ( <replaceable class="PARAMETER">data_type</replaceable> [, ...] ) ] AS <replaceable class="PARAMETER">statement</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-&common;
-  <para>
-   <command>PREPARE</command> creates a prepared statement. A prepared
-   statement is a server-side object that can be used to optimize
-   performance. When the <command>PREPARE</command> statement is
-   executed, the specified statement is parsed, rewritten, and
-   planned. When an <command>EXECUTE</command> command is subsequently
-   issued, the prepared statement need only be executed. Thus, the
-   parsing, rewriting, and planning stages are only performed once,
-   instead of every time the statement is executed.
-  </para>
-
-  <para>
-   Prepared statements can take parameters: values that are
-   substituted into the statement when it is executed. When creating
-   the prepared statement, refer to parameters by position, using
-   <literal>$1</>, <literal>$2</>, etc. A corresponding list of
-   parameter data types can optionally be specified. When a
-   parameter's data type is not specified or is declared as
-   <literal>unknown</literal>, the type is inferred from the context
-   in which the parameter is used (if possible). When executing the
-   statement, specify the actual values for these parameters in the
-   <command>EXECUTE</command> statement.  Refer to <xref
-   linkend="sql-execute"> for more
-   information about that.
-  </para>
-
-  <para>
-   Prepared statements only last for the duration of the current
-   database session. When the session ends, the prepared statement is
-   forgotten, so it must be recreated before being used again. This
-   also means that a single  prepared statement cannot be used by
-   multiple simultaneous database clients; however, each client can create
-   their own prepared statement to use.  The prepared statement can be
-   manually cleaned up using the <xref linkend="sql-deallocate"> command.
-  </para>
-
-  <para>
-   Prepared statements have the largest performance advantage when a
-   single session is being used to execute a large number of similar
-   statements. The performance difference will be particularly
-   significant if the statements are complex to plan or rewrite, for
-   example, if the query involves a join of many tables or requires
-   the application of several rules. If the statement is relatively simple
-   to plan and rewrite but relatively expensive to execute, the
-   performance advantage of prepared statements will be less noticeable.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      An arbitrary name given to this particular prepared
-      statement. It must be unique within a single session and is
-      subsequently used to execute or deallocate a previously prepared
-      statement.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">data_type</replaceable></term>
-    <listitem>
-     <para>
-      The data type of a parameter to the prepared statement.  If the
-      data type of a particular parameter is unspecified or is
-      specified as <literal>unknown</literal>, it will be inferred
-      from the context in which the parameter is used. To refer to the
-      parameters in the prepared statement itself, use
-      <literal>$1</literal>, <literal>$2</literal>, etc.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">statement</replaceable></term>
-    <listitem>
-     <para>
-      Any <command>SELECT</>, <command>INSERT</>, <command>UPDATE</>,
-      <command>DELETE</>, or <command>VALUES</> statement.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   In some situations, the query plan produced for a prepared
-   statement will be inferior to the query plan that would have been
-   chosen if the statement had been submitted and executed
-   normally. This is because when the statement is planned and the
-   planner attempts to determine the optimal query plan, the actual
-   values of any parameters specified in the statement are
-   unavailable. <productname>PostgreSQL</productname> collects
-   statistics on the distribution of data in the table, and can use
-   constant values in a statement to make guesses about the likely
-   result of executing the statement. Since this data is unavailable
-   when planning prepared statements with parameters, the chosen plan
-   might be suboptimal. To examine the query plan
-   <productname>PostgreSQL</productname> has chosen for a prepared
-   statement, use <xref linkend="sql-explain">.
-  </para>
-
-  <para>
-   For more information on query planning and the statistics collected
-   by <productname>PostgreSQL</productname> for that purpose, see
-   the <xref linkend="sql-analyze">
-   documentation.
-  </para>
-
-  <para>
-   You can see all available prepared statements of a session by querying the
-   <link linkend="view-pg-prepared-statements"><structname>pg_prepared_statements</structname></link>
-   system view.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-prepare-examples">
-  <title id="sql-prepare-examples-title">Examples</title>
-  <para>
-   Create a prepared statement for an <command>INSERT</command>
-   statement, and then execute it:
-<programlisting>
-PREPARE fooplan (int, text, bool, numeric) AS
-    INSERT INTO foo VALUES($1, $2, $3, $4);
-EXECUTE fooplan(1, 'Hunter Valley', 't', 200.00);
-</programlisting>
-  </para>
-
-  <para>
-   Create a prepared statement for a <command>SELECT</command>
-   statement, and then execute it:
-<programlisting>
-PREPARE usrrptplan (int) AS
-    SELECT * FROM users u, logs l WHERE u.usrid=$1 AND u.usrid=l.usrid
-    AND l.date = $2;
-EXECUTE usrrptplan(1, current_date);
-</programlisting>
-
-   Note that the data type of the second parameter is not specified,
-   so it is inferred from the context in which <literal>$2</> is used.
-  </para>
- </refsect1>
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard includes a <command>PREPARE</command> statement,
-   but it is only for use in embedded SQL. This version of the
-   <command>PREPARE</command> statement also uses a somewhat different
-   syntax.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-deallocate"></member>
-   <member><xref linkend="sql-execute"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/prepare_transaction.sgmlin b/doc-xc/src/sgml/ref/prepare_transaction.sgmlin
deleted file mode 100644
index 150f660393..0000000000
--- a/doc-xc/src/sgml/ref/prepare_transaction.sgmlin
+++ /dev/null
@@ -1,201 +0,0 @@
-<!--
-doc/src/sgml/ref/prepare_transaction.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-PREPARE-TRANSACTION">
- <refmeta>
-  <refentrytitle>PREPARE TRANSACTION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>PREPARE TRANSACTION</refname>
-  <refpurpose>prepare the current transaction for two-phase commit</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-prepare-transaction">
-  <primary>PREPARE TRANSACTION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-PREPARE TRANSACTION <replaceable class="PARAMETER">transaction_id</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>PREPARE TRANSACTION</command> prepares the current transaction
-   for two-phase commit. After this command, the transaction is no longer
-   associated with the current session; instead, its state is fully stored on
-   disk, and there is a very high probability that it can be committed
-   successfully, even if a database crash occurs before the commit is
-   requested.
-  </para>
-
-  <para>
-   Once prepared, a transaction can later be committed or rolled back
-   with <xref linkend="sql-commit-prepared">
-   or <xref linkend="sql-rollback-prepared">,
-   respectively.  Those commands can be issued from any session, not
-   only the one that executed the original transaction.
-  </para>
-
-  <para>
-   From the point of view of the issuing session, <command>PREPARE
-   TRANSACTION</command> is not unlike a <command>ROLLBACK</> command:
-   after executing it, there is no active current transaction, and the
-   effects of the prepared transaction are no longer visible.  (The effects
-   will become visible again if the transaction is committed.)
-  </para>
-
-  <para>
-   If the <command>PREPARE TRANSACTION</command> command fails for any
-   reason, it becomes a <command>ROLLBACK</>: the current transaction
-   is canceled.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">transaction_id</replaceable></term>
-    <listitem>
-     <para>
-      An arbitrary identifier that later identifies this transaction for
-      <command>COMMIT PREPARED</> or <command>ROLLBACK PREPARED</>.
-      The identifier must be written as a string literal, and must be
-      less than 200 bytes long.  It must not be the same as the identifier
-      used for any currently prepared transaction.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <command>PREPARE TRANSACTION</> is not intended for use in applications
-   or interactive sessions. Its purpose is to allow an external
-   transaction manager to perform atomic global transactions across multiple
-   databases or other transactional resources. Unless you're writing a
-   transaction manager, you probably shouldn't be using <command>PREPARE
-   TRANSACTION</>.
-  </para>
-
-  <para>
-   This command must be used inside a transaction block. Use <xref
-   linkend="sql-begin"> to start one.
-  </para>
-
-  <para>
-   It is not currently allowed to <command>PREPARE</> a transaction that
-   has executed any operations involving temporary tables,
-   created any cursors <literal>WITH HOLD</>, or executed
-   <command>LISTEN</> or <command>UNLISTEN</>.
-   Those features are too tightly
-   tied to the current session to be useful in a transaction to be prepared.
-  </para>
-
-  <para>
-   If the transaction modified any run-time parameters with <command>SET</>
-   (without the <literal>LOCAL</> option),
-   those effects persist after <command>PREPARE TRANSACTION</>, and will not
-   be affected by any later <command>COMMIT PREPARED</command> or
-   <command>ROLLBACK PREPARED</command>.  Thus, in this one respect
-   <command>PREPARE TRANSACTION</> acts more like <command>COMMIT</> than
-   <command>ROLLBACK</>.
-  </para>
-
-  <para>
-   All currently available prepared transactions are listed in the
-   <link linkend="view-pg-prepared-xacts"><structname>pg_prepared_xacts</structname></link>
-   system view.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   If the transaction is involved by more than one Datanode and/or
-   Coordinator, <command>COMMIT PREPARED</> will be propagated to
-   these nodes.
-  </para>
-
-&xconly;
-  <para>
-   Transaction id beginning with <literal>_$XC$</literal> is reserved by COORDINATOR for
-   internal use.   You cannot use this form of transaction_id externally.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   If the transaction is involved by more than one Datanode and/or
-   Coordinator, <command>COMMIT PREPARED</> will be propagated to
-   these nodes.
-  </para>
-
-&xlonly;
-  <para>
-   Transaction id beginning with <literal>_$XL$</literal> is reserved by COORDINATOR for
-   internal use.   You cannot use this form of transaction_id externally.
-  </para>
-<!## end>
-
-&common;
-  <caution>
-   <para>
-    It is unwise to leave transactions in the prepared state for a long time.
-    This will interfere with the ability of <command>VACUUM</> to reclaim
-    storage, and in extreme cases could cause the database to shut down
-    to prevent transaction ID wraparound (see <xref
-    linkend="vacuum-for-wraparound">).  Keep in mind also that the transaction
-    continues to hold whatever locks it held.  The intended usage of the
-    feature is that a prepared transaction will normally be committed or
-    rolled back as soon as an external transaction manager has verified that
-    other databases are also prepared to commit.
-   </para>
-
-   <para>
-    If you have not set up an external transaction manager to track prepared
-    transactions and ensure they get closed out promptly, it is best to keep
-    the prepared-transaction feature disabled by setting
-    <xref linkend="guc-max-prepared-transactions"> to zero.  This will
-    prevent accidental creation of prepared transactions that might then
-    be forgotten and eventually cause problems.
-   </para>
-  </caution>
- </refsect1>
-
- <refsect1 id="sql-prepare-transaction-examples">
-  <title id="sql-prepare-transaction-examples-title">Examples</title>
-  <para>
-   Prepare the current transaction for two-phase commit, using
-   <literal>foobar</> as the transaction identifier:
-
-<programlisting>
-PREPARE TRANSACTION 'foobar';
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-commit-prepared"></member>
-   <member><xref linkend="sql-rollback-prepared"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/psql-ref.sgmlin b/doc-xc/src/sgml/ref/psql-ref.sgmlin
deleted file mode 100644
index 886069b4f0..0000000000
--- a/doc-xc/src/sgml/ref/psql-ref.sgmlin
+++ /dev/null
@@ -1,3604 +0,0 @@
-<!--
-doc/src/sgml/ref/psql-ref.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-PSQL">
-  <refmeta>
-    <refentrytitle><application>psql</application></refentrytitle>
-    <manvolnum>1</manvolnum>
-    <refmiscinfo>Application</refmiscinfo>
-  </refmeta>
-
-  <refnamediv>
-    <refname><application>psql</application></refname>
-    <refpurpose>
-<!## PG>
-      <productname>PostgreSQL</productname> interactive terminal
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname> interactive terminal
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname> interactive terminal
-<!## end>
-    </refpurpose>
-  </refnamediv>
-
- <indexterm zone="app-psql">
-  <primary>psql</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>psql</command>
-   <arg rep="repeat"><replaceable class="parameter">option</replaceable></arg>
-   <arg><replaceable class="parameter">dbname</replaceable>
-   <arg><replaceable class="parameter">username</replaceable></arg></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-    <para>
-     <application>psql</application> is a terminal-based front-end to
-<!## PG>
-     <productname>PostgreSQL</productname>. It enables you to type in
-     queries interactively, issue them to
-     <productname>PostgreSQL</productname>, and see the query results.
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname>. It enables you to type in
-     queries interactively, issue them to
-     <productname>Postgres-XC</productname>, and see the query results.
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname>. It enables you to type in
-     queries interactively, issue them to
-     <productname>Postgres-XL</productname>, and see the query results.
-<!## end>
-     Alternatively, input can be from a file. In addition, it provides a
-     number of meta-commands and various shell-like features to
-     facilitate writing scripts and automating a wide variety of tasks.
-    </para>
- </refsect1>
-
- <refsect1 id="R1-APP-PSQL-3">
-  <title>Options</title>
-
-&common;
-
-  <variablelist>
-    <varlistentry>
-      <term><option>-a</></term>
-      <term><option>--echo-all</></term>
-      <listitem>
-      <para>
-      Print all input lines to standard output as they are read. This is more
-      useful for script processing than interactive mode. This is
-      equivalent to setting the variable <varname>ECHO</varname> to
-      <literal>all</literal>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-A</></term>
-      <term><option>--no-align</></term>
-      <listitem>
-      <para>
-      Switches to unaligned output mode. (The default output mode is
-      otherwise aligned.)
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-c <replaceable class="parameter">command</replaceable></></term>
-      <term><option>--command=<replaceable class="parameter">command</replaceable></></term>
-      <listitem>
-      <para>
-      Specifies that <application>psql</application> is to execute one
-      command string, <replaceable class="parameter">command</replaceable>,
-      and then exit. This is useful in shell scripts. Start-up files
-      (<filename>psqlrc</filename> and <filename>~/.psqlrc</filename>) are
-      ignored with this option.
-      </para>
-      <para>
-      <replaceable class="parameter">command</replaceable> must be either
-      a command string that is completely parsable by the server (i.e.,
-      it contains no <application>psql</application>-specific features),
-      or a single backslash command. Thus you cannot mix
-      <acronym>SQL</acronym> and <application>psql</application>
-      meta-commands with this option. To achieve that, you could
-      pipe the string into <application>psql</application>, like
-      this: <literal>echo '\x \\ SELECT * FROM foo;' | psql</literal>.
-      (<literal>\\</> is the separator meta-command.)
-      </para>
-      <para>
-       If the command string contains multiple SQL commands, they are
-       processed in a single transaction, unless there are explicit
-       <command>BEGIN</>/<command>COMMIT</> commands included in the
-       string to divide it into multiple transactions.  This is
-       different from the behavior when the same string is fed to
-       <application>psql</application>'s standard input.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-d <replaceable class="parameter">dbname</replaceable></></term>
-      <term><option>--dbname=<replaceable class="parameter">dbname</replaceable></></term>
-      <listitem>
-      <para>
-       Specifies the name of the database to connect to. This is
-       equivalent to specifying <replaceable
-       class="parameter">dbname</replaceable> as the first non-option
-       argument on the command line.
-      </para>
-      <para>
-       If this parameter contains an <symbol>=</symbol> sign, it is treated as a
-       <parameter>conninfo</parameter> string. See <xref linkend="libpq-connect"> for more information.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-e</></term>
-      <term><option>--echo-queries</></term>
-      <listitem>
-      <para>
-      Copy all SQL commands sent to the server to standard output as well.
-      This is equivalent
-      to setting the variable <varname>ECHO</varname> to
-      <literal>queries</literal>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-E</></term>
-      <term><option>--echo-hidden</></term>
-      <listitem>
-      <para>
-      Echo the actual queries generated by <command>\d</command> and other backslash
-      commands. You can use this to study <application>psql</application>'s
-      internal operations. This is equivalent to
-      setting the variable <varname>ECHO_HIDDEN</varname> from within
-      <application>psql</application>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-f <replaceable class="parameter">filename</replaceable></></term>
-      <term><option>--file=<replaceable class="parameter">filename</replaceable></></term>
-      <listitem>
-      <para>
-      Use the file <replaceable class="parameter">filename</replaceable>
-      as the source of commands instead of reading commands interactively.
-      After the file is processed, <application>psql</application>
-      terminates. This is in many ways equivalent to the internal
-      command <command>\i</command>.
-      </para>
-
-      <para>
-       If <replaceable>filename</replaceable> is <literal>-</literal>
-       (hyphen), then standard input is read.
-      </para>
-
-      <para>
-      Using this option is subtly different from writing <literal>psql
-      &lt; <replaceable
-      class="parameter">filename</replaceable></literal>. In general,
-      both will do what you expect, but using <literal>-f</literal>
-      enables some nice features such as error messages with line
-      numbers. There is also a slight chance that using this option will
-      reduce the start-up overhead. On the other hand, the variant using
-      the shell's input redirection is (in theory) guaranteed to yield
-      exactly the same output you would have received had you entered
-      everything by hand.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-F <replaceable class="parameter">separator</replaceable></></term>
-      <term><option>--field-separator=<replaceable class="parameter">separator</replaceable></></term>
-      <listitem>
-      <para>
-      Use <replaceable class="parameter">separator</replaceable> as the
-      field separator for unaligned output. This is equivalent to
-      <command>\pset fieldsep</command> or <command>\f</command>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-h <replaceable class="parameter">hostname</replaceable></></term>
-      <term><option>--host=<replaceable class="parameter">hostname</replaceable></></term>
-      <listitem>
-      <para>
-      Specifies the host name of the machine on which the
-      server is running. If the value begins
-      with a slash, it is used as the directory for the Unix-domain
-      socket.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-H</></term>
-      <term><option>--html</></term>
-      <listitem>
-      <para>
-      Turn on <acronym>HTML</acronym> tabular output. This is
-      equivalent to <literal>\pset format html</literal> or the
-      <command>\H</command> command.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-l</></term>
-      <term><option>--list</></term>
-      <listitem>
-      <para>
-      List all available databases, then exit. Other non-connection
-      options are ignored. This is similar to the internal command
-      <command>\list</command>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-L <replaceable class="parameter">filename</replaceable></></term>
-      <term><option>--log-file=<replaceable class="parameter">filename</replaceable></></term>
-      <listitem>
-      <para>
-       Write all query output into file <replaceable
-       class="parameter">filename</replaceable>, in addition to the
-       normal output destination.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-n</></term>
-      <term><option>--no-readline</></term>
-      <listitem>
-      <para>
-       Do not use readline for line editing and do not use the history.
-       This can be useful to turn off tab expansion when cutting and pasting.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-o <replaceable class="parameter">filename</replaceable></></term>
-      <term><option>--output=<replaceable class="parameter">filename</replaceable></></term>
-      <listitem>
-      <para>
-      Put all query output into file <replaceable
-      class="parameter">filename</replaceable>. This is equivalent to
-      the command <command>\o</command>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></></term>
-      <listitem>
-      <para>
-      Specifies the TCP port or the local Unix-domain
-      socket file extension on which the server is listening for
-      connections. Defaults to the value of the <envar>PGPORT</envar>
-      environment variable or, if not set, to the port specified at
-      compile time, usually 5432.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-P <replaceable class="parameter">assignment</replaceable></></term>
-      <term><option>--pset=<replaceable class="parameter">assignment</replaceable></></term>
-      <listitem>
-      <para>
-      Specifies printing options, in the style of
-      <command>\pset</command>. Note that here you
-      have to separate name and value with an equal sign instead of a
-      space. For example, to set the output format to LaTeX, you could write
-      <literal>-P format=latex</literal>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-q</></term>
-      <term><option>--quiet</></term>
-      <listitem>
-      <para>
-      Specifies that <application>psql</application> should do its work
-      quietly. By default, it prints welcome messages and various
-      informational output. If this option is used, none of this
-      happens. This is useful with the <option>-c</option> option.
-      Within <application>psql</application> you can also set the
-      <varname>QUIET</varname> variable to achieve the same effect.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-R <replaceable class="parameter">separator</replaceable></></term>
-      <term><option>--record-separator=<replaceable class="parameter">separator</replaceable></></term>
-      <listitem>
-      <para>
-      Use <replaceable class="parameter">separator</replaceable> as the
-      record separator for unaligned output. This is equivalent to the
-      <command>\pset recordsep</command> command.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-s</></term>
-      <term><option>--single-step</></term>
-      <listitem>
-      <para>
-      Run in single-step mode. That means the user is prompted before
-      each command is sent to the server, with the option to cancel
-      execution as well. Use this to debug scripts.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-S</></term>
-      <term><option>--single-line</></term>
-      <listitem>
-      <para>
-      Runs in single-line mode where a newline terminates an SQL command, as a
-      semicolon does.
-      </para>
-
-      <note>
-      <para>
-      This mode is provided for those who insist on it, but you are not
-      necessarily encouraged to use it. In particular, if you mix
-      <acronym>SQL</acronym> and meta-commands on a line the order of
-      execution might not always be clear to the inexperienced user.
-      </para>
-      </note>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-t</></term>
-      <term><option>--tuples-only</></term>
-      <listitem>
-      <para>
-      Turn off printing of column names and result row count footers,
-      etc. This is equivalent to the <command>\t</command> command.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-T <replaceable class="parameter">table_options</replaceable></></term>
-      <term><option>--table-attr=<replaceable class="parameter">table_options</replaceable></></term>
-      <listitem>
-      <para>
-      Specifies options to be placed within the
-      <acronym>HTML</acronym> <sgmltag>table</sgmltag> tag. See
-      <command>\pset</command> for details.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-      <para>
-      Connect to the database as the user <replaceable
-      class="parameter">username</replaceable> instead of the default.
-      (You must have permission to do so, of course.)
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-v <replaceable class="parameter">assignment</replaceable></></term>
-      <term><option>--set=<replaceable class="parameter">assignment</replaceable></></term>
-      <term><option>--variable=<replaceable class="parameter">assignment</replaceable></></term>
-      <listitem>
-      <para>
-      Perform a variable assignment, like the <command>\set</command>
-      internal command. Note that you must separate name and value, if
-      any, by an equal sign on the command line. To unset a variable,
-      leave off the equal sign. To just set a variable without a value,
-      use the equal sign but leave off the value. These assignments are
-      done during a very early stage of start-up, so variables reserved
-      for internal purposes might get overwritten later.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-V</></term>
-      <term><option>--version</></term>
-      <listitem>
-      <para>
-      Print the <application>psql</application> version and exit.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>-w</></term>
-     <term><option>--no-password</></term>
-     <listitem>
-      <para>
-       Never issue a password prompt.  If the server requires password
-       authentication and a password is not available by other means
-       such as a <filename>.pgpass</filename> file, the connection
-       attempt will fail.  This option can be useful in batch jobs and
-       scripts where no user is present to enter a password.
-      </para>
-
-      <para>
-       Note that this option will remain set for the entire session,
-       and so it affects uses of the meta-command
-       <command>\connect</command> as well as the initial connection attempt.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-      <para>
-       Force <application>psql</application> to prompt for a
-       password before connecting to a database.
-      </para>
-
-      <para>
-       This option is never essential, since <application>psql</application>
-       will automatically prompt for a password if the server demands
-       password authentication.  However, <application>psql</application>
-       will waste a connection attempt finding out that the server wants a
-       password.  In some cases it is worth typing <option>-W</> to avoid
-       the extra connection attempt.
-      </para>
-
-      <para>
-       Note that this option will remain set for the entire session,
-       and so it affects uses of the meta-command
-       <command>\connect</command> as well as the initial connection attempt.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-x</></term>
-      <term><option>--expanded</></term>
-      <listitem>
-      <para>
-      Turn on the expanded table formatting mode. This is equivalent to the
-      <command>\x</command> command.
-      </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-X,</></term>
-      <term><option>--no-psqlrc</></term>
-      <listitem>
-      <para>
-      Do not read the start-up file (neither the system-wide
-      <filename>psqlrc</filename> file nor the user's
-      <filename>~/.psqlrc</filename> file).
-      </para>
-      </listitem>
-    </varlistentry>
-
-     <varlistentry>
-      <term><option>-1</option></term>
-      <term><option>--single-transaction</option></term>
-      <listitem>
-       <para>
-        When <application>psql</application> executes a script with the
-        <option>-f</> option, adding this option wraps
-        <command>BEGIN</>/<command>COMMIT</> around the script to execute it
-        as a single transaction.  This ensures that either all the commands
-        complete successfully, or no changes are applied.
-       </para>
-
-       <para>
-        If the script itself uses <command>BEGIN</>, <command>COMMIT</>,
-        or <command>ROLLBACK</>, this option will not have the desired
-        effects.
-        Also, if the script contains any command that cannot be executed
-        inside a transaction block, specifying this option will cause that
-        command (and hence the whole transaction) to fail.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    <varlistentry>
-      <term><option>-?</></term>
-      <term><option>--help</></term>
-      <listitem>
-      <para>
-      Show help about <application>psql</application> command line
-      arguments, and exit.
-      </para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
- </refsect1>
-
-
- <refsect1>
-  <title>Exit Status</title>
-&common;
-
-  <para>
-   <application>psql</application> returns 0 to the shell if it
-   finished normally, 1 if a fatal error of its own occurs (e.g. out of memory,
-   file not found), 2 if the connection to the server went bad
-   and the session was not interactive, and 3 if an error occurred in a
-   script and the variable <varname>ON_ERROR_STOP</varname> was set.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Usage</title>
-
-&common;
-  <refsect2 id="R2-APP-PSQL-connecting">
-    <title>Connecting to a Database</title>
-
-&common;
-    <para>
-    <application>psql</application> is a regular
-<!## PG>
-    <productname>PostgreSQL</productname> client application. In order
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> client application. In order
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> client application. In order
-<!## end>
-    to connect to a database you need to know the name of your target
-    database, the host name and port number of the server, and what user
-    name you want to connect as. <application>psql</application> can be
-    told about those parameters via command line options, namely
-    <option>-d</option>, <option>-h</option>, <option>-p</option>, and
-    <option>-U</option> respectively. If an argument is found that does
-    not belong to any option it will be interpreted as the database name
-    (or the user name, if the database name is already given). Not all
-    of these options are required; there are useful defaults. If you omit the host
-    name, <application>psql</> will connect via a Unix-domain socket
-    to a server on the local host, or via TCP/IP to <literal>localhost</> on
-    machines that don't have Unix-domain sockets. The default port number is
-    determined at compile time.
-    Since the database server uses the same default, you will not have
-    to specify the port in most cases. The default user name is your
-    Unix user name, as is the default database name. Note that you cannot
-    just connect to any database under any user name. Your database
-    administrator should have informed you about your access rights.
-    </para>
-
-    <para>
-    When the defaults aren't quite right, you can save yourself
-    some typing by setting the environment variables
-    <envar>PGDATABASE</envar>, <envar>PGHOST</envar>,
-    <envar>PGPORT</envar> and/or <envar>PGUSER</envar> to appropriate
-    values. (For additional environment variables, see <xref
-    linkend="libpq-envars">.) It is also convenient to have a
-    <filename>~/.pgpass</> file to avoid regularly having to type in
-    passwords. See <xref linkend="libpq-pgpass"> for more information.
-    </para>
-
-    <para>
-     An alternative way to specify connection parameters is in a
-     <parameter>conninfo</parameter> string, which is used instead of a
-     database name. This mechanism give you very wide control over the
-     connection. For example:
-<programlisting>
-$ <userinput>psql "service=myservice sslmode=require"</userinput>
-</programlisting>
-     This way you can also use LDAP for connection parameter lookup as
-     described in <xref linkend="libpq-ldap">.
-     See <xref linkend="libpq-connect"> for more information on all the
-     available connection options.
-    </para>
-
-    <para>
-    If the connection could not be made for any reason (e.g., insufficient
-    privileges, server is not running on the targeted host, etc.),
-    <application>psql</application> will return an error and terminate.
-    </para>
-
-    <para>
-     If at least one of standard input or standard output are a
-     terminal, then <application>psql</application> sets the client
-     encoding to <quote>auto</quote>, which will detect the
-     appropriate client encoding from the locale settings
-     (<envar>LC_CTYPE</envar> environment variable on Unix systems).
-     If this doesn't work out as expected, the client encoding can be
-     overridden using the environment
-     variable <envar>PGCLIENTENCODING</envar>.
-    </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PSQL-4">
-    <title>Entering SQL Commands</title>
-&common;
-
-    <para>
-    In normal operation, <application>psql</application> provides a
-    prompt with the name of the database to which
-    <application>psql</application> is currently connected, followed by
-    the string <literal>=&gt;</literal>. For example:
-<programlisting>
-$ <userinput>psql testdb</userinput>
-psql (&version;)
-Type "help" for help.
-
-testdb=&gt;
-</programlisting>
-    </para>
-
-    <para>
-    At the prompt, the user can type in <acronym>SQL</acronym> commands.
-    Ordinarily, input lines are sent to the server when a
-    command-terminating semicolon is reached. An end of line does not
-    terminate a command.  Thus commands can be spread over several lines for
-    clarity. If the command was sent and executed without error, the results
-    of the command are displayed on the screen.
-    </para>
-
-    <para>
-    Whenever a command is executed, <application>psql</application> also polls
-    for asynchronous notification events generated by
-    <xref linkend="SQL-LISTEN"> and
-    <xref linkend="SQL-NOTIFY">.
-    </para>
-  </refsect2>
-
-  <refsect2 id="APP-PSQL-meta-commands">
-    <title>Meta-Commands</title>
-&common;
-
-    <para>
-    Anything you enter in <application>psql</application> that begins
-    with an unquoted backslash is a <application>psql</application>
-    meta-command that is processed by <application>psql</application>
-    itself. These commands make
-    <application>psql</application> more useful for administration or
-    scripting. Meta-commands are often called slash or backslash commands.
-    </para>
-
-    <para>
-    The format of a <application>psql</application> command is the backslash,
-    followed immediately by a command verb, then any arguments. The arguments
-    are separated from the command verb and each other by any number of
-    whitespace characters.
-    </para>
-
-    <para>
-    To include whitespace into an argument you can quote it with a
-    single quote. To include a single quote into such an argument,
-    use two single quotes. Anything contained in single quotes is
-    furthermore subject to C-like substitutions for
-    <literal>\n</literal> (new line), <literal>\t</literal> (tab),
-    <literal>\</literal><replaceable>digits</replaceable> (octal), and
-    <literal>\x</literal><replaceable>digits</replaceable> (hexadecimal).
-    </para>
-
-    <para>
-    If an unquoted argument begins with a colon (<literal>:</literal>),
-    it is taken as a <application>psql</> variable and the value of the
-    variable is used as the argument instead.  If the variable name is
-    surrounded by single quotes (e.g. <literal>:'var'</literal>), it
-    will be escaped as an SQL literal and the result will be used as
-    the argument.  If the variable name is surrounded by double quotes,
-    it will be escaped as an SQL identifier and the result will be used
-    as the argument.
-    </para>
-
-    <para>
-    Arguments that are enclosed in backquotes (<literal>`</literal>)
-    are taken as a command line that is passed to the shell. The
-    output of the command (with any trailing newline removed) is taken
-    as the argument value. The above escape sequences also apply in
-    backquotes.
-    </para>
-
-    <para>
-    Some commands take an <acronym>SQL</acronym> identifier (such as a
-    table name) as argument. These arguments follow the syntax rules
-    of <acronym>SQL</acronym>: Unquoted letters are forced to
-    lowercase, while double quotes (<literal>"</>) protect letters
-    from case conversion and allow incorporation of whitespace into
-    the identifier.  Within double quotes, paired double quotes reduce
-    to a single double quote in the resulting name.  For example,
-    <literal>FOO"BAR"BAZ</> is interpreted as <literal>fooBARbaz</>,
-    and <literal>"A weird"" name"</> becomes <literal>A weird"
-    name</>.
-    </para>
-
-    <para>
-    Parsing for arguments stops at the end of the line, or when another
-    unquoted backslash is found.  An unquoted backslash
-    is taken as the beginning of a new meta-command. The special
-    sequence <literal>\\</literal> (two backslashes) marks the end of
-    arguments and continues parsing <acronym>SQL</acronym> commands, if
-    any. That way <acronym>SQL</acronym> and
-    <application>psql</application> commands can be freely mixed on a
-    line. But in any case, the arguments of a meta-command cannot
-    continue beyond the end of the line.
-    </para>
-
-    <para>
-    The following meta-commands are defined:
-
-    <variablelist>
-      <varlistentry>
-        <term><literal>\a</literal></term>
-        <listitem>
-        <para>
-        If the current table output format is unaligned, it is switched to aligned.
-        If it is not unaligned, it is set to unaligned. This command is
-        kept for backwards compatibility. See <command>\pset</command> for a
-        more general solution.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\c</literal> or <literal>\connect</literal> <literal>[ <replaceable class="parameter">dbname</replaceable> [ <replaceable class="parameter">username</replaceable> ] [ <replaceable class="parameter">host</replaceable> ] [ <replaceable class="parameter">port</replaceable> ] ]</literal></term>
-        <listitem>
-        <para>
-<!## PG>
-        Establishes a new connection to a <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-        Establishes a new connection to a <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-        Establishes a new connection to a <productname>Postgres-XL</>
-<!## end>
-        server. If the new connection is successfully made, the
-        previous connection is closed. If any of <replaceable
-        class="parameter">dbname</replaceable>, <replaceable
-        class="parameter">username</replaceable>, <replaceable
-        class="parameter">host</replaceable> or <replaceable
-        class="parameter">port</replaceable> are omitted or specified
-        as <literal>-</literal>, the value of that parameter from the
-        previous connection is used. If there is no previous
-        connection, the <application>libpq</application> default for
-        the parameter's value is used.
-        </para>
-
-        <para>
-        If the connection attempt failed (wrong user name, access
-        denied, etc.), the previous connection will only be kept if
-        <application>psql</application> is in interactive mode. When
-        executing a non-interactive script, processing will
-        immediately stop with an error. This distinction was chosen as
-        a user convenience against typos on the one hand, and a safety
-        mechanism that scripts are not accidentally acting on the
-        wrong database on the other hand.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\C [ <replaceable class="parameter">title</replaceable> ]</literal></term>
-        <listitem>
-        <para>
-        Sets the title of any tables being printed as the result of a
-        query or unset any such title. This command is equivalent to
-        <literal>\pset title <replaceable
-        class="parameter">title</replaceable></literal>. (The name of
-        this command derives from <quote>caption</quote>, as it was
-        previously only used to set the caption in an
-        <acronym>HTML</acronym> table.)
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>\cd [ <replaceable>directory</replaceable> ]</literal></term>
-       <listitem>
-        <para>
-         Changes the current working directory to
-         <replaceable>directory</replaceable>. Without argument, changes
-         to the current user's home directory.
-        </para>
-
-        <tip>
-         <para>
-          To print your current working directory, use <literal>\! pwd</literal>.
-         </para>
-        </tip>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\conninfo</literal></term>
-        <listitem>
-        <para>
-        Outputs information about the current database connection.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\copy { <replaceable class="parameter">table</replaceable> [ ( <replaceable class="parameter">column_list</replaceable> ) ] | ( <replaceable class="parameter">query</replaceable> ) }
-        { <literal>from</literal> | <literal>to</literal> }
-        { <replaceable class="parameter">filename</replaceable> | stdin | stdout | pstdin | pstdout }
-        [ with ]
-            [ binary ]
-            [ oids ]
-            [ delimiter [ as ] '<replaceable class="parameter">character</replaceable>' ]
-            [ null [ as ] '<replaceable class="parameter">string</replaceable>' ]
-            [ csv
-              [ header ]
-              [ quote [ as ] '<replaceable class="parameter">character</replaceable>' ]
-              [ escape [ as ] '<replaceable class="parameter">character</replaceable>' ]
-              [ force quote <replaceable class="parameter">column_list</replaceable> | * ]
-              [ force not null <replaceable class="parameter">column_list</replaceable> ] ]</literal>
-        </term>
-
-        <listitem>
-        <para>
-        Performs a frontend (client) copy. This is an operation that
-        runs an <acronym>SQL</acronym> <xref linkend="SQL-COPY">
-        command, but instead of the server
-        reading or writing the specified file,
-        <application>psql</application> reads or writes the file and
-        routes the data between the server and the local file system.
-        This means that file accessibility and privileges are those of
-        the local user, not the server, and no SQL superuser
-        privileges are required.
-        </para>
-
-        <para>
-        The syntax of the command is similar to that of the
-        <acronym>SQL</acronym> <xref linkend="sql-copy">
-        command.  Note that, because of this,
-        special parsing rules apply to the <command>\copy</command>
-        command. In particular, the variable substitution rules and
-        backslash escapes do not apply.
-        </para>
-
-        <para>
-        <literal>\copy ... from stdin | to stdout</literal>
-        reads/writes based on the command input and output respectively.
-        All rows are read from the same source that issued the command,
-        continuing until <literal>\.</literal> is read or the stream
-        reaches <acronym>EOF</>. Output is sent to the same place as
-        command output. To read/write from
-        <application>psql</application>'s standard input or output, use
-        <literal>pstdin</> or <literal>pstdout</>. This option is useful
-        for populating tables in-line within a SQL script file.
-        </para>
-
-        <tip>
-        <para>
-        This operation is not as efficient as the <acronym>SQL</acronym>
-        <command>COPY</command> command because all data must pass
-        through the client/server connection. For large
-        amounts of data the <acronym>SQL</acronym> command might be preferable.
-        </para>
-        </tip>
-
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\copyright</literal></term>
-        <listitem>
-        <para>
-        Shows the copyright and distribution terms of
-<!## PG>
-        <productname>PostgreSQL</productname>.
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname>.
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname>.
-<!## end>
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\d[S+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-
-        <listitem>
-        <para>
-        For each relation (table, view, index, sequence or foreign table)
-        matching the
-        <replaceable class="parameter">pattern</replaceable>, show all
-        columns, their types, the tablespace (if not the default) and any
-        special attributes such as <literal>NOT NULL</literal> or defaults.
-        Associated indexes, constraints, rules, and triggers are
-        also shown.  For foreign tables, the associated foreign
-        server is shown as well.
-        (<quote>Matching the pattern</> is defined in
-        <xref linkend="APP-PSQL-patterns" endterm="APP-PSQL-patterns-title">
-        below.)
-        </para>
-
-        <para>
-        The command form <literal>\d+</literal> is identical, except that
-        more information is displayed: any comments associated with the
-        columns of the table are shown, as is the presence of OIDs in the
-        table, the view definition if the relation is a view, the generic
-        options if the relation is a foreign table, distribution method
-        and location nodes information if the relation is a table but not
-        foreigh table.
-        </para>
-
-        <para>
-        By default, only user-created objects are shown;  supply a
-        pattern or the <literal>S</literal> modifier to include system
-        objects.
-        </para>
-
-        <note>
-        <para>
-        If <command>\d</command> is used without a
-        <replaceable class="parameter">pattern</replaceable> argument, it is
-        equivalent to <command>\dtvsE</command> which will show a list of
-        all visible tables, views, sequences and foreign tables.
-        This is purely a convenience measure.
-        </para>
-        </note>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\da[S] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-
-        <listitem>
-        <para>
-        Lists aggregate functions, together with their
-        return type and the data types they operate on. If <replaceable
-        class="parameter">pattern</replaceable>
-        is specified, only aggregates whose names match the pattern are shown.
-        By default, only user-created objects are shown;  supply a
-        pattern or the <literal>S</literal> modifier to include system
-        objects.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\db[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-
-        <listitem>
-        <para>
-        Lists tablespaces. If <replaceable
-        class="parameter">pattern</replaceable>
-        is specified, only tablespaces whose names match the pattern are shown.
-        If <literal>+</literal> is appended to the command name, each object
-        is listed with its associated permissions.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dc[S] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists conversions between character-set encodings.
-        If <replaceable class="parameter">pattern</replaceable>
-        is specified, only conversions whose names match the pattern are
-        listed.
-        By default, only user-created objects are shown;  supply a
-        pattern or the <literal>S</literal> modifier to include system
-        objects.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dC [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists type casts.
-        If <replaceable class="parameter">pattern</replaceable>
-        is specified, only casts whose source or target types match the
-        pattern are listed.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dd[S] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Shows the descriptions of objects matching the <replaceable
-        class="parameter">pattern</replaceable>, or of all visible objects if
-        no argument is given.  But in either case, only objects that have
-        a description are listed.
-        By default, only user-created objects are shown;  supply a
-        pattern or the <literal>S</literal> modifier to include system
-        objects.
-        <quote>Object</quote> covers aggregates, functions, operators,
-        types, relations (tables, views, indexes, sequences), large
-        objects, rules, and triggers. For example:
-<!## PG>
-<programlisting>
-=&gt; <userinput>\dd version</userinput>
-                     Object descriptions
-   Schema   |  Name   |  Object  |        Description
-------------+---------+----------+---------------------------
- pg_catalog | version | function | PostgreSQL version string
-(1 row)
-</programlisting>
-<!## end>
-<!## XC>
-<programlisting>
-=&gt; <userinput>\dd version</userinput>
-                     Object descriptions
-   Schema   |  Name   |  Object  |        Description
-------------+---------+----------+---------------------------
- pg_catalog | version | function | Postgres-XC version string
-(1 row)
-</programlisting>
-<!## end>
-<!## XL>
-<programlisting>
-=&gt; <userinput>\dd version</userinput>
-                     Object descriptions
-   Schema   |  Name   |  Object  |        Description
-------------+---------+----------+---------------------------
- pg_catalog | version | function | Postgres-XL version string
-(1 row)
-</programlisting>
-<!## end>
-        </para>
-
-        <para>
-        Descriptions for objects can be created with the <xref
-        linkend="sql-comment">
-        <acronym>SQL</acronym> command.
-       </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\ddp [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists default access privilege settings.  An entry is shown for
-        each role (and schema, if applicable) for which the default
-        privilege settings have been changed from the built-in defaults.
-        If <replaceable class="parameter">pattern</replaceable> is
-        specified, only entries whose role name or schema name matches
-        the pattern are listed.
-        </para>
-
-        <para>
-        The <xref linkend="sql-alterdefaultprivileges"> command is used to set
-        default access privileges.  The meaning of the
-        privilege display is explained under
-        <xref linkend="sql-grant">.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dD[S] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists domains. If <replaceable
-        class="parameter">pattern</replaceable>
-        is specified, only domains whose names match the pattern are shown.
-        By default, only user-created objects are shown;  supply a
-        pattern or the <literal>S</literal> modifier to include system
-        objects.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dE[S+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <term><literal>\di[S+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <term><literal>\ds[S+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <term><literal>\dt[S+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <term><literal>\dv[S+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-
-        <listitem>
-        <para>
-        In this group of commands, the letters <literal>E</literal>,
-        <literal>i</literal>, <literal>s</literal>,
-        <literal>t</literal>, and <literal>v</literal>
-        stand for foreign table, index, sequence, table, and view,
-        respectively.
-        You can specify any or all of
-        these letters, in any order, to obtain a listing of objects
-        of these types.  For example, <literal>\dit</> lists indexes
-        and tables.  If <literal>+</literal> is
-        appended to the command name, each object is listed with its
-        physical size on disk and its associated description, if any.
-        If <replaceable class="parameter">pattern</replaceable> is
-        specified, only objects whose names match the pattern are listed.
-        By default, only user-created objects are shown; supply a
-        pattern or the <literal>S</literal> modifier to include system
-        objects.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\des[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists foreign servers (mnemonic: <quote>external
-        servers</quote>).
-        If <replaceable class="parameter">pattern</replaceable> is
-        specified, only those servers whose name matches the pattern
-        are listed.  If the form <literal>\des+</literal> is used, a
-        full description of each server is shown, including the
-        server's ACL, type, version, and options.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\det[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists foreign tables (mnemonic: <quote>external tables</quote>).
-        If <replaceable class="parameter">pattern</replaceable> is
-        specified, only entries whose table name or schema name matches
-        the pattern are listed.  If the form <literal>\det+</literal>
-        is used, generic options are also displayed.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\deu[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists user mappings (mnemonic: <quote>external
-        users</quote>).
-        If <replaceable class="parameter">pattern</replaceable> is
-        specified, only those mappings whose user names match the
-        pattern are listed.  If the form <literal>\deu+</literal> is
-        used, additional information about each mapping is shown.
-        </para>
-
-        <caution>
-        <para>
-        <literal>\deu+</literal> might also display the user name and
-        password of the remote user, so care should be taken not to
-        disclose them.
-        </para>
-        </caution>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dew[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists foreign-data wrappers (mnemonic: <quote>external
-        wrappers</quote>).
-        If <replaceable class="parameter">pattern</replaceable> is
-        specified, only those foreign-data wrappers whose name matches
-        the pattern are listed.  If the form <literal>\dew+</literal>
-        is used, the ACL and options of the foreign-data wrapper are
-        also shown.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\df[antwS+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-
-        <listitem>
-        <para>
-        Lists functions, together with their arguments, return types, and
-        function types, which are classified as <quote>agg</> (aggregate),
-        <quote>normal</>, <quote>trigger</>, or <quote>window</>.
-        To display only functions
-        of specific type(s), add the corresponding letters <literal>a</>,
-        <literal>n</>, <literal>t</>, or <literal>w</> to the command.
-        If <replaceable
-        class="parameter">pattern</replaceable> is specified, only
-        functions whose names match the pattern are shown.  If the
-        form <literal>\df+</literal> is used, additional information
-        about each function, including volatility, language, source
-        code and description, is shown.  By default, only user-created
-        objects are shown; supply a pattern or the <literal>S</literal>
-        modifier to include system objects.
-        </para>
-
-        <tip>
-        <para>
-        To look up functions taking arguments or returning values of a specific
-        type, use your pager's search capability to scroll through the
-        <literal>\df</> output.
-        </para>
-        </tip>
-
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\dF[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-         Lists text search configurations.
-         If <replaceable class="parameter">pattern</replaceable> is specified,
-         only configurations whose names match the pattern are shown.
-         If the form <literal>\dF+</literal> is used, a full description of
-         each configuration is shown, including the underlying text search
-         parser and the dictionary list for each parser token type.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\dFd[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-         Lists text search dictionaries.
-         If <replaceable class="parameter">pattern</replaceable> is specified,
-         only dictionaries whose names match the pattern are shown.
-         If the form <literal>\dFd+</literal> is used, additional information
-         is shown about each selected dictionary, including the underlying
-         text search template and the option values.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\dFp[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-         Lists text search parsers.
-         If <replaceable class="parameter">pattern</replaceable> is specified,
-         only parsers whose names match the pattern are shown.
-         If the form <literal>\dFp+</literal> is used, a full description of
-         each parser is shown, including the underlying functions and the
-         list of recognized token types.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\dFt[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-         Lists text search templates.
-         If <replaceable class="parameter">pattern</replaceable> is specified,
-         only templates whose names match the pattern are shown.
-         If the form <literal>\dFt+</literal> is used, additional information
-         is shown about each template, including the underlying function names.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dg[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists database roles. If <replaceable
-        class="parameter">pattern</replaceable> is specified, only
-        those roles whose names match the pattern are listed.
-        (This command is now effectively the same as <literal>\du</literal>).
-        If the form <literal>\dg+</literal> is used, additional information
-        is shown about each role, including the comment for each role.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dl</literal></term>
-        <listitem>
-        <para>
-        This is an alias for <command>\lo_list</command>, which shows a
-        list of large objects.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\dL[S+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists procedural languages. If <replaceable
-        class="parameter">pattern</replaceable>
-        is specified, only languages whose names match the pattern are listed.
-        By default, only user-created languages
-        are shown; supply the <literal>S</literal> modifier to include system
-        objects. If <literal>+</literal> is appended to the command name, each
-        language is listed with its call handler, validator, access privileges,
-        and whether it is a system object.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dn[S+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-
-        <listitem>
-        <para>
-        Lists schemas (namespaces). If <replaceable
-        class="parameter">pattern</replaceable>
-        is specified, only schemas whose names match the pattern are listed.
-        By default, only user-created objects are shown; supply a
-        pattern or the <literal>S</literal> modifier to include system objects.
-        If <literal>+</literal> is appended to the command name, each object
-        is listed with its associated permissions and description, if any.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\do[S] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists operators with their operand and return types.
-        If <replaceable class="parameter">pattern</replaceable> is
-        specified, only operators whose names match the pattern are listed.
-        By default, only user-created objects are shown;  supply a
-        pattern or the <literal>S</literal> modifier to include system
-        objects.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dO[S+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists collations.
-        If <replaceable class="parameter">pattern</replaceable> is
-        specified, only collations whose names match the pattern are
-        listed.  By default, only user-created objects are shown;
-        supply a pattern or the <literal>S</literal> modifier to
-        include system objects.  If <literal>+</literal> is appended
-        to the command name, each collation is listed with its associated
-        description, if any.
-        Note that only collations usable with the current database's encoding
-        are shown, so the results may vary in different databases of the
-        same installation.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dp [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists tables, views and sequences with their
-        associated access privileges.
-        If <replaceable class="parameter">pattern</replaceable> is
-        specified, only tables, views and sequences whose names match the
-        pattern are listed.
-        </para>
-
-        <para>
-        The <xref linkend="sql-grant"> and
-        <xref linkend="sql-revoke">
-        commands are used to set access privileges.  The meaning of the
-        privilege display is explained under
-        <xref linkend="sql-grant">.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\drds [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">role-pattern</replaceable></link> [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">database-pattern</replaceable></link> ] ]</literal></term>
-        <listitem>
-        <para>
-        Lists defined configuration settings.  These settings can be
-        role-specific, database-specific, or both.
-        <replaceable>role-pattern</replaceable> and
-        <replaceable>database-pattern</replaceable> are used to select
-        specific roles and databases to list, respectively.  If omitted, or if
-        <literal>*</> is specified, all settings are listed, including those
-        not role-specific or database-specific, respectively.
-        </para>
-
-        <para>
-        The <xref linkend="sql-alterrole"> and
-        <xref linkend="sql-alterdatabase">
-        commands are used to define per-role and per-database configuration
-        settings.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\dT[S+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists data types.
-        If <replaceable class="parameter">pattern</replaceable> is
-        specified, only types whose names match the pattern are listed.
-        If <literal>+</literal> is appended to the command name, each type is
-        listed with its internal name and size, as well as its allowed values
-        if it is an <type>enum</> type.
-        By default, only user-created objects are shown;  supply a
-        pattern or the <literal>S</literal> modifier to include system
-        objects.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\du[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists database roles. If <replaceable
-        class="parameter">pattern</replaceable> is specified, only
-        those roles whose names match the pattern are listed.
-        If the form <literal>\du+</literal> is used, additional information
-        is shown about each role, including the comment for each role.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\dx[+] [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists installed extensions.
-        If <replaceable class="parameter">pattern</replaceable>
-        is specified, only those extensions whose names match the pattern
-        are listed.
-        If the form <literal>\dx+</literal> is used, all the objects belonging
-        to each matching extension are listed.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\e</literal> or <literal>\edit</> <literal> <optional> <replaceable class="parameter">filename</> </optional> <optional> <replaceable class="parameter">line_number</> </optional> </literal></term>
-
-        <listitem>
-        <para>
-        If <replaceable class="parameter">filename</replaceable> is
-        specified, the file is edited; after the editor exits, its
-        content is copied back to the query buffer. If no <replaceable
-        class="parameter">filename</replaceable> is given, the current query
-        buffer is copied to a temporary file which is then edited in the same
-        fashion.
-        </para>
-
-        <para>
-        The new query buffer is then re-parsed according to the normal
-        rules of <application>psql</application>, where the whole buffer
-        is treated as a single line. (Thus you cannot make scripts this
-        way. Use <command>\i</command> for that.) This means that
-        if the query ends with (or contains) a semicolon, it is
-        immediately executed. Otherwise it will merely wait in the
-        query buffer; type semicolon or <literal>\g</> to send it, or
-        <literal>\r</> to cancel.
-        </para>
-
-        <tip>
-        <para>
-        <application>psql</application> checks the environment
-        variables <envar>PSQL_EDITOR</envar>, <envar>EDITOR</envar>, and
-        <envar>VISUAL</envar> (in that order) for an editor to use. If
-        all of them are unset, <filename>vi</filename> is used on Unix
-        systems, <filename>notepad.exe</filename> on Windows systems.
-        </para>
-        </tip>
-
-        <para>
-        If a line number is specified, <application>psql</application> will
-        position the cursor on the specified line of the file or query buffer.
-        This feature requires the <varname>EDITOR_LINENUMBER_SWITCH</varname>
-        variable to be set, so that <application>psql</application> knows how
-        to specify the line number to the editor.  Note that if a single
-        all-digits argument is given, <application>psql</application> assumes
-        it is a line number not a file name.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\echo <replaceable class="parameter">text</replaceable> [ ... ]</literal></term>
-        <listitem>
-        <para>
-        Prints the arguments to the standard output, separated by one
-        space and followed by a newline. This can be useful to
-        intersperse information in the output of scripts. For example:
-<programlisting>
-=&gt; <userinput>\echo `date`</userinput>
-Tue Oct 26 21:40:57 CEST 1999
-</programlisting>
-        If the first argument is an unquoted <literal>-n</literal> the trailing
-        newline is not written.
-        </para>
-
-        <tip>
-        <para>
-        If you use the <command>\o</command> command to redirect your
-        query output you might wish to use <command>\qecho</command>
-        instead of this command.
-        </para>
-        </tip>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\ef <optional> <replaceable class="parameter">function_description</> <optional>  <replaceable class="parameter">line_number</> </optional> </optional> </literal></term>
-
-        <listitem>
-        <para>
-         This command fetches and edits the definition of the named function,
-         in the form of a <command>CREATE OR REPLACE FUNCTION</> command.
-         Editing is done in the same way as for <literal>\edit</>.
-         After the editor exits, the updated command waits in the query buffer;
-         type semicolon or <literal>\g</> to send it, or <literal>\r</>
-         to cancel.
-        </para>
-
-        <para>
-         The target function can be specified by name alone, or by name
-         and arguments, for example <literal>foo(integer, text)</>.
-         The argument types must be given if there is more
-         than one function of the same name.
-        </para>
-
-        <para>
-         If no function is specified, a blank <command>CREATE FUNCTION</>
-         template is presented for editing.
-        </para>
-
-        <para>
-        If a line number is specified, <application>psql</application> will
-        position the cursor on the specified line of the function body
-        (note that the function body typically does not begin on the
-        first line of the file).
-        This feature requires the <varname>EDITOR_LINENUMBER_SWITCH</varname>
-        variable to be set, so that <application>psql</application> knows how
-        to specify the line number to the editor.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\encoding [ <replaceable class="parameter">encoding</replaceable> ]</literal></term>
-
-        <listitem>
-        <para>
-        Sets the client character set encoding.  Without an argument, this command
-        shows the current encoding.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\f [ <replaceable class="parameter">string</replaceable> ]</literal></term>
-
-        <listitem>
-        <para>
-        Sets the field separator for unaligned query output. The default
-        is the vertical bar (<literal>|</literal>). See also
-        <command>\pset</command> for a generic way of setting output
-        options.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\g</literal> [ { <replaceable class="parameter">filename</replaceable> | <literal>|</literal><replaceable class="parameter">command</replaceable> } ]</term>
-
-        <listitem>
-        <para>
-        Sends the current query input buffer to the server and
-        optionally stores the query's output in <replaceable
-        class="parameter">filename</replaceable> or pipes the output
-        into a separate Unix shell executing <replaceable
-        class="parameter">command</replaceable>. A bare
-        <literal>\g</literal> is virtually equivalent to a semicolon. A
-        <literal>\g</literal> with argument is a <quote>one-shot</quote>
-        alternative to the <command>\o</command> command.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\h</literal> or <literal>\help</literal> <literal>[ <replaceable class="parameter">command</replaceable> ]</literal></term>
-        <listitem>
-        <para>
-        Gives syntax help on the specified <acronym>SQL</acronym>
-        command. If <replaceable class="parameter">command</replaceable>
-        is not specified, then <application>psql</application> will list
-        all the commands for which syntax help is available. If
-        <replaceable class="parameter">command</replaceable> is an
-        asterisk (<literal>*</literal>), then syntax help on all
-        <acronym>SQL</acronym> commands is shown.
-        </para>
-
-        <note>
-        <para>
-        To simplify typing, commands that consists of several words do
-        not have to be quoted. Thus it is fine to type <userinput>\help
-        alter table</userinput>.
-        </para>
-        </note>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\H</literal></term>
-        <listitem>
-        <para>
-        Turns on <acronym>HTML</acronym> query output format. If the
-        <acronym>HTML</acronym> format is already on, it is switched
-        back to the default aligned text format. This command is for
-        compatibility and convenience, but see <command>\pset</command>
-        about setting other output options.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\i <replaceable class="parameter">filename</replaceable></literal></term>
-        <listitem>
-        <para>
-        Reads input from the file <replaceable
-        class="parameter">filename</replaceable> and executes it as
-        though it had been typed on the keyboard.
-        </para>
-        <note>
-        <para>
-        If you want to see the lines on the screen as they are read you
-        must set the variable <varname>ECHO</varname> to
-        <literal>all</literal>.
-        </para>
-        </note>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\l</literal> (or <literal>\list</literal>)</term>
-        <term><literal>\l+</literal> (or <literal>\list+</literal>)</term>
-        <listitem>
-        <para>
-        List the names, owners, character set encodings, and access privileges
-        of all the databases in the server.
-        If <literal>+</literal> is appended to the command name, database
-        sizes, default tablespaces, and descriptions are also displayed.
-        (Size information is only available for databases that the current
-        user can connect to.)
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\lo_export <replaceable class="parameter">loid</replaceable> <replaceable class="parameter">filename</replaceable></literal></term>
-
-        <listitem>
-        <para>
-        Reads the large object with <acronym>OID</acronym> <replaceable
-        class="parameter">loid</replaceable> from the database and
-        writes it to <replaceable
-        class="parameter">filename</replaceable>. Note that this is
-        subtly different from the server function
-        <function>lo_export</function>, which acts with the permissions
-        of the user that the database server runs as and on the server's
-        file system.
-        </para>
-        <tip>
-        <para>
-        Use <command>\lo_list</command> to find out the large object's
-        <acronym>OID</acronym>.
-        </para>
-        </tip>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\lo_import <replaceable class="parameter">filename</replaceable> [ <replaceable class="parameter">comment</replaceable> ]</literal></term>
-
-        <listitem>
-        <para>
-<!## PG>
-        Stores the file into a <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-        Stores the file into a <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-        Stores the file into a <productname>Postgres-XL</productname>
-<!## end>
-        large object. Optionally, it associates the given
-        comment with the object. Example:
-<programlisting>
-foo=&gt; <userinput>\lo_import '/home/peter/pictures/photo.xcf' 'a picture of me'</userinput>
-lo_import 152801
-</programlisting>
-        The response indicates that the large object received object
-        ID 152801, which can be used to access the newly-created large
-        object in the future. For the sake of readability, it is
-        recommended to always associate a human-readable comment with
-        every object. Both OIDs and comments can be viewed with the
-        <command>\lo_list</command> command.
-        </para>
-
-        <para>
-        Note that this command is subtly different from the server-side
-        <function>lo_import</function> because it acts as the local user
-        on the local file system, rather than the server's user and file
-        system.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\lo_list</literal></term>
-        <listitem>
-        <para>
-<!## PG>
-        Shows a list of all <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-        Shows a list of all <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-        Shows a list of all <productname>Postgres-XL</productname>
-<!## end>
-        large objects currently stored in the database,
-        along with any comments provided for them.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\lo_unlink <replaceable class="parameter">loid</replaceable></literal></term>
-
-        <listitem>
-        <para>
-        Deletes the large object with <acronym>OID</acronym>
-        <replaceable class="parameter">loid</replaceable> from the
-        database.
-        </para>
-
-        <tip>
-        <para>
-        Use <command>\lo_list</command> to find out the large object's
-        <acronym>OID</acronym>.
-        </para>
-        </tip>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\o</literal> [ {<replaceable class="parameter">filename</replaceable> | <literal>|</literal><replaceable class="parameter">command</replaceable>} ]</term>
-
-        <listitem>
-        <para>
-        Saves future query results to the file <replaceable
-        class="parameter">filename</replaceable> or pipes future results
-        into a separate Unix shell to execute <replaceable
-        class="parameter">command</replaceable>. If no arguments are
-        specified, the query output will be reset to the standard output.
-        </para>
-
-        <para>
-        <quote>Query results</quote> includes all tables, command
-        responses, and notices obtained from the database server, as
-        well as output of various backslash commands that query the
-        database (such as <command>\d</command>), but not error
-        messages.
-        </para>
-
-        <tip>
-        <para>
-        To intersperse text output in between query results, use
-        <command>\qecho</command>.
-        </para>
-        </tip>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\p</literal></term>
-        <listitem>
-        <para>
-        Print the current query buffer to the standard output.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\password [ <replaceable class="parameter">username</replaceable> ]</literal></term>
-        <listitem>
-        <para>
-        Changes the password of the specified user (by default, the current
-        user).  This command prompts for the new password, encrypts it, and
-        sends it to the server as an <command>ALTER ROLE</> command.  This
-        makes sure that the new password does not appear in cleartext in the
-        command history, the server log, or elsewhere.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\prompt [ <replaceable class="parameter">text</replaceable> ] <replaceable class="parameter">name</replaceable></literal></term>
-        <listitem>
-        <para>
-         Prompts the user to set variable <replaceable
-         class="parameter">name</>.  An optional prompt, <replaceable
-         class="parameter">text</>, can be specified.  (For multiword
-         prompts, use single quotes.)
-        </para>
-
-        <para>
-         By default, <literal>\prompt</> uses the terminal for input and
-         output.  However, if the <option>-f</> command line switch is
-         used, <literal>\prompt</> uses standard input and standard output.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\pset <replaceable class="parameter">option</replaceable> [ <replaceable class="parameter">value</replaceable> ]</literal></term>
-
-        <listitem>
-        <para>
-        This command sets options affecting the output of query result tables.
-        <replaceable class="parameter">option</replaceable>
-        indicates which option is to be set. The semantics of
-        <replaceable class="parameter">value</replaceable> vary depending
-        on the selected option.  For some options, omitting <replaceable
-        class="parameter">value</replaceable> causes the option to be toggled
-        or unset, as described under the particular option.  If no such
-        behavior is mentioned, then omitting
-        <replaceable class="parameter">value</replaceable> just results in
-        the current setting being displayed.
-        </para>
-
-        <para>
-        Adjustable printing options are:
-        <variablelist>
-          <varlistentry>
-          <term><literal>border</literal></term>
-          <listitem>
-          <para>
-          The <replaceable class="parameter">value</replaceable> must be a
-          number. In general, the higher
-          the number the more borders and lines the tables will have,
-          but this depends on the particular format. In
-          <acronym>HTML</acronym> format, this will translate directly
-          into the <literal>border=...</literal> attribute; in the
-          other formats only values 0 (no border), 1 (internal dividing lines),
-          and 2 (table frame) make sense.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>columns</literal></term>
-          <listitem>
-          <para>
-          Sets the target width for the <literal>wrapped</> format, and also
-          the width limit for determining whether output is wide enough to
-          require the pager.
-          Zero (the default) causes the target width to be controlled by the
-          environment variable <envar>COLUMNS</>, or the detected screen width
-          if <envar>COLUMNS</> is not set.
-          In addition, if <literal>columns</> is zero then the
-          <literal>wrapped</> format only affects screen output.
-          If <literal>columns</> is nonzero then file and pipe output is
-          wrapped to that width as well.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>expanded</literal> (or <literal>x</literal>)</term>
-          <listitem>
-          <para>
-          If <replaceable class="parameter">value</replaceable> is specified
-          it must be either <literal>on</literal> or <literal>off</literal>
-          which will enable or disable expanded mode.  If <replaceable
-          class="parameter">value</replaceable> is omitted the command toggles
-          between regular and expanded mode.
-          When expanded mode is enabled, query results
-          are displayed in two columns, with the column name on the left and
-          the data on the right. This mode is useful if the data wouldn't fit
-          on the screen in the normal <quote>horizontal</quote> mode.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>fieldsep</literal></term>
-          <listitem>
-          <para>
-          Specifies the field separator to be used in unaligned output
-          format. That way one can create, for example, tab- or
-          comma-separated output, which other programs might prefer. To
-          set a tab as field separator, type <literal>\pset fieldsep
-          '\t'</literal>. The default field separator is
-          <literal>'|'</literal> (a vertical bar).
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>footer</literal></term>
-          <listitem>
-          <para>
-          If <replaceable class="parameter">value</replaceable> is specified
-          it must be either <literal>on</literal> or <literal>off</literal>
-          which will enable or disable display of the table footer
-          (the <literal>(<replaceable>n</> rows)</literal> count).
-          If <replaceable class="parameter">value</replaceable> is omitted the
-          command toggles footer display on or off.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>format</literal></term>
-          <listitem>
-          <para>
-          Sets the output format to one of <literal>unaligned</literal>,
-          <literal>aligned</literal>, <literal>wrapped</literal>,
-          <literal>html</literal>,
-          <literal>latex</literal>, or <literal>troff-ms</literal>.
-          Unique abbreviations are allowed.  (That would mean one letter
-          is enough.)
-          </para>
-
-          <para>
-          <literal>unaligned</> format writes all columns of a row on one
-          line, separated by the currently active field separator. This
-          is useful for creating output that might be intended to be read
-          in by other programs (for example, tab-separated or comma-separated
-          format).
-          </para>
-
-          <para>
-          <literal>aligned</literal> format is the standard, human-readable,
-          nicely formatted text output;  this is the default.
-          </para>
-
-          <para>
-          <literal>wrapped</> format is like <literal>aligned</> but wraps
-          wide data values across lines to make the output fit in the target
-          column width.  The target width is determined as described under
-          the <literal>columns</> option.  Note that <application>psql</> will
-          not attempt to wrap column header titles; therefore,
-          <literal>wrapped</> format behaves the same as <literal>aligned</>
-          if the total width needed for column headers exceeds the target.
-          </para>
-
-          <para>
-          The <literal>html</>, <literal>latex</>, and <literal>troff-ms</>
-          formats put out tables that are intended to
-          be included in documents using the respective mark-up
-          language. They are not complete documents! (This might not be
-          so dramatic in <acronym>HTML</acronym>, but in LaTeX you must
-          have a complete document wrapper.)
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>linestyle</literal></term>
-          <listitem>
-          <para>
-          Sets the border line drawing style to one
-          of <literal>ascii</literal>, <literal>old-ascii</literal>
-          or <literal>unicode</literal>.
-          Unique abbreviations are allowed.  (That would mean one
-          letter is enough.)
-          The default setting is <literal>ascii</>.
-          This option only affects the <literal>aligned</> and
-          <literal>wrapped</> output formats.
-          </para>
-
-          <para>
-          <literal>ascii</literal> style uses plain <acronym>ASCII</acronym>
-          characters.  Newlines in data are shown using
-          a <literal>+</literal> symbol in the right-hand margin.
-          When the <literal>wrapped</literal> format wraps data from
-          one line to the next without a newline character, a dot
-          (<literal>.</>) is shown in the right-hand margin of the first line,
-          and again in the left-hand margin of the following line.
-          </para>
-
-          <para>
-          <literal>old-ascii</literal> style uses plain <acronym>ASCII</>
-          characters, using the formatting style used
-          in <productname>PostgreSQL</productname> 8.4 and earlier.
-          Newlines in data are shown using a <literal>:</literal>
-          symbol in place of the left-hand column separator.
-          When the data is wrapped from one line
-          to the next without a newline character, a <literal>;</>
-          symbol is used in place of the left-hand column separator.
-          </para>
-
-          <para>
-          <literal>unicode</literal> style uses Unicode box-drawing characters.
-          Newlines in data are shown using a carriage return symbol
-          in the right-hand margin.  When the data is wrapped from one line
-          to the next without a newline character, an ellipsis symbol
-          is shown in the right-hand margin of the first line, and
-          again in the left-hand margin of the following line.
-          </para>
-
-          <para>
-          When the <literal>border</> setting is greater than zero,
-          this option also determines the characters
-          with which the border lines are drawn.
-          Plain <acronym>ASCII</acronym> characters work everywhere, but
-          Unicode characters look nicer on displays that recognize them.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>null</literal></term>
-          <listitem>
-          <para>
-          Sets the string to be printed in place of a null value.
-          The default is to print nothing, which can easily be mistaken for
-          an empty string. For example, one might prefer <literal>\pset null
-          '(null)'</literal>.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>numericlocale</literal></term>
-          <listitem>
-          <para>
-          If <replaceable class="parameter">value</replaceable> is specified
-          it must be either <literal>on</literal> or <literal>off</literal>
-          which will enable or disable display of a locale-specific character
-          to separate groups of digits to the left of the decimal marker.
-          If <replaceable class="parameter">value</replaceable> is omitted the
-          command toggles between regular and locale-specific numeric output.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>pager</literal></term>
-          <listitem>
-          <para>
-          Controls use of a pager program for query and <application>psql</>
-          help output. If the environment variable <envar>PAGER</envar>
-          is set, the output is piped to the specified program.
-          Otherwise a platform-dependent default (such as
-          <filename>more</filename>) is used.
-          </para>
-
-          <para>
-          When the <literal>pager</> option is <literal>off</>, the pager
-          program is not used. When the <literal>pager</> option is
-          <literal>on</>, the pager is used when appropriate, i.e., when the
-          output is to a terminal and will not fit on the screen.
-          The <literal>pager</> option can also be set to <literal>always</>,
-          which causes the pager to be used for all terminal output regardless
-          of whether it fits on the screen.  <literal>\pset pager</>
-          without a <replaceable class="parameter">value</replaceable>
-          toggles pager use on and off.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>recordsep</literal></term>
-          <listitem>
-          <para>
-          Specifies the record (line) separator to use in unaligned
-          output format. The default is a newline character.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>tableattr</literal> (or <literal>T</literal>)</term>
-          <listitem>
-          <para>
-          Specifies attributes to be placed inside the
-          <acronym>HTML</acronym> <sgmltag>table</sgmltag> tag in
-          <literal>html</> output format. This
-          could for example be <literal>cellpadding</literal> or
-          <literal>bgcolor</literal>. Note that you probably don't want
-          to specify <literal>border</literal> here, as that is already
-          taken care of by <literal>\pset border</literal>.
-          If no
-          <replaceable class="parameter">value</replaceable> is given,
-          the table attributes are unset.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>title</literal></term>
-          <listitem>
-          <para>
-          Sets the table title for any subsequently printed tables. This
-          can be used to give your output descriptive tags. If no
-          <replaceable class="parameter">value</replaceable> is given,
-          the title is unset.
-          </para>
-          </listitem>
-          </varlistentry>
-
-          <varlistentry>
-          <term><literal>tuples_only</literal> (or <literal>t</literal>)</term>
-          <listitem>
-          <para>
-          If <replaceable class="parameter">value</replaceable> is specified
-          it must be either <literal>on</literal> or <literal>off</literal>
-          which will enable or disable tuples-only mode.
-          If <replaceable class="parameter">value</replaceable> is omitted the
-          command toggles between regular and tuples-only output.
-          Regular output includes extra information such
-          as column headers, titles, and various footers. In tuples-only
-          mode, only actual table data is shown.
-          </para>
-          </listitem>
-          </varlistentry>
-        </variablelist>
-        </para>
-
-        <para>
-        Illustrations of how these different formats look can be seen in
-        the <xref linkend="APP-PSQL-examples"
-        endterm="APP-PSQL-examples-title"> section.
-        </para>
-
-        <tip>
-        <para>
-        There are various shortcut commands for <command>\pset</command>. See
-        <command>\a</command>, <command>\C</command>, <command>\H</command>,
-        <command>\t</command>, <command>\T</command>, and <command>\x</command>.
-        </para>
-        </tip>
-
-        <note>
-        <para>
-        It is an error to call <command>\pset</command> without any
-        arguments. In the future this case might show the current status
-        of all printing options.
-        </para>
-        </note>
-
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\q</literal></term>
-        <listitem>
-        <para>
-        Quits the <application>psql</application> program.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\qecho <replaceable class="parameter">text</replaceable> [ ... ] </literal></term>
-        <listitem>
-        <para>
-        This command is identical to <command>\echo</command> except
-        that the output will be written to the query output channel, as
-        set by <command>\o</command>.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\r</literal></term>
-        <listitem>
-        <para>
-        Resets (clears) the query buffer.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\s [ <replaceable class="parameter">filename</replaceable> ]</literal></term>
-        <listitem>
-        <para>
-        Print or save the command line history to <replaceable
-        class="parameter">filename</replaceable>. If <replaceable
-        class="parameter">filename</replaceable> is omitted, the history
-        is written to the standard output. This option is only available
-        if <application>psql</application> is configured to use the
-        <acronym>GNU</acronym> <application>Readline</application> library.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\set [ <replaceable class="parameter">name</replaceable> [ <replaceable class="parameter">value</replaceable> [ ... ] ] ]</literal></term>
-
-        <listitem>
-        <para>
-        Sets the internal variable <replaceable
-        class="parameter">name</replaceable> to <replaceable
-        class="parameter">value</replaceable> or, if more than one value
-        is given, to the concatenation of all of them. If no second
-        argument is given, the variable is just set with no value. To
-        unset a variable, use the <command>\unset</command> command.
-        </para>
-
-        <para>
-        Valid variable names can contain characters, digits, and
-        underscores. See the section <xref
-        linkend="APP-PSQL-variables"
-        endterm="APP-PSQL-variables-title"> below for details.
-        Variable names are case-sensitive.
-        </para>
-
-        <para>
-        Although you are welcome to set any variable to anything you
-        want, <application>psql</application> treats several variables
-        as special. They are documented in the section about variables.
-        </para>
-
-        <note>
-        <para>
-        This command is totally separate from the <acronym>SQL</acronym>
-        command <xref linkend="SQL-SET">.
-        </para>
-        </note>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\sf[+] <replaceable class="parameter">function_description</> </literal></term>
-
-        <listitem>
-        <para>
-         This command fetches and shows the definition of the named function,
-         in the form of a <command>CREATE OR REPLACE FUNCTION</> command.
-         The definition is printed to the current query output channel,
-         as set by <command>\o</command>.
-        </para>
-
-        <para>
-         The target function can be specified by name alone, or by name
-         and arguments, for example <literal>foo(integer, text)</>.
-         The argument types must be given if there is more
-         than one function of the same name.
-        </para>
-
-        <para>
-         If <literal>+</literal> is appended to the command name, then the
-         output lines are numbered, with the first line of the function body
-         being line 1.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\t</literal></term>
-        <listitem>
-        <para>
-        Toggles the display of output column name headings and row count
-        footer. This command is equivalent to <literal>\pset
-        tuples_only</literal> and is provided for convenience.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\T <replaceable class="parameter">table_options</replaceable></literal></term>
-        <listitem>
-        <para>
-        Specifies attributes to be placed within the
-        <sgmltag>table</sgmltag> tag in <acronym>HTML</acronym>
-        output format. This command is equivalent to <literal>\pset
-        tableattr <replaceable
-        class="parameter">table_options</replaceable></literal>.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-       <term><literal>\timing [ <replaceable class="parameter">on</replaceable> | <replaceable class="parameter">off</replaceable> ]</literal></term>
-        <listitem>
-        <para>
-         Without parameter, toggles a display of how long each SQL statement
-         takes, in milliseconds.  With parameter, sets same.
-        </para>
-       </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\w</literal> <replaceable class="parameter">filename</replaceable></term>
-        <term><literal>\w</literal> <literal>|</><replaceable class="parameter">command</replaceable></term>
-        <listitem>
-        <para>
-        Outputs the current query buffer to the file <replaceable
-        class="parameter">filename</replaceable> or pipes it to the Unix
-        command <replaceable class="parameter">command</replaceable>.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\x</literal></term>
-        <listitem>
-        <para>
-        Toggles expanded table formatting mode. As such it is equivalent to
-        <literal>\pset expanded</literal>.
-       </para>
-       </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\z [ <link linkend="APP-PSQL-patterns"><replaceable class="parameter">pattern</replaceable></link> ]</literal></term>
-        <listitem>
-        <para>
-        Lists tables, views and sequences with their
-        associated access privileges.
-        If a <replaceable class="parameter">pattern</replaceable> is
-        specified, only tables, views and sequences whose names match the
-        pattern are listed.
-        </para>
-
-        <para>
-        This is an alias for <command>\dp</command> (<quote>display
-        privileges</quote>).
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\! [ <replaceable class="parameter">command</replaceable> ]</literal></term>
-        <listitem>
-        <para>
-        Escapes to a separate Unix shell or executes the Unix command
-        <replaceable class="parameter">command</replaceable>. The
-        arguments are not further interpreted; the shell will see them
-        as-is.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\?</literal></term>
-        <listitem>
-        <para>
-        Shows help information about the backslash commands.
-        </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </para>
-
-  <refsect3 id="APP-PSQL-patterns">
-   <title id="APP-PSQL-patterns-title">Patterns</title>
-
-   <indexterm>
-    <primary>patterns</primary>
-    <secondary>in psql and pg_dump</secondary>
-   </indexterm>
-&common;
-
-  <para>
-   The various <literal>\d</> commands accept a <replaceable
-   class="parameter">pattern</replaceable> parameter to specify the
-   object name(s) to be displayed.  In the simplest case, a pattern
-   is just the exact name of the object.  The characters within a
-   pattern are normally folded to lower case, just as in SQL names;
-   for example, <literal>\dt FOO</> will display the table named
-   <literal>foo</>.  As in SQL names, placing double quotes around
-   a pattern stops folding to lower case.  Should you need to include
-   an actual double quote character in a pattern, write it as a pair
-   of double quotes within a double-quote sequence; again this is in
-   accord with the rules for SQL quoted identifiers.  For example,
-   <literal>\dt "FOO""BAR"</> will display the table named
-   <literal>FOO"BAR</> (not <literal>foo"bar</>).  Unlike the normal
-   rules for SQL names, you can put double quotes around just part
-   of a pattern, for instance <literal>\dt FOO"FOO"BAR</> will display
-   the table named <literal>fooFOObar</>.
-  </para>
-
-  <para>
-   Whenever the <replaceable class="parameter">pattern</replaceable> parameter
-   is omitted completely, the <literal>\d</> commands display all objects
-   that are visible in the current schema search path &mdash; this is
-   equivalent to using <literal>*</> as the pattern.
-   (An object is said to be <firstterm>visible</> if its
-   containing schema is in the search path and no object of the same
-   kind and name appears earlier in the search path. This is equivalent to the
-   statement that the object can be referenced by name without explicit
-   schema qualification.)
-   To see all objects in the database regardless of visibility,
-   use <literal>*.*</> as the pattern.
-  </para>
-
-  <para>
-   Within a pattern, <literal>*</> matches any sequence of characters
-   (including no characters) and <literal>?</> matches any single character.
-   (This notation is comparable to Unix shell file name patterns.)
-   For example, <literal>\dt int*</> displays tables whose names
-   begin with <literal>int</>.  But within double quotes, <literal>*</>
-   and <literal>?</> lose these special meanings and are just matched
-   literally.
-  </para>
-
-  <para>
-   A pattern that contains a dot (<literal>.</>) is interpreted as a schema
-   name pattern followed by an object name pattern.  For example,
-   <literal>\dt foo*.*bar*</> displays all tables whose table name
-   includes <literal>bar</> that are in schemas whose schema name
-   starts with <literal>foo</>.  When no dot appears, then the pattern
-   matches only objects that are visible in the current schema search path.
-   Again, a dot within double quotes loses its special meaning and is matched
-   literally.
-  </para>
-
-  <para>
-   Advanced users can use regular-expression notations such as character
-   classes, for example <literal>[0-9]</> to match any digit.  All regular
-   expression special characters work as specified in
-   <xref linkend="functions-posix-regexp">, except for <literal>.</> which
-   is taken as a separator as mentioned above, <literal>*</> which is
-   translated to the regular-expression notation <literal>.*</>,
-   <literal>?</> which is translated to <literal>.</>, and
-   <literal>$</> which is matched literally.  You can emulate
-   these pattern characters at need by writing
-   <literal>?</> for <literal>.</>,
-   <literal>(<replaceable class="parameter">R</replaceable>+|)</literal> for
-   <literal><replaceable class="parameter">R</replaceable>*</literal>, or
-   <literal>(<replaceable class="parameter">R</replaceable>|)</literal> for
-   <literal><replaceable class="parameter">R</replaceable>?</literal>.
-   <literal>$</> is not needed as a regular-expression character since
-   the pattern must match the whole name, unlike the usual
-   interpretation of regular expressions (in other words, <literal>$</>
-   is automatically appended to your pattern).  Write <literal>*</> at the
-   beginning and/or end if you don't wish the pattern to be anchored.
-   Note that within double quotes, all regular expression special characters
-   lose their special meanings and are matched literally.  Also, the regular
-   expression special characters are matched literally in operator name
-   patterns (i.e., the argument of <literal>\do</>).
-  </para>
-  </refsect3>
- </refsect2>
-
- <refsect2>
-  <title>Advanced Features</title>
-
-&common;
-   <refsect3 id="APP-PSQL-variables">
-    <title id="APP-PSQL-variables-title">Variables</title>
-
-&common;
-    <para>
-    <application>psql</application> provides variable substitution
-    features similar to common Unix command shells.
-    Variables are simply name/value pairs, where the value
-    can be any string of any length. To set variables, use the
-    <application>psql</application> meta-command
-    <command>\set</command>:
-<programlisting>
-testdb=&gt; <userinput>\set foo bar</userinput>
-</programlisting>
-    sets the variable <literal>foo</literal> to the value
-    <literal>bar</literal>. To retrieve the content of the variable, precede
-    the name with a colon and use it as the argument of any slash
-    command:
-<programlisting>
-testdb=&gt; <userinput>\echo :foo</userinput>
-bar
-</programlisting>
-    </para>
-
-    <note>
-    <para>
-    The arguments of <command>\set</command> are subject to the same
-    substitution rules as with other commands. Thus you can construct
-    interesting references such as <literal>\set :foo
-    'something'</literal> and get <quote>soft links</quote> or
-    <quote>variable variables</quote> of <productname>Perl</productname>
-    or <productname><acronym>PHP</acronym></productname> fame,
-    respectively. Unfortunately (or fortunately?), there is no way to do
-    anything useful with these constructs. On the other hand,
-    <literal>\set bar :foo</literal> is a perfectly valid way to copy a
-    variable.
-    </para>
-    </note>
-
-    <para>
-    If you call <command>\set</command> without a second argument, the
-    variable is set, with an empty string as value. To unset (or delete) a
-    variable, use the command <command>\unset</command>.
-    </para>
-
-    <para>
-    <application>psql</application>'s internal variable names can
-    consist of letters, numbers, and underscores in any order and any
-    number of them. A number of these variables are treated specially
-    by <application>psql</application>. They indicate certain option
-    settings that can be changed at run time by altering the value of
-    the variable or that represent some state of the application. Although
-    you can use these variables for any other purpose, this is not
-    recommended, as the program behavior might grow really strange
-    really quickly. By convention, all specially treated variables
-    consist of all upper-case letters (and possibly numbers and
-    underscores). To ensure maximum compatibility in the future, avoid
-    using such variable names for your own purposes. A list of all specially
-    treated variables follows.
-   </para>
-
-    <variablelist>
-      <varlistentry>
-      <indexterm>
-       <primary>autocommit</primary>
-       <secondary>psql</secondary>
-      </indexterm>
-        <term><varname>AUTOCOMMIT</varname></term>
-        <listitem>
-        <para>
-        When <literal>on</> (the default), each SQL command is automatically
-        committed upon successful completion.  To postpone commit in this
-        mode, you must enter a <command>BEGIN</> or <command>START
-        TRANSACTION</> SQL command.  When <literal>off</> or unset, SQL
-        commands are not committed until you explicitly issue
-        <command>COMMIT</> or <command>END</>.  The autocommit-off
-        mode works by issuing an implicit <command>BEGIN</> for you, just
-        before any command that is not already in a transaction block and
-        is not itself a <command>BEGIN</> or other transaction-control
-        command, nor a command that cannot be executed inside a transaction
-        block (such as <command>VACUUM</>).
-        </para>
-
-        <note>
-        <para>
-         In autocommit-off mode, you must explicitly abandon any failed
-         transaction by entering <command>ABORT</> or <command>ROLLBACK</>.
-         Also keep in mind that if you exit the session
-         without committing, your work will be lost.
-        </para>
-        </note>
-
-        <note>
-        <para>
-<!## PG>
-         The autocommit-on mode is <productname>PostgreSQL</>'s traditional
-         behavior, but autocommit-off is closer to the SQL spec.  If you
-<!## end>
-<!## XC>
-         The autocommit-on mode is <productname>Postgres-XC</>'s traditional
-         behavior inherited from <productname>PostgreSQL</>, but autocommit-off is closer to the SQL spec.  If you
-<!## end>
-<!## XL>
-         The autocommit-on mode is <productname>Postgres-XL</>'s traditional
-         behavior inherited from <productname>PostgreSQL</>, but autocommit-off is closer to the SQL spec.  If you
-<!## end>
-         prefer autocommit-off, you might wish to set it in the system-wide
-         <filename>psqlrc</filename> file or your
-         <filename>~/.psqlrc</filename> file.
-        </para>
-        </note>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>DBNAME</varname></term>
-        <listitem>
-        <para>
-        The name of the database you are currently connected to. This is
-        set every time you connect to a database (including program
-        start-up), but can be unset.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>ECHO</varname></term>
-        <listitem>
-        <para>
-        If set to <literal>all</literal>, all lines
-        entered from the keyboard or from a script are written to the standard output
-        before they are parsed or executed. To select this behavior on program
-        start-up, use the switch <option>-a</option>. If set to
-        <literal>queries</literal>,
-        <application>psql</application> merely prints all queries as
-        they are sent to the server. The switch for this is
-        <option>-e</option>.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>ECHO_HIDDEN</varname></term>
-        <listitem>
-        <para>
-        When this variable is set and a backslash command queries the
-        database, the query is first shown. This way you can study the
-<!## PG>
-        <productname>PostgreSQL</productname> internals and provide
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> internals and provide
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> internals and provide
-<!## end>
-        similar functionality in your own programs. (To select this behavior
-        on program start-up, use the switch <option>-E</option>.)  If you set
-        the variable to the value <literal>noexec</literal>, the queries are
-        just shown but are not actually sent to the server and executed.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>EDITOR_LINENUMBER_SWITCH</varname></term>
-        <listitem>
-        <para>
-        When <command>\edit</command> or <command>\ef</command> is used with a
-        line number argument, this variable specifies the command-line switch
-        used to pass the line number to the user's editor.  For editors such
-        as <productname>emacs</> or <productname>vi</>, you can simply set
-        this variable to a plus sign.  Include a trailing space in the value
-        of the variable if there needs to be space between the switch name and
-        the line number.
-        Examples:
-
-<programlisting>
-\set EDITOR_LINENUMBER_SWITCH +
-\set EDITOR_LINENUMBER_SWITCH '--line '
-</programlisting>
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>ENCODING</varname></term>
-        <listitem>
-        <para>
-        The current client character set encoding.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>FETCH_COUNT</varname></term>
-        <listitem>
-        <para>
-        If this variable is set to an integer value &gt; 0,
-        the results of <command>SELECT</command> queries are fetched
-        and displayed in groups of that many rows, rather than the
-        default behavior of collecting the entire result set before
-        display.  Therefore only a
-        limited amount of memory is used, regardless of the size of
-        the result set.  Settings of 100 to 1000 are commonly used
-        when enabling this feature.
-        Keep in mind that when using this feature, a query might
-        fail after having already displayed some rows.
-        </para>
-        <tip>
-        <para>
-        Although you can use any output format with this feature,
-        the default <literal>aligned</> format tends to look bad
-        because each group of <varname>FETCH_COUNT</varname> rows
-        will be formatted separately, leading to varying column
-        widths across the row groups.  The other output formats work better.
-        </para>
-        </tip>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>HISTCONTROL</varname></term>
-        <listitem>
-        <para>
-         If this variable is set to <literal>ignorespace</literal>,
-         lines which begin with a space are not entered into the history
-         list. If set to a value of <literal>ignoredups</literal>, lines
-         matching the previous history line are not entered. A value of
-         <literal>ignoreboth</literal> combines the two options. If
-         unset, or if set to any other value than those above, all lines
-         read in interactive mode are saved on the history list.
-        </para>
-        <note>
-        <para>
-        This feature was shamelessly plagiarized from
-        <application>Bash</application>.
-        </para>
-        </note>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>HISTFILE</varname></term>
-        <listitem>
-        <para>
-        The file name that will be used to store the history list. The default
-        value is <filename>~/.psql_history</filename>.  For example, putting:
-<programlisting>
-\set HISTFILE ~/.psql_history- :DBNAME
-</programlisting>
-        in <filename>~/.psqlrc</filename> will cause
-        <application>psql</application> to maintain a separate history for
-        each database.
-        </para>
-        <note>
-        <para>
-        This feature was shamelessly plagiarized from
-        <application>Bash</application>.
-        </para>
-        </note>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>HISTSIZE</varname></term>
-        <listitem>
-        <para>
-        The number of commands to store in the command history. The
-        default value is 500.
-        </para>
-        <note>
-        <para>
-        This feature was shamelessly plagiarized from
-        <application>Bash</application>.
-        </para>
-        </note>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>HOST</varname></term>
-        <listitem>
-        <para>
-        The database server host you are currently connected to. This is
-        set every time you connect to a database (including program
-        start-up), but can be unset.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>IGNOREEOF</varname></term>
-        <listitem>
-        <para>
-         If unset, sending an <acronym>EOF</> character (usually
-         <keycombo action="simul"><keycap>Control</><keycap>D</></>)
-         to an interactive session of <application>psql</application>
-         will terminate the application. If set to a numeric value,
-         that many <acronym>EOF</> characters are ignored before the
-         application terminates.  If the variable is set but has no
-         numeric value, the default is 10.
-        </para>
-        <note>
-        <para>
-        This feature was shamelessly plagiarized from
-        <application>Bash</application>.
-        </para>
-        </note>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>LASTOID</varname></term>
-        <listitem>
-        <para>
-        The value of the last affected OID, as returned from an
-        <command>INSERT</command> or <command>\lo_import</command>
-        command. This variable is only guaranteed to be valid until
-        after the result of the next <acronym>SQL</acronym> command has
-        been displayed.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-      <indexterm>
-       <primary>rollback</primary>
-       <secondary>psql</secondary>
-      </indexterm>
-        <term><varname>ON_ERROR_ROLLBACK</varname></term>
-        <listitem>
-        <para>
-        When <literal>on</>, if a statement in a transaction block
-        generates an error, the error is ignored and the transaction
-        continues. When <literal>interactive</>, such errors are only
-        ignored in interactive sessions, and not when reading script
-        files. When <literal>off</> (the default), a statement in a
-        transaction block that generates an error aborts the entire
-        transaction. The on_error_rollback-on mode works by issuing an
-        implicit <command>SAVEPOINT</> for you, just before each command
-        that is in a transaction block, and rolls back to the savepoint
-        on error.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>ON_ERROR_STOP</varname></term>
-        <listitem>
-        <para>
-        By default, if non-interactive scripts encounter an error, such
-        as a malformed <acronym>SQL</acronym> command or internal
-        meta-command, processing continues. This has been the
-        traditional behavior of <application>psql</application> but it
-        is sometimes not desirable. If this variable is set, script
-        processing will immediately terminate. If the script was called
-        from another script it will terminate in the same fashion. If
-        the outermost script was not called from an interactive
-        <application>psql</application> session but rather using the
-        <option>-f</option> option, <application>psql</application> will
-        return error code 3, to distinguish this case from fatal error
-        conditions (error code 1).
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>PORT</varname></term>
-        <listitem>
-        <para>
-        The database server port to which you are currently connected.
-        This is set every time you connect to a database (including
-        program start-up), but can be unset.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>PROMPT1</varname></term>
-        <term><varname>PROMPT2</varname></term>
-        <term><varname>PROMPT3</varname></term>
-        <listitem>
-        <para>
-        These specify what the prompts <application>psql</application>
-        issues should look like. See <xref
-        linkend="APP-PSQL-prompting"
-        endterm="APP-PSQL-prompting-title"> below.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>QUIET</varname></term>
-        <listitem>
-        <para>
-        This variable is equivalent to the command line option
-        <option>-q</option>. It is probably not too useful in
-        interactive mode.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>SINGLELINE</varname></term>
-        <listitem>
-        <para>
-        This variable is equivalent to the command line option
-        <option>-S</option>.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>SINGLESTEP</varname></term>
-        <listitem>
-        <para>
-        This variable is equivalent to the command line option
-        <option>-s</option>.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>USER</varname></term>
-        <listitem>
-        <para>
-        The database user you are currently connected as. This is set
-        every time you connect to a database (including program
-        start-up), but can be unset.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>VERBOSITY</varname></term>
-        <listitem>
-        <para>
-        This variable can be set to the values <literal>default</>,
-        <literal>verbose</>, or <literal>terse</> to control the verbosity
-        of error reports.
-        </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-   </refsect3>
-
-   <refsect3>
-    <title><acronym>SQL</acronym> Interpolation</title>
-&common;
-
-    <para>
-    An additional useful feature of <application>psql</application>
-    variables is that you can substitute (<quote>interpolate</quote>)
-    them into regular <acronym>SQL</acronym> statements.
-    <application>psql</application> provides special facilities for
-    ensuring that values used as SQL literals and identifiers are
-    properly escaped.  The syntax for interpolating a value without
-    any special escaping is again to prepend the variable name with a colon
-    (<literal>:</literal>):
-<programlisting>
-testdb=&gt; <userinput>\set foo 'my_table'</userinput>
-testdb=&gt; <userinput>SELECT * FROM :foo;</userinput>
-</programlisting>
-    would then query the table <literal>my_table</literal>. Note that this
-    may be unsafe: the value of the variable is copied literally, so it can
-    even contain unbalanced quotes or backslash commands. You must make sure
-    that it makes sense where you put it.
-    </para>
-
-    <para>
-    When a value is to be used as an SQL literal or identifier, it is
-    safest to arrange for it to be escaped.  To escape the value of
-    a variable as an SQL literal, write a colon followed by the variable
-    name in single quotes.  To escape the value an SQL identifier, write
-    a colon followed by the variable name in double quotes.  The previous
-    example would be more safely written this way:
-<programlisting>
-testdb=&gt; <userinput>\set foo 'my_table'</userinput>
-testdb=&gt; <userinput>SELECT * FROM :"foo";</userinput>
-</programlisting>
-    Variable interpolation will not be performed into quoted
-    <acronym>SQL</acronym> entities.
-    </para>
-
-    <para>
-    One  possible use of this mechanism is to
-    copy the contents of a file into a table column. First load the file into a
-    variable and then proceed as above:
-<programlisting>
-testdb=&gt; <userinput>\set content `cat my_file.txt`</userinput>
-testdb=&gt; <userinput>INSERT INTO my_table VALUES (:'content');</userinput>
-</programlisting>
-    (Note that this still won't work if <filename>my_file.txt</filename> contains NUL bytes.
-    psql does not support embedded NUL bytes in variable values.)
-    </para>
-
-    <para>
-    Since colons can legally appear in SQL commands, an apparent attempt
-    at interpolation (such as <literal>:name</literal>,
-    <literal>:'name'</literal>, or <literal>:"name"</literal>) is not
-    changed unless the named variable is currently set. In any case, you
-    can escape a colon with a backslash to protect it from substitution.
-    (The colon syntax for variables is standard <acronym>SQL</acronym> for
-    embedded query languages, such as <application>ECPG</application>.
-    The colon syntax for array slices and type casts are
-<!## PG>
-    <productname>PostgreSQL</productname> extensions, hence the
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> extensions, hence the
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> extensions, hence the
-<!## end>
-    conflict.  The colon syntax for escaping a variable's value as an
-    SQL literal or identifier is a <application>psql</application>
-    extension.)
-    </para>
-
-   </refsect3>
-
-   <refsect3 id="APP-PSQL-prompting">
-    <title id="APP-PSQL-prompting-title">Prompting</title>
-&common;
-
-    <para>
-    The prompts <application>psql</application> issues can be customized
-    to your preference. The three variables <varname>PROMPT1</varname>,
-    <varname>PROMPT2</varname>, and <varname>PROMPT3</varname> contain strings
-    and special escape sequences that describe the appearance of the
-    prompt. Prompt 1 is the normal prompt that is issued when
-    <application>psql</application> requests a new command. Prompt 2 is
-    issued when more input is expected during command input because the
-    command was not terminated with a semicolon or a quote was not closed.
-    Prompt 3 is issued when you run an <acronym>SQL</acronym>
-    <command>COPY</command> command and you are expected to type in the
-    row values on the terminal.
-    </para>
-
-    <para>
-    The value of the selected prompt variable is printed literally,
-    except where a percent sign (<literal>%</literal>) is encountered.
-    Depending on the next character, certain other text is substituted
-    instead. Defined substitutions are:
-
-    <variablelist>
-      <varlistentry>
-        <term><literal>%M</literal></term>
-        <listitem>
-         <para>
-          The full host name (with domain name) of the database server,
-          or <literal>[local]</literal> if the connection is over a Unix
-          domain socket, or
-          <literal>[local:<replaceable>/dir/name</replaceable>]</literal>,
-          if the Unix domain socket is not at the compiled in default
-          location.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%m</literal></term>
-        <listitem>
-         <para>
-          The host name of the database server, truncated at the
-          first dot, or <literal>[local]</literal> if the connection is
-          over a Unix domain socket.
-         </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%&gt;</literal></term>
-        <listitem><para>The port number at which the database server is listening.</para></listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%n</literal></term>
-        <listitem>
-         <para>
-          The database session user name.  (The expansion of this
-          value might change during a database session as the result
-          of the command <command>SET SESSION
-          AUTHORIZATION</command>.)
-         </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%/</literal></term>
-        <listitem><para>The name of the current database.</para></listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%~</literal></term>
-        <listitem><para>Like <literal>%/</literal>, but the output is <literal>~</literal>
-         (tilde) if the database is your default database.</para></listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%#</literal></term>
-        <listitem>
-         <para>
-          If the session user is a database superuser, then a
-          <literal>#</literal>, otherwise a <literal>&gt;</literal>.
-          (The expansion of this value might change during a database
-          session as the result of the command <command>SET SESSION
-          AUTHORIZATION</command>.)
-         </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%R</literal></term>
-        <listitem>
-        <para>
-        In prompt 1 normally <literal>=</literal>, but <literal>^</literal> if
-        in single-line mode, and <literal>!</literal> if the session is
-        disconnected from the database (which can happen if
-        <command>\connect</command> fails). In prompt 2 the sequence is
-        replaced by <literal>-</literal>, <literal>*</literal>, a single quote,
-        a double quote, or a dollar sign, depending on whether
-        <application>psql</application> expects more input because the
-        command wasn't terminated yet, because you are inside a
-        <literal>/* ... */</literal> comment, or because you are inside
-        a quoted or dollar-escaped string. In prompt 3 the sequence doesn't
-        produce anything.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%x</literal></term>
-        <listitem>
-        <para>
-        Transaction status: an empty string when not in a transaction
-        block, or <literal>*</> when in a transaction block, or
-        <literal>!</> when in a failed transaction block, or <literal>?</>
-        when the transaction state is indeterminate (for example, because
-        there is no connection).
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%</literal><replaceable class="parameter">digits</replaceable></term>
-        <listitem>
-        <para>
-        The character with the indicated octal code is substituted.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%:</literal><replaceable class="parameter">name</replaceable><literal>:</literal></term>
-        <listitem>
-        <para>
-        The value of the <application>psql</application> variable
-        <replaceable class="parameter">name</replaceable>. See the
-        section <xref linkend="APP-PSQL-variables"
-        endterm="APP-PSQL-variables-title"> for details.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%`</literal><replaceable class="parameter">command</replaceable><literal>`</literal></term>
-        <listitem>
-        <para>
-        The output of <replaceable
-        class="parameter">command</replaceable>, similar to ordinary
-        <quote>back-tick</quote> substitution.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%[</literal> ... <literal>%]</literal></term>
-        <listitem>
-         <para>
-         Prompts can contain terminal control characters which, for
-         example, change the color, background, or style of the prompt
-         text, or change the title of the terminal window. In order for
-         the line editing features of <application>Readline</application> to work properly, these
-         non-printing control characters must be designated as invisible
-         by surrounding them with <literal>%[</literal> and
-         <literal>%]</literal>. Multiple pairs of these can occur within
-         the prompt.  For example:
-<programlisting>
-testdb=&gt; \set PROMPT1 '%[%033[1;33;40m%]%n@%/%R%[%033[0m%]%# '
-</programlisting>
-         results in a boldfaced (<literal>1;</literal>) yellow-on-black
-         (<literal>33;40</literal>) prompt on VT100-compatible, color-capable
-         terminals.
-        </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    To insert a percent sign into your prompt, write
-    <literal>%%</literal>. The default prompts are
-    <literal>'%/%R%# '</literal> for prompts 1 and 2, and
-    <literal>'&gt;&gt; '</literal> for prompt 3.
-    </para>
-
-    <note>
-    <para>
-    This feature was shamelessly plagiarized from
-    <application>tcsh</application>.
-    </para>
-    </note>
-
-   </refsect3>
-
-   <refsect3>
-    <title>Command-Line Editing</title>
-&common;
-
-    <para>
-    <application>psql</application> supports the <application>Readline</application>
-    library for convenient line editing and retrieval. The command
-    history is automatically saved when <application>psql</application>
-    exits and is reloaded when
-    <application>psql</application> starts up. Tab-completion is also
-    supported, although the completion logic makes no claim to be an
-    <acronym>SQL</acronym> parser.  If for some reason you do not like the tab completion, you
-    can turn it off by putting this in a file named
-    <filename>.inputrc</filename> in your home directory:
-<programlisting>
-$if psql
-set disable-completion on
-$endif
-</programlisting>
-    (This is not a <application>psql</application> but a
-    <application>Readline</application> feature. Read its documentation
-    for further details.)
-    </para>
-   </refsect3>
-  </refsect2>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-&common;
-
-  <variablelist>
-
-   <varlistentry>
-    <term><envar>COLUMNS</envar></term>
-
-    <listitem>
-     <para>
-      If <literal>\pset columns</> is zero, controls the
-      width for the <literal>wrapped</> format and width for determining
-      if wide output requires the pager.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PAGER</envar></term>
-
-    <listitem>
-     <para>
-      If the query results do not fit on the screen, they are piped
-      through this command.  Typical values are
-      <literal>more</literal> or <literal>less</literal>.  The default
-      is platform-dependent.  The use of the pager can be disabled by
-      using the <command>\pset</command> command.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PGDATABASE</envar></term>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters (see <xref linkend="libpq-envars">).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>PSQL_EDITOR</envar></term>
-    <term><envar>EDITOR</envar></term>
-    <term><envar>VISUAL</envar></term>
-
-    <listitem>
-     <para>
-      Editor used by the <command>\e</command> command.  The variables
-      are examined in the order listed; the first that is set is used.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>SHELL</envar></term>
-
-    <listitem>
-     <para>
-      Command executed by the <command>\!</command> command.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><envar>TMPDIR</envar></term>
-
-    <listitem>
-     <para>
-      Directory for storing temporary files.  The default is
-      <filename>/tmp</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-<!## PG>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-<!## end>
-<!## XC>
-   This utility, like most other <productname>Postgres-XC</> utilities,
-<!## end>
-<!## XL>
-   This utility, like most other <productname>Postgres-XL</> utilities,
-<!## end>
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Files</title>
-&common;
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Unless it is passed an <option>-X</option>
-     or <option>-c</option> option,
-     <application>psql</application> attempts to
-     read and execute commands from the system-wide
-     <filename>psqlrc</filename> file and the user's
-     <filename>~/.psqlrc</filename> file before starting up.
-     (On Windows, the user's startup file is named
-     <filename>%APPDATA%\postgresql\psqlrc.conf</filename>.)
-     See <filename><replaceable>PREFIX</>/share/psqlrc.sample</>
-     for information on setting up the system-wide file.  It could be used
-     to set up the client or the server to taste (using the <command>\set
-     </command> and <command>SET</command> commands).
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Both the system-wide <filename>psqlrc</filename> file and the user's
-     <filename>~/.psqlrc</filename> file can be made version-specific
-<!## PG>
-     by appending a dash and the <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-     by appending a dash and the <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-     by appending a dash and the <productname>Postgres-XL</productname>
-<!## end>
-     release number, for example <filename>~/.psqlrc-&version;</filename>.
-     A matching version-specific file will be read in preference to a
-     non-version-specific file.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The command-line history is stored in the file
-     <filename>~/.psql_history</filename>, or
-     <filename>%APPDATA%\postgresql\psql_history</filename> on Windows.
-    </para>
-   </listitem>
-  </itemizedlist>
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-&common;
-
-    <itemizedlist>
-      <listitem>
-      <para>
-       In an earlier life <application>psql</application> allowed the
-       first argument of a single-letter backslash command to start
-       directly after the command, without intervening whitespace.
-       As of <productname>PostgreSQL</productname> 8.4 this is no
-       longer allowed.
-      </para>
-      </listitem>
-
-      <listitem>
-      <para>
-       <application>psql</application> is only guaranteed to work smoothly
-       with servers of the same version. That does not mean other combinations
-       will fail outright, but subtle and not-so-subtle problems might come
-       up.  Backslash commands are particularly likely to fail if the
-       server is of a newer version than <application>psql</> itself.  However,
-       backslash commands of the <literal>\d</> family should work with
-       servers of versions back to 7.4, though not necessarily with servers
-       newer than  <application>psql</> itself.
-      </para>
-      </listitem>
-
-    </itemizedlist>
- </refsect1>
-
-<!## PG>
- <refsect1>
-  <title>Notes for Windows Users</title>
-
- <para>
-  <application>psql</application> is built as a <quote>console
-  application</>.  Since the Windows console windows use a different
-  encoding than the rest of the system, you must take special care
-  when using 8-bit characters within <application>psql</application>.
-  If <application>psql</application> detects a problematic
-  console code page, it will warn you at startup. To change the
-  console code page, two things are necessary:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Set the code page by entering <userinput>cmd.exe /c chcp
-      1252</userinput>. (1252 is a code page that is appropriate for
-      German; replace it with your value.) If you are using Cygwin,
-      you can put this command in <filename>/etc/profile</filename>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Set the console font to <literal>Lucida Console</>, because the
-      raster font does not work with the ANSI code page.
-     </para>
-    </listitem>
-   </itemizedlist>
- </para>
-
- </refsect1>
-<!## end>
-
- <refsect1 id="APP-PSQL-examples">
-  <title id="APP-PSQL-examples-title">Examples</title>
-&common;
-
-  <para>
-  The first example shows how to spread a command over several lines of
-  input. Notice the changing prompt:
-<programlisting>
-testdb=&gt; <userinput>CREATE TABLE my_table (</userinput>
-testdb(&gt; <userinput> first integer not null default 0,</userinput>
-testdb(&gt; <userinput> second text)</userinput>
-testdb-&gt; <userinput>;</userinput>
-CREATE TABLE
-</programlisting>
-  Now look at the table definition again:
-<programlisting>
-testdb=&gt; <userinput>\d my_table</userinput>
-             Table "my_table"
- Attribute |  Type   |      Modifier
------------+---------+--------------------
- first     | integer | not null default 0
- second    | text    |
-
-</programlisting>
-  Now we change the prompt to something more interesting:
-<programlisting>
-testdb=&gt; <userinput>\set PROMPT1 '%n@%m %~%R%# '</userinput>
-peter@localhost testdb=&gt;
-</programlisting>
-  Let's assume you have filled the table with data and want to take a
-  look at it:
-<programlisting>
-peter@localhost testdb=&gt; SELECT * FROM my_table;
- first | second
--------+--------
-     1 | one
-     2 | two
-     3 | three
-     4 | four
-(4 rows)
-
-</programlisting>
-  You can display tables in different ways by using the
-  <command>\pset</command> command:
-<programlisting>
-peter@localhost testdb=&gt; <userinput>\pset border 2</userinput>
-Border style is 2.
-peter@localhost testdb=&gt; <userinput>SELECT * FROM my_table;</userinput>
-+-------+--------+
-| first | second |
-+-------+--------+
-|     1 | one    |
-|     2 | two    |
-|     3 | three  |
-|     4 | four   |
-+-------+--------+
-(4 rows)
-
-peter@localhost testdb=&gt; <userinput>\pset border 0</userinput>
-Border style is 0.
-peter@localhost testdb=&gt; <userinput>SELECT * FROM my_table;</userinput>
-first second
------ ------
-    1 one
-    2 two
-    3 three
-    4 four
-(4 rows)
-
-peter@localhost testdb=&gt; <userinput>\pset border 1</userinput>
-Border style is 1.
-peter@localhost testdb=&gt; <userinput>\pset format unaligned</userinput>
-Output format is unaligned.
-peter@localhost testdb=&gt; <userinput>\pset fieldsep ","</userinput>
-Field separator is ",".
-peter@localhost testdb=&gt; <userinput>\pset tuples_only</userinput>
-Showing only tuples.
-peter@localhost testdb=&gt; <userinput>SELECT second, first FROM my_table;</userinput>
-one,1
-two,2
-three,3
-four,4
-</programlisting>
-  Alternatively, use the short commands:
-<programlisting>
-peter@localhost testdb=&gt; <userinput>\a \t \x</userinput>
-Output format is aligned.
-Tuples only is off.
-Expanded display is on.
-peter@localhost testdb=&gt; <userinput>SELECT * FROM my_table;</userinput>
--[ RECORD 1 ]-
-first  | 1
-second | one
--[ RECORD 2 ]-
-first  | 2
-second | two
--[ RECORD 3 ]-
-first  | 3
-second | three
--[ RECORD 4 ]-
-first  | 4
-second | four
-</programlisting>
-  </para>
-
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/reassign_owned.sgmlin b/doc-xc/src/sgml/ref/reassign_owned.sgmlin
deleted file mode 100644
index 9ca53ebcc2..0000000000
--- a/doc-xc/src/sgml/ref/reassign_owned.sgmlin
+++ /dev/null
@@ -1,132 +0,0 @@
-<!--
-doc/src/sgml/ref/reassign_owned.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-REASSIGN-OWNED">
- <refmeta>
-  <refentrytitle>REASSIGN OWNED</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>REASSIGN OWNED</refname>
-  <refpurpose>change the ownership of database objects owned by a database role</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-reassign-owned">
-  <primary>REASSIGN OWNED</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-REASSIGN OWNED BY <replaceable class="PARAMETER">old_role</replaceable> [, ...] TO <replaceable class="PARAMETER">new_role</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>REASSIGN OWNED</command> instructs the system to change
-   the ownership of the database objects owned by one of the
-   old_roles, to new_role.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">old_role</replaceable></term>
-    <listitem>
-     <para>
-      The name of a role. The ownership of all the objects in the
-      current database owned by this role will be reassigned to
-      <replaceable class="PARAMETER">new_role</replaceable>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">new_role</replaceable></term>
-    <listitem>
-     <para>
-      The name of the role that will be made the new owner of the
-      affected objects.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-&common;
-  <para>
-   <command>REASSIGN OWNED</command> is often used to prepare for the
-   removal of one or more roles. Because <command>REASSIGN
-   OWNED</command> only affects the objects in the current database,
-   it is usually necessary to execute this command in each database
-   that contains objects owned by a role that is to be removed.
-  </para>
-
-  <para>
-   <command>REASSIGN OWNED</command> requires privileges on both the
-   source role(s) and the target role.
-  </para>
-
-  <para>
-   The <xref linkend="sql-drop-owned"> command is an alternative that
-   drops all the database objects owned by one or more roles. Note
-   also that <command>DROP OWNED</command> requires privileges only
-   on the source role(s).
-  </para>
-
-  <para>
-   The <command>REASSIGN OWNED</command> command does not affect the
-   privileges granted to the old_roles in objects that are not owned
-   by them.  Use <command>DROP OWNED</command> to revoke those
-   privileges.
-  </para>
-
-  <para>
-   The <command>REASSIGN OWNED</command> command does not affect the
-   ownership of any databases owned by the role.  Use
-   <xref linkend="sql-alterdatabase"> to reassign that ownership.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-&common;
-  <para>
-   The <command>REASSIGN OWNED</command> statement is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension inherited from <productname>PostgreSQL</productname>.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension inherited from <productname>PostgreSQL</productname>.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-drop-owned"></member>
-   <member><xref linkend="sql-droprole"></member>
-   <member><xref linkend="sql-alterdatabase"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/reindex.sgmlin b/doc-xc/src/sgml/ref/reindex.sgmlin
deleted file mode 100644
index 5b93691813..0000000000
--- a/doc-xc/src/sgml/ref/reindex.sgmlin
+++ /dev/null
@@ -1,295 +0,0 @@
-<!--
-doc/src/sgml/ref/reindex.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-REINDEX">
- <refmeta>
-  <refentrytitle>REINDEX</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>REINDEX</refname>
-  <refpurpose>rebuild indexes</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-reindex">
-  <primary>REINDEX</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-REINDEX { INDEX | TABLE | DATABASE | SYSTEM } <replaceable class="PARAMETER">name</replaceable> [ FORCE ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>REINDEX</command> rebuilds an index using the data
-   stored in the index's table, replacing the old copy of the index. There are
-   several scenarios in which to use <command>REINDEX</command>:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      An index has become corrupted, and no longer contains valid
-      data. Although in theory this should never happen, in
-      practice indexes can become corrupted due to software bugs or
-      hardware failures.  <command>REINDEX</command> provides a
-      recovery method.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      An index has become <quote>bloated</>, that it is contains many
-      empty or nearly-empty pages.  This can occur with B-tree indexes in
-<!## PG>
-      <productname>PostgreSQL</productname> under certain uncommon access
-<!## end>
-<!## XC>
-      <productname>Postgres-XC</productname> under certain uncommon access
-<!## end>
-<!## XL>
-      <productname>Postgres-XL</productname> under certain uncommon access
-<!## end>
-      patterns. <command>REINDEX</command> provides a way to reduce
-      the space consumption of the index by writing a new version of
-      the index without the dead pages. See <xref
-      linkend="routine-reindex"> for more information.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      You have altered a storage parameter (such as fillfactor)
-      for an index, and wish to ensure that the change has taken full effect.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      An index build with the <literal>CONCURRENTLY</> option failed, leaving
-      an <quote>invalid</> index. Such indexes are useless but it can be
-      convenient to use <command>REINDEX</> to rebuild them. Note that
-      <command>REINDEX</> will not perform a concurrent build. To build the
-      index without interfering with production you should drop the index and
-      reissue the <command>CREATE INDEX CONCURRENTLY</> command.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-&common;
-  <variablelist>
-   <varlistentry>
-    <term><literal>INDEX</literal></term>
-    <listitem>
-     <para>
-      Recreate the specified index.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TABLE</literal></term>
-    <listitem>
-     <para>
-      Recreate all indexes of the specified table.  If the table has a
-      secondary <quote>TOAST</> table, that is reindexed as well.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DATABASE</literal></term>
-    <listitem>
-     <para>
-      Recreate all indexes within the current database.
-      Indexes on shared system catalogs are also processed.
-      This form of <command>REINDEX</command> cannot be executed inside a
-      transaction block.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SYSTEM</literal></term>
-    <listitem>
-     <para>
-      Recreate all indexes on system catalogs within the current database.
-      Indexes on shared system catalogs are included.
-      Indexes on user tables are not processed.
-      This form of <command>REINDEX</command> cannot be executed inside a
-      transaction block.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the specific index, table, or database to be
-      reindexed.  Index and table names can be schema-qualified.
-      Presently, <command>REINDEX DATABASE</> and <command>REINDEX SYSTEM</>
-      can only reindex the current database, so their parameter must match
-      the current database's name.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>FORCE</literal></term>
-    <listitem>
-     <para>
-      This is an obsolete option; it is ignored if specified.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-&common;
-  <para>
-   If you suspect corruption of an index on a user table, you can
-   simply rebuild that index, or all indexes on the table, using
-   <command>REINDEX INDEX</command> or <command>REINDEX TABLE</command>.
-  </para>
-
-  <para>
-   Things are more difficult if you need to recover from corruption of
-   an index on a system table.  In this case it's important for the
-   system to not have used any of the suspect indexes itself.
-   (Indeed, in this sort of scenario you might find that server
-   processes are crashing immediately at start-up, due to reliance on
-   the corrupted indexes.)  To recover safely, the server must be started
-   with the <option>-P</option> option, which prevents it from using
-   indexes for system catalog lookups.
-  </para>
-
-  <para>
-   One way to do this is to shut down the server and start a single-user
-<!## PG>
-   <productname>PostgreSQL</productname> server
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> servers
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> servers
-<!## end>
-   with the <option>-P</option> option included on its command line.
-   Then, <command>REINDEX DATABASE</>, <command>REINDEX SYSTEM</>,
-   <command>REINDEX TABLE</>, or <command>REINDEX INDEX</> can be
-   issued, depending on how much you want to reconstruct.  If in
-   doubt, use <command>REINDEX SYSTEM</> to select
-   reconstruction of all system indexes in the database.  Then quit
-   the single-user server session and restart the regular server.
-   See the <xref linkend="app-postgres"> reference page for more
-   information about how to interact with the single-user server
-   interface.
-  </para>
-
-  <para>
-   Alternatively, a regular server session can be started with
-   <option>-P</option> included in its command line options.
-   The method for doing this varies across clients, but in all
-   <application>libpq</>-based clients, it is possible to set
-   the <envar>PGOPTIONS</envar> environment variable to <literal>-P</>
-   before starting the client.  Note that while this method does not
-   require locking out other clients, it might still be wise to prevent
-   other users from connecting to the damaged database until repairs
-   have been completed.
-  </para>
-
-  <para>
-   <command>REINDEX</command> is similar to a drop and recreate of the index
-   in that the index contents are rebuilt from scratch.  However, the locking
-   considerations are rather different.  <command>REINDEX</> locks out writes
-   but not reads of the index's parent table.  It also takes an exclusive lock
-   on the specific index being processed, which will block reads that attempt
-   to use that index.  In contrast, <command>DROP INDEX</> momentarily takes
-   exclusive lock on the parent table, blocking both writes and reads.  The
-   subsequent <command>CREATE INDEX</> locks out writes but not reads; since
-   the index is not there, no read will attempt to use it, meaning that there
-   will be no blocking but reads might be forced into expensive sequential
-   scans.
-  </para>
-
-  <para>
-   Reindexing a single index or table requires being the owner of that
-   index or table.  Reindexing a database requires being the owner of
-   the database (note that the owner can therefore rebuild indexes of
-   tables owned by other users).  Of course, superusers can always
-   reindex anything.
-  </para>
-
-  <para>
-   Prior to <productname>PostgreSQL</productname> 8.1, <command>REINDEX
-   DATABASE</> processed only system indexes, not all indexes as one would
-   expect from the name.  This has been changed to reduce the surprise
-   factor.  The old behavior is available as <command>REINDEX SYSTEM</>.
-  </para>
-
-  <para>
-   Prior to <productname>PostgreSQL</productname> 7.4, <command>REINDEX
-   TABLE</> did not automatically process TOAST tables, and so those had
-   to be reindexed by separate commands.  This is still possible, but
-   redundant.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Rebuild a single index:
-
-<programlisting>
-REINDEX INDEX my_index;
-</programlisting>
-  </para>
-
-  <para>
-   Rebuild all the indexes on the table <literal>my_table</literal>:
-
-<programlisting>
-REINDEX TABLE my_table;
-</programlisting>
-  </para>
-
-  <para>
-   Rebuild all indexes in a particular database, without trusting the
-   system indexes to be valid already:
-
-<programlisting>
-$ <userinput>export PGOPTIONS="-P"</userinput>
-$ <userinput>psql broken_db</userinput>
-...
-broken_db=&gt; REINDEX DATABASE broken_db;
-broken_db=&gt; \q
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-&common;
-  <para>
-   There is no <command>REINDEX</command> command in the SQL standard.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/reindexdb.sgmlin b/doc-xc/src/sgml/ref/reindexdb.sgmlin
deleted file mode 100644
index 1b9a095d27..0000000000
--- a/doc-xc/src/sgml/ref/reindexdb.sgmlin
+++ /dev/null
@@ -1,382 +0,0 @@
-<!--
-doc/src/sgml/ref/reindexdb.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-REINDEXDB">
- <refmeta>
-  <refentrytitle><application>reindexdb</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
-<!## PG>
- <refnamediv>
-  <refname id="reindexdb">reindexdb</refname>
-  <refpurpose>reindex a <productname>PostgreSQL</productname> database</refpurpose>
- </refnamediv>
-<!## end>
-<!## XC>
- <refnamediv>
-  <refname id="reindexdb">reindexdb</refname>
-  <refpurpose>reindex a <productname>Postgres-XC</productname> database</refpurpose>
- </refnamediv>
-<!## end>
-<!## XL>
- <refnamediv>
-  <refname id="reindexdb">reindexdb</refname>
-  <refpurpose>reindex a <productname>Postgres-XL</productname> database</refpurpose>
- </refnamediv>
-<!## end>
-
- <indexterm zone="app-reindexdb">
-  <primary>reindexdb</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>reindexdb</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg>--table | -t <replaceable>table</replaceable> </arg>
-   <arg>--index | -i <replaceable>index</replaceable> </arg>
-   <arg><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>reindexdb</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg>--all | -a</arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>reindexdb</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <arg>--system | -s</arg>
-   <arg><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <application>reindexdb</application> is a utility for rebuilding indexes
-<!## PG>
-   in a <productname>PostgreSQL</productname> database.
-<!## end>
-<!## XC>
-   in a <productname>Postgres-XC</productname> database.
-<!## end>
-<!## XL>
-   in a <productname>Postgres-XL</productname> database.
-<!## end>
-  </para>
-
-  <para>
-   <application>reindexdb</application> is a wrapper around the SQL
-   command <xref linkend="SQL-REINDEX">.
-   There is no effective difference between reindexing databases via
-   this utility and via other methods for accessing the server.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-
-&common;
-
-   <para>
-    <application>reindexdb</application> accepts the following command-line arguments:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-a</></term>
-      <term><option>--all</></term>
-      <listitem>
-       <para>
-        Reindex all databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option><optional>-d</> <replaceable class="parameter">dbname</replaceable></></term>
-      <term><option><optional>--dbname=</><replaceable class="parameter">dbname</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the name of the database to be reindexed.
-        If this is not specified and <option>-a</option> (or
-        <option>--all</option>) is not used, the database name is read
-        from the environment variable <envar>PGDATABASE</envar>.  If
-        that is not set, the user name specified for the connection is
-        used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</></term>
-      <term><option>--echo</></term>
-      <listitem>
-       <para>
-        Echo the commands that <application>reindexdb</application> generates
-        and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-i <replaceable class="parameter">index</replaceable></></term>
-      <term><option>--index=<replaceable class="parameter">index</replaceable></></term>
-      <listitem>
-       <para>
-        Recreate <replaceable class="parameter">index</replaceable> only.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-q</></term>
-      <term><option>--quiet</></term>
-      <listitem>
-       <para>
-        Do not display progress messages.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</></term>
-      <term><option>--system</></term>
-      <listitem>
-       <para>
-        Reindex database's system catalogs.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t <replaceable class="parameter">table</replaceable></></term>
-      <term><option>--table=<replaceable class="parameter">table</replaceable></></term>
-      <listitem>
-       <para>
-        Reindex <replaceable class="parameter">table</replaceable> only.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    <varlistentry>
-      <term><option>-V</></term>
-      <term><option>--version</></term>
-      <listitem>
-       <para>
-       Print the <application>reindexdb</application> version and exit.
-       </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><option>-?</></term>
-      <term><option>--help</></term>
-      <listitem>
-      <para>
-      Show help about <application>reindexdb</application> command line
-      arguments, and exit.
-      </para>
-      </listitem>
-    </varlistentry>
-
-   </variablelist>
-
-   </para>
-
-   <para>
-    <application>reindexdb</application> also accepts
-    the following command-line arguments for connection parameters:
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the server is
-        running.  If the value begins with a slash, it is used as the
-        directory for the Unix domain socket.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server
-        is listening for connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-       <para>
-        Force <application>reindexdb</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>reindexdb</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>reindexdb</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-&common;
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATABASE</envar></term>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-<!## PG>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-<!## end>
-<!## XC>
-   This utility, like most other <productname>Postgres-XC</> utilities,
-<!## end>
-<!## XL>
-   This utility, like most other <productname>Postgres-XL</> utilities,
-<!## end>
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Diagnostics</title>
-&common;
-
-  <para>
-   In case of difficulty, see <xref linkend="SQL-REINDEX">
-   and <xref linkend="APP-PSQL"> for
-   discussions of potential problems and error messages.
-   The database server must be running at the
-   targeted host.  Also, any default connection settings and environment
-   variables used by the <application>libpq</application> front-end
-   library will apply.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-&common;
-
-  <para>
-   <application>reindexdb</application> might need to connect several
-<!## PG>
-   times to the <productname>PostgreSQL</productname> server, asking
-<!## end>
-<!## XC>
-   times to the <productname>Postgres-XC</productname> server, asking
-<!## end>
-<!## XL>
-   times to the <productname>Postgres-XL</productname> server, asking
-<!## end>
-   for a password each time. It is convenient to have a
-   <filename>~/.pgpass</> file in such cases. See <xref
-   linkend="libpq-pgpass"> for more information.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Examples</title>
-&common;
-
-   <para>
-    To reindex the database <literal>test</literal>:
-<screen>
-<prompt>$ </prompt><userinput>reindexdb test</userinput>
-</screen>
-   </para>
-
-   <para>
-    To reindex the table <literal>foo</literal> and the index
-    <literal>bar</literal> in a database named <literal>abcd</literal>:
-<screen>
-<prompt>$ </prompt><userinput>reindexdb --table foo --index bar abcd</userinput>
-</screen>
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-&common;
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-reindex"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/release_savepoint.sgmlin b/doc-xc/src/sgml/ref/release_savepoint.sgmlin
deleted file mode 100644
index 119fda70d8..0000000000
--- a/doc-xc/src/sgml/ref/release_savepoint.sgmlin
+++ /dev/null
@@ -1,149 +0,0 @@
-<!--
-doc/src/sgml/ref/release_savepoint.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-RELEASE-SAVEPOINT">
- <refmeta>
-  <refentrytitle>RELEASE SAVEPOINT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>RELEASE SAVEPOINT</refname>
-  <refpurpose>destroy a previously defined savepoint</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-release-savepoint">
-  <primary>RELEASE SAVEPOINT</primary>
- </indexterm>
-
- <indexterm zone="sql-release-savepoint">
-  <primary>savepoints</primary>
-  <secondary>releasing</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-RELEASE [ SAVEPOINT ] <replaceable>savepoint_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>RELEASE SAVEPOINT</command> is not supported by the
-   current release of <productname>Postgres-XC</productname>.
-  </para>
- </refsect1>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>RELEASE SAVEPOINT</command> is not supported by the
-   current release of <productname>Postgres-XL</productname>.
-  </para>
- </refsect1>
-<!## end>
-
-<!## PG>
-  <para>
-   <command>RELEASE SAVEPOINT</command> destroys a savepoint previously defined
-   in the current transaction.
-  </para>
-
-  <para>
-   Destroying a savepoint makes it unavailable as a rollback point,
-   but it has no other user visible behavior.  It does not undo the
-   effects of commands executed after the savepoint was established.
-   (To do that, see <xref linkend="sql-rollback-to">.)
-   Destroying a savepoint when
-   it is no longer needed allows the system to reclaim some resources
-   earlier than transaction end.
-  </para>
-
-  <para>
-   <command>RELEASE SAVEPOINT</command> also destroys all savepoints that were
-   established after the named savepoint was established.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable>savepoint_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the savepoint to destroy.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Specifying a savepoint name that was not previously defined is an error.
-  </para>
-
-  <para>
-   It is not possible to release a savepoint when the transaction is in
-   an aborted state.
-  </para>
-
-  <para>
-   If multiple savepoints have the same name, only the one that was most
-   recently defined is released.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To establish and later destroy a savepoint:
-<programlisting>
-BEGIN;
-    INSERT INTO table1 VALUES (3);
-    SAVEPOINT my_savepoint;
-    INSERT INTO table1 VALUES (4);
-    RELEASE SAVEPOINT my_savepoint;
-COMMIT;
-</programlisting>
-   The above transaction will insert both 3 and 4.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   This command conforms to the <acronym>SQL</> standard.  The standard
-   specifies that the key word <literal>SAVEPOINT</literal> is
-   mandatory, but <productname>PostgreSQL</productname> allows it to
-   be omitted.
-  </para>
- </refsect1>
-<!## end>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-begin"></member>
-   <member><xref linkend="sql-commit"></member>
-   <member><xref linkend="sql-rollback"></member>
-   <member><xref linkend="sql-rollback-to"></member>
-   <member><xref linkend="sql-savepoint"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/reset.sgmlin b/doc-xc/src/sgml/ref/reset.sgmlin
deleted file mode 100644
index 3bf6dfdcfd..0000000000
--- a/doc-xc/src/sgml/ref/reset.sgmlin
+++ /dev/null
@@ -1,124 +0,0 @@
-<!--
-doc/src/sgml/ref/reset.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-RESET">
- <refmeta>
-  <refentrytitle>RESET</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>RESET</refname>
-  <refpurpose>restore the value of a run-time parameter to the default value</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-reset">
-  <primary>RESET</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-RESET <replaceable class="PARAMETER">configuration_parameter</replaceable>
-RESET ALL
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>RESET</command> restores run-time parameters to their
-   default values.  <command>RESET</command> is an alternative
-   spelling for
-<synopsis>
-SET <replaceable class="parameter">configuration_parameter</replaceable> TO DEFAULT
-</synopsis>
-   Refer to <xref linkend="sql-set"> for
-   details.
-  </para>
-
-  <para>
-   The default value is defined as the value that the parameter would
-   have had, if no <command>SET</> had ever been issued for it in the
-   current session.  The actual source of this value might be a
-   compiled-in default, the configuration file, command-line options,
-   or per-database or per-user default settings.  This is subtly different
-   from defining it as <quote>the value that the parameter had at session
-   start</>, because if the value came from the configuration file, it
-   will be reset to whatever is specified by the configuration file now.
-   See <xref linkend="runtime-config"> for details.
-  </para>
-
-  <para>
-   The transactional behavior of <command>RESET</> is the same as
-   <command>SET</>: its effects will be undone by transaction rollback.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">configuration_parameter</replaceable></term>
-    <listitem>
-     <para>
-      Name of a settable run-time parameter.  Available parameters are
-      documented in <xref linkend="runtime-config"> and on the
-      <xref linkend="sql-set"> reference page.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ALL</literal></term>
-    <listitem>
-     <para>
-      Resets all settable run-time parameters to default values.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Set the <varname>timezone</> configuration variable to its default value:
-<screen>
-RESET timezone;
-</screen>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-<!## PG>
-   <command>RESET</command> is a <productname>PostgreSQL</productname> extension.
-<!## end>
-<!## XC>
-   <command>RESET</command> is a <productname>Postgres-XC</productname> extension.
-<!## end>
-<!## XL>
-   <command>RESET</command> is a <productname>Postgres-XL</productname> extension.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="SQL-SET"></member>
-   <member><xref linkend="SQL-SHOW"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/revoke.sgmlin b/doc-xc/src/sgml/ref/revoke.sgmlin
deleted file mode 100644
index 4b5acbf821..0000000000
--- a/doc-xc/src/sgml/ref/revoke.sgmlin
+++ /dev/null
@@ -1,298 +0,0 @@
-<!--
-doc/src/sgml/ref/revoke.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-REVOKE">
- <refmeta>
-  <refentrytitle>REVOKE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>REVOKE</refname>
-  <refpurpose>remove access privileges</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-revoke">
-  <primary>REVOKE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-REVOKE [ GRANT OPTION FOR ]
-    { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER }
-    [, ...] | ALL [ PRIVILEGES ] }
-    ON { [ TABLE ] <replaceable class="PARAMETER">table_name</replaceable> [, ...]
-         | ALL TABLES IN SCHEMA <replaceable>schema_name</replaceable> [, ...] }
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { { SELECT | INSERT | UPDATE | REFERENCES } ( <replaceable class="PARAMETER">column</replaceable> [, ...] )
-    [, ...] | ALL [ PRIVILEGES ] ( <replaceable class="PARAMETER">column</replaceable> [, ...] ) }
-    ON [ TABLE ] <replaceable class="PARAMETER">table_name</replaceable> [, ...]
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { { USAGE | SELECT | UPDATE }
-    [, ...] | ALL [ PRIVILEGES ] }
-    ON { SEQUENCE <replaceable class="PARAMETER">sequence_name</replaceable> [, ...]
-         | ALL SEQUENCES IN SCHEMA <replaceable>schema_name</replaceable> [, ...] }
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { { CREATE | CONNECT | TEMPORARY | TEMP } [, ...] | ALL [ PRIVILEGES ] }
-    ON DATABASE <replaceable>database_name</replaceable> [, ...]
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { USAGE | ALL [ PRIVILEGES ] }
-    ON FOREIGN DATA WRAPPER <replaceable>fdw_name</replaceable> [, ...]
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { USAGE | ALL [ PRIVILEGES ] }
-    ON FOREIGN SERVER <replaceable>server_name</replaceable> [, ...]
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { EXECUTE | ALL [ PRIVILEGES ] }
-    ON { FUNCTION <replaceable>function_name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">arg_name</replaceable> ] <replaceable class="parameter">arg_type</replaceable> [, ...] ] ) [, ...]
-         | ALL FUNCTIONS IN SCHEMA <replaceable>schema_name</replaceable> [, ...] }
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { USAGE | ALL [ PRIVILEGES ] }
-    ON LANGUAGE <replaceable>lang_name</replaceable> [, ...]
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { { SELECT | UPDATE } [, ...] | ALL [ PRIVILEGES ] }
-    ON LARGE OBJECT <replaceable class="PARAMETER">loid</replaceable> [, ...]
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { { CREATE | USAGE } [, ...] | ALL [ PRIVILEGES ] }
-    ON SCHEMA <replaceable>schema_name</replaceable> [, ...]
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ GRANT OPTION FOR ]
-    { CREATE | ALL [ PRIVILEGES ] }
-    ON TABLESPACE <replaceable>tablespace_name</replaceable> [, ...]
-    FROM { [ GROUP ] <replaceable class="PARAMETER">role_name</replaceable> | PUBLIC } [, ...]
-    [ CASCADE | RESTRICT ]
-
-REVOKE [ ADMIN OPTION FOR ]
-    <replaceable class="PARAMETER">role_name</replaceable> [, ...] FROM <replaceable class="PARAMETER">role_name</replaceable> [, ...]
-    [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="SQL-REVOKE-description">
-  <title>Description</title>
-
-&common;
-
-  <para>
-   The <command>REVOKE</command> command revokes previously granted
-   privileges from one or more roles.  The key word
-   <literal>PUBLIC</literal> refers to the implicitly defined group of
-   all roles.
-  </para>
-
-  <para>
-   See the description of the <xref linkend="sql-grant"> command for
-   the meaning of the privilege types.
-  </para>
-
-  <para>
-   Note that any particular role will have the sum
-   of privileges granted directly to it, privileges granted to any role it
-   is presently a member of, and privileges granted to
-   <literal>PUBLIC</literal>.  Thus, for example, revoking <literal>SELECT</> privilege
-   from <literal>PUBLIC</literal> does not necessarily mean that all roles
-   have lost <literal>SELECT</> privilege on the object: those who have it granted
-   directly or via another role will still have it.  Similarly, revoking
-   <literal>SELECT</> from a user might not prevent that user from using
-   <literal>SELECT</> if <literal>PUBLIC</literal> or another membership
-   role still has <literal>SELECT</> rights.
-  </para>
-
-  <para>
-   If <literal>GRANT OPTION FOR</literal> is specified, only the grant
-   option for the privilege is revoked, not the privilege itself.
-   Otherwise, both the privilege and the grant option are revoked.
-  </para>
-
-  <para>
-   If a user holds a privilege with grant option and has granted it to
-   other users then the privileges held by those other users are
-   called dependent privileges. If the privilege or the grant option
-   held by the first user is being revoked and dependent privileges
-   exist, those dependent privileges are also revoked if
-   <literal>CASCADE</literal> is specified; if it is not, the revoke action
-   will fail.  This recursive revocation only affects privileges that
-   were granted through a chain of users that is traceable to the user
-   that is the subject of this <literal>REVOKE</literal> command.
-   Thus, the affected users might effectively keep the privilege if it
-   was also granted through other users.
-  </para>
-
-  <para>
-   When revoking privileges on a table, the corresponding column privileges
-   (if any) are automatically revoked on each column of the table, as well.
-  </para>
-
-  <para>
-   When revoking membership in a role, <literal>GRANT OPTION</> is instead
-   called <literal>ADMIN OPTION</>, but the behavior is similar.
-   Note also that this form of the command does not
-   allow the noise word <literal>GROUP</>.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-REVOKE-notes">
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="app-psql">'s <command>\dp</command> command to
-   display the privileges granted on existing tables and columns.  See <xref
-   linkend="sql-grant"> for information about the
-   format.  For non-table objects there are other <command>\d</> commands
-   that can display their privileges.
-  </para>
-
-  <para>
-   A user can only revoke privileges that were granted directly by
-   that user.  If, for example, user A has granted a privilege with
-   grant option to user B, and user B has in turned granted it to user
-   C, then user A cannot revoke the privilege directly from C.
-   Instead, user A could revoke the grant option from user B and use
-   the <literal>CASCADE</literal> option so that the privilege is
-   in turn revoked from user C.  For another example, if both A and B
-   have granted the same privilege to C, A can revoke his own grant
-   but not B's grant, so C will still effectively have the privilege.
-  </para>
-
-   <para>
-    When a non-owner of an object attempts to <command>REVOKE</> privileges
-    on the object, the command will fail outright if the user has no
-    privileges whatsoever on the object.  As long as some privilege is
-    available, the command will proceed, but it will revoke only those
-    privileges for which the user has grant options.  The <command>REVOKE ALL
-    PRIVILEGES</> forms will issue a warning message if no grant options are
-    held, while the other forms will issue a warning if grant options for
-    any of the privileges specifically named in the command are not held.
-    (In principle these statements apply to the object owner as well, but
-    since the owner is always treated as holding all grant options, the
-    cases can never occur.)
-   </para>
-
-   <para>
-    If a superuser chooses to issue a <command>GRANT</> or <command>REVOKE</>
-    command, the command is performed as though it were issued by the
-    owner of the affected object.  Since all privileges ultimately come
-    from the object owner (possibly indirectly via chains of grant options),
-    it is possible for a superuser to revoke all privileges, but this might
-    require use of <literal>CASCADE</literal> as stated above.
-   </para>
-
-   <para>
-    <command>REVOKE</> can also be done by a role
-    that is not the owner of the affected object, but is a member of the role
-    that owns the object, or is a member of a role that holds privileges
-    <literal>WITH GRANT OPTION</literal> on the object.  In this case the
-    command is performed as though it were issued by the containing role that
-    actually owns the object or holds the privileges
-    <literal>WITH GRANT OPTION</literal>.  For example, if table
-    <literal>t1</> is owned by role <literal>g1</>, of which role
-    <literal>u1</> is a member, then <literal>u1</> can revoke privileges
-    on <literal>t1</> that are recorded as being granted by <literal>g1</>.
-    This would include grants made by <literal>u1</> as well as by other
-    members of role <literal>g1</>.
-   </para>
-
-   <para>
-    If the role executing <command>REVOKE</> holds privileges
-    indirectly via more than one role membership path, it is unspecified
-    which containing role will be used to perform the command.  In such cases
-    it is best practice to use <command>SET ROLE</> to become the specific
-    role you want to do the <command>REVOKE</> as.  Failure to do so might
-    lead to revoking privileges other than the ones you intended, or not
-    revoking anything at all.
-   </para>
- </refsect1>
-
- <refsect1 id="SQL-REVOKE-examples">
-  <title>Examples</title>
-
-  <para>
-   Revoke insert privilege for the public on table
-   <literal>films</literal>:
-
-<programlisting>
-REVOKE INSERT ON films FROM PUBLIC;
-</programlisting>
-  </para>
-
-  <para>
-   Revoke all privileges from user <literal>manuel</literal> on view
-   <literal>kinds</literal>:
-
-<programlisting>
-REVOKE ALL PRIVILEGES ON kinds FROM manuel;
-</programlisting>
-
-   Note that this actually means <quote>revoke all privileges that I
-   granted</>.
-  </para>
-
-  <para>
-   Revoke membership in role <literal>admins</> from user <literal>joe</>:
-
-<programlisting>
-REVOKE admins FROM joe;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-REVOKE-compatibility">
-  <title>Compatibility</title>
-
-   <para>
-    The compatibility notes of the <xref linkend="sql-grant"> command
-    apply analogously to <command>REVOKE</command>.
-    The keyword <literal>RESTRICT</literal> or <literal>CASCADE</literal>
-<!## PG>
-    is required according to the standard, but <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-    is required according to the standard, but <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-    is required according to the standard, but <productname>Postgres-XL</>
-<!## end>
-    assumes <literal>RESTRICT</literal> by default.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simpara>
-   <xref linkend="sql-grant">
-  </simpara>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/rollback.sgmlin b/doc-xc/src/sgml/ref/rollback.sgmlin
deleted file mode 100644
index 31a7fa5c7c..0000000000
--- a/doc-xc/src/sgml/ref/rollback.sgmlin
+++ /dev/null
@@ -1,99 +0,0 @@
-<!--
-doc/src/sgml/ref/rollback.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ROLLBACK">
- <refmeta>
-  <refentrytitle>ROLLBACK</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ROLLBACK</refname>
-  <refpurpose>abort the current transaction</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-rollback">
-  <primary>ROLLBACK</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ROLLBACK [ WORK | TRANSACTION ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>ROLLBACK</command> rolls back the current transaction and causes
-   all the updates made by the transaction to be discarded.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>WORK</literal></term>
-    <term><literal>TRANSACTION</literal></term>
-    <listitem>
-     <para>
-      Optional key words. They have no effect.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-COMMIT"> to
-   successfully terminate a transaction.
-  </para>
-
-  <para>
-   Issuing <command>ROLLBACK</> when not inside a transaction does
-   no harm, but it will provoke a warning message.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To abort all changes:
-<programlisting>
-ROLLBACK;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard only specifies the two forms
-   <literal>ROLLBACK</literal> and <literal>ROLLBACK
-   WORK</literal>. Otherwise, this command is fully conforming.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-begin"></member>
-   <member><xref linkend="sql-commit"></member>
-   <member><xref linkend="sql-rollback-to"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/rollback_prepared.sgmlin b/doc-xc/src/sgml/ref/rollback_prepared.sgmlin
deleted file mode 100644
index a744922887..0000000000
--- a/doc-xc/src/sgml/ref/rollback_prepared.sgmlin
+++ /dev/null
@@ -1,132 +0,0 @@
-<!--
-doc/src/sgml/ref/rollback_prepared.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ROLLBACK-PREPARED">
- <refmeta>
-  <refentrytitle>ROLLBACK PREPARED</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ROLLBACK PREPARED</refname>
-  <refpurpose>cancel a transaction that was earlier prepared for two-phase commit</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-rollback-prepared">
-  <primary>ROLLBACK PREPARED</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ROLLBACK PREPARED <replaceable class="PARAMETER">transaction_id</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-<!-- NOTICE:
-     Make sure if this propagates to involved nodes -> Michael 
--->
-
-  <para>
-   <command>ROLLBACK PREPARED</command> rolls back a transaction that is in
-   prepared state.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">transaction_id</replaceable></term>
-    <listitem>
-     <para>
-      The transaction identifier of the transaction that is to be
-      rolled back.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   To roll back a prepared transaction, you must be either the same user that
-   executed the transaction originally, or a superuser.  But you do not
-   have to be in the same session that executed the transaction.
-  </para>
-
-  <para>
-   This command cannot be executed inside a transaction block. The prepared
-   transaction is rolled back immediately.
-  </para>
-
-  <para>
-   All currently available prepared transactions are listed in the
-   <link linkend="view-pg-prepared-xacts"><structname>pg_prepared_xacts</structname></link>
-   system view.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   If more than one Datanode and/or Coordinator are involved in the
-   transaction, <command>ROLLBACK PREPARED</> command will propagate to
-   all these nodes.
-  </para>
-&xconly;
-  <para>
-   If <literal>xc_maintenance_mode</literal> GUC parameter is set to <literal>ON</literal>, <command>ROLLBACK PREPARED</command> will not propagate to other nodes.   It just runs locally and report the result to <literal>GTM</literal>.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   If more than one Datanode and/or Coordinator are involved in the
-   transaction, the <command>ROLLBACK PREPARED</> command will propagate to
-   all the nodes involved.
-  </para>
-&xlonly;
-  <para>
-   If <literal>xc_maintenance_mode</literal> GUC parameter is set to <literal>ON</literal>, <command>ROLLBACK PREPARED</command> will not propagate to other nodes.   It just runs locally and report the result to <literal>GTM</literal>.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1 id="sql-rollback-prepared-examples">
-  <title id="sql-rollback-prepared-examples-title">Examples</title>
-  <para>
-   Roll back the transaction identified by the transaction
-   identifier <literal>foobar</>:
-
-<programlisting>
-ROLLBACK PREPARED 'foobar';
-</programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-prepare-transaction"></member>
-   <member><xref linkend="sql-commit-prepared"></member>
-<!## XC>
-   <member><xref linkend="guc-xc-maintenance-mode"></member>
-<!## end>
-<!## XL>
-   <member><xref linkend="guc-xc-maintenance-mode"></member>
-<!## end>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/rollback_to.sgmlin b/doc-xc/src/sgml/ref/rollback_to.sgmlin
deleted file mode 100644
index 6ee1972860..0000000000
--- a/doc-xc/src/sgml/ref/rollback_to.sgmlin
+++ /dev/null
@@ -1,177 +0,0 @@
-<!--
-doc/src/sgml/ref/rollback_to.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ROLLBACK-TO">
- <refmeta>
-  <refentrytitle>ROLLBACK TO SAVEPOINT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ROLLBACK TO SAVEPOINT</refname>
-  <refpurpose>roll back to a savepoint</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-rollback-to">
-  <primary>ROLLBACK TO SAVEPOINT</primary>
- </indexterm>
-
- <indexterm zone="sql-rollback-to">
-  <primary>savepoints</primary>
-  <secondary>rolling back</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-ROLLBACK [ WORK | TRANSACTION ] TO [ SAVEPOINT ] <replaceable>savepoint_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>ROLLBACK TO</> has not been supported
-   by <productname>Postgres-XC</> yet.  This may be supported in the
-   future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>ROLLBACK TO</> is not yet supported
-   in <productname>Postgres-XL</>.  This may be supported in the
-   future releases.
-  </para>
-<!## end>
-<!## PG>
-  <para>
-   Roll back all commands that were executed after the savepoint was
-   established.  The savepoint remains valid and can be rolled back to
-   again later, if needed.
-  </para>
-
-  <para>
-   <command>ROLLBACK TO SAVEPOINT</> implicitly destroys all savepoints that
-   were established after the named savepoint.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">savepoint_name</></term>
-    <listitem>
-     <para>
-      The savepoint to roll back to.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-RELEASE-SAVEPOINT"
-  > to destroy a savepoint without
-   discarding the effects of commands executed after it was established.
-  </para>
-
-  <para>
-   Specifying a savepoint name that has not been established is an error.
-  </para>
-
-  <para>
-   Cursors have somewhat non-transactional behavior with respect to
-   savepoints.  Any cursor that is opened inside a savepoint will be closed
-   when the savepoint is rolled back.  If a previously opened cursor is
-   affected by a <command>FETCH</> or <command>MOVE</> command inside a
-   savepoint that is later rolled back, the cursor remains at the
-   position that <command>FETCH</> left it pointing to (that is, the cursor
-   motion caused by <command>FETCH</> is not rolled back).
-   Closing a cursor is not undone by rolling back, either.
-   However, other side-effects caused by the cursor's query (such as
-   side-effects of volatile functions called by the query) <emphasis>are</>
-   rolled back if they occur during a savepoint that is later rolled back.
-   A cursor whose execution causes a transaction to abort is put in a
-   cannot-execute state, so while the transaction can be restored using
-   <command>ROLLBACK TO SAVEPOINT</>, the cursor can no longer be used.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To undo the effects of the commands executed after <literal>my_savepoint</literal>
-   was established:
-<programlisting>
-ROLLBACK TO SAVEPOINT my_savepoint;
-</programlisting>
-  </para>
-
-  <para>
-   Cursor positions are not affected by savepoint rollback:
-<programlisting>
-BEGIN;
-
-DECLARE foo CURSOR FOR SELECT 1 UNION SELECT 2;
-
-SAVEPOINT foo;
-
-FETCH 1 FROM foo;
- ?column? 
-----------
-        1
-
-ROLLBACK TO SAVEPOINT foo;
-
-FETCH 1 FROM foo;
- ?column? 
-----------
-        2
-
-COMMIT;
-</programlisting>
-   </para>
-
-
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The <acronym>SQL</> standard specifies that the key word
-   <literal>SAVEPOINT</> is mandatory, but <productname>PostgreSQL</>
-   and <productname>Oracle</> allow it to be omitted.  SQL allows
-   only <literal>WORK</>, not <literal>TRANSACTION</>, as a noise word
-   after <literal>ROLLBACK</>.  Also, SQL has an optional clause
-   <literal>AND [ NO ] CHAIN</> which is not currently supported by
-   <productname>PostgreSQL</>.  Otherwise, this command conforms to
-   the SQL standard.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-begin"></member>
-   <member><xref linkend="sql-commit"></member>
-   <member><xref linkend="sql-release-savepoint"></member>
-   <member><xref linkend="sql-rollback"></member>
-   <member><xref linkend="sql-savepoint"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/savepoint.sgmlin b/doc-xc/src/sgml/ref/savepoint.sgmlin
deleted file mode 100644
index db759a28d2..0000000000
--- a/doc-xc/src/sgml/ref/savepoint.sgmlin
+++ /dev/null
@@ -1,155 +0,0 @@
-<!--
-doc/src/sgml/ref/savepoint.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SAVEPOINT">
- <refmeta>
-  <refentrytitle>SAVEPOINT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SAVEPOINT</refname>
-  <refpurpose>define a new savepoint within the current transaction</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-savepoint">
-  <primary>SAVEPOINT</primary>
- </indexterm>
-
- <indexterm zone="sql-savepoint">
-  <primary>savepoints</primary>
-  <secondary>defining</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SAVEPOINT <replaceable>savepoint_name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>SAVEPOINT</> is not yet supported
-   by <productname>Postgres-XC</>.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>SAVEPOINT</> has not been supported
-   by <productname>Postgres-XL</> yet.  This command may be supported
-   in the future releases.
-  </para>
-<!## end>
-<!## PG>
-  <para>
-   <command>SAVEPOINT</command> establishes a new savepoint within
-   the current transaction.
-  </para>
-
-  <para>
-   A savepoint is a special mark inside a transaction that allows all commands
-   that are executed after it was established to be rolled back, restoring
-   the transaction state to what it was at the time of the savepoint.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable>savepoint_name</replaceable></term>
-    <listitem>
-     <para>
-      The name to give to the new savepoint.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-ROLLBACK-TO"> to
-   rollback to a savepoint.  Use <xref linkend="SQL-RELEASE-SAVEPOINT">
-   to destroy a savepoint, keeping
-   the effects of commands executed after it was established.
-  </para>
-
-  <para>
-   Savepoints can only be established when inside a transaction block.
-   There can be multiple savepoints defined within a transaction.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To establish a savepoint and later undo the effects of all commands executed
-   after it was established:
-<programlisting>
-BEGIN;
-    INSERT INTO table1 VALUES (1);
-    SAVEPOINT my_savepoint;
-    INSERT INTO table1 VALUES (2);
-    ROLLBACK TO SAVEPOINT my_savepoint;
-    INSERT INTO table1 VALUES (3);
-COMMIT;
-</programlisting>
-   The above transaction will insert the values 1 and 3, but not 2.
-  </para>
-
-  <para>
-   To establish and later destroy a savepoint:
-<programlisting>
-BEGIN;
-    INSERT INTO table1 VALUES (3);
-    SAVEPOINT my_savepoint;
-    INSERT INTO table1 VALUES (4);
-    RELEASE SAVEPOINT my_savepoint;
-COMMIT;
-</programlisting>
-   The above transaction will insert both 3 and 4.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   SQL requires a savepoint to be destroyed automatically when another
-   savepoint with the same name is established.  In
-   <productname>PostgreSQL</>, the old savepoint is kept, though only the more
-   recent one will be used when rolling back or releasing.  (Releasing the
-   newer savepoint with <command>RELEASE SAVEPOINT</> will cause the older one
-   to again become accessible to <command>ROLLBACK TO SAVEPOINT</> and
-   <command>RELEASE SAVEPOINT</>.) Otherwise, <command>SAVEPOINT</command> is
-   fully SQL conforming.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-begin"></member>
-   <member><xref linkend="sql-commit"></member>
-   <member><xref linkend="sql-release-savepoint"></member>
-   <member><xref linkend="sql-rollback"></member>
-   <member><xref linkend="sql-rollback-to"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/security_label.sgmlin b/doc-xc/src/sgml/ref/security_label.sgmlin
deleted file mode 100644
index 8a01b940de..0000000000
--- a/doc-xc/src/sgml/ref/security_label.sgmlin
+++ /dev/null
@@ -1,206 +0,0 @@
-<!--
-doc/src/sgml/ref/security_label.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SECURITY-LABEL">
- <refmeta>
-  <refentrytitle>SECURITY LABEL</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SECURITY LABEL</refname>
-  <refpurpose>define or change a security label applied to an object</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-security-label">
-  <primary>SECURITY LABEL</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SECURITY LABEL [ FOR <replaceable class="PARAMETER">provider</replaceable> ] ON
-{
-  TABLE <replaceable class="PARAMETER">object_name</replaceable> |
-  COLUMN <replaceable class="PARAMETER">table_name</replaceable>.<replaceable class="PARAMETER">column_name</replaceable> |
-  AGGREGATE <replaceable class="PARAMETER">agg_name</replaceable> (<replaceable class="PARAMETER">agg_type</replaceable> [, ...] ) |
-  DOMAIN <replaceable class="PARAMETER">object_name</replaceable> |
-  FOREIGN TABLE <replaceable class="PARAMETER">object_name</replaceable>
-  FUNCTION <replaceable class="PARAMETER">function_name</replaceable> ( [ [ <replaceable class="parameter">argmode</replaceable> ] [ <replaceable class="parameter">argname</replaceable> ] <replaceable class="parameter">argtype</replaceable> [, ...] ] ) |
-  LARGE OBJECT <replaceable class="PARAMETER">large_object_oid</replaceable> |
-  [ PROCEDURAL ] LANGUAGE <replaceable class="PARAMETER">object_name</replaceable> |
-  SCHEMA <replaceable class="PARAMETER">object_name</replaceable> |
-  SEQUENCE <replaceable class="PARAMETER">object_name</replaceable> |
-  TYPE <replaceable class="PARAMETER">object_name</replaceable> |
-  VIEW <replaceable class="PARAMETER">object_name</replaceable>
-} IS '<replaceable class="PARAMETER">label</replaceable>'
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>SECURITY LABEL</command> applies a security label to a database
-   object.  An arbitrary number of security labels, one per label provider, can
-   be associated with a given database object.  Label providers are loadable
-   modules which register themselves by using the function
-   <function>register_label_provider</>.
-  </para>
-
-  <note>
-    <para>
-      <function>register_label_provider</> is not an SQL function; it can
-      only be called from C code loaded into the backend.
-    </para>
-  </note>
-
-  <para>
-   The label provider determines whether a given label is valid and whether
-   it is permissible to assign that label to a given object.  The meaning of a
-   given label is likewise at the discretion of the label provider.
-   <productname>PostgreSQL</> places no restrictions on whether or how a
-   label provider must interpret security labels; it merely provides a
-   mechanism for storing them.  In practice, this facility is intended to allow
-   integration with label-based mandatory access control (MAC) systems such as
-   <productname>SE-Linux</>.  Such systems make all access control decisions
-   based on object labels, rather than traditional discretionary access control
-   (DAC) concepts such as users and groups.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">object_name</replaceable></term>
-    <term><replaceable class="parameter">table_name.column_name</replaceable></term>
-    <term><replaceable class="parameter">agg_name</replaceable></term>
-    <term><replaceable class="parameter">function_name</replaceable></term>
-    <listitem>
-     <para>
-      The name of the object to be labeled.  Names of tables,
-      aggregates, domains, foreign tables, functions, sequences, types, and
-      views can be schema-qualified.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">provider</replaceable></term>
-    <listitem>
-     <para>
-      The name of the provider with which this label is to be associated.  The
-      named provider must be loaded and must consent to the proposed labeling
-      operation.  If exactly one provider is loaded, the provider name may be
-      omitted for brevity.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">arg_type</replaceable></term>
-    <listitem>
-     <para>
-      An input data type on which the aggregate function operates.
-      To reference a zero-argument aggregate function, write <literal>*</>
-      in place of the list of input data types.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argmode</replaceable></term>
-
-    <listitem>
-     <para>
-      The mode of a function argument: <literal>IN</>, <literal>OUT</>,
-      <literal>INOUT</>, or <literal>VARIADIC</>.
-      If omitted, the default is <literal>IN</>.
-      Note that <command>SECURITY LABEL ON FUNCTION</command> does not actually
-      pay any attention to <literal>OUT</> arguments, since only the input
-      arguments are needed to determine the function's identity.
-      So it is sufficient to list the <literal>IN</>, <literal>INOUT</>,
-      and <literal>VARIADIC</> arguments.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argname</replaceable></term>
-
-    <listitem>
-     <para>
-      The name of a function argument.
-      Note that <command>SECURITY LABEL ON FUNCTION</command> does not actually
-      pay any attention to argument names, since only the argument data
-      types are needed to determine the function's identity.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">argtype</replaceable></term>
-
-    <listitem>
-     <para>
-      The data type(s) of the function's arguments (optionally
-      schema-qualified), if any.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">large_object_oid</replaceable></term>
-    <listitem>
-     <para>
-      The OID of the large object.
-     </para>
-    </listitem>
-   </varlistentry>
-
-    <varlistentry>
-     <term><literal>PROCEDURAL</literal></term>
-
-     <listitem>
-      <para>
-       This is a noise word.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">label</replaceable></term>
-    <listitem>
-     <para>
-      The new security label, written as a string literal; or <literal>NULL</>
-      to drop the security label.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   The following example shows how the security label of a table might
-   be changed.
-
-<programlisting>
-SECURITY LABEL FOR selinux ON TABLE mytable IS 'system_u:object_r:sepgsql_table_t:s0';
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   There is no <command>SECURITY LABEL</command> command in the SQL standard.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/select.sgmlin b/doc-xc/src/sgml/ref/select.sgmlin
deleted file mode 100644
index a523a3ba02..0000000000
--- a/doc-xc/src/sgml/ref/select.sgmlin
+++ /dev/null
@@ -1,1707 +0,0 @@
-<!--
-doc/src/sgml/ref/select.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SELECT">
- <refmeta>
-  <refentrytitle>SELECT</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SELECT</refname>
-  <refname>TABLE</refname>
-  <refname>WITH</refname>
-  <refpurpose>retrieve rows from a table or view</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-select">
-  <primary>SELECT</primary>
- </indexterm>
-
- <indexterm zone="sql-select">
-  <primary>TABLE command</primary>
- </indexterm>
-
- <indexterm zone="sql-select">
-  <primary>WITH</primary>
-  <secondary>in SELECT</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-[ WITH [ RECURSIVE ] <replaceable class="parameter">with_query</replaceable> [, ...] ]
-SELECT [ ALL | DISTINCT [ ON ( <replaceable class="parameter">expression</replaceable> [, ...] ) ] ]
-    * | <replaceable class="parameter">expression</replaceable> [ [ AS ] <replaceable class="parameter">output_name</replaceable> ] [, ...]
-    [ FROM <replaceable class="parameter">from_item</replaceable> [, ...] ]
-    [ WHERE <replaceable class="parameter">condition</replaceable> ]
-    [ GROUP BY <replaceable class="parameter">expression</replaceable> [, ...] ]
-    [ HAVING <replaceable class="parameter">condition</replaceable> [, ...] ]
-    [ WINDOW <replaceable class="parameter">window_name</replaceable> AS ( <replaceable class="parameter">window_definition</replaceable> ) [, ...] ]
-    [ { UNION | INTERSECT | EXCEPT } [ ALL | DISTINCT ] <replaceable class="parameter">select</replaceable> ]
-    [ ORDER BY <replaceable class="parameter">expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [ NULLS { FIRST | LAST } ] [, ...] ]
-    [ LIMIT { <replaceable class="parameter">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="parameter">start</replaceable> [ ROW | ROWS ] ]
-    [ FETCH { FIRST | NEXT } [ <replaceable class="parameter">count</replaceable> ] { ROW | ROWS } ONLY ]
-    [ FOR { UPDATE | SHARE } [ OF <replaceable class="parameter">table_name</replaceable> [, ...] ] [ NOWAIT ] [...] ]
-
-<phrase>where <replaceable class="parameter">from_item</replaceable> can be one of:</phrase>
-
-    [ ONLY ] <replaceable class="parameter">table_name</replaceable> [ * ] [ [ AS ] <replaceable class="parameter">alias</replaceable> [ ( <replaceable class="parameter">column_alias</replaceable> [, ...] ) ] ]
-    ( <replaceable class="parameter">select</replaceable> ) [ AS ] <replaceable class="parameter">alias</replaceable> [ ( <replaceable class="parameter">column_alias</replaceable> [, ...] ) ]
-    <replaceable class="parameter">function_name</replaceable> ( [ <replaceable class="parameter">argument</replaceable> [, ...] ] ) [ AS ] <replaceable class="parameter">alias</replaceable> [ ( <replaceable class="parameter">column_alias</replaceable> [, ...] | <replaceable class="parameter">column_definition</replaceable> [, ...] ) ]
-    <replaceable class="parameter">function_name</replaceable> ( [ <replaceable class="parameter">argument</replaceable> [, ...] ] ) AS ( <replaceable class="parameter">column_definition</replaceable> [, ...] )
-    <replaceable class="parameter">from_item</replaceable> [ NATURAL ] <replaceable class="parameter">join_type</replaceable> <replaceable class="parameter">from_item</replaceable> [ ON <replaceable class="parameter">join_condition</replaceable> | USING ( <replaceable class="parameter">join_column</replaceable> [, ...] ) ]
-
-<phrase>and <replaceable class="parameter">with_query</replaceable> is:</phrase>
-
-    <replaceable class="parameter">with_query_name</replaceable> [ ( <replaceable class="parameter">column_name</replaceable> [, ...] ) ] AS ( <replaceable class="parameter">select</replaceable> )
-
-TABLE { [ ONLY ] <replaceable class="parameter">table_name</replaceable> [ * ] | <replaceable class="parameter">with_query_name</replaceable> }
-</synopsis>
-
-</refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>SELECT</command> retrieves rows from zero or more tables.
-   The general processing of <command>SELECT</command> is as follows:
-
-   <orderedlist>
-    <listitem>
-     <para>
-      All queries in the <literal>WITH</literal> list are computed.
-      These effectively serve as temporary tables that can be referenced
-      in the <literal>FROM</literal> list.  A <literal>WITH</literal> query
-      that is referenced more than once in <literal>FROM</literal> is
-      computed only once.
-      (See <xref linkend="sql-with" endterm="sql-with-title"> below.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      All elements in the <literal>FROM</literal> list are computed.
-      (Each element in the <literal>FROM</literal> list is a real or
-      virtual table.)  If more than one element is specified in the
-      <literal>FROM</literal> list, they are cross-joined together.
-      (See <xref linkend="sql-from" endterm="sql-from-title"> below.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      If the <literal>WHERE</literal> clause is specified, all rows
-      that do not satisfy the condition are eliminated from the
-      output.  (See <xref linkend="sql-where"
-      endterm="sql-where-title"> below.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      If the <literal>GROUP BY</literal> clause is specified, the
-      output is combined into groups of rows that match on one or more
-      values.  If the <literal>HAVING</literal> clause is present, it
-      eliminates groups that do not satisfy the given condition.  (See
-      <xref linkend="sql-groupby" endterm="sql-groupby-title"> and
-      <xref linkend="sql-having" endterm="sql-having-title"> below.)
-     </para>
-
-    </listitem>
-
-    <listitem>
-     <para>
-      The actual output rows are computed using the
-      <command>SELECT</command> output expressions for each selected
-      row or row group.  (See
-      <xref linkend="sql-select-list" endterm="sql-select-list-title">
-      below.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <literal>SELECT DISTINCT</literal> eliminates duplicate rows from the
-      result.  <literal>SELECT DISTINCT ON</literal> eliminates rows that
-      match on all the specified expressions.  <literal>SELECT ALL</literal>
-      (the default) will return all candidate rows, including
-      duplicates.  (See <xref linkend="sql-distinct"
-      endterm="sql-distinct-title"> below.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Using the operators <literal>UNION</literal>,
-      <literal>INTERSECT</literal>, and <literal>EXCEPT</literal>, the
-      output of more than one <command>SELECT</command> statement can
-      be combined to form a single result set.  The
-      <literal>UNION</literal> operator returns all rows that are in
-      one or both of the result sets.  The
-      <literal>INTERSECT</literal> operator returns all rows that are
-      strictly in both result sets.  The <literal>EXCEPT</literal>
-      operator returns the rows that are in the first result set but
-      not in the second.  In all three cases, duplicate rows are
-      eliminated unless <literal>ALL</literal> is specified.  The noise
-      word <literal>DISTINCT</> can be added to explicitly specify
-      eliminating duplicate rows.  Notice that <literal>DISTINCT</> is
-      the default behavior here, even though <literal>ALL</literal> is
-      the default for <command>SELECT</> itself.  (See
-      <xref linkend="sql-union" endterm="sql-union-title">, <xref
-      linkend="sql-intersect" endterm="sql-intersect-title">, and
-      <xref linkend="sql-except" endterm="sql-except-title"> below.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      If the <literal>ORDER BY</literal> clause is specified, the
-      returned rows are sorted in the specified order.  If
-      <literal>ORDER BY</literal> is not given, the rows are returned
-      in whatever order the system finds fastest to produce.  (See
-      <xref linkend="sql-orderby" endterm="sql-orderby-title"> below.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      If the <literal>LIMIT</literal> (or <literal>FETCH FIRST</literal>) or <literal>OFFSET</literal>
-      clause is specified, the <command>SELECT</command> statement
-      only returns a subset of the result rows. (See <xref
-      linkend="sql-limit" endterm="sql-limit-title"> below.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      If <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal>
-      is specified, the
-      <command>SELECT</command> statement locks the selected rows
-      against concurrent updates.  (See <xref linkend="sql-for-update-share"
-      endterm="sql-for-update-share-title"> below.)
-     </para>
-    </listitem>
-   </orderedlist>
-  </para>
-
-  <para>
-   You must have <literal>SELECT</literal> privilege on each column used
-   in a <command>SELECT</> command.  The use of <literal>FOR UPDATE</literal>
-   or <literal>FOR SHARE</literal> requires
-   <literal>UPDATE</literal> privilege as well (for at least one column
-   of each table so selected).
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <refsect2 id="SQL-WITH">
-   <title id="sql-with-title"><literal>WITH</literal> Clause</title>
-
-   <para>
-    The <literal>WITH</literal> clause allows you to specify one or more
-    subqueries that can be referenced by name in the primary query.
-    The subqueries effectively act as temporary tables or views
-    for the duration of the primary query.
-    Each subquery can be a <command>SELECT</command>,
-    <command>INSERT</command>, <command>UPDATE</command> or
-    <command>DELETE</command> statement.
-    When writing a data-modifying statement (<command>INSERT</command>,
-    <command>UPDATE</command> or <command>DELETE</command>) in
-    <literal>WITH</>, it is usual to include a <literal>RETURNING</> clause.
-    It is the output of <literal>RETURNING</>, <emphasis>not</> the underlying
-    table that the statement modifies, that forms the temporary table that is
-    read by the primary query.  If <literal>RETURNING</> is omitted, the
-    statement is still executed, but it produces no output so it cannot be
-    referenced as a table by the primary query.
-   </para>
-
-   <para>
-    A name (without schema qualification) must be specified for each
-    <literal>WITH</literal> query.  Optionally, a list of column names
-    can be specified; if this is omitted,
-    the column names are inferred from the subquery.
-   </para>
-
-   <para>
-    If <literal>RECURSIVE</literal> is specified, it allows a
-    <command>SELECT</command> subquery to reference itself by name.  Such a
-    subquery must have the form
-<synopsis>
-<replaceable class="parameter">non_recursive_term</replaceable> UNION [ ALL | DISTINCT ] <replaceable class="parameter">recursive_term</replaceable>
-</synopsis>
-    where the recursive self-reference must appear on the right-hand
-    side of the <literal>UNION</>.  Only one recursive self-reference
-    is permitted per query.  Recursive data-modifying statements are not
-    supported, but you can use the results of a recursive
-    <command>SELECT</command> query in
-    a data-modifying statement.  See <xref linkend="queries-with"> for
-    an example.
-   </para>
-
-   <para>
-    Another effect of <literal>RECURSIVE</literal> is that
-    <literal>WITH</literal> queries need not be ordered: a query
-    can reference another one that is later in the list.  (However,
-    circular references, or mutual recursion, are not implemented.)
-    Without <literal>RECURSIVE</literal>, <literal>WITH</literal> queries
-    can only reference sibling <literal>WITH</literal> queries
-    that are earlier in the <literal>WITH</literal> list.
-   </para>
-
-   <para>
-    A key property of <literal>WITH</literal> queries is that they
-    are evaluated only once per execution of the primary query,
-    even if the primary query refers to them more than once.
-    In particular, data-modifying statements are guaranteed to be
-    executed once and only once, regardless of whether the primary query
-    reads all or any of their output.
-   </para>
-
-   <para>
-    The primary query and the <literal>WITH</literal> queries are all
-    (notionally) executed at the same time.  This implies that the effects of
-    a data-modifying statement in <literal>WITH</literal> cannot be seen from
-    other parts of the query, other than by reading its <literal>RETURNING</>
-    output.  If two such data-modifying statements attempt to modify the same
-    row, the results are unspecified.
-   </para>
-
-   <para>
-    See <xref linkend="queries-with"> for additional information.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-FROM">
-   <title id="sql-from-title"><literal>FROM</literal> Clause</title>
-   <para>
-    The <literal>FROM</literal> clause specifies one or more source
-    tables for the <command>SELECT</command>.  If multiple sources are
-    specified, the result is the Cartesian product (cross join) of all
-    the sources.  But usually qualification conditions
-    are added to restrict the returned rows to a small subset of the
-    Cartesian product.
-   </para>
-
-   <para>
-    The <literal>FROM</literal> clause can contain the following
-    elements:
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">table_name</replaceable></term>
-      <listitem>
-       <para>
-        The name (optionally schema-qualified) of an existing table or
-        view.  If <literal>ONLY</> is specified, only that table is
-        scanned.  If <literal>ONLY</> is not specified, the table and
-        any descendant tables are scanned.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">alias</replaceable></term>
-      <listitem>
-       <para>
-        A substitute name for the <literal>FROM</> item containing the
-        alias.  An alias is used for brevity or to eliminate ambiguity
-        for self-joins (where the same table is scanned multiple
-        times).  When an alias is provided, it completely hides the
-        actual name of the table or function; for example given
-        <literal>FROM foo AS f</>, the remainder of the
-        <command>SELECT</command> must refer to this <literal>FROM</>
-        item as <literal>f</> not <literal>foo</>.  If an alias is
-        written, a column alias list can also be written to provide
-        substitute names for one or more columns of the table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">select</replaceable></term>
-      <listitem>
-       <para>
-        A sub-<command>SELECT</command> can appear in the
-        <literal>FROM</literal> clause.  This acts as though its
-        output were created as a temporary table for the duration of
-        this single <command>SELECT</command> command.  Note that the
-        sub-<command>SELECT</command> must be surrounded by
-        parentheses, and an alias <emphasis>must</emphasis> be
-        provided for it.  A
-        <xref linkend="sql-values"> command
-        can also be used here.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">with_query_name</replaceable></term>
-      <listitem>
-       <para>
-        A <literal>WITH</> query is referenced by writing its name,
-        just as though the query's name were a table name.  (In fact,
-        the <literal>WITH</> query hides any real table of the same name
-        for the purposes of the primary query.  If necessary, you can
-        refer to a real table of the same name by schema-qualifying
-        the table's name.)
-        An alias can be provided in the same way as for a table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">function_name</replaceable></term>
-      <listitem>
-       <para>
-        Function calls can appear in the <literal>FROM</literal>
-        clause.  (This is especially useful for functions that return
-        result sets, but any function can be used.)  This acts as
-        though its output were created as a temporary table for the
-        duration of this single <command>SELECT</command> command. An
-        alias can also be used. If an alias is written, a column alias
-        list can also be written to provide substitute names for one
-        or more attributes of the function's composite return type. If
-        the function has been defined as returning the <type>record</>
-        data type, then an alias or the key word <literal>AS</> must
-        be present, followed by a column definition list in the form
-        <literal>( <replaceable
-        class="parameter">column_name</replaceable> <replaceable
-        class="parameter">data_type</replaceable> <optional>, ... </>
-        )</literal>.  The column definition list must match the actual
-        number and types of columns returned by the function.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">join_type</replaceable></term>
-      <listitem>
-       <para>
-        One of
-        <itemizedlist>
-         <listitem>
-          <para><literal>[ INNER ] JOIN</literal></para>
-         </listitem>
-         <listitem>
-          <para><literal>LEFT [ OUTER ] JOIN</literal></para>
-         </listitem>
-         <listitem>
-          <para><literal>RIGHT [ OUTER ] JOIN</literal></para>
-         </listitem>
-         <listitem>
-          <para><literal>FULL [ OUTER ] JOIN</literal></para>
-         </listitem>
-         <listitem>
-          <para><literal>CROSS JOIN</literal></para>
-         </listitem>
-        </itemizedlist>
-
-        For the <literal>INNER</> and <literal>OUTER</> join types, a
-        join condition must be specified, namely exactly one of
-        <literal>NATURAL</>, <literal>ON <replaceable
-        class="parameter">join_condition</replaceable></literal>, or
-        <literal>USING (<replaceable
-        class="parameter">join_column</replaceable> [, ...])</literal>.
-        See below for the meaning.  For <literal>CROSS JOIN</literal>,
-        none of these clauses can appear.
-       </para>
-
-       <para>
-        A <literal>JOIN</literal> clause combines two
-        <literal>FROM</> items.  Use parentheses if necessary to
-        determine the order of nesting.  In the absence of parentheses,
-        <literal>JOIN</literal>s nest left-to-right.  In any case
-        <literal>JOIN</literal> binds more tightly than the commas
-        separating <literal>FROM</> items.
-       </para>
-
-       <para>
-        <literal>CROSS JOIN</> and <literal>INNER JOIN</literal>
-        produce a simple Cartesian product, the same result as you get from
-        listing the two items at the top level of <literal>FROM</>,
-        but restricted by the join condition (if any).
-        <literal>CROSS JOIN</> is equivalent to <literal>INNER JOIN ON
-        (TRUE)</>, that is, no rows are removed by qualification.
-        These join types are just a notational convenience, since they
-        do nothing you couldn't do with plain <literal>FROM</> and
-        <literal>WHERE</>.
-       </para>
-
-       <para>
-        <literal>LEFT OUTER JOIN</> returns all rows in the qualified
-        Cartesian product (i.e., all combined rows that pass its join
-        condition), plus one copy of each row in the left-hand table
-        for which there was no right-hand row that passed the join
-        condition.  This left-hand row is extended to the full width
-        of the joined table by inserting null values for the
-        right-hand columns.  Note that only the <literal>JOIN</>
-        clause's own condition is considered while deciding which rows
-        have matches.  Outer conditions are applied afterwards.
-       </para>
-
-       <para>
-        Conversely, <literal>RIGHT OUTER JOIN</> returns all the
-        joined rows, plus one row for each unmatched right-hand row
-        (extended with nulls on the left).  This is just a notational
-        convenience, since you could convert it to a <literal>LEFT
-        OUTER JOIN</> by switching the left and right inputs.
-       </para>
-
-       <para>
-        <literal>FULL OUTER JOIN</> returns all the joined rows, plus
-        one row for each unmatched left-hand row (extended with nulls
-        on the right), plus one row for each unmatched right-hand row
-        (extended with nulls on the left).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ON <replaceable class="parameter">join_condition</replaceable></literal></term>
-      <listitem>
-       <para>
-        <replaceable class="parameter">join_condition</replaceable> is
-        an expression resulting in a value of type
-        <type>boolean</type> (similar to a <literal>WHERE</literal>
-        clause) that specifies which rows in a join are considered to
-        match.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>USING ( <replaceable class="parameter">join_column</replaceable> [, ...] )</literal></term>
-      <listitem>
-       <para>
-        A clause of the form <literal>USING ( a, b, ... )</literal> is
-        shorthand for <literal>ON left_table.a = right_table.a AND
-        left_table.b = right_table.b ...</literal>.  Also,
-        <literal>USING</> implies that only one of each pair of
-        equivalent columns will be included in the join output, not
-        both.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>NATURAL</literal></term>
-      <listitem>
-       <para>
-        <literal>NATURAL</literal> is shorthand for a
-        <literal>USING</> list that mentions all columns in the two
-        tables that have the same names.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-WHERE">
-   <title id="sql-where-title"><literal>WHERE</literal> Clause</title>
-
-   <para>
-    The optional <literal>WHERE</literal> clause has the general form
-<synopsis>
-WHERE <replaceable class="parameter">condition</replaceable>
-</synopsis>
-    where <replaceable class="parameter">condition</replaceable> is
-    any expression that evaluates to a result of type
-    <type>boolean</type>.  Any row that does not satisfy this
-    condition will be eliminated from the output.  A row satisfies the
-    condition if it returns true when the actual row values are
-    substituted for any variable references.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-GROUPBY">
-   <title id="sql-groupby-title"><literal>GROUP BY</literal> Clause</title>
-
-   <para>
-    The optional <literal>GROUP BY</literal> clause has the general form
-<synopsis>
-GROUP BY <replaceable class="parameter">expression</replaceable> [, ...]
-</synopsis>
-   </para>
-
-   <para>
-    <literal>GROUP BY</literal> will condense into a single row all
-    selected rows that share the same values for the grouped
-    expressions.  <replaceable
-    class="parameter">expression</replaceable> can be an input column
-    name, or the name or ordinal number of an output column
-    (<command>SELECT</command> list item), or an arbitrary
-    expression formed from input-column values.  In case of ambiguity,
-    a <literal>GROUP BY</literal> name will be interpreted as an
-    input-column name rather than an output column name.
-   </para>
-
-   <para>
-    Aggregate functions, if any are used, are computed across all rows
-    making up each group, producing a separate value for each group
-    (whereas without <literal>GROUP BY</literal>, an aggregate
-    produces a single value computed across all the selected rows).
-    When <literal>GROUP BY</literal> is present, it is not valid for
-    the <command>SELECT</command> list expressions to refer to
-    ungrouped columns except within aggregate functions or if the
-    ungrouped column is functionally dependent on the grouped columns,
-    since there would otherwise be more than one possible value to
-    return for an ungrouped column.  A functional dependency exists if
-    the grouped columns (or a subset thereof) are the primary key of
-    the table containing the ungrouped column.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-HAVING">
-   <title id="sql-having-title"><literal>HAVING</literal> Clause</title>
-
-   <para>
-    The optional <literal>HAVING</literal> clause has the general form
-<synopsis>
-HAVING <replaceable class="parameter">condition</replaceable>
-</synopsis>
-    where <replaceable class="parameter">condition</replaceable> is
-    the same as specified for the <literal>WHERE</literal> clause.
-   </para>
-
-   <para>
-    <literal>HAVING</literal> eliminates group rows that do not
-    satisfy the condition.  <literal>HAVING</literal> is different
-    from <literal>WHERE</literal>: <literal>WHERE</literal> filters
-    individual rows before the application of <literal>GROUP
-    BY</literal>, while <literal>HAVING</literal> filters group rows
-    created by <literal>GROUP BY</literal>.  Each column referenced in
-    <replaceable class="parameter">condition</replaceable> must
-    unambiguously reference a grouping column, unless the reference
-    appears within an aggregate function.
-   </para>
-
-   <para>
-    The presence of <literal>HAVING</literal> turns a query into a grouped
-    query even if there is no <literal>GROUP BY</> clause.  This is the
-    same as what happens when the query contains aggregate functions but
-    no <literal>GROUP BY</> clause.  All the selected rows are considered to
-    form a single group, and the <command>SELECT</command> list and
-    <literal>HAVING</literal> clause can only reference table columns from
-    within aggregate functions.  Such a query will emit a single row if the
-    <literal>HAVING</literal> condition is true, zero rows if it is not true.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-WINDOW">
-   <title id="sql-window-title"><literal>WINDOW</literal> Clause</title>
-
-   <para>
-    The optional <literal>WINDOW</literal> clause has the general form
-<synopsis>
-WINDOW <replaceable class="parameter">window_name</replaceable> AS ( <replaceable class="parameter">window_definition</replaceable> ) [, ...]
-</synopsis>
-    where <replaceable class="parameter">window_name</replaceable> is
-    a name that can be referenced from subsequent window definitions or
-    <literal>OVER</> clauses, and
-    <replaceable class="parameter">window_definition</replaceable> is
-<synopsis>
-[ <replaceable class="parameter">existing_window_name</replaceable> ]
-[ PARTITION BY <replaceable class="parameter">expression</replaceable> [, ...] ]
-[ ORDER BY <replaceable class="parameter">expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [ NULLS { FIRST | LAST } ] [, ...] ]
-[ <replaceable class="parameter">frame_clause</replaceable> ]
-</synopsis>
-   </para>
-
-   <para>
-    If an <replaceable class="parameter">existing_window_name</replaceable>
-    is specified it must refer to an earlier entry in the <literal>WINDOW</>
-    list; the new window copies its partitioning clause from that entry,
-    as well as its ordering clause if any.  In this case the new window cannot
-    specify its own <literal>PARTITION BY</> clause, and it can specify
-    <literal>ORDER BY</> only if the copied window does not have one.
-    The new window always uses its own frame clause; the copied window
-    must not specify a frame clause.
-   </para>
-
-   <para>
-    The elements of the <literal>PARTITION BY</> list are interpreted in
-    much the same fashion as elements of a
-    <xref linkend="sql-groupby" endterm="sql-groupby-title">, except that
-    they are always simple expressions and never the name or number of an
-    output column.
-    Another difference is that these expressions can contain aggregate
-    function calls, which are not allowed in a regular <literal>GROUP BY</>
-    clause.  They are allowed here because windowing occurs after grouping
-    and aggregation.
-   </para>
-
-   <para>
-    Similarly, the elements of the <literal>ORDER BY</> list are interpreted
-    in much the same fashion as elements of an
-    <xref linkend="sql-orderby" endterm="sql-orderby-title">, except that
-    the expressions are always taken as simple expressions and never the name
-    or number of an output column.
-   </para>
-
-   <para>
-    The optional <replaceable class="parameter">frame_clause</> defines
-    the <firstterm>window frame</> for window functions that depend on the
-    frame (not all do).  The window frame is a set of related rows for
-    each row of the query (called the <firstterm>current row</>).
-    The <replaceable class="parameter">frame_clause</> can be one of
-
-<synopsis>
-[ RANGE | ROWS ] <replaceable>frame_start</>
-[ RANGE | ROWS ] BETWEEN <replaceable>frame_start</> AND <replaceable>frame_end</>
-</synopsis>
-
-    where <replaceable>frame_start</> and <replaceable>frame_end</> can be
-    one of
-
-<synopsis>
-UNBOUNDED PRECEDING
-<replaceable>value</replaceable> PRECEDING
-CURRENT ROW
-<replaceable>value</replaceable> FOLLOWING
-UNBOUNDED FOLLOWING
-</synopsis>
-
-    If <replaceable>frame_end</> is omitted it defaults to <literal>CURRENT
-    ROW</>.  Restrictions are that
-    <replaceable>frame_start</> cannot be <literal>UNBOUNDED FOLLOWING</>,
-    <replaceable>frame_end</> cannot be <literal>UNBOUNDED PRECEDING</>,
-    and the <replaceable>frame_end</> choice cannot appear earlier in the
-    above list than the <replaceable>frame_start</> choice &mdash; for example
-    <literal>RANGE BETWEEN CURRENT ROW AND <replaceable>value</>
-    PRECEDING</literal> is not allowed.
-   </para>
-
-   <para>
-    The default framing option is <literal>RANGE UNBOUNDED PRECEDING</>,
-    which is the same as <literal>RANGE BETWEEN UNBOUNDED PRECEDING AND
-    CURRENT ROW</>; it sets the frame to be all rows from the partition start
-    up through the current row's last peer in the <literal>ORDER BY</>
-    ordering (which means all rows if there is no <literal>ORDER BY</>).
-    In general, <literal>UNBOUNDED PRECEDING</> means that the frame
-    starts with the first row of the partition, and similarly
-    <literal>UNBOUNDED FOLLOWING</> means that the frame ends with the last
-    row of the partition (regardless of <literal>RANGE</> or <literal>ROWS</>
-    mode).  In <literal>ROWS</> mode, <literal>CURRENT ROW</>
-    means that the frame starts or ends with the current row; but in
-    <literal>RANGE</> mode it means that the frame starts or ends with
-    the current row's first or last peer in the <literal>ORDER BY</> ordering.
-    The <replaceable>value</> <literal>PRECEDING</> and
-    <replaceable>value</> <literal>FOLLOWING</> cases are currently only
-    allowed in <literal>ROWS</> mode.  They indicate that the frame starts
-    or ends with the row that many rows before or after the current row.
-    <replaceable>value</replaceable> must be an integer expression not
-    containing any variables, aggregate functions, or window functions.
-    The value must not be null or negative; but it can be zero, which
-    selects the current row itself.
-   </para>
-
-   <para>
-    Beware that the <literal>ROWS</> options can produce unpredictable
-    results if the <literal>ORDER BY</> ordering does not order the rows
-    uniquely.  The <literal>RANGE</> options are designed to ensure that
-    rows that are peers in the <literal>ORDER BY</> ordering are treated
-    alike; any two peer rows will be both in or both not in the frame.
-   </para>
-
-   <para>
-    The purpose of a <literal>WINDOW</literal> clause is to specify the
-    behavior of <firstterm>window functions</> appearing in the query's
-    <xref linkend="sql-select-list" endterm="sql-select-list-title"> or
-    <xref linkend="sql-orderby" endterm="sql-orderby-title">.  These functions
-    can reference the <literal>WINDOW</literal> clause entries by name
-    in their <literal>OVER</> clauses.  A <literal>WINDOW</literal> clause
-    entry does not have to be referenced anywhere, however; if it is not
-    used in the query it is simply ignored.  It is possible to use window
-    functions without any <literal>WINDOW</literal> clause at all, since
-    a window function call can specify its window definition directly in
-    its <literal>OVER</> clause.  However, the <literal>WINDOW</literal>
-    clause saves typing when the same window definition is needed for more
-    than one window function.
-   </para>
-
-   <para>
-    Window functions are described in detail in
-    <xref linkend="tutorial-window">,
-    <xref linkend="syntax-window-functions">, and
-    <xref linkend="queries-window">.
-   </para>
-  </refsect2>
-
-  <refsect2 id="sql-select-list">
-   <title id="sql-select-list-title"><command>SELECT</command> List</title>
-
-   <para>
-    The <command>SELECT</command> list (between the key words
-    <literal>SELECT</> and <literal>FROM</>) specifies expressions
-    that form the output rows of the <command>SELECT</command>
-    statement.  The expressions can (and usually do) refer to columns
-    computed in the <literal>FROM</> clause.
-   </para>
-
-   <para>
-    Just as in a table, every output column of a <command>SELECT</command>
-    has a name.  In a simple <command>SELECT</command> this name is just
-    used to label the column for display, but when the <command>SELECT</>
-    is a sub-query of a larger query, the name is seen by the larger query
-    as the column name of the virtual table produced by the sub-query.
-    To specify the name to use for an output column, write
-    <literal>AS</> <replaceable class="parameter">output_name</replaceable>
-    after the column's expression.  (You can omit <literal>AS</literal>,
-    but only if the desired output name does not match any
-    <productname>PostgreSQL</productname> keyword (see <xref
-    linkend="sql-keywords-appendix">).  For protection against possible
-    future keyword additions, it is recommended that you always either
-    write <literal>AS</literal> or double-quote the output name.)
-    If you do not specify a column name, a name is chosen automatically
-    by <productname>PostgreSQL</productname>.  If the column's expression
-    is a simple column reference then the chosen name is the same as that
-    column's name; in more complex cases a generated name looking like
-    <literal>?column<replaceable>N</>?</literal> is usually chosen.
-   </para>
-
-   <para>
-    An output column's name can be used to refer to the column's value in
-    <literal>ORDER BY</> and <literal>GROUP BY</> clauses, but not in the
-    <literal>WHERE</> or <literal>HAVING</> clauses; there you must write
-    out the expression instead.
-   </para>
-
-   <para>
-    Instead of an expression, <literal>*</literal> can be written in
-    the output list as a shorthand for all the columns of the selected
-    rows.  Also, you can write <literal><replaceable
-    class="parameter">table_name</replaceable>.*</literal> as a
-    shorthand for the columns coming from just that table.  In these
-    cases it is not possible to specify new names with <literal>AS</>;
-    the output column names will be the same as the table columns' names.
-   </para>
-  </refsect2>
-
-  <refsect2 id="sql-distinct">
-   <title id="sql-distinct-title"><literal>DISTINCT</literal> Clause</title>
-
-   <para>
-    If <literal>SELECT DISTINCT</> is specified, all duplicate rows are
-    removed from the result set (one row is kept from each group of
-    duplicates).  <literal>SELECT ALL</> specifies the opposite: all rows are
-    kept; that is the default.
-   </para>
-
-   <para>
-    <literal>SELECT DISTINCT ON ( <replaceable
-    class="parameter">expression</replaceable> [, ...] )</literal>
-    keeps only the first row of each set of rows where the given
-    expressions evaluate to equal.  The <literal>DISTINCT ON</literal>
-    expressions are interpreted using the same rules as for
-    <literal>ORDER BY</> (see above).  Note that the <quote>first
-    row</quote> of each set is unpredictable unless <literal>ORDER
-    BY</> is used to ensure that the desired row appears first.  For
-    example:
-<programlisting>
-SELECT DISTINCT ON (location) location, time, report
-    FROM weather_reports
-    ORDER BY location, time DESC;
-</programlisting>
-    retrieves the most recent weather report for each location.  But
-    if we had not used <literal>ORDER BY</> to force descending order
-    of time values for each location, we'd have gotten a report from
-    an unpredictable time for each location.
-   </para>
-
-   <para>
-    The <literal>DISTINCT ON</> expression(s) must match the leftmost
-    <literal>ORDER BY</> expression(s).  The <literal>ORDER BY</> clause
-    will normally contain additional expression(s) that determine the
-    desired precedence of rows within each <literal>DISTINCT ON</> group.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-UNION">
-   <title id="sql-union-title"><literal>UNION</literal> Clause</title>
-
-   <para>
-    The <literal>UNION</literal> clause has this general form:
-<synopsis>
-<replaceable class="parameter">select_statement</replaceable> UNION [ ALL | DISTINCT ] <replaceable class="parameter">select_statement</replaceable>
-</synopsis>
-    <replaceable class="parameter">select_statement</replaceable> is
-    any <command>SELECT</command> statement without an <literal>ORDER
-    BY</>, <literal>LIMIT</>, <literal>FOR UPDATE</literal>, or
-    <literal>FOR SHARE</literal> clause.
-    (<literal>ORDER BY</> and <literal>LIMIT</> can be attached to a
-    subexpression if it is enclosed in parentheses.  Without
-    parentheses, these clauses will be taken to apply to the result of
-    the <literal>UNION</literal>, not to its right-hand input
-    expression.)
-   </para>
-
-   <para>
-    The <literal>UNION</literal> operator computes the set union of
-    the rows returned by the involved <command>SELECT</command>
-    statements.  A row is in the set union of two result sets if it
-    appears in at least one of the result sets.  The two
-    <command>SELECT</command> statements that represent the direct
-    operands of the <literal>UNION</literal> must produce the same
-    number of columns, and corresponding columns must be of compatible
-    data types.
-   </para>
-
-   <para>
-    The result of <literal>UNION</> does not contain any duplicate
-    rows unless the <literal>ALL</> option is specified.
-    <literal>ALL</> prevents elimination of duplicates.  (Therefore,
-    <literal>UNION ALL</> is usually significantly quicker than
-    <literal>UNION</>; use <literal>ALL</> when you can.)
-    <literal>DISTINCT</> can be written to explicitly specify the
-    default behavior of eliminating duplicate rows.
-   </para>
-
-   <para>
-    Multiple <literal>UNION</> operators in the same
-    <command>SELECT</command> statement are evaluated left to right,
-    unless otherwise indicated by parentheses.
-   </para>
-
-   <para>
-    Currently, <literal>FOR UPDATE</> and <literal>FOR SHARE</> cannot be
-    specified either for a <literal>UNION</> result or for any input of a
-    <literal>UNION</>.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-INTERSECT">
-   <title id="sql-intersect-title"><literal>INTERSECT</literal> Clause</title>
-
-   <para>
-    The <literal>INTERSECT</literal> clause has this general form:
-<synopsis>
-<replaceable class="parameter">select_statement</replaceable> INTERSECT [ ALL | DISTINCT ] <replaceable class="parameter">select_statement</replaceable>
-</synopsis>
-    <replaceable class="parameter">select_statement</replaceable> is
-    any <command>SELECT</command> statement without an <literal>ORDER
-    BY</>, <literal>LIMIT</>, <literal>FOR UPDATE</literal>, or
-    <literal>FOR SHARE</literal> clause.
-   </para>
-
-   <para>
-    The <literal>INTERSECT</literal> operator computes the set
-    intersection of the rows returned by the involved
-    <command>SELECT</command> statements.  A row is in the
-    intersection of two result sets if it appears in both result sets.
-   </para>
-
-   <para>
-    The result of <literal>INTERSECT</literal> does not contain any
-    duplicate rows unless the <literal>ALL</> option is specified.
-    With <literal>ALL</>, a row that has <replaceable>m</> duplicates in the
-    left table and <replaceable>n</> duplicates in the right table will appear
-    min(<replaceable>m</>,<replaceable>n</>) times in the result set.
-    <literal>DISTINCT</> can be written to explicitly specify the
-    default behavior of eliminating duplicate rows.
-   </para>
-
-   <para>
-    Multiple <literal>INTERSECT</literal> operators in the same
-    <command>SELECT</command> statement are evaluated left to right,
-    unless parentheses dictate otherwise.
-    <literal>INTERSECT</literal> binds more tightly than
-    <literal>UNION</literal>.  That is, <literal>A UNION B INTERSECT
-    C</literal> will be read as <literal>A UNION (B INTERSECT
-    C)</literal>.
-   </para>
-
-   <para>
-    Currently, <literal>FOR UPDATE</> and <literal>FOR SHARE</> cannot be
-    specified either for an <literal>INTERSECT</> result or for any input of
-    an <literal>INTERSECT</>.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-EXCEPT">
-   <title id="sql-except-title"><literal>EXCEPT</literal> Clause</title>
-
-   <para>
-    The <literal>EXCEPT</literal> clause has this general form:
-<synopsis>
-<replaceable class="parameter">select_statement</replaceable> EXCEPT [ ALL | DISTINCT ] <replaceable class="parameter">select_statement</replaceable>
-</synopsis>
-    <replaceable class="parameter">select_statement</replaceable> is
-    any <command>SELECT</command> statement without an <literal>ORDER
-    BY</>, <literal>LIMIT</>, <literal>FOR UPDATE</literal>, or
-    <literal>FOR SHARE</literal> clause.
-   </para>
-
-   <para>
-    The <literal>EXCEPT</literal> operator computes the set of rows
-    that are in the result of the left <command>SELECT</command>
-    statement but not in the result of the right one.
-   </para>
-
-   <para>
-    The result of <literal>EXCEPT</literal> does not contain any
-    duplicate rows unless the <literal>ALL</> option is specified.
-    With <literal>ALL</>, a row that has <replaceable>m</> duplicates in the
-    left table and <replaceable>n</> duplicates in the right table will appear
-    max(<replaceable>m</>-<replaceable>n</>,0) times in the result set.
-    <literal>DISTINCT</> can be written to explicitly specify the
-    default behavior of eliminating duplicate rows.
-   </para>
-
-   <para>
-    Multiple <literal>EXCEPT</literal> operators in the same
-    <command>SELECT</command> statement are evaluated left to right,
-    unless parentheses dictate otherwise.  <literal>EXCEPT</> binds at
-    the same level as <literal>UNION</>.
-   </para>
-
-   <para>
-    Currently, <literal>FOR UPDATE</> and <literal>FOR SHARE</> cannot be
-    specified either for an <literal>EXCEPT</> result or for any input of
-    an <literal>EXCEPT</>.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-ORDERBY">
-   <title id="sql-orderby-title"><literal>ORDER BY</literal> Clause</title>
-
-   <para>
-    The optional <literal>ORDER BY</literal> clause has this general form:
-<synopsis>
-ORDER BY <replaceable class="parameter">expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [ NULLS { FIRST | LAST } ] [, ...]
-</synopsis>
-    The <literal>ORDER BY</literal> clause causes the result rows to
-    be sorted according to the specified expression(s).  If two rows are
-    equal according to the leftmost expression, they are compared
-    according to the next expression and so on.  If they are equal
-    according to all specified expressions, they are returned in
-    an implementation-dependent order.
-   </para>
-
-   <para>
-    Each <replaceable class="parameter">expression</replaceable> can be the
-    name or ordinal number of an output column
-    (<command>SELECT</command> list item), or it can be an arbitrary
-    expression formed from input-column values.
-   </para>
-
-   <para>
-    The ordinal number refers to the ordinal (left-to-right) position
-    of the output column. This feature makes it possible to define an
-    ordering on the basis of a column that does not have a unique
-    name.  This is never absolutely necessary because it is always
-    possible to assign a name to an output column using the
-    <literal>AS</> clause.
-   </para>
-
-   <para>
-    It is also possible to use arbitrary expressions in the
-    <literal>ORDER BY</literal> clause, including columns that do not
-    appear in the <command>SELECT</command> output list.  Thus the
-    following statement is valid:
-<programlisting>
-SELECT name FROM distributors ORDER BY code;
-</programlisting>
-    A limitation of this feature is that an <literal>ORDER BY</>
-    clause applying to the result of a <literal>UNION</>,
-    <literal>INTERSECT</>, or <literal>EXCEPT</> clause can only
-    specify an output column name or number, not an expression.
-   </para>
-
-   <para>
-    If an <literal>ORDER BY</> expression is a simple name that
-    matches both an output column name and an input column name,
-    <literal>ORDER BY</> will interpret it as the output column name.
-    This is the opposite of the choice that <literal>GROUP BY</> will
-    make in the same situation.  This inconsistency is made to be
-    compatible with the SQL standard.
-   </para>
-
-   <para>
-    Optionally one can add the key word <literal>ASC</> (ascending) or
-    <literal>DESC</> (descending) after any expression in the
-    <literal>ORDER BY</> clause.  If not specified, <literal>ASC</> is
-    assumed by default.  Alternatively, a specific ordering operator
-    name can be specified in the <literal>USING</> clause.
-    An ordering operator must be a less-than or greater-than
-    member of some B-tree operator family.
-    <literal>ASC</> is usually equivalent to <literal>USING &lt;</> and
-    <literal>DESC</> is usually equivalent to <literal>USING &gt;</>.
-    (But the creator of a user-defined data type can define exactly what the
-    default sort ordering is, and it might correspond to operators with other
-    names.)
-   </para>
-
-   <para>
-    If <literal>NULLS LAST</> is specified, null values sort after all
-    non-null values; if <literal>NULLS FIRST</> is specified, null values
-    sort before all non-null values.  If neither is specified, the default
-    behavior is <literal>NULLS LAST</> when <literal>ASC</> is specified
-    or implied, and <literal>NULLS FIRST</> when <literal>DESC</> is specified
-    (thus, the default is to act as though nulls are larger than non-nulls).
-    When <literal>USING</> is specified, the default nulls ordering depends
-    on whether the operator is a less-than or greater-than operator.
-   </para>
-
-   <para>
-    Note that ordering options apply only to the expression they follow;
-    for example <literal>ORDER BY x, y DESC</> does not mean
-    the same thing as <literal>ORDER BY x DESC, y DESC</>.
-   </para>
-
-   <para>
-    Character-string data is sorted according to the locale-specific
-    collation order that was established when the database was created.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-LIMIT">
-   <title id="sql-limit-title"><literal>LIMIT</literal> Clause</title>
-
-   <para>
-    The <literal>LIMIT</literal> clause consists of two independent
-    sub-clauses:
-<synopsis>
-LIMIT { <replaceable class="parameter">count</replaceable> | ALL }
-OFFSET <replaceable class="parameter">start</replaceable>
-</synopsis>
-    <replaceable class="parameter">count</replaceable> specifies the
-    maximum number of rows to return, while <replaceable
-    class="parameter">start</replaceable> specifies the number of rows
-    to skip before starting to return rows.  When both are specified,
-    <replaceable class="parameter">start</replaceable> rows are skipped
-    before starting to count the <replaceable
-    class="parameter">count</replaceable> rows to be returned.
-   </para>
-
-   <para>
-    If the <replaceable class="parameter">count</replaceable> expression
-    evaluates to NULL, it is treated as <literal>LIMIT ALL</>, i.e., no
-    limit.  If <replaceable class="parameter">start</replaceable> evaluates
-    to NULL, it is treated the same as <literal>OFFSET 0</>.
-   </para>
-
-   <para>
-    SQL:2008 introduced a different syntax to achieve the same result,
-    which <productname>PostgreSQL</> also supports.  It is:
-<synopsis>
-OFFSET <replaceable class="parameter">start</replaceable> { ROW | ROWS }
-FETCH { FIRST | NEXT } [ <replaceable class="parameter">count</replaceable> ] { ROW | ROWS } ONLY
-</synopsis>
-    According to the standard, the <literal>OFFSET</literal> clause must come
-    before the <literal>FETCH</literal> clause if both are present; but
-    <productname>PostgreSQL</> is laxer and allows either order.
-    <literal>ROW</literal>
-    and <literal>ROWS</literal> as well as <literal>FIRST</literal>
-    and <literal>NEXT</literal> are noise words that don't influence
-    the effects of these clauses.  In this syntax, when using expressions
-    other than simple constants for <replaceable class="parameter">start</>
-    or <replaceable class="parameter">count</replaceable>, parentheses will be
-    necessary in most cases.  If <replaceable class="parameter">count</> is
-    omitted in <literal>FETCH</>, it defaults to 1.
-   </para>
-
-   <para>
-    When using <literal>LIMIT</>, it is a good idea to use an
-    <literal>ORDER BY</> clause that constrains the result rows into a
-    unique order.  Otherwise you will get an unpredictable subset of
-    the query's rows &mdash; you might be asking for the tenth through
-    twentieth rows, but tenth through twentieth in what ordering?  You
-    don't know what ordering unless you specify <literal>ORDER BY</>.
-   </para>
-
-   <para>
-    The query planner takes <literal>LIMIT</> into account when
-    generating a query plan, so you are very likely to get different
-    plans (yielding different row orders) depending on what you use
-    for <literal>LIMIT</> and <literal>OFFSET</>.  Thus, using
-    different <literal>LIMIT</>/<literal>OFFSET</> values to select
-    different subsets of a query result <emphasis>will give
-    inconsistent results</emphasis> unless you enforce a predictable
-    result ordering with <literal>ORDER BY</>.  This is not a bug; it
-    is an inherent consequence of the fact that SQL does not promise
-    to deliver the results of a query in any particular order unless
-    <literal>ORDER BY</> is used to constrain the order.
-   </para>
-
-   <para>
-    It is even possible for repeated executions of the same <literal>LIMIT</>
-    query to return different subsets of the rows of a table, if there
-    is not an <literal>ORDER BY</> to enforce selection of a deterministic
-    subset.  Again, this is not a bug; determinism of the results is
-    simply not guaranteed in such a case.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-FOR-UPDATE-SHARE">
-   <title id="sql-for-update-share-title"><literal>FOR UPDATE</literal>/<literal>FOR SHARE</literal> Clause</title>
-
-   <para>
-    The <literal>FOR UPDATE</literal> clause has this form:
-<synopsis>
-FOR UPDATE [ OF <replaceable class="parameter">table_name</replaceable> [, ...] ] [ NOWAIT ]
-</synopsis>
-   </para>
-
-   <para>
-    The closely related <literal>FOR SHARE</literal> clause has this form:
-<synopsis>
-FOR SHARE [ OF <replaceable class="parameter">table_name</replaceable> [, ...] ] [ NOWAIT ]
-</synopsis>
-   </para>
-
-   <para>
-    <literal>FOR UPDATE</literal> causes the rows retrieved by the
-    <command>SELECT</command> statement to be locked as though for
-    update.  This prevents them from being modified or deleted by
-    other transactions until the current transaction ends.  That is,
-    other transactions that attempt <command>UPDATE</command>,
-    <command>DELETE</command>, or <command>SELECT FOR UPDATE</command>
-    of these rows will be blocked until the current transaction ends.
-    Also, if an <command>UPDATE</command>, <command>DELETE</command>,
-    or <command>SELECT FOR UPDATE</command> from another transaction
-    has already locked a selected row or rows, <command>SELECT FOR
-    UPDATE</command> will wait for the other transaction to complete,
-    and will then lock and return the updated row (or no row, if the
-    row was deleted).  Within a <literal>REPEATABLE READ</> or <literal>SERIALIZABLE</> transaction,
-    however, an error will be thrown if a row to be locked has changed
-    since the transaction started.  For further discussion see <xref
-    linkend="mvcc">.
-   </para>
-
-   <para>
-    <literal>FOR SHARE</literal> behaves similarly, except that it
-    acquires a shared rather than exclusive lock on each retrieved
-    row.  A shared lock blocks other transactions from performing
-    <command>UPDATE</command>, <command>DELETE</command>, or <command>SELECT
-    FOR UPDATE</command> on these rows, but it does not prevent them
-    from performing <command>SELECT FOR SHARE</command>.
-   </para>
-
-   <para>
-    To prevent the operation from waiting for other transactions to commit,
-    use the <literal>NOWAIT</> option.  With <literal>NOWAIT</>, the statement
-    reports an error, rather than waiting, if a selected row
-    cannot be locked immediately.  Note that <literal>NOWAIT</> applies only
-    to the row-level lock(s) &mdash; the required <literal>ROW SHARE</literal>
-    table-level lock is still taken in the ordinary way (see
-    <xref linkend="mvcc">).  You can use
-    <xref linkend="sql-lock">
-    with the <literal>NOWAIT</> option first,
-    if you need to acquire the table-level lock without waiting.
-   </para>
-
-   <para>
-    If specific tables are named in <literal>FOR UPDATE</literal>
-    or <literal>FOR SHARE</literal>,
-    then only rows coming from those tables are locked; any other
-    tables used in the <command>SELECT</command> are simply read as
-    usual.  A <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal>
-    clause without a table list affects all tables used in the statement.
-    If <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal> is
-    applied to a view or sub-query, it affects all tables used in
-    the view or sub-query.
-    However, <literal>FOR UPDATE</literal>/<literal>FOR SHARE</literal>
-    do not apply to <literal>WITH</> queries referenced by the primary query.
-    If you want row locking to occur within a <literal>WITH</> query, specify
-    <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal> within the
-    <literal>WITH</> query.
-   </para>
-
-   <para>
-    Multiple <literal>FOR UPDATE</literal> and <literal>FOR SHARE</literal>
-    clauses can be written if it is necessary to specify different locking
-    behavior for different tables.  If the same table is mentioned (or
-    implicitly affected) by both <literal>FOR UPDATE</literal> and
-    <literal>FOR SHARE</literal> clauses, then it is processed as
-    <literal>FOR UPDATE</literal>.  Similarly, a table is processed
-    as <literal>NOWAIT</> if that is specified in any of the clauses
-    affecting it.
-   </para>
-
-   <para>
-    <literal>FOR UPDATE</literal> and <literal>FOR SHARE</literal> cannot be
-    used in contexts where returned rows cannot be clearly identified with
-    individual table rows; for example they cannot be used with aggregation.
-   </para>
-
-   <para>
-    When <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal>
-    appears at the top level of a <command>SELECT</> query, the rows that
-    are locked are exactly those that are returned by the query; in the
-    case of a join query, the rows locked are those that contribute to
-    returned join rows.  In addition, rows that satisfied the query
-    conditions as of the query snapshot will be locked, although they
-    will not be returned if they were updated after the snapshot
-    and no longer satisfy the query conditions.  If a
-    <literal>LIMIT</> is used, locking stops
-    once enough rows have been returned to satisfy the limit (but note that
-    rows skipped over by <literal>OFFSET</> will get locked).  Similarly,
-    if <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal>
-    is used in a cursor's query, only rows actually fetched or stepped past
-    by the cursor will be locked.
-   </para>
-
-   <para>
-    When <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal>
-    appears in a sub-<command>SELECT</>, the rows locked are those
-    returned to the outer query by the sub-query.  This might involve
-    fewer rows than inspection of the sub-query alone would suggest,
-    since conditions from the outer query might be used to optimize
-    execution of the sub-query.  For example,
-<programlisting>
-SELECT * FROM (SELECT * FROM mytable FOR UPDATE) ss WHERE col1 = 5;
-</programlisting>
-    will lock only rows having <literal>col1 = 5</>, even though that
-    condition is not textually within the sub-query.
-   </para>
-
-  <caution>
-   <para>
-    Avoid locking a row and then modifying it within a later savepoint or
-    <application>PL/pgSQL</application> exception block.  A subsequent
-    rollback would cause the lock to be lost.  For example:
-<programlisting>
-BEGIN;
-SELECT * FROM mytable WHERE key = 1 FOR UPDATE;
-SAVEPOINT s;
-UPDATE mytable SET ... WHERE key = 1;
-ROLLBACK TO s;
-</programlisting>
-    After the <command>ROLLBACK</>, the row is effectively unlocked, rather
-    than returned to its pre-savepoint state of being locked but not modified.
-    This hazard occurs if a row locked in the current transaction is updated
-    or deleted, or if a shared lock is upgraded to exclusive: in all these
-    cases, the former lock state is forgotten.  If the transaction is then
-    rolled back to a state between the original locking command and the
-    subsequent change, the row will appear not to be locked at all.  This is
-    an implementation deficiency which will be addressed in a future release
-    of <productname>PostgreSQL</productname>.
-   </para>
-  </caution>
-
-  <caution>
-   <para>
-    It is possible for a <command>SELECT</> command using <literal>ORDER
-    BY</literal> and <literal>FOR UPDATE/SHARE</literal> to return rows out of
-    order.  This is because <literal>ORDER BY</> is applied first.
-    The command sorts the result, but might then block trying to obtain a lock
-    on one or more of the rows.  Once the <literal>SELECT</> unblocks, some
-    of the ordering column values might have been modified, leading to those
-    rows appearing to be out of order (though they are in order in terms
-    of the original column values).  This can be worked around at need by
-    placing the <literal>FOR UPDATE/SHARE</literal> clause in a sub-query,
-    for example
-<programlisting>
-SELECT * FROM (SELECT * FROM mytable FOR UPDATE) ss ORDER BY column1;
-</programlisting>
-    Note that this will result in locking all rows of <structname>mytable</>,
-    whereas <literal>FOR UPDATE</> at the top level would lock only the
-    actually returned rows.  This can make for a significant performance
-    difference, particularly if the <literal>ORDER BY</> is combined with
-    <literal>LIMIT</> or other restrictions.  So this technique is recommended
-    only if concurrent updates of the ordering columns are expected and a
-    strictly sorted result is required.
-   </para>
-  </caution>
-  </refsect2>
-
-  <refsect2 id="SQL-TABLE">
-   <title><literal>TABLE</literal> Command</title>
-
-   <para>
-    The command
-<programlisting>
-TABLE <replaceable class="parameter">name</replaceable>
-</programlisting>
-    is completely equivalent to
-<programlisting>
-SELECT * FROM <replaceable class="parameter">name</replaceable>
-</programlisting>
-    It can be used as a top-level command or as a space-saving syntax
-    variant in parts of complex queries.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To join the table <literal>films</literal> with the table
-   <literal>distributors</literal>:
-
-<programlisting>
-SELECT f.title, f.did, d.name, f.date_prod, f.kind
-    FROM distributors d, films f
-    WHERE f.did = d.did
-
-       title       | did |     name     | date_prod  |   kind
--------------------+-----+--------------+------------+----------
- The Third Man     | 101 | British Lion | 1949-12-23 | Drama
- The African Queen | 101 | British Lion | 1951-08-11 | Romantic
- ...
-</programlisting>
-  </para>
-
-  <para>
-   To sum the column <literal>len</literal> of all films and group
-   the results by <literal>kind</literal>:
-
-<programlisting>
-SELECT kind, sum(len) AS total FROM films GROUP BY kind;
-
-   kind   | total
-----------+-------
- Action   | 07:34
- Comedy   | 02:58
- Drama    | 14:28
- Musical  | 06:42
- Romantic | 04:38
-</programlisting>
-  </para>
-
-  <para>
-   To sum the column <literal>len</literal> of all films, group
-   the results by <literal>kind</literal> and show those group totals
-   that are less than 5 hours:
-
-<programlisting>
-SELECT kind, sum(len) AS total
-    FROM films
-    GROUP BY kind
-    HAVING sum(len) &lt; interval '5 hours';
-
-   kind   | total
-----------+-------
- Comedy   | 02:58
- Romantic | 04:38
-</programlisting>
-  </para>
-
-  <para>
-   The following two examples are identical ways of sorting the individual
-   results according to the contents of the second column
-   (<literal>name</literal>):
-
-<programlisting>
-SELECT * FROM distributors ORDER BY name;
-SELECT * FROM distributors ORDER BY 2;
-
- did |       name
------+------------------
- 109 | 20th Century Fox
- 110 | Bavaria Atelier
- 101 | British Lion
- 107 | Columbia
- 102 | Jean Luc Godard
- 113 | Luso films
- 104 | Mosfilm
- 103 | Paramount
- 106 | Toho
- 105 | United Artists
- 111 | Walt Disney
- 112 | Warner Bros.
- 108 | Westward
-</programlisting>
-  </para>
-
-  <para>
-   The next example shows how to obtain the union of the tables
-   <literal>distributors</literal> and
-   <literal>actors</literal>, restricting the results to those that begin
-   with the letter W in each table.  Only distinct rows are wanted, so the
-   key word <literal>ALL</literal> is omitted.
-
-<programlisting>
-distributors:               actors:
- did |     name              id |     name
------+--------------        ----+----------------
- 108 | Westward               1 | Woody Allen
- 111 | Walt Disney            2 | Warren Beatty
- 112 | Warner Bros.           3 | Walter Matthau
- ...                         ...
-
-SELECT distributors.name
-    FROM distributors
-    WHERE distributors.name LIKE 'W%'
-UNION
-SELECT actors.name
-    FROM actors
-    WHERE actors.name LIKE 'W%';
-
-      name
-----------------
- Walt Disney
- Walter Matthau
- Warner Bros.
- Warren Beatty
- Westward
- Woody Allen
-</programlisting>
-  </para>
-
-  <para>
-   This example shows how to use a function in the <literal>FROM</>
-   clause, both with and without a column definition list:
-
-<programlisting>
-CREATE FUNCTION distributors(int) RETURNS SETOF distributors AS $$
-    SELECT * FROM distributors WHERE did = $1;
-$$ LANGUAGE SQL;
-
-SELECT * FROM distributors(111);
- did |    name
------+-------------
- 111 | Walt Disney
-
-CREATE FUNCTION distributors_2(int) RETURNS SETOF record AS $$
-    SELECT * FROM distributors WHERE did = $1;
-$$ LANGUAGE SQL;
-
-SELECT * FROM distributors_2(111) AS (f1 int, f2 text);
- f1  |     f2
------+-------------
- 111 | Walt Disney
-</programlisting>
-  </para>
-
-  <para>
-   This example shows how to use a simple <literal>WITH</> clause:
-
-<programlisting>
-WITH t AS (
-    SELECT random() as x FROM generate_series(1, 3)
-  )
-SELECT * FROM t
-UNION ALL
-SELECT * FROM t
-
-         x          
---------------------
-  0.534150459803641
-  0.520092216785997
- 0.0735620250925422
-  0.534150459803641
-  0.520092216785997
- 0.0735620250925422
-</programlisting>
-
-   Notice that the <literal>WITH</> query was evaluated only once,
-   so that we got two sets of the same three random values.
-  </para>
-
-  <para>
-   This example uses <literal>WITH RECURSIVE</literal> to find all
-   subordinates (direct or indirect) of the employee Mary, and their
-   level of indirectness, from a table that shows only direct
-   subordinates:
-
-<programlisting>
-WITH RECURSIVE employee_recursive(distance, employee_name, manager_name) AS (
-    SELECT 1, employee_name, manager_name
-    FROM employee
-    WHERE manager_name = 'Mary'
-  UNION ALL
-    SELECT er.distance + 1, e.employee_name, e.manager_name
-    FROM employee_recursive er, employee e
-    WHERE er.employee_name = e.manager_name
-  )
-SELECT distance, employee_name FROM employee_recursive;
-</programlisting>
-
-   Notice the typical form of recursive queries:
-   an initial condition, followed by <literal>UNION</literal>,
-   followed by the recursive part of the query. Be sure that the
-   recursive part of the query will eventually return no tuples, or
-   else the query will loop indefinitely.  (See <xref linkend="queries-with">
-   for more examples.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   Of course, the <command>SELECT</command> statement is compatible
-   with the SQL standard.  But there are some extensions and some
-   missing features.
-  </para>
-
-  <refsect2>
-   <title>Omitted <literal>FROM</literal> Clauses</title>
-
-   <para>
-    <productname>PostgreSQL</productname> allows one to omit the
-    <literal>FROM</literal> clause.  It has a straightforward use to
-    compute the results of simple expressions:
-<programlisting>
-SELECT 2+2;
-
- ?column?
-----------
-        4
-</programlisting>
-    Some other <acronym>SQL</acronym> databases cannot do this except
-    by introducing a dummy one-row table from which to do the
-    <command>SELECT</command>.
-   </para>
-
-   <para>
-    Note that if a <literal>FROM</literal> clause is not specified,
-    the query cannot reference any database tables. For example, the
-    following query is invalid:
-<programlisting>
-SELECT distributors.* WHERE distributors.name = 'Westward';
-</programlisting>
-    <productname>PostgreSQL</productname> releases prior to
-    8.1 would accept queries of this form, and add an implicit entry
-    to the query's <literal>FROM</literal> clause for each table
-    referenced by the query. This is no longer allowed.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Omitting the <literal>AS</literal> Key Word</title>
-
-   <para>
-    In the SQL standard, the optional key word <literal>AS</> can be
-    omitted before an output column name whenever the new column name
-    is a valid column name (that is, not the same as any reserved
-    keyword).  <productname>PostgreSQL</productname> is slightly more
-    restrictive: <literal>AS</> is required if the new column name
-    matches any keyword at all, reserved or not.  Recommended practice is
-    to use <literal>AS</> or double-quote output column names, to prevent
-    any possible conflict against future keyword additions.
-   </para>
-
-   <para>
-    In <literal>FROM</literal> items, both the standard and
-    <productname>PostgreSQL</productname> allow <literal>AS</> to
-    be omitted before an alias that is an unreserved keyword.  But
-    this is impractical for output column names, because of syntactic
-    ambiguities.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title><literal>ONLY</literal> and Parentheses</title>
-
-   <para>
-    The SQL standard requires parentheses around the table name
-    after <literal>ONLY</literal>, as in <literal>SELECT * FROM ONLY
-    (tab1), ONLY (tab2) WHERE ...</literal>.  PostgreSQL supports that
-    as well, but the parentheses are optional.  (This point applies
-    equally to all SQL commands supporting the <literal>ONLY</literal>
-    option.)
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Namespace Available to <literal>GROUP BY</literal> and <literal>ORDER BY</literal></title>
-
-   <para>
-    In the SQL-92 standard, an <literal>ORDER BY</literal> clause can
-    only use output column names or numbers, while a <literal>GROUP
-    BY</literal> clause can only use expressions based on input column
-    names.  <productname>PostgreSQL</productname> extends each of
-    these clauses to allow the other choice as well (but it uses the
-    standard's interpretation if there is ambiguity).
-    <productname>PostgreSQL</productname> also allows both clauses to
-    specify arbitrary expressions.  Note that names appearing in an
-    expression will always be taken as input-column names, not as
-    output-column names.
-   </para>
-
-   <para>
-    SQL:1999 and later use a slightly different definition which is not
-    entirely upward compatible with SQL-92.
-    In most cases, however, <productname>PostgreSQL</productname>
-    will interpret an <literal>ORDER BY</literal> or <literal>GROUP
-    BY</literal> expression the same way SQL:1999 does.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Functional Dependencies</title>
-
-   <para>
-    <productname>PostgreSQL</productname> recognizes functional dependency
-    (allowing columns to be omitted from <literal>GROUP BY</>) only when
-    a table's primary key is included in the <literal>GROUP BY</> list.
-    The SQL standard specifies additional conditions that should be
-    recognized.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title><literal>WINDOW</literal> Clause Restrictions</title>
-
-   <para>
-    The SQL standard provides additional options for the window
-    <replaceable class="parameter">frame_clause</>.
-    <productname>PostgreSQL</productname> currently supports only the
-    options listed above.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title><literal>LIMIT</literal> and <literal>OFFSET</literal></title>
-
-   <para>
-    The clauses <literal>LIMIT</literal> and <literal>OFFSET</literal>
-    are <productname>PostgreSQL</productname>-specific syntax, also
-    used by <productname>MySQL</productname>.  The SQL:2008 standard
-    has introduced the clauses <literal>OFFSET ... FETCH {FIRST|NEXT}
-    ...</literal> for the same functionality, as shown above
-    in <xref linkend="sql-limit" endterm="sql-limit-title">.  This
-    syntax is also used by <productname>IBM DB2</productname>.
-    (Applications written for <productname>Oracle</productname>
-    frequently use a workaround involving the automatically
-    generated <literal>rownum</literal> column, which is not available in
-    PostgreSQL, to implement the effects of these clauses.)
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title><literal>FOR UPDATE</> and <literal>FOR SHARE</></title>
-
-   <para>
-    Although <literal>FOR UPDATE</> appears in the SQL standard, the
-    standard allows it only as an option of <command>DECLARE CURSOR</>.
-    <productname>PostgreSQL</productname> allows it in any <command>SELECT</>
-    query as well as in sub-<command>SELECT</>s, but this is an extension.
-    The <literal>FOR SHARE</> variant, and the <literal>NOWAIT</> option,
-    do not appear in the standard.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Data-Modifying Statements in <literal>WITH</></title>
-
-   <para>
-    <productname>PostgreSQL</productname> allows <command>INSERT</>,
-    <command>UPDATE</>, and <command>DELETE</> to be used as <literal>WITH</>
-    queries.  This is not found in the SQL standard.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Nonstandard Clauses</title>
-
-   <para>
-    The clause <literal>DISTINCT ON</literal> is not defined in the
-    SQL standard.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/select_into.sgmlin b/doc-xc/src/sgml/ref/select_into.sgmlin
deleted file mode 100644
index 6b1d8eb62e..0000000000
--- a/doc-xc/src/sgml/ref/select_into.sgmlin
+++ /dev/null
@@ -1,176 +0,0 @@
-<!--
-doc/src/sgml/ref/select_into.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SELECTINTO">
- <refmeta>
-  <refentrytitle>SELECT INTO</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SELECT INTO</refname>
-  <refpurpose>define a new table from the results of a query</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-selectinto">
-  <primary>SELECT INTO</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-[ WITH [ RECURSIVE ] <replaceable class="parameter">with_query</replaceable> [, ...] ]
-SELECT [ ALL | DISTINCT [ ON ( <replaceable class="parameter">expression</replaceable> [, ...] ) ] ]
-    * | <replaceable class="parameter">expression</replaceable> [ [ AS ] <replaceable class="parameter">output_name</replaceable> ] [, ...]
-    INTO [ TEMPORARY | TEMP | UNLOGGED ] [ TABLE ] <replaceable class="parameter">new_table</replaceable>
-    [ FROM <replaceable class="parameter">from_item</replaceable> [, ...] ]
-    [ WHERE <replaceable class="parameter">condition</replaceable> ]
-    [ GROUP BY <replaceable class="parameter">expression</replaceable> [, ...] ]
-    [ HAVING <replaceable class="parameter">condition</replaceable> [, ...] ]
-    [ WINDOW <replaceable class="parameter">window_name</replaceable> AS ( <replaceable class="parameter">window_definition</replaceable> ) [, ...] ]
-    [ { UNION | INTERSECT | EXCEPT } [ ALL | DISTINCT ] <replaceable class="parameter">select</replaceable> ]
-    [ ORDER BY <replaceable class="parameter">expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [ NULLS { FIRST | LAST } ] [, ...] ]
-    [ LIMIT { <replaceable class="parameter">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="parameter">start</replaceable> [ ROW | ROWS ] ]
-    [ FETCH { FIRST | NEXT } [ <replaceable class="parameter">count</replaceable> ] { ROW | ROWS } ONLY ]
-    [ FOR { UPDATE | SHARE } [ OF <replaceable class="parameter">table_name</replaceable> [, ...] ] [ NOWAIT ] [...] ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>SELECT INTO</command> creates a new table and fills it
-   with data computed by a query.  The data is not returned to the
-   client, as it is with a normal <command>SELECT</command>.  The new
-   table's columns have the names and data types associated with the
-   output columns of the <command>SELECT</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-  <varlistentry>
-   <term><literal>TEMPORARY</literal> or <literal>TEMP</literal></term>
-   <listitem>
-    <para>
-     If specified, the table is created as a temporary table.  Refer
-     to <xref linkend="sql-createtable"> for details.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><literal>UNLOGGED</literal></term>
-   <listitem>
-    <para>
-     If specified, the table is created as an unlogged table.  Refer
-     to <xref linkend="sql-createtable"> for details.
-    </para>
-   </listitem>
-  </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">new_table</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the table to be created.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   All other parameters are described in detail under <xref
-   linkend="sql-select">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <xref linkend="sql-createtableas"> is functionally similar to
-   <command>SELECT INTO</command>.  <command>CREATE TABLE AS</command>
-   is the recommended syntax, since this form of <command>SELECT
-   INTO</command> is not available in <application>ECPG</application>
-   or <application>PL/pgSQL</application>, because they interpret the
-   <literal>INTO</literal> clause differently. Furthermore,
-   <command>CREATE TABLE AS</command> offers a superset of the
-   functionality provided by <command>SELECT INTO</command>.
-  </para>
-
-  <para>
-   Prior to <productname>PostgreSQL</> 8.1, the table created by
-   <command>SELECT INTO</command> included OIDs by default. In
-   <productname>PostgreSQL</productname> 8.1, this is not the case
-   &mdash; to include OIDs in the new table, the <xref
-   linkend="guc-default-with-oids"> configuration variable must be
-   enabled. Alternatively, <command>CREATE TABLE AS</command> can be
-   used with the <literal>WITH OIDS</literal> clause.
-  </para>
-
-<!## XC>
-&xconly;
-   <para>
-    In Postgres-XC, <command>SELECT INTO</command> distributes data
-    of the newly-created table on all the node respecting the default
-    distribution which is <literal>HASH</literal> on the first column
-    having a type that can be distributed. If no columns are found,
-    distribution is done by <literal>ROUNDROBIN</literal>.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    In Postgres-XL, the <command>SELECT INTO</command> distributes data
-    of the newly-created table on all the nodes respecting the default
-    distribution which is <literal>HASH</literal> on the first column
-    having a type that can be distributed. If no columns are found,
-    distribution is done by <literal>ROUNDROBIN</literal>.
-   </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Create a new table <literal>films_recent</literal> consisting of only
-   recent entries from the table <literal>films</literal>:
-
-<programlisting>
-SELECT * INTO films_recent FROM films WHERE date_prod &gt;= '2002-01-01';
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard uses <command>SELECT INTO</command> to
-   represent selecting values into scalar variables of a host program,
-   rather than creating a new table.  This indeed is the usage found
-   in <application>ECPG</application> (see <xref linkend="ecpg">) and
-   <application>PL/pgSQL</application> (see <xref linkend="plpgsql">).
-   The <productname>PostgreSQL</productname> usage of <command>SELECT
-   INTO</command> to represent table creation is historical.  It is
-   best to use <command>CREATE TABLE AS</command> for this purpose in
-   new code.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtableas"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/set.sgmlin b/doc-xc/src/sgml/ref/set.sgmlin
deleted file mode 100644
index 0469eb12ce..0000000000
--- a/doc-xc/src/sgml/ref/set.sgmlin
+++ /dev/null
@@ -1,347 +0,0 @@
-<!--
-doc/src/sgml/ref/set.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SET">
- <refmeta>
-  <refentrytitle>SET</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SET</refname>
-  <refpurpose>change a run-time parameter</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-set">
-  <primary>SET</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SET [ SESSION | LOCAL ] <replaceable class="PARAMETER">configuration_parameter</replaceable> { TO | = } { <replaceable class="PARAMETER">value</replaceable> | '<replaceable class="PARAMETER">value</replaceable>' | DEFAULT }
-SET [ SESSION | LOCAL ] TIME ZONE { <replaceable class="PARAMETER">timezone</replaceable> | LOCAL | DEFAULT }
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   The <command>SET</command> command changes run-time configuration
-   parameters.  Many of the run-time parameters listed in
-   <xref linkend="runtime-config"> can be changed on-the-fly with
-   <command>SET</command>.
-   (But some require superuser privileges to change, and others cannot
-   be changed after server or session start.)
-   <command>SET</command> only affects the value used by the current
-   session.
-  </para>
-
-  <para>
-   If <command>SET</command> (or equivalently <command>SET SESSION</command>)
-   is issued within a transaction that is later aborted, the effects of the
-   <command>SET</command> command disappear when the transaction is rolled
-   back.  Once the surrounding transaction is committed, the effects
-   will persist until the end of the session, unless overridden by another
-   <command>SET</command>.
-  </para>
-
-  <para>
-   The effects of <command>SET LOCAL</command> last only till the end of
-   the current transaction, whether committed or not.  A special case is
-   <command>SET</command> followed by <command>SET LOCAL</command> within
-   a single transaction: the <command>SET LOCAL</command> value will be
-   seen until the end of the transaction, but afterwards (if the transaction
-   is committed) the <command>SET</command> value will take effect.
-  </para>
-
-  <para>
-   The effects of <command>SET</command> or <command>SET LOCAL</command> are
-   also canceled by rolling back to a savepoint that is earlier than the
-   command.
-  </para>
-
-  <para>
-   If <command>SET LOCAL</command> is used within a function that has a
-   <literal>SET</> option for the same variable (see
-   <xref linkend="sql-createfunction">),
-   the effects of the <command>SET LOCAL</command> command disappear at
-   function exit; that is, the value in effect when the function was called is
-   restored anyway.  This allows <command>SET LOCAL</command> to be used for
-   dynamic or repeated changes of a parameter within a function, while still
-   having the convenience of using the <literal>SET</> option to save and
-   restore the caller's value.  However, a regular <command>SET</> command
-   overrides any surrounding function's <literal>SET</> option; its effects
-   will persist unless rolled back.
-  </para>
-
-  <note>
-   <para>
-    In <productname>PostgreSQL</productname> versions 8.0 through 8.2,
-    the effects of a <command>SET LOCAL</command> would be canceled by
-    releasing an earlier savepoint, or by successful exit from a
-    <application>PL/pgSQL</application> exception block.  This behavior
-    has been changed because it was deemed unintuitive.
-   </para>
-  </note>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>SESSION</></term>
-    <listitem>
-     <para>
-      Specifies that the command takes effect for the current session.
-      (This is the default if neither <literal>SESSION</> nor
-      <literal>LOCAL</> appears.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>LOCAL</></term>
-    <listitem>
-     <para>
-      Specifies that the command takes effect for only the current
-      transaction.  After <command>COMMIT</> or <command>ROLLBACK</>,
-      the session-level setting takes effect again.  Note that
-      <command>SET LOCAL</> will appear to have no effect if it is
-      executed outside a <command>BEGIN</> block, since the
-      transaction will end immediately.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">configuration_parameter</replaceable></term>
-    <listitem>
-     <para>
-      Name of a settable run-time parameter.  Available parameters are
-      documented in <xref linkend="runtime-config"> and below.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">value</replaceable></term>
-    <listitem>
-     <para>
-      New value of parameter.  Values can be specified as string
-      constants, identifiers, numbers, or comma-separated lists of
-      these, as appropriate for the particular parameter.
-      <literal>DEFAULT</literal> can be written to specify
-      resetting the parameter to its default value (that is, whatever
-      value it would have had if no <command>SET</> had been executed
-      in the current session).
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-   Besides the configuration parameters documented in <xref
-   linkend="runtime-config">, there are a few that can only be
-   adjusted using the <command>SET</command> command or that have a
-   special syntax:
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>SCHEMA</literal></term>
-     <listitem>
-      <para>
-       <literal>SET SCHEMA '<replaceable>value</>'</> is an alias for
-       <literal>SET search_path TO <replaceable>value</></>.  Only one
-       schema can be specified using this syntax.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>NAMES</literal></term>
-     <listitem>
-      <para>
-       <literal>SET NAMES <replaceable>value</></> is an alias for
-       <literal>SET client_encoding TO <replaceable>value</></>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>SEED</literal></term>
-     <listitem>
-      <para>
-       Sets the internal seed for the random number generator (the
-       function <function>random</function>).  Allowed values are
-       floating-point numbers between -1 and 1, which are then
-       multiplied by 2<superscript>31</>-1.
-      </para>
-
-      <para>
-       The seed can also be set by invoking the function
-       <function>setseed</function>:
-<programlisting>
-SELECT setseed(<replaceable>value</replaceable>);
-</programlisting>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>TIME ZONE</literal></term>
-     <listitem>
-      <para>
-       <literal>SET TIME ZONE <replaceable>value</></> is an alias
-       for <literal>SET timezone TO <replaceable>value</></>.  The
-       syntax <literal>SET TIME ZONE</literal> allows special syntax
-       for the time zone specification.  Here are examples of valid
-       values:
-
-       <variablelist>
-        <varlistentry>
-         <term><literal>'PST8PDT'</literal></term>
-         <listitem>
-          <para>
-           The time zone for Berkeley, California.
-          </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term><literal>'Europe/Rome'</literal></term>
-         <listitem>
-          <para>
-           The time zone for Italy.
-          </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term><literal>-7</literal></term>
-         <listitem>
-          <para>
-           The time zone 7 hours west from UTC (equivalent
-           to PDT).  Positive values are east from UTC.
-          </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term><literal>INTERVAL '-08:00' HOUR TO MINUTE</literal></term>
-         <listitem>
-          <para>
-           The time zone 8 hours west from UTC (equivalent
-           to PST).
-          </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term><literal>LOCAL</literal></term>
-         <term><literal>DEFAULT</literal></term>
-         <listitem>
-          <para>
-           Set the time zone to your local time zone (that is, the
-           server's default value of <varname>timezone</>; if this
-           has not been explicitly set anywhere, it will be the zone that
-           the server's operating system defaults to).
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-
-       See <xref linkend="datatype-timezones"> for more information
-       about time zones.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   The function <function>set_config</function> provides equivalent
-   functionality; see <xref linkend="functions-admin">.
-   Also, it is possible to UPDATE the
-   <link linkend="view-pg-settings"><structname>pg_settings</structname></link>
-   system view to perform the equivalent of <command>SET</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Set the schema search path:
-<programlisting>
-SET search_path TO my_schema, public;
-</programlisting>
-  </para>
-
-  <para>
-   Set the style of date to traditional
-   <productname>POSTGRES</productname> with <quote>day before month</>
-   input convention:
-<screen>
-SET datestyle TO postgres, dmy;
-</screen>
-  </para>
-
-  <para>
-   Set the time zone for Berkeley, California:
-<screen>
-SET TIME ZONE 'PST8PDT';
-</screen>
-  </para>
-
-  <para>
-   Set the time zone for Italy:
-<screen>
-SET TIME ZONE 'Europe/Rome';
-</screen>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <literal>SET TIME ZONE</literal> extends syntax defined in the SQL
-   standard.  The standard allows only numeric time zone offsets while
-<!## PG>
-   <productname>PostgreSQL</productname> allows more flexible
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> allows more flexible
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> allows more flexible
-<!## end>
-   time-zone specifications.  All other <literal>SET</literal>
-<!## PG>
-   features are <productname>PostgreSQL</productname> extensions.
-<!## end>
-<!## XC>
-   features are <productname>Postgres-XC</productname> extensions.
-<!## end>
-<!## XL>
-   features are <productname>Postgres-XL</productname> extensions.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="SQL-RESET"></member>
-   <member><xref linkend="SQL-SHOW"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/set_constraints.sgmlin b/doc-xc/src/sgml/ref/set_constraints.sgmlin
deleted file mode 100644
index 454ac919d6..0000000000
--- a/doc-xc/src/sgml/ref/set_constraints.sgmlin
+++ /dev/null
@@ -1,125 +0,0 @@
-<!-- doc/src/sgml/ref/set_constraints.sgml -->
-<refentry id="SQL-SET-CONSTRAINTS">
- <refmeta>
-  <refentrytitle>SET CONSTRAINTS</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SET CONSTRAINTS</refname>
-  <refpurpose>set constraint check timing for the current transaction</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-set-constraints">
-  <primary>SET CONSTRAINTS</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SET CONSTRAINTS { ALL | <replaceable class="parameter">name</replaceable> [, ...] } { DEFERRED | IMMEDIATE }
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>SET CONSTRAINTS</command> sets the behavior of constraint
-   checking within the current transaction. <literal>IMMEDIATE</literal>
-   constraints are checked at the end of each
-   statement. <literal>DEFERRED</literal> constraints are not checked until
-   transaction commit.  Each constraint has its own
-   <literal>IMMEDIATE</literal> or <literal>DEFERRED</literal> mode.
-  </para>
-
-  <para>
-   Upon creation, a constraint is given one of three
-   characteristics: <literal>DEFERRABLE INITIALLY DEFERRED</literal>,
-   <literal>DEFERRABLE INITIALLY IMMEDIATE</literal>, or
-   <literal>NOT DEFERRABLE</literal>. The third
-   class is always <literal>IMMEDIATE</literal> and is not affected by the
-   <command>SET CONSTRAINTS</command> command.  The first two classes start
-   every transaction in the indicated mode, but their behavior can be changed
-   within a transaction by <command>SET CONSTRAINTS</command>.
-  </para>
-
-  <para>
-   <command>SET CONSTRAINTS</command> with a list of constraint names changes
-   the mode of just those constraints (which must all be deferrable).  Each
-   constraint name can be schema-qualified.  The
-   current schema search path is used to find the first matching name if
-   no schema name is specified.  <command>SET CONSTRAINTS ALL</command>
-   changes the mode of all deferrable constraints.
-  </para>
-
-  <para>
-   When <command>SET CONSTRAINTS</command> changes the mode of a constraint
-   from <literal>DEFERRED</literal>
-   to <literal>IMMEDIATE</literal>, the new mode takes effect
-   retroactively: any outstanding data modifications that would have
-   been checked at the end of the transaction are instead checked during the
-   execution of the <command>SET CONSTRAINTS</command> command.
-   If any such constraint is violated, the <command>SET CONSTRAINTS</command>
-   fails (and does not change the constraint mode).  Thus, <command>SET
-   CONSTRAINTS</command> can be used to force checking of constraints to
-   occur at a specific point in a transaction.
-  </para>
-
-  <para>
-   Currently, only <literal>UNIQUE</>, <literal>PRIMARY KEY</>,
-   <literal>REFERENCES</> (foreign key), and <literal>EXCLUDE</>
-   constraints are affected by this setting.
-   <literal>NOT NULL</> and <literal>CHECK</> constraints are
-   always checked immediately when a row is inserted or modified
-   (<emphasis>not</> at the end of the statement).
-   Uniqueness and exclusion constraints that have not been declared
-   <literal>DEFERRABLE</> are also checked immediately.
-  </para>
-
-  <para>
-   The firing of triggers that are declared as <quote>constraint triggers</>
-   is also controlled by this setting &mdash; they fire at the same time
-   that the associated constraint should be checked.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Because <productname>PostgreSQL</productname> does not require constraint
-   names to be unique within a schema (but only per-table), it is possible
-   that there is more than one match for a specified constraint name.
-   In this case <command>SET CONSTRAINTS</command> will act on all matches.
-   For a non-schema-qualified name, once a match or matches have been found in
-   some schema in the search path, schemas appearing later in the path are not
-   searched.
-  </para>
-
-  <para>
-   This command only alters the behavior of constraints within the
-   current transaction. Thus, if you execute this command outside of a
-   transaction block
-   (<command>BEGIN</command>/<command>COMMIT</command> pair), it will
-   not appear to have any effect.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   This command complies with the behavior defined in the SQL
-   standard, except for the limitation that, in
-   <productname>PostgreSQL</productname>, it does not apply to
-   <literal>NOT NULL</> and <literal>CHECK</> constraints.
-   Also, <productname>PostgreSQL</productname> checks non-deferrable
-   uniqueness constraints immediately, not at end of statement as the
-   standard would suggest.
-  </para>
-
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/set_role.sgmlin b/doc-xc/src/sgml/ref/set_role.sgmlin
deleted file mode 100644
index 8e0147db81..0000000000
--- a/doc-xc/src/sgml/ref/set_role.sgmlin
+++ /dev/null
@@ -1,150 +0,0 @@
-<!--
-doc/src/sgml/ref/set_role.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SET-ROLE">
- <refmeta>
-  <refentrytitle>SET ROLE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SET ROLE</refname>
-  <refpurpose>set the current user identifier of the current session</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-set-role">
-  <primary>SET ROLE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SET [ SESSION | LOCAL ] ROLE <replaceable class="parameter">role_name</replaceable>
-SET [ SESSION | LOCAL ] ROLE NONE
-RESET ROLE
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   This command sets the current user
-   identifier of the current SQL session to be <replaceable
-   class="parameter">role_name</replaceable>.  The role name can be
-   written as either an identifier or a string literal.
-   After <command>SET ROLE</>, permissions checking for SQL commands
-   is carried out as though the named role were the one that had logged
-   in originally.
-  </para>
-
-  <para>
-   The specified <replaceable class="parameter">role_name</replaceable>
-   must be a role that the current session user is a member of.
-   (If the session user is a superuser, any role can be selected.)
-  </para>
-
-  <para>
-   The <literal>SESSION</> and <literal>LOCAL</> modifiers act the same
-   as for the regular <xref linkend="SQL-SET">
-   command.
-  </para>
-
-  <para>
-   The <literal>NONE</> and <literal>RESET</> forms reset the current
-   user identifier to be the current session user identifier.
-   These forms can be executed by any user.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Using this command, it is possible to either add privileges or restrict
-   one's privileges.  If the session user role has the <literal>INHERITS</>
-   attribute, then it automatically has all the privileges of every role that
-   it could <command>SET ROLE</> to; in this case <command>SET ROLE</>
-   effectively drops all the privileges assigned directly to the session user
-   and to the other roles it is a member of, leaving only the privileges
-   available to the named role.  On the other hand, if the session user role
-   has the <literal>NOINHERITS</> attribute, <command>SET ROLE</> drops the
-   privileges assigned directly to the session user and instead acquires the
-   privileges available to the named role.
-  </para>
-
-  <para>
-   In particular, when a superuser chooses to <command>SET ROLE</> to a
-   non-superuser role, she loses her superuser privileges.
-  </para>
-
-  <para>
-   <command>SET ROLE</> has effects comparable to
-   <xref linkend="sql-set-session-authorization">, but the privilege
-   checks involved are quite different.  Also,
-   <command>SET SESSION AUTHORIZATION</> determines which roles are
-   allowable for later <command>SET ROLE</> commands, whereas changing
-   roles with <command>SET ROLE</> does not change the set of roles
-   allowed to a later <command>SET ROLE</>.
-  </para>
-
-  <para>
-   <command>SET ROLE</> does not process session variables as specified by
-   the role's <xref linkend="sql-alterrole"> settings;  this only happens during
-   login.
-  </para>
-
-  <para>
-   <command>SET ROLE</> cannot be used within a
-   <literal>SECURITY DEFINER</> function.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-<programlisting>
-SELECT SESSION_USER, CURRENT_USER;
-
- session_user | current_user 
---------------+--------------
- peter        | peter
-
-SET ROLE 'paul';
-
-SELECT SESSION_USER, CURRENT_USER;
-
- session_user | current_user 
---------------+--------------
- peter        | paul
-</programlisting>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <productname>PostgreSQL</productname>
-   allows identifier syntax (<literal>"rolename"</literal>), while
-   the SQL standard requires the role name to be written as a string
-   literal.  SQL does not allow this command during a transaction;
-   <productname>PostgreSQL</productname> does not make this
-   restriction because there is no reason to.
-   The <literal>SESSION</> and <literal>LOCAL</> modifiers are a
-   <productname>PostgreSQL</productname> extension, as is the
-   <literal>RESET</> syntax.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-set-session-authorization"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/set_session_auth.sgmlin b/doc-xc/src/sgml/ref/set_session_auth.sgmlin
deleted file mode 100644
index 79e63865c1..0000000000
--- a/doc-xc/src/sgml/ref/set_session_auth.sgmlin
+++ /dev/null
@@ -1,128 +0,0 @@
-<!-- doc/src/sgml/ref/set_session_auth.sgml -->
-<refentry id="SQL-SET-SESSION-AUTHORIZATION">
- <refmeta>
-  <refentrytitle>SET SESSION AUTHORIZATION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SET SESSION AUTHORIZATION</refname>
-  <refpurpose>set the session user identifier and the current user identifier of the current session</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-set-session-authorization">
-  <primary>SET SESSION AUTHORIZATION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SET [ SESSION | LOCAL ] SESSION AUTHORIZATION <replaceable class="parameter">user_name</replaceable>
-SET [ SESSION | LOCAL ] SESSION AUTHORIZATION DEFAULT
-RESET SESSION AUTHORIZATION
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   This command sets the session user identifier and the current user
-   identifier of the current SQL session to be <replaceable
-   class="parameter">user_name</replaceable>.  The user name can be
-   written as either an identifier or a string literal.  Using this
-   command, it is possible, for example, to temporarily become an
-   unprivileged user and later switch back to being a superuser.
-  </para>
-
-  <para>
-   The session user identifier is initially set to be the (possibly
-   authenticated) user name provided by the client.  The current user
-   identifier is normally equal to the session user identifier, but
-   might change temporarily in the context of <literal>SECURITY DEFINER</>
-   functions and similar mechanisms; it can also be changed by
-   <xref linkend="sql-set-role">.
-   The current user identifier is relevant for permission checking.
-  </para>
-
-  <para>
-   The session user identifier can be changed only if the initial session
-   user (the <firstterm>authenticated user</firstterm>) had the
-   superuser privilege.  Otherwise, the command is accepted only if it
-   specifies the authenticated user name.
-  </para>
-
-  <para>
-   The <literal>SESSION</> and <literal>LOCAL</> modifiers act the same
-   as for the regular <xref linkend="SQL-SET">
-   command.
-  </para>
-
-  <para>
-   The <literal>DEFAULT</> and <literal>RESET</> forms reset the session
-   and current user identifiers to be the originally authenticated user
-   name.  These forms can be executed by any user.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <command>SET SESSION AUTHORIZATION</> cannot be used within a
-   <literal>SECURITY DEFINER</> function.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-<programlisting>
-SELECT SESSION_USER, CURRENT_USER;
-
- session_user | current_user 
---------------+--------------
- peter        | peter
-
-SET SESSION AUTHORIZATION 'paul';
-
-SELECT SESSION_USER, CURRENT_USER;
-
- session_user | current_user 
---------------+--------------
- paul         | paul
-</programlisting>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL standard allows some other expressions to appear in place
-   of the literal <replaceable>user_name</replaceable>, but these options
-   are not important in practice.  <productname>PostgreSQL</productname>
-   allows identifier syntax (<literal>"username"</literal>), which SQL
-   does not.  SQL does not allow this command during a transaction;
-   <productname>PostgreSQL</productname> does not make this
-   restriction because there is no reason to.
-   The <literal>SESSION</> and <literal>LOCAL</> modifiers are a
-   <productname>PostgreSQL</productname> extension, as is the
-   <literal>RESET</> syntax.
-  </para>
-
-  <para>
-   The privileges necessary to execute this command are left
-   implementation-defined by the standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-set-role"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/set_transaction.sgmlin b/doc-xc/src/sgml/ref/set_transaction.sgmlin
deleted file mode 100644
index 98be8541d9..0000000000
--- a/doc-xc/src/sgml/ref/set_transaction.sgmlin
+++ /dev/null
@@ -1,215 +0,0 @@
-<!-- doc/src/sgml/ref/set_transaction.sgml -->
-<refentry id="SQL-SET-TRANSACTION">
- <refmeta>
-  <refentrytitle>SET TRANSACTION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SET TRANSACTION</refname>
-  <refpurpose>set the characteristics of the current transaction</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-set-transaction">
-  <primary>SET TRANSACTION</primary>
- </indexterm>
-
- <indexterm>
-  <primary>transaction isolation level</primary>
-  <secondary>setting</secondary>
- </indexterm>
-
- <indexterm>
-  <primary>read-only transaction</primary>
-  <secondary>setting</secondary>
- </indexterm>
-
- <indexterm>
-  <primary>deferrable transaction</primary>
-  <secondary>setting</secondary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SET TRANSACTION <replaceable class="parameter">transaction_mode</replaceable> [, ...]
-SET SESSION CHARACTERISTICS AS TRANSACTION <replaceable class="parameter">transaction_mode</replaceable> [, ...]
-
-<phrase>where <replaceable class="parameter">transaction_mode</replaceable> is one of:</phrase>
-
-    ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED }
-    READ WRITE | READ ONLY
-    [ NOT ] DEFERRABLE
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   The <command>SET TRANSACTION</command> command sets the
-   characteristics of the current transaction. It has no effect on any
-   subsequent transactions.  <command>SET SESSION
-   CHARACTERISTICS</command> sets the default transaction
-   characteristics for subsequent transactions of a session.  These
-   defaults can be overridden by <command>SET TRANSACTION</command>
-   for an individual transaction.
-  </para>
-
-  <para>
-   The available transaction characteristics are the transaction
-   isolation level, the transaction access mode (read/write or
-   read-only), and the deferrable mode.
-  </para>
-
-  <para>
-   The isolation level of a transaction determines what data the
-   transaction can see when other transactions are running concurrently:
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>READ COMMITTED</literal></term>
-     <listitem>
-      <para>
-       A statement can only see rows committed before it began. This
-       is the default.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>REPEATABLE READ</literal></term>
-     <listitem>
-      <para>
-       All statements of the current transaction can only see rows committed
-       before the first query or data-modification statement was executed in
-       this transaction.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>SERIALIZABLE</literal></term>
-     <listitem>
-      <para>
-       All statements of the current transaction can only see rows committed
-       before the first query or data-modification statement was executed in
-       this transaction.  If a pattern of reads and writes among concurrent
-       serializable transactions would create a situation which could not
-       have occurred for any serial (one-at-a-time) execution of those
-       transactions, one of them will be rolled back with a
-       <literal>serialization_failure</literal> <literal>SQLSTATE</literal>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-   The SQL standard defines one additional level, <literal>READ
-   UNCOMMITTED</literal>.
-   In <productname>PostgreSQL</productname> <literal>READ
-   UNCOMMITTED</literal> is treated as <literal>READ COMMITTED</literal>.
-  </para>
-
-  <para>
-   The transaction isolation level cannot be changed after the first query or
-   data-modification statement (<command>SELECT</command>,
-   <command>INSERT</command>, <command>DELETE</command>,
-   <command>UPDATE</command>, <command>FETCH</command>, or
-   <command>COPY</command>) of a transaction has been executed.  See
-   <xref linkend="mvcc"> for more information about transaction
-   isolation and concurrency control.
-  </para>
-
-  <para>
-   The transaction access mode determines whether the transaction is
-   read/write or read-only.  Read/write is the default.  When a
-   transaction is read-only, the following SQL commands are
-   disallowed: <literal>INSERT</literal>, <literal>UPDATE</literal>,
-   <literal>DELETE</literal>, and <literal>COPY FROM</literal> if the
-   table they would write to is not a temporary table; all
-   <literal>CREATE</literal>, <literal>ALTER</literal>, and
-   <literal>DROP</literal> commands; <literal>COMMENT</literal>,
-   <literal>GRANT</literal>, <literal>REVOKE</literal>,
-   <literal>TRUNCATE</literal>; and <literal>EXPLAIN ANALYZE</literal>
-   and <literal>EXECUTE</literal> if the command they would execute is
-   among those listed.  This is a high-level notion of read-only that
-   does not prevent all writes to disk.
-  </para>
-
-  <para>
-   The <literal>DEFERRABLE</literal> transaction property has no effect
-   unless the transaction is also <literal>SERIALIZABLE</literal> and
-   <literal>READ ONLY</literal>.  When all of these properties are set on a
-   transaction, the transaction may block when first acquiring its snapshot,
-   after which it is able to run without the normal overhead of a
-   <literal>SERIALIZABLE</literal> transaction and without any risk of
-   contributing to or being cancelled by a serialization failure.  This mode
-   is well suited for long-running reports or backups.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   If <command>SET TRANSACTION</command> is executed without a prior
-   <command>START TRANSACTION</command> or  <command>BEGIN</command>,
-   it will appear to have no effect, since the transaction will immediately
-   end.
-  </para>
-
-  <para>
-   It is possible to dispense with <command>SET TRANSACTION</command>
-   by instead specifying the desired <replaceable
-   class="parameter">transaction_modes</replaceable> in
-   <command>BEGIN</command> or <command>START TRANSACTION</command>.
-  </para>
-
-  <para>
-   The session default transaction modes can also be set by setting the
-   configuration parameters <xref linkend="guc-default-transaction-isolation">,
-   <xref linkend="guc-default-transaction-read-only">, and
-   <xref linkend="guc-default-transaction-deferrable">.
-   (In fact <command>SET SESSION CHARACTERISTICS</command> is just a
-   verbose equivalent for setting these variables with <command>SET</>.)
-   This means the defaults can be set in the configuration file, via
-   <command>ALTER DATABASE</>, etc.  Consult <xref linkend="runtime-config">
-   for more information.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-SET-TRANSACTION-3">
-  <title>Compatibility</title>
-
-  <para>
-   Both commands are defined in the <acronym>SQL</acronym> standard.
-   <literal>SERIALIZABLE</literal> is the default transaction
-   isolation level in the standard.  In
-   <productname>PostgreSQL</productname> the default is ordinarily
-   <literal>READ COMMITTED</literal>, but you can change it as
-   mentioned above.
-  </para>
-
-  <para>
-   In the SQL standard, there is one other transaction characteristic
-   that can be set with these commands: the size of the diagnostics
-   area.  This concept is specific to embedded SQL, and therefore is
-   not implemented in the <productname>PostgreSQL</productname> server.
-  </para>
-
-  <para>
-   The <literal>DEFERRABLE</literal>
-   <replaceable class="parameter">transaction_mode</replaceable>
-   is a <productname>PostgreSQL</productname> language extension.
-  </para>
-
-  <para>
-   The SQL standard requires commas between successive <replaceable
-   class="parameter">transaction_modes</replaceable>, but for historical
-   reasons <productname>PostgreSQL</productname> allows the commas to be
-   omitted.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/show.sgmlin b/doc-xc/src/sgml/ref/show.sgmlin
deleted file mode 100644
index 5ddc76db57..0000000000
--- a/doc-xc/src/sgml/ref/show.sgmlin
+++ /dev/null
@@ -1,227 +0,0 @@
-<!--
-doc/src/sgml/ref/show.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SHOW">
- <refmeta>
-  <refentrytitle>SHOW</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SHOW</refname>
-  <refpurpose>show the value of a run-time parameter</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-show">
-  <primary>SHOW</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SHOW <replaceable class="PARAMETER">name</replaceable>
-SHOW ALL
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>SHOW</command> will display the current setting of
-   run-time parameters. These variables can be set using the
-   <command>SET</command> statement, by editing the
-   <filename>postgresql.conf</filename> configuration file, through
-   the <envar>PGOPTIONS</envar> environmental variable (when using
-   <application>libpq</> or a <application>libpq</>-based
-   application), or through command-line flags when starting the
-   <command>postgres</command> server.  See <xref
-   linkend="runtime-config"> for details.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name of a run-time parameter.  Available parameters are
-      documented in <xref linkend="runtime-config"> and on the <xref
-      linkend="SQL-SET"> reference page.  In
-      addition, there are a few parameters that can be shown but not
-      set:
-
-      <variablelist>
-       <varlistentry>
-        <term><literal>SERVER_VERSION</literal></term>
-        <listitem>
-         <para>
-          Shows the server's version number.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>SERVER_ENCODING</literal></term>
-        <listitem>
-         <para>
-          Shows the server-side character set encoding.  At present,
-          this parameter can be shown but not set, because the
-          encoding is determined at database creation time.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>LC_COLLATE</literal></term>
-        <listitem>
-         <para>
-          Shows the database's locale setting for collation (text
-          ordering).  At present, this parameter can be shown but not
-          set, because the setting is determined at database creation
-          time.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>LC_CTYPE</literal></term>
-        <listitem>
-         <para>
-          Shows the database's locale setting for character
-          classification.  At present, this parameter can be shown but
-          not set, because the setting is determined at database creation
-          time.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>IS_SUPERUSER</literal></term>
-        <listitem>
-         <para>
-          True if the current role has superuser privileges.
-         </para>
-        </listitem>
-       </varlistentry>
-      </variablelist>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ALL</literal></term>
-    <listitem>
-     <para>
-      Show the values of all configuration parameters, with descriptions.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   The function <function>current_setting</function> produces
-   equivalent output; see <xref linkend="functions-admin">.
-   Also, the
-   <link linkend="view-pg-settings"><structname>pg_settings</structname></link>
-   system view produces the same information.
-
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   <productname>Postgres-XC</> only shows local settings.  This
-   restriction may be solved in the future releases.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <productname>Postgres-XL</> only shows local settings.  This
-   restriction may be changed in the future releases.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Show the current setting of the parameter <varname>DateStyle</varname>:
-
-<programlisting>
-SHOW DateStyle;
- DateStyle
------------
- ISO, MDY
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-   Show the current setting of the parameter <varname>geqo</varname>:
-<programlisting>
-SHOW geqo;
- geqo
-------
- on
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-   Show all settings:
-<programlisting>
-SHOW ALL;
-            name         | setting |                description                                                          
--------------------------+---------+-------------------------------------------------
- allow_system_table_mods | off     | Allows modifications of the structure of ...
-    .
-    .
-    .
- xmloption               | content | Sets whether XML data in implicit parsing ...
- zero_damaged_pages      | off     | Continues processing past damaged page headers.
-(196 rows)
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The <command>SHOW</command> command is a
-<!## PG>
-   <productname>PostgreSQL</productname> extension.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extension.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extension.
-<!## end>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="SQL-SET"></member>
-   <member><xref linkend="SQL-RESET"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/start_transaction.sgmlin b/doc-xc/src/sgml/ref/start_transaction.sgmlin
deleted file mode 100644
index 8262f40784..0000000000
--- a/doc-xc/src/sgml/ref/start_transaction.sgmlin
+++ /dev/null
@@ -1,115 +0,0 @@
-<!--
-doc/src/sgml/ref/start_transaction.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-START-TRANSACTION">
- <refmeta>
-  <refentrytitle>START TRANSACTION</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>START TRANSACTION</refname>
-  <refpurpose>start a transaction block</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-start-transaction">
-  <primary>START TRANSACTION</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-START TRANSACTION [ <replaceable class="parameter">transaction_mode</replaceable> [, ...] ]
-
-<phrase>where <replaceable class="parameter">transaction_mode</replaceable> is one of:</phrase>
-
-    ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED }
-    READ WRITE | READ ONLY
-    [ NOT ] DEFERRABLE
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   This command begins a new transaction block. If the isolation level,
-   read/write mode, or deferrable mode is specified, the new transaction has those
-   characteristics, as if <xref linkend="sql-set-transaction"> was executed. This is the same
-   as the <xref linkend="sql-begin"> command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <para>
-   Refer to <xref linkend="sql-set-transaction"> for information on the meaning
-   of the parameters to this statement.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   In the standard, it is not necessary to issue <command>START TRANSACTION</>
-   to start a transaction block: any SQL command implicitly begins a block.
-<!## PG>
-   <productname>PostgreSQL</productname>'s behavior can be seen as implicitly
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>'s behavior can be seen as implicitly
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>'s behavior can be seen as implicitly
-<!## end>
-   issuing a <command>COMMIT</command> after each command that does not
-   follow <command>START TRANSACTION</> (or <command>BEGIN</command>),
-   and it is therefore often called <quote>autocommit</>.
-   Other relational database systems might offer an autocommit feature
-   as a convenience.
-  </para>
-
-  <para>
-   The <literal>DEFERRABLE</literal>
-   <replaceable class="parameter">transaction_mode</replaceable>
-   is a <productname>PostgreSQL</productname> language extension.
-  </para>
-
-  <para>
-   The SQL standard requires commas between successive <replaceable
-   class="parameter">transaction_modes</replaceable>, but for historical
-<!## PG>
-   reasons <productname>PostgreSQL</productname> allows the commas to be
-<!## end>
-<!## XC>
-   reasons <productname>Postgres-XC</productname> allows the commas to be
-<!## end>
-<!## XL>
-   reasons <productname>Postgres-XL</productname> allows the commas to be
-<!## end>
-   omitted.
-  </para>
-
-  <para>
-   See also the compatibility section of <xref linkend="sql-set-transaction">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-begin"></member>
-   <member><xref linkend="sql-commit"></member>
-   <member><xref linkend="sql-rollback"></member>
-   <member><xref linkend="sql-savepoint"></member>
-   <member><xref linkend="sql-set-transaction"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/truncate.sgmlin b/doc-xc/src/sgml/ref/truncate.sgmlin
deleted file mode 100644
index 526b849df3..0000000000
--- a/doc-xc/src/sgml/ref/truncate.sgmlin
+++ /dev/null
@@ -1,233 +0,0 @@
-<!--
-doc/src/sgml/ref/truncate.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-TRUNCATE">
- <refmeta>
-  <refentrytitle>TRUNCATE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>TRUNCATE</refname>
-  <refpurpose>empty a table or set of tables</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-truncate">
-  <primary>TRUNCATE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-TRUNCATE [ TABLE ] [ ONLY ] <replaceable class="PARAMETER">name</replaceable> [, ... ]
-    [ RESTART IDENTITY | CONTINUE IDENTITY ] [ CASCADE | RESTRICT ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-
-  <para>
-   <command>TRUNCATE</command> quickly removes all rows from a set of
-   tables. It has the same effect as an unqualified
-   <command>DELETE</command> on each table, but since it does not actually
-   scan the tables it is faster. Furthermore, it reclaims disk space
-   immediately, rather than requiring a subsequent <command>VACUUM</command>
-   operation. This is most useful on large tables.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">name</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of a table to be
-      truncated.  If <literal>ONLY</> is specified, only that table is
-      truncated.  If <literal>ONLY</> is not specified, the table and
-      all its descendant tables (if any) are truncated.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTART IDENTITY</literal></term>
-    <listitem>
-     <para>
-      Automatically restart sequences owned by columns of
-      the truncated table(s). 
-<!## XL>
-This feature is not implemented in
-      Postgres-XL currently.
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CONTINUE IDENTITY</literal></term>
-    <listitem>
-     <para>
-      Do not change the values of sequences.  This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CASCADE</literal></term>
-    <listitem>
-     <para>
-      Automatically truncate all tables that have foreign-key references
-      to any of the named tables, or to any tables added to the group
-      due to <literal>CASCADE</literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>RESTRICT</literal></term>
-    <listitem>
-     <para>
-      Refuse to truncate if any of the tables have foreign-key references
-      from tables that are not listed in the command.  This is the default.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   You must have the <literal>TRUNCATE</literal> privilege on a table
-   to truncate it.
-  </para>
-
-  <para>
-   <command>TRUNCATE</> acquires an <literal>ACCESS EXCLUSIVE</> lock on each
-   table it operates on, which blocks all other concurrent operations
-   on the table.  When <literal>RESTART IDENTITY</> is specified, any
-   sequences that are to be restarted are likewise locked exclusively.
-   If concurrent access to a table is required, then
-   the <command>DELETE</> command should be used instead.
-  </para>
-
-  <para>
-   <command>TRUNCATE</> cannot be used on a table that has foreign-key
-   references from other tables, unless all such tables are also truncated
-   in the same command.  Checking validity in such cases would require table
-   scans, and the whole point is not to do one.  The <literal>CASCADE</>
-   option can be used to automatically include all dependent tables &mdash;
-   but be very careful when using this option, or else you might lose data you
-   did not intend to!
-  </para>
-
-  <para>
-   <command>TRUNCATE</> will not fire any <literal>ON DELETE</literal>
-   triggers that might exist for the tables.  But it will fire
-   <literal>ON TRUNCATE</literal> triggers.
-   If <literal>ON TRUNCATE</> triggers are defined for any of
-   the tables, then all <literal>BEFORE TRUNCATE</literal> triggers are
-   fired before any truncation happens, and all <literal>AFTER
-   TRUNCATE</literal> triggers are fired after the last truncation is
-   performed and any sequences are reset.
-   The triggers will fire in the order that the tables are
-   to be processed (first those listed in the command, and then any
-   that were added due to cascading).
-  </para>
-
-  <warning>
-   <para>
-    <command>TRUNCATE</> is not MVCC-safe (see <xref linkend="mvcc">
-     for general information about MVCC).  After truncation, the table
-     will appear empty to all concurrent transactions, even if they
-     are using a snapshot taken before the truncation occurred.  This
-     will only be an issue for a transaction that did not access the
-     truncated table before the truncation happened &mdash; any
-     transaction that has done so would hold at least an
-     <literal>ACCESS SHARE</literal> lock, which would block
-     <command>TRUNCATE</> until that transaction completes.  So
-     truncation will not cause any apparent inconsistency in the table
-     contents for successive queries on the same table, but it could
-     cause visible inconsistency between the contents of the truncated
-     table and other tables in the database.
-   </para>
-  </warning>
-
-  <para>
-   <command>TRUNCATE</> is transaction-safe with respect to the data
-   in the tables: the truncation will be safely rolled back if the surrounding
-   transaction does not commit.
-  </para>
-
-  <para>
-   When <literal>RESTART IDENTITY</> is specified, the implied
-   <command>ALTER SEQUENCE RESTART</> operations are also done
-   transactionally; that is, they will be rolled back if the surrounding
-   transaction does not commit.  This is unlike the normal behavior of
-   <command>ALTER SEQUENCE RESTART</>.  Be aware that if any additional
-   sequence operations are done on the restarted sequences before the
-   transaction rolls back, the effects of these operations on the sequences
-   will be rolled back, but not their effects on <function>currval()</>;
-   that is, after the transaction <function>currval()</> will continue to
-   reflect the last sequence value obtained inside the failed transaction,
-   even though the sequence itself may no longer be consistent with that.
-   This is similar to the usual behavior of <function>currval()</> after
-   a failed transaction.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Truncate the tables <literal>bigtable</literal> and
-   <literal>fattable</literal>:
-
-<programlisting>
-TRUNCATE bigtable, fattable;
-</programlisting>
-  </para>
-
-  <para>
-   The same, and also reset any associated sequence generators:
-
-<programlisting>
-TRUNCATE bigtable, fattable RESTART IDENTITY;
-</programlisting>
-  </para>
-
-  <para>
-   Truncate the table <literal>othertable</literal>, and cascade to any tables
-   that reference <literal>othertable</literal> via foreign-key
-   constraints:
-
-<programlisting>
-TRUNCATE othertable CASCADE;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   The SQL:2008 standard includes a <command>TRUNCATE</command> command
-   with the syntax <literal>TRUNCATE TABLE
-   <replaceable>tablename</replaceable></literal>.  The clauses
-   <literal>CONTINUE IDENTITY</literal>/<literal>RESTART IDENTITY</literal>
-   also appear in that standard, but have slightly different though related
-   meanings.  Some of the concurrency behavior of this command is left
-   implementation-defined by the standard, so the above notes should be
-   considered and compared with other implementations if necessary.
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/unlisten.sgmlin b/doc-xc/src/sgml/ref/unlisten.sgmlin
deleted file mode 100644
index d2a6c95324..0000000000
--- a/doc-xc/src/sgml/ref/unlisten.sgmlin
+++ /dev/null
@@ -1,152 +0,0 @@
-<!--
-doc/src/sgml/ref/unlisten.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-UNLISTEN">
- <refmeta>
-  <refentrytitle>UNLISTEN</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>UNLISTEN</refname>
-  <refpurpose>stop listening for a notification</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-unlisten">
-  <primary>UNLISTEN</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-UNLISTEN { <replaceable class="PARAMETER">channel</replaceable> | * }
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-<!## XC>
-&xconly;
-  <para>
-   <command>UNLISTEN</> statement has not been supported
-   in <productname>Postgres-XC</> yet.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   <command>UNLISTEN</> statement is not yet supported
-   in <productname>Postgres-XL</>.
-  </para>
-<!## end>
-
-<!## PG>
-
-  <para>
-   <command>UNLISTEN</command> is used to remove an existing
-   registration for <command>NOTIFY</command> events.
-   <command>UNLISTEN</command> cancels any existing registration of
-   the current <productname>PostgreSQL</productname> session as a
-   listener on the notification channel named <replaceable
-   class="PARAMETER">channel</replaceable>.  The special wildcard
-   <literal>*</literal> cancels all listener registrations for the
-   current session.
-  </para>
-
-  <para>
-   <xref linkend="sql-notify">
-   contains a more extensive
-   discussion of the use of <command>LISTEN</command> and
-   <command>NOTIFY</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">channel</replaceable></term>
-    <listitem>
-     <para>
-      Name of a notification channel (any identifier).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>*</literal></term>
-    <listitem>
-     <para>
-      All current listen registrations for this session are cleared.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   You can unlisten something you were not listening for; no warning or error
-   will appear.
-  </para>
-
-  <para>
-   At the end of each session, <command>UNLISTEN *</command> is
-   automatically executed.
-  </para>
-
-  <para>
-   A transaction that has executed <command>UNLISTEN</command> cannot be
-   prepared for two-phase commit.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   To make a registration:
-
-<programlisting>
-LISTEN virtual;
-NOTIFY virtual;
-Asynchronous notification "virtual" received from server process with PID 8448.
-</programlisting>
-  </para>
-
-  <para>
-   Once <command>UNLISTEN</> has been executed, further <command>NOTIFY</>
-   messages will be ignored:
-
-<programlisting>
-UNLISTEN virtual;
-NOTIFY virtual;
--- no NOTIFY event is received
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>UNLISTEN</command> command in the SQL standard.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-listen"></member>
-   <member><xref linkend="sql-notify"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/unpause_cluster.sgmlin b/doc-xc/src/sgml/ref/unpause_cluster.sgmlin
deleted file mode 100644
index d138370107..0000000000
--- a/doc-xc/src/sgml/ref/unpause_cluster.sgmlin
+++ /dev/null
@@ -1,55 +0,0 @@
-<!--
-doc/src/sgml/ref/unpause_cluster.sgml
-PostgreSQL documentation
--->
-<!## XL>
-<refentry id="SQL-UNPAUSECLUSTER">
- <refmeta>
-  <refentrytitle>UNPAUSE CLUSTER</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>UNPAUSE CLUSTER</refname>
-  <refpurpose>unpause the <productname>Postgres-XL</productname> cluster</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-pausecluster">
-  <primary>UNPAUSE CLUSTER</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-UNPAUSE CLUSTER
-
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&xlonly;
-
-  <para>
-   <command>UNPAUSE CLUSTER </command> is a SQL command specific
-   to <productname>Postgres-XL</productname> that unpauses 
-   cluster operation.
-  </para>
-
-  <para>
-   If the DBA previously paused the cluster via the command <xref linkend="sql-pausecluster">, the DBA can resume operation vi <command>UNPAUSE CLUSTER</command>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-  <para>
-   <command>UNPAUSE CLUSTER</command> does not conform to the <acronym>
-   SQL</acronym> standards, it is a Postgres-XL specific command.
-  </para>
- </refsect1>
-
-</refentry>
-<!## end>
-
diff --git a/doc-xc/src/sgml/ref/update.sgmlin b/doc-xc/src/sgml/ref/update.sgmlin
deleted file mode 100644
index 0a05ede893..0000000000
--- a/doc-xc/src/sgml/ref/update.sgmlin
+++ /dev/null
@@ -1,461 +0,0 @@
-<!--
-doc/src/sgml/ref/update.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-UPDATE">
- <refmeta>
-  <refentrytitle>UPDATE</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>UPDATE</refname>
-  <refpurpose>update rows of a table</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-update">
-  <primary>UPDATE</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<!## PG>
-<synopsis>
-[ WITH [ RECURSIVE ] <replaceable class="parameter">with_query</replaceable> [, ...] ]
-UPDATE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ [ AS ] <replaceable class="parameter">alias</replaceable> ]
-    SET { <replaceable class="PARAMETER">column</replaceable> = { <replaceable class="PARAMETER">expression</replaceable> | DEFAULT } |
-          ( <replaceable class="PARAMETER">column</replaceable> [, ...] ) = ( { <replaceable class="PARAMETER">expression</replaceable> | DEFAULT } [, ...] ) } [, ...]
-    [ FROM <replaceable class="PARAMETER">from_list</replaceable> ]
-    [ WHERE <replaceable class="PARAMETER">condition</replaceable> | WHERE CURRENT OF <replaceable class="PARAMETER">cursor_name</replaceable> ]
-    [ RETURNING * | <replaceable class="parameter">output_expression</replaceable> [ [ AS ] <replaceable class="parameter">output_name</replaceable> ] [, ...] ]
-</synopsis>
-<!## end>
-<!## XC>
-<synopsis>
-UPDATE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ [ AS ] <replaceable class="parameter">alias</replaceable> ]
-    SET { <replaceable class="PARAMETER">column</replaceable> = { <replaceable class="PARAMETER">expression</replaceable> | DEFAULT } |
-          ( <replaceable class="PARAMETER">column</replaceable> [, ...] ) = ( { <replaceable class="PARAMETER">expression</replaceable> | DEFAULT } [, ...] ) } [, ...]
-    [ WHERE <replaceable class="PARAMETER">condition</replaceable> ]
-    [ RETURNING * | <replaceable class="parameter">output_expression</replaceable> [ [ AS ] <replaceable class="parameter">output_name</replaceable> ] [, ...] ]
-</synopsis>
-<!## end>
-<!## XL>
-<synopsis>
-UPDATE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ [ AS ] <replaceable class="parameter">alias</replaceable> ]
-    SET { <replaceable class="PARAMETER">column</replaceable> = { <replaceable class="PARAMETER">expression</replaceable> | DEFAULT } |
-          ( <replaceable class="PARAMETER">column</replaceable> [, ...] ) = ( { <replaceable class="PARAMETER">expression</replaceable> | DEFAULT } [, ...] ) } [, ...]
-    [ WHERE <replaceable class="PARAMETER">condition</replaceable> ]
-    [ RETURNING * | <replaceable class="parameter">output_expression</replaceable> [ [ AS ] <replaceable class="parameter">output_name</replaceable> ] [, ...] ]
-</synopsis>
-<!## end>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>UPDATE</command> changes the values of the specified
-   columns in all rows that satisfy the condition. Only the columns to
-   be modified need be mentioned in the <literal>SET</literal> clause;
-   columns not explicitly modified retain their previous values.
-  </para>
-
-  <para>
-   By default, <command>UPDATE</command> will update rows in the
-   specified table and all its subtables. If you wish to only update
-   the specific table mentioned, you must use the <literal>ONLY</>
-   clause.
-  </para>
-
-  <para>
-   There are two ways to modify a table using information contained in
-   other tables in the database: using sub-selects, or specifying
-   additional tables in the <literal>FROM</literal> clause. Which
-   technique is more appropriate depends on the specific
-   circumstances.
-  </para>
-
-  <para>
-   The optional <literal>RETURNING</> clause causes <command>UPDATE</>
-   to compute and return value(s) based on each row actually updated.
-   Any expression using the table's columns, and/or columns of other
-   tables mentioned in <literal>FROM</literal>, can be computed.
-   The new (post-update) values of the table's columns are used.
-   The syntax of the <literal>RETURNING</> list is identical to that of the
-   output list of <command>SELECT</>.
-  </para>
-
-  <para>
-   You must have the <literal>UPDATE</literal> privilege on the table,
-   or at least on the column(s) that are listed to be updated.
-   You must also have the <literal>SELECT</literal>
-   privilege on any column whose values are read in the
-   <replaceable class="parameter">expressions</replaceable> or
-   <replaceable class="parameter">condition</replaceable>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="parameter">with_query</replaceable></term>
-    <listitem>
-     <para>
-      The <literal>WITH</literal> clause allows you to specify one or more
-      subqueries that can be referenced by name in the <command>UPDATE</>
-      query. See <xref linkend="queries-with"> and <xref linkend="sql-select">
-      for details.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">table</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of the table to update.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">alias</replaceable></term>
-    <listitem>
-     <para>
-      A substitute name for the target table. When an alias is
-      provided, it completely hides the actual name of the table.  For
-      example, given <literal>UPDATE foo AS f</>, the remainder of the
-      <command>UPDATE</command> statement must refer to this table as
-      <literal>f</> not <literal>foo</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">column</replaceable></term>
-    <listitem>
-     <para>
-      The name of a column in <replaceable
-      class="PARAMETER">table</replaceable>.
-      The column name can be qualified with a subfield name or array
-      subscript, if needed.  Do not include the table's name in the
-      specification of a target column &mdash; for example,
-      <literal>UPDATE tab SET tab.col = 1</> is invalid.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">expression</replaceable></term>
-    <listitem>
-     <para>
-      An expression to assign to the column.  The expression can use the
-      old values of this and other columns in the table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>DEFAULT</literal></term>
-    <listitem>
-     <para>
-      Set the column to its default value (which will be NULL if no
-      specific default expression has been assigned to it).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">from_list</replaceable></term>
-    <listitem>
-     <para>
-      A list of table expressions, allowing columns from other tables
-      to appear in the <literal>WHERE</> condition and the update
-      expressions. This is similar to the list of tables that can be
-      specified in the <xref linkend="sql-from"
-      endterm="sql-from-title"> of a <command>SELECT</command>
-      statement.  Note that the target table must not appear in the
-      <replaceable>from_list</>, unless you intend a self-join (in which
-      case it must appear with an alias in the <replaceable>from_list</>).
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">condition</replaceable></term>
-    <listitem>
-     <para>
-      An expression that returns a value of type <type>boolean</type>.
-      Only rows for which this expression returns <literal>true</>
-      will be updated.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">cursor_name</replaceable></term>
-    <listitem>
-&pgonly;
-     <para>
-      The name of the cursor to use in a <literal>WHERE CURRENT OF</>
-      condition.  The row to be updated is the one most recently fetched
-      from this cursor.  The cursor must be a non-grouping
-      query on the <command>UPDATE</>'s target table.
-      Note that <literal>WHERE CURRENT OF</> cannot be
-      specified together with a Boolean condition.  See
-      <xref linkend="sql-declare">
-      for more information about using cursors with
-      <literal>WHERE CURRENT OF</>.
-<!## XC>
-      <footnote>
-       <para>
-        <literal>WHERE CURRENT OF</literal> clause is not supported by
-        the current release of <productname>Postgres-XC</productname>.
-       </para>
-      </footnote>
-<!## end>
-<!## XL>
-      <footnote>
-       <para>
-        <literal>WHERE CURRENT OF</literal> clause is not supported by
-        the current release of <productname>Postgres-XL</productname>.
-       </para>
-      </footnote>
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">output_expression</replaceable></term>
-    <listitem>
-     <para>
-<!## PG>
-      An expression to be computed and returned by the <command>UPDATE</>
-      command after each row is updated.  The expression can use any
-      column names of the <replaceable class="PARAMETER">table</replaceable>
-      or table(s) listed in <literal>FROM</>.
-      Write <literal>*</> to return all columns.
-<!## end>
-<!## XC>
-      An expression to be computed and returned by the <command>UPDATE</>
-      command after each row is updated.  The expression can use any
-      column names of the <replaceable class="PARAMETER">table</replaceable>.
-      Write <literal>*</> to return all columns.
-<!## end>
-<!## XL>
-      An expression to be computed and returned by the <command>UPDATE</>
-      command after each row is updated.  The expression can use any
-      column names of the <replaceable class="PARAMETER">table</replaceable>.
-      Write <literal>*</> to return all columns.
-<!## end>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">output_name</replaceable></term>
-    <listitem>
-     <para>
-      A name to use for a returned column.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Outputs</title>
-
-  <para>
-   On successful completion, an <command>UPDATE</> command returns a command
-   tag of the form
-<screen>
-UPDATE <replaceable class="parameter">count</replaceable>
-</screen>
-   The <replaceable class="parameter">count</replaceable> is the number
-   of rows updated.  If <replaceable class="parameter">count</replaceable> is
-   0, no rows matched the <replaceable
-   class="parameter">condition</replaceable> (this is not considered
-   an error).
-  </para>
-
-  <para>
-   If the <command>UPDATE</> command contains a <literal>RETURNING</>
-   clause, the result will be similar to that of a <command>SELECT</>
-   statement containing the columns and values defined in the
-   <literal>RETURNING</> list, computed over the row(s) updated by the
-   command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-<!## PG>
-<!-- NOTICE:
-     FROM clause not supported yet
--->
-  <para>
-   When a <literal>FROM</> clause is present, what essentially happens
-   is that the target table is joined to the tables mentioned in the
-   <replaceable>from_list</replaceable>, and each output row of the join
-   represents an update operation for the target table.  When using
-   <literal>FROM</> you should ensure that the join
-   produces at most one output row for each row to be modified.  In
-   other words, a target row shouldn't join to more than one row from
-   the other table(s).  If it does, then only one of the join rows
-   will be used to update the target row, but which one will be used
-   is not readily predictable.
-  </para>
-<!## end>
-
-  <para>
-   Because of this indeterminacy, referencing other tables only within
-   sub-selects is safer, though often harder to read and slower than
-   using a join.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Change the word <literal>Drama</> to <literal>Dramatic</> in the
-   column <structfield>kind</> of the table <structname>films</structname>:
-
-<programlisting>
-UPDATE films SET kind = 'Dramatic' WHERE kind = 'Drama';
-</programlisting>
-  </para>
-
-  <para>
-   Adjust temperature entries and reset precipitation to its default
-   value in one row of the table <structname>weather</structname>:
-
-<programlisting>
-UPDATE weather SET temp_lo = temp_lo+1, temp_hi = temp_lo+15, prcp = DEFAULT
-  WHERE city = 'San Francisco' AND date = '2003-07-03';
-</programlisting>
-  </para>
-
-  <para>
-   Perform the same operation and return the updated entries:
-
-<programlisting>
-UPDATE weather SET temp_lo = temp_lo+1, temp_hi = temp_lo+15, prcp = DEFAULT
-  WHERE city = 'San Francisco' AND date = '2003-07-03'
-  RETURNING temp_lo, temp_hi, prcp;
-</programlisting>
-  </para>
-
-  <para>
-   Use the alternative column-list syntax to do the same update:
-<programlisting>
-UPDATE weather SET (temp_lo, temp_hi, prcp) = (temp_lo+1, temp_lo+15, DEFAULT)
-  WHERE city = 'San Francisco' AND date = '2003-07-03';
-</programlisting>
-  </para>
-
-<!## PG>
-<!-- NOTICE:
-     FROM clause not supported yet
--->
-  <para>
-   Increment the sales count of the salesperson who manages the
-   account for Acme Corporation, using the <literal>FROM</literal>
-   clause syntax:
-<programlisting>
-UPDATE employees SET sales_count = sales_count + 1 FROM accounts
-  WHERE accounts.name = 'Acme Corporation'
-  AND employees.id = accounts.sales_person;
-</programlisting>
-  </para>
-<!## end>
-
-<!## PG>
-<!-- NOTICE:
-     FROM clause not supported yet
--->
-  <para>
-   Perform the same operation, using a sub-select in the
-   <literal>WHERE</literal> clause:
-<programlisting>
-UPDATE employees SET sales_count = sales_count + 1 WHERE id =
-  (SELECT sales_person FROM accounts WHERE name = 'Acme Corporation');
-</programlisting>
-  </para>
-<!## end>
-
-  <para>
-   Attempt to insert a new stock item along with the quantity of stock. If
-   the item already exists, instead update the stock count of the existing
-   item. To do this without failing the entire transaction, use savepoints:
-<programlisting>
-BEGIN;
--- other operations
-SAVEPOINT sp1;
-INSERT INTO wines VALUES('Chateau Lafite 2003', '24');
--- Assume the above fails because of a unique key violation,
--- so now we issue these commands:
-ROLLBACK TO sp1;
-UPDATE wines SET stock = stock + 24 WHERE winename = 'Chateau Lafite 2003';
--- continue with other operations, and eventually
-COMMIT;
-</programlisting>
-  </para>
-
-<!## PG>
-  <para>
-   Change the <structfield>kind</> column of the table
-   <structname>films</structname> in the row on which the cursor
-   <literal>c_films</> is currently positioned:
-<programlisting>
-UPDATE films SET kind = 'Dramatic' WHERE CURRENT OF c_films;
-</programlisting>
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   This command conforms to the <acronym>SQL</acronym> standard, except
-   that the <literal>FROM</literal> and <literal>RETURNING</> clauses
-   are <productname>PostgreSQL</productname> extensions, as is the ability
-   to use <literal>WITH</> with <command>UPDATE</>.
-  </para>
-
-  <para>
-   According to the standard, the column-list syntax should allow a list
-   of columns to be assigned from a single row-valued expression, such
-   as a sub-select:
-<programlisting>
-UPDATE accounts SET (contact_last_name, contact_first_name) =
-    (SELECT last_name, first_name FROM salesmen
-     WHERE salesmen.id = accounts.sales_id);
-</programlisting>
-   This is not currently implemented &mdash; the source must be a list
-   of independent expressions.
-  </para>
-
-<!## PG>
-<!-- NOTICE:
-     FROM clause not supported yet
--->
-  <para>
-   Some other database systems offer a <literal>FROM</> option in which
-   the target table is supposed to be listed again within <literal>FROM</>.
-   That is not how <productname>PostgreSQL</productname> interprets
-   <literal>FROM</>.  Be careful when porting applications that use this
-   extension.
-  </para>
-<!## end>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/vacuum.sgmlin b/doc-xc/src/sgml/ref/vacuum.sgmlin
deleted file mode 100644
index 6414e0eae0..0000000000
--- a/doc-xc/src/sgml/ref/vacuum.sgmlin
+++ /dev/null
@@ -1,319 +0,0 @@
-<!--
-doc/src/sgml/ref/vacuum.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-VACUUM">
- <refmeta>
-  <refentrytitle>VACUUM</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>VACUUM</refname>
-  <refpurpose>garbage-collect and optionally analyze a database</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-vacuum">
-  <primary>VACUUM</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-VACUUM [ ( { FULL | FREEZE | VERBOSE | ANALYZE } [, ...] ) ] [ <replaceable class="PARAMETER">table</replaceable> [ (<replaceable class="PARAMETER">column</replaceable> [, ...] ) ] ]
-VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> ]
-VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">table</replaceable> [ (<replaceable class="PARAMETER">column</replaceable> [, ...] ) ] ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>VACUUM</command> reclaims storage occupied by dead tuples.
-<!## PG>
-   In normal <productname>PostgreSQL</productname> operation, tuples that
-<!## end>
-<!## XC>
-   In normal <productname>Postgres-XC</productname> operation, tuples that
-<!## end>
-<!## XL>
-   In normal <productname>Postgres-XL</productname> operation, tuples that
-<!## end>
-   are deleted or obsoleted by an update are not physically removed from
-   their table; they remain present until a <command>VACUUM</command> is
-   done.  Therefore it's necessary to do <command>VACUUM</command>
-   periodically, especially on frequently-updated tables.
-  </para>
-
-  <para>
-   With no parameter, <command>VACUUM</command> processes every table in the
-   current database that the current user has permission to vacuum.
-   With a parameter, <command>VACUUM</command> processes only that table.
-  </para>
-
-  <para>
-   <command>VACUUM ANALYZE</command> performs a <command>VACUUM</command>
-   and then an <command>ANALYZE</command> for each selected table.  This
-   is a handy combination form for routine maintenance scripts.  See
-   <xref linkend="sql-analyze">
-   for more details about its processing.
-  </para>
-
-  <para>
-   Plain <command>VACUUM</command> (without <literal>FULL</>) simply reclaims
-   space and makes it
-   available for re-use.  This form of the command can operate in parallel
-   with normal reading and writing of the table, as an exclusive lock
-   is not obtained.  However, extra space is not returned to the operating
-   system (in most cases); it's just kept available for re-use within the
-   same table.  <command>VACUUM FULL</command> rewrites the entire contents
-   of the table into a new disk file with no extra space, allowing unused
-   space to be returned to the operating system.  This form is much slower and
-   requires an exclusive lock on each table while it is being processed.
-  </para>
-
-  <para>
-   When the option list is surrounded by parentheses, the options can be
-   written in any order.  Without parentheses, options must be specified
-   in exactly the order shown above.
-   The parenthesized syntax was added in
-   <productname>PostgreSQL</productname> 9.0;  the unparenthesized
-   syntax is deprecated.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   In <productname>Postgres-XC</>, <command>VACUUM</> will be performed
-   on all the Datanodes as well.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   In <productname>Postgres-XL</>, <command>VACUUM</> will be performed
-   on all the Datanodes as well.
-  </para>
-<!## end>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-&common;
-  <variablelist>
-   <varlistentry>
-    <term><literal>FULL</literal></term>
-    <listitem>
-     <para>
-      Selects <quote>full</quote> vacuum, which can reclaim more
-      space, but takes much longer and exclusively locks the table.
-      This method also requires extra disk space, since it writes a
-      new copy of the table and doesn't release the old copy until
-      the operation is complete.  Usually this should only be used when a
-      significant amount of space needs to be reclaimed from within the table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>FREEZE</literal></term>
-    <listitem>
-     <para>
-      Selects aggressive <quote>freezing</quote> of tuples.
-      Specifying <literal>FREEZE</literal> is equivalent to performing
-      <command>VACUUM</command> with the
-      <xref linkend="guc-vacuum-freeze-min-age"> parameter
-      set to zero.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>VERBOSE</literal></term>
-    <listitem>
-     <para>
-      Prints a detailed vacuum activity report for each table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ANALYZE</literal></term>
-    <listitem>
-     <para>
-      Updates statistics used by the planner to determine the most
-      efficient way to execute a query.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">table</replaceable></term>
-    <listitem>
-     <para>
-      The name (optionally schema-qualified) of a specific table to
-      vacuum. Defaults to all tables in the current database.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="PARAMETER">column</replaceable></term>
-    <listitem>
-     <para>
-      The name of a specific column to analyze. Defaults to all columns.
-      If a column list is specified, <literal>ANALYZE</> is implied.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Outputs</title>
-
-   <para>
-    When <literal>VERBOSE</> is specified, <command>VACUUM</> emits
-    progress messages to indicate which table is currently being
-    processed.  Various statistics about the tables are printed as well.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-   <para>
-    To vacuum a table, one must ordinarily be the table's owner or a
-    superuser.  However, database owners are allowed to
-    vacuum all tables in their databases, except shared catalogs.
-    (The restriction for shared catalogs means that a true database-wide
-    <command>VACUUM</> can only be performed by a superuser.)
-    <command>VACUUM</> will skip over any tables that the calling user
-    does not have permission to vacuum.
-   </para>
-
-   <para>
-    <command>VACUUM</> cannot be executed inside a transaction block.
-   </para>
-
-   <para>
-    For tables with <acronym>GIN</> indexes, <command>VACUUM</command> (in
-    any form) also completes any pending index insertions, by moving pending
-    index entries to the appropriate places in the main <acronym>GIN</> index
-    structure.  See <xref linkend="gin-fast-update"> for details.
-   </para>
-
-   <para>
-    We recommend that active production databases be
-    vacuumed frequently (at least nightly), in order to
-    remove dead rows. After adding or deleting a large number
-    of rows, it might be a good idea to issue a <command>VACUUM
-    ANALYZE</command> command for the affected table. This will update the
-    system catalogs with
-    the results of all recent changes, and allow the
-<!## PG>
-    <productname>PostgreSQL</productname> query planner to make better
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> query planner to make better
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> query planner to make better
-<!## end>
-    choices in planning queries.
-   </para>
-
-   <para>
-    The <option>FULL</option> option is not recommended for routine use,
-    but might be useful in special cases.  An example is when you have deleted
-    or updated most of the rows in a table and would like the table to
-    physically shrink to occupy less disk space and allow faster table
-    scans. <command>VACUUM FULL</command> will usually shrink the table
-    more than a plain <command>VACUUM</command> would.
-   </para>
-
-   <para>
-    <command>VACUUM</command> causes a substantial increase in I/O traffic,
-    which might cause poor performance for other active sessions.  Therefore,
-    it is sometimes advisable to use the cost-based vacuum delay feature.
-    See <xref linkend="runtime-config-resource-vacuum-cost"> for details.
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> includes an <quote>autovacuum</>
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> includes an <quote>autovacuum</>
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> includes an <quote>autovacuum</>
-<!## end>
-    facility which can automate routine vacuum maintenance.  For more
-    information about automatic and manual vacuuming, see
-    <xref linkend="routine-vacuuming">.
-   </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   The following is an example from running <command>VACUUM</command> on a
-   table in the regression database:
-
-<programlisting>
-regression=# VACUUM (VERBOSE, ANALYZE) onek;
-INFO:  vacuuming "public.onek"
-INFO:  index "onek_unique1" now contains 1000 tuples in 14 pages
-DETAIL:  3000 index tuples were removed.
-0 index pages have been deleted, 0 are currently reusable.
-CPU 0.01s/0.08u sec elapsed 0.18 sec.
-INFO:  index "onek_unique2" now contains 1000 tuples in 16 pages
-DETAIL:  3000 index tuples were removed.
-0 index pages have been deleted, 0 are currently reusable.
-CPU 0.00s/0.07u sec elapsed 0.23 sec.
-INFO:  index "onek_hundred" now contains 1000 tuples in 13 pages
-DETAIL:  3000 index tuples were removed.
-0 index pages have been deleted, 0 are currently reusable.
-CPU 0.01s/0.08u sec elapsed 0.17 sec.
-INFO:  index "onek_stringu1" now contains 1000 tuples in 48 pages
-DETAIL:  3000 index tuples were removed.
-0 index pages have been deleted, 0 are currently reusable.
-CPU 0.01s/0.09u sec elapsed 0.59 sec.
-INFO:  "onek": removed 3000 tuples in 108 pages
-DETAIL:  CPU 0.01s/0.06u sec elapsed 0.07 sec.
-INFO:  "onek": found 3000 removable, 1000 nonremovable tuples in 143 pages
-DETAIL:  0 dead tuples cannot be removed yet.
-There were 0 unused item pointers.
-0 pages are entirely empty.
-CPU 0.07s/0.39u sec elapsed 1.56 sec.
-INFO:  analyzing "public.onek"
-INFO:  "onek": 36 pages, 1000 rows sampled, 1000 estimated total rows
-VACUUM
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   There is no <command>VACUUM</command> statement in the SQL standard.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-vacuumdb"></member>
-   <member><xref linkend="runtime-config-resource-vacuum-cost"></member>
-   <member><xref linkend="autovacuum"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/ref/vacuumdb.sgmlin b/doc-xc/src/sgml/ref/vacuumdb.sgmlin
deleted file mode 100644
index 30c1fd5937..0000000000
--- a/doc-xc/src/sgml/ref/vacuumdb.sgmlin
+++ /dev/null
@@ -1,430 +0,0 @@
-<!--
-doc/src/sgml/ref/vacuumdb.sgml
-PostgreSQL documentation
--->
-
-<refentry id="APP-VACUUMDB">
- <refmeta>
-  <refentrytitle><application>vacuumdb</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname id="vacuumdb">vacuumdb</refname>
-  <refpurpose>garbage-collect and analyze a <productname>PostgreSQL</productname> database</refpurpose>
- </refnamediv>
-
- <indexterm zone="app-vacuumdb">
-  <primary>vacuumdb</primary>
- </indexterm>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>vacuumdb</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <group><arg>--full</arg><arg>-f</arg></group>
-   <group><arg>--freeze</arg><arg>-F</arg></group>
-   <group><arg>--verbose</arg><arg>-v</arg></group>
-   <group><arg>--analyze</arg><arg>-z</arg></group>
-   <group><arg>--analyze-only</arg><arg>-Z</arg></group>
-   <arg>--table | -t <replaceable>table</replaceable>
-    <arg>( <replaceable class="parameter">column</replaceable> [,...] )</arg>
-   </arg>
-   <arg><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
-
-  <cmdsynopsis>
-   <command>vacuumdb</command>
-   <arg rep="repeat"><replaceable>connection-option</replaceable></arg>
-   <group><arg>--full</arg><arg>-f</arg></group>
-   <group><arg>--freeze</arg><arg>-F</arg></group>
-   <group><arg>--verbose</arg><arg>-v</arg></group>
-   <group><arg>--analyze</arg><arg>-z</arg></group>
-   <group><arg>--analyze-only</arg><arg>-Z</arg></group>
-   <group><arg>--all</arg><arg>-a</arg></group>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <application>vacuumdb</application> is a utility for cleaning a
-<!## PG>
-   <productname>PostgreSQL</productname> database.
-   <application>vacuumdb</application> will also generate internal statistics
-   used by the <productname>PostgreSQL</productname> query optimizer.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> database.
-   <application>vacuumdb</application> will also generate internal statistics
-   used by the <productname>Postgres-XC</productname> query optimizer.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> database.
-   <application>vacuumdb</application> will also generate internal statistics
-   used by the <productname>Postgres-XL</productname> query optimizer.
-<!## end>
-  </para>
-
-  <para>
-   <application>vacuumdb</application> is a wrapper around the SQL
-   command <xref linkend="SQL-VACUUM">.
-   There is no effective difference between vacuuming and analyzing
-   databases via this utility and via other methods for accessing the
-   server.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   In <productname>Postgres-XC</>, <command>VACUUM</> will be
-   performed in all the Datanodes as well.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   In <productname>Postgres-XL</>, <command>VACUUM</> will be
-   performed in all the Datanodes as well.
-  </para>
-<!## end>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-&common;
-   <para>
-    <application>vacuumdb</application> accepts the following command-line arguments:
-    <variablelist>
-     <varlistentry>
-      <term><option>-a</option></term>
-      <term><option>--all</option></term>
-      <listitem>
-       <para>
-        Vacuum all databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option><optional>-d</> <replaceable class="parameter">dbname</replaceable></option></term>
-      <term><option><optional>--dbname=</><replaceable class="parameter">dbname</replaceable></option></term>
-      <listitem>
-       <para>
-        Specifies the name of the database to be cleaned or analyzed.
-        If this is not specified and <option>-a</option> (or
-        <option>--all</option>) is not used, the database name is read
-        from the environment variable <envar>PGDATABASE</envar>.  If
-        that is not set, the user name specified for the connection is
-        used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-e</></term>
-      <term><option>--echo</></term>
-      <listitem>
-       <para>
-        Echo the commands that <application>vacuumdb</application> generates
-        and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-f</option></term>
-      <term><option>--full</option></term>
-      <listitem>
-       <para>
-        Perform <quote>full</quote> vacuuming.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-F</option></term>
-      <term><option>--freeze</option></term>
-      <listitem>
-       <para>
-        Aggressively <quote>freeze</quote> tuples.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-q</></term>
-      <term><option>--quiet</></term>
-      <listitem>
-       <para>
-        Do not display progress messages.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-t <replaceable class="parameter">table</replaceable> [ (<replaceable class="parameter">column</replaceable> [,...]) ]</option></term>
-      <term><option>--table=<replaceable class="parameter">table</replaceable> [ (<replaceable class="parameter">column</replaceable> [,...]) ]</option></term>
-      <listitem>
-       <para>
-        Clean or analyze <replaceable class="parameter">table</replaceable> only.
-        Column names can be specified only in conjunction with
-        the <option>--analyze</option> or <option>--analyze-only</option> options.
-       </para>
-       <tip>
-        <para>
-         If you specify columns, you probably have to escape the parentheses
-         from the shell.  (See examples below.)
-        </para>
-       </tip>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-v</option></term>
-      <term><option>--verbose</option></term>
-      <listitem>
-       <para>
-        Print detailed information during processing.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-V</></term>
-       <term><option>--version</></term>
-       <listitem>
-       <para>
-       Print the <application>vacuumdb</application> version and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-z</option></term>
-      <term><option>--analyze</option></term>
-      <listitem>
-       <para>
-        Also calculate statistics for use by the optimizer.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-Z</option></term>
-      <term><option>--analyze-only</option></term>
-      <listitem>
-       <para>
-        Only calculate statistics for use by the optimizer (no vacuum).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-       <term><option>-?</></term>
-       <term><option>--help</></term>
-       <listitem>
-       <para>
-       Show help about <application>vacuumdb</application> command line
-       arguments, and exit.
-       </para>
-       </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    <application>vacuumdb</application> also accepts
-    the following command-line arguments for connection parameters:
-    <variablelist>
-     <varlistentry>
-      <term><option>-h <replaceable class="parameter">host</replaceable></></term>
-      <term><option>--host=<replaceable class="parameter">host</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the host name of the machine on which the server
-        is running.  If the value begins with a slash, it is used
-        as the directory for the Unix domain socket.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p <replaceable class="parameter">port</replaceable></></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></></term>
-      <listitem>
-       <para>
-        Specifies the TCP port or local Unix domain socket file
-        extension on which the server
-        is listening for connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable class="parameter">username</replaceable></></term>
-      <term><option>--username=<replaceable class="parameter">username</replaceable></></term>
-      <listitem>
-       <para>
-        User name to connect as.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-w</></term>
-      <term><option>--no-password</></term>
-      <listitem>
-       <para>
-        Never issue a password prompt.  If the server requires
-        password authentication and a password is not available by
-        other means such as a <filename>.pgpass</filename> file, the
-        connection attempt will fail.  This option can be useful in
-        batch jobs and scripts where no user is present to enter a
-        password.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</></term>
-      <term><option>--password</></term>
-      <listitem>
-       <para>
-        Force <application>vacuumdb</application> to prompt for a
-        password before connecting to a database.
-       </para>
-
-       <para>
-        This option is never essential, since
-        <application>vacuumdb</application> will automatically prompt
-        for a password if the server demands password authentication.
-        However, <application>vacuumdb</application> will waste a
-        connection attempt finding out that the server wants a password.
-        In some cases it is worth typing <option>-W</> to avoid the extra
-        connection attempt.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Environment</title>
-&common;
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATABASE</envar></term>
-    <term><envar>PGHOST</envar></term>
-    <term><envar>PGPORT</envar></term>
-    <term><envar>PGUSER</envar></term>
-
-    <listitem>
-     <para>
-      Default connection parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-  <para>
-<!## PG>
-   This utility, like most other <productname>PostgreSQL</> utilities,
-<!## end>
-<!## XC>
-   This utility, like most other <productname>Postgres-XC</> utilities,
-<!## end>
-<!## XL>
-   This utility, like most other <productname>Postgres-XL</> utilities,
-<!## end>
-   also uses the environment variables supported by <application>libpq</>
-   (see <xref linkend="libpq-envars">).
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Diagnostics</title>
-&common;
-  <para>
-   In case of difficulty, see <xref linkend="SQL-VACUUM">
-   and <xref linkend="APP-PSQL"> for
-   discussions of potential problems and error messages.
-   The database server must be running at the
-   targeted host.  Also, any default connection settings and environment
-   variables used by the <application>libpq</application> front-end
-   library will apply.
-  </para>
-
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <application>vacuumdb</application> might need to connect several
-<!## PG>
-   times to the <productname>PostgreSQL</productname> server, asking
-<!## end>
-<!## XC>
-   times to the <productname>Postgres-XC</productname> server, asking
-<!## end>
-<!## XL>
-   times to the <productname>Postgres-XL</productname> server, asking
-<!## end>
-   for a password each time. It is convenient to have a
-   <filename>~/.pgpass</> file in such cases. See <xref
-   linkend="libpq-pgpass"> for more information.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-   <para>
-    To clean the database <literal>test</literal>:
-<screen>
-<prompt>$ </prompt><userinput>vacuumdb test</userinput>
-</screen>
-   </para>
-
-   <para>
-    To clean and analyze for the optimizer a database named
-    <literal>bigdb</literal>:
-<screen>
-<prompt>$ </prompt><userinput>vacuumdb --analyze bigdb</userinput>
-</screen>
-   </para>
-
-   <para>
-    To clean a single table
-    <literal>foo</literal> in a database named
-    <literal>xyzzy</literal>, and analyze a single column
-    <literal>bar</literal> of the table for the optimizer:
-<screen>
-<prompt>$ </prompt><userinput>vacuumdb --analyze --verbose --table 'foo(bar)' xyzzy</userinput>
-</screen>
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-vacuum"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
diff --git a/doc-xc/src/sgml/ref/values.sgmlin b/doc-xc/src/sgml/ref/values.sgmlin
deleted file mode 100644
index 45bd5e2c5b..0000000000
--- a/doc-xc/src/sgml/ref/values.sgmlin
+++ /dev/null
@@ -1,267 +0,0 @@
-<!--
-doc/src/sgml/ref/values.sgml
-PostgreSQL documentation
--->
-
-<refentry id="SQL-VALUES">
- <refmeta>
-  <refentrytitle>VALUES</refentrytitle>
-  <manvolnum>7</manvolnum>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>VALUES</refname>
-  <refpurpose>compute a set of rows</refpurpose>
- </refnamediv>
-
- <indexterm zone="sql-values">
-  <primary>VALUES</primary>
- </indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-VALUES ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) [, ...]
-    [ ORDER BY <replaceable class="parameter">sort_expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [, ...] ]
-    [ LIMIT { <replaceable class="parameter">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="parameter">start</replaceable> [ ROW | ROWS ] ]
-    [ FETCH { FIRST | NEXT } [ <replaceable class="parameter">count</replaceable> ] { ROW | ROWS } ONLY ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&common;
-
-  <para>
-   <command>VALUES</command> computes a row value or set of row values
-   specified by value expressions.  It is most commonly used to generate
-   a <quote>constant table</> within a larger command, but it can be
-   used on its own.
-  </para>
-
-  <para>
-   When more than one row is specified, all the rows must have the same
-   number of elements.  The data types of the resulting table's columns are
-   determined by combining the explicit or inferred types of the expressions
-   appearing in that column, using the same rules as for <literal>UNION</>
-   (see <xref linkend="typeconv-union-case">).
-  </para>
-
-  <para>
-   Within larger commands, <command>VALUES</> is syntactically allowed
-   anywhere that <command>SELECT</> is.  Because it is treated like a
-   <command>SELECT</> by the grammar, it is possible to use
-   the <literal>ORDER BY</>, <literal>LIMIT</> (or
-   equivalently <literal>FETCH FIRST</literal>),
-   and <literal>OFFSET</> clauses with a
-   <command>VALUES</> command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-&common;
-  <variablelist>
-   <varlistentry>
-    <term><replaceable class="PARAMETER">expression</replaceable></term>
-    <listitem>
-     <para>
-      A constant or expression to compute and insert at the indicated place
-      in the resulting table (set of rows).  In a <command>VALUES</> list
-      appearing at the top level of an <command>INSERT</>, an
-      <replaceable class="PARAMETER">expression</replaceable> can be replaced
-      by <literal>DEFAULT</literal> to indicate that the destination column's
-      default value should be inserted.  <literal>DEFAULT</literal> cannot
-      be used when <command>VALUES</> appears in other contexts.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">sort_expression</replaceable></term>
-    <listitem>
-     <para>
-      An expression or integer constant indicating how to sort the result
-      rows.  This expression can refer to the columns of the
-      <command>VALUES</> result as <literal>column1</>, <literal>column2</>,
-      etc.  For more details see
-      <xref linkend="sql-orderby" endterm="sql-orderby-title">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">operator</replaceable></term>
-    <listitem>
-     <para>
-      A sorting operator.  For details see
-      <xref linkend="sql-orderby" endterm="sql-orderby-title">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">count</replaceable></term>
-    <listitem>
-     <para>
-      The maximum number of rows to return.  For details see
-      <xref linkend="sql-limit" endterm="sql-limit-title">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable class="parameter">start</replaceable></term>
-    <listitem>
-     <para>
-      The number of rows to skip before starting to return rows.
-      For details see
-      <xref linkend="sql-limit" endterm="sql-limit-title">.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-&common;
-  <para>
-   <command>VALUES</> lists with very large numbers of rows should be avoided,
-   as you might encounter out-of-memory failures or poor performance.
-   <command>VALUES</> appearing within <command>INSERT</> is a special case
-   (because the desired column types are known from the <command>INSERT</>'s
-   target table, and need not be inferred by scanning the <command>VALUES</>
-   list), so it can handle larger lists than are practical in other contexts.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-&common;
-  <para>
-   A bare <command>VALUES</> command:
-
-<programlisting>
-VALUES (1, 'one'), (2, 'two'), (3, 'three');
-</programlisting>
-
-   This will return a table of two columns and three rows.  It's effectively
-   equivalent to:
-
-<programlisting>
-SELECT 1 AS column1, 'one' AS column2
-UNION ALL
-SELECT 2, 'two'
-UNION ALL
-SELECT 3, 'three';
-</programlisting>
-
-  </para>
-
-  <para>
-   More usually, <command>VALUES</> is used within a larger SQL command.
-   The most common use is in <command>INSERT</>:
-
-<programlisting>
-INSERT INTO films (code, title, did, date_prod, kind)
-    VALUES ('T_601', 'Yojimbo', 106, '1961-06-16', 'Drama');
-</programlisting>
-  </para>
-
-  <para>
-   In the context of <command>INSERT</>, entries of a <command>VALUES</> list
-   can be <literal>DEFAULT</literal> to indicate that the column default
-   should be used here instead of specifying a value:
-
-<programlisting>
-INSERT INTO films VALUES
-    ('UA502', 'Bananas', 105, DEFAULT, 'Comedy', '82 minutes'),
-    ('T_601', 'Yojimbo', 106, DEFAULT, 'Drama', DEFAULT);
-</programlisting>
-  </para>
-
-  <para>
-   <command>VALUES</> can also be used where a sub-<command>SELECT</> might
-   be written, for example in a <literal>FROM</> clause:
-
-<programlisting>
-SELECT f.*
-  FROM films f, (VALUES('MGM', 'Horror'), ('UA', 'Sci-Fi')) AS t (studio, kind)
-  WHERE f.studio = t.studio AND f.kind = t.kind;
-
-UPDATE employees SET salary = salary * v.increase
-  FROM (VALUES(1, 200000, 1.2), (2, 400000, 1.4)) AS v (depno, target, increase)
-  WHERE employees.depno = v.depno AND employees.sales &gt;= v.target;
-</programlisting>
-
-   Note that an <literal>AS</> clause is required when <command>VALUES</>
-   is used in a <literal>FROM</> clause, just as is true for
-   <command>SELECT</>.  It is not required that the <literal>AS</> clause
-   specify names for all the columns, but it's good practice to do so.
-   (The default column names for <command>VALUES</> are <literal>column1</>,
-<!## PG>
-   <literal>column2</>, etc in <productname>PostgreSQL</productname>, but
-<!## end>
-<!## XC>
-   <literal>column2</>, etc in <productname>Postgres-XC</productname>, but
-<!## end>
-<!## XL>
-   <literal>column2</>, etc in <productname>Postgres-XL</productname>, but
-<!## end>
-   these names might be different in other database systems.)
-  </para>
-
-  <para>
-   When <command>VALUES</> is used in <command>INSERT</>, the values are all
-   automatically coerced to the data type of the corresponding destination
-   column.  When it's used in other contexts, it might be necessary to specify
-   the correct data type.  If the entries are all quoted literal constants,
-   coercing the first is sufficient to determine the assumed type for all:
-
-<programlisting>
-SELECT * FROM machines
-WHERE ip_address IN (VALUES('192.168.0.1'::inet), ('192.168.0.10'), ('192.168.1.43'));
-</programlisting>
-  </para>
-
-  <tip>
-   <para>
-    For simple <literal>IN</> tests, it's better to rely on the
-    list-of-scalars form of <literal>IN</> than to write a <command>VALUES</>
-    query as shown above.  The list of scalars method requires less writing
-    and is often more efficient.
-   </para>
-  </tip>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-&common
-  <para>
-   <command>VALUES</command> conforms to the SQL standard.
-   <literal>LIMIT</literal> and <literal>OFFSET</literal> are
-<!## PG>
-   <productname>PostgreSQL</productname> extensions; see also
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> extensions; see also
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> extensions; see also
-<!## end>
-   under <xref linkend="sql-select">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-insert"></member>
-   <member><xref linkend="sql-select"></member>
-  </simplelist>
- </refsect1>
-</refentry>
diff --git a/doc-xc/src/sgml/reference.sgmlin b/doc-xc/src/sgml/reference.sgmlin
deleted file mode 100644
index 535bb65b76..0000000000
--- a/doc-xc/src/sgml/reference.sgmlin
+++ /dev/null
@@ -1,360 +0,0 @@
-<!-- doc/src/sgml/reference.sgml -->
-
-<part id="reference">
- <title>Reference</title>
-
- <partintro>
-
-&common;
-
-  <para>
-   The entries in this Reference are meant to provide in reasonable
-   length an authoritative, complete, and formal summary about their
-   respective subjects.  More information about the use of
-<!## PG>
-   <productname>PostgreSQL</productname>, in narrative, tutorial, or
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>, in narrative, tutorial, or
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>, in narrative, tutorial, or
-<!## end>
-   example form, can be found in other parts of this book.  See the
-   cross-references listed on each reference page.
-  </para>
-
-  <para>
-   The reference entries are also available as traditional
-   <quote>man</quote> pages.
-  </para>
- </partintro>
-
- <reference id="sql-commands">
-  <title>SQL Commands</title>
-
-  <partintro>
-   <para>
-    This part contains reference information for the
-    <acronym>SQL</acronym> commands supported by
-<!## PG>
-    <productname>PostgreSQL</productname>.  By <quote>SQL</quote> the
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>.  By <quote>SQL</quote> the
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>.  By <quote>SQL</quote> the
-<!## end>
-    language in general is meant; information about the standards
-    conformance and compatibility of each command can be found on the
-    respective reference page.
-   </para>
-  </partintro>
-
-   &abort;
-   &alterAggregate;
-   &alterCollation;
-   &alterConversion;
-   &alterDatabase;
-   &alterDefaultPrivileges;
-   &alterDomain;
-   &alterExtension;
-   &alterForeignDataWrapper;
-   &alterForeignTable;
-   &alterFunction;
-   &alterGroup;
-   &alterIndex;
-   &alterLanguage;
-   &alterLargeObject;
-<!## XC>
-   &alterNode;
-<!## end>
-<!## XL>
-   &alterNode;
-<!## end>
-   &alterOperator;
-   &alterOperatorClass;
-   &alterOperatorFamily;
-   &alterRole;
-   &alterSchema;
-   &alterSequence;
-   &alterServer;
-   &alterTable;
-   &alterTableSpace;
-   &alterTSConfig;
-   &alterTSDictionary;
-   &alterTSParser;
-   &alterTSTemplate;
-   &alterTrigger;
-   &alterType;
-   &alterUser;
-   &alterUserMapping;
-   &alterView;
-   &analyze;
-   &begin;
-   &checkpoint;
-<!## XC>
-   &cleanConnection;
-<!## end>
-<!## XL>
-   &cleanConnection;
-<!## end>
-   &close;
-   &cluster;
-   &commentOn;
-   &commit;
-   &commitPrepared;
-   &copyTable;
-   &createAggregate;
-<!## XC>
-   &createBarrier;
-<!## end>
-<!## XL>
-   &createBarrier;
-<!## end>
-   &createCast;
-   &createCollation;
-   &createConversion;
-   &createDatabase;
-   &createDomain;
-   &createExtension;
-   &createForeignDataWrapper;
-   &createForeignTable;
-   &createFunction;
-   &createGroup;
-   &createIndex;
-   &createLanguage;
-<!## XC>
-   &createNode;
-   &createNodeGroup;
-<!## end>
-<!## XL>
-   &createNode;
-   &createNodeGroup;
-<!## end>
-   &createOperator;
-   &createOperatorClass;
-   &createOperatorFamily;
-   &createRole;
-   &createRule;
-   &createSchema;
-   &createSequence;
-   &createServer;
-   &createTable;
-   &createTableAs;
-   &createTableSpace;
-   &createTSConfig;
-   &createTSDictionary;
-   &createTSParser;
-   &createTSTemplate;
-   &createTrigger;
-   &createType;
-   &createUser;
-   &createUserMapping;
-   &createView;
-   &deallocate;
-   &declare;
-   &delete;
-   &discard;
-   &do;
-   &dropAggregate;
-   &dropCast;
-   &dropCollation;
-   &dropConversion;
-   &dropDatabase;
-   &dropDomain;
-   &dropExtension;
-   &dropForeignDataWrapper;
-   &dropForeignTable;
-   &dropFunction;
-   &dropGroup;
-   &dropIndex;
-   &dropLanguage;
-<!## XC>
-   &dropNode;
-   &dropNodeGroup;
-<!## end>
-<!## XL>
-   &dropNode;
-   &dropNodeGroup;
-<!## end>
-   &dropOperator;
-   &dropOperatorClass;
-   &dropOperatorFamily;
-   &dropOwned;
-   &dropRole;
-   &dropRule;
-   &dropSchema;
-   &dropSequence;
-   &dropServer;
-   &dropTable;
-   &dropTableSpace;
-   &dropTSConfig;
-   &dropTSDictionary;
-   &dropTSParser;
-   &dropTSTemplate;
-   &dropTrigger;
-   &dropType;
-   &dropUser;
-   &dropUserMapping;
-   &dropView;
-   &end;
-   &execute;
-<!## XC>
-   &executeDirect;
-<!## end>
-<!## XL>
-   &executeDirect;
-<!## end>
-   &explain;
-   &fetch;
-   &grant;
-   &insert;
-   &listen;
-   &load;
-   &lock;
-   &move;
-   &notify;
-<!## XL>
-   &pauseCluster;
-<!## end>
-   &prepare;
-   &prepareTransaction;
-   &reassignOwned;
-   &reindex;
-   &releaseSavepoint;
-   &reset;
-   &revoke;
-   &rollback;
-   &rollbackPrepared;
-   &rollbackTo;
-   &savepoint;
-   &securityLabel;
-   &select;
-   &selectInto;
-   &set;
-   &setConstraints;
-   &setRole;
-   &setSessionAuth;
-   &setTransaction;
-   &show;
-   &startTransaction;
-   &truncate;
-   &unlisten;
-<!## XL>
-   &unpauseCluster;
-<!## end>
-   &update;
-   &vacuum;
-   &values;
-
- </reference>
-
- <reference id="reference-client">
-<!## PG>
-  <title>PostgreSQL Client Applications</title>
-<!## end>
-<!## XC>
-  <title>Postgres-XC Client Applications</title>
-<!## end>
-<!## XL>
-  <title>Postgres-XL Client Applications</title>
-<!## end>
-
-  <partintro>
-   <para>
-    This part contains reference information for
-<!## PG>
-    <productname>PostgreSQL</productname> client applications and
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> client applications and
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> client applications and
-<!## end>
-    utilities.  Not all of these commands are of general utility; some
-    might require special privileges.  The common feature of these
-    applications is that they can be run on any host, independent of
-    where the database server resides.
-   </para>
-  </partintro>
-
-   &clusterdb;
-   &createdb;
-   &createlang;
-   &createuser;
-   &dropdb;
-   &droplang;
-   &dropuser;
-   &ecpgRef;
-   &pgBasebackup;
-   &pgConfig;
-   &pgDump;
-   &pgDumpall;
-   &pgRestore;
-   &psqlRef;
-   &reindexdb;
-   &vacuumdb;
-
- </reference>
-
- <reference id="reference-server">
-<!## PG>
-  <title>PostgreSQL Server Applications</title>
-<!## end>
-<!## XC>
-  <title>Postgres-XC Server Applications</title>
-<!## end>
-<!## XL>
-  <title>Postgres-XL Server Applications</title>
-<!## end>
-
-  <partintro>
-   <para>
-    This part contains reference information for
-<!## PG>
-    <productname>PostgreSQL</productname> server applications and
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> server applications and
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> server applications and
-<!## end>
-    support utilities.  These commands can only be run usefully on the
-    host where the database server resides.  Other utility programs
-    are listed in <xref linkend="reference-client">.
-   </para>
-  </partintro>
-
-<!## XC>
-   &gtm;
-   &gtmPxy;
-   &gtmCtl;
-<!## end>
-<!## XL>
-   &gtm;
-   &gtmPxy;
-   &gtmCtl;
-<!## end>
-   &initdb;
-<!## XC>
-   &initgtm;
-<!## end>
-<!## XL>
-   &initgtm;
-<!## end>
-   &pgControldata;
-   &pgCtl;
-   &pgResetxlog;
-<!## notYet>
-   &pgxcClean;
-<!## end>
-   &postgres;
-   &postmaster;
-
- </reference>
-
-</part>
diff --git a/doc-xc/src/sgml/regress.sgmlin b/doc-xc/src/sgml/regress.sgmlin
deleted file mode 100644
index 4c5964c66a..0000000000
--- a/doc-xc/src/sgml/regress.sgmlin
+++ /dev/null
@@ -1,704 +0,0 @@
-<!-- doc/src/sgml/regress.sgml -->
-
- <chapter id="regress">
-  <title>Regression Tests</title>
-
-  <indexterm zone="regress">
-   <primary>regression tests</primary>
-  </indexterm>
-
-  <indexterm zone="regress">
-   <primary>test</primary>
-  </indexterm>
-<!## XC>
-&xconly;
-  <para>
-   Current version of <productname>Postgres-XC</productname> doesn't
-   support the regression test to run after building but before
-   installation.  You can use each test manually but it is left to
-   users.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Current version of <productname>Postgres-XL</productname> doesn't
-   support the regression test to run after building but before
-   installation.  You can use each test manually but it is left to
-   users.
-  </para>
-<!## end>
-
-<!## PG>
-  <para>
-   The regression tests are a comprehensive set of tests for the SQL
-   implementation in <productname>PostgreSQL</productname>.  They test
-   standard SQL operations as well as the extended capabilities of
-   <productname>PostgreSQL</productname>.
-  </para>
-<!## end>
-
-  <sect1 id="regress-run">
-   <title>Running the Tests</title>
-
-<!## XC>
-&xconly;
-  <para>
-   Current version of <productname>Postgres-XC</productname> doesn't
-   support the regression test to run after building but before
-   installation.  You can use each test manually but it is left to
-   users.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Current version of <productname>Postgres-XL</productname> doesn't
-   support the regression test to run after building but before
-   installation.  You can use each test manually but it is left to
-   users.
-  </para>
-<!## end>
-<!## PG>
-  <para>
-   The regression tests can be run against an already installed and
-   running server, or using a temporary installation within the build
-   tree.  Furthermore, there is a <quote>parallel</quote> and a
-   <quote>sequential</quote> mode for running the tests.  The
-   sequential method runs each test script alone, while the
-   parallel method starts up multiple server processes to run groups
-   of tests in parallel.  Parallel testing gives confidence that
-   interprocess communication and locking are working correctly.
-  </para>
-
-  <sect2>
-   <title>Running the Tests Against a Temporary Installation</title>
-
-  <para>
-   To run the parallel regression tests after building but before installation,
-   type:
-<screen>
-gmake check
-</screen>
-   in the top-level directory.  (Or you can change to
-   <filename>src/test/regress</filename> and run the command there.)
-   This will first build several auxiliary files, such as
-   sample user-defined trigger functions, and then run the test driver
-   script.  At the end you should see something like:
-<screen>
-<computeroutput>
-=======================
- All 115 tests passed.
-=======================
-</computeroutput>
-</screen>
-   or otherwise a note about which tests failed.  See <xref
-   linkend="regress-evaluation"> below before assuming that a
-   <quote>failure</> represents a serious problem.
-  </para>
-
-   <para>
-    Because this test method runs a temporary server, it will not work
-    when you are the root user (since the server will not start as root).
-    If you already did the build as root, you do not have to start all
-    over.  Instead, make the regression test directory writable by
-    some other user, log in as that user, and restart the tests.
-    For example:
-<screen>
-<prompt>root# </prompt><userinput>chmod -R a+w src/test/regress</userinput>
-<prompt>root# </prompt><userinput>su - joeuser</userinput>
-<prompt>joeuser$ </prompt><userinput>cd <replaceable>top-level build directory</></userinput>
-<prompt>joeuser$ </prompt><userinput>gmake check</userinput>
-</screen>
-    (The only possible <quote>security risk</quote> here is that other
-    users might be able to alter the regression test results behind
-    your back.  Use common sense when managing user permissions.)
-   </para>
-   <para>
-    Alternatively, run the tests after installation.
-   </para>
-
-   <para>
-    If you have configured <productname>PostgreSQL</productname> to install
-    into a location where an older <productname>PostgreSQL</productname>
-    installation already exists, and you perform <literal>gmake check</>
-    before installing the new version, you might find that the tests fail
-    because the new programs try to use the already-installed shared
-    libraries.  (Typical symptoms are complaints about undefined symbols.)
-    If you wish to run the tests before overwriting the old installation,
-    you'll need to build with <literal>configure --disable-rpath</>.
-    It is not recommended that you use this option for the final installation,
-    however.
-   </para>
-
-   <para>
-    The parallel regression test starts quite a few processes under your
-    user ID.  Presently, the maximum concurrency is twenty parallel test
-    scripts, which means forty processes: there's a server process and a
-    <application>psql</> process for each test script.
-    So if your system enforces a per-user limit on the number of processes,
-    make sure this limit is at least fifty or so, else you might get
-    random-seeming failures in the parallel test.  If you are not in
-    a position to raise the limit, you can cut down the degree of parallelism
-    by setting the <literal>MAX_CONNECTIONS</> parameter.  For example:
-<screen>
-gmake MAX_CONNECTIONS=10 check
-</screen>
-    runs no more than ten tests concurrently.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Running the Tests Against an Existing Installation</title>
-
-  <para>
-   To run the tests after installation<![%standalone-ignore;[ (see <xref linkend="installation">)]]>,
-   initialize a data area and start the
-   server, <![%standalone-ignore;[as explained in <xref linkend="runtime">, ]]> then type:
-<screen>
-gmake installcheck
-</screen>
-or for a parallel test:
-<screen>
-gmake installcheck-parallel
-</screen>
-   The tests will expect to contact the server at the local host and the
-   default port number, unless directed otherwise by <envar>PGHOST</envar> and
-   <envar>PGPORT</envar> environment variables.
-  </para>
-
-  <para>
-   The source distribution also contains regression tests for the optional
-   procedural languages and for some of the <filename>contrib</> modules.
-   At present, these tests can be used only against an already-installed
-   server.  To run the tests for all procedural languages that have been
-   built and installed, change to the <filename>src/pl</> directory of the
-   build tree and type:
-<screen>
-gmake installcheck
-</screen>
-   You can also do this in any of the subdirectories of <filename>src/pl</>
-   to run tests for just one procedural language.  To run the tests for all
-   <filename>contrib</> modules that have them, change to the
-   <filename>contrib</> directory of the build tree and type:
-<screen>
-gmake installcheck
-</screen>
-   The <filename>contrib</> modules must have been built and installed first.
-   You can also do this in a subdirectory of <filename>contrib</> to run
-   the tests for just one module.
-  </para>
-  </sect2>
-
-  <sect2>
-   <title>Testing Hot Standby</title>
-
-  <para>
-   The source distribution also contains regression tests of the static
-   behaviour of Hot Standby. These tests require a running primary server
-   and a running standby server that is accepting new WAL changes from the
-   primary using either file-based log shipping or streaming replication.
-   Those servers are not automatically created for you, nor is the setup
-   documented here. Please check the various sections of the documentation already
-   devoted to the required commands and related issues.
-  </para>
-
-  <para>
-   First create a database called "regression" on the primary.
-<screen>
-psql -h primary -c "CREATE DATABASE regression"
-</screen>
-   Next, run a preparatory script on the primary in the regression database:
-   <filename>src/test/regress/sql/hs_primary_setup.sql</filename>, and
-   allow for the changes to propagate to the standby, for example
-<screen>
-psql -h primary -f src/test/regress/sql/hs_primary_setup.sql regression
-</screen>
-   Now confirm that the default connection for the tester is the standby
-   server under test and then run the <literal>standbycheck</> target from the regression
-   directory:
-<screen>
-cd src/test/regress
-gmake standbycheck
-</screen>
-  </para>
-
-  <para>
-   Some extreme behaviours can also be generated on the primary using the
-   script: <filename>src/test/regress/sql/hs_primary_extremes.sql</filename>
-   to allow the behaviour of the standby to be tested.
-  </para>
-
-  <para>
-   Additional automated testing may be available in later releases.
-  </para>
-  </sect2>
-
-  <sect2>
-   <title>Locale and Encoding</title>
-
-   <para>
-    By default, the tests against a temporary installation use the
-    locale defined in the current environment and the corresponding
-    database encoding as determined by <command>initdb</command>.  It
-    can be useful to test different locales by setting the appropriate
-    environment variables, for example:
-<screen>
-gmake check LANG=C
-gmake check LC_COLLATE=en_US.utf8 LC_CTYPE=fr_CA.utf8
-</screen>
-    For implementation reasons, setting <envar>LC_ALL</envar> does not
-    work for this purpose; all the other locale-related environment
-    variables do work.
-   </para>
-
-   <para>
-    When testing against an existing installation, the locale is
-    determined by the existing database cluster and cannot be set
-    separately for the test run.
-   </para>
-
-   <para>
-    You can also choose the database encoding explicitly by setting
-    the variable <envar>ENCODING</envar>, for example:
-<screen>
-gmake check LANG=C ENCODING=EUC_JP
-</screen>
-    Setting the database encoding this way typically only makes sense
-    if the locale is C; otherwise the encoding is chosen automatically
-    from the locale, and specifying an encoding that does not match
-    the locale will result in an error.
-   </para>
-
-   <para>
-    The encoding can be set for tests against a temporary or an
-    existing installation.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Extra Tests</title>
-
-   <para>
-    The regression test suite contains a few test files that are not
-    run by default, because they might be platform-dependent or take a
-    very long time to run.  You can run these or other extra test
-    files by setting the variable <envar>EXTRA_TESTS</envar>.  For
-    example, to run the <literal>numeric_big</literal> test:
-<screen>
-gmake check EXTRA_TESTS=numeric_big
-</screen>
-    To run the collation tests:
-<screen>
-gmake check EXTRA_TESTS=collate.linux.utf8 LANG=en_US.utf8
-</screen>
-    The <literal>collate.linux.utf8</> test works only on Linux/glibc
-    platforms, and only when run in a database that uses UTF-8 encoding.
-   </para>
-  </sect2>
-<!## end>
-  </sect1>
-
-  <sect1 id="regress-evaluation">
-   <title>Test Evaluation</title>
-
-<!## XC>
-&xconly;
-  <para>
-   Current version of <productname>Postgres-XC</productname> doesn't
-   support the regression test to run after building but before
-   installation.  You can use each test manually but it is left to
-   users.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Current version of <productname>Postgres-XL</productname> doesn't
-   support the regression test to run after building but before
-   installation.  You can use each test manually but it is left to
-   users.
-  </para>
-<!## end>
-
-<!## PG>
-   <para>
-    Some properly installed and fully functional
-    <productname>PostgreSQL</productname> installations can
-    <quote>fail</quote> some of these regression tests due to
-    platform-specific artifacts such as varying floating-point representation
-    and message wording. The tests are currently evaluated using a simple
-    <command>diff</command> comparison against the outputs
-    generated on a reference system, so the results are sensitive to
-    small system differences.  When a test is reported as
-    <quote>failed</quote>, always examine the differences between
-    expected and actual results; you might find that the
-    differences are not significant.  Nonetheless, we still strive to
-    maintain accurate reference files across all supported platforms,
-    so it can be expected that all tests pass.
-   </para>
-
-   <para>
-    The actual outputs of the regression tests are in files in the
-    <filename>src/test/regress/results</filename> directory. The test
-    script uses <command>diff</command> to compare each output
-    file against the reference outputs stored in the
-    <filename>src/test/regress/expected</filename> directory.  Any
-    differences are saved for your inspection in
-    <filename>src/test/regress/regression.diffs</filename>.  (Or you
-    can run <command>diff</command> yourself, if you prefer.)
-   </para>
-
-   <para>
-    If for some reason a particular platform generates a <quote>failure</>
-    for a given test, but inspection of the output convinces you that
-    the result is valid, you can add a new comparison file to silence
-    the failure report in future test runs.  See
-    <xref linkend="regress-variant"> for details.
-   </para>
-
-   <sect2>
-    <title>Error Message Differences</title>
-
-    <para>
-     Some of the regression tests involve intentional invalid input
-     values.  Error messages can come from either the
-     <productname>PostgreSQL</productname> code or from the host
-     platform system routines. In the latter case, the messages can
-     vary between platforms, but should reflect similar
-     information. These differences in messages will result in a
-     <quote>failed</quote> regression test that can be validated by
-     inspection.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Locale Differences</title>
-
-    <para>
-     If you run the tests against a server that was
-     initialized with a collation-order locale other than C, then
-     there might be differences due to sort order and subsequent
-     failures.  The regression test suite is set up to handle this
-     problem by providing alternate result files that together are
-     known to handle a large number of locales.
-    </para>
-
-    <para>
-     To run the tests in a different locale when using the
-     temporary-installation method, pass the appropriate
-     locale-related environment variables on
-     the <command>make</command> command line, for example:
-<programlisting>
-gmake check LANG=de_DE.utf8
-</programlisting>
-     (The regression test driver unsets <envar>LC_ALL</envar>, so it
-     does not work to choose the locale using that variable.)  To use
-     no locale, either unset all locale-related environment variables
-     (or set them to <literal>C</literal>) or use the following
-     special invocation:
-<programlisting>
-gmake check NO_LOCALE=1
-</programlisting>
-     When running the tests against an existing installation, the
-     locale setup is determined by the existing installation.  To
-     change it, initialize the database cluster with a different
-     locale by passing the appropriate options
-     to <command>initdb</command>.
-    </para>
-
-    <para>
-     In general, it is nevertheless advisable to try to run the
-     regression tests in the locale setup that is wanted for
-     production use, as this will exercise the locale- and
-     encoding-related code portions that will actually be used in
-     production.  Depending on the operating system environment, you
-     might get failures, but then you will at least know what
-     locale-specific behaviors to expect when running real
-     applications.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Date and Time Differences</title>
-
-    <para>
-     Most of the date and time results are dependent on the time zone
-     environment.  The reference files are generated for time zone
-     <literal>PST8PDT</literal> (Berkeley, California), and there will be
-     apparent failures if the tests are not run with that time zone setting.
-     The regression test driver sets environment variable
-     <envar>PGTZ</envar> to <literal>PST8PDT</literal>, which normally
-     ensures proper results.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Floating-Point Differences</title>
-
-    <para>
-     Some of the tests involve computing 64-bit floating-point numbers (<type>double
-     precision</type>) from table columns. Differences in
-     results involving mathematical functions of <type>double
-     precision</type> columns have been observed.  The <literal>float8</> and
-     <literal>geometry</> tests are particularly prone to small differences
-     across platforms, or even with different compiler optimization setting.
-     Human eyeball comparison is needed to determine the real
-     significance of these differences which are usually 10 places to
-     the right of the decimal point.
-    </para>
-
-    <para>
-     Some systems display minus zero as <literal>-0</>, while others
-     just show <literal>0</>.
-    </para>
-
-    <para>
-     Some systems signal errors from <function>pow()</function> and
-     <function>exp()</function> differently from the mechanism
-     expected by the current <productname>PostgreSQL</productname>
-     code.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Row Ordering Differences</title>
-
-    <para>
-You might see differences in which the same rows are output in a
-different order than what appears in the expected file.  In most cases
-this is not, strictly speaking, a bug.  Most of the regression test
-scripts are not so pedantic as to use an <literal>ORDER BY</> for every single
-<literal>SELECT</>, and so their result row orderings are not well-defined
-according to the SQL specification.  In practice, since we are
-looking at the same queries being executed on the same data by the same
-software, we usually get the same result ordering on all platforms,
-so the lack of <literal>ORDER BY</> is not a problem.  Some queries do exhibit
-cross-platform ordering differences, however.  When testing against an
-already-installed server, ordering differences can also be caused by
-non-C locale settings or non-default parameter settings, such as custom values
-of <varname>work_mem</> or the planner cost parameters.
-    </para>
-
-    <para>
-Therefore, if you see an ordering difference, it's not something to
-worry about, unless the query does have an <literal>ORDER BY</> that your
-result is violating.  However, please report it anyway, so that we can add an
-<literal>ORDER BY</> to that particular query to eliminate the bogus
-<quote>failure</quote> in future releases.
-    </para>
-
-    <para>
-You might wonder why we don't order all the regression test queries explicitly
-to get rid of this issue once and for all.  The reason is that that would
-make the regression tests less useful, not more, since they'd tend
-to exercise query plan types that produce ordered results to the
-exclusion of those that don't.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Insufficient Stack Depth</title>
-
-    <para>
-     If the <literal>errors</literal> test results in a server crash
-     at the <literal>select infinite_recurse()</> command, it means that
-     the platform's limit on process stack size is smaller than the
-     <![%standalone-ignore;[<xref linkend="guc-max-stack-depth">]]>
-     <![%standalone-include;[<literal>max_stack_depth</literal>]]>
-     parameter indicates.  This
-     can be fixed by running the server under a higher stack
-     size limit (4MB is recommended with the default value of
-     <varname>max_stack_depth</>).  If you are unable to do that, an
-     alternative is to reduce the value of <varname>max_stack_depth</>.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>The <quote>random</quote> Test</title>
-
-    <para>
-     The <literal>random</literal> test script is intended to produce
-     random results.   In rare cases, this causes the random regression
-     test to fail.  Typing:
-<programlisting>
-diff results/random.out expected/random.out
-</programlisting>
-     should produce only one or a few lines of differences.  You need
-     not worry unless the random test fails repeatedly.
-    </para>
-   </sect2>
-<!## end>
-  </sect1>
-
-<!-- We might want to move the following section into the developer's guide. -->
-  <sect1 id="regress-variant">
-   <title>Variant Comparison Files</title>
-
-<!## XC>
-&xconly;
-  <para>
-   Current version of <productname>Postgres-XC</productname> doesn't
-   support the regression test to run after building but before
-   installation.  You can use each test manually but it is left to
-   users.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Current version of <productname>Postgres-XL</productname> doesn't
-   support the regression test to run after building but before
-   installation.  You can use each test manually but it is left to
-   users.
-  </para>
-<!## end>
-
-<!## PG>
-   <para>
-    Since some of the tests inherently produce environment-dependent
-    results, we have provided ways to specify alternate <quote>expected</>
-    result files.  Each regression test can have several comparison files
-    showing possible results on different platforms.  There are two
-    independent mechanisms for determining which comparison file is used
-    for each test.
-   </para>
-
-   <para>
-    The first mechanism allows comparison files to be selected for
-    specific platforms.  There is a mapping file,
-    <filename>src/test/regress/resultmap</filename>, that defines
-    which comparison file to use for each platform.
-    To eliminate bogus test <quote>failures</quote> for a particular platform,
-    you first choose or make a variant result file, and then add a line to the
-    <filename>resultmap</filename> file.
-   </para>
-
-   <para>
-    Each line in the mapping file is of the form
-<synopsis>
-testname:output:platformpattern=comparisonfilename
-</synopsis>
-    The test name is just the name of the particular regression test
-    module. The output value indicates which output file to check. For the
-    standard regression tests, this is always <literal>out</literal>. The
-    value corresponds to the file extension of the output file.
-    The platform pattern is a pattern in the style of the Unix
-    tool <command>expr</> (that is, a regular expression with an implicit
-    <literal>^</literal> anchor at the start).  It is matched against the
-    platform name as printed by <command>config.guess</command>.
-    The comparison file name is the base name of the substitute result
-    comparison file.
-   </para>
-
-   <para>
-    For example: some systems interpret very small floating-point values
-    as zero, rather than reporting an underflow error.  This causes a
-    few differences in the <filename>float8</> regression test.
-    Therefore, we provide a variant comparison file,
-    <filename>float8-small-is-zero.out</filename>, which includes
-    the results to be expected on these systems.  To silence the bogus
-    <quote>failure</quote> message on <systemitem>OpenBSD</systemitem>
-    platforms, <filename>resultmap</filename> includes:
-<programlisting>
-float8:out:i.86-.*-openbsd=float8-small-is-zero.out
-</programlisting>
-    which will trigger on any machine where the output of
-    <command>config.guess</command> matches <literal>i.86-.*-openbsd</literal>.
-    Other lines
-    in <filename>resultmap</> select the variant comparison file for other
-    platforms where it's appropriate.
-   </para>
-
-   <para>
-    The second selection mechanism for variant comparison files is
-    much more automatic: it simply uses the <quote>best match</> among
-    several supplied comparison files.  The regression test driver
-    script considers both the standard comparison file for a test,
-    <literal><replaceable>testname</>.out</>, and variant files named
-    <literal><replaceable>testname</>_<replaceable>digit</>.out</>
-    (where the <replaceable>digit</> is any single digit
-    <literal>0</>-<literal>9</>).  If any such file is an exact match,
-    the test is considered to pass; otherwise, the one that generates
-    the shortest diff is used to create the failure report.  (If
-    <filename>resultmap</filename> includes an entry for the particular
-    test, then the base <replaceable>testname</> is the substitute
-    name given in <filename>resultmap</filename>.)
-   </para>
-
-   <para>
-    For example, for the <literal>char</literal> test, the comparison file
-    <filename>char.out</filename> contains results that are expected
-    in the <literal>C</> and <literal>POSIX</> locales, while
-    the file <filename>char_1.out</filename> contains results sorted as
-    they appear in many other locales.
-   </para>
-
-   <para>
-    The best-match mechanism was devised to cope with locale-dependent
-    results, but it can be used in any situation where the test results
-    cannot be predicted easily from the platform name alone.  A limitation of
-    this mechanism is that the test driver cannot tell which variant is
-    actually <quote>correct</> for the current environment; it will just pick
-    the variant that seems to work best.  Therefore it is safest to use this
-    mechanism only for variant results that you are willing to consider
-    equally valid in all contexts.
-   </para>
-<!## end>
-  </sect1>
-
-  <sect1 id="regress-coverage">
-   <title>Test Coverage Examination</title>
-
-<!## XC>
-&xconly;
-  <para>
-   Current version of <productname>Postgres-XC</productname> doesn't
-   support the regression test to run after building but before
-   installation.  You can use each test manually but it is left to
-   users.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Current version of <productname>Postgres-XL</productname> doesn't
-   support the regression test to run after building but before
-   installation.  You can use each test manually but it is left to
-   users.
-  </para>
-<!## end>
-
-<!## PG>
-   <para>
-    The PostgreSQL source code can be compiled with coverage testing
-    instrumentation, so that it becomes possible to examine which
-    parts of the code are covered by the regression tests or any other
-    test suite that is run with the code.  This is currently supported
-    when compiling with GCC and requires the <command>gcov</command>
-    and <command>lcov</command> programs.
-   </para>
-
-   <para>
-    A typical workflow would look like this:
-<screen>
-./configure --enable-coverage ... OTHER OPTIONS ...
-gmake
-gmake check # or other test suite
-gmake coverage-html
-</screen>
-    Then point your HTML browser
-    to <filename>coverage/index.html</filename>.
-    The <command>gmake</command> commands also work in subdirectories.
-   </para>
-
-   <para>
-    To reset the execution counts between test runs, run:
-<screen>
-gmake coverage-clean
-</screen>
-   </para>
-<!## end>
-  </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/release-7.4.sgmlin b/doc-xc/src/sgml/release-7.4.sgmlin
deleted file mode 100644
index ee8184b16c..0000000000
--- a/doc-xc/src/sgml/release-7.4.sgmlin
+++ /dev/null
@@ -1,4622 +0,0 @@
-<!-- doc/src/sgml/release-7.4.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-7-4-30">
-  <title>Release 7.4.30</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2010-10-04</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.29.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <para>
-   This is expected to be the last <productname>PostgreSQL</> release
-   in the 7.4.X series.  Users are encouraged to update to a newer
-   release branch soon.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.30</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you are upgrading from a version earlier than 7.4.26,
-    see the release notes for 7.4.26.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Use a separate interpreter for each calling SQL userid in PL/Perl and
-      PL/Tcl (Tom Lane)
-     </para>
-
-     <para>
-      This change prevents security problems that can be caused by subverting
-      Perl or Tcl code that will be executed later in the same session under
-      another SQL user identity (for example, within a <literal>SECURITY
-      DEFINER</> function).  Most scripting languages offer numerous ways that
-      that might be done, such as redefining standard functions or operators
-      called by the target function.  Without this change, any SQL user with
-      Perl or Tcl language usage rights can do essentially anything with the
-      SQL privileges of the target function's owner.
-     </para>
-
-     <para>
-      The cost of this change is that intentional communication among Perl
-      and Tcl functions becomes more difficult.  To provide an escape hatch,
-      PL/PerlU and PL/TclU functions continue to use only one interpreter
-      per session.  This is not considered a security issue since all such
-      functions execute at the trust level of a database superuser already.
-     </para>
-
-     <para>
-      It is likely that third-party procedural languages that claim to offer
-      trusted execution have similar security issues.  We advise contacting
-      the authors of any PL you are depending on for security-critical
-      purposes.
-     </para>
-
-     <para>
-      Our thanks to Tim Bunce for pointing out this issue (CVE-2010-3433).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible crashes in <function>pg_get_expr()</> by disallowing
-      it from being called with an argument that is not one of the system
-      catalog columns it's intended to be used with
-      (Heikki Linnakangas, Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>cannot handle unplanned sub-select</quote> error (Tom Lane)
-     </para>
-
-     <para>
-      This occurred when a sub-select contains a join alias reference that
-      expands into an expression containing another sub-select.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Take care to fsync the contents of lockfiles (both
-      <filename>postmaster.pid</> and the socket lockfile) while writing them
-      (Tom Lane)
-     </para>
-
-     <para>
-      This omission could result in corrupted lockfile contents if the
-      machine crashes shortly after postmaster start.  That could in turn
-      prevent subsequent attempts to start the postmaster from succeeding,
-      until the lockfile is manually removed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <filename>contrib/dblink</>'s handling of tables containing
-      dropped columns (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix connection leak after <quote>duplicate connection name</quote>
-      errors in <filename>contrib/dblink</> (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update build infrastructure and documentation to reflect the source code
-      repository's move from CVS to Git (Magnus Hagander and others)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-29">
-  <title>Release 7.4.29</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2010-05-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.28.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <para>
-   The <productname>PostgreSQL</> community will stop releasing updates
-   for the 7.4.X release series in July 2010.
-   Users are encouraged to update to a newer release branch soon.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.29</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you are upgrading from a version earlier than 7.4.26,
-    see the release notes for 7.4.26.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Enforce restrictions in <literal>plperl</> using an opmask applied to
-      the whole interpreter, instead of using <filename>Safe.pm</>
-      (Tim Bunce, Andrew Dunstan)
-     </para>
-
-     <para>
-      Recent developments have convinced us that <filename>Safe.pm</> is too
-      insecure to rely on for making <literal>plperl</> trustable.  This
-      change removes use of <filename>Safe.pm</> altogether, in favor of using
-      a separate interpreter with an opcode mask that is always applied.
-      Pleasant side effects of the change include that it is now possible to
-      use Perl's <literal>strict</> pragma in a natural way in
-      <literal>plperl</>, and that Perl's <literal>$a</> and <literal>$b</>
-      variables work as expected in sort routines, and that function
-      compilation is significantly faster.  (CVE-2010-1169)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent PL/Tcl from executing untrustworthy code from
-      <structname>pltcl_modules</> (Tom)
-     </para>
-
-     <para>
-      PL/Tcl's feature for autoloading Tcl code from a database table
-      could be exploited for trojan-horse attacks, because there was no
-      restriction on who could create or insert into that table.  This change
-      disables the feature unless <structname>pltcl_modules</> is owned by a
-      superuser.  (However, the permissions on the table are not checked, so
-      installations that really need a less-than-secure modules table can
-      still grant suitable privileges to trusted non-superusers.)  Also,
-      prevent loading code into the unrestricted <quote>normal</> Tcl
-      interpreter unless we are really going to execute a <literal>pltclu</>
-      function.  (CVE-2010-1170)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not allow an unprivileged user to reset superuser-only parameter
-      settings (Alvaro)
-     </para>
-
-     <para>
-      Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
-      ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
-      a database he owns, this would remove all special parameter settings
-      for the user or database, even ones that are only supposed to be
-      changeable by a superuser.  Now, the <command>ALTER</> will only
-      remove the parameters that the user has permission to change.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crash during backend shutdown if shutdown occurs
-      when a <literal>CONTEXT</> addition would be made to log entries (Tom)
-     </para>
-
-     <para>
-      In some cases the context-printing function would fail because the
-      current transaction had already been rolled back when it came time
-      to print a log message.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update pl/perl's <filename>ppport.h</> for modern Perl versions
-      (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
-      interrupts promptly (Tatsuhito Kasahara)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make server startup deal properly with the case that
-      <function>shmget()</> returns <literal>EINVAL</> for an existing
-      shared memory segment (Tom)
-     </para>
-
-     <para>
-      This behavior has been observed on BSD-derived kernels including OS X.
-      It resulted in an entirely-misleading startup failure complaining that
-      the shared memory request size was too large.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-28">
-  <title>Release 7.4.28</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2010-03-15</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.27.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <para>
-   The <productname>PostgreSQL</> community will stop releasing updates
-   for the 7.4.X release series in July 2010.
-   Users are encouraged to update to a newer release branch soon.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.28</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you are upgrading from a version earlier than 7.4.26,
-    see the release notes for 7.4.26.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Add new configuration parameter <varname>ssl_renegotiation_limit</> to
-      control how often we do session key renegotiation for an SSL connection
-      (Magnus)
-     </para>
-
-     <para>
-      This can be set to zero to disable renegotiation completely, which may
-      be required if a broken SSL library is used.  In particular, some
-      vendors are shipping stopgap patches for CVE-2009-3555 that cause
-      renegotiation attempts to fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>substring()</> for <type>bit</> types treat any negative
-      length as meaning <quote>all the rest of the string</> (Tom)
-     </para>
-
-     <para>
-      The previous coding treated only -1 that way, and would produce an
-      invalid result value for other negative values, possibly leading to
-      a crash (CVE-2010-0442).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some cases of pathologically slow regular expression matching (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      When reading <filename>pg_hba.conf</> and related files, do not treat
-      <literal>@something</> as a file inclusion request if the <literal>@</>
-      appears inside quote marks; also, never treat <literal>@</> by itself
-      as a file inclusion request (Tom)
-     </para>
-
-     <para>
-      This prevents erratic behavior if a role or database name starts with
-      <literal>@</>.  If you need to include a file whose path name
-      contains spaces, you can still do so, but you must write
-      <literal>@"/path to/file"</> rather than putting the quotes around
-      the whole construct.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite loop on some platforms if a directory is named as
-      an inclusion target in <filename>pg_hba.conf</> and related files
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
-     </para>
-
-     <para>
-      The only known symptom of this oversight is that the Tcl
-      <literal>clock</> command misbehaves if using Tcl 8.5 or later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent crash in <filename>contrib/dblink</> when too many key
-      columns are specified to a <function>dblink_build_sql_*</> function
-      (Rushabh Lathia, Joe Conway)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-27">
-  <title>Release 7.4.27</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-12-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.26.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.27</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you are upgrading from a version earlier than 7.4.26,
-    see the release notes for 7.4.26.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Protect against indirect security threats caused by index functions
-      changing session-local state (Gurjeet Singh, Tom)
-     </para>
-
-     <para>
-      This change prevents allegedly-immutable index functions from possibly
-      subverting a superuser's session (CVE-2009-4136).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Reject SSL certificates containing an embedded null byte in the common
-      name (CN) field (Magnus)
-     </para>
-
-     <para>
-      This prevents unintended matching of a certificate to a server or client
-      name during SSL validation (CVE-2009-4034).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash during backend-startup-time cache initialization (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent signals from interrupting <literal>VACUUM</> at unsafe times
-      (Alvaro)
-     </para>
-
-     <para>
-      This fix prevents a PANIC if a <literal>VACUUM FULL</> is cancelled
-      after it's already committed its tuple movements, as well as transient
-      errors if a plain <literal>VACUUM</> is interrupted after having
-      truncated the table.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash due to integer overflow in hash table size
-      calculation (Tom)
-     </para>
-
-     <para>
-      This could occur with extremely large planner estimates for the size of
-      a hashjoin's result.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix very rare crash in <type>inet</>/<type>cidr</> comparisons (Chris
-      Mikkelson)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PAM password processing to be more robust (Tom)
-     </para>
-
-     <para>
-      The previous code is known to fail with the combination of the Linux
-      <literal>pam_krb5</> PAM module with Microsoft Active Directory as the
-      domain controller.  It might have problems elsewhere too, since it was
-      making unjustified assumptions about what arguments the PAM stack would
-      pass to it.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make the postmaster ignore any <literal>application_name</> parameter in
-      connection request packets, to improve compatibility with future libpq
-      versions (Tom)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-26">
-  <title>Release 7.4.26</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-09-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.25.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.26</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you have any hash indexes on <type>interval</> columns,
-    you must <command>REINDEX</> them after updating to 7.4.26.
-    Also, if you are upgrading from a version earlier than 7.4.11,
-    see the release notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Disallow <command>RESET ROLE</> and <command>RESET SESSION
-      AUTHORIZATION</> inside security-definer functions (Tom, Heikki)
-     </para>
-
-     <para>
-      This covers a case that was missed in the previous patch that
-      disallowed <command>SET ROLE</> and <command>SET SESSION
-      AUTHORIZATION</> inside security-definer functions.
-      (See CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix handling of sub-SELECTs appearing in the arguments of
-      an outer-level aggregate function (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix hash calculation for data type <type>interval</> (Tom)
-     </para>
-
-     <para>
-      This corrects wrong results for hash joins on interval values.
-      It also changes the contents of hash indexes on interval columns.
-      If you have any such indexes, you must <command>REINDEX</> them
-      after updating.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix overflow for <literal>INTERVAL '<replaceable>x</> ms'</literal>
-      when <replaceable>x</> is more than 2 million and integer
-      datetimes are in use (Alex Hunsaker)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix calculation of distance between a point and a line segment (Tom)
-     </para>
-
-     <para>
-      This led to incorrect results from a number of geometric operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <type>money</> data type to work in locales where currency
-      amounts have no fractional digits, e.g. Japan (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Properly round datetime input like
-      <literal>00:12:57.9999999999999999999999999999</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix poor choice of page split point in GiST R-tree operator classes
-      (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix portability issues in plperl initialization (Andrew Dunstan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve robustness of <application>libpq</>'s code to recover
-      from errors during <command>COPY FROM STDIN</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid including conflicting readline and editline header files
-      when both libraries are installed (Zdenek Kotala)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-25">
-  <title>Release 7.4.25</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-03-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.24.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.25</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you are upgrading from a version earlier than 7.4.11,
-    see the release notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent error recursion crashes when encoding conversion fails (Tom)
-     </para>
-
-     <para>
-      This change extends fixes made in the last two minor releases for
-      related failure scenarios.  The previous fixes were narrowly tailored
-      for the original problem reports, but we have now recognized that
-      <emphasis>any</> error thrown by an encoding conversion function could
-      potentially lead to infinite recursion while trying to report the
-      error.  The solution therefore is to disable translation and encoding
-      conversion and report the plain-ASCII form of any error message,
-      if we find we have gotten into a recursive error reporting situation.
-      (CVE-2009-0922)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>CREATE CONVERSION</> with the wrong encodings
-      for the specified conversion function (Heikki)
-     </para>
-
-     <para>
-      This prevents one possible scenario for encoding conversion failure.
-      The previous change is a backstop to guard against other kinds of
-      failures in the same area.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix core dump when <function>to_char()</> is given format codes that
-      are inappropriate for the type of the data argument (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>MUST</> (Mauritius Island Summer Time) to the default list
-      of known timezone abbreviations (Xavier Bugaud)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-24">
-  <title>Release 7.4.24</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-02-02</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.23.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.24</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you are upgrading from a version earlier than 7.4.11,
-    see the release notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Improve handling of URLs in <function>headline()</> function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve handling of overlength headlines in <function>headline()</>
-      function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible Assert failure or misconversion if an encoding
-      conversion is created with the wrong conversion function for the
-      specified pair of encodings (Tom, Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unnecessary locking of small tables in <command>VACUUM</>
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix uninitialized variables in <filename>contrib/tsearch2</>'s
-      <function>get_covers()</> function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in <function>to_char()</>'s handling of <literal>TH</>
-      format codes (Andreas Scherbaum)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make all documentation reference <literal>pgsql-bugs</> and/or
-      <literal>pgsql-hackers</> as appropriate, instead of the
-      now-decommissioned <literal>pgsql-ports</> and <literal>pgsql-patches</>
-      mailing lists (Tom)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-23">
-  <title>Release 7.4.23</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-11-03</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.22.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.23</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you are upgrading from a version earlier than 7.4.11,
-    see the release notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix backend crash when the client encoding cannot represent a localized
-      error message (Tom)
-     </para>
-
-     <para>
-      We have addressed similar issues before, but it would still fail if
-      the <quote>character has no equivalent</> message itself couldn't
-      be converted.  The fix is to disable localization and send the plain
-      ASCII error message when we detect such a situation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect tsearch2 headline generation when single query
-      item matches first word of text (Sushant Sinha)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix improper display of fractional seconds in interval values when
-      using a non-ISO datestyle in an <option>--enable-integer-datetimes</>
-      build (Ron Mayer)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <function>SPI_getvalue</> and <function>SPI_getbinval</>
-      behave correctly when the passed tuple and tuple descriptor have
-      different numbers of columns (Tom)
-     </para>
-
-     <para>
-      This situation is normal when a table has had columns added or removed,
-      but these two functions didn't handle it properly.
-      The only likely consequence is an incorrect error indication.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</>'s parsing of <command>CREATE USER</> (Michael)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-22">
-  <title>Release 7.4.22</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-09-22</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.21.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.22</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you are upgrading from a version earlier than 7.4.11,
-    see the release notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix datetime input functions to correctly detect integer overflow when
-      running on a 64-bit platform (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve performance of writing very long log messages to syslog (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in backwards scanning of a cursor on a <literal>SELECT DISTINCT
-      ON</> query (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner to estimate that <literal>GROUP BY</> expressions yielding
-      boolean results always result in two groups, regardless of the
-      expressions' contents (Tom)
-     </para>
-
-     <para>
-      This is very substantially more accurate than the regular <literal>GROUP
-      BY</> estimate for certain boolean tests like <replaceable>col</>
-      <literal>IS NULL</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <application>pg_dump</> and <application>pg_restore</>'s
-      error reporting after failure to send a SQL command (Tom)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-21">
-  <title>Release 7.4.21</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-06-12</simpara>
-  </note>
-
-  <para>
-   This release contains one serious bug fix over 7.4.20.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.21</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you are upgrading from a version earlier than 7.4.11,
-    see the release notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Make <function>pg_get_ruledef()</> parenthesize negative constants (Tom)
-     </para>
-
-     <para>
-      Before this fix, a negative constant in a view or rule might be dumped
-      as, say, <literal>-42::integer</>, which is subtly incorrect: it should
-      be <literal>(-42)::integer</> due to operator precedence rules.
-      Usually this would make little difference, but it could interact with
-      another recent patch to cause
-      <productname>PostgreSQL</> to reject what had been a valid
-      <command>SELECT DISTINCT</> view query.  Since this could result in
-      <application>pg_dump</> output failing to reload, it is being treated
-      as a high-priority fix.  The only released versions in which dump
-      output is actually incorrect are 8.3.1 and 8.2.7.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-20">
-  <title>Release 7.4.20</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>never released</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.19.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.20</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-    However, if you are upgrading from a version earlier than 7.4.11,
-    see the release notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix conversions between ISO-8859-5 and other encodings to handle
-      Cyrillic <quote>Yo</> characters (<literal>e</> and <literal>E</> with
-      two dots) (Sergey Burladyan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a few datatype input functions
-      that were allowing unused bytes in their results to contain
-      uninitialized, unpredictable values (Tom)
-     </para>
-
-     <para>
-      This could lead to failures in which two apparently identical literal
-      values were not seen as equal, resulting in the parser complaining
-      about unmatched <literal>ORDER BY</> and <literal>DISTINCT</>
-      expressions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a corner case in regular-expression substring matching
-      (<literal>substring(<replaceable>string</> from
-      <replaceable>pattern</>)</literal>) (Tom)
-     </para>
-
-     <para>
-      The problem occurs when there is a match to the pattern overall but
-      the user has specified a parenthesized subexpression and that
-      subexpression hasn't got a match.  An example is
-      <literal>substring('foo' from 'foo(bar)?')</>.
-      This should return NULL, since <literal>(bar)</> isn't matched, but
-      it was mistakenly returning the whole-pattern match instead (ie,
-      <literal>foo</>).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect result from <application>ecpg</>'s
-      <function>PGTYPEStimestamp_sub()</> function (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>DatumGetBool</> macro to not fail with <application>gcc</>
-      4.3 (Tom)
-     </para>
-
-     <para>
-      This problem affects <quote>old style</> (V0) C functions that
-      return boolean.  The fix is already in 8.3, but the need to
-      back-patch it was not realized at the time.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix longstanding <command>LISTEN</>/<command>NOTIFY</>
-      race condition (Tom)
-     </para>
-
-     <para>
-      In rare cases a session that had just executed a
-      <command>LISTEN</> might not get a notification, even though
-      one would be expected because the concurrent transaction executing
-      <command>NOTIFY</> was observed to commit later.
-     </para>
-
-     <para>
-      A side effect of the fix is that a transaction that has executed
-      a not-yet-committed <command>LISTEN</> command will not see any
-      row in <structname>pg_listener</> for the <command>LISTEN</>,
-      should it choose to look; formerly it would have.  This behavior
-      was never documented one way or the other, but it is possible that
-      some applications depend on the old behavior.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix display of constant expressions in <literal>ORDER BY</>
-      and <literal>GROUP BY</> (Tom)
-     </para>
-
-     <para>
-      An explictly casted constant would be shown incorrectly.  This could
-      for example lead to corruption of a view definition during
-      dump and reload.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>libpq</> to handle NOTICE messages correctly
-      during COPY OUT (Tom)
-     </para>
-
-     <para>
-      This failure has only been observed to occur when a user-defined
-      datatype's output routine issues a NOTICE, but there is no
-      guarantee it couldn't happen due to other causes.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-19">
-  <title>Release 7.4.19</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-01-07</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.18,
-   including fixes for significant security issues.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.19</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.11, see the release
-    notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent functions in indexes from executing with the privileges of
-      the user running <command>VACUUM</>, <command>ANALYZE</>, etc (Tom)
-     </para>
-
-     <para>
-      Functions used in index expressions and partial-index
-      predicates are evaluated whenever a new table entry is made.  It has
-      long been understood that this poses a risk of trojan-horse code
-      execution if one modifies a table owned by an untrustworthy user.
-      (Note that triggers, defaults, check constraints, etc. pose the
-      same type of risk.)  But functions in indexes pose extra danger
-      because they will be executed by routine maintenance operations
-      such as <command>VACUUM FULL</>, which are commonly performed
-      automatically under a superuser account.  For example, a nefarious user
-      can execute code with superuser privileges by setting up a
-      trojan-horse index definition and waiting for the next routine vacuum.
-      The fix arranges for standard maintenance operations
-      (including <command>VACUUM</>, <command>ANALYZE</>, <command>REINDEX</>,
-      and <command>CLUSTER</>) to execute as the table owner rather than
-      the calling user, using the same privilege-switching mechanism already
-      used for <literal>SECURITY DEFINER</> functions.  To prevent bypassing
-      this security measure, execution of <command>SET SESSION
-      AUTHORIZATION</> and <command>SET ROLE</> is now forbidden within a
-      <literal>SECURITY DEFINER</> context.  (CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Repair assorted bugs in the regular-expression package (Tom, Will Drewry)
-     </para>
-
-     <para>
-      Suitably crafted regular-expression patterns could cause crashes,
-      infinite or near-infinite looping, and/or massive memory consumption,
-      all of which pose denial-of-service hazards for applications that
-      accept regex search patterns from untrustworthy sources.
-      (CVE-2007-4769, CVE-2007-4772, CVE-2007-6067)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require non-superusers who use <filename>/contrib/dblink</> to use only
-      password authentication, as a security measure (Joe)
-     </para>
-
-     <para>
-      The fix that appeared for this in 7.4.18 was incomplete, as it plugged
-      the hole for only some <filename>dblink</> functions.  (CVE-2007-6601,
-      CVE-2007-3278)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner failure in some cases of <literal>WHERE false AND var IN
-      (SELECT ...)</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential crash in <function>translate()</> when using a multibyte
-      database encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Python to not crash on long exception messages (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <application>ecpg</> parser fixes (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <filename>contrib/tablefunc</>'s <function>crosstab()</> handle
-      NULL rowid as a category in its own right, rather than crashing (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <type>tsvector</> and <type>tsquery</> output routines to
-      escape backslashes correctly (Teodor, Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash of <function>to_tsvector()</> on huge input strings (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require a specific version of <productname>Autoconf</> to be used
-      when re-generating the <command>configure</> script (Peter)
-     </para>
-
-     <para>
-      This affects developers and packagers only.  The change was made
-      to prevent accidental use of untested combinations of
-      <productname>Autoconf</> and <productname>PostgreSQL</> versions.
-      You can remove the version check if you really want to use a
-      different <productname>Autoconf</> version, but it's
-      your responsibility whether the result works or not.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-18">
-  <title>Release 7.4.18</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-09-17</simpara>
-  </note>
-
-  <para>
-   This release contains fixes from 7.4.17.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.18</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.11, see the release
-    notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent index corruption when a transaction inserts rows and
-      then aborts close to the end of a concurrent <command>VACUUM</>
-      on the same table (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>CREATE DOMAIN ... DEFAULT NULL</> work properly (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix excessive logging of <acronym>SSL</> error messages (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash when <varname>log_min_error_statement</> logging runs out
-      of memory (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent <command>CLUSTER</> from failing
-      due to attempting to process temporary tables of other sessions (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require non-superusers who use <filename>/contrib/dblink</> to use only
-      password authentication, as a security measure (Joe)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-17">
-  <title>Release 7.4.17</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-04-23</simpara>
-  </note>
-
-  <para>
-   This release contains fixes from 7.4.16,
-   including a security fix.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.17</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.11, see the release
-    notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Support explicit placement of the temporary-table schema within
-     <varname>search_path</>, and disable searching it for functions
-     and operators (Tom)
-    </para>
-    <para>
-     This is needed to allow a security-definer function to set a
-     truly secure value of <varname>search_path</>.  Without it,
-     an unprivileged SQL user can use temporary objects to execute code
-     with the privileges of the security-definer function (CVE-2007-2138).
-     See <command>CREATE FUNCTION</> for more information.
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     <filename>/contrib/tsearch2</> crash fixes (Teodor)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix potential-data-corruption bug in how <command>VACUUM FULL</> handles
-     <command>UPDATE</> chains (Tom, Pavan Deolasee)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix PANIC during enlargement of a hash index (bug introduced in 7.4.15)
-     (Tom)
-    </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-16">
-  <title>Release 7.4.16</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-02-05</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.15, including
-   a security fix.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.16</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.11, see the release
-    notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Remove security vulnerability that allowed connected users
-     to read backend memory (Tom)
-    </para>
-    <para>
-     The vulnerability involves suppressing the normal check that a SQL
-     function returns the data type it's declared to, or changing the
-     data type of a table column used in a SQL function (CVE-2007-0555).
-     This error can easily be exploited to cause a backend crash, and in
-     principle might be used to read database content that the user
-     should not be able to access.
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix rare bug wherein btree index page splits could fail
-     due to choosing an infeasible split point (Heikki Linnakangas)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix for rare Assert() crash triggered by <literal>UNION</> (Tom)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Tighten security of multi-byte character processing for UTF8 sequences
-     over three bytes long (Tom)
-    </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-15">
-  <title>Release 7.4.15</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-01-08</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.14.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.15</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.11, see the release
-    notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Improve handling of <function>getaddrinfo()</> on AIX (Tom)
-     </para>
-
-     <para>
-      This fixes a problem with starting the statistics collector,
-      among other things.
-     </para>
-    </listitem>
-
-     <listitem>
-      <para>
-       Fix <quote>failed to re-find parent key</> errors in
-       <command>VACUUM</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix bugs affecting multi-gigabyte hash indexes (Tom)
-      </para>
-     </listitem>
-
-    <listitem>
-     <para>
-      Fix error when constructing an <literal>ARRAY[]</> made up of multiple
-      empty elements (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>to_number()</> and <function>to_char(numeric)</>
-      are now <literal>STABLE</>, not <literal>IMMUTABLE</>, for
-      new <application>initdb</> installs (Tom)
-     </para>
-
-     <para>
-      This is because <varname>lc_numeric</> can potentially
-      change the output of these functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve index usage of regular expressions that use parentheses (Tom)
-     </para>
-
-     <para>
-      This improves <application>psql</> <literal>\d</> performance also.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-14">
-  <title>Release 7.4.14</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-10-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.13.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.14</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.11, see the release
-    notes for 7.4.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fix core dump when an untyped literal is taken as
-ANYARRAY</para></listitem>
-<listitem><para>Fix <function>string_to_array()</> to handle overlapping
- matches for the separator string</para>
-<para>For example, <literal>string_to_array('123xx456xxx789', 'xx')</>.
-</para></listitem>
-<listitem><para>Fix corner cases in pattern matching for
- <application>psql</>'s <literal>\d</> commands</para></listitem>
-<listitem><para>Fix index-corrupting bugs in /contrib/ltree
- (Teodor)</para></listitem>
-<listitem><para>Fix backslash escaping in /contrib/dbmirror</para></listitem>
-<listitem><para>Adjust regression tests for recent changes in US DST laws
-</para> </listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-13">
-  <title>Release 7.4.13</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-05-23</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.12,
-   including patches for extremely serious security issues.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.13</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.11, see the release
-    notes for 7.4.11.
-   </para>
-
-   <para>
-    Full security against the SQL-injection attacks described in
-    CVE-2006-2313 and CVE-2006-2314 might require changes in application
-    code.  If you have applications that embed untrustworthy strings
-    into SQL commands, you should examine them as soon as possible to
-    ensure that they are using recommended escaping techniques.  In
-    most cases, applications should be using subroutines provided by
-    libraries or drivers (such as <application>libpq</>'s
-    <function>PQescapeStringConn()</>) to perform string escaping,
-    rather than relying on <foreignphrase>ad hoc</> code to do it.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Change the server to reject invalidly-encoded multibyte
-characters in all cases (Tatsuo, Tom)</para>
-<para>While <productname>PostgreSQL</> has been moving in this direction for
-some time, the checks are now applied uniformly to all encodings and all
-textual input, and are now always errors not merely warnings.  This change
-defends against SQL-injection attacks of the type described in CVE-2006-2313.
-</para></listitem>
-
-<listitem><para>Reject unsafe uses of <literal>\'</> in string literals</para>
-<para>As a server-side defense against SQL-injection attacks of the type
-described in CVE-2006-2314, the server now only accepts <literal>''</> and not
-<literal>\'</> as a representation of ASCII single quote in SQL string
-literals.  By default, <literal>\'</> is rejected only when
-<varname>client_encoding</> is set to a client-only encoding (SJIS, BIG5, GBK,
-GB18030, or UHC), which is the scenario in which SQL injection is possible.
-A new configuration parameter <varname>backslash_quote</> is available to
-adjust this behavior when needed.  Note that full security against
-CVE-2006-2314 might require client-side changes; the purpose of
-<varname>backslash_quote</> is in part to make it obvious that insecure
-clients are insecure.
-</para></listitem>
-
-<listitem><para>Modify <application>libpq</>'s string-escaping routines to be
-aware of encoding considerations and
-<varname>standard_conforming_strings</></para>
-<para>This fixes <application>libpq</>-using applications for the security
-issues described in CVE-2006-2313 and CVE-2006-2314, and also future-proofs
-them against the planned changeover to SQL-standard string literal syntax.
-Applications that use multiple <productname>PostgreSQL</> connections
-concurrently should migrate to <function>PQescapeStringConn()</> and
-<function>PQescapeByteaConn()</> to ensure that escaping is done correctly
-for the settings in use in each database connection.  Applications that
-do string escaping <quote>by hand</> should be modified to rely on library
-routines instead.
-</para></listitem>
-
-<listitem><para>Fix some incorrect encoding conversion functions</para>
-<para><function>win1251_to_iso</>, <function>alt_to_iso</>,
-<function>euc_tw_to_big5</>, <function>euc_tw_to_mic</>,
-<function>mic_to_euc_tw</> were all broken to varying
-extents.
-</para></listitem>
-
-<listitem><para>Clean up stray remaining uses of <literal>\'</> in strings
-(Bruce, Jan)</para></listitem>
-
-<listitem><para>Fix bug that sometimes caused OR'd index scans to
-miss rows they should have returned</para></listitem>
-
-<listitem><para>Fix WAL replay for case where a btree index has been
-truncated</para></listitem>
-
-<listitem><para>Fix <literal>SIMILAR TO</> for patterns involving
-<literal>|</> (Tom)</para></listitem>
-
-<listitem><para>Fix server to use custom DH SSL parameters correctly (Michael
-Fuhr)</para></listitem>
-
-<listitem><para>Fix for Bonjour on Intel Macs (Ashley Clark)</para></listitem>
-
-<listitem><para>Fix various minor memory leaks</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-12">
-  <title>Release 7.4.12</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-02-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.11.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.12</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.11, see the release
-    notes for 7.4.11.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix potential crash in <command>SET
-SESSION AUTHORIZATION</> (CVE-2006-0553)</para>
-<para>An unprivileged user could crash the server process, resulting in
-momentary denial of service to other users, if the server has been compiled
-with Asserts enabled (which is not the default).
-Thanks to Akio Ishida for reporting this problem.
-</para></listitem>
-
-<listitem><para>Fix bug with row visibility logic in self-inserted
-rows (Tom)</para>
-<para>Under rare circumstances a row inserted by the current command
-could be seen as already valid, when it should not be.  Repairs bug
-created in 7.4.9 and 7.3.11 releases.
-</para></listitem>
-
-<listitem><para>Fix race condition that could lead to <quote>file already
-exists</> errors during pg_clog file creation
-(Tom)</para></listitem>
-
-<listitem><para>Properly check <literal>DOMAIN</> constraints for
-<literal>UNKNOWN</> parameters in prepared statements
-(Neil)</para></listitem>
-
-<listitem><para>Fix to allow restoring dumps that have cross-schema
-references to custom operators (Tom)</para></listitem>
-
-<listitem><para>Portability fix for testing presence of <function>finite</>
-and <function>isinf</> during configure (Tom)</para></listitem>
-
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-11">
-  <title>Release 7.4.11</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-01-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.10.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.11</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.8, see the release
-    notes for 7.4.8.
-    Also, you might need to <command>REINDEX</> indexes on textual
-    columns after updating, if you are affected by the locale or
-    <application>plperl</> issues described below.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix for protocol-level Describe messages issued
-outside a transaction or in a failed transaction (Tom)</para></listitem>
-
-<listitem><para>Fix character string comparison for locales that consider
-different character combinations as equal, such as Hungarian (Tom)</para>
-<para>This might require <command>REINDEX</> to fix existing indexes on
-textual columns.</para></listitem>
-
-<listitem><para>Set locale environment variables during postmaster startup
-to ensure that <application>plperl</> won't change the locale later</para>
-<para>This fixes a problem that occurred if the <application>postmaster</> was
-started with environment variables specifying a different locale than what
-<application>initdb</> had been told.  Under these conditions, any use of
-<application>plperl</> was likely to lead to corrupt indexes.  You might need
-<command>REINDEX</> to fix existing indexes on
-textual columns if this has happened to you.</para></listitem>
-
-<listitem><para>Fix longstanding bug in strpos() and regular expression
-handling in certain rarely used Asian multi-byte character sets (Tatsuo)
-</para></listitem>
-
-<listitem><para>Fix bug in <filename>/contrib/pgcrypto</> gen_salt,
-which caused it not to use all available salt space for MD5 and
-XDES algorithms (Marko Kreen, Solar Designer)</para>
-<para>Salts for Blowfish and standard DES are unaffected.</para></listitem>
-
-<listitem><para>Fix <filename>/contrib/dblink</> to throw an error,
-rather than crashing, when the number of columns specified is different from
-what's actually returned by the query (Joe)</para></listitem>
-
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-10">
-  <title>Release 7.4.10</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-12-12</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.9.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.10</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.8, see the release
-    notes for 7.4.8.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix race condition in transaction log management</para>
-<para>There was a narrow window in which an I/O operation could be initiated
-for the wrong page, leading to an Assert failure or data
-corruption.</para>
-</listitem>
-
-<listitem><para>Prevent failure if client sends Bind protocol message
-when current transaction is already aborted</para></listitem>
-
-<listitem><para><filename>/contrib/ltree</> fixes (Teodor)</para></listitem>
-
-<listitem><para>AIX and HPUX compile fixes (Tom)</para></listitem>
-
-<listitem><para>Fix longstanding planning error for outer joins</para>
-<para>This bug sometimes caused a bogus error <quote>RIGHT JOIN is
-only supported with merge-joinable join conditions</>.</para></listitem>
-
-<listitem><para>Prevent core dump in <application>pg_autovacuum</> when a
-table has been dropped</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-9">
-  <title>Release 7.4.9</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-10-04</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.8.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.9</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    if you are upgrading from a version earlier than 7.4.8, see the release
-    notes for 7.4.8.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fix error that allowed <command>VACUUM</> to remove
-<literal>ctid</> chains too soon, and add more checking in code that follows
-<literal>ctid</> links</para>
-<para>This fixes a long-standing problem that could cause crashes in very rare
-circumstances.</para></listitem>
-<listitem><para>Fix <type>CHAR()</> to properly pad spaces to the specified
-length when using a multiple-byte character set (Yoshiyuki Asaba)</para>
-<para>In prior releases, the padding of <type>CHAR()</> was incorrect
-because it only padded to the specified number of bytes without
-considering how many characters were stored.</para></listitem>
-<listitem><para>Fix the sense of the test for read-only transaction
-in <command>COPY</></para>
-<para>The code formerly prohibited <command>COPY TO</>, where it should
-prohibit <command>COPY FROM</>.
-</para></listitem>
-<listitem><para>Fix planning problem with outer-join ON clauses that reference
-only the inner-side relation</para></listitem>
-<listitem><para>Further fixes for <literal>x FULL JOIN y ON true</> corner
-cases</para></listitem>
-<listitem><para>Make <function>array_in</> and <function>array_recv</> more
-paranoid about validating their OID parameter</para></listitem>
-<listitem><para>Fix missing rows in queries like <literal>UPDATE a=... WHERE
-a...</> with GiST index on column <literal>a</></para></listitem>
-<listitem><para>Improve robustness of datetime parsing</para></listitem>
-<listitem><para>Improve checking for partially-written WAL
-pages</para></listitem>
-<listitem><para>Improve robustness of signal handling when SSL is
-enabled</para></listitem>
-<listitem><para>Don't try to open more than <literal>max_files_per_process</>
-files during postmaster startup</para></listitem>
-<listitem><para>Various memory leakage fixes</para></listitem>
-<listitem><para>Various portability improvements</para></listitem>
-<listitem><para>Fix PL/pgSQL to handle <literal>var := var</> correctly when
-the variable is of pass-by-reference type</para></listitem>
-<listitem><para>Update <filename>contrib/tsearch2</> to use current Snowball
-code</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-8">
-  <title>Release 7.4.8</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-05-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.7, including several
-   security-related issues.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.8</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    it is one possible way of handling two significant security problems
-    that have been found in the initial contents of 7.4.X system
-    catalogs.  A dump/initdb/reload sequence using 7.4.8's initdb will
-    automatically correct these problems.
-   </para>
-
-   <para>
-    The larger security problem is that the built-in character set encoding
-    conversion functions can be invoked from SQL commands by unprivileged
-    users, but the functions were not designed for such use and are not
-    secure against malicious choices of arguments.  The fix involves changing
-    the declared parameter list of these functions so that they can no longer
-    be invoked from SQL commands.  (This does not affect their normal use
-    by the encoding conversion machinery.)
-   </para>
-
-   <para>
-    The lesser problem is that the <filename>contrib/tsearch2</> module
-    creates several functions that are misdeclared to return
-    <type>internal</> when they do not accept <type>internal</> arguments.
-    This breaks type safety for all functions using <type>internal</>
-    arguments.
-   </para>
-
-   <para>
-    It is strongly recommended that all installations repair these errors,
-    either by initdb or by following the manual repair procedures given
-    below.  The errors at least allow unprivileged database users to crash
-    their server process, and might allow unprivileged users to gain the
-    privileges of a database superuser.
-   </para>
-
-   <para>
-    If you wish not to do an initdb, perform the following procedures instead.
-    As the database superuser, do:
-
-<programlisting>
-BEGIN;
-UPDATE pg_proc SET proargtypes[3] = 'internal'::regtype
-WHERE pronamespace = 11 AND pronargs = 5
-     AND proargtypes[2] = 'cstring'::regtype;
--- The command should report having updated 90 rows;
--- if not, rollback and investigate instead of committing!
-COMMIT;
-</programlisting>
-
-    Next, if you have installed <filename>contrib/tsearch2</>, do:
-
-<programlisting>
-BEGIN;
-UPDATE pg_proc SET proargtypes[0] = 'internal'::regtype
-WHERE oid IN (
-   'dex_init(text)'::regprocedure,
-   'snb_en_init(text)'::regprocedure,
-   'snb_ru_init(text)'::regprocedure,
-   'spell_init(text)'::regprocedure,
-   'syn_init(text)'::regprocedure
-);
--- The command should report having updated 5 rows;
--- if not, rollback and investigate instead of committing!
-COMMIT;
-</programlisting>
-
-    If this command fails with a message like <quote>function
-    "dex_init(text)" does not exist</>, then either <filename>tsearch2</>
-    is not installed in this database, or you already did the update.
-   </para>
-
-   <para>
-    The above procedures must be carried out in <emphasis>each</> database
-    of an installation, including <literal>template1</>, and ideally
-    including <literal>template0</> as well.  If you do not fix the
-    template databases then any subsequently created databases will contain
-    the same errors.  <literal>template1</> can be fixed in the same way
-    as any other database, but fixing <literal>template0</> requires
-    additional steps.  First, from any database issue:
-<programlisting>
-UPDATE pg_database SET datallowconn = true WHERE datname = 'template0';
-</programlisting>
-     Next connect to <literal>template0</> and perform the above repair
-     procedures.  Finally, do:
-<programlisting>
--- re-freeze template0:
-VACUUM FREEZE;
--- and protect it against future alterations:
-UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Change encoding function signature to prevent
-misuse</para></listitem>
-<listitem><para>Change <filename>contrib/tsearch2</> to avoid unsafe use of
-<type>INTERNAL</> function results</para></listitem>
-<listitem><para>Repair ancient race condition that allowed a transaction to be
-seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner
-than for other purposes</para>
-<para>This is an extremely serious bug since it could lead to apparent
-data inconsistencies being briefly visible to applications.</para></listitem>
-<listitem><para>Repair race condition between relation extension and
-VACUUM</para>
-<para>This could theoretically have caused loss of a page's worth of
-freshly-inserted data, although the scenario seems of very low probability.
-There are no known cases of it having caused more than an Assert failure.
-</para></listitem>
-<listitem><para>Fix comparisons of <type>TIME WITH TIME ZONE</> values</para>
-<para>
-The comparison code was wrong in the case where the
-<literal>--enable-integer-datetimes</> configuration switch had been used.
-NOTE: if you have an index on a <type>TIME WITH TIME ZONE</> column,
-it will need to be <command>REINDEX</>ed after installing this update, because
-the fix corrects the sort order of column values.
-</para></listitem>
-<listitem><para>Fix <function>EXTRACT(EPOCH)</> for
-<type>TIME WITH TIME ZONE</> values</para></listitem>
-<listitem><para>Fix mis-display of negative fractional seconds in
-<type>INTERVAL</> values</para>
-<para>
-This error only occurred when the
-<literal>--enable-integer-datetimes</> configuration switch had been used.
-</para></listitem>
-<listitem><para>Ensure operations done during backend shutdown are counted by
-statistics collector</para>
-<para>
-This is expected to resolve reports of <application>pg_autovacuum</>
-not vacuuming the system catalogs often enough &mdash; it was not being
-told about catalog deletions caused by temporary table removal during
-backend exit.
-</para></listitem>
-<listitem><para>Additional buffer overrun checks in plpgsql
-(Neil)</para></listitem>
-<listitem><para>Fix pg_dump to dump trigger names containing <literal>%</>
-correctly (Neil)</para></listitem>
-<listitem><para>Fix <filename>contrib/pgcrypto</> for newer OpenSSL builds
-(Marko Kreen)</para></listitem>
-<listitem><para>Still more 64-bit fixes for
-<filename>contrib/intagg</></para></listitem>
-<listitem><para>Prevent incorrect optimization of functions returning
-<type>RECORD</></para></listitem>
-<listitem><para>Prevent <function>to_char(interval)</> from dumping core for
-month-related formats</para></listitem>
-<listitem><para>Prevent crash on <literal>COALESCE(NULL,NULL)</></para></listitem>
-<listitem><para>Fix <function>array_map</> to call PL functions correctly</para></listitem>
-<listitem><para>Fix permission checking in <command>ALTER DATABASE RENAME</></para></listitem>
-<listitem><para>Fix <command>ALTER LANGUAGE RENAME</></para></listitem>
-<listitem><para>Make <function>RemoveFromWaitQueue</> clean up after itself</para>
-<para>
-This fixes a lock management error that would only be visible if a transaction
-was kicked out of a wait for a lock (typically by query cancel) and then the
-holder of the lock released it within a very narrow window.
-</para></listitem>
-<listitem><para>Fix problem with untyped parameter appearing in
-<command>INSERT ... SELECT</></para></listitem>
-<listitem><para>Fix <command>CLUSTER</> failure after
-<command>ALTER TABLE SET WITHOUT OIDS</></para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-7">
-  <title>Release 7.4.7</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-01-31</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.6, including several
-   security-related issues.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.4.7</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Disallow <command>LOAD</> to non-superusers</para>
-<para>
-On platforms that will automatically execute initialization functions of a
-shared library (this includes at least Windows and ELF-based Unixen),
-<command>LOAD</> can be used to make the server execute arbitrary code.
-Thanks to NGS Software for reporting this.</para></listitem>
-<listitem><para>Check that creator of an aggregate function has the right to
-execute the specified transition functions</para>
-<para>
-This oversight made it possible to bypass denial of EXECUTE
-permission on a function.</para></listitem>
-<listitem><para>Fix security and 64-bit issues in
-contrib/intagg</para></listitem>
-<listitem><para>Add needed STRICT marking to some contrib functions (Kris
-Jurka)</para></listitem>
-<listitem><para>Avoid buffer overrun when plpgsql cursor declaration has too
-many parameters (Neil)</para></listitem>
-<listitem><para>Fix planning error for FULL and RIGHT outer joins</para>
-<para>
-The result of the join was mistakenly supposed to be sorted the same as the
-left input.  This could not only deliver mis-sorted output to the user, but
-in case of nested merge joins could give outright wrong answers.
-</para></listitem>
-<listitem><para>Fix plperl for quote marks in tuple fields</para></listitem>
-<listitem><para>Fix display of negative intervals in SQL and GERMAN
-datestyles</para></listitem>
-<listitem><para>Make age(timestamptz) do calculation in local timezone not
-GMT</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-6">
-  <title>Release 7.4.6</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2004-10-22</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.5.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.4.6</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Repair possible failure to update hint bits on disk</para>
-<para>
-Under rare circumstances this oversight could lead to
-<quote>could not access transaction status</> failures, which qualifies
-it as a potential-data-loss bug.
-</para></listitem>
-<listitem><para>Ensure that hashed outer join does not miss tuples</para>
-<para>
-Very large left joins using a hash join plan could fail to output unmatched
-left-side rows given just the right data distribution.
-</para></listitem>
-<listitem><para>Disallow running <application>pg_ctl</> as root</para>
-<para>
-This is to guard against any possible security issues.
-</para></listitem>
-<listitem><para>Avoid using temp files in <filename>/tmp</> in <command>make_oidjoins_check</command></para>
-<para>
-This has been reported as a security issue, though it's hardly worthy of
-concern since there is no reason for non-developers to use this script anyway.
-</para></listitem>
-<listitem><para>Prevent forced backend shutdown from re-emitting prior command
-result</para>
-<para>
-In rare cases, a client might think that its last command had succeeded when
-it really had been aborted by forced database shutdown.
-</para></listitem>
-<listitem><para>Repair bug in <function>pg_stat_get_backend_idset</function></para>
-<para>
-This could lead to misbehavior in some of the system-statistics views.
-</para></listitem>
-<listitem><para>Fix small memory leak in postmaster</para></listitem>
-<listitem><para>Fix <quote>expected both swapped tables to have TOAST
-tables</> bug</para>
-<para>
-This could arise in cases such as CLUSTER after ALTER TABLE DROP COLUMN.
-</para></listitem>
-<listitem><para>Prevent <literal>pg_ctl restart</> from adding <literal>-D</> multiple times</para></listitem>
-<listitem><para>Fix problem with NULL values in GiST indexes</para></listitem>
-<listitem><para><literal>::</> is no longer interpreted as a variable in an
-ECPG prepare statement</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-5">
-  <title>Release 7.4.5</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2004-08-18</simpara>
-  </note>
-
-  <para>
-   This release contains one serious bug fix over 7.4.4.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.4.5</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Repair possible crash during concurrent B-tree index insertions</para>
-<para>
-This patch fixes a rare case in which concurrent insertions into a B-tree index
-could result in a server panic.  No permanent damage would result, but it's
-still worth a re-release.  The bug does not exist in pre-7.4 releases.
-</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-4">
-  <title>Release 7.4.4</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2004-08-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.3.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.4.4</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Prevent possible loss of committed transactions during crash</para>
-<para>
-Due to insufficient interlocking between transaction commit and checkpointing,
-it was possible for transactions committed just before the most recent
-checkpoint to be lost, in whole or in part, following a database crash and
-restart.  This is a serious bug that has existed
-since <productname>PostgreSQL</productname> 7.1.
-</para></listitem>
-<listitem><para>Check HAVING restriction before evaluating result list of an
-aggregate plan</para></listitem>
-<listitem><para>Avoid crash when session's current user ID is deleted</para></listitem>
-<listitem><para>Fix hashed crosstab for zero-rows case (Joe)</para></listitem>
-<listitem><para>Force cache update after renaming a column in a foreign key</para></listitem>
-<listitem><para>Pretty-print UNION queries correctly</para></listitem>
-<listitem><para>Make psql handle <literal>\r\n</> newlines properly in COPY IN</para></listitem>
-<listitem><para><application>pg_dump</> handled ACLs with grant options incorrectly</para></listitem>
-<listitem><para>Fix thread support for OS X and Solaris</para></listitem>
-<listitem><para>Updated JDBC driver (build 215) with various fixes</para></listitem>
-<listitem><para>ECPG fixes</para></listitem>
-<listitem><para>Translation updates (various contributors)</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-3">
-  <title>Release 7.4.3</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2004-06-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.2.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.4.3</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fix temporary memory leak when using non-hashed aggregates (Tom)</para></listitem>
-<listitem><para>ECPG fixes, including some for Informix compatibility (Michael)</para></listitem>
-<listitem><para>Fixes for compiling with thread-safety, particularly Solaris (Bruce)</para></listitem>
-<listitem><para>Fix error in COPY IN termination when using the old network protocol (ljb)</para></listitem>
-<listitem><para>Several important fixes in pg_autovacuum, including fixes for
-large tables, unsigned oids, stability, temp tables, and debug mode
-(Matthew T. O'Connor)</para></listitem>
-<listitem><para>Fix problem with reading tar-format dumps on NetBSD and BSD/OS (Bruce)</para></listitem>
-<listitem><para>Several JDBC fixes</para></listitem>
-<listitem><para>Fix ALTER SEQUENCE RESTART where last_value equals the restart value (Tom)</para></listitem>
-<listitem><para>Repair failure to recalculate nested sub-selects (Tom)</para></listitem>
-<listitem><para>Fix problems with non-constant expressions in LIMIT/OFFSET</para></listitem>
-<listitem><para>Support FULL JOIN with no join clause, such as X FULL JOIN Y ON TRUE (Tom)</para></listitem>
-<listitem><para>Fix another zero-column table bug (Tom)</para></listitem>
-<listitem><para>Improve handling of non-qualified identifiers in GROUP BY clauses in sub-selects (Tom)</para>
-<para>
-Select-list aliases within the sub-select will now take precedence over
-names from outer query levels.
-</para></listitem>
-<listitem><para>Do not generate <quote>NATURAL CROSS JOIN</> when decompiling rules (Tom)</para></listitem>
-<listitem><para>Add checks for invalid field length in binary COPY (Tom)</para>
-<para>
- This fixes a difficult-to-exploit security hole.
-</para></listitem>
-<listitem><para>Avoid locking conflict between <command>ANALYZE</command> and <command>LISTEN</command>/<command>NOTIFY</command></para></listitem>
-<listitem><para>Numerous translation updates (various contributors)</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-2">
-  <title>Release 7.4.2</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2004-03-08</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.1.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.4.2</title>
-
-   <para>
-    A dump/restore is not required for those running 7.4.X.  However,
-    it might be advisable as the easiest method of incorporating fixes for
-    two errors that have been found in the initial contents of 7.4.X system
-    catalogs.  A dump/initdb/reload sequence using 7.4.2's initdb will
-    automatically correct these problems.
-   </para>
-
-   <para>
-    The more severe of the two errors is that data type <type>anyarray</>
-    has the wrong alignment label; this is a problem because the
-    <structname>pg_statistic</> system catalog uses <type>anyarray</>
-    columns.  The mislabeling can cause planner misestimations and even
-    crashes when planning queries that involve <literal>WHERE</> clauses on
-    double-aligned columns (such as <type>float8</> and <type>timestamp</>).
-    It is strongly recommended that all installations repair this error,
-    either by initdb or by following the manual repair procedure given
-    below.
-   </para>
-
-   <para>
-    The lesser error is that the system view <structname>pg_settings</>
-    ought to be marked as having public update access, to allow
-    <literal>UPDATE pg_settings</> to be used as a substitute for
-    <command>SET</>.  This can also be fixed either by initdb or manually,
-    but it is not necessary to fix unless you want to use <literal>UPDATE
-    pg_settings</>.
-   </para>
-
-   <para>
-    If you wish not to do an initdb, the following procedure will work
-    for fixing <structname>pg_statistic</>.  As the database superuser,
-    do:
-
-<programlisting>
--- clear out old data in pg_statistic:
-DELETE FROM pg_statistic;
-VACUUM pg_statistic;
--- this should update 1 row:
-UPDATE pg_type SET typalign = 'd' WHERE oid = 2277;
--- this should update 6 rows:
-UPDATE pg_attribute SET attalign = 'd' WHERE atttypid = 2277;
---
--- At this point you MUST start a fresh backend to avoid a crash!
---
--- repopulate pg_statistic:
-ANALYZE;
-</programlisting>
-
-    This can be done in a live database, but beware that all backends
-    running in the altered database must be restarted before it is safe to
-    repopulate <structname>pg_statistic</>.
-   </para>
-
-   <para>
-    To repair the <structname>pg_settings</> error, simply do:
-<programlisting>
-GRANT SELECT, UPDATE ON pg_settings TO PUBLIC;
-</programlisting>
-   </para>
-
-   <para>
-    The above procedures must be carried out in <emphasis>each</> database
-    of an installation, including <literal>template1</>, and ideally
-    including <literal>template0</> as well.  If you do not fix the
-    template databases then any subsequently created databases will contain
-    the same errors.  <literal>template1</> can be fixed in the same way
-    as any other database, but fixing <literal>template0</> requires
-    additional steps.  First, from any database issue:
-<programlisting>
-UPDATE pg_database SET datallowconn = true WHERE datname = 'template0';
-</programlisting>
-     Next connect to <literal>template0</> and perform the above repair
-     procedures.  Finally, do:
-<programlisting>
--- re-freeze template0:
-VACUUM FREEZE;
--- and protect it against future alterations:
-UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<para>
-   Release 7.4.2 incorporates all the fixes included in release 7.3.6,
-   plus the following fixes:
-</para>
-
-<itemizedlist>
-<listitem><para>Fix <structname>pg_statistics</> alignment bug that could crash optimizer</para>
-<para>See above for details about this problem.</para></listitem>
-<listitem><para>Allow non-super users to update <structname>pg_settings</></para></listitem>
-<listitem><para>Fix several optimizer bugs, most of which led to
-<quote>variable not found in subplan target lists</> errors</para></listitem>
-<listitem><para>Avoid out-of-memory failure during startup of large multiple
-index scan</para></listitem>
-<listitem><para>Fix multibyte problem that could lead to <quote>out of
-memory</> error during <command>COPY IN</></para></listitem>
-<listitem><para>Fix problems with <command>SELECT INTO</> / <command>CREATE
-TABLE AS</> from tables without OIDs</para></listitem>
-<listitem><para>Fix problems with <filename>alter_table</> regression test
-during parallel testing</para></listitem>
-<listitem><para>Fix problems with hitting open file limit, especially on OS X (Tom)</para></listitem>
-<listitem><para>Partial fix for Turkish-locale issues</para>
-<para>initdb will succeed now in Turkish locale, but there are still some
-inconveniences associated with the <literal>i/I</> problem.</para></listitem>
-<listitem><para>Make pg_dump set client encoding on restore</para></listitem>
-<listitem><para>Other minor pg_dump fixes</para></listitem>
-<listitem><para>Allow ecpg to again use C keywords as column names (Michael)</para></listitem>
-<listitem><para>Added ecpg <literal>WHENEVER NOT_FOUND</> to
-<literal>SELECT/INSERT/UPDATE/DELETE</> (Michael)</para></listitem>
-<listitem><para>Fix ecpg crash for queries calling set-returning functions (Michael)</para></listitem>
-<listitem><para>Various other ecpg fixes (Michael)</para></listitem>
-<listitem><para>Fixes for Borland compiler</para></listitem>
-<listitem><para>Thread build improvements (Bruce)</para></listitem>
-<listitem><para>Various other build fixes</para></listitem>
-<listitem><para>Various JDBC fixes</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-4-1">
-  <title>Release 7.4.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2003-12-22</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.4.
-   For information about new features in the 7.4 major release, see
-   <xref linkend="release-7-4">.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.4.1</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running 7.4.
-   </para>
-
-   <para>
-    If you want to install the fixes in the information schema
-    you need to reload it into the database.
-    This is either accomplished by initializing a new cluster
-    by running <command>initdb</command>, or by running the following
-    sequence of SQL commands in each database (ideally including
-    <literal>template1</literal>) as a superuser in
-    <application>psql</application>, after installing the new release:
-<programlisting>
-DROP SCHEMA information_schema CASCADE;
-\i /usr/local/pgsql/share/information_schema.sql
-</programlisting>
-    Substitute your installation path in the second command.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fixed bug in <command>CREATE SCHEMA</command> parsing in ECPG (Michael)</para></listitem>
-<listitem><para>Fix compile error when <option>--enable-thread-safety</option> and <option>--with-perl</option> are used together (Peter)</para></listitem>
-<listitem><para>Fix for subqueries that used hash joins (Tom)</para>
-<para>
-   Certain subqueries that used hash joins would crash because of
-   improperly shared structures.
-</para></listitem>
-<listitem><para>Fix free space map compaction bug (Tom)</para>
-<para>
-   This fixes a bug where compaction of the free space map could lead
-   to a database server shutdown.
-</para>
-</listitem>
-<listitem><para>Fix for Borland compiler build of libpq (Bruce)</para></listitem>
-<listitem><para>Fix <function>netmask()</function> and <function>hostmask()</function> to return the maximum-length masklen (Tom)</para>
-<para>
-   Fix these functions to return values consistent with pre-7.4
-   releases.
-</para>
-</listitem>
-<listitem><para>Several <filename>contrib/pg_autovacuum</filename> fixes</para>
-<para>
-   Fixes include improper variable initialization, missing vacuum after
-   <command>TRUNCATE</command>, and duration computation overflow for long vacuums.
-</para>
-</listitem>
-<listitem><para>Allow compile of <filename>contrib/cube</filename> under Cygwin (Jason Tishler)</para></listitem>
-<listitem><para>Fix Solaris use of password file when no passwords are defined (Tom)</para>
-<para>
-   Fix crash on Solaris caused by use of any type of password
-   authentication when no passwords were defined.
-</para>
-</listitem>
-<listitem><para>JDBC fix for thread problems, other fixes</para></listitem>
-<listitem><para>Fix for <type>bytea</type> index lookups (Joe)</para></listitem>
-<listitem><para>Fix information schema for bit data types (Peter)</para></listitem>
-<listitem><para>Force zero_damaged_pages to be on during recovery from WAL</para></listitem>
-<listitem><para>Prevent some obscure cases of <quote>variable not in subplan target lists</quote></para></listitem>
-<listitem><para>Make <function>PQescapeBytea</function> and <function>byteaout</function> consistent with each other (Joe)</para></listitem>
-<listitem><para>Escape <type>bytea</type> output for bytes &gt; 0x7e(Joe)</para>
-<para>
- If different client encodings are used for <type>bytea</type> output and input, it
- is possible for <type>bytea</type> values to be corrupted by the differing
- encodings.  This fix escapes all bytes that might be affected.
-</para>
-</listitem>
-<listitem><para>Added missing <function>SPI_finish()</function> calls to dblink's <function>get_tuple_of_interest()</function> (Joe)</para></listitem>
-<listitem><para>New Czech FAQ</para></listitem>
-<listitem><para>Fix information schema view <literal>constraint_column_usage</literal> for foreign keys (Peter)</para></listitem>
-<listitem><para>ECPG fixes (Michael)</para></listitem>
-<listitem><para>Fix bug with multiple <literal>IN</literal> subqueries and joins in the subqueries (Tom)</para></listitem>
-<listitem><para>Allow <literal>COUNT('x')</literal> to work (Tom)</para></listitem>
-<listitem><para>Install ECPG include files for Informix compatibility into separate directory (Peter)</para>
-<para>
- Some names of ECPG include files for Informix compatibility conflicted with operating system include files.
- By installing them in their own directory, name conflicts have been reduced.
-</para>
-</listitem>
-<listitem><para>Fix SSL memory leak (Neil)</para>
-<para>
- This release fixes a bug in 7.4 where SSL didn't free all memory it allocated.
-</para>
-</listitem>
-<listitem><para>Prevent <filename>pg_service.conf</filename> from using service name as default dbname (Bruce)</para></listitem>
-<listitem><para>Fix local ident authentication on FreeBSD (Tom)</para></listitem>
-</itemizedlist>
-
- </sect2>
-</sect1>
-
-<sect1 id="release-7-4">
- <title>Release 7.4</title>
-
- <note>
-  <title>Release Date</title>
-  <simpara>2003-11-17</simpara>
- </note>
-
- <sect2>
-  <title>Overview</title>
-
-  <para>
-   Major changes in this release:
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term>
-     <literal>IN</literal> / <literal>NOT IN</literal> subqueries are
-     now much more efficient
-    </term>
-
-    <listitem>
-     <para>
-      In previous releases, <literal>IN</literal>/<literal>NOT
-      IN</literal> subqueries were joined to the upper query by
-      sequentially scanning the subquery looking for a match.  The
-      7.4 code uses the same sophisticated techniques used by
-      ordinary joins and so is much faster.  An
-      <literal>IN</literal> will now usually be as fast as or faster
-      than an equivalent <literal>EXISTS</literal> subquery; this
-      reverses the conventional wisdom that applied to previous
-      releases.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Improved <literal>GROUP BY</literal> processing by using hash buckets
-    </term>
-
-    <listitem>
-     <para>
-      In previous releases, rows to be grouped had to be sorted
-      first.  The 7.4 code can do <literal>GROUP BY</literal>
-      without sorting, by accumulating results into a hash table
-      with one entry per group.  It will still use the sort
-      technique, however, if the hash table is estimated to be too
-      large to fit in <varname>sort_mem</>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     New multikey hash join capability
-    </term>
-
-    <listitem>
-     <para>
-      In previous releases, hash joins could only occur on single
-      keys.  This release allows multicolumn hash joins.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Queries using the explicit <literal>JOIN</literal> syntax are
-     now better optimized
-    </term>
-
-    <listitem>
-     <para>
-      Prior releases evaluated queries using the explicit
-      <literal>JOIN</literal> syntax only in the order implied by
-      the syntax. 7.4 allows full optimization of these queries,
-      meaning the optimizer considers all possible join orderings
-      and chooses the most efficient.  Outer joins, however, must
-      still follow the declared ordering.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Faster and more powerful regular expression code
-    </term>
-
-    <listitem>
-     <para>
-      The entire regular expression module has been replaced with a
-      new version by Henry Spencer, originally written for Tcl.  The
-      code greatly improves performance and supports several flavors
-      of regular expressions.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Function-inlining for simple SQL functions
-    </term>
-
-    <listitem>
-     <para>
-      Simple SQL functions can now be inlined by including their SQL
-      in the main query.  This improves performance by eliminating
-      per-call overhead.  That means simple SQL functions now
-      behave like macros.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Full support for IPv6 connections and IPv6 address data types
-    </term>
-
-    <listitem>
-     <para>
-      Previous releases allowed only IPv4 connections, and the IP
-      data types only supported IPv4 addresses. This release adds
-      full IPv6 support in both of these areas.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Major improvements in SSL performance and reliability
-    </term>
-
-    <listitem>
-     <para>
-      Several people very familiar with the SSL API have overhauled
-      our SSL code to improve SSL key negotiation and error
-      recovery.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Make free space map efficiently reuse empty index pages,
-     and other free space management improvements
-    </term>
-
-    <listitem>
-     <para>
-      In previous releases, B-tree index pages that were left empty
-      because of deleted rows could only be reused by rows with
-      index values similar to the rows originally indexed on that
-      page. In 7.4, <command>VACUUM</command> records empty index
-      pages and allows them to be reused for any future index rows.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     SQL-standard information schema
-    </term>
-
-    <listitem>
-     <para>
-      The information schema provides a standardized and stable way
-      to access information about the schema objects defined in a
-      database.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Cursors conform more closely to the SQL standard
-    </term>
-
-    <listitem>
-     <para>
-      The commands <command>FETCH</command> and
-      <command>MOVE</command> have been overhauled to conform more
-      closely to the SQL standard.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Cursors can exist outside transactions
-    </term>
-
-    <listitem>
-     <para>
-      These cursors are also called holdable cursors.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     New client-to-server protocol
-    </term>
-
-    <listitem>
-     <para>
-      The new protocol adds error codes, more status information,
-      faster startup, better support for binary data transmission,
-      parameter values separated from SQL commands, prepared
-      statements available at the protocol level, and cleaner
-      recovery from <command>COPY</command> failures.  The older
-      protocol is still supported by both server and clients.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     <application>libpq</application> and
-     <application>ECPG</application> applications are now fully
-     thread-safe
-    </term>
-
-    <listitem>
-     <para>
-      While previous <application>libpq</application> releases
-      already supported threads, this release improves thread safety
-      by fixing some non-thread-safe code that was used during
-      database connection startup.  The <command>configure</command>
-      option <option>--enable-thread-safety</option> must be used to
-      enable this feature.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     New version of full-text indexing
-    </term>
-
-    <listitem>
-     <para>
-      A new full-text indexing suite is available in
-      <filename>contrib/tsearch2</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     New autovacuum tool
-    </term>
-
-    <listitem>
-     <para>
-      The new autovacuum tool in
-      <filename>contrib/autovacuum</filename> monitors the database
-      statistics tables for
-      <command>INSERT</command>/<command>UPDATE</command>/<command>DELETE</command>
-      activity and automatically vacuums tables when needed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Array handling has been improved and moved into the server core
-    </term>
-
-    <listitem>
-     <para>
-      Many array limitations have been removed, and arrays behave
-      more like fully-supported data types.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </sect2>
-
- <sect2>
-  <title>Migration to Version 7.4</title>
-
-  <para>
-   A dump/restore using <application>pg_dump</application> is
-   required for those wishing to migrate data from any previous
-   release.
-  </para>
-
-  <para>
-   Observe the following incompatibilities:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     The server-side autocommit setting was removed and
-     reimplemented in client applications and languages.
-     Server-side autocommit was causing too many problems with
-     languages and applications that wanted to control their own
-     autocommit behavior, so autocommit was removed from the server
-     and added to individual client APIs as appropriate.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Error message wording has changed substantially in this
-     release.  Significant effort was invested to make the messages
-     more consistent and user-oriented.  If your applications try to
-     detect different error conditions by parsing the error message,
-     you are strongly encouraged to use the new error code facility instead.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Inner joins using the explicit <literal>JOIN</literal> syntax
-     might behave differently because they are now better
-     optimized.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     A number of server configuration parameters have been renamed
-     for clarity, primarily those related to
-     logging.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <literal>FETCH 0</literal> or <literal>MOVE 0</literal> now
-     does nothing.  In prior releases, <literal>FETCH 0</literal>
-     would fetch all remaining rows, and <literal>MOVE 0</literal>
-     would move to the end of the cursor.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <command>FETCH</command> and <command>MOVE</command> now return
-     the actual number of rows fetched/moved, or zero if at the
-     beginning/end of the cursor.  Prior releases would return the
-     row count passed to the command, not the number of rows
-     actually fetched or moved.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <command>COPY</command> now can process files that use
-     carriage-return or carriage-return/line-feed end-of-line
-     sequences. Literal carriage-returns and line-feeds are no
-     longer accepted in data values; use <literal>\r</literal> and
-     <literal>\n</literal> instead.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Trailing spaces are now trimmed when converting from type
-     <type>char(<replaceable>n</>)</type> to
-     <type>varchar(<replaceable>n</>)</type> or <type>text</type>.
-     This is what most people always expected to happen anyway.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The data type <type>float(<replaceable>p</>)</type> now
-     measures <replaceable>p</> in binary digits, not decimal
-     digits.  The new behavior follows the SQL standard.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Ambiguous date values now must match the ordering specified by
-     the <varname>datestyle</varname> setting.  In prior releases, a
-     date specification of <literal>10/20/03</> was interpreted as a
-     date in October even if <varname>datestyle</> specified that
-     the day should be first.  7.4 will throw an error if a date
-     specification is invalid for the current setting of
-     <varname>datestyle</>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The functions <function>oidrand</function>,
-     <function>oidsrand</function>, and
-     <function>userfntest</function> have been removed.  These
-     functions were determined to be no longer useful.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     String literals specifying time-varying date/time values, such
-     as <literal>'now'</literal> or <literal>'today'</literal> will
-     no longer work as expected in column default expressions; they
-     now cause the time of the table creation to be the default, not
-     the time of the insertion.  Functions such as
-     <function>now()</>, <function>current_timestamp</>, or
-     <function>current_date</function> should be used instead.
-    </para>
-
-    <para>
-     In previous releases, there was special code so that strings
-     such as <literal>'now'</literal> were interpreted at
-     <command>INSERT</> time and not at table creation time, but
-     this work around didn't cover all cases.  Release 7.4 now
-     requires that defaults be defined properly using functions such
-     as <function>now()</> or <function>current_timestamp</>. These
-     will work in all situations.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The dollar sign (<literal>$</>) is no longer allowed in
-     operator names.  It can instead be a non-first character in
-     identifiers.  This was done to improve compatibility with other
-     database systems, and to avoid syntax problems when parameter
-     placeholders (<literal>$<replaceable>n</></>) are written
-     adjacent to operators.
-    </para>
-   </listitem>
-
-  </itemizedlist>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-
-  <para>
-   Below you will find a detailed account of the changes between
-   release 7.4 and the previous major release.
-  </para>
-
- <sect3>
-  <title>Server Operation Changes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Allow IPv6 server connections (Nigel Kukard, Johan Jordaan,
-     Bruce, Tom, Kurt Roeckx, Andrew Dunstan)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Fix SSL to handle errors cleanly (Nathan Mueller)
-    </para>
-    <para>
-     In prior releases, certain SSL API error reports were not
-     handled correctly.  This release fixes those problems.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     SSL protocol security and performance improvements (Sean Chittenden)
-    </para>
-    <para>
-     SSL key renegotiation was happening too frequently, causing poor
-     SSL performance.  Also, initial key handling was improved.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Print lock information when a deadlock is detected (Tom)
-    </para>
-    <para>
-     This allows easier debugging of deadlock situations.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Update <filename>/tmp</filename> socket modification times
-     regularly to avoid their removal (Tom)
-    </para>
-    <para>
-     This should help prevent <filename>/tmp</filename> directory
-     cleaner administration scripts from removing server socket
-     files.
-    </para>
-   </listitem>
-
-   <listitem><para>Enable PAM for Mac OS X (Aaron Hillegass)</para></listitem>
-
-   <listitem>
-    <para>Make B-tree indexes fully WAL-safe (Tom)</para>
-    <para>
-     In prior releases, under certain rare cases, a server crash
-     could cause B-tree indexes to become corrupt. This release
-     removes those last few rare cases.
-    </para>
-   </listitem>
-
-   <listitem><para>Allow B-tree index compaction and empty page reuse (Tom)</para></listitem>
-
-   <listitem>
-    <para>
-     Fix inconsistent index lookups during split of first root page (Tom)
-    </para>
-    <para>
-     In prior releases, when a single-page index split into two
-     pages, there was a brief period when another database session
-     could miss seeing an index entry.  This release fixes that rare
-     failure case.
-    </para>
-   </listitem>
-
-   <listitem><para>Improve free space map allocation logic (Tom)</para></listitem>
-
-   <listitem>
-    <para>Preserve free space information between server restarts (Tom)</para>
-    <para>
-     In prior releases, the free space map was not saved when the
-     postmaster was stopped, so newly started servers had no free
-     space information. This release saves the free space map, and
-     reloads it when the server is restarted.
-    </para>
-   </listitem>
-
-   <listitem><para>Add start time to <literal>pg_stat_activity</literal> (Neil)</para></listitem>
-   <listitem><para>New code to detect corrupt disk pages; erase with <varname>zero_damaged_pages</varname> (Tom)</para></listitem>
-   <listitem><para>New client/server protocol: faster, no username length limit, allow clean exit from <command>COPY</command> (Tom)</para></listitem>
-   <listitem><para>Add transaction status, table ID, column ID to client/server protocol (Tom)</para></listitem>
-   <listitem><para>Add binary I/O to client/server protocol (Tom)</para></listitem>
-   <listitem><para>Remove autocommit server setting; move to client applications (Tom)</para></listitem>
-   <listitem><para>New error message wording, error codes, and three levels of error detail (Tom, Joe, Peter)</para></listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>Performance Improvements</title>
-
-  <itemizedlist>
-   <listitem><para>Add hashing for <literal>GROUP BY</literal> aggregates (Tom)</para></listitem>
-   <listitem><para>Make nested-loop joins be smarter about multicolumn indexes (Tom)</para></listitem>
-   <listitem><para>Allow multikey hash joins (Tom)</para></listitem>
-   <listitem><para>Improve constant folding (Tom)</para></listitem>
-   <listitem><para>Add ability to inline simple SQL functions (Tom)</para></listitem>
-
-   <listitem>
-    <para>Reduce memory usage for queries using complex functions (Tom)</para>
-    <para>
-     In prior releases, functions returning allocated memory would
-     not free it until the query completed. This release allows the
-     freeing of function-allocated memory when the function call
-     completes, reducing the total memory used by functions.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Improve GEQO optimizer performance (Tom)</para>
-    <para>
-     This release fixes several inefficiencies in the way the GEQO optimizer
-     manages potential query paths.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow <literal>IN</>/<literal>NOT IN</> to be handled via hash
-     tables (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Improve <literal>NOT IN (<replaceable>subquery</>)</literal>
-     performance (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow most <literal>IN</literal> subqueries to be processed as
-     joins (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Pattern matching operations can use indexes regardless of
-     locale (Peter)
-    </para>
-    <para>
-     There is no way for non-ASCII locales to use the standard
-     indexes for <literal>LIKE</literal> comparisons. This release
-     adds a way to create a special index for
-     <literal>LIKE</literal>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow the postmaster to preload libraries using <varname>preload_libraries</varname> (Joe)</para>
-    <para>
-     For shared libraries that require a long time to load, this
-     option is available so the library can be preloaded in the
-     postmaster and inherited by all database sessions.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Improve optimizer cost computations, particularly for subqueries (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Avoid sort when subquery <literal>ORDER BY</literal> matches upper query (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Deduce that <literal>WHERE a.x = b.y AND b.y = 42</literal> also
-     means <literal>a.x = 42</literal> (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow hash/merge joins on complex joins (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow hash joins for more data types (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow join optimization of explicit inner joins, disable with
-     <varname>join_collapse_limit</varname> (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Add parameter <varname>from_collapse_limit</varname> to control
-     conversion of subqueries to joins (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Use faster and more powerful regular expression code from Tcl
-     (Henry Spencer, Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Use bit-mapped relation sets in the optimizer (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Improve connection startup time (Tom)</para>
-    <para>
-     The new client/server protocol requires fewer network packets to
-     start a database session.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Improve trigger/constraint performance (Stephan)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Improve speed of <literal>col IN (const, const, const, ...)</literal> (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Fix hash indexes which were broken in rare cases (Tom)
-    </para>
-   </listitem>
-
-   <listitem><para>Improve hash index concurrency and speed (Tom)</para>
-    <para>
-     Prior releases suffered from poor hash index performance,
-     particularly for high concurrency situations. This release fixes
-     that, and the development group is interested in reports
-     comparing B-tree and hash index performance.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Align shared buffers on 32-byte boundary for copy speed improvement (Manfred Spraul)</para>
-    <para>
-     Certain CPU's perform faster data copies when addresses are
-     32-byte aligned.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Data type <type>numeric</type> reimplemented for better performance (Tom)</para>
-    <para>
-     <type>numeric</type> used to be stored in base 100. The new code
-     uses base 10000, for significantly better performance.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>Server Configuration Changes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>Rename server parameter <varname>server_min_messages</> to <varname>log_min_messages</> (Bruce)</para>
-    <para>
-     This was done so most parameters that control the server logs
-     begin with <literal>log_</>.
-    </para>
-   </listitem>
-
-   <listitem><para>Rename <varname>show_*_stats</> to <varname>log_*_stats</> (Bruce)</para></listitem>
-   <listitem><para>Rename <varname>show_source_port</> to <varname>log_source_port</> (Bruce)</para></listitem>
-   <listitem><para>Rename <varname>hostname_lookup</> to <varname>log_hostname</> (Bruce)</para></listitem>
-
-   <listitem>
-    <para>Add <varname>checkpoint_warning</> to warn of excessive checkpointing (Bruce)</para>
-    <para>
-     In prior releases, it was difficult to determine if checkpoint
-     was happening too frequently. This feature adds a warning to the
-     server logs when excessive checkpointing happens.
-    </para>
-   </listitem>
-
-   <listitem><para>New read-only server parameters for localization (Tom)</para></listitem>
-
-   <listitem>
-    <para>
-     Change debug server log messages to output as <literal>DEBUG</>
-     rather than <literal>LOG</> (Bruce)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Prevent server log variables from being turned off by non-superusers (Bruce)</para>
-    <para>
-     This is a security feature so non-superusers cannot disable
-     logging that was enabled by the administrator.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <varname>log_min_messages</>/<varname>client_min_messages</> now
-     controls <varname>debug_*</> output (Bruce)
-    </para>
-    <para>
-     This centralizes client debug information so all debug output
-     can be sent to either the client or server logs.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Add Mac OS X Rendezvous server support (Chris Campbell)</para>
-    <para>
-     This allows Mac OS X hosts to query the network for available
-     <productname>PostgreSQL</productname> servers.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Add ability to print only slow statements using
-     <varname>log_min_duration_statement</varname>
-     (Christopher)
-    </para>
-    <para>
-     This is an often requested debugging feature that allows
-     administrators to see only slow queries in their server logs.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow <filename>pg_hba.conf</filename> to accept netmasks in CIDR format (Andrew Dunstan)</para>
-    <para>
-     This allows administrators to merge the host IP address and
-     netmask fields into a single CIDR field in <filename>pg_hba.conf</filename>.
-    </para>
-   </listitem>
-
-   <listitem><para>New read-only parameter <varname>is_superuser</varname> (Tom)</para></listitem>
-
-   <listitem>
-    <para>New parameter <varname>log_error_verbosity</varname> to control error detail (Tom)</para>
-    <para>
-     This works with the new error reporting feature to supply
-     additional error information like hints, file names and line
-     numbers.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para><literal>postgres --describe-config</literal> now dumps server config variables (Aizaz Ahmed, Peter)</para>
-    <para>
-     This option is useful for administration tools that need to know
-     the configuration variable names and their minimums, maximums,
-     defaults, and descriptions.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Add new columns in <literal>pg_settings</literal>:
-     <literal>context</>, <literal>type</>, <literal>source</>,
-     <literal>min_val</>, <literal>max_val</> (Joe)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Make default <varname>shared_buffers</> 1000 and
-     <varname>max_connections</> 100, if possible (Tom)
-    </para>
-    <para>
-     Prior versions defaulted to 64 shared buffers so <productname>PostgreSQL</productname>
-     would start on even very old systems. This release tests the
-     amount of shared memory allowed by the platform and selects more
-     reasonable default values if possible.  Of course, users are
-     still encouraged to evaluate their resource load and size
-     <varname>shared_buffers</varname> accordingly.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     New <filename>pg_hba.conf</filename> record type
-     <literal>hostnossl</> to prevent SSL connections (Jon
-     Jensen)
-    </para>
-    <para>
-     In prior releases, there was no way to prevent SSL connections
-     if both the client and server supported SSL. This option allows
-     that capability.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Remove parameter <varname>geqo_random_seed</varname>
-     (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Add server parameter <varname>regex_flavor</varname> to control regular expression processing (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Make <command>pg_ctl</command> better handle nonstandard ports (Greg)
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>Query Changes</title>
-
-  <itemizedlist>
-   <listitem><para>New SQL-standard information schema (Peter)</para></listitem>
-   <listitem><para>Add read-only transactions (Peter)</para></listitem>
-   <listitem><para>Print key name and value in foreign-key violation messages (Dmitry Tkach)</para></listitem>
-
-   <listitem>
-    <para>Allow users to see their own queries in <literal>pg_stat_activity</literal> (Kevin Brown)</para>
-    <para>
-     In prior releases, only the superuser could see query strings
-     using <literal>pg_stat_activity</literal>. Now ordinary users
-     can see their own query strings.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Fix aggregates in subqueries to match SQL standard (Tom)</para>
-    <para>
-     The SQL standard says that an aggregate function appearing
-     within a nested subquery belongs to the outer query if its
-     argument contains only outer-query variables.  Prior
-     <productname>PostgreSQL</productname> releases did not handle
-     this fine point correctly.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Add option to prevent auto-addition of tables referenced in query (Nigel J. Andrews)</para>
-    <para>
-     By default, tables mentioned in the query are automatically
-     added to the <literal>FROM</> clause if they are not already
-     there.  This is compatible with historic
-     <productname>POSTGRES</productname> behavior but is contrary to
-     the SQL standard.  This option allows selecting
-     standard-compatible behavior.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow <literal>UPDATE ... SET col = DEFAULT</literal> (Rod)</para>
-    <para>
-     This allows <command>UPDATE</command> to set a column to its
-     declared default value.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow expressions to be used in <literal>LIMIT</>/<literal>OFFSET</> (Tom)</para>
-    <para>
-     In prior releases, <literal>LIMIT</>/<literal>OFFSET</> could
-     only use constants, not expressions.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Implement <literal>CREATE TABLE AS EXECUTE</literal> (Neil, Peter)</para>
-   </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>Object Manipulation Changes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>Make <command>CREATE SEQUENCE</command> grammar more conforming to SQL:2003 (Neil)</para>
-   </listitem>
-
-   <listitem>
-    <para>Add statement-level triggers (Neil)</para>
-    <para>
-     While this allows a trigger to fire at the end of a statement,
-     it does not allow the trigger to access all rows modified by the
-     statement.  This capability is planned for a future release.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Add check constraints for domains (Rod)</para>
-    <para>
-     This greatly increases the usefulness of domains by allowing
-     them to use check constraints.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Add <command>ALTER DOMAIN</command> (Rod)</para>
-    <para>
-     This allows manipulation of existing domains.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Fix several zero-column table bugs (Tom)</para>
-    <para>
-     <productname>PostgreSQL</productname> supports zero-column tables. This fixes various bugs
-     that occur when using such tables.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Have <literal>ALTER TABLE ... ADD PRIMARY KEY</literal> add not-null constraint (Rod)</para>
-    <para>
-     In prior releases, <literal>ALTER TABLE ... ADD
-     PRIMARY</literal> would add a unique index, but not a not-null
-     constraint.  That is fixed in this release.
-    </para>
-   </listitem>
-
-   <listitem><para>Add <literal>ALTER TABLE ... WITHOUT OIDS</literal> (Rod)</para>
-    <para>
-     This allows control over whether new and updated rows will have
-     an OID column.  This is most useful for saving storage space.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Add <literal>ALTER SEQUENCE</literal> to modify minimum, maximum,
-     increment, cache, cycle values (Rod)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Add <literal>ALTER TABLE ... CLUSTER ON</literal> (Alvaro Herrera)</para>
-    <para>
-     This command is used by <command>pg_dump</command> to record the
-     cluster column for each table previously clustered. This
-     information is used by database-wide cluster to cluster all
-     previously clustered tables.
-    </para>
-   </listitem>
-
-   <listitem><para>Improve automatic type casting for domains (Rod, Tom)</para></listitem>
-   <listitem><para>Allow dollar signs in identifiers, except as first character (Tom)</para></listitem>
-   <listitem><para>Disallow dollar signs in operator names, so <literal>x=$1</> works (Tom)</para></listitem>
-
-   <listitem>
-    <para>
-     Allow copying table schema using <literal>LIKE
-     <replaceable>subtable</replaceable></literal>, also SQL:2003
-     feature <literal>INCLUDING DEFAULTS</literal> (Rod)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Add <literal>WITH GRANT OPTION</literal> clause to
-     <command>GRANT</command> (Peter)
-    </para>
-    <para>
-     This enabled <command>GRANT</command> to give other users the
-     ability to grant privileges on a object.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>Utility Command Changes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>Add <literal>ON COMMIT</literal> clause to <command>CREATE TABLE</command> for temporary tables (Gavin)</para>
-    <para>
-     This adds the ability for a table to be dropped or all rows
-     deleted on transaction commit.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow cursors outside transactions using <literal>WITH HOLD</literal> (Neil)</para>
-    <para>
-     In previous releases, cursors were removed at the end of the
-     transaction that created them. Cursors can now be created with
-     the <literal>WITH HOLD</literal> option, which allows them to
-     continue to be accessed after the creating transaction has
-     committed.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para><literal>FETCH 0</literal> and <literal>MOVE 0 </literal> now do nothing (Bruce)</para>
-    <para>
-     In previous releases, <literal>FETCH 0</literal> fetched all
-     remaining rows, and <literal>MOVE 0</literal> moved to the end
-     of the cursor.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Cause <command>FETCH</command> and <command>MOVE</command> to
-     return the number of rows fetched/moved, or zero if at the
-     beginning/end of cursor, per SQL standard (Bruce)
-    </para>
-    <para>
-     In prior releases, the row count returned by
-     <command>FETCH</command> and <command>MOVE</command> did not
-     accurately reflect the number of rows processed.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Properly handle <literal>SCROLL</literal> with cursors, or
-    report an error (Neil)</para>
-    <para>
-     Allowing random access (both forward and backward scrolling) to
-     some kinds of queries cannot be done without some additional
-     work. If <literal>SCROLL</literal> is specified when the cursor
-     is created, this additional work will be performed. Furthermore,
-     if the cursor has been created with <literal>NO SCROLL</literal>,
-     no random access is allowed.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Implement SQL-compatible options <literal>FIRST</>,
-     <literal>LAST</>, <literal>ABSOLUTE <replaceable>n</></>,
-     <literal>RELATIVE <replaceable>n</></> for
-     <command>FETCH</command> and <command>MOVE</command> (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow <command>EXPLAIN</command> on <command>DECLARE CURSOR</command> (Tom)</para>
-   </listitem>
-
-   <listitem>
-    <para>Allow <command>CLUSTER</command> to use index marked as pre-clustered by default (Alvaro Herrera)</para>
-   </listitem>
-
-   <listitem>
-    <para>Allow <command>CLUSTER</command> to cluster all tables (Alvaro Herrera)</para>
-    <para>
-     This allows all previously clustered tables in a database to be
-     reclustered with a single command.
-    </para>
-   </listitem>
-
-   <listitem><para>Prevent <command>CLUSTER</command> on partial indexes (Tom)</para></listitem>
-
-   <listitem><para>Allow DOS and Mac line-endings in <command>COPY</> files (Bruce)</para></listitem>
-
-   <listitem>
-    <para>
-     Disallow literal carriage return as a data value,
-     backslash-carriage-return and <literal>\r</> are still allowed
-     (Bruce)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para><command>COPY</> changes (binary, <literal>\.</>) (Tom)</para>
-   </listitem>
-
-   <listitem>
-    <para>Recover from <command>COPY</command> failure cleanly (Tom)</para>
-   </listitem>
-
-   <listitem>
-    <para>Prevent possible memory leaks in <command>COPY</command> (Tom)</para>
-   </listitem>
-
-   <listitem>
-    <para>Make <command>TRUNCATE</command> transaction-safe (Rod)</para>
-    <para>
-     <command>TRUNCATE</command> can now be used inside a
-     transaction. If the transaction aborts, the changes made by the
-     <command>TRUNCATE</command> are automatically rolled back.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow prepare/bind of utility commands like
-     <command>FETCH</command> and <command>EXPLAIN</command> (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Add <command>EXPLAIN EXECUTE</command> (Neil)</para>
-   </listitem>
-
-   <listitem>
-    <para>Improve <command>VACUUM</command> performance on indexes by reducing WAL traffic (Tom)</para>
-   </listitem>
-
-   <listitem>
-    <para>Functional indexes have been generalized into indexes on expressions (Tom)</para>
-    <para>
-     In prior releases, functional indexes only supported a simple
-     function applied to one or more column names.  This release
-     allows any type of scalar expression.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Have <command>SHOW TRANSACTION ISOLATION</command> match input
-     to <command>SET TRANSACTION ISOLATION</command>
-     (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-      Have <command>COMMENT ON DATABASE</command> on nonlocal
-      database generate a warning, rather than an error (Rod)
-     </para>
-
-    <para>
-     Database comments are stored in database-local tables so
-     comments on a database have to be stored in each database.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Improve reliability of <command>LISTEN</>/<command>NOTIFY</> (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow <command>REINDEX</command> to reliably reindex nonshared system catalog indexes (Tom)</para>
-    <para>
-     This allows system tables to be reindexed without the
-     requirement of a standalone session, which was necessary in
-     previous releases. The only tables that now require a standalone
-     session for reindexing are the global system tables
-     <literal>pg_database</>, <literal>pg_shadow</>, and
-     <literal>pg_group</>.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>Data Type and Function Changes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     New server parameter <varname>extra_float_digits</varname> to
-     control precision display of floating-point numbers (Pedro
-     Ferreira, Tom)
-    </para>
-    <para>
-     This controls output precision which was causing regression
-     testing problems.
-    </para>
-   </listitem>
-
-   <listitem><para>Allow <literal>+1300</literal> as a numeric time-zone specifier, for FJST (Tom)</para></listitem>
-
-   <listitem>
-    <para>
-     Remove rarely used functions <function>oidrand</>,
-     <function>oidsrand</>, and <function>userfntest</> functions
-     (Neil)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Add <function>md5()</> function to main server, already in <filename>contrib/pgcrypto</filename> (Joe)</para>
-    <para>
-     An MD5 function was frequently requested. For more complex
-     encryption capabilities, use
-     <filename>contrib/pgcrypto</filename>.
-    </para>
-   </listitem>
-
-   <listitem><para>Increase date range of <type>timestamp</type> (John Cochran)</para></listitem>
-
-   <listitem>
-    <para>
-     Change <literal>EXTRACT(EPOCH FROM timestamp)</literal> so
-     <type>timestamp without time zone</type> is assumed to be in
-     local time, not GMT (Tom)
-    </para>
-   </listitem>
-
-   <listitem><para>Trap division by zero in case the operating system doesn't prevent it (Tom)</para></listitem>
-   <listitem><para>Change the <type>numeric</type> data type internally to base 10000 (Tom)</para></listitem>
-   <listitem><para>New <function>hostmask()</function> function (Greg Wickham)</para></listitem>
-   <listitem><para>Fixes for <function>to_char()</function> and <function>to_timestamp()</function> (Karel)</para></listitem>
-
-   <listitem>
-    <para>
-     Allow functions that can take any argument data type and return
-     any data type, using <type>anyelement</type> and
-     <type>anyarray</type> (Joe)
-    </para>
-    <para>
-     This allows the creation of functions that can work with any
-     data type.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Arrays can now be specified as <literal>ARRAY[1,2,3]</literal>,
-     <literal>ARRAY[['a','b'],['c','d']]</literal>, or
-     <literal>ARRAY[ARRAY[ARRAY[2]]]</literal> (Joe)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow proper comparisons for arrays, including <literal>ORDER
-     BY</literal> and <literal>DISTINCT</literal> support
-     (Joe)
-    </para>
-   </listitem>
-
-   <listitem><para>Allow indexes on array columns (Joe)</para></listitem>
-   <listitem><para>Allow array concatenation with <literal>||</literal> (Joe)</para></listitem>
-
-   <listitem>
-    <para>
-     Allow <literal>WHERE</literal> qualification
-     <literal><replaceable>expr</> <replaceable>op</> ANY/SOME/ALL
-     (<replaceable>array_expr</>)</literal> (Joe)
-    </para>
-    <para>
-     This allows arrays to behave like a list of values, for purposes
-     like <literal>SELECT * FROM tab WHERE col IN
-     (array_val)</literal>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     New array functions <function>array_append</>,
-     <function>array_cat</>, <function>array_lower</>,
-     <function>array_prepend</>, <function>array_to_string</>,
-     <function>array_upper</>, <function>string_to_array</> (Joe)
-    </para>
-   </listitem>
-
-   <listitem><para>Allow user defined aggregates to use polymorphic functions (Joe)</para></listitem>
-   <listitem><para>Allow assignments to empty arrays (Joe)</para></listitem>
-
-   <listitem>
-    <para>
-     Allow 60 in seconds fields of <type>time</type>,
-     <type>timestamp</type>, and <type>interval</type> input values
-     (Tom)
-    </para>
-    <para>
-     Sixty-second values are needed for leap seconds.
-    </para>
-   </listitem>
-
-   <listitem><para>Allow <type>cidr</type> data type to be cast to <type>text</type> (Tom)</para></listitem>
-
-   <listitem><para>Disallow invalid time zone names in SET TIMEZONE</para></listitem>
-
-   <listitem>
-    <para>
-     Trim trailing spaces when <type>char</type> is cast to
-     <type>varchar</> or <type>text</> (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Make <type>float(<replaceable>p</>)</> measure the precision
-     <replaceable>p</> in binary digits, not decimal digits
-     (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Add IPv6 support to the <type>inet</type> and <type>cidr</type> data types (Michael Graff)</para>
-   </listitem>
-
-   <listitem>
-    <para>Add <function>family()</function> function to report whether address is IPv4 or IPv6 (Michael Graff)</para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Have <literal>SHOW datestyle</literal> generate output similar
-     to that used by <literal>SET datestyle</literal> (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Make <literal>EXTRACT(TIMEZONE)</literal> and <literal>SET/SHOW
-     TIME ZONE</literal> follow the SQL convention for the sign of
-     time zone offsets, i.e., positive is east from UTC (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Fix <literal>date_trunc('quarter', ...)</literal> (B&ouml;jthe Zolt&aacute;n)</para>
-    <para>
-     Prior releases returned an incorrect value for this function call.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Make <function>initcap()</function> more compatible with Oracle (Mike Nolan)</para>
-    <para>
-     <function>initcap()</function> now uppercases a letter appearing
-     after any non-alphanumeric character, rather than only after
-     whitespace.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow only <varname>datestyle</varname> field order for date values not in ISO-8601 format (Greg)</para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Add new <varname>datestyle</varname> values <literal>MDY</>,
-     <literal>DMY</>, and <literal>YMD</> to set input field order;
-     honor <literal>US</> and <literal>European</> for backward
-     compatibility (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     String literals like <literal>'now'</literal> or
-     <literal>'today'</literal> will no longer work as a column
-     default. Use functions such as <function>now()</function>,
-     <function>current_timestamp</function> instead.  (change
-     required for prepared statements) (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Treat NaN as larger than any other value in <function>min()</>/<function>max()</> (Tom)</para>
-    <para>
-     NaN was already sorted after ordinary numeric values for most
-     purposes, but <function>min()</> and <function>max()</> didn't
-     get this right.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Prevent interval from suppressing <literal>:00</literal>
-    seconds display</para>
-   </listitem>
-
-   <listitem>
-    <para>
-     New functions <function>pg_get_triggerdef(prettyprint)</function>
-     and <function>pg_conversion_is_visible()</function> (Christopher)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow time to be specified as <literal>040506</> or <literal>0405</> (Tom)</para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Input date order must now be <literal>YYYY-MM-DD</literal> (with 4-digit year) or
-     match <varname>datestyle</varname>
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Make <function>pg_get_constraintdef</function> support
-     unique, primary-key, and check constraints (Christopher)
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>Server-Side Language Changes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Prevent PL/pgSQL crash when <literal>RETURN NEXT</literal> is
-     used on a zero-row record variable (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Make PL/Python's <function>spi_execute</function> interface
-     handle null values properly (Andrew Bosma)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow PL/pgSQL to declare variables of composite types without <literal>%ROWTYPE</literal> (Tom)</para>
-   </listitem>
-
-   <listitem>
-    <para>Fix PL/Python's <function>_quote()</function> function to handle big integers</para>
-   </listitem>
-
-   <listitem>
-    <para>Make PL/Python an untrusted language, now called <literal>plpythonu</literal> (Kevin Jacobs, Tom)</para>
-    <para>
-     The Python language no longer supports a restricted execution
-     environment, so the trusted version of PL/Python was removed. If
-     this situation changes, a version of PL/Python that can be used
-     by non-superusers will be readded.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow polymorphic PL/pgSQL functions (Joe, Tom)</para>
-   </listitem>
-
-   <listitem>
-    <para>Allow polymorphic SQL functions (Joe)</para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Improved compiled function caching mechanism in PL/pgSQL with
-     full support for polymorphism (Joe)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Add new parameter <literal>$0</> in PL/pgSQL representing the
-     function's actual return type (Joe)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow PL/Tcl and PL/Python to use the same trigger on multiple tables (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Fixed PL/Tcl's <function>spi_prepare</function> to accept fully
-     qualified type names in the parameter type list
-     (Jan)
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>psql Changes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>Add <literal>\pset pager always</literal> to always use pager (Greg)</para>
-    <para>
-     This forces the pager to be used even if the number of rows is
-     less than the screen height.  This is valuable for rows that
-     wrap across several screen rows.
-    </para>
-   </listitem>
-
-   <listitem><para>Improve tab completion (Rod, Ross Reedstrom, Ian Barwick)</para></listitem>
-   <listitem><para>Reorder <literal>\?</> help into groupings (Harald Armin Massa, Bruce)</para></listitem>
-   <listitem><para>Add backslash commands for listing schemas, casts, and conversions (Christopher)</para></listitem>
-
-   <listitem>
-    <para>
-     <command>\encoding</> now changes based on the server parameter
-     <varname>client_encoding</varname> (Tom)
-    </para>
-    <para>
-     In previous versions, <command>\encoding</command> was not aware
-     of encoding changes made using <literal>SET
-     client_encoding</literal>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Save editor buffer into readline history (Ross)</para>
-    <para>
-     When <command>\e</> is used to edit a query, the result is saved
-     in the readline history for retrieval using the up arrow.
-    </para>
-   </listitem>
-
-   <listitem><para>Improve <command>\d</command> display (Christopher)</para></listitem>
-   <listitem><para>Enhance HTML mode to be more standards-conforming (Greg)</para></listitem>
-
-   <listitem>
-    <para>New <command>\set AUTOCOMMIT off</command> capability (Tom)</para>
-    <para>
-     This takes the place of the removed server parameter <varname>autocommit</varname>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>New <command>\set VERBOSITY</command> to control error detail (Tom)</para>
-    <para>
-     This controls the new error reporting details.
-    </para>
-   </listitem>
-
-   <listitem><para>New prompt escape sequence <literal>%x</literal> to show transaction status (Tom)</para></listitem>
-   <listitem><para>Long options for <application>psql</application> are now available on all platforms</para></listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>pg_dump Changes</title>
-
-  <itemizedlist>
-   <listitem><para>Multiple pg_dump fixes, including tar format and large objects</para></listitem>
-   <listitem><para>Allow pg_dump to dump specific schemas (Neil)</para></listitem>
-
-   <listitem>
-    <para>Make pg_dump preserve column storage characteristics (Christopher)</para>
-    <para>
-     This preserves <literal>ALTER TABLE ... SET STORAGE</literal> information.
-    </para>
-   </listitem>
-
-   <listitem><para>Make pg_dump preserve <command>CLUSTER</command> characteristics (Christopher)</para></listitem>
-
-   <listitem>
-    <para>
-     Have pg_dumpall use <command>GRANT</>/<command>REVOKE</> to dump database-level privileges (Tom)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow pg_dumpall to support the options <option>-a</>,
-     <option>-s</>, <option>-x</> of pg_dump (Tom)
-    </para>
-   </listitem>
-
-   <listitem><para>Prevent pg_dump from lowercasing identifiers specified on the command line (Tom)</para></listitem>
-
-   <listitem>
-    <para>
-     pg_dump options <option>--use-set-session-authorization</option>
-     and <option>--no-reconnect</option> now do nothing, all dumps
-     use <command>SET SESSION AUTHORIZATION</command>
-    </para>
-    <para>
-     pg_dump no longer reconnects to switch users, but instead always
-     uses <command>SET SESSION AUTHORIZATION</command>. This will
-     reduce password prompting during restores.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Long options for <application>pg_dump</application> are now available on all platforms</para>
-    <para>
-     <productname>PostgreSQL</productname> now includes its own
-     long-option processing routines.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>libpq Changes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Add function <function>PQfreemem</function> for freeing memory on
-     Windows, suggested for <command>NOTIFY</command> (Bruce)
-    </para>
-    <para>
-     Windows requires that memory allocated in a library be freed by
-     a function in the same library, hence
-     <function>free()</function> doesn't work for freeing memory
-     allocated by libpq. <function>PQfreemem</function> is the proper
-     way to free libpq memory, especially on Windows, and is
-     recommended for other platforms as well.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Document service capability, and add sample file (Bruce)</para>
-    <para>
-     This allows clients to look up connection information in a
-     central file on the client machine.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Make <function>PQsetdbLogin</function> have the same defaults as
-     <function>PQconnectdb</function> (Tom)
-    </para>
-   </listitem>
-
-   <listitem><para>Allow libpq to cleanly fail when result sets are too large (Tom)</para></listitem>
-
-   <listitem>
-    <para>
-     Improve performance of function <function>PQunescapeBytea</function> (Ben Lamb)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow thread-safe libpq with <filename>configure</filename>
-     option <option>--enable-thread-safety</option> (Lee Kindness,
-     Philip Yarra)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow function <function>pqInternalNotice</function> to accept a
-     format string and arguments instead of just a preformatted
-     message (Tom, Sean Chittenden)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Control SSL negotiation with <literal>sslmode</literal> values
-     <literal>disable</literal>, <literal>allow</literal>,
-     <literal>prefer</literal>, and <literal>require</literal> (Jon
-     Jensen)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Allow new error codes and levels of text (Tom)</para>
-   </listitem>
-
-   <listitem>
-    <para>Allow access to the underlying table and column of a query result (Tom)</para>
-    <para>
-     This is helpful for query-builder applications that want to know
-     the underlying table and column names associated with a specific
-     result set.
-    </para>
-   </listitem>
-
-   <listitem><para>Allow access to the current transaction status (Tom)</para></listitem>
-   <listitem><para>Add ability to pass binary data directly to the server (Tom)</para></listitem>
-
-   <listitem>
-    <para>
-     Add function <function>PQexecPrepared</function> and
-     <function>PQsendQueryPrepared</function> functions which perform
-     bind/execute of previously prepared statements (Tom)
-     </para>
-    </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>JDBC Changes</title>
-
-  <itemizedlist>
-   <listitem><para>Allow <function>setNull</function> on updateable result sets</para></listitem>
-   <listitem><para>Allow <function>executeBatch</function> on a prepared statement (Barry)</para></listitem>
-   <listitem><para>Support SSL connections (Barry)</para></listitem>
-   <listitem><para>Handle schema names in result sets (Paul Sorenson)</para></listitem>
-   <listitem><para>Add refcursor support (Nic Ferrier)</para></listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>Miscellaneous Interface Changes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>Prevent possible memory leak or core dump during libpgtcl shutdown (Tom)</para>
-   </listitem>
-   <listitem>
-    <para>Add Informix compatibility to ECPG (Michael)</para>
-    <para>
-     This allows ECPG to process embedded C programs that were
-     written using certain Informix extensions.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Add type <type>decimal</type> to ECPG that is fixed length, for Informix (Michael)</para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Allow thread-safe embedded SQL programs with
-     <filename>configure</filename> option
-     <option>--enable-thread-safety</option> (Lee Kindness, Bruce)
-    </para>
-    <para>
-     This allows multiple threads to access the database at the same
-     time.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>Moved Python client PyGreSQL to <ulink url="http://www.pygresql.org"></ulink> (Marc)</para>
-   </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>Source Code Changes</title>
-
-  <itemizedlist>
-   <listitem><para>Prevent need for separate platform geometry regression result files (Tom)</para></listitem>
-   <listitem><para>Improved PPC locking primitive (Reinhard Max)</para></listitem>
-   <listitem><para>New function <function>palloc0</function> to allocate and clear memory (Bruce)</para></listitem>
-   <listitem><para>Fix locking code for s390x CPU (64-bit) (Tom)</para></listitem>
-   <listitem><para>Allow OpenBSD to use local ident credentials (William Ahern)</para></listitem>
-   <listitem><para>Make query plan trees read-only to executor (Tom)</para></listitem>
-   <listitem><para>Add Darwin startup scripts (David Wheeler)</para></listitem>
-   <listitem><para>Allow libpq to compile with Borland C++ compiler (Lester Godwin, Karl Waclawek)</para></listitem>
-   <listitem><para>Use our own version of <function>getopt_long()</function> if needed (Peter)</para></listitem>
-   <listitem><para>Convert administration scripts to C (Peter)</para></listitem>
-   <listitem><para> Bison &gt;= 1.85 is now required to build the <productname>PostgreSQL</> grammar, if building from CVS</para></listitem>
-   <listitem><para>Merge documentation into one book (Peter)</para></listitem>
-   <listitem><para>Add Windows compatibility functions (Bruce)</para></listitem>
-   <listitem><para>Allow client interfaces to compile under MinGW (Bruce)</para></listitem>
-   <listitem><para>New <function>ereport()</function> function for error reporting (Tom)</para></listitem>
-   <listitem><para>Support Intel compiler on Linux (Peter)</para></listitem>
-   <listitem><para>Improve Linux startup scripts (Slawomir Sudnik, Darko Prenosil)</para></listitem>
-   <listitem><para>Add support for AMD Opteron and Itanium (Jeffrey W. Baker, Bruce)</para></listitem>
-   <listitem>
-    <para>Remove <option>--enable-recode</option> option from <command>configure</command></para>
-    <para>
-     This was no longer needed now that we have <command>CREATE CONVERSION</command>.
-    </para>
-   </listitem>
-   <listitem>
-    <para>Generate a compile error if spinlock code is not found (Bruce)</para>
-    <para>
-     Platforms without spinlock code will now fail to compile, rather
-     than silently using semaphores. This failure can be disabled
-     with a new <command>configure</command> option.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect3>
-
- <sect3>
-  <title>Contrib Changes</title>
-
-  <itemizedlist>
-   <listitem><para>Change dbmirror license to BSD</para></listitem>
-   <listitem><para>Improve earthdistance (Bruno Wolff III)</para></listitem>
-   <listitem><para>Portability improvements to pgcrypto (Marko Kreen)</para></listitem>
-   <listitem><para>Prevent crash in xml (John Gray, Michael Richards)</para></listitem>
-   <listitem><para>Update oracle</para></listitem>
-   <listitem><para>Update mysql</para></listitem>
-   <listitem><para>Update cube (Bruno Wolff III)</para></listitem>
-   <listitem><para>Update earthdistance to use cube (Bruno Wolff III)</para></listitem>
-   <listitem><para>Update btree_gist (Oleg)</para></listitem>
-   <listitem><para>New tsearch2 full-text search module (Oleg, Teodor)</para></listitem>
-   <listitem><para>Add hash-based crosstab function to tablefuncs (Joe)</para></listitem>
-   <listitem><para>Add serial column to order <function>connectby()</> siblings in tablefuncs (Nabil Sayegh,Joe)</para></listitem>
-   <listitem><para>Add named persistent connections to dblink (Shridhar Daithanka)</para></listitem>
-   <listitem><para>New pg_autovacuum allows automatic <command>VACUUM</command> (Matthew T. O'Connor)</para></listitem>
-   <listitem><para>Make pgbench honor environment variables <envar>PGHOST</>, <envar>PGPORT</>, <envar>PGUSER</> (Tatsuo)</para></listitem>
-   <listitem><para>Improve intarray (Teodor Sigaev)</para></listitem>
-   <listitem><para>Improve pgstattuple (Rod)</para></listitem>
-   <listitem><para>Fix bug in <function>metaphone()</function> in fuzzystrmatch</para></listitem>
-   <listitem><para>Improve adddepend (Rod)</para></listitem>
-   <listitem><para>Update spi/timetravel (B&ouml;jthe Zolt&aacute;n)</para></listitem>
-   <listitem><para>Fix dbase <option>-s</> option and improve non-ASCII handling (Thomas Behr, M&aacute;rcio Smiderle)</para></listitem>
-   <listitem><para>Remove array module because features now included by default (Joe)</para></listitem>
-  </itemizedlist>
- </sect3>
- </sect2>
-</sect1>
diff --git a/doc-xc/src/sgml/release-8.0.sgmlin b/doc-xc/src/sgml/release-8.0.sgmlin
deleted file mode 100644
index 469a76d893..0000000000
--- a/doc-xc/src/sgml/release-8.0.sgmlin
+++ /dev/null
@@ -1,5421 +0,0 @@
-<!-- doc/src/sgml/release-8.0.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-8-0-26">
-  <title>Release 8.0.26</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2010-10-04</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.25.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <para>
-   This is expected to be the last <productname>PostgreSQL</> release
-   in the 8.0.X series.  Users are encouraged to update to a newer
-   release branch soon.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.26</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you are upgrading from a version earlier than 8.0.22,
-    see the release notes for 8.0.22.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Use a separate interpreter for each calling SQL userid in PL/Perl and
-      PL/Tcl (Tom Lane)
-     </para>
-
-     <para>
-      This change prevents security problems that can be caused by subverting
-      Perl or Tcl code that will be executed later in the same session under
-      another SQL user identity (for example, within a <literal>SECURITY
-      DEFINER</> function).  Most scripting languages offer numerous ways that
-      that might be done, such as redefining standard functions or operators
-      called by the target function.  Without this change, any SQL user with
-      Perl or Tcl language usage rights can do essentially anything with the
-      SQL privileges of the target function's owner.
-     </para>
-
-     <para>
-      The cost of this change is that intentional communication among Perl
-      and Tcl functions becomes more difficult.  To provide an escape hatch,
-      PL/PerlU and PL/TclU functions continue to use only one interpreter
-      per session.  This is not considered a security issue since all such
-      functions execute at the trust level of a database superuser already.
-     </para>
-
-     <para>
-      It is likely that third-party procedural languages that claim to offer
-      trusted execution have similar security issues.  We advise contacting
-      the authors of any PL you are depending on for security-critical
-      purposes.
-     </para>
-
-     <para>
-      Our thanks to Tim Bunce for pointing out this issue (CVE-2010-3433).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible crashes in <function>pg_get_expr()</> by disallowing
-      it from being called with an argument that is not one of the system
-      catalog columns it's intended to be used with
-      (Heikki Linnakangas, Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>cannot handle unplanned sub-select</quote> error (Tom Lane)
-     </para>
-
-     <para>
-      This occurred when a sub-select contains a join alias reference that
-      expands into an expression containing another sub-select.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Defend against functions returning setof record where not all the
-      returned rows are actually of the same rowtype (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Take care to fsync the contents of lockfiles (both
-      <filename>postmaster.pid</> and the socket lockfile) while writing them
-      (Tom Lane)
-     </para>
-
-     <para>
-      This omission could result in corrupted lockfile contents if the
-      machine crashes shortly after postmaster start.  That could in turn
-      prevent subsequent attempts to start the postmaster from succeeding,
-      until the lockfile is manually removed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid recursion while assigning XIDs to heavily-nested
-      subtransactions (Andres Freund, Robert Haas)
-     </para>
-
-     <para>
-      The original coding could result in a crash if there was limited
-      stack space.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <varname>log_line_prefix</>'s <literal>%i</> escape,
-      which could produce junk early in backend startup (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible data corruption in <command>ALTER TABLE ... SET
-      TABLESPACE</> when archiving is enabled (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow <command>CREATE DATABASE</> and <command>ALTER DATABASE ... SET
-      TABLESPACE</> to be interrupted by query-cancel (Guillaume Lelarge)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In PL/Python, defend against null pointer results from
-      <function>PyCObject_AsVoidPtr</> and <function>PyCObject_FromVoidPtr</>
-      (Peter Eisentraut)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <filename>contrib/dblink</>'s handling of tables containing
-      dropped columns (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix connection leak after <quote>duplicate connection name</quote>
-      errors in <filename>contrib/dblink</> (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/dblink</> to handle connection names longer than
-      62 bytes correctly (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update build infrastructure and documentation to reflect the source code
-      repository's move from CVS to Git (Magnus Hagander and others)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010l
-      for DST law changes in Egypt and Palestine; also historical corrections
-      for Finland.
-     </para>
-
-     <para>
-      This change also adds new names for two Micronesian timezones:
-      Pacific/Chuuk is now preferred over Pacific/Truk (and the preferred
-      abbreviation is CHUT not TRUT) and Pacific/Pohnpei is preferred over
-      Pacific/Ponape.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-25">
-  <title>Release 8.0.25</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2010-05-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.24.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <para>
-   The <productname>PostgreSQL</> community will stop releasing updates
-   for the 8.0.X release series in July 2010.
-   Users are encouraged to update to a newer release branch soon.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.25</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you are upgrading from a version earlier than 8.0.22,
-    see the release notes for 8.0.22.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Enforce restrictions in <literal>plperl</> using an opmask applied to
-      the whole interpreter, instead of using <filename>Safe.pm</>
-      (Tim Bunce, Andrew Dunstan)
-     </para>
-
-     <para>
-      Recent developments have convinced us that <filename>Safe.pm</> is too
-      insecure to rely on for making <literal>plperl</> trustable.  This
-      change removes use of <filename>Safe.pm</> altogether, in favor of using
-      a separate interpreter with an opcode mask that is always applied.
-      Pleasant side effects of the change include that it is now possible to
-      use Perl's <literal>strict</> pragma in a natural way in
-      <literal>plperl</>, and that Perl's <literal>$a</> and <literal>$b</>
-      variables work as expected in sort routines, and that function
-      compilation is significantly faster.  (CVE-2010-1169)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent PL/Tcl from executing untrustworthy code from
-      <structname>pltcl_modules</> (Tom)
-     </para>
-
-     <para>
-      PL/Tcl's feature for autoloading Tcl code from a database table
-      could be exploited for trojan-horse attacks, because there was no
-      restriction on who could create or insert into that table.  This change
-      disables the feature unless <structname>pltcl_modules</> is owned by a
-      superuser.  (However, the permissions on the table are not checked, so
-      installations that really need a less-than-secure modules table can
-      still grant suitable privileges to trusted non-superusers.)  Also,
-      prevent loading code into the unrestricted <quote>normal</> Tcl
-      interpreter unless we are really going to execute a <literal>pltclu</>
-      function.  (CVE-2010-1170)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not allow an unprivileged user to reset superuser-only parameter
-      settings (Alvaro)
-     </para>
-
-     <para>
-      Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
-      ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
-      a database he owns, this would remove all special parameter settings
-      for the user or database, even ones that are only supposed to be
-      changeable by a superuser.  Now, the <command>ALTER</> will only
-      remove the parameters that the user has permission to change.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crash during backend shutdown if shutdown occurs
-      when a <literal>CONTEXT</> addition would be made to log entries (Tom)
-     </para>
-
-     <para>
-      In some cases the context-printing function would fail because the
-      current transaction had already been rolled back when it came time
-      to print a log message.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update pl/perl's <filename>ppport.h</> for modern Perl versions
-      (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite recursion in <application>psql</> when expanding
-      a variable that refers to itself (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
-      interrupts promptly (Tatsuhito Kasahara)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make server startup deal properly with the case that
-      <function>shmget()</> returns <literal>EINVAL</> for an existing
-      shared memory segment (Tom)
-     </para>
-
-     <para>
-      This behavior has been observed on BSD-derived kernels including OS X.
-      It resulted in an entirely-misleading startup failure complaining that
-      the shared memory request size was too large.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010j
-      for DST law changes in Argentina, Australian Antarctic, Bangladesh,
-      Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia;
-      also historical corrections for Taiwan.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-24">
-  <title>Release 8.0.24</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2010-03-15</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.23.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <para>
-   The <productname>PostgreSQL</> community will stop releasing updates
-   for the 8.0.X release series in July 2010.
-   Users are encouraged to update to a newer release branch soon.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.24</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you are upgrading from a version earlier than 8.0.22,
-    see the release notes for 8.0.22.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Add new configuration parameter <varname>ssl_renegotiation_limit</> to
-      control how often we do session key renegotiation for an SSL connection
-      (Magnus)
-     </para>
-
-     <para>
-      This can be set to zero to disable renegotiation completely, which may
-      be required if a broken SSL library is used.  In particular, some
-      vendors are shipping stopgap patches for CVE-2009-3555 that cause
-      renegotiation attempts to fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes when trying to recover from a failure in
-      subtransaction start (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix server memory leak associated with use of savepoints and a client
-      encoding different from server's encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>substring()</> for <type>bit</> types treat any negative
-      length as meaning <quote>all the rest of the string</> (Tom)
-     </para>
-
-     <para>
-      The previous coding treated only -1 that way, and would produce an
-      invalid result value for other negative values, possibly leading to
-      a crash (CVE-2010-0442).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix integer-to-bit-string conversions to handle the first fractional
-      byte correctly when the output bit width is wider than the given
-      integer by something other than a multiple of 8 bits (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some cases of pathologically slow regular expression matching (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix the <literal>STOP WAL LOCATION</> entry in backup history files to
-      report the next WAL segment's name when the end location is exactly at a
-      segment boundary (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      When reading <filename>pg_hba.conf</> and related files, do not treat
-      <literal>@something</> as a file inclusion request if the <literal>@</>
-      appears inside quote marks; also, never treat <literal>@</> by itself
-      as a file inclusion request (Tom)
-     </para>
-
-     <para>
-      This prevents erratic behavior if a role or database name starts with
-      <literal>@</>.  If you need to include a file whose path name
-      contains spaces, you can still do so, but you must write
-      <literal>@"/path to/file"</> rather than putting the quotes around
-      the whole construct.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite loop on some platforms if a directory is named as
-      an inclusion target in <filename>pg_hba.conf</> and related files
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix plpgsql failure in one case where a composite column is set to NULL
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>volatile</> markings in PL/Python to avoid possible
-      compiler-specific misbehavior (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
-     </para>
-
-     <para>
-      The only known symptom of this oversight is that the Tcl
-      <literal>clock</> command misbehaves if using Tcl 8.5 or later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent crash in <filename>contrib/dblink</> when too many key
-      columns are specified to a <function>dblink_build_sql_*</> function
-      (Rushabh Lathia, Joe Conway)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted crashes in <filename>contrib/xml2</> caused by sloppy
-      memory management (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010e
-      for DST law changes in Bangladesh, Chile, Fiji, Mexico, Paraguay, Samoa.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-23">
-  <title>Release 8.0.23</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-12-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.22.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.23</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you are upgrading from a version earlier than 8.0.22,
-    see the release notes for 8.0.22.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Protect against indirect security threats caused by index functions
-      changing session-local state (Gurjeet Singh, Tom)
-     </para>
-
-     <para>
-      This change prevents allegedly-immutable index functions from possibly
-      subverting a superuser's session (CVE-2009-4136).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Reject SSL certificates containing an embedded null byte in the common
-      name (CN) field (Magnus)
-     </para>
-
-     <para>
-      This prevents unintended matching of a certificate to a server or client
-      name during SSL validation (CVE-2009-4034).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash during backend-startup-time cache initialization (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent signals from interrupting <literal>VACUUM</> at unsafe times
-      (Alvaro)
-     </para>
-
-     <para>
-      This fix prevents a PANIC if a <literal>VACUUM FULL</> is cancelled
-      after it's already committed its tuple movements, as well as transient
-      errors if a plain <literal>VACUUM</> is interrupted after having
-      truncated the table.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash due to integer overflow in hash table size
-      calculation (Tom)
-     </para>
-
-     <para>
-      This could occur with extremely large planner estimates for the size of
-      a hashjoin's result.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix very rare crash in <type>inet</>/<type>cidr</> comparisons (Chris
-      Mikkelson)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix premature drop of temporary files used for a cursor that is accessed
-      within a subtransaction (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PAM password processing to be more robust (Tom)
-     </para>
-
-     <para>
-      The previous code is known to fail with the combination of the Linux
-      <literal>pam_krb5</> PAM module with Microsoft Active Directory as the
-      domain controller.  It might have problems elsewhere too, since it was
-      making unjustified assumptions about what arguments the PAM stack would
-      pass to it.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix rare crash in exception processing in PL/Python (Peter)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <application>psql</>'s flex module is compiled with the correct
-      system header definitions (Tom)
-     </para>
-
-     <para>
-      This fixes build failures on platforms where
-      <literal>--enable-largefile</> causes incompatible changes in the
-      generated code.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make the postmaster ignore any <literal>application_name</> parameter in
-      connection request packets, to improve compatibility with future libpq
-      versions (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009s
-      for DST law changes in Antarctica, Argentina, Bangladesh, Fiji,
-      Novokuznetsk, Pakistan, Palestine, Samoa, Syria; also historical
-      corrections for Hong Kong.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-22">
-  <title>Release 8.0.22</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-09-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.21.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.22</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you have any hash indexes on <type>interval</> columns,
-    you must <command>REINDEX</> them after updating to 8.0.22.
-    Also, if you are upgrading from a version earlier than 8.0.6,
-    see the release notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Disallow <command>RESET ROLE</> and <command>RESET SESSION
-      AUTHORIZATION</> inside security-definer functions (Tom, Heikki)
-     </para>
-
-     <para>
-      This covers a case that was missed in the previous patch that
-      disallowed <command>SET ROLE</> and <command>SET SESSION
-      AUTHORIZATION</> inside security-definer functions.
-      (See CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix handling of sub-SELECTs appearing in the arguments of
-      an outer-level aggregate function (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix hash calculation for data type <type>interval</> (Tom)
-     </para>
-
-     <para>
-      This corrects wrong results for hash joins on interval values.
-      It also changes the contents of hash indexes on interval columns.
-      If you have any such indexes, you must <command>REINDEX</> them
-      after updating.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Treat <function>to_char(..., 'TH')</> as an uppercase ordinal
-      suffix with <literal>'HH'</>/<literal>'HH12'</> (Heikki)
-     </para>
-
-     <para>
-      It was previously handled as <literal>'th'</> (lowercase).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix overflow for <literal>INTERVAL '<replaceable>x</> ms'</literal>
-      when <replaceable>x</> is more than 2 million and integer
-      datetimes are in use (Alex Hunsaker)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix calculation of distance between a point and a line segment (Tom)
-     </para>
-
-     <para>
-      This led to incorrect results from a number of geometric operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <type>money</> data type to work in locales where currency
-      amounts have no fractional digits, e.g. Japan (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Properly round datetime input like
-      <literal>00:12:57.9999999999999999999999999999</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix poor choice of page split point in GiST R-tree operator classes
-      (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix portability issues in plperl initialization (Andrew Dunstan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to not go into an infinite loop if
-      <filename>postgresql.conf</> is empty (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/xml2</>'s <function>xslt_process()</> to
-      properly handle the maximum number of parameters (twenty) (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve robustness of <application>libpq</>'s code to recover
-      from errors during <command>COPY FROM STDIN</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid including conflicting readline and editline header files
-      when both libraries are installed (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009l
-      for DST law changes in Bangladesh, Egypt, Jordan, Pakistan,
-      Argentina/San_Luis, Cuba, Jordan (historical correction only),
-      Mauritius, Morocco, Palestine, Syria, Tunisia.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-21">
-  <title>Release 8.0.21</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-03-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.20.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.21</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you are upgrading from a version earlier than 8.0.6,
-    see the release notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent error recursion crashes when encoding conversion fails (Tom)
-     </para>
-
-     <para>
-      This change extends fixes made in the last two minor releases for
-      related failure scenarios.  The previous fixes were narrowly tailored
-      for the original problem reports, but we have now recognized that
-      <emphasis>any</> error thrown by an encoding conversion function could
-      potentially lead to infinite recursion while trying to report the
-      error.  The solution therefore is to disable translation and encoding
-      conversion and report the plain-ASCII form of any error message,
-      if we find we have gotten into a recursive error reporting situation.
-      (CVE-2009-0922)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>CREATE CONVERSION</> with the wrong encodings
-      for the specified conversion function (Heikki)
-     </para>
-
-     <para>
-      This prevents one possible scenario for encoding conversion failure.
-      The previous change is a backstop to guard against other kinds of
-      failures in the same area.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix core dump when <function>to_char()</> is given format codes that
-      are inappropriate for the type of the data argument (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>MUST</> (Mauritius Island Summer Time) to the default list
-      of known timezone abbreviations (Xavier Bugaud)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-20">
-  <title>Release 8.0.20</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-02-02</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.19.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.20</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you are upgrading from a version earlier than 8.0.6,
-    see the release notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Improve handling of URLs in <function>headline()</> function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve handling of overlength headlines in <function>headline()</>
-      function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible Assert failure or misconversion if an encoding
-      conversion is created with the wrong conversion function for the
-      specified pair of encodings (Tom, Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unnecessary locking of small tables in <command>VACUUM</>
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix uninitialized variables in <filename>contrib/tsearch2</>'s
-      <function>get_covers()</> function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make all documentation reference <literal>pgsql-bugs</> and/or
-      <literal>pgsql-hackers</> as appropriate, instead of the
-      now-decommissioned <literal>pgsql-ports</> and <literal>pgsql-patches</>
-      mailing lists (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009a (for
-      Kathmandu and historical DST corrections in Switzerland, Cuba)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-19">
-  <title>Release 8.0.19</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-11-03</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.18.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.19</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you are upgrading from a version earlier than 8.0.6,
-    see the release notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix backend crash when the client encoding cannot represent a localized
-      error message (Tom)
-     </para>
-
-     <para>
-      We have addressed similar issues before, but it would still fail if
-      the <quote>character has no equivalent</> message itself couldn't
-      be converted.  The fix is to disable localization and send the plain
-      ASCII error message when we detect such a situation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash when deeply nested functions are invoked from
-      a trigger (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure an error is reported when a newly-defined PL/pgSQL trigger
-      function is invoked as a normal function (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect tsearch2 headline generation when single query
-      item matches first word of text (Sushant Sinha)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix improper display of fractional seconds in interval values when
-      using a non-ISO datestyle in an <option>--enable-integer-datetimes</>
-      build (Ron Mayer)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <function>SPI_getvalue</> and <function>SPI_getbinval</>
-      behave correctly when the passed tuple and tuple descriptor have
-      different numbers of columns (Tom)
-     </para>
-
-     <para>
-      This situation is normal when a table has had columns added or removed,
-      but these two functions didn't handle it properly.
-      The only likely consequence is an incorrect error indication.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</>'s parsing of <command>CREATE USER</> (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix recent breakage of <literal>pg_ctl restart</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008i (for
-      DST law changes in Argentina, Brazil, Mauritius, Syria)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-18">
-  <title>Release 8.0.18</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-09-22</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.17.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.18</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you are upgrading from a version earlier than 8.0.6,
-    see the release notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Widen local lock counters from 32 to 64 bits (Tom)
-     </para>
-
-     <para>
-      This responds to reports that the counters could overflow in
-      sufficiently long transactions, leading to unexpected <quote>lock is
-      already held</> errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add checks in executor startup to ensure that the tuples produced by an
-      <command>INSERT</> or <command>UPDATE</> will match the target table's
-      current rowtype (Tom)
-     </para>
-
-     <para>
-      <command>ALTER COLUMN TYPE</>, followed by re-use of a previously
-      cached plan, could produce this type of situation.  The check protects
-      against data corruption and/or crashes that could ensue.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix datetime input functions to correctly detect integer overflow when
-      running on a 64-bit platform (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve performance of writing very long log messages to syslog (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in backwards scanning of a cursor on a <literal>SELECT DISTINCT
-      ON</> query (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner to estimate that <literal>GROUP BY</> expressions yielding
-      boolean results always result in two groups, regardless of the
-      expressions' contents (Tom)
-     </para>
-
-     <para>
-      This is very substantially more accurate than the regular <literal>GROUP
-      BY</> estimate for certain boolean tests like <replaceable>col</>
-      <literal>IS NULL</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Tcl to behave correctly with Tcl 8.5, and to be more careful
-      about the encoding of data sent to or from Tcl (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Python to work with Python 2.5
-     </para>
-
-     <para>
-      This is a back-port of fixes made during the 8.2 development cycle.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <application>pg_dump</> and <application>pg_restore</>'s
-      error reporting after failure to send a SQL command (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to properly preserve postmaster
-      command-line arguments across a <literal>restart</> (Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008f (for
-      DST law changes in Argentina, Bahamas, Brazil, Mauritius, Morocco,
-      Pakistan, Palestine, and Paraguay)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-17">
-  <title>Release 8.0.17</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-06-12</simpara>
-  </note>
-
-  <para>
-   This release contains one serious bug fix over 8.0.16.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.17</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you are upgrading from a version earlier than 8.0.6,
-    see the release notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Make <function>pg_get_ruledef()</> parenthesize negative constants (Tom)
-     </para>
-
-     <para>
-      Before this fix, a negative constant in a view or rule might be dumped
-      as, say, <literal>-42::integer</>, which is subtly incorrect: it should
-      be <literal>(-42)::integer</> due to operator precedence rules.
-      Usually this would make little difference, but it could interact with
-      another recent patch to cause
-      <productname>PostgreSQL</> to reject what had been a valid
-      <command>SELECT DISTINCT</> view query.  Since this could result in
-      <application>pg_dump</> output failing to reload, it is being treated
-      as a high-priority fix.  The only released versions in which dump
-      output is actually incorrect are 8.3.1 and 8.2.7.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-16">
-  <title>Release 8.0.16</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>never released</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.15.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.16</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.
-    However, if you are upgrading from a version earlier than 8.0.6,
-    see the release notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix <command>ALTER TABLE ADD COLUMN ... PRIMARY KEY</> so that the new
-      column is correctly checked to see if it's been initialized to all
-      non-nulls (Brendan Jurd)
-     </para>
-
-     <para>
-      Previous versions neglected to check this requirement at all.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible <command>CREATE TABLE</> failure when inheriting the
-      <quote>same</> constraint from multiple parent relations that
-      inherited that constraint from a common ancestor (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix conversions between ISO-8859-5 and other encodings to handle
-      Cyrillic <quote>Yo</> characters (<literal>e</> and <literal>E</> with
-      two dots) (Sergey Burladyan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a few datatype input functions
-      that were allowing unused bytes in their results to contain
-      uninitialized, unpredictable values (Tom)
-     </para>
-
-     <para>
-      This could lead to failures in which two apparently identical literal
-      values were not seen as equal, resulting in the parser complaining
-      about unmatched <literal>ORDER BY</> and <literal>DISTINCT</>
-      expressions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a corner case in regular-expression substring matching
-      (<literal>substring(<replaceable>string</> from
-      <replaceable>pattern</>)</literal>) (Tom)
-     </para>
-
-     <para>
-      The problem occurs when there is a match to the pattern overall but
-      the user has specified a parenthesized subexpression and that
-      subexpression hasn't got a match.  An example is
-      <literal>substring('foo' from 'foo(bar)?')</>.
-      This should return NULL, since <literal>(bar)</> isn't matched, but
-      it was mistakenly returning the whole-pattern match instead (ie,
-      <literal>foo</>).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008c (for
-      DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba,
-      Argentina/San_Luis, and Chile)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect result from <application>ecpg</>'s
-      <function>PGTYPEStimestamp_sub()</> function (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix core dump in <filename>contrib/xml2</>'s
-      <function>xpath_table()</> function when the input query returns a
-      NULL value (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/xml2</>'s makefile to not override
-      <literal>CFLAGS</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>DatumGetBool</> macro to not fail with <application>gcc</>
-      4.3 (Tom)
-     </para>
-
-     <para>
-      This problem affects <quote>old style</> (V0) C functions that
-      return boolean.  The fix is already in 8.3, but the need to
-      back-patch it was not realized at the time.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix longstanding <command>LISTEN</>/<command>NOTIFY</>
-      race condition (Tom)
-     </para>
-
-     <para>
-      In rare cases a session that had just executed a
-      <command>LISTEN</> might not get a notification, even though
-      one would be expected because the concurrent transaction executing
-      <command>NOTIFY</> was observed to commit later.
-     </para>
-
-     <para>
-      A side effect of the fix is that a transaction that has executed
-      a not-yet-committed <command>LISTEN</> command will not see any
-      row in <structname>pg_listener</> for the <command>LISTEN</>,
-      should it choose to look; formerly it would have.  This behavior
-      was never documented one way or the other, but it is possible that
-      some applications depend on the old behavior.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix rare crash when an error occurs during a query using a hash index
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix input of datetime values for February 29 in years BC (Tom)
-     </para>
-
-     <para>
-      The former coding was mistaken about which years were leap years.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>unrecognized node type</> error in some variants of
-      <command>ALTER OWNER</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to correctly extract the postmaster's port
-      number from command-line options (Itagaki Takahiro, Tom)
-     </para>
-
-     <para>
-      Previously, <literal>pg_ctl start -w</> could try to contact the
-      postmaster on the wrong port, leading to bogus reports of startup
-      failure.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Use <option>-fwrapv</> to defend against possible misoptimization
-      in recent <application>gcc</> versions (Tom)
-     </para>
-
-     <para>
-      This is known to be necessary when building <productname>PostgreSQL</>
-      with <application>gcc</> 4.3 or later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix display of constant expressions in <literal>ORDER BY</>
-      and <literal>GROUP BY</> (Tom)
-     </para>
-
-     <para>
-      An explictly casted constant would be shown incorrectly.  This could
-      for example lead to corruption of a view definition during
-      dump and reload.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>libpq</> to handle NOTICE messages correctly
-      during COPY OUT (Tom)
-     </para>
-
-     <para>
-      This failure has only been observed to occur when a user-defined
-      datatype's output routine issues a NOTICE, but there is no
-      guarantee it couldn't happen due to other causes.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-15">
-  <title>Release 8.0.15</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-01-07</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.14,
-   including fixes for significant security issues.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <para>
-   This is the last 8.0.X release for which the <productname>PostgreSQL</>
-   community will produce binary packages for <productname>Windows</>.
-   Windows users are encouraged to move to 8.2.X or later,
-   since there are Windows-specific fixes in 8.2.X that
-   are impractical to back-port.  8.0.X will continue to
-   be supported on other platforms.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.15</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.6, see the release
-    notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent functions in indexes from executing with the privileges of
-      the user running <command>VACUUM</>, <command>ANALYZE</>, etc (Tom)
-     </para>
-
-     <para>
-      Functions used in index expressions and partial-index
-      predicates are evaluated whenever a new table entry is made.  It has
-      long been understood that this poses a risk of trojan-horse code
-      execution if one modifies a table owned by an untrustworthy user.
-      (Note that triggers, defaults, check constraints, etc. pose the
-      same type of risk.)  But functions in indexes pose extra danger
-      because they will be executed by routine maintenance operations
-      such as <command>VACUUM FULL</>, which are commonly performed
-      automatically under a superuser account.  For example, a nefarious user
-      can execute code with superuser privileges by setting up a
-      trojan-horse index definition and waiting for the next routine vacuum.
-      The fix arranges for standard maintenance operations
-      (including <command>VACUUM</>, <command>ANALYZE</>, <command>REINDEX</>,
-      and <command>CLUSTER</>) to execute as the table owner rather than
-      the calling user, using the same privilege-switching mechanism already
-      used for <literal>SECURITY DEFINER</> functions.  To prevent bypassing
-      this security measure, execution of <command>SET SESSION
-      AUTHORIZATION</> and <command>SET ROLE</> is now forbidden within a
-      <literal>SECURITY DEFINER</> context.  (CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Repair assorted bugs in the regular-expression package (Tom, Will Drewry)
-     </para>
-
-     <para>
-      Suitably crafted regular-expression patterns could cause crashes,
-      infinite or near-infinite looping, and/or massive memory consumption,
-      all of which pose denial-of-service hazards for applications that
-      accept regex search patterns from untrustworthy sources.
-      (CVE-2007-4769, CVE-2007-4772, CVE-2007-6067)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require non-superusers who use <filename>/contrib/dblink</> to use only
-      password authentication, as a security measure (Joe)
-     </para>
-
-     <para>
-      The fix that appeared for this in 8.0.14 was incomplete, as it plugged
-      the hole for only some <filename>dblink</> functions.  (CVE-2007-6601,
-      CVE-2007-3278)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2007k
-      (in particular, recent Argentina changes) (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner failure in some cases of <literal>WHERE false AND var IN
-      (SELECT ...)</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Preserve the tablespace of indexes that are
-      rebuilt by <command>ALTER TABLE ... ALTER COLUMN TYPE</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make archive recovery always start a new WAL timeline, rather than only
-      when a recovery stop time was used (Simon)
-     </para>
-
-     <para>
-      This avoids a corner-case risk of trying to overwrite an existing
-      archived copy of the last WAL segment, and seems simpler and cleaner
-      than the original definition.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>VACUUM</> not use all of <varname>maintenance_work_mem</>
-      when the table is too small for it to be useful (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential crash in <function>translate()</> when using a multibyte
-      database encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Perl to cope when platform's Perl defines type <literal>bool</>
-      as <literal>int</> rather than <literal>char</> (Tom)
-     </para>
-
-     <para>
-      While this could theoretically happen anywhere, no standard build of
-      Perl did things this way ... until <productname>Mac OS X</> 10.5.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Python to not crash on long exception messages (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_dump</> to correctly handle inheritance child tables
-      that have default expressions different from their parent's (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <application>ecpg</> parser fixes (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <filename>contrib/tablefunc</>'s <function>crosstab()</> handle
-      NULL rowid as a category in its own right, rather than crashing (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <type>tsvector</> and <type>tsquery</> output routines to
-      escape backslashes correctly (Teodor, Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash of <function>to_tsvector()</> on huge input strings (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require a specific version of <productname>Autoconf</> to be used
-      when re-generating the <command>configure</> script (Peter)
-     </para>
-
-     <para>
-      This affects developers and packagers only.  The change was made
-      to prevent accidental use of untested combinations of
-      <productname>Autoconf</> and <productname>PostgreSQL</> versions.
-      You can remove the version check if you really want to use a
-      different <productname>Autoconf</> version, but it's
-      your responsibility whether the result works or not.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-14">
-  <title>Release 8.0.14</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-09-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.13.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.14</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.6, see the release
-    notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent index corruption when a transaction inserts rows and
-      then aborts close to the end of a concurrent <command>VACUUM</>
-      on the same table (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>CREATE DOMAIN ... DEFAULT NULL</> work properly (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix excessive logging of <acronym>SSL</> error messages (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix logging so that log messages are never interleaved when using
-      the syslogger process (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash when <varname>log_min_error_statement</> logging runs out
-      of memory (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect handling of some foreign-key corner cases (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent <command>CLUSTER</> from failing
-      due to attempting to process temporary tables of other sessions (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update the time zone database rules, particularly New Zealand's upcoming changes (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Windows socket improvements (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Suppress timezone name (<literal>%Z</>) in log timestamps on Windows
-      because of possible encoding mismatches (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require non-superusers who use <filename>/contrib/dblink</> to use only
-      password authentication, as a security measure (Joe)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-13">
-  <title>Release 8.0.13</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-04-23</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.12,
-   including a security fix.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.13</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.6, see the release
-    notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Support explicit placement of the temporary-table schema within
-     <varname>search_path</>, and disable searching it for functions
-     and operators (Tom)
-    </para>
-    <para>
-     This is needed to allow a security-definer function to set a
-     truly secure value of <varname>search_path</>.  Without it,
-     an unprivileged SQL user can use temporary objects to execute code
-     with the privileges of the security-definer function (CVE-2007-2138).
-     See <command>CREATE FUNCTION</> for more information.
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     <filename>/contrib/tsearch2</> crash fixes (Teodor)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix potential-data-corruption bug in how <command>VACUUM FULL</> handles
-     <command>UPDATE</> chains (Tom, Pavan Deolasee)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix PANIC during enlargement of a hash index (bug introduced in 8.0.10)
-     (Tom)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix POSIX-style timezone specs to follow new USA DST rules (Tom)
-    </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-12">
-  <title>Release 8.0.12</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-02-07</simpara>
-  </note>
-
-  <para>
-   This release contains one fix from 8.0.11.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.12</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.6, see the release
-    notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Remove overly-restrictive check for type length in constraints and
-     functional indexes(Tom)
-    </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-11">
-  <title>Release 8.0.11</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-02-05</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.10, including
-   a security fix.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.11</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.6, see the release
-    notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Remove security vulnerabilities that allowed connected users
-     to read backend memory (Tom)
-    </para>
-    <para>
-     The vulnerabilities involve suppressing the normal check that a SQL
-     function returns the data type it's declared to, and changing the
-     data type of a table column (CVE-2007-0555, CVE-2007-0556).  These
-     errors can easily be exploited to cause a backend crash, and in
-     principle might be used to read database content that the user
-     should not be able to access.
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix rare bug wherein btree index page splits could fail
-     due to choosing an infeasible split point (Heikki Linnakangas)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix for rare Assert() crash triggered by <literal>UNION</> (Tom)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Tighten security of multi-byte character processing for UTF8 sequences
-     over three bytes long (Tom)
-    </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-10">
-  <title>Release 8.0.10</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-01-08</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.9.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.10</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.6, see the release
-    notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Improve handling of <function>getaddrinfo()</> on AIX (Tom)
-     </para>
-
-     <para>
-      This fixes a problem with starting the statistics collector,
-      among other things.
-     </para>
-    </listitem>
-
-     <listitem>
-      <para>
-       Fix <quote>failed to re-find parent key</> errors in
-       <command>VACUUM</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix race condition for truncation of a large relation across a
-       gigabyte boundary by <command>VACUUM</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix bugs affecting multi-gigabyte hash indexes (Tom)
-      </para>
-     </listitem>
-
-    <listitem>
-     <para>
-      Fix possible deadlock in Windows signal handling (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix error when constructing an <literal>ARRAY[]</> made up of multiple
-      empty elements (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix ecpg memory leak during connection (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>to_number()</> and <function>to_char(numeric)</>
-      are now <literal>STABLE</>, not <literal>IMMUTABLE</>, for
-      new <application>initdb</> installs (Tom)
-     </para>
-
-     <para>
-      This is because <varname>lc_numeric</> can potentially
-      change the output of these functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve index usage of regular expressions that use parentheses (Tom)
-     </para>
-
-     <para>
-      This improves <application>psql</> <literal>\d</> performance also.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update timezone database
-     </para>
-
-     <para>
-      This affects Australian and Canadian daylight-savings rules in
-      particular.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-9">
-  <title>Release 8.0.9</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-10-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.8.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.9</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.6, see the release
-    notes for 8.0.6.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fix crash when referencing <literal>NEW</> row
-values in rule WHERE expressions (Tom)</para></listitem>
-<listitem><para>Fix core dump when an untyped literal is taken as
-ANYARRAY</para></listitem>
-<listitem><para>Fix mishandling of AFTER triggers when query contains a SQL
-function returning multiple rows (Tom)</para></listitem>
-<listitem><para>Fix <command>ALTER TABLE ... TYPE</> to recheck
-<literal>NOT NULL</> for <literal>USING</> clause (Tom)</para></listitem>
-<listitem><para>Fix <function>string_to_array()</> to handle overlapping
- matches for the separator string</para>
-<para>For example, <literal>string_to_array('123xx456xxx789', 'xx')</>.
-</para></listitem>
-<listitem><para>Fix corner cases in pattern matching for
- <application>psql</>'s <literal>\d</> commands</para></listitem>
-<listitem><para>Fix index-corrupting bugs in /contrib/ltree
- (Teodor)</para></listitem>
-<listitem><para>Numerous robustness fixes in <application>ecpg</> (Joachim
-Wieland)</para></listitem>
-<listitem><para>Fix backslash escaping in /contrib/dbmirror</para></listitem>
-<listitem><para>Fix instability of statistics collection on Win32 (Tom, Andrew)</para></listitem>
-<listitem><para>Fixes for <systemitem class="osname">AIX</> and
-<productname>Intel</> compilers (Tom)</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-8">
-  <title>Release 8.0.8</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-05-23</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.7,
-   including patches for extremely serious security issues.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.8</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.6, see the release
-    notes for 8.0.6.
-   </para>
-
-   <para>
-    Full security against the SQL-injection attacks described in
-    CVE-2006-2313 and CVE-2006-2314 might require changes in application
-    code.  If you have applications that embed untrustworthy strings
-    into SQL commands, you should examine them as soon as possible to
-    ensure that they are using recommended escaping techniques.  In
-    most cases, applications should be using subroutines provided by
-    libraries or drivers (such as <application>libpq</>'s
-    <function>PQescapeStringConn()</>) to perform string escaping,
-    rather than relying on <foreignphrase>ad hoc</> code to do it.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Change the server to reject invalidly-encoded multibyte
-characters in all cases (Tatsuo, Tom)</para>
-<para>While <productname>PostgreSQL</> has been moving in this direction for
-some time, the checks are now applied uniformly to all encodings and all
-textual input, and are now always errors not merely warnings.  This change
-defends against SQL-injection attacks of the type described in CVE-2006-2313.
-</para></listitem>
-
-<listitem><para>Reject unsafe uses of <literal>\'</> in string literals</para>
-<para>As a server-side defense against SQL-injection attacks of the type
-described in CVE-2006-2314, the server now only accepts <literal>''</> and not
-<literal>\'</> as a representation of ASCII single quote in SQL string
-literals.  By default, <literal>\'</> is rejected only when
-<varname>client_encoding</> is set to a client-only encoding (SJIS, BIG5, GBK,
-GB18030, or UHC), which is the scenario in which SQL injection is possible.
-A new configuration parameter <varname>backslash_quote</> is available to
-adjust this behavior when needed.  Note that full security against
-CVE-2006-2314 might require client-side changes; the purpose of
-<varname>backslash_quote</> is in part to make it obvious that insecure
-clients are insecure.
-</para></listitem>
-
-<listitem><para>Modify <application>libpq</>'s string-escaping routines to be
-aware of encoding considerations and
-<varname>standard_conforming_strings</></para>
-<para>This fixes <application>libpq</>-using applications for the security
-issues described in CVE-2006-2313 and CVE-2006-2314, and also future-proofs
-them against the planned changeover to SQL-standard string literal syntax.
-Applications that use multiple <productname>PostgreSQL</> connections
-concurrently should migrate to <function>PQescapeStringConn()</> and
-<function>PQescapeByteaConn()</> to ensure that escaping is done correctly
-for the settings in use in each database connection.  Applications that
-do string escaping <quote>by hand</> should be modified to rely on library
-routines instead.
-</para></listitem>
-
-<listitem><para>Fix some incorrect encoding conversion functions</para>
-<para><function>win1251_to_iso</>, <function>alt_to_iso</>,
-<function>euc_tw_to_big5</>, <function>euc_tw_to_mic</>,
-<function>mic_to_euc_tw</> were all broken to varying
-extents.
-</para></listitem>
-
-<listitem><para>Clean up stray remaining uses of <literal>\'</> in strings
-(Bruce, Jan)</para></listitem>
-
-<listitem><para>Fix bug that sometimes caused OR'd index scans to
-miss rows they should have returned</para></listitem>
-
-<listitem><para>Fix WAL replay for case where a btree index has been
-truncated</para></listitem>
-
-<listitem><para>Fix <literal>SIMILAR TO</> for patterns involving
-<literal>|</> (Tom)</para></listitem>
-
-<listitem><para>Fix <command>SELECT INTO</> and <command>CREATE TABLE AS</> to
-create tables in the default tablespace, not the base directory (Kris
-Jurka)</para></listitem>
-
-<listitem><para>Fix server to use custom DH SSL parameters correctly (Michael
-Fuhr)</para></listitem>
-
-<listitem><para>Fix for Bonjour on Intel Macs (Ashley Clark)</para></listitem>
-
-<listitem><para>Fix various minor memory leaks</para></listitem>
-
-<listitem><para>Fix problem with password prompting on some Win32 systems
-(Robert Kinberg)</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-7">
-  <title>Release 8.0.7</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-02-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.6.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.7</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.6, see the release
-    notes for 8.0.6.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix potential crash in <command>SET
-SESSION AUTHORIZATION</> (CVE-2006-0553)</para>
-<para>An unprivileged user could crash the server process, resulting in
-momentary denial of service to other users, if the server has been compiled
-with Asserts enabled (which is not the default).
-Thanks to Akio Ishida for reporting this problem.
-</para></listitem>
-
-<listitem><para>Fix bug with row visibility logic in self-inserted
-rows (Tom)</para>
-<para>Under rare circumstances a row inserted by the current command
-could be seen as already valid, when it should not be.  Repairs bug
-created in 8.0.4, 7.4.9, and 7.3.11 releases.
-</para></listitem>
-
-<listitem><para>Fix race condition that could lead to <quote>file already
-exists</> errors during pg_clog and pg_subtrans file creation
-(Tom)</para></listitem>
-
-<listitem><para>Fix cases that could lead to crashes if a cache-invalidation
-message arrives at just the wrong time (Tom)</para></listitem>
-
-<listitem><para>Properly check <literal>DOMAIN</> constraints for
-<literal>UNKNOWN</> parameters in prepared statements
-(Neil)</para></listitem>
-
-<listitem><para>Ensure <command>ALTER COLUMN TYPE</> will process
-<literal>FOREIGN KEY</>, <literal>UNIQUE</>, and <literal>PRIMARY KEY</>
-constraints in the proper order (Nakano Yoshihisa)</para></listitem>
-
-<listitem><para>Fixes to allow restoring dumps that have cross-schema
-references to custom operators or operator classes (Tom)</para></listitem>
-
-<listitem><para>Allow <application>pg_restore</> to continue properly after a
-<command>COPY</> failure; formerly it tried to treat the remaining
-<command>COPY</> data as SQL commands (Stephen Frost)</para></listitem>
-
-<listitem><para>Fix <application>pg_ctl</> <literal>unregister</> crash
-when the  data directory is not specified (Magnus)</para></listitem>
-
-<listitem><para>Fix <application>ecpg</> crash on AMD64 and PPC
-(Neil)</para></listitem>
-
-<listitem><para>Recover properly if error occurs during argument passing
-in <application>PL/python</> (Neil)</para></listitem>
-
-<listitem><para>Fix <application>PL/perl</>'s handling of locales on
-Win32 to match the backend (Andrew)</para></listitem>
-
-<listitem><para>Fix crash when <literal>log_min_messages</> is set to
-<literal>DEBUG3</> or above in <filename>postgresql.conf</> on Win32
-(Bruce)</para></listitem>
-
-<listitem><para>Fix <application>pgxs</> <literal>-L</> library path
-specification for Win32, Cygwin, OS X, AIX (Bruce)</para></listitem>
-
-<listitem><para>Check that SID is enabled while checking for Win32 admin
-privileges (Magnus)</para></listitem>
-
-<listitem><para>Properly reject out-of-range date inputs (Kris
-Jurka)</para></listitem>
-
-<listitem><para>Portability fix for testing presence of <function>finite</>
-and <function>isinf</> during configure (Tom)</para></listitem>
-
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-6">
-  <title>Release 8.0.6</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-01-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.5.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.6</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.3, see the release
-    notes for 8.0.3.
-    Also, you might need to <command>REINDEX</> indexes on textual
-    columns after updating, if you are affected by the locale or
-    <application>plperl</> issues described below.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix Windows code so that postmaster will continue rather
-than exit if there is no more room in ShmemBackendArray (Magnus)</para>
-<para>The previous behavior could lead to a denial-of-service situation if too
-many connection requests arrive close together.  This applies
-<emphasis>only</> to the Windows port.</para></listitem>
-
-<listitem><para>Fix bug introduced in 8.0 that could allow ReadBuffer
-to return an already-used page as new, potentially causing loss of
-recently-committed data (Tom)</para></listitem>
-
-<listitem><para>Fix for protocol-level Describe messages issued
-outside a transaction or in a failed transaction (Tom)</para></listitem>
-
-<listitem><para>Fix character string comparison for locales that consider
-different character combinations as equal, such as Hungarian (Tom)</para>
-<para>This might require <command>REINDEX</> to fix existing indexes on
-textual columns.</para></listitem>
-
-<listitem><para>Set locale environment variables during postmaster startup
-to ensure that <application>plperl</> won't change the locale later</para>
-<para>This fixes a problem that occurred if the <application>postmaster</> was
-started with environment variables specifying a different locale than what
-<application>initdb</> had been told.  Under these conditions, any use of
-<application>plperl</> was likely to lead to corrupt indexes.  You might need
-<command>REINDEX</> to fix existing indexes on
-textual columns if this has happened to you.</para></listitem>
-
-<listitem><para>Allow more flexible relocation of installation
-directories (Tom)</para>
-<para>Previous releases supported relocation only if all installation
-directory paths were the same except for the last component.</para></listitem>
-
-<listitem><para>Fix longstanding bug in strpos() and regular expression
-handling in certain rarely used Asian multi-byte character sets (Tatsuo)
-</para></listitem>
-
-<listitem><para>Various fixes for functions returning <literal>RECORD</>s
-(Tom) </para></listitem>
-
-<listitem><para>Fix bug in <filename>/contrib/pgcrypto</> gen_salt,
-which caused it not to use all available salt space for MD5 and
-XDES algorithms (Marko Kreen, Solar Designer)</para>
-<para>Salts for Blowfish and standard DES are unaffected.</para></listitem>
-
-<listitem><para>Fix <filename>/contrib/dblink</> to throw an error,
-rather than crashing, when the number of columns specified is different from
-what's actually returned by the query (Joe)</para></listitem>
-
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-5">
-  <title>Release 8.0.5</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-12-12</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.4.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.5</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.3, see the release
-    notes for 8.0.3.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix race condition in transaction log management</para>
-<para>There was a narrow window in which an I/O operation could be initiated
-for the wrong page, leading to an Assert failure or data
-corruption.</para>
-</listitem>
-
-<listitem><para>Fix bgwriter problems after recovering from errors
-(Tom)</para>
-<para>
-The background writer was found to leak buffer pins after write errors.
-While not fatal in itself, this might lead to mysterious blockages of
-later VACUUM commands.
-</para>
-</listitem>
-
-<listitem><para>Prevent failure if client sends Bind protocol message
-when current transaction is already aborted</para></listitem>
-
-<listitem><para><filename>/contrib/ltree</> fixes (Teodor)</para></listitem>
-
-<listitem><para>AIX and HPUX compile fixes (Tom)</para></listitem>
-
-<listitem><para>Retry file reads and writes after Windows
-NO_SYSTEM_RESOURCES error (Qingqing Zhou)</para></listitem>
-
-<listitem><para>Fix intermittent failure when <varname>log_line_prefix</>
-includes <literal>%i</></para></listitem>
-
-<listitem><para>Fix <application>psql</> performance issue with long scripts
-on Windows (Merlin Moncure)</para></listitem>
-
-<listitem><para>Fix missing updates of <filename>pg_group</> flat
-file</para></listitem>
-
-<listitem><para>Fix longstanding planning error for outer joins</para>
-<para>This bug sometimes caused a bogus error <quote>RIGHT JOIN is
-only supported with merge-joinable join conditions</>.</para></listitem>
-
-<listitem><para>Postpone timezone initialization until after
-<filename>postmaster.pid</> is created</para>
-<para>This avoids confusing startup scripts that expect the pid file to appear
-quickly.</para></listitem>
-
-<listitem><para>Prevent core dump in <application>pg_autovacuum</> when a
-table has been dropped</para></listitem>
-
-<listitem><para>Fix problems with whole-row references (<literal>foo.*</>)
-to subquery results</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-4">
-  <title>Release 8.0.4</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-10-04</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.3.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.4</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    if you are upgrading from a version earlier than 8.0.3, see the release
-    notes for 8.0.3.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fix error that allowed <command>VACUUM</> to remove
-<literal>ctid</> chains too soon, and add more checking in code that follows
-<literal>ctid</> links</para>
-<para>This fixes a long-standing problem that could cause crashes in very rare
-circumstances.</para></listitem>
-<listitem><para>Fix <type>CHAR()</> to properly pad spaces to the specified
-length when using a multiple-byte character set (Yoshiyuki Asaba)</para>
-<para>In prior releases, the padding of <type>CHAR()</> was incorrect
-because it only padded to the specified number of bytes without
-considering how many characters were stored.</para></listitem>
-<listitem><para>Force a checkpoint before committing <command>CREATE
-DATABASE</></para>
-<para>This should fix recent reports of <quote>index is not a btree</>
-failures when a crash occurs shortly after <command>CREATE
-DATABASE</>.</para></listitem>
-<listitem><para>Fix the sense of the test for read-only transaction
-in <command>COPY</></para>
-<para>The code formerly prohibited <command>COPY TO</>, where it should
-prohibit <command>COPY FROM</>.
-</para></listitem>
-<listitem><para>Handle consecutive embedded newlines in <command>COPY</>
-CSV-mode input</para></listitem>
-<listitem><para>Fix <function>date_trunc(week)</> for dates near year
-end</para></listitem>
-<listitem><para>Fix planning problem with outer-join ON clauses that reference
-only the inner-side relation</para></listitem>
-<listitem><para>Further fixes for <literal>x FULL JOIN y ON true</> corner
-cases</para></listitem>
-<listitem><para>Fix overenthusiastic optimization of <literal>x IN (SELECT
-DISTINCT ...)</> and related cases</para></listitem>
-<listitem><para>Fix mis-planning of queries with small <literal>LIMIT</>
-values due to poorly thought out <quote>fuzzy</> cost
-comparison</para></listitem>
-<listitem><para>Make <function>array_in</> and <function>array_recv</> more
-paranoid about validating their OID parameter</para></listitem>
-<listitem><para>Fix missing rows in queries like <literal>UPDATE a=... WHERE
-a...</> with GiST index on column <literal>a</></para></listitem>
-<listitem><para>Improve robustness of datetime parsing</para></listitem>
-<listitem><para>Improve checking for partially-written WAL
-pages</para></listitem>
-<listitem><para>Improve robustness of signal handling when SSL is
-enabled</para></listitem>
-<listitem><para>Improve MIPS and M68K spinlock code</para></listitem>
-<listitem><para>Don't try to open more than <literal>max_files_per_process</>
-files during postmaster startup</para></listitem>
-<listitem><para>Various memory leakage fixes</para></listitem>
-<listitem><para>Various portability improvements</para></listitem>
-<listitem><para>Update timezone data files</para></listitem>
-<listitem><para>Improve handling of DLL load failures on Windows</para></listitem>
-<listitem><para>Improve random-number generation on Windows</para></listitem>
-<listitem><para>Make <literal>psql -f filename</> return a nonzero exit code
-when opening the file fails</para></listitem>
-<listitem><para>Change <application>pg_dump</> to handle inherited check
-constraints more reliably</para></listitem>
-<listitem><para>Fix password prompting in <application>pg_restore</> on
-Windows</para></listitem>
-<listitem><para>Fix PL/pgSQL to handle <literal>var := var</> correctly when
-the variable is of pass-by-reference type</para></listitem>
-<listitem><para>Fix PL/Perl <literal>%_SHARED</> so it's actually
-shared</para></listitem>
-<listitem><para>Fix <filename>contrib/pg_autovacuum</> to allow sleep
-intervals over 2000 sec</para></listitem>
-<listitem><para>Update <filename>contrib/tsearch2</> to use current Snowball
-code</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-3">
-  <title>Release 8.0.3</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-05-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.2, including several
-   security-related issues.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.3</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.X.  However,
-    it is one possible way of handling two significant security problems
-    that have been found in the initial contents of 8.0.X system
-    catalogs.  A dump/initdb/reload sequence using 8.0.3's initdb will
-    automatically correct these problems.
-   </para>
-
-   <para>
-    The larger security problem is that the built-in character set encoding
-    conversion functions can be invoked from SQL commands by unprivileged
-    users, but the functions were not designed for such use and are not
-    secure against malicious choices of arguments.  The fix involves changing
-    the declared parameter list of these functions so that they can no longer
-    be invoked from SQL commands.  (This does not affect their normal use
-    by the encoding conversion machinery.)
-   </para>
-
-   <para>
-    The lesser problem is that the <filename>contrib/tsearch2</> module
-    creates several functions that are improperly declared to return
-    <type>internal</> when they do not accept <type>internal</> arguments.
-    This breaks type safety for all functions using <type>internal</>
-    arguments.
-   </para>
-
-   <para>
-    It is strongly recommended that all installations repair these errors,
-    either by initdb or by following the manual repair procedure given
-    below.  The errors at least allow unprivileged database users to crash
-    their server process, and might allow unprivileged users to gain the
-    privileges of a database superuser.
-   </para>
-
-   <para>
-    If you wish not to do an initdb, perform the same manual repair
-    procedures shown in the <link linkend="release-7-4-8">7.4.8 release
-    notes</link>.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Change encoding function signature to prevent
-misuse</para></listitem>
-<listitem><para>Change <filename>contrib/tsearch2</> to avoid unsafe use of
-<type>INTERNAL</> function results</para></listitem>
-<listitem><para>Guard against incorrect second parameter to
-<function>record_out</></para></listitem>
-<listitem><para>Repair ancient race condition that allowed a transaction to be
-seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner
-than for other purposes</para>
-<para>This is an extremely serious bug since it could lead to apparent
-data inconsistencies being briefly visible to applications.</para></listitem>
-<listitem><para>Repair race condition between relation extension and
-VACUUM</para>
-<para>This could theoretically have caused loss of a page's worth of
-freshly-inserted data, although the scenario seems of very low probability.
-There are no known cases of it having caused more than an Assert failure.
-</para></listitem>
-<listitem><para>Fix comparisons of <type>TIME WITH TIME ZONE</> values</para>
-<para>
-The comparison code was wrong in the case where the
-<literal>--enable-integer-datetimes</> configuration switch had been used.
-NOTE: if you have an index on a <type>TIME WITH TIME ZONE</> column,
-it will need to be <command>REINDEX</>ed after installing this update, because
-the fix corrects the sort order of column values.
-</para></listitem>
-<listitem><para>Fix <function>EXTRACT(EPOCH)</> for
-<type>TIME WITH TIME ZONE</> values</para></listitem>
-<listitem><para>Fix mis-display of negative fractional seconds in
-<type>INTERVAL</> values</para>
-<para>
-This error only occurred when the
-<literal>--enable-integer-datetimes</> configuration switch had been used.
-</para></listitem>
-<listitem><para>Fix pg_dump to dump trigger names containing <literal>%</>
-correctly (Neil)</para></listitem>
-<listitem><para>Still more 64-bit fixes for
-<filename>contrib/intagg</></para></listitem>
-<listitem><para>Prevent incorrect optimization of functions returning
-<type>RECORD</></para></listitem>
-<listitem><para>Prevent crash on <literal>COALESCE(NULL,NULL)</></para></listitem>
-<listitem><para>Fix Borland makefile for libpq</para></listitem>
-<listitem><para>Fix <filename>contrib/btree_gist</> for <type>timetz</> type
-(Teodor)</para></listitem>
-<listitem><para>Make <command>pg_ctl</> check the PID found in
-<filename>postmaster.pid</> to see if it is still a live
-process</para></listitem>
-<listitem><para>Fix <command>pg_dump</>/<command>pg_restore</> problems caused
-by addition of dump timestamps</para></listitem>
-<listitem><para>Fix interaction between materializing holdable cursors and
-firing deferred triggers during transaction commit</para></listitem>
-<listitem><para>Fix memory leak in SQL functions returning pass-by-reference
-data types</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-2">
-  <title>Release 8.0.2</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-04-07</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.1.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.2</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.*.
-    This release updates the major version number of the
-    <productname>PostgreSQL</productname> libraries, so it might be
-    necessary to re-link some user applications if they cannot
-    find the properly-numbered shared library.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Increment the major version number of all interface
-libraries (Bruce)</para>
-<para>
-This should have been done in 8.0.0.  It is required so 7.4.X versions
-of PostgreSQL client applications, like <application>psql</>,
-can be used on the same machine as 8.0.X applications.  This might require
-re-linking user applications that use these libraries.
-</para></listitem>
-<listitem><para>Add Windows-only <varname>wal_sync_method</> setting of
-<option>fsync_writethrough</> (Magnus, Bruce)</para>
-<para>
-This setting causes <productname>PostgreSQL</productname> to write through
-any disk-drive write cache when writing to WAL.
-This behavior was formerly called <option>fsync</>, but was
-renamed because it acts quite differently from <option>fsync</> on other
-platforms.
-</para>
-</listitem>
-<listitem><para>Enable the <varname>wal_sync_method</> setting of
-<option>open_datasync</> on Windows, and make it the default for that
- platform (Magnus, Bruce)</para>
-<para>
-Because the default is no longer <option>fsync_writethrough</>,
-data loss is possible during a power failure if the disk drive has
-write caching enabled. To turn off the write cache on Windows,
-from the <application>Device Manager</>, choose the drive properties,
-then <literal>Policies</>.
-</para>
-</listitem>
-<listitem><para>New cache management algorithm <acronym>2Q</> replaces
-<acronym>ARC</> (Tom)</para>
-<para>
-This was done to avoid a pending US patent on <acronym>ARC</>.  The
-<acronym>2Q</> code might be a few percentage points slower than
-<acronym>ARC</> for some work loads.  A better cache management algorithm
-will appear in 8.1.
-</para></listitem>
-<listitem><para>Planner adjustments to improve behavior on freshly-created
-tables (Tom)</para></listitem>
-<listitem><para>Allow plpgsql to assign to an element of an array that is
-initially <literal>NULL</> (Tom)</para>
-<para>
-Formerly the array would remain <literal>NULL</>, but now it becomes a
-single-element array.  The main SQL engine was changed to handle
-<command>UPDATE</> of a null array value this way in 8.0, but the similar
-case in plpgsql was overlooked.
-</para>
-</listitem>
-<listitem><para>Convert <literal>\r\n</> and <literal>\r</> to <literal>\n</>
-in plpython function bodies (Michael Fuhr)</para>
-<para>
- This prevents syntax errors when plpython code is written on a Windows or
- Mac client.
-</para>
-</listitem>
-<listitem><para>Allow SPI cursors to handle utility commands that return rows,
-such as <command>EXPLAIN</> (Tom)</para></listitem>
-<listitem><para>Fix <command>CLUSTER</> failure after <command>ALTER TABLE
-SET WITHOUT OIDS</> (Tom)</para></listitem>
-<listitem><para>Reduce memory usage of <command>ALTER TABLE ADD COLUMN</>
-(Neil)</para></listitem>
-<listitem><para>Fix <command>ALTER LANGUAGE RENAME</> (Tom)</para></listitem>
-<listitem><para>Document the Windows-only <literal>register</> and
-<literal>unregister</> options of <application>pg_ctl</> (Magnus)</para></listitem>
-<listitem><para>Ensure operations done during backend shutdown are counted by
-statistics collector</para>
-<para>
-This is expected to resolve reports of <application>pg_autovacuum</>
-not vacuuming the system catalogs often enough &mdash; it was not being
-told about catalog deletions caused by temporary table removal during
-backend exit.
-</para></listitem>
-<listitem><para>Change the Windows default for configuration parameter
-<varname>log_destination</> to <option>eventlog</> (Magnus)</para>
-<para>
-By default, a server running on Windows will now send log output to the
-Windows event logger rather than standard error.
-</para></listitem>
-<listitem><para>Make Kerberos authentication work on Windows (Magnus)</para></listitem>
-<listitem><para>Allow <command>ALTER DATABASE RENAME</> by superusers
-who aren't flagged as having CREATEDB privilege (Tom)</para></listitem>
-<listitem><para>Modify WAL log entries for <command>CREATE</> and
-<command>DROP DATABASE</> to not specify absolute paths (Tom)</para>
-<para>This allows point-in-time recovery on a different machine with possibly
-different database location.  Note that <command>CREATE TABLESPACE</> still
-poses a hazard in such situations.
-</para></listitem>
-<listitem><para>Fix crash from a backend exiting with an open transaction
-that created a table and opened a cursor on it (Tom)</para></listitem>
-<listitem><para>Fix <function>array_map()</> so it can call PL functions
-(Tom)</para></listitem>
-<listitem><para>Several <filename>contrib/tsearch2</> and
-<filename>contrib/btree_gist</> fixes (Teodor)
-</para></listitem>
-<listitem><para>Fix crash of some <filename>contrib/pgcrypto</>
-functions on some platforms (Marko Kreen)</para></listitem>
-<listitem><para>Fix <filename>contrib/intagg</> for 64-bit platforms
-(Tom)</para></listitem>
-<listitem><para>Fix ecpg bugs in parsing of <command>CREATE</> statement
-(Michael)</para></listitem>
-<listitem><para>Work around gcc bug on powerpc and amd64 causing problems in
-ecpg (Christof Petig)</para></listitem>
-<listitem><para>Do not use locale-aware versions of <function>upper()</>,
-<function>lower()</>, and <function>initcap()</> when the locale is
-<literal>C</> (Bruce)</para>
-<para>
- This allows these functions to work on platforms that generate errors
- for non-7-bit data when the locale is <literal>C</>.
-</para></listitem>
-<listitem><para>Fix <function>quote_ident()</> to quote names that match keywords (Tom)</para></listitem>
-<listitem><para>Fix <function>to_date()</> to behave reasonably when
-<literal>CC</> and <literal>YY</> fields are both used (Karel)</para></listitem>
-<listitem><para>Prevent <function>to_char(interval)</> from failing
-when given a zero-month interval (Tom)</para></listitem>
-<listitem><para>Fix wrong week returned by <function>date_trunc('week')</>
-(Bruce)</para>
-<para>
-<function>date_trunc('week')</>
-returned the wrong year for the first few days of January in some years.
-</para></listitem>
-<listitem><para>Use the correct default mask length for class <literal>D</>
-addresses in <type>INET</> data types (Tom)</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0-1">
-  <title>Release 8.0.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-01-31</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.0.0, including several
-   security-related issues.
-   For information about new features in the 8.0 major release, see
-   <xref linkend="release-8-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.0.1</title>
-
-   <para>
-    A dump/restore is not required for those running 8.0.0.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Disallow <command>LOAD</> to non-superusers</para>
-<para>
-On platforms that will automatically execute initialization functions of a
-shared library (this includes at least Windows and ELF-based Unixen),
-<command>LOAD</> can be used to make the server execute arbitrary code.
-Thanks to NGS Software for reporting this.</para></listitem>
-<listitem><para>Check that creator of an aggregate function has the right to
-execute the specified transition functions</para>
-<para>
-This oversight made it possible to bypass denial of EXECUTE
-permission on a function.</para></listitem>
-<listitem><para>Fix security and 64-bit issues in
-contrib/intagg</para></listitem>
-<listitem><para>Add needed STRICT marking to some contrib functions (Kris
-Jurka)</para></listitem>
-<listitem><para>Avoid buffer overrun when plpgsql cursor declaration has too
-many parameters (Neil)</para></listitem>
-<listitem><para>Make <command>ALTER TABLE ADD COLUMN</> enforce domain
-constraints in all cases</para></listitem>
-<listitem><para>Fix planning error for FULL and RIGHT outer joins</para>
-<para>
-The result of the join was mistakenly supposed to be sorted the same as the
-left input.  This could not only deliver mis-sorted output to the user, but
-in case of nested merge joins could give outright wrong answers.
-</para></listitem>
-<listitem><para>Improve planning of grouped aggregate queries</para></listitem>
-<listitem><para><command>ROLLBACK TO <replaceable>savepoint</></command>
-closes cursors created since the savepoint</para></listitem>
-<listitem><para>Fix inadequate backend stack size on Windows</para></listitem>
-<listitem><para>Avoid SHGetSpecialFolderPath() on Windows
-(Magnus)</para></listitem>
-<listitem><para>Fix some problems in running pg_autovacuum as a Windows
-service (Dave Page)</para></listitem>
-<listitem><para>Multiple minor bug fixes in
-pg_dump/pg_restore</para></listitem>
-<listitem><para>Fix ecpg segfault with named structs used in
-typedefs (Michael)</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-0">
-  <title>Release 8.0</title>
-
-  <note>
-   <title>Release Date</title>
-   <simpara>2005-01-19</simpara>
-  </note>
-
-  <sect2>
-   <title>Overview</title>
-
-   <para>
-    Major changes in this release:
-   </para>
-
-   <variablelist>
-    <varlistentry>
-     <term>
-      Microsoft Windows Native Server
-     </term>
-
-     <listitem>
-      <para>
-       This is the first <productname>PostgreSQL</productname> release
-       to run natively on <trademark class="registered">Microsoft Windows</> as
-       a server. It can run as a <productname>Windows</> service. This
-       release supports NT-based Windows releases like
-       <productname>Windows 2000 SP4</>, <productname>Windows XP</>, and
-       <productname>Windows 2003</>. Older releases like
-       <productname>Windows 95</>, <productname>Windows 98</>, and
-       <productname>Windows ME</> are not supported because these operating
-       systems do not have the infrastructure to support
-       <productname>PostgreSQL</productname>. A separate installer
-       project has been created to ease installation on
-       <productname>Windows</> &mdash; see <ulink
-       url="http://www.postgresql.org/ftp/win32/"></ulink>.
-      </para>
-
-      <para>
-       Although tested throughout our release cycle, the Windows port
-       does not have the benefit of years of use in production
-       environments that <productname>PostgreSQL</productname> has on
-       Unix platforms.  Therefore it should be treated with the same
-       level of caution as you would a new product.
-      </para>
-
-      <para>
-       Previous releases required the Unix emulation toolkit
-       <productname>Cygwin</> in order to run the server on Windows
-       operating systems.  <productname>PostgreSQL</productname> has
-       supported native clients on Windows for many years.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Savepoints
-     </term>
-
-     <listitem>
-      <para>
-       Savepoints allow specific parts of a transaction to be aborted
-       without affecting the remainder of the transaction. Prior
-       releases had no such capability; there was no way to recover
-       from a statement failure within a transaction except by
-       aborting the whole transaction. This feature is valuable for
-       application writers who require error recovery within a
-       complex transaction.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Point-In-Time Recovery
-     </term>
-
-     <listitem>
-      <para>
-       In previous releases there was no way to recover from disk
-       drive failure except to restore from a previous backup or use
-       a standby replication server.  Point-in-time recovery allows
-       continuous backup of the server.  You can recover either to
-       the point of failure or to some transaction in the past.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Tablespaces
-     </term>
-
-     <listitem>
-      <para>
-       Tablespaces allow administrators to select different file systems
-       for storage of individual tables, indexes, and databases.
-       This improves performance and control over disk space
-       usage. Prior releases used <application>initlocation</> and
-       manual symlink management for such tasks.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Improved Buffer Management, <command>CHECKPOINT</command>,
-      <command>VACUUM</command>
-     </term>
-
-     <listitem>
-      <para>
-       This release has a more intelligent buffer replacement strategy,
-       which will make better use of available shared buffers and
-       improve performance. The performance impact of vacuum and
-       checkpoints is also lessened.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Change Column Types
-     </term>
-
-     <listitem>
-      <para>
-       A column's data type can now be changed with <command>ALTER
-       TABLE</command>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      New Perl Server-Side Language
-     </term>
-
-     <listitem>
-      <para>
-       A new version of the <application>plperl</> server-side language now
-       supports a persistent shared storage area, triggers, returning records
-       and arrays of records, and SPI calls to access the database.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-       Comma-separated-value (CSV) support in <command>COPY</command>
-     </term>
-
-     <listitem>
-      <para>
-       <command>COPY</command> can now read and write
-       comma-separated-value files. It has the flexibility to
-       interpret nonstandard quoting and separation characters too.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </sect2>
-
-  <sect2>
-   <title>Migration to Version 8.0</title>
-
-   <para>
-    A dump/restore using <application>pg_dump</application> is
-    required for those wishing to migrate data from any previous
-    release.
-   </para>
-
-   <para>
-    Observe the following incompatibilities:
-   </para>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      In <option>READ COMMITTED</> serialization mode, volatile functions
-      now see the results of concurrent transactions committed up to the
-      beginning of each statement within the function, rather than up to the
-      beginning of the interactive command that called the function.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Functions declared <option>STABLE</> or <option>IMMUTABLE</> always
-      use the snapshot of the calling query, and therefore do not see the
-      effects of actions taken after the calling query starts, whether in
-      their own transaction or other transactions.  Such a function must be
-      read-only, too, meaning that it cannot use any SQL commands other than
-      <command>SELECT</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Nondeferred <option>AFTER</> triggers are now fired immediately
-      after completion of the triggering query, rather than upon
-      finishing the current interactive command. This makes a
-      difference when the triggering query occurred within a function:
-      the trigger is invoked before the function proceeds to its next
-      operation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Server configuration parameters <varname>virtual_host</> and
-      <varname>tcpip_socket</> have been replaced with a more general
-      parameter <varname>listen_addresses</>. Also, the server now listens on
-      <literal>localhost</> by default, which eliminates the need for the
-      <literal>-i</> postmaster switch in many scenarios.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Server configuration parameters <varname>SortMem</> and
-      <varname>VacuumMem</> have been renamed to <varname>work_mem</>
-      and <varname>maintenance_work_mem</> to better reflect their
-      use. The original names are still supported in
-      <command>SET</command> and <command>SHOW</command>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Server configuration parameters <varname>log_pid</>,
-      <varname>log_timestamp</>, and <varname>log_source_port</> have been
-      replaced with a more general parameter <varname>log_line_prefix</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Server configuration parameter <varname>syslog</> has been
-      replaced with a more logical <varname>log_destination</> variable to
-      control the log output destination.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Server configuration parameter <varname>log_statement</> has been
-      changed so it can selectively log just database modification or
-      data definition statements.  Server configuration parameter
-      <varname>log_duration</> now prints only when <varname>log_statement</>
-      prints the query.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Server configuration parameter <varname>max_expr_depth</> parameter has
-      been replaced with <varname>max_stack_depth</> which measures the
-      physical stack size rather than the expression nesting depth. This
-      helps prevent session termination due to stack overflow caused by
-      recursive functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The <function>length()</> function no longer counts trailing spaces in
-      <type>CHAR(n)</> values.
-     </para>
-    </listitem>
-
-   <listitem>
-    <para>
-     Casting an integer to <type>BIT(N)</> selects the rightmost N bits of the
-     integer, not the leftmost N bits as before.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Updating an element or slice of a NULL array value now produces
-     a nonnull array result, namely an array containing
-     just the assigned-to positions.
-    </para>
-   </listitem>
-
-    <listitem>
-     <para>
-      Syntax checking of array input values has been tightened up
-      considerably. Junk that was previously allowed in odd places with
-      odd results now causes an error. Empty-string element values
-      must now be written as <literal>""</>, rather than writing nothing.
-      Also changed behavior with respect to whitespace surrounding
-      array elements: trailing whitespace is now ignored, for symmetry
-      with leading whitespace (which has always been ignored).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Overflow in integer arithmetic operations is now detected and
-      reported as an error.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The arithmetic operators associated with the single-byte
-      <type>"char"</> data type have been removed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The <function>extract()</> function (also called
-      <function>date_part</>) now returns the proper year for BC dates.
-      It previously returned one less than the correct year. The
-      function now also returns the proper values for millennium and
-      century.
-     </para>
-    </listitem>
-
-   <listitem>
-    <para>
-     <type>CIDR</> values now must have their nonmasked bits be zero.
-     For example, we no longer allow
-     <literal>204.248.199.1/31</literal> as a <type>CIDR</> value. Such
-     values should never have been accepted by
-     <productname>PostgreSQL</productname> and will now be rejected.
-    </para>
-   </listitem>
-
-    <listitem>
-     <para>
-      <command>EXECUTE</command> now returns a completion tag that
-      matches the executed statement.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <application>psql</>'s <command>\copy</> command now reads or
-      writes to the query's <literal>stdin/stdout</>, rather than
-      <application>psql</>'s <literal>stdin/stdout</>. The previous
-      behavior can be accessed via new
-      <option>pstdin</>/<option>pstdout</> parameters.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-     The JDBC client interface has been removed from the core
-     distribution, and is now hosted at <ulink url=
-     "http://jdbc.postgresql.org"></ulink>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-     The Tcl client interface has also been removed. There are several
-     Tcl interfaces now hosted at <ulink url=
-     "http://gborg.postgresql.org"></ulink>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The server now uses its own time zone database, rather than the
-      one supplied by the operating system. This will provide consistent
-      behavior across all platforms.  In most cases, there should be
-      little noticeable difference in time zone behavior, except that
-      the time zone names used by <command>SET</>/<command>SHOW</>
-      <varname>TimeZone</> might be different from what your platform provides.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <application>Configure</>'s threading option no longer requires
-      users to run tests or edit configuration files; threading options
-      are now detected automatically.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Now that tablespaces have been implemented,
-      <application>initlocation</> has been removed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The API for user-defined GiST indexes has been changed. The
-      Union and PickSplit methods are now passed a pointer to a
-      special <structname>GistEntryVector</structname> structure,
-      rather than a <type>bytea</type>.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-  </sect2>
-
- <sect2>
-  <title>Deprecated Features</title>
-
-  <para>
-    Some aspects of <productname>PostgreSQL</productname>'s behavior
-    have been determined to be suboptimal. For the sake of backward
-    compatibility these have not been removed in 8.0, but they are
-    considered deprecated and will be removed in the next major
-    release.
-    </para>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      The 8.1 release will remove the <function>to_char()</> function
-      for intervals.
-     </para>
-    </listitem>
-
-     <listitem>
-      <para>
-       The server now warns of empty strings passed to
-       <type>oid</type>/<type>float4</type>/<type>float8</type> data
-       types, but continues to interpret them as zeroes as before.
-       In the next major release, empty strings will be considered
-       invalid input for these data types.
-      </para>
-     </listitem>
-
-    <listitem>
-     <para>
-      By default, tables in <productname>PostgreSQL</productname> 8.0
-      and earlier are created with <type>OID</>s. In the next release,
-      this will <emphasis>not</emphasis> be the case: to create a table
-      that contains <type>OID</>s, the <option>WITH OIDS</> clause must
-      be specified or the <varname>default_with_oids</varname>
-      configuration parameter must be set. Users are encouraged to
-      explicitly specify <option>WITH OIDS</> if their tables
-      require OIDs for compatibility with future releases of
-      <productname>PostgreSQL</productname>.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-    Below you will find a detailed account of the changes between
-    release 8.0 and the previous major release.
-   </para>
-
-   <sect3>
-    <title>Performance Improvements</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Support cross-data-type index usage (Tom)
-      </para>
-      <para>
-       Before this change, many queries would not use an index if the data
-       types did not match exactly. This improvement makes index usage more
-       intuitive and consistent.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New buffer replacement strategy that improves caching (Jan)
-      </para>
-      <para>
-       Prior releases used a least-recently-used (LRU) cache to keep
-       recently referenced pages in memory. The LRU algorithm
-       did not consider the number of times a specific cache entry was
-       accessed, so large table scans could force out useful cache pages.
-       The new cache algorithm uses four separate lists to track most
-       recently used and most frequently used cache pages and dynamically
-       optimize their replacement based on the work load. This should
-       lead to much more efficient use of the shared buffer cache.
-       Administrators who have tested shared buffer sizes in the past
-       should retest with this new cache replacement policy.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add subprocess to write dirty buffers periodically to reduce
-       checkpoint writes (Jan)
-      </para>
-      <para>
-       In previous releases, the checkpoint process, which runs every few
-       minutes, would write all dirty buffers to the operating system's
-       buffer cache then flush all dirty operating system buffers to
-       disk. This resulted in a periodic spike in disk usage that often
-       hurt performance. The new code uses a background writer to trickle
-       disk writes at a steady pace so checkpoints have far fewer dirty
-       pages to write to disk. Also, the new code does not issue a global
-       <function>sync()</> call, but instead <function>fsync()</>s just
-       the files written since the last checkpoint. This should improve
-       performance and minimize degradation during checkpoints.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add ability to prolong vacuum to reduce performance impact (Jan)
-      </para>
-      <para>
-       On busy systems, <command>VACUUM</command> performs many I/O
-       requests which can hurt performance for other users. This
-       release allows you to slow down <command>VACUUM</command> to
-       reduce its impact on other users, though this increases the
-       total duration of <command>VACUUM</command>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve B-tree index performance for duplicate keys (Dmitry Tkach, Tom)
-      </para>
-      <para>
-       This improves the way indexes are scanned when many duplicate
-       values exist in the index.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use dynamically-generated table size estimates while planning (Tom)
-      </para>
-      <para>
-       Formerly the planner estimated table sizes using the values seen
-       by the last <command>VACUUM</command> or <command>ANALYZE</command>,
-       both as to physical table size (number of pages) and number of rows.
-       Now, the current physical table size is obtained from the kernel,
-       and the number of rows is estimated by multiplying the table size
-       by the row density (rows per page) seen by the last
-       <command>VACUUM</command> or <command>ANALYZE</command>.  This should
-       produce more reliable estimates in cases where the table size has
-       changed significantly since the last housekeeping command.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improved index usage with <literal>OR</> clauses (Tom)
-      </para>
-      <para>
-       This allows the optimizer to use indexes in statements with many OR
-       clauses that would not have been indexed in the past.  It can also use
-       multi-column indexes where the first column is specified and the second
-       column is part of an <literal>OR</> clause.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve matching of partial index clauses (Tom)
-      </para>
-      <para>
-       The server is now smarter about using partial indexes in queries
-       involving complex <option>WHERE</> clauses.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve performance of the GEQO optimizer (Tom)
-      </para>
-      <para>
-       The GEQO optimizer is used to plan queries involving many tables (by
-       default, twelve or more). This release speeds up the way queries are
-       analyzed to decrease time spent in optimization.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Miscellaneous optimizer improvements
-      </para>
-      <para>
-       There is not room here to list all the minor improvements made, but
-       numerous special cases work better than in prior releases.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve lookup speed for C functions (Tom)
-      </para>
-      <para>
-       This release uses a hash table to lookup information for dynamically
-       loaded C functions. This improves their speed so they perform nearly as
-       quickly as functions that are built into the server executable.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add type-specific <command>ANALYZE</command> statistics
-       capability (Mark Cave-Ayland)
-      </para>
-      <para>
-       This feature allows more flexibility in generating statistics
-       for nonstandard data types.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <command>ANALYZE</command> now collects statistics for
-       expression indexes (Tom)
-      </para>
-      <para>
-       Expression indexes (also called functional indexes) allow users to
-       index not just columns but the results of expressions and function
-       calls. With this release, the optimizer can gather and use statistics
-       about the contents of expression indexes.  This will greatly improve
-       the quality of planning for queries in which an expression index is
-       relevant.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New two-stage sampling method for <command>ANALYZE</command>
-       (Manfred Koizar)
-      </para>
-      <para>
-       This gives better statistics when the density of valid rows is very
-       different in different regions of a table.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Speed up <command>TRUNCATE</command> (Tom)
-      </para>
-      <para>
-       This buys back some of the performance loss observed in 7.4, while still
-       keeping <command>TRUNCATE</command> transaction-safe.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Server Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add WAL file archiving and point-in-time recovery (Simon Riggs)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add tablespaces so admins can control disk layout (Gavin)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a built-in log rotation program (Andreas Pflug)
-      </para>
-      <para>
-       It is now possible to log server messages conveniently without
-       relying on either <application>syslog</> or an external log
-       rotation program.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new read-only server configuration parameters to show server
-       compile-time settings: <varname>block_size</>,
-       <varname>integer_datetimes</>, <varname>max_function_args</>,
-       <varname>max_identifier_length</>, <varname>max_index_keys</>  (Joe)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make quoting of <literal>sameuser</>, <literal>samegroup</>, and
-       <literal>all</> remove special meaning of these terms in
-       <filename>pg_hba.conf</> (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use clearer IPv6 name <literal>::1/128</> for
-       <literal>localhost</> in default <filename>pg_hba.conf</> (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use CIDR format in <filename>pg_hba.conf</> examples (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Rename server configuration parameters <varname>SortMem</> and
-       <varname>VacuumMem</> to <varname>work_mem</> and
-       <varname>maintenance_work_mem</> (Old names still supported) (Tom)
-      </para>
-      <para>
-       This change was made to clarify that bulk operations such as index and
-       foreign key creation use <varname>maintenance_work_mem</>, while
-       <varname>work_mem</> is for workspaces used during query execution.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow logging of session disconnections using server configuration
-       <varname>log_disconnections</> (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new server configuration parameter <varname>log_line_prefix</> to
-       allow control of information emitted in each log line (Andrew)
-      </para>
-      <para>
-       Available information includes user name, database name, remote IP
-       address, and session start time.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove server configuration parameters <varname>log_pid</>,
-       <varname>log_timestamp</>, <varname>log_source_port</>; functionality
-       superseded by <varname>log_line_prefix</> (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Replace the <varname>virtual_host</> and <varname>tcpip_socket</>
-       parameters with a unified <varname>listen_addresses</> parameter
-       (Andrew, Tom)
-      </para>
-      <para>
-       <varname>virtual_host</> could only specify a single IP address to
-       listen on.  <varname>listen_addresses</> allows multiple addresses
-       to be specified.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Listen on localhost by default, which eliminates the need for the
-       <option>-i</> postmaster switch in many scenarios (Andrew)
-      </para>
-      <para>
-       Listening on localhost (<literal>127.0.0.1</>) opens no new
-       security holes but allows configurations like Windows and JDBC,
-       which do not support local sockets, to work without special
-       adjustments.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <varname>syslog</> server configuration parameter, and add more
-       logical <varname>log_destination</> variable to control log output
-       location (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change server configuration parameter <varname>log_statement</> to take
-       values <varname>all</>, <varname>mod</>, <varname>ddl</>, or
-       <varname>none</> to select which queries are logged (Bruce)
-      </para>
-      <para>
-       This allows administrators to log only data definition changes or
-       only data modification statements.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Some logging-related configuration parameters could formerly be adjusted
-       by ordinary users, but only in the <quote>more verbose</> direction.
-       They are now treated more strictly: only superusers can set them.
-       However, a superuser can use <command>ALTER USER</> to provide per-user
-       settings of these values for non-superusers.  Also, it is now possible
-       for superusers to set values of superuser-only configuration parameters
-       via <literal>PGOPTIONS</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow configuration files to be placed outside the data directory (mlw)
-      </para>
-      <para>
-       By default, configuration files are kept in the cluster's top directory.
-       With this addition, configuration files can be placed outside the
-       data directory, easing administration.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Plan prepared queries only when first executed so constants can be
-       used for statistics (Oliver Jowett)
-      </para>
-      <para>
-       Prepared statements plan queries once and execute them many
-       times. While prepared queries avoid the overhead of re-planning
-       on each use, the quality of the plan suffers from not knowing the exact
-       parameters to be used in the query.  In this release, planning of
-       unnamed prepared statements is delayed until the first execution,
-       and the actual parameter values of that execution are used as
-       optimization hints.  This allows use of out-of-line parameter passing
-       without incurring a performance penalty.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>DECLARE CURSOR</command> to take parameters
-       (Oliver Jowett)
-      </para>
-      <para>
-       It is now useful to issue <command>DECLARE CURSOR</command> in a
-       <function>Parse</> message with parameters. The parameter values
-       sent at <function>Bind</> time will be substituted into the
-       execution of the cursor's query.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix hash joins and aggregates of <type>inet</type> and
-       <type>cidr</type> data types (Tom)
-      </para>
-      <para>
-       Release 7.4 handled hashing of mixed <type>inet</type> and
-       <type>cidr</type> values incorrectly.  (This bug did not exist
-       in prior releases because they wouldn't try to hash either
-       data type.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <varname>log_duration</> print only when <varname>log_statement</>
-       prints the query (Ed L.)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Query Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add savepoints (nested transactions) (Alvaro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Unsupported isolation levels are now accepted and promoted to the
-       nearest supported level (Peter)
-      </para>
-      <para>
-       The SQL specification states that if a database doesn't support a
-       specific isolation level, it should use the next more restrictive level.
-       This change complies with that recommendation.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>BEGIN WORK</command> to specify transaction
-       isolation levels like <command>START TRANSACTION</command> does
-       (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix table permission checking for cases in which rules generate
-       a query type different from the originally submitted query (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Implement dollar quoting to simplify single-quote usage (Andrew, Tom,
-       David Fetter)
-      </para>
-      <para>
-       In previous releases, because single quotes had to be used to
-       quote a function's body, the use of single quotes inside the
-       function text required use of two single quotes or other error-prone
-       notations. With this release we add the ability to use "dollar
-       quoting" to quote a block of text.  The ability to use different
-       quoting delimiters at different nesting levels greatly simplifies
-       the task of quoting correctly, especially in complex functions.
-       Dollar quoting can be used anywhere quoted text is needed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <literal>CASE val WHEN compval1 THEN ...</> evaluate <literal>val</> only once (Tom)
-      </para>
-      <para>
-       <option>CASE</> no longer evaluates the tested expression multiple
-       times. This has benefits when the expression is complex or is
-       volatile.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Test <option>HAVING</> before computing target list of an
-       aggregate query (Tom)
-      </para>
-      <para>
-       Fixes improper failure of cases such as <literal>SELECT SUM(win)/SUM(lose)
-       ... GROUP BY ... HAVING SUM(lose) &gt; 0</>.  This should work but formerly
-       could fail with divide-by-zero.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Replace <varname>max_expr_depth</> parameter with
-       <varname>max_stack_depth</> parameter, measured in kilobytes of stack
-       size (Tom)
-      </para>
-      <para>
-      This gives us a fairly bulletproof defense against crashing due to
-      runaway recursive functions. Instead of measuring the depth of expression
-      nesting, we now directly measure the size of the execution stack.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow arbitrary row expressions (Tom)
-      </para>
-      <para>
-       This release allows SQL expressions to contain arbitrary composite
-       types, that is, row values. It also allows functions to more easily
-       take rows as arguments and return row values.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <option>LIKE</>/<option>ILIKE</> to be used as the operator
-       in row and subselect comparisons (Fabien Coelho)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Avoid locale-specific case conversion of basic ASCII letters in
-       identifiers and keywords (Tom)
-      </para>
-      <para>
-       This solves the <quote>Turkish problem</> with mangling of words
-       containing <literal>I</> and  <literal>i</>.  Folding of characters
-       outside the 7-bit-ASCII set is still locale-aware.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve syntax error reporting (Fabien, Tom)
-      </para>
-      <para>
-       Syntax error reports are more useful than before.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change <command>EXECUTE</command> to return a completion tag
-       matching the executed statement (Kris Jurka)
-      </para>
-      <para>
-       Previous releases return an <command>EXECUTE</command> tag for
-       any <command>EXECUTE</command> call. In this release, the tag
-       returned will reflect the command executed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Avoid emitting <option>NATURAL CROSS JOIN</> in rule listings (Tom)
-      </para>
-      <para>
-       Such a clause makes no logical sense, but in some cases the rule
-       decompiler formerly produced this syntax.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Object Manipulation Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <command>COMMENT ON</> for casts, conversions, languages,
-       operator classes, and large objects (Christopher)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new server configuration parameter <varname>default_with_oids</> to
-       control whether tables are created with <type>OID</>s by default (Neil)
-      </para>
-      <para>
-       This allows administrators to control whether <command>CREATE
-       TABLE</command> commands create tables with or without <type>OID</>
-       columns by default.  (Note: the current factory default setting for
-       <varname>default_with_oids</> is <literal>TRUE</>, but the default
-       will become <literal>FALSE</> in future releases.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>WITH</> / <option>WITHOUT OIDS</> clause to
-       <command>CREATE TABLE AS</command> (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>ALTER TABLE DROP COLUMN</> to drop an <type>OID</>
-       column (<command>ALTER TABLE SET WITHOUT OIDS</> still works)
-       (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow composite types as table columns (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>ALTER ... ADD COLUMN</> with defaults and
-       <option>NOT NULL</> constraints; works per SQL spec (Rod)
-      </para>
-      <para>
-       It is now possible for <option>ADD COLUMN</> to create a column
-       that is not initially filled with NULLs, but with a specified
-       default value.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>ALTER COLUMN TYPE</> to change column's type (Rod)
-      </para>
-      <para>
-       It is now possible to alter a column's data type without dropping
-       and re-adding the column.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow multiple <command>ALTER</> actions in a single <command>ALTER
-       TABLE</command> command (Rod)
-      </para>
-      <para>
-       This is particularly useful for <command>ALTER</> commands that
-       rewrite the table (which include <option>ALTER COLUMN TYPE</> and
-       <option>ADD COLUMN</> with a default). By grouping
-       <command>ALTER</> commands together, the table need be rewritten
-       only once.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>ALTER TABLE</command> to add <type>SERIAL</type>
-       columns (Tom)
-      </para>
-      <para>
-       This falls out from the new capability of specifying defaults for new
-       columns.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow changing the owners of aggregates, conversions, databases,
-       functions, operators, operator classes, schemas, types, and tablespaces
-       (Christopher, Euler Taveira de Oliveira)
-      </para>
-      <para>
-       Previously this required modifying the system tables directly.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow temporary object creation to be limited to <option>SECURITY
-       DEFINER</> functions (Sean Chittenden)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>ALTER TABLE ... SET WITHOUT CLUSTER</> (Christopher)
-      </para>
-      <para>
-       Prior to this release, there was no way to clear an auto-cluster
-       specification except to modify the system tables.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Constraint/Index/<type>SERIAL</> names are now
-       <replaceable>table_column_type</>
-       with numbers appended to guarantee uniqueness within the schema
-       (Tom)
-      </para>
-      <para>
-       The SQL specification states that such names should be unique
-       within a schema.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>pg_get_serial_sequence()</> to return a
-       <type>SERIAL</> column's sequence name (Christopher)
-      </para>
-      <para>
-       This allows automated scripts to reliably find the <type>SERIAL</>
-       sequence name.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Warn when primary/foreign key data type mismatch requires costly lookup
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New <command>ALTER INDEX</> command to allow moving of indexes
-       between tablespaces (Gavin)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <command>ALTER TABLE OWNER</> change dependent sequence
-       ownership too (Alvaro)
-      </para>
-     </listitem>
-
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Utility Command Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow <command>CREATE SCHEMA</command> to create triggers,
-       indexes, and sequences (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>ALSO</> keyword to <command>CREATE RULE</command> (Fabien
-       Coelho)
-      </para>
-      <para>
-       This allows <option>ALSO</> to be added to rule creation to contrast it with
-       <option>INSTEAD</> rules.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>NOWAIT</> option to <command>LOCK</command> (Tatsuo)
-      </para>
-      <para>
-       This allows the <command>LOCK</command> command to fail if it
-       would have to wait for the requested lock.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>COPY</command> to read and write
-       comma-separated-value (CSV) files (Andrew, Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Generate error if the <command>COPY</command> delimiter and NULL
-       string conflict (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <command>GRANT</command>/<command>REVOKE</command> behavior
-       follows the SQL spec more closely
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Avoid locking conflict between <command>CREATE INDEX</command>
-       and <command>CHECKPOINT</command> (Tom)
-      </para>
-      <para>
-       In 7.3 and 7.4, a long-running B-tree index build could block concurrent
-       <command>CHECKPOINT</>s from completing, thereby causing WAL bloat because the
-       WAL log could not be recycled.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Database-wide <command>ANALYZE</command> does not hold locks
-       across tables (Tom)
-      </para>
-      <para>
-       This reduces the potential for deadlocks against other backends
-       that want exclusive locks on tables.  To get the benefit of this
-       change, do not execute database-wide <command>ANALYZE</command>
-       inside a transaction block (<command>BEGIN</command> block); it
-       must be able to commit and start a new transaction for each
-       table.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <command>REINDEX</command> does not exclusively lock the index's
-       parent table anymore
-      </para>
-      <para>
-       The index itself is still exclusively locked, but readers of the
-       table can continue if they are not using the particular index
-       being rebuilt.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Erase MD5 user passwords when a user is renamed (Bruce)
-      </para>
-      <para>
-       <productname>PostgreSQL</productname> uses the user name as salt
-       when encrypting passwords via MD5. When a user's name is changed,
-       the salt will no longer match the stored MD5 password, so the
-       stored password becomes useless.  In this release a notice is
-       generated and the password is cleared.  A new password must then
-       be assigned if the user is to be able to log in with a password.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New <application>pg_ctl</> <option>kill</> option for Windows (Andrew)
-      </para>
-      <para>
-       Windows does not have a <literal>kill</> command to send signals to
-       backends so this capability was added to <application>pg_ctl</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Information schema improvements
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>--pwfile</> option to
-       <application>initdb</application> so the initial password can be
-       set by GUI tools (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Detect locale/encoding mismatch in
-       <application>initdb</application> (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>register</> command to <application>pg_ctl</> to
-       register Windows operating system service (Dave Page)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Data Type and Function Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       More complete support for composite types (row types)  (Tom)
-      </para>
-      <para>
-       Composite values can be used in many places where only scalar values
-       worked before.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reject nonrectangular array values as erroneous (Joe)
-      </para>
-      <para>
-       Formerly, <function>array_in</> would silently build a
-       surprising result.
-      </para>
-     </listitem>
-
-      <listitem>
-       <para>
-        Overflow in integer arithmetic operations is now detected (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The arithmetic operators associated with the single-byte
-        <type>"char"</> data type have been removed.
-       </para>
-       <para>
-        Formerly, the parser would select these operators in many situations
-        where an <quote>unable to select an operator</> error would be more
-        appropriate, such as <literal>null * null</>.  If you actually want
-        to do arithmetic on a <type>"char"</> column, you can cast it to
-        integer explicitly.
-       </para>
-      </listitem>
-
-     <listitem>
-       <para>
-        Syntax checking of array input values considerably tightened up (Joe)
-       </para>
-      <para>
-        Junk that was previously allowed in odd places with odd results
-        now causes an <literal>ERROR</>, for example, non-whitespace
-        after the closing right brace.
-       </para>
-     </listitem>
-
-     <listitem>
-       <para>
-        Empty-string array element values must now be written as
-        <literal>""</>, rather than writing nothing (Joe)
-       </para>
-      <para>
-        Formerly, both ways of writing an empty-string element value were
-        allowed, but now a quoted empty string is required.  The case where
-        nothing at all appears will probably be considered to be a NULL
-        element value in some future release.
-       </para>
-     </listitem>
-
-     <listitem>
-       <para>
-        Array element trailing whitespace is now ignored (Joe)
-       </para>
-      <para>
-        Formerly leading whitespace was ignored, but trailing whitespace
-        between an element value and the delimiter or right brace was
-        significant.  Now trailing whitespace is also ignored.
-       </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Emit array values with explicit array bounds when lower bound is not one
-       (Joe)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Accept <literal>YYYY-monthname-DD</> as a date string (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <function>netmask</> and <function>hostmask</> functions
-       return maximum-length mask length (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change factorial function to return <type>numeric</type> (Gavin)
-      </para>
-      <para>
-       Returning <type>numeric</type> allows the factorial function to
-       work for a wider range of input values.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>to_char</>/<function>to_date()</> date conversion
-       improvements (Kurt Roeckx, Fabien Coelho)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <function>length()</> disregard trailing spaces in
-       <type>CHAR(n)</> (Gavin)
-      </para>
-      <para>
-       This change was made to improve consistency: trailing spaces are
-       semantically insignificant in <type>CHAR(n)</> data, so they
-       should not be counted by <function>length()</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Warn about empty string being passed to
-       <type>OID</>/<type>float4</>/<type>float8</> data types (Neil)
-      </para>
-      <para>
-       8.1 will throw an error instead.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow leading or trailing whitespace in
-       <type>int2</>/<type>int4</>/<type>int8</>/<type>float4</>/<type>float8</>
-       input routines
-       (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Better support for IEEE <literal>Infinity</> and <literal>NaN</>
-       values in <type>float4</type>/<type>float8</type> (Neil)
-      </para>
-      <para>
-       These should now work on all platforms that support IEEE-compliant
-       floating point arithmetic.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>week</> option to <function>date_trunc()</> (Robert Creager)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <function>to_char</function> for <literal>1 BC</>
-       (previously it returned <literal>1 AD</>) (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <function>date_part(year)</> for BC dates (previously it
-       returned one less than the correct year) (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <function>date_part()</> to return the proper millennium and
-       century (Fabien Coelho)
-      </para>
-      <para>
-       In previous versions, the century and millennium results had a wrong
-       number and started in the wrong year, as compared to standard
-       reckoning of such things.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>ceiling()</> as an alias for <function>ceil()</>,
-       and <function>power()</> as an alias for <function>pow()</> for
-       standards compliance (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change <function>ln()</>, <function>log()</>,
-       <function>power()</>, and <function>sqrt()</> to emit the correct
-       <literal>SQLSTATE</> error codes for certain error conditions, as
-       specified by SQL:2003 (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>width_bucket()</> function as defined by SQL:2003 (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>generate_series()</> functions to simplify working
-       with numeric sets (Joe)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <function>upper/lower/initcap()</> functions to work with
-       multibyte encodings (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add boolean and bitwise integer <option>AND</>/<option>OR</>
-       aggregates (Fabien Coelho)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New session information functions to return network addresses for client
-       and server (Sean Chittenden)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add function to determine the area of a closed path (Sean Chittenden)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add function to send cancel request to other backends (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <type>interval</> plus <type>datetime</> operators (Tom)
-      </para>
-      <para>
-       The reverse ordering, <type>datetime</> plus <type>interval</>,
-       was already supported, but both are required by the SQL standard.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Casting an integer to <type>BIT(N)</> selects the rightmost N bits
-       of the integer
-       (Tom)
-      </para>
-      <para>
-       In prior releases, the leftmost N bits were selected, but this was
-       deemed unhelpful, not to mention inconsistent with casting from bit
-       to int.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Require <type>CIDR</> values to have all nonmasked bits be zero
-       (Kevin Brintnall)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Server-Side Language Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       In <literal>READ COMMITTED</> serialization mode, volatile functions
-       now see the results of concurrent transactions committed up to the
-       beginning of each statement within the function, rather than up to the
-       beginning of the interactive command that called the function.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Functions declared <literal>STABLE</> or <literal>IMMUTABLE</> always
-       use the snapshot of the calling query, and therefore do not see the
-       effects of actions taken after the calling query starts, whether in
-       their own transaction or other transactions.  Such a function must be
-       read-only, too, meaning that it cannot use any SQL commands other than
-       <command>SELECT</>.  There is a considerable performance gain from
-       declaring a function <literal>STABLE</> or <literal>IMMUTABLE</>
-       rather than <literal>VOLATILE</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Nondeferred <option>AFTER</> triggers are now fired immediately
-       after completion of the triggering query, rather than upon
-       finishing the current interactive command. This makes a difference
-       when the triggering query occurred within a function: the trigger
-       is invoked before the function proceeds to its next operation. For
-       example, if a function inserts a new row into a table, any
-       nondeferred foreign key checks occur before proceeding with the
-       function.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow function parameters to be declared with names (Dennis Bj&ouml;rklund)
-      </para>
-      <para>
-       This allows better documentation of functions.  Whether the names
-       actually do anything depends on the specific function language
-       being used.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow PL/pgSQL parameter names to be referenced in the function (Dennis Bj&ouml;rklund)
-      </para>
-      <para>
-       This basically creates an automatic alias for each named parameter.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Do minimal syntax checking of PL/pgSQL functions at creation time (Tom)
-      </para>
-      <para>
-       This allows us to catch simple syntax errors sooner.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       More support for composite types (row and record variables) in PL/pgSQL
-      </para>
-      <para>
-       For example, it now works to pass a rowtype variable to another function
-       as a single variable.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Default values for PL/pgSQL variables can now reference previously
-       declared variables
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve parsing of PL/pgSQL FOR loops (Tom)
-      </para>
-      <para>
-       Parsing is now driven by presence of <literal>".."</> rather than
-       data type of <option>FOR</> variable. This makes no difference for
-       correct functions, but should result in more understandable error
-       messages when a mistake is made.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Major overhaul of PL/Perl server-side language (Command Prompt, Andrew Dunstan)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In PL/Tcl, SPI commands are now run in subtransactions.  If an error
-       occurs, the subtransaction is cleaned up and the error is reported
-       as an ordinary Tcl error, which can be trapped with <literal>catch</>.
-       Formerly, it was not possible to catch such errors.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Accept <command>ELSEIF</> in PL/pgSQL (Neil)
-      </para>
-      <para>
-       Previously PL/pgSQL only allowed <command>ELSIF</>, but many people
-       are accustomed to spelling this keyword <command>ELSEIF</>.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title><application>psql</> Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Improve <application>psql</> information display about database
-       objects (Christopher)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>psql</> to display group membership in
-       <command>\du</> and <command>\dg</> (Markus Bertheau)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Prevent <application>psql</> <command>\dn</command> from showing
-       temporary schemas (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>psql</> to handle tilde user expansion for file
-       names (Zach Irmen)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>psql</> to display fancy prompts, including
-       color, via <application>readline</> (Reece Hart, Chet Ramey)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <application>psql</> <command>\copy</> match <command>COPY</command> command syntax
-       fully (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Show the location of syntax errors (Fabien Coelho, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>CLUSTER</command> information to <application>psql</>
-       <command>\d</> display
-       (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change <application>psql</> <command>\copy stdin/stdout</> to read
-       from command input/output (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>pstdin</>/<option>pstdout</> to read from
-       <application>psql</>'s <literal>stdin</>/<literal>stdout</> (Mark
-       Feit)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add global <application>psql</> configuration file, <filename>psqlrc.sample</filename>
-       (Bruce)
-      </para>
-      <para>
-       This allows a central file where global <application>psql</> startup commands can
-       be stored.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Have <application>psql</> <command>\d+</> indicate if the table
-       has an <type>OID</> column (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       On Windows, use binary mode in <application>psql</> when reading files so control-Z
-       is not seen as end-of-file
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Have <command>\dn+</> show permissions and description for schemas (Dennis
-       Bj&ouml;rklund)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve tab completion support (Stefan Kaltenbrunn, Greg Sabino Mullane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow boolean settings to be set using upper or lower case (Michael Paesold)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title><application>pg_dump</> Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Use dependency information to improve the reliability of
-       <application>pg_dump</> (Tom)
-      </para>
-      <para>
-       This should solve the longstanding problems with related objects
-       sometimes being dumped in the wrong order.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Have <application>pg_dump</> output objects in alphabetical order if possible (Tom)
-      </para>
-      <para>
-       This should make it easier to identify changes between
-       dump files.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>pg_restore</> to ignore some SQL errors (Fabien Coelho)
-      </para>
-      <para>
-       This makes <application>pg_restore</>'s behavior similar to the
-       results of feeding a <application>pg_dump</> output script to
-       <application>psql</>. In most cases, ignoring errors and plowing
-       ahead is the most useful thing to do. Also added was a pg_restore
-       option to give the old behavior of exiting on an error.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <application>pg_restore</> <option>-l</> display now includes
-       objects' schema names
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New begin/end markers in <application>pg_dump</> text output (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add start/stop times for
-       <application>pg_dump</>/<application>pg_dumpall</> in verbose mode
-       (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow most <application>pg_dump</> options in
-       <application>pg_dumpall</> (Christopher)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Have <application>pg_dump</> use <command>ALTER OWNER</> rather
-       than <command>SET SESSION AUTHORIZATION</> by default
-       (Christopher)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>libpq Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Make libpq's <option>SIGPIPE</> handling thread-safe (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>PQmbdsplen()</> which returns the display length
-       of a character (Tatsuo)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add thread locking to <application>SSL</> and
-       <application>Kerberos</> connections (Manfred Spraul)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <function>PQoidValue()</>, <function>PQcmdTuples()</>, and
-       <function>PQoidStatus()</> to work on <command>EXECUTE</command>
-       commands (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>PQserverVersion()</> to provide more convenient
-       access to the server version number (Greg Sabino Mullane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>PQprepare/PQsendPrepared()</> functions to support
-       preparing statements without necessarily specifying the data types
-       of their parameters (Abhijit Menon-Sen)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Many ECPG improvements, including <command>SET DESCRIPTOR</> (Michael)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Source Code Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow the database server to run natively on Windows (Claudio, Magnus, Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Shell script commands converted to C versions for Windows support (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Create an extension makefile framework (Fabien Coelho, Peter)
-      </para>
-      <para>
-       This simplifies the task of building extensions outside the original
-       source tree.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support relocatable installations (Bruce)
-      </para>
-      <para>
-       Directory paths for installed files (such as the
-       <filename>/share</> directory) are now computed relative to the
-       actual location of the executables, so that an installation tree
-       can be moved to another place without reconfiguring and
-       rebuilding.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use <option>--with-docdir</> to choose installation location of documentation; also
-       allow <option>--infodir</> (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>--without-docdir</> to prevent installation of documentation (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Upgrade to <application>DocBook</> V4.2 SGML (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New <literal>PostgreSQL</> <application>CVS</> tag (Marc)
-      </para>
-      <para>
-       This was done to make it easier for organizations to manage their
-       own copies of the <productname>PostgreSQL</productname>
-       <application>CVS</> repository. File version stamps from the master
-       repository will not get munged by checking into or out of a copied
-       repository.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Clarify locking code (Manfred Koizar)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Buffer manager cleanup (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Decouple platform tests from CPU spinlock code (Bruce, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add inlined test-and-set code on PA-RISC for <application>gcc</>
-       (ViSolve, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve i386 spinlock code (Manfred Spraul)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Clean up spinlock assembly code to avoid warnings from newer
-       <application>gcc</> releases (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove JDBC from source tree; now a separate project
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove the libpgtcl client interface; now a separate project
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       More accurately estimate memory and file descriptor usage (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improvements to the Mac OS X startup scripts (Ray A.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New <function>fsync()</> test program (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Major documentation improvements (Neil, Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <application>pg_encoding</application>; not needed
-       anymore
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <application>pg_id</application>; not needed anymore
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <application>initlocation</application>; not needed
-       anymore
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Auto-detect thread flags (no more manual testing) (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use Olson's public domain <application>timezone</> library (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       With threading enabled, use thread flags on Unixware for
-       backend executables too (Bruce)
-      </para>
-      <para>
-       Unixware cannot mix threaded and nonthreaded object files in the
-       same executable, so everything must be compiled as threaded.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <application>psql</> now uses a <application>flex</>-generated
-       lexical analyzer to process command strings
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reimplement the linked list data structure used throughout the
-       backend (Neil)
-      </para>
-      <para>
-       This improves performance by allowing list append and length
-       operations to be more efficient.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow dynamically loaded modules to create their own server configuration
-       parameters (Thomas Hallgren)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New Brazilian version of FAQ (Euler Taveira de Oliveira)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add French FAQ (Guillaume Lelarge)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New <application>pgevent</> for Windows logging
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make libpq and ECPG build as proper shared libraries on OS X (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Contrib Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Overhaul of <filename>contrib/dblink</> (Joe)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <filename>contrib/dbmirror</> improvements (Steven Singer)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New <filename>contrib/xml2</> (John Gray, Torchbox)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Updated <filename>contrib/mysql</filename>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New version of <filename>contrib/btree_gist</> (Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New <filename>contrib/trgm</>, trigram matching for
-       <productname>PostgreSQL</productname> (Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Many <filename>contrib/tsearch2</> improvements (Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add double metaphone to <filename>contrib/fuzzystrmatch</> (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <filename>contrib/pg_autovacuum</> to run as a Windows service (Dave Page)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add functions to <filename>contrib/dbsize</> (Andreas Pflug)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Removed <filename>contrib/pg_logger</>: obsoleted by integrated logging
-       subprocess
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Removed <filename>contrib/rserv</>: obsoleted by various separate projects
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-  </sect2>
- </sect1>
diff --git a/doc-xc/src/sgml/release-8.1.sgmlin b/doc-xc/src/sgml/release-8.1.sgmlin
deleted file mode 100644
index 4e1a0c5dd0..0000000000
--- a/doc-xc/src/sgml/release-8.1.sgmlin
+++ /dev/null
@@ -1,5444 +0,0 @@
-<!-- doc/src/sgml/release-8.1.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-8-1-23">
-  <title>Release 8.1.23</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2010-12-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.22.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <para>
-   This is expected to be the last <productname>PostgreSQL</> release
-   in the 8.1.X series.  Users are encouraged to update to a newer
-   release branch soon.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.23</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.18,
-    see the release notes for 8.1.18.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Force the default
-      <link linkend="guc-wal-sync-method"><varname>wal_sync_method</></link>
-      to be <literal>fdatasync</> on Linux (Tom Lane, Marti Raudsepp)
-     </para>
-
-     <para>
-      The default on Linux has actually been <literal>fdatasync</> for many
-      years, but recent kernel changes caused <productname>PostgreSQL</> to
-      choose <literal>open_datasync</> instead.  This choice did not result
-      in any performance improvement, and caused outright failures on
-      certain filesystems, notably <literal>ext4</> with the
-      <literal>data=journal</> mount option.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix recovery from base backup when the starting checkpoint WAL record
-      is not in the same WAL segment as its redo point (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add support for detecting register-stack overrun on <literal>IA64</>
-      (Tom Lane)
-     </para>
-
-     <para>
-      The <literal>IA64</> architecture has two hardware stacks.  Full
-      prevention of stack-overrun failures requires checking both.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add a check for stack overflow in <function>copyObject()</> (Tom Lane)
-     </para>
-
-     <para>
-      Certain code paths could crash due to stack overflow given a
-      sufficiently complex query.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix detection of page splits in temporary GiST indexes (Heikki
-      Linnakangas)
-     </para>
-
-     <para>
-      It is possible to have a <quote>concurrent</> page split in a
-      temporary index, if for example there is an open cursor scanning the
-      index when an insertion is done.  GiST failed to detect this case and
-      hence could deliver wrong results when execution of the cursor
-      continued.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid memory leakage while <command>ANALYZE</>'ing complex index
-      expressions (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure an index that uses a whole-row Var still depends on its table
-      (Tom Lane)
-     </para>
-
-     <para>
-      An index declared like <literal>create index i on t (foo(t.*))</>
-      would not automatically get dropped when its table was dropped.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not <quote>inline</> a SQL function with multiple <literal>OUT</>
-      parameters (Tom Lane)
-     </para>
-
-     <para>
-      This avoids a possible crash due to loss of information about the
-      expected result rowtype.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix constant-folding of <literal>COALESCE()</> expressions (Tom Lane)
-     </para>
-
-     <para>
-      The planner would sometimes attempt to evaluate sub-expressions that
-      in fact could never be reached, possibly leading to unexpected errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add print functionality for <structname>InhRelation</> nodes (Tom Lane)
-     </para>
-
-     <para>
-      This avoids a failure when <varname>debug_print_parse</> is enabled
-      and certain types of query are executed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect calculation of distance from a point to a horizontal
-      line segment (Tom Lane)
-     </para>
-
-     <para>
-      This bug affected several different geometric distance-measurement
-      operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/pgSQL</>'s handling of <quote>simple</>
-      expressions to not fail in recursion or error-recovery cases (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in <filename>contrib/cube</>'s GiST picksplit algorithm
-      (Alexander Korotkov)
-     </para>
-
-     <para>
-      This could result in considerable inefficiency, though not actually
-      incorrect answers, in a GiST index on a <type>cube</> column.
-      If you have such an index, consider <command>REINDEX</>ing it after
-      installing this update.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Don't emit <quote>identifier will be truncated</> notices in
-      <filename>contrib/dblink</> except when creating new connections
-      (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential coredump on missing public key in
-      <filename>contrib/pgcrypto</> (Marti Raudsepp)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak in <filename>contrib/xml2</>'s XPath query functions
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010o
-      for DST law changes in Fiji and Samoa;
-      also historical corrections for Hong Kong.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-22">
-  <title>Release 8.1.22</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2010-10-04</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.21.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <para>
-   The <productname>PostgreSQL</> community will stop releasing updates
-   for the 8.1.X release series in November 2010.
-   Users are encouraged to update to a newer release branch soon.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.22</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.18,
-    see the release notes for 8.1.18.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Use a separate interpreter for each calling SQL userid in PL/Perl and
-      PL/Tcl (Tom Lane)
-     </para>
-
-     <para>
-      This change prevents security problems that can be caused by subverting
-      Perl or Tcl code that will be executed later in the same session under
-      another SQL user identity (for example, within a <literal>SECURITY
-      DEFINER</> function).  Most scripting languages offer numerous ways that
-      that might be done, such as redefining standard functions or operators
-      called by the target function.  Without this change, any SQL user with
-      Perl or Tcl language usage rights can do essentially anything with the
-      SQL privileges of the target function's owner.
-     </para>
-
-     <para>
-      The cost of this change is that intentional communication among Perl
-      and Tcl functions becomes more difficult.  To provide an escape hatch,
-      PL/PerlU and PL/TclU functions continue to use only one interpreter
-      per session.  This is not considered a security issue since all such
-      functions execute at the trust level of a database superuser already.
-     </para>
-
-     <para>
-      It is likely that third-party procedural languages that claim to offer
-      trusted execution have similar security issues.  We advise contacting
-      the authors of any PL you are depending on for security-critical
-      purposes.
-     </para>
-
-     <para>
-      Our thanks to Tim Bunce for pointing out this issue (CVE-2010-3433).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible crashes in <function>pg_get_expr()</> by disallowing
-      it from being called with an argument that is not one of the system
-      catalog columns it's intended to be used with
-      (Heikki Linnakangas, Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>cannot handle unplanned sub-select</quote> error (Tom Lane)
-     </para>
-
-     <para>
-      This occurred when a sub-select contains a join alias reference that
-      expands into an expression containing another sub-select.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent show_session_authorization() from crashing within autovacuum
-      processes (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Defend against functions returning setof record where not all the
-      returned rows are actually of the same rowtype (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible failure when hashing a pass-by-reference function result
-      (Tao Ma, Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Take care to fsync the contents of lockfiles (both
-      <filename>postmaster.pid</> and the socket lockfile) while writing them
-      (Tom Lane)
-     </para>
-
-     <para>
-      This omission could result in corrupted lockfile contents if the
-      machine crashes shortly after postmaster start.  That could in turn
-      prevent subsequent attempts to start the postmaster from succeeding,
-      until the lockfile is manually removed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid recursion while assigning XIDs to heavily-nested
-      subtransactions (Andres Freund, Robert Haas)
-     </para>
-
-     <para>
-      The original coding could result in a crash if there was limited
-      stack space.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <varname>log_line_prefix</>'s <literal>%i</> escape,
-      which could produce junk early in backend startup (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible data corruption in <command>ALTER TABLE ... SET
-      TABLESPACE</> when archiving is enabled (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow <command>CREATE DATABASE</> and <command>ALTER DATABASE ... SET
-      TABLESPACE</> to be interrupted by query-cancel (Guillaume Lelarge)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In PL/Python, defend against null pointer results from
-      <function>PyCObject_AsVoidPtr</> and <function>PyCObject_FromVoidPtr</>
-      (Peter Eisentraut)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <filename>contrib/dblink</>'s handling of tables containing
-      dropped columns (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix connection leak after <quote>duplicate connection name</quote>
-      errors in <filename>contrib/dblink</> (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/dblink</> to handle connection names longer than
-      62 bytes correctly (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update build infrastructure and documentation to reflect the source code
-      repository's move from CVS to Git (Magnus Hagander and others)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010l
-      for DST law changes in Egypt and Palestine; also historical corrections
-      for Finland.
-     </para>
-
-     <para>
-      This change also adds new names for two Micronesian timezones:
-      Pacific/Chuuk is now preferred over Pacific/Truk (and the preferred
-      abbreviation is CHUT not TRUT) and Pacific/Pohnpei is preferred over
-      Pacific/Ponape.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-21">
-  <title>Release 8.1.21</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2010-05-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.20.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.21</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.18,
-    see the release notes for 8.1.18.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Enforce restrictions in <literal>plperl</> using an opmask applied to
-      the whole interpreter, instead of using <filename>Safe.pm</>
-      (Tim Bunce, Andrew Dunstan)
-     </para>
-
-     <para>
-      Recent developments have convinced us that <filename>Safe.pm</> is too
-      insecure to rely on for making <literal>plperl</> trustable.  This
-      change removes use of <filename>Safe.pm</> altogether, in favor of using
-      a separate interpreter with an opcode mask that is always applied.
-      Pleasant side effects of the change include that it is now possible to
-      use Perl's <literal>strict</> pragma in a natural way in
-      <literal>plperl</>, and that Perl's <literal>$a</> and <literal>$b</>
-      variables work as expected in sort routines, and that function
-      compilation is significantly faster.  (CVE-2010-1169)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent PL/Tcl from executing untrustworthy code from
-      <structname>pltcl_modules</> (Tom)
-     </para>
-
-     <para>
-      PL/Tcl's feature for autoloading Tcl code from a database table
-      could be exploited for trojan-horse attacks, because there was no
-      restriction on who could create or insert into that table.  This change
-      disables the feature unless <structname>pltcl_modules</> is owned by a
-      superuser.  (However, the permissions on the table are not checked, so
-      installations that really need a less-than-secure modules table can
-      still grant suitable privileges to trusted non-superusers.)  Also,
-      prevent loading code into the unrestricted <quote>normal</> Tcl
-      interpreter unless we are really going to execute a <literal>pltclu</>
-      function.  (CVE-2010-1170)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not allow an unprivileged user to reset superuser-only parameter
-      settings (Alvaro)
-     </para>
-
-     <para>
-      Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
-      ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
-      a database he owns, this would remove all special parameter settings
-      for the user or database, even ones that are only supposed to be
-      changeable by a superuser.  Now, the <command>ALTER</> will only
-      remove the parameters that the user has permission to change.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crash during backend shutdown if shutdown occurs
-      when a <literal>CONTEXT</> addition would be made to log entries (Tom)
-     </para>
-
-     <para>
-      In some cases the context-printing function would fail because the
-      current transaction had already been rolled back when it came time
-      to print a log message.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update pl/perl's <filename>ppport.h</> for modern Perl versions
-      (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite recursion in <application>psql</> when expanding
-      a variable that refers to itself (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
-      interrupts promptly (Tatsuhito Kasahara)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make server startup deal properly with the case that
-      <function>shmget()</> returns <literal>EINVAL</> for an existing
-      shared memory segment (Tom)
-     </para>
-
-     <para>
-      This behavior has been observed on BSD-derived kernels including OS X.
-      It resulted in an entirely-misleading startup failure complaining that
-      the shared memory request size was too large.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010j
-      for DST law changes in Argentina, Australian Antarctic, Bangladesh,
-      Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia;
-      also historical corrections for Taiwan.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-20">
-  <title>Release 8.1.20</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2010-03-15</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.19.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.20</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.18,
-    see the release notes for 8.1.18.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Add new configuration parameter <varname>ssl_renegotiation_limit</> to
-      control how often we do session key renegotiation for an SSL connection
-      (Magnus)
-     </para>
-
-     <para>
-      This can be set to zero to disable renegotiation completely, which may
-      be required if a broken SSL library is used.  In particular, some
-      vendors are shipping stopgap patches for CVE-2009-3555 that cause
-      renegotiation attempts to fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes when trying to recover from a failure in
-      subtransaction start (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix server memory leak associated with use of savepoints and a client
-      encoding different from server's encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>substring()</> for <type>bit</> types treat any negative
-      length as meaning <quote>all the rest of the string</> (Tom)
-     </para>
-
-     <para>
-      The previous coding treated only -1 that way, and would produce an
-      invalid result value for other negative values, possibly leading to
-      a crash (CVE-2010-0442).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix integer-to-bit-string conversions to handle the first fractional
-      byte correctly when the output bit width is wider than the given
-      integer by something other than a multiple of 8 bits (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some cases of pathologically slow regular expression matching (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix the <literal>STOP WAL LOCATION</> entry in backup history files to
-      report the next WAL segment's name when the end location is exactly at a
-      segment boundary (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some more cases of temporary-file leakage (Heikki)
-     </para>
-
-     <para>
-      This corrects a problem introduced in the previous minor release.
-      One case that failed is when a plpgsql function returning set is
-      called within another function's exception handler.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      When reading <filename>pg_hba.conf</> and related files, do not treat
-      <literal>@something</> as a file inclusion request if the <literal>@</>
-      appears inside quote marks; also, never treat <literal>@</> by itself
-      as a file inclusion request (Tom)
-     </para>
-
-     <para>
-      This prevents erratic behavior if a role or database name starts with
-      <literal>@</>.  If you need to include a file whose path name
-      contains spaces, you can still do so, but you must write
-      <literal>@"/path to/file"</> rather than putting the quotes around
-      the whole construct.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite loop on some platforms if a directory is named as
-      an inclusion target in <filename>pg_hba.conf</> and related files
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>psql</>'s <literal>numericlocale</> option to not
-      format strings it shouldn't in latex and troff output formats (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix plpgsql failure in one case where a composite column is set to NULL
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>volatile</> markings in PL/Python to avoid possible
-      compiler-specific misbehavior (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
-     </para>
-
-     <para>
-      The only known symptom of this oversight is that the Tcl
-      <literal>clock</> command misbehaves if using Tcl 8.5 or later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent crash in <filename>contrib/dblink</> when too many key
-      columns are specified to a <function>dblink_build_sql_*</> function
-      (Rushabh Lathia, Joe Conway)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted crashes in <filename>contrib/xml2</> caused by sloppy
-      memory management (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010e
-      for DST law changes in Bangladesh, Chile, Fiji, Mexico, Paraguay, Samoa.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-19">
-  <title>Release 8.1.19</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-12-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.18.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.19</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.18,
-    see the release notes for 8.1.18.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Protect against indirect security threats caused by index functions
-      changing session-local state (Gurjeet Singh, Tom)
-     </para>
-
-     <para>
-      This change prevents allegedly-immutable index functions from possibly
-      subverting a superuser's session (CVE-2009-4136).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Reject SSL certificates containing an embedded null byte in the common
-      name (CN) field (Magnus)
-     </para>
-
-     <para>
-      This prevents unintended matching of a certificate to a server or client
-      name during SSL validation (CVE-2009-4034).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash during backend-startup-time cache initialization (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent signals from interrupting <literal>VACUUM</> at unsafe times
-      (Alvaro)
-     </para>
-
-     <para>
-      This fix prevents a PANIC if a <literal>VACUUM FULL</> is cancelled
-      after it's already committed its tuple movements, as well as transient
-      errors if a plain <literal>VACUUM</> is interrupted after having
-      truncated the table.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash due to integer overflow in hash table size
-      calculation (Tom)
-     </para>
-
-     <para>
-      This could occur with extremely large planner estimates for the size of
-      a hashjoin's result.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix very rare crash in <type>inet</>/<type>cidr</> comparisons (Chris
-      Mikkelson)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that shared tuple-level locks held by prepared transactions are
-      not ignored (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix premature drop of temporary files used for a cursor that is accessed
-      within a subtransaction (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PAM password processing to be more robust (Tom)
-     </para>
-
-     <para>
-      The previous code is known to fail with the combination of the Linux
-      <literal>pam_krb5</> PAM module with Microsoft Active Directory as the
-      domain controller.  It might have problems elsewhere too, since it was
-      making unjustified assumptions about what arguments the PAM stack would
-      pass to it.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix processing of ownership dependencies during <literal>CREATE OR
-      REPLACE FUNCTION</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that Perl arrays are properly converted to
-      <productname>PostgreSQL</> arrays when returned by a set-returning
-      PL/Perl function (Andrew Dunstan, Abhijit Menon-Sen)
-     </para>
-
-     <para>
-      This worked correctly already for non-set-returning functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix rare crash in exception processing in PL/Python (Peter)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <application>psql</>'s flex module is compiled with the correct
-      system header definitions (Tom)
-     </para>
-
-     <para>
-      This fixes build failures on platforms where
-      <literal>--enable-largefile</> causes incompatible changes in the
-      generated code.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make the postmaster ignore any <literal>application_name</> parameter in
-      connection request packets, to improve compatibility with future libpq
-      versions (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009s
-      for DST law changes in Antarctica, Argentina, Bangladesh, Fiji,
-      Novokuznetsk, Pakistan, Palestine, Samoa, Syria; also historical
-      corrections for Hong Kong.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-18">
-  <title>Release 8.1.18</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-09-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.17.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.18</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you have any hash indexes on <type>interval</> columns,
-    you must <command>REINDEX</> them after updating to 8.1.18.
-    Also, if you are upgrading from a version earlier than 8.1.15,
-    see the release notes for 8.1.15.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Disallow <command>RESET ROLE</> and <command>RESET SESSION
-      AUTHORIZATION</> inside security-definer functions (Tom, Heikki)
-     </para>
-
-     <para>
-      This covers a case that was missed in the previous patch that
-      disallowed <command>SET ROLE</> and <command>SET SESSION
-      AUTHORIZATION</> inside security-definer functions.
-      (See CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix handling of sub-SELECTs appearing in the arguments of
-      an outer-level aggregate function (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix hash calculation for data type <type>interval</> (Tom)
-     </para>
-
-     <para>
-      This corrects wrong results for hash joins on interval values.
-      It also changes the contents of hash indexes on interval columns.
-      If you have any such indexes, you must <command>REINDEX</> them
-      after updating.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Treat <function>to_char(..., 'TH')</> as an uppercase ordinal
-      suffix with <literal>'HH'</>/<literal>'HH12'</> (Heikki)
-     </para>
-
-     <para>
-      It was previously handled as <literal>'th'</> (lowercase).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix overflow for <literal>INTERVAL '<replaceable>x</> ms'</literal>
-      when <replaceable>x</> is more than 2 million and integer
-      datetimes are in use (Alex Hunsaker)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix calculation of distance between a point and a line segment (Tom)
-     </para>
-
-     <para>
-      This led to incorrect results from a number of geometric operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <type>money</> data type to work in locales where currency
-      amounts have no fractional digits, e.g. Japan (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Properly round datetime input like
-      <literal>00:12:57.9999999999999999999999999999</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix poor choice of page split point in GiST R-tree operator classes
-      (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix portability issues in plperl initialization (Andrew Dunstan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to not go into an infinite loop if
-      <filename>postgresql.conf</> is empty (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/xml2</>'s <function>xslt_process()</> to
-      properly handle the maximum number of parameters (twenty) (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve robustness of <application>libpq</>'s code to recover
-      from errors during <command>COPY FROM STDIN</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid including conflicting readline and editline header files
-      when both libraries are installed (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009l
-      for DST law changes in Bangladesh, Egypt, Jordan, Pakistan,
-      Argentina/San_Luis, Cuba, Jordan (historical correction only),
-      Mauritius, Morocco, Palestine, Syria, Tunisia.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-17">
-  <title>Release 8.1.17</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-03-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.16.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.17</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.15,
-    see the release notes for 8.1.15.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent error recursion crashes when encoding conversion fails (Tom)
-     </para>
-
-     <para>
-      This change extends fixes made in the last two minor releases for
-      related failure scenarios.  The previous fixes were narrowly tailored
-      for the original problem reports, but we have now recognized that
-      <emphasis>any</> error thrown by an encoding conversion function could
-      potentially lead to infinite recursion while trying to report the
-      error.  The solution therefore is to disable translation and encoding
-      conversion and report the plain-ASCII form of any error message,
-      if we find we have gotten into a recursive error reporting situation.
-      (CVE-2009-0922)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>CREATE CONVERSION</> with the wrong encodings
-      for the specified conversion function (Heikki)
-     </para>
-
-     <para>
-      This prevents one possible scenario for encoding conversion failure.
-      The previous change is a backstop to guard against other kinds of
-      failures in the same area.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix core dump when <function>to_char()</> is given format codes that
-      are inappropriate for the type of the data argument (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix decompilation of <literal>CASE WHEN</> with an implicit coercion
-      (Tom)
-     </para>
-
-     <para>
-      This mistake could lead to Assert failures in an Assert-enabled build,
-      or an <quote>unexpected CASE WHEN clause</> error message in other
-      cases, when trying to examine or dump a view.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible misassignment of the owner of a TOAST table's rowtype (Tom)
-     </para>
-
-     <para>
-      If <command>CLUSTER</> or a rewriting variant of <command>ALTER TABLE</>
-      were executed by someone other than the table owner, the
-      <structname>pg_type</> entry for the table's TOAST table would end up
-      marked as owned by that someone.  This caused no immediate problems,
-      since the permissions on the TOAST rowtype aren't examined by any
-      ordinary database operation.  However, it could lead to unexpected
-      failures if one later tried to drop the role that issued the command
-      (in 8.1 or 8.2), or <quote>owner of data type appears to be invalid</>
-      warnings from <application>pg_dump</> after having done so (in 8.3).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Clean up PL/pgSQL error status variables fully at block exit
-      (Ashesh Vashi and Dave Page)
-     </para>
-
-     <para>
-      This is not a problem for PL/pgSQL itself, but the omission could cause
-      the PL/pgSQL Debugger to crash while examining the state of a function.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>MUST</> (Mauritius Island Summer Time) to the default list
-      of known timezone abbreviations (Xavier Bugaud)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-16">
-  <title>Release 8.1.16</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2009-02-02</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.15.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.16</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.15,
-    see the release notes for 8.1.15.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix crash in autovacuum (Alvaro)
-     </para>
-
-     <para>
-      The crash occurs only after vacuuming a whole database for
-      anti-transaction-wraparound purposes, which means that it occurs
-      infrequently and is hard to track down.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve handling of URLs in <function>headline()</> function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve handling of overlength headlines in <function>headline()</>
-      function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible Assert failure or misconversion if an encoding
-      conversion is created with the wrong conversion function for the
-      specified pair of encodings (Tom, Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unnecessary locking of small tables in <command>VACUUM</>
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that the contents of a holdable cursor don't depend on the
-      contents of TOAST tables (Tom)
-     </para>
-
-     <para>
-      Previously, large field values in a cursor result might be represented
-      as TOAST pointers, which would fail if the referenced table got dropped
-      before the cursor is read, or if the large value is deleted and then
-      vacuumed away.  This cannot happen with an ordinary cursor,
-      but it could with a cursor that is held past its creating transaction.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix uninitialized variables in <filename>contrib/tsearch2</>'s
-      <function>get_covers()</> function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>configure</> script to properly report failure when
-      unable to obtain linkage information for PL/Perl (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make all documentation reference <literal>pgsql-bugs</> and/or
-      <literal>pgsql-hackers</> as appropriate, instead of the
-      now-decommissioned <literal>pgsql-ports</> and <literal>pgsql-patches</>
-      mailing lists (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009a (for
-      Kathmandu and historical DST corrections in Switzerland, Cuba)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-15">
-  <title>Release 8.1.15</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-11-03</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.14.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.15</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.  Also, if you were running a previous
-    8.1.X release, it is recommended to <command>REINDEX</> all GiST
-    indexes after the upgrade.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix GiST index corruption due to marking the wrong index entry
-      <quote>dead</> after a deletion (Teodor)
-     </para>
-
-     <para>
-      This would result in index searches failing to find rows they
-      should have found.  Corrupted indexes can be fixed with
-      <command>REINDEX</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix backend crash when the client encoding cannot represent a localized
-      error message (Tom)
-     </para>
-
-     <para>
-      We have addressed similar issues before, but it would still fail if
-      the <quote>character has no equivalent</> message itself couldn't
-      be converted.  The fix is to disable localization and send the plain
-      ASCII error message when we detect such a situation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash when deeply nested functions are invoked from
-      a trigger (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix mis-expansion of rule queries when a sub-<literal>SELECT</> appears
-      in a function call in <literal>FROM</>,  a multi-row <literal>VALUES</>
-      list, or a <literal>RETURNING</> list (Tom)
-     </para>
-
-     <para>
-      The usual symptom of this problem is an <quote>unrecognized node type</>
-      error.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure an error is reported when a newly-defined PL/pgSQL trigger
-      function is invoked as a normal function (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible collision of <structfield>relfilenode</> numbers
-      when moving a table to another tablespace with <command>ALTER SET
-      TABLESPACE</> (Heikki)
-     </para>
-
-     <para>
-      The command tried to re-use the existing filename, instead of
-      picking one that is known unused in the destination directory.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect tsearch2 headline generation when single query
-      item matches first word of text (Sushant Sinha)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix improper display of fractional seconds in interval values when
-      using a non-ISO datestyle in an <option>--enable-integer-datetimes</>
-      build (Ron Mayer)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <function>SPI_getvalue</> and <function>SPI_getbinval</>
-      behave correctly when the passed tuple and tuple descriptor have
-      different numbers of columns (Tom)
-     </para>
-
-     <para>
-      This situation is normal when a table has had columns added or removed,
-      but these two functions didn't handle it properly.
-      The only likely consequence is an incorrect error indication.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</>'s parsing of <command>CREATE ROLE</> (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix recent breakage of <literal>pg_ctl restart</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008i (for
-      DST law changes in Argentina, Brazil, Mauritius, Syria)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-14">
-  <title>Release 8.1.14</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-09-22</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.13.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.14</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Widen local lock counters from 32 to 64 bits (Tom)
-     </para>
-
-     <para>
-      This responds to reports that the counters could overflow in
-      sufficiently long transactions, leading to unexpected <quote>lock is
-      already held</> errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible duplicate output of tuples during a GiST index scan (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add checks in executor startup to ensure that the tuples produced by an
-      <command>INSERT</> or <command>UPDATE</> will match the target table's
-      current rowtype (Tom)
-     </para>
-
-     <para>
-      <command>ALTER COLUMN TYPE</>, followed by re-use of a previously
-      cached plan, could produce this type of situation.  The check protects
-      against data corruption and/or crashes that could ensue.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>AT TIME ZONE</> to first try to interpret its timezone
-      argument as a timezone abbreviation, and only try it as a full timezone
-      name if that fails, rather than the other way around as formerly (Tom)
-     </para>
-
-     <para>
-      The timestamp input functions have always resolved ambiguous zone names
-      in this order.  Making <literal>AT TIME ZONE</> do so as well improves
-      consistency, and fixes a compatibility bug introduced in 8.1:
-      in ambiguous cases we now behave the same as 8.0 and before did,
-      since in the older versions <literal>AT TIME ZONE</> accepted
-      <emphasis>only</> abbreviations.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix datetime input functions to correctly detect integer overflow when
-      running on a 64-bit platform (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve performance of writing very long log messages to syslog (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in backwards scanning of a cursor on a <literal>SELECT DISTINCT
-      ON</> query (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner bug with nested sub-select expressions (Tom)
-     </para>
-
-     <para>
-      If the outer sub-select has no direct dependency on the parent query,
-      but the inner one does, the outer value might not get recalculated
-      for new parent query rows.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner to estimate that <literal>GROUP BY</> expressions yielding
-      boolean results always result in two groups, regardless of the
-      expressions' contents (Tom)
-     </para>
-
-     <para>
-      This is very substantially more accurate than the regular <literal>GROUP
-      BY</> estimate for certain boolean tests like <replaceable>col</>
-      <literal>IS NULL</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/pgSQL to not fail when a <literal>FOR</> loop's target variable
-      is a record containing composite-type fields (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Tcl to behave correctly with Tcl 8.5, and to be more careful
-      about the encoding of data sent to or from Tcl (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Python to work with Python 2.5
-     </para>
-
-     <para>
-      This is a back-port of fixes made during the 8.2 development cycle.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <application>pg_dump</> and <application>pg_restore</>'s
-      error reporting after failure to send a SQL command (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to properly preserve postmaster
-      command-line arguments across a <literal>restart</> (Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008f (for
-      DST law changes in Argentina, Bahamas, Brazil, Mauritius, Morocco,
-      Pakistan, Palestine, and Paraguay)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-13">
-  <title>Release 8.1.13</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-06-12</simpara>
-  </note>
-
-  <para>
-   This release contains one serious and one minor bug fix over 8.1.12.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.13</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Make <function>pg_get_ruledef()</> parenthesize negative constants (Tom)
-     </para>
-
-     <para>
-      Before this fix, a negative constant in a view or rule might be dumped
-      as, say, <literal>-42::integer</>, which is subtly incorrect: it should
-      be <literal>(-42)::integer</> due to operator precedence rules.
-      Usually this would make little difference, but it could interact with
-      another recent patch to cause
-      <productname>PostgreSQL</> to reject what had been a valid
-      <command>SELECT DISTINCT</> view query.  Since this could result in
-      <application>pg_dump</> output failing to reload, it is being treated
-      as a high-priority fix.  The only released versions in which dump
-      output is actually incorrect are 8.3.1 and 8.2.7.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>ALTER AGGREGATE ... OWNER TO</> update
-      <structname>pg_shdepend</> (Tom)
-     </para>
-
-     <para>
-      This oversight could lead to problems if the aggregate was later
-      involved in a <command>DROP OWNED</> or <command>REASSIGN OWNED</>
-      operation.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-12">
-  <title>Release 8.1.12</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>never released</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.11.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.12</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix <command>ALTER TABLE ADD COLUMN ... PRIMARY KEY</> so that the new
-      column is correctly checked to see if it's been initialized to all
-      non-nulls (Brendan Jurd)
-     </para>
-
-     <para>
-      Previous versions neglected to check this requirement at all.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible <command>CREATE TABLE</> failure when inheriting the
-      <quote>same</> constraint from multiple parent relations that
-      inherited that constraint from a common ancestor (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix conversions between ISO-8859-5 and other encodings to handle
-      Cyrillic <quote>Yo</> characters (<literal>e</> and <literal>E</> with
-      two dots) (Sergey Burladyan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a few datatype input functions
-      that were allowing unused bytes in their results to contain
-      uninitialized, unpredictable values (Tom)
-     </para>
-
-     <para>
-      This could lead to failures in which two apparently identical literal
-      values were not seen as equal, resulting in the parser complaining
-      about unmatched <literal>ORDER BY</> and <literal>DISTINCT</>
-      expressions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a corner case in regular-expression substring matching
-      (<literal>substring(<replaceable>string</> from
-      <replaceable>pattern</>)</literal>) (Tom)
-     </para>
-
-     <para>
-      The problem occurs when there is a match to the pattern overall but
-      the user has specified a parenthesized subexpression and that
-      subexpression hasn't got a match.  An example is
-      <literal>substring('foo' from 'foo(bar)?')</>.
-      This should return NULL, since <literal>(bar)</> isn't matched, but
-      it was mistakenly returning the whole-pattern match instead (ie,
-      <literal>foo</>).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008c (for
-      DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba,
-      Argentina/San_Luis, and Chile)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect result from <application>ecpg</>'s
-      <function>PGTYPEStimestamp_sub()</> function (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix core dump in <filename>contrib/xml2</>'s
-      <function>xpath_table()</> function when the input query returns a
-      NULL value (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/xml2</>'s makefile to not override
-      <literal>CFLAGS</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>DatumGetBool</> macro to not fail with <application>gcc</>
-      4.3 (Tom)
-     </para>
-
-     <para>
-      This problem affects <quote>old style</> (V0) C functions that
-      return boolean.  The fix is already in 8.3, but the need to
-      back-patch it was not realized at the time.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix longstanding <command>LISTEN</>/<command>NOTIFY</>
-      race condition (Tom)
-     </para>
-
-     <para>
-      In rare cases a session that had just executed a
-      <command>LISTEN</> might not get a notification, even though
-      one would be expected because the concurrent transaction executing
-      <command>NOTIFY</> was observed to commit later.
-     </para>
-
-     <para>
-      A side effect of the fix is that a transaction that has executed
-      a not-yet-committed <command>LISTEN</> command will not see any
-      row in <structname>pg_listener</> for the <command>LISTEN</>,
-      should it choose to look; formerly it would have.  This behavior
-      was never documented one way or the other, but it is possible that
-      some applications depend on the old behavior.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>LISTEN</> and <command>UNLISTEN</> within a
-      prepared transaction (Tom)
-     </para>
-
-     <para>
-      This was formerly allowed but trying to do it had various unpleasant
-      consequences, notably that the originating backend could not exit
-      as long as an <command>UNLISTEN</> remained uncommitted.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix rare crash when an error occurs during a query using a hash index
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix input of datetime values for February 29 in years BC (Tom)
-     </para>
-
-     <para>
-      The former coding was mistaken about which years were leap years.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>unrecognized node type</> error in some variants of
-      <command>ALTER OWNER</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to correctly extract the postmaster's port
-      number from command-line options (Itagaki Takahiro, Tom)
-     </para>
-
-     <para>
-      Previously, <literal>pg_ctl start -w</> could try to contact the
-      postmaster on the wrong port, leading to bogus reports of startup
-      failure.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Use <option>-fwrapv</> to defend against possible misoptimization
-      in recent <application>gcc</> versions (Tom)
-     </para>
-
-     <para>
-      This is known to be necessary when building <productname>PostgreSQL</>
-      with <application>gcc</> 4.3 or later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix display of constant expressions in <literal>ORDER BY</>
-      and <literal>GROUP BY</> (Tom)
-     </para>
-
-     <para>
-      An explictly casted constant would be shown incorrectly.  This could
-      for example lead to corruption of a view definition during
-      dump and reload.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>libpq</> to handle NOTICE messages correctly
-      during COPY OUT (Tom)
-     </para>
-
-     <para>
-      This failure has only been observed to occur when a user-defined
-      datatype's output routine issues a NOTICE, but there is no
-      guarantee it couldn't happen due to other causes.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-11">
-  <title>Release 8.1.11</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-01-07</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.10,
-   including fixes for significant security issues.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <para>
-   This is the last 8.1.X release for which the <productname>PostgreSQL</>
-   community will produce binary packages for <productname>Windows</>.
-   Windows users are encouraged to move to 8.2.X or later,
-   since there are Windows-specific fixes in 8.2.X that
-   are impractical to back-port.  8.1.X will continue to
-   be supported on other platforms.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.11</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent functions in indexes from executing with the privileges of
-      the user running <command>VACUUM</>, <command>ANALYZE</>, etc (Tom)
-     </para>
-
-     <para>
-      Functions used in index expressions and partial-index
-      predicates are evaluated whenever a new table entry is made.  It has
-      long been understood that this poses a risk of trojan-horse code
-      execution if one modifies a table owned by an untrustworthy user.
-      (Note that triggers, defaults, check constraints, etc. pose the
-      same type of risk.)  But functions in indexes pose extra danger
-      because they will be executed by routine maintenance operations
-      such as <command>VACUUM FULL</>, which are commonly performed
-      automatically under a superuser account.  For example, a nefarious user
-      can execute code with superuser privileges by setting up a
-      trojan-horse index definition and waiting for the next routine vacuum.
-      The fix arranges for standard maintenance operations
-      (including <command>VACUUM</>, <command>ANALYZE</>, <command>REINDEX</>,
-      and <command>CLUSTER</>) to execute as the table owner rather than
-      the calling user, using the same privilege-switching mechanism already
-      used for <literal>SECURITY DEFINER</> functions.  To prevent bypassing
-      this security measure, execution of <command>SET SESSION
-      AUTHORIZATION</> and <command>SET ROLE</> is now forbidden within a
-      <literal>SECURITY DEFINER</> context.  (CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Repair assorted bugs in the regular-expression package (Tom, Will Drewry)
-     </para>
-
-     <para>
-      Suitably crafted regular-expression patterns could cause crashes,
-      infinite or near-infinite looping, and/or massive memory consumption,
-      all of which pose denial-of-service hazards for applications that
-      accept regex search patterns from untrustworthy sources.
-      (CVE-2007-4769, CVE-2007-4772, CVE-2007-6067)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require non-superusers who use <filename>/contrib/dblink</> to use only
-      password authentication, as a security measure (Joe)
-     </para>
-
-     <para>
-      The fix that appeared for this in 8.1.10 was incomplete, as it plugged
-      the hole for only some <filename>dblink</> functions.  (CVE-2007-6601,
-      CVE-2007-3278)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2007k
-      (in particular, recent Argentina changes) (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve planner's handling of LIKE/regex estimation in non-C locales
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner failure in some cases of <literal>WHERE false AND var IN
-      (SELECT ...)</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Preserve the tablespace of indexes that are
-      rebuilt by <command>ALTER TABLE ... ALTER COLUMN TYPE</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make archive recovery always start a new WAL timeline, rather than only
-      when a recovery stop time was used (Simon)
-     </para>
-
-     <para>
-      This avoids a corner-case risk of trying to overwrite an existing
-      archived copy of the last WAL segment, and seems simpler and cleaner
-      than the original definition.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>VACUUM</> not use all of <varname>maintenance_work_mem</>
-      when the table is too small for it to be useful (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential crash in <function>translate()</> when using a multibyte
-      database encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix overflow in <literal>extract(epoch from interval)</> for intervals
-      exceeding 68 years (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Perl to not fail when a UTF-8 regular expression is used
-      in a trusted function (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Perl to cope when platform's Perl defines type <literal>bool</>
-      as <literal>int</> rather than <literal>char</> (Tom)
-     </para>
-
-     <para>
-      While this could theoretically happen anywhere, no standard build of
-      Perl did things this way ... until <productname>Mac OS X</> 10.5.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Python to not crash on long exception messages (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_dump</> to correctly handle inheritance child tables
-      that have default expressions different from their parent's (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>libpq</> crash when <varname>PGPASSFILE</> refers
-      to a file that is not a plain file (Martin Pitt)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <application>ecpg</> parser fixes (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <filename>contrib/pgcrypto</> defend against
-      <application>OpenSSL</> libraries that fail on keys longer than 128
-      bits; which is the case at least on some Solaris versions (Marko Kreen)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <filename>contrib/tablefunc</>'s <function>crosstab()</> handle
-      NULL rowid as a category in its own right, rather than crashing (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <type>tsvector</> and <type>tsquery</> output routines to
-      escape backslashes correctly (Teodor, Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash of <function>to_tsvector()</> on huge input strings (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require a specific version of <productname>Autoconf</> to be used
-      when re-generating the <command>configure</> script (Peter)
-     </para>
-
-     <para>
-      This affects developers and packagers only.  The change was made
-      to prevent accidental use of untested combinations of
-      <productname>Autoconf</> and <productname>PostgreSQL</> versions.
-      You can remove the version check if you really want to use a
-      different <productname>Autoconf</> version, but it's
-      your responsibility whether the result works or not.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-10">
-  <title>Release 8.1.10</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-09-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.9.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.10</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent index corruption when a transaction inserts rows and
-      then aborts close to the end of a concurrent <command>VACUUM</>
-      on the same table (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>CREATE DOMAIN ... DEFAULT NULL</> work properly (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow the <type>interval</> data type to accept input consisting only of
-      milliseconds or microseconds (Neil)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Speed up rtree index insertion (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix excessive logging of <acronym>SSL</> error messages (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix logging so that log messages are never interleaved when using
-      the syslogger process (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash when <varname>log_min_error_statement</> logging runs out
-      of memory (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect handling of some foreign-key corner cases (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent <command>REINDEX</> and <command>CLUSTER</> from failing
-      due to attempting to process temporary tables of other sessions (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update the time zone database rules, particularly New Zealand's upcoming changes (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Windows socket improvements (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Suppress timezone name (<literal>%Z</>) in log timestamps on Windows
-      because of possible encoding mismatches (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require non-superusers who use <filename>/contrib/dblink</> to use only
-      password authentication, as a security measure (Joe)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-9">
-  <title>Release 8.1.9</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-04-23</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.8,
-   including a security fix.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.9</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Support explicit placement of the temporary-table schema within
-     <varname>search_path</>, and disable searching it for functions
-     and operators (Tom)
-    </para>
-    <para>
-     This is needed to allow a security-definer function to set a
-     truly secure value of <varname>search_path</>.  Without it,
-     an unprivileged SQL user can use temporary objects to execute code
-     with the privileges of the security-definer function (CVE-2007-2138).
-     See <command>CREATE FUNCTION</> for more information.
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     <filename>/contrib/tsearch2</> crash fixes (Teodor)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Require <command>COMMIT PREPARED</> to be executed in the same
-     database as the transaction was prepared in (Heikki)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix potential-data-corruption bug in how <command>VACUUM FULL</> handles
-     <command>UPDATE</> chains (Tom, Pavan Deolasee)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Planner fixes, including improving outer join and bitmap scan
-     selection logic (Tom)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix PANIC during enlargement of a hash index (bug introduced in 8.1.6)
-     (Tom)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix POSIX-style timezone specs to follow new USA DST rules (Tom)
-    </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-8">
-  <title>Release 8.1.8</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-02-07</simpara>
-  </note>
-
-  <para>
-   This release contains one fix from 8.1.7.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.8</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Remove overly-restrictive check for type length in constraints and
-     functional indexes(Tom)
-    </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-7">
-  <title>Release 8.1.7</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-02-05</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.6, including
-   a security fix.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.7</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Remove security vulnerabilities that allowed connected users
-     to read backend memory (Tom)
-    </para>
-    <para>
-     The vulnerabilities involve suppressing the normal check that a SQL
-     function returns the data type it's declared to, and changing the
-     data type of a table column (CVE-2007-0555, CVE-2007-0556).  These
-     errors can easily be exploited to cause a backend crash, and in
-     principle might be used to read database content that the user
-     should not be able to access.
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix rare bug wherein btree index page splits could fail
-     due to choosing an infeasible split point (Heikki Linnakangas)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Improve <command>VACUUM</> performance for databases with many tables (Tom)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix autovacuum to avoid leaving non-permanent transaction IDs in
-     non-connectable databases (Alvaro)
-    </para>
-
-    <para>
-     This bug affects the 8.1 branch only.
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix for rare Assert() crash triggered by <literal>UNION</> (Tom)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Tighten security of multi-byte character processing for UTF8 sequences
-     over three bytes long (Tom)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix bogus <quote>permission denied</> failures occurring on Windows
-     due to attempts to fsync already-deleted files (Magnus, Tom)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix possible crashes when an already-in-use PL/pgSQL function is
-     updated (Tom)
-    </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-6">
-  <title>Release 8.1.6</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-01-08</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.5.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.6</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Improve handling of <function>getaddrinfo()</> on AIX (Tom)
-     </para>
-
-     <para>
-      This fixes a problem with starting the statistics collector,
-      among other things.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_restore</> to handle a tar-format backup
-      that contains large objects (blobs) with comments (Tom)
-     </para>
-    </listitem>
-
-     <listitem>
-      <para>
-       Fix <quote>failed to re-find parent key</> errors in
-       <command>VACUUM</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Clean out <filename>pg_internal.init</> cache files during server
-       restart (Simon)
-      </para>
-
-      <para>
-       This avoids a hazard that the cache files might contain stale
-       data after PITR recovery.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix race condition for truncation of a large relation across a
-       gigabyte boundary by <command>VACUUM</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix bug causing needless deadlock errors on row-level locks (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix bugs affecting multi-gigabyte hash indexes (Tom)
-      </para>
-     </listitem>
-
-    <listitem>
-     <para>
-      Fix possible deadlock in Windows signal handling (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix error when constructing an <literal>ARRAY[]</> made up of multiple
-      empty elements (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix ecpg memory leak during connection (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix for Darwin (OS X) compilation (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>to_number()</> and <function>to_char(numeric)</>
-      are now <literal>STABLE</>, not <literal>IMMUTABLE</>, for
-      new <application>initdb</> installs (Tom)
-     </para>
-
-     <para>
-      This is because <varname>lc_numeric</> can potentially
-      change the output of these functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve index usage of regular expressions that use parentheses (Tom)
-     </para>
-
-     <para>
-      This improves <application>psql</> <literal>\d</> performance also.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update timezone database
-     </para>
-
-     <para>
-      This affects Australian and Canadian daylight-savings rules in
-      particular.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-5">
-  <title>Release 8.1.5</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-10-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.4.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.5</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Disallow aggregate functions in <command>UPDATE</>
-commands, except within sub-SELECTs (Tom)</para>
-<para>The behavior of such an aggregate was unpredictable, and in 8.1.X
-could cause a crash, so it has been disabled.  The SQL standard does not allow
-this either.</para></listitem>
-<listitem><para>Fix core dump when an untyped literal is taken as
-ANYARRAY</para></listitem>
-<listitem><para>Fix core dump in duration logging for extended query protocol
-when a <command>COMMIT</> or <command>ROLLBACK</> is
-executed</para></listitem>
-<listitem><para>Fix mishandling of AFTER triggers when query contains a SQL
-function returning multiple rows (Tom)</para></listitem>
-<listitem><para>Fix <command>ALTER TABLE ... TYPE</> to recheck
-<literal>NOT NULL</> for <literal>USING</> clause (Tom)</para></listitem>
-<listitem><para>Fix <function>string_to_array()</> to handle overlapping
- matches for the separator string</para>
-<para>For example, <literal>string_to_array('123xx456xxx789', 'xx')</>.
-</para></listitem>
-<listitem><para>Fix <function>to_timestamp()</> for
-<literal>AM</>/<literal>PM</> formats (Bruce)</para></listitem>
-<listitem><para>Fix autovacuum's calculation that decides whether
- <command>ANALYZE</> is needed (Alvaro)</para></listitem>
-<listitem><para>Fix corner cases in pattern matching for
- <application>psql</>'s <literal>\d</> commands</para></listitem>
-<listitem><para>Fix index-corrupting bugs in /contrib/ltree
- (Teodor)</para></listitem>
-<listitem><para>Numerous robustness fixes in <application>ecpg</> (Joachim
-Wieland)</para></listitem>
-<listitem><para>Fix backslash escaping in /contrib/dbmirror</para></listitem>
-<listitem><para>Minor fixes in /contrib/dblink and /contrib/tsearch2</para>
-</listitem>
-<listitem><para>Efficiency improvements in hash tables and bitmap index scans
-(Tom)</para></listitem>
-<listitem><para>Fix instability of statistics collection on Windows (Tom, Andrew)</para></listitem>
-<listitem><para>Fix <varname>statement_timeout</> to use the proper
-units on Win32 (Bruce)</para>
-<para>In previous Win32 8.1.X versions, the delay was off by a factor of
-100.</para></listitem>
-<listitem><para>Fixes for <acronym>MSVC</> and <productname>Borland C++</>
-compilers (Hiroshi Saito)</para></listitem>
-<listitem><para>Fixes for <systemitem class="osname">AIX</> and
-<productname>Intel</> compilers (Tom)</para></listitem>
-<listitem><para>Fix rare bug in continuous archiving (Tom)</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-4">
-  <title>Release 8.1.4</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-05-23</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.3,
-   including patches for extremely serious security issues.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.4</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-
-   <para>
-    Full security against the SQL-injection attacks described in
-    CVE-2006-2313 and CVE-2006-2314 might require changes in application
-    code.  If you have applications that embed untrustworthy strings
-    into SQL commands, you should examine them as soon as possible to
-    ensure that they are using recommended escaping techniques.  In
-    most cases, applications should be using subroutines provided by
-    libraries or drivers (such as <application>libpq</>'s
-    <function>PQescapeStringConn()</>) to perform string escaping,
-    rather than relying on <foreignphrase>ad hoc</> code to do it.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Change the server to reject invalidly-encoded multibyte
-characters in all cases (Tatsuo, Tom)</para>
-<para>While <productname>PostgreSQL</> has been moving in this direction for
-some time, the checks are now applied uniformly to all encodings and all
-textual input, and are now always errors not merely warnings.  This change
-defends against SQL-injection attacks of the type described in CVE-2006-2313.
-</para></listitem>
-
-<listitem><para>Reject unsafe uses of <literal>\'</> in string literals</para>
-<para>As a server-side defense against SQL-injection attacks of the type
-described in CVE-2006-2314, the server now only accepts <literal>''</> and not
-<literal>\'</> as a representation of ASCII single quote in SQL string
-literals.  By default, <literal>\'</> is rejected only when
-<varname>client_encoding</> is set to a client-only encoding (SJIS, BIG5, GBK,
-GB18030, or UHC), which is the scenario in which SQL injection is possible.
-A new configuration parameter <varname>backslash_quote</> is available to
-adjust this behavior when needed.  Note that full security against
-CVE-2006-2314 might require client-side changes; the purpose of
-<varname>backslash_quote</> is in part to make it obvious that insecure
-clients are insecure.
-</para></listitem>
-
-<listitem><para>Modify <application>libpq</>'s string-escaping routines to be
-aware of encoding considerations and
-<varname>standard_conforming_strings</></para>
-<para>This fixes <application>libpq</>-using applications for the security
-issues described in CVE-2006-2313 and CVE-2006-2314, and also future-proofs
-them against the planned changeover to SQL-standard string literal syntax.
-Applications that use multiple <productname>PostgreSQL</> connections
-concurrently should migrate to <function>PQescapeStringConn()</> and
-<function>PQescapeByteaConn()</> to ensure that escaping is done correctly
-for the settings in use in each database connection.  Applications that
-do string escaping <quote>by hand</> should be modified to rely on library
-routines instead.
-</para></listitem>
-
-<listitem><para>Fix weak key selection in pgcrypto (Marko Kreen)</para>
-<para>Errors in fortuna PRNG reseeding logic could cause a predictable
-session key to be selected by <function>pgp_sym_encrypt()</> in some cases.
-This only affects non-OpenSSL-using builds.
-</para></listitem>
-
-<listitem><para>Fix some incorrect encoding conversion functions</para>
-<para><function>win1251_to_iso</>, <function>win866_to_iso</>,
-<function>euc_tw_to_big5</>, <function>euc_tw_to_mic</>,
-<function>mic_to_euc_tw</> were all broken to varying
-extents.
-</para></listitem>
-
-<listitem><para>Clean up stray remaining uses of <literal>\'</> in strings
-(Bruce, Jan)</para></listitem>
-
-<listitem><para>Make autovacuum visible in <structname>pg_stat_activity</>
-(Alvaro)</para></listitem>
-
-<listitem><para>Disable <literal>full_page_writes</> (Tom)</para>
-<para>In certain cases, having <literal>full_page_writes</> off would cause
-crash recovery to fail.  A proper fix will appear in 8.2; for now it's just
-disabled.
-</para></listitem>
-
-<listitem><para>Various planner fixes, particularly for bitmap index scans and
-MIN/MAX optimization (Tom)</para></listitem>
-
-<listitem><para>Fix incorrect optimization in merge join (Tom)</para>
-<para>Outer joins could sometimes emit multiple copies of unmatched rows.
-</para></listitem>
-
-<listitem><para>Fix crash from using and modifying a plpgsql function in the
-same transaction</para></listitem>
-
-<listitem><para>Fix WAL replay for case where a B-Tree index has been
-truncated</para></listitem>
-
-<listitem><para>Fix <literal>SIMILAR TO</> for patterns involving
-<literal>|</> (Tom)</para></listitem>
-
-<listitem><para>Fix <command>SELECT INTO</> and <command>CREATE TABLE AS</> to
-create tables in the default tablespace, not the base directory (Kris
-Jurka)</para></listitem>
-
-<listitem><para>Fix server to use custom DH SSL parameters correctly (Michael
-Fuhr)</para></listitem>
-
-<listitem><para>Improve qsort performance (Dann Corbit)</para>
-<para>Currently this code is only used on Solaris.
-</para></listitem>
-
-<listitem><para>Fix for OS/X Bonjour on x86 systems (Ashley Clark)</para></listitem>
-
-<listitem><para>Fix various minor memory leaks</para></listitem>
-
-<listitem><para>Fix problem with password prompting on some Win32 systems
-(Robert Kinberg)</para></listitem>
-
-<listitem><para>Improve <application>pg_dump</>'s handling of default values
-for domains</para></listitem>
-
-<listitem><para>Fix <application>pg_dumpall</> to handle identically-named
-users and groups reasonably (only possible when dumping from a pre-8.1 server)
-(Tom)</para>
-<para>The user and group will be merged into a single role with
-<literal>LOGIN</> permission.  Formerly the merged role wouldn't have
-<literal>LOGIN</> permission, making it unusable as a user.
-</para></listitem>
-
-<listitem><para>Fix <application>pg_restore</> <literal>-n</> to work as
-documented (Tom)</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-3">
-  <title>Release 8.1.3</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-02-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.2,
-   including one very serious security issue.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.3</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, if you are upgrading from a version earlier than 8.1.2,
-    see the release notes for 8.1.2.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix bug that allowed any logged-in user to <command>SET
-ROLE</> to any other database user id (CVE-2006-0553)</para>
-<para>Due to inadequate validity checking, a user could exploit the special
-case that <command>SET ROLE</> normally uses to restore the previous role
-setting after an error.  This allowed ordinary users to acquire superuser
-status, for example.
-The escalation-of-privilege risk exists only in 8.1.0-8.1.2.
-However, in all releases back to 7.3 there is a related bug in <command>SET
-SESSION AUTHORIZATION</> that allows unprivileged users to crash the server,
-if it has been compiled with Asserts enabled (which is not the default).
-Thanks to Akio Ishida for reporting this problem.
-</para></listitem>
-
-<listitem><para>Fix bug with row visibility logic in self-inserted
-rows (Tom)</para>
-<para>Under rare circumstances a row inserted by the current command
-could be seen as already valid, when it should not be.  Repairs bug
-created in 8.0.4, 7.4.9, and 7.3.11 releases.
-</para></listitem>
-
-<listitem><para>Fix race condition that could lead to <quote>file already
-exists</> errors during pg_clog and pg_subtrans file creation
-(Tom)</para></listitem>
-
-<listitem><para>Fix cases that could lead to crashes if a cache-invalidation
-message arrives at just the wrong time (Tom)</para></listitem>
-
-<listitem><para>Properly check <literal>DOMAIN</> constraints for
-<literal>UNKNOWN</> parameters in prepared statements
-(Neil)</para></listitem>
-
-<listitem><para>Ensure <command>ALTER COLUMN TYPE</> will process
-<literal>FOREIGN KEY</>, <literal>UNIQUE</>, and <literal>PRIMARY KEY</>
-constraints in the proper order (Nakano Yoshihisa)</para></listitem>
-
-<listitem><para>Fixes to allow restoring dumps that have cross-schema
-references to custom operators or operator classes (Tom)</para></listitem>
-
-<listitem><para>Allow <application>pg_restore</> to continue properly after a
-<command>COPY</> failure; formerly it tried to treat the remaining
-<command>COPY</> data as SQL commands (Stephen Frost)</para></listitem>
-
-<listitem><para>Fix <application>pg_ctl</> <literal>unregister</> crash
-when the  data directory is not specified (Magnus)</para></listitem>
-
-<listitem><para>Fix <application>libpq</> <function>PQprint</> HTML tags
-(Christoph Zwerschke)</para></listitem>
-
-<listitem><para>Fix <application>ecpg</> crash on AMD64 and PPC
-(Neil)</para></listitem>
-
-<listitem><para>Allow <literal>SETOF</> and <literal>%TYPE</> to be used
-together in function result type declarations</para></listitem>
-
-<listitem><para>Recover properly if error occurs during argument passing
-in <application>PL/python</> (Neil)</para></listitem>
-
-<listitem><para>Fix memory leak in <function>plperl_return_next</>
-(Neil)</para></listitem>
-
-<listitem><para>Fix <application>PL/perl</>'s handling of locales on
-Win32 to match the backend (Andrew)</para></listitem>
-
-<listitem><para>Various optimizer fixes (Tom)</para></listitem>
-
-<listitem><para>Fix crash when <literal>log_min_messages</> is set to
-<literal>DEBUG3</> or above in <filename>postgresql.conf</> on Win32
-(Bruce)</para></listitem>
-
-<listitem><para>Fix <application>pgxs</> <literal>-L</> library path
-specification for Win32, Cygwin, OS X, AIX (Bruce)</para></listitem>
-
-<listitem><para>Check that SID is enabled while checking for Win32 admin
-privileges (Magnus)</para></listitem>
-
-<listitem><para>Properly reject out-of-range date inputs (Kris
-Jurka)</para></listitem>
-
-<listitem><para>Portability fix for testing presence of <function>finite</>
-and <function>isinf</> during configure (Tom)</para></listitem>
-
-<listitem><para>Improve speed of <command>COPY IN</> via libpq, by
-avoiding a kernel call per data line (Alon Goldshuv)</para></listitem>
-
-<listitem><para>Improve speed of <filename>/contrib/tsearch2</> index
-creation (Tom)</para></listitem>
-
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-2">
-  <title>Release 8.1.2</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-01-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.1.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.2</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-    However, you might need to <command>REINDEX</> indexes on textual
-    columns after updating, if you are affected by the locale or
-    <application>plperl</> issues described below.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix Windows code so that postmaster will continue rather
-than exit if there is no more room in ShmemBackendArray (Magnus)</para>
-<para>The previous behavior could lead to a denial-of-service situation if too
-many connection requests arrive close together.  This applies
-<emphasis>only</> to the Windows port.</para></listitem>
-
-<listitem><para>Fix bug introduced in 8.0 that could allow ReadBuffer
-to return an already-used page as new, potentially causing loss of
-recently-committed data (Tom)</para></listitem>
-
-<listitem><para>Fix for protocol-level Describe messages issued
-outside a transaction or in a failed transaction (Tom)</para></listitem>
-
-<listitem><para>Fix character string comparison for locales that consider
-different character combinations as equal, such as Hungarian (Tom)</para>
-<para>This might require <command>REINDEX</> to fix existing indexes on
-textual columns.</para></listitem>
-
-<listitem><para>Set locale environment variables during postmaster startup
-to ensure that <application>plperl</> won't change the locale later</para>
-<para>This fixes a problem that occurred if the <application>postmaster</> was
-started with environment variables specifying a different locale than what
-<application>initdb</> had been told.  Under these conditions, any use of
-<application>plperl</> was likely to lead to corrupt indexes.  You might need
-<command>REINDEX</> to fix existing indexes on
-textual columns if this has happened to you.</para></listitem>
-
-<listitem><para>Allow more flexible relocation of installation
-directories (Tom)</para>
-<para>Previous releases supported relocation only if all installation
-directory paths were the same except for the last component.</para></listitem>
-
-<listitem><para>Prevent crashes caused by the use of
-<literal>ISO-8859-5</> and <literal>ISO-8859-9</> encodings
-(Tatsuo)</para></listitem>
-
-<listitem><para>Fix longstanding bug in strpos() and regular expression
-handling in certain rarely used Asian multi-byte character sets (Tatsuo)
-</para></listitem>
-
-<listitem><para>Fix bug where COPY CSV mode considered any
-<literal>\.</> to terminate the copy data</para> <para>The new code
-requires <literal>\.</> to appear alone on a line, as per
-documentation.</para></listitem>
-
-<listitem><para>Make COPY CSV mode quote a literal data value of
-<literal>\.</> to ensure it cannot be interpreted as the
-end-of-data marker (Bruce)</para></listitem>
-
-<listitem><para>Various fixes for functions returning <literal>RECORD</>s
-(Tom) </para></listitem>
-
-<listitem><para>Fix processing of <filename>postgresql.conf</> so a
-final line with no newline is processed properly (Tom)
-</para></listitem>
-
-<listitem><para>Fix bug in <filename>/contrib/pgcrypto</> gen_salt,
-which caused it not to use all available salt space for MD5 and
-XDES algorithms (Marko Kreen, Solar Designer)</para>
-<para>Salts for Blowfish and standard DES are unaffected.</para></listitem>
-
-<listitem><para>Fix autovacuum crash when processing expression indexes
-</para></listitem>
-
-<listitem><para>Fix <filename>/contrib/dblink</> to throw an error,
-rather than crashing, when the number of columns specified is different from
-what's actually returned by the query (Joe)</para></listitem>
-
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1-1">
-  <title>Release 8.1.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-12-12</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.1.0.
-   For information about new features in the 8.1 major release, see
-   <xref linkend="release-8-1">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.1.1</title>
-
-   <para>
-    A dump/restore is not required for those running 8.1.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fix incorrect optimizations of outer-join conditions
-(Tom)</para></listitem>
-
-<listitem><para>Fix problems with wrong reported column names in cases
-involving sub-selects flattened by the optimizer (Tom)</para></listitem>
-
-<listitem><para>Fix update failures in scenarios involving CHECK constraints,
-toasted columns, <emphasis>and</> indexes (Tom)</para></listitem>
-
-<listitem><para>Fix bgwriter problems after recovering from errors
-(Tom)</para>
-<para>
-The background writer was found to leak buffer pins after write errors.
-While not fatal in itself, this might lead to mysterious blockages of
-later VACUUM commands.
-</para>
-</listitem>
-
-<listitem><para>Prevent failure if client sends Bind protocol message
-when current transaction is already aborted</para></listitem>
-
-<listitem><para><filename>/contrib/tsearch2</> and <filename>/contrib/ltree</>
-fixes (Teodor)</para></listitem>
-
-<listitem><para>Fix problems with translated error messages in
-languages that require word reordering, such as Turkish; also problems with
-unexpected truncation of output strings and wrong display of the smallest
-possible bigint value (Andrew, Tom)</para>
-<para>
-These problems only appeared on platforms that were using our
-<filename>port/snprintf.c</> code, which includes BSD variants if
-<literal>--enable-nls</> was given, and perhaps others.  In addition,
-a different form of the translated-error-message problem could appear
-on Windows depending on which version of <filename>libintl</> was used.
-</para></listitem>
-
-<listitem><para>Re-allow <literal>AM</>/<literal>PM</>, <literal>HH</>,
-<literal>HH12</>, and <literal>D</> format specifiers for
-<function>to_char(time)</> and <function>to_char(interval)</>.
-(<function>to_char(interval)</> should probably use
-<literal>HH24</>.) (Bruce)</para></listitem>
-
-<listitem><para>AIX, HPUX, and MSVC compile fixes (Tom, Hiroshi
-Saito)</para></listitem>
-
-<listitem><para>Optimizer improvements (Tom)</para></listitem>
-
-<listitem><para>Retry file reads and writes after Windows
-NO_SYSTEM_RESOURCES error (Qingqing Zhou)</para></listitem>
-
-<listitem><para>Prevent <application>autovacuum</> from crashing during
-ANALYZE of expression index (Alvaro)</para></listitem>
-
-<listitem><para>Fix problems with ON COMMIT DELETE ROWS temp
-tables</para></listitem>
-
-<listitem><para>Fix problems when a trigger alters the output of a SELECT
-DISTINCT query</para></listitem>
-
-<listitem><para>Add 8.1.0 release note item on how to migrate invalid
-<literal>UTF-8</> byte sequences (Paul Lindner)</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-1">
-  <title>Release 8.1</title>
-
-  <note>
-   <title>Release Date</title>
-   <simpara>2005-11-08</simpara>
-  </note>
-
-  <sect2>
-   <title>Overview</title>
-
-   <para>
-    Major changes in this release:
-   </para>
-
-   <variablelist>
-
-    <varlistentry>
-     <term>
-      Improve concurrent access to the shared buffer cache (Tom)
-     </term>
-
-     <listitem>
-      <para>
-       Access to the shared buffer cache was identified as a
-       significant scalability problem, particularly on multi-CPU
-       systems. In this release, the way that locking is done in the
-       buffer manager has been overhauled to reduce lock contention
-       and improve scalability. The buffer manager has also been
-       changed to use a <quote>clock sweep</quote> replacement
-       policy.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Allow index scans to use an intermediate in-memory bitmap (Tom)
-     </term>
-
-     <listitem>
-      <para>
-       In previous releases, only a single index could be used to do
-       lookups on a table. With this feature, if a query has
-       <command>WHERE tab.col1 = 4 and tab.col2 = 9</>, and there is
-       no multicolumn index on <literal>col1</> and <literal>col2</>,
-       but there is an index on <literal>col1</> and another on
-       <literal>col2</>, it is possible to search both indexes and
-       combine the results in memory, then do heap fetches for only
-       the rows matching both the <literal>col1</> and
-       <literal>col2</> restrictions. This is very useful in
-       environments that have a lot of unstructured queries where it
-       is impossible to create indexes that match all possible access
-       conditions.  Bitmap scans are useful even with a single index,
-       as they reduce the amount of random access needed; a bitmap
-       index scan is efficient for retrieving fairly large fractions
-       of the complete table, whereas plain index scans are not.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Add two-phase commit (Heikki Linnakangas, Alvaro, Tom)
-     </term>
-
-     <listitem>
-      <para>
-       Two-phase commit allows transactions to be "prepared" on several
-       computers, and once all computers have successfully prepared
-       their transactions (none failed), all transactions can be
-       committed. Even if a machine crashes after a prepare, the
-       prepared transaction can be committed after the machine is
-       restarted. New syntax includes <command>PREPARE TRANSACTION</> and
-       <command>COMMIT/ROLLBACK PREPARED</>. A new system view
-       <literal>pg_prepared_xacts</> has also been added.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Create a new role system that replaces users and groups
-      (Stephen Frost)
-     </term>
-
-     <listitem>
-      <para>
-       Roles are a combination of users and groups. Like users, they
-       can have login capability, and like groups, a role can have
-       other roles as members. Roles basically remove the distinction
-       between users and groups. For example, a role can:
-      </para>
-
-      <itemizedlist>
-
-       <listitem>
-        <para>
-          Have login capability (optionally)
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         Own objects
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         Hold access permissions for database objects
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         Inherit permissions from other roles it is a member of
-        </para>
-       </listitem>
-
-      </itemizedlist>
-      <para>
-       Once a user logs into a role, she obtains capabilities of
-       the login role plus any inherited roles, and can use
-       <command>SET ROLE</> to switch to other roles she is a member of.
-       This feature is a generalization of the SQL standard's concept of
-       roles.
-       This change also replaces <structname>pg_shadow</> and
-       <structname>pg_group</> by new role-capable catalogs
-       <structname>pg_authid</> and <structname>pg_auth_members</>. The old
-       tables are redefined as read-only views on the new role tables.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Automatically use indexes for <function>MIN()</> and
-      <function>MAX()</> (Tom)
-     </term>
-
-     <listitem>
-      <para>
-       In previous releases, the only way to use an index for
-       <function>MIN()</> or <function>MAX()</> was to rewrite the
-       query as <command>SELECT col FROM tab ORDER BY col LIMIT 1</>.
-       Index usage now happens automatically.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Move <filename>/contrib/pg_autovacuum</> into the main server
-      (Alvaro)
-     </term>
-
-     <listitem>
-      <para>
-       Integrating autovacuum into the server allows it to be
-       automatically started and stopped in sync with the database
-       server, and allows autovacuum to be configured from
-       <filename>postgresql.conf</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Add shared row level locks using <command>SELECT ... FOR SHARE</>
-      (Alvaro)
-     </term>
-
-     <listitem>
-      <para>
-       While <productname>PostgreSQL</productname>'s MVCC locking
-       allows <command>SELECT</> to never be blocked by writers and
-       therefore does not need shared row locks for typical operations,
-       shared locks are useful for applications that require shared row
-       locking.  In particular this reduces the locking requirements
-       imposed by referential integrity checks.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Add dependencies on shared objects, specifically roles
-      (Alvaro)
-     </term>
-
-     <listitem>
-      <para>
-       This extension of the dependency mechanism prevents roles from
-       being dropped while there are still database objects they own.
-       Formerly it was possible to accidentally <quote>orphan</> objects by
-       deleting their owner.  While this could be recovered from, it
-       was messy and unpleasant.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Improve performance for partitioned tables (Simon)
-     </term>
-
-     <listitem>
-      <para>
-       The new <varname>constraint_exclusion</varname> configuration
-       parameter avoids lookups on child tables where constraints indicate
-       that no matching rows exist in the child table.
-      </para>
-      <para>
-       This allows for a basic type of table partitioning. If child tables
-       store separate key ranges and this is enforced using appropriate
-       <command>CHECK</> constraints, the optimizer will skip child
-       table accesses when the constraint guarantees no matching rows
-       exist in the child table.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </sect2>
-
-  <sect2>
-   <title>Migration to Version 8.1</title>
-
-   <para>
-    A dump/restore using <application>pg_dump</application> is required
-    for those wishing to migrate data from any previous release.
-   </para>
-
-   <para>
-    The 8.0 release announced that the <function>to_char()</> function
-    for intervals would be removed in 8.1. However, since no better API
-    has been suggested, <function>to_char(interval)</> has been enhanced in
-    8.1 and will remain in the server.
-   </para>
-
-   <para>
-    Observe the following incompatibilities:
-   </para>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      <varname>add_missing_from</> is now false by default (Neil)
-     </para>
-     <para>
-      By default, we now generate an error if a table is used in a query
-      without a <literal>FROM</> reference.  The old behavior is still
-      available, but the parameter must be set to 'true' to obtain it.
-     </para>
-
-     <para>
-      It might be necessary to set <varname>add_missing_from</> to true
-      in order to load an existing dump file, if the dump contains any
-      views or rules created using the implicit-<literal>FROM</> syntax.
-      This should be a one-time annoyance, because
-      <productname>PostgreSQL</productname> 8.1 will convert
-      such views and rules to standard explicit-<literal>FROM</> syntax.
-      Subsequent dumps will therefore not have the problem.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Cause input of a zero-length string (<literal>''</literal>) for
-      <type>float4</type>/<type>float8</type>/<type>oid</type>
-      to throw an error, rather than treating it as a zero (Neil)
-     </para>
-     <para>
-      This change is consistent with the current handling of
-      zero-length strings for integers. The schedule for this change
-      was announced in 8.0.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <varname>default_with_oids</> is now false by default (Neil)
-     </para>
-     <para>
-      With this option set to false, user-created tables no longer
-      have an OID column unless <command>WITH OIDS</> is specified in
-      <command>CREATE TABLE</>. Though OIDs have existed in all
-      releases of <productname>PostgreSQL</>, their use is limited
-      because they are only four bytes long and the counter is shared
-      across all installed databases. The preferred way of uniquely
-      identifying rows is via sequences and the <type>SERIAL</> type,
-      which have been supported since <productname>PostgreSQL</> 6.4.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>E''</> syntax so eventually ordinary strings can
-      treat backslashes literally (Bruce)
-     </para>
-     <para>
-      Currently <productname>PostgreSQL</productname> processes a
-      backslash in a string literal as introducing a special escape sequence,
-      e.g. <literal>\n</> or <literal>\010</>.
-      While this allows easy entry of special values, it is
-      nonstandard and makes porting of applications from other
-      databases more difficult. For this reason, the
-      <productname>PostgreSQL</productname> project is planning to
-      remove the special meaning of backslashes in strings. For
-      backward compatibility and for users who want special backslash
-      processing, a new string syntax has been created. This new string
-      syntax is formed by writing an <literal>E</> immediately preceding the
-      single quote that starts the string, e.g. <literal>E'hi\n'</>. While
-      this release does not change the handling of backslashes in strings, it
-      does add new configuration parameters to help users migrate applications
-      for future releases:
-     </para>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        <varname>standard_conforming_strings</> &mdash; does this release
-        treat backslashes literally in ordinary strings?
-       </para>
-      </listitem>
-
-      <listitem>
-      <para>
-       <varname>escape_string_warning</> &mdash; warn about backslashes in
-       ordinary (non-E) strings
-      </para>
-     </listitem>
-
-     </itemizedlist>
-
-     <para>
-      The <varname>standard_conforming_strings</> value is read-only.
-      Applications can retrieve the value to know how backslashes are
-      processed.  (Presence of the parameter can also be taken as an
-      indication that <literal>E''</> string syntax is supported.)
-      In a future release, <varname>standard_conforming_strings</>
-      will be true, meaning backslashes will be treated literally in
-      non-E strings. To prepare for this change, use <literal>E''</>
-      strings in places that need special backslash processing, and
-      turn on <varname>escape_string_warning</> to find additional
-      strings that need to be converted to use <literal>E''</>.
-      Also, use two single-quotes (<literal>''</>) to embed a literal
-      single-quote in a string, rather than the
-      <productname>PostgreSQL</productname>-supported syntax of
-      backslash single-quote (<literal>\'</>).  The former is
-      standards-conforming and does not require the use of the
-      <literal>E''</> string syntax.  You can also use the
-      <literal>$$</> string syntax, which does not treat backslashes
-      specially.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>REINDEX DATABASE</> reindex all indexes in the
-      database (Tom)
-     </para>
-     <para>
-      Formerly, <command>REINDEX DATABASE</> reindexed only
-      system tables. This new behavior seems more intuitive. A new
-      command <command>REINDEX SYSTEM</> provides the old functionality
-      of reindexing just the system tables.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Read-only large object descriptors now obey MVCC snapshot semantics
-     </para>
-     <para>
-      When a large object is opened with <literal>INV_READ</> (and not
-      <literal>INV_WRITE</>), the data read from the descriptor will now
-      reflect a <quote>snapshot</> of the large object's state at the
-      time of the transaction snapshot in use by the query that called
-      <function>lo_open()</>.  To obtain the old behavior of always
-      returning the latest committed data, include <literal>INV_WRITE</>
-      in the mode flags for <function>lo_open()</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add proper dependencies for arguments of sequence functions (Tom)
-     </para>
-     <para>
-      In previous releases, sequence names passed to <function>nextval()</>,
-      <function>currval()</>, and <function>setval()</> were stored as
-      simple text strings, meaning that renaming or dropping a
-      sequence used in a <literal>DEFAULT</> clause made the clause
-      invalid. This release stores all newly-created sequence function
-      arguments as internal OIDs, allowing them to track sequence
-      renaming, and adding dependency information that prevents
-      improper sequence removal. It also makes such <literal>DEFAULT</>
-      clauses immune to schema renaming and search path changes.
-     </para>
-     <para>
-      Some applications might rely on the old behavior of
-      run-time lookup for sequence names. This can still be done by
-      explicitly casting the argument to <type>text</>, for example
-      <literal>nextval('myseq'::text)</>.
-     </para>
-     <para>
-      Pre-8.1 database dumps loaded into 8.1 will use the old text-based
-      representation and therefore will not have the features of
-      OID-stored arguments. However, it is possible to update a
-      database containing text-based <literal>DEFAULT</> clauses.
-      First, save this query into a file, such as <filename>fixseq.sql</>:
-<programlisting>
-SELECT  'ALTER TABLE ' ||
-   pg_catalog.quote_ident(n.nspname) || '.' ||
-   pg_catalog.quote_ident(c.relname) ||
-   ' ALTER COLUMN ' || pg_catalog.quote_ident(a.attname) ||
-   ' SET DEFAULT ' ||
-   regexp_replace(d.adsrc,
-                  $$val\(\(('[^']*')::text\)::regclass$$,
-                  $$val(\1$$,
-                  'g') ||
-   ';'
-FROM    pg_namespace n, pg_class c, pg_attribute a, pg_attrdef d
-WHERE   n.oid = c.relnamespace AND
-   c.oid = a.attrelid AND
-   a.attrelid = d.adrelid AND
-   a.attnum = d.adnum AND
-   d.adsrc ~ $$val\(\('[^']*'::text\)::regclass$$;
-</programlisting>
-      Next, run the query against a database to find what
-      adjustments are required, like this for database <literal>db1</>:
-<programlisting>
-psql -t -f fixseq.sql db1
-</programlisting>
-      This will show the <command>ALTER TABLE</> commands needed to
-      convert the database to the newer OID-based representation.
-      If the commands look reasonable, run this to update the database:
-<programlisting>
-psql -t -f fixseq.sql db1 | psql -e db1
-</programlisting>
-      This process must be repeated in each database to be updated.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In <application>psql</application>, treat unquoted
-      <literal>\{digit}+</> sequences as octal (Bruce)
-     </para>
-     <para>
-      In previous releases, <literal>\{digit}+</> sequences were
-      treated as decimal, and only <literal>\0{digit}+</> were treated
-      as octal. This change was made for consistency.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Remove grammar productions for prefix and postfix <literal>%</>
-      and <literal>^</> operators
-      (Tom)
-     </para>
-     <para>
-      These have never been documented and complicated the use of the
-      modulus operator (<literal>%</>) with negative numbers.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <literal>&amp;&lt;</> and <literal>&amp;&gt;</> for polygons
-      consistent with the box "over" operators (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <command>CREATE LANGUAGE</> can ignore the provided arguments
-      in favor of information from <structname>pg_pltemplate</>
-      (Tom)
-     </para>
-     <para>
-      A new system catalog <structname>pg_pltemplate</> has been defined
-      to carry information about the preferred definitions of procedural
-      languages (such as whether they have validator functions).  When
-      an entry exists in this catalog for the language being created,
-      <command>CREATE LANGUAGE</> will ignore all its parameters except the
-      language name and instead use the catalog information.  This measure
-      was taken because of increasing problems with obsolete language
-      definitions being loaded by old dump files.  As of 8.1,
-      <application>pg_dump</> will dump procedural language definitions as
-      just <command>CREATE LANGUAGE <replaceable>name</></command>, relying
-      on a template entry to exist at load time.  We expect this will be a
-      more future-proof representation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>pg_cancel_backend(int)</function> return a
-      <type>boolean</type> rather than an <type>integer</type> (Neil)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Some users are having problems loading UTF-8 data into 8.1.X.
-      This is because previous versions allowed invalid UTF-8 byte
-      sequences to be entered into the database, and this release
-      properly accepts only valid UTF-8 sequences. One way to correct a
-      dumpfile is to run the command <command>iconv -c -f UTF-8 -t
-      UTF-8 -o cleanfile.sql dumpfile.sql</>. The <literal>-c</> option
-      removes invalid character sequences. A diff of the two files will
-      show the sequences that are invalid. <command>iconv</> reads the
-      entire input file into memory so it might be necessary to use
-      <application>split</> to break up the dump into multiple smaller
-      files for processing.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-  </sect2>
-
-  <sect2>
-   <title>Additional Changes</title>
-
-   <para>
-    Below you will find a detailed account of the additional changes
-    between <productname>PostgreSQL</productname> 8.1 and the
-    previous major release.
-   </para>
-
-   <sect3>
-    <title>Performance Improvements</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Improve GiST and R-tree index performance (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve the optimizer, including auto-resizing of hash joins
-       (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Overhaul internal API in several areas
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change WAL record CRCs from 64-bit to 32-bit (Tom)
-      </para>
-      <para>
-       We determined that the extra cost of computing 64-bit CRCs was
-       significant, and the gain in reliability too marginal to justify it.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Prevent writing large empty gaps in WAL pages (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve spinlock behavior on SMP machines, particularly Opterons (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow nonconsecutive index columns to be used in a multicolumn
-       index (Tom)
-      </para>
-      <para>
-       For example, this allows an index on columns a,b,c to be used in
-       a query with <command>WHERE a = 4 and c = 10</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Skip WAL logging for <command>CREATE TABLE AS</> /
-       <command>SELECT INTO</> (Simon)
-      </para>
-      <para>
-       Since a crash during <command>CREATE TABLE AS</> would cause the
-       table to be dropped during recovery, there is no reason to WAL
-       log as the table is loaded.  (Logging still happens if WAL
-       archiving is enabled, however.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow concurrent GiST index access (Teodor, Oleg)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add configuration parameter <varname>full_page_writes</> to
-       control writing full pages to WAL (Bruce)
-      </para>
-      <para>
-       To prevent partial disk writes from corrupting the database,
-       <productname>PostgreSQL</productname> writes a complete copy of
-       each database disk page to WAL the first time it is modified
-       after a checkpoint. This option turns off that functionality for more
-       speed.  This is safe to use with battery-backed disk caches where
-       partial page writes cannot happen.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use <literal>O_DIRECT</> if available when using
-       <literal>O_SYNC</> for <varname>wal_sync_method</varname>
-       (Itagaki Takahiro)
-      </para>
-      <para>
-       <literal>O_DIRECT</> causes disk writes to bypass the kernel
-       cache, and for WAL writes, this improves performance.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <command>COPY FROM</> performance (Alon Goldshuv)
-      </para>
-      <para>
-       This was accomplished by reading <command>COPY</> input in
-       larger chunks, rather than character by character.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve the performance of <function>COUNT()</function>,
-       <function>SUM</function>, <function>AVG()</function>,
-       <function>STDDEV()</function>, and
-       <function>VARIANCE()</function> (Neil, Tom)
-      </para>
-     </listitem>
-    </itemizedlist>
-   </sect3>
-
-   <sect3>
-    <title>Server Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Prevent problems due to transaction ID (XID) wraparound (Tom)
-      </para>
-      <para>
-       The server will now warn when the transaction counter approaches
-       the wraparound point.  If the counter becomes too close to wraparound,
-       the server will stop accepting queries.  This ensures that data is
-       not lost before needed vacuuming is performed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix problems with object IDs (OIDs) conflicting with existing system
-       objects after the OID counter has wrapped around (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add warning about the need to increase
-       <varname>max_fsm_relations</> and <varname>max_fsm_pages</>
-       during <command>VACUUM</> (Ron Mayer)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <varname>temp_buffers</> configuration parameter to allow
-       users to determine the size of the local buffer area for
-       temporary table access (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add session start time and client IP address to
-       <literal>pg_stat_activity</> (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Adjust <literal>pg_stat</> views for bitmap scans (Tom)
-      </para>
-      <para>
-       The meanings of some of the fields have changed slightly.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Enhance <literal>pg_locks</> view (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Log queries for client-side <command>PREPARE</> and
-       <command>EXECUTE</> (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow Kerberos name and user name case sensitivity to be
-       specified in <filename>postgresql.conf</> (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add configuration parameter <varname>krb_server_hostname</> so
-       that the server host name can be specified as part of service
-       principal (Todd Kover)
-      </para>
-      <para>
-       If not set, any service principal matching an entry in the
-       keytab can be used. This is new Kerberos matching behavior in
-       this release.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <varname>log_line_prefix</> options for millisecond
-       timestamps (<literal>%m</>) and remote host (<literal>%h</>) (Ed
-       L.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add WAL logging for GiST indexes (Teodor, Oleg)
-      </para>
-      <para>
-       GiST indexes are now safe for crash and point-in-time recovery.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove old <filename>*.backup</> files when we do
-       <function>pg_stop_backup()</> (Bruce)
-      </para>
-      <para>
-       This prevents a large number of <filename>*.backup</> files from
-       existing in <filename>pg_xlog/</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add configuration parameters to control TCP/IP keep-alive
-       times for idle, interval, and count (Oliver Jowett)
-      </para>
-
-      <para>
-       These values can be changed to allow more rapid detection of
-       lost client connections.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add per-user and per-database connection limits (Petr Jelinek)
-      </para>
-      <para>
-       Using <command>ALTER USER</> and <command>ALTER DATABASE</>,
-       limits can now be enforced on the maximum number of sessions that
-       can concurrently connect as a specific user or to a specific database.
-       Setting the limit to zero disables user or database connections.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow more than two gigabytes of shared memory and per-backend
-       work memory on 64-bit machines (Koichi Suzuki)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New system catalog <structname>pg_pltemplate</> allows overriding
-       obsolete procedural-language definitions in dump files (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Query Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add temporary views (Koju Iijima, Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <command>HAVING</> without any aggregate functions or
-       <command>GROUP BY</> so that the query returns a single group (Tom)
-      </para>
-      <para>
-       Previously, such a case would treat the <command>HAVING</>
-       clause the same as a <command>WHERE</> clause.  This was not per spec.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>USING</> clause to allow additional tables to be
-       specified to <command>DELETE</> (Euler Taveira de Oliveira, Neil)
-      </para>
-      <para>
-       In prior releases, there was no clear method for specifying
-       additional tables to be used for joins in a <command>DELETE</>
-       statement. <command>UPDATE</> already has a <literal>FROM</>
-       clause for this purpose.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <literal>\x</> hex escapes in backend and ecpg
-       strings (Bruce)
-      </para>
-      <para>
-       This is just like the standard C <literal>\x</> escape syntax.
-       Octal escapes were already supported.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>BETWEEN SYMMETRIC</> query syntax (Pavel Stehule)
-      </para>
-      <para>
-       This feature allows <command>BETWEEN</> comparisons without
-       requiring the first value to be less than the second. For
-       example, <command>2 BETWEEN [ASYMMETRIC] 3 AND 1</> returns
-       false, while <command>2 BETWEEN SYMMETRIC 3 AND 1</> returns
-       true. <command>BETWEEN ASYMMETRIC</> was already supported.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>NOWAIT</> option to <command>SELECT ... FOR
-       UPDATE/SHARE</> (Hans-Juergen Schoenig)
-      </para>
-      <para>
-       While the <varname>statement_timeout</> configuration
-       parameter allows a query taking more than a certain amount of
-       time to be cancelled, the <command>NOWAIT</> option allows a
-       query to be canceled as soon as a <command>SELECT ... FOR
-       UPDATE/SHARE</> command cannot immediately acquire a row lock.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Object Manipulation Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Track dependencies of shared objects (Alvaro)
-      </para>
-      <para>
-       <productname>PostgreSQL</productname> allows global tables
-       (users, databases, tablespaces) to reference information in
-       multiple databases. This addition adds dependency information
-       for global tables, so, for example, user ownership can be
-       tracked across databases, so a user who owns something in any
-       database can no longer be removed. Dependency tracking already
-       existed for database-local objects.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow limited <command>ALTER OWNER</> commands to be performed
-       by the object owner (Stephen Frost)
-      </para>
-      <para>
-       Prior releases allowed only superusers to change object owners.
-       Now, ownership can be transferred if the user executing the command
-       owns the object and would be able to create it as the new owner
-       (that is, the user is a member of the new owning role and that role
-       has the CREATE permission that would be needed to create the object
-       afresh).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>ALTER</> object <command>SET SCHEMA</> capability
-       for some object types (tables, functions, types) (Bernd Helmle)
-      </para>
-      <para>
-       This allows objects to be moved to different schemas.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>ALTER TABLE ENABLE/DISABLE TRIGGER</command> to
-       disable triggers (Satoshi Nagayasu)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Utility Command Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow <command>TRUNCATE</> to truncate multiple tables in a
-       single command (Alvaro)
-      </para>
-      <para>
-       Because of referential integrity checks, it is not allowed to
-       truncate a table that is part of a referential integrity
-       constraint. Using this new functionality, <command>TRUNCATE</>
-       can be used to truncate such tables, if both tables involved in
-       a referential integrity constraint are truncated in a single
-       <command>TRUNCATE</> command.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Properly process carriage returns and line feeds in
-       <command>COPY CSV</> mode (Andrew)
-      </para>
-      <para>
-       In release 8.0, carriage returns and line feeds in <command>CSV
-       COPY TO</> were processed in an inconsistent manner. (This was
-       documented on the TODO list.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>COPY WITH CSV HEADER</> to allow a header line as
-       the first line in <command>COPY</> (Andrew)
-      </para>
-      <para>
-       This allows handling of the common <command>CSV</> usage of
-       placing the column names on the first line of the data file. For
-       <command>COPY TO</>, the first line contains the column names,
-       and for <command>COPY FROM</>, the first line is ignored.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       On Windows, display better sub-second precision in
-       <command>EXPLAIN ANALYZE</> (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add trigger duration display to <command>EXPLAIN ANALYZE</>
-       (Tom)
-      </para>
-      <para>
-       Prior releases included trigger execution time as part of the
-       total execution time, but did not show it separately.  It is now
-       possible to see how much time is spent in each trigger.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <literal>\x</> hex escapes in <command>COPY</>
-       (Sergey Ten)
-      </para>
-      <para>
-       Previous releases only supported octal escapes.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <command>SHOW ALL</> include variable descriptions
-       (Matthias Schmidt)
-      </para>
-      <para>
-       <command>SHOW</> varname still only displays the variable's
-       value and does not include the description.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <application>initdb</application> create a new standard
-       database called <literal>postgres</>, and convert utilities to
-       use <literal>postgres</> rather than <literal>template1</> for
-       standard lookups (Dave)
-      </para>
-      <para>
-       In prior releases, <literal>template1</> was used both as a
-       default connection for utilities like
-       <application>createuser</application>, and as a template for
-       new databases. This caused <command>CREATE DATABASE</> to
-       sometimes fail, because a new database cannot be created if
-       anyone else is in the template database. With this change, the
-       default connection database is now <literal>postgres</>,
-       meaning it is much less likely someone will be using
-       <literal>template1</> during <command>CREATE DATABASE</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Create new <application>reindexdb</application> command-line
-       utility by moving <filename>/contrib/reindexdb</> into the
-       server (Euler Taveira de Oliveira)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Data Type and Function Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <function>MAX()</> and <function>MIN()</> aggregates for
-       array types (Koju Iijima)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <function>to_date()</> and <function>to_timestamp()</> to
-       behave reasonably when <literal>CC</> and <literal>YY</> fields
-       are both used (Karel Zak)
-      </para>
-      <para>
-       If the format specification contains <literal>CC</> and a year
-       specification is <literal>YYY</> or longer, ignore the
-       <literal>CC</>. If the year specification is <literal>YY</> or
-       shorter, interpret <literal>CC</> as the previous century.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>md5(bytea)</> (Abhijit Menon-Sen)
-      </para>
-      <para>
-       <function>md5(text)</> already existed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <command>numeric ^ numeric</> based on
-       <function>power(numeric, numeric)</>
-      </para>
-      <para>
-       The function already existed, but there was no operator assigned
-       to it.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <type>NUMERIC</> modulus by properly truncating the quotient
-       during computation (Bruce)
-      </para>
-      <para>
-       In previous releases, modulus for large values sometimes
-       returned negative results due to rounding of the quotient.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a function <function>lastval()</> (Dennis Bj&ouml;rklund)
-      </para>
-      <para>
-       <function>lastval()</> is a simplified version of
-       <function>currval()</>. It automatically determines the proper
-       sequence name based on the most recent <function>nextval()</> or
-       <function>setval()</> call performed by the current session.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>to_timestamp(DOUBLE PRECISION) (Michael Glaesemann)</>
-      </para>
-      <para>
-       Converts Unix seconds since 1970 to a <type>TIMESTAMP WITH
-       TIMEZONE</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>pg_postmaster_start_time()</> function (Euler
-       Taveira de Oliveira, Matthias Schmidt)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow the full use of time zone names in <command>AT TIME
-       ZONE</>, not just the short list previously available (Magnus)
-      </para>
-      <para>
-       Previously, only a predefined list of time zone names were
-       supported by <command>AT TIME ZONE</>. Now any supported time
-       zone name can be used, e.g.:
-<programlisting>
-SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London';
-</programlisting>
-       In the above query, the time zone used is adjusted based on the
-       daylight saving time rules that were in effect on the supplied
-       date.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>GREATEST()</> and <function>LEAST()</> variadic
-       functions (Pavel Stehule)
-      </para>
-      <para>
-       These functions take a variable number of arguments and return
-       the greatest or least value among the arguments.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>pg_column_size()</> (Mark Kirkwood)
-      </para>
-      <para>
-       This returns storage size of a column, which might be compressed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>regexp_replace()</> (Atsushi Ogawa)
-      </para>
-      <para>
-       This allows regular expression replacement, like sed. An optional
-       flag argument allows selection of global (replace all) and
-       case-insensitive modes.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix interval division and multiplication (Bruce)
-      </para>
-      <para>
-       Previous versions sometimes returned unjustified results, like
-       <command>'4 months'::interval / 5</> returning <command>'1 mon
-       -6 days'</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix roundoff behavior in timestamp, time, and interval output (Tom)
-      </para>
-      <para>
-       This fixes some cases in which the seconds field would be shown as
-       <literal>60</> instead of incrementing the higher-order fields.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a separate day field to type <type>interval</> so a one day
-       interval can be distinguished from a 24 hour interval (Michael
-       Glaesemann)
-      </para>
-      <para>
-       Days that contain a daylight saving time adjustment are not 24
-       hours long, but typically 23 or 25 hours.  This change creates a
-       conceptual distinction between intervals of <quote>so many days</>
-       and intervals of <quote>so many hours</>.  Adding
-       <literal>1 day</> to a timestamp now gives the same local time on
-       the next day even if a daylight saving time adjustment occurs
-       between, whereas adding <literal>24 hours</> will give a different
-       local time when this happens.  For example, under US DST rules:
-<programlisting>
-'2005-04-03 00:00:00-05' + '1 day' = '2005-04-04 00:00:00-04'
-'2005-04-03 00:00:00-05' + '24 hours' = '2005-04-04 01:00:00-04'
-</programlisting>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>justify_days()</> and <function>justify_hours()</>
-       (Michael Glaesemann)
-      </para>
-      <para>
-       These functions, respectively, adjust days to an appropriate
-       number of full months and days, and adjust hours to an
-       appropriate number of full days and hours.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Move <filename>/contrib/dbsize</> into the backend, and rename
-       some of the functions (Dave Page, Andreas Pflug)
-      </para>
-      <para>
-       <itemizedlist>
-
-        <listitem>
-         <para>
-           <function>pg_tablespace_size()</>
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-          <function>pg_database_size()</>
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-          <function>pg_relation_size()</>
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-          <function>pg_total_relation_size()</>
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-          <function>pg_size_pretty()</>
-         </para>
-        </listitem>
-
-       </itemizedlist>
-      </para>
-      <para>
-       <function>pg_total_relation_size()</> includes indexes and TOAST
-       tables.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add functions for read-only file access to the cluster directory
-       (Dave Page, Andreas Pflug)
-      </para>
-      <para>
-       <itemizedlist>
-
-        <listitem>
-         <para>
-          <function>pg_stat_file()</>
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-          <function>pg_read_file()</>
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-          <function>pg_ls_dir()</>
-         </para>
-        </listitem>
-
-       </itemizedlist>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>pg_reload_conf()</> to force reloading of the
-       configuration files (Dave Page, Andreas Pflug)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>pg_rotate_logfile()</> to force rotation of the
-       server log file (Dave Page, Andreas Pflug)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change <literal>pg_stat_*</> views to include TOAST tables (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Encoding and Locale Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Rename some encodings to be more consistent and to follow
-       international standards (Bruce)
-      </para>
-      <para>
-       <itemizedlist>
-
-        <listitem>
-         <para>
-          <literal>UNICODE</> is now <literal>UTF8</>
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-          <literal>ALT</> is now <literal>WIN866</>
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-          <literal>WIN</> is now <literal>WIN1251</>
-         </para>
-        </listitem>
-
-        <listitem>
-         <para>
-         <literal>TCVN</> is now <literal>WIN1258</>
-         </para>
-        </listitem>
-
-       </itemizedlist>
-      </para>
-
-      <para>
-       The original names still work.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <literal>WIN1252</> encoding (Roland Volkmann)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for four-byte <literal>UTF8</> characters (John
-       Hansen)
-      </para>
-      <para>
-       Previously only one, two, and three-byte <literal>UTF8</> characters
-       were supported. This is particularly important for support for
-       some Chinese character sets.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow direct conversion between <literal>EUC_JP</> and
-       <literal>SJIS</> to improve performance (Atsushi Ogawa)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow the UTF8 encoding to work on Windows (Magnus)
-      </para>
-      <para>
-       This is done by mapping UTF8 to the Windows-native UTF16
-       implementation.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>General Server-Side Language Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Fix <command>ALTER LANGUAGE RENAME</> (Sergey Yatskevich)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow function characteristics, like strictness and volatility,
-       to be modified via <command>ALTER FUNCTION</> (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Increase the maximum number of function arguments to 100 (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow SQL and PL/pgSQL functions to use <command>OUT</> and
-       <command>INOUT</> parameters (Tom)
-      </para>
-      <para>
-       <command>OUT</> is an alternate way for a function to return
-       values. Instead of using <command>RETURN</>, values can be
-       returned by assigning to parameters declared as <command>OUT</> or
-       <command>INOUT</>.  This is notationally simpler in some cases,
-       particularly so when multiple values need to be returned.
-       While returning multiple values from a function
-       was possible in previous releases, this greatly simplifies the
-       process.  (The feature will be extended to other server-side
-       languages in future releases.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Move language handler functions into the <literal>pg_catalog</> schema
-      </para>
-      <para>
-       This makes it easier to drop the public schema if desired.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>SPI_getnspname()</function> to SPI (Neil)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-   <sect3>
-    <title>PL/pgSQL Server-Side Language Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Overhaul the memory management of PL/pgSQL functions (Neil)
-      </para>
-      <para>
-       The parsetree of each function is now stored in a separate
-       memory context. This allows this memory to be easily reclaimed
-       when it is no longer needed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Check function syntax at <command>CREATE FUNCTION</> time,
-       rather than at runtime (Neil)
-      </para>
-      <para>
-       Previously, most syntax errors were reported only when the
-       function was executed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>OPEN</> to open non-<command>SELECT</> queries
-       like <command>EXPLAIN</> and <command>SHOW</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       No longer require functions to issue a <command>RETURN</>
-       statement (Tom)
-      </para>
-      <para>
-       This is a byproduct of the newly added <command>OUT</> and
-       <command>INOUT</> functionality.  <command>RETURN</> can
-       be omitted when it is not needed to provide the function's
-       return value.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for an optional <command>INTO</> clause to
-       PL/pgSQL's <command>EXECUTE</> statement (Pavel Stehule, Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <command>CREATE TABLE AS</> set <command>ROW_COUNT</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Define <literal>SQLSTATE</> and <literal>SQLERRM</> to return
-       the <literal>SQLSTATE</> and error message of the current
-       exception (Pavel Stehule, Neil)
-      </para>
-      <para>
-       These variables are only defined inside exception blocks.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow the parameters to the <command>RAISE</> statement to be
-       expressions (Pavel Stehule, Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a loop <command>CONTINUE</> statement (Pavel Stehule, Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow block and loop labels (Pavel Stehule)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>PL/Perl Server-Side Language Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow large result sets to be returned efficiently (Abhijit
-       Menon-Sen)
-      </para>
-      <para>
-       This allows functions to use <function>return_next()</> to avoid
-       building the entire result set in memory.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow one-row-at-a-time retrieval of query results (Abhijit Menon-Sen)
-      </para>
-      <para>
-       This allows functions to use <function>spi_query()</> and
-       <function>spi_fetchrow()</> to avoid accumulating the entire
-       result set in memory.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Force PL/Perl to handle strings as <literal>UTF8</> if the
-       server encoding is <literal>UTF8</> (David Kamholz)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a validator function for PL/Perl (Andrew)
-      </para>
-      <para>
-       This allows syntax errors to be reported at definition time,
-       rather than execution time.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow PL/Perl to return a Perl array when the function returns
-       an array type (Andrew)
-      </para>
-      <para>
-       This basically maps <productname>PostgreSQL</productname> arrays
-       to Perl arrays.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow Perl nonfatal warnings to generate <command>NOTICE</>
-       messages (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow Perl's <literal>strict</> mode to be enabled (Andrew)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title><application>psql</> Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <command>\set ON_ERROR_ROLLBACK</> to allow statements in
-       a transaction to error without affecting the rest of the
-       transaction (Greg Sabino Mullane)
-      </para>
-      <para>
-       This is basically implemented by wrapping every statement in a
-       sub-transaction.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <literal>\x</> hex strings in
-       <application>psql</> variables (Bruce)
-      </para>
-      <para>
-       Octal escapes were already supported.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <command>troff -ms</> output format (Roger
-       Leigh)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow the history file location to be controlled by
-       <envar>HISTFILE</> (Andreas Seltenreich)
-      </para>
-      <para>
-       This allows configuration of per-database history storage.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Prevent <command>\x</> (expanded mode) from affecting
-       the output of <command>\d tablename</> (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>-L</> option to <application>psql</application> to
-       log sessions (Lorne Sunley)
-      </para>
-      <para>
-       This option was added because some operating systems do not have
-       simple command-line activity logging functionality.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <command>\d</> show the tablespaces of indexes (Qingqing
-       Zhou)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>psql</application> help (<command>\h</>) to
-       make a best guess on the proper help information (Greg Sabino
-       Mullane)
-      </para>
-      <para>
-       This allows the user to just add <command>\h</> to the front of
-       the syntax error query and get help on the supported syntax.
-       Previously any additional query text beyond the command name
-       had to be removed to use <command>\h</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>\pset numericlocale</> to allow numbers to be
-       output in a locale-aware format (Eugen Nedelcu)
-      </para>
-      <para>
-       For example, using <literal>C</> locale <literal>100000</> would
-       be output as <literal>100,000.0</> while a European locale might
-       output this value as <literal>100.000,0</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make startup banner show both server version number and
-       <application>psql</>'s version number, when they are different (Bruce)
-      </para>
-      <para>
-       Also, a warning will be shown if the server and <application>psql</>
-       are from different major releases.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title><application>pg_dump</> Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <option>-n</> / <option>--schema</> switch to
-       <application>pg_restore</> (Richard van den Berg)
-      </para>
-      <para>
-       This allows just the objects in a specified schema to be restored.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>pg_dump</> to dump large objects even in
-       text mode (Tom)
-      </para>
-      <para>
-       With this change, large objects are now always dumped; the former
-       <option>-b</> switch is a no-op.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>pg_dump</> to dump a consistent snapshot of
-       large objects (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Dump comments for large objects (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <option>--encoding</> to <application>pg_dump</>
-       (Magnus Hagander)
-      </para>
-      <para>
-       This allows a database to be dumped in an encoding that is
-       different from the server's encoding. This is valuable when
-       transferring the dump to a machine with a different encoding.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Rely on <structname>pg_pltemplate</> for procedural languages (Tom)
-      </para>
-      <para>
-       If the call handler for a procedural language is in the
-       <literal>pg_catalog</> schema, <application>pg_dump</> does not
-       dump the handler.  Instead, it dumps the language using just
-       <command>CREATE LANGUAGE <replaceable>name</></command>,
-       relying on the <structname>pg_pltemplate</> catalog to provide
-       the language's creation parameters at load time.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title><application>libpq</application> Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add a <envar>PGPASSFILE</> environment variable to specify the
-       password file's filename (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>lo_create()</>, that is similar to
-       <function>lo_creat()</> but allows the OID of the large object
-       to be specified (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <application>libpq</application> consistently return an error
-       to the client application on <function>malloc()</function>
-       failure (Neil)
-      </para>
-     </listitem>
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Source Code Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Fix <application>pgxs</> to support building against a relocated
-       installation
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add spinlock support for the Itanium processor using Intel
-       compiler (Vikram Kalsi)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add Kerberos 5 support for Windows (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add Chinese FAQ ([email protected])
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Rename Rendezvous to Bonjour to match OS/X feature renaming
-       (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <literal>fsync_writethrough</literal> on
-       Darwin (Chris Campbell)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Streamline the passing of information within the server, the
-       optimizer, and the lock system (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>pg_config</> to be compiled using MSVC (Andrew)
-      </para>
-      <para>
-       This is required to build DBD::Pg using <application>MSVC</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove support for Kerberos V4 (Magnus)
-      </para>
-      <para>
-       Kerberos 4 had security vulnerabilities and is no longer
-       maintained.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Code cleanups (Coverity static analysis performed by
-       EnterpriseDB)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Modify <filename>postgresql.conf</> to use documentation defaults
-       <literal>on</>/<literal>off</> rather than
-       <literal>true</>/<literal>false</> (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Enhance <application>pg_config</> to be able to report more
-       build-time values (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>libpq</application> to be built thread-safe
-       on Windows (Dave Page)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow IPv6 connections to be used on Windows (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add Server Administration documentation about I/O subsystem
-       reliability (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Move private declarations from <filename>gist.h</filename> to
-       <filename>gist_private.h</filename> (Neil)
-      </para>
-
-      <para>
-       In previous releases, <filename>gist.h</> contained both the
-       public GiST API (intended for use by authors of GiST index
-       implementations) as well as some private declarations used by
-       the implementation of GiST itself. The latter have been moved
-       to a separate file, <filename>gist_private.h</>. Most GiST
-       index implementations should be unaffected.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Overhaul GiST memory management (Neil)
-      </para>
-
-      <para>
-       GiST methods are now always invoked in a short-lived memory
-       context. Therefore, memory allocated via <function>palloc()</>
-       will be reclaimed automatically, so GiST index implementations
-       do not need to manually release allocated memory via
-       <function>pfree()</>.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </sect3>
-
-
-   <sect3>
-    <title>Contrib Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <filename>/contrib/pg_buffercache</> contrib module (Mark
-       Kirkwood)
-      </para>
-      <para>
-       This displays the contents of the buffer cache, for debugging and
-       performance tuning purposes.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <filename>/contrib/array</> because it is obsolete (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Clean up the <filename>/contrib/lo</> module (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Move <filename>/contrib/findoidjoins</> to
-       <filename>/src/tools</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove the <literal>&lt;&lt;</>, <literal>&gt;&gt;</>,
-       <literal>&amp;&lt;</>, and <literal>&amp;&gt;</> operators from
-       <filename>/contrib/cube</>
-      </para>
-      <para>
-       These operators were not useful.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <filename>/contrib/btree_gist</> (Janko Richter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <filename>/contrib/pgbench</> (Tomoaki Sato, Tatsuo)
-      </para>
-      <para>
-       There is now a facility for testing with SQL command scripts given
-       by the user, instead of only a hard-wired command sequence.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <filename>/contrib/pgcrypto</> (Marko Kreen)
-      </para>
-
-      <itemizedlist>
-
-       <listitem>
-        <para>
-         Implementation of OpenPGP symmetric-key and public-key encryption
-        </para>
-        <para>
-         Both RSA and Elgamal public-key algorithms are supported.
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         Stand alone build: include SHA256/384/512 hashes, Fortuna PRNG
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         OpenSSL build: support 3DES, use internal AES with OpenSSL &lt; 0.9.7
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         Take build parameters (OpenSSL, zlib) from <filename>configure</> result
-        </para>
-        <para>
-         There is no need to edit the <filename>Makefile</> anymore.
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         Remove support for <filename>libmhash</> and <filename>libmcrypt</>
-        </para>
-       </listitem>
-
-      </itemizedlist>
-     </listitem>
-
-    </itemizedlist>
-   </sect3>
-
-  </sect2>
- </sect1>
diff --git a/doc-xc/src/sgml/release-8.2.sgmlin b/doc-xc/src/sgml/release-8.2.sgmlin
deleted file mode 100644
index 2dd49d6a06..0000000000
--- a/doc-xc/src/sgml/release-8.2.sgmlin
+++ /dev/null
@@ -1,6410 +0,0 @@
-<!-- doc/src/sgml/release-8.2.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-8-2-20">
-  <title>Release 8.2.20</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2011-01-31</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.19.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.20</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.14,
-    see the release notes for 8.2.14.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Avoid failures when <command>EXPLAIN</> tries to display a simple-form
-      <literal>CASE</> expression (Tom Lane)
-     </para>
-
-     <para>
-      If the <literal>CASE</>'s test expression was a constant, the planner
-      could simplify the <literal>CASE</> into a form that confused the
-      expression-display code, resulting in <quote>unexpected CASE WHEN
-      clause</> errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assignment to an array slice that is before the existing range
-      of subscripts (Tom Lane)
-     </para>
-
-     <para>
-      If there was a gap between the newly added subscripts and the first
-      pre-existing subscript, the code miscalculated how many entries needed
-      to be copied from the old array's null bitmap, potentially leading to
-      data corruption or crash.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unexpected conversion overflow in planner for very distant date
-      values (Tom Lane)
-     </para>
-
-     <para>
-      The <type>date</> type supports a wider range of dates than can be
-      represented by the <type>timestamp</> types, but the planner assumed it
-      could always convert a date to timestamp with impunity.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_restore</>'s text output for large objects (BLOBs)
-      when <varname>standard_conforming_strings</> is on (Tom Lane)
-     </para>
-
-     <para>
-      Although restoring directly to a database worked correctly, string
-      escaping was incorrect if <application>pg_restore</> was asked for
-      SQL text output and <varname>standard_conforming_strings</> had been
-      enabled in the source database.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix erroneous parsing of <type>tsquery</> values containing
-      <literal>... &amp; !(subexpression) | ...</literal> (Tom Lane)
-     </para>
-
-     <para>
-      Queries containing this combination of operators were not executed
-      correctly.  The same error existed in <filename>contrib/intarray</>'s
-      <type>query_int</> type and <filename>contrib/ltree</>'s
-      <type>ltxtquery</> type.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix buffer overrun in <filename>contrib/intarray</>'s input function
-      for the <type>query_int</> type (Apple)
-     </para>
-
-     <para>
-      This bug is a security risk since the function's return address could
-      be overwritten.  Thanks to Apple Inc's security team for reporting this
-      issue and supplying the fix.  (CVE-2010-4015)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in <filename>contrib/seg</>'s GiST picksplit algorithm
-      (Alexander Korotkov)
-     </para>
-
-     <para>
-      This could result in considerable inefficiency, though not actually
-      incorrect answers, in a GiST index on a <type>seg</> column.
-      If you have such an index, consider <command>REINDEX</>ing it after
-      installing this update.  (This is identical to the bug that was fixed in
-      <filename>contrib/cube</> in the previous update.)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-19">
-  <title>Release 8.2.19</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-12-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.18.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.19</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.14,
-    see the release notes for 8.2.14.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Force the default
-      <link linkend="guc-wal-sync-method"><varname>wal_sync_method</></link>
-      to be <literal>fdatasync</> on Linux (Tom Lane, Marti Raudsepp)
-     </para>
-
-     <para>
-      The default on Linux has actually been <literal>fdatasync</> for many
-      years, but recent kernel changes caused <productname>PostgreSQL</> to
-      choose <literal>open_datasync</> instead.  This choice did not result
-      in any performance improvement, and caused outright failures on
-      certain filesystems, notably <literal>ext4</> with the
-      <literal>data=journal</> mount option.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane)
-     </para>
-
-     <para>
-      This could result in <quote>bad buffer id: 0</> failures or
-      corruption of index contents during replication.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix recovery from base backup when the starting checkpoint WAL record
-      is not in the same WAL segment as its redo point (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add support for detecting register-stack overrun on <literal>IA64</>
-      (Tom Lane)
-     </para>
-
-     <para>
-      The <literal>IA64</> architecture has two hardware stacks.  Full
-      prevention of stack-overrun failures requires checking both.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add a check for stack overflow in <function>copyObject()</> (Tom Lane)
-     </para>
-
-     <para>
-      Certain code paths could crash due to stack overflow given a
-      sufficiently complex query.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix detection of page splits in temporary GiST indexes (Heikki
-      Linnakangas)
-     </para>
-
-     <para>
-      It is possible to have a <quote>concurrent</> page split in a
-      temporary index, if for example there is an open cursor scanning the
-      index when an insertion is done.  GiST failed to detect this case and
-      hence could deliver wrong results when execution of the cursor
-      continued.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid memory leakage while <command>ANALYZE</>'ing complex index
-      expressions (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure an index that uses a whole-row Var still depends on its table
-      (Tom Lane)
-     </para>
-
-     <para>
-      An index declared like <literal>create index i on t (foo(t.*))</>
-      would not automatically get dropped when its table was dropped.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not <quote>inline</> a SQL function with multiple <literal>OUT</>
-      parameters (Tom Lane)
-     </para>
-
-     <para>
-      This avoids a possible crash due to loss of information about the
-      expected result rowtype.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Behave correctly if <literal>ORDER BY</>, <literal>LIMIT</>,
-      <literal>FOR UPDATE</>, or <literal>WITH</> is attached to the
-      <literal>VALUES</> part of <literal>INSERT ... VALUES</> (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix constant-folding of <literal>COALESCE()</> expressions (Tom Lane)
-     </para>
-
-     <para>
-      The planner would sometimes attempt to evaluate sub-expressions that
-      in fact could never be reached, possibly leading to unexpected errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add print functionality for <structname>InhRelation</> nodes (Tom Lane)
-     </para>
-
-     <para>
-      This avoids a failure when <varname>debug_print_parse</> is enabled
-      and certain types of query are executed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect calculation of distance from a point to a horizontal
-      line segment (Tom Lane)
-     </para>
-
-     <para>
-      This bug affected several different geometric distance-measurement
-      operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/pgSQL</>'s handling of <quote>simple</>
-      expressions to not fail in recursion or error-recovery cases (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/Python</>'s handling of set-returning functions
-      (Jan Urbanski)
-     </para>
-
-     <para>
-      Attempts to call SPI functions within the iterator generating a set
-      result would fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in <filename>contrib/cube</>'s GiST picksplit algorithm
-      (Alexander Korotkov)
-     </para>
-
-     <para>
-      This could result in considerable inefficiency, though not actually
-      incorrect answers, in a GiST index on a <type>cube</> column.
-      If you have such an index, consider <command>REINDEX</>ing it after
-      installing this update.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Don't emit <quote>identifier will be truncated</> notices in
-      <filename>contrib/dblink</> except when creating new connections
-      (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential coredump on missing public key in
-      <filename>contrib/pgcrypto</> (Marti Raudsepp)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak in <filename>contrib/xml2</>'s XPath query functions
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010o
-      for DST law changes in Fiji and Samoa;
-      also historical corrections for Hong Kong.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-18">
-  <title>Release 8.2.18</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-10-04</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.17.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.18</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.14,
-    see the release notes for 8.2.14.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Use a separate interpreter for each calling SQL userid in PL/Perl and
-      PL/Tcl (Tom Lane)
-     </para>
-
-     <para>
-      This change prevents security problems that can be caused by subverting
-      Perl or Tcl code that will be executed later in the same session under
-      another SQL user identity (for example, within a <literal>SECURITY
-      DEFINER</> function).  Most scripting languages offer numerous ways that
-      that might be done, such as redefining standard functions or operators
-      called by the target function.  Without this change, any SQL user with
-      Perl or Tcl language usage rights can do essentially anything with the
-      SQL privileges of the target function's owner.
-     </para>
-
-     <para>
-      The cost of this change is that intentional communication among Perl
-      and Tcl functions becomes more difficult.  To provide an escape hatch,
-      PL/PerlU and PL/TclU functions continue to use only one interpreter
-      per session.  This is not considered a security issue since all such
-      functions execute at the trust level of a database superuser already.
-     </para>
-
-     <para>
-      It is likely that third-party procedural languages that claim to offer
-      trusted execution have similar security issues.  We advise contacting
-      the authors of any PL you are depending on for security-critical
-      purposes.
-     </para>
-
-     <para>
-      Our thanks to Tim Bunce for pointing out this issue (CVE-2010-3433).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible crashes in <function>pg_get_expr()</> by disallowing
-      it from being called with an argument that is not one of the system
-      catalog columns it's intended to be used with
-      (Heikki Linnakangas, Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix Windows shared-memory allocation code
-      (Tsutomu Yamada, Magnus Hagander)
-     </para>
-
-     <para>
-      This bug led to the often-reported <quote>could not reattach to shared
-      memory</quote> error message.  This is a back-patch of a fix that was
-      applied to newer branches some time ago.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Treat exit code 128 (<literal>ERROR_WAIT_NO_CHILDREN</>) as non-fatal on
-      Windows (Magnus Hagander)
-     </para>
-
-     <para>
-      Under high load, Windows processes will sometimes fail at startup with
-      this error code.  Formerly the postmaster treated this as a panic
-      condition and restarted the whole database, but that seems to be
-      an overreaction.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible duplicate scans of <literal>UNION ALL</> member relations
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>cannot handle unplanned sub-select</quote> error (Tom Lane)
-     </para>
-
-     <para>
-      This occurred when a sub-select contains a join alias reference that
-      expands into an expression containing another sub-select.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Reduce PANIC to ERROR in some occasionally-reported btree failure cases,
-      and provide additional detail in the resulting error messages
-      (Tom Lane)
-     </para>
-
-     <para>
-      This should improve the system's robustness with corrupted indexes.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent show_session_authorization() from crashing within autovacuum
-      processes (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Defend against functions returning setof record where not all the
-      returned rows are actually of the same rowtype (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible failure when hashing a pass-by-reference function result
-      (Tao Ma, Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Take care to fsync the contents of lockfiles (both
-      <filename>postmaster.pid</> and the socket lockfile) while writing them
-      (Tom Lane)
-     </para>
-
-     <para>
-      This omission could result in corrupted lockfile contents if the
-      machine crashes shortly after postmaster start.  That could in turn
-      prevent subsequent attempts to start the postmaster from succeeding,
-      until the lockfile is manually removed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid recursion while assigning XIDs to heavily-nested
-      subtransactions (Andres Freund, Robert Haas)
-     </para>
-
-     <para>
-      The original coding could result in a crash if there was limited
-      stack space.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <varname>log_line_prefix</>'s <literal>%i</> escape,
-      which could produce junk early in backend startup (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible data corruption in <command>ALTER TABLE ... SET
-      TABLESPACE</> when archiving is enabled (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow <command>CREATE DATABASE</> and <command>ALTER DATABASE ... SET
-      TABLESPACE</> to be interrupted by query-cancel (Guillaume Lelarge)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In PL/Python, defend against null pointer results from
-      <function>PyCObject_AsVoidPtr</> and <function>PyCObject_FromVoidPtr</>
-      (Peter Eisentraut)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <filename>contrib/dblink</>'s handling of tables containing
-      dropped columns (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix connection leak after <quote>duplicate connection name</quote>
-      errors in <filename>contrib/dblink</> (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/dblink</> to handle connection names longer than
-      62 bytes correctly (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <function>hstore(text, text)</>
-      function to <filename>contrib/hstore</> (Robert Haas)
-     </para>
-
-     <para>
-      This function is the recommended substitute for the now-deprecated
-      <literal>=&gt;</> operator.  It was back-patched so that future-proofed
-      code can be used with older server versions.  Note that the patch will
-      be effective only after <filename>contrib/hstore</> is installed or
-      reinstalled in a particular database.  Users might prefer to execute
-      the <command>CREATE FUNCTION</> command by hand, instead.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update build infrastructure and documentation to reflect the source code
-      repository's move from CVS to Git (Magnus Hagander and others)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010l
-      for DST law changes in Egypt and Palestine; also historical corrections
-      for Finland.
-     </para>
-
-     <para>
-      This change also adds new names for two Micronesian timezones:
-      Pacific/Chuuk is now preferred over Pacific/Truk (and the preferred
-      abbreviation is CHUT not TRUT) and Pacific/Pohnpei is preferred over
-      Pacific/Ponape.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make Windows' <quote>N. Central Asia Standard Time</> timezone map to
-      Asia/Novosibirsk, not Asia/Almaty (Magnus Hagander)
-     </para>
-
-     <para>
-      Microsoft changed the DST behavior of this zone in the timezone update
-      from KB976098. Asia/Novosibirsk is a better match to its new behavior.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-17">
-  <title>Release 8.2.17</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-05-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.16.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.17</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.14,
-    see the release notes for 8.2.14.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Enforce restrictions in <literal>plperl</> using an opmask applied to
-      the whole interpreter, instead of using <filename>Safe.pm</>
-      (Tim Bunce, Andrew Dunstan)
-     </para>
-
-     <para>
-      Recent developments have convinced us that <filename>Safe.pm</> is too
-      insecure to rely on for making <literal>plperl</> trustable.  This
-      change removes use of <filename>Safe.pm</> altogether, in favor of using
-      a separate interpreter with an opcode mask that is always applied.
-      Pleasant side effects of the change include that it is now possible to
-      use Perl's <literal>strict</> pragma in a natural way in
-      <literal>plperl</>, and that Perl's <literal>$a</> and <literal>$b</>
-      variables work as expected in sort routines, and that function
-      compilation is significantly faster.  (CVE-2010-1169)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent PL/Tcl from executing untrustworthy code from
-      <structname>pltcl_modules</> (Tom)
-     </para>
-
-     <para>
-      PL/Tcl's feature for autoloading Tcl code from a database table
-      could be exploited for trojan-horse attacks, because there was no
-      restriction on who could create or insert into that table.  This change
-      disables the feature unless <structname>pltcl_modules</> is owned by a
-      superuser.  (However, the permissions on the table are not checked, so
-      installations that really need a less-than-secure modules table can
-      still grant suitable privileges to trusted non-superusers.)  Also,
-      prevent loading code into the unrestricted <quote>normal</> Tcl
-      interpreter unless we are really going to execute a <literal>pltclu</>
-      function.  (CVE-2010-1170)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash if a cache reset message is received during
-      rebuild of a relcache entry (Heikki)
-     </para>
-
-     <para>
-      This error was introduced in 8.2.16 while fixing a related failure.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not allow an unprivileged user to reset superuser-only parameter
-      settings (Alvaro)
-     </para>
-
-     <para>
-      Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
-      ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
-      a database he owns, this would remove all special parameter settings
-      for the user or database, even ones that are only supposed to be
-      changeable by a superuser.  Now, the <command>ALTER</> will only
-      remove the parameters that the user has permission to change.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crash during backend shutdown if shutdown occurs
-      when a <literal>CONTEXT</> addition would be made to log entries (Tom)
-     </para>
-
-     <para>
-      In some cases the context-printing function would fail because the
-      current transaction had already been rolled back when it came time
-      to print a log message.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update pl/perl's <filename>ppport.h</> for modern Perl versions
-      (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite recursion in <application>psql</> when expanding
-      a variable that refers to itself (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>psql</>'s <literal>\copy</> to not add spaces around
-      a dot within <literal>\copy (select ...)</> (Tom)
-     </para>
-
-     <para>
-      Addition of spaces around the decimal point in a numeric literal would
-      result in a syntax error.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
-      interrupts promptly (Tatsuhito Kasahara)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make server startup deal properly with the case that
-      <function>shmget()</> returns <literal>EINVAL</> for an existing
-      shared memory segment (Tom)
-     </para>
-
-     <para>
-      This behavior has been observed on BSD-derived kernels including OS X.
-      It resulted in an entirely-misleading startup failure complaining that
-      the shared memory request size was too large.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crashes in syslogger process on Windows (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Deal more robustly with incomplete time zone information in the
-      Windows registry (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update the set of known Windows time zone names (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010j
-      for DST law changes in Argentina, Australian Antarctic, Bangladesh,
-      Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia;
-      also historical corrections for Taiwan.
-     </para>
-
-     <para>
-      Also, add <literal>PKST</> (Pakistan Summer Time) to the default set of
-      timezone abbreviations.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-16">
-  <title>Release 8.2.16</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-03-15</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.15.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.16</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.14,
-    see the release notes for 8.2.14.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Add new configuration parameter <varname>ssl_renegotiation_limit</> to
-      control how often we do session key renegotiation for an SSL connection
-      (Magnus)
-     </para>
-
-     <para>
-      This can be set to zero to disable renegotiation completely, which may
-      be required if a broken SSL library is used.  In particular, some
-      vendors are shipping stopgap patches for CVE-2009-3555 that cause
-      renegotiation attempts to fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible deadlock during backend startup (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes due to not handling errors during relcache reload
-      cleanly (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes when trying to recover from a failure in
-      subtransaction start (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix server memory leak associated with use of savepoints and a client
-      encoding different from server's encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect WAL data emitted during end-of-recovery cleanup of a GIST
-      index page split (Yoichi Hirai)
-     </para>
-
-     <para>
-      This would result in index corruption, or even more likely an error
-      during WAL replay, if we were unlucky enough to crash during
-      end-of-recovery cleanup after having completed an incomplete GIST
-      insertion.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>substring()</> for <type>bit</> types treat any negative
-      length as meaning <quote>all the rest of the string</> (Tom)
-     </para>
-
-     <para>
-      The previous coding treated only -1 that way, and would produce an
-      invalid result value for other negative values, possibly leading to
-      a crash (CVE-2010-0442).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix integer-to-bit-string conversions to handle the first fractional
-      byte correctly when the output bit width is wider than the given
-      integer by something other than a multiple of 8 bits (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some cases of pathologically slow regular expression matching (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix the <literal>STOP WAL LOCATION</> entry in backup history files to
-      report the next WAL segment's name when the end location is exactly at a
-      segment boundary (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some more cases of temporary-file leakage (Heikki)
-     </para>
-
-     <para>
-      This corrects a problem introduced in the previous minor release.
-      One case that failed is when a plpgsql function returning set is
-      called within another function's exception handler.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve constraint exclusion processing of boolean-variable cases,
-      in particular make it possible to exclude a partition that has a
-      <quote>bool_column = false</> constraint (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      When reading <filename>pg_hba.conf</> and related files, do not treat
-      <literal>@something</> as a file inclusion request if the <literal>@</>
-      appears inside quote marks; also, never treat <literal>@</> by itself
-      as a file inclusion request (Tom)
-     </para>
-
-     <para>
-      This prevents erratic behavior if a role or database name starts with
-      <literal>@</>.  If you need to include a file whose path name
-      contains spaces, you can still do so, but you must write
-      <literal>@"/path to/file"</> rather than putting the quotes around
-      the whole construct.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite loop on some platforms if a directory is named as
-      an inclusion target in <filename>pg_hba.conf</> and related files
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible infinite loop if <function>SSL_read</> or
-      <function>SSL_write</> fails without setting <varname>errno</> (Tom)
-     </para>
-
-     <para>
-      This is reportedly possible with some Windows versions of
-      <application>openssl</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>psql</>'s <literal>numericlocale</> option to not
-      format strings it shouldn't in latex and troff output formats (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <application>psql</> return the correct exit status (3) when
-      <literal>ON_ERROR_STOP</> and <literal>--single-transaction</> are
-      both specified and an error occurs during the implied <command>COMMIT</>
-      (Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix plpgsql failure in one case where a composite column is set to NULL
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible failure when calling PL/Perl functions from PL/PerlU
-      or vice versa (Tim Bunce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>volatile</> markings in PL/Python to avoid possible
-      compiler-specific misbehavior (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
-     </para>
-
-     <para>
-      The only known symptom of this oversight is that the Tcl
-      <literal>clock</> command misbehaves if using Tcl 8.5 or later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent crash in <filename>contrib/dblink</> when too many key
-      columns are specified to a <function>dblink_build_sql_*</> function
-      (Rushabh Lathia, Joe Conway)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted crashes in <filename>contrib/xml2</> caused by sloppy
-      memory management (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make building of <filename>contrib/xml2</> more robust on Windows
-      (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix race condition in Windows signal handling (Radu Ilie)
-     </para>
-
-     <para>
-      One known symptom of this bug is that rows in <structname>pg_listener</>
-      could be dropped under heavy load.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010e
-      for DST law changes in Bangladesh, Chile, Fiji, Mexico, Paraguay, Samoa.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-15">
-  <title>Release 8.2.15</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2009-12-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.14.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.15</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.14,
-    see the release notes for 8.2.14.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Protect against indirect security threats caused by index functions
-      changing session-local state (Gurjeet Singh, Tom)
-     </para>
-
-     <para>
-      This change prevents allegedly-immutable index functions from possibly
-      subverting a superuser's session (CVE-2009-4136).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Reject SSL certificates containing an embedded null byte in the common
-      name (CN) field (Magnus)
-     </para>
-
-     <para>
-      This prevents unintended matching of a certificate to a server or client
-      name during SSL validation (CVE-2009-4034).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash during backend-startup-time cache initialization (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent signals from interrupting <literal>VACUUM</> at unsafe times
-      (Alvaro)
-     </para>
-
-     <para>
-      This fix prevents a PANIC if a <literal>VACUUM FULL</> is cancelled
-      after it's already committed its tuple movements, as well as transient
-      errors if a plain <literal>VACUUM</> is interrupted after having
-      truncated the table.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash due to integer overflow in hash table size
-      calculation (Tom)
-     </para>
-
-     <para>
-      This could occur with extremely large planner estimates for the size of
-      a hashjoin's result.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix very rare crash in <type>inet</>/<type>cidr</> comparisons (Chris
-      Mikkelson)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that shared tuple-level locks held by prepared transactions are
-      not ignored (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix premature drop of temporary files used for a cursor that is accessed
-      within a subtransaction (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect logic for GiST index page splits, when the split depends
-      on a non-first column of the index (Paul Ramsey)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Don't error out if recycling or removing an old WAL file fails at the
-      end of checkpoint (Heikki)
-     </para>
-
-     <para>
-      It's better to treat the problem as non-fatal and allow the checkpoint
-      to complete.  Future checkpoints will retry the removal.  Such problems
-      are not expected in normal operation, but have been seen to be
-      caused by misdesigned Windows anti-virus and backup software.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure WAL files aren't repeatedly archived on Windows (Heikki)
-     </para>
-
-     <para>
-      This is another symptom that could happen if some other process
-      interfered with deletion of a no-longer-needed file.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PAM password processing to be more robust (Tom)
-     </para>
-
-     <para>
-      The previous code is known to fail with the combination of the Linux
-      <literal>pam_krb5</> PAM module with Microsoft Active Directory as the
-      domain controller.  It might have problems elsewhere too, since it was
-      making unjustified assumptions about what arguments the PAM stack would
-      pass to it.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix processing of ownership dependencies during <literal>CREATE OR
-      REPLACE FUNCTION</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug with calling <literal>plperl</> from <literal>plperlu</> or vice
-      versa (Tom)
-     </para>
-
-     <para>
-      An error exit from the inner function could result in crashes due to
-      failure to re-select the correct Perl interpreter for the outer function.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix session-lifespan memory leak when a PL/Perl function is redefined
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that Perl arrays are properly converted to
-      <productname>PostgreSQL</> arrays when returned by a set-returning
-      PL/Perl function (Andrew Dunstan, Abhijit Menon-Sen)
-     </para>
-
-     <para>
-      This worked correctly already for non-set-returning functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix rare crash in exception processing in PL/Python (Peter)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <application>psql</>'s flex module is compiled with the correct
-      system header definitions (Tom)
-     </para>
-
-     <para>
-      This fixes build failures on platforms where
-      <literal>--enable-largefile</> causes incompatible changes in the
-      generated code.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make the postmaster ignore any <literal>application_name</> parameter in
-      connection request packets, to improve compatibility with future libpq
-      versions (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update the timezone abbreviation files to match current reality (Joachim
-      Wieland)
-     </para>
-
-     <para>
-      This includes adding <literal>IDT</> and <literal>SGT</> to the default
-      timezone abbreviation set.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009s
-      for DST law changes in Antarctica, Argentina, Bangladesh, Fiji,
-      Novokuznetsk, Pakistan, Palestine, Samoa, Syria; also historical
-      corrections for Hong Kong.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-14">
-  <title>Release 8.2.14</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2009-09-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.13.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.14</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you have any hash indexes on <type>interval</> columns,
-    you must <command>REINDEX</> them after updating to 8.2.14.
-    Also, if you are upgrading from a version earlier than 8.2.11,
-    see the release notes for 8.2.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Force WAL segment switch during <function>pg_start_backup()</>
-      (Heikki)
-     </para>
-
-     <para>
-      This avoids corner cases that could render a base backup unusable.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>RESET ROLE</> and <command>RESET SESSION
-      AUTHORIZATION</> inside security-definer functions (Tom, Heikki)
-     </para>
-
-     <para>
-      This covers a case that was missed in the previous patch that
-      disallowed <command>SET ROLE</> and <command>SET SESSION
-      AUTHORIZATION</> inside security-definer functions.
-      (See CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>LOAD</> of an already-loaded loadable module
-      into a no-op (Tom)
-     </para>
-
-     <para>
-      Formerly, <command>LOAD</> would attempt to unload and re-load the
-      module, but this is unsafe and not all that useful.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow empty passwords during LDAP authentication (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix handling of sub-SELECTs appearing in the arguments of
-      an outer-level aggregate function (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bugs associated with fetching a whole-row value from the
-      output of a Sort or Materialize plan node (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Revert planner change that disabled partial-index and constraint
-      exclusion optimizations when there were more than 100 clauses in
-      an AND or OR list (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix hash calculation for data type <type>interval</> (Tom)
-     </para>
-
-     <para>
-      This corrects wrong results for hash joins on interval values.
-      It also changes the contents of hash indexes on interval columns.
-      If you have any such indexes, you must <command>REINDEX</> them
-      after updating.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Treat <function>to_char(..., 'TH')</> as an uppercase ordinal
-      suffix with <literal>'HH'</>/<literal>'HH12'</> (Heikki)
-     </para>
-
-     <para>
-      It was previously handled as <literal>'th'</> (lowercase).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix overflow for <literal>INTERVAL '<replaceable>x</> ms'</literal>
-      when <replaceable>x</> is more than 2 million and integer
-      datetimes are in use (Alex Hunsaker)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix calculation of distance between a point and a line segment (Tom)
-     </para>
-
-     <para>
-      This led to incorrect results from a number of geometric operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <type>money</> data type to work in locales where currency
-      amounts have no fractional digits, e.g. Japan (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Properly round datetime input like
-      <literal>00:12:57.9999999999999999999999999999</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix poor choice of page split point in GiST R-tree operator classes
-      (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid performance degradation in bulk inserts into GIN indexes
-      when the input values are (nearly) in sorted order (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Correctly enforce NOT NULL domain constraints in some contexts in
-      PL/pgSQL (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix portability issues in plperl initialization (Andrew Dunstan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to not go into an infinite loop if
-      <filename>postgresql.conf</> is empty (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <filename>contrib/hstore</> throw an error when a key or
-      value is too long to fit in its data structure, rather than
-      silently truncating it (Andrew Gierth)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/xml2</>'s <function>xslt_process()</> to
-      properly handle the maximum number of parameters (twenty) (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve robustness of <application>libpq</>'s code to recover
-      from errors during <command>COPY FROM STDIN</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid including conflicting readline and editline header files
-      when both libraries are installed (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009l
-      for DST law changes in Bangladesh, Egypt, Jordan, Pakistan,
-      Argentina/San_Luis, Cuba, Jordan (historical correction only),
-      Mauritius, Morocco, Palestine, Syria, Tunisia.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-13">
-  <title>Release 8.2.13</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2009-03-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.12.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.13</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.11,
-    see the release notes for 8.2.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent error recursion crashes when encoding conversion fails (Tom)
-     </para>
-
-     <para>
-      This change extends fixes made in the last two minor releases for
-      related failure scenarios.  The previous fixes were narrowly tailored
-      for the original problem reports, but we have now recognized that
-      <emphasis>any</> error thrown by an encoding conversion function could
-      potentially lead to infinite recursion while trying to report the
-      error.  The solution therefore is to disable translation and encoding
-      conversion and report the plain-ASCII form of any error message,
-      if we find we have gotten into a recursive error reporting situation.
-      (CVE-2009-0922)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>CREATE CONVERSION</> with the wrong encodings
-      for the specified conversion function (Heikki)
-     </para>
-
-     <para>
-      This prevents one possible scenario for encoding conversion failure.
-      The previous change is a backstop to guard against other kinds of
-      failures in the same area.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix core dump when <function>to_char()</> is given format codes that
-      are inappropriate for the type of the data argument (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible failure in <filename>contrib/tsearch2</> when C locale is
-      used with a multi-byte encoding (Teodor)
-     </para>
-
-     <para>
-      Crashes were possible on platforms where <type>wchar_t</> is narrower
-      than <type>int</>; Windows in particular.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix extreme inefficiency in <filename>contrib/tsearch2</> parser's
-      handling of an email-like string containing multiple <literal>@</>
-      characters (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix decompilation of <literal>CASE WHEN</> with an implicit coercion
-      (Tom)
-     </para>
-
-     <para>
-      This mistake could lead to Assert failures in an Assert-enabled build,
-      or an <quote>unexpected CASE WHEN clause</> error message in other
-      cases, when trying to examine or dump a view.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible misassignment of the owner of a TOAST table's rowtype (Tom)
-     </para>
-
-     <para>
-      If <command>CLUSTER</> or a rewriting variant of <command>ALTER TABLE</>
-      were executed by someone other than the table owner, the
-      <structname>pg_type</> entry for the table's TOAST table would end up
-      marked as owned by that someone.  This caused no immediate problems,
-      since the permissions on the TOAST rowtype aren't examined by any
-      ordinary database operation.  However, it could lead to unexpected
-      failures if one later tried to drop the role that issued the command
-      (in 8.1 or 8.2), or <quote>owner of data type appears to be invalid</>
-      warnings from <application>pg_dump</> after having done so (in 8.3).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/pgSQL to not treat <literal>INTO</> after <command>INSERT</> as
-      an INTO-variables clause anywhere in the string, not only at the start;
-      in particular, don't fail for <command>INSERT INTO</> within
-      <command>CREATE RULE</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Clean up PL/pgSQL error status variables fully at block exit
-      (Ashesh Vashi and Dave Page)
-     </para>
-
-     <para>
-      This is not a problem for PL/pgSQL itself, but the omission could cause
-      the PL/pgSQL Debugger to crash while examining the state of a function.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Retry failed calls to <function>CallNamedPipe()</> on Windows
-      (Steve Marshall, Magnus)
-     </para>
-
-     <para>
-      It appears that this function can sometimes fail transiently;
-      we previously treated any failure as a hard error, which could
-      confuse <command>LISTEN</>/<command>NOTIFY</> as well as other
-      operations.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>MUST</> (Mauritius Island Summer Time) to the default list
-      of known timezone abbreviations (Xavier Bugaud)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-12">
-  <title>Release 8.2.12</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2009-02-02</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.11.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.12</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.11,
-    see the release notes for 8.2.11.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Improve handling of URLs in <function>headline()</> function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve handling of overlength headlines in <function>headline()</>
-      function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible Assert failure or misconversion if an encoding
-      conversion is created with the wrong conversion function for the
-      specified pair of encodings (Tom, Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible Assert failure if a statement executed in PL/pgSQL is
-      rewritten into another kind of statement, for example if an
-      <command>INSERT</> is rewritten into an <command>UPDATE</> (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that a snapshot is available to datatype input functions (Tom)
-     </para>
-
-     <para>
-      This primarily affects domains that are declared with <literal>CHECK</>
-      constraints involving user-defined stable or immutable functions.  Such
-      functions typically fail if no snapshot has been set.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make it safer for SPI-using functions to be used within datatype I/O;
-      in particular, to be used in domain check constraints (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unnecessary locking of small tables in <command>VACUUM</>
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a problem that made <literal>UPDATE RETURNING tableoid</>
-      return zero instead of the correct OID (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner misestimation of selectivity when transitive equality
-      is applied to an outer-join clause (Tom)
-     </para>
-
-     <para>
-      This could result in bad plans for queries like
-      <literal>... from a left join b on a.a1 = b.b1 where a.a1 = 42 ...</>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve optimizer's handling of long <literal>IN</> lists (Tom)
-     </para>
-
-     <para>
-      This change avoids wasting large amounts of time on such lists
-      when constraint exclusion is enabled.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that the contents of a holdable cursor don't depend on the
-      contents of TOAST tables (Tom)
-     </para>
-
-     <para>
-      Previously, large field values in a cursor result might be represented
-      as TOAST pointers, which would fail if the referenced table got dropped
-      before the cursor is read, or if the large value is deleted and then
-      vacuumed away.  This cannot happen with an ordinary cursor,
-      but it could with a cursor that is held past its creating transaction.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak when a set-returning function is terminated without
-      reading its whole result (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/dblink</>'s
-      <function>dblink_get_result(text,bool)</> function (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible garbage output from <filename>contrib/sslinfo</> functions
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>configure</> script to properly report failure when
-      unable to obtain linkage information for PL/Perl (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make all documentation reference <literal>pgsql-bugs</> and/or
-      <literal>pgsql-hackers</> as appropriate, instead of the
-      now-decommissioned <literal>pgsql-ports</> and <literal>pgsql-patches</>
-      mailing lists (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009a (for
-      Kathmandu and historical DST corrections in Switzerland, Cuba)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-11">
-  <title>Release 8.2.11</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2008-11-03</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.10.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.11</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.7,
-    see the release notes for 8.2.7.  Also, if you were running a previous
-    8.2.X release, it is recommended to <command>REINDEX</> all GiST
-    indexes after the upgrade.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix GiST index corruption due to marking the wrong index entry
-      <quote>dead</> after a deletion (Teodor)
-     </para>
-
-     <para>
-      This would result in index searches failing to find rows they
-      should have found.  Corrupted indexes can be fixed with
-      <command>REINDEX</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix backend crash when the client encoding cannot represent a localized
-      error message (Tom)
-     </para>
-
-     <para>
-      We have addressed similar issues before, but it would still fail if
-      the <quote>character has no equivalent</> message itself couldn't
-      be converted.  The fix is to disable localization and send the plain
-      ASCII error message when we detect such a situation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash when deeply nested functions are invoked from
-      a trigger (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve optimization of <replaceable>expression</> <literal>IN</>
-      (<replaceable>expression-list</>) queries (Tom, per an idea from Robert
-      Haas)
-     </para>
-
-     <para>
-      Cases in which there are query variables on the right-hand side had been
-      handled less efficiently in 8.2.x and 8.3.x than in prior versions.
-      The fix restores 8.1 behavior for such cases.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix mis-expansion of rule queries when a sub-<literal>SELECT</> appears
-      in a function call in <literal>FROM</>,  a multi-row <literal>VALUES</>
-      list, or a <literal>RETURNING</> list (Tom)
-     </para>
-
-     <para>
-      The usual symptom of this problem is an <quote>unrecognized node type</>
-      error.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak during rescan of a hashed aggregation plan (Neil)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure an error is reported when a newly-defined PL/pgSQL trigger
-      function is invoked as a normal function (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible collision of <structfield>relfilenode</> numbers
-      when moving a table to another tablespace with <command>ALTER SET
-      TABLESPACE</> (Heikki)
-     </para>
-
-     <para>
-      The command tried to re-use the existing filename, instead of
-      picking one that is known unused in the destination directory.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect tsearch2 headline generation when single query
-      item matches first word of text (Sushant Sinha)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix improper display of fractional seconds in interval values when
-      using a non-ISO datestyle in an <option>--enable-integer-datetimes</>
-      build (Ron Mayer)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <function>SPI_getvalue</> and <function>SPI_getbinval</>
-      behave correctly when the passed tuple and tuple descriptor have
-      different numbers of columns (Tom)
-     </para>
-
-     <para>
-      This situation is normal when a table has had columns added or removed,
-      but these two functions didn't handle it properly.
-      The only likely consequence is an incorrect error indication.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</>'s parsing of <command>CREATE ROLE</> (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix recent breakage of <literal>pg_ctl restart</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <filename>pg_control</> is opened in binary mode
-      (Itagaki Takahiro)
-     </para>
-
-     <para>
-      <application>pg_controldata</> and <application>pg_resetxlog</>
-      did this incorrectly, and so could fail on Windows.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008i (for
-      DST law changes in Argentina, Brazil, Mauritius, Syria)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-10">
-  <title>Release 8.2.10</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2008-09-22</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.9.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.10</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.7,
-    see the release notes for 8.2.7.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix bug in btree WAL recovery code (Heikki)
-     </para>
-
-     <para>
-      Recovery failed if the WAL ended partway through a page split operation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential miscalculation of <structfield>datfrozenxid</> (Alvaro)
-     </para>
-
-     <para>
-      This error may explain some recent reports of failure to remove old
-      <structname>pg_clog</> data.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Widen local lock counters from 32 to 64 bits (Tom)
-     </para>
-
-     <para>
-      This responds to reports that the counters could overflow in
-      sufficiently long transactions, leading to unexpected <quote>lock is
-      already held</> errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible duplicate output of tuples during a GiST index scan (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix missed permissions checks when a view contains a simple
-      <literal>UNION ALL</> construct (Heikki)
-     </para>
-
-     <para>
-      Permissions for the referenced tables were checked properly, but not
-      permissions for the view itself.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add checks in executor startup to ensure that the tuples produced by an
-      <command>INSERT</> or <command>UPDATE</> will match the target table's
-      current rowtype (Tom)
-     </para>
-
-     <para>
-      <command>ALTER COLUMN TYPE</>, followed by re-use of a previously
-      cached plan, could produce this type of situation.  The check protects
-      against data corruption and/or crashes that could ensue.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible repeated drops during <command>DROP OWNED</> (Tom)
-     </para>
-
-     <para>
-      This would typically result in strange errors such as <quote>cache
-      lookup failed for relation NNN</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>AT TIME ZONE</> to first try to interpret its timezone
-      argument as a timezone abbreviation, and only try it as a full timezone
-      name if that fails, rather than the other way around as formerly (Tom)
-     </para>
-
-     <para>
-      The timestamp input functions have always resolved ambiguous zone names
-      in this order.  Making <literal>AT TIME ZONE</> do so as well improves
-      consistency, and fixes a compatibility bug introduced in 8.1:
-      in ambiguous cases we now behave the same as 8.0 and before did,
-      since in the older versions <literal>AT TIME ZONE</> accepted
-      <emphasis>only</> abbreviations.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix datetime input functions to correctly detect integer overflow when
-      running on a 64-bit platform (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent integer overflows during units conversion when displaying a
-      configuration parameter that has units (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve performance of writing very long log messages to syslog (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow spaces in the suffix part of an LDAP URL in
-      <filename>pg_hba.conf</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in backwards scanning of a cursor on a <literal>SELECT DISTINCT
-      ON</> query (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner bug with nested sub-select expressions (Tom)
-     </para>
-
-     <para>
-      If the outer sub-select has no direct dependency on the parent query,
-      but the inner one does, the outer value might not get recalculated
-      for new parent query rows.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner to estimate that <literal>GROUP BY</> expressions yielding
-      boolean results always result in two groups, regardless of the
-      expressions' contents (Tom)
-     </para>
-
-     <para>
-      This is very substantially more accurate than the regular <literal>GROUP
-      BY</> estimate for certain boolean tests like <replaceable>col</>
-      <literal>IS NULL</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/pgSQL to not fail when a <literal>FOR</> loop's target variable
-      is a record containing composite-type fields (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Tcl to behave correctly with Tcl 8.5, and to be more careful
-      about the encoding of data sent to or from Tcl (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      On Windows, work around a Microsoft bug by preventing
-      <application>libpq</> from trying to send more than 64kB per system call
-      (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <application>pg_dump</> and <application>pg_restore</>'s
-      error reporting after failure to send a SQL command (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to properly preserve postmaster
-      command-line arguments across a <literal>restart</> (Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008f (for
-      DST law changes in Argentina, Bahamas, Brazil, Mauritius, Morocco,
-      Pakistan, Palestine, and Paraguay)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-9">
-  <title>Release 8.2.9</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2008-06-12</simpara>
-  </note>
-
-  <para>
-   This release contains one serious and one minor bug fix over 8.2.8.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.9</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.7,
-    see the release notes for 8.2.7.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Make <function>pg_get_ruledef()</> parenthesize negative constants (Tom)
-     </para>
-
-     <para>
-      Before this fix, a negative constant in a view or rule might be dumped
-      as, say, <literal>-42::integer</>, which is subtly incorrect: it should
-      be <literal>(-42)::integer</> due to operator precedence rules.
-      Usually this would make little difference, but it could interact with
-      another recent patch to cause
-      <productname>PostgreSQL</> to reject what had been a valid
-      <command>SELECT DISTINCT</> view query.  Since this could result in
-      <application>pg_dump</> output failing to reload, it is being treated
-      as a high-priority fix.  The only released versions in which dump
-      output is actually incorrect are 8.3.1 and 8.2.7.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>ALTER AGGREGATE ... OWNER TO</> update
-      <structname>pg_shdepend</> (Tom)
-     </para>
-
-     <para>
-      This oversight could lead to problems if the aggregate was later
-      involved in a <command>DROP OWNED</> or <command>REASSIGN OWNED</>
-      operation.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-8">
-  <title>Release 8.2.8</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>never released</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.7.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.8</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, if you are upgrading from a version earlier than 8.2.7,
-    see the release notes for 8.2.7.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix <literal>ERRORDATA_STACK_SIZE exceeded</literal> crash that
-      occurred on Windows when using UTF-8 database encoding and a different
-      client encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <command>ALTER TABLE ADD COLUMN ... PRIMARY KEY</> so that the new
-      column is correctly checked to see if it's been initialized to all
-      non-nulls (Brendan Jurd)
-     </para>
-
-     <para>
-      Previous versions neglected to check this requirement at all.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible <command>CREATE TABLE</> failure when inheriting the
-      <quote>same</> constraint from multiple parent relations that
-      inherited that constraint from a common ancestor (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <function>pg_get_ruledef()</> to show the alias, if any, attached
-      to the target table of an <command>UPDATE</> or <command>DELETE</>
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix GIN bug that could result in a <literal>too many LWLocks
-      taken</literal> failure (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crash when decompressing corrupted data
-      (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Repair two places where SIGTERM exit of a backend could leave corrupted
-      state in shared memory (Tom)
-     </para>
-
-     <para>
-      Neither case is very important if SIGTERM is used to shut down the
-      whole database cluster together, but there was a problem if someone
-      tried to SIGTERM individual backends.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix conversions between ISO-8859-5 and other encodings to handle
-      Cyrillic <quote>Yo</> characters (<literal>e</> and <literal>E</> with
-      two dots) (Sergey Burladyan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix several datatype input functions, notably <function>array_in()</>,
-      that were allowing unused bytes in their results to contain
-      uninitialized, unpredictable values (Tom)
-     </para>
-
-     <para>
-      This could lead to failures in which two apparently identical literal
-      values were not seen as equal, resulting in the parser complaining
-      about unmatched <literal>ORDER BY</> and <literal>DISTINCT</>
-      expressions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a corner case in regular-expression substring matching
-      (<literal>substring(<replaceable>string</> from
-      <replaceable>pattern</>)</literal>) (Tom)
-     </para>
-
-     <para>
-      The problem occurs when there is a match to the pattern overall but
-      the user has specified a parenthesized subexpression and that
-      subexpression hasn't got a match.  An example is
-      <literal>substring('foo' from 'foo(bar)?')</>.
-      This should return NULL, since <literal>(bar)</> isn't matched, but
-      it was mistakenly returning the whole-pattern match instead (ie,
-      <literal>foo</>).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008c (for
-      DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba, and
-      Argentina/San_Luis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect result from <application>ecpg</>'s
-      <function>PGTYPEStimestamp_sub()</> function (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix broken GiST comparison function for <filename>contrib/tsearch2</>'s
-      <type>tsquery</> type (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes in <filename>contrib/cube</> functions (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix core dump in <filename>contrib/xml2</>'s
-      <function>xpath_table()</> function when the input query returns a
-      NULL value (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/xml2</>'s makefile to not override
-      <literal>CFLAGS</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>DatumGetBool</> macro to not fail with <application>gcc</>
-      4.3 (Tom)
-     </para>
-
-     <para>
-      This problem affects <quote>old style</> (V0) C functions that
-      return boolean.  The fix is already in 8.3, but the need to
-      back-patch it was not realized at the time.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-7">
-  <title>Release 8.2.7</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2008-03-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.6.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.7</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-    However, you might need to <command>REINDEX</> indexes on textual
-    columns after updating, if you are affected by the Windows locale
-    issue described below.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix character string comparison for Windows locales that consider
-      different character combinations as equal (Tom)
-     </para>
-
-     <para>
-      This fix applies only on Windows and only when using UTF-8
-      database encoding.  The same fix was made for all other cases
-      over two years ago, but Windows with UTF-8 uses a separate code
-      path that was not updated.  If you are using a locale that
-      considers some non-identical strings as equal, you may need to
-      <command>REINDEX</> to fix existing indexes on textual columns.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Repair potential deadlock between concurrent <command>VACUUM FULL</>
-      operations on different system catalogs (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix longstanding <command>LISTEN</>/<command>NOTIFY</>
-      race condition (Tom)
-     </para>
-
-     <para>
-      In rare cases a session that had just executed a
-      <command>LISTEN</> might not get a notification, even though
-      one would be expected because the concurrent transaction executing
-      <command>NOTIFY</> was observed to commit later.
-     </para>
-
-     <para>
-      A side effect of the fix is that a transaction that has executed
-      a not-yet-committed <command>LISTEN</> command will not see any
-      row in <structname>pg_listener</> for the <command>LISTEN</>,
-      should it choose to look; formerly it would have.  This behavior
-      was never documented one way or the other, but it is possible that
-      some applications depend on the old behavior.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>LISTEN</> and <command>UNLISTEN</> within a
-      prepared transaction (Tom)
-     </para>
-
-     <para>
-      This was formerly allowed but trying to do it had various unpleasant
-      consequences, notably that the originating backend could not exit
-      as long as an <command>UNLISTEN</> remained uncommitted.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow dropping a temporary table within a
-      prepared transaction (Heikki)
-     </para>
-
-     <para>
-      This was correctly disallowed by 8.1, but the check was inadvertently
-      broken in 8.2.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix rare crash when an error occurs during a query using a hash index
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leaks in certain usages of set-returning functions (Neil)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix input of datetime values for February 29 in years BC (Tom)
-     </para>
-
-     <para>
-      The former coding was mistaken about which years were leap years.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>unrecognized node type</> error in some variants of
-      <command>ALTER OWNER</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <structname>pg_stat_activity</>.<structfield>waiting</> flag
-      is cleared when a lock wait is aborted (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix handling of process permissions on Windows Vista (Dave, Magnus)
-     </para>
-
-     <para>
-      In particular, this fix allows starting the server as the Administrator
-      user.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008a
-      (in particular, recent Chile changes); adjust timezone abbreviation
-      <literal>VET</> (Venezuela) to mean UTC-4:30, not UTC-4:00 (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to correctly extract the postmaster's port
-      number from command-line options (Itagaki Takahiro, Tom)
-     </para>
-
-     <para>
-      Previously, <literal>pg_ctl start -w</> could try to contact the
-      postmaster on the wrong port, leading to bogus reports of startup
-      failure.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Use <option>-fwrapv</> to defend against possible misoptimization
-      in recent <application>gcc</> versions (Tom)
-     </para>
-
-     <para>
-      This is known to be necessary when building <productname>PostgreSQL</>
-      with <application>gcc</> 4.3 or later.
-     </para>
-    </listitem>
-
-
-    <listitem>
-     <para>
-      Correctly enforce <varname>statement_timeout</> values longer
-      than <literal>INT_MAX</> microseconds (about 35 minutes) (Tom)
-     </para>
-
-     <para>
-      This bug affects only builds with <option>--enable-integer-datetimes</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>unexpected PARAM_SUBLINK ID</> planner error when
-      constant-folding simplifies a sub-select (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix logical errors in constraint-exclusion handling of <literal>IS
-      NULL</> and <literal>NOT</> expressions (Tom)
-     </para>
-
-     <para>
-      The planner would sometimes exclude partitions that should not
-      have been excluded because of the possibility of NULL results.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix another cause of <quote>failed to build any N-way joins</>
-      planner errors (Tom)
-     </para>
-
-     <para>
-      This could happen in cases where a clauseless join needed to be
-      forced before a join clause could be exploited.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect constant propagation in outer-join planning (Tom)
-     </para>
-
-     <para>
-      The planner could sometimes incorrectly conclude that a variable
-      could be constrained to be equal to a constant, leading
-      to wrong query results.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix display of constant expressions in <literal>ORDER BY</>
-      and <literal>GROUP BY</> (Tom)
-     </para>
-
-     <para>
-      An explictly casted constant would be shown incorrectly.  This could
-      for example lead to corruption of a view definition during
-      dump and reload.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>libpq</> to handle NOTICE messages correctly
-      during COPY OUT (Tom)
-     </para>
-
-     <para>
-      This failure has only been observed to occur when a user-defined
-      datatype's output routine issues a NOTICE, but there is no
-      guarantee it couldn't happen due to other causes.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-6">
-  <title>Release 8.2.6</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2008-01-07</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.5,
-   including fixes for significant security issues.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.6</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent functions in indexes from executing with the privileges of
-      the user running <command>VACUUM</>, <command>ANALYZE</>, etc (Tom)
-     </para>
-
-     <para>
-      Functions used in index expressions and partial-index
-      predicates are evaluated whenever a new table entry is made.  It has
-      long been understood that this poses a risk of trojan-horse code
-      execution if one modifies a table owned by an untrustworthy user.
-      (Note that triggers, defaults, check constraints, etc. pose the
-      same type of risk.)  But functions in indexes pose extra danger
-      because they will be executed by routine maintenance operations
-      such as <command>VACUUM FULL</>, which are commonly performed
-      automatically under a superuser account.  For example, a nefarious user
-      can execute code with superuser privileges by setting up a
-      trojan-horse index definition and waiting for the next routine vacuum.
-      The fix arranges for standard maintenance operations
-      (including <command>VACUUM</>, <command>ANALYZE</>, <command>REINDEX</>,
-      and <command>CLUSTER</>) to execute as the table owner rather than
-      the calling user, using the same privilege-switching mechanism already
-      used for <literal>SECURITY DEFINER</> functions.  To prevent bypassing
-      this security measure, execution of <command>SET SESSION
-      AUTHORIZATION</> and <command>SET ROLE</> is now forbidden within a
-      <literal>SECURITY DEFINER</> context.  (CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Repair assorted bugs in the regular-expression package (Tom, Will Drewry)
-     </para>
-
-     <para>
-      Suitably crafted regular-expression patterns could cause crashes,
-      infinite or near-infinite looping, and/or massive memory consumption,
-      all of which pose denial-of-service hazards for applications that
-      accept regex search patterns from untrustworthy sources.
-      (CVE-2007-4769, CVE-2007-4772, CVE-2007-6067)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require non-superusers who use <filename>/contrib/dblink</> to use only
-      password authentication, as a security measure (Joe)
-     </para>
-
-     <para>
-      The fix that appeared for this in 8.2.5 was incomplete, as it plugged
-      the hole for only some <filename>dblink</> functions.  (CVE-2007-6601,
-      CVE-2007-3278)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bugs in WAL replay for GIN indexes (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix GIN index build to work properly when
-      <varname>maintenance_work_mem</> is 4GB or more (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2007k
-      (in particular, recent Argentina changes) (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve planner's handling of LIKE/regex estimation in non-C locales
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planning-speed problem for deep outer-join nests, as well as
-      possible poor choice of join order (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner failure in some cases of <literal>WHERE false AND var IN
-      (SELECT ...)</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>CREATE TABLE ... SERIAL</> and
-      <command>ALTER SEQUENCE ... OWNED BY</> not change the
-      <function>currval()</> state of the sequence (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Preserve the tablespace and storage parameters of indexes that are
-      rebuilt by <command>ALTER TABLE ... ALTER COLUMN TYPE</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make archive recovery always start a new WAL timeline, rather than only
-      when a recovery stop time was used (Simon)
-     </para>
-
-     <para>
-      This avoids a corner-case risk of trying to overwrite an existing
-      archived copy of the last WAL segment, and seems simpler and cleaner
-      than the original definition.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>VACUUM</> not use all of <varname>maintenance_work_mem</>
-      when the table is too small for it to be useful (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential crash in <function>translate()</> when using a multibyte
-      database encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>corr()</> return the correct result for negative
-      correlation values (Neil)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix overflow in <literal>extract(epoch from interval)</> for intervals
-      exceeding 68 years (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Perl to not fail when a UTF-8 regular expression is used
-      in a trusted function (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Perl to cope when platform's Perl defines type <literal>bool</>
-      as <literal>int</> rather than <literal>char</> (Tom)
-     </para>
-
-     <para>
-      While this could theoretically happen anywhere, no standard build of
-      Perl did things this way ... until <productname>Mac OS X</> 10.5.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Python to work correctly with Python 2.5 on 64-bit machines
-      (Marko Kreen)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Python to not crash on long exception messages (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_dump</> to correctly handle inheritance child tables
-      that have default expressions different from their parent's (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>libpq</> crash when <varname>PGPASSFILE</> refers
-      to a file that is not a plain file (Martin Pitt)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <application>ecpg</> parser fixes (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <filename>contrib/pgcrypto</> defend against
-      <application>OpenSSL</> libraries that fail on keys longer than 128
-      bits; which is the case at least on some Solaris versions (Marko Kreen)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <filename>contrib/tablefunc</>'s <function>crosstab()</> handle
-      NULL rowid as a category in its own right, rather than crashing (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <type>tsvector</> and <type>tsquery</> output routines to
-      escape backslashes correctly (Teodor, Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash of <function>to_tsvector()</> on huge input strings (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require a specific version of <productname>Autoconf</> to be used
-      when re-generating the <command>configure</> script (Peter)
-     </para>
-
-     <para>
-      This affects developers and packagers only.  The change was made
-      to prevent accidental use of untested combinations of
-      <productname>Autoconf</> and <productname>PostgreSQL</> versions.
-      You can remove the version check if you really want to use a
-      different <productname>Autoconf</> version, but it's
-      your responsibility whether the result works or not.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update <function>gettimeofday</> configuration check so that
-      <productname>PostgreSQL</> can be built on newer versions of
-      <productname>MinGW</> (Magnus)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-5">
-  <title>Release 8.2.5</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2007-09-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.4.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.5</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent index corruption when a transaction inserts rows and
-      then aborts close to the end of a concurrent <command>VACUUM</>
-      on the same table (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>ALTER DOMAIN ADD CONSTRAINT</> for cases involving
-      domains over domains (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>CREATE DOMAIN ... DEFAULT NULL</> work properly (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some planner problems with outer joins, notably poor
-      size estimation for <literal>t1 LEFT JOIN t2 WHERE t2.col IS NULL</>
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow the <type>interval</> data type to accept input consisting only of
-      milliseconds or microseconds (Neil)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow timezone name to appear before the year in <type>timestamp</> input (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fixes for <acronym>GIN</> indexes used by <filename>/contrib/tsearch2</> (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Speed up rtree index insertion (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix excessive logging of <acronym>SSL</> error messages (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix logging so that log messages are never interleaved when using
-      the syslogger process (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash when <varname>log_min_error_statement</> logging runs out
-      of memory (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect handling of some foreign-key corner cases (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <function>stddev_pop(numeric)</> and <function>var_pop(numeric)</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent <command>REINDEX</> and <command>CLUSTER</> from failing
-      due to attempting to process temporary tables of other sessions (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update the time zone database rules, particularly New Zealand's upcoming changes (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Windows socket and semaphore improvements (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>pg_ctl -w</> work properly in Windows service mode (Dave Page)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory allocation bug when using <application>MIT Kerberos</> on Windows (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Suppress timezone name (<literal>%Z</>) in log timestamps on Windows
-      because of possible encoding mismatches (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require non-superusers who use <filename>/contrib/dblink</> to use only
-      password authentication, as a security measure (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Restrict <filename>/contrib/pgstattuple</> functions to superusers, for security reasons (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not let <filename>/contrib/intarray</> try to make its GIN opclass
-      the default (this caused problems at dump/restore) (Tom)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-4">
-  <title>Release 8.2.4</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2007-04-23</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.3,
-   including a security fix.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.4</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Support explicit placement of the temporary-table schema within
-      <varname>search_path</>, and disable searching it for functions
-      and operators (Tom)
-     </para>
-
-     <para>
-      This is needed to allow a security-definer function to set a
-      truly secure value of <varname>search_path</>.  Without it,
-      an unprivileged SQL user can use temporary objects to execute code
-      with the privileges of the security-definer function (CVE-2007-2138).
-      See <command>CREATE FUNCTION</> for more information.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <varname>shared_preload_libraries</> for Windows
-      by forcing reload in each backend (Korry Douglas)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <function>to_char()</> so it properly upper/lower cases localized day or month
-      names (Pavel Stehule)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <filename>/contrib/tsearch2</> crash fixes (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require <command>COMMIT PREPARED</> to be executed in the same
-      database as the transaction was prepared in (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow <command>pg_dump</> to do binary backups larger than two gigabytes
-      on Windows (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New traditional (Taiwan) Chinese <acronym>FAQ</> (Zhou Daojing)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent the statistics collector from writing to disk too frequently (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential-data-corruption bug in how <command>VACUUM FULL</> handles
-      <command>UPDATE</> chains (Tom, Pavan Deolasee)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in domains that use array types (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <command>pg_dump</> so it can dump a serial column's sequence
-      using <option>-t</> when not also dumping the owning table
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Planner fixes, including improving outer join and bitmap scan
-      selection logic (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible wrong answers or crash when a PL/pgSQL function tries
-      to <literal>RETURN</> from within an <literal>EXCEPTION</> block
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PANIC during enlargement of a hash index (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix POSIX-style timezone specs to follow new USA DST rules (Tom)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-3">
-  <title>Release 8.2.3</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2007-02-07</simpara>
-  </note>
-
-  <para>
-   This release contains two fixes from 8.2.2.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.3</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Remove overly-restrictive check for type length in constraints and
-      functional indexes(Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix optimization so MIN/MAX in subqueries can again use indexes (Tom)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-2">
-  <title>Release 8.2.2</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2007-02-05</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.1, including
-   a security fix.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.2</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.X.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Remove security vulnerabilities that allowed connected users
-      to read backend memory (Tom)
-     </para>
-
-     <para>
-      The vulnerabilities involve suppressing the normal check that a SQL
-      function returns the data type it's declared to, and changing the
-      data type of a table column (CVE-2007-0555, CVE-2007-0556).  These
-      errors can easily be exploited to cause a backend crash, and in
-      principle might be used to read database content that the user
-      should not be able to access.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix not-so-rare-anymore bug wherein btree index page splits could fail
-      due to choosing an infeasible split point (Heikki Linnakangas)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix Borland C compile scripts (L Bayuk)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Properly handle <function>to_char('CC')</> for years ending in
-      <literal>00</> (Tom)
-     </para>
-
-     <para>
-      Year 2000 is in the twentieth century, not the twenty-first.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <filename>/contrib/tsearch2</> localization improvements (Tatsuo, Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect permission check in
-      <literal>information_schema.key_column_usage</> view (Tom)
-     </para>
-
-     <para>
-      The symptom is <quote>relation with OID nnnnn does not exist</> errors.
-      To get this fix without using <command>initdb</>, use <command>CREATE OR
-      REPLACE VIEW</> to install the corrected definition found in
-      <filename>share/information_schema.sql</>.  Note you will need to do
-      this in each database.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <command>VACUUM</> performance for databases with many tables (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix for rare Assert() crash triggered by <literal>UNION</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potentially incorrect results from index searches using
-      <literal>ROW</> inequality conditions (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Tighten security of multi-byte character processing for UTF8 sequences
-      over three bytes long (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bogus <quote>permission denied</> failures occurring on Windows
-      due to attempts to fsync already-deleted files (Magnus, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug that could cause the statistics collector
-      to hang on Windows (Magnus)
-     </para>
-
-     <para>
-      This would in turn lead to autovacuum not working.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes when an already-in-use PL/pgSQL function is
-      updated (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve PL/pgSQL handling of domain types (Sergiy Vyshnevetskiy, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible errors in processing PL/pgSQL exception blocks (Tom)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2-1">
-  <title>Release 8.2.1</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2007-01-08</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.2.
-   For information about new features in the 8.2 major release, see
-   <xref linkend="release-8-2">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.2.1</title>
-
-   <para>
-    A dump/restore is not required for those running 8.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix crash with <literal>SELECT</> ... <literal>LIMIT ALL</> (also
-      <literal>LIMIT NULL</>) (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <filename>Several /contrib/tsearch2</> fixes (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      On Windows, make log messages coming from the operating system use
-      <acronym>ASCII</> encoding (Hiroshi Saito)
-     </para>
-
-     <para>
-      This fixes a conversion problem when there is a mismatch between
-      the encoding of the operating system and database server.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix Windows linking of <application>pg_dump</> using
-      <filename>win32.mak</>
-      (Hiroshi Saito)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner mistakes for outer join queries (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix several problems in queries involving sub-SELECTs (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential crash in SPI during subtransaction abort (Tom)
-     </para>
-
-     <para>
-      This affects all PL functions since they all use SPI.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve build speed of <acronym>PDF</> documentation (Peter)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Re-add <acronym>JST</> (Japan) timezone abbreviation (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve optimization decisions related to index scans (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Have <application>psql</> print multi-byte combining characters as
-      before, rather than output as <literal>\u</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve index usage of regular expressions that use parentheses (Tom)
-     </para>
-
-     <para>
-      This improves <application>psql</> <literal>\d</> performance also.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <application>pg_dumpall</> assume that databases have public
-      <literal>CONNECT</> privilege, when dumping from a pre-8.2 server (Tom)
-     </para>
-
-     <para>
-      This preserves the previous behavior that anyone can connect to a
-      database if allowed by <filename>pg_hba.conf</>.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-2">
-  <title>Release 8.2</title>
-
-  <note>
-   <title>Release date</title>
-   <simpara>2006-12-05</simpara>
-  </note>
-
-  <sect2>
-   <title>Overview</title>
-
-   <para>
-    This release adds many functionality and performance improvements that
-    were requested by users, including:
-
-   <itemizedlist>
-
-     <listitem>
-      <para>
-       Query language enhancements including <command>INSERT/UPDATE/DELETE
-       RETURNING</command>, multirow <literal>VALUES</literal> lists, and
-       optional target-table alias in
-       <command>UPDATE</>/<command>DELETE</command>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Index creation without blocking concurrent
-       <command>INSERT</>/<command>UPDATE</>/<command>DELETE</>
-       operations
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Many query optimization improvements, including support for
-       reordering outer joins
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improved sorting performance with lower memory usage
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       More efficient locking with better concurrency
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       More efficient vacuuming
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Easier administration of warm standby servers
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New <literal>FILLFACTOR</literal> support for tables and indexes
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Monitoring, logging, and performance tuning additions
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       More control over creating and dropping objects
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Table inheritance relationships can be defined
-       for and removed from pre-existing tables
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <command>COPY TO</command> can copy the output of an arbitrary
-       <command>SELECT</command> statement
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Array improvements, including nulls in arrays
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Aggregate-function improvements, including multiple-input
-       aggregates and SQL:2003 statistical functions
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Many <filename>contrib/</filename> improvements
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Migration to Version 8.2</title>
-
-   <para>
-    A dump/restore using <application>pg_dump</application> is
-    required for those wishing to migrate data from any previous
-    release.
-   </para>
-
-   <para>
-    Observe the following incompatibilities:
-   </para>
-
-   <itemizedlist>
-
-     <listitem>
-      <para>
-       Set <link
-       linkend="guc-escape-string-warning"><varname>escape_string_warning</></link>
-       to <literal>on</> by default (Bruce)
-      </para>
-
-      <para>
-       This issues a warning if backslash escapes are used in
-       <link linkend="sql-syntax-strings">non-escape (non-<literal>E''</>)
-       strings</link>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change the <link linkend="sql-syntax-row-constructors">row
-       constructor syntax</link> (<literal>ROW(...)</>) so that
-       list elements <literal>foo.*</> will be expanded to a list
-       of their member fields, rather than creating a nested
-       row type field as formerly (Tom)
-      </para>
-
-      <para>
-       The new behavior is substantially more useful since it
-       allows, for example, triggers to check for data changes
-       with <literal>IF row(new.*) IS DISTINCT FROM row(old.*)</>.
-       The old behavior is still available by omitting <literal>.*</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <link linkend="row-wise-comparison">row comparisons</link>
-       follow <acronym>SQL</> standard semantics and allow them
-       to be used in index scans (Tom)
-      </para>
-
-      <para>
-       Previously, row = and &lt;&gt; comparisons followed the
-       standard but &lt; &lt;= &gt; &gt;= did not.  A row comparison
-       can now be used as an index constraint for a multicolumn
-       index matching the row value.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <link linkend="functions-comparison">row <literal>IS <optional>NOT</> NULL</literal></link>
-       tests follow <acronym>SQL</> standard semantics (Tom)
-      </para>
-
-      <para>
-       The former behavior conformed to the standard for simple cases
-       with <literal>IS NULL</>, but <literal>IS NOT NULL</> would return
-       true if any row field was non-null, whereas the standard says it
-       should return true only when all fields are non-null.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <link linkend="SQL-SET-CONSTRAINTS"><command>SET
-       CONSTRAINT</></link> affect only one constraint (Kris Jurka)
-      </para>
-
-      <para>
-       In previous releases, <command>SET CONSTRAINT</> modified
-       all constraints with a matching name.  In this release,
-       the schema search path is used to modify only the first
-       matching constraint.  A schema specification is also
-       supported.  This more nearly conforms to the SQL standard.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <literal>RULE</> permission for tables, for security reasons
-       (Tom)
-      </para>
-
-      <para>
-       As of this release, only a table's owner can create or modify
-       rules for the table.  For backwards compatibility,
-       <command>GRANT</>/<command>REVOKE RULE</> is still accepted,
-       but it does nothing.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Array comparison improvements (Tom)
-      </para>
-
-      <para>
-       Now array dimensions are also compared.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change <link linkend="functions-array">array concatenation</link>
-       to match documented behavior (Tom)
-      </para>
-
-      <para>
-       This changes the previous behavior where concatenation
-       would modify the array lower bound.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make command-line options of <application>postmaster</>
-       and <link linkend="app-postgres"><application>postgres</></link>
-       identical (Peter)
-      </para>
-
-      <para>
-       This allows the postmaster to pass arguments to each backend
-       without using <literal>-o</>.  Note that some options are now
-       only available as long-form options, because there were conflicting
-       single-letter options.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Deprecate use of <application>postmaster</> symbolic link (Peter)
-      </para>
-
-      <para>
-       <application>postmaster</> and <application>postgres</>
-       commands now act identically, with the behavior determined
-       by command-line options.  The <application>postmaster</> symbolic link is
-       kept for compatibility, but is not really needed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change <link
-       linkend="guc-log-duration"><varname>log_duration</></link>
-       to output even if the query is not output (Tom)
-      </para>
-
-      <para>
-       In prior releases, <varname>log_duration</> only printed if
-       the query appeared earlier in the log.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <link
-       linkend="functions-formatting"><function>to_char(time)</></link>
-       and <link
-       linkend="functions-formatting"><function>to_char(interval)</></link>
-       treat <literal>HH</> and <literal>HH12</> as 12-hour
-       intervals
-      </para>
-
-      <para>
-       Most applications should use <literal>HH24</> unless they
-       want a 12-hour display.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Zero unmasked bits in conversion from <link
-       linkend="datatype-inet"><type>INET</></link> to <link
-       linkend="datatype-inet"><type>CIDR</></link> (Tom)
-      </para>
-
-      <para>
-       This ensures that the converted value is actually valid for
-       <type>CIDR</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <varname>australian_timezones</> configuration variable
-       (Joachim Wieland)
-      </para>
-
-      <para>
-       This variable has been superseded by a more general facility
-       for configuring timezone abbreviations.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve cost estimation for nested-loop index scans (Tom)
-      </para>
-
-      <para>
-       This might eliminate the need to set unrealistically small
-       values of <link
-       linkend="guc-random-page-cost"><varname>random_page_cost</></link>.
-       If you have been using a very small <varname>random_page_cost</>,
-       please recheck your test cases.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change behavior of <command>pg_dump</> <literal>-n</> and
-       <literal>-t</> options.  (Greg Sabino Mullane)
-      </para>
-      <para>
-       See the <command>pg_dump</> manual page for details.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change <link linkend="libpq"><application>libpq</></link>
-       <function>PQdsplen()</> to return a useful value (Martijn
-       van Oosterhout)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Declare <link linkend="libpq"><application>libpq</></link>
-       <function>PQgetssl()</> as returning <literal>void *</>,
-       rather than <literal>SSL *</> (Martijn van Oosterhout)
-      </para>
-
-      <para>
-       This allows applications to use the function without including
-       the OpenSSL headers.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       C-language loadable modules must now include a
-       <link linkend="xfunc-c-dynload"><literal>PG_MODULE_MAGIC</></link>
-       macro call for version compatibility checking
-       (Martijn van Oosterhout)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       For security's sake, modules used by a PL/PerlU function are no
-       longer available to PL/Perl functions (Andrew)
-      </para>
-      <note>
-       <para>
-        This also implies that data can no longer be shared between a PL/Perl
-        function and a PL/PerlU function.
-        Some Perl installations have not been compiled with the correct flags
-        to allow multiple interpreters to exist within a single process.
-        In this situation PL/Perl and PL/PerlU cannot both be used in a
-        single backend. The solution is to get a Perl installation which
-        supports multiple interpreters.
-       </para>
-      </note>
-     </listitem>
-
-     <listitem>
-      <para>
-       In <filename>contrib/xml2/</>, rename <function>xml_valid()</> to
-       <function>xml_is_well_formed()</> (Tom)
-      </para>
-
-      <para>
-       <function>xml_valid()</> will remain for backward compatibility,
-       but its behavior will change to do schema checking in a future
-       release.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <filename>contrib/ora2pg/</>, now at <ulink
-       url="http://www.samse.fr/GPL/ora2pg"></ulink>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove contrib modules that have been migrated to PgFoundry:
-       <filename>adddepend</>, <filename>dbase</>, <filename>dbmirror</>,
-       <filename>fulltextindex</>, <filename>mac</>, <filename>userlock</>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove abandoned contrib modules:
-       <filename>mSQL-interface</>, <filename>tips</>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <acronym>QNX</> and <acronym>BEOS</> ports (Bruce)
-      </para>
-
-      <para>
-       These ports no longer had active maintainers.
-      </para>
-     </listitem>
-
-   </itemizedlist>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-    Below you will find a detailed account of the
-    changes between <productname>PostgreSQL</productname> 8.2 and
-    the previous major release.
-   </para>
-
-   <sect3>
-    <title>Performance Improvements</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow the planner to reorder <link linkend="queries-join">outer
-       joins</link> in some circumstances (Tom)
-      </para>
-
-      <para>
-       In previous releases, outer joins would always be evaluated in
-       the order written in the query. This change allows the
-       query optimizer to consider reordering outer joins, in cases where
-       it can determine that the join order can be changed without
-       altering the meaning of the query.  This can make a
-       considerable performance difference for queries involving
-       multiple outer joins or mixed inner and outer joins.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve efficiency of <link
-       linkend="functions-comparisons"><literal>IN</>
-       (list-of-expressions)</link> clauses (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve sorting speed and reduce memory usage (Simon, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve subtransaction performance (Alvaro, Itagaki Takahiro,
-       Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>FILLFACTOR</> to <link
-       linkend="SQL-CREATETABLE">table</link> and <link
-       linkend="SQL-CREATEINDEX">index</link> creation (ITAGAKI
-       Takahiro)
-      </para>
-
-      <para>
-       This leaves extra free space in each table or index page,
-       allowing improved performance as the database grows.  This
-       is particularly valuable to maintain clustering.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Increase default values for <link
-       linkend="guc-shared-buffers"><varname>shared_buffers</></link>
-       and <varname>max_fsm_pages</>
-       (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve locking performance by breaking the lock manager tables into
-       sections
-       (Tom)
-      </para>
-
-      <para>
-       This allows locking to be more fine-grained, reducing
-       contention.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reduce locking requirements of sequential scans (Qingqing
-       Zhou)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reduce locking required for database creation and destruction
-       (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve the optimizer's selectivity estimates for <link
-       linkend="functions-like"><literal>LIKE</></link>, <link
-       linkend="functions-like"><literal>ILIKE</></link>, and
-       <link linkend="functions-posix-regexp">regular expression</link>
-       operations (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve planning of joins to <link linkend="ddl-inherit">inherited
-       tables</link> and <link linkend="queries-union"><literal>UNION
-       ALL</></link> views (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="guc-constraint-exclusion">constraint
-       exclusion</link> to be applied to <link
-       linkend="ddl-inherit">inherited</link> <command>UPDATE</> and
-       <command>DELETE</> queries (Tom)
-      </para>
-
-      <para>
-       <command>SELECT</> already honored constraint exclusion.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve planning of constant <literal>WHERE</> clauses, such as
-       a condition that depends only on variables inherited from an
-       outer query level (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Protocol-level unnamed prepared statements are re-planned
-       for each set of <literal>BIND</> values (Tom)
-      </para>
-
-      <para>
-       This improves performance because the exact parameter values
-       can be used in the plan.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Speed up vacuuming of B-Tree indexes (Heikki Linnakangas,
-       Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Avoid extra scan of tables without indexes during <link
-       linkend="SQL-VACUUM"><command>VACUUM</></link> (Greg Stark)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve multicolumn <link linkend="GiST"><acronym>GiST</></link>
-       indexing (Oleg, Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove dead index entries before B-Tree page split (Junji
-       Teramoto)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Server Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow a forced switch to a new transaction log file (Simon, Tom)
-      </para>
-
-      <para>
-       This is valuable for keeping warm standby slave servers
-       in sync with the master.  Transaction log file switching now also happens
-       automatically during <link
-       linkend="functions-admin"><function>pg_stop_backup()</></link>.
-       This ensures that all
-       transaction log files needed for recovery can be archived immediately.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <acronym>WAL</> informational functions (Simon)
-      </para>
-
-      <para>
-       Add functions for interrogating the current transaction log insertion
-       point and determining <acronym>WAL</> filenames from the
-       hex <acronym>WAL</> locations displayed by <link
-       linkend="functions-admin"><function>pg_stop_backup()</></link>
-       and related functions.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve recovery from a crash during <acronym>WAL</> replay (Simon)
-      </para>
-
-      <para>
-       The server now does periodic checkpoints during <acronym>WAL</>
-       recovery, so if there is a crash, future <acronym>WAL</>
-       recovery is shortened.  This also eliminates the need for
-       warm standby servers to replay the entire log since the
-       base backup if they crash.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve reliability of long-term <acronym>WAL</> replay
-       (Heikki, Simon, Tom)
-      </para>
-
-      <para>
-       Formerly, trying to roll forward through more than 2 billion
-       transactions would not work due to XID wraparound.  This meant
-       warm standby servers had to be reloaded
-       from fresh base backups periodically.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="guc-archive-timeout"><varname>archive_timeout</></link>
-       to force transaction log file switches at a given interval (Simon)
-      </para>
-
-      <para>
-       This enforces a maximum replication delay for warm standby servers.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add native <link linkend="auth-ldap"><acronym>LDAP</></link>
-       authentication (Magnus Hagander)
-      </para>
-
-      <para>
-       This is particularly useful for platforms that do not
-       support <acronym>PAM</>, such as Windows.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="sql-grant-description-objects"><literal>GRANT
-       CONNECT ON DATABASE</></link> (Gevik Babakhani)
-      </para>
-
-      <para>
-       This gives SQL-level control over database access.  It works as
-       an additional filter on top of the existing
-       <link linkend="auth-pg-hba-conf"><filename>pg_hba.conf</></link>
-       controls.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <link linkend="ssl-tcp"><acronym>SSL</>
-       Certificate Revocation List</link> (<acronym>CRL</>) files
-       (Libor Hoho&scaron;)
-      </para>
-
-      <para>
-       The server and <application>libpq</> both recognize <acronym>CRL</>
-       files now.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="GiST"><acronym>GiST</></link> indexes are
-       now clusterable (Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove routine autovacuum server log entries (Bruce)
-      </para>
-
-      <para>
-       <link
-       linkend="monitoring-stats-views-table"><literal>pg_stat_activity</></link>
-       now shows autovacuum activity.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Track maximum XID age within individual tables, instead of whole databases (Alvaro)
-      </para>
-
-      <para>
-       This reduces the overhead involved in preventing transaction
-       ID wraparound, by avoiding unnecessary VACUUMs.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add last vacuum and analyze timestamp columns to the stats
-       collector (Larry Rosenman)
-      </para>
-
-      <para>
-       These values now appear in the <link
-       linkend="monitoring-stats-views-table"><literal>pg_stat_*_tables</></link>
-       system views.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve performance of statistics monitoring, especially
-       <varname>stats_command_string</>
-       (Tom, Bruce)
-      </para>
-
-      <para>
-       This release enables <varname>stats_command_string</> by
-       default, now that its overhead is minimal.  This means
-       <link
-       linkend="monitoring-stats-views-table"><literal>pg_stat_activity</></link>
-       will now show all active queries by default.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a <literal>waiting</> column to <link
-       linkend="monitoring-stats-views-table"><literal>pg_stat_activity</></link>
-       (Tom)
-      </para>
-
-      <para>
-       This allows <structname>pg_stat_activity</> to show all the
-       information included in the <application>ps</> display.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add configuration parameter <link
-       linkend="guc-update-process-title"><varname>update_process_title</></link>
-       to control whether the <application>ps</> display is updated
-       for every command (Bruce)
-      </para>
-
-      <para>
-       On platforms where it is expensive to update the <application>ps</>
-       display, it might be worthwhile to turn this off and rely solely on
-       <structname>pg_stat_activity</> for status information.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow units to be specified in configuration settings
-       (Peter)
-      </para>
-
-      <para>
-       For example, you can now set <link
-       linkend="guc-shared-buffers"><varname>shared_buffers</></link>
-       to <literal>32MB</> rather than mentally converting sizes.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <link linkend="config-setting">include
-       directives</link> in <filename>postgresql.conf</> (Joachim
-       Wieland)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve logging of protocol-level prepare/bind/execute
-       messages (Bruce, Tom)
-      </para>
-
-      <para>
-       Such logging now shows statement names, bind parameter
-       values, and the text of the query being executed.  Also,
-       the query text is properly included in logged error messages
-       when enabled by <varname>log_min_error_statement</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Prevent <link
-       linkend="guc-max-stack-depth"><varname>max_stack_depth</></link>
-       from being set to unsafe values
-      </para>
-
-      <para>
-       On platforms where we can determine the actual kernel stack depth
-       limit (which is most), make sure that the initial default value of
-       <varname>max_stack_depth</> is safe, and reject attempts to set it
-       to unsafely large values.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Enable highlighting of error location in query in more
-       cases (Tom)
-      </para>
-
-      <para>
-       The server is now able to report a specific error location for
-       some semantic errors (such as unrecognized column name), rather
-       than just for basic syntax errors as before.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <quote>failed to re-find parent key</> errors in
-       <command>VACUUM</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Clean out <filename>pg_internal.init</> cache files during server
-       restart (Simon)
-      </para>
-
-      <para>
-       This avoids a hazard that the cache files might contain stale
-       data after PITR recovery.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix race condition for truncation of a large relation across a
-       gigabyte boundary by <command>VACUUM</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix bug causing needless deadlock errors on row-level locks (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix bugs affecting multi-gigabyte hash indexes (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Each backend process is now its own process group leader (Tom)
-      </para>
-
-      <para>
-       This allows query cancel to abort subprocesses invoked from a
-       backend or archive/recovery process.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Query Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <link linkend="SQL-INSERT"><command>INSERT</></link>/<link
-       linkend="SQL-UPDATE"><command>UPDATE</></link>/<link
-       linkend="SQL-DELETE"><command>DELETE</></link>
-       <literal>RETURNING</> (Jonah Harris, Tom)
-      </para>
-
-      <para>
-       This allows these commands to return values, such as the
-       computed serial key for a new row.  In the <command>UPDATE</>
-       case, values from the updated version of the row are returned.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for multiple-row <link
-       linkend="queries-values"><literal>VALUES</></link> clauses,
-       per SQL standard (Joe, Tom)
-      </para>
-
-      <para>
-       This allows <command>INSERT</> to insert multiple rows of
-       constants, or queries to generate result sets using constants.
-       For example, <literal>INSERT ...  VALUES (...), (...),
-       ....</>, and <literal>SELECT * FROM (VALUES (...), (...),
-       ....) AS alias(f1, ...)</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="SQL-UPDATE"><command>UPDATE</></link>
-       and <link linkend="SQL-DELETE"><command>DELETE</></link>
-       to use an alias for the target table (Atsushi Ogawa)
-      </para>
-
-      <para>
-       The SQL standard does not permit an alias in these commands, but
-       many database systems allow one anyway for notational convenience.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="SQL-UPDATE"><command>UPDATE</></link>
-       to set multiple columns with a list of values (Susanne
-       Ebrecht)
-      </para>
-
-      <para>
-       This is basically a short-hand for assigning the columns
-       and values in pairs.  The syntax is <literal>UPDATE tab
-       SET (<replaceable>column</>, ...) = (<replaceable>val</>, ...)</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make row comparisons work per standard (Tom)
-      </para>
-
-      <para>
-       The forms &lt;, &lt;=, &gt;, &gt;= now compare rows lexicographically,
-       that is, compare the first elements, if equal compare the second
-       elements, and so on.  Formerly they expanded to an AND condition
-       across all the elements, which was neither standard nor very useful.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="SQL-TRUNCATE"><literal>CASCADE</></link>
-       option to <command>TRUNCATE</> (Joachim Wieland)
-      </para>
-
-      <para>
-       This causes <command>TRUNCATE</> to automatically include all tables
-       that reference the specified table(s) via foreign keys.  While
-       convenient, this is a dangerous tool &mdash; use with caution!
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support <literal>FOR UPDATE</> and <literal>FOR SHARE</>
-       in the same <link linkend="SQL-INSERT"><literal>SELECT</></link>
-       command (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="functions-comparisons"><literal>IS NOT
-       DISTINCT FROM</></link> (Pavel Stehule)
-      </para>
-
-      <para>
-       This operator is similar to equality (<literal>=</>), but
-       evaluates to true when both left and right operands are
-       <literal>NULL</>, and to false when just one is, rather than
-       yielding <literal>NULL</> in these cases.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve the length output used by <link
-       linkend="queries-union"><literal>UNION</></link>/<literal>INTERSECT</>/<literal>EXCEPT</>
-       (Tom)
-      </para>
-
-      <para>
-       When all corresponding columns are of the same defined length, that
-       length is used for the result, rather than a generic length.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="functions-like"><literal>ILIKE</></link>
-       to work for multi-byte encodings (Tom)
-      </para>
-
-      <para>
-       Internally, <literal>ILIKE</> now calls <function>lower()</>
-       and then uses <literal>LIKE</>.  Locale-specific regular
-       expression patterns still do not work in these encodings.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Enable <link
-       linkend="guc-standard-conforming-strings"><varname>standard_conforming_strings</></link>
-       to be turned <literal>on</> (Kevin Grittner)
-      </para>
-
-      <para>
-       This allows backslash escaping in strings to be disabled,
-       making <productname>PostgreSQL</> more
-       standards-compliant.  The default is <literal>off</> for backwards
-       compatibility, but future releases will default this to <literal>on</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Do not flatten subqueries that contain <literal>volatile</>
-       functions in their target lists (Jaime Casanova)
-      </para>
-
-      <para>
-       This prevents surprising behavior due to multiple evaluation
-       of a <literal>volatile</> function (such as <function>random()</>
-       or <function>nextval()</>).  It might cause performance
-       degradation in the presence of functions that are unnecessarily
-       marked as <literal>volatile</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add system views <link
-       linkend="view-pg-prepared-statements"><literal>pg_prepared_statements</></link>
-       and <link
-       linkend="view-pg-cursors"><literal>pg_cursors</></link>
-       to show prepared statements and open cursors (Joachim Wieland, Neil)
-      </para>
-
-      <para>
-       These are very useful in pooled connection setups.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support portal parameters in <link
-       linkend="SQL-EXPLAIN"><command>EXPLAIN</></link> and <link
-       linkend="SQL-EXECUTE"><command>EXECUTE</></link> (Tom)
-      </para>
-
-      <para>
-       This allows, for example, <acronym>JDBC</> <literal>?</> parameters to
-       work in these commands.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If <acronym>SQL</>-level <link
-       linkend="SQL-PREPARE"><command>PREPARE</></link> parameters
-       are unspecified, infer their types from the content of the
-       query (Neil)
-      </para>
-
-      <para>
-       Protocol-level <command>PREPARE</> already did this.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>LIMIT</> and <literal>OFFSET</> to exceed
-       two billion (Dhanaraj M)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Object Manipulation Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <literal>TABLESPACE</> clause to <link
-       linkend="SQL-CREATETABLEAS"><command>CREATE TABLE AS</></link>
-       (Neil)
-      </para>
-
-      <para>
-       This allows a tablespace to be specified for the new table.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>ON COMMIT</> clause to <link
-       linkend="SQL-CREATETABLEAS"><command>CREATE TABLE AS</></link>
-       (Neil)
-      </para>
-
-      <para>
-       This allows temporary tables to be truncated or dropped on
-       transaction commit.  The default behavior is for the table
-       to remain until the session ends.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>INCLUDING CONSTRAINTS</> to <link
-       linkend="SQL-CREATETABLE"><command>CREATE TABLE LIKE</></link>
-       (Greg Stark)
-      </para>
-
-      <para>
-       This allows easy copying of <literal>CHECK</> constraints to a new
-       table.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow the creation of placeholder (shell) <link
-       linkend="SQL-CREATETYPE">types</link> (Martijn van Oosterhout)
-      </para>
-
-      <para>
-       A shell type declaration creates a type name, without specifying
-       any of the details of the type.  Making a shell type is useful
-       because it allows cleaner declaration of the type's input/output
-       functions, which must exist before the type can be defined <quote>for
-       real</>.  The syntax is <command>CREATE TYPE <replaceable
-       class="parameter">typename</replaceable></>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="SQL-CREATEAGGREGATE">Aggregate functions</link>
-       now support multiple input parameters (Sergey Koposov, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new aggregate creation <link
-       linkend="SQL-CREATEAGGREGATE">syntax</link> (Tom)
-      </para>
-
-      <para>
-       The new syntax is <command>CREATE AGGREGATE
-       <replaceable>aggname</> (<replaceable>input_type</>)
-       (<replaceable>parameter_list</>)</command>.  This more
-       naturally supports the new multi-parameter aggregate
-       functionality.  The previous syntax is still supported.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="SQL-ALTERROLE"><command>ALTER ROLE PASSWORD NULL</></link>
-       to remove a previously set role password (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>DROP</> object <literal>IF EXISTS</> for many
-       object types (Andrew)
-      </para>
-
-      <para>
-       This allows <command>DROP</> operations on non-existent
-       objects without generating an error.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="SQL-DROP-OWNED"><literal>DROP OWNED</></link>
-       to drop all objects owned by a role (Alvaro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="SQL-REASSIGN-OWNED"><literal>REASSIGN
-       OWNED</></link> to reassign ownership of all objects owned
-       by a role (Alvaro)
-      </para>
-
-      <para>
-       This, and <literal>DROP OWNED</> above, facilitate dropping
-       roles.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="SQL-GRANT"><command>GRANT ON SEQUENCE</></link>
-       syntax (Bruce)
-      </para>
-
-      <para>
-       This was added for setting sequence-specific permissions.
-       <literal>GRANT ON TABLE</> for sequences is still supported
-       for backward compatibility.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="SQL-GRANT"><literal>USAGE</></link>
-       permission for sequences that allows only <function>currval()</>
-       and <function>nextval()</>, not <function>setval()</>
-       (Bruce)
-      </para>
-
-      <para>
-       <literal>USAGE</> permission allows more fine-grained
-       control over sequence access.  Granting <literal>USAGE</>
-       allows users to increment
-       a sequence, but prevents them from setting the sequence to
-       an arbitrary value using <function>setval()</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="SQL-ALTERTABLE"><literal>ALTER TABLE
-       [ NO ] INHERIT</></link> (Greg Stark)
-      </para>
-
-      <para>
-       This allows inheritance to be adjusted dynamically, rather than
-       just at table creation and destruction.  This is very valuable
-       when using inheritance to implement table partitioning.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="SQL-COMMENT">comments</link> on global
-       objects to be stored globally (Kris Jurka)
-      </para>
-
-      <para>
-       Previously, comments attached to databases were stored in individual
-       databases, making them ineffective, and there was no provision
-       at all for comments on roles or tablespaces.  This change adds a new
-       shared catalog <link
-       linkend="catalog-pg-shdescription"><structname>pg_shdescription</structname></link>
-       and stores comments on databases, roles, and tablespaces therein.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Utility Command Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add option to allow indexes to be created without blocking
-       concurrent writes to the table (Greg Stark, Tom)
-      </para>
-
-      <para>
-       The new syntax is <link linkend="SQL-CREATEINDEX"><command>CREATE
-       INDEX CONCURRENTLY</></link>.  The default behavior is
-       still to block table modification while a index is being
-       created.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Provide <link linkend="functions-advisory-locks">advisory
-       locking</link> functionality (Abhijit Menon-Sen, Tom)
-      </para>
-
-      <para>
-       This is a new locking API designed to replace what used to be
-       in /contrib/userlock.  The userlock code is now on pgfoundry.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="SQL-COPY"><command>COPY</></link> to
-       dump a <command>SELECT</> query (Zoltan Boszormenyi, Karel
-       Zak)
-      </para>
-
-      <para>
-       This allows <command>COPY</> to dump arbitrary <acronym>SQL</>
-       queries. The syntax is <literal>COPY (SELECT ...) TO</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make the <link linkend="SQL-COPY"><command>COPY</></link>
-       command return a command tag that includes the number of
-       rows copied (Volkan YAZICI)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="SQL-VACUUM"><command>VACUUM</></link>
-       to expire rows without being affected by other concurrent
-       <command>VACUUM</> operations (Hannu Krossing, Alvaro, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <link linkend="APP-INITDB"><application>initdb</></link>
-       detect the operating system locale and set the default
-       <varname>DateStyle</> accordingly (Peter)
-      </para>
-
-      <para>
-       This makes it more likely that the installed
-       <filename>postgresql.conf</> <varname>DateStyle</> value will
-       be as desired.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reduce number of progress messages displayed by <application>initdb</> (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Date/Time Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow full timezone names in <link
-       linkend="datatype-datetime"><type>timestamp</></link> input values
-       (Joachim Wieland)
-      </para>
-
-      <para>
-       For example, <literal>'2006-05-24 21:11
-       America/New_York'::timestamptz</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support configurable timezone abbreviations (Joachim Wieland)
-      </para>
-
-      <para>
-       A desired set of timezone abbreviations can be chosen via the
-       configuration parameter <link
-       linkend="guc-timezone-abbreviations"><varname>timezone_abbreviations</></link>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="view-pg-timezone-abbrevs"><varname>pg_timezone_abbrevs</></link>
-       and <link
-       linkend="view-pg-timezone-names"><varname>pg_timezone_names</></link>
-       views to show supported timezones (Magnus Hagander)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="functions-datetime-table"><function>clock_timestamp()</></link>,
-       <link
-       linkend="functions-datetime-table"><function>statement_timestamp()</></link>,
-       and <link
-       linkend="functions-datetime-table"><function>transaction_timestamp()</></link>
-       (Bruce)
-      </para>
-
-      <para>
-       <function>clock_timestamp()</> is the current wall-clock time,
-       <function>statement_timestamp()</> is the time the current
-       statement arrived at the server, and
-       <function>transaction_timestamp()</> is an alias for
-       <function>now()</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link
-       linkend="functions-formatting"><function>to_char()</></link>
-       to print localized month and day names (Euler Taveira de
-       Oliveira)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link
-       linkend="functions-formatting"><function>to_char(time)</></link>
-       and <link
-       linkend="functions-formatting"><function>to_char(interval)</></link>
-       to output <acronym>AM</>/<acronym>PM</> specifications
-       (Bruce)
-      </para>
-
-      <para>
-       Intervals and times are treated as 24-hour periods, e.g.
-       <literal>25 hours</> is considered <acronym>AM</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new function <link
-       linkend="functions-datetime-table"><function>justify_interval()</></link>
-       to adjust interval units (Mark Dilger)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow timezone offsets up to 14:59 away from GMT
-      </para>
-
-      <para>
-       Kiribati uses GMT+14, so we'd better accept that.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Interval computation improvements (Michael Glaesemann, Bruce)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Other Data Type and Function Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow arrays to contain <literal>NULL</> elements (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow assignment to array elements not contiguous with the existing
-       entries (Tom)
-      </para>
-
-      <para>
-       The intervening array positions will be filled with nulls.
-       This is per SQL standard.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New built-in <link linkend="functions-array">operators</link>
-       for array-subset comparisons (<literal>@&gt;</>,
-       <literal>&lt;@</>, <literal>&amp;&amp;</>) (Teodor, Tom)
-      </para>
-
-      <para>
-       These operators can be indexed for many data types using
-       <acronym>GiST</> or <acronym>GIN</> indexes.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add convenient arithmetic <link
-       linkend="cidr-inet-operators-table">operations</link> on
-       <type>INET</>/<type>CIDR</> values (Stephen R. van den
-       Berg)
-      </para>
-
-      <para>
-       The new operators are <literal>&amp;</> (and), <literal>|</>
-       (or), <literal>~</> (not), <type>inet</> <literal>+</> <type>int8</>,
-       <type>inet</> <literal>-</> <type>int8</>, and
-       <type>inet</> <literal>-</> <type>inet</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new <link
-       linkend="functions-aggregate-statistics-table">aggregate functions</link>
-       from SQL:2003 (Neil)
-      </para>
-
-      <para>
-       The new functions are <function>var_pop()</>,
-       <function>var_samp()</>, <function>stddev_pop()</>, and
-       <function>stddev_samp()</>.  <function>var_samp()</> and
-       <function>stddev_samp()</> are merely renamings of the
-       existing aggregates <function>variance()</> and
-       <function>stddev()</>.  The latter names remain available
-       for backward compatibility.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add SQL:2003 statistical <link
-       linkend="functions-aggregate-statistics-table">aggregates</link>
-       (Sergey Koposov)
-      </para>
-
-      <para>
-       New functions:  <function>regr_intercept()</>,
-       <function>regr_slope()</>, <function>regr_r2()</>,
-       <function>corr()</>, <function>covar_samp()</>,
-       <function>covar_pop()</>, <function>regr_avgx()</>,
-       <function>regr_avgy()</>, <function>regr_sxy()</>,
-       <function>regr_sxx()</>, <function>regr_syy()</>,
-       <function>regr_count()</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="SQL-CREATEDOMAIN">domains</link> to be
-       based on other domains (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Properly enforce domain <link
-       linkend="ddl-constraints"><literal>CHECK</></link> constraints
-       everywhere (Neil, Tom)
-      </para>
-
-      <para>
-       For example, the result of a user-defined function that is
-       declared to return a domain type is now checked against the
-       domain's constraints. This closes a significant hole in the domain
-       implementation.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix problems with dumping renamed <link
-       linkend="datatype-serial"><type>SERIAL</></link> columns
-       (Tom)
-      </para>
-
-      <para>
-       The fix is to dump a <type>SERIAL</> column by explicitly
-       specifying its <literal>DEFAULT</> and sequence elements,
-       and reconstructing the <type>SERIAL</> column on reload
-       using a new <link linkend="SQL-ALTERSEQUENCE"><command>ALTER
-       SEQUENCE OWNED BY</></link> command.  This also allows
-       dropping a <type>SERIAL</> column specification.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a server-side sleep function <link
-       linkend="functions-datetime-delay"><function>pg_sleep()</></link>
-       (Joachim Wieland)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add all comparison operators for the <link
-       linkend="datatype-oid"><type>tid</></link> (tuple id) data
-       type (Mark Kirkwood, Greg Stark, Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>PL/pgSQL Server-Side Language Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <literal>TG_table_name</> and <literal>TG_table_schema</> to
-       trigger parameters (Andrew)
-      </para>
-
-      <para>
-       <literal>TG_relname</> is now deprecated.  Comparable
-       changes have been made in the trigger parameters for the other
-       PLs as well.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>FOR</> statements to return values to scalars
-       as well as records and row types (Pavel Stehule)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a <literal>BY</> clause to the <literal>FOR</> loop,
-       to control the iteration increment (Jaime Casanova)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>STRICT</> to <link
-       linkend="plpgsql-statements-sql-onerow"><command>SELECT
-       INTO</></link> (Matt Miller)
-      </para>
-
-      <para>
-       <literal>STRICT</> mode throws an exception if more or less
-       than one row is returned by the <command>SELECT</>, for
-       <productname>Oracle PL/SQL</> compatibility.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>PL/Perl Server-Side Language Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <literal>table_name</> and <literal>table_schema</> to
-       trigger parameters (Adam Sj&oslash;gren)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add prepared queries (Dmitry Karasik)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <literal>$_TD</> trigger data a global variable (Andrew)
-      </para>
-
-      <para>
-       Previously, it was lexical, which caused unexpected sharing
-       violations.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Run PL/Perl and PL/PerlU in separate interpreters, for security
-       reasons (Andrew)
-      </para>
-      <para>
-       In consequence, they can no longer share data nor loaded modules.
-       Also, if Perl has not been compiled with the requisite flags to
-       allow multiple interpreters, only one of these languages can be used
-       in any given backend process.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>PL/Python Server-Side Language Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Named parameters are passed as ordinary variables, as well as in the
-       <literal>args[]</> array (Sven Suursoho)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>table_name</> and <literal>table_schema</> to
-       trigger parameters (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow returning of composite types and result sets (Sven Suursoho)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Return result-set as <literal>list</>, <literal>iterator</>,
-       or <literal>generator </>(Sven Suursoho)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow functions to return <literal>void</> (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Python 2.5 is now supported (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><link linkend="APP-PSQL"><application>psql</></link> Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add new command <literal>\password</> for changing role
-       password with client-side password encryption (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>\c</> to connect to a new host and port
-       number (David, Volkan YAZICI)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add tablespace display to <literal>\l+</> (Philip Yarra)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <literal>\df</> slash command to include the argument
-       names and modes (<literal>OUT</> or <literal>INOUT</>) of
-       the function (David Fetter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support binary <command>COPY</> (Andreas Pflug)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add option to run the entire session in a single transaction
-       (Simon)
-      </para>
-
-      <para>
-       Use option <literal>-1</> or <literal>--single-transaction</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support for automatically retrieving <command>SELECT</>
-       results in batches using a cursor (Chris Mair)
-      </para>
-
-      <para>
-       This is enabled using <command>\set FETCH_COUNT
-       <replaceable>n</></command>. This
-       feature allows large result sets to be retrieved in
-       <application>psql</> without attempting to buffer the entire
-       result set in memory.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make multi-line values align in the proper column
-       (Martijn van Oosterhout)
-      </para>
-
-      <para>
-       Field values containing newlines are now displayed in a more
-       readable fashion.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Save multi-line statements as a single entry, rather than
-       one line at a time (Sergey E. Koposov)
-      </para>
-
-      <para>
-       This makes up-arrow recall of queries easier.  (This is
-       not available on Windows, because that platform uses the native
-       command-line editing present in the operating system.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make the line counter 64-bit so it can handle files with more
-       than two billion lines (David Fetter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Report both the returned data and the command status tag
-       for <command>INSERT</>/<command>UPDATE</>/<command>DELETE
-       RETURNING</> (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><link linkend="APP-PGDUMP"><application>pg_dump</></link> Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow complex selection of objects to be included or excluded
-       by <application>pg_dump</> (Greg Sabino Mullane)
-      </para>
-
-      <para>
-       <application>pg_dump</> now supports multiple <literal>-n</>
-       (schema) and <literal>-t</> (table) options, and adds
-       <literal>-N</> and <literal>-T</> options to exclude objects.
-       Also, the arguments of these switches can now be wild-card expressions
-       rather than single object names, for example
-       <literal>-t 'foo*'</>, and a schema can be part of
-       a <literal>-t</> or <literal>-T</> switch, for example
-       <literal>-t schema1.table1</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="APP-PGRESTORE"><application>pg_restore</></link>
-       <literal>--no-data-for-failed-tables</> option to suppress
-       loading data if table creation failed (i.e., the table already
-       exists) (Martin Pitt)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="APP-PGRESTORE"><application>pg_restore</></link>
-       option to run the entire session in a single transaction
-       (Simon)
-      </para>
-
-      <para>
-       Use option <literal>-1</> or <literal>--single-transaction</>.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><link linkend="libpq"><application>libpq</></link> Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="libpq-misc"><function>PQencryptPassword()</></link>
-       to encrypt passwords (Tom)
-      </para>
-
-      <para>
-       This allows passwords to be sent pre-encrypted for commands
-       like <link linkend="SQL-ALTERROLE"><command>ALTER ROLE ...
-       PASSWORD</></link>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add function <link
-       linkend="libpq-threading"><function>PQisthreadsafe()</></link>
-       (Bruce)
-      </para>
-
-      <para>
-       This allows applications to query the thread-safety status
-       of the library.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="libpq-exec-main"><function>PQdescribePrepared()</></link>,
-       <link
-       linkend="libpq-exec-main"><function>PQdescribePortal()</></link>,
-       and related functions to return information about previously
-       prepared statements and open cursors (Volkan YAZICI)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="libpq-ldap"><acronym>LDAP</></link> lookups
-       from <link
-       linkend="libpq-pgservice"><filename>pg_service.conf</></link>
-       (Laurenz Albe)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow a hostname in <link
-       linkend="libpq-pgpass"><filename>~/.pgpass</></link>
-       to match the default socket directory (Bruce)
-      </para>
-
-      <para>
-       A blank hostname continues to match any Unix-socket connection,
-       but this addition allows entries that are specific to one of
-       several postmasters on the machine.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><link linkend="ecpg"><application>ecpg</></link> Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow <link linkend="SQL-SHOW"><command>SHOW</></link> to
-       put its result into a variable (Joachim Wieland)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="SQL-COPY"><command>COPY TO STDOUT</></link>
-       (Joachim Wieland)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add regression tests (Joachim Wieland, Michael)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Major source code cleanups (Joachim Wieland, Michael)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><application>Windows</> Port</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow <acronym>MSVC</> to compile the <productname>PostgreSQL</>
-       server (Magnus, Hiroshi Saito)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <acronym>MSVC</> support for utility commands and <link
-       linkend="APP-PGDUMP"><application>pg_dump</></link> (Hiroshi
-       Saito)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for Windows code pages <literal>1253</>,
-       <literal>1254</>, <literal>1255</>, and <literal>1257</>
-       (Kris Jurka)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Drop privileges on startup, so that the server can be started from
-       an administrative account (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Stability fixes (Qingqing Zhou, Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add native semaphore implementation (Qingqing Zhou)
-      </para>
-
-      <para>
-       The previous code mimicked SysV semaphores.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Source Code Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <link linkend="GIN"><acronym>GIN</></link> (Generalized
-       Inverted iNdex) index access method (Teodor, Oleg)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove R-tree indexing (Tom)
-      </para>
-
-      <para>
-       Rtree has been re-implemented using <link
-       linkend="GiST"><acronym>GiST</></link>. Among other
-       differences, this means that rtree indexes now have support
-       for crash recovery via write-ahead logging (WAL).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reduce libraries needlessly linked into the backend (Martijn
-       van Oosterhout, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a configure flag to allow libedit to be preferred over
-       <acronym>GNU</> readline (Bruce)
-      </para>
-
-      <para>
-       Use configure <link
-       linkend="configure"><literal>--with-libedit-preferred</></link>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow installation into directories containing spaces
-       (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve ability to relocate installation directories (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <productname>Solaris x86_64</> using the
-       <productname>Solaris</> compiler (Pierre Girard, Theo
-       Schlossnagle, Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <application>DTrace</> support (Robert Lor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>PG_VERSION_NUM</> for use by third-party
-       applications wanting to test the backend version in C using &gt;
-       and &lt; comparisons (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>XLOG_BLCKSZ</> as independent from <literal>BLCKSZ</>
-       (Mark Wong)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>LWLOCK_STATS</> define to report locking
-       activity (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Emit warnings for unknown <application>configure</> options
-       (Martijn van Oosterhout)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add server support for <quote>plugin</> libraries
-       that can be used for add-on tasks such as debugging and performance
-       measurement (Korry Douglas)
-      </para>
-
-      <para>
-       This consists of two features: a table of <quote>rendezvous
-       variables</> that allows separately-loaded shared libraries to
-       communicate, and a new configuration parameter <link
-       linkend="guc-local-preload-libraries"><varname>local_preload_libraries</></link>
-       that allows libraries to be loaded into specific sessions without
-       explicit cooperation from the client application.  This allows
-       external add-ons to implement features such as a PL/pgSQL debugger.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Rename existing configuration parameter
-       <varname>preload_libraries</> to <link
-       linkend="guc-shared-preload-libraries"><varname>shared_preload_libraries</></link>
-       (Tom)
-      </para>
-
-      <para>
-       This was done for clarity in comparison to
-       <varname>local_preload_libraries</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new configuration parameter <link
-       linkend="guc-server-version-num"><varname>server_version_num</></link>
-       (Greg Sabino Mullane)
-      </para>
-
-      <para>
-       This is like <varname>server_version</varname>, but is an
-       integer, e.g.  <literal>80200</>. This allows applications to
-       make version checks more easily.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a configuration parameter <link
-       linkend="guc-seq-page-cost"><varname>seq_page_cost</></link>
-       (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Re-implement the <link linkend="regress">regression test</link> script as a C program
-       (Magnus, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow loadable modules to allocate shared memory and
-       lightweight locks (Marc Munro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add automatic initialization and finalization of dynamically
-       loaded libraries (Ralf Engelschall, Tom)
-      </para>
-
-      <para>
-       New <link linkend="xfunc-c-dynload">functions</link>
-       <function>_PG_init()</> and <function>_PG_fini()</> are
-       called if the library defines such symbols.  Hence we no
-       longer need to specify an initialization function in
-       <varname>shared_preload_libraries</>; we can assume that
-       the library used the <function>_PG_init()</> convention
-       instead.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="xfunc-c-dynload"><literal>PG_MODULE_MAGIC</></link>
-       header block to all shared object files (Martijn van
-       Oosterhout)
-      </para>
-
-      <para>
-       The magic block prevents version mismatches between loadable object
-       files and servers.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Add shared library support for AIX (Laurenz Albe)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New <link linkend="datatype-xml"><acronym>XML</></link>
-       documentation section (Bruce)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Contrib Changes</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Major tsearch2 improvements (Oleg, Teodor)
-      </para>
-
-      <itemizedlist>
-
-       <listitem>
-        <para>
-         multibyte encoding support, including <acronym>UTF8</>
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         query rewriting support
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         improved ranking functions
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         thesaurus dictionary support
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Ispell dictionaries now recognize <application>MySpell</>
-         format, used by <application>OpenOffice</>
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         <acronym>GIN</> support
-        </para>
-       </listitem>
-
-      </itemizedlist>
-
-     </listitem>
-
-     <listitem>
-      <para>
-       Add adminpack module containing <application>Pgadmin</> administration
-       functions (Dave)
-      </para>
-
-      <para>
-       These functions provide additional file system access
-       routines not present in the default <productname>PostgreSQL</>
-       server.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add sslinfo module (Victor Wagner)
-      </para>
-
-      <para>
-       Reports information about the current connection's <acronym>SSL</>
-       certificate.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add pgrowlocks module (Tatsuo)
-      </para>
-
-      <para>
-       This shows row locking information for a specified table.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add hstore module (Oleg, Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add isn module, replacing isbn_issn (Jeremy Kronuz)
-      </para>
-
-      <para>
-       This new implementation supports <acronym>EAN13</>, <acronym>UPC</>,
-       <acronym>ISBN</> (books), <acronym>ISMN</> (music), and
-       <acronym>ISSN</> (serials).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add index information functions to pgstattuple (ITAGAKI Takahiro,
-       Satoshi Nagayasu)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add pg_freespacemap module to display free space map information
-       (Mark Kirkwood)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       pgcrypto now has all planned functionality (Marko Kreen)
-      </para>
-      <itemizedlist>
-       <listitem>
-        <para>
-         Include iMath library in pgcrypto to have the public-key encryption
-         functions always available.
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Add SHA224 algorithm that was missing in OpenBSD code.
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Activate builtin code for SHA224/256/384/512 hashes on older
-         OpenSSL to have those algorithms always available.
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         New function gen_random_bytes() that returns cryptographically strong
-         randomness.  Useful for generating encryption keys.
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         Remove digest_exists(), hmac_exists() and cipher_exists() functions.
-        </para>
-       </listitem>
-      </itemizedlist>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improvements to cube module (Joshua Reich)
-      </para>
-
-      <para>
-       New functions are <function>cube(float[])</>,
-       <function>cube(float[], float[])</>, and
-       <function>cube_subset(cube, int4[])</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add async query capability to dblink (Kai Londenberg,
-       Joe Conway)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New operators for array-subset comparisons (<literal>@&gt;</>,
-       <literal>&lt;@</>, <literal>&amp;&amp;</>) (Tom)
-      </para>
-
-      <para>
-       Various contrib packages already had these operators for their
-       datatypes, but the naming wasn't consistent.  We have now added
-       consistently named array-subset comparison operators to the core code
-       and all the contrib packages that have such functionality.
-       (The old names remain available, but are deprecated.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add uninstall scripts for all contrib packages that have install
-       scripts (David, Josh Drake)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-  </sect2>
- </sect1>
diff --git a/doc-xc/src/sgml/release-8.3.sgmlin b/doc-xc/src/sgml/release-8.3.sgmlin
deleted file mode 100644
index c0595ab5df..0000000000
--- a/doc-xc/src/sgml/release-8.3.sgmlin
+++ /dev/null
@@ -1,6433 +0,0 @@
-<!-- doc/src/sgml/release-8.3.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-8-3-14">
-  <title>Release 8.3.14</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2011-01-31</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.13.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.14</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.8,
-    see the release notes for 8.3.8.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Avoid failures when <command>EXPLAIN</> tries to display a simple-form
-      <literal>CASE</> expression (Tom Lane)
-     </para>
-
-     <para>
-      If the <literal>CASE</>'s test expression was a constant, the planner
-      could simplify the <literal>CASE</> into a form that confused the
-      expression-display code, resulting in <quote>unexpected CASE WHEN
-      clause</> errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assignment to an array slice that is before the existing range
-      of subscripts (Tom Lane)
-     </para>
-
-     <para>
-      If there was a gap between the newly added subscripts and the first
-      pre-existing subscript, the code miscalculated how many entries needed
-      to be copied from the old array's null bitmap, potentially leading to
-      data corruption or crash.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unexpected conversion overflow in planner for very distant date
-      values (Tom Lane)
-     </para>
-
-     <para>
-      The <type>date</> type supports a wider range of dates than can be
-      represented by the <type>timestamp</> types, but the planner assumed it
-      could always convert a date to timestamp with impunity.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_restore</>'s text output for large objects (BLOBs)
-      when <varname>standard_conforming_strings</> is on (Tom Lane)
-     </para>
-
-     <para>
-      Although restoring directly to a database worked correctly, string
-      escaping was incorrect if <application>pg_restore</> was asked for
-      SQL text output and <varname>standard_conforming_strings</> had been
-      enabled in the source database.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix erroneous parsing of <type>tsquery</> values containing
-      <literal>... &amp; !(subexpression) | ...</literal> (Tom Lane)
-     </para>
-
-     <para>
-      Queries containing this combination of operators were not executed
-      correctly.  The same error existed in <filename>contrib/intarray</>'s
-      <type>query_int</> type and <filename>contrib/ltree</>'s
-      <type>ltxtquery</> type.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix buffer overrun in <filename>contrib/intarray</>'s input function
-      for the <type>query_int</> type (Apple)
-     </para>
-
-     <para>
-      This bug is a security risk since the function's return address could
-      be overwritten.  Thanks to Apple Inc's security team for reporting this
-      issue and supplying the fix.  (CVE-2010-4015)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in <filename>contrib/seg</>'s GiST picksplit algorithm
-      (Alexander Korotkov)
-     </para>
-
-     <para>
-      This could result in considerable inefficiency, though not actually
-      incorrect answers, in a GiST index on a <type>seg</> column.
-      If you have such an index, consider <command>REINDEX</>ing it after
-      installing this update.  (This is identical to the bug that was fixed in
-      <filename>contrib/cube</> in the previous update.)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-13">
-  <title>Release 8.3.13</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-12-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.12.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.13</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.8,
-    see the release notes for 8.3.8.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Force the default
-      <link linkend="guc-wal-sync-method"><varname>wal_sync_method</></link>
-      to be <literal>fdatasync</> on Linux (Tom Lane, Marti Raudsepp)
-     </para>
-
-     <para>
-      The default on Linux has actually been <literal>fdatasync</> for many
-      years, but recent kernel changes caused <productname>PostgreSQL</> to
-      choose <literal>open_datasync</> instead.  This choice did not result
-      in any performance improvement, and caused outright failures on
-      certain filesystems, notably <literal>ext4</> with the
-      <literal>data=journal</> mount option.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane)
-     </para>
-
-     <para>
-      This could result in <quote>bad buffer id: 0</> failures or
-      corruption of index contents during replication.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix recovery from base backup when the starting checkpoint WAL record
-      is not in the same WAL segment as its redo point (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix persistent slowdown of autovacuum workers when multiple workers
-      remain active for a long time (Tom Lane)
-     </para>
-
-     <para>
-      The effective <varname>vacuum_cost_limit</> for an autovacuum worker
-      could drop to nearly zero if it processed enough tables, causing it
-      to run extremely slowly.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add support for detecting register-stack overrun on <literal>IA64</>
-      (Tom Lane)
-     </para>
-
-     <para>
-      The <literal>IA64</> architecture has two hardware stacks.  Full
-      prevention of stack-overrun failures requires checking both.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add a check for stack overflow in <function>copyObject()</> (Tom Lane)
-     </para>
-
-     <para>
-      Certain code paths could crash due to stack overflow given a
-      sufficiently complex query.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix detection of page splits in temporary GiST indexes (Heikki
-      Linnakangas)
-     </para>
-
-     <para>
-      It is possible to have a <quote>concurrent</> page split in a
-      temporary index, if for example there is an open cursor scanning the
-      index when an insertion is done.  GiST failed to detect this case and
-      hence could deliver wrong results when execution of the cursor
-      continued.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid memory leakage while <command>ANALYZE</>'ing complex index
-      expressions (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure an index that uses a whole-row Var still depends on its table
-      (Tom Lane)
-     </para>
-
-     <para>
-      An index declared like <literal>create index i on t (foo(t.*))</>
-      would not automatically get dropped when its table was dropped.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not <quote>inline</> a SQL function with multiple <literal>OUT</>
-      parameters (Tom Lane)
-     </para>
-
-     <para>
-      This avoids a possible crash due to loss of information about the
-      expected result rowtype.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Behave correctly if <literal>ORDER BY</>, <literal>LIMIT</>,
-      <literal>FOR UPDATE</>, or <literal>WITH</> is attached to the
-      <literal>VALUES</> part of <literal>INSERT ... VALUES</> (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix constant-folding of <literal>COALESCE()</> expressions (Tom Lane)
-     </para>
-
-     <para>
-      The planner would sometimes attempt to evaluate sub-expressions that
-      in fact could never be reached, possibly leading to unexpected errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix postmaster crash when connection acceptance
-      (<function>accept()</> or one of the calls made immediately after it)
-      fails, and the postmaster was compiled with GSSAPI support (Alexander
-      Chernikov)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix missed unlink of temporary files when <varname>log_temp_files</>
-      is active (Tom Lane)
-     </para>
-
-     <para>
-      If an error occurred while attempting to emit the log message, the
-      unlink was not done, resulting in accumulation of temp files.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add print functionality for <structname>InhRelation</> nodes (Tom Lane)
-     </para>
-
-     <para>
-      This avoids a failure when <varname>debug_print_parse</> is enabled
-      and certain types of query are executed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect calculation of distance from a point to a horizontal
-      line segment (Tom Lane)
-     </para>
-
-     <para>
-      This bug affected several different geometric distance-measurement
-      operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/pgSQL</>'s handling of <quote>simple</>
-      expressions to not fail in recursion or error-recovery cases (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/Python</>'s handling of set-returning functions
-      (Jan Urbanski)
-     </para>
-
-     <para>
-      Attempts to call SPI functions within the iterator generating a set
-      result would fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in <filename>contrib/cube</>'s GiST picksplit algorithm
-      (Alexander Korotkov)
-     </para>
-
-     <para>
-      This could result in considerable inefficiency, though not actually
-      incorrect answers, in a GiST index on a <type>cube</> column.
-      If you have such an index, consider <command>REINDEX</>ing it after
-      installing this update.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Don't emit <quote>identifier will be truncated</> notices in
-      <filename>contrib/dblink</> except when creating new connections
-      (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential coredump on missing public key in
-      <filename>contrib/pgcrypto</> (Marti Raudsepp)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak in <filename>contrib/xml2</>'s XPath query functions
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010o
-      for DST law changes in Fiji and Samoa;
-      also historical corrections for Hong Kong.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-12">
-  <title>Release 8.3.12</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-10-04</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.11.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.12</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.8,
-    see the release notes for 8.3.8.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Use a separate interpreter for each calling SQL userid in PL/Perl and
-      PL/Tcl (Tom Lane)
-     </para>
-
-     <para>
-      This change prevents security problems that can be caused by subverting
-      Perl or Tcl code that will be executed later in the same session under
-      another SQL user identity (for example, within a <literal>SECURITY
-      DEFINER</> function).  Most scripting languages offer numerous ways that
-      that might be done, such as redefining standard functions or operators
-      called by the target function.  Without this change, any SQL user with
-      Perl or Tcl language usage rights can do essentially anything with the
-      SQL privileges of the target function's owner.
-     </para>
-
-     <para>
-      The cost of this change is that intentional communication among Perl
-      and Tcl functions becomes more difficult.  To provide an escape hatch,
-      PL/PerlU and PL/TclU functions continue to use only one interpreter
-      per session.  This is not considered a security issue since all such
-      functions execute at the trust level of a database superuser already.
-     </para>
-
-     <para>
-      It is likely that third-party procedural languages that claim to offer
-      trusted execution have similar security issues.  We advise contacting
-      the authors of any PL you are depending on for security-critical
-      purposes.
-     </para>
-
-     <para>
-      Our thanks to Tim Bunce for pointing out this issue (CVE-2010-3433).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible crashes in <function>pg_get_expr()</> by disallowing
-      it from being called with an argument that is not one of the system
-      catalog columns it's intended to be used with
-      (Heikki Linnakangas, Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Treat exit code 128 (<literal>ERROR_WAIT_NO_CHILDREN</>) as non-fatal on
-      Windows (Magnus Hagander)
-     </para>
-
-     <para>
-      Under high load, Windows processes will sometimes fail at startup with
-      this error code.  Formerly the postmaster treated this as a panic
-      condition and restarted the whole database, but that seems to be
-      an overreaction.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect usage of non-strict OR joinclauses in Append indexscans
-      (Tom Lane)
-     </para>
-
-     <para>
-      This is a back-patch of an 8.4 fix that was missed in the 8.3 branch.
-      This corrects an error introduced in 8.3.8 that could cause incorrect
-      results for outer joins when the inner relation is an inheritance tree
-      or <literal>UNION ALL</> subquery.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible duplicate scans of <literal>UNION ALL</> member relations
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>cannot handle unplanned sub-select</quote> error (Tom Lane)
-     </para>
-
-     <para>
-      This occurred when a sub-select contains a join alias reference that
-      expands into an expression containing another sub-select.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix failure to mark cached plans as transient (Tom Lane)
-     </para>
-
-     <para>
-      If a plan is prepared while <command>CREATE INDEX CONCURRENTLY</> is
-      in progress for one of the referenced tables, it is supposed to be
-      re-planned once the index is ready for use.  This was not happening
-      reliably.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Reduce PANIC to ERROR in some occasionally-reported btree failure cases,
-      and provide additional detail in the resulting error messages
-      (Tom Lane)
-     </para>
-
-     <para>
-      This should improve the system's robustness with corrupted indexes.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent show_session_authorization() from crashing within autovacuum
-      processes (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Defend against functions returning setof record where not all the
-      returned rows are actually of the same rowtype (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible failure when hashing a pass-by-reference function result
-      (Tao Ma, Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve merge join's handling of NULLs in the join columns (Tom Lane)
-     </para>
-
-     <para>
-      A merge join can now stop entirely upon reaching the first NULL,
-      if the sort order is such that NULLs sort high.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Take care to fsync the contents of lockfiles (both
-      <filename>postmaster.pid</> and the socket lockfile) while writing them
-      (Tom Lane)
-     </para>
-
-     <para>
-      This omission could result in corrupted lockfile contents if the
-      machine crashes shortly after postmaster start.  That could in turn
-      prevent subsequent attempts to start the postmaster from succeeding,
-      until the lockfile is manually removed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid recursion while assigning XIDs to heavily-nested
-      subtransactions (Andres Freund, Robert Haas)
-     </para>
-
-     <para>
-      The original coding could result in a crash if there was limited
-      stack space.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid holding open old WAL segments in the walwriter process
-      (Magnus Hagander, Heikki Linnakangas)
-     </para>
-
-     <para>
-      The previous coding would prevent removal of no-longer-needed segments.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <varname>log_line_prefix</>'s <literal>%i</> escape,
-      which could produce junk early in backend startup (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible data corruption in <command>ALTER TABLE ... SET
-      TABLESPACE</> when archiving is enabled (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow <command>CREATE DATABASE</> and <command>ALTER DATABASE ... SET
-      TABLESPACE</> to be interrupted by query-cancel (Guillaume Lelarge)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <command>REASSIGN OWNED</> to handle operator classes and families
-      (Asko Tiidumaa)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible core dump when comparing two empty <type>tsquery</> values
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>LIKE</>'s handling of patterns containing <literal>%</>
-      followed by <literal>_</> (Tom Lane)
-     </para>
-
-     <para>
-      We've fixed this before, but there were still some incorrectly-handled
-      cases.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In PL/Python, defend against null pointer results from
-      <function>PyCObject_AsVoidPtr</> and <function>PyCObject_FromVoidPtr</>
-      (Peter Eisentraut)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make psql recognize <command>DISCARD ALL</> as a command that should
-      not be encased in a transaction block in autocommit-off mode
-      (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</> to process data from <literal>RETURNING</>
-      clauses correctly (Michael Meskes)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <filename>contrib/dblink</>'s handling of tables containing
-      dropped columns (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix connection leak after <quote>duplicate connection name</quote>
-      errors in <filename>contrib/dblink</> (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/dblink</> to handle connection names longer than
-      62 bytes correctly (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <function>hstore(text, text)</>
-      function to <filename>contrib/hstore</> (Robert Haas)
-     </para>
-
-     <para>
-      This function is the recommended substitute for the now-deprecated
-      <literal>=&gt;</> operator.  It was back-patched so that future-proofed
-      code can be used with older server versions.  Note that the patch will
-      be effective only after <filename>contrib/hstore</> is installed or
-      reinstalled in a particular database.  Users might prefer to execute
-      the <command>CREATE FUNCTION</> command by hand, instead.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update build infrastructure and documentation to reflect the source code
-      repository's move from CVS to Git (Magnus Hagander and others)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010l
-      for DST law changes in Egypt and Palestine; also historical corrections
-      for Finland.
-     </para>
-
-     <para>
-      This change also adds new names for two Micronesian timezones:
-      Pacific/Chuuk is now preferred over Pacific/Truk (and the preferred
-      abbreviation is CHUT not TRUT) and Pacific/Pohnpei is preferred over
-      Pacific/Ponape.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make Windows' <quote>N. Central Asia Standard Time</> timezone map to
-      Asia/Novosibirsk, not Asia/Almaty (Magnus Hagander)
-     </para>
-
-     <para>
-      Microsoft changed the DST behavior of this zone in the timezone update
-      from KB976098. Asia/Novosibirsk is a better match to its new behavior.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-11">
-  <title>Release 8.3.11</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-05-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.10.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.11</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.8,
-    see the release notes for 8.3.8.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Enforce restrictions in <literal>plperl</> using an opmask applied to
-      the whole interpreter, instead of using <filename>Safe.pm</>
-      (Tim Bunce, Andrew Dunstan)
-     </para>
-
-     <para>
-      Recent developments have convinced us that <filename>Safe.pm</> is too
-      insecure to rely on for making <literal>plperl</> trustable.  This
-      change removes use of <filename>Safe.pm</> altogether, in favor of using
-      a separate interpreter with an opcode mask that is always applied.
-      Pleasant side effects of the change include that it is now possible to
-      use Perl's <literal>strict</> pragma in a natural way in
-      <literal>plperl</>, and that Perl's <literal>$a</> and <literal>$b</>
-      variables work as expected in sort routines, and that function
-      compilation is significantly faster.  (CVE-2010-1169)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent PL/Tcl from executing untrustworthy code from
-      <structname>pltcl_modules</> (Tom)
-     </para>
-
-     <para>
-      PL/Tcl's feature for autoloading Tcl code from a database table
-      could be exploited for trojan-horse attacks, because there was no
-      restriction on who could create or insert into that table.  This change
-      disables the feature unless <structname>pltcl_modules</> is owned by a
-      superuser.  (However, the permissions on the table are not checked, so
-      installations that really need a less-than-secure modules table can
-      still grant suitable privileges to trusted non-superusers.)  Also,
-      prevent loading code into the unrestricted <quote>normal</> Tcl
-      interpreter unless we are really going to execute a <literal>pltclu</>
-      function.  (CVE-2010-1170)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash if a cache reset message is received during
-      rebuild of a relcache entry (Heikki)
-     </para>
-
-     <para>
-      This error was introduced in 8.3.10 while fixing a related failure.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Apply per-function GUC settings while running the language validator
-      for the function (Itagaki Takahiro)
-     </para>
-
-     <para>
-      This avoids failures if the function's code is invalid without the
-      setting; an example is that SQL functions may not parse if the
-      <varname>search_path</> is not correct.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not allow an unprivileged user to reset superuser-only parameter
-      settings (Alvaro)
-     </para>
-
-     <para>
-      Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
-      ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
-      a database he owns, this would remove all special parameter settings
-      for the user or database, even ones that are only supposed to be
-      changeable by a superuser.  Now, the <command>ALTER</> will only
-      remove the parameters that the user has permission to change.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crash during backend shutdown if shutdown occurs
-      when a <literal>CONTEXT</> addition would be made to log entries (Tom)
-     </para>
-
-     <para>
-      In some cases the context-printing function would fail because the
-      current transaction had already been rolled back when it came time
-      to print a log message.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure the archiver process responds to changes in
-      <varname>archive_command</> as soon as possible (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update pl/perl's <filename>ppport.h</> for modern Perl versions
-      (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite recursion in <application>psql</> when expanding
-      a variable that refers to itself (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>psql</>'s <literal>\copy</> to not add spaces around
-      a dot within <literal>\copy (select ...)</> (Tom)
-     </para>
-
-     <para>
-      Addition of spaces around the decimal point in a numeric literal would
-      result in a syntax error.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix unnecessary <quote>GIN indexes do not support whole-index scans</>
-      errors for unsatisfiable queries using <filename>contrib/intarray</>
-      operators (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
-      interrupts promptly (Tatsuhito Kasahara)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make server startup deal properly with the case that
-      <function>shmget()</> returns <literal>EINVAL</> for an existing
-      shared memory segment (Tom)
-     </para>
-
-     <para>
-      This behavior has been observed on BSD-derived kernels including OS X.
-      It resulted in an entirely-misleading startup failure complaining that
-      the shared memory request size was too large.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crashes in syslogger process on Windows (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Deal more robustly with incomplete time zone information in the
-      Windows registry (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update the set of known Windows time zone names (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010j
-      for DST law changes in Argentina, Australian Antarctic, Bangladesh,
-      Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia;
-      also historical corrections for Taiwan.
-     </para>
-
-     <para>
-      Also, add <literal>PKST</> (Pakistan Summer Time) to the default set of
-      timezone abbreviations.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-10">
-  <title>Release 8.3.10</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-03-15</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.9.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.10</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.8,
-    see the release notes for 8.3.8.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Add new configuration parameter <varname>ssl_renegotiation_limit</> to
-      control how often we do session key renegotiation for an SSL connection
-      (Magnus)
-     </para>
-
-     <para>
-      This can be set to zero to disable renegotiation completely, which may
-      be required if a broken SSL library is used.  In particular, some
-      vendors are shipping stopgap patches for CVE-2009-3555 that cause
-      renegotiation attempts to fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible deadlock during backend startup (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes due to not handling errors during relcache reload
-      cleanly (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash due to use of dangling pointer to a cached plan
-      (Tatsuo)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes when trying to recover from a failure in
-      subtransaction start (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix server memory leak associated with use of savepoints and a client
-      encoding different from server's encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect WAL data emitted during end-of-recovery cleanup of a GIST
-      index page split (Yoichi Hirai)
-     </para>
-
-     <para>
-      This would result in index corruption, or even more likely an error
-      during WAL replay, if we were unlucky enough to crash during
-      end-of-recovery cleanup after having completed an incomplete GIST
-      insertion.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>substring()</> for <type>bit</> types treat any negative
-      length as meaning <quote>all the rest of the string</> (Tom)
-     </para>
-
-     <para>
-      The previous coding treated only -1 that way, and would produce an
-      invalid result value for other negative values, possibly leading to
-      a crash (CVE-2010-0442).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix integer-to-bit-string conversions to handle the first fractional
-      byte correctly when the output bit width is wider than the given
-      integer by something other than a multiple of 8 bits (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some cases of pathologically slow regular expression matching (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted crashes in <type>xml</> processing caused by sloppy
-      memory management (Tom)
-     </para>
-
-     <para>
-      This is a back-patch of changes first applied in 8.4.  The 8.3 code
-      was known buggy, but the new code was sufficiently different to not
-      want to back-patch it until it had gotten some field testing.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug with trying to update a field of an element of a
-      composite-type array column (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix the <literal>STOP WAL LOCATION</> entry in backup history files to
-      report the next WAL segment's name when the end location is exactly at a
-      segment boundary (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some more cases of temporary-file leakage (Heikki)
-     </para>
-
-     <para>
-      This corrects a problem introduced in the previous minor release.
-      One case that failed is when a plpgsql function returning set is
-      called within another function's exception handler.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve constraint exclusion processing of boolean-variable cases,
-      in particular make it possible to exclude a partition that has a
-      <quote>bool_column = false</> constraint (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      When reading <filename>pg_hba.conf</> and related files, do not treat
-      <literal>@something</> as a file inclusion request if the <literal>@</>
-      appears inside quote marks; also, never treat <literal>@</> by itself
-      as a file inclusion request (Tom)
-     </para>
-
-     <para>
-      This prevents erratic behavior if a role or database name starts with
-      <literal>@</>.  If you need to include a file whose path name
-      contains spaces, you can still do so, but you must write
-      <literal>@"/path to/file"</> rather than putting the quotes around
-      the whole construct.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite loop on some platforms if a directory is named as
-      an inclusion target in <filename>pg_hba.conf</> and related files
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible infinite loop if <function>SSL_read</> or
-      <function>SSL_write</> fails without setting <varname>errno</> (Tom)
-     </para>
-
-     <para>
-      This is reportedly possible with some Windows versions of
-      <application>openssl</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <acronym>GSSAPI</> authentication on local connections,
-      since it requires a hostname to function correctly (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <application>ecpg</> report the proper SQLSTATE if the connection
-      disappears (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>psql</>'s <literal>numericlocale</> option to not
-      format strings it shouldn't in latex and troff output formats (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <application>psql</> return the correct exit status (3) when
-      <literal>ON_ERROR_STOP</> and <literal>--single-transaction</> are
-      both specified and an error occurs during the implied <command>COMMIT</>
-      (Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix plpgsql failure in one case where a composite column is set to NULL
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible failure when calling PL/Perl functions from PL/PerlU
-      or vice versa (Tim Bunce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>volatile</> markings in PL/Python to avoid possible
-      compiler-specific misbehavior (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
-     </para>
-
-     <para>
-      The only known symptom of this oversight is that the Tcl
-      <literal>clock</> command misbehaves if using Tcl 8.5 or later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent crash in <filename>contrib/dblink</> when too many key
-      columns are specified to a <function>dblink_build_sql_*</> function
-      (Rushabh Lathia, Joe Conway)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow zero-dimensional arrays in <filename>contrib/ltree</> operations
-      (Tom)
-     </para>
-
-     <para>
-      This case was formerly rejected as an error, but it's more convenient to
-      treat it the same as a zero-element array.  In particular this avoids
-      unnecessary failures when an <type>ltree</> operation is applied to the
-      result of <literal>ARRAY(SELECT ...)</> and the sub-select returns no
-      rows.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted crashes in <filename>contrib/xml2</> caused by sloppy
-      memory management (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make building of <filename>contrib/xml2</> more robust on Windows
-      (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix race condition in Windows signal handling (Radu Ilie)
-     </para>
-
-     <para>
-      One known symptom of this bug is that rows in <structname>pg_listener</>
-      could be dropped under heavy load.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010e
-      for DST law changes in Bangladesh, Chile, Fiji, Mexico, Paraguay, Samoa.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-9">
-  <title>Release 8.3.9</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2009-12-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.8.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.9</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.8,
-    see the release notes for 8.3.8.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Protect against indirect security threats caused by index functions
-      changing session-local state (Gurjeet Singh, Tom)
-     </para>
-
-     <para>
-      This change prevents allegedly-immutable index functions from possibly
-      subverting a superuser's session (CVE-2009-4136).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Reject SSL certificates containing an embedded null byte in the common
-      name (CN) field (Magnus)
-     </para>
-
-     <para>
-      This prevents unintended matching of a certificate to a server or client
-      name during SSL validation (CVE-2009-4034).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash during backend-startup-time cache initialization (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid crash on empty thesaurus dictionary (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent signals from interrupting <literal>VACUUM</> at unsafe times
-      (Alvaro)
-     </para>
-
-     <para>
-      This fix prevents a PANIC if a <literal>VACUUM FULL</> is cancelled
-      after it's already committed its tuple movements, as well as transient
-      errors if a plain <literal>VACUUM</> is interrupted after having
-      truncated the table.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash due to integer overflow in hash table size
-      calculation (Tom)
-     </para>
-
-     <para>
-      This could occur with extremely large planner estimates for the size of
-      a hashjoin's result.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix very rare crash in <type>inet</>/<type>cidr</> comparisons (Chris
-      Mikkelson)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that shared tuple-level locks held by prepared transactions are
-      not ignored (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix premature drop of temporary files used for a cursor that is accessed
-      within a subtransaction (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak in syslogger process when rotating to a new CSV logfile
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix Windows permission-downgrade logic (Jesse Morris)
-     </para>
-
-     <para>
-      This fixes some cases where the database failed to start on Windows,
-      often with misleading error messages such as <quote>could not locate
-      matching postgres executable</quote>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect logic for GiST index page splits, when the split depends
-      on a non-first column of the index (Paul Ramsey)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Don't error out if recycling or removing an old WAL file fails at the
-      end of checkpoint (Heikki)
-     </para>
-
-     <para>
-      It's better to treat the problem as non-fatal and allow the checkpoint
-      to complete.  Future checkpoints will retry the removal.  Such problems
-      are not expected in normal operation, but have been seen to be
-      caused by misdesigned Windows anti-virus and backup software.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure WAL files aren't repeatedly archived on Windows (Heikki)
-     </para>
-
-     <para>
-      This is another symptom that could happen if some other process
-      interfered with deletion of a no-longer-needed file.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PAM password processing to be more robust (Tom)
-     </para>
-
-     <para>
-      The previous code is known to fail with the combination of the Linux
-      <literal>pam_krb5</> PAM module with Microsoft Active Directory as the
-      domain controller.  It might have problems elsewhere too, since it was
-      making unjustified assumptions about what arguments the PAM stack would
-      pass to it.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Raise the maximum authentication token (Kerberos ticket) size in GSSAPI
-      and SSPI authentication methods (Ian Turner)
-     </para>
-
-     <para>
-      While the old 2000-byte limit was more than enough for Unix Kerberos
-      implementations, tickets issued by Windows Domain Controllers can be
-      much larger.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Re-enable collection of access statistics for sequences (Akira Kurosawa)
-     </para>
-
-     <para>
-      This used to work but was broken in 8.3.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix processing of ownership dependencies during <literal>CREATE OR
-      REPLACE FUNCTION</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect handling of <literal>WHERE</>
-      <replaceable>x</>=<replaceable>x</> conditions (Tom)
-     </para>
-
-     <para>
-      In some cases these could get ignored as redundant, but they aren't
-      &mdash; they're equivalent to <replaceable>x</> <literal>IS NOT NULL</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make text search parser accept underscores in XML attributes (Peter)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix encoding handling in <type>xml</> binary input (Heikki)
-     </para>
-
-     <para>
-      If the XML header doesn't specify an encoding, we now assume UTF-8 by
-      default; the previous handling was inconsistent.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug with calling <literal>plperl</> from <literal>plperlu</> or vice
-      versa (Tom)
-     </para>
-
-     <para>
-      An error exit from the inner function could result in crashes due to
-      failure to re-select the correct Perl interpreter for the outer function.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix session-lifespan memory leak when a PL/Perl function is redefined
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that Perl arrays are properly converted to
-      <productname>PostgreSQL</> arrays when returned by a set-returning
-      PL/Perl function (Andrew Dunstan, Abhijit Menon-Sen)
-     </para>
-
-     <para>
-      This worked correctly already for non-set-returning functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix rare crash in exception processing in PL/Python (Peter)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In <filename>contrib/pg_standby</>, disable triggering failover with a
-      signal on Windows (Fujii Masao)
-     </para>
-
-     <para>
-      This never did anything useful, because Windows doesn't have Unix-style
-      signals, but recent changes made it actually crash.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <application>psql</>'s flex module is compiled with the correct
-      system header definitions (Tom)
-     </para>
-
-     <para>
-      This fixes build failures on platforms where
-      <literal>--enable-largefile</> causes incompatible changes in the
-      generated code.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make the postmaster ignore any <literal>application_name</> parameter in
-      connection request packets, to improve compatibility with future libpq
-      versions (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update the timezone abbreviation files to match current reality (Joachim
-      Wieland)
-     </para>
-
-     <para>
-      This includes adding <literal>IDT</> and <literal>SGT</> to the default
-      timezone abbreviation set.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009s
-      for DST law changes in Antarctica, Argentina, Bangladesh, Fiji,
-      Novokuznetsk, Pakistan, Palestine, Samoa, Syria; also historical
-      corrections for Hong Kong.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-8">
-  <title>Release 8.3.8</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2009-09-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.7.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.8</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you have any hash indexes on <type>interval</> columns,
-    you must <command>REINDEX</> them after updating to 8.3.8.
-    Also, if you are upgrading from a version earlier than 8.3.5,
-    see the release notes for 8.3.5.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix Windows shared-memory allocation code (Tsutomu Yamada, Magnus)
-     </para>
-
-     <para>
-      This bug led to the often-reported <quote>could not reattach
-      to shared memory</> error message.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Force WAL segment switch during <function>pg_start_backup()</>
-      (Heikki)
-     </para>
-
-     <para>
-      This avoids corner cases that could render a base backup unusable.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>RESET ROLE</> and <command>RESET SESSION
-      AUTHORIZATION</> inside security-definer functions (Tom, Heikki)
-     </para>
-
-     <para>
-      This covers a case that was missed in the previous patch that
-      disallowed <command>SET ROLE</> and <command>SET SESSION
-      AUTHORIZATION</> inside security-definer functions.
-      (See CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>LOAD</> of an already-loaded loadable module
-      into a no-op (Tom)
-     </para>
-
-     <para>
-      Formerly, <command>LOAD</> would attempt to unload and re-load the
-      module, but this is unsafe and not all that useful.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow empty passwords during LDAP authentication (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix handling of sub-SELECTs appearing in the arguments of
-      an outer-level aggregate function (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bugs associated with fetching a whole-row value from the
-      output of a Sort or Materialize plan node (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent <varname>synchronize_seqscans</> from changing the results of
-      scrollable and <literal>WITH HOLD</> cursors (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Revert planner change that disabled partial-index and constraint
-      exclusion optimizations when there were more than 100 clauses in
-      an AND or OR list (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix hash calculation for data type <type>interval</> (Tom)
-     </para>
-
-     <para>
-      This corrects wrong results for hash joins on interval values.
-      It also changes the contents of hash indexes on interval columns.
-      If you have any such indexes, you must <command>REINDEX</> them
-      after updating.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Treat <function>to_char(..., 'TH')</> as an uppercase ordinal
-      suffix with <literal>'HH'</>/<literal>'HH12'</> (Heikki)
-     </para>
-
-     <para>
-      It was previously handled as <literal>'th'</> (lowercase).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix overflow for <literal>INTERVAL '<replaceable>x</> ms'</literal>
-      when <replaceable>x</> is more than 2 million and integer
-      datetimes are in use (Alex Hunsaker)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix calculation of distance between a point and a line segment (Tom)
-     </para>
-
-     <para>
-      This led to incorrect results from a number of geometric operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <type>money</> data type to work in locales where currency
-      amounts have no fractional digits, e.g. Japan (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>LIKE</> for case where pattern contains <literal>%_</>
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Properly round datetime input like
-      <literal>00:12:57.9999999999999999999999999999</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leaks in XML operations (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix poor choice of page split point in GiST R-tree operator classes
-      (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that a <quote>fast shutdown</> request will forcibly terminate
-      open sessions, even if a <quote>smart shutdown</> was already in progress
-      (Fujii Masao)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid performance degradation in bulk inserts into GIN indexes
-      when the input values are (nearly) in sorted order (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Correctly enforce NOT NULL domain constraints in some contexts in
-      PL/pgSQL (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix portability issues in plperl initialization (Andrew Dunstan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to not go into an infinite loop if
-      <filename>postgresql.conf</> is empty (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <application>pg_dump</>'s efficiency when there are
-      many large objects (Tamas Vincze)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Use <literal>SIGUSR1</>, not <literal>SIGQUIT</>, as the
-      failover signal for <application>pg_standby</> (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <application>pg_standby</>'s <literal>maxretries</> option
-      behave as documented (Fujii Masao)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <filename>contrib/hstore</> throw an error when a key or
-      value is too long to fit in its data structure, rather than
-      silently truncating it (Andrew Gierth)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/xml2</>'s <function>xslt_process()</> to
-      properly handle the maximum number of parameters (twenty) (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve robustness of <application>libpq</>'s code to recover
-      from errors during <command>COPY FROM STDIN</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid including conflicting readline and editline header files
-      when both libraries are installed (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009l
-      for DST law changes in Bangladesh, Egypt, Jordan, Pakistan,
-      Argentina/San_Luis, Cuba, Jordan (historical correction only),
-      Mauritius, Morocco, Palestine, Syria, Tunisia.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-7">
-  <title>Release 8.3.7</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2009-03-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.6.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.7</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.5,
-    see the release notes for 8.3.5.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent error recursion crashes when encoding conversion fails (Tom)
-     </para>
-
-     <para>
-      This change extends fixes made in the last two minor releases for
-      related failure scenarios.  The previous fixes were narrowly tailored
-      for the original problem reports, but we have now recognized that
-      <emphasis>any</> error thrown by an encoding conversion function could
-      potentially lead to infinite recursion while trying to report the
-      error.  The solution therefore is to disable translation and encoding
-      conversion and report the plain-ASCII form of any error message,
-      if we find we have gotten into a recursive error reporting situation.
-      (CVE-2009-0922)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>CREATE CONVERSION</> with the wrong encodings
-      for the specified conversion function (Heikki)
-     </para>
-
-     <para>
-      This prevents one possible scenario for encoding conversion failure.
-      The previous change is a backstop to guard against other kinds of
-      failures in the same area.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <function>xpath()</> to not modify the path expression unless
-      necessary, and to make a saner attempt at it when necessary (Andrew)
-     </para>
-
-     <para>
-      The SQL standard suggests that <function>xpath</> should work on data
-      that is a document fragment, but <application>libxml</> doesn't support
-      that, and indeed it's not clear that this is sensible according to the
-      XPath standard.  <function>xpath</> attempted to work around this
-      mismatch by modifying both the data and the path expression, but the
-      modification was buggy and could cause valid searches to fail.  Now,
-      <function>xpath</> checks whether the data is in fact a well-formed
-      document, and if so invokes <application>libxml</> with no change to the
-      data or path expression.  Otherwise, a different modification method
-      that is somewhat less likely to fail is used.
-     </para>
-
-     <note>
-      <para>
-       The new modification method is still not 100% satisfactory, and it
-       seems likely that no real solution is possible.  This patch should
-       therefore be viewed as a band-aid to keep from breaking existing
-       applications unnecessarily.  It is likely that
-       <productname>PostgreSQL</> 8.4 will simply reject use of
-       <function>xpath</> on data that is not a well-formed document.
-      </para>
-     </note>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix core dump when <function>to_char()</> is given format codes that
-      are inappropriate for the type of the data argument (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible failure in text search when C locale is used with
-      a multi-byte encoding (Teodor)
-     </para>
-
-     <para>
-      Crashes were possible on platforms where <type>wchar_t</> is narrower
-      than <type>int</>; Windows in particular.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix extreme inefficiency in text search parser's handling of an
-      email-like string containing multiple <literal>@</> characters (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner problem with sub-<command>SELECT</> in the output list
-      of a larger subquery (Tom)
-     </para>
-
-     <para>
-      The known symptom of this bug is a <quote>failed to locate grouping
-      columns</> error that is dependent on the datatype involved;
-      but there could be other issues as well.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix decompilation of <literal>CASE WHEN</> with an implicit coercion
-      (Tom)
-     </para>
-
-     <para>
-      This mistake could lead to Assert failures in an Assert-enabled build,
-      or an <quote>unexpected CASE WHEN clause</> error message in other
-      cases, when trying to examine or dump a view.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible misassignment of the owner of a TOAST table's rowtype (Tom)
-     </para>
-
-     <para>
-      If <command>CLUSTER</> or a rewriting variant of <command>ALTER TABLE</>
-      were executed by someone other than the table owner, the
-      <structname>pg_type</> entry for the table's TOAST table would end up
-      marked as owned by that someone.  This caused no immediate problems,
-      since the permissions on the TOAST rowtype aren't examined by any
-      ordinary database operation.  However, it could lead to unexpected
-      failures if one later tried to drop the role that issued the command
-      (in 8.1 or 8.2), or <quote>owner of data type appears to be invalid</>
-      warnings from <application>pg_dump</> after having done so (in 8.3).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Change <command>UNLISTEN</> to exit quickly if the current session has
-      never executed any <command>LISTEN</> command (Tom)
-     </para>
-
-     <para>
-      Most of the time this is not a particularly useful optimization, but
-      since <command>DISCARD ALL</> invokes <command>UNLISTEN</>, the previous
-      coding caused a substantial performance problem for applications that
-      made heavy use of <command>DISCARD ALL</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/pgSQL to not treat <literal>INTO</> after <command>INSERT</> as
-      an INTO-variables clause anywhere in the string, not only at the start;
-      in particular, don't fail for <command>INSERT INTO</> within
-      <command>CREATE RULE</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Clean up PL/pgSQL error status variables fully at block exit
-      (Ashesh Vashi and Dave Page)
-     </para>
-
-     <para>
-      This is not a problem for PL/pgSQL itself, but the omission could cause
-      the PL/pgSQL Debugger to crash while examining the state of a function.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Retry failed calls to <function>CallNamedPipe()</> on Windows
-      (Steve Marshall, Magnus)
-     </para>
-
-     <para>
-      It appears that this function can sometimes fail transiently;
-      we previously treated any failure as a hard error, which could
-      confuse <command>LISTEN</>/<command>NOTIFY</> as well as other
-      operations.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>MUST</> (Mauritius Island Summer Time) to the default list
-      of known timezone abbreviations (Xavier Bugaud)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-6">
-  <title>Release 8.3.6</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2009-02-02</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.5.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.6</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.5,
-    see the release notes for 8.3.5.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Make <command>DISCARD ALL</> release advisory locks, in addition
-      to everything it already did (Tom)
-     </para>
-
-     <para>
-      This was decided to be the most appropriate behavior.  This could
-      affect existing applications, however.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix whole-index GiST scans to work correctly (Teodor)
-     </para>
-
-     <para>
-      This error could cause rows to be lost if a table is clustered
-      on a GiST index.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash of <literal>xmlconcat(NULL)</> (Peter)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash in <literal>ispell</> dictionary if high-bit-set
-      characters are used as flags (Teodor)
-     </para>
-
-     <para>
-      This is known to be done by one widely available Norwegian dictionary,
-      and the same condition may exist in others.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix misordering of <application>pg_dump</> output for composite types
-      (Tom)
-     </para>
-
-     <para>
-      The most likely problem was for user-defined operator classes to
-      be dumped after indexes or views that needed them.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve handling of URLs in <function>headline()</> function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve handling of overlength headlines in <function>headline()</>
-      function (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible Assert failure or misconversion if an encoding
-      conversion is created with the wrong conversion function for the
-      specified pair of encodings (Tom, Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible Assert failure if a statement executed in PL/pgSQL is
-      rewritten into another kind of statement, for example if an
-      <command>INSERT</> is rewritten into an <command>UPDATE</> (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that a snapshot is available to datatype input functions (Tom)
-     </para>
-
-     <para>
-      This primarily affects domains that are declared with <literal>CHECK</>
-      constraints involving user-defined stable or immutable functions.  Such
-      functions typically fail if no snapshot has been set.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make it safer for SPI-using functions to be used within datatype I/O;
-      in particular, to be used in domain check constraints (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unnecessary locking of small tables in <command>VACUUM</>
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a problem that sometimes kept <command>ALTER TABLE ENABLE/DISABLE
-      RULE</> from being recognized by active sessions (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a problem that made <literal>UPDATE RETURNING tableoid</>
-      return zero instead of the correct OID (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow functions declared as taking <type>ANYARRAY</> to work on
-      the <structname>pg_statistic</> columns of that type (Tom)
-     </para>
-
-     <para>
-      This used to work, but was unintentionally broken in 8.3.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner misestimation of selectivity when transitive equality
-      is applied to an outer-join clause (Tom)
-     </para>
-
-     <para>
-      This could result in bad plans for queries like
-      <literal>... from a left join b on a.a1 = b.b1 where a.a1 = 42 ...</>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve optimizer's handling of long <literal>IN</> lists (Tom)
-     </para>
-
-     <para>
-      This change avoids wasting large amounts of time on such lists
-      when constraint exclusion is enabled.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent synchronous scan during GIN index build (Tom)
-     </para>
-
-     <para>
-      Because GIN is optimized for inserting tuples in increasing TID order,
-      choosing to use a synchronous scan could slow the build by a factor of
-      three or more.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that the contents of a holdable cursor don't depend on the
-      contents of TOAST tables (Tom)
-     </para>
-
-     <para>
-      Previously, large field values in a cursor result might be represented
-      as TOAST pointers, which would fail if the referenced table got dropped
-      before the cursor is read, or if the large value is deleted and then
-      vacuumed away.  This cannot happen with an ordinary cursor,
-      but it could with a cursor that is held past its creating transaction.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak when a set-returning function is terminated without
-      reading its whole result (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix encoding conversion problems in XML functions when the database
-      encoding isn't UTF-8 (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/dblink</>'s
-      <function>dblink_get_result(text,bool)</> function (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible garbage output from <filename>contrib/sslinfo</> functions
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect behavior of <filename>contrib/tsearch2</> compatibility
-      trigger when it's fired more than once in a command (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible mis-signaling in autovacuum (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Support running as a service on Windows 7 beta (Dave and Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</>'s handling of varchar structs (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>configure</> script to properly report failure when
-      unable to obtain linkage information for PL/Perl (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make all documentation reference <literal>pgsql-bugs</> and/or
-      <literal>pgsql-hackers</> as appropriate, instead of the
-      now-decommissioned <literal>pgsql-ports</> and <literal>pgsql-patches</>
-      mailing lists (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009a (for
-      Kathmandu and historical DST corrections in Switzerland, Cuba)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-5">
-  <title>Release 8.3.5</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2008-11-03</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.4.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.5</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.1,
-    see the release notes for 8.3.1.  Also, if you were running a previous
-    8.3.X release, it is recommended to <command>REINDEX</> all GiST
-    indexes after the upgrade.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix GiST index corruption due to marking the wrong index entry
-      <quote>dead</> after a deletion (Teodor)
-     </para>
-
-     <para>
-      This would result in index searches failing to find rows they
-      should have found.  Corrupted indexes can be fixed with
-      <command>REINDEX</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix backend crash when the client encoding cannot represent a localized
-      error message (Tom)
-     </para>
-
-     <para>
-      We have addressed similar issues before, but it would still fail if
-      the <quote>character has no equivalent</> message itself couldn't
-      be converted.  The fix is to disable localization and send the plain
-      ASCII error message when we detect such a situation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash in <type>bytea</>-to-XML mapping (Michael McMaster)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash when deeply nested functions are invoked from
-      a trigger (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve optimization of <replaceable>expression</> <literal>IN</>
-      (<replaceable>expression-list</>) queries (Tom, per an idea from Robert
-      Haas)
-     </para>
-
-     <para>
-      Cases in which there are query variables on the right-hand side had been
-      handled less efficiently in 8.2.x and 8.3.x than in prior versions.
-      The fix restores 8.1 behavior for such cases.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix mis-expansion of rule queries when a sub-<literal>SELECT</> appears
-      in a function call in <literal>FROM</>,  a multi-row <literal>VALUES</>
-      list, or a <literal>RETURNING</> list (Tom)
-     </para>
-
-     <para>
-      The usual symptom of this problem is an <quote>unrecognized node type</>
-      error.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix Assert failure during rescan of an <literal>IS NULL</>
-      search of a GiST index (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak during rescan of a hashed aggregation plan (Neil)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure an error is reported when a newly-defined PL/pgSQL trigger
-      function is invoked as a normal function (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Force a checkpoint before <command>CREATE DATABASE</> starts to copy
-      files (Heikki)
-     </para>
-
-     <para>
-      This prevents a possible failure if files had recently been deleted
-      in the source database.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible collision of <structfield>relfilenode</> numbers
-      when moving a table to another tablespace with <command>ALTER SET
-      TABLESPACE</> (Heikki)
-     </para>
-
-     <para>
-      The command tried to re-use the existing filename, instead of
-      picking one that is known unused in the destination directory.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect text search headline generation when single query
-      item matches first word of text (Sushant Sinha)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix improper display of fractional seconds in interval values when
-      using a non-ISO datestyle in an <option>--enable-integer-datetimes</>
-      build (Ron Mayer)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <literal>ILIKE</> compare characters case-insensitively
-      even when they're escaped (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <command>DISCARD</> is handled properly by statement logging (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect logging of last-completed-transaction time during
-      PITR recovery (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <function>SPI_getvalue</> and <function>SPI_getbinval</>
-      behave correctly when the passed tuple and tuple descriptor have
-      different numbers of columns (Tom)
-     </para>
-
-     <para>
-      This situation is normal when a table has had columns added or removed,
-      but these two functions didn't handle it properly.
-      The only likely consequence is an incorrect error indication.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Mark <varname>SessionReplicationRole</> as <literal>PGDLLIMPORT</>
-      so it can be used by <application>Slony</> on Windows (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix small memory leak when using <application>libpq</>'s
-      <literal>gsslib</> parameter (Magnus)
-     </para>
-
-     <para>
-      The space used by the parameter string was not freed at connection
-      close.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <application>libgssapi</> is linked into <application>libpq</>
-      if needed (Markus Schaaf)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</>'s parsing of <command>CREATE ROLE</> (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix recent breakage of <literal>pg_ctl restart</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <filename>pg_control</> is opened in binary mode
-      (Itagaki Takahiro)
-     </para>
-
-     <para>
-      <application>pg_controldata</> and <application>pg_resetxlog</>
-      did this incorrectly, and so could fail on Windows.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008i (for
-      DST law changes in Argentina, Brazil, Mauritius, Syria)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-4">
-  <title>Release 8.3.4</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2008-09-22</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.3.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.4</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.1,
-    see the release notes for 8.3.1.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix bug in btree WAL recovery code (Heikki)
-     </para>
-
-     <para>
-      Recovery failed if the WAL ended partway through a page split operation.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential use of wrong cutoff XID for HOT page pruning (Alvaro)
-     </para>
-
-     <para>
-      This error created a risk of corruption in system
-      catalogs that are consulted by <command>VACUUM</>: dead tuple versions
-      might be removed too soon.  The impact of this on actual database
-      operations would be minimal, since the system doesn't follow MVCC
-      rules while examining catalogs, but it might result in transiently
-      wrong output from <application>pg_dump</> or other client programs.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential miscalculation of <structfield>datfrozenxid</> (Alvaro)
-     </para>
-
-     <para>
-      This error may explain some recent reports of failure to remove old
-      <structname>pg_clog</> data.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect HOT updates after <structname>pg_class</> is reindexed
-      (Tom)
-     </para>
-
-     <para>
-      Corruption of <structname>pg_class</> could occur if <literal>REINDEX
-      TABLE pg_class</> was followed in the same session by an <literal>ALTER
-      TABLE RENAME</> or <literal>ALTER TABLE SET SCHEMA</> command.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix missed <quote>combo cid</> case (Karl Schnaitter)
-     </para>
-
-     <para>
-      This error made rows incorrectly invisible to a transaction in which they
-      had been deleted by multiple subtransactions that all aborted.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent autovacuum from crashing if the table it's currently
-      checking is deleted at just the wrong time (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Widen local lock counters from 32 to 64 bits (Tom)
-     </para>
-
-     <para>
-      This responds to reports that the counters could overflow in
-      sufficiently long transactions, leading to unexpected <quote>lock is
-      already held</> errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible duplicate output of tuples during a GiST index scan (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Regenerate foreign key checking queries from scratch when either
-      table is modified (Tom)
-     </para>
-
-     <para>
-      Previously, 8.3 would attempt to replan the query, but would work from
-      previously generated query text.  This led to failures if a
-      table or column was renamed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix missed permissions checks when a view contains a simple
-      <literal>UNION ALL</> construct (Heikki)
-     </para>
-
-     <para>
-      Permissions for the referenced tables were checked properly, but not
-      permissions for the view itself.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add checks in executor startup to ensure that the tuples produced by an
-      <command>INSERT</> or <command>UPDATE</> will match the target table's
-      current rowtype (Tom)
-     </para>
-
-     <para>
-      This situation is believed to be impossible in 8.3, but it can happen in
-      prior releases, so a check seems prudent.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible repeated drops during <command>DROP OWNED</> (Tom)
-     </para>
-
-     <para>
-      This would typically result in strange errors such as <quote>cache
-      lookup failed for relation NNN</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix several memory leaks in XML operations (Kris Jurka, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <function>xmlserialize()</> to raise error properly for
-      unacceptable target data type (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a couple of places that mis-handled multibyte characters in text
-      search configuration file parsing (Tom)
-     </para>
-
-     <para>
-      Certain characters occurring in configuration files would always cause
-      <quote>invalid byte sequence for encoding</> failures.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Provide file name and line number location for all errors reported
-      in text search configuration files (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>AT TIME ZONE</> to first try to interpret its timezone
-      argument as a timezone abbreviation, and only try it as a full timezone
-      name if that fails, rather than the other way around as formerly (Tom)
-     </para>
-
-     <para>
-      The timestamp input functions have always resolved ambiguous zone names
-      in this order.  Making <literal>AT TIME ZONE</> do so as well improves
-      consistency, and fixes a compatibility bug introduced in 8.1:
-      in ambiguous cases we now behave the same as 8.0 and before did,
-      since in the older versions <literal>AT TIME ZONE</> accepted
-      <emphasis>only</> abbreviations.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix datetime input functions to correctly detect integer overflow when
-      running on a 64-bit platform (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent integer overflows during units conversion when displaying a
-      configuration parameter that has units (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve performance of writing very long log messages to syslog (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow spaces in the suffix part of an LDAP URL in
-      <filename>pg_hba.conf</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in backwards scanning of a cursor on a <literal>SELECT DISTINCT
-      ON</> query (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner bug that could improperly push down <literal>IS NULL</>
-      tests below an outer join (Tom)
-     </para>
-
-     <para>
-      This was triggered by occurrence of <literal>IS NULL</> tests for
-      the same relation in all arms of an upper <literal>OR</> clause.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner bug with nested sub-select expressions (Tom)
-     </para>
-
-     <para>
-      If the outer sub-select has no direct dependency on the parent query,
-      but the inner one does, the outer value might not get recalculated
-      for new parent query rows.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner to estimate that <literal>GROUP BY</> expressions yielding
-      boolean results always result in two groups, regardless of the
-      expressions' contents (Tom)
-     </para>
-
-     <para>
-      This is very substantially more accurate than the regular <literal>GROUP
-      BY</> estimate for certain boolean tests like <replaceable>col</>
-      <literal>IS NULL</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/pgSQL to not fail when a <literal>FOR</> loop's target variable
-      is a record containing composite-type fields (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Tcl to behave correctly with Tcl 8.5, and to be more careful
-      about the encoding of data sent to or from Tcl (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve performance of <function>PQescapeBytea()</> (Rudolf Leitgeb)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      On Windows, work around a Microsoft bug by preventing
-      <application>libpq</> from trying to send more than 64kB per system call
-      (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</> to handle variables properly in <command>SET</>
-      commands (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <application>pg_dump</> and <application>pg_restore</>'s
-      error reporting after failure to send a SQL command (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to properly preserve postmaster
-      command-line arguments across a <literal>restart</> (Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix erroneous WAL file cutoff point calculation in
-      <application>pg_standby</> (Simon)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008f (for
-      DST law changes in Argentina, Bahamas, Brazil, Mauritius, Morocco,
-      Pakistan, Palestine, and Paraguay)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-3">
-  <title>Release 8.3.3</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2008-06-12</simpara>
-  </note>
-
-  <para>
-   This release contains one serious and one minor bug fix over 8.3.2.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.3</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.1,
-    see the release notes for 8.3.1.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Make <function>pg_get_ruledef()</> parenthesize negative constants (Tom)
-     </para>
-
-     <para>
-      Before this fix, a negative constant in a view or rule might be dumped
-      as, say, <literal>-42::integer</>, which is subtly incorrect: it should
-      be <literal>(-42)::integer</> due to operator precedence rules.
-      Usually this would make little difference, but it could interact with
-      another recent patch to cause
-      <productname>PostgreSQL</> to reject what had been a valid
-      <command>SELECT DISTINCT</> view query.  Since this could result in
-      <application>pg_dump</> output failing to reload, it is being treated
-      as a high-priority fix.  The only released versions in which dump
-      output is actually incorrect are 8.3.1 and 8.2.7.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>ALTER AGGREGATE ... OWNER TO</> update
-      <structname>pg_shdepend</> (Tom)
-     </para>
-
-     <para>
-      This oversight could lead to problems if the aggregate was later
-      involved in a <command>DROP OWNED</> or <command>REASSIGN OWNED</>
-      operation.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-2">
-  <title>Release 8.3.2</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>never released</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.1.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.2</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, if you are upgrading from a version earlier than 8.3.1,
-    see the release notes for 8.3.1.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix <literal>ERRORDATA_STACK_SIZE exceeded</literal> crash that
-      occurred on Windows when using UTF-8 database encoding and a different
-      client encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect archive truncation point calculation for the
-      <literal>%r</> macro in <varname>recovery_command</> parameters
-      (Simon)
-     </para>
-
-     <para>
-      This could lead to data loss if a warm-standby script relied on
-      <literal>%r</> to decide when to throw away WAL segment files.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <command>ALTER TABLE ADD COLUMN ... PRIMARY KEY</> so that the new
-      column is correctly checked to see if it's been initialized to all
-      non-nulls (Brendan Jurd)
-     </para>
-
-     <para>
-      Previous versions neglected to check this requirement at all.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <command>REASSIGN OWNED</> so that it works on procedural
-      languages too (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix problems with <command>SELECT FOR UPDATE/SHARE</> occurring as a
-      subquery in a query with a non-<command>SELECT</> top-level operation
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible <command>CREATE TABLE</> failure when inheriting the
-      <quote>same</> constraint from multiple parent relations that
-      inherited that constraint from a common ancestor (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <function>pg_get_ruledef()</> to show the alias, if any, attached
-      to the target table of an <command>UPDATE</> or <command>DELETE</>
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Restore the pre-8.3 behavior that an out-of-range block number in a
-      TID being used in a TidScan plan results in silently not matching any
-      rows (Tom)
-     </para>
-
-     <para>
-      8.3.0 and 8.3.1 threw an error instead.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix GIN bug that could result in a <literal>too many LWLocks
-      taken</literal> failure (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix broken GiST comparison function for <type>tsquery</> (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <function>tsvector_update_trigger()</> and <function>ts_stat()</>
-      to accept domains over the types they expect to work with (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix failure to support enum data types as foreign keys (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crash when decompressing corrupted data
-      (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix race conditions between delayed unlinks and <command>DROP
-      DATABASE</> (Heikki)
-     </para>
-
-     <para>
-      In the worst case this could result in deleting a newly created table
-      in a new database that happened to get the same OID as the
-      recently-dropped one; but of course that is an extremely
-      low-probability scenario.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Repair two places where SIGTERM exit of a backend could leave corrupted
-      state in shared memory (Tom)
-     </para>
-
-     <para>
-      Neither case is very important if SIGTERM is used to shut down the
-      whole database cluster together, but there was a problem if someone
-      tried to SIGTERM individual backends.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash due to incorrect plan generated for an
-      <literal><replaceable>x</> IN (SELECT <replaceable>y</>
-      FROM ...)</literal> clause when <replaceable>x</> and <replaceable>y</>
-      have different data types; and make sure the behavior is semantically
-      correct when the conversion from <replaceable>y</>'s type to
-      <replaceable>x</>'s type is lossy (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix oversight that prevented the planner from substituting known Param
-      values as if they were constants (Tom)
-     </para>
-
-     <para>
-      This mistake partially disabled optimization of unnamed
-      extended-Query statements in 8.3.0 and 8.3.1: in particular the
-      LIKE-to-indexscan optimization would never be applied if the LIKE
-      pattern was passed as a parameter, and constraint exclusion
-      depending on a parameter value didn't work either.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner failure when an indexable <function>MIN</> or
-      <function>MAX</> aggregate is used with <literal>DISTINCT</> or
-      <literal>ORDER BY</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix planner to ensure it never uses a <quote>physical tlist</> for a
-      plan node that is feeding a Sort node (Tom)
-     </para>
-
-     <para>
-      This led to the sort having to push around more data than it really
-      needed to, since unused column values were included in the sorted
-      data.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unnecessary copying of query strings (Tom)
-     </para>
-
-     <para>
-      This fixes a performance problem introduced in 8.3.0 when a very large
-      number of commands are submitted as a single query string.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>TransactionIdIsCurrentTransactionId()</> use binary
-      search instead of linear search when checking child-transaction XIDs
-      (Heikki)
-     </para>
-
-     <para>
-      This fixes some cases in which 8.3.0 was significantly
-      slower than earlier releases.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix conversions between ISO-8859-5 and other encodings to handle
-      Cyrillic <quote>Yo</> characters (<literal>e</> and <literal>E</> with
-      two dots) (Sergey Burladyan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix several datatype input functions, notably <function>array_in()</>,
-      that were allowing unused bytes in their results to contain
-      uninitialized, unpredictable values (Tom)
-     </para>
-
-     <para>
-      This could lead to failures in which two apparently identical literal
-      values were not seen as equal, resulting in the parser complaining
-      about unmatched <literal>ORDER BY</> and <literal>DISTINCT</>
-      expressions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a corner case in regular-expression substring matching
-      (<literal>substring(<replaceable>string</> from
-      <replaceable>pattern</>)</literal>) (Tom)
-     </para>
-
-     <para>
-      The problem occurs when there is a match to the pattern overall but
-      the user has specified a parenthesized subexpression and that
-      subexpression hasn't got a match.  An example is
-      <literal>substring('foo' from 'foo(bar)?')</>.
-      This should return NULL, since <literal>(bar)</> isn't matched, but
-      it was mistakenly returning the whole-pattern match instead (ie,
-      <literal>foo</>).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent cancellation of an auto-vacuum that was launched to prevent
-      XID wraparound (Alvaro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <command>ANALYZE</>'s handling of in-doubt tuples (those
-      inserted or deleted by a not-yet-committed transaction) so that the
-      counts it reports to the stats collector are more likely to be correct
-      (Pavan Deolasee)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>initdb</> to reject a relative path for its
-      <literal>--xlogdir</> (<literal>-X</>) option (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <application>psql</> print tab characters as an appropriate
-      number of spaces, rather than <literal>\x09</literal> as was done in
-      8.3.0 and 8.3.1 (Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008c (for
-      DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba, and
-      Argentina/San_Luis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <function>ECPGget_PGconn()</> function to
-      <application>ecpglib</> (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect result from <application>ecpg</>'s
-      <function>PGTYPEStimestamp_sub()</> function (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix handling of continuation line markers in <application>ecpg</>
-      (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes in <filename>contrib/cube</> functions (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix core dump in <filename>contrib/xml2</>'s
-      <function>xpath_table()</> function when the input query returns a
-      NULL value (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/xml2</>'s makefile to not override
-      <literal>CFLAGS</>, and make it auto-configure properly for
-      <application>libxslt</> present or not (Tom)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3-1">
-  <title>Release 8.3.1</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2008-03-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.3.0.
-   For information about new features in the 8.3 major release, see
-   <xref linkend="release-8-3">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.3.1</title>
-
-   <para>
-    A dump/restore is not required for those running 8.3.X.
-    However, you might need to <command>REINDEX</> indexes on textual
-    columns after updating, if you are affected by the Windows locale
-    issue described below.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix character string comparison for Windows locales that consider
-      different character combinations as equal (Tom)
-     </para>
-
-     <para>
-      This fix applies only on Windows and only when using UTF-8
-      database encoding.  The same fix was made for all other cases
-      over two years ago, but Windows with UTF-8 uses a separate code
-      path that was not updated.  If you are using a locale that
-      considers some non-identical strings as equal, you may need to
-      <command>REINDEX</> to fix existing indexes on textual columns.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Repair corner-case bugs in <command>VACUUM FULL</> (Tom)
-     </para>
-
-     <para>
-      A potential deadlock between concurrent <command>VACUUM FULL</>
-      operations on different system catalogs was introduced in 8.2.
-      This has now been corrected.  8.3 made this worse because the
-      deadlock could occur within a critical code section, making it
-      a PANIC rather than just ERROR condition.
-     </para>
-
-     <para>
-      Also, a <command>VACUUM FULL</> that failed partway through
-      vacuuming a system catalog could result in cache corruption in
-      concurrent database sessions.
-     </para>
-
-     <para>
-      Another <command>VACUUM FULL</> bug introduced in 8.3 could
-      result in a crash or out-of-memory report when dealing with
-      pages containing no live tuples.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix misbehavior of foreign key checks involving <type>character</>
-      or <type>bit</> columns (Tom)
-     </para>
-
-     <para>
-      If the referencing column were of a different but compatible type
-      (for instance <type>varchar</>), the constraint was enforced incorrectly.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid needless deadlock failures in no-op foreign-key checks (Stephan
-      Szabo, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible core dump when re-planning a prepared query (Tom)
-     </para>
-
-     <para>
-      This bug affected only protocol-level prepare operations, not
-      SQL <command>PREPARE</>, and so tended to be seen only with
-      JDBC, DBI, and other client-side drivers that use prepared
-      statements heavily.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible failure when re-planning a query that calls an SPI-using
-      function (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix failure in row-wise comparisons involving columns of different
-      datatypes (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix longstanding <command>LISTEN</>/<command>NOTIFY</>
-      race condition (Tom)
-     </para>
-
-     <para>
-      In rare cases a session that had just executed a
-      <command>LISTEN</> might not get a notification, even though
-      one would be expected because the concurrent transaction executing
-      <command>NOTIFY</> was observed to commit later.
-     </para>
-
-     <para>
-      A side effect of the fix is that a transaction that has executed
-      a not-yet-committed <command>LISTEN</> command will not see any
-      row in <structname>pg_listener</> for the <command>LISTEN</>,
-      should it choose to look; formerly it would have.  This behavior
-      was never documented one way or the other, but it is possible that
-      some applications depend on the old behavior.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>LISTEN</> and <command>UNLISTEN</> within a
-      prepared transaction (Tom)
-     </para>
-
-     <para>
-      This was formerly allowed but trying to do it had various unpleasant
-      consequences, notably that the originating backend could not exit
-      as long as an <command>UNLISTEN</> remained uncommitted.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow dropping a temporary table within a
-      prepared transaction (Heikki)
-     </para>
-
-     <para>
-      This was correctly disallowed by 8.1, but the check was inadvertently
-      broken in 8.2 and 8.3.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix rare crash when an error occurs during a query using a hash index
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect comparison of <type>tsquery</> values (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect behavior of <literal>LIKE</> with non-ASCII characters
-      in single-byte encodings (Rolf Jentsch)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disable <function>xmlvalidate</> (Tom)
-     </para>
-
-     <para>
-      This function should have been removed before 8.3 release, but
-      was inadvertently left in the source code.  It poses a small
-      security risk since unprivileged users could use it to read the
-      first few characters of any file accessible to the server.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leaks in certain usages of set-returning functions (Neil)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>encode(<replaceable>bytea</>, 'escape')</> convert all
-      high-bit-set byte values into <literal>\</><replaceable>nnn</> octal
-      escape sequences (Tom)
-     </para>
-
-     <para>
-      This is necessary to avoid encoding problems when the database
-      encoding is multi-byte.  This change could pose compatibility issues
-      for applications that are expecting specific results from
-      <function>encode</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix input of datetime values for February 29 in years BC (Tom)
-     </para>
-
-     <para>
-      The former coding was mistaken about which years were leap years.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>unrecognized node type</> error in some variants of
-      <command>ALTER OWNER</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid tablespace permissions errors in <command>CREATE TABLE LIKE
-      INCLUDING INDEXES</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <structname>pg_stat_activity</>.<structfield>waiting</> flag
-      is cleared when a lock wait is aborted (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix handling of process permissions on Windows Vista (Dave, Magnus)
-     </para>
-
-     <para>
-      In particular, this fix allows starting the server as the Administrator
-      user.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2008a
-      (in particular, recent Chile changes); adjust timezone abbreviation
-      <literal>VET</> (Venezuela) to mean UTC-4:30, not UTC-4:00 (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</> problems with arrays (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to correctly extract the postmaster's port
-      number from command-line options (Itagaki Takahiro, Tom)
-     </para>
-
-     <para>
-      Previously, <literal>pg_ctl start -w</> could try to contact the
-      postmaster on the wrong port, leading to bogus reports of startup
-      failure.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Use <option>-fwrapv</> to defend against possible misoptimization
-      in recent <application>gcc</> versions (Tom)
-     </para>
-
-     <para>
-      This is known to be necessary when building <productname>PostgreSQL</>
-      with <application>gcc</> 4.3 or later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Enable building <filename>contrib/uuid-ossp</> with MSVC (Hiroshi Saito)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-3">
-  <title>Release 8.3</title>
-
-  <note>
-   <title>Release date</title>
-   <simpara>2008-02-04</simpara>
-  </note>
-
-  <sect2>
-   <title>Overview</title>
-
-   <para>
-    With significant new functionality and performance enhancements,
-    this release represents a major leap forward for
-    <productname>PostgreSQL</>. This was made possible by a growing
-    community that has dramatically accelerated the pace of
-    development. This release adds the following major features:
-   </para>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Full text search is integrated into the core database system
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Support for the SQL/XML standard, including new operators and an
-      <type>XML</type> data type
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Enumerated data types (<type>ENUM</type>)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Arrays of composite types
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Universally Unique Identifier (<type>UUID</>) data type
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add control over whether <literal>NULL</>s sort first or last
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Updatable cursors
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Server configuration parameters can now be set on a per-function
-      basis
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      User-defined types can now have type modifiers
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Automatically re-plan cached queries when table
-      definitions change or statistics are updated
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Numerous improvements in logging and statistics collection
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Support Security Service Provider Interface (<acronym>SSPI</>) for
-      authentication on Windows
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Support multiple concurrent autovacuum processes, and other
-      autovacuum improvements
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow the whole <productname>PostgreSQL</> distribution to be compiled
-      with <productname>Microsoft Visual C++</>
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <para>
-    Major performance improvements are listed below.  Most of
-    these enhancements are automatic and do not require user changes or
-    tuning:
-   </para>
-
-  <itemizedlist>
-
-    <listitem>
-     <para>
-      Asynchronous commit delays writes to WAL during transaction commit
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Checkpoint writes can be spread over a longer time period to smooth
-      the I/O spike during each checkpoint
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Heap-Only Tuples (<acronym>HOT</>) accelerate space reuse for
-      most <command>UPDATE</>s and <command>DELETE</>s
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Just-in-time background writer strategy improves disk write
-      efficiency
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Using non-persistent transaction IDs for read-only transactions
-      reduces overhead and <command>VACUUM</> requirements
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Per-field and per-row storage overhead has been reduced
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Large sequential scans no longer force out frequently used
-      cached pages
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Concurrent large sequential scans can now share disk reads
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <literal>ORDER BY ... LIMIT</> can be done without sorting
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <para>
-    The above items are explained in more detail in the sections below.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Migration to Version 8.3</title>
-
-   <para>
-    A dump/restore using <application>pg_dump</application> is
-    required for those wishing to migrate data from any previous
-    release.
-   </para>
-
-   <para>
-    Observe the following incompatibilities:
-   </para>
-
-   <sect3>
-    <title>General</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Non-character data types are no longer automatically cast to
-       <type>TEXT</> (Peter, Tom)
-      </para>
-
-      <para>
-       Previously, if a non-character value was supplied to an operator or
-       function that requires <type>text</> input, it was automatically
-       cast to <type>text</>, for most (though not all) built-in data types.
-       This no longer happens: an explicit cast to <type>text</> is now
-       required for all non-character-string types.  For example, these
-       expressions formerly worked:
-
-<programlisting>
-substr(current_date, 1, 4)
-23 LIKE '2%'
-</programlisting>
-
-       but will now draw <quote>function does not exist</> and <quote>operator
-       does not exist</> errors respectively.  Use an explicit cast instead:
-
-<programlisting>
-substr(current_date::text, 1, 4)
-23::text LIKE '2%'
-</programlisting>
-
-       (Of course, you can use the more verbose <literal>CAST()</> syntax too.)
-       The reason for the change is that these automatic casts too often caused
-       surprising behavior.  An example is that in previous releases, this
-       expression was accepted but did not do what was expected:
-
-<programlisting>
-current_date &lt; 2017-11-17
-</programlisting>
-
-       This is actually comparing a date to an integer, which should be
-       (and now is) rejected &mdash; but in the presence of automatic
-       casts both sides were cast to <type>text</> and a textual comparison
-       was done, because the <literal>text &lt; text</> operator was able
-       to match the expression when no other <literal>&lt;</> operator could.
-      </para>
-
-      <para>
-       Types <type>char(<replaceable>n</>)</type> and
-       <type>varchar(<replaceable>n</>)</type> still cast to <type>text</>
-       automatically.  Also, automatic casting to <type>text</> still works for
-       inputs to the concatenation (<literal>||</>) operator, so long as least
-       one input is a character-string type.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Full text search features from <filename>contrib/tsearch2</> have
-        been moved into the core server, with some minor syntax changes
-      </para>
-
-      <para>
-       <filename>contrib/tsearch2</> now contains a compatibility
-       interface.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>ARRAY(SELECT ...)</literal>, where the <command>SELECT</>
-       returns no rows, now returns an empty array, rather than NULL
-       (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The array type name for a base data type is no longer always the base
-       type's name with an underscore prefix
-      </para>
-
-      <para>
-       The old naming convention is still honored when possible, but
-       application code should no longer depend on it. Instead
-       use the new <literal>pg_type.typarray</literal> column to
-       identify the array data type associated with a given type.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>ORDER BY ... USING</> <replaceable>operator</> must now
-       use a less-than or greater-than <replaceable>operator</> that is
-       defined in a btree operator class
-      </para>
-
-      <para>
-       This restriction was added to prevent inconsistent results.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <command>SET LOCAL</command> changes now persist until
-       the end of the outermost transaction, unless rolled back (Tom)
-      </para>
-
-      <para>
-       Previously <command>SET LOCAL</command>'s effects were lost
-       after subtransaction commit (<command>RELEASE SAVEPOINT</>
-       or exit from a PL/pgSQL exception block).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Commands rejected in transaction blocks are now also rejected in
-       multiple-statement query strings (Tom)
-      </para>
-
-      <para>
-       For example, <literal>"BEGIN; DROP DATABASE; COMMIT"</> will now be
-       rejected even if submitted as a single query message.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <command>ROLLBACK</> outside a transaction block now
-       issues <literal>NOTICE</> instead of <literal>WARNING</> (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Prevent <command>NOTIFY</command>/<command>LISTEN</command>/<command>UNLISTEN</command>
-       from accepting schema-qualified names (Bruce)
-      </para>
-
-      <para>
-       Formerly, these commands accepted <literal>schema.relation</> but
-       ignored the schema part, which was confusing.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <command>ALTER SEQUENCE</> no longer affects the sequence's
-       <function>currval()</> state (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Foreign keys now must match indexable conditions for
-       cross-data-type references (Tom)
-      </para>
-
-      <para>
-       This improves semantic consistency and helps avoid
-       performance problems.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Restrict object size functions to users who have reasonable
-       permissions to view such information (Tom)
-      </para>
-
-      <para>
-       For example, <function>pg_database_size()</function> now requires
-       <literal>CONNECT</> permission, which is granted to everyone by
-       default. <function>pg_tablespace_size()</function> requires
-       <literal>CREATE</> permission in the tablespace, or is allowed if
-       the tablespace is the default tablespace for the database.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove the undocumented <literal>!!=</> (not in) operator (Tom)
-      </para>
-
-      <para>
-       <literal>NOT IN (SELECT ...)</literal> is the proper way to
-       perform this operation.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Internal hashing functions are now more uniformly-distributed (Tom)
-      </para>
-
-      <para>
-       If application code was computing and storing hash values using
-       internal <productname>PostgreSQL</> hashing functions, the hash
-       values must be regenerated.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       C-code conventions for handling variable-length data values
-       have changed (Greg Stark, Tom)
-      </para>
-
-      <para>
-       The new <function>SET_VARSIZE()</> macro <emphasis>must</> be used
-       to set the length of generated <type>varlena</> values. Also, it
-       might be necessary to expand (<quote>de-TOAST</quote>) input values
-       in more cases.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Continuous archiving no longer reports each successful archive
-       operation to the server logs unless <literal>DEBUG</> level is used
-       (Simon)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    </sect3>
-
-    <sect3>
-     <title>Configuration Parameters</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Numerous changes in administrative server parameters
-      </para>
-
-      <para>
-       <varname>bgwriter_lru_percent</>,
-       <varname>bgwriter_all_percent</>,
-       <varname>bgwriter_all_maxpages</>,
-       <varname>stats_start_collector</>, and
-       <varname>stats_reset_on_server_start</> are removed.
-       <varname>redirect_stderr</> is renamed to
-       <varname>logging_collector</>.
-       <varname>stats_command_string</> is renamed to
-       <varname>track_activities</>.
-       <varname>stats_block_level</> and <varname>stats_row_level</>
-       are merged into <varname>track_counts</>.
-       A new boolean configuration parameter, <varname>archive_mode</>,
-       controls archiving. Autovacuum's default settings have changed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <varname>stats_start_collector</varname> parameter (Tom)
-      </para>
-
-      <para>
-       We now always start the collector process, unless <acronym>UDP</>
-       socket creation fails.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <varname>stats_reset_on_server_start</varname> parameter (Tom)
-      </para>
-
-      <para>
-       This was removed because <function>pg_stat_reset()</function>
-       can be used for this purpose.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Commenting out a parameter in <filename>postgresql.conf</> now
-       causes it to revert to its default value (Joachim Wieland)
-      </para>
-
-      <para>
-       Previously, commenting out an entry left the parameter's value unchanged
-       until the next server restart.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    </sect3>
-
-
-    <sect3>
-     <title>Character Encodings</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add more checks for invalidly-encoded data (Andrew)
-      </para>
-
-      <para>
-       This change plugs some holes that existed in literal backslash
-       escape string processing and <command>COPY</command> escape
-       processing. Now the de-escaped string is rechecked to see if the
-       result created an invalid multi-byte character.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Disallow database encodings that are inconsistent with the server's
-       locale setting (Tom)
-      </para>
-
-      <para>
-       On most platforms, <literal>C</> locale is the only locale that
-       will work with any database encoding.  Other locale settings imply
-       a specific encoding and will misbehave if the database encoding
-       is something different.  (Typical symptoms include bogus textual
-       sort order and wrong results from <function>upper()</> or
-       <function>lower()</>.)  The server now rejects attempts to create
-       databases that have an incompatible encoding.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Ensure that <function>chr()</function> cannot create
-       invalidly-encoded values (Andrew)
-      </para>
-
-      <para>
-       In UTF8-encoded databases the argument of <function>chr()</function> is
-       now treated as a Unicode code point. In other multi-byte encodings
-       <function>chr()</function>'s argument must designate a 7-bit ASCII
-       character.  Zero is no longer accepted.
-       <function>ascii()</function> has been adjusted to match.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Adjust <function>convert()</function> behavior to ensure encoding
-       validity (Andrew)
-      </para>
-
-      <para>
-       The two argument form of <function>convert()</function> has been
-       removed. The three argument form now takes a <type>bytea</type>
-       first argument and returns a <type>bytea</type>. To cover the
-       loss of functionality, three new functions have been added:
-      </para>
-
-      <itemizedlist>
-       <listitem>
-        <para>
-         <function>convert_from(bytea, name)</function> returns
-         <type>text</> &mdash; converts the first argument from the named
-         encoding to the database encoding
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         <function>convert_to(text, name)</function> returns
-         <type>bytea</> &mdash; converts the first argument from the
-         database encoding to the named encoding
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         <function>length(bytea, name)</function> returns
-         <type>integer</> &mdash; gives the length of the first
-         argument in characters in the named encoding
-        </para>
-       </listitem>
-      </itemizedlist>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <literal>convert(argument USING conversion_name)</literal>
-       (Andrew)
-      </para>
-
-      <para>
-       Its behavior did not match the SQL standard.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make JOHAB encoding client-only (Tatsuo)
-      </para>
-
-      <para>
-       JOHAB is not safe as a server-side encoding.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-    Below you will find a detailed account of the
-    changes between <productname>PostgreSQL</productname> 8.3 and
-    the previous major release.
-   </para>
-
-   <sect3>
-    <title>Performance</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Asynchronous commit delays writes to WAL during transaction commit
-       (Simon)
-      </para>
-
-      <para>
-       This feature dramatically increases performance for short data-modifying
-       transactions.  The disadvantage is that because disk writes are delayed,
-       if the database or operating system crashes before data is written to
-       the disk, committed data will be lost.  This feature is useful for
-       applications that can accept some data loss.  Unlike turning off
-       <varname>fsync</varname>, using asynchronous commit does not put
-       database consistency at risk; the worst case is that after a crash the
-       last few reportedly-committed transactions might not be committed after
-       all.
-       This feature is enabled by turning off <varname>synchronous_commit</>
-       (which can be done per-session or per-transaction, if some transactions
-       are critical and others are not).
-       <varname>wal_writer_delay</> can be adjusted to control the maximum
-       delay before transactions actually reach disk.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Checkpoint writes can be spread over a longer time period to smooth
-       the I/O spike during each checkpoint (Itagaki Takahiro and Heikki
-       Linnakangas)
-      </para>
-
-      <para>
-       Previously all modified buffers were forced to disk as quickly as
-       possible during a
-       checkpoint, causing an I/O spike that decreased server performance.
-       This new approach spreads out disk writes during checkpoints,
-       reducing peak I/O usage. (User-requested and shutdown checkpoints
-       are still written as quickly as possible.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Heap-Only Tuples (<acronym>HOT</>) accelerate space reuse for most
-       <command>UPDATE</>s and <command>DELETE</>s (Pavan Deolasee, with
-       ideas from many others)
-      </para>
-
-      <para>
-       <command>UPDATE</>s and <command>DELETE</>s leave dead tuples
-       behind, as do failed <command>INSERT</>s.  Previously only
-       <command>VACUUM</> could reclaim space taken by dead tuples. With
-       <acronym>HOT</> dead tuple space can be automatically reclaimed at
-       the time of <command>INSERT</> or <command>UPDATE</> if no changes
-       are made to indexed columns.  This allows for more consistent
-       performance.  Also, <acronym>HOT</> avoids adding duplicate index
-       entries.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Just-in-time background writer strategy improves disk write
-       efficiency (Greg Smith, Itagaki Takahiro)
-      </para>
-
-      <para>
-       This greatly reduces the need for manual tuning of the background
-       writer.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Per-field and per-row storage overhead have been reduced
-       (Greg Stark, Heikki Linnakangas)
-      </para>
-
-      <para>
-       Variable-length data types with data values less than 128 bytes long
-       will see a storage decrease of 3 to 6 bytes. For example, two adjacent
-       <type>char(1)</type> fields now use 4 bytes instead of 16. Row headers
-       are also 4 bytes shorter than before.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Using non-persistent transaction IDs for read-only transactions
-       reduces overhead and <command>VACUUM</> requirements (Florian Pflug)
-      </para>
-
-      <para>
-       Non-persistent transaction IDs do not increment the global
-       transaction counter. Therefore, they reduce the load on
-       <structname>pg_clog</> and increase the time between forced
-       vacuums to prevent transaction ID wraparound.
-       Other performance
-       improvements were also made that should improve concurrency.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Avoid incrementing the command counter after a read-only command (Tom)
-      </para>
-
-      <para>
-       There was formerly a hard limit of 2<superscript>32</>
-       (4 billion) commands per transaction.  Now only commands that
-       actually changed the database count, so while this limit still
-       exists, it should be significantly less annoying.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Create a dedicated <acronym>WAL</> writer process to off-load
-       work from backends (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Skip unnecessary WAL writes for <command>CLUSTER</command> and
-       <command>COPY</command> (Simon)
-      </para>
-
-      <para>
-       Unless WAL archiving is enabled, the system now avoids WAL writes
-       for <command>CLUSTER</command> and just <function>fsync()</>s the
-       table at the end of the command.  It also does the same for
-       <command>COPY</command> if the table was created in the same
-       transaction.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Large sequential scans no longer force out frequently used
-       cached pages (Simon, Heikki, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Concurrent large sequential scans can now share disk reads (Jeff Davis)
-      </para>
-
-      <para>
-       This is accomplished by starting the new sequential scan in the
-       middle of the table (where another sequential scan is already
-       in-progress) and wrapping around to the beginning to finish.  This
-       can affect the order of returned rows in a query that does not
-       specify <literal>ORDER BY</>.  The <varname>synchronize_seqscans</>
-       configuration parameter can be used to disable this if necessary.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>ORDER BY ... LIMIT</> can be done without sorting
-       (Greg Stark)
-      </para>
-
-      <para>
-       This is done by sequentially scanning the table and tracking just
-       the <quote>top N</> candidate rows, rather than performing a
-       full sort of the entire table.  This is useful when there is no
-       matching index and the <literal>LIMIT</> is not large.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Put a rate limit on messages sent to the statistics
-       collector by backends
-       (Tom)
-      </para>
-
-      <para>
-       This reduces overhead for short transactions, but might sometimes
-       increase the delay before statistics are tallied.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve hash join performance for cases with many NULLs (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Speed up operator lookup for cases with non-exact datatype matches (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Server</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Autovacuum is now enabled by default (Alvaro)
-      </para>
-
-      <para>
-       Several changes were made to eliminate disadvantages of having
-       autovacuum enabled, thereby justifying the change in default.
-       Several other autovacuum parameter defaults were also modified.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support multiple concurrent autovacuum processes (Alvaro, Itagaki
-       Takahiro)
-      </para>
-
-      <para>
-       This allows multiple vacuums to run concurrently.  This prevents
-       vacuuming of a large table from delaying vacuuming of smaller tables.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Automatically re-plan cached queries when table
-       definitions change or statistics are updated (Tom)
-      </para>
-
-      <para>
-       Previously PL/pgSQL functions that referenced temporary tables
-       would fail if the temporary table was dropped and recreated
-       between function invocations, unless <literal>EXECUTE</> was
-       used.  This improvement fixes that problem and many related issues.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a <varname>temp_tablespaces</varname> parameter to control
-       the tablespaces for temporary tables and files (Jaime Casanova,
-       Albert Cervera, Bernd Helmle)
-      </para>
-
-      <para>
-       This parameter defines a list of tablespaces to be used.  This
-       enables spreading the I/O load across multiple tablespaces. A random
-       tablespace is chosen each time a temporary object is created.
-       Temporary files are no longer stored in per-database
-       <filename>pgsql_tmp/</filename> directories but in per-tablespace
-       directories.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Place temporary tables' TOAST tables in special schemas named
-       <literal>pg_toast_temp_<replaceable>nnn</></literal> (Tom)
-      </para>
-
-      <para>
-       This allows low-level code to recognize these tables as temporary,
-       which enables various optimizations such as not WAL-logging changes
-       and using local rather than shared buffers for access. This also
-       fixes a bug wherein backends unexpectedly held open file references
-       to temporary TOAST tables.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix problem that a constant flow of new connection requests could
-       indefinitely delay the postmaster from completing a shutdown or
-       a crash restart (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Guard against a very-low-probability data loss scenario by preventing
-       re-use of a deleted table's relfilenode until after the next
-       checkpoint (Heikki)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <command>CREATE CONSTRAINT TRIGGER</>
-       to convert old-style foreign key trigger definitions into regular
-       foreign key constraints (Tom)
-      </para>
-
-      <para>
-       This will ease porting of foreign key constraints carried forward from
-       pre-7.3 databases, if they were never converted using
-       <filename>contrib/adddepend</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <literal>DEFAULT NULL</> to override inherited defaults (Tom)
-      </para>
-
-      <para>
-       <literal>DEFAULT NULL</> was formerly considered a noise phrase, but it
-       should (and now does) override non-null defaults that would otherwise
-       be inherited from a parent table or domain.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new encodings EUC_JIS_2004 and SHIFT_JIS_2004 (Tatsuo)
-      </para>
-
-      <para>
-       These new encodings can be converted to and from UTF-8.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change server startup log message from <quote>database system is
-       ready</quote> to <quote>database system is ready to accept
-       connections</quote>, and adjust its timing
-      </para>
-
-      <para>
-       The message now appears only when the postmaster is really ready
-       to accept connections.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Monitoring</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <varname>log_autovacuum_min_duration</varname> parameter to
-       support configurable logging of autovacuum activity (Simon, Alvaro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <varname>log_lock_waits</varname> parameter to log lock waiting
-       (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <varname>log_temp_files</varname> parameter to log temporary
-       file usage (Bill Moran)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <varname>log_checkpoints</varname> parameter to improve logging
-       of checkpoints (Greg Smith, Heikki)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <varname>log_line_prefix</varname> now supports
-       <literal>%s</literal> and <literal>%c</literal> escapes in all
-       processes (Andrew)
-      </para>
-
-      <para>
-       Previously these escapes worked only for user sessions, not for
-       background database processes.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <varname>log_restartpoints</varname> to control logging of
-       point-in-time recovery restart points (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Last transaction end time is now logged at end of recovery and at
-       each logged restart point (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Autovacuum now reports its activity start time in
-       <literal>pg_stat_activity</literal> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow server log output in comma-separated value (CSV) format (Arul
-       Shaji, Greg Smith, Andrew Dunstan)
-      </para>
-
-      <para>
-       CSV-format log files can easily be loaded into a database table for
-       subsequent analysis.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use PostgreSQL-supplied timezone support for formatting timestamps
-       displayed in the server log (Tom)
-      </para>
-
-      <para>
-       This avoids Windows-specific problems with localized time zone
-       names that are in the wrong encoding. There is a new
-       <varname>log_timezone</> parameter that controls the timezone
-       used in log messages, independently of the client-visible
-       <varname>timezone</> parameter.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New system view <literal>pg_stat_bgwriter</literal> displays
-       statistics about background writer activity (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new columns for database-wide tuple statistics to
-       <literal>pg_stat_database</literal> (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add an <literal>xact_start</literal> (transaction start time) column to
-       <literal>pg_stat_activity</literal> (Neil)
-      </para>
-
-      <para>
-       This makes it easier to identify long-running transactions.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>n_live_tuples</> and <literal>n_dead_tuples</> columns
-       to <literal>pg_stat_all_tables</literal> and related views (Glen
-       Parker)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Merge <varname>stats_block_level</> and <varname>stats_row_level</>
-       parameters into a single parameter <varname>track_counts</>, which
-       controls all messages sent to the statistics collector process
-       (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Rename <varname>stats_command_string</varname> parameter to
-       <varname>track_activities</varname> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix statistical counting of live and dead tuples to recognize that
-       committed and aborted transactions have different effects (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Authentication</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Support Security Service Provider Interface (<acronym>SSPI</>) for
-       authentication on Windows (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support GSSAPI authentication (Henry Hotz, Magnus)
-      </para>
-
-      <para>
-       This should be preferred to native Kerberos authentication because
-       GSSAPI is an industry standard.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support a global SSL configuration file (Victor Wagner)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <varname>ssl_ciphers</> parameter to control accepted SSL ciphers
-       (Victor Wagner)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a Kerberos realm parameter, <varname>krb_realm</> (Magnus)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Write-Ahead Log (<acronym>WAL</>) and Continuous Archiving</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Change the timestamps recorded in transaction WAL records from
-       time_t to TimestampTz representation (Tom)
-      </para>
-
-      <para>
-       This provides sub-second resolution in WAL, which can be useful for
-       point-in-time recovery.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reduce WAL disk space needed by warm standby servers (Simon)
-      </para>
-
-      <para>
-       This change allows a warm standby server to pass the name of the earliest
-       still-needed WAL file to the recovery script, allowing automatic removal
-       of no-longer-needed WAL files.  This is done using <literal>%r</> in
-       the <varname>restore_command</varname> parameter of
-       <filename>recovery.conf</filename>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       New boolean configuration parameter, <varname>archive_mode</>,
-       controls archiving (Simon)
-      </para>
-
-      <para>
-       Previously setting <varname>archive_command</> to an empty string
-       turned off archiving. Now <varname>archive_mode</> turns archiving
-       on and off, independently of <varname>archive_command</>. This is
-       useful for stopping archiving temporarily.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Queries</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Full text search is integrated into the core database
-       system (Teodor, Oleg)
-      </para>
-
-      <para>
-       Text search has been improved, moved into the core code, and is now
-       installed by default.  <filename>contrib/tsearch2</> now contains
-       a compatibility interface.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add control over whether <literal>NULL</>s sort first or last (Teodor, Tom)
-      </para>
-
-      <para>
-       The syntax is <literal>ORDER BY ... NULLS FIRST/LAST</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow per-column ascending/descending (<literal>ASC</>/<literal>DESC</>)
-       ordering options for indexes (Teodor, Tom)
-      </para>
-
-      <para>
-       Previously a query using <literal>ORDER BY</> with mixed
-       <literal>ASC</>/<literal>DESC</> specifiers could not fully use
-       an index. Now an index can be fully used in such cases if the
-       index was created with matching
-       <literal>ASC</>/<literal>DESC</> specifications.
-       <literal>NULL</> sort order within an index can be controlled, too.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>col IS NULL</> to use an index (Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Updatable cursors (Arul Shaji, Tom)
-      </para>
-
-      <para>
-       This eliminates the need to reference a primary key to
-       <command>UPDATE</> or <command>DELETE</> rows returned by a cursor.
-       The syntax is <literal>UPDATE/DELETE WHERE CURRENT OF</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>FOR UPDATE</literal> in cursors (Arul Shaji, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Create a general mechanism that supports casts to and from the
-       standard string types (<type>TEXT</type>, <type>VARCHAR</type>,
-       <type>CHAR</type>) for <emphasis>every</emphasis> datatype, by
-       invoking the datatype's I/O functions (Tom)
-      </para>
-
-      <para>
-       Previously, such casts were available only for types that had
-       specialized function(s) for the purpose.
-       These new casts are assignment-only in the to-string direction,
-       explicit-only in the other direction, and therefore should create no
-       surprising behavior.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>UNION</> and related constructs to return a domain
-       type, when all inputs are of that domain type (Tom)
-      </para>
-
-      <para>
-       Formerly, the output would be considered to be of the domain's base
-       type.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow limited hashing when using two different data types (Tom)
-      </para>
-
-      <para>
-       This allows hash joins, hash indexes, hashed subplans, and hash
-       aggregation to be used in situations involving cross-data-type
-       comparisons, if the data types have compatible hash functions.
-       Currently, cross-data-type hashing support exists for
-       <type>smallint</type>/<type>integer</type>/<type>bigint</type>,
-       and for <type>float4</type>/<type>float8</type>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve optimizer logic for detecting when variables are equal
-       in a <literal>WHERE</> clause (Tom)
-      </para>
-
-      <para>
-       This allows mergejoins to work with descending sort orders, and
-       improves recognition of redundant sort columns.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve performance when planning large inheritance trees in
-       cases where most tables are excluded by constraints (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Object Manipulation</title>
-    <itemizedlist>
-
-     <listitem>
-
-      <para>
-       Arrays of composite types (David Fetter, Andrew, Tom)
-      </para>
-
-      <para>
-       In addition to arrays of explicitly-declared composite types,
-       arrays of the rowtypes of regular tables and views are now
-       supported, except for rowtypes of system catalogs, sequences, and TOAST
-       tables.
-      </para>
-
-     </listitem>
-
-     <listitem>
-      <para>
-       Server configuration parameters can now be set on a per-function
-       basis (Tom)
-      </para>
-
-      <para>
-       For example, functions can now set their own
-       <varname>search_path</> to prevent unexpected behavior if a
-       different <varname>search_path</> exists at run-time.  Security
-       definer functions should set <varname>search_path</varname> to
-       avoid security loopholes.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <command>CREATE/ALTER FUNCTION</command> now supports
-       <literal>COST</literal> and <literal>ROWS</literal> options (Tom)
-      </para>
-
-      <para>
-       <literal>COST</literal> allows specification of the cost of a
-       function call.  <literal>ROWS</literal> allows specification of
-       the average number or rows returned by a set-returning function.
-       These values are used by the optimizer in choosing the best plan.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Implement <command>CREATE TABLE LIKE ...  INCLUDING
-       INDEXES</command> (Trevor Hardcastle, Nikhil Sontakke, Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>CREATE INDEX CONCURRENTLY</command> to ignore
-       transactions in other databases (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>ALTER VIEW ... RENAME TO</command> and <command>ALTER
-       SEQUENCE ... RENAME TO</command> (David Fetter, Neil)
-      </para>
-
-      <para>
-       Previously this could only be done via <command>ALTER TABLE ...
-       RENAME TO</command>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <command>CREATE/DROP/RENAME DATABASE</> wait briefly for
-       conflicting backends to exit before failing (Tom)
-      </para>
-
-      <para>
-       This increases the likelihood that these commands will succeed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow triggers and rules to be deactivated in groups using a
-       configuration parameter, for replication purposes (Jan)
-      </para>
-
-      <para>
-       This allows replication systems to disable triggers and rewrite
-       rules as a group without modifying the system catalogs directly.
-       The behavior is controlled by <command>ALTER TABLE</> and a new
-       parameter <varname>session_replication_role</varname>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       User-defined types can now have type modifiers (Teodor, Tom)
-      </para>
-
-      <para>
-       This allows a user-defined type to take a modifier, like
-       <type>ssnum(7)</>.  Previously only built-in
-       data types could have modifiers.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Utility Commands</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Non-superuser database owners now are able to add trusted procedural
-       languages to their databases by default (Jeremy Drake)
-      </para>
-
-      <para>
-       While this is reasonably safe, some administrators might wish to
-       revoke the privilege. It is controlled by
-       <structname>pg_pltemplate</>.<structfield>tmpldbacreate</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow a session's current parameter setting to be used as the
-       default for future sessions (Tom)
-      </para>
-
-      <para>
-       This is done with <literal>SET ... FROM CURRENT</literal> in
-       <command>CREATE/ALTER FUNCTION</command>, <command>ALTER
-       DATABASE</command>, or <command>ALTER ROLE</command>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Implement new commands <command>DISCARD ALL</command>,
-       <command>DISCARD PLANS</command>, <command>DISCARD
-       TEMPORARY</command>, <command>CLOSE ALL</command>, and
-       <command>DEALLOCATE ALL</command> (Marko Kreen, Neil)
-      </para>
-
-      <para>
-       These commands simplify resetting a database session to its initial
-       state, and are particularly useful for connection-pooling software.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <command>CLUSTER</command> MVCC-safe (Heikki Linnakangas)
-      </para>
-
-      <para>
-       Formerly, <command>CLUSTER</command> would discard all tuples
-       that were committed dead, even if there were still transactions
-       that should be able to see them under MVCC visibility rules.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new <command>CLUSTER</command> syntax: <literal>CLUSTER
-       <replaceable>table</> USING <replaceable>index</></literal>
-       (Holger Schurig)
-     </para>
-
-      <para>
-       The old <command>CLUSTER</command> syntax is still supported, but
-       the new form is considered more logical.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <command>EXPLAIN</command> so it can show complex plans
-       more accurately (Tom)
-      </para>
-
-      <para>
-       References to subplan outputs are now always shown correctly,
-       instead of using <literal>?column<replaceable>N</>?</literal>
-       for complicated cases.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Limit the amount of information reported when a user is dropped
-       (Alvaro)
-      </para>
-
-      <para>
-       Previously, dropping (or attempting to drop) a user who owned many
-       objects could result in large <literal>NOTICE</literal> or
-       <literal>ERROR</literal> messages listing all these objects; this
-       caused problems for some client applications.  The length of the
-       message is now limited, although a full list is still sent to the
-       server log.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Data Types</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Support for the SQL/XML standard, including new operators and an
-       <type>XML</type> data type (Nikolay Samokhvalov, Pavel Stehule, Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Enumerated data types (<type>ENUM</type>) (Tom Dunstan)
-      </para>
-
-      <para>
-       This feature provides convenient support for fields that have a
-       small, fixed set of allowed values.  An example of creating an
-       <literal>ENUM</> type is
-       <literal>CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy')</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Universally Unique Identifier (<type>UUID</>) data type (Gevik
-       Babakhani, Neil)
-      </para>
-
-      <para>
-       This closely matches <acronym>RFC</> 4122.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Widen the <type>MONEY</type> data type to 64 bits (D'Arcy Cain)
-      </para>
-
-      <para>
-       This greatly increases the range of supported <type>MONEY</>
-       values.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <type>float4</type>/<type>float8</type> to handle
-       <literal>Infinity</> and <literal>NAN</> (Not A Number)
-       consistently (Bruce)
-      </para>
-
-      <para>
-       The code formerly was not consistent about distinguishing
-       <literal>Infinity</> from overflow conditions.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow leading and trailing whitespace during input of
-       <type>boolean</type> values (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Prevent <command>COPY</> from using digits and lowercase letters as
-       delimiters (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Functions</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add new regular expression functions
-       <function>regexp_matches()</function>,
-       <function>regexp_split_to_array()</function>, and
-       <function>regexp_split_to_table()</function> (Jeremy Drake, Neil)
-      </para>
-
-      <para>
-       These functions provide extraction of regular expression
-       subexpressions and allow splitting a string using a POSIX regular
-       expression.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>lo_truncate()</function> for large object truncation
-       (Kris Jurka)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Implement <function>width_bucket()</function> for the <type>float8</>
-       data type (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>pg_stat_clear_snapshot()</function> to discard
-       statistics snapshots collected during the current transaction
-       (Tom)
-      </para>
-
-      <para>
-       The first request for statistics in a transaction takes a statistics
-       snapshot that does not change during the transaction.  This function
-       allows the snapshot to be discarded and a new snapshot loaded during
-       the next statistics query. This is particularly useful for PL/pgSQL
-       functions, which are confined to a single transaction.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>isodow</> option to <function>EXTRACT()</> and
-       <function>date_part()</> (Bruce)
-      </para>
-
-      <para>
-       This returns the day of the week, with Sunday as seven.
-       (<literal>dow</> returns Sunday as zero.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>ID</> (ISO day of week) and <literal>IDDD</> (ISO
-       day of year) format codes for <function>to_char()</>,
-       <function>to_date()</>, and <function>to_timestamp()</> (Brendan
-       Jurd)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <function>to_timestamp()</> and <function>to_date()</>
-       assume <literal>TM</literal> (trim) option for potentially
-       variable-width fields (Bruce)
-      </para>
-
-      <para>
-       This matches <productname>Oracle</>'s behavior.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix off-by-one conversion error in
-       <function>to_date()</function>/<function>to_timestamp()</function>
-       <literal>D</> (non-ISO day of week) fields (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <function>setseed()</function> return void, rather than a
-       useless integer value (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a hash function for <type>NUMERIC</type> (Neil)
-      </para>
-
-      <para>
-       This allows hash indexes and hash-based plans to be used with
-       <type>NUMERIC</type> columns.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve efficiency of
-       <literal>LIKE</literal>/<literal>ILIKE</literal>, especially for
-       multi-byte character sets like UTF-8 (Andrew, Itagaki Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <function>currtid()</function> functions require
-       <literal>SELECT</literal> privileges on the target table (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add several <function>txid_*()</function> functions to query
-       active transaction IDs (Jan)
-      </para>
-
-      <para>
-       This is useful for various replication solutions.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>PL/pgSQL Server-Side Language</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add scrollable cursor support, including directional control in
-       <command>FETCH</command> (Pavel Stehule)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>IN</literal> as an alternative to
-       <literal>FROM</literal> in PL/pgSQL's <command>FETCH</command>
-       statement, for consistency with the backend's
-       <command>FETCH</command> command (Pavel Stehule)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>MOVE</command> to PL/pgSQL (Magnus, Pavel Stehule,
-       Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Implement <command>RETURN QUERY</command> (Pavel Stehule, Neil)
-      </para>
-
-      <para>
-       This adds convenient syntax for PL/pgSQL set-returning functions
-       that want to return the result of a query.  <command>RETURN QUERY</>
-       is easier and more efficient than a loop
-       around <command>RETURN NEXT</command>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow function parameter names to be qualified with the
-       function's name (Tom)
-      </para>
-
-      <para>
-       For example, <literal>myfunc.myvar</>. This is particularly
-       useful for specifying variables in a query where the variable
-       name might match a column name.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make qualification of variables with block labels work properly (Tom)
-      </para>
-
-      <para>
-       Formerly, outer-level block labels could unexpectedly interfere with
-       recognition of inner-level record or row references.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Tighten requirements for <literal>FOR</literal> loop
-       <literal>STEP</> values (Tom)
-      </para>
-
-      <para>
-       Prevent non-positive <literal>STEP</> values, and handle
-       loop overflows.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve accuracy when reporting syntax error locations (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Other Server-Side Languages</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow type-name arguments to PL/Perl
-       <function>spi_prepare()</function> to be data type aliases in
-       addition to names found in <literal>pg_type</literal> (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow type-name arguments to PL/Python
-       <function>plpy.prepare()</function> to be data type aliases in
-       addition to names found in <literal>pg_type</literal> (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow type-name arguments to PL/Tcl <function>spi_prepare</> to
-       be data type aliases in addition to names found in
-       <literal>pg_type</literal> (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Enable PL/PythonU to compile on Python 2.5 (Marko Kreen)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support a true PL/Python boolean type in compatible Python versions
-       (Python 2.3 and later) (Marko Kreen)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix PL/Tcl problems with thread-enabled <filename>libtcl</> spawning
-       multiple threads within the backend (Steve Marshall, Paul Bayer,
-       Doug Knight)
-      </para>
-
-      <para>
-       This caused all sorts of unpleasantness.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><link linkend="APP-PSQL"><application>psql</></link></title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       List disabled triggers separately in <literal>\d</literal> output
-       (Brendan Jurd)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In <literal>\d</literal> patterns, always match <literal>$</literal>
-       literally (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Show aggregate return types in <literal>\da</literal> output
-       (Greg Sabino Mullane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add the function's volatility status to the output of
-       <literal>\df+</literal> (Neil)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>\prompt</literal> capability (Chad Wagner)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>\pset</literal>, <literal>\t</literal>, and
-       <literal>\x</literal> to specify <literal>on</> or <literal>off</>,
-       rather than just toggling (Chad Wagner)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>\sleep</> capability (Jan)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Enable <literal>\timing</> output for <literal>\copy</> (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <literal>\timing</literal> resolution on Windows
-       (Itagaki Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Flush <literal>\o</> output after each backslash command (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Correctly detect and report errors while reading a <literal>-f</>
-       input file (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <literal>-u</> option (this option has long been deprecated)
-       (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><link linkend="APP-PGDUMP"><application>pg_dump</></link></title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <literal>--tablespaces-only</> and <literal>--roles-only</>
-       options to <application>pg_dumpall</application> (Dave Page)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add an output file option to
-       <application>pg_dumpall</application> (Dave Page)
-      </para>
-
-      <para>
-       This is primarily useful on Windows, where output redirection of
-       child <application>pg_dump</application> processes does not work.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>pg_dumpall</> to accept an initial-connection
-       database name rather than the default
-       <literal>template1</literal> (Dave Page)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In <literal>-n</> and <literal>-t</> switches, always match
-       <literal>$</literal> literally (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve performance when a database has thousands of objects (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <literal>-u</> option (this option has long been deprecated)
-       (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Other Client Applications</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       In <application>initdb</>, allow the location of the
-       <filename>pg_xlog</filename> directory to be specified
-       (Euler Taveira de Oliveira)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Enable server core dump generation in <application>pg_regress</>
-       on supported operating systems (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a <literal>-t</> (timeout) parameter to <application>pg_ctl</>
-       (Bruce)
-      </para>
-
-      <para>
-       This controls how long <application>pg_ctl</> will wait when waiting
-       for server startup or shutdown.  Formerly the timeout was hard-wired
-       as 60 seconds.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a <application>pg_ctl</> option to control generation
-       of server core dumps (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow Control-C to cancel <application>clusterdb</>,
-       <application>reindexdb</>, and <application>vacuumdb</> (Itagaki
-       Takahiro, Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Suppress command tag output for <application>createdb</>,
-       <application>createuser</>, <application>dropdb</>, and
-       <application>dropuser</> (Peter)
-      </para>
-
-      <para>
-       The <literal>--quiet</> option is ignored and will be removed in 8.4.
-       Progress messages when acting on all databases now go to stdout
-       instead of stderr because they are not actually errors.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><link linkend="libpq"><application>libpq</></link></title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Interpret the <literal>dbName</> parameter of
-       <function>PQsetdbLogin()</> as a <literal>conninfo</> string if
-       it contains an equals sign (Andrew)
-      </para>
-
-      <para>
-       This allows use of <literal>conninfo</> strings in client
-       programs that still use <literal>PQsetdbLogin()</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support a global <acronym>SSL</> configuration file (Victor
-       Wagner)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add environment variable <varname>PGSSLKEY</> to control
-       <acronym>SSL</> hardware keys (Victor Wagner)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>lo_truncate()</function> for large object
-       truncation (Kris Jurka)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>PQconnectionNeedsPassword()</function> that returns
-       true if the server required a password but none was supplied
-       (Joe Conway, Tom)
-      </para>
-
-      <para>
-       If this returns true after a failed connection attempt, a client
-       application should prompt the user for a password.  In the past
-       applications have had to check for a specific error message string to
-       decide whether a password is needed; that approach is now
-       deprecated.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>PQconnectionUsedPassword()</function> that returns
-       true if the supplied password was actually used
-       (Joe Conway, Tom)
-      </para>
-
-      <para>
-       This is useful in some security contexts where it is important
-       to know whether a user-supplied password is actually valid.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><link linkend="ecpg"><application>ecpg</></link></title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Use V3 frontend/backend protocol (Michael)
-      </para>
-
-      <para>
-       This adds support for server-side prepared statements.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use native threads, instead of pthreads, on Windows (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve thread-safety of ecpglib (Itagaki Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make the ecpg libraries export only necessary API symbols (Michael)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><application>Windows</> Port</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow the whole <productname>PostgreSQL</> distribution to be compiled
-       with <productname>Microsoft Visual C++</> (Magnus and others)
-      </para>
-
-      <para>
-       This allows Windows-based developers to use familiar development
-       and debugging tools.
-       Windows executables made with Visual C++ might also have better
-       stability and performance than those made with other tool sets.
-       The client-only Visual C++ build scripts have been removed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Drastically reduce postmaster's memory usage when it has many child
-       processes (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow regression tests to be started by an administrative
-       user (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add native shared memory implementation (Magnus)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Server Programming Interface (<acronym>SPI</>)</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add cursor-related functionality in SPI (Pavel Stehule)
-      </para>
-
-      <para>
-       Allow access to the cursor-related planning options, and add
-       <command>FETCH</>/<command>MOVE</> routines.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow execution of cursor commands through
-       <function>SPI_execute</function> (Tom)
-      </para>
-
-      <para>
-       The macro <literal>SPI_ERROR_CURSOR</> still exists but will
-       never be returned.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       SPI plan pointers are now declared as <literal>SPIPlanPtr</> instead of
-       <literal>void *</> (Tom)
-      </para>
-
-      <para>
-       This does not break application code, but switching is
-       recommended to help catch simple programming mistakes.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Build Options</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <application>configure</> option <literal>--enable-profiling</>
-       to enable code profiling (works only with <application>gcc</>)
-       (Korry Douglas and Nikhil Sontakke)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <application>configure</> option <literal>--with-system-tzdata</>
-       to use the operating system's time zone database (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <acronym>PGXS</> so extensions can be built against PostgreSQL
-       installations whose <application>pg_config</> program does not
-       appear first in the <varname>PATH</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support <command>gmake draft</command> when building the
-       <acronym>SGML</> documentation (Bruce)
-      </para>
-
-      <para>
-       Unless <literal>draft</> is used, the documentation build will
-       now be repeated if necessary to ensure the index is up-to-date.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Source Code</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Rename macro <literal>DLLIMPORT</> to <literal>PGDLLIMPORT</> to
-       avoid conflicting with third party includes (like Tcl) that
-       define <literal>DLLIMPORT</> (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Create <quote>operator families</quote> to improve planning of
-       queries involving cross-data-type comparisons (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Update GIN <function>extractQuery()</> API to allow signalling
-       that nothing can satisfy the query (Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Move <literal>NAMEDATALEN</> definition from
-       <filename>postgres_ext.h</> to <filename>pg_config_manual.h</>
-       (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Provide <function>strlcpy()</function> and
-       <function>strlcat()</function> on all platforms, and replace
-       error-prone uses of <function>strncpy()</function>,
-       <function>strncat()</function>, etc (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Create hooks to let an external plugin monitor (or even replace) the
-       planner and create plans for hypothetical situations (Gurjeet
-       Singh, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Create a function variable <literal>join_search_hook</> to let plugins
-       override the join search order portion of the planner (Julius
-       Stroffek)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>tas()</> support for Renesas' M32R processor
-       (Kazuhiro Inaoka)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>quote_identifier()</function> and
-       <application>pg_dump</application> no longer quote keywords that are
-       unreserved according to the grammar (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change the on-disk representation of the <type>NUMERIC</type>
-       data type so that the <structfield>sign_dscale</> word comes
-       before the weight (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use <acronym>SYSV</> semaphores rather than POSIX on Darwin
-       &gt;= 6.0, i.e., OS X 10.2 and up (Chris Marcellino)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="acronyms">acronym</link> and <link
-       linkend="creating-cluster-nfs">NFS</link> documentation
-       sections (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       "Postgres" is now documented as an accepted alias for
-       "PostgreSQL" (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add documentation about preventing database server spoofing when
-       the server is down (Bruce)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Contrib</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Move <filename>contrib</> <filename>README</> content into the
-       main <productname>PostgreSQL</> documentation (Albert Cervera i
-       Areny)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <filename>contrib/pageinspect</filename> module for low-level
-       page inspection (Simon, Heikki)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <filename>contrib/pg_standby</filename> module for controlling
-       warm standby operation (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <filename>contrib/uuid-ossp</filename> module for generating
-       <type>UUID</> values using the OSSP UUID library (Peter)
-      </para>
-
-      <para>
-       Use <application>configure</>
-       <literal>--with-ossp-uuid</literal> to activate. This takes
-       advantage of the new <type>UUID</type> builtin type.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <filename>contrib/dict_int</filename>,
-       <filename>contrib/dict_xsyn</filename>, and
-       <filename>contrib/test_parser</filename> modules to provide
-       sample add-on text search dictionary templates and parsers
-       (Sergey Karpov)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>contrib/pgbench</> to set the fillfactor (Pavan
-       Deolasee)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add timestamps to <application>contrib/pgbench</> <literal>-l</>
-       (Greg Smith)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add usage count statistics to
-       <filename>contrib/pgbuffercache</filename> (Greg Smith)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add GIN support for <filename>contrib/hstore</> (Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add GIN support for <filename>contrib/pg_trgm</> (Guillaume Smet, Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Update OS/X startup scripts in
-       <filename>contrib/start-scripts</filename> (Mark Cotner, David
-       Fetter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Restrict <function>pgrowlocks()</function> and
-       <function>dblink_get_pkey()</function> to users who have
-       <literal>SELECT</literal> privilege on the target table (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Restrict <filename>contrib/pgstattuple</filename> functions to
-       superusers (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <filename>contrib/xml2</filename> is deprecated and planned for
-       removal in 8.4 (Peter)
-      </para>
-
-      <para>
-       The new XML support in core PostgreSQL supersedes this module.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-  </sect2>
- </sect1>
diff --git a/doc-xc/src/sgml/release-8.4.sgmlin b/doc-xc/src/sgml/release-8.4.sgmlin
deleted file mode 100644
index 5e6980517d..0000000000
--- a/doc-xc/src/sgml/release-8.4.sgmlin
+++ /dev/null
@@ -1,5959 +0,0 @@
-<!-- doc/src/sgml/release-8.4.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-8-4-7">
-  <title>Release 8.4.7</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2011-01-31</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.4.6.
-   For information about new features in the 8.4 major release, see
-   <xref linkend="release-8-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.4.7</title>
-
-   <para>
-    A dump/restore is not required for those running 8.4.X.
-    However, if you are upgrading from a version earlier than 8.4.2,
-    see the release notes for 8.4.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Avoid failures when <command>EXPLAIN</> tries to display a simple-form
-      <literal>CASE</> expression (Tom Lane)
-     </para>
-
-     <para>
-      If the <literal>CASE</>'s test expression was a constant, the planner
-      could simplify the <literal>CASE</> into a form that confused the
-      expression-display code, resulting in <quote>unexpected CASE WHEN
-      clause</> errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assignment to an array slice that is before the existing range
-      of subscripts (Tom Lane)
-     </para>
-
-     <para>
-      If there was a gap between the newly added subscripts and the first
-      pre-existing subscript, the code miscalculated how many entries needed
-      to be copied from the old array's null bitmap, potentially leading to
-      data corruption or crash.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unexpected conversion overflow in planner for very distant date
-      values (Tom Lane)
-     </para>
-
-     <para>
-      The <type>date</> type supports a wider range of dates than can be
-      represented by the <type>timestamp</> types, but the planner assumed it
-      could always convert a date to timestamp with impunity.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_restore</>'s text output for large objects (BLOBs)
-      when <varname>standard_conforming_strings</> is on (Tom Lane)
-     </para>
-
-     <para>
-      Although restoring directly to a database worked correctly, string
-      escaping was incorrect if <application>pg_restore</> was asked for
-      SQL text output and <varname>standard_conforming_strings</> had been
-      enabled in the source database.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix erroneous parsing of <type>tsquery</> values containing
-      <literal>... &amp; !(subexpression) | ...</literal> (Tom Lane)
-     </para>
-
-     <para>
-      Queries containing this combination of operators were not executed
-      correctly.  The same error existed in <filename>contrib/intarray</>'s
-      <type>query_int</> type and <filename>contrib/ltree</>'s
-      <type>ltxtquery</> type.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix buffer overrun in <filename>contrib/intarray</>'s input function
-      for the <type>query_int</> type (Apple)
-     </para>
-
-     <para>
-      This bug is a security risk since the function's return address could
-      be overwritten.  Thanks to Apple Inc's security team for reporting this
-      issue and supplying the fix.  (CVE-2010-4015)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in <filename>contrib/seg</>'s GiST picksplit algorithm
-      (Alexander Korotkov)
-     </para>
-
-     <para>
-      This could result in considerable inefficiency, though not actually
-      incorrect answers, in a GiST index on a <type>seg</> column.
-      If you have such an index, consider <command>REINDEX</>ing it after
-      installing this update.  (This is identical to the bug that was fixed in
-      <filename>contrib/cube</> in the previous update.)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-4-6">
-  <title>Release 8.4.6</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-12-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.4.5.
-   For information about new features in the 8.4 major release, see
-   <xref linkend="release-8-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.4.6</title>
-
-   <para>
-    A dump/restore is not required for those running 8.4.X.
-    However, if you are upgrading from a version earlier than 8.4.2,
-    see the release notes for 8.4.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Force the default
-      <link linkend="guc-wal-sync-method"><varname>wal_sync_method</></link>
-      to be <literal>fdatasync</> on Linux (Tom Lane, Marti Raudsepp)
-     </para>
-
-     <para>
-      The default on Linux has actually been <literal>fdatasync</> for many
-      years, but recent kernel changes caused <productname>PostgreSQL</> to
-      choose <literal>open_datasync</> instead.  This choice did not result
-      in any performance improvement, and caused outright failures on
-      certain filesystems, notably <literal>ext4</> with the
-      <literal>data=journal</> mount option.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane)
-     </para>
-
-     <para>
-      This could result in <quote>bad buffer id: 0</> failures or
-      corruption of index contents during replication.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix recovery from base backup when the starting checkpoint WAL record
-      is not in the same WAL segment as its redo point (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix persistent slowdown of autovacuum workers when multiple workers
-      remain active for a long time (Tom Lane)
-     </para>
-
-     <para>
-      The effective <varname>vacuum_cost_limit</> for an autovacuum worker
-      could drop to nearly zero if it processed enough tables, causing it
-      to run extremely slowly.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add support for detecting register-stack overrun on <literal>IA64</>
-      (Tom Lane)
-     </para>
-
-     <para>
-      The <literal>IA64</> architecture has two hardware stacks.  Full
-      prevention of stack-overrun failures requires checking both.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add a check for stack overflow in <function>copyObject()</> (Tom Lane)
-     </para>
-
-     <para>
-      Certain code paths could crash due to stack overflow given a
-      sufficiently complex query.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix detection of page splits in temporary GiST indexes (Heikki
-      Linnakangas)
-     </para>
-
-     <para>
-      It is possible to have a <quote>concurrent</> page split in a
-      temporary index, if for example there is an open cursor scanning the
-      index when an insertion is done.  GiST failed to detect this case and
-      hence could deliver wrong results when execution of the cursor
-      continued.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix error checking during early connection processing (Tom Lane)
-     </para>
-
-     <para>
-      The check for too many child processes was skipped in some cases,
-      possibly leading to postmaster crash when attempting to add the new
-      child process to fixed-size arrays.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve efficiency of window functions (Tom Lane)
-     </para>
-
-     <para>
-      Certain cases where a large number of tuples needed to be read in
-      advance, but <varname>work_mem</> was large enough to allow them all
-      to be held in memory, were unexpectedly slow.
-      <function>percent_rank()</>, <function>cume_dist()</> and
-      <function>ntile()</> in particular were subject to this problem.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid memory leakage while <command>ANALYZE</>'ing complex index
-      expressions (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure an index that uses a whole-row Var still depends on its table
-      (Tom Lane)
-     </para>
-
-     <para>
-      An index declared like <literal>create index i on t (foo(t.*))</>
-      would not automatically get dropped when its table was dropped.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not <quote>inline</> a SQL function with multiple <literal>OUT</>
-      parameters (Tom Lane)
-     </para>
-
-     <para>
-      This avoids a possible crash due to loss of information about the
-      expected result rowtype.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Behave correctly if <literal>ORDER BY</>, <literal>LIMIT</>,
-      <literal>FOR UPDATE</>, or <literal>WITH</> is attached to the
-      <literal>VALUES</> part of <literal>INSERT ... VALUES</> (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix constant-folding of <literal>COALESCE()</> expressions (Tom Lane)
-     </para>
-
-     <para>
-      The planner would sometimes attempt to evaluate sub-expressions that
-      in fact could never be reached, possibly leading to unexpected errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix postmaster crash when connection acceptance
-      (<function>accept()</> or one of the calls made immediately after it)
-      fails, and the postmaster was compiled with GSSAPI support (Alexander
-      Chernikov)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix missed unlink of temporary files when <varname>log_temp_files</>
-      is active (Tom Lane)
-     </para>
-
-     <para>
-      If an error occurred while attempting to emit the log message, the
-      unlink was not done, resulting in accumulation of temp files.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add print functionality for <structname>InhRelation</> nodes (Tom Lane)
-     </para>
-
-     <para>
-      This avoids a failure when <varname>debug_print_parse</> is enabled
-      and certain types of query are executed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect calculation of distance from a point to a horizontal
-      line segment (Tom Lane)
-     </para>
-
-     <para>
-      This bug affected several different geometric distance-measurement
-      operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect calculation of transaction status in
-      <application>ecpg</> (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/pgSQL</>'s handling of <quote>simple</>
-      expressions to not fail in recursion or error-recovery cases (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/Python</>'s handling of set-returning functions
-      (Jan Urbanski)
-     </para>
-
-     <para>
-      Attempts to call SPI functions within the iterator generating a set
-      result would fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in <filename>contrib/cube</>'s GiST picksplit algorithm
-      (Alexander Korotkov)
-     </para>
-
-     <para>
-      This could result in considerable inefficiency, though not actually
-      incorrect answers, in a GiST index on a <type>cube</> column.
-      If you have such an index, consider <command>REINDEX</>ing it after
-      installing this update.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Don't emit <quote>identifier will be truncated</> notices in
-      <filename>contrib/dblink</> except when creating new connections
-      (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential coredump on missing public key in
-      <filename>contrib/pgcrypto</> (Marti Raudsepp)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak in <filename>contrib/xml2</>'s XPath query functions
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010o
-      for DST law changes in Fiji and Samoa;
-      also historical corrections for Hong Kong.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-4-5">
-  <title>Release 8.4.5</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-10-04</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.4.4.
-   For information about new features in the 8.4 major release, see
-   <xref linkend="release-8-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.4.5</title>
-
-   <para>
-    A dump/restore is not required for those running 8.4.X.
-    However, if you are upgrading from a version earlier than 8.4.2,
-    see the release notes for 8.4.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Use a separate interpreter for each calling SQL userid in PL/Perl and
-      PL/Tcl (Tom Lane)
-     </para>
-
-     <para>
-      This change prevents security problems that can be caused by subverting
-      Perl or Tcl code that will be executed later in the same session under
-      another SQL user identity (for example, within a <literal>SECURITY
-      DEFINER</> function).  Most scripting languages offer numerous ways that
-      that might be done, such as redefining standard functions or operators
-      called by the target function.  Without this change, any SQL user with
-      Perl or Tcl language usage rights can do essentially anything with the
-      SQL privileges of the target function's owner.
-     </para>
-
-     <para>
-      The cost of this change is that intentional communication among Perl
-      and Tcl functions becomes more difficult.  To provide an escape hatch,
-      PL/PerlU and PL/TclU functions continue to use only one interpreter
-      per session.  This is not considered a security issue since all such
-      functions execute at the trust level of a database superuser already.
-     </para>
-
-     <para>
-      It is likely that third-party procedural languages that claim to offer
-      trusted execution have similar security issues.  We advise contacting
-      the authors of any PL you are depending on for security-critical
-      purposes.
-     </para>
-
-     <para>
-      Our thanks to Tim Bunce for pointing out this issue (CVE-2010-3433).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent possible crashes in <function>pg_get_expr()</> by disallowing
-      it from being called with an argument that is not one of the system
-      catalog columns it's intended to be used with
-      (Heikki Linnakangas, Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Treat exit code 128 (<literal>ERROR_WAIT_NO_CHILDREN</>) as non-fatal on
-      Windows (Magnus Hagander)
-     </para>
-
-     <para>
-      Under high load, Windows processes will sometimes fail at startup with
-      this error code.  Formerly the postmaster treated this as a panic
-      condition and restarted the whole database, but that seems to be
-      an overreaction.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect placement of placeholder evaluation (Tom Lane)
-     </para>
-
-     <para>
-      This bug could result in query outputs being non-null when they
-      should be null, in cases where the inner side of an outer join
-      is a sub-select with non-strict expressions in its output list.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible duplicate scans of <literal>UNION ALL</> member relations
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>cannot handle unplanned sub-select</quote> error (Tom Lane)
-     </para>
-
-     <para>
-      This occurred when a sub-select contains a join alias reference that
-      expands into an expression containing another sub-select.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix mishandling of whole-row Vars that reference a view or sub-select
-      and appear within a nested sub-select (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix mishandling of cross-type <literal>IN</> comparisons (Tom Lane)
-     </para>
-
-     <para>
-      This could result in failures if the planner tried to implement an
-      <literal>IN</> join with a sort-then-unique-then-plain-join plan.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix computation of <command>ANALYZE</> statistics for <type>tsvector</>
-      columns (Jan Urbanski)
-     </para>
-
-     <para>
-      The original coding could produce incorrect statistics, leading to
-      poor plan choices later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve planner's estimate of memory used by <function>array_agg()</>,
-      <function>string_agg()</>, and similar aggregate functions
-      (Hitoshi Harada)
-     </para>
-
-     <para>
-      The previous drastic underestimate could lead to out-of-memory failures
-      due to inappropriate choice of a hash-aggregation plan.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix failure to mark cached plans as transient (Tom Lane)
-     </para>
-
-     <para>
-      If a plan is prepared while <command>CREATE INDEX CONCURRENTLY</> is
-      in progress for one of the referenced tables, it is supposed to be
-      re-planned once the index is ready for use.  This was not happening
-      reliably.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Reduce PANIC to ERROR in some occasionally-reported btree failure cases,
-      and provide additional detail in the resulting error messages
-      (Tom Lane)
-     </para>
-
-     <para>
-      This should improve the system's robustness with corrupted indexes.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect search logic for partial-match queries with GIN indexes
-      (Tom Lane)
-     </para>
-
-     <para>
-      Cases involving AND/OR combination of several GIN index conditions
-      didn't always give the right answer, and were sometimes much slower
-      than necessary.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent show_session_authorization() from crashing within autovacuum
-      processes (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Defend against functions returning setof record where not all the
-      returned rows are actually of the same rowtype (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible corruption of pending trigger event lists during
-      subtransaction rollback (Tom Lane)
-     </para>
-
-     <para>
-      This could lead to a crash or incorrect firing of triggers.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible failure when hashing a pass-by-reference function result
-      (Tao Ma, Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve merge join's handling of NULLs in the join columns (Tom Lane)
-     </para>
-
-     <para>
-      A merge join can now stop entirely upon reaching the first NULL,
-      if the sort order is such that NULLs sort high.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Take care to fsync the contents of lockfiles (both
-      <filename>postmaster.pid</> and the socket lockfile) while writing them
-      (Tom Lane)
-     </para>
-
-     <para>
-      This omission could result in corrupted lockfile contents if the
-      machine crashes shortly after postmaster start.  That could in turn
-      prevent subsequent attempts to start the postmaster from succeeding,
-      until the lockfile is manually removed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid recursion while assigning XIDs to heavily-nested
-      subtransactions (Andres Freund, Robert Haas)
-     </para>
-
-     <para>
-      The original coding could result in a crash if there was limited
-      stack space.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid holding open old WAL segments in the walwriter process
-      (Magnus Hagander, Heikki Linnakangas)
-     </para>
-
-     <para>
-      The previous coding would prevent removal of no-longer-needed segments.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <varname>log_line_prefix</>'s <literal>%i</> escape,
-      which could produce junk early in backend startup (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent misinterpretation of partially-specified relation options
-      for TOAST tables (Itagaki Takahiro)
-     </para>
-
-     <para>
-      In particular, <literal>fillfactor</> would be read as zero if any
-      other reloption had been set for the table, leading to serious bloat.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix inheritance count tracking in <command>ALTER TABLE ... ADD
-      CONSTRAINT</> (Robert Haas)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible data corruption in <command>ALTER TABLE ... SET
-      TABLESPACE</> when archiving is enabled (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow <command>CREATE DATABASE</> and <command>ALTER DATABASE ... SET
-      TABLESPACE</> to be interrupted by query-cancel (Guillaume Lelarge)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <command>CREATE INDEX</>'s checking of whether proposed index
-      expressions are immutable (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <command>REASSIGN OWNED</> to handle operator classes and families
-      (Asko Tiidumaa)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible core dump when comparing two empty <type>tsquery</> values
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>LIKE</>'s handling of patterns containing <literal>%</>
-      followed by <literal>_</> (Tom Lane)
-     </para>
-
-     <para>
-      We've fixed this before, but there were still some incorrectly-handled
-      cases.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Re-allow input of Julian dates prior to 0001-01-01 AD (Tom Lane)
-     </para>
-
-     <para>
-      Input such as <literal>'J100000'::date</> worked before 8.4,
-      but was unintentionally broken by added error-checking.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/pgSQL to throw an error, not crash, if a cursor is closed within
-      a <literal>FOR</> loop that is iterating over that cursor
-      (Heikki Linnakangas)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In PL/Python, defend against null pointer results from
-      <function>PyCObject_AsVoidPtr</> and <function>PyCObject_FromVoidPtr</>
-      (Peter Eisentraut)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In <application>libpq</>, fix full SSL certificate verification for the
-      case where both <literal>host</> and <literal>hostaddr</> are specified
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make psql recognize <command>DISCARD ALL</> as a command that should
-      not be encased in a transaction block in autocommit-off mode
-      (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some issues in <application>pg_dump</>'s handling of SQL/MED objects
-      (Tom Lane)
-     </para>
-
-     <para>
-      Notably, <application>pg_dump</> would always fail if run by a
-      non-superuser, which was not intended.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <application>pg_dump</> and <application>pg_restore</>'s
-      handling of non-seekable archive files (Tom Lane, Robert Haas)
-     </para>
-
-     <para>
-      This is important for proper functioning of parallel restore.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve parallel pg_restore's ability to cope with selective restore
-      (<literal>-L</> option) (Tom Lane)
-     </para>
-
-     <para>
-      The original code tended to fail if the <literal>-L</> file commanded
-      a non-default restore ordering.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</> to process data from <literal>RETURNING</>
-      clauses correctly (Michael Meskes)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some memory leaks in <application>ecpg</> (Zoltan Boszormenyi)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <filename>contrib/dblink</>'s handling of tables containing
-      dropped columns (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix connection leak after <quote>duplicate connection name</quote>
-      errors in <filename>contrib/dblink</> (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/dblink</> to handle connection names longer than
-      62 bytes correctly (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <function>hstore(text, text)</>
-      function to <filename>contrib/hstore</> (Robert Haas)
-     </para>
-
-     <para>
-      This function is the recommended substitute for the now-deprecated
-      <literal>=&gt;</> operator.  It was back-patched so that future-proofed
-      code can be used with older server versions.  Note that the patch will
-      be effective only after <filename>contrib/hstore</> is installed or
-      reinstalled in a particular database.  Users might prefer to execute
-      the <command>CREATE FUNCTION</> command by hand, instead.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update build infrastructure and documentation to reflect the source code
-      repository's move from CVS to Git (Magnus Hagander and others)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010l
-      for DST law changes in Egypt and Palestine; also historical corrections
-      for Finland.
-     </para>
-
-     <para>
-      This change also adds new names for two Micronesian timezones:
-      Pacific/Chuuk is now preferred over Pacific/Truk (and the preferred
-      abbreviation is CHUT not TRUT) and Pacific/Pohnpei is preferred over
-      Pacific/Ponape.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make Windows' <quote>N. Central Asia Standard Time</> timezone map to
-      Asia/Novosibirsk, not Asia/Almaty (Magnus Hagander)
-     </para>
-
-     <para>
-      Microsoft changed the DST behavior of this zone in the timezone update
-      from KB976098. Asia/Novosibirsk is a better match to its new behavior.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-4-4">
-  <title>Release 8.4.4</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-05-17</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.4.3.
-   For information about new features in the 8.4 major release, see
-   <xref linkend="release-8-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.4.4</title>
-
-   <para>
-    A dump/restore is not required for those running 8.4.X.
-    However, if you are upgrading from a version earlier than 8.4.2,
-    see the release notes for 8.4.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Enforce restrictions in <literal>plperl</> using an opmask applied to
-      the whole interpreter, instead of using <filename>Safe.pm</>
-      (Tim Bunce, Andrew Dunstan)
-     </para>
-
-     <para>
-      Recent developments have convinced us that <filename>Safe.pm</> is too
-      insecure to rely on for making <literal>plperl</> trustable.  This
-      change removes use of <filename>Safe.pm</> altogether, in favor of using
-      a separate interpreter with an opcode mask that is always applied.
-      Pleasant side effects of the change include that it is now possible to
-      use Perl's <literal>strict</> pragma in a natural way in
-      <literal>plperl</>, and that Perl's <literal>$a</> and <literal>$b</>
-      variables work as expected in sort routines, and that function
-      compilation is significantly faster.  (CVE-2010-1169)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent PL/Tcl from executing untrustworthy code from
-      <structname>pltcl_modules</> (Tom)
-     </para>
-
-     <para>
-      PL/Tcl's feature for autoloading Tcl code from a database table
-      could be exploited for trojan-horse attacks, because there was no
-      restriction on who could create or insert into that table.  This change
-      disables the feature unless <structname>pltcl_modules</> is owned by a
-      superuser.  (However, the permissions on the table are not checked, so
-      installations that really need a less-than-secure modules table can
-      still grant suitable privileges to trusted non-superusers.)  Also,
-      prevent loading code into the unrestricted <quote>normal</> Tcl
-      interpreter unless we are really going to execute a <literal>pltclu</>
-      function.  (CVE-2010-1170)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix data corruption during WAL replay of
-      <literal>ALTER ... SET TABLESPACE</> (Tom)
-     </para>
-
-     <para>
-      When <varname>archive_mode</> is on, <literal>ALTER ... SET TABLESPACE</>
-      generates a WAL record whose replay logic was incorrect.  It could write
-      the data to the wrong place, leading to possibly-unrecoverable data
-      corruption.  Data corruption would be observed on standby slaves, and
-      could occur on the master as well if a database crash and recovery
-      occurred after committing the <literal>ALTER</> and before the next
-      checkpoint.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash if a cache reset message is received during
-      rebuild of a relcache entry (Heikki)
-     </para>
-
-     <para>
-      This error was introduced in 8.4.3 while fixing a related failure.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Apply per-function GUC settings while running the language validator
-      for the function (Itagaki Takahiro)
-     </para>
-
-     <para>
-      This avoids failures if the function's code is invalid without the
-      setting; an example is that SQL functions may not parse if the
-      <varname>search_path</> is not correct.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do constraint exclusion for inherited <command>UPDATE</> and
-      <command>DELETE</> target tables when
-      <varname>constraint_exclusion</> = <literal>partition</> (Tom)
-     </para>
-
-     <para>
-      Due to an oversight, this setting previously only caused constraint
-      exclusion to be checked in <command>SELECT</> commands.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not allow an unprivileged user to reset superuser-only parameter
-      settings (Alvaro)
-     </para>
-
-     <para>
-      Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
-      ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
-      a database he owns, this would remove all special parameter settings
-      for the user or database, even ones that are only supposed to be
-      changeable by a superuser.  Now, the <command>ALTER</> will only
-      remove the parameters that the user has permission to change.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crash during backend shutdown if shutdown occurs
-      when a <literal>CONTEXT</> addition would be made to log entries (Tom)
-     </para>
-
-     <para>
-      In some cases the context-printing function would fail because the
-      current transaction had already been rolled back when it came time
-      to print a log message.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix erroneous handling of <literal>%r</> parameter in
-      <varname>recovery_end_command</> (Heikki)
-     </para>
-
-     <para>
-      The value always came out zero.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure the archiver process responds to changes in
-      <varname>archive_command</> as soon as possible (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix pl/pgsql's <literal>CASE</> statement to not fail when the
-      case expression is a query that returns no rows (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update pl/perl's <filename>ppport.h</> for modern Perl versions
-      (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Handle empty-string connect parameters properly in ecpg (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite recursion in <application>psql</> when expanding
-      a variable that refers to itself (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>psql</>'s <literal>\copy</> to not add spaces around
-      a dot within <literal>\copy (select ...)</> (Tom)
-     </para>
-
-     <para>
-      Addition of spaces around the decimal point in a numeric literal would
-      result in a syntax error.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid formatting failure in <application>psql</> when running in a
-      locale context that doesn't match the <varname>client_encoding</>
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix unnecessary <quote>GIN indexes do not support whole-index scans</>
-      errors for unsatisfiable queries using <filename>contrib/intarray</>
-      operators (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
-      interrupts promptly (Tatsuhito Kasahara)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make server startup deal properly with the case that
-      <function>shmget()</> returns <literal>EINVAL</> for an existing
-      shared memory segment (Tom)
-     </para>
-
-     <para>
-      This behavior has been observed on BSD-derived kernels including OS X.
-      It resulted in an entirely-misleading startup failure complaining that
-      the shared memory request size was too large.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid possible crashes in syslogger process on Windows (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Deal more robustly with incomplete time zone information in the
-      Windows registry (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update the set of known Windows time zone names (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010j
-      for DST law changes in Argentina, Australian Antarctic, Bangladesh,
-      Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia;
-      also historical corrections for Taiwan.
-     </para>
-
-     <para>
-      Also, add <literal>PKST</> (Pakistan Summer Time) to the default set of
-      timezone abbreviations.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-4-3">
-  <title>Release 8.4.3</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-03-15</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.4.2.
-   For information about new features in the 8.4 major release, see
-   <xref linkend="release-8-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.4.3</title>
-
-   <para>
-    A dump/restore is not required for those running 8.4.X.
-    However, if you are upgrading from a version earlier than 8.4.2,
-    see the release notes for 8.4.2.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Add new configuration parameter <varname>ssl_renegotiation_limit</> to
-      control how often we do session key renegotiation for an SSL connection
-      (Magnus)
-     </para>
-
-     <para>
-      This can be set to zero to disable renegotiation completely, which may
-      be required if a broken SSL library is used.  In particular, some
-      vendors are shipping stopgap patches for CVE-2009-3555 that cause
-      renegotiation attempts to fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible deadlock during backend startup (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes due to not handling errors during relcache reload
-      cleanly (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash due to use of dangling pointer to a cached plan
-      (Tatsuo)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash due to overenthusiastic invalidation of cached
-      plan for <command>ROLLBACK</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crashes when trying to recover from a failure in
-      subtransaction start (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix server memory leak associated with use of savepoints and a client
-      encoding different from server's encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect WAL data emitted during end-of-recovery cleanup of a GIST
-      index page split (Yoichi Hirai)
-     </para>
-
-     <para>
-      This would result in index corruption, or even more likely an error
-      during WAL replay, if we were unlucky enough to crash during
-      end-of-recovery cleanup after having completed an incomplete GIST
-      insertion.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in WAL redo cleanup method for GIN indexes (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect comparison of scan key in GIN index search (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>substring()</> for <type>bit</> types treat any negative
-      length as meaning <quote>all the rest of the string</> (Tom)
-     </para>
-
-     <para>
-      The previous coding treated only -1 that way, and would produce an
-      invalid result value for other negative values, possibly leading to
-      a crash (CVE-2010-0442).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix integer-to-bit-string conversions to handle the first fractional
-      byte correctly when the output bit width is wider than the given
-      integer by something other than a multiple of 8 bits (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some cases of pathologically slow regular expression matching (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug occurring when trying to inline a SQL function that returns
-      a set of a composite type that contains dropped columns (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug with trying to update a field of an element of a
-      composite-type array column (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid failure when <command>EXPLAIN</> has to print a FieldStore or
-      assignment ArrayRef expression (Tom)
-     </para>
-
-     <para>
-      These cases can arise now that <command>EXPLAIN VERBOSE</> tries to
-      print plan node target lists.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid an unnecessary coercion failure in some cases where an undecorated
-      literal string appears in a subquery within
-      <command>UNION</>/<command>INTERSECT</>/<command>EXCEPT</> (Tom)
-     </para>
-
-     <para>
-      This fixes a regression for some cases that worked before 8.4.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid undesirable rowtype compatibility check failures in some cases
-      where a whole-row Var has a rowtype that contains dropped columns (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix the <literal>STOP WAL LOCATION</> entry in backup history files to
-      report the next WAL segment's name when the end location is exactly at a
-      segment boundary (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Always pass the catalog ID to an option validator function specified in
-      <command>CREATE FOREIGN DATA WRAPPER</> (Martin Pihlak)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix some more cases of temporary-file leakage (Heikki)
-     </para>
-
-     <para>
-      This corrects a problem introduced in the previous minor release.
-      One case that failed is when a plpgsql function returning set is
-      called within another function's exception handler.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add support for doing <literal>FULL JOIN ON FALSE</> (Tom)
-     </para>
-
-     <para>
-      This prevents a regression from pre-8.4 releases for some queries that
-      can now be simplified to a constant-false join condition.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve constraint exclusion processing of boolean-variable cases,
-      in particular make it possible to exclude a partition that has a
-      <quote>bool_column = false</> constraint (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent treating an <literal>INOUT</> cast as representing binary
-      compatibility (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Include column name in the message when warning about inability to
-      grant or revoke column-level privileges (Stephen Frost)
-     </para>
-
-     <para>
-      This is more useful than before and helps to prevent confusion when
-      a <command>REVOKE</> generates multiple messages, which formerly
-      appeared to be duplicates.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      When reading <filename>pg_hba.conf</> and related files, do not treat
-      <literal>@something</> as a file inclusion request if the <literal>@</>
-      appears inside quote marks; also, never treat <literal>@</> by itself
-      as a file inclusion request (Tom)
-     </para>
-
-     <para>
-      This prevents erratic behavior if a role or database name starts with
-      <literal>@</>.  If you need to include a file whose path name
-      contains spaces, you can still do so, but you must write
-      <literal>@"/path to/file"</> rather than putting the quotes around
-      the whole construct.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite loop on some platforms if a directory is named as
-      an inclusion target in <filename>pg_hba.conf</> and related files
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible infinite loop if <function>SSL_read</> or
-      <function>SSL_write</> fails without setting <varname>errno</> (Tom)
-     </para>
-
-     <para>
-      This is reportedly possible with some Windows versions of
-      <application>openssl</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <acronym>GSSAPI</> authentication on local connections,
-      since it requires a hostname to function correctly (Magnus)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Protect <application>ecpg</> against applications freeing strings
-      unexpectedly (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <application>ecpg</> report the proper SQLSTATE if the connection
-      disappears (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix translation of cell contents in <application>psql</> <literal>\d</>
-      output (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>psql</>'s <literal>numericlocale</> option to not
-      format strings it shouldn't in latex and troff output formats (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a small per-query memory leak in <application>psql</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <application>psql</> return the correct exit status (3) when
-      <literal>ON_ERROR_STOP</> and <literal>--single-transaction</> are
-      both specified and an error occurs during the implied <command>COMMIT</>
-      (Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_dump</>'s output of permissions for foreign servers
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash in parallel <application>pg_restore</> due to
-      out-of-range dependency IDs (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix plpgsql failure in one case where a composite column is set to NULL
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible failure when calling PL/Perl functions from PL/PerlU
-      or vice versa (Tim Bunce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>volatile</> markings in PL/Python to avoid possible
-      compiler-specific misbehavior (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
-     </para>
-
-     <para>
-      The only known symptom of this oversight is that the Tcl
-      <literal>clock</> command misbehaves if using Tcl 8.5 or later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent <function>ExecutorEnd</> from being run on portals created
-      within a failed transaction or subtransaction (Tom)
-     </para>
-
-     <para>
-      This is known to cause issues when using
-      <filename>contrib/auto_explain</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent crash in <filename>contrib/dblink</> when too many key
-      columns are specified to a <function>dblink_build_sql_*</> function
-      (Rushabh Lathia, Joe Conway)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow zero-dimensional arrays in <filename>contrib/ltree</> operations
-      (Tom)
-     </para>
-
-     <para>
-      This case was formerly rejected as an error, but it's more convenient to
-      treat it the same as a zero-element array.  In particular this avoids
-      unnecessary failures when an <type>ltree</> operation is applied to the
-      result of <literal>ARRAY(SELECT ...)</> and the sub-select returns no
-      rows.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted crashes in <filename>contrib/xml2</> caused by sloppy
-      memory management (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make building of <filename>contrib/xml2</> more robust on Windows
-      (Andrew)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix race condition in Windows signal handling (Radu Ilie)
-     </para>
-
-     <para>
-      One known symptom of this bug is that rows in <structname>pg_listener</>
-      could be dropped under heavy load.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make the configure script report failure if the C compiler does
-      not provide a working 64-bit integer datatype (Tom)
-     </para>
-
-     <para>
-      This case has been broken for some time, and no longer seems worth
-      supporting, so just reject it at configure time instead.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010e
-      for DST law changes in Bangladesh, Chile, Fiji, Mexico, Paraguay, Samoa.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-4-2">
-  <title>Release 8.4.2</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2009-12-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.4.1.
-   For information about new features in the 8.4 major release, see
-   <xref linkend="release-8-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.4.2</title>
-
-   <para>
-    A dump/restore is not required for those running 8.4.X.
-    However, if you have any hash indexes,
-    you should <command>REINDEX</> them after updating to 8.4.2,
-    to repair possible damage.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Protect against indirect security threats caused by index functions
-      changing session-local state (Gurjeet Singh, Tom)
-     </para>
-
-     <para>
-      This change prevents allegedly-immutable index functions from possibly
-      subverting a superuser's session (CVE-2009-4136).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Reject SSL certificates containing an embedded null byte in the common
-      name (CN) field (Magnus)
-     </para>
-
-     <para>
-      This prevents unintended matching of a certificate to a server or client
-      name during SSL validation (CVE-2009-4034).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix hash index corruption (Tom)
-     </para>
-
-     <para>
-      The 8.4 change that made hash indexes keep entries sorted by hash value
-      failed to update the bucket splitting and compaction routines to
-      preserve the ordering.  So application of either of those operations
-      could lead to permanent corruption of an index, in the sense that
-      searches might fail to find entries that are present.  To deal with
-      this, it is recommended to <literal>REINDEX</> any hash indexes you may
-      have after installing this update.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash during backend-startup-time cache initialization (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid crash on empty thesaurus dictionary (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent signals from interrupting <literal>VACUUM</> at unsafe times
-      (Alvaro)
-     </para>
-
-     <para>
-      This fix prevents a PANIC if a <literal>VACUUM FULL</> is cancelled
-      after it's already committed its tuple movements, as well as transient
-      errors if a plain <literal>VACUUM</> is interrupted after having
-      truncated the table.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible crash due to integer overflow in hash table size
-      calculation (Tom)
-     </para>
-
-     <para>
-      This could occur with extremely large planner estimates for the size of
-      a hashjoin's result.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash if a <literal>DROP</> is attempted on an internally-dependent
-      object (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix very rare crash in <type>inet</>/<type>cidr</> comparisons (Chris
-      Mikkelson)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that shared tuple-level locks held by prepared transactions are
-      not ignored (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix premature drop of temporary files used for a cursor that is accessed
-      within a subtransaction (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak in syslogger process when rotating to a new CSV logfile
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak in postmaster when re-parsing <filename>pg_hba.conf</>
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix Windows permission-downgrade logic (Jesse Morris)
-     </para>
-
-     <para>
-      This fixes some cases where the database failed to start on Windows,
-      often with misleading error messages such as <quote>could not locate
-      matching postgres executable</quote>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <literal>FOR UPDATE/SHARE</> in the primary query not propagate
-      into <literal>WITH</> queries (Tom)
-     </para>
-
-     <para>
-      For example, in
-<programlisting>
-WITH w AS (SELECT * FROM foo) SELECT * FROM w, bar ... FOR UPDATE
-</programlisting>
-      the <literal>FOR UPDATE</> will now affect <literal>bar</> but not
-      <literal>foo</>.  This is more useful and consistent than the original
-      8.4 behavior, which tried to propagate <literal>FOR UPDATE</> into the
-      <literal>WITH</> query but always failed due to assorted implementation
-      restrictions.  It also follows the design rule that <literal>WITH</>
-      queries are executed as if independent of the main query.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug with a <literal>WITH RECURSIVE</> query immediately inside
-      another one (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix concurrency bug in hash indexes (Tom)
-     </para>
-
-     <para>
-      Concurrent insertions could cause index scans to transiently report
-      wrong results.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect logic for GiST index page splits, when the split depends
-      on a non-first column of the index (Paul Ramsey)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix wrong search results for a multi-column GIN index with
-      <literal>fastupdate</> enabled (Teodor)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bugs in WAL entry creation for GIN indexes (Tom)
-     </para>
-
-     <para>
-      These bugs were masked when <varname>full_page_writes</> was on, but
-      with it off a WAL replay failure was certain if a crash occurred before
-      the next checkpoint.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Don't error out if recycling or removing an old WAL file fails at the
-      end of checkpoint (Heikki)
-     </para>
-
-     <para>
-      It's better to treat the problem as non-fatal and allow the checkpoint
-      to complete.  Future checkpoints will retry the removal.  Such problems
-      are not expected in normal operation, but have been seen to be
-      caused by misdesigned Windows anti-virus and backup software.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure WAL files aren't repeatedly archived on Windows (Heikki)
-     </para>
-
-     <para>
-      This is another symptom that could happen if some other process
-      interfered with deletion of a no-longer-needed file.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PAM password processing to be more robust (Tom)
-     </para>
-
-     <para>
-      The previous code is known to fail with the combination of the Linux
-      <literal>pam_krb5</> PAM module with Microsoft Active Directory as the
-      domain controller.  It might have problems elsewhere too, since it was
-      making unjustified assumptions about what arguments the PAM stack would
-      pass to it.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Raise the maximum authentication token (Kerberos ticket) size in GSSAPI
-      and SSPI authentication methods (Ian Turner)
-     </para>
-
-     <para>
-      While the old 2000-byte limit was more than enough for Unix Kerberos
-      implementations, tickets issued by Windows Domain Controllers can be
-      much larger.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that domain constraints are enforced in constructs like
-      <literal>ARRAY[...]::domain</>, where the domain is over an array type
-      (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix foreign-key logic for some cases involving composite-type columns
-      as foreign keys (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that a cursor's snapshot is not modified after it is created
-      (Alvaro)
-     </para>
-
-     <para>
-      This could lead to a cursor delivering wrong results if later operations
-      in the same transaction modify the data the cursor is supposed to return.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <literal>CREATE TABLE</> to properly merge default expressions
-      coming from different inheritance parent tables (Tom)
-     </para>
-
-     <para>
-      This used to work but was broken in 8.4.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Re-enable collection of access statistics for sequences (Akira Kurosawa)
-     </para>
-
-     <para>
-      This used to work but was broken in 8.3.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix processing of ownership dependencies during <literal>CREATE OR
-      REPLACE FUNCTION</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect handling of <literal>WHERE</>
-      <replaceable>x</>=<replaceable>x</> conditions (Tom)
-     </para>
-
-     <para>
-      In some cases these could get ignored as redundant, but they aren't
-      &mdash; they're equivalent to <replaceable>x</> <literal>IS NOT NULL</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect plan construction when using hash aggregation to implement
-      <literal>DISTINCT</> for textually identical volatile expressions (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix Assert failure for a volatile <literal>SELECT DISTINCT ON</>
-      expression (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <function>ts_stat()</> to not fail on an empty <type>tsvector</>
-      value (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make text search parser accept underscores in XML attributes (Peter)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix encoding handling in <type>xml</> binary input (Heikki)
-     </para>
-
-     <para>
-      If the XML header doesn't specify an encoding, we now assume UTF-8 by
-      default; the previous handling was inconsistent.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug with calling <literal>plperl</> from <literal>plperlu</> or vice
-      versa (Tom)
-     </para>
-
-     <para>
-      An error exit from the inner function could result in crashes due to
-      failure to re-select the correct Perl interpreter for the outer function.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix session-lifespan memory leak when a PL/Perl function is redefined
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that Perl arrays are properly converted to
-      <productname>PostgreSQL</> arrays when returned by a set-returning
-      PL/Perl function (Andrew Dunstan, Abhijit Menon-Sen)
-     </para>
-
-     <para>
-      This worked correctly already for non-set-returning functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix rare crash in exception processing in PL/Python (Peter)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</> problem with comments in <literal>DECLARE
-      CURSOR</> statements (Michael)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>ecpg</> to not treat recently-added keywords as
-      reserved words (Tom)
-     </para>
-
-     <para>
-      This affected the keywords <literal>CALLED</>, <literal>CATALOG</>,
-      <literal>DEFINER</>, <literal>ENUM</>, <literal>FOLLOWING</>,
-      <literal>INVOKER</>, <literal>OPTIONS</>, <literal>PARTITION</>,
-      <literal>PRECEDING</>, <literal>RANGE</>, <literal>SECURITY</>,
-      <literal>SERVER</>, <literal>UNBOUNDED</>, and <literal>WRAPPER</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Re-allow regular expression special characters in <application>psql</>'s
-      <literal>\df</> function name parameter (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In <filename>contrib/fuzzystrmatch</>, correct the calculation of
-      <function>levenshtein</> distances with non-default costs (Marcin Mank)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In <filename>contrib/pg_standby</>, disable triggering failover with a
-      signal on Windows (Fujii Masao)
-     </para>
-
-     <para>
-      This never did anything useful, because Windows doesn't have Unix-style
-      signals, but recent changes made it actually crash.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Put <literal>FREEZE</> and <literal>VERBOSE</> options in the right
-      order in the <literal>VACUUM</> command that
-      <filename>contrib/vacuumdb</> produces (Heikki)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible leak of connections when <filename>contrib/dblink</>
-      encounters an error (Tatsuhito Kasahara)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure <application>psql</>'s flex module is compiled with the correct
-      system header definitions (Tom)
-     </para>
-
-     <para>
-      This fixes build failures on platforms where
-      <literal>--enable-largefile</> causes incompatible changes in the
-      generated code.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make the postmaster ignore any <literal>application_name</> parameter in
-      connection request packets, to improve compatibility with future libpq
-      versions (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update the timezone abbreviation files to match current reality (Joachim
-      Wieland)
-     </para>
-
-     <para>
-      This includes adding <literal>IDT</> to the default
-      timezone abbreviation set.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009s
-      for DST law changes in Antarctica, Argentina, Bangladesh, Fiji,
-      Novokuznetsk, Pakistan, Palestine, Samoa, Syria; also historical
-      corrections for Hong Kong.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-4-1">
-  <title>Release 8.4.1</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2009-09-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 8.4.
-   For information about new features in the 8.4 major release, see
-   <xref linkend="release-8-4">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 8.4.1</title>
-
-   <para>
-    A dump/restore is not required for those running 8.4.X.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Fix WAL page header initialization at the end of archive recovery
-      (Heikki)
-     </para>
-
-     <para>
-      This could lead to failure to process the WAL in a subsequent
-      archive recovery.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>cannot make new WAL entries during recovery</> error (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix problem that could make expired rows visible after a crash (Tom)
-     </para>
-
-     <para>
-      This bug involved a page status bit potentially not being set
-      correctly after a server crash.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Disallow <command>RESET ROLE</> and <command>RESET SESSION
-      AUTHORIZATION</> inside security-definer functions (Tom, Heikki)
-     </para>
-
-     <para>
-      This covers a case that was missed in the previous patch that
-      disallowed <command>SET ROLE</> and <command>SET SESSION
-      AUTHORIZATION</> inside security-definer functions.
-      (See CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>LOAD</> of an already-loaded loadable module
-      into a no-op (Tom)
-     </para>
-
-     <para>
-      Formerly, <command>LOAD</> would attempt to unload and re-load the
-      module, but this is unsafe and not all that useful.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make window function <literal>PARTITION BY</> and <literal>ORDER BY</>
-      items always be interpreted as simple expressions (Tom)
-     </para>
-
-     <para>
-      In 8.4.0 these lists were parsed following the rules used for
-      top-level <literal>GROUP BY</> and <literal>ORDER BY</> lists.
-      But this was not correct per the SQL standard, and it led to possible
-      circularity.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix several errors in planning of semi-joins (Tom)
-     </para>
-
-     <para>
-      These led to wrong query results in some cases where <literal>IN</>
-      or <literal>EXISTS</> was used together with another join.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix handling of whole-row references to subqueries that are within
-      an outer join (Tom)
-     </para>
-
-     <para>
-      An example is
-      <literal>SELECT COUNT(ss.*) FROM ... LEFT JOIN (SELECT ...) ss ON ...</>.
-      Here, <literal>ss.*</> would be treated as <literal>ROW(NULL,NULL,...)</>
-      for null-extended join rows, which is not the same as a simple NULL.
-      Now it is treated as a simple NULL.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix Windows shared-memory allocation code (Tsutomu Yamada, Magnus)
-     </para>
-
-     <para>
-      This bug led to the often-reported <quote>could not reattach
-      to shared memory</> error message.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix locale handling with plperl (Heikki)
-     </para>
-
-     <para>
-      This bug could cause the server's locale setting to change when a
-      plperl function is called, leading to data corruption.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix handling of reloptions to ensure setting one option doesn't
-      force default values for others (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure that a <quote>fast shutdown</> request will forcibly terminate
-      open sessions, even if a <quote>smart shutdown</> was already in progress
-      (Fujii Masao)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid memory leak for <function>array_agg()</> in <literal>GROUP BY</>
-      queries (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Treat <function>to_char(..., 'TH')</> as an uppercase ordinal
-      suffix with <literal>'HH'</>/<literal>'HH12'</> (Heikki)
-     </para>
-
-     <para>
-      It was previously handled as <literal>'th'</> (lowercase).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Include the fractional part in the result of
-      <function>EXTRACT(second)</> and
-      <function>EXTRACT(milliseconds)</> for
-      <type>time</> and <type>time with time zone</> inputs (Tom)
-     </para>
-
-     <para>
-      This has always worked for floating-point datetime configurations,
-      but was broken in the integer datetime code.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix overflow for <literal>INTERVAL '<replaceable>x</> ms'</literal>
-      when <replaceable>x</> is more than 2 million and integer
-      datetimes are in use (Alex Hunsaker)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve performance when processing toasted values in index scans (Tom)
-     </para>
-
-     <para>
-      This is particularly useful for <ulink
-      url="http://postgis.refractions.net/">PostGIS</ulink>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix a typo that disabled <varname>commit_delay</> (Jeff Janes)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Output early-startup messages to <filename>postmaster.log</> if the
-      server is started in silent mode (Tom)
-     </para>
-
-     <para>
-      Previously such error messages were discarded, leading to
-      difficulty in debugging.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Remove translated FAQs (Peter)
-     </para>
-
-     <para>
-      They are now on the <ulink
-      url="http://wiki.postgresql.org/wiki/FAQ">wiki</ulink>.  The
-      main FAQ was moved to the wiki some time ago.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>pg_ctl</> to not go into an infinite loop if
-      <filename>postgresql.conf</> is empty (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix several errors in <application>pg_dump</>'s
-      <literal>--binary-upgrade</> mode (Bruce, Tom)
-     </para>
-
-     <para>
-      <literal>pg_dump --binary-upgrade</> is used by pg_migrator.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <filename>contrib/xml2</>'s <function>xslt_process()</> to
-      properly handle the maximum number of parameters (twenty) (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve robustness of <application>libpq</>'s code to recover
-      from errors during <command>COPY FROM STDIN</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid including conflicting readline and editline header files
-      when both libraries are installed (Zdenek Kotala)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Work around gcc bug that causes <quote>floating-point exception</>
-      instead of <quote>division by zero</> on some platforms (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2009l
-      for DST law changes in Bangladesh, Egypt, Mauritius.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-8-4">
-  <title>Release 8.4</title>
-
-  <note>
-   <title>Release date</title>
-   <simpara>2009-07-01</simpara>
-  </note>
-
-  <sect2>
-   <title>Overview</title>
-
-   <para>
-    After many years of development, <productname>PostgreSQL</> has
-    become feature-complete in many areas.   This release shows a
-    targeted approach to adding features (e.g., authentication,
-    monitoring, space reuse), and adds capabilities defined in the
-    later SQL standards.  The major areas of enhancement are:
-   </para>
-
-   <itemizedlist>
-
-    <!-- This list duplicates items below, but without authors or details-->
-
-    <listitem>
-     <para>
-      Windowing Functions
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Common Table Expressions and Recursive Queries
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Default and variadic parameters for functions
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Parallel Restore
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Column Permissions
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Per-database locale settings
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improved hash indexes
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improved join performance for <literal>EXISTS</> and <literal>NOT EXISTS</> queries
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Easier-to-use Warm Standby
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Automatic sizing of the Free Space Map
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Visibility Map (greatly reduces vacuum overhead for slowly-changing tables)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Version-aware psql (backslash commands work against older servers)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Support SSL certificates for user authentication
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Per-function runtime statistics
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Easy editing of functions in psql
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New contrib modules: pg_stat_statements, auto_explain, citext, btree_gin
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <para>
-    The above items are explained in more detail in the sections below.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Migration to Version 8.4</title>
-
-   <para>
-    A dump/restore using <application>pg_dump</application> is
-    required for those wishing to migrate data from any previous
-    release.
-   </para>
-
-   <para>
-    Observe the following incompatibilities:
-   </para>
-
-   <sect3>
-    <title>General</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Use 64-bit integer datetimes by default (Neil Conway)
-      </para>
-
-      <para>
-       Previously this was selected by <application>configure</>'s
-       <option>--enable-integer-datetimes</> option.  To retain
-       the old behavior, build with <option>--disable-integer-datetimes</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <application>ipcclean</> utility command (Bruce)
-      </para>
-
-      <para>
-       The utility only worked on a few platforms.  Users should use
-       their operating system tools instead.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Server Settings</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Change default setting for
-       <literal>log_min_messages</> to <literal>warning</> (previously
-       it was <literal>notice</>) to reduce log file volume (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change default setting for <literal>max_prepared_transactions</> to
-       zero (previously it was 5) (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <literal>debug_print_parse</>, <literal>debug_print_rewritten</>,
-       and <literal>debug_print_plan</>
-       output appear at <literal>LOG</> message level, not
-       <literal>DEBUG1</> as formerly (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <literal>debug_pretty_print</> default to <literal>on</> (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <varname>explain_pretty_print</> parameter (no longer needed) (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <varname>log_temp_files</> settable by superusers only, like other
-       logging options (Simon Riggs)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove automatic appending of the epoch timestamp when no <literal>%</>
-       escapes are present in <literal>log_filename</> (Robert Haas)
-      </para>
-
-      <para>
-       This change was made because some users wanted a fixed log filename,
-       for use with an external log rotation tool.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <varname>log_restartpoints</> from <filename>recovery.conf</>;
-       instead use <varname>log_checkpoints</> (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <varname>krb_realm</> and <varname>krb_server_hostname</>;
-       these are now set in <filename>pg_hba.conf</> instead (Magnus)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       There are also significant changes in <link
-       linkend="release-8-4-pg-hba-conf"><filename>pg_hba.conf</></link>,
-       as described below.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Queries</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Change <command>TRUNCATE</> and <command>LOCK</> to
-       apply to child tables of the specified table(s) (Peter)
-      </para>
-
-      <para>
-       These commands now accept an <literal>ONLY</> option that prevents
-       processing child tables; this option must be used if the old
-       behavior is needed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <command>SELECT DISTINCT</> and
-       <literal>UNION</>/<literal>INTERSECT</>/<literal>EXCEPT</>
-       no longer always produce sorted output (Tom)
-      </para>
-
-      <para>
-       Previously, these types of queries always removed duplicate rows
-       by means of Sort/Unique processing (i.e., sort then remove adjacent
-       duplicates).  Now they can be implemented by hashing, which will not
-       produce sorted output.  If an application relied on the output being
-       in sorted order, the recommended fix is to add an <literal>ORDER BY</>
-       clause.  As a short-term workaround, the previous behavior can be
-       restored by disabling <literal>enable_hashagg</>, but that is a very
-       performance-expensive fix.  <literal>SELECT DISTINCT ON</> never uses
-       hashing, however, so its behavior is unchanged.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Force child tables to inherit <literal>CHECK</> constraints from parents
-       (Alex Hunsaker, Nikhil Sontakke, Tom)
-      </para>
-
-      <para>
-       Formerly it was possible to drop such a constraint from a child
-       table, allowing rows that violate the constraint to be visible
-       when scanning the parent table.  This was deemed inconsistent,
-       as well as contrary to SQL standard.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Disallow negative <literal>LIMIT</> or <literal>OFFSET</>
-       values, rather than treating them as zero (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Disallow <command>LOCK TABLE</> outside a transaction block
-       (Tom)
-      </para>
-
-      <para>
-       Such an operation is useless because the lock would be released
-       immediately.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Sequences now contain an additional <structfield>start_value</> column
-       (Zoltan Boszormenyi)
-      </para>
-
-      <para>
-       This supports <command>ALTER SEQUENCE ... RESTART</>.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-
-   <sect3>
-    <title>Functions and Operators</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Make <type>numeric</> zero raised to a fractional power return
-       <literal>0</>, rather than throwing an error, and make
-       <type>numeric</> zero raised to the zero power return <literal>1</>,
-       rather than error (Bruce)
-      </para>
-
-      <para>
-       This matches the longstanding <type>float8</> behavior.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow unary minus of floating-point values to produce minus zero (Tom)
-      </para>
-
-      <para>
-       The changed behavior is more <acronym>IEEE</>-standard
-       compliant.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Throw an error if an escape character is the last character in
-       a <literal>LIKE</> pattern (i.e., it has nothing to escape) (Tom)
-      </para>
-
-      <para>
-       Previously, such an escape character was silently ignored,
-       thus possibly masking application logic errors.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <literal>~=~</> and <literal>~&lt;&gt;~</> operators
-       formerly used for <literal>LIKE</> index comparisons (Tom)
-      </para>
-
-      <para>
-       Pattern indexes now use the regular equality operator.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>xpath()</> now passes its arguments to <application>libxml</>
-       without any changes (Andrew)
-      </para>
-
-      <para>
-       This means that the XML argument must be a well-formed XML document.
-       The previous coding attempted to allow XML fragments, but it did not
-       work well.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <function>xmlelement()</> format attribute values just like
-       content values (Peter)
-      </para>
-
-      <para>
-       Previously, attribute values were formatted according to the
-       normal SQL output behavior, which is sometimes at odds with
-       XML rules.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Rewrite memory management for <application>libxml</>-using functions
-       (Tom)
-      </para>
-
-      <para>
-       This change should avoid some compatibility problems with use of
-       <application>libxml</> in PL/Perl and other add-on code.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Adopt a faster algorithm for hash functions (Kenneth Marshall,
-       based on work of Bob Jenkins)
-      </para>
-
-      <para>
-       Many of the built-in hash functions now deliver different results on
-       little-endian and big-endian platforms.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title>Temporal Functions and Operators</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        <varname>DateStyle</> no longer controls <type>interval</> output
-        formatting; instead there is a new variable <varname>IntervalStyle</>
-        (Ron Mayer)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve consistency of handling of fractional seconds in
-        <type>timestamp</> and <type>interval</> output (Ron Mayer)
-       </para>
-
-       <para>
-        This may result in displaying a different number of fractional
-        digits than before, or rounding instead of truncating.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <function>to_char()</>'s localized month/day names depend
-        on <varname>LC_TIME</>, not <varname>LC_MESSAGES</> (Euler
-        Taveira de Oliveira)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Cause <function>to_date()</> and <function>to_timestamp()</>
-        to more consistently report errors for invalid input (Brendan
-        Jurd)
-       </para>
-
-       <para>
-        Previous versions would often ignore or silently misread input
-        that did not match the format string.  Such cases will now
-        result in an error.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Fix <function>to_timestamp()</> to not require upper/lower case
-        matching for meridian (<literal>AM</>/<literal>PM</>) and era
-        (<literal>BC</>/<literal>AD</>) format designations  (Brendan
-        Jurd)
-       </para>
-
-       <para>
-        For example, input value <literal>ad</> now matches the format
-        string <literal>AD</>.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-    Below you will find a detailed account of the changes between
-    <productname>PostgreSQL</productname> 8.4 and the previous major
-    release.
-   </para>
-
-   <sect3>
-    <title>Performance</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Improve optimizer statistics calculations (Jan Urbanski, Tom)
-      </para>
-
-      <para>
-       In particular, estimates for full-text-search operators are
-       greatly improved.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>SELECT DISTINCT</> and
-       <literal>UNION</>/<literal>INTERSECT</>/<literal>EXCEPT</> to
-       use hashing (Tom)
-      </para>
-
-      <para>
-       This means that these types of queries no longer automatically
-       produce sorted output.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Create explicit concepts of semi-joins and anti-joins (Tom)
-      </para>
-
-      <para>
-       This work formalizes our previous ad-hoc treatment of <literal>IN
-       (SELECT ...)</> clauses, and extends it to <literal>EXISTS</> and
-       <literal>NOT EXISTS</> clauses.  It should result in significantly
-       better planning of <literal>EXISTS</> and <literal>NOT EXISTS</>
-       queries.  In general, logically equivalent <literal>IN</> and
-       <literal>EXISTS</> clauses should now have similar performance,
-       whereas previously <literal>IN</> often won.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve optimization of sub-selects beneath outer joins (Tom)
-      </para>
-
-      <para>
-       Formerly, a sub-select or view could not be optimized very well if it
-       appeared within the nullable side of an outer join and contained
-       non-strict expressions (for instance, constants) in its result list.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve the performance of <function>text_position()</> and
-       related functions by using Boyer-Moore-Horspool searching (David
-       Rowley)
-      </para>
-
-      <para>
-       This is particularly helpful for long search patterns.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reduce I/O load of writing the statistics collection file
-       by writing the file only when requested (Martin Pihlak)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve performance for bulk inserts (Robert Haas, Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Increase the default value of <varname>default_statistics_target</>
-       from <literal>10</> to <literal>100</> (Greg Sabino Mullane,
-       Tom)
-      </para>
-
-      <para>
-       The maximum value was also increased from <literal>1000</> to
-       <literal>10000</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Perform <varname>constraint_exclusion</> checking by default
-       in queries involving inheritance or <literal>UNION ALL</> (Tom)
-      </para>
-
-      <para>
-       A new <varname>constraint_exclusion</> setting,
-       <literal>partition</>, was added to specify this behavior.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow I/O read-ahead for bitmap index scans (Greg Stark)
-      </para>
-
-      <para>
-       The amount of read-ahead is controlled by
-       <varname>effective_io_concurrency</>.  This feature is available only
-       if the kernel has <function>posix_fadvise()</> support.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Inline simple set-returning <acronym>SQL</> functions in
-       <literal>FROM</> clauses (Richard Rowell)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve performance of multi-batch hash joins by providing a special
-       case for join key values that are especially common in the outer
-       relation (Bryce Cutt, Ramon Lawrence)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reduce volume of temporary data in multi-batch hash joins
-       by suppressing <quote>physical tlist</> optimization (Michael
-       Henderson, Ramon Lawrence)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Avoid waiting for idle-in-transaction sessions during
-       <command>CREATE INDEX CONCURRENTLY</> (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve performance of shared cache invalidation (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Server</title>
-
-    <sect4>
-     <title>Settings</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Convert many <filename>postgresql.conf</> settings to enumerated
-        values so that <literal>pg_settings</> can display the valid
-        values (Magnus)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <varname>cursor_tuple_fraction</> parameter to control the
-        fraction of a cursor's rows that the planner assumes will be
-        fetched (Robert Hell)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow underscores in the names of custom variable
-        classes in <filename>postgresql.conf</> (Tom)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Authentication and security</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Remove support for the (insecure) <literal>crypt</> authentication method
-        (Magnus)
-       </para>
-
-       <para>
-        This effectively obsoletes pre-<productname>PostgreSQL</> 7.2 client
-        libraries, as there is no longer any non-plaintext password method that
-        they can use.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support regular expressions in <filename>pg_ident.conf</>
-        (Magnus)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <productname>Kerberos</>/<acronym>GSSAPI</> parameters
-        to be changed without restarting the postmaster (Magnus)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support <acronym>SSL</> certificate chains in server certificate
-        file (Andrew Gierth)
-       </para>
-
-       <para>
-        Including the full certificate chain makes the client able
-        to verify the certificate without having all intermediate CA
-        certificates present in the local store, which is often the case for
-        commercial CAs.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Report appropriate error message for combination of <literal>MD5</>
-        authentication and <varname>db_user_namespace</> enabled (Bruce)
-       </para>
-      </listitem>
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4 id="release-8-4-pg-hba-conf">
-     <title><filename>pg_hba.conf</></title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Change all authentication options to use <literal>name=value</>
-        syntax (Magnus)
-       </para>
-
-       <para>
-        This makes incompatible changes to the <literal>ldap</>,
-        <literal>pam</> and <literal>ident</> authentication methods. All
-        <filename>pg_hba.conf</> entries with these methods need to be
-        rewritten using the new format.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Remove the <literal>ident sameuser</> option, instead making that
-        behavior the default if no usermap is specified (Magnus)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow a usermap parameter for all external authentication methods
-        (Magnus)
-       </para>
-
-       <para>
-        Previously a usermap was only supported for <literal>ident</>
-        authentication.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <literal>clientcert</> option to control requesting of a
-        client certificate (Magnus)
-       </para>
-
-       <para>
-        Previously this was controlled by the presence of a root
-        certificate file in the server's data directory.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <literal>cert</> authentication method to allow
-        <emphasis>user</> authentication via <acronym>SSL</> certificates
-        (Magnus)
-       </para>
-
-       <para>
-        Previously <acronym>SSL</> certificates could only verify that
-        the client had access to a certificate, not authenticate a
-        user.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <literal>krb5</>, <literal>gssapi</> and <literal>sspi</>
-        realm and <literal>krb5</> host settings to be specified in
-        <filename>pg_hba.conf</> (Magnus)
-       </para>
-
-       <para>
-        These override the settings in <filename>postgresql.conf</>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <varname>include_realm</> parameter for <literal>krb5</>,
-        <literal>gssapi</>, and <literal>sspi</> methods (Magnus)
-       </para>
-
-       <para>
-        This allows identical usernames from different realms to be
-        authenticated as different database users using usermaps.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Parse <filename>pg_hba.conf</> fully when it is loaded,
-        so that errors are reported immediately (Magnus)
-       </para>
-
-       <para>
-        Previously, most errors in the file wouldn't be detected until clients
-        tried to connect, so an erroneous file could render the system
-        unusable.  With the new behavior, if an error is detected during
-        reload then the bad file is rejected and the postmaster continues
-        to use its old copy.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Show all parsing errors in <filename>pg_hba.conf</> instead of
-        aborting after the first one (Selena Deckelmann)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support <literal>ident</> authentication over Unix-domain sockets
-        on <productname>Solaris</> (Garick Hamlin)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Continuous Archiving</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Provide an option to <function>pg_start_backup()</> to force its
-        implied checkpoint to finish as quickly as possible (Tom)
-       </para>
-
-       <para>
-        The default behavior avoids excess I/O consumption, but that is
-        pointless if no concurrent query activity is going on.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <function>pg_stop_backup()</> wait for modified <acronym>WAL</>
-        files to be archived (Simon)
-       </para>
-
-       <para>
-        This guarantees that the backup is valid at the time
-        <function>pg_stop_backup()</> completes.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        When archiving is enabled, rotate the last WAL segment at shutdown
-        so that all transactions can be archived immediately
-        (Guillaume Smet, Heikki)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Delay <quote>smart</> shutdown while a continuous archiving base backup
-        is in progress (Laurenz Albe)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Cancel a continuous archiving base backup if <quote>fast</> shutdown
-        is requested (Laurenz Albe)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <filename>recovery.conf</> boolean variables to take the
-        same range of string values as <filename>postgresql.conf</>
-        boolean variables
-        (Bruce)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Monitoring</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add <function>pg_conf_load_time()</> to report when
-        the <productname>PostgreSQL</> configuration files were last loaded
-        (George Gensure)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>pg_terminate_backend()</> to safely terminate a
-        backend (the <literal>SIGTERM</> signal works also) (Tom, Bruce)
-       </para>
-
-       <para>
-        While it's always been possible to <literal>SIGTERM</> a single
-        backend, this was previously considered unsupported; and testing
-        of the case found some bugs that are now fixed.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add ability to track user-defined functions' call counts and
-        runtimes (Martin Pihlak)
-       </para>
-
-       <para>
-        Function statistics appear in a new system view,
-        <literal>pg_stat_user_functions</>.  Tracking is controlled
-        by the new parameter <varname>track_functions</>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow specification of the maximum query string size in
-        <literal>pg_stat_activity</> via new
-        <varname>track_activity_query_size</> parameter (Thomas Lee)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Increase the maximum line length sent to <application>syslog</>, in
-        hopes of improving performance (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add read-only configuration variables <varname>segment_size</>,
-        <varname>wal_block_size</>, and <varname>wal_segment_size</>
-        (Bernd Helmle)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        When reporting a deadlock, report the text of all queries involved
-        in the deadlock to the server log  (Itagaki Takahiro)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>pg_stat_get_activity(pid)</> function to return
-        information about a specific process id (Magnus)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow the location of the server's statistics file to be specified
-        via <varname>stats_temp_directory</> (Magnus)
-       </para>
-
-       <para>
-        This allows the statistics file to be placed in a
-        <acronym>RAM</>-resident directory to reduce I/O requirements.
-        On startup/shutdown, the file is copied to its traditional location
-        (<literal>$PGDATA/global/</>) so it is preserved across restarts.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Queries</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add support for <literal>WINDOW</> functions (Hitoshi Harada)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for <literal>WITH</> clauses (CTEs), including <literal>WITH
-       RECURSIVE</> (Yoshiyuki Asaba, Tatsuo Ishii, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <command>TABLE</> command (Peter)
-      </para>
-
-      <para>
-       <literal>TABLE tablename</> is a SQL standard short-hand for
-       <literal>SELECT * FROM tablename</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>AS</> to be optional when specifying a
-       <command>SELECT</> (or <literal>RETURNING</>) column output
-       label (Hiroshi Saito)
-      </para>
-
-      <para>
-       This works so long as the column label is not any
-       <productname>PostgreSQL</> keyword; otherwise <literal>AS</> is still
-       needed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support set-returning functions in <command>SELECT</> result lists
-       even for functions that return their result via a tuplestore (Tom)
-      </para>
-
-      <para>
-       In particular, this means that functions written in PL/pgSQL
-       and other PL languages can now be called this way.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support set-returning functions in the output of aggregation
-       and grouping queries (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>SELECT FOR UPDATE</>/<literal>SHARE</> to work
-       on inheritance trees (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add infrastructure for <acronym>SQL/MED</> (Martin Pihlak,
-       Peter)
-      </para>
-
-      <para>
-       There are no remote or external <acronym>SQL/MED</> capabilities
-       yet, but this change provides a standardized and future-proof
-       system for managing connection information for modules like
-       <filename>dblink</> and <filename>plproxy</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Invalidate cached plans when referenced schemas, functions, operators,
-       or operator classes are modified (Martin Pihlak, Tom)
-      </para>
-
-      <para>
-       This improves the system's ability to respond to on-the-fly
-       DDL changes.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Allow comparison of composite types and allow arrays of
-       anonymous composite types (Tom)
-      </para>
-
-      <para>
-       This allows constructs such as
-       <literal>row(1, 1.1) = any (array[row(7, 7.7), row(1, 1.0)])</>.
-       This is particularly useful in recursive queries.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for Unicode string literal and identifier specifications
-       using code points, e.g. <literal>U&amp;'d\0061t\+000061'</>
-       (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reject <literal>\000</> in string literals and <command>COPY</> data
-       (Tom)
-      </para>
-
-      <para>
-       Previously, this was accepted but had the effect of terminating
-       the string contents.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve the parser's ability to report error locations (Tom)
-      </para>
-
-      <para>
-       An error location is now reported for many semantic errors,
-       such as mismatched datatypes, that previously could not be localized.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title><command>TRUNCATE</></title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Support statement-level <literal>ON TRUNCATE</> triggers (Simon)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <literal>RESTART</>/<literal>CONTINUE IDENTITY</> options
-        for <command>TRUNCATE TABLE</>
-        (Zoltan Boszormenyi)
-       </para>
-
-       <para>
-        The start value of a sequence can be changed by <command>ALTER
-        SEQUENCE START WITH</>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <command>TRUNCATE tab1, tab1</> to succeed (Bruce)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add a separate <command>TRUNCATE</> permission (Robert Haas)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><command>EXPLAIN</></title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Make <command>EXPLAIN VERBOSE</> show the output columns of each
-        plan node (Tom)
-       </para>
-
-       <para>
-        Previously <command>EXPLAIN VERBOSE</> output an internal
-        representation of the query plan.  (That behavior is now
-        available via <varname>debug_print_plan</>.)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>EXPLAIN</> identify subplans and initplans with
-        individual labels (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>EXPLAIN</> honor <varname>debug_print_plan</> (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <command>EXPLAIN</> on <command>CREATE TABLE AS</> (Peter)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><literal>LIMIT</>/<literal>OFFSET</></title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Allow sub-selects in <literal>LIMIT</> and <literal>OFFSET</> (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <acronym>SQL</>-standard syntax for
-        <literal>LIMIT</>/<literal>OFFSET</> capabilities (Peter)
-       </para>
-
-       <para>
-        To wit,
-        <literal>OFFSET num {ROW|ROWS} FETCH {FIRST|NEXT} [num] {ROW|ROWS}
-        ONLY</>.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Object Manipulation</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add support for column-level privileges (Stephen Frost, KaiGai
-       Kohei)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Refactor multi-object <command>DROP</> operations to reduce the
-       need for <literal>CASCADE</> (Alex Hunsaker)
-      </para>
-
-      <para>
-       For example, if table <literal>B</> has a dependency on table
-       <literal>A</>, the command <literal>DROP TABLE A, B</> no longer
-       requires the <literal>CASCADE</> option.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix various problems with concurrent <command>DROP</> commands
-       by ensuring that locks are taken before we begin to drop dependencies
-       of an object (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve reporting of dependencies during <command>DROP</>
-       commands (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>WITH [NO] DATA</> clause to <command>CREATE TABLE
-       AS</>, per the <acronym>SQL</> standard (Peter, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for user-defined I/O conversion casts (Heikki)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>CREATE AGGREGATE</> to use an <type>internal</>
-       transition datatype (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>LIKE</> clause to <command>CREATE TYPE</> (Tom)
-      </para>
-
-      <para>
-       This simplifies creation of data types that use the same internal
-       representation as an existing type.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow specification of the type category and <quote>preferred</>
-       status for user-defined base types (Tom)
-      </para>
-
-      <para>
-       This allows more control over the coercion behavior of user-defined
-       types.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>CREATE OR REPLACE VIEW</> to add columns to the
-       end of a view (Robert Haas)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title><command>ALTER</></title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add <command>ALTER TYPE RENAME</> (Petr Jelinek)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <command>ALTER SEQUENCE ... RESTART</> (with no parameter) to
-        reset a sequence to its initial value (Zoltan Boszormenyi)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Modify the <command>ALTER TABLE</> syntax to allow all reasonable
-        combinations for tables, indexes, sequences, and views (Tom)
-       </para>
-
-       <para>
-        This change allows the following new syntaxes:
-
-        <itemizedlist>
-         <listitem>
-          <para>
-           <command>ALTER SEQUENCE OWNER TO</>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <command>ALTER VIEW ALTER COLUMN SET/DROP DEFAULT</>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <command>ALTER VIEW OWNER TO</>
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           <command>ALTER VIEW SET SCHEMA</>
-          </para>
-         </listitem>
-        </itemizedlist>
-
-        There is no actual new functionality here, but formerly
-        you had to say <command>ALTER TABLE</> to do these things,
-        which was confusing.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add support for the syntax <command>ALTER TABLE ... ALTER COLUMN
-        ... SET DATA TYPE</> (Peter)
-       </para>
-
-       <para>
-        This is <acronym>SQL</>-standard syntax for functionality that
-        was already supported.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>ALTER TABLE SET WITHOUT OIDS</> rewrite the table
-        to physically remove <type>OID</> values (Tom)
-       </para>
-
-       <para>
-        Also, add <command>ALTER TABLE SET WITH OIDS</> to rewrite the
-        table to add <type>OID</>s.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Database Manipulation</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Improve reporting of
-        <command>CREATE</>/<command>DROP</>/<command>RENAME DATABASE</>
-        failure when uncommitted prepared transactions are the cause
-        (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <varname>LC_COLLATE</> and <varname>LC_CTYPE</> into
-        per-database settings (Radek Strnad, Heikki)
-       </para>
-
-       <para>
-        This makes collation similar to encoding, which was always
-        configurable per database.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve checks that the database encoding, collation
-        (<varname>LC_COLLATE</>), and character classes
-        (<varname>LC_CTYPE</>) match (Heikki, Tom)
-       </para>
-
-       <para>
-        Note in particular that a new database's encoding and locale
-        settings can be changed only when copying from <literal>template0</>.
-        This prevents possibly copying data that doesn't match the settings.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <command>ALTER DATABASE SET TABLESPACE</> to move a database
-        to a new tablespace (Guillaume Lelarge, Bernd Helmle)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Utility Operations</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add a <literal>VERBOSE</> option to the <command>CLUSTER</> command and
-       <application>clusterdb</> (Jim Cox)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Decrease memory requirements for recording pending trigger
-       events (Tom)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title>Indexes</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Dramatically improve the speed of building and accessing hash
-        indexes (Tom Raney, Shreya Bhargava)
-       </para>
-
-       <para>
-        This allows hash indexes to be sometimes faster than btree
-        indexes.  However, hash indexes are still not crash-safe.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make hash indexes store only the hash code, not the full value of
-        the indexed column (Xiao Meng)
-       </para>
-
-       <para>
-        This greatly reduces the size of hash indexes for long indexed
-        values, improving performance.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Implement fast update option for GIN indexes (Teodor, Oleg)
-       </para>
-
-       <para>
-        This option greatly improves update speed at a small penalty in search
-        speed.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <literal>xxx_pattern_ops</> indexes can now be used for simple
-        equality comparisons, not only for <literal>LIKE</> (Tom)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Full Text Indexes</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Remove the requirement to use <literal>@@@</> when doing
-        <acronym>GIN</> weighted lookups on full text indexes (Tom, Teodor)
-       </para>
-
-       <para>
-        The normal <literal>@@</> text search operator can be used
-        instead.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add an optimizer selectivity function for <literal>@@</> text
-        search operations (Jan Urbanski)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow prefix matching in full text searches (Teodor Sigaev,
-        Oleg Bartunov)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support multi-column <acronym>GIN</> indexes (Teodor Sigaev)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve support for Nepali language and Devanagari alphabet (Teodor)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><command>VACUUM</></title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Track free space in separate per-relation <quote>fork</> files (Heikki)
-       </para>
-
-       <para>
-        Free space discovered by <command>VACUUM</> is now recorded in
-        <filename>*_fsm</> files, rather than in a fixed-sized shared memory
-        area.  The <varname>max_fsm_pages</> and <varname>max_fsm_relations</>
-        settings have been removed, greatly simplifying administration of
-        free space management.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add a visibility map to track pages that do not require
-        vacuuming (Heikki)
-       </para>
-
-       <para>
-        This allows <command>VACUUM</> to avoid scanning all of
-        a table when only a portion of the table needs vacuuming.
-        The visibility map is stored in per-relation <quote>fork</> files.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <varname>vacuum_freeze_table_age</> parameter to control
-        when <command>VACUUM</> should ignore the visibility map and
-        do a full table scan to freeze tuples (Heikki)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Track transaction snapshots more carefully (Alvaro)
-       </para>
-
-       <para>
-        This improves <command>VACUUM</>'s ability to reclaim space
-        in the presence of long-running transactions.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add ability to specify per-relation autovacuum and <acronym>TOAST</>
-        parameters in <command>CREATE TABLE</> (Alvaro, Euler Taveira de
-        Oliveira)
-       </para>
-
-       <para>
-        Autovacuum options used to be stored in a system table.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <literal>--freeze</> option to <application>vacuumdb</>
-        (Bruce)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Data Types</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add a <literal>CaseSensitive</> option for text search synonym
-       dictionaries (Simon)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve the precision of <type>NUMERIC</> division (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add basic arithmetic operators for <type>int2</> with <type>int8</>
-       (Tom)
-      </para>
-
-      <para>
-       This eliminates the need for explicit casting in some situations.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <type>UUID</> input to accept an optional hyphen after
-       every fourth digit (Robert Haas)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>on</>/<literal>off</> as input for the boolean data type
-       (Itagaki Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow spaces around <literal>NaN</> in the input string for
-       type <type>numeric</> (Sam Mason)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title>Temporal Data Types</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Reject year <literal>0 BC</> and years <literal>000</> and
-        <literal>0000</> (Tom)
-       </para>
-
-       <para>
-        Previously these were interpreted as <literal>1 BC</>.
-        (Note: years <literal>0</> and <literal>00</> are still assumed to be
-        the year 2000.)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Include <literal>SGT</> (Singapore time) in the default list of
-        known time zone abbreviations (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support <literal>infinity</> and <literal>-infinity</> as
-        values of type <type>date</> (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make parsing of <type>interval</> literals more standard-compliant
-        (Tom, Ron Mayer)
-       </para>
-
-       <para>
-        For example, <literal>INTERVAL '1' YEAR</> now does what it's
-        supposed to.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <type>interval</> fractional-seconds precision to be specified
-        after the <literal>second</> keyword, for <acronym>SQL</> standard
-        compliance (Tom)
-       </para>
-
-       <para>
-        Formerly the precision had to be specified after the keyword
-        <type>interval</>.  (For backwards compatibility, this syntax is still
-        supported, though deprecated.)  Data type definitions will now be
-        output using the standard format.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support the <acronym>IS0 8601</> <type>interval</> syntax (Ron
-        Mayer, Kevin Grittner)
-       </para>
-
-       <para>
-        For example, <literal>INTERVAL 'P1Y2M3DT4H5M6.7S'</> is now
-        supported.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <varname>IntervalStyle</> parameter
-        which controls how <type>interval</> values are output (Ron Mayer)
-       </para>
-
-       <para>
-        Valid values are:  <literal>postgres</>, <literal>postgres_verbose</>,
-        <literal>sql_standard</>, <literal>iso_8601</>.  This setting also
-        controls the handling of negative <type>interval</> input when only
-        some fields have positive/negative designations.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve consistency of handling of fractional seconds in
-        <type>timestamp</> and <type>interval</> output (Ron Mayer)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Arrays</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Improve the handling of casts applied to <literal>ARRAY[]</>
-        constructs, such as <literal>ARRAY[...]::integer[]</>
-        (Brendan Jurd)
-       </para>
-
-       <para>
-        Formerly <productname>PostgreSQL</> attempted to determine a data type
-        for the <literal>ARRAY[]</> construct without reference to the ensuing
-        cast.  This could fail unnecessarily in many cases, in particular when
-        the <literal>ARRAY[]</> construct was empty or contained only
-        ambiguous entries such as <literal>NULL</>.  Now the cast is consulted
-        to determine the type that the array elements must be.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <acronym>SQL</>-syntax <type>ARRAY</> dimensions optional
-        to match the <acronym>SQL</> standard (Peter)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>array_ndims()</> to return the number
-        of dimensions of an array (Robert Haas)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>array_length()</> to return the length
-        of an array for a specified dimension (Jim Nasby, Robert
-        Haas, Peter Eisentraut)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add aggregate function <function>array_agg()</>, which
-        returns all aggregated values as a single array (Robert Haas,
-        Jeff Davis, Peter)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>unnest()</>, which converts an array to
-        individual row values (Tom)
-       </para>
-
-       <para>
-        This is the opposite of <function>array_agg()</>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>array_fill()</> to create arrays initialized with
-        a value (Pavel Stehule)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>generate_subscripts()</> to simplify generating
-        the range of an array's subscripts (Pavel Stehule)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Wide-Value Storage (<acronym>TOAST</>)</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Consider <acronym>TOAST</> compression on values as short as
-        32 bytes (previously 256 bytes) (Greg Stark)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Require 25% minimum space savings before using <acronym>TOAST</>
-        compression (previously 20% for small values and any-savings-at-all
-        for large values) (Greg)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve <acronym>TOAST</> heuristics for rows that have a mix of large
-        and small toastable fields, so that we prefer to push large values out
-        of line and don't compress small values unnecessarily (Greg, Tom)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Functions</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Document that <function>setseed()</> allows values from
-       <literal>-1</> to <literal>1</> (not just <literal>0</> to
-       <literal>1</>), and enforce the valid range (Kris Jurka)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add server-side function <function>lo_import(filename, oid)</>
-       (Tatsuo)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>quote_nullable()</>, which behaves like
-       <function>quote_literal()</> but returns the string <literal>NULL</> for
-       a null argument (Brendan Jurd)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve full text search <function>headline()</> function to
-       allow extracting several fragments of text (Sushant Sinha)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>suppress_redundant_updates_trigger()</> trigger
-       function to avoid overhead for non-data-changing updates (Andrew)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>div(numeric, numeric)</> to perform <type>numeric</>
-       division without rounding (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <type>timestamp</> and <type>timestamptz</> versions of
-       <function>generate_series()</> (Hitoshi Harada)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title>Object Information Functions</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Implement <function>current_query()</> for use by functions
-        that need to know the currently running query (Tomas Doran)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>pg_get_keywords()</> to return a list of the
-        parser keywords (Dave Page)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>pg_get_functiondef()</> to see a function's
-        definition (Abhijit Menon-Sen)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow the second argument of <function>pg_get_expr()</> to be zero
-        when deparsing an expression that does not contain variables (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Modify <function>pg_relation_size()</> to use <literal>regclass</>
-        (Heikki)
-       </para>
-
-       <para>
-        <function>pg_relation_size(data_type_name)</> no longer works.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <literal>boot_val</> and <literal>reset_val</> columns to
-        <literal>pg_settings</> output (Greg Smith)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add source file name and line number columns to
-        <literal>pg_settings</> output for variables set in a configuration
-        file (Magnus, Alvaro)
-       </para>
-
-       <para>
-        For security reasons, these columns are only visible to superusers.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add support for <varname>CURRENT_CATALOG</>,
-        <varname>CURRENT_SCHEMA</>, <varname>SET CATALOG</>, <varname>SET
-        SCHEMA</> (Peter)
-       </para>
-
-       <para>
-        These provide <acronym>SQL</>-standard syntax for existing features.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>pg_typeof()</> which returns the data type
-        of any value (Brendan Jurd)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <function>version()</> return information about whether
-        the server is a 32- or 64-bit binary (Bruce)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Fix the behavior of information schema columns
-        <structfield>is_insertable_into</> and <structfield>is_updatable</> to
-        be consistent (Peter)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve the behavior of information schema
-        <structfield>datetime_precision</> columns (Peter)
-       </para>
-
-       <para>
-        These columns now show zero for <type>date</> columns, and 6
-        (the default precision) for <type>time</>, <type>timestamp</>, and
-        <type>interval</> without a declared precision, rather than showing
-        null as formerly.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Convert remaining builtin set-returning functions to use
-        <literal>OUT</> parameters (Jaime Casanova)
-       </para>
-
-       <para>
-        This makes it possible to call these functions without specifying
-        a column list:  <function>pg_show_all_settings()</>,
-        <function>pg_lock_status()</>, <function>pg_prepared_xact()</>,
-        <function>pg_prepared_statement()</>, <function>pg_cursor()</>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <function>pg_*_is_visible()</> and
-        <function>has_*_privilege()</> functions return <literal>NULL</>
-        for invalid OIDs, rather than reporting an error (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Extend <function>has_*_privilege()</> functions to allow inquiring
-        about the OR of multiple privileges in one call (Stephen
-        Frost, Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <function>has_column_privilege()</> and
-        <function>has_any_column_privilege()</> functions (Stephen
-        Frost, Tom)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Function Creation</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Support variadic functions (functions with a variable number
-        of arguments) (Pavel Stehule)
-       </para>
-
-       <para>
-        Only trailing arguments can be optional, and they all must be
-        of the same data type.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support default values for function arguments (Pavel Stehule)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <command>CREATE FUNCTION ... RETURNS TABLE</> clause (Pavel
-        Stehule)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <acronym>SQL</>-language functions to return the output
-        of an <command>INSERT</>/<command>UPDATE</>/<command>DELETE</>
-        <literal>RETURNING</> clause (Tom)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>PL/pgSQL Server-Side Language</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Support <literal>EXECUTE USING</> for easier insertion of data
-        values into a dynamic query string (Pavel Stehule)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow looping over the results of a cursor using a <literal>FOR</>
-        loop (Pavel Stehule)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support <literal>RETURN QUERY EXECUTE</> (Pavel
-        Stehule)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve the <literal>RAISE</> command (Pavel Stehule)
-
-        <itemizedlist>
-         <listitem>
-          <para>
-           Support <literal>DETAIL</> and <literal>HINT</> fields
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           Support specification of the <literal>SQLSTATE</> error code
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           Support an exception name parameter
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-           Allow <literal>RAISE</> without parameters in an exception
-           block to re-throw the current error
-          </para>
-         </listitem>
-        </itemizedlist>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow specification of <varname>SQLSTATE</> codes
-        in <literal>EXCEPTION</> lists (Pavel Stehule)
-       </para>
-
-       <para>
-        This is useful for handling custom <varname>SQLSTATE</> codes.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support the <literal>CASE</> statement (Pavel Stehule)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>RETURN QUERY</> set the special <literal>FOUND</> and
-        <command>GET DIAGNOSTICS</> <literal>ROW_COUNT</> variables
-        (Pavel Stehule)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>FETCH</> and <command>MOVE</> set the
-        <command>GET DIAGNOSTICS</> <literal>ROW_COUNT</> variable
-        (Andrew Gierth)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>EXIT</> without a label always exit the innermost
-        loop (Tom)
-       </para>
-
-       <para>
-        Formerly, if there were a <literal>BEGIN</> block more closely nested
-        than any loop, it would exit that block instead.  The new behavior
-        matches Oracle(TM) and is also what was previously stated by our own
-        documentation.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make processing of string literals and nested block comments
-        match the main SQL parser's processing (Tom)
-       </para>
-
-       <para>
-        In particular, the format string in <command>RAISE</> now works
-        the same as any other string literal, including being subject
-        to <varname>standard_conforming_strings</>.  This change also
-        fixes other cases in which valid commands would fail when
-        <varname>standard_conforming_strings</> is on.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Avoid memory leakage when the same function is called at varying
-        exception-block nesting depths (Tom)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Client Applications</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Fix <literal>pg_ctl restart</> to preserve command-line arguments
-       (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>-w</>/<literal>--no-password</> option that
-       prevents password prompting in all utilities that have a
-       <literal>-W</>/<literal>--password</> option (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <option>-q</> (quiet) option of <application>createdb</>,
-       <application>createuser</>, <application>dropdb</>,
-       <application>dropuser</> (Peter)
-      </para>
-
-      <para>
-       These options have had no effect since <productname>PostgreSQL</>
-       8.3.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title><application>psql</></title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Remove verbose startup banner; now just suggest <literal>help</>
-        (Joshua Drake)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <literal>help</> show common backslash commands (Greg
-        Sabino Mullane)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <literal>\pset format wrapped</> mode to wrap output to the
-        screen width, or file/pipe output too if <literal>\pset columns</>
-        is set (Bryce Nesbitt)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow all supported spellings of boolean values in <command>\pset</>,
-        rather than just <literal>on</> and <literal>off</> (Bruce)
-       </para>
-
-       <para>
-        Formerly, any string other than <quote>off</> was silently taken
-        to mean <literal>true</>.  <application>psql</> will now complain
-        about unrecognized spellings (but still take them as <literal>true</>).
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Use the pager for wide output (Bruce)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Require a space between a one-letter backslash command and its first
-        argument (Bernd Helmle)
-       </para>
-
-       <para>
-        This removes a historical source of ambiguity.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve tab completion support for schema-qualified and
-        quoted identifiers (Greg Sabino Mullane)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add optional <literal>on</>/<literal>off</> argument for
-        <command>\timing</> (David Fetter)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Display access control rights on multiple lines (Brendan
-        Jurd, Andreas Scherbaum)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>\l</> show database access privileges (Andrew Gilligan)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>\l+</> show database sizes, if permissions
-        allow (Andrew Gilligan)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add the <command>\ef</> command to edit function definitions
-        (Abhijit Menon-Sen)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><application>psql</> \d* commands</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Make <command>\d*</> commands that do not have a pattern argument
-        show system objects only if the <literal>S</> modifier is specified
-        (Greg Sabino Mullane, Bruce)
-       </para>
-
-       <para>
-        The former behavior was inconsistent across different variants
-        of <command>\d</>, and in most cases it provided no easy way to see
-        just user objects.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve <command>\d*</> commands to work with older
-        <productname>PostgreSQL</> server versions (back to 7.4),
-        not only the current server version
-        (Guillaume Lelarge)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>\d</> show foreign-key constraints that reference
-        the selected table (Kenneth D'Souza)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>\d</> on a sequence show its column values
-        (Euler Taveira de Oliveira)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add column storage type and other relation options to the
-        <command>\d+</> display (Gregory Stark, Euler Taveira de
-        Oliveira)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Show relation size in <command>\dt+</> output (Dickson S.
-        Guedes)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Show the possible values of <literal>enum</> types in <command>\dT+</>
-        (David Fetter)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <command>\dC</> to accept a wildcard pattern, which matches
-        either datatype involved in the cast (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add a function type column to <command>\df</>'s output, and add
-        options to list only selected types of functions (David Fetter)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <command>\df</> not hide functions that take or return
-        type <type>cstring</> (Tom)
-       </para>
-
-       <para>
-        Previously, such functions were hidden because most of them are
-        datatype I/O functions, which were deemed uninteresting.  The new
-        policy about hiding system functions by default makes this wart
-        unnecessary.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><application>pg_dump</></title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add a <literal>--no-tablespaces</> option to
-        <application>pg_dump</>/<application>pg_dumpall</>/<application>pg_restore</>
-        so that dumps can be restored to clusters that have non-matching
-        tablespace layouts (Gavin Roy)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Remove <option>-d</> and <option>-D</> options from
-        <application>pg_dump</> and <application>pg_dumpall</> (Tom)
-       </para>
-
-       <para>
-        These options were too frequently confused with the option to
-        select a database name in other <productname>PostgreSQL</>
-        client applications.  The functionality is still available,
-        but you must now spell out the long option name
-        <option>--inserts</> or <option>--column-inserts</>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Remove <option>-i</>/<option>--ignore-version</> option from
-        <application>pg_dump</> and <application>pg_dumpall</> (Tom)
-       </para>
-
-       <para>
-        Use of this option does not throw an error, but it has no
-        effect.  This option was removed because the version checks
-        are necessary for safety.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Disable <varname>statement_timeout</> during dump and restore
-        (Joshua Drake)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <application>pg_dump</>/<application>pg_dumpall</> option
-        <option>--lock-wait-timeout</> (David Gould)
-       </para>
-
-       <para>
-        This allows dumps to fail if unable to acquire a shared lock
-        within the specified amount of time.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Reorder <application>pg_dump</> <literal>--data-only</> output
-        to dump tables referenced by foreign keys before
-        the referencing tables (Tom)
-       </para>
-
-       <para>
-        This allows data loads when foreign keys are already present.
-        If circular references make a safe ordering impossible, a
-        <literal>NOTICE</> is issued.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <application>pg_dump</>, <application>pg_dumpall</>, and
-        <application>pg_restore</> to use a specified role (Benedek
-        L&aacute;szl&oacute;)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <application>pg_restore</> to use multiple concurrent
-        connections to do the restore (Andrew)
-       </para>
-
-       <para>
-        The number of concurrent connections is controlled by the option
-        <literal>--jobs</>.  This is supported only for custom-format archives.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Programming Tools</title>
-
-    <sect4>
-     <title><application>libpq</></title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Allow the <type>OID</> to be specified when importing a large
-        object, via new function <function>lo_import_with_oid()</> (Tatsuo)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <quote>events</> support (Andrew Chernow, Merlin Moncure)
-       </para>
-
-       <para>
-        This adds the ability to register callbacks to manage private
-        data associated with <structname>PGconn</> and <structname>PGresult</>
-        objects.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve error handling to allow the return of multiple
-        error messages as multi-line error reports (Magnus)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <function>PQexecParams()</> and related functions return
-        <varname>PGRES_EMPTY_QUERY</> for an empty query (Tom)
-       </para>
-
-       <para>
-        They previously returned <varname>PGRES_COMMAND_OK</>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Document how to avoid the overhead of <function>WSACleanup()</>
-        on Windows (Andrew Chernow)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Do not rely on Kerberos tickets to determine the default database
-        username (Magnus)
-       </para>
-
-       <para>
-        Previously, a Kerberos-capable build of libpq would use the
-        principal name from any available Kerberos ticket as default
-        database username, even if the connection wasn't using Kerberos
-        authentication.  This was deemed inconsistent and confusing.
-        The default username is now determined the same way with or
-        without Kerberos.  Note however that the database username must still
-        match the ticket when Kerberos authentication is used.
-       </para>
-      </listitem>
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><application>libpq</> <acronym>SSL</> (Secure Sockets Layer)
-      support</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Fix certificate validation for <acronym>SSL</> connections
-        (Magnus)
-       </para>
-
-       <para>
-        <application>libpq</> now supports verifying both the certificate
-        and the name of the server when making <acronym>SSL</>
-        connections. If a root certificate is not available to use for
-        verification, <acronym>SSL</> connections will fail. The
-        <literal>sslmode</> parameter is used to enable certificate
-        verification and set the level of checking.
-        The default is still not to do any verification, allowing connections
-        to SSL-enabled servers without requiring a root certificate on the
-        client.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support wildcard server certificates (Magnus)
-       </para>
-
-       <para>
-        If a certificate <acronym>CN</> starts with <literal>*</>, it will
-        be treated as a wildcard when matching the hostname, allowing the
-        use of the same certificate for multiple servers.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow the file locations for client certificates to be specified
-        (Mark Woodward, Alvaro, Magnus)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add a <function>PQinitOpenSSL</> function to allow greater control
-        over OpenSSL/libcrypto initialization (Andrew Chernow)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <application>libpq</> unregister its <application>OpenSSL</>
-        callbacks when no database connections remain open
-        (Bruce, Magnus, Russell Smith)
-       </para>
-
-       <para>
-        This is required for applications that unload the libpq library,
-        otherwise invalid <application>OpenSSL</> callbacks will remain.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><application>ecpg</></title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add localization support for messages (Euler Taveira de
-        Oliveira)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        ecpg parser is now automatically generated from the server
-        parser (Michael)
-       </para>
-
-       <para>
-        Previously the ecpg parser was hand-maintained.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Server Programming Interface (<acronym>SPI</>)</title>
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add support for single-use plans with out-of-line
-        parameters (Tom)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add new <varname>SPI_OK_REWRITTEN</> return code for
-        <function>SPI_execute()</> (Heikki)
-       </para>
-
-       <para>
-        This is used when a command is rewritten to another type of
-        command.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Remove unnecessary inclusions from <filename>executor/spi.h</> (Tom)
-       </para>
-
-       <para>
-        SPI-using modules might need to add some <literal>#include</>
-        lines if they were depending on <filename>spi.h</> to include
-        things for them.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Build Options</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Update build system to use <productname>Autoconf</> 2.61 (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Require <productname>GNU bison</> for source code builds (Peter)
-      </para>
-
-      <para>
-       This has effectively been required for several years, but now there
-       is no infrastructure claiming to support other parser tools.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <application>pg_config</> <literal>--htmldir</> option
-       (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Pass <type>float4</> by value inside the server (Zoltan
-       Boszormenyi)
-      </para>
-
-      <para>
-       Add <application>configure</> option
-       <literal>--disable-float4-byval</> to use the old behavior.
-       External C functions that use old-style (version 0) call convention
-       and pass or return <type>float4</> values will be broken by this
-       change, so you may need the <application>configure</> option if you
-       have such functions and don't want to update them.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Pass <type>float8</>, <type>int8</>, and related datatypes
-       by value inside the server on 64-bit platforms (Zoltan Boszormenyi)
-      </para>
-
-      <para>
-       Add <application>configure</> option
-       <literal>--disable-float8-byval</> to use the old behavior.
-       As above, this change might break old-style external C functions.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add configure options <literal>--with-segsize</>,
-       <literal>--with-blocksize</>, <literal>--with-wal-blocksize</>,
-       <literal>--with-wal-segsize</> (Zdenek Kotala, Tom)
-      </para>
-
-      <para>
-       This simplifies build-time control over several constants that
-       previously could only be changed by editing
-       <filename>pg_config_manual.h</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow threaded builds on <productname>Solaris</> 2.5 (Bruce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use the system's <function>getopt_long()</> on <productname>Solaris</>
-       (Zdenek Kotala, Tom)
-      </para>
-
-      <para>
-       This makes option processing more consistent with what Solaris users
-       expect.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for the <productname>Sun Studio</> compiler on
-       <productname>Linux</> (Julius Stroffek)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Append the major version number to the backend <application>gettext</>
-       domain, and the <literal>soname</> major version number to
-       libraries' <application>gettext</> domain (Peter)
-      </para>
-
-      <para>
-       This simplifies parallel installations of multiple versions.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for code coverage testing with <application>gcov</>
-       (Michelle Caisse)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow out-of-tree builds on <productname>Mingw</> and
-       <productname>Cygwin</> (Richard Evans)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix the use of <productname>Mingw</> as a cross-compiling source
-       platform (Peter)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Source Code</title>
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Support 64-bit time zone data files (Heikki)
-      </para>
-
-      <para>
-       This adds support for daylight saving time (<acronym>DST</>)
-       calculations beyond the year 2038.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Deprecate use of platform's <type>time_t</> data type (Tom)
-      </para>
-
-      <para>
-       Some platforms have migrated to 64-bit <type>time_t</>, some have
-       not, and Windows can't make up its mind what it's doing.  Define
-       <type>pg_time_t</> to have the same meaning as <type>time_t</>,
-       but always be 64 bits (unless the platform has no 64-bit integer type),
-       and use that type in all module APIs and on-disk data formats.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix bug in handling of the time zone database when cross-compiling
-       (Richard Evans)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Link backend object files in one step, rather than in stages
-       (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <application>gettext</> support to allow better translation
-       of plurals (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add message translation support to the PL languages (Alvaro, Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add more <application>DTrace</> probes (Robert Lor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Enable <application>DTrace</> support on <application>Mac OS X
-       Leopard</> and other non-Solaris platforms (Robert Lor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Simplify and standardize conversions between C strings and
-       <type>text</> datums, by providing common functions for the purpose
-       (Brendan Jurd, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Clean up the <filename>include/catalog/</> header files so that
-       frontend programs can include them without including
-       <filename>postgres.h</>
-       (Zdenek Kotala)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <type>name</> char-aligned, and suppress zero-padding of
-       <type>name</> entries in indexes (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Recover better if dynamically-loaded code executes <function>exit()</>
-       (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a hook to let plug-ins monitor the executor (Itagaki
-       Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a hook to allow the planner's statistics lookup behavior to
-       be overridden (Simon Riggs)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>shmem_startup_hook()</> for custom shared memory
-       requirements (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Replace the index access method <function>amgetmulti</> entry point
-       with <function>amgetbitmap</>, and extend the API for
-       <function>amgettuple</> to support run-time determination of
-       operator lossiness (Heikki, Tom, Teodor)
-      </para>
-
-      <para>
-       The API for GIN and GiST opclass <function>consistent</> functions
-       has been extended as well.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for partial-match searches in <acronym>GIN</> indexes
-       (Teodor Sigaev, Oleg Bartunov)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Replace <structname>pg_class</> column <structfield>reltriggers</>
-       with boolean <structfield>relhastriggers</> (Simon)
-      </para>
-
-      <para>
-       Also remove unused <structname>pg_class</> columns
-       <structfield>relukeys</>, <structfield>relfkeys</>, and
-       <structfield>relrefs</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a <structfield>relistemp</> column to <structname>pg_class</>
-       to ease identification of temporary tables (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Move platform <acronym>FAQ</>s into the main documentation
-       (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Prevent parser input files from being built with any conflicts
-       (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for the <literal>KOI8U</> (Ukrainian) encoding
-       (Peter)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add Japanese message translations (Japan PostgreSQL Users Group)
-      </para>
-
-      <para>
-       This used to be maintained as a separate project.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix problem when setting <varname>LC_MESSAGES</> on
-       <application>MSVC</>-built systems (Hiroshi Inoue, Hiroshi
-       Saito, Magnus)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Contrib</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <filename>contrib/auto_explain</> to automatically run
-       <command>EXPLAIN</> on queries exceeding a specified duration
-       (Itagaki Takahiro, Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <filename>contrib/btree_gin</> to allow GIN indexes to
-       handle more datatypes (Oleg, Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <filename>contrib/citext</> to provide a case-insensitive,
-       multibyte-aware text data type (David Wheeler)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <filename>contrib/pg_stat_statements</> for server-wide
-       tracking of statement execution statistics (Itagaki Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add duration and query mode options to <filename>contrib/pgbench</>
-       (Itagaki Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <filename>contrib/pgbench</> use table names
-       <structname>pgbench_accounts</>, <structname>pgbench_branches</>,
-       <structname>pgbench_history</>, and <structname>pgbench_tellers</>,
-       rather than just <structname>accounts</>, <structname>branches</>,
-       <structname>history</>, and <structname>tellers</> (Tom)
-      </para>
-
-      <para>
-       This is to reduce the risk of accidentally destroying real data
-       by running <application>pgbench</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <filename>contrib/pgstattuple</> to handle tables and
-       indexes with over 2 billion pages (Tatsuhito Kasahara)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In <filename>contrib/fuzzystrmatch</>, add a version of the
-       Levenshtein string-distance function that allows the user to
-       specify the costs of insertion, deletion, and substitution
-       (Volkan Yazici)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <filename>contrib/ltree</> support multibyte encodings
-       (laser)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Enable <filename>contrib/dblink</> to use connection information
-       stored in the SQL/MED catalogs (Joe Conway)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <filename>contrib/dblink</>'s reporting of errors from
-       the remote server (Joe Conway)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <filename>contrib/dblink</> set <varname>client_encoding</>
-       to match the local database's encoding (Joe Conway)
-      </para>
-
-      <para>
-       This prevents encoding problems when communicating with a remote
-       database that uses a different encoding.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make sure <filename>contrib/dblink</> uses a password supplied
-       by the user, and not accidentally taken from the server's
-       <filename>.pgpass</> file (Joe Conway)
-      </para>
-
-      <para>
-       This is a minor security enhancement.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <function>fsm_page_contents()</>
-       to <filename>contrib/pageinspect</> (Heikki)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Modify <function>get_raw_page()</> to support free space map
-       (<filename>*_fsm</>) files.  Also update
-       <filename>contrib/pg_freespacemap</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for multibyte encodings to <filename>contrib/pg_trgm</>
-       (Teodor)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Rewrite <filename>contrib/intagg</> to use new
-       functions <function>array_agg()</> and <function>unnest()</>
-       (Tom)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <filename>contrib/pg_standby</> recover all available WAL before
-       failover (Fujii Masao, Simon, Heikki)
-      </para>
-
-      <para>
-       To make this work safely, you now need to set the new
-       <literal>recovery_end_command</> option in <filename>recovery.conf</>
-       to clean up the trigger file after failover. <application>pg_standby</>
-       will no longer remove the trigger file itself.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <filename>contrib/pg_standby</>'s <option>-l</> option is now a no-op,
-       because it is unsafe to use a symlink (Simon)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-  </sect2>
- </sect1>
diff --git a/doc-xc/src/sgml/release-9.0.sgmlin b/doc-xc/src/sgml/release-9.0.sgmlin
deleted file mode 100644
index dcd9e1e22c..0000000000
--- a/doc-xc/src/sgml/release-9.0.sgmlin
+++ /dev/null
@@ -1,4156 +0,0 @@
-<!-- doc/src/sgml/release-9.0.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-9-0-3">
-  <title>Release 9.0.3</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2011-01-31</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 9.0.2.
-   For information about new features in the 9.0 major release, see
-   <xref linkend="release-9-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 9.0.3</title>
-
-   <para>
-    A dump/restore is not required for those running 9.0.X.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Before exiting <application>walreceiver</>, ensure all the received WAL
-      is fsync'd to disk (Heikki Linnakangas)
-     </para>
-
-     <para>
-      Otherwise the standby server could replay some un-synced WAL, conceivably
-      leading to data corruption if the system crashes just at that point.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid excess fsync activity in <application>walreceiver</>
-      (Heikki Linnakangas)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>ALTER TABLE</> revalidate uniqueness and exclusion
-      constraints when needed (Noah Misch)
-     </para>
-
-     <para>
-      This was broken in 9.0 by a change that was intended to suppress
-      revalidation during <command>VACUUM FULL</> and <command>CLUSTER</>,
-      but unintentionally affected <command>ALTER TABLE</> as well.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix EvalPlanQual for <command>UPDATE</> of an inheritance tree in which
-      the tables are not all alike (Tom Lane)
-     </para>
-
-     <para>
-      Any variation in the table row types (including dropped columns present
-      in only some child tables) would confuse the EvalPlanQual code, leading
-      to misbehavior or even crashes.  Since EvalPlanQual is only executed
-      during concurrent updates to the same row, the problem was only seen
-      intermittently.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid failures when <command>EXPLAIN</> tries to display a simple-form
-      <literal>CASE</> expression (Tom Lane)
-     </para>
-
-     <para>
-      If the <literal>CASE</>'s test expression was a constant, the planner
-      could simplify the <literal>CASE</> into a form that confused the
-      expression-display code, resulting in <quote>unexpected CASE WHEN
-      clause</> errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assignment to an array slice that is before the existing range
-      of subscripts (Tom Lane)
-     </para>
-
-     <para>
-      If there was a gap between the newly added subscripts and the first
-      pre-existing subscript, the code miscalculated how many entries needed
-      to be copied from the old array's null bitmap, potentially leading to
-      data corruption or crash.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unexpected conversion overflow in planner for very distant date
-      values (Tom Lane)
-     </para>
-
-     <para>
-      The <type>date</> type supports a wider range of dates than can be
-      represented by the <type>timestamp</> types, but the planner assumed it
-      could always convert a date to timestamp with impunity.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix PL/Python crash when an array contains null entries (Alex Hunsaker)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Remove <application>ecpg</>'s fixed length limit for constants defining
-      an array dimension (Michael Meskes)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix erroneous parsing of <type>tsquery</> values containing
-      <literal>... &amp; !(subexpression) | ...</literal> (Tom Lane)
-     </para>
-
-     <para>
-      Queries containing this combination of operators were not executed
-      correctly.  The same error existed in <filename>contrib/intarray</>'s
-      <type>query_int</> type and <filename>contrib/ltree</>'s
-      <type>ltxtquery</> type.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix buffer overrun in <filename>contrib/intarray</>'s input function
-      for the <type>query_int</> type (Apple)
-     </para>
-
-     <para>
-      This bug is a security risk since the function's return address could
-      be overwritten.  Thanks to Apple Inc's security team for reporting this
-      issue and supplying the fix.  (CVE-2010-4015)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in <filename>contrib/seg</>'s GiST picksplit algorithm
-      (Alexander Korotkov)
-     </para>
-
-     <para>
-      This could result in considerable inefficiency, though not actually
-      incorrect answers, in a GiST index on a <type>seg</> column.
-      If you have such an index, consider <command>REINDEX</>ing it after
-      installing this update.  (This is identical to the bug that was fixed in
-      <filename>contrib/cube</> in the previous update.)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-9-0-2">
-  <title>Release 9.0.2</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-12-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 9.0.1.
-   For information about new features in the 9.0 major release, see
-   <xref linkend="release-9-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 9.0.2</title>
-
-   <para>
-    A dump/restore is not required for those running 9.0.X.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Force the default
-      <link linkend="guc-wal-sync-method"><varname>wal_sync_method</></link>
-      to be <literal>fdatasync</> on Linux (Tom Lane, Marti Raudsepp)
-     </para>
-
-     <para>
-      The default on Linux has actually been <literal>fdatasync</> for many
-      years, but recent kernel changes caused <productname>PostgreSQL</> to
-      choose <literal>open_datasync</> instead.  This choice did not result
-      in any performance improvement, and caused outright failures on
-      certain filesystems, notably <literal>ext4</> with the
-      <literal>data=journal</> mount option.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>too many KnownAssignedXids</> error during Hot Standby
-      replay (Heikki Linnakangas)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix race condition in lock acquisition during Hot Standby (Simon Riggs)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid unnecessary conflicts during Hot Standby (Simon Riggs)
-     </para>
-
-     <para>
-      This fixes some cases where replay was considered to conflict with
-      standby queries (causing delay of replay or possibly cancellation of
-      the queries), but there was no real conflict.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane)
-     </para>
-
-     <para>
-      This could result in <quote>bad buffer id: 0</> failures or
-      corruption of index contents during replication.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix recovery from base backup when the starting checkpoint WAL record
-      is not in the same WAL segment as its redo point (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix corner-case bug when streaming replication is enabled immediately
-      after creating the master database cluster (Heikki Linnakangas)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix persistent slowdown of autovacuum workers when multiple workers
-      remain active for a long time (Tom Lane)
-     </para>
-
-     <para>
-      The effective <varname>vacuum_cost_limit</> for an autovacuum worker
-      could drop to nearly zero if it processed enough tables, causing it
-      to run extremely slowly.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix long-term memory leak in autovacuum launcher (Alvaro Herrera)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid failure when trying to report an impending transaction
-      wraparound condition from outside a transaction (Tom Lane)
-     </para>
-
-     <para>
-      This oversight prevented recovery after transaction wraparound got
-      too close, because database startup processing would fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add support for detecting register-stack overrun on <literal>IA64</>
-      (Tom Lane)
-     </para>
-
-     <para>
-      The <literal>IA64</> architecture has two hardware stacks.  Full
-      prevention of stack-overrun failures requires checking both.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add a check for stack overflow in <function>copyObject()</> (Tom Lane)
-     </para>
-
-     <para>
-      Certain code paths could crash due to stack overflow given a
-      sufficiently complex query.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix detection of page splits in temporary GiST indexes (Heikki
-      Linnakangas)
-     </para>
-
-     <para>
-      It is possible to have a <quote>concurrent</> page split in a
-      temporary index, if for example there is an open cursor scanning the
-      index when an insertion is done.  GiST failed to detect this case and
-      hence could deliver wrong results when execution of the cursor
-      continued.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix error checking during early connection processing (Tom Lane)
-     </para>
-
-     <para>
-      The check for too many child processes was skipped in some cases,
-      possibly leading to postmaster crash when attempting to add the new
-      child process to fixed-size arrays.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve efficiency of window functions (Tom Lane)
-     </para>
-
-     <para>
-      Certain cases where a large number of tuples needed to be read in
-      advance, but <varname>work_mem</> was large enough to allow them all
-      to be held in memory, were unexpectedly slow.
-      <function>percent_rank()</>, <function>cume_dist()</> and
-      <function>ntile()</> in particular were subject to this problem.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid memory leakage while <command>ANALYZE</>'ing complex index
-      expressions (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ensure an index that uses a whole-row Var still depends on its table
-      (Tom Lane)
-     </para>
-
-     <para>
-      An index declared like <literal>create index i on t (foo(t.*))</>
-      would not automatically get dropped when its table was dropped.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add missing support in <command>DROP OWNED BY</> for removing foreign
-      data wrapper/server privileges belonging to a user (Heikki Linnakangas)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Do not <quote>inline</> a SQL function with multiple <literal>OUT</>
-      parameters (Tom Lane)
-     </para>
-
-     <para>
-      This avoids a possible crash due to loss of information about the
-      expected result rowtype.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash when inline-ing a set-returning function whose argument list
-      contains a reference to an inline-able user function (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Behave correctly if <literal>ORDER BY</>, <literal>LIMIT</>,
-      <literal>FOR UPDATE</>, or <literal>WITH</> is attached to the
-      <literal>VALUES</> part of <literal>INSERT ... VALUES</> (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make the <literal>OFF</> keyword unreserved (Heikki Linnakangas)
-     </para>
-
-     <para>
-      This prevents problems with using <literal>off</> as a variable name in
-      <application>PL/pgSQL</>.  That worked before 9.0, but was now broken
-      because <application>PL/pgSQL</> now treats all core reserved words
-      as reserved.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix constant-folding of <literal>COALESCE()</> expressions (Tom Lane)
-     </para>
-
-     <para>
-      The planner would sometimes attempt to evaluate sub-expressions that
-      in fact could never be reached, possibly leading to unexpected errors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <quote>could not find pathkey item to sort</> planner failure
-      with comparison of whole-row Vars (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix postmaster crash when connection acceptance
-      (<function>accept()</> or one of the calls made immediately after it)
-      fails, and the postmaster was compiled with GSSAPI support (Alexander
-      Chernikov)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Retry after receiving an invalid response packet from a RADIUS
-      authentication server (Magnus Hagander)
-     </para>
-
-     <para>
-      This fixes a low-risk potential denial of service condition.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix missed unlink of temporary files when <varname>log_temp_files</>
-      is active (Tom Lane)
-     </para>
-
-     <para>
-      If an error occurred while attempting to emit the log message, the
-      unlink was not done, resulting in accumulation of temp files.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add print functionality for <structname>InhRelation</> nodes (Tom Lane)
-     </para>
-
-     <para>
-      This avoids a failure when <varname>debug_print_parse</> is enabled
-      and certain types of query are executed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect calculation of distance from a point to a horizontal
-      line segment (Tom Lane)
-     </para>
-
-     <para>
-      This bug affected several different geometric distance-measurement
-      operators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect calculation of transaction status in
-      <application>ecpg</> (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix errors in <application>psql</>'s Unicode-escape support (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Speed up parallel <application>pg_restore</> when the archive
-      contains many large objects (blobs) (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/pgSQL</>'s handling of <quote>simple</>
-      expressions to not fail in recursion or error-recovery cases (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/pgSQL</>'s error reporting for no-such-column
-      cases (Tom Lane)
-     </para>
-
-     <para>
-      As of 9.0, it would sometimes report <quote>missing FROM-clause entry
-      for table foo</> when <quote>record foo has no field bar</> would be
-      more appropriate.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/Python</> to honor typmod (i.e., length or
-      precision restrictions) when assigning to tuple fields (Tom Lane)
-     </para>
-
-     <para>
-      This fixes a regression from 8.4.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <application>PL/Python</>'s handling of set-returning functions
-      (Jan Urbanski)
-     </para>
-
-     <para>
-      Attempts to call SPI functions within the iterator generating a set
-      result would fail.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix bug in <filename>contrib/cube</>'s GiST picksplit algorithm
-      (Alexander Korotkov)
-     </para>
-
-     <para>
-      This could result in considerable inefficiency, though not actually
-      incorrect answers, in a GiST index on a <type>cube</> column.
-      If you have such an index, consider <command>REINDEX</>ing it after
-      installing this update.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Don't emit <quote>identifier will be truncated</> notices in
-      <filename>contrib/dblink</> except when creating new connections
-      (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential coredump on missing public key in
-      <filename>contrib/pgcrypto</> (Marti Raudsepp)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix buffer overrun in <filename>contrib/pg_upgrade</> (Hernan Gonzalez)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix memory leak in <filename>contrib/xml2</>'s XPath query functions
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update time zone data files to <application>tzdata</> release 2010o
-      for DST law changes in Fiji and Samoa;
-      also historical corrections for Hong Kong.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-9-0-1">
-  <title>Release 9.0.1</title>
-
-  <note>
-  <title>Release date</title>
-  <simpara>2010-10-04</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 9.0.0.
-   For information about new features in the 9.0 major release, see
-   <xref linkend="release-9-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 9.0.1</title>
-
-   <para>
-    A dump/restore is not required for those running 9.0.X.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Use a separate interpreter for each calling SQL userid in PL/Perl and
-      PL/Tcl (Tom Lane)
-     </para>
-
-     <para>
-      This change prevents security problems that can be caused by subverting
-      Perl or Tcl code that will be executed later in the same session under
-      another SQL user identity (for example, within a <literal>SECURITY
-      DEFINER</> function).  Most scripting languages offer numerous ways that
-      that might be done, such as redefining standard functions or operators
-      called by the target function.  Without this change, any SQL user with
-      Perl or Tcl language usage rights can do essentially anything with the
-      SQL privileges of the target function's owner.
-     </para>
-
-     <para>
-      The cost of this change is that intentional communication among Perl
-      and Tcl functions becomes more difficult.  To provide an escape hatch,
-      PL/PerlU and PL/TclU functions continue to use only one interpreter
-      per session.  This is not considered a security issue since all such
-      functions execute at the trust level of a database superuser already.
-     </para>
-
-     <para>
-      It is likely that third-party procedural languages that claim to offer
-      trusted execution have similar security issues.  We advise contacting
-      the authors of any PL you are depending on for security-critical
-      purposes.
-     </para>
-
-     <para>
-      Our thanks to Tim Bunce for pointing out this issue (CVE-2010-3433).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <function>pg_get_expr()</> security fix so that the function
-      can still be used on the output of a sub-select (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix incorrect placement of placeholder evaluation (Tom Lane)
-     </para>
-
-     <para>
-      This bug could result in query outputs being non-null when they
-      should be null, in cases where the inner side of an outer join
-      is a sub-select with non-strict expressions in its output list.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix join removal's handling of placeholder expressions (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix possible duplicate scans of <literal>UNION ALL</> member relations
-      (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent infinite loop in ProcessIncomingNotify() after unlistening
-      (Jeff Davis)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Prevent show_session_authorization() from crashing within autovacuum
-      processes (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Re-allow input of Julian dates prior to 0001-01-01 AD (Tom Lane)
-     </para>
-
-     <para>
-      Input such as <literal>'J100000'::date</> worked before 8.4,
-      but was unintentionally broken by added error-checking.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make psql recognize <command>DISCARD ALL</> as a command that should
-      not be encased in a transaction block in autocommit-off mode
-      (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update build infrastructure and documentation to reflect the source code
-      repository's move from CVS to Git (Magnus Hagander and others)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-9-0">
-  <title>Release 9.0</title>
-
-  <note>
-   <title>Release date</title>
-   <simpara>2010-09-20</simpara>
-  </note>
-
-  <sect2>
-   <title>Overview</title>
-
-   <para>
-    This release of
-    <productname>PostgreSQL</> adds features that have been requested
-    for years, such as easy-to-use replication, a mass permission-changing
-    facility, and anonymous code blocks. While past major releases have
-    been conservative in their scope, this release shows a
-    bold new desire to provide facilities that new and existing
-    users of <productname>PostgreSQL</> will embrace. This has all
-    been done with few incompatibilities. Major enhancements include:
-   </para>
-
-   <itemizedlist>
-
-    <!-- This list duplicates items below, but without authors or details-->
-
-    <listitem>
-
-     <para>
-      Built-in replication based on log shipping.  This advance consists of
-      two features: Streaming Replication, allowing continuous archive
-      (<acronym>WAL</>) files to be streamed over a network connection to a
-      standby server, and Hot Standby, allowing continuous archive standby
-      servers to execute read-only queries.  The net effect is to support a
-      single master with multiple read-only slave servers.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Easier database object permissions management. <link
-      linkend="SQL-GRANT"><command>GRANT</>/<command>REVOKE IN
-      SCHEMA</></link> supports mass permissions changes on existing objects,
-      while <link linkend="SQL-ALTERDEFAULTPRIVILEGES"><command>ALTER DEFAULT
-      PRIVILEGES</></link> allows control of privileges for objects created in
-      the future.  Large objects (BLOBs) now support permissions management as
-      well.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Broadly enhanced stored procedure support.
-      The <link linkend="SQL-DO"><command>DO</></link> statement supports
-      ad-hoc or <quote>anonymous</> code blocks.
-      Functions can now be called using named parameters.
-      <link linkend="plpgsql">PL/pgSQL</link> is now installed by default, and
-      <link linkend="plperl">PL/Perl</link> and <link
-      linkend="plpython">PL/Python</link> have been enhanced in several ways,
-      including support for Python3.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Full support for <link linkend="install-windows">64-bit
-      <productname>Windows</></link>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      More advanced reporting queries, including additional windowing options
-      (<literal>PRECEDING</> and <literal>FOLLOWING</>) and the ability to
-      control the order in which values are fed to aggregate functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New trigger features, including
-      SQL-standard-compliant <link
-      linkend="SQL-CREATETRIGGER">per-column triggers</link> and
-      conditional trigger execution.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <link linkend="SQL-CREATETABLE-compatibility">Deferrable
-      unique constraints</link>. Mass updates to unique keys are now possible
-      without trickery.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <link linkend="ddl-constraints-exclusion">Exclusion constraints</link>.
-      These provide a generalized version of unique constraints, allowing
-      enforcement of complex conditions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New and enhanced security features, including RADIUS authentication,
-      LDAP authentication improvements, and a new contrib module
-      <link linkend="passwordcheck"><filename>passwordcheck</></link>
-      for testing password strength.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New high-performance implementation of the
-      <link linkend="SQL-LISTEN"><command>LISTEN</></link>/<link
-      linkend="SQL-NOTIFY"><command>NOTIFY</></link> feature.
-      Pending events are now stored in a memory-based queue rather than
-      a table.  Also, a <quote>payload</> string can be sent with each
-      event, rather than transmitting just an event name as before.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New implementation of
-      <link linkend="SQL-VACUUM"><command>VACUUM FULL</></link>.
-      This command now rewrites the entire table and indexes, rather than
-      moving individual rows to compact space.  It is substantially faster
-      in most cases, and no longer results in index bloat.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New contrib module
-      <link linkend="pgupgrade"><filename>pg_upgrade</></link>
-      to support in-place upgrades from 8.3 or 8.4 to 9.0.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Multiple performance enhancements for specific types of queries,
-      including elimination of unnecessary joins.  This helps optimize some
-      automatically-generated queries, such as those produced by
-      object-relational mappers (ORMs).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <link linkend="SQL-EXPLAIN "><command>EXPLAIN</></link> enhancements.
-      The output is now available in JSON, XML, or YAML format, and includes
-      buffer utilization and other data not previously available.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <link linkend="hstore"><filename>hstore</></link> improvements,
-      including new functions and greater data capacity.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <para>
-    The above items are explained in more detail in the sections below.
-   </para>
-
-  </sect2>
-
-  <sect2>
-
-  <title>Migration to Version 9.0</title>
-
-  <para>
-   A dump/restore using <application>pg_dump</application>,
-   or use of <application>pg_upgrade</application>, is required
-   for those wishing to migrate data from any previous
-   release.
-  </para>
-
-  <para>
-   Version 9.0 contains a number of changes that selectively break backwards
-   compatibility in order to support new features and code quality
-   improvements.  In particular, users who make extensive use of PL/pgSQL,
-   Point-In-Time Recovery (PITR), or Warm Standby should test their
-   applications because of slight user-visible changes in those areas.
-   Observe the following incompatibilities:
-  </para>
-
-  <sect3>
-   <title>Server Settings</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Remove server parameter <varname>add_missing_from</>, which was
-      defaulted to off for many years (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Remove server parameter <varname>regex_flavor</>, which
-      was defaulted to <link
-      linkend="posix-syntax-details"><literal>advanced</></link>
-      for many years (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <link linkend="guc-archive-mode"><varname>archive_mode</></link>
-      now only affects <link
-      linkend="guc-archive-command"><varname>archive_command</></link>;
-      a new setting, <link
-      linkend="guc-wal-level"><varname>wal_level</></link>, affects
-      the contents of the write-ahead log (Heikki Linnakangas)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <link linkend="guc-log-temp-files"><varname>log_temp_files</></link>
-      now uses default file size units of kilobytes (Robert Haas)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect3>
-
-  <sect3>
-   <title>Queries</title>
-
-   <itemizedlist>
-
-   <listitem>
-    <para>
-     When querying a <link linkend="ddl-inherit">parent table</link>,
-     do not do any separate permission checks on child tables
-     scanned as part of the query (Peter Eisentraut)
-    </para>
-
-    <para>
-     The SQL standard specifies this behavior, and it is also much more
-     convenient in practice than the former behavior of checking permissions
-     on each child as well as the parent.
-    </para>
-   </listitem>
-
-   </itemizedlist>
-
-  </sect3>
-
-  <sect3>
-   <title>Data Types</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      <link linkend="datatype-binary"><type>bytea</></link> output now
-      appears in hex format by default (Peter Eisentraut)
-     </para>
-
-     <para>
-      The server parameter <link
-      linkend="guc-bytea-output"><varname>bytea_output</></link> can be
-      used to select the traditional output format if needed for
-      compatibility.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Array input now considers only plain ASCII whitespace characters
-      to be potentially ignorable; it will never ignore non-ASCII characters,
-      even if they are whitespace according to some locales (Tom Lane)
-     </para>
-
-     <para>
-      This avoids some corner cases where array values could be interpreted
-      differently depending on the server's locale settings.
-     </para>
-    </listitem>
-
-   <listitem>
-    <para>
-     Improve standards compliance of <link
-     linkend="functions-similarto-regexp"><literal>SIMILAR TO</></link>
-     patterns and SQL-style <function>substring()</> patterns (Tom Lane)
-    </para>
-
-    <para>
-     This includes treating <literal>?</> and <literal>{...}</> as
-     pattern metacharacters, while they were simple literal characters
-     before; that corresponds to new features added in SQL:2008.
-     Also, <literal>^</> and <literal>$</> are now treated as simple
-     literal characters; formerly they were treated as metacharacters,
-     as if the pattern were following POSIX rather than SQL rules.
-     Also, in SQL-standard <function>substring()</>, use of parentheses
-     for nesting no longer interferes with capturing of a substring.
-     Also, processing of bracket expressions (character classes) is
-     now more standards-compliant.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Reject negative length values in 3-parameter <link
-     linkend="functions-string-sql"><function>substring()</></link>
-     for bit strings, per the SQL standard (Tom Lane)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Make <function>date_trunc</> truncate rather than round when reducing
-     precision of fractional seconds (Tom Lane)
-    </para>
-
-    <para>
-     The code always acted this way for integer-based dates/times.
-     Now float-based dates/times behave similarly.
-    </para>
-   </listitem>
-
-  </itemizedlist>
-
-  </sect3>
-
-  <sect3>
-   <title>Object Renaming</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Tighten enforcement of column name consistency during <command>RENAME</>
-      when a child table inherits the same column from multiple unrelated
-      parents (KaiGai Kohei)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      No longer automatically rename indexes and index columns when the
-      underlying table columns are renamed (Tom Lane)
-     </para>
-
-     <para>
-      Administrators can still rename such indexes and columns manually.
-      This change will require an update of the JDBC driver, and possibly other
-      drivers, so that unique indexes are correctly recognized after a rename.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <command>CREATE OR REPLACE FUNCTION</command> can no longer change
-      the declared names of function parameters (Pavel Stehule)
-     </para>
-
-     <para>
-      In order to avoid creating ambiguity in named-parameter calls, it is
-      no longer allowed to change the aliases for input parameters
-      in the declaration of an existing function (although names can still
-      be assigned to previously unnamed parameters).  You now have to
-      <command>DROP</command> and recreate the function to do that.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect3>
-
-  <sect3>
-   <title>PL/pgSQL</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      PL/pgSQL now throws an error if a variable name conflicts with a
-      column name used in a query (Tom Lane)
-     </para>
-
-     <para>
-      The former behavior was to bind ambiguous names to PL/pgSQL variables
-      in preference to query columns, which often resulted in surprising
-      misbehavior. Throwing an error allows easy detection of ambiguous
-      situations.  Although it's recommended that functions encountering this
-      type of error be modified to remove the conflict, the old behavior can
-      be restored if necessary via the configuration parameter <link
-      linkend="plpgsql-var-subst"><varname>plpgsql.variable_conflict</></link>,
-      or via the per-function option <literal>#variable_conflict</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      PL/pgSQL no longer allows variable names that match certain SQL
-      reserved words (Tom Lane)
-     </para>
-
-     <para>
-      This is a consequence of aligning the PL/pgSQL parser to match the
-      core SQL parser more closely.  If necessary,
-      variable names can be double-quoted to avoid this restriction.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      PL/pgSQL now requires columns of composite results to match the
-      expected type modifier as well as base type (Pavel Stehule, Tom Lane)
-     </para>
-
-     <para>
-      For example, if a column of the result type is declared as
-      <literal>NUMERIC(30,2)</>, it is no longer acceptable to return a
-      <literal>NUMERIC</> of some other precision in that column.  Previous
-      versions neglected to check the type modifier and would thus allow
-      result rows that didn't actually conform to the declared restrictions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      PL/pgSQL now treats selection into composite fields more consistently
-      (Tom Lane)
-     </para>
-
-     <para>
-      Formerly, a statement like
-      <literal>SELECT ... INTO <replaceable>rec</>.<replaceable>fld</> FROM ...</literal>
-      was treated as a scalar assignment even if the record field
-      <replaceable>fld</> was of composite type.  Now it is treated as a
-      record assignment, the same as when the <literal>INTO</> target is a
-      regular variable of composite type.  So the values to be assigned to the
-      field's subfields should be written as separate columns of the
-      <command>SELECT</> list, not as a <literal>ROW(...)</> construct as in
-      previous versions.
-     </para>
-
-     <para>
-      If you need to do this in a way that will work in both 9.0 and previous
-      releases, you can write something like
-      <literal><replaceable>rec</>.<replaceable>fld</> := ROW(...) FROM ...</literal>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Remove PL/pgSQL's <literal>RENAME</> declaration (Tom Lane)
-     </para>
-
-     <para>
-      Instead of <literal>RENAME</>, use <link
-      linkend="plpgsql-declaration-alias"><literal>ALIAS</></link>,
-      which can now create an alias for any variable, not only dollar sign
-      parameter names (such as <literal>$1</>) as before.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-  </sect3>
-
-  <sect3>
-   <title>Other Incompatibilities</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Deprecate use of <literal>=&gt;</> as an operator name (Robert Haas)
-     </para>
-
-     <para>
-      Future versions of <productname>PostgreSQL</> will probably reject
-      this operator name entirely, in order to support the SQL-standard
-      notation for named function parameters.  For the moment, it is
-      still allowed, but a warning is emitted when such an operator is
-      defined.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Remove support for platforms that don't have a working 64-bit
-      integer data type (Tom Lane)
-     </para>
-
-     <para>
-      It is believed all still-supported platforms have working 64-bit
-      integer data types.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-  </sect3>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-   <para>
-    Version 9.0 has an unprecedented number of new major features,
-    and over 200 enhancements, improvements, new commands,
-    new functions, and other changes.
-   </para>
-
-  <sect3>
-   <title>Server</title>
-
-   <sect4>
-    <title>Continuous Archiving and Streaming Replication</title>
-
-    <para>
-     PostgreSQL's existing standby-server capability has been expanded both to
-     support read-only queries on standby servers and to greatly reduce
-     the lag between master and standby servers.  For many users, this
-     will be a useful and low-administration form of replication, either
-     for high availability or for horizontal scalability.
-    </para>
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Allow a standby server to accept read-only queries
-       (Simon Riggs, Heikki Linnakangas)
-      </para>
-
-      <para>
-       This feature is called Hot Standby. There are new
-       <filename>postgresql.conf</> and <filename>recovery.conf</>
-       settings to control this feature, as well as extensive
-       <link linkend="hot-standby">documentation</link>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow write-ahead log (<acronym>WAL</>) data to be streamed to a
-       standby server (Fujii Masao, Heikki Linnakangas)
-      </para>
-
-      <para>
-       This feature is called Streaming Replication.
-       Previously <acronym>WAL</> data could be sent to standby servers only
-       in units of entire <acronym>WAL</> files (normally 16 megabytes each).
-       Streaming Replication eliminates this inefficiency and allows updates
-       on the master to be propagated to standby servers with very little
-       delay.  There are new <filename>postgresql.conf</> and
-       <filename>recovery.conf</> settings to control this feature, as well as
-       extensive <link linkend="streaming-replication">documentation</link>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="functions-recovery-info-table"><function>pg_last_xlog_receive_location()</></link>
-       and <function>pg_last_xlog_replay_location()</>, which
-       can be used to monitor standby server <acronym>WAL</>
-       activity (Simon Riggs, Fujii Masao, Heikki Linnakangas)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Performance</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow per-tablespace values to be set for sequential and random page
-       cost estimates (<varname>seq_page_cost</>/<varname>random_page_cost</>)
-       via <link linkend="SQL-ALTERTABLESPACE"><command>ALTER TABLESPACE
-       ... SET/RESET</></link> (Robert Haas)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve performance and reliability of EvalPlanQual rechecks in join
-       queries (Tom Lane)
-      </para>
-
-      <para>
-       <command>UPDATE</>, <command>DELETE</>, and <command>SELECT FOR
-       UPDATE/SHARE</> queries that involve joins will now behave much better
-       when encountering freshly-updated rows.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve performance of <link
-       linkend="SQL-TRUNCATE"><command>TRUNCATE</></link> when
-       the table was created or truncated earlier in the same transaction
-       (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve performance of finding inheritance child tables (Tom Lane)
-      </para>
-     </listitem>
-
-     </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Optimizer</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Remove unnecessary <link linkend="queries-join">outer
-       joins</link> (Robert Haas)
-      </para>
-
-      <para>
-       Outer joins where the inner side is unique and not referenced above
-       the join are unnecessary and are therefore now removed.  This will
-       accelerate many automatically generated queries, such as those created
-       by object-relational mappers (ORMs).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <literal>IS NOT NULL</> restrictions to use indexes (Tom Lane)
-      </para>
-
-      <para>
-       This is particularly useful for finding
-       <function>MAX()</>/<function>MIN()</> values in indexes that
-       contain many null values.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve the optimizer's choices about when to use materialize nodes,
-       and when to use sorting versus hashing for <literal>DISTINCT</>
-       (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve the optimizer's equivalence detection for expressions involving
-       <type>boolean</> <literal>&lt;&gt;</> operators (Tom Lane)
-      </para>
-     </listitem>
-    </itemizedlist>
-   </sect4>
-
-   <sect4>
-    <title><link linkend="geqo">GEQO</link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Use the same random seed every time GEQO plans a query (Andres
-       Freund)
-      </para>
-
-      <para>
-       While the Genetic Query Optimizer (GEQO) still selects
-       random plans, it now always selects the same random plans for identical
-       queries, thus giving more consistent performance. You can modify <link
-       linkend="guc-geqo-seed"><varname>geqo_seed</></link> to experiment with
-       alternative plans.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve GEQO plan selection (Tom Lane)
-      </para>
-
-      <para>
-       This avoids the rare error <quote>failed to make a valid plan</>,
-       and should also improve planning speed.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Optimizer Statistics</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Improve <link linkend="SQL-ANALYZE"><command>ANALYZE</></link>
-       to support inheritance-tree statistics (Tom Lane)
-      </para>
-
-      <para>
-       This is particularly useful for partitioned tables.  However,
-       autovacuum does not yet automatically re-analyze parent tables
-       when child tables change.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <link linkend="routine-vacuuming">autovacuum</link>'s
-       detection of when re-analyze is necessary (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve optimizer's estimation for greater/less-than comparisons
-       (Tom Lane)
-      </para>
-
-      <para>
-       When looking up statistics for greater/less-than comparisons,
-       if the comparison value is in the first or last histogram bucket,
-       use an index (if available) to fetch the current actual column
-       minimum or maximum.  This greatly improves the accuracy of estimates
-       for comparison values near the ends of the data range, particularly
-       if the range is constantly changing due to addition of new data.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow setting of number-of-distinct-values statistics using <link
-       linkend="SQL-ALTERTABLE"><command>ALTER TABLE</></link>
-       (Robert Haas)
-      </para>
-
-      <para>
-       This allows users to override the estimated number or percentage of
-       distinct values for a column. This statistic is normally computed by
-       <command>ANALYZE</>, but the estimate can be poor, especially on tables
-       with very large numbers of rows.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Authentication</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add support for <link
-       linkend="auth-radius"><acronym>RADIUS</></link> (Remote
-       Authentication Dial In User Service) authentication
-       (Magnus Hagander)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="auth-ldap"><acronym>LDAP</></link>
-       (Lightweight Directory Access Protocol) authentication
-       to operate in <quote>search/bind</> mode
-       (Robert Fleming, Magnus Hagander)
-      </para>
-
-      <para>
-       This allows the user to be looked up first, then the system uses
-       the <acronym>DN</> (Distinguished Name) returned for that user.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="auth-pg-hba-conf"><literal>samehost</></link>
-       and <literal>samenet</> designations to
-       <filename>pg_hba.conf</> (Stef Walter)
-      </para>
-
-      <para>
-       These match the server's <acronym>IP</> address and subnet address
-       respectively.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Pass trusted SSL root certificate names to the client so the client
-       can return an appropriate client certificate (Craig Ringer)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Monitoring</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add the ability for clients to set an <link
-       linkend="libpq-connect-application-name">application
-       name</link>, which is displayed in
-       <structname>pg_stat_activity</> (Dave Page)
-      </para>
-
-      <para>
-       This allows administrators to characterize database traffic
-       and troubleshoot problems by source application.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a SQLSTATE option (<literal>%e</>) to <link
-       linkend="guc-log-line-prefix"><varname>log_line_prefix</></link>
-       (Guillaume Smet)
-      </para>
-
-      <para>
-       This allows users to compile statistics on errors and messages
-       by error code number.
-      </para>
-
-     </listitem>
-
-     <listitem>
-      <para>
-       Write to the Windows event log in <acronym>UTF16</> encoding
-       (Itagaki Takahiro)
-      </para>
-
-      <para>
-       Now there is true multilingual support for PostgreSQL log messages
-       on Windows.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Statistics Counters</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="monitoring-stats-funcs-table"><function>pg_stat_reset_shared('bgwriter')</></link>
-       to reset the cluster-wide shared statistics for the
-       background writer (Greg Smith)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="monitoring-stats-funcs-table"><function>pg_stat_reset_single_table_counters()</></link>
-       and <function>pg_stat_reset_single_function_counters()</>
-       to allow resetting the statistics counters for individual
-       tables and functions (Magnus Hagander)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Server Settings</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow setting of configuration parameters based on <link
-       linkend="sql-alterrole">database/role combinations</link>
-       (Alvaro Herrera)
-      </para>
-
-      <para>
-       Previously only per-database and per-role settings were possible,
-       not combinations. All role and database settings are now stored
-       in the new <structname>pg_db_role_setting</> system catalog. A new
-       <application>psql</> command <literal>\drds</> shows these settings.
-       The legacy system views <structname>pg_roles</>,
-       <structname>pg_shadow</>, and <structname>pg_user</>
-       do not show combination settings, and therefore no longer
-       completely represent the configuration for a user or database.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add server parameter <link
-       linkend="guc-bonjour"><varname>bonjour</></link>, which
-       controls whether a Bonjour-enabled server advertises
-       itself via <productname>Bonjour</> (Tom Lane)
-      </para>
-
-      <para>
-       The default is off, meaning it does not advertise.  This allows
-       packagers to distribute Bonjour-enabled builds without worrying
-       that individual users might not want the feature.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add server parameter <link
-       linkend="guc-enable-material"><varname>enable_material</></link>, which
-       controls the use of materialize nodes in the optimizer
-       (Robert Haas)
-      </para>
-
-      <para>
-       The default is on.  When off, the optimizer will not add
-       materialize nodes purely for performance reasons, though they
-       will still be used when necessary for correctness.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change server parameter <link
-       linkend="guc-log-temp-files"><varname>log_temp_files</></link> to
-       use default file size units of kilobytes (Robert Haas)
-      </para>
-
-      <para>
-       Previously this setting was interpreted in bytes if no units were
-       specified.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Log changes of parameter values when <filename>postgresql.conf</> is
-       reloaded (Peter Eisentraut)
-      </para>
-
-      <para>
-       This lets administrators and security staff audit changes of database
-       settings, and is also very convenient for checking the effects of
-       <filename>postgresql.conf</> edits.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Properly enforce superuser permissions for custom server parameters
-       (Tom Lane)
-      </para>
-
-      <para>
-       Non-superusers can no longer issue <command>ALTER
-       ROLE</>/<command>DATABASE SET</> for parameters that are not currently
-       known to the server.  This allows the server to correctly check that
-       superuser-only parameters are only set by superusers.  Previously,
-       the <literal>SET</> would be allowed and then ignored at session start,
-       making superuser-only custom parameters much less useful than they
-       should be.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title>Queries</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Perform <link linkend="SQL-FOR-UPDATE-SHARE"><command>SELECT
-      FOR UPDATE</>/<literal>SHARE</></link> processing after
-      applying <literal>LIMIT</>, so the number of rows returned
-      is always predictable (Tom Lane)
-     </para>
-
-     <para>
-      Previously, changes made by concurrent transactions could cause a
-      <command>SELECT FOR UPDATE</> to unexpectedly return fewer rows than
-      specified by its <literal>LIMIT</>. <literal>FOR UPDATE</> in combination
-      with <literal>ORDER BY</> can still produce surprising results, but that
-      can be corrected by placing <literal>FOR UPDATE</> in a subquery.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow mixing of traditional and SQL-standard <link
-      linkend="SQL-LIMIT"><literal>LIMIT</>/<literal>OFFSET</></link>
-      syntax (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Extend the supported frame options in <link
-      linkend="SQL-WINDOW">window functions</link> (Hitoshi
-      Harada)
-     </para>
-
-     <para>
-      Frames can now start with <literal>CURRENT ROW</>, and the <literal>ROWS
-      <replaceable>n</> PRECEDING</>/<literal>FOLLOWING</> options are now
-      supported.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>SELECT INTO</> and <command>CREATE TABLE AS</> return
-      row counts to the client in their command tags
-      (Boszormenyi Zoltan)
-     </para>
-
-     <para>
-      This can save an entire round-trip to the client, allowing result counts
-      and pagination to be calculated without an additional
-      <command>COUNT</command> query.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <sect4>
-    <title>Unicode Strings</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Support Unicode surrogate pairs (dual 16-bit representation) in
-       <link
-       linkend="sql-syntax-strings-uescape"><literal>U&amp;</></link>
-       strings and identifiers (Peter Eisentraut)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support Unicode escapes in <link
-       linkend="sql-syntax-strings-escape"><literal>E'...'</></link>
-       strings (Marko Kreen)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title>Object Manipulation</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Speed up <link linkend="SQL-CREATEDATABASE"><command>CREATE
-      DATABASE</></link> by deferring flushes to disk (Andres
-      Freund, Greg Stark)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow <link linkend="SQL-COMMENT">comments</link> on
-      columns of tables, views, and composite types only, not other
-      relation types such as indexes and <acronym>TOAST</> tables (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow the creation of <link
-      linkend="SQL-CREATETYPE-enum">enumerated types</link> containing
-      no values (Bruce Momjian)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Let values of columns having storage type <literal>MAIN</> remain on
-      the main heap page unless the row cannot fit on a page (Kevin Grittner)
-     </para>
-
-     <para>
-      Previously <literal>MAIN</> values were forced out to <acronym>TOAST</>
-      tables until the row size was less than one-quarter of the page size.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <sect4>
-    <title><command>ALTER TABLE</></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Implement <literal>IF EXISTS</> for <literal>ALTER TABLE DROP COLUMN</>
-       and <literal>ALTER TABLE DROP CONSTRAINT </> (Andres Freund)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>ALTER TABLE</> commands that rewrite tables to skip
-       <acronym>WAL</> logging (Itagaki Takahiro)
-      </para>
-
-      <para>
-       Such operations either produce a new copy of the table or are rolled
-       back, so <acronym>WAL</> archiving can be skipped, unless running in
-       continuous archiving mode.  This reduces I/O overhead and improves
-       performance.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix failure of <literal>ALTER TABLE <replaceable>table</> ADD COLUMN
-       <replaceable>col</> serial</literal> when done by non-owner of table
-       (Tom Lane)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title><link linkend="SQL-CREATETABLE"><command>CREATE TABLE</></link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add support for copying <literal>COMMENTS</> and <literal>STORAGE</>
-       settings in <command>CREATE TABLE ... LIKE</> commands
-       (Itagaki Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a shortcut for copying all properties in <command>CREATE
-       TABLE ... LIKE</> commands (Itagaki Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add the SQL-standard
-       <literal>CREATE TABLE ... OF <replaceable>type</></literal> command
-       (Peter Eisentraut)
-      </para>
-
-      <para>
-       This allows creation of a table that matches an existing composite
-       type. Additional constraints and defaults can be specified in the
-       command.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Constraints</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <link linkend="SQL-CREATETABLE-compatibility">deferrable
-       unique constraints</link> (Dean Rasheed)
-      </para>
-
-      <para>
-       This allows mass updates, such as
-       <literal>UPDATE tab SET col = col + 1</>,
-       to work reliably
-       on columns that have unique indexes or are marked as primary keys.
-       If the constraint is specified as <literal>DEFERRABLE</> it will be
-       checked at the end of the statement, rather than after each row is
-       updated. The constraint check can also be deferred until the end of the
-       current transaction, allowing such updates to be spread over multiple
-       SQL commands.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add
-       <link linkend="ddl-constraints-exclusion">exclusion constraints</link>
-       (Jeff Davis)
-      </para>
-
-      <para>
-       Exclusion constraints generalize uniqueness constraints by allowing
-       arbitrary comparison operators, not just equality.  They are created
-       with the <link linkend="SQL-CREATETABLE-EXCLUDE"><command>CREATE
-       TABLE CONSTRAINT ... EXCLUDE</></link> clause.
-       The most common use of exclusion constraints is to specify that column
-       entries must not overlap, rather than simply not be equal.  This is
-       useful for time periods and other ranges, as well as arrays.
-       This feature enhances checking of data integrity for many
-       calendaring, time-management, and scientific applications.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve uniqueness-constraint violation error messages to
-       report the values causing the failure (Itagaki Takahiro)
-      </para>
-
-      <para>
-       For example, a uniqueness constraint violation might now report
-       <literal>Key (x)=(2) already exists</>.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Object Permissions</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add the ability to make mass permission changes across a whole
-       schema using the new <link
-       linkend="SQL-GRANT"><command>GRANT</>/<command>REVOKE
-       IN SCHEMA</></link> clause (Petr Jelinek)
-      </para>
-
-      <para>
-       This simplifies management of object permissions
-       and makes it easier to utilize database roles for application
-       data security.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="SQL-ALTERDEFAULTPRIVILEGES"><command>ALTER
-       DEFAULT PRIVILEGES</></link> command to control privileges
-       of objects created later (Petr Jelinek)
-      </para>
-
-      <para>
-       This greatly simplifies the assignment of object privileges in a
-       complex database application.  Default privileges can be set for
-       tables, views, sequences, and functions. Defaults may be assigned on a
-       per-schema basis, or database-wide.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add the ability to control large object (BLOB) permissions with
-       <command>GRANT</>/<command>REVOKE</> (KaiGai Kohei)
-      </para>
-
-      <para>
-       Formerly, any database user could read or modify any large object.
-       Read and write permissions can now be granted and revoked per
-       large object, and the ownership of large objects is tracked.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title>Utility Operations</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Make <link linkend="SQL-LISTEN"><command>LISTEN</></link>/<link
-      linkend="SQL-NOTIFY"><command>NOTIFY</></link> store pending events
-      in a memory queue, rather than in a system table (Joachim
-      Wieland)
-     </para>
-
-     <para>
-      This substantially improves performance, while retaining the existing
-      features of transactional support and guaranteed delivery.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow <link linkend="SQL-NOTIFY"><command>NOTIFY</></link>
-      to pass an optional <quote>payload</> string to listeners
-      (Joachim Wieland)
-     </para>
-
-     <para>
-      This greatly improves the usefulness of
-      <command>LISTEN</>/<command>NOTIFY</> as a
-      general-purpose event queue system.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow <link linkend="SQL-CLUSTER"><command>CLUSTER</></link>
-      on all per-database system catalogs (Tom Lane)
-     </para>
-
-     <para>
-      Shared catalogs still cannot be clustered.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <sect4>
-    <title><link linkend="SQL-COPY"><command>COPY</></link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Accept <literal>COPY ... CSV FORCE QUOTE *</>
-       (Itagaki Takahiro)
-      </para>
-
-      <para>
-       Now <literal>*</> can be used as shorthand for <quote>all columns</>
-       in the <literal>FORCE QUOTE</> clause.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new <command>COPY</> syntax that allows options to be
-       specified inside parentheses (Robert Haas, Emmanuel Cecchet)
-      </para>
-
-      <para>
-       This allows greater flexibility for future <command>COPY</> options.
-       The old syntax is still supported, but only for pre-existing options.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title><link linkend="SQL-EXPLAIN"><command>EXPLAIN</></link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow <command>EXPLAIN</> to output in <acronym>XML</>,
-       <acronym>JSON</>, or <acronym>YAML</> format (Robert Haas, Greg
-       Sabino Mullane)
-      </para>
-
-      <para>
-       The new output formats are easily machine-readable, supporting the
-       development of new tools for analysis of <command>EXPLAIN</> output.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new <literal>BUFFERS</> option to report query
-       buffer usage during <command>EXPLAIN ANALYZE</> (Itagaki Takahiro)
-      </para>
-
-      <para>
-       This allows better query profiling for individual queries.
-       Buffer usage is no longer reported in the output for <link
-       linkend="runtime-config-statistics-monitor">log_statement_stats</link>
-       and related settings.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add hash usage information to <command>EXPLAIN</> output (Robert
-       Haas)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new <command>EXPLAIN</> syntax that allows options to be
-       specified inside parentheses (Robert Haas)
-      </para>
-
-      <para>
-       This allows greater flexibility for future <command>EXPLAIN</> options.
-       The old syntax is still supported, but only for pre-existing options.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title><link linkend="SQL-VACUUM"><command>VACUUM</></link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Change <command>VACUUM FULL</> to rewrite the entire table and
-       rebuild its indexes, rather than moving individual rows around to
-       compact space (Itagaki Takahiro, Tom Lane)
-      </para>
-
-      <para>
-       The previous method was usually slower and caused index bloat.
-       Note that the new method will use more disk space transiently
-       during <command>VACUUM FULL</>; potentially as much as twice
-       the space normally occupied by the table and its indexes.
-      </para>
-
-     </listitem>
-
-     <listitem>
-      <para>
-       Add new <command>VACUUM</> syntax that allows options to be
-       specified inside parentheses (Itagaki Takahiro)
-      </para>
-
-      <para>
-       This allows greater flexibility for future <command>VACUUM</> options.
-       The old syntax is still supported, but only for pre-existing options.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Indexes</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow an index to be named automatically by omitting the index name in
-       <link linkend="SQL-CREATEINDEX"><command>CREATE INDEX</></link>
-       (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       By default, multicolumn indexes are now named after all their columns;
-       and index expression columns are now named based on their expressions
-       (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Reindexing shared system catalogs is now fully transactional
-       and crash-safe (Tom Lane)
-      </para>
-
-      <para>
-       Formerly, reindexing a shared index was only allowed in standalone
-       mode, and a crash during the operation could leave the index in
-       worse condition than it was before.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <literal>point_ops</> operator class for <acronym>GiST</>
-      (Teodor Sigaev)
-      </para>
-
-      <para>
-       This feature permits <acronym>GiST</> indexing of <type>point</>
-       columns.  The index can be used for several types of queries
-       such as <replaceable>point</> <literal>&lt;@</> <replaceable>polygon</>
-       (point is in polygon).  This should make many
-       <productname>PostGIS</> queries faster.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use red-black binary trees for <acronym>GIN</> index creation
-       (Teodor Sigaev)
-      </para>
-
-      <para>
-       Red-black trees are self-balancing.  This avoids slowdowns in
-       cases where the input is in nonrandom order.
-      </para>
-
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title>Data Types</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Allow <link linkend="datatype-binary"><type>bytea</></link> values
-      to be written in hex notation (Peter Eisentraut)
-     </para>
-
-     <para>
-      The server parameter <link
-      linkend="guc-bytea-output"><varname>bytea_output</></link> controls
-      whether hex or traditional format is used for <type>bytea</>
-      output.  Libpq's <function>PQescapeByteaConn()</> function automatically
-      uses the hex format when connected to <productname>PostgreSQL</> 9.0
-      or newer servers.
-     </para>
-
-     <para>
-      The new hex format will be directly compatible with more applications
-      that use binary data, allowing them to store and retrieve it without
-      extra conversion.  It is also significantly faster to read and write
-      than the traditional format.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow server parameter <link
-      linkend="guc-extra-float-digits">extra_float_digits</link>
-      to be increased to <literal>3</> (Tom Lane)
-     </para>
-
-     <para>
-      The previous maximum <varname>extra_float_digits</> setting was
-      <literal>2</>.  There are cases where 3 digits are needed to dump and
-      restore <type>float4</> values exactly.  <application>pg_dump</> will
-      now use the setting of 3 when dumping from a server that allows it.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Tighten input checking for <type>int2vector</> values (Caleb
-      Welton)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <sect4>
-    <title><link linkend="textsearch">Full Text Search</link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add prefix support in <literal>synonym</> dictionaries
-       (Teodor Sigaev)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <firstterm>filtering</> dictionaries (Teodor Sigaev)
-      </para>
-
-      <para>
-       Filtering dictionaries allow tokens to be modified then passed to
-       subsequent dictionaries.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow underscores in email-address tokens (Teodor Sigaev)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use more standards-compliant rules for parsing <acronym>URL</> tokens
-       (Tom Lane)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title>Functions</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Allow function calls to supply parameter names and match them to named
-      parameters in the function definition (Pavel Stehule)
-     </para>
-
-     <para>
-      For example, if a function is defined to take parameters <literal>a</>
-      and <literal>b</>, it can be called with <literal>func(a := 7, b
-      := 12)</> or <literal>func(b := 12, a := 7)</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Support locale-specific <link
-      linkend="functions-posix-regexp">regular expression</link>
-      processing with <acronym>UTF-8</> server encoding (Tom Lane)
-     </para>
-
-     <para>
-      Locale-specific regular expression functionality includes
-      case-insensitive matching and locale-specific character classes.
-      Previously, these features worked correctly for non-<acronym>ASCII</>
-      characters only if the database used a single-byte server encoding (such
-      as LATIN1).  They will still misbehave in multi-byte encodings other
-      than <acronym>UTF-8</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add support for scientific notation in <link
-      linkend="functions-formatting"><function>to_char()</></link>
-      (<link linkend="functions-formatting-numeric-table"><literal>EEEE</>
-      specification</link>)
-      (Pavel Stehule, Brendan Jurd)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>to_char()</> honor <link
-      linkend="functions-formatting-datetimemod-table"><literal>FM</></link>
-      (fill mode) in <literal>Y</>, <literal>YY</>, and
-      <literal>YYY</> specifications (Bruce Momjian, Tom Lane)
-     </para>
-
-     <para>
-      It was already honored by <literal>YYYY</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix <function>to_char()</> to output localized numeric and monetary
-      strings in the correct encoding on <productname>Windows</>
-      (Hiroshi Inoue, Itagaki Takahiro, Bruce Momjian)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Correct calculations of <link
-      linkend="functions-geometry-op-table"><quote>overlaps</quote></link>
-      and <quote>contains</quote> operations for polygons (Teodor Sigaev)
-     </para>
-
-     <para>
-      The polygon <literal>&amp;&amp;</> (overlaps) operator formerly just
-      checked to see if the two polygons' bounding boxes overlapped.  It now
-      does a more correct check.  The polygon <literal>@&gt;</> and
-      <literal>&lt;@</> (contains/contained by) operators formerly checked
-      to see if one polygon's vertexes were all contained in the other;
-      this can wrongly report <quote>true</> for some non-convex polygons.
-      Now they check that all line segments of one polygon are contained in
-      the other.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <sect4>
-    <title>Aggregates</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow aggregate functions to use <link
-       linkend="syntax-aggregates"><literal>ORDER BY</></link> (Andrew Gierth)
-      </para>
-
-      <para>
-       For example, this is now supported: <literal>array_agg(a ORDER BY
-       b)</>.  This is useful with aggregates for which the order of input
-       values is significant, and eliminates the need to use a nonstandard
-       subquery to determine the ordering.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Multi-argument aggregate functions can now use <literal>DISTINCT</>
-       (Andrew Gierth)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add the <link
-       linkend="functions-aggregate-table"><function>string_agg()</></link>
-       aggregate function to combine values into a single
-       string (Pavel Stehule)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Aggregate functions that are called with <literal>DISTINCT</> are
-       now passed NULL values if the aggregate transition function is
-       not marked as <literal>STRICT</> (Andrew Gierth)
-      </para>
-
-      <para>
-       For example, <literal>agg(DISTINCT x)</> might pass a NULL <literal>x</>
-       value to <function>agg()</>.  This is more consistent with the behavior
-       in non-<literal>DISTINCT</> cases.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Bit Strings</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="functions-binarystring-other"><function>get_bit()</></link>
-       and <function>set_bit()</> functions for <type>bit</>
-       strings, mirroring those for <type>bytea</> (Leonardo
-       F)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Implement <link
-       linkend="functions-string-sql"><function>OVERLAY()</></link>
-       (replace) for <type>bit</> strings and <type>bytea</>
-       (Leonardo F)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Object Information Functions</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="functions-admin-dbsize"><function>pg_table_size()</></link>
-       and <function>pg_indexes_size()</> to provide a more
-       user-friendly interface to the <function>pg_relation_size()</>
-       function (Bernd Helmle)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="functions-info-access-table"><function>has_sequence_privilege()</></link>
-       for sequence permission checking (Abhijit Menon-Sen)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Update the <link linkend="information-schema">information_schema</link>
-       views to conform to SQL:2008
-       (Peter Eisentraut)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make the <literal>information_schema</> views correctly display maximum
-       octet lengths for <type>char</> and <type>varchar</> columns (Peter
-       Eisentraut)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Speed up <literal>information_schema</> privilege views
-       (Joachim Wieland)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Function and Trigger Creation</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Support execution of anonymous code blocks using the <link
-       linkend="SQL-DO"><command>DO</></link> statement
-       (Petr Jelinek, Joshua Tolley, Hannu Valtonen)
-      </para>
-
-      <para>
-       This allows execution of server-side code without the need to create
-       and delete a temporary function definition.  Code can be executed in
-       any language for which the user has permissions to define a function.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Implement SQL-standard-compliant <link
-       linkend="SQL-CREATETRIGGER">per-column triggers</link>
-       (Itagaki Takahiro)
-      </para>
-
-      <para>
-       Such triggers are fired only when the specified column(s) are affected
-       by the query, e.g. appear in an <command>UPDATE</>'s <literal>SET</>
-       list.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add the <literal>WHEN</> clause to <link
-       linkend="SQL-CREATETRIGGER"><command>CREATE TRIGGER</></link>
-       to allow control over whether a trigger is fired (Itagaki
-       Takahiro)
-      </para>
-
-      <para>
-       While the same type of check can always be performed inside the
-       trigger, doing it in an external <literal>WHEN</> clause can have
-       performance benefits.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title>Server-Side Languages</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Add the <literal>OR REPLACE</> clause to <link
-      linkend="SQL-CREATELANGUAGE"><command>CREATE LANGUAGE</></link>
-      (Tom Lane)
-     </para>
-
-     <para>
-      This is helpful to optionally install a language if it does not
-      already exist, and is particularly helpful now that PL/pgSQL is
-      installed by default.
-     </para>
-    </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-    <title><link linkend="plpgsql">PL/pgSQL</link> Server-Side
-    Language</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Install PL/pgSQL by default (Bruce Momjian)
-      </para>
-
-      <para>
-       The language can still be removed from a particular database if the
-       administrator has security or performance concerns about making it
-       available.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve handling of cases where PL/pgSQL variable names conflict with
-       identifiers used in queries within a function
-       (Tom Lane)
-      </para>
-
-      <para>
-       The default behavior is now to throw an error when there is a conflict,
-       so as to avoid surprising behaviors.  This can be modified, via the
-       configuration parameter <link
-       linkend="plpgsql-var-subst"><varname>plpgsql.variable_conflict</></link>
-       or the per-function option <literal>#variable_conflict</>, to allow
-       either the variable or the query-supplied column to be used.  In any
-       case PL/pgSQL will no longer attempt to substitute variables in places
-       where they would not be syntactically valid.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make PL/pgSQL use the main lexer, rather than its own version
-       (Tom Lane)
-      </para>
-
-      <para>
-       This ensures accurate tracking of the main system's behavior for details
-       such as string escaping.  Some user-visible details, such as the set
-       of keywords considered reserved in PL/pgSQL, have changed in
-       consequence.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Avoid throwing an unnecessary error for an invalid record reference
-       (Tom Lane)
-      </para>
-
-      <para>
-       An error is now thrown only if the reference is actually fetched,
-       rather than whenever the enclosing expression is reached.  For
-       example, many people have tried to do this in triggers:
-<programlisting>
-if TG_OP = 'INSERT' and NEW.col1 = ... then
-</programlisting>
-       This will now actually work as expected.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve PL/pgSQL's ability to handle row types with dropped columns
-       (Pavel Stehule)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow input parameters to be assigned values within
-       PL/pgSQL functions (Steve Prentice)
-      </para>
-
-      <para>
-       Formerly, input parameters were treated as being declared
-       <literal>CONST</>, so the function's code could not change their
-       values.  This restriction has been removed to simplify
-       porting of functions from other DBMSes that do not impose the
-       equivalent restriction.  An input parameter now acts like a local
-       variable initialized to the passed-in value.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve error location reporting in PL/pgSQL (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <replaceable>count</> and <literal>ALL</> options to <command>MOVE
-       FORWARD</>/<literal>BACKWARD</> in PL/pgSQL (Pavel Stehule)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow PL/pgSQL's <literal>WHERE CURRENT OF</> to use a cursor
-       variable (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow PL/pgSQL's <command>OPEN <replaceable>cursor</> FOR EXECUTE</> to
-       use parameters (Pavel Stehule, Itagaki Takahiro)
-      </para>
-
-      <para>
-       This is accomplished with a new <literal>USING</> clause.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title><link linkend="plperl">PL/Perl</link> Server-Side Language</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add new PL/Perl functions: <link
-       linkend="plperl-utility-functions"><function>quote_literal()</></link>,
-       <function>quote_nullable()</>, <function>quote_ident()</>,
-       <function>encode_bytea()</>, <function>decode_bytea()</>,
-       <function>looks_like_number()</>,
-       <function>encode_array_literal()</>,
-       <function>encode_array_constructor()</> (Tim Bunce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add server parameter <link
-       linkend="guc-plperl-on-init"><varname>plperl.on_init</></link> to
-       specify a PL/Perl initialization function (Tim
-       Bunce)
-      </para>
-
-      <para>
-       <link
-       linkend="guc-plperl-on-plperl-init"><varname>plperl.on_plperl_init</></link>
-       and <link
-       linkend="guc-plperl-on-plperl-init"><varname>plperl.on_plperlu_init</></link>
-       are also available for initialization that is specific to the trusted
-       or untrusted language respectively.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support <command>END</> blocks in PL/Perl (Tim Bunce)
-      </para>
-
-      <para>
-       <command>END</> blocks do not currently allow database access.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>use strict</> in PL/Perl (Tim Bunce)
-      </para>
-
-      <para>
-       Perl <literal>strict</> checks can also be globally enabled with the
-       new server parameter <link
-       linkend="guc-plperl-use-strict"><varname>plperl.use_strict</></link>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>require</> in PL/Perl (Tim Bunce)
-      </para>
-
-      <para>
-       This basically tests to see if the module is loaded, and if not,
-       generates an error.  It will not allow loading of modules that
-       the administrator has not preloaded via the initialization parameters.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <command>use feature</> in PL/Perl if Perl version 5.10 or
-       later is used (Tim Bunce)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Verify that PL/Perl return values are valid in the server encoding
-       (Andrew Dunstan)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title><link linkend="plpython">PL/Python</link> Server-Side Language</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add Unicode support in PL/Python (Peter Eisentraut)
-      </para>
-
-      <para>
-       Strings are automatically converted from/to the server encoding as
-       necessary.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <type>bytea</> support in PL/Python (Caleb Welton)
-      </para>
-
-      <para>
-       <type>Bytea</> values passed into PL/Python are now represented as
-       binary, rather than the PostgreSQL <type>bytea</> text format.
-       <type>Bytea</> values containing null bytes are now also output
-       properly from PL/Python.  Passing of boolean, integer, and float
-       values was also improved.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support <link linkend="plpython-arrays">arrays</link> as parameters and
-       return values in PL/Python (Peter Eisentraut)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve mapping of SQL domains to Python types (Peter Eisentraut)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <application>Python</> 3 support to PL/Python (Peter Eisentraut)
-      </para>
-
-      <para>
-       The new server-side language is called <link
-       linkend="plpython-python23"><literal>plpython3u</></link>.  This
-       cannot be used in the same session with the
-       <application>Python</> 2 server-side language.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve error location and exception reporting in PL/Python (Peter Eisentraut)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title>Client Applications</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Add an <option>--analyze-only</> option to <link
-     linkend="APP-VACUUMDB"><command>vacuumdb</></link>, to analyze without
-     vacuuming (Bruce Momjian)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <sect4>
-    <title><link linkend="APP-PSQL"><application>psql</></link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add support for quoting/escaping the values of <application>psql</>
-       <link linkend="APP-PSQL-variables">variables</link> as SQL strings or
-       identifiers (Pavel Stehule, Robert Haas)
-      </para>
-
-      <para>
-       For example, <literal>:'var'</> will produce the value of
-       <literal>var</> quoted and properly escaped as a literal string, while
-       <literal>:"var"</> will produce its value quoted and escaped as an
-       identifier.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Ignore a leading UTF-8-encoded Unicode byte-order marker in
-       script files read by <application>psql</> (Itagaki Takahiro)
-      </para>
-
-      <para>
-       This is enabled when the client encoding is <acronym>UTF-8</>.
-       It improves compatibility with certain editors, mostly on Windows,
-       that insist on inserting such markers.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <command>psql --file -</> to properly honor <link
-       linkend="R1-APP-PSQL-3"><option>--single-transaction</></link>
-       (Bruce Momjian)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Avoid overwriting of <application>psql</>'s command-line history when
-       two <application>psql</> sessions are run concurrently (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve <application>psql</>'s tab completion support (Itagaki
-       Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Show <literal>\timing</> output when it is enabled, regardless of
-       <quote>quiet</> mode (Peter Eisentraut)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect5>
-    <title><application>psql</> Display</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Improve display of wrapped columns in <application>psql</> (Roger
-        Leigh)
-       </para>
-
-       <para>
-        This behavior is now the default.
-        The previous formatting is available by using <command>\pset linestyle
-        old-ascii</>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <application>psql</> to use fancy Unicode line-drawing
-        characters via <command>\pset linestyle unicode</> (Roger Leigh)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect5>
-
-    <sect5>
-     <title><application>psql</> <link
-     linkend="APP-PSQL-meta-commands"><command>\d</></link>
-     Commands</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Make <command>\d</> show child tables that inherit from the specified
-        parent (Damien Clochard)
-       </para>
-
-       <para>
-        <command>\d</> shows only the number of child tables, while
-        <command>\d+</> shows the names of all child tables.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Show definitions of index columns in <command>\d index_name</>
-        (Khee Chin)
-       </para>
-
-       <para>
-        The definition is useful for expression indexes.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Show a view's defining query only in
-        <command>\d+</>, not in <command>\d</> (Peter Eisentraut)
-       </para>
-
-       <para>
-        Always including the query was deemed overly verbose.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect5>
-   </sect4>
-
-   <sect4>
-    <title><link linkend="APP-PGDUMP"><application>pg_dump</></link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Make <application>pg_dump</>/<application>pg_restore</>
-       <link linkend="pg-dump-options"><option>--clean</></link>
-       also remove large objects (Itagaki Takahiro)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <application>pg_dump</> to properly dump large objects when
-       <literal>standard_conforming_strings</> is enabled (Tom Lane)
-      </para>
-
-      <para>
-       The previous coding could fail when dumping to an archive file
-       and then generating script output from <application>pg_restore</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <application>pg_restore</> now emits large-object data in hex format
-       when generating script output (Tom Lane)
-      </para>
-
-      <para>
-       This could cause compatibility problems if the script is then
-       loaded into a pre-9.0 server.  To work around that, restore
-       directly to the server, instead.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>pg_dump</> to dump comments attached to columns
-       of composite types (Taro Minowa (Higepon))
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <application>pg_dump</> <link
-       linkend="pg-dump-options"><option>--verbose</></link>
-       output the <application>pg_dump</> and server versions
-       in text output mode (Jim Cox, Tom Lane)
-      </para>
-
-      <para>
-       These were already provided in custom output mode.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <application>pg_restore</> now complains if any command-line arguments
-       remain after the switches and optional file name (Tom Lane)
-      </para>
-
-      <para>
-       Previously, it silently ignored any such arguments.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title><link
-    linkend="app-pg-ctl"><application>pg_ctl</></link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow <application>pg_ctl</> to be used safely to start the
-       <application>postmaster</> during a system reboot (Tom Lane)
-      </para>
-
-      <para>
-       Previously, <application>pg_ctl</>'s parent process could have been
-       mistakenly identified as a running <application>postmaster</> based on
-       a stale <application>postmaster</> lock file, resulting in a transient
-       failure to start the database.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Give <application>pg_ctl</> the ability to initialize the database
-       (by invoking <application>initdb</>) (Zdenek Kotala)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title><application>Development Tools</></title>
-
-   <sect4>
-    <title><link linkend="libpq"><application>libpq</></link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add new <application>libpq</> functions
-       <link
-       linkend="libpq-connect"><function>PQconnectdbParams()</></link>
-       and <function>PQconnectStartParams()</> (Guillaume
-       Lelarge)
-      </para>
-
-      <para>
-       These functions are similar to <function>PQconnectdb()</> and
-       <function>PQconnectStart()</> except that they accept a null-terminated
-       array of connection options, rather than requiring all options to
-       be provided in a single string.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <application>libpq</> functions <link
-       linkend="libpq-exec-escape-string"><function>PQescapeLiteral()</></link>
-       and <function>PQescapeIdentifier()</> (Robert Haas)
-      </para>
-
-      <para>
-       These functions return appropriately quoted and escaped SQL string
-       literals and identifiers. The caller is not required to pre-allocate
-       the string result, as is required by <function>PQescapeStringConn()</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for a per-user service file (<link
-       linkend="libpq-pgservice"><filename>.pg_service.conf</></link>),
-       which is checked before the site-wide service file
-       (Peter Eisentraut)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Properly report an error if the specified <application>libpq</> service
-       cannot be found (Peter Eisentraut)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="libpq-keepalives">TCP keepalive settings</link>
-       in libpq (Tollef Fog Heen, Fujii Masao, Robert Haas)
-      </para>
-
-      <para>
-       Keepalive settings were already supported on the server end of
-       TCP connections.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Avoid extra system calls to block and unblock <literal>SIGPIPE</>
-       in <application>libpq</>, on platforms that offer alternative methods
-       (Jeremy Kerr)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       When a <link linkend="libpq-pgpass"><filename>.pgpass</></link>-supplied
-       password fails, mention where the password came from in the error
-       message (Bruce Momjian)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Load all SSL certificates given in the client certificate file
-       (Tom Lane)
-      </para>
-
-      <para>
-       This improves support for indirectly-signed SSL certificates.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title><link linkend="ecpg"><application>ecpg</></link></title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add <link linkend="ecpg-descriptors"><acronym>SQLDA</></link>
-       (SQL Descriptor Area) support to <application>ecpg</>
-       (Boszormenyi Zoltan)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add the <link linkend="ecpg-descriptors"><command>DESCRIBE</>
-       [ <literal>OUTPUT</> ]</link> statement to <application>ecpg</>
-       (Boszormenyi Zoltan)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add an <link linkend="ecpg-library">ECPGtransactionStatus</link>
-       function to return the current transaction status (Bernd Helmle)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add the <literal>string</> data type in <application>ecpg</>
-       Informix-compatibility mode (Boszormenyi Zoltan)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>ecpg</> to use <literal>new</> and <literal>old</>
-       variable names without restriction (Michael Meskes)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <application>ecpg</> to use variable names in
-       <function>free()</> (Michael Meskes)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <function>ecpg_dynamic_type()</> return zero for non-SQL3 data
-       types (Michael Meskes)
-      </para>
-
-      <para>
-       Previously it returned the negative of the data type OID.
-       This could be confused with valid type OIDs, however.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support <type>long long</> types on platforms that already have 64-bit
-       <type>long</> (Michael Meskes)
-      </para>
-     </listitem>
-
-     </itemizedlist>
-
-     <sect5>
-      <title><application>ecpg</> Cursors</title>
-
-      <itemizedlist>
-
-      <listitem>
-       <para>
-        Add out-of-scope cursor support in <application>ecpg</>'s native mode
-        (Boszormenyi Zoltan)
-       </para>
-
-       <para>
-        This allows <command>DECLARE</> to use variables that are not in
-        scope when <command>OPEN</> is called. This facility already existed
-        in <application>ecpg</>'s Informix-compatibility mode.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow dynamic cursor names in <application>ecpg</> (Boszormenyi Zoltan)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <application>ecpg</> to use noise words <literal>FROM</> and
-        <literal>IN</> in <command>FETCH</> and <command>MOVE</> (Boszormenyi
-        Zoltan)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect5>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title>Build Options</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Enable client thread safety by default (Bruce Momjian)
-     </para>
-
-     <para>
-      The thread-safety option can be disabled with <link
-      linkend="configure"><literal>configure</></link>
-      <option>--disable-thread-safety</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add support for controlling the Linux out-of-memory killer
-      (Alex Hunsaker, Tom Lane)
-     </para>
-
-     <para>
-      Now that <filename>/proc/self/oom_adj</> allows disabling
-      of the <productname>Linux</> out-of-memory (<acronym>OOM</>)
-      killer, it's recommendable to disable OOM kills for the postmaster.
-      It may then be desirable to re-enable OOM kills for the postmaster's
-      child processes.  The new compile-time option <link
-      linkend="linux-memory-overcommit"><literal>LINUX_OOM_ADJ</></link>
-      allows the killer to be reactivated for child processes.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <sect4>
-    <title>Makefiles</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       New <filename>Makefile</> targets <link
-       linkend="build"><literal>world</></link>,
-       <literal>install-world</>, and <literal>installcheck-world</>
-       (Andrew Dunstan)
-      </para>
-
-      <para>
-       These are similar to the existing <literal>all</>, <literal>install</>,
-       and <literal>installcheck</> targets, but they also build the
-       <acronym>HTML</> documentation, build and test <filename>contrib</>,
-       and test server-side languages and <application>ecpg</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add data and documentation installation location control to <link
-       linkend="xfunc-c-pgxs"><acronym>PGXS</></link> Makefiles
-       (Mark Cave-Ayland)
-      </para>
-     </listitem>
-
-    <listitem>
-     <para>
-      Add Makefile rules to build the <productname>PostgreSQL</> documentation
-      as a single <acronym>HTML</> file or as a single plain-text file
-      (Peter Eisentraut, Bruce Momjian)
-     </para>
-    </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Windows</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Support compiling on <link
-       linkend="install-windows">64-bit
-       <productname>Windows</></link> and running in 64-bit
-       mode (Tsutomu Yamada, Magnus Hagander)
-      </para>
-
-      <para>
-       This allows for large shared memory sizes on <productname>Windows</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support server builds using <link
-       linkend="install-windows-full"><productname>Visual Studio
-       2008</></link> (Magnus Hagander)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title>Source Code</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Distribute prebuilt documentation in a subdirectory tree, rather than
-      as tar archive files inside the distribution tarball
-      (Peter Eisentraut)
-     </para>
-
-     <para>
-      For example, the prebuilt <acronym>HTML</> documentation is now in
-      <filename>doc/src/sgml/html/</>; the manual pages are packaged
-      similarly.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make the server's lexer reentrant (Tom Lane)
-     </para>
-
-     <para>
-      This was needed for use of the lexer by PL/pgSQL.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve speed of memory allocation (Tom Lane, Greg Stark)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      User-defined constraint triggers now have entries in
-      <structname>pg_constraint</> as well as <structname>pg_trigger</>
-      (Tom Lane)
-     </para>
-
-     <para>
-      Because of this change,
-      <structname>pg_constraint</>.<structfield>pgconstrname</> is now
-      redundant and has been removed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add system catalog columns
-      <structname>pg_constraint</>.<structfield>conindid</> and
-      <structname>pg_trigger</>.<structfield>tgconstrindid</>
-      to better document the use of indexes for constraint
-      enforcement (Tom Lane)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow multiple conditions to be communicated to backends using a single
-      operating system signal (Fujii Masao)
-     </para>
-
-     <para>
-      This allows new features to be added without a platform-specific
-      constraint on the number of signal conditions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve source code test coverage, including <filename>contrib</>, PL/Python,
-      and PL/Perl (Peter Eisentraut, Andrew Dunstan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Remove the use of flat files for system table bootstrapping
-      (Tom Lane, Alvaro Herrera)
-     </para>
-
-     <para>
-      This improves performance when using many roles or
-      databases, and eliminates some possible failure conditions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Automatically generate the initial contents of
-      <structname>pg_attribute</> for <quote>bootstrapped</> catalogs
-      (John Naylor)
-     </para>
-
-     <para>
-      This greatly simplifies changes to these catalogs.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Split the processing of
-      <command>INSERT</>/<command>UPDATE</>/<command>DELETE</> operations out
-      of <filename>execMain.c</> (Marko Tiikkaja)
-     </para>
-
-     <para>
-      Updates are now executed in a separate ModifyTable node.  This change is
-      necessary infrastructure for future improvements.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Simplify translation of <application>psql</>'s SQL help text
-      (Peter Eisentraut)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Reduce the lengths of some file names so that all file paths in the
-      distribution tarball are less than 100 characters (Tom Lane)
-     </para>
-
-     <para>
-      Some decompression programs have problems with longer file paths.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add a new <link
-      linkend="errcodes-table"><literal>ERRCODE_INVALID_PASSWORD</></link>
-      <literal>SQLSTATE</> error code (Bruce Momjian)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      With authors' permissions, remove the few remaining personal source code
-      copyright notices (Bruce Momjian)
-     </para>
-
-     <para>
-      The personal copyright notices were insignificant but the community
-      occasionally had to answer questions about them.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add new documentation <link linkend="non-durability">section</link>
-      about running <productname>PostgreSQL</> in non-durable mode
-      to improve performance (Bruce Momjian)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Restructure the <acronym>HTML</> documentation
-      <filename>Makefile</> rules to make their dependency checks work
-      correctly, avoiding unnecessary rebuilds (Peter Eisentraut)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Use <productname>DocBook</> <acronym>XSL</> stylesheets for man page
-      building, rather than <productname>Docbook2X</> (Peter Eisentraut)
-     </para>
-
-     <para>
-      This changes the set of tools needed to build the man pages.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve PL/Perl code structure (Tim Bunce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve error context reports in PL/Perl (Alexey Klyukin)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   <sect4>
-    <title>New Build Requirements</title>
-
-     <para>
-      Note that these requirements do not apply when building from a
-      distribution tarball, since tarballs include the files that these
-      programs are used to build.
-     </para>
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Require <application>Autoconf</> 2.63 to build
-       <application>configure</> (Peter Eisentraut)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Require <application>Flex</> 2.5.31 or later to build
-       from a <acronym>CVS</> checkout (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Require <application>Perl</> version 5.8 or later to build
-       from a <acronym>CVS</> checkout (John Naylor, Andrew Dunstan)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Portability</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Use a more modern <acronym>API</> for <application>Bonjour</> (Tom Lane)
-      </para>
-
-      <para>
-       Bonjour support now requires <productname>OS X</> 10.3 or later.
-       The older API has been deprecated by Apple.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add spinlock support for the <productname>SuperH</>
-       architecture (Nobuhiro Iwamatsu)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow non-<application>GCC</> compilers to use inline functions if
-       they support them (Kurt Harriman)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove support for platforms that don't have a working 64-bit
-       integer data type (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Restructure use of <literal>LDFLAGS</> to be more consistent
-       across platforms (Tom Lane)
-      </para>
-
-      <para>
-       <literal>LDFLAGS</> is now used for linking both executables and shared
-       libraries, and we add on <literal>LDFLAGS_EX</> when linking
-       executables, or <literal>LDFLAGS_SL</> when linking shared libraries.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Server Programming</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Make backend header files safe to include in <productname>C++</>
-       (Kurt Harriman, Peter Eisentraut)
-      </para>
-
-      <para>
-       These changes remove keyword conflicts that previously made
-       <productname>C++</> usage difficult in backend code.  However, there
-       are still other complexities when using <productname>C++</> for backend
-       functions. <literal>extern "C" { }</> is still necessary in
-       appropriate places, and memory management and error handling are
-       still problematic.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link
-       linkend="xaggr"><function>AggCheckCallContext()</></link>
-       for use in detecting if a <productname>C</> function is
-       being called as an aggregate (Hitoshi Harada)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change calling convention for <function>SearchSysCache()</> and related
-       functions to avoid hard-wiring the maximum number of cache keys
-       (Robert Haas)
-      </para>
-
-      <para>
-       Existing calls will still work for the moment, but can be expected to
-       break in 9.1 or later if not converted to the new style.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Require calls of <function>fastgetattr()</> and
-       <function>heap_getattr()</> backend macros to provide a non-NULL fourth
-       argument (Robert Haas)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Custom typanalyze functions should no longer rely on
-       <structname>VacAttrStats</>.<structfield>attr</> to determine the type
-       of data they will be passed (Tom Lane)
-      </para>
-
-      <para>
-       This was changed to allow collection of statistics on index columns
-       for which the storage type is different from the underlying column
-       data type.  There are new fields that tell the actual datatype being
-       analyzed.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Server Hooks</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add parser hooks for processing ColumnRef and ParamRef nodes
-       (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add a ProcessUtility hook so loadable modules can control utility
-       commands (Itagaki Takahiro)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-   <sect4>
-    <title>Binary Upgrade Support</title>
-
-    <itemizedlist>
-
-    <listitem>
-     <para>
-      Add <link linkend="pgupgrade"><filename>contrib/pg_upgrade</></link>
-      to support in-place upgrades (Bruce Momjian)
-     </para>
-
-     <para>
-      This avoids the requirement of dumping/reloading the database when
-      upgrading to a new major release of PostgreSQL, thus reducing downtime
-      by orders of magnitude. It supports upgrades to 9.0
-      from PostgreSQL 8.3 and 8.4.
-     </para>
-    </listitem>
-
-     <listitem>
-      <para>
-       Add support for preserving relation <link
-       linkend="catalog-pg-class"><structname>relfilenode</></link> values
-       during binary upgrades (Bruce Momjian)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for preserving <structname>pg_type</>
-       and <structname>pg_enum</> OIDs during binary upgrades
-       (Bruce Momjian)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Move data files within tablespaces into
-       <productname>PostgreSQL</>-version-specific subdirectories
-       (Bruce Momjian)
-      </para>
-
-      <para>
-       This simplifies binary upgrades.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect4>
-
-  </sect3>
-
-  <sect3>
-   <title>Contrib</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Add multithreading option (<option>-j</>) to <link
-      linkend="pgbench"><filename>contrib/pgbench</></link>
-      (Itagaki Takahiro)
-     </para>
-
-     <para>
-      This allows multiple <acronym>CPU</>s to be used by pgbench,
-      reducing the risk of pgbench itself becoming the test bottleneck.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <command>\shell</> and <command>\setshell</> meta
-      commands to <link
-      linkend="pgbench"><filename>contrib/pgbench</></link>
-      (Michael Paquier)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New features for <link
-      linkend="dict-xsyn"><filename>contrib/dict_xsyn</></link>
-      (Sergey Karpov)
-     </para>
-
-     <para>
-      The new options are <literal>matchorig</>, <literal>matchsynonyms</>,
-      and <literal>keepsynonyms</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add full text dictionary <link
-      linkend="unaccent"><filename>contrib/unaccent</></link>
-      (Teodor Sigaev)
-     </para>
-
-     <para>
-      This filtering dictionary removes accents from letters, which
-      makes full-text searches over multiple languages much easier.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <link
-      linkend="CONTRIB-DBLINK-GET-NOTIFY"><function>dblink_get_notify()</></link>
-      to <filename>contrib/dblink</> (Marcus Kempe)
-     </para>
-
-     <para>
-      This allows asynchronous notifications in <productname>dblink</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <filename>contrib/dblink</>'s handling of dropped columns
-      (Tom Lane)
-     </para>
-
-     <para>
-      This affects <link
-      linkend="CONTRIB-DBLINK-BUILD-SQL-INSERT"><function>dblink_build_sql_insert()</></link>
-      and related functions.  These functions now number columns according
-      to logical not physical column numbers.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Greatly increase <link
-      linkend="hstore"><filename>contrib/hstore</></link>'s data
-      length limit, and add B-tree and hash support so <literal>GROUP
-      BY</> and <literal>DISTINCT</> operations are possible on
-      <type>hstore</> columns (Andrew Gierth)
-     </para>
-
-     <para>
-      New functions and operators were also added.  These improvements
-      make <type>hstore</> a full-function key-value store embedded in
-      <productname>PostgreSQL</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <link
-      linkend="passwordcheck"><filename>contrib/passwordcheck</></link>
-      to support site-specific password strength policies (Laurenz
-      Albe)
-     </para>
-
-     <para>
-      The source code of this module should be modified to implement
-      site-specific password policies.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <link
-      linkend="pgarchivecleanup"><filename>contrib/pg_archivecleanup</></link>
-      tool (Simon Riggs)
-     </para>
-
-     <para>
-      This is designed to be used in the
-      <literal>archive_cleanup_command</literal>
-      server parameter, to remove no-longer-needed archive files.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add query text to <link
-      linkend="auto-explain"><filename>contrib/auto_explain</></link>
-      output (Andrew Dunstan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add buffer access counters to <link
-      linkend="pgstatstatements"><filename>contrib/pg_stat_statements</></link>
-      (Itagaki Takahiro)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Update <link
-      linkend="server-start"><filename>contrib/start-scripts/linux</></link>
-      to use <filename>/proc/self/oom_adj</> to disable the
-      <link linkend="linux-memory-overcommit"><productname>Linux</>
-      out-of-memory</link> (<acronym>OOM</>) killer (Alex
-      Hunsaker, Tom Lane)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect3>
- </sect2>
-</sect1>
diff --git a/doc-xc/src/sgml/release-9.1.sgmlin b/doc-xc/src/sgml/release-9.1.sgmlin
deleted file mode 100644
index 2d6c8edf9b..0000000000
--- a/doc-xc/src/sgml/release-9.1.sgmlin
+++ /dev/null
@@ -1,2811 +0,0 @@
-<!-- doc/src/sgml/release-9.1.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-9-1">
-  <title>Release 9.1</title>
-
-  <note>
-   <title>Release Date</title>
-   <simpara>2011-??-??</simpara>
-  </note>
-
-  <para>CURRENT AS OF 2011-06-09</para>
-
-  <sect2>
-   <title>Overview</title>
-
-   <para>
-    This release of
-    <productname>PostgreSQL</> adds numerous major features, including:
-   </para>
-
-   <para>
-    (summary to be added)
-   </para>
-
-   <para>
-    The above items are explained in more detail in the sections below.
-   </para>
-
-  </sect2>
-
-  <sect2>
-
-  <title>Migration to Version 9.1</title>
-
-   <para>
-    A dump/restore using <application>pg_dump</application>,
-    or use of <application>pg_upgrade</application>, is required
-    for those wishing to migrate data from any previous
-    release.
-   </para>
-
-   <para>
-    Version 9.1 contains a number of changes that may affect compatibility
-    with previous releases.  Observe the following incompatibilities:
-   </para>
-
-   <sect3>
-    <title>Strings</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Change the default value of <link
-       linkend="guc-standard-conforming-strings"><varname>standard_conforming_strings</></link>
-       to on (Robert Haas)
-      </para>
-
-      <para>
-       By default, backslashes are now ordinary characters in string literals,
-       not escape characters.  This change removes a long-standing
-       incompatibility with the SQL standard.  <link
-       linkend="guc-escape-string-warning"><varname>escape_string_warning</></link>
-       has produced warnings about this usage for years.  <literal>E''</>
-       strings are the proper way to embed backslash escapes in strings and are
-       unaffected by this change.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Casting</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Disallow function-style and attribute-style data type casts for
-       composite types (Tom Lane)
-      </para>
-
-      <para>
-       For example, disallow
-       <literal><replaceable>composite_value</>.text</literal> and
-       <literal>text(<replaceable>composite_value</>)</literal>.
-       Unintentional uses of this syntax have frequently resulted in bug
-       reports; although it was not a bug, it seems better to go back to
-       rejecting such expressions.
-       The <literal>CAST</> and <literal>::</> syntaxes are still available
-       for use when a cast of an entire composite value is actually intended.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Tighten casting checks for domains based on arrays (Tom Lane)
-      </para>
-
-      <para>
-       When a domain is based on an array type, it is allowed to <quote>look
-       through</> the domain type to access the array elements, including
-       subscripting the domain value to fetch or assign an element.
-       Assignment to an element of such a domain value, for instance via
-       <literal>UPDATE ... SET domaincol[5] = ...</>, will now result in
-       rechecking the domain type's constraints, whereas before the checks
-       were skipped.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Arrays</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Change <link
-       linkend="array-functions-table"><function>string_to_array()</></link>
-       to return an empty array for a zero-length string (Pavel
-       Stehule)
-      </para>
-
-      <para>
-       Previously this returned a null value.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Change <link
-       linkend="array-functions-table"><function>string_to_array()</></link>
-       so a <literal>NULL</> separator splits the string into characters
-       (Pavel Stehule)
-      </para>
-
-      <para>
-       Previously this returned a null value.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Object Modification</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Fix improper checks for before/after triggers (Tom Lane)
-      </para>
-
-      <para>
-       Triggers can now be fired in three cases: <literal>BEFORE</>,
-       <literal>AFTER</>, or <literal>INSTEAD OF</> some action.
-       Trigger function authors should verify that their logic behaves
-       sanely in all three cases.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Require superuser or <literal>CREATEROLE</> permissions in order to
-        set role comments (Tom Lane)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Server Settings</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Change <link
-       linkend="functions-recovery-info-table"><function>pg_last_xlog_receive_location()</></link>
-       so it never moves backwards (Fujii Masao)
-      </para>
-
-      <para>
-       Previously <function>pg_last_xlog_receive_location()</> could
-       move backward when streaming replication is restarted.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Have logging of replication connections honor <link
-       linkend="guc-log-connections"><varname>log_connections</></link>
-       (Magnus Hagander)
-      </para>
-
-      <para>
-       Previously replication connections were always logged.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title><link linkend="plpgsql">PL/pgSQL</link> Server-Side Language</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Change PL/pgSQL's <literal>RAISE</> command without parameters
-       to be catchable by the attached exception block (Piyush Newe)
-      </para>
-
-      <para>
-       Previously <literal>RAISE</> in a code block was always scoped to
-       an attached exception block, so it was uncatchable at the same
-       scope.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Adjust PL/pgSQL's error line numbering code to be consistent
-       with other PLs (Pavel Stehule)
-      </para>
-
-      <para>
-       Previously, PL/pgSQL would ignore (not count) an empty line at the
-       start of the function body.  Since this was inconsistent with all
-       other languages, the special case was removed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make PL/pgSQL complain about conflicting IN and OUT parameter names
-       (Tom Lane)
-      </para>
-
-      <para>
-       Formerly, the collision was not detected, and the name would just
-       silently refer to only the OUT parameter.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Type modifiers of PL/pgSQL variables are now visible to the SQL parser
-       (Tom Lane)
-      </para>
-
-      <para>
-       A type modifier (such as a varchar length limit) attached to a PL/pgSQL
-       variable was formerly enforced during assignments, but was ignored for
-       all other purposes.  Such variables will now behave more like table
-       columns declared with the same modifier.  This is not expected to make
-       any visible difference in most cases, but it could result in subtle
-       changes for some SQL commands issued by PL/pgSQL functions.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Other Incompatibilities</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Make <link
-       linkend="monitoring-stats-funcs-table"><function>pg_stat_reset()</></link>
-       reset all database-level statistics (Tomas Vondra)
-      </para>
-
-      <para>
-       Some <structname>pg_stat_database</> counters were not being reset.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Fix some <link
-        linkend="infoschema-triggers"><structname>information_schema.triggers</></link>
-        column names to match the new SQL-standard names (Dean Rasheed)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Treat <application>ECPG</> cursor names as case-insensitive (Zoltan Boszormenyi)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-    <para>
-     Version 9.1 has ...
-    </para>
-
-   <sect3>
-    <title>Server</title>
-
-    <sect4>
-     <title>Performance</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Support unlogged tables using the <link
-        linkend="SQL-CREATETABLE-description"><literal>UNLOGGED</></link>
-        option in <link linkend="SQL-CREATETABLE"><command>CREATE
-        TABLE</></link> (Robert Haas)
-       </para>
-
-       <para>
-        Such tables provide better update performance than regular tables,
-        but are not crash-safe: their contents are automatically cleared in
-        case of a server crash.  Their contents do not propagate to
-        replication slaves, either.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <literal>FULL OUTER JOIN</literal> to be implemented as a
-        hash join, and allow either side of a <literal>LEFT OUTER JOIN</>
-        or <literal>RIGHT OUTER JOIN</> to be hashed (Tom Lane)
-       </para>
-
-       <para>
-        Previously <literal>FULL OUTER JOIN</literal> could only be
-        implemented as a merge join, and <literal>LEFT OUTER JOIN</literal>
-        and <literal>RIGHT OUTER JOIN</literal> could hash only the nullable
-        side of the join.  These changes provide additional query optimization
-        possibilities.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Merge duplicate fsync requests on busy systems (Robert Haas,
-         Greg Smith)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve performance of <link
-        linkend="guc-commit-siblings"><varname>commit_siblings</></link>
-        (Greg Smith)
-       </para>
-
-       <para>
-        This allows the use of <varname>commit_siblings</varname> with
-        less overhead.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Reduce the memory requirement for large ispell dictionaries
-        (Pavel Stehule, Tom Lane)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Optimizer</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Allow inheritance table scans to return meaningfully-sorted
-        results (Greg Stark, Hans-Jurgen Schonig, Robert Haas, Tom Lane)
-       </para>
-
-       <para>
-        This allows better optimization of queries that use <literal>ORDER
-        BY</>, <literal>LIMIT</>, or <literal>MIN</>/<literal>MAX</> with
-        inherited tables.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Improve GIN index scan cost estimation (Teodor Sigaev)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve cost estimation for aggregates and window functions (Tom Lane)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Authentication</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Support host names and host suffixes
-        (e.g. <literal>.example.com</>) in <link
-        linkend="auth-pg-hba-conf"><filename>pg_hba.conf</></link>
-        (Peter Eisentraut)
-       </para>
-
-       <para>
-        Previously only host <acronym>IP</> addresses and <acronym>CIDR</>
-        values were supported.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support the key word <literal>all</> in the host column of <link
-        linkend="auth-pg-hba-conf"><filename>pg_hba.conf</></link>
-        (Peter Eisentraut)
-       </para>
-
-       <para>
-        Previously people used <literal>0.0.0.0/0</> or <literal>::/0</>
-        for this.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Reject <literal>local</> lines in <link
-        linkend="auth-pg-hba-conf"><filename>pg_hba.conf</></link>
-        on platforms that don't support Unix-socket connections
-        (Magnus Hagander)
-       </para>
-
-       <para>
-        Formerly, such lines were silently ignored, which could be surprising.
-        This makes the behavior more like other unsupported cases.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <link linkend="gssapi-auth"><acronym>GSSAPI</></link>
-        to be used to authenticate to servers via <link
-        linkend="sspi-auth"><acronym>SSPI</></link> (Christian Ullrich)
-       </para>
-
-       <para>
-        Specifically this allows Unix-based <acronym>GSSAPI</> clients
-        to do <acronym>SSPI</> authentication with Windows servers.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <link linkend="auth-ident"><literal>ident</literal></link>
-        authentication over local sockets is now known as
-        <link linkend="auth-peer"><literal>peer</literal></link>
-        (Magnus Hagander)
-       </para>
-
-       <para>
-        The old term is still accepted for backward compatibility.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Rewrite <link linkend="auth-peer"><acronym>peer</></link>
-        authentication to avoid use of credential control messages (Tom Lane)
-       </para>
-
-       <para>
-        This change makes the peer authentication code simpler and
-        better-performing.  However, it requires the platform to provide the
-        <function>getpeereid</> function or an equivalent socket operation.
-        So far as is known, the only platform for which peer authentication
-        worked before and now will not is pre-5.0 NetBSD.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Monitoring</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add details to the logging of restartpoints and checkpoints,
-        which is controlled by <link
-        linkend="guc-log-checkpoints"><varname>log_checkpoints</></link>
-        (Fujii Masao, Greg Smith)
-       </para>
-
-       <para>
-        New details show <acronym>WAL</> file and sync activity.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add <link
-         linkend="guc-log-file-mode"><varname>log_file_mode</></link>
-         which controls the permissions on log files created by the
-         logging collector (Martin Pihlak)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Statistical Views</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add <structfield>client_hostname</structfield> column to <link
-        linkend="monitoring-stats-views-table"><structname>pg_stat_activity</></link>
-        (Peter Eisentraut)
-       </para>
-
-       <para>
-        Previously only the client address was reported.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <link
-        linkend="monitoring-stats-views-table"><structname>pg_stat_xact_*</></link>
-        statistics functions and views (Joel Jacobson)
-       </para>
-
-       <para>
-        These are like the database-wide statistics counter views, but
-        reflect counts for only the current transaction.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add time of last reset in database-level and background writer
-         statistics views (Tomas Vondra)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add columns showing the number of vacuum and analyze operations
-         in <link
-         linkend="monitoring-stats-views-table"><structname>pg_stat_*_tables</></link>
-         views (Magnus Hagander)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <structfield>buffers_backend_fsync</> column to <link
-        linkend="monitoring-stats-views-table"><structname>pg_stat_bgwriter</></link>
-        (Greg Smith)
-       </para>
-
-       <para>
-        This new column counts the number of times a backend fsyncs a
-        buffer.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Server Settings</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Allow auto-tuning of <link
-        linkend="guc-wal-buffers"><varname>wal_buffers</></link> (Greg
-        Smith)
-       </para>
-
-       <para>
-        <varname>wal_buffers</> is now auto-tuned by default based on
-        the size of <varname>shared_buffers</>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Increase the maximum values for
-        <link linkend="guc-deadlock-timeout"><varname>deadlock_timeout</varname></link>,
-        <link linkend="guc-log-min-duration-statement"><varname>log_min_duration_statement</varname></link>, and
-        <link linkend="guc-log-autovacuum-min-duration"><varname>log_autovacuum_min_duration</varname></link>
-        (Peter Eisentraut)
-       </para>
-
-       <para>
-        The maximum value for each of these parameters was previously
-        only about 35 minutes.  Much larger values are now allowed.
-       </para>
-      </listitem>
-
-      </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Replication and Recovery</title>
-
-   <sect4>
-    <title>Streaming Replication and Continuous Archiving</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow <link linkend="synchronous-replication">synchronous
-       replication</link> (Simon Riggs, Fujii Masao)
-      </para>
-
-      <para>
-       This allows the primary to wait for a standby to write the transaction
-       information to disk before acknowledging the commit.
-       One standby at a time can take the role of the synchronous standby,
-       as controlled by the
-       <link linkend="guc-synchronous-standby-names"><varname>synchronous_standby_names</varname></link>
-       setting.  Synchronous replication can be enabled or disabled on a
-       per-transaction basis using the
-       <link linkend="guc-synchronous-commit"><varname>synchronous_commit</></link>
-       setting.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add protocol support for sending file system backups to standbys using
-       the streaming replication network connection (Magnus Hagander,
-       Heikki Linnakangas)
-      </para>
-
-      <para>
-       This avoids the requirement of manually transferring a file
-       system backup when setting up a standby server.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add
-       <link linkend="guc-replication-timeout"><varname>replication_timeout</></link>
-       setting (Fujii Masao, Heikki Linnakangas)
-      </para>
-
-      <para>
-       Replication connections that are idle for more than the
-       <varname>replication_timeout</> interval will be terminated
-       automatically.  Formerly, a failed connection was typically not
-       detected until the TCP timeout elapsed, which is inconveniently
-       long in many situations.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add command-line tool <link
-       linkend="app-pgbasebackup"><application>pg_basebackup</></link>
-       for creating a new standby server or database backup (Magnus
-       Hagander)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add replication <link linkend="SQL-CREATEROLE">permission</link>
-       for roles (Magnus Hagander)
-      </para>
-
-      <para>
-       This is a read-only permission used for streaming replication.
-       It allows a non-superuser role to be used for replication connections.
-       Previously only superusers could initiate replication
-       connections; superusers still have this permission by default.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Replication Monitoring</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add system view <link
-        linkend="monitoring-stats-views-table"><structname>pg_stat_replication</></link>
-        which displays activity of <acronym>WAL</> sender processes (Itagaki
-        Takahiro, Simon Riggs)
-       </para>
-
-       <para>
-        This reports the status of all connected standby servers.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add monitoring function <link
-        linkend="functions-recovery-info-table"><function>pg_last_xact_replay_timestamp()</></link>
-        (Fujii Masao)
-       </para>
-
-       <para>
-        This returns the time at which the primary generated the most
-        recent commit or abort record applied on the standby.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Hot Standby</title>
-
-     <itemizedlist>
-
-     <listitem>
-      <para>
-       Add configuration parameter <link
-       linkend="guc-hot-standby-feedback"><varname>hot_standby_feedback</></link>
-       to enable standbys to postpone cleanup of old row versions on the
-       primary (Simon Riggs)
-      </para>
-
-      <para>
-       This helps avoid cancelling long-running queries on the standby.
-      </para>
-     </listitem>
-
-      <listitem>
-       <para>
-        Add the <link
-        linkend="monitoring-stats-views-table"><structname>pg_stat_database_conflicts</></link>
-        system view to show queries that have been canceled and the
-        reason (Magnus Hagander)
-       </para>
-
-       <para>
-        Cancellations can occur because of dropped tablespaces, lock
-        timeouts, old snapshots, pinned buffers, and deadlocks.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add a <structfield>conflicts</> count to <link
-        linkend="monitoring-stats-views-table"><structname>pg_stat_database</></link>
-        (Magnus Hagander)
-       </para>
-
-       <para>
-        This is the number of conflicts that occurred in the database.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Increase the maximum values for
-        <link linkend="guc-max-standby-archive-delay"><varname>max_standby_archive_delay</varname></link> and
-        <link linkend="guc-max-standby-streaming-delay"><varname>max_standby_streaming_delay</varname></link>.
-       </para>
-
-       <para>
-        The maximum value for each of these parameters was previously
-        only about 35 minutes.  Much larger values are now allowed.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <link
-        linkend="errcodes-table"><literal>ERRCODE_T_R_DATABASE_DROPPED</></link>
-        error code to report recovery conflicts due to dropped databases
-        (Tatsuo Ishii)
-       </para>
-
-       <para>
-        This is useful for connection pooling software.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Recovery Control</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add functions to control streaming replication replay (Simon
-        Riggs)
-       </para>
-
-       <para>
-        The new functions are <link
-        linkend="functions-recovery-control-table"><function>pg_xlog_replay_pause()</></link>,
-        <link
-        linkend="functions-recovery-control-table"><function>pg_xlog_replay_resume()</></link>,
-        and the status function <link
-        linkend="functions-recovery-control-table"><function>pg_is_xlog_replay_paused()</></link>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <filename>recovery.conf</> setting <link
-        linkend="pause-at-recovery-target"><varname>pause_at_recovery_target</></link>
-        to pause recovery at target (Simon Riggs)
-       </para>
-
-       <para>
-        This allows a recovery server to be queried to check whether
-        the recovery point is the one desired.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add the ability to create named restore points using <link
-        linkend="functions-admin-backup-table"><function>pg_create_restore_point()</></link>
-        (Jaime Casanova)
-       </para>
-
-       <para>
-        These named restore points can be specified as recovery
-        targets using the new <filename>recovery.conf</> setting
-        <link linkend="recovery-target-name"><varname>recovery_target_name</></link>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow standby recovery to switch to a new timeline automatically
-        (Heikki Linnakangas)
-       </para>
-
-       <para>
-        Now standby servers scan the archive directory for new
-        timelines periodically.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <link
-        linkend="guc-restart-after-crash"><varname>restart_after_crash</></link>
-        setting which disables automatic server restart after a backend
-        crash (Robert Haas)
-       </para>
-
-       <para>
-        This allows external cluster management software to take control
-        of whether servers restart or not.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <link
-        linkend="recovery-config"><filename>recovery.conf</></link>
-        to use the same quoting behavior as <filename>postgresql.conf</>
-        (Dimitri Fontaine)
-       </para>
-
-       <para>
-        Previously all values had to be quoted.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Queries</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add a true <link
-        linkend="xact-serializable">serializable</link> isolation
-        level (Kevin Grittner, Dan Ports)
-       </para>
-
-       <para>
-        Previously, asking for serializable isolation guaranteed only that a
-        single MVCC snapshot would be used for the entire transaction, which
-        allowed certain documented anomalies.  The old snapshot isolation
-        behavior is still accessible by requesting the <link
-        linkend="xact-repeatable-read"><literal>REPEATABLE READ</></link>
-        isolation level.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow data-modification commands
-        (<command>INSERT</>/<command>UPDATE</>/<command>DELETE)</> in
-        <link linkend="queries-with"><literal>WITH</></link> clauses
-        (Marko Tiikkaja, Hitoshi Harada)
-       </para>
-
-       <para>
-        These commands can use <literal>RETURNING</> to pass data up to the
-        containing query.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <link linkend="queries-with"><literal>WITH</></link>
-        clauses to be attached to <command>INSERT</>, <command>UPDATE</>,
-        <command>DELETE</> statements (Marko Tiikkaja, Hitoshi Harada)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow non-<link linkend="queries-group"><literal>GROUP
-        BY</></link> columns in the query target list when the primary
-        key is specified in the <literal>GROUP BY</> clause (Peter
-        Eisentraut)
-       </para>
-
-       <para>
-        Some other database system already allowed this behavior, and
-        because of the primary key, the result is unambiguous.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow use of the key word <literal>DISTINCT</> in <link
-        linkend="queries-union"><literal>UNION</>/<literal>INTERSECT</>/<literal>EXCEPT</></link>
-        clauses (Tom Lane)
-       </para>
-
-       <para>
-        <literal>DISTINCT</> is the default behavior so use of this
-        key word is redundant, but the SQL standard allows it.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Fix ordinary queries with rules to use the same snapshot behavior
-        as <command>EXPLAIN ANALYZE</> (Marko Tiikkaja)
-       </para>
-
-       <para>
-        Previously <command>EXPLAIN ANALYZE</> used a slightly different
-        snapshot for queries involving rules.  The <command>EXPLAIN ANALYZE</>
-        behavior was judged to be more logical.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    <sect4>
-     <title>Strings</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add per-column <link
-        linkend="collation">collation</link> support
-        (Peter Eisentraut, Tom Lane)
-       </para>
-
-       <para>
-        Previously collation could only be set at database creation.
-        Collation can now be set per column, domain, index, or
-        expression, via the SQL-standard <literal>COLLATE</> clause.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Object Manipulation</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add <link linkend="extend-extensions">extensions</link> which
-        simplify packaging of additions to <productname>PostgreSQL</>
-        (Dimitri Fontaine, Tom Lane)
-       </para>
-
-       <para>
-        Extensions are controlled by the new <link
-        linkend="SQL-CREATEEXTENSION"><command>CREATE</></link>/<link
-        linkend="SQL-ALTEREXTENSION"><command>ALTER</></link>/<link
-        linkend="SQL-DROPEXTENSION"><command>DROP EXTENSION</></link>
-        commands.  This replaces ad-hoc methods of grouping objects that
-        are added to a <productname>PostgreSQL</> installation.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add support for <link linkend="SQL-CREATEFOREIGNTABLE">foreign
-        tables</link> (Shigeru Hanada, Robert Haas, Jan Urbanski,
-        Heikki Linnakangas)
-       </para>
-
-       <para>
-        This allows data stored outside the database to be used like
-        native <productname>PostgreSQL</>-stored data.  Foreign tables
-        are currently read-only, however.
-       </para>
-      </listitem>
-
-     <listitem>
-      <para>
-         Allow new values to be added to an existing enum type via
-         <link linkend="SQL-ALTERTYPE"><command>ALTER TYPE</></link> (Andrew
-         Dunstan)
-      </para>
-     </listitem>
-
-      <listitem>
-       <para>
-        Add <link linkend="SQL-ALTERTYPE"><command>ALTER TYPE ...
-        ADD/DROP/ALTER/RENAME ATTRIBUTE</></link> (Peter Eisentraut)
-       </para>
-
-       <para>
-        This allows modification of composite types.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    <sect4>
-     <title><command>ALTER</> Object</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add <literal>RESTRICT</>/<literal>CASCADE</> to <link
-        linkend="SQL-ALTERTYPE"><command>ALTER TYPE</></link> operations
-        on typed tables (Peter Eisentraut)
-       </para>
-
-       <para>
-        This controls
-        <literal>ADD</>/<literal>DROP</>/<literal>ALTER</>/<literal>RENAME
-        ATTRIBUTE</> cascading behavior.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support <literal>ALTER TABLE <replaceable>name</> {OF | NOT OF}
-        <replaceable>type</></literal>
-        (Noah Misch)
-       </para>
-
-       <para>
-        This syntax allows a standalone table to be made into a typed table,
-        or a typed table to be made standalone.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add support for more object types in <command>ALTER ... SET
-        SCHEMA</> commands (Dimitri Fontaine)
-       </para>
-
-       <para>
-        This command is now supported for conversions, operators, operator
-        classes, operator families, text search configurations, text search
-        dictionaries, text search parsers, and text search templates.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><link linkend="SQL-CREATETABLE"><command>CREATE/ALTER TABLE</></link></title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add <command>ALTER TABLE ...
-        ADD UNIQUE/PRIMARY KEY USING INDEX</command>
-        (Gurjeet Singh)
-       </para>
-
-       <para>
-        This allows a primary key or unique constraint to be defined using an
-        existing unique index, including a concurrently created unique index.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <command>ALTER TABLE</>
-        to add foreign keys without validation (Simon Riggs)
-       </para>
-
-       <para>
-        The new option is called <literal>NOT VALID</>, which can
-        later be modified to <literal>VALIDATED</> and validation
-        checks performed. Together these allow you to add a foreign key
-        with minimal impact on read and write operations.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <link linkend="SQL-ALTERTABLE"><command>ALTER TABLE
-        ... SET DATA TYPE</command></link> to avoid table rewrites in
-        appropriate cases (Noah Misch, Robert Haas)
-       </para>
-
-       <para>
-        For example, converting a <type>varchar</> column to
-        <type>text</> no longer requires a rewrite of the table.
-        However, increasing the length constraint on a
-        <type>varchar</> column still requires a table rewrite.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <link linkend="SQL-CREATETABLE"><command>CREATE TABLE IF
-        NOT EXISTS</></link> syntax (Robert Haas)
-       </para>
-
-       <para>
-        This allows table creation without causing an error if the
-        table already exists.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Fix possible <quote>tuple concurrently updated</quote> error
-        when two backends attempted to add an inheritance
-        child to the same table at the same time (Robert Haas)
-       </para>
-
-       <para>
-        <link linkend="sql-altertable"><command>ALTER TABLE</command></link>
-        now takes a stronger lock on the parent table, so that both children do
-        not try to update it simultaneously.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Object Permissions</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add a <link linkend="SQL-SECURITY-LABEL"><command>SECURITY
-        LABEL</></link> command (KaiGai Kohei)
-       </para>
-
-       <para>
-        This allows security labels to be assigned to objects.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Utility Operations</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Add transaction-level <link linkend="advisory-locks">advisory
-       locks</link> (Marko Tiikkaja)
-      </para>
-
-      <para>
-       This is similar to the existing session-level advisory locks,
-       but the locks are automatically released at transaction end.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Make <link linkend="SQL-TRUNCATE"><command>TRUNCATE ... RESTART
-       IDENTITY</></link> restart sequences transactionally (Steve
-       Singer)
-      </para>
-
-      <para>
-       Previously the counter could have been left out of sync if a
-       backend crashed between the on-commit truncation activity and
-       commit completion.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title><link linkend="SQL-COPY"><command>COPY</></link></title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add <literal>ENCODING</> option to <link
-        linkend="SQL-COPY"><command>COPY TO/FROM</></link> (Hitoshi
-        Harada, Itagaki Takahiro)
-       </para>
-
-       <para>
-        This allows the encoding of the <command>COPY</> file to be
-        specified separately from client encoding.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add bidirectional <link linkend="SQL-COPY"><command>COPY</></link>
-        protocol support (Fujii Masao)
-       </para>
-
-       <para>
-        This is currently only used by streaming replication.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><link linkend="SQL-EXPLAIN"><command>EXPLAIN</></link></title>
-
-      <itemizedlist>
-
-      <listitem>
-       <para>
-        Make <command>EXPLAIN VERBOSE</> show the function call expression
-        in a <literal>FunctionScan</literal> node (Tom Lane)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><link linkend="SQL-VACUUM"><command>VACUUM</></link></title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add additional details to the output of <link
-        linkend="SQL-VACUUM"><command>VACUUM FULL VERBOSE</></link>
-        and <link linkend="SQL-CLUSTER"><command>CLUSTER VERBOSE</></link>
-        (Itagaki Takahiro)
-       </para>
-
-       <para>
-        New information includes the live and dead tuple count and
-        whether <command>CLUSTER</> is using an index to rebuild.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Prevent <link linkend="autovacuum">autovacuum</link> from
-        waiting if it cannot acquire a lock (Robert Haas)
-       </para>
-
-       <para>
-        It will try to vacuum later.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><link linkend="SQL-CLUSTER"><command>CLUSTER</></link></title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Allow <command>CLUSTER</> to sort the table rather than scanning
-        the index when it seems likely to be cheaper (Leonardo Francalanci)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Indexes</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add nearest-neighbor (order-by-operator) searching to <link
-        linkend="GiST"><acronym>GiST</> indexes</link> (Teodor Sigaev, Tom Lane)
-       </para>
-
-       <para>
-        This allows <acronym>GiST</> indexes to quickly return the
-        <replaceable>N</> closest values in a query with <literal>LIMIT</>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <link linkend="GIN"><acronym>GIN</> indexes</link> to index null
-        and empty values (Tom Lane)
-       </para>
-
-       <para>
-        This allows full <acronym>GIN</> index scans, and fixes various
-        corner cases in which GIN scans would fail.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <link linkend="GIN"><acronym>GIN</> indexes</link> to
-        better recognize duplicate search entries (Tom Lane)
-       </para>
-
-       <para>
-        This reduces the cost of index scans, especially in cases where
-        it avoids unnecessary full index scans.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Fix <link linkend="GiST"><acronym>GiST</> indexes</link> to be fully
-        crash-safe (Heikki Linnakangas)
-       </para>
-
-       <para>
-        Previously there were rare cases where a <command>REINDEX</>
-        would be required (you would be informed).
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Data Types</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Allow <type>numeric</> to use a more compact, two-byte header
-       in common cases (Robert Haas)
-      </para>
-
-      <para>
-       Previously all <type>numeric</> values had four-byte headers;
-       this saves on disk storage.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Add support for dividing <type>money</> by <type>money</>
-        (Andy Balholm)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow binary I/O on type <type>void</type> (Radoslaw Smogura)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve hypotenuse calculations for geometric operators (Paul Matthews)
-      </para>
-
-      <para>
-       This avoids unnecessary overflows, and may also be more accurate.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support hashing array values (Tom Lane)
-      </para>
-
-      <para>
-       This provides additional query optimization possibilities.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Don't treat a composite type as sortable unless all its column types
-       are sortable (Tom Lane)
-      </para>
-
-      <para>
-       This avoids possible <quote>could not identify a comparison function</>
-       failures at runtime, if it is possible to implement the query without
-       sorting.  Also, <command>ANALYZE</> won't try to use inappropriate
-       statistics-gathering methods for columns of such composite types.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title>Casting</title>
-
-     <itemizedlist>
-
-     <listitem>
-      <para>
-        Add support for casting between <type>money</> and <type>numeric</>
-        (Andy Balholm)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add support for casting from <type>int4</> and <type>int8</>
-       to <type>numeric</> (Joey Adams)
-      </para>
-     </listitem>
-
-      <listitem>
-       <para>
-        Allow casting a table's row type to the table's supertype if
-        it's a typed table (Peter Eisentraut)
-       </para>
-
-       <para>
-        This is analogous to the existing facility that allows casting a row
-        type to a supertable's row type.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><link linkend="functions-xml"><acronym>XML</></link></title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add <acronym>XML</> function <link
-        linkend="xml-exists"><literal>XMLEXISTS</></link> and <link
-        linkend="xml-exists"><function>xpath_exists()</></link>
-        functions (Mike Fowler)
-       </para>
-
-       <para>
-        These are used for XPath matching.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <acronym>XML</> functions <link
-        linkend="xml-is-well-formed"><function>xml_is_well_formed()</></link>,
-        <link
-        linkend="xml-is-well-formed"><function>xml_is_well_formed_document()</></link>,
-        <link
-        linkend="xml-is-well-formed"><function>xml_is_well_formed_content()</></link>
-        (Mike Fowler)
-       </para>
-
-       <para>
-        These check whether the input is properly-formed <acronym>XML</>.
-        They provide functionality that was previously available only in
-        the deprecated <filename>contrib/xml2</filename> module.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Functions</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add SQL function <link
-        linkend="format"><function>format(text)</></link>, which
-        behaves like C's <function>printf()</> (Pavel Stehule, Robert
-        Haas)
-       </para>
-
-       <para>
-        It currently supports formats for strings, SQL literals, and
-        SQL identifiers.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add string functions <link
-        linkend="functions-string-other"><function>concat()</></link>,
-        <link
-        linkend="functions-string-other"><function>concat_ws()</></link>,
-        <link linkend="functions-string-other"><function>left()</></link>,
-        <link linkend="functions-string-other"><function>right()</></link>,
-        and <link
-        linkend="functions-string-other"><function>reverse()</></link>
-        (Pavel Stehule)
-       </para>
-
-       <para>
-        These improve compatibility with other database products.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add function <link
-         linkend="functions-admin-genfile"><function>pg_read_binary_file()</></link>
-         to read binary files (Dimitri Fontaine, Itagaki Takahiro)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add a single-parameter version of function <link
-         linkend="functions-admin-genfile"><function>pg_read_file()</></link>
-         to read an entire file (Dimitri Fontaine, Itagaki Takahiro)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add three-parameter forms of <link
-         linkend="array-functions-table"><function>array_to_string()</></link>
-         and <link
-         linkend="array-functions-table"><function>string_to_array()</></link>
-         for null value processing control (Pavel Stehule)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    <sect4>
-     <title>Object Information Functions</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add the <link
-        linkend="functions-info-catalog-table"><function>pg_describe_object()</></link>
-        function (Alvaro Herrera)
-       </para>
-
-       <para>
-        This function is used to obtain a human-readable string describing
-        an object, based on the <link
-        linkend="catalog-pg-class"><structname>pg_class</structname></link>
-        OID, object OID, and sub-object ID.  It can be used to help
-        interpret the contents of <link
-        linkend="catalog-pg-depend"><structname>pg_depend</structname></link>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Update comments for built-in operators and their underlying
-         functions (Tom Lane)
-       </para>
-
-       <para>
-        Functions that are meant to be used via an associated operator
-        are now commented as such.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add variable <link
-        linkend="guc-quote-all-identifiers"><varname>quote_all_identifiers</></link>
-        to force the quoting of all identifiers in <command>EXPLAIN</>
-        and in system catalog functions like <link
-        linkend="functions-info-catalog-table"><function>pg_get_viewdef()</></link>
-        (Robert Haas)
-       </para>
-
-       <para>
-        This makes exporting schemas to tools and other databases with
-        different quoting rules easier.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add columns to the <link
-        linkend="infoschema-sequences"><structname>information_schema.sequences</></link>
-        system view (Peter Eisentraut)
-       </para>
-
-       <para>
-        Previously, though the view existed, the columns about the
-        sequence parameters were unimplemented.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <literal>public</> as a pseudo-role name in <link
-        linkend="functions-info-access-table"><function>has_table_privilege()</></link>
-        and related functions (Alvaro Herrera)
-       </para>
-
-       <para>
-        This allows checking for public permissions.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Function and Trigger Creation</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Support <link linkend="SQL-CREATETRIGGER"><literal>INSTEAD
-        OF</></link> triggers on views (Dean Rasheed)
-       </para>
-
-       <para>
-        This feature can be used to implement fully updatable views.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Minimize lock levels for <link
-        linkend="SQL-CREATETRIGGER"><command>CREATE TRIGGER</></link>
-        and many <link linkend="SQL-ALTERTABLE"><command>ALTER
-        TABLE</></link> and <link linkend="SQL-CREATERULE"><command>CREATE
-        RULE</></link> operations (Simon Riggs)
-       </para>
-
-       <para>
-        This improves database availability when altering active databases.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Server-Side Languages</title>
-
-    <sect4>
-     <title><link linkend="plpgsql">PL/pgSQL</link> Server-Side Language</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add <link linkend="plpgsql-foreach-array"><command>FOREACH IN
-        ARRAY</></link> to <link linkend="plpgsql">PL/pgSQL</link>
-        (Pavel Stehule)
-       </para>
-
-       <para>
-        This is more efficient and readable than previous methods of
-        iterating through the elements of an array value.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <command>RAISE</command> without parameters to be caught in
-        the same places that could catch a <command>RAISE ERROR</command>
-        from the same location (Piyush Newe)
-       </para>
-
-       <para>
-        The previous coding threw the error
-        from the block containing the active exception handler.
-        The new behavior is more consistent with other DBMS products.
-       </para>
-      </listitem>
-
-    </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><link linkend="plperl">PL/Perl</link> Server-Side Language</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Allow generic record arguments to PL/Perl functions (Andrew
-        Dunstan)
-       </para>
-
-       <para>
-        PL/Perl functions can now be declared to accept type <type>record</>.
-        The behavior is the same as for any named composite type.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Convert PL/Perl array arguments to Perl arrays (Alexey Klyukin,
-        Alex Hunsaker)
-       </para>
-
-       <para>
-        String representations are still available.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Convert PL/Perl composite-type arguments to Perl hashes
-        (Alexey Klyukin, Alex Hunsaker)
-       </para>
-
-       <para>
-        String representations are still available.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><link linkend="plpython">PL/Python</link> Server-Side Language</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add table function support for PL/Python (Jan Urbanski)
-       </para>
-
-       <para>
-        PL/Python can now return multiple <literal>OUT</> parameters
-        and record sets.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add a validator to PL/Python (Jan Urbanski)
-       </para>
-
-       <para>
-        This allows PL/Python functions to be syntax-checked at function
-        creation time.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow exceptions for SQL queries in PL/Python (Jan Urbanski)
-       </para>
-
-       <para>
-        This allows access to SQL-generated exception error codes from
-        PL/Python exception blocks.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add PL/Python explicit subtransactions (Jan Urbanski)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add PL/Python functions for quoting strings (Jan Urbanski)
-       </para>
-
-       <para>
-        The functions are <link
-        linkend="plpython-util"><literal>plpy.quote_ident</></link>,
-        <link linkend="plpython-util"><literal>plpy.quote_literal</></link>,
-        and <link
-        linkend="plpython-util"><literal>plpy.quote_nullable</></link>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add traceback information to PL/Python errors (Jan Urbanski)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Report PL/Python errors from iterators with <literal>PLy_elog</> (Jan
-         Urbanski)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Fix exception handling with Python 3 (Jan Urbanski)
-       </para>
-
-       <para>
-        Exception classes were previously not available in
-        <literal>plpy</> under Python 3.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Client Applications</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-        Mark <link
-        linkend="APP-CREATELANG"><application>createlang</></link>
-        and <link linkend="APP-DROPLANG"><application>droplang</></link>
-        as deprecated now that they just invoke extension commands (Tom
-        Lane)
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title><link linkend="APP-PSQL"><application>psql</></link></title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-         Add <application>psql</> command <literal>\conninfo</>
-         to show current connection information (David Christensen)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add <application>psql</> command <literal>\sf</> to
-         show a function's definition (Pavel Stehule)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add <application>psql</> command <literal>\dL</> to list
-         languages (Fernando Ike)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <option>S</> (<quote>system</>) option to <application>psql</>'s
-        <literal>\dn</> (list schemas) command (Tom Lane)
-       </para>
-
-       <para>
-        <literal>\dn</> without <literal>S</> now suppresses system
-        schemas.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow <application>psql</>'s <literal>\e</> and <literal>\ef</>
-        commands to accept a line number to be used to position the
-        cursor in the editor (Pavel Stehule)
-       </para>
-
-       <para>
-        This is passed to the editor according to the
-        <envar>EDITOR_LINENUMBER_SWITCH</> psql variable.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Have <application>psql</> set the client encoding from the
-        operating system locale by default (Heikki Linnakangas)
-       </para>
-
-       <para>
-        This only happens if the <envar>PGCLIENTENCODING</> environment
-        variable is not set.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <literal>\d</literal> distinguish between unique
-        indexes and unique constraints (Josh Kupershmidt)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Make <literal>\dt+</literal> report <function>pg_table_size</>
-        instead of <function>pg_relation_size</> when talking to 9.0 or
-        later servers (Bernd Helmle)
-       </para>
-
-       <para>
-        This is a more useful measure of table size, but note that it is
-        not identical to what was previously reported in the same display.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Additional tab completion support (Itagaki Takahiro, Pavel Stehule,
-        Andrey Popp, Christoph Berg, David Fetter, Josh Kupershmidt)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><link linkend="APP-PGDUMP"><application>pg_dump</></link></title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-         Add <link linkend="APP-PGDUMP"><application>pg_dump</></link>
-         and <link
-         linkend="APP-PG-DUMPALL"><application>pg_dumpall</></link>
-         option <option>--quote-all-identifiers</> to force quoting
-         of all identifiers (Robert Haas)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <literal>directory</> format to <application>pg_dump</>
-        (Joachim Wieland, Heikki Linnakangas)
-       </para>
-
-       <para>
-        This is internally similar to the <literal>tar</>
-        <application>pg_dump</> format.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><link linkend="APP-PG-CTL"><application>pg_ctl</></link></title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Fix <application>pg_ctl</>
-        so it no longer incorrectly reports that the server is not
-        running (Bruce Momjian)
-       </para>
-
-       <para>
-        Previously this could happen if the server was running but
-        <application>pg_ctl</> could not authenticate.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve <application>pg_ctl</> start's <quote>wait</quote>
-        (<option>-w</>) option (Bruce Momjian, Tom Lane)
-       </para>
-
-       <para>
-        The wait mode is now significantly more robust.  It will not get
-        confused by non-default postmaster port numbers, non-default
-        Unix-domain socket locations, permission problems, or stale
-        postmaster lock files.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add <literal>promote</> option to <application>pg_ctl</> to
-         switch a standby server to primary (Fujii Masao)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title><application>Development Tools</></title>
-
-    <sect4>
-     <title><link linkend="libpq"><application>libpq</></link></title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add a libpq connection option <literal>client_encoding</>
-        which behaves like the <envar>PGCLIENTENCODING</> environment
-        variable (Heikki Linnakangas)
-       </para>
-
-       <para>
-        The value <literal>auto</> sets the client encoding based on
-        the operating system locale.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <link
-        linkend="libpq-pqlibversion"><function>PQlibVersion()</></link>
-        function which returns the libpq library version (Magnus
-        Hagander)
-       </para>
-
-       <para>
-        libpq already had <function>PQserverVersion()</> which returns
-        the server version.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Allow libpq database clients to
-        check the user name of the server process using <link
-        linkend="libpq-connect-requirepeer"><literal>requirepeer</></link>
-        when connecting via Unix-domain sockets
-        (Peter Eisentraut)
-       </para>
-
-       <para>
-        <productname>PostgreSQL</> already allowed servers to check
-        the client user name when connecting via Unix-domain sockets.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <link linkend="libpq-pqping"><function>PQping()</></link>
-        and <link
-        linkend="libpq-pqpingparams"><function>PQpingParams()</></link>
-        to libpq (Bruce Momjian, Tom Lane)
-       </para>
-
-       <para>
-        These functions allow detection of the server's status without
-        trying to open a new session.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title><link linkend="ecpg"><application>ECPG</></link></title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-         Allow ECPG to accept dynamic cursor names even in
-         <literal>WHERE CURRENT OF</literal> clauses
-       </para>
-      </listitem>
-
-     </itemizedlist>
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Build Options</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Use <literal>+Olibmerrno</> compile flag with HP-UX C compilers
-        that accept it (Ibrar Ahmed)
-       </para>
-
-       <para>
-        This avoids possible misbehavior of math library calls on recent
-        HP platforms.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    <sect4>
-     <title>Makefiles</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Improved parallel make support (Peter Eisentraut)
-       </para>
-
-       <para>
-        This allows for faster compiles.  Also, <literal>make -k</>
-        now works more consistently.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Require <acronym>GNU</> <link
-         linkend="install-requirements"><application>make</></link>
-         3.80 or newer (Peter Eisentraut)
-       </para>
-
-       <para>
-        This is necessary because of the parallel-make improvements.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <literal>make maintainer-check</> target
-        (Peter Eisentraut)
-       </para>
-
-       <para>
-        This target performs various source code checks that are not
-        appropriate for either the build or the regression tests.  Currently:
-        duplicate_oids, SGML syntax and tabs check, NLS syntax check.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Support <literal>make check</> in <filename>contrib</>
-        (Peter Eisentraut)
-       </para>
-
-       <para>
-        Formerly only <literal>make installcheck</> worked, but now
-        there is support for testing in a temporary installation.
-        The top-level <literal>make check-world</> target now includes
-        testing <filename>contrib</> this way.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Windows</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-         On Windows, allow <link
-         linkend="app-pg-ctl"><application>pg_ctl</></link> to register
-         the service as auto-start or start-on-demand (Quan Zongliang)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add support for collecting <link linkend="windows-crash-dumps">crash
-        dumps</link> on Windows (Craig Ringer, Magnus Hagander)
-       </para>
-
-       <para>
-        <productname>minidumps</> can now be generated by non-debug
-        Windows binaries and analyzed by standard debugging tools.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Enable building with the MinGW64 compiler (Andrew Dunstan)
-       </para>
-
-       <para>
-        This allows building 64-bit Windows binaries even on non-Windows
-        platforms via cross-compiling.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Source Code</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Revise the API for GUC variable assign hooks (Tom Lane)
-       </para>
-
-       <para>
-        The previous functions of assign hooks are now split between check
-        hooks and assign hooks, where the former can fail but the latter
-        shouldn't.  This change will impact add-on modules that define custom
-        GUC parameters.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add latches to the source code to wait for events (Heikki
-         Linnakangas)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Centralize data modification permissions-checking logic
-         (KaiGai Kohei)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add missing <function>get_<replaceable>object</>_oid()</function> functions, for consistency
-         (Robert Haas)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Improve ability to use C++ compilers for <link
-         linkend="xfunc-c">compiling add-on modules</link> by removing
-         conflicting key words (Tom Lane)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add support for DragonFly <acronym>BSD</> (Rumko)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Expose <function>quote_literal_cstr()</> for backend use
-         (Robert Haas)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Run <link linkend="build">regression tests</link> in the
-        default encoding (Peter Eisentraut)
-       </para>
-
-       <para>
-        Regression tests were previously always run with
-        <literal>SQL_ASCII</> encoding.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add <application>src/tools/git_changelog</> to replace
-         <application>cvs2cl</> and <application>pgcvslog</> (Robert
-         Haas, Tom Lane)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <application>git-external-diff</> script to
-        <filename>src/tools</> (Bruce Momjian)
-       </para>
-
-       <para>
-        This is used to generate context diffs from git.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    <sect4>
-     <title>Server Hooks</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-         Add source code hooks to check permissions (Robert Haas,
-         Stephen Frost)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add post-object-creation function hooks for use by security
-         frameworks (KaiGai Kohei)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add a client authentication hook (KaiGai Kohei)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Contrib</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Modify <filename>contrib</> modules and stored procedure
-       languages to install via the new <link
-       linkend="extend-extensions">extension</link> mechanism (Tom Lane,
-       Dimitri Fontaine)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="file-fdw"><filename>contrib/file_fdw</></link>
-       foreign-data wrapper (Shigeru Hanada)
-      </para>
-
-      <para>
-       Foreign tables using this foreign data wrapper can read flat files
-       in a manner very similar to <command>COPY</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Add nearest-neighbor support to <link
-        linkend="pgtrgm"><filename>contrib/pg_trgm</></link> and <link
-        linkend="btree-gist"><filename>contrib/btree_gist</></link>
-        (Teodor Sigaev)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Add <link
-        linkend="btree-gist"><filename>contrib/btree_gist</></link>
-        support for searching on not-equals (Jeff Davis)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Fix <link
-        linkend="fuzzystrmatch"><filename>contrib/fuzzystrmatch</></link>'s
-        <function>levenshtein()</> function to handle multibyte characters
-        (Alexander Korotkov)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Add <function>ssl_cipher()</> and <function>ssl_version()</>
-        functions to <link
-        linkend="sslinfo"><filename>contrib/sslinfo</></link> (Robert
-        Haas)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fix <link linkend="intarray"><filename>contrib/intarray</></link>
-       and <link linkend="hstore"><filename>contrib/hstore</></link>
-       to give consistent results with indexed empty arrays (Tom Lane)
-      </para>
-
-      <para>
-       Previously an empty-array query that used an index might return
-       different results from one that used a sequential scan.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Allow <link linkend="intarray"><filename>contrib/intarray</></link>
-       to work properly on multidimensional arrays (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In
-       <link linkend="intarray"><filename>contrib/intarray</></link>,
-       avoid errors complaining about the presence of nulls in cases where no
-       nulls are actually present (Tom Lane)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In
-       <link linkend="intarray"><filename>contrib/intarray</></link>,
-       fix behavior of containment operators with respect to empty arrays
-       (Tom Lane)
-      </para>
-
-      <para>
-       Empty arrays are now correctly considered to be contained in any other
-       array.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remove <link linkend="xml2"><filename>contrib/xml2</></link>'s
-       arbitrary limit on the number of
-       <replaceable>parameter</>=<replaceable>value</> pairs that can be
-       handled by <function>xslt_process()</> (Pavel Stehule)
-      </para>
-
-      <para>
-       The previous limit was 10.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In <link linkend="pageinspect"><filename>contrib/pageinspect</></link>,
-       fix heap_page_item to return infomasks as 32-bit values (Alvaro Herrera)
-      </para>
-
-      <para>
-       This avoids returning negative values, which was confusing.  The
-       underlying value is a 16-bit unsigned integer.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-    <sect4>
-     <title>Security</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-        Add <link linkend="sepgsql"><filename>contrib/sepgsql</></link>
-        to interface permission checks with <acronym>SE</>-Linux (KaiGai Kohei)
-       </para>
-
-       <para>
-        This uses the new <link
-        linkend="SQL-SECURITY-LABEL"><command>SECURITY LABEL</></link>
-        facility.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add contrib module <link
-        linkend="auth-delay"><filename>auth_delay</></link> (KaiGai
-        Kohei)
-       </para>
-
-       <para>
-        This causes the server to pause before returning authentication
-        failure;  it is designed to make brute force password attacks
-        more difficult.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <link linkend="dummy-seclabel">dummy_seclabel</link>
-        contrib module (KaiGai Kohei)
-       </para>
-
-       <para>
-        This is used for permission regression testing.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Performance</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-         Add support for <literal>LIKE</> and <literal>ILIKE</> index
-         searches to <link
-         linkend="pgtrgm"><filename>contrib/pg_trgm</></link> (Alexander
-         Korotkov)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add <function>levenshtein_less_equal()</> function to <link
-         linkend="fuzzystrmatch"><filename>contrib/fuzzystrmatch</></link>,
-         which is optimized for small distances (Alexander Korotkov)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Improve performance of index lookups on <link
-        linkend="seg"><filename>contrib/seg</></link> columns (Alexander
-        Korotkov)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Improve performance of <link
-         linkend="pgupgrade"><application>pg_upgrade</></link> for
-         databases with many relations (Bruce Momjian)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add flag to <link
-         linkend="pgbench"><filename>contrib/pgbench</></link> to
-         report per-statement latencies (Florian Pflug)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-    <sect4>
-     <title>Fsync Testing</title>
-
-     <itemizedlist>
-
-      <listitem>
-       <para>
-         Move <filename>src/tools/test_fsync</> to <link
-         linkend="pgtestfsync"><filename>contrib/pg_test_fsync</></link>
-         (Bruce Momjian, Tom Lane)
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Add <literal>O_DIRECT</> support to <link
-        linkend="pgtestfsync"><filename>contrib/pg_test_fsync</></link>
-        (Bruce Momjian)
-       </para>
-
-       <para>
-        This matches the use of <literal>O_DIRECT</> by <link
-        linkend="guc-wal-sync-method"><varname>wal_sync_method</></link>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-         Add new tests to <link
-         linkend="pgtestfsync"><filename>contrib/pg_test_fsync</></link>
-         (Bruce Momjian)
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-    </sect4>
-
-   </sect3>
-
-   <sect3>
-    <title>Documentation</title>
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-        Extensive <link linkend="ecpg"><application>ECPG</> documentation</link>
-        improvements (Satoshi Nagayasu)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-        Extensive proofreading and documentation improvements
-        (Thom Brown, Josh Kupershmidt, Susanne Ebrecht)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add documentation for <link
-       linkend="guc-exit-on-error"><varname>exit_on_error</></link>
-       (Robert Haas)
-      </para>
-
-      <para>
-       This parameter causes sessions to exit on any error.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add documentation for <link
-       linkend="functions-info-catalog-table"><function>pg_options_to_table()</></link>
-       (Josh Berkus)
-      </para>
-
-      <para>
-       This function shows table storage options in a readable form.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Document that it is possible to access all composite type
-       fields using <link
-       linkend="field-selection"><literal>(compositeval).*</></link>
-       syntax (Peter Eisentraut)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Document that <link
-       linkend="functions-string-other"><function>translate()</></link>
-       removes characters in <literal>from</> that don't have a
-       corresponding <literal>to</> character (Josh Kupershmidt)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Merge docs for <command>CREATE CONSTRAINT TRIGGER</> and <link
-       linkend="SQL-CREATETRIGGER"><command>CREATE TRIGGER</></link>
-       (Alvaro Herrera)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Centralize <link linkend="ddl-priv">permission</link> and <link
-       linkend="upgrading">upgrade</link> documentation (Bruce Momjian)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Add <link linkend="sysvipc-parameters">kernel tuning
-       documentation</link> for Solaris 10 (Josh Berkus)
-      </para>
-
-      <para>
-       Previously only Solaris 9 kernel tuning was documented.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-  </sect2>
- </sect1>
diff --git a/doc-xc/src/sgml/release-old.sgmlin b/doc-xc/src/sgml/release-old.sgmlin
deleted file mode 100644
index f03683ec3f..0000000000
--- a/doc-xc/src/sgml/release-old.sgmlin
+++ /dev/null
@@ -1,6657 +0,0 @@
-<!-- doc/src/sgml/release-old.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-7-3-21">
-  <title>Release 7.3.21</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2008-01-07</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.20,
-   including fixes for significant security issues.
-  </para>
-
-  <para>
-   This is expected to be the last <productname>PostgreSQL</> release
-   in the 7.3.X series.  Users are encouraged to update to a newer
-   release branch soon.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.21</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.13, see the release
-    notes for 7.3.13.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent functions in indexes from executing with the privileges of
-      the user running <command>VACUUM</>, <command>ANALYZE</>, etc (Tom)
-     </para>
-
-     <para>
-      Functions used in index expressions and partial-index
-      predicates are evaluated whenever a new table entry is made.  It has
-      long been understood that this poses a risk of trojan-horse code
-      execution if one modifies a table owned by an untrustworthy user.
-      (Note that triggers, defaults, check constraints, etc. pose the
-      same type of risk.)  But functions in indexes pose extra danger
-      because they will be executed by routine maintenance operations
-      such as <command>VACUUM FULL</>, which are commonly performed
-      automatically under a superuser account.  For example, a nefarious user
-      can execute code with superuser privileges by setting up a
-      trojan-horse index definition and waiting for the next routine vacuum.
-      The fix arranges for standard maintenance operations
-      (including <command>VACUUM</>, <command>ANALYZE</>, <command>REINDEX</>,
-      and <command>CLUSTER</>) to execute as the table owner rather than
-      the calling user, using the same privilege-switching mechanism already
-      used for <literal>SECURITY DEFINER</> functions.  To prevent bypassing
-      this security measure, execution of <command>SET SESSION
-      AUTHORIZATION</> and <command>SET ROLE</> is now forbidden within a
-      <literal>SECURITY DEFINER</> context.  (CVE-2007-6600)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require non-superusers who use <filename>/contrib/dblink</> to use only
-      password authentication, as a security measure (Joe)
-     </para>
-
-     <para>
-      The fix that appeared for this in 7.3.20 was incomplete, as it plugged
-      the hole for only some <filename>dblink</> functions.  (CVE-2007-6601,
-      CVE-2007-3278)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix potential crash in <function>translate()</> when using a multibyte
-      database encoding (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <filename>contrib/tablefunc</>'s <function>crosstab()</> handle
-      NULL rowid as a category in its own right, rather than crashing (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require a specific version of <productname>Autoconf</> to be used
-      when re-generating the <command>configure</> script (Peter)
-     </para>
-
-     <para>
-      This affects developers and packagers only.  The change was made
-      to prevent accidental use of untested combinations of
-      <productname>Autoconf</> and <productname>PostgreSQL</> versions.
-      You can remove the version check if you really want to use a
-      different <productname>Autoconf</> version, but it's
-      your responsibility whether the result works or not.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-20">
-  <title>Release 7.3.20</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-09-17</simpara>
-  </note>
-
-  <para>
-   This release contains fixes from 7.3.19.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.20</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.13, see the release
-    notes for 7.3.13.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Prevent index corruption when a transaction inserts rows and
-      then aborts close to the end of a concurrent <command>VACUUM</>
-      on the same table (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>CREATE DOMAIN ... DEFAULT NULL</> work properly (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix crash when <varname>log_min_error_statement</> logging runs out
-      of memory (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Require non-superusers who use <filename>/contrib/dblink</> to use only
-      password authentication, as a security measure (Joe)
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-19">
-  <title>Release 7.3.19</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-04-23</simpara>
-  </note>
-
-  <para>
-   This release contains fixes from 7.3.18,
-   including a security fix.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.19</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.13, see the release
-    notes for 7.3.13.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Support explicit placement of the temporary-table schema within
-     <varname>search_path</>, and disable searching it for functions
-     and operators (Tom)
-    </para>
-    <para>
-     This is needed to allow a security-definer function to set a
-     truly secure value of <varname>search_path</>.  Without it,
-     an unprivileged SQL user can use temporary objects to execute code
-     with the privileges of the security-definer function (CVE-2007-2138).
-     See <command>CREATE FUNCTION</> for more information.
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix potential-data-corruption bug in how <command>VACUUM FULL</> handles
-     <command>UPDATE</> chains (Tom, Pavan Deolasee)
-    </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-18">
-  <title>Release 7.3.18</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-02-05</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.17, including
-   a security fix.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.18</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.13, see the release
-    notes for 7.3.13.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-    <para>
-     Remove security vulnerability that allowed connected users
-     to read backend memory (Tom)
-    </para>
-    <para>
-     The vulnerability involves changing the
-     data type of a table column used in a SQL function (CVE-2007-0555).
-     This error can easily be exploited to cause a backend crash, and in
-     principle might be used to read database content that the user
-     should not be able to access.
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Fix rare bug wherein btree index page splits could fail
-     due to choosing an infeasible split point (Heikki Linnakangas)
-    </para>
-    </listitem>
-
-    <listitem>
-    <para>
-     Tighten security of multi-byte character processing for UTF8 sequences
-     over three bytes long (Tom)
-    </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-17">
-  <title>Release 7.3.17</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2007-01-08</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.16.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.17</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.13, see the release
-    notes for 7.3.13.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      <function>to_number()</> and <function>to_char(numeric)</>
-      are now <literal>STABLE</>, not <literal>IMMUTABLE</>, for
-      new <application>initdb</> installs (Tom)
-     </para>
-
-     <para>
-      This is because <varname>lc_numeric</> can potentially
-      change the output of these functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve index usage of regular expressions that use parentheses (Tom)
-     </para>
-
-     <para>
-      This improves <application>psql</> <literal>\d</> performance also.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-16">
-  <title>Release 7.3.16</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-10-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.15.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.16</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.13, see the release
-    notes for 7.3.13.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fix corner cases in pattern matching for
- <application>psql</>'s <literal>\d</> commands</para></listitem>
-<listitem><para>Fix index-corrupting bugs in /contrib/ltree
- (Teodor)</para></listitem>
-<listitem><para>Back-port 7.4 spinlock code to improve performance and support
-64-bit architectures better</para> </listitem>
-<listitem><para>Fix SSL-related memory leak in libpq</para> </listitem>
-<listitem><para>Fix backslash escaping in /contrib/dbmirror</para></listitem>
-<listitem><para>Adjust regression tests for recent changes in US DST laws
-</para> </listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-15">
-  <title>Release 7.3.15</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-05-23</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.14,
-   including patches for extremely serious security issues.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.15</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.13, see the release
-    notes for 7.3.13.
-   </para>
-
-   <para>
-    Full security against the SQL-injection attacks described in
-    CVE-2006-2313 and CVE-2006-2314 might require changes in application
-    code.  If you have applications that embed untrustworthy strings
-    into SQL commands, you should examine them as soon as possible to
-    ensure that they are using recommended escaping techniques.  In
-    most cases, applications should be using subroutines provided by
-    libraries or drivers (such as <application>libpq</>'s
-    <function>PQescapeStringConn()</>) to perform string escaping,
-    rather than relying on <foreignphrase>ad hoc</> code to do it.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Change the server to reject invalidly-encoded multibyte
-characters in all cases (Tatsuo, Tom)</para>
-<para>While <productname>PostgreSQL</> has been moving in this direction for
-some time, the checks are now applied uniformly to all encodings and all
-textual input, and are now always errors not merely warnings.  This change
-defends against SQL-injection attacks of the type described in CVE-2006-2313.
-</para></listitem>
-
-<listitem><para>Reject unsafe uses of <literal>\'</> in string literals</para>
-<para>As a server-side defense against SQL-injection attacks of the type
-described in CVE-2006-2314, the server now only accepts <literal>''</> and not
-<literal>\'</> as a representation of ASCII single quote in SQL string
-literals.  By default, <literal>\'</> is rejected only when
-<varname>client_encoding</> is set to a client-only encoding (SJIS, BIG5, GBK,
-GB18030, or UHC), which is the scenario in which SQL injection is possible.
-A new configuration parameter <varname>backslash_quote</> is available to
-adjust this behavior when needed.  Note that full security against
-CVE-2006-2314 might require client-side changes; the purpose of
-<varname>backslash_quote</> is in part to make it obvious that insecure
-clients are insecure.
-</para></listitem>
-
-<listitem><para>Modify <application>libpq</>'s string-escaping routines to be
-aware of encoding considerations</para>
-<para>This fixes <application>libpq</>-using applications for the security
-issues described in CVE-2006-2313 and CVE-2006-2314.
-Applications that use multiple <productname>PostgreSQL</> connections
-concurrently should migrate to <function>PQescapeStringConn()</> and
-<function>PQescapeByteaConn()</> to ensure that escaping is done correctly
-for the settings in use in each database connection.  Applications that
-do string escaping <quote>by hand</> should be modified to rely on library
-routines instead.
-</para></listitem>
-
-<listitem><para>Fix some incorrect encoding conversion functions</para>
-<para><function>win1251_to_iso</>, <function>alt_to_iso</>,
-<function>euc_tw_to_big5</>, <function>euc_tw_to_mic</>,
-<function>mic_to_euc_tw</> were all broken to varying
-extents.
-</para></listitem>
-
-<listitem><para>Clean up stray remaining uses of <literal>\'</> in strings
-(Bruce, Jan)</para></listitem>
-
-<listitem><para>Fix server to use custom DH SSL parameters correctly (Michael
-Fuhr)</para></listitem>
-
-<listitem><para>Fix various minor memory leaks</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-14">
-  <title>Release 7.3.14</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-02-14</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.13.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.14</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.13, see the release
-    notes for 7.3.13.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix potential crash in <command>SET
-SESSION AUTHORIZATION</> (CVE-2006-0553)</para>
-<para>An unprivileged user could crash the server process, resulting in
-momentary denial of service to other users, if the server has been compiled
-with Asserts enabled (which is not the default).
-Thanks to Akio Ishida for reporting this problem.
-</para></listitem>
-
-<listitem><para>Fix bug with row visibility logic in self-inserted
-rows (Tom)</para>
-<para>Under rare circumstances a row inserted by the current command
-could be seen as already valid, when it should not be.  Repairs bug
-created in 7.3.11 release.
-</para></listitem>
-
-<listitem><para>Fix race condition that could lead to <quote>file already
-exists</> errors during pg_clog file creation
-(Tom)</para></listitem>
-
-<listitem><para>Fix to allow restoring dumps that have cross-schema
-references to custom operators (Tom)</para></listitem>
-
-<listitem><para>Portability fix for testing presence of <function>finite</>
-and <function>isinf</> during configure (Tom)</para></listitem>
-
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-13">
-  <title>Release 7.3.13</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2006-01-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.12.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.13</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.10, see the release
-    notes for 7.3.10.
-    Also, you might need to <command>REINDEX</> indexes on textual
-    columns after updating, if you are affected by the locale or
-    <application>plperl</> issues described below.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix character string comparison for locales that consider
-different character combinations as equal, such as Hungarian (Tom)</para>
-<para>This might require <command>REINDEX</> to fix existing indexes on
-textual columns.</para></listitem>
-
-<listitem><para>Set locale environment variables during postmaster startup
-to ensure that <application>plperl</> won't change the locale later</para>
-<para>This fixes a problem that occurred if the <application>postmaster</> was
-started with environment variables specifying a different locale than what
-<application>initdb</> had been told.  Under these conditions, any use of
-<application>plperl</> was likely to lead to corrupt indexes.  You might need
-<command>REINDEX</> to fix existing indexes on
-textual columns if this has happened to you.</para></listitem>
-
-<listitem><para>Fix longstanding bug in strpos() and regular expression
-handling in certain rarely used Asian multi-byte character sets (Tatsuo)
-</para></listitem>
-
-<listitem><para>Fix bug in <filename>/contrib/pgcrypto</> gen_salt,
-which caused it not to use all available salt space for MD5 and
-XDES algorithms (Marko Kreen, Solar Designer)</para>
-<para>Salts for Blowfish and standard DES are unaffected.</para></listitem>
-
-<listitem><para>Fix <filename>/contrib/dblink</> to throw an error,
-rather than crashing, when the number of columns specified is different from
-what's actually returned by the query (Joe)</para></listitem>
-
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-12">
-  <title>Release 7.3.12</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-12-12</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.11.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.12</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.10, see the release
-    notes for 7.3.10.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-
-<listitem><para>Fix race condition in transaction log management</para>
-<para>There was a narrow window in which an I/O operation could be initiated
-for the wrong page, leading to an Assert failure or data
-corruption.</para>
-</listitem>
-
-<listitem><para><filename>/contrib/ltree</> fixes (Teodor)</para></listitem>
-
-<listitem><para>Fix longstanding planning error for outer joins</para>
-<para>This bug sometimes caused a bogus error <quote>RIGHT JOIN is
-only supported with merge-joinable join conditions</>.</para></listitem>
-
-<listitem><para>Prevent core dump in <application>pg_autovacuum</> when a
-table has been dropped</para></listitem>
-
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-11">
-  <title>Release 7.3.11</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-10-04</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.10.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.11</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    if you are upgrading from a version earlier than 7.3.10, see the release
-    notes for 7.3.10.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fix error that allowed <command>VACUUM</> to remove
-<literal>ctid</> chains too soon, and add more checking in code that follows
-<literal>ctid</> links</para>
-<para>This fixes a long-standing problem that could cause crashes in very rare
-circumstances.</para></listitem>
-<listitem><para>Fix <type>CHAR()</> to properly pad spaces to the specified
-length when using a multiple-byte character set (Yoshiyuki Asaba)</para>
-<para>In prior releases, the padding of <type>CHAR()</> was incorrect
-because it only padded to the specified number of bytes without
-considering how many characters were stored.</para></listitem>
-<listitem><para>Fix missing rows in queries like <literal>UPDATE a=... WHERE
-a...</> with GiST index on column <literal>a</></para></listitem>
-<listitem><para>Improve checking for partially-written WAL
-pages</para></listitem>
-<listitem><para>Improve robustness of signal handling when SSL is
-enabled</para></listitem>
-<listitem><para>Various memory leakage fixes</para></listitem>
-<listitem><para>Various portability improvements</para></listitem>
-<listitem><para>Fix PL/pgSQL to handle <literal>var := var</> correctly when
-the variable is of pass-by-reference type</para></listitem>
-</itemizedlist>
-
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-3-10">
-  <title>Release 7.3.10</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-05-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.9, including several
-   security-related issues.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.10</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.  However,
-    it is one possible way of handling a significant security problem
-    that has been found in the initial contents of 7.3.X system
-    catalogs.  A dump/initdb/reload sequence using 7.3.10's initdb will
-    automatically correct this problem.
-   </para>
-
-   <para>
-    The security problem is that the built-in character set encoding
-    conversion functions can be invoked from SQL commands by unprivileged
-    users, but the functions were not designed for such use and are not
-    secure against malicious choices of arguments.  The fix involves changing
-    the declared parameter list of these functions so that they can no longer
-    be invoked from SQL commands.  (This does not affect their normal use
-    by the encoding conversion machinery.)
-    It is strongly recommended that all installations repair this error,
-    either by initdb or by following the manual repair procedure given
-    below.  The error at least allows unprivileged database users to crash
-    their server process, and might allow unprivileged users to gain the
-    privileges of a database superuser.
-   </para>
-
-   <para>
-    If you wish not to do an initdb, perform the following procedure instead.
-    As the database superuser, do:
-
-<programlisting>
-BEGIN;
-UPDATE pg_proc SET proargtypes[3] = 'internal'::regtype
-WHERE pronamespace = 11 AND pronargs = 5
-     AND proargtypes[2] = 'cstring'::regtype;
--- The command should report having updated 90 rows;
--- if not, rollback and investigate instead of committing!
-COMMIT;
-</programlisting>
-   </para>
-
-   <para>
-    The above procedure must be carried out in <emphasis>each</> database
-    of an installation, including <literal>template1</>, and ideally
-    including <literal>template0</> as well.  If you do not fix the
-    template databases then any subsequently created databases will contain
-    the same error.  <literal>template1</> can be fixed in the same way
-    as any other database, but fixing <literal>template0</> requires
-    additional steps.  First, from any database issue:
-<programlisting>
-UPDATE pg_database SET datallowconn = true WHERE datname = 'template0';
-</programlisting>
-     Next connect to <literal>template0</> and perform the above repair
-     procedure.  Finally, do:
-<programlisting>
--- re-freeze template0:
-VACUUM FREEZE;
--- and protect it against future alterations:
-UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Change encoding function signature to prevent
-misuse</para></listitem>
-<listitem><para>Repair ancient race condition that allowed a transaction to be
-seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner
-than for other purposes</para>
-<para>This is an extremely serious bug since it could lead to apparent
-data inconsistencies being briefly visible to applications.</para></listitem>
-<listitem><para>Repair race condition between relation extension and
-VACUUM</para>
-<para>This could theoretically have caused loss of a page's worth of
-freshly-inserted data, although the scenario seems of very low probability.
-There are no known cases of it having caused more than an Assert failure.
-</para></listitem>
-<listitem><para>Fix comparisons of <type>TIME WITH TIME ZONE</> values</para>
-<para>
-The comparison code was wrong in the case where the
-<literal>--enable-integer-datetimes</> configuration switch had been used.
-NOTE: if you have an index on a <type>TIME WITH TIME ZONE</> column,
-it will need to be <command>REINDEX</>ed after installing this update, because
-the fix corrects the sort order of column values.
-</para></listitem>
-<listitem><para>Fix <function>EXTRACT(EPOCH)</> for
-<type>TIME WITH TIME ZONE</> values</para></listitem>
-<listitem><para>Fix mis-display of negative fractional seconds in
-<type>INTERVAL</> values</para>
-<para>
-This error only occurred when the
-<literal>--enable-integer-datetimes</> configuration switch had been used.
-</para></listitem>
-<listitem><para>Additional buffer overrun checks in plpgsql
-(Neil)</para></listitem>
-<listitem><para>Fix pg_dump to dump trigger names containing <literal>%</>
-correctly (Neil)</para></listitem>
-<listitem><para>Prevent <function>to_char(interval)</> from dumping core for
-month-related formats</para></listitem>
-<listitem><para>Fix <filename>contrib/pgcrypto</> for newer OpenSSL builds
-(Marko Kreen)</para></listitem>
-<listitem><para>Still more 64-bit fixes for
-<filename>contrib/intagg</></para></listitem>
-<listitem><para>Prevent incorrect optimization of functions returning
-<type>RECORD</></para></listitem>
-</itemizedlist>
-
- </sect2>
-</sect1>
-
- <sect1 id="release-7-3-9">
-  <title>Release 7.3.9</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-01-31</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.8, including several
-   security-related issues.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.3.9</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Disallow <command>LOAD</> to non-superusers</para>
-<para>
-On platforms that will automatically execute initialization functions of a
-shared library (this includes at least Windows and ELF-based Unixen),
-<command>LOAD</> can be used to make the server execute arbitrary code.
-Thanks to NGS Software for reporting this.</para></listitem>
-<listitem><para>Check that creator of an aggregate function has the right to
-execute the specified transition functions</para>
-<para>
-This oversight made it possible to bypass denial of EXECUTE
-permission on a function.</para></listitem>
-<listitem><para>Fix security and 64-bit issues in
-contrib/intagg</para></listitem>
-<listitem><para>Add needed STRICT marking to some contrib functions (Kris
-Jurka)</para></listitem>
-<listitem><para>Avoid buffer overrun when plpgsql cursor declaration has too
-many parameters (Neil)</para></listitem>
-<listitem><para>Fix planning error for FULL and RIGHT outer joins</para>
-<para>
-The result of the join was mistakenly supposed to be sorted the same as the
-left input.  This could not only deliver mis-sorted output to the user, but
-in case of nested merge joins could give outright wrong answers.
-</para></listitem>
-<listitem><para>Fix plperl for quote marks in tuple fields</para></listitem>
-<listitem><para>Fix display of negative intervals in SQL and GERMAN
-datestyles</para></listitem>
-</itemizedlist>
-
- </sect2>
-</sect1>
-
- <sect1 id="release-7-3-8">
-  <title>Release 7.3.8</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2004-10-22</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.7.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.3.8</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Repair possible failure to update hint bits on disk</para>
-<para>
-Under rare circumstances this oversight could lead to
-<quote>could not access transaction status</> failures, which qualifies
-it as a potential-data-loss bug.
-</para></listitem>
-<listitem><para>Ensure that hashed outer join does not miss tuples</para>
-<para>
-Very large left joins using a hash join plan could fail to output unmatched
-left-side rows given just the right data distribution.
-</para></listitem>
-<listitem><para>Disallow running pg_ctl as root</para>
-<para>
-This is to guard against any possible security issues.
-</para></listitem>
-<listitem><para>Avoid using temp files in /tmp in make_oidjoins_check</para>
-<para>
-This has been reported as a security issue, though it's hardly worthy of
-concern since there is no reason for non-developers to use this script anyway.
-</para></listitem>
-</itemizedlist>
-
- </sect2>
-</sect1>
-
- <sect1 id="release-7-3-7">
-  <title>Release 7.3.7</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2004-08-16</simpara>
-  </note>
-
-  <para>
-   This release contains one critical fix over 7.3.6, and some minor items.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.3.7</title>
-
-   <para>
-    A dump/restore is not required for those running 7.3.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Prevent possible loss of committed transactions during crash</para>
-<para>
-Due to insufficient interlocking between transaction commit and checkpointing,
-it was possible for transactions committed just before the most recent
-checkpoint to be lost, in whole or in part, following a database crash and
-restart.  This is a serious bug that has existed
-since <productname>PostgreSQL</productname> 7.1.
-</para></listitem>
-<listitem><para>Remove asymmetrical word processing in tsearch (Teodor)</para></listitem>
-<listitem><para>Properly schema-qualify function names when pg_dump'ing a CAST</para></listitem>
-</itemizedlist>
-
- </sect2>
-</sect1>
-
- <sect1 id="release-7-3-6">
-  <title>Release 7.3.6</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2004-03-02</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.3.5.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.3.6</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running 7.3.*.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Revert erroneous changes in rule permissions checking</para>
-<para>A patch applied in 7.3.3 to fix a corner case in rule permissions checks
-turns out to have disabled rule-related permissions checks in many
-not-so-corner cases.  This would for example allow users to insert into views
-they weren't supposed to have permission to insert into.  We have therefore
-reverted the 7.3.3 patch.  The original bug will be fixed in 8.0.
-</para></listitem>
-<listitem><para>Repair incorrect order of operations in
-GetNewTransactionId()</para>
-<para>
-This bug could result in failure under out-of-disk-space conditions, including
-inability to restart even after disk space is freed.
-</para></listitem>
-<listitem><para>Ensure configure selects -fno-strict-aliasing even when
-an external value for CFLAGS is supplied</para>
-<para>
-On some platforms, building with -fstrict-aliasing causes bugs.
-</para></listitem>
-<listitem><para>Make pg_restore handle 64-bit off_t correctly</para>
-<para>
-This bug prevented proper restoration from archive files exceeding 4 GB.
-</para></listitem>
-<listitem><para>Make contrib/dblink not assume that local and remote type OIDs
-match (Joe)</para></listitem>
-<listitem><para>Quote connectby()'s start_with argument properly (Joe)</para></listitem>
-<listitem><para>Don't crash when a rowtype argument to a plpgsql function is
-NULL</para></listitem>
-<listitem><para>Avoid generating invalid character encoding sequences in
-corner cases when planning LIKE operations</para></listitem>
-<listitem><para>Ensure text_position() cannot scan past end of source string
-in multibyte cases (Korea PostgreSQL Users' Group)</para></listitem>
-<listitem><para>Fix index optimization and selectivity estimates for LIKE
-operations on bytea columns (Joe)</para></listitem>
-</itemizedlist>
-
- </sect2>
-</sect1>
-
- <sect1 id="release-7-3-5">
-  <title>Release 7.3.5</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2003-12-03</simpara>
-  </note>
-
-  <para>
-   This has a variety of fixes from 7.3.4.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.3.5</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running 7.3.*.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Force zero_damaged_pages to be on during recovery from WAL</para></listitem>
-<listitem><para>Prevent some obscure cases of <quote>variable not in subplan target lists</quote></para></listitem>
-<listitem><para>Force stats processes to detach from shared memory, ensuring cleaner shutdown</para></listitem>
-<listitem><para>Make PQescapeBytea and byteaout consistent with each other (Joe)</para></listitem>
-<listitem><para>Added missing SPI_finish() calls to dblink's get_tuple_of_interest() (Joe)</para></listitem>
-<listitem><para>Fix for possible foreign key violation when rule rewrites INSERT (Jan)</para></listitem>
-<listitem><para>Support qualified type names in PL/Tcl's spi_prepare command (Jan)</para></listitem>
-<listitem><para>Make pg_dump handle a procedural language handler located in pg_catalog</para></listitem>
-<listitem><para>Make pg_dump handle cases where a custom opclass is in another schema</para></listitem>
-<listitem><para>Make pg_dump dump binary-compatible casts correctly (Jan)</para></listitem>
-<listitem><para>Fix insertion of expressions containing subqueries into rule bodies</para></listitem>
-<listitem><para>Fix incorrect argument processing in clusterdb script (Anand Ranganathan)</para></listitem>
-<listitem><para>Fix problems with dropped columns in plpython triggers</para></listitem>
-<listitem><para>Repair problems with to_char() reading past end of its input string (Karel)</para></listitem>
-<listitem><para>Fix GB18030 mapping errors (Tatsuo)</para></listitem>
-<listitem><para>Fix several problems with SSL error handling and asynchronous SSL I/O</para></listitem>
-<listitem><para>Remove ability to bind a list of values to a single parameter in JDBC
-(prevents possible SQL-injection attacks)</para></listitem>
-<listitem><para>Fix some errors in HAVE_INT64_TIMESTAMP code paths</para></listitem>
-<listitem><para>Fix corner case for btree search in parallel with first root page split</para></listitem>
-</itemizedlist>
-
- </sect2>
-</sect1>
-
- <sect1 id="release-7-3-4">
-  <title>Release 7.3.4</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2003-07-24</simpara>
-  </note>
-
-  <para>
-   This has a variety of fixes from 7.3.3.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.3.4</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running 7.3.*.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Repair breakage in timestamp-to-date conversion for dates before 2000</para></listitem>
-<listitem><para>Prevent rare possibility of server startup failure (Tom)</para></listitem>
-<listitem><para>Fix bugs in interval-to-time conversion (Tom)</para></listitem>
-<listitem><para>Add constraint names in a few places in pg_dump (Rod)</para></listitem>
-<listitem><para>Improve performance of functions with many parameters (Tom)</para></listitem>
-<listitem><para>Fix to_ascii() buffer overruns (Tom)</para></listitem>
-<listitem><para>Prevent restore of database comments from throwing an error (Tom)</para></listitem>
-<listitem><para>Work around buggy strxfrm() present in some Solaris releases (Tom)</para></listitem>
-<listitem><para>Properly escape jdbc setObject() strings to improve security (Barry)</para></listitem>
-</itemizedlist>
-  </sect2>
- </sect1>
-
-
-<sect1 id="release-7-3-3">
- <title>Release 7.3.3</title>
-
- <note>
-  <title>Release Date</title>
-  <simpara>2003-05-22</simpara>
- </note>
-
- <para>
-  This release contains a variety of fixes for version 7.3.2.
- </para>
-
- <sect2>
-  <title>Migration to Version 7.3.3</title>
-
-  <para>
-   A dump/restore is <emphasis>not</emphasis> required for those
-   running version 7.3.*.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Repair sometimes-incorrect computation of StartUpID after a crash</para></listitem>
-<listitem><para>Avoid slowness with lots of deferred triggers in one transaction (Stephan)</para></listitem>
-<listitem><para>Don't lock referenced row when <command>UPDATE</command> doesn't change foreign key's value (Jan)</para></listitem>
-<listitem><para>Use <command>-fPIC</command> not <command>-fpic</command> on Sparc (Tom Callaway)</para></listitem>
-<listitem><para>Repair lack of schema-awareness in contrib/reindexdb</para></listitem>
-<listitem><para>Fix contrib/intarray error for zero-element result array (Teodor)</para></listitem>
-<listitem><para>Ensure createuser script will exit on control-C (Oliver)</para></listitem>
-<listitem><para>Fix errors when the type of a dropped column has itself been dropped</para></listitem>
-<listitem><para><command>CHECKPOINT</command> does not cause database panic on failure in noncritical steps</para></listitem>
-<listitem><para>Accept 60 in seconds fields of timestamp, time, interval input values</para></listitem>
-<listitem><para>Issue notice, not error, if <type>TIMESTAMP</type>,
-<type> TIME</type>, or <type>INTERVAL</type> precision too large</para></listitem>
-<listitem><para>Fix <function>abstime-to-time</function> cast function (fix is
-      not applied unless you <application>initdb</application>)</para></listitem>
-<listitem><para>Fix <application>pg_proc</application> entry for
-     <type>timestampt_izone</type> (fix is not applied unless you
-       <application>initdb</application>)</para></listitem>
-<listitem><para>Make <function>EXTRACT(EPOCH FROM timestamp without time zone)</function> treat input as local time</para></listitem>
-<listitem><para><command>'now'::timestamptz</command> gave wrong answer if timezone changed earlier in transaction</para></listitem>
-<listitem><para><envar>HAVE_INT64_TIMESTAMP</envar> code for time with timezone overwrote its input</para></listitem>
-<listitem><para>Accept <command>GLOBAL TEMP/TEMPORARY</command> as a
-      synonym for <command>TEMPORARY</command></para></listitem>
-<listitem><para>Avoid improper schema-privilege-check failure in foreign-key triggers</para></listitem>
-<listitem><para>Fix bugs in foreign-key triggers for <command>SET DEFAULT</command> action</para></listitem>
-<listitem><para>Fix incorrect time-qual check in row fetch for
-      <command>UPDATE</command> and <command>DELETE</command> triggers</para></listitem>
-<listitem><para>Foreign-key clauses were parsed but ignored in
-      <command>ALTER TABLE ADD COLUMN</command></para></listitem>
-<listitem><para>Fix createlang script breakage for case where handler function already exists</para></listitem>
-<listitem><para>Fix misbehavior on zero-column tables in <application>pg_dump</application>, COPY, ANALYZE, other places</para></listitem>
-<listitem><para>Fix misbehavior of <function>func_error()</function> on type names containing '%'</para></listitem>
-<listitem><para>Fix misbehavior of <function>replace()</function> on strings containing '%'</para></listitem>
-<listitem><para>Regular-expression patterns containing certain multibyte characters failed</para></listitem>
-<listitem><para>Account correctly for <command>NULL</command>s in more cases in join size estimation</para></listitem>
-<listitem><para>Avoid conflict with system definition of <function>isblank()</function> function or macro</para></listitem>
-<listitem><para>Fix failure to convert large code point values in EUC_TW conversions (Tatsuo)</para></listitem>
-<listitem><para>Fix error recovery for <function>SSL_read</function>/<function>SSL_write</function> calls</para></listitem>
-<listitem><para>Don't do early constant-folding of type coercion expressions</para></listitem>
-<listitem><para>Validate page header fields immediately after reading in any page</para></listitem>
-<listitem><para>Repair incorrect check for ungrouped variables in unnamed joins</para></listitem>
-<listitem><para>Fix buffer overrun in <function>to_ascii</function> (Guido Notari)</para></listitem>
-<listitem><para>contrib/ltree fixes (Teodor)</para></listitem>
-<listitem><para>Fix core dump in deadlock detection on machines where char is unsigned</para></listitem>
-<listitem><para>Avoid running out of buffers in many-way indexscan (bug introduced in 7.3)</para></listitem>
-<listitem><para>Fix planner's selectivity estimation functions to handle domains properly</para></listitem>
-<listitem><para>Fix <application>dbmirror</application> memory-allocation bug (Steven Singer)</para></listitem>
-<listitem><para>Prevent infinite loop in <function>ln(numeric)</function> due to roundoff error</para></listitem>
-<listitem><para><command>GROUP BY</command> got confused if there were multiple equal GROUP BY items</para></listitem>
-<listitem><para>Fix bad plan when inherited <command>UPDATE</command>/<command>DELETE</command> references another inherited table</para></listitem>
-<listitem><para>Prevent clustering on incomplete (partial or non-NULL-storing) indexes</para></listitem>
-<listitem><para>Service shutdown request at proper time if it arrives while still starting up</para></listitem>
-<listitem><para>Fix left-links in temporary indexes (could make backwards scans miss entries)</para></listitem>
-<listitem><para>Fix incorrect handling of client_encoding setting in postgresql.conf (Tatsuo)</para></listitem>
-<listitem><para>Fix failure to respond to <command>pg_ctl stop -m fast</command> after Async_NotifyHandler runs</para></listitem>
-<listitem><para>Fix SPI for case where rule contains multiple statements of the same type</para></listitem>
-<listitem><para>Fix problem with checking for wrong type of access privilege in rule query</para></listitem>
-<listitem><para>Fix problem with <command>EXCEPT</command> in <command>CREATE RULE</command></para></listitem>
-<listitem><para>Prevent problem with dropping temp tables having serial columns</para></listitem>
-<listitem><para>Fix replace_vars_with_subplan_refs failure in complex views</para></listitem>
-<listitem><para>Fix regexp slowness in single-byte encodings (Tatsuo)</para></listitem>
-<listitem><para>Allow qualified type names in <command>CREATE CAST</command>
-      and <command> DROP CAST</command></para></listitem>
-<listitem><para>Accept <function>SETOF type[]</function>, which formerly had to
-      be written <function>SETOF _type</function></para></listitem>
-<listitem><para>Fix <application>pg_dump</application> core dump in some cases with procedural languages</para></listitem>
-<listitem><para>Force ISO datestyle in <application>pg_dump</application> output, for portability (Oliver)</para></listitem>
-<listitem><para><application>pg_dump</application> failed to handle error return
-      from <function>lo_read</function> (Oleg Drokin)</para></listitem>
-<listitem><para><application>pg_dumpall</application> failed with groups having no members (Nick Eskelinen)</para></listitem>
-<listitem><para><application>pg_dumpall</application> failed to recognize --globals-only switch</para></listitem>
-<listitem><para>pg_restore failed to restore blobs if -X disable-triggers is specified</para></listitem>
-<listitem><para>Repair intrafunction memory leak in plpgsql</para></listitem>
-<listitem><para>pltcl's <command>elog</command> command dumped core if given wrong parameters (Ian Harding)</para></listitem>
-<listitem><para>plpython used wrong value of <envar>atttypmod</envar> (Brad McLean)</para></listitem>
-<listitem><para>Fix improper quoting of boolean values in Python interface (D'Arcy)</para></listitem>
-<listitem><para>Added <function>addDataType()</function> method to PGConnection interface for JDBC</para></listitem>
-<listitem><para>Fixed various problems with updateable ResultSets for JDBC (Shawn Green)</para></listitem>
-<listitem><para>Fixed various problems with DatabaseMetaData for JDBC (Kris Jurka, Peter Royal)</para></listitem>
-<listitem><para>Fixed problem with parsing table ACLs in JDBC</para></listitem>
-<listitem><para>Better error message for character set conversion problems in JDBC</para></listitem>
-</itemizedlist>
- </sect2>
-</sect1>
-
-
-<sect1 id="release-7-3-2">
- <title>Release 7.3.2</title>
-
- <note>
-  <title>Release Date</title>
-  <simpara>2003-02-04</simpara>
- </note>
-
- <para>
-  This release contains a variety of fixes for version 7.3.1.
- </para>
-
-
- <sect2>
-  <title>Migration to Version 7.3.2</title>
-
-  <para>
-   A dump/restore is <emphasis>not</emphasis> required for those
-   running version 7.3.*.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Restore creation of OID column in CREATE TABLE AS / SELECT INTO</para></listitem>
-<listitem><para>Fix <application>pg_dump</> core dump when dumping views having comments</para></listitem>
-<listitem><para>Dump DEFERRABLE/INITIALLY DEFERRED constraints properly</para></listitem>
-<listitem><para>Fix UPDATE when child table's column numbering differs from parent</para></listitem>
-<listitem><para>Increase default value of max_fsm_relations</para></listitem>
-<listitem><para>Fix problem when fetching backwards in a cursor for a single-row query</para></listitem>
-<listitem><para>Make backward fetch work properly with cursor on SELECT DISTINCT query</para></listitem>
-<listitem><para>Fix problems with loading <application>pg_dump</> files containing contrib/lo usage</para></listitem>
-<listitem><para>Fix problem with all-numeric user names</para></listitem>
-<listitem><para>Fix possible memory leak and core dump during disconnect in libpgtcl</para></listitem>
-<listitem><para>Make plpython's spi_execute command handle nulls properly (Andrew Bosma)</para></listitem>
-<listitem><para>Adjust plpython error reporting so that its regression test passes again</para></listitem>
-<listitem><para>Work with bison 1.875</para></listitem>
-<listitem><para>Handle mixed-case names properly in plpgsql's %type (Neil)</para></listitem>
-<listitem><para>Fix core dump in pltcl when executing a query rewritten by a rule</para></listitem>
-<listitem><para>Repair array subscript overruns (per report from Yichen Xie)</para></listitem>
-<listitem><para>Reduce MAX_TIME_PRECISION from 13 to 10 in floating-point case</para></listitem>
-<listitem><para>Correctly case-fold variable names in per-database and per-user settings</para></listitem>
-<listitem><para>Fix coredump in plpgsql's RETURN NEXT when SELECT into record returns no rows</para></listitem>
-<listitem><para>Fix outdated use of pg_type.typprtlen in python client interface</para></listitem>
-<listitem><para>Correctly handle fractional seconds in timestamps in JDBC driver</para></listitem>
-<listitem><para>Improve performance of getImportedKeys() in JDBC</para></listitem>
-<listitem><para>Make shared-library symlinks work standardly on HPUX (Giles)</para></listitem>
-<listitem><para>Repair inconsistent rounding behavior for timestamp, time, interval</para></listitem>
-<listitem><para>SSL negotiation fixes (Nathan Mueller)</para></listitem>
-<listitem><para>Make libpq's ~/.pgpass feature work when connecting with PQconnectDB</para></listitem>
-<listitem><para>Update my2pg, ora2pg</para></listitem>
-<listitem><para>Translation updates</para></listitem>
-<listitem><para>Add casts between types lo and oid in contrib/lo</para></listitem>
-<listitem><para>fastpath code now checks for privilege to call function</para></listitem>
-</itemizedlist>
- </sect2>
-</sect1>
-
-
-<sect1 id="release-7-3-1">
- <title>Release 7.3.1</title>
-
- <note>
-  <title>Release Date</title>
-  <simpara>2002-12-18</simpara>
- </note>
-
- <para>
-  This release contains a variety of fixes for version 7.3.
- </para>
-
-
- <sect2>
-  <title>Migration to Version 7.3.1</title>
-
-  <para>
-   A dump/restore is <emphasis>not</emphasis> required for those
-   running version 7.3. However, it should be noted that the main
-   <productname>PostgreSQL</productname> interface library, libpq,
-   has a new major version number for this release, which might require
-   recompilation of client code in certain cases.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fix a core dump of COPY TO when client/server encodings don't match (Tom)</para></listitem>
-<listitem><para>Allow <application>pg_dump</> to work with pre-7.2 servers (Philip)</para></listitem>
-<listitem><para>contrib/adddepend fixes (Tom)</para></listitem>
-<listitem><para>Fix problem with deletion of per-user/per-database config settings (Tom)</para></listitem>
-<listitem><para>contrib/vacuumlo fix (Tom)</para></listitem>
-<listitem><para>Allow 'password' encryption even when pg_shadow contains MD5 passwords (Bruce)</para></listitem>
-<listitem><para>contrib/dbmirror fix (Steven Singer)</para></listitem>
-<listitem><para>Optimizer fixes (Tom)</para></listitem>
-<listitem><para>contrib/tsearch fixes (Teodor Sigaev, Magnus)</para></listitem>
-<listitem><para>Allow locale names to be mixed case (Nicolai Tufar)</para></listitem>
-<listitem><para>Increment libpq library's major version number (Bruce)</para></listitem>
-<listitem><para>pg_hba.conf error reporting fixes (Bruce, Neil)</para></listitem>
-<listitem><para>Add SCO Openserver 5.0.4 as a supported platform (Bruce)</para></listitem>
-<listitem><para>Prevent EXPLAIN from crashing server (Tom)</para></listitem>
-<listitem><para>SSL fixes (Nathan Mueller)</para></listitem>
-<listitem><para>Prevent composite column creation via ALTER TABLE (Tom)</para></listitem>
-</itemizedlist>
- </sect2>
-</sect1>
-
-
-<sect1 id="release-7-3">
- <title>Release 7.3</title>
-
- <note>
-  <title>Release Date</title>
-  <simpara>2002-11-27</simpara>
- </note>
-
- <sect2>
-  <title>Overview</title>
-
-  <para>
-   Major changes in this release:
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term>Schemas</term>
-    <listitem>
-     <para>
-      Schemas allow users to create objects in separate namespaces,
-      so two people or applications can have tables with the same
-      name. There is also a public schema for shared tables.
-      Table/index creation can be restricted by removing privileges
-      on the public schema.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Drop Column</term>
-    <listitem>
-     <para>
-      <productname>PostgreSQL</productname> now supports the
-      <literal>ALTER TABLE ... DROP COLUMN</literal> functionality.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Table Functions</term>
-    <listitem>
-     <para>
-      Functions returning multiple rows and/or multiple columns are
-      now much easier to use than before.  You can call such a
-      <quote>table function</quote> in the <literal>SELECT</literal>
-      <literal>FROM</literal> clause, treating its output like a
-      table. Also, <application>PL/pgSQL</application> functions can
-      now return sets.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Prepared Queries</term>
-    <listitem>
-     <para>
-      <productname>PostgreSQL</productname> now supports prepared
-      queries, for improved performance.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Dependency Tracking</term>
-    <listitem>
-     <para>
-      <productname>PostgreSQL</productname> now records object
-      dependencies, which allows improvements in many areas.
-      <command>DROP</command> statements now take either
-      <literal>CASCADE</> or <literal>RESTRICT</> to control whether
-      dependent objects are also dropped.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Privileges</term>
-    <listitem>
-     <para>
-      Functions and procedural languages now have privileges, and
-      functions can be defined to run with the privileges of their
-      creator.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Internationalization</term>
-    <listitem>
-     <para>
-      Both multibyte and locale support are now always enabled.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Logging</term>
-    <listitem>
-     <para>
-      A variety of logging options have been enhanced.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Interfaces</term>
-    <listitem>
-     <para>
-      A large number of interfaces have been moved to <ulink
-      url="http://gborg.postgresql.org">http://gborg.postgresql.org</>
-      where they can be developed and released independently.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Functions/Identifiers</term>
-    <listitem>
-     <para>
-      By default, functions can now take up to 32 parameters, and
-      identifiers can be up to 63 bytes long.  Also, <literal>OPAQUE</>
-      is now deprecated: there are specific <quote>pseudo-datatypes</>
-      to represent each of the former meanings of <literal>OPAQUE</>
-      in function argument and result types.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </sect2>
-
- <sect2>
-  <title>Migration to Version 7.3</title>
-
-  <para>
-   A dump/restore using <application>pg_dump</> is required for those
-   wishing to migrate data from any previous release. If your
-   application examines the system catalogs, additional changes will
-   be required due to the introduction of schemas in 7.3; for more
-   information, see: <ulink
-   url="http://developer.postgresql.org/~momjian/upgrade_tips_7.3"></>.
-  </para>
-
-  <para>
-   Observe the following incompatibilities:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Pre-6.3 clients are no longer supported.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <filename>pg_hba.conf</filename> now has a column for the user
-     name and additional features.  Existing files need to be
-     adjusted.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Several <filename>postgresql.conf</filename> logging parameters
-     have been renamed.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <literal>LIMIT #,#</literal> has been disabled; use
-     <literal>LIMIT # OFFSET #</literal>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <command>INSERT</command> statements with column lists must
-     specify a value for each specified column. For example,
-     <literal>INSERT INTO tab (col1, col2) VALUES ('val1')</literal>
-     is now invalid.  It's still allowed to supply fewer columns than
-     expected if the <command>INSERT</command> does not have a column list.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <type>serial</type> columns are no longer automatically
-     <literal>UNIQUE</>; thus, an index will not automatically be
-     created.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     A <command>SET</command> command inside an aborted transaction
-     is now rolled back.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <command>COPY</command> no longer considers missing trailing
-     columns to be null.  All columns need to be specified.
-     (However, one can achieve a similar effect by specifying a
-     column list in the <command>COPY</command> command.)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The data type <type>timestamp</type> is now equivalent to
-     <type>timestamp without time zone</type>, instead of
-     <type>timestamp with time zone</type>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Pre-7.3 databases loaded into 7.3 will not have the new object
-     dependencies for <type>serial</type> columns, unique
-     constraints, and foreign keys. See the directory
-     <filename>contrib/adddepend/</filename> for a detailed
-     description and a script that will add such dependencies.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     An empty string (<literal>''</literal>) is no longer allowed as
-     the input into an integer field.  Formerly, it was silently
-     interpreted as 0.
-    </para>
-   </listitem>
-
-  </itemizedlist>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-
-  <sect3>
-   <title>Server Operation</title>
-<itemizedlist>
-<listitem><para>Add pg_locks view to show locks (Neil)</para></listitem>
-<listitem><para>Security fixes for password negotiation memory allocation (Neil)</para></listitem>
-<listitem><para>Remove support for version 0 FE/BE protocol (<productname>PostgreSQL</productname> 6.2 and earlier) (Tom)</para></listitem>
-<listitem><para>Reserve the last few backend slots for superusers, add parameter superuser_reserved_connections to control this (Nigel J. Andrews)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Performance</title>
-<itemizedlist>
-<listitem><para>Improve startup by calling localtime() only once (Tom)</para></listitem>
-<listitem><para>Cache system catalog information in flat files for faster startup (Tom)</para></listitem>
-<listitem><para>Improve caching of index information (Tom)</para></listitem>
-<listitem><para>Optimizer improvements (Tom, Fernando Nasser)</para></listitem>
-<listitem><para>Catalog caches now store failed lookups (Tom)</para></listitem>
-<listitem><para>Hash function improvements (Neil)</para></listitem>
-<listitem><para>Improve performance of query tokenization and network handling (Peter)</para></listitem>
-<listitem><para>Speed improvement for large object restore (Mario Weilguni)</para></listitem>
-<listitem><para>Mark expired index entries on first lookup, saving later heap fetches (Tom)</para></listitem>
-<listitem><para>Avoid excessive NULL bitmap padding (Manfred Koizar)</para></listitem>
-<listitem><para>Add BSD-licensed qsort() for Solaris, for performance (Bruce)</para></listitem>
-<listitem><para>Reduce per-row overhead by four bytes (Manfred Koizar)</para></listitem>
-<listitem><para>Fix GEQO optimizer bug (Neil Conway)</para></listitem>
-<listitem><para>Make WITHOUT OID actually save four bytes per row (Manfred Koizar)</para></listitem>
-<listitem><para>Add default_statistics_target variable to specify ANALYZE buckets (Neil)</para></listitem>
-<listitem><para>Use local buffer cache for temporary tables so no WAL overhead (Tom)</para></listitem>
-<listitem><para>Improve free space map performance on large tables (Stephen Marshall, Tom)</para></listitem>
-<listitem><para>Improved WAL write concurrency (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Privileges</title>
-<itemizedlist>
-<listitem><para>Add privileges on functions and procedural languages (Peter)</para></listitem>
-<listitem><para>Add OWNER to CREATE DATABASE so superusers can create databases on behalf of unprivileged users (Gavin Sherry, Tom)</para></listitem>
-<listitem><para>Add new object privilege bits EXECUTE and USAGE (Tom)</para></listitem>
-<listitem><para>Add SET SESSION AUTHORIZATION DEFAULT and RESET SESSION AUTHORIZATION (Tom)</para></listitem>
-<listitem><para>Allow functions to be executed with the privilege of the function owner (Peter)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Server Configuration</title>
-<itemizedlist>
-<listitem><para>Server log messages now tagged with LOG, not DEBUG (Bruce)</para></listitem>
-<listitem><para>Add user column to pg_hba.conf (Bruce)</para></listitem>
-<listitem><para>Have log_connections output two lines in log file (Tom)</para></listitem>
-<listitem><para>Remove debug_level from postgresql.conf, now server_min_messages (Bruce)</para></listitem>
-<listitem><para>New ALTER DATABASE/USER ... SET command for per-user/database initialization (Peter)</para></listitem>
-<listitem><para>New parameters server_min_messages and client_min_messages to control which messages are sent to the server logs or client applications (Bruce)</para></listitem>
-<listitem><para>Allow pg_hba.conf to specify lists of users/databases separated by commas, group names prepended with +, and file names prepended with @ (Bruce)</para></listitem>
-<listitem><para>Remove secondary password file capability and pg_password utility (Bruce)</para></listitem>
-<listitem><para>Add variable db_user_namespace for database-local user names (Bruce)</para></listitem>
-<listitem><para>SSL improvements (Bear Giles)</para></listitem>
-<listitem><para>Make encryption of stored passwords the default (Bruce)</para></listitem>
-<listitem><para>Allow pg_statistics to be reset by calling pg_stat_reset() (Christopher)</para></listitem>
-<listitem><para>Add log_duration parameter (Bruce)</para></listitem>
-<listitem><para>Rename debug_print_query to log_statement (Bruce)</para></listitem>
-<listitem><para>Rename show_query_stats to show_statement_stats (Bruce)</para></listitem>
-<listitem><para>Add param log_min_error_statement to print commands to logs on error (Gavin)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Queries</title>
-<itemizedlist>
-<listitem><para>Make cursors insensitive, meaning their contents do not change (Tom)</para></listitem>
-<listitem><para>Disable LIMIT #,# syntax; now only LIMIT # OFFSET # supported (Bruce)</para></listitem>
-<listitem><para>Increase identifier length to 63 (Neil, Bruce)</para></listitem>
-<listitem><para>UNION fixes for merging &gt;= 3 columns of different lengths (Tom)</para></listitem>
-<listitem><para>Add DEFAULT key word to INSERT, e.g., INSERT ... (..., DEFAULT, ...) (Rod)</para></listitem>
-<listitem><para>Allow views to have default values using ALTER COLUMN ... SET DEFAULT (Neil)</para></listitem>
-<listitem><para>Fail on INSERTs with column lists that don't supply all column values, e.g., INSERT INTO tab (col1, col2) VALUES ('val1');  (Rod)</para></listitem>
-<listitem><para>Fix for join aliases (Tom)</para></listitem>
-<listitem><para>Fix for FULL OUTER JOINs (Tom)</para></listitem>
-<listitem><para>Improve reporting of invalid identifier and location (Tom, Gavin)</para></listitem>
-<listitem><para>Fix OPEN cursor(args) (Tom)</para></listitem>
-<listitem><para>Allow 'ctid' to be used in a view and currtid(viewname) (Hiroshi)</para></listitem>
-<listitem><para>Fix for CREATE TABLE AS with UNION (Tom)</para></listitem>
-<listitem><para>SQL99 syntax improvements (Thomas)</para></listitem>
-<listitem><para>Add statement_timeout variable to cancel queries (Bruce)</para></listitem>
-<listitem><para>Allow prepared queries with PREPARE/EXECUTE (Neil)</para></listitem>
-<listitem><para>Allow FOR UPDATE to appear after LIMIT/OFFSET (Bruce)</para></listitem>
-<listitem><para>Add variable autocommit (Tom, David Van Wie)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Object Manipulation</title>
-<itemizedlist>
-<listitem><para>Make equals signs optional in CREATE DATABASE (Gavin Sherry)</para></listitem>
-<listitem><para>Make ALTER TABLE OWNER change index ownership too (Neil)</para></listitem>
-<listitem><para>New ALTER TABLE tabname ALTER COLUMN colname SET STORAGE controls TOAST storage, compression (John Gray)</para></listitem>
-<listitem><para>Add schema support, CREATE/DROP SCHEMA (Tom)</para></listitem>
-<listitem><para>Create schema for temporary tables (Tom)</para></listitem>
-<listitem><para>Add variable search_path for schema search (Tom)</para></listitem>
-<listitem><para>Add ALTER TABLE SET/DROP NOT NULL (Christopher)</para></listitem>
-<listitem><para>New CREATE FUNCTION volatility levels (Tom)</para></listitem>
-<listitem><para>Make rule names unique only per table (Tom)</para></listitem>
-<listitem><para>Add 'ON tablename' clause to DROP RULE and COMMENT ON RULE (Tom)</para></listitem>
-<listitem><para>Add ALTER TRIGGER RENAME (Joe)</para></listitem>
-<listitem><para>New current_schema() and current_schemas() inquiry functions (Tom)</para></listitem>
-<listitem><para>Allow functions to return multiple rows (table functions) (Joe)</para></listitem>
-<listitem><para>Make WITH optional in CREATE DATABASE, for consistency (Bruce)</para></listitem>
-<listitem><para>Add object dependency tracking (Rod, Tom)</para></listitem>
-<listitem><para>Add RESTRICT/CASCADE to DROP commands (Rod)</para></listitem>
-<listitem><para>Add ALTER TABLE DROP for non-CHECK CONSTRAINT (Rod)</para></listitem>
-<listitem><para>Autodestroy sequence on DROP of table with SERIAL (Rod)</para></listitem>
-<listitem><para>Prevent column dropping if column is used by foreign key (Rod)</para></listitem>
-<listitem><para>Automatically drop constraints/functions when object is dropped (Rod)</para></listitem>
-<listitem><para>Add CREATE/DROP OPERATOR CLASS (Bill Studenmund, Tom)</para></listitem>
-<listitem><para>Add ALTER TABLE DROP COLUMN (Christopher, Tom, Hiroshi)</para></listitem>
-<listitem><para>Prevent inherited columns from being removed or renamed (Alvaro Herrera)</para></listitem>
-<listitem><para>Fix foreign key constraints to not error on intermediate database states (Stephan)</para></listitem>
-<listitem><para>Propagate column or table renaming to foreign key constraints</para></listitem>
-<listitem><para>Add CREATE OR REPLACE VIEW (Gavin, Neil, Tom)</para></listitem>
-<listitem><para>Add CREATE OR REPLACE RULE (Gavin, Neil, Tom)</para></listitem>
-<listitem><para>Have rules execute alphabetically, returning more predictable values (Tom)</para></listitem>
-<listitem><para>Triggers are now fired in alphabetical order (Tom)</para></listitem>
-<listitem><para>Add /contrib/adddepend to handle pre-7.3 object dependencies (Rod)</para></listitem>
-<listitem><para>Allow better casting when inserting/updating values (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Utility Commands</title>
-<itemizedlist>
-<listitem><para>Have COPY TO output embedded carriage returns and newlines as \r and \n (Tom)</para></listitem>
-<listitem><para>Allow DELIMITER in COPY FROM to be 8-bit clean (Tatsuo)</para></listitem>
-<listitem><para>Make <application>pg_dump</> use ALTER TABLE ADD PRIMARY KEY, for performance (Neil)</para></listitem>
-<listitem><para>Disable brackets in multistatement rules (Bruce)</para></listitem>
-<listitem><para>Disable VACUUM from being called inside a function (Bruce)</para></listitem>
-<listitem><para>Allow dropdb and other scripts to use identifiers with spaces (Bruce)</para></listitem>
-<listitem><para>Restrict database comment changes to the current database</para></listitem>
-<listitem><para>Allow comments on operators, independent of the underlying function (Rod)</para></listitem>
-<listitem><para>Rollback SET commands in aborted transactions (Tom)</para></listitem>
-<listitem><para>EXPLAIN now outputs as a query (Tom)</para></listitem>
-<listitem><para>Display condition expressions and sort keys in EXPLAIN (Tom)</para></listitem>
-<listitem><para>Add 'SET LOCAL var = value' to set configuration variables for a single transaction (Tom)</para></listitem>
-<listitem><para>Allow ANALYZE to run in a transaction (Bruce)</para></listitem>
-<listitem><para>Improve COPY syntax using new WITH clauses, keep backward compatibility (Bruce)</para></listitem>
-<listitem><para>Fix <application>pg_dump</> to consistently output tags in non-ASCII dumps (Bruce)</para></listitem>
-<listitem><para>Make foreign key constraints clearer in dump file (Rod)</para></listitem>
-<listitem><para>Add COMMENT ON CONSTRAINT (Rod)</para></listitem>
-<listitem><para>Allow COPY TO/FROM to specify column names (Brent Verner)</para></listitem>
-<listitem><para>Dump UNIQUE and PRIMARY KEY constraints as ALTER TABLE (Rod)</para></listitem>
-<listitem><para>Have SHOW output a query result (Joe)</para></listitem>
-<listitem><para>Generate failure on short COPY lines rather than pad NULLs (Neil)</para></listitem>
-<listitem><para>Fix CLUSTER to preserve all table attributes (Alvaro Herrera)</para></listitem>
-<listitem><para>New pg_settings table to view/modify GUC settings (Joe)</para></listitem>
-<listitem><para>Add smart quoting, portability improvements to <application>pg_dump</> output (Peter)</para></listitem>
-<listitem><para>Dump serial columns out as SERIAL (Tom)</para></listitem>
-<listitem><para>Enable large file support, &gt;2G for <application>pg_dump</> (Peter, Philip Warner, Bruce)</para></listitem>
-<listitem><para>Disallow TRUNCATE on tables that are involved in referential constraints (Rod)</para></listitem>
-<listitem><para>Have TRUNCATE also auto-truncate the toast table of the relation (Tom)</para></listitem>
-<listitem><para>Add clusterdb utility that will auto-cluster an entire database based on previous CLUSTER operations (Alvaro Herrera)</para></listitem>
-<listitem><para>Overhaul pg_dumpall (Peter)</para></listitem>
-<listitem><para>Allow REINDEX of TOAST tables (Tom)</para></listitem>
-<listitem><para>Implemented START TRANSACTION, per SQL99 (Neil)</para></listitem>
-<listitem><para>Fix rare index corruption when a page split affects bulk delete (Tom)</para></listitem>
-<listitem><para>Fix ALTER TABLE ... ADD COLUMN for inheritance (Alvaro Herrera)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Data Types and Functions</title>
-<itemizedlist>
-<listitem><para>Fix factorial(0) to return 1 (Bruce)</para></listitem>
-<listitem><para>Date/time/timezone improvements (Thomas)</para></listitem>
-<listitem><para>Fix for array slice extraction (Tom)</para></listitem>
-<listitem><para>Fix extract/date_part to report proper microseconds for timestamp (Tatsuo)</para></listitem>
-<listitem><para>Allow text_substr() and bytea_substr() to read TOAST values more efficiently (John Gray)</para></listitem>
-<listitem><para>Add domain support (Rod)</para></listitem>
-<listitem><para>Make WITHOUT TIME ZONE the default for TIMESTAMP and TIME data types (Thomas)</para></listitem>
-<listitem><para>Allow alternate storage scheme of 64-bit integers for date/time types using --enable-integer-datetimes in configure (Thomas)</para></listitem>
-<listitem><para>Make timezone(timestamptz) return timestamp rather than a string (Thomas)</para></listitem>
-<listitem><para>Allow fractional seconds in date/time types for dates prior to 1BC (Thomas)</para></listitem>
-<listitem><para>Limit timestamp data types to 6 decimal places of precision (Thomas)</para></listitem>
-<listitem><para>Change timezone conversion functions from timetz() to timezone() (Thomas)</para></listitem>
-<listitem><para>Add configuration variables datestyle and timezone (Tom)</para></listitem>
-<listitem><para>Add OVERLAY(), which allows substitution of a substring in a string (Thomas)</para></listitem>
-<listitem><para>Add SIMILAR TO (Thomas, Tom)</para></listitem>
-<listitem><para>Add regular expression SUBSTRING(string FROM pat FOR escape) (Thomas)</para></listitem>
-<listitem><para>Add LOCALTIME and LOCALTIMESTAMP functions (Thomas)</para></listitem>
-<listitem><para>Add named composite types using CREATE TYPE typename AS (column) (Joe)</para></listitem>
-<listitem><para>Allow composite type definition in the table alias clause (Joe)</para></listitem>
-<listitem><para>Add new API to simplify creation of C language table functions (Joe)</para></listitem>
-<listitem><para>Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard (Thomas)</para></listitem>
-<listitem><para>Allow macaddr data type to accept 12 hex digits with no separators (Mike Wyer)</para></listitem>
-<listitem><para>Add CREATE/DROP CAST (Peter)</para></listitem>
-<listitem><para>Add IS DISTINCT FROM operator (Thomas)</para></listitem>
-<listitem><para>Add SQL99 TREAT() function, synonym for CAST() (Thomas)</para></listitem>
-<listitem><para>Add pg_backend_pid() to output backend pid (Bruce)</para></listitem>
-<listitem><para>Add IS OF / IS NOT OF type predicate (Thomas)</para></listitem>
-<listitem><para>Allow bit string constants without fully-specified length (Thomas)</para></listitem>
-<listitem><para>Allow conversion between 8-byte integers and bit strings (Thomas)</para></listitem>
-<listitem><para>Implement hex literal conversion to bit string literal (Thomas)</para></listitem>
-<listitem><para>Allow table functions to appear in the FROM clause (Joe)</para></listitem>
-<listitem><para>Increase maximum number of function parameters to 32 (Bruce)</para></listitem>
-<listitem><para>No longer automatically create index for SERIAL column (Tom)</para></listitem>
-<listitem><para>Add current_database() (Rod)</para></listitem>
-<listitem><para>Fix cash_words() to not overflow buffer (Tom)</para></listitem>
-<listitem><para>Add functions replace(), split_part(), to_hex() (Joe)</para></listitem>
-<listitem><para>Fix LIKE for bytea as a right-hand argument (Joe)</para></listitem>
-<listitem><para>Prevent crashes caused by SELECT cash_out(2) (Tom)</para></listitem>
-<listitem><para>Fix to_char(1,'FM999.99') to return a period (Karel)</para></listitem>
-<listitem><para>Fix trigger/type/language functions returning OPAQUE to return proper type (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Internationalization</title>
-<itemizedlist>
-<listitem><para>Add additional encodings: Korean (JOHAB), Thai (WIN874), Vietnamese (TCVN), Arabic (WIN1256), Simplified Chinese (GBK), Korean (UHC) (Eiji Tokuya)</para></listitem>
-<listitem><para>Enable locale support by default (Peter)</para></listitem>
-<listitem><para>Add locale variables (Peter)</para></listitem>
-<listitem><para>Escape byes &gt;= 0x7f for multibyte in PQescapeBytea/PQunescapeBytea (Tatsuo)</para></listitem>
-<listitem><para>Add locale awareness to regular expression character classes</para></listitem>
-<listitem><para>Enable multibyte support by default (Tatsuo)</para></listitem>
-<listitem><para>Add GB18030 multibyte support (Bill Huang)</para></listitem>
-<listitem><para>Add CREATE/DROP CONVERSION, allowing loadable encodings (Tatsuo, Kaori)</para></listitem>
-<listitem><para>Add pg_conversion table (Tatsuo)</para></listitem>
-<listitem><para>Add SQL99 CONVERT() function (Tatsuo)</para></listitem>
-<listitem><para>pg_dumpall, pg_controldata, and pg_resetxlog now national-language aware (Peter)</para></listitem>
-<listitem><para>New and updated translations</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Server-side Languages</title>
-<itemizedlist>
-<listitem><para>Allow recursive SQL function (Peter)</para></listitem>
-<listitem><para>Change PL/Tcl build to use configured compiler and Makefile.shlib (Peter)</para></listitem>
-<listitem><para>Overhaul the PL/pgSQL FOUND variable to be more Oracle-compatible (Neil, Tom)</para></listitem>
-<listitem><para>Allow PL/pgSQL to handle quoted identifiers (Tom)</para></listitem>
-<listitem><para>Allow set-returning PL/pgSQL functions (Neil)</para></listitem>
-<listitem><para>Make PL/pgSQL schema-aware (Joe)</para></listitem>
-<listitem><para>Remove some memory leaks (Nigel J. Andrews, Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>psql</title>
-<itemizedlist>
-<listitem><para>Don't lowercase psql \connect database name for 7.2.0 compatibility (Tom)</para></listitem>
-<listitem><para>Add psql \timing to time user queries (Greg Sabino Mullane)</para></listitem>
-<listitem><para>Have psql \d show index information (Greg Sabino Mullane)</para></listitem>
-<listitem><para>New psql \dD shows domains (Jonathan Eisler)</para></listitem>
-<listitem><para>Allow psql to show rules on views (Paul ?)</para></listitem>
-<listitem><para>Fix for psql variable substitution (Tom)</para></listitem>
-<listitem><para>Allow psql \d to show temporary table structure (Tom)</para></listitem>
-<listitem><para>Allow psql \d to show foreign keys (Rod)</para></listitem>
-<listitem><para>Fix \? to honor \pset pager (Bruce)</para></listitem>
-<listitem><para>Have psql reports its version number on startup (Tom)</para></listitem>
-<listitem><para>Allow \copy to specify column names (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>libpq</title>
-<itemizedlist>
-<listitem><para>Add ~/.pgpass to store host/user password combinations (Alvaro Herrera)</para></listitem>
-<listitem><para>Add PQunescapeBytea() function to libpq (Patrick Welche)</para></listitem>
-<listitem><para>Fix for sending large queries over non-blocking connections (Bernhard Herzog)</para></listitem>
-<listitem><para>Fix for libpq using timers on Win9X (David Ford)</para></listitem>
-<listitem><para>Allow libpq notify to handle servers with different-length identifiers (Tom)</para></listitem>
-<listitem><para>Add libpq PQescapeString() and PQescapeBytea() to Windows (Bruce)</para></listitem>
-<listitem><para>Fix for SSL with non-blocking connections (Jack Bates)</para></listitem>
-<listitem><para>Add libpq connection timeout parameter (Denis A Ustimenko)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>JDBC</title>
-<itemizedlist>
-<listitem><para>Allow JDBC to compile with JDK 1.4 (Dave)</para></listitem>
-<listitem><para>Add JDBC 3 support (Barry)</para></listitem>
-<listitem><para>Allows JDBC to set loglevel by adding ?loglevel=X to the connection URL (Barry)</para></listitem>
-<listitem><para>Add Driver.info() message that prints out the version number (Barry)</para></listitem>
-<listitem><para>Add updateable result sets (Raghu Nidagal, Dave)</para></listitem>
-<listitem><para>Add support for callable statements (Paul Bethe)</para></listitem>
-<listitem><para>Add query cancel capability</para></listitem>
-<listitem><para>Add refresh row (Dave)</para></listitem>
-<listitem><para>Fix MD5 encryption handling for multibyte servers (Jun Kawai)</para></listitem>
-<listitem><para>Add support for prepared statements (Barry)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Miscellaneous Interfaces</title>
-<itemizedlist>
-<listitem><para>Fixed ECPG bug concerning octal numbers in single quotes (Michael)</para></listitem>
-<listitem><para>Move src/interfaces/libpgeasy to http://gborg.postgresql.org (Marc, Bruce)</para></listitem>
-<listitem><para>Improve Python interface (Elliot Lee, Andrew Johnson, Greg Copeland)</para></listitem>
-<listitem><para>Add libpgtcl connection close event (Gerhard Hintermayer)</para></listitem>
-<listitem><para>Move src/interfaces/libpq++ to http://gborg.postgresql.org (Marc, Bruce)</para></listitem>
-<listitem><para>Move src/interfaces/odbc to http://gborg.postgresql.org (Marc)</para></listitem>
-<listitem><para>Move src/interfaces/libpgeasy to http://gborg.postgresql.org (Marc, Bruce)</para></listitem>
-<listitem><para>Move src/interfaces/perl5 to http://gborg.postgresql.org (Marc, Bruce)</para></listitem>
-<listitem><para>Remove src/bin/pgaccess from main tree, now at http://www.pgaccess.org (Bruce)</para></listitem>
-<listitem><para>Add pg_on_connection_loss command to libpgtcl (Gerhard Hintermayer, Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Source Code</title>
-<itemizedlist>
-<listitem><para>Fix for parallel make (Peter)</para></listitem>
-<listitem><para>AIX fixes for linking Tcl (Andreas Zeugswetter)</para></listitem>
-<listitem><para>Allow PL/Perl to build under Cygwin (Jason Tishler)</para></listitem>
-<listitem><para>Improve MIPS compiles (Peter, Oliver Elphick)</para></listitem>
-<listitem><para>Require Autoconf version 2.53 (Peter)</para></listitem>
-<listitem><para>Require readline and zlib by default in configure (Peter)</para></listitem>
-<listitem><para>Allow Solaris to use Intimate Shared Memory (ISM), for performance (Scott Brunza, P.J. Josh Rovero)</para></listitem>
-<listitem><para>Always enable syslog in compile, remove --enable-syslog option (Tatsuo)</para></listitem>
-<listitem><para>Always enable multibyte in compile, remove --enable-multibyte option (Tatsuo)</para></listitem>
-<listitem><para>Always enable locale in compile, remove --enable-locale option (Peter)</para></listitem>
-<listitem><para>Fix for Win9x DLL creation (Magnus Naeslund)</para></listitem>
-<listitem><para>Fix for link() usage by WAL code on Windows, BeOS (Jason Tishler)</para></listitem>
-<listitem><para>Add sys/types.h to c.h, remove from main files (Peter, Bruce)</para></listitem>
-<listitem><para>Fix AIX hang on SMP machines (Tomoyuki Niijima)</para></listitem>
-<listitem><para>AIX SMP hang fix (Tomoyuki Niijima)</para></listitem>
-<listitem><para>Fix pre-1970 date handling on newer glibc libraries (Tom)</para></listitem>
-<listitem><para>Fix PowerPC SMP locking (Tom)</para></listitem>
-<listitem><para>Prevent gcc -ffast-math from being used (Peter, Tom)</para></listitem>
-<listitem><para>Bison &gt;= 1.50 now required for developer builds</para></listitem>
-<listitem><para>Kerberos 5 support now builds with Heimdal (Peter)</para></listitem>
-<listitem><para>Add appendix in the User's Guide which lists SQL features (Thomas)</para></listitem>
-<listitem><para>Improve loadable module linking to use RTLD_NOW (Tom)</para></listitem>
-<listitem><para>New error levels WARNING, INFO, LOG, DEBUG[1-5] (Bruce)</para></listitem>
-<listitem><para>New src/port directory holds replaced libc functions (Peter, Bruce)</para></listitem>
-<listitem><para>New pg_namespace system catalog for schemas (Tom)</para></listitem>
-<listitem><para>Add pg_class.relnamespace for schemas (Tom)</para></listitem>
-<listitem><para>Add pg_type.typnamespace for schemas (Tom)</para></listitem>
-<listitem><para>Add pg_proc.pronamespace for schemas (Tom)</para></listitem>
-<listitem><para>Restructure aggregates to have pg_proc entries (Tom)</para></listitem>
-<listitem><para>System relations now have their own namespace, pg_* test not required (Fernando Nasser)</para></listitem>
-<listitem><para>Rename TOAST index names to be *_index rather than *_idx (Neil)</para></listitem>
-<listitem><para>Add namespaces for operators, opclasses (Tom)</para></listitem>
-<listitem><para>Add additional checks to server control file (Thomas)</para></listitem>
-<listitem><para>New Polish FAQ (Marcin Mazurek)</para></listitem>
-<listitem><para>Add Posix semaphore support (Tom)</para></listitem>
-<listitem><para>Document need for reindex (Bruce)</para></listitem>
-<listitem><para>Rename some internal identifiers to simplify Windows compile (Jan, Katherine Ward)</para></listitem>
-<listitem><para>Add documentation on computing disk space (Bruce)</para></listitem>
-<listitem><para>Remove KSQO from GUC (Bruce)</para></listitem>
-<listitem><para>Fix memory leak in rtree (Kenneth Been)</para></listitem>
-<listitem><para>Modify a few error messages for consistency (Bruce)</para></listitem>
-<listitem><para>Remove unused system table columns (Peter)</para></listitem>
-<listitem><para>Make system columns NOT NULL where appropriate (Tom)</para></listitem>
-<listitem><para>Clean up use of sprintf in favor of snprintf() (Neil, Jukka Holappa)</para></listitem>
-<listitem><para>Remove OPAQUE and create specific subtypes (Tom)</para></listitem>
-<listitem><para>Cleanups in array internal handling (Joe, Tom)</para></listitem>
-<listitem><para>Disallow pg_atoi('') (Bruce)</para></listitem>
-<listitem><para>Remove parameter wal_files because WAL files are now recycled (Bruce)</para></listitem>
-<listitem><para>Add version numbers to heap pages (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Contrib</title>
-<itemizedlist>
-<listitem><para>Allow inet arrays in /contrib/array (Neil)</para></listitem>
-<listitem><para>GiST fixes (Teodor Sigaev, Neil)</para></listitem>
-<listitem><para>Upgrade /contrib/mysql</para></listitem>
-<listitem><para>Add /contrib/dbsize which shows table sizes without vacuum (Peter)</para></listitem>
-<listitem><para>Add /contrib/intagg, integer aggregator routines (mlw)</para></listitem>
-<listitem><para>Improve /contrib/oid2name (Neil, Bruce)</para></listitem>
-<listitem><para>Improve /contrib/tsearch (Oleg, Teodor Sigaev)</para></listitem>
-<listitem><para>Cleanups of /contrib/rserver (Alexey V. Borzov)</para></listitem>
-<listitem><para>Update /contrib/oracle conversion utility (Gilles Darold)</para></listitem>
-<listitem><para>Update /contrib/dblink (Joe)</para></listitem>
-<listitem><para>Improve options supported by /contrib/vacuumlo (Mario Weilguni)</para></listitem>
-<listitem><para>Improvements to /contrib/intarray (Oleg, Teodor Sigaev, Andrey Oktyabrski)</para></listitem>
-<listitem><para>Add /contrib/reindexdb utility (Shaun Thomas)</para></listitem>
-<listitem><para>Add indexing to /contrib/isbn_issn (Dan Weston)</para></listitem>
-<listitem><para>Add /contrib/dbmirror (Steven Singer)</para></listitem>
-<listitem><para>Improve /contrib/pgbench (Neil)</para></listitem>
-<listitem><para>Add /contrib/tablefunc table function examples (Joe)</para></listitem>
-<listitem><para>Add /contrib/ltree data type for tree structures (Teodor Sigaev, Oleg Bartunov)</para></listitem>
-<listitem><para>Move /contrib/pg_controldata, pg_resetxlog into main tree (Bruce)</para></listitem>
-<listitem><para>Fixes to /contrib/cube (Bruno Wolff)</para></listitem>
-<listitem><para>Improve /contrib/fulltextindex (Christopher)</para></listitem>
-</itemizedlist>
-  </sect3>
-
- </sect2>
-</sect1>
-
- <sect1 id="release-7-2-8">
-  <title>Release 7.2.8</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-05-09</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.2.7, including one
-   security-related issue.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.2.8</title>
-
-   <para>
-    A dump/restore is not required for those running 7.2.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Repair ancient race condition that allowed a transaction to be
-seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner
-than for other purposes</para>
-<para>This is an extremely serious bug since it could lead to apparent
-data inconsistencies being briefly visible to applications.</para></listitem>
-<listitem><para>Repair race condition between relation extension and
-VACUUM</para>
-<para>This could theoretically have caused loss of a page's worth of
-freshly-inserted data, although the scenario seems of very low probability.
-There are no known cases of it having caused more than an Assert failure.
-</para></listitem>
-<listitem><para>Fix <function>EXTRACT(EPOCH)</> for
-<type>TIME WITH TIME ZONE</> values</para></listitem>
-<listitem><para>Additional buffer overrun checks in plpgsql
-(Neil)</para></listitem>
-<listitem><para>Fix pg_dump to dump index names and trigger names containing
-<literal>%</> correctly (Neil)</para></listitem>
-<listitem><para>Prevent <function>to_char(interval)</> from dumping core for
-month-related formats</para></listitem>
-<listitem><para>Fix <filename>contrib/pgcrypto</> for newer OpenSSL builds
-(Marko Kreen)</para></listitem>
-</itemizedlist>
-
- </sect2>
-</sect1>
-
- <sect1 id="release-7-2-7">
-  <title>Release 7.2.7</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2005-01-31</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.2.6, including several
-   security-related issues.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.2.7</title>
-
-   <para>
-    A dump/restore is not required for those running 7.2.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Disallow <command>LOAD</> to non-superusers</para>
-<para>
-On platforms that will automatically execute initialization functions of a
-shared library (this includes at least Windows and ELF-based Unixen),
-<command>LOAD</> can be used to make the server execute arbitrary code.
-Thanks to NGS Software for reporting this.</para></listitem>
-<listitem><para>Add needed STRICT marking to some contrib functions (Kris
-Jurka)</para></listitem>
-<listitem><para>Avoid buffer overrun when plpgsql cursor declaration has too
-many parameters (Neil)</para></listitem>
-<listitem><para>Fix planning error for FULL and RIGHT outer joins</para>
-<para>
-The result of the join was mistakenly supposed to be sorted the same as the
-left input.  This could not only deliver mis-sorted output to the user, but
-in case of nested merge joins could give outright wrong answers.
-</para></listitem>
-<listitem><para>Fix display of negative intervals in SQL and GERMAN
-datestyles</para></listitem>
-</itemizedlist>
-
- </sect2>
-</sect1>
-
- <sect1 id="release-7-2-6">
-  <title>Release 7.2.6</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2004-10-22</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.2.5.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.2.6</title>
-
-   <para>
-    A dump/restore is not required for those running 7.2.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Repair possible failure to update hint bits on disk</para>
-<para>
-Under rare circumstances this oversight could lead to
-<quote>could not access transaction status</> failures, which qualifies
-it as a potential-data-loss bug.
-</para></listitem>
-<listitem><para>Ensure that hashed outer join does not miss tuples</para>
-<para>
-Very large left joins using a hash join plan could fail to output unmatched
-left-side rows given just the right data distribution.
-</para></listitem>
-<listitem><para>Disallow running pg_ctl as root</para>
-<para>
-This is to guard against any possible security issues.
-</para></listitem>
-<listitem><para>Avoid using temp files in /tmp in make_oidjoins_check</para>
-<para>
-This has been reported as a security issue, though it's hardly worthy of
-concern since there is no reason for non-developers to use this script anyway.
-</para></listitem>
-<listitem><para>Update to newer versions of Bison</para></listitem>
-</itemizedlist>
-
- </sect2>
-</sect1>
-
- <sect1 id="release-7-2-5">
-  <title>Release 7.2.5</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2004-08-16</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 7.2.4.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.2.5</title>
-
-   <para>
-    A dump/restore is not required for those running 7.2.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Prevent possible loss of committed transactions during crash</para>
-<para>
-Due to insufficient interlocking between transaction commit and checkpointing,
-it was possible for transactions committed just before the most recent
-checkpoint to be lost, in whole or in part, following a database crash and
-restart.  This is a serious bug that has existed
-since <productname>PostgreSQL</productname> 7.1.
-</para></listitem>
-<listitem><para>Fix corner case for btree search in parallel with first root page split</para></listitem>
-<listitem><para>Fix buffer overrun in <function>to_ascii</function> (Guido Notari)</para></listitem>
-<listitem><para>Fix core dump in deadlock detection on machines where char is unsigned</para></listitem>
-<listitem><para>Fix failure to respond to <command>pg_ctl stop -m fast</command> after Async_NotifyHandler runs</para></listitem>
-<listitem><para>Repair memory leaks in pg_dump</para></listitem>
-<listitem><para>Avoid conflict with system definition of <function>isblank()</function> function or macro</para></listitem>
-</itemizedlist>
- </sect2>
-</sect1>
-
-<sect1 id="release-7-2-4">
- <title>Release 7.2.4</title>
-
- <note>
-  <title>Release Date</title>
-  <simpara>2003-01-30</simpara>
- </note>
-
- <para>
-  This release contains a variety of fixes for version 7.2.3,
-  including fixes to prevent possible data loss.
- </para>
-
- <sect2>
-  <title>Migration to Version 7.2.4</title>
-
-  <para>
-   A dump/restore is <emphasis>not</emphasis> required for those
-   running version 7.2.*.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Fix some additional cases of VACUUM "No one parent tuple was found" error</para></listitem>
-<listitem><para>Prevent VACUUM from being called inside a function  (Bruce)</para></listitem>
-<listitem><para>Ensure pg_clog updates are sync'd to disk before marking checkpoint complete</para></listitem>
-<listitem><para>Avoid integer overflow during large hash joins</para></listitem>
-<listitem><para>Make GROUP commands work when pg_group.grolist is large enough to be toasted</para></listitem>
-<listitem><para>Fix errors in datetime tables; some timezone names weren't being recognized</para></listitem>
-<listitem><para>Fix integer overflows in circle_poly(), path_encode(), path_add()  (Neil)</para></listitem>
-<listitem><para>Repair long-standing logic errors in lseg_eq(), lseg_ne(), lseg_center()</para></listitem>
-</itemizedlist>
- </sect2>
-</sect1>
-
-
-<sect1 id="release-7-2-3">
- <title>Release 7.2.3</title>
-
- <note>
-  <title>Release Date</title>
-  <simpara>2002-10-01</simpara>
- </note>
-
- <para>
-  This release contains a variety of fixes for version 7.2.2,
-  including fixes to prevent possible data loss.
- </para>
-
- <sect2>
-  <title>Migration to Version 7.2.3</title>
-
-  <para>
-   A dump/restore is <emphasis>not</emphasis> required for those
-   running version 7.2.*.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Prevent possible compressed transaction log loss (Tom)</para></listitem>
-<listitem><para>Prevent non-superuser from increasing most recent vacuum info (Tom)</para></listitem>
-<listitem><para>Handle pre-1970 date values in newer versions of glibc (Tom)</para></listitem>
-<listitem><para>Fix possible hang during server shutdown</para></listitem>
-<listitem><para>Prevent spinlock hangs on SMP PPC machines (Tomoyuki Niijima)</para></listitem>
-<listitem><para>Fix <application>pg_dump</> to properly dump FULL JOIN USING (Tom)</para></listitem>
-</itemizedlist>
- </sect2>
-</sect1>
-
-
-<sect1 id="release-7-2-2">
- <title>Release 7.2.2</title>
-
- <note>
-  <title>Release Date</title>
-  <simpara>2002-08-23</simpara>
- </note>
-
- <para>
-  This release contains a variety of fixes for version 7.2.1.
- </para>
-
- <sect2>
-  <title>Migration to Version 7.2.2</title>
-
-  <para>
-   A dump/restore is <emphasis>not</emphasis> required for those
-   running version 7.2.*.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)</para></listitem>
-<listitem><para>Fix for compressed transaction log id wraparound (Tom)</para></listitem>
-<listitem><para>Fix PQescapeBytea/PQunescapeBytea so that they handle bytes &gt; 0x7f (Tatsuo)</para></listitem>
-<listitem><para>Fix for psql and <application>pg_dump</> crashing when invoked with non-existent long options (Tatsuo)</para></listitem>
-<listitem><para>Fix crash when invoking geometric operators (Tom)</para></listitem>
-<listitem><para>Allow OPEN cursor(args) (Tom)</para></listitem>
-<listitem><para>Fix for rtree_gist index build (Teodor)</para></listitem>
-<listitem><para>Fix for dumping user-defined aggregates (Tom)</para></listitem>
-<listitem><para>contrib/intarray fixes (Oleg)</para></listitem>
-<listitem><para>Fix for complex UNION/EXCEPT/INTERSECT queries using parens (Tom)</para></listitem>
-<listitem><para>Fix to pg_convert (Tatsuo)</para></listitem>
-<listitem><para>Fix for crash with long DATA strings (Thomas, Neil)</para></listitem>
-<listitem><para>Fix for repeat(), lpad(), rpad() and long strings (Neil)</para></listitem>
-</itemizedlist>
- </sect2>
-</sect1>
-
-
-<sect1 id="release-7-2-1">
- <title>Release 7.2.1</title>
-
- <note>
-  <title>Release Date</title>
-  <simpara>2002-03-21</simpara>
- </note>
-
- <para>
-  This release contains a variety of fixes for version 7.2.
- </para>
-
- <sect2>
-  <title>Migration to Version 7.2.1</title>
-
-  <para>
-   A dump/restore is <emphasis>not</emphasis> required for those
-   running version 7.2.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-
-<itemizedlist>
-<listitem><para>Ensure that sequence counters do not go backwards after a crash (Tom)</para></listitem>
-<listitem><para>Fix pgaccess kanji-conversion key binding (Tatsuo)</para></listitem>
-<listitem><para>Optimizer improvements (Tom)</para></listitem>
-<listitem><para>Cash I/O improvements (Tom)</para></listitem>
-<listitem><para>New Russian FAQ</para></listitem>
-<listitem><para>Compile fix for missing AuthBlockSig (Heiko)</para></listitem>
-<listitem><para>Additional time zones and time zone fixes (Thomas)</para></listitem>
-<listitem><para>Allow psql \connect to handle mixed case database and user names (Tom)</para></listitem>
-<listitem><para>Return proper OID on command completion even with ON INSERT rules (Tom)</para></listitem>
-<listitem><para>Allow COPY FROM to use 8-bit DELIMITERS (Tatsuo)</para></listitem>
-<listitem><para>Fix bug in extract/date_part for milliseconds/microseconds (Tatsuo)</para></listitem>
-<listitem><para>Improve handling of multiple UNIONs with different lengths (Tom)</para></listitem>
-<listitem><para>contrib/btree_gist improvements (Teodor Sigaev)</para></listitem>
-<listitem><para>contrib/tsearch dictionary improvements, see README.tsearch for an additional installation step (Thomas T. Thai, Teodor Sigaev)</para></listitem>
-<listitem><para>Fix for array subscripts handling (Tom)</para></listitem>
-<listitem><para>Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)</para></listitem>
-</itemizedlist>
- </sect2>
-</sect1>
-
-
-<sect1 id="release-7-2">
- <title>Release 7.2</title>
-
- <note>
-  <title>Release Date</title>
-  <simpara>2002-02-04</simpara>
- </note>
-
- <sect2>
-  <title>Overview</title>
-
-  <para>
-   This release improves <productname>PostgreSQL</> for use in
-   high-volume applications.
-  </para>
-
-  <para>
-   Major changes in this release:
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term>VACUUM</term>
-    <listitem>
-     <para>
-      Vacuuming no longer locks tables, thus allowing normal user
-      access during the vacuum.  A new <command>VACUUM FULL</>
-      command does old-style vacuum by locking the table and
-      shrinking the on-disk copy of the table.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Transactions</term>
-    <listitem>
-     <para>
-      There is no longer a problem with installations that exceed
-      four billion transactions.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>OIDs</term>
-    <listitem>
-     <para>
-      OIDs are now optional.  Users can now create tables without
-      OIDs for cases where OID usage is excessive.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Optimizer</term>
-    <listitem>
-     <para>
-      The system now computes histogram column statistics during
-      <command>ANALYZE</>, allowing much better optimizer choices.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Security</term>
-    <listitem>
-     <para>
-      A new MD5 encryption option allows more secure storage and
-      transfer of passwords.  A new Unix-domain socket
-      authentication option is available on Linux and BSD systems.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Statistics</term>
-    <listitem>
-     <para>
-      Administrators can use the new table access statistics module
-      to get fine-grained information about table and index usage.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Internationalization</term>
-    <listitem>
-     <para>
-      Program and library messages can now be displayed in several
-      languages.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
- </sect2>
-
- <sect2>
-  <title>Migration to Version 7.2</title>
-
-  <para>
-   A dump/restore using <command>pg_dump</command> is required for
-   those wishing to migrate data from any previous release.
-  </para>
-
-  <para>
-   Observe the following incompatibilities:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     The semantics of the <command>VACUUM</command> command have
-     changed in this release.  You might wish to update your
-     maintenance procedures accordingly.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     In this release, comparisons using <literal>= NULL</literal>
-     will always return false (or NULL, more precisely).  Previous
-     releases automatically transformed this syntax to <literal>IS
-     NULL</literal>.  The old behavior can be re-enabled using a
-     <filename>postgresql.conf</filename> parameter.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The <filename>pg_hba.conf</> and <filename>pg_ident.conf</>
-     configuration is now only reloaded after receiving a
-     <systemitem>SIGHUP</> signal, not with each connection.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The function <filename>octet_length()</> now returns the uncompressed data length.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The date/time value <literal>'current'</literal> is no longer
-     available.  You will need to rewrite your applications.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The <literal>timestamp()</literal>, <literal>time()</literal>,
-     and <literal>interval()</literal> functions are no longer
-     available.  Instead of <literal>timestamp()</literal>, use
-     <literal>timestamp 'string'</literal> or <literal>CAST</literal>.
-    </para>
-   </listitem>
-
-  </itemizedlist>
-
-  <para>
-   The <literal>SELECT ... LIMIT #,#</literal> syntax will be removed
-   in the next release. You should change your queries to use
-   separate LIMIT and OFFSET clauses, e.g. <literal>LIMIT 10 OFFSET
-   20</literal>.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Changes</title>
-
-  <sect3>
-   <title>Server Operation</title>
-<itemizedlist>
-<listitem><para>Create temporary files in a separate directory (Bruce)</para></listitem>
-<listitem><para>Delete orphaned temporary files on postmaster startup (Bruce)</para></listitem>
-<listitem><para>Added unique indexes to some system tables (Tom)</para></listitem>
-<listitem><para>System table operator reorganization (Oleg Bartunov, Teodor Sigaev, Tom)</para></listitem>
-<listitem><para>Renamed pg_log to pg_clog (Tom)</para></listitem>
-<listitem><para>Enable SIGTERM, SIGQUIT to kill backends (Jan)</para></listitem>
-<listitem><para>Removed compile-time limit on number of backends (Tom)</para></listitem>
-<listitem><para>Better cleanup for semaphore resource failure (Tatsuo, Tom)</para></listitem>
-<listitem><para>Allow safe transaction ID wraparound (Tom)</para></listitem>
-<listitem><para>Removed OIDs from some system tables (Tom)</para></listitem>
-<listitem><para>Removed "triggered data change violation" error check (Tom)</para></listitem>
-<listitem><para>SPI portal creation of prepared/saved plans (Jan)</para></listitem>
-<listitem><para>Allow SPI column functions to work for system columns (Tom)</para></listitem>
-<listitem><para>Long value compression improvement (Tom)</para></listitem>
-<listitem><para>Statistics collector for table, index access (Jan)</para></listitem>
-<listitem><para>Truncate extra-long sequence names to a reasonable value (Tom)</para></listitem>
-<listitem><para>Measure transaction times in milliseconds (Thomas)</para></listitem>
-<listitem><para>Fix TID sequential scans (Hiroshi)</para></listitem>
-<listitem><para>Superuser ID now fixed at 1 (Peter E)</para></listitem>
-<listitem><para>New pg_ctl "reload" option (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Performance</title>
-<itemizedlist>
-<listitem><para>Optimizer improvements (Tom)</para></listitem>
-<listitem><para>New histogram column statistics for optimizer (Tom)</para></listitem>
-<listitem><para>Reuse write-ahead log files rather than discarding them (Tom)</para></listitem>
-<listitem><para>Cache improvements (Tom)</para></listitem>
-<listitem><para>IS NULL, IS NOT NULL optimizer improvement (Tom)</para></listitem>
-<listitem><para>Improve lock manager to reduce lock contention (Tom)</para></listitem>
-<listitem><para>Keep relcache entries for index access support functions (Tom)</para></listitem>
-<listitem><para>Allow better selectivity with NaN and infinities in NUMERIC (Tom)</para></listitem>
-<listitem><para>R-tree performance improvements (Kenneth Been)</para></listitem>
-<listitem><para>B-tree splits more efficient (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Privileges</title>
-<itemizedlist>
-<listitem><para>Change UPDATE, DELETE privileges to be distinct (Peter E)</para></listitem>
-<listitem><para>New REFERENCES, TRIGGER privileges (Peter E)</para></listitem>
-<listitem><para>Allow GRANT/REVOKE to/from more than one user at a time (Peter E)</para></listitem>
-<listitem><para>New has_table_privilege() function (Joe Conway)</para></listitem>
-<listitem><para>Allow non-superuser to vacuum database (Tom)</para></listitem>
-<listitem><para>New SET SESSION AUTHORIZATION command (Peter E)</para></listitem>
-<listitem><para>Fix bug in privilege modifications on newly created tables (Tom)</para></listitem>
-<listitem><para>Disallow access to pg_statistic for non-superuser, add user-accessible views (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Client Authentication</title>
-<itemizedlist>
-<listitem><para>Fork postmaster before doing authentication to prevent hangs (Peter E)</para></listitem>
-<listitem><para>Add ident authentication over Unix domain sockets on Linux, *BSD (Helge Bahmann, Oliver Elphick, Teodor Sigaev, Bruce)</para></listitem>
-<listitem><para>Add a password authentication method that uses MD5 encryption (Bruce)</para></listitem>
-<listitem><para>Allow encryption of stored passwords using MD5 (Bruce)</para></listitem>
-<listitem><para>PAM authentication (Dominic J. Eidson)</para></listitem>
-<listitem><para>Load pg_hba.conf and pg_ident.conf only on startup and SIGHUP (Bruce)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Server Configuration</title>
-<itemizedlist>
-<listitem><para>Interpretation of some time zone abbreviations as Australian rather than North American now settable at run time (Bruce)</para></listitem>
-<listitem><para>New parameter to set default transaction isolation level (Peter E)</para></listitem>
-<listitem><para>New parameter to enable conversion of "expr = NULL" into "expr IS NULL", off by default (Peter E)</para></listitem>
-<listitem><para>New parameter to control memory usage by VACUUM (Tom)</para></listitem>
-<listitem><para>New parameter to set client authentication timeout (Tom)</para></listitem>
-<listitem><para>New parameter to set maximum number of open files (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Queries</title>
-<itemizedlist>
-<listitem><para>Statements added by INSERT rules now execute after the INSERT (Jan)</para></listitem>
-<listitem><para>Prevent unadorned relation names in target list (Bruce)</para></listitem>
-<listitem><para>NULLs now sort after all normal values in ORDER BY (Tom)</para></listitem>
-<listitem><para>New IS UNKNOWN, IS NOT UNKNOWN Boolean tests (Tom)</para></listitem>
-<listitem><para>New SHARE UPDATE EXCLUSIVE lock mode (Tom)</para></listitem>
-<listitem><para>New EXPLAIN ANALYZE command that shows run times and row counts (Martijn van Oosterhout)</para></listitem>
-<listitem><para>Fix problem with LIMIT and subqueries (Tom)</para></listitem>
-<listitem><para>Fix for LIMIT, DISTINCT ON pushed into subqueries (Tom)</para></listitem>
-<listitem><para>Fix nested EXCEPT/INTERSECT (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Schema Manipulation</title>
-<itemizedlist>
-<listitem><para>Fix SERIAL in temporary tables (Bruce)</para></listitem>
-<listitem><para>Allow temporary sequences (Bruce)</para></listitem>
-<listitem><para>Sequences now use int8 internally (Tom)</para></listitem>
-<listitem><para>New SERIAL8 creates int8 columns with sequences, default still SERIAL4 (Tom)</para></listitem>
-<listitem><para>Make OIDs optional using WITHOUT OIDS (Tom)</para></listitem>
-<listitem><para>Add %TYPE syntax to CREATE TYPE (Ian Lance Taylor)</para></listitem>
-<listitem><para>Add ALTER TABLE / DROP CONSTRAINT for CHECK constraints (Christopher Kings-Lynne)</para></listitem>
-<listitem><para>New CREATE OR REPLACE FUNCTION to alter existing function (preserving the function OID) (Gavin Sherry)</para></listitem>
-<listitem><para>Add ALTER TABLE / ADD [ UNIQUE | PRIMARY ] (Christopher Kings-Lynne)</para></listitem>
-<listitem><para>Allow column renaming in views</para></listitem>
-<listitem><para>Make ALTER TABLE / RENAME COLUMN update column names of indexes (Brent Verner)</para></listitem>
-<listitem><para>Fix for ALTER TABLE / ADD CONSTRAINT ... CHECK with inherited tables (Stephan Szabo)</para></listitem>
-<listitem><para>ALTER TABLE RENAME update foreign-key trigger arguments correctly (Brent Verner)</para></listitem>
-<listitem><para>DROP AGGREGATE and COMMENT ON AGGREGATE now accept an aggtype (Tom)</para></listitem>
-<listitem><para>Add automatic return type data casting for SQL functions (Tom)</para></listitem>
-<listitem><para>Allow GiST indexes to handle NULLs and multikey indexes (Oleg Bartunov, Teodor Sigaev, Tom)</para></listitem>
-<listitem><para>Enable partial indexes (Martijn van Oosterhout)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Utility Commands</title>
-<itemizedlist>
-<listitem><para>Add RESET ALL, SHOW ALL (Marko Kreen)</para></listitem>
-<listitem><para>CREATE/ALTER USER/GROUP now allow options in any order (Vince)</para></listitem>
-<listitem><para>Add LOCK A, B, C functionality (Neil Padgett)</para></listitem>
-<listitem><para>New ENCRYPTED/UNENCRYPTED option to CREATE/ALTER USER (Bruce)</para></listitem>
-<listitem><para>New light-weight VACUUM does not lock table; old semantics are available as VACUUM FULL (Tom)</para></listitem>
-<listitem><para>Disable COPY TO/FROM on views (Bruce)</para></listitem>
-<listitem><para>COPY DELIMITERS string must be exactly one character (Tom)</para></listitem>
-<listitem><para>VACUUM warning about index tuples fewer than heap now only appears when appropriate (Martijn van Oosterhout)</para></listitem>
-<listitem><para>Fix privilege checks for CREATE INDEX (Tom)</para></listitem>
-<listitem><para>Disallow inappropriate use of CREATE/DROP INDEX/TRIGGER/VIEW (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Data Types and Functions</title>
-<itemizedlist>
-<listitem><para>SUM(), AVG(), COUNT() now uses int8 internally for speed (Tom)</para></listitem>
-<listitem><para>Add convert(), convert2() (Tatsuo)</para></listitem>
-<listitem><para>New function bit_length() (Peter E)</para></listitem>
-<listitem><para>Make the "n" in CHAR(n)/VARCHAR(n) represents letters, not bytes (Tatsuo)</para></listitem>
-<listitem><para>CHAR(), VARCHAR() now reject strings that are too long (Peter E)</para></listitem>
-<listitem><para>BIT VARYING now rejects bit strings that are too long (Peter E)</para></listitem>
-<listitem><para>BIT now rejects bit strings that do not match declared size (Peter E)</para></listitem>
-<listitem><para>INET, CIDR text conversion functions (Alex Pilosov)</para></listitem>
-<listitem><para>INET, CIDR operators &lt;&lt; and &lt;&lt;= indexable (Alex Pilosov)</para></listitem>
-<listitem><para>Bytea \### now requires valid three digit octal number</para></listitem>
-<listitem><para>Bytea comparison improvements, now supports =, &lt;&gt;, &gt;, &gt;=, &lt;, and &lt;=</para></listitem>
-<listitem><para>Bytea now supports B-tree indexes</para></listitem>
-<listitem><para>Bytea now supports LIKE, LIKE...ESCAPE, NOT LIKE, NOT LIKE...ESCAPE</para></listitem>
-<listitem><para>Bytea now supports concatenation</para></listitem>
-<listitem><para>New bytea functions: position, substring, trim, btrim, and length</para></listitem>
-<listitem><para>New encode() function mode, "escaped", converts minimally escaped bytea to/from text</para></listitem>
-<listitem><para>Add pg_database_encoding_max_length() (Tatsuo)</para></listitem>
-<listitem><para>Add pg_client_encoding() function (Tatsuo)</para></listitem>
-<listitem><para>now() returns time with millisecond precision (Thomas)</para></listitem>
-<listitem><para>New TIMESTAMP WITHOUT TIMEZONE data type (Thomas)</para></listitem>
-<listitem><para>Add ISO date/time specification with "T", yyyy-mm-ddThh:mm:ss (Thomas)</para></listitem>
-<listitem><para>New xid/int comparison functions (Hiroshi)</para></listitem>
-<listitem><para>Add precision to TIME, TIMESTAMP, and INTERVAL data types (Thomas)</para></listitem>
-<listitem><para>Modify type coercion logic to attempt binary-compatible functions first (Tom)</para></listitem>
-<listitem><para>New encode() function installed by default (Marko Kreen)</para></listitem>
-<listitem><para>Improved to_*() conversion functions (Karel Zak)</para></listitem>
-<listitem><para>Optimize LIKE/ILIKE when using single-byte encodings (Tatsuo)</para></listitem>
-<listitem><para>New functions in contrib/pgcrypto: crypt(), hmac(), encrypt(), gen_salt() (Marko Kreen)</para></listitem>
-<listitem><para>Correct description of translate() function (Bruce)</para></listitem>
-<listitem><para>Add INTERVAL argument for SET TIME ZONE (Thomas)</para></listitem>
-<listitem><para>Add INTERVAL YEAR TO MONTH (etc.) syntax (Thomas)</para></listitem>
-<listitem><para>Optimize length functions when using single-byte encodings (Tatsuo)</para></listitem>
-<listitem><para>Fix path_inter, path_distance, path_length, dist_ppath to handle closed paths (Curtis Barrett, Tom)</para></listitem>
-<listitem><para>octet_length(text) now returns non-compressed length (Tatsuo, Bruce)</para></listitem>
-<listitem><para>Handle "July" full name in date/time literals (Greg Sabino Mullane)</para></listitem>
-<listitem><para>Some datatype() function calls now evaluated differently</para></listitem>
-<listitem><para>Add support for Julian and ISO time specifications (Thomas)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Internationalization</title>
-<itemizedlist>
-<listitem><para>National language support in psql, <application>pg_dump</>, libpq, and server (Peter E)</para></listitem>
-<listitem><para>Message translations in Chinese (simplified, traditional), Czech, French, German, Hungarian, Russian, Swedish (Peter E, Serguei A. Mokhov, Karel Zak, Weiping He, Zhenbang Wei, Kovacs Zoltan)</para></listitem>
-<listitem><para>Make trim, ltrim, rtrim, btrim, lpad, rpad, translate multibyte aware (Tatsuo)</para></listitem>
-<listitem><para>Add LATIN5,6,7,8,9,10 support (Tatsuo)</para></listitem>
-<listitem><para>Add ISO 8859-5,6,7,8 support (Tatsuo)</para></listitem>
-<listitem><para>Correct LATIN5 to mean ISO-8859-9, not ISO-8859-5 (Tatsuo)</para></listitem>
-<listitem><para>Make mic2ascii() non-ASCII aware (Tatsuo)</para></listitem>
-<listitem><para>Reject invalid multibyte character sequences (Tatsuo)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title><application>PL/pgSQL</></title>
-<itemizedlist>
-<listitem><para>Now uses portals for SELECT loops, allowing huge result sets (Jan)</para></listitem>
-<listitem><para>CURSOR and REFCURSOR support (Jan)</para></listitem>
-<listitem><para>Can now return open cursors (Jan)</para></listitem>
-<listitem><para>Add ELSEIF (Klaus Reger)</para></listitem>
-<listitem><para>Improve PL/pgSQL error reporting, including location of error (Tom)</para></listitem>
-<listitem><para>Allow IS or FOR key words in cursor declaration, for compatibility (Bruce)</para></listitem>
-<listitem><para>Fix for SELECT ... FOR UPDATE (Tom)</para></listitem>
-<listitem><para>Fix for PERFORM returning multiple rows (Tom)</para></listitem>
-<listitem><para>Make PL/pgSQL use the server's type coercion code (Tom)</para></listitem>
-<listitem><para>Memory leak fix (Jan, Tom)</para></listitem>
-<listitem><para>Make trailing semicolon optional (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>PL/Perl</title>
-<itemizedlist>
-<listitem><para>New untrusted PL/Perl (Alex Pilosov)</para></listitem>
-<listitem><para>PL/Perl is now built on some platforms even if libperl is not shared (Peter E)</para></listitem>
-</itemizedlist>
-   </sect3>
-
-  <sect3>
-   <title>PL/Tcl</title>
-<itemizedlist>
-<listitem><para>Now reports errorInfo (Vsevolod Lobko)</para></listitem>
-<listitem><para>Add spi_lastoid function ([email protected])</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>PL/Python</title>
-<itemizedlist>
-<listitem><para>...is new (Andrew Bosma)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title><application>psql</></title>
-<itemizedlist>
-<listitem><para>\d displays indexes in unique, primary groupings (Christopher Kings-Lynne)</para></listitem>
-<listitem><para>Allow trailing semicolons in backslash commands (Greg Sabino Mullane)</para></listitem>
-<listitem><para>Read password from /dev/tty if possible</para></listitem>
-<listitem><para>Force new password prompt when changing user and database (Tatsuo, Tom)</para></listitem>
-<listitem><para>Format the correct number of columns for Unicode (Patrice)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title><application>libpq</></title>
-<itemizedlist>
-<listitem><para>New function PQescapeString() to escape quotes in command strings (Florian Weimer)</para></listitem>
-<listitem><para>New function PQescapeBytea() escapes binary strings for use as SQL string literals</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>JDBC</title>
-<itemizedlist>
-<listitem><para>Return OID of INSERT (Ken K)</para></listitem>
-<listitem><para>Handle more data types (Ken K)</para></listitem>
-<listitem><para>Handle single quotes and newlines in strings (Ken K)</para></listitem>
-<listitem><para>Handle NULL variables (Ken K)</para></listitem>
-<listitem><para>Fix for time zone handling (Barry Lind)</para></listitem>
-<listitem><para>Improved Druid support</para></listitem>
-<listitem><para>Allow eight-bit characters with non-multibyte server (Barry Lind)</para></listitem>
-<listitem><para>Support BIT, BINARY types (Ned Wolpert)</para></listitem>
-<listitem><para>Reduce memory usage (Michael Stephens, Dave Cramer)</para></listitem>
-<listitem><para>Update DatabaseMetaData (Peter E)</para></listitem>
-<listitem><para>Add DatabaseMetaData.getCatalogs() (Peter E)</para></listitem>
-<listitem><para>Encoding fixes (Anders Bengtsson)</para></listitem>
-<listitem><para>Get/setCatalog methods (Jason Davies)</para></listitem>
-<listitem><para>DatabaseMetaData.getColumns() now returns column defaults (Jason Davies)</para></listitem>
-<listitem><para>DatabaseMetaData.getColumns() performance improvement (Jeroen van Vianen)</para></listitem>
-<listitem><para>Some JDBC1 and JDBC2 merging (Anders Bengtsson)</para></listitem>
-<listitem><para>Transaction performance improvements (Barry Lind)</para></listitem>
-<listitem><para>Array fixes (Greg Zoller)</para></listitem>
-<listitem><para>Serialize addition </para></listitem>
-<listitem><para>Fix batch processing (Rene Pijlman)</para></listitem>
-<listitem><para>ExecSQL method reorganization (Anders Bengtsson)</para></listitem>
-<listitem><para>GetColumn() fixes (Jeroen van Vianen)</para></listitem>
-<listitem><para>Fix isWriteable() function (Rene Pijlman)</para></listitem>
-<listitem><para>Improved passage of JDBC2 conformance tests (Rene Pijlman)</para></listitem>
-<listitem><para>Add bytea type capability (Barry Lind)</para></listitem>
-<listitem><para>Add isNullable() (Rene Pijlman)</para></listitem>
-<listitem><para>JDBC date/time test suite fixes (Liam Stewart)</para></listitem>
-<listitem><para>Fix for SELECT 'id' AS xxx FROM table (Dave Cramer)</para></listitem>
-<listitem><para>Fix DatabaseMetaData to show precision properly (Mark Lillywhite)</para></listitem>
-<listitem><para>New getImported/getExported keys (Jason Davies)</para></listitem>
-<listitem><para>MD5 password encryption support (Jeremy Wohl)</para></listitem>
-<listitem><para>Fix to actually use type cache (Ned Wolpert)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>ODBC</title>
-<itemizedlist>
-<listitem><para>Remove query size limit (Hiroshi)</para></listitem>
-<listitem><para>Remove text field size limit (Hiroshi)</para></listitem>
-<listitem><para>Fix for SQLPrimaryKeys in multibyte mode (Hiroshi)</para></listitem>
-<listitem><para>Allow ODBC procedure calls (Hiroshi)</para></listitem>
-<listitem><para>Improve boolean handing (Aidan Mountford)</para></listitem>
-<listitem><para>Most configuration options now settable via DSN (Hiroshi)</para></listitem>
-<listitem><para>Multibyte, performance fixes (Hiroshi)</para></listitem>
-<listitem><para>Allow driver to be used with iODBC or unixODBC (Peter E)</para></listitem>
-<listitem><para>MD5 password encryption support (Bruce)</para></listitem>
-<listitem><para>Add more compatibility functions to odbc.sql (Peter E)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title><application>ECPG</></title>
-<itemizedlist>
-<listitem><para>EXECUTE ... INTO implemented (Christof Petig)</para></listitem>
-<listitem><para>Multiple row descriptor support (e.g. CARDINALITY) (Christof Petig)</para></listitem>
-<listitem><para>Fix for GRANT parameters (Lee Kindness)</para></listitem>
-<listitem><para>Fix INITIALLY DEFERRED bug</para></listitem>
-<listitem><para>Various bug fixes (Michael, Christof Petig)</para></listitem>
-<listitem><para>Auto allocation for indicator variable arrays (int *ind_p=NULL)</para></listitem>
-<listitem><para>Auto allocation for string arrays (char **foo_pp=NULL)</para></listitem>
-<listitem><para>ECPGfree_auto_mem fixed</para></listitem>
-<listitem><para>All function names with external linkage are now prefixed by ECPG</para></listitem>
-<listitem><para>Fixes for arrays of structures (Michael)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Misc. Interfaces</title>
-<itemizedlist>
-<listitem><para>Python fix fetchone() (Gerhard Haring)</para></listitem>
-<listitem><para>Use UTF, Unicode in Tcl where appropriate (Vsevolod Lobko, Reinhard Max)</para></listitem>
-<listitem><para>Add Tcl COPY TO/FROM (ljb)</para></listitem>
-<listitem><para>Prevent output of default index op class in <application>pg_dump</> (Tom)</para></listitem>
-<listitem><para>Fix libpgeasy memory leak (Bruce)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Build and Install</title>
-<itemizedlist>
-<listitem><para>Configure, dynamic loader, and shared library fixes (Peter E)</para></listitem>
-<listitem><para>Fixes in QNX 4 port (Bernd Tegge)</para></listitem>
-<listitem><para>Fixes in Cygwin and Windows ports (Jason Tishler, Gerhard Haring, Dmitry Yurtaev, Darko Prenosil, Mikhail Terekhov)</para></listitem>
-<listitem><para>Fix for Windows socket communication failures (Magnus, Mikhail Terekhov)</para></listitem>
-<listitem><para>Hurd compile fix (Oliver Elphick)</para></listitem>
-<listitem><para>BeOS fixes (Cyril Velter)</para></listitem>
-<listitem><para>Remove configure --enable-unicode-conversion, now enabled by multibyte (Tatsuo)</para></listitem>
-<listitem><para>AIX fixes (Tatsuo, Andreas)</para></listitem>
-<listitem><para>Fix parallel make (Peter E)</para></listitem>
-<listitem><para>Install SQL language manual pages into OS-specific directories (Peter E)</para></listitem>
-<listitem><para>Rename config.h to pg_config.h (Peter E)</para></listitem>
-<listitem><para>Reorganize installation layout of header files (Peter E)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Source Code</title>
-<itemizedlist>
-<listitem><para>Remove SEP_CHAR (Bruce)</para></listitem>
-<listitem><para>New GUC hooks (Tom)</para></listitem>
-<listitem><para>Merge GUC and command line handling (Marko Kreen)</para></listitem>
-<listitem><para>Remove EXTEND INDEX (Martijn van Oosterhout, Tom)</para></listitem>
-<listitem><para>New pgjindent utility to indent java code (Bruce)</para></listitem>
-<listitem><para>Remove define of true/false when compiling under C++ (Leandro Fanzone, Tom)</para></listitem>
-<listitem><para>pgindent fixes (Bruce, Tom)</para></listitem>
-<listitem><para>Replace strcasecmp() with strcmp() where appropriate (Peter E)</para></listitem>
-<listitem><para>Dynahash portability improvements (Tom)</para></listitem>
-<listitem><para>Add 'volatile' usage in spinlock structures</para></listitem>
-<listitem><para>Improve signal handling logic (Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Contrib</title>
-<itemizedlist>
-<listitem><para>New contrib/rtree_gist (Oleg Bartunov, Teodor Sigaev)</para></listitem>
-<listitem><para>New contrib/tsearch full-text indexing (Oleg, Teodor Sigaev)</para></listitem>
-<listitem><para>Add contrib/dblink for remote database access (Joe Conway)</para></listitem>
-<listitem><para>contrib/ora2pg Oracle conversion utility (Gilles Darold)</para></listitem>
-<listitem><para>contrib/xml XML conversion utility (John Gray)</para></listitem>
-<listitem><para>contrib/fulltextindex fixes (Christopher Kings-Lynne)</para></listitem>
-<listitem><para>New contrib/fuzzystrmatch with levenshtein and metaphone, soundex merged (Joe Conway)</para></listitem>
-<listitem><para>Add contrib/intarray boolean queries, binary search, fixes (Oleg Bartunov)</para></listitem>
-<listitem><para>New pg_upgrade utility (Bruce)</para></listitem>
-<listitem><para>Add new pg_resetxlog options (Bruce, Tom)</para></listitem>
-</itemizedlist>
-  </sect3>
- </sect2>
-</sect1>
-
-
- <sect1 id="release-7-1-3">
-  <title>Release 7.1.3</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2001-08-15</simpara>
-  </note>
-
-  <sect2>
-   <title>Migration to Version 7.1.3</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those running
-    7.1.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Remove unused WAL segments of large transactions (Tom)
-Multiaction rule fix (Tom)
-PL/pgSQL memory allocation fix (Jan)
-VACUUM buffer fix (Tom)
-Regression test fixes (Tom)
-pg_dump fixes for GRANT/REVOKE/comments on views, user-defined types (Tom)
-Fix subselects with DISTINCT ON or LIMIT (Tom)
-BeOS fix
-Disable COPY TO/FROM a view (Tom)
-Cygwin build (Jason Tishler)
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="release-7-1-2">
-  <title>Release 7.1.2</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2001-05-11</simpara>
-  </note>
-
-  <para>
-   This has one fix from 7.1.1.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.1.2</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those running
-    7.1.X.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Fix PL/pgSQL SELECTs when returning no rows
-Fix for psql backslash core dump
-Referential integrity privilege fix
-Optimizer fixes
-pg_dump cleanups
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="release-7-1-1">
-  <title>Release 7.1.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2001-05-05</simpara>
-  </note>
-
-  <para>
-   This has a variety of fixes from 7.1.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.1.1</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those running
-    7.1.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Fix for numeric MODULO operator (Tom)
-pg_dump fixes (Philip)
-pg_dump can dump 7.0 databases (Philip)
-readline 4.2 fixes (Peter E)
-JOIN fixes (Tom)
-AIX, MSWIN, VAX, N32K fixes (Tom)
-Multibytes fixes (Tom)
-Unicode fixes (Tatsuo)
-Optimizer improvements (Tom)
-Fix for whole rows in functions (Tom)
-Fix for pg_ctl and option strings with spaces (Peter E)
-ODBC fixes (Hiroshi)
-EXTRACT can now take string argument (Thomas)
-Python fixes (Darcy)
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="release-7-1">
-  <title>Release 7.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2001-04-13</simpara>
-  </note>
-
-  <para>
-       This release focuses on removing limitations that have existed in the
-       <productname>PostgreSQL</productname> code for many years.
-  </para>
-
-  <para>
-   Major changes in this release:
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term>
-      Write-ahead Log (WAL)
-    </term>
-    <listitem>
-     <para>
-To maintain database consistency in case of an operating system crash,
-previous releases of <productname>PostgreSQL</productname> have forced
-all data modifications to disk before each transaction commit.  With
-WAL, only one log file must be flushed to disk, greatly improving
-performance.  If you have been using -F in previous releases to
-disable disk flushes, you might want to consider discontinuing its use.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-      TOAST
-    </term>
-    <listitem>
-     <para>
-      TOAST - Previous releases had a compiled-in row length limit,
-typically 8k - 32k. This limit made storage of long text fields
-difficult.  With TOAST, long rows of any length can be stored with good
-performance.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-      Outer Joins
-    </term>
-    <listitem>
-     <para>
-We now support outer joins.  The UNION/NOT IN
-workaround for outer joins is no longer required.  We use the SQL92
-outer join syntax.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-      Function Manager
-    </term>
-    <listitem>
-     <para>
-The previous C function manager did not
-handle null values properly, nor did it support 64-bit <acronym>CPU</acronym>'s (Alpha).  The new
-function manager does.  You can continue using your old custom
-functions, but you might want to rewrite them in the future to use the new
-function manager call interface.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-      Complex Queries
-    </term>
-    <listitem>
-     <para>
-A large number of complex queries that were
-unsupported in previous releases now work.  Many combinations of views,
-aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables
-now work properly. Inherited tables are now accessed by default.
-Subqueries in FROM are now supported.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
-  <sect2>
-   <title>Migration to Version 7.1</title>
-
-   <para>
-       A dump/restore using pg_dump is required for those wishing to migrate
-       data from any previous release.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Bug Fixes
----------
-Many multibyte/Unicode/locale fixes (Tatsuo and others)
-More reliable ALTER TABLE RENAME (Tom)
-Kerberos V fixes (David Wragg)
-Fix for INSERT INTO...SELECT where targetlist has subqueries (Tom)
-Prompt username/password on standard error (Bruce)
-Large objects inv_read/inv_write fixes (Tom)
-Fixes for to_char(), to_date(), to_ascii(), and to_timestamp() (Karel,
-   Daniel Baldoni)
-Prevent query expressions from leaking memory (Tom)
-Allow UPDATE of arrays elements (Tom)
-Wake up lock waiters during cancel (Hiroshi)
-Fix rare cursor crash when using hash join (Tom)
-Fix for DROP TABLE/INDEX in rolled-back transaction (Hiroshi)
-Fix psql crash from \l+ if MULTIBYTE enabled (Peter E)
-Fix truncation of rule names during CREATE VIEW (Ross Reedstrom)
-Fix PL/perl (Alex Kapranoff)
-Disallow LOCK on views (Mark Hollomon)
-Disallow INSERT/UPDATE/DELETE on views (Mark Hollomon)
-Disallow DROP RULE, CREATE INDEX, TRUNCATE on views (Mark Hollomon)
-Allow PL/pgSQL accept non-ASCII identifiers (Tatsuo)
-Allow views to proper handle GROUP BY, aggregates, DISTINCT (Tom)
-Fix rare failure with TRUNCATE command (Tom)
-Allow UNION/INTERSECT/EXCEPT to be used with ALL, subqueries, views,
-   DISTINCT, ORDER BY, SELECT...INTO (Tom)
-Fix parser failures during aborted transactions (Tom)
-Allow temporary relations to properly clean up indexes (Bruce)
-Fix VACUUM problem with moving rows in same page (Tom)
-Modify pg_dump to better handle user-defined items in template1 (Philip)
-Allow LIMIT in VIEW (Tom)
-Require cursor FETCH to honor LIMIT (Tom)
-Allow PRIMARY/FOREIGN Key definitions on inherited columns (Stephan)
-Allow ORDER BY, LIMIT in subqueries (Tom)
-Allow UNION in CREATE RULE (Tom)
-Make ALTER/DROP TABLE rollback-able (Vadim, Tom)
-Store initdb collation in pg_control so collation cannot be changed (Tom)
-Fix INSERT...SELECT with rules (Tom)
-Fix FOR UPDATE inside views and subselects (Tom)
-Fix OVERLAPS operators conform to SQL92 spec regarding NULLs (Tom)
-Fix lpad() and rpad() to handle length less than input string (Tom)
-Fix use of NOTIFY in some rules (Tom)
-Overhaul btree code (Tom)
-Fix NOT NULL use in Pl/pgSQL variables (Tom)
-Overhaul GIST code (Oleg)
-Fix CLUSTER to preserve constraints and column default (Tom)
-Improved deadlock detection handling (Tom)
-Allow multiple SERIAL columns in a table (Tom)
-Prevent occasional index corruption (Vadim)
-
-Enhancements
-------------
-Add OUTER JOINs (Tom)
-Function manager overhaul (Tom)
-Allow ALTER TABLE RENAME on indexes (Tom)
-Improve CLUSTER (Tom)
-Improve ps status display for more platforms (Peter E, Marc)
-Improve CREATE FUNCTION failure message (Ross)
-JDBC improvements (Peter, Travis Bauer, Christopher Cain, William Webber,
-   Gunnar)
-Grand Unified Configuration scheme/GUC.  Many options can now be set in
-   data/postgresql.conf, postmaster/postgres flags, or SET commands (Peter E)
-Improved handling of file descriptor cache (Tom)
-New warning code about auto-created table alias entries (Bruce)
-Overhaul initdb process (Tom, Peter E)
-Overhaul of inherited tables; inherited tables now accessed by default;
-  new ONLY key word prevents it (Chris Bitmead, Tom)
-ODBC cleanups/improvements (Nick Gorham, Stephan Szabo, Zoltan Kovacs,
-   Michael Fork)
-Allow renaming of temp tables (Tom)
-Overhaul memory manager contexts (Tom)
-pg_dumpall uses CREATE USER or CREATE GROUP rather using COPY (Peter E)
-Overhaul pg_dump (Philip Warner)
-Allow pg_hba.conf secondary password file to specify only username (Peter E)
-Allow TEMPORARY or TEMP key word when creating temporary tables (Bruce)
-New memory leak checker (Karel)
-New SET SESSION CHARACTERISTICS (Thomas)
-Allow nested block comments (Thomas)
-Add WITHOUT TIME ZONE type qualifier (Thomas)
-New ALTER TABLE ADD CONSTRAINT (Stephan)
-Use NUMERIC accumulators for INTEGER aggregates (Tom)
-Overhaul aggregate code (Tom)
-New VARIANCE and STDDEV() aggregates
-Improve dependency ordering of pg_dump (Philip)
-New pg_restore command (Philip)
-New pg_dump tar output option (Philip)
-New pg_dump of large objects  (Philip)
-New ESCAPE option to LIKE (Thomas)
-New case-insensitive LIKE - ILIKE (Thomas)
-Allow functional indexes to use binary-compatible type (Tom)
-Allow SQL functions to be used in more contexts (Tom)
-New pg_config utility (Peter E)
-New PL/pgSQL EXECUTE command which allows dynamic SQL and utility statements
-   (Jan)
-New PL/pgSQL GET DIAGNOSTICS statement for SPI value access (Jan)
-New quote_identifiers() and quote_literal() functions (Jan)
-New ALTER TABLE table OWNER TO user command (Mark Hollomon)
-Allow subselects in FROM, i.e. FROM (SELECT ...) [AS] alias (Tom)
-Update PyGreSQL to version 3.1 (D'Arcy)
-Store tables as files named by OID (Vadim)
-New SQL function setval(seq,val,bool) for use in pg_dump (Philip)
-Require DROP VIEW to remove views, no DROP TABLE (Mark)
-Allow DROP VIEW view1, view2 (Mark)
-Allow multiple objects in DROP INDEX, DROP RULE, and DROP TYPE (Tom)
-Allow automatic conversion to/from Unicode (Tatsuo, Eiji)
-New /contrib/pgcrypto hashing functions (Marko Kreen)
-New pg_dumpall --globals-only option (Peter E)
-New CHECKPOINT command for WAL which creates new WAL log file (Vadim)
-New AT TIME ZONE syntax (Thomas)
-Allow location of Unix domain socket to be configurable (David J. MacKenzie)
-Allow postmaster to listen on a specific IP address (David J. MacKenzie)
-Allow socket path name to be specified in hostname by using leading slash
-   (David J. MacKenzie)
-Allow CREATE DATABASE to specify template database (Tom)
-New utility to convert MySQL schema dumps to SQL92 and PostgreSQL (Thomas)
-New /contrib/rserv replication toolkit (Vadim)
-New file format for COPY BINARY (Tom)
-New /contrib/oid2name to map numeric files to table names (B Palmer)
-New "idle in transaction" ps status message (Marc)
-Update to pgaccess 0.98.7 (Constantin Teodorescu)
-pg_ctl now defaults to -w (wait) on shutdown, new -l (log) option
-Add rudimentary dependency checking to pg_dump (Philip)
-
-Types
------
-Fix INET/CIDR type ordering and add new functions (Tom)
-Make OID behave as an unsigned type (Tom)
-Allow BIGINT as synonym for INT8 (Peter E)
-New int2 and int8 comparison operators (Tom)
-New BIT and BIT VARYING types (Adriaan Joubert, Tom, Peter E)
-CHAR() no longer faster than VARCHAR() because of TOAST (Tom)
-New GIST seg/cube examples (Gene Selkov)
-Improved round(numeric) handling (Tom)
-Fix CIDR output formatting (Tom)
-New CIDR abbrev() function (Tom)
-
-Performance
------------
-Write-Ahead Log (WAL) to provide crash recovery with less performance
-   overhead (Vadim)
-ANALYZE stage of VACUUM no longer exclusively locks table (Bruce)
-Reduced file seeks (Denis Perchine)
-Improve BTREE code for duplicate keys (Tom)
-Store all large objects in a single table (Denis Perchine, Tom)
-Improve memory allocation performance (Karel, Tom)
-
-Source Code
------------
-New function manager call conventions (Tom)
-SGI portability fixes (David Kaelbling)
-New configure --enable-syslog option (Peter E)
-New BSDI README (Bruce)
-configure script moved to top level, not /src (Peter E)
-Makefile/configuration/compilation overhaul (Peter E)
-New configure --with-python option (Peter E)
-Solaris cleanups (Peter E)
-Overhaul /contrib Makefiles (Karel)
-New OpenSSL configuration option (Magnus, Peter E)
-AIX fixes (Andreas)
-QNX fixes (Maurizio)
-New heap_open(), heap_openr() API (Tom)
-Remove colon and semi-colon operators (Thomas)
-New pg_class.relkind value for views (Mark Hollomon)
-Rename ichar() to chr() (Karel)
-New documentation for btrim(), ascii(), chr(), repeat() (Karel)
-Fixes for NT/Cygwin (Pete Forman)
-AIX port fixes (Andreas)
-New BeOS port (David Reid, Cyril Velter)
-Add proofreader's changes to docs (Addison-Wesley, Bruce)
-New Alpha spinlock code (Adriaan Joubert, Compaq)
-UnixWare port overhaul (Peter E)
-New Darwin/MacOS X port (Peter Bierman, Bruce Hartzler)
-New FreeBSD Alpha port (Alfred)
-Overhaul shared memory segments (Tom)
-Add IBM S/390 support (Neale Ferguson)
-Moved macmanuf to /contrib (Larry Rosenman)
-Syslog improvements (Larry Rosenman)
-New template0 database that contains no user additions (Tom)
-New /contrib/cube and /contrib/seg GIST sample code (Gene Selkov)
-Allow NetBSD's libedit instead of readline (Peter)
-Improved assembly language source code format (Bruce)
-New contrib/pg_logger
-New --template option to createdb
-New contrib/pg_control utility (Oliver)
-New FreeBSD tools ipc_check, start-scripts/freebsd
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="release-7-0-3">
-  <title>Release 7.0.3</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2000-11-11</simpara>
-  </note>
-
-  <para>
-   This has a variety of fixes from 7.0.2.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.0.3</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those running
-    7.0.*.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Jdbc fixes (Peter)
-Large object fix (Tom)
-Fix lean in COPY WITH OIDS leak (Tom)
-Fix backwards-index-scan (Tom)
-Fix SELECT ... FOR UPDATE so it checks for duplicate keys (Hiroshi)
-Add --enable-syslog to configure (Marc)
-Fix abort transaction at backend exit in rare cases (Tom)
-Fix for psql \l+ when multibyte enabled (Tatsuo)
-Allow PL/pgSQL to accept non ascii identifiers (Tatsuo)
-Make vacuum always flush buffers (Tom)
-Fix to allow cancel while waiting for a lock (Hiroshi)
-Fix for memory allocation problem in user authentication code (Tom)
-Remove bogus use of int4out() (Tom)
-Fixes for multiple subqueries in COALESCE or BETWEEN (Tom)
-Fix for failure of triggers on heap open in certain cases (Jeroen van
-   Vianen)
-Fix for erroneous selectivity of not-equals (Tom)
-Fix for erroneous use of strcmp() (Tom)
-Fix for bug where storage manager accesses items beyond end of file
-   (Tom)
-Fix to include kernel errno message in all smgr elog messages (Tom)
-Fix for '.' not in PATH at build time (SL Baur)
-Fix for out-of-file-descriptors error (Tom)
-Fix to make pg_dump dump 'iscachable' flag for functions (Tom)
-Fix for subselect in targetlist of Append node (Tom)
-Fix for mergejoin plans (Tom)
-Fix TRUNCATE failure on relations with indexes (Tom)
-Avoid database-wide restart on write error (Hiroshi)
-Fix nodeMaterial to honor chgParam by recomputing its output (Tom)
-Fix VACUUM problem with moving chain of update row versions when source
-   and destination of a row version lie on the same page (Tom)
-Fix user.c CommandCounterIncrement (Tom)
-Fix for AM/PM boundary problem in to_char() (Karel Zak)
-Fix TIME aggregate handling (Tom)
-Fix to_char() to avoid coredump on NULL input (Tom)
-Buffer fix (Tom)
-Fix for inserting/copying longer multibyte strings into char() data
-   types (Tatsuo)
-Fix for crash of backend, on abort (Tom)
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="release-7-0-2">
-  <title>Release 7.0.2</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2000-06-05</simpara>
-  </note>
-
-  <para>
-   This is a repackaging of 7.0.1 with added documentation.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 7.0.2</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those running
-    7.*.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Added documentation to tarball.
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="release-7-0-1">
-  <title>Release 7.0.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2000-06-01</simpara>
-  </note>
-
-  <para>
-   This is a cleanup release for 7.0.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 7.0.1</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those running
-    7.0.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Fix many CLUSTER failures (Tom)
-Allow ALTER TABLE RENAME works on indexes (Tom)
-Fix plpgsql to handle datetime-&gt;timestamp and timespan-&gt;interval (Bruce)
-New configure --with-setproctitle switch to use setproctitle() (Marc, Bruce)
-Fix the off by one errors in ResultSet from 6.5.3, and more.
-jdbc ResultSet fixes (Joseph Shraibman)
-optimizer tunings (Tom)
-Fix create user for pgaccess
-Fix for UNLISTEN failure
-IRIX fixes (David Kaelbling)
-QNX fixes (Andreas Kardos)
-Reduce COPY IN lock level (Tom)
-Change libpqeasy to use PQconnectdb() style parameters (Bruce)
-Fix pg_dump to handle OID indexes (Tom)
-Fix small memory leak (Tom)
-Solaris fix for createdb/dropdb (Tatsuo)
-Fix for non-blocking connections (Alfred Perlstein)
-Fix improper recovery after RENAME TABLE failures (Tom)
-Copy pg_ident.conf.sample into /lib directory in install (Bruce)
-Add SJIS UDC (NEC selection IBM kanji) support (Eiji Tokuya)
-Fix too long syslog message (Tatsuo)
-Fix problem with quoted indexes that are too long (Tom)
-JDBC ResultSet.getTimestamp() fix (Gregory Krasnow &amp; Floyd Marinescu)
-ecpg changes (Michael)
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="release-7-0">
-  <title>Release 7.0</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>2000-05-08</simpara>
-  </note>
-
-  <para>
-   This release contains improvements in many areas, demonstrating
-   the continued growth of <productname>PostgreSQL</productname>.
-   There are more improvements and fixes in 7.0 than in any previous
-   release. The developers have confidence that this is the best
-   release yet; we do our best to put out only solid releases, and
-   this one is no exception.
-  </para>
-
-  <para>
-   Major changes in this release:
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term>
-     Foreign Keys
-    </term>
-    <listitem>
-     <para>
-      Foreign keys are now implemented, with the exception of PARTIAL MATCH
-      foreign keys. Many users have been asking for this feature, and we are
-      pleased to offer it.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Optimizer Overhaul
-    </term>
-    <listitem>
-     <para>
-      Continuing on work started a year ago, the optimizer has been
-      improved, allowing better query plan selection and faster performance
-      with less memory usage.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Updated <application>psql</application>
-    </term>
-    <listitem>
-     <para>
-      <application>psql</application>, our interactive terminal monitor, has been
-      updated with a variety of new features. See the <application>psql</application> manual page for details.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     Join Syntax
-    </term>
-    <listitem>
-     <para>
-      SQL92 join syntax is now supported, though only as
-      <literal>INNER JOIN</> for this release. <literal>JOIN</>,
-      <literal>NATURAL JOIN</>, <literal>JOIN</>/<literal>USING</>,
-      and <literal>JOIN</>/<literal>ON</> are available, as are
-      column correlation names.
-     </para>
-    </listitem>
-
-   </varlistentry>
-  </variablelist>
-
-  <sect2>
-   <title>Migration to Version 7.0</title>
-
-   <para>
-    A dump/restore using <application>pg_dump</application>
-    is required for those wishing to migrate data from any
-    previous release of <productname>PostgreSQL</productname>.
-    For those upgrading from 6.5.*, you can instead use
-    <application>pg_upgrade</application> to upgrade to this
-    release; however, a full dump/reload installation is always the
-    most robust method for upgrades.
-   </para>
-
-   <para>
-    Interface and compatibility issues to consider for the new
-    release include:
-   </para>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      The date/time types <type>datetime</type> and
-      <type>timespan</type> have been superseded by the
-      SQL92-defined types <type>timestamp</type> and
-      <type>interval</type>. Although there has been some effort to
-      ease the transition by allowing
-      <productname>PostgreSQL</productname> to recognize
-      the deprecated type names and translate them to the new type
-      names, this mechanism cannot be completely transparent to
-      your existing application.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The optimizer has been substantially improved in the area of
-      query cost estimation. In some cases, this will result in
-      decreased query times as the optimizer makes a better choice
-      for the preferred plan. However, in a small number of cases,
-      usually involving pathological distributions of data, your
-      query times might go up. If you are dealing with large amounts
-      of data, you might want to check your queries to verify
-      performance.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The <acronym>JDBC</acronym> and <acronym>ODBC</acronym>
-      interfaces have been upgraded and extended.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The string function <function>CHAR_LENGTH</function> is now a
-      native function. Previous versions translated this into a call
-      to <function>LENGTH</function>, which could result in
-      ambiguity with other types implementing
-      <function>LENGTH</function> such as the geometric types.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Bug Fixes
----------
-Prevent function calls exceeding maximum number of arguments (Tom)
-Improve CASE construct (Tom)
-Fix SELECT coalesce(f1,0) FROM int4_tbl GROUP BY f1 (Tom)
-Fix SELECT sentence.words[0] FROM sentence GROUP BY sentence.words[0] (Tom)
-Fix GROUP BY scan bug (Tom)
-Improvements in SQL grammar processing (Tom)
-Fix for views involved in INSERT ... SELECT ... (Tom)
-Fix for SELECT a/2, a/2 FROM test_missing_target GROUP BY a/2 (Tom)
-Fix for subselects in INSERT ... SELECT (Tom)
-Prevent INSERT ... SELECT ... ORDER BY (Tom)
-Fixes for relations greater than 2GB, including vacuum
-Improve propagating system table changes to other backends (Tom)
-Improve propagating user table changes to other backends (Tom)
-Fix handling of temp tables in complex situations (Bruce, Tom)
-Allow table locking at table open, improving concurrent reliability (Tom)
-Properly quote sequence names in pg_dump (Ross J. Reedstrom)
-Prevent DROP DATABASE while others accessing
-Prevent any rows from being returned by GROUP BY if no rows processed (Tom)
-Fix SELECT COUNT(1) FROM table WHERE ...' if no rows matching WHERE (Tom)
-Fix pg_upgrade so it works for MVCC (Tom)
-Fix for SELECT ... WHERE x IN (SELECT ... HAVING SUM(x) &gt; 1) (Tom)
-Fix for "f1 datetime DEFAULT 'now'"  (Tom)
-Fix problems with CURRENT_DATE used in DEFAULT (Tom)
-Allow comment-only lines, and ;;; lines too. (Tom)
-Improve recovery after failed disk writes, disk full (Hiroshi)
-Fix cases where table is mentioned in FROM but not joined (Tom)
-Allow HAVING clause without aggregate functions (Tom)
-Fix for "--" comment and no trailing newline, as seen in perl interface
-Improve pg_dump failure error reports (Bruce)
-Allow sorts and hashes to exceed 2GB file sizes (Tom)
-Fix for pg_dump dumping of inherited rules (Tom)
-Fix for NULL handling comparisons (Tom)
-Fix inconsistent state caused by failed CREATE/DROP commands (Hiroshi)
-Fix for dbname with dash
-Prevent DROP INDEX from interfering with other backends (Tom)
-Fix file descriptor leak in verify_password()
-Fix for "Unable to identify an operator =$" problem
-Fix ODBC so no segfault if CommLog and Debug enabled (Dirk Niggemann)
-Fix for recursive exit call (Massimo)
-Fix for extra-long timezones (Jeroen van Vianen)
-Make pg_dump preserve primary key information (Peter E)
-Prevent databases with single quotes (Peter E)
-Prevent DROP DATABASE inside  transaction (Peter E)
-ecpg memory leak fixes (Stephen Birch)
-Fix for SELECT null::text, SELECT int4fac(null) and SELECT 2 + (null) (Tom)
-Y2K timestamp fix (Massimo)
-Fix for VACUUM 'HEAP_MOVED_IN was not expected' errors (Tom)
-Fix for views with tables/columns containing spaces  (Tom)
-Prevent privileges on indexes (Peter E)
-Fix for spinlock stuck problem when error is generated (Hiroshi)
-Fix ipcclean on Linux
-Fix handling of NULL constraint conditions (Tom)
-Fix memory leak in odbc driver (Nick Gorham)
-Fix for privilege check on UNION tables (Tom)
-Fix to allow SELECT 'a' LIKE 'a' (Tom)
-Fix for SELECT 1 + NULL (Tom)
-Fixes to CHAR
-Fix log() on numeric type (Tom)
-Deprecate ':' and ';' operators
-Allow vacuum of temporary tables
-Disallow inherited columns with the same name as new columns
-Recover or force failure when disk space is exhausted (Hiroshi)
-Fix INSERT INTO ... SELECT with AS columns matching result columns
-Fix INSERT ... SELECT ... GROUP BY groups by target columns not source columns (Tom)
-Fix CREATE TABLE test (a char(5) DEFAULT text '', b int4) with INSERT (Tom)
-Fix UNION with LIMIT
-Fix CREATE TABLE x AS SELECT 1 UNION SELECT 2
-Fix CREATE TABLE test(col char(2) DEFAULT user)
-Fix mismatched types in CREATE TABLE ... DEFAULT
-Fix SELECT * FROM pg_class where oid in (0,-1)
-Fix SELECT COUNT('asdf') FROM pg_class WHERE oid=12
-Prevent user who can create databases can modifying pg_database table (Peter E)
-Fix btree to give a useful elog when key &gt; 1/2 (page - overhead) (Tom)
-Fix INSERT of 0.0 into DECIMAL(4,4) field (Tom)
-
-Enhancements
-------------
-New CLI interface include file sqlcli.h, based on SQL3/SQL98
-Remove all limits on query length, row length limit still exists (Tom)
-Update jdbc protocol to 2.0 (Jens Glaser <email>[email protected]</email>)
-Add TRUNCATE command to quickly truncate relation (Mike Mascari)
-Fix to give super user and createdb user proper update catalog rights (Peter E)
-Allow ecpg bool variables to have NULL values (Christof)
-Issue ecpg error if NULL value for variable with no NULL indicator (Christof)
-Allow ^C to cancel COPY command (Massimo)
-Add SET FSYNC and SHOW PG_OPTIONS commands(Massimo)
-Function name overloading for dynamically-loaded C functions (Frankpitt)
-Add CmdTuples() to libpq++(Vince)
-New CREATE CONSTRAINT TRIGGER and SET CONSTRAINTS commands(Jan)
-Allow CREATE FUNCTION/WITH clause to be used for all language types
-configure --enable-debug adds -g (Peter E)
-configure --disable-debug removes -g (Peter E)
-Allow more complex default expressions (Tom)
-First real FOREIGN KEY constraint trigger functionality (Jan)
-Add FOREIGN KEY ... MATCH FULL ... ON DELETE CASCADE (Jan)
-Add FOREIGN KEY ... MATCH &lt;unspecified&gt; referential actions (Don Baccus)
-Allow WHERE restriction on ctid (physical heap location) (Hiroshi)
-Move pginterface from contrib to interface directory, rename to pgeasy (Bruce)
-Change pgeasy connectdb() parameter ordering (Bruce)
-Require SELECT DISTINCT target list to have all ORDER BY columns (Tom)
-Add Oracle's COMMENT ON command (Mike Mascari <email>[email protected]</email>)
-libpq's PQsetNoticeProcessor function now returns previous hook(Peter E)
-Prevent PQsetNoticeProcessor from being set to NULL (Peter E)
-Make USING in COPY optional (Bruce)
-Allow subselects in the target list (Tom)
-Allow subselects on the left side of comparison operators (Tom)
-New parallel regression test (Jan)
-Change backend-side COPY to write files with permissions 644 not 666 (Tom)
-Force permissions on PGDATA directory to be secure, even if it exists (Tom)
-Added psql LASTOID variable to return last inserted oid (Peter E)
-Allow concurrent vacuum and remove pg_vlock vacuum lock file (Tom)
-Add privilege check for vacuum (Peter E)
-New libpq functions to allow asynchronous connections: PQconnectStart(),
-  PQconnectPoll(), PQresetStart(), PQresetPoll(), PQsetenvStart(),
-  PQsetenvPoll(), PQsetenvAbort (Ewan Mellor)
-New libpq PQsetenv() function (Ewan Mellor)
-create/alter user extension (Peter E)
-New postmaster.pid and postmaster.opts under $PGDATA (Tatsuo)
-New scripts for create/drop user/db (Peter E)
-Major psql overhaul (Peter E)
-Add const to libpq interface (Peter E)
-New libpq function PQoidValue (Peter E)
-Show specific non-aggregate causing problem with GROUP BY (Tom)
-Make changes to pg_shadow recreate pg_pwd file (Peter E)
-Add aggregate(DISTINCT ...) (Tom)
-Allow flag to control COPY input/output of NULLs (Peter E)
-Make postgres user have a password by default (Peter E)
-Add CREATE/ALTER/DROP GROUP (Peter E)
-All administration scripts now support --long options (Peter E, Karel)
-Vacuumdb script now supports --all option (Peter E)
-ecpg new portable FETCH syntax
-Add ecpg EXEC SQL IFDEF, EXEC SQL IFNDEF, EXEC SQL ELSE, EXEC SQL ELIF
-       and EXEC SQL ENDIF directives
-Add pg_ctl script to control backend start-up (Tatsuo)
-Add postmaster.opts.default file to store start-up flags (Tatsuo)
-Allow --with-mb=SQL_ASCII
-Increase maximum number of index keys to 16 (Bruce)
-Increase maximum number of function arguments to 16 (Bruce)
-Allow configuration of maximum number of index keys and arguments (Bruce)
-Allow unprivileged users to change their passwords (Peter E)
-Password authentication enabled; required for new users (Peter E)
-Disallow dropping a user who owns a database (Peter E)
-Change initdb option --with-mb to --enable-multibyte
-Add option for initdb to prompts for superuser password (Peter E)
-Allow complex type casts like col::numeric(9,2) and col::int2::float8 (Tom)
-Updated user interfaces on initdb, initlocation, pg_dump, ipcclean (Peter E)
-New pg_char_to_encoding() and pg_encoding_to_char() functions (Tatsuo)
-libpq non-blocking mode (Alfred Perlstein)
-Improve conversion of types in casts that don't specify a length
-New plperl internal programming language (Mark Hollomon)
-Allow COPY IN to read file that do not end with a newline (Tom)
-Indicate when long identifiers are truncated (Tom)
-Allow aggregates to use type equivalency (Peter E)
-Add Oracle's to_char(), to_date(), to_datetime(), to_timestamp(), to_number()
-       conversion functions (Karel Zak &lt;[email protected]&gt;)
-Add SELECT DISTINCT ON (expr [, expr ...]) targetlist ... (Tom)
-Check to be sure ORDER BY is compatible with the DISTINCT operation (Tom)
-Add NUMERIC and int8 types to ODBC
-Improve EXPLAIN results for Append, Group, Agg, Unique (Tom)
-Add ALTER TABLE ... ADD FOREIGN KEY (Stephan Szabo)
-Allow SELECT .. FOR UPDATE in PL/pgSQL (Hiroshi)
-Enable backward sequential scan even after reaching EOF (Hiroshi)
-Add btree indexing of boolean values, &gt;= and &lt;= (Don Baccus)
-Print current line number when COPY FROM fails (Massimo)
-Recognize POSIX time zone e.g. "PST+8" and "GMT-8" (Thomas)
-Add DEC as synonym for DECIMAL (Thomas)
-Add SESSION_USER as SQL92 key word, same as CURRENT_USER (Thomas)
-Implement SQL92 column aliases (aka correlation names) (Thomas)
-Implement SQL92 join syntax (Thomas)
-Make INTERVAL reserved word allowed as a column identifier (Thomas)
-Implement REINDEX command (Hiroshi)
-Accept ALL in aggregate function SUM(ALL col) (Tom)
-Prevent GROUP BY from using column aliases (Tom)
-New psql \encoding option (Tatsuo)
-Allow PQrequestCancel() to terminate when in waiting-for-lock state (Hiroshi)
-Allow negation of a negative number in all cases
-Add ecpg descriptors (Christof, Michael)
-Allow CREATE VIEW v AS SELECT f1::char(8) FROM tbl
-Allow casts with length, like foo::char(8)
-New libpq functions PQsetClientEncoding(), PQclientEncoding() (Tatsuo)
-Add support for SJIS user defined characters (Tatsuo)
-Larger views/rules supported
-Make libpq's PQconndefaults() thread-safe (Tom)
-Disable // as comment to be ANSI conforming, should use -- (Tom)
-Allow column aliases on views CREATE VIEW name (collist)
-Fixes for views with subqueries (Tom)
-Allow UPDATE table SET fld = (SELECT ...) (Tom)
-SET command options no longer require quotes
-Update pgaccess to 0.98.6
-New SET SEED command
-New pg_options.sample file
-New SET FSYNC command (Massimo)
-Allow pg_descriptions when creating tables
-Allow pg_descriptions when creating types, columns, and functions
-Allow psql \copy to allow delimiters (Peter E)
-Allow psql to print nulls as distinct from "" [null] (Peter E)
-
-Types
------
-Many array fixes (Tom)
-Allow bare column names to be subscripted as arrays (Tom)
-Improve type casting of int and float constants (Tom)
-Cleanups for int8 inputs, range checking, and type conversion (Tom)
-Fix for SELECT timespan('21:11:26'::time) (Tom)
-netmask('x.x.x.x/0') is 255.255.255.255 instead of 0.0.0.0 (Oleg Sharoiko)
-Add btree index on NUMERIC (Jan)
-Perl fix for large objects containing NUL characters (Douglas Thomson)
-ODBC fix for large objects (free)
-Fix indexing of cidr data type
-Fix for Ethernet MAC addresses (macaddr type) comparisons
-Fix for date/time types when overflows happened in computations (Tom)
-Allow array on int8 (Peter E)
-Fix for rounding/overflow of NUMERIC type, like NUMERIC(4,4) (Tom)
-Allow NUMERIC arrays
-Fix bugs in NUMERIC ceil() and floor() functions (Tom)
-Make char_length()/octet_length including trailing blanks (Tom)
-Made abstime/reltime use int4 instead of time_t (Peter E)
-New lztext data type for compressed text fields
-Revise code to handle coercion of int and float constants (Tom)
-Start at new code to implement a BIT and BIT VARYING type (Adriaan Joubert)
-NUMERIC now accepts scientific notation (Tom)
-NUMERIC to int4 rounds (Tom)
-Convert float4/8 to NUMERIC properly (Tom)
-Allow type conversion with NUMERIC (Thomas)
-Make ISO date style (2000-02-16 09:33) the default (Thomas)
-Add NATIONAL CHAR [ VARYING ] (Thomas)
-Allow NUMERIC round and trunc to accept negative scales (Tom)
-New TIME WITH TIME ZONE type (Thomas)
-Add MAX()/MIN() on time type (Thomas)
-Add abs(), mod(), fac() for int8 (Thomas)
-Rename functions to round(), sqrt(), cbrt(), pow() for float8 (Thomas)
-Add transcendental math functions (e.g. sin(), acos()) for float8 (Thomas)
-Add exp() and ln() for NUMERIC type
-Rename NUMERIC power() to pow() (Thomas)
-Improved TRANSLATE() function (Edwin Ramirez, Tom)
-Allow X=-Y operators  (Tom)
-Allow SELECT float8(COUNT(*))/(SELECT COUNT(*) FROM t) FROM t GROUP BY f1; (Tom)
-Allow LOCALE to use indexes in regular expression searches (Tom)
-Allow creation of functional indexes to use default types
-
-Performance
------------
-Prevent exponential space consumption with many AND's and OR's (Tom)
-Collect attribute selectivity values for system columns (Tom)
-Reduce memory usage of aggregates (Tom)
-Fix for LIKE optimization to use indexes with multibyte encodings (Tom)
-Fix r-tree index optimizer selectivity (Thomas)
-Improve optimizer selectivity computations and functions (Tom)
-Optimize btree searching for cases where many equal keys exist (Tom)
-Enable fast LIKE index processing only if index present (Tom)
-Re-use free space on index pages with duplicates (Tom)
-Improve hash join processing (Tom)
-Prevent descending sort if result is already sorted(Hiroshi)
-Allow commuting of index scan query qualifications (Tom)
-Prefer index scans in cases where ORDER BY/GROUP BY is required (Tom)
-Allocate large memory requests in fix-sized chunks for performance (Tom)
-Fix vacuum's performance by reducing memory allocation requests (Tom)
-Implement constant-expression simplification (Bernard Frankpitt, Tom)
-Use secondary columns to be used to determine start of index scan (Hiroshi)
-Prevent quadruple use of disk space when doing internal sorting (Tom)
-Faster sorting by calling fewer functions (Tom)
-Create system indexes to match all system caches (Bruce, Hiroshi)
-Make system caches use system indexes (Bruce)
-Make all system indexes unique (Bruce)
-Improve pg_statistics management for VACUUM speed improvement (Tom)
-Flush backend cache less frequently (Tom, Hiroshi)
-COPY now reuses previous memory allocation, improving performance (Tom)
-Improve optimization cost estimation (Tom)
-Improve optimizer estimate of range queries x &gt; lowbound AND x &lt; highbound (Tom)
-Use DNF instead of CNF where appropriate (Tom, Taral)
-Further cleanup for OR-of-AND WHERE-clauses (Tom)
-Make use of index in OR clauses (x = 1 AND y = 2) OR (x = 2 AND y = 4) (Tom)
-Smarter optimizer computations for random index page access (Tom)
-New SET variable to control optimizer costs (Tom)
-Optimizer queries based on LIMIT, OFFSET, and EXISTS qualifications (Tom)
-Reduce optimizer internal housekeeping of join paths for speedup (Tom)
-Major subquery speedup (Tom)
-Fewer fsync writes when fsync is not disabled (Tom)
-Improved LIKE optimizer estimates (Tom)
-Prevent fsync in SELECT-only queries (Vadim)
-Make index creation use psort code, because it is now faster (Tom)
-Allow creation of sort temp tables &gt; 1 Gig
-
-Source Tree Changes
--------------------
-Fix for linux PPC compile
-New generic expression-tree-walker subroutine (Tom)
-Change form() to varargform() to prevent portability problems
-Improved range checking for large integers on Alphas
-Clean up #include in /include directory (Bruce)
-Add scripts for checking includes (Bruce)
-Remove un-needed #include's from *.c files (Bruce)
-Change #include's to use &lt;&gt; and "" as appropriate (Bruce)
-Enable Windows compilation of libpq
-Alpha spinlock fix from Uncle George <email>[email protected]</email>
-Overhaul of optimizer data structures (Tom)
-Fix to cygipc library (Yutaka Tanida)
-Allow pgsql to work on newer Cygwin snapshots (Dan)
-New catalog version number (Tom)
-Add Linux ARM
-Rename heap_replace to heap_update
-Update for QNX (Dr. Andreas Kardos)
-New platform-specific regression handling (Tom)
-Rename oid8 -&gt; oidvector and int28 -&gt; int2vector (Bruce)
-Included all yacc and lex files into the distribution (Peter E.)
-Remove lextest, no longer needed (Peter E)
-Fix for libpq and psql on Windows (Magnus)
-Internally change datetime and timespan into timestamp and interval (Thomas)
-Fix for plpgsql on BSD/OS
-Add SQL_ASCII test case to the regression test (Tatsuo)
-configure --with-mb now deprecated (Tatsuo)
-NT fixes
-NetBSD fixes (Johnny C. Lam <email>[email protected]</email>)
-Fixes for Alpha compiles
-New multibyte encodings
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="release-6-5-3">
-  <title>Release 6.5.3</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1999-10-13</simpara>
-  </note>
-
-  <para>
-   This is basically a cleanup release for 6.5.2.  We have added a new
-   <application>PgAccess</> that was missing in 6.5.2, and installed an NT-specific fix.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 6.5.3</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those running
-    6.5.*.
-   </para>
-  </sect2>
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Updated version of pgaccess 0.98
-NT-specific patch
-Fix dumping rules on inherited tables
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="release-6-5-2">
-  <title>Release 6.5.2</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1999-09-15</simpara>
-  </note>
-
-  <para>
-   This is basically a cleanup release for 6.5.1.  We have fixed a variety of
-   problems reported by 6.5.1 users.
-  </para>
-
-
-  <sect2>
-   <title>Migration to Version 6.5.2</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those running
-    6.5.*.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-subselect+CASE fixes(Tom)
-Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik)
-Fixes for CASE in WHERE join clauses(Tom)
-Fix BTScan abort(Tom)
-Repair the check for redundant UNIQUE and PRIMARY KEY indexes(Thomas)
-Improve it so that it checks for multicolumn constraints(Thomas)
-Fix for Windows making problem with MB enabled(Hiroki Kataoka)
-Allow BSD yacc and bison to compile pl code(Bruce)
-Fix SET NAMES working
-int8 fixes(Thomas)
-Fix vacuum's memory consumption(Hiroshi,Tatsuo)
-Reduce the total memory consumption of vacuum(Tom)
-Fix for timestamp(datetime)
-Rule deparsing bugfixes(Tom)
-Fix quoting problems in mkMakefile.tcldefs.sh.in and mkMakefile.tkdefs.sh.in(Tom)
-This is to re-use space on index pages freed by vacuum(Vadim)
-document -x for pg_dump(Bruce)
-Fix for unary operators in rule deparser(Tom)
-Comment out FileUnlink of excess segments during mdtruncate()(Tom)
-IRIX linking fix from Yu Cao &gt;[email protected]&lt;
-Repair logic error in LIKE: should not return LIKE_ABORT
-  when reach end of pattern before end of text(Tom)
-Repair incorrect cleanup of heap memory allocation during transaction abort(Tom)
-Updated version of pgaccess 0.98
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="release-6-5-1">
-  <title>Release 6.5.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1999-07-15</simpara>
-  </note>
-
-  <para>
-   This is basically a cleanup release for 6.5.  We have fixed a variety of
-   problems reported by 6.5 users.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 6.5.1</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those running
-    6.5.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Add NT README file
-Portability fixes for linux_ppc, IRIX, linux_alpha, OpenBSD, alpha
-Remove QUERY_LIMIT, use SELECT...LIMIT
-Fix for EXPLAIN on inheritance(Tom)
-Patch to allow vacuum on multisegment tables(Hiroshi)
-R-Tree optimizer selectivity fix(Tom)
-ACL file descriptor leak fix(Atsushi Ogawa)
-New expression subtree code(Tom)
-Avoid disk writes for read-only transactions(Vadim)
-Fix for removal of temp tables if last transaction was aborted(Bruce)
-Fix to prevent too large row from being created(Bruce)
-plpgsql fixes
-Allow port numbers 32k - 64k(Bruce)
-Add ^ precedence(Bruce)
-Rename sort files called pg_temp to pg_sorttemp(Bruce)
-Fix for microseconds in time values(Tom)
-Tutorial source cleanup
-New linux_m68k port
-Fix for sorting of NULL's in some cases(Tom)
-Shared library dependencies fixed (Tom)
-Fixed glitches affecting GROUP BY in subselects(Tom)
-Fix some compiler warnings (Tomoaki Nishiyama)
-Add Win1250 (Czech) support (Pavel Behal)
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="release-6-5">
-  <title>Release 6.5</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1999-06-09</simpara>
-  </note>
-
-  <para>
-   This release marks a major step in the development team's mastery of the source
-   code we inherited from Berkeley.  You will see we are now easily adding
-   major features, thanks to the increasing size and experience of our
-   world-wide development team.
-  </para>
-
-  <para>
-   Here is a brief summary of the more notable changes:
-
-   <variablelist>
-    <varlistentry>
-     <term>
-      Multiversion concurrency control(MVCC)
-     </term>
-     <listitem>
-      <para>
-       This removes our old table-level locking, and replaces it with
-       a locking system that is superior to most commercial database
-       systems.  In a traditional system, each row that is modified
-       is locked until committed, preventing reads by other users.
-       MVCC uses the natural multiversion nature of
-       <productname>PostgreSQL</productname> to allow readers to
-       continue reading consistent data during writer activity.
-       Writers continue to use the compact pg_log transaction system.
-       This is all performed without having to allocate a lock for
-       every row like traditional database systems.  So, basically,
-       we no longer are restricted by simple table-level locking; we
-       have something better than row-level locking.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Hot backups from <application>pg_dump</application>
-     </term>
-     <listitem>
-      <para>
-       <application>pg_dump</application> takes advantage of the new
-       MVCC features to give a consistent database dump/backup while
-       the database stays online and available for queries.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Numeric data type
-     </term>
-     <listitem>
-      <para>
-       We now have a true numeric data type, with
-       user-specified precision.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Temporary tables
-     </term>
-     <listitem>
-      <para>
-       Temporary tables are guaranteed to have unique names
-       within a database session, and are destroyed on session exit.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      New SQL features
-     </term>
-     <listitem>
-      <para>
-       We now have CASE, INTERSECT, and EXCEPT statement
-       support.  We have new LIMIT/OFFSET, SET TRANSACTION ISOLATION LEVEL,
-       SELECT ... FOR UPDATE, and an improved LOCK TABLE command.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Speedups
-     </term>
-     <listitem>
-      <para>
-       We continue to speed up <productname>PostgreSQL</productname>,
-       thanks to the variety of talents within our team.  We have
-       sped up memory allocation, optimization, table joins, and row
-       transfer routines.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Ports
-     </term>
-     <listitem>
-      <para>
-       We continue to expand our port list, this time including
-       <systemitem class="osname">Windows NT</>/<systemitem>ix86</> and <systemitem class="osname">NetBSD</>/<systemitem>arm32</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Interfaces
-     </term>
-     <listitem>
-      <para>
-       Most interfaces have new versions, and existing functionality
-       has been improved.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Documentation
-     </term>
-     <listitem>
-      <para>
-       New and updated material is present throughout the
-       documentation. New <acronym>FAQ</acronym>s have been
-       contributed for <systemitem class="osname">SGI</> and <systemitem class="osname">AIX</> platforms.
-       The <citetitle>Tutorial</citetitle> has introductory information
-       on <acronym>SQL</acronym> from Stefan Simkovics.
-       For the <citetitle>User's Guide</citetitle>, there are
-       reference pages covering the postmaster and more utility
-       programs, and a new appendix
-       contains details on date/time behavior.
-       The <citetitle>Administrator's Guide</citetitle> has a new
-       chapter on troubleshooting from Tom Lane.
-       And the <citetitle>Programmer's Guide</citetitle> has a
-       description of query processing, also from Stefan, and details
-       on obtaining the <productname>PostgreSQL</productname> source
-       tree via anonymous <productname>CVS</productname> and
-       <productname>CVSup</productname>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <sect2>
-   <title>Migration to Version 6.5</title>
-
-   <para>
-    A dump/restore using <application>pg_dump</application>
-    is required for those wishing to migrate data from any
-    previous release of <productname>PostgreSQL</productname>.
-    <application>pg_upgrade</application> can <emphasis>not</emphasis>
-    be used to upgrade to this release because the on-disk structure
-    of the tables has changed compared to previous releases.
-   </para>
-
-   <para>
-    The new Multiversion Concurrency Control (MVCC) features can
-    give somewhat different behaviors in multiuser
-    environments. <emphasis>Read and understand the following section
-     to ensure that your existing applications will give you the
-     behavior you need.</emphasis>
-   </para>
-
-   <sect3>
-    <title>Multiversion Concurrency Control</title>
-
-    <para>
-     Because readers in 6.5 don't lock data, regardless of transaction
-     isolation level, data read by one transaction can be overwritten by
-     another. In other words, if a row is returned by
-     <command>SELECT</command> it doesn't mean that this row really exists
-     at the time it is returned (i.e. sometime after the statement or
-     transaction began) nor that the row is protected from being deleted or
-     updated by concurrent transactions before the current transaction does
-     a commit or rollback.
-    </para>
-
-    <para>
-     To ensure the actual existence of a row and protect it against
-     concurrent updates one must use <command>SELECT FOR UPDATE</command> or
-     an appropriate <command>LOCK TABLE</command> statement. This should be
-     taken into account when porting applications from previous releases of
-     <productname>PostgreSQL</productname> and other environments.
-    </para>
-
-    <para>
-     Keep the above in mind if you are using
-     <filename>contrib/refint.*</filename> triggers for
-     referential integrity. Additional techniques are required now. One way is
-     to use <command>LOCK parent_table IN SHARE ROW EXCLUSIVE MODE</command>
-     command if a transaction is going to update/delete a primary key and
-     use <command>LOCK parent_table IN SHARE MODE</command> command if a
-     transaction is going to update/insert a foreign key.
-
-     <note>
-      <para>
-       Note that if you run a transaction in SERIALIZABLE mode then you must
-       execute the <command>LOCK</command> commands above before execution of any
-       <acronym>DML</acronym> statement
-       (<command>SELECT/INSERT/DELETE/UPDATE/FETCH/COPY_TO</command>) in the
-       transaction.
-      </para>
-     </note>
-    </para>
-
-    <para>
-     These inconveniences will disappear in the future
-     when the ability to read dirty
-     (uncommitted) data (regardless of isolation level) and true referential
-     integrity will be implemented.
-    </para>
-   </sect3>
-   </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Bug Fixes
----------
-Fix text&lt;-&gt;float8 and text&lt;-&gt;float4 conversion functions(Thomas)
-Fix for creating tables with mixed-case constraints(Billy)
-Change exp()/pow() behavior to generate error on underflow/overflow(Jan)
-Fix bug in pg_dump -z
-Memory overrun cleanups(Tatsuo)
-Fix for lo_import crash(Tatsuo)
-Adjust handling of data type names to suppress double quotes(Thomas)
-Use type coercion for matching columns and DEFAULT(Thomas)
-Fix deadlock so it only checks once after one second of sleep(Bruce)
-Fixes for aggregates and PL/pgsql(Hiroshi)
-Fix for subquery crash(Vadim)
-Fix for libpq function PQfnumber and case-insensitive names(Bahman Rafatjoo)
-Fix for large object write-in-middle, no extra block, memory consumption(Tatsuo)
-Fix for pg_dump -d or -D and  quote special characters in INSERT
-Repair serious problems with dynahash(Tom)
-Fix INET/CIDR portability problems
-Fix problem with selectivity error in ALTER TABLE ADD COLUMN(Bruce)
-Fix executor so mergejoin of different column types works(Tom)
-Fix for Alpha OR selectivity bug
-Fix OR index selectivity problem(Bruce)
-Fix so \d shows proper length for char()/varchar()(Ryan)
-Fix tutorial code(Clark)
-Improve destroyuser checking(Oliver)
-Fix for Kerberos(Rodney McDuff)
-Fix for dropping database while dirty buffers(Bruce)
-Fix so sequence nextval() can be case-sensitive(Bruce)
-Fix !!= operator
-Drop buffers before destroying database files(Bruce)
-Fix case where executor evaluates functions twice(Tatsuo)
-Allow sequence nextval actions to be case-sensitive(Bruce)
-Fix optimizer indexing not working for negative numbers(Bruce)
-Fix for memory leak in executor with fjIsNull
-Fix for aggregate memory leaks(Erik Riedel)
-Allow user name containing a dash to grant privileges
-Cleanup of NULL in inet types
-Clean up system table bugs(Tom)
-Fix problems of PAGER and \? command(Masaaki Sakaida)
-Reduce default multisegment file size limit to 1GB(Peter)
-Fix for dumping of CREATE OPERATOR(Tom)
-Fix for backward scanning of cursors(Hiroshi Inoue)
-Fix for COPY FROM STDIN when using \i(Tom)
-Fix for subselect is compared inside an expression(Jan)
-Fix handling of error reporting while returning rows(Tom)
-Fix problems with reference to array types(Tom,Jan)
-Prevent UPDATE SET oid(Jan)
-Fix pg_dump so -t option can handle case-sensitive tablenames
-Fixes for GROUP BY in special cases(Tom, Jan)
-Fix for memory leak in failed queries(Tom)
-DEFAULT now supports mixed-case identifiers(Tom)
-Fix for multisegment uses of DROP/RENAME table, indexes(Ole Gjerde)
-Disable use of pg_dump with both -o and -d options(Bruce)
-Allow pg_dump to properly dump group privileges(Bruce)
-Fix GROUP BY in INSERT INTO table SELECT * FROM table2(Jan)
-Fix for computations in views(Jan)
-Fix for aggregates on array indexes(Tom)
-Fix for DEFAULT handles single quotes in value requiring too many quotes
-Fix security problem with non-super users importing/exporting large objects(Tom)
-Rollback of transaction that creates table cleaned up properly(Tom)
-Fix to allow long table and column names to generate proper serial names(Tom)
-
-Enhancements
-------------
-Add "vacuumdb" utility
-Speed up libpq by allocating memory better(Tom)
-EXPLAIN all indexes used(Tom)
-Implement CASE, COALESCE, NULLIF  expression(Thomas)
-New pg_dump table output format(Constantin)
-Add string min()/max() functions(Thomas)
-Extend new type coercion techniques to aggregates(Thomas)
-New moddatetime contrib(Terry)
-Update to pgaccess 0.96(Constantin)
-Add routines for single-byte "char" type(Thomas)
-Improved substr() function(Thomas)
-Improved multibyte handling(Tatsuo)
-Multiversion concurrency control/MVCC(Vadim)
-New Serialized mode(Vadim)
-Fix for tables over 2gigs(Peter)
-New SET TRANSACTION ISOLATION LEVEL(Vadim)
-New LOCK TABLE IN ... MODE(Vadim)
-Update ODBC driver(Byron)
-New NUMERIC data type(Jan)
-New SELECT FOR UPDATE(Vadim)
-Handle "NaN" and "Infinity" for input values(Jan)
-Improved date/year handling(Thomas)
-Improved handling of backend connections(Magnus)
-New options ELOG_TIMESTAMPS and USE_SYSLOG options for log files(Massimo)
-New TCL_ARRAYS option(Massimo)
-New INTERSECT and EXCEPT(Stefan)
-New pg_index.indisprimary for primary key tracking(D'Arcy)
-New pg_dump option to allow dropping of tables before creation(Brook)
-Speedup of row output routines(Tom)
-New READ COMMITTED isolation level(Vadim)
-New TEMP tables/indexes(Bruce)
-Prevent sorting if result is already sorted(Jan)
-New memory allocation optimization(Jan)
-Allow psql to do \p\g(Bruce)
-Allow multiple rule actions(Jan)
-Added LIMIT/OFFSET functionality(Jan)
-Improve optimizer when joining a large number of tables(Bruce)
-New intro to SQL from S. Simkovics' Master's Thesis (Stefan, Thomas)
-New intro to backend processing from S. Simkovics' Master's Thesis (Stefan)
-Improved int8 support(Ryan Bradetich, Thomas, Tom)
-New routines to convert between int8 and text/varchar types(Thomas)
-New bushy plans, where meta-tables are joined(Bruce)
-Enable right-hand queries by default(Bruce)
-Allow reliable maximum number of backends to be set at configure time
-     (--with-maxbackends and postmaster switch (-N backends))(Tom)
-GEQO default now 10 tables because of optimizer speedups(Tom)
-Allow NULL=Var for MS-SQL portability(Michael, Bruce)
-Modify contrib check_primary_key() so either "automatic" or "dependent"(Anand)
-Allow psql \d on a view show query(Ryan)
-Speedup for LIKE(Bruce)
-Ecpg fixes/features, see src/interfaces/ecpg/ChangeLog file(Michael)
-JDBC fixes/features, see src/interfaces/jdbc/CHANGELOG(Peter)
-Make % operator have precedence like /(Bruce)
-Add new postgres -O option to allow system table structure changes(Bruce)
-Update contrib/pginterface/findoidjoins script(Tom)
-Major speedup in vacuum of deleted rows with indexes(Vadim)
-Allow non-SQL functions to run different versions based on arguments(Tom)
-Add -E option that shows actual queries sent by \dt and friends(Masaaki Sakaida)
-Add version number in start-up banners for psql(Masaaki Sakaida)
-New contrib/vacuumlo removes large objects not referenced(Peter)
-New initialization for table sizes so non-vacuumed tables perform better(Tom)
-Improve error messages when a connection is rejected(Tom)
-Support for arrays of char() and varchar() fields(Massimo)
-Overhaul of hash code to increase reliability and performance(Tom)
-Update to PyGreSQL 2.4(D'Arcy)
-Changed debug options so -d4 and -d5 produce different node displays(Jan)
-New pg_options: pretty_plan, pretty_parse, pretty_rewritten(Jan)
-Better optimization statistics for system table access(Tom)
-Better handling of non-default block sizes(Massimo)
-Improve GEQO optimizer memory consumption(Tom)
-UNION now supports ORDER BY of columns not in target list(Jan)
-Major libpq++ improvements(Vince Vielhaber)
-pg_dump now uses -z(ACL's) as default(Bruce)
-backend cache, memory speedups(Tom)
-have pg_dump do everything in one snapshot transaction(Vadim)
-fix for large object memory leakage, fix for pg_dumping(Tom)
-INET type now respects netmask for comparisons
-Make VACUUM ANALYZE only use a readlock(Vadim)
-Allow VIEWs on UNIONS(Jan)
-pg_dump now can generate consistent snapshots on active databases(Vadim)
-
-Source Tree Changes
--------------------
-Improve port matching(Tom)
-Portability fixes for SunOS
-Add Windows NT backend port and enable dynamic loading(Magnus and Daniel Horak)
-New port to Cobalt Qube(Mips) running Linux(Tatsuo)
-Port to NetBSD/m68k(Mr. Mutsuki Nakajima)
-Port to NetBSD/sun3(Mr. Mutsuki Nakajima)
-Port to NetBSD/macppc(Toshimi Aoki)
-Fix for tcl/tk configuration(Vince)
-Removed CURRENT key word for rule queries(Jan)
-NT dynamic loading now works(Daniel Horak)
-Add ARM32 support(Andrew McMurry)
-Better support for HP-UX 11 and UnixWare
-Improve file handling to be more uniform, prevent file descriptor leak(Tom)
-New install commands for plpgsql(Jan)
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-
-<sect1 id="release-6-4-2">
-<title>Release 6.4.2</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1998-12-20</simpara>
-  </note>
-
-<para>
-The 6.4.1 release was improperly packaged.  This also has one additional
-bug fix.
-</para>
-
-
-<sect2>
-<title>Migration to Version 6.4.2</title>
-
-<para>
-A dump/restore is <emphasis>not</emphasis> required for those running
-6.4.*.
-</para>
-</sect2>
-<sect2>
-<title>Changes</title>
-
-<para>
-<programlisting>
-Fix for datetime constant problem on some platforms(Thomas)
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-
-
-<sect1 id="release-6-4-1">
-<title>Release 6.4.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1998-12-18</simpara>
-  </note>
-
-<para>
-This is basically a cleanup release for 6.4.  We have fixed a variety of
-problems reported by 6.4 users.
-</para>
-
-
-<sect2>
-<title>Migration to Version 6.4.1</title>
-
-<para>
-A dump/restore is <emphasis>not</emphasis> required for those running
-6.4.
-</para>
-</sect2>
-<sect2>
-<title>Changes</title>
-
-<para>
-<programlisting>
-Add pg_dump -N flag to force double quotes around identifiers.  This is
-       the default(Thomas)
-Fix for NOT in where clause causing crash(Bruce)
-EXPLAIN VERBOSE coredump fix(Vadim)
-Fix shared-library problems on Linux
-Fix test for table existence to allow mixed-case and whitespace in
-       the table name(Thomas)
-Fix a couple of pg_dump bugs
-Configure matches template/.similar entries better(Tom)
-Change builtin function names from SPI_* to spi_*
-OR WHERE clause fix(Vadim)
-Fixes for mixed-case table names(Billy)
-contrib/linux/postgres.init.csh/sh fix(Thomas)
-libpq memory overrun fix
-SunOS fixes(Tom)
-Change exp() behavior to generate error on underflow(Thomas)
-pg_dump fixes for memory leak, inheritance constraints, layout change
-update pgaccess to 0.93
-Fix prototype for 64-bit platforms
-Multibyte fixes(Tatsuo)
-New ecpg man page
-Fix memory overruns(Tatsuo)
-Fix for lo_import() crash(Bruce)
-Better search for install program(Tom)
-Timezone fixes(Tom)
-HP-UX fixes(Tom)
-Use implicit type coercion for matching DEFAULT values(Thomas)
-Add routines to help with single-byte (internal) character type(Thomas)
-Compilation of libpq for Windows fixes(Magnus)
-Upgrade to PyGreSQL 2.2(D'Arcy)
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-
-
-<sect1 id="release-6-4">
-<title>Release 6.4</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1998-10-30</simpara>
-  </note>
-
-<para>
-There are <emphasis>many</emphasis> new features and improvements in this release.
-Thanks to our developers and maintainers, nearly every aspect of the system
-has received some attention since the previous release.
-Here is a brief, incomplete summary:
-
-<itemizedlist>
-<listitem>
-<para>
-Views and rules are now functional thanks to extensive new code in the
-rewrite rules system from Jan Wieck. He also wrote a chapter on it
-for the <citetitle>Programmer's Guide</citetitle>.
-</para>
-</listitem>
-<listitem>
-<para>
-Jan also contributed a second procedural language, <application>PL/pgSQL</application>, to go with the
-original <application>PL/pgTCL</application> procedural language he contributed last release.
-</para>
-</listitem>
-
-<listitem>
-<para>
-We have optional multiple-byte character set support from Tatsuo Ishii
-to complement our existing locale support.
-</para>
-</listitem>
-
-<listitem>
-<para>
-Client/server communications has been cleaned up, with better support for
-asynchronous messages and interrupts thanks to Tom Lane.
-</para>
-</listitem>
-
-<listitem>
-<para>
-The parser will now perform automatic type coercion to match arguments
-to available operators and functions, and to match columns and expressions
-with target columns. This uses a generic mechanism which supports
-the type extensibility features of <productname>PostgreSQL</productname>.
-There is a new chapter in the <citetitle>User's Guide</citetitle>
-which covers this topic.
-</para>
-</listitem>
-
-<listitem>
-<para>
-Three new data types have been added.
-Two types, <type>inet</type> and <type>cidr</type>, support various forms
-of IP network, subnet, and machine addressing. There is now an 8-byte integer
-type available on some platforms. See the chapter on data types
-in the <citetitle>User's Guide</citetitle> for details.
-A fourth type, <type>serial</type>, is now supported by the parser as an
-amalgam of the <type>int4</type> type, a sequence, and a unique index.
-</para>
-</listitem>
-
-<listitem>
-<para>
-Several more <acronym>SQL92</acronym>-compatible syntax features have been
-added, including <command>INSERT DEFAULT VALUES</command>
-</para>
-</listitem>
-
-<listitem>
-<para>
-The automatic configuration and installation system has received some
-attention, and should be more robust for more platforms than it has ever
-been.
-</para>
-</listitem>
-
-</itemizedlist>
-</para>
-
-<sect2>
-<title>Migration to Version 6.4</title>
-
-<para>
-A dump/restore using <application>pg_dump</application>
-or <application>pg_dumpall</application>
-is required for those wishing to migrate data from any
-previous release of <productname>PostgreSQL</productname>.
-</para>
-</sect2>
-
-  <sect2>
-<title>Changes</title>
-
-   <para>
-<programlisting>
-Bug Fixes
----------
-Fix for a tiny memory leak in PQsetdb/PQfinish(Bryan)
-Remove char2-16 data types, use char/varchar(Darren)
-Pqfn not handles a NOTICE message(Anders)
-Reduced busywaiting overhead for spinlocks with many backends (dg)
-Stuck spinlock detection (dg)
-Fix up "ISO-style" timespan decoding and encoding(Thomas)
-Fix problem with table drop after rollback of transaction(Vadim)
-Change error message and remove non-functional update message(Vadim)
-Fix for COPY array checking
-Fix for SELECT 1 UNION SELECT NULL
-Fix for buffer leaks in large object calls(Pascal)
-Change owner from oid to int4 type(Bruce)
-Fix a bug in the oracle compatibility functions btrim() ltrim() and rtrim()
-Fix for shared invalidation cache overflow(Massimo)
-Prevent file descriptor leaks in failed COPY's(Bruce)
-Fix memory leak in libpgtcl's pg_select(Constantin)
-Fix problems with username/passwords over 8 characters(Tom)
-Fix problems with handling of asynchronous NOTIFY in backend(Tom)
-Fix of many bad system table entries(Tom)
-
-Enhancements
-------------
-Upgrade ecpg and ecpglib,see src/interfaces/ecpc/ChangeLog(Michael)
-Show the index used in an EXPLAIN(Zeugswetter)
-EXPLAIN  invokes  rule system and shows plan(s) for rewritten queries(Jan)
-Multibyte awareness of many data types and functions, via configure(Tatsuo)
-New configure --with-mb option(Tatsuo)
-New initdb --pgencoding option(Tatsuo)
-New createdb -E multibyte option(Tatsuo)
-Select version(); now returns PostgreSQL version(Jeroen)
-libpq now allows asynchronous clients(Tom)
-Allow cancel from client of backend query(Tom)
-psql now cancels query with Control-C(Tom)
-libpq users need not issue dummy queries to get NOTIFY messages(Tom)
-NOTIFY now sends sender's PID, so you can tell whether it was your own(Tom)
-PGresult struct now includes associated error message, if any(Tom)
-Define "tz_hour" and "tz_minute" arguments to date_part()(Thomas)
-Add routines to convert between varchar and bpchar(Thomas)
-Add routines to allow sizing of varchar and bpchar into target columns(Thomas)
-Add bit flags to support timezonehour and minute in data retrieval(Thomas)
-Allow more variations on valid floating point numbers (e.g. ".1", "1e6")(Thomas)
-Fixes for unary minus parsing with leading spaces(Thomas)
-Implement TIMEZONE_HOUR, TIMEZONE_MINUTE per SQL92 specs(Thomas)
-Check for and properly ignore FOREIGN KEY column constraints(Thomas)
-Define USER as synonym for CURRENT_USER per SQL92 specs(Thomas)
-Enable HAVING clause but no fixes elsewhere yet.
-Make "char" type a synonym for "char(1)" (actually implemented as bpchar)(Thomas)
-Save string type if specified for DEFAULT clause handling(Thomas)
-Coerce operations involving different data types(Thomas)
-Allow some index use for columns of different types(Thomas)
-Add capabilities for automatic type conversion(Thomas)
-Cleanups for large objects, so file is truncated on open(Peter)
-Readline cleanups(Tom)
-Allow psql  \f \ to make spaces as delimiter(Bruce)
-Pass pg_attribute.atttypmod to the frontend for column field lengths(Tom,Bruce)
-Msql compatibility library in /contrib(Aldrin)
-Remove the requirement that ORDER/GROUP BY clause identifiers be
-included in the target list(David)
-Convert columns to match columns in UNION clauses(Thomas)
-Remove fork()/exec() and only do fork()(Bruce)
-Jdbc cleanups(Peter)
-Show backend status on ps command line(only works on some platforms)(Bruce)
-Pg_hba.conf now has a sameuser option in the database field
-Make lo_unlink take oid param, not int4
-New DISABLE_COMPLEX_MACRO for compilers that cannot handle our macros(Bruce)
-Libpgtcl now handles NOTIFY as a Tcl event, need not send dummy queries(Tom)
-libpgtcl cleanups(Tom)
-Add -error option to libpgtcl's pg_result command(Tom)
-New locale patch, see docs/README/locale(Oleg)
-Fix for pg_dump so CONSTRAINT and CHECK syntax is correct(ccb)
-New contrib/lo code for large object orphan removal(Peter)
-New psql command "SET CLIENT_ENCODING TO 'encoding'" for multibytes
-feature, see /doc/README.mb(Tatsuo)
-contrib/noupdate code to revoke update permission on a column
-libpq can now be compiled on Windows(Magnus)
-Add PQsetdbLogin() in libpq
-New 8-byte integer type, checked by configure for OS support(Thomas)
-Better support for quoted table/column names(Thomas)
-Surround table and column names with double-quotes in pg_dump(Thomas)
-PQreset() now works with passwords(Tom)
-Handle case of GROUP BY target list column number out of range(David)
-Allow UNION in subselects
-Add auto-size to screen to \d? commands(Bruce)
-Use UNION to show all \d? results in one query(Bruce)
-Add \d? field search feature(Bruce)
-Pg_dump issues fewer \connect requests(Tom)
-Make pg_dump -z flag work better, document it in manual page(Tom)
-Add HAVING clause with full support for subselects and unions(Stephan)
-Full text indexing routines in contrib/fulltextindex(Maarten)
-Transaction ids now stored in shared memory(Vadim)
-New PGCLIENTENCODING when issuing COPY command(Tatsuo)
-Support for SQL92 syntax "SET NAMES"(Tatsuo)
-Support for LATIN2-5(Tatsuo)
-Add UNICODE regression test case(Tatsuo)
-Lock manager cleanup, new locking modes for LLL(Vadim)
-Allow index use with OR clauses(Bruce)
-Allows "SELECT NULL ORDER BY 1;"
-Explain VERBOSE prints the plan, and now pretty-prints the plan to
-the postmaster log file(Bruce)
-Add indexes display to \d command(Bruce)
-Allow GROUP BY on functions(David)
-New pg_class.relkind for large objects(Bruce)
-New way to send libpq NOTICE messages to a different location(Tom)
-New \w write command to psql(Bruce)
-New /contrib/findoidjoins scans oid columns to find join relationships(Bruce)
-Allow binary-compatible indexes to be considered when checking for valid
-Indexes for restriction clauses containing a constant(Thomas)
-New ISBN/ISSN code in /contrib/isbn_issn
-Allow NOT LIKE, IN, NOT IN, BETWEEN, and NOT BETWEEN constraint(Thomas)
-New rewrite system fixes many problems with rules and views(Jan)
-       * Rules on relations work
-       * Event qualifications on insert/update/delete work
-       * New OLD variable to reference CURRENT, CURRENT will be remove in future
-       * Update rules can reference NEW and OLD in rule qualifications/actions
-       * Insert/update/delete rules on views work
-       * Multiple rule actions are now supported, surrounded by parentheses
-       * Regular users can create views/rules on tables they have RULE permits
-       * Rules and views inherit the privileges of the creator
-       * No rules at the column level
-       * No UPDATE NEW/OLD rules
-       * New pg_tables, pg_indexes, pg_rules and pg_views system views
-       * Only a single action on SELECT rules
-       * Total rewrite overhaul, perhaps for 6.5
-       * handle subselects
-       * handle aggregates on views
-       * handle insert into select from view works
-System indexes are now multikey(Bruce)
-Oidint2, oidint4, and oidname types are removed(Bruce)
-Use system cache for more system table lookups(Bruce)
-New backend programming language PL/pgSQL in backend/pl(Jan)
-New SERIAL data type, auto-creates sequence/index(Thomas)
-Enable assert checking without a recompile(Massimo)
-User lock enhancements(Massimo)
-New setval() command to set sequence value(Massimo)
-Auto-remove unix socket file on start-up if no postmaster running(Massimo)
-Conditional trace package(Massimo)
-New UNLISTEN command(Massimo)
-psql and libpq now compile under Windows using win32.mak(Magnus)
-Lo_read no longer stores trailing NULL(Bruce)
-Identifiers are now truncated to 31 characters internally(Bruce)
-Createuser options now available on the command line
-Code for 64-bit integer supported added, configure tested, int8 type(Thomas)
-Prevent file descriptor leaf from failed COPY(Bruce)
-New pg_upgrade command(Bruce)
-Updated /contrib directories(Massimo)
-New CREATE TABLE DEFAULT VALUES statement available(Thomas)
-New INSERT INTO TABLE DEFAULT VALUES statement available(Thomas)
-New DECLARE and FETCH feature(Thomas)
-libpq's internal structures now not exported(Tom)
-Allow up to 8 key indexes(Bruce)
-Remove ARCHIVE key word, that is no longer used(Thomas)
-pg_dump -n flag to suppress quotes around indentifiers
-disable system columns for views(Jan)
-new INET and CIDR types for network addresses(TomH, Paul)
-no more double quotes in psql output
-pg_dump now dumps views(Terry)
-new SET QUERY_LIMIT(Tatsuo,Jan)
-
-Source Tree Changes
--------------------
-/contrib cleanup(Jun)
-Inline some small functions called for every row(Bruce)
-Alpha/linux fixes
-HP-UX cleanups(Tom)
-Multibyte regression tests(Soonmyung.)
-Remove --disabled options from configure
-Define PGDOC to use POSTGRESDIR by default
-Make regression optional
-Remove extra braces code to pgindent(Bruce)
-Add bsdi shared library support(Bruce)
-New --without-CXX support configure option(Brook)
-New FAQ_CVS
-Update backend flowchart in tools/backend(Bruce)
-Change atttypmod from int16 to int32(Bruce, Tom)
-Getrusage() fix for platforms that do not have it(Tom)
-Add PQconnectdb, PGUSER, PGPASSWORD to libpq man page
-NS32K platform fixes(Phil Nelson, John Buller)
-SCO 7/UnixWare 2.x fixes(Billy,others)
-Sparc/Solaris 2.5 fixes(Ryan)
-Pgbuiltin.3 is obsolete, move to doc files(Thomas)
-Even more documentation(Thomas)
-Nextstep support(Jacek)
-Aix support(David)
-pginterface manual page(Bruce)
-shared libraries all have version numbers
-merged all OS-specific shared library defines into one file
-smarter TCL/TK configuration checking(Billy)
-smarter perl configuration(Brook)
-configure uses supplied install-sh if no install script found(Tom)
-new Makefile.shlib for shared library configuration(Tom)
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-<sect1 id="release-6-3-2">
-<title>Release 6.3.2</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1998-04-07</simpara>
-  </note>
-
-<para>
-This is a bug-fix release for 6.3.x.
-Refer to the release notes for version 6.3 for a more complete summary of new features.
-</para>
-<para>
-Summary:
-
-<itemizedlist>
-<listitem>
-<para>
-Repairs automatic configuration support for some platforms, including Linux,
-from breakage inadvertently introduced in version 6.3.1.
-</para>
-</listitem>
-
-<listitem>
-<para>
-Correctly handles function calls on the left side of BETWEEN and LIKE clauses.
-</para>
-</listitem>
-
-</itemizedlist>
-</para>
-<para>
-A dump/restore is NOT required for those running 6.3 or 6.3.1.  A
-<literal>make distclean</>, <literal>make</>, and <literal>make install</> is all that is required.
-This last step should be performed while the postmaster is not running.
-You should re-link any custom applications that use <productname>PostgreSQL</productname> libraries.
-</para>
-<para>
-For upgrades from pre-6.3 installations,
-refer to the installation and migration instructions for version 6.3.
-</para>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Configure detection improvements for tcl/tk(Brook Milligan, Alvin)
-Manual page improvements(Bruce)
-BETWEEN and LIKE fix(Thomas)
-fix for psql \connect used by pg_dump(Oliver Elphick)
-New odbc driver
-pgaccess, version 0.86
-qsort removed, now uses libc version, cleanups(Jeroen)
-fix for buffer over-runs detected(Maurice Gittens)
-fix for buffer overrun in libpgtcl(Randy Kunkee)
-fix for UNION with DISTINCT or ORDER BY(Bruce)
-gettimeofday configure check(Doug Winterburn)
-Fix "indexes not used" bug(Vadim)
-docs additions(Thomas)
-Fix for backend memory leak(Bruce)
-libreadline cleanup(Erwan MAS)
-Remove DISTDIR(Bruce)
-Makefile dependency cleanup(Jeroen van Vianen)
-ASSERT fixes(Bruce)
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="release-6-3-1">
-  <title>Release 6.3.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1998-03-23</simpara>
-  </note>
-
-  <para>
-   Summary:
-
-<itemizedlist>
-<listitem>
-<para>
-Additional support for multibyte character sets.
-</para>
-</listitem>
-
-<listitem>
-<para>
-Repair byte ordering for mixed-endian clients and servers.
-</para>
-</listitem>
-
-<listitem>
-<para>
-Minor updates to allowed SQL syntax.
-</para>
-</listitem>
-
-<listitem>
-<para>
-Improvements to the configuration autodetection for installation.
-</para>
-</listitem>
-
-</itemizedlist>
-</para>
-<para>
-A dump/restore is NOT required for those running 6.3.  A
-<literal>make distclean</>, <literal>make</>, and <literal>make install</> is all that is required.
-This last step should be performed while the postmaster is not running.
-You should re-link any custom applications that use <productname>PostgreSQL</productname> libraries.
-</para>
-<para>
-For upgrades from pre-6.3 installations,
-refer to the installation and migration instructions for version 6.3.
-</para>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-ecpg cleanup/fixes, now version 1.1(Michael Meskes)
-pg_user cleanup(Bruce)
-large object fix for pg_dump and tclsh (alvin)
-LIKE fix for multiple adjacent underscores
-fix for redefining builtin functions(Thomas)
-ultrix4 cleanup
-upgrade to pg_access 0.83
-updated CLUSTER manual page
-multibyte character set support, see doc/README.mb(Tatsuo)
-configure --with-pgport fix
-pg_ident fix
-big-endian fix for backend communications(Kataoka)
-SUBSTR() and substring() fix(Jan)
-several jdbc fixes(Peter)
-libpgtcl improvements, see libptcl/README(Randy Kunkee)
-Fix for "Datasize = 0" error(Vadim)
-Prevent \do from wrapping(Bruce)
-Remove duplicate Russian character set entries
-Sunos4 cleanup
-Allow optional TABLE key word in LOCK and SELECT INTO(Thomas)
-CREATE SEQUENCE options to allow a negative integer(Thomas)
-Add "PASSWORD" as an allowed column identifier(Thomas)
-Add checks for UNION target fields(Bruce)
-Fix Alpha port(Dwayne Bailey)
-Fix for text arrays containing quotes(Doug Gibson)
-Solaris compile fix(Albert Chin-A-Young)
-Better identify tcl and tk libs and includes(Bruce)
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="release-6-3">
-  <title>Release 6.3</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1998-03-01</simpara>
-  </note>
-
-  <para>
-   There are <emphasis>many</emphasis> new features and improvements in this release.
-   Here is a brief, incomplete summary:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Many new SQL features, including
-      full <acronym>SQL92</acronym> subselect capability
-      (everything is here but target-list subselects).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Support for client-side environment variables to specify time zone and date style.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Socket interface for client/server connection. This is the default now
-      so you might need to start <application>postmaster</application> with the
-      <option>-i</option> flag.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Better password authorization mechanisms. Default table privileges have changed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Old-style <firstterm>time travel</firstterm>
-      has been removed. Performance has been improved.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <note>
-   <para>
-    Bruce Momjian wrote the following notes to introduce the new release.
-   </para>
-  </note>
-
-  <para>
-   There are some general 6.3 issues that I want to mention.  These are
-   only the big items that cannot be described in one sentence.  A review
-   of the detailed changes list is still needed.
-  </para>
-  <para>
-   First, we now have subselects.  Now that we have them, I would like to
-   mention that without subselects, SQL is a very limited language.
-   Subselects are a major feature, and you should review your code for
-   places where subselects provide a better solution for your queries.  I
-   think you will find that there are more uses for subselects than you might
-   think.  Vadim has put us on the big SQL map with subselects, and fully
-   functional ones too.  The only thing you cannot do with subselects is to
-   use them in the target list.
-  </para>
-  <para>
-   Second, 6.3 uses Unix domain sockets rather than TCP/IP by default.  To
-   enable connections from other machines, you have to use the new
-   postmaster -i option, and of course edit <filename>pg_hba.conf</filename>.  Also, for this
-   reason, the format of <filename>pg_hba.conf</filename> has changed.
-  </para>
-  <para>
-   Third, <type>char()</type> fields will now allow faster access than <type>varchar()</type> or
-   <type>text</type>. Specifically, the <type>text</> and <type>varchar()</type> have a penalty for access to
-   any columns after the first column of this type.  <type>char()</type> used to also
-   have this access penalty, but it no longer does.  This might suggest that
-   you redesign some of your tables, especially if you have short character
-   columns that you have defined as <type>varchar()</type> or <type>text</type>.  This and other
-   changes make 6.3 even faster than earlier releases.
-  </para>
-  <para>
-   We now have passwords definable independent of any Unix file.  There are
-   new SQL USER commands.
-   See the <citetitle>Administrator's Guide</citetitle> for more
-   information.  There is a new table, pg_shadow, which is used to store
-   user information and user passwords, and it by default only SELECT-able
-   by the <systemitem>postgres</systemitem> super-user.  pg_user is now a view of pg_shadow, and is
-   SELECT-able by PUBLIC.  You should keep using pg_user in your
-   application without changes.
-  </para>
-  <para>
-   User-created tables now no longer have SELECT privilege to PUBLIC by
-   default.  This was done because the ANSI standard requires it.  You can
-   of course GRANT any privileges you want after the table is created.
-   System tables continue to be SELECT-able by PUBLIC.
-  </para>
-  <para>
-   We also have real deadlock detection code.  No more sixty-second
-   timeouts.  And the new locking code implements a <acronym>FIFO</acronym> better, so there
-   should be less resource starvation during heavy use.
-  </para>
-  <para>
-   Many complaints have been made about inadequate documentation in previous
-   releases.  Thomas has put much effort into many new manuals for this
-   release.  Check out the doc/ directory.
-  </para>
-  <para>
-   For performance reasons, time travel is gone, but can be implemented
-   using triggers (see <filename>pgsql/contrib/spi/README</filename>).  Please check out the new
-   \d command for types, operators, etc.  Also, views have their own
-   privileges now, not based on the underlying tables, so privileges on
-   them have to be set separately.  Check <filename>/pgsql/interfaces</filename> for some new
-   ways to talk to <productname>PostgreSQL</productname>.
-  </para>
-  <para>
-   This is the first release that really required an explanation for
-   existing users.  In many ways, this was necessary because the new
-   release removes many limitations, and the work-arounds people were using
-   are no longer needed.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 6.3</title>
-
-   <para>
-    A dump/restore using <application>pg_dump</application>
-    or <application>pg_dumpall</application>
-    is required for those wishing to migrate data from any
-    previous release of <productname>PostgreSQL</productname>.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Bug Fixes
----------
-Fix binary cursors broken by MOVE implementation(Vadim)
-Fix for tcl library crash(Jan)
-Fix for array handling, from Gerhard Hintermayer
-Fix acl error, and remove duplicate pqtrace(Bruce)
-Fix psql \e for empty file(Bruce)
-Fix for textcat on varchar() fields(Bruce)
-Fix for DBT Sendproc (Zeugswetter Andres)
-Fix vacuum analyze syntax problem(Bruce)
-Fix for international identifiers(Tatsuo)
-Fix aggregates on inherited tables(Bruce)
-Fix substr() for out-of-bounds data
-Fix for select 1=1 or 2=2, select 1=1 and 2=2, and select sum(2+2)(Bruce)
-Fix notty output to show status result.  -q option still turns it off(Bruce)
-Fix for count(*), aggs with views and multiple tables and sum(3)(Bruce)
-Fix cluster(Bruce)
-Fix for PQtrace start/stop several times(Bruce)
-Fix a variety of locking problems like newer lock waiters getting
-       lock before older waiters, and having readlock people not share
-       locks if a writer is waiting for a lock, and waiting writers not
-       getting priority over waiting readers(Bruce)
-Fix crashes in psql when executing queries from external files(James)
-Fix problem with multiple order by columns, with the first one having
-       NULL values(Jeroen)
-Use correct hash table support functions for float8 and int4(Thomas)
-Re-enable JOIN= option in CREATE OPERATOR statement (Thomas)
-Change precedence for boolean operators to match expected behavior(Thomas)
-Generate elog(ERROR) on over-large integer(Bruce)
-Allow multiple-argument functions in constraint clauses(Thomas)
-Check boolean input literals for 'true','false','yes','no','1','0'
-       and throw elog(ERROR) if unrecognized(Thomas)
-Major large objects fix
-Fix for GROUP BY showing duplicates(Vadim)
-Fix for index scans in MergeJoin(Vadim)
-
-Enhancements
-------------
-Subselects with EXISTS, IN, ALL, ANY key words (Vadim, Bruce, Thomas)
-New User Manual(Thomas, others)
-Speedup by inlining some frequently-called functions
-Real deadlock detection, no more timeouts(Bruce)
-Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP,
-       CURRENT_USER(Thomas)
-Modify constraint syntax to be SQL92-compliant(Thomas)
-Implement SQL92 PRIMARY KEY and UNIQUE clauses using indexes(Thomas)
-Recognize SQL92 syntax for FOREIGN KEY. Throw elog notice(Thomas)
-Allow NOT NULL UNIQUE constraint clause (each allowed separately before)(Thomas)
-Allow PostgreSQL-style casting ("::") of non-constants(Thomas)
-Add support for SQL3 TRUE and FALSE boolean constants(Thomas)
-Support SQL92 syntax for IS TRUE/IS FALSE/IS NOT TRUE/IS NOT FALSE(Thomas)
-Allow shorter strings for boolean literals (e.g. "t", "tr", "tru")(Thomas)
-Allow SQL92 delimited identifiers(Thomas)
-Implement SQL92 binary and hexadecimal string decoding (b'10' and x'1F')(Thomas)
-Support SQL92 syntax for type coercion of literal strings
-       (e.g. "DATETIME 'now'")(Thomas)
-Add conversions for int2, int4, and OID types to and from text(Thomas)
-Use shared lock when building indexes(Vadim)
-Free memory allocated for an user query inside transaction block after
-       this query is done, was turned off in &lt;= 6.2.1(Vadim)
-New SQL statement CREATE PROCEDURAL LANGUAGE(Jan)
-New <productname>PostgreSQL</productname> Procedural Language (PL) backend interface(Jan)
-Rename pg_dump -H option to -h(Bruce)
-Add Java support for passwords, European dates(Peter)
-Use indexes for LIKE and ~, !~ operations(Bruce)
-Add hash functions for datetime and timespan(Thomas)
-Time Travel removed(Vadim, Bruce)
-Add paging for \d and \z, and fix \i(Bruce)
-Add Unix domain socket support to backend and to frontend library(Goran)
-Implement CREATE DATABASE/WITH LOCATION and initlocation utility(Thomas)
-Allow more SQL92 and/or <productname>PostgreSQL</productname> reserved words as column identifiers(Thomas)
-Augment support for SQL92 SET TIME ZONE...(Thomas)
-SET/SHOW/RESET TIME ZONE uses TZ backend environment variable(Thomas)
-Implement SET keyword = DEFAULT and SET TIME ZONE DEFAULT(Thomas)
-Enable SET TIME ZONE using TZ environment variable(Thomas)
-Add PGDATESTYLE environment variable to frontend and backend initialization(Thomas)
-Add PGTZ, PGCOSTHEAP, PGCOSTINDEX, PGRPLANS, PGGEQO
-       frontend library initialization environment variables(Thomas)
-Regression tests time zone automatically set with "setenv PGTZ PST8PDT"(Thomas)
-Add pg_description table for info on tables, columns, operators, types, and
-       aggregates(Bruce)
-Increase 16 char limit on system table/index names to 32 characters(Bruce)
-Rename system indexes(Bruce)
-Add 'GERMAN' option to SET DATESTYLE(Thomas)
-Define an "ISO-style" timespan output format with "hh:mm:ss" fields(Thomas)
-Allow fractional values for delta times (e.g. '2.5 days')(Thomas)
-Validate numeric input more carefully for delta times(Thomas)
-Implement day of year as possible input to date_part()(Thomas)
-Define timespan_finite() and text_timespan() functions(Thomas)
-Remove archive stuff(Bruce)
-Allow for a pg_password authentication database that is separate from
-       the system password file(Todd)
-Dump ACLs, GRANT, REVOKE privileges(Matt)
-Define text, varchar, and bpchar string length functions(Thomas)
-Fix Query handling for inheritance, and cost computations(Bruce)
-Implement CREATE TABLE/AS SELECT (alternative to SELECT/INTO)(Thomas)
-Allow NOT, IS NULL, IS NOT NULL in constraints(Thomas)
-Implement UNIONs for SELECT(Bruce)
-Add UNION, GROUP, DISTINCT to INSERT(Bruce)
-varchar() stores only necessary bytes on disk(Bruce)
-Fix for BLOBs(Peter)
-Mega-Patch for JDBC...see README_6.3 for list of changes(Peter)
-Remove unused "option" from PQconnectdb()
-New LOCK command and lock manual page describing deadlocks(Bruce)
-Add new psql \da, \dd, \df, \do, \dS, and \dT commands(Bruce)
-Enhance psql \z to show sequences(Bruce)
-Show NOT NULL and DEFAULT in psql \d table(Bruce)
-New psql .psqlrc file start-up(Andrew)
-Modify sample start-up script in contrib/linux to show syslog(Thomas)
-New types for IP and MAC addresses in contrib/ip_and_mac(TomH)
-Unix system time conversions with date/time types in contrib/unixdate(Thomas)
-Update of contrib stuff(Massimo)
-Add Unix socket support to DBD::Pg(Goran)
-New python interface (PyGreSQL 2.0)(D'Arcy)
-New frontend/backend protocol has a version number, network byte order(Phil)
-Security features in pg_hba.conf enhanced and documented, many cleanups(Phil)
-CHAR() now faster access than VARCHAR() or TEXT
-ecpg embedded SQL preprocessor
-Reduce system column overhead(Vadmin)
-Remove pg_time table(Vadim)
-Add pg_type attribute to identify types that need length (bpchar, varchar)
-Add report of offending line when COPY command fails
-Allow VIEW privileges to be set separately from the underlying tables.
-       For security, use GRANT/REVOKE on views as appropriate(Jan)
-Tables now have no default GRANT SELECT TO PUBLIC.  You must
-       explicitly grant such privileges.
-Clean up tutorial examples(Darren)
-
-Source Tree Changes
--------------------
-Add new html development tools, and flow chart in /tools/backend
-Fix for SCO compiles
-Stratus computer port Robert Gillies
-Added support for shlib for BSD44_derived &amp; i386_solaris
-Make configure more automated(Brook)
-Add script to check regression test results
-Break parser functions into smaller files, group together(Bruce)
-Rename heap_create to heap_create_and_catalog, rename heap_creatr
-       to heap_create()(Bruce)
-Sparc/Linux patch for locking(TomS)
-Remove PORTNAME and reorganize port-specific stuff(Marc)
-Add optimizer README file(Bruce)
-Remove some recursion in optimizer and clean up some code there(Bruce)
-Fix for NetBSD locking(Henry)
-Fix for libptcl make(Tatsuo)
-AIX patch(Darren)
-Change IS TRUE, IS FALSE, ... to expressions using "=" rather than
-       function calls to istrue() or isfalse() to allow optimization(Thomas)
-Various fixes NetBSD/Sparc related(TomH)
-Alpha linux locking(Travis,Ryan)
-Change elog(WARN) to elog(ERROR)(Bruce)
-FAQ for FreeBSD(Marc)
-Bring in the PostODBC source tree as part of our standard distribution(Marc)
-A minor patch for HP/UX 10 vs 9(Stan)
-New pg_attribute.atttypmod for type-specific info like varchar length(Bruce)
-UnixWare patches(Billy)
-New i386 'lock' for spinlock asm(Billy)
-Support for multiplexed backends is removed
-Start an OpenBSD port
-Start an AUX port
-Start a Cygnus port
-Add string functions to regression suite(Thomas)
-Expand a few function names formerly truncated to 16 characters(Thomas)
-Remove un-needed malloc() calls and replace with palloc()(Bruce)
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-<sect1 id="release-6-2-1">
-<title>Release 6.2.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1997-10-17</simpara>
-  </note>
-
-<para>
-6.2.1 is a bug-fix and usability release on 6.2.
-</para>
-<para>
-Summary:
-
-<itemizedlist>
-<listitem>
-<para>
-Allow strings to span lines, per <acronym>SQL92</acronym>.
-</para>
-</listitem>
-
-<listitem>
-<para>
-Include example trigger function for inserting user names on table updates.
-</para>
-</listitem>
-
-</itemizedlist>
-</para>
-<para>
-This is a minor bug-fix release on 6.2.
-For upgrades from pre-6.2 systems, a full dump/reload is required.
-Refer to the 6.2 release notes for instructions.
-</para>
-
-<sect2>
-<title>Migration from version 6.2 to version 6.2.1</title>
-
-<para>
-This is a minor bug-fix release. A dump/reload is not required from version 6.2,
-but is required from any release prior to 6.2.
-</para>
-<para>
-In upgrading from version 6.2, if you choose to dump/reload you will find that
-avg(money) is now calculated correctly. All other bug fixes take effect
-upon updating the executables.
-</para>
-<para>
-Another way to avoid dump/reload is to use the following SQL command
-from <command>psql</command> to update the existing system table:
-
-<programlisting>
-update pg_aggregate set aggfinalfn = 'cash_div_flt8'
- where aggname = 'avg' and aggbasetype = 790;
-</programlisting>
-</para>
-<para>
-This will need to be done to every existing database, including template1.
-</para>
-</sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Allow TIME and TYPE column names(Thomas)
-Allow larger range of true/false as boolean values(Thomas)
-Support output of "now" and "current"(Thomas)
-Handle DEFAULT with INSERT of NULL properly(Vadim)
-Fix for relation reference counts problem in buffer manager(Vadim)
-Allow strings to span lines, like ANSI(Thomas)
-Fix for backward cursor with ORDER BY(Vadim)
-Fix avg(cash) computation(Thomas)
-Fix for specifying a column twice in ORDER/GROUP BY(Vadim)
-Documented new libpq function to return affected rows, PQcmdTuples(Bruce)
-Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-<sect1 id="release-6-2">
-<title>Release 6.2</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1997-10-02</simpara>
-  </note>
-
-<para>
-A dump/restore is required for those wishing to migrate data from
-previous releases of <productname>PostgreSQL</productname>.
-</para>
-
-<sect2>
-<title>Migration from version 6.1 to version 6.2</title>
-
-<para>
-This migration requires a complete dump of the 6.1 database and a
-restore of the database in 6.2.
-</para>
-<para>
-Note that the <command>pg_dump</command> and <command>pg_dumpall</command> utility from 6.2 should be used
-to dump the 6.1 database.
-</para>
-</sect2>
-
-<sect2>
-<title>Migration from version 1.<replaceable>x</> to version 6.2</title>
-
-<para>
-Those migrating from earlier 1.* releases should first upgrade to 1.09
-because the COPY output format was improved from the 1.02 release.
-</para>
-</sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Bug Fixes
----------
-Fix problems with pg_dump for inheritance, sequences, archive tables(Bruce)
-Fix compile errors on overflow due to shifts, unsigned, and bad prototypes
-        from Solaris(Diab Jerius)
-Fix bugs in geometric line arithmetic (bad intersection calculations)(Thomas)
-Check for geometric intersections at endpoints to avoid rounding ugliness(Thomas)
-Catch non-functional delete attempts(Vadim)
-Change time function names to be more consistent(Michael Reifenberg)
-Check for zero divides(Michael Reifenberg)
-Fix very old bug which made rows changed/inserted by a command
-       visible to the command itself (so we had multiple update of
-       updated rows, etc.)(Vadim)
-Fix for SELECT null, 'fail' FROM pg_am (Patrick)
-SELECT NULL as EMPTY_FIELD now allowed(Patrick)
-Remove un-needed signal stuff from contrib/pginterface
-Fix OR (where x != 1 or x isnull didn't return rows with x NULL) (Vadim)
-Fix time_cmp function (Vadim)
-Fix handling of functions with non-attribute first argument in
-       WHERE clauses (Vadim)
-Fix GROUP BY when order of entries is different from order
-       in target list (Vadim)
-Fix pg_dump for aggregates without sfunc1 (Vadim)
-
-Enhancements
-------------
-Default genetic optimizer GEQO parameter is now 8(Bruce)
-Allow use parameters in target list having aggregates in functions(Vadim)
-Added JDBC driver as an interface(Adrian &amp; Peter)
-pg_password utility
-Return number of rows inserted/affected by INSERT/UPDATE/DELETE etc.(Vadim)
-Triggers implemented with CREATE TRIGGER (SQL3)(Vadim)
-SPI (Server Programming Interface) allows execution of queries inside
-       C-functions (Vadim)
-NOT NULL implemented (SQL92)(Robson Paniago de Miranda)
-Include reserved words for string handling, outer joins, and unions(Thomas)
-Implement extended comments ("/* ... */") using exclusive states(Thomas)
-Add "//" single-line comments(Bruce)
-Remove some restrictions on characters in operator names(Thomas)
-DEFAULT and CONSTRAINT for tables implemented (SQL92)(Vadim &amp; Thomas)
-Add text concatenation operator and function (SQL92)(Thomas)
-Support WITH TIME ZONE syntax (SQL92)(Thomas)
-Support INTERVAL unit TO unit syntax (SQL92)(Thomas)
-Define types DOUBLE PRECISION, INTERVAL, CHARACTER,
-       and CHARACTER VARYING (SQL92)(Thomas)
-Define type FLOAT(p) and rudimentary DECIMAL(p,s), NUMERIC(p,s) (SQL92)(Thomas)
-Define EXTRACT(), POSITION(), SUBSTRING(), and TRIM() (SQL92)(Thomas)
-Define CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP (SQL92)(Thomas)
-Add syntax and warnings for UNION, HAVING, INNER and OUTER JOIN (SQL92)(Thomas)
-Add more reserved words, mostly for SQL92 compliance(Thomas)
-Allow hh:mm:ss time entry for timespan/reltime types(Thomas)
-Add center() routines for lseg, path, polygon(Thomas)
-Add distance() routines for circle-polygon, polygon-polygon(Thomas)
-Check explicitly for points and polygons contained within polygons
-       using an axis-crossing algorithm(Thomas)
-Add routine to convert circle-box(Thomas)
-Merge conflicting operators for different geometric data types(Thomas)
-Replace distance operator "&lt;===&gt;" with "&lt;-&gt;"(Thomas)
-Replace "above" operator "!^" with "&gt;^" and "below" operator "!|" with "&lt;^"(Thomas)
-Add routines for text trimming on both ends, substring, and string position(Thomas)
-Added conversion routines circle(box) and poly(circle)(Thomas)
-Allow internal sorts to be stored in memory rather than in files(Bruce &amp; Vadim)
-Allow functions and operators on internally-identical types to succeed(Bruce)
-Speed up backend start-up after profiling analysis(Bruce)
-Inline frequently called functions for performance(Bruce)
-Reduce open() calls(Bruce)
-psql:  Add PAGER for \h and \?,\C fix
-Fix for psql pager when no tty(Bruce)
-New entab utility(Bruce)
-General trigger functions for referential integrity (Vadim)
-General trigger functions for time travel (Vadim)
-General trigger functions for AUTOINCREMENT/IDENTITY feature (Vadim)
-MOVE implementation (Vadim)
-
-Source Tree Changes
--------------------
-HP-UX 10 patches (Vladimir Turin)
-Added SCO support, (Daniel Harris)
-MkLinux patches (Tatsuo Ishii)
-Change geometric box terminology from "length" to "width"(Thomas)
-Deprecate temporary unstored slope fields in geometric code(Thomas)
-Remove restart instructions from INSTALL(Bruce)
-Look in /usr/ucb first for install(Bruce)
-Fix c++ copy example code(Thomas)
-Add -o to psql manual page(Bruce)
-Prevent relname unallocated string length from being copied into database(Bruce)
-Cleanup for NAMEDATALEN use(Bruce)
-Fix pg_proc names over 15 chars in output(Bruce)
-Add strNcpy() function(Bruce)
-remove some (void) casts that are unnecessary(Bruce)
-new interfaces directory(Marc)
-Replace fopen() calls with calls to fd.c functions(Bruce)
-Make functions static where possible(Bruce)
-enclose unused functions in #ifdef NOT_USED(Bruce)
-Remove call to difftime() in timestamp support to fix SunOS(Bruce &amp; Thomas)
-Changes for Digital Unix
-Portability fix for pg_dumpall(Bruce)
-Rename pg_attribute.attnvals to attdispersion(Bruce)
-"intro/unix" manual page now "pgintro"(Bruce)
-"built-in" manual page now "pgbuiltin"(Bruce)
-"drop" manual page now "drop_table"(Bruce)
-Add "create_trigger", "drop_trigger" manual pages(Thomas)
-Add constraints regression test(Vadim &amp; Thomas)
-Add comments syntax regression test(Thomas)
-Add PGINDENT and support program(Bruce)
-Massive commit to run PGINDENT on all *.c and *.h files(Bruce)
-Files moved to /src/tools directory(Bruce)
-SPI and Trigger programming guides (Vadim &amp; D'Arcy)
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-<sect1 id="release-6-1-1">
-<title>Release 6.1.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1997-07-22</simpara>
-  </note>
-
-<sect2>
-<title>Migration from version 6.1 to version 6.1.1</title>
-
-<para>
-This is a minor bug-fix release. A dump/reload is not required from version 6.1,
-but is required from any release prior to 6.1.
-Refer to the release notes for 6.1 for more details.
-</para>
-</sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-fix for SET with options (Thomas)
-allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce)
-new psql \connect option allows changing usernames without changing databases
-fix for initdb --debug option(Yoshihiko Ichikawa))
-lextest cleanup(Bruce)
-hash fixes(Vadim)
-fix date/time month boundary arithmetic(Thomas)
-fix timezone daylight handling for some ports(Thomas, Bruce, Tatsuo)
-timestamp overhauled to use standard functions(Thomas)
-other code cleanup in date/time routines(Thomas)
-psql's \d now case-insensitive(Bruce)
-psql's backslash commands can now have trailing semicolon(Bruce)
-fix memory leak in psql when using \g(Bruce)
-major fix for endian handling of communication to server(Thomas, Tatsuo)
-Fix for Solaris assembler and include files(Yoshihiko Ichikawa)
-allow underscores in usernames(Bruce)
-pg_dumpall now returns proper status, portability fix(Bruce)
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-<sect1 id="release-6-1">
-<title>Release 6.1</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1997-06-08</simpara>
-  </note>
-
-<para>
- The regression tests have been adapted and extensively modified for the
- 6.1 release of <productname>PostgreSQL</productname>.
-</para>
-
-<para>
- Three new data types (<type>datetime</type>, <type>timespan</type>, and <type>circle</type>) have been added to
- the native set of <productname>PostgreSQL</productname> types. Points, boxes, paths, and polygons
- have had their output formats made consistent across the data types.
- The polygon output in misc.out has only been spot-checked for correctness
- relative to the original regression output.
-</para>
-
-<para>
- <productname>PostgreSQL</productname> 6.1 introduces a new, alternate
-optimizer which uses <firstterm>genetic</firstterm>
- algorithms. These algorithms introduce a random behavior in the ordering
- of query results when the query contains multiple qualifiers or multiple
- tables (giving the optimizer a choice on order of evaluation). Several
- regression tests have been modified to explicitly order the results, and
- hence are insensitive to optimizer choices. A few regression tests are
- for data types which are inherently unordered (e.g. points and time
- intervals) and tests involving those types are explicitly bracketed with
- <command>set geqo to 'off'</command> and <command>reset geqo</command>.
-</para>
-
-<para>
- The interpretation of array specifiers (the curly braces around atomic
- values) appears to have changed sometime after the original regression
- tests were generated. The current <filename>./expected/*.out</filename> files reflect this
- new interpretation, which might not be correct!
-</para>
-
-<para>
- The float8 regression test fails on at least some platforms. This is due
- to differences in implementations of <function>pow()</function> and <function>exp()</function> and the signaling
- mechanisms used for overflow and underflow conditions.
-</para>
-
-<para>
- The <quote>random</> results in the random test should cause the
- <quote>random</quote> test to be <quote>failed</quote>, since the
- regression tests are evaluated using a simple diff. However,
- <quote>random</> does not seem to produce random results on my test
- machine (Linux/<application>gcc</>/i686).
-</para>
-
-<sect2>
-<title>Migration to Version 6.1</title>
-
-<para>
-This migration requires a complete dump of the 6.0 database and a
-restore of the database in 6.1.
-</para>
-<para>
-Those migrating from earlier 1.* releases should first upgrade to 1.09
-because the COPY output format was improved from the 1.02 release.
-</para>
-</sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Bug Fixes
----------
-packet length checking in library routines
-lock manager priority patch
-check for under/over flow of float8(Bruce)
-multitable join fix(Vadim)
-SIGPIPE crash fix(Darren)
-large object fixes(Sven)
-allow btree indexes to handle NULLs(Vadim)
-timezone fixes(D'Arcy)
-select SUM(x) can return NULL on no rows(Thomas)
-internal optimizer, executor bug fixes(Vadim)
-fix problem where inner loop in &lt; or &lt;= has no rows(Vadim)
-prevent re-commuting join index clauses(Vadim)
-fix join clauses for multiple tables(Vadim)
-fix hash, hashjoin for arrays(Vadim)
-fix btree for abstime type(Vadim)
-large object fixes(Raymond)
-fix buffer leak in hash indexes (Vadim)
-fix rtree for use in inner scan (Vadim)
-fix gist for use in inner scan, cleanups (Vadim, Andrea)
-avoid unnecessary local buffers allocation (Vadim, Massimo)
-fix local buffers leak in transaction aborts (Vadim)
-fix file manager memmory leaks, cleanups (Vadim, Massimo)
-fix storage manager memmory leaks (Vadim)
-fix btree duplicates handling (Vadim)
-fix deleted rows reincarnation caused by vacuum (Vadim)
-fix SELECT varchar()/char() INTO TABLE made zero-length fields(Bruce)
-many psql, pg_dump, and libpq memory leaks fixed using Purify (Igor)
-
-Enhancements
-------------
-attribute optimization statistics(Bruce)
-much faster new btree bulk load code(Paul)
-BTREE UNIQUE added to bulk load code(Vadim)
-new lock debug code(Massimo)
-massive changes to libpg++(Leo)
-new GEQO optimizer speeds table multitable optimization(Martin)
-new WARN message for non-unique insert into unique key(Marc)
-update x=-3, no spaces, now valid(Bruce)
-remove case-sensitive identifier handling(Bruce,Thomas,Dan)
-debug backend now pretty-prints tree(Darren)
-new Oracle character functions(Edmund)
-new plaintext password functions(Dan)
-no such class or insufficient privilege changed to distinct messages(Dan)
-new ANSI timestamp function(Dan)
-new ANSI Time and Date types (Thomas)
-move large chunks of data in backend(Martin)
-multicolumn btree indexes(Vadim)
-new SET var TO value command(Martin)
-update transaction status on reads(Dan)
-new locale settings for character types(Oleg)
-new SEQUENCE serial number generator(Vadim)
-GROUP BY function now possible(Vadim)
-re-organize regression test(Thomas,Marc)
-new optimizer operation weights(Vadim)
-new psql \z grant/permit option(Marc)
-new MONEY data type(D'Arcy,Thomas)
-tcp socket communication speed improved(Vadim)
-new VACUUM option for attribute statistics, and for certain columns (Vadim)
-many geometric type improvements(Thomas,Keith)
-additional regression tests(Thomas)
-new datestyle variable(Thomas,Vadim,Martin)
-more comparison operators for sorting types(Thomas)
-new conversion functions(Thomas)
-new more compact btree format(Vadim)
-allow pg_dumpall to preserve database ownership(Bruce)
-new SET GEQO=# and R_PLANS variable(Vadim)
-old (!GEQO) optimizer can use right-sided plans (Vadim)
-typechecking improvement in SQL parser(Bruce)
-new SET, SHOW, RESET commands(Thomas,Vadim)
-new \connect database USER option
-new destroydb -i option (Igor)
-new \dt and \di psql commands (Darren)
-SELECT "\n" now escapes newline (A. Duursma)
-new geometry conversion functions from old format (Thomas)
-
-Source tree changes
--------------------
-new configuration script(Marc)
-readline configuration option added(Marc)
-OS-specific configuration options removed(Marc)
-new OS-specific template files(Marc)
-no more need to edit Makefile.global(Marc)
-re-arrange include files(Marc)
-nextstep patches (Gregor Hoffleit)
-removed Windows-specific code(Bruce)
-removed postmaster -e option, now only postgres -e option (Bruce)
-merge duplicate library code in front/backends(Martin)
-now works with eBones, international Kerberos(Jun)
-more shared library support
-c++ include file cleanup(Bruce)
-warn about buggy flex(Bruce)
-DG/UX, Ultrix, IRIX, AIX portability fixes
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-<sect1 id="release-6-0">
-<title>Release 6.0</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1997-01-29</simpara>
-  </note>
-
-<para>
-A dump/restore is required for those wishing to migrate data from
-previous releases of <productname>PostgreSQL</productname>.
-</para>
-
-<sect2>
-<title>Migration from version 1.09 to version 6.0</title>
-
-<para>
-This migration requires a complete dump of the 1.09 database and a
-restore of the database in 6.0.
-</para>
-</sect2>
-
-<sect2>
-<title>Migration from pre-1.09 to version 6.0</title>
-
-<para>
-Those migrating from earlier 1.* releases should first upgrade to 1.09
-because the COPY output format was improved from the 1.02 release.
-</para>
-</sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <para>
-<programlisting>
-Bug Fixes
----------
-ALTER TABLE bug - running postgres process needs to re-read table definition
-Allow vacuum to be run on one table or entire database(Bruce)
-Array fixes
-Fix array over-runs of memory writes(Kurt)
-Fix elusive btree range/non-range bug(Dan)
-Fix for hash indexes on some types like time and date
-Fix for pg_log size explosion
-Fix permissions on lo_export()(Bruce)
-Fix uninitialized reads of memory(Kurt)
-Fixed ALTER TABLE ... char(3) bug(Bruce)
-Fixed a few small memory leaks
-Fixed EXPLAIN handling of options and changed full_path option name
-Fixed output of group acl privileges
-Memory leaks (hunt and destroy with tools like Purify(Kurt)
-Minor improvements to rules system
-NOTIFY fixes
-New asserts for run-checking
-Overhauled parser/analyze code to properly report errors and increase speed
-Pg_dump -d now handles NULL's properly(Bruce)
-Prevent SELECT NULL from crashing server (Bruce)
-Properly report errors when INSERT ... SELECT columns did not match
-Properly report errors when insert column names were not correct
-psql \g filename now works(Bruce)
-psql fixed problem with multiple statements on one line with multiple outputs
-Removed duplicate system OIDs
-SELECT * INTO TABLE . GROUP/ORDER BY gives unlink error if table exists(Bruce)
-Several fixes for queries that crashed the backend
-Starting quote in insert string errors(Bruce)
-Submitting an empty query now returns empty status, not just " " query(Bruce)
-
-Enhancements
-------------
-Add EXPLAIN manual page(Bruce)
-Add UNIQUE index capability(Dan)
-Add hostname/user level access control rather than just hostname and user
-Add synonym of != for &lt;&gt;(Bruce)
-Allow "select oid,* from table"
-Allow BY,ORDER BY to specify columns by number, or by non-alias table.column(Bruce)
-Allow COPY from the frontend(Bryan)
-Allow GROUP BY to use alias column name(Bruce)
-Allow actual compression, not just reuse on the same page(Vadim)
-Allow installation-configuration option to auto-add all local users(Bryan)
-Allow libpq to distinguish between text value '' and null(Bruce)
-Allow non-postgres users with createdb privs to destroydb's
-Allow restriction on who can create C functions(Bryan)
-Allow restriction on who can do backend COPY(Bryan)
-Can shrink tables, pg_time and pg_log(Vadim &amp; Erich)
-Change debug level 2 to print queries only, changed debug heading layout(Bruce)
-Change default decimal constant representation from float4 to float8(Bruce)
-European date format now set when postmaster is started
-Execute lowercase function names if not found with exact case
-Fixes for aggregate/GROUP processing, allow 'select sum(func(x),sum(x+y) from z'
-Gist now included in the distribution(Marc)
-Idend authentication of local users(Bryan)
-Implement BETWEEN qualifier(Bruce)
-Implement IN qualifier(Bruce)
-libpq has PQgetisnull()(Bruce)
-libpq++ improvements
-New options to initdb(Bryan)
-Pg_dump allow dump of OIDs(Bruce)
-Pg_dump create indexes after tables are loaded for speed(Bruce)
-Pg_dumpall dumps all databases, and the user table
-Pginterface additions for NULL values(Bruce)
-Prevent postmaster from being run as root
-psql \h and \? is now readable(Bruce)
-psql allow backslashed, semicolons anywhere on the line(Bruce)
-psql changed command prompt for lines in query or in quotes(Bruce)
-psql char(3) now displays as (bp)char in \d output(Bruce)
-psql return code now more accurate(Bryan?)
-psql updated help syntax(Bruce)
-Re-visit and fix vacuum(Vadim)
-Reduce size of regression diffs, remove timezone name difference(Bruce)
-Remove compile-time parameters to enable binary distributions(Bryan)
-Reverse meaning of HBA masks(Bryan)
-Secure Authentication of local users(Bryan)
-Speed up vacuum(Vadim)
-Vacuum now had VERBOSE option(Bruce)
-
-Source tree changes
--------------------
-All functions now have prototypes that are compared against the calls
-Allow asserts to be disabled easily from Makefile.global(Bruce)
-Change oid constants used in code to #define names
-Decoupled sparc and solaris defines(Kurt)
-Gcc -Wall compiles cleanly with warnings only from unfixable constructs
-Major include file reorganization/reduction(Marc)
-Make now stops on compile failure(Bryan)
-Makefile restructuring(Bryan, Marc)
-Merge bsdi_2_1 to bsdi(Bruce)
-Monitor program removed
-Name change from Postgres95 to PostgreSQL
-New config.h file(Marc, Bryan)
-PG_VERSION now set to 6.0 and used by postmaster
-Portability additions, including Ultrix, DG/UX, AIX, and Solaris
-Reduced the number of #define's, centralized #define's
-Remove duplicate OIDS in system tables(Dan)
-Remove duplicate system catalog info or report mismatches(Dan)
-Removed many os-specific #define's
-Restructured object file generation/location(Bryan, Marc)
-Restructured port-specific file locations(Bryan, Marc)
-Unused/uninitialized variables corrected
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-<sect1 id="release-1-09">
-<title>Release 1.09</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1996-11-04</simpara>
-  </note>
-
-<para>
-Sorry, we didn't keep track of changes from 1.02 to 1.09.  Some of
-the changes listed in 6.0 were actually included in the 1.02.1 to 1.09
-releases.
-</para>
-</sect1>
-
-<sect1 id="release-1-02">
-<title>Release 1.02</title>
-
-  <note>
-  <title>Release Date</title>
-  <simpara>1996-08-01</simpara>
-  </note>
-
-<sect2>
-<title>Migration from version 1.02 to version 1.02.1</title>
-
-<para>
-Here is a new migration file for 1.02.1.  It includes the 'copy' change
-and a script to convert old <acronym>ASCII</acronym> files.
-</para>
-<note>
-<para>
-The following notes are for the benefit of users who want to migrate
-databases from <productname>Postgres95</> 1.01 and 1.02 to <productname>Postgres95</> 1.02.1.
-</para>
-<para>
-If you are starting afresh with <productname>Postgres95</> 1.02.1 and do not need
-to migrate old databases, you do not need to read any further.
-</para>
-</note>
-
-<para>
-In order to upgrade older <productname>Postgres95</> version 1.01 or 1.02 databases to
-version 1.02.1, the following steps are required:
-</para>
-<procedure>
-<step>
-<para>
-Start up a new 1.02.1 postmaster
-</para>
-</step>
-<step>
-<para>
-Add the new built-in functions and operators of 1.02.1 to 1.01 or 1.02
-  databases.  This is done by running the new 1.02.1 server against
-  your own 1.01 or 1.02 database and applying the queries attached at
-  the end of the file.   This can be done easily through <command>psql</>.  If your
-  1.01 or 1.02 database is named <literal>testdb</literal> and you have cut the commands
-  from the end of this file and saved them in <filename>addfunc.sql</filename>:
-<programlisting>
-% psql testdb -f addfunc.sql
-</programlisting>
-
-Those upgrading 1.02 databases will get a warning when executing the
-last two statements in the file because they are already present in 1.02.  This is
-not a cause for concern.
-</para>
-</step>
-</procedure>
-</sect2>
-
-<sect2>
-<title>Dump/Reload Procedure</title>
-
-<para>
-If you are trying to reload a pg_dump or text-mode, <literal>copy tablename to
-stdout</literal> generated with a previous version, you will need to run the
-attached <command>sed</command> script on the ASCII file before loading it into the
-database.  The old format used '.' as end-of-data, while '\.' is now the
-end-of-data marker.  Also, empty strings are now loaded in as '' rather
-than NULL. See the copy manual page for full details.
-
-<programlisting>
-sed 's/^\.$/\\./g' &lt;in_file &gt;out_file
-</programlisting>
-</para>
-<para>
-If you are loading an older binary copy or non-<systemitem>stdout</> copy, there is no
-end-of-data character, and hence no conversion necessary.
-
-<programlisting>
--- following lines added by agc to reflect the case-insensitive
--- regexp searching for varchar (in 1.02), and bpchar (in 1.02.1)
-create operator ~* (leftarg = bpchar, rightarg = text, procedure = texticregexeq);
-create operator !~* (leftarg = bpchar, rightarg = text, procedure = texticregexne);
-create operator ~* (leftarg = varchar, rightarg = text, procedure = texticregexeq);
-create operator !~* (leftarg = varchar, rightarg = text, procedure = texticregexne);
-</programlisting>
-</para>
-</sect2>
-
-<sect2>
-<title>Changes</title>
-
-<para>
-<programlisting>
-Source code maintenance and development
- * worldwide team of volunteers
- * the source tree now in CVS at ftp.ki.net
-
-Enhancements
- * psql (and underlying libpq library) now has many more options for
-   formatting output, including HTML
- * pg_dump now output the schema and/or the data, with many fixes to
-   enhance completeness.
- * psql used in place of monitor in administration shell scripts.
-   monitor to be deprecated in next release.
- * date/time functions enhanced
- * NULL insert/update/comparison fixed/enhanced
- * TCL/TK lib and shell fixed to work with both tck7.4/tk4.0 and tcl7.5/tk4.1
-
-Bug Fixes (almost too numerous to mention)
- * indexes
- * storage management
- * check for NULL pointer before dereferencing
- * Makefile fixes
-
-New Ports
- * added SolarisX86 port
- * added BSD/OS 2.1 port
- * added DG/UX port
-</programlisting>
-</para>
-<!--
-Contributors (apologies to any missed)
- * Kurt J. Lidl &lt;[email protected]&gt;
-        (missed in first run, but no less important)
- * Erich Stamberger &lt;[email protected]&gt;
- * Jason Wright &lt;[email protected]&gt;
- * Cees de Groot &lt;[email protected]&gt;
- * [email protected]
- * [email protected] (Michael Siebenborn (6929))
- * Brian E. Gallew &lt;[email protected]&gt;
- * Vadim B. Mikheev &lt;[email protected]&gt;
- * Adam Sussman &lt;[email protected]&gt;
- * Chris Dunlop &lt;[email protected]&gt;
- * Marc G. Fournier &lt;[email protected]&gt;
- * Dan McGuirk &lt;[email protected]&gt;
- * Dr_George_D_Detlefsen &lt;[email protected]&gt;
- * Erich Stamberger &lt;[email protected]&gt;
- * Massimo Dal Zotto &lt;[email protected]&gt;
- * Randy Kunkee &lt;[email protected]&gt;
- * Rick Weldon &lt;[email protected]&gt;
- * Thomas van Reimersdahl &lt;[email protected]&gt;
- * david bennett &lt;[email protected]&gt;
- * [email protected]
- * Julian Assange &lt;[email protected]&gt;
- * Bruce Momjian &lt;[email protected]&gt;
- * Paul "Shag" Walmsley &lt;[email protected]&gt;
- * "Alistair G. Crooks" &lt;[email protected]&gt;
--->
-</sect2>
-</sect1>
-
-<sect1 id="release-1-01">
-<title>Release 1.01</title>
-
-   <note>
-   <title>Release Date</title>
-   <simpara>1996-02-23</simpara>
-   </note>
-
-
-<sect2>
-<title>Migration from version 1.0 to version 1.01</title>
-
-<para>
-The following notes are for the benefit of users who want to migrate
-databases from <productname>Postgres95</> 1.0 to <productname>Postgres95</> 1.01.
-</para>
-<para>
-If you are starting afresh with <productname>Postgres95</> 1.01 and do not need
-to migrate old databases, you do not need to read any further.
-</para>
-<para>
-In order to <productname>Postgres95</> version 1.01 with databases created with
-<productname>Postgres95</> version 1.0, the following steps are required:
-</para>
-<procedure>
-<step>
-<para>
-Set the definition of <symbol>NAMEDATALEN</symbol> in <filename>src/Makefile.global</filename> to 16
-   and <symbol>OIDNAMELEN</symbol> to 20.
-</para>
-</step>
-<step>
-<para>
-Decide whether you want to use Host based authentication.
-</para>
-<substeps>
-<step>
-<para>
-If you do, you must create a file name <literal>pg_hba</literal> in your top-level data
-   directory (typically the value of your <envar>$PGDATA</envar>).  <filename>src/libpq/pg_hba</filename>
-   shows an example syntax.
-</para>
-</step>
-<step>
-<para>
-If you do not want host-based authentication, you can comment out
-   the line:
-<programlisting>
-HBA = 1
-</programlisting>
-   in <filename>src/Makefile.global</filename>
-</para>
-<para>
-   Note that host-based authentication is turned on by default, and if
-   you do not take steps A or B above, the out-of-the-box 1.01 will
-   not allow you to connect to 1.0 databases.
-</para>
-</step>
-</substeps>
-</step>
-
-<step>
-<para>
-Compile and install 1.01, but DO NOT do the <command>initdb</command> step.
-</para>
-</step>
-<step>
-<para>
-Before doing anything else, terminate your 1.0 postmaster, and
-   backup your existing <envar>$PGDATA</envar> directory.
-</para>
-</step>
-<step>
-<para>
-Set your <envar>PGDATA</envar> environment variable to your 1.0 databases, but set up
-   path up so that 1.01 binaries are being used.
-</para>
-</step>
-<step>
-<para>
-Modify the file <filename><envar>$PGDATA</envar>/PG_VERSION</filename> from 5.0 to 5.1
-</para>
-</step>
-<step>
-<para>
-Start up a new 1.01 postmaster
-</para>
-</step>
-<step>
-<para>
-Add the new built-in functions and operators of 1.01 to 1.0
-   databases.  This is done by running the new 1.01 server against
-   your own 1.0 database and applying the queries attached and saving
-   in the file 1.0_to_1.01.sql.   This can be done easily through <command>psql</command>.
-   If your 1.0 database is name <literal>testdb</literal>:
-
-<programlisting>
-% psql testdb -f 1.0_to_1.01.sql
-</programlisting>
-
-and then execute the following commands (cut and paste from here):
-
-<programlisting>
--- add builtin functions that are new to 1.01
-
-create function int4eqoid (int4, oid) returns bool as 'foo'
-language 'internal';
-create function oideqint4 (oid, int4) returns bool as 'foo'
-language 'internal';
-create function char2icregexeq (char2, text) returns bool as 'foo'
-language 'internal';
-create function char2icregexne (char2, text) returns bool as 'foo'
-language 'internal';
-create function char4icregexeq (char4, text) returns bool as 'foo'
-language 'internal';
-create function char4icregexne (char4, text) returns bool as 'foo'
-language 'internal';
-create function char8icregexeq (char8, text) returns bool as 'foo'
-language 'internal';
-create function char8icregexne (char8, text) returns bool as 'foo'
-language 'internal';
-create function char16icregexeq (char16, text) returns bool as 'foo'
-language 'internal';
-create function char16icregexne (char16, text) returns bool as 'foo'
-language 'internal';
-create function texticregexeq (text, text) returns bool as 'foo'
-language 'internal';
-create function texticregexne (text, text) returns bool as 'foo'
-language 'internal';
-
--- add builtin functions that are new to 1.01
-
-create operator = (leftarg = int4, rightarg = oid, procedure = int4eqoid);
-create operator = (leftarg = oid, rightarg = int4, procedure = oideqint4);
-create operator ~* (leftarg = char2, rightarg = text, procedure = char2icregexeq);
-create operator !~* (leftarg = char2, rightarg = text, procedure = char2icregexne);
-create operator ~* (leftarg = char4, rightarg = text, procedure = char4icregexeq);
-create operator !~* (leftarg = char4, rightarg = text, procedure = char4icregexne);
-create operator ~* (leftarg = char8, rightarg = text, procedure = char8icregexeq);
-create operator !~* (leftarg = char8, rightarg = text, procedure = char8icregexne);
-create operator ~* (leftarg = char16, rightarg = text, procedure = char16icregexeq);
-create operator !~* (leftarg = char16, rightarg = text, procedure = char16icregexne);
-create operator ~* (leftarg = text, rightarg = text, procedure = texticregexeq);
-create operator !~* (leftarg = text, rightarg = text, procedure = texticregexne);
-</programlisting>
-</para>
-</step>
-</procedure>
-</sect2>
-
-<sect2>
-<title>Changes</title>
-
-<para>
-<programlisting>
-Incompatibilities:
- * 1.01 is backwards compatible with 1.0 database provided the user
-   follow the steps outlined in the MIGRATION_from_1.0_to_1.01 file.
-   If those steps are not taken, 1.01 is not compatible with 1.0 database.
-
-Enhancements:
- * added PQdisplayTuples() to libpq and changed monitor and psql to use it
- * added NeXT port (requires SysVIPC implementation)
- * added CAST .. AS ... syntax
- * added ASC and DESC key words
- * added 'internal' as a possible language for CREATE FUNCTION
-   internal functions are C functions which have been statically linked
-   into the postgres backend.
- * a new type "name" has been added for system identifiers (table names,
-   attribute names, etc.)  This replaces the old char16 type.   The
-   of name is set by the NAMEDATALEN #define in src/Makefile.global
- * a readable reference manual that describes the query language.
- * added host-based access control.  A configuration file ($PGDATA/pg_hba)
-   is used to hold the configuration data.  If host-based access control
-   is not desired, comment out HBA=1 in src/Makefile.global.
- * changed regex handling to be uniform use of Henry Spencer's regex code
-   regardless of platform.  The regex code is included in the distribution
- * added functions and operators for case-insensitive regular expressions.
-   The operators are ~* and !~*.
- * pg_dump uses COPY instead of SELECT loop for better performance
-
-Bug fixes:
- * fixed an optimizer bug that was causing core dumps when
-   functions calls were used in comparisons in the WHERE clause
- * changed all uses of getuid to geteuid so that effective uids are used
- * psql now returns non-zero status on errors when using -c
- * applied public patches 1-14
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-<sect1 id="release-1-0">
-<title>Release 1.0</title>
-
-   <note>
-   <title>Release Date</title>
-   <simpara>1995-09-05</simpara>
-   </note>
-
-<sect2>
-<title>Changes</title>
-
-<para>
-<programlisting>
-Copyright change:
- * The copyright of <productname>Postgres</productname> 1.0 has been loosened to be freely modifiable
-   and modifiable for any purpose.  Please read the COPYRIGHT file.
-   Thanks to Professor Michael Stonebraker for making this possible.
-
-Incompatibilities:
- *  date formats have to be MM-DD-YYYY (or DD-MM-YYYY if you're using
-   EUROPEAN STYLE).  This follows SQL-92 specs.
- *  "delimiters" is now a key word
-
-Enhancements:
- *  sql LIKE syntax has been added
- *  copy command now takes an optional USING DELIMITER specification.
-   delimiters can be any single-character string.
- *  IRIX 5.3 port has been added.
-   Thanks to Paul Walmsley and others.
- *  updated pg_dump to work with new libpq
- *  \d has been added psql
-   Thanks to Keith Parks
- *  regexp performance for architectures that use POSIX regex has been
-   improved due to caching of precompiled patterns.
-   Thanks to Alistair Crooks
- *  a new version of libpq++
-   Thanks to William Wanders
-
-Bug fixes:
- *  arbitrary userids can be specified in the createuser script
- *  \c to connect to other databases in psql now works.
- *  bad pg_proc entry for float4inc() is fixed
- *  users with usecreatedb field set can now create databases without
-   having to be usesuper
- *  remove access control entries when the entry no longer has any
-   privileges
- *  fixed non-portable datetimes implementation
- *  added kerberos flags to the src/backend/Makefile
- *  libpq now works with kerberos
- *  typographic errors in the user manual have been corrected.
- *  btrees with multiple index never worked, now we tell you they don't
-   work when you try to use them
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-<sect1 id="release-0-03">
-<title><productname>Postgres95</productname> Release 0.03</title>
-
-   <note>
-   <title>Release Date</title>
-   <simpara>1995-07-21</simpara>
-   </note>
-
-<sect2>
-<title>Changes</title>
-<para>
-<programlisting>
-Incompatible changes:
- * BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS VERSIONS
-   (due to system catalog changes and indexing structure changes).
- * double-quote (") is deprecated as a quoting character for string literals;
-   you need to convert them to single quotes ('). <!-- " -->
- * name of aggregates (eg. int4sum) are renamed in accordance with the
-   SQL standard (eg. sum).
- * CHANGE ACL syntax is replaced by GRANT/REVOKE syntax.
- * float literals (eg. 3.14) are now of type float4 (instead of float8 in
-   previous releases); you might have to do typecasting if you depend on it
-   being of type float8.  If you neglect to do the typecasting and you assign
-   a float literal to a field of type float8, you might get incorrect values
-   stored!
- * LIBPQ has been totally revamped so that frontend applications
-   can connect to multiple backends
- * the usesysid field in pg_user has been changed from int2 to int4 to
-   allow wider range of Unix user ids.
- * the netbsd/freebsd/bsd o/s ports have been consolidated into a
-   single BSD44_derived port.  (thanks to Alistair Crooks)
-
-SQL standard-compliance (the following details changes that makes postgres95
-more compliant to the SQL-92 standard):
- * the following SQL types are now built-in: smallint, int(eger), float, real,
-   char(N), varchar(N), date and time.
-
-   The following are aliases to existing postgres types:
-                smallint -&gt; int2
-                integer, int -&gt; int4
-                float, real  -&gt; float4
-   char(N) and varchar(N) are implemented as truncated text types. In
-   addition, char(N) does blank-padding.
- * single-quote (') is used for quoting string literals; '' (in addition to
-   \') is supported as means of inserting a single quote in a string
- * SQL standard aggregate names (MAX, MIN, AVG, SUM, COUNT) are used
-   (Also, aggregates can now be overloaded, i.e. you can define your
-   own MAX aggregate to take in a user-defined type.)
- * CHANGE ACL removed. GRANT/REVOKE syntax added.
-   - Privileges can be given to a group using the "GROUP" key word.
-        For example:
-                GRANT SELECT ON foobar TO GROUP my_group;
-        The key word 'PUBLIC' is also supported to mean all users.
-
-        Privileges can only be granted or revoked to one user or group
-        at a time.
-
-        "WITH GRANT OPTION" is not supported.  Only class owners can change
-        access control
-   - The default access control is to grant users readonly access.
-     You must explicitly grant insert/update access to users.  To change
-     this, modify the line in
-                src/backend/utils/acl.h
-     that defines ACL_WORLD_DEFAULT
-
-Bug fixes:
- * the bug where aggregates of empty tables were not run has been fixed. Now,
-   aggregates run on empty tables will return the initial conditions of the
-   aggregates. Thus, COUNT of an empty  table will now properly return 0.
-   MAX/MIN of an empty table will return a row of value NULL.
- * allow the use of \; inside the monitor
- * the LISTEN/NOTIFY asynchronous notification mechanism now work
- * NOTIFY in rule action bodies now work
- * hash indexes work, and access methods in general should perform better.
-   creation of large btree indexes should be much faster.  (thanks to Paul
-   Aoki)
-
-Other changes and enhancements:
- * addition of an EXPLAIN statement used for explaining the query execution
-   plan (eg. "EXPLAIN SELECT * FROM EMP" prints out the execution plan for
-   the query).
- * WARN and NOTICE messages no longer have timestamps on them. To turn on
-   timestamps of error messages, uncomment the line in
-   src/backend/utils/elog.h:
-        /* define ELOG_TIMESTAMPS */
- * On an access control violation, the message
-        "Either no such class or insufficient privilege"
-   will be given.  This is the same message that is returned when
-   a class is not found.  This dissuades non-privileged users from
-   guessing the existence of privileged classes.
- * some additional system catalog changes have been made that are not
-   visible to the user.
-
-libpgtcl changes:
- * The -oid option has been added to the "pg_result" tcl command.
-   pg_result -oid returns oid of the last row inserted.   If the
-   last command was not an INSERT, then pg_result -oid returns "".
- * the large object interface is available as pg_lo* tcl commands:
-   pg_lo_open, pg_lo_close, pg_lo_creat, etc.
-
-Portability enhancements and New Ports:
- * flex/lex problems have been cleared up.  Now, you should be able to use
-   flex instead of lex on any platforms.  We no longer make assumptions of
-   what lexer you use based on the platform you use.
- * The Linux-ELF port is now supported.  Various configuration have been
-   tested:  The following configuration is known to work:
-        kernel 1.2.10, gcc 2.6.3, libc 4.7.2, flex 2.5.2, bison 1.24
-   with everything in ELF format,
-
-New utilities:
- * ipcclean added to the distribution
-   ipcclean usually does not need to be run, but if your backend crashes
-   and leaves shared memory segments hanging around, ipcclean will
-   clean them up for you.
-
-New documentation:
- * the user manual has been revised and libpq documentation added.
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-<sect1 id="release-0-02">
-<title><productname>Postgres95</productname> Release 0.02</title>
-
-   <note>
-   <title>Release Date</title>
-   <simpara>1995-05-25</simpara>
-   </note>
-
-<sect2>
-<title>Changes</title>
-
-<para>
-<programlisting>
-Incompatible changes:
- * The SQL statement for creating a database is 'CREATE DATABASE' instead
-   of 'CREATEDB'. Similarly, dropping a database is 'DROP DATABASE' instead
-   of 'DESTROYDB'. However, the names of the executables 'createdb' and
-   'destroydb' remain the same.
-
-New tools:
- * pgperl - a Perl (4.036) interface to Postgres95
- * pg_dump - a utility for dumping out a postgres database into a
-        script file containing query commands. The script files are in a ASCII
-        format and can be used to reconstruct the database, even on other
-        machines and other architectures. (Also good for converting
-        a Postgres 4.2 database to Postgres95 database.)
-
-The following ports have been incorporated into postgres95-beta-0.02:
- * the NetBSD port by Alistair Crooks
- * the AIX port by Mike Tung
- * the Windows NT port by Jon Forrest (more stuff but not done yet)
- * the Linux ELF port by Brian Gallew
-
-The following bugs have been fixed in postgres95-beta-0.02:
- * new lines not escaped in COPY OUT and problem with COPY OUT when first
-   attribute is a '.'
- * cannot type return to use the default user id in createuser
- * SELECT DISTINCT on big tables crashes
- * Linux installation problems
- * monitor doesn't allow use of 'localhost' as PGHOST
- * psql core dumps when doing \c or \l
- * the "pgtclsh" target missing from src/bin/pgtclsh/Makefile
- * libpgtcl has a hard-wired default port number
- * SELECT DISTINCT INTO TABLE hangs
- * CREATE TYPE doesn't accept 'variable' as the internallength
- * wrong result using more than 1 aggregate in a SELECT
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
-<sect1 id="release-0-01">
-<title><productname>Postgres95</productname> Release 0.01</title>
-
-   <note>
-   <title>Release Date</title>
-   <simpara>1995-05-01</simpara>
-   </note>
-
-<para>
-Initial release.
-</para>
-</sect1>
-
-<![IGNORE[
-  <sect1 id="timing-results">
-   <title>Timing Results</title>
-
-   <para>
-    These timing results are from running the regression test with the commands
-
-<programlisting>
-% cd src/test/regress
-% make all
-% time make runtest
-</programlisting>
-   </para>
-   <para>
-    Timing under Linux 2.0.27 seems to have a roughly 5% variation from run
-    to run, presumably due to the scheduling vagaries of multitasking systems.
-   </para>
-
-   <sect2>
-    <title>Version 6.5</title>
-
-    <para>
-     As has been the case for previous releases, timing between
-     releases is not directly comparable since new regression tests
-     have been added. In general, 6.5 is faster than previous
-     releases.
-    </para>
-
-    <para>
-     Timing with <function>fsync()</function> disabled:
-
-<literallayout class="monospaced">
-Time   System
-02:00  Dual Pentium Pro 180, 224MB, UW-SCSI, Linux 2.0.36, gcc 2.7.2.3 -O2 -m486
-04:38  Sparc Ultra 1 143MHz, 64MB, Solaris 2.6
-</literallayout>
-    </para>
-
-    <para>
-     Timing with <function>fsync()</function> enabled:
-
-<literallayout class="monospaced">
-Time   System
-04:21  Dual Pentium Pro 180, 224MB, UW-SCSI, Linux 2.0.36, gcc 2.7.2.3 -O2 -m486
-</literallayout>
-
-     For the <systemitem class="osname">Linux</systemitem> system above, using <acronym>UW-SCSI</acronym> disks rather than (older) <acronym>IDE</acronym>
-     disks leads to a 50% improvement in speed on the regression test.
-    </para>
-   </sect2>
-
-<sect2>
-<title>Version 6.4beta</title>
-
-<para>
-The times for this release are not directly comparable to those for previous releases
-since some additional regression tests have been included.
-In general, however, 6.4 should be slightly faster than the previous release (thanks, Bruce!).
-</para>
-<para>
-<literallayout class="monospaced">
-Time   System
-02:26  Dual Pentium Pro 180, 96MB, UW-SCSI, Linux 2.0.30, gcc 2.7.2.1 -O2 -m486
-</literallayout>
-</para>
-</sect2>
-
-<sect2>
-<title>Version 6.3</title>
-
-<para>
-The times for this release are not directly comparable to those for previous releases
-since some additional regression tests have been included and some obsolete tests involving
-time travel have been removed.
-In general, however, 6.3 is substantially faster than previous releases (thanks, Bruce!).
-</para>
-<para>
-<programlisting>
-  Time   System
-  02:30  Dual Pentium Pro 180, 96MB, UW-SCSI, Linux 2.0.30, gcc 2.7.2.1 -O2 -m486
-  04:12  Dual Pentium Pro 180, 96MB, EIDE, Linux 2.0.30, gcc 2.7.2.1 -O2 -m486
-</programlisting>
-</para>
-</sect2>
-
-<sect2>
-<title>Version 6.1</title>
-
-<para>
-<programlisting>
-  Time   System
-  06:12  Pentium Pro 180, 32MB, EIDE, Linux 2.0.30, gcc 2.7.2 -O2 -m486
-  12:06  P-100, 48MB, Linux 2.0.29, gcc
-  39:58  Sparc IPC 32MB, Solaris 2.5, gcc 2.7.2.1 -O -g
-</programlisting>
-</para>
-</sect2>
-</sect1>
-]]>
diff --git a/doc-xc/src/sgml/release-xc-1.0.sgmlin b/doc-xc/src/sgml/release-xc-1.0.sgmlin
deleted file mode 100644
index 1379929916..0000000000
--- a/doc-xc/src/sgml/release-xc-1.0.sgmlin
+++ /dev/null
@@ -1,1214 +0,0 @@
-<!-- doc/src/sgml/release-xc-1.0.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-xc-1-0-1">
-  <title>Release 1.0.1</title>
-
-  <note>
-   <title>Release Date</title>
-   <simpara>2012-09-??</simpara>
-  </note>
-
-  <para>
-   This release contains a variety of fixes from 1.0.0.
-   For information about new features in the 1.0 major release, see
-   <xref linkend="release-xc-1-0">.
-  </para>
-
-  <sect2>
-   <title>Migration to Version 1.0.1</title>
-
-   <para>
-    A dump/restore is not required for those running 1.0.X.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
-
-   <itemizedlist>
-
-    <listitem>
-     <para>
-      Make data ordering consistent in query for test <filename>join.sql</> (Michael Paquier)
-     </para>
-
-     <para>
-      Regression test join failed occasionally depending on the cluster
-      configuration.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix for sequence removal on GTM when related database is dropped
-      (Michael Paquier, Dimitrije Radojevic)
-     </para>
-
-     <para>
-      There was an error on GTM side when comparing sequence key strings
-      related to key size when sequence drop is based on a sequence key type
-      GTM_SEQ_DB_NAME.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix for <literal>INSERT SELECT</> for partially replicated tables.
-      Remote DML planning was not taking into account the node list
-      to be used on a relation when modifying data on it. (Michael Paquier)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Push -l option of <command>gtm_ctl</> to gtm (Michael Meskes).
-     </para>
-
-     <para>
-      This avoids to have an empty output file when <command>gtm_ctl</> has a log file defined
-      and change log file name of GTM according to what is given by <command>gtm_ctl</>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix for crash at gtm_proxy startup in 32b-linux machines (Koichi Suzuki, Plexo Rama)
-     </para>
-
-     <para>
-      This fix adds an additional boolean flag in GTM-Proxy thread info
-      to make it similar to the one used in GTM. The problem which was
-      happening was that GTM-Proxy tried to use the memory structure of
-      the thread info of GTM.
-      Crash problems are solved but we should find in the future a smarter
-      way to manage GTM and GTM-Proxy memory allocation APIs as they are
-      now strongly dependant on each other and we may find similar issues
-      if some new developments are done on GTM and/or GTM-Proxy.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Activate <command>gtm_ctl</> status (Koichi Suzuki, Michael Paquier)
-     </para>
-
-     <para>
-      <command>gtm_ctl</> can control the status of a GTM server like <command>
-      pg_ctl</> does with <productname>PostgreSQL</> instances (in the case of <productname>
-      Postgres-XC</> Coordinator and Datanode).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix for incorrect <literal>COPY</> for partially distributed tables (Michael Paquier)
-     </para>
-
-     <para>
-      When a table was distributed on a portion of nodes. <literal>COPY</> process
-      was not correctly choosing the output node during a <literal>COPY TO</>. This
-      problem has been put into light by a case where table was replicated
-      without using the first datanode of the cluster. It happened that
-      there was the same problem for hash/modulo tables as well.
-      A test case in xc_copy has been added to cover this problem, and
-      a small portion managing <literal>COPY TO</> in <filename>execRemote.c</> has been cleaned.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Correct whitespaces, format and message format in <filename>gtm_client.c</> (Andrei Martsinchyk)
-     </para>
-
-     <para>
-      This had consequences on the data types of the values sent by
-      GTM which was not matching those GTM Standby was trying to read.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Solve SEGENV for GTM-Standby (Andrei Martsinchyk)
-     </para>
-
-     <para>
-      Wrong variable was referenced when writing terminating null at the
-      end of a string. It caused seg faults, because the referenced variable
-      was not initialized yet.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Introduce new GTM thread status managing thread backup (Andrei Martsinchyk)
-     </para>
-
-     <para>
-      In the case of a GTM standby crash during the initial backup, the
-      master GTM remained locked. The origin of this problem was during
-      GTM backup process, where GTM locks all its threads one by one,
-      performs a backup and then releases everything.
-      This commit adds an additional control layer able to detect the
-      thread status during backup. The new status GTM_THREAD_BACKUP is
-      introduced for this purpose. Once backup is performed, the thread
-      status is changed to GTM_THREAD_RUNNING.
-      Hence, if the handler (GTM) is invoked upon sudden disconnection for
-      backend (here GTM-Standby) disconnect of its connection and it sees
-      that the current thread has status GTM_THREAD_BACKUP it goes ahead
-      and releases the locks.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Release GTM thread lock before exit (Andrei Martsinchyk)
-     </para>
-
-     <para>
-      This avoid to have another thread waiting for it, as it is possible
-      it waits for it.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Block GXID generation on standbys (Andrei Martsinchyk)
-     </para>
-
-     <para>
-      If a node accidentally connects to the Standby and reconnects to the
-      Master afterwards, it will get an inconsistent GXID value since GTM
-      Master is not aware of GXIDs generated by GTM Standby.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      validate_part_col_updatable was falsely assuming that the table with no
-      location info is as good as non-existent table. This assumption is not true for
-      catalogs or coordinator only tables. In such cases, this function should not look for any
-      distribution column, since one can not exist for a table local to the
-      coordinator (Ashutosh Bapat)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix for bug 3556031: pgadmin3 connection error (Michael Paquier)
-     </para>
-
-     <para>
-      pgadmin3 parses the output of <literal>SELECT version()</> to determine
-      the server version it is connecting to. For Postgres-XC, this
-      output result was changed and completed with Postgres-XC and
-      PostgreSQL version. pgadmin thought that the version of server
-      was the one of <productname>Postgres-XC</>, meaning 1.0 for 1.0 stable
-      and 1.1 for master branch. In consequence to that, SQL queries with
-      very old catalog were run to server, and of course errors were reported
-      to client and pgadmin could not work correctly.
-      This is solved with changing back version() to its former output.
-      An additional function <function>pgxc_version()</> is added to provide a way
-      for application to inform about <productname>Postgres-XC</> version and
-      the <productname>PostgreSQL</> version it is based on.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Refactoring of <filename>pg_regress.c</> due to bugs with O2 compilation (Michael Paquier)
-     </para>
-
-     <para>
-      When code was being compiled with O2, initialization and start-up
-      of GTM was done twice, creating errors in log files.
-      In consequence, functions related to start and initialization of
-      PGXC nodes and GTM are unified to clarify code and additional checks
-      are added to verify that nodes have been correctly started.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix compilation flag O2 not set in CFLAGS at configure step by default (Michael Paquier)
-     </para>
-
-     <para>
-      The flag -DPGXC is mandatory for correct compilation and is set once
-      all the compilation flags have been determined.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Block <literal>EXECUTE DIRECT</> when used from a Datanode (Michael Paquier)
-     </para>
-
-     <para>
-      This caused the Datanode to crash, and it is however a functionality
-      only usable by Coordinators.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix snapshot management on slave nodes and on Datanodes accessed directly by
-      applications (Michael Paquier)
-     </para>
-
-     <para>
-      A slave node session acquires its snapshot directly from WAL like <productname>
-      PostgreSQL</> does. Also, a Datanode is now able to get a global snapshot directly
-      from GTM, avoiding WARNING messages that a snapshot is not available.
-     </para>
-
-     <para>
-      Queries interacting with remote nodes running on slave nodes are blocked.
-      Such queries need a global snapshot and a new transaction ID, but sessions
-      on slave nodes cannot acquire that.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Correct query generation of <literal>COPY</> with quoted table names (Nikhil Sontakke)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix race condition in GXID generation for autovacuum wraparound (Michael Paquier)
-     </para>
-
-     <para>
-      When an autovacuum wraparound begins, a global snapshot with a
-      global GXID is obtained from GTM. After getting this snapshot,
-      the code checks for wraparound conditions. Before this check, the
-      lock on GXID generation is released and then taken back. Just after
-      taking back the lock the GXID is updated to the latest value in cache.
-      However, during this time it is possible that ShmemVariableCache->nextXid
-      is updated by another local session that obtained a transaction ID
-      from GTM. GXID generation concurrency is managed globally at GTM, so we
-      cannot rely here on the local ShmemVariableCache->nextXid to update the
-      GXID of autovacuum. Updating it to a wrong value makes is async with GTM
-      information and such autovacuum is not able to gather a global snapshot
-      correctly, making the autovacuum session inconsistent with the other global
-      sessions. This could fatally crash a node under certain conditions like
-      GXID being updated concurrently by multiple sessions at the same time
-      during the wraparound condition checks.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix for <literal>DDL ALTER ROLE ... REPLICATION</> not recognized (Nikhil Sontakke)
-     </para>
-
-     <para>
-      <productname>PostgreSQL</> 9.1 code uses the word <literal>REPLICATION</> in
-      <literal>ALTER TABLE</> as a portion of <literal>IDENT</>. However it is a
-      reserved keyword in Postgres-XC due to its use in clause <literal>DISTRIBUTE BY</>,
-      extension of <literal>CREATE TABLE</> and <literal>ALTER TABLE</>.
-      So here what is done is completing deparsing of <literal>ALTER ROLE</> to use
-      <literal>REPLICATION</> as a normal reserved keyword.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix GTM startup with "*" set as <varname>listen_addresses</> on OSX (Michael Paquier)
-     </para>
-
-     <para>
-      On OSX, GTM was not able to start with default parameter values.
-      This had side effects on regressions with make check, making impossible
-      to run a simple default regression test.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="release-xc-1-0">
-  <title>Release 1.0</title>
-
-  <note>
-   <title>Release Date</title>
-   <simpara>2012-06-07</simpara>
-  </note>
-
-  <sect2>
-   <title>Overview</title>
-
-   <para>
-    <productname>Postgres-XC</> 1.0 is a symetric (multi-master, read and write-scalable)
-    shared-nothing cluster based on PostgreSQL. This release version is based on
-    PostgreSQL 9.1. 
-   </para>
-
-   <para>
-    Currently the only architectures supported are 64 bit Linux operating systems.
-   </para>
-
-   <para>
-    This release of <productname>Postgres-XC</> is the first major release and
-    contains the following features, characteristics and enhancements:
-   </para>
-
-   <itemizedlist>
-    <!-- This list is a summary of each item detailed below, without authors -->
-    <listitem>
-     <para>
-      Support and extensions for existing features of PostgreSQL in a cluster-wide environment.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      SQL extensions and functionalities exclusive to <productname>Postgres-XC</> for management
-      and operations related to a cluster, which add a node-level granularity for
-      cluster operations.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Creation of Global Transaction Manager (GTM), which is a centralized component
-      providing cluster-wide Multi-version Concurrency Control (MVCC).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Creation of mechanisms exclusive to <productname>Postgres-XC</> and enhancements of existing
-      internal mechanisms of <productname>PostgreSQL</>, which are related to connection pooling,
-      global transaction management, query planning, rewriting, analyzing and execution.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Restrictions related to existing features in <productname>PostgreSQL</> and currently not supported by
-      <productname>Postgres-XC</>.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   <para>
-    The above items are explained in more detail in the sections below.
-   </para>
-
-  <para>
-   The original overall architecture and design of <productname>Postgres-XC</> is by Koichi Suzuki, Mason Sharp, 
-   Pavan Deolasee, Andrei Martsinchyk and Michael Paquier. Koichi Suzuki is the original project lead.
-  </para>
-
-  </sect2>
-
-  <sect2>
-
-  <title>Details</title>
-
-   <para>
-    This section is divided into the following parts:
-   </para>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Existing standard features supported and related extensions
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      SQL extensions exclusive to <productname>Postgres-XC</>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Internal mechanisms exclusive to <productname>Postgres-XC</>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Global transaction management features
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Restrictions
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   <sect3>
-    <title>Existing standard features supported and related extensions</title>
-
-     <para>
-      This is an exhaustive list of all the features included in <productname>PostgreSQL</>
-      and currently supported in <productname>Postgres-XC</>. Some features have needed extensions.
-      In this case, the contributors are specified. If not listed in the restrictions,
-      all the <productname>PostgreSQL</> standard functionalities are supported and are expected to work.
-     </para>
-     <!-- complete list of existing features of Postgres supported -->
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        List of all the CREATE/ALTER/DROP SQL commands supported. All the features listed
-        here work like native PostgreSQL. Extensions may have been added to make them usable
-        in a cluster environment.
-       </para>
-       <para>
-        <link linkend="SQL-CREATEUSER"><command>CREATE USER</></link>,
-        <link linkend="SQL-ALTERUSER"><command>ALTER USER</></link>,
-        <link linkend="SQL-DROPUSER"><command>DROP USER</></link>,
-        <link linkend="SQL-CREATEAGGREGATE"><command>CREATE AGGREGATE</></link>,
-        <link linkend="SQL-ALTERAGGREGATE"><command>ALTER AGGREGATE</></link>,
-        <link linkend="SQL-DROPAGGREGATE"><command>DROP AGGREGATE</></link>,
-        <link linkend="SQL-CREATECOLLATION"><command>CREATE COLLATION</></link>,
-        <link linkend="SQL-ALTERCOLLATION"><command>ALTER COLLATION</></link>,
-        <link linkend="SQL-DROPCOLLATION"><command>DROP COLLATION</></link>,
-        <link linkend="SQL-CREATECONVERSION"><command>CREATE CONVERSION</></link>,
-        <link linkend="SQL-ALTERCONVERSION"><command>ALTER CONVERSION</></link>,
-        <link linkend="SQL-DROPCONVERSION"><command>DROP CONVERSION</></link>,
-        <link linkend="SQL-CREATEDATABASE"><command>CREATE DATABASE</></link>,
-        <link linkend="SQL-ALTERDATABASE"><command>ALTER DATABASE</></link>,
-        <link linkend="SQL-DROPDATABASE"><command>DROP DATABASE</></link>,
-        <link linkend="SQL-ALTERDEFAULTPRIVILEGES"><command>ALTER DEFAULT PRIVILEGES</></link>,
-        <link linkend="SQL-CREATEDOMAIN"><command>CREATE DOMAIN</></link>,
-        <link linkend="SQL-ALTERDOMAIN"><command>ALTER DOMAIN</></link>,
-        <link linkend="SQL-DROPDOMAIN"><command>DROP DOMAIN</></link>,
-        <link linkend="SQL-CREATEFUNCTION"><command>CREATE FUNCTION</></link>,
-        <link linkend="SQL-ALTERFUNCTION"><command>ALTER FUNCTION</></link>,
-        <link linkend="SQL-DROPFUNCTION"><command>DROP FUNCTION</></link>,
-        <link linkend="SQL-CREATEGROUP"><command>CREATE GROUP</></link>,
-        <link linkend="SQL-ALTERGROUP"><command>ALTER GROUP</></link>,
-        <link linkend="SQL-DROPGROUP"><command>DROP GROUP</></link>,
-        <link linkend="SQL-CREATEINDEX"><command>CREATE INDEX</></link>,
-        <link linkend="SQL-ALTERINDEX"><command>ALTER INDEX</></link>,
-        <link linkend="SQL-DROPINDEX"><command>DROP INDEX</></link>,
-        <link linkend="SQL-CREATELANGUAGE"><command>CREATE LANGUAGE</></link>,
-        <link linkend="SQL-ALTERLANGUAGE"><command>ALTER LANGUAGE</></link>,
-        <link linkend="SQL-DROPLANGUAGE"><command>DROP LANGUAGE</></link>,
-        <link linkend="SQL-CREATEOPCLASS"><command>CREATE OPERATOR CLASS</></link>,
-        <link linkend="SQL-ALTEROPCLASS"><command>ALTER OPERATOR CLASS</></link>,
-        <link linkend="SQL-DROPOPCLASS"><command>DROP OPERATOR CLASS</></link>,
-        <link linkend="SQL-CREATEOPFAMILY"><command>CREATE OPERATOR FAMILY</></link>,
-        <link linkend="SQL-ALTEROPFAMILY"><command>ALTER OPERATOR FAMILY</></link>,
-        <link linkend="SQL-DROPOPFAMILY"><command>DROP OPERATOR FAMILY</></link>,
-        <link linkend="SQL-CREATEROLE"><command>CREATE ROLE</></link>,
-        <link linkend="SQL-ALTERROLE"><command>ALTER ROLE</></link>,
-        <link linkend="SQL-DROPROLE"><command>DROP ROLE</></link>,
-        <link linkend="SQL-CREATESCHEMA"><command>CREATE SCHEMA</></link>,
-        <link linkend="SQL-ALTERSCHEMA"><command>ALTER SCHEMA</></link>,
-        <link linkend="SQL-DROPSCHEMA"><command>DROP SCHEMA</></link>,
-        <link linkend="SQL-CREATESEQUENCE"><command>CREATE SEQUENCE</></link>,
-        <link linkend="SQL-ALTERSEQUENCE"><command>ALTER SEQUENCE</></link>,
-        <link linkend="SQL-DROPSEQUENCE"><command>DROP SEQUENCE</></link>,
-        <link linkend="SQL-CREATETABLE"><command>CREATE TABLE</></link>,
-        <link linkend="SQL-ALTERTABLE"><command>ALTER TABLE</></link>,
-        <link linkend="SQL-DROPTABLE"><command>DROP TABLE</></link>,
-        <link linkend="SQL-CREATETABLESPACE"><command>CREATE TABLESPACE</></link>,
-        <link linkend="SQL-ALTERTABLESPACE"><command>ALTER TABLESPACE</></link>,
-        <link linkend="SQL-DROPTABLESPACE"><command>DROP TABLESPACE</></link>,
-        <link linkend="SQL-CREATETSCONFIG"><command>CREATE TEXT SEARCH CONFIGURATION</></link>,
-        <link linkend="SQL-ALTERTSCONFIG"><command>ALTER TEXT SEARCH CONFIGURATION</></link>,
-        <link linkend="SQL-DROPTSCONFIG"><command>DROP TEXT SEARCH CONFIGURATION</></link>,
-        <link linkend="SQL-CREATETSDICTIONARY"><command>CREATE TEXT SEARCH DICTIONARY</></link>,
-        <link linkend="SQL-ALTERTSDICTIONARY"><command>ALTER TEXT SEARCH DICTIONARY</></link>,
-        <link linkend="SQL-DROPTSDICTIONARY"><command>DROP TEXT SEARCH DICTIONARY</></link>,
-        <link linkend="SQL-CREATETSPARSER"><command>CREATE TEXT SEARCH PARSER</></link>,
-        <link linkend="SQL-ALTERTSPARSER"><command>ALTER TEXT SEARCH PARSER</></link>,
-        <link linkend="SQL-DROPTSPARSER"><command>DROP TEXT SEARCH PARSER</></link>,
-        <link linkend="SQL-CREATETSTEMPLATE"><command>CREATE TEXT SEARCH TEMPLATE</></link>,
-        <link linkend="SQL-ALTERTSTEMPLATE"><command>ALTER TEXT SEARCH TEMPLATE</></link>,
-        <link linkend="SQL-DROPTSTEMPLATE"><command>DROP TEXT SEARCH TEMPLATE</></link>,
-        <link linkend="SQL-CREATETYPE"><command>CREATE TYPE</></link>,
-        <link linkend="SQL-ALTERTYPE"><command>ALTER TYPE</></link>,
-        <link linkend="SQL-DROPTYPE"><command>DROP TYPE</></link>, 
-        <link linkend="SQL-CREATEUSER"><command>CREATE USER</></link>,
-        <link linkend="SQL-ALTERUSER"><command>ALTER USER</></link>,
-        <link linkend="SQL-DROPUSER"><command>DROP USER</></link>, 
-        <link linkend="SQL-CREATEVIEW"><command>CREATE VIEW</></link>,
-        <link linkend="SQL-ALTERVIEW"><command>ALTER VIEW</></link>,
-        <link linkend="SQL-DROPVIEW"><command>DROP VIEW</></link>,
-        <link linkend="SQL-CREATECAST"><command>CREATE CAST</></link>,
-        <link linkend="SQL-DROPCAST"><command>DROP CAST</></link>,
-        <link linkend="SQL-CREATERULE"><command>CREATE RULE</></link>,
-        <link linkend="SQL-DROPRULE"><command>DROP RULE</></link>,
-        <link linkend="SQL-CREATETABLEAS"><command>CREATE TABLE AS</></link>,
-       </para>
-      </listitem>
-      <listitem>
-       <para>List of other supported SQL</para>
-       <para>
-        <link linkend="SQL-ANALYZE"><command>ANALYZE</></link>,
-        <link linkend="SQL-BEGIN"><command>BEGIN</></link>,
-        <link linkend="SQL-CHECKPOINT"><command>CHECKPOINT</></link>, 
-        <link linkend="SQL-CLOSE"><command>CLOSE</></link>,
-        <link linkend="SQL-CLUSTER"><command>CLUSTER</></link>,
-        <link linkend="SQL-COMMENT"><command>COMMENT</></link>,
-        <link linkend="SQL-COMMIT"><command>COMMIT</></link>,
-        <link linkend="SQL-COMMIT-PREPARED"><command>COMMIT PREPARED</></link>,
-        <link linkend="SQL-COPY"><command>COPY</></link>,
-        <link linkend="SQL-DEALLOCATE"><command>DEALLOCATE</></link>,
-        <link linkend="SQL-DECLARE"><command>DECLARE</></link>,
-        <link linkend="SQL-DELETE"><command>DELETE</></link>,
-        <link linkend="SQL-DISCARD"><command>DISCARD</></link>,
-        <link linkend="SQL-DO"><command>DO</></link>,
-        <link linkend="SQL-END"><command>END</></link>,
-        <link linkend="SQL-EXECUTE"><command>EXECUTE</></link>,
-        <link linkend="SQL-EXPLAIN"><command>EXPLAIN</></link>,
-        <link linkend="SQL-FETCH"><command>FETCH</></link>,
-        <link linkend="SQL-GRANT"><command>GRANT</></link>,
-        <link linkend="SQL-INSERT"><command>INSERT</></link>,
-        <link linkend="SQL-LOAD"><command>LOAD</></link>,
-        <link linkend="SQL-LOCK"><command>LOCK</></link>,
-        <link linkend="SQL-MOVE"><command>MOVE</></link>,
-        <link linkend="SQL-PREPARE"><command>PREPARE</></link>,
-        <link linkend="SQL-PREPARE-TRANSACTION"><command>PREPARE TRANSACTION</></link>,
-        <link linkend="SQL-REASSIGN-OWNED"><command>REASSIGN OWNED</></link>,
-        <link linkend="SQL-REINDEX"><command>REINDEX</></link>,
-        <link linkend="SQL-RESET"><command>RESET</></link>,
-        <link linkend="SQL-REVOKE"><command>REVOKE</></link>,
-        <link linkend="SQL-ROLLBACK"><command>ROLLBACK</></link>,
-        <link linkend="SQL-ROLLBACK-PREPARED"><command>ROLLBACK PREPARED</></link>,
-        <link linkend="SQL-SELECT"><command>SELECT</></link>,
-        <link linkend="SQL-SELECTINTO"><command>SELECT INTO</></link>,
-        <link linkend="SQL-SET"><command>SET</></link>,
-        <link linkend="SQL-SET-CONSTRAINTS"><command>SET CONSTRAINTS</></link>,
-        <link linkend="SQL-SET-ROLE"><command>SET ROLE</></link>,
-        <link linkend="SQL-SET-SESSION-AUTHORIZATION"><command>SET SESSION AUTHORIZATION</></link>,
-        <link linkend="SQL-SHOW"><command>SHOW</></link>,
-        <link linkend="SQL-START-TRANSACTION"><command>START TRANSACTION</></link>,
-        <link linkend="SQL-TRUNCATE"><command>TRUNCATE</></link>,
-        <link linkend="SQL-UPDATE"><command>UPDATE</></link>,
-        <link linkend="SQL-VACUUM"><command>VACUUM</></link>,
-        <link linkend="SQL-VALUES"><command>VALUES</></link>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        HOT-Standby and streaming replication, working as in native <productname>PostgreSQL</>, 
-        at the Coordinator and Datanode level.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <application>pg_dump</> (Michael Paquier): extension to manage table distribution type
-        in a dump.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <application>initdb</> (Michael Paquier): addition of a new mandatory option <option>
-        --nodename=<replaceable class="parameter">nodename</replaceable></option> to specify
-        a node name when initializing it. This adds a parameter (pgxc_node_name) to the 
-        node's postgresql.conf file that the node uses to identify itself.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>ORDER BY</command>, <command>LIMIT</command>, <command>OFFSET</command> clauses:
-        those clauses can be evaluated directly on Datanodes or on Coordinators depending on how
-        query is shippable or not to remote nodes (Andrei Martsinchyk).
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Table distribution definition (Mason Sharp, Abbas Butt, Michael Paquier): <link linkend="SQL-CREATETABLE">
-        <command>CREATE TABLE</></link> has been extended with <command>DISTRIBUTE BY</command>
-        to be able to specify the table distribution at table creation. Distribution is tuple-based.
-        Four types are supported: replication, hash-distribution, modulo-distribution and round
-        robin.
-       </para>
-       <para>
-        The node list where table data is stored can also be defined with the extension <command>TO NODE</command>
-        or <command>TO GROUP</command>.
-       </para>
-       <para>
-        All the distribution data is stored in catalog <link linkend="catalog-pgxc-node"><structname>pgxc_node
-        </structname></link>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>JOIN</command> clauses (Mason Sharp, Andrei Martsinchyk): extension to generate a remote join plan
-        depending on the quals used in queries and table distribution types. This remote join plan
-        can be reduced depending on distribution types or nodes where table data is located.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>GROUP BY</command> clause (Ashutosh Bapat): some optimizations have been added in planner to evaluate if a clause
-        can be shipped to remote nodes or not.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Window functions (Ashutosh Bapat): such functions are not shipped to remote nodes and are exclusively
-        evaluated on Coordinator
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>INSERT</command> with multiple values (Wang Diancheng, Pavan Deolasee): this feature
-        has been extended to manage the case of distributed tables by hash, modulo or round robin.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Aggregate functions (Andrei Martsinchyk, Ashutosh Bapat): a collection function is determined on Coordinator to collect
-        correctly the results from Datanodes.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>SELECT FOR UPDATE</command> (Abbas Butt). The implementation is not the most performant
-        as in the case of a join on native <productname>PostgreSQL</>, where locks are taken on the tuples where join
-        condition is achieved, but instead locks are taken on all the tuples used to evaluate the join condition.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>SERIAL</command> types (Michael Paquier): they behave like native <productname>PostgreSQL</>, but an extension has been
-        added to create the table having <command>SERIAL</command> columns in cluster correctly.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>TABLESPACE</command> (Michael Paquier): an extension has been made to allow nodes to share
-        the same tablespace repository even if those nodes are on the same server. It is
-        possible to use <link linkend="SQL-EXECUTEDIRECT"><command>EXECUTE DIRECT</></link>
-        with <link linkend="SQL-CREATETABLESPACE"><command>CREATE TABLESPACE</></link>
-        and <link linkend="SQL-DROPTABLESPACE"><command>DROP TABLESPACE</></link> to
-        choose the tablespace folder for each node.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>INSERT SELECT</command> (Pavan Deolasee): extensions have 
-        been done to manage that for all the table distribution types.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>PREPARE</command> and <command>EXECUTE</command> (Andrei Martsinchyk, Ashutosh Bapat):
-        extensions have been done to send parse and bind parameters to remote Datanodes. Those functions
-        behave like in vanilla.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>EXPLAIN</command> (Andrei Martsinchyk, Ashutosh Bapat, Michael Paquier): Addition of options to 
-        print the nodes involved in query, as well as extensions to print remote queries for remote node plans.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>COPY</command> (Andrei Martsinchyk, Amit Khandekar): some extension has been
-        added to copy data to remote nodes depending on table distribution. Support for
-        <command>BINARY</command> and <command>DEFAULT</command> columns using non-shippable
-        expressions as default expressions are also supported.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>CREATE TABLE AS</command> and <command>SELECT INTO</command> (Pavan Deolasee):
-        Support is extended with remote node planning and table distributions. Table distribution
-        can be specified for <command>CREATE TABLE AS</command>. <command>SELECT INTO</command>
-        uses the default distribution type, i.e distribution by hash on the first
-        column found as hashable or round robin if nothing can be used as a distribution key.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Session parameters (Michael Paquier): session and local parameters are all supported.
-        Those parameters are managed with connection pooling. Connections with user-customized session
-        parameters are locked in session and not pulled back to pool. When a session finishes, session
-        parameter reset is made on each connection that was used by session and then pulled back to
-        connection pool.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Sequence consistency in transaction blocks (Michael Paquier): As sequence values
-        are evaluated in Global Transaction Manager, a callback mechanism for the following
-        cases has been created.
-       </para>
-       <para>
-        <itemizedlist>
-         <listitem>
-          <para>
-            Drop a sequence on GTM when the transaction that created this sequence aborts.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-            Drop a sequence on GTM when the transaction that dropped this sequence commits.
-          </para>
-         </listitem>
-         <listitem>
-          <para>
-            Fallback to its former name a sequence whose name has been modified in a transaction
-            that aborts.
-          </para>
-         </listitem>
-        </itemizedlist>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        System functions (Amit Khandekar and Koichi Suzuki): most of them are working like native but some extensions have been
-        added for relation-size functions (<function>pg_relation_size()</>, <function>pg_tablespace_size()
-        </>, <function>pg_database_size()</>) and locking functions.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        New configuration parameters in <filename>postgresql.conf</>
-       </para>
-       <para>
-        <itemizedlist>
-         <listitem>
-          <para><varname>pooler_port</></para>
-          <para>Port opened by pooler to which backends can connect to communicate with</para>
-         </listitem>
-         <listitem>
-          <para><varname>min_pool_size</></para>
-          <para>Minimum number of connections in pool</para>
-         </listitem>
-         <listitem>
-          <para><varname>max_pool_size</></para>
-          <para>Maximum number of connections in pool</para>
-         </listitem>
-         <listitem>
-          <para><varname>persistent_Datanode_connections</></para>
-          <para>On/off switch to make sessions keep the same connections when used.
-          This may be useful in lower concurrency environments with many session
-          parameters set.
-          </para>
-         </listitem>
-         <listitem>
-          <para><varname>max_coordinators</></para>
-          <para>Maximum number of Coordinators that can be defined in local node</para>
-         </listitem>
-         <listitem>
-          <para><varname>max_datanodes</></para>
-          <para>Maximum number of Datanodes that can be defined in local node</para>
-         </listitem>
-         <listitem>
-          <para><varname>gtm_host</></para>
-          <para>Host to connect to GTM</para>
-         </listitem>
-         <listitem>
-          <para><varname>gtm_port</></para>
-          <para>Port to connect to GTM</para>
-         </listitem>
-         <listitem>
-          <para><varname>pgxc_node_name</></para>
-          <para>Name of the local node. This is currently set by initdb.</para>
-         </listitem>
-         <listitem>
-          <para><varname>strict_statement_checking</></para>
-          <para>Forbid unsafe SQL</para>
-         </listitem>
-         <listitem>
-          <para><varname>enforce_two_phase_commit</></para>
-          <para>Control parameter used for temporary objects to enforce the use of autocommit on transactions
-                that used temporary objects if disabled.</para>
-         </listitem>
-        </itemizedlist>
-       </para>
-      </listitem>
-     </itemizedlist>
-   </sect3>
-
-   <sect3>
-    <title>SQL extensions exclusive to <productname>Postgres-XC</></title>
-
-    <para>
-     This section lists all the new SQL functionalities and system functions that are exclusive to <productname>Postgres-XC</>
-     and can be used to manage a cluster environment.
-    </para>
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       <link linkend="SQL-CREATENODE"><command>CREATE NODE</></link>,
-       <link linkend="SQL-ALTERNODE"><command>ALTER NODE</></link>,
-       <link linkend="SQL-DROPNODE"><command>DROP NODE</></link> (Michael Paquier, Abbas Butt)
-      </para>
-      <para>
-       These SQL commands are used to manage cluster node information in catalog
-       <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.
-      </para>
-      <para>
-       These commands run only on the local node where they are run, and running them on Datanodes
-       make no sense as this catalog data is used only by Coordinator to identify remote nodes
-       and by connection pooling to get necessary remote connection information.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="SQL-CREATENODEGROUP"><command>CREATE NODE GROUP</></link>,
-       <link linkend="SQL-DROPNODEGROUP"><command>DROP NODE GROUP</></link> (Michael Paquier, Abbas Butt)
-      </para>
-      <para>
-       <command>CREATE NODE GROUP</> and <command>DROP NODE GROUP</> manage the node groups that
-       can be used when creating a table with the extension <command>TO GROUP</> of <command>CREATE TABLE</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="SQL-CREATEBARRIER"><command>CREATE BARRIER</></link> (Pavan Deolasee)
-      </para>
-      <para>
-       When specified with an ID, this command allows to register in all of the nodes of the cluster
-       a common and consistent time point to be able to recover all the nodes consistently back to
-       this point. Internally, a barrier is written in the WAL file of all of the nodes.
-      </para>
-      <para>
-       <varname>recovery_target_barrier</varname> in <filename>recovery.conf</> can be used to recover
-        a node to a given barrier ID.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="SQL-CLEANCONNECTION"><command>CLEAN CONNECTION</></link> (Michael Paquier)
-      </para>
-      <para>
-       <command>CLEAN CONNECTION</command> is a connection pooling utility able to drop connections on chosen node(s)
-       for a given database or/and user.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>pgxc_pool_check()</>, <function>pgxc_pool_reload()</> (Michael Paquier, Abbas Butt)
-      </para>
-      <para>
-       Those system functions can be used to check or update the data cached in pooler with
-       <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>. <function>pgxc_pool_check()</>
-       checks if the connection information is consistent between pooler cache and catalogs.
-       <function>pgxc_pool_reload()</> updates the connection information cached in pool.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="SQL-EXECUTEDIRECT"><command>EXECUTE DIRECT</></link> (Andrei Martsinchyk, Michael Paquier)
-      </para>
-      <para>
-       <command>EXECUTE DIRECT</> can be used to launch a query directly to a given node. Only a single node
-       can be targetted at the same time.
-      </para>
-      <para>
-       <command>INSERT</command>, <command>UPDATE</command> and <command>DELETE</command> are not authorized.
-      </para>
-      <para>
-       Utilities are basically forbidden but some are authorized for cluster management purposes.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Internal mechanisms exclusive to <productname>Postgres-XC</></title>
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Connection pooling (Andrei Martsinchyk, Michael Paquier)
-      </para>
-
-      <para>
-       Connection pooling is added on Coordinator to dynamically manage
-       and with a minimum cost connections to remote nodes. This pooler
-       uses data of catalog <link linkend="catalog-pgxc-node"><structname>pgxc_node
-        </structname></link>. It is a separate process that is forked off of the postmaster.
-      </para>
-
-      <para>
-       Connection pools are divided per both user and database for security reasons.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Fast-query shipping (Mason Sharp, Ashutosh Bapat, Andrei Martsinchyk)
-      </para>
-
-      <para>
-       Fast-query shipping (FQS) is an additional planner exclusive to <productname>
-       Postgres-XC</> designed to determine as fast as possible if a query can be
-       completely shipped to Datanodes depending on its parsed content. A fallback
-       to standard planner is made if query cannot be shipped as-is.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remote query planning, standard and remote join (Mason Sharp, Andrei Martsinchyk, Pavan Deolasee, Ashutosh Bapat)
-      </para>
-
-      <para>
-       This additional planner can build a plan to replace the <productname>PostgreSQL</>
-       scan plan by a RemoteQuery plan able to scan remote nodes in executor. This includes
-       plans to be able to build remote joins, reducible join functionalities are also included.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remote INSERT, UPDATE, DELETE planning (Pavan Deolasee, Michael Paquier)
-      </para>
-      <para>
-       This additional planner can be used by <productname>PostgreSQL</> standard planner
-       to generate plans for DML queries to remote nodes. Those plans are placed on top
-       of an inner scan plan.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Remode node location identification and data (Michael Paquier, Abbas Butt)
-      </para>
-      <para>
-       Nodes use their names as unique identifiers in the cluster and use the information
-       stored in <link linkend="catalog-pgxc-node"><structname>pgxc_node
-       </structname></link> to define the location of remote node to be used. Cluster nodes
-       can also be defined as groups stored in <link linkend="catalog-pgxc-group"><structname>pgxc_group
-       </structname></link>.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Global Transaction Manager (Pavan Deolasee, with input from Koichi Suzuki and Mason Sharp)</title>
-
-    <para>
-     Global Transaction manager (GTM) is a module exclusive to <productname>Postgres-XC</>
-     able to maintain the same level of MVCC as vanilla <productname>PostgreSQL</> by
-     distributing global transaction ID and global snapshot. GTM is also used to store global
-     information about two-phase commit transactions when external application requested
-     it. Sequence information (name, values) is managed directly in GTM.
-    </para>
-
-    <para>
-     This section lists all the modules and extensions related to GTM.
-    </para>
-
-    <para>
-     <link linkend="APP-GTM-PROXY">GTM-Proxy</link> can be used between <command>Postgres-XC</>
-     nodes and GTM to control the number of messages by grouping them.
-    </para>
-
-    <para>
-     <link linkend="APP-GTM">GTM-Standby</link> is a solution that prevents GTM single point
-     of failure. (Koichi Suzuki) 
-    </para>
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       <link linkend="APP-INITGTM"><command>initgtm</command></link> (Michael Paquier)
-      </para>
-      <para>
-       Module that can initialize GTM data folder. Can be used to initialize GTM or GTM-Proxy.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <filename>gtm.conf</> (Koichi Suzuki)
-      </para>
-      <para>
-       Configuration file of GTM. More details about configuration parameters <link linkend="APP-GTM">here</link>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <filename>gtm_proxy.conf</> (Koichi Suzuki)
-      </para>
-      <para>
-       Configuration file of GTM Proxy. More details about configuration parameters <link linkend="APP-GTM-PROXY">here</link>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="APP-GTM-CTL"><command>gtm_ctl</></link>
-      </para>
-      <para>
-       Module similar to <command>pg_ctl</> able to control GTM, GTM-Standby and GTM-Proxy in similar ways.
-       <command>pg_ctl</> can be used to reconnect GTM-Proxy to a new GTM and to failover a GTM-Standy to become
-       a primary GTM.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Restrictions</title>
-
-     <itemizedlist>
-      <listitem>
-       <para>List of all the unsupported SQL commands</para>
-       <para>
-        <link linkend="SQL-CREATEEXTENSION"><command>CREATE EXTENSION</></link>,
-        <link linkend="SQL-ALTEREXTENSION"><command>ALTER EXTENSION</></link>,
-        <link linkend="SQL-DROPEXTENSION"><command>DROP EXTENSION</></link>,
-        <link linkend="SQL-CREATEFOREIGNDATAWRAPPER"><command>CREATE FOREIGN DATA WRAPPER</></link>,
-        <link linkend="SQL-ALTERFOREIGNDATAWRAPPER"><command>ALTER FOREIGN DATA WRAPPER</></link>,
-        <link linkend="SQL-DROPFOREIGNDATAWRAPPER"><command>DROP FOREIGN DATA WRAPPER</></link>,
-        <link linkend="SQL-CREATEFOREIGNTABLE"><command>CREATE FOREIGN TABLE</></link>,
-        <link linkend="SQL-ALTERFOREIGNTABLE"><command>ALTER FOREIGN TABLE</></link>,
-        <link linkend="SQL-DROPFOREIGNTABLE"><command>DROP FOREIGN TABLE</></link>,
-        <link linkend="SQL-ALTERLARGEOBJECT"><command>ALTER LARGE OBJECT</></link>,
-        <link linkend="SQL-CREATESERVER"><command>CREATE SERVER</></link>,
-        <link linkend="SQL-ALTERSERVER"><command>ALTER SERVER</></link>,
-        <link linkend="SQL-DROPSERVER"><command>DROP SERVER</></link>,
-        <link linkend="SQL-CREATETRIGGER"><command>CREATE TRIGGER</></link>,
-        <link linkend="SQL-ALTERTRIGGER"><command>ALTER TRIGGER</></link>,
-        <link linkend="SQL-DROPTRIGGER"><command>DROP TRIGGER</></link>,
-        <link linkend="SQL-CREATEUSERMAPPING"><command>CREATE USER MAPPING</></link>,
-        <link linkend="SQL-ALTERUSERMAPPING"><command>ALTER USER MAPPING</></link>,
-        <link linkend="SQL-DROPUSERMAPPING"><command>DROP USER MAPPING</></link>,
-        <link linkend="SQL-LISTEN"><command>LISTEN</></link>,
-        <link linkend="SQL-NOTIFY"><command>NOTIFY</></link>,
-        <link linkend="SQL-RELEASE-SAVEPOINT"><command>RELEASE SAVEPOINT</></link>,
-        <link linkend="SQL-ROLLBACK-TO"><command>ROLLBACK TO SAVEPOINT</></link>,
-        <link linkend="SQL-SAVEPOINT"><command>SAVEPOINT</></link>,
-        <link linkend="SQL-SECURITY-LABEL"><command>SECURITY LABEL</></link>,
-        <link linkend="SQL-UNLISTEN"><command>UNLISTEN</></link>,
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Table distribution definition cannot be changed.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Distribution key of a table cannot be updated.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Utilities cannot be used in SQL functions.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        DML cannot be used in plpgsql functions.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>CREATE TABLE AS EXECUTE</command> is not supported.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>WHERE CURRENT OF</command> is not supported.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>RETURNING</command> is not supported.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        In cursors, <command>MOVE BACKWARD</command> works only if <command>SCROLL</command>
-        is used in <command>CURSOR</command>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>WITH HOLD</command> cursors are not supported.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Statictics are not managed globally. When requesting statistics
-        only the data related to node directly connected to is taken into account.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Barriers have no timeout functionalities, meaning that if a 2PC transaction is
-        stuck forever, barrier will be stuck too.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-   </sect3>
-   </sect2>
-
-   <sect2>
-
-    <title>Acknowledgement</title>
-
-    <itemizedlist>
-     <listitem>
-      <para>NTT Open Source Software Center</para>
-     </listitem>
-     <listitem>
-      <para>EnterpriseDB</para>
-     </listitem>
-    </itemizedlist>
-
-   </sect2>
- </sect1>
diff --git a/doc-xc/src/sgml/release-xl-9.2.sgmlin b/doc-xc/src/sgml/release-xl-9.2.sgmlin
deleted file mode 100644
index 959b01da94..0000000000
--- a/doc-xc/src/sgml/release-xl-9.2.sgmlin
+++ /dev/null
@@ -1,527 +0,0 @@
-<!-- doc/src/sgml/release-xl-9.2.sgml -->
-<!-- See header comment in release.sgml about typical markup -->
-
- <sect1 id="release-xl-9-2">
-  <title>Release 9.2rc</title>
-
-  <note>
-   <title>Release Date</title>
-   <simpara>2014-05-13</simpara>
-  </note>
-
-  <sect2>
-   <title>Overview</title>
-
-   <para>
-    <productname>Postgres-XL</> 9.2 is a symetric multi-headed, read and write-scalable
-    shared-nothing massively parallel processing cluster based on PostgreSQL. This release version is based on
-    PostgreSQL 9.2.4.
-   </para>
-
-   <para>
-    Currently the only architectures supported are 64 bit Linux operating systems.
-   </para>
-
-   <para>
-    This release of <productname>Postgres-XL</> is the first major release and
-    contains the following features, characteristics and enhancements:
-   </para>
-
-   <itemizedlist>
-    <!-- This list is a summary of each item detailed below, without authors -->
-    <listitem>
-     <para>
-      Support and extensions for existing features of PostgreSQL in a cluster-wide environment.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      SQL extensions and functionalities for management
-      and operations related to a cluster, which add a node-level granularity for
-      cluster operations.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Creation of Global Transaction Manager (GTM), which is a centralized component
-      providing cluster-wide Multi-version Concurrency Control (MVCC).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Creation of mechanisms for <productname>Postgres-XL</> and enhancements of existing
-      internal mechanisms of <productname>PostgreSQL</>, which are related to connection pooling,
-      global transaction management, query planning, rewriting, analyzing and execution.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Restrictions related to existing features in <productname>PostgreSQL</> and currently not supported by
-      <productname>Postgres-XL</>.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   <para>
-    The above items are explained in more detail in the sections below.
-   </para>
-
-
-  <para>
-   Postgres-XL builds off another project called Postgres-XC.
-   The original overall architecture and design of <productname>Postgres-XC</> is by Koichi Suzuki, Mason Sharp, 
-   Pavan Deolasee, Andrei Martsinchyk and Michael Paquier. Koichi Suzuki is the original project lead. More recent long time contributors include Ashutosh Bapat, Abbas Butt, and Amit Khandekar.
-  </para>
-  <para>
-   Postgres-XL modifies the architecture to more tightly bond the components together and add massively parallel processing with direct Datanode to Datanode communication for fast performance. In addition, a plan is determined one time, serialized and sent down to the Datanodes instead of sending down SQL statements and reparsing.  Also, there have been some changes made to support multi-tenancy, locking down access to pg_catalog tables and providing better pooler management. The key architects and developers are Andrei Martsinchyk, Mason Sharp, Nikhil Sontakke, and Jim Mlodgenski, with Mason Sharp the project lead.
-  </para>
-
-  </sect2>
-
-  <sect2>
-
-  <title>Details</title>
-
-   <sect3>
-    <title>Existing standard features supported and related extensions</title>
-
-     <para>
-      This is an exhaustive list of all the features included in <productname>PostgreSQL</>
-      and currently supported in <productname>Postgres-XL</>. 
-     </para>
-     <!-- complete list of existing features of Postgres supported -->
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        A list of all the CREATE/ALTER/DROP SQL commands supported appears below. 
-        All of the features listed
-        here work like native PostgreSQL. Extensions may have been added to make them usable
-        in a cluster environment.
-       </para>
-       <para>
-        <link linkend="SQL-CREATEUSER"><command>CREATE USER</></link>,
-        <link linkend="SQL-ALTERUSER"><command>ALTER USER</></link>,
-        <link linkend="SQL-DROPUSER"><command>DROP USER</></link>,
-        <link linkend="SQL-CREATEAGGREGATE"><command>CREATE AGGREGATE</></link>,
-        <link linkend="SQL-ALTERAGGREGATE"><command>ALTER AGGREGATE</></link>,
-        <link linkend="SQL-DROPAGGREGATE"><command>DROP AGGREGATE</></link>,
-        <link linkend="SQL-CREATECOLLATION"><command>CREATE COLLATION</></link>,
-        <link linkend="SQL-ALTERCOLLATION"><command>ALTER COLLATION</></link>,
-        <link linkend="SQL-DROPCOLLATION"><command>DROP COLLATION</></link>,
-        <link linkend="SQL-CREATECONVERSION"><command>CREATE CONVERSION</></link>,
-        <link linkend="SQL-ALTERCONVERSION"><command>ALTER CONVERSION</></link>,
-        <link linkend="SQL-DROPCONVERSION"><command>DROP CONVERSION</></link>,
-        <link linkend="SQL-CREATEDATABASE"><command>CREATE DATABASE</></link>,
-        <link linkend="SQL-ALTERDATABASE"><command>ALTER DATABASE</></link>,
-        <link linkend="SQL-DROPDATABASE"><command>DROP DATABASE</></link>,
-        <link linkend="SQL-ALTERDEFAULTPRIVILEGES"><command>ALTER DEFAULT PRIVILEGES</></link>,
-        <link linkend="SQL-CREATEDOMAIN"><command>CREATE DOMAIN</></link>,
-        <link linkend="SQL-ALTERDOMAIN"><command>ALTER DOMAIN</></link>,
-        <link linkend="SQL-DROPDOMAIN"><command>DROP DOMAIN</></link>,
-        <link linkend="SQL-CREATEFUNCTION"><command>CREATE FUNCTION</></link>,
-        <link linkend="SQL-ALTERFUNCTION"><command>ALTER FUNCTION</></link>,
-        <link linkend="SQL-DROPFUNCTION"><command>DROP FUNCTION</></link>,
-        <link linkend="SQL-CREATEGROUP"><command>CREATE GROUP</></link>,
-        <link linkend="SQL-ALTERGROUP"><command>ALTER GROUP</></link>,
-        <link linkend="SQL-DROPGROUP"><command>DROP GROUP</></link>,
-        <link linkend="SQL-CREATEINDEX"><command>CREATE INDEX</></link>,
-        <link linkend="SQL-ALTERINDEX"><command>ALTER INDEX</></link>,
-        <link linkend="SQL-DROPINDEX"><command>DROP INDEX</></link>,
-        <link linkend="SQL-CREATELANGUAGE"><command>CREATE LANGUAGE</></link>,
-        <link linkend="SQL-ALTERLANGUAGE"><command>ALTER LANGUAGE</></link>,
-        <link linkend="SQL-DROPLANGUAGE"><command>DROP LANGUAGE</></link>,
-        <link linkend="SQL-CREATEOPCLASS"><command>CREATE OPERATOR CLASS</></link>,
-        <link linkend="SQL-ALTEROPCLASS"><command>ALTER OPERATOR CLASS</></link>,
-        <link linkend="SQL-DROPOPCLASS"><command>DROP OPERATOR CLASS</></link>,
-        <link linkend="SQL-CREATEOPFAMILY"><command>CREATE OPERATOR FAMILY</></link>,
-        <link linkend="SQL-ALTEROPFAMILY"><command>ALTER OPERATOR FAMILY</></link>,
-        <link linkend="SQL-DROPOPFAMILY"><command>DROP OPERATOR FAMILY</></link>,
-        <link linkend="SQL-CREATEROLE"><command>CREATE ROLE</></link>,
-        <link linkend="SQL-ALTERROLE"><command>ALTER ROLE</></link>,
-        <link linkend="SQL-DROPROLE"><command>DROP ROLE</></link>,
-        <link linkend="SQL-CREATESCHEMA"><command>CREATE SCHEMA</></link>,
-        <link linkend="SQL-ALTERSCHEMA"><command>ALTER SCHEMA</></link>,
-        <link linkend="SQL-DROPSCHEMA"><command>DROP SCHEMA</></link>,
-        <link linkend="SQL-CREATESEQUENCE"><command>CREATE SEQUENCE</></link>,
-        <link linkend="SQL-ALTERSEQUENCE"><command>ALTER SEQUENCE</></link>,
-        <link linkend="SQL-DROPSEQUENCE"><command>DROP SEQUENCE</></link>,
-        <link linkend="SQL-CREATETABLE"><command>CREATE TABLE</></link>,
-        <link linkend="SQL-ALTERTABLE"><command>ALTER TABLE</></link>,
-        <link linkend="SQL-DROPTABLE"><command>DROP TABLE</></link>,
-        <link linkend="SQL-CREATETABLESPACE"><command>CREATE TABLESPACE</></link>,
-        <link linkend="SQL-ALTERTABLESPACE"><command>ALTER TABLESPACE</></link>,
-        <link linkend="SQL-DROPTABLESPACE"><command>DROP TABLESPACE</></link>,
-        <link linkend="SQL-CREATETSCONFIG"><command>CREATE TEXT SEARCH CONFIGURATION</></link>,
-        <link linkend="SQL-ALTERTSCONFIG"><command>ALTER TEXT SEARCH CONFIGURATION</></link>,
-        <link linkend="SQL-DROPTSCONFIG"><command>DROP TEXT SEARCH CONFIGURATION</></link>,
-        <link linkend="SQL-CREATETSDICTIONARY"><command>CREATE TEXT SEARCH DICTIONARY</></link>,
-        <link linkend="SQL-ALTERTSDICTIONARY"><command>ALTER TEXT SEARCH DICTIONARY</></link>,
-        <link linkend="SQL-DROPTSDICTIONARY"><command>DROP TEXT SEARCH DICTIONARY</></link>,
-        <link linkend="SQL-CREATETSPARSER"><command>CREATE TEXT SEARCH PARSER</></link>,
-        <link linkend="SQL-ALTERTSPARSER"><command>ALTER TEXT SEARCH PARSER</></link>,
-        <link linkend="SQL-DROPTSPARSER"><command>DROP TEXT SEARCH PARSER</></link>,
-        <link linkend="SQL-CREATETSTEMPLATE"><command>CREATE TEXT SEARCH TEMPLATE</></link>,
-        <link linkend="SQL-ALTERTSTEMPLATE"><command>ALTER TEXT SEARCH TEMPLATE</></link>,
-        <link linkend="SQL-DROPTSTEMPLATE"><command>DROP TEXT SEARCH TEMPLATE</></link>,
-        <link linkend="SQL-CREATETYPE"><command>CREATE TYPE</></link>,
-        <link linkend="SQL-ALTERTYPE"><command>ALTER TYPE</></link>,
-        <link linkend="SQL-DROPTYPE"><command>DROP TYPE</></link>, 
-        <link linkend="SQL-CREATEUSER"><command>CREATE USER</></link>,
-        <link linkend="SQL-ALTERUSER"><command>ALTER USER</></link>,
-        <link linkend="SQL-DROPUSER"><command>DROP USER</></link>, 
-        <link linkend="SQL-CREATEVIEW"><command>CREATE VIEW</></link>,
-        <link linkend="SQL-ALTERVIEW"><command>ALTER VIEW</></link>,
-        <link linkend="SQL-DROPVIEW"><command>DROP VIEW</></link>,
-        <link linkend="SQL-CREATECAST"><command>CREATE CAST</></link>,
-        <link linkend="SQL-DROPCAST"><command>DROP CAST</></link>,
-        <link linkend="SQL-CREATERULE"><command>CREATE RULE</></link>,
-        <link linkend="SQL-DROPRULE"><command>DROP RULE</></link>,
-        <link linkend="SQL-CREATETABLEAS"><command>CREATE TABLE AS</></link>,
-       </para>
-      </listitem>
-      <listitem>
-       <para>List of other supported SQL</para>
-       <para>
-        <link linkend="SQL-ANALYZE"><command>ANALYZE</></link>,
-        <link linkend="SQL-BEGIN"><command>BEGIN</></link>,
-        <link linkend="SQL-CHECKPOINT"><command>CHECKPOINT</></link>, 
-        <link linkend="SQL-CLOSE"><command>CLOSE</></link>,
-        <link linkend="SQL-CLUSTER"><command>CLUSTER</></link>,
-        <link linkend="SQL-COMMENT"><command>COMMENT</></link>,
-        <link linkend="SQL-COMMIT"><command>COMMIT</></link>,
-        <link linkend="SQL-COMMIT-PREPARED"><command>COMMIT PREPARED</></link>,
-        <link linkend="SQL-COPY"><command>COPY</></link>,
-        <link linkend="SQL-DEALLOCATE"><command>DEALLOCATE</></link>,
-        <link linkend="SQL-DECLARE"><command>DECLARE</></link>,
-        <link linkend="SQL-DELETE"><command>DELETE</></link>,
-        <link linkend="SQL-DISCARD"><command>DISCARD</></link>,
-        <link linkend="SQL-DO"><command>DO</></link>,
-        <link linkend="SQL-END"><command>END</></link>,
-        <link linkend="SQL-EXECUTE"><command>EXECUTE</></link>,
-        <link linkend="SQL-EXPLAIN"><command>EXPLAIN</></link>,
-        <link linkend="SQL-FETCH"><command>FETCH</></link>,
-        <link linkend="SQL-GRANT"><command>GRANT</></link>,
-        <link linkend="SQL-INSERT"><command>INSERT</></link>,
-        <link linkend="SQL-LOAD"><command>LOAD</></link>,
-        <link linkend="SQL-LOCK"><command>LOCK</></link>,
-        <link linkend="SQL-MOVE"><command>MOVE</></link>,
-        <link linkend="SQL-PREPARE"><command>PREPARE</></link>,
-        <link linkend="SQL-PREPARE-TRANSACTION"><command>PREPARE TRANSACTION</></link>,
-        <link linkend="SQL-REASSIGN-OWNED"><command>REASSIGN OWNED</></link>,
-        <link linkend="SQL-REINDEX"><command>REINDEX</></link>,
-        <link linkend="SQL-RESET"><command>RESET</></link>,
-        <link linkend="SQL-REVOKE"><command>REVOKE</></link>,
-        <link linkend="SQL-ROLLBACK"><command>ROLLBACK</></link>,
-        <link linkend="SQL-ROLLBACK-PREPARED"><command>ROLLBACK PREPARED</></link>,
-        <link linkend="SQL-SELECT"><command>SELECT</></link>,
-        <link linkend="SQL-SELECTINTO"><command>SELECT INTO</></link>,
-        <link linkend="SQL-SET"><command>SET</></link>,
-        <link linkend="SQL-SET-CONSTRAINTS"><command>SET CONSTRAINTS</></link>,
-        <link linkend="SQL-SET-ROLE"><command>SET ROLE</></link>,
-        <link linkend="SQL-SET-SESSION-AUTHORIZATION"><command>SET SESSION AUTHORIZATION</></link>,
-        <link linkend="SQL-SHOW"><command>SHOW</></link>,
-        <link linkend="SQL-START-TRANSACTION"><command>START TRANSACTION</></link>,
-        <link linkend="SQL-TRUNCATE"><command>TRUNCATE</></link>,
-        <link linkend="SQL-UPDATE"><command>UPDATE</></link>,
-        <link linkend="SQL-VACUUM"><command>VACUUM</></link>,
-        <link linkend="SQL-VALUES"><command>VALUES</></link>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        HOT-Standby and streaming replication work as in native <productname>PostgreSQL</>, 
-        at the Coordinator and Datanode level.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        New configuration parameters in <filename>postgresql.conf</>
-       </para>
-       <para>
-        <itemizedlist>
-         <listitem>
-          <para><varname>pooler_port</></para>
-          <para>Port opened by pooler to which backends can connect to communicate with</para>
-         </listitem>
-         <listitem>
-          <para><varname>min_pool_size</></para>
-          <para>Minimum number of connections in pool</para>
-         </listitem>
-         <listitem>
-          <para><varname>max_pool_size</></para>
-          <para>Maximum number of connections in pool</para>
-         </listitem>
-         <listitem>
-          <para><varname>pool_maintenance_timeout</></para>
-          <para>When to clean up idle connections</para>
-         </listitem>
-         <listitem>
-          <para><varname>remote_query_cost</></para>
-          <para>Cost overhead for setting up a remote query</para>
-         </listitem>
-         <listitem>
-          <para><varname>network_byte_cost</></para>
-          <para>Data shipping cost for query planning</para>
-         </listitem>
-         <listitem>
-          <para><varname>sequence_range</></para>
-          <para>For frequent requests of sequences, get up to this range</para>
-         </listitem>
-         <listitem>
-          <para><varname>max_pool_size</></para>
-          <para>Maximum number of connections in pool</para>
-         </listitem>
-         <listitem>
-          <para><varname>max_pool_size</></para>
-          <para>Maximum number of connections in pool</para>
-         </listitem>
-         <listitem>
-          <para><varname>max_coordinators</></para>
-          <para>Maximum number of Coordinators that can be defined in local node</para>
-         </listitem>
-         <listitem>
-          <para><varname>max_datanodes</></para>
-          <para>Maximum number of Datanodes that can be defined in local node</para>
-         </listitem>
-         <listitem>
-          <para><varname>gtm_host</></para>
-          <para>Host to connect to GTM</para>
-         </listitem>
-         <listitem>
-          <para><varname>gtm_port</></para>
-          <para>Port to connect to GTM</para>
-         </listitem>
-         <listitem>
-          <para><varname>pgxc_node_name</></para>
-          <para>Name of the local node. This is currently set by initdb.</para>
-         </listitem>
-        </itemizedlist>
-       </para>
-      </listitem>
-     </itemizedlist>
-   </sect3>
-
-   <sect3>
-    <title>SQL extensions for <productname>Postgres-XL</></title>
-
-    <para>
-     This section lists all the new SQL functionalities and system functions that 
-     and can be used to manage a cluster environment.
-    </para>
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       <link linkend="SQL-CREATENODE"><command>CREATE NODE</></link>,
-       <link linkend="SQL-ALTERNODE"><command>ALTER NODE</></link>,
-       <link linkend="SQL-DROPNODE"><command>DROP NODE</></link>
-      </para>
-      <para>
-       These SQL commands are used to manage cluster node information in catalog
-       <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>.
-      </para>
-      <para>
-       These commands run only on the local node where they are run, and running them on Datanodes
-       make no sense as this catalog data is used only by Coordinator to identify remote nodes
-       and by connection pooling to get necessary remote connection information.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="SQL-CREATENODEGROUP"><command>CREATE NODE GROUP</></link>,
-       <link linkend="SQL-DROPNODEGROUP"><command>DROP NODE GROUP</></link>
-      </para>
-      <para>
-       <command>CREATE NODE GROUP</> and <command>DROP NODE GROUP</> manage the node groups that
-       can be used when creating a table with the extension <command>TO GROUP</> of <command>CREATE TABLE</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="SQL-CREATEBARRIER"><command>CREATE BARRIER</></link>
-      </para>
-      <para>
-       When specified with an ID, this command allows to register in all of the nodes of the cluster
-       a common and consistent time point to be able to recover all the nodes consistently back to
-       this point. Internally, a barrier is written in the WAL file of all of the nodes.
-      </para>
-      <para>
-       <varname>recovery_target_barrier</varname> in <filename>recovery.conf</> can be used to recover
-        a node to a given barrier ID.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="SQL-CLEANCONNECTION"><command>CLEAN CONNECTION</></link> 
-      </para>
-      <para>
-       <command>CLEAN CONNECTION</command> is a connection pooling utility able to drop connections on chosen node(s)
-       for a given database or/and user.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>pgxc_pool_check()</>, <function>pgxc_pool_reload()</>
-      </para>
-      <para>
-       Those system functions can be used to check or update the data cached in pooler with
-       <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname></link>. <function>pgxc_pool_check()</>
-       checks if the connection information is consistent between pooler cache and catalogs.
-       <function>pgxc_pool_reload()</> updates the connection information cached in pool.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="SQL-EXECUTEDIRECT"><command>EXECUTE DIRECT</></link>
-      </para>
-      <para>
-       <command>EXECUTE DIRECT</> can be used to launch a query directly to a given node. Only a single node
-       can be targetted at the same time.
-      </para>
-      <para>
-       <command>INSERT</command>, <command>UPDATE</command> and <command>DELETE</command> are not authorized.
-      </para>
-      <para>
-       Utilities are basically forbidden but some are authorized for cluster management purposes.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <link linkend="SQL-PAUSECLUSTER"><command>PAUSE CLUSTER</></link>
-       <link linkend="SQL-UNPAUSECLUSTER"><command>UNPAUSE CLUSTER</></link>
-      </para>
-      <para>
-       <command>PAUSE CLUSTER</> and <command>UNPAUSE CLUSTER</>
-       can be used to halt other cluster activity except for the session
-       that invoked it.  Client sessions are not disconnected, they just
-       are paused until brief maintenance is done, like restarting 
-       or moving a Datanode.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect3>
-
-   <sect3>
-    <title>Restrictions</title>
-
-     <itemizedlist>
-      <listitem>
-       <para>List of all the unsupported SQL commands</para>
-       <para>
-        <link linkend="SQL-CREATEEXTENSION"><command>CREATE EXTENSION</></link>,
-        <link linkend="SQL-ALTEREXTENSION"><command>ALTER EXTENSION</></link>,
-        <link linkend="SQL-DROPEXTENSION"><command>DROP EXTENSION</></link>,
-        <link linkend="SQL-CREATEFOREIGNDATAWRAPPER"><command>CREATE FOREIGN DATA WRAPPER</></link>,
-        <link linkend="SQL-ALTERFOREIGNDATAWRAPPER"><command>ALTER FOREIGN DATA WRAPPER</></link>,
-        <link linkend="SQL-DROPFOREIGNDATAWRAPPER"><command>DROP FOREIGN DATA WRAPPER</></link>,
-        <link linkend="SQL-CREATEFOREIGNTABLE"><command>CREATE FOREIGN TABLE</></link>,
-        <link linkend="SQL-ALTERFOREIGNTABLE"><command>ALTER FOREIGN TABLE</></link>,
-        <link linkend="SQL-DROPFOREIGNTABLE"><command>DROP FOREIGN TABLE</></link>,
-        <link linkend="SQL-ALTERLARGEOBJECT"><command>ALTER LARGE OBJECT</></link>,
-        <link linkend="SQL-CREATESERVER"><command>CREATE SERVER</></link>,
-        <link linkend="SQL-ALTERSERVER"><command>ALTER SERVER</></link>,
-        <link linkend="SQL-DROPSERVER"><command>DROP SERVER</></link>,
-        <link linkend="SQL-CREATETRIGGER"><command>CREATE TRIGGER</></link>,
-        <link linkend="SQL-ALTERTRIGGER"><command>ALTER TRIGGER</></link>,
-        <link linkend="SQL-DROPTRIGGER"><command>DROP TRIGGER</></link>,
-        <link linkend="SQL-CREATEUSERMAPPING"><command>CREATE USER MAPPING</></link>,
-        <link linkend="SQL-ALTERUSERMAPPING"><command>ALTER USER MAPPING</></link>,
-        <link linkend="SQL-DROPUSERMAPPING"><command>DROP USER MAPPING</></link>,
-        <link linkend="SQL-LISTEN"><command>LISTEN</></link>,
-        <link linkend="SQL-NOTIFY"><command>NOTIFY</></link>,
-        <link linkend="SQL-RELEASE-SAVEPOINT"><command>RELEASE SAVEPOINT</></link>,
-        <link linkend="SQL-ROLLBACK-TO"><command>ROLLBACK TO SAVEPOINT</></link>,
-        <link linkend="SQL-SAVEPOINT"><command>SAVEPOINT</></link>,
-        <link linkend="SQL-SECURITY-LABEL"><command>SECURITY LABEL</></link>,
-        <link linkend="SQL-UNLISTEN"><command>UNLISTEN</></link>,
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Table distribution definition cannot be changed.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Distribution key of a table cannot be updated.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Triggers are not supported
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Functions are always pushed down to the data nodes. This can be dangerous if a stored function tries to use data that is really on another node!  Use with caution; it will only use data local to the node, so updates should not be done.  The documentation in this area to make this clearer.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The CLUSTER command is currently broken if used without any arguments. CLUSTER does work for one table at a time, however.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        WITH queries work, however, WITH RECURSIVE is currently blocked.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        ORDER BY currently cannot be used in subqueries.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Sequences currently cannot be used in temp tables.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <command>CREATE TABLE AS EXECUTE</command> is not supported.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Barriers have no timeout, meaning that if a 2PC transaction is
-        stuck forever, the barrier will be stuck too.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The regression test suite needs further refinement. Some of the listed differences are because of an unsupported feature which manipulates the data set and throws off expected results. In addition, the expected plan output for some should be udpated.
-       </para>
-      </listitem>
-
-     </itemizedlist>
-
-   </sect3>
-   </sect2>
-
- </sect1>
diff --git a/doc-xc/src/sgml/release.sgmlin b/doc-xc/src/sgml/release.sgmlin
deleted file mode 100644
index 8c01ec1d40..0000000000
--- a/doc-xc/src/sgml/release.sgmlin
+++ /dev/null
@@ -1,127 +0,0 @@
-<!-- doc/src/sgml/release.sgml -->
-<!--
-
-Typical markup:
-
-&<>                             use & escapes
-PostgreSQL                      <productname>
-postgresql.conf, pg_hba.conf,
-        recovery.conf           <filename>
-[A-Z][A-Z_ ]+[A-Z_]             <command>, <literal>, <envar>
-[A-Za-z_][A-Za-z0-9_]+()        <function>
--[-A-Za-z_]+                    <option>
-[A-Za-z_]/[A-Za-z_]+            <filename>
-psql                            <application>
-pg_[A-Za-z0-9_]+                <application>, <structname>
-[A-Z][A-Z][A-Z_ ]*              <type>, <varname>
-
-non-ASCII characters            convert to HTML4 entity (&) escapes
-
-        official:      http://www.w3.org/TR/html4/sgml/entities.html
-        one page:      http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html
-        other lists:   http://www.zipcon.net/~swhite/docs/computers/browsers/entities.html
-                       http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html
-                       http://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references
-
-        we cannot use UTF8 because SGML Docbook
-        does not support it
-          http://www.pemberley.com/janeinfo/latin1.html#latexta
-
-wrap long lines
-
-For new features, add links to the documentation sections.  Use </link>
-not just </> so that generate_history.pl can remove it, so HISTORY.html
-can be created without links to the main documentation.  Don't use <xref>.
-
--->
-
-<appendix id="release">
- <title>Release Notes</title>
-
-  <para>
-   The release notes contain the significant changes in each
-<!## XC>
-   <productname>Postgres-XC</> release, with major features and migration
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> release, with major features and migration
-<!## end>
-<!## PG>
-   <productname>PostgreSQL</> release, with major features and migration
-<!## end>
-   issues listed at the top.  The release notes do not contain changes
-   that affect only a few users or changes that are internal and therefore not
-   user-visible.  For example, the optimizer is improved in almost every
-   release, but the improvements are usually observed by users as simply
-   faster queries.
-  </para>
-
-<!## XC>
-  <para>
-   A complete list of changes for each release can be obtained by
-   viewing the <link linkend="git">Git</link> logs for each release.
-   The <ulink
-   url="https://sourceforge.net/mailarchive/forum.php?forum_name=postgres-xc-committers">
-   <literal>postgres-xc-committers</literal>
-   email list</ulink> records all source code changes as well.  There is also
-   a <ulink url="http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary">web
-   interface</ulink> that shows changes to specific files.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   A complete list of changes for each release can be obtained by
-   viewing the <link linkend="git">Git</link> logs for each release.
-   The <ulink
-   url="https://sourceforge.net/mailarchive/forum.php?forum_name=postgres-xl-committers">
-   <literal>postgres-xl-committers</literal>
-   email list</ulink> records all of the source code changes as well.  There is also
-   a <ulink url="http://postgres-xl.git.sourceforge.net/git/gitweb.cgi?p=postgres-xl/postgres-xl;a=summary">web
-   interface</ulink> that shows changes to specific files.
-  </para>
-<!## end>
-<!## PG>
-  <para>
-   A complete list of changes for each release can be obtained by
-   viewing the <link linkend="git">Git</link> logs for each release.
-   The <ulink
-   url="http://archives.postgres-xl.org/pgxl-committers/"><literal>pgxl-committers</literal>
-   email list</ulink> records all source code changes as well.  There is also
-   a <ulink url="http://git.postgres-xl.org/gitweb?p=postgres-xl;a=summary">web
-   interface</ulink> that shows changes to specific files.
-  </para>
-<!## end>
-
-  <para>
-   The name appearing next to each item represents the major developer for
-   that item.  Of course all changes involve community discussion and patch
-   review, so each item is truly a community effort.
-  </para>
-
-&release-xl-9.2;
-<!--
-  To add a new major-release series, add an entry here and in filelist.sgml.
-  Follow the naming convention, or you'll confuse generate_history.pl.
-
-  The reason for splitting the release notes this way is so that appropriate
-  subsets can easily be copied into back branches.
-<!## XL>
-&release-xl-9.2;
-<!## end>
--->
-<!## XC>
-&release-xc-1.0;
-<!## end>
-<!## PG>
-&release-9.1;
-&release-9.0;
-&release-8.4;
-&release-8.3;
-&release-8.2;
-&release-8.1;
-&release-8.0;
-&release-7.4;
-&release-old;
-<!## end>
-
-</appendix>
diff --git a/doc-xc/src/sgml/remove-node.sgmlin b/doc-xc/src/sgml/remove-node.sgmlin
deleted file mode 100644
index 8573abc3d7..0000000000
--- a/doc-xc/src/sgml/remove-node.sgmlin
+++ /dev/null
@@ -1,160 +0,0 @@
-<!-- doc/src/sgml/remove-node.sgml -->
-
-<chapter id="remove-node">
- <title>Removing an Existing Node</title>
-
- <indexterm zone="remove-node">
-  <primary>Remove an existing node</primary>
- </indexterm>
-
-<!## XC>
-&xconly;
-<!## end>
-<!## XL>
-&xlonly;
-<!## end>
-
- <para>
-  This chapter outlines steps to remove an existing coordinator or a datanode from a running cluster.
- </para>
-
-  <para>
-  </para>
-
- <sect1 id="remove-node-coordinator">
-  <title>Removing an Existing Coordinator</title>
-
-  <indexterm zone="remove-node-coordinator">
-   <primary>Remove an existing coordinator</primary>
-  </indexterm>
-
-  <para>
-    Assume a two coordinator cluster, COORD_1 and COORD_2. Suppose we want to remove COORD_2 for any reason. The following steps should be performed to remove an existing coordinator from a running cluster:
-  </para>
-
-  <para>
-    <orderedlist>
-      <listitem>
-        <para>
-          Stop the coordinator to be removed. In our example we need to stop COORD_2.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Connect to any of the coordinators except the one to be removed. In our example assuming COORD_1 is running on port 5432, the following command would connect to COORD_1
-        </para>
-        <programlisting>
-          psql postgres -p 5432
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Drop the coordinator to be removed. For example to drop coordinator COORD_2
-        </para>
-        <programlisting>
-          DROP NODE COORD_2;
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Update the connection information cached in pooler.
-        </para>
-        <programlisting>
-          SELECT pgxc_pool_reload();
-        </programlisting>
-      </listitem>
-
-    </orderedlist>
-  </para>
-  <para>
-    COORD_2 is now removed from the cluster and COORD_1 would work as if COORD_2 never existed.
-  </para>
-  <para>
-    CAUTION : If COORD_2 is still running and clients are connected to it, any queries issued would create inconsistencies in the cluster.
-  </para>
-
- </sect1>
-
- <sect1 id="remove-node-datanode">
-  <title>Removing an Existing Datanode</title>
-
-  <indexterm zone="remove-node-datanode">
-   <primary>Remove an existing Datanode</primary>
-  </indexterm>
-
-  <para>
-    Assume a two coordinator cluster, COORD_1 and COORD_2 with three datanodes DATA_NODE_1, DATA_NODE_2 and DATA_NODE_3. Suppose we want to remove DATA_NODE_3 for any reason. Further assume there is a table named rr_tab_foo distributed in round robin fashion and has rows on all the three datanodes. Following steps should be performed to remove an existing datanode from a running cluster:
-  </para>
-
-  <para>
-    <orderedlist>
-
-      <listitem>
-        <para>
-          Transfer the data from the datanode to be removed to the rest of the datanodes for all the tables in all the databases. For example to shift data of the table rr_tab_foo to the rest of the nodes we can use command:
-        </para>
-        <programlisting>
-          ALTER TABLE rr_tab_foo DELETE NODE (DATA_NODE_3);
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Confirm that there is no data left on the datanode to be removed. For example to confirm that there is no data left on DATA_NODE_3, we can use the following command, it should return ZERO rows. In case of non-zero rows it returns the OIDs of the relations whose data still exists on DATA_NODE_3.
-        </para>
-        <programlisting>
-          SELECT c.pcrelid FROM pgxc_class c, pgxc_node n WHERE n.node_name = 'DATA_NODE_3' AND n.oid = ANY (c.nodeoids);
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Stop the datanode server to be removed. Now any SELECTs or DMLs that involve the datanode to be removed would start failing.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Connect to any of the coordinators. In our example assuming COORD_1 is running on port 5432, the following command would connect to COORD_1.
-        </para>
-        <programlisting>
-          psql postgres -p 5432
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Drop the datanode to be removed. For example to drop datanode DATA_NODE_3 use command.
-        </para>
-        <programlisting>
-          DROP NODE DATA_NODE_3;
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Update the connection information cached in pooler.
-        </para>
-        <programlisting>
-          SELECT pgxc_pool_reload();
-        </programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Repeat the above three steps (4,5,6) for all the coordinators in the cluster. In our example we would need to repeat the above steps by connecting to COORD_2.
-        </para>
-      </listitem>
-
-    </orderedlist>
-  </para>
-  <para>
-    DATA_NODE_3 is now removed from the cluster.
-  </para>
-
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/rowtypes.sgmlin b/doc-xc/src/sgml/rowtypes.sgmlin
deleted file mode 100644
index 949024110b..0000000000
--- a/doc-xc/src/sgml/rowtypes.sgmlin
+++ /dev/null
@@ -1,332 +0,0 @@
-<!-- doc/src/sgml/rowtypes.sgml -->
-
-<sect1 id="rowtypes">
- <title>Composite Types</title>
-
- <indexterm>
-  <primary>composite type</primary>
- </indexterm>
-
- <indexterm>
-  <primary>row type</primary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  A <firstterm>composite type</> represents the structure of a row or record;
-  it is essentially just a list of field names and their data types.
-  <productname>PostgreSQL</productname> allows  composite types to be
-  used in many of the same ways that simple types can be used.  For example, a
-  column of a table can be declared to be of a composite type.
- </para>
-
- <sect2>
-  <title>Declaration of Composite Types</title>
-
- <para>
-  Here are two simple examples of defining composite types:
-<programlisting>
-CREATE TYPE complex AS (
-    r       double precision,
-    i       double precision
-);
-
-CREATE TYPE inventory_item AS (
-    name            text,
-    supplier_id     integer,
-    price           numeric
-);
-</programlisting>
-  The syntax is comparable to <command>CREATE TABLE</>, except that only
-  field names and types can be specified; no constraints (such as <literal>NOT
-  NULL</>) can presently be included.  Note that the <literal>AS</> keyword
-  is essential; without it, the system will think a different kind
-  of <command>CREATE TYPE</> command is meant, and you will get odd syntax
-  errors.
- </para>
-
- <para>
-  Having defined the types, we can use them to create tables:
-
-<programlisting>
-CREATE TABLE on_hand (
-    item      inventory_item,
-    count     integer
-);
-
-INSERT INTO on_hand VALUES (ROW('fuzzy dice', 42, 1.99), 1000);
-</programlisting>
-
-  or functions:
-
-<programlisting>
-CREATE FUNCTION price_extension(inventory_item, integer) RETURNS numeric
-AS 'SELECT $1.price * $2' LANGUAGE SQL;
-
-SELECT price_extension(item, 10) FROM on_hand;
-</programlisting>
-
- </para>
-
- <para>
-  Whenever you create a table, a composite type is also automatically
-  created, with the same name as the table, to represent the table's
-  row type.  For example, had we said:
-<programlisting>
-CREATE TABLE inventory_item (
-    name            text,
-    supplier_id     integer REFERENCES suppliers,
-    price           numeric CHECK (price &gt; 0)
-);
-</programlisting>
-  then the same <literal>inventory_item</> composite type shown above would
-  come into being as a
-  byproduct, and could be used just as above.  Note however an important
-  restriction of the current implementation: since no constraints are
-  associated with a composite type, the constraints shown in the table
-  definition <emphasis>do not apply</> to values of the composite type
-  outside the table.  (A partial workaround is to use domain
-  types as members of composite types.)
- </para>
- </sect2>
-
- <sect2>
-  <title>Composite Value Input</title>
-
-  <indexterm>
-   <primary>composite type</primary>
-   <secondary>constant</secondary>
-  </indexterm>
-
-  <para>
-   To write a composite value as a literal constant, enclose the field
-   values within parentheses and separate them by commas.  You can put double
-   quotes around any field value, and must do so if it contains commas or
-   parentheses.  (More details appear below.)  Thus, the general format of a
-   composite constant is the following:
-<synopsis>
-'( <replaceable>val1</replaceable> , <replaceable>val2</replaceable> , ... )'
-</synopsis>
-   An example is:
-<programlisting>
-'("fuzzy dice",42,1.99)'
-</programlisting>
-   which would be a valid value of the <literal>inventory_item</> type
-   defined above.  To make a field be NULL, write no characters at all
-   in its position in the list.  For example, this constant specifies
-   a NULL third field:
-<programlisting>
-'("fuzzy dice",42,)'
-</programlisting>
-   If you want an empty string rather than NULL, write double quotes:
-<programlisting>
-'("",42,)'
-</programlisting>
-   Here the first field is a non-NULL empty string, the third is NULL.
-  </para>
-
-  <para>
-   (These constants are actually only a special case of
-   the generic type constants discussed in <xref
-   linkend="sql-syntax-constants-generic">.  The constant is initially
-   treated as a string and passed to the composite-type input conversion
-   routine.  An explicit type specification might be necessary.)
-  </para>
-
- <para>
-  The <literal>ROW</literal> expression syntax can also be used to
-  construct composite values.  In most cases this is considerably
-  simpler to use than the string-literal syntax since you don't have
-  to worry about multiple layers of quoting.  We already used this
-  method above:
-<programlisting>
-ROW('fuzzy dice', 42, 1.99)
-ROW('', 42, NULL)
-</programlisting>
-  The ROW keyword is actually optional as long as you have more than one
-  field in the expression, so these can simplify to:
-<programlisting>
-('fuzzy dice', 42, 1.99)
-('', 42, NULL)
-</programlisting>
-  The <literal>ROW</> expression syntax is discussed in more detail in <xref
-  linkend="sql-syntax-row-constructors">.
- </para>
- </sect2>
-
- <sect2>
-  <title>Accessing Composite Types</title>
-
- <para>
-  To access a field of a composite column, one writes a dot and the field
-  name, much like selecting a field from a table name.  In fact, it's so
-  much like selecting from a table name that you often have to use parentheses
-  to keep from confusing the parser.  For example, you might try to select
-  some subfields from our <literal>on_hand</> example table with something
-  like:
-
-<programlisting>
-SELECT item.name FROM on_hand WHERE item.price &gt; 9.99;
-</programlisting>
-
-  This will not work since the name <literal>item</> is taken to be a table
-  name, not a column name of <literal>on_hand</>, per SQL syntax rules.
-  You must write it like this:
-
-<programlisting>
-SELECT (item).name FROM on_hand WHERE (item).price &gt; 9.99;
-</programlisting>
-
-  or if you need to use the table name as well (for instance in a multitable
-  query), like this:
-
-<programlisting>
-SELECT (on_hand.item).name FROM on_hand WHERE (on_hand.item).price &gt; 9.99;
-</programlisting>
-
-  Now the parenthesized object is correctly interpreted as a reference to
-  the <literal>item</> column, and then the subfield can be selected from it.
- </para>
-
- <para>
-  Similar syntactic issues apply whenever you select a field from a composite
-  value.  For instance, to select just one field from the result of a function
-  that returns a composite value, you'd need to write something like:
-
-<programlisting>
-SELECT (my_func(...)).field FROM ...
-</programlisting>
-
-  Without the extra parentheses, this will generate a syntax error.
- </para>
- </sect2>
-
- <sect2>
-  <title>Modifying Composite Types</title>
-
- <para>
-  Here are some examples of the proper syntax for inserting and updating
-  composite columns.
-  First, inserting or updating a whole column:
-
-<programlisting>
-INSERT INTO mytab (complex_col) VALUES((1.1,2.2));
-
-UPDATE mytab SET complex_col = ROW(1.1,2.2) WHERE ...;
-</programlisting>
-
-  The first example omits <literal>ROW</>, the second uses it; we
-  could have done it either way.
- </para>
-
- <para>
-  We can update an individual subfield of a composite column:
-
-<programlisting>
-UPDATE mytab SET complex_col.r = (complex_col).r + 1 WHERE ...;
-</programlisting>
-
-  Notice here that we don't need to (and indeed cannot)
-  put parentheses around the column name appearing just after
-  <literal>SET</>, but we do need parentheses when referencing the same
-  column in the expression to the right of the equal sign.
- </para>
-
- <para>
-  And we can specify subfields as targets for <command>INSERT</>, too:
-
-<programlisting>
-INSERT INTO mytab (complex_col.r, complex_col.i) VALUES(1.1, 2.2);
-</programlisting>
-
-  Had we not supplied values for all the subfields of the column, the
-  remaining subfields would have been filled with null values.
- </para>
- </sect2>
-
- <sect2>
-  <title>Composite Type Input and Output Syntax</title>
-
-  <para>
-   The external text representation of a composite value consists of items that
-   are interpreted according to the I/O conversion rules for the individual
-   field types, plus decoration that indicates the composite structure.
-   The decoration consists of parentheses (<literal>(</> and <literal>)</>)
-   around the whole value, plus commas (<literal>,</>) between adjacent
-   items.  Whitespace outside the parentheses is ignored, but within the
-   parentheses it is considered part of the field value, and might or might not be
-   significant depending on the input conversion rules for the field data type.
-   For example, in:
-<programlisting>
-'(  42)'
-</programlisting>
-   the whitespace will be ignored if the field type is integer, but not if
-   it is text.
-  </para>
-
-  <para>
-   As shown previously, when writing a composite value you can write double
-   quotes around any individual field value.
-   You <emphasis>must</> do so if the field value would otherwise
-   confuse the composite-value parser.  In particular, fields containing
-   parentheses, commas, double quotes, or backslashes must be double-quoted.
-   To put a double quote or backslash in a quoted composite field value,
-   precede it with a backslash.  (Also, a pair of double quotes within a
-   double-quoted field value is taken to represent a double quote character,
-   analogously to the rules for single quotes in SQL literal strings.)
-   Alternatively, you can avoid quoting and use backslash-escaping to
-   protect all data characters
-   that would otherwise be taken as composite syntax.
-  </para>
-
-  <para>
-   A completely empty field value (no characters at all between the commas
-   or parentheses) represents a NULL.  To write a value that is an empty
-   string rather than NULL, write <literal>""</>.
-  </para>
-
-  <para>
-   The composite output routine will put double quotes around field values
-   if they are empty strings or contain parentheses, commas,
-   double quotes, backslashes, or white space.  (Doing so for white space
-   is not essential, but aids legibility.)  Double quotes and backslashes
-   embedded in field values will be doubled.
-  </para>
-
- <note>
-  <para>
-   Remember that what you write in an SQL command will first be interpreted
-   as a string literal, and then as a composite.  This doubles the number of
-   backslashes you need (assuming escape string syntax is used).
-   For example, to insert a <type>text</> field
-   containing a double quote and a backslash in a composite
-   value, you'd need to write:
-<programlisting>
-INSERT ... VALUES (E'("\\"\\\\")');
-</programlisting>
-   The string-literal processor removes one level of backslashes, so that
-   what arrives at the composite-value parser looks like
-   <literal>("\"\\")</>.  In turn, the string
-   fed to the <type>text</> data type's input routine
-   becomes <literal>"\</>.  (If we were working
-   with a data type whose input routine also treated backslashes specially,
-   <type>bytea</> for example, we might need as many as eight backslashes
-   in the command to get one backslash into the stored composite field.)
-   Dollar quoting (see <xref linkend="sql-syntax-dollar-quoting">) can be
-   used to avoid the need to double backslashes.
-  </para>
- </note>
-
- <tip>
-  <para>
-   The <literal>ROW</> constructor syntax is usually easier to work with
-   than the composite-literal syntax when writing composite values in SQL
-   commands.
-   In <literal>ROW</>, individual field values are written the same way
-   they would be written when not members of a composite.
-  </para>
- </tip>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/rules.sgmlin b/doc-xc/src/sgml/rules.sgmlin
deleted file mode 100644
index 174787d298..0000000000
--- a/doc-xc/src/sgml/rules.sgmlin
+++ /dev/null
@@ -1,2212 +0,0 @@
-<!-- doc/src/sgml/rules.sgml -->
-
-<chapter id="rules">
-<title>The Rule System</title>
-
- <indexterm zone="rules">
-  <primary>rule</primary>
- </indexterm>
-
-&common;
-
-<para>
-     This chapter discusses the rule system in
-     <productname>PostgreSQL</productname>.  Production rule systems
-     are conceptually simple, but there are many subtle points
-     involved in actually using them.
-</para>
-
-<para>
-     Some other database systems define active database rules, which
-     are usually stored procedures and triggers.  In
-     <productname>PostgreSQL</productname>, these can be implemented
-     using functions and triggers as well.
-</para>
-
-<para>
-     The rule system (more precisely speaking, the query rewrite rule
-     system) is totally different from stored procedures and triggers.
-     It modifies queries to take rules into consideration, and then
-     passes the modified query to the query planner for planning and
-     execution.  It is very powerful, and can be used for many things
-     such as query language procedures, views, and versions.  The
-     theoretical foundations and the power of this rule system are
-     also discussed in <xref linkend="STON90b"> and <xref
-     linkend="ONG90">.
-</para>
-
-<sect1 id="querytree">
-<title>The Query Tree</title>
-
-<indexterm zone="querytree">
- <primary>query tree</primary>
-</indexterm>
-
-&common;
-<para>
-    To understand how the rule system works it is necessary to know
-    when it is invoked and what its input and results are.
-</para>
-
-<para>
-    The rule system is located between the parser and the planner.
-    It takes the output of the parser, one query tree, and the user-defined
-    rewrite rules, which are also
-    query trees with some extra information, and creates zero or more
-    query trees as result. So its input and output are always things
-    the parser itself could have produced and thus, anything it sees
-    is basically representable as an <acronym>SQL</acronym> statement.
-</para>
-
-<para>
-    Now what is a query tree? It is an internal representation of an
-    <acronym>SQL</acronym> statement where the single parts that it is
-    built from are stored separately. These query trees can be shown
-    in the server log if you set the configuration parameters
-    <varname>debug_print_parse</varname>,
-    <varname>debug_print_rewritten</varname>, or
-    <varname>debug_print_plan</varname>.  The rule actions are also
-    stored as query trees, in the system catalog
-    <structname>pg_rewrite</structname>.  They are not formatted like
-    the log output, but they contain exactly the same information.
-</para>
-
-<para>
-    Reading a raw query tree requires some experience.  But since
-    <acronym>SQL</acronym> representations of query trees are
-    sufficient to understand the rule system, this chapter will not
-    teach how to read them.
-</para>
-
-<para>
-    When reading the <acronym>SQL</acronym> representations of the
-    query trees in this chapter it is necessary to be able to identify
-    the parts the statement is broken into when it is in the query tree
-    structure. The parts of a query tree are
-
-<variablelist>
-    <varlistentry>
-    <term>
-        the command type
-    </term>
-    <listitem>
-    <para>
-        This is a simple value telling which command
-        (<command>SELECT</command>, <command>INSERT</command>,
-        <command>UPDATE</command>, <command>DELETE</command>) produced
-        the query tree.
-    </para>
-    </listitem>
-    </varlistentry>
-
-    <varlistentry>
-    <term>
-        the range table
-    </term>
-      <indexterm><primary>range table</></>
-    <listitem>
-    <para>
-        The range table is a list of relations that are used in the query.
-        In a <command>SELECT</command> statement these are the relations given after
-        the <literal>FROM</literal> key word.
-    </para>
-
-    <para>
-        Every range table entry identifies a table or view and tells
-        by which name it is called in the other parts of the query.
-        In the query tree, the range table entries are referenced by
-        number rather than by name, so here it doesn't matter if there
-        are duplicate names as it would in an <acronym>SQL</acronym>
-        statement. This can happen after the range tables of rules
-        have been merged in. The examples in this chapter will not have
-        this situation.
-    </para>
-    </listitem>
-    </varlistentry>
-
-    <varlistentry>
-    <term>
-        the result relation
-    </term>
-    <listitem>
-    <para>
-        This is an index into the range table that identifies the
-        relation where the results of the query go.
-    </para>
-
-    <para>
-        <command>SELECT</command> queries don't have a result
-        relation. (The special case of <command>SELECT INTO</command> is
-        mostly identical to <command>CREATE TABLE</command> followed by
-        <literal>INSERT ... SELECT</literal>, and is not discussed
-        separately here.)
-    </para>
-
-    <para>
-        For <command>INSERT</command>, <command>UPDATE</command>, and
-        <command>DELETE</command> commands, the result relation is the table
-        (or view!) where the changes are to take effect.
-    </para>
-    </listitem>
-    </varlistentry>
-
-    <varlistentry>
-    <term>
-        the target list
-    </term>
-    <indexterm><primary>target list</></>
-    <listitem>
-    <para>
-        The target list is a list of expressions that define the
-        result of the query.  In the case of a
-        <command>SELECT</command>, these expressions are the ones that
-        build the final output of the query.  They correspond to the
-        expressions between the key words <command>SELECT</command>
-        and <command>FROM</command>.  (<literal>*</literal> is just an
-        abbreviation for all the column names of a relation.  It is
-        expanded by the parser into the individual columns, so the
-        rule system never sees it.)
-    </para>
-
-    <para>
-        <command>DELETE</command> commands don't need a normal target list
-        because they don't produce any result.  Instead, the rule system
-        adds a special <acronym>CTID</> entry to the empty target list,
-        to allow the executor to find the row to be deleted.
-        (<acronym>CTID</> is added when the result relation is an ordinary
-        table.  If it is a view, a whole-row variable is added instead,
-        as described in <xref linkend="rules-views-update">.)
-    </para>
-
-    <para>
-        For <command>INSERT</command> commands, the target list describes
-        the new rows that should go into the result relation. It consists of the
-        expressions in the <literal>VALUES</> clause or the ones from the
-        <command>SELECT</command> clause in <literal>INSERT
-        ... SELECT</literal>.  The first step of the rewrite process adds
-        target list entries for any columns that were not assigned to by
-        the original command but have defaults.  Any remaining columns (with
-        neither a given value nor a default) will be filled in by the
-        planner with a constant null expression.
-    </para>
-
-    <para>
-        For <command>UPDATE</command> commands, the target list
-        describes the new rows that should replace the old ones. In the
-        rule system, it contains just the expressions from the <literal>SET
-        column = expression</literal> part of the command.  The planner will
-        handle missing columns by inserting expressions that copy the values
-        from the old row into the new one.  Just as for <command>DELETE</>,
-        the rule system adds a <acronym>CTID</> or whole-row variable so that
-        the executor can identify the old row to be updated.
-    </para>
-
-    <para>
-        Every entry in the target list contains an expression that can
-        be a constant value, a variable pointing to a column of one
-        of the relations in the range table, a parameter, or an expression
-        tree made of function calls, constants, variables, operators, etc.
-    </para>
-    </listitem>
-    </varlistentry>
-
-    <varlistentry>
-    <term>
-        the qualification
-    </term>
-    <listitem>
-    <para>
-        The query's qualification is an expression much like one of
-        those contained in the target list entries. The result value of
-        this expression is a Boolean that tells whether the operation
-        (<command>INSERT</command>, <command>UPDATE</command>,
-        <command>DELETE</command>, or <command>SELECT</command>) for the
-        final result row should be executed or not. It corresponds to the <literal>WHERE</> clause
-        of an <acronym>SQL</acronym> statement.
-    </para>
-    </listitem>
-    </varlistentry>
-
-    <varlistentry>
-    <term>
-        the join tree
-    </term>
-    <listitem>
-    <para>
-        The query's join tree shows the structure of the <literal>FROM</> clause.
-        For a simple query like <literal>SELECT ... FROM a, b, c</literal>, the join tree is just
-        a list of the <literal>FROM</> items, because we are allowed to join them in
-        any order.  But when <literal>JOIN</> expressions, particularly outer joins,
-        are used, we have to join in the order shown by the joins.
-        In that case, the join tree shows the structure of the <literal>JOIN</> expressions.  The
-        restrictions associated with particular <literal>JOIN</> clauses (from <literal>ON</> or
-        <literal>USING</> expressions) are stored as qualification expressions attached
-        to those join-tree nodes.  It turns out to be convenient to store
-        the top-level <literal>WHERE</> expression as a qualification attached to the
-        top-level join-tree item, too.  So really the join tree represents
-        both the <literal>FROM</> and <literal>WHERE</> clauses of a <command>SELECT</command>.
-    </para>
-    </listitem>
-    </varlistentry>
-
-    <varlistentry>
-    <term>
-        the others
-    </term>
-    <listitem>
-    <para>
-        The other parts of the query tree like the <literal>ORDER BY</>
-        clause aren't of interest here. The rule system
-        substitutes some entries there while applying rules, but that
-        doesn't have much to do with the fundamentals of the rule
-        system.
-    </para>
-    </listitem>
-    </varlistentry>
-
-</variablelist>
-</para>
-</sect1>
-
-<sect1 id="rules-views">
-<title>Views and the Rule System</title>
-
-<indexterm zone="rules-views">
- <primary>rule</primary>
- <secondary>and views</secondary>
-</indexterm>
-
-<indexterm zone="rules-views">
- <primary>view</>
- <secondary>implementation through rules</>
-</indexterm>
-
-&common;
-<para>
-    Views in <productname>PostgreSQL</productname> are implemented
-    using the rule system. In fact, there is essentially no difference
-    between:
-
-<programlisting>
-CREATE VIEW myview AS SELECT * FROM mytab;
-</programlisting>
-
-    compared against the two commands:
-
-<programlisting>
-CREATE TABLE myview (<replaceable>same column list as mytab</replaceable>);
-CREATE RULE "_RETURN" AS ON SELECT TO myview DO INSTEAD
-    SELECT * FROM mytab;
-</programlisting>
-
-    because this is exactly what the <command>CREATE VIEW</command>
-    command does internally.  This has some side effects. One of them
-    is that the information about a view in the
-    <productname>PostgreSQL</productname> system catalogs is exactly
-    the same as it is for a table. So for the parser, there is
-    absolutely no difference between a table and a view. They are the
-    same thing: relations.
-</para>
-
-<sect2 id="rules-select">
-<title>How <command>SELECT</command> Rules Work</title>
-
-<indexterm zone="rules-select">
- <primary>rule</primary>
- <secondary sortas="SELECT">for SELECT</secondary>
-</indexterm>
-
-&common;
-<para>
-    Rules <literal>ON SELECT</> are applied to all queries as the last step, even
-    if the command given is an <command>INSERT</command>,
-    <command>UPDATE</command> or <command>DELETE</command>. And they
-    have different semantics from rules on the other command types in that they modify the
-    query tree in place instead of creating a new one.  So
-    <command>SELECT</command> rules are described first.
-</para>
-
-<para>
-    Currently, there can be only one action in an <literal>ON SELECT</> rule, and it must
-    be an unconditional <command>SELECT</> action that is <literal>INSTEAD</>. This restriction was
-    required to make rules safe enough to open them for ordinary users, and
-    it restricts <literal>ON SELECT</> rules to act like views.
-</para>
-
-<para>
-    The examples for this chapter are two join views that do some
-    calculations and some more views using them in turn.  One of the
-    two first views is customized later by adding rules for
-    <command>INSERT</command>, <command>UPDATE</command>, and
-    <command>DELETE</command> operations so that the final result will
-    be a view that behaves like a real table with some magic
-    functionality.  This is not such a simple example to start from and
-    this makes things harder to get into. But it's better to have one
-    example that covers all the points discussed step by step rather
-    than having many different ones that might mix up in mind.
-</para>
-
-<para>
-For the example, we need a little <literal>min</literal> function that
-returns the lower of 2 integer values. We create that as:
-
-<programlisting>
-CREATE FUNCTION min(integer, integer) RETURNS integer AS $$
-    SELECT CASE WHEN $1 &lt; $2 THEN $1 ELSE $2 END
-$$ LANGUAGE SQL STRICT;
-</programlisting>
-</para>
-
-<para>
-    The real tables we need in the first two rule system descriptions
-    are these:
-
-<programlisting>
-CREATE TABLE shoe_data (
-    shoename   text,          -- primary key
-    sh_avail   integer,       -- available number of pairs
-    slcolor    text,          -- preferred shoelace color
-    slminlen   real,          -- minimum shoelace length
-    slmaxlen   real,          -- maximum shoelace length
-    slunit     text           -- length unit
-);
-
-CREATE TABLE shoelace_data (
-    sl_name    text,          -- primary key
-    sl_avail   integer,       -- available number of pairs
-    sl_color   text,          -- shoelace color
-    sl_len     real,          -- shoelace length
-    sl_unit    text           -- length unit
-);
-
-CREATE TABLE unit (
-    un_name    text,          -- primary key
-    un_fact    real           -- factor to transform to cm
-);
-</programlisting>
-
-    As you can see, they represent shoe-store data.
-</para>
-
-<para>
-    The views are created as:
-
-<programlisting>
-CREATE VIEW shoe AS
-    SELECT sh.shoename,
-           sh.sh_avail,
-           sh.slcolor,
-           sh.slminlen,
-           sh.slminlen * un.un_fact AS slminlen_cm,
-           sh.slmaxlen,
-           sh.slmaxlen * un.un_fact AS slmaxlen_cm,
-           sh.slunit
-      FROM shoe_data sh, unit un
-     WHERE sh.slunit = un.un_name;
-
-CREATE VIEW shoelace AS
-    SELECT s.sl_name,
-           s.sl_avail,
-           s.sl_color,
-           s.sl_len,
-           s.sl_unit,
-           s.sl_len * u.un_fact AS sl_len_cm
-      FROM shoelace_data s, unit u
-     WHERE s.sl_unit = u.un_name;
-
-CREATE VIEW shoe_ready AS
-    SELECT rsh.shoename,
-           rsh.sh_avail,
-           rsl.sl_name,
-           rsl.sl_avail,
-           min(rsh.sh_avail, rsl.sl_avail) AS total_avail
-      FROM shoe rsh, shoelace rsl
-     WHERE rsl.sl_color = rsh.slcolor
-       AND rsl.sl_len_cm &gt;= rsh.slminlen_cm
-       AND rsl.sl_len_cm &lt;= rsh.slmaxlen_cm;
-</programlisting>
-
-    The <command>CREATE VIEW</command> command for the
-    <literal>shoelace</literal> view (which is the simplest one we
-    have) will create a relation <literal>shoelace</> and an entry in
-    <structname>pg_rewrite</structname> that tells that there is a
-    rewrite rule that must be applied whenever the relation <literal>shoelace</>
-    is referenced in a query's range table.  The rule has no rule
-    qualification (discussed later, with the non-<command>SELECT</> rules, since
-    <command>SELECT</> rules currently cannot have them) and it is <literal>INSTEAD</>. Note
-    that rule qualifications are not the same as query qualifications.
-    The action of our rule has a query qualification.
-    The action of the rule is one query tree that is a copy of the
-    <command>SELECT</command> statement in the view creation command.
-</para>
-
-    <note>
-    <para>
-    The two extra range
-    table entries for <literal>NEW</> and <literal>OLD</> that you can see in
-    the <structname>pg_rewrite</structname> entry aren't of interest
-    for <command>SELECT</command> rules.
-    </para>
-    </note>
-
-<para>
-    Now we populate <literal>unit</literal>, <literal>shoe_data</literal>
-    and <literal>shoelace_data</literal> and run a simple query on a view:
-
-<programlisting>
-INSERT INTO unit VALUES ('cm', 1.0);
-INSERT INTO unit VALUES ('m', 100.0);
-INSERT INTO unit VALUES ('inch', 2.54);
-
-INSERT INTO shoe_data VALUES ('sh1', 2, 'black', 70.0, 90.0, 'cm');
-INSERT INTO shoe_data VALUES ('sh2', 0, 'black', 30.0, 40.0, 'inch');
-INSERT INTO shoe_data VALUES ('sh3', 4, 'brown', 50.0, 65.0, 'cm');
-INSERT INTO shoe_data VALUES ('sh4', 3, 'brown', 40.0, 50.0, 'inch');
-
-INSERT INTO shoelace_data VALUES ('sl1', 5, 'black', 80.0, 'cm');
-INSERT INTO shoelace_data VALUES ('sl2', 6, 'black', 100.0, 'cm');
-INSERT INTO shoelace_data VALUES ('sl3', 0, 'black', 35.0 , 'inch');
-INSERT INTO shoelace_data VALUES ('sl4', 8, 'black', 40.0 , 'inch');
-INSERT INTO shoelace_data VALUES ('sl5', 4, 'brown', 1.0 , 'm');
-INSERT INTO shoelace_data VALUES ('sl6', 0, 'brown', 0.9 , 'm');
-INSERT INTO shoelace_data VALUES ('sl7', 7, 'brown', 60 , 'cm');
-INSERT INTO shoelace_data VALUES ('sl8', 1, 'brown', 40 , 'inch');
-
-SELECT * FROM shoelace;
-
- sl_name   | sl_avail | sl_color | sl_len | sl_unit | sl_len_cm
------------+----------+----------+--------+---------+-----------
- sl1       |        5 | black    |     80 | cm      |        80
- sl2       |        6 | black    |    100 | cm      |       100
- sl7       |        7 | brown    |     60 | cm      |        60
- sl3       |        0 | black    |     35 | inch    |      88.9
- sl4       |        8 | black    |     40 | inch    |     101.6
- sl8       |        1 | brown    |     40 | inch    |     101.6
- sl5       |        4 | brown    |      1 | m       |       100
- sl6       |        0 | brown    |    0.9 | m       |        90
-(8 rows)
-</programlisting>
-   </para>
-
-   <para>
-    This is the simplest <command>SELECT</command> you can do on our
-    views, so we take this opportunity to explain the basics of view
-    rules.  The <literal>SELECT * FROM shoelace</literal> was
-    interpreted by the parser and produced the query tree:
-
-<programlisting>
-SELECT shoelace.sl_name, shoelace.sl_avail,
-       shoelace.sl_color, shoelace.sl_len,
-       shoelace.sl_unit, shoelace.sl_len_cm
-  FROM shoelace shoelace;
-</programlisting>
-
-    and this is given to the rule system. The rule system walks through the
-    range table and checks if there are rules
-    for any relation. When processing the range table entry for
-    <literal>shoelace</literal> (the only one up to now) it finds the
-    <literal>_RETURN</literal> rule with the query tree:
-
-<programlisting>
-SELECT s.sl_name, s.sl_avail,
-       s.sl_color, s.sl_len, s.sl_unit,
-       s.sl_len * u.un_fact AS sl_len_cm
-  FROM shoelace old, shoelace new,
-       shoelace_data s, unit u
- WHERE s.sl_unit = u.un_name;
-</programlisting>
-</para>
-
-<para>
-    To expand the view, the rewriter simply creates a subquery range-table
-    entry containing the rule's action query tree, and substitutes this
-    range table entry for the original one that referenced the view.  The
-    resulting rewritten query tree is almost the same as if you had typed:
-
-<programlisting>
-SELECT shoelace.sl_name, shoelace.sl_avail,
-       shoelace.sl_color, shoelace.sl_len,
-       shoelace.sl_unit, shoelace.sl_len_cm
-  FROM (SELECT s.sl_name,
-               s.sl_avail,
-               s.sl_color,
-               s.sl_len,
-               s.sl_unit,
-               s.sl_len * u.un_fact AS sl_len_cm
-          FROM shoelace_data s, unit u
-         WHERE s.sl_unit = u.un_name) shoelace;
-</programlisting>
-
-     There is one difference however: the subquery's range table has two
-     extra entries <literal>shoelace old</> and <literal>shoelace new</>.  These entries don't
-     participate directly in the query, since they aren't referenced by
-     the subquery's join tree or target list.  The rewriter uses them
-     to store the access privilege check information that was originally present
-     in the range-table entry that referenced the view.  In this way, the
-     executor will still check that the user has proper privileges to access
-     the view, even though there's no direct use of the view in the rewritten
-     query.
-</para>
-
-<para>
-    That was the first rule applied.  The rule system will continue checking
-    the remaining range-table entries in the top query (in this example there
-    are no more), and it will recursively check the range-table entries in
-    the added subquery to see if any of them reference views.  (But it
-    won't expand <literal>old</> or <literal>new</> &mdash; otherwise we'd have infinite recursion!)
-    In this example, there are no rewrite rules for <literal>shoelace_data</> or <literal>unit</>,
-    so rewriting is complete and the above is the final result given to
-    the planner.
-</para>
-
-<para>
-    Now we want to write a query that finds out for which shoes currently in the store
-    we have the matching shoelaces (color and length) and where the
-    total number of exactly matching pairs is greater or equal to two.
-
-<programlisting>
-SELECT * FROM shoe_ready WHERE total_avail &gt;= 2;
-
- shoename | sh_avail | sl_name | sl_avail | total_avail
-----------+----------+---------+----------+-------------
- sh1      |        2 | sl1     |        5 |           2
- sh3      |        4 | sl7     |        7 |           4
-(2 rows)
-</programlisting>
-</para>
-
-<para>
-    The output of the parser this time is the query tree:
-
-<programlisting>
-SELECT shoe_ready.shoename, shoe_ready.sh_avail,
-       shoe_ready.sl_name, shoe_ready.sl_avail,
-       shoe_ready.total_avail
-  FROM shoe_ready shoe_ready
- WHERE shoe_ready.total_avail &gt;= 2;
-</programlisting>
-
-    The first rule applied will be the one for the
-    <literal>shoe_ready</literal> view and it results in the
-    query tree:
-
-<programlisting>
-SELECT shoe_ready.shoename, shoe_ready.sh_avail,
-       shoe_ready.sl_name, shoe_ready.sl_avail,
-       shoe_ready.total_avail
-  FROM (SELECT rsh.shoename,
-               rsh.sh_avail,
-               rsl.sl_name,
-               rsl.sl_avail,
-               min(rsh.sh_avail, rsl.sl_avail) AS total_avail
-          FROM shoe rsh, shoelace rsl
-         WHERE rsl.sl_color = rsh.slcolor
-           AND rsl.sl_len_cm &gt;= rsh.slminlen_cm
-           AND rsl.sl_len_cm &lt;= rsh.slmaxlen_cm) shoe_ready
- WHERE shoe_ready.total_avail &gt;= 2;
-</programlisting>
-
-    Similarly, the rules for <literal>shoe</literal> and
-    <literal>shoelace</literal> are substituted into the range table of
-    the subquery, leading to a three-level final query tree:
-
-<programlisting>
-SELECT shoe_ready.shoename, shoe_ready.sh_avail,
-       shoe_ready.sl_name, shoe_ready.sl_avail,
-       shoe_ready.total_avail
-  FROM (SELECT rsh.shoename,
-               rsh.sh_avail,
-               rsl.sl_name,
-               rsl.sl_avail,
-               min(rsh.sh_avail, rsl.sl_avail) AS total_avail
-          FROM (SELECT sh.shoename,
-                       sh.sh_avail,
-                       sh.slcolor,
-                       sh.slminlen,
-                       sh.slminlen * un.un_fact AS slminlen_cm,
-                       sh.slmaxlen,
-                       sh.slmaxlen * un.un_fact AS slmaxlen_cm,
-                       sh.slunit
-                  FROM shoe_data sh, unit un
-                 WHERE sh.slunit = un.un_name) rsh,
-               (SELECT s.sl_name,
-                       s.sl_avail,
-                       s.sl_color,
-                       s.sl_len,
-                       s.sl_unit,
-                       s.sl_len * u.un_fact AS sl_len_cm
-                  FROM shoelace_data s, unit u
-                 WHERE s.sl_unit = u.un_name) rsl
-         WHERE rsl.sl_color = rsh.slcolor
-           AND rsl.sl_len_cm &gt;= rsh.slminlen_cm
-           AND rsl.sl_len_cm &lt;= rsh.slmaxlen_cm) shoe_ready
- WHERE shoe_ready.total_avail &gt; 2;
-</programlisting>
-   </para>
-
-   <para>
-    It turns out that the planner will collapse this tree into a
-    two-level query tree: the bottommost <command>SELECT</command>
-    commands will be <quote>pulled up</quote> into the middle
-    <command>SELECT</command> since there's no need to process them
-    separately.  But the middle <command>SELECT</command> will remain
-    separate from the top, because it contains aggregate functions.
-    If we pulled those up it would change the behavior of the topmost
-    <command>SELECT</command>, which we don't want.  However,
-    collapsing the query tree is an optimization that the rewrite
-    system doesn't have to concern itself with.
-   </para>
-</sect2>
-
-<sect2>
-<title>View Rules in Non-<command>SELECT</command> Statements</title>
-
-<!## XC>
-&pgonly
-<para>
-     Non-<command>SELECT</command> statements in rules are not
-     supported by the current version
-     of <productname>Postgres-XC</productname>.
-</para>
-<!## end>
-<!## XL>
-&pgonly
-<para>
-     Non-<command>SELECT</command> statements in rules are not
-     supported by the current version
-     of <productname>Postgres-XL</productname>.
-</para>
-<!## end>
-
-<!## PG>
-<para>
-    Two details of the query tree aren't touched in the description of
-    view rules above. These are the command type and the result relation.
-    In fact, the command type is not needed by view rules, but the result
-    relation may affect the way in which the query rewriter works, because
-    special care needs to be taken if the result relation is a view.
-</para>
-
-<para>
-    There are only a few differences between a query tree for a
-    <command>SELECT</command> and one for any other
-    command. Obviously, they have a different command type and for a
-    command other than a <command>SELECT</command>, the result
-    relation points to the range-table entry where the result should
-    go.  Everything else is absolutely the same.  So having two tables
-    <literal>t1</> and <literal>t2</> with columns <literal>a</> and
-    <literal>b</>, the query trees for the two statements:
-
-<programlisting>
-SELECT t2.b FROM t1, t2 WHERE t1.a = t2.a;
-
-UPDATE t1 SET b = t2.b FROM t2 WHERE t1.a = t2.a;
-</programlisting>
-
-    are nearly identical.  In particular:
-
-    <itemizedlist>
-        <listitem>
-        <para>
-            The range tables contain entries for the tables <literal>t1</> and <literal>t2</>.
-        </para>
-        </listitem>
-
-        <listitem>
-        <para>
-            The target lists contain one variable that points to column
-            <literal>b</> of the range table entry for table <literal>t2</>.
-        </para>
-        </listitem>
-
-        <listitem>
-        <para>
-            The qualification expressions compare the columns <literal>a</> of both
-            range-table entries for equality.
-        </para>
-        </listitem>
-
-        <listitem>
-        <para>
-            The join trees show a simple join between <literal>t1</> and <literal>t2</>.
-        </para>
-        </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    The consequence is, that both query trees result in similar
-    execution plans: They are both joins over the two tables. For the
-    <command>UPDATE</command> the missing columns from <literal>t1</> are added to
-    the target list by the planner and the final query tree will read
-    as:
-
-<programlisting>
-UPDATE t1 SET a = t1.a, b = t2.b FROM t2 WHERE t1.a = t2.a;
-</programlisting>
-
-    and thus the executor run over the join will produce exactly the
-    same result set as:
-
-<programlisting>
-SELECT t1.a, t2.b FROM t1, t2 WHERE t1.a = t2.a;
-</programlisting>
-
-    But there is a little problem in
-    <command>UPDATE</command>: the part of the executor plan that does
-    the join does not care what the results from the join are
-    meant for. It just produces a result set of rows. The fact that
-    one is a <command>SELECT</command> command and the other is an
-    <command>UPDATE</command> is handled higher up in the executor, where
-    it knows that this is an <command>UPDATE</command>, and it knows that
-    this result should go into table <literal>t1</>. But which of the rows
-    that are there has to be replaced by the new row?
-</para>
-
-<para>
-    To resolve this problem, another entry is added to the target list
-    in <command>UPDATE</command> (and also in
-    <command>DELETE</command>) statements: the current tuple ID
-    (<acronym>CTID</>).<indexterm><primary>CTID</></>
-    This is a system column containing the
-    file block number and position in the block for the row. Knowing
-    the table, the <acronym>CTID</> can be used to retrieve the
-    original row of <literal>t1</> to be updated.  After adding the
-    <acronym>CTID</> to the target list, the query actually looks like:
-
-<programlisting>
-SELECT t1.a, t2.b, t1.ctid FROM t1, t2 WHERE t1.a = t2.a;
-</programlisting>
-
-    Now another detail of <productname>PostgreSQL</productname> enters
-    the stage. Old table rows aren't overwritten, and this
-    is why <command>ROLLBACK</command> is fast. In an <command>UPDATE</command>,
-    the new result row is inserted into the table (after stripping the
-    <acronym>CTID</>) and in the row header of the old row, which the
-    <acronym>CTID</> pointed to, the <literal>cmax</> and
-    <literal>xmax</> entries are set to the current command counter
-    and current transaction ID. Thus the old row is hidden, and after
-    the transaction commits the vacuum cleaner can eventually remove
-    the dead row.
-</para>
-
-<para>
-    Knowing all that, we can simply apply view rules in absolutely
-    the same way to any command. There is no difference.
-</para>
-
-<!## end>
-</sect2>
-
-<sect2>
-<title>The Power of Views in <productname>PostgreSQL</productname></title>
-
-&common;
-<para>
-    The above demonstrates how the rule system incorporates view
-    definitions into the original query tree. In the second example, a
-    simple <command>SELECT</command> from one view created a final
-    query tree that is a join of 4 tables (<literal>unit</> was used twice with
-    different names).
-</para>
-
-<para>
-    The benefit of implementing views with the rule system is,
-    that the planner has all
-    the information about which tables have to be scanned plus the
-    relationships between these tables plus the restrictive
-    qualifications from the views plus the qualifications from
-    the original query
-    in one single query tree. And this is still the situation
-    when the original query is already a join over views.
-    The planner has to decide which is
-    the best path to execute the query, and the more information
-    the planner has, the better this decision can be. And
-    the rule system as implemented in <productname>PostgreSQL</productname>
-    ensures, that this is all information available about the query
-    up to that point.
-</para>
-</sect2>
-
-<sect2 id="rules-views-update">
-<title>Updating a View</title>
-
-&common;
-<para>
-    What happens if a view is named as the target relation for an
-    <command>INSERT</command>, <command>UPDATE</command>, or
-    <command>DELETE</command>?  Simply doing the substitutions
-    described above would give a query tree in which the result
-    relation points at a subquery range-table entry, which will not
-    work.  Instead, the rewriter assumes that the operation will be
-    handled by an <literal>INSTEAD OF</> trigger on the view.
-    (If there is no such trigger, the executor will throw an error
-    when execution starts.)  Rewriting works slightly differently
-    in this case.  For <command>INSERT</command>, the rewriter does
-    nothing at all with the view, leaving it as the result relation
-    for the query.  For <command>UPDATE</command> and
-    <command>DELETE</command>, it's still necessary to expand the
-    view query to produce the <quote>old</> rows that the command will
-    attempt to update or delete.  So the view is expanded as normal,
-    but another unexpanded range-table entry is added to the query
-    to represent the view in its capacity as the result relation.
-</para>
-
-<para>
-    The problem that now arises is how to identify the rows to be
-    updated in the view. Recall that when the result relation
-    is a table, a special <acronym>CTID</> entry is added to the target
-    list to identify the physical locations of the rows to be updated.
-    This does not work if the result relation is a view, because a view
-    does not have any <acronym>CTID</>, since its rows do not have
-    actual physical locations. Instead, for an <command>UPDATE</command>
-    or <command>DELETE</command> operation, a special <literal>wholerow</>
-    entry is added to the target list, which expands to include all
-    columns from the view. The executor uses this value to supply the
-    <quote>old</> row to the <literal>INSTEAD OF</> trigger.  It is
-    up to the trigger to work out what to update based on the old and
-    new row values.
-</para>
-
-<para>
-    If there are no <literal>INSTEAD OF</> triggers to update the view,
-    the executor will throw an error, because it cannot automatically
-    update a view by itself. To change this, we can define rules that
-    modify the behavior of <command>INSERT</command>,
-    <command>UPDATE</command>, and <command>DELETE</command> commands on
-    a view. These rules will rewrite the command, typically into a command
-    that updates one or more tables, rather than views. That is the topic
-    of the next section.
-</para>
-
-<para>
-    Note that rules are evaluated first, rewriting the original query
-    before it is planned and executed. Therefore, if a view has
-    <literal>INSTEAD OF</> triggers as well as rules on <command>INSERT</>,
-    <command>UPDATE</>, or <command>DELETE</>, then the rules will be
-    evaluated first, and depending on the result, the triggers may not be
-    used at all.
-</para>
-</sect2>
-
-</sect1>
-
-<sect1 id="rules-update">
-<title>Rules on <command>INSERT</>, <command>UPDATE</>, and <command>DELETE</></title>
-
-<indexterm zone="rules-update">
- <primary>rule</primary>
- <secondary sortas="INSERT">for INSERT</secondary>
-</indexterm>
-
-<indexterm zone="rules-update">
- <primary>rule</primary>
- <secondary sortas="UPDATE">for UPDATE</secondary>
-</indexterm>
-
-<indexterm zone="rules-update">
- <primary>rule</primary>
- <secondary sortas="DELETE">for DELETE</secondary>
-</indexterm>
-
-&common;
-<para>
-    Rules that are defined on <command>INSERT</>, <command>UPDATE</>,
-    and <command>DELETE</> are significantly different from the view rules
-    described in the previous section. First, their <command>CREATE
-    RULE</command> command allows more:
-
-    <itemizedlist>
-        <listitem>
-        <para>
-            They are allowed to have no action.
-        </para>
-        </listitem>
-
-        <listitem>
-        <para>
-            They can have multiple actions.
-        </para>
-        </listitem>
-
-        <listitem>
-        <para>
-            They can be <literal>INSTEAD</> or <literal>ALSO</> (the default).
-        </para>
-        </listitem>
-
-        <listitem>
-        <para>
-            The pseudorelations <literal>NEW</> and <literal>OLD</> become useful.
-        </para>
-        </listitem>
-
-        <listitem>
-        <para>
-            They can have rule qualifications.
-        </para>
-        </listitem>
-    </itemizedlist>
-
-    Second, they don't modify the query tree in place. Instead they
-    create zero or more new query trees and can throw away the
-    original one.
-</para>
-
-<sect2>
-<title>How Update Rules Work</title>
-
-&common;
-<para>
-    Keep the syntax:
-
-<programlisting>
-CREATE [ OR REPLACE ] RULE <replaceable class="parameter">name</replaceable> AS ON <replaceable class="parameter">event</replaceable>
-    TO <replaceable class="parameter">table</replaceable> [ WHERE <replaceable class="parameter">condition</replaceable> ]
-    DO [ ALSO | INSTEAD ] { NOTHING | <replaceable class="parameter">command</replaceable> | ( <replaceable class="parameter">command</replaceable> ; <replaceable class="parameter">command</replaceable> ... ) }
-</programlisting>
-
-    in mind.
-    In the following, <firstterm>update rules</> means rules that are defined
-    on <command>INSERT</>, <command>UPDATE</>, or <command>DELETE</>.
-</para>
-
-<para>
-    Update rules get applied by the rule system when the result
-    relation and the command type of a query tree are equal to the
-    object and event given in the <command>CREATE RULE</command> command.
-    For update rules, the rule system creates a list of query trees.
-    Initially the query-tree list is empty.
-    There can be zero (<literal>NOTHING</> key word), one, or multiple actions.
-    To simplify, we will look at a rule with one action. This rule
-    can have a qualification or not and it can be <literal>INSTEAD</> or
-    <literal>ALSO</> (the default).
-</para>
-
-<para>
-    What is a rule qualification? It is a restriction that tells
-    when the actions of the rule should be done and when not. This
-    qualification can only reference the pseudorelations <literal>NEW</> and/or <literal>OLD</>,
-    which basically represent the relation that was given as object (but with a
-    special meaning).
-</para>
-
-   <para>
-    So we have three cases that produce the following query trees for
-    a one-action rule.
-
-    <variablelist>
-     <varlistentry>
-      <term>No qualification, with either <literal>ALSO</> or
-      <literal>INSTEAD</></term>
-      <listitem>
-       <para>
-        the query tree from the rule action with the original query
-        tree's qualification added
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Qualification given and <literal>ALSO</></term>
-      <listitem>
-       <para>
-        the query tree from the rule action with the rule
-        qualification and the original query tree's qualification
-        added
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Qualification given and <literal>INSTEAD</></term>
-      <listitem>
-       <para>
-        the query tree from the rule action with the rule
-        qualification and the original query tree's qualification; and
-        the original query tree with the negated rule qualification
-        added
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    Finally, if the rule is <literal>ALSO</>, the unchanged original query tree is
-    added to the list. Since only qualified <literal>INSTEAD</> rules already add the
-    original query tree, we end up with either one or two output query trees
-    for a rule with one action.
-</para>
-
-<para>
-    For <literal>ON INSERT</> rules, the original query (if not suppressed by <literal>INSTEAD</>)
-    is done before any actions added by rules.  This allows the actions to
-    see the inserted row(s).  But for <literal>ON UPDATE</> and <literal>ON
-    DELETE</> rules, the original query is done after the actions added by rules.
-    This ensures that the actions can see the to-be-updated or to-be-deleted
-    rows; otherwise, the actions might do nothing because they find no rows
-    matching their qualifications.
-</para>
-
-<para>
-    The query trees generated from rule actions are thrown into the
-    rewrite system again, and maybe more rules get applied resulting
-    in more or less query trees.
-    So a rule's actions must have either a different
-    command type or a different result relation than the rule itself is
-    on, otherwise this recursive process will end up in an infinite loop.
-    (Recursive expansion of a rule will be detected and reported as an
-    error.)
-</para>
-
-<para>
-    The query trees found in the actions of the
-    <structname>pg_rewrite</structname> system catalog are only
-    templates. Since they can reference the range-table entries for
-    <literal>NEW</> and <literal>OLD</>, some substitutions have to be made before they can be
-    used. For any reference to <literal>NEW</>, the target list of the original
-    query is searched for a corresponding entry. If found, that
-    entry's expression replaces the reference. Otherwise, <literal>NEW</> means the
-    same as <literal>OLD</> (for an <command>UPDATE</command>) or is replaced by
-    a null value (for an <command>INSERT</command>). Any reference to <literal>OLD</> is
-    replaced by a reference to the range-table entry that is the
-    result relation.
-</para>
-
-<para>
-    After the system is done applying update rules, it applies view rules to the
-    produced query tree(s).  Views cannot insert new update actions so
-    there is no need to apply update rules to the output of view rewriting.
-</para>
-
-<sect3>
-<title>A First Rule Step by Step</title>
-
-&common;
-<para>
-    Say we want to trace changes to the <literal>sl_avail</> column in the
-    <literal>shoelace_data</literal> relation. So we set up a log table
-    and a rule that conditionally writes a log entry when an
-    <command>UPDATE</command> is performed on
-    <literal>shoelace_data</literal>.
-
-<programlisting>
-CREATE TABLE shoelace_log (
-    sl_name    text,          -- shoelace changed
-    sl_avail   integer,       -- new available value
-    log_who    text,          -- who did it
-    log_when   timestamp      -- when
-);
-
-CREATE RULE log_shoelace AS ON UPDATE TO shoelace_data
-    WHERE NEW.sl_avail &lt;&gt; OLD.sl_avail
-    DO INSERT INTO shoelace_log VALUES (
-                                    NEW.sl_name,
-                                    NEW.sl_avail,
-                                    current_user,
-                                    current_timestamp
-                                );
-</programlisting>
-</para>
-
-<para>
-    Now someone does:
-
-<programlisting>
-UPDATE shoelace_data SET sl_avail = 6 WHERE sl_name = 'sl7';
-</programlisting>
-
-    and we look at the log table:
-
-<programlisting>
-SELECT * FROM shoelace_log;
-
- sl_name | sl_avail | log_who | log_when                        
----------+----------+---------+----------------------------------
- sl7     |        6 | Al      | Tue Oct 20 16:14:45 1998 MET DST
-(1 row)
-</programlisting>
-   </para>
-
-   <para>
-    That's what we expected. What happened in the background is the following.
-    The parser created the query tree:
-
-<programlisting>
-UPDATE shoelace_data SET sl_avail = 6
-  FROM shoelace_data shoelace_data
- WHERE shoelace_data.sl_name = 'sl7';
-</programlisting>
-
-    There is a rule <literal>log_shoelace</literal> that is <literal>ON UPDATE</> with the rule
-    qualification expression:
-
-<programlisting>
-NEW.sl_avail &lt;&gt; OLD.sl_avail
-</programlisting>
-
-    and the action:
-
-<programlisting>
-INSERT INTO shoelace_log VALUES (
-       new.sl_name, new.sl_avail,
-       current_user, current_timestamp )
-  FROM shoelace_data new, shoelace_data old;
-</programlisting>
-
-    (This looks a little strange since you cannot normally write
-    <literal>INSERT ... VALUES ... FROM</>.  The <literal>FROM</>
-    clause here is just to indicate that there are range-table entries
-    in the query tree for <literal>new</> and <literal>old</>.
-    These are needed so that they can be referenced by variables in
-    the <command>INSERT</command> command's query tree.)
-</para>
-
-<para>
-    The rule is a qualified <literal>ALSO</> rule, so the rule system
-    has to return two query trees: the modified rule action and the original
-    query tree. In step 1, the range table of the original query is
-    incorporated into the rule's action query tree. This results in:
-
-<programlisting>
-INSERT INTO shoelace_log VALUES (
-       new.sl_name, new.sl_avail,
-       current_user, current_timestamp )
-  FROM shoelace_data new, shoelace_data old,
-       <emphasis>shoelace_data shoelace_data</emphasis>;
-</programlisting>
-
-    In step 2, the rule qualification is added to it, so the result set
-    is restricted to rows where <literal>sl_avail</> changes:
-
-<programlisting>
-INSERT INTO shoelace_log VALUES (
-       new.sl_name, new.sl_avail,
-       current_user, current_timestamp )
-  FROM shoelace_data new, shoelace_data old,
-       shoelace_data shoelace_data
- <emphasis>WHERE new.sl_avail &lt;&gt; old.sl_avail</emphasis>;
-</programlisting>
-
-    (This looks even stranger, since <literal>INSERT ... VALUES</> doesn't have
-    a <literal>WHERE</> clause either, but the planner and executor will have no
-    difficulty with it.  They need to support this same functionality
-    anyway for <literal>INSERT ... SELECT</>.)
-   </para>
-
-   <para>
-    In step 3, the original query tree's qualification is added,
-    restricting the result set further to only the rows that would have been touched
-    by the original query:
-
-<programlisting>
-INSERT INTO shoelace_log VALUES (
-       new.sl_name, new.sl_avail,
-       current_user, current_timestamp )
-  FROM shoelace_data new, shoelace_data old,
-       shoelace_data shoelace_data
- WHERE new.sl_avail &lt;&gt; old.sl_avail
-   <emphasis>AND shoelace_data.sl_name = 'sl7'</emphasis>;
-</programlisting>
-   </para>
-
-   <para>
-    Step 4 replaces references to <literal>NEW</> by the target list entries from the
-    original query tree or by the matching variable references
-    from the result relation:
-
-<programlisting>
-INSERT INTO shoelace_log VALUES (
-       <emphasis>shoelace_data.sl_name</emphasis>, <emphasis>6</emphasis>,
-       current_user, current_timestamp )
-  FROM shoelace_data new, shoelace_data old,
-       shoelace_data shoelace_data
- WHERE <emphasis>6</emphasis> &lt;&gt; old.sl_avail
-   AND shoelace_data.sl_name = 'sl7';
-</programlisting>
-
-   </para>
-
-   <para>
-    Step 5 changes <literal>OLD</> references into result relation references:
-
-<programlisting>
-INSERT INTO shoelace_log VALUES (
-       shoelace_data.sl_name, 6,
-       current_user, current_timestamp )
-  FROM shoelace_data new, shoelace_data old,
-       shoelace_data shoelace_data
- WHERE 6 &lt;&gt; <emphasis>shoelace_data.sl_avail</emphasis>
-   AND shoelace_data.sl_name = 'sl7';
-</programlisting>
-   </para>
-
-   <para>
-    That's it.  Since the rule is <literal>ALSO</>, we also output the
-    original query tree.  In short, the output from the rule system
-    is a list of two query trees that correspond to these statements:
-
-<programlisting>
-INSERT INTO shoelace_log VALUES (
-       shoelace_data.sl_name, 6,
-       current_user, current_timestamp )
-  FROM shoelace_data
- WHERE 6 &lt;&gt; shoelace_data.sl_avail
-   AND shoelace_data.sl_name = 'sl7';
-
-UPDATE shoelace_data SET sl_avail = 6
- WHERE sl_name = 'sl7';
-</programlisting>
-
-    These are executed in this order, and that is exactly what
-    the rule was meant to do.
-   </para>
-
-   <para>
-    The substitutions and the added qualifications
-    ensure that, if the original query would be, say:
-
-<programlisting>
-UPDATE shoelace_data SET sl_color = 'green'
- WHERE sl_name = 'sl7';
-</programlisting>
-
-    no log entry would get written.  In that case, the original query
-    tree does not contain a target list entry for
-    <literal>sl_avail</>, so <literal>NEW.sl_avail</> will get
-    replaced by <literal>shoelace_data.sl_avail</>.  Thus, the extra
-    command generated by the rule is:
-
-<programlisting>
-INSERT INTO shoelace_log VALUES (
-       shoelace_data.sl_name, <emphasis>shoelace_data.sl_avail</emphasis>,
-       current_user, current_timestamp )
-  FROM shoelace_data
- WHERE <emphasis>shoelace_data.sl_avail</emphasis> &lt;&gt; shoelace_data.sl_avail
-   AND shoelace_data.sl_name = 'sl7';
-</programlisting>
-
-    and that qualification will never be true.
-   </para>
-
-   <para>
-    It will also work if the original query modifies multiple rows. So
-    if someone issued the command:
-
-<programlisting>
-UPDATE shoelace_data SET sl_avail = 0
- WHERE sl_color = 'black';
-</programlisting>
-
-    four rows in fact get updated (<literal>sl1</>, <literal>sl2</>, <literal>sl3</>, and <literal>sl4</>).
-    But <literal>sl3</> already has <literal>sl_avail = 0</>.   In this case, the original
-    query trees qualification is different and that results
-    in the extra query tree:
-
-<programlisting>
-INSERT INTO shoelace_log
-SELECT shoelace_data.sl_name, 0,
-       current_user, current_timestamp
-  FROM shoelace_data
- WHERE 0 &lt;&gt; shoelace_data.sl_avail
-   AND <emphasis>shoelace_data.sl_color = 'black'</emphasis>;
-</programlisting>
-
-    being generated by the rule.  This query tree will surely insert
-    three new log entries. And that's absolutely correct.
-</para>
-
-<para>
-    Here we can see why it is important that the original query tree
-    is executed last.  If the <command>UPDATE</command> had been
-    executed first, all the rows would have already been set to zero, so the
-    logging <command>INSERT</command> would not find any row where
-    <literal>0 &lt;&gt; shoelace_data.sl_avail</literal>.
-</para>
-</sect3>
-
-</sect2>
-
-<sect2 id="rules-update-views">
-<title>Cooperation with Views</title>
-
-<indexterm zone="rules-update-views"><primary>view</><secondary>updating</></>
-
-&common;
-<para>
-    A simple way to protect view relations from the mentioned
-    possibility that someone can try to run <command>INSERT</command>,
-    <command>UPDATE</command>, or <command>DELETE</command> on them is
-    to let those query trees get thrown away.  So we could create the rules:
-
-<programlisting>
-CREATE RULE shoe_ins_protect AS ON INSERT TO shoe
-    DO INSTEAD NOTHING;
-CREATE RULE shoe_upd_protect AS ON UPDATE TO shoe
-    DO INSTEAD NOTHING;
-CREATE RULE shoe_del_protect AS ON DELETE TO shoe
-    DO INSTEAD NOTHING;
-</programlisting>
-
-    If someone now tries to do any of these operations on the view
-    relation <literal>shoe</literal>, the rule system will
-    apply these rules. Since the rules have
-    no actions and are <literal>INSTEAD</>, the resulting list of
-    query trees will be empty and the whole query will become
-    nothing because there is nothing left to be optimized or
-    executed after the rule system is done with it.
-</para>
-
-<para>
-    A more sophisticated way to use the rule system is to
-    create rules that rewrite the query tree into one that
-    does the right operation on the real tables. To do that
-    on the <literal>shoelace</literal> view, we create
-    the following rules:
-
-<programlisting>
-CREATE RULE shoelace_ins AS ON INSERT TO shoelace
-    DO INSTEAD
-    INSERT INTO shoelace_data VALUES (
-           NEW.sl_name,
-           NEW.sl_avail,
-           NEW.sl_color,
-           NEW.sl_len,
-           NEW.sl_unit
-    );
-
-CREATE RULE shoelace_upd AS ON UPDATE TO shoelace
-    DO INSTEAD
-    UPDATE shoelace_data
-       SET sl_name = NEW.sl_name,
-           sl_avail = NEW.sl_avail,
-           sl_color = NEW.sl_color,
-           sl_len = NEW.sl_len,
-           sl_unit = NEW.sl_unit
-     WHERE sl_name = OLD.sl_name;
-
-CREATE RULE shoelace_del AS ON DELETE TO shoelace
-    DO INSTEAD
-    DELETE FROM shoelace_data
-     WHERE sl_name = OLD.sl_name;
-</programlisting>
-   </para>
-
-   <para>
-    If you want to support <literal>RETURNING</> queries on the view,
-    you need to make the rules include <literal>RETURNING</> clauses that
-    compute the view rows.  This is usually pretty trivial for views on a
-    single table, but it's a bit tedious for join views such as
-    <literal>shoelace</literal>.  An example for the insert case is:
-
-<programlisting>
-CREATE RULE shoelace_ins AS ON INSERT TO shoelace
-    DO INSTEAD
-    INSERT INTO shoelace_data VALUES (
-           NEW.sl_name,
-           NEW.sl_avail,
-           NEW.sl_color,
-           NEW.sl_len,
-           NEW.sl_unit
-    )
-    RETURNING
-           shoelace_data.*,
-           (SELECT shoelace_data.sl_len * u.un_fact
-            FROM unit u WHERE shoelace_data.sl_unit = u.un_name);
-</programlisting>
-
-    Note that this one rule supports both <command>INSERT</> and
-    <command>INSERT RETURNING</> queries on the view &mdash; the
-    <literal>RETURNING</> clause is simply ignored for <command>INSERT</>.
-   </para>
-
-   <para>
-    Now assume that once in a while, a pack of shoelaces arrives at
-    the shop and a big parts list along with it.  But you don't want
-    to manually update the <literal>shoelace</literal> view every
-    time.  Instead we setup two little tables: one where you can
-    insert the items from the part list, and one with a special
-    trick. The creation commands for these are:
-
-<programlisting>
-CREATE TABLE shoelace_arrive (
-    arr_name    text,
-    arr_quant   integer
-);
-
-CREATE TABLE shoelace_ok (
-    ok_name     text,
-    ok_quant    integer
-);
-
-CREATE RULE shoelace_ok_ins AS ON INSERT TO shoelace_ok
-    DO INSTEAD
-    UPDATE shoelace
-       SET sl_avail = sl_avail + NEW.ok_quant
-     WHERE sl_name = NEW.ok_name;
-</programlisting>
-
-    Now you can fill the table <literal>shoelace_arrive</literal> with
-    the data from the parts list:
-
-<programlisting>
-SELECT * FROM shoelace_arrive;
-
- arr_name | arr_quant
-----------+-----------
- sl3      |        10
- sl6      |        20
- sl8      |        20
-(3 rows)
-</programlisting>
-
-    Take a quick look at the current data:
-
-<programlisting>
-SELECT * FROM shoelace;
-
- sl_name  | sl_avail | sl_color | sl_len | sl_unit | sl_len_cm
-----------+----------+----------+--------+---------+-----------
- sl1      |        5 | black    |     80 | cm      |        80
- sl2      |        6 | black    |    100 | cm      |       100
- sl7      |        6 | brown    |     60 | cm      |        60
- sl3      |        0 | black    |     35 | inch    |      88.9
- sl4      |        8 | black    |     40 | inch    |     101.6
- sl8      |        1 | brown    |     40 | inch    |     101.6
- sl5      |        4 | brown    |      1 | m       |       100
- sl6      |        0 | brown    |    0.9 | m       |        90
-(8 rows)
-</programlisting>
-
-    Now move the arrived shoelaces in:
-
-<programlisting>
-INSERT INTO shoelace_ok SELECT * FROM shoelace_arrive;
-</programlisting>
-
-    and check the results:
-
-<programlisting>
-SELECT * FROM shoelace ORDER BY sl_name;
-
- sl_name  | sl_avail | sl_color | sl_len | sl_unit | sl_len_cm
-----------+----------+----------+--------+---------+-----------
- sl1      |        5 | black    |     80 | cm      |        80
- sl2      |        6 | black    |    100 | cm      |       100
- sl7      |        6 | brown    |     60 | cm      |        60
- sl4      |        8 | black    |     40 | inch    |     101.6
- sl3      |       10 | black    |     35 | inch    |      88.9
- sl8      |       21 | brown    |     40 | inch    |     101.6
- sl5      |        4 | brown    |      1 | m       |       100
- sl6      |       20 | brown    |    0.9 | m       |        90
-(8 rows)
-
-SELECT * FROM shoelace_log;
-
- sl_name | sl_avail | log_who| log_when                        
----------+----------+--------+----------------------------------
- sl7     |        6 | Al     | Tue Oct 20 19:14:45 1998 MET DST
- sl3     |       10 | Al     | Tue Oct 20 19:25:16 1998 MET DST
- sl6     |       20 | Al     | Tue Oct 20 19:25:16 1998 MET DST
- sl8     |       21 | Al     | Tue Oct 20 19:25:16 1998 MET DST
-(4 rows)
-</programlisting>
-   </para>
-
-   <para>
-    It's a long way from the one <literal>INSERT ... SELECT</literal>
-    to these results. And the description of the query-tree
-    transformation will be the last in this chapter.  First, there is
-    the parser's output:
-
-<programlisting>
-INSERT INTO shoelace_ok
-SELECT shoelace_arrive.arr_name, shoelace_arrive.arr_quant
-  FROM shoelace_arrive shoelace_arrive, shoelace_ok shoelace_ok;
-</programlisting>
-
-    Now the first rule <literal>shoelace_ok_ins</literal> is applied and turns this
-    into:
-
-<programlisting>
-UPDATE shoelace
-   SET sl_avail = shoelace.sl_avail + shoelace_arrive.arr_quant
-  FROM shoelace_arrive shoelace_arrive, shoelace_ok shoelace_ok,
-       shoelace_ok old, shoelace_ok new,
-       shoelace shoelace
- WHERE shoelace.sl_name = shoelace_arrive.arr_name;
-</programlisting>
-
-    and throws away the original <command>INSERT</command> on
-    <literal>shoelace_ok</literal>.  This rewritten query is passed to
-    the rule system again, and the second applied rule
-    <literal>shoelace_upd</literal> produces:
-
-<programlisting>
-UPDATE shoelace_data
-   SET sl_name = shoelace.sl_name,
-       sl_avail = shoelace.sl_avail + shoelace_arrive.arr_quant,
-       sl_color = shoelace.sl_color,
-       sl_len = shoelace.sl_len,
-       sl_unit = shoelace.sl_unit
-  FROM shoelace_arrive shoelace_arrive, shoelace_ok shoelace_ok,
-       shoelace_ok old, shoelace_ok new,
-       shoelace shoelace, shoelace old,
-       shoelace new, shoelace_data shoelace_data
- WHERE shoelace.sl_name = shoelace_arrive.arr_name
-   AND shoelace_data.sl_name = shoelace.sl_name;
-</programlisting>
-
-    Again it's an <literal>INSTEAD</> rule and the previous query tree is trashed.
-    Note that this query still uses the view <literal>shoelace</literal>.
-    But the rule system isn't finished with this step, so it continues
-    and applies the <literal>_RETURN</literal> rule on it, and we get:
-
-<programlisting>
-UPDATE shoelace_data
-   SET sl_name = s.sl_name,
-       sl_avail = s.sl_avail + shoelace_arrive.arr_quant,
-       sl_color = s.sl_color,
-       sl_len = s.sl_len,
-       sl_unit = s.sl_unit
-  FROM shoelace_arrive shoelace_arrive, shoelace_ok shoelace_ok,
-       shoelace_ok old, shoelace_ok new,
-       shoelace shoelace, shoelace old,
-       shoelace new, shoelace_data shoelace_data,
-       shoelace old, shoelace new,
-       shoelace_data s, unit u
- WHERE s.sl_name = shoelace_arrive.arr_name
-   AND shoelace_data.sl_name = s.sl_name;
-</programlisting>
-
-    Finally, the rule <literal>log_shoelace</literal> gets applied,
-    producing the extra query tree:
-
-<programlisting>
-INSERT INTO shoelace_log
-SELECT s.sl_name,
-       s.sl_avail + shoelace_arrive.arr_quant,
-       current_user,
-       current_timestamp
-  FROM shoelace_arrive shoelace_arrive, shoelace_ok shoelace_ok,
-       shoelace_ok old, shoelace_ok new,
-       shoelace shoelace, shoelace old,
-       shoelace new, shoelace_data shoelace_data,
-       shoelace old, shoelace new,
-       shoelace_data s, unit u,
-       shoelace_data old, shoelace_data new
-       shoelace_log shoelace_log
- WHERE s.sl_name = shoelace_arrive.arr_name
-   AND shoelace_data.sl_name = s.sl_name
-   AND (s.sl_avail + shoelace_arrive.arr_quant) &lt;&gt; s.sl_avail;
-</programlisting>
-
-    After that the rule system runs out of rules and returns the
-    generated query trees.
-   </para>
-
-   <para>
-    So we end up with two final query trees that are equivalent to the
-    <acronym>SQL</acronym> statements:
-
-<programlisting>
-INSERT INTO shoelace_log
-SELECT s.sl_name,
-       s.sl_avail + shoelace_arrive.arr_quant,
-       current_user,
-       current_timestamp
-  FROM shoelace_arrive shoelace_arrive, shoelace_data shoelace_data,
-       shoelace_data s
- WHERE s.sl_name = shoelace_arrive.arr_name
-   AND shoelace_data.sl_name = s.sl_name
-   AND s.sl_avail + shoelace_arrive.arr_quant &lt;&gt; s.sl_avail;
-
-UPDATE shoelace_data
-   SET sl_avail = shoelace_data.sl_avail + shoelace_arrive.arr_quant
-  FROM shoelace_arrive shoelace_arrive,
-       shoelace_data shoelace_data,
-       shoelace_data s
- WHERE s.sl_name = shoelace_arrive.sl_name
-   AND shoelace_data.sl_name = s.sl_name;
-</programlisting>
-
-    The result is that data coming from one relation inserted into another,
-    changed into updates on a third, changed into updating
-    a fourth plus logging that final update in a fifth
-    gets reduced into two queries.
-</para>
-
-<para>
-    There is a little detail that's a bit ugly. Looking at the two
-    queries, it turns out that the <literal>shoelace_data</literal>
-    relation appears twice in the range table where it could
-    definitely be reduced to one. The planner does not handle it and
-    so the execution plan for the rule systems output of the
-    <command>INSERT</command> will be
-
-<literallayout class="monospaced">
-Nested Loop
-  -&gt;  Merge Join
-        -&gt;  Seq Scan
-              -&gt;  Sort
-                    -&gt;  Seq Scan on s
-        -&gt;  Seq Scan
-              -&gt;  Sort
-                    -&gt;  Seq Scan on shoelace_arrive
-  -&gt;  Seq Scan on shoelace_data
-</literallayout>
-
-    while omitting the extra range table entry would result in a
-
-<literallayout class="monospaced">
-Merge Join
-  -&gt;  Seq Scan
-        -&gt;  Sort
-              -&gt;  Seq Scan on s
-  -&gt;  Seq Scan
-        -&gt;  Sort
-              -&gt;  Seq Scan on shoelace_arrive
-</literallayout>
-
-    which produces exactly the same entries in the log table.  Thus,
-    the rule system caused one extra scan on the table
-    <literal>shoelace_data</literal> that is absolutely not
-    necessary. And the same redundant scan is done once more in the
-    <command>UPDATE</command>. But it was a really hard job to make
-    that all possible at all.
-</para>
-
-<para>
-    Now we make a final demonstration of the
-    <productname>PostgreSQL</productname> rule system and its power.
-    Say you add some shoelaces with extraordinary colors to your
-    database:
-
-<programlisting>
-INSERT INTO shoelace VALUES ('sl9', 0, 'pink', 35.0, 'inch', 0.0);
-INSERT INTO shoelace VALUES ('sl10', 1000, 'magenta', 40.0, 'inch', 0.0);
-</programlisting>
-
-    We would like to make a view to check which
-    <literal>shoelace</literal> entries do not fit any shoe in color.
-    The view for this is:
-
-<programlisting>
-CREATE VIEW shoelace_mismatch AS
-    SELECT * FROM shoelace WHERE NOT EXISTS
-        (SELECT shoename FROM shoe WHERE slcolor = sl_color);
-</programlisting>
-
-    Its output is:
-
-<programlisting>
-SELECT * FROM shoelace_mismatch;
-
- sl_name | sl_avail | sl_color | sl_len | sl_unit | sl_len_cm
----------+----------+----------+--------+---------+-----------
- sl9     |        0 | pink     |     35 | inch    |      88.9
- sl10    |     1000 | magenta  |     40 | inch    |     101.6
-</programlisting>
-   </para>
-
-   <para>
-    Now we want to set it up so that mismatching shoelaces that are
-    not in stock are deleted from the database.
-    To make it a little harder for <productname>PostgreSQL</productname>,
-    we don't delete it directly. Instead we create one more view:
-
-<programlisting>
-CREATE VIEW shoelace_can_delete AS
-    SELECT * FROM shoelace_mismatch WHERE sl_avail = 0;
-</programlisting>
-
-    and do it this way:
-
-<programlisting>
-DELETE FROM shoelace WHERE EXISTS
-    (SELECT * FROM shoelace_can_delete
-             WHERE sl_name = shoelace.sl_name);
-</programlisting>
-
-    <foreignphrase>Voil&agrave;</foreignphrase>:
-
-<programlisting>
-SELECT * FROM shoelace;
-
- sl_name | sl_avail | sl_color | sl_len | sl_unit | sl_len_cm
----------+----------+----------+--------+---------+-----------
- sl1     |        5 | black    |     80 | cm      |        80
- sl2     |        6 | black    |    100 | cm      |       100
- sl7     |        6 | brown    |     60 | cm      |        60
- sl4     |        8 | black    |     40 | inch    |     101.6
- sl3     |       10 | black    |     35 | inch    |      88.9
- sl8     |       21 | brown    |     40 | inch    |     101.6
- sl10    |     1000 | magenta  |     40 | inch    |     101.6
- sl5     |        4 | brown    |      1 | m       |       100
- sl6     |       20 | brown    |    0.9 | m       |        90
-(9 rows)
-</programlisting>
-   </para>
-
-   <para>
-    A <command>DELETE</command> on a view, with a subquery qualification that
-    in total uses 4 nesting/joined views, where one of them
-    itself has a subquery qualification containing a view
-    and where calculated view columns are used,
-    gets rewritten into
-    one single query tree that deletes the requested data
-    from a real table.
-</para>
-
-<para>
-    There are probably only a few situations out in the real world
-    where such a construct is necessary. But it makes you feel
-    comfortable that it works.
-</para>
-</sect2>
-
-</sect1>
-
-<sect1 id="rules-privileges">
-<title>Rules and Privileges</title>
-
-<indexterm zone="rules-privileges">
- <primary>privilege</primary>
- <secondary sortas="Regeln">with rules</secondary>
-</indexterm>
-
-<indexterm zone="rules-privileges">
- <primary>privilege</primary>
- <secondary sortas="Sichten">with views</secondary>
-</indexterm>
-
-&common;
-<para>
-    Due to rewriting of queries by the <productname>PostgreSQL</productname>
-    rule system, other tables/views than those used in the original
-    query get accessed. When update rules are used, this can include write access
-    to tables.
-</para>
-
-<para>
-    Rewrite rules don't have a separate owner. The owner of
-    a relation (table or view) is automatically the owner of the
-    rewrite rules that are defined for it.
-    The <productname>PostgreSQL</productname> rule system changes the
-    behavior of the default access control system. Relations that
-    are used due to rules get checked against the
-    privileges of the rule owner, not the user invoking the rule.
-    This means that a user only needs the required privileges
-    for the tables/views that he names explicitly in his queries.
-</para>
-
-<para>
-    For example: A user has a list of phone numbers where some of
-    them are private, the others are of interest for the secretary of the office.
-    He can construct the following:
-
-<programlisting>
-CREATE TABLE phone_data (person text, phone text, private boolean);
-CREATE VIEW phone_number AS
-    SELECT person, CASE WHEN NOT private THEN phone END AS phone
-    FROM phone_data;
-GRANT SELECT ON phone_number TO secretary;
-</programlisting>
-
-    Nobody except him (and the database superusers) can access the
-    <literal>phone_data</> table. But because of the <command>GRANT</>,
-    the secretary can run a <command>SELECT</command> on the
-    <literal>phone_number</> view. The rule system will rewrite the
-    <command>SELECT</command> from <literal>phone_number</> into a
-    <command>SELECT</command> from <literal>phone_data</>.
-    Since the user is the owner of
-    <literal>phone_number</> and therefore the owner of the rule, the
-    read access to <literal>phone_data</> is now checked against his
-    privileges and the query is permitted. The check for accessing
-    <literal>phone_number</> is also performed, but this is done
-    against the invoking user, so nobody but the user and the
-    secretary can use it.
-</para>
-
-<para>
-    The privileges are checked rule by rule. So the secretary is for now the
-    only one who can see the public phone numbers. But the secretary can setup
-    another view and grant access to that to the public. Then, anyone
-    can see the <literal>phone_number</> data through the secretary's view.
-    What the secretary cannot do is to create a view that directly
-    accesses <literal>phone_data</>.  (Actually he can, but it will not work since
-    every access will be denied during the permission checks.)
-    And as soon as the user will notice, that the secretary opened
-    his <literal>phone_number</> view, he can revoke his access. Immediately, any
-    access to the secretary's view would fail.
-</para>
-
-<para>
-    One might think that this rule-by-rule checking is a security
-    hole, but in fact it isn't.   But if it did not work this way, the secretary
-    could set up a table with the same columns as <literal>phone_number</> and
-    copy the data to there once per day. Then it's his own data and
-    he can grant access to everyone he wants. A
-    <command>GRANT</command> command means, <quote>I trust you</quote>.
-    If someone you trust does the thing above, it's time to
-    think it over and then use <command>REVOKE</command>.
-</para>
-
-<para>
-    Note that while views can be used to hide the contents of certain
-    columns using the technique shown above, they cannot be used to reliably
-    conceal the data in unseen rows.  For example, the following view is
-    insecure:
-<programlisting>
-CREATE VIEW phone_number AS
-    SELECT person, phone FROM phone_data WHERE phone NOT LIKE '412%';
-</programlisting>
-    This view might seem secure, since the rule system will rewrite any
-    <command>SELECT</command> from <literal>phone_number</> into a
-    <command>SELECT</command> from <literal>phone_data</> and add the
-    qualification that only entries where <literal>phone</> does not begin
-    with 412 are wanted.  But if the user can create his or her own functions,
-    it is not difficult to convince the planner to execute the user-defined
-    function prior to the <function>NOT LIKE</function> expression.
-    For example:
-<programlisting>
-CREATE FUNCTION tricky(text, text) RETURNS bool AS $$
-BEGIN
-    RAISE NOTICE '% => %', $1, $2;
-    RETURN true;
-END
-$$ LANGUAGE plpgsql COST 0.0000000000000000000001;
-
-SELECT * FROM phone_number WHERE tricky(person, phone);
-</programlisting>
-    Every person and phone number in the <literal>phone_data</> table will be
-    printed as a <literal>NOTICE</literal>, because the planner will choose to
-    execute the inexpensive <function>tricky</function> function before the
-    more expensive <function>NOT LIKE</function>.  Even if the user is
-    prevented from defining new functions, built-in functions can be used in
-    similar attacks.  (For example, most casting functions include their
-    input values in the error messages they produce.)
-</para>
-
-<para>
-    Similar considerations apply to update rules. In the examples of
-    the previous section, the owner of the tables in the example
-    database could grant the privileges <literal>SELECT</>,
-    <literal>INSERT</>, <literal>UPDATE</>, and <literal>DELETE</> on
-    the <literal>shoelace</> view to someone else, but only
-    <literal>SELECT</> on <literal>shoelace_log</>. The rule action to
-    write log entries will still be executed successfully, and that
-    other user could see the log entries.  But he cannot create fake
-    entries, nor could he manipulate or remove existing ones.  In this
-    case, there is no possibility of subverting the rules by convincing
-    the planner to alter the order of operations, because the only rule
-    which references <literal>shoelace_log</> is an unqualified
-    <literal>INSERT</>.  This might not be true in more complex scenarios.
-</para>
-</sect1>
-
-<sect1 id="rules-status">
-<title>Rules and Command Status</title>
-
-&common;
-<para>
-    The <productname>PostgreSQL</productname> server returns a command
-    status string, such as <literal>INSERT 149592 1</>, for each
-    command it receives.  This is simple enough when there are no rules
-    involved, but what happens when the query is rewritten by rules?
-</para>
-
-<para>
-    Rules affect the command status as follows:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       If there is no unconditional <literal>INSTEAD</> rule for the query, then
-       the originally given query will be executed, and its command
-       status will be returned as usual.  (But note that if there were
-       any conditional <literal>INSTEAD</> rules, the negation of their qualifications
-       will have been added to the original query.  This might reduce the
-       number of rows it processes, and if so the reported status will
-       be affected.)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If there is any unconditional <literal>INSTEAD</> rule for the query, then
-       the original query will not be executed at all.  In this case,
-       the server will return the command status for the last query
-       that was inserted by an <literal>INSTEAD</> rule (conditional or
-       unconditional) and is of the same command type
-       (<command>INSERT</command>, <command>UPDATE</command>, or
-       <command>DELETE</command>) as the original query.  If no query
-       meeting those requirements is added by any rule, then the
-       returned command status shows the original query type and
-       zeroes for the row-count and OID fields.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    (This system was established in <productname>PostgreSQL</> 7.3.
-    In versions before that, the command status might show different
-    results when rules exist.)
-</para>
-
-<para>
-    The programmer can ensure that any desired <literal>INSTEAD</> rule is the one
-    that sets the command status in the second case, by giving it the
-    alphabetically last rule name among the active rules, so that it
-    gets applied last.
-</para>
-</sect1>
-
-<sect1 id="rules-triggers">
-<title>Rules Versus Triggers</title>
-
-<indexterm zone="rules-triggers">
- <primary>rule</primary>
- <secondary sortas="Trigger">compared with triggers</secondary>
-</indexterm>
-
-<indexterm zone="rules-triggers">
- <primary>trigger</primary>
- <secondary sortas="Regeln">compared with rules</secondary>
-</indexterm>
-
-<!## XC>
-&xconly;
-<para>
-    Trigger is not supported by the current release
-    of <productname>Postgres-XC</>.  This may be supported in the
-    future releases.
-</para>
-<!## end>
-<!## XL>
-&xlonly;
-<para>
-    Trigger is not supported by the current release
-    of <productname>Postgres-XL</>.  This may be supported in the
-    future releases.
-</para>
-<!## end>
-
-<!## PG>
-<para>
-    Many things that can be done using triggers can also be
-    implemented using the <productname>PostgreSQL</productname>
-    rule system.  One of the things that cannot be implemented by
-    rules are some kinds of constraints, especially foreign keys. It is possible
-    to place a qualified rule that rewrites a command to <literal>NOTHING</>
-    if the value of a column does not appear in another table.
-    But then the data is silently thrown away and that's
-    not a good idea. If checks for valid values are required,
-    and in the case of an invalid value an error message should
-    be generated, it must be done by a trigger.
-</para>
-
-<para>
-    In this chapter, we focused on using rules to update views. All of
-    the update rule examples in this chapter can also be implemented
-    using <literal>INSTEAD OF</> triggers on the views.  Writing such
-    triggers is often easier than writing rules, particularly if complex
-    logic is required to perform the update.
-</para>
-
-<para>
-    For the things that can be implemented by both, which is best
-    depends on the usage of the database.
-    A trigger is fired once for each affected row. A rule modifies
-    the query or generates an additional query. So if many
-    rows are affected in one statement, a rule issuing one extra
-    command is likely to be faster than a trigger that is
-    called for every single row and must re-determine what to do
-    many times.  However, the trigger approach is conceptually far
-    simpler than the rule approach, and is easier for novices to get right.
-</para>
-
-<para>
-    Here we show an example of how the choice of rules versus triggers
-    plays out in one situation.  There are two tables:
-
-<programlisting>
-CREATE TABLE computer (
-    hostname        text,    -- indexed
-    manufacturer    text     -- indexed
-);
-
-CREATE TABLE software (
-    software        text,    -- indexed
-    hostname        text     -- indexed
-);
-</programlisting>
-
-    Both tables have many thousands of rows and the indexes on
-    <structfield>hostname</> are unique.  The rule or trigger should
-    implement a constraint that deletes rows from <literal>software</>
-    that reference a deleted computer.  The trigger would use this command:
-
-<programlisting>
-DELETE FROM software WHERE hostname = $1;
-</programlisting>
-
-    Since the trigger is called for each individual row deleted from
-    <literal>computer</>, it can prepare and save the plan for this
-    command and pass the <structfield>hostname</> value in the
-    parameter.  The rule would be written as:
-
-<programlisting>
-CREATE RULE computer_del AS ON DELETE TO computer
-    DO DELETE FROM software WHERE hostname = OLD.hostname;
-</programlisting>
-   </para>
-
-   <para>
-    Now we look at different types of deletes. In the case of a:
-
-<programlisting>
-DELETE FROM computer WHERE hostname = 'mypc.local.net';
-</programlisting>
-
-    the table <literal>computer</> is scanned by index (fast), and the
-    command issued by the trigger would also use an index scan (also fast).
-    The extra command from the rule would be:
-
-<programlisting>
-DELETE FROM software WHERE computer.hostname = 'mypc.local.net'
-                       AND software.hostname = computer.hostname;
-</programlisting>
-
-    Since there are appropriate indexes setup, the planner
-    will create a plan of
-
-<literallayout class="monospaced">
-Nestloop
-  -&gt;  Index Scan using comp_hostidx on computer
-  -&gt;  Index Scan using soft_hostidx on software
-</literallayout>
-
-    So there would be not that much difference in speed between
-    the trigger and the rule implementation.
-   </para>
-
-   <para>
-    With the next delete we want to get rid of all the 2000 computers
-    where the <structfield>hostname</> starts with
-    <literal>old</>. There are two possible commands to do that. One
-    is:
-
-<programlisting>
-DELETE FROM computer WHERE hostname &gt;= 'old'
-                       AND hostname &lt;  'ole'
-</programlisting>
-
-    The command added by the rule will be:
-
-<programlisting>
-DELETE FROM software WHERE computer.hostname &gt;= 'old' AND computer.hostname &lt; 'ole'
-                       AND software.hostname = computer.hostname;
-</programlisting>
-
-    with the plan
-
-<literallayout class="monospaced">
-Hash Join
-  -&gt;  Seq Scan on software
-  -&gt;  Hash
-    -&gt;  Index Scan using comp_hostidx on computer
-</literallayout>
-
-    The other possible command is:
-
-<programlisting>
-DELETE FROM computer WHERE hostname ~ '^old';
-</programlisting>
-
-    which results in the following executing plan for the command
-    added by the rule:
-
-<literallayout class="monospaced">
-Nestloop
-  -&gt;  Index Scan using comp_hostidx on computer
-  -&gt;  Index Scan using soft_hostidx on software
-</literallayout>
-
-    This shows, that the planner does not realize that the
-    qualification for <structfield>hostname</> in
-    <literal>computer</> could also be used for an index scan on
-    <literal>software</> when there are multiple qualification
-    expressions combined with <literal>AND</>, which is what it does
-    in the regular-expression version of the command. The trigger will
-    get invoked once for each of the 2000 old computers that have to be
-    deleted, and that will result in one index scan over
-    <literal>computer</> and 2000 index scans over
-    <literal>software</>. The rule implementation will do it with two
-    commands that use indexes.  And it depends on the overall size of
-    the table <literal>software</> whether the rule will still be faster in the
-    sequential scan situation. 2000 command executions from the trigger over the SPI
-    manager take some time, even if all the index blocks will soon be in the cache.
-</para>
-
-<para>
-    The last command we look at is:
-
-<programlisting>
-DELETE FROM computer WHERE manufacturer = 'bim';
-</programlisting>
-
-    Again this could result in many rows to be deleted from
-    <literal>computer</>. So the trigger will again run many commands
-    through the executor.  The command generated by the rule will be:
-
-<programlisting>
-DELETE FROM software WHERE computer.manufacturer = 'bim'
-                       AND software.hostname = computer.hostname;
-</programlisting>
-
-    The plan for that command will again be the nested loop over two
-    index scans, only using a different index on <literal>computer</>:
-
-<programlisting>
-Nestloop
-  -&gt;  Index Scan using comp_manufidx on computer
-  -&gt;  Index Scan using soft_hostidx on software
-</programlisting>
-
-    In any of these cases, the extra commands from the rule system
-    will be more or less independent from the number of affected rows
-    in a command.
-</para>
-
-<![IGNORE[
-<!-- What's happening with this?  If it doesn't come back, remove this section. -->
-<para>
-    Another situation is cases on <command>UPDATE</command> where it depends on the
-    change of an attribute if an action should be performed or
-    not. The only way to
-    create a rule as in the shoelace_log example is to do it with
-    a rule qualification. That results in an extra query that is
-    performed always, even if the attribute of interest cannot
-    change at all because it does not appear in the target list
-    of the initial query. When this is enabled again, it will be
-    one more advantage of rules over triggers. Optimization of
-    a trigger must fail by definition in this case, because the
-    fact that its actions will only be done when a specific attribute
-    is updated is hidden in its functionality. The definition of
-    a trigger only allows to specify it on row level, so whenever a
-    row is touched, the trigger must be called to make its
-    decision. The rule system will know it by looking up the
-    target list and will suppress the additional query completely
-    if the attribute isn't touched. So the rule, qualified or not,
-    will only do its scans if there ever could be something to do.
-</para>
-]]>
-
-<para>
-    The summary is, rules will only be significantly slower than
-    triggers if their actions result in large and badly qualified
-    joins, a situation where the planner fails.
-</para>
-<!## end>
-</sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/runtime.sgmlin b/doc-xc/src/sgml/runtime.sgmlin
deleted file mode 100644
index b32ac832cd..0000000000
--- a/doc-xc/src/sgml/runtime.sgmlin
+++ /dev/null
@@ -1,3897 +0,0 @@
-<!-- doc/src/sgml/runtime.sgml -->
-
-<chapter id="runtime">
- <title>Server Setup and Operation</title>
-
- <para>
-  This chapter discusses how to set up and run the database server
-  and its interactions with the operating system.
- </para>
-
- <sect1 id="postgres-user">
-<!## PG>
-  <title>The <productname>PostgreSQL</productname> User Account</title>
-<!## end>
-<!## XC>
-  <title>The <productname>Postgres-XC</productname> User Account</title>
-<!## end>
-<!## XL>
-  <title>The <productname>Postgres-XL</productname> User Account</title>
-<!## end>
-
-  <indexterm>
-   <primary>postgres user</primary>
-  </indexterm>
-&common;
-  <para>
-   As with any server daemon that is accessible to the outside world,
-<!## PG>
-   it is advisable to run <productname>PostgreSQL</productname> under a
-<!## end>
-<!## XC>
-   it is advisable to run <productname>Postgres-XC</productname> under a
-<!## end>
-<!## XL>
-   it is advisable to run <productname>Postgres-XL</productname> under a
-<!## end>
-   separate user account. This user account should only own the data
-   that is managed by the server, and should not be shared with other
-   daemons. (For example, using the user <literal>nobody</literal> is a bad
-   idea.) It is not advisable to install executables owned by this
-   user because compromised systems could then modify their own
-   binaries.
-  </para>
-
-  <para>
-   To add a Unix user account to your system, look for a command
-   <command>useradd</command> or <command>adduser</command>. The user
-   name <systemitem>postgres</systemitem> is often used, and is assumed
-   throughout this book, but you can use another name if you like.
-  </para>
- </sect1>
-
- <sect1 id="creating-cluster">
-  <title>Creating a Database Cluster</title>
-
-  <indexterm>
-   <primary>database cluster</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>data area</primary>
-   <see>database cluster</see>
-  </indexterm>
-
-<!## XL>
-  <para>
-   The steps to configure a <productname>Postgres-XL</productname> 
-   cluster can be cumbersome. It is highly recommended that you make use 
-   of a utility called <xref linkend="pgxc-ctl"> to make this task easier,
-   and you can skip a lot of the content in this chapter. 
-   That said, you may read on to understand how to manually configure
-   the cluster, which essentially describes the steps that <xref linkend="pgxc-ctl"> does.
-  </para>
-<!## end>
-  <para>
-   Before you can do anything, you must initialize a database storage
-   area on disk. We call this a <firstterm>database cluster</firstterm>.
-   (<acronym>SQL</acronym> uses the term catalog cluster.) A
-   database cluster is a collection of databases that is managed by a
-   single instance of a running database server. After initialization, a
-   database cluster will contain a database named <literal>postgres</literal>,
-   which is meant as a default database for use by utilities, users and third
-   party applications.  The database server itself does not require the
-   <literal>postgres</literal> database to exist, but many external utility
-   programs assume it exists.  Another database created within each cluster
-   during initialization is called
-   <literal>template1</literal>.  As the name suggests, this will be used
-   as a template for subsequently created databases; it should not be
-   used for actual work.  (See <xref linkend="managing-databases"> for
-   information about creating new databases within a cluster.)
-  </para>
-
- <!## XC>
-&xconly;
-  <para>
-   You should initialize  <firstterm>database cluster</firstterm> for
-   each <firstterm>Coordinator</> and <firstterm>Datanode</>.
-  </para>
- <!## end>
-&common;
-  <para>
-   In file system terms, a database cluster will be a single directory
-   under which all data will be stored. We call this the <firstterm>data
-   directory</firstterm> or <firstterm>data area</firstterm>. It is
-   completely up to you where you choose to store your data.  There is no
-   default, although locations such as
-   <filename>/usr/local/pgsql/data</filename> or
-   <filename>/var/lib/pgsql/data</filename> are popular. To initialize a
-   database cluster, use the command <xref
-   linkend="app-initdb">,<indexterm><primary>initdb</></> which is
-<!## PG>
-   installed with <productname>PostgreSQL</productname>. The desired
-   file system location of your database cluster is indicated by the
-   <option>-D</option> option, for example:
-<screen>
-<prompt>$</> <userinput>initdb -D /usr/local/pgsql/data</userinput>
-</screen>
-<!## end>
-<!## XC>
-   installed with <productname>Postgres-XC</productname>. The desired
-   file system location of your database cluster is indicated by the
-   <option>-D</option> option. You also need to define a node name for
-   the cluster element initialized, for example:
-<screen>
-<prompt>$</> <userinput>initdb -D /usr/local/pgsql/data --nodename foo</userinput>
-</screen>
-<!## end>
-<!## XL>
-   installed with <productname>Postgres-XL</productname>. The desired
-   file system location of your database cluster is indicated by the
-   <option>-D</option> option. You also need to define a node name for
-   the cluster element initialized, for example:
-<screen>
-<prompt>$</> <userinput>initdb -D /usr/local/pgsql/data --nodename foo</userinput>
-</screen>
-<!## end>
-<!## PG>
-   Note that you must execute this command while logged into the
-   <productname>PostgreSQL</productname> user account, which is
-   described in the previous section.
-<!## end>
-<!## XC>
-&xconly;
-   Note that you must execute this command while logged into the
-   <productname>Postgres-XC</productname> user account, which is
-   described in the previous section.  You should assign
-   separate <firstterm>data directory</> to
-   each <firstterm>Coordinator</> and <firstterm>Datanode</> if you
-   are configuring them in a same server.  
-<!## end>
-<!## XL>
-&xlonly;
-   Note that you must execute this command while logged into the
-   <productname>Postgres-XL</productname> user account, which is
-   described in the previous section.  You should assign
-   separate <firstterm>data directory</> to
-   each <firstterm>Coordinator</> and <firstterm>Datanode</> if you
-   are configuring them in a same server.  
-<!## end>
-  </para>
-  <tip>
-   <para>
-    As an alternative to the <option>-D</option> option, you can set
-    the environment variable <envar>PGDATA</envar>.
-    <indexterm><primary><envar>PGDATA</envar></primary></indexterm>
-   </para>
-<!## XC>
-   <para>
-    If you configure multiple <firstterm>Coordinator</>
-    and/or <firstterm>Datanode</>, you cannot
-    share <envar>PGDATA</envar> among them and you must
-    specify <firstterm>data directory</> explicitly.
-   </para>
-   <para>
-    <option>--nodename</option> is mandatory for all the nodes at initialization
-   </para>
-<!## end>
-<!## XL>
-   <para>
-    If you configure multiple <firstterm>Coordinator</>
-    and/or <firstterm>Datanode</>, you cannot
-    share <envar>PGDATA</envar> among them and you must
-    specify <firstterm>data directory</> explicitly.
-   </para>
-   <para>
-    <option>--nodename</option> is mandatory for all the nodes at initialization
-   </para>
-<!## end>
-  </tip>
-&common;
-  <para>
-   Alternatively, you can run <command>initdb</command> via
-   the <xref linkend="app-pg-ctl">
-   program<indexterm><primary>pg_ctl</></> like so:
-<!## PG>
-<screen>
-<prompt>$</> <userinput>pg_ctl -D /usr/local/pgsql/data initdb</userinput>
-</screen>
-<!## end>
-<!## XC>
-<screen>
-<prompt>$</> <userinput>pg_ctl -D /usr/local/pgsql/data -o '--nodename foo' initdb</userinput>
-</screen>
-<!## end>
-<!## XL>
-<screen>
-<prompt>$</> <userinput>pg_ctl -D /usr/local/pgsql/data -o '--nodename foo' initdb</userinput>
-</screen>
-<!## end>
-   This may be more intuitive if you are
-   using <command>pg_ctl</command> for starting and stopping the
-   server (see <xref linkend="server-start">), so
-   that <command>pg_ctl</command> would be the sole command you use
-   for managing the database server instance.
-  </para>
-
-  <para>
-   <command>initdb</command> will attempt to create the directory you
-   specify if it does not already exist. It is likely that it will not
-   have the permission to do so (if you followed our advice and created
-   an unprivileged account). In that case you should create the
-   directory yourself (as root) and change the owner to be the
-<!## PG>
-   <productname>PostgreSQL</productname> user. Here is how this might
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> user. Here is how this might
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> user. Here is how this might
-<!## end>
-   be done:
-<screen>
-root# <userinput>mkdir /usr/local/pgsql/data</userinput>
-root# <userinput>chown postgres /usr/local/pgsql/data</userinput>
-root# <userinput>su postgres</userinput>
-postgres$ <userinput>initdb -D /usr/local/pgsql/data --nodename foo</userinput>
-</screen>
-  </para>
-
-  <para>
-   <command>initdb</command> will refuse to run if the data directory
-   looks like it has already been initialized.</para>
-
-  <para>
-   Because the data directory contains all the data stored in the
-   database, it is essential that it be secured from unauthorized
-   access. <command>initdb</command> therefore revokes access
-   permissions from everyone but the
-<!## PG>
-   <productname>PostgreSQL</productname> user.
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> user.
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> user.
-<!## end>
-  </para>
-
-  <para>
-   However, while the directory contents are secure, the default
-   client authentication setup allows any local user to connect to the
-   database and even become the database superuser. If you do not
-   trust other local users, we recommend you use one of
-   <command>initdb</command>'s <option>-W</option>, <option>--pwprompt</option>
-   or <option>--pwfile</option> options to assign a password to the
-   database superuser.<indexterm>
-     <primary>password</>
-     <secondary>of the superuser</>
-   </indexterm>
-   Also, specify <option>-A md5</> or
-   <option>-A password</> so that the default <literal>trust</> authentication
-   mode is not used; or modify the generated <filename>pg_hba.conf</filename>
-   file after running <command>initdb</command>, but
-   <emphasis>before</> you start the server for the first time. (Other
-   reasonable approaches include using <literal>peer</literal> authentication
-   or file system permissions to restrict connections. See <xref
-   linkend="client-authentication"> for more information.)
-  </para>
-
-  <para>
-   <command>initdb</command> also initializes the default
-   locale<indexterm><primary>locale</></> for the database cluster.
-   Normally, it will just take the locale settings in the environment
-   and apply them to the initialized database.  It is possible to
-   specify a different locale for the database; more information about
-   that can be found in <xref linkend="locale">.  The default sort order used
-   within the particular database cluster is set by
-   <command>initdb</command>, and while you can create new databases using
-   different sort order, the order used in the template databases that initdb
-   creates cannot be changed without dropping and recreating them.
-   There is also a performance impact for using locales
-   other than <literal>C</> or <literal>POSIX</>. Therefore, it is
-   important to make this choice correctly the first time.
-  </para>
-
-  <para>
-   <command>initdb</command> also sets the default character set encoding
-   for the database cluster.  Normally this should be chosen to match the
-   locale setting.  For details see <xref linkend="multibyte">.
-  </para>
-
-  <sect2 id="creating-cluster-nfs">
-   <title>Network File Systems</title>
-
-   <indexterm zone="creating-cluster-nfs">
-    <primary>Network File Systems</primary>
-   </indexterm>
-   <indexterm><primary><acronym>NFS</></><see>Network File Systems</></>
-   <indexterm><primary>Network Attached Storage (<acronym>NAS</>)</><see>Network File Systems</></>
-&common;
-   <para>
-    Many installations create database clusters on network file systems.
-    Sometimes this is done directly via <acronym>NFS</>, or by using a
-    Network Attached Storage (<acronym>NAS</>) device that uses
-<!## PG>
-    <acronym>NFS</> internally.  <productname>PostgreSQL</> does nothing
-<!## end>
-<!## XC>
-    <acronym>NFS</> internally.  <productname>Postgres-XC</> does nothing
-<!## end>
-<!## XL>
-    <acronym>NFS</> internally.  <productname>Postgres-XL</> does nothing
-<!## end>
-    special for <acronym>NFS</> file systems, meaning it assumes
-    <acronym>NFS</> behaves exactly like locally-connected drives
-    (<acronym>DAS</>, Direct Attached Storage).  If client and server
-    <acronym>NFS</> implementations have non-standard semantics, this can
-    cause reliability problems (see <ulink
-    url="http://www.time-travellers.org/shane/papers/NFS_considered_harmful.html"></ulink>).
-    Specifically, delayed (asynchronous) writes to the <acronym>NFS</>
-    server can cause reliability problems;   if possible, mount
-    <acronym>NFS</> file systems synchronously (without caching) to avoid
-    this.  Also, soft-mounting <acronym>NFS</> is not recommended.
-    (Storage Area Networks (<acronym>SAN</>) use a low-level
-    communication protocol rather than <acronym>NFS</>.)
-   </para>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="server-start">
-<!## PG>
-  <title>Starting the Database Server</title>
-<!## end>
-<!## XC>
-  <title>Starting Postgres-XC Cluster</title>
-<!## end>
-<!## XL>
-  <title>Starting Postgres-XL Cluster</title>
-<!## end>
-
-<!## XC>
-&xconly;
-  <para>
-   Before anyone can access <productname>Postgres-XC</>
-   (or <productname>XC</> in short) database, you must
-   start <productname>XC</> database cluster.
-   As described in the previous chapter, <productname>XC</> consists of
-   various components. 
-   Minimum set of components are GTM, GTM-Proxy, Coordinator and
-   Datanode.
-   You must configure and start each of them.
-   Following sections will give you how to configure and start them.   
-   <filename>pgxc_clean</> and <filename>GTM-Standby</> are described in high-availability
-   sections.
-  </para>
-
-  <sect2 id="creating-databases">
-   <title>Creating Databases</title>
-&xconly;
-   <para>
-    You should initialize each database which
-    composes <productname>Postgres-XC</> database cluster system. 
-    Both Coordinator and Datanode has its own database and you should
-    initialize these database.
-    Coordinator holds just database catalog and temporary data store.  
-    Datanode holds most of your data.  
-    First of all, you should determine how many Coordinators/Datanodes
-    to run and where they should run. 
-    It is a good convention that you run a Coordinator where you run a
-    Datanode.   
-    In this case, you should run <filename>GTM-Proxy</> on the same
-    server too. 
-    It simplifies <productname>XC</> configuration and help to make
-    workload of each servers even.
-   </para>
-
-   <para>
-    Both Coordinator and Datanode have their
-    own databases, essentially <productname>PostgreSQL</> databases.
-    They are separate and you should initialize them separately.
-   </para>
-  </sect2>
-
-  <sect2 id="gtm-start">
-   <title>Starting GTM</title>
-&xconly;
-   <para>
-    GTM provides global transaction management feature to all the
-    other components in <productname>Postgres-XC</> database cluster.
-    Because GTM handles transaction requirements from all
-    the Coordinators and Datanodes, it is highly advised to run this
-    in a separate server.
-   </para>
-
-  <para>
-   Before you start GTM, you should decide followings:
-  </para>
-
-  <variablelist>
-
-  <varlistentry>
-   <term>Where to run GTM</term>
-   <listitem>
-
-    <para>
-     Because GTM receives all the request to begin/end
-     transactions and to refer to sequence values, you should
-     run GTM in a separate server.  If you
-     run GTM in the same server as Datanode or
-     Coordinator, it will become harder to make workload reasonably
-     balanced.
-    </para>
-    <para>
-     Then, you should determine GTM's working directory.
-     Please create this directory before you run GTM.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Listen address and port of GTM</term>
-   <listitem>
-    <para>
-     Next, you should determine listen address and port
-     of GTM.
-     Listen address can be either the IP address or host name which
-     receives request from other component,
-     typically <filename>GTM-Proxy</filename>.
-    </para>
-   </listitem>
-   </varlistentry>
-
-  </variablelist>
-
-   <para>
-    When this is determined, you can initialize GTM with the command <xref
-   linkend="app-initgtm">,
-    for example:
-<screen>
-<prompt>$</> <userinput>initgtm -Z gtm -D /usr/local/pgsql/data_gtm</userinput>
-</screen>
-   </para>
-
-   <para>
-    All the parameters related to GTM can be modified in <filename>gtm.conf</filename>
-    located in data folder initialized by <command>initgtm</command>.
-   </para>
-
-   <para>
-    Then you can start GTM as follows:
-<!-- Check precise parameters -->
-<screen>
-<prompt>$</> <userinput>gtm -D /usr/local/pgsql/data_gtm</userinput>
-</screen>
-    where <option>-D</> option specifies working directory of GTM.
-   </para>
-   <para>
-    Alternatively, GTM can be started using <command>gtm_ctl</>, for example:
-<screen>
-<prompt>$</> <userinput>gtm_ctl -Z gtm start -D /usr/local/pgsql/data_gtm</userinput>
-</screen>
-   </para>
-
-  </sect2>
-  <sect2 id="gtm-proxy-start">
-   <title>Starting GTM-Proxy</title>
-&xconly;
-   <para>
-    GTM-Proxy is not a mandatory component of Postgres-XC cluster but
-    it can be used to group messages between GTM and cluster nodes,
-    reducing workload and the number of packages exchanged through network.
-   </para>
-
-   <para>
-    As described in the previous section, <filename>GTM-Proxy</> needs
-    its own listen address, port, working directory and GTM-Proxy ID,
-    which should be unique and begins with one.
-    In addition, you should determine how many working threads to
-    run.
-    You should also use GTM's address and port to start <filename>GTM-Proxy</>.
-   </para>
-
-   <para>
-    Then, you need first to initialize GTM-Proxy with <command>initgtm</command>,
-    for example:
-<screen>
-<prompt>$</> <userinput>initgtm -Z gtm_proxy -D /usr/local/pgsql/data_gtm_proxy</userinput>
-</screen>
-   </para>
-
-   <para>
-    All the parameters related to GTM-Proxy can be modified in <filename>gtm_proxy.conf</filename>
-    located in data folder initialized by <command>initgtm</command>.
-   </para>
-
-   <para>
-    Then, you can start <filename>GTM-Proxy</> like:
-<screen>
-<prompt>$</> <userinput>gtm_proxy -D /usr/local/pgsql/data_gtm_proxy</userinput>
-</screen>
-    where <option>-D</> specifies <filename>GTM-Proxy</>'s working
-    directory.
-   </para>
-
-  <para>
-   Alternatively, you can start GTM-Proxy using <filename>gtm_ctl</>
-   as follows:
-<screen>
-<prompt>$</> <userinput>gtm_ctl start -Z gtm_proxy -D /usr/local/pgsql/data_gtm_proxy</userinput>
-</screen>
-  </para>
-
-  </sect2>
-
-  <sect2 id="Datanode-configuration">
-   <title>Configuring Datanode</title>
-&xconly;
-   <para>
-    Before starting Coordinator or Datanode, you must configure them.
-    You can configure Coordinator or Datanode by
-    editing <filename>postgresql.conf</> file located at their working
-    directory as you specified by <option>-D</> option
-    in <filename>initdb</> command.
-   </para>
-
-   <para>
-    Datanode is almost native <productname>PostgreSQL</> with some
-    extension.
-    Additional options in <filename>postgresql.conf</> for the
-    Datanode are as follows:
-   </para>
-
-  <variablelist>
-
-  <varlistentry>
-   <term>max_connections</term>
-   <listitem>
-
-    <para>
-     This value is not just a number of connections you expect to each
-     Coordinator.
-	 Each Coordinator backend has a chance to connect to all the
-     Datanode.
-     You should specify number of total connections whole Coordinator
-     may accept.
-     For example, if you have five Coordinators and each of them may
-     accept forty connections, you should specify 200 as this
-     parameter value.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>max_prepared_transactions</term>
-   <listitem>
-    <para>
-     Even though your application does not intend to
-     issue <command>PREPARE TRANSACTION</>, Coordinator may issue this
-     internally when more than one Datanode are involved.
-	 You should specify this parameter the same value
-     as <filename>max_connections</>.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>pgxc_node_name</term>
-   <listitem>
-    <para>
-     GTM needs to identify each Datanode, as specified by
-     this parameter.
-     The value should be unique and start with one.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>port</term>
-   <listitem>
-    <para>
-     Because both Coordinator and Datanode may run on the same server,
-     you may want to assign separate port number to the Datanode.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>gtm_port</term>
-   <listitem>
-    <para>
-     Specify the port number of GTM-Proxy, as specified
-     in <option>-p</> option in <command>gtm_proxy</>
-     or <command>gtm_ctl</>.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>gtm_host</term>
-   <listitem>
-    <para>
-     Specify the host name or IP address of GTM-Proxy, as specified
-     in <option>-h</> option in <command>gtm_proxy</>
-     or <command>gtm_ctl</>.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>pooler_port</term>
-   <listitem>
-    <para>
-		Specify the port number that the pooler should use. This must not
-conflict with any other server ports used on this host.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  </variablelist>
-
-   </sect2>
-
-  <sect2 id="Coordinator-configuration">
-   <title>Configuring Coordinator</title>
-&xconly;
-   <para>
-    Although Coordinator and Datanode shares the same binary, their
-    configuration is a little different due to their functionalities.
-   </para>
-
-  <variablelist>
-
-  <varlistentry>
-   <term>max_connections</term>
-   <listitem>
-    <para>
-     You don't have to take other Coordinator or Datanode into
-     account.
-	 Just specify the number of connections the Coordinator accepts
-     from applications.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>max_prepared_transactions</term>
-   <listitem>
-    <para>
-     Specify at least total number of Coordinators in the cluster.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>pgxc_node_name</term>
-   <listitem>
-    <para>
-     GTM needs to identify each Datanode, as specified by
-     this parameter.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>port</term>
-   <listitem>
-    <para>
-     Because both Coordinator and Datanode may run on the same server,
-     you may want to assign separate port number to the Coordinator.
-     It may be convenient to use default value of PostgreSQL listen
-     port.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>gtm_port</term>
-   <listitem>
-    <para>
-     Specify the port number of GTM-Proxy, as specified
-     in <option>-p</> option in <command>gtm_proxy</>
-     or <command>gtm_ctl</>.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>gtm_host</term>
-   <listitem>
-    <para>
-     Specify the host name or IP address of GTM-Proxy, as specified
-     in <option>-h</> option in <command>gtm_proxy</>
-     or <command>gtm_ctl</>.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>max_pool_size</term>
-   <listitem>
-    <para>
-     Coordinator maintains connections to Datanode as a pool.
-     This parameter specifies max number of connections the
-     Coordinator maintains.
-     Specify <option>max_connection</> value of remote nodes as this
-     parameter value.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>min_pool_size</term>
-   <listitem>
-    <para>
-     This is the minimum number of Coordinator to remote node connections
-     maintained by the pooler.
-     Typically specify 1.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>max_coordinators</term>
-   <listitem>
-    <para>
-     This is the maximum number of Coordinators that can be configured in the cluster.
-     Specify exact number if it is not planned to add more Coordinators
-     while cluster is running, or greater, if it is desired to dynamically
-     resize cluster. It costs about 140 bytes of shared memory per slot.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>max_datanodes</term>
-   <listitem>
-    <para>
-     This is the maximum number of Datanodes configured in the cluster.
-     Specify exact number if it is not planned to add more Datanodes
-     while cluster is running, or greater, if it is desired to dynamically
-     resize cluster. It costs about 140 bytes of shared memory per slot.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>enforce_two_phase_commit</term>
-   <listitem>
-    <para>
-     Enforce the usage of two-phase commit on transactions involving ON COMMIT actions
-     or temporary objects. Usage of autocommit instead of two-phase commit may break data
-     consistency so use at your own risk.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  </variablelist>
-
-  </sect2>
-
-  <sect2 id="starting-Datanode">
-   <title>Starting Datanodes</title>
-
-   <para>
-    Now you can start central component
-    of <productname>Postgres-XC</>, Datanode and Coordinator.
-	If you're familiar with starting <productname>PostgreSQL</>
-    database server, this step is very similar to <productname>PostgreSQL</>.
-   </para>
-
-   <para>
-    You can start a Datanode as follows:
-<screen>
-<prompt>$</> <userinput>postgres --datanode -D /usr/local/pgsql/data</userinput>
-</screen>
-    <option>--datanode</> specifies <command>postgres</> should run as a
-    Datanode. You may need to specify <option>-i</> <command>postgres</> to
-    accept connection from TCP/IP connections or edit <filename>pg_hba.conf</filename>
-    if cluster uses nodes among several servers.
-   </para>
-
-  </sect2>
-
-  <sect2 id="starting-Coordinator">
-   <title>Starting Coordinators</title>
-&xconly;
-   <para>
-    You can start a Coordinator as follows:
-<screen>
-<prompt>$</> <userinput>postgres --coordinator -D /usr/local/pgsql/Datanode</userinput>
-</screen>
-    <option>--coordinator</> specifies <command>postgres</> should run as a
-    Coordinator. You may need to specify <option>-i</> <command>postgres</> to
-    accept connection from TCP/IP connections or edit <filename>pg_hba.conf</filename>
-    if cluster uses nodes among several servers.
-   </para>
-
-  </sect2>
-
-
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Before anyone can access <productname>Postgres-XL</>
-   (or <productname>XL</> in short) database, you must
-   start <productname>XL</> database cluster.
-   As described in the previous chapter, <productname>XL</> consists of
-   various components. 
-   Minimum set of components are GTM, GTM-Proxy, Coordinator and
-   Datanode.
-   You must configure and start each of them.
-   Following sections will give you how to configure and start them.   
-   <filename>pgxc_clean</> and <filename>GTM-Standby</> are described in high-availability
-   sections.
-  </para>
-
-  <sect2 id="creating-databases">
-   <title>Creating Databases</title>
-&xlonly;
-   <para>
-    You should initialize each database which
-    composes <productname>Postgres-XL</> database cluster system. 
-    Both Coordinator and Datanode has its own database and you should
-    initialize these database.
-    Coordinator holds just database catalog and temporary data store.  
-    Datanode holds most of your data.  
-    First of all, you should determine how many Coordinators/Datanodes
-    to run and where they should run. 
-    It is a good convention that you run a Coordinator where you run a
-    Datanode.   
-    In this case, you should run <filename>GTM-Proxy</> on the same
-    server too. 
-    It simplifies <productname>XL</> configuration and help to make
-    workload of each servers even.
-   </para>
-
-   <para>
-    Both Coordinator and Datanode have their
-    own databases, essentially <productname>PostgreSQL</> databases.
-    They are separate and you should initialize them separately.
-   </para>
-  </sect2>
-
-  <sect2 id="gtm-start">
-   <title>Starting GTM</title>
-&xlonly;
-   <para>
-    GTM provides global transaction management feature to all the
-    other components in <productname>Postgres-XL</> database cluster.
-    Because GTM handles transaction requirements from all
-    the Coordinators and Datanodes, it is highly advised to run this
-    in a separate server.
-   </para>
-
-  <para>
-   Before you start GTM, you should decide followings:
-  </para>
-
-  <variablelist>
-
-  <varlistentry>
-   <term>Where to run GTM</term>
-   <listitem>
-
-    <para>
-     Because GTM receives all the request to begin/end
-     transactions and to refer to sequence values, you should
-     run GTM in a separate server.  If you
-     run GTM in the same server as Datanode or
-     Coordinator, it will become harder to make workload reasonably
-     balanced.
-    </para>
-    <para>
-     Then, you should determine GTM's working directory.
-     Please create this directory before you run GTM.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Listen address and port of GTM</term>
-   <listitem>
-    <para>
-     Next, you should determine listen address and port
-     of GTM.
-     Listen address can be either the IP address or host name which
-     receives request from other component,
-     typically <filename>GTM-Proxy</filename>.
-    </para>
-   </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>GTM id</term>
-    <listitem>
-     <para>
-      You have a chance to run more than one GTM in
-      one <productname>Postgres-XL</> cluster.  
-      For example, if you need a backup of GTM in
-      high-availability environment, you need to run
-      two GTMs.
-      You should give unique GTM id to each of such GTMs.
-      GTM id value begins with one.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
-   <para>
-    When this is determined, you can initialize GTM with the command <xref
-   linkend="app-initgtm">,
-    for example:
-<screen>
-<prompt>$</> <userinput>initgtm -Z gtm -D /usr/local/pgsql/data_gtm</userinput>
-</screen>
-   </para>
-
-   <para>
-    All the parameters related to GTM can be modified in <filename>gtm.conf</filename>
-    located in data folder initialized by <command>initgtm</command>.
-   </para>
-
-   <para>
-    Then you can start GTM as follows:
-<!-- Check precise parameters -->
-<screen>
-<prompt>$</> <userinput>gtm -D /usr/local/pgsql/data_gtm</userinput>
-</screen>
-    where <option>-D</> option specifies working directory of GTM.
-   </para>
-   <para>
-    Alternatively, GTM can be started using <command>gtm_ctl</>, for example:
-<screen>
-<prompt>$</> <userinput>gtm_ctl -Z gtm start -D /usr/local/pgsql/data_gtm</userinput>
-</screen>
-   </para>
-
-  </sect2>
-  <sect2 id="gtm-proxy-start">
-   <title>Starting GTM-Proxy</title>
-&xlonly;
-   <para>
-    GTM-Proxy is not a mandatory component of Postgres-XL cluster but
-    it can be used to group messages between GTM and cluster nodes,
-    reducing workload and the number of packages exchanged through network.
-   </para>
-
-   <para>
-    As described in the previous section, <filename>GTM-Proxy</> needs
-    its own listen address, port, working directory and GTM-Proxy ID,
-    which should be unique and begins with one.
-    In addition, you should determine how many working threads to
-    run.
-    You should also use GTM's address and port to start <filename>GTM-Proxy</>.
-   </para>
-
-   <para>
-    Then, you need first to initialize GTM-Proxy with <command>initgtm</command>,
-    for example:
-<screen>
-<prompt>$</> <userinput>initgtm -Z gtm_proxy -D /usr/local/pgsql/data_gtm_proxy</userinput>
-</screen>
-   </para>
-
-   <para>
-    All the parameters related to GTM-Proxy can be modified in <filename>gtm_proxy.conf</filename>
-    located in data folder initialized by <command>initgtm</command>.
-   </para>
-
-   <para>
-    Then, you can start <filename>GTM-Proxy</> like:
-<screen>
-<prompt>$</> <userinput>gtm_proxy -D /usr/local/pgsql/data_gtm_proxy</userinput>
-</screen>
-    where <option>-D</> specifies <filename>GTM-Proxy</>'s working
-    directory.
-   </para>
-
-  <para>
-   Alternatively, you can start GTM-Proxy using <filename>gtm_ctl</>
-   as follows:
-<screen>
-<prompt>$</> <userinput>gtm_ctl start -Z gtm_proxy -D /usr/local/pgsql/data_gtm_proxy</userinput>
-</screen>
-  </para>
-
-  </sect2>
-
-  <sect2 id="Datanode-configuration">
-   <title>Configuring Datanodes</title>
-&xlonly;
-   <para>
-    Before starting Coordinator or Datanode, you must configure them.
-    You can configure Coordinator or Datanode by
-    editing <filename>postgresql.conf</> file located at their working
-    directory as you specified by <option>-D</> option
-    in <filename>initdb</> command.
-   </para>
-
-   <para>
-    Datanode is almost native <productname>PostgreSQL</> with some
-    extension.
-    Additional options in <filename>postgresql.conf</> for the
-    Datanode are as follows:
-   </para>
-
-  <variablelist>
-
-  <varlistentry>
-   <term>max_connections</term>
-   <listitem>
-
-    <para>
-     This value is not just a number of connections you expect to each
-     Coordinator.
-	 Each Coordinator backend has a chance to connect to all the
-     Datanode.
-     You should specify number of total connections whole Coordinator
-     may accept.
-     For example, if you have five Coordinators and each of them may
-     accept forty connections, you should specify 200 as this
-     parameter value.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>max_prepared_transactions</term>
-   <listitem>
-    <para>
-     Even though your application does not intend to
-     issue <command>PREPARE TRANSACTION</>, Coordinator may issue this
-     internally when more than one Datanode are involved.
-	 You should specify this parameter the same value
-     as <filename>max_connections</>.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>pgxc_node_name</term>
-   <listitem>
-    <para>
-     GTM needs to identify each Datanode, as specified by
-     this parameter.
-     The value should be unique and start with one.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>port</term>
-   <listitem>
-    <para>
-     Because both Coordinator and Datanode may run on the same server,
-     you may want to assign separate port number to the Datanode.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>gtm_port</term>
-   <listitem>
-    <para>
-     Specify the port number of GTM-Proxy, as specified
-     in <option>-p</> option in <command>gtm_proxy</>
-     or <command>gtm_ctl</>.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>gtm_host</term>
-   <listitem>
-    <para>
-     Specify the host name or IP address of GTM-Proxy, as specified
-     in <option>-h</> option in <command>gtm_proxy</>
-     or <command>gtm_ctl</>.
-    </para>
-   </listitem>
-  </varlistentry>
-
-    <varlistentry>
-     <term>shared_queues</term>
-     <listitem>
-      <para>
-       For some joins that occur in queries, data from one Datanode may
-       need to be joined with data from another Datanode.
-       <productname>Postgres-XL</productname> uses shared queues for this purpose.
-       During execution each Datanode knows if it needs to produce or consume
-       tuples, or both.
-      </para>
-      <para>
-       Note that there may be mulitple shared_queues used even for a single
-       query. So a value should be set taking into account the number of
-       connections it can accept and expected number of such joins occurring
-       simultaneously.
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>shared_queue_size</term>
-     <listitem>
-      <para>
-       This parameter sets the size of each each shared queue allocated.
-      </para>
-     </listitem>
-    </varlistentry>
-
-  </variablelist>
-
-   </sect2>
-
-  <sect2 id="Coordinator-configuration">
-   <title>Configuring Coordinators</title>
-&xlonly;
-   <para>
-    Although Coordinator and Datanode shares the same binary, their
-    configuration is a little different due to their functionalities.
-   </para>
-
-  <variablelist>
-
-  <varlistentry>
-   <term>max_connections</term>
-   <listitem>
-    <para>
-     You don't have to take other Coordinator or Datanode into
-     account.
-	 Just specify the number of connections the Coordinator accepts
-     from applications.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>max_prepared_transactions</term>
-   <listitem>
-    <para>
-     Specify at least total number of Coordinators in the cluster.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>pgxc_node_name</term>
-   <listitem>
-    <para>
-     GTM needs to identify each Datanode, as specified by
-     this parameter.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>port</term>
-   <listitem>
-    <para>
-     Because both Coordinator and Datanode may run on the same server,
-     you may want to assign separate port number to the Coordinator.
-     It may be convenient to use default value of PostgreSQL listen
-     port.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>gtm_port</term>
-   <listitem>
-    <para>
-     Specify the port number of GTM-Proxy, as specified
-     in <option>-p</> option in <command>gtm_proxy</>
-     or <command>gtm_ctl</>.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>gtm_host</term>
-   <listitem>
-    <para>
-     Specify the host name or IP address of GTM-Proxy, as specified
-     in <option>-h</> option in <command>gtm_proxy</>
-     or <command>gtm_ctl</>.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>pooler_port</term>
-   <listitem>
-    <para>
-		Specify the port number that the pooler should use. This must not
-conflict with any other server ports used on this host.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>max_pool_size</term>
-   <listitem>
-    <para>
-     Coordinator maintains connections to Datanode as a pool.
-     This parameter specifies max number of connections the
-     Coordinator maintains.
-     Specify <option>max_connection</> value of remote nodes as this
-     parameter value.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>min_pool_size</term>
-   <listitem>
-    <para>
-     This is the minimum number of Coordinator to remote node connections
-     maintained by the pooler.
-     Typically specify 1.
-    </para>
-   </listitem>
-  </varlistentry>
-
-    <varlistentry>
-     <term>pool_conn_keepalive</term>
-     <listitem>
-      <para>
-       This parameter specifies how long to keep the connection alive.
-       If older than this amount, the pooler discards the connection.
-       This parameter is useful in multi-tenant environments where
-       many connections to many different databases may be used,
-       so that idle connections may cleaned up. It is also useful
-       for automatically closing connections occasionally in case
-       there is some unknown memory leak so that this memory can be freed.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>pool_maintenance_timeout</term>
-     <listitem>
-      <para>
-       This parameter specifies how long to wait until pooler
-       maintenance is performed. During such maintenance,
-       old idle connections are discarded.
-       This parameter is useful in multi-tenant environments where
-       many connections to many different databases may be used,
-       so that idle connections may cleaned up.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>remote_query_cost</term>
-     <listitem>
-      <para>
-       This parameter specifies the cost overhead of setting up
-       a remote query to obtain remote data. It is used by
-       the planner in costing queries.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>network_byte_cost</term>
-     <listitem>
-      <para>
-       This parameter is used in query cost planning to
-       estimate the cost involved in row shipping and obtaining
-       remote data based on the expected data size.
-       Row shipping is expensive and adds latency, so this
-       setting helps to favor plans that minimizes row shipping.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>sequence_range</term>
-     <listitem>
-      <para>
-       This parameter is used to get several sequence values
-       at once from GTM.  This greatly speeds up COPY and INSERT SELECT
-       operations where the target table uses sequences.
-       <productname>Postgres-XL</productname> will not use this entire
-       amount at once, but will increase the request size over
-       time if many requests are done in a short time frame in
-       the same session.
-       After a short time without any sequence requests, decreases back down to 1.
-       Note that any settings here are overriden if the CACHE clause was
-       used in <xref linkend='sql-createsequence'> or <xref linkend='sql-altersequence'>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-  <varlistentry>
-   <term>max_coordinators</term>
-   <listitem>
-    <para>
-     This is the maximum number of Coordinators that can be configured in the cluster.
-     Specify exact number if it is not planned to add more Coordinators
-     while cluster is running, or greater, if it is desired to dynamically
-     resize cluster. It costs about 140 bytes of shared memory per slot.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>max_datanodes</term>
-   <listitem>
-    <para>
-     This is the maximum number of Datanodes configured in the cluster.
-     Specify exact number if it is not planned to add more Datanodes
-     while cluster is running, or greater, if it is desired to dynamically
-     resize cluster. It costs about 140 bytes of shared memory per slot.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>enforce_two_phase_commit</term>
-   <listitem>
-    <para>
-     Enforce the usage of two-phase commit on transactions involving ON COMMIT actions
-     or temporary objects. Usage of autocommit instead of two-phase commit may break data
-     consistency so use at your own risk.
-    </para>
-   </listitem>
-  </varlistentry>
-  </variablelist>
-
-  </sect2>
-
-  <sect2 id="starting-Datanode">
-   <title>Starting Datanodes</title>
-
-   <para>
-    Now you can start central component
-    of <productname>Postgres-XL</>, Datanode and Coordinator.
-	If you're familiar with starting <productname>PostgreSQL</>
-    database server, this step is very similar to <productname>PostgreSQL</>.
-   </para>
-
-   <para>
-    You can start a Datanode as follows:
-<screen>
-<prompt>$</> <userinput>postgres --datanode -D /usr/local/pgsql/data</userinput>
-</screen>
-    <option>--datanode</> specifies <command>postgres</> should run as a
-    Datanode. You may need to specify <option>-i</> <command>postgres</> to
-    accept connection from TCP/IP connections or edit <filename>pg_hba.conf</filename>
-    if cluster uses nodes among several servers.
-   </para>
-
-  </sect2>
-
-  <sect2 id="starting-Coordinator">
-   <title>Starting Coordinators</title>
-&xlonly;
-   <para>
-    You can start a Coordinator as follows:
-<screen>
-<prompt>$</> <userinput>postgres --coordinator -D /usr/local/pgsql/Datanode</userinput>
-</screen>
-    <option>--coordinator</> specifies <command>postgres</> should run as a
-    Coordinator. You may need to specify <option>-i</> <command>postgres</> to
-    accept connection from TCP/IP connections or edit <filename>pg_hba.conf</filename>
-    if cluster uses nodes among several servers.
-   </para>
-
-  </sect2>
-
-
-<!## end>
-<!## PG>
-  <para>
-   Before anyone can access the database, you must start the database
-   server. The database server program is called
-   <command>postgres</command>.<indexterm><primary>postgres</></>
-   The <command>postgres</command> program must know where to
-   find the data it is supposed to use. This is done with the
-   <option>-D</option> option. Thus, the simplest way to start the
-   server is:
-<screen>
-$ <userinput>postgres -D /usr/local/pgsql/data</userinput>
-</screen>
-   which will leave the server running in the foreground. This must be
-   done while logged into the <productname>PostgreSQL</productname> user
-   account. Without <option>-D</option>, the server will try to use
-   the data directory named by the environment variable <envar>PGDATA</envar>.
-   If that variable is not provided either, it will fail.
-  </para>
-
-  <para>
-   Normally it is better to start <command>postgres</command> in the
-   background.  For this, use the usual Unix shell syntax:
-<screen>
-$ <userinput>postgres -D /usr/local/pgsql/data &gt;logfile 2&gt;&amp;1 &amp;</userinput>
-</screen>
-   It is important to store the server's <systemitem>stdout</> and
-   <systemitem>stderr</> output somewhere, as shown above. It will help
-   for auditing purposes and to diagnose problems. (See <xref
-   linkend="logfile-maintenance"> for a more thorough discussion of log
-   file handling.)
-  </para>
-
-  <para>
-   The <command>postgres</command> program also takes a number of other
-   command-line options. For more information, see the
-   <xref linkend="app-postgres"> reference page
-   and <xref linkend="runtime-config"> below.
-  </para>
-
-  <para>
-   This shell syntax can get tedious quickly.  Therefore the wrapper
-   program
-   <xref linkend="app-pg-ctl"><indexterm><primary>pg_ctl</primary></indexterm>
-   is provided to simplify some tasks.  For example:
-<programlisting>
-pg_ctl start -l logfile
-</programlisting>
-   will start the server in the background and put the output into the
-   named log file. The <option>-D</option> option has the same meaning
-   here as for <command>postgres</command>. <command>pg_ctl</command>
-   is also capable of stopping the server.
-  </para>
-
-  <para>
-   Normally, you will want to start the database server when the
-   computer boots.<indexterm>
-     <primary>booting</>
-     <secondary>starting the server during</>
-   </indexterm>
-   Autostart scripts are operating-system-specific.
-   There are a few distributed with
-   <productname>PostgreSQL</productname> in the
-   <filename>contrib/start-scripts</> directory. Installing one will require
-   root privileges.
-  </para>
-
-  <para>
-   Different systems have different conventions for starting up daemons
-   at boot time. Many systems have a file
-   <filename>/etc/rc.local</filename> or
-   <filename>/etc/rc.d/rc.local</filename>. Others use
-   <filename>rc.d</> directories. Whatever you do, the server must be
-   run by the <productname>PostgreSQL</productname> user account
-   <emphasis>and not by root</emphasis> or any other user. Therefore you
-   probably should form your commands using <literal>su -c '...'
-   postgres</literal>.  For example:
-<programlisting>
-su -c 'pg_ctl start -D /usr/local/pgsql/data -l serverlog' postgres
-</programlisting>
-  </para>
-
-  <para>
-   Here are a few more operating-system-specific suggestions. (In each
-   case be sure to use the proper installation directory and user
-   name where we show generic values.)
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      For <productname>FreeBSD</productname>, look at the file
-      <filename>contrib/start-scripts/freebsd</filename> in the
-      <productname>PostgreSQL</productname> source distribution.
-      <indexterm><primary>FreeBSD</><secondary>start script</secondary></>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      On <productname>OpenBSD</productname>, add the following lines
-      to the file <filename>/etc/rc.local</filename>:
-      <indexterm><primary>OpenBSD</><secondary>start script</secondary></>
-<programlisting>
-if [ -x /usr/local/pgsql/bin/pg_ctl -a -x /usr/local/pgsql/bin/postgres ]; then
-    su - -c '/usr/local/pgsql/bin/pg_ctl start -l /var/postgresql/log -s' postgres
-    echo -n ' postgresql'
-fi
-</programlisting>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      On <productname>Linux</productname> systems either add
-      <indexterm><primary>Linux</><secondary>start script</secondary></>
-<programlisting>
-/usr/local/pgsql/bin/pg_ctl start -l logfile -D /usr/local/pgsql/data
-</programlisting>
-      to <filename>/etc/rc.d/rc.local</filename> or look at the file
-      <filename>contrib/start-scripts/linux</filename> in the
-      <productname>PostgreSQL</productname> source distribution.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      On <productname>NetBSD</productname>, either use the
-      <productname>FreeBSD</productname> or
-      <productname>Linux</productname> start scripts, depending on
-      preference. <indexterm><primary>NetBSD</><secondary>start script</secondary></>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      On <productname>Solaris</productname>, create a file called
-      <filename>/etc/init.d/postgresql</filename> that contains
-      the following line:
-      <indexterm><primary>Solaris</><secondary>start script</secondary></>
-<programlisting>
-su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D /usr/local/pgsql/data"
-</programlisting>
-      Then, create a symbolic link to it in <filename>/etc/rc3.d</> as
-      <filename>S99postgresql</>.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-  </para>
-
-   <para>
-    While the server is running, its
-    <acronym>PID</acronym> is stored in the file
-    <filename>postmaster.pid</filename> in the data directory. This is
-    used to prevent multiple server instances from
-    running in the same data directory and can also be used for
-    shutting down the server.
-   </para>
-
-<!## end>
-
-   <sect2 id="server-start-failures">
-    <title>Server Start-up Failures</title>
-&common;
-    <para>
-     There are several common reasons the server might fail to
-     start. Check the server's log file, or start it by hand (without
-     redirecting standard output or standard error) and see what error
-     messages appear. Below we explain some of the most common error
-     messages in more detail.
-    </para>
-
-    <para>
-<screen>
-LOG:  could not bind IPv4 socket: Address already in use
-HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
-FATAL:  could not create TCP/IP listen socket
-</screen>
-     This usually means just what it suggests: you tried to start
-     another server on the same port where one is already running.
-     However, if the kernel error message is not <computeroutput>Address
-     already in use</computeroutput> or some variant of that, there might
-     be a different problem. For example, trying to start a server
-     on a reserved port number might draw something like:
-<screen>
-$ <userinput>postgres -p 666</userinput>
-LOG:  could not bind IPv4 socket: Permission denied
-HINT:  Is another postmaster already running on port 666? If not, wait a few seconds and retry.
-FATAL:  could not create TCP/IP listen socket
-</screen>
-    </para>
-
-    <para>
-     A message like:
-<screen>
-FATAL:  could not create shared memory segment: Invalid argument
-DETAIL:  Failed system call was shmget(key=5440001, size=4011376640, 03600).
-</screen>
-     probably means your kernel's limit on the size of shared memory is
-     smaller than the work area <productname>PostgreSQL</productname>
-     is trying to create (4011376640 bytes in this example). Or it could
-     mean that you do not have System-V-style shared memory support
-     configured into your kernel at all. As a temporary workaround, you
-     can try starting the server with a smaller-than-normal number of
-     buffers (<xref linkend="guc-shared-buffers">). You will eventually want
-     to reconfigure your kernel to increase the allowed shared memory
-     size. You might also see this message when trying to start multiple
-     servers on the same machine, if their total space requested
-     exceeds the kernel limit.
-    </para>
-
-    <para>
-     An error like:
-<screen>
-FATAL:  could not create semaphores: No space left on device
-DETAIL:  Failed system call was semget(5440126, 17, 03600).
-</screen>
-     does <emphasis>not</emphasis> mean you've run out of disk
-     space. It means your kernel's limit on the number of <systemitem
-     class="osname">System V</> semaphores is smaller than the number
-     <productname>PostgreSQL</productname> wants to create. As above,
-     you might be able to work around the problem by starting the
-     server with a reduced number of allowed connections
-     (<xref linkend="guc-max-connections">), but you'll eventually want to
-     increase the kernel limit.
-    </para>
-
-    <para>
-     If you get an <quote>illegal system call</> error, it is likely that
-     shared memory or semaphores are not supported in your kernel at
-     all. In that case your only option is to reconfigure the kernel to
-     enable these features.
-    </para>
-
-    <para>
-     Details about configuring <systemitem class="osname">System V</>
-     <acronym>IPC</> facilities are given in <xref linkend="sysvipc">.
-    </para>
-   </sect2>
-
-   <sect2 id="client-connection-problems">
-    <title>Client Connection Problems</title>
-&common;
-    <para>
-     Although the error conditions possible on the client side are quite
-     varied and application-dependent, a few of them might be directly
-     related to how the server was started. Conditions other than
-     those shown below should be documented with the respective client
-     application.
-    </para>
-
-    <para>
-<screen>
-psql: could not connect to server: Connection refused
-        Is the server running on host "server.joe.com" and accepting
-        TCP/IP connections on port 5432?
-</screen>
-     This is the generic <quote>I couldn't find a server to talk
-     to</quote> failure. It looks like the above when TCP/IP
-     communication is attempted. A common mistake is to forget to
-     configure the server to allow TCP/IP connections.
-    </para>
-
-    <para>
-     Alternatively, you'll get this when attempting Unix-domain socket
-     communication to a local server:
-<screen>
-psql: could not connect to server: No such file or directory
-        Is the server running locally and accepting
-        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
-</screen>
-    </para>
-
-    <para>
-     The last line is useful in verifying that the client is trying to
-     connect to the right place. If there is in fact no server
-     running there, the kernel error message will typically be either
-     <computeroutput>Connection refused</computeroutput> or
-     <computeroutput>No such file or directory</computeroutput>, as
-     illustrated. (It is important to realize that
-     <computeroutput>Connection refused</computeroutput> in this context
-     does <emphasis>not</emphasis> mean that the server got your
-     connection request and rejected it. That case will produce a
-     different message, as shown in <xref
-     linkend="client-authentication-problems">.) Other error messages
-     such as <computeroutput>Connection timed out</computeroutput> might
-     indicate more fundamental problems, like lack of network
-     connectivity.
-    </para>
-   </sect2>
-  </sect1>
-
- <sect1 id="kernel-resources">
-  <title>Managing Kernel Resources</title>
-&common;
-  <para>
-<!## PG>
-   A large <productname>PostgreSQL</> installation can quickly exhaust
-<!## end>
-<!## XC>
-   A large <productname>Postgres-XC</> installation can quickly exhaust
-<!## end>
-<!## XL>
-   A large <productname>Postgres-XL</> installation can quickly exhaust
-<!## end>
-   various operating system resource limits. (On some systems, the
-   factory defaults are so low that you don't even need a really
-   <quote>large</> installation.) If you have encountered this kind of
-   problem, keep reading.
-  </para>
-
-  <sect2 id="sysvipc">
-   <title>Shared Memory and Semaphores</title>
-&common;
-   <indexterm zone="sysvipc">
-    <primary>shared memory</primary>
-   </indexterm>
-
-   <indexterm zone="sysvipc">
-    <primary>semaphores</primary>
-   </indexterm>
-
-   <para>
-    Shared memory and semaphores are collectively referred to as
-    <quote><systemitem class="osname">System V</>
-    <acronym>IPC</></quote> (together with message queues, which are not
-<!## PG>
-    relevant for <productname>PostgreSQL</>). Almost all modern
-<!## end>
-<!## XC>
-    relevant for <productname>Postgres-XC</>). Almost all modern
-<!## end>
-<!## XL>
-    relevant for <productname>Postgres-XL</>). Almost all modern
-<!## end>
-    operating systems provide these features, but many of them don't have
-    them turned on or sufficiently sized by default, especially as
-    available RAM and the demands of database applications grow.
-    (On <systemitem class="osname">Windows</>,
-<!## PG>
-    <productname>PostgreSQL</> provides its own replacement
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> provides its own replacement
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> provides its own replacement
-<!## end>
-    implementation of these facilities, so most of this section
-    can be disregarded.)
-   </para>
-
-   <para>
-    The complete lack of these facilities is usually manifested by an
-    <errorname>Illegal system call</> error upon server start. In
-    that case there is no alternative but to reconfigure your
-<!## PG>
-    kernel.  <productname>PostgreSQL</> won't work without them.
-<!## end>
-<!## XC>
-    kernel.  <productname>Postgres-XC</> won't work without them.
-<!## end>
-<!## XL>
-    kernel.  <productname>Postgres-XL</> won't work without them.
-<!## end>
-    This situation is rare, however, among modern operating systems.
-   </para>
-
-   <para>
-<!## PG>
-    When <productname>PostgreSQL</> exceeds one of the various hard
-<!## end>
-<!## XC>
-    When <productname>Postgres-XC</> exceeds one of the various hard
-<!## end>
-<!## XL>
-    When <productname>Postgres-XL</> exceeds one of the various hard
-<!## end>
-    <acronym>IPC</> limits, the server will refuse to start and
-    should leave an instructive error message describing the problem
-    and what to do about it. (See also <xref
-    linkend="server-start-failures">.) The relevant kernel
-    parameters are named consistently across different systems; <xref
-    linkend="sysvipc-parameters"> gives an overview. The methods to set
-    them, however, vary. Suggestions for some platforms are given below.
-   </para>
-
-
-   <table id="sysvipc-parameters">
-    <title><systemitem class="osname">System V</> <acronym>IPC</> Parameters</title>
-
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Name</>
-       <entry>Description</>
-       <entry>Reasonable values</>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><varname>SHMMAX</></>
-       <entry>Maximum size of shared memory segment (bytes)</>
-       <entry>at least several megabytes (see text)</entry>
-      </row>
-
-      <row>
-       <entry><varname>SHMMIN</></>
-       <entry>Minimum size of shared memory segment (bytes)</>
-       <entry>1</>
-      </row>
-
-      <row>
-       <entry><varname>SHMALL</></>
-       <entry>Total amount of shared memory available (bytes or pages)</>
-       <entry>if bytes, same as <varname>SHMMAX</varname>; if pages, <literal>ceil(SHMMAX/PAGE_SIZE)</literal></>
-      </row>
-
-      <row>
-       <entry><varname>SHMSEG</></>
-       <entry>Maximum number of shared memory segments per process</>
-       <entry>only 1 segment is needed, but the default is much higher</>
-      </row>
-
-       <row>
-        <entry><varname>SHMMNI</></>
-        <entry>Maximum number of shared memory segments system-wide</>
-        <entry>like <varname>SHMSEG</> plus room for other applications</>
-       </row>
-
-       <row>
-        <entry><varname>SEMMNI</></>
-        <entry>Maximum number of semaphore identifiers (i.e., sets)</>
-        <entry>at least <literal>ceil((max_connections + autovacuum_max_workers) / 16)</literal></>
-       </row>
-
-       <row>
-        <entry><varname>SEMMNS</></>
-        <entry>Maximum number of semaphores system-wide</>
-        <entry><literal>ceil((max_connections + autovacuum_max_workers) / 16) * 17</literal> plus room for other applications</>
-       </row>
-
-       <row>
-        <entry><varname>SEMMSL</></>
-        <entry>Maximum number of semaphores per set</>
-        <entry>at least 17</>
-       </row>
-
-       <row>
-        <entry><varname>SEMMAP</></>
-        <entry>Number of entries in semaphore map</>
-        <entry>see text</>
-       </row>
-
-       <row>
-        <entry><varname>SEMVMX</></>
-        <entry>Maximum value of semaphore</>
-        <entry>at least 1000 (The default is often 32767; do not change unless necessary)</>
-       </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-
-   <para>
-    <indexterm><primary>SHMMAX</primary></indexterm> The most important
-    shared memory parameter is <varname>SHMMAX</>, the maximum size, in
-    bytes, of a shared memory segment. If you get an error message from
-    <function>shmget</> like <quote>Invalid argument</>, it is
-    likely that this limit has been exceeded.  The size of the required
-    shared memory segment varies depending on several
-<!## PG>
-    <productname>PostgreSQL</> configuration parameters, as shown in
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> configuration parameters, as shown in
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> configuration parameters, as shown in
-<!## end>
-    <xref linkend="shared-memory-parameters">.  (Any error message you might
-    get will include the exact size of the failed allocation request.)
-    You can, as a temporary solution, lower some of those settings to
-    avoid the failure.  While it is possible to get
-<!## PG>
-    <productname>PostgreSQL</> to run with <varname>SHMMAX</> as small as
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> to run with <varname>SHMMAX</> as small as
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> to run with <varname>SHMMAX</> as small as
-<!## end>
-    2 MB, you need considerably more for acceptable performance.  Desirable
-    settings are in the hundreds of megabytes to a few gigabytes.
-   </para>
-
-   <para>
-    Some systems also have a limit on the total amount of shared memory in
-    the system (<varname>SHMALL</>).  Make sure this is large enough
-<!## PG>
-    for <productname>PostgreSQL</> plus any other applications that
-<!## end>
-<!## XC>
-    for <productname>Postgres-XC</> plus any other applications that
-<!## end>
-<!## XL>
-    for <productname>Postgres-XL</> plus any other applications that
-<!## end>
-    are using shared memory segments.  Note that <varname>SHMALL</>
-    is measured in pages rather than bytes on many systems.
-   </para>
-
-   <para>
-    Less likely to cause problems is the minimum size for shared
-    memory segments (<varname>SHMMIN</>), which should be at most
-<!## PG>
-    approximately 500 kB for <productname>PostgreSQL</> (it is
-<!## end>
-<!## XC>
-    approximately 500 kB for <productname>Postgres-XC</> (it is
-<!## end>
-<!## XL>
-    approximately 500 kB for <productname>Postgres-XL</> (it is
-<!## end>
-    usually just 1). The maximum number of segments system-wide
-    (<varname>SHMMNI</>) or per-process (<varname>SHMSEG</>) are unlikely
-    to cause a problem unless your system has them set to zero.
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</> uses one semaphore per allowed connection
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> uses one semaphore per allowed connection
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> uses one semaphore per allowed connection
-<!## end>
-    (<xref linkend="guc-max-connections">) and allowed autovacuum worker
-    process (<xref linkend="guc-autovacuum-max-workers">), in sets of 16.
-    Each such set will
-    also contain a 17th semaphore which contains a <quote>magic
-    number</quote>, to detect collision with semaphore sets used by
-    other applications. The maximum number of semaphores in the system
-    is set by <varname>SEMMNS</>, which consequently must be at least
-    as high as <varname>max_connections</> plus
-    <varname>autovacuum_max_workers</>, plus one extra for each 16
-    allowed connections plus workers (see the formula in <xref
-    linkend="sysvipc-parameters">).  The parameter <varname>SEMMNI</>
-    determines the limit on the number of semaphore sets that can
-    exist on the system at one time.  Hence this parameter must be at
-    least <literal>ceil((max_connections + autovacuum_max_workers) / 16)</>.
-    Lowering the number
-    of allowed connections is a temporary workaround for failures,
-    which are usually confusingly worded <quote>No space
-    left on device</>, from the function <function>semget</>.
-   </para>
-
-   <para>
-    In some cases it might also be necessary to increase
-    <varname>SEMMAP</> to be at least on the order of
-    <varname>SEMMNS</>. This parameter defines the size of the semaphore
-    resource map, in which each contiguous block of available semaphores
-    needs an entry. When a semaphore set is freed it is either added to
-    an existing entry that is adjacent to the freed block or it is
-    registered under a new map entry. If the map is full, the freed
-    semaphores get lost (until reboot). Fragmentation of the semaphore
-    space could over time lead to fewer available semaphores than there
-    should be.
-   </para>
-
-   <para>
-    The <varname>SEMMSL</> parameter, which determines how many
-    semaphores can be in a set, must be at least 17 for
-<!## PG>
-    <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</>.
-<!## end>
-   </para>
-
-   <para>
-    Various other settings related to <quote>semaphore undo</>, such as
-    <varname>SEMMNU</> and <varname>SEMUME</>, do not affect
-<!## PG>
-    <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</>.
-<!## end>
-   </para>
-
-
-    <variablelist>
-     <varlistentry>
-      <term><systemitem class="osname">AIX</></term>
-      <indexterm><primary>AIX</><secondary>IPC configuration</></>
-      <listitem>
-       <para>
-        At least as of version 5.1, it should not be necessary to do
-        any special configuration for such parameters as
-        <varname>SHMMAX</varname>, as it appears this is configured to
-        allow all memory to be used as shared memory.  That is the
-        sort of configuration commonly used for other databases such
-        as <application>DB/2</application>.</para>
-
-       <para> It might, however, be necessary to modify the global
-       <command>ulimit</command> information in
-       <filename>/etc/security/limits</filename>, as the default hard
-       limits for file sizes (<varname>fsize</varname>) and numbers of
-       files (<varname>nofiles</varname>) might be too low.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><systemitem class="osname">BSD/OS</></term>
-      <indexterm><primary>BSD/OS</><secondary>IPC configuration</></>
-      <listitem>
-       <formalpara>
-        <title>Shared Memory</title>
-        <para>
-         By default, only 4 MB of shared memory is supported. Keep in
-         mind that shared memory is not pageable; it is locked in RAM.
-         To increase the amount of shared memory supported by your
-         system, add something like the following to your kernel configuration
-         file:
-<programlisting>
-options "SHMALL=8192"
-options "SHMMAX=\(SHMALL*PAGE_SIZE\)"
-</programlisting>
-         <varname>SHMALL</> is measured in 4 kB pages, so a value of
-         1024 represents 4 MB of shared memory. Therefore the above increases
-         the maximum shared memory area to 32 MB.
-         For those running 4.3 or later, you will probably also need to increase
-         <varname>KERNEL_VIRTUAL_MB</> above the default <literal>248</>.
-         Once all changes have been made, recompile the kernel, and reboot.
-        </para>
-       </formalpara>
-
-       <formalpara>
-        <title>Semaphores</title>
-        <para>
-         You will probably want to increase the number of semaphores
-         as well; the default system total of 60 will only allow about
-<!## PG>
-         50 <productname>PostgreSQL</productname> connections.  Set the
-<!## end>
-<!## XC>
-         50 <productname>Postgres-XC</productname> connections.  Set the
-<!## end>
-<!## XL>
-         50 <productname>Postgres-XL</productname> connections.  Set the
-<!## end>
-         values you want in your kernel configuration file, e.g.:
-<programlisting>
-options "SEMMNI=40"
-options "SEMMNS=240"
-</programlisting>
-        </para>
-       </formalpara>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">FreeBSD</></term>
-      <indexterm><primary>FreeBSD</><secondary>IPC configuration</></>
-      <listitem>
-       <para>
-        The default settings are only suitable for small installations
-        (for example, default <varname>SHMMAX</varname> is 32
-        MB). Changes can be made via the <command>sysctl</command> or
-        <command>loader</command> interfaces.  The following
-        parameters can be set using <command>sysctl</command>:
-<screen>
-<prompt>$</prompt> <userinput>sysctl -w kern.ipc.shmall=32768</userinput>
-<prompt>$</prompt> <userinput>sysctl -w kern.ipc.shmmax=134217728</userinput>
-<prompt>$</prompt> <userinput>sysctl -w kern.ipc.semmap=256</userinput>
-</screen>
-        To have these settings persist over reboots, modify
-        <filename>/etc/sysctl.conf</filename>.
-       </para>
-
-       <para>
-        The remaining semaphore settings are read-only as far as
-        <command>sysctl</command> is concerned, but can be changed
-        before boot using the <command>loader</command> prompt:
-<screen>
-<prompt>(loader)</prompt> <userinput>set kern.ipc.semmni=256</userinput>
-<prompt>(loader)</prompt> <userinput>set kern.ipc.semmns=512</userinput>
-<prompt>(loader)</prompt> <userinput>set kern.ipc.semmnu=256</userinput>
-</screen>
-        Similarly these can be saved between reboots in
-        <filename>/boot/loader.conf</filename>.
-       </para>
-
-       <para>
-        You might also want to configure your kernel to lock shared
-        memory into RAM and prevent it from being paged out to swap.
-        This can be accomplished using the <command>sysctl</command>
-        setting <literal>kern.ipc.shm_use_phys</literal>.
-       </para>
-
-       <para>
-        If running in FreeBSD jails by enabling <application>sysctl</>'s
-        <literal>security.jail.sysvipc_allowed</>, <application>postmaster</>s
-        running in different jails should be run by different operating system
-        users.  This improves security because it prevents non-root users
-        from interfering with shared memory or semaphores in different jails,
-<!## PG>
-        and it allows the PostgreSQL IPC cleanup code to function properly.
-<!## end>
-<!## XC>
-        and it allows the Postgres-XC IPC cleanup code to function properly.
-<!## end>
-<!## XL>
-        and it allows the Postgres-XL IPC cleanup code to function properly.
-<!## end>
-        (In FreeBSD 6.0 and later the IPC cleanup code does not properly detect
-        processes in other jails, preventing the running of postmasters on the
-        same port in different jails.)
-       </para>
-
-       <para>
-        <systemitem class="osname">FreeBSD</> versions before 4.0 work like
-        <systemitem class="osname">NetBSD</> and <systemitem class="osname">
-        OpenBSD</> (see below).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><systemitem class="osname">NetBSD</></term>
-      <term><systemitem class="osname">OpenBSD</></term>
-      <indexterm><primary>NetBSD</><secondary>IPC configuration</></>
-      <indexterm><primary>OpenBSD</><secondary>IPC configuration</></>
-      <listitem>
-       <para>
-        The options <varname>SYSVSHM</> and <varname>SYSVSEM</> need
-        to be enabled when the kernel is compiled. (They are by
-        default.) The maximum size of shared memory is determined by
-        the option <varname>SHMMAXPGS</> (in pages). The following
-        shows an example of how to set the various parameters on
-        <systemitem class="osname">NetBSD</>
-        (<systemitem class="osname">OpenBSD</> uses <literal>option</> instead):
-<programlisting>
-options        SYSVSHM
-options        SHMMAXPGS=4096
-options        SHMSEG=256
-
-options        SYSVSEM
-options        SEMMNI=256
-options        SEMMNS=512
-options        SEMMNU=256
-options        SEMMAP=256
-</programlisting>
-       </para>
-
-       <para>
-        You might also want to configure your kernel to lock shared
-        memory into RAM and prevent it from being paged out to swap.
-        This can be accomplished using the <command>sysctl</command>
-        setting <literal>kern.ipc.shm_use_phys</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">HP-UX</></term>
-      <indexterm><primary>HP-UX</><secondary>IPC configuration</></>
-      <listitem>
-       <para>
-        The default settings tend to suffice for normal installations.
-        On <productname>HP-UX</> 10, the factory default for
-        <varname>SEMMNS</> is 128, which might be too low for larger
-        database sites.
-       </para>
-       <para>
-        <acronym>IPC</> parameters can be set in the <application>System
-        Administration Manager</> (<acronym>SAM</>) under
-        <menuchoice><guimenu>Kernel
-        Configuration</><guimenuitem>Configurable Parameters</></>. Choose
-        <guibutton>Create A New Kernel</> when you're done.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">Linux</></term>
-      <indexterm><primary>Linux</><secondary>IPC configuration</></>
-      <listitem>
-       <para>
-        The default maximum segment size is 32 MB, which is only adequate
-<!## PG>
-        for very small <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-        for very small <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-        for very small <productname>Postgres-XL</productname>
-<!## end>
-        installations.  The default maximum total size is 2097152
-        pages.  A page is almost always 4096 bytes except in unusual
-        kernel configurations with <quote>huge pages</quote>
-        (use <literal>getconf PAGE_SIZE</literal> to verify).  That
-        makes a default limit of 8 GB, which is often enough, but not
-        always.
-       </para>
-
-       <para>
-        The shared memory size settings can be changed via the
-        <command>sysctl</command> interface.  For example, to allow 16 GB:
-<screen>
-<prompt>$</prompt> <userinput>sysctl -w kernel.shmmax=17179869184</userinput>
-<prompt>$</prompt> <userinput>sysctl -w kernel.shmall=4194304</userinput>
-</screen>
-        In addition these settings can be preserved between reboots in
-        the file <filename>/etc/sysctl.conf</filename>.  Doing that is
-        highly recommended.
-       </para>
-
-       <para>
-        Ancient distributions might not have the <command>sysctl</command> program,
-        but equivalent changes can be made by manipulating the
-        <filename>/proc</filename> file system:
-<screen>
-<prompt>$</prompt> <userinput>echo 17179869184 &gt;/proc/sys/kernel/shmmax</userinput>
-<prompt>$</prompt> <userinput>echo 4194304 &gt;/proc/sys/kernel/shmall</userinput>
-</screen>
-       </para>
-
-       <para>
-        The remaining defaults are quite generously sized, and usually
-        do not require changes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">MacOS X</></term>
-      <indexterm><primary>MacOS X</><secondary>IPC configuration</></>
-      <listitem>
-       <para>
-        The recommended method for configuring shared memory in OS X
-        is to create a file named <filename>/etc/sysctl.conf</>,
-        containing variable assignments such as:
-<programlisting>
-kern.sysv.shmmax=4194304
-kern.sysv.shmmin=1
-kern.sysv.shmmni=32
-kern.sysv.shmseg=8
-kern.sysv.shmall=1024
-</programlisting>
-        Note that in some OS X versions,
-        <emphasis>all five</> shared-memory parameters must be set in
-        <filename>/etc/sysctl.conf</>, else the values will be ignored.
-       </para>
-
-       <para>
-        Beware that recent releases of OS X ignore attempts to set
-        <varname>SHMMAX</> to a value that isn't an exact multiple of 4096.
-       </para>
-
-       <para>
-        <varname>SHMALL</> is measured in 4 kB pages on this platform.
-       </para>
-
-       <para>
-        In older OS X versions, you will need to reboot to have changes in the
-        shared memory parameters take effect.  As of 10.5 it is possible to
-        change all but <varname>SHMMNI</> on the fly, using
-        <application>sysctl</>.  But it's still best to set up your preferred
-        values via <filename>/etc/sysctl.conf</>, so that the values will be
-        kept across reboots.
-       </para>
-
-       <para>
-        The file <filename>/etc/sysctl.conf</> is only honored in OS X
-        10.3.9 and later.  If you are running a previous 10.3.x release,
-        you must edit the file <filename>/etc/rc</>
-        and change the values in the following commands:
-<programlisting>
-sysctl -w kern.sysv.shmmax
-sysctl -w kern.sysv.shmmin
-sysctl -w kern.sysv.shmmni
-sysctl -w kern.sysv.shmseg
-sysctl -w kern.sysv.shmall
-</programlisting>
-        Note that
-        <filename>/etc/rc</> is usually overwritten by OS X system updates,
-        so you should expect to have to redo these edits after each update.
-       </para>
-
-       <para>
-        In OS X 10.2 and earlier, instead edit these commands in the file
-        <filename>/System/Library/StartupItems/SystemTuning/SystemTuning</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">SCO OpenServer</></term>
-      <indexterm><primary>SCO OpenServer</><secondary>IPC configuration</></>
-      <listitem>
-       <para>
-        In the default configuration, only 512 kB of shared memory per
-        segment is allowed. To increase the setting, first change to the
-        directory <filename>/etc/conf/cf.d</>. To display the current value of
-        <varname>SHMMAX</>, run:
-<programlisting>
-./configure -y SHMMAX
-</programlisting>
-        To set a new value for <varname>SHMMAX</>, run:
-<programlisting>
-./configure SHMMAX=<replaceable>value</>
-</programlisting>
-        where <replaceable>value</> is the new value you want to use
-        (in bytes). After setting <varname>SHMMAX</>, rebuild the kernel:
-<programlisting>
-./link_unix
-</programlisting>
-        and reboot.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">Solaris</> 2.6 to 2.9 (Solaris
-      6 to Solaris 9)</term>
-      <indexterm><primary>Solaris</><secondary>IPC configuration</></>
-      <listitem>
-       <para>
-        The default maximum size of a shared memory segment is too low for
-<!## PG>
-        <productname>PostgreSQL</>. The relevant settings can be changed in
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</>. The relevant settings can be changed in
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</>. The relevant settings can be changed in
-<!## end>
-        <filename>/etc/system</>, for example:
-<programlisting>
-set shmsys:shminfo_shmmax=0x2000000
-set shmsys:shminfo_shmmin=1
-set shmsys:shminfo_shmmni=256
-set shmsys:shminfo_shmseg=256
-
-set semsys:seminfo_semmap=256
-set semsys:seminfo_semmni=512
-set semsys:seminfo_semmns=512
-set semsys:seminfo_semmsl=32
-</programlisting>
-        You need to reboot for the changes to take effect.  See also
-        <ulink url="http://sunsite.uakom.sk/sunworldonline/swol-09-1997/swol-09-insidesolaris.html"></ulink>
-        for information on shared memory under older versions of Solaris.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><systemitem class="osname">Solaris</> 2.10 (Solaris
-      10)</term>
-      <term><systemitem class="osname">OpenSolaris</></term>
-      <listitem>
-       <para>
-        In Solaris 10 and OpenSolaris, the default shared memory and
-        semaphore settings are good enough for most
-        <productname>PostgreSQL</> applications.  Solaris now defaults
-        to a <varname>SHMMAX</> of one-quarter of system <acronym>RAM</>.  If
-        you need to increase this in order to set shared memory settings
-        slightly higher, you should use a project setting associated
-        with the <literal>postgres</> user.  For example, run the
-        following as <literal>root</>:
-<programlisting>
-projadd -c "PostgreSQL DB User" -K "project.max-shm-memory=(privileged,8GB,deny)" -U postgres -G postgres user.postgres
-</programlisting>
-       </para>
-
-       <para>
-        This command adds the <literal>user.postgres</> project and
-        raises the shared memory maximum for the <literal>postgres</>
-        user to 8GB, and takes effect the next time that user logs
-        in, or when you restart <productname>PostgreSQL</> (not reload).
-        The above assumes that <productname>PostgreSQL</> is run by
-        the <literal>postgres</> user in the <literal>postgres</>
-        group.  No server reboot is required.
-       </para>
-
-       <para>
-        Other recommended kernel setting changes for database servers which will
-        have a large number of connections are:
-<programlisting>
-project.max-shm-ids=(priv,32768,deny)
-project.max-sem-ids=(priv,4096,deny)
-project.max-msg-ids=(priv,4096,deny)
-</programlisting>
-       </para>
-
-       <para>
-        Additionally, if you are running <productname>PostgreSQL</>
-        inside a zone, you may need to raise the zone resource usage
-        limits as well.  See "Chapter2:  Projects and Tasks" in the
-        <citetitle>Solaris 10 System Administrator's Guide</> for more
-        information on <literal>projects</> and <command>prctl</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">UnixWare</></term>
-      <indexterm><primary>UnixWare</><secondary>IPC configuration</></>
-      <listitem>
-       <para>
-        On <productname>UnixWare</> 7, the maximum size for shared
-        memory segments is only 512 kB in the default configuration.
-        To display the current value of <varname>SHMMAX</>, run:
-<programlisting>
-/etc/conf/bin/idtune -g SHMMAX
-</programlisting>
-        which displays the current, default, minimum, and maximum
-        values. To set a new value for <varname>SHMMAX</>,
-        run:
-<programlisting>
-/etc/conf/bin/idtune SHMMAX <replaceable>value</>
-</programlisting>
-        where <replaceable>value</> is the new value you want to use
-        (in bytes). After setting <varname>SHMMAX</>, rebuild the
-        kernel:
-<programlisting>
-/etc/conf/bin/idbuild -B
-</programlisting>
-        and reboot.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-
-   <table id="shared-memory-parameters">
-<!## PG>
-    <title><productname>PostgreSQL</productname> Shared Memory Usage</>
-<!## end>
-<!## XC>
-    <title><productname>Postgres-XC</productname> Shared Memory Usage</>
-<!## end>
-<!## XL>
-    <title><productname>Postgres-XL</productname> Shared Memory Usage</>
-<!## end>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Usage</>
-       <entry>Approximate shared memory bytes required (as of 8.3)</>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry>Connections</>
-       <entry>(1800 + 270 * <xref
-       linkend="guc-max-locks-per-transaction">) * <xref
-       linkend="guc-max-connections"></entry>
-      </row>
-
-      <row>
-       <entry>Autovacuum workers</>
-       <entry>(1800 + 270 * <xref
-       linkend="guc-max-locks-per-transaction">) * <xref
-       linkend="guc-autovacuum-max-workers"></entry>
-      </row>
-
-      <row>
-       <entry>Prepared transactions</>
-       <entry>(770 + 270 * <xref
-       linkend="guc-max-locks-per-transaction">) * <xref linkend="guc-max-prepared-transactions"></entry>
-      </row>
-
-      <row>
-       <entry>Shared disk buffers</>
-       <entry>(<xref linkend="guc-block-size"> + 208) * <xref linkend="guc-shared-buffers"></entry>
-      </row>
-
-      <row>
-       <entry>WAL buffers</>
-       <entry>(<xref linkend="guc-wal-block-size"> + 8) * <xref linkend="guc-wal-buffers"></entry>
-      </row>
-
-      <row>
-       <entry>Fixed space requirements</>
-       <entry>770 kB</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  </sect2>
-
-  <sect2>
-   <title>Resource Limits</title>
-&common;
-   <para>
-    Unix-like operating systems enforce various kinds of resource limits
-    that might interfere with the operation of your
-<!## PG>
-    <productname>PostgreSQL</productname> server. Of particular
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> server. Of particular
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> server. Of particular
-<!## end>
-    importance are limits on the number of processes per user, the
-    number of open files per process, and the amount of memory available
-    to each process. Each of these have a <quote>hard</quote> and a
-    <quote>soft</quote> limit. The soft limit is what actually counts
-    but it can be changed by the user up to the hard limit. The hard
-    limit can only be changed by the root user. The system call
-    <function>setrlimit</function> is responsible for setting these
-    parameters. The shell's built-in command <command>ulimit</command>
-    (Bourne shells) or <command>limit</command> (<application>csh</>) is
-    used to control the resource limits from the command line. On
-    BSD-derived systems the file <filename>/etc/login.conf</filename>
-    controls the various resource limits set during login. See the
-    operating system documentation for details. The relevant
-    parameters are <varname>maxproc</varname>,
-    <varname>openfiles</varname>, and <varname>datasize</varname>. For
-    example:
-<programlisting>
-default:\
-...
-        :datasize-cur=256M:\
-        :maxproc-cur=256:\
-        :openfiles-cur=256:\
-...
-</programlisting>
-    (<literal>-cur</literal> is the soft limit.  Append
-    <literal>-max</literal> to set the hard limit.)
-   </para>
-
-   <para>
-    Kernels can also have system-wide limits on some resources.
-    <itemizedlist>
-     <listitem>
-      <para>
-      On <productname>Linux</productname>
-      <filename>/proc/sys/fs/file-max</filename> determines the
-      maximum number of open files that the kernel will support.  It can
-      be changed by writing a different number into the file or by
-      adding an assignment in <filename>/etc/sysctl.conf</filename>.
-      The maximum limit of files per process is fixed at the time the
-      kernel is compiled; see
-      <filename>/usr/src/linux/Documentation/proc.txt</filename> for
-      more information.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-<!## PG>
-    The <productname>PostgreSQL</productname> server uses one process
-<!## end>
-<!## XC>
-    The <productname>Postgres-XC</productname> server uses one process
-<!## end>
-<!## XL>
-    The <productname>Postgres-XL</productname> server uses one process
-<!## end>
-    per connection so you should provide for at least as many processes
-    as allowed connections, in addition to what you need for the rest
-    of your system.  This is usually not a problem but if you run
-    several servers on one machine things might get tight.
-   </para>
-
-   <para>
-    The factory default limit on open files is often set to
-    <quote>socially friendly</quote> values that allow many users to
-    coexist on a machine without using an inappropriate fraction of
-    the system resources.  If you run many servers on a machine this
-    is perhaps what you want, but on dedicated servers you might want to
-    raise this limit.
-   </para>
-
-   <para>
-    On the other side of the coin, some systems allow individual
-    processes to open large numbers of files; if more than a few
-    processes do so then the system-wide limit can easily be exceeded.
-    If you find this happening, and you do not want to alter the
-<!## PG>
-    system-wide limit, you can set <productname>PostgreSQL</>'s <xref
-<!## end>
-<!## XC>
-    system-wide limit, you can set <productname>Postgres-XC</>'s <xref
-<!## end>
-<!## XL>
-    system-wide limit, you can set <productname>Postgres-XL</>'s <xref
-<!## end>
-    linkend="guc-max-files-per-process"> configuration parameter to
-    limit the consumption of open files.
-   </para>
-  </sect2>
-
-  <sect2 id="linux-memory-overcommit">
-   <title>Linux Memory Overcommit</title>
-&common;
-   <para>
-    In Linux 2.4 and later, the default virtual memory behavior is not
-<!## PG>
-    optimal for <productname>PostgreSQL</productname>. Because of the
-<!## end>
-<!## XC>
-    optimal for <productname>Postgres-XC</productname>. Because of the
-<!## end>
-<!## XL>
-    optimal for <productname>Postgres-XL</productname>. Because of the
-<!## end>
-    way that the kernel implements memory overcommit, the kernel might
-<!## PG>
-    terminate the <productname>PostgreSQL</productname> server (the
-<!## end>
-<!## XC>
-    terminate the <productname>Postgres-XC</productname> server (the
-<!## end>
-<!## XL>
-    terminate the <productname>Postgres-XL</productname> server (the
-<!## end>
-    master server process) if the memory demands of
-    another process cause the system to run out of virtual memory.
-   </para>
-
-   <para>
-    If this happens, you will see a kernel message that looks like
-    this (consult your system documentation and configuration on where
-    to look for such a message):
-<programlisting>
-Out of Memory: Killed process 12345 (postgres).
-</programlisting>
-    This indicates that the <filename>postgres</filename> process
-    has been terminated due to memory pressure.
-    Although existing database connections will continue to function
-    normally, no new connections will be accepted.  To recover,
-<!## PG>
-    <productname>PostgreSQL</productname> will need to be restarted.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> will need to be restarted.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> will need to be restarted.
-<!## end>
-   </para>
-
-   <para>
-    One way to avoid this problem is to run
-<!## PG>
-    <productname>PostgreSQL</productname> on a machine where you can
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> on a machine where you can
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> on a machine where you can
-<!## end>
-    be sure that other processes will not run the machine out of
-    memory.  If memory is tight, increasing the swap space of the
-    operating system can help avoid the problem, because the
-    out-of-memory (OOM) killer is invoked only when physical memory and
-    swap space are exhausted.
-   </para>
-
-   <para>
-    On Linux 2.6 and later, it is possible to modify the
-    kernel's behavior so that it will not <quote>overcommit</> memory.
-    Although this setting will not prevent the <ulink
-    url="http://lwn.net/Articles/104179/">OOM killer</> from being invoked
-    altogether, it will lower the chances significantly and will therefore
-    lead to more robust system behavior.  This is done by selecting strict
-    overcommit mode via <command>sysctl</command>:
-<programlisting>
-sysctl -w vm.overcommit_memory=2
-</programlisting>
-    or placing an equivalent entry in <filename>/etc/sysctl.conf</>.
-    You might also wish to modify the related setting
-    <varname>vm.overcommit_ratio</>.  For details see the kernel documentation
-    file <filename>Documentation/vm/overcommit-accounting</>.
-   </para>
-
-   <para>
-    Another approach, which can be used with or without altering
-    <varname>vm.overcommit_memory</>, is to set the process-specific
-    <varname>oom_adj</> value for the postmaster process to <literal>-17</>,
-    thereby guaranteeing it will not be targeted by the OOM killer.  The
-    simplest way to do this is to execute
-<programlisting>
-echo -17 > /proc/self/oom_adj
-</programlisting>
-    in the postmaster's startup script just before invoking the postmaster.
-    Note that this action must be done as root, or it will have no effect;
-    so a root-owned startup script is the easiest place to do it.  If you
-<!## PG>
-    do this, you may also wish to build <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-    do this, you may also wish to build <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-    do this, you may also wish to build <productname>Postgres-XL</>
-<!## end>
-    with <literal>-DLINUX_OOM_ADJ=0</> added to <varname>CFLAGS</>.
-    That will cause postmaster child processes to run with the normal
-    <varname>oom_adj</> value of zero, so that the OOM killer can still
-    target them at need.
-   </para>
-
-   <note>
-   <para>
-    Some vendors' Linux 2.4 kernels are reported to have early versions
-    of the 2.6 overcommit <command>sysctl</command> parameter.  However, setting
-    <literal>vm.overcommit_memory</> to 2
-    on a 2.4 kernel that does not have the relevant code will make
-    things worse, not better.  It is recommended that you inspect
-    the actual kernel source code (see the function
-    <function>vm_enough_memory</> in the file <filename>mm/mmap.c</>)
-    to verify what is supported in your kernel before you try this in a 2.4
-    installation.  The presence of the <filename>overcommit-accounting</>
-    documentation file should <emphasis>not</> be taken as evidence that the
-    feature is there.  If in any doubt, consult a kernel expert or your
-    kernel vendor.
-   </para>
-   </note>
-  </sect2>
- </sect1>
-
-
- <sect1 id="server-shutdown">
-  <title>Shutting Down the Server</title>
-
-  <indexterm zone="server-shutdown">
-   <primary>shutdown</>
-  </indexterm>
-<!## XC>
-&xconly;
-  <para>
-   This section describes how to shutdown each Coordinator and
-   Datanode.
-   Please note that you should shutdown Coordinator first and then
-   Datanodes, GTM-Proxy and GTM.
-  </para>
-
-  <sect2 id="Coordinator-Datanode-shutdown">
-   <title>Shutting Down Coordinators and Datanodes</title>
-
-<!## end>
-<!## XL>
-  <para>
-   This section describes how to shutdown each Coordinator and
-   Datanode.
-   Please note that you should shutdown Coordinator first and then
-   Datanodes, GTM-Proxy and GTM.
-  </para>
-
-  <sect2 id="Coordinator-Datanode-shutdown">
-   <title>Shutting Down Coordinators and Datanodes</title>
-
-<!## end>
-&common;
-  <para>
-   There are several ways to shut down the database server. You control
-   the type of shutdown by sending different signals to the master
-   <command>postgres</command> process.
-
-   <variablelist>
-    <varlistentry>
-     <term><systemitem>SIGTERM</systemitem><indexterm><primary>SIGTERM</></></term>
-     <listitem>
-      <para>
-       This is the <firstterm>Smart Shutdown</firstterm> mode.
-       After receiving <systemitem>SIGTERM</systemitem>, the server
-       disallows new connections, but lets existing sessions end their
-       work normally. It shuts down only after all of the sessions terminate.
-       If the server is in online backup mode, it additionally waits
-       until online backup mode is no longer active.  While backup mode is
-       active, new connections will still be allowed, but only to superusers
-       (this exception allows a superuser to connect to terminate
-       online backup mode).  If the server is in recovery when a smart
-       shutdown is requested, recovery and streaming replication will be
-       stopped only after all regular sessions have terminated.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><systemitem>SIGINT</systemitem><indexterm><primary>SIGINT</></></term>
-     <listitem>
-      <para>
-       This is the <firstterm>Fast Shutdown</firstterm> mode.
-       The server disallows new connections and sends all existing
-       server processes <systemitem>SIGTERM</systemitem>, which will cause them
-       to abort their current transactions and exit promptly. It then
-       waits for all server processes to exit and finally shuts down.
-       If the server is in online backup mode, backup mode will be
-       terminated, rendering the backup useless.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><systemitem>SIGQUIT</systemitem><indexterm><primary>SIGQUIT</></></term>
-     <listitem>
-      <para>
-      This is the <firstterm>Immediate Shutdown</firstterm> mode.
-      The master <command>postgres</command> process will send a
-      <systemitem>SIGQUIT</systemitem> to all child processes and exit
-      immediately, without properly shutting itself down. The child processes
-      likewise exit immediately upon receiving
-      <systemitem>SIGQUIT</systemitem>. This will lead to recovery (by
-      replaying the WAL log) upon next start-up. This is recommended
-      only in emergencies.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   The <xref linkend="app-pg-ctl"> program provides a convenient
-   interface for sending these signals to shut down the server.
-   Alternatively, you can send the signal directly using <command>kill</>
-   on non-Windows systems.
-   The <acronym>PID</> of the <command>postgres</command> process can be
-   found using the <command>ps</command> program, or from the file
-   <filename>postmaster.pid</filename> in the data directory. For
-   example, to do a fast shutdown:
-<screen>
-$ <userinput>kill -INT `head -1 /usr/local/pgsql/data/postmaster.pid`</userinput>
-</screen>
-  </para>
-
-  <important>
-   <para>
-    It is best not to use <systemitem>SIGKILL</systemitem> to shut down
-    the server.  Doing so will prevent the server from releasing
-    shared memory and semaphores, which might then have to be done
-    manually before a new server can be started.  Furthermore,
-    <systemitem>SIGKILL</systemitem> kills the <command>postgres</command>
-    process without letting it relay the signal to its subprocesses,
-    so it will be necessary to kill the individual subprocesses by hand as
-    well.
-   </para>
-  </important>
-
-  <para>
-   To terminate an individual session while allowing other sessions to
-   continue, use <function>pg_terminate_backend()</> (see <xref
-   linkend="functions-admin-signal-table">) or send a
-   <systemitem>SIGTERM</> signal to the child process associated with
-   the session.
-  </para>
- </sect2>
-
-<!## XC>
-
- <sect2 id="shutting-down-gtm-proxy">
-  <title>Shutting Down GTM-Proxies</title>
-
-&common;
-  <para>
-   You can shut down GTM-Proxies by sending SIGKILL, SIGTERM, SIGQUIT,
-   SIGINT or SIGHUP to each GTM-Proxy process.
-   GTM-Proxy process number is recorded in the
-   file <filename>gtm_proxy.pid</> located in each GTM-Proxy's working
-   directory.
-  </para>
-
- </sect2>
-
- <sect2 id="shutting-down-gtm">
-  <title>Shutting Down GTM</title>
-&xconly;
-  <para>
-   You can shut down GTM by sending SIGKILL, SIGTERM, SIGQUIT,
-   SIGINT or SIGHUP to GTM process.
-   GTM process number is recorded in the
-   file <filename>gtm.pid</> located in GTM's working
-   directory.
-  </para>
-
- </sect2>
-
-<!## end>
-<!## XL>
-
- <sect2 id="shutting-down-gtm-proxy">
-  <title>Shutting Down GTM-Proxies</title>
-
-&common;
-  <para>
-   You can shut down GTM-Proxies by sending SIGKILL, SIGTERM, SIGQUIT,
-   SIGINT or SIGHUP to each GTM-Proxy process.
-   GTM-Proxy process number is recorded in the
-   file <filename>gtm_proxy.pid</> located in each GTM-Proxy's working
-   directory.
-  </para>
-
- </sect2>
-
- <sect2 id="shutting-down-gtm">
-  <title>Shutting Down GTM</title>
-&xlonly;
-  <para>
-   You can shut down GTM by sending SIGKILL, SIGTERM, SIGQUIT,
-   SIGINT or SIGHUP to GTM process.
-   GTM process number is recorded in the
-   file <filename>gtm.pid</> located in GTM's working
-   directory.
-  </para>
-
- </sect2>
-
-<!## end>
-
- </sect1>
-
- <sect1 id="upgrading">
-  <title>Upgrading a <productname>PostgreSQL</> Cluster</title>
-
-  <indexterm zone="upgrading">
-   <primary>upgrading</primary>
-  </indexterm>
-
-  <indexterm zone="upgrading">
-   <primary>version</primary>
-   <secondary>compatibility</secondary>
-  </indexterm>
-
-  <para>
-   This section discusses how to upgrade your database data from one
-   <productname>PostgreSQL</> release to a newer one.
-  </para>
-
-<!## XC>
-&xconly;
-  <para>
-   Because <productname>Postgres-XC</>'s Coordinators and Datanodes
-   are essentially <productname>PostgreSQL</> servers, you can follw
-   the steps described below to upgrade each of them.  Please note
-   that you should do this manually.
-  </para>
-<!## end>
-<!## XL>
-  <para>
-   Because <productname>Postgres-XL</>'s Coordinators and Datanodes
-   are essentially <productname>PostgreSQL</> servers, you can follw
-   the steps described below to upgrade each of them.  Please note
-   that you should do this manually.
-  </para>
-<!## end>
-
-  <para>
-   <productname>PostgreSQL</> major versions are represented by the
-   first two digit groups of the version number, e.g., 8.4.
-   <productname>PostgreSQL</> minor versions are represented by the
-   third group of version digits, e.g., 8.4.2 is the second minor
-   release of 8.4.  Minor releases never change the internal storage
-   format and are always compatible with earlier and later minor
-   releases of the same major version number, e.g., 8.4.2 is compatible
-   with 8.4, 8.4.1 and 8.4.6.  To update between compatible versions,
-   you simply replace the executables while the server is down and
-   restart the server.  The data directory remains unchanged &mdash;
-   minor upgrades are that simple.
-  </para>
-
-  <para>
-   For <emphasis>major</> releases of <productname>PostgreSQL</>, the
-   internal data storage format is subject to change, thus complicating
-   upgrades.  The traditional method for moving data to a new major version
-   is to dump and reload the database.  Other methods are available,
-   as discussed below.
-  </para>
-
-  <para>
-<!## PG>
-   New major versions also typically introduce some user-visible
-   incompatibilities, so application programming changes might be required.
-   All user-visible changes are listed in the release notes (<xref
-   linkend="release">);  pay particular attention to the section
-   labeled "Migration".  If you are upgrading across several major
-   versions, be sure to read the release notes for each intervening
-   version.
-<!## end>
-<!## XC>
-<!-- PG release notes are not attached in XC reference -->
-   New major versions also typically introduce some user-visible
-   incompatibilities, so application programming changes might be required.
-   All user-visible changes are listed in the release notes;
-   pay particular attention to the section
-   labeled "Migration".  If you are upgrading across several major
-   versions, be sure to read the release notes for each intervening
-   version.
-<!## end>
-<!## XL>
-<!-- PG release notes are not attached in XL reference -->
-   New major versions also typically introduce some user-visible
-   incompatibilities, so application programming changes might be required.
-   All user-visible changes are listed in the release notes;
-   pay particular attention to the section
-   labeled "Migration".  If you are upgrading across several major
-   versions, be sure to read the release notes for each intervening
-   version.
-<!## end>
-  </para>
-
-  <para>
-   Cautious users will want to test their client applications on the new
-   version before switching over fully; therefore, it's often a good idea to
-   set up concurrent installations of old and new versions.  When
-   testing a <productname>PostgreSQL</> major upgrade, consider the
-   following categories of possible changes:
-  </para>
-
-  <variablelist>
-
-   <varlistentry>
-    <term>Administration</term>
-    <listitem>
-     <para>
-      The capabilities available for administrators to monitor and control
-      the server often change and improve in each major release.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>SQL</term>
-    <listitem>
-     <para>
-      Typically this includes new SQL command capabilities and not changes
-      in behavior, unless specifically mentioned in the release notes.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Library API</term>
-    <listitem>
-     <para>
-      Typically libraries like <application>libpq</> only add new
-      functionality, again unless mentioned in the release notes.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>System Catalogs</term>
-    <listitem>
-     <para>
-      System catalog changes usually only affect database management tools.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Server C-language API</term>
-    <listitem>
-     <para>
-      This involves changes in the backend function API, which is written
-      in the C programming language.  Such changes affect code that
-      references backend functions deep inside the server.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
-  <sect2 id="upgrade-methods-pgdump">
-   <title>Upgrading Data via <application>pg_dump</></title>
-
-   <para>
-    To dump data from one major version of <productname>PostgreSQL</> and
-    reload it in another, you must use <application>pg_dump</>; file system
-    level backup methods will not work. (There are checks in place that prevent
-    you from using a data directory with an incompatible version of
-    <productname>PostgreSQL</productname>, so no great harm can be done by
-    trying to start the wrong server version on a data directory.)
-   </para>
-
-   <para>
-    It is recommended that you use the <application>pg_dump</> and
-    <application>pg_dumpall</> programs from the newer version of
-    <productname>PostgreSQL</>, to take advantage of enhancements
-    that might have been made in these programs.  Current releases of the
-    dump programs can read data from any server version back to 7.0.
-   </para>
-
-   <para>
-    These instructions assume that your existing installation is under the
-    <filename>/usr/local/pgsql</> directory, and that the data area is in
-    <filename>/usr/local/pgsql/data</>.  Substitute your paths
-    appropriately.
-   </para>
-
-   <procedure>
-    <step>
-     <para>
-      If making a backup, make sure that your database is not being updated.
-      This does not affect the integrity of the backup, but the changed
-      data would of course not be included. If necessary, edit the
-      permissions in the file <filename>/usr/local/pgsql/data/pg_hba.conf</>
-      (or equivalent) to disallow access from everyone except you.
-      See <xref linkend="client-authentication"> for additional information on
-      access control.
-     </para>
-
-     <para>
-      <indexterm>
-       <primary>pg_dumpall</primary>
-       <secondary>use during upgrade</secondary>
-      </indexterm>
-
-      To back up your database installation, type:
-<screen>
-<userinput>pg_dumpall &gt; <replaceable>outputfile</></userinput>
-</screen>
-      If you need to preserve OIDs (such as when using them as
-      foreign keys), then use the <option>-o</option> option when running
-      <application>pg_dumpall</>.
-     </para>
-
-     <para>
-      To make the backup, you can use the <application>pg_dumpall</application>
-      command from the version you are currently running.  For best
-      results, however, try to use the <application>pg_dumpall</application>
-      command from <productname>PostgreSQL</productname> &version;,
-      since this version contains bug fixes and improvements over older
-      versions.  While this advice might seem idiosyncratic since you
-      haven't installed the new version yet, it is advisable to follow
-      it if you plan to install the new version in parallel with the
-      old version.  In that case you can complete the installation
-      normally and transfer the data later.  This will also decrease
-      the downtime.
-     </para>
-    </step>
-
-    <step>
-     <para>
-      Shut down the old server:
-<screen>
-<userinput>pg_ctl stop</>
-</screen>
-      On systems that have <productname>PostgreSQL</> started at boot time,
-      there is probably a start-up file that will accomplish the same thing. For
-      example, on a <systemitem class="osname">Red Hat Linux</> system one
-      might find that this works:
-<screen>
-<userinput>/etc/rc.d/init.d/postgresql stop</userinput>
-</screen>
-      See <xref linkend="runtime"> for details about starting and
-      stopping the server.
-     </para>
-    </step>
-
-    <step>
-     <para>
-      If restoring from backup, rename or delete the old installation
-      directory.  It is a good idea to rename the directory, rather than
-      delete it, in case you have trouble and need to revert to it.  Keep
-      in mind the directory might consume significant disk space.  To rename
-      the directory, use a command like this:
-<screen>
-<userinput>mv /usr/local/pgsql /usr/local/pgsql.old</>
-</screen>
-     (Be sure to move the directory as a single unit so relative paths
-     remain unchanged.)
-     </para>
-    </step>
-
-    <step>
-     <para>
-      Install the new version of <productname>PostgreSQL</productname> as
-      outlined in <![%standalone-include[the next section.]]>
-      <![%standalone-ignore[<xref linkend="install-procedure">.]]>
-     </para>
-    </step>
-
-    <step>
-     <para>
-      Create a new database cluster if needed.  Remember that you must
-      execute these commands while logged in to the special database user
-      account (which you already have if you are upgrading).
-<programlisting>
-<userinput>/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data</>
-</programlisting>
-     </para>
-    </step>
-
-    <step>
-     <para>
-      Restore your previous <filename>pg_hba.conf</> and any
-      <filename>postgresql.conf</> modifications.
-     </para>
-    </step>
-
-    <step>
-     <para>
-      Start the database server, again using the special database user
-      account:
-<programlisting>
-<userinput>/usr/local/pgsql/bin/postgres -D /usr/local/pgsql/data</>
-</programlisting>
-     </para>
-    </step>
-
-    <step>
-     <para>
-      Finally, restore your data from backup with:
-<screen>
-<userinput>/usr/local/pgsql/bin/psql -d postgres -f <replaceable>outputfile</></userinput>
-</screen>
-      using the <emphasis>new</> <application>psql</>.
-     </para>
-    </step>
-   </procedure>
-
-   <para>
-    The least downtime can be achieved by installing the new server in
-    a different directory and running both the old and the new servers
-    in parallel, on different ports. Then you can use something like:
-
-<programlisting>
-pg_dumpall -p 5432 | psql -d postgres -p 5433
-</programlisting>
-    to transfer your data.
-   </para>
-
-  </sect2>
-
-  <sect2 id="upgrading-methods-other">
-   <title>Non-Dump Upgrade Methods</title>
-
-   <para>
-    The <link linkend="pgupgrade">pg_upgrade</link> module allows an
-    installation to be migrated in-place from one major
-    <productname>PostgreSQL</> version to the next.  Upgrades can be
-    performed in minutes.
-<!## XL>
-	<note>
-	 <para>
-		Support for <link linkend="pgupgrade">pg_upgrade</link> is not tested
-in <productname>Postgres-XL</productname>. Users are advised to use other
-methods for upgrading to next major version of
-<productname>Postgres-XL</productname>.
-	 </para>
-	</note>
-<!## end>
-   </para>
-
-   <para>
-    It is also possible to use certain replication methods, such as
-    <productname>Slony</>, to create a standby server with the updated version of
-    <productname>PostgreSQL</>.  This is possible because Slony supports
-    replication between different major versions of
-    <productname>PostgreSQL</>.  The standby can be on the same computer or
-    a different computer.  Once it has synced up with the master server
-    (running the older version of <productname>PostgreSQL</>), you can
-    switch masters and make the standby the master and shut down the older
-    database instance.  Such a switch-over results in only several seconds
-    of downtime for an upgrade.
-   </para>
-
-  </sect2>
- </sect1>
-
- <sect1 id="preventing-server-spoofing">
-<!## PG>
-  <title>Preventing Server Spoofing</title>
-<!## end>
-<!## XC>
-  <title>Preventing Coordinator/Datanode Spoofing</title>
-<!## end>
-<!## XL>
-  <title>Preventing Coordinator/Datanode Spoofing</title>
-<!## end>
-
-  <indexterm zone="preventing-server-spoofing">
-   <primary>server spoofing</primary>
-  </indexterm>
-
-&common;
-  <para>
-<!## PG>
-   While the server is running, it is not possible for a malicious user
-<!## end>
-<!## XC>
-   While Coordinators and Datanodes are running, it is not possible for a malicious user
-<!## end>
-<!## XL>
-   While Coordinators and Datanodes are running, it is not possible for a malicious user
-<!## end>
-   to take the place of the normal database server.  However, when the
-   server is down, it is possible for a local user to spoof the normal
-   server by starting their own server.  The spoof server could read
-   passwords and queries sent by clients, but could not return any data
-   because the <varname>PGDATA</> directory would still be secure because
-   of directory permissions. Spoofing is possible because any user can
-   start a database server; a client cannot identify an invalid server
-   unless it is specially configured.
-  </para>
-
-  <para>
-   The simplest way to prevent spoofing for <literal>local</>
-   connections is to use a Unix domain socket directory (<xref
-   linkend="guc-unix-socket-directory">) that has write permission only
-   for a trusted local user.  This prevents a malicious user from creating
-   their own socket file in that directory.  If you are concerned that
-   some applications might still reference <filename>/tmp</> for the
-   socket file and hence be vulnerable to spoofing, during operating system
-   startup create a symbolic link <filename>/tmp/.s.PGSQL.5432</> that points
-   to the relocated socket file.  You also might need to modify your
-   <filename>/tmp</> cleanup script to prevent removal of the symbolic link.
-  </para>
-
-  <para>
-   To prevent spoofing on TCP connections, the best solution is to use
-   SSL certificates and make sure that clients check the server's certificate.
-   To do that, the server
-   must be configured to accept only <literal>hostssl</> connections (<xref
-   linkend="auth-pg-hba-conf">) and have SSL
-   <filename>server.key</filename> (key) and
-   <filename>server.crt</filename> (certificate) files (<xref
-   linkend="ssl-tcp">). The TCP client must connect using
-   <literal>sslmode=verify-ca</> or
-   <literal>verify-full</> and have the appropriate root certificate
-   file installed (<xref linkend="libpq-connect">).
-  </para>
- </sect1>
-
- <sect1 id="encryption-options">
-  <title>Encryption Options</title>
-
-  <indexterm zone="encryption-options">
-   <primary>encryption</primary>
-  </indexterm>
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> offers encryption at several
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> offers encryption at several
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> offers encryption at several
-<!## end>
-   levels, and provides flexibility in protecting data from disclosure
-   due to database server theft, unscrupulous administrators, and
-   insecure networks. Encryption might also be required to secure
-   sensitive data such as medical records or financial transactions.
-  </para>
-
-  <variablelist>
-
-  <varlistentry>
-   <term>Password Storage Encryption</term>
-   <listitem>
-
-    <para>
-     By default, database user passwords are stored as MD5 hashes, so
-     the administrator cannot determine the actual password assigned
-     to the user. If MD5 encryption is used for client authentication,
-     the unencrypted password is never even temporarily present on the
-     server because the client MD5-encrypts it before being sent
-     across the network.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Encryption For Specific Columns</term>
-
-   <listitem>
-    <para>
-     The <xref linkend="pgcrypto"> module allows certain fields to be
-     stored encrypted.
-     This is useful if only some of the data is sensitive.
-     The client supplies the decryption key and the data is decrypted
-     on the server and then sent to the client.
-    </para>
-
-    <para>
-     The decrypted data and the decryption key are present on the
-     server for a brief time while it is being decrypted and
-     communicated between the client and server. This presents a brief
-     moment where the data and keys can be intercepted by someone with
-     complete access to the database server, such as the system
-     administrator.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Data Partition Encryption</term>
-
-   <listitem>
-    <para>
-     On Linux, encryption can be layered on top of a file system
-     using a <quote>loopback device</quote>. This allows an entire
-     file system partition to be encrypted on disk, and decrypted by the
-     operating system. On FreeBSD, the equivalent facility is called
-     GEOM Based Disk Encryption (<acronym>gbde</acronym>), and many
-     other operating systems support this functionality, including Windows.
-    </para>
-
-    <para>
-     This mechanism prevents unencrypted data from being read from the
-     drives if the drives or the entire computer is stolen. This does
-     not protect against attacks while the file system is mounted,
-     because when mounted, the operating system provides an unencrypted
-     view of the data. However, to mount the file system, you need some
-     way for the encryption key to be passed to the operating system,
-     and sometimes the key is stored somewhere on the host that mounts
-     the disk.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Encrypting Passwords Across A Network</term>
-
-   <listitem>
-     <para>
-      The <literal>MD5</> authentication method double-encrypts the
-      password on the client before sending it to the server. It first
-      MD5-encrypts it based on the user name, and then encrypts it
-      based on a random salt sent by the server when the database
-      connection was made. It is this double-encrypted value that is
-      sent over the network to the server. Double-encryption not only
-      prevents the password from being discovered, it also prevents
-      another connection from using the same encrypted password to
-      connect to the database server at a later time.
-     </para>
-    </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Encrypting Data Across A Network</term>
-
-    <listitem>
-     <para>
-      SSL connections encrypt all data sent across the network: the
-      password, the queries, and the data returned. The
-      <filename>pg_hba.conf</> file allows administrators to specify
-      which hosts can use non-encrypted connections (<literal>host</>)
-      and which require SSL-encrypted connections
-      (<literal>hostssl</>). Also, clients can specify that they
-      connect to servers only via SSL. <application>Stunnel</> or
-      <application>SSH</> can also be used to encrypt transmissions.
-     </para>
-    </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>SSL Host Authentication</term>
-
-   <listitem>
-    <para>
-     It is possible for both the client and server to provide SSL
-     certificates to each other. It takes some extra configuration
-     on each side, but this provides stronger verification of identity
-     than the mere use of passwords. It prevents a computer from
-     pretending to be the server just long enough to read the password
-     sent by the client. It also helps prevent <quote>man in the middle</>
-     attacks where a computer between the client and server pretends to
-     be the server and reads and passes all data between the client and
-     server.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term>Client-Side Encryption</term>
-
-   <listitem>
-    <para>
-     If the system administrator for the server's machine cannot be trusted,
-     it is necessary
-     for the client to encrypt the data; this way, unencrypted data
-     never appears on the database server. Data is encrypted on the
-     client before being sent to the server, and database results have
-     to be decrypted on the client before being used.
-    </para>
-   </listitem>
-  </varlistentry>
-
-  </variablelist>
-
- </sect1>
-
- <sect1 id="ssl-tcp">
-  <title>Secure TCP/IP Connections with SSL</title>
-
-  <indexterm zone="ssl-tcp">
-   <primary>SSL</primary>
-  </indexterm>
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</> has native support for using
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> has native support for using
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> has native support for using
-<!## end>
-   <acronym>SSL</> connections to encrypt client/server communications
-   for increased security. This requires that
-   <productname>OpenSSL</productname> is installed on both client and
-<!## PG>
-   server systems and that support in <productname>PostgreSQL</> is
-<!## end>
-<!## XC>
-   server systems and that support in <productname>Postgres-XC</> is
-<!## end>
-<!## XL>
-   server systems and that support in <productname>Postgres-XL</> is
-<!## end>
-   enabled at build time (see <xref linkend="installation">).
-  </para>
-
-  <para>
-   With <acronym>SSL</> support compiled in, the
-<!## PG>
-   <productname>PostgreSQL</> server can be started with
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> server can be started with
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> server can be started with
-<!## end>
-   <acronym>SSL</> enabled by setting the parameter
-   <xref linkend="guc-ssl"> to <literal>on</> in
-   <filename>postgresql.conf</>.  The server will listen for both normal
-   and <acronym>SSL</> connections on the same TCP port, and will negotiate
-   with any connecting client on whether to use <acronym>SSL</>.  By
-   default, this is at the client's option; see <xref
-   linkend="auth-pg-hba-conf"> about how to set up the server to require
-   use of <acronym>SSL</> for some or all connections.
-  </para>
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> reads the system-wide
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> reads the system-wide
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> reads the system-wide
-<!## end>
-   <productname>OpenSSL</productname> configuration file. By default, this
-   file is named <filename>openssl.cnf</filename> and is located in the
-   directory reported by <literal>openssl version -d</>.
-   This default can be overridden by setting environment variable
-   <envar>OPENSSL_CONF</envar> to the name of the desired configuration file.
-  </para>
-
-  <para>
-   <productname>OpenSSL</productname> supports a wide range of ciphers
-   and authentication algorithms, of varying strength.  While a list of
-   ciphers can be specified in the <productname>OpenSSL</productname>
-   configuration file, you can specify ciphers specifically for use by
-   the database server by modifying <xref linkend="guc-ssl-ciphers"> in
-   <filename>postgresql.conf</>.
-  </para>
-
-  <note>
-   <para>
-    It is possible to have authentication without encryption overhead by
-    using <literal>NULL-SHA</> or <literal>NULL-MD5</> ciphers.  However,
-    a man-in-the-middle could read and pass communications between client
-    and server.  Also, encryption overhead is minimal compared to the
-    overhead of authentication.  For these reasons NULL ciphers are not
-    recommended.
-   </para>
-  </note>
-
-  <para>
-   To start in <acronym>SSL</> mode, the files <filename>server.crt</>
-   and <filename>server.key</> must exist in the server's data directory.
-   These files should contain the server certificate and private key,
-   respectively.
-   On Unix systems, the permissions on <filename>server.key</filename> must
-   disallow any access to world or group; achieve this by the command
-   <command>chmod 0600 server.key</command>.
-   If the private key is protected with a passphrase, the
-   server will prompt for the passphrase and will not start until it has
-   been entered.
-  </para>
-
-  <para>
-   In some cases, the server certificate might be signed by an
-   <quote>intermediate</> certificate authority, rather than one that is
-   directly trusted by clients.  To use such a certificate, append the
-   certificate of the signing authority to the <filename>server.crt</> file,
-   then its parent authority's certificate, and so on up to a <quote>root</>
-   authority that is trusted by the clients.  The root certificate should
-   be included in every case where <filename>server.crt</> contains more than
-   one certificate.
-  </para>
-
-  <sect2 id="ssl-client-certificates">
-   <title>Using Client Certificates</title>
-
-&common;
-   <para>
-   To require the client to supply a trusted certificate, place
-   certificates of the certificate authorities (<acronym>CA</acronym>s)
-   you trust in the file <filename>root.crt</filename> in the data
-   directory, and set the <literal>clientcert</literal> parameter
-   to 1 on the appropriate <literal>hostssl</> line(s) in
-   <filename>pg_hba.conf</>.
-   A certificate will then be requested from the client during
-   SSL connection startup.  (See <xref linkend="libpq-ssl"> for a
-   description of how to set up certificates on the client.)  The server will
-   verify that the client's certificate is signed by one of the trusted
-   certificate authorities.  Certificate Revocation List (CRL) entries
-   are also checked if the file <filename>root.crl</filename> exists.
-   <!-- If this URL changes replace it with a URL to www.archive.org. -->
-   (See <ulink
-   url="http://h71000.www7.hp.com/DOC/83final/BA554_90007/ch04s02.html"></>
-   for diagrams showing SSL certificate usage.)
-  </para>
-
-  <para>
-   The <literal>clientcert</literal> option in <filename>pg_hba.conf</> is
-   available for all authentication methods, but only for rows specified as
-   <literal>hostssl</>.  When <literal>clientcert</literal> is not specified
-   or is set to 0, the server will still verify presented client
-   certificates against <filename>root.crt</filename> if that file exists
-   &mdash; but it will not insist that a client certificate be presented.
-  </para>
-
-  <para>
-   Note that <filename>root.crt</filename> lists the top-level CAs that are
-   considered trusted for signing client certificates.  In principle it need
-   not list the CA that signed the server's certificate, though in most cases
-   that CA would also be trusted for client certificates.
-  </para>
-
-  <para>
-   If you are setting up client certificates, you may wish to use
-   the <literal>cert</> authentication method, so that the certificates
-   control user authentication as well as providing connection security.
-   See <xref linkend="auth-cert"> for details.
-  </para>
-  </sect2>
-
-  <sect2 id="ssl-server-files">
-   <title>SSL Server File Usage</title>
-
-&common;
-   <para>
-    <xref linkend="ssl-file-usage"> summarizes the files that are
-    relevant to the SSL setup on the server.
-   </para>
-
-  <table id="ssl-file-usage">
-   <title>SSL Server File Usage</title>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>File</entry>
-      <entry>Contents</entry>
-      <entry>Effect</entry>
-     </row>
-    </thead>
-
-    <tbody>
-
-     <row>
-      <entry><filename>$PGDATA/server.crt</></entry>
-      <entry>server certificate</entry>
-      <entry>sent to client to indicate server's identity</entry>
-     </row>
-
-     <row>
-      <entry><filename>$PGDATA/server.key</></entry>
-      <entry>server private key</entry>
-      <entry>proves server certificate was sent by the owner; does not indicate
-      certificate owner is trustworthy</entry>
-     </row>
-
-     <row>
-      <entry><filename>$PGDATA/root.crt</></entry>
-      <entry>trusted certificate authorities</entry>
-      <entry>checks that client certificate is
-      signed by a trusted certificate authority</entry>
-     </row>
-
-     <row>
-      <entry><filename>$PGDATA/root.crl</></entry>
-      <entry>certificates revoked by certificate authorities</entry>
-      <entry>client certificate must not be on this list</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-   <para>
-    The files <filename>server.key</>, <filename>server.crt</>,
-    <filename>root.crt</filename>, and <filename>root.crl</filename>
-    are only examined during server start; so you must restart
-    the server for changes in them to take effect.
-   </para>
-  </sect2>
-
-  <sect2 id="ssl-certificate-creation">
-   <title>Creating a Self-signed Certificate</title>
-
-&common;
-   <para>
-    To create a quick self-signed certificate for the server, use the
-    following <productname>OpenSSL</productname> command:
-<programlisting>
-openssl req -new -text -out server.req
-</programlisting>
-    Fill out the information that <application>openssl</> asks for. Make sure
-    you enter the local host name as <quote>Common Name</>; the challenge
-    password can be left blank. The program will generate a key that is
-    passphrase protected; it will not accept a passphrase that is less
-    than four characters long. To remove the passphrase (as you must if
-    you want automatic start-up of the server), run the commands:
-<programlisting>
-openssl rsa -in privkey.pem -out server.key
-rm privkey.pem
-</programlisting>
-    Enter the old passphrase to unlock the existing key. Now do:
-<programlisting>
-openssl req -x509 -in server.req -text -key server.key -out server.crt
-</programlisting>
-    to turn the certificate into a self-signed certificate and to copy
-    the key and certificate to where the server will look for them.
-    Finally do:
-<programlisting>
-chmod og-rwx server.key
-</programlisting>
-    because the server will reject the file if its permissions are more
-    liberal than this.
-    For more details on how to create your server private key and
-    certificate, refer to the <productname>OpenSSL</> documentation.
-   </para>
-
-   <para>
-    A self-signed certificate can be used for testing, but a certificate
-    signed by a certificate authority (<acronym>CA</>) (either one of the
-    global <acronym>CAs</> or a local one) should be used in production
-    so that clients can verify the server's identity. If all the clients
-    are local to the organization, using a local <acronym>CA</> is
-    recommended.
-   </para>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="ssh-tunnels">
-  <title>Secure TCP/IP Connections with <application>SSH</application> Tunnels</title>
-
-  <indexterm zone="ssh-tunnels">
-   <primary>ssh</primary>
-  </indexterm>
-&common;
-  <para>
-   It is possible to use <application>SSH</application> to encrypt the network
-   connection between clients and a
-<!## PG>
-   <productname>PostgreSQL</productname> server. Done properly, this
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> server. Done properly, this
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> server. Done properly, this
-<!## end>
-   provides an adequately secure network connection, even for non-SSL-capable
-   clients.
-  </para>
-
-  <para>
-   First make sure that an <application>SSH</application> server is
-   running properly on the same machine as the
-<!## PG>
-   <productname>PostgreSQL</productname> server and that you can log in using
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> server and that you can log in using
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> server and that you can log in using
-<!## end>
-   <command>ssh</command> as some user. Then you can establish a secure
-   tunnel with a command like this from the client machine:
-<programlisting>
-ssh -L 63333:localhost:5432 [email protected]
-</programlisting>
-   The first number in the <option>-L</option> argument, 63333, is the
-   port number of your end of the tunnel; it can be any unused port.
-   (IANA reserves ports 49152 through 65535 for private use.)  The
-   second number, 5432, is the remote end of the tunnel: the port
-   number your server is using. The name or IP address between the
-   port numbers is the host with the database server you are going to
-   connect to, as seen from the host you are logging in to, which
-   is <literal>foo.com</literal> in this example. In order to connect
-   to the database server using this tunnel, you connect to port 63333
-   on the local machine:
-<programlisting>
-psql -h localhost -p 63333 postgres
-</programlisting>
-   To the database server it will then look as though you are really
-   user <literal>joe</literal> on host <literal>foo.com</literal>
-   connecting to <literal>localhost</literal> in that context, and it
-   will use whatever authentication procedure was configured for
-   connections from this user and host.  Note that the server will not
-   think the connection is SSL-encrypted, since in fact it is not
-   encrypted between the
-   <application>SSH</application> server and the
-<!## PG>
-   <productname>PostgreSQL</productname> server.  This should not pose any
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> server.  This should not pose any
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> server.  This should not pose any
-<!## end>
-   extra security risk as long as they are on the same machine.
-  </para>
-
-  <para>
-   In order for the
-   tunnel setup to succeed you must be allowed to connect via
-   <command>ssh</command> as <literal>[email protected]</literal>, just
-   as if you had attempted to use <command>ssh</command> to create a
-   terminal session.
-  </para>
-
-  <para>
-   You could also have set up the port forwarding as
-<programlisting>
-ssh -L 63333:foo.com:5432 [email protected]
-</programlisting>
-   but then the database server will see the connection as coming in
-   on its <literal>foo.com</literal> interface, which is not opened by
-   the default setting <literal>listen_addresses =
-   'localhost'</literal>.  This is usually not what you want.
-  </para>
-
-  <para>
-   If you have to <quote>hop</quote> to the database server via some
-   login host, one possible setup could look like this:
-<programlisting>
-ssh -L 63333:db.foo.com:5432 [email protected]
-</programlisting>
-   Note that this way the connection
-   from <literal>shell.foo.com</literal>
-   to <literal>db.foo.com</literal> will not be encrypted by the SSH
-   tunnel.
-   SSH offers quite a few configuration possibilities when the network
-   is restricted in various ways.  Please refer to the SSH
-   documentation for details.
-  </para>
-
-  <tip>
-   <para>
-    Several other applications exist that can provide secure tunnels using
-    a procedure similar in concept to the one just described.
-   </para>
-  </tip>
-
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/seg.sgmlin b/doc-xc/src/sgml/seg.sgmlin
deleted file mode 100644
index d74d02769c..0000000000
--- a/doc-xc/src/sgml/seg.sgmlin
+++ /dev/null
@@ -1,404 +0,0 @@
-<!-- doc/src/sgml/seg.sgml -->
-
-<sect1 id="seg" xreflabel="seg">
- <title>seg</title>
-
- <indexterm zone="seg">
-  <primary>seg</primary>
- </indexterm>
-
-&common;
-
- <para>
-  This module implements a data type <type>seg</> for
-  representing line segments, or floating point intervals.
-  <type>seg</> can represent uncertainty in the interval endpoints,
-  making it especially useful for representing laboratory measurements.
- </para>
-
- <sect2>
-  <title>Rationale</title>
-
-&common;
-  <para>
-   The geometry of measurements is usually more complex than that of a
-   point in a numeric continuum. A measurement is usually a segment of
-   that continuum with somewhat fuzzy limits. The measurements come out
-   as intervals because of uncertainty and randomness, as well as because
-   the value being measured may naturally be an interval indicating some
-   condition, such as the temperature range of stability of a protein.
-  </para>
-
-  <para>
-   Using just common sense, it appears more convenient to store such data
-   as intervals, rather than pairs of numbers. In practice, it even turns
-   out more efficient in most applications.
-  </para>
-
-  <para>
-   Further along the line of common sense, the fuzziness of the limits
-   suggests that the use of traditional numeric data types leads to a
-   certain loss of information. Consider this: your instrument reads
-   6.50, and you input this reading into the database. What do you get
-   when you fetch it? Watch:
-
-<screen>
-test=> select 6.50 :: float8 as "pH";
- pH
----
-6.5
-(1 row)
-</screen>
-
-   In the world of measurements, 6.50 is not the same as 6.5. It may
-   sometimes be critically different. The experimenters usually write
-   down (and publish) the digits they trust. 6.50 is actually a fuzzy
-   interval contained within a bigger and even fuzzier interval, 6.5,
-   with their center points being (probably) the only common feature they
-   share. We definitely do not want such different data items to appear the
-   same.
-  </para>
-
-  <para>
-   Conclusion? It is nice to have a special data type that can record the
-   limits of an interval with arbitrarily variable precision. Variable in
-   the sense that each data element records its own precision.
-  </para>
-
-  <para>
-   Check this out:
-
-<screen>
-test=> select '6.25 .. 6.50'::seg as "pH";
-          pH
-------------
-6.25 .. 6.50
-(1 row)
-</screen>
-  </para>
- </sect2>
-
- <sect2>
-  <title>Syntax</title>
-
-&common;
-  <para>
-   The external representation of an interval is formed using one or two
-   floating-point numbers joined by the range operator (<literal>..</literal>
-   or <literal>...</literal>).  Alternatively, it can be specified as a
-   center point plus or minus a deviation.
-   Optional certainty indicators (<literal>&lt;</literal>,
-   <literal>&gt;</literal> or <literal>~</literal>) can be stored as well.
-   (Certainty indicators are ignored by all the built-in operators, however.)
-   <xref linkend="seg-repr-table"> gives an overview of allowed
-   representations; <xref linkend="seg-input-examples"> shows some
-   examples.
-  </para>
-
-  <para>
-   In <xref linkend="seg-repr-table">, <replaceable>x</>, <replaceable>y</>, and
-   <replaceable>delta</> denote
-   floating-point numbers.  <replaceable>x</> and <replaceable>y</>, but
-   not <replaceable>delta</>, can be preceded by a certainty indicator.
-  </para>
-
-  <table id="seg-repr-table">
-   <title><type>seg</> External Representations</title>
-   <tgroup cols="2">
-    <tbody>
-     <row>
-      <entry><literal><replaceable>x</></literal></entry>
-      <entry>Single value (zero-length interval)
-      </entry>
-     </row>
-     <row>
-      <entry><literal><replaceable>x</> .. <replaceable>y</></literal></entry>
-      <entry>Interval from <replaceable>x</> to <replaceable>y</>
-      </entry>
-     </row>
-     <row>
-      <entry><literal><replaceable>x</> (+-) <replaceable>delta</></literal></entry>
-      <entry>Interval from <replaceable>x</> - <replaceable>delta</> to
-      <replaceable>x</> + <replaceable>delta</>
-      </entry>
-     </row>
-     <row>
-      <entry><literal><replaceable>x</> ..</literal></entry>
-      <entry>Open interval with lower bound <replaceable>x</>
-      </entry>
-     </row>
-     <row>
-      <entry><literal>.. <replaceable>x</></literal></entry>
-      <entry>Open interval with upper bound <replaceable>x</>
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <table id="seg-input-examples">
-   <title>Examples of Valid <type>seg</> Input</title>
-   <tgroup cols="2">
-    <tbody>
-     <row>
-      <entry><literal>5.0</literal></entry>
-      <entry>
-       Creates a zero-length segment (a point, if you will)
-      </entry>
-     </row>
-     <row>
-      <entry><literal>~5.0</literal></entry>
-      <entry>
-       Creates a zero-length segment and records
-       <literal>~</> in the data.  <literal>~</literal> is ignored
-       by <type>seg</> operations, but
-       is preserved as a comment.
-      </entry>
-     </row>
-     <row>
-      <entry><literal>&lt;5.0</literal></entry>
-      <entry>
-       Creates a point at 5.0.  <literal>&lt;</literal> is ignored but
-       is preserved as a comment.
-      </entry>
-     </row>
-     <row>
-      <entry><literal>&gt;5.0</literal></entry>
-      <entry>
-       Creates a point at 5.0.  <literal>&gt;</literal> is ignored but
-       is preserved as a comment.
-      </entry>
-     </row>
-     <row>
-      <entry><literal>5(+-)0.3</literal></entry>
-      <entry>
-        Creates an interval <literal>4.7 .. 5.3</literal>.
-        Note that the <literal>(+-)</> notation isn't preserved.
-      </entry>
-     </row>
-     <row>
-      <entry><literal>50 .. </literal></entry>
-      <entry>Everything that is greater than or equal to 50</entry>
-     </row>
-     <row>
-      <entry><literal>.. 0</literal></entry>
-      <entry>Everything that is less than or equal to 0</entry>
-     </row>
-     <row>
-      <entry><literal>1.5e-2 .. 2E-2 </literal></entry>
-      <entry>Creates an interval <literal>0.015 .. 0.02</literal></entry>
-     </row>
-     <row>
-      <entry><literal>1 ... 2</literal></entry>
-      <entry>
-       The same as <literal>1...2</literal>, or <literal>1 .. 2</literal>,
-       or <literal>1..2</literal>
-       (spaces around the range operator are ignored)
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   Because <literal>...</> is widely used in data sources, it is allowed
-   as an alternative spelling of <literal>..</>.  Unfortunately, this
-   creates a parsing ambiguity: it is not clear whether the upper bound
-   in <literal>0...23</> is meant to be <literal>23</> or <literal>0.23</>.
-   This is resolved by requiring at least one digit before the decimal
-   point in all numbers in <type>seg</> input.
-  </para>
-
-  <para>
-   As a sanity check, <type>seg</> rejects intervals with the lower bound
-   greater than the upper, for example <literal>5 .. 2</>.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>Precision</title>
-
-&common;
-  <para>
-   <type>seg</> values are stored internally as pairs of 32-bit floating point
-   numbers. This means that numbers with more than 7 significant digits
-   will be truncated.
-  </para>
-
-  <para>
-   Numbers with 7 or fewer significant digits retain their
-   original precision. That is, if your query returns 0.00, you will be
-   sure that the trailing zeroes are not the artifacts of formatting: they
-   reflect the precision of the original data. The number of leading
-   zeroes does not affect precision: the value 0.0067 is considered to
-   have just 2 significant digits.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Usage</title>
-
-&common;
-  <para>
-   The <filename>seg</> module includes a GiST index operator class for
-   <type>seg</> values.
-   The operators supported by the GiST operator class are shown in <xref linkend="seg-gist-operators">.
-  </para>
-
-  <table id="seg-gist-operators">
-   <title>Seg GiST Operators</title>
-   <tgroup cols="2">
-    <thead>
-     <row>
-      <entry>Operator</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>[a, b] &lt;&lt; [c, d]</literal></entry>
-      <entry>[a, b] is entirely to the left of [c, d].  That is, [a,
-       b] &lt;&lt; [c, d] is true if b &lt; c and false otherwise.</entry>
-     </row>
-
-     <row>
-      <entry><literal>[a, b] &gt;&gt; [c, d]</literal></entry>
-      <entry>[a, b] is entirely to the right of [c, d].  That is, [a,
-       b] &gt;&gt; [c, d] is true if a &gt; d and false otherwise.</entry>
-     </row>
-
-     <row>
-      <entry><literal>[a, b] &amp;&lt; [c, d]</literal></entry>
-      <entry>Overlaps or is left of &mdash; This might be better read
-       as <quote>does not extend to right of</quote>.  It is true when
-       b &lt;= d.</entry>
-     </row>
-
-     <row>
-      <entry><literal>[a, b] &amp;&gt; [c, d]</literal></entry>
-      <entry>Overlaps or is right of &mdash; This might be better read
-       as <quote>does not extend to left of</quote>.  It is true when
-       a &gt;= c.</entry>
-     </row>
-
-     <row>
-      <entry><literal>[a, b] = [c, d]</literal></entry>
-      <entry>Same as &mdash; The segments [a, b] and [c, d] are
-       identical, that is, a = c and b = d.</entry>
-     </row>
-
-     <row>
-      <entry><literal>[a, b] &amp;&amp; [c, d]</literal></entry>
-      <entry>The segments [a, b] and [c, d] overlap.</entry>
-     </row>
-
-     <row>
-      <entry><literal>[a, b] @&gt; [c, d]</literal></entry>
-      <entry>The segment [a, b] contains the segment [c, d], that is,
-       a &lt;= c and b &gt;= d.</entry>
-     </row>
-
-     <row>
-      <entry><literal>[a, b] &lt;@ [c, d]</literal></entry>
-      <entry>The segment [a, b] is contained in [c, d], that is, a
-       &gt;= c and b &lt;= d.</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   (Before PostgreSQL 8.2, the containment operators <literal>@&gt;</> and <literal>&lt;@</> were
-   respectively called <literal>@</> and <literal>~</>.  These names are still available, but are
-   deprecated and will eventually be retired.  Notice that the old names
-   are reversed from the convention formerly followed by the core geometric
-   data types!)
-  </para>
-
-  <para>
-   The standard B-tree operators are also provided, for example
-
-  <informaltable>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Operator</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><literal>[a, b] &lt; [c, d]</literal></entry>
-       <entry>Less than</entry>
-      </row>
-
-      <row>
-       <entry><literal>[a, b] &gt; [c, d]</literal></entry>
-       <entry>Greater than</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </informaltable>
-
-   These operators do not make a lot of sense for any practical
-   purpose but sorting. These operators first compare (a) to (c),
-   and if these are equal, compare (b) to (d). That results in
-   reasonably good sorting in most cases, which is useful if
-   you want to use ORDER BY with this type.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Notes</title>
-
-&common;
-  <para>
-   For examples of usage, see the regression test <filename>sql/seg.sql</>.
-  </para>
-
-  <para>
-   The mechanism that converts <literal>(+-)</> to regular ranges
-   isn't completely accurate in determining the number of significant digits
-   for the boundaries.  For example, it adds an extra digit to the lower
-   boundary if the resulting interval includes a power of ten:
-
-<screen>
-postgres=> select '10(+-)1'::seg as seg;
-      seg
----------
-9.0 .. 11             -- should be: 9 .. 11
-</screen>
-  </para>
-
-  <para>
-   The performance of an R-tree index can largely depend on the initial
-   order of input values. It may be very helpful to sort the input table
-   on the <type>seg</> column; see the script <filename>sort-segments.pl</>
-   for an example.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Credits</title>
-
-  <para>
-   Original author: Gene Selkov, Jr. <email>[email protected]</email>,
-   Mathematics and Computer Science Division, Argonne National Laboratory.
-  </para>
-
-  <para>
-   My thanks are primarily to Prof. Joe Hellerstein
-   (<ulink url="http://db.cs.berkeley.edu/jmh/"></ulink>) for elucidating the
-   gist of the GiST (<ulink url="http://gist.cs.berkeley.edu/"></ulink>). I am
-   also grateful to all Postgres developers, present and past, for enabling
-   myself to create my own world and live undisturbed in it. And I would like
-   to acknowledge my gratitude to Argonne Lab and to the U.S. Department of
-   Energy for the years of faithful support of my database research.
-  </para>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/sepgsql.sgmlin b/doc-xc/src/sgml/sepgsql.sgmlin
deleted file mode 100644
index db9b64cc88..0000000000
--- a/doc-xc/src/sgml/sepgsql.sgmlin
+++ /dev/null
@@ -1,552 +0,0 @@
-<!-- doc/src/sgml/sepgsql.sgml -->
-
-<sect1 id="sepgsql" xreflabel="sepgsql">
- <title>sepgsql</title>
-
- <indexterm zone="sepgsql">
-  <primary>sepgsql</primary>
- </indexterm>
-
- <para>
-  <filename>sepgsql</> is a loadable module which supports label-based
-  mandatory access control (MAC) based on <productname>SELinux</> security
-  policy.
- </para>
-
- <warning>
-   <para>
-     This implementation has signification limitations, and does not enforce
-     mandatory access control for all actions.  See
-     <xref linkend="sepgsql-limitations">.
-   </para>
- </warning>
-
- <sect2 id="sepgsql-overview">
-  <title>Overview</title>
-
-  <para>
-   This module integrates with <productname>SELinux</> to provide an
-   additional layer of security checking above and beyond what is normally
-   provided by <productname>PostgreSQL</productname>.  From the perspective of
-   <productname>SELinux</>, this module allows
-   <productname>PostgreSQL</productname> to function as a user-space object
-   manager.  Each table or function access initiated by a DML query will be
-   checked against the system security policy.  This check is an additional to
-   the usual permissions checking performed by
-   <productname>PostgreSQL</productname>.
-  </para>
-
-  <para>
-   <productname>SELinux</productname> access control decisions are made using
-   security labels, which are represented by strings such as
-   <literal>system_u:object_r:sepgsql_table_t:s0</>.  Each access control
-   decision involves two labels: the label of the subject attempting to
-   perform the action, and the label of the object on which the operation is
-   to be performed.  Since these labels can be applied to any sort of object,
-   access control decisions for objects stored within the database can be
-   (and, with this module, are) subjected to the same general criteria used
-   for objects of any other type (e.g. files).  This design is intended to
-   allow a centralized security policy to protect information assets
-   independent of the particulars of how those assets are stored.
-  </para>
-
-  <para>
-   The <xref linkend="sql-security-label"> statement allows assignment of
-   a security label to a database object.
-  </para>
-
- </sect2>
- <sect2 id="sepgsql-installation">
-  <title>Installation</title>
-
-  <para>
-    This module can only be used on <productname>Linux</productname> 2.6.28
-    or higher with <productname>SELinux</productname> enabled.  It is not
-    available on any other platform, and must be explicitly enabled using
-    <literal>--with-selinux</>.  You will also need <productname>libselinux</>
-    2.0.93 or higher and <productname>selinux-policy</> 3.9.13 or higher
-    (some distributions may backport the necessary rules into older policy
-    versions).
-  </para>
-
-  <para>
-   The <command>sestatus</> command allows you to check the status of
-   <productname>SELinux</productname>.
-<screen>
-$ sestatus
-SELinux status:                 enabled
-SELinuxfs mount:                /selinux
-Current mode:                   enforcing
-Mode from config file:          enforcing
-Policy version:                 24
-Policy from config file:        targeted
-</screen>
-   If <productname>SELinux</> is disabled or not installed, you must set
-   that product up first before installing this module.
-  </para>
-
-  <para>
-   To use this module, you must add include <literal>sepgsql</>
-   in <xref linkend="guc-shared-preload-libraries">.  The module will not
-   function if loaded in any other manner.  Once the module is loaded, you
-   should execute <filename>sepgsql.sql</filename> in each database.
-   This will install functions needed for security label management, and
-   assign initial security labels.
-  </para>
-
-  <para>
-   The following instructions that assume your installation is under the
-   <filename>/usr/local/pgsql</> directory. Adjust the paths shown below as
-   appropriate for your installation.
-  </para>
-
-<screen>
-$ initdb
-$ vi $PGDATA/postgresql.conf
-$ for DBNAME in template0 template1 postgres; do
-  postgres --single -F -O -c exit_on_error=true $DBNAME \
-      &lt; /usr/local/pgsql/share/contrib/sepgsql.sql &gt; /dev/null
-  done
-</screen>
-
-  <para>
-   If the installation process completes without error, you can now start the
-   server normally.
-  </para>
- </sect2>
-
- <sect2 id="sepgsql-regression">
-  <title>Regression Tests</title>
-  <para>
-   Due to the nature of <productname>SELinux</productname>, running the
-   regression tests for this module requires several additional configuration
-   steps.
-  </para>
-
-  <para>
-   First, build and install the policy package for the regression test.
-   The <filename>sepgsql-regtest.pp</> is a special purpose policy package
-   which provides a set of rules to be allowed during the regression tests.
-   It should be built from the policy source file 
-   (<filename>sepgsql-regtest.te</>), which is normally done using
-   <command>make</command>.  You will need to locate the appropriate
-   Makefile on your system; the path shown below is only an example.
-   Once built, you can install this policy package using the
-   <command>semodule</> command, which links supplied policy packages and
-   loads them into the kernel space.  If this package is correctly installed,
-   <literal><command>semodule</> -l</> should list sepgsql-regtest as an
-   available policy package.
-  </para>
-
-<screen>
-$ make -C ./contrib/sepgsql -f /usr/share/selinux/devel/Makefile
-$ su
-# semodule -u ./contrib/sepgsql/sepgsql-regtest.pp
-# semodule -l
-    :
-sepgsql-regtest 1.03
-    :
-</screen>
-
-  <para>
-   Second, turn on <literal>sepgsql_regression_test_mode</>.
-   We don't enable all the rules in the <filename>sepgsql-regtest.pp</>
-   by default, for your system's safety.
-   The <literal>sepgsql_regression_test_mode</literal> parameter is associated
-   with rules to launch regression test.
-   It can be turned on using <command>setsebool</> command.
-  </para>
-
-<screen>
-$ su
-# setsebool sepgsql_regression_test_mode on
-# getsebool sepgsql_regression_test_mode
-sepgsql_regression_test_mode --> on
-</screen>
-
-  <para>
-   Last, kick the regression test from the <literal>unconfined_t</> domain.
-  </para>
-
-  <para>
-   The <command>id</> command tells us the current working domain.
-   Confirm your shell is now performing with the <literal>unconfined_t</>
-   domain as follows.
-  </para>
-<screen>
-$ id -Z
-unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
-</screen>
-
-  <para>
-   See <xref linkend="sepgsql-resources"> for details on adjusting your
-   working domain, if necessary.
-  </para>
-
-  <para>
-   If <command>pg_regress</> fails to launch the <command>psql</> command,
-   you may need to ensure that the <command>psql</> command is labeled
-   as <literal>bin_t</>.  If it is not, the <command>restorecon</> command can
-   often be used to fix up security labels within the
-   <productname>PostgreSQL</productname> installation directory.
-  </para>
-
-<screen>
-$ restorecon -R /usr/local/pgsql/
-</screen>
- </sect2>
-
- <sect2 id="sepgsql-parameters">
-  <title>GUC Parameters</title>
-
-  <variablelist>
-   <varlistentry id="guc-sepgsql-permissive" xreflabel="sepgsql.permissive">
-    <term><varname>sepgsql.permissive</> (<type>boolean</type>)</term>
-    <indexterm>
-     <primary><varname>sepgsql.permissive</> configuration parameter</primary>
-    </indexterm>
-    <listitem>
-     <para>
-      This parameter enables <productname>SE-PostgreSQL</> to function
-      in permissive mode, regardless of the system setting.
-      The default is off.
-      This parameter can only be set in the <filename>postgresql.conf</>
-      file or on the server command line.
-     </para>
-
-     <para>
-      When this parameter is on, <productname>SE-PostgreSQL</> functions
-      in permissive mode, even if the platform system is working in enforcing
-      mode.  This parameter is primarily useful for testing purposes.
-     </para>
-    </listitem>
-
-   </varlistentry>
-   <varlistentry id="guc-sepgsql-debug-audit" xreflabel="sepgsql.debug_audit">
-    <term><varname>sepgsql.debug_audit</> (<type>boolean</>)</>
-    <indexterm>
-     <primary><varname>sepgsql.debug_audit</> configuration parameter</>
-    </indexterm>
-    <listitem>
-     <para>
-      This parameter enables the printing of audit messages independent from
-      the policy setting.
-      The default is off (according to the security policy setting).
-     </para>
-
-     <para>
-      The security policy of <productname>SELinux</> also has rules to
-      control whether or not particular accesses are logged.
-      By default, access violations are logged, but allowed
-      accesses are not.
-     </para>
-
-     <para>
-      This parameter forces all possible logging to be turned on, regardless
-      of the system policy.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </sect2>
-
- <sect2 id="sepgsql-features">
-  <title>Features</title>
-  <sect3>
-   <title>Controlled Object Classes</title>
-   <para>
-    The security model of <productname>SELinux</> describes all the access
-    control rules as a relationship between a subject entity (typically,
-    it is a client of database) and an object entity, each of which is
-    identified by a security label.  If access to an unlabelled object is
-    attempted, the object is treated as if it were assigned the label
-    <literal>unlabeled_t</>.
-   </para>
-
-   <para>
-    Currently, <productname>sepgsql</productname> allows security labels to be
-    assigned to schemas, tables, columns, sequences, views, and functions.
-    When <productname>sepgsql</productname> is in use, security labels are
-    automatically assigned to supported database objects at creation time.
-    This label is called as a default security label, being decided according
-    to the system security policy, which takes as input the creator's label
-    and the label assigned to the new object's parent object.
-   </para>
-
-   <para>
-    A new database object basically inherits the security label of the parent
-    object, except when the security policy has special rules known as
-    type-transition rules, in which case a different label may be applied.
-    For schemas, the parent object is the current database; for columns, it
-    is the corresponding table; for tables, sequences, views, and functions,
-    it is the containing schema.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title>DML Permissions</title>
-
-   <para>
-    For tables, <literal>db_table:select</>, <literal>db_table:insert</>,
-    <literal>db_table:update</> or <literal>db_table:delete</> is
-    checked for all the referenced target tables depending on the sort of
-    statement;
-    in addition, <literal>db_table:select</> is also checked for
-    all the tables that contain the columns referenced in the
-    <literal>WHERE</> or <literal>RETURNING</> clause, as a data source
-    of <literal>UPDATE</>, and so on.
-   </para>
-
-   <para>
-<synopsis>
-UPDATE t1 SET x = 2, y = md5sum(y) WHERE z = 100;
-</synopsis>
-
-    In this case, we must have <literal>db_table:select</> in addition to
-    <literal>db_table:update</>, because <literal>t1.a</> is referenced
-    within the <literal>WHERE</> clause.  Column-level permissions will also be
-    checked for each referenced column.
-   </para>
-
-   <para>
-    The client must be allowed to access all referenced tables and
-    columns, even if they originated from views which were then expanded,
-    so that we apply consistent access control rules independent of the manner
-    in which the table contents are referenced.
-   </para>
-
-   <para>
-    For columns, <literal>db_column:select</> is checked on
-    not only the columns being read using <literal>SELECT</>, but being
-    referenced in other DML statements.
-   </para>
-
-   <para>
-    Of course, it also checks <literal>db_column:update</> or
-    <literal>db_column:insert</> on the column being modified by
-    <literal>UPDATE</> or <literal>INSERT</>.
-   </para>
-
-   <para>
-<synopsis>
-UPDATE t1 SET x = 2, y = md5sum(y) WHERE z = 100;
-</synopsis>
-    In this case, it checks <literal>db_column:update</> on
-    the <literal>t1.x</> being updated, <literal>db_column:{select update}</>
-    on the <literal>t1.y</> being updated and referenced,
-    and <literal>db_column:select</> on the <literal>t1.z</> being only
-    referenced in the <literal>WHERE</> clause.
-    <literal>db_table:{select update}</> will also be checked
-    at the table level.
-   </para>
-
-   <para>
-    For sequences, <literal>db_sequence:get_value</> is checked when we
-    reference a sequence object using <literal>SELECT</>; however, note that we
-    do not currently check permissions on execution of corresponding functions
-    such as <literal>lastval()</>.
-   </para>
-
-   <para>
-    For views, <literal>db_view:expand</> shall be checked, then any other
-    corresponding permissions shall be also checked on the objects being
-    expanded from the view, individually.
-   </para>
-
-   <para>
-    For functions, <literal>db_procedure:{execute}</> is defined, but not
-    checked in this version.
-   </para>
-
-   <para>
-    The default database privilege system allows database superusers to
-    modify system catalogs using DML commands, and reference or modify
-    toast tables.  These operations are prohibited when
-    <productname>sepgsql</> is enabled.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title>DDL Permissions</title>
-   <para>
-    On <xref linkend="sql-security-label"> command, <literal>setattr</> and
-    <literal>relabelfrom</> shall be checked on the object being relabeled
-    with an old security label, then <literal>relabelto</> on the supplied
-    new security label.
-   </para>
-
-   <para>
-    In the case where multiple label providers are installed and the user tries
-    to set a security label, but is not managed by <productname>SELinux</>,
-    only <literal>setattr</> should be checked here.
-    This is currently not checked due to implementation restrictions.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title>Trusted Procedure</title>
-   <para>
-    Trusted procedures are similar to security definer functions or set-uid
-    commands. <productname>SELinux</> provides a feature to allow trusted
-    code to run using a security label different from that of the client,
-    generally for the purpose of providing highly controlled access to
-    sensitive data (e.g. rows might be omitted, or the precision of stored
-    values might be reduced).  Whether or not a function acts as a trusted
-    procedure is controlled by its security label and the operating system
-    security policy.  For example:
-   </para>
-
-<screen>
-postgres=# CREATE TABLE customer (
-               cid     int primary key,
-               cname   text,
-               credit  text
-           );
-CREATE TABLE
-postgres=# SECURITY LABEL ON COLUMN customer.credit
-               IS 'system_u:object_r:sepgsql_secret_table_t:s0';
-SECURITY LABEL
-postgres=# CREATE FUNCTION show_credit(int) RETURNS text
-             AS 'SELECT regexp_replace(credit, ''-[0-9]+$'', ''-xxxx'', ''g'')
-                        FROM customer WHERE cid = $1'
-           LANGUAGE sql;
-CREATE FUNCTION
-postgres=# SECURITY LABEL ON FUNCTION show_credit(int)
-               IS 'system_u:object_r:sepgsql_trusted_proc_exec_t:s0';
-SECURITY LABEL
-</screen>
-
-   <para>
-    The above operations should be performed by an administrative user.
-   </para>
-
-<screen>
-postgres=# SELECT * FROM customer;
-ERROR:  SELinux: security policy violation
-postgres=# SELECT cid, cname, show_credit(cid) FROM customer;
- cid | cname  |     show_credit
------+--------+---------------------
-   1 | taro   | 1111-2222-3333-xxxx
-   2 | hanako | 5555-6666-7777-xxxx
-(2 rows)
-</screen>
-
-   <para>
-    In this case, a regular user cannot reference <literal>customer.credit</>
-    directly, but a trusted procedure <literal>show_credit</> enables us
-    to print the credit card number of customers with some of the digits masked
-    out.
-   </para>
-  </sect3>
-
-  <sect3>
-   <title>Miscellaneous</title>
-   <para>
-    We reject the <xref linkend="sql-load"> command across the board, because
-    any module loaded could easily circumvent security policy enforcement.
-   </para>
-
-  </sect3>
- </sect2>
-
- <sect2 id="sepgsql-limitations">
-  <title>Limitations</title>
-
-  <variablelist>
-   <varlistentry>
-    <term>Userspace access vector cache</term>
-    <listitem>
-     <para>
-      <productname>sepgsql</> does not yet support an access vector cache.
-      This would likely improve performance.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Data Definition Language (DDL) Permissions</term>
-    <listitem>
-     <para>
-      Due to implementation restrictions, DDL permissions are not checked.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Data Control Language (DCL) Permissions</term>
-    <listitem>
-     <para>
-      Due to implementation restrictions, DCL permissions are not checked.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Row-level access control</term>
-    <listitem>
-     <para>
-      <productname>PostgreSQL</> does not support row-level access; therefore,
-      <productname>sepgsql</productname> does not support it either.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Covert channels</term>
-    <listitem>
-     <para>
-      <productname>sepgsql</> never tries to hide existence of
-      a certain object, even if the user is not allowed to the reference.
-      For example, we can infer the existence of an invisible object as
-      a result of primary key conflicts, foreign key violations, and so on,
-      even if we cannot reference contents of these objects.  The existence
-      of a top secret table cannot be hidden; we only hope to conceal its
-      contents.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </sect2>
-
- <sect2 id="sepgsql-resources">
-  <title>External Resources</title>
-  <variablelist>
-   <varlistentry>
-    <term><ulink url="http://wiki.postgresql.org/wiki/SEPostgreSQL">SE-PostgreSQL Introduction</ulink></term>
-    <listitem>
-     <para>
-      This wiki page provides a brief-overview, security design, architecture,
-      administration and upcoming features.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry>
-    <term><ulink url="http://docs.fedoraproject.org/selinux-user-guide/">Fedora SELinux User Guide</ulink></term>
-    <listitem>
-     <para>
-      This document provides a wide spectrum of knowledge to administer
-      <productname>SELinux</> on your systems.
-      It focuses primarily on Fedora, but is not limited to Fedora.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry>
-    <term><ulink url="http://docs.fedoraproject.org/selinux-faq">Fedora SELinux FAQ</ulink></term>
-    <listitem>
-     <para>
-      This document answers frequently asked questions about
-      <productname>SELinux</productname>.
-      It focuses primarily on Fedora, but is not limited to Fedora.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </sect2>
-
- <sect2 id="sepgsql-author">
-  <title>Author</title>
-  <para>
-   KaiGai Kohei <email>[email protected]</email>
-  </para>
- </sect2>
-</sect1>
diff --git a/doc-xc/src/sgml/sourcerepo.sgmlin b/doc-xc/src/sgml/sourcerepo.sgmlin
deleted file mode 100644
index 9a218e9329..0000000000
--- a/doc-xc/src/sgml/sourcerepo.sgmlin
+++ /dev/null
@@ -1,268 +0,0 @@
-<!-- doc/src/sgml/sourcerepo.sgml -->
-
-<appendix id="sourcerepo">
- <title>The Source Code Repository</title>
-
-<!## PG>
- <para>
-  The <productname>PostgreSQL</productname> source code is stored and managed
-  using the <productname>Git</productname> version control system. A public
-  mirror of the master repository is available; it is updated within a minute
-  of any change to the master repository.
- </para>
-
- <para>
-  Our wiki, <ulink
-  url="http://wiki.postgresql.org/wiki/Working_with_Git"></ulink>,
-  has some discussion on working with Git.
- </para>
-
-  <para>
-   Note that building <productname>PostgreSQL</productname> from the source
-   repository requires reasonably up-to-date versions of <application>bison</>,
-   <application>flex</>, and <application>Perl</>. These tools are not needed
-   to build from a distribution tarball since the files they are used to build
-   are included in the tarball.  Other tool requirements are the same as shown
-   in <xref linkend="installation">.
-  </para>
-<!## end>
-<!## XC>
-&xconly;
- <para>
-  The <productname>Postgres-XC</productname> source code is stored and managed
-  using the <productname>Git</productname> version control system. A public
-  mirror of the master repository is available; it is updated within a minute
-  of any change to the master repository.
- </para>
-
-  <para>
-   Note that building <productname>Postgres-XC</productname> from the source
-   repository requires reasonably up-to-date versions of <application>bison</>,
-   <application>flex</>, and <application>Perl</>. These tools are not needed
-   to build from a distribution tarball since the files they are used to build
-   are included in the tarball.  Other tool requirements are the same as shown
-   in <xref linkend="installation">.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
- <para>
-  The <productname>Postgres-XL</productname> source code is stored and managed
-  using the <productname>Git</productname> version control system. A public
-  mirror of the master repository is available; it is updated within a minute
-  of any change to the master repository.
- </para>
-
-  <para>
-   Note that building <productname>Postgres-XL</productname> from the source
-   repository requires reasonably up-to-date versions of <application>bison</>,
-   <application>flex</>, and <application>Perl</>. These tools are not needed
-   to build from a distribution tarball since the files they are used to build
-   are included in the tarball.  Other tool requirements are the same as shown
-   in <xref linkend="installation">.
-  </para>
-<!## end>
-
- <sect1 id="git">
-  <title>Getting The Source via <productname>Git</></title>
-
-<!## PG>
-  <para>
-   With <productname>Git</> you will make a copy of the entire code repository
-   on your local machine, so you will have access to all history and branches
-   offline. This is the fastest and most flexible way to develop or test
-   patches.
-  </para>
-
-  <procedure>
-   <title>Git</title>
-
-   <step>
-    <para>
-     You will need an installed version of <productname>Git</>, which you can
-     get from <ulink url="http://git-scm.com"></ulink>. Many systems already
-     have a recent version of <application>Git</> installed by default, or
-     available in their package distribution system.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     To begin using the Git repository, make a clone of the official mirror:
-
-<programlisting>
-<!## XC>
-git clone git://postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc
-<!## end>
-<!## XL>
-git clone git://git.code.sf.net/p/postgres-xl/postgres-xl 
-<!## end>
-</programlisting>
-
-     This will copy the full repository to your local machine, so it may take
-     a while to complete, especially if you have a slow Internet connection.
-     The files will be placed in a new subdirectory <filename>postgresql</> of
-     your current directory.
-    </para>
-
-    <para>
-     The Git mirror can also be reached via the HTTP protocol, if for example
-     a firewall is blocking access to the Git protocol. Just change the URL
-     prefix to <literal>http</>, as in:
-
-<programlisting>
-<!## XC>
-git clone http://postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc
-<!## end>
-<!## XL>
-git clone git://git.code.sf.net/p/postgres-xl/postgres-xl 
-<!## end>
-</programlisting>
-
-     The HTTP protocol is less efficient than the Git protocol, so it will be
-     slower to use.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Whenever you want to get the latest updates in the system, <command>cd</>
-     into the repository, and run:
-
-<programlisting>
-git fetch
-</programlisting>
-    </para>
-   </step>
-  </procedure>
-
-  <para>
-   <productname>Git</> can do a lot more things than just fetch the source. For
-   more information, consult the <productname>Git</> man pages, or see the
-   website at <ulink url="http://git-scm.com"></>.
-  </para>
-<!## end>
-<!## XC>
-&xconly;
-  <para>
-   With <productname>Git</> you will make a copy of the entire code repository
-   on your local machine, so you will have access to all history and branches
-   offline. This is the fastest and most flexible way to develop or test
-   patches.
-  </para>
-
-  <procedure>
-   <title>Git</title>
-
-   <step>
-    <para>
-     You will need an installed version of <productname>Git</>, which you can
-     get from <ulink url="http://git-scm.com"></ulink>. Many systems already
-     have a recent version of <application>Git</> installed by default, or
-     available in their package distribution system.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     To begin using the Git repository, make a clone of the official mirror:
-
-<programlisting>
-<!## XC>
-git clone git://postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc
-<!## end>
-<!## XL>
-git clone git://git.code.sf.net/p/postgres-xl/postgres-xl
-<!## end>
-</programlisting>
-
-     This will copy the full repository to your local machine, so it may take
-     a while to complete, especially if you have a slow Internet connection.
-     The files will be placed in a new subdirectory <filename>postgresql</> of
-     your current directory.
-    </para>
-
-   </step>
-
-   <step>
-    <para>
-     Whenever you want to get the latest updates in the system, <command>cd</>
-     into the repository, and run:
-
-<programlisting>
-git fetch
-</programlisting>
-    </para>
-   </step>
-  </procedure>
-
-  <para>
-   <productname>Git</> can do a lot more things than just fetch the source. For
-   more information, consult the <productname>Git</> man pages, or see the
-   website at <ulink url="http://git-scm.com"></>.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   With <productname>Git</> you will make a copy of the entire code repository
-   on your local machine, so you will have access to all history and branches
-   offline. This is the fastest and most flexible way to develop or test
-   patches.
-  </para>
-
-  <procedure>
-   <title>Git</title>
-
-   <step>
-    <para>
-     You will need an installed version of <productname>Git</>, which you can
-     get from <ulink url="http://git-scm.com"></ulink>. Many systems already
-     have a recent version of <application>Git</> installed by default, or
-     available in their package distribution system.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     To begin using the Git repository, make a clone of the official mirror:
-
-<programlisting>
-<!## XC>
-git clone git://postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc
-<!## end>
-<!## XL>
-git clone git://git.code.sf.net/p/postgres-xl/postgres-xl
-<!## end>
-</programlisting>
-
-     This will copy the full repository to your local machine, so it may take
-     a while to complete, especially if you have a slow Internet connection.
-     The files will be placed in a new subdirectory <filename>postgresql</> of
-     your current directory.
-    </para>
-
-   </step>
-
-   <step>
-    <para>
-     Whenever you want to get the latest updates in the system, <command>cd</>
-     into the repository, and run:
-
-<programlisting>
-git fetch
-</programlisting>
-    </para>
-   </step>
-  </procedure>
-
-  <para>
-   <productname>Git</> can do a lot more things than just fetch the source. For
-   more information, consult the <productname>Git</> man pages, or see the
-   website at <ulink url="http://git-scm.com"></>.
-  </para>
-<!## end>
-
- </sect1>
-
-</appendix>
diff --git a/doc-xc/src/sgml/sources.sgmlin b/doc-xc/src/sgml/sources.sgmlin
deleted file mode 100644
index 54d1ccbf4b..0000000000
--- a/doc-xc/src/sgml/sources.sgmlin
+++ /dev/null
@@ -1,792 +0,0 @@
-<!-- doc/src/sgml/sources.sgml -->
-
- <chapter id="source">
-<!## PG>
-  <title>PostgreSQL Coding Conventions</title>
-<!## end>
-<!## XC>
-  <title>Postgres-XC Coding Conventions</title>
-<!## end>
-<!## XL>
-  <title>Postgres-XL Coding Conventions</title>
-<!## end>
-
-&common;
-
-  <sect1 id="source-format">
-   <title>Formatting</title>
-
-&common;
-   <para>
-    Source code formatting uses 4 column tab spacing, with
-    tabs preserved (i.e., tabs are not expanded to spaces).
-    Each logical indentation level is one additional tab stop.
-   </para>
-
-   <para>
-    Layout rules (brace positioning, etc) follow BSD conventions.  In
-    particular, curly braces for the controlled blocks of <literal>if</>,
-    <literal>while</>, <literal>switch</>, etc go on their own lines.
-   </para>
-
-   <para>
-    Limit line lengths so that the code is readable in an 80-column window.
-    (This doesn't mean that you must never go past 80 columns.  For instance,
-    breaking a long error message string in arbitrary places just to keep the
-    code within 80 columns is probably not a net gain in readability.)
-   </para>
-
-   <para>
-    Do not use C++ style comments (<literal>//</> comments).  Strict ANSI C
-    compilers do not accept them.  For the same reason, do not use C++
-    extensions such as declaring new variables mid-block.
-   </para>
-
-   <para>
-    The preferred style for multi-line comment blocks is
-<programlisting>
-/*
- * comment text begins here
- * and continues here
- */
-</programlisting>
-    Note that comment blocks that begin in column 1 will be preserved as-is
-    by <application>pgindent</>, but it will re-flow indented comment blocks
-    as though they were plain text.  If you want to preserve the line breaks
-    in an indented block, add dashes like this:
-<programlisting>
-    /*----------
-     * comment text begins here
-     * and continues here
-     *----------
-     */
-</programlisting>
-   </para>
-
-   <para>
-    While submitted patches do not absolutely have to follow these formatting
-    rules, it's a good idea to do so.  Your code will get run through
-    <application>pgindent</> before the next release, so there's no point in
-    making it look nice under some other set of formatting conventions.
-    A good rule of thumb for patches is <quote>make the new code look like
-    the existing code around it</>.
-   </para>
-
-   <para>
-    The <filename>src/tools</filename> directory contains sample settings
-    files that can be used with the <productname>emacs</productname>,
-    <productname>xemacs</productname> or <productname>vim</productname>
-    editors to help ensure that they format code according to these
-    conventions.
-   </para>
-
-   <para>
-    The text browsing tools <application>more</application> and
-    <application>less</application> can be invoked as:
-<programlisting>
-more -x4
-less -x4
-</programlisting>
-    to make them show tabs appropriately.
-   </para>
-  </sect1>
-
-  <sect1 id="error-message-reporting">
-   <title>Reporting Errors Within the Server</title>
-
-   <indexterm>
-    <primary>ereport</primary>
-   </indexterm>
-   <indexterm>
-    <primary>elog</primary>
-   </indexterm>
-
-&common;
-   <para>
-    Error, warning, and log messages generated within the server code
-    should be created using <function>ereport</>, or its older cousin
-    <function>elog</>.  The use of this function is complex enough to
-    require some explanation.
-   </para>
-
-   <para>
-    There are two required elements for every message: a severity level
-    (ranging from <literal>DEBUG</> to <literal>PANIC</>) and a primary
-    message text.  In addition there are optional elements, the most
-    common of which is an error identifier code that follows the SQL spec's
-    SQLSTATE conventions.
-    <function>ereport</> itself is just a shell function, that exists
-    mainly for the syntactic convenience of making message generation
-    look like a function call in the C source code.  The only parameter
-    accepted directly by <function>ereport</> is the severity level.
-    The primary message text and any optional message elements are
-    generated by calling auxiliary functions, such as <function>errmsg</>,
-    within the <function>ereport</> call.
-   </para>
-
-   <para>
-    A typical call to <function>ereport</> might look like this:
-<programlisting>
-ereport(ERROR,
-        (errcode(ERRCODE_DIVISION_BY_ZERO),
-         errmsg("division by zero")));
-</programlisting>
-    This specifies error severity level <literal>ERROR</> (a run-of-the-mill
-    error).  The <function>errcode</> call specifies the SQLSTATE error code
-    using a macro defined in <filename>src/include/utils/errcodes.h</>.  The
-    <function>errmsg</> call provides the primary message text.  Notice the
-    extra set of parentheses surrounding the auxiliary function calls &mdash;
-    these are annoying but syntactically necessary.
-   </para>
-
-   <para>
-    Here is a more complex example:
-<programlisting>
-ereport(ERROR,
-        (errcode(ERRCODE_AMBIGUOUS_FUNCTION),
-         errmsg("function %s is not unique",
-                func_signature_string(funcname, nargs,
-                                      NIL, actual_arg_types)),
-         errhint("Unable to choose a best candidate function. "
-                 "You might need to add explicit typecasts.")));
-</programlisting>
-    This illustrates the use of format codes to embed run-time values into
-    a message text.  Also, an optional <quote>hint</> message is provided.
-   </para>
-
-   <para>
-    The available auxiliary routines for <function>ereport</> are:
-  <itemizedlist>
-   <listitem>
-    <para>
-     <function>errcode(sqlerrcode)</function> specifies the SQLSTATE error identifier
-     code for the condition.  If this routine is not called, the error
-     identifier defaults to
-     <literal>ERRCODE_INTERNAL_ERROR</> when the error severity level is
-     <literal>ERROR</> or higher, <literal>ERRCODE_WARNING</> when the
-     error level is <literal>WARNING</>, otherwise (for <literal>NOTICE</>
-     and below) <literal>ERRCODE_SUCCESSFUL_COMPLETION</>.
-     While these defaults are often convenient, always think whether they
-     are appropriate before omitting the <function>errcode()</> call.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errmsg(const char *msg, ...)</function> specifies the primary error
-     message text, and possibly run-time values to insert into it.  Insertions
-     are specified by <function>sprintf</>-style format codes.  In addition to
-     the standard format codes accepted by <function>sprintf</>, the format
-     code <literal>%m</> can be used to insert the error message returned
-     by <function>strerror</> for the current value of <literal>errno</>.
-     <footnote>
-      <para>
-       That is, the value that was current when the <function>ereport</> call
-       was reached; changes of <literal>errno</> within the auxiliary reporting
-       routines will not affect it.  That would not be true if you were to
-       write <literal>strerror(errno)</> explicitly in <function>errmsg</>'s
-       parameter list; accordingly, do not do so.
-      </para>
-     </footnote>
-     <literal>%m</> does not require any
-     corresponding entry in the parameter list for <function>errmsg</>.
-     Note that the message string will be run through <function>gettext</>
-     for possible localization before format codes are processed.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errmsg_internal(const char *msg, ...)</function> is the same as
-     <function>errmsg</>, except that the message string will not be
-     translated nor included in the internationalization message dictionary.
-     This should be used for <quote>cannot happen</> cases that are probably
-     not worth expending translation effort on.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errmsg_plural(const char *fmt_singular, const char *fmt_plural,
-     unsigned long n, ...)</function> is like <function>errmsg</>, but with
-     support for various plural forms of the message.
-     <replaceable>fmt_singular</> is the English singular format,
-     <replaceable>fmt_plural</> is the English plural format,
-     <replaceable>n</> is the integer value that determines which plural
-     form is needed, and the remaining arguments are formatted according
-     to the selected format string.  For more information see
-     <xref linkend="nls-guidelines">.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errdetail(const char *msg, ...)</function> supplies an optional
-     <quote>detail</> message; this is to be used when there is additional
-     information that seems inappropriate to put in the primary message.
-     The message string is processed in just the same way as for
-     <function>errmsg</>.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errdetail_log(const char *msg, ...)</function> is the same as
-     <function>errdetail</> except that this string goes only to the server
-     log, never to the client.  If both <function>errdetail</> and
-     <function>errdetail_log</> are used then one string goes to the client
-     and the other to the log.  This is useful for error details that are
-     too security-sensitive or too bulky to include in the report
-     sent to the client.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errdetail_plural(const char *fmt_singular, const char *fmt_plural,
-     unsigned long n, ...)</function> is like <function>errdetail</>, but with
-     support for various plural forms of the message.
-     For more information see <xref linkend="nls-guidelines">.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errhint(const char *msg, ...)</function> supplies an optional
-     <quote>hint</> message; this is to be used when offering suggestions
-     about how to fix the problem, as opposed to factual details about
-     what went wrong.
-     The message string is processed in just the same way as for
-     <function>errmsg</>.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errcontext(const char *msg, ...)</function> is not normally called
-     directly from an <function>ereport</> message site; rather it is used
-     in <literal>error_context_stack</> callback functions to provide
-     information about the context in which an error occurred, such as the
-     current location in a PL function.
-     The message string is processed in just the same way as for
-     <function>errmsg</>.  Unlike the other auxiliary functions, this can
-     be called more than once per <function>ereport</> call; the successive
-     strings thus supplied are concatenated with separating newlines.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errposition(int cursorpos)</function> specifies the textual location
-     of an error within a query string.  Currently it is only useful for
-     errors detected in the lexical and syntactic analysis phases of
-     query processing.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errcode_for_file_access()</> is a convenience function that
-     selects an appropriate SQLSTATE error identifier for a failure in a
-     file-access-related system call.  It uses the saved
-     <literal>errno</> to determine which error code to generate.
-     Usually this should be used in combination with <literal>%m</> in the
-     primary error message text.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errcode_for_socket_access()</> is a convenience function that
-     selects an appropriate SQLSTATE error identifier for a failure in a
-     socket-related system call.
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <function>errhidestmt(bool hide_stmt)</function> can be called to specify
-     suppression of the <literal>STATEMENT:</> portion of a message in the
-     postmaster log.  Generally this is appropriate if the message text
-     includes the current statement already.
-    </para>
-   </listitem>
-  </itemizedlist>
-   </para>
-
-   <para>
-    There is an older function <function>elog</> that is still heavily used.
-    An <function>elog</> call:
-<programlisting>
-elog(level, "format string", ...);
-</programlisting>
-    is exactly equivalent to:
-<programlisting>
-ereport(level, (errmsg_internal("format string", ...)));
-</programlisting>
-    Notice that the SQLSTATE error code is always defaulted, and the message
-    string is not subject to translation.
-    Therefore, <function>elog</> should be used only for internal errors and
-    low-level debug logging.  Any message that is likely to be of interest to
-    ordinary users should go through <function>ereport</>.  Nonetheless,
-    there are enough internal <quote>cannot happen</> error checks in the
-    system that <function>elog</> is still widely used; it is preferred for
-    those messages for its notational simplicity.
-   </para>
-
-   <para>
-    Advice about writing good error messages can be found in
-    <xref linkend="error-style-guide">.
-   </para>
-  </sect1>
-
-  <sect1 id="error-style-guide">
-   <title>Error Message Style Guide</title>
-
-&common;
-   <para>
-    This style guide is offered in the hope of maintaining a consistent,
-    user-friendly style throughout all the messages generated by
-<!## PG>
-    <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</>.
-<!## end>
-   </para>
-
-  <simplesect>
-   <title>What Goes Where</title>
-
-   <para>
-    The primary message should be short, factual, and avoid reference to
-    implementation details such as specific function names.
-    <quote>Short</quote> means <quote>should fit on one line under normal
-    conditions</quote>.  Use a detail message if needed to keep the primary
-    message short, or if you feel a need to mention implementation details
-    such as the particular system call that failed. Both primary and detail
-    messages should be factual.  Use a hint message for suggestions about what
-    to do to fix the problem, especially if the suggestion might not always be
-    applicable.
-   </para>
-
-   <para>
-    For example, instead of:
-<programlisting>
-IpcMemoryCreate: shmget(key=%d, size=%u, 0%o) failed: %m
-(plus a long addendum that is basically a hint)
-</programlisting>
-    write:
-<programlisting>
-Primary:    could not create shared memory segment: %m
-Detail:     Failed syscall was shmget(key=%d, size=%u, 0%o).
-Hint:       the addendum
-</programlisting>
-   </para>
-
-   <para>
-    Rationale: keeping the primary message short helps keep it to the point,
-    and lets clients lay out screen space on the assumption that one line is
-    enough for error messages.  Detail and hint messages can be relegated to a
-    verbose mode, or perhaps a pop-up error-details window.  Also, details and
-    hints would normally be suppressed from the server log to save
-    space. Reference to implementation details is best avoided since users
-    don't know the details anyway.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Formatting</title>
-
-   <para>
-    Don't put any specific assumptions about formatting into the message
-    texts.  Expect clients and the server log to wrap lines to fit their own
-    needs.  In long messages, newline characters (\n) can be used to indicate
-    suggested paragraph breaks.  Don't end a message with a newline.  Don't
-    use tabs or other formatting characters.  (In error context displays,
-    newlines are automatically added to separate levels of context such as
-    function calls.)
-   </para>
-
-   <para>
-    Rationale: Messages are not necessarily displayed on terminal-type
-    displays.  In GUI displays or browsers these formatting instructions are
-    at best ignored.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Quotation Marks</title>
-
-   <para>
-    English text should use double quotes when quoting is appropriate.
-    Text in other languages should consistently use one kind of quotes that is
-    consistent with publishing customs and computer output of other programs.
-   </para>
-
-   <para>
-    Rationale: The choice of double quotes over single quotes is somewhat
-    arbitrary, but tends to be the preferred use.  Some have suggested
-    choosing the kind of quotes depending on the type of object according to
-    SQL conventions (namely, strings single quoted, identifiers double
-    quoted).  But this is a language-internal technical issue that many users
-    aren't even familiar with, it won't scale to other kinds of quoted terms,
-    it doesn't translate to other languages, and it's pretty pointless, too.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Use of Quotes</title>
-
-   <para>
-    Use quotes always to delimit file names, user-supplied identifiers, and
-    other variables that might contain words.  Do not use them to mark up
-    variables that will not contain words (for example, operator names).
-   </para>
-
-   <para>
-    There are functions in the backend that will double-quote their own output
-    at need (for example, <function>format_type_be()</function>).  Do not put
-    additional quotes around the output of such functions.
-   </para>
-
-   <para>
-    Rationale: Objects can have names that create ambiguity when embedded in a
-    message.  Be consistent about denoting where a plugged-in name starts and
-    ends.  But don't clutter messages with unnecessary or duplicate quote
-    marks.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Grammar and Punctuation</title>
-
-   <para>
-    The rules are different for primary error messages and for detail/hint
-    messages:
-   </para>
-
-   <para>
-    Primary error messages: Do not capitalize the first letter.  Do not end a
-    message with a period.  Do not even think about ending a message with an
-    exclamation point.
-   </para>
-
-   <para>
-    Detail and hint messages: Use complete sentences, and end each with
-    a period.  Capitalize the first word of sentences.  Put two spaces after
-    the period if another sentence follows (for English text; might be
-    inappropriate in other languages).
-   </para>
-
-   <para>
-    Error context strings: Do not capitalize the first letter and do
-    not end the string with a period.  Context strings should normally
-    not be complete sentences.
-   </para>
-
-   <para>
-    Rationale: Avoiding punctuation makes it easier for client applications to
-    embed the message into a variety of grammatical contexts.  Often, primary
-    messages are not grammatically complete sentences anyway.  (And if they're
-    long enough to be more than one sentence, they should be split into
-    primary and detail parts.)  However, detail and hint messages are longer
-    and might need to include multiple sentences.  For consistency, they should
-    follow complete-sentence style even when there's only one sentence.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Upper Case vs. Lower Case</title>
-
-   <para>
-    Use lower case for message wording, including the first letter of a
-    primary error message.  Use upper case for SQL commands and key words if
-    they appear in the message.
-   </para>
-
-   <para>
-    Rationale: It's easier to make everything look more consistent this
-    way, since some messages are complete sentences and some not.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Avoid Passive Voice</title>
-
-   <para>
-    Use the active voice.  Use complete sentences when there is an acting
-    subject (<quote>A could not do B</quote>).  Use telegram style without
-    subject if the subject would be the program itself; do not use
-    <quote>I</quote> for the program.
-   </para>
-
-   <para>
-    Rationale: The program is not human.  Don't pretend otherwise.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Present vs. Past Tense</title>
-
-   <para>
-    Use past tense if an attempt to do something failed, but could perhaps
-    succeed next time (perhaps after fixing some problem).  Use present tense
-    if the failure is certainly permanent.
-   </para>
-
-   <para>
-    There is a nontrivial semantic difference between sentences of the form:
-<programlisting>
-could not open file "%s": %m
-</programlisting>
-and:
-<programlisting>
-cannot open file "%s"
-</programlisting>
-    The first one means that the attempt to open the file failed.  The
-    message should give a reason, such as <quote>disk full</quote> or
-    <quote>file doesn't exist</quote>.  The past tense is appropriate because
-    next time the disk might not be full anymore or the file in question might
-    exist.
-   </para>
-
-   <para>
-    The second form indicates that the functionality of opening the named file
-    does not exist at all in the program, or that it's conceptually
-    impossible.  The present tense is appropriate because the condition will
-    persist indefinitely.
-   </para>
-
-   <para>
-    Rationale: Granted, the average user will not be able to draw great
-    conclusions merely from the tense of the message, but since the language
-    provides us with a grammar we should use it correctly.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Type of the Object</title>
-
-   <para>
-    When citing the name of an object, state what kind of object it is.
-   </para>
-
-   <para>
-    Rationale: Otherwise no one will know what <quote>foo.bar.baz</>
-    refers to.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Brackets</title>
-
-   <para>
-    Square brackets are only to be used (1) in command synopses to denote
-    optional arguments, or (2) to denote an array subscript.
-   </para>
-
-   <para>
-    Rationale: Anything else does not correspond to widely-known customary
-    usage and will confuse people.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Assembling Error Messages</title>
-
-   <para>
-   When a message includes text that is generated elsewhere, embed it in
-   this style:
-<programlisting>
-could not open file %s: %m
-</programlisting>
-   </para>
-
-   <para>
-    Rationale: It would be difficult to account for all possible error codes
-    to paste this into a single smooth sentence, so some sort of punctuation
-    is needed.  Putting the embedded text in parentheses has also been
-    suggested, but it's unnatural if the embedded text is likely to be the
-    most important part of the message, as is often the case.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Reasons for Errors</title>
-
-   <para>
-    Messages should always state the reason why an error occurred.
-    For example:
-<programlisting>
-BAD:    could not open file %s
-BETTER: could not open file %s (I/O failure)
-</programlisting>
-    If no reason is known you better fix the code.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Function Names</title>
-
-   <para>
-    Don't include the name of the reporting routine in the error text. We have
-    other mechanisms for finding that out when needed, and for most users it's
-    not helpful information.  If the error text doesn't make as much sense
-    without the function name, reword it.
-<programlisting>
-BAD:    pg_atoi: error in "z": cannot parse "z"
-BETTER: invalid input syntax for integer: "z"
-</programlisting>
-   </para>
-
-   <para>
-    Avoid mentioning called function names, either; instead say what the code
-    was trying to do:
-<programlisting>
-BAD:    open() failed: %m
-BETTER: could not open file %s: %m
-</programlisting>
-    If it really seems necessary, mention the system call in the detail
-    message.  (In some cases, providing the actual values passed to the
-    system call might be appropriate information for the detail message.)
-   </para>
-
-   <para>
-    Rationale: Users don't know what all those functions do.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Tricky Words to Avoid</title>
-
-  <formalpara>
-    <title>Unable</title>
-   <para>
-    <quote>Unable</quote> is nearly the passive voice.  Better use
-    <quote>cannot</quote> or <quote>could not</quote>, as appropriate.
-   </para>
-  </formalpara>
-
-  <formalpara>
-    <title>Bad</title>
-   <para>
-    Error messages like <quote>bad result</quote> are really hard to interpret
-    intelligently.  It's better to write why the result is <quote>bad</quote>,
-    e.g., <quote>invalid format</quote>.
-   </para>
-  </formalpara>
-
-  <formalpara>
-    <title>Illegal</title>
-   <para>
-    <quote>Illegal</quote> stands for a violation of the law, the rest is
-    <quote>invalid</quote>. Better yet, say why it's invalid.
-   </para>
-  </formalpara>
-
-  <formalpara>
-    <title>Unknown</title>
-   <para>
-    Try to avoid <quote>unknown</quote>.  Consider <quote>error: unknown
-    response</quote>.  If you don't know what the response is, how do you know
-    it's erroneous? <quote>Unrecognized</quote> is often a better choice.
-    Also, be sure to include the value being complained of.
-<programlisting>
-BAD:    unknown node type
-BETTER: unrecognized node type: 42
-</programlisting>
-   </para>
-  </formalpara>
-
-  <formalpara>
-    <title>Find vs. Exists</title>
-   <para>
-    If the program uses a nontrivial algorithm to locate a resource (e.g., a
-    path search) and that algorithm fails, it is fair to say that the program
-    couldn't <quote>find</quote> the resource.  If, on the other hand, the
-    expected location of the resource is known but the program cannot access
-    it there then say that the resource doesn't <quote>exist</quote>.  Using
-    <quote>find</quote> in this case sounds weak and confuses the issue.
-   </para>
-  </formalpara>
-
-  <formalpara>
-    <title>May vs. Can vs. Might</title>
-   <para>
-    <quote>May</quote> suggests permission (e.g., "You may borrow my rake."),
-    and has little use in documentation or error messages.
-    <quote>Can</quote> suggests ability (e.g., "I can lift that log."),
-    and <quote>might</quote> suggests possibility (e.g., "It might rain
-    today.").  Using the proper word clarifies meaning and assists
-    translation.
-   </para>
-  </formalpara>
-
-  <formalpara>
-    <title>Contractions</title>
-   <para>
-    Avoid contractions, like <quote>can't</quote>;  use
-    <quote>cannot</quote> instead.
-   </para>
-  </formalpara>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Proper Spelling</title>
-
-   <para>
-    Spell out words in full.  For instance, avoid:
-  <itemizedlist>
-   <listitem>
-    <para>
-     spec
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     stats
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     parens
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     auth
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     xact
-    </para>
-   </listitem>
-  </itemizedlist>
-   </para>
-
-   <para>
-    Rationale: This will improve consistency.
-   </para>
-
-  </simplesect>
-
-  <simplesect>
-   <title>Localization</title>
-
-   <para>
-    Keep in mind that error message texts need to be translated into other
-    languages.  Follow the guidelines in <xref linkend="nls-guidelines">
-    to avoid making life difficult for translators.
-   </para>
-  </simplesect>
-
-  </sect1>
-
- </chapter>
diff --git a/doc-xc/src/sgml/spi.sgmlin b/doc-xc/src/sgml/spi.sgmlin
deleted file mode 100644
index 97fc78e0fc..0000000000
--- a/doc-xc/src/sgml/spi.sgmlin
+++ /dev/null
@@ -1,4107 +0,0 @@
-<!-- doc/src/sgml/spi.sgml -->
-
-<chapter id="spi">
- <title>Server Programming Interface</title>
-
- <indexterm zone="spi">
-  <primary>SPI</primary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  The <firstterm>Server Programming Interface</firstterm>
-  (<acronym>SPI</acronym>) gives writers of user-defined
-  <acronym>C</acronym> functions the ability to run
-  <acronym>SQL</acronym> commands inside their functions.
-  <acronym>SPI</acronym> is a set of
-  interface functions to simplify access to the parser, planner,
-  and executor. <acronym>SPI</acronym> also does some
-  memory management.
- </para>
-
- <note>
-  <para>
-   The available procedural languages provide various means to
-   execute SQL commands from procedures.  Most of these facilities are
-   based on SPI, so this documentation might be of use for users
-   of those languages as well.
-  </para>
- </note>
-
- <para>
-  To avoid misunderstanding we'll use the term <quote>function</quote>
-  when we speak of <acronym>SPI</acronym> interface functions and
-  <quote>procedure</quote> for a user-defined C-function that is
-  using <acronym>SPI</acronym>.
- </para>
-
- <para>
-  Note that if a command invoked via SPI fails, then control will not be
-  returned to your procedure.  Rather, the
-  transaction or subtransaction in which your procedure executes will be
-  rolled back.  (This might seem surprising given that the SPI functions mostly
-  have documented error-return conventions.  Those conventions only apply
-  for errors detected within the SPI functions themselves, however.)
-  It is possible to recover control after an error by establishing your own
-  subtransaction surrounding SPI calls that might fail.  This is not currently
-  documented because the mechanisms required are still in flux.
- </para>
-
- <para>
-  <acronym>SPI</acronym> functions return a nonnegative result on
-  success (either via a returned integer value or in the global
-  variable <varname>SPI_result</varname>, as described below).  On
-  error, a negative result or <symbol>NULL</symbol> will be returned.
- </para>
-
- <para>
-  Source code files that use SPI must include the header file
-  <filename>executor/spi.h</filename>.
- </para>
-
-
-<sect1 id="spi-interface">
- <title>Interface Functions</title>
-
- <refentry id="spi-spi-connect">
-  <refmeta>
-   <refentrytitle>SPI_connect</refentrytitle>
-   <manvolnum>3</manvolnum>
-  </refmeta>
-
-  <refnamediv>
-   <refname>SPI_connect</refname>
-   <refpurpose>connect a procedure to the SPI manager</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_connect</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_connect(void)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-&pgnotice;
-  <para>
-   <function>SPI_connect</function> opens a connection from a
-   procedure invocation to the SPI manager.  You must call this
-   function if you want to execute commands through SPI.  Some utility
-   SPI functions can be called from unconnected procedures.
-  </para>
-
-  <para>
-   If your procedure is already connected,
-   <function>SPI_connect</function> will return the error code
-   <returnvalue>SPI_ERROR_CONNECT</returnvalue>.  This could happen if
-   a procedure that has called <function>SPI_connect</function>
-   directly calls another procedure that calls
-   <function>SPI_connect</function>.  While recursive calls to the
-   <acronym>SPI</acronym> manager are permitted when an SQL command
-   called through SPI invokes another function that uses
-   <acronym>SPI</acronym>, directly nested calls to
-   <function>SPI_connect</function> and
-   <function>SPI_finish</function> are forbidden.
-   (But see <function>SPI_push</function> and <function>SPI_pop</function>.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><symbol>SPI_OK_CONNECT</symbol></term>
-    <listitem>
-     <para>
-      on success
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><symbol>SPI_ERROR_CONNECT</symbol></term>
-    <listitem>
-     <para>
-      on error
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-finish">
- <refmeta>
-  <refentrytitle>SPI_finish</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_finish</refname>
-  <refpurpose>disconnect a procedure from the SPI manager</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_finish</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_finish(void)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_finish</function> closes an existing connection to
-   the SPI manager.  You must call this function after completing the
-   SPI operations needed during your procedure's current invocation.
-   You do not need to worry about making this happen, however, if you
-   abort the transaction via <literal>elog(ERROR)</literal>.  In that
-   case SPI will clean itself up automatically.
-  </para>
-
-  <para>
-   If <function>SPI_finish</function> is called without having a valid
-   connection, it will return <symbol>SPI_ERROR_UNCONNECTED</symbol>.
-   There is no fundamental problem with this; it means that the SPI
-   manager has nothing to do.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><symbol>SPI_OK_FINISH</symbol></term>
-    <listitem>
-     <para>
-      if properly disconnected
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><symbol>SPI_ERROR_UNCONNECTED</symbol></term>
-    <listitem>
-     <para>
-      if called from an unconnected procedure
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-push">
- <refmeta>
-  <refentrytitle>SPI_push</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_push</refname>
-  <refpurpose>push SPI stack to allow recursive SPI usage</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_push</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void SPI_push(void)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_push</function> should be called before executing another
-   procedure that might itself wish to use SPI.
-   After <function>SPI_push</function>, SPI is no longer in a
-   <quote>connected</> state, and SPI function calls will be rejected unless
-   a fresh <function>SPI_connect</function> is done.  This ensures a clean
-   separation between your procedure's SPI state and that of another procedure
-   you call.  After the other procedure returns, call
-   <function>SPI_pop</function> to restore access to your own SPI state.
-  </para>
-
-  <para>
-   Note that <function>SPI_execute</function> and related functions
-   automatically do the equivalent of <function>SPI_push</function> before
-   passing control back to the SQL execution engine, so it is not necessary
-   for you to worry about this when using those functions.
-   Only when you are directly calling arbitrary code that might contain
-   <function>SPI_connect</function> calls do you need to issue
-   <function>SPI_push</function> and <function>SPI_pop</function>.
-  </para>
- </refsect1>
-
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-pop">
- <refmeta>
-  <refentrytitle>SPI_pop</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_pop</refname>
-  <refpurpose>pop SPI stack to return from recursive SPI usage</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_pop</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void SPI_pop(void)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_pop</function> pops the previous environment from the
-   SPI call stack.  See <function>SPI_push</function>.
-  </para>
- </refsect1>
-
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-execute">
- <refmeta>
-  <refentrytitle>SPI_execute</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_execute</refname>
-  <refpurpose>execute a command</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_execute</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_execute(const char * <parameter>command</parameter>, bool <parameter>read_only</parameter>, long <parameter>count</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_execute</function> executes the specified SQL command
-   for <parameter>count</parameter> rows.  If <parameter>read_only</parameter>
-   is <literal>true</>, the command must be read-only, and execution overhead
-   is somewhat reduced.
-  </para>
-
-  <para>
-   This function can only be called from a connected procedure.
-  </para>
-
-  <para>
-   If <parameter>count</parameter> is zero then the command is executed
-   for all rows that it applies to.  If <parameter>count</parameter>
-   is greater than 0, then the number of rows for which the command
-   will be executed is restricted (much like a
-   <literal>LIMIT</literal> clause). For example:
-<programlisting>
-SPI_execute("INSERT INTO foo SELECT * FROM bar", false, 5);
-</programlisting>
-   will allow at most 5 rows to be inserted into the table.
-  </para>
-
-  <para>
-   You can pass multiple commands in one string, but later commands cannot
-   depend on the creation of objects earlier in the string, because the
-   whole string will be parsed and planned before execution begins.
-   <function>SPI_execute</function> returns the
-   result for the command executed last.  The <parameter>count</parameter>
-   limit applies to each command separately, but it is not applied to
-   hidden commands generated by rules.
-  </para>
-
-  <para>
-   When <parameter>read_only</parameter> is <literal>false</>,
-   <function>SPI_execute</function> increments the command
-   counter and computes a new <firstterm>snapshot</> before executing each
-   command in the string.  The snapshot does not actually change if the
-   current transaction isolation level is <literal>SERIALIZABLE</> or <literal>REPEATABLE READ</>, but in
-   <literal>READ COMMITTED</> mode the snapshot update allows each command to
-   see the results of newly committed transactions from other sessions.
-   This is essential for consistent behavior when the commands are modifying
-   the database.
-  </para>
-
-  <para>
-   When <parameter>read_only</parameter> is <literal>true</>,
-   <function>SPI_execute</function> does not update either the snapshot
-   or the command counter, and it allows only plain <command>SELECT</>
-   commands to appear in the command string.  The commands are executed
-   using the snapshot previously established for the surrounding query.
-   This execution mode is somewhat faster than the read/write mode due
-   to eliminating per-command overhead.  It also allows genuinely
-   <firstterm>stable</> functions to be built: since successive executions
-   will all use the same snapshot, there will be no change in the results.
-  </para>
-
-  <para>
-   It is generally unwise to mix read-only and read-write commands within
-   a single function using SPI; that could result in very confusing behavior,
-   since the read-only queries would not see the results of any database
-   updates done by the read-write queries.
-  </para>
-
-  <para>
-   The actual number of rows for which the (last) command was executed
-   is returned in the global variable <varname>SPI_processed</varname>.
-   If the return value of the function is <symbol>SPI_OK_SELECT</symbol>,
-   <symbol>SPI_OK_INSERT_RETURNING</symbol>,
-   <symbol>SPI_OK_DELETE_RETURNING</symbol>, or
-   <symbol>SPI_OK_UPDATE_RETURNING</symbol>,
-   then you can use the
-   global pointer <literal>SPITupleTable *SPI_tuptable</literal> to
-   access the result rows.  Some utility commands (such as
-   <command>EXPLAIN</>) also return row sets, and <literal>SPI_tuptable</>
-   will contain the result in these cases too.
-  </para>
-
-  <para>
-   The structure <structname>SPITupleTable</structname> is defined
-   thus:
-<programlisting>
-typedef struct
-{
-    MemoryContext tuptabcxt;    /* memory context of result table */
-    uint32      alloced;        /* number of alloced vals */
-    uint32      free;           /* number of free vals */
-    TupleDesc   tupdesc;        /* row descriptor */
-    HeapTuple  *vals;           /* rows */
-} SPITupleTable;
-</programlisting>
-   <structfield>vals</> is an array of pointers to rows.  (The number
-   of valid entries is given by <varname>SPI_processed</varname>.)
-   <structfield>tupdesc</> is a row descriptor which you can pass to
-   SPI functions dealing with rows.  <structfield>tuptabcxt</>,
-   <structfield>alloced</>, and <structfield>free</> are internal
-   fields not intended for use by SPI callers.
-  </para>
-
-  <para>
-   <function>SPI_finish</function> frees all
-   <structname>SPITupleTable</>s allocated during the current
-   procedure.  You can free a particular result table earlier, if you
-   are done with it, by calling <function>SPI_freetuptable</function>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>const char * <parameter>command</parameter></literal></term>
-    <listitem>
-     <para>
-      string containing command to execute
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>bool <parameter>read_only</parameter></literal></term>
-    <listitem>
-     <para>
-      <literal>true</> for read-only execution
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>long <parameter>count</parameter></literal></term>
-    <listitem>
-     <para>
-      maximum number of rows to process or return
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   If the execution of the command was successful then one of the
-   following (nonnegative) values will be returned:
-
-   <variablelist>
-    <varlistentry>
-     <term><symbol>SPI_OK_SELECT</symbol></term>
-     <listitem>
-      <para>
-       if a <command>SELECT</command> (but not <command>SELECT
-       INTO</>) was executed
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_OK_SELINTO</symbol></term>
-     <listitem>
-      <para>
-       if a <command>SELECT INTO</command> was executed
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_OK_INSERT</symbol></term>
-     <listitem>
-      <para>
-       if an <command>INSERT</command> was executed
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_OK_DELETE</symbol></term>
-     <listitem>
-      <para>
-       if a <command>DELETE</command> was executed
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_OK_UPDATE</symbol></term>
-     <listitem>
-      <para>
-       if an <command>UPDATE</command> was executed
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_OK_INSERT_RETURNING</symbol></term>
-     <listitem>
-      <para>
-       if an <command>INSERT RETURNING</command> was executed
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_OK_DELETE_RETURNING</symbol></term>
-     <listitem>
-      <para>
-       if a <command>DELETE RETURNING</command> was executed
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_OK_UPDATE_RETURNING</symbol></term>
-     <listitem>
-      <para>
-       if an <command>UPDATE RETURNING</command> was executed
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_OK_UTILITY</symbol></term>
-     <listitem>
-      <para>
-       if a utility command (e.g., <command>CREATE TABLE</command>)
-       was executed
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_OK_REWRITTEN</symbol></term>
-     <listitem>
-      <para>
-       if the command was rewritten into another kind of command (e.g.,
-       <command>UPDATE</command> became an <command>INSERT</command>) by a <link linkend="rules">rule</link>.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   On error, one of the following negative values is returned:
-
-   <variablelist>
-    <varlistentry>
-     <term><symbol>SPI_ERROR_ARGUMENT</symbol></term>
-     <listitem>
-      <para>
-       if <parameter>command</parameter> is <symbol>NULL</symbol> or
-       <parameter>count</parameter> is less than 0
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_ERROR_COPY</symbol></term>
-     <listitem>
-      <para>
-       if <command>COPY TO stdout</> or <command>COPY FROM stdin</>
-       was attempted
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_ERROR_TRANSACTION</symbol></term>
-     <listitem>
-      <para>
-       if a transaction manipulation command was attempted
-       (<command>BEGIN</>,
-       <command>COMMIT</>,
-       <command>ROLLBACK</>,
-       <command>SAVEPOINT</>,
-       <command>PREPARE TRANSACTION</>,
-       <command>COMMIT PREPARED</>,
-       <command>ROLLBACK PREPARED</>,
-       or any variant thereof)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_ERROR_OPUNKNOWN</symbol></term>
-     <listitem>
-      <para>
-       if the command type is unknown (shouldn't happen)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_ERROR_UNCONNECTED</symbol></term>
-     <listitem>
-      <para>
-       if called from an unconnected procedure
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   The functions <function>SPI_execute</function>,
-   <function>SPI_exec</function>,
-   <function>SPI_execute_plan</function>, and
-   <function>SPI_execp</function> change both
-   <varname>SPI_processed</varname> and
-   <varname>SPI_tuptable</varname> (just the pointer, not the contents
-   of the structure).  Save these two global variables into local
-   procedure variables if you need to access the result table of
-   <function>SPI_execute</function> or a related function
-   across later calls.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-exec">
- <refmeta>
-  <refentrytitle>SPI_exec</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_exec</refname>
-  <refpurpose>execute a read/write command</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_exec</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_exec(const char * <parameter>command</parameter>, long <parameter>count</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_exec</function> is the same as
-   <function>SPI_execute</function>, with the latter's
-   <parameter>read_only</parameter> parameter always taken as
-   <literal>false</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>const char * <parameter>command</parameter></literal></term>
-    <listitem>
-     <para>
-      string containing command to execute
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>long <parameter>count</parameter></literal></term>
-    <listitem>
-     <para>
-      maximum number of rows to process or return
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   See <function>SPI_execute</function>.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-execute-with-args">
- <refmeta>
-  <refentrytitle>SPI_execute_with_args</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_execute_with_args</refname>
-  <refpurpose>execute a command with out-of-line parameters</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_execute_with_args</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_execute_with_args(const char *<parameter>command</parameter>,
-                          int <parameter>nargs</parameter>, Oid *<parameter>argtypes</parameter>,
-                          Datum *<parameter>values</parameter>, const char *<parameter>nulls</parameter>,
-                          bool <parameter>read_only</parameter>, long <parameter>count</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_execute_with_args</function> executes a command that might
-   include references to externally supplied parameters.  The command text
-   refers to a parameter as <literal>$<replaceable>n</></literal>, and
-   the call specifies data types and values for each such symbol.
-   <parameter>read_only</parameter> and <parameter>count</parameter> have
-   the same interpretation as in <function>SPI_execute</function>.
-  </para>
-
-  <para>
-   The main advantage of this routine compared to
-   <function>SPI_execute</function> is that data values can be inserted
-   into the command without tedious quoting/escaping, and thus with much
-   less risk of SQL-injection attacks.
-  </para>
-
-  <para>
-   Similar results can be achieved with <function>SPI_prepare</> followed by
-   <function>SPI_execute_plan</function>; however, when using this function
-   the query plan is customized to the specific parameter values provided.
-   For one-time query execution, this function should be preferred.
-   If the same command is to be executed with many different parameters,
-   either method might be faster, depending on the cost of re-planning
-   versus the benefit of custom plans.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>const char * <parameter>command</parameter></literal></term>
-    <listitem>
-     <para>
-      command string
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>nargs</parameter></literal></term>
-    <listitem>
-     <para>
-      number of input parameters (<literal>$1</>, <literal>$2</>, etc.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Oid * <parameter>argtypes</parameter></literal></term>
-    <listitem>
-     <para>
-      an array containing the <acronym>OID</acronym>s of
-      the data types of the parameters
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Datum * <parameter>values</parameter></literal></term>
-    <listitem>
-     <para>
-      an array of actual parameter values
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>const char * <parameter>nulls</parameter></literal></term>
-    <listitem>
-     <para>
-      an array describing which parameters are null
-     </para>
-
-     <para>
-      If <parameter>nulls</parameter> is <symbol>NULL</symbol> then
-      <function>SPI_execute_with_args</function> assumes that no parameters are
-      null.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>bool <parameter>read_only</parameter></literal></term>
-    <listitem>
-     <para>
-      <literal>true</> for read-only execution
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>long <parameter>count</parameter></literal></term>
-    <listitem>
-     <para>
-      maximum number of rows to process or return
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   The return value is the same as for <function>SPI_execute</function>.
-  </para>
-
-  <para>
-   <varname>SPI_processed</varname> and
-   <varname>SPI_tuptable</varname> are set as in
-   <function>SPI_execute</function> if successful.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-prepare">
- <refmeta>
-  <refentrytitle>SPI_prepare</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_prepare</refname>
-  <refpurpose>prepare a plan for a command, without executing it yet</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_prepare</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SPIPlanPtr SPI_prepare(const char * <parameter>command</parameter>, int <parameter>nargs</parameter>, Oid * <parameter>argtypes</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_prepare</function> creates and returns an execution
-   plan for the specified command, but doesn't execute the command.
-   This function should only be called from a connected procedure.
-  </para>
-
-  <para>
-   When the same or a similar command is to be executed repeatedly, it
-   might be advantageous to perform the planning only once.
-   <function>SPI_prepare</function> converts a command string into an
-   execution plan that can be executed repeatedly using
-   <function>SPI_execute_plan</function>.
-  </para>
-
-  <para>
-   A prepared command can be generalized by writing parameters
-   (<literal>$1</>, <literal>$2</>, etc.) in place of what would be
-   constants in a normal command.  The actual values of the parameters
-   are then specified when <function>SPI_execute_plan</function> is called.
-   This allows the prepared command to be used over a wider range of
-   situations than would be possible without parameters.
-  </para>
-
-  <para>
-   The plan returned by <function>SPI_prepare</function> can be used
-   only in the current invocation of the procedure, since
-   <function>SPI_finish</function> frees memory allocated for a plan.
-   But a plan can be saved for longer using the function
-   <function>SPI_saveplan</function>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>const char * <parameter>command</parameter></literal></term>
-    <listitem>
-     <para>
-      command string
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>nargs</parameter></literal></term>
-    <listitem>
-     <para>
-      number of input parameters (<literal>$1</>, <literal>$2</>, etc.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Oid * <parameter>argtypes</parameter></literal></term>
-    <listitem>
-     <para>
-      pointer to an array containing the <acronym>OID</acronym>s of
-      the data types of the parameters
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   <function>SPI_prepare</function> returns a non-null pointer to an
-   execution plan.  On error, <symbol>NULL</symbol> will be returned,
-   and <varname>SPI_result</varname> will be set to one of the same
-   error codes used by <function>SPI_execute</function>, except that
-   it is set to <symbol>SPI_ERROR_ARGUMENT</symbol> if
-   <parameter>command</parameter> is <symbol>NULL</symbol>, or if
-   <parameter>nargs</> is less than 0, or if <parameter>nargs</> is
-   greater than 0 and <parameter>argtypes</> is <symbol>NULL</symbol>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <type>SPIPlanPtr</> is declared as a pointer to an opaque struct type in
-   <filename>spi.h</>.  It is unwise to try to access its contents
-   directly, as that makes your code much more likely to break in
-   future revisions of <productname>PostgreSQL</productname>.
-  </para>
-
-  <para>
-   There is a disadvantage to using parameters: since the planner does
-   not know the values that will be supplied for the parameters, it
-   might make worse planning choices than it would make for a normal
-   command with all constants visible.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-prepare-cursor">
- <refmeta>
-  <refentrytitle>SPI_prepare_cursor</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_prepare_cursor</refname>
-  <refpurpose>prepare a plan for a command, without executing it yet</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_prepare_cursor</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SPIPlanPtr SPI_prepare_cursor(const char * <parameter>command</parameter>, int <parameter>nargs</parameter>,
-                              Oid * <parameter>argtypes</parameter>, int <parameter>cursorOptions</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_prepare_cursor</function> is identical to
-   <function>SPI_prepare</function>, except that it also allows specification
-   of the planner's <quote>cursor options</> parameter.  This is a bit mask
-   having the values shown in <filename>nodes/parsenodes.h</filename>
-   for the <structfield>options</> field of <structname>DeclareCursorStmt</>.
-   <function>SPI_prepare</function> always takes the cursor options as zero.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>const char * <parameter>command</parameter></literal></term>
-    <listitem>
-     <para>
-      command string
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>nargs</parameter></literal></term>
-    <listitem>
-     <para>
-      number of input parameters (<literal>$1</>, <literal>$2</>, etc.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Oid * <parameter>argtypes</parameter></literal></term>
-    <listitem>
-     <para>
-      pointer to an array containing the <acronym>OID</acronym>s of
-      the data types of the parameters
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>cursorOptions</parameter></literal></term>
-    <listitem>
-     <para>
-      integer bit mask of cursor options; zero produces default behavior
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   <function>SPI_prepare_cursor</function> has the same return conventions as
-   <function>SPI_prepare</function>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Useful bits to set in <parameter>cursorOptions</> include
-   <symbol>CURSOR_OPT_SCROLL</symbol>,
-   <symbol>CURSOR_OPT_NO_SCROLL</symbol>, and
-   <symbol>CURSOR_OPT_FAST_PLAN</symbol>.  Note in particular that
-   <symbol>CURSOR_OPT_HOLD</symbol> is ignored.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-prepare-params">
- <refmeta>
-  <refentrytitle>SPI_prepare_params</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_prepare_params</refname>
-  <refpurpose>prepare a plan for a command, without executing it yet</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_prepare_params</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SPIPlanPtr SPI_prepare_params(const char * <parameter>command</parameter>,
-                              ParserSetupHook <parameter>parserSetup</parameter>,
-                              void * <parameter>parserSetupArg</parameter>,
-                              int <parameter>cursorOptions</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_prepare_params</function> creates and returns an execution
-   plan for the specified command, but doesn't execute the command.
-   This function is equivalent to <function>SPI_prepare_cursor</function>,
-   with the addition that the caller can specify parser hook functions
-   to control the parsing of external parameter references.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>const char * <parameter>command</parameter></literal></term>
-    <listitem>
-     <para>
-      command string
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ParserSetupHook <parameter>parserSetup</parameter></literal></term>
-    <listitem>
-     <para>
-      Parser hook setup function
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>void * <parameter>parserSetupArg</parameter></literal></term>
-    <listitem>
-     <para>
-      passthrough argument for <parameter>parserSetup</parameter>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>cursorOptions</parameter></literal></term>
-    <listitem>
-     <para>
-      integer bit mask of cursor options; zero produces default behavior
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   <function>SPI_prepare_params</function> has the same return conventions as
-   <function>SPI_prepare</function>.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-getargcount">
- <refmeta>
-  <refentrytitle>SPI_getargcount</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_getargcount</refname>
-  <refpurpose>return the number of arguments needed by a plan
-  prepared by <function>SPI_prepare</function></refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_getargcount</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_getargcount(SPIPlanPtr <parameter>plan</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_getargcount</function> returns the number of arguments needed
-   to execute a plan prepared by <function>SPI_prepare</function>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>SPIPlanPtr <parameter>plan</parameter></literal></term>
-    <listitem>
-     <para>
-      execution plan (returned by <function>SPI_prepare</function>)
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-  <para>
-    The count of expected arguments for the <parameter>plan</parameter>.
-    If the <parameter>plan</parameter> is <symbol>NULL</symbol> or invalid,
-    <varname>SPI_result</varname> is set to <symbol>SPI_ERROR_ARGUMENT</symbol>
-    and -1 is returned.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-getargtypeid">
- <refmeta>
-  <refentrytitle>SPI_getargtypeid</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_getargtypeid</refname>
-  <refpurpose>return the data type OID for an argument of
-  a plan prepared by <function>SPI_prepare</function></refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_getargtypeid</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-Oid SPI_getargtypeid(SPIPlanPtr <parameter>plan</parameter>, int <parameter>argIndex</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_getargtypeid</function> returns the OID representing the type
-   id for the <parameter>argIndex</parameter>'th argument of a plan prepared by
-   <function>SPI_prepare</function>. First argument is at index zero.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>SPIPlanPtr <parameter>plan</parameter></literal></term>
-    <listitem>
-     <para>
-      execution plan (returned by <function>SPI_prepare</function>)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>argIndex</parameter></literal></term>
-    <listitem>
-     <para>
-      zero based index of the argument
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-  <para>
-    The type id of the argument at the given index.
-    If the <parameter>plan</parameter> is <symbol>NULL</symbol> or invalid,
-    or <parameter>argIndex</parameter> is less than 0 or
-    not less than the number of arguments declared for the
-    <parameter>plan</parameter>,
-    <varname>SPI_result</varname> is set to <symbol>SPI_ERROR_ARGUMENT</symbol>
-    and <symbol>InvalidOid</symbol> is returned.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-is-cursor-plan">
- <refmeta>
-  <refentrytitle>SPI_is_cursor_plan</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_is_cursor_plan</refname>
-  <refpurpose>return <symbol>true</symbol> if a plan
-  prepared by <function>SPI_prepare</function> can be used with
-  <function>SPI_cursor_open</function></refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_is_cursor_plan</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-bool SPI_is_cursor_plan(SPIPlanPtr <parameter>plan</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_is_cursor_plan</function> returns <symbol>true</symbol>
-   if a plan prepared by <function>SPI_prepare</function> can be passed
-   as an argument to <function>SPI_cursor_open</function>, or
-   <symbol>false</symbol> if that is not the case. The criteria are that the
-   <parameter>plan</parameter> represents one single command and that this
-   command returns tuples to the caller; for example, <command>SELECT</>
-   is allowed unless it contains an <literal>INTO</> clause, and
-   <command>UPDATE</> is allowed only if it contains a <literal>RETURNING</>
-   clause.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>SPIPlanPtr <parameter>plan</parameter></literal></term>
-    <listitem>
-     <para>
-      execution plan (returned by <function>SPI_prepare</function>)
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-  <para>
-    <symbol>true</symbol> or <symbol>false</symbol> to indicate if the
-    <parameter>plan</parameter> can produce a cursor or not, with
-    <varname>SPI_result</varname> set to zero.
-    If it is not possible to determine the answer (for example,
-    if the <parameter>plan</parameter> is <symbol>NULL</symbol> or invalid,
-    or if called when not connected to SPI), then
-    <varname>SPI_result</varname> is set to a suitable error code
-    and <symbol>false</symbol> is returned.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-execute-plan">
- <refmeta>
-  <refentrytitle>SPI_execute_plan</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_execute_plan</refname>
-  <refpurpose>execute a plan prepared by <function>SPI_prepare</function></refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_execute_plan</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_execute_plan(SPIPlanPtr <parameter>plan</parameter>, Datum * <parameter>values</parameter>, const char * <parameter>nulls</parameter>,
-                     bool <parameter>read_only</parameter>, long <parameter>count</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_execute_plan</function> executes a plan prepared by
-   <function>SPI_prepare</function>.  <parameter>read_only</parameter> and
-   <parameter>count</parameter> have the same interpretation as in
-   <function>SPI_execute</function>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>SPIPlanPtr <parameter>plan</parameter></literal></term>
-    <listitem>
-     <para>
-      execution plan (returned by <function>SPI_prepare</function>)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Datum * <parameter>values</parameter></literal></term>
-    <listitem>
-     <para>
-      An array of actual parameter values.  Must have same length as the
-      plan's number of arguments.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>const char * <parameter>nulls</parameter></literal></term>
-    <listitem>
-     <para>
-      An array describing which parameters are null.  Must have same length as
-      the plan's number of arguments.
-      <literal>n</literal> indicates a null value (entry in
-      <parameter>values</> will be ignored); a space indicates a
-      nonnull value (entry in <parameter>values</> is valid).
-     </para>
-
-     <para>
-      If <parameter>nulls</parameter> is <symbol>NULL</symbol> then
-      <function>SPI_execute_plan</function> assumes that no parameters are
-      null.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>bool <parameter>read_only</parameter></literal></term>
-    <listitem>
-     <para>
-      <literal>true</> for read-only execution
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>long <parameter>count</parameter></literal></term>
-    <listitem>
-     <para>
-      maximum number of rows to process or return
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   The return value is the same as for <function>SPI_execute</function>,
-   with the following additional possible error (negative) results:
-
-   <variablelist>
-    <varlistentry>
-     <term><symbol>SPI_ERROR_ARGUMENT</symbol></term>
-     <listitem>
-      <para>
-       if <parameter>plan</parameter> is <symbol>NULL</symbol> or invalid,
-       or <parameter>count</parameter> is less than 0
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_ERROR_PARAM</symbol></term>
-     <listitem>
-      <para>
-       if <parameter>values</parameter> is <symbol>NULL</symbol> and
-       <parameter>plan</parameter> was prepared with some parameters
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   <varname>SPI_processed</varname> and
-   <varname>SPI_tuptable</varname> are set as in
-   <function>SPI_execute</function> if successful.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-execute-plan-with-paramlist">
- <refmeta>
-  <refentrytitle>SPI_execute_plan_with_paramlist</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_execute_plan_with_paramlist</refname>
-  <refpurpose>execute a plan prepared by <function>SPI_prepare</function></refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_execute_plan_with_paramlist</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_execute_plan_with_paramlist(SPIPlanPtr <parameter>plan</parameter>,
-                                    ParamListInfo <parameter>params</parameter>,
-                                    bool <parameter>read_only</parameter>,
-                                    long <parameter>count</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_execute_plan_with_paramlist</function> executes a plan
-   prepared by <function>SPI_prepare</function>.
-   This function is equivalent to <function>SPI_execute_plan</function>
-   except that information about the parameter values to be passed to the
-   query is presented differently.  The <literal>ParamListInfo</>
-   representation can be convenient for passing down values that are
-   already available in that format.  It also supports use of dynamic
-   parameter sets via hook functions specified in <literal>ParamListInfo</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>SPIPlanPtr <parameter>plan</parameter></literal></term>
-    <listitem>
-     <para>
-      execution plan (returned by <function>SPI_prepare</function>)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ParamListInfo <parameter>params</parameter></literal></term>
-    <listitem>
-     <para>
-      data structure containing parameter types and values; NULL if none
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>bool <parameter>read_only</parameter></literal></term>
-    <listitem>
-     <para>
-      <literal>true</> for read-only execution
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>long <parameter>count</parameter></literal></term>
-    <listitem>
-     <para>
-      maximum number of rows to process or return
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   The return value is the same as for <function>SPI_execute_plan</function>.
-  </para>
-
-  <para>
-   <varname>SPI_processed</varname> and
-   <varname>SPI_tuptable</varname> are set as in
-   <function>SPI_execute_plan</function> if successful.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-execp">
- <refmeta>
-  <refentrytitle>SPI_execp</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_execp</refname>
-  <refpurpose>execute a plan in read/write mode</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_execp</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_execp(SPIPlanPtr <parameter>plan</parameter>, Datum * <parameter>values</parameter>, const char * <parameter>nulls</parameter>, long <parameter>count</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_execp</function> is the same as
-   <function>SPI_execute_plan</function>, with the latter's
-   <parameter>read_only</parameter> parameter always taken as
-   <literal>false</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>SPIPlanPtr <parameter>plan</parameter></literal></term>
-    <listitem>
-     <para>
-      execution plan (returned by <function>SPI_prepare</function>)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Datum * <parameter>values</parameter></literal></term>
-    <listitem>
-     <para>
-      An array of actual parameter values.  Must have same length as the
-      plan's number of arguments.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>const char * <parameter>nulls</parameter></literal></term>
-    <listitem>
-     <para>
-      An array describing which parameters are null.  Must have same length as
-      the plan's number of arguments.
-      <literal>n</literal> indicates a null value (entry in
-      <parameter>values</> will be ignored); a space indicates a
-      nonnull value (entry in <parameter>values</> is valid).
-     </para>
-
-     <para>
-      If <parameter>nulls</parameter> is <symbol>NULL</symbol> then
-      <function>SPI_execp</function> assumes that no parameters are
-      null.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>long <parameter>count</parameter></literal></term>
-    <listitem>
-     <para>
-      maximum number of rows to process or return
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   See <function>SPI_execute_plan</function>.
-  </para>
-
-  <para>
-   <varname>SPI_processed</varname> and
-   <varname>SPI_tuptable</varname> are set as in
-   <function>SPI_execute</function> if successful.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-cursor-open">
- <refmeta>
-  <refentrytitle>SPI_cursor_open</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_cursor_open</refname>
-  <refpurpose>set up a cursor using a plan created with <function>SPI_prepare</function></refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_cursor_open</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-Portal SPI_cursor_open(const char * <parameter>name</parameter>, SPIPlanPtr <parameter>plan</parameter>,
-                       Datum * <parameter>values</parameter>, const char * <parameter>nulls</parameter>,
-                       bool <parameter>read_only</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_cursor_open</function> sets up a cursor (internally,
-   a portal) that will execute a plan prepared by
-   <function>SPI_prepare</function>.  The parameters have the same
-   meanings as the corresponding parameters to
-   <function>SPI_execute_plan</function>.
-  </para>
-
-  <para>
-   Using a cursor instead of executing the plan directly has two
-   benefits.  First, the result rows can be retrieved a few at a time,
-   avoiding memory overrun for queries that return many rows.  Second,
-   a portal can outlive the current procedure (it can, in fact, live
-   to the end of the current transaction).  Returning the portal name
-   to the procedure's caller provides a way of returning a row set as
-   result.
-  </para>
-
-  <para>
-   The passed-in parameter data will be copied into the cursor's portal, so it
-   can be freed while the cursor still exists.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>const char * <parameter>name</parameter></literal></term>
-    <listitem>
-     <para>
-      name for portal, or <symbol>NULL</symbol> to let the system
-      select a name
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SPIPlanPtr <parameter>plan</parameter></literal></term>
-    <listitem>
-     <para>
-      execution plan (returned by <function>SPI_prepare</function>)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Datum * <parameter>values</parameter></literal></term>
-    <listitem>
-     <para>
-      An array of actual parameter values.  Must have same length as the
-      plan's number of arguments.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>const char * <parameter>nulls</parameter></literal></term>
-    <listitem>
-     <para>
-      An array describing which parameters are null.  Must have same length as
-      the plan's number of arguments.
-      <literal>n</literal> indicates a null value (entry in
-      <parameter>values</> will be ignored); a space indicates a
-      nonnull value (entry in <parameter>values</> is valid).
-     </para>
-
-     <para>
-      If <parameter>nulls</parameter> is <symbol>NULL</symbol> then
-      <function>SPI_cursor_open</function> assumes that no parameters are
-      null.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>bool <parameter>read_only</parameter></literal></term>
-    <listitem>
-     <para>
-      <literal>true</> for read-only execution
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   Pointer to portal containing the cursor.  Note there is no error
-   return convention; any error will be reported via <function>elog</>.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-cursor-open-with-args">
- <refmeta>
-  <refentrytitle>SPI_cursor_open_with_args</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_cursor_open_with_args</refname>
-  <refpurpose>set up a cursor using a query and parameters</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_cursor_open_with_args</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-Portal SPI_cursor_open_with_args(const char *<parameter>name</parameter>,
-                                 const char *<parameter>command</parameter>,
-                                 int <parameter>nargs</parameter>, Oid *<parameter>argtypes</parameter>,
-                                 Datum *<parameter>values</parameter>, const char *<parameter>nulls</parameter>,
-                                 bool <parameter>read_only</parameter>, int <parameter>cursorOptions</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_cursor_open_with_args</function> sets up a cursor
-   (internally, a portal) that will execute the specified query.
-   Most of the parameters have the same meanings as the corresponding
-   parameters to <function>SPI_prepare_cursor</function>
-   and <function>SPI_cursor_open</function>.
-  </para>
-
-  <para>
-   For one-time query execution, this function should be preferred
-   over <function>SPI_prepare_cursor</function> followed by
-   <function>SPI_cursor_open</function>.
-   If the same command is to be executed with many different parameters,
-   either method might be faster, depending on the cost of re-planning
-   versus the benefit of custom plans.
-  </para>
-
-  <para>
-   The passed-in parameter data will be copied into the cursor's portal, so it
-   can be freed while the cursor still exists.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>const char * <parameter>name</parameter></literal></term>
-    <listitem>
-     <para>
-      name for portal, or <symbol>NULL</symbol> to let the system
-      select a name
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>const char * <parameter>command</parameter></literal></term>
-    <listitem>
-     <para>
-      command string
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>nargs</parameter></literal></term>
-    <listitem>
-     <para>
-      number of input parameters (<literal>$1</>, <literal>$2</>, etc.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Oid * <parameter>argtypes</parameter></literal></term>
-    <listitem>
-     <para>
-      an array containing the <acronym>OID</acronym>s of
-      the data types of the parameters
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Datum * <parameter>values</parameter></literal></term>
-    <listitem>
-     <para>
-      an array of actual parameter values
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>const char * <parameter>nulls</parameter></literal></term>
-    <listitem>
-     <para>
-      an array describing which parameters are null
-     </para>
-
-     <para>
-      If <parameter>nulls</parameter> is <symbol>NULL</symbol> then
-      <function>SPI_cursor_open_with_args</function> assumes that no
-      parameters are null.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>bool <parameter>read_only</parameter></literal></term>
-    <listitem>
-     <para>
-      <literal>true</> for read-only execution
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>cursorOptions</parameter></literal></term>
-    <listitem>
-     <para>
-      integer bit mask of cursor options; zero produces default behavior
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   Pointer to portal containing the cursor.  Note there is no error
-   return convention; any error will be reported via <function>elog</>.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-cursor-open-with-paramlist">
- <refmeta>
-  <refentrytitle>SPI_cursor_open_with_paramlist</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_cursor_open_with_paramlist</refname>
-  <refpurpose>set up a cursor using parameters</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_cursor_open_with_paramlist</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-Portal SPI_cursor_open_with_paramlist(const char *<parameter>name</parameter>,
-                                      SPIPlanPtr <parameter>plan</parameter>,
-                                      ParamListInfo <parameter>params</parameter>,
-                                      bool <parameter>read_only</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_cursor_open_with_paramlist</function> sets up a cursor
-   (internally, a portal) that will execute a plan prepared by
-   <function>SPI_prepare</function>.
-   This function is equivalent to <function>SPI_cursor_open</function>
-   except that information about the parameter values to be passed to the
-   query is presented differently.  The <literal>ParamListInfo</>
-   representation can be convenient for passing down values that are
-   already available in that format.  It also supports use of dynamic
-   parameter sets via hook functions specified in <literal>ParamListInfo</>.
-  </para>
-
-  <para>
-   The passed-in parameter data will be copied into the cursor's portal, so it
-   can be freed while the cursor still exists.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>const char * <parameter>name</parameter></literal></term>
-    <listitem>
-     <para>
-      name for portal, or <symbol>NULL</symbol> to let the system
-      select a name
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>SPIPlanPtr <parameter>plan</parameter></literal></term>
-    <listitem>
-     <para>
-      execution plan (returned by <function>SPI_prepare</function>)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>ParamListInfo <parameter>params</parameter></literal></term>
-    <listitem>
-     <para>
-      data structure containing parameter types and values; NULL if none
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>bool <parameter>read_only</parameter></literal></term>
-    <listitem>
-     <para>
-      <literal>true</> for read-only execution
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   Pointer to portal containing the cursor.  Note there is no error
-   return convention; any error will be reported via <function>elog</>.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-cursor-find">
- <refmeta>
-  <refentrytitle>SPI_cursor_find</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_cursor_find</refname>
-  <refpurpose>find an existing cursor by name</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_cursor_find</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-Portal SPI_cursor_find(const char * <parameter>name</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_cursor_find</function> finds an existing portal by
-   name.  This is primarily useful to resolve a cursor name returned
-   as text by some other function.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>const char * <parameter>name</parameter></literal></term>
-    <listitem>
-     <para>
-      name of the portal
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   pointer to the portal with the specified name, or
-   <symbol>NULL</symbol> if none was found
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-cursor-fetch">
- <refmeta>
-  <refentrytitle>SPI_cursor_fetch</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_cursor_fetch</refname>
-  <refpurpose>fetch some rows from a cursor</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_cursor_fetch</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void SPI_cursor_fetch(Portal <parameter>portal</parameter>, bool <parameter>forward</parameter>, long <parameter>count</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_cursor_fetch</function> fetches some rows from a
-   cursor.  This is equivalent to a subset of the SQL command
-   <command>FETCH</> (see <function>SPI_scroll_cursor_fetch</function>
-   for more functionality).
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>Portal <parameter>portal</parameter></literal></term>
-    <listitem>
-     <para>
-      portal containing the cursor
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>bool <parameter>forward</parameter></literal></term>
-    <listitem>
-     <para>
-      true for fetch forward, false for fetch backward
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>long <parameter>count</parameter></literal></term>
-    <listitem>
-     <para>
-      maximum number of rows to fetch
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   <varname>SPI_processed</varname> and
-   <varname>SPI_tuptable</varname> are set as in
-   <function>SPI_execute</function> if successful.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Fetching backward may fail if the cursor's plan was not created
-   with the <symbol>CURSOR_OPT_SCROLL</symbol> option.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-cursor-move">
- <refmeta>
-  <refentrytitle>SPI_cursor_move</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_cursor_move</refname>
-  <refpurpose>move a cursor</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_cursor_move</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void SPI_cursor_move(Portal <parameter>portal</parameter>, bool <parameter>forward</parameter>, long <parameter>count</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_cursor_move</function> skips over some number of rows
-   in a cursor.  This is equivalent to a subset of the SQL command
-   <command>MOVE</> (see <function>SPI_scroll_cursor_move</function>
-   for more functionality).
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>Portal <parameter>portal</parameter></literal></term>
-    <listitem>
-     <para>
-      portal containing the cursor
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>bool <parameter>forward</parameter></literal></term>
-    <listitem>
-     <para>
-      true for move forward, false for move backward
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>long <parameter>count</parameter></literal></term>
-    <listitem>
-     <para>
-      maximum number of rows to move
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Moving backward may fail if the cursor's plan was not created
-   with the <symbol>CURSOR_OPT_SCROLL</symbol> option.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-scroll-cursor-fetch">
- <refmeta>
-  <refentrytitle>SPI_scroll_cursor_fetch</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_scroll_cursor_fetch</refname>
-  <refpurpose>fetch some rows from a cursor</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_scroll_cursor_fetch</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void SPI_scroll_cursor_fetch(Portal <parameter>portal</parameter>, FetchDirection <parameter>direction</parameter>,
-                             long <parameter>count</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_scroll_cursor_fetch</function> fetches some rows from a
-   cursor.  This is equivalent to the SQL command <command>FETCH</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>Portal <parameter>portal</parameter></literal></term>
-    <listitem>
-     <para>
-      portal containing the cursor
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>FetchDirection <parameter>direction</parameter></literal></term>
-    <listitem>
-     <para>
-      one of <symbol>FETCH_FORWARD</symbol>,
-      <symbol>FETCH_BACKWARD</symbol>,
-      <symbol>FETCH_ABSOLUTE</symbol> or
-      <symbol>FETCH_RELATIVE</symbol>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>long <parameter>count</parameter></literal></term>
-    <listitem>
-     <para>
-      number of rows to fetch for
-      <symbol>FETCH_FORWARD</symbol> or
-      <symbol>FETCH_BACKWARD</symbol>; absolute row number to fetch for
-      <symbol>FETCH_ABSOLUTE</symbol>; or relative row number to fetch for
-      <symbol>FETCH_RELATIVE</symbol>
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   <varname>SPI_processed</varname> and
-   <varname>SPI_tuptable</varname> are set as in
-   <function>SPI_execute</function> if successful.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   See the SQL <xref linkend="sql-fetch"> command
-   for details of the interpretation of the
-   <parameter>direction</parameter> and
-   <parameter>count</parameter> parameters.
-  </para>
-
-  <para>
-   Direction values other than <symbol>FETCH_FORWARD</symbol>
-   may fail if the cursor's plan was not created
-   with the <symbol>CURSOR_OPT_SCROLL</symbol> option.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-scroll-cursor-move">
- <refmeta>
-  <refentrytitle>SPI_scroll_cursor_move</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_scroll_cursor_move</refname>
-  <refpurpose>move a cursor</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_scroll_cursor_move</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void SPI_scroll_cursor_move(Portal <parameter>portal</parameter>, FetchDirection <parameter>direction</parameter>,
-                            long <parameter>count</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_scroll_cursor_move</function> skips over some number of rows
-   in a cursor.  This is equivalent to the SQL command
-   <command>MOVE</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>Portal <parameter>portal</parameter></literal></term>
-    <listitem>
-     <para>
-      portal containing the cursor
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>FetchDirection <parameter>direction</parameter></literal></term>
-    <listitem>
-     <para>
-      one of <symbol>FETCH_FORWARD</symbol>,
-      <symbol>FETCH_BACKWARD</symbol>,
-      <symbol>FETCH_ABSOLUTE</symbol> or
-      <symbol>FETCH_RELATIVE</symbol>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>long <parameter>count</parameter></literal></term>
-    <listitem>
-     <para>
-      number of rows to move for
-      <symbol>FETCH_FORWARD</symbol> or
-      <symbol>FETCH_BACKWARD</symbol>; absolute row number to move to for
-      <symbol>FETCH_ABSOLUTE</symbol>; or relative row number to move to for
-      <symbol>FETCH_RELATIVE</symbol>
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   <varname>SPI_processed</varname> is set as in
-   <function>SPI_execute</function> if successful.
-   <varname>SPI_tuptable</varname> is set to <symbol>NULL</>, since
-   no rows are returned by this function.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   See the SQL <xref linkend="sql-fetch"> command
-   for details of the interpretation of the
-   <parameter>direction</parameter> and
-   <parameter>count</parameter> parameters.
-  </para>
-
-  <para>
-   Direction values other than <symbol>FETCH_FORWARD</symbol>
-   may fail if the cursor's plan was not created
-   with the <symbol>CURSOR_OPT_SCROLL</symbol> option.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-cursor-close">
- <refmeta>
-  <refentrytitle>SPI_cursor_close</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_cursor_close</refname>
-  <refpurpose>close a cursor</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_cursor_close</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void SPI_cursor_close(Portal <parameter>portal</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_cursor_close</function> closes a previously created
-   cursor and releases its portal storage.
-  </para>
-
-  <para>
-   All open cursors are closed automatically at the end of a
-   transaction.  <function>SPI_cursor_close</function> need only be
-   invoked if it is desirable to release resources sooner.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>Portal <parameter>portal</parameter></literal></term>
-    <listitem>
-     <para>
-      portal containing the cursor
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-saveplan">
- <refmeta>
-  <refentrytitle>SPI_saveplan</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_saveplan</refname>
-  <refpurpose>save a plan</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_saveplan</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-SPIPlanPtr SPI_saveplan(SPIPlanPtr <parameter>plan</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_saveplan</function> saves a passed plan (prepared by
-   <function>SPI_prepare</function>) in memory that will not be freed
-   by <function>SPI_finish</function> nor by the transaction manager,
-   and returns a pointer to the saved plan.  This gives you the
-   ability to reuse prepared plans in the subsequent invocations of
-   your procedure in the current session.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>SPIPlanPtr <parameter>plan</parameter></literal></term>
-    <listitem>
-     <para>
-      the plan to be saved
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   Pointer to the saved plan; <symbol>NULL</symbol> if unsuccessful.
-   On error, <varname>SPI_result</varname> is set thus:
-
-   <variablelist>
-    <varlistentry>
-     <term><symbol>SPI_ERROR_ARGUMENT</symbol></term>
-     <listitem>
-      <para>
-       if <parameter>plan</parameter> is <symbol>NULL</symbol> or invalid
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_ERROR_UNCONNECTED</symbol></term>
-     <listitem>
-      <para>
-       if called from an unconnected procedure
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   The passed-in plan is not freed, so you might wish to do
-   <function>SPI_freeplan</function> on it to avoid leaking memory
-   until <function>SPI_finish</>.
-  </para>
-
-  <para>
-   If one of the objects (a table, function, etc.) referenced by the
-   prepared plan is dropped or redefined, then future executions of
-   <function>SPI_execute_plan</function> may fail or return different
-   results than the plan initially indicates.
-  </para>
- </refsect1>
-</refentry>
-
-</sect1>
-
-<sect1 id="spi-interface-support">
- <title>Interface Support Functions</title>
-
-&pgnotice;
- <para>
-  The functions described here provide an interface for extracting
-  information from result sets returned by <function>SPI_execute</> and
-  other SPI functions.
- </para>
-
- <para>
-  All functions described in this section can be used by both
-  connected and unconnected procedures.
- </para>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-fname">
- <refmeta>
-  <refentrytitle>SPI_fname</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_fname</refname>
-  <refpurpose>determine the column name for the specified column number</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_fname</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-char * SPI_fname(TupleDesc <parameter>rowdesc</parameter>, int <parameter>colnumber</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_fname</function> returns a copy of the column name of the
-   specified column.  (You can use <function>pfree</function> to
-   release the copy of the name when you don't need it anymore.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>TupleDesc <parameter>rowdesc</parameter></literal></term>
-    <listitem>
-     <para>
-      input row description
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>colnumber</parameter></literal></term>
-    <listitem>
-     <para>
-      column number (count starts at 1)
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   The column name; <symbol>NULL</symbol> if
-   <parameter>colnumber</parameter> is out of range.
-   <varname>SPI_result</varname> set to
-   <symbol>SPI_ERROR_NOATTRIBUTE</symbol> on error.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-fnumber">
- <refmeta>
-  <refentrytitle>SPI_fnumber</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_fnumber</refname>
-  <refpurpose>determine the column number for the specified column name</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_fnumber</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_fnumber(TupleDesc <parameter>rowdesc</parameter>, const char * <parameter>colname</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_fnumber</function> returns the column number for the
-   column with the specified name.
-  </para>
-
-  <para>
-   If <parameter>colname</parameter> refers to a system column (e.g.,
-   <literal>oid</>) then the appropriate negative column number will
-   be returned.  The caller should be careful to test the return value
-   for exact equality to <symbol>SPI_ERROR_NOATTRIBUTE</symbol> to
-   detect an error; testing the result for less than or equal to 0 is
-   not correct unless system columns should be rejected.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>TupleDesc <parameter>rowdesc</parameter></literal></term>
-    <listitem>
-     <para>
-      input row description
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>const char * <parameter>colname</parameter></literal></term>
-    <listitem>
-     <para>
-      column name
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   Column number (count starts at 1), or
-   <symbol>SPI_ERROR_NOATTRIBUTE</symbol> if the named column was not
-   found.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-getvalue">
- <refmeta>
-  <refentrytitle>SPI_getvalue</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_getvalue</refname>
-  <refpurpose>return the string value of the specified column</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_getvalue</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-char * SPI_getvalue(HeapTuple <parameter>row</parameter>, TupleDesc <parameter>rowdesc</parameter>, int <parameter>colnumber</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_getvalue</function> returns the string representation
-   of the value of the specified column.
-  </para>
-
-  <para>
-   The result is returned in memory allocated using
-   <function>palloc</function>.  (You can use
-   <function>pfree</function> to release the memory when you don't
-   need it anymore.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>HeapTuple <parameter>row</parameter></literal></term>
-    <listitem>
-     <para>
-      input row to be examined
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TupleDesc <parameter>rowdesc</parameter></literal></term>
-    <listitem>
-     <para>
-      input row description
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>colnumber</parameter></literal></term>
-    <listitem>
-     <para>
-      column number (count starts at 1)
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   Column value, or <symbol>NULL</symbol> if the column is null,
-   <parameter>colnumber</parameter> is out of range
-   (<varname>SPI_result</varname> is set to
-   <symbol>SPI_ERROR_NOATTRIBUTE</symbol>), or no output function is
-   available (<varname>SPI_result</varname> is set to
-   <symbol>SPI_ERROR_NOOUTFUNC</symbol>).
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-getbinval">
- <refmeta>
-  <refentrytitle>SPI_getbinval</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_getbinval</refname>
-  <refpurpose>return the binary value of the specified column</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_getbinval</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-Datum SPI_getbinval(HeapTuple <parameter>row</parameter>, TupleDesc <parameter>rowdesc</parameter>, int <parameter>colnumber</parameter>,
-                    bool * <parameter>isnull</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_getbinval</function> returns the value of the
-   specified column in the internal form (as type <type>Datum</type>).
-  </para>
-
-  <para>
-   This function does not allocate new space for the datum.  In the
-   case of a pass-by-reference data type, the return value will be a
-   pointer into the passed row.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>HeapTuple <parameter>row</parameter></literal></term>
-    <listitem>
-     <para>
-      input row to be examined
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TupleDesc <parameter>rowdesc</parameter></literal></term>
-    <listitem>
-     <para>
-      input row description
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>colnumber</parameter></literal></term>
-    <listitem>
-     <para>
-      column number (count starts at 1)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>bool * <parameter>isnull</parameter></literal></term>
-    <listitem>
-     <para>
-      flag for a null value in the column
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   The binary value of the column is returned.  The variable pointed
-   to by <parameter>isnull</parameter> is set to true if the column is
-   null, else to false.
-  </para>
-
-  <para>
-   <varname>SPI_result</varname> is set to
-   <symbol>SPI_ERROR_NOATTRIBUTE</symbol> on error.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-gettype">
- <refmeta>
-  <refentrytitle>SPI_gettype</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_gettype</refname>
-  <refpurpose>return the data type name of the specified column</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_gettype</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-char * SPI_gettype(TupleDesc <parameter>rowdesc</parameter>, int <parameter>colnumber</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_gettype</function> returns a copy of the data type name of the
-   specified column.  (You can use <function>pfree</function> to
-   release the copy of the name when you don't need it anymore.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>TupleDesc <parameter>rowdesc</parameter></literal></term>
-    <listitem>
-     <para>
-      input row description
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>colnumber</parameter></literal></term>
-    <listitem>
-     <para>
-      column number (count starts at 1)
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   The data type name of the specified column, or
-   <symbol>NULL</symbol> on error.  <varname>SPI_result</varname> is
-   set to <symbol>SPI_ERROR_NOATTRIBUTE</symbol> on error.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-gettypeid">
- <refmeta>
-  <refentrytitle>SPI_gettypeid</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_gettypeid</refname>
-  <refpurpose>return the data type <acronym>OID</acronym> of the specified column</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_gettypeid</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-Oid SPI_gettypeid(TupleDesc <parameter>rowdesc</parameter>, int <parameter>colnumber</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_gettypeid</function> returns the
-   <acronym>OID</acronym> of the data type of the specified column.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>TupleDesc <parameter>rowdesc</parameter></literal></term>
-    <listitem>
-     <para>
-      input row description
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>colnumber</parameter></literal></term>
-    <listitem>
-     <para>
-      column number (count starts at 1)
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   The <acronym>OID</acronym> of the data type of the specified column
-   or <symbol>InvalidOid</symbol> on error.  On error,
-   <varname>SPI_result</varname> is set to
-   <symbol>SPI_ERROR_NOATTRIBUTE</symbol>.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-getrelname">
- <refmeta>
-  <refentrytitle>SPI_getrelname</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_getrelname</refname>
-  <refpurpose>return the name of the specified relation</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_getrelname</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-char * SPI_getrelname(Relation <parameter>rel</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_getrelname</function> returns a copy of the name of the
-   specified relation.  (You can use <function>pfree</function> to
-   release the copy of the name when you don't need it anymore.)
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>Relation <parameter>rel</parameter></literal></term>
-    <listitem>
-     <para>
-      input relation
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   The name of the specified relation.
-  </para>
- </refsect1>
-</refentry>
-
-<refentry id="spi-spi-getnspname">
- <refmeta>
-  <refentrytitle>SPI_getnspname</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_getnspname</refname>
-  <refpurpose>return the namespace of the specified relation</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_getnspname</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-char * SPI_getnspname(Relation <parameter>rel</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_getnspname</function> returns a copy of the name of
-   the namespace that the specified <structname>Relation</structname>
-   belongs to. This is equivalent to the relation's schema. You should
-   <function>pfree</function> the return value of this function when
-   you are finished with it.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>Relation <parameter>rel</parameter></literal></term>
-    <listitem>
-     <para>
-      input relation
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   The name of the specified relation's namespace.
-  </para>
- </refsect1>
-</refentry>
-
- </sect1>
-
- <sect1 id="spi-memory">
-  <title>Memory Management</title>
-
-&pgnotice;
-  <para>
-    <indexterm>
-     <primary>memory context</primary>
-     <secondary>in SPI</secondary>
-    </indexterm>
-   <productname>PostgreSQL</productname> allocates memory within
-   <firstterm>memory contexts</firstterm>, which provide a convenient method of
-   managing allocations made in many different places that need to
-   live for differing amounts of time.  Destroying a context releases
-   all the memory that was allocated in it.  Thus, it is not necessary
-   to keep track of individual objects to avoid memory leaks; instead
-   only a relatively small number of contexts have to be managed.
-   <function>palloc</function> and related functions allocate memory
-   from the <quote>current</> context.
-  </para>
-
-  <para>
-   <function>SPI_connect</function> creates a new memory context and
-   makes it current.  <function>SPI_finish</function> restores the
-   previous current memory context and destroys the context created by
-   <function>SPI_connect</function>.  These actions ensure that
-   transient memory allocations made inside your procedure are
-   reclaimed at procedure exit, avoiding memory leakage.
-  </para>
-
-  <para>
-   However, if your procedure needs to return an object in allocated
-   memory (such as a value of a pass-by-reference data type), you
-   cannot allocate that memory using <function>palloc</function>, at
-   least not while you are connected to SPI.  If you try, the object
-   will be deallocated by <function>SPI_finish</function>, and your
-   procedure will not work reliably.  To solve this problem, use
-   <function>SPI_palloc</function> to allocate memory for your return
-   object.  <function>SPI_palloc</function> allocates memory in the
-   <quote>upper executor context</quote>, that is, the memory context
-   that was current when <function>SPI_connect</function> was called,
-   which is precisely the right context for a value returned from your
-   procedure.
-  </para>
-
-  <para>
-   If <function>SPI_palloc</function> is called while the procedure is
-   not connected to SPI, then it acts the same as a normal
-   <function>palloc</function>.  Before a procedure connects to the
-   SPI manager, the current memory context is the upper executor
-   context, so all allocations made by the procedure via
-   <function>palloc</function> or by SPI utility functions are made in
-   this context.
-  </para>
-
-  <para>
-   When <function>SPI_connect</function> is called, the private
-   context of the procedure, which is created by
-   <function>SPI_connect</function>, is made the current context.  All
-   allocations made by <function>palloc</function>,
-   <function>repalloc</function>, or SPI utility functions (except for
-   <function>SPI_copytuple</function>,
-   <function>SPI_returntuple</function>,
-   <function>SPI_modifytuple</function>, and
-   <function>SPI_palloc</function>) are made in this context.  When a
-   procedure disconnects from the SPI manager (via
-   <function>SPI_finish</function>) the current context is restored to
-   the upper executor context, and all allocations made in the
-   procedure memory context are freed and cannot be used any more.
-  </para>
-
-  <para>
-   All functions described in this section can be used by both
-   connected and unconnected procedures.  In an unconnected procedure,
-   they act the same as the underlying ordinary server functions
-   (<function>palloc</>, etc.).
-  </para>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-palloc">
- <refmeta>
-  <refentrytitle>SPI_palloc</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_palloc</refname>
-  <refpurpose>allocate memory in the upper executor context</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_palloc</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void * SPI_palloc(Size <parameter>size</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_palloc</function> allocates memory in the upper
-   executor context.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>Size <parameter>size</parameter></literal></term>
-    <listitem>
-     <para>
-      size in bytes of storage to allocate
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   pointer to new storage space of the specified size
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-realloc">
- <refmeta>
-  <refentrytitle>SPI_repalloc</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_repalloc</refname>
-  <refpurpose>reallocate memory in the upper executor context</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_repalloc</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void * SPI_repalloc(void * <parameter>pointer</parameter>, Size <parameter>size</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_repalloc</function> changes the size of a memory
-   segment previously allocated using <function>SPI_palloc</function>.
-  </para>
-
-  <para>
-   This function is no longer different from plain
-   <function>repalloc</function>.  It's kept just for backward
-   compatibility of existing code.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>void * <parameter>pointer</parameter></literal></term>
-    <listitem>
-     <para>
-      pointer to existing storage to change
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Size <parameter>size</parameter></literal></term>
-    <listitem>
-     <para>
-      size in bytes of storage to allocate
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   pointer to new storage space of specified size with the contents
-   copied from the existing area
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-pfree">
- <refmeta>
-  <refentrytitle>SPI_pfree</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_pfree</refname>
-  <refpurpose>free memory in the upper executor context</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_pfree</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void SPI_pfree(void * <parameter>pointer</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_pfree</function> frees memory previously allocated
-   using <function>SPI_palloc</function> or
-   <function>SPI_repalloc</function>.
-  </para>
-
-  <para>
-   This function is no longer different from plain
-   <function>pfree</function>.  It's kept just for backward
-   compatibility of existing code.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>void * <parameter>pointer</parameter></literal></term>
-    <listitem>
-     <para>
-      pointer to existing storage to free
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-copytuple">
- <refmeta>
-  <refentrytitle>SPI_copytuple</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_copytuple</refname>
-  <refpurpose>make a copy of a row in the upper executor context</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_copytuple</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-HeapTuple SPI_copytuple(HeapTuple <parameter>row</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_copytuple</function> makes a copy of a row in the
-   upper executor context.  This is normally used to return a modified
-   row from a trigger.  In a function declared to return a composite
-   type, use <function>SPI_returntuple</function> instead.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>HeapTuple <parameter>row</parameter></literal></term>
-    <listitem>
-     <para>
-      row to be copied
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   the copied row; <symbol>NULL</symbol> only if
-   <parameter>tuple</parameter> is <symbol>NULL</symbol>
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-returntuple">
- <refmeta>
-  <refentrytitle>SPI_returntuple</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_returntuple</refname>
-  <refpurpose>prepare to return a tuple as a Datum</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_returntuple</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-HeapTupleHeader SPI_returntuple(HeapTuple <parameter>row</parameter>, TupleDesc <parameter>rowdesc</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_returntuple</function> makes a copy of a row in
-   the upper executor context, returning it in the form of a row type <type>Datum</type>.
-   The returned pointer need only be converted to <type>Datum</type> via <function>PointerGetDatum</function>
-   before returning.
-  </para>
-
-  <para>
-   Note that this should be used for functions that are declared to return
-   composite types.  It is not used for triggers; use
-   <function>SPI_copytuple</> for returning a modified row in a trigger.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>HeapTuple <parameter>row</parameter></literal></term>
-    <listitem>
-     <para>
-      row to be copied
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>TupleDesc <parameter>rowdesc</parameter></literal></term>
-    <listitem>
-     <para>
-      descriptor for row (pass the same descriptor each time for most
-      effective caching)
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   <type>HeapTupleHeader</type> pointing to copied row;
-   <symbol>NULL</symbol> only if
-   <parameter>row</parameter> or <parameter>rowdesc</parameter> is
-   <symbol>NULL</symbol>
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-modifytuple">
- <refmeta>
-  <refentrytitle>SPI_modifytuple</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_modifytuple</refname>
-  <refpurpose>create a row by replacing selected fields of a given row</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_modifytuple</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-HeapTuple SPI_modifytuple(Relation <parameter>rel</parameter>, HeapTuple <parameter>row</parameter>, int <parameter>ncols</parameter>,
-                          int * <parameter>colnum</parameter>, Datum * <parameter>values</parameter>, const char * <parameter>nulls</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_modifytuple</function> creates a new row by
-   substituting new values for selected columns, copying the original
-   row's columns at other positions.  The input row is not modified.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>Relation <parameter>rel</parameter></literal></term>
-    <listitem>
-     <para>
-      Used only as the source of the row descriptor for the row.
-      (Passing a relation rather than a row descriptor is a
-      misfeature.)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>HeapTuple <parameter>row</parameter></literal></term>
-    <listitem>
-     <para>
-      row to be modified
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int <parameter>ncols</parameter></literal></term>
-    <listitem>
-     <para>
-      number of column numbers in the array
-      <parameter>colnum</parameter>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>int * <parameter>colnum</parameter></literal></term>
-    <listitem>
-     <para>
-      array of the numbers of the columns that are to be changed
-      (column numbers start at 1)
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>Datum * <parameter>values</parameter></literal></term>
-    <listitem>
-     <para>
-      new values for the specified columns
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>const char * <parameter>Nulls</parameter></literal></term>
-    <listitem>
-     <para>
-      which new values are null, if any (see
-      <function>SPI_execute_plan</function> for the format)
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   new row with modifications, allocated in the upper executor
-   context; <symbol>NULL</symbol> only if <parameter>row</parameter>
-   is <symbol>NULL</symbol>
-  </para>
-
-  <para>
-   On error, <varname>SPI_result</varname> is set as follows:
-   <variablelist>
-    <varlistentry>
-     <term><symbol>SPI_ERROR_ARGUMENT</symbol></term>
-     <listitem>
-      <para>
-       if <parameter>rel</> is <symbol>NULL</>, or if
-       <parameter>row</> is <symbol>NULL</>, or if <parameter>ncols</>
-       is less than or equal to 0, or if <parameter>colnum</> is
-       <symbol>NULL</>, or if <parameter>values</> is <symbol>NULL</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><symbol>SPI_ERROR_NOATTRIBUTE</symbol></term>
-     <listitem>
-      <para>
-       if <parameter>colnum</> contains an invalid column number (less
-       than or equal to 0 or greater than the number of column in
-       <parameter>row</>)
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-freetuple">
- <refmeta>
-  <refentrytitle>SPI_freetuple</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_freetuple</refname>
-  <refpurpose>free a row allocated in the upper executor context</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_freetuple</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void SPI_freetuple(HeapTuple <parameter>row</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_freetuple</function> frees a row previously allocated
-   in the upper executor context.
-  </para>
-
-  <para>
-   This function is no longer different from plain
-   <function>heap_freetuple</function>.  It's kept just for backward
-   compatibility of existing code.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>HeapTuple <parameter>row</parameter></literal></term>
-    <listitem>
-     <para>
-      row to free
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-freetupletable">
- <refmeta>
-  <refentrytitle>SPI_freetuptable</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_freetuptable</refname>
-  <refpurpose>free a row set created by <function>SPI_execute</> or a similar
-  function</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_freetuptable</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-void SPI_freetuptable(SPITupleTable * <parameter>tuptable</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_freetuptable</function> frees a row set created by a
-   prior SPI command execution function, such as
-   <function>SPI_execute</>.  Therefore, this function is usually called
-   with the global variable <varname>SPI_tupletable</varname> as
-   argument.
-  </para>
-
-  <para>
-   This function is useful if a SPI procedure needs to execute
-   multiple commands and does not want to keep the results of earlier
-   commands around until it ends.  Note that any unfreed row sets will
-   be freed anyway at <function>SPI_finish</>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>SPITupleTable * <parameter>tuptable</parameter></literal></term>
-    <listitem>
-     <para>
-      pointer to row set to free
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-</refentry>
-
-<!-- *********************************************** -->
-
-<refentry id="spi-spi-freeplan">
- <refmeta>
-  <refentrytitle>SPI_freeplan</refentrytitle>
-  <manvolnum>3</manvolnum>
- </refmeta>
-
- <refnamediv>
-  <refname>SPI_freeplan</refname>
-  <refpurpose>free a previously saved plan</refpurpose>
- </refnamediv>
-
- <indexterm><primary>SPI_freeplan</primary></indexterm>
-
- <refsynopsisdiv>
-<synopsis>
-int SPI_freeplan(SPIPlanPtr <parameter>plan</parameter>)
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <function>SPI_freeplan</function> releases a command execution plan
-   previously returned by <function>SPI_prepare</function> or saved by
-   <function>SPI_saveplan</function>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Arguments</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><literal>SPIPlanPtr <parameter>plan</parameter></literal></term>
-    <listitem>
-     <para>
-      pointer to plan to free
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Return Value</title>
-
-  <para>
-   <symbol>SPI_ERROR_ARGUMENT</symbol> if <parameter>plan</parameter>
-   is <symbol>NULL</symbol> or invalid
-  </para>
- </refsect1>
-</refentry>
-
- </sect1>
-
- <sect1 id="spi-visibility">
-  <title>Visibility of Data Changes</title>
-
-&pgnotice;
-  <para>
-   The following rules govern the visibility of data changes in
-   functions that use SPI (or any other C function):
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      During the execution of an SQL command, any data changes made by
-      the command are invisible to the command itself.  For
-      example, in:
-<programlisting>
-INSERT INTO a SELECT * FROM a;
-</programlisting>
-      the inserted rows are invisible to the <command>SELECT</command>
-      part.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Changes made by a command C are visible to all commands that are
-      started after C, no matter whether they are started inside C
-      (during the execution of C) or after C is done.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Commands executed via SPI inside a function called by an SQL command
-      (either an ordinary function or a trigger) follow one or the
-      other of the above rules depending on the read/write flag passed
-      to SPI.  Commands executed in read-only mode follow the first
-      rule: they cannot see changes of the calling command.  Commands executed
-      in read-write mode follow the second rule: they can see all changes made
-      so far.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      All standard procedural languages set the SPI read-write mode
-      depending on the volatility attribute of the function.  Commands of
-      <literal>STABLE</> and <literal>IMMUTABLE</> functions are done in
-      read-only mode, while commands of <literal>VOLATILE</> functions are
-      done in read-write mode.  While authors of C functions are able to
-      violate this convention, it's unlikely to be a good idea to do so.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   The next section contains an example that illustrates the
-   application of these rules.
-  </para>
- </sect1>
-
- <sect1 id="spi-examples">
-  <title>Examples</title>
-
-&pgnotice;
-  <para>
-   This section contains a very simple example of SPI usage. The
-   procedure <function>execq</function> takes an SQL command as its
-   first argument and a row count as its second, executes the command
-   using <function>SPI_exec</function> and returns the number of rows
-   that were processed by the command.  You can find more complex
-   examples for SPI in the source tree in
-   <filename>src/test/regress/regress.c</filename> and in the
-   <xref linkend="contrib-spi"> module.
-  </para>
-
-<programlisting>
-#include "postgres.h"
-
-#include "executor/spi.h"
-#include "utils/builtins.h"
-
-#ifdef PG_MODULE_MAGIC
-PG_MODULE_MAGIC;
-#endif
-
-int execq(text *sql, int cnt);
-
-int
-execq(text *sql, int cnt)
-{
-    char *command;
-    int ret;
-    int proc;
-
-    /* Convert given text object to a C string */
-    command = text_to_cstring(sql);
-
-    SPI_connect();
-
-    ret = SPI_exec(command, cnt);
-
-    proc = SPI_processed;
-    /*
-     * If some rows were fetched, print them via elog(INFO).
-     */
-    if (ret &gt; 0 &amp;&amp; SPI_tuptable != NULL)
-    {
-        TupleDesc tupdesc = SPI_tuptable-&gt;tupdesc;
-        SPITupleTable *tuptable = SPI_tuptable;
-        char buf[8192];
-        int i, j;
-
-        for (j = 0; j &lt; proc; j++)
-        {
-            HeapTuple tuple = tuptable-&gt;vals[j];
-
-            for (i = 1, buf[0] = 0; i &lt;= tupdesc-&gt;natts; i++)
-                snprintf(buf + strlen (buf), sizeof(buf) - strlen(buf), " %s%s",
-                        SPI_getvalue(tuple, tupdesc, i),
-                        (i == tupdesc-&gt;natts) ? " " : " |");
-            elog(INFO, "EXECQ: %s", buf);
-        }
-    }
-
-    SPI_finish();
-    pfree(command);
-
-    return (proc);
-}
-</programlisting>
-
-  <para>
-   (This function uses call convention version 0, to make the example
-   easier to understand.  In real applications you should use the new
-   version 1 interface.)
-  </para>
-
-  <para>
-   This is how you declare the function after having compiled it into
-   a shared library (details are in <xref linkend="dfunc">.):
-
-<programlisting>
-CREATE FUNCTION execq(text, integer) RETURNS integer
-    AS '<replaceable>filename</replaceable>'
-    LANGUAGE C;
-</programlisting>
-  </para>
-
-  <para>
-   Here is a sample session:
-
-<programlisting>
-=&gt; SELECT execq('CREATE TABLE a (x integer)', 0);
- execq
--------
-     0
-(1 row)
-
-=&gt; INSERT INTO a VALUES (execq('INSERT INTO a VALUES (0)', 0));
-INSERT 0 1
-=&gt; SELECT execq('SELECT * FROM a', 0);
-INFO:  EXECQ:  0    -- inserted by execq
-INFO:  EXECQ:  1    -- returned by execq and inserted by upper INSERT
-
- execq
--------
-     2
-(1 row)
-
-=&gt; SELECT execq('INSERT INTO a SELECT x + 2 FROM a', 1);
- execq
--------
-     1
-(1 row)
-
-=&gt; SELECT execq('SELECT * FROM a', 10);
-INFO:  EXECQ:  0
-INFO:  EXECQ:  1
-INFO:  EXECQ:  2    -- 0 + 2, only one row inserted - as specified
-
- execq
--------
-     3              -- 10 is the max value only, 3 is the real number of rows
-(1 row)
-
-=&gt; DELETE FROM a;
-DELETE 3
-=&gt; INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1);
-INSERT 0 1
-=&gt; SELECT * FROM a;
- x
----
- 1                  -- no rows in a (0) + 1
-(1 row)
-
-=&gt; INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1);
-INFO:  EXECQ:  1
-INSERT 0 1
-=&gt; SELECT * FROM a;
- x
----
- 1
- 2                  -- there was one row in a + 1
-(2 rows)
-
--- This demonstrates the data changes visibility rule:
-
-=&gt; INSERT INTO a SELECT execq('SELECT * FROM a', 0) * x FROM a;
-INFO:  EXECQ:  1
-INFO:  EXECQ:  2
-INFO:  EXECQ:  1
-INFO:  EXECQ:  2
-INFO:  EXECQ:  2
-INSERT 0 2
-=&gt; SELECT * FROM a;
- x
----
- 1
- 2
- 2                  -- 2 rows * 1 (x in first row)
- 6                  -- 3 rows (2 + 1 just inserted) * 2 (x in second row)
-(4 rows)               ^^^^^^
-                       rows visible to execq() in different invocations
-</programlisting>
-  </para>
- </sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/sql.sgmlin b/doc-xc/src/sgml/sql.sgmlin
deleted file mode 100644
index 88408ced7a..0000000000
--- a/doc-xc/src/sgml/sql.sgmlin
+++ /dev/null
@@ -1,2195 +0,0 @@
-<!-- doc/src/sgml/sql.sgml -->
-
- <chapter id="sql-intro">
-  <title>SQL</title>
-
-&common;
-
-  <abstract>
-   <para>
-    This chapter introduces the mathematical concepts behind
-    relational databases. It is not required reading, so if you bog
-    down or want to get straight to some simple examples feel free to
-    jump ahead to the next chapter and come back when you have more
-    time and patience. This stuff is supposed to be fun!
-   </para>
-
-   <para>
-    This material originally appeared as a part of
-    Stefan Simkovics' Master's Thesis
-    (<xref linkend="SIM98" endterm="SIM98">).
-   </para>
-  </abstract>
-
-  <para>
-   <acronym>SQL</acronym> has become the most popular relational query
-   language.
-   The name <quote><acronym>SQL</acronym></quote> is an abbreviation for
-   <firstterm>Structured Query Language</firstterm>.
-   In 1974 Donald Chamberlin and others defined the
-   language SEQUEL (<firstterm>Structured English Query
-    Language</firstterm>) at IBM
-   Research. This language was first implemented in an IBM
-   prototype called SEQUEL-XRM in 1974-75. In 1976-77 a revised version
-   of SEQUEL called SEQUEL/2 was defined and the name was changed to
-   <acronym>SQL</acronym>
-   subsequently.
-  </para>
-
-  <para>
-   A new prototype called System R was developed by IBM in 1977. System R
-   implemented a large subset of SEQUEL/2 (now <acronym>SQL</acronym>)
-   and a number of
-   changes were made to <acronym>SQL</acronym> during the project.
-   System R was installed in
-   a number of user sites, both internal IBM sites and also some selected
-   customer sites. Thanks to the success and acceptance of System R at
-   those user sites IBM started to develop commercial products that
-   implemented the <acronym>SQL</acronym> language based on the System
-   R technology.
-  </para>
-
-  <para>
-   Over the next years IBM and also a number of other vendors announced
-   <acronym>SQL</acronym> products such as
-   <productname>SQL/DS</productname> (IBM),
-   <productname>DB2</productname> (IBM),
-   <productname>ORACLE</productname> (Oracle Corp.),
-   <productname>DG/SQL</productname> (Data General Corp.),
-   and <productname>SYBASE</productname> (Sybase Inc.).
-  </para>
-
-  <para>
-   <acronym>SQL</acronym> is also an official standard now. In 1982
-   the American National
-   Standards Institute (<acronym>ANSI</acronym>) chartered its
-   Database Committee X3H2 to
-   develop a proposal for a standard relational language. This proposal
-   was ratified in 1986 and consisted essentially of the IBM dialect of
-   <acronym>SQL</acronym>. In 1987 this <acronym>ANSI</acronym>
-   standard was also accepted as an international
-   standard by the International Organization for Standardization
-   (<acronym>ISO</acronym>).
-   This original standard version of <acronym>SQL</acronym> is often
-   referred to,
-   informally, as <quote><abbrev>SQL/86</abbrev></quote>. In 1989 the original
-   standard was extended
-   and this new standard is often, again informally, referred to as
-   <quote><abbrev>SQL/89</abbrev></quote>. Also in 1989, a related standard called
-   <firstterm>Database Language Embedded <acronym>SQL</acronym></firstterm>
-   (<acronym>ESQL</acronym>) was developed.
-  </para>
-
-  <para>
-   The <acronym>ISO</acronym> and <acronym>ANSI</acronym> committees
-   have been working for many years on the
-   definition of a greatly expanded version of the original standard,
-   referred to informally as <firstterm><acronym>SQL2</acronym></firstterm>
-   or <firstterm><acronym>SQL/92</acronym></firstterm>. This version became a
-   ratified standard - <quote>International Standard ISO/IEC 9075:1992,
-   Database Language <acronym>SQL</acronym></quote> - in late 1992.
-   <acronym>SQL/92</acronym> is the version
-   normally meant when people refer to <quote>the <acronym>SQL</acronym>
-   standard</quote>. A detailed
-   description of <acronym>SQL/92</acronym> is given in
-   <xref linkend="DATE97" endterm="DATE97">. At the time of
-   writing this document a new standard informally referred to
-   as <firstterm><acronym>SQL3</acronym></firstterm>
-   is under development. It is planned to make <acronym>SQL</acronym>
-   a Turing-complete
-   language, i.e., all computable queries (e.g., recursive queries) will be
-   possible. This has now been completed as SQL:2003.
-  </para>
-
-  <sect1 id="rel-model">
-   <title>The Relational Data Model</title>
-&common;
-  <para>
-    As mentioned before, <acronym>SQL</acronym> is a relational
-    language. That means it is
-    based on the <firstterm>relational data model</firstterm>
-    first published by E.F. Codd in
-    1970. We will give a formal description of the relational model
-    later (in
-    <xref linkend="formal-notion" endterm="formal-notion">)
-    but first we want to have a look at it from a more intuitive
-    point of view.
-  </para>
-
-  <para>
-    A <firstterm>relational database</firstterm> is a database that is
-    perceived by its
-    users as a <firstterm>collection of tables</firstterm> (and
-    nothing else but tables).
-    A table consists of rows and columns where each row represents a
-    record and each column represents an attribute of the records
-    contained in the table.
-    <xref linkend="supplier-fig" endterm="supplier-fig">
-    shows an example of a database consisting of three tables:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       SUPPLIER is a table storing the number
-       (SNO), the name (SNAME) and the city (CITY) of a supplier.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       PART is a table storing the number (PNO) the name (PNAME) and
-       the price (PRICE) of a part.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       SELLS stores information about which part (PNO) is sold by which
-       supplier (SNO).
-       It serves in a sense to connect the other two tables together.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    <example>
-     <title id="supplier-fig">The Suppliers and Parts Database</title>
-<screen>
-SUPPLIER:                   SELLS:
- SNO |  SNAME  |  CITY       SNO | PNO
-----+---------+--------     -----+-----
- 1  |  Smith  | London        1  |  1
- 2  |  Jones  | Paris         1  |  2
- 3  |  Adams  | Vienna        2  |  4
- 4  |  Blake  | Rome          3  |  1
-                              3  |  3
-                              4  |  2
-PART:                         4  |  3
- PNO |  PNAME  |  PRICE       4  |  4
-----+---------+---------
- 1  |  Screw  |   10
- 2  |  Nut    |    8
- 3  |  Bolt   |   15
- 4  |  Cam    |   25
-</screen>
-    </example>
-   </para>
-
-   <para>
-    The tables PART and SUPPLIER can be regarded as
-    <firstterm>entities</firstterm> and
-    SELLS can be regarded as a <firstterm>relationship</firstterm>
-    between a particular
-    part and a particular supplier.
-   </para>
-
-   <para>
-    As we will see later, <acronym>SQL</acronym> operates on tables
-    like the ones just
-    defined but before that we will study the theory of the relational
-    model.
-   </para>
-  </sect1>
-
-  <sect1 id="relmodel-formal">
-   <title id="formal-notion">Relational Data Model Formalities</title>
-&common;
-   <para>
-    The mathematical concept underlying the relational model is the
-    set-theoretic <firstterm>relation</firstterm> which is a subset of
-    the Cartesian
-    product of a list of domains. This set-theoretic relation gives
-    the model its name (do not confuse it with the relationship from the
-    <firstterm>Entity-Relationship model</firstterm>).
-    Formally a domain is simply a set of
-    values. For example the set of integers is a domain. Also the set of
-    character strings of length 20 and the real numbers are examples of
-    domains.
-   </para>
-
-   <para>
-<!--
-\begin{definition}
-The <firstterm>Cartesian product</firstterm> of domains $D_{1},
-    D_{2},\ldots, D_{k}$ written
-\mbox{$D_{1} \times D_{2} \times \ldots \times D_{k}$} is the set of
-all $k$-tuples $(v_{1},v_{2},\ldots,v_{k})$ such that \mbox{$v_{1} \in
-D_{1}, v_{2} \in D_{2}, \ldots, v_{k} \in D_{k}$}.
-\end{definition}
--->
-    The <firstterm>Cartesian product</firstterm> of domains
-    <parameter>D<subscript>1</subscript></parameter>,
-    <parameter>D<subscript>2</subscript></parameter>,
-    ...
-    <parameter>D<subscript>k</subscript></parameter>,
-    written
-    <parameter>D<subscript>1</subscript></parameter> &times;
-    <parameter>D<subscript>2</subscript></parameter> &times;
-    ... &times;
-    <parameter>D<subscript>k</subscript></parameter>
-    is the set of all k-tuples
-    <parameter>v<subscript>1</subscript></parameter>,
-    <parameter>v<subscript>2</subscript></parameter>,
-    ...
-    <parameter>v<subscript>k</subscript></parameter>,
-    such that
-    <parameter>v<subscript>1</subscript></parameter> &isin;
-    <parameter>D<subscript>1</subscript></parameter>,
-    <parameter>v<subscript>2</subscript></parameter> &isin;
-    <parameter>D<subscript>2</subscript></parameter>,
-    ...
-    <parameter>v<subscript>k</subscript></parameter> &isin;
-    <parameter>D<subscript>k</subscript></parameter>.
-   </para>
-
-   <para>
-    For example, when we have
-<!--
- $k=2$, $D_{1}=\{0,1\}$ and
-$D_{2}=\{a,b,c\}$, then $D_{1} \times D_{2}$ is
-$\{(0,a),(0,b),(0,c),(1,a),(1,b),(1,c)\}$.
--->
-    <parameter>k</parameter>=2,
-    <parameter>D<subscript>1</subscript></parameter>=<literal>{0,1}</literal> and
-    <parameter>D<subscript>2</subscript></parameter>=<literal>{a,b,c}</literal> then
-    <parameter>D<subscript>1</subscript></parameter> &times;
-    <parameter>D<subscript>2</subscript></parameter> is
-    <literal>{(0,a),(0,b),(0,c),(1,a),(1,b),(1,c)}</literal>.
-   </para>
-
-   <para>
-<!--
-\begin{definition}
-A Relation is any subset of the Cartesian product of one or more
-domains: $R \subseteq$ \mbox{$D_{1} \times D_{2} \times \ldots \times D_{k}$}
-\end{definition}
--->
-    A Relation is any subset of the Cartesian product of one or more
-    domains: <parameter>R</parameter> &sube;
-    <parameter>D<subscript>1</subscript></parameter> &times;
-    <parameter>D<subscript>2</subscript></parameter> &times;
-    ... &times;
-    <parameter>D<subscript>k</subscript></parameter>.
-   </para>
-
-   <para>
-    For example <literal>{(0,a),(0,b),(1,a)}</literal> is a relation;
-    it is in fact a subset of
-    <parameter>D<subscript>1</subscript></parameter> &times;
-    <parameter>D<subscript>2</subscript></parameter>
-    mentioned above.
-   </para>
-
-   <para>
-    The members of a relation are called tuples. Each relation of some
-    Cartesian product
-    <parameter>D<subscript>1</subscript></parameter> &times;
-    <parameter>D<subscript>2</subscript></parameter> &times;
-    ... &times;
-    <parameter>D<subscript>k</subscript></parameter>
-    is said to have arity <literal>k</literal> and is therefore a set
-    of <literal>k</literal>-tuples.
-   </para>
-
-   <para>
-    A relation can be viewed as a table (as we already did, remember
-    <xref linkend="supplier-fig" endterm="supplier-fig"> where
-    every tuple is represented by a row and every column corresponds to
-    one component of a tuple. Giving names (called attributes) to the
-    columns leads to the definition of a
-    <firstterm>relation scheme</firstterm>.
-   </para>
-
-   <para>
-<!--
-\begin{definition}
-A {\it relation scheme} $R$ is a finite set of attributes
-\mbox{$\{A_{1},A_{2},\ldots,A_{k}\}$}. There is a domain $D_{i}$ for
-each attribute $A_{i}, 1 \le i \le k$ where the values of the
-attributes are taken from. We often write a relation scheme as
-\mbox{$R(A_{1},A_{2},\ldots,A_{k})$}.
-\end{definition}
--->
-    A <firstterm>relation scheme</firstterm> <literal>R</literal> is a
-    finite set of attributes
-    <parameter>A<subscript>1</subscript></parameter>,
-    <parameter>A<subscript>2</subscript></parameter>,
-    ...
-    <parameter>A<subscript>k</subscript></parameter>.
-    There is a domain
-    <parameter>D<subscript>i</subscript></parameter>,
-    for each attribute
-    <parameter>A<subscript>i</subscript></parameter>,
-    1 &lt;= <literal>i</literal> &lt;= <literal>k</literal>,
-    where the values of the attributes are taken from. We often write
-    a relation scheme as
-    <literal>R(<parameter>A<subscript>1</subscript></parameter>,
-    <parameter>A<subscript>2</subscript></parameter>,
-    ...
-    <parameter>A<subscript>k</subscript></parameter>)</literal>.
-
-    <note>
-     <para>
-      A <firstterm>relation scheme</firstterm> is just a kind of template
-      whereas a <firstterm>relation</firstterm> is an instance of a
-      <firstterm>relation
-       scheme</firstterm>. The relation consists of tuples (and can
-      therefore be
-      viewed as a table); not so the relation scheme.
-     </para>
-    </note>
-   </para>
-
-   <sect2>
-    <title id="domains">Domains vs. Data Types</title>
-&common;
-    <para>
-     We often talked about <firstterm>domains</firstterm>
-     in the last section. Recall that a
-     domain is, formally, just a set of values (e.g., the set of integers or
-     the real numbers). In terms of database systems we often talk of
-     <firstterm>data types</firstterm> instead of domains.
-     When we define a table we have to make
-     a decision about which attributes to include. Additionally we
-     have to decide which kind of data is going to be stored as
-     attribute values. For example the values of
-     <classname>SNAME</classname> from the table
-     <classname>SUPPLIER</classname> will be character strings,
-     whereas <classname>SNO</classname> will store
-     integers. We define this by assigning a data type to each
-     attribute. The type of <classname>SNAME</classname> will be
-     <type>VARCHAR(20)</type> (this is the <acronym>SQL</acronym> type
-     for character strings of length &lt;= 20),
-     the type of <classname>SNO</classname> will be
-     <type>INTEGER</type>. With the assignment of a data type we also
-     have selected
-     a domain for an attribute. The domain of
-     <classname>SNAME</classname> is the set of all
-     character strings of length &lt;= 20,
-     the domain of <classname>SNO</classname> is the set of
-     all integer numbers.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="relmodel-oper">
-   <title id="operations">Operations in the Relational Data Model</title>
-&common;
-   <para>
-    In the previous section
-    (<xref linkend="formal-notion" endterm="formal-notion">)
-    we defined the mathematical notion of
-    the relational model. Now we know how the data can be stored using a
-    relational data model but we do not know what to do with all these
-    tables to retrieve something from the database yet. For example somebody
-    could ask for the names of all suppliers that sell the part
-    'Screw'. Therefore two rather different kinds of notations for
-    expressing operations on relations have been defined:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       The <firstterm>Relational Algebra</firstterm> which is an
-       algebraic notation,
-       where queries are expressed by applying specialized operators to the
-       relations.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The <firstterm>Relational Calculus</firstterm> which is a
-       logical notation,
-       where queries are expressed by formulating some logical restrictions
-       that the tuples in the answer must satisfy.
-      </para>
-    </listitem>
-    </itemizedlist>
-   </para>
-
-   <sect2>
-    <title id="rel-alg">Relational Algebra</title>
-&common;
-    <para>
-     The <firstterm>Relational Algebra</firstterm> was introduced by
-     E. F. Codd in 1972. It consists of a set of operations on relations:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        SELECT (&sigma;): extracts <firstterm>tuples</firstterm> from
-        a relation that
-        satisfy a given restriction. Let <parameter>R</parameter> be a
-        table that contains an attribute
-        <parameter>A</parameter>.
-&sigma;<subscript>A=a</subscript>(R) = {t &isin; R &mid; t(A) = a}
-        where <literal>t</literal> denotes a
-        tuple of <parameter>R</parameter> and <literal>t(A)</literal>
-        denotes the value of attribute <parameter>A</parameter> of
-        tuple <literal>t</literal>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        PROJECT (&pi;): extracts specified
-        <firstterm>attributes</firstterm> (columns) from a
-        relation. Let <classname>R</classname> be a relation
-        that contains an attribute <classname>X</classname>.
-        &pi;<subscript>X</subscript>(<classname>R</classname>) = {t(X) &mid; t &isin; <classname>R</classname>},
-        where <literal>t</literal>(<classname>X</classname>) denotes the value of
-        attribute <classname>X</classname> of tuple <literal>t</literal>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        PRODUCT (&times;): builds the Cartesian product of two
-        relations. Let <classname>R</classname> be a table with arity
-        <literal>k</literal><subscript>1</subscript> and let
-        <classname>S</classname> be a table with
-        arity <literal>k</literal><subscript>2</subscript>.
-        <classname>R</classname> &times; <classname>S</classname>
-        is the set of all
-        <literal>k</literal><subscript>1</subscript>
-        + <literal>k</literal><subscript>2</subscript>-tuples
-        whose first <literal>k</literal><subscript>1</subscript>
-        components form a tuple in <classname>R</classname> and whose last
-        <literal>k</literal><subscript>2</subscript> components form a
-        tuple in <classname>S</classname>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        UNION (&cup;): builds the set-theoretic union of two
-        tables. Given the tables <classname>R</classname> and
-        <classname>S</classname> (both must have the same arity),
-        the union <classname>R</classname> &cup; <classname>S</classname>
-        is the set of tuples that are in <classname>R</classname>
-        or <classname>S</classname> or both.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        INTERSECT (&cap;): builds the set-theoretic intersection of two
-        tables. Given the tables <classname>R</classname> and
-        <classname>S</classname>,
-        <classname>R</classname> &cap; <classname>S</classname> is the
-        set of tuples
-        that are in <classname>R</classname> and in
-        <classname>S</classname>.
-        We again require that <classname>R</classname> and
-        <classname>S</classname> have the
-        same arity.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        DIFFERENCE (&minus; or &setmn;): builds the set difference of
-        two tables. Let <classname>R</classname> and <classname>S</classname>
-        again be two tables with the same
-        arity. <classname>R</classname> - <classname>S</classname>
-        is the set of tuples in <classname>R</classname> but not in
-        <classname>S</classname>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        JOIN (&prod;): connects two tables by their common
-        attributes. Let <classname>R</classname> be a table with the
-        attributes <classname>A</classname>,<classname>B</classname>
-        and <classname>C</classname> and
-        let <classname>S</classname> be a table with the attributes
-        <classname>C</classname>,<classname>D</classname>
-        and <classname>E</classname>. There is one
-        attribute common to both relations,
-        the attribute <classname>C</classname>.
-<!--
-        <classname>R</classname> &prod; <classname>S</classname> =
-        &pi;<subscript><classname>R</classname>.<classname>A</classname>,<classname>R</classname>.<classname>B</classname>,<classname>R</classname>.<classname>C</classname>,<classname>S</classname>.<classname>D</classname>,<classname>S</classname>.<classname>E</classname></subscript>(&sigma;<subscript><classname>R</classname>.<classname>C</classname>=<classname>S</classname>.<classname>C</classname></subscript>(<classname>R</classname> &times; <classname>S</classname>)).
--->
-        R &prod; S = &pi;<subscript>R.A,R.B,R.C,S.D,S.E</subscript>(&sigma;<subscript>R.C=S.C</subscript>(R &times; S)).
-        What are we doing here? We first calculate the Cartesian
-        product
-        <classname>R</classname> &times; <classname>S</classname>.
-        Then we select those tuples whose values for the common
-        attribute <classname>C</classname> are equal
-        (&sigma;<subscript>R.C = S.C</subscript>).
-        Now we have a table
-        that contains the attribute <classname>C</classname>
-        two times and we correct this by
-        projecting out the duplicate column.
-       </para>
-
-       <example>
-        <title id="join-example">An Inner Join</title>
-
-        <para>
-         Let's have a look at the tables that are produced by evaluating the steps
-         necessary for a join.
-         Let the following two tables be given:
-
-<screen>
-R:                 S:
- A | B | C          C | D | E
----+---+---        ---+---+---
- 1 | 2 | 3          3 | a | b
- 4 | 5 | 6          6 | c | d
- 7 | 8 | 9
-</screen>
-        </para>
-       </example>
-
-       <para>
-        First we calculate the Cartesian product
-        <classname>R</classname> &times; <classname>S</classname> and
-        get:
-
-<screen>
-R x S:
- A | B | R.C | S.C | D | E
----+---+-----+-----+---+---
- 1 | 2 |  3  |  3  | a | b
- 1 | 2 |  3  |  6  | c | d
- 4 | 5 |  6  |  3  | a | b
- 4 | 5 |  6  |  6  | c | d
- 7 | 8 |  9  |  3  | a | b
- 7 | 8 |  9  |  6  | c | d
-</screen>
-       </para>
-
-       <para>
-        After the selection
-        &sigma;<subscript>R.C=S.C</subscript>(R &times; S)
-        we get:
-
-<screen>
- A | B | R.C | S.C | D | E
----+---+-----+-----+---+---
- 1 | 2 |  3  |  3  | a | b
- 4 | 5 |  6  |  6  | c | d
-</screen>
-       </para>
-
-       <para>
-        To remove the duplicate column
-        <classname>S</classname>.<classname>C</classname>
-        we project it out by the following operation:
-        &pi;<subscript>R.A,R.B,R.C,S.D,S.E</subscript>(&sigma;<subscript>R.C=S.C</subscript>(R &times; S))
-        and get:
-
-<screen>
- A | B | C | D | E
----+---+---+---+---
- 1 | 2 | 3 | a | b
- 4 | 5 | 6 | c | d
-</screen>
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        DIVIDE (&divide;): Let <classname>R</classname> be a table
-        with the attributes A, B, C, and D and let
-        <classname>S</classname> be a table with the attributes
-        C and D.
-        Then we define the division as:
-
-<programlisting>
-R &divide; S = {t &mid; &forall; t<subscript>s</subscript> &isin; S &exist; t<subscript>r</subscript> &isin; R
-</programlisting>
-
-        such that
-t<subscript>r</subscript>(A,B)=t&and;t<subscript>r</subscript>(C,D)=t<subscript>s</subscript>}
-        where
-        t<subscript>r</subscript>(x,y)
-        denotes a
-        tuple of table <classname>R</classname> that consists only of
-        the components <literal>x</literal> and <literal>y</literal>.
-        Note that the tuple <literal>t</literal> only consists of the
-        components <classname>A</classname> and
-        <classname>B</classname> of relation <classname>R</classname>.
-       </para>
-
-       <para id="divide-example">
-        Given the following tables
-
-<screen>
-R:                    S:
- A | B | C | D         C | D
----+---+---+---       ---+---
- a | b | c | d         c | d
- a | b | e | f         e | f
- b | c | e | f
- e | d | c | d
- e | d | e | f
- a | b | d | e
-</screen>
-
-        R &divide; S
-        is derived as
-
-<screen>
- A | B
----+---
- a | b
- e | d
-</screen>
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     For a more detailed description and definition of the relational
-     algebra refer to [<xref linkend="ULL88" endterm="ULL88">] or
-     [<xref linkend="DATE04" endterm="DATE04">].
-    </para>
-
-    <example>
-     <title id="suppl-rel-alg">A Query Using Relational Algebra</title>
-     <para>
-      Recall that we formulated all those relational operators to be able to
-      retrieve data from the database. Let's return to our example from
-      the previous
-      section (<xref linkend="operations" endterm="operations">)
-      where someone wanted to know the names of all
-      suppliers that sell the part <literal>Screw</literal>.
-      This question can be answered
-      using relational algebra by the following operation:
-
-<programlisting>
-&pi;<subscript>SUPPLIER.SNAME</subscript>(&sigma;<subscript>PART.PNAME='Screw'</subscript>(SUPPLIER &prod; SELLS &prod; PART))
-</programlisting>
-     </para>
-
-     <para>
-      We call such an operation a query. If we evaluate the above query
-      against the our example tables
-      (<xref linkend="supplier-fig" endterm="supplier-fig">)
-      we will obtain the following result:
-
-<screen>
- SNAME
--------
- Smith
- Adams
-</screen>
-     </para>
-    </example>
-   </sect2>
-
-   <sect2 id="rel-calc">
-    <title>Relational Calculus</title>
-&common;
-    <para>
-     The relational calculus is based on the
-     <firstterm>first order logic</firstterm>. There are
-     two variants of the relational calculus:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        The <firstterm>Domain Relational Calculus</firstterm>
-        (<acronym>DRC</acronym>), where variables
-        stand for components (attributes) of the tuples.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The <firstterm>Tuple Relational Calculus</firstterm>
-        (<acronym>TRC</acronym>), where variables stand for tuples.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     We want to discuss the tuple relational calculus only because it is
-     the one underlying the most relational languages. For a detailed
-     discussion on <acronym>DRC</acronym> (and also
-     <acronym>TRC</acronym>) see
-     <xref linkend="DATE04" endterm="DATE04">
-     or
-     <xref linkend="ULL88" endterm="ULL88">.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Tuple Relational Calculus</title>
-&common;
-    <para>
-     The queries used in <acronym>TRC</acronym> are of the following
-     form:
-
-<programlisting>
-x(A) &mid; F(x)
-</programlisting>
-
-     where <literal>x</literal> is a tuple variable
-     <classname>A</classname> is a set of attributes and <literal>F</literal> is a
-     formula. The resulting relation consists of all tuples
-     <literal>t(A)</literal> that satisfy <literal>F(t)</literal>.
-    </para>
-
-    <para>
-     If we want to answer the question from example
-     <xref linkend="suppl-rel-alg" endterm="suppl-rel-alg">
-     using <acronym>TRC</acronym> we formulate the following query:
-
-<programlisting>
-{x(SNAME) &mid; x &isin; SUPPLIER &and;
-    &exist; y &isin; SELLS &exist; z &isin; PART (y(SNO)=x(SNO) &and;
-    z(PNO)=y(PNO) &and;
-    z(PNAME)='Screw')}
-</programlisting>
-    </para>
-
-    <para>
-     Evaluating the query against the tables from
-     <xref linkend="supplier-fig" endterm="supplier-fig">
-     again leads to the same result
-     as in
-     <xref linkend="suppl-rel-alg" endterm="suppl-rel-alg">.
-    </para>
-   </sect2>
-
-   <sect2 id="alg-vs-calc">
-    <title>Relational Algebra vs. Relational Calculus</title>
-&common;
-    <para>
-     The relational algebra and the relational calculus have the same
-     <firstterm>expressive power</firstterm>; i.e., all queries that
-     can be formulated using relational algebra can also be formulated
-     using the relational calculus and vice versa.
-     This was first proved by E. F. Codd in
-     1972. This proof is based on an algorithm (<quote>Codd's reduction
-     algorithm</quote>) by which an arbitrary expression of the relational
-     calculus can be reduced to a semantically equivalent expression of
-     relational algebra. For a more detailed discussion on that refer to
-     <xref linkend="DATE04" endterm="DATE04">
-     and
-     <xref linkend="ULL88" endterm="ULL88">.
-    </para>
-
-    <para>
-     It is sometimes said that languages based on the relational
-     calculus are <quote>higher level</quote> or <quote>more
-     declarative</quote> than languages based on relational algebra
-     because the algebra (partially) specifies the order of operations
-     while the calculus leaves it to a compiler or interpreter to
-     determine the most efficient order of evaluation.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="sql-language">
-   <title>The <acronym>SQL</acronym> Language</title>
-&common;
-   <para>
-    As is the case with most modern relational languages,
-    <acronym>SQL</acronym> is based on the tuple
-    relational calculus. As a result every query that can be formulated
-    using the tuple relational calculus (or equivalently, relational
-    algebra) can also be formulated using
-    <acronym>SQL</acronym>. There are, however,
-    capabilities beyond the scope of relational algebra or calculus. Here
-    is a list of some additional features provided by
-    <acronym>SQL</acronym> that are not
-    part of relational algebra or calculus:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Commands for insertion, deletion or modification of data.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Arithmetic capability: In <acronym>SQL</acronym> it is possible
-       to involve
-       arithmetic operations as well as comparisons, e.g.:
-
-<programlisting>
-A &lt; B + 3.
-</programlisting>
-
-       Note
-       that + or other arithmetic operators appear neither in relational
-       algebra nor in relational calculus.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Assignment and Print Commands: It is possible to print a
-       relation constructed by a query and to assign a computed relation to a
-       relation name.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Aggregate Functions: Operations such as
-       <firstterm>average</firstterm>, <firstterm>sum</firstterm>,
-       <firstterm>max</firstterm>, etc. can be applied to columns of a
-       relation to
-       obtain a single quantity.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <sect2 id="select">
-    <title id="select-title">Select</title>
-&common;
-    <para>
-     The most often used command in <acronym>SQL</acronym> is the
-     <command>SELECT</command> statement,
-     used to retrieve data. The syntax is:
-
-<!## PG>
-<!-- NO INTO -->
-<synopsis>
-SELECT [ ALL | DISTINCT [ ON ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) ] ]
-    * | <replaceable class="PARAMETER">expression</replaceable> [ [ AS ] <replaceable class="PARAMETER">output_name</replaceable> ] [, ...]
-    [ INTO [ TEMPORARY | TEMP ] [ TABLE ] <replaceable class="PARAMETER">new_table</replaceable> ]
-    [ FROM <replaceable class="PARAMETER">from_item</replaceable> [, ...] ]
-    [ WHERE <replaceable class="PARAMETER">condition</replaceable> ]
-    [ GROUP BY <replaceable class="PARAMETER">expression</replaceable> [, ...] ]
-    [ HAVING <replaceable class="PARAMETER">condition</replaceable> [, ...] ]
-    [ { UNION | INTERSECT | EXCEPT } [ ALL ] <replaceable class="PARAMETER">select</replaceable> ]
-    [ ORDER BY <replaceable class="parameter">expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [ NULLS { FIRST | LAST } ] [, ...] ]
-    [ LIMIT { <replaceable class="PARAMETER">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="PARAMETER">start</replaceable> ]
-    [ FOR { UPDATE | SHARE } [ OF <replaceable class="parameter">table_name</replaceable> [, ...] ] [ NOWAIT ] [...] ]
-</synopsis>
-<!## end>
-<!## XC>
-<synopsis>
-SELECT [ ALL | DISTINCT [ ON ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) ] ]
-    * | <replaceable class="PARAMETER">expression</replaceable> [ [ AS ] <replaceable class="PARAMETER">output_name</replaceable> ] [, ...]
-    [ FROM <replaceable class="PARAMETER">from_item</replaceable> [, ...] ]
-    [ WHERE <replaceable class="PARAMETER">condition</replaceable> ]
-    [ GROUP BY <replaceable class="PARAMETER">expression</replaceable> [, ...] ]
-    [ HAVING <replaceable class="PARAMETER">condition</replaceable> [, ...] ]
-    [ { UNION | INTERSECT | EXCEPT } [ ALL ] <replaceable class="PARAMETER">select</replaceable> ]
-    [ ORDER BY <replaceable class="parameter">expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [ NULLS { FIRST | LAST } ] [, ...] ]
-    [ LIMIT { <replaceable class="PARAMETER">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="PARAMETER">start</replaceable> ]
-    [ FOR { UPDATE | SHARE } [ OF <replaceable class="parameter">table_name</replaceable> [, ...] ] [ NOWAIT ] [...] ]
-<!## end>
-<!## XL>
-<synopsis>
-SELECT [ ALL | DISTINCT [ ON ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) ] ]
-    * | <replaceable class="PARAMETER">expression</replaceable> [ [ AS ] <replaceable class="PARAMETER">output_name</replaceable> ] [, ...]
-    [ FROM <replaceable class="PARAMETER">from_item</replaceable> [, ...] ]
-    [ WHERE <replaceable class="PARAMETER">condition</replaceable> ]
-    [ GROUP BY <replaceable class="PARAMETER">expression</replaceable> [, ...] ]
-    [ HAVING <replaceable class="PARAMETER">condition</replaceable> [, ...] ]
-    [ { UNION | INTERSECT | EXLEPT } [ ALL ] <replaceable class="PARAMETER">select</replaceable> ]
-    [ ORDER BY <replaceable class="parameter">expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [ NULLS { FIRST | LAST } ] [, ...] ]
-    [ LIMIT { <replaceable class="PARAMETER">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="PARAMETER">start</replaceable> ]
-    [ FOR { UPDATE | SHARE } [ OF <replaceable class="parameter">table_name</replaceable> [, ...] ] [ NOWAIT ] [...] ]
-<!## end>
-    </para>
-
-    <para>
-     Now we will illustrate the complex syntax of the
-     <command>SELECT</command> statement with various examples. The
-     tables used for the examples are defined in <xref
-     linkend="supplier-fig" endterm="supplier-fig">.
-    </para>
-
-    <sect3>
-     <title>Simple Selects</title>
-&common;
-     <para>
-      Here are some simple examples using a <command>SELECT</command> statement:
-
-      <example>
-       <title id="simple-query">Simple Query with Qualification</title>
-       <para>
-        To retrieve all tuples from table PART where the attribute PRICE is
-        greater than 10 we formulate the following query:
-
-<programlisting>
-SELECT * FROM PART
-    WHERE PRICE &gt; 10;
-</programlisting>
-
-        and get the table:
-
-<screen>
- PNO |  PNAME  |  PRICE
------+---------+--------
-  3  |  Bolt   |   15
-  4  |  Cam    |   25
-</screen>
-       </para>
-
-       <para>
-        Using <quote>*</quote> in the <command>SELECT</command> statement
-        will deliver all attributes from the table. If we want to retrieve
-        only the attributes PNAME and PRICE from table PART we use the
-        statement:
-
-<programlisting>
-SELECT PNAME, PRICE
-    FROM PART
-    WHERE PRICE &gt; 10;
-</programlisting>
-
-        In this case the result is:
-
-<screen>
-                      PNAME  |  PRICE
-                     --------+--------
-                      Bolt   |   15
-                      Cam    |   25
-</screen>
-
-        Note that the <acronym>SQL</acronym> <command>SELECT</command>
-        corresponds to the <quote>projection</quote> in relational algebra
-        not to the <quote>selection</quote> (see <xref linkend="rel-alg"
-        endterm="rel-alg"> for more details).
-       </para>
-
-       <para>
-        The qualifications in the WHERE clause can also be logically connected
-        using the keywords OR, AND, and NOT:
-
-<programlisting>
-SELECT PNAME, PRICE
-    FROM PART
-    WHERE PNAME = 'Bolt' AND
-         (PRICE = 0 OR PRICE &lt;= 15);
-</programlisting>
-
-        will lead to the result:
-
-<screen>
- PNAME  |  PRICE
---------+--------
- Bolt   |   15
-</screen>
-       </para>
-
-       <para>
-        Arithmetic operations can be used in the target list and in the WHERE
-        clause. For example if we want to know how much it would cost if we
-        take two pieces of a part we could use the following query:
-
-<programlisting>
-SELECT PNAME, PRICE * 2 AS DOUBLE
-    FROM PART
-    WHERE PRICE * 2 &lt; 50;
-</programlisting>
-
-        and we get:
-
-<screen>
- PNAME  |  DOUBLE
---------+---------
- Screw  |    20
- Nut    |    16
- Bolt   |    30
-</screen>
-
-        Note that the word DOUBLE after the keyword AS is the new title of the
-        second column. This technique can be used for every element of the
-        target list to assign a new title to the resulting
-        column. This new title
-        is often referred to as alias. The alias cannot be used throughout the
-        rest of the query.
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Joins</title>
-&common;
-     <para id="simple-join">
-      The following example shows how <firstterm>joins</firstterm> are
-      realized in <acronym>SQL</acronym>.
-     </para>
-
-     <para>
-      To join the three tables SUPPLIER, PART and SELLS over their common
-      attributes we formulate the following statement:
-
-<programlisting>
-SELECT S.SNAME, P.PNAME
-    FROM SUPPLIER S, PART P, SELLS SE
-    WHERE S.SNO = SE.SNO AND
-          P.PNO = SE.PNO;
-</programlisting>
-
-      and get the following table as a result:
-
-<screen>
- SNAME | PNAME
--------+-------
- Smith | Screw
- Smith | Nut
- Jones | Cam
- Adams | Screw
- Adams | Bolt
- Blake | Nut
- Blake | Bolt
- Blake | Cam
-</screen>
-     </para>
-
-     <para>
-      In the FROM clause we introduced an alias name for every relation
-      because there are common named attributes (SNO and PNO) among the
-      relations. Now we can distinguish between the common named attributes
-      by simply prefixing the attribute name with the alias name followed by
-      a dot. The join is calculated in the same way as shown in
-      <xref linkend="join-example" endterm="join-example">.
-      First the Cartesian product
-
-      SUPPLIER &times; PART &times; SELLS
-
-      is derived. Now only those tuples satisfying the
-      conditions given in the WHERE clause are selected (i.e., the common
-      named attributes have to be equal). Finally we project out all
-      columns but S.SNAME and P.PNAME.
-     </para>
-
-     <para>
-     Another way to perform joins is to use the SQL JOIN syntax as follows:
-<programlisting>
-SELECT sname, pname from supplier
-    JOIN sells USING (sno)
-    JOIN part USING (pno);
-</programlisting>
-    giving again:
-<screen>
- sname | pname
--------+-------
- Smith | Screw
- Adams | Screw
- Smith | Nut
- Blake | Nut
- Adams | Bolt
- Blake | Bolt
- Jones | Cam
- Blake | Cam
-(8 rows)
-</screen>
-     </para>
-
-     <para>
-     A joined table, created using JOIN syntax, is a table reference list
-     item that occurs in a FROM clause and before any WHERE, GROUP BY,
-     or HAVING clause.  Other table references, including table names or
-     other JOIN clauses, can be included in the FROM clause if separated
-     by commas.  JOINed tables are logically like any other
-     table listed in the FROM clause.
-     </para>
-
-     <para>
-      SQL JOINs come in two main types, CROSS JOINs (unqualified joins)
-      and <firstterm>qualified JOINs</>.  Qualified joins can be further
-      subdivided based on the way in which the <firstterm>join condition</>
-      is specified (ON, USING, or NATURAL) and the way in which it is
-      applied (INNER or OUTER join).
-     </para>
-
-    <variablelist>
-        <title>Join Types</title>
-        <varlistentry>
-            <term>CROSS JOIN</term>
-            <listitem>
-            <cmdsynopsis>
-                <arg choice="req"> <replaceable class="parameter">T1</replaceable> </arg>
-                <command> CROSS JOIN </command>
-                <arg choice="req"> <replaceable class="parameter">T2</replaceable> </arg>
-            </cmdsynopsis>
-
-            <para>
-            A cross join takes two tables T1 and T2 having N and M rows
-            respectively, and returns a joined table containing all
-            N*M possible joined rows. For each row R1 of T1, each row
-            R2 of T2 is joined with R1 to yield a joined table row JR
-            consisting of all fields in R1 and R2. A CROSS JOIN is
-            equivalent to an INNER JOIN ON TRUE.
-            </para>
-            </listitem>
-        </varlistentry>
-
-        <varlistentry>
-            <term>Qualified JOINs</term>
-            <listitem>
-
-            <cmdsynopsis>
-            <arg choice="req"> <replaceable class="parameter">T1</replaceable> </arg>
-            <arg choice="opt"> NATURAL </arg>
-            <group choice="opt">
-                <arg choice="opt"> INNER </arg>
-                <arg>
-                <group choice="req">
-                    <arg choice="plain"> LEFT </arg>
-                    <arg choice="plain"> RIGHT </arg>
-                    <arg choice="plain"> FULL </arg>
-                </group>
-                <arg choice="opt"> OUTER </arg>
-                    </arg>
-                </group>
-            <command> JOIN </command>
-            <arg choice="req"> <replaceable class="parameter">T2</replaceable> </arg>
-            <group choice="req">
-                <arg> ON <replaceable>search condition</replaceable></arg>
-                <arg> USING ( <replaceable>join column list</replaceable> ) </arg>
-            </group>
-            </cmdsynopsis>
-
-            <para>
-            A qualified JOIN must specify its join condition
-            by providing one (and only one) of NATURAL, ON, or
-            USING.  The ON clause
-            takes a <replaceable>search condition</replaceable>,
-            which is the same as in a WHERE clause.  The USING
-            clause takes a comma-separated list of column names,
-            which the joined tables must have in common, and joins
-            the tables on equality of those columns.  NATURAL is
-            shorthand for a USING clause that lists all the common
-            column names of the two tables.  A side-effect of both
-            USING and NATURAL is that only one copy of each joined
-            column is emitted into the result table (compare the
-            relational-algebra definition of JOIN, shown earlier).
-            </para>
-
-            <!-- begin join semantics -->
-            <variablelist>
-            <varlistentry>
-                <term>
-                    <cmdsynopsis>
-                        <arg> INNER </arg>
-                        <command> JOIN </command>
-                    </cmdsynopsis>
-                </term>
-                <listitem>
-                <para>
-                For each row R1 of T1, the joined table has a row for each row
-                in T2 that satisfies the join condition with R1.
-                </para>
-                <tip>
-                <para>
-                    The words INNER and OUTER are optional for all JOINs.
-                    INNER is the default.  LEFT, RIGHT, and FULL imply an
-                    OUTER JOIN.
-                    </para>
-                </tip>
-                </listitem>
-            </varlistentry>
-            <varlistentry>
-                <term>
-                    <cmdsynopsis>
-                        <arg choice="plain"> LEFT </arg>
-                        <arg> OUTER </arg>
-                        <command> JOIN </command>
-                    </cmdsynopsis>
-                </term>
-                <listitem>
-                <para>
-                First, an INNER JOIN is performed.
-                Then, for each row in T1 that does not satisfy the join
-                condition with any row in T2, an additional joined row is
-                returned with null fields in the columns from T2.
-                </para>
-                <tip>
-                    <para>
-                    The joined table unconditionally has a row for each row in T1.
-                    </para>
-                </tip>
-                </listitem>
-            </varlistentry>
-            <varlistentry>
-                <term>
-                    <cmdsynopsis>
-                        <arg choice="plain"> RIGHT </arg>
-                        <arg> OUTER </arg>
-                        <command> JOIN </command>
-                    </cmdsynopsis>
-                </term>
-                <listitem>
-                <para>
-                First, an INNER JOIN is performed.
-                Then, for each row in T2 that does not satisfy the join
-                condition with any row in T1, an additional joined row is
-                returned with null fields in the columns from T1.
-                </para>
-                <tip>
-                    <para>
-                    The joined table unconditionally has a row for each row in T2.
-                    </para>
-                </tip>
-                </listitem>
-            </varlistentry>
-            <varlistentry>
-                <term>
-                    <cmdsynopsis>
-                        <arg choice="plain"> FULL </arg>
-                        <arg> OUTER </arg>
-                        <command> JOIN </command>
-                    </cmdsynopsis>
-                </term>
-                <listitem>
-                <para>
-                First, an INNER JOIN is performed.
-                Then, for each row in T1 that does not satisfy the join
-                condition with any row in T2, an additional joined row is
-                returned with null fields in the columns from T2.
-                Also, for each row in T2 that does not satisfy the join
-                condition with any row in T1, an additional joined row is
-                returned with null fields in the columns from T1.
-                </para>
-                <tip>
-                    <para>
-                    The joined table unconditionally has a row for every row of T1
-                    and a row for every row of T2.
-                    </para>
-                </tip>
-                </listitem>
-            </varlistentry>
-            </variablelist>
-            <!-- end join semantics -->
-
-            </listitem>
-        </varlistentry>
-     </variablelist>
-
-     <para>
-     JOINs of all types can be chained together or nested where either or both of
-     <replaceable class="parameter">T1</replaceable> and
-     <replaceable class="parameter">T2</replaceable> can be JOINed tables.
-     Parenthesis can be used around JOIN clauses to control the order
-     of JOINs which are otherwise processed left to right.
-     </para>
-
-    </sect3>
-
-    <sect3>
-     <title id="aggregates-tutorial">Aggregate Functions</title>
-&common;
-     <para>
-      <acronym>SQL</acronym> provides aggregate functions such as AVG,
-      COUNT, SUM, MIN, and MAX.  The argument(s) of an aggregate function
-      are evaluated at each row that satisfies the WHERE
-      clause, and the aggregate function is calculated over this set
-      of input values.  Normally, an aggregate delivers a single
-      result for a whole <command>SELECT</command> statement.  But if
-      grouping is specified in the query, then a separate calculation
-      is done over the rows of each group, and an aggregate result is
-      delivered per group (see next section).
-
-      <example>
-       <title id="aggregates-example">Aggregates</title>
-
-       <para>
-        If we want to know the average cost of all parts in table PART we use
-        the following query:
-
-<programlisting>
-SELECT AVG(PRICE) AS AVG_PRICE
-    FROM PART;
-</programlisting>
-       </para>
-
-       <para>
-        The result is:
-
-<screen>
- AVG_PRICE
------------
-   14.5
-</screen>
-       </para>
-
-       <para>
-        If we want to know how many parts are defined in table PART we use
-        the statement:
-
-<programlisting>
-SELECT COUNT(PNO)
-    FROM PART;
-</programlisting>
-
-        and get:
-
-<screen>
- COUNT
--------
-   4
-</screen>
-
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Aggregation by Groups</title>
-&common;
-     <para>
-      <acronym>SQL</acronym> allows one to partition the tuples of a table
-      into groups. Then the
-      aggregate functions described above can be applied to the groups &mdash;
-      i.e., the value of the aggregate function is no longer calculated over
-      all the values of the specified column but over all values of a
-      group. Thus the aggregate function is evaluated separately for every
-      group.
-     </para>
-
-     <para>
-      The partitioning of the tuples into groups is done by using the
-      keywords <command>GROUP BY</command> followed by a list of
-      attributes that define the
-      groups. If we have
-      <command>GROUP BY A<subscript>1</subscript>, &tdot;, A<subscript>k</subscript></command>
-      we partition
-      the relation into groups, such that two tuples are in the same group
-      if and only if they agree on all the attributes
-      A<subscript>1</subscript>, &tdot;, A<subscript>k</subscript>.
-
-      <example>
-       <title id="aggregates-groupby">Aggregates</title>
-       <para>
-        If we want to know how many parts are sold by every supplier we
-        formulate the query:
-
-<programlisting>
-SELECT S.SNO, S.SNAME, COUNT(SE.PNO)
-    FROM SUPPLIER S, SELLS SE
-    WHERE S.SNO = SE.SNO
-    GROUP BY S.SNO, S.SNAME;
-</programlisting>
-
-        and get:
-
-<screen>
- SNO | SNAME | COUNT
------+-------+-------
-  1  | Smith |   2
-  2  | Jones |   1
-  3  | Adams |   2
-  4  | Blake |   3
-</screen>
-       </para>
-
-       <para>
-        Now let's have a look of what is happening here.
-        First the join of the
-        tables SUPPLIER and SELLS is derived:
-
-<screen>
- S.SNO | S.SNAME | SE.PNO
--------+---------+--------
-   1   |  Smith  |   1
-   1   |  Smith  |   2
-   2   |  Jones  |   4
-   3   |  Adams  |   1
-   3   |  Adams  |   3
-   4   |  Blake  |   2
-   4   |  Blake  |   3
-   4   |  Blake  |   4
-</screen>
-       </para>
-
-       <para>
-        Next we partition the tuples into groups by putting all tuples
-        together that agree on both attributes S.SNO and S.SNAME:
-
-<screen>
- S.SNO | S.SNAME | SE.PNO
--------+---------+--------
-   1   |  Smith  |   1
-                 |   2
---------------------------
-   2   |  Jones  |   4
---------------------------
-   3   |  Adams  |   1
-                 |   3
---------------------------
-   4   |  Blake  |   2
-                 |   3
-                 |   4
-</screen>
-       </para>
-
-       <para>
-        In our example we got four groups and now we can apply the aggregate
-        function COUNT to every group leading to the final result of the query
-        given above.
-       </para>
-      </example>
-     </para>
-
-     <para>
-      Note that for a query using GROUP BY and aggregate
-      functions to make sense, the target list can only refer directly to
-      the attributes being grouped by.  Other attributes can only be used
-      inside the arguments of aggregate functions.  Otherwise there would
-      not be a unique value to associate with the other attributes.
-     </para>
-
-     <para>
-      Also observe that it makes no sense to ask for an aggregate of
-      an aggregate, e.g., AVG(MAX(sno)), because a
-      <command>SELECT</command> only does one pass of grouping and
-      aggregation.  You can get a result of this kind by using a
-      temporary table or a sub-SELECT in the FROM clause to do the
-      first level of aggregation.
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Having</title>
-&common;
-     <para>
-      The HAVING clause works much like the WHERE clause and is used to
-      consider only those groups satisfying the qualification given in the
-      HAVING clause.  Essentially, WHERE filters out unwanted input rows
-      before grouping and aggregation are done, whereas HAVING filters out
-      unwanted group rows post-GROUP.  Therefore, WHERE cannot refer to the
-      results of aggregate functions.  On the other hand, there's no point
-      in writing a HAVING condition that doesn't involve an aggregate
-      function!  If your condition doesn't involve aggregates, you might
-      as well write it in WHERE, and thereby avoid the computation of
-      aggregates for groups that you're just going to throw away anyway.
-
-      <example>
-       <title id="having-example">Having</title>
-
-       <para>
-        If we want only those suppliers selling more than one part we use the
-        query:
-
-<programlisting>
-SELECT S.SNO, S.SNAME, COUNT(SE.PNO)
-    FROM SUPPLIER S, SELLS SE
-    WHERE S.SNO = SE.SNO
-    GROUP BY S.SNO, S.SNAME
-    HAVING COUNT(SE.PNO) &gt; 1;
-</programlisting>
-
-        and get:
-
-<screen>
- SNO | SNAME | COUNT
------+-------+-------
-  1  | Smith |   2
-  3  | Adams |   2
-  4  | Blake |   3
-</screen>
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Subqueries</title>
-
-&xconly;
-<!## XC>
-     <para>
-      Subqueries in <productname>Postgres-XC</> have restrictions.
-      You may be warned if some of them cannot be handled.
-     </para>
-<!## end>
-<!## XL>
-     <para>
-      Subqueries in <productname>Postgres-XL</> have restrictions.
-      You may be warned if some of them cannot be handled.
-     </para>
-<!## end>
-&common;
-     <para>
-      In the WHERE and HAVING clauses the use of subqueries (subselects) is
-      allowed in every place where a value is expected. In this case the
-      value must be derived by evaluating the subquery first. The usage of
-      subqueries extends the expressive power of
-      <acronym>SQL</acronym>.
-
-      <example>
-       <title id="subselect-example">Subselect</title>
-
-       <para>
-        If we want to know all parts having a greater price than the part
-        named 'Screw' we use the query:
-
-<programlisting>
-SELECT *
-    FROM PART
-    WHERE PRICE &gt; (SELECT PRICE FROM PART
-                   WHERE PNAME='Screw');
-</programlisting>
-       </para>
-
-       <para>
-        The result is:
-
-<screen>
- PNO |  PNAME  |  PRICE
------+---------+--------
-  3  |  Bolt   |   15
-  4  |  Cam    |   25
-</screen>
-       </para>
-
-       <para>
-        When we look at the above query we can see the keyword
-        <command>SELECT</command> two times. The first one at the
-        beginning of the query - we will refer to it as outer
-        <command>SELECT</command> - and the one in the WHERE clause which
-        begins a nested query - we will refer to it as inner
-        <command>SELECT</command>. For every tuple of the outer
-        <command>SELECT</command> the inner <command>SELECT</command> has
-        to be evaluated. After every evaluation we know the price of the
-        tuple named 'Screw' and we can check if the price of the actual
-        tuple is greater.  (Actually, in this example the inner query need
-        only be evaluated once, since it does not depend on the state of
-        the outer query.)
-       </para>
-
-       <para>
-        If we want to know all suppliers that do not sell any part
-        (e.g., to be able to remove these suppliers from the database) we use:
-
-<programlisting>
-SELECT *
-    FROM SUPPLIER S
-    WHERE NOT EXISTS
-        (SELECT * FROM SELLS SE
-         WHERE SE.SNO = S.SNO);
-</programlisting>
-       </para>
-
-       <para>
-        In our example the result will be empty because every supplier
-        sells at least one part. Note that we use S.SNO from the outer
-        <command>SELECT</command> within the WHERE clause of the inner
-        <command>SELECT</command>. Here the subquery must be evaluated
-        afresh for each tuple from the outer query, i.e., the value for
-        S.SNO is always taken from the current tuple of the outer
-        <command>SELECT</command>.
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Subqueries in FROM</title>
-&common;
-     <para>
-      A somewhat different way of using subqueries is to put them in the
-      FROM clause.  This is a useful feature because a subquery of this
-      kind can output multiple columns and rows, whereas a subquery used
-      in an expression must deliver just a single result.  It also lets
-      us get more than one round of grouping/aggregation without resorting
-      to a temporary table.
-
-      <example>
-       <title id="subselect-in-from-example">Subselect in FROM</title>
-
-       <para>
-        If we want to know the highest average part price among all our
-        suppliers, we cannot write MAX(AVG(PRICE)), but we can write:
-
-<programlisting>
-SELECT MAX(subtable.avgprice)
-    FROM (SELECT AVG(P.PRICE) AS avgprice
-          FROM SUPPLIER S, PART P, SELLS SE
-          WHERE S.SNO = SE.SNO AND
-                P.PNO = SE.PNO
-          GROUP BY S.SNO) subtable;
-</programlisting>
-
-        The subquery returns one row per supplier (because of its GROUP BY)
-        and then we aggregate over those rows in the outer query.
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Union, Intersect, Except</title>
-&common;
-     <para>
-      These operations calculate the union, intersection and set theoretic
-      difference of the tuples derived by two subqueries.
-
-      <example>
-       <title id="union-example">Union, Intersect, Except</title>
-
-       <para>
-        The following query is an example for UNION:
-
-<programlisting>
-SELECT S.SNO, S.SNAME, S.CITY
-    FROM SUPPLIER S
-    WHERE S.SNAME = 'Jones'
-UNION
-    SELECT S.SNO, S.SNAME, S.CITY
-    FROM SUPPLIER S
-    WHERE S.SNAME = 'Adams';
-</programlisting>
-
-gives the result:
-
-<screen>
- SNO | SNAME |  CITY
------+-------+--------
-  2  | Jones | Paris
-  3  | Adams | Vienna
-</screen>
-       </para>
-
-       <para>
-        Here is an example for INTERSECT:
-
-<programlisting>
-SELECT S.SNO, S.SNAME, S.CITY
-    FROM SUPPLIER S
-    WHERE S.SNO &gt; 1
-INTERSECT
-    SELECT S.SNO, S.SNAME, S.CITY
-    FROM SUPPLIER S
-    WHERE S.SNO &lt; 3;
-</programlisting>
-
-        gives the result:
-
-<screen>
- SNO | SNAME |  CITY
------+-------+--------
-  2  | Jones | Paris
-</screen>
-
-        The only tuple returned by both parts of the query is the one having SNO=2.
-       </para>
-
-       <para>
-        Finally an example for EXCEPT:
-
-<programlisting>
-SELECT S.SNO, S.SNAME, S.CITY
-    FROM SUPPLIER S
-    WHERE S.SNO &gt; 1
-EXCEPT
-    SELECT S.SNO, S.SNAME, S.CITY
-    FROM SUPPLIER S
-    WHERE S.SNO &gt; 3;
-</programlisting>
-
-        gives the result:
-
-<screen>
- SNO | SNAME |  CITY
------+-------+--------
-  2  | Jones | Paris
-  3  | Adams | Vienna
-</screen>
-       </para>
-      </example>
-     </para>
-    </sect3>
-   </sect2>
-
-   <sect2 id="datadef">
-    <title>Data Definition</title>
-&common;
-    <para>
-     There is a set of commands used for data definition included in the
-     <acronym>SQL</acronym> language.
-    </para>
-
-    <sect3 id="create">
-     <title id="create-title">Create Table</title>
-&common;
-     <para>
-      The most fundamental command for data definition is the
-      one that creates a new relation (a new table). The syntax of the
-      <command>CREATE TABLE</command> command is:
-
-<synopsis>
-CREATE TABLE <replaceable class="parameter">table_name</replaceable>
-    (<replaceable class="parameter">name_of_attr_1</replaceable> <replaceable class="parameter">type_of_attr_1</replaceable>
-     [, <replaceable class="parameter">name_of_attr_2</replaceable> <replaceable class="parameter">type_of_attr_2</replaceable>
-     [, ...]]);
-</synopsis>
-
-      <example>
-       <title id="table-create">Table Creation</title>
-
-       <para>
-        To create the tables defined in
-        <xref linkend="supplier-fig" endterm="supplier-fig"> the
-        following <acronym>SQL</acronym> statements are used:
-
-<programlisting>
-CREATE TABLE SUPPLIER
-    (SNO   INTEGER,
-     SNAME VARCHAR(20),
-     CITY  VARCHAR(20));
-</programlisting>
-
-<programlisting>
-CREATE TABLE PART
-    (PNO   INTEGER,
-     PNAME VARCHAR(20),
-     PRICE DECIMAL(4 , 2));
-</programlisting>
-
-<programlisting>
-CREATE TABLE SELLS
-    (SNO INTEGER,
-     PNO INTEGER);
-</programlisting>
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Data Types in <acronym>SQL</acronym></title>
-&common;
-     <para>
-      The following is a list of some data types that are supported by
-      <acronym>SQL</acronym>:
-
-      <itemizedlist>
-       <listitem>
-        <para>
-         INTEGER: signed fullword binary integer (31 bits precision).
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         SMALLINT: signed halfword binary integer (15 bits precision).
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         DECIMAL (<replaceable class="parameter">p</replaceable>[,<replaceable class="parameter">q</replaceable>]):
-         signed packed decimal number of up to
-         <replaceable class="parameter">p</replaceable>
-         digits, with
-         <replaceable class="parameter">q</replaceable>
-         digits to the right of the decimal point.
-         If <replaceable class="parameter">q</replaceable>
-         is omitted it is assumed to be 0.
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         FLOAT: signed doubleword floating point number.
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         VARCHAR(<replaceable class="parameter">n</replaceable>):
-         varying length character string of maximum length
-         <replaceable class="parameter">n</replaceable>.
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         CHAR(<replaceable class="parameter">n</replaceable>):
-         fixed length character string of length
-         <replaceable class="parameter">n</replaceable>.
-        </para>
-       </listitem>
-
-      </itemizedlist>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Create Index</title>
-&common;
-     <para>
-      Indexes are used to speed up access to a relation. If a relation <classname>R</classname>
-      has an index on attribute <classname>A</classname> then we can
-      retrieve all tuples <replaceable>t</replaceable>
-      having
-      <replaceable>t</replaceable>(<classname>A</classname>) = <replaceable>a</replaceable>
-      in time roughly proportional to the number of such
-      tuples <replaceable>t</replaceable>
-      rather than in time proportional to the size of <classname>R</classname>.
-     </para>
-
-     <para>
-      To create an index in <acronym>SQL</acronym>
-      the <command>CREATE INDEX</command> command is used. The syntax is:
-
-<programlisting>
-CREATE INDEX <replaceable class="parameter">index_name</replaceable>
-    ON <replaceable class="parameter">table_name</replaceable> ( <replaceable class="parameter">name_of_attribute</replaceable> );
-</programlisting>
-     </para>
-
-     <para>
-      <example>
-       <title id="index-create">Create Index</title>
-
-       <para>
-        To create an index named I on attribute SNAME of relation SUPPLIER
-        we use the following statement:
-
-<programlisting>
-CREATE INDEX I ON SUPPLIER (SNAME);
-</programlisting>
-     </para>
-
-       <para>
-        The created index is maintained automatically, i.e., whenever a new
-        tuple is inserted into the relation SUPPLIER the index I is
-        adapted. Note that the only changes a user can perceive when an
-        index is present are increased speed for <command>SELECT</command>
-        and decreases in speed of updates.
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Create View</title>
-&common;
-     <para>
-      A view can be regarded as a <firstterm>virtual table</firstterm>,
-      i.e., a table that
-      does not <emphasis>physically</emphasis> exist in the database
-      but looks to the user
-      as if it does. By contrast, when we talk of a
-      <firstterm>base table</firstterm> there is
-      really a physically stored counterpart of each row of the table
-      somewhere in the physical storage.
-     </para>
-
-     <para>
-      Views do not have their own, physically separate, distinguishable
-      stored data. Instead, the system stores the definition of the
-      view (i.e., the rules about how to access physically stored base
-      tables in order to materialize the view) somewhere in the system
-      catalogs (see
-      <xref linkend="tutorial-catalogs-title" endterm="tutorial-catalogs-title">). For a
-      discussion on different techniques to implement views refer to
-<!--
-      section
-      <xref linkend="view-impl" endterm="view-impl">.
--->
-      <citetitle>SIM98</citetitle>.
-     </para>
-
-     <para>
-      In <acronym>SQL</acronym> the <command>CREATE VIEW</command>
-      command is used to define a view. The syntax
-      is:
-
-<programlisting>
-CREATE VIEW <replaceable class="parameter">view_name</replaceable>
-    AS <replaceable class="parameter">select_stmt</replaceable>
-</programlisting>
-
-      where <replaceable class="parameter">select_stmt</replaceable>
-      is a valid select statement as defined
-      in <xref linkend="select-title" endterm="select-title">.
-      Note that <replaceable class="parameter">select_stmt</replaceable> is
-      not executed when the view is created. It is just stored in the
-      <firstterm>system catalogs</firstterm>
-      and is executed whenever a query against the view is made.
-     </para>
-
-     <para>
-      Let the following view definition be given (we use
-      the tables from
-      <xref linkend="supplier-fig" endterm="supplier-fig"> again):
-
-<programlisting>
-CREATE VIEW London_Suppliers
-    AS SELECT S.SNAME, P.PNAME
-        FROM SUPPLIER S, PART P, SELLS SE
-        WHERE S.SNO = SE.SNO AND
-              P.PNO = SE.PNO AND
-              S.CITY = 'London';
-</programlisting>
-     </para>
-
-     <para>
-      Now we can use this <firstterm>virtual relation</firstterm>
-      <classname>London_Suppliers</classname> as
-      if it were another base table:
-
-<programlisting>
-SELECT * FROM London_Suppliers
-    WHERE PNAME = 'Screw';
-</programlisting>
-
-      which will return the following table:
-
-<screen>
- SNAME | PNAME
--------+-------
- Smith | Screw                 
-</screen>
-     </para>
-
-     <para>
-      To calculate this result the database system has to do a
-      <emphasis>hidden</emphasis>
-      access to the base tables SUPPLIER, SELLS and PART first. It
-      does so by executing the query given in the view definition against
-      those base tables. After that the additional qualifications
-      (given in the
-      query against the view) can be applied to obtain the resulting
-      table.
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Drop Table, Drop Index, Drop View</title>
-&common;
-     <para>
-      To destroy a table (including all tuples stored in that table) the
-      <command>DROP TABLE</command> command is used:
-
-<programlisting>
-DROP TABLE <replaceable class="parameter">table_name</replaceable>;
-</programlisting>
-      </para>
-
-     <para>
-      To destroy the SUPPLIER table use the following statement:
-
-<programlisting>
-DROP TABLE SUPPLIER;
-</programlisting>
-     </para>
-
-     <para>
-      The <command>DROP INDEX</command> command is used to destroy an index:
-
-<programlisting>
-DROP INDEX <replaceable class="parameter">index_name</replaceable>;
-</programlisting>
-     </para>
-
-     <para>
-      Finally to destroy a given view use the command <command>DROP
-      VIEW</command>:
-
-<programlisting>
-DROP VIEW <replaceable class="parameter">view_name</replaceable>;
-</programlisting>
-     </para>
-    </sect3>
-   </sect2>
-
-   <sect2>
-    <title>Data Manipulation</title>
-&common;
-    <sect3>
-     <title>Insert Into</title>
-&common;
-     <para>
-      Once a table is created (see
-      <xref linkend="create-title" endterm="create-title">), it can be filled
-      with tuples using the command <command>INSERT INTO</command>.
-      The syntax is:
-
-<programlisting>
-INSERT INTO <replaceable class="parameter">table_name</replaceable> (<replaceable class="parameter">name_of_attr_1</replaceable>
-    [, <replaceable class="parameter">name_of_attr_2</replaceable> [, ...]])
-    VALUES (<replaceable class="parameter">val_attr_1</replaceable> [, <replaceable class="parameter">val_attr_2</replaceable> [, ...]]);
-</programlisting>
-     </para>
-
-     <para>
-      To insert the first tuple into the relation SUPPLIER (from
-      <xref linkend="supplier-fig" endterm="supplier-fig">) we use the
-      following statement:
-
-<programlisting>
-INSERT INTO SUPPLIER (SNO, SNAME, CITY)
-    VALUES (1, 'Smith', 'London');
-</programlisting>
-     </para>
-
-     <para>
-      To insert the first tuple into the relation SELLS we use:
-
-<programlisting>
-INSERT INTO SELLS (SNO, PNO)
-    VALUES (1, 1);
-</programlisting>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Update</title>
-&common;
-     <para>
-      To change one or more attribute values of tuples in a relation the
-      <command>UPDATE</command> command is used. The syntax is:
-
-<programlisting>
-UPDATE <replaceable class="parameter">table_name</replaceable>
-    SET <replaceable class="parameter">name_of_attr_1</replaceable> = <replaceable class="parameter">value_1</replaceable>
-        [, ... [, <replaceable class="parameter">name_of_attr_k</replaceable> = <replaceable class="parameter">value_k</replaceable>]]
-    WHERE <replaceable class="parameter">condition</replaceable>;
-</programlisting>
-     </para>
-
-     <para>
-      To change the value of attribute PRICE of the part 'Screw' in the
-      relation PART we use:
-
-<programlisting>
-UPDATE PART
-    SET PRICE = 15
-    WHERE PNAME = 'Screw';
-</programlisting>
-     </para>
-
-     <para>
-      The new value of attribute PRICE of the tuple whose name is 'Screw' is
-      now 15.
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Delete</title>
-&common;
-     <para>
-      To delete a tuple from a particular table use the command DELETE
-      FROM. The syntax is:
-
-<programlisting>
-DELETE FROM <replaceable class="parameter">table_name</replaceable>
-    WHERE <replaceable class="parameter">condition</replaceable>;
-</programlisting>
-     </para>
-
-     <para>
-      To delete the supplier called 'Smith' of the table SUPPLIER the
-      following statement is used:
-
-<programlisting>
-DELETE FROM SUPPLIER
-    WHERE SNAME = 'Smith';
-</programlisting>
-     </para>
-    </sect3>
-   </sect2>
-
-   <sect2 id="tutorial-catalogs">
-    <title id="tutorial-catalogs-title">System Catalogs</title>
-&common;
-    <para>
-     In every <acronym>SQL</acronym> database system
-     <firstterm>system catalogs</firstterm> are used to keep
-     track of which tables, views indexes etc. are defined in the
-     database. These system catalogs can be queried as if they were normal
-     relations. For example there is one catalog used for the definition of
-     views. This catalog stores the query from the view definition. Whenever
-     a query against a view is made, the system first gets the
-     <firstterm>view definition query</firstterm> out of the catalog
-     and materializes the view
-     before proceeding with the user query (see
-<!--
-      section
-      <xref linkend="view-impl" endterm="view-impl">.
-    <citetitle>SIM98</citetitle>
--->
-     <xref linkend="SIM98" endterm="SIM98">
-     for a more detailed
-     description). For more information about system catalogs refer to
-     <xref linkend="DATE04" endterm="DATE04">.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Embedded <acronym>SQL</acronym></title>
-&common;
-    <para>
-     In this section we will sketch how <acronym>SQL</acronym> can be
-     embedded into a host language (e.g., <literal>C</literal>).
-     There are two main reasons why we want to use <acronym>SQL</acronym>
-     from a host language:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        There are queries that cannot be formulated using pure <acronym>SQL</acronym>
-        (i.e., recursive queries). To be able to perform such queries we need a
-        host language with a greater expressive power than
-        <acronym>SQL</acronym>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        We simply want to access a database from some application that
-        is written in the host language (e.g., a ticket reservation system
-        with a graphical user interface is written in C and the information
-        about which tickets are still left is stored in a database that can be
-        accessed using embedded <acronym>SQL</acronym>).
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     A program using embedded <acronym>SQL</acronym>
-     in a host language consists of statements
-     of the host language and of
-     <firstterm>embedded <acronym>SQL</acronym></firstterm>
-     (<acronym>ESQL</acronym>) statements. Every <acronym>ESQL</acronym>
-     statement begins with the keywords <command>EXEC SQL</command>.
-     The <acronym>ESQL</acronym> statements are
-     transformed to statements of the host language
-     by a <firstterm>precompiler</firstterm>
-     (which usually inserts
-     calls to library routines that perform the various <acronym>SQL</acronym>
-     commands).
-    </para>
-
-    <para>
-     When we look at the examples throughout
-     <xref linkend="select-title" endterm="select-title"> we
-     realize that the result of the queries is very often a set of
-     tuples. Most host languages are not designed to operate on sets so we
-     need a mechanism to access every single tuple of the set of tuples
-     returned by a SELECT statement. This mechanism can be provided by
-     declaring a <firstterm>cursor</firstterm>.
-     After that we can use the <command>FETCH</command> command to
-     retrieve a tuple and set the cursor to the next tuple.
-    </para>
-
-    <para>
-     For a detailed discussion on embedded <acronym>SQL</acronym>
-     refer to
-     <xref linkend="DATE97" endterm="DATE97">,
-     <xref linkend="DATE04" endterm="DATE04">,
-     or
-     <xref linkend="ULL88" endterm="ULL88">.
-    </para>
-   </sect2>
-  </sect1>
- </chapter>
diff --git a/doc-xc/src/sgml/sslinfo.sgmlin b/doc-xc/src/sgml/sslinfo.sgmlin
deleted file mode 100644
index 79845fca43..0000000000
--- a/doc-xc/src/sgml/sslinfo.sgmlin
+++ /dev/null
@@ -1,213 +0,0 @@
-<!-- doc/src/sgml/sslinfo.sgml -->
-
-<sect1 id="sslinfo" xreflabel="sslinfo">
- <title>sslinfo</title>
-
- <indexterm zone="sslinfo">
-  <primary>sslinfo</primary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  The <filename>sslinfo</> module provides information about the SSL
-  certificate that the current client provided when connecting to
-  <productname>PostgreSQL</>.  The module is useless (most functions
-  will return NULL) if the current connection does not use SSL.
- </para>
-
- <para>
-  This extension won't build at all unless the installation was
-  configured with <literal>--with-openssl</>.
- </para>
-
- <sect2>
-  <title>Functions Provided</title>
-&pgnotice;
-  <variablelist>
-   <varlistentry>
-    <term><function>
-ssl_is_used() returns boolean
-    </function></term>
-    <listitem>
-    <para>
-     Returns TRUE if current connection to server uses SSL, and FALSE
-     otherwise.
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><function>
-ssl_version() returns text
-    </function></term>
-    <listitem>
-    <para>
-     Returns the name of the protocol used for the SSL connection (e.g. SSLv2,
-     SSLv3, or TLSv1).
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><function>
-ssl_cipher() returns text
-    </function></term>
-    <listitem>
-    <para>
-     Returns the name of the cipher used for the SSL connection
-     (e.g. DHE-RSA-AES256-SHA).
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><function>
-ssl_client_cert_present() returns boolean
-    </function></term>
-    <listitem>
-    <para>
-     Returns TRUE if current client has presented a valid SSL client
-     certificate to the server, and FALSE otherwise.  (The server
-     might or might not be configured to require a client certificate.)
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><function>
-ssl_client_serial() returns numeric
-    </function></term>
-    <listitem>
-    <para>
-     Returns serial number of current client certificate.  The combination of
-     certificate serial number and certificate issuer is guaranteed to
-     uniquely identify a certificate (but not its owner &mdash; the owner
-     ought to regularly change his keys, and get new certificates from the
-     issuer).
-    </para>
-
-    <para>
-     So, if you run your own CA and allow only certificates from this CA to
-     be accepted by the server, the serial number is the most reliable (albeit
-     not very mnemonic) means to identify a user.
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><function>
-ssl_client_dn() returns text
-    </function></term>
-    <listitem>
-    <para>
-     Returns the full subject of the current client certificate, converting
-     character data into the current database encoding.  It is assumed that
-     if you use non-ASCII characters in the certificate names, your
-     database is able to represent these characters, too.  If your database
-     uses the SQL_ASCII encoding, non-ASCII characters in the name will be
-     represented as UTF-8 sequences.
-    </para>
-
-    <para>
-     The result looks like <literal>/CN=Somebody /C=Some country/O=Some organization</>.
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><function>
-ssl_issuer_dn() returns text
-    </function></term>
-    <listitem>
-    <para>
-     Returns the full issuer name of the current client certificate, converting
-     character data into the current database encoding.  Encoding conversions
-     are handled the same as for <function>ssl_client_dn</>.
-    </para>
-    <para>
-     The combination of the return value of this function with the
-     certificate serial number uniquely identifies the certificate.
-    </para>
-    <para>
-     This function is really useful only if you have more than one trusted CA
-     certificate in your server's <filename>root.crt</> file, or if this CA
-     has issued some intermediate certificate authority certificates.
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><function>
-ssl_client_dn_field(fieldname text) returns text
-    </function></term>
-    <listitem>
-    <para>
-     This function returns the value of the specified field in the
-     certificate subject, or NULL if the field is not present.
-     Field names are string constants that are
-     converted into ASN1 object identifiers using the OpenSSL object
-     database.  The following values are acceptable:
-    </para>
-<literallayout class="monospaced">
-commonName (alias CN)
-surname (alias SN)
-name
-givenName (alias GN)
-countryName (alias C)
-localityName (alias L)
-stateOrProvinceName (alias ST)
-organizationName (alias O)
-organizationUnitName (alias OU)
-title
-description
-initials
-postalCode
-streetAddress
-generationQualifier
-description
-dnQualifier
-x500UniqueIdentifier
-pseudonym
-role
-emailAddress
-</literallayout>
-    <para>
-     All of these fields are optional, except <structfield>commonName</>.
-     It depends
-     entirely on your CA's policy which of them would be included and which
-     wouldn't.  The meaning of these fields, however, is strictly defined by
-     the X.500 and X.509 standards, so you cannot just assign arbitrary
-     meaning to them.
-    </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><function>
-ssl_issuer_field(fieldname text) returns text
-    </function></term>
-    <listitem>
-    <para>
-     Same as <function>ssl_client_dn_field</>, but for the certificate issuer
-     rather than the certificate subject.
-    </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Victor Wagner <email>[email protected]</email>, Cryptocom LTD
-  </para>
-
-  <para>
-   E-Mail of Cryptocom OpenSSL development group:
-   <email>[email protected]</email>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/standalone-install.sgmlin b/doc-xc/src/sgml/standalone-install.sgmlin
deleted file mode 100644
index c94b397a9d..0000000000
--- a/doc-xc/src/sgml/standalone-install.sgmlin
+++ /dev/null
@@ -1,42 +0,0 @@
-<!-- doc/src/sgml/standalone-install.sgml -->
-
-<!--
-This file helps in generating the INSTALL text file that lives in the
-top level directory of the distribution. The exact process is like
-this:
-
-1. Paste together with installation.sgml
-
-2. Process with jade to HTML (use -V nochunks)
-
-3. Remove "Chapter 1" heading
-
-4. Save as text file in Netscape
-
-5. Put in place of old INSTALL file
-
-Running 'make INSTALL' in the doc/src/sgml directory will do 1 through
-3 for you.
--->
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN" [
-
-<!ENTITY % version SYSTEM "version.sgml">
-%version;
-
-<!--
-The standalone version has some portions that are different from the
-version that is integrated into the full documentation set, in
-particular as regards links. The following are essentially SGML's
-equivalent of C's #ifdef and friends. The other end of this is in
-installation.sgml.
--->
-
- <!ENTITY % standalone-ignore  "IGNORE">
- <!ENTITY % standalone-include "INCLUDE">
-
-<!--
-When you're building the full documentation set, you want to flip the
-IGNORE and INCLUDE.
--->
-]>
diff --git a/doc-xc/src/sgml/start.sgmlin b/doc-xc/src/sgml/start.sgmlin
deleted file mode 100644
index adbe9ae970..0000000000
--- a/doc-xc/src/sgml/start.sgmlin
+++ /dev/null
@@ -1,891 +0,0 @@
-<!-- doc/src/sgml/start.sgml -->
-
- <chapter id="tutorial-start">
-  <title>Getting Started</title>
-
-  <sect1 id="tutorial-install">
-   <title>Installation</title>
-
-   <para>
-&common;
-    <!## PG>
-    Before you can use <productname>PostgreSQL</productname> you need
-    to install it, of course.  It is possible that
-    <productname>PostgreSQL</productname> is already installed at your
-    site, either because it was included in your operating system
-    distribution or because the system administrator already installed
-    it.  If that is the case, you should obtain information from the
-    operating system documentation or your system administrator about
-    how to access <productname>PostgreSQL</productname>.
-    <!## end>
-    <!## XC>
-    Before you can use <productname>Postgres-XC</productname> you need
-    to install it, of course.  It is possible that
-    <productname>Postgres-XC</productname> is already installed at your
-    site, either because it was included in your operating system
-    distribution or because the system administrator already installed
-    it.  If that is the case, you should obtain information from the
-    operating system documentation or your system administrator about
-    how to access <productname>Postgres-XC</productname>.
-    <!## end>
-    <!## XL>
-    Before you can use <productname>Postgres-XL</productname> you need
-    to install it, of course.  It is possible that
-    <productname>Postgres-XL</productname> is already installed at your
-    site, either because it was included in your operating system
-    distribution or because the system administrator already installed
-    it.  If that is the case, you should obtain information from the
-    operating system documentation or your system administrator about
-    how to access <productname>Postgres-XL</productname>.
-    <!## end>
-   </para>
-
-   <para>
-    <!## PG>
-    If you are not sure whether <productname>PostgreSQL</productname>
-    is already available or whether you can use it for your
-    experimentation then you can install it yourself.  Doing so is not
-    hard and it can be a good exercise.
-    <productname>PostgreSQL</productname> can be installed by any
-    unprivileged user; no superuser (<systemitem>root</systemitem>)
-    access is required.
-    <!## end>
-    <!## XC>
-    If you are not sure whether <productname>Postgres-XC</productname>
-    is already available or whether you can use it for your
-    experimentation then you can install it yourself.  Doing so is not
-    hard and it can be a good exercise.
-    <productname>Postgres-XC</productname> can be installed by any
-    unprivileged user; no superuser (<systemitem>root</systemitem>)
-    access is required.
-    <!## end>
-    <!## XL>
-    If you are not sure whether <productname>Postgres-XL</productname>
-    is already available or whether you can use it for your
-    experimentation then you can install it yourself.  Doing so is not
-    hard and it can be a good exercise.
-    <productname>Postgres-XL</productname> can be installed by any
-    unprivileged user; no superuser (<systemitem>root</systemitem>)
-    access is required.
-    <!## end>
-   </para>
-
-   <para>
-    <!## PG>
-    If you are installing <productname>PostgreSQL</productname>
-    yourself, then refer to <xref linkend="installation">
-    for instructions on installation, and return to
-    this guide when the installation is complete.  Be sure to follow
-    closely the section about setting up the appropriate environment
-    variables.
-    <!## end>
-    <!## XC>
-    If you are installing <productname>Postgres-XC</productname>
-    yourself, then refer to <xref linkend="installation">
-    for instructions on installation, and return to
-    this guide when the installation is complete.  Be sure to follow
-    closely the section about setting up the appropriate environment
-    variables.
-    <!## end>
-    <!## XL>
-    If you are installing <productname>Postgres-XL</productname>
-    yourself, then refer to <xref linkend="installation">
-    for instructions on installation, and return to
-    this guide when the installation is complete.  Be sure to follow
-    closely the section about setting up the appropriate environment
-    variables.
-    <!## end>
-   </para>
-
-   <para>
-    If your site administrator has not set things up in the default
-    way, you might have some more work to do.  For example, if the
-    database server machine is a remote machine, you will need to set
-    the <envar>PGHOST</envar> environment variable to the name of the
-    database server machine.  The environment variable
-    <envar>PGPORT</envar> might also have to be set.  The bottom line is
-    this: if you try to start an application program and it complains
-    that it cannot connect to the database, you should consult your
-    site administrator or, if that is you, the documentation to make
-    sure that your environment is properly set up.  If you did not
-    understand the preceding paragraph then read the next section.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-arch">
-   <title>Architectural Fundamentals</title>
-
-<!## XC>
-&xconly;
-<!## end>
-<!## XL>
-&xlonly;
-<!## end>
-
-   <para>
-<!## PG>
-    Before we proceed, you should understand the basic
-    <productname>PostgreSQL</productname> system architecture.
-    Understanding how the parts of
-    <productname>PostgreSQL</productname> interact will make this
-    chapter somewhat clearer.
-<!## end>
-<!## XC>
-    Before we proceed, you should understand the basic
-    <productname>Postgres-XC</productname> system architecture.
-    Understanding how the parts of
-    <productname>Postgres-XC</productname> interact will make this
-    chapter somewhat clearer.
-<!## end>
-<!## XL>
-    Before we proceed, you should understand the basic
-    <productname>Postgres-XL</productname> system architecture.
-    Understanding how the parts of
-    <productname>Postgres-XL</productname> interact will make this
-    chapter somewhat clearer.
-<!## end>
-   </para>
-
-<!## XC>
-   <para>
-    <productname>Postgres-XC</>, in short, is a collection
-    of <productname>PostgreSQL</> database clusters which act as if the whole
-    collection is a single database cluster.  Based on your database design,
-    each table is replicated or distributed among member databases.
-   </para>
-
-   <para>
-    To provide this capability, <productname>Postgres-XC</> is
-    composed of three major components called GTM, Coordinator and
-    Datanode.  GTM is responsible to provide ACID property of
-    transactions. Datanode stores table data and handle SQL statements
-    locally.  Coordinator handles each SQL statements from
-    applications, determines which datanode to go, and decomposes it
-    into local SQL statements for each datanode.
-   </para>
-
-   <para>
-    You should run GTM in a separate server because GTM has to take
-    care of transaction requirements from all the coordinators and
-    datanodes.  To group multiple requirements and responses from
-    coordinator and datanode running on the same server, you can
-    configure GTM-Proxy.  GTM-Proxy reduces the number of interaction
-    and the amount of data to GTM.  GTM-Proxy also helps to take care
-    of GTM failure.
-   </para>
-
-   <para>
-    It is a good convention to run both coordinator and datanode in a
-    same server because we don't have to worry about workload balance
-    between the two.  You can have any number of servers where these
-    two components are running.  Because both coordinator and datanode
-    are essentially PostgreSQL database, you should configure them to
-    avoid resource conflict.  It is very important to assign them
-    different working directory and port number.
-   </para>
-
-   <para>
-    Postgres-XC allow multiple coordinators which accept statments
-    from applications independently but in an integrated way.  Any
-    writes from any coordinator is available from any other
-    coordinators.  They acts as if they are single database.
-    Coordinator's role is to accept statments, find what datanodes are
-    involved, Ode-compose incoming statements for each datanode if
-    needed, proxy statements to target datanode, collect the results
-    and write them back to applications.
-   </para>
-
-   <para>
-    Coordinator does not store any user data.  It stores only catalog
-    data to determine how to decompose the statement, where the target
-    datanodes are, among others.  Therefore, you don't have to worry
-    about coordinator failure much.  When the coordinator fails, you
-    can just switch to the other one.
-   </para>
-
-   <para>
-    GTM could be single point of failure (SPOF).  To prevent this, you
-    can run another GTM as GTM-Standby to backup GTM's status.  When
-    GTM fails, GTM-Proxy can switch to the standby on the fly.  This
-    will be described in detail in high-availability sections.
-   </para>
-<!## end>
-<!## XL>
-   <para>
-    <productname>Postgres-XL</>, in short, is a collection
-    of <productname>PostgreSQL</> database clusters which act as if the whole
-    collection is a single database cluster.  Based on your database design,
-    each table is replicated or distributed among member databases.
-   </para>
-
-  <para>
-    To provide this capability, <productname>Postgres-XL</> is
-    composed of three major components called the GTM, Coordinator and
-    Datanode.  The GTM is responsible to provide ACID property of
-    transactions. The Datanode stores table data and handle SQL statements
-    locally.  The Coordinator handles each SQL statements from
-    applications, determines which Datanode to go, and sends plans on
-    to the appropriate Datanodes.
-   </para>
-
-   <para>
-    You usually should run GTM on a separate server because GTM has to take
-    care of transaction requirements from all the Coordinators and
-    Datanodes.  To group multiple requests and responses from
-    Coordinator and Datanode processes running on the same server, you can
-    configure GTM-Proxy.  GTM-Proxy reduces the number of interactions
-    and the amount of data to GTM.  GTM-Proxy also helps handle
-    GTM failures.
-   </para>
-
-   <para>
-    It is often good practice to run both Coordinator and Datanode on the
-    same server because we don't have to worry about workload balance
-    between the two, and you can often get at data from replicated tables locally
-    without sending an additional request out on the network.
-    You can have any number of servers where these
-    two components are running.  Because both Coordinator and Datanode
-    are essentially PostgreSQL instances, you should configure them to
-    avoid resource conflict.  It is very important to assign them
-    different working directories and port numbers.
-   </para>
-
-   <para>
-    Postgres-XL allows multiple Coordinators to accept statements
-    from applications independently but in an integrated way.  Any
-    writes from any Coordinator is available from any other
-    Coordinators.  They acts as if they are single database.
-    The Coordinator's role is to accept statements, find what Datanodes are
-    involved, send query plans on to the appropriate Datanodes if
-    needed, collect the results
-    and write them back to applications.
-   </para>
-
-   <para>
-    The Coordinator does not store any user data.  It stores only catalog
-    data to determine how to process statements, where the target
-    Datanodes are, among others.  Therefore, you don't have to worry
-    about Coordinator failure much.  When the Coordinator fails, you
-    can just switch to the other one.
-   </para>
-
-   <para>
-    The GTM could be single point of failure (SPOF).  To prevent this, you
-    can run another GTM as GTM-Standby to backup GTM's status.  When
-    GTM fails, GTM-Proxy can switch to the standby on the fly.  This
-    will be described in detail in high-availability sections.
-   </para>
-<!## end>
-   <para>
-<!## PG>
-    In database jargon, <productname>PostgreSQL</productname> uses a
-    client/server model.  A <productname>PostgreSQL</productname>
-    session consists of the following cooperating processes
-    (programs):
-<!## end>
-<!## XC>
-    As described above, coordinator and datanode
-    of <productname>Postgres-XC</> are
-    essentially <productname>PostgreSQL</> database servers. In database
-    jargon, <productname>PostgreSQL</productname> uses a client/server
-    model.  A <productname>PostgreSQL</productname> session consists
-    of the following cooperating processes (programs):
-<!## end>
-<!## XL>
-    As described above, the Coordinators and Datanodes
-    of <productname>Postgres-XL</> are
-    essentially <productname>PostgreSQL</> database servers. In database
-    jargon, <productname>PostgreSQL</productname> uses a client/server
-    model.  A <productname>PostgreSQL</productname> session consists
-    of the following cooperating processes (programs):
-<!## end>
-
-&common;
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       A server process, which manages the database files, accepts
-       connections to the database from client applications, and
-       performs database actions on behalf of the clients.  The
-       database server program is called
-       <filename>postgres</filename>.
-       <indexterm><primary>postgres</primary></indexterm>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The user's client (frontend) application that wants to perform
-       database operations.  Client applications can be very diverse
-       in nature:  a client could be a text-oriented tool, a graphical
-       application, a web server that accesses the database to
-       display web pages, or a specialized database maintenance tool.
-       Some client applications are supplied with the
-<!## PG>
-       <productname>PostgreSQL</productname> distribution; most are
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</productname> distribution; most are
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</productname> distribution; most are
-<!## end>
-       developed by users.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </para>
-
-   <para>
-    As is typical of client/server applications, the client and the
-    server can be on different hosts.  In that case they communicate
-    over a TCP/IP network connection.  You should keep this in mind,
-    because the files that can be accessed on a client machine might
-    not be accessible (or might only be accessible using a different
-    file name) on the database server machine.
-   </para>
-
-   <para>
-<!## PG>
-    The <productname>PostgreSQL</productname> server can handle
-    multiple concurrent connections from clients.  To achieve this it
-    starts (<quote>forks</quote>) a new process for each connection.
-    From that point on, the client and the new server process
-    communicate without intervention by the original
-    <filename>postgres</filename> process.  Thus, the
-    master server process is always running, waiting for
-    client connections, whereas client and associated server processes
-    come and go.  (All of this is of course invisible to the user.  We
-    only mention it here for completeness.)
-<!## end>
-<!## XC>
-    The <productname>Postgres-XC</> can handle
-    multiple concurrent connections from clients.  To achieve this it
-    starts (<quote>forks</quote>) a new process for each connection.
-    From that point on, the client and the new server process
-    communicate without intervention by the original
-    <filename>postgres</filename> process.  Thus, the
-    master server process is always running, waiting for
-    client connections, whereas client and associated server processes
-    come and go.  (All of this is of course invisible to the user.  We
-    only mention it here for completeness.)
-<!## end>
-<!## XL>
-    The <productname>Postgres-XL</> can handle
-    multiple concurrent connections from clients.  To achieve this it
-    starts (<quote>forks</quote>) a new process for each connection.
-    From that point on, the client and the new server process
-    communicate without intervention by the original
-    <filename>postgres</filename> process.  Thus, the
-    master server process is always running, waiting for
-    client connections, whereas client and associated server processes
-    come and go.  (All of this is of course invisible to the user.  We
-    only mention it here for completeness.)
-<!## end>
-   </para>
-  </sect1>
-
-
-
-  <sect1 id="tutorial-createdb">
-   <title>Creating a Database</title>
-
-   <indexterm zone="tutorial-createdb">
-    <primary>database</primary>
-    <secondary>creating</secondary>
-   </indexterm>
-
-   <indexterm zone="tutorial-createdb">
-    <primary>createdb</primary>
-   </indexterm>
-&common;
-   <para>
-<!## PG>
-    The first test to see whether you can access the database server
-    is to try to create a database.  A running
-    <productname>PostgreSQL</productname> server can manage many
-    databases.  Typically, a separate database is used for each
-    project or for each user.
-<!## end>
-<!## XC>
-    The first test to see whether you can access the database server
-    is to try to create a database.  Running
-    <productname>Postgres-XC</productname> servers (coordinators and datanodes)  can manage many
-    databases.  Typically, a separate database is used for each
-    project or for each user.
-<!## end>
-<!## XL>
-    The first test to see whether you can access the database server
-    is to try to create a database.  Running
-    <productname>Postgres-XL</productname> servers (coordinators and datanodes)  can manage many
-    databases.  Typically, a separate database is used for each
-    project or for each user.
-<!## end>
-   </para>
-
-
-   <para>
-    Possibly, your site administrator has already created a database
-    for your use.  He should have told you what the name of your
-    database is.  In that case you can omit this step and skip ahead
-    to the next section.
-   </para>
-
-   <para>
-    To create a new database, in this example named
-    <literal>mydb</literal>, you use the following command:
-<screen>
-<prompt>$</prompt> <userinput>createdb mydb</userinput>
-</screen>
-    If this produces no response then this step was successful and you can skip over the
-    remainder of this section.
-   </para>
-
-   <para>
-    If you see a message similar to:
-<screen>
-createdb: command not found
-</screen>
-<!## PG>
-    then <productname>PostgreSQL</> was not installed properly.  Either it was not
-<!## end>
-<!## XC>
-    then <productname>Postgres-XC</> was not installed properly.  Either it was not
-<!## end>
-<!## XL>
-    then <productname>Postgres-XL</> was not installed properly.  Either it was not
-<!## end>
-    installed at all or your shell's search path was not set to include it.
-    Try calling the command with an absolute path instead:
-<screen>
-<prompt>$</prompt> <userinput>/usr/local/pgsql/bin/createdb mydb</userinput>
-</screen>
-    The path at your site might be different.  Contact your site
-    administrator or check the installation instructions to
-    correct the situation.
-   </para>
-
-
-   <para>
-    Another response could be this:
-<screen>
-createdb: could not connect to database postgres: could not connect to server: No such file or directory
-        Is the server running locally and accepting
-        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
-</screen>
-    This means that the server was not started, or it was not started
-    where <command>createdb</command> expected it.  Again, check the
-    installation instructions or consult the administrator.
-   </para>
-
-   <para>
-    Another response could be this:
-<screen>
-createdb: could not connect to database postgres: FATAL:  role "joe" does not exist
-</screen>
-<!## PG>
-    where your own login name is mentioned.  This will happen if the
-    administrator has not created a <productname>PostgreSQL</> user account
-    for you.  (<productname>PostgreSQL</> user accounts are distinct from
-    operating system user accounts.)  If you are the administrator, see
-    <xref linkend="user-manag"> for help creating accounts.  You will need to
-    become the operating system user under which <productname>PostgreSQL</>
-    was installed (usually <literal>postgres</>) to create the first user
-    account.  It could also be that you were assigned a
-    <productname>PostgreSQL</> user name that is different from your
-    operating system user name; in that case you need to use the <option>-U</>
-    switch or set the <envar>PGUSER</> environment variable to specify your
-    <productname>PostgreSQL</> user name.
-<!## end>
-<!## XC>
-    where your own login name is mentioned.  This will happen if the
-    administrator has not created a <productname>Postgres-XC</> user account
-    for you.  (<productname>Postgres-XC</> user accounts are distinct from
-    operating system user accounts.)  If you are the administrator, see
-    <xref linkend="user-manag"> for help creating accounts.  You will need to
-    become the operating system user under which <productname>Postgres-XC</>
-    was installed (usually <literal>postgres</>) to create the first user
-    account.  It could also be that you were assigned a
-    <productname>Postgres-XC</> user name that is different from your
-    operating system user name; in that case you need to use the <option>-U</>
-    switch or set the <envar>PGUSER</> environment variable to specify your
-    <productname>Postgres-XC</> user name.
-<!## end>
-<!## XL>
-    where your own login name is mentioned.  This will happen if the
-    administrator has not created a <productname>Postgres-XL</> user account
-    for you.  (<productname>Postgres-XL</> user accounts are distinct from
-    operating system user accounts.)  If you are the administrator, see
-    <xref linkend="user-manag"> for help creating accounts.  You will need to
-    become the operating system user under which <productname>Postgres-XL</>
-    was installed (usually <literal>postgres</>) to create the first user
-    account.  It could also be that you were assigned a
-    <productname>Postgres-XL</> user name that is different from your
-    operating system user name; in that case you need to use the <option>-U</>
-    switch or set the <envar>PGUSER</> environment variable to specify your
-    <productname>Postgres-XL</> user name.
-<!## end>
-   </para>
-
-<!## XC>
-&xconly;
-<!## end>
-<!## XL>
-&xlonly;
-<!## end>
-   <para>
-    If you have a user account but it does not have the privileges required to
-    create a database, you will see the following:
-<screen>
-createdb: database creation failed: ERROR:  permission denied to create database
-</screen>
-<!## PG>
-    Not every user has authorization to create new databases.  If
-    <productname>PostgreSQL</productname> refuses to create databases
-    for you then the site administrator needs to grant you permission
-    to create databases.  Consult your site administrator if this
-    occurs.  If you installed <productname>PostgreSQL</productname>
-    yourself then you should log in for the purposes of this tutorial
-    under the user account that you started the server as.
-<!## end>
-<!## XC>
-    Not every user has authorization to create new databases.  If
-    <productname>Postgres-XC</productname> refuses to create databases
-    for you then the site administrator needs to grant you permission
-    to create databases.  Consult your site administrator if this
-    occurs.  If you installed <productname>Postgres-XC</productname>
-    yourself then you should log in for the purposes of this tutorial
-    under the user account that you started the server as.
-<!## end>
-<!## XL>
-    Not every user has authorization to create new databases.  If
-    <productname>Postgres-XL</productname> refuses to create databases
-    for you then the site administrator needs to grant you permission
-    to create databases.  Consult your site administrator if this
-    occurs.  If you installed <productname>Postgres-XL</productname>
-    yourself then you should log in for the purposes of this tutorial
-    under the user account that you started the server as.
-<!## end>
-
-<!## XC>
-    Or you may have error message like:
-<screen>
-createdb: database creation failed: ERROR:  source database "template1" is being accessed by other users
-DETAIL:  There are 1 other session(s) using the database.
-</screen>
-    This means that at least one of the Coordinator poolers still holds a connection to template1 database to one of the datanodes.  To release them, you should do the following as the database superuser.
-<screen>
-<prompt>$</prompt> <userinput>psql</userinput>
-...
-<prompt>koichi=#</prompt> <userinput>CLEAN CONNECTION TO ALL FOR template1;</userinput>
-CLEAN CONNECTION
-<prompt>koichi=#</prompt>
-</screen>
-   </para>
-<!## end>
-<!## XL>
-    Or you may have error message like:
-<screen>
-createdb: database creation failed: ERROR:  source database "template1" is being accessed by other users
-DETAIL:  There are 1 other session(s) using the database.
-</screen>
-    This means that at least one of the Coordinator poolers still holds a connection to template1 database to one of the datanodes.  To release them, you should do the following as the database superuser.
-<screen>
-<prompt>$</prompt> <userinput>psql</userinput>
-...
-<prompt>koichi=#</prompt> <userinput>CLEAN CONNECTION TO ALL FOR template1;</userinput>
-CLEAN CONNECTION
-<prompt>koichi=#</prompt>
-</screen>
-   </para>
-<!## end>
-
-&common;
-   <para>
-    <footnote>
-     <para>
-<!## PG>
-      As an explanation for why this works:
-      <productname>PostgreSQL</productname> user names are separate
-      from operating system user accounts.  When you connect to a
-      database, you can choose what
-      <productname>PostgreSQL</productname> user name to connect as;
-      if you don't, it will default to the same name as your current
-      operating system account.  As it happens, there will always be a
-      <productname>PostgreSQL</productname> user account that has the
-      same name as the operating system user that started the server,
-      and it also happens that that user always has permission to
-      create databases.  Instead of logging in as that user you can
-      also specify the <option>-U</option> option everywhere to select
-      a <productname>PostgreSQL</productname> user name to connect as.
-<!## end>
-<!## XC>
-      As an explanation for why this works:
-      <productname>Postgres-XC</productname> user names are separate
-      from operating system user accounts.  When you connect to a
-      database, you can choose what
-      <productname>Postgres-XC</productname> user name to connect as;
-      if you don't, it will default to the same name as your current
-      operating system account.  As it happens, there will always be a
-      <productname>Postgres-XC</productname> user account that has the
-      same name as the operating system user that started the server,
-      and it also happens that that user always has permission to
-      create databases.  Instead of logging in as that user you can
-      also specify the <option>-U</option> option everywhere to select
-      a <productname>Postgres-XC</productname> user name to connect as.
-<!## end>
-<!## XL>
-      As an explanation for why this works:
-      <productname>Postgres-XL</productname> user names are separate
-      from operating system user accounts.  When you connect to a
-      database, you can choose what
-      <productname>Postgres-XL</productname> user name to connect as;
-      if you don't, it will default to the same name as your current
-      operating system account.  As it happens, there will always be a
-      <productname>Postgres-XL</productname> user account that has the
-      same name as the operating system user that started the server,
-      and it also happens that that user always has permission to
-      create databases.  Instead of logging in as that user you can
-      also specify the <option>-U</option> option everywhere to select
-      a <productname>Postgres-XL</productname> user name to connect as.
-<!## end>
-     </para>
-    </footnote>
-   </para>
-
-   <para>
-&common;
-<!## PG>
-    You can also create databases with other names.
-    <productname>PostgreSQL</productname> allows you to create any
-    number of databases at a given site.  Database names must have an
-    alphabetic first character and are limited to 63 characters in
-    length.  A convenient choice is to create a database with the same
-    name as your current user name.  Many tools assume that database
-    name as the default, so it can save you some typing.  To create
-    that database, simply type:
-<!## end>
-<!## XC>
-    You can also create databases with other names.
-    <productname>Postgres-XC</productname> allows you to create any
-    number of databases at a given site.  Database names must have an
-    alphabetic first character and are limited to 63 characters in
-    length.  A convenient choice is to create a database with the same
-    name as your current user name.  Many tools assume that database
-    name as the default, so it can save you some typing.  To create
-    that database, simply type:
-<!## end>
-<!## XL>
-    You can also create databases with other names.
-    <productname>Postgres-XL</productname> allows you to create any
-    number of databases at a given site.  Database names must have an
-    alphabetic first character and are limited to 63 characters in
-    length.  A convenient choice is to create a database with the same
-    name as your current user name.  Many tools assume that database
-    name as the default, so it can save you some typing.  To create
-    that database, simply type:
-<!## end>
-<screen>
-<prompt>$</prompt> <userinput>createdb</userinput>
-</screen>
-   </para>
-
-   <para>
-    If you do not want to use your database anymore you can remove it.
-    For example, if you are the owner (creator) of the database
-    <literal>mydb</literal>, you can destroy it using the following
-    command:
-<screen>
-<prompt>$</prompt> <userinput>dropdb mydb</userinput>
-</screen>
-    (For this command, the database name does not default to the user
-    account name.  You always need to specify it.)  This action
-    physically removes all files associated with the database and
-    cannot be undone, so this should only be done with a great deal of
-    forethought.
-   </para>
-
-   <para>
-    More about <command>createdb</command> and <command>dropdb</command> can
-    be found in <xref linkend="APP-CREATEDB"> and <xref linkend="APP-DROPDB">
-    respectively.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-accessdb">
-   <title>Accessing a Database</title>
-
-   <indexterm zone="tutorial-accessdb">
-    <primary>psql</primary>
-   </indexterm>
-&common;
-   <para>
-    Once you have created a database, you can access it by:
-
-    <itemizedlist spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-<!## PG>
-       Running the <productname>PostgreSQL</productname> interactive
-       terminal program, called <application><firstterm>psql</></application>, which allows you
-       to interactively enter, edit, and execute
-       <acronym>SQL</acronym> commands.
-<!## end>
-<!## XC>
-       Running the <productname>Postgres-XC</productname> interactive
-       terminal program, called <application><firstterm>psql</></application>, which allows you
-       to interactively enter, edit, and execute
-       <acronym>SQL</acronym> commands.
-<!## end>
-<!## XL>
-       Running the <productname>Postgres-XL</productname> interactive
-       terminal program, called <application><firstterm>psql</></application>, which allows you
-       to interactively enter, edit, and execute
-       <acronym>SQL</acronym> commands.
-<!## end>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Using an existing graphical frontend tool like
-       <application>pgAdmin</application> or an office suite with
-       <acronym>ODBC</> or <acronym>JDBC</> support to create and manipulate a
-       database.  These possibilities are not covered in this
-       tutorial.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Writing a custom application, using one of the several
-       available language bindings.  These possibilities are discussed
-       further in <xref linkend="client-interfaces">.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    You probably want to start up <command>psql</command> to try
-    the examples in this tutorial.  It can be activated for the
-    <literal>mydb</literal> database by typing the command:
-<screen>
-<prompt>$</prompt> <userinput>psql mydb</userinput>
-</screen>
-    If you do not supply the database name then it will default to your
-    user account name.  You already discovered this scheme in the
-    previous section using <command>createdb</command>.
-   </para>
-
-   <para>
-    In <command>psql</command>, you will be greeted with the following
-    message:
-<screen>
-psql (&version;)
-Type "help" for help.
-
-mydb=&gt;
-</screen>
-    <indexterm><primary>superuser</primary></indexterm>
-    The last line could also be:
-<screen>
-mydb=#
-</screen>
-<!## PG>
-    That would mean you are a database superuser, which is most likely
-    the case if you installed <productname>PostgreSQL</productname>
-    yourself.  Being a superuser means that you are not subject to
-    access controls.  For the purposes of this tutorial that is not
-    important.
-<!## end>
-<!## XC>
-    That would mean you are a database superuser, which is most likely
-    the case if you installed <productname>Postgres-XC</productname>
-    yourself.  Being a superuser means that you are not subject to
-    access controls.  For the purposes of this tutorial that is not
-    important.
-<!## end>
-<!## XL>
-    That would mean you are a database superuser, which is most likely
-    the case if you installed <productname>Postgres-XL</productname>
-    yourself.  Being a superuser means that you are not subject to
-    access controls.  For the purposes of this tutorial that is not
-    important.
-<!## end>
-   </para>
-
-   <para>
-    If you encounter problems starting <command>psql</command>
-    then go back to the previous section.  The diagnostics of
-    <command>createdb</command> and <command>psql</command> are
-    similar, and if the former worked the latter should work as well.
-   </para>
-
-   <para>
-<!-- The following function does not acto properly.   Not good to put in the reference manual -->
-    The last line printed out by <command>psql</command> is the
-    prompt, and it indicates that <command>psql</command> is listening
-    to you and that you can type <acronym>SQL</acronym> queries into a
-    work space maintained by <command>psql</command>.  Try out these
-    commands:
-    <indexterm><primary>version</primary></indexterm>
-<screen>
-<prompt>mydb=&gt;</prompt> <userinput>SELECT version();</userinput>
-                               version
- -----------------------------------------------------------------------
- PostgreSQL &version; on i586-pc-linux-gnu, compiled by GCC 2.96, 32-bit
-(1 row)
-
-<prompt>mydb=&gt;</prompt> <userinput>SELECT current_date;</userinput>
-    date
-------------
- 2002-08-31
-(1 row)
-
-<prompt>mydb=&gt;</prompt> <userinput>SELECT 2 + 2;</userinput>
- ?column?
-----------
-        4
-(1 row)
-</screen>
-   </para>
-
-   <para>
-    The <command>psql</command> program has a number of internal
-    commands that are not SQL commands.  They begin with the backslash
-    character, <quote><literal>\</literal></quote>.
-    For example,
-    you can get help on the syntax of various
-<!## PG>
-    <productname>PostgreSQL</productname> <acronym>SQL</acronym>
-<!## end>
-<!## XC>
-    <acronym>SQL</acronym>
-<!## end>
-<!## XL>
-    <acronym>SQL</acronym>
-<!## end>
-    commands by typing:
-<screen>
-<prompt>mydb=&gt;</prompt> <userinput>\h</userinput>
-</screen>
-   </para>
-
-   <para>
-    To get out of <command>psql</command>, type:
-<screen>
-<prompt>mydb=&gt;</prompt> <userinput>\q</userinput>
-</screen>
-    and <command>psql</command> will quit and return you to your
-    command shell. (For more internal commands, type
-    <literal>\?</literal> at the <command>psql</command> prompt.)  The
-    full capabilities of <command>psql</command> are documented in
-    <xref linkend="app-psql">.  In this tutorial we will not use these
-    features explicitly, but you can use them yourself when it is helpful.
-   </para>
-
-  </sect1>
- </chapter>
diff --git a/doc-xc/src/sgml/storage.sgmlin b/doc-xc/src/sgml/storage.sgmlin
deleted file mode 100644
index 3811e47e9a..0000000000
--- a/doc-xc/src/sgml/storage.sgmlin
+++ /dev/null
@@ -1,882 +0,0 @@
-<!-- doc/src/sgml/storage.sgml -->
-
-<chapter id="storage">
-
-<title>Database Physical Storage</title>
-
-&pgnotice;
-
-<para>
-This chapter provides an overview of the physical storage format used by
-<productname>PostgreSQL</productname> databases.
-</para>
-
-<sect1 id="storage-file-layout">
-
-<title>Database File Layout</title>
-
-&pgnotice;
-<para>
-This section describes the storage format at the level of files and
-directories.
-</para>
-
-<para>
-All the data needed for a database cluster is stored within the cluster's data
-directory, commonly referred to as <varname>PGDATA</> (after the name of the
-environment variable that can be used to define it).  A common location for
-<varname>PGDATA</> is <filename>/var/lib/pgsql/data</>.  Multiple clusters,
-managed by different server instances, can exist on the same machine.
-</para>
-
-<para>
-The <varname>PGDATA</> directory contains several subdirectories and control
-files, as shown in <xref linkend="pgdata-contents-table">.  In addition to
-these required items, the cluster configuration files
-<filename>postgresql.conf</filename>, <filename>pg_hba.conf</filename>, and
-<filename>pg_ident.conf</filename> are traditionally stored in
-<varname>PGDATA</> (although in <productname>PostgreSQL</productname> 8.0 and
-later, it is possible to keep them elsewhere).
-</para>
-
-<table tocentry="1" id="pgdata-contents-table">
-<title>Contents of <varname>PGDATA</></title>
-<tgroup cols="2">
-<thead>
-<row>
-<entry>
-Item
-</entry>
-<entry>Description</entry>
-</row>
-</thead>
-
-<tbody>
-
-<row>
- <entry><filename>PG_VERSION</></entry>
- <entry>A file containing the major version number of <productname>PostgreSQL</productname></entry>
-</row>
-
-<row>
- <entry><filename>base</></entry>
- <entry>Subdirectory containing per-database subdirectories</entry>
-</row>
-
-<row>
- <entry><filename>global</></entry>
- <entry>Subdirectory containing cluster-wide tables, such as
- <structname>pg_database</></entry>
-</row>
-
-<row>
- <entry><filename>pg_clog</></entry>
- <entry>Subdirectory containing transaction commit status data</entry>
-</row>
-
-<row>
- <entry><filename>pg_multixact</></entry>
- <entry>Subdirectory containing multitransaction status data
-  (used for shared row locks)</entry>
-</row>
-
-<row>
- <entry><filename>pg_notify</></entry>
- <entry>Subdirectory containing LISTEN/NOTIFY status data</entry>
-</row>
-
-<row>
- <entry><filename>pg_serial</></entry>
- <entry>Subdirectory containing information about committed serializable transactions</entry>
-</row>
-
-<row>
- <entry><filename>pg_stat_tmp</></entry>
- <entry>Subdirectory containing temporary files for the statistics
-  subsystem</entry>
-</row>
-
-<row>
- <entry><filename>pg_subtrans</></entry>
- <entry>Subdirectory containing subtransaction status data</entry>
-</row>
-
-<row>
- <entry><filename>pg_tblspc</></entry>
- <entry>Subdirectory containing symbolic links to tablespaces</entry>
-</row>
-
-<row>
- <entry><filename>pg_twophase</></entry>
- <entry>Subdirectory containing state files for prepared transactions</entry>
-</row>
-
-<row>
- <entry><filename>pg_xlog</></entry>
- <entry>Subdirectory containing WAL (Write Ahead Log) files</entry>
-</row>
-
-<row>
- <entry><filename>postmaster.opts</></entry>
- <entry>A file recording the command-line options the server was
-last started with</entry>
-</row>
-
-<row>
- <entry><filename>postmaster.pid</></entry>
- <entry>A lock file recording the current postmaster process id (PID),
-  cluster data directory path,
-  postmaster start timestamp,
-  port number,
-  Unix-domain socket directory path (empty on Windows),
-  first valid listen_address (IP address or <literal>*</>, or empty if
-  not listening on TCP),
-  and shared memory segment ID
-  (this file is not present after server shutdown)</entry>
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-<para>
-For each database in the cluster there is a subdirectory within
-<varname>PGDATA</><filename>/base</>, named after the database's OID in
-<structname>pg_database</>.  This subdirectory is the default location
-for the database's files; in particular, its system catalogs are stored
-there.
-</para>
-
-<para>
-Each table and index is stored in a separate file.  For ordinary relations,
-these files are named after the table or index's <firstterm>filenode</> number,
-which can be found in <structname>pg_class</>.<structfield>relfilenode</>. But
-for temporary relations, the file name is of the form
-<literal>t<replaceable>BBB</>_<replaceable>FFF</></>, where <replaceable>BBB</>
-is the backend ID of the backend which created the file, and <replaceable>FFF</>
-is the filenode number.  In either case, in addition to the main file (a/k/a
-main fork), each table and index has a <firstterm>free space map</> (see <xref
-linkend="storage-fsm">), which stores information about free space available in
-the relation.  The free space map is stored in a file named with the filenode
-number plus the suffix <literal>_fsm</>.  Tables also have a
-<firstterm>visibility map</>, stored in a fork with the suffix <literal>_vm</>,
-to track which pages are known to have no dead tuples.  The visibility map is
-described further in <xref linkend="storage-vm">.  Unlogged tables and indexes
-have a third fork, known as the initialization fork, which is stored in a fork
-with the suffix <literal>_init</literal> (see <xref linkend="storage-init">).
-</para>
-
-<caution>
-<para>
-Note that while a table's filenode often matches its OID, this is
-<emphasis>not</> necessarily the case; some operations, like
-<command>TRUNCATE</>, <command>REINDEX</>, <command>CLUSTER</> and some forms
-of <command>ALTER TABLE</>, can change the filenode while preserving the OID.
-Avoid assuming that filenode and table OID are the same.
-Also, for certain system catalogs including <structname>pg_class</> itself,
-<structname>pg_class</>.<structfield>relfilenode</> contains zero.  The
-actual filenode number of these catalogs is stored in a lower-level data
-structure, and can be obtained using the <function>pg_relation_filenode()</>
-function.
-</para>
-</caution>
-
-<para>
-When a table or index exceeds 1 GB, it is divided into gigabyte-sized
-<firstterm>segments</>.  The first segment's file name is the same as the
-filenode; subsequent segments are named filenode.1, filenode.2, etc.
-This arrangement avoids problems on platforms that have file size limitations.
-(Actually, 1 GB is just the default segment size.  The segment size can be
-adjusted using the configuration option <option>--with-segsize</option>
-when building <productname>PostgreSQL</>.)
-In principle, free space map and visibility map forks could require multiple
-segments as well, though this is unlikely to happen in practice.
-</para>
-
-<para>
-A table that has columns with potentially large entries will have an
-associated <firstterm>TOAST</> table, which is used for out-of-line storage of
-field values that are too large to keep in the table rows proper.
-<structname>pg_class</>.<structfield>reltoastrelid</> links from a table to
-its <acronym>TOAST</> table, if any.
-See <xref linkend="storage-toast"> for more information.
-</para>
-
-<para>
-The contents of tables and indexes are discussed further in
-<xref linkend="storage-page-layout">.
-</para>
-
-<para>
-Tablespaces make the scenario more complicated.  Each user-defined tablespace
-has a symbolic link inside the <varname>PGDATA</><filename>/pg_tblspc</>
-directory, which points to the physical tablespace directory (i.e., the
-location specified in the tablespace's <command>CREATE TABLESPACE</> command).
-This symbolic link is named after
-the tablespace's OID.  Inside the physical tablespace directory there is
-a subdirectory with a name that depends on the <productname>PostgreSQL</>
-server version, such as <literal>PG_9.0_201008051</>.  (The reason for using
-this subdirectory is so that successive versions of the database can use
-the same <command>CREATE TABLESPACE</> location value without conflicts.)
-Within the version-specific subdirectory, there is
-a subdirectory for each database that has elements in the tablespace, named
-after the database's OID.  Tables and indexes are stored within that
-directory, using the filenode naming scheme.
-The <literal>pg_default</> tablespace is not accessed through
-<filename>pg_tblspc</>, but corresponds to
-<varname>PGDATA</><filename>/base</>.  Similarly, the <literal>pg_global</>
-tablespace is not accessed through <filename>pg_tblspc</>, but corresponds to
-<varname>PGDATA</><filename>/global</>.
-</para>
-
-<para>
-The <function>pg_relation_filepath()</> function shows the entire path
-(relative to <varname>PGDATA</>) of any relation.  It is often useful
-as a substitute for remembering many of the above rules.  But keep in
-mind that this function just gives the name of the first segment of the
-main fork of the relation &mdash; you may need to append a segment number
-and/or <literal>_fsm</> or <literal>_vm</> to find all the files associated
-with the relation.
-</para>
-
-<para>
-Temporary files (for operations such as sorting more data than can fit in
-memory) are created within <varname>PGDATA</><filename>/base/pgsql_tmp</>,
-or within a <filename>pgsql_tmp</> subdirectory of a tablespace directory
-if a tablespace other than <literal>pg_default</> is specified for them.
-The name of a temporary file has the form
-<filename>pgsql_tmp<replaceable>PPP</>.<replaceable>NNN</></filename>,
-where <replaceable>PPP</> is the PID of the owning backend and
-<replaceable>NNN</> distinguishes different temporary files of that backend.
-</para>
-
-</sect1>
-
-<sect1 id="storage-toast">
-
-<title>TOAST</title>
-
-    <indexterm>
-     <primary>TOAST</primary>
-    </indexterm>
-    <indexterm><primary>sliced bread</><see>TOAST</></indexterm>
-
-&pgnotice;
-<para>
-This section provides an overview of <acronym>TOAST</> (The
-Oversized-Attribute Storage Technique).
-</para>
-
-<para>
-<productname>PostgreSQL</productname> uses a fixed page size (commonly
-8 kB), and does not allow tuples to span multiple pages.  Therefore,  it is
-not possible to store very large field values directly.  To overcome
-this limitation, large  field values are compressed and/or broken up into
-multiple physical rows. This happens transparently to the user, with only
-small impact on most of the backend code.  The technique is affectionately
-known as <acronym>TOAST</>  (or <quote>the best thing since sliced bread</>).
-</para>
-
-<para>
-Only certain data types support <acronym>TOAST</> &mdash; there is no need to
-impose the overhead on data types that cannot produce large field values.
-To support <acronym>TOAST</>, a data type must have a variable-length
-(<firstterm>varlena</>) representation, in which the first 32-bit word of any
-stored value contains the total length of the value in bytes (including
-itself).  <acronym>TOAST</> does not constrain the rest of the representation.
-All the C-level functions supporting a <acronym>TOAST</>-able data type must
-be careful to handle <acronym>TOAST</>ed input values.  (This is normally done
-by invoking <function>PG_DETOAST_DATUM</> before doing anything with an input
-value, but in some cases more efficient approaches are possible.)
-</para>
-
-<para>
-<acronym>TOAST</> usurps two bits of the varlena length word (the high-order
-bits on big-endian machines, the low-order bits on little-endian machines),
-thereby limiting the logical size of any value of a <acronym>TOAST</>-able
-data type to 1 GB (2<superscript>30</> - 1 bytes).  When both bits are zero,
-the value is an ordinary un-<acronym>TOAST</>ed value of the data type, and
-the remaining bits of the length word give the total datum size (including
-length word) in bytes.  When the highest-order or lowest-order bit is set,
-the value has only a single-byte header instead of the normal four-byte
-header, and the remaining bits give the total datum size (including length
-byte) in bytes.  As a special case, if the remaining bits are all zero
-(which would be impossible for a self-inclusive length), the value is a
-pointer to out-of-line data stored in a separate TOAST table.  (The size of
-a TOAST pointer is given in the second byte of the datum.)
-Values with single-byte headers aren't aligned on any particular
-boundary, either.  Lastly, when the highest-order or lowest-order bit is
-clear but the adjacent bit is set, the content of the datum has been
-compressed and must be decompressed before use.  In this case the remaining
-bits of the length word give the total size of the compressed datum, not the
-original data.  Note that compression is also possible for out-of-line data
-but the varlena header does not tell whether it has occurred &mdash;
-the content of the TOAST pointer tells that, instead.
-</para>
-
-<para>
-If any of the columns of a table are <acronym>TOAST</>-able, the table will
-have an associated <acronym>TOAST</> table, whose OID is stored in the table's
-<structname>pg_class</>.<structfield>reltoastrelid</> entry.  Out-of-line
-<acronym>TOAST</>ed values are kept in the <acronym>TOAST</> table, as
-described in more detail below.
-</para>
-
-<para>
-The compression technique used is a fairly simple and very fast member
-of the LZ family of compression techniques.  See
-<filename>src/backend/utils/adt/pg_lzcompress.c</> for the details.
-</para>
-
-<para>
-Out-of-line values are divided (after compression if used) into chunks of at
-most <symbol>TOAST_MAX_CHUNK_SIZE</> bytes (by default this value is chosen
-so that four chunk rows will fit on a page, making it about 2000 bytes).
-Each chunk is stored
-as a separate row in the <acronym>TOAST</> table for the owning table.  Every
-<acronym>TOAST</> table has the columns <structfield>chunk_id</> (an OID
-identifying the particular <acronym>TOAST</>ed value),
-<structfield>chunk_seq</> (a sequence number for the chunk within its value),
-and <structfield>chunk_data</> (the actual data of the chunk).  A unique index
-on <structfield>chunk_id</> and <structfield>chunk_seq</> provides fast
-retrieval of the values.  A pointer datum representing an out-of-line
-<acronym>TOAST</>ed value therefore needs to store the OID of the
-<acronym>TOAST</> table in which to look and the OID of the specific value
-(its <structfield>chunk_id</>).  For convenience, pointer datums also store the
-logical datum size (original uncompressed data length) and actual stored size
-(different if compression was applied).  Allowing for the varlena header bytes,
-the total size of a <acronym>TOAST</> pointer datum is therefore 18 bytes
-regardless of the actual size of the represented value.
-</para>
-
-<para>
-The <acronym>TOAST</> code is triggered only
-when a row value to be stored in a table is wider than
-<symbol>TOAST_TUPLE_THRESHOLD</> bytes (normally 2 kB).
-The <acronym>TOAST</> code will compress and/or move
-field values out-of-line until the row value is shorter than
-<symbol>TOAST_TUPLE_TARGET</> bytes (also normally 2 kB)
-or no more gains can be had.  During an UPDATE
-operation, values of unchanged fields are normally preserved as-is; so an
-UPDATE of a row with out-of-line values incurs no <acronym>TOAST</> costs if
-none of the out-of-line values change.
-</para>
-
-<para>
-The <acronym>TOAST</> code recognizes four different strategies for storing
-<acronym>TOAST</>-able columns:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <literal>PLAIN</literal> prevents either compression or
-      out-of-line storage; furthermore it disables use of single-byte headers
-      for varlena types.
-      This is the only possible strategy for
-      columns of non-<acronym>TOAST</>-able data types.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>EXTENDED</literal> allows both compression and out-of-line
-      storage.  This is the default for most <acronym>TOAST</>-able data types.
-      Compression will be attempted first, then out-of-line storage if
-      the row is still too big.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>EXTERNAL</literal> allows out-of-line storage but not
-      compression.  Use of <literal>EXTERNAL</literal> will
-      make substring operations on wide <type>text</type> and
-      <type>bytea</type> columns faster (at the penalty of increased storage
-      space) because these operations are optimized to fetch only the
-      required parts of the out-of-line value when it is not compressed.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>MAIN</literal> allows compression but not out-of-line
-      storage.  (Actually, out-of-line storage will still be performed
-      for such columns, but only as a last resort when there is no other
-      way to make the row small enough to fit on a page.)
-     </para>
-    </listitem>
-   </itemizedlist>
-
-Each <acronym>TOAST</>-able data type specifies a default strategy for columns
-of that data type, but the strategy for a given table column can be altered
-with <command>ALTER TABLE SET STORAGE</>.
-</para>
-
-<para>
-This scheme has a number of advantages compared to a more straightforward
-approach such as allowing row values to span pages.  Assuming that queries are
-usually qualified by comparisons against relatively small key values, most of
-the work of the executor will be done using the main row entry. The big values
-of <acronym>TOAST</>ed attributes will only be pulled out (if selected at all)
-at the time the result set is sent to the client. Thus, the main table is much
-smaller and more of its rows fit in the shared buffer cache than would be the
-case without any out-of-line storage. Sort sets shrink also, and sorts will
-more often be done entirely in memory. A little test showed that a table
-containing typical HTML pages and their URLs was stored in about half of the
-raw data size including the <acronym>TOAST</> table, and that the main table
-contained only about 10% of the entire data (the URLs and some small HTML
-pages). There was no run time difference compared to an un-<acronym>TOAST</>ed
-comparison table, in which all the HTML pages were cut down to 7 kB to fit.
-</para>
-
-</sect1>
-
-<sect1 id="storage-fsm">
-
-<title>Free Space Map</title>
-
-<indexterm>
- <primary>Free Space Map</primary>
-</indexterm>
-<indexterm><primary>FSM</><see>Free Space Map</></indexterm>
-
-&pgnotice;
-<para>
-Each heap and index relation, except for hash indexes, has a Free Space Map
-(FSM) to keep track of available space in the relation. It's stored
-alongside the main relation data in a separate relation fork, named after the
-filenode number of the relation, plus a <literal>_fsm</> suffix. For example,
-if the filenode of a relation is 12345, the FSM is stored in a file called
-<filename>12345_fsm</>, in the same directory as the main relation file.
-</para>
-
-<para>
-The Free Space Map is organized as a tree of <acronym>FSM</> pages. The
-bottom level <acronym>FSM</> pages store the free space available on each
-heap (or index) page, using one byte to represent each such page. The upper
-levels aggregate information from the lower levels.
-</para>
-
-<para>
-Within each <acronym>FSM</> page is a binary tree, stored in an array with
-one byte per node. Each leaf node represents a heap page, or a lower level
-<acronym>FSM</> page. In each non-leaf node, the higher of its children's
-values is stored. The maximum value in the leaf nodes is therefore stored
-at the root.
-</para>
-
-<para>
-See <filename>src/backend/storage/freespace/README</> for more details on
-how the <acronym>FSM</> is structured, and how it's updated and searched.
-The <xref linkend="pgfreespacemap"> module
-can be used to examine the information stored in free space maps.
-</para>
-
-</sect1>
-
-<sect1 id="storage-vm">
-
-<title>Visibility Map</title>
-
-<indexterm>
- <primary>Visibility Map</primary>
-</indexterm>
-<indexterm><primary>VM</><see>Visibility Map</></indexterm>
-
-&pgnotice;
-<para>
-Each heap relation has a Visibility Map
-(VM) to keep track of which pages contain only tuples that are known to be
-visible to all active transactions. It's stored
-alongside the main relation data in a separate relation fork, named after the
-filenode number of the relation, plus a <literal>_vm</> suffix. For example,
-if the filenode of a relation is 12345, the VM is stored in a file called
-<filename>12345_vm</>, in the same directory as the main relation file.
-Note that indexes do not have VMs.
-</para>
-
-<para>
-The visibility map simply stores one bit per heap page. A set bit means
-that all tuples on the page are known to be visible to all transactions.
-This means that the page does not contain any tuples that need to be vacuumed;
-in future it might also be used to avoid visiting the page for visibility
-checks. The map is conservative in the sense that we
-make sure that whenever a bit is set, we know the condition is true, but if
-a bit is not set, it might or might not be true.
-</para>
-
-</sect1>
-
-<sect1 id="storage-init">
-
-<title>The Initialization Fork</title>
-
-<indexterm>
- <primary>Initialization Fork</primary>
-</indexterm>
-
-<para>
-Each unlogged table, and each index on an unlogged table, has an initialization
-fork.  The initialization fork is an empty table or index of the appropriate
-type.  When an unlogged table must be reset to empty due to a crash, the
-initialization fork is copied over the main fork, and any other forks are
-erased (they will be recreated automatically as needed).
-</para>
-
-</sect1>
-
-<sect1 id="storage-page-layout">
-
-<title>Database Page Layout</title>
-
-&pgnotice;
-<para>
-This section provides an overview of the page format used within
-<productname>PostgreSQL</productname> tables and indexes.<footnote>
-  <para>
-    Actually, index access methods need not use this page format.
-    All the existing index methods do use this basic format,
-    but the data kept on index metapages usually doesn't follow
-    the item layout rules.
-  </para>
-</footnote>
-Sequences and <acronym>TOAST</> tables are formatted just like a regular table.
-</para>
-
-<para>
-In the following explanation, a
-<firstterm>byte</firstterm>
-is assumed to contain 8 bits.  In addition, the term
-<firstterm>item</firstterm>
-refers to an individual data value that is stored on a page.  In a table,
-an item is a row; in an index, an item is an index entry.
-</para>
-
-<para>
-Every table and index is stored as an array of <firstterm>pages</> of a
-fixed size (usually 8 kB, although a different page size can be selected
-when compiling the server).  In a table, all the pages are logically
-equivalent, so a particular item (row) can be stored in any page.  In
-indexes, the first page is generally reserved as a <firstterm>metapage</>
-holding control information, and there can be different types of pages
-within the index, depending on the index access method.
-</para>
-
-<para>
-<xref linkend="page-table"> shows the overall layout of a page.
-There are five parts to each page.
-</para>
-
-<table tocentry="1" id="page-table">
-<title>Overall Page Layout</title>
-<titleabbrev>Page Layout</titleabbrev>
-<tgroup cols="2">
-<thead>
-<row>
-<entry>
-Item
-</entry>
-<entry>Description</entry>
-</row>
-</thead>
-
-<tbody>
-
-<row>
- <entry>PageHeaderData</entry>
- <entry>24 bytes long. Contains general information about the page, including
-free space pointers.</entry>
-</row>
-
-<row>
-<entry>ItemIdData</entry>
-<entry>Array of (offset,length) pairs pointing to the actual items.
-4 bytes per item.</entry>
-</row>
-
-<row>
-<entry>Free space</entry>
-<entry>The unallocated space. New item pointers are allocated from the start
-of this area, new items from the end.</entry>
-</row>
-
-<row>
-<entry>Items</entry>
-<entry>The actual items themselves.</entry>
-</row>
-
-<row>
-<entry>Special space</entry>
-<entry>Index access method specific data. Different methods store different
-data. Empty in ordinary tables.</entry>
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
- <para>
-
-  The first 24 bytes of each page consists of a page header
-  (PageHeaderData). Its format is detailed in <xref
-  linkend="pageheaderdata-table">. The first two fields track the most
-  recent WAL entry related to this page. Next is a 2-byte field
-  containing flag bits. This is followed by three 2-byte integer fields
-  (<structfield>pd_lower</structfield>, <structfield>pd_upper</structfield>,
-  and <structfield>pd_special</structfield>). These contain byte offsets
-  from the page start to the start
-  of unallocated space, to the end of unallocated space, and to the start of
-  the special space.
-  The next 2 bytes of the page header,
-  <structfield>pd_pagesize_version</structfield>, store both the page size
-  and a version indicator.  Beginning with
-  <productname>PostgreSQL</productname> 8.3 the version number is 4;
-  <productname>PostgreSQL</productname> 8.1 and 8.2 used version number 3;
-  <productname>PostgreSQL</productname> 8.0 used version number 2;
-  <productname>PostgreSQL</productname> 7.3 and 7.4 used version number 1;
-  prior releases used version number 0.
-  (The basic page layout and header format has not changed in most of these
-  versions, but the layout of heap row headers has.)  The page size
-  is basically only present as a cross-check; there is no support for having
-  more than one page size in an installation.
-  The last field is a hint that shows whether pruning the page is likely
-  to be profitable: it tracks the oldest un-pruned XMAX on the page.
-
- </para>
-
- <table tocentry="1" id="pageheaderdata-table">
- <title>PageHeaderData Layout</title>
- <titleabbrev>PageHeaderData Layout</titleabbrev>
- <tgroup cols="4">
- <thead>
-  <row>
-   <entry>Field</entry>
-   <entry>Type</entry>
-   <entry>Length</entry>
-   <entry>Description</entry>
-  </row>
- </thead>
- <tbody>
-  <row>
-   <entry>pd_lsn</entry>
-   <entry>XLogRecPtr</entry>
-   <entry>8 bytes</entry>
-   <entry>LSN: next byte after last byte of xlog record for last change
-   to this page</entry>
-  </row>
-  <row>
-   <entry>pd_tli</entry>
-   <entry>uint16</entry>
-   <entry>2 bytes</entry>
-   <entry>TimeLineID of last change (only its lowest 16 bits)</entry>
-  </row>
-  <row>
-   <entry>pd_flags</entry>
-   <entry>uint16</entry>
-   <entry>2 bytes</entry>
-   <entry>Flag bits</entry>
-  </row>
-  <row>
-   <entry>pd_lower</entry>
-   <entry>LocationIndex</entry>
-   <entry>2 bytes</entry>
-   <entry>Offset to start of free space</entry>
-  </row>
-  <row>
-   <entry>pd_upper</entry>
-   <entry>LocationIndex</entry>
-   <entry>2 bytes</entry>
-   <entry>Offset to end of free space</entry>
-  </row>
-  <row>
-   <entry>pd_special</entry>
-   <entry>LocationIndex</entry>
-   <entry>2 bytes</entry>
-   <entry>Offset to start of special space</entry>
-  </row>
-  <row>
-   <entry>pd_pagesize_version</entry>
-   <entry>uint16</entry>
-   <entry>2 bytes</entry>
-   <entry>Page size and layout version number information</entry>
-  </row>
-  <row>
-   <entry>pd_prune_xid</entry>
-   <entry>TransactionId</entry>
-   <entry>4 bytes</entry>
-   <entry>Oldest unpruned XMAX on page, or zero if none</entry>
-  </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
-  All the details can be found in
-  <filename>src/include/storage/bufpage.h</filename>.
- </para>
-
- <para>
-
-  Following the page header are item identifiers
-  (<type>ItemIdData</type>), each requiring four bytes.
-  An item identifier contains a byte-offset to
-  the start of an item, its length in bytes, and a few attribute bits
-  which affect its interpretation.
-  New item identifiers are allocated
-  as needed from the beginning of the unallocated space.
-  The number of item identifiers present can be determined by looking at
-  <structfield>pd_lower</>, which is increased to allocate a new identifier.
-  Because an item
-  identifier is never moved until it is freed, its index can be used on a
-  long-term basis to reference an item, even when the item itself is moved
-  around on the page to compact free space.  In fact, every pointer to an
-  item (<type>ItemPointer</type>, also known as
-  <type>CTID</type>) created by
-  <productname>PostgreSQL</productname> consists of a page number and the
-  index of an item identifier.
-
- </para>
-
- <para>
-
-  The items themselves are stored in space allocated backwards from the end
-  of unallocated space.  The exact structure varies depending on what the
-  table is to contain. Tables and sequences both use a structure named
-  <type>HeapTupleHeaderData</type>, described below.
-
- </para>
-
- <para>
-
-  The final section is the <quote>special section</quote> which can
- contain anything the access method wishes to store.  For example,
-  b-tree indexes store links to the page's left and right siblings,
-  as well as some other data relevant to the index structure.
-  Ordinary tables do not use a special section at all (indicated by setting
-  <structfield>pd_special</> to equal the page size).
-
- </para>
-
- <para>
-
-  All table rows are structured in the same way. There is a fixed-size
-  header (occupying 23 bytes on most machines), followed by an optional null
-  bitmap, an optional object ID field, and the user data. The header is
-  detailed
-  in <xref linkend="heaptupleheaderdata-table">.  The actual user data
-  (columns of the row) begins at the offset indicated by
-  <structfield>t_hoff</>, which must always be a multiple of the MAXALIGN
-  distance for the platform.
-  The null bitmap is
-  only present if the <firstterm>HEAP_HASNULL</firstterm> bit is set in
-  <structfield>t_infomask</structfield>. If it is present it begins just after
-  the fixed header and occupies enough bytes to have one bit per data column
-  (that is, <structfield>t_natts</> bits altogether). In this list of bits, a
-  1 bit indicates not-null, a 0 bit is a null.  When the bitmap is not
-  present, all columns are assumed not-null.
-  The object ID is only present if the <firstterm>HEAP_HASOID</firstterm> bit
-  is set in <structfield>t_infomask</structfield>.  If present, it appears just
-  before the <structfield>t_hoff</> boundary.  Any padding needed to make
-  <structfield>t_hoff</> a MAXALIGN multiple will appear between the null
-  bitmap and the object ID.  (This in turn ensures that the object ID is
-  suitably aligned.)
-
- </para>
-
- <table tocentry="1" id="heaptupleheaderdata-table">
- <title>HeapTupleHeaderData Layout</title>
- <titleabbrev>HeapTupleHeaderData Layout</titleabbrev>
- <tgroup cols="4">
- <thead>
-  <row>
-   <entry>Field</entry>
-   <entry>Type</entry>
-   <entry>Length</entry>
-   <entry>Description</entry>
-  </row>
- </thead>
- <tbody>
-  <row>
-   <entry>t_xmin</entry>
-   <entry>TransactionId</entry>
-   <entry>4 bytes</entry>
-   <entry>insert XID stamp</entry>
-  </row>
-  <row>
-   <entry>t_xmax</entry>
-   <entry>TransactionId</entry>
-   <entry>4 bytes</entry>
-   <entry>delete XID stamp</entry>
-  </row>
-  <row>
-   <entry>t_cid</entry>
-   <entry>CommandId</entry>
-   <entry>4 bytes</entry>
-   <entry>insert and/or delete CID stamp (overlays with t_xvac)</entry>
-  </row>
-  <row>
-   <entry>t_xvac</entry>
-   <entry>TransactionId</entry>
-   <entry>4 bytes</entry>
-   <entry>XID for VACUUM operation moving a row version</entry>
-  </row>
-  <row>
-   <entry>t_ctid</entry>
-   <entry>ItemPointerData</entry>
-   <entry>6 bytes</entry>
-   <entry>current TID of this or newer row version</entry>
-  </row>
-  <row>
-   <entry>t_infomask2</entry>
-   <entry>int16</entry>
-   <entry>2 bytes</entry>
-   <entry>number of attributes, plus various flag bits</entry>
-  </row>
-  <row>
-   <entry>t_infomask</entry>
-   <entry>uint16</entry>
-   <entry>2 bytes</entry>
-   <entry>various flag bits</entry>
-  </row>
-  <row>
-   <entry>t_hoff</entry>
-   <entry>uint8</entry>
-   <entry>1 byte</entry>
-   <entry>offset to user data</entry>
-  </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
-   All the details can be found in
-   <filename>src/include/access/htup.h</filename>.
- </para>
-
- <para>
-
-  Interpreting the actual data can only be done with information obtained
-  from other tables, mostly <structname>pg_attribute</structname>. The
-  key values needed to identify field locations are
-  <structfield>attlen</structfield> and <structfield>attalign</structfield>.
-  There is no way to directly get a
-  particular attribute, except when there are only fixed width fields and no
-  null values. All this trickery is wrapped up in the functions
-  <firstterm>heap_getattr</firstterm>, <firstterm>fastgetattr</firstterm>
-  and <firstterm>heap_getsysattr</firstterm>.
-
- </para>
- <para>
-
-  To read the data you need to examine each attribute in turn. First check
-  whether the field is NULL according to the null bitmap. If it is, go to
-  the next. Then make sure you have the right alignment.  If the field is a
-  fixed width field, then all the bytes are simply placed. If it's a
-  variable length field (attlen = -1) then it's a bit more complicated.
-  All variable-length data types share the common header structure
-  <type>struct varlena</type>, which includes the total length of the stored
-  value and some flag bits.  Depending on the flags, the data can be either
-  inline or in a <acronym>TOAST</> table;
-  it might be compressed, too (see <xref linkend="storage-toast">).
-
- </para>
-</sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/stylesheet-common.xsl b/doc-xc/src/sgml/stylesheet-common.xsl
deleted file mode 100644
index 2ad0a7f1ca..0000000000
--- a/doc-xc/src/sgml/stylesheet-common.xsl
+++ /dev/null
@@ -1,88 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                version="1.0">
-
-<!--
-  This file contains XSLT stylesheet customizations that are common to
-  all output formats (HTML, HTML Help, XSL-FO, etc.).
-  -->
-
-
-<!-- Parameters -->
-
-<xsl:param name="pg.fast" select="'0'"/>
-
-<!--
-<xsl:param name="draft.mode">
-  <xsl:choose>
-    <xsl:when test="contains($pg.version, 'devel')">yes</xsl:when>
-    <xsl:otherwise>no</xsl:otherwise>
-  </xsl:choose>
-</xsl:param>
--->
-
-<xsl:param name="show.comments">
-  <xsl:choose>
-    <xsl:when test="contains($pg.version, 'devel')">1</xsl:when>
-    <xsl:otherwise>0</xsl:otherwise>
-  </xsl:choose>
-</xsl:param>
-
-<xsl:param name="callout.graphics" select="'0'"></xsl:param>
-<xsl:param name="toc.section.depth">2</xsl:param>
-<xsl:param name="linenumbering.extension" select="'0'"></xsl:param>
-<xsl:param name="generate.index" select="1 - $pg.fast"></xsl:param>
-<xsl:param name="preface.autolabel" select="1 - $pg.fast"></xsl:param>
-<xsl:param name="section.autolabel" select="1 - $pg.fast"></xsl:param>
-<xsl:param name="section.label.includes.component.label" select="1 - $pg.fast"></xsl:param>
-<xsl:param name="refentry.xref.manvolnum" select="0"/>
-<xsl:param name="formal.procedures" select="0"></xsl:param>
-<xsl:param name="punct.honorific" select="''"></xsl:param>
-
-
-<!-- Change display of some elements -->
-
-<xsl:template match="command">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="productname">
-  <xsl:call-template name="inline.charseq"/>
-</xsl:template>
-
-<xsl:template match="structfield">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="structname">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="symbol">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="systemitem">
-  <xsl:call-template name="inline.charseq"/>
-</xsl:template>
-
-<xsl:template match="token">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="type">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="programlisting/emphasis">
-  <xsl:call-template name="inline.boldseq"/>
-</xsl:template>
-
-
-<!-- Special support for Tcl synopses -->
-
-<xsl:template match="optional[@role='tcl']">
-  ?<xsl:call-template name="inline.charseq"/>?
-</xsl:template>
-
-</xsl:stylesheet>
diff --git a/doc-xc/src/sgml/stylesheet-fo.xsl b/doc-xc/src/sgml/stylesheet-fo.xsl
deleted file mode 100644
index d982a3c46a..0000000000
--- a/doc-xc/src/sgml/stylesheet-fo.xsl
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                version="1.0"
-                xmlns:fo="http://www.w3.org/1999/XSL/Format">
-
-<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl"/>
-<xsl:include href="stylesheet-common.xsl" />
-
-</xsl:stylesheet>
diff --git a/doc-xc/src/sgml/stylesheet-hh.xsl b/doc-xc/src/sgml/stylesheet-hh.xsl
deleted file mode 100644
index 1c50518c70..0000000000
--- a/doc-xc/src/sgml/stylesheet-hh.xsl
+++ /dev/null
@@ -1,35 +0,0 @@
-<?xml version='1.0'?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                version='1.0'
-                xmlns="http://www.w3.org/TR/xhtml1/transitional"
-                exclude-result-prefixes="#default">
-
-<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/htmlhelp/htmlhelp.xsl"/>
-<xsl:include href="stylesheet-common.xsl" />
-
-<!-- Parameters -->
-<xsl:param name="htmlhelp.use.hhk" select="'1'"/>
-
-<xsl:param name="html.stylesheet" select="'stylesheet.css'"></xsl:param>
-<xsl:param name="use.id.as.filename" select="'1'"></xsl:param>
-<xsl:param name="make.valid.html" select="1"></xsl:param>
-<xsl:param name="generate.id.attributes" select="1"></xsl:param>
-<xsl:param name="generate.legalnotice.link" select="1"></xsl:param>
-<xsl:param name="link.mailto.url">[email protected]</xsl:param>
-<xsl:param name="chunker.output.indent" select="'yes'"/>
-<xsl:param name="chunk.quietly" select="1"></xsl:param>
-
-
-<!--
-  Format multiple terms in varlistentry vertically, instead
-  of comma-separated.
- -->
-
-<xsl:template match="varlistentry/term[position()!=last()]">
-  <span class="term">
-    <xsl:call-template name="anchor"/>
-    <xsl:apply-templates/>
-  </span><br/>
-</xsl:template>
-
-</xsl:stylesheet>
diff --git a/doc-xc/src/sgml/stylesheet-man.xsl b/doc-xc/src/sgml/stylesheet-man.xsl
deleted file mode 100644
index 8c614ca754..0000000000
--- a/doc-xc/src/sgml/stylesheet-man.xsl
+++ /dev/null
@@ -1,203 +0,0 @@
-<?xml version='1.0'?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-		xmlns:exsl="http://exslt.org/common"
-                version='1.0'
-                exclude-result-prefixes="exsl">
-
-<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"/>
-<xsl:import href="stylesheet-common.xsl" />
-
-
-<!-- The following is a workaround for what may actually be a mistake
-     in our markup.  The problem is in a situation like
-
-<para>
- <command>FOO</command> is ...
-
-     there is strictly speaking a line break before "FOO".  In the
-     HTML output, this does not appear to be a problem, but in the man
-     page output, this shows up.  Using this setting, pure whitespace
-     text nodes are removed, so the problem is solved. -->
-<xsl:strip-space elements="para"/>
-
-
-<!-- Parameters -->
-
-<xsl:param name="man.authors.section.enabled">0</xsl:param>
-<xsl:param name="man.copyright.section.enabled">0</xsl:param>
-<xsl:param name="man.output.base.dir"></xsl:param>
-<xsl:param name="man.output.in.separate.dir" select="1"></xsl:param>
-<xsl:param name="refentry.meta.get.quietly" select="0"></xsl:param>
-<xsl:param name="man.th.title.max.length">32</xsl:param> <!-- enough room for "CREATE TEXT SEARCH CONFIGURATION" -->
-<xsl:param name="man.th.extra3.max.length">40</xsl:param> <!-- enough room for "PostgreSQL X.Ydevel Documentation" -->
-<xsl:param name="refentry.xref.manvolnum" select="1"/> <!-- overridden from stylesheet-common.xsl -->
-
-<!-- Fixup for apostrophe groff output.  See the following references:
-     <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457839>
-     <https://sourceforge.net/tracker/?func=detail&aid=2412738&group_id=21935&atid=373747>
- -->
-<xsl:param name="man.string.subst.map.local.post">
-  <substitution oldstring="\'" newstring="\(aq"></substitution>
-</xsl:param>
-
-
-<!-- Custom templates -->
-
-<xsl:template match="refentry" mode="xref-to">
-  <xsl:param name="referrer"/>
-  <xsl:param name="xrefstyle"/>
-
-  <xsl:choose>
-    <!-- If the refname contains a space, we construct a reference
-         like CREATE DATABASE (CREATE_DATABASE(7)), so the reader
-         knows both the command name being referred to and the name of
-         the man page to read about it. -->
-    <xsl:when test="contains(refnamediv/refname[1],' ')">
-      <xsl:variable name="mangled.title">
-       <xsl:value-of select="translate(refnamediv/refname[1],' ','_')"/>
-      </xsl:variable>
-      <xsl:apply-templates select="refnamediv/refname[1]"/>
-      <xsl:text> (</xsl:text>
-      <xsl:call-template name="bold">
-       <xsl:with-param name="node" select="exsl:node-set($mangled.title)"/>
-       <xsl:with-param name="context" select="."/>
-      </xsl:call-template>
-      <xsl:apply-templates select="refmeta/manvolnum"/>
-      <xsl:text>)</xsl:text>
-    </xsl:when>
-
-    <!-- This is the original case, except that boldness has been
-         added, per the convention mentioned in man-pages(7). -->
-    <xsl:otherwise>
-      <xsl:choose>
-        <xsl:when test="refmeta/refentrytitle">
-	 <xsl:call-template name="bold">
-	  <xsl:with-param name="node" select="refmeta/refentrytitle"/>
-	  <xsl:with-param name="context" select="."/>
-	 </xsl:call-template>
-        </xsl:when>
-        <xsl:otherwise>
-	 <xsl:call-template name="bold">
-	  <xsl:with-param name="node" select="refnamediv/refname[1]"/>
-	  <xsl:with-param name="context" select="."/>
-	 </xsl:call-template>
-        </xsl:otherwise>
-      </xsl:choose>
-      <xsl:apply-templates select="refmeta/manvolnum"/>
-    </xsl:otherwise>
-  </xsl:choose>
-
-</xsl:template>
-
-
-<!-- For refentries we don't man to generate a man page for, leave out
-     manvolnum, let it default to 0, and skip writing out man files
-     with section 0. -->
-
-<!-- overridden from common/refentry.xsl -->
-<xsl:template name="get.refentry.section">
-  <xsl:choose>
-    <xsl:when test="refmeta/manvolnum">
-      <xsl:value-of select="refmeta/manvolnum"/>
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:text>0</xsl:text>
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-<!-- overridden from manpages/other.xsl -->
-  <xsl:template name="write.man.file">
-    <xsl:param name="name"/>
-    <xsl:param name="section"/>
-    <xsl:param name="lang"/>
-    <xsl:param name="content"/>
-    <xsl:param name="filename">
-      <xsl:call-template name="make.adjusted.man.filename">
-        <xsl:with-param name="name" select="$name"/>
-        <xsl:with-param name="section" select="$section"/>
-        <xsl:with-param name="lang" select="$lang"/>
-      </xsl:call-template>
-    </xsl:param>
-    <xsl:if test="$section != 0">
-    <xsl:call-template name="write.text.chunk">
-      <xsl:with-param name="filename" select="$filename"/>
-      <xsl:with-param name="suppress-context-node-name" select="1"/>
-      <xsl:with-param name="quiet" select="$man.output.quietly"/>
-      <xsl:with-param
-          name="message-prolog"
-          >Note: </xsl:with-param>
-      <xsl:with-param name="encoding" select="$man.output.encoding"/>
-      <xsl:with-param name="content" select="$content"/>
-    </xsl:call-template>
-    </xsl:if>
-  </xsl:template>
-
-
-<!-- Overridden template as workaround for this problem:
-     <https://sourceforge.net/tracker/?func=detail&aid=2831602&group_id=21935&atid=373747>
--->
-  <xsl:template name="write.stubs">
-    <xsl:param name="first.refname"/>
-    <xsl:param name="section"/>
-    <xsl:param name="lang"/>
-    <xsl:for-each select="refnamediv/refname">
-      <xsl:if test=". != $first.refname">
-        <xsl:call-template name="write.text.chunk">
-          <xsl:with-param name="filename">
-            <xsl:call-template name="make.adjusted.man.filename">
-              <xsl:with-param name="name" select="."/>
-              <xsl:with-param name="section" select="$section"/>
-              <xsl:with-param name="lang" select="$lang"/>
-            </xsl:call-template>
-          </xsl:with-param>
-          <xsl:with-param name="quiet" select="$man.output.quietly"/>
-          <xsl:with-param name="suppress-context-node-name" select="1"/>
-          <xsl:with-param name="message-prolog">Note: </xsl:with-param>
-          <xsl:with-param name="message-epilog"> (soelim stub)</xsl:with-param>
-          <xsl:with-param name="content">
-	    <xsl:choose>
-	      <xsl:when test="$man.output.in.separate.dir = 0">
-		<xsl:value-of select="concat('.so man', $section, '/')"/>
-	      </xsl:when>
-	      <xsl:otherwise>
-		<xsl:value-of select="'.so '"/> <!-- added case -->
-	      </xsl:otherwise>
-	    </xsl:choose>
-            <xsl:call-template name="make.adjusted.man.filename">
-              <xsl:with-param name="name" select="$first.refname"/>
-              <xsl:with-param name="section" select="$section"/>
-            </xsl:call-template>
-            <xsl:text>&#10;</xsl:text>
-          </xsl:with-param>
-        </xsl:call-template>
-      </xsl:if>
-    </xsl:for-each>
-  </xsl:template>
-
-
-<!-- Gentext customization -->
-
-<!-- see http://www.sagehill.net/docbookxsl/CustomGentext.html -->
-<xsl:param name="local.l10n.xml" select="document('')"/>
-<l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
-  <l:l10n language="en">
-    <!-- Use ISO 8601 date format. -->
-    <l:context name="datetime">
-      <l:template name="format" text="Y-m-d"/>
-    </l:context>
-
-    <!-- Slight rephrasing to indicate that missing sections are found
-         in the documentation. -->
-    <l:context name="xref-number-and-title">
-      <l:template name="chapter" text="Chapter %n, %t, in the documentation"/>
-      <l:template name="sect1" text="Section %n, “%t”, in the documentation"/>
-      <l:template name="sect2" text="Section %n, “%t”, in the documentation"/>
-      <l:template name="sect3" text="Section %n, “%t”, in the documentation"/>
-      <l:template name="sect4" text="Section %n, “%t”, in the documentation"/>
-      <l:template name="sect5" text="Section %n, “%t”, in the documentation"/>
-    </l:context>
-  </l:l10n>
-</l:i18n>
-
-</xsl:stylesheet>
diff --git a/doc-xc/src/sgml/stylesheet.css b/doc-xc/src/sgml/stylesheet.css
deleted file mode 100644
index 0fd0f01782..0000000000
--- a/doc-xc/src/sgml/stylesheet.css
+++ /dev/null
@@ -1,96 +0,0 @@
-/* doc/src/sgml/stylesheet.css */
-
-/* color scheme similar to www.postgresql.org */
-
-BODY {
-	color: #000000;
-	background: #FFFFFF;
-	font-family: verdana, sans-serif;
-}
-
-A:link		{ color:#0066A2; }
-A:visited	{ color:#004E66; }
-A:active	{ color:#0066A2; }
-A:hover		{ color:#000000; }
-
-H1 {
-	font-size: 1.4em;
-	font-weight: bold;
-	margin-top: 0em;
-	margin-bottom: 0em;
-	color: #EC5800;
-}
-
-H2 {
-	font-size: 1.2em;
-	margin: 1.2em 0em 1.2em 0em;
-	font-weight: bold;
-	color: #666;
-}
-
-H3 {
-	font-size: 1.1em;
-	margin: 1.2em 0em 1.2em 0em;
-	font-weight: bold;
-	color: #666;
-}
-
-H4 {
-	font-size: 0.95em;
-	margin: 1.2em 0em 1.2em 0em;
-	font-weight: normal;
-	color: #666;
-}
-
-H5 {
-	font-size: 0.9em;
-	margin: 1.2em 0em 1.2em 0em;
-	font-weight: normal;
-}
-
-H6 {
-	font-size: 0.85em;
-	margin: 1.2em 0em 1.2em 0em;
-	font-weight: normal;
-}
-
-/* center some titles */
-
-.BOOK .TITLE, .BOOK .CORPAUTHOR, .BOOK .COPYRIGHT {
-	text-align: center;
-}
-
-/* decoration for formal examples */
-
-DIV.EXAMPLE {
-	padding-left: 15px;
-	border-style: solid;
-	border-width: 0px;
-	border-left-width: 2px;
-	border-color: black;
-	margin: 0.5ex;
-}
-
-/* less dense spacing of TOC */
-
-.BOOK .TOC DL DT {
-	padding-top: 1.5ex;
-	padding-bottom: 1.5ex;
-}
-
-.BOOK .TOC DL DL DT {
-	padding-top: 0ex;
-	padding-bottom: 0ex;
-}
-
-/* miscellaneous */
-
-PRE.LITERALLAYOUT, .SCREEN, .SYNOPSIS, .PROGRAMLISTING {
-	margin-left: 4ex;
-}
-
-.COMMENT	{ color: red; }
-
-VAR		{ font-family: monospace; font-style: italic; }
-/* Konqueror's standard style for ACRONYM is italic. */
-ACRONYM		{ font-style: inherit; }
diff --git a/doc-xc/src/sgml/stylesheet.dsl b/doc-xc/src/sgml/stylesheet.dsl
deleted file mode 100644
index 637758ff42..0000000000
--- a/doc-xc/src/sgml/stylesheet.dsl
+++ /dev/null
@@ -1,871 +0,0 @@
-<!-- doc/src/sgml/stylesheet.dsl -->
-<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [
-
-<!-- must turn on one of these with -i on the jade command line -->
-<!ENTITY % output-html          "IGNORE">
-<!ENTITY % output-print         "IGNORE">
-<!ENTITY % output-text          "IGNORE">
-
-<![ %output-html; [
-<!ENTITY dbstyle PUBLIC "-//Norman Walsh//DOCUMENT DocBook HTML Stylesheet//EN" CDATA DSSSL>
-]]>
-
-<![ %output-print; [
-<!ENTITY dbstyle PUBLIC "-//Norman Walsh//DOCUMENT DocBook Print Stylesheet//EN" CDATA DSSSL>
-]]>
-
-<![ %output-text; [
-<!ENTITY dbstyle PUBLIC "-//Norman Walsh//DOCUMENT DocBook HTML Stylesheet//EN" CDATA DSSSL>
-]]>
-
-]>
-
-<style-sheet>
- <style-specification use="docbook">
-  <style-specification-body>
-
-<!-- general customization ......................................... -->
-
-<!-- (applicable to all output formats) -->
-
-(define draft-mode              #f)
-
-(define pgsql-docs-list "[email protected]")
-
-;; Don't show manpage volume numbers
-(define %refentry-xref-manvolnum% #f)
-
-;; Don't use graphics for callouts.  (We could probably do that, but
-;; it needs extra work.)
-(define %callout-graphics%      #f)
-
-;; Show comments during the development stage.
-(define %show-comments%         draft-mode)
-
-;; Don't append period if run-in title ends with any of these
-;; characters.  We had to add the colon here.  This is fixed in
-;; stylesheets version 1.71, so it can be removed sometime.
-(define %content-title-end-punct%
-  '(#\. #\! #\? #\:))
-
-;; No automatic punctuation after honorific name parts
-(define %honorific-punctuation% "")
-
-;; Change display of some elements
-(element command ($mono-seq$))
-(element envar ($mono-seq$))
-(element lineannotation ($italic-seq$))
-(element literal ($mono-seq$))
-(element option ($mono-seq$))
-(element parameter ($mono-seq$))
-(element structfield ($mono-seq$))
-(element structname ($mono-seq$))
-(element symbol ($mono-seq$))
-(element token ($mono-seq$))
-(element type ($mono-seq$))
-(element varname ($mono-seq$))
-(element (programlisting emphasis) ($bold-seq$)) ;; to highlight sections of code
-
-;; Special support for Tcl synopses
-(element optional
-  (if (equal? (attribute-string (normalize "role")) "tcl")
-      (make sequence
-        (literal "?")
-        ($charseq$)
-        (literal "?"))
-      (make sequence
-        (literal %arg-choice-opt-open-str%)
-        ($charseq$)
-        (literal %arg-choice-opt-close-str%))))
-
-;; Avoid excessive cross-reference labels
-(define (auto-xref-indirect? target ancestor)
-  (cond
-;   ;; Always add indirect references to another book
-;   ((member (gi ancestor) (book-element-list))
-;    #t)
-   ;; Add indirect references to the section or component a block
-   ;; is in iff chapters aren't autolabelled.  (Otherwise "Figure 1-3"
-   ;; is sufficient)
-   ((and (member (gi target) (block-element-list))
-         (not %chapter-autolabel%))
-    #t)
-   ;; Add indirect references to the component a section is in if
-   ;; the sections are not autolabelled
-   ((and (member (gi target) (section-element-list))
-         (member (gi ancestor) (component-element-list))
-         (not %section-autolabel%))
-    #t)
-   (else #f)))
-
-
-;; Bibliography things
-
-;; Use the titles of bibliography entries in cross-references
-(define biblio-xref-title       #t)
-
-;; Process bibliography entry components in the order shown below, not
-;; in the order they appear in the document.  (I suppose this should
-;; be made to fit some publishing standard.)
-(define %biblioentry-in-entry-order% #f)
-
-(define (biblioentry-inline-elements)
-  (list
-   (normalize "author")
-   (normalize "authorgroup")
-   (normalize "title")
-   (normalize "subtitle")
-   (normalize "volumenum")
-   (normalize "edition")
-   (normalize "othercredit")
-   (normalize "contrib")
-   (normalize "editor")
-   (normalize "publishername")
-   (normalize "confgroup")
-   (normalize "publisher")
-   (normalize "isbn")
-   (normalize "issn")
-   (normalize "pubsnumber")
-   (normalize "date")
-   (normalize "pubdate")
-   (normalize "pagenums")
-   (normalize "bibliomisc")))
-
-(mode biblioentry-inline-mode
-
-  (element confgroup
-    (make sequence
-      (literal "Proc. ")
-      (next-match)))
-
-  (element isbn
-    (make sequence
-      (literal "ISBN ")
-      (process-children)))
-
-  (element issn
-    (make sequence
-      (literal "ISSN ")
-      (process-children))))
-
-
-;; The rules in the default stylesheet for productname format it as a
-;; paragraph.  This may be suitable for productname directly within
-;; *info, but it's nonsense when productname is used inline, as we do.
-(mode set-titlepage-recto-mode
-  (element (para productname) ($charseq$)))
-(mode set-titlepage-verso-mode
-  (element (para productname) ($charseq$)))
-(mode book-titlepage-recto-mode
-  (element (para productname) ($charseq$)))
-(mode book-titlepage-verso-mode
-  (element (para productname) ($charseq$)))
-;; Add more here if needed...
-
-
-;; Replace a sequence of whitespace in a string by a single space
-(define (normalize-whitespace str #!optional (whitespace '(#\space #\U-000D)))
-  (let loop ((characters (string->list str))
-             (result '())
-             (prev-was-space #f))
-    (if (null? characters)
-        (list->string (reverse result))
-        (let ((c (car characters))
-              (rest (cdr characters)))
-          (if (member c whitespace)
-              (if prev-was-space
-                  (loop rest result #t)
-                  (loop rest (cons #\space result) #t))
-              (loop rest (cons c result) #f))))))
-
-
-<!-- HTML output customization ..................................... -->
-
-<![ %output-html; [
-
-(define %section-autolabel%     #t)
-(define %label-preface-sections% #f)
-(define %generate-legalnotice-link% #t)
-(define %html-ext%              ".html")
-(define %root-filename%         "index")
-(define %link-mailto-url%       (string-append "mailto:" pgsql-docs-list))
-(define %use-id-as-filename%    #t)
-(define %stylesheet%            "stylesheet.css")
-(define %graphic-default-extension% "gif")
-(define %gentext-nav-use-ff%    #t)
-(define %body-attr%             '())
-(define ($generate-book-lot-list$) '())
-(define use-output-dir          #t)
-(define %output-dir%            "html")
-(define html-index-filename     "../HTML.index")
-
-
-;; Only build HTML.index or the actual HTML output, not both.  Saves a
-;; *lot* of time.  (overrides docbook.dsl)
-(root
-   (if (not html-index)
-       (make sequence
-         (process-children)
-         (with-mode manifest
-           (process-children)))
-       (with-mode htmlindex
-         (process-children))))
-
-
-;; Do not combine first section into chapter chunk.
-(define (chunk-skip-first-element-list) '())
-
-;; Returns the depth of auto TOC that should be made at the nd-level
-(define (toc-depth nd)
-  (cond ((string=? (gi nd) (normalize "book")) 2)
-	((string=? (gi nd) (normalize "set")) 2)
-	((string=? (gi nd) (normalize "part")) 2)
-	((string=? (gi nd) (normalize "chapter")) 2)
-	(else 1)))
-
-;; Put a horizontal line in the set TOC (just like the book TOC looks)
-(define (set-titlepage-separator side)
-  (if (equal? side 'recto)
-      (make empty-element gi: "HR")
-      (empty-sosofo)))
-
-;; Add character encoding and time of creation into HTML header
-(define %html-header-tags%
-  (list (list "META" '("HTTP-EQUIV" "Content-Type") '("CONTENT" "text/html; charset=ISO-8859-1"))
-	(list "META" '("NAME" "creation") (list "CONTENT" (time->string (time) #t)))))
-
-
-;; Block elements are allowed in PARA in DocBook, but not in P in
-;; HTML.  With %fix-para-wrappers% turned on, the stylesheets attempt
-;; to avoid putting block elements in HTML P tags by outputting
-;; additional end/begin P pairs around them.
-(define %fix-para-wrappers% #t)
-
-;; ...but we need to do some extra work to make the above apply to PRE
-;; as well.  (mostly pasted from dbverb.dsl)
-(define ($verbatim-display$ indent line-numbers?)
-  (let ((content (make element gi: "PRE"
-                       attributes: (list
-                                    (list "CLASS" (gi)))
-                       (if (or indent line-numbers?)
-                           ($verbatim-line-by-line$ indent line-numbers?)
-                           (process-children)))))
-    (if %shade-verbatim%
-        (make element gi: "TABLE"
-              attributes: ($shade-verbatim-attr$)
-              (make element gi: "TR"
-                    (make element gi: "TD"
-                          content)))
-	(make sequence
-	  (para-check)
-	  content
-	  (para-check 'restart)))))
-
-;; ...and for notes.
-(element note
-  (make sequence
-    (para-check)
-    ($admonition$)
-    (para-check 'restart)))
-
-;;; XXX The above is very ugly.  It might be better to run 'tidy' on
-;;; the resulting *.html files.
-
-
-;; Format multiple terms in varlistentry vertically, instead
-;; of comma-separated.
-(element (varlistentry term)
-  (make sequence
-    (process-children-trim)
-    (if (not (last-sibling?))
-        (make empty-element gi: "BR")
-        (empty-sosofo))))
-
-
-;; Customization of header, add title attributes (overrides
-;; dbcommon.dsl)
-(define (default-header-nav-tbl-ff elemnode prev next prevsib nextsib)
-  (let* ((r1? (nav-banner? elemnode))
-	 (r1-sosofo (make element gi: "TR"
-			  (make element gi: "TH"
-				attributes: (list
-					     (list "COLSPAN" "5")
-					     (list "ALIGN" "center")
-					     (list "VALIGN" "bottom"))
-				(make element gi: "A"
-				      attributes: (list
-						   (list "HREF" (href-to (nav-home elemnode))))
-				      (nav-banner elemnode)))))
-	 (r2? (or (not (node-list-empty? prev))
-		  (not (node-list-empty? next))
-		  (not (node-list-empty? prevsib))
-		  (not (node-list-empty? nextsib))
-		  (nav-context? elemnode)))
-	 (r2-sosofo (make element gi: "TR"
-			  (make element gi: "TD"
-				attributes: (list
-					     (list "WIDTH" "10%")
-					     (list "ALIGN" "left")
-					     (list "VALIGN" "top"))
-				(if (node-list-empty? prev)
-				    (make entity-ref name: "nbsp")
-				    (make element gi: "A"
-					  attributes: (list
-						       (list "TITLE" (element-title-string prev))
-						       (list "HREF"
-							     (href-to
-							      prev))
-						       (list "ACCESSKEY"
-							     "P"))
-					  (gentext-nav-prev prev))))
-			  (make element gi: "TD"
-				attributes: (list
-					     (list "WIDTH" "10%")
-					     (list "ALIGN" "left")
-					     (list "VALIGN" "top"))
-				(if (node-list-empty? prevsib)
-				    (make entity-ref name: "nbsp")
-				    (make element gi: "A"
-					  attributes: (list
-						       (list "TITLE" (element-title-string prevsib))
-						       (list "HREF"
-							     (href-to
-							      prevsib)))
-					  (gentext-nav-prev-sibling prevsib))))
-			  (make element gi: "TD"
-				attributes: (list
-					     (list "WIDTH" "60%")
-					     (list "ALIGN" "center")
-					     (list "VALIGN" "bottom"))
-				(nav-context elemnode))
-			  (make element gi: "TD"
-				attributes: (list
-					     (list "WIDTH" "10%")
-					     (list "ALIGN" "right")
-					     (list "VALIGN" "top"))
-				(if (node-list-empty? nextsib)
-				    (make entity-ref name: "nbsp")
-				    (make element gi: "A"
-					  attributes: (list
-						       (list "TITLE" (element-title-string nextsib))
-						       (list "HREF"
-							     (href-to
-							      nextsib)))
-					  (gentext-nav-next-sibling nextsib))))
-			  (make element gi: "TD"
-				attributes: (list
-					     (list "WIDTH" "10%")
-					     (list "ALIGN" "right")
-					     (list "VALIGN" "top"))
-				(if (node-list-empty? next)
-				    (make entity-ref name: "nbsp")
-				    (make element gi: "A"
-					  attributes: (list
-						       (list "TITLE" (element-title-string next))
-						       (list "HREF"
-							     (href-to
-							      next))
-						       (list "ACCESSKEY"
-							     "N"))
-					  (gentext-nav-next next)))))))
-    (if (or r1? r2?)
-	(make element gi: "DIV"
-	      attributes: '(("CLASS" "NAVHEADER"))
-	  (make element gi: "TABLE"
-		attributes: (list
-			     (list "SUMMARY" "Header navigation table")
-			     (list "WIDTH" %gentext-nav-tblwidth%)
-			     (list "BORDER" "0")
-			     (list "CELLPADDING" "0")
-			     (list "CELLSPACING" "0"))
-		(if r1? r1-sosofo (empty-sosofo))
-		(if r2? r2-sosofo (empty-sosofo)))
-	  (make empty-element gi: "HR"
-		attributes: (list
-			     (list "ALIGN" "LEFT")
-			     (list "WIDTH" %gentext-nav-tblwidth%))))
-	(empty-sosofo))))
-
-
-;; Put index "quicklinks" (A | B | C | ...) at the top of the bookindex page.
-
-(element index
-  (let ((preamble (node-list-filter-by-not-gi
-                   (children (current-node))
-                   (list (normalize "indexentry"))))
-        (indexdivs  (node-list-filter-by-gi
-		     (children (current-node))
-		     (list (normalize "indexdiv"))))
-        (entries  (node-list-filter-by-gi
-                   (children (current-node))
-                   (list (normalize "indexentry")))))
-    (html-document
-     (with-mode head-title-mode
-       (literal (element-title-string (current-node))))
-     (make element gi: "DIV"
-           attributes: (list (list "CLASS" (gi)))
-           ($component-separator$)
-           ($component-title$)
-	   (if (node-list-empty? indexdivs)
-	       (empty-sosofo)
-	       (make element gi: "P"
-		     attributes: (list (list "CLASS" "INDEXDIV-QUICKLINKS"))
-		     (with-mode indexdiv-quicklinks-mode
-		       (process-node-list indexdivs))))
-           (process-node-list preamble)
-           (if (node-list-empty? entries)
-               (empty-sosofo)
-               (make element gi: "DL"
-                     (process-node-list entries)))))))
-
-
-(mode indexdiv-quicklinks-mode
-  (element indexdiv
-    (make sequence
-      (make element gi: "A"
-	    attributes: (list (list "HREF" (href-to (current-node))))
-	    (element-title-sosofo))
-      (if (not (last-sibling?))
-	  (literal " | ")
-	  (literal "")))))
-
-
-;; Changed to strip and normalize index term content (overrides
-;; dbindex.dsl)
-(define (htmlindexterm)
-  (let* ((attr    (gi (current-node)))
-         (content (data (current-node)))
-         (string  (strip (normalize-whitespace content))) ;; changed
-         (sortas  (attribute-string (normalize "sortas"))))
-    (make sequence
-      (make formatting-instruction data: attr)
-      (if sortas
-          (make sequence
-            (make formatting-instruction data: "[")
-            (make formatting-instruction data: sortas)
-            (make formatting-instruction data: "]"))
-          (empty-sosofo))
-      (make formatting-instruction data: " ")
-      (make formatting-instruction data: string)
-      (htmlnewline))))
-
-
-]]> <!-- %output-html -->
-
-
-<!-- Print output customization .................................... -->
-
-<![ %output-print; [
-
-(define %section-autolabel%     #t)
-(define %default-quadding%      'justify)
-
-;; Don't know how well hyphenation works with other backends.  Might
-;; turn this on if desired.
-(define %hyphenation%
-  (if tex-backend #t #f))
-
-;; Put footnotes at the bottom of the page (rather than end of
-;; section), and put the URLs of links into footnotes.
-;;
-;; bop-footnotes only works with TeX, otherwise it's ignored.  But
-;; when both of these are #t and TeX is used, you need at least
-;; stylesheets 1.73 because otherwise you don't get any footnotes at
-;; all for the links.
-(define bop-footnotes           #t)
-(define %footnote-ulinks%       #t)
-
-(define %refentry-new-page%     #t)
-(define %refentry-keep%         #f)
-
-;; Disabled because of TeX problems
-;; (http://archives.postgresql.org/pgsql-docs/2007-12/msg00056.php)
-(define ($generate-book-lot-list$) '())
-
-;; Indentation of verbatim environments.  (This should really be done
-;; with start-indent in DSSSL.)
-;; Use of indentation in this area exposes a bug in openjade,
-;; http://archives.postgresql.org/pgsql-docs/2006-12/msg00064.php
-;; (define %indent-programlisting-lines% "    ")
-;; (define %indent-screen-lines% "    ")
-;; (define %indent-synopsis-lines% "    ")
-
-
-;; Default graphic format: Jadetex wants eps, pdfjadetex wants pdf.
-;; (Note that pdfjadetex will not accept eps, that's why we need to
-;; create a different .tex file for each.)  What works with RTF?
-
-(define texpdf-output #f) ;; override from command line
-
-(define %graphic-default-extension%
-  (cond (tex-backend (if texpdf-output "pdf" "eps"))
-	(rtf-backend "gif")
-	(else "XXX")))
-
-;; Need to add pdf here so that the above works.  Default setup
-;; doesn't know about PDF.
-(define preferred-mediaobject-extensions
-  (list "eps" "ps" "jpg" "jpeg" "pdf" "png"))
-
-
-;; Don't show links when citing a bibliography entry.  This fouls up
-;; the footnumber counting.  To get the link, one can still look into
-;; the bibliography itself.
-(mode xref-title-mode
-  (element ulink
-    (process-children)))
-
-
-;; Format legalnotice justified and with space between paragraphs.
-(mode book-titlepage-verso-mode
-  (element (legalnotice para)
-    (make paragraph
-      use: book-titlepage-verso-style	;; alter this if ever it needs to appear elsewhere
-      quadding: %default-quadding%
-      line-spacing: (* 0.8 (inherited-line-spacing))
-      font-size: (* 0.8 (inherited-font-size))
-      space-before: (* 0.8 %para-sep%)
-      space-after: (* 0.8 %para-sep%)
-      first-line-start-indent: (if (is-first-para)
-				   (* 0.8 %para-indent-firstpara%)
-				   (* 0.8 %para-indent%))
-      (process-children))))
-
-
-;; Fix spacing problems in variablelists
-
-(element (varlistentry term)
-  (make paragraph
-    space-before: (if (first-sibling?)
-		      %para-sep%
-		      0pt)
-    keep-with-next?: #t
-    (process-children)))
-
-(define %varlistentry-indent% 2em)
-
-(element (varlistentry listitem)
-  (make sequence
-    start-indent: (+ (inherited-start-indent) %varlistentry-indent%)
-    (process-children)))
-
-
-;; Whitespace fixes for itemizedlists and orderedlists
-
-(define (process-listitem-content)
-  (if (absolute-first-sibling?)
-      (make sequence
-        (process-children-trim))
-      (next-match)))
-
-
-;; Default stylesheets format simplelists as tables.  This spells
-;; trouble for Jade.  So we just format them as plain lines.
-
-(define %simplelist-indent% 1em)
-
-(define (my-simplelist-vert members)
-  (make display-group
-    space-before: %para-sep%
-    space-after: %para-sep%
-    start-indent: (+ %simplelist-indent% (inherited-start-indent))
-    (process-children)))
-
-(element simplelist
-  (let ((type (attribute-string (normalize "type")))
-        (cols (if (attribute-string (normalize "columns"))
-                  (if (> (string->number (attribute-string (normalize "columns"))) 0)
-                      (string->number (attribute-string (normalize "columns")))
-                      1)
-                  1))
-        (members (select-elements (children (current-node)) (normalize "member"))))
-    (cond
-       ((equal? type (normalize "inline"))
-	(if (equal? (gi (parent (current-node)))
-		    (normalize "para"))
-	    (process-children)
-	    (make paragraph
-	      space-before: %para-sep%
-	      space-after: %para-sep%
-	      start-indent: (inherited-start-indent))))
-       ((equal? type (normalize "vert"))
-        (my-simplelist-vert members))
-       ((equal? type (normalize "horiz"))
-        (simplelist-table 'row    cols members)))))
-
-(element member
-  (let ((type (inherited-attribute-string (normalize "type"))))
-    (cond
-     ((equal? type (normalize "inline"))
-      (make sequence
-	(process-children)
-	(if (not (last-sibling?))
-	    (literal ", ")
-	    (literal ""))))
-      ((equal? type (normalize "vert"))
-       (make paragraph
-	 space-before: 0pt
-	 space-after: 0pt))
-      ((equal? type (normalize "horiz"))
-       (make paragraph
-	 quadding: 'start
-	 (process-children))))))
-
-
-;; Jadetex doesn't handle links to the content of tables, so
-;; indexterms that point to table entries will go nowhere.  We fix
-;; this by pointing the index entry to the table itself instead, which
-;; should be equally useful in practice.
-
-(define (find-parent-table nd)
-  (let ((table (ancestor-member nd ($table-element-list$))))
-    (if (node-list-empty? table)
-	nd
-	table)))
-
-;; (The function below overrides the one in print/dbindex.dsl.)
-
-(define (indexentry-link nd)
-  (let* ((id        (attribute-string (normalize "role") nd))
-         (prelim-target (find-indexterm id))
-         (target    (find-parent-table prelim-target))
-         (preferred (not (node-list-empty?
-                          (select-elements (children (current-node))
-                                           (normalize "emphasis")))))
-         (sosofo    (if (node-list-empty? target)
-                        (literal "?")
-                        (make link
-                          destination: (node-list-address target)
-                          (with-mode toc-page-number-mode
-                            (process-node-list target))))))
-    (if preferred
-        (make sequence
-          font-weight: 'bold
-          sosofo)
-        sosofo)))
-
-
-;; By default, the part and reference title pages get wrong page
-;; numbers: The first title page gets roman numerals carried over from
-;; preface/toc -- we want arabic numerals.  We also need to make sure
-;; that page-number-restart is set of #f explicitly, because otherwise
-;; it will carry over from the previous component, which is not good.
-;;
-;; (This looks worse than it is.  It's copied from print/dbttlpg.dsl
-;; and common/dbcommon.dsl and modified in minor detail.)
-
-(define (first-part?)
-  (let* ((book (ancestor (normalize "book")))
-	 (nd   (ancestor-member (current-node)
-				(append
-				 (component-element-list)
-				 (division-element-list))))
-	 (bookch (children book)))
-    (let loop ((nl bookch))
-      (if (node-list-empty? nl)
-	  #f
-	  (if (equal? (gi (node-list-first nl)) (normalize "part"))
-	      (if (node-list=? (node-list-first nl) nd)
-		  #t
-		  #f)
-	      (loop (node-list-rest nl)))))))
-
-(define (first-reference?)
-  (let* ((book (ancestor (normalize "book")))
-	 (nd   (ancestor-member (current-node)
-				(append
-				 (component-element-list)
-				 (division-element-list))))
-	 (bookch (children book)))
-    (let loop ((nl bookch))
-      (if (node-list-empty? nl)
-	  #f
-	  (if (equal? (gi (node-list-first nl)) (normalize "reference"))
-	      (if (node-list=? (node-list-first nl) nd)
-		  #t
-		  #f)
-	      (loop (node-list-rest nl)))))))
-
-
-(define (part-titlepage elements #!optional (side 'recto))
-  (let ((nodelist (titlepage-nodelist
-		   (if (equal? side 'recto)
-		       (reference-titlepage-recto-elements)
-		       (reference-titlepage-verso-elements))
-		   elements))
-        ;; partintro is a special case...
-	(partintro (node-list-first
-		    (node-list-filter-by-gi elements (list (normalize "partintro"))))))
-    (if (part-titlepage-content? elements side)
-	(make simple-page-sequence
-	  page-n-columns: %titlepage-n-columns%
-	  ;; Make sure that page number format is correct.
-	  page-number-format: ($page-number-format$)
-	  ;; Make sure that the page number is set to 1 if this is the
-	  ;; first part in the book
-	  page-number-restart?: (first-part?)
-	  input-whitespace-treatment: 'collapse
-	  use: default-text-style
-
-	  ;; This hack is required for the RTF backend. If an external-graphic
-	  ;; is the first thing on the page, RTF doesn't seem to do the right
-	  ;; thing (the graphic winds up on the baseline of the first line
-	  ;; of the page, left justified).  This "one point rule" fixes
-	  ;; that problem.
-	  (make paragraph
-	    line-spacing: 1pt
-	    (literal ""))
-
-	  (let loop ((nl nodelist) (lastnode (empty-node-list)))
-	    (if (node-list-empty? nl)
-		(empty-sosofo)
-		(make sequence
-		  (if (or (node-list-empty? lastnode)
-			  (not (equal? (gi (node-list-first nl))
-				       (gi lastnode))))
-		      (part-titlepage-before (node-list-first nl) side)
-		      (empty-sosofo))
-		  (cond
-		   ((equal? (gi (node-list-first nl)) (normalize "subtitle"))
-		    (part-titlepage-subtitle (node-list-first nl) side))
-		   ((equal? (gi (node-list-first nl)) (normalize "title"))
-		    (part-titlepage-title (node-list-first nl) side))
-		   (else
-		    (part-titlepage-default (node-list-first nl) side)))
-		  (loop (node-list-rest nl) (node-list-first nl)))))
-
-	  (if (and %generate-part-toc%
-		   %generate-part-toc-on-titlepage%
-		   (equal? side 'recto))
-	      (make display-group
-		(build-toc (current-node)
-			   (toc-depth (current-node))))
-	      (empty-sosofo))
-
-	  ;; PartIntro is a special case
-	  (if (and (equal? side 'recto)
-		   (not (node-list-empty? partintro))
-		   %generate-partintro-on-titlepage%)
-	      ($process-partintro$ partintro #f)
-	      (empty-sosofo)))
-
-	(empty-sosofo))))
-
-
-(define (reference-titlepage elements #!optional (side 'recto))
-  (let ((nodelist (titlepage-nodelist
-		   (if (equal? side 'recto)
-		       (reference-titlepage-recto-elements)
-		       (reference-titlepage-verso-elements))
-		   elements))
-        ;; partintro is a special case...
-	(partintro (node-list-first
-		    (node-list-filter-by-gi elements (list (normalize "partintro"))))))
-    (if (reference-titlepage-content? elements side)
-	(make simple-page-sequence
-	  page-n-columns: %titlepage-n-columns%
-	  ;; Make sure that page number format is correct.
-	  page-number-format: ($page-number-format$)
-	  ;; Make sure that the page number is set to 1 if this is the
-	  ;; first part in the book
-	  page-number-restart?: (first-reference?)
-	  input-whitespace-treatment: 'collapse
-	  use: default-text-style
-
-	  ;; This hack is required for the RTF backend. If an external-graphic
-	  ;; is the first thing on the page, RTF doesn't seem to do the right
-	  ;; thing (the graphic winds up on the baseline of the first line
-	  ;; of the page, left justified).  This "one point rule" fixes
-	  ;; that problem.
-	  (make paragraph
-	    line-spacing: 1pt
-	    (literal ""))
-
-	  (let loop ((nl nodelist) (lastnode (empty-node-list)))
-	    (if (node-list-empty? nl)
-		(empty-sosofo)
-		(make sequence
-		  (if (or (node-list-empty? lastnode)
-			  (not (equal? (gi (node-list-first nl))
-				       (gi lastnode))))
-		      (reference-titlepage-before (node-list-first nl) side)
-		      (empty-sosofo))
-		  (cond
-		   ((equal? (gi (node-list-first nl)) (normalize "author"))
-		    (reference-titlepage-author (node-list-first nl) side))
-		   ((equal? (gi (node-list-first nl)) (normalize "authorgroup"))
-		    (reference-titlepage-authorgroup (node-list-first nl) side))
-		   ((equal? (gi (node-list-first nl)) (normalize "corpauthor"))
-		    (reference-titlepage-corpauthor (node-list-first nl) side))
-		   ((equal? (gi (node-list-first nl)) (normalize "editor"))
-		    (reference-titlepage-editor (node-list-first nl) side))
-		   ((equal? (gi (node-list-first nl)) (normalize "subtitle"))
-		    (reference-titlepage-subtitle (node-list-first nl) side))
-		   ((equal? (gi (node-list-first nl)) (normalize "title"))
-		    (reference-titlepage-title (node-list-first nl) side))
-		   (else
-		    (reference-titlepage-default (node-list-first nl) side)))
-		  (loop (node-list-rest nl) (node-list-first nl)))))
-
-	  (if (and %generate-reference-toc%
-		   %generate-reference-toc-on-titlepage%
-		   (equal? side 'recto))
-	      (make display-group
-		(build-toc (current-node)
-			   (toc-depth (current-node))))
-	      (empty-sosofo))
-
-	  ;; PartIntro is a special case
-	  (if (and (equal? side 'recto)
-		   (not (node-list-empty? partintro))
-		   %generate-partintro-on-titlepage%)
-	      ($process-partintro$ partintro #f)
-	      (empty-sosofo)))
-
-	(empty-sosofo))))
-
-]]> <!-- %output-print -->
-
-
-<!-- Plain text output customization ............................... -->
-
-<!--
-This is used for making the INSTALL file and others.  We customize the
-HTML stylesheets to be suitable for dumping plain text (via Netscape,
-Lynx, or similar).
--->
-
-<![ %output-text; [
-
-(define %section-autolabel% #f)
-(define %chapter-autolabel% #f)
-(define $generate-chapter-toc$ (lambda () #f))
-
-;; For text output, produce "ASCII markup" for emphasis and such.
-
-(define ($asterix-seq$ #!optional (sosofo (process-children)))
-  (make sequence
-    (literal "*")
-    sosofo
-    (literal "*")))
-
-(define ($dquote-seq$ #!optional (sosofo (process-children)))
-  (make sequence
-    (literal (gentext-start-quote))
-    sosofo
-    (literal (gentext-end-quote))))
-
-(element (para command) ($dquote-seq$))
-(element (para emphasis) ($asterix-seq$))
-(element (para filename) ($dquote-seq$))
-(element (para option) ($dquote-seq$))
-(element (para replaceable) ($dquote-seq$))
-(element (para userinput) ($dquote-seq$))
-
-]]> <!-- %output-text -->
-
-  </style-specification-body>
- </style-specification>
-
- <external-specification id="docbook" document="dbstyle">
-</style-sheet>
diff --git a/doc-xc/src/sgml/stylesheet.xsl b/doc-xc/src/sgml/stylesheet.xsl
deleted file mode 100644
index 19cb5b0f64..0000000000
--- a/doc-xc/src/sgml/stylesheet.xsl
+++ /dev/null
@@ -1,35 +0,0 @@
-<?xml version='1.0'?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                version='1.0'
-                xmlns="http://www.w3.org/TR/xhtml1/transitional"
-                exclude-result-prefixes="#default">
-
-<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl"/>
-<xsl:include href="stylesheet-common.xsl" />
-
-
-<!-- Parameters -->
-<xsl:param name="base.dir" select="'html'"></xsl:param>
-<xsl:param name="html.stylesheet" select="'stylesheet.css'"></xsl:param>
-<xsl:param name="use.id.as.filename" select="'1'"></xsl:param>
-<xsl:param name="make.valid.html" select="1"></xsl:param>
-<xsl:param name="generate.id.attributes" select="1"></xsl:param>
-<xsl:param name="generate.legalnotice.link" select="1"></xsl:param>
-<xsl:param name="link.mailto.url">[email protected]</xsl:param>
-<xsl:param name="chunker.output.indent" select="'yes'"/>
-<xsl:param name="chunk.quietly" select="1"></xsl:param>
-
-
-<!--
-  Format multiple terms in varlistentry vertically, instead
-  of comma-separated.
- -->
-
-<xsl:template match="varlistentry/term[position()!=last()]">
-  <span class="term">
-    <xsl:call-template name="anchor"/>
-    <xsl:apply-templates/>
-  </span><br/>
-</xsl:template>
-
-</xsl:stylesheet>
diff --git a/doc-xc/src/sgml/syntax.sgmlin b/doc-xc/src/sgml/syntax.sgmlin
deleted file mode 100644
index 72472d5d5f..0000000000
--- a/doc-xc/src/sgml/syntax.sgmlin
+++ /dev/null
@@ -1,2670 +0,0 @@
-<!-- doc/src/sgml/syntax.sgml -->
-
-<chapter id="sql-syntax">
- <title>SQL Syntax</title>
-
- <indexterm zone="sql-syntax">
-  <primary>syntax</primary>
-  <secondary>SQL</secondary>
- </indexterm>
-
- <para>
-  This chapter describes the syntax of SQL.  It forms the foundation
-  for understanding the following chapters which will go into detail
-  about how SQL commands are applied to define and modify data.
- </para>
-
- <para>
-  We also advise users who are already familiar with SQL to read this
-  chapter carefully because it contains several rules and concepts that
-  are implemented inconsistently among SQL databases or that are
-  <!## PG>
-  specific to <productname>PostgreSQL</productname>.
-  <!## end>
-  <!## XC>
-  specific to <productname>Postgres-XC</productname>.
-  <!## end>
- </para>
-
-
- <sect1 id="sql-syntax-lexical">
-  <title>Lexical Structure</title>
-
-  <indexterm>
-   <primary>token</primary>
-  </indexterm>
-
-&common;
-  <para>
-   SQL input consists of a sequence of
-   <firstterm>commands</firstterm>.  A command is composed of a
-   sequence of <firstterm>tokens</firstterm>, terminated by a
-   semicolon (<quote>;</quote>).  The end of the input stream also
-   terminates a command.  Which tokens are valid depends on the syntax
-   of the particular command.
-  </para>
-
-  <para>
-   A token can be a <firstterm>key word</firstterm>, an
-   <firstterm>identifier</firstterm>, a <firstterm>quoted
-   identifier</firstterm>, a <firstterm>literal</firstterm> (or
-   constant), or a special character symbol.  Tokens are normally
-   separated by whitespace (space, tab, newline), but need not be if
-   there is no ambiguity (which is generally only the case if a
-   special character is adjacent to some other token type).
-  </para>
-
-   <para>
-    For example, the following is (syntactically) valid SQL input:
-<programlisting>
-SELECT * FROM MY_TABLE;
-UPDATE MY_TABLE SET A = 5;
-INSERT INTO MY_TABLE VALUES (3, 'hi there');
-</programlisting>
-    This is a sequence of three commands, one per line (although this
-    is not required; more than one command can be on a line, and
-    commands can usefully be split across lines).
-   </para>
-
-  <para>
-   Additionally, <firstterm>comments</firstterm> can occur in SQL
-   input.  They are not tokens, they are effectively equivalent to
-   whitespace.
-  </para>
-
-  <para>
-   The SQL syntax is not very consistent regarding what tokens
-   identify commands and which are operands or parameters.  The first
-   few tokens are generally the command name, so in the above example
-   we would usually speak of a <quote>SELECT</quote>, an
-   <quote>UPDATE</quote>, and an <quote>INSERT</quote> command.  But
-   for instance the <command>UPDATE</command> command always requires
-   a <token>SET</token> token to appear in a certain position, and
-   this particular variation of <command>INSERT</command> also
-   requires a <token>VALUES</token> in order to be complete.  The
-   precise syntax rules for each command are described in <xref linkend="reference">.
-  </para>
-
-  <sect2 id="sql-syntax-identifiers">
-   <title>Identifiers and Key Words</title>
-
-   <indexterm zone="sql-syntax-identifiers">
-    <primary>identifier</primary>
-    <secondary>syntax of</secondary>
-   </indexterm>
-
-   <indexterm zone="sql-syntax-identifiers">
-    <primary>name</primary>
-    <secondary>syntax of</secondary>
-   </indexterm>
-
-   <indexterm zone="sql-syntax-identifiers">
-    <primary>key word</primary>
-    <secondary>syntax of</secondary>
-   </indexterm>
-&common;
-   <para>
-    Tokens such as <token>SELECT</token>, <token>UPDATE</token>, or
-    <token>VALUES</token> in the example above are examples of
-    <firstterm>key words</firstterm>, that is, words that have a fixed
-    meaning in the SQL language.  The tokens <token>MY_TABLE</token>
-    and <token>A</token> are examples of
-    <firstterm>identifiers</firstterm>.  They identify names of
-    tables, columns, or other database objects, depending on the
-    command they are used in.  Therefore they are sometimes simply
-    called <quote>names</quote>.  Key words and identifiers have the
-    same lexical structure, meaning that one cannot know whether a
-    token is an identifier or a key word without knowing the language.
-    A complete list of key words can be found in <xref
-    linkend="sql-keywords-appendix">.
-   </para>
-
-   <para>
-    SQL identifiers and key words must begin with a letter
-    (<literal>a</literal>-<literal>z</literal>, but also letters with
-    diacritical marks and non-Latin letters) or an underscore
-    (<literal>_</literal>).  Subsequent characters in an identifier or
-    key word can be letters, underscores, digits
-    (<literal>0</literal>-<literal>9</literal>), or dollar signs
-    (<literal>$</>).  Note that dollar signs are not allowed in identifiers
-    according to the letter of the SQL standard, so their use might render
-    applications less portable.
-    The SQL standard will not define a key word that contains
-    digits or starts or ends with an underscore, so identifiers of this
-    form are safe against possible conflict with future extensions of the
-    standard.
-   </para>
-
-   <para>
-    <indexterm><primary>identifier</primary><secondary>length</secondary></indexterm>
-    The system uses no more than <symbol>NAMEDATALEN</symbol>-1
-    bytes of an identifier; longer names can be written in
-    commands, but they will be truncated.  By default,
-    <symbol>NAMEDATALEN</symbol> is 64 so the maximum identifier
-    length is 63 bytes. If this limit is problematic, it can be raised by
-    changing the <symbol>NAMEDATALEN</symbol> constant in
-    <filename>src/include/pg_config_manual.h</filename>.
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>case sensitivity</primary>
-     <secondary>of SQL commands</secondary>
-    </indexterm>
-    Key words and unquoted identifiers are case insensitive.  Therefore:
-<programlisting>
-UPDATE MY_TABLE SET A = 5;
-</programlisting>
-    can equivalently be written as:
-<programlisting>
-uPDaTE my_TabLE SeT a = 5;
-</programlisting>
-    A convention often used is to write key words in upper
-    case and names in lower case, e.g.:
-<programlisting>
-UPDATE my_table SET a = 5;
-</programlisting>
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>quotation marks</primary>
-     <secondary>and identifiers</secondary>
-    </indexterm>
-    There is a second kind of identifier:  the <firstterm>delimited
-    identifier</firstterm> or <firstterm>quoted
-    identifier</firstterm>.  It is formed by enclosing an arbitrary
-    sequence of characters in double-quotes
-    (<literal>"</literal>). <!-- " font-lock mania --> A delimited
-    identifier is always an identifier, never a key word.  So
-    <literal>"select"</literal> could be used to refer to a column or
-    table named <quote>select</quote>, whereas an unquoted
-    <literal>select</literal> would be taken as a key word and
-    would therefore provoke a parse error when used where a table or
-    column name is expected.  The example can be written with quoted
-    identifiers like this:
-<programlisting>
-UPDATE "my_table" SET "a" = 5;
-</programlisting>
-   </para>
-
-   <para>
-    Quoted identifiers can contain any character, except the character
-    with code zero.  (To include a double quote, write two double quotes.)
-    This allows constructing table or column names that would
-    otherwise not be possible, such as ones containing spaces or
-    ampersands.  The length limitation still applies.
-   </para>
-
-   <indexterm>
-     <primary>Unicode escape</primary>
-     <secondary>in identifiers</secondary>
-   </indexterm>
-
-   <para>
-    A variant of quoted
-    identifiers allows including escaped Unicode characters identified
-    by their code points.  This variant starts
-    with <literal>U&amp;</literal> (upper or lower case U followed by
-    ampersand) immediately before the opening double quote, without
-    any spaces in between, for example <literal>U&amp;"foo"</literal>.
-    (Note that this creates an ambiguity with the
-    operator <literal>&amp;</literal>.  Use spaces around the operator to
-    avoid this problem.)  Inside the quotes, Unicode characters can be
-    specified in escaped form by writing a backslash followed by the
-    four-digit hexadecimal code point number or alternatively a
-    backslash followed by a plus sign followed by a six-digit
-    hexadecimal code point number.  For example, the
-    identifier <literal>"data"</literal> could be written as
-<programlisting>
-U&amp;"d\0061t\+000061"
-</programlisting>
-    The following less trivial example writes the Russian
-    word <quote>slon</quote> (elephant) in Cyrillic letters:
-<programlisting>
-U&amp;"\0441\043B\043E\043D"
-</programlisting>
-   </para>
-
-   <para>
-    If a different escape character than backslash is desired, it can
-    be specified using
-    the <literal>UESCAPE</literal><indexterm><primary>UESCAPE</primary></indexterm>
-    clause after the string, for example:
-<programlisting>
-U&amp;"d!0061t!+000061" UESCAPE '!'
-</programlisting>
-    The escape character can be any single character other than a
-    hexadecimal digit, the plus sign, a single quote, a double quote,
-    or a whitespace character.  Note that the escape character is
-    written in single quotes, not double quotes.
-   </para>
-
-   <para>
-    To include the escape character in the identifier literally, write
-    it twice.
-   </para>
-
-   <para>
-    The Unicode escape syntax works only when the server encoding is
-    <literal>UTF8</>.  When other server encodings are used, only code
-    points in the ASCII range (up to <literal>\007F</literal>) can be
-    specified.  Both the 4-digit and the 6-digit form can be used to
-    specify UTF-16 surrogate pairs to compose characters with code
-    points larger than U+FFFF, although the availability of the
-    6-digit form technically makes this unnecessary.  (Surrogate
-    pairs are not stored directly, but combined into a single
-    code point that is then encoded in UTF-8.)
-   </para>
-
-   <para>
-    Quoting an identifier also makes it case-sensitive, whereas
-    unquoted names are always folded to lower case.  For example, the
-    identifiers <literal>FOO</literal>, <literal>foo</literal>, and
-    <literal>"foo"</literal> are considered the same by
-<!## PG>
-    <productname>PostgreSQL</productname>, but
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>, but
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>, but
-<!## end>
-    <literal>"Foo"</literal> and <literal>"FOO"</literal> are
-    different from these three and each other.  (The folding of
-<!## PG>
-    unquoted names to lower case in <productname>PostgreSQL</> is
-<!## end>
-<!## XC>
-    unquoted names to lower case in <productname>Postgres-XC</> is
-<!## end>
-<!## XL>
-    unquoted names to lower case in <productname>Postgres-XL</> is
-<!## end>
-    incompatible with the SQL standard, which says that unquoted names
-    should be folded to upper case.  Thus, <literal>foo</literal>
-    should be equivalent to <literal>"FOO"</literal> not
-    <literal>"foo"</literal> according to the standard.  If you want
-    to write portable applications you are advised to always quote a
-    particular name or never quote it.)
-   </para>
-  </sect2>
-
-
-  <sect2 id="sql-syntax-constants">
-   <title>Constants</title>
-
-   <indexterm zone="sql-syntax-constants">
-    <primary>constant</primary>
-   </indexterm>
-&common;
-   <para>
-    There are three kinds of <firstterm>implicitly-typed
-<!## PG>
-    constants</firstterm> in <productname>PostgreSQL</productname>:
-<!## end>
-<!## XC>
-    constants</firstterm> in <productname>Postgres-XC</productname>:
-<!## end>
-<!## XL>
-    constants</firstterm> in <productname>Postgres-XL</productname>:
-<!## end>
-    strings, bit strings, and numbers.
-    Constants can also be specified with explicit types, which can
-    enable more accurate representation and more efficient handling by
-    the system. These alternatives are discussed in the following
-    subsections.
-   </para>
-
-   <sect3 id="sql-syntax-strings">
-    <title>String Constants</title>
-
-    <indexterm zone="sql-syntax-strings">
-     <primary>character string</primary>
-     <secondary>constant</secondary>
-    </indexterm>
-&common;
-    <para>
-     <indexterm>
-      <primary>quotation marks</primary>
-      <secondary>escaping</secondary>
-     </indexterm>
-     A string constant in SQL is an arbitrary sequence of characters
-     bounded by single quotes (<literal>'</literal>), for example
-     <literal>'This is a string'</literal>.  To include
-     a single-quote character within a string constant,
-     write two adjacent single quotes, e.g.,
-     <literal>'Dianne''s horse'</literal>.
-     Note that this is <emphasis>not</> the same as a double-quote
-     character (<literal>"</>). <!-- font-lock sanity: " -->
-    </para>
-
-    <para>
-     Two string constants that are only separated by whitespace
-     <emphasis>with at least one newline</emphasis> are concatenated
-     and effectively treated as if the string had been written as one
-     constant.  For example:
-<programlisting>
-SELECT 'foo'
-'bar';
-</programlisting>
-     is equivalent to:
-<programlisting>
-SELECT 'foobar';
-</programlisting>
-     but:
-<programlisting>
-SELECT 'foo'      'bar';
-</programlisting>
-     is not valid syntax.  (This slightly bizarre behavior is specified
-<!## PG>
-     by <acronym>SQL</acronym>; <productname>PostgreSQL</productname> is
-<!## end>
-<!## XC>
-     by <acronym>SQL</acronym>; <productname>Postgres-XC</productname> is
-<!## end>
-<!## XL>
-     by <acronym>SQL</acronym>; <productname>Postgres-XL</productname> is
-<!## end>
-     following the standard.)
-    </para>
-   </sect3>
-
-   <sect3 id="sql-syntax-strings-escape">
-    <title>String Constants with C-style Escapes</title>
-
-     <indexterm zone="sql-syntax-strings-escape">
-      <primary>escape string syntax</primary>
-     </indexterm>
-     <indexterm zone="sql-syntax-strings-escape">
-      <primary>backslash escapes</primary>
-     </indexterm>
-&common;
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> also accepts <quote>escape</>
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> also accepts <quote>escape</>
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> also accepts <quote>escape</>
-<!## end>
-     string constants, which are an extension to the SQL standard.
-     An escape string constant is specified by writing the letter
-     <literal>E</literal> (upper or lower case) just before the opening single
-     quote, e.g., <literal>E'foo'</>.  (When continuing an escape string
-     constant across lines, write <literal>E</> only before the first opening
-     quote.)
-     Within an escape string, a backslash character (<literal>\</>) begins a
-     C-like <firstterm>backslash escape</> sequence, in which the combination
-     of backslash and following character(s) represent a special byte
-     value, as shown in <xref linkend="sql-backslash-table">.
-    </para>
-
-     <table id="sql-backslash-table">
-      <title>Backslash Escape Sequences</title>
-      <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>Backslash Escape Sequence</>
-        <entry>Interpretation</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry><literal>\b</literal></entry>
-        <entry>backspace</entry>
-       </row>
-       <row>
-        <entry><literal>\f</literal></entry>
-        <entry>form feed</entry>
-       </row>
-       <row>
-        <entry><literal>\n</literal></entry>
-        <entry>newline</entry>
-       </row>
-       <row>
-        <entry><literal>\r</literal></entry>
-        <entry>carriage return</entry>
-       </row>
-       <row>
-        <entry><literal>\t</literal></entry>
-        <entry>tab</entry>
-       </row>
-       <row>
-        <entry>
-         <literal>\<replaceable>o</replaceable></literal>,
-         <literal>\<replaceable>oo</replaceable></literal>,
-         <literal>\<replaceable>ooo</replaceable></literal>
-         (<replaceable>o</replaceable> = 0 - 7)
-        </entry>
-        <entry>octal byte value</entry>
-       </row>
-       <row>
-        <entry>
-         <literal>\x<replaceable>h</replaceable></literal>,
-         <literal>\x<replaceable>hh</replaceable></literal>
-         (<replaceable>h</replaceable> = 0 - 9, A - F)
-        </entry>
-        <entry>hexadecimal byte value</entry>
-       </row>
-       <row>
-        <entry>
-         <literal>\u<replaceable>xxxx</replaceable></literal>,
-         <literal>\U<replaceable>xxxxxxxx</replaceable></literal>
-         (<replaceable>x</replaceable> = 0 - 9, A - F)
-        </entry>
-        <entry>16 or 32-bit hexadecimal Unicode character value</entry>
-       </row>
-      </tbody>
-      </tgroup>
-     </table>
-
-    <para>
-     Any other
-     character following a backslash is taken literally. Thus, to
-     include a backslash character, write two backslashes (<literal>\\</>).
-     Also, a single quote can be included in an escape string by writing
-     <literal>\'</literal>, in addition to the normal way of <literal>''</>.
-    </para>
-
-    <para>
-     It is your responsibility that the byte sequences you create,
-     especially when using the octal or hexadecimal escapes, compose
-     valid characters in the server character set encoding.  When the
-     server encoding is UTF-8, then the Unicode escapes or the
-     alternative Unicode escape syntax, explained
-     in <xref linkend="sql-syntax-strings-uescape">, should be used
-     instead.  (The alternative would be doing the UTF-8 encoding by
-     hand and writing out the bytes, which would be very cumbersome.)
-    </para>
-
-    <para>
-     The Unicode escape syntax works fully only when the server
-     encoding is <literal>UTF8</>.  When other server encodings are
-     used, only code points in the ASCII range (up
-     to <literal>\u007F</>) can be specified.  Both the 4-digit and
-     the 8-digit form can be used to specify UTF-16 surrogate pairs to
-     compose characters with code points larger than U+FFFF, although
-     the availability of the 8-digit form technically makes this
-     unnecessary.  (When surrogate pairs are used when the server
-     encoding is <literal>UTF8</>, they are first combined into a
-     single code point that is then encoded in UTF-8.)
-    </para>
-
-    <caution>
-    <para>
-     If the configuration parameter
-     <xref linkend="guc-standard-conforming-strings"> is <literal>off</>,
-<!## PG>
-     then <productname>PostgreSQL</productname> recognizes backslash escapes
-<!## end>
-<!## XC>
-     then <productname>Postgres-XC</productname> recognizes backslash escapes
-<!## end>
-<!## XL>
-     then <productname>Postgres-XL</productname> recognizes backslash escapes
-<!## end>
-     in both regular and escape string constants.  However, as of
-     <productname>PostgreSQL</> 9.1, the default is <literal>on</>, meaning
-     that backslash escapes are recognized only in escape string constants.
-     This behavior is more standards-compliant, but might break applications
-     which rely on the historical behavior, where backslash escapes
-     were always recognized.  As a workaround, you can set this parameter
-     to <literal>off</>, but it is better to migrate away from using backslash
-     escapes.  If you need to use a backslash escape to represent a special
-     character, write the string constant with an <literal>E</>.
-    </para>
-
-    <para>
-     In addition to <varname>standard_conforming_strings</>, the configuration
-     parameters <xref linkend="guc-escape-string-warning"> and
-     <xref linkend="guc-backslash-quote"> govern treatment of backslashes
-     in string constants.
-    </para>
-    </caution>
-
-    <para>
-     The character with the code zero cannot be in a string constant.
-    </para>
-   </sect3>
-
-   <sect3 id="sql-syntax-strings-uescape">
-    <title>String Constants with Unicode Escapes</title>
-
-    <indexterm  zone="sql-syntax-strings-uescape">
-     <primary>Unicode escape</primary>
-     <secondary>in string constants</secondary>
-    </indexterm>
-&common;
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> also supports another type
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> also supports another type
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> also supports another type
-<!## end>
-     of escape syntax for strings that allows specifying arbitrary
-     Unicode characters by code point.  A Unicode escape string
-     constant starts with <literal>U&amp;</literal> (upper or lower case
-     letter U followed by ampersand) immediately before the opening
-     quote, without any spaces in between, for
-     example <literal>U&amp;'foo'</literal>.  (Note that this creates an
-     ambiguity with the operator <literal>&amp;</literal>.  Use spaces
-     around the operator to avoid this problem.)  Inside the quotes,
-     Unicode characters can be specified in escaped form by writing a
-     backslash followed by the four-digit hexadecimal code point
-     number or alternatively a backslash followed by a plus sign
-     followed by a six-digit hexadecimal code point number.  For
-     example, the string <literal>'data'</literal> could be written as
-<programlisting>
-U&amp;'d\0061t\+000061'
-</programlisting>
-     The following less trivial example writes the Russian
-     word <quote>slon</quote> (elephant) in Cyrillic letters:
-<programlisting>
-U&amp;'\0441\043B\043E\043D'
-</programlisting>
-    </para>
-
-    <para>
-     If a different escape character than backslash is desired, it can
-     be specified using
-     the <literal>UESCAPE</literal><indexterm><primary>UESCAPE</primary></indexterm>
-     clause after the string, for example:
-<programlisting>
-U&amp;'d!0061t!+000061' UESCAPE '!'
-</programlisting>
-     The escape character can be any single character other than a
-     hexadecimal digit, the plus sign, a single quote, a double quote,
-     or a whitespace character.
-    </para>
-
-    <para>
-     The Unicode escape syntax works only when the server encoding is
-     <literal>UTF8</>.  When other server encodings are used, only
-     code points in the ASCII range (up to <literal>\007F</literal>)
-     can be specified.  Both the 4-digit and the 6-digit form can be
-     used to specify UTF-16 surrogate pairs to compose characters with
-     code points larger than U+FFFF, although the availability of the
-     6-digit form technically makes this unnecessary.  (When surrogate
-     pairs are used when the server encoding is <literal>UTF8</>, they
-     are first combined into a single code point that is then encoded
-     in UTF-8.)
-    </para>
-
-    <para>
-     Also, the Unicode escape syntax for string constants only works
-     when the configuration
-     parameter <xref linkend="guc-standard-conforming-strings"> is
-     turned on.  This is because otherwise this syntax could confuse
-     clients that parse the SQL statements to the point that it could
-     lead to SQL injections and similar security issues.  If the
-     parameter is set to off, this syntax will be rejected with an
-     error message.
-    </para>
-
-    <para>
-     To include the escape character in the string literally, write it
-     twice.
-    </para>
-   </sect3>
-
-   <sect3 id="sql-syntax-dollar-quoting">
-    <title>Dollar-quoted String Constants</title>
-
-     <indexterm>
-      <primary>dollar quoting</primary>
-     </indexterm>
-&common;
-    <para>
-     While the standard syntax for specifying string constants is usually
-     convenient, it can be difficult to understand when the desired string
-     contains many single quotes or backslashes, since each of those must
-     be doubled. To allow more readable queries in such situations,
-<!## PG>
-     <productname>PostgreSQL</productname> provides another way, called
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> provides another way, called
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> provides another way, called
-<!## end>
-     <quote>dollar quoting</quote>, to write string constants.
-     A dollar-quoted string constant
-     consists of a dollar sign (<literal>$</literal>), an optional
-     <quote>tag</quote> of zero or more characters, another dollar
-     sign, an arbitrary sequence of characters that makes up the
-     string content, a dollar sign, the same tag that began this
-     dollar quote, and a dollar sign. For example, here are two
-     different ways to specify the string <quote>Dianne's horse</>
-     using dollar quoting:
-<programlisting>
-$$Dianne's horse$$
-$SomeTag$Dianne's horse$SomeTag$
-</programlisting>
-     Notice that inside the dollar-quoted string, single quotes can be
-     used without needing to be escaped.  Indeed, no characters inside
-     a dollar-quoted string are ever escaped: the string content is always
-     written literally.  Backslashes are not special, and neither are
-     dollar signs, unless they are part of a sequence matching the opening
-     tag.
-    </para>
-
-    <para>
-     It is possible to nest dollar-quoted string constants by choosing
-     different tags at each nesting level.  This is most commonly used in
-     writing function definitions.  For example:
-<programlisting>
-$function$
-BEGIN
-    RETURN ($1 ~ $q$[\t\r\n\v\\]$q$);
-END;
-$function$
-</programlisting>
-     Here, the sequence <literal>$q$[\t\r\n\v\\]$q$</> represents a
-     dollar-quoted literal string <literal>[\t\r\n\v\\]</>, which will
-     be recognized when the function body is executed by
-<!## PG>
-     <productname>PostgreSQL</>.  But since the sequence does not match
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</>.  But since the sequence does not match
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</>.  But since the sequence does not match
-<!## end>
-     the outer dollar quoting delimiter <literal>$function$</>, it is
-     just some more characters within the constant so far as the outer
-     string is concerned.
-    </para>
-
-    <para>
-     The tag, if any, of a dollar-quoted string follows the same rules
-     as an unquoted identifier, except that it cannot contain a dollar sign.
-     Tags are case sensitive, so <literal>$tag$String content$tag$</literal>
-     is correct, but <literal>$TAG$String content$tag$</literal> is not.
-    </para>
-
-    <para>
-     A dollar-quoted string that follows a keyword or identifier must
-     be separated from it by whitespace; otherwise the dollar quoting
-     delimiter would be taken as part of the preceding identifier.
-    </para>
-
-    <para>
-     Dollar quoting is not part of the SQL standard, but it is often a more
-     convenient way to write complicated string literals than the
-     standard-compliant single quote syntax.  It is particularly useful when
-     representing string constants inside other constants, as is often needed
-     in procedural function definitions.  With single-quote syntax, each
-     backslash in the above example would have to be written as four
-     backslashes, which would be reduced to two backslashes in parsing the
-     original string constant, and then to one when the inner string constant
-     is re-parsed during function execution.
-    </para>
-   </sect3>
-
-   <sect3 id="sql-syntax-bit-strings">
-    <title>Bit-string Constants</title>
-
-    <indexterm zone="sql-syntax-bit-strings">
-     <primary>bit string</primary>
-     <secondary>constant</secondary>
-    </indexterm>
-&common;
-
-    <para>
-     Bit-string constants look like regular string constants with a
-     <literal>B</literal> (upper or lower case) immediately before the
-     opening quote (no intervening whitespace), e.g.,
-     <literal>B'1001'</literal>.  The only characters allowed within
-     bit-string constants are <literal>0</literal> and
-     <literal>1</literal>.
-    </para>
-
-    <para>
-     Alternatively, bit-string constants can be specified in hexadecimal
-     notation, using a leading <literal>X</literal> (upper or lower case),
-     e.g., <literal>X'1FF'</literal>.  This notation is equivalent to
-     a bit-string constant with four binary digits for each hexadecimal digit.
-    </para>
-
-    <para>
-     Both forms of bit-string constant can be continued
-     across lines in the same way as regular string constants.
-     Dollar quoting cannot be used in a bit-string constant.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Numeric Constants</title>
-
-    <indexterm>
-     <primary>number</primary>
-     <secondary>constant</secondary>
-    </indexterm>
-&common;
-
-    <para>
-     Numeric constants are accepted in these general forms:
-<synopsis>
-<replaceable>digits</replaceable>
-<replaceable>digits</replaceable>.<optional><replaceable>digits</replaceable></optional><optional>e<optional>+-</optional><replaceable>digits</replaceable></optional>
-<optional><replaceable>digits</replaceable></optional>.<replaceable>digits</replaceable><optional>e<optional>+-</optional><replaceable>digits</replaceable></optional>
-<replaceable>digits</replaceable>e<optional>+-</optional><replaceable>digits</replaceable>
-</synopsis>
-     where <replaceable>digits</replaceable> is one or more decimal
-     digits (0 through 9).  At least one digit must be before or after the
-     decimal point, if one is used.  At least one digit must follow the
-     exponent marker (<literal>e</literal>), if one is present.
-     There cannot be any spaces or other characters embedded in the
-     constant.  Note that any leading plus or minus sign is not actually
-     considered part of the constant; it is an operator applied to the
-     constant.
-    </para>
-
-    <para>
-     These are some examples of valid numeric constants:
-<literallayout>
-42
-3.5
-4.
-.001
-5e2
-1.925e-3
-</literallayout>
-    </para>
-
-    <para>
-     <indexterm><primary>integer</primary></indexterm>
-     <indexterm><primary>bigint</primary></indexterm>
-     <indexterm><primary>numeric</primary></indexterm>
-     A numeric constant that contains neither a decimal point nor an
-     exponent is initially presumed to be type <type>integer</> if its
-     value fits in type <type>integer</> (32 bits); otherwise it is
-     presumed to be type <type>bigint</> if its
-     value fits in type <type>bigint</> (64 bits); otherwise it is
-     taken to be type <type>numeric</>.  Constants that contain decimal
-     points and/or exponents are always initially presumed to be type
-     <type>numeric</>.
-    </para>
-
-    <para>
-     The initially assigned data type of a numeric constant is just a
-     starting point for the type resolution algorithms.  In most cases
-     the constant will be automatically coerced to the most
-     appropriate type depending on context.  When necessary, you can
-     force a numeric value to be interpreted as a specific data type
-     by casting it.<indexterm><primary>type cast</primary></indexterm>
-     For example, you can force a numeric value to be treated as type
-     <type>real</> (<type>float4</>) by writing:
-
-<programlisting>
-REAL '1.23'  -- string style
-1.23::REAL   -- PostgreSQL (historical) style
-</programlisting>
-
-     These are actually just special cases of the general casting
-     notations discussed next.
-    </para>
-   </sect3>
-
-   <sect3 id="sql-syntax-constants-generic">
-    <title>Constants of Other Types</title>
-
-    <indexterm>
-     <primary>data type</primary>
-     <secondary>constant</secondary>
-    </indexterm>
-&common;
-
-    <para>
-     A constant of an <emphasis>arbitrary</emphasis> type can be
-     entered using any one of the following notations:
-<synopsis>
-<replaceable>type</replaceable> '<replaceable>string</replaceable>'
-'<replaceable>string</replaceable>'::<replaceable>type</replaceable>
-CAST ( '<replaceable>string</replaceable>' AS <replaceable>type</replaceable> )
-</synopsis>
-     The string constant's text is passed to the input conversion
-     routine for the type called <replaceable>type</replaceable>. The
-     result is a constant of the indicated type.  The explicit type
-     cast can be omitted if there is no ambiguity as to the type the
-     constant must be (for example, when it is assigned directly to a
-     table column), in which case it is automatically coerced.
-    </para>
-
-    <para>
-     The string constant can be written using either regular SQL
-     notation or dollar-quoting.
-    </para>
-
-    <para>
-     It is also possible to specify a type coercion using a function-like
-     syntax:
-<synopsis>
-<replaceable>typename</replaceable> ( '<replaceable>string</replaceable>' )
-</synopsis>
-     but not all type names can be used in this way; see <xref
-     linkend="sql-syntax-type-casts"> for details.
-    </para>
-
-    <para>
-     The <literal>::</literal>, <literal>CAST()</literal>, and
-     function-call syntaxes can also be used to specify run-time type
-     conversions of arbitrary expressions, as discussed in <xref
-     linkend="sql-syntax-type-casts">.  To avoid syntactic ambiguity, the
-     <literal><replaceable>type</> '<replaceable>string</>'</literal>
-     syntax can only be used to specify the type of a simple literal constant.
-     Another restriction on the
-     <literal><replaceable>type</> '<replaceable>string</>'</literal>
-     syntax is that it does not work for array types; use <literal>::</literal>
-     or <literal>CAST()</literal> to specify the type of an array constant.
-    </para>
-
-    <para>
-     The <literal>CAST()</> syntax conforms to SQL.  The
-     <literal><replaceable>type</> '<replaceable>string</>'</literal>
-     syntax is a generalization of the standard: SQL specifies this syntax only
-<!## PG>
-     for a few data types, but <productname>PostgreSQL</productname> allows it
-<!## end>
-<!## XC>
-     for a few data types, but <productname>Postgres-XC</productname> allows it
-<!## end>
-<!## XL>
-     for a few data types, but <productname>Postgres-XL</productname> allows it
-<!## end>
-     for all types.  The syntax with
-<!## PG>
-     <literal>::</literal> is historical <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-     <literal>::</literal> is historical <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-     <literal>::</literal> is historical <productname>Postgres-XL</productname>
-<!## end>
-     usage, as is the function-call syntax.
-    </para>
-   </sect3>
-  </sect2>
-
-  <sect2 id="sql-syntax-operators">
-   <title>Operators</title>
-
-   <indexterm zone="sql-syntax-operators">
-    <primary>operator</primary>
-    <secondary>syntax</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    An operator name is a sequence of up to <symbol>NAMEDATALEN</symbol>-1
-    (63 by default) characters from the following list:
-<literallayout>
-+ - * / &lt; &gt; = ~ ! @ # % ^ &amp; | ` ?
-</literallayout>
-
-    There are a few restrictions on operator names, however:
-    <itemizedlist>
-     <listitem>
-      <para>
-       <literal>--</literal> and <literal>/*</literal> cannot appear
-       anywhere in an operator name, since they will be taken as the
-       start of a comment.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       A multiple-character operator name cannot end in <literal>+</> or <literal>-</>,
-       unless the name also contains at least one of these characters:
-<literallayout>
-~ ! @ # % ^ &amp; | ` ?
-</literallayout>
-       For example, <literal>@-</literal> is an allowed operator name,
-       but <literal>*-</literal> is not.  This restriction allows
-<!## PG>
-       <productname>PostgreSQL</productname> to parse SQL-compliant
-<!## end>
-<!## XC>
-       <productname>Postgres-XC</productname> to parse SQL-compliant
-<!## end>
-<!## XL>
-       <productname>Postgres-XL</productname> to parse SQL-compliant
-<!## end>
-       queries without requiring spaces between tokens.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    When working with non-SQL-standard operator names, you will usually
-    need to separate adjacent operators with spaces to avoid ambiguity.
-    For example, if you have defined a left unary operator named <literal>@</literal>,
-    you cannot write <literal>X*@Y</literal>; you must write
-    <literal>X* @Y</literal> to ensure that
-<!## PG>
-    <productname>PostgreSQL</productname> reads it as two operator names
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> reads it as two operator names
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> reads it as two operator names
-<!## end>
-    not one.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Special Characters</title>
-&common;
-
-  <para>
-   Some characters that are not alphanumeric have a special meaning
-   that is different from being an operator.  Details on the usage can
-   be found at the location where the respective syntax element is
-   described.  This section only exists to advise the existence and
-   summarize the purposes of these characters.
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      A dollar sign (<literal>$</literal>) followed by digits is used
-      to represent a positional parameter in the body of a function
-      definition or a prepared statement.  In other contexts the
-      dollar sign can be part of an identifier or a dollar-quoted string
-      constant.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Parentheses (<literal>()</literal>) have their usual meaning to
-      group expressions and enforce precedence.  In some cases
-      parentheses are required as part of the fixed syntax of a
-      particular SQL command.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Brackets (<literal>[]</literal>) are used to select the elements
-      of an array.  See <xref linkend="arrays"> for more information
-      on arrays.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Commas (<literal>,</literal>) are used in some syntactical
-      constructs to separate the elements of a list.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The semicolon (<literal>;</literal>) terminates an SQL command.
-      It cannot appear anywhere within a command, except within a
-      string constant or quoted identifier.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The colon (<literal>:</literal>) is used to select
-      <quote>slices</quote> from arrays. (See <xref
-      linkend="arrays">.)  In certain SQL dialects (such as Embedded
-      SQL), the colon is used to prefix variable names.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The asterisk (<literal>*</literal>) is used in some contexts to denote
-      all the fields of a table row or composite value.  It also
-      has a special meaning when used as the argument of an
-      aggregate function, namely that the aggregate does not require
-      any explicit parameter.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The period (<literal>.</literal>) is used in numeric
-      constants, and to separate schema, table, and column names.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   </para>
-  </sect2>
-
-  <sect2 id="sql-syntax-comments">
-   <title>Comments</title>
-
-   <indexterm zone="sql-syntax-comments">
-    <primary>comment</primary>
-    <secondary sortas="SQL">in SQL</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    A comment is a sequence of characters beginning with
-    double dashes and extending to the end of the line, e.g.:
-<programlisting>
--- This is a standard SQL comment
-</programlisting>
-   </para>
-
-   <para>
-    Alternatively, C-style block comments can be used:
-<programlisting>
-/* multiline comment
- * with nesting: /* nested block comment */
- */
-</programlisting>
-    where the comment begins with <literal>/*</literal> and extends to
-    the matching occurrence of <literal>*/</literal>. These block
-    comments nest, as specified in the SQL standard but unlike C, so that one can
-    comment out larger blocks of code that might contain existing block
-    comments.
-   </para>
-
-   <para>
-    A comment is removed from the input stream before further syntax
-    analysis and is effectively replaced by whitespace.
-   </para>
-  </sect2>
-
-  <sect2 id="sql-precedence">
-   <title>Operator Precedence</title>
-
-   <indexterm zone="sql-precedence">
-    <primary>operator</primary>
-    <secondary>precedence</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    <xref linkend="sql-precedence-table"> shows the precedence and
-<!## PG>
-    associativity of the operators in <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-    associativity of the operators in <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-    associativity of the operators in <productname>Postgres-XL</>.
-<!## end>
-    Most operators have the same precedence and are left-associative.
-    The precedence and associativity of the operators is hard-wired
-    into the parser.  This can lead to non-intuitive behavior; for
-    example the Boolean operators <literal>&lt;</> and
-    <literal>&gt;</> have a different precedence than the Boolean
-    operators <literal>&lt;=</> and <literal>&gt;=</>.  Also, you will
-    sometimes need to add parentheses when using combinations of
-    binary and unary operators.  For instance:
-<programlisting>
-SELECT 5 ! - 6;
-</programlisting>
-   will be parsed as:
-<programlisting>
-SELECT 5 ! (- 6);
-</programlisting>
-    because the parser has no idea &mdash; until it is too late
-    &mdash; that <token>!</token> is defined as a postfix operator,
-    not an infix one.  To get the desired behavior in this case, you
-    must write:
-<programlisting>
-SELECT (5 !) - 6;
-</programlisting>
-    This is the price one pays for extensibility.
-   </para>
-
-   <table id="sql-precedence-table">
-    <title>Operator Precedence (decreasing)</title>
-
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Operator/Element</entry>
-       <entry>Associativity</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><token>.</token></entry>
-       <entry>left</entry>
-       <entry>table/column name separator</entry>
-      </row>
-
-      <row>
-       <entry><token>::</token></entry>
-       <entry>left</entry>
-<!## PG>
-       <entry><productname>PostgreSQL</productname>-style typecast</entry>
-<!## end>
-<!## XC>
-       <entry><productname>Postgres-XC</productname>-style typecast</entry>
-<!## end>
-<!## XL>
-       <entry><productname>Postgres-XL</productname>-style typecast</entry>
-<!## end>
-      </row>
-
-      <row>
-       <entry><token>[</token> <token>]</token></entry>
-       <entry>left</entry>
-       <entry>array element selection</entry>
-      </row>
-
-      <row>
-       <entry><token>+</token> <token>-</token></entry>
-       <entry>right</entry>
-       <entry>unary plus, unary minus</entry>
-      </row>
-
-      <row>
-       <entry><token>^</token></entry>
-       <entry>left</entry>
-       <entry>exponentiation</entry>
-      </row>
-
-      <row>
-       <entry><token>*</token> <token>/</token> <token>%</token></entry>
-       <entry>left</entry>
-       <entry>multiplication, division, modulo</entry>
-      </row>
-
-      <row>
-       <entry><token>+</token> <token>-</token></entry>
-       <entry>left</entry>
-       <entry>addition, subtraction</entry>
-      </row>
-
-      <row>
-       <entry><token>IS</token></entry>
-       <entry></entry>
-       <entry><literal>IS TRUE</>, <literal>IS FALSE</>, <literal>IS NULL</>, etc</entry>
-      </row>
-
-      <row>
-       <entry><token>ISNULL</token></entry>
-       <entry></entry>
-       <entry>test for null</entry>
-      </row>
-
-      <row>
-       <entry><token>NOTNULL</token></entry>
-       <entry></entry>
-       <entry>test for not null</entry>
-      </row>
-
-      <row>
-       <entry>(any other)</entry>
-       <entry>left</entry>
-       <entry>all other native and user-defined operators</entry>
-      </row>
-
-      <row>
-       <entry><token>IN</token></entry>
-       <entry></entry>
-       <entry>set membership</entry>
-      </row>
-
-      <row>
-       <entry><token>BETWEEN</token></entry>
-       <entry></entry>
-       <entry>range containment</entry>
-      </row>
-
-      <row>
-       <entry><token>OVERLAPS</token></entry>
-       <entry></entry>
-       <entry>time interval overlap</entry>
-      </row>
-
-      <row>
-       <entry><token>LIKE</token> <token>ILIKE</token> <token>SIMILAR</token></entry>
-       <entry></entry>
-       <entry>string pattern matching</entry>
-      </row>
-
-      <row>
-       <entry><token>&lt;</token> <token>&gt;</token></entry>
-       <entry></entry>
-       <entry>less than, greater than</entry>
-      </row>
-
-      <row>
-       <entry><token>=</token></entry>
-       <entry>right</entry>
-       <entry>equality, assignment</entry>
-      </row>
-
-      <row>
-       <entry><token>NOT</token></entry>
-       <entry>right</entry>
-       <entry>logical negation</entry>
-      </row>
-
-      <row>
-       <entry><token>AND</token></entry>
-       <entry>left</entry>
-       <entry>logical conjunction</entry>
-      </row>
-
-      <row>
-       <entry><token>OR</token></entry>
-       <entry>left</entry>
-       <entry>logical disjunction</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    Note that the operator precedence rules also apply to user-defined
-    operators that have the same names as the built-in operators
-    mentioned above.  For example, if you define a
-    <quote>+</quote> operator for some custom data type it will have
-    the same precedence as the built-in <quote>+</quote> operator, no
-    matter what yours does.
-   </para>
-
-   <para>
-    When a schema-qualified operator name is used in the
-    <literal>OPERATOR</> syntax, as for example in:
-<programlisting>
-SELECT 3 OPERATOR(pg_catalog.+) 4;
-</programlisting>
-    the <literal>OPERATOR</> construct is taken to have the default precedence
-    shown in <xref linkend="sql-precedence-table"> for <quote>any other</> operator.  This is true no matter
-    which specific operator appears inside <literal>OPERATOR()</>.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="sql-expressions">
-  <title>Value Expressions</title>
-
-  <indexterm zone="sql-expressions">
-   <primary>expression</primary>
-   <secondary>syntax</secondary>
-  </indexterm>
-
-  <indexterm zone="sql-expressions">
-   <primary>value expression</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>scalar</primary>
-   <see>expression</see>
-  </indexterm>
-&common;
-
-  <para>
-   Value expressions are used in a variety of contexts, such
-   as in the target list of the <command>SELECT</command> command, as
-   new column values in <command>INSERT</command> or
-   <command>UPDATE</command>, or in search conditions in a number of
-   commands.  The result of a value expression is sometimes called a
-   <firstterm>scalar</firstterm>, to distinguish it from the result of
-   a table expression (which is a table).  Value expressions are
-   therefore also called <firstterm>scalar expressions</firstterm> (or
-   even simply <firstterm>expressions</firstterm>).  The expression
-   syntax allows the calculation of values from primitive parts using
-   arithmetic, logical, set, and other operations.
-  </para>
-
-  <para>
-   A value expression is one of the following:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      A constant or literal value
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A column reference
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A positional parameter reference, in the body of a function definition
-      or prepared statement
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A subscripted expression
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A field selection expression
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      An operator invocation
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A function call
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      An aggregate expression
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A window function call
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A type cast
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A collation expression
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A scalar subquery
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      An array constructor
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A row constructor
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Another value expression in parentheses (used to group
-      subexpressions and override
-      precedence<indexterm><primary>parenthesis</></>)
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   In addition to this list, there are a number of constructs that can
-   be classified as an expression but do not follow any general syntax
-   rules.  These generally have the semantics of a function or
-   operator and are explained in the appropriate location in <xref
-   linkend="functions">.  An example is the <literal>IS NULL</literal>
-   clause.
-  </para>
-
-  <para>
-   We have already discussed constants in <xref
-   linkend="sql-syntax-constants">.  The following sections discuss
-   the remaining options.
-  </para>
-
-  <sect2>
-   <title>Column References</title>
-
-   <indexterm>
-    <primary>column reference</primary>
-   </indexterm>
-&common;
-
-   <para>
-    A column can be referenced in the form:
-<synopsis>
-<replaceable>correlation</replaceable>.<replaceable>columnname</replaceable>
-</synopsis>
-   </para>
-
-   <para>
-    <replaceable>correlation</replaceable> is the name of a
-    table (possibly qualified with a schema name), or an alias for a table
-    defined by means of a <literal>FROM</literal> clause.
-    The correlation name and separating dot can be omitted if the column name
-    is unique across all the tables being used in the current query.  (See also <xref linkend="queries">.)
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Positional Parameters</title>
-
-   <indexterm>
-    <primary>parameter</primary>
-    <secondary>syntax</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>$</primary>
-   </indexterm>
-&common;
-
-   <para>
-    A positional parameter reference is used to indicate a value
-    that is supplied externally to an SQL statement.  Parameters are
-    used in SQL function definitions and in prepared queries.  Some
-    client libraries also support specifying data values separately
-    from the SQL command string, in which case parameters are used to
-    refer to the out-of-line data values.
-    The form of a parameter reference is:
-<synopsis>
-$<replaceable>number</replaceable>
-</synopsis>
-   </para>
-
-   <para>
-    For example, consider the definition of a function,
-    <function>dept</function>, as:
-
-<programlisting>
-CREATE FUNCTION dept(text) RETURNS dept
-    AS $$ SELECT * FROM dept WHERE name = $1 $$
-    LANGUAGE SQL;
-</programlisting>
-
-    Here the <literal>$1</literal> references the value of the first
-    function argument whenever the function is invoked.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Subscripts</title>
-
-   <indexterm>
-    <primary>subscript</primary>
-   </indexterm>
-&common;
-
-   <para>
-    If an expression yields a value of an array type, then a specific
-    element of the array value can be extracted by writing
-<synopsis>
-<replaceable>expression</replaceable>[<replaceable>subscript</replaceable>]
-</synopsis>
-    or multiple adjacent elements (an <quote>array slice</>) can be extracted
-    by writing
-<synopsis>
-<replaceable>expression</replaceable>[<replaceable>lower_subscript</replaceable>:<replaceable>upper_subscript</replaceable>]
-</synopsis>
-    (Here, the brackets <literal>[ ]</literal> are meant to appear literally.)
-    Each <replaceable>subscript</replaceable> is itself an expression,
-    which must yield an integer value.
-   </para>
-
-   <para>
-    In general the array <replaceable>expression</replaceable> must be
-    parenthesized, but the parentheses can be omitted when the expression
-    to be subscripted is just a column reference or positional parameter.
-    Also, multiple subscripts can be concatenated when the original array
-    is multidimensional.
-    For example:
-
-<programlisting>
-mytable.arraycolumn[4]
-mytable.two_d_column[17][34]
-$1[10:42]
-(arrayfunction(a,b))[42]
-</programlisting>
-
-    The parentheses in the last example are required.
-    See <xref linkend="arrays"> for more about arrays.
-   </para>
-  </sect2>
-
-  <sect2 id="field-selection">
-   <title>Field Selection</title>
-
-   <indexterm>
-    <primary>field selection</primary>
-   </indexterm>
-&common;
-
-   <para>
-    If an expression yields a value of a composite type (row type), then a
-    specific field of the row can be extracted by writing
-<synopsis>
-<replaceable>expression</replaceable>.<replaceable>fieldname</replaceable>
-</synopsis>
-   </para>
-
-   <para>
-    In general the row <replaceable>expression</replaceable> must be
-    parenthesized, but the parentheses can be omitted when the expression
-    to be selected from is just a table reference or positional parameter.
-    For example:
-
-<programlisting>
-mytable.mycolumn
-$1.somecolumn
-(rowfunction(a,b)).col3
-</programlisting>
-
-    (Thus, a qualified column reference is actually just a special case
-    of the field selection syntax.)  An important special case is
-    extracting a field from a table column that is of a composite type:
-
-<programlisting>
-(compositecol).somefield
-(mytable.compositecol).somefield
-</programlisting>
-
-    The parentheses are required here to show that
-    <structfield>compositecol</> is a column name not a table name,
-    or that <structname>mytable</> is a table name not a schema name
-    in the second case.
-   </para>
-
-   <para>
-    In a select list (see <xref linkend="queries-select-lists">), you
-    can ask for all fields of a composite value by
-    writing <literal>.*</literal>:
-<programlisting>
-(compositecol).*
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Operator Invocations</title>
-
-   <indexterm>
-    <primary>operator</primary>
-    <secondary>invocation</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    There are three possible syntaxes for an operator invocation:
-    <simplelist>
-     <member><replaceable>expression</replaceable> <replaceable>operator</replaceable> <replaceable>expression</replaceable> (binary infix operator)</member>
-     <member><replaceable>operator</replaceable> <replaceable>expression</replaceable> (unary prefix operator)</member>
-     <member><replaceable>expression</replaceable> <replaceable>operator</replaceable> (unary postfix operator)</member>
-    </simplelist>
-    where the <replaceable>operator</replaceable> token follows the syntax
-    rules of <xref linkend="sql-syntax-operators">, or is one of the
-    key words <token>AND</token>, <token>OR</token>, and
-    <token>NOT</token>, or is a qualified operator name in the form:
-<synopsis>
-<literal>OPERATOR(</><replaceable>schema</><literal>.</><replaceable>operatorname</><literal>)</>
-</synopsis>
-    Which particular operators exist and whether
-    they are unary or binary depends on what operators have been
-    defined by the system or the user.  <xref linkend="functions">
-    describes the built-in operators.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Function Calls</title>
-
-   <indexterm>
-    <primary>function</primary>
-    <secondary>invocation</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    The syntax for a function call is the name of a function
-    (possibly qualified with a schema name), followed by its argument list
-    enclosed in parentheses:
-
-<synopsis>
-<replaceable>function_name</replaceable> (<optional><replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ... </optional></optional> )
-</synopsis>
-   </para>
-
-   <para>
-    For example, the following computes the square root of 2:
-<programlisting>
-sqrt(2)
-</programlisting>
-   </para>
-
-   <para>
-    The list of built-in functions is in <xref linkend="functions">.
-    Other functions can be added by the user.
-   </para>
-
-   <para>
-    The arguments can optionally have names attached.
-    See <xref linkend="sql-syntax-calling-funcs"> for details.
-   </para>
-
-   <note>
-    <para>
-     A function that takes a single argument of composite type can
-     optionally be called using field-selection syntax, and conversely
-     field selection can be written in functional style.  That is, the
-     notations <literal>col(table)</> and <literal>table.col</> are
-     interchangeable.  This behavior is not SQL-standard but is provided
-     in <productname>PostgreSQL</> because it allows use of functions to
-     emulate <quote>computed fields</>.  For more information see
-     <xref linkend="xfunc-sql-composite-functions">.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2 id="syntax-aggregates">
-   <title>Aggregate Expressions</title>
-
-   <indexterm zone="syntax-aggregates">
-    <primary>aggregate function</primary>
-    <secondary>invocation</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    An <firstterm>aggregate expression</firstterm> represents the
-    application of an aggregate function across the rows selected by a
-    query.  An aggregate function reduces multiple inputs to a single
-    output value, such as the sum or average of the inputs.  The
-    syntax of an aggregate expression is one of the following:
-
-<synopsis>
-<replaceable>aggregate_name</replaceable> (<replaceable>expression</replaceable> [ , ... ] [ <replaceable>order_by_clause</replaceable> ] )
-<replaceable>aggregate_name</replaceable> (ALL <replaceable>expression</replaceable> [ , ... ] [ <replaceable>order_by_clause</replaceable> ] )
-<replaceable>aggregate_name</replaceable> (DISTINCT <replaceable>expression</replaceable> [ , ... ] [ <replaceable>order_by_clause</replaceable> ] )
-<replaceable>aggregate_name</replaceable> ( * )
-</synopsis>
-
-    where <replaceable>aggregate_name</replaceable> is a previously
-    defined aggregate (possibly qualified with a schema name),
-    <replaceable>expression</replaceable> is
-    any value expression that does not itself contain an aggregate
-    expression or a window function call, and
-    <replaceable>order_by_clause</replaceable> is a optional
-    <literal>ORDER BY</> clause as described below.
-   </para>
-
-   <para>
-    The first form of aggregate expression invokes the aggregate
-    once for each input row.
-    The second form is the same as the first, since
-    <literal>ALL</literal> is the default.
-    The third form invokes the aggregate once for each distinct value
-    of the expression (or distinct set of values, for multiple expressions)
-    found in the input rows.
-    The last form invokes the aggregate once for each input row; since no
-    particular input value is specified, it is generally only useful
-    for the <function>count(*)</function> aggregate function.
-   </para>
-
-   <para>
-    Most aggregate functions ignore null inputs, so that rows in which
-    one or more of the expression(s) yield null are discarded.  This
-    can be assumed to be true, unless otherwise specified, for all
-    built-in aggregates.
-   </para>
-
-   <para>
-    For example, <literal>count(*)</literal> yields the total number
-    of input rows; <literal>count(f1)</literal> yields the number of
-    input rows in which <literal>f1</literal> is non-null, since
-    <function>count</> ignores nulls; and
-    <literal>count(distinct f1)</literal> yields the number of
-    distinct non-null values of <literal>f1</literal>.
-   </para>
-
-   <para>
-    Ordinarily, the input rows are fed to the aggregate function in an
-    unspecified order.  In many cases this does not matter; for example,
-    <function>min</> produces the same result no matter what order it
-    receives the inputs in.  However, some aggregate functions
-    (such as <function>array_agg</> and <function>string_agg</>) produce
-    results that depend on the ordering of the input rows.  When using
-    such an aggregate, the optional <replaceable>order_by_clause</> can be
-    used to specify the desired ordering.  The <replaceable>order_by_clause</>
-    has the same syntax as for a query-level <literal>ORDER BY</> clause, as
-    described in <xref linkend="queries-order">, except that its expressions
-    are always just expressions and cannot be output-column names or numbers.
-    For example:
-<programlisting>
-SELECT array_agg(a ORDER BY b DESC) FROM table;
-</programlisting>
-   </para>
-
-   <para>
-    When dealing with multiple-argument aggregate functions, note that the
-    <literal>ORDER BY</> clause goes after all the aggregate arguments.
-    For example, write this:
-<programlisting>
-SELECT string_agg(a, ',' ORDER BY a) FROM table;
-</programlisting>
-    not this:
-<programlisting>
-SELECT string_agg(a ORDER BY a, ',') FROM table;  -- incorrect
-</programlisting>
-    The latter is syntactically valid, but it represents a call of a
-    single-argument aggregate function with two <literal>ORDER BY</> keys
-    (the second one being rather useless since it's a constant).
-   </para>
-
-   <para>
-    If <literal>DISTINCT</> is specified in addition to an
-    <replaceable>order_by_clause</>, then all the <literal>ORDER BY</>
-    expressions must match regular arguments of the aggregate; that is,
-    you cannot sort on an expression that is not included in the
-    <literal>DISTINCT</> list.
-   </para>
-
-   <note>
-    <para>
-     The ability to specify both <literal>DISTINCT</> and <literal>ORDER BY</>
-<!## PG>
-     in an aggregate function is a <productname>PostgreSQL</> extension.
-<!## end>
-<!## XC>
-     in an aggregate function is a <productname>Postgres-XC</> extension.
-<!## end>
-<!## XL>
-     in an aggregate function is a <productname>Postgres-XL</> extension.
-<!## end>
-    </para>
-   </note>
-
-   <para>
-    The predefined aggregate functions are described in <xref
-    linkend="functions-aggregate">.  Other aggregate functions can be added
-    by the user.
-   </para>
-
-   <para>
-    An aggregate expression can only appear in the result list or
-    <literal>HAVING</> clause of a <command>SELECT</> command.
-    It is forbidden in other clauses, such as <literal>WHERE</>,
-    because those clauses are logically evaluated before the results
-    of aggregates are formed.
-   </para>
-
-   <para>
-    When an aggregate expression appears in a subquery (see
-    <xref linkend="sql-syntax-scalar-subqueries"> and
-    <xref linkend="functions-subquery">), the aggregate is normally
-    evaluated over the rows of the subquery.  But an exception occurs
-    if the aggregate's arguments contain only outer-level variables:
-    the aggregate then belongs to the nearest such outer level, and is
-    evaluated over the rows of that query.  The aggregate expression
-    as a whole is then an outer reference for the subquery it appears in,
-    and acts as a constant over any one evaluation of that subquery.
-    The restriction about
-    appearing only in the result list or <literal>HAVING</> clause
-    applies with respect to the query level that the aggregate belongs to.
-   </para>
-  </sect2>
-
-  <sect2 id="syntax-window-functions">
-   <title>Window Function Calls</title>
-
-   <indexterm zone="syntax-window-functions">
-    <primary>window function</primary>
-    <secondary>invocation</secondary>
-   </indexterm>
-
-   <indexterm zone="syntax-window-functions">
-    <primary>OVER clause</primary>
-   </indexterm>
-
-   <para>
-    A <firstterm>window function call</firstterm> represents the application
-    of an aggregate-like function over some portion of the rows selected
-    by a query.  Unlike regular aggregate function calls, this is not tied
-    to grouping of the selected rows into a single output row &mdash; each
-    row remains separate in the query output.  However the window function
-    is able to scan all the rows that would be part of the current row's
-    group according to the grouping specification (<literal>PARTITION BY</>
-    list) of the window function call.
-    The syntax of a window function call is one of the following:
-
-<synopsis>
-<replaceable>function_name</replaceable> (<optional><replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ... </optional></optional>) OVER ( <replaceable class="parameter">window_definition</replaceable> )
-<replaceable>function_name</replaceable> (<optional><replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ... </optional></optional>) OVER <replaceable>window_name</replaceable>
-<replaceable>function_name</replaceable> ( * ) OVER ( <replaceable class="parameter">window_definition</replaceable> )
-<replaceable>function_name</replaceable> ( * ) OVER <replaceable>window_name</replaceable>
-</synopsis>
-    where <replaceable class="parameter">window_definition</replaceable>
-    has the syntax
-<synopsis>
-[ <replaceable class="parameter">existing_window_name</replaceable> ]
-[ PARTITION BY <replaceable class="parameter">expression</replaceable> [, ...] ]
-[ ORDER BY <replaceable class="parameter">expression</replaceable> [ ASC | DESC | USING <replaceable class="parameter">operator</replaceable> ] [ NULLS { FIRST | LAST } ] [, ...] ]
-[ <replaceable class="parameter">frame_clause</replaceable> ]
-</synopsis>
-    and the optional <replaceable class="parameter">frame_clause</replaceable>
-    can be one of
-<synopsis>
-[ RANGE | ROWS ] <replaceable>frame_start</>
-[ RANGE | ROWS ] BETWEEN <replaceable>frame_start</> AND <replaceable>frame_end</>
-</synopsis>
-    where <replaceable>frame_start</> and <replaceable>frame_end</> can be
-    one of
-<synopsis>
-UNBOUNDED PRECEDING
-<replaceable>value</replaceable> PRECEDING
-CURRENT ROW
-<replaceable>value</replaceable> FOLLOWING
-UNBOUNDED FOLLOWING
-</synopsis>
-   </para>
-
-   <para>
-    Here, <replaceable>expression</replaceable> represents any value
-    expression that does not itself contain window function calls.
-    The <literal>PARTITION BY</> and <literal>ORDER BY</> lists have
-    essentially the same syntax and semantics as <literal>GROUP BY</>
-    and <literal>ORDER BY</> clauses of the whole query, except that their
-    expressions are always just expressions and cannot be output-column
-    names or numbers.
-    <replaceable>window_name</replaceable> is a reference to a named window
-    specification defined in the query's <literal>WINDOW</literal> clause.
-    Named window specifications are usually referenced with just
-    <literal>OVER</> <replaceable>window_name</replaceable>, but it is
-    also possible to write a window name inside the parentheses and then
-    optionally supply an ordering clause and/or frame clause (the referenced
-    window must lack these clauses, if they are supplied here).
-    This latter syntax follows the same rules as modifying an existing
-    window name within the <literal>WINDOW</literal> clause; see the
-    <xref linkend="sql-select"> reference
-    page for details.
-   </para>
-
-   <para>
-    The <replaceable class="parameter">frame_clause</replaceable> specifies
-    the set of rows constituting the <firstterm>window frame</>, for those
-    window functions that act on the frame instead of the whole partition.
-    If <replaceable>frame_end</> is omitted it defaults to <literal>CURRENT
-    ROW</>.  Restrictions are that
-    <replaceable>frame_start</> cannot be <literal>UNBOUNDED FOLLOWING</>,
-    <replaceable>frame_end</> cannot be <literal>UNBOUNDED PRECEDING</>,
-    and the <replaceable>frame_end</> choice cannot appear earlier in the
-    above list than the <replaceable>frame_start</> choice &mdash; for example
-    <literal>RANGE BETWEEN CURRENT ROW AND <replaceable>value</>
-    PRECEDING</literal> is not allowed.
-    The default framing option is <literal>RANGE UNBOUNDED PRECEDING</>,
-    which is the same as <literal>RANGE BETWEEN UNBOUNDED PRECEDING AND
-    CURRENT ROW</>; it sets the frame to be all rows from the partition start
-    up through the current row's last peer in the <literal>ORDER BY</>
-    ordering (which means all rows if there is no <literal>ORDER BY</>).
-    In general, <literal>UNBOUNDED PRECEDING</> means that the frame
-    starts with the first row of the partition, and similarly
-    <literal>UNBOUNDED FOLLOWING</> means that the frame ends with the last
-    row of the partition (regardless of <literal>RANGE</> or <literal>ROWS</>
-    mode).  In <literal>ROWS</> mode, <literal>CURRENT ROW</>
-    means that the frame starts or ends with the current row; but in
-    <literal>RANGE</> mode it means that the frame starts or ends with
-    the current row's first or last peer in the <literal>ORDER BY</> ordering.
-    The <replaceable>value</> <literal>PRECEDING</> and
-    <replaceable>value</> <literal>FOLLOWING</> cases are currently only
-    allowed in <literal>ROWS</> mode.  They indicate that the frame starts
-    or ends with the row that many rows before or after the current row.
-    <replaceable>value</replaceable> must be an integer expression not
-    containing any variables, aggregate functions, or window functions.
-    The value must not be null or negative; but it can be zero, which
-    selects the current row itself.
-   </para>
-
-   <para>
-    The built-in window functions are described in <xref
-    linkend="functions-window-table">.  Other window functions can be added by
-    the user.  Also, any built-in or user-defined aggregate function can be
-    used as a window function.
-   </para>
-
-   <para>
-    The syntaxes using <literal>*</> are used for calling parameter-less
-    aggregate functions as window functions, for example
-    <literal>count(*) OVER (PARTITION BY x ORDER BY y)</>.
-    <literal>*</> is customarily not used for non-aggregate window functions.
-    Aggregate window functions, unlike normal aggregate functions, do not
-    allow <literal>DISTINCT</> or <literal>ORDER BY</> to be used within the
-    function argument list.
-   </para>
-
-   <para>
-    Window function calls are permitted only in the <literal>SELECT</literal>
-    list and the <literal>ORDER BY</> clause of the query.
-   </para>
-
-   <para>
-    More information about window functions can be found in
-    <xref linkend="tutorial-window">,
-    <xref linkend="functions-window">,
-    <xref linkend="queries-window">.
-   </para>
-  </sect2>
-
-  <sect2 id="sql-syntax-type-casts">
-   <title>Type Casts</title>
-
-   <indexterm>
-    <primary>data type</primary>
-    <secondary>type cast</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>type cast</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>::</primary>
-   </indexterm>
-&common;
-
-   <para>
-    A type cast specifies a conversion from one data type to another.
-<!## PG>
-    <productname>PostgreSQL</productname> accepts two equivalent syntaxes
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> accepts two equivalent syntaxes
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> accepts two equivalent syntaxes
-<!## end>
-    for type casts:
-<synopsis>
-CAST ( <replaceable>expression</replaceable> AS <replaceable>type</replaceable> )
-<replaceable>expression</replaceable>::<replaceable>type</replaceable>
-</synopsis>
-    The <literal>CAST</> syntax conforms to SQL; the syntax with
-<!## PG>
-    <literal>::</literal> is historical <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-    <literal>::</literal> is historical <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-    <literal>::</literal> is historical <productname>Postgres-XL</productname>
-<!## end>
-    usage.
-   </para>
-
-   <para>
-    When a cast is applied to a value expression of a known type, it
-    represents a run-time type conversion.  The cast will succeed only
-    if a suitable type conversion operation has been defined.  Notice that this
-    is subtly different from the use of casts with constants, as shown in
-    <xref linkend="sql-syntax-constants-generic">.  A cast applied to an
-    unadorned string literal represents the initial assignment of a type
-    to a literal constant value, and so it will succeed for any type
-    (if the contents of the string literal are acceptable input syntax for the
-    data type).
-   </para>
-
-   <para>
-    An explicit type cast can usually be omitted if there is no ambiguity as
-    to the type that a value expression must produce (for example, when it is
-    assigned to a table column); the system will automatically apply a
-    type cast in such cases.  However, automatic casting is only done for
-    casts that are marked <quote>OK to apply implicitly</>
-    in the system catalogs.  Other casts must be invoked with
-    explicit casting syntax.  This restriction is intended to prevent
-    surprising conversions from being applied silently.
-   </para>
-
-   <para>
-    It is also possible to specify a type cast using a function-like
-    syntax:
-<synopsis>
-<replaceable>typename</replaceable> ( <replaceable>expression</replaceable> )
-</synopsis>
-    However, this only works for types whose names are also valid as
-    function names.  For example, <literal>double precision</literal>
-    cannot be used this way, but the equivalent <literal>float8</literal>
-    can.  Also, the names <literal>interval</>, <literal>time</>, and
-    <literal>timestamp</> can only be used in this fashion if they are
-    double-quoted, because of syntactic conflicts.  Therefore, the use of
-    the function-like cast syntax leads to inconsistencies and should
-    probably be avoided.
-   </para>
-
-   <note>
-    <para>
-     The function-like syntax is in fact just a function call.  When
-     one of the two standard cast syntaxes is used to do a run-time
-     conversion, it will internally invoke a registered function to
-     perform the conversion.  By convention, these conversion functions
-     have the same name as their output type, and thus the <quote>function-like
-     syntax</> is nothing more than a direct invocation of the underlying
-     conversion function.  Obviously, this is not something that a portable
-     application should rely on.  For further details see
-     <xref linkend="sql-createcast">.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2 id="sql-syntax-collate-exprs">
-   <title>Collation Expressions</title>
-
-   <indexterm>
-    <primary>COLLATE</primary>
-   </indexterm>
-
-   <para>
-    The <literal>COLLATE</literal> clause overrides the collation of
-    an expression.  It is appended to the expression it applies to:
-<synopsis>
-<replaceable>expr</replaceable> COLLATE <replaceable>collation</replaceable>
-</synopsis>
-    where <replaceable>collation</replaceable> is a possibly
-    schema-qualified identifier.  The <literal>COLLATE</literal>
-    clause binds tighter than operators; parentheses can be used when
-    necessary.
-   </para>
-
-   <para>
-    If no collation is explicitly specified, the database system
-    either derives a collation from the columns involved in the
-    expression, or it defaults to the default collation of the
-    database if no column is involved in the expression.
-   </para>
-
-   <para>
-    The two common uses of the <literal>COLLATE</literal> clause are
-    overriding the sort order in an <literal>ORDER BY</> clause, for
-    example:
-<programlisting>
-SELECT a, b, c FROM tbl WHERE ... ORDER BY a COLLATE "C";
-</programlisting>
-    and overriding the collation of a function or operator call that
-    has locale-sensitive results, for example:
-<programlisting>
-SELECT * FROM tbl WHERE a &gt; 'foo' COLLATE "C";
-</programlisting>
-    Note that in the latter case the <literal>COLLATE</> clause is
-    attached to an input argument of the operator we wish to affect.
-    It doesn't matter which argument of the operator or function call the
-    <literal>COLLATE</> clause is attached to, because the collation that is
-    applied by the operator or function is derived by considering all
-    arguments, and an explicit <literal>COLLATE</> clause will override the
-    collations of all other arguments.  (Attaching non-matching
-    <literal>COLLATE</> clauses to more than one argument, however, is an
-    error.  For more details see <xref linkend="collation">.)
-    Thus, this gives the same result as the previous example:
-<programlisting>
-SELECT * FROM tbl WHERE a COLLATE "C" &gt; 'foo';
-</programlisting>
-    But this is an error:
-<programlisting>
-SELECT * FROM tbl WHERE (a &gt; 'foo') COLLATE "C";
-</programlisting>
-    because it attempts to apply a collation to the result of the
-    <literal>&gt;</> operator, which is of the non-collatable data type
-    <type>boolean</>.
-   </para>
-  </sect2>
-
-  <sect2 id="sql-syntax-scalar-subqueries">
-   <title>Scalar Subqueries</title>
-
-   <indexterm>
-    <primary>subquery</primary>
-   </indexterm>
-&common;
-
-   <para>
-    A scalar subquery is an ordinary
-    <command>SELECT</command> query in parentheses that returns exactly one
-    row with one column.  (See <xref linkend="queries"> for information about writing queries.)
-    The <command>SELECT</command> query is executed
-    and the single returned value is used in the surrounding value expression.
-    It is an error to use a query that
-    returns more than one row or more than one column as a scalar subquery.
-    (But if, during a particular execution, the subquery returns no rows,
-    there is no error; the scalar result is taken to be null.)
-    The subquery can refer to variables from the surrounding query,
-    which will act as constants during any one evaluation of the subquery.
-    See also <xref linkend="functions-subquery"> for other expressions involving subqueries.
-   </para>
-
-   <para>
-    For example, the following finds the largest city population in each
-    state:
-<programlisting>
-SELECT name, (SELECT max(pop) FROM cities WHERE cities.state = states.name)
-    FROM states;
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="sql-syntax-array-constructors">
-   <title>Array Constructors</title>
-
-   <indexterm>
-    <primary>array</primary>
-    <secondary>constructor</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>ARRAY</primary>
-   </indexterm>
-&common;
-
-   <para>
-    An array constructor is an expression that builds an
-    array value using values for its member elements.  A simple array
-    constructor
-    consists of the key word <literal>ARRAY</literal>, a left square bracket
-    <literal>[</>, a list of expressions (separated by commas) for the
-    array element values, and finally a right square bracket <literal>]</>.
-    For example:
-<programlisting>
-SELECT ARRAY[1,2,3+4];
-  array
----------
- {1,2,7}
-(1 row)
-</programlisting>
-    By default,
-    the array element type is the common type of the member expressions,
-    determined using the same rules as for <literal>UNION</> or
-    <literal>CASE</> constructs (see <xref linkend="typeconv-union-case">).
-    You can override this by explicitly casting the array constructor to the
-    desired type, for example:
-<programlisting>
-SELECT ARRAY[1,2,22.7]::integer[];
-  array
-----------
- {1,2,23}
-(1 row)
-</programlisting>
-    This has the same effect as casting each expression to the array
-    element type individually.
-    For more on casting, see <xref linkend="sql-syntax-type-casts">.
-   </para>
-
-   <para>
-    Multidimensional array values can be built by nesting array
-    constructors.
-    In the inner constructors, the key word <literal>ARRAY</literal> can
-    be omitted.  For example, these produce the same result:
-
-<programlisting>
-SELECT ARRAY[ARRAY[1,2], ARRAY[3,4]];
-     array
----------------
- {{1,2},{3,4}}
-(1 row)
-
-SELECT ARRAY[[1,2],[3,4]];
-     array
----------------
- {{1,2},{3,4}}
-(1 row)
-</programlisting>
-
-    Since multidimensional arrays must be rectangular, inner constructors
-    at the same level must produce sub-arrays of identical dimensions.
-    Any cast applied to the outer <literal>ARRAY</> constructor propagates
-    automatically to all the inner constructors.
-  </para>
-
-  <para>
-    Multidimensional array constructor elements can be anything yielding
-    an array of the proper kind, not only a sub-<literal>ARRAY</> construct.
-    For example:
-<programlisting>
-CREATE TABLE arr(f1 int[], f2 int[]);
-
-INSERT INTO arr VALUES (ARRAY[[1,2],[3,4]], ARRAY[[5,6],[7,8]]);
-
-SELECT ARRAY[f1, f2, '{{9,10},{11,12}}'::int[]] FROM arr;
-                     array
-------------------------------------------------
- {{{1,2},{3,4}},{{5,6},{7,8}},{{9,10},{11,12}}}
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-   You can construct an empty array, but since it's impossible to have an
-   array with no type, you must explicitly cast your empty array to the
-   desired type.  For example:
-<programlisting>
-SELECT ARRAY[]::integer[];
- array
--------
- {}
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-   It is also possible to construct an array from the results of a
-   subquery.  In this form, the array constructor is written with the
-   key word <literal>ARRAY</literal> followed by a parenthesized (not
-   bracketed) subquery. For example:
-<programlisting>
-SELECT ARRAY(SELECT oid FROM pg_proc WHERE proname LIKE 'bytea%');
-                          ?column?
--------------------------------------------------------------
- {2011,1954,1948,1952,1951,1244,1950,2005,1949,1953,2006,31}
-(1 row)
-</programlisting>
-   The subquery must return a single column. The resulting
-   one-dimensional array will have an element for each row in the
-   subquery result, with an element type matching that of the
-   subquery's output column.
-  </para>
-
-  <para>
-   The subscripts of an array value built with <literal>ARRAY</literal>
-   always begin with one.  For more information about arrays, see
-   <xref linkend="arrays">.
-  </para>
-
-  </sect2>
-
-  <sect2 id="sql-syntax-row-constructors">
-   <title>Row Constructors</title>
-
-   <indexterm>
-    <primary>composite type</primary>
-    <secondary>constructor</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>row type</primary>
-    <secondary>constructor</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>ROW</primary>
-   </indexterm>
-&common;
-
-   <para>
-    A row constructor is an expression that builds a row value (also
-    called a composite value) using values
-    for its member fields.  A row constructor consists of the key word
-    <literal>ROW</literal>, a left parenthesis, zero or more
-    expressions (separated by commas) for the row field values, and finally
-    a right parenthesis.  For example:
-<programlisting>
-SELECT ROW(1,2.5,'this is a test');
-</programlisting>
-    The key word <literal>ROW</> is optional when there is more than one
-    expression in the list.
-   </para>
-
-   <para>
-    A row constructor can include the syntax
-    <replaceable>rowvalue</replaceable><literal>.*</literal>,
-    which will be expanded to a list of the elements of the row value,
-    just as occurs when the <literal>.*</> syntax is used at the top level
-    of a <command>SELECT</> list.  For example, if table <literal>t</> has
-    columns <literal>f1</> and <literal>f2</>, these are the same:
-<programlisting>
-SELECT ROW(t.*, 42) FROM t;
-SELECT ROW(t.f1, t.f2, 42) FROM t;
-</programlisting>
-   </para>
-
-   <note>
-    <para>
-     Before <productname>PostgreSQL</productname> 8.2, the
-     <literal>.*</literal> syntax was not expanded, so that writing
-     <literal>ROW(t.*, 42)</> created a two-field row whose first field
-     was another row value.  The new behavior is usually more useful.
-     If you need the old behavior of nested row values, write the inner
-     row value without <literal>.*</literal>, for instance
-     <literal>ROW(t, 42)</>.
-    </para>
-   </note>
-
-   <para>
-    By default, the value created by a <literal>ROW</> expression is of
-    an anonymous record type.  If necessary, it can be cast to a named
-    composite type &mdash; either the row type of a table, or a composite type
-    created with <command>CREATE TYPE AS</>.  An explicit cast might be needed
-    to avoid ambiguity.  For example:
-<programlisting>
-CREATE TABLE mytable(f1 int, f2 float, f3 text);
-
-CREATE FUNCTION getf1(mytable) RETURNS int AS 'SELECT $1.f1' LANGUAGE SQL;
-
--- No cast needed since only one getf1() exists
-SELECT getf1(ROW(1,2.5,'this is a test'));
- getf1
--------
-     1
-(1 row)
-
-CREATE TYPE myrowtype AS (f1 int, f2 text, f3 numeric);
-
-CREATE FUNCTION getf1(myrowtype) RETURNS int AS 'SELECT $1.f1' LANGUAGE SQL;
-
--- Now we need a cast to indicate which function to call:
-SELECT getf1(ROW(1,2.5,'this is a test'));
-ERROR:  function getf1(record) is not unique
-
-SELECT getf1(ROW(1,2.5,'this is a test')::mytable);
- getf1
--------
-     1
-(1 row)
-
-SELECT getf1(CAST(ROW(11,'this is a test',2.5) AS myrowtype));
- getf1
--------
-    11
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-   Row constructors can be used to build composite values to be stored
-   in a composite-type table column, or to be passed to a function that
-   accepts a composite parameter.  Also,
-   it is possible to compare two row values or test a row with
-   <literal>IS NULL</> or <literal>IS NOT NULL</>, for example:
-<programlisting>
-SELECT ROW(1,2.5,'this is a test') = ROW(1, 3, 'not the same');
-
-SELECT ROW(table.*) IS NULL FROM table;  -- detect all-null rows
-</programlisting>
-   For more detail see <xref linkend="functions-comparisons">.
-   Row constructors can also be used in connection with subqueries,
-   as discussed in <xref linkend="functions-subquery">.
-  </para>
-
-  </sect2>
-
-  <sect2 id="syntax-express-eval">
-   <title>Expression Evaluation Rules</title>
-
-   <indexterm>
-    <primary>expression</primary>
-    <secondary>order of evaluation</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    The order of evaluation of subexpressions is not defined.  In
-    particular, the inputs of an operator or function are not necessarily
-    evaluated left-to-right or in any other fixed order.
-   </para>
-
-   <para>
-    Furthermore, if the result of an expression can be determined by
-    evaluating only some parts of it, then other subexpressions
-    might not be evaluated at all.  For instance, if one wrote:
-<programlisting>
-SELECT true OR somefunc();
-</programlisting>
-    then <literal>somefunc()</literal> would (probably) not be called
-    at all. The same would be the case if one wrote:
-<programlisting>
-SELECT somefunc() OR true;
-</programlisting>
-    Note that this is not the same as the left-to-right
-    <quote>short-circuiting</quote> of Boolean operators that is found
-    in some programming languages.
-   </para>
-
-   <para>
-    As a consequence, it is unwise to use functions with side effects
-    as part of complex expressions.  It is particularly dangerous to
-    rely on side effects or evaluation order in <literal>WHERE</> and <literal>HAVING</> clauses,
-    since those clauses are extensively reprocessed as part of
-    developing an execution plan.  Boolean
-    expressions (<literal>AND</>/<literal>OR</>/<literal>NOT</> combinations) in those clauses can be reorganized
-    in any manner allowed by the laws of Boolean algebra.
-   </para>
-
-   <para>
-    When it is essential to force evaluation order, a <literal>CASE</>
-    construct (see <xref linkend="functions-conditional">) can be
-    used.  For example, this is an untrustworthy way of trying to
-    avoid division by zero in a <literal>WHERE</> clause:
-<programlisting>
-SELECT ... WHERE x &gt; 0 AND y/x &gt; 1.5;
-</programlisting>
-    But this is safe:
-<programlisting>
-SELECT ... WHERE CASE WHEN x &gt; 0 THEN y/x &gt; 1.5 ELSE false END;
-</programlisting>
-    A <literal>CASE</> construct used in this fashion will defeat optimization
-    attempts, so it should only be done when necessary.  (In this particular
-    example, it would be better to sidestep the problem by writing
-    <literal>y &gt; 1.5*x</> instead.)
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="sql-syntax-calling-funcs">
-  <title>Calling Functions</title>
-
-   <indexterm zone="sql-syntax-calling-funcs">
-    <primary>notation</primary>
-    <secondary>functions</secondary>
-   </indexterm>
-&common;
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> allows functions that have named
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> allows functions that have named
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> allows functions that have named
-<!## end>
-    parameters to be called using either <firstterm>positional</firstterm> or
-    <firstterm>named</firstterm> notation.  Named notation is especially
-    useful for functions that have a large number of parameters, since it
-    makes the associations between parameters and actual arguments more
-    explicit and reliable.
-    In positional notation, a function call is written with
-    its argument values in the same order as they are defined in the function
-    declaration.  In named notation, the arguments are matched to the
-    function parameters by name and can be written in any order.
-   </para>
-
-   <para>
-    In either notation, parameters that have default values given in the
-    function declaration need not be written in the call at all.  But this
-    is particularly useful in named notation, since any combination of
-    parameters can be omitted; while in positional notation parameters can
-    only be omitted from right to left.
-   </para>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> also supports
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> also supports
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> also supports
-<!## end>
-    <firstterm>mixed</firstterm> notation, which combines positional and
-    named notation.  In this case, positional parameters are written first
-    and named parameters appear after them.
-   </para>
-
-   <para>
-    The following examples will illustrate the usage of all three
-    notations, using the following function definition:
-<programlisting>
-CREATE FUNCTION concat_lower_or_upper(a text, b text, uppercase boolean DEFAULT false)
-RETURNS text
-AS
-$$
- SELECT CASE
-        WHEN $3 THEN UPPER($1 || ' ' || $2)
-        ELSE LOWER($1 || ' ' || $2)
-        END;
-$$
-LANGUAGE SQL IMMUTABLE STRICT;
-</programlisting>
-    Function <function>concat_lower_or_upper</function> has two mandatory
-    parameters, <literal>a</literal> and <literal>b</literal>.  Additionally
-    there is one optional parameter <literal>uppercase</literal> which defaults
-    to <literal>false</literal>.  The <literal>a</literal> and
-    <literal>b</literal> inputs will be concatenated, and forced to either
-    upper or lower case depending on the <literal>uppercase</literal>
-    parameter.  The remaining details of this function
-    definition are not important here (see <xref linkend="extend"> for
-    more information).
-   </para>
-
-   <sect2 id="sql-syntax-calling-funcs-positional">
-    <title>Using Positional Notation</title>
-
-    <indexterm>
-     <primary>function</primary>
-     <secondary>positional notation</secondary>
-    </indexterm>
-&common;
-
-    <para>
-     Positional notation is the traditional mechanism for passing arguments
-<!## PG>
-     to functions in <productname>PostgreSQL</productname>.  An example is:
-<!## end>
-<!## XC>
-     to functions in <productname>Postgres-XC</productname>.  An example is:
-<!## end>
-<!## XL>
-     to functions in <productname>Postgres-XL</productname>.  An example is:
-<!## end>
-<screen>
-SELECT concat_lower_or_upper('Hello', 'World', true);
- concat_lower_or_upper 
------------------------
- HELLO WORLD
-(1 row)
-</screen>
-     All arguments are specified in order.  The result is upper case since
-     <literal>uppercase</literal> is specified as <literal>true</literal>.
-     Another example is:
-<screen>
-SELECT concat_lower_or_upper('Hello', 'World');
- concat_lower_or_upper 
------------------------
- hello world
-(1 row)
-</screen>
-     Here, the <literal>uppercase</literal> parameter is omitted, so it
-     receives its default value of <literal>false</literal>, resulting in
-     lower case output.  In positional notation, arguments can be omitted
-     from right to left so long as they have defaults.
-    </para>
-   </sect2>
-
-   <sect2 id="sql-syntax-calling-funcs-named">
-    <title>Using Named Notation</title>
-
-    <indexterm>
-     <primary>function</primary>
-     <secondary>named notation</secondary>
-    </indexterm>
-&common;
-
-    <para>
-     In named notation, each argument's name is specified using
-     <literal>:=</literal> to separate it from the argument expression.
-     For example:
-<screen>
-SELECT concat_lower_or_upper(a := 'Hello', b := 'World');
- concat_lower_or_upper 
------------------------
- hello world
-(1 row)
-</screen>
-     Again, the argument <literal>uppercase</literal> was omitted
-     so it is set to <literal>false</literal> implicitly.  One advantage of
-     using named notation is that the arguments may be specified in any
-     order, for example:
-<screen>
-SELECT concat_lower_or_upper(a := 'Hello', b := 'World', uppercase := true);
- concat_lower_or_upper 
------------------------
- HELLO WORLD
-(1 row)
-
-SELECT concat_lower_or_upper(a := 'Hello', uppercase := true, b := 'World');
- concat_lower_or_upper 
------------------------
- HELLO WORLD
-(1 row)
-</screen>
-    </para>
-   </sect2>
-
-  <sect2 id="sql-syntax-calling-funcs-mixed">
-   <title>Using Mixed Notation</title>
-
-   <indexterm>
-    <primary>function</primary>
-    <secondary>mixed notation</secondary>
-   </indexterm>
-&common;
-
-   <para>
-    The mixed notation combines positional and named notation. However, as
-    already mentioned, named arguments cannot precede positional arguments.
-    For example:
-<screen>
-SELECT concat_lower_or_upper('Hello', 'World', uppercase := true);
- concat_lower_or_upper 
------------------------
- HELLO WORLD
-(1 row)
-</screen>
-    In the above query, the arguments <literal>a</literal> and
-    <literal>b</literal> are specified positionally, while
-    <literal>uppercase</> is specified by name.  In this example,
-    that adds little except documentation.  With a more complex function
-    having numerous parameters that have default values, named or mixed
-    notation can save a great deal of writing and reduce chances for error.
-   </para>
-  </sect2>
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/tablefunc.sgmlin b/doc-xc/src/sgml/tablefunc.sgmlin
deleted file mode 100644
index 9a594244fb..0000000000
--- a/doc-xc/src/sgml/tablefunc.sgmlin
+++ /dev/null
@@ -1,822 +0,0 @@
-<!-- doc/src/sgml/tablefunc.sgml -->
-
-<sect1 id="tablefunc" xreflabel="tablefunc">
- <title>tablefunc</title>
-
- <indexterm zone="tablefunc">
-  <primary>tablefunc</primary>
- </indexterm>
-
-&pgonly;
-
- <para>
-  The <filename>tablefunc</> module includes various functions that return
-  tables (that is, multiple rows).  These functions are useful both in their
-  own right and as examples of how to write C functions that return
-  multiple rows.
- </para>
-
- <sect2>
-  <title>Functions Provided</title>
-
-&pgnotice;
-  <para>
-   <xref linkend="tablefunc-functions"> shows the functions provided
-   by the <filename>tablefunc</filename> module.
-  </para>
-
-  <table id="tablefunc-functions">
-   <title><filename>tablefunc</> Functions</title>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Returns</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><function>normal_rand(int numvals, float8 mean, float8 stddev)</function></entry>
-      <entry><type>setof float8</></entry>
-      <entry>
-       Produces a set of normally distributed random values
-      </entry>
-     </row>
-     <row>
-      <entry><function>crosstab(text sql)</function></entry>
-      <entry><type>setof record</></entry>
-      <entry>
-       Produces a <quote>pivot table</> containing
-       row names plus <replaceable>N</> value columns, where
-       <replaceable>N</> is determined by the row type specified in the calling
-       query
-      </entry>
-     </row>
-     <row>
-      <entry><function>crosstab<replaceable>N</>(text sql)</function></entry>
-      <entry><type>setof table_crosstab_<replaceable>N</></></entry>
-      <entry>
-       Produces a <quote>pivot table</> containing
-       row names plus <replaceable>N</> value columns.
-       <function>crosstab2</>, <function>crosstab3</>, and
-       <function>crosstab4</> are predefined, but you can create additional
-       <function>crosstab<replaceable>N</></> functions as described below
-      </entry>
-     </row>
-     <row>
-      <entry><function>crosstab(text source_sql, text category_sql)</function></entry>
-      <entry><type>setof record</></entry>
-      <entry>
-       Produces a <quote>pivot table</>
-       with the value columns specified by a second query
-      </entry>
-     </row>
-     <row>
-      <entry><function>crosstab(text sql, int N)</function></entry>
-      <entry><type>setof record</></entry>
-      <entry>
-       <para>Obsolete version of <function>crosstab(text)</>.
-        The parameter <replaceable>N</> is now ignored, since the number of
-        value columns is always determined by the calling query
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry>
-       <function>
-        connectby(text relname, text keyid_fld, text parent_keyid_fld
-        [, text orderby_fld ], text start_with, int max_depth
-        [, text branch_delim ])
-       </function>
-      </entry>
-      <entry><type>setof record</></entry>
-      <entry>
-       Produces a representation of a hierarchical tree structure
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <sect3>
-   <title><function>normal_rand</function></title>
-
-<synopsis>
-normal_rand(int numvals, float8 mean, float8 stddev) returns setof float8
-</synopsis>
-
-&pgnotice;
-    <para>
-     <function>normal_rand</> produces a set of normally distributed random
-     values (Gaussian distribution).
-    </para>
-
-    <para>
-     <parameter>numvals</parameter> is the number of values to be returned
-     from the function. <parameter>mean</parameter> is the mean of the normal
-     distribution of values and <parameter>stddev</parameter> is the standard
-     deviation of the normal distribution of values.
-    </para>
-
-    <para>
-     For example, this call requests 1000 values with a mean of 5 and a
-     standard deviation of 3:
-    </para>
-
-<screen>
-test=# SELECT * FROM normal_rand(1000, 5, 3);
-     normal_rand
-----------------------
-     1.56556322244898
-     9.10040991424657
-     5.36957140345079
-   -0.369151492880995
-    0.283600703686639
-       .
-       .
-       .
-     4.82992125404908
-     9.71308014517282
-     2.49639286969028
-(1000 rows)
-</screen>
-  </sect3>
-
-  <sect3>
-   <title><function>crosstab(text)</function></title>
-
-<synopsis>
-crosstab(text sql)
-crosstab(text sql, int N)
-</synopsis>
-
-&pgnotice;
-   <para>
-    The <function>crosstab</> function is used to produce <quote>pivot</>
-    displays, wherein data is listed across the page rather than down.
-    For example, we might have data like
-<programlisting>
-row1    val11
-row1    val12
-row1    val13
-...
-row2    val21
-row2    val22
-row2    val23
-...
-</programlisting>
-    which we wish to display like
-<programlisting>
-row1    val11   val12   val13   ...
-row2    val21   val22   val23   ...
-...
-</programlisting>
-    The <function>crosstab</> function takes a text parameter that is a SQL
-    query producing raw data formatted in the first way, and produces a table
-    formatted in the second way.
-   </para>
-
-   <para>
-    The <parameter>sql</parameter> parameter is a SQL statement that produces
-    the source set of data. This statement must return one
-    <structfield>row_name</structfield> column, one
-    <structfield>category</structfield> column, and one
-    <structfield>value</structfield> column.  <parameter>N</parameter> is an
-    obsolete parameter, ignored if supplied (formerly this had to match the
-    number of output value columns, but now that is determined by the
-    calling query).
-   </para>
-
-   <para>
-    For example, the provided query might produce a set something like:
-<programlisting>
- row_name    cat    value
-----------+-------+-------
-  row1      cat1    val1
-  row1      cat2    val2
-  row1      cat3    val3
-  row1      cat4    val4
-  row2      cat1    val5
-  row2      cat2    val6
-  row2      cat3    val7
-  row2      cat4    val8
-</programlisting>
-   </para>
-
-   <para>
-    The <function>crosstab</> function is declared to return <type>setof
-    record</type>, so the actual names and types of the output columns must be
-    defined in the <literal>FROM</> clause of the calling <command>SELECT</>
-    statement, for example:
-<programlisting>
-SELECT * FROM crosstab('...') AS ct(row_name text, category_1 text, category_2 text);
-</programlisting>
-    This example produces a set something like:
-<programlisting>
-           &lt;== value  columns  ==&gt;
- row_name   category_1   category_2
-----------+------------+------------
-  row1        val1         val2
-  row2        val5         val6
-</programlisting>
-   </para>
-
-   <para>
-    The <literal>FROM</> clause must define the output as one
-    <structfield>row_name</> column (of the same data type as the first result
-    column of the SQL query) followed by N <structfield>value</> columns
-    (all of the same data type as the third result column of the SQL query).
-    You can set up as many output value columns as you wish.  The names of the
-    output columns are up to you.
-   </para>
-
-   <para>
-    The <function>crosstab</> function produces one output row for each
-    consecutive group of input rows with the same
-    <structfield>row_name</structfield> value.  It fills the output
-    <structfield>value</> columns, left to right, with the
-    <structfield>value</structfield> fields from these rows.  If there
-    are fewer rows in a group than there are output <structfield>value</>
-    columns, the extra output columns are filled with nulls; if there are
-    more rows, the extra input rows are skipped.
-   </para>
-
-   <para>
-    In practice the SQL query should always specify <literal>ORDER BY 1,2</>
-    to ensure that the input rows are properly ordered, that is, values with
-    the same <structfield>row_name</structfield> are brought together and
-    correctly ordered within the row.  Notice that <function>crosstab</>
-    itself does not pay any attention to the second column of the query
-    result; it's just there to be ordered by, to control the order in which
-    the third-column values appear across the page.
-   </para>
-
-   <para>
-    Here is a complete example:
-<programlisting>
-CREATE TABLE ct(id SERIAL, rowid TEXT, attribute TEXT, value TEXT);
-INSERT INTO ct(rowid, attribute, value) VALUES('test1','att1','val1');
-INSERT INTO ct(rowid, attribute, value) VALUES('test1','att2','val2');
-INSERT INTO ct(rowid, attribute, value) VALUES('test1','att3','val3');
-INSERT INTO ct(rowid, attribute, value) VALUES('test1','att4','val4');
-INSERT INTO ct(rowid, attribute, value) VALUES('test2','att1','val5');
-INSERT INTO ct(rowid, attribute, value) VALUES('test2','att2','val6');
-INSERT INTO ct(rowid, attribute, value) VALUES('test2','att3','val7');
-INSERT INTO ct(rowid, attribute, value) VALUES('test2','att4','val8');
-
-SELECT *
-FROM crosstab(
-  'select rowid, attribute, value
-   from ct
-   where attribute = ''att2'' or attribute = ''att3''
-   order by 1,2')
-AS ct(row_name text, category_1 text, category_2 text, category_3 text);
-
- row_name | category_1 | category_2 | category_3
-----------+------------+------------+------------
- test1    | val2       | val3       |
- test2    | val6       | val7       |
-(2 rows)
-</programlisting>
-   </para>
-
-   <para>
-    You can avoid always having to write out a <literal>FROM</> clause to
-    define the output columns, by setting up a custom crosstab function that
-    has the desired output row type wired into its definition.  This is
-    described in the next section.  Another possibility is to embed the
-    required <literal>FROM</> clause in a view definition.
-   </para>
-
-  </sect3>
-
-  <sect3>
-   <title><function>crosstab<replaceable>N</>(text)</function></title>
-
-<synopsis>
-crosstab<replaceable>N</>(text sql)
-</synopsis>
-
-&pgnotice;
-    <para>
-     The <function>crosstab<replaceable>N</></> functions are examples of how
-     to set up custom wrappers for the general <function>crosstab</> function,
-     so that you need not write out column names and types in the calling
-     <command>SELECT</> query.  The <filename>tablefunc</> module includes
-     <function>crosstab2</>, <function>crosstab3</>, and
-     <function>crosstab4</>, whose output row types are defined as
-    </para>
-
-<programlisting>
-CREATE TYPE tablefunc_crosstab_N AS (
-    row_name TEXT,
-    category_1 TEXT,
-    category_2 TEXT,
-        .
-        .
-        .
-    category_N TEXT
-);
-</programlisting>
-
-    <para>
-     Thus, these functions can be used directly when the input query produces
-     <structfield>row_name</> and <structfield>value</> columns of type
-     <type>text</>, and you want 2, 3, or 4 output values columns.
-     In all other ways they behave exactly as described above for the
-     general <function>crosstab</> function.
-    </para>
-
-    <para>
-     For instance, the example given in the previous section would also
-     work as
-<programlisting>
-SELECT *
-FROM crosstab3(
-  'select rowid, attribute, value
-   from ct
-   where attribute = ''att2'' or attribute = ''att3''
-   order by 1,2');
-</programlisting>
-    </para>
-
-    <para>
-     These functions are provided mostly for illustration purposes. You
-     can create your own return types and functions based on the
-     underlying <function>crosstab()</> function.  There are two ways
-     to do it:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Create a composite type describing the desired output columns,
-       similar to the examples in
-       <filename>contrib/tablefunc/tablefunc--1.0.sql</>.
-       Then define a
-       unique function name accepting one <type>text</> parameter and returning
-       <type>setof your_type_name</>, but linking to the same underlying
-       <function>crosstab</> C function.  For example, if your source data
-       produces row names that are <type>text</>, and values that are
-       <type>float8</>, and you want 5 value columns:
-<programlisting>
-CREATE TYPE my_crosstab_float8_5_cols AS (
-    my_row_name text,
-    my_category_1 float8,
-    my_category_2 float8,
-    my_category_3 float8,
-    my_category_4 float8,
-    my_category_5 float8
-);
-
-CREATE OR REPLACE FUNCTION crosstab_float8_5_cols(text)
-    RETURNS setof my_crosstab_float8_5_cols
-    AS '$libdir/tablefunc','crosstab' LANGUAGE C STABLE STRICT;
-</programlisting>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Use <literal>OUT</> parameters to define the return type implicitly.
-       The same example could also be done this way:
-<programlisting>
-CREATE OR REPLACE FUNCTION crosstab_float8_5_cols(
-    IN text,
-    OUT my_row_name text,
-    OUT my_category_1 float8,
-    OUT my_category_2 float8,
-    OUT my_category_3 float8,
-    OUT my_category_4 float8,
-    OUT my_category_5 float8)
-  RETURNS setof record
-  AS '$libdir/tablefunc','crosstab' LANGUAGE C STABLE STRICT;
-</programlisting>
-      </para>
-     </listitem>
-    </itemizedlist>
-    </para>
-
-  </sect3>
-
-  <sect3>
-   <title><function>crosstab(text, text)</function></title>
-
-<synopsis>
-crosstab(text source_sql, text category_sql)
-</synopsis>
-
-&pgnotice;
-   <para>
-    The main limitation of the single-parameter form of <function>crosstab</>
-    is that it treats all values in a group alike, inserting each value into
-    the first available column.  If you want the value
-    columns to correspond to specific categories of data, and some groups
-    might not have data for some of the categories, that doesn't work well.
-    The two-parameter form of <function>crosstab</> handles this case by
-    providing an explicit list of the categories corresponding to the
-    output columns.
-   </para>
-
-   <para>
-    <parameter>source_sql</parameter> is a SQL statement that produces the
-    source set of data.  This statement must return one
-    <structfield>row_name</structfield> column, one
-    <structfield>category</structfield> column, and one
-    <structfield>value</structfield> column. It may also have one or more
-    <quote>extra</quote> columns.
-    The <structfield>row_name</structfield> column must be first. The
-    <structfield>category</structfield> and <structfield>value</structfield>
-    columns must be the last two columns, in that order.  Any columns between
-    <structfield>row_name</structfield> and
-    <structfield>category</structfield> are treated as <quote>extra</>.
-    The <quote>extra</quote> columns are expected to be the same for all rows
-    with the same <structfield>row_name</structfield> value.
-   </para>
-
-   <para>
-    For example, <parameter>source_sql</parameter> might produce a set
-    something like:
-<programlisting>
-SELECT row_name, extra_col, cat, value FROM foo ORDER BY 1;
-
- row_name    extra_col   cat    value
-----------+------------+-----+---------
-  row1         extra1    cat1    val1
-  row1         extra1    cat2    val2
-  row1         extra1    cat4    val4
-  row2         extra2    cat1    val5
-  row2         extra2    cat2    val6
-  row2         extra2    cat3    val7
-  row2         extra2    cat4    val8
-</programlisting>
-   </para>
-
-   <para>
-    <parameter>category_sql</parameter> is a SQL statement that produces
-    the set of categories. This statement must return only one column.
-    It must produce at least one row, or an error will be generated.
-    Also, it must not produce duplicate values, or an error will be
-    generated.  <parameter>category_sql</parameter> might be something like:
-
-<programlisting>
-SELECT DISTINCT cat FROM foo ORDER BY 1;
-    cat
-  -------
-    cat1
-    cat2
-    cat3
-    cat4
-</programlisting>
-   </para>
-
-   <para>
-    The <function>crosstab</> function is declared to return <type>setof
-    record</type>, so the actual names and types of the output columns must be
-    defined in the <literal>FROM</> clause of the calling <command>SELECT</>
-    statement, for example:
-
-<programlisting>
-SELECT * FROM crosstab('...', '...')
-    AS ct(row_name text, extra text, cat1 text, cat2 text, cat3 text, cat4 text);
-</programlisting>
-   </para>
-
-   <para>
-    This will produce a result something like:
-<programlisting>
-                  &lt;==  value  columns   ==&gt;
-row_name   extra   cat1   cat2   cat3   cat4
----------+-------+------+------+------+------
-  row1     extra1  val1   val2          val4
-  row2     extra2  val5   val6   val7   val8
-</programlisting>
-   </para>
-
-   <para>
-    The <literal>FROM</> clause must define the proper number of output
-    columns of the proper data types.  If there are <replaceable>N</>
-    columns in the <parameter>source_sql</> query's result, the first
-    <replaceable>N</>-2 of them must match up with the first
-    <replaceable>N</>-2 output columns.  The remaining output columns
-    must have the type of the last column of the <parameter>source_sql</>
-    query's result, and there must be exactly as many of them as there
-    are rows in the <parameter>category_sql</parameter> query's result.
-   </para>
-
-   <para>
-    The <function>crosstab</> function produces one output row for each
-    consecutive group of input rows with the same
-    <structfield>row_name</structfield> value.  The output
-    <structfield>row_name</structfield> column, plus any <quote>extra</>
-    columns, are copied from the first row of the group.  The output
-    <structfield>value</> columns are filled with the
-    <structfield>value</structfield> fields from rows having matching
-    <structfield>category</> values.  If a row's <structfield>category</>
-    does not match any output of the <parameter>category_sql</parameter>
-    query, its <structfield>value</structfield> is ignored.  Output
-    columns whose matching category is not present in any input row
-    of the group are filled with nulls.
-   </para>
-
-   <para>
-    In practice the <parameter>source_sql</parameter> query should always
-    specify <literal>ORDER BY 1</> to ensure that values with the same
-    <structfield>row_name</structfield> are brought together.  However,
-    ordering of the categories within a group is not important.
-    Also, it is essential to be sure that the order of the
-    <parameter>category_sql</parameter> query's output matches the specified
-    output column order.
-   </para>
-
-   <para>
-    Here are two complete examples:
-<programlisting>
-create table sales(year int, month int, qty int);
-insert into sales values(2007, 1, 1000);
-insert into sales values(2007, 2, 1500);
-insert into sales values(2007, 7, 500);
-insert into sales values(2007, 11, 1500);
-insert into sales values(2007, 12, 2000);
-insert into sales values(2008, 1, 1000);
-
-select * from crosstab(
-  'select year, month, qty from sales order by 1',
-  'select m from generate_series(1,12) m'
-) as (
-  year int,
-  "Jan" int,
-  "Feb" int,
-  "Mar" int,
-  "Apr" int,
-  "May" int,
-  "Jun" int,
-  "Jul" int,
-  "Aug" int,
-  "Sep" int,
-  "Oct" int,
-  "Nov" int,
-  "Dec" int
-);
- year | Jan  | Feb  | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov  | Dec
-------+------+------+-----+-----+-----+-----+-----+-----+-----+-----+------+------
- 2007 | 1000 | 1500 |     |     |     |     | 500 |     |     |     | 1500 | 2000
- 2008 | 1000 |      |     |     |     |     |     |     |     |     |      |
-(2 rows)
-</programlisting>
-
-<programlisting>
-CREATE TABLE cth(rowid text, rowdt timestamp, attribute text, val text);
-INSERT INTO cth VALUES('test1','01 March 2003','temperature','42');
-INSERT INTO cth VALUES('test1','01 March 2003','test_result','PASS');
-INSERT INTO cth VALUES('test1','01 March 2003','volts','2.6987');
-INSERT INTO cth VALUES('test2','02 March 2003','temperature','53');
-INSERT INTO cth VALUES('test2','02 March 2003','test_result','FAIL');
-INSERT INTO cth VALUES('test2','02 March 2003','test_startdate','01 March 2003');
-INSERT INTO cth VALUES('test2','02 March 2003','volts','3.1234');
-
-SELECT * FROM crosstab
-(
-  'SELECT rowid, rowdt, attribute, val FROM cth ORDER BY 1',
-  'SELECT DISTINCT attribute FROM cth ORDER BY 1'
-)
-AS
-(
-       rowid text,
-       rowdt timestamp,
-       temperature int4,
-       test_result text,
-       test_startdate timestamp,
-       volts float8
-);
- rowid |          rowdt           | temperature | test_result |      test_startdate      | volts
--------+--------------------------+-------------+-------------+--------------------------+--------
- test1 | Sat Mar 01 00:00:00 2003 |          42 | PASS        |                          | 2.6987
- test2 | Sun Mar 02 00:00:00 2003 |          53 | FAIL        | Sat Mar 01 00:00:00 2003 | 3.1234
-(2 rows)
-</programlisting>
-   </para>
-
-   <para>
-    You can create predefined functions to avoid having to write out
-    the result column names and types in each query.  See the examples
-    in the previous section.  The underlying C function for this form
-    of <function>crosstab</> is named <literal>crosstab_hash</>.
-   </para>
-
-  </sect3>
-
-  <sect3>
-   <title><function>connectby</function></title>
-
-<synopsis>
-connectby(text relname, text keyid_fld, text parent_keyid_fld
-          [, text orderby_fld ], text start_with, int max_depth
-          [, text branch_delim ])
-</synopsis>
-
-&pgnotice;
-   <para>
-    The <function>connectby</> function produces a display of hierarchical
-    data that is stored in a table.  The table must have a key field that
-    uniquely identifies rows, and a parent-key field that references the
-    parent (if any) of each row.  <function>connectby</> can display the
-    sub-tree descending from any row.
-   </para>
-
-   <para>
-    <xref linkend="tablefunc-connectby-parameters"> explains the
-    parameters.
-   </para>
-
-   <table id="tablefunc-connectby-parameters">
-    <title><function>connectby</function> Parameters</title>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Parameter</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry><parameter>relname</parameter></entry>
-       <entry>Name of the source relation</entry>
-      </row>
-      <row>
-       <entry><parameter>keyid_fld</parameter></entry>
-       <entry>Name of the key field</entry>
-      </row>
-      <row>
-       <entry><parameter>parent_keyid_fld</parameter></entry>
-       <entry>Name of the parent-key field</entry>
-      </row>
-      <row>
-       <entry><parameter>orderby_fld</parameter></entry>
-       <entry>Name of the field to order siblings by (optional)</entry>
-      </row>
-      <row>
-       <entry><parameter>start_with</parameter></entry>
-       <entry>Key value of the row to start at</entry>
-      </row>
-      <row>
-       <entry><parameter>max_depth</parameter></entry>
-       <entry>Maximum depth to descend to, or zero for unlimited depth</entry>
-      </row>
-      <row>
-       <entry><parameter>branch_delim</parameter></entry>
-       <entry>String to separate keys with in branch output (optional)</entry>
-      </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-    <para>
-     The key and parent-key fields can be any data type, but they must be
-     the same type.  Note that the <parameter>start_with</> value must be
-     entered as a text string, regardless of the type of the key field.
-    </para>
-
-    <para>
-     The <function>connectby</> function is declared to return <type>setof
-     record</type>, so the actual names and types of the output columns must be
-     defined in the <literal>FROM</> clause of the calling <command>SELECT</>
-     statement, for example:
-    </para>
-
-<programlisting>
-SELECT * FROM connectby('connectby_tree', 'keyid', 'parent_keyid', 'pos', 'row2', 0, '~')
-    AS t(keyid text, parent_keyid text, level int, branch text, pos int);
-</programlisting>
-
-    <para>
-     The first two output columns are used for the current row's key and
-     its parent row's key; they must match the type of the table's key field.
-     The third output column is the depth in the tree and must be of type
-     <type>integer</>.  If a <parameter>branch_delim</parameter> parameter was
-     given, the next output column is the branch display and must be of type
-     <type>text</>.  Finally, if an <parameter>orderby_fld</parameter>
-     parameter was given, the last output column is a serial number, and must
-     be of type <type>integer</>.
-    </para>
-
-    <para>
-     The <quote>branch</> output column shows the path of keys taken to
-     reach the current row.  The keys are separated by the specified
-     <parameter>branch_delim</parameter> string.  If no branch display is
-     wanted, omit both the <parameter>branch_delim</parameter> parameter
-     and the branch column in the output column list.
-    </para>
-
-    <para>
-     If the ordering of siblings of the same parent is important,
-     include the <parameter>orderby_fld</parameter> parameter to
-     specify which field to order siblings by.  This field can be of any
-     sortable data type.  The output column list must include a final
-     integer serial-number column, if and only if
-     <parameter>orderby_fld</parameter> is specified.
-    </para>
-
-    <para>
-     The parameters representing table and field names are copied as-is
-     into the SQL queries that <function>connectby</> generates internally.
-     Therefore, include double quotes if the names are mixed-case or contain
-     special characters.  You may also need to schema-qualify the table name.
-    </para>
-
-    <para>
-     In large tables, performance will be poor unless there is an index on
-     the parent-key field.
-    </para>
-
-    <para>
-     It is important that the <parameter>branch_delim</parameter> string
-     not appear in any key values, else <function>connectby</> may incorrectly
-     report an infinite-recursion error.  Note that if
-     <parameter>branch_delim</parameter> is not provided, a default value
-     of <literal>~</> is used for recursion detection purposes.
-     <!-- That pretty well sucks.  FIXME -->
-    </para>
-
-    <para>
-     Here is an example:
-<programlisting>
-CREATE TABLE connectby_tree(keyid text, parent_keyid text, pos int);
-
-INSERT INTO connectby_tree VALUES('row1',NULL, 0);
-INSERT INTO connectby_tree VALUES('row2','row1', 0);
-INSERT INTO connectby_tree VALUES('row3','row1', 0);
-INSERT INTO connectby_tree VALUES('row4','row2', 1);
-INSERT INTO connectby_tree VALUES('row5','row2', 0);
-INSERT INTO connectby_tree VALUES('row6','row4', 0);
-INSERT INTO connectby_tree VALUES('row7','row3', 0);
-INSERT INTO connectby_tree VALUES('row8','row6', 0);
-INSERT INTO connectby_tree VALUES('row9','row5', 0);
-
--- with branch, without orderby_fld (order of results is not guaranteed)
-SELECT * FROM connectby('connectby_tree', 'keyid', 'parent_keyid', 'row2', 0, '~')
- AS t(keyid text, parent_keyid text, level int, branch text);
- keyid | parent_keyid | level |       branch
--------+--------------+-------+---------------------
- row2  |              |     0 | row2
- row4  | row2         |     1 | row2~row4
- row6  | row4         |     2 | row2~row4~row6
- row8  | row6         |     3 | row2~row4~row6~row8
- row5  | row2         |     1 | row2~row5
- row9  | row5         |     2 | row2~row5~row9
-(6 rows)
-
--- without branch, without orderby_fld (order of results is not guaranteed)
-SELECT * FROM connectby('connectby_tree', 'keyid', 'parent_keyid', 'row2', 0)
- AS t(keyid text, parent_keyid text, level int);
- keyid | parent_keyid | level
--------+--------------+-------
- row2  |              |     0
- row4  | row2         |     1
- row6  | row4         |     2
- row8  | row6         |     3
- row5  | row2         |     1
- row9  | row5         |     2
-(6 rows)
-
--- with branch, with orderby_fld (notice that row5 comes before row4)
-SELECT * FROM connectby('connectby_tree', 'keyid', 'parent_keyid', 'pos', 'row2', 0, '~')
- AS t(keyid text, parent_keyid text, level int, branch text, pos int);
- keyid | parent_keyid | level |       branch        | pos
--------+--------------+-------+---------------------+-----
- row2  |              |     0 | row2                |   1
- row5  | row2         |     1 | row2~row5           |   2
- row9  | row5         |     2 | row2~row5~row9      |   3
- row4  | row2         |     1 | row2~row4           |   4
- row6  | row4         |     2 | row2~row4~row6      |   5
- row8  | row6         |     3 | row2~row4~row6~row8 |   6
-(6 rows)
-
--- without branch, with orderby_fld (notice that row5 comes before row4)
-SELECT * FROM connectby('connectby_tree', 'keyid', 'parent_keyid', 'pos', 'row2', 0)
- AS t(keyid text, parent_keyid text, level int, pos int);
- keyid | parent_keyid | level | pos
--------+--------------+-------+-----
- row2  |              |     0 |   1
- row5  | row2         |     1 |   2
- row9  | row5         |     2 |   3
- row4  | row2         |     1 |   4
- row6  | row4         |     2 |   5
- row8  | row6         |     3 |   6
-(6 rows)
-</programlisting>
-    </para>
-   </sect3>
-
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Joe Conway
-  </para>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/test-parser.sgmlin b/doc-xc/src/sgml/test-parser.sgmlin
deleted file mode 100644
index 281a6bae02..0000000000
--- a/doc-xc/src/sgml/test-parser.sgmlin
+++ /dev/null
@@ -1,93 +0,0 @@
-<!-- doc/src/sgml/test-parser.sgml -->
-
-<sect1 id="test-parser" xreflabel="test_parser">
- <title>test_parser</title>
-
- <indexterm zone="test-parser">
-  <primary>test_parser</primary>
- </indexterm>
-
-&common;
-
- <para>
-  <filename>test_parser</> is an example of a custom parser for full-text
-  search.  It doesn't do anything especially useful, but can serve as
-  a starting point for developing your own parser.
- </para>
-
- <para>
-  <filename>test_parser</> recognizes words separated by white space,
-  and returns just two token types:
-
-<programlisting>
-mydb=# SELECT * FROM ts_token_type('testparser');
- tokid | alias |  description
--------+-------+---------------
-     3 | word  | Word
-    12 | blank | Space symbols
-(2 rows)
-</programlisting>
-
-  These token numbers have been chosen to be compatible with the default
-  parser's numbering.  This allows us to use its <function>headline()</>
-  function, thus keeping the example simple.
- </para>
-
- <sect2>
-  <title>Usage</title>
-
-&common;
-  <para>
-   Installing the <literal>test_parser</> extension creates a text search
-   parser <literal>testparser</>.  It has no user-configurable parameters.
-  </para>
-
-  <para>
-   You can test the parser with, for example,
-
-<programlisting>
-mydb=# SELECT * FROM ts_parse('testparser', 'That''s my first own parser');
- tokid | token
--------+--------
-     3 | That's
-    12 |
-     3 | my
-    12 |
-     3 | first
-    12 |
-     3 | own
-    12 |
-     3 | parser
-</programlisting>
-  </para>
-
-  <para>
-   Real-world use requires setting up a text search configuration
-   that uses the parser.  For example,
-
-<programlisting>
-mydb=# CREATE TEXT SEARCH CONFIGURATION testcfg ( PARSER = testparser );
-CREATE TEXT SEARCH CONFIGURATION
-
-mydb=# ALTER TEXT SEARCH CONFIGURATION testcfg
-mydb-#   ADD MAPPING FOR word WITH english_stem;
-ALTER TEXT SEARCH CONFIGURATION
-
-mydb=#  SELECT to_tsvector('testcfg', 'That''s my first own parser');
-          to_tsvector
--------------------------------
- 'that':1 'first':3 'parser':5
-(1 row)
-
-mydb=# SELECT ts_headline('testcfg', 'Supernovae stars are the brightest phenomena in galaxies',
-mydb(#                    to_tsquery('testcfg', 'star'));
-                           ts_headline
------------------------------------------------------------------
- Supernovae &lt;b&gt;stars&lt;/b&gt; are the brightest phenomena in galaxies
-(1 row)
-</programlisting>
-  </para>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/textsearch.sgmlin b/doc-xc/src/sgml/textsearch.sgmlin
deleted file mode 100644
index c6e1ea411d..0000000000
--- a/doc-xc/src/sgml/textsearch.sgmlin
+++ /dev/null
@@ -1,3962 +0,0 @@
-<!-- doc/src/sgml/textsearch.sgml -->
-
-<chapter id="textsearch">
- <title>Full Text Search</title>
-
-  <indexterm zone="textsearch">
-   <primary>full text search</primary>
-  </indexterm>
-
-  <indexterm zone="textsearch">
-   <primary>text search</primary>
-  </indexterm>
-
-&common;
-
- <sect1 id="textsearch-intro">
-  <title>Introduction</title>
-
-  <para>
-   Full Text Searching (or just <firstterm>text search</firstterm>) provides
-   the capability to identify natural-language <firstterm>documents</> that
-   satisfy a <firstterm>query</firstterm>, and optionally to sort them by
-   relevance to the query.  The most common type of search
-   is to find all documents containing given <firstterm>query terms</firstterm>
-   and return them in order of their <firstterm>similarity</firstterm> to the
-   query.  Notions of <varname>query</varname> and
-   <varname>similarity</varname> are very flexible and depend on the specific
-   application. The simplest search considers <varname>query</varname> as a
-   set of words and <varname>similarity</varname> as the frequency of query
-   words in the document.
-  </para>
-
-  <para>
-   Textual search operators have existed in databases for years.
-<!## PG>
-   <productname>PostgreSQL</productname> has
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> has
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> has
-<!## end>
-   <literal>~</literal>, <literal>~*</literal>, <literal>LIKE</literal>, and
-   <literal>ILIKE</literal> operators for textual data types, but they lack
-   many essential properties required by modern information systems:
-  </para>
-
-  <itemizedlist  spacing="compact" mark="bullet">
-   <listitem>
-    <para>
-     There is no linguistic support, even for English.  Regular expressions
-     are not sufficient because they cannot easily handle derived words, e.g.,
-     <literal>satisfies</literal> and <literal>satisfy</literal>. You might
-     miss documents that contain <literal>satisfies</literal>, although you
-     probably would like to find them when searching for
-     <literal>satisfy</literal>. It is possible to use <literal>OR</literal>
-     to search for multiple derived forms, but this is tedious and error-prone
-     (some words can have several thousand derivatives).
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     They provide no ordering (ranking) of search results, which makes them
-     ineffective when thousands of matching documents are found.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     They tend to be slow because there is no index support, so they must
-     process all documents for every search.
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   Full text indexing allows documents to be <emphasis>preprocessed</emphasis>
-   and an index saved for later rapid searching. Preprocessing includes:
-  </para>
-
-  <itemizedlist  mark="none">
-   <listitem>
-    <para>
-     <emphasis>Parsing documents into <firstterm>tokens</></emphasis>. It is
-     useful to identify various classes of tokens, e.g., numbers, words,
-     complex words, email addresses, so that they can be processed
-     differently.  In principle token classes depend on the specific
-     application, but for most purposes it is adequate to use a predefined
-     set of classes.
-<!## PG>
-     <productname>PostgreSQL</productname> uses a <firstterm>parser</> to
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> uses a <firstterm>parser</> to
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> uses a <firstterm>parser</> to
-<!## end>
-     perform this step.  A standard parser is provided, and custom parsers
-     can be created for specific needs.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <emphasis>Converting tokens into <firstterm>lexemes</></emphasis>.
-     A lexeme is a string, just like a token, but it has been
-     <firstterm>normalized</> so that different forms of the same word
-     are made alike.  For example, normalization almost always includes
-     folding upper-case letters to lower-case, and often involves removal
-     of suffixes (such as <literal>s</> or <literal>es</> in English).
-     This allows searches to find variant forms of the
-     same word, without tediously entering all the possible variants.
-     Also, this step typically eliminates <firstterm>stop words</>, which
-     are words that are so common that they are useless for searching.
-     (In short, then, tokens are raw fragments of the document text, while
-     lexemes are words that are believed useful for indexing and searching.)
-<!## PG>
-     <productname>PostgreSQL</productname> uses <firstterm>dictionaries</> to
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> uses <firstterm>dictionaries</> to
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> uses <firstterm>dictionaries</> to
-<!## end>
-     perform this step.  Various standard dictionaries are provided, and
-     custom ones can be created for specific needs.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <emphasis>Storing preprocessed documents optimized for
-     searching</emphasis>.  For example, each document can be represented
-     as a sorted array of normalized lexemes. Along with the lexemes it is
-     often desirable to store positional information to use for
-     <firstterm>proximity ranking</firstterm>, so that a document that
-     contains a more <quote>dense</> region of query words is
-     assigned a higher rank than one with scattered query words.
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   Dictionaries allow fine-grained control over how tokens are normalized.
-   With appropriate dictionaries, you can:
-  </para>
-
-  <itemizedlist  spacing="compact" mark="bullet">
-   <listitem>
-    <para>
-     Define stop words that should not be indexed.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Map synonyms to a single word using <application>Ispell</>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Map phrases to a single word using a thesaurus.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Map different variations of a word to a canonical form using
-     an <application>Ispell</> dictionary.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Map different variations of a word to a canonical form using
-     <application>Snowball</> stemmer rules.
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   A data type <type>tsvector</type> is provided for storing preprocessed
-   documents, along with a type <type>tsquery</type> for representing processed
-   queries (<xref linkend="datatype-textsearch">).  There are many
-   functions and operators available for these data types
-   (<xref linkend="functions-textsearch">), the most important of which is
-   the match operator <literal>@@</literal>, which we introduce in
-   <xref linkend="textsearch-matching">.  Full text searches can be accelerated
-   using indexes (<xref linkend="textsearch-indexes">).
-  </para>
-
-
-  <sect2 id="textsearch-document">
-   <title>What Is a Document?</title>
-
-   <indexterm zone="textsearch-document">
-    <primary>document</primary>
-    <secondary>text search</secondary>
-   </indexterm>
-
-   <para>
-    A <firstterm>document</> is the unit of searching in a full text search
-    system; for example, a magazine article or email message.  The text search
-    engine must be able to parse documents and store associations of lexemes
-    (key words) with their parent document. Later, these associations are
-    used to search for documents that contain query words.
-   </para>
-
-   <para>
-<!## PG>
-    For searches within <productname>PostgreSQL</productname>,
-<!## end>
-<!## XC>
-    For searches within <productname>Postgres-XC</productname>,
-<!## end>
-<!## XL>
-    For searches within <productname>Postgres-XL</productname>,
-<!## end>
-    a document is normally a textual field within a row of a database table,
-    or possibly a combination (concatenation) of such fields, perhaps stored
-    in several tables or obtained dynamically. In other words, a document can
-    be constructed from different parts for indexing and it might not be
-    stored anywhere as a whole. For example:
-
-<programlisting>
-SELECT title || ' ' ||  author || ' ' ||  abstract || ' ' || body AS document
-FROM messages
-WHERE mid = 12;
-
-SELECT m.title || ' ' || m.author || ' ' || m.abstract || ' ' || d.body AS document
-FROM messages m, docs d
-WHERE mid = did AND mid = 12;
-</programlisting>
-   </para>
-
-   <note>
-    <para>
-     Actually, in these example queries, <function>coalesce</function>
-     should be used to prevent a single <literal>NULL</literal> attribute from
-     causing a <literal>NULL</literal> result for the whole document.
-    </para>
-   </note>
-
-   <para>
-    Another possibility is to store the documents as simple text files in the
-    file system. In this case, the database can be used to store the full text
-    index and to execute searches, and some unique identifier can be used to
-    retrieve the document from the file system.  However, retrieving files
-    from outside the database requires superuser permissions or special
-    function support, so this is usually less convenient than keeping all
-<!## PG>
-    the data inside <productname>PostgreSQL</productname>.  Also, keeping
-<!## end>
-<!## XC>
-    the data inside <productname>Postgres-XC</productname>.  Also, keeping
-<!## end>
-<!## XL>
-    the data inside <productname>Postgres-XL</productname>.  Also, keeping
-<!## end>
-    everything inside the database allows easy access
-    to document metadata to assist in indexing and display.
-   </para>
-
-   <para>
-    For text search purposes, each document must be reduced to the
-    preprocessed <type>tsvector</> format.  Searching and ranking
-    are performed entirely on the <type>tsvector</> representation
-    of a document &mdash; the original text need only be retrieved
-    when the document has been selected for display to a user.
-    We therefore often speak of the <type>tsvector</> as being the
-    document, but of course it is only a compact representation of
-    the full document.
-   </para>
-  </sect2>
-
-  <sect2 id="textsearch-matching">
-   <title>Basic Text Matching</title>
-
-   <para>
-<!## PG>
-    Full text searching in <productname>PostgreSQL</productname> is based on
-<!## end>
-<!## XC>
-    Full text searching in <productname>Postgres-XC</productname> is based on
-<!## end>
-<!## XL>
-    Full text searching in <productname>Postgres-XL</productname> is based on
-<!## end>
-    the match operator <literal>@@</literal>, which returns
-    <literal>true</literal> if a <type>tsvector</type>
-    (document) matches a <type>tsquery</type> (query).
-    It doesn't matter which data type is written first:
-
-<programlisting>
-SELECT 'a fat cat sat on a mat and ate a fat rat'::tsvector @@ 'cat &amp; rat'::tsquery;
- ?column?
-----------
- t
-
-SELECT 'fat &amp; cow'::tsquery @@ 'a fat cat sat on a mat and ate a fat rat'::tsvector;
- ?column?
-----------
- f
-</programlisting>
-   </para>
-
-   <para>
-    As the above example suggests, a <type>tsquery</type> is not just raw
-    text, any more than a <type>tsvector</type> is.  A <type>tsquery</type>
-    contains search terms, which must be already-normalized lexemes, and
-    may combine multiple terms using AND, OR, and NOT operators.
-    (For details see <xref linkend="datatype-textsearch">.)  There are
-    functions <function>to_tsquery</> and <function>plainto_tsquery</>
-    that are helpful in converting user-written text into a proper
-    <type>tsquery</type>, for example by normalizing words appearing in
-    the text.  Similarly, <function>to_tsvector</> is used to parse and
-    normalize a document string.  So in practice a text search match would
-    look more like this:
-
-<programlisting>
-SELECT to_tsvector('fat cats ate fat rats') @@ to_tsquery('fat &amp; rat');
- ?column? 
-----------
- t
-</programlisting>
-
-    Observe that this match would not succeed if written as
-
-<programlisting>
-SELECT 'fat cats ate fat rats'::tsvector @@ to_tsquery('fat &amp; rat');
- ?column? 
-----------
- f
-</programlisting>
-
-    since here no normalization of the word <literal>rats</> will occur.
-    The elements of a <type>tsvector</> are lexemes, which are assumed
-    already normalized, so <literal>rats</> does not match <literal>rat</>.
-   </para>
-
-   <para>
-    The <literal>@@</literal> operator also
-    supports <type>text</type> input, allowing explicit conversion of a text
-    string to <type>tsvector</type> or <type>tsquery</> to be skipped
-    in simple cases.  The variants available are:
-
-<programlisting>
-tsvector @@ tsquery
-tsquery  @@ tsvector
-text @@ tsquery
-text @@ text
-</programlisting>
-   </para>
-
-   <para>
-    The first two of these we saw already.
-    The form <type>text</type> <literal>@@</literal> <type>tsquery</type>
-    is equivalent to <literal>to_tsvector(x) @@ y</literal>.
-    The form <type>text</type> <literal>@@</literal> <type>text</type>
-    is equivalent to <literal>to_tsvector(x) @@ plainto_tsquery(y)</literal>.
-   </para>
-  </sect2>
-
-  <sect2 id="textsearch-intro-configurations">
-   <title>Configurations</title>
-
-   <para>
-    The above are all simple text search examples.  As mentioned before, full
-    text search functionality includes the ability to do many more things:
-    skip indexing certain words (stop words), process synonyms, and use
-    sophisticated parsing, e.g., parse based on more than just white space.
-    This functionality is controlled by <firstterm>text search
-<!## PG>
-    configurations</>.  <productname>PostgreSQL</> comes with predefined
-<!## end>
-<!## XC>
-    configurations</>.  <productname>Postgres-XC</> comes with predefined
-<!## end>
-<!## XL>
-    configurations</>.  <productname>Postgres-XL</> comes with predefined
-<!## end>
-    configurations for many languages, and you can easily create your own
-    configurations.  (<application>psql</>'s <command>\dF</> command
-    shows all available configurations.)
-   </para>
-
-   <para>
-    During installation an appropriate configuration is selected and
-    <xref linkend="guc-default-text-search-config"> is set accordingly
-    in <filename>postgresql.conf</>.  If you are using the same text search
-    configuration for the entire cluster you can use the value in
-    <filename>postgresql.conf</>.  To use different configurations
-    throughout the cluster but the same configuration within any one database,
-    use <command>ALTER DATABASE ... SET</>.  Otherwise, you can set
-    <varname>default_text_search_config</varname> in each session.
-   </para>
-
-   <para>
-    Each text search function that depends on a configuration has an optional
-    <type>regconfig</> argument, so that the configuration to use can be
-    specified explicitly.  <varname>default_text_search_config</varname>
-    is used only when this argument is omitted.
-   </para>
-
-   <para>
-    To make it easier to build custom text search configurations, a
-    configuration is built up from simpler database objects.
-<!## PG>
-    <productname>PostgreSQL</>'s text search facility provides
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</>'s text search facility provides
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</>'s text search facility provides
-<!## end>
-    four types of configuration-related database objects:
-   </para>
-
-  <itemizedlist  spacing="compact" mark="bullet">
-   <listitem>
-    <para>
-     <firstterm>Text search parsers</> break documents into tokens
-     and classify each token (for example, as words or numbers).
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <firstterm>Text search dictionaries</> convert tokens to normalized
-     form and reject stop words.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <firstterm>Text search templates</> provide the functions underlying
-     dictionaries.  (A dictionary simply specifies a template and a set
-     of parameters for the template.)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     <firstterm>Text search configurations</> select a parser and a set
-     of dictionaries to use to normalize the tokens produced by the parser.
-    </para>
-   </listitem>
-  </itemizedlist>
-
-   <para>
-    Text search parsers and templates are built from low-level C functions;
-    therefore it requires C programming ability to develop new ones, and
-    superuser privileges to install one into a database.  (There are examples
-    of add-on parsers and templates in the <filename>contrib/</> area of the
-<!## PG>
-    <productname>PostgreSQL</> distribution.)  Since dictionaries and
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> distribution.)  Since dictionaries and
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> distribution.)  Since dictionaries and
-<!## end>
-    configurations just parameterize and connect together some underlying
-    parsers and templates, no special privilege is needed to create a new
-    dictionary or configuration.  Examples of creating custom dictionaries and
-    configurations appear later in this chapter.
-   </para>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="textsearch-tables">
-  <title>Tables and Indexes</title>
-
-  <para>
-   The examples in the previous section illustrated full text matching using
-   simple constant strings.  This section shows how to search table data,
-   optionally using indexes.
-  </para>
-
-  <sect2 id="textsearch-tables-search">
-   <title>Searching a Table</title>
-
-   <para>
-    It is possible to do a full text search without an index.  A simple query
-    to print the <structname>title</> of each row that contains the word
-    <literal>friend</> in its <structfield>body</> field is:
-
-<programlisting>
-SELECT title
-FROM pgweb
-WHERE to_tsvector('english', body) @@ to_tsquery('english', 'friend');
-</programlisting>
-
-    This will also find related words such as <literal>friends</>
-    and <literal>friendly</>, since all these are reduced to the same
-    normalized lexeme.
-   </para>
-
-   <para>
-    The query above specifies that the <literal>english</> configuration
-    is to be used to parse and normalize the strings.  Alternatively we
-    could omit the configuration parameters:
-
-<programlisting>
-SELECT title
-FROM pgweb
-WHERE to_tsvector(body) @@ to_tsquery('friend');
-</programlisting>
-
-    This query will use the configuration set by <xref
-    linkend="guc-default-text-search-config">.
-   </para>
-
-   <para>
-    A more complex example is to
-    select the ten most recent documents that contain <literal>create</> and
-    <literal>table</> in the <structname>title</> or <structname>body</>:
-
-<programlisting>
-SELECT title
-FROM pgweb
-WHERE to_tsvector(title || ' ' || body) @@ to_tsquery('create &amp; table')
-ORDER BY last_mod_date DESC
-LIMIT 10;
-</programlisting>
-
-    For clarity we omitted the <function>coalesce</function> function calls
-    which would be needed to find rows that contain <literal>NULL</literal>
-    in one of the two fields.
-   </para>
-
-   <para>
-    Although these queries will work without an index, most applications
-    will find this approach too slow, except perhaps for occasional ad-hoc
-    searches.  Practical use of text searching usually requires creating
-    an index.
-   </para>
-
-  </sect2>
-
-  <sect2 id="textsearch-tables-index">
-   <title>Creating Indexes</title>
-
-   <para>
-    We can create a <acronym>GIN</acronym> index (<xref
-    linkend="textsearch-indexes">) to speed up text searches:
-
-<programlisting>
-CREATE INDEX pgweb_idx ON pgweb USING gin(to_tsvector('english', body));
-</programlisting>
-
-    Notice that the 2-argument version of <function>to_tsvector</function> is
-    used.  Only text search functions that specify a configuration name can
-    be used in expression indexes (<xref linkend="indexes-expressional">).
-    This is because the index contents must be unaffected by <xref
-    linkend="guc-default-text-search-config">.  If they were affected, the
-    index contents might be inconsistent because different entries could
-    contain <type>tsvector</>s that were created with different text search
-    configurations, and there would be no way to guess which was which.  It
-    would be impossible to dump and restore such an index correctly.
-   </para>
-
-   <para>
-    Because the two-argument version of <function>to_tsvector</function> was
-    used in the index above, only a query reference that uses the 2-argument
-    version of <function>to_tsvector</function> with the same configuration
-    name will use that index.  That is, <literal>WHERE
-    to_tsvector('english', body) @@ 'a &amp; b'</> can use the index,
-    but <literal>WHERE to_tsvector(body) @@ 'a &amp; b'</> cannot.
-    This ensures that an index will be used only with the same configuration
-    used to create the index entries.
-   </para>
-
-  <para>
-    It is possible to set up more complex expression indexes wherein the
-    configuration name is specified by another column, e.g.:
-
-<programlisting>
-CREATE INDEX pgweb_idx ON pgweb USING gin(to_tsvector(config_name, body));
-</programlisting>
-
-    where <literal>config_name</> is a column in the <literal>pgweb</>
-    table.  This allows mixed configurations in the same index while
-    recording which configuration was used for each index entry.  This
-    would be useful, for example, if the document collection contained
-    documents in different languages.  Again,
-    queries that are meant to use the index must be phrased to match, e.g.,
-    <literal>WHERE to_tsvector(config_name, body) @@ 'a &amp; b'</>.
-   </para>
-
-   <para>
-    Indexes can even concatenate columns:
-
-<programlisting>
-CREATE INDEX pgweb_idx ON pgweb USING gin(to_tsvector('english', title || ' ' || body));
-</programlisting>
-   </para>
-
-   <para>
-    Another approach is to create a separate <type>tsvector</> column
-    to hold the output of <function>to_tsvector</>.  This example is a
-    concatenation of <literal>title</literal> and <literal>body</literal>,
-    using <function>coalesce</> to ensure that one field will still be
-    indexed when the other is <literal>NULL</>:
-
-<programlisting>
-ALTER TABLE pgweb ADD COLUMN textsearchable_index_col tsvector;
-UPDATE pgweb SET textsearchable_index_col =
-     to_tsvector('english', coalesce(title,'') || ' ' || coalesce(body,''));
-</programlisting>
-
-    Then we create a <acronym>GIN</acronym> index to speed up the search:
-
-<programlisting>
-CREATE INDEX textsearch_idx ON pgweb USING gin(textsearchable_index_col);
-</programlisting>
-
-    Now we are ready to perform a fast full text search:
-
-<programlisting>
-SELECT title
-FROM pgweb
-WHERE textsearchable_index_col @@ to_tsquery('create &amp; table')
-ORDER BY last_mod_date DESC
-LIMIT 10;
-</programlisting>
-   </para>
-
-   <para>
-    When using a separate column to store the <type>tsvector</>
-    representation,
-    it is necessary to create a trigger to keep the <type>tsvector</>
-    column current anytime <literal>title</> or <literal>body</> changes.
-    <xref linkend="textsearch-update-triggers"> explains how to do that.
-   </para>
-
-   <para>
-    One advantage of the separate-column approach over an expression index
-    is that it is not necessary to explicitly specify the text search
-    configuration in queries in order to make use of the index.  As shown
-    in the example above, the query can depend on
-    <varname>default_text_search_config</>.  Another advantage is that
-    searches will be faster, since it will not be necessary to redo the
-    <function>to_tsvector</> calls to verify index matches.  (This is more
-    important when using a GiST index than a GIN index; see <xref
-    linkend="textsearch-indexes">.)  The expression-index approach is
-    simpler to set up, however, and it requires less disk space since the
-    <type>tsvector</> representation is not stored explicitly.
-   </para>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="textsearch-controls">
-  <title>Controlling Text Search</title>
-
-  <para>
-   To implement full text searching there must be a function to create a
-   <type>tsvector</type> from a document and a <type>tsquery</type> from a
-   user query. Also, we need to return results in a useful order, so we need
-   a function that compares documents with respect to their relevance to
-   the query. It's also important to be able to display the results nicely.
-<!## PG>
-   <productname>PostgreSQL</productname> provides support for all of these
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> provides support for all of these
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> provides support for all of these
-<!## end>
-   functions.
-  </para>
-
-  <sect2 id="textsearch-parsing-documents">
-   <title>Parsing Documents</title>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> provides the
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> provides the
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> provides the
-<!## end>
-    function <function>to_tsvector</function> for converting a document to
-    the <type>tsvector</type> data type.
-   </para>
-
-   <indexterm>
-    <primary>to_tsvector</primary>
-   </indexterm>
-
-<synopsis>
-to_tsvector(<optional> <replaceable class="PARAMETER">config</replaceable> <type>regconfig</>, </optional> <replaceable class="PARAMETER">document</replaceable> <type>text</>) returns <type>tsvector</>
-</synopsis>
-
-   <para>
-    <function>to_tsvector</function> parses a textual document into tokens,
-    reduces the tokens to lexemes, and returns a <type>tsvector</type> which
-    lists the lexemes together with their positions in the document.
-    The document is processed according to the specified or default
-    text search configuration.
-    Here is a simple example:
-
-<screen>
-SELECT to_tsvector('english', 'a fat  cat sat on a mat - it ate a fat rats');
-                  to_tsvector
------------------------------------------------------
- 'ate':9 'cat':3 'fat':2,11 'mat':7 'rat':12 'sat':4
-</screen>
-   </para>
-
-   <para>
-    In the example above we see that the resulting <type>tsvector</type> does not
-    contain the words <literal>a</literal>, <literal>on</literal>, or
-    <literal>it</literal>, the word <literal>rats</literal> became
-    <literal>rat</literal>, and the punctuation sign <literal>-</literal> was
-    ignored.
-   </para>
-
-   <para>
-    The <function>to_tsvector</function> function internally calls a parser
-    which breaks the document text into tokens and assigns a type to
-    each token.  For each token, a list of
-    dictionaries (<xref linkend="textsearch-dictionaries">) is consulted,
-    where the list can vary depending on the token type.  The first dictionary
-    that <firstterm>recognizes</> the token emits one or more normalized
-    <firstterm>lexemes</firstterm> to represent the token.  For example,
-    <literal>rats</literal> became <literal>rat</literal> because one of the
-    dictionaries recognized that the word <literal>rats</literal> is a plural
-    form of <literal>rat</literal>.  Some words are recognized as
-    <firstterm>stop words</> (<xref linkend="textsearch-stopwords">), which
-    causes them to be ignored since they occur too frequently to be useful in
-    searching.  In our example these are
-    <literal>a</literal>, <literal>on</literal>, and <literal>it</literal>.
-    If no dictionary in the list recognizes the token then it is also ignored.
-    In this example that happened to the punctuation sign <literal>-</literal>
-    because there are in fact no dictionaries assigned for its token type
-    (<literal>Space symbols</literal>), meaning space tokens will never be
-    indexed. The choices of parser, dictionaries and which types of tokens to
-    index are determined by the selected text search configuration (<xref
-    linkend="textsearch-configuration">).  It is possible to have
-    many different configurations in the same database, and predefined
-    configurations are available for various languages. In our example
-    we used the default configuration <literal>english</literal> for the
-    English language.
-   </para>
-
-   <para>
-    The function <function>setweight</function> can be used to label the
-    entries of a <type>tsvector</type> with a given <firstterm>weight</>,
-    where a weight is one of the letters <literal>A</>, <literal>B</>,
-    <literal>C</>, or <literal>D</>.
-    This is typically used to mark entries coming from
-    different parts of a document, such as title versus body.  Later, this
-    information can be used for ranking of search results.
-   </para>
-
-   <para>
-    Because <function>to_tsvector</function>(<literal>NULL</literal>) will
-    return <literal>NULL</literal>, it is recommended to use
-    <function>coalesce</function> whenever a field might be null.
-    Here is the recommended method for creating
-    a <type>tsvector</type> from a structured document:
-
-<programlisting>
-UPDATE tt SET ti =
-    setweight(to_tsvector(coalesce(title,'')), 'A')    ||
-    setweight(to_tsvector(coalesce(keyword,'')), 'B')  ||
-    setweight(to_tsvector(coalesce(abstract,'')), 'C') ||
-    setweight(to_tsvector(coalesce(body,'')), 'D');
-</programlisting>
-
-    Here we have used <function>setweight</function> to label the source
-    of each lexeme in the finished <type>tsvector</type>, and then merged
-    the labeled <type>tsvector</type> values using the <type>tsvector</>
-    concatenation operator <literal>||</>.  (<xref
-    linkend="textsearch-manipulate-tsvector"> gives details about these
-    operations.)
-   </para>
-
-  </sect2>
-
-  <sect2 id="textsearch-parsing-queries">
-   <title>Parsing Queries</title>
-
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> provides the
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> provides the
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> provides the
-<!## end>
-    functions <function>to_tsquery</function> and
-    <function>plainto_tsquery</function> for converting a query to
-    the <type>tsquery</type> data type.  <function>to_tsquery</function>
-    offers access to more features than <function>plainto_tsquery</function>,
-    but is less forgiving about its input.
-   </para>
-
-   <indexterm>
-    <primary>to_tsquery</primary>
-   </indexterm>
-
-<synopsis>
-to_tsquery(<optional> <replaceable class="PARAMETER">config</replaceable> <type>regconfig</>, </optional> <replaceable class="PARAMETER">querytext</replaceable> <type>text</>) returns <type>tsquery</>
-</synopsis>
-
-   <para>
-    <function>to_tsquery</function> creates a <type>tsquery</> value from
-    <replaceable>querytext</replaceable>, which must consist of single tokens
-    separated by the Boolean operators <literal>&amp;</literal> (AND),
-    <literal>|</literal> (OR) and <literal>!</literal> (NOT).  These operators
-    can be grouped using parentheses.  In other words, the input to
-    <function>to_tsquery</function> must already follow the general rules for
-    <type>tsquery</> input, as described in <xref
-    linkend="datatype-textsearch">.  The difference is that while basic
-    <type>tsquery</> input takes the tokens at face value,
-    <function>to_tsquery</function> normalizes each token to a lexeme using
-    the specified or default configuration, and discards any tokens that are
-    stop words according to the configuration.  For example:
-
-<screen>
-SELECT to_tsquery('english', 'The &amp; Fat &amp; Rats');
-  to_tsquery   
----------------
- 'fat' &amp; 'rat'
-</screen>
-
-    As in basic <type>tsquery</> input, weight(s) can be attached to each
-    lexeme to restrict it to match only <type>tsvector</> lexemes of those
-    weight(s).  For example:
-
-<screen>
-SELECT to_tsquery('english', 'Fat | Rats:AB');
-    to_tsquery    
-------------------
- 'fat' | 'rat':AB
-</screen>
-
-    Also, <literal>*</> can be attached to a lexeme to specify prefix matching:
-
-<screen>
-SELECT to_tsquery('supern:*A &amp; star:A*B');
-        to_tsquery        
---------------------------
- 'supern':*A &amp; 'star':*AB
-</screen>
-
-    Such a lexeme will match any word in a <type>tsvector</> that begins
-    with the given string.
-   </para>
-
-   <para>
-    <function>to_tsquery</function> can also accept single-quoted
-    phrases.  This is primarily useful when the configuration includes a
-    thesaurus dictionary that may trigger on such phrases.
-    In the example below, a thesaurus contains the rule <literal>supernovae
-    stars : sn</literal>:
-
-<screen>
-SELECT to_tsquery('''supernovae stars'' &amp; !crab');
-  to_tsquery
----------------
- 'sn' &amp; !'crab'
-</screen>
-
-    Without quotes, <function>to_tsquery</function> will generate a syntax
-    error for tokens that are not separated by an AND or OR operator.
-   </para>
-
-   <indexterm>
-    <primary>plainto_tsquery</primary>
-   </indexterm>
-
-<synopsis>
-plainto_tsquery(<optional> <replaceable class="PARAMETER">config</replaceable> <type>regconfig</>, </optional> <replaceable class="PARAMETER">querytext</replaceable> <type>text</>) returns <type>tsquery</>
-</synopsis>
-
-   <para>
-    <function>plainto_tsquery</> transforms unformatted text
-    <replaceable>querytext</replaceable> to <type>tsquery</type>.
-    The text is parsed and normalized much as for <function>to_tsvector</>,
-    then the <literal>&amp;</literal> (AND) Boolean operator is inserted
-    between surviving words.
-   </para>
-
-   <para>
-    Example:
-
-<screen>
-SELECT plainto_tsquery('english', 'The Fat Rats');
- plainto_tsquery 
------------------
- 'fat' &amp; 'rat'
-</screen>
-
-    Note that <function>plainto_tsquery</> cannot
-    recognize Boolean operators, weight labels, or prefix-match labels
-    in its input:
-
-<screen>
-SELECT plainto_tsquery('english', 'The Fat &amp; Rats:C');
-   plainto_tsquery   
----------------------
- 'fat' &amp; 'rat' &amp; 'c'
-</screen>
-
-    Here, all the input punctuation was discarded as being space symbols.
-   </para>
-
-  </sect2>
-
-  <sect2 id="textsearch-ranking">
-   <title>Ranking Search Results</title>
-
-   <para>
-    Ranking attempts to measure how relevant documents are to a particular
-    query, so that when there are many matches the most relevant ones can be
-<!## PG>
-    shown first.  <productname>PostgreSQL</productname> provides two
-<!## end>
-<!## XC>
-    shown first.  <productname>Postgres-XC</productname> provides two
-<!## end>
-<!## XL>
-    shown first.  <productname>Postgres-XL</productname> provides two
-<!## end>
-    predefined ranking functions, which take into account lexical, proximity,
-    and structural information; that is, they consider how often the query
-    terms appear in the document, how close together the terms are in the
-    document, and how important is the part of the document where they occur.
-    However, the concept of relevancy is vague and very application-specific.
-    Different applications might require additional information for ranking,
-    e.g., document modification time.  The built-in ranking functions are only
-    examples.  You can write your own ranking functions and/or combine their
-    results with additional factors to fit your specific needs.
-   </para>
-
-   <para>
-    The two ranking functions currently available are:
-
-    <variablelist>
-
-     <varlistentry>
-
-      <indexterm>
-       <primary>ts_rank</primary>
-      </indexterm>
-
-      <term>
-<synopsis>
-ts_rank(<optional> <replaceable class="PARAMETER">weights</replaceable> <type>float4[]</>, </optional> <replaceable class="PARAMETER">vector</replaceable> <type>tsvector</>,
-        <replaceable class="PARAMETER">query</replaceable> <type>tsquery</> <optional>, <replaceable class="PARAMETER">normalization</replaceable> <type>integer</> </optional>) returns <type>float4</>
-</synopsis>
-      </term>
-
-      <listitem>
-       <para>
-        Standard ranking function.<!-- TODO document this better -->
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-
-      <indexterm>
-       <primary>ts_rank_cd</primary>
-      </indexterm>
-
-      <term>
-<synopsis>
-ts_rank_cd(<optional> <replaceable class="PARAMETER">weights</replaceable> <type>float4[]</>, </optional> <replaceable class="PARAMETER">vector</replaceable> <type>tsvector</>,
-           <replaceable class="PARAMETER">query</replaceable> <type>tsquery</> <optional>, <replaceable class="PARAMETER">normalization</replaceable> <type>integer</> </optional>) returns <type>float4</>
-</synopsis>
-      </term>
-
-      <listitem>
-       <para>
-        This function computes the <firstterm>cover density</firstterm>
-        ranking for the given document vector and query, as described in
-        Clarke, Cormack, and Tudhope's "Relevance Ranking for One to Three
-        Term Queries" in the journal "Information Processing and Management",
-        1999.
-       </para>
-
-       <para>
-        This function requires positional information in its input.
-        Therefore it will not work on <quote>stripped</> <type>tsvector</>
-        values &mdash; it will always return zero.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-   </para>
-
-   <para>
-    For both these functions,
-    the optional <replaceable class="PARAMETER">weights</replaceable>
-    argument offers the ability to weigh word instances more or less
-    heavily depending on how they are labeled.  The weight arrays specify
-    how heavily to weigh each category of word, in the order:
-
-<synopsis>
-{D-weight, C-weight, B-weight, A-weight}
-</synopsis>
-
-    If no <replaceable class="PARAMETER">weights</replaceable> are provided,
-    then these defaults are used:
-
-<programlisting>
-{0.1, 0.2, 0.4, 1.0}
-</programlisting>
-
-    Typically weights are used to mark words from special areas of the
-    document, like the title or an initial abstract, so they can be
-    treated with more or less importance than words in the document body.
-   </para>
-
-   <para>
-    Since a longer document has a greater chance of containing a query term
-    it is reasonable to take into account document size, e.g., a hundred-word
-    document with five instances of a search word is probably more relevant
-    than a thousand-word document with five instances.  Both ranking functions
-    take an integer <replaceable>normalization</replaceable> option that
-    specifies whether and how a document's length should impact its rank.
-    The integer option controls several behaviors, so it is a bit mask:
-    you can specify one or more behaviors using
-    <literal>|</literal> (for example, <literal>2|4</literal>).
-
-    <itemizedlist  spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       0 (the default) ignores the document length
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       1 divides the rank by 1 + the logarithm of the document length
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       2 divides the rank by the document length
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       4 divides the rank by the mean harmonic distance between extents
-       (this is implemented only by <function>ts_rank_cd</>)
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       8 divides the rank by the number of unique words in document
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       16 divides the rank by 1 + the logarithm of the number
-       of unique words in document
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       32 divides the rank by itself + 1
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    If more than one flag bit is specified, the transformations are
-    applied in the order listed.
-   </para>
-
-   <para>
-    It is important to note that the ranking functions do not use any global
-    information, so it is impossible to produce a fair normalization to 1% or
-    100% as sometimes desired.  Normalization option 32
-    (<literal>rank/(rank+1)</literal>) can be applied to scale all ranks
-    into the range zero to one, but of course this is just a cosmetic change;
-    it will not affect the ordering of the search results.
-   </para>
-
-   <para>
-    Here is an example that selects only the ten highest-ranked matches:
-
-<screen>
-SELECT title, ts_rank_cd(textsearch, query) AS rank
-FROM apod, to_tsquery('neutrino|(dark &amp; matter)') query
-WHERE query @@ textsearch
-ORDER BY rank DESC
-LIMIT 10;
-                     title                     |   rank
------------------------------------------------+----------
- Neutrinos in the Sun                          |      3.1
- The Sudbury Neutrino Detector                 |      2.4
- A MACHO View of Galactic Dark Matter          |  2.01317
- Hot Gas and Dark Matter                       |  1.91171
- The Virgo Cluster: Hot Plasma and Dark Matter |  1.90953
- Rafting for Solar Neutrinos                   |      1.9
- NGC 4650A: Strange Galaxy and Dark Matter     |  1.85774
- Hot Gas and Dark Matter                       |   1.6123
- Ice Fishing for Cosmic Neutrinos              |      1.6
- Weak Lensing Distorts the Universe            | 0.818218
-</screen>
-
-    This is the same example using normalized ranking:
-
-<screen>
-SELECT title, ts_rank_cd(textsearch, query, 32 /* rank/(rank+1) */ ) AS rank
-FROM apod, to_tsquery('neutrino|(dark &amp; matter)') query
-WHERE  query @@ textsearch
-ORDER BY rank DESC
-LIMIT 10;
-                     title                     |        rank
------------------------------------------------+-------------------
- Neutrinos in the Sun                          | 0.756097569485493
- The Sudbury Neutrino Detector                 | 0.705882361190954
- A MACHO View of Galactic Dark Matter          | 0.668123210574724
- Hot Gas and Dark Matter                       |  0.65655958650282
- The Virgo Cluster: Hot Plasma and Dark Matter | 0.656301290640973
- Rafting for Solar Neutrinos                   | 0.655172410958162
- NGC 4650A: Strange Galaxy and Dark Matter     | 0.650072921219637
- Hot Gas and Dark Matter                       | 0.617195790024749
- Ice Fishing for Cosmic Neutrinos              | 0.615384618911517
- Weak Lensing Distorts the Universe            | 0.450010798361481
-</screen>
-   </para>
-
-   <para>
-    Ranking can be expensive since it requires consulting the
-    <type>tsvector</type> of each matching document, which can be I/O bound and
-    therefore slow. Unfortunately, it is almost impossible to avoid since
-    practical queries often result in large numbers of matches.
-   </para>
-
-  </sect2>
-
-  <sect2 id="textsearch-headline">
-   <title>Highlighting Results</title>
-
-   <para>
-    To present search results it is ideal to show a part of each document and
-    how it is related to the query. Usually, search engines show fragments of
-<!## PG>
-    the document with marked search terms.  <productname>PostgreSQL</>
-<!## end>
-<!## XC>
-    the document with marked search terms.  <productname>Postgres-XC</>
-<!## end>
-<!## XL>
-    the document with marked search terms.  <productname>Postgres-XL</>
-<!## end>
-    provides a function <function>ts_headline</function> that
-    implements this functionality.
-   </para>
-
-   <indexterm>
-    <primary>ts_headline</primary>
-   </indexterm>
-
-<synopsis>
-ts_headline(<optional> <replaceable class="PARAMETER">config</replaceable> <type>regconfig</>, </optional> <replaceable class="PARAMETER">document</replaceable> <type>text</>, <replaceable class="PARAMETER">query</replaceable> <type>tsquery</> <optional>, <replaceable class="PARAMETER">options</replaceable> <type>text</> </optional>) returns <type>text</>
-</synopsis>
-
-   <para>
-    <function>ts_headline</function> accepts a document along
-    with a query, and returns an excerpt from
-    the document in which terms from the query are highlighted.  The
-    configuration to be used to parse the document can be specified by
-    <replaceable>config</replaceable>; if <replaceable>config</replaceable>
-    is omitted, the
-    <varname>default_text_search_config</varname> configuration is used.
-   </para>
-
-   <para>
-    If an <replaceable>options</replaceable> string is specified it must
-    consist of a comma-separated list of one or more
-    <replaceable>option</><literal>=</><replaceable>value</> pairs.
-    The available options are:
-
-    <itemizedlist  spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       <literal>StartSel</>, <literal>StopSel</literal>: the strings with
-       which to delimit query words appearing in the document, to distinguish
-       them from other excerpted words.  You must double-quote these strings
-       if they contain spaces or commas.
-      </para>
-     </listitem>
-     <listitem >
-      <para>
-       <literal>MaxWords</>, <literal>MinWords</literal>: these numbers
-       determine the longest and shortest headlines to output.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <literal>ShortWord</literal>: words of this length or less will be
-       dropped at the start and end of a headline. The default
-       value of three eliminates common English articles.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <literal>HighlightAll</literal>: Boolean flag;  if
-       <literal>true</literal> the whole document will be used as the
-       headline, ignoring the preceding three parameters.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <literal>MaxFragments</literal>: maximum number of text excerpts
-       or fragments to display.  The default value of zero selects a
-       non-fragment-oriented headline generation method.  A value greater than
-       zero selects fragment-based headline generation.  This method
-       finds text fragments with as many query words as possible and
-       stretches those fragments around the query words.  As a result
-       query words are close to the middle of each fragment and have words on
-       each side. Each fragment will be of at most <literal>MaxWords</> and
-       words of length <literal>ShortWord</> or less are dropped at the start
-       and end of each fragment. If not all query words are found in the
-       document, then a single fragment of the first <literal>MinWords</>
-       in the document will be displayed.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <literal>FragmentDelimiter</literal>: When more than one fragment is
-       displayed, the fragments will be separated by this string.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    Any unspecified options receive these defaults:
-
-<programlisting>
-StartSel=&lt;b&gt;, StopSel=&lt;/b&gt;,
-MaxWords=35, MinWords=15, ShortWord=3, HighlightAll=FALSE,
-MaxFragments=0, FragmentDelimiter=" ... "
-</programlisting>
-   </para>
-
-   <para>
-    For example:
-
-<screen>
-SELECT ts_headline('english',
-  'The most common type of search
-is to find all documents containing given query terms
-and return them in order of their similarity to the
-query.',
-  to_tsquery('query &amp; similarity'));
-                        ts_headline                         
-------------------------------------------------------------
- containing given &lt;b&gt;query&lt;/b&gt; terms
- and return them in order of their &lt;b&gt;similarity&lt;/b&gt; to the
- &lt;b&gt;query&lt;/b&gt;.
-
-SELECT ts_headline('english',
-  'The most common type of search
-is to find all documents containing given query terms
-and return them in order of their similarity to the
-query.',
-  to_tsquery('query &amp; similarity'),
-  'StartSel = &lt;, StopSel = &gt;');
-                      ts_headline                      
--------------------------------------------------------
- containing given &lt;query&gt; terms
- and return them in order of their &lt;similarity&gt; to the
- &lt;query&gt;.
-</screen>
-   </para>
-
-   <para>
-    <function>ts_headline</> uses the original document, not a
-    <type>tsvector</type> summary, so it can be slow and should be used with
-    care.  A typical mistake is to call <function>ts_headline</function> for
-    <emphasis>every</emphasis> matching document when only ten documents are
-    to be shown. <acronym>SQL</acronym> subqueries can help; here is an
-    example:
-
-<programlisting>
-SELECT id, ts_headline(body, q), rank
-FROM (SELECT id, body, q, ts_rank_cd(ti, q) AS rank
-      FROM apod, to_tsquery('stars') q
-      WHERE ti @@ q
-      ORDER BY rank DESC
-      LIMIT 10) AS foo;
-</programlisting>
-   </para>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="textsearch-features">
-  <title>Additional Features</title>
-
-  <para>
-   This section describes additional functions and operators that are
-   useful in connection with text search.
-  </para>
-
-  <sect2 id="textsearch-manipulate-tsvector">
-   <title>Manipulating Documents</title>
-
-   <para>
-    <xref linkend="textsearch-parsing-documents"> showed how raw textual
-    documents can be converted into <type>tsvector</> values.
-<!## PG>
-    <productname>PostgreSQL</productname> also provides functions and
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> also provides functions and
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> also provides functions and
-<!## end>
-    operators that can be used to manipulate documents that are already
-    in <type>tsvector</> form.
-   </para>
-
-   <variablelist>
-
-    <varlistentry>
-
-     <indexterm>
-      <primary>tsvector concatenation</primary>
-     </indexterm>
-
-     <term>
-<synopsis>
-<type>tsvector</> || <type>tsvector</>
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       The <type>tsvector</> concatenation operator
-       returns a vector which combines the lexemes and positional information
-       of the two vectors given as arguments.  Positions and weight labels
-       are retained during the concatenation.
-       Positions appearing in the right-hand vector are offset by the largest
-       position mentioned in the left-hand vector, so that the result is
-       nearly equivalent to the result of performing <function>to_tsvector</>
-       on the concatenation of the two original document strings.  (The
-       equivalence is not exact, because any stop-words removed from the
-       end of the left-hand argument will not affect the result, whereas
-       they would have affected the positions of the lexemes in the
-       right-hand argument if textual concatenation were used.)
-      </para>
-
-      <para>
-       One advantage of using concatenation in the vector form, rather than
-       concatenating text before applying <function>to_tsvector</>, is that
-       you can use different configurations to parse different sections
-       of the document.  Also, because the <function>setweight</> function
-       marks all lexemes of the given vector the same way, it is necessary
-       to parse the text and do <function>setweight</> before concatenating
-       if you want to label different parts of the document with different
-       weights.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-
-     <indexterm>
-      <primary>setweight</primary>
-     </indexterm>
-
-     <term>
-<synopsis>
-setweight(<replaceable class="PARAMETER">vector</replaceable> <type>tsvector</>, <replaceable class="PARAMETER">weight</replaceable> <type>"char"</>) returns <type>tsvector</>
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       <function>setweight</> returns a copy of the input vector in which every
-       position has been labeled with the given <replaceable>weight</>, either
-       <literal>A</literal>, <literal>B</literal>, <literal>C</literal>, or
-       <literal>D</literal>.  (<literal>D</literal> is the default for new
-       vectors and as such is not displayed on output.)  These labels are
-       retained when vectors are concatenated, allowing words from different
-       parts of a document to be weighted differently by ranking functions.
-      </para>
-
-      <para>
-       Note that weight labels apply to <emphasis>positions</>, not
-       <emphasis>lexemes</>.  If the input vector has been stripped of
-       positions then <function>setweight</> does nothing.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <indexterm>
-      <primary>length(tsvector)</primary>
-     </indexterm>
-
-     <term>
-<synopsis>
-length(<replaceable class="PARAMETER">vector</replaceable> <type>tsvector</>) returns <type>integer</>
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the number of lexemes stored in the vector.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-
-     <indexterm>
-      <primary>strip</primary>
-     </indexterm>
-
-     <term>
-<synopsis>
-strip(<replaceable class="PARAMETER">vector</replaceable> <type>tsvector</>) returns <type>tsvector</>
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       Returns a vector which lists the same lexemes as the given vector, but
-       which lacks any position or weight information.  While the returned
-       vector is much less useful than an unstripped vector for relevance
-       ranking, it will usually be much smaller.
-      </para>
-     </listitem>
-
-    </varlistentry>
-
-   </variablelist>
-
-  </sect2>
-
-  <sect2 id="textsearch-manipulate-tsquery">
-   <title>Manipulating Queries</title>
-
-   <para>
-    <xref linkend="textsearch-parsing-queries"> showed how raw textual
-    queries can be converted into <type>tsquery</> values.
-<!## PG>
-    <productname>PostgreSQL</productname> also provides functions and
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> also provides functions and
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> also provides functions and
-<!## end>
-    operators that can be used to manipulate queries that are already
-    in <type>tsquery</> form.
-   </para>
-
-   <variablelist>
-
-    <varlistentry>
-
-     <term>
-<synopsis>
-<type>tsquery</> &amp;&amp; <type>tsquery</>
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the AND-combination of the two given queries.
-      </para>
-     </listitem>
-
-    </varlistentry>
-
-    <varlistentry>
-
-     <term>
-<synopsis>
-<type>tsquery</> || <type>tsquery</>
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the OR-combination of the two given queries.
-      </para>
-     </listitem>
-
-    </varlistentry>
-
-    <varlistentry>
-
-     <term>
-<synopsis>
-!! <type>tsquery</>
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the negation (NOT) of the given query.
-      </para>
-     </listitem>
-
-    </varlistentry>
-
-    <varlistentry>
-
-     <indexterm>
-      <primary>numnode</primary>
-     </indexterm>
-
-     <term>
-<synopsis>
-numnode(<replaceable class="PARAMETER">query</replaceable> <type>tsquery</>) returns <type>integer</>
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the number of nodes (lexemes plus operators) in a
-       <type>tsquery</>. This function is useful
-       to determine if the <replaceable>query</replaceable> is meaningful
-       (returns &gt; 0), or contains only stop words (returns 0).
-       Examples:
-
-<screen>
-SELECT numnode(plainto_tsquery('the any'));
-NOTICE:  query contains only stopword(s) or doesn't contain lexeme(s), ignored
- numnode
----------
-       0
-
-SELECT numnode('foo &amp; bar'::tsquery);
- numnode
----------
-       3
-</screen>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-
-     <indexterm>
-      <primary>querytree</primary>
-     </indexterm>
-
-     <term>
-<synopsis>
-querytree(<replaceable class="PARAMETER">query</replaceable> <type>tsquery</>) returns <type>text</>
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       Returns the portion of a <type>tsquery</> that can be used for
-       searching an index.  This function is useful for detecting
-       unindexable queries, for example those containing only stop words
-       or only negated terms.  For example:
-
-<screen>
-SELECT querytree(to_tsquery('!defined'));
- querytree
------------
-
-</screen>
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-
-   <sect3 id="textsearch-query-rewriting">
-    <title>Query Rewriting</title>
-
-    <indexterm zone="textsearch-query-rewriting">
-     <primary>ts_rewrite</primary>
-    </indexterm>
-
-    <para>
-     The <function>ts_rewrite</function> family of functions search a
-     given <type>tsquery</> for occurrences of a target
-     subquery, and replace each occurrence with a
-     substitute subquery.  In essence this operation is a
-     <type>tsquery</>-specific version of substring replacement.
-     A target and substitute combination can be
-     thought of as a <firstterm>query rewrite rule</>.  A collection
-     of such rewrite rules can be a powerful search aid.
-     For example, you can expand the search using synonyms
-     (e.g., <literal>new york</>, <literal>big apple</>, <literal>nyc</>,
-     <literal>gotham</>) or narrow the search to direct the user to some hot
-     topic.  There is some overlap in functionality between this feature
-     and thesaurus dictionaries (<xref linkend="textsearch-thesaurus">).
-     However, you can modify a set of rewrite rules on-the-fly without
-     reindexing, whereas updating a thesaurus requires reindexing to be
-     effective.
-    </para>
-
-    <variablelist>
-
-     <varlistentry>
-
-      <term>
-<synopsis>
-ts_rewrite (<replaceable class="PARAMETER">query</replaceable> <type>tsquery</>, <replaceable class="PARAMETER">target</replaceable> <type>tsquery</>, <replaceable class="PARAMETER">substitute</replaceable> <type>tsquery</>) returns <type>tsquery</>
-</synopsis>
-      </term>
-
-      <listitem>
-       <para>
-        This form of <function>ts_rewrite</> simply applies a single
-        rewrite rule: <replaceable class="PARAMETER">target</replaceable>
-        is replaced by <replaceable class="PARAMETER">substitute</replaceable>
-        wherever it appears in <replaceable
-        class="PARAMETER">query</replaceable>.  For example:
-
-<screen>
-SELECT ts_rewrite('a &amp; b'::tsquery, 'a'::tsquery, 'c'::tsquery);
- ts_rewrite
-------------
- 'b' &amp; 'c'
-</screen>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-
-      <term>
-<synopsis>
-ts_rewrite (<replaceable class="PARAMETER">query</> <type>tsquery</>, <replaceable class="PARAMETER">select</> <type>text</>) returns <type>tsquery</>
-</synopsis>
-      </term>
-
-      <listitem>
-       <para>
-        This form of <function>ts_rewrite</> accepts a starting
-        <replaceable>query</> and a SQL <replaceable>select</> command, which
-        is given as a text string.  The <replaceable>select</> must yield two
-        columns of <type>tsquery</> type.  For each row of the
-        <replaceable>select</> result, occurrences of the first column value
-        (the target) are replaced by the second column value (the substitute)
-        within the current <replaceable>query</> value.  For example:
-
-<screen>
-CREATE TABLE aliases (t tsquery PRIMARY KEY, s tsquery);
-INSERT INTO aliases VALUES('a', 'c');
-
-SELECT ts_rewrite('a &amp; b'::tsquery, 'SELECT t,s FROM aliases');
- ts_rewrite
-------------
- 'b' &amp; 'c'
-</screen>
-       </para>
-
-       <para>
-        Note that when multiple rewrite rules are applied in this way,
-        the order of application can be important; so in practice you will
-        want the source query to <literal>ORDER BY</> some ordering key.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-    <para>
-     Let's consider a real-life astronomical example. We'll expand query
-     <literal>supernovae</literal> using table-driven rewriting rules:
-
-<screen>
-CREATE TABLE aliases (t tsquery primary key, s tsquery);
-INSERT INTO aliases VALUES(to_tsquery('supernovae'), to_tsquery('supernovae|sn'));
-
-SELECT ts_rewrite(to_tsquery('supernovae &amp; crab'), 'SELECT * FROM aliases');
-           ts_rewrite            
----------------------------------
- 'crab' &amp; ( 'supernova' | 'sn' )
-</screen>
-
-     We can change the rewriting rules just by updating the table:
-
-<screen>
-UPDATE aliases
-SET s = to_tsquery('supernovae|sn &amp; !nebulae')
-WHERE t = to_tsquery('supernovae');
-
-SELECT ts_rewrite(to_tsquery('supernovae &amp; crab'), 'SELECT * FROM aliases');
-                 ts_rewrite                  
----------------------------------------------
- 'crab' &amp; ( 'supernova' | 'sn' &amp; !'nebula' )
-</screen>
-    </para>
-
-    <para>
-     Rewriting can be slow when there are many rewriting rules, since it
-     checks every rule for a possible match. To filter out obvious non-candidate
-     rules we can use the containment operators for the <type>tsquery</type>
-     type. In the example below, we select only those rules which might match
-     the original query:
-
-<screen>
-SELECT ts_rewrite('a &amp; b'::tsquery,
-                  'SELECT t,s FROM aliases WHERE ''a &amp; b''::tsquery @&gt; t');
- ts_rewrite
-------------
- 'b' &amp; 'c'
-</screen>
-    </para>
-
-   </sect3>
-
-  </sect2>
-
-  <sect2 id="textsearch-update-triggers">
-   <title>Triggers for Automatic Updates</title>
-
-   <indexterm>
-    <primary>trigger</primary>
-    <secondary>for updating a derived tsvector column</secondary>
-   </indexterm>
-
-   <para>
-    When using a separate column to store the <type>tsvector</> representation
-    of your documents, it is necessary to create a trigger to update the
-    <type>tsvector</> column when the document content columns change.
-    Two built-in trigger functions are available for this, or you can write
-    your own.
-   </para>
-
-<synopsis>
-tsvector_update_trigger(<replaceable class="PARAMETER">tsvector_column_name</replaceable>, <replaceable class="PARAMETER">config_name</replaceable>, <replaceable class="PARAMETER">text_column_name</replaceable> <optional>, ... </optional>)
-tsvector_update_trigger_column(<replaceable class="PARAMETER">tsvector_column_name</replaceable>, <replaceable class="PARAMETER">config_column_name</replaceable>, <replaceable class="PARAMETER">text_column_name</replaceable> <optional>, ... </optional>)
-</synopsis>
-
-   <para>
-    These trigger functions automatically compute a <type>tsvector</>
-    column from one or more textual columns, under the control of
-    parameters specified in the <command>CREATE TRIGGER</> command.
-    An example of their use is:
-
-<screen>
-CREATE TABLE messages (
-    title       text,
-    body        text,
-    tsv         tsvector
-);
-
-CREATE TRIGGER tsvectorupdate BEFORE INSERT OR UPDATE
-ON messages FOR EACH ROW EXECUTE PROCEDURE
-tsvector_update_trigger(tsv, 'pg_catalog.english', title, body);
-
-INSERT INTO messages VALUES('title here', 'the body text is here');
-
-SELECT * FROM messages;
-   title    |         body          |            tsv             
-------------+-----------------------+----------------------------
- title here | the body text is here | 'bodi':4 'text':5 'titl':1
-
-SELECT title, body FROM messages WHERE tsv @@ to_tsquery('title &amp; body');
-   title    |         body          
-------------+-----------------------
- title here | the body text is here
-</screen>
-
-    Having created this trigger, any change in <structfield>title</> or
-    <structfield>body</> will automatically be reflected into
-    <structfield>tsv</>, without the application having to worry about it.
-   </para>
-
-   <para>
-    The first trigger argument must be the name of the <type>tsvector</>
-    column to be updated.  The second argument specifies the text search
-    configuration to be used to perform the conversion.  For
-    <function>tsvector_update_trigger</>, the configuration name is simply
-    given as the second trigger argument.  It must be schema-qualified as
-    shown above, so that the trigger behavior will not change with changes
-    in <varname>search_path</>.  For
-    <function>tsvector_update_trigger_column</>, the second trigger argument
-    is the name of another table column, which must be of type
-    <type>regconfig</>.  This allows a per-row selection of configuration
-    to be made.  The remaining argument(s) are the names of textual columns
-    (of type <type>text</>, <type>varchar</>, or <type>char</>).  These
-    will be included in the document in the order given.  NULL values will
-    be skipped (but the other columns will still be indexed).
-   </para>
-
-   <para>
-    A limitation of these built-in triggers is that they treat all the
-    input columns alike.  To process columns differently &mdash; for
-    example, to weight title differently from body &mdash; it is necessary
-    to write a custom trigger.  Here is an example using
-    <application>PL/pgSQL</application> as the trigger language:
-
-<programlisting>
-CREATE FUNCTION messages_trigger() RETURNS trigger AS $$
-begin
-  new.tsv :=
-     setweight(to_tsvector('pg_catalog.english', coalesce(new.title,'')), 'A') ||
-     setweight(to_tsvector('pg_catalog.english', coalesce(new.body,'')), 'D');
-  return new;
-end
-$$ LANGUAGE plpgsql;
-
-CREATE TRIGGER tsvectorupdate BEFORE INSERT OR UPDATE
-    ON messages FOR EACH ROW EXECUTE PROCEDURE messages_trigger();
-</programlisting>
-   </para>
-
-   <para>
-    Keep in mind that it is important to specify the configuration name
-    explicitly when creating <type>tsvector</> values inside triggers,
-    so that the column's contents will not be affected by changes to
-    <varname>default_text_search_config</>.  Failure to do this is likely to
-    lead to problems such as search results changing after a dump and reload.
-   </para>
-
-  </sect2>
-
-  <sect2 id="textsearch-statistics">
-   <title>Gathering Document Statistics</title>
-
-   <indexterm>
-    <primary>ts_stat</primary>
-   </indexterm>
-
-   <para>
-    The function <function>ts_stat</> is useful for checking your
-    configuration and for finding stop-word candidates.
-   </para>
-
-<synopsis>
-ts_stat(<replaceable class="PARAMETER">sqlquery</replaceable> <type>text</>, <optional> <replaceable class="PARAMETER">weights</replaceable> <type>text</>, </optional>
-        OUT <replaceable class="PARAMETER">word</replaceable> <type>text</>, OUT <replaceable class="PARAMETER">ndoc</replaceable> <type>integer</>,
-        OUT <replaceable class="PARAMETER">nentry</replaceable> <type>integer</>) returns <type>setof record</>
-</synopsis>
-
-   <para>
-    <replaceable>sqlquery</replaceable> is a text value containing an SQL
-    query which must return a single <type>tsvector</type> column.
-    <function>ts_stat</> executes the query and returns statistics about
-    each distinct lexeme (word) contained in the <type>tsvector</type>
-    data.  The columns returned are
-
-    <itemizedlist  spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       <replaceable>word</> <type>text</> &mdash; the value of a lexeme
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <replaceable>ndoc</> <type>integer</> &mdash; number of documents
-       (<type>tsvector</>s) the word occurred in
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <replaceable>nentry</> <type>integer</> &mdash; total number of
-       occurrences of the word
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    If <replaceable>weights</replaceable> is supplied, only occurrences
-    having one of those weights are counted.
-   </para>
-
-   <para>
-    For example, to find the ten most frequent words in a document collection:
-
-<programlisting>
-SELECT * FROM ts_stat('SELECT vector FROM apod')
-ORDER BY nentry DESC, ndoc DESC, word
-LIMIT 10;
-</programlisting>
-
-    The same, but counting only word occurrences with weight <literal>A</>
-    or <literal>B</>:
-
-<programlisting>
-SELECT * FROM ts_stat('SELECT vector FROM apod', 'ab')
-ORDER BY nentry DESC, ndoc DESC, word
-LIMIT 10;
-</programlisting>
-   </para>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="textsearch-parsers">
-  <title>Parsers</title>
-
-  <para>
-   Text search parsers are responsible for splitting raw document text
-   into <firstterm>tokens</> and identifying each token's type, where
-   the set of possible types is defined by the parser itself.
-   Note that a parser does not modify the text at all &mdash; it simply
-   identifies plausible word boundaries.  Because of this limited scope,
-   there is less need for application-specific custom parsers than there is
-<!## PG>
-   for custom dictionaries.  At present <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   for custom dictionaries.  At present <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   for custom dictionaries.  At present <productname>Postgres-XL</productname>
-<!## end>
-   provides just one built-in parser, which has been found to be useful for a
-   wide range of applications.
-  </para>
-
-  <para>
-   The built-in parser is named <literal>pg_catalog.default</>.
-   It recognizes 23 token types, shown in <xref linkend="textsearch-default-parser">.
-  </para>
-
-  <table id="textsearch-default-parser">
-   <title>Default Parser's Token Types</title>
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Alias</entry>
-      <entry>Description</entry>
-      <entry>Example</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><literal>asciiword</></entry>
-      <entry>Word, all ASCII letters</entry>
-      <entry><literal>elephant</literal></entry>
-     </row>
-     <row>
-      <entry><literal>word</></entry>
-      <entry>Word, all letters</entry>
-      <entry><literal>ma&ntilde;ana</literal></entry>
-     </row>
-     <row>
-      <entry><literal>numword</></entry>
-      <entry>Word, letters and digits</entry>
-      <entry><literal>beta1</literal></entry>
-     </row>
-     <row>
-      <entry><literal>asciihword</></entry>
-      <entry>Hyphenated word, all ASCII</entry>
-      <entry><literal>up-to-date</literal></entry>
-     </row>
-     <row>
-      <entry><literal>hword</></entry>
-      <entry>Hyphenated word, all letters</entry>
-      <entry><literal>l&oacute;gico-matem&aacute;tica</literal></entry>
-     </row>
-     <row>
-      <entry><literal>numhword</></entry>
-      <entry>Hyphenated word, letters and digits</entry>
-      <entry><literal>postgresql-beta1</literal></entry>
-     </row>
-     <row>
-      <entry><literal>hword_asciipart</></entry>
-      <entry>Hyphenated word part, all ASCII</entry>
-<!## PG>
-      <entry><literal>postgresql</literal> in the context <literal>postgresql-beta1</literal></entry>
-<!## end>
-<!## XC>
-      <entry><literal>postgres-XC</literal> in the context <literal>postgresql-beta1</literal></entry>
-<!## end>
-<!## XL>
-      <entry><literal>postgres-XL</literal> in the context <literal>postgresql-beta1</literal></entry>
-<!## end>
-     </row>
-     <row>
-      <entry><literal>hword_part</></entry>
-      <entry>Hyphenated word part, all letters</entry>
-      <entry><literal>l&oacute;gico</literal> or <literal>matem&aacute;tica</literal>
-       in the context <literal>l&oacute;gico-matem&aacute;tica</literal></entry>
-     </row>
-     <row>
-      <entry><literal>hword_numpart</></entry>
-      <entry>Hyphenated word part, letters and digits</entry>
-      <entry><literal>beta1</literal> in the context
-<!## PG>
-       <literal>postgresql-beta1</literal></entry>
-<!## end>
-<!## XC>
-       <literal>postgres-XC-beta1</literal></entry>
-<!## end>
-<!## XL>
-       <literal>postgres-XL-beta1</literal></entry>
-<!## end>
-     </row>
-     <row>
-      <entry><literal>email</></entry>
-      <entry>Email address</entry>
-      <entry><literal>[email protected]</literal></entry>
-     </row>
-     <row>
-      <entry><literal>protocol</></entry>
-      <entry>Protocol head</entry>
-      <entry><literal>http://</literal></entry>
-     </row>
-     <row>
-      <entry><literal>url</></entry>
-      <entry>URL</entry>
-      <entry><literal>example.com/stuff/index.html</literal></entry>
-     </row>
-     <row>
-      <entry><literal>host</></entry>
-      <entry>Host</entry>
-      <entry><literal>example.com</literal></entry>
-     </row>
-     <row>
-      <entry><literal>url_path</></entry>
-      <entry>URL path</entry>
-      <entry><literal>/stuff/index.html</literal>, in the context of a URL</entry>
-     </row>
-     <row>
-      <entry><literal>file</></entry>
-      <entry>File or path name</entry>
-      <entry><literal>/usr/local/foo.txt</literal>, if not within a URL</entry>
-     </row>
-     <row>
-      <entry><literal>sfloat</></entry>
-      <entry>Scientific notation</entry>
-      <entry><literal>-1.234e56</literal></entry>
-     </row>
-     <row>
-      <entry><literal>float</></entry>
-      <entry>Decimal notation</entry>
-      <entry><literal>-1.234</literal></entry>
-     </row>
-     <row>
-      <entry><literal>int</></entry>
-      <entry>Signed integer</entry>
-      <entry><literal>-1234</literal></entry>
-     </row>
-     <row>
-      <entry><literal>uint</></entry>
-      <entry>Unsigned integer</entry>
-      <entry><literal>1234</literal></entry>
-     </row>
-     <row>
-      <entry><literal>version</></entry>
-      <entry>Version number</entry>
-      <entry><literal>8.3.0</literal></entry>
-     </row>
-     <row>
-      <entry><literal>tag</></entry>
-      <entry>XML tag</entry>
-      <entry><literal>&lt;a href="dictionaries.html"&gt;</literal></entry>
-     </row>
-     <row>
-      <entry><literal>entity</></entry>
-      <entry>XML entity</entry>
-      <entry><literal>&amp;amp;</literal></entry>
-     </row>
-     <row>
-      <entry><literal>blank</></entry>
-      <entry>Space symbols</entry>
-      <entry>(any whitespace or punctuation not otherwise recognized)</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <note>
-   <para>
-    The parser's notion of a <quote>letter</> is determined by the database's
-    locale setting, specifically <varname>lc_ctype</>.  Words containing
-    only the basic ASCII letters are reported as a separate token type,
-    since it is sometimes useful to distinguish them.  In most European
-    languages, token types <literal>word</> and <literal>asciiword</>
-    should be treated alike.
-   </para>
-
-   <para>
-    <literal>email</> does not support all valid email characters as
-    defined by RFC 5322.  Specifically, the only non-alphanumeric
-    characters supported for email user names are period, dash, and
-    underscore.
-   </para>
-  </note>
-
-  <para>
-   It is possible for the parser to produce overlapping tokens from the same
-   piece of text.  As an example, a hyphenated word will be reported both
-   as the entire word and as each component:
-
-<screen>
-SELECT alias, description, token FROM ts_debug('foo-bar-beta1');
-      alias      |               description                |     token     
------------------+------------------------------------------+---------------
- numhword        | Hyphenated word, letters and digits      | foo-bar-beta1
- hword_asciipart | Hyphenated word part, all ASCII          | foo
- blank           | Space symbols                            | -
- hword_asciipart | Hyphenated word part, all ASCII          | bar
- blank           | Space symbols                            | -
- hword_numpart   | Hyphenated word part, letters and digits | beta1
-</screen>
-
-   This behavior is desirable since it allows searches to work for both
-   the whole compound word and for components.  Here is another
-   instructive example:
-
-<screen>
-SELECT alias, description, token FROM ts_debug('http://example.com/stuff/index.html');
-  alias   |  description  |            token             
-----------+---------------+------------------------------
- protocol | Protocol head | http://
- url      | URL           | example.com/stuff/index.html
- host     | Host          | example.com
- url_path | URL path      | /stuff/index.html
-</screen>
-  </para>
-
- </sect1>
-
- <sect1 id="textsearch-dictionaries">
-  <title>Dictionaries</title>
-
-  <para>
-   Dictionaries are used to eliminate words that should not be considered in a
-   search (<firstterm>stop words</>), and to <firstterm>normalize</> words so
-   that different derived forms of the same word will match.  A successfully
-   normalized word is called a <firstterm>lexeme</>.  Aside from
-   improving search quality, normalization and removal of stop words reduce the
-   size of the <type>tsvector</type> representation of a document, thereby
-   improving performance.  Normalization does not always have linguistic meaning
-   and usually depends on application semantics.
-  </para>
-
-  <para>
-   Some examples of normalization:
-
-   <itemizedlist  spacing="compact" mark="bullet">
-
-    <listitem>
-     <para>
-      Linguistic - Ispell dictionaries try to reduce input words to a
-      normalized form; stemmer dictionaries remove word endings
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <acronym>URL</acronym> locations can be canonicalized to make
-      equivalent URLs match:
-
-      <itemizedlist  spacing="compact" mark="bullet">
-       <listitem>
-        <para>
-         http://www.pgsql.ru/db/mw/index.html
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         http://www.pgsql.ru/db/mw/
-        </para>
-       </listitem>
-       <listitem>
-        <para>
-         http://www.pgsql.ru/db/../db/mw/index.html
-        </para>
-       </listitem>
-      </itemizedlist>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Color names can be replaced by their hexadecimal values, e.g.,
-      <literal>red, green, blue, magenta -> FF0000, 00FF00, 0000FF, FF00FF</literal>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      If indexing numbers, we can
-      remove some fractional digits to reduce the range of possible
-      numbers, so for example <emphasis>3.14</emphasis>159265359,
-      <emphasis>3.14</emphasis>15926, <emphasis>3.14</emphasis> will be the same
-      after normalization if only two digits are kept after the decimal point.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-  </para>
-
-  <para>
-   A dictionary is a program that accepts a token as
-   input and returns:
-   <itemizedlist  spacing="compact" mark="bullet">
-    <listitem>
-     <para>
-      an array of lexemes if the input token is known to the dictionary
-      (notice that one token can produce more than one lexeme)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      a single lexeme with the <literal>TSL_FILTER</> flag set, to replace
-      the original token with a new token to be passed to subsequent
-      dictionaries (a dictionary that does this is called a
-      <firstterm>filtering dictionary</>)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      an empty array if the dictionary knows the token, but it is a stop word
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      <literal>NULL</literal> if the dictionary does not recognize the input token
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> provides predefined dictionaries for
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> provides predefined dictionaries for
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> provides predefined dictionaries for
-<!## end>
-   many languages.  There are also several predefined templates that can be
-   used to create new dictionaries with custom parameters.  Each predefined
-   dictionary template is described below.  If no existing
-   template is suitable, it is possible to create new ones; see the
-<!## PG>
-   <filename>contrib/</> area of the <productname>PostgreSQL</> distribution
-<!## end>
-<!## XC>
-   <filename>contrib/</> area of the <productname>Postgres-XC</> distribution
-<!## end>
-<!## XL>
-   <filename>contrib/</> area of the <productname>Postgres-XL</> distribution
-<!## end>
-   for examples.
-  </para>
-
-  <para>
-   A text search configuration binds a parser together with a set of
-   dictionaries to process the parser's output tokens.  For each token
-   type that the parser can return, a separate list of dictionaries is
-   specified by the configuration.  When a token of that type is found
-   by the parser, each dictionary in the list is consulted in turn,
-   until some dictionary recognizes it as a known word.  If it is identified
-   as a stop word, or if no dictionary recognizes the token, it will be
-   discarded and not indexed or searched for.
-   Normally, the first dictionary that returns a non-<literal>NULL</>
-   output determines the result, and any remaining dictionaries are not
-   consulted; but a filtering dictionary can replace the given word
-   with a modified word, which is then passed to subsequent dictionaries.
-  </para>
-
-  <para>
-   The general rule for configuring a list of dictionaries
-   is to place first the most narrow, most specific dictionary, then the more
-   general dictionaries, finishing with a very general dictionary, like
-   a <application>Snowball</> stemmer or <literal>simple</>, which
-   recognizes everything.  For example, for an astronomy-specific search
-   (<literal>astro_en</literal> configuration) one could bind token type
-   <type>asciiword</type> (ASCII word) to a synonym dictionary of astronomical
-   terms, a general English dictionary and a <application>Snowball</> English
-   stemmer:
-
-<programlisting>
-ALTER TEXT SEARCH CONFIGURATION astro_en
-    ADD MAPPING FOR asciiword WITH astrosyn, english_ispell, english_stem;
-</programlisting>
-  </para>
-
-  <para>
-   A filtering dictionary can be placed anywhere in the list, except at the
-   end where it'd be useless.  Filtering dictionaries are useful to partially
-   normalize words to simplify the task of later dictionaries.  For example,
-   a filtering dictionary could be used to remove accents from accented
-   letters, as is done by the <xref linkend="unaccent"> module.
-  </para>
-
-  <sect2 id="textsearch-stopwords">
-   <title>Stop Words</title>
-
-   <para>
-    Stop words are words that are very common, appear in almost every
-    document, and have no discrimination value. Therefore, they can be ignored
-    in the context of full text searching. For example, every English text
-    contains words like <literal>a</literal> and <literal>the</>, so it is
-    useless to store them in an index.  However, stop words do affect the
-    positions in <type>tsvector</type>, which in turn affect ranking:
-
-<screen>
-SELECT to_tsvector('english','in the list of stop words');
-        to_tsvector
-----------------------------
- 'list':3 'stop':5 'word':6
-</screen>
-
-    The missing positions 1,2,4 are because of stop words.  Ranks
-    calculated for documents with and without stop words are quite different:
-
-<screen>
-SELECT ts_rank_cd (to_tsvector('english','in the list of stop words'), to_tsquery('list &amp; stop'));
- ts_rank_cd
-------------
-       0.05
-
-SELECT ts_rank_cd (to_tsvector('english','list stop words'), to_tsquery('list &amp; stop'));
- ts_rank_cd
-------------
-        0.1
-</screen>
-
-   </para>
-
-   <para>
-    It is up to the specific dictionary how it treats stop words. For example,
-    <literal>ispell</literal> dictionaries first normalize words and then
-    look at the list of stop words, while <literal>Snowball</literal> stemmers
-    first check the list of stop words. The reason for the different
-    behavior is an attempt to decrease noise.
-   </para>
-
-  </sect2>
-
-  <sect2 id="textsearch-simple-dictionary">
-   <title>Simple Dictionary</title>
-
-   <para>
-    The <literal>simple</> dictionary template operates by converting the
-    input token to lower case and checking it against a file of stop words.
-    If it is found in the file then an empty array is returned, causing
-    the token to be discarded.  If not, the lower-cased form of the word
-    is returned as the normalized lexeme.  Alternatively, the dictionary
-    can be configured to report non-stop-words as unrecognized, allowing
-    them to be passed on to the next dictionary in the list.
-   </para>
-
-   <para>
-    Here is an example of a dictionary definition using the <literal>simple</>
-    template:
-
-<programlisting>
-CREATE TEXT SEARCH DICTIONARY public.simple_dict (
-    TEMPLATE = pg_catalog.simple,
-    STOPWORDS = english
-);
-</programlisting>
-
-    Here, <literal>english</literal> is the base name of a file of stop words.
-    The file's full name will be
-    <filename>$SHAREDIR/tsearch_data/english.stop</>,
-    where <literal>$SHAREDIR</> means the
-<!## PG>
-    <productname>PostgreSQL</productname> installation's shared-data directory,
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> installation's shared-data directory,
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> installation's shared-data directory,
-<!## end>
-<!## PG>
-    often <filename>/usr/local/share/postgresql</> (use <command>pg_config
-<!## end>
-<!## XC>
-    often <filename>/usr/local/share/postgres-XC</> (use <command>pg_config
-<!## end>
-<!## XL>
-    often <filename>/usr/local/share/postgres-XL</> (use <command>pg_config
-<!## end>
-    --sharedir</> to determine it if you're not sure).
-    The file format is simply a list
-    of words, one per line.  Blank lines and trailing spaces are ignored,
-    and upper case is folded to lower case, but no other processing is done
-    on the file contents.
-   </para>
-
-   <para>
-    Now we can test our dictionary:
-
-<screen>
-SELECT ts_lexize('public.simple_dict','YeS');
- ts_lexize
------------
- {yes}
-
-SELECT ts_lexize('public.simple_dict','The');
- ts_lexize
------------
- {}
-</screen>
-   </para>
-
-   <para>
-    We can also choose to return <literal>NULL</>, instead of the lower-cased
-    word, if it is not found in the stop words file.  This behavior is
-    selected by setting the dictionary's <literal>Accept</> parameter to
-    <literal>false</>.  Continuing the example:
-
-<screen>
-ALTER TEXT SEARCH DICTIONARY public.simple_dict ( Accept = false );
-
-SELECT ts_lexize('public.simple_dict','YeS');
- ts_lexize
------------
-
-
-SELECT ts_lexize('public.simple_dict','The');
- ts_lexize
------------
- {}
-</screen>
-   </para>
-
-   <para>
-    With the default setting of <literal>Accept</> = <literal>true</>,
-    it is only useful to place a <literal>simple</> dictionary at the end
-    of a list of dictionaries, since it will never pass on any token to
-    a following dictionary.  Conversely, <literal>Accept</> = <literal>false</>
-    is only useful when there is at least one following dictionary.
-   </para>
-
-   <caution>
-    <para>
-     Most types of dictionaries rely on configuration files, such as files of
-     stop words.  These files <emphasis>must</> be stored in UTF-8 encoding.
-     They will be translated to the actual database encoding, if that is
-     different, when they are read into the server.
-    </para>
-   </caution>
-
-   <caution>
-    <para>
-     Normally, a database session will read a dictionary configuration file
-     only once, when it is first used within the session.  If you modify a
-     configuration file and want to force existing sessions to pick up the
-     new contents, issue an <command>ALTER TEXT SEARCH DICTIONARY</> command
-     on the dictionary.  This can be a <quote>dummy</> update that doesn't
-     actually change any parameter values.
-    </para>
-   </caution>
-
-  </sect2>
-
-  <sect2 id="textsearch-synonym-dictionary">
-   <title>Synonym Dictionary</title>
-
-   <para>
-    This dictionary template is used to create dictionaries that replace a
-    word with a synonym. Phrases are not supported (use the thesaurus
-    template (<xref linkend="textsearch-thesaurus">) for that).  A synonym
-    dictionary can be used to overcome linguistic problems, for example, to
-    prevent an English stemmer dictionary from reducing the word 'Paris' to
-    'pari'.  It is enough to have a <literal>Paris paris</literal> line in the
-    synonym dictionary and put it before the <literal>english_stem</>
-    dictionary.  For example:
-
-<screen>
-SELECT * FROM ts_debug('english', 'Paris');
-   alias   |   description   | token |  dictionaries  |  dictionary  | lexemes 
------------+-----------------+-------+----------------+--------------+---------
- asciiword | Word, all ASCII | Paris | {english_stem} | english_stem | {pari}
-
-CREATE TEXT SEARCH DICTIONARY my_synonym (
-    TEMPLATE = synonym,
-    SYNONYMS = my_synonyms
-);
-
-ALTER TEXT SEARCH CONFIGURATION english
-    ALTER MAPPING FOR asciiword
-    WITH my_synonym, english_stem;
-
-SELECT * FROM ts_debug('english', 'Paris');
-   alias   |   description   | token |       dictionaries        | dictionary | lexemes 
------------+-----------------+-------+---------------------------+------------+---------
- asciiword | Word, all ASCII | Paris | {my_synonym,english_stem} | my_synonym | {paris}
-</screen>
-   </para>
-
-   <para>
-    The only parameter required by the <literal>synonym</> template is
-    <literal>SYNONYMS</>, which is the base name of its configuration file
-    &mdash; <literal>my_synonyms</> in the above example.
-    The file's full name will be
-    <filename>$SHAREDIR/tsearch_data/my_synonyms.syn</>
-    (where <literal>$SHAREDIR</> means the
-<!## PG>
-    <productname>PostgreSQL</> installation's shared-data directory).
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</> installation's shared-data directory).
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</> installation's shared-data directory).
-<!## end>
-    The file format is just one line
-    per word to be substituted, with the word followed by its synonym,
-    separated by white space.  Blank lines and trailing spaces are ignored.
-   </para>
-
-   <para>
-    The <literal>synonym</> template also has an optional parameter
-    <literal>CaseSensitive</>, which defaults to <literal>false</>.  When
-    <literal>CaseSensitive</> is <literal>false</>, words in the synonym file
-    are folded to lower case, as are input tokens.  When it is
-    <literal>true</>, words and tokens are not folded to lower case,
-    but are compared as-is.
-   </para>
-
-   <para>
-    An asterisk (<literal>*</literal>) can be placed at the end of a synonym
-    in the configuration file.  This indicates that the synonym is a prefix.
-    The asterisk is ignored when the entry is used in
-    <function>to_tsvector()</function>, but when it is used in
-    <function>to_tsquery()</function>, the result will be a query item with
-    the prefix match marker (see
-    <xref linkend="textsearch-parsing-queries">).
-    For example, suppose we have these entries in
-    <filename>$SHAREDIR/tsearch_data/synonym_sample.syn</>:
-<programlisting>
-postgres        pgsql
-postgresql      pgsql
-postgre pgsql
-gogle   googl
-indices index*
-</programlisting>
-    Then we will get these results:
-<screen>
-mydb=# CREATE TEXT SEARCH DICTIONARY syn (template=synonym, synonyms='synonym_sample');
-mydb=# SELECT ts_lexize('syn','indices');
- ts_lexize
------------
- {index}
-(1 row)
-
-mydb=# CREATE TEXT SEARCH CONFIGURATION tst (copy=simple);
-mydb=# ALTER TEXT SEARCH CONFIGURATION tst ALTER MAPPING FOR asciiword WITH syn;
-mydb=# SELECT to_tsvector('tst','indices');
- to_tsvector
--------------
- 'index':1
-(1 row)
-
-mydb=# SELECT to_tsquery('tst','indices');
- to_tsquery
-------------
- 'index':*
-(1 row)
-
-mydb=# SELECT 'indexes are very useful'::tsvector;
-            tsvector             
----------------------------------
- 'are' 'indexes' 'useful' 'very'
-(1 row)
-
-mydb=# SELECT 'indexes are very useful'::tsvector @@ to_tsquery('tst','indices');
- ?column?
-----------
- t
-(1 row)
-</screen>
-   </para>
-  </sect2>
-
-  <sect2 id="textsearch-thesaurus">
-   <title>Thesaurus Dictionary</title>
-
-   <para>
-    A thesaurus dictionary (sometimes abbreviated as <acronym>TZ</acronym>) is
-    a collection of words that includes information about the relationships
-    of words and phrases, i.e., broader terms (<acronym>BT</acronym>), narrower
-    terms (<acronym>NT</acronym>), preferred terms, non-preferred terms, related
-    terms, etc.
-   </para>
-
-   <para>
-    Basically a thesaurus dictionary replaces all non-preferred terms by one
-    preferred term and, optionally, preserves the original terms for indexing
-<!## PG>
-    as well.  <productname>PostgreSQL</>'s current implementation of the
-<!## end>
-<!## XC>
-    as well.  <productname>Postgres-XC</>'s current implementation of the
-<!## end>
-<!## XL>
-    as well.  <productname>Postgres-XL</>'s current implementation of the
-<!## end>
-    thesaurus dictionary is an extension of the synonym dictionary with added
-    <firstterm>phrase</firstterm> support.  A thesaurus dictionary requires
-    a configuration file of the following format:
-
-<programlisting>
-# this is a comment
-sample word(s) : indexed word(s)
-more sample word(s) : more indexed word(s)
-...
-</programlisting>
-
-    where  the colon (<symbol>:</symbol>) symbol acts as a delimiter between a
-    a phrase and its replacement.
-   </para>
-
-   <para>
-    A thesaurus dictionary uses a <firstterm>subdictionary</firstterm> (which
-    is specified in the dictionary's configuration) to normalize the input
-    text before checking for phrase matches. It is only possible to select one
-    subdictionary.  An error is reported if the subdictionary fails to
-    recognize a word. In that case, you should remove the use of the word or
-    teach the subdictionary about it.  You can place an asterisk
-    (<symbol>*</symbol>) at the beginning of an indexed word to skip applying
-    the subdictionary to it, but all sample words <emphasis>must</> be known
-    to the subdictionary.
-   </para>
-
-   <para>
-    The thesaurus dictionary chooses the longest match if there are multiple
-    phrases matching the input, and ties are broken by using the last
-    definition.
-   </para>
-
-   <para>
-    Specific stop words recognized by the subdictionary cannot be
-    specified;  instead use <literal>?</> to mark the location where any
-    stop word can appear.  For example, assuming that <literal>a</> and
-    <literal>the</> are stop words according to the subdictionary:
-
-<programlisting>
-? one ? two : swsw
-</programlisting>
-
-    matches <literal>a one the two</> and <literal>the one a two</>;
-    both would be replaced by <literal>swsw</>.
-   </para>
-
-   <para>
-    Since a thesaurus dictionary has the capability to recognize phrases it
-    must remember its state and interact with the parser. A thesaurus dictionary
-    uses these assignments to check if it should handle the next word or stop
-    accumulation.  The thesaurus dictionary must be configured
-    carefully. For example, if the thesaurus dictionary is assigned to handle
-    only the <literal>asciiword</literal> token, then a thesaurus dictionary
-    definition like <literal>one 7</> will not work since token type
-    <literal>uint</literal> is not assigned to the thesaurus dictionary.
-   </para>
-
-   <caution>
-    <para>
-     Thesauruses are used during indexing so any change in the thesaurus
-     dictionary's parameters <emphasis>requires</emphasis> reindexing.
-     For most other dictionary types, small changes such as adding or
-     removing stopwords does not force reindexing.
-    </para>
-   </caution>
-
-  <sect3 id="textsearch-thesaurus-config">
-   <title>Thesaurus Configuration</title>
-
-   <para>
-    To define a new thesaurus dictionary, use the <literal>thesaurus</>
-    template.  For example:
-
-<programlisting>
-CREATE TEXT SEARCH DICTIONARY thesaurus_simple (
-    TEMPLATE = thesaurus,
-    DictFile = mythesaurus,
-    Dictionary = pg_catalog.english_stem
-);
-</programlisting>
-
-    Here:
-    <itemizedlist  spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       <literal>thesaurus_simple</literal> is the new dictionary's name
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <literal>mythesaurus</literal> is the base name of the thesaurus
-       configuration file.
-       (Its full name will be <filename>$SHAREDIR/tsearch_data/mythesaurus.ths</>,
-       where <literal>$SHAREDIR</> means the installation shared-data
-       directory.)
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <literal>pg_catalog.english_stem</literal> is the subdictionary (here,
-       a Snowball English stemmer) to use for thesaurus normalization.
-       Notice that the subdictionary will have its own
-       configuration (for example, stop words), which is not shown here.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    Now it is possible to bind the thesaurus dictionary <literal>thesaurus_simple</literal>
-    to the desired token types in a configuration, for example:
-
-<programlisting>
-ALTER TEXT SEARCH CONFIGURATION russian
-    ALTER MAPPING FOR asciiword, asciihword, hword_asciipart
-    WITH thesaurus_simple;
-</programlisting>
-   </para>
-
-  </sect3>
-
-  <sect3 id="textsearch-thesaurus-examples">
-   <title>Thesaurus Example</title>
-
-   <para>
-    Consider a simple astronomical thesaurus <literal>thesaurus_astro</literal>,
-    which contains some astronomical word combinations:
-
-<programlisting>
-supernovae stars : sn
-crab nebulae : crab
-</programlisting>
-
-    Below we create a dictionary and bind some token types to
-    an astronomical thesaurus and English stemmer:
-
-<programlisting>
-CREATE TEXT SEARCH DICTIONARY thesaurus_astro (
-    TEMPLATE = thesaurus,
-    DictFile = thesaurus_astro,
-    Dictionary = english_stem
-);
-
-ALTER TEXT SEARCH CONFIGURATION russian
-    ALTER MAPPING FOR asciiword, asciihword, hword_asciipart
-    WITH thesaurus_astro, english_stem;
-</programlisting>
-
-    Now we can see how it works.
-    <function>ts_lexize</function> is not very useful for testing a thesaurus,
-    because it treats its input as a single token.  Instead we can use
-    <function>plainto_tsquery</function> and <function>to_tsvector</function>
-    which will break their input strings into multiple tokens:
-
-<screen>
-SELECT plainto_tsquery('supernova star');
- plainto_tsquery
------------------
- 'sn'
-
-SELECT to_tsvector('supernova star');
- to_tsvector
--------------
- 'sn':1
-</screen>
-
-    In principle, one can use <function>to_tsquery</function> if you quote
-    the argument:
-
-<screen>
-SELECT to_tsquery('''supernova star''');
- to_tsquery
-------------
- 'sn'
-</screen>
-
-    Notice that <literal>supernova star</literal> matches <literal>supernovae
-    stars</literal> in <literal>thesaurus_astro</literal> because we specified
-    the <literal>english_stem</literal> stemmer in the thesaurus definition.
-    The stemmer removed the <literal>e</> and <literal>s</>.
-   </para>
-
-   <para>
-    To index the original phrase as well as the substitute, just include it
-    in the right-hand part of the definition:
-
-<screen>
-supernovae stars : sn supernovae stars
-
-SELECT plainto_tsquery('supernova star');
-       plainto_tsquery
------------------------------
- 'sn' &amp; 'supernova' &amp; 'star'
-</screen>
-   </para>
-
-  </sect3>
-
-  </sect2>
-
-  <sect2 id="textsearch-ispell-dictionary">
-   <title><application>Ispell</> Dictionary</title>
-
-   <para>
-    The <application>Ispell</> dictionary template supports
-    <firstterm>morphological dictionaries</>, which can normalize many
-    different linguistic forms of a word into the same lexeme.  For example,
-    an English <application>Ispell</> dictionary can match all declensions and
-    conjugations of the search term <literal>bank</literal>, e.g.,
-    <literal>banking</>, <literal>banked</>, <literal>banks</>,
-    <literal>banks'</>, and <literal>bank's</>.
-   </para>
-
-   <para>
-<!## PG>
-    The standard <productname>PostgreSQL</productname> distribution does
-<!## end>
-<!## XC>
-    The standard <productname>Postgres-XC</productname> distribution does
-<!## end>
-<!## XL>
-    The standard <productname>Postgres-XL</productname> distribution does
-<!## end>
-    not include any <application>Ispell</> configuration files.
-    Dictionaries for a large number of languages are available from <ulink
-    url="http://ficus-www.cs.ucla.edu/geoff/ispell.html">Ispell</ulink>.
-    Also, some more modern dictionary file formats are supported &mdash; <ulink
-    url="http://en.wikipedia.org/wiki/MySpell">MySpell</ulink> (OO &lt; 2.0.1)
-    and <ulink url="http://sourceforge.net/projects/hunspell/">Hunspell</ulink>
-    (OO &gt;= 2.0.2).  A large list of dictionaries is available on the <ulink
-    url="http://wiki.services.openoffice.org/wiki/Dictionaries">OpenOffice
-    Wiki</ulink>.
-   </para>
-
-   <para>
-    To create an <application>Ispell</> dictionary, use the built-in
-    <literal>ispell</literal> template and specify several parameters:
-   </para>
-
-<programlisting>
-CREATE TEXT SEARCH DICTIONARY english_ispell (
-    TEMPLATE = ispell,
-    DictFile = english,
-    AffFile = english,
-    StopWords = english
-);
-</programlisting>
-
-   <para>
-    Here, <literal>DictFile</>, <literal>AffFile</>, and <literal>StopWords</>
-    specify the base names of the dictionary, affixes, and stop-words files.
-    The stop-words file has the same format explained above for the
-    <literal>simple</> dictionary type.  The format of the other files is
-    not specified here but is available from the above-mentioned web sites.
-   </para>
-
-   <para>
-    Ispell dictionaries usually recognize a limited set of words, so they
-    should be followed by another broader dictionary; for
-    example, a Snowball dictionary, which recognizes everything.
-   </para>
-
-   <para>
-    Ispell dictionaries support splitting compound words;
-    a useful feature.
-    Notice that the affix file should specify a special flag using the
-    <literal>compoundwords controlled</literal> statement that marks dictionary
-    words that can participate in compound formation:
-
-<programlisting>
-compoundwords  controlled z
-</programlisting>
-
-    Here are some examples for the Norwegian language:
-
-<programlisting>
-SELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');
-   {over,buljong,terning,pakk,mester,assistent}
-SELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');
-   {sjokoladefabrikk,sjokolade,fabrikk}
-</programlisting>
-   </para>
-
-   <note>
-    <para>
-     <application>MySpell</> does not support compound words.
-     <application>Hunspell</> has sophisticated support for compound words. At
-<!## PG>
-     present, <productname>PostgreSQL</productname> implements only the basic
-<!## end>
-<!## XC>
-     present, <productname>Postgres-XC</productname> implements only the basic
-<!## end>
-<!## XL>
-     present, <productname>Postgres-XL</productname> implements only the basic
-<!## end>
-     compound word operations of Hunspell.
-    </para>
-   </note>
-
-  </sect2>
-
-  <sect2 id="textsearch-snowball-dictionary">
-   <title><application>Snowball</> Dictionary</title>
-
-   <para>
-    The <application>Snowball</> dictionary template is based on a project
-    by Martin Porter, inventor of the popular Porter's stemming algorithm
-    for the English language.  Snowball now provides stemming algorithms for
-    many languages (see the <ulink url="http://snowball.tartarus.org">Snowball
-    site</ulink> for more information).  Each algorithm understands how to
-    reduce common variant forms of words to a base, or stem, spelling within
-    its language.  A Snowball dictionary requires a <literal>language</>
-    parameter to identify which stemmer to use, and optionally can specify a
-    <literal>stopword</> file name that gives a list of words to eliminate.
-<!## PG>
-    (<productname>PostgreSQL</productname>'s standard stopword lists are also
-<!## end>
-<!## XC>
-    (<productname>Postgres-XC</productname>'s standard stopword lists are also
-<!## end>
-<!## XL>
-    (<productname>Postgres-XL</productname>'s standard stopword lists are also
-<!## end>
-    provided by the Snowball project.)
-    For example, there is a built-in definition equivalent to
-
-<programlisting>
-CREATE TEXT SEARCH DICTIONARY english_stem (
-    TEMPLATE = snowball,
-    Language = english,
-    StopWords = english
-);
-</programlisting>
-
-    The stopword file format is the same as already explained.
-   </para>
-
-   <para>
-    A <application>Snowball</> dictionary recognizes everything, whether
-    or not it is able to simplify the word, so it should be placed
-    at the end of the dictionary list. It is useless to have it
-    before any other dictionary because a token will never pass through it to
-    the next dictionary.
-   </para>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="textsearch-configuration">
-  <title>Configuration Example</title>
-
-   <para>
-    A text search configuration specifies all options necessary to transform a
-    document into a <type>tsvector</type>: the parser to use to break text
-    into tokens, and the dictionaries to use to transform each token into a
-    lexeme.  Every call of
-    <function>to_tsvector</function> or <function>to_tsquery</function>
-    needs a text search configuration to perform its processing.
-    The configuration parameter
-    <xref linkend="guc-default-text-search-config">
-    specifies the name of the default configuration, which is the
-    one used by text search functions if an explicit configuration
-    parameter is omitted.
-    It can be set in <filename>postgresql.conf</filename>, or set for an
-    individual session using the <command>SET</> command.
-   </para>
-
-   <para>
-    Several predefined text search configurations are available, and
-    you can create custom configurations easily.  To facilitate management
-    of text search objects, a set of <acronym>SQL</acronym> commands
-    is available, and there are several <application>psql</application> commands that display information
-    about text search objects (<xref linkend="textsearch-psql">).
-   </para>
-
-   <para>
-    As an example we will create a configuration
-    <literal>pg</literal>, starting by duplicating the built-in
-    <literal>english</> configuration:
-
-<programlisting>
-CREATE TEXT SEARCH CONFIGURATION public.pg ( COPY = pg_catalog.english );
-</programlisting>
-   </para>
-
-   <para>
-<!## PG>
-    We will use a PostgreSQL-specific synonym list
-<!## end>
-<!## XC>
-    We will use a Postgres-XC-specific synonym list
-<!## end>
-<!## XL>
-    We will use a Postgres-XL-specific synonym list
-<!## end>
-    and store it in <filename>$SHAREDIR/tsearch_data/pg_dict.syn</filename>.
-    The file contents look like:
-
-<programlisting>
-postgres    pg
-pgsql       pg
-postgresql  pg
-</programlisting>
-
-    We define the synonym dictionary like this:
-
-<programlisting>
-CREATE TEXT SEARCH DICTIONARY pg_dict (
-    TEMPLATE = synonym,
-    SYNONYMS = pg_dict
-);
-</programlisting>
-
-    Next we register the <productname>Ispell</> dictionary
-    <literal>english_ispell</literal>, which has its own configuration files:
-
-<programlisting>
-CREATE TEXT SEARCH DICTIONARY english_ispell (
-    TEMPLATE = ispell,
-    DictFile = english,
-    AffFile = english,
-    StopWords = english
-);
-</programlisting>
-
-    Now we can set up the mappings for words in configuration
-    <literal>pg</>:
-
-<programlisting>
-ALTER TEXT SEARCH CONFIGURATION pg
-    ALTER MAPPING FOR asciiword, asciihword, hword_asciipart,
-                      word, hword, hword_part
-    WITH pg_dict, english_ispell, english_stem;
-</programlisting>
-
-    We choose not to index or search some token types that the built-in
-    configuration does handle:
-
-<programlisting>
-ALTER TEXT SEARCH CONFIGURATION pg
-    DROP MAPPING FOR email, url, url_path, sfloat, float;
-</programlisting>
-   </para>
-
-   <para>
-    Now we can test our configuration:
-
-<programlisting>
-SELECT * FROM ts_debug('public.pg', '
-<!## PG>
-PostgreSQL, the highly scalable, SQL compliant, open source object-relational
-<!## end>
-<!## XC>
-Postgres-XC, the highly scalable, SQL compliant, open source object-relational
-<!## end>
-<!## XL>
-Postgres-XL, the highly scalable, SQL compliant, open source object-relational
-<!## end>
-database management system, is now undergoing beta testing of the next
-version of our software.
-');
-</programlisting>
-   </para>
-
-   <para>
-    The next step is to set the session to use the new configuration, which was
-    created in the <literal>public</> schema:
-
-<screen>
-=&gt; \dF
-   List of text search configurations
- Schema  | Name | Description
----------+------+-------------
- public  | pg   |
-
-SET default_text_search_config = 'public.pg';
-SET
-
-SHOW default_text_search_config;
- default_text_search_config
-----------------------------
- public.pg
-</screen>
-  </para>
-
- </sect1>
-
- <sect1 id="textsearch-debugging">
-  <title>Testing and Debugging Text Search</title>
-
-  <para>
-   The behavior of a custom text search configuration can easily become
-   confusing.  The functions described
-   in this section are useful for testing text search objects.  You can
-   test a complete configuration, or test parsers and dictionaries separately.
-  </para>
-
-  <sect2 id="textsearch-configuration-testing">
-   <title>Configuration Testing</title>
-
-  <para>
-   The function <function>ts_debug</function> allows easy testing of a
-   text search configuration.
-  </para>
-
-  <indexterm>
-   <primary>ts_debug</primary>
-  </indexterm>
-
-<synopsis>
-ts_debug(<optional> <replaceable class="PARAMETER">config</replaceable> <type>regconfig</>, </optional> <replaceable class="PARAMETER">document</replaceable> <type>text</>,
-         OUT <replaceable class="PARAMETER">alias</> <type>text</>,
-         OUT <replaceable class="PARAMETER">description</> <type>text</>,
-         OUT <replaceable class="PARAMETER">token</> <type>text</>,
-         OUT <replaceable class="PARAMETER">dictionaries</> <type>regdictionary[]</>,
-         OUT <replaceable class="PARAMETER">dictionary</> <type>regdictionary</>,
-         OUT <replaceable class="PARAMETER">lexemes</> <type>text[]</>)
-         returns setof record
-</synopsis>
-
-  <para>
-   <function>ts_debug</> displays information about every token of
-   <replaceable class="PARAMETER">document</replaceable> as produced by the
-   parser and processed by the configured dictionaries.  It uses the
-   configuration specified by <replaceable
-   class="PARAMETER">config</replaceable>,
-   or <varname>default_text_search_config</varname> if that argument is
-   omitted.
-  </para>
-
-  <para>
-   <function>ts_debug</> returns one row for each token identified in the text
-   by the parser.  The columns returned are
-
-    <itemizedlist  spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       <replaceable>alias</> <type>text</> &mdash; short name of the token type
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <replaceable>description</> <type>text</> &mdash; description of the
-       token type
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <replaceable>token</> <type>text</> &mdash; text of the token
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <replaceable>dictionaries</> <type>regdictionary[]</> &mdash; the
-       dictionaries selected by the configuration for this token type
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <replaceable>dictionary</> <type>regdictionary</> &mdash; the dictionary
-       that recognized the token, or <literal>NULL</> if none did
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <replaceable>lexemes</> <type>text[]</> &mdash; the lexeme(s) produced
-       by the dictionary that recognized the token, or <literal>NULL</> if
-       none did; an empty array (<literal>{}</>) means it was recognized as a
-       stop word
-      </para>
-     </listitem>
-    </itemizedlist>
-  </para>
-
-  <para>
-   Here is a simple example:
-
-<screen>
-SELECT * FROM ts_debug('english','a fat  cat sat on a mat - it ate a fat rats');
-   alias   |   description   | token |  dictionaries  |  dictionary  | lexemes 
------------+-----------------+-------+----------------+--------------+---------
- asciiword | Word, all ASCII | a     | {english_stem} | english_stem | {}
- blank     | Space symbols   |       | {}             |              | 
- asciiword | Word, all ASCII | fat   | {english_stem} | english_stem | {fat}
- blank     | Space symbols   |       | {}             |              | 
- asciiword | Word, all ASCII | cat   | {english_stem} | english_stem | {cat}
- blank     | Space symbols   |       | {}             |              | 
- asciiword | Word, all ASCII | sat   | {english_stem} | english_stem | {sat}
- blank     | Space symbols   |       | {}             |              | 
- asciiword | Word, all ASCII | on    | {english_stem} | english_stem | {}
- blank     | Space symbols   |       | {}             |              | 
- asciiword | Word, all ASCII | a     | {english_stem} | english_stem | {}
- blank     | Space symbols   |       | {}             |              | 
- asciiword | Word, all ASCII | mat   | {english_stem} | english_stem | {mat}
- blank     | Space symbols   |       | {}             |              | 
- blank     | Space symbols   | -     | {}             |              | 
- asciiword | Word, all ASCII | it    | {english_stem} | english_stem | {}
- blank     | Space symbols   |       | {}             |              | 
- asciiword | Word, all ASCII | ate   | {english_stem} | english_stem | {ate}
- blank     | Space symbols   |       | {}             |              | 
- asciiword | Word, all ASCII | a     | {english_stem} | english_stem | {}
- blank     | Space symbols   |       | {}             |              | 
- asciiword | Word, all ASCII | fat   | {english_stem} | english_stem | {fat}
- blank     | Space symbols   |       | {}             |              | 
- asciiword | Word, all ASCII | rats  | {english_stem} | english_stem | {rat}
-</screen>
-  </para>
-
-  <para>
-   For a more extensive demonstration, we
-   first create a <literal>public.english</literal> configuration and
-   Ispell dictionary for the English language:
-  </para>
-
-<programlisting>
-CREATE TEXT SEARCH CONFIGURATION public.english ( COPY = pg_catalog.english );
-
-CREATE TEXT SEARCH DICTIONARY english_ispell (
-    TEMPLATE = ispell,
-    DictFile = english,
-    AffFile = english,
-    StopWords = english
-);
-
-ALTER TEXT SEARCH CONFIGURATION public.english
-   ALTER MAPPING FOR asciiword WITH english_ispell, english_stem;
-</programlisting>
-
-<screen>
-SELECT * FROM ts_debug('public.english','The Brightest supernovaes');
-   alias   |   description   |    token    |         dictionaries          |   dictionary   |   lexemes   
------------+-----------------+-------------+-------------------------------+----------------+-------------
- asciiword | Word, all ASCII | The         | {english_ispell,english_stem} | english_ispell | {}
- blank     | Space symbols   |             | {}                            |                | 
- asciiword | Word, all ASCII | Brightest   | {english_ispell,english_stem} | english_ispell | {bright}
- blank     | Space symbols   |             | {}                            |                | 
- asciiword | Word, all ASCII | supernovaes | {english_ispell,english_stem} | english_stem   | {supernova}
-</screen>
-
-  <para>
-   In this example, the word <literal>Brightest</> was recognized by the
-   parser as an <literal>ASCII word</literal> (alias <literal>asciiword</literal>).
-   For this token type the dictionary list is
-   <literal>english_ispell</> and
-   <literal>english_stem</literal>. The word was recognized by
-   <literal>english_ispell</literal>, which reduced it to the noun
-   <literal>bright</literal>. The word <literal>supernovaes</literal> is
-   unknown to the <literal>english_ispell</literal> dictionary so it
-   was passed to the next dictionary, and, fortunately, was recognized (in
-   fact, <literal>english_stem</literal> is a Snowball dictionary which
-   recognizes everything; that is why it was placed at the end of the
-   dictionary list).
-  </para>
-
-  <para>
-   The word <literal>The</literal> was recognized by the
-   <literal>english_ispell</literal> dictionary as a stop word (<xref
-   linkend="textsearch-stopwords">) and will not be indexed.
-   The spaces are discarded too, since the configuration provides no
-   dictionaries at all for them.
-  </para>
-
-  <para>
-   You can reduce the width of the output by explicitly specifying which columns
-   you want to see:
-
-<screen>
-SELECT alias, token, dictionary, lexemes
-FROM ts_debug('public.english','The Brightest supernovaes');
-   alias   |    token    |   dictionary   |   lexemes   
------------+-------------+----------------+-------------
- asciiword | The         | english_ispell | {}
- blank     |             |                | 
- asciiword | Brightest   | english_ispell | {bright}
- blank     |             |                | 
- asciiword | supernovaes | english_stem   | {supernova}
-</screen>
-  </para>
-
-  </sect2>
-
-  <sect2 id="textsearch-parser-testing">
-   <title>Parser Testing</title>
-
-  <para>
-   The following functions allow direct testing of a text search parser.
-  </para>
-
-  <indexterm>
-   <primary>ts_parse</primary>
-  </indexterm>
-
-<synopsis>
-ts_parse(<replaceable class="PARAMETER">parser_name</replaceable> <type>text</>, <replaceable class="PARAMETER">document</replaceable> <type>text</>,
-         OUT <replaceable class="PARAMETER">tokid</> <type>integer</>, OUT <replaceable class="PARAMETER">token</> <type>text</>) returns <type>setof record</>
-ts_parse(<replaceable class="PARAMETER">parser_oid</replaceable> <type>oid</>, <replaceable class="PARAMETER">document</replaceable> <type>text</>,
-         OUT <replaceable class="PARAMETER">tokid</> <type>integer</>, OUT <replaceable class="PARAMETER">token</> <type>text</>) returns <type>setof record</>
-</synopsis>
-
-  <para>
-   <function>ts_parse</> parses the given <replaceable>document</replaceable>
-   and returns a series of records, one for each token produced by
-   parsing. Each record includes a <varname>tokid</varname> showing the
-   assigned token type and a <varname>token</varname> which is the text of the
-   token.  For example:
-
-<screen>
-SELECT * FROM ts_parse('default', '123 - a number');
- tokid | token
--------+--------
-    22 | 123
-    12 |
-    12 | -
-     1 | a
-    12 |
-     1 | number
-</screen>
-  </para>
-
-  <indexterm>
-   <primary>ts_token_type</primary>
-  </indexterm>
-
-<synopsis>
-ts_token_type(<replaceable class="PARAMETER">parser_name</> <type>text</>, OUT <replaceable class="PARAMETER">tokid</> <type>integer</>,
-              OUT <replaceable class="PARAMETER">alias</> <type>text</>, OUT <replaceable class="PARAMETER">description</> <type>text</>) returns <type>setof record</>
-ts_token_type(<replaceable class="PARAMETER">parser_oid</> <type>oid</>, OUT <replaceable class="PARAMETER">tokid</> <type>integer</>,
-              OUT <replaceable class="PARAMETER">alias</> <type>text</>, OUT <replaceable class="PARAMETER">description</> <type>text</>) returns <type>setof record</>
-</synopsis>
-
-  <para>
-   <function>ts_token_type</> returns a table which describes each type of
-   token the specified parser can recognize.  For each token type, the table
-   gives the integer <varname>tokid</varname> that the parser uses to label a
-   token of that type, the <varname>alias</varname> that names the token type
-   in configuration commands, and a short <varname>description</varname>.  For
-   example:
-
-<screen>
-SELECT * FROM ts_token_type('default');
- tokid |      alias      |               description                
--------+-----------------+------------------------------------------
-     1 | asciiword       | Word, all ASCII
-     2 | word            | Word, all letters
-     3 | numword         | Word, letters and digits
-     4 | email           | Email address
-     5 | url             | URL
-     6 | host            | Host
-     7 | sfloat          | Scientific notation
-     8 | version         | Version number
-     9 | hword_numpart   | Hyphenated word part, letters and digits
-    10 | hword_part      | Hyphenated word part, all letters
-    11 | hword_asciipart | Hyphenated word part, all ASCII
-    12 | blank           | Space symbols
-    13 | tag             | XML tag
-    14 | protocol        | Protocol head
-    15 | numhword        | Hyphenated word, letters and digits
-    16 | asciihword      | Hyphenated word, all ASCII
-    17 | hword           | Hyphenated word, all letters
-    18 | url_path        | URL path
-    19 | file            | File or path name
-    20 | float           | Decimal notation
-    21 | int             | Signed integer
-    22 | uint            | Unsigned integer
-    23 | entity          | XML entity
-</screen>
-   </para>
-
-  </sect2>
-
-  <sect2 id="textsearch-dictionary-testing">
-   <title>Dictionary Testing</title>
-
-   <para>
-    The <function>ts_lexize</> function facilitates dictionary testing.
-   </para>
-
-   <indexterm>
-    <primary>ts_lexize</primary>
-   </indexterm>
-
-<synopsis>
-ts_lexize(<replaceable class="PARAMETER">dict</replaceable> <type>regdictionary</>, <replaceable class="PARAMETER">token</replaceable> <type>text</>) returns <type>text[]</>
-</synopsis>
-
-   <para>
-    <function>ts_lexize</> returns an array of lexemes if the input
-    <replaceable>token</replaceable> is known to the dictionary,
-    or an empty array if the token
-    is known to the dictionary but it is a stop word, or
-    <literal>NULL</literal> if it is an unknown word.
-   </para>
-
-   <para>
-    Examples:
-
-<screen>
-SELECT ts_lexize('english_stem', 'stars');
- ts_lexize
------------
- {star}
-
-SELECT ts_lexize('english_stem', 'a');
- ts_lexize
------------
- {}
-</screen>
-   </para>
-
-   <note>
-    <para>
-     The <function>ts_lexize</function> function expects a single
-     <emphasis>token</emphasis>, not text. Here is a case
-     where this can be confusing:
-
-<screen>
-SELECT ts_lexize('thesaurus_astro','supernovae stars') is null;
- ?column?
-----------
- t
-</screen>
-
-     The thesaurus dictionary <literal>thesaurus_astro</literal> does know the
-     phrase <literal>supernovae stars</literal>, but <function>ts_lexize</>
-     fails since it does not parse the input text but treats it as a single
-     token. Use <function>plainto_tsquery</> or <function>to_tsvector</> to
-     test thesaurus dictionaries, for example:
-
-<screen>
-SELECT plainto_tsquery('supernovae stars');
- plainto_tsquery
------------------
- 'sn'
-</screen>
-    </para>
-   </note>
-
-  </sect2>
-
- </sect1>
-
- <sect1 id="textsearch-indexes">
-  <title>GiST and GIN Index Types</title>
-
-  <indexterm zone="textsearch-indexes">
-   <primary>text search</primary>
-   <secondary>indexes</secondary>
-  </indexterm>
-
-  <para>
-   There are two kinds of indexes that can be used to speed up full text
-   searches.
-   Note that indexes are not mandatory for full text searching, but in
-   cases where a column is searched on a regular basis, an index is
-   usually desirable.
-
-   <variablelist>
-
-    <varlistentry>
-
-     <indexterm zone="textsearch-indexes">
-      <primary>index</primary>
-      <secondary>GiST</secondary>
-      <tertiary>text search</tertiary>
-     </indexterm>
-
-     <term>
-<synopsis>
-CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable> USING gist(<replaceable>column</replaceable>);
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       Creates a GiST (Generalized Search Tree)-based index.
-       The <replaceable>column</replaceable> can be of <type>tsvector</> or
-       <type>tsquery</> type.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-
-     <indexterm zone="textsearch-indexes">
-      <primary>index</primary>
-      <secondary>GIN</secondary>
-      <tertiary>text search</tertiary>
-     </indexterm>
-
-     <term>
-<synopsis>
-CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable> USING gin(<replaceable>column</replaceable>);
-</synopsis>
-     </term>
-
-     <listitem>
-      <para>
-       Creates a GIN (Generalized Inverted Index)-based index.
-       The <replaceable>column</replaceable> must be of <type>tsvector</> type.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
-
-  <para>
-   There are substantial performance differences between the two index types,
-   so it is important to understand their characteristics.
-  </para>
-
-  <para>
-   A GiST index is <firstterm>lossy</firstterm>, meaning that the index
-   may produce false matches, and it is necessary
-   to check the actual table row to eliminate such false matches.
-<!## PG>
-   (<productname>PostgreSQL</productname> does this automatically when needed.)
-<!## end>
-<!## XC>
-   (<productname>Postgres-XC</productname> does this automatically when needed.)
-<!## end>
-<!## XL>
-   (<productname>Postgres-XL</productname> does this automatically when needed.)
-<!## end>
-   GiST indexes are lossy because each document is represented in the
-   index by a fixed-length signature. The signature is generated by hashing
-   each word into a single bit in an n-bit string, with all these bits OR-ed
-   together to produce an n-bit document signature.  When two words hash to
-   the same bit position there will be a false match.  If all words in
-   the query have matches (real or false) then the table row must be
-   retrieved to see if the match is correct.
-  </para>
-
-  <para>
-   Lossiness causes performance degradation due to unnecessary fetches of table
-   records that turn out to be false matches.  Since random access to table
-   records is slow, this limits the usefulness of GiST indexes.  The
-   likelihood of false matches depends on several factors, in particular the
-   number of unique words, so using dictionaries to reduce this number is
-   recommended.
-  </para>
-
-  <para>
-   GIN indexes are not lossy for standard queries, but their performance
-   depends logarithmically on the number of unique words.
-   (However, GIN indexes store only the words (lexemes) of <type>tsvector</>
-   values, and not their weight labels.  Thus a table row recheck is needed
-   when using a query that involves weights.)
-  </para>
-
-  <para>
-   In choosing which index type to use, GiST or GIN, consider these
-   performance differences:
-
-   <itemizedlist  spacing="compact" mark="bullet">
-    <listitem>
-     <para>
-      GIN index lookups are about three times faster than GiST
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      GIN indexes take about three times longer to build than GiST
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      GIN indexes are moderately slower to update than GiST indexes, but
-      about 10 times slower if fast-update support was disabled
-      (see <xref linkend="gin-fast-update"> for details)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      GIN indexes are two-to-three times larger than GiST indexes
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   As a rule of thumb, <acronym>GIN</acronym> indexes are best for static data
-   because lookups are faster.  For dynamic data, GiST indexes are
-   faster to update.  Specifically, <acronym>GiST</acronym> indexes are very
-   good for dynamic data and fast if the number of unique words (lexemes) is
-   under 100,000, while <acronym>GIN</acronym> indexes will handle 100,000+
-   lexemes better but are slower to update.
-  </para>
-
-  <para>
-   Note that <acronym>GIN</acronym> index build time can often be improved
-   by increasing <xref linkend="guc-maintenance-work-mem">, while
-   <acronym>GiST</acronym> index build time is not sensitive to that
-   parameter.
-  </para>
-
-  <para>
-   Partitioning of big collections and the proper use of GiST and GIN indexes
-   allows the implementation of very fast searches with online update.
-   Partitioning can be done at the database level using table inheritance,
-   or by distributing documents over
-   servers and collecting search results using the <xref linkend="dblink">
-   module. The latter is possible because ranking functions use
-   only local information.
-  </para>
-
- </sect1>
-
- <sect1 id="textsearch-psql">
-  <title><application>psql</> Support</title>
-
-  <para>
-   Information about text search configuration objects can be obtained
-   in <application>psql</application> using a set of commands:
-<synopsis>
-\dF{d,p,t}<optional>+</optional> <optional>PATTERN</optional>
-</synopsis>
-   An optional <literal>+</literal> produces more details.
-  </para>
-
-  <para>
-   The optional parameter <literal>PATTERN</literal> can be the name of
-   a text search object, optionally schema-qualified.  If
-   <literal>PATTERN</literal> is omitted then information about all
-   visible objects will be displayed.  <literal>PATTERN</literal> can be a
-   regular expression and can provide <emphasis>separate</emphasis> patterns
-   for the schema and object names.  The following examples illustrate this:
-
-<screen>
-=&gt; \dF *fulltext*
-       List of text search configurations
- Schema |  Name        | Description
---------+--------------+-------------
- public | fulltext_cfg |
-</screen>
-
-<screen>
-=&gt; \dF *.fulltext*
-       List of text search configurations
- Schema   |  Name        | Description
-----------+----------------------------
- fulltext | fulltext_cfg |
- public   | fulltext_cfg |
-</screen>
-
-   The available commands are:
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term><synopsis>\dF<optional>+</optional> <optional>PATTERN</optional></synopsis></term>
-    <listitem>
-     <para>
-      List text search configurations (add <literal>+</> for more detail).
-<screen>
-=&gt; \dF russian
-            List of text search configurations
-   Schema   |  Name   |            Description             
-------------+---------+------------------------------------
- pg_catalog | russian | configuration for russian language
-
-=&gt; \dF+ russian
-Text search configuration "pg_catalog.russian"
-Parser: "pg_catalog.default"
-      Token      | Dictionaries 
------------------+--------------
- asciihword      | english_stem
- asciiword       | english_stem
- email           | simple
- file            | simple
- float           | simple
- host            | simple
- hword           | russian_stem
- hword_asciipart | english_stem
- hword_numpart   | simple
- hword_part      | russian_stem
- int             | simple
- numhword        | simple
- numword         | simple
- sfloat          | simple
- uint            | simple
- url             | simple
- url_path        | simple
- version         | simple
- word            | russian_stem
-</screen>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><synopsis>\dFd<optional>+</optional> <optional>PATTERN</optional></synopsis></term>
-    <listitem>
-     <para>
-      List text search dictionaries (add <literal>+</> for more detail).
-<screen>
-=&gt; \dFd
-                            List of text search dictionaries
-   Schema   |      Name       |                        Description                        
-------------+-----------------+-----------------------------------------------------------
- pg_catalog | danish_stem     | snowball stemmer for danish language
- pg_catalog | dutch_stem      | snowball stemmer for dutch language
- pg_catalog | english_stem    | snowball stemmer for english language
- pg_catalog | finnish_stem    | snowball stemmer for finnish language
- pg_catalog | french_stem     | snowball stemmer for french language
- pg_catalog | german_stem     | snowball stemmer for german language
- pg_catalog | hungarian_stem  | snowball stemmer for hungarian language
- pg_catalog | italian_stem    | snowball stemmer for italian language
- pg_catalog | norwegian_stem  | snowball stemmer for norwegian language
- pg_catalog | portuguese_stem | snowball stemmer for portuguese language
- pg_catalog | romanian_stem   | snowball stemmer for romanian language
- pg_catalog | russian_stem    | snowball stemmer for russian language
- pg_catalog | simple          | simple dictionary: just lower case and check for stopword
- pg_catalog | spanish_stem    | snowball stemmer for spanish language
- pg_catalog | swedish_stem    | snowball stemmer for swedish language
- pg_catalog | turkish_stem    | snowball stemmer for turkish language
-</screen>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-   <term><synopsis>\dFp<optional>+</optional> <optional>PATTERN</optional></synopsis></term>
-    <listitem>
-     <para>
-      List text search parsers (add <literal>+</> for more detail).
-<screen>
-=&gt; \dFp
-        List of text search parsers
-   Schema   |  Name   |     Description     
-------------+---------+---------------------
- pg_catalog | default | default word parser
-=&gt; \dFp+
-    Text search parser "pg_catalog.default"
-     Method      |    Function    | Description 
------------------+----------------+-------------
- Start parse     | prsd_start     | 
- Get next token  | prsd_nexttoken | 
- End parse       | prsd_end       | 
- Get headline    | prsd_headline  | 
- Get token types | prsd_lextype   | 
-
-        Token types for parser "pg_catalog.default"
-   Token name    |               Description                
------------------+------------------------------------------
- asciihword      | Hyphenated word, all ASCII
- asciiword       | Word, all ASCII
- blank           | Space symbols
- email           | Email address
- entity          | XML entity
- file            | File or path name
- float           | Decimal notation
- host            | Host
- hword           | Hyphenated word, all letters
- hword_asciipart | Hyphenated word part, all ASCII
- hword_numpart   | Hyphenated word part, letters and digits
- hword_part      | Hyphenated word part, all letters
- int             | Signed integer
- numhword        | Hyphenated word, letters and digits
- numword         | Word, letters and digits
- protocol        | Protocol head
- sfloat          | Scientific notation
- tag             | XML tag
- uint            | Unsigned integer
- url             | URL
- url_path        | URL path
- version         | Version number
- word            | Word, all letters
-(23 rows)
-</screen>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-   <term><synopsis>\dFt<optional>+</optional> <optional>PATTERN</optional></synopsis></term>
-    <listitem>
-     <para>
-      List text search templates (add <literal>+</> for more detail).
-<screen>
-=&gt; \dFt
-                           List of text search templates
-   Schema   |   Name    |                        Description                        
-------------+-----------+-----------------------------------------------------------
- pg_catalog | ispell    | ispell dictionary
- pg_catalog | simple    | simple dictionary: just lower case and check for stopword
- pg_catalog | snowball  | snowball stemmer
- pg_catalog | synonym   | synonym dictionary: replace word by its synonym
- pg_catalog | thesaurus | thesaurus dictionary: phrase by phrase substitution
-</screen>
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
- </sect1>
-
- <sect1 id="textsearch-limitations">
-  <title>Limitations</title>
-
-  <para>
-<!## PG>
-   The current limitations of <productname>PostgreSQL</productname>'s
-<!## end>
-<!## XC>
-   The current limitations of <productname>Postgres-XC</productname>'s
-<!## end>
-<!## XL>
-   The current limitations of <productname>Postgres-XL</productname>'s
-<!## end>
-   text search features are:
-   <itemizedlist  spacing="compact" mark="bullet">
-    <listitem>
-     <para>The length of each lexeme must be less than 2K bytes</para>
-    </listitem>
-    <listitem>
-     <para>The length of a <type>tsvector</type> (lexemes + positions) must be
-     less than 1 megabyte</para>
-    </listitem>
-    <listitem>
-     <!-- TODO: number of lexemes in what?  This is unclear -->
-     <para>The number of lexemes must be less than
-     2<superscript>64</superscript></para>
-    </listitem>
-    <listitem>
-     <para>Position values in <type>tsvector</> must be greater than 0 and
-     no more than 16,383</para>
-    </listitem>
-    <listitem>
-     <para>No more than 256 positions per lexeme</para>
-    </listitem>
-    <listitem>
-     <para>The number of nodes (lexemes + operators) in a <type>tsquery</type>
-     must be less than 32,768</para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   For comparison, the <productname>PostgreSQL</productname> 8.1 documentation
-   contained 10,441 unique words, a total of 335,420 words, and the most
-   frequent word <quote>postgresql</> was mentioned 6,127 times in 655
-   documents.
-  </para>
-
-   <!-- TODO we need to put a date on these numbers? -->
-  <para>
-<!## PG>
-   Another example &mdash; the <productname>PostgreSQL</productname> mailing
-<!## end>
-<!## XC>
-   Another example &mdash; the <productname>Postgres-XC</productname> mailing
-<!## end>
-<!## XL>
-   Another example &mdash; the <productname>Postgres-XL</productname> mailing
-<!## end>
-   list archives contained 910,989 unique words with 57,491,343 lexemes in
-   461,020 messages.
-  </para>
-
- </sect1>
-
- <sect1 id="textsearch-migration">
-  <title>Migration from Pre-8.3 Text Search</title>
-
-  <para>
-   Applications that use the <xref linkend="tsearch2">
-   module for text searching will need some adjustments to work
-   with the
-   built-in features:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Some functions have been renamed or had small adjustments in their
-     argument lists, and all of them are now in the <literal>pg_catalog</>
-     schema, whereas in a previous installation they would have been in
-     <literal>public</> or another non-system schema.  There is a new
-     version of <application>tsearch2</>
-     that provides a compatibility layer to solve most problems in this
-     area.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The old <application>tsearch2</> functions and other objects
-     <emphasis>must</> be suppressed when loading <application>pg_dump</>
-     output from a pre-8.3 database.  While many of them won't load anyway,
-     a few will and then cause problems.  One simple way to deal with this
-     is to load the new <application>tsearch2</> module before restoring
-     the dump; then it will block the old objects from being loaded.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Text search configuration setup is completely different now.
-     Instead of manually inserting rows into configuration tables,
-     search is configured through the specialized SQL commands shown
-     earlier in this chapter.  There is no automated
-     support for converting an existing custom configuration for 8.3;
-     you're on your own here.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Most types of dictionaries rely on some outside-the-database
-     configuration files.  These are largely compatible with pre-8.3
-     usage, but note the following differences:
-
-     <itemizedlist  spacing="compact" mark="bullet">
-      <listitem>
-       <para>
-        Configuration files now must be placed in a single specified
-        directory (<filename>$SHAREDIR/tsearch_data</>), and must have
-        a specific extension depending on the type of file, as noted
-        previously in the descriptions of the various dictionary types.
-        This restriction was added to forestall security problems.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Configuration files must be encoded in UTF-8 encoding,
-        regardless of what database encoding is used.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        In thesaurus configuration files, stop words must be marked with
-        <literal>?</>.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </listitem>
-
-  </itemizedlist>
-
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/trigger.sgmlin b/doc-xc/src/sgml/trigger.sgmlin
deleted file mode 100644
index b20b8fb6be..0000000000
--- a/doc-xc/src/sgml/trigger.sgmlin
+++ /dev/null
@@ -1,915 +0,0 @@
-<!-- doc/src/sgml/trigger.sgml -->
-
- <chapter id="triggers">
-  <title>Triggers</title>
-
-  <indexterm zone="triggers">
-   <primary>trigger</primary>
-  </indexterm>
-
-<!## XC>
-&xconly;
-  <para>
-   The trigger will be supported in the future.  The document will be supported then.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Triggers are not currently supported, but will be in the future. 
-  </para>
-<!## end>
-
-<!## PG>
-  <para>
-   This chapter provides general information about writing trigger functions.
-   Trigger functions can be written in most of the available procedural
-   languages, including
-   <application>PL/pgSQL</application> (<xref linkend="plpgsql">),
-   <application>PL/Tcl</application> (<xref linkend="pltcl">),
-   <application>PL/Perl</application> (<xref linkend="plperl">), and
-   <application>PL/Python</application> (<xref linkend="plpython">).
-   After reading this chapter, you should consult the chapter for
-   your favorite procedural language to find out the language-specific
-   details of writing a trigger in it.
-  </para>
-
-  <para>
-   It is also possible to write a trigger function in C, although
-   most people find it easier to use one of the procedural languages.
-   It is not currently possible to write a trigger function in the
-   plain SQL function language.
-  </para>
-<!## end>
-
-  <sect1 id="trigger-definition">
-   <title>Overview of Trigger Behavior</title>
-
-<!## XC>
-&xconly;
-  <para>
-   The trigger will be supported in the future.  The document will be supported then.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Triggers are not currently supported, but will be in the future. 
-  </para>
-<!## end>
-<!## PG>
-   <para>
-    A trigger is a specification that the database should automatically
-    execute a particular function whenever a certain type of operation is
-    performed.  Triggers can be attached to both tables and views.
-  </para>
-
-  <para>
-    On tables, triggers can be defined to execute either before or after any
-    <command>INSERT</command>, <command>UPDATE</command>, or
-    <command>DELETE</command> operation, either once per modified row,
-    or once per <acronym>SQL</acronym> statement.
-    <command>UPDATE</command> triggers can moreover be set to fire only if
-    certain columns are mentioned in the <literal>SET</literal> clause of the
-    <command>UPDATE</command> statement.
-    Triggers can also fire for <command>TRUNCATE</command> statements.
-    If a trigger event occurs, the trigger's function is called at the
-    appropriate time to handle the event.
-   </para>
-
-   <para>
-    On views, triggers can be defined to execute instead of
-    <command>INSERT</command>, <command>UPDATE</command>, or
-    <command>DELETE</command> operations.  <literal>INSTEAD OF</> triggers
-    are fired once for each row that needs to be modified in the view.
-    It is the responsibility of the
-    trigger's function to perform the necessary modifications to the
-    underlying base tables and, where appropriate, return the modified
-    row as it will appear in the view.  Triggers on views can also be defined
-    to execute once per <acronym>SQL</acronym> statement, before or after
-    <command>INSERT</command>, <command>UPDATE</command>, or
-    <command>DELETE</command> operations.
-   </para>
-
-   <para>
-    The trigger function must be defined before the trigger itself can be
-    created.  The trigger function must be declared as a
-    function taking no arguments and returning type <literal>trigger</>.
-    (The trigger function receives its input through a specially-passed
-    <structname>TriggerData</> structure, not in the form of ordinary function
-    arguments.)
-   </para>
-
-   <para>
-    Once a suitable trigger function has been created, the trigger is
-    established with
-    <xref linkend="sql-createtrigger">.
-    The same trigger function can be used for multiple triggers.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</productname> offers both <firstterm>per-row</>
-    triggers and <firstterm>per-statement</> triggers.  With a per-row
-    trigger, the trigger function
-    is invoked once for each row that is affected by the statement
-    that fired the trigger. In contrast, a per-statement trigger is
-    invoked only once when an appropriate statement is executed,
-    regardless of the number of rows affected by that statement. In
-    particular, a statement that affects zero rows will still result
-    in the execution of any applicable per-statement triggers. These
-    two types of triggers are sometimes called <firstterm>row-level</>
-    triggers and <firstterm>statement-level</> triggers,
-    respectively. Triggers on <command>TRUNCATE</command> may only be
-    defined at statement level.  On views, triggers that fire before or
-    after may only be defined at statement level, while triggers that fire
-    instead of an <command>INSERT</command>, <command>UPDATE</command>,
-    or <command>DELETE</command> may only be defined at row level.
-   </para>
-
-   <para>
-    Triggers are also classified according to whether they fire
-    <firstterm>before</>, <firstterm>after</>, or
-    <firstterm>instead of</> the operation. These are referred to
-    as <literal>BEFORE</> triggers, <literal>AFTER</> triggers, and
-    <literal>INSTEAD OF</> triggers respectively.
-    Statement-level <literal>BEFORE</> triggers naturally fire before the
-    statement starts to do anything, while statement-level <literal>AFTER</>
-    triggers fire at the very end of the statement.  These types of
-    triggers may be defined on tables or views.  Row-level <literal>BEFORE</>
-    triggers fire immediately before a particular row is operated on,
-    while row-level <literal>AFTER</> triggers fire at the end of the
-    statement (but before any statement-level <literal>AFTER</> triggers).
-    These types of triggers may only be defined on tables.  Row-level
-    <literal>INSTEAD OF</> triggers may only be defined on views, and fire
-    immediately as each row in the view is identified as needing to be
-    operated on.
-   </para>
-
-   <para>
-    Trigger functions invoked by per-statement triggers should always
-    return <symbol>NULL</symbol>. Trigger functions invoked by per-row
-    triggers can return a table row (a value of
-    type <structname>HeapTuple</structname>) to the calling executor,
-    if they choose.  A row-level trigger fired before an operation has
-    the following choices:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       It can return <symbol>NULL</> to skip the operation for the
-       current row. This instructs the executor to not perform the
-       row-level operation that invoked the trigger (the insertion,
-       modification, or deletion of a particular table row).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       For row-level <command>INSERT</command>
-       and <command>UPDATE</command> triggers only, the returned row
-       becomes the row that will be inserted or will replace the row
-       being updated.  This allows the trigger function to modify the
-       row being inserted or updated.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    A row-level <literal>BEFORE</> trigger that does not intend to cause
-    either of these behaviors must be careful to return as its result the same
-    row that was passed in (that is, the <varname>NEW</varname> row
-    for <command>INSERT</command> and <command>UPDATE</command>
-    triggers, the <varname>OLD</varname> row for
-    <command>DELETE</command> triggers).
-   </para>
-
-   <para>
-    A row-level <literal>INSTEAD OF</> trigger should either return
-    <symbol>NULL</> to indicate that it did not modify any data from
-    the view's underlying base tables, or it should return the view
-    row that was passed in (the <varname>NEW</varname> row
-    for <command>INSERT</command> and <command>UPDATE</command>
-    operations, or the <varname>OLD</varname> row for
-    <command>DELETE</command> operations). A nonnull return value is
-    used to signal that the trigger performed the necessary data
-    modifications in the view.  This will cause the count of the number
-    of rows affected by the command to be incremented. For
-    <command>INSERT</> and <command>UPDATE</> operations, the trigger
-    may modify the <varname>NEW</> row before returning it.  This will
-    change the data returned by
-    <command>INSERT RETURNING</> or <command>UPDATE RETURNING</>,
-    and is useful when the view will not show exactly the same data
-    that was provided.
-   </para>
-
-   <para>
-    The return value is ignored for row-level triggers fired after an
-    operation, and so they can return <symbol>NULL</>.
-   </para>
-
-   <para>
-    If more than one trigger is defined for the same event on the same
-    relation, the triggers will be fired in alphabetical order by
-    trigger name.  In the case of <literal>BEFORE</> and
-    <literal>INSTEAD OF</> triggers, the possibly-modified row returned by
-    each trigger becomes the input to the next trigger.  If any
-    <literal>BEFORE</> or <literal>INSTEAD OF</> trigger returns
-    <symbol>NULL</>, the operation is abandoned for that row and subsequent
-    triggers are not fired (for that row).
-   </para>
-
-   <para>
-    A trigger definition can also specify a Boolean <literal>WHEN</>
-    condition, which will be tested to see whether the trigger should
-    be fired.  In row-level triggers the <literal>WHEN</> condition can
-    examine the old and/or new values of columns of the row.  (Statement-level
-    triggers can also have <literal>WHEN</> conditions, although the feature
-    is not so useful for them.)  In a <literal>BEFORE</> trigger, the
-    <literal>WHEN</>
-    condition is evaluated just before the function is or would be executed,
-    so using <literal>WHEN</> is not materially different from testing the
-    same condition at the beginning of the trigger function.  However, in
-    an <literal>AFTER</> trigger, the <literal>WHEN</> condition is evaluated
-    just after the row update occurs, and it determines whether an event is
-    queued to fire the trigger at the end of statement.  So when an
-    <literal>AFTER</> trigger's
-    <literal>WHEN</> condition does not return true, it is not necessary
-    to queue an event nor to re-fetch the row at end of statement.  This
-    can result in significant speedups in statements that modify many
-    rows, if the trigger only needs to be fired for a few of the rows.
-    <literal>INSTEAD OF</> triggers do not support
-    <literal>WHEN</> conditions.
-   </para>
-
-   <para>
-    Typically, row-level <literal>BEFORE</> triggers are used for checking or
-    modifying the data that will be inserted or updated.  For example,
-    a <literal>BEFORE</> trigger might be used to insert the current time into a
-    <type>timestamp</type> column, or to check that two elements of the row are
-    consistent. Row-level <literal>AFTER</> triggers are most sensibly
-    used to propagate the updates to other tables, or make consistency
-    checks against other tables.  The reason for this division of labor is
-    that an <literal>AFTER</> trigger can be certain it is seeing the final
-    value of the row, while a <literal>BEFORE</> trigger cannot; there might
-    be other <literal>BEFORE</> triggers firing after it.  If you have no
-    specific reason to make a trigger <literal>BEFORE</> or
-    <literal>AFTER</>, the <literal>BEFORE</> case is more efficient, since
-    the information about
-    the operation doesn't have to be saved until end of statement.
-   </para>
-
-   <para>
-    If a trigger function executes SQL commands then these
-    commands might fire triggers again. This is known as cascading
-    triggers.  There is no direct limitation on the number of cascade
-    levels.  It is possible for cascades to cause a recursive invocation
-    of the same trigger; for example, an <command>INSERT</command>
-    trigger might execute a command that inserts an additional row
-    into the same table, causing the <command>INSERT</command> trigger
-    to be fired again.  It is the trigger programmer's responsibility
-    to avoid infinite recursion in such scenarios.
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>trigger</>
-     <secondary>arguments for trigger functions</>
-    </indexterm>
-    When a trigger is being defined, arguments can be specified for
-    it. The purpose of including arguments in the
-    trigger definition is to allow different triggers with similar
-    requirements to call the same function.  As an example, there
-    could be a generalized trigger function that takes as its
-    arguments two column names and puts the current user in one and
-    the current time stamp in the other.  Properly written, this
-    trigger function would be independent of the specific table it is
-    triggering on.  So the same function could be used for
-    <command>INSERT</command> events on any table with suitable
-    columns, to automatically track creation of records in a
-    transaction table for example. It could also be used to track
-    last-update events if defined as an <command>UPDATE</command>
-    trigger.
-   </para>
-
-   <para>
-    Each programming language that supports triggers has its own method
-    for making the trigger input data available to the trigger function.
-    This input data includes the type of trigger event (e.g.,
-    <command>INSERT</command> or <command>UPDATE</command>) as well as any
-    arguments that were listed in <command>CREATE TRIGGER</>.
-    For a row-level trigger, the input data also includes the
-    <varname>NEW</varname> row for <command>INSERT</command> and
-    <command>UPDATE</command> triggers, and/or the <varname>OLD</varname> row
-    for <command>UPDATE</command> and <command>DELETE</command> triggers.
-    Statement-level triggers do not currently have any way to examine the
-    individual row(s) modified by the statement.
-   </para>
-<!## end>
-  </sect1>
-
-  <sect1 id="trigger-datachanges">
-   <title>Visibility of Data Changes</title>
-
-<!## XC>
-&xconly;
-  <para>
-   The trigger will be supported in the future.  The document will be supported then.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Triggers are not currently supported, but will be in the future. 
-  </para>
-<!## end>
-
-<!## PG>
-
-   <para>
-    If you execute SQL commands in your trigger function, and these
-    commands access the table that the trigger is for, then
-    you need to be aware of the data visibility rules, because they determine
-    whether these SQL commands will see the data change that the trigger
-    is fired for.  Briefly:
-
-    <itemizedlist>
-
-     <listitem>
-      <para>
-       Statement-level triggers follow simple visibility rules: none of
-       the changes made by a statement are visible to statement-level
-       triggers that are invoked before the statement, whereas all
-       modifications are visible to statement-level <literal>AFTER</>
-       triggers.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The data change (insertion, update, or deletion) causing the
-       trigger to fire is naturally <emphasis>not</emphasis> visible
-       to SQL commands executed in a row-level <literal>BEFORE</> trigger,
-       because it hasn't happened yet.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       However, SQL commands executed in a row-level <literal>BEFORE</>
-       trigger <emphasis>will</emphasis> see the effects of data
-       changes for rows previously processed in the same outer
-       command.  This requires caution, since the ordering of these
-       change events is not in general predictable; a SQL command that
-       affects multiple rows can visit the rows in any order.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Similarly, a row-level <literal>INSTEAD OF</> trigger will see the
-       effects of data changes made by previous firings of <literal>INSTEAD
-       OF</> triggers in the same outer command.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       When a row-level <literal>AFTER</> trigger is fired, all data
-       changes made
-       by the outer command are already complete, and are visible to
-       the invoked trigger function.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    If your trigger function is written in any of the standard procedural
-    languages, then the above statements apply only if the function is
-    declared <literal>VOLATILE</>.  Functions that are declared
-    <literal>STABLE</> or <literal>IMMUTABLE</> will not see changes made by
-    the calling command in any case.
-   </para>
-
-   <para>
-    Further information about data visibility rules can be found in
-    <xref linkend="spi-visibility">.  The example in <xref
-    linkend="trigger-example"> contains a demonstration of these rules.
-   </para>
-<!## end>
-  </sect1>
-
-  <sect1 id="trigger-interface">
-   <title>Writing Trigger Functions in C</title>
-
-   <indexterm zone="trigger-interface">
-    <primary>trigger</primary>
-    <secondary>in C</secondary>
-   </indexterm>
-
-<!## XC>
-&xconly;
-  <para>
-   The trigger will be supported in the future.  The document will be supported then.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Triggers are not currently supported, but will be in the future. 
-  </para>
-<!## end>
-
-<!## PG>
-   <para>
-    This section describes the low-level details of the interface to a
-    trigger function.  This information is only needed when writing
-    trigger functions in C.  If you are using a higher-level language then
-    these details are handled for you.  In most cases you should consider
-    using a procedural language before writing your triggers in C.  The
-    documentation of each procedural language explains how to write a
-    trigger in that language.
-   </para>
-
-   <para>
-    Trigger functions must use the <quote>version 1</> function manager
-    interface.
-   </para>
-
-   <para>
-    When a function is called by the trigger manager, it is not passed
-    any normal arguments, but it is passed a <quote>context</>
-    pointer pointing to a <structname>TriggerData</> structure.  C
-    functions can check whether they were called from the trigger
-    manager or not by executing the macro:
-<programlisting>
-CALLED_AS_TRIGGER(fcinfo)
-</programlisting>
-    which expands to:
-<programlisting>
-((fcinfo)-&gt;context != NULL &amp;&amp; IsA((fcinfo)-&gt;context, TriggerData))
-</programlisting>
-    If this returns true, then it is safe to cast
-    <literal>fcinfo-&gt;context</> to type <literal>TriggerData
-    *</literal> and make use of the pointed-to
-    <structname>TriggerData</> structure.  The function must
-    <emphasis>not</emphasis> alter the <structname>TriggerData</>
-    structure or any of the data it points to.
-   </para>
-
-   <para>
-    <structname>struct TriggerData</structname> is defined in
-    <filename>commands/trigger.h</filename>:
-
-<programlisting>
-typedef struct TriggerData
-{
-    NodeTag       type;
-    TriggerEvent  tg_event;
-    Relation      tg_relation;
-    HeapTuple     tg_trigtuple;
-    HeapTuple     tg_newtuple;
-    Trigger      *tg_trigger;
-    Buffer        tg_trigtuplebuf;
-    Buffer        tg_newtuplebuf;
-} TriggerData;
-</programlisting>
-
-    where the members are defined as follows:
-
-    <variablelist>
-     <varlistentry>
-      <term><structfield>type</></term>
-      <listitem>
-       <para>
-        Always <literal>T_TriggerData</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><structfield>tg_event</></term>
-      <listitem>
-       <para>
-        Describes the event for which the function is called. You can use the
-        following macros to examine <literal>tg_event</literal>:
-
-        <variablelist>
-         <varlistentry>
-          <term><literal>TRIGGER_FIRED_BEFORE(tg_event)</literal></term>
-          <listitem>
-           <para>
-            Returns true if the trigger fired before the operation.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>TRIGGER_FIRED_AFTER(tg_event)</literal></term>
-          <listitem>
-           <para>
-            Returns true if the trigger fired after the operation.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>TRIGGER_FIRED_INSTEAD(tg_event)</literal></term>
-          <listitem>
-           <para>
-            Returns true if the trigger fired instead of the operation.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>TRIGGER_FIRED_FOR_ROW(tg_event)</literal></term>
-          <listitem>
-           <para>
-            Returns true if the trigger fired for a row-level event.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>TRIGGER_FIRED_FOR_STATEMENT(tg_event)</literal></term>
-          <listitem>
-           <para>
-            Returns true if the trigger fired for a statement-level event.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>TRIGGER_FIRED_BY_INSERT(tg_event)</literal></term>
-          <listitem>
-           <para>
-            Returns true if the trigger was fired by an <command>INSERT</command> command.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>TRIGGER_FIRED_BY_UPDATE(tg_event)</literal></term>
-          <listitem>
-           <para>
-            Returns true if the trigger was fired by an <command>UPDATE</command> command.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>TRIGGER_FIRED_BY_DELETE(tg_event)</literal></term>
-          <listitem>
-           <para>
-            Returns true if the trigger was fired by a <command>DELETE</command> command.
-           </para>
-          </listitem>
-         </varlistentry>
-
-         <varlistentry>
-          <term><literal>TRIGGER_FIRED_BY_TRUNCATE(tg_event)</literal></term>
-          <listitem>
-           <para>
-            Returns true if the trigger was fired by a <command>TRUNCATE</command> command.
-           </para>
-          </listitem>
-         </varlistentry>
-        </variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><structfield>tg_relation</></term>
-      <listitem>
-       <para>
-        A pointer to a structure describing the relation that the trigger fired for.
-        Look at <filename>utils/rel.h</> for details about
-        this structure.  The most interesting things are
-        <literal>tg_relation-&gt;rd_att</> (descriptor of the relation
-        tuples) and <literal>tg_relation-&gt;rd_rel-&gt;relname</>
-        (relation name; the type is not <type>char*</> but
-        <type>NameData</>; use
-        <literal>SPI_getrelname(tg_relation)</> to get a <type>char*</> if you
-        need a copy of the name).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><structfield>tg_trigtuple</></term>
-      <listitem>
-       <para>
-        A pointer to the row for which the trigger was fired. This is
-        the row being inserted, updated, or deleted.  If this trigger
-        was fired for an <command>INSERT</command> or
-        <command>DELETE</command> then this is what you should return
-        from the function if you don't want to replace the row with
-        a different one (in the case of <command>INSERT</command>) or
-        skip the operation.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><structfield>tg_newtuple</></term>
-      <listitem>
-       <para>
-        A pointer to the new version of the row, if the trigger was
-        fired for an <command>UPDATE</command>, and <symbol>NULL</> if
-        it is for an <command>INSERT</command> or a
-        <command>DELETE</command>. This is what you have to return
-        from the function if the event is an <command>UPDATE</command>
-        and you don't want to replace this row by a different one or
-        skip the operation.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><structfield>tg_trigger</></term>
-      <listitem>
-       <para>
-        A pointer to a structure of type <structname>Trigger</>,
-        defined in <filename>utils/rel.h</>:
-
-<programlisting>
-typedef struct Trigger
-{
-    Oid         tgoid;
-    char       *tgname;
-    Oid         tgfoid;
-    int16       tgtype;
-    bool        tgenabled;
-    bool        tgisinternal;
-    Oid         tgconstrrelid;
-    Oid         tgconstrindid;
-    Oid         tgconstraint;
-    bool        tgdeferrable;
-    bool        tginitdeferred;
-    int16       tgnargs;
-    int16       tgnattr;
-    int16      *tgattr;
-    char      **tgargs;
-    char       *tgqual;
-} Trigger;
-</programlisting>
-
-       where <structfield>tgname</> is the trigger's name,
-       <structfield>tgnargs</> is the number of arguments in
-       <structfield>tgargs</>, and <structfield>tgargs</> is an array of
-       pointers to the arguments specified in the <command>CREATE
-       TRIGGER</command> statement. The other members are for internal use
-       only.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><structfield>tg_trigtuplebuf</></term>
-      <listitem>
-       <para>
-        The buffer containing <structfield>tg_trigtuple</structfield>, or <symbol>InvalidBuffer</symbol> if there
-        is no such tuple or it is not stored in a disk buffer.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><structfield>tg_newtuplebuf</></term>
-      <listitem>
-       <para>
-        The buffer containing <structfield>tg_newtuple</structfield>, or <symbol>InvalidBuffer</symbol> if there
-        is no such tuple or it is not stored in a disk buffer.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    A trigger function must return either a
-    <structname>HeapTuple</> pointer or a <symbol>NULL</> pointer
-    (<emphasis>not</> an SQL null value, that is, do not set <parameter>isNull</parameter> true).
-    Be careful to return either
-    <structfield>tg_trigtuple</> or <structfield>tg_newtuple</>,
-    as appropriate, if you don't want to modify the row being operated on.
-   </para>
-<!## end>
-  </sect1>
-
-  <sect1 id="trigger-example">
-   <title>A Complete Trigger Example</title>
-
-<!## XC>
-&xconly;
-  <para>
-   The trigger will be supported in the future.  The document will be supported then.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Triggers are not currently supported, but will be in the future. 
-  </para>
-<!## end>
-
-<!## PG>
-   <para>
-    Here is a very simple example of a trigger function written in C.
-    (Examples of triggers written in procedural languages can be found
-    in the documentation of the procedural languages.)
-   </para>
-
-   <para>
-    The function <function>trigf</> reports the number of rows in the
-    table <structname>ttest</> and skips the actual operation if the
-    command attempts to insert a null value into the column
-    <structfield>x</>. (So the trigger acts as a not-null constraint but
-    doesn't abort the transaction.)
-   </para>
-
-   <para>
-    First, the table definition:
-<programlisting>
-CREATE TABLE ttest (
-    x integer
-);
-</programlisting>
-   </para>
-
-   <para>
-    This is the source code of the trigger function:
-<programlisting><![CDATA[
-#include "postgres.h"
-#include "executor/spi.h"       /* this is what you need to work with SPI */
-#include "commands/trigger.h"   /* ... and triggers */
-
-#ifdef PG_MODULE_MAGIC
-PG_MODULE_MAGIC;
-#endif
-
-extern Datum trigf(PG_FUNCTION_ARGS);
-
-PG_FUNCTION_INFO_V1(trigf);
-
-Datum
-trigf(PG_FUNCTION_ARGS)
-{
-    TriggerData *trigdata = (TriggerData *) fcinfo->context;
-    TupleDesc   tupdesc;
-    HeapTuple   rettuple;
-    char       *when;
-    bool        checknull = false;
-    bool        isnull;
-    int         ret, i;
-
-    /* make sure it's called as a trigger at all */
-    if (!CALLED_AS_TRIGGER(fcinfo))
-        elog(ERROR, "trigf: not called by trigger manager");
-
-    /* tuple to return to executor */
-    if (TRIGGER_FIRED_BY_UPDATE(trigdata->tg_event))
-        rettuple = trigdata->tg_newtuple;
-    else
-        rettuple = trigdata->tg_trigtuple;
-
-    /* check for null values */
-    if (!TRIGGER_FIRED_BY_DELETE(trigdata->tg_event)
-        && TRIGGER_FIRED_BEFORE(trigdata->tg_event))
-        checknull = true;
-
-    if (TRIGGER_FIRED_BEFORE(trigdata->tg_event))
-        when = "before";
-    else
-        when = "after ";
-
-    tupdesc = trigdata->tg_relation->rd_att;
-
-    /* connect to SPI manager */
-    if ((ret = SPI_connect()) < 0)
-        elog(ERROR, "trigf (fired %s): SPI_connect returned %d", when, ret);
-
-    /* get number of rows in table */
-    ret = SPI_exec("SELECT count(*) FROM ttest", 0);
-
-    if (ret < 0)
-        elog(ERROR, "trigf (fired %s): SPI_exec returned %d", when, ret);
-
-    /* count(*) returns int8, so be careful to convert */
-    i = DatumGetInt64(SPI_getbinval(SPI_tuptable->vals[0],
-                                    SPI_tuptable->tupdesc,
-                                    1,
-                                    &isnull));
-
-    elog (INFO, "trigf (fired %s): there are %d rows in ttest", when, i);
-
-    SPI_finish();
-
-    if (checknull)
-    {
-        SPI_getbinval(rettuple, tupdesc, 1, &isnull);
-        if (isnull)
-            rettuple = NULL;
-    }
-
-    return PointerGetDatum(rettuple);
-}
-]]>
-</programlisting>
-   </para>
-
-   <para>
-    After you have compiled the source code (see <xref
-    linkend="dfunc">), declare the function and the triggers:
-<programlisting>
-CREATE FUNCTION trigf() RETURNS trigger
-    AS '<replaceable>filename</>'
-    LANGUAGE C;
-
-CREATE TRIGGER tbefore BEFORE INSERT OR UPDATE OR DELETE ON ttest
-    FOR EACH ROW EXECUTE PROCEDURE trigf();
-
-CREATE TRIGGER tafter AFTER INSERT OR UPDATE OR DELETE ON ttest
-    FOR EACH ROW EXECUTE PROCEDURE trigf();
-</programlisting>
-   </para>
-
-   <para>
-    Now you can test the operation of the trigger:
-<screen>
-=&gt; INSERT INTO ttest VALUES (NULL);
-INFO:  trigf (fired before): there are 0 rows in ttest
-INSERT 0 0
-
--- Insertion skipped and AFTER trigger is not fired
-
-=&gt; SELECT * FROM ttest;
- x
----
-(0 rows)
-
-=&gt; INSERT INTO ttest VALUES (1);
-INFO:  trigf (fired before): there are 0 rows in ttest
-INFO:  trigf (fired after ): there are 1 rows in ttest
-                                       ^^^^^^^^
-                             remember what we said about visibility.
-INSERT 167793 1
-vac=&gt; SELECT * FROM ttest;
- x
----
- 1
-(1 row)
-
-=&gt; INSERT INTO ttest SELECT x * 2 FROM ttest;
-INFO:  trigf (fired before): there are 1 rows in ttest
-INFO:  trigf (fired after ): there are 2 rows in ttest
-                                       ^^^^^^
-                             remember what we said about visibility.
-INSERT 167794 1
-=&gt; SELECT * FROM ttest;
- x
----
- 1
- 2
-(2 rows)
-
-=&gt; UPDATE ttest SET x = NULL WHERE x = 2;
-INFO:  trigf (fired before): there are 2 rows in ttest
-UPDATE 0
-=&gt; UPDATE ttest SET x = 4 WHERE x = 2;
-INFO:  trigf (fired before): there are 2 rows in ttest
-INFO:  trigf (fired after ): there are 2 rows in ttest
-UPDATE 1
-vac=&gt; SELECT * FROM ttest;
- x
----
- 1
- 4
-(2 rows)
-
-=&gt; DELETE FROM ttest;
-INFO:  trigf (fired before): there are 2 rows in ttest
-INFO:  trigf (fired before): there are 1 rows in ttest
-INFO:  trigf (fired after ): there are 0 rows in ttest
-INFO:  trigf (fired after ): there are 0 rows in ttest
-                                       ^^^^^^
-                             remember what we said about visibility.
-DELETE 2
-=&gt; SELECT * FROM ttest;
- x
----
-(0 rows)
-</screen>
-
-   </para>
-
-   <para>
-    There are more complex examples in
-    <filename>src/test/regress/regress.c</filename> and
-    in <xref linkend="contrib-spi">.
-   </para>
-<!## end>
-  </sect1>
- </chapter>
diff --git a/doc-xc/src/sgml/tsearch2.sgmlin b/doc-xc/src/sgml/tsearch2.sgmlin
deleted file mode 100644
index b161f95581..0000000000
--- a/doc-xc/src/sgml/tsearch2.sgmlin
+++ /dev/null
@@ -1,207 +0,0 @@
-<!-- doc/src/sgml/tsearch2.sgml -->
-
-<sect1 id="tsearch2" xreflabel="tsearch2">
- <title>tsearch2</title>
-
- <indexterm zone="tsearch2">
-  <primary>tsearch2</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <application>tsearch2</> module provides backwards-compatible
-  text search functionality for applications that used
-  <application>tsearch2</> before text searching was integrated
-  into core <productname>PostgreSQL</productname> in release 8.3.
- </para>
-
- <sect2>
-  <title>Portability Issues</title>
-
-&common;
-  <para>
-   Although the built-in text search features were based on
-   <application>tsearch2</> and are largely similar to it,
-   there are numerous small differences that will create portability
-   issues for existing applications:
-  </para>
-
-  <itemizedlist mark="bullet">
-   <listitem>
-    <para>
-     Some functions' names were changed, for example <function>rank</>
-     to <function>ts_rank</>.
-     The replacement <literal>tsearch2</literal> module
-     provides aliases having the old names.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The built-in text search data types and functions all exist within
-     the system schema <literal>pg_catalog</>.  In an installation using
-     <application>tsearch2</>, these objects would usually have been in
-     the <literal>public</> schema, though some users chose to place them
-     in a separate schema of their own.  Explicitly schema-qualified
-     references to the objects will therefore fail in either case.
-     The replacement <literal>tsearch2</literal> module
-     provides alias objects that are stored in <literal>public</>
-     (or another schema if necessary) so that such references will still work.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     There is no concept of a <quote>current parser</> or <quote>current
-     dictionary</> in the built-in text search features, only of a current
-     search configuration (set by the <varname>default_text_search_config</>
-     parameter).  While the current parser and current dictionary were used
-     only by functions intended for debugging, this might still pose
-     a porting obstacle in some cases.
-     The replacement <literal>tsearch2</literal> module emulates these
-     additional state variables and provides backwards-compatible functions
-     for setting and retrieving them.
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   There are some issues that are not addressed by the replacement
-   <literal>tsearch2</literal> module, and will therefore require
-   application code changes in any case:
-  </para>
-
-  <itemizedlist mark="bullet">
-   <listitem>
-    <para>
-     The old <function>tsearch2</> trigger function allowed items in its
-     argument list to be names of functions to be invoked on the text data
-     before it was converted to <type>tsvector</> format.  This was removed
-     as being a security hole, since it was not possible to guarantee that
-     the function invoked was the one intended.  The recommended approach
-     if the data must be massaged before being indexed is to write a custom
-     trigger that does the work for itself.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Text search configuration information has been moved into core
-     system catalogs that are noticeably different from the tables used
-     by <application>tsearch2</>.  Any applications that examined
-     or modified those tables will need adjustment.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     If an application used any custom text search configurations,
-     those will need to be set up in the core
-     catalogs using the new text search configuration SQL commands.
-     The replacement <literal>tsearch2</literal> module offers a little
-     bit of support for this by making it possible to load an old set
-     of <application>tsearch2</> configuration tables into
-     <productname>PostgreSQL</productname> 8.3.  (Without the module,
-     it is not possible to load the configuration data because values in the
-     <type>regprocedure</> columns cannot be resolved to functions.)
-     While those configuration tables won't actually <emphasis>do</>
-     anything, at least their contents will be available to be consulted
-     while setting up an equivalent custom configuration in 8.3.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The old <function>reset_tsearch()</> and <function>get_covers()</>
-     functions are not supported.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The replacement <literal>tsearch2</literal> module does not define
-     any alias operators, relying entirely on the built-in ones.
-     This would only pose an issue if an application used explicitly
-     schema-qualified operator names, which is very uncommon.
-    </para>
-   </listitem>
-  </itemizedlist>
-
- </sect2>
-
- <sect2>
-  <title>Converting a pre-8.3 Installation</title>
-
-&common;
-  <para>
-   The recommended way to update a pre-8.3 installation that uses
-   <application>tsearch2</> is:
-  </para>
-
-  <procedure>
-   <step>
-    <para>
-     Make a dump from the old installation in the usual way,
-     but be sure not to use <literal>-c</> (<literal>--clean</>)
-     option of <application>pg_dump</> or <application>pg_dumpall</>.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     In the new installation, create empty database(s) and install
-     the replacement <literal>tsearch2</literal> module into each
-     database that will use text search.  This must be done
-     <emphasis>before</> loading the dump data!  If your old installation
-     had the <application>tsearch2</> objects in a schema other
-     than <literal>public</>, be sure to adjust the
-     <command>CREATE EXTENSION</> command so that the replacement
-     objects are created in that same schema.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Load the dump data.  There will be quite a few errors reported
-     due to failure to recreate the original <application>tsearch2</>
-     objects.  These errors can be ignored, but this means you cannot
-     restore the dump in a single transaction (eg, you cannot use
-     <application>pg_restore</>'s <option>-1</> switch).
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Examine the contents of the restored <application>tsearch2</>
-     configuration tables (<structname>pg_ts_cfg</> and so on), and
-     create equivalent built-in text search configurations as needed.
-     You may drop the old configuration tables once you've extracted
-     all the useful information from them.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Test your application.
-    </para>
-   </step>
-  </procedure>
-
-  <para>
-   At a later time you may wish to rename application references
-   to the alias text search objects, so that you can eventually
-   uninstall the replacement <literal>tsearch2</literal> module.
-  </para>
-
- </sect2>
-
- <sect2>
-  <title>References</title>
-  <para>
-   Tsearch2 Development Site
-   <ulink url="http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/"></ulink>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/typeconv.sgmlin b/doc-xc/src/sgml/typeconv.sgmlin
deleted file mode 100644
index df79e73dea..0000000000
--- a/doc-xc/src/sgml/typeconv.sgmlin
+++ /dev/null
@@ -1,1116 +0,0 @@
-<!-- doc/src/sgml/typeconv.sgml -->
-
-<chapter id="typeconv">
-<title>Type Conversion</title>
-
-<indexterm zone="typeconv">
- <primary>data type</primary>
- <secondary>conversion</secondary>
-</indexterm>
-
-&common;
-
-<para>
-<!## PG>
-<acronym>SQL</acronym> statements can, intentionally or not, require
-the mixing of different data types in the same expression.
-<productname>PostgreSQL</productname> has extensive facilities for
-evaluating mixed-type expressions.
-<!## end>
-<!## XC>
-<acronym>SQL</acronym> statements can, intentionally or not, require
-the mixing of different data types in the same expression.
-<productname>Postgres-XC</productname> inherits extensive facilities for
-evaluating mixed-type expressions from <productname>PostgreSQL</>.
-<!## end>
-<!## XL>
-<acronym>SQL</acronym> statements can, intentionally or not, require
-the mixing of different data types in the same expression.
-<productname>Postgres-XL</productname> inherits extensive facilities for
-evaluating mixed-type expressions from <productname>PostgreSQL</>.
-<!## end>
-</para>
-
-<para>
-In many cases a user does not need
-to understand the details of the type conversion mechanism.
-<!## PG>
-However, implicit conversions done by <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-However, implicit conversions done by <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-However, implicit conversions done by <productname>Postgres-XL</productname>
-<!## end>
-can affect the results of a query.  When necessary, these results
-can be tailored by using <emphasis>explicit</emphasis> type conversion.
-</para>
-
-<para>
-<!## PG>
-This chapter introduces the <productname>PostgreSQL</productname>
-type conversion mechanisms and conventions.
-Refer to the relevant sections in <xref linkend="datatype"> and <xref linkend="functions">
-for more information on specific data types and allowed functions and
-operators.
-<!## end>
-<!## XC>
-This chapter introduces the <productname>Postgres-XC</productname>
-type conversion mechanisms and conventions inherited from <productname>PostgreSQL</>.
-Refer to the relevant sections in <xref linkend="datatype"> and <xref linkend="functions">
-for more information on specific data types and allowed functions and
-operators.
-<!## end>
-<!## XL>
-This chapter introduces the <productname>Postgres-XL</productname>
-type conversion mechanisms and conventions inherited from <productname>PostgreSQL</>.
-Refer to the relevant sections in <xref linkend="datatype"> and <xref linkend="functions">
-for more information on specific data types and allowed functions and
-operators.
-<!## end>
-</para>
-
-<sect1 id="typeconv-overview">
-<title>Overview</title>
-&common;
-<!## PG>
-<para>
-<acronym>SQL</acronym> is a strongly typed language. That is, every data item
-has an associated data type which determines its behavior and allowed usage.
-<productname>PostgreSQL</productname> has an extensible type system that is
-more general and flexible than other <acronym>SQL</acronym> implementations.
-Hence, most type conversion behavior in <productname>PostgreSQL</productname>
-is governed by general rules rather than by <foreignphrase>ad hoc</>
-heuristics.  This allows the use of mixed-type expressions even with
-user-defined types.
-</para>
-<!## end>
-<!## XC>
-<para>
-<acronym>SQL</acronym> is a strongly typed language. That is, every data item
-has an associated data type which determines its behavior and allowed usage.
-<productname>Postgres-XC</productname> has an extensible type system that is
-more general and flexible than other <acronym>SQL</acronym> implementations.
-Hence, most type conversion behavior in <productname>Postgres-XC</productname>
-is governed by general rules rather than by <foreignphrase>ad hoc</>
-heuristics.  This allows the use of mixed-type expressions even with
-user-defined types.
-</para>
-<!## end>
-<!## XL>
-<para>
-<acronym>SQL</acronym> is a strongly typed language. That is, every data item
-has an associated data type which determines its behavior and allowed usage.
-<productname>Postgres-XL</productname> has an extensible type system that is
-more general and flexible than other <acronym>SQL</acronym> implementations.
-Hence, most type conversion behavior in <productname>Postgres-XL</productname>
-is governed by general rules rather than by <foreignphrase>ad hoc</>
-heuristics.  This allows the use of mixed-type expressions even with
-user-defined types.
-</para>
-<!## end>
-
-<para>
-<!## PG>
-The <productname>PostgreSQL</productname> scanner/parser divides lexical
-elements into five fundamental categories: integers, non-integer numbers,
-strings, identifiers, and key words.  Constants of most non-numeric types are
-first classified as strings. The <acronym>SQL</acronym> language definition
-allows specifying type names with strings, and this mechanism can be used in
-<productname>PostgreSQL</productname> to start the parser down the correct
-path. For example, the query:
-<!## end>
-<!## XC>
-The <productname>Postgres-XC</productname> scanner/parser divides lexical
-elements into five fundamental categories: integers, non-integer numbers,
-strings, identifiers, and key words.  Constants of most non-numeric types are
-first classified as strings. The <acronym>SQL</acronym> language definition
-allows specifying type names with strings, and this mechanism can be used in
-<productname>Postgres-XC</productname> to start the parser down the correct
-path. For example, the query:
-<!## end>
-<!## XL>
-The <productname>Postgres-XL</productname> scanner/parser divides lexical
-elements into five fundamental categories: integers, non-integer numbers,
-strings, identifiers, and key words.  Constants of most non-numeric types are
-first classified as strings. The <acronym>SQL</acronym> language definition
-allows specifying type names with strings, and this mechanism can be used in
-<productname>Postgres-XL</productname> to start the parser down the correct
-path. For example, the query:
-<!## end>
-
-<screen>
-SELECT text 'Origin' AS "label", point '(0,0)' AS "value";
-
- label  | value
---------+-------
- Origin | (0,0)
-(1 row)
-</screen>
-
-has two literal constants, of type <type>text</type> and <type>point</type>.
-If a type is not specified for a string literal, then the placeholder type
-<type>unknown</type> is assigned initially, to be resolved in later
-stages as described below.
-</para>
-
-<para>
-There are four fundamental <acronym>SQL</acronym> constructs requiring
-<!## PG>
-distinct type conversion rules in the <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-distinct type conversion rules in the <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-distinct type conversion rules in the <productname>Postgres-XL</productname>
-<!## end>
-parser:
-
-<variablelist>
-<varlistentry>
-<term>
-Function calls
-</term>
-<listitem>
-<!## PG>
-<para>
-Much of the <productname>PostgreSQL</productname> type system is built around a
-rich set of functions. Functions can have one or more arguments.
-Since <productname>PostgreSQL</productname> permits function
-overloading, the function name alone does not uniquely identify the function
-to be called; the parser must select the right function based on the data
-types of the supplied arguments.
-</para>
-<!## end>
-<!## XC>
-<para>
-Much of the <productname>Postgres-XC</productname> type system is built around a
-rich set of functions. Functions can have one or more arguments.
-Since <productname>Postgres-XC</productname> permits function
-overloading, the function name alone does not uniquely identify the function
-to be called; the parser must select the right function based on the data
-types of the supplied arguments.
-</para>
-<!## end>
-<!## XL>
-<para>
-Much of the <productname>Postgres-XL</productname> type system is built around a
-rich set of functions. Functions can have one or more arguments.
-Since <productname>Postgres-XL</productname> permits function
-overloading, the function name alone does not uniquely identify the function
-to be called; the parser must select the right function based on the data
-types of the supplied arguments.
-</para>
-<!## end>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-Operators
-</term>
-<listitem>
-<!## PG>
-<para>
-<productname>PostgreSQL</productname> allows expressions with
-prefix and postfix unary (one-argument) operators,
-as well as binary (two-argument) operators.  Like functions, operators can
-be overloaded, so the same problem of selecting the right operator
-exists.
-</para>
-<!## end>
-<!## XC>
-<para>
-<productname>Postgres-XC</productname> allows expressions with
-prefix and postfix unary (one-argument) operators,
-as well as binary (two-argument) operators.  Like functions, operators can
-be overloaded, so the same problem of selecting the right operator
-exists.
-</para>
-<!## end>
-<!## XL>
-<para>
-<productname>Postgres-XL</productname> allows expressions with
-prefix and postfix unary (one-argument) operators,
-as well as binary (two-argument) operators.  Like functions, operators can
-be overloaded, so the same problem of selecting the right operator
-exists.
-</para>
-<!## end>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-Value Storage
-</term>
-<listitem>
-<para>
-<acronym>SQL</acronym> <command>INSERT</command> and <command>UPDATE</command> statements place the results of
-expressions into a table. The expressions in the statement must be matched up
-with, and perhaps converted to, the types of the target columns.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-<literal>UNION</literal>, <literal>CASE</literal>, and related constructs
-</term>
-<listitem>
-<para>
-Since all query results from a unionized <command>SELECT</command> statement
-must appear in a single set of columns, the types of the results of each
-<command>SELECT</> clause must be matched up and converted to a uniform set.
-Similarly, the result expressions of a <literal>CASE</> construct must be
-converted to a common type so that the <literal>CASE</> expression as a whole
-has a known output type.  The same holds for <literal>ARRAY</> constructs,
-and for the <function>GREATEST</> and <function>LEAST</> functions.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</para>
-
-<para>
-The system catalogs store information about which conversions, or
-<firstterm>casts</firstterm>, exist between which data types, and how to
-perform those conversions.  Additional casts can be added by the user
-with the <xref linkend="sql-createcast">
-command.  (This is usually
-done in conjunction with defining new data types.  The set of casts
-between built-in types has been carefully crafted and is best not
-altered.)
-</para>
-
-<indexterm>
- <primary>data type</primary>
- <secondary>category</secondary>
-</indexterm>
-
-<para>
-An additional heuristic provided by the parser allows improved determination
-of the proper casting behavior among groups of types that have implicit casts.
-Data types are divided into several basic <firstterm>type
-categories</firstterm>, including <type>boolean</type>, <type>numeric</type>,
-<type>string</type>, <type>bitstring</type>, <type>datetime</type>,
-<type>timespan</type>, <type>geometric</type>, <type>network</type>, and
-user-defined.  (For a list see <xref linkend="catalog-typcategory-table">;
-but note it is also possible to create custom type categories.)  Within each
-category there can be one or more <firstterm>preferred types</firstterm>, which
-are preferred when there is a choice of possible types.  With careful selection
-of preferred types and available implicit casts, it is possible to ensure that
-ambiguous expressions (those with multiple candidate parsing solutions) can be
-resolved in a useful way.
-</para>
-
-<para>
-All type conversion rules are designed with several principles in mind:
-
-<itemizedlist>
-<listitem>
-<para>
-Implicit conversions should never have surprising or unpredictable outcomes.
-</para>
-</listitem>
-
-<listitem>
-<para>
-There should be no extra overhead in the parser or executor
-if a query does not need implicit type conversion.
-That is, if a query is well-formed and the types already match, then the query should execute
-without spending extra time in the parser and without introducing unnecessary implicit conversion
-calls in the query.
-</para>
-
-<para>
-Additionally, if a query usually requires an implicit conversion for a function, and
-if then the user defines a new function with the correct argument types, the parser
-should use this new function and no longer do implicit conversion to use the old function.
-</para>
-</listitem>
-</itemizedlist>
-</para>
-
-</sect1>
-
-<sect1 id="typeconv-oper">
-<title>Operators</title>
-
-<indexterm zone="typeconv-oper">
- <primary>operator</primary>
- <secondary>type resolution in an invocation</secondary>
-</indexterm>
-&common;
-  <para>
-   The specific operator that is referenced by an operator expression
-   is determined using the following procedure.
-   Note that this procedure is indirectly affected
-   by the precedence of the involved operators, since that will determine
-   which sub-expressions are taken to be the inputs of which operators.
-   See <xref linkend="sql-precedence"> for more information.
-  </para>
-
-<procedure>
-<title>Operator Type Resolution</title>
-
-<step performance="required">
-<para>
-Select the operators to be considered from the
-<classname>pg_operator</classname> system catalog.  If a non-schema-qualified
-operator name was used (the usual case), the operators
-considered are those with the matching name and argument count that are
-visible in the current search path (see <xref linkend="ddl-schemas-path">).
-If a qualified operator name was given, only operators in the specified
-schema are considered.
-</para>
-
-<substeps>
-<step performance="optional">
-<para>
-If the search path finds multiple operators with identical argument types,
-only the one appearing earliest in the path is considered.  Operators with
-different argument types are considered on an equal footing regardless of
-search path position.
-</para>
-</step>
-</substeps>
-</step>
-
-<step performance="required">
-<para>
-Check for an operator accepting exactly the input argument types.
-If one exists (there can be only one exact match in the set of
-operators considered), use it.
-</para>
-
-<substeps>
-<step performance="optional">
-<para>
-If one argument of a binary operator invocation is of the <type>unknown</type> type,
-then assume it is the same type as the other argument for this check.
-Invocations involving two <type>unknown</type> inputs, or a unary operator
-with an <type>unknown</type> input, will never find a match at this step.
-</para>
-</step>
-</substeps>
-</step>
-
-<step performance="required">
-<para>
-Look for the best match.
-</para>
-<substeps>
-<step performance="required">
-<para>
-Discard candidate operators for which the input types do not match
-and cannot be converted (using an implicit conversion) to match.
-<type>unknown</type> literals are
-assumed to be convertible to anything for this purpose.  If only one
-candidate remains, use it; else continue to the next step.
-</para>
-</step>
-<step performance="required">
-<para>
-Run through all candidates and keep those with the most exact matches
-on input types.  (Domains are considered the same as their base type
-for this purpose.)  Keep all candidates if none have exact matches.
-If only one candidate remains, use it; else continue to the next step.
-</para>
-</step>
-<step performance="required">
-<para>
-Run through all candidates and keep those that accept preferred types (of the
-input data type's type category) at the most positions where type conversion
-will be required.
-Keep all candidates if none accept preferred types.
-If only one candidate remains, use it; else continue to the next step.
-</para>
-</step>
-<step performance="required">
-<para>
-If any input arguments are <type>unknown</type>, check the type
-categories accepted at those argument positions by the remaining
-candidates.  At each position, select the <type>string</type> category
-if any
-candidate accepts that category.  (This bias towards string is appropriate
-since an unknown-type literal looks like a string.) Otherwise, if
-all the remaining candidates accept the same type category, select that
-category; otherwise fail because the correct choice cannot be deduced
-without more clues.  Now discard
-candidates that do not accept the selected type category.  Furthermore,
-if any candidate accepts a preferred type in that category,
-discard candidates that accept non-preferred types for that argument.
-</para>
-</step>
-<step performance="required">
-<para>
-If only one candidate remains, use it.  If no candidate or more than one
-candidate remains,
-then fail.
-</para>
-</step>
-</substeps>
-</step>
-</procedure>
-
-<para>
-Some examples follow.
-</para>
-
-<example>
-<title>Factorial Operator Type Resolution</title>
-
-<para>
-There is only one factorial operator (postfix <literal>!</>)
-defined in the standard catalog, and it takes an argument of type
-<type>bigint</type>.
-The scanner assigns an initial type of <type>integer</type> to the argument
-in this query expression:
-<screen>
-SELECT 40 ! AS "40 factorial";
-
-                   40 factorial
---------------------------------------------------
- 815915283247897734345611269596115894272000000000
-(1 row)
-</screen>
-
-So the parser does a type conversion on the operand and the query
-is equivalent to:
-
-<screen>
-SELECT CAST(40 AS bigint) ! AS "40 factorial";
-</screen>
-</para>
-</example>
-
-<example>
-<title>String Concatenation Operator Type Resolution</title>
-
-<para>
-A string-like syntax is used for working with string types and for
-working with complex extension types.
-Strings with unspecified type are matched with likely operator candidates.
-</para>
-
-<para>
-An example with one unspecified argument:
-<screen>
-SELECT text 'abc' || 'def' AS "text and unknown";
-
- text and unknown
-------------------
- abcdef
-(1 row)
-</screen>
-</para>
-
-<para>
-In this case the parser looks to see if there is an operator taking <type>text</type>
-for both arguments. Since there is, it assumes that the second argument should
-be interpreted as type <type>text</type>.
-</para>
-
-<para>
-Here is a concatenation on unspecified types:
-<screen>
-SELECT 'abc' || 'def' AS "unspecified";
-
- unspecified
--------------
- abcdef
-(1 row)
-</screen>
-</para>
-
-<para>
-In this case there is no initial hint for which type to use, since no types
-are specified in the query. So, the parser looks for all candidate operators
-and finds that there are candidates accepting both string-category and
-bit-string-category inputs.  Since string category is preferred when available,
-that category is selected, and then the
-preferred type for strings, <type>text</type>, is used as the specific
-type to resolve the unknown literals as.
-</para>
-</example>
-
-<example>
-<title>Absolute-Value and Negation Operator Type Resolution</title>
-
-<para>
-<!## PG>
-The <productname>PostgreSQL</productname> operator catalog has several
-entries for the prefix operator <literal>@</>, all of which implement
-absolute-value operations for various numeric data types.  One of these
-entries is for type <type>float8</type>, which is the preferred type in
-the numeric category.  Therefore, <productname>PostgreSQL</productname>
-will use that entry when faced with an <type>unknown</> input:
-<!## end>
-<!## XC>
-The <productname>Postgres-XC</productname> operator catalog has several
-entries for the prefix operator <literal>@</>, all of which implement
-absolute-value operations for various numeric data types.  One of these
-entries is for type <type>float8</type>, which is the preferred type in
-the numeric category.  Therefore, <productname>Postgres-XC</productname>
-will use that entry when faced with an <type>unknown</> input:
-<!## end>
-<!## XL>
-The <productname>Postgres-XL</productname> operator catalog has several
-entries for the prefix operator <literal>@</>, all of which implement
-absolute-value operations for various numeric data types.  One of these
-entries is for type <type>float8</type>, which is the preferred type in
-the numeric category.  Therefore, <productname>Postgres-XL</productname>
-will use that entry when faced with an <type>unknown</> input:
-<!## end>
-<screen>
-SELECT @ '-4.5' AS "abs";
- abs
------
- 4.5
-(1 row)
-</screen>
-Here the system has implicitly resolved the unknown-type literal as type
-<type>float8</type> before applying the chosen operator.  We can verify that
-<type>float8</type> and not some other type was used:
-<screen>
-SELECT @ '-4.5e500' AS "abs";
-
-ERROR:  "-4.5e500" is out of range for type double precision
-</screen>
-</para>
-
-<para>
-On the other hand, the prefix operator <literal>~</> (bitwise negation)
-is defined only for integer data types, not for <type>float8</type>.  So, if we
-try a similar case with <literal>~</>, we get:
-<screen>
-SELECT ~ '20' AS "negation";
-
-ERROR:  operator is not unique: ~ "unknown"
-HINT:  Could not choose a best candidate operator. You might need to add
-explicit type casts.
-</screen>
-This happens because the system cannot decide which of the several
-possible <literal>~</> operators should be preferred.  We can help
-it out with an explicit cast:
-<screen>
-SELECT ~ CAST('20' AS int8) AS "negation";
-
- negation
-----------
-      -21
-(1 row)
-</screen>
-</para>
-</example>
-
-</sect1>
-
-<sect1 id="typeconv-func">
-<title>Functions</title>
-
-<indexterm zone="typeconv-func">
- <primary>function</primary>
- <secondary>type resolution in an invocation</secondary>
-</indexterm>
-&common;
-  <para>
-   The specific function that is referenced by a function call
-   is determined using the following procedure.
-  </para>
-
-<procedure>
-<title>Function Type Resolution</title>
-
-<step performance="required">
-<para>
-Select the functions to be considered from the
-<classname>pg_proc</classname> system catalog.  If a non-schema-qualified
-function name was used, the functions
-considered are those with the matching name and argument count that are
-visible in the current search path (see <xref linkend="ddl-schemas-path">).
-If a qualified function name was given, only functions in the specified
-schema are considered.
-</para>
-
-<substeps>
-<step performance="optional">
-<para>
-If the search path finds multiple functions of identical argument types,
-only the one appearing earliest in the path is considered.  Functions of
-different argument types are considered on an equal footing regardless of
-search path position.
-</para>
-</step>
-<step performance="optional">
-<para>
-If a function is declared with a <literal>VARIADIC</> array parameter, and
-the call does not use the <literal>VARIADIC</> keyword, then the function
-is treated as if the array parameter were replaced by one or more occurrences
-of its element type, as needed to match the call.  After such expansion the
-function might have effective argument types identical to some non-variadic
-function.  In that case the function appearing earlier in the search path is
-used, or if the two functions are in the same schema, the non-variadic one is
-preferred.
-</para>
-</step>
-<step performance="optional">
-<para>
-Functions that have default values for parameters are considered to match any
-call that omits zero or more of the defaultable parameter positions.  If more
-than one such function matches a call, the one appearing earliest in the
-search path is used.  If there are two or more such functions in the same
-schema with identical parameter types in the non-defaulted positions (which is
-possible if they have different sets of defaultable parameters), the system
-will not be able to determine which to prefer, and so an <quote>ambiguous
-function call</> error will result if no better match to the call can be
-found.
-</para>
-</step>
-</substeps>
-</step>
-
-<step performance="required">
-<para>
-Check for a function accepting exactly the input argument types.
-If one exists (there can be only one exact match in the set of
-functions considered), use it.
-(Cases involving <type>unknown</type> will never find a match at
-this step.)
-</para>
-</step>
-
-<step performance="required">
-<para>
-If no exact match is found, see if the function call appears
-to be a special type conversion request.  This happens if the function call
-has just one argument and the function name is the same as the (internal)
-name of some data type.  Furthermore, the function argument must be either
-an unknown-type literal, or a type that is binary-coercible to the named
-data type, or a type that could be converted to the named data type by
-applying that type's I/O functions (that is, the conversion is either to or
-from one of the standard string types).  When these conditions are met,
-the function call is treated as a form of <literal>CAST</> specification.
-  <footnote>
-   <para>
-    The reason for this step is to support function-style cast specifications
-    in cases where there is not an actual cast function.  If there is a cast
-    function, it is conventionally named after its output type, and so there
-    is no need to have a special case.  See
-    <xref linkend="sql-createcast">
-    for additional commentary.
-   </para>
-  </footnote>
-</para>
-</step>
-<step performance="required">
-<para>
-Look for the best match.
-</para>
-<substeps>
-<step performance="required">
-<para>
-Discard candidate functions for which the input types do not match
-and cannot be converted (using an implicit conversion) to match.
-<type>unknown</type> literals are
-assumed to be convertible to anything for this purpose.  If only one
-candidate remains, use it; else continue to the next step.
-</para>
-</step>
-<step performance="required">
-<para>
-Run through all candidates and keep those with the most exact matches
-on input types.  (Domains are considered the same as their base type
-for this purpose.)  Keep all candidates if none have exact matches.
-If only one candidate remains, use it; else continue to the next step.
-</para>
-</step>
-<step performance="required">
-<para>
-Run through all candidates and keep those that accept preferred types (of the
-input data type's type category) at the most positions where type conversion
-will be required.
-Keep all candidates if none accept preferred types.
-If only one candidate remains, use it; else continue to the next step.
-</para>
-</step>
-<step performance="required">
-<para>
-If any input arguments are <type>unknown</type>, check the type categories
-accepted
-at those argument positions by the remaining candidates.  At each position,
-select the <type>string</type> category if any candidate accepts that category.
-(This bias towards string
-is appropriate since an unknown-type literal looks like a string.)
-Otherwise, if all the remaining candidates accept the same type category,
-select that category; otherwise fail because
-the correct choice cannot be deduced without more clues.
-Now discard candidates that do not accept the selected type category.
-Furthermore, if any candidate accepts a preferred type in that category,
-discard candidates that accept non-preferred types for that argument.
-</para>
-</step>
-<step performance="required">
-<para>
-If only one candidate remains, use it.  If no candidate or more than one
-candidate remains,
-then fail.
-</para>
-</step>
-</substeps>
-</step>
-</procedure>
-
-<para>
-Note that the <quote>best match</> rules are identical for operator and
-function type resolution.
-Some examples follow.
-</para>
-
-<example>
-<title>Rounding Function Argument Type Resolution</title>
-
-<para>
-There is only one <function>round</function> function that takes two
-arguments; it takes a first argument of type <type>numeric</type> and
-a second argument of type <type>integer</type>.
-So the following query automatically converts
-the first argument of type <type>integer</type> to
-<type>numeric</type>:
-
-<screen>
-SELECT round(4, 4);
-
- round
---------
- 4.0000
-(1 row)
-</screen>
-
-That query is actually transformed by the parser to:
-<screen>
-SELECT round(CAST (4 AS numeric), 4);
-</screen>
-</para>
-
-<para>
-Since numeric constants with decimal points are initially assigned the
-type <type>numeric</type>, the following query will require no type
-conversion and therefore might be slightly more efficient:
-<screen>
-SELECT round(4.0, 4);
-</screen>
-</para>
-</example>
-
-<example>
-<title>Substring Function Type Resolution</title>
-
-<para>
-There are several <function>substr</function> functions, one of which
-takes types <type>text</type> and <type>integer</type>.  If called
-with a string constant of unspecified type, the system chooses the
-candidate function that accepts an argument of the preferred category
-<literal>string</literal> (namely of type <type>text</type>).
-
-<screen>
-SELECT substr('1234', 3);
-
- substr
---------
-     34
-(1 row)
-</screen>
-</para>
-
-<para>
-If the string is declared to be of type <type>varchar</type>, as might be the case
-if it comes from a table, then the parser will try to convert it to become <type>text</type>:
-<screen>
-SELECT substr(varchar '1234', 3);
-
- substr
---------
-     34
-(1 row)
-</screen>
-
-This is transformed by the parser to effectively become:
-<screen>
-SELECT substr(CAST (varchar '1234' AS text), 3);
-</screen>
-</para>
-<para>
-<note>
-<para>
-The parser learns from the <structname>pg_cast</> catalog that
-<type>text</type> and <type>varchar</type>
-are binary-compatible, meaning that one can be passed to a function that
-accepts the other without doing any physical conversion.  Therefore, no
-type conversion call is really inserted in this case.
-</para>
-</note>
-</para>
-
-<para>
-And, if the function is called with an argument of type <type>integer</type>,
-the parser will try to convert that to <type>text</type>:
-<screen>
-SELECT substr(1234, 3);
-ERROR:  function substr(integer, integer) does not exist
-HINT:  No function matches the given name and argument types. You might need
-to add explicit type casts.
-</screen>
-
-This does not work because <type>integer</> does not have an implicit cast
-to <type>text</>.  An explicit cast will work, however:
-<screen>
-SELECT substr(CAST (1234 AS text), 3);
-
- substr
---------
-     34
-(1 row)
-</screen>
-</para>
-</example>
-
-</sect1>
-
-<sect1 id="typeconv-query">
-<title>Value Storage</title>
-&common;
-  <para>
-   Values to be inserted into a table are converted to the destination
-   column's data type according to the
-   following steps.
-  </para>
-
-<procedure>
-<title>Value Storage Type Conversion</title>
-
-<step performance="required">
-<para>
-Check for an exact match with the target.
-</para>
-</step>
-
-<step performance="required">
-<para>
-Otherwise, try to convert the expression to the target type.  This will succeed
-if there is a registered cast between the two types.
-If the expression is an unknown-type literal, the contents of
-the literal string will be fed to the input conversion routine for the target
-type.
-</para>
-</step>
-
-<step performance="required">
-<para>
-Check to see if there is a sizing cast for the target type.  A sizing
-cast is a cast from that type to itself.  If one is found in the
-<structname>pg_cast</> catalog, apply it to the expression before storing
-into the destination column.  The implementation function for such a cast
-always takes an extra parameter of type <type>integer</type>, which receives
-the destination column's declared length (actually, its
-<structfield>atttypmod</> value; the interpretation of
-<structfield>atttypmod</> varies for different data types).  The cast function
-is responsible for applying any length-dependent semantics such as size
-checking or truncation.
-</para>
-</step>
-
-</procedure>
-
-<example>
-<title><type>character</type> Storage Type Conversion</title>
-
-<para>
-For a target column declared as <type>character(20)</type> the following statement
-ensures that the stored value is sized correctly:
-
-<screen>
-CREATE TABLE vv (v character(20));
-INSERT INTO vv SELECT 'abc' || 'def';
-SELECT v, length(v) FROM vv;
-
-          v           | length
-----------------------+--------
- abcdef               |     20
-(1 row)
-</screen>
-</para>
-
-<para>
-What has really happened here is that the two unknown literals are resolved
-to <type>text</type> by default, allowing the <literal>||</literal> operator
-to be resolved as <type>text</type> concatenation.  Then the <type>text</type>
-result of the operator is converted to <type>bpchar</type> (<quote>blank-padded
-char</>, the internal name of the <type>character</type> data type) to match the target
-column type.  (Since the conversion from <type>text</type> to
-<type>bpchar</type> is binary-coercible, this conversion does
-not insert any real function call.)  Finally, the sizing function
-<literal>bpchar(bpchar, integer)</literal> is found in the system catalog
-and applied to the operator's result and the stored column length.  This
-type-specific function performs the required length check and addition of
-padding spaces.
-</para>
-</example>
-</sect1>
-
-<sect1 id="typeconv-union-case">
-<title><literal>UNION</literal>, <literal>CASE</literal>, and Related Constructs</title>
-
-<indexterm zone="typeconv-union-case">
- <primary>UNION</primary>
- <secondary>determination of result type</secondary>
-</indexterm>
-
-<indexterm zone="typeconv-union-case">
- <primary>CASE</primary>
- <secondary>determination of result type</secondary>
-</indexterm>
-
-<indexterm zone="typeconv-union-case">
- <primary>ARRAY</primary>
- <secondary>determination of result type</secondary>
-</indexterm>
-
-<indexterm zone="typeconv-union-case">
- <primary>VALUES</primary>
- <secondary>determination of result type</secondary>
-</indexterm>
-
-<indexterm zone="typeconv-union-case">
- <primary>GREATEST</primary>
- <secondary>determination of result type</secondary>
-</indexterm>
-
-<indexterm zone="typeconv-union-case">
- <primary>LEAST</primary>
- <secondary>determination of result type</secondary>
-</indexterm>
-&common;
-<para>
-SQL <literal>UNION</> constructs must match up possibly dissimilar
-types to become a single result set.  The resolution algorithm is
-applied separately to each output column of a union query.  The
-<literal>INTERSECT</> and <literal>EXCEPT</> constructs resolve
-dissimilar types in the same way as <literal>UNION</>.  The
-<literal>CASE</>, <literal>ARRAY</>, <literal>VALUES</>,
-<function>GREATEST</> and <function>LEAST</> constructs use the identical
-algorithm to match up their component expressions and select a result
-data type.
-</para>
-
-<procedure>
-<title>Type Resolution for <literal>UNION</literal>, <literal>CASE</literal>,
-and Related Constructs</title>
-
-<step performance="required">
-<para>
-If all inputs are of the same type, and it is not <type>unknown</type>,
-resolve as that type.  Otherwise, replace any domain types in the list with
-their underlying base types.
-</para>
-</step>
-
-<step performance="required">
-<para>
-If all inputs are of type <type>unknown</type>, resolve as type
-<type>text</type> (the preferred type of the string category).
-Otherwise, <type>unknown</type> inputs are ignored.
-</para>
-</step>
-
-<step performance="required">
-<para>
-If the non-unknown inputs are not all of the same type category, fail.
-</para>
-</step>
-
-<step performance="required">
-<para>
-Choose the first non-unknown input type which is a preferred type in
-that category, if there is one.
-</para>
-</step>
-
-<step performance="required">
-<para>
-Otherwise, choose the last non-unknown input type that allows all the
-preceding non-unknown inputs to be implicitly converted to it.  (There
-always is such a type, since at least the first type in the list must
-satisfy this condition.)
-</para>
-</step>
-
-<step performance="required">
-<para>
-Convert all inputs to the selected type.  Fail if there is not a
-conversion from a given input to the selected type.
-</para>
-</step>
-</procedure>
-
-<para>
-Some examples follow.
-</para>
-
-<example>
-<title>Type Resolution with Underspecified Types in a Union</title>
-
-<para>
-<screen>
-SELECT text 'a' AS "text" UNION SELECT 'b';
-
- text
-------
- a
- b
-(2 rows)
-</screen>
-Here, the unknown-type literal <literal>'b'</literal> will be resolved to type <type>text</type>.
-</para>
-</example>
-
-<example>
-<title>Type Resolution in a Simple Union</title>
-
-<para>
-<screen>
-SELECT 1.2 AS "numeric" UNION SELECT 1;
-
- numeric
----------
-       1
-     1.2
-(2 rows)
-</screen>
-The literal <literal>1.2</> is of type <type>numeric</>,
-and the <type>integer</type> value <literal>1</> can be cast implicitly to
-<type>numeric</>, so that type is used.
-</para>
-</example>
-
-<example>
-<title>Type Resolution in a Transposed Union</title>
-
-<para>
-<screen>
-SELECT 1 AS "real" UNION SELECT CAST('2.2' AS REAL);
-
- real
-------
-    1
-  2.2
-(2 rows)
-</screen>
-Here, since type <type>real</> cannot be implicitly cast to <type>integer</>,
-but <type>integer</> can be implicitly cast to <type>real</>, the union
-result type is resolved as <type>real</>.
-</para>
-</example>
-
-</sect1>
-</chapter>
diff --git a/doc-xc/src/sgml/unaccent.sgmlin b/doc-xc/src/sgml/unaccent.sgmlin
deleted file mode 100644
index c8982d7b64..0000000000
--- a/doc-xc/src/sgml/unaccent.sgmlin
+++ /dev/null
@@ -1,170 +0,0 @@
-<!-- doc/src/sgml/unaccent.sgml -->
-
-<sect1 id="unaccent" xreflabel="unaccent">
- <title>unaccent</title>
-
- <indexterm zone="unaccent">
-  <primary>unaccent</primary>
- </indexterm>
-
-&common;
-
- <para>
-  <filename>unaccent</> is a text search dictionary that removes accents
-  (diacritic signs) from lexemes.
-  It's a filtering dictionary, which means its output is
-  always passed to the next dictionary (if any), unlike the normal
-  behavior of dictionaries.  This allows accent-insensitive processing
-  for full text search.
- </para>
-
- <para>
-  The current implementation of <filename>unaccent</> cannot be used as a
-  normalizing dictionary for the <filename>thesaurus</filename> dictionary.
- </para>
-
- <sect2>
-  <title>Configuration</title>
-
-&common;
-  <para>
-   An <literal>unaccent</> dictionary accepts the following options:
-  </para>
-  <itemizedlist>
-   <listitem>
-    <para>
-     <literal>RULES</> is the base name of the file containing the list of
-     translation rules.  This file must be stored in
-     <filename>$SHAREDIR/tsearch_data/</> (where <literal>$SHAREDIR</> means
-<!## PG>
-     the <productname>PostgreSQL</> installation's shared-data directory).
-<!## end>
-<!## XC>
-     the <productname>Postgres-XC</> installation's shared-data directory).
-<!## end>
-<!## XL>
-     the <productname>Postgres-XL</> installation's shared-data directory).
-<!## end>
-     Its name must end in <literal>.rules</> (which is not to be included in
-     the <literal>RULES</> parameter).
-    </para>
-   </listitem>
-  </itemizedlist>
-  <para>
-   The rules file has the following format:
-  </para>
-  <itemizedlist>
-   <listitem>
-    <para>
-     Each line represents a pair, consisting of a character with accent
-     followed by a character without accent.  The first is translated into
-     the second.  For example,
-<programlisting>
-&Agrave;        A
-&Aacute;        A
-&Acirc;        A
-&Atilde;        A
-&Auml;        A
-&Aring;        A
-&AElig;        A
-</programlisting>
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   A more complete example, which is directly useful for most European
-   languages, can be found in <filename>unaccent.rules</>, which is installed
-   in <filename>$SHAREDIR/tsearch_data/</> when the <filename>unaccent</>
-   module is installed.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Usage</title>
-
-&common;
-  <para>
-   Installing the <literal>unaccent</> extension creates a text
-   search template <literal>unaccent</> and a dictionary <literal>unaccent</>
-   based on it.  The <literal>unaccent</> dictionary has the default
-   parameter setting <literal>RULES='unaccent'</>, which makes it immediately
-   usable with the standard <filename>unaccent.rules</> file.
-   If you wish, you can alter the parameter, for example
-
-<programlisting>
-mydb=# ALTER TEXT SEARCH DICTIONARY unaccent (RULES='my_rules');
-</programlisting>
-
-   or create new dictionaries based on the template.
-  </para>
-
-  <para>
-   To test the dictionary, you can try:
-<programlisting>
-mydb=# select ts_lexize('unaccent','H&ocirc;tel');
- ts_lexize
------------
- {Hotel}
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-   Here is an example showing how to insert the
-   <filename>unaccent</> dictionary into a text search configuration:
-<programlisting>
-mydb=# CREATE TEXT SEARCH CONFIGURATION fr ( COPY = french );
-mydb=# ALTER TEXT SEARCH CONFIGURATION fr
-        ALTER MAPPING FOR hword, hword_part, word
-        WITH unaccent, french_stem;
-mydb=# select to_tsvector('fr','H&ocirc;tels de la Mer');
-    to_tsvector
--------------------
- 'hotel':1 'mer':4
-(1 row)
-
-mydb=# select to_tsvector('fr','H&ocirc;tel de la Mer') @@ to_tsquery('fr','Hotels');
- ?column?
-----------
- t
-(1 row)
-
-mydb=# select ts_headline('fr','H&ocirc;tel de la Mer',to_tsquery('fr','Hotels'));
-      ts_headline
-------------------------
- &lt;b&gt;H&ocirc;tel&lt;/b&gt; de la Mer
-(1 row)
-</programlisting>
-  </para>
- </sect2>
-
- <sect2>
- <title>Functions</title>
-
-&common;
- <para>
-  The <function>unaccent()</> function removes accents (diacritic signs) from
-  a given string.  Basically, it's a wrapper around the
-  <filename>unaccent</> dictionary, but it can be used outside normal
-  text search contexts.
- </para>
-
- <indexterm>
-  <primary>unaccent</primary>
- </indexterm>
-
-<synopsis>
-unaccent(<optional><replaceable class="PARAMETER">dictionary</replaceable>, </optional> <replaceable class="PARAMETER">string</replaceable>) returns <type>text</type>
-</synopsis>
-
- <para>
-  For example:
-<programlisting>
-SELECT unaccent('unaccent', 'H&ocirc;tel');
-SELECT unaccent('H&ocirc;tel');
-</programlisting>
- </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/user-manag.sgmlin b/doc-xc/src/sgml/user-manag.sgmlin
deleted file mode 100644
index 2f469945e3..0000000000
--- a/doc-xc/src/sgml/user-manag.sgmlin
+++ /dev/null
@@ -1,497 +0,0 @@
-<!-- doc/src/sgml/user-manag.sgml -->
-
-<chapter id="user-manag">
- <title>Database Roles</title>
-
-&common;
-
- <para>
-<!## PG>
-  <productname>PostgreSQL</productname> manages database access permissions
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> manages database access permissions
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> manages database access permissions
-<!## end>
-  using the concept of <firstterm>roles</>.  A role can be thought of as
-  either a database user, or a group of database users, depending on how
-  the role is set up.  Roles can own database objects (for example,
-  tables) and can assign privileges on those objects to other roles to
-  control who has access to which objects.  Furthermore, it is possible
-  to grant <firstterm>membership</> in a role to another role, thus
-  allowing the member role to use privileges assigned to another role.
- </para>
-
- <para>
-  The concept of roles subsumes the concepts of <quote>users</> and
-<!## PG>
-  <quote>groups</>.  In <productname>PostgreSQL</productname> versions
-<!## end>
-<!## XC>
-  <quote>groups</>.  In <productname>Postgres-XC</productname> versions
-<!## end>
-<!## XL>
-  <quote>groups</>.  In <productname>Postgres-XL</productname> versions
-<!## end>
-  before 8.1, users and groups were distinct kinds of entities, but now
-  there are only roles.  Any role can act as a user, a group, or both.
- </para>
-
- <para>
-  This chapter describes how to create and manage roles.
-  More information about the effects of role privileges on various
-  database objects can be found in <xref linkend="ddl-priv">.
- </para>
-
- <sect1 id="database-roles">
-  <title>Database Roles</title>
-
-  <indexterm zone="database-roles">
-   <primary>role</primary>
-  </indexterm>
-
-  <indexterm zone="database-roles">
-   <primary>user</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>CREATE ROLE</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>DROP ROLE</primary>
-  </indexterm>
-&common;
-  <para>
-   Database roles are conceptually completely separate from
-   operating system users. In practice it might be convenient to
-   maintain a correspondence, but this is not required. Database roles
-   are global across a database cluster installation (and not
-   per individual database). To create a role use the <xref
-   linkend="sql-createrole"> SQL command:
-<synopsis>
-CREATE ROLE <replaceable>name</replaceable>;
-</synopsis>
-   <replaceable>name</replaceable> follows the rules for SQL
-   identifiers: either unadorned without special characters, or
-   double-quoted.  (In practice, you will usually want to add additional
-   options, such as <literal>LOGIN</>, to the command.  More details appear
-   below.)  To remove an existing role, use the analogous
-   <xref linkend="sql-droprole"> command:
-<synopsis>
-DROP ROLE <replaceable>name</replaceable>;
-</synopsis>
-  </para>
-
-  <indexterm>
-   <primary>createuser</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>dropuser</primary>
-  </indexterm>
-
-  <para>
-   For convenience, the programs <xref linkend="app-createuser">
-   and <xref linkend="app-dropuser"> are provided as wrappers
-   around these SQL commands that can be called from the shell command
-   line:
-<synopsis>
-createuser <replaceable>name</replaceable>
-dropuser <replaceable>name</replaceable>
-</synopsis>
-  </para>
-
-  <para>
-   To determine the set of existing roles, examine the <structname>pg_roles</>
-   system catalog, for example
-<synopsis>
-SELECT rolname FROM pg_roles;
-</synopsis>
-   The <xref linkend="app-psql"> program's <literal>\du</> meta-command
-   is also useful for listing the existing roles.
-  </para>
-
-  <para>
-   In order to bootstrap the database system, a freshly initialized
-   system always contains one predefined role. This role is always
-   a <quote>superuser</>, and by default (unless altered when running
-   <command>initdb</command>) it will have the same name as the
-   operating system user that initialized the database
-   cluster. Customarily, this role will be named
-   <literal>postgres</literal>. In order to create more roles you
-   first have to connect as this initial role.
-  </para>
-
-  <para>
-   Every connection to the database server is made using the name of some
-   particular role, and this role determines the initial access privileges for
-   commands issued in that connection.
-   The role name to use for a particular database
-   connection is indicated by the client that is initiating the
-   connection request in an application-specific fashion. For example,
-   the <command>psql</command> program uses the
-   <option>-U</option> command line option to indicate the role to
-   connect as.  Many applications assume the name of the current
-   operating system user by default (including
-   <command>createuser</> and <command>psql</>).  Therefore it
-   is often convenient to maintain a naming correspondence between
-   roles and operating system users.
-  </para>
-
-  <para>
-   The set of database roles a given client connection can connect as
-   is determined by the client authentication setup, as explained in
-   <xref linkend="client-authentication">. (Thus, a client is not
-   limited to connect as the role matching
-   its operating system user, just as a person's login name
-   need not match her real name.)  Since the role
-   identity determines the set of privileges available to a connected
-   client, it is important to carefully configure privileges when setting up
-   a multiuser environment.
-  </para>
- </sect1>
-
- <sect1 id="role-attributes">
-  <title>Role Attributes</title>
-&common;
-   <para>
-    A database role can have a number of attributes that define its
-    privileges and interact with the client authentication system.
-
-    <variablelist>
-     <varlistentry>
-      <term>login privilege<indexterm><primary>login privilege</></></term>
-      <listitem>
-       <para>
-        Only roles that have the <literal>LOGIN</> attribute can be used
-        as the initial role name for a database connection.  A role with
-        the <literal>LOGIN</> attribute can be considered the same
-        as a <quote>database user</>.  To create a role with login privilege,
-        use either:
-<programlisting>
-CREATE ROLE <replaceable>name</replaceable> LOGIN;
-CREATE USER <replaceable>name</replaceable>;
-</programlisting>
-        (<command>CREATE USER</> is equivalent to <command>CREATE ROLE</>
-        except that <command>CREATE USER</> assumes <literal>LOGIN</> by
-        default, while <command>CREATE ROLE</> does not.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>superuser status<indexterm><primary>superuser</></></term>
-      <listitem>
-       <para>
-        A database superuser bypasses all permission checks, except the right
-        to log in or the right to initiate replication.  This is a
-        dangerous privilege and should not be used carelessly; it is best
-        to do most of your work as a role that is not a superuser.
-        To create a new database superuser, use <literal>CREATE ROLE
-        <replaceable>name</replaceable> SUPERUSER</literal>.  You must do
-        this as a role that is already a superuser. Creating a superuser
-        will by default also grant permissions to initiate streaming
-        replication. For increased security this can be disallowed using
-        <literal>CREATE ROLE <replaceable>name</replaceable> SUPERUSER
-        NOREPLICATION</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>database creation<indexterm><primary>database</><secondary>privilege to create</></></term>
-      <listitem>
-       <para>
-        A role must be explicitly given permission to create databases
-        (except for superusers, since those bypass all permission
-        checks). To create such a role, use <literal>CREATE ROLE
-        <replaceable>name</replaceable> CREATEDB</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>role creation<indexterm><primary>role</><secondary>privilege to create</></></term>
-      <listitem>
-       <para>
-        A role must be explicitly given permission to create more roles
-        (except for superusers, since those bypass all permission
-        checks). To create such a role, use <literal>CREATE ROLE
-        <replaceable>name</replaceable> CREATEROLE</literal>.
-        A role with <literal>CREATEROLE</> privilege can alter and drop
-        other roles, too, as well as grant or revoke membership in them.
-        However, to create, alter, drop, or change membership of a
-        superuser role, superuser status is required;
-        <literal>CREATEROLE</> is insufficient for that.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>initiating replication<indexterm><primary>role</><secondary>privilege to initiate replication</></></term>
-      <listitem>
-       <para>
-        A role must explicitly be given permission to initiate streaming
-        replication. A role used for streaming replication must always
-        have <literal>LOGIN</> permission as well. To create such a role, use
-        <literal>CREATE ROLE <replaceable>name</replaceable> REPLICATION
-        LOGIN</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>password<indexterm><primary>password</></></term>
-      <listitem>
-       <para>
-        A password is only significant if the client authentication
-        method requires the user to supply a password when connecting
-        to the database. The <option>password</> and
-        <option>md5</> authentication methods
-        make use of passwords. Database passwords are separate from
-        operating system passwords. Specify a password upon role
-        creation with <literal>CREATE ROLE
-        <replaceable>name</replaceable> PASSWORD '<replaceable>string</>'</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    A role's attributes can be modified after creation with
-    <command>ALTER ROLE</command>.<indexterm><primary>ALTER ROLE</></>
-    See the reference pages for the <xref linkend="sql-createrole"
-   > and <xref linkend="sql-alterrole"
-   > commands for details.
-   </para>
-
-  <tip>
-   <para>
-    It is good practice to create a role that has the <literal>CREATEDB</>
-    and <literal>CREATEROLE</> privileges, but is not a superuser, and then
-    use this role for all routine management of databases and roles.  This
-    approach avoids the dangers of operating as a superuser for tasks that
-    do not really require it.
-   </para>
-  </tip>
-
-  <para>
-   A role can also have role-specific defaults for many of the run-time
-   configuration settings described in <xref
-   linkend="runtime-config">.  For example, if for some reason you
-   want to disable index scans (hint: not a good idea) anytime you
-   connect, you can use:
-<programlisting>
-ALTER ROLE myname SET enable_indexscan TO off;
-</programlisting>
-   This will save the setting (but not set it immediately).  In
-   subsequent connections by this role it will appear as though
-   <literal>SET enable_indexscan TO off</literal> had been executed
-   just before the session started.
-   You can still alter this setting during the session; it will only
-   be the default. To remove a role-specific default setting, use
-   <literal>ALTER ROLE <replaceable>rolename</> RESET <replaceable>varname</></literal>.
-   Note that role-specific defaults attached to roles without
-   <literal>LOGIN</> privilege are fairly useless, since they will never
-   be invoked.
-  </para>
- </sect1>
-
- <sect1 id="role-membership">
-  <title>Role Membership</title>
-
-  <indexterm zone="role-membership">
-   <primary>role</><secondary>membership in</>
-  </indexterm>
-&common;
-  <para>
-   It is frequently convenient to group users together to ease
-   management of privileges: that way, privileges can be granted to, or
-<!## PG>
-   revoked from, a group as a whole.  In <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   revoked from, a group as a whole.  In <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   revoked from, a group as a whole.  In <productname>Postgres-XL</productname>
-<!## end>
-   this is done by creating a role that represents the group, and then
-   granting <firstterm>membership</> in the group role to individual user
-   roles.
-  </para>
-
-  <para>
-   To set up a group role, first create the role:
-<synopsis>
-CREATE ROLE <replaceable>name</replaceable>;
-</synopsis>
-   Typically a role being used as a group would not have the <literal>LOGIN</>
-   attribute, though you can set it if you wish.
-  </para>
-
-  <para>
-   Once the group role exists, you can add and remove members using the
-   <xref linkend="sql-grant"> and
-   <xref linkend="sql-revoke"> commands:
-<synopsis>
-GRANT <replaceable>group_role</replaceable> TO <replaceable>role1</replaceable>, ... ;
-REVOKE <replaceable>group_role</replaceable> FROM <replaceable>role1</replaceable>, ... ;
-</synopsis>
-   You can grant membership to other group roles, too (since there isn't
-   really any distinction between group roles and non-group roles).  The
-   database will not let you set up circular membership loops.  Also,
-   it is not permitted to grant membership in a role to
-   <literal>PUBLIC</literal>.
-  </para>
-
-  <para>
-   The members of a group role can use the privileges of the role in two
-   ways.  First, every member of a group can explicitly do
-   <xref linkend="sql-set-role"> to
-   temporarily <quote>become</> the group role.  In this state, the
-   database session has access to the privileges of the group role rather
-   than the original login role, and any database objects created are
-   considered owned by the group role not the login role.  Second, member
-   roles that have the <literal>INHERIT</> attribute automatically have use
-   of the privileges of roles of which they are members, including any
-   privileges inherited by those roles.
-   As an example, suppose we have done:
-<programlisting>
-CREATE ROLE joe LOGIN INHERIT;
-CREATE ROLE admin NOINHERIT;
-CREATE ROLE wheel NOINHERIT;
-GRANT admin TO joe;
-GRANT wheel TO admin;
-</programlisting>
-   Immediately after connecting as role <literal>joe</>, a database
-   session will have use of privileges granted directly to <literal>joe</>
-   plus any privileges granted to <literal>admin</>, because <literal>joe</>
-   <quote>inherits</> <literal>admin</>'s privileges.  However, privileges
-   granted to <literal>wheel</> are not available, because even though
-   <literal>joe</> is indirectly a member of <literal>wheel</>, the
-   membership is via <literal>admin</> which has the <literal>NOINHERIT</>
-   attribute.  After:
-<programlisting>
-SET ROLE admin;
-</programlisting>
-   the session would have use of only those privileges granted to
-   <literal>admin</>, and not those granted to <literal>joe</>.  After:
-<programlisting>
-SET ROLE wheel;
-</programlisting>
-   the session would have use of only those privileges granted to
-   <literal>wheel</>, and not those granted to either <literal>joe</>
-   or <literal>admin</>.  The original privilege state can be restored
-   with any of:
-<programlisting>
-SET ROLE joe;
-SET ROLE NONE;
-RESET ROLE;
-</programlisting>
-  </para>
-
-  <note>
-   <para>
-    The <command>SET ROLE</> command always allows selecting any role
-    that the original login role is directly or indirectly a member of.
-    Thus, in the above example, it is not necessary to become
-    <literal>admin</> before becoming <literal>wheel</>.
-   </para>
-  </note>
-
-  <note>
-   <para>
-    In the SQL standard, there is a clear distinction between users and roles,
-    and users do not automatically inherit privileges while roles do.  This
-<!## PG>
-    behavior can be obtained in <productname>PostgreSQL</productname> by giving
-<!## end>
-<!## XC>
-    behavior can be obtained in <productname>Postgres-XC</productname> by giving
-<!## end>
-<!## XL>
-    behavior can be obtained in <productname>Postgres-XL</productname> by giving
-<!## end>
-    roles being used as SQL roles the <literal>INHERIT</> attribute, while
-    giving roles being used as SQL users the <literal>NOINHERIT</> attribute.
-<!## PG>
-    However, <productname>PostgreSQL</productname> defaults to giving all roles
-<!## end>
-<!## XC>
-    However, <productname>Postgres-XC</productname> defaults to giving all roles
-<!## end>
-<!## XL>
-    However, <productname>Postgres-XL</productname> defaults to giving all roles
-<!## end>
-    the <literal>INHERIT</> attribute, for backward compatibility with pre-8.1
-    releases in which users always had use of permissions granted to groups
-    they were members of.
-   </para>
-  </note>
-
-  <para>
-   The role attributes <literal>LOGIN</>, <literal>SUPERUSER</>,
-   <literal>CREATEDB</>, and <literal>CREATEROLE</> can be thought of as
-   special privileges, but they are never inherited as ordinary privileges
-   on database objects are.  You must actually <command>SET ROLE</> to a
-   specific role having one of these attributes in order to make use of
-   the attribute.  Continuing the above example, we might choose to
-   grant <literal>CREATEDB</> and <literal>CREATEROLE</> to the
-   <literal>admin</> role.  Then a session connecting as role <literal>joe</>
-   would not have these privileges immediately, only after doing
-   <command>SET ROLE admin</>.
-  </para>
-
-  <para>
-  </para>
-
-  <para>
-   To destroy a group role, use <xref
-   linkend="sql-droprole">:
-<synopsis>
-DROP ROLE <replaceable>name</replaceable>;
-</synopsis>
-   Any memberships in the group role are automatically revoked (but the
-   member roles are not otherwise affected).  Note however that any objects
-   owned by the group role must first be dropped or reassigned to other
-   owners; and any permissions granted to the group role must be revoked.
-  </para>
- </sect1>
-
- <sect1 id="perm-functions">
-  <title>Function and Trigger Security</title>
-&common;
-  <para>
-   Functions and triggers allow users to insert code into the backend
-   server that other users might execute unintentionally. Hence, both
-   mechanisms permit users to <quote>Trojan horse</quote>
-   others with relative ease. The only real protection is tight
-   control over who can define functions.
-  </para>
-
-  <para>
-   Functions run inside the backend
-   server process with the operating system permissions of the
-   database server daemon.  If the programming language
-   used for the function allows unchecked memory accesses, it is
-   possible to change the server's internal data structures.
-   Hence, among many other things, such functions can circumvent any
-   system access controls.  Function languages that allow such access
-   are considered <quote>untrusted</>, and
-<!## PG>
-   <productname>PostgreSQL</productname> allows only superusers to
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> allows only superusers to
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> allows only superusers to
-<!## end>
-   create functions written in those languages.
-  </para>
- </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/uuid-ossp.sgmlin b/doc-xc/src/sgml/uuid-ossp.sgmlin
deleted file mode 100644
index 41d1f17a1e..0000000000
--- a/doc-xc/src/sgml/uuid-ossp.sgmlin
+++ /dev/null
@@ -1,178 +0,0 @@
-<!-- doc/src/sgml/uuid-ossp.sgml -->
-
-<sect1 id="uuid-ossp" xreflabel="uuid-ossp">
- <title>uuid-ossp</title>
-
- <indexterm zone="uuid-ossp">
-  <primary>uuid-ossp</primary>
- </indexterm>
-
-&pgnotice;
-
- <para>
-  The <filename>uuid-ossp</> module provides functions to generate universally
-  unique identifiers (UUIDs) using one of several standard algorithms.  There
-  are also functions to produce certain special UUID constants.
- </para>
-
- <para>
-  This module depends on the OSSP UUID library, which can be found at
-  <ulink url="http://www.ossp.org/pkg/lib/uuid/"></ulink>.
- </para>
-
- <sect2>
-  <title><literal>uuid-ossp</literal> Functions</title>
-
-&pgnotice;
-  <para>
-   <xref linkend="uuid-ossp-functions"> shows the functions available to
-   generate UUIDs.
-   The relevant standards ITU-T Rec. X.667, ISO/IEC 9834-8:2005, and RFC
-   4122 specify four algorithms for generating UUIDs, identified by the
-   version numbers 1, 3, 4, and 5.  (There is no version 2 algorithm.)
-   Each of these algorithms could be suitable for a different set of
-   applications.
-  </para>
-
-  <table id="uuid-ossp-functions">
-   <title>Functions for UUID Generation</title>
-   <tgroup cols="2">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><literal>uuid_generate_v1()</literal></entry>
-      <entry>
-       <para>
-        This function generates a version 1 UUID.  This involves the MAC
-        address of the computer and a time stamp.  Note that UUIDs of this
-        kind reveal the identity of the computer that created the identifier
-        and the time at which it did so, which might make it unsuitable for
-        certain security-sensitive applications.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><literal>uuid_generate_v1mc()</literal></entry>
-      <entry>
-       <para>
-        This function generates a version 1 UUID but uses a random multicast
-        MAC address instead of the real MAC address of the computer.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><literal>uuid_generate_v3(namespace uuid, name text)</literal></entry>
-      <entry>
-       <para>
-        This function generates a version 3 UUID in the given namespace using
-        the specified input name.  The namespace should be one of the special
-        constants produced by the <function>uuid_ns_*()</> functions shown
-        in <xref linkend="uuid-ossp-constants">.  (It could be any UUID in theory.)  The name is an identifier
-        in the selected namespace.
-       </para>
-
-       <para>
-        For example:
-
-<programlisting>
-SELECT uuid_generate_v3(uuid_ns_url(), 'http://www.postgresql.org');
-</programlisting>
-
-        The name parameter will be MD5-hashed, so the cleartext cannot be
-        derived from the generated UUID.
-        The generation of UUIDs by this method has no random or
-        environment-dependent element and is therefore reproducible.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><literal>uuid_generate_v4()</literal></entry>
-      <entry>
-       <para>
-        This function generates a version 4 UUID, which is derived entirely
-        from random numbers.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><literal>uuid_generate_v5(namespace uuid, name text)</literal></entry>
-      <entry>
-       <para>
-        This function generates a version 5 UUID, which works like a version 3
-        UUID except that SHA-1 is used as a hashing method.  Version 5 should
-        be preferred over version 3 because SHA-1 is thought to be more secure
-        than MD5.
-       </para>
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <table id="uuid-ossp-constants">
-   <title>Functions Returning UUID Constants</title>
-   <tgroup cols="2">
-    <tbody>
-     <row>
-      <entry><literal>uuid_nil()</literal></entry>
-      <entry>
-       <para>
-        A <quote>nil</> UUID constant, which does not occur as a real UUID.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><literal>uuid_ns_dns()</literal></entry>
-      <entry>
-       <para>
-        Constant designating the DNS namespace for UUIDs.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><literal>uuid_ns_url()</literal></entry>
-      <entry>
-       <para>
-        Constant designating the URL namespace for UUIDs.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><literal>uuid_ns_oid()</literal></entry>
-      <entry>
-       <para>
-        Constant designating the ISO object identifier (OID) namespace for
-        UUIDs.  (This pertains to ASN.1 OIDs, which are unrelated to the OIDs
-        used in <productname>PostgreSQL</>.)
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><literal>uuid_ns_x500()</literal></entry>
-      <entry>
-       <para>
-        Constant designating the X.500 distinguished name (DN) namespace for
-        UUIDs.
-       </para>
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Peter Eisentraut <email>[email protected]</email>
-  </para>
-
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/vacuumlo.sgmlin b/doc-xc/src/sgml/vacuumlo.sgmlin
deleted file mode 100644
index 23662cd212..0000000000
--- a/doc-xc/src/sgml/vacuumlo.sgmlin
+++ /dev/null
@@ -1,158 +0,0 @@
-<!-- doc/src/sgml/vacuumlo.sgml -->
-
-<sect1 id="vacuumlo" xreflabel="vacuumlo">
- <title>vacuumlo</title>
-
- <indexterm zone="vacuumlo">
-  <primary>vacuumlo</primary>
- </indexterm>
-
-<!## XC>
-&xconly;
-
- <para>
-  <application>vacuumlo</> has not been supported
-  by <productname>Postgres-XC</> at present.  This may be supported in
-  the future releases.
- </para>
-<!## end>
-<!## XL>
-&xlonly;
-
- <para>
-  <application>vacuumlo</> is not supported
-  by <productname>Postgres-XL</> at present.  This may be supported in
-  the future releases.
- </para>
-<!## end>
-
-<!## PG>
- <para>
-  <application>vacuumlo</> is a simple utility program that will remove any
-  <quote>orphaned</> large objects from a
-  <productname>PostgreSQL</> database.  An orphaned large object (LO) is
-  considered to be any LO whose OID does not appear in any <type>oid</> or
-  <type>lo</> data column of the database.
- </para>
-
- <para>
-  If you use this, you may also be interested in the <function>lo_manage</>
-  trigger in the <xref linkend="lo"> module.
-  <function>lo_manage</> is useful to try
-  to avoid creating orphaned LOs in the first place.
- </para>
-
- <sect2>
-  <title>Usage</title>
-
-<synopsis>
-vacuumlo [options] database [database2 ... databaseN]
-</synopsis>
-
-  <para>
-   All databases named on the command line are processed.  Available options
-   include:
-  </para>
-
-  <variablelist>
-   <varlistentry>
-    <term><option>-v</option></term>
-    <listitem>
-     <para>Write a lot of progress messages.</para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>-n</option></term>
-    <listitem>
-     <para>Don't remove anything, just show what would be done.</para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>-U</option> <replaceable>username</></term>
-    <listitem>
-     <para>User name to connect as.</para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>-w</></term>
-    <term><option>--no-password</></term>
-    <listitem>
-     <para>
-      Never issue a password prompt.  If the server requires password
-      authentication and a password is not available by other means
-      such as a <filename>.pgpass</filename> file, the connection
-      attempt will fail.  This option can be useful in batch jobs and
-      scripts where no user is present to enter a password.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>-W</option></term>
-    <listitem>
-     <para>
-      Force <application>vacuumlo</application> to prompt for a
-      password before connecting to a database.
-     </para>
-
-     <para>
-      This option is never essential, since
-      <application>vacuumlo</application> will automatically prompt
-      for a password if the server demands password authentication.
-      However, <application>vacuumlo</application> will waste a
-      connection attempt finding out that the server wants a password.
-      In some cases it is worth typing <option>-W</> to avoid the extra
-      connection attempt.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>-h</option> <replaceable>hostname</></term>
-    <listitem>
-     <para>Database server's host.</para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><option>-p</option> <replaceable>port</></term>
-    <listitem>
-     <para>Database server's port.</para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </sect2>
-
- <sect2>
-  <title>Method</title>
-
-  <para>
-   First, it builds a temporary table which contains all of the OIDs of the
-   large objects in that database.
-  </para>
-
-  <para>
-   It then scans through all columns in the database that are of type
-   <type>oid</> or <type>lo</>, and removes matching entries from the
-  temporary table.
-  </para>
-
-  <para>
-   The remaining entries in the temp table identify orphaned LOs.
-   These are removed.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   Peter Mount <email>[email protected]</email>
-  </para>
- </sect2>
-<!## end>
-
-</sect1>
diff --git a/doc-xc/src/sgml/version.sgmlin b/doc-xc/src/sgml/version.sgmlin
deleted file mode 100644
index 213d6a0fc4..0000000000
--- a/doc-xc/src/sgml/version.sgmlin
+++ /dev/null
@@ -1,2 +0,0 @@
-<!entity version "9.2">
-<!entity majorversion "9.2">
diff --git a/doc-xc/src/sgml/wal.sgmlin b/doc-xc/src/sgml/wal.sgmlin
deleted file mode 100644
index bd3ab6c564..0000000000
--- a/doc-xc/src/sgml/wal.sgmlin
+++ /dev/null
@@ -1,905 +0,0 @@
-<!-- doc/src/sgml/wal.sgml -->
-
-<chapter id="wal">
- <title>Reliability and the Write-Ahead Log</title>
-
-&common;
-
- <para>
-  This chapter explains how the Write-Ahead Log is used to obtain
-  efficient, reliable operation.
- </para>
-
- <sect1 id="wal-reliability">
-  <title>Reliability</title>
-&common;
-
-  <para>
-   Reliability is an important property of any serious database
-<!## PG>
-   system, and <productname>PostgreSQL</> does everything possible to
-<!## end>
-<!## XC>
-   system, and <productname>Postgres-XC</> does everything possible to
-<!## end>
-<!## XL>
-   system, and <productname>Postgres-XL</> does everything possible to
-<!## end>
-   guarantee reliable operation. One aspect of reliable operation is
-   that all data recorded by a committed transaction should be stored
-   in a nonvolatile area that is safe from power loss, operating
-   system failure, and hardware failure (except failure of the
-   nonvolatile area itself, of course).  Successfully writing the data
-   to the computer's permanent storage (disk drive or equivalent)
-   ordinarily meets this requirement.  In fact, even if a computer is
-   fatally damaged, if the disk drives survive they can be moved to
-   another computer with similar hardware and all committed
-   transactions will remain intact.
-  </para>
-
-  <para>
-   While forcing data to the disk platters periodically might seem like
-   a simple operation, it is not. Because disk drives are dramatically
-   slower than main memory and CPUs, several layers of caching exist
-   between the computer's main memory and the disk platters.
-   First, there is the operating system's buffer cache, which caches
-   frequently requested disk blocks and combines disk writes. Fortunately,
-   all operating systems give applications a way to force writes from
-<!## PG>
-   the buffer cache to disk, and <productname>PostgreSQL</> uses those
-<!## end>
-<!## XC>
-   the buffer cache to disk, and <productname>Postgres-XC</> uses those
-<!## end>
-<!## XL>
-   the buffer cache to disk, and <productname>Postgres-XL</> uses those
-<!## end>
-   features.  (See the <xref linkend="guc-wal-sync-method"> parameter
-   to adjust how this is done.)
-  </para>
-
-  <para>
-   Next, there might be a cache in the disk drive controller; this is
-   particularly common on <acronym>RAID</> controller cards. Some of
-   these caches are <firstterm>write-through</>, meaning writes are sent
-   to the drive as soon as they arrive. Others are
-   <firstterm>write-back</>, meaning data is sent to the drive at
-   some later time. Such caches can be a reliability hazard because the
-   memory in the disk controller cache is volatile, and will lose its
-   contents in a power failure.  Better controller cards have
-   <firstterm>battery-backup units</> (<acronym>BBU</>s), meaning
-   the card has a battery that
-   maintains power to the cache in case of system power loss.  After power
-   is restored the data will be written to the disk drives.
-  </para>
-
-  <para>
-   And finally, most disk drives have caches. Some are write-through
-   while some are write-back, and the same concerns about data loss
-   exist for write-back drive caches as for disk controller
-   caches.  Consumer-grade IDE and SATA drives are particularly likely
-   to have write-back caches that will not survive a power failure.  Many
-   solid-state drives (SSD) also have volatile write-back caches.
-  </para>
-
-  <para>
-   These caches can typically be disabled; however, the method for doing
-   this varies by operating system and drive type:
-  </para>
-
-  <itemizedlist>
-    <listitem>
-      <para>
-        On <productname>Linux</>, IDE drives can be queried using
-        <command>hdparm -I</command>; write caching is enabled if there is
-        a <literal>*</> next to <literal>Write cache</>.  <command>hdparm -W</>
-        can be used to turn off write caching.  SCSI drives can be queried
-        using <ulink url="http://sg.danny.cz/sg/sdparm.html"><application>sdparm</></ulink>.
-        Use <command>sdparm --get=WCE</command> to check
-        whether the write cache is enabled and <command>sdparm --clear=WCE</>
-        to disable it.
-      </para>
-    </listitem>
-
-    <listitem>
-      <para>
-        On <productname>FreeBSD</>, IDE drives can be queried using
-        <command>atacontrol</command> and write caching turned off using
-        <literal>hw.ata.wc=0</> in <filename>/boot/loader.conf</>;
-        SCSI drives use <command>sdparm</command>.
-      </para>
-    </listitem>
-
-    <listitem>
-      <para>
-        On <productname>Solaris</>, the disk write cache is controlled by
-        <ulink url="http://www.sun.com/bigadmin/content/submitted/format_utility.jsp"><literal>format -e</></ulink>.
-        (The Solaris <acronym>ZFS</> file system is safe with disk write-cache
-        enabled because it issues its own disk cache flush commands.)
-      </para>
-    </listitem>
-
-    <listitem>
-      <para>
-        On <productname>Windows</>, if <varname>wal_sync_method</> is
-        <literal>open_datasync</> (the default), write caching can be disabled
-        by unchecking <literal>My Computer\Open\<replaceable>disk drive</>\Properties\Hardware\Properties\Policies\Enable write caching on the disk</>.
-        Alternatively, set <varname>wal_sync_method</varname> to
-        <literal>fsync</> or <literal>fsync_writethrough</>, which prevent
-        write caching.
-      </para>
-    </listitem>
-
-    <listitem>
-      <para>
-        On <productname>Mac OS X</productname>, write caching can be prevented by
-        setting <varname>wal_sync_method</> to <literal>fsync_writethrough</>.
-      </para>
-    </listitem>
-  </itemizedlist>
-
-  <para>
-   Recent SATA drives (those following <acronym>ATAPI-6</> or later)
-   offer a drive cache flush command (<command>FLUSH CACHE EXT</>),
-   while SCSI drives have long supported a similar command
-   <command>SYNCHRONIZE CACHE</>.  These commands are not directly
-<!## PG>
-   accessible to <productname>PostgreSQL</>, but some file systems
-<!## end>
-<!## XC>
-   accessible to <productname>Postgres-XC</>, but some file systems
-<!## end>
-<!## XL>
-   accessible to <productname>Postgres-XL</>, but some file systems
-<!## end>
-   (e.g., <acronym>ZFS</>, <acronym>ext4</>) can use them to flush
-   data to the platters on write-back-enabled drives.  Unfortunately, such
-   file systems behave suboptimally when combined with battery-backup unit
-   (<acronym>BBU</>) disk controllers.  In such setups, the synchronize
-   command forces all data from the controller cache to the disks,
-   eliminating much of the benefit of the BBU.  You can run the
-   <xref linkend="pgtestfsync"> module to see
-   if you are affected.  If you are affected, the performance benefits
-   of the BBU can be regained by turning off write barriers in
-   the file system or reconfiguring the disk controller, if that is
-   an option.  If write barriers are turned off, make sure the battery
-   remains functional; a faulty battery can potentially lead to data loss.
-   Hopefully file system and disk controller designers will eventually
-   address this suboptimal behavior.
-  </para>
-
-  <para>
-   When the operating system sends a write request to the storage hardware,
-   there is little it can do to make sure the data has arrived at a truly
-   non-volatile storage area. Rather, it is the
-   administrator's responsibility to make certain that all storage components
-   ensure data integrity.  Avoid disk controllers that have non-battery-backed
-   write caches.  At the drive level, disable write-back caching if the
-   drive cannot guarantee the data will be written before shutdown.
-   If you use SSDs, be aware that many of these do not honor cache flush
-   commands by default.
-   You can test for reliable I/O subsystem behavior using <ulink
-   url="http://brad.livejournal.com/2116715.html"><filename>diskchecker.pl</filename></ulink>.
-  </para>
-
-  <para>
-   Another risk of data loss is posed by the disk platter write
-   operations themselves. Disk platters are divided into sectors,
-   commonly 512 bytes each.  Every physical read or write operation
-   processes a whole sector.
-   When a write request arrives at the drive, it might be for some multiple
-<!## PG>
-   of 512 bytes (<productname>PostgreSQL</> typically writes 8192 bytes, or
-<!## end>
-<!## XC>
-   of 512 bytes (<productname>Postgres-XC</> typically writes 8192 bytes, or
-<!## end>
-<!## XL>
-   of 512 bytes (<productname>Postgres-XL</> typically writes 8192 bytes, or
-<!## end>
-   16 sectors, at a time), and the process of writing could fail due
-   to power loss at any time, meaning some of the 512-byte sectors were
-   written while others were not.  To guard against such failures,
-<!## PG>
-   <productname>PostgreSQL</> periodically writes full page images to
-   permanent WAL storage <emphasis>before</> modifying the actual page on
-   disk. By doing this, during crash recovery <productname>PostgreSQL</> can
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> periodically writes full page images to
-   permanent WAL storage <emphasis>before</> modifying the actual page on
-   disk. By doing this, during crash recovery <productname>Postgres-XC</> can
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> periodically writes full page images to
-   permanent WAL storage <emphasis>before</> modifying the actual page on
-   disk. By doing this, during crash recovery <productname>Postgres-XL</> can
-<!## end>
-   restore partially-written pages from WAL.  If you have file-system software
-   that prevents partial page writes (e.g., ZFS),  you can turn off
-   this page imaging by turning off the <xref
-   linkend="guc-full-page-writes"> parameter. Battery-Backed Unit
-   (BBU) disk controllers do not prevent partial page writes unless
-   they guarantee that data is written to the BBU as full (8kB) pages.
-  </para>
- </sect1>
-
-  <sect1 id="wal-intro">
-   <title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
-
-   <indexterm zone="wal">
-    <primary>WAL</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>transaction log</primary>
-    <see>WAL</see>
-   </indexterm>
-&common;
-
-   <para>
-    <firstterm>Write-Ahead Logging</firstterm> (<acronym>WAL</acronym>)
-    is a standard method for ensuring data integrity.  A detailed
-    description can be found in most (if not all) books about
-    transaction processing. Briefly, <acronym>WAL</acronym>'s central
-    concept is that changes to data files (where tables and indexes
-    reside) must be written only after those changes have been logged,
-    that is, after log records describing the changes have been flushed
-    to permanent storage. If we follow this procedure, we do not need
-    to flush data pages to disk on every transaction commit, because we
-    know that in the event of a crash we will be able to recover the
-    database using the log: any changes that have not been applied to
-    the data pages can be redone from the log records.  (This is
-    roll-forward recovery, also known as REDO.)
-   </para>
-
-   <tip>
-    <para>
-     Because <acronym>WAL</acronym> restores database file
-     contents after a crash, journaled file systems are not necessary for
-     reliable storage of the data files or WAL files.  In fact, journaling
-     overhead can reduce performance, especially if journaling
-     causes file system <emphasis>data</emphasis> to be flushed
-     to disk.  Fortunately, data flushing during journaling can
-     often be disabled with a file system mount option, e.g.
-     <literal>data=writeback</> on a Linux ext3 file system.
-     Journaled file systems do improve boot speed after a crash.
-    </para>
-   </tip>
-
-
-   <para>
-    Using <acronym>WAL</acronym> results in a
-    significantly reduced number of disk writes, because only the log
-    file needs to be flushed to disk to guarantee that a transaction is
-    committed, rather than every data file changed by the transaction.
-    The log file is written sequentially,
-    and so the cost of syncing the log is much less than the cost of
-    flushing the data pages.  This is especially true for servers
-    handling many small transactions touching different parts of the data
-    store.  Furthermore, when the server is processing many small concurrent
-    transactions, one <function>fsync</function> of the log file may
-    suffice to commit many transactions.
-   </para>
-
-   <para>
-    <acronym>WAL</acronym> also makes it possible to support on-line
-    backup and point-in-time recovery, as described in <xref
-    linkend="continuous-archiving">.  By archiving the WAL data we can support
-    reverting to any time instant covered by the available WAL data:
-    we simply install a prior physical backup of the database, and
-    replay the WAL log just as far as the desired time.  What's more,
-    the physical backup doesn't have to be an instantaneous snapshot
-    of the database state &mdash; if it is made over some period of time,
-    then replaying the WAL log for that period will fix any internal
-    inconsistencies.
-   </para>
-  </sect1>
-
- <sect1 id="wal-async-commit">
-  <title>Asynchronous Commit</title>
-
-   <indexterm>
-    <primary>synchronous commit</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>asynchronous commit</primary>
-   </indexterm>
-&common;
-
-  <para>
-   <firstterm>Asynchronous commit</> is an option that allows transactions
-   to complete more quickly, at the cost that the most recent transactions may
-   be lost if the database should crash.  In many applications this is an
-   acceptable trade-off.
-  </para>
-
-  <para>
-   As described in the previous section, transaction commit is normally
-   <firstterm>synchronous</>: the server waits for the transaction's
-   <acronym>WAL</acronym> records to be flushed to permanent storage
-   before returning a success indication to the client.  The client is
-   therefore guaranteed that a transaction reported to be committed will
-   be preserved, even in the event of a server crash immediately after.
-   However, for short transactions this delay is a major component of the
-   total transaction time.  Selecting asynchronous commit mode means that
-   the server returns success as soon as the transaction is logically
-   completed, before the <acronym>WAL</acronym> records it generated have
-   actually made their way to disk.  This can provide a significant boost
-   in throughput for small transactions.
-  </para>
-
-  <para>
-   Asynchronous commit introduces the risk of data loss. There is a short
-   time window between the report of transaction completion to the client
-   and the time that the transaction is truly committed (that is, it is
-   guaranteed not to be lost if the server crashes).  Thus asynchronous
-   commit should not be used if the client will take external actions
-   relying on the assumption that the transaction will be remembered.
-   As an example, a bank would certainly not use asynchronous commit for
-   a transaction recording an ATM's dispensing of cash.  But in many
-   scenarios, such as event logging, there is no need for a strong
-   guarantee of this kind.
-  </para>
-
-  <para>
-   The risk that is taken by using asynchronous commit is of data loss,
-   not data corruption.  If the database should crash, it will recover
-   by replaying <acronym>WAL</acronym> up to the last record that was
-   flushed.  The database will therefore be restored to a self-consistent
-   state, but any transactions that were not yet flushed to disk will
-   not be reflected in that state.  The net effect is therefore loss of
-   the last few transactions.  Because the transactions are replayed in
-   commit order, no inconsistency can be introduced &mdash; for example,
-   if transaction B made changes relying on the effects of a previous
-   transaction A, it is not possible for A's effects to be lost while B's
-   effects are preserved.
-  </para>
-
-  <para>
-   The user can select the commit mode of each transaction, so that
-   it is possible to have both synchronous and asynchronous commit
-   transactions running concurrently.  This allows flexible trade-offs
-   between performance and certainty of transaction durability.
-   The commit mode is controlled by the user-settable parameter
-   <xref linkend="guc-synchronous-commit">, which can be changed in any of
-   the ways that a configuration parameter can be set.  The mode used for
-   any one transaction depends on the value of
-   <varname>synchronous_commit</varname> when transaction commit begins.
-  </para>
-
-  <para>
-   Certain utility commands, for instance <command>DROP TABLE</>, are
-   forced to commit synchronously regardless of the setting of
-   <varname>synchronous_commit</varname>.  This is to ensure consistency
-   between the server's file system and the logical state of the database.
-   The commands supporting two-phase commit, such as <command>PREPARE
-   TRANSACTION</>, are also always synchronous.
-  </para>
-
-  <para>
-   If the database crashes during the risk window between an
-   asynchronous commit and the writing of the transaction's
-   <acronym>WAL</acronym> records,
-   then changes made during that transaction <emphasis>will</> be lost.
-   The duration of the
-   risk window is limited because a background process (the <quote>WAL
-   writer</>) flushes unwritten <acronym>WAL</acronym> records to disk
-   every <xref linkend="guc-wal-writer-delay"> milliseconds.
-   The actual maximum duration of the risk window is three times
-   <varname>wal_writer_delay</varname> because the WAL writer is
-   designed to favor writing whole pages at a time during busy periods.
-  </para>
-
-  <caution>
-   <para>
-    An immediate-mode shutdown is equivalent to a server crash, and will
-    therefore cause loss of any unflushed asynchronous commits.
-   </para>
-  </caution>
-
-  <para>
-   Asynchronous commit provides behavior different from setting
-   <xref linkend="guc-fsync"> = off.
-   <varname>fsync</varname> is a server-wide
-   setting that will alter the behavior of all transactions.  It disables
-<!## PG>
-   all logic within <productname>PostgreSQL</> that attempts to synchronize
-   writes to different portions of the database, and therefore a system
-   crash (that is, a hardware or operating system crash, not a failure of
-   <productname>PostgreSQL</> itself) could result in arbitrarily bad
-<!## end>
-<!## XC>
-   all logic within <productname>Postgres-XC</> that attempts to synchronize
-   writes to different portions of the database, and therefore a system
-   crash (that is, a hardware or operating system crash, not a failure of
-   <productname>Postgres-XC</> itself) could result in arbitrarily bad
-<!## end>
-<!## XL>
-   all logic within <productname>Postgres-XL</> that attempts to synchronize
-   writes to different portions of the database, and therefore a system
-   crash (that is, a hardware or operating system crash, not a failure of
-   <productname>Postgres-XL</> itself) could result in arbitrarily bad
-<!## end>
-   corruption of the database state.  In many scenarios, asynchronous
-   commit provides most of the performance improvement that could be
-   obtained by turning off <varname>fsync</varname>, but without the risk
-   of data corruption.
-  </para>
-
-  <para>
-   <xref linkend="guc-commit-delay"> also sounds very similar to
-   asynchronous commit, but it is actually a synchronous commit method
-   (in fact, <varname>commit_delay</varname> is ignored during an
-   asynchronous commit).  <varname>commit_delay</varname> causes a delay
-   just before a synchronous commit attempts to flush
-   <acronym>WAL</acronym> to disk, in the hope that a single flush
-   executed by one such transaction can also serve other transactions
-   committing at about the same time.  Setting <varname>commit_delay</varname>
-   can only help when there are many concurrently committing transactions,
-   and it is difficult to tune it to a value that actually helps rather
-   than hurt throughput.
-  </para>
-
- </sect1>
-
- <sect1 id="wal-configuration">
-  <title><acronym>WAL</acronym> Configuration</title>
-&common;
-
-  <para>
-   There are several <acronym>WAL</>-related configuration parameters that
-   affect database performance. This section explains their use.
-   Consult <xref linkend="runtime-config"> for general information about
-   setting server configuration parameters.
-  </para>
-
-  <para>
-   <firstterm>Checkpoints</firstterm><indexterm><primary>checkpoint</></>
-   are points in the sequence of transactions at which it is guaranteed
-   that the heap and index data files have been updated with all information written before
-   the checkpoint.  At checkpoint time, all dirty data pages are flushed to
-   disk and a special checkpoint record is written to the log file.
-   (The changes were previously flushed to the <acronym>WAL</acronym> files.)
-   In the event of a crash, the crash recovery procedure looks at the latest
-   checkpoint record to determine the point in the log (known as the redo
-   record) from which it should start the REDO operation.  Any changes made to
-   data files before that point are guaranteed to be already on disk.  Hence, after
-   a checkpoint, log segments preceding the one containing
-   the redo record are no longer needed and can be recycled or removed. (When
-   <acronym>WAL</acronym> archiving is being done, the log segments must be
-   archived before being recycled or removed.)
-  </para>
-
-  <para>
-   The checkpoint requirement of flushing all dirty data pages to disk
-   can cause a significant I/O load.  For this reason, checkpoint
-   activity is throttled so I/O begins at checkpoint start and completes
-   before the next checkpoint starts;  this minimizes performance
-   degradation during checkpoints.
-  </para>
-
-  <para>
-   The server's background writer process automatically performs
-   a checkpoint every so often.  A checkpoint is created every <xref
-   linkend="guc-checkpoint-segments"> log segments, or every <xref
-   linkend="guc-checkpoint-timeout"> seconds, whichever comes first.
-   The default settings are 3 segments and 300 seconds (5 minutes), respectively.
-   It is also possible to force a checkpoint by using the SQL command
-   <command>CHECKPOINT</command>.
-  </para>
-
-  <para>
-   Reducing <varname>checkpoint_segments</varname> and/or
-   <varname>checkpoint_timeout</varname> causes checkpoints to occur
-   more often. This allows faster after-crash recovery (since less work
-   will need to be redone). However, one must balance this against the
-   increased cost of flushing dirty data pages more often. If
-   <xref linkend="guc-full-page-writes"> is set (as is the default), there is
-   another factor to consider. To ensure data page consistency,
-   the first modification of a data page after each checkpoint results in
-   logging the entire page content. In that case,
-   a smaller checkpoint interval increases the volume of output to the WAL log,
-   partially negating the goal of using a smaller interval,
-   and in any case causing more disk I/O.
-  </para>
-
-  <para>
-   Checkpoints are fairly expensive, first because they require writing
-   out all currently dirty buffers, and second because they result in
-   extra subsequent WAL traffic as discussed above.  It is therefore
-   wise to set the checkpointing parameters high enough that checkpoints
-   don't happen too often.  As a simple sanity check on your checkpointing
-   parameters, you can set the <xref linkend="guc-checkpoint-warning">
-   parameter.  If checkpoints happen closer together than
-   <varname>checkpoint_warning</> seconds,
-   a message will be output to the server log recommending increasing
-   <varname>checkpoint_segments</varname>.  Occasional appearance of such
-   a message is not cause for alarm, but if it appears often then the
-   checkpoint control parameters should be increased. Bulk operations such
-   as large <command>COPY</> transfers might cause a number of such warnings
-   to appear if you have not set <varname>checkpoint_segments</> high
-   enough.
-  </para>
-
-  <para>
-   To avoid flooding the I/O system with a burst of page writes,
-   writing dirty buffers during a checkpoint is spread over a period of time.
-   That period is controlled by
-   <xref linkend="guc-checkpoint-completion-target">, which is
-   given as a fraction of the checkpoint interval.
-   The I/O rate is adjusted so that the checkpoint finishes when the
-   given fraction of <varname>checkpoint_segments</varname> WAL segments
-   have been consumed since checkpoint start, or the given fraction of
-   <varname>checkpoint_timeout</varname> seconds have elapsed,
-   whichever is sooner.  With the default value of 0.5,
-<!## PG>
-   <productname>PostgreSQL</> can be expected to complete each checkpoint
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</> can be expected to complete each checkpoint
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</> can be expected to complete each checkpoint
-<!## end>
-   in about half the time before the next checkpoint starts.  On a system
-   that's very close to maximum I/O throughput during normal operation,
-   you might want to increase <varname>checkpoint_completion_target</varname>
-   to reduce the I/O load from checkpoints.  The disadvantage of this is that
-   prolonging checkpoints affects recovery time, because more WAL segments
-   will need to be kept around for possible use in recovery.  Although
-   <varname>checkpoint_completion_target</varname> can be set as high as 1.0,
-   it is best to keep it less than that (perhaps 0.9 at most) since
-   checkpoints include some other activities besides writing dirty buffers.
-   A setting of 1.0 is quite likely to result in checkpoints not being
-   completed on time, which would result in performance loss due to
-   unexpected variation in the number of WAL segments needed.
-  </para>
-
-  <para>
-   There will always be at least one WAL segment file, and will normally
-   not be more than (2 + <varname>checkpoint_completion_target</varname>) * <varname>checkpoint_segments</varname> + 1
-   or <varname>checkpoint_segments</> + <xref linkend="guc-wal-keep-segments"> + 1
-   files.  Each segment file is normally 16 MB (though this size can be
-   altered when building the server).  You can use this to estimate space
-   requirements for <acronym>WAL</acronym>.
-   Ordinarily, when old log segment files are no longer needed, they
-   are recycled (renamed to become the next segments in the numbered
-   sequence). If, due to a short-term peak of log output rate, there
-   are more than 3 * <varname>checkpoint_segments</varname> + 1
-   segment files, the unneeded segment files will be deleted instead
-   of recycled until the system gets back under this limit.
-  </para>
-
-  <para>
-   In archive recovery or standby mode, the server periodically performs
-   <firstterm>restartpoints</><indexterm><primary>restartpoint</></>
-   which are similar to checkpoints in normal operation: the server forces
-   all its state to disk, updates the <filename>pg_control</> file to
-   indicate that the already-processed WAL data need not be scanned again,
-   and then recycles any old log segment files in <filename>pg_xlog</>
-   directory. A restartpoint is triggered if at least one checkpoint record
-   has been replayed and <varname>checkpoint_timeout</> seconds have passed
-   since last restartpoint. In standby mode, a restartpoint is also triggered
-   if <varname>checkpoint_segments</> log segments have been replayed since
-   last restartpoint and at least one checkpoint record has been replayed.
-   Restartpoints can't be performed more frequently than checkpoints in the
-   master because restartpoints can only be performed at checkpoint records.
-  </para>
-
-  <para>
-   There are two commonly used internal <acronym>WAL</acronym> functions:
-   <function>LogInsert</function> and <function>LogFlush</function>.
-   <function>LogInsert</function> is used to place a new record into
-   the <acronym>WAL</acronym> buffers in shared memory. If there is no
-   space for the new record, <function>LogInsert</function> will have
-   to write (move to kernel cache) a few filled <acronym>WAL</acronym>
-   buffers. This is undesirable because <function>LogInsert</function>
-   is used on every database low level modification (for example, row
-   insertion) at a time when an exclusive lock is held on affected
-   data pages, so the operation needs to be as fast as possible.  What
-   is worse, writing <acronym>WAL</acronym> buffers might also force the
-   creation of a new log segment, which takes even more
-   time. Normally, <acronym>WAL</acronym> buffers should be written
-   and flushed by a <function>LogFlush</function> request, which is
-   made, for the most part, at transaction commit time to ensure that
-   transaction records are flushed to permanent storage. On systems
-   with high log output, <function>LogFlush</function> requests might
-   not occur often enough to prevent <function>LogInsert</function>
-   from having to do writes.  On such systems
-   one should increase the number of <acronym>WAL</acronym> buffers by
-   modifying the configuration parameter <xref
-   linkend="guc-wal-buffers">.  The default number of <acronym>WAL</acronym>
-   buffers is 8.  Increasing this value will
-   correspondingly increase shared memory usage.  When
-   <xref linkend="guc-full-page-writes"> is set and the system is very busy,
-   setting this value higher will help smooth response times during the
-   period immediately following each checkpoint.
-  </para>
-
-  <para>
-   The <xref linkend="guc-commit-delay"> parameter defines for how many
-   microseconds the server process will sleep after writing a commit
-   record to the log with <function>LogInsert</function> but before
-   performing a <function>LogFlush</function>. This delay allows other
-   server processes to add their commit records to the log so as to have all
-   of them flushed with a single log sync. No sleep will occur if
-   <xref linkend="guc-fsync">
-   is not enabled, or if fewer than <xref linkend="guc-commit-siblings">
-   other sessions are currently in active transactions; this avoids
-   sleeping when it's unlikely that any other session will commit soon.
-   Note that on most platforms, the resolution of a sleep request is
-   ten milliseconds, so that any nonzero <varname>commit_delay</varname>
-   setting between 1 and 10000 microseconds would have the same effect.
-   Good values for these parameters are not yet clear; experimentation
-   is encouraged.
-  </para>
-
-  <para>
-   The <xref linkend="guc-wal-sync-method"> parameter determines how
-<!## PG>
-   <productname>PostgreSQL</productname> will ask the kernel to force
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> will ask the kernel to force
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> will ask the kernel to force
-<!## end>
-   <acronym>WAL</acronym> updates out to disk.
-   All the options should be the same in terms of reliability, with
-   the exception of <literal>fsync_writethrough</>, which can sometimes
-   force a flush of the disk cache even when other options do not do so.
-   However, it's quite platform-specific which one will be the fastest;
-   you can test option speeds using the <xref
-   linkend="pgtestfsync"> module.
-   Note that this parameter is irrelevant if <varname>fsync</varname>
-   has been turned off.
-  </para>
-
-  <para>
-   Enabling the <xref linkend="guc-wal-debug"> configuration parameter
-<!## PG>
-   (provided that <productname>PostgreSQL</productname> has been
-<!## end>
-<!## XC>
-   (provided that <productname>Postgres-XC</productname> has been
-<!## end>
-<!## XL>
-   (provided that <productname>Postgres-XL</productname> has been
-<!## end>
-   compiled with support for it) will result in each
-   <function>LogInsert</function> and <function>LogFlush</function>
-   <acronym>WAL</acronym> call being logged to the server log. This
-   option might be replaced by a more general mechanism in the future.
-  </para>
- </sect1>
-
- <sect1 id="wal-internals">
-  <title>WAL Internals</title>
-&common;
-
-  <para>
-   <acronym>WAL</acronym> is automatically enabled; no action is
-   required from the administrator except ensuring that the
-   disk-space requirements for the <acronym>WAL</acronym> logs are met,
-   and that any necessary tuning is done (see <xref
-   linkend="wal-configuration">).
-  </para>
-
-  <para>
-   <acronym>WAL</acronym> logs are stored in the directory
-   <filename>pg_xlog</filename> under the data directory, as a set of
-   segment files, normally each 16 MB in size (but the size can be changed
-   by altering the <option>--with-wal-segsize</> configure option when
-   building the server).  Each segment is divided into pages, normally
-   8 kB each (this size can be changed via the <option>--with-wal-blocksize</>
-   configure option).  The log record headers are described in
-   <filename>access/xlog.h</filename>; the record content is dependent
-   on the type of event that is being logged.  Segment files are given
-   ever-increasing numbers as names, starting at
-   <filename>000000010000000000000000</filename>.  The numbers do not wrap,
-   but it will take a very, very long time to exhaust the
-   available stock of numbers.
-  </para>
-
-  <para>
-   It is advantageous if the log is located on a different disk from the
-   main database files.  This can be achieved by moving the
-   <filename>pg_xlog</filename> directory to another location (while the server
-   is shut down, of course) and creating a symbolic link from the
-   original location in the main data directory to the new location.
-  </para>
-
-  <para>
-   The aim of <acronym>WAL</acronym> is to ensure that the log is
-   written before database records are altered, but this can be subverted by
-   disk drives<indexterm><primary>disk drive</></> that falsely report a
-   successful write to the kernel,
-   when in fact they have only cached the data and not yet stored it
-   on the disk.  A power failure in such a situation might lead to
-   irrecoverable data corruption.  Administrators should try to ensure
-<!## PG>
-   that disks holding <productname>PostgreSQL</productname>'s
-<!## end>
-<!## XC>
-   that disks holding <productname>Postgres-XC</productname>'s
-<!## end>
-<!## XL>
-   that disks holding <productname>Postgres-XL</productname>'s
-<!## end>
-   <acronym>WAL</acronym> log files do not make such false reports.
-   (See <xref linkend="wal-reliability">.)
-  </para>
-
-  <para>
-   After a checkpoint has been made and the log flushed, the
-   checkpoint's position is saved in the file
-   <filename>pg_control</filename>. Therefore, at the start of recovery,
-   the server first reads <filename>pg_control</filename> and
-   then the checkpoint record; then it performs the REDO operation by
-   scanning forward from the log position indicated in the checkpoint
-   record.  Because the entire content of data pages is saved in the
-   log on the first page modification after a checkpoint (assuming
-   <xref linkend="guc-full-page-writes"> is not disabled), all pages
-   changed since the checkpoint will be restored to a consistent
-   state.
-  </para>
-
-  <para>
-   To deal with the case where <filename>pg_control</filename> is
-   corrupt, we should support the possibility of scanning existing log
-   segments in reverse order &mdash; newest to oldest &mdash; in order to find the
-   latest checkpoint.  This has not been implemented yet.
-   <filename>pg_control</filename> is small enough (less than one disk page)
-   that it is not subject to partial-write problems, and as of this writing
-   there have been no reports of database failures due solely to the inability
-   to read <filename>pg_control</filename> itself.  So while it is
-   theoretically a weak spot, <filename>pg_control</filename> does not
-   seem to be a problem in practice.
-  </para>
- </sect1>
-
-<!## XC>
-
- <sect1 id="barriers">
-  <title>Barrier</title>
-&xconly;
-  <para>
-   Its important to ensure that any global transaction in the cluster
-   must either be committed on all the nodes or none of the nodes. If
-   the global recovery is done in a way such that on one node the
-   <acronym>WAL</acronym> recovery stops after a commit record of some
-   global transaction is processed, but stops before the commit record for
-   the same transaction is processed on some other node, the cluster may
-   be left in an inconsistent state. Since the commit messages of global
-   transactions can arrive out-of-order on different nodes, its very hard
-   to find a common synchronization point. For example, for two global
-   transactions T1 and T2, the commit messages for these transactions
-   can arrive on nodes N1 and N2 such that N1 receives commit message
-   for T1 first and N2 receives commit message T2 first. In this case,
-   during <acronym>PITR</acronym>, irrespective of whether we stop at
-   T1 or T2, the cluster would lose its consistency since at least one
-   transaction will be marked as committed on one node and as aborted
-   on the other node.
-  </para>
-
-  <para>
-   During recovery, it can be hard and even impossible to find
-   cluster-wide consistent synchronization points. In fact, such
-   synchronization points may not exists at all. Postgres-XC provides
-   a mechanism to create such synchronization points, called barriers,
-   during normal operation. A barrier can be created by using a SQL
-   command <command>BARRIER</command>
-  </para>
-
-  <para>
-   User must connect to one of the Coordinators and issue the
-   <command>BARRIER</command> command, optionally followed by an
-   identifier. If user does not specify an identifier, an unique
-   identifier will be generated and returned to the caller.  Upon
-   receiving the <command>BARRIER</command> command, the Coordinator
-   temporarily pauses any new two-phase commits. It also communicates with
-   other Coordinators to ensure that there are no in-progress two-phase
-   commits in the cluster. At that point, a barrier <acronym>WAL</acronym>
-   record along with the user-given or system-generated BARRIER identifier
-   is writtent to the <acronym>WAL</acronym> stream of all Datanodes and
-   the Coordinators.
-  </para>
-
-  <para>
-   User can create as many barriers as she wants to. At the time of
-   point-in-time-recovery, same barrier id must be specified in the
-   <filename>recovery.conf</filename> files of all the Coordinators and
-   Datanodes. When every node in the cluster recovers to the same barrier
-   id, a cluster-wide consistent state is reached. Its important that
-   the recovery must be started from a backup taken before the barrier
-   was generated. If no matching barrier record is found, either because
-   the barrier was created before the base backup used for the recovery
-   or the said barrier was never created, the recovery is run to the end.
-  </para>
-  
-  <para>
-   Note that in the current release, Postgres-XC has no means to detect
-   if another barrier with the same name already exists. So the user
-   must be careful while choosing a barrier identifier and ensure
-   that an unique identifier is used for every barrier. Similarly, at
-   the time of recovery, user must specify the same barrier id in the
-   <filename>recovery.conf</filename> file on all the nodes. Otherwise,
-   the cluster would not recover to a global consistent image.
-  </para>
- </sect1>
-<!## end>
-<!## XL>
-
- <sect1 id="barriers">
-  <title>Barrier</title>
-&xlonly;
-  <para>
-   Its important to ensure that any global transactions in the cluster
-   must either be committed on all the nodes or none of the nodes. If
-   global recovery is done in a way such that on one node the
-   <acronym>WAL</acronym> recovery stops after a commit record of some
-   global transaction is processed, but stops before the commit record for
-   the same transaction is processed on some other node, the cluster may
-   be left in an inconsistent state. Since the commit messages of global
-   transactions can arrive out-of-order on different nodes, its very hard
-   to find a common synchronization point. For example, for two global
-   transactions T1 and T2, the commit messages for these transactions
-   can arrive on nodes N1 and N2 such that N1 receives commit message
-   for T1 first and N2 receives commit message T2 first. In this case,
-   during <acronym>PITR</acronym>, irrespective of whether we stop at
-   T1 or T2, the cluster would lose its consistency since at least one
-   transaction will be marked as committed on one node and as aborted
-   on the other node.
-  </para>
-
-  <para>
-   During recovery, it can be hard and even impossible to find
-   cluster-wide consistent synchronization points. In fact, such
-   synchronization points may not exists at all. Postgres-XL provides
-   a mechanism to create such synchronization points, called barriers,
-   during normal operation. A barrier can be created by using a SQL
-   command <command>BARRIER</command>
-  </para>
-
-  <para>
-   The user must connect to one of the Coordinators and issue the
-   <command>BARRIER</command> command, optionally followed by an
-   identifier. If the user does not specify an identifier, an unique
-   identifier will be generated and returned to the caller.  Upon
-   receiving the <command>BARRIER</command> command, the Coordinator
-   temporarily pauses any new two-phase commits. It also communicates with
-   other Coordinators to ensure that there are no in-progress two-phase
-   commits in the cluster. At that point, a barrier <acronym>WAL</acronym>
-   record along with the user-given or system-generated BARRIER identifier
-   is writtent to the <acronym>WAL</acronym> stream of all Datanodes and
-   the Coordinators.
-  </para>
-
-  <para>
-   The user can create as many barriers as she wants to. At the time of
-   point-in-time-recovery, the same barrier id must be specified in the
-   <filename>recovery.conf</filename> files of all the Coordinators and
-   Datanodes. When every node in the cluster recovers to the same barrier
-   id, a cluster-wide consistent state is reached. Its important that
-   the recovery must be started from a backup taken before the barrier
-   was generated. If no matching barrier record is found, either because
-   the barrier was created before the base backup used for the recovery
-   or the said barrier was never created, the recovery is run to the end.
-  </para>
-  
-  <para>
-   Note that in the current release, Postgres-XL has no means to detect
-   if another barrier with the same name already exists. So the user
-   must be careful while choosing a barrier identifier and ensure
-   that an unique identifier is used for every barrier. Similarly, at
-   the time of recovery, the user must specify the same barrier id in the
-   <filename>recovery.conf</filename> file on all the nodes. Otherwise,
-   the cluster would not recover to a global consistent image.
-  </para>
- </sect1>
-<!## end>
-
-</chapter>
diff --git a/doc-xc/src/sgml/xaggr.sgmlin b/doc-xc/src/sgml/xaggr.sgmlin
deleted file mode 100644
index 5fccd25f79..0000000000
--- a/doc-xc/src/sgml/xaggr.sgmlin
+++ /dev/null
@@ -1,439 +0,0 @@
-<!-- doc/src/sgml/xaggr.sgml -->
-
- <sect1 id="xaggr">
-  <title>User-defined Aggregates</title>
-
-  <indexterm zone="xaggr">
-   <primary>aggregate function</primary>
-   <secondary>user-defined</secondary>
-  </indexterm>
-
-&common;
-
-<!## PG>
-  <para>
-   Aggregate functions  in <productname>PostgreSQL</productname>
-   are expressed in terms of <firstterm>state values</firstterm>
-   and <firstterm>state transition functions</firstterm>.
-   That is, an aggregate operates using a state value that is updated
-   as each successive input row is processed.
-   To define a new aggregate
-   function, one selects a data type for the state value,
-   an initial value for the state, and a state transition
-   function.  The state transition function is just an
-   ordinary function that could also be used outside the
-   context of the aggregate.  A <firstterm>final function</firstterm>
-   can also be specified, in case the desired result of the aggregate
-   is different from the data that needs to be kept in the running
-   state value.
-  </para>
-<!## end>
-<!## XC>
-&xconly;
-  <para>
-   Aggregate functions  in <productname>Postgres-XC</productname>
-   are expressed in terms of <firstterm>state values</firstterm>
-   and <firstterm>state functions namely transition function and collection
-   function</firstterm>.
-   That is, an aggregate operates using 1. a transition state value that is updated
-   as each successive input row, in a given set of rows, is processed, and
-   2. (optionally) collection state value that is updated as each successive
-   transition state value is processed.
-   To define a new aggregate
-   function, one selects a data type for the state value,
-   an initial value for the transition state, and a state transition
-   function.  The state transition function is just an
-   ordinary function that could also be used outside the
-   context of the aggregate.  A collection function and an initial value for
-   the collection state can also be specified, if one wants to take advantage of
-   distributed aggregation.  Similar to transition function, a collection
-   function can be an ordinary function that could also be used outside the
-   context of the aggregate.  A <firstterm>final function</firstterm>
-   can also be specified, in case the desired result of the aggregate
-   is different from the data that needs to be kept in the running
-   state (either collection or transition) value.
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-   Aggregate functions  in <productname>Postgres-XL</productname>
-   are expressed in terms of <firstterm>state values</firstterm>
-   and <firstterm>state functions namely transition function and collection
-   function</firstterm>.
-   That is, an aggregate operates using 1. a transition state value that is updated
-   as each successive input row, in a given set of rows, is processed, and
-   2. (optionally) collection state value that is updated as each successive
-   transition state value is processed.
-   To define a new aggregate
-   function, one selects a data type for the state value,
-   an initial value for the transition state, and a state transition
-   function.  The state transition function is just an
-   ordinary function that could also be used outside the
-   context of the aggregate.  A collection function and an initial value for
-   the collection state can also be specified, if one wants to take advantage of
-   distributed aggregation.  Similar to transition function, a collection
-   function can be an ordinary function that could also be used outside the
-   context of the aggregate.  A <firstterm>final function</firstterm>
-   can also be specified, in case the desired result of the aggregate
-   is different from the data that needs to be kept in the running
-   state (either collection or transition) value.
-  </para>
-<!## end>
-
-&common;
-  <para>
-   Thus, in addition to the argument and result data types seen by a user
-   of the aggregate, there is an internal state-value data type that
-   might be different from both the argument and result types.
-  </para>
-
-  <para>
-   If we define an aggregate that does not use a final function,
-   we have an aggregate that computes a running function of
-   the column values from each row.  <function>sum</>  is  an
-   example  of  this  kind  of aggregate.  <function>sum</> starts at
-   zero and always adds the current  row's  value  to
-   its  running  total.  For example, if we want to make a <function>sum</>
-   aggregate to work on a data type for complex numbers,
-   we only need the addition function for that data type.
-   The aggregate definition would be:
-
-<screen>
-CREATE AGGREGATE sum (complex)
-(
-    sfunc = complex_add,
-    stype = complex,
-    initcond = '(0,0)'
-);
-
-SELECT sum(a) FROM test_complex;
-
-   sum
------------
- (34,53.9)
-</screen>
-
-   (Notice that we are relying on function overloading: there is more than
-    one aggregate named <function>sum</>, but
-<!## PG>
-   <productname>PostgreSQL</productname> can figure out which kind
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> can figure out which kind
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> can figure out which kind
-<!## end>
-   of sum applies to a column of type <type>complex</type>.)
-  </para>
-
-<!## PG>
-  <para>
-   The above definition of <function>sum</function> will return zero (the initial
-   state condition) if there are no nonnull input values.
-   Perhaps we want to return null in that case instead &mdash; the SQL standard
-   expects <function>sum</function> to behave that way.  We can do this simply by
-   omitting the <literal>initcond</literal> phrase, so that the initial state
-   condition is null.  Ordinarily this would mean that the <literal>sfunc</literal>
-   would need to check for a null state-condition input, but for
-   <function>sum</function> and some other simple aggregates like
-   <function>max</> and <function>min</>,
-   it is sufficient to insert the first nonnull input value into
-   the state variable and then start applying the transition function
-   at the second nonnull input value.  <productname>PostgreSQL</productname>
-   will do that automatically if the initial condition is null and
-   the transition function is marked <quote>strict</> (i.e., not to be called
-   for null inputs).
-  </para>
-<!## end>
-<!## XC>
-&xconly;
-  <para>
-  In <productname>Postgres-XC</productname>, a user can provide collection
-  function if distributed aggregation is expected for improving performance. The
-  collection function essentially combines the state transition results produced
-  at different Datanodes. Without a final function the result produced by the
-  collection function is the result of aggregate. Above definition of aggregate
-  <function>sum</> for complex number data type can be modified to have a
-  collection function as follows
-
-<screen>
-CREATE AGGREGATE sum (complex)
-(
-    sfunc = complex_add,
-    stype = complex,
-cfunc = complex_add,
-    initcond = '(0,0)'
-initcollect = '(0.0)'
-);
-
-SELECT sum(a) FROM test_complex;
-
-   sum
------------
- (34,53.9)
-</screen>
-
-  Notice that both the CREATE AGGREGATE commands work in
-  <productname>Postgres-XC</productname>. Aggregate created by either command
-  produces the same results.
-  </para>
-
-&xconly;
-  <para>
-   The above definitions of <function>sum</function> will return zero (the initial
-   state condition) if there are no nonnull input values.
-   Perhaps we want to return null in that case instead &mdash; the SQL standard
-   expects <function>sum</function> to behave that way.  We can do this simply by
-   omitting the <literal>initcond</literal> phrase, so that the initial state
-   condition is null.  Ordinarily this would mean that the <literal>sfunc</literal>
-   would need to check for a null state-condition input, but for
-   <function>sum</function> and some other simple aggregates like
-   <function>max</> and <function>min</>,
-   it is sufficient to insert the first nonnull input value into
-   the state variable and then start applying the transition function
-   at the second nonnull input value.  <productname>Postgres-XC</productname>
-   will do that automatically if the initial condition is null and
-   the transition function is marked <quote>strict</> (i.e., not to be called
-   for null inputs).
-  </para>
-<!## end>
-<!## XL>
-&xlonly;
-  <para>
-  In <productname>Postgres-XL</productname>, a user can provide collection
-  function if distributed aggregation is expected for improving performance. The
-  collection function essentially combines the state transition results produced
-  at different Datanodes. Without a final function the result produced by the
-  collection function is the result of aggregate. Above the definition of aggregate
-  <function>sum</> for complex numeric data types can be modified to have a
-  collection function as follows
-
-<screen>
-CREATE AGGREGATE sum (complex)
-(
-    sfunc = complex_add,
-    stype = complex,
-cfunc = complex_add,
-    initcond = '(0,0)'
-initcollect = '(0.0)'
-);
-
-SELECT sum(a) FROM test_complex;
-
-   sum
------------
- (34,53.9)
-</screen>
-
-  Notice that both the CREATE AGGREGATE commands work in
-  <productname>Postgres-XL</productname>. An aggregate created by either command
-  produces the same results.
-  </para>
-
-&xlonly;
-  <para>
-   The above definitions of <function>sum</function> will return zero (the initial
-   state condition) if there are no nonnull input values.
-   Perhaps we want to return null in that case instead &mdash; the SQL standard
-   expects <function>sum</function> to behave that way.  We can do this simply by
-   omitting the <literal>initcond</literal> phrase, so that the initial state
-   condition is null.  Ordinarily this would mean that the <literal>sfunc</literal>
-   would need to check for a null state-condition input, but for
-   <function>sum</function> and some other simple aggregates like
-   <function>max</> and <function>min</>,
-   it is sufficient to insert the first nonnull input value into
-   the state variable and then start applying the transition function
-   at the second nonnull input value.  <productname>Postgres-XL</productname>
-   will do that automatically if the initial condition is null and
-   the transition function is marked <quote>strict</> (i.e., not to be called
-   for null inputs).
-  </para>
-<!## end>
-
-  <para>
-<!## PG>
-   Another bit of default behavior for a <quote>strict</> transition function
-<!## end>
-<!## XC>
-   Another bit of default behavior for a <quote>strict</> transition/collection function
-<!## end>
-<!## XL>
-   Another bit of default behavior for a <quote>strict</> transition/collection function
-<!## end>
-   is that the previous state value is retained unchanged whenever a
-   null input value is encountered.  Thus, null values are ignored.  If you
-   need some other behavior for null inputs, do not declare your
-<!## PG>
-   transition function as strict; instead code it to test for null inputs and
-<!## end>
-<!## XC>
-   transition/collection function as strict; instead code it to test for null inputs and
-<!## end>
-<!## XL>
-   transition/collection function as strict; instead code it to test for null inputs and
-<!## end>
-   do whatever is needed.
-  </para>
-
-  <para>
-   <function>avg</> (average) is a more complex example of an aggregate.
-   It requires
-   two pieces of running state: the sum of the inputs and the count
-   of the number of inputs.  The final result is obtained by dividing
-   these quantities.  Average is typically implemented by using a
-   two-element array as the state value.  For example,
-   the built-in implementation of <function>avg(float8)</function>
-   looks like:
-
-<!## PG>
-<programlisting>
-CREATE AGGREGATE avg (float8)
-(
-    sfunc = float8_accum,
-    stype = float8[],
-    finalfunc = float8_avg,
-    initcond = '{0,0}'
-);
-</programlisting>
-<!## end>
-<!## XC>
-<programlisting>
-CREATE AGGREGATE avg (float8)
-(
-    sfunc = float8_accum,
-    stype = float8[],
-    cfunc = float8_collect,
-    finalfunc = float8_avg,
-    initcond = '{0,0}'
-    initcollect = '{0,0,0}'
-);
-</programlisting>
-<!## end>
-<!## XL>
-<programlisting>
-CREATE AGGREGATE avg (float8)
-(
-    sfunc = float8_accum,
-    stype = float8[],
-    cfunc = float8_collect,
-    finalfunc = float8_avg,
-    initcond = '{0,0}'
-    initcollect = '{0,0,0}'
-);
-</programlisting>
-<!## end>
-
-<!## PG>
-   (<function>float8_accum</> requires a three-element array, not just
-<!## end>
-<!## XC>
-   (<function>float8_accum</> and <function>float8_collect</>
-   require a three-element array, not just
-<!## end>
-<!## XL>
-   (<function>float8_accum</> and <function>float8_collect</>
-   require a three-element array, not just
-<!## end>
-    two elements, because it accumulates the sum of squares as well as
-    the sum and count of the inputs.  This is so that it can be used for
-    some other aggregates besides <function>avg</>.)
-  </para>
-
-  <para>
-   Aggregate functions can use polymorphic
-<!## PG>
-   state transition functions or final functions, so that the same functions
-<!## end>
-<!## XC>
-   state transition/collection functions or final functions, so that the same functions
-<!## end>
-<!## XL>
-   state transition/collection functions or final functions, so that the same functions
-<!## end>
-   can be used to implement multiple aggregates.
-   See <xref linkend="extend-types-polymorphic">
-   for an explanation of polymorphic functions.
-   Going a step further, the aggregate function itself can be specified
-   with polymorphic input type(s) and state type, allowing a single
-   aggregate definition to serve for multiple input data types.
-   Here is an example of a polymorphic aggregate:
-
-<programlisting>
-CREATE AGGREGATE array_accum (anyelement)
-(
-    sfunc = array_append,
-    stype = anyarray,
-    initcond = '{}'
-);
-</programlisting>
-
-   Here, the actual state type for any aggregate call is the array type
-   having the actual input type as elements.  The behavior of the aggregate
-   is to concatenate all the inputs into an array of that type.
-   (Note: the built-in aggregate <function>array_agg</> provides similar
-   functionality, with better performance than this definition would have.)
-  </para>
-
-&common;
-  <para>
-   Here's the output using two different actual data types as arguments:
-
-<programlisting>
-SELECT attrelid::regclass, array_accum(attname)
-    FROM pg_attribute
-    WHERE attnum &gt; 0 AND attrelid = 'pg_tablespace'::regclass
-    GROUP BY attrelid;
-
-   attrelid    |              array_accum              
----------------+---------------------------------------
- pg_tablespace | {spcname,spcowner,spclocation,spcacl}
-(1 row)
-
-SELECT attrelid::regclass, array_accum(atttypid::regtype)
-    FROM pg_attribute
-    WHERE attnum &gt; 0 AND attrelid = 'pg_tablespace'::regclass
-    GROUP BY attrelid;
-
-   attrelid    |        array_accum        
----------------+---------------------------
- pg_tablespace | {name,oid,text,aclitem[]}
-(1 row)
-</programlisting>
-  </para>
-
-  <para>
-   A function written in C can detect that it is being called as an
-   aggregate transition or final function by calling
-   <function>AggCheckCallContext</>, for example:
-<programlisting>
-if (AggCheckCallContext(fcinfo, NULL))
-</programlisting>
-   One reason for checking this is that when it is true for a transition
-<!## PG>
-   function, the first input
-   must be a temporary transition value and can therefore safely be modified
-<!## end>
-<!## XC>
-   function, the first input to transition or collection function
-   must be a temporary transition/collection value and can therefore safely be modified
-<!## end>
-<!## XL>
-   function, the first input to transition or collection function
-   must be a temporary transition/collection value and can therefore safely be modified
-<!## end>
-   in-place rather than allocating a new copy.  (This is the <emphasis>only</>
-   case where it is safe for a function to modify a pass-by-reference input.
-   In particular, aggregate final functions should not modify their inputs in
-   any case, because in some cases they will be re-executed on the same
-   final transition value.)
-   See <literal>int8inc()</> for an example.
-  </para>
-
-  <para>
-   For further details see the
-   <xref linkend="sql-createaggregate">
-   command.
-  </para>
- </sect1>
diff --git a/doc-xc/src/sgml/xc-constraint.sgmlin b/doc-xc/src/sgml/xc-constraint.sgmlin
deleted file mode 100644
index 5e9a75a8c6..0000000000
--- a/doc-xc/src/sgml/xc-constraint.sgmlin
+++ /dev/null
@@ -1,14 +0,0 @@
-<!## XC>
-<para>
-<productname>Postgres-XC</> supports constraints only enforceable locally.
-You should not specify any constraint which need to refer to rows at remote node.
-</para>
-<!## end>
-<!## XL>
-<para>
-<productname>Postgres-XL</> supports constraints only enforceable locally.
-You should not specify any constraint which need to refer to rows on remote node.
-For example, a unique index on a replicated is locally enforceable (every tuple exists
-on every node). A unique index on a column of a round-robin distributed table cannot be enforced locally.
-</para>
-<!## end>
diff --git a/doc-xc/src/sgml/xconly.sgmlin b/doc-xc/src/sgml/xconly.sgmlin
deleted file mode 100644
index d9c69e9e50..0000000000
--- a/doc-xc/src/sgml/xconly.sgmlin
+++ /dev/null
@@ -1,7 +0,0 @@
-<!## XC>
-<note>
-<para>
-The following description applies only to <productname>Postgres-XC</>
-</para>
-</note>
-<!## end>
diff --git a/doc-xc/src/sgml/xfunc.sgmlin b/doc-xc/src/sgml/xfunc.sgmlin
deleted file mode 100644
index 0f47f89e34..0000000000
--- a/doc-xc/src/sgml/xfunc.sgmlin
+++ /dev/null
@@ -1,3610 +0,0 @@
-<!-- doc/src/sgml/xfunc.sgml -->
-
- <sect1 id="xfunc">
-  <title>User-defined Functions</title>
-
-  <indexterm zone="xfunc">
-   <primary>function</primary>
-   <secondary>user-defined</secondary>
-  </indexterm>
-
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> provides four kinds of
-<!## end>
-<!## XC>
-   Similar to <productname>PostgreSQL</productname>, <productname>Postgres-XC</> provides four kinds of
-<!## end>
-<!## XL>
-   Similar to <productname>PostgreSQL</productname>, <productname>Postgres-XL</> provides four kinds of
-<!## end>
-   functions:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      query language functions (functions written in
-      <acronym>SQL</acronym>) (<xref linkend="xfunc-sql">)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      procedural language functions (functions written in, for
-      example, <application>PL/pgSQL</> or <application>PL/Tcl</>)
-      (<xref linkend="xfunc-pl">)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      internal functions (<xref linkend="xfunc-internal">)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      C-language functions (<xref linkend="xfunc-c">)
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   Every kind
-   of  function  can take base types, composite types, or
-   combinations of these as arguments (parameters). In addition,
-   every kind of function can return a base type or
-   a composite type.  Functions can also be defined to return
-   sets of base or composite values.
-  </para>
-
-  <para>
-   Many kinds of functions can take or return certain pseudo-types
-   (such as polymorphic types), but the available facilities vary.
-   Consult the description of each kind of function for more details.
-  </para>
-
-  <para>
-   It's easiest to define <acronym>SQL</acronym>
-   functions, so we'll start by discussing those.
-   Most of the concepts presented for <acronym>SQL</acronym> functions
-   will carry over to the other types of functions.
-  </para>
-
-  <para>
-   Throughout this chapter, it can be useful to look at the reference
-   page of the <xref linkend="sql-createfunction"> command to
-   understand the examples better.  Some examples from this chapter
-   can be found in <filename>funcs.sql</filename> and
-   <filename>funcs.c</filename> in the <filename>src/tutorial</>
-<!## PG>
-   directory in the <productname>PostgreSQL</productname> source
-<!## end>
-<!## XC>
-   directory in the <productname>Postgres-XC</productname> source
-<!## end>
-<!## XL>
-   directory in the <productname>Postgres-XL</productname> source
-<!## end>
-   distribution.
-  </para>
-
-<!## XC>
-&xconly;
-   <para>
-    <productname>Postgres-XC</> allow only one SQL statement embedded
-    in each function.  This restriction will be removed in the future
-    releases.
-   </para>
-<!## end>
-<!## XL>
-&xlonly;
-   <para>
-    <productname>Postgres-XL</> allow only one SQL statement embedded
-    in each function.  This restriction will be removed in the future
-    releases.
-   </para>
-<!## end>
-  </sect1>
-
-  <sect1 id="xfunc-sql">
-   <title>Query Language (<acronym>SQL</acronym>) Functions</title>
-
-   <indexterm zone="xfunc-sql">
-    <primary>function</primary>
-    <secondary>user-defined</secondary>
-    <tertiary>in SQL</tertiary>
-   </indexterm>
-
-&common;
-   <para>
-    SQL functions execute an arbitrary list of SQL statements, returning
-    the result of the last query in the list.
-    In the simple (non-set)
-    case, the first row of the last query's result will be returned.
-    (Bear in mind that <quote>the first row</quote> of a multirow
-    result is not well-defined unless you use <literal>ORDER BY</>.)
-    If the last query happens
-    to return no rows at all, the null value will be returned.
-   </para>
-
-   <para>
-    Alternatively, an SQL function can be declared to return a set,
-    by specifying the function's return type as <literal>SETOF
-    <replaceable>sometype</></literal>, or equivalently by declaring it as
-    <literal>RETURNS TABLE(<replaceable>columns</>)</literal>.  In this case
-    all rows of the last query's result are returned.  Further details appear
-    below.
-   </para>
-
-   <para>
-    The body of an SQL function must be a list of SQL
-    statements separated by semicolons.  A semicolon after the last
-    statement is optional.  Unless the function is declared to return
-    <type>void</>, the last statement must be a <command>SELECT</>,
-    or an <command>INSERT</>, <command>UPDATE</>, or <command>DELETE</>
-    that has a <literal>RETURNING</> clause.
-   </para>
-
-    <para>
-     Any collection of commands in the  <acronym>SQL</acronym>
-     language can be packaged together and defined as a function.
-     Besides <command>SELECT</command> queries, the commands can include data
-     modification queries (<command>INSERT</command>,
-     <command>UPDATE</command>, and <command>DELETE</command>), as well as
-     other SQL commands. (You cannot use transaction control commands, e.g.
-     <command>COMMIT</>, <command>SAVEPOINT</>, and some utility
-     commands, e.g.  <literal>VACUUM</>, in <acronym>SQL</acronym> functions.)
-     However, the final command
-     must be a <command>SELECT</command> or have a <literal>RETURNING</>
-     clause that returns whatever is
-     specified as the function's return type.  Alternatively, if you
-     want to define a SQL function that performs actions but has no
-     useful value to return, you can define it as returning <type>void</>.
-     For example, this function removes rows with negative salaries from
-     the <literal>emp</> table:
-
-<screen>
-CREATE FUNCTION clean_emp() RETURNS void AS '
-    DELETE FROM emp
-        WHERE salary &lt; 0;
-' LANGUAGE SQL;
-
-SELECT clean_emp();
-
- clean_emp
------------
-
-(1 row)
-</screen>
-    </para>
-
-   <para>
-    The syntax of the <command>CREATE FUNCTION</command> command requires
-    the function body to be written as a string constant.  It is usually
-    most convenient to use dollar quoting (see <xref
-    linkend="sql-syntax-dollar-quoting">) for the string constant.
-    If you choose to use regular single-quoted string constant syntax,
-    you must double single quote marks (<literal>'</>) and backslashes
-    (<literal>\</>) (assuming escape string syntax) in the body of
-    the function (see <xref linkend="sql-syntax-strings">).
-   </para>
-
-   <para>
-    Arguments to the SQL function are referenced in the function
-    body using the syntax <literal>$<replaceable>n</></>: <literal>$1</>
-    refers to the first argument, <literal>$2</> to the second, and so on.
-    If an argument is of a composite type, then the dot notation,
-    e.g., <literal>$1.name</literal>, can be used to access attributes
-    of the argument.  The arguments can only be used as data values,
-    not as identifiers.  Thus for example this is reasonable:
-<programlisting>
-INSERT INTO mytable VALUES ($1);
-</programlisting>
-but this will not work:
-<programlisting>
-INSERT INTO $1 VALUES (42);
-</programlisting>
-   </para>
-
-   <sect2 id="xfunc-sql-base-functions">
-    <title><acronym>SQL</acronym> Functions on Base Types</title>
-&common;
-    <para>
-     The simplest possible <acronym>SQL</acronym> function has no arguments and
-     simply returns a base type, such as <type>integer</type>:
-
-<screen>
-CREATE FUNCTION one() RETURNS integer AS $$
-    SELECT 1 AS result;
-$$ LANGUAGE SQL;
-
--- Alternative syntax for string literal:
-CREATE FUNCTION one() RETURNS integer AS '
-    SELECT 1 AS result;
-' LANGUAGE SQL;
-
-SELECT one();
-
- one
------
-   1
-</screen>
-    </para>
-
-    <para>
-     Notice that we defined a column alias within the function body for the result of the function
-     (with  the  name <literal>result</>),  but this column alias is not visible
-     outside the function.  Hence,  the  result  is labeled <literal>one</>
-     instead of <literal>result</>.
-    </para>
-
-    <para>
-     It is almost as easy to define <acronym>SQL</acronym> functions
-     that take base types as arguments.  In the example below, notice
-     how we refer to the arguments within the function as <literal>$1</>
-     and <literal>$2</>.
-
-<screen>
-CREATE FUNCTION add_em(integer, integer) RETURNS integer AS $$
-    SELECT $1 + $2;
-$$ LANGUAGE SQL;
-
-SELECT add_em(1, 2) AS answer;
-
- answer
---------
-      3
-</screen>
-    </para>
-
-    <para>
-     Here is a more useful function, which might be used to debit a
-     bank account:
-
-<programlisting>
-CREATE FUNCTION tf1 (integer, numeric) RETURNS integer AS $$
-    UPDATE bank
-        SET balance = balance - $2
-        WHERE accountno = $1;
-    SELECT 1;
-$$ LANGUAGE SQL;
-</programlisting>
-
-     A user could execute this function to debit account 17 by $100.00 as
-     follows:
-
-<programlisting>
-SELECT tf1(17, 100.0);
-</programlisting>
-    </para>
-
-<!## PG>
-<!-- NOTICE:
-     No "RETURNING", only one statement in each function
--->
-    <para>
-     In practice one would probably like a more useful result from the
-     function than a constant 1, so a more likely definition
-     is:
-
-<programlisting>
-CREATE FUNCTION tf1 (integer, numeric) RETURNS numeric AS $$
-    UPDATE bank
-        SET balance = balance - $2
-        WHERE accountno = $1;
-    SELECT balance FROM bank WHERE accountno = $1;
-$$ LANGUAGE SQL;
-</programlisting>
-
-     which adjusts the balance and returns the new balance.
-     The same thing could be done in one command using <literal>RETURNING</>:
-
-<programlisting>
-CREATE FUNCTION tf1 (integer, numeric) RETURNS numeric AS $$
-    UPDATE bank
-        SET balance = balance - $2
-        WHERE accountno = $1
-    RETURNING balance;
-$$ LANGUAGE SQL;
-</programlisting>
-    </para>
-<!## end>
-<!## XC>
-&xconly;
-    <para>
-     Here, original <productname>PostgreSQL</> document describes
-     multiple statement function and <command>RETURNING</> clause,
-     neither of them are not supported by <productname>Postgres-XC</>
-     yet.  They will be supported in the future releases.
-    </para>
-<!## end>
-<!## XL>
-&xlonly;
-    <para>
-     Here, original <productname>PostgreSQL</> document describes
-     multiple statement function and <command>RETURNING</> clause,
-     neither of them are not supported by <productname>Postgres-XL</>
-     yet.  They will be supported in the future releases.
-    </para>
-<!## end>
-   </sect2>
-
-   <sect2 id="xfunc-sql-composite-functions">
-    <title><acronym>SQL</acronym> Functions on Composite Types</title>
-
-&common;
-    <para>
-     When writing  functions with arguments of composite
-     types, we must  not  only  specify  which
-     argument  we  want (as we did above with <literal>$1</> and <literal>$2</literal>) but
-     also the desired attribute (field) of  that  argument.   For  example,
-     suppose that
-     <type>emp</type> is a table containing employee data, and therefore
-     also the name of the composite type of each row of the table.  Here
-     is a function <function>double_salary</function> that computes what someone's
-     salary would be if it were doubled:
-
-<screen>
-CREATE TABLE emp (
-    name        text,
-    salary      numeric,
-    age         integer,
-    cubicle     point
-);
-
-INSERT INTO emp VALUES ('Bill', 4200, 45, '(2,1)');
-
-CREATE FUNCTION double_salary(emp) RETURNS numeric AS $$
-    SELECT $1.salary * 2 AS salary;
-$$ LANGUAGE SQL;
-
-SELECT name, double_salary(emp.*) AS dream
-    FROM emp
-    WHERE emp.cubicle ~= point '(2,1)';
-
- name | dream
-------+-------
- Bill |  8400
-</screen>
-    </para>
-
-    <para>
-     Notice the use of the syntax <literal>$1.salary</literal>
-     to select one field of the argument row value.  Also notice
-     how the calling <command>SELECT</> command uses <literal>*</>
-     to select
-     the entire current row of a table as a composite value.  The table
-     row can alternatively be referenced using just the table name,
-     like this:
-<screen>
-SELECT name, double_salary(emp) AS dream
-    FROM emp
-    WHERE emp.cubicle ~= point '(2,1)';
-</screen>
-     but this usage is deprecated since it's easy to get confused.
-    </para>
-
-    <para>
-     Sometimes it is handy to construct a composite argument value
-     on-the-fly.  This can be done with the <literal>ROW</> construct.
-     For example, we could adjust the data being passed to the function:
-<screen>
-SELECT name, double_salary(ROW(name, salary*1.1, age, cubicle)) AS dream
-    FROM emp;
-</screen>
-    </para>
-
-    <para>
-     It is also possible to build a function that returns a composite type.
-     This is an example of a function
-     that returns a single <type>emp</type> row:
-
-<programlisting>
-CREATE FUNCTION new_emp() RETURNS emp AS $$
-    SELECT text 'None' AS name,
-        1000.0 AS salary,
-        25 AS age,
-        point '(2,2)' AS cubicle;
-$$ LANGUAGE SQL;
-</programlisting>
-
-     In this example we have specified each of  the  attributes
-     with  a  constant value, but any computation
-     could have been substituted for these constants.
-    </para>
-
-    <para>
-     Note two important things about defining the function:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        The select list order in the query must be exactly the same as
-        that in which the columns appear in the table associated
-        with the composite type.  (Naming the columns, as we did above,
-        is irrelevant to the system.)
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        You must typecast the expressions to match the
-        definition of the composite type, or you will get errors like this:
-<screen>
-<computeroutput>
-ERROR:  function declared to return emp returns varchar instead of text at column 1
-</computeroutput>
-</screen>
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     A different way to define the same function is:
-
-<programlisting>
-CREATE FUNCTION new_emp() RETURNS emp AS $$
-    SELECT ROW('None', 1000.0, 25, '(2,2)')::emp;
-$$ LANGUAGE SQL;
-</programlisting>
-
-     Here we wrote a <command>SELECT</> that returns just a single
-     column of the correct composite type.  This isn't really better
-     in this situation, but it is a handy alternative in some cases
-     &mdash; for example, if we need to compute the result by calling
-     another function that returns the desired composite value.
-    </para>
-
-    <para>
-     We could call this function directly in either of two ways:
-
-<screen>
-SELECT new_emp();
-
-         new_emp
---------------------------
- (None,1000.0,25,"(2,2)")
-
-SELECT * FROM new_emp();
-
- name | salary | age | cubicle
-------+--------+-----+---------
- None | 1000.0 |  25 | (2,2)
-</screen>
-
-     The second way is described more fully in <xref
-     linkend="xfunc-sql-table-functions">.
-    </para>
-
-    <para>
-     When you use a function that returns a composite type,
-     you might want only one field (attribute) from its result.
-     You can do that with syntax like this:
-
-<screen>
-SELECT (new_emp()).name;
-
- name
-------
- None
-</screen>
-
-     The extra parentheses are needed to keep the parser from getting
-     confused.  If you try to do it without them, you get something like this:
-
-<screen>
-SELECT new_emp().name;
-ERROR:  syntax error at or near "."
-LINE 1: SELECT new_emp().name;
-                        ^
-</screen>
-    </para>
-
-    <para>
-     Another option is to use
-     functional notation for extracting an attribute.  The  simple  way
-     to explain this is that we can use the
-     notations <literal>attribute(table)</>  and  <literal>table.attribute</>
-     interchangeably.
-
-<screen>
-SELECT name(new_emp());
-
- name
-------
- None
-</screen>
-
-<screen>
--- This is the same as:
--- SELECT emp.name AS youngster FROM emp WHERE emp.age &lt; 30;
-
-SELECT name(emp) AS youngster FROM emp WHERE age(emp) &lt; 30;
-
- youngster
------------
- Sam
- Andy
-</screen>
-    </para>
-
-    <tip>
-     <para>
-      The equivalence between functional notation and attribute notation
-      makes it possible to use functions on composite types to emulate
-      <quote>computed fields</>.
-      <indexterm>
-       <primary>computed field</primary>
-      </indexterm>
-      <indexterm>
-       <primary>field</primary>
-       <secondary>computed</secondary>
-      </indexterm>
-      For example, using the previous definition
-      for <literal>double_salary(emp)</>, we can write
-
-<screen>
-SELECT emp.name, emp.double_salary FROM emp;
-</screen>
-
-      An application using this wouldn't need to be directly aware that
-      <literal>double_salary</> isn't a real column of the table.
-      (You can also emulate computed fields with views.)
-     </para>
-
-     <para>
-      Because of this behavior, it's unwise to give a function that takes
-      a single composite-type argument the same name as any of the fields of
-      that composite type.
-     </para>
-    </tip>
-
-    <para>
-     Another way to use a function returning a composite type is to pass the
-     result to another function that accepts the correct row type as input:
-
-<screen>
-CREATE FUNCTION getname(emp) RETURNS text AS $$
-    SELECT $1.name;
-$$ LANGUAGE SQL;
-
-SELECT getname(new_emp());
- getname
----------
- None
-(1 row)
-</screen>
-    </para>
-
-    <para>
-     Still another way to use a function that returns a composite type is to
-     call it as a table function, as described in <xref
-     linkend="xfunc-sql-table-functions">.
-    </para>
-   </sect2>
-
-   <sect2 id="xfunc-named-parameters">
-    <title><acronym>SQL</> Functions with Parameter Names</title>
-
-   <indexterm>
-    <primary>function</primary>
-    <secondary>named parameter</secondary>
-   </indexterm>
-<!## PG>
-<!-- NOTICE:
-     No RETURNING yet!
--->
-    <para>
-     It is possible to attach names to a function's parameters, for example
-
-<programlisting>
-CREATE FUNCTION tf1 (acct_no integer, debit numeric) RETURNS numeric AS $$
-    UPDATE bank
-        SET balance = balance - $2
-        WHERE accountno = $1
-    RETURNING balance;
-$$ LANGUAGE SQL;
-</programlisting>
-
-     Here the first parameter has been given the name <literal>acct_no</>,
-     and the second parameter the name <literal>debit</>.
-     So far as the SQL function itself is concerned, these names are just
-     decoration; you must still refer to the parameters as <literal>$1</>,
-     <literal>$2</>, etc within the function body.  (Some procedural
-     languages let you use the parameter names instead.)  However,
-     attaching names to the parameters is useful for documentation purposes.
-     When a function has many parameters, it is also useful to use the names
-     while calling the function, as described in
-     <xref linkend="sql-syntax-calling-funcs">.
-    </para>
-<!## end>
-<!## XC>
-&xconly;
-    <para>
-     This feature needs <command>RETURNING</> clause, which is not
-     supported in current <productname>Postgres-XC</>.  This feature
-     will be supported in the future releases.
-    </para>
-<!## end>
-<!## XL>
-&xlonly;
-    <para>
-     This feature needs <command>RETURNING</> clause, which is not
-     supported in current <productname>Postgres-XL</>.  This feature
-     will be supported in the future releases.
-    </para>
-<!## end>
-   </sect2>
-
-   <sect2 id="xfunc-output-parameters">
-    <title><acronym>SQL</> Functions with Output Parameters</title>
-
-   <indexterm>
-    <primary>function</primary>
-    <secondary>output parameter</secondary>
-   </indexterm>
-&common;
-    <para>
-     An alternative way of describing a function's results is to define it
-     with <firstterm>output parameters</>, as in this example:
-
-<screen>
-CREATE FUNCTION add_em (IN x int, IN y int, OUT sum int)
-AS 'SELECT $1 + $2'
-LANGUAGE SQL;
-
-SELECT add_em(3,7);
- add_em
---------
-     10
-(1 row)
-</screen>
-
-     This is not essentially different from the version of <literal>add_em</>
-     shown in <xref linkend="xfunc-sql-base-functions">.  The real value of
-     output parameters is that they provide a convenient way of defining
-     functions that return several columns.  For example,
-
-<screen>
-CREATE FUNCTION sum_n_product (x int, y int, OUT sum int, OUT product int)
-AS 'SELECT $1 + $2, $1 * $2'
-LANGUAGE SQL;
-
- SELECT * FROM sum_n_product(11,42);
- sum | product
------+---------
-  53 |     462
-(1 row)
-</screen>
-
-     What has essentially happened here is that we have created an anonymous
-     composite type for the result of the function.  The above example has
-     the same end result as
-
-<screen>
-CREATE TYPE sum_prod AS (sum int, product int);
-
-CREATE FUNCTION sum_n_product (int, int) RETURNS sum_prod
-AS 'SELECT $1 + $2, $1 * $2'
-LANGUAGE SQL;
-</screen>
-
-     but not having to bother with the separate composite type definition
-     is often handy.  Notice that the names attached to the output parameters
-     are not just decoration, but determine the column names of the anonymous
-     composite type.  (If you omit a name for an output parameter, the
-     system will choose a name on its own.)
-    </para>
-
-    <para>
-     Notice that output parameters are not included in the calling argument
-     list when invoking such a function from SQL.  This is because
-<!## PG>
-     <productname>PostgreSQL</productname> considers only the input
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> considers only the input
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> considers only the input
-<!## end>
-     parameters to define the function's calling signature.  That means
-     also that only the input parameters matter when referencing the function
-     for purposes such as dropping it.  We could drop the above function
-     with either of
-
-<screen>
-DROP FUNCTION sum_n_product (x int, y int, OUT sum int, OUT product int);
-DROP FUNCTION sum_n_product (int, int);
-</screen>
-    </para>
-
-    <para>
-     Parameters can be marked as <literal>IN</> (the default),
-     <literal>OUT</>, <literal>INOUT</>, or <literal>VARIADIC</>.
-     An <literal>INOUT</>
-     parameter serves as both an input parameter (part of the calling
-     argument list) and an output parameter (part of the result record type).
-     <literal>VARIADIC</> parameters are input parameters, but are treated
-     specially as described next.
-    </para>
-   </sect2>
-
-   <sect2 id="xfunc-sql-variadic-functions">
-    <title><acronym>SQL</> Functions with Variable Numbers of Arguments</title>
-
-    <indexterm>
-     <primary>function</primary>
-     <secondary>variadic</secondary>
-    </indexterm>
-
-    <indexterm>
-     <primary>variadic function</primary>
-    </indexterm>
-<!## XC>
-<!-- NOTICE:
-     VARIADIC is not well tested yet.  CREATE FUNCTION succeeds but the result can be wrong.
--->
-&xconly;
-    <para>
-     It is highly recommended not to use <literal>VARIADIC</> in the
-     current <productname>Postgres-XC</>.  It is not well reviewed and
-     may return wrong result.
-    </para>
-<!## end>
-<!## XL>
-<!-- NOTICE:
-     VARIADIC is not well tested yet.  CREATE FUNCTION succeeds but the result can be wrong.
--->
-&xlonly;
-    <para>
-     It is highly recommended not to use <literal>VARIADIC</> in the
-     current <productname>Postgres-XL</>.  It is not well reviewed and
-     may return wrong result.
-    </para>
-<!## end>
-    <para>
-     <acronym>SQL</acronym> functions can be declared to accept
-     variable numbers of arguments, so long as all the <quote>optional</>
-     arguments are of the same data type.  The optional arguments will be
-     passed to the function as an array.  The function is declared by
-     marking the last parameter as <literal>VARIADIC</>; this parameter
-     must be declared as being of an array type.  For example:
-
-<screen>
-CREATE FUNCTION mleast(VARIADIC arr numeric[]) RETURNS numeric AS $$
-    SELECT min($1[i]) FROM generate_subscripts($1, 1) g(i);
-$$ LANGUAGE SQL;
-
-SELECT mleast(10, -1, 5, 4.4);
- mleast 
---------
-     -1
-(1 row)
-</screen>
-
-     Effectively, all the actual arguments at or beyond the
-     <literal>VARIADIC</> position are gathered up into a one-dimensional
-     array, as if you had written
-
-<screen>
-SELECT mleast(ARRAY[10, -1, 5, 4.4]);    -- doesn't work
-</screen>
-
-     You can't actually write that, though &mdash; or at least, it will
-     not match this function definition.  A parameter marked
-     <literal>VARIADIC</> matches one or more occurrences of its element
-     type, not of its own type.
-    </para>
-
-    <para>
-     Sometimes it is useful to be able to pass an already-constructed array
-     to a variadic function; this is particularly handy when one variadic
-     function wants to pass on its array parameter to another one.  You can
-     do that by specifying <literal>VARIADIC</> in the call:
-
-<screen>
-SELECT mleast(VARIADIC ARRAY[10, -1, 5, 4.4]);
-</screen>
-
-     This prevents expansion of the function's variadic parameter into its
-     element type, thereby allowing the array argument value to match
-     normally.  <literal>VARIADIC</> can only be attached to the last
-     actual argument of a function call.
-    </para>
-
-    <para>
-     The array element parameters generated from a variadic parameter are
-     treated as not having any names of their own.  This means it is not
-     possible to call a variadic function using named arguments (<xref
-     linkend="sql-syntax-calling-funcs">), except when you specify
-     <literal>VARIADIC</>.  For example, this will work:
-
-<screen>
-SELECT mleast(VARIADIC arr := ARRAY[10, -1, 5, 4.4]);
-</screen>
-
-     but not these:
-
-<screen>
-SELECT mleast(arr := 10);
-SELECT mleast(arr := ARRAY[10, -1, 5, 4.4]);
-</screen>
-    </para>
-   </sect2>
-
-   <sect2 id="xfunc-sql-parameter-defaults">
-    <title><acronym>SQL</> Functions with Default Values for Arguments</title>
-
-    <indexterm>
-     <primary>function</primary>
-     <secondary>default values for arguments</secondary>
-    </indexterm>
-&common;
-    <para>
-     Functions can be declared with default values for some or all input
-     arguments.  The default values are inserted whenever the function is
-     called with insufficiently many actual arguments.  Since arguments
-     can only be omitted from the end of the actual argument list, all
-     parameters after a parameter with a default value have to have
-     default values as well.  (Although the use of named argument notation
-     could allow this restriction to be relaxed, it's still enforced so that
-     positional argument notation works sensibly.)
-    </para>
-
-    <para>
-     For example:
-<screen>
-CREATE FUNCTION foo(a int, b int DEFAULT 2, c int DEFAULT 3)
-RETURNS int
-LANGUAGE SQL
-AS $$
-    SELECT $1 + $2 + $3;
-$$;
-
-SELECT foo(10, 20, 30);
- foo 
------
-  60
-(1 row)
-
-SELECT foo(10, 20);
- foo 
------
-  33
-(1 row)
-
-SELECT foo(10);
- foo 
------
-  15
-(1 row)
-
-SELECT foo();  -- fails since there is no default for the first argument
-ERROR:  function foo() does not exist
-</screen>
-     The <literal>=</literal> sign can also be used in place of the
-     key word <literal>DEFAULT</literal>.
-    </para>
-   </sect2>
-
-   <sect2 id="xfunc-sql-table-functions">
-    <title><acronym>SQL</acronym> Functions as Table Sources</title>
-&common;
-    <para>
-     All SQL functions can be used in the <literal>FROM</> clause of a query,
-     but it is particularly useful for functions returning composite types.
-     If the function is defined to return a base type, the table function
-     produces a one-column table.  If the function is defined to return
-     a composite type, the table function produces a column for each attribute
-     of the composite type.
-    </para>
-
-    <para>
-     Here is an example:
-
-<screen>
-CREATE TABLE foo (fooid int, foosubid int, fooname text);
-INSERT INTO foo VALUES (1, 1, 'Joe');
-INSERT INTO foo VALUES (1, 2, 'Ed');
-INSERT INTO foo VALUES (2, 1, 'Mary');
-
-CREATE FUNCTION getfoo(int) RETURNS foo AS $$
-    SELECT * FROM foo WHERE fooid = $1;
-$$ LANGUAGE SQL;
-
-SELECT *, upper(fooname) FROM getfoo(1) AS t1;
-
- fooid | foosubid | fooname | upper
--------+----------+---------+-------
-     1 |        1 | Joe     | JOE
-(1 row)
-</screen>
-
-     As the example shows, we can work with the columns of the function's
-     result just the same as if they were columns of a regular table.
-    </para>
-
-    <para>
-     Note that we only got one row out of the function.  This is because
-     we did not use <literal>SETOF</>.  That is described in the next section.
-    </para>
-   </sect2>
-
-   <sect2 id="xfunc-sql-functions-returning-set">
-    <title><acronym>SQL</acronym> Functions Returning Sets</title>
-
-    <indexterm>
-     <primary>function</primary>
-     <secondary>with SETOF</secondary>
-    </indexterm>
-
-    <para>
-     When an SQL function is declared as returning <literal>SETOF
-     <replaceable>sometype</></literal>, the function's final
-     query is executed to completion, and each row it
-     outputs is returned as an element of the result set.
-    </para>
-
-    <para>
-     This feature is normally used when calling the function in the <literal>FROM</>
-     clause.  In this case each row returned by the function becomes
-     a row of the table seen by the query.  For example, assume that
-     table <literal>foo</> has the same contents as above, and we say:
-
-<programlisting>
-CREATE FUNCTION getfoo(int) RETURNS SETOF foo AS $$
-    SELECT * FROM foo WHERE fooid = $1;
-$$ LANGUAGE SQL;
-
-SELECT * FROM getfoo(1) AS t1;
-</programlisting>
-
-     Then we would get:
-<screen>
- fooid | foosubid | fooname
--------+----------+---------
-     1 |        1 | Joe
-     1 |        2 | Ed
-(2 rows)
-</screen>
-    </para>
-
-    <para>
-     It is also possible to return multiple rows with the columns defined by
-     output parameters, like this:
-
-<programlisting>
-CREATE TABLE tab (y int, z int);
-INSERT INTO tab VALUES (1, 2), (3, 4), (5, 6), (7, 8);
-
-CREATE FUNCTION sum_n_product_with_tab (x int, OUT sum int, OUT product int)
-RETURNS SETOF record
-AS $$
-    SELECT $1 + tab.y, $1 * tab.y FROM tab;
-$$ LANGUAGE SQL;
-
-SELECT * FROM sum_n_product_with_tab(10);
- sum | product
------+---------
-  11 |      10
-  13 |      30
-  15 |      50
-  17 |      70
-(4 rows)
-</programlisting>
-
-     The key point here is that you must write <literal>RETURNS SETOF record</>
-     to indicate that the function returns multiple rows instead of just one.
-     If there is only one output parameter, write that parameter's type
-     instead of <type>record</>.
-    </para>
-
-    <para>
-     Currently, functions returning sets can also be called in the select list
-     of a query.  For each row that the query
-     generates by itself, the function returning set is invoked, and an output
-     row is generated for each element of the function's result set. Note,
-     however, that this capability is deprecated and might be removed in future
-     releases. The following is an example function returning a set from the
-     select list:
-
-<screen>
-CREATE FUNCTION listchildren(text) RETURNS SETOF text AS $$
-    SELECT name FROM nodes WHERE parent = $1
-$$ LANGUAGE SQL;
-
-SELECT * FROM nodes;
-   name    | parent
------------+--------
- Top       |
- Child1    | Top
- Child2    | Top
- Child3    | Top
- SubChild1 | Child1
- SubChild2 | Child1
-(6 rows)
-
-SELECT listchildren('Top');
- listchildren
---------------
- Child1
- Child2
- Child3
-(3 rows)
-
-SELECT name, listchildren(name) FROM nodes;
-  name  | listchildren
---------+--------------
- Top    | Child1
- Top    | Child2
- Top    | Child3
- Child1 | SubChild1
- Child1 | SubChild2
-(5 rows)
-</screen>
-
-     In the last <command>SELECT</command>,
-     notice that no output row appears for <literal>Child2</>, <literal>Child3</>, etc.
-     This happens because <function>listchildren</function> returns an empty set
-     for those arguments, so no result rows are generated.
-    </para>
-
-    <note>
-     <para>
-      If a function's last command is <command>INSERT</>, <command>UPDATE</>,
-      or <command>DELETE</> with <literal>RETURNING</>, that command will
-      always be executed to completion, even if the function is not declared
-      with <literal>SETOF</> or the calling query does not fetch all the
-      result rows.  Any extra rows produced by the <literal>RETURNING</>
-      clause are silently dropped, but the commanded table modifications
-      still happen (and are all completed before returning from the function).
-     </para>
-    </note>
-   </sect2>
-
-   <sect2 id="xfunc-sql-functions-returning-table">
-    <title><acronym>SQL</acronym> Functions Returning <literal>TABLE</></title>
-
-    <indexterm>
-     <primary>function</primary>
-     <secondary>RETURNS TABLE</secondary>
-    </indexterm>
-&common;
-    <para>
-     There is another way to declare a function as returning a set,
-     which is to use the syntax
-     <literal>RETURNS TABLE(<replaceable>columns</>)</literal>.
-     This is equivalent to using one or more <literal>OUT</> parameters plus
-     marking the function as returning <literal>SETOF record</> (or
-     <literal>SETOF</> a single output parameter's type, as appropriate).
-     This notation is specified in recent versions of the SQL standard, and
-     thus may be more portable than using <literal>SETOF</>.
-    </para>
-
-    <para>
-     For example, the preceding sum-and-product example could also be
-     done this way:
-
-<programlisting>
-CREATE FUNCTION sum_n_product_with_tab (x int)
-RETURNS TABLE(sum int, product int) AS $$
-    SELECT $1 + tab.y, $1 * tab.y FROM tab;
-$$ LANGUAGE SQL;
-</programlisting>
-
-     It is not allowed to use explicit <literal>OUT</> or <literal>INOUT</>
-     parameters with the <literal>RETURNS TABLE</> notation &mdash; you must
-     put all the output columns in the <literal>TABLE</> list.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Polymorphic <acronym>SQL</acronym> Functions</title>
-&common;
-    <para>
-     <acronym>SQL</acronym> functions can be declared to accept and
-     return the polymorphic types <type>anyelement</type>,
-     <type>anyarray</type>, <type>anynonarray</type>, and
-     <type>anyenum</type>.  See <xref
-     linkend="extend-types-polymorphic"> for a more detailed
-     explanation of polymorphic functions. Here is a polymorphic
-     function <function>make_array</function> that builds up an array
-     from two arbitrary data type elements:
-<screen>
-CREATE FUNCTION make_array(anyelement, anyelement) RETURNS anyarray AS $$
-    SELECT ARRAY[$1, $2];
-$$ LANGUAGE SQL;
-
-SELECT make_array(1, 2) AS intarray, make_array('a'::text, 'b') AS textarray;
- intarray | textarray
-----------+-----------
- {1,2}    | {a,b}
-(1 row)
-</screen>
-    </para>
-
-    <para>
-     Notice the use of the typecast <literal>'a'::text</literal>
-     to specify that the argument is of type <type>text</type>. This is
-     required if the argument is just a string literal, since otherwise
-     it would be treated as type
-     <type>unknown</type>, and array of <type>unknown</type> is not a valid
-     type.
-     Without the typecast, you will get errors like this:
-<screen>
-<computeroutput>
-ERROR:  could not determine polymorphic type because input has type "unknown"
-</computeroutput>
-</screen>
-    </para>
-
-    <para>
-     It is permitted to have polymorphic arguments with a fixed
-     return type, but the converse is not. For example:
-<screen>
-CREATE FUNCTION is_greater(anyelement, anyelement) RETURNS boolean AS $$
-    SELECT $1 &gt; $2;
-$$ LANGUAGE SQL;
-
-SELECT is_greater(1, 2);
- is_greater
-------------
- f
-(1 row)
-
-CREATE FUNCTION invalid_func() RETURNS anyelement AS $$
-    SELECT 1;
-$$ LANGUAGE SQL;
-ERROR:  cannot determine result data type
-DETAIL:  A function returning a polymorphic type must have at least one polymorphic argument.
-</screen>
-    </para>
-
-    <para>
-     Polymorphism can be used with functions that have output arguments.
-     For example:
-<screen>
-CREATE FUNCTION dup (f1 anyelement, OUT f2 anyelement, OUT f3 anyarray)
-AS 'select $1, array[$1,$1]' LANGUAGE SQL;
-
-SELECT * FROM dup(22);
- f2 |   f3
-----+---------
- 22 | {22,22}
-(1 row)
-</screen>
-    </para>
-
-<!## PG>
-    <para>
-     Polymorphism can also be used with variadic functions.
-     For example:
-<screen>
-CREATE FUNCTION anyleast (VARIADIC anyarray) RETURNS anyelement AS $$
-    SELECT min($1[i]) FROM generate_subscripts($1, 1) g(i);
-$$ LANGUAGE SQL;
-
-SELECT anyleast(10, -1, 5, 4);
- anyleast 
-----------
-       -1
-(1 row)
-
-SELECT anyleast('abc'::text, 'def');
- anyleast 
-----------
- abc
-(1 row)
-
-CREATE FUNCTION concat_values(text, VARIADIC anyarray) RETURNS text AS $$
-    SELECT array_to_string($2, $1);
-$$ LANGUAGE SQL;
-
-SELECT concat_values('|', 1, 4, 2);
- concat_values 
----------------
- 1|4|2
-(1 row)
-</screen>
-    </para>
-<!## end>
-<!## XC>
-<!-- NOTICE:
-     VARIADIC is not well tested and supported
--->
-&xconly;
-    <para>
-     Here, original <productname>PostgreSQL</> document describes an
-     example with <command>VARIADIC</>, which is not well tested and
-     supported in current <productname>Postgres-XC</>.  This may be
-     supported in the future releases.
-    </para>
-<!## end>
-<!## XL>
-<!-- NOTICE:
-     VARIADIC is not well tested and supported
--->
-&xlonly;
-    <para>
-     Here, original <productname>PostgreSQL</> document describes an
-     example with <command>VARIADIC</>, which is not well tested and
-     supported in current <productname>Postgres-XL</>.  This may be
-     supported in the future releases.
-    </para>
-<!## end>
-   </sect2>
-
-   <sect2>
-    <title><acronym>SQL</acronym> Functions with Collations</title>
-
-    <indexterm>
-     <primary>collation</>
-     <secondary>in SQL functions</>
-    </indexterm>
-
-    <para>
-     When a SQL function has one or more parameters of collatable data types,
-     a collation is identified for each function call depending on the
-     collations assigned to the actual arguments, as described in <xref
-     linkend="collation">.  If a collation is successfully identified
-     (i.e., there are no conflicts of implicit collations among the arguments)
-     then all the collatable parameters are treated as having that collation
-     implicitly.  This will affect the behavior of collation-sensitive
-     operations within the function.  For example, using the
-     <function>anyleast</> function described above, the result of
-<programlisting>
-SELECT anyleast('abc'::text, 'ABC');
-</programlisting>
-     will depend on the database's default collation.  In <literal>C</> locale
-     the result will be <literal>ABC</>, but in many other locales it will
-     be <literal>abc</>.  The collation to use can be forced by adding
-     a <literal>COLLATE</> clause to any of the arguments, for example
-<programlisting>
-SELECT anyleast('abc'::text, 'ABC' COLLATE "C");
-</programlisting>
-     Alternatively, if you wish a function to operate with a particular
-     collation regardless of what it is called with, insert
-     <literal>COLLATE</> clauses as needed in the function definition.
-     This version of <function>anyleast</> would always use <literal>en_US</>
-     locale to compare strings:
-<programlisting>
-CREATE FUNCTION anyleast (VARIADIC anyarray) RETURNS anyelement AS $$
-    SELECT min($1[i] COLLATE "en_US") FROM generate_subscripts($1, 1) g(i);
-$$ LANGUAGE SQL;
-</programlisting>
-     But note that this will throw an error if applied to a non-collatable
-     data type.
-    </para>
-
-    <para>
-     If no common collation can be identified among the actual arguments,
-     then a SQL function treats its parameters as having their data types'
-     default collation (which is usually the database's default collation,
-     but could be different for parameters of domain types).
-    </para>
-
-    <para>
-     The behavior of collatable parameters can be thought of as a limited
-     form of polymorphism, applicable only to textual data types.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="xfunc-overload">
-   <title>Function Overloading</title>
-
-   <indexterm zone="xfunc-overload">
-    <primary>overloading</primary>
-    <secondary>functions</secondary>
-   </indexterm>
-&common;
-   <para>
-    More than one function can be defined with the same SQL name, so long
-    as the arguments they take are different.  In other words,
-    function names can be <firstterm>overloaded</firstterm>.  When a
-    query is executed, the server will determine which function to
-    call from the data types and the number of the provided arguments.
-    Overloading can also be used to simulate functions with a variable
-    number of arguments, up to a finite maximum number.
-   </para>
-
-   <para>
-    When creating a family of overloaded functions, one should be
-    careful not to create ambiguities.  For instance, given the
-    functions:
-<programlisting>
-CREATE FUNCTION test(int, real) RETURNS ...
-CREATE FUNCTION test(smallint, double precision) RETURNS ...
-</programlisting>
-    it is not immediately clear which function would be called with
-    some trivial input like <literal>test(1, 1.5)</literal>.  The
-    currently implemented resolution rules are described in
-    <xref linkend="typeconv">, but it is unwise to design a system that subtly
-    relies on this behavior.
-   </para>
-
-   <para>
-    A function that takes a single argument of a composite type should
-    generally not have the same name as any attribute (field) of that type.
-    Recall that <literal>attribute(table)</literal> is considered equivalent
-    to <literal>table.attribute</literal>.  In the case that there is an
-    ambiguity between a function on a composite type and an attribute of
-    the composite type, the attribute will always be used.  It is possible
-    to override that choice by schema-qualifying the function name
-    (that is, <literal>schema.func(table)</literal>) but it's better to
-    avoid the problem by not choosing conflicting names.
-   </para>
-
-   <para>
-    Another possible conflict is between variadic and non-variadic functions.
-    For instance, it is possible to create both <literal>foo(numeric)</> and
-    <literal>foo(VARIADIC numeric[])</>.  In this case it is unclear which one
-    should be matched to a call providing a single numeric argument, such as
-    <literal>foo(10.1)</>.  The rule is that the function appearing
-    earlier in the search path is used, or if the two functions are in the
-    same schema, the non-variadic one is preferred.
-   </para>
-
-   <para>
-    When overloading C-language functions, there is an additional
-    constraint: The C name of each function in the family of
-    overloaded functions must be different from the C names of all
-    other functions, either internal or dynamically loaded.  If this
-    rule is violated, the behavior is not portable.  You might get a
-    run-time linker error, or one of the functions will get called
-    (usually the internal one).  The alternative form of the
-    <literal>AS</> clause for the SQL <command>CREATE
-    FUNCTION</command> command decouples the SQL function name from
-    the function name in the C source code.  For instance:
-<programlisting>
-CREATE FUNCTION test(int) RETURNS int
-    AS '<replaceable>filename</>', 'test_1arg'
-    LANGUAGE C;
-CREATE FUNCTION test(int, int) RETURNS int
-    AS '<replaceable>filename</>', 'test_2arg'
-    LANGUAGE C;
-</programlisting>
-    The names of the C functions here reflect one of many possible conventions.
-   </para>
-  </sect1>
-
-  <sect1 id="xfunc-volatility">
-   <title>Function Volatility Categories</title>
-
-   <indexterm zone="xfunc-volatility">
-    <primary>volatility</primary>
-    <secondary>functions</secondary>
-   </indexterm>
-   <indexterm zone="xfunc-volatility">
-    <primary>VOLATILE</primary>
-   </indexterm>
-   <indexterm zone="xfunc-volatility">
-    <primary>STABLE</primary>
-   </indexterm>
-   <indexterm zone="xfunc-volatility">
-    <primary>IMMUTABLE</primary>
-   </indexterm>
-&common;
-   <para>
-    Every function has a <firstterm>volatility</> classification, with
-    the possibilities being <literal>VOLATILE</>, <literal>STABLE</>, or
-    <literal>IMMUTABLE</>.  <literal>VOLATILE</> is the default if the
-    <xref linkend="sql-createfunction">
-    command does not specify a category.  The volatility category is a
-    promise to the optimizer about the behavior of the function:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      A <literal>VOLATILE</> function can do anything, including modifying
-      the database.  It can return different results on successive calls with
-      the same arguments.  The optimizer makes no assumptions about the
-      behavior of such functions.  A query using a volatile function will
-      re-evaluate the function at every row where its value is needed.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      A <literal>STABLE</> function cannot modify the database and is
-      guaranteed to return the same results given the same arguments
-      for all rows within a single statement. This category allows the
-      optimizer to optimize multiple calls of the function to a single
-      call. In particular, it is safe to use an expression containing
-      such a function in an index scan condition. (Since an index scan
-      will evaluate the comparison value only once, not once at each
-      row, it is not valid to use a <literal>VOLATILE</> function in an
-      index scan condition.)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      An <literal>IMMUTABLE</> function cannot modify the database and is
-      guaranteed to return the same results given the same arguments forever.
-      This category allows the optimizer to pre-evaluate the function when
-      a query calls it with constant arguments.  For example, a query like
-      <literal>SELECT ... WHERE x = 2 + 2</> can be simplified on sight to
-      <literal>SELECT ... WHERE x = 4</>, because the function underlying
-      the integer addition operator is marked <literal>IMMUTABLE</>.
-     </para>
-    </listitem>
-   </itemizedlist>
-   </para>
-
-   <para>
-    For best optimization results, you should label your functions with the
-    strictest volatility category that is valid for them.
-   </para>
-
-   <para>
-    Any function with side-effects <emphasis>must</> be labeled
-    <literal>VOLATILE</>, so that calls to it cannot be optimized away.
-    Even a function with no side-effects needs to be labeled
-    <literal>VOLATILE</> if its value can change within a single query;
-    some examples are <literal>random()</>, <literal>currval()</>,
-    <literal>timeofday()</>.
-   </para>
-
-   <para>
-    Another important example is that the <function>current_timestamp</>
-    family of functions qualify as <literal>STABLE</>, since their values do
-    not change within a transaction.
-   </para>
-
-   <para>
-    There is relatively little difference between <literal>STABLE</> and
-    <literal>IMMUTABLE</> categories when considering simple interactive
-    queries that are planned and immediately executed: it doesn't matter
-    a lot whether a function is executed once during planning or once during
-    query execution startup.  But there is a big difference if the plan is
-    saved and reused later.  Labeling a function <literal>IMMUTABLE</> when
-    it really isn't might allow it to be prematurely folded to a constant during
-    planning, resulting in a stale value being re-used during subsequent uses
-    of the plan.  This is a hazard when using prepared statements or when
-    using function languages that cache plans (such as
-    <application>PL/pgSQL</>).
-   </para>
-
-   <para>
-    For functions written in SQL or in any of the standard procedural
-    languages, there is a second important property determined by the
-    volatility category, namely the visibility of any data changes that have
-    been made by the SQL command that is calling the function.  A
-    <literal>VOLATILE</> function will see such changes, a <literal>STABLE</>
-    or <literal>IMMUTABLE</> function will not.  This behavior is implemented
-    using the snapshotting behavior of MVCC (see <xref linkend="mvcc">):
-    <literal>STABLE</> and <literal>IMMUTABLE</> functions use a snapshot
-    established as of the start of the calling query, whereas
-    <literal>VOLATILE</> functions obtain a fresh snapshot at the start of
-    each query they execute.
-   </para>
-
-   <note>
-    <para>
-     Functions written in C can manage snapshots however they want, but it's
-     usually a good idea to make C functions work this way too.
-    </para>
-   </note>
-
-   <para>
-    Because of this snapshotting behavior,
-    a function containing only <command>SELECT</> commands can safely be
-    marked <literal>STABLE</>, even if it selects from tables that might be
-    undergoing modifications by concurrent queries.
-<!## PG>
-    <productname>PostgreSQL</productname> will execute all commands of a
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> will execute all commands of a
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> will execute all commands of a
-<!## end>
-    <literal>STABLE</> function using the snapshot established for the
-    calling query, and so it will see a fixed view of the database throughout
-    that query.
-   </para>
-
-   <para>
-    The same snapshotting behavior is used for <command>SELECT</> commands
-    within <literal>IMMUTABLE</> functions.  It is generally unwise to select
-    from database tables within an <literal>IMMUTABLE</> function at all,
-    since the immutability will be broken if the table contents ever change.
-<!## PG>
-    However, <productname>PostgreSQL</productname> does not enforce that you
-<!## end>
-<!## XC>
-    However, <productname>Postgres-XC</productname> does not enforce that you
-<!## end>
-<!## XL>
-    However, <productname>Postgres-XL</productname> does not enforce that you
-<!## end>
-    do not do that.
-   </para>
-
-   <para>
-    A common error is to label a function <literal>IMMUTABLE</> when its
-    results depend on a configuration parameter.  For example, a function
-    that manipulates timestamps might well have results that depend on the
-    <xref linkend="guc-timezone"> setting.  For safety, such functions should
-    be labeled <literal>STABLE</> instead.
-   </para>
-
-   <note>
-    <para>
-     Before <productname>PostgreSQL</productname> release 8.0, the requirement
-     that <literal>STABLE</> and <literal>IMMUTABLE</> functions cannot modify
-     the database was not enforced by the system.  Releases 8.0 and later enforce it
-     by requiring SQL functions and procedural language functions of these
-     categories to contain no SQL commands other than <command>SELECT</>.
-     (This is not a completely bulletproof test, since such functions could
-     still call <literal>VOLATILE</> functions that modify the database.
-     If you do that, you will find that the <literal>STABLE</> or
-     <literal>IMMUTABLE</> function does not notice the database changes
-     applied by the called function, since they are hidden from its snapshot.)
-    </para>
-   </note>
-  </sect1>
-
-  <sect1 id="xfunc-pl">
-   <title>Procedural Language Functions</title>
-&common;
-   <para>
-<!## PG>
-    <productname>PostgreSQL</productname> allows user-defined functions
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> allows user-defined functions
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> allows user-defined functions
-<!## end>
-    to be written in other languages besides SQL and C.  These other
-    languages are generically called <firstterm>procedural
-    languages</firstterm> (<acronym>PL</>s).
-    Procedural languages aren't built into the
-<!## PG>
-    <productname>PostgreSQL</productname> server; they are offered
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname> server; they are offered
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname> server; they are offered
-<!## end>
-    by loadable modules.
-    See <xref linkend="xplang"> and following chapters for more
-    information.
-   </para>
-  </sect1>
-
-  <sect1 id="xfunc-internal">
-   <title>Internal Functions</title>
-
-   <indexterm zone="xfunc-internal"><primary>function</><secondary>internal</></>
-&common;
-   <para>
-    Internal functions are functions written in C that have been statically
-<!## PG>
-    linked into the <productname>PostgreSQL</productname> server.
-<!## end>
-<!## XC>
-    linked into the <productname>Postgres-XC</productname> server.
-<!## end>
-<!## XL>
-    linked into the <productname>Postgres-XL</productname> server.
-<!## end>
-    The <quote>body</quote> of the function definition
-    specifies the C-language name of the function, which need not be the
-    same as the name being declared for SQL use.
-    (For reasons of backward compatibility, an empty body
-    is accepted as meaning that the C-language function name is the
-    same as the SQL name.)
-   </para>
-
-   <para>
-    Normally, all internal functions present in the
-    server are declared during the initialization of the database cluster
-    (see <xref linkend="creating-cluster">),
-    but a user could use <command>CREATE FUNCTION</command>
-    to create additional alias names for an internal function.
-    Internal functions are declared in <command>CREATE FUNCTION</command>
-    with language name <literal>internal</literal>.  For instance, to
-    create an alias for the <function>sqrt</function> function:
-<programlisting>
-CREATE FUNCTION square_root(double precision) RETURNS double precision
-    AS 'dsqrt'
-    LANGUAGE internal
-    STRICT;
-</programlisting>
-    (Most internal functions expect to be declared <quote>strict</quote>.)
-   </para>
-
-   <note>
-    <para>
-     Not all <quote>predefined</quote> functions are
-     <quote>internal</quote> in the above sense.  Some predefined
-     functions are written in SQL.
-    </para>
-   </note>
-  </sect1>
-
-  <sect1 id="xfunc-c">
-   <title>C-Language Functions</title>
-
-   <indexterm zone="xfunc-c">
-    <primary>function</primary>
-    <secondary>user-defined</secondary>
-    <tertiary>in C</tertiary>
-   </indexterm>
-&common;
-   <para>
-    User-defined functions can be written in C (or a language that can
-    be made compatible with C, such as C++).  Such functions are
-    compiled into dynamically loadable objects (also called shared
-    libraries) and are loaded by the server on demand.  The dynamic
-    loading feature is what distinguishes <quote>C language</> functions
-    from <quote>internal</> functions &mdash; the actual coding conventions
-    are essentially the same for both.  (Hence, the standard internal
-    function library is a rich source of coding examples for user-defined
-    C functions.)
-   </para>
-
-   <para>
-    Two different calling conventions are currently used for C functions.
-    The newer <quote>version 1</quote> calling convention is indicated by writing
-    a <literal>PG_FUNCTION_INFO_V1()</literal> macro call for the function,
-    as illustrated below.  Lack of such a macro indicates an old-style
-    (<quote>version 0</quote>) function.  The language name specified in <command>CREATE FUNCTION</command>
-    is <literal>C</literal> in either case.  Old-style functions are now deprecated
-    because of portability problems and lack of functionality, but they
-    are still supported for compatibility reasons.
-   </para>
-
-  <sect2 id="xfunc-c-dynload">
-   <title>Dynamic Loading</title>
-
-   <indexterm zone="xfunc-c-dynload">
-    <primary>dynamic loading</primary>
-   </indexterm>
-&common;
-   <para>
-    The first time a user-defined function in a particular
-    loadable object file is called in a session,
-    the dynamic loader loads that object file into memory so that the
-    function can be called.  The <command>CREATE FUNCTION</command>
-    for a user-defined C function must therefore specify two pieces of
-    information for the function: the name of the loadable
-    object file, and the C name (link symbol) of the specific function to call
-    within that object file.  If the C name is not explicitly specified then
-    it is assumed to be the same as the SQL function name.
-   </para>
-
-   <para>
-    The following algorithm is used to locate the shared object file
-    based on the name given in the <command>CREATE FUNCTION</command>
-    command:
-
-    <orderedlist>
-     <listitem>
-      <para>
-       If the name is an absolute path, the given file is loaded.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If the name starts with the string <literal>$libdir</literal>,
-<!## PG>
-       that part is replaced by the <productname>PostgreSQL</> package
-<!## end>
-<!## XC>
-       that part is replaced by the <productname>Postgres-XC</> package
-<!## end>
-<!## XL>
-       that part is replaced by the <productname>Postgres-XL</> package
-<!## end>
-        library directory
-       name, which is determined at build time.<indexterm><primary>$libdir</></>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If the name does not contain a directory part, the file is
-       searched for in the path specified by the configuration variable
-       <xref linkend="guc-dynamic-library-path">.<indexterm><primary>dynamic_library_path</></>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Otherwise (the file was not found in the path, or it contains a
-       non-absolute directory part), the dynamic loader will try to
-       take the name as given, which will most likely fail.  (It is
-       unreliable to depend on the current working directory.)
-      </para>
-     </listitem>
-    </orderedlist>
-
-    If this sequence does not work, the platform-specific shared
-    library file name extension (often <filename>.so</filename>) is
-    appended to the given name and this sequence is tried again.  If
-    that fails as well, the load will fail.
-   </para>
-
-   <para>
-    It is recommended to locate shared libraries either relative to
-    <literal>$libdir</literal> or through the dynamic library path.
-    This simplifies version upgrades if the new installation is at a
-    different location.  The actual directory that
-    <literal>$libdir</literal> stands for can be found out with the
-    command <literal>pg_config --pkglibdir</literal>.
-   </para>
-
-   <para>
-<!## PG>
-    The user ID the <productname>PostgreSQL</productname> server runs
-<!## end>
-<!## XC>
-    The user ID the <productname>Postgres-XC</productname> server runs
-<!## end>
-<!## XL>
-    The user ID the <productname>Postgres-XL</productname> server runs
-<!## end>
-    as must be able to traverse the path to the file you intend to
-    load.  Making the file or a higher-level directory not readable
-    and/or not executable by the <systemitem>postgres</systemitem>
-    user is a common mistake.
-   </para>
-
-   <para>
-    In any case, the file name that is given in the
-    <command>CREATE FUNCTION</command> command is recorded literally
-    in the system catalogs, so if the file needs to be loaded again
-    the same procedure is applied.
-   </para>
-
-   <note>
-    <para>
-<!## PG>
-     <productname>PostgreSQL</productname> will not compile a C function
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> will not compile a C function
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> will not compile a C function
-<!## end>
-     automatically.  The object file must be compiled before it is referenced
-     in a <command>CREATE
-     FUNCTION</> command.  See <xref linkend="dfunc"> for additional
-     information.
-    </para>
-   </note>
-
-   <indexterm zone="xfunc-c-dynload">
-    <primary>magic block</primary>
-   </indexterm>
-
-   <para>
-    To ensure that a dynamically loaded object file is not loaded into an
-<!## PG>
-    incompatible server, <productname>PostgreSQL</productname> checks that the
-<!## end>
-<!## XC>
-    incompatible server, <productname>Postgres-XC</productname> checks that the
-<!## end>
-<!## XL>
-    incompatible server, <productname>Postgres-XL</productname> checks that the
-<!## end>
-    file contains a <quote>magic block</> with the appropriate contents.
-    This allows the server to detect obvious incompatibilities, such as code
-    compiled for a different major version of
-<!## PG>
-    <productname>PostgreSQL</productname>.  A magic block is required as of
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>.  A magic block is required as of
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>.  A magic block is required as of
-<!## end>
-    <productname>PostgreSQL</productname> 8.2.  To include a magic block,
-    write this in one (and only one) of the module source files, after having
-    included the header <filename>fmgr.h</>:
-
-<programlisting>
-#ifdef PG_MODULE_MAGIC
-PG_MODULE_MAGIC;
-#endif
-</programlisting>
-
-    The <literal>#ifdef</> test can be omitted if the code doesn't
-    need to compile against pre-8.2 <productname>PostgreSQL</productname>
-    releases.
-   </para>
-
-   <para>
-    After it is used for the first time, a dynamically loaded object
-    file is retained in memory.  Future calls in the same session to
-    the function(s) in that file will only incur the small overhead of
-    a symbol table lookup.  If you need to force a reload of an object
-    file, for example after recompiling it, begin a fresh session.
-   </para>
-
-   <indexterm zone="xfunc-c-dynload">
-    <primary>_PG_init</primary>
-   </indexterm>
-   <indexterm zone="xfunc-c-dynload">
-    <primary>_PG_fini</primary>
-   </indexterm>
-   <indexterm zone="xfunc-c-dynload">
-    <primary>library initialization function</primary>
-   </indexterm>
-   <indexterm zone="xfunc-c-dynload">
-    <primary>library finalization function</primary>
-   </indexterm>
-
-   <para>
-    Optionally, a dynamically loaded file can contain initialization and
-    finalization functions.  If the file includes a function named
-    <function>_PG_init</>, that function will be called immediately after
-    loading the file.  The function receives no parameters and should
-    return void.  If the file includes a function named
-    <function>_PG_fini</>, that function will be called immediately before
-    unloading the file.  Likewise, the function receives no parameters and
-    should return void.  Note that <function>_PG_fini</> will only be called
-    during an unload of the file, not during process termination.
-    (Presently, unloads are disabled and will never occur, but this may
-    change in the future.)
-   </para>
-
-  </sect2>
-
-   <sect2 id="xfunc-c-basetype">
-    <title>Base Types in C-Language Functions</title>
-
-    <indexterm zone="xfunc-c-basetype">
-     <primary>data type</primary>
-     <secondary>internal organization</secondary>
-    </indexterm>
-&common;
-<!## PG>
-    <para>
-     To know how to write C-language functions, you need to know how
-     <productname>PostgreSQL</productname> internally represents base
-     data types and how they can be passed to and from functions.
-     Internally, <productname>PostgreSQL</productname> regards a base
-     type as a <quote>blob of memory</quote>.  The user-defined
-     functions that you define over a type in turn define the way that
-     <productname>PostgreSQL</productname> can operate on it.  That
-     is, <productname>PostgreSQL</productname> will only store and
-     retrieve the data from disk and use your user-defined functions
-     to input, process, and output the data.
-    </para>
-<!## end>
-<!## XC>
-    <para>
-     To know how to write C-language functions, you need to know how
-     <productname>Postgres-XC</productname> internally represents base
-     data types and how they can be passed to and from functions.
-     Internally, <productname>Postgres-XC</productname> regards a base
-     type as a <quote>blob of memory</quote>.  The user-defined
-     functions that you define over a type in turn define the way that
-     <productname>Postgres-XC</productname> can operate on it.  That
-     is, <productname>Postgres-XC</productname> will only store and
-     retrieve the data from disk and use your user-defined functions
-     to input, process, and output the data.
-    </para>
-<!## end>
-<!## XL>
-    <para>
-     To know how to write C-language functions, you need to know how
-     <productname>Postgres-XL</productname> internally represents base
-     data types and how they can be passed to and from functions.
-     Internally, <productname>Postgres-XL</productname> regards a base
-     type as a <quote>blob of memory</quote>.  The user-defined
-     functions that you define over a type in turn define the way that
-     <productname>Postgres-XL</productname> can operate on it.  That
-     is, <productname>Postgres-XL</productname> will only store and
-     retrieve the data from disk and use your user-defined functions
-     to input, process, and output the data.
-    </para>
-<!## end>
-
-    <para>
-     Base types can have one of three internal formats:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        pass by value, fixed-length
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        pass by reference, fixed-length
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        pass by reference, variable-length
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     By-value  types  can  only be 1, 2, or 4 bytes in length
-     (also 8 bytes, if <literal>sizeof(Datum)</literal> is 8 on your machine).
-     You should be careful to define your types such that they will be the
-     same size (in bytes) on all architectures.  For example, the
-     <literal>long</literal> type is dangerous because it is 4 bytes on some
-     machines and 8 bytes on others, whereas <type>int</type> type is 4 bytes
-     on most Unix machines.  A reasonable implementation of the
-     <type>int4</type> type on Unix machines might be:
-
-<programlisting>
-/* 4-byte integer, passed by value */
-typedef int int4;
-</programlisting>
-    </para>
-
-    <para>
-     On  the  other hand, fixed-length types of any size can
-     be passed by-reference.  For example, here is a  sample
-<!## PG>
-     implementation of a <productname>PostgreSQL</productname> type:
-<!## end>
-<!## XC>
-     implementation of a <productname>Postgres-XC</productname> type:
-<!## end>
-<!## XL>
-     implementation of a <productname>Postgres-XL</productname> type:
-<!## end>
-
-<programlisting>
-/* 16-byte structure, passed by reference */
-typedef struct
-{
-    double  x, y;
-} Point;
-</programlisting>
-
-     Only  pointers  to  such types can be used when passing
-<!## PG>
-     them in and out of <productname>PostgreSQL</productname> functions.
-<!## end>
-<!## XC>
-     them in and out of <productname>Postgres-XC</productname> functions.
-<!## end>
-<!## XL>
-     them in and out of <productname>Postgres-XL</productname> functions.
-<!## end>
-     To return a value of such a type, allocate the right amount of
-     memory with <literal>palloc</literal>, fill in the allocated memory,
-     and return a pointer to it.  (Also, if you just want to return the
-     same value as one of your input arguments that's of the same data type,
-     you can skip the extra <literal>palloc</literal> and just return the
-     pointer to the input value.)
-    </para>
-
-    <para>
-     Finally, all variable-length types must also be  passed
-     by  reference.   All  variable-length  types must begin
-     with a length field of exactly 4 bytes, and all data to
-     be  stored within that type must be located in the memory
-     immediately  following  that  length  field.   The
-     length field contains the total length of the structure,
-     that is,  it  includes  the  size  of  the  length  field
-     itself.
-    </para>
-
-    <warning>
-     <para>
-      <emphasis>Never</> modify the contents of a pass-by-reference input
-      value.  If you do so you are likely to corrupt on-disk data, since
-      the pointer you are given might point directly into a disk buffer.
-      The sole exception to this rule is explained in
-      <xref linkend="xaggr">.
-     </para>
-    </warning>
-
-    <para>
-     As an example, we can define the type <type>text</type> as
-     follows:
-
-<programlisting>
-typedef struct {
-    int4 length;
-    char data[1];
-} text;
-</programlisting>
-
-     Obviously,  the  data  field declared here is not long enough to hold
-     all possible strings.  Since it's impossible to declare a variable-size
-     structure in <acronym>C</acronym>, we rely on the knowledge that the
-     <acronym>C</acronym> compiler won't range-check array subscripts.  We
-     just allocate the necessary amount of space and then access the array as
-     if it were declared the right length.  (This is a common trick, which
-     you can read about in many textbooks about C.)
-    </para>
-
-    <para>
-     When manipulating
-     variable-length types, we must  be  careful  to  allocate
-     the  correct amount  of memory and set the length field correctly.
-     For example, if we wanted to  store  40  bytes  in  a <structname>text</>
-     structure, we might use a code fragment like this:
-
-<programlisting><![CDATA[
-#include "postgres.h"
-...
-char buffer[40]; /* our source data */
-...
-text *destination = (text *) palloc(VARHDRSZ + 40);
-destination->length = VARHDRSZ + 40;
-memcpy(destination->data, buffer, 40);
-...
-]]>
-</programlisting>
-
-     <literal>VARHDRSZ</> is the same as <literal>sizeof(int4)</>, but
-     it's considered good style to use the macro <literal>VARHDRSZ</>
-     to refer to the size of the overhead for a variable-length type.
-    </para>
-
-    <para>
-     <xref linkend="xfunc-c-type-table"> specifies which C type
-     corresponds to which SQL type when writing a C-language function
-<!## PG>
-     that uses a built-in type of <productname>PostgreSQL</>.
-<!## end>
-<!## XC>
-     that uses a built-in type of <productname>Postgres-XC</>.
-<!## end>
-<!## XL>
-     that uses a built-in type of <productname>Postgres-XL</>.
-<!## end>
-     The <quote>Defined In</quote> column gives the header file that
-     needs to be included to get the type definition.  (The actual
-     definition might be in a different file that is included by the
-     listed file.  It is recommended that users stick to the defined
-     interface.)  Note that you should always include
-     <filename>postgres.h</filename> first in any source file, because
-     it declares a number of things that you will need anyway.
-    </para>
-
-     <table tocentry="1" id="xfunc-c-type-table">
-      <title>Equivalent C Types for Built-in SQL Types</title>
-      <tgroup cols="3">
-       <thead>
-        <row>
-         <entry>
-          SQL Type
-         </entry>
-         <entry>
-          C Type
-         </entry>
-         <entry>
-          Defined In
-         </entry>
-        </row>
-       </thead>
-       <tbody>
-        <row>
-         <entry><type>abstime</type></entry>
-         <entry><type>AbsoluteTime</type></entry>
-         <entry><filename>utils/nabstime.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>boolean</type></entry>
-         <entry><type>bool</type></entry>
-         <entry><filename>postgres.h</filename> (maybe compiler built-in)</entry>
-        </row>
-        <row>
-         <entry><type>box</type></entry>
-         <entry><type>BOX*</type></entry>
-         <entry><filename>utils/geo_decls.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>bytea</type></entry>
-         <entry><type>bytea*</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>"char"</type></entry>
-         <entry><type>char</type></entry>
-         <entry>(compiler built-in)</entry>
-        </row>
-        <row>
-         <entry><type>character</type></entry>
-         <entry><type>BpChar*</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>cid</type></entry>
-         <entry><type>CommandId</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>date</type></entry>
-         <entry><type>DateADT</type></entry>
-         <entry><filename>utils/date.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>smallint</type> (<type>int2</type>)</entry>
-         <entry><type>int2</type> or <type>int16</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>int2vector</type></entry>
-         <entry><type>int2vector*</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>integer</type> (<type>int4</type>)</entry>
-         <entry><type>int4</type> or <type>int32</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>real</type> (<type>float4</type>)</entry>
-         <entry><type>float4*</type></entry>
-        <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>double precision</type> (<type>float8</type>)</entry>
-         <entry><type>float8*</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>interval</type></entry>
-         <entry><type>Interval*</type></entry>
-         <entry><filename>utils/timestamp.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>lseg</type></entry>
-         <entry><type>LSEG*</type></entry>
-         <entry><filename>utils/geo_decls.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>name</type></entry>
-         <entry><type>Name</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>oid</type></entry>
-         <entry><type>Oid</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>oidvector</type></entry>
-         <entry><type>oidvector*</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>path</type></entry>
-         <entry><type>PATH*</type></entry>
-         <entry><filename>utils/geo_decls.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>point</type></entry>
-         <entry><type>POINT*</type></entry>
-         <entry><filename>utils/geo_decls.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>regproc</type></entry>
-         <entry><type>regproc</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>reltime</type></entry>
-         <entry><type>RelativeTime</type></entry>
-         <entry><filename>utils/nabstime.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>text</type></entry>
-         <entry><type>text*</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>tid</type></entry>
-         <entry><type>ItemPointer</type></entry>
-         <entry><filename>storage/itemptr.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>time</type></entry>
-         <entry><type>TimeADT</type></entry>
-         <entry><filename>utils/date.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>time with time zone</type></entry>
-         <entry><type>TimeTzADT</type></entry>
-         <entry><filename>utils/date.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>timestamp</type></entry>
-         <entry><type>Timestamp*</type></entry>
-         <entry><filename>utils/timestamp.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>tinterval</type></entry>
-         <entry><type>TimeInterval</type></entry>
-         <entry><filename>utils/nabstime.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>varchar</type></entry>
-         <entry><type>VarChar*</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-        <row>
-         <entry><type>xid</type></entry>
-         <entry><type>TransactionId</type></entry>
-         <entry><filename>postgres.h</filename></entry>
-        </row>
-       </tbody>
-      </tgroup>
-     </table>
-
-    <para>
-     Now that we've gone over all of the possible structures
-     for base types, we can show some examples of real functions.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Version 0 Calling Conventions</title>
-&common;
-    <para>
-     We present the <quote>old style</quote> calling convention first &mdash; although
-     this approach is now deprecated, it's easier to get a handle on
-     initially.  In the version-0 method, the arguments and result
-     of the C function are just declared in normal C style, but being
-     careful to use the C representation of each SQL data type as shown
-     above.
-    </para>
-
-    <para>
-     Here are some examples:
-
-<programlisting><![CDATA[
-#include "postgres.h"
-#include <string.h>
-#include "utils/geo_decls.h"
-
-#ifdef PG_MODULE_MAGIC
-PG_MODULE_MAGIC;
-#endif
-
-/* by value */
-
-int
-add_one(int arg)
-{
-    return arg + 1;
-}
-
-/* by reference, fixed length */
-
-float8 *
-add_one_float8(float8 *arg)
-{
-    float8    *result = (float8 *) palloc(sizeof(float8));
-
-    *result = *arg + 1.0;
-
-    return result;
-}
-
-Point *
-makepoint(Point *pointx, Point *pointy)
-{
-    Point     *new_point = (Point *) palloc(sizeof(Point));
-
-    new_point->x = pointx->x;
-    new_point->y = pointy->y;
-
-    return new_point;
-}
-
-/* by reference, variable length */
-
-text *
-copytext(text *t)
-{
-    /*
-     * VARSIZE is the total size of the struct in bytes.
-     */
-    text *new_t = (text *) palloc(VARSIZE(t));
-    SET_VARSIZE(new_t, VARSIZE(t));
-    /*
-     * VARDATA is a pointer to the data region of the struct.
-     */
-    memcpy((void *) VARDATA(new_t), /* destination */
-           (void *) VARDATA(t),     /* source */
-           VARSIZE(t) - VARHDRSZ);  /* how many bytes */
-    return new_t;
-}
-
-text *
-concat_text(text *arg1, text *arg2)
-{
-    int32 new_text_size = VARSIZE(arg1) + VARSIZE(arg2) - VARHDRSZ;
-    text *new_text = (text *) palloc(new_text_size);
-
-    SET_VARSIZE(new_text, new_text_size);
-    memcpy(VARDATA(new_text), VARDATA(arg1), VARSIZE(arg1) - VARHDRSZ);
-    memcpy(VARDATA(new_text) + (VARSIZE(arg1) - VARHDRSZ),
-           VARDATA(arg2), VARSIZE(arg2) - VARHDRSZ);
-    return new_text;
-}
-]]>
-</programlisting>
-    </para>
-
-    <para>
-     Supposing that the above code has been prepared in file
-     <filename>funcs.c</filename> and compiled into a shared object,
-<!## PG>
-     we could define the functions to <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-     we could define the functions to <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-     we could define the functions to <productname>Postgres-XL</productname>
-<!## end>
-     with commands like this:
-
-<programlisting>
-CREATE FUNCTION add_one(integer) RETURNS integer
-     AS '<replaceable>DIRECTORY</replaceable>/funcs', 'add_one'
-     LANGUAGE C STRICT;
-
--- note overloading of SQL function name "add_one"
-CREATE FUNCTION add_one(double precision) RETURNS double precision
-     AS '<replaceable>DIRECTORY</replaceable>/funcs', 'add_one_float8'
-     LANGUAGE C STRICT;
-
-CREATE FUNCTION makepoint(point, point) RETURNS point
-     AS '<replaceable>DIRECTORY</replaceable>/funcs', 'makepoint'
-     LANGUAGE C STRICT;
-
-CREATE FUNCTION copytext(text) RETURNS text
-     AS '<replaceable>DIRECTORY</replaceable>/funcs', 'copytext'
-     LANGUAGE C STRICT;
-
-CREATE FUNCTION concat_text(text, text) RETURNS text
-     AS '<replaceable>DIRECTORY</replaceable>/funcs', 'concat_text'
-     LANGUAGE C STRICT;
-</programlisting>
-    </para>
-
-    <para>
-     Here, <replaceable>DIRECTORY</replaceable> stands for the
-     directory of the shared library file (for instance the
-<!## PG>
-     <productname>PostgreSQL</productname> tutorial directory, which
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> tutorial directory, which
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> tutorial directory, which
-<!## end>
-     contains the code for the examples used in this section).
-     (Better style would be to use just <literal>'funcs'</> in the
-     <literal>AS</> clause, after having added
-     <replaceable>DIRECTORY</replaceable> to the search path.  In any
-     case, we can omit the system-specific extension for a shared
-     library, commonly <literal>.so</literal> or
-     <literal>.sl</literal>.)
-    </para>
-
-    <para>
-     Notice that we have specified the functions as <quote>strict</quote>,
-     meaning that
-     the system should automatically assume a null result if any input
-     value is null.  By doing this, we avoid having to check for null inputs
-     in the function code.  Without this, we'd have to check for null values
-     explicitly, by checking for a null pointer for each
-     pass-by-reference argument.  (For pass-by-value arguments, we don't
-     even have a way to check!)
-    </para>
-
-    <para>
-     Although this calling convention is simple to use,
-     it is not very portable; on some architectures there are problems
-     with passing data types that are smaller than <type>int</type> this way.  Also, there is
-     no simple way to return a null result, nor to cope with null arguments
-     in any way other than making the function strict.  The version-1
-     convention, presented next, overcomes these objections.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Version 1 Calling Conventions</title>
-&common;
-    <para>
-     The version-1 calling convention relies on macros to suppress most
-     of the complexity of passing arguments and results.  The C declaration
-     of a version-1 function is always:
-<programlisting>
-Datum funcname(PG_FUNCTION_ARGS)
-</programlisting>
-     In addition, the macro call:
-<programlisting>
-PG_FUNCTION_INFO_V1(funcname);
-</programlisting>
-     must appear in the same source file.  (Conventionally, it's
-     written just before the function itself.)  This macro call is not
-     needed for <literal>internal</>-language functions, since
-<!## PG>
-     <productname>PostgreSQL</> assumes that all internal functions
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</> assumes that all internal functions
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</> assumes that all internal functions
-<!## end>
-     use the version-1 convention.  It is, however, required for
-     dynamically-loaded functions.
-    </para>
-
-    <para>
-     In a version-1 function, each actual argument is fetched using a
-     <function>PG_GETARG_<replaceable>xxx</replaceable>()</function>
-     macro that corresponds to the argument's data type, and the
-     result is returned using a
-     <function>PG_RETURN_<replaceable>xxx</replaceable>()</function>
-     macro for the return type.
-     <function>PG_GETARG_<replaceable>xxx</replaceable>()</function>
-     takes as its argument the number of the function argument to
-     fetch, where the count starts at 0.
-     <function>PG_RETURN_<replaceable>xxx</replaceable>()</function>
-     takes as its argument the actual value to return.
-    </para>
-
-    <para>
-     Here we show the same functions as above, coded in version-1 style:
-
-<programlisting><![CDATA[
-#include "postgres.h"
-#include <string.h>
-#include "fmgr.h"
-#include "utils/geo_decls.h"
-
-#ifdef PG_MODULE_MAGIC
-PG_MODULE_MAGIC;
-#endif
-
-/* by value */
-
-PG_FUNCTION_INFO_V1(add_one);
-
-Datum
-add_one(PG_FUNCTION_ARGS)
-{
-    int32   arg = PG_GETARG_INT32(0);
-
-    PG_RETURN_INT32(arg + 1);
-}
-
-/* by reference, fixed length */
-
-PG_FUNCTION_INFO_V1(add_one_float8);
-
-Datum
-add_one_float8(PG_FUNCTION_ARGS)
-{
-    /* The macros for FLOAT8 hide its pass-by-reference nature. */
-    float8   arg = PG_GETARG_FLOAT8(0);
-
-    PG_RETURN_FLOAT8(arg + 1.0);
-}
-
-PG_FUNCTION_INFO_V1(makepoint);
-
-Datum
-makepoint(PG_FUNCTION_ARGS)
-{
-    /* Here, the pass-by-reference nature of Point is not hidden. */
-    Point     *pointx = PG_GETARG_POINT_P(0);
-    Point     *pointy = PG_GETARG_POINT_P(1);
-    Point     *new_point = (Point *) palloc(sizeof(Point));
-
-    new_point->x = pointx->x;
-    new_point->y = pointy->y;
-
-    PG_RETURN_POINT_P(new_point);
-}
-
-/* by reference, variable length */
-
-PG_FUNCTION_INFO_V1(copytext);
-
-Datum
-copytext(PG_FUNCTION_ARGS)
-{
-    text     *t = PG_GETARG_TEXT_P(0);
-    /*
-     * VARSIZE is the total size of the struct in bytes.
-     */
-    text     *new_t = (text *) palloc(VARSIZE(t));
-    SET_VARSIZE(new_t, VARSIZE(t));
-    /*
-     * VARDATA is a pointer to the data region of the struct.
-     */
-    memcpy((void *) VARDATA(new_t), /* destination */
-           (void *) VARDATA(t),     /* source */
-           VARSIZE(t) - VARHDRSZ);  /* how many bytes */
-    PG_RETURN_TEXT_P(new_t);
-}
-
-PG_FUNCTION_INFO_V1(concat_text);
-
-Datum
-concat_text(PG_FUNCTION_ARGS)
-{
-    text  *arg1 = PG_GETARG_TEXT_P(0);
-    text  *arg2 = PG_GETARG_TEXT_P(1);
-    int32 new_text_size = VARSIZE(arg1) + VARSIZE(arg2) - VARHDRSZ;
-    text *new_text = (text *) palloc(new_text_size);
-
-    SET_VARSIZE(new_text, new_text_size);
-    memcpy(VARDATA(new_text), VARDATA(arg1), VARSIZE(arg1) - VARHDRSZ);
-    memcpy(VARDATA(new_text) + (VARSIZE(arg1) - VARHDRSZ),
-           VARDATA(arg2), VARSIZE(arg2) - VARHDRSZ);
-    PG_RETURN_TEXT_P(new_text);
-}
-]]>
-</programlisting>
-    </para>
-
-    <para>
-     The <command>CREATE FUNCTION</command> commands are the same as
-     for the version-0 equivalents.
-    </para>
-
-    <para>
-     At first glance, the version-1 coding conventions might appear to
-     be just pointless obscurantism.  They do, however, offer a number
-     of improvements, because the macros can hide unnecessary detail.
-     An example is that in coding <function>add_one_float8</>, we no longer need to
-     be aware that <type>float8</type> is a pass-by-reference type.  Another
-     example is that the <literal>GETARG</> macros for variable-length types allow
-     for more efficient fetching of <quote>toasted</quote> (compressed or
-     out-of-line) values.
-    </para>
-
-    <para>
-     One big improvement in version-1 functions is better handling of null
-     inputs and results.  The macro <function>PG_ARGISNULL(<replaceable>n</>)</function>
-     allows a function to test whether each input is null.  (Of course, doing
-     this is only necessary in functions not declared <quote>strict</>.)
-     As with the
-     <function>PG_GETARG_<replaceable>xxx</replaceable>()</function> macros,
-     the input arguments are counted beginning at zero.  Note that one
-     should refrain from executing
-     <function>PG_GETARG_<replaceable>xxx</replaceable>()</function> until
-     one has verified that the argument isn't null.
-     To return a null result, execute <function>PG_RETURN_NULL()</function>;
-     this works in both strict and nonstrict functions.
-    </para>
-
-    <para>
-     Other options provided in the new-style interface are two
-     variants of the
-     <function>PG_GETARG_<replaceable>xxx</replaceable>()</function>
-     macros. The first of these,
-     <function>PG_GETARG_<replaceable>xxx</replaceable>_COPY()</function>,
-     guarantees to return a copy of the specified argument that is
-     safe for writing into. (The normal macros will sometimes return a
-     pointer to a value that is physically stored in a table, which
-     must not be written to. Using the
-     <function>PG_GETARG_<replaceable>xxx</replaceable>_COPY()</function>
-     macros guarantees a writable result.)
-    The second variant consists of the
-    <function>PG_GETARG_<replaceable>xxx</replaceable>_SLICE()</function>
-    macros which take three arguments. The first is the number of the
-    function argument (as above). The second and third are the offset and
-    length of the segment to be returned. Offsets are counted from
-    zero, and a negative length requests that the remainder of the
-    value be returned. These macros provide more efficient access to
-    parts of large values in the case where they have storage type
-    <quote>external</quote>. (The storage type of a column can be specified using
-    <literal>ALTER TABLE <replaceable>tablename</replaceable> ALTER
-    COLUMN <replaceable>colname</replaceable> SET STORAGE
-    <replaceable>storagetype</replaceable></literal>. <replaceable>storagetype</replaceable> is one of
-    <literal>plain</>, <literal>external</>, <literal>extended</literal>,
-     or <literal>main</>.)
-    </para>
-
-    <para>
-     Finally, the version-1 function call conventions make it possible
-     to return set results (<xref linkend="xfunc-c-return-set">) and
-     implement trigger functions (<xref linkend="triggers">) and
-     procedural-language call handlers (<xref
-     linkend="plhandler">).  Version-1 code is also more
-     portable than version-0, because it does not break restrictions
-     on function call protocol in the C standard.  For more details
-     see <filename>src/backend/utils/fmgr/README</filename> in the
-     source distribution.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Writing Code</title>
-&common;
-    <para>
-     Before we turn to the more advanced topics, we should discuss
-<!## PG>
-     some coding rules for <productname>PostgreSQL</productname>
-     C-language functions.  While it might be possible to load functions
-     written in languages other than C into
-     <productname>PostgreSQL</productname>, this is usually difficult
-<!## end>
-<!## XC>
-     some coding rules for <productname>Postgres-XC</productname>
-     C-language functions.  While it might be possible to load functions
-     written in languages other than C into
-     <productname>Postgres-XC</productname>, this is usually difficult
-<!## end>
-<!## XL>
-     some coding rules for <productname>Postgres-XL</productname>
-     C-language functions.  While it might be possible to load functions
-     written in languages other than C into
-     <productname>Postgres-XL</productname>, this is usually difficult
-<!## end>
-     (when it is possible at all) because other languages, such as
-     C++, FORTRAN, or Pascal often do not follow the same calling
-     convention as C.  That is, other languages do not pass argument
-     and return values between functions in the same way.  For this
-     reason, we will assume that your C-language functions are
-     actually written in C.
-    </para>
-
-    <para>
-     The basic rules for writing and building C functions are as follows:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        Use <literal>pg_config
-        --includedir-server</literal><indexterm><primary>pg_config</><secondary>with user-defined C functions</></>
-<!## PG>
-        to find out where the <productname>PostgreSQL</> server header
-<!## end>
-<!## XC>
-        to find out where the <productname>Postgres-XC</> server header
-<!## end>
-<!## XL>
-        to find out where the <productname>Postgres-XL</> server header
-<!## end>
-        files are installed on your system (or the system that your
-        users will be running on).
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Compiling and linking your code so that it can be dynamically
-<!## PG>
-        loaded into <productname>PostgreSQL</productname> always
-<!## end>
-<!## XC>
-        loaded into <productname>Postgres-XC</productname> always
-<!## end>
-<!## XL>
-        loaded into <productname>Postgres-XL</productname> always
-<!## end>
-        requires special flags.  See <xref linkend="dfunc"> for a
-        detailed explanation of how to do it for your particular
-        operating system.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Remember to define a <quote>magic block</> for your shared library,
-        as described in <xref linkend="xfunc-c-dynload">.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        When allocating memory, use the
-<!## PG>
-        <productname>PostgreSQL</productname> functions
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> functions
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> functions
-<!## end>
-        <function>palloc</function><indexterm><primary>palloc</></> and <function>pfree</function><indexterm><primary>pfree</></>
-        instead of the corresponding C library functions
-        <function>malloc</function> and <function>free</function>.
-        The memory allocated by <function>palloc</function> will be
-        freed automatically at the end of each transaction, preventing
-        memory leaks.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Always zero the bytes of your structures using
-        <function>memset</function>.  Without this, it's difficult to
-        support hash indexes or hash joins, as you must pick out only
-        the significant bits of your data structure to compute a hash.
-        Even if you initialize all fields of your structure, there might be
-        alignment padding (holes in the structure) that contain
-        garbage values.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-<!## PG>
-        Most of the internal <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-        Most of the internal <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-        Most of the internal <productname>Postgres-XL</productname>
-<!## end>
-        types are declared in <filename>postgres.h</filename>, while
-        the function manager interfaces
-        (<symbol>PG_FUNCTION_ARGS</symbol>, etc.)  are in
-        <filename>fmgr.h</filename>, so you will need to include at
-        least these two files.  For portability reasons it's best to
-        include <filename>postgres.h</filename> <emphasis>first</>,
-        before any other system or user header files.  Including
-        <filename>postgres.h</filename> will also include
-        <filename>elog.h</filename> and <filename>palloc.h</filename>
-        for you.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Symbol names defined within object files must not conflict
-        with each other or with symbols defined in the
-<!## PG>
-        <productname>PostgreSQL</productname> server executable.  You
-<!## end>
-<!## XC>
-        <productname>Postgres-XC</productname> server executable.  You
-<!## end>
-<!## XL>
-        <productname>Postgres-XL</productname> server executable.  You
-<!## end>
-        will have to rename your functions or variables if you get
-        error messages to this effect.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </sect2>
-
-&dfunc;
-
-   <sect2>
-    <title>Composite-type Arguments</title>
-
-    <para>
-     Composite types do not have a fixed layout like C structures.
-     Instances of a composite type can contain null fields.  In
-     addition, composite types that are part of an inheritance
-     hierarchy can have different fields than other members of the
-     same inheritance hierarchy.  Therefore,
-<!## PG>
-     <productname>PostgreSQL</productname> provides a function
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> provides a function
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> provides a function
-<!## end>
-     interface for accessing fields of composite types from C.
-    </para>
-
-    <para>
-     Suppose we want to write a function to answer the query:
-
-<programlisting>
-SELECT name, c_overpaid(emp, 1500) AS overpaid
-    FROM emp
-    WHERE name = 'Bill' OR name = 'Sam';
-</programlisting>
-
-     Using call conventions version 0, we can define
-     <function>c_overpaid</> as:
-
-<programlisting><![CDATA[
-#include "postgres.h"
-#include "executor/executor.h"  /* for GetAttributeByName() */
-
-#ifdef PG_MODULE_MAGIC
-PG_MODULE_MAGIC;
-#endif
-
-bool
-c_overpaid(HeapTupleHeader t, /* the current row of emp */
-           int32 limit)
-{
-    bool isnull;
-    int32 salary;
-
-    salary = DatumGetInt32(GetAttributeByName(t, "salary", &isnull));
-    if (isnull)
-        return false;
-    return salary > limit;
-}
-]]>
-</programlisting>
-
-     In version-1 coding, the above would look like this:
-
-<programlisting><![CDATA[
-#include "postgres.h"
-#include "executor/executor.h"  /* for GetAttributeByName() */
-
-#ifdef PG_MODULE_MAGIC
-PG_MODULE_MAGIC;
-#endif
-
-PG_FUNCTION_INFO_V1(c_overpaid);
-
-Datum
-c_overpaid(PG_FUNCTION_ARGS)
-{
-    HeapTupleHeader  t = PG_GETARG_HEAPTUPLEHEADER(0);
-    int32            limit = PG_GETARG_INT32(1);
-    bool isnull;
-    Datum salary;
-
-    salary = GetAttributeByName(t, "salary", &isnull);
-    if (isnull)
-        PG_RETURN_BOOL(false);
-    /* Alternatively, we might prefer to do PG_RETURN_NULL() for null salary. */
-
-    PG_RETURN_BOOL(DatumGetInt32(salary) > limit);
-}
-]]>
-</programlisting>
-    </para>
-
-    <para>
-     <function>GetAttributeByName</function> is the
-<!## PG>
-     <productname>PostgreSQL</productname> system function that
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> system function that
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> system function that
-<!## end>
-     returns attributes out of the specified row.  It has
-     three arguments: the argument of type <type>HeapTupleHeader</type> passed
-     into
-     the  function, the name of the desired attribute, and a
-     return parameter that tells whether  the  attribute
-     is  null.   <function>GetAttributeByName</function> returns a <type>Datum</type>
-     value that you can convert to the proper data type by using the
-     appropriate <function>DatumGet<replaceable>XXX</replaceable>()</function>
-     macro.  Note that the return value is meaningless if the null flag is
-     set; always check the null flag before trying to do anything with the
-     result.
-    </para>
-
-    <para>
-     There is also <function>GetAttributeByNum</function>, which selects
-     the target attribute by column number instead of name.
-    </para>
-
-    <para>
-     The following command declares the function
-     <function>c_overpaid</function> in SQL:
-
-<programlisting>
-CREATE FUNCTION c_overpaid(emp, integer) RETURNS boolean
-    AS '<replaceable>DIRECTORY</replaceable>/funcs', 'c_overpaid'
-    LANGUAGE C STRICT;
-</programlisting>
-
-     Notice we have used <literal>STRICT</> so that we did not have to
-     check whether the input arguments were NULL.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Returning Rows (Composite Types)</title>
-&common;
-    <para>
-     To return a row or composite-type value from a C-language
-     function, you can use a special API that provides macros and
-     functions to hide most of the complexity of building composite
-     data types.  To use this API, the source file must include:
-<programlisting>
-#include "funcapi.h"
-</programlisting>
-    </para>
-
-    <para>
-     There are two ways you can build a composite data value (henceforth
-     a <quote>tuple</>): you can build it from an array of Datum values,
-     or from an array of C strings that can be passed to the input
-     conversion functions of the tuple's column data types.  In either
-     case, you first need to obtain or construct a <structname>TupleDesc</>
-     descriptor for the tuple structure.  When working with Datums, you
-     pass the <structname>TupleDesc</> to <function>BlessTupleDesc</>,
-     and then call <function>heap_form_tuple</> for each row.  When working
-     with C strings, you pass the <structname>TupleDesc</> to
-     <function>TupleDescGetAttInMetadata</>, and then call
-     <function>BuildTupleFromCStrings</> for each row.  In the case of a
-     function returning a set of tuples, the setup steps can all be done
-     once during the first call of the function.
-    </para>
-
-    <para>
-     Several helper functions are available for setting up the needed
-     <structname>TupleDesc</>.  The recommended way to do this in most
-     functions returning composite values is to call:
-<programlisting>
-TypeFuncClass get_call_result_type(FunctionCallInfo fcinfo,
-                                   Oid *resultTypeId,
-                                   TupleDesc *resultTupleDesc)
-</programlisting>
-     passing the same <literal>fcinfo</> struct passed to the calling function
-     itself.  (This of course requires that you use the version-1
-     calling conventions.)  <varname>resultTypeId</> can be specified
-     as <literal>NULL</> or as the address of a local variable to receive the
-     function's result type OID.  <varname>resultTupleDesc</> should be the
-     address of a local <structname>TupleDesc</> variable.  Check that the
-     result is <literal>TYPEFUNC_COMPOSITE</>; if so,
-     <varname>resultTupleDesc</> has been filled with the needed
-     <structname>TupleDesc</>.  (If it is not, you can report an error along
-     the lines of <quote>function returning record called in context that
-     cannot accept type record</quote>.)
-    </para>
-
-    <tip>
-     <para>
-      <function>get_call_result_type</> can resolve the actual type of a
-      polymorphic function result; so it is useful in functions that return
-      scalar polymorphic results, not only functions that return composites.
-      The <varname>resultTypeId</> output is primarily useful for functions
-      returning polymorphic scalars.
-     </para>
-    </tip>
-
-    <note>
-     <para>
-      <function>get_call_result_type</> has a sibling
-      <function>get_expr_result_type</>, which can be used to resolve the
-      expected output type for a function call represented by an expression
-      tree.  This can be used when trying to determine the result type from
-      outside the function itself.  There is also
-      <function>get_func_result_type</>, which can be used when only the
-      function's OID is available.  However these functions are not able
-      to deal with functions declared to return <structname>record</>, and
-      <function>get_func_result_type</> cannot resolve polymorphic types,
-      so you should preferentially use <function>get_call_result_type</>.
-     </para>
-    </note>
-
-    <para>
-     Older, now-deprecated functions for obtaining
-     <structname>TupleDesc</>s are:
-<programlisting>
-TupleDesc RelationNameGetTupleDesc(const char *relname)
-</programlisting>
-     to get a <structname>TupleDesc</> for the row type of a named relation,
-     and:
-<programlisting>
-TupleDesc TypeGetTupleDesc(Oid typeoid, List *colaliases)
-</programlisting>
-     to get a <structname>TupleDesc</> based on a type OID. This can
-     be used to get a <structname>TupleDesc</> for a base or
-     composite type.  It will not work for a function that returns
-     <structname>record</>, however, and it cannot resolve polymorphic
-     types.
-    </para>
-
-    <para>
-     Once you have a <structname>TupleDesc</>, call:
-<programlisting>
-TupleDesc BlessTupleDesc(TupleDesc tupdesc)
-</programlisting>
-     if you plan to work with Datums, or:
-<programlisting>
-AttInMetadata *TupleDescGetAttInMetadata(TupleDesc tupdesc)
-</programlisting>
-     if you plan to work with C strings.  If you are writing a function
-     returning set, you can save the results of these functions in the
-     <structname>FuncCallContext</> structure &mdash; use the
-     <structfield>tuple_desc</> or <structfield>attinmeta</> field
-     respectively.
-    </para>
-
-    <para>
-     When working with Datums, use:
-<programlisting>
-HeapTuple heap_form_tuple(TupleDesc tupdesc, Datum *values, bool *isnull)
-</programlisting>
-     to build a <structname>HeapTuple</> given user data in Datum form.
-    </para>
-
-    <para>
-     When working with C strings, use:
-<programlisting>
-HeapTuple BuildTupleFromCStrings(AttInMetadata *attinmeta, char **values)
-</programlisting>
-     to build a <structname>HeapTuple</> given user data
-     in C string form.  <literal>values</literal> is an array of C strings,
-     one for each attribute of the return row. Each C string should be in
-     the form expected by the input function of the attribute data
-     type. In order to return a null value for one of the attributes,
-     the corresponding pointer in the <parameter>values</> array
-     should be set to <symbol>NULL</>.  This function will need to
-     be called again for each row you return.
-    </para>
-
-    <para>
-     Once you have built a tuple to return from your function, it
-     must be converted into a <type>Datum</>. Use:
-<programlisting>
-HeapTupleGetDatum(HeapTuple tuple)
-</programlisting>
-     to convert a <structname>HeapTuple</> into a valid Datum.  This
-     <type>Datum</> can be returned directly if you intend to return
-     just a single row, or it can be used as the current return value
-     in a set-returning function.
-    </para>
-
-    <para>
-     An example appears in the next section.
-    </para>
-
-   </sect2>
-
-   <sect2 id="xfunc-c-return-set">
-    <title>Returning Sets</title>
-&common;
-    <para>
-     There is also a special API that provides support for returning
-     sets (multiple rows) from a C-language function.  A set-returning
-     function must follow the version-1 calling conventions.  Also,
-     source files must include <filename>funcapi.h</filename>, as
-     above.
-    </para>
-
-    <para>
-     A set-returning function (<acronym>SRF</>) is called
-     once for each item it returns.  The <acronym>SRF</> must
-     therefore save enough state to remember what it was doing and
-     return the next item on each call.
-     The structure <structname>FuncCallContext</> is provided to help
-     control this process.  Within a function, <literal>fcinfo-&gt;flinfo-&gt;fn_extra</>
-     is used to hold a pointer to <structname>FuncCallContext</>
-     across calls.
-<programlisting>
-typedef struct
-{
-    /*
-     * Number of times we've been called before
-     *
-     * call_cntr is initialized to 0 for you by SRF_FIRSTCALL_INIT(), and
-     * incremented for you every time SRF_RETURN_NEXT() is called.
-     */
-    uint32 call_cntr;
-
-    /*
-     * OPTIONAL maximum number of calls
-     *
-     * max_calls is here for convenience only and setting it is optional.
-     * If not set, you must provide alternative means to know when the
-     * function is done.
-     */
-    uint32 max_calls;
-
-    /*
-     * OPTIONAL pointer to result slot
-     *
-     * This is obsolete and only present for backward compatibility, viz,
-     * user-defined SRFs that use the deprecated TupleDescGetSlot().
-     */
-    TupleTableSlot *slot;
-
-    /*
-     * OPTIONAL pointer to miscellaneous user-provided context information
-     *
-     * user_fctx is for use as a pointer to your own data to retain
-     * arbitrary context information between calls of your function.
-     */
-    void *user_fctx;
-
-    /*
-     * OPTIONAL pointer to struct containing attribute type input metadata
-     *
-     * attinmeta is for use when returning tuples (i.e., composite data types)
-     * and is not used when returning base data types. It is only needed
-     * if you intend to use BuildTupleFromCStrings() to create the return
-     * tuple.
-     */
-    AttInMetadata *attinmeta;
-
-    /*
-     * memory context used for structures that must live for multiple calls
-     *
-     * multi_call_memory_ctx is set by SRF_FIRSTCALL_INIT() for you, and used
-     * by SRF_RETURN_DONE() for cleanup. It is the most appropriate memory
-     * context for any memory that is to be reused across multiple calls
-     * of the SRF.
-     */
-    MemoryContext multi_call_memory_ctx;
-
-    /*
-     * OPTIONAL pointer to struct containing tuple description
-     *
-     * tuple_desc is for use when returning tuples (i.e., composite data types)
-     * and is only needed if you are going to build the tuples with
-     * heap_form_tuple() rather than with BuildTupleFromCStrings().  Note that
-     * the TupleDesc pointer stored here should usually have been run through
-     * BlessTupleDesc() first.
-     */
-    TupleDesc tuple_desc;
-
-} FuncCallContext;
-</programlisting>
-    </para>
-
-    <para>
-     An <acronym>SRF</> uses several functions and macros that
-     automatically manipulate the <structname>FuncCallContext</>
-     structure (and expect to find it via <literal>fn_extra</>).  Use:
-<programlisting>
-SRF_IS_FIRSTCALL()
-</programlisting>
-     to determine if your function is being called for the first or a
-     subsequent time. On the first call (only) use:
-<programlisting>
-SRF_FIRSTCALL_INIT()
-</programlisting>
-     to initialize the <structname>FuncCallContext</>. On every function call,
-     including the first, use:
-<programlisting>
-SRF_PERCALL_SETUP()
-</programlisting>
-     to properly set up for using the <structname>FuncCallContext</>
-     and clearing any previously returned data left over from the
-     previous pass.
-    </para>
-
-    <para>
-     If your function has data to return, use:
-<programlisting>
-SRF_RETURN_NEXT(funcctx, result)
-</programlisting>
-     to return it to the caller.  (<literal>result</> must be of type
-     <type>Datum</>, either a single value or a tuple prepared as
-     described above.)  Finally, when your function is finished
-     returning data, use:
-<programlisting>
-SRF_RETURN_DONE(funcctx)
-</programlisting>
-     to clean up and end the <acronym>SRF</>.
-    </para>
-
-    <para>
-     The memory context that is current when the <acronym>SRF</> is called is
-     a transient context that will be cleared between calls.  This means
-     that you do not need to call <function>pfree</> on everything
-     you allocated using <function>palloc</>; it will go away anyway.  However, if you want to allocate
-     any data structures to live across calls, you need to put them somewhere
-     else.  The memory context referenced by
-     <structfield>multi_call_memory_ctx</> is a suitable location for any
-     data that needs to survive until the <acronym>SRF</> is finished running.  In most
-     cases, this means that you should switch into
-     <structfield>multi_call_memory_ctx</> while doing the first-call setup.
-    </para>
-
-    <para>
-     A complete pseudo-code example looks like the following:
-<programlisting>
-Datum
-my_set_returning_function(PG_FUNCTION_ARGS)
-{
-    FuncCallContext  *funcctx;
-    Datum             result;
-    <replaceable>further declarations as needed</replaceable>
-
-    if (SRF_IS_FIRSTCALL())
-    {
-        MemoryContext oldcontext;
-
-        funcctx = SRF_FIRSTCALL_INIT();
-        oldcontext = MemoryContextSwitchTo(funcctx-&gt;multi_call_memory_ctx);
-        /* One-time setup code appears here: */
-        <replaceable>user code</replaceable>
-        <replaceable>if returning composite</replaceable>
-            <replaceable>build TupleDesc, and perhaps AttInMetadata</replaceable>
-        <replaceable>endif returning composite</replaceable>
-        <replaceable>user code</replaceable>
-        MemoryContextSwitchTo(oldcontext);
-    }
-
-    /* Each-time setup code appears here: */
-    <replaceable>user code</replaceable>
-    funcctx = SRF_PERCALL_SETUP();
-    <replaceable>user code</replaceable>
-
-    /* this is just one way we might test whether we are done: */
-    if (funcctx-&gt;call_cntr &lt; funcctx-&gt;max_calls)
-    {
-        /* Here we want to return another item: */
-        <replaceable>user code</replaceable>
-        <replaceable>obtain result Datum</replaceable>
-        SRF_RETURN_NEXT(funcctx, result);
-    }
-    else
-    {
-        /* Here we are done returning items and just need to clean up: */
-        <replaceable>user code</replaceable>
-        SRF_RETURN_DONE(funcctx);
-    }
-}
-</programlisting>
-    </para>
-
-    <para>
-     A complete example of a simple <acronym>SRF</> returning a composite type
-     looks like:
-<programlisting><![CDATA[
-PG_FUNCTION_INFO_V1(retcomposite);
-
-Datum
-retcomposite(PG_FUNCTION_ARGS)
-{
-    FuncCallContext     *funcctx;
-    int                  call_cntr;
-    int                  max_calls;
-    TupleDesc            tupdesc;
-    AttInMetadata       *attinmeta;
-
-    /* stuff done only on the first call of the function */
-    if (SRF_IS_FIRSTCALL())
-    {
-        MemoryContext   oldcontext;
-
-        /* create a function context for cross-call persistence */
-        funcctx = SRF_FIRSTCALL_INIT();
-
-        /* switch to memory context appropriate for multiple function calls */
-        oldcontext = MemoryContextSwitchTo(funcctx->multi_call_memory_ctx);
-
-        /* total number of tuples to be returned */
-        funcctx->max_calls = PG_GETARG_UINT32(0);
-
-        /* Build a tuple descriptor for our result type */
-        if (get_call_result_type(fcinfo, NULL, &tupdesc) != TYPEFUNC_COMPOSITE)
-            ereport(ERROR,
-                    (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
-                     errmsg("function returning record called in context "
-                            "that cannot accept type record")));
-
-        /*
-         * generate attribute metadata needed later to produce tuples from raw
-         * C strings
-         */
-        attinmeta = TupleDescGetAttInMetadata(tupdesc);
-        funcctx->attinmeta = attinmeta;
-
-        MemoryContextSwitchTo(oldcontext);
-    }
-
-    /* stuff done on every call of the function */
-    funcctx = SRF_PERCALL_SETUP();
-
-    call_cntr = funcctx->call_cntr;
-    max_calls = funcctx->max_calls;
-    attinmeta = funcctx->attinmeta;
-
-    if (call_cntr < max_calls)    /* do when there is more left to send */
-    {
-        char       **values;
-        HeapTuple    tuple;
-        Datum        result;
-
-        /*
-         * Prepare a values array for building the returned tuple.
-         * This should be an array of C strings which will
-         * be processed later by the type input functions.
-         */
-        values = (char **) palloc(3 * sizeof(char *));
-        values[0] = (char *) palloc(16 * sizeof(char));
-        values[1] = (char *) palloc(16 * sizeof(char));
-        values[2] = (char *) palloc(16 * sizeof(char));
-
-        snprintf(values[0], 16, "%d", 1 * PG_GETARG_INT32(1));
-        snprintf(values[1], 16, "%d", 2 * PG_GETARG_INT32(1));
-        snprintf(values[2], 16, "%d", 3 * PG_GETARG_INT32(1));
-
-        /* build a tuple */
-        tuple = BuildTupleFromCStrings(attinmeta, values);
-
-        /* make the tuple into a datum */
-        result = HeapTupleGetDatum(tuple);
-
-        /* clean up (this is not really necessary) */
-        pfree(values[0]);
-        pfree(values[1]);
-        pfree(values[2]);
-        pfree(values);
-
-        SRF_RETURN_NEXT(funcctx, result);
-    }
-    else    /* do when there is no more left */
-    {
-        SRF_RETURN_DONE(funcctx);
-    }
-}
-]]>
-</programlisting>
-
-     One way to declare this function in SQL is:
-<programlisting>
-CREATE TYPE __retcomposite AS (f1 integer, f2 integer, f3 integer);
-
-CREATE OR REPLACE FUNCTION retcomposite(integer, integer)
-    RETURNS SETOF __retcomposite
-    AS '<replaceable>filename</>', 'retcomposite'
-    LANGUAGE C IMMUTABLE STRICT;
-</programlisting>
-     A different way is to use OUT parameters:
-<programlisting>
-CREATE OR REPLACE FUNCTION retcomposite(IN integer, IN integer,
-    OUT f1 integer, OUT f2 integer, OUT f3 integer)
-    RETURNS SETOF record
-    AS '<replaceable>filename</>', 'retcomposite'
-    LANGUAGE C IMMUTABLE STRICT;
-</programlisting>
-     Notice that in this method the output type of the function is formally
-     an anonymous <structname>record</> type.
-    </para>
-
-    <para>
-     The directory <link linkend="tablefunc">contrib/tablefunc</>
-     module in the source distribution contains more examples of
-     set-returning functions.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Polymorphic Arguments and Return Types</title>
-&common;
-    <para>
-     C-language functions can be declared to accept and
-     return the polymorphic types
-     <type>anyelement</type>, <type>anyarray</type>, <type>anynonarray</type>,
-     and <type>anyenum</type>.
-     See <xref linkend="extend-types-polymorphic"> for a more detailed explanation
-     of polymorphic functions. When function arguments or return types
-     are defined as polymorphic types, the function author cannot know
-     in advance what data type it will be called with, or
-     need to return. There are two routines provided in <filename>fmgr.h</>
-     to allow a version-1 C function to discover the actual data types
-     of its arguments and the type it is expected to return. The routines are
-     called <literal>get_fn_expr_rettype(FmgrInfo *flinfo)</> and
-     <literal>get_fn_expr_argtype(FmgrInfo *flinfo, int argnum)</>.
-     They return the result or argument type OID, or <symbol>InvalidOid</symbol> if the
-     information is not available.
-     The structure <literal>flinfo</> is normally accessed as
-     <literal>fcinfo-&gt;flinfo</>. The parameter <literal>argnum</>
-     is zero based.  <function>get_call_result_type</> can also be used
-     as an alternative to <function>get_fn_expr_rettype</>.
-    </para>
-
-    <para>
-     For example, suppose we want to write a function to accept a single
-     element of any type, and return a one-dimensional array of that type:
-
-<programlisting>
-PG_FUNCTION_INFO_V1(make_array);
-Datum
-make_array(PG_FUNCTION_ARGS)
-{
-    ArrayType  *result;
-    Oid         element_type = get_fn_expr_argtype(fcinfo-&gt;flinfo, 0);
-    Datum       element;
-    bool        isnull;
-    int16       typlen;
-    bool        typbyval;
-    char        typalign;
-    int         ndims;
-    int         dims[MAXDIM];
-    int         lbs[MAXDIM];
-
-    if (!OidIsValid(element_type))
-        elog(ERROR, "could not determine data type of input");
-
-    /* get the provided element, being careful in case it's NULL */
-    isnull = PG_ARGISNULL(0);
-    if (isnull)
-        element = (Datum) 0;
-    else
-        element = PG_GETARG_DATUM(0);
-
-    /* we have one dimension */
-    ndims = 1;
-    /* and one element */
-    dims[0] = 1;
-    /* and lower bound is 1 */
-    lbs[0] = 1;
-
-    /* get required info about the element type */
-    get_typlenbyvalalign(element_type, &amp;typlen, &amp;typbyval, &amp;typalign);
-
-    /* now build the array */
-    result = construct_md_array(&amp;element, &amp;isnull, ndims, dims, lbs,
-                                element_type, typlen, typbyval, typalign);
-
-    PG_RETURN_ARRAYTYPE_P(result);
-}
-</programlisting>
-    </para>
-
-    <para>
-     The following command declares the function
-     <function>make_array</function> in SQL:
-
-<programlisting>
-CREATE FUNCTION make_array(anyelement) RETURNS anyarray
-    AS '<replaceable>DIRECTORY</replaceable>/funcs', 'make_array'
-    LANGUAGE C IMMUTABLE;
-</programlisting>
-    </para>
-
-    <para>
-     There is a variant of polymorphism that is only available to C-language
-     functions: they can be declared to take parameters of type
-     <literal>"any"</>.  (Note that this type name must be double-quoted,
-     since it's also a SQL reserved word.)  This works like
-     <type>anyelement</> except that it does not constrain different
-     <literal>"any"</> arguments to be the same type, nor do they help
-     determine the function's result type.  A C-language function can also
-     declare its final parameter to be <literal>VARIADIC "any"</>.  This will
-     match one or more actual arguments of any type (not necessarily the same
-     type).  These arguments will <emphasis>not</> be gathered into an array
-     as happens with normal variadic functions; they will just be passed to
-     the function separately.  The <function>PG_NARGS()</> macro and the
-     methods described above must be used to determine the number of actual
-     arguments and their types when using this feature.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Shared Memory and LWLocks</title>
-&common;
-    <para>
-     Add-ins can reserve LWLocks and an allocation of shared memory on server
-     startup.  The add-in's shared library must be preloaded by specifying
-     it in
-     <xref linkend="guc-shared-preload-libraries"><indexterm><primary>shared_preload_libraries</></>.
-     Shared memory is reserved by calling:
-<programlisting>
-void RequestAddinShmemSpace(int size)
-</programlisting>
-     from your <function>_PG_init</> function.
-    </para>
-    <para>
-     LWLocks are reserved by calling:
-<programlisting>
-void RequestAddinLWLocks(int n)
-</programlisting>
-     from <function>_PG_init</>.
-    </para>
-    <para>
-     To avoid possible race-conditions, each backend should use the LWLock
-     <function>AddinShmemInitLock</> when connecting to and initializing
-     its allocation of shared memory, as shown here:
-<programlisting>
-static mystruct *ptr = NULL;
-
-if (!ptr)
-{
-        bool    found;
-
-        LWLockAcquire(AddinShmemInitLock, LW_EXCLUSIVE);
-        ptr = ShmemInitStruct("my struct name", size, &amp;found);
-        if (!found)
-        {
-                initialize contents of shmem area;
-                acquire any requested LWLocks using:
-                ptr->mylockid = LWLockAssign();
-        }
-        LWLockRelease(AddinShmemInitLock);
-}
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2 id="extend-Cpp">
-    <title>Using C++ for Extensibility</title>
-
-    <indexterm zone="extend-Cpp">
-     <primary>C++</primary>
-    </indexterm>
-
-    <para>
-<!## PG>
-     Although the <productname>PostgreSQL</productname> backend is written in
-<!## end>
-<!## XC>
-     Although the <productname>Postgres-XC</productname> backend is written in
-<!## end>
-<!## XL>
-     Although the <productname>Postgres-XL</productname> backend is written in
-<!## end>
-     C, it is possible to write extensions in C++ if these guidelines are
-     followed:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-         All functions accessed by the backend must present a C interface
-         to the backend;  these C functions can then call C++ functions.
-         For example, <literal>extern C</> linkage is required for
-         backend-accessed functions.  This is also necessary for any
-         functions that are passed as pointers between the backend and
-         C++ code.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        Free memory using the appropriate deallocation method.  For example,
-        most backend memory is allocated using <function>palloc()</>, so use
-        <function>pfree()</> to free it.  Using C++
-        <function>delete</> in such cases will fail.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        Prevent exceptions from propagating into the C code (use a catch-all
-        block at the top level of all <literal>extern C</> functions).  This
-        is necessary even if the C++ code does not explicitly throw any
-        exceptions, because events like out-of-memory can still throw
-        exceptions.  Any exceptions must be caught and appropriate errors
-        passed back to the C interface.  If possible, compile C++ with
-        <option>-fno-exceptions</> to eliminate exceptions entirely; in such
-        cases, you must check for failures in your C++ code, e.g.  check for
-        NULL returned by <function>new()</>.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-        If calling backend functions from C++ code, be sure that the
-        C++ call stack contains only plain old data structures
-        (<acronym>POD</>).  This is necessary because backend errors
-        generate a distant <function>longjmp()</> that does not properly
-        unroll a C++ call stack with non-POD objects.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     In summary, it is best to place C++ code behind a wall of
-     <literal>extern C</> functions that interface to the backend,
-     and avoid exception, memory, and call stack leakage.
-    </para>
-   </sect2>
-
-  </sect1>
diff --git a/doc-xc/src/sgml/xindex.sgmlin b/doc-xc/src/sgml/xindex.sgmlin
deleted file mode 100644
index a0130e77d9..0000000000
--- a/doc-xc/src/sgml/xindex.sgmlin
+++ /dev/null
@@ -1,1132 +0,0 @@
-<!-- doc/src/sgml/xindex.sgml -->
-
-<sect1 id="xindex">
- <title>Interfacing Extensions To Indexes</title>
-
- <indexterm zone="xindex">
-  <primary>index</primary>
-  <secondary>for user-defined data type</secondary>
- </indexterm>
-
-&common;
-
-  <para>
-   The procedures described thus far let you define new types, new
-   functions, and new operators. However, we cannot yet define an
-   index on a column of a new data type.  To do this, we must define an
-   <firstterm>operator class</> for the new data type.  Later in this
-   section, we will illustrate this concept in an example: a new
-   operator class for the B-tree index method that stores and sorts
-   complex numbers in ascending absolute value order.
-  </para>
-
-  <para>
-   Operator classes can be grouped into <firstterm>operator families</>
-   to show the relationships between semantically compatible classes.
-   When only a single data type is involved, an operator class is sufficient,
-   so we'll focus on that case first and then return to operator families.
-  </para>
-
- <sect2 id="xindex-opclass">
-  <title>Index Methods and Operator Classes</title>
-&common;
-  <para>
-   The <classname>pg_am</classname> table contains one row for every
-   index method (internally known as access method).  Support for
-   regular access to tables is built into
-<!## PG>
-   <productname>PostgreSQL</productname>, but all index methods are
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname>, but all index methods are
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname>, but all index methods are
-<!## end>
-   described in <classname>pg_am</classname>.  It is possible to add a
-   new index method by defining the required interface routines and
-   then creating a row in <classname>pg_am</classname> &mdash; but that is
-   beyond the scope of this chapter (see <xref linkend="indexam">).
-  </para>
-
-  <para>
-   The routines for an index method do not directly know anything
-   about the data types that the index method will operate on.
-   Instead, an <firstterm>operator
-   class</><indexterm><primary>operator class</></indexterm>
-   identifies the set of operations that the index method needs to use
-   to work with a particular data type.  Operator classes are so
-   called because one thing they specify is the set of
-   <literal>WHERE</>-clause operators that can be used with an index
-   (i.e., can be converted into an index-scan qualification).  An
-   operator class can also specify some <firstterm>support
-   procedures</> that are needed by the internal operations of the
-   index method, but do not directly correspond to any
-   <literal>WHERE</>-clause operator that can be used with the index.
-  </para>
-
-  <para>
-   It is possible to define multiple operator classes for the same
-   data type and index method.  By doing this, multiple
-   sets of indexing semantics can be defined for a single data type.
-   For example, a B-tree index requires a sort ordering to be defined
-   for each data type it works on.
-   It might be useful for a complex-number data type
-   to have one B-tree operator class that sorts the data by complex
-   absolute value, another that sorts by real part, and so on.
-   Typically, one of the operator classes will be deemed most commonly
-   useful and will be marked as the default operator class for that
-   data type and index method.
-  </para>
-
-  <para>
-   The same operator class name
-   can be used for several different index methods (for example, both B-tree
-   and hash index methods have operator classes named
-   <literal>int4_ops</literal>), but each such class is an independent
-   entity and must be defined separately.
-  </para>
- </sect2>
-
- <sect2 id="xindex-strategies">
-  <title>Index Method Strategies</title>
-&common;
-  <para>
-   The operators associated with an operator class are identified by
-   <quote>strategy numbers</>, which serve to identify the semantics of
-   each operator within the context of its operator class.
-   For example, B-trees impose a strict ordering on keys, lesser to greater,
-   and so operators like <quote>less than</> and <quote>greater than or equal
-   to</> are interesting with respect to a B-tree.
-   Because
-<!## PG>
-   <productname>PostgreSQL</productname> allows the user to define operators,
-   <productname>PostgreSQL</productname> cannot look at the name of an operator
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> allows the user to define operators,
-   <productname>Postgres-XC</productname> cannot look at the name of an operator
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> allows the user to define operators,
-   <productname>Postgres-XL</productname> cannot look at the name of an operator
-<!## end>
-   (e.g., <literal>&lt;</> or <literal>&gt;=</>) and tell what kind of
-   comparison it is.  Instead, the index method defines a set of
-   <quote>strategies</>, which can be thought of as generalized operators.
-   Each operator class specifies which actual operator corresponds to each
-   strategy for a particular data type and interpretation of the index
-   semantics.
-  </para>
-
-  <para>
-   The B-tree index method defines five strategies, shown in <xref
-   linkend="xindex-btree-strat-table">.
-  </para>
-
-   <table tocentry="1" id="xindex-btree-strat-table">
-    <title>B-tree Strategies</title>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Operation</entry>
-       <entry>Strategy Number</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>less than</entry>
-       <entry>1</entry>
-      </row>
-      <row>
-       <entry>less than or equal</entry>
-       <entry>2</entry>
-      </row>
-      <row>
-       <entry>equal</entry>
-       <entry>3</entry>
-      </row>
-      <row>
-       <entry>greater than or equal</entry>
-       <entry>4</entry>
-      </row>
-      <row>
-       <entry>greater than</entry>
-       <entry>5</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   Hash indexes support only equality comparisons, and so they use only one
-   strategy, shown in <xref linkend="xindex-hash-strat-table">.
-  </para>
-
-   <table tocentry="1" id="xindex-hash-strat-table">
-    <title>Hash Strategies</title>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Operation</entry>
-       <entry>Strategy Number</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>equal</entry>
-       <entry>1</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   GiST indexes are more flexible: they do not have a fixed set of
-   strategies at all.  Instead, the <quote>consistency</> support routine
-   of each particular GiST operator class interprets the strategy numbers
-   however it likes.  As an example, several of the built-in GiST index
-   operator classes index two-dimensional geometric objects, providing
-   the <quote>R-tree</> strategies shown in
-   <xref linkend="xindex-rtree-strat-table">.  Four of these are true
-   two-dimensional tests (overlaps, same, contains, contained by);
-   four of them consider only the X direction; and the other four
-   provide the same tests in the Y direction.
-  </para>
-
-   <table tocentry="1" id="xindex-rtree-strat-table">
-    <title>GiST Two-Dimensional <quote>R-tree</> Strategies</title>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Operation</entry>
-       <entry>Strategy Number</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>strictly left of</entry>
-       <entry>1</entry>
-      </row>
-      <row>
-       <entry>does not extend to right of</entry>
-       <entry>2</entry>
-      </row>
-      <row>
-       <entry>overlaps</entry>
-       <entry>3</entry>
-      </row>
-      <row>
-       <entry>does not extend to left of</entry>
-       <entry>4</entry>
-      </row>
-      <row>
-       <entry>strictly right of</entry>
-       <entry>5</entry>
-      </row>
-      <row>
-       <entry>same</entry>
-       <entry>6</entry>
-      </row>
-      <row>
-       <entry>contains</entry>
-       <entry>7</entry>
-      </row>
-      <row>
-       <entry>contained by</entry>
-       <entry>8</entry>
-      </row>
-      <row>
-       <entry>does not extend above</entry>
-       <entry>9</entry>
-      </row>
-      <row>
-       <entry>strictly below</entry>
-       <entry>10</entry>
-      </row>
-      <row>
-       <entry>strictly above</entry>
-       <entry>11</entry>
-      </row>
-      <row>
-       <entry>does not extend below</entry>
-       <entry>12</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   GIN indexes are similar to GiST indexes in flexibility: they don't have a
-   fixed set of strategies. Instead the support routines of each operator
-   class interpret the strategy numbers according to the operator class's
-   definition. As an example, the strategy numbers used by the built-in
-   operator classes for arrays are
-   shown in <xref linkend="xindex-gin-array-strat-table">.
-  </para>
-
-   <table tocentry="1" id="xindex-gin-array-strat-table">
-    <title>GIN Array Strategies</title>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Operation</entry>
-       <entry>Strategy Number</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>overlap</entry>
-       <entry>1</entry>
-      </row>
-      <row>
-       <entry>contains</entry>
-       <entry>2</entry>
-      </row>
-      <row>
-       <entry>is contained by</entry>
-       <entry>3</entry>
-      </row>
-      <row>
-       <entry>equal</entry>
-       <entry>4</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   Notice that all the operators listed above return Boolean values.  In
-   practice, all operators defined as index method search operators must
-   return type <type>boolean</type>, since they must appear at the top
-   level of a <literal>WHERE</> clause to be used with an index.
-   (Some index access methods also support <firstterm>ordering operators</>,
-   which typically don't return Boolean values; that feature is discussed
-   in <xref linkend="xindex-ordering-ops">.)
-  </para>
- </sect2>
-
- <sect2 id="xindex-support">
-  <title>Index Method Support Routines</title>
-&common;
-  <para>
-   Strategies aren't usually enough information for the system to figure
-   out how to use an index.  In practice, the index methods require
-   additional support routines in order to work. For example, the B-tree
-   index method must be able to compare two keys and determine whether one
-   is greater than, equal to, or less than the other.  Similarly, the
-   hash index method must be able to compute hash codes for key values.
-   These operations do not correspond to operators used in qualifications in
-   SQL commands;  they are administrative routines used by
-   the index methods, internally.
-  </para>
-
-  <para>
-   Just as with strategies, the operator class identifies which specific
-   functions should play each of these roles for a given data type and
-   semantic interpretation.  The index method defines the set
-   of functions it needs, and the operator class identifies the correct
-   functions to use by assigning them to the <quote>support function numbers</>
-   specified by the index method.
-  </para>
-
-  <para>
-   B-trees require a single support function, shown in <xref
-   linkend="xindex-btree-support-table">.
-  </para>
-
-   <table tocentry="1" id="xindex-btree-support-table">
-    <title>B-tree Support Functions</title>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Support Number</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>
-        Compare two keys and return an integer less than zero, zero, or
-        greater than zero, indicating whether the first key is less than,
-        equal to, or greater than the second
-       </entry>
-       <entry>1</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   Hash indexes likewise require one support function, shown in <xref
-   linkend="xindex-hash-support-table">.
-  </para>
-
-   <table tocentry="1" id="xindex-hash-support-table">
-    <title>Hash Support Functions</title>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Support Number</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>Compute the hash value for a key</entry>
-       <entry>1</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   GiST indexes require seven support functions, with an optional eighth, as
-   shown in <xref linkend="xindex-gist-support-table">.
-  </para>
-
-   <table tocentry="1" id="xindex-gist-support-table">
-    <title>GiST Support Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Description</entry>
-       <entry>Support Number</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry><function>consistent</></entry>
-       <entry>determine whether key satisfies the
-        query qualifier</entry>
-       <entry>1</entry>
-      </row>
-      <row>
-       <entry><function>union</></entry>
-       <entry>compute union of a set of keys</entry>
-       <entry>2</entry>
-      </row>
-      <row>
-       <entry><function>compress</></entry>
-       <entry>compute a compressed representation of a key or value
-        to be indexed</entry>
-       <entry>3</entry>
-      </row>
-      <row>
-       <entry><function>decompress</></entry>
-       <entry>compute a decompressed representation of a
-        compressed key</entry>
-       <entry>4</entry>
-      </row>
-      <row>
-       <entry><function>penalty</></entry>
-       <entry>compute penalty for inserting new key into subtree
-       with given subtree's key</entry>
-       <entry>5</entry>
-      </row>
-      <row>
-       <entry><function>picksplit</></entry>
-       <entry>determine which entries of a page are to be moved
-       to the new page and compute the union keys for resulting pages</entry>
-       <entry>6</entry>
-      </row>
-      <row>
-       <entry><function>equal</></entry>
-       <entry>compare two keys and return true if they are equal</entry>
-       <entry>7</entry>
-      </row>
-      <row>
-       <entry><function>distance</></entry>
-       <entry>
-        (optional method) determine distance from key to query value
-       </entry>
-       <entry>8</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   GIN indexes require four support functions, with an optional fifth, as
-   shown in <xref linkend="xindex-gin-support-table">.
-  </para>
-
-   <table tocentry="1" id="xindex-gin-support-table">
-    <title>GIN Support Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Description</entry>
-       <entry>Support Number</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry><function>compare</></entry>
-       <entry>
-        compare two keys and return an integer less than zero, zero,
-        or greater than zero, indicating whether the first key is less than,
-        equal to, or greater than the second
-       </entry>
-       <entry>1</entry>
-      </row>
-      <row>
-       <entry><function>extractValue</></entry>
-       <entry>extract keys from a value to be indexed</entry>
-       <entry>2</entry>
-      </row>
-      <row>
-       <entry><function>extractQuery</></entry>
-       <entry>extract keys from a query condition</entry>
-       <entry>3</entry>
-      </row>
-      <row>
-       <entry><function>consistent</></entry>
-       <entry>determine whether value matches query condition</entry>
-       <entry>4</entry>
-      </row>
-      <row>
-       <entry><function>comparePartial</></entry>
-       <entry>
-        (optional method) compare partial key from
-        query and key from index, and return an integer less than zero, zero,
-        or greater than zero, indicating whether GIN should ignore this index
-        entry, treat the entry as a match, or stop the index scan
-       </entry>
-       <entry>5</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   Unlike search operators, support functions return whichever data
-   type the particular index method expects; for example in the case
-   of the comparison function for B-trees, a signed integer.  The number
-   and types of the arguments to each support function are likewise
-   dependent on the index method.  For B-tree and hash the support functions
-   take the same input data types as do the operators included in the operator
-   class, but this is not the case for most GIN and GiST support functions.
-  </para>
- </sect2>
-
- <sect2 id="xindex-example">
-  <title>An Example</title>
-&common;
-  <para>
-   Now that we have seen the ideas, here is the promised example of
-   creating a new operator class.
-   (You can find a working copy of this example in
-   <filename>src/tutorial/complex.c</filename> and
-   <filename>src/tutorial/complex.sql</filename> in the source
-   distribution.)
-   The operator class encapsulates
-   operators that sort complex numbers in absolute value order, so we
-   choose the name <literal>complex_abs_ops</literal>.  First, we need
-   a set of operators.  The procedure for defining operators was
-   discussed in <xref linkend="xoper">.  For an operator class on
-   B-trees, the operators we require are:
-
-   <itemizedlist spacing="compact">
-    <listitem><simpara>absolute-value less-than (strategy 1)</></>
-    <listitem><simpara>absolute-value less-than-or-equal (strategy 2)</></>
-    <listitem><simpara>absolute-value equal (strategy 3)</></>
-    <listitem><simpara>absolute-value greater-than-or-equal (strategy 4)</></>
-    <listitem><simpara>absolute-value greater-than (strategy 5)</></>
-   </itemizedlist>
-  </para>
-
-  <para>
-   The least error-prone way to define a related set of comparison operators
-   is to write the B-tree comparison support function first, and then write the
-   other functions as one-line wrappers around the support function.  This
-   reduces the odds of getting inconsistent results for corner cases.
-   Following this approach, we first write:
-
-<programlisting><![CDATA[
-#define Mag(c)  ((c)->x*(c)->x + (c)->y*(c)->y)
-
-static int
-complex_abs_cmp_internal(Complex *a, Complex *b)
-{
-    double      amag = Mag(a),
-                bmag = Mag(b);
-
-    if (amag < bmag)
-        return -1;
-    if (amag > bmag)
-        return 1;
-    return 0;
-}
-]]>
-</programlisting>
-
-   Now the less-than function looks like:
-
-<programlisting><![CDATA[
-PG_FUNCTION_INFO_V1(complex_abs_lt);
-
-Datum
-complex_abs_lt(PG_FUNCTION_ARGS)
-{
-    Complex    *a = (Complex *) PG_GETARG_POINTER(0);
-    Complex    *b = (Complex *) PG_GETARG_POINTER(1);
-
-    PG_RETURN_BOOL(complex_abs_cmp_internal(a, b) < 0);
-}
-]]>
-</programlisting>
-
-   The other four functions differ only in how they compare the internal
-   function's result to zero.
-  </para>
-
-  <para>
-   Next we declare the functions and the operators based on the functions
-   to SQL:
-
-<programlisting>
-CREATE FUNCTION complex_abs_lt(complex, complex) RETURNS bool
-    AS '<replaceable>filename</replaceable>', 'complex_abs_lt'
-    LANGUAGE C IMMUTABLE STRICT;
-
-CREATE OPERATOR &lt; (
-   leftarg = complex, rightarg = complex, procedure = complex_abs_lt,
-   commutator = &gt; , negator = &gt;= ,
-   restrict = scalarltsel, join = scalarltjoinsel
-);
-</programlisting>
-   It is important to specify the correct commutator and negator operators,
-   as well as suitable restriction and join selectivity
-   functions, otherwise the optimizer will be unable to make effective
-   use of the index.  Note that the less-than, equal, and
-   greater-than cases should use different selectivity functions.
-  </para>
-
-  <para>
-   Other things worth noting are happening here:
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     There can only be one operator named, say, <literal>=</literal>
-     and taking type <type>complex</type> for both operands.  In this
-     case we don't have any other operator <literal>=</literal> for
-     <type>complex</type>, but if we were building a practical data
-     type we'd probably want <literal>=</literal> to be the ordinary
-     equality operation for complex numbers (and not the equality of
-     the absolute values).  In that case, we'd need to use some other
-     operator name for <function>complex_abs_eq</>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-<!## PG>
-     Although <productname>PostgreSQL</productname> can cope with
-<!## end>
-<!## XC>
-     Although <productname>Postgres-XC</productname> can cope with
-<!## end>
-<!## XL>
-     Although <productname>Postgres-XL</productname> can cope with
-<!## end>
-     functions having the same SQL name as long as they have different
-     argument data types, C can only cope with one global function
-     having a given name.  So we shouldn't name the C function
-     something simple like <filename>abs_eq</filename>.  Usually it's
-     a good practice to include the data type name in the C function
-     name, so as not to conflict with functions for other data types.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     We could have made the SQL name
-     of the function <filename>abs_eq</filename>, relying on
-<!## PG>
-     <productname>PostgreSQL</productname> to distinguish it by
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> to distinguish it by
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> to distinguish it by
-<!## end>
-     argument data types from any other SQL function of the same name.
-     To keep the example simple, we make the function have the same
-     names at the C level and SQL level.
-    </para>
-   </listitem>
-  </itemizedlist>
-  </para>
-
-  <para>
-   The next step is the registration of the support routine required
-   by B-trees.  The example C code that implements this is in the same
-   file that contains the operator functions.  This is how we declare
-   the function:
-
-<programlisting>
-CREATE FUNCTION complex_abs_cmp(complex, complex)
-    RETURNS integer
-    AS '<replaceable>filename</replaceable>'
-    LANGUAGE C IMMUTABLE STRICT;
-</programlisting>
-  </para>
-
-  <para>
-   Now that we have the required operators and support routine,
-   we can finally create the operator class:
-
-<programlisting><![CDATA[
-CREATE OPERATOR CLASS complex_abs_ops
-    DEFAULT FOR TYPE complex USING btree AS
-        OPERATOR        1       < ,
-        OPERATOR        2       <= ,
-        OPERATOR        3       = ,
-        OPERATOR        4       >= ,
-        OPERATOR        5       > ,
-        FUNCTION        1       complex_abs_cmp(complex, complex);
-]]>
-</programlisting>
-  </para>
-
-  <para>
-   And we're done!  It should now be possible to create
-   and use B-tree indexes on <type>complex</type> columns.
-  </para>
-
-  <para>
-   We could have written the operator entries more verbosely, as in:
-<programlisting>
-        OPERATOR        1       &lt; (complex, complex) ,
-</programlisting>
-   but there is no need to do so when the operators take the same data type
-   we are defining the operator class for.
-  </para>
-
-  <para>
-   The above example assumes that you want to make this new operator class the
-   default B-tree operator class for the <type>complex</type> data type.
-   If you don't, just leave out the word <literal>DEFAULT</>.
-  </para>
- </sect2>
-
- <sect2 id="xindex-opfamily">
-  <title>Operator Classes and Operator Families</title>
-&common;
-  <para>
-   So far we have implicitly assumed that an operator class deals with
-   only one data type.  While there certainly can be only one data type in
-   a particular index column, it is often useful to index operations that
-   compare an indexed column to a value of a different data type.  Also,
-   if there is use for a cross-data-type operator in connection with an
-   operator class, it is often the case that the other data type has a
-   related operator class of its own.  It is helpful to make the connections
-   between related classes explicit, because this can aid the planner in
-   optimizing SQL queries (particularly for B-tree operator classes, since
-   the planner contains a great deal of knowledge about how to work with them).
-  </para>
-
-  <para>
-<!## PG>
-   To handle these needs, <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-   To handle these needs, <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-   To handle these needs, <productname>Postgres-XL</productname>
-<!## end>
-   uses the concept of an <firstterm>operator
-   family</><indexterm><primary>operator family</></indexterm>.
-   An operator family contains one or more operator classes, and can also
-   contain indexable operators and corresponding support functions that
-   belong to the family as a whole but not to any single class within the
-   family.  We say that such operators and functions are <quote>loose</>
-   within the family, as opposed to being bound into a specific class.
-   Typically each operator class contains single-data-type operators
-   while cross-data-type operators are loose in the family.
-  </para>
-
-  <para>
-   All the operators and functions in an operator family must have compatible
-   semantics, where the compatibility requirements are set by the index
-   method.  You might therefore wonder why bother to single out particular
-   subsets of the family as operator classes; and indeed for many purposes
-   the class divisions are irrelevant and the family is the only interesting
-   grouping.  The reason for defining operator classes is that they specify
-   how much of the family is needed to support any particular index.
-   If there is an index using an operator class, then that operator class
-   cannot be dropped without dropping the index &mdash; but other parts of
-   the operator family, namely other operator classes and loose operators,
-   could be dropped.  Thus, an operator class should be specified to contain
-   the minimum set of operators and functions that are reasonably needed
-   to work with an index on a specific data type, and then related but
-   non-essential operators can be added as loose members of the operator
-   family.
-  </para>
-
-  <para>
-<!## PG>
-   As an example, <productname>PostgreSQL</productname> has a built-in
-<!## end>
-<!## XC>
-   As an example, <productname>Postgres-XC</productname> has a built-in
-<!## end>
-<!## XL>
-   As an example, <productname>Postgres-XL</productname> has a built-in
-<!## end>
-   B-tree operator family <literal>integer_ops</>, which includes operator
-   classes <literal>int8_ops</>, <literal>int4_ops</>, and
-   <literal>int2_ops</> for indexes on <type>bigint</> (<type>int8</>),
-   <type>integer</> (<type>int4</>), and <type>smallint</> (<type>int2</>)
-   columns respectively.  The family also contains cross-data-type comparison
-   operators allowing any two of these types to be compared, so that an index
-   on one of these types can be searched using a comparison value of another
-   type.  The family could be duplicated by these definitions:
-
-<programlisting><![CDATA[
-CREATE OPERATOR FAMILY integer_ops USING btree;
-
-CREATE OPERATOR CLASS int8_ops
-DEFAULT FOR TYPE int8 USING btree FAMILY integer_ops AS
-  -- standard int8 comparisons
-  OPERATOR 1 < ,
-  OPERATOR 2 <= ,
-  OPERATOR 3 = ,
-  OPERATOR 4 >= ,
-  OPERATOR 5 > ,
-  FUNCTION 1 btint8cmp(int8, int8) ;
-
-CREATE OPERATOR CLASS int4_ops
-DEFAULT FOR TYPE int4 USING btree FAMILY integer_ops AS
-  -- standard int4 comparisons
-  OPERATOR 1 < ,
-  OPERATOR 2 <= ,
-  OPERATOR 3 = ,
-  OPERATOR 4 >= ,
-  OPERATOR 5 > ,
-  FUNCTION 1 btint4cmp(int4, int4) ;
-
-CREATE OPERATOR CLASS int2_ops
-DEFAULT FOR TYPE int2 USING btree FAMILY integer_ops AS
-  -- standard int2 comparisons
-  OPERATOR 1 < ,
-  OPERATOR 2 <= ,
-  OPERATOR 3 = ,
-  OPERATOR 4 >= ,
-  OPERATOR 5 > ,
-  FUNCTION 1 btint2cmp(int2, int2) ;
-
-ALTER OPERATOR FAMILY integer_ops USING btree ADD
-  -- cross-type comparisons int8 vs int2
-  OPERATOR 1 < (int8, int2) ,
-  OPERATOR 2 <= (int8, int2) ,
-  OPERATOR 3 = (int8, int2) ,
-  OPERATOR 4 >= (int8, int2) ,
-  OPERATOR 5 > (int8, int2) ,
-  FUNCTION 1 btint82cmp(int8, int2) ,
-
-  -- cross-type comparisons int8 vs int4
-  OPERATOR 1 < (int8, int4) ,
-  OPERATOR 2 <= (int8, int4) ,
-  OPERATOR 3 = (int8, int4) ,
-  OPERATOR 4 >= (int8, int4) ,
-  OPERATOR 5 > (int8, int4) ,
-  FUNCTION 1 btint84cmp(int8, int4) ,
-
-  -- cross-type comparisons int4 vs int2
-  OPERATOR 1 < (int4, int2) ,
-  OPERATOR 2 <= (int4, int2) ,
-  OPERATOR 3 = (int4, int2) ,
-  OPERATOR 4 >= (int4, int2) ,
-  OPERATOR 5 > (int4, int2) ,
-  FUNCTION 1 btint42cmp(int4, int2) ,
-
-  -- cross-type comparisons int4 vs int8
-  OPERATOR 1 < (int4, int8) ,
-  OPERATOR 2 <= (int4, int8) ,
-  OPERATOR 3 = (int4, int8) ,
-  OPERATOR 4 >= (int4, int8) ,
-  OPERATOR 5 > (int4, int8) ,
-  FUNCTION 1 btint48cmp(int4, int8) ,
-
-  -- cross-type comparisons int2 vs int8
-  OPERATOR 1 < (int2, int8) ,
-  OPERATOR 2 <= (int2, int8) ,
-  OPERATOR 3 = (int2, int8) ,
-  OPERATOR 4 >= (int2, int8) ,
-  OPERATOR 5 > (int2, int8) ,
-  FUNCTION 1 btint28cmp(int2, int8) ,
-
-  -- cross-type comparisons int2 vs int4
-  OPERATOR 1 < (int2, int4) ,
-  OPERATOR 2 <= (int2, int4) ,
-  OPERATOR 3 = (int2, int4) ,
-  OPERATOR 4 >= (int2, int4) ,
-  OPERATOR 5 > (int2, int4) ,
-  FUNCTION 1 btint24cmp(int2, int4) ;
-]]>
-</programlisting>
-
-   Notice that this definition <quote>overloads</> the operator strategy and
-   support function numbers: each number occurs multiple times within the
-   family.  This is allowed so long as each instance of a
-   particular number has distinct input data types.  The instances that have
-   both input types equal to an operator class's input type are the
-   primary operators and support functions for that operator class,
-   and in most cases should be declared as part of the operator class rather
-   than as loose members of the family.
-  </para>
-
-  <para>
-   In a B-tree operator family, all the operators in the family must sort
-   compatibly, meaning that the transitive laws hold across all the data types
-   supported by the family: <quote>if A = B and B = C, then A =
-   C</>, and <quote>if A &lt; B and B &lt; C, then A &lt; C</>.  For each
-   operator in the family there must be a support function having the same
-   two input data types as the operator.  It is recommended that a family be
-   complete, i.e., for each combination of data types, all operators are
-   included.  Each operator class should include just the non-cross-type
-   operators and support function for its data type.
-  </para>
-
-  <para>
-   To build a multiple-data-type hash operator family, compatible hash
-   support functions must be created for each data type supported by the
-   family.  Here compatibility means that the functions are guaranteed to
-   return the same hash code for any two values that are considered equal
-   by the family's equality operators, even when the values are of different
-   types.  This is usually difficult to accomplish when the types have
-   different physical representations, but it can be done in some cases.
-   Notice that there is only one support function per data type, not one
-   per equality operator.  It is recommended that a family be complete, i.e.,
-   provide an equality operator for each combination of data types.
-   Each operator class should include just the non-cross-type equality
-   operator and the support function for its data type.
-  </para>
-
-  <para>
-   GIN and GiST indexes do not have any explicit notion of cross-data-type
-   operations.  The set of operators supported is just whatever the primary
-   support functions for a given operator class can handle.
-  </para>
-
-  <note>
-   <para>
-    Prior to <productname>PostgreSQL</productname> 8.3, there was no concept
-    of operator families, and so any cross-data-type operators intended to be
-    used with an index had to be bound directly into the index's operator
-    class.  While this approach still works, it is deprecated because it
-    makes an index's dependencies too broad, and because the planner can
-    handle cross-data-type comparisons more effectively when both data types
-    have operators in the same operator family.
-   </para>
-  </note>
- </sect2>
-
- <sect2 id="xindex-opclass-dependencies">
-  <title>System Dependencies on Operator Classes</title>
-
-   <indexterm>
-    <primary>ordering operator</primary>
-   </indexterm>
-&common;
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> uses operator classes to infer the
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> uses operator classes to infer the
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> uses operator classes to infer the
-<!## end>
-   properties of operators in more ways than just whether they can be used
-   with indexes.  Therefore, you might want to create operator classes
-   even if you have no intention of indexing any columns of your data type.
-  </para>
-
-  <para>
-   In particular, there are SQL features such as <literal>ORDER BY</> and
-   <literal>DISTINCT</> that require comparison and sorting of values.
-   To implement these features on a user-defined data type,
-<!## PG>
-   <productname>PostgreSQL</productname> looks for the default B-tree operator
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> looks for the default B-tree operator
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> looks for the default B-tree operator
-<!## end>
-   class for the data type.  The <quote>equals</> member of this operator
-   class defines the system's notion of equality of values for
-   <literal>GROUP BY</> and <literal>DISTINCT</>, and the sort ordering
-   imposed by the operator class defines the default <literal>ORDER BY</>
-   ordering.
-  </para>
-
-  <para>
-   Comparison of arrays of user-defined types also relies on the semantics
-   defined by the default B-tree operator class.
-  </para>
-
-  <para>
-   If there is no default B-tree operator class for a data type, the system
-   will look for a default hash operator class.  But since that kind of
-   operator class only provides equality, in practice it is only enough
-   to support array equality.
-  </para>
-
-  <para>
-   When there is no default operator class for a data type, you will get
-   errors like <quote>could not identify an ordering operator</> if you
-   try to use these SQL features with the data type.
-  </para>
-
-   <note>
-    <para>
-     In <productname>PostgreSQL</productname> versions before 7.4,
-     sorting and grouping operations would implicitly use operators named
-     <literal>=</>, <literal>&lt;</>, and <literal>&gt;</>.  The new
-     behavior of relying on default operator classes avoids having to make
-     any assumption about the behavior of operators with particular names.
-    </para>
-   </note>
-
-  <para>
-   Another important point is that an operator that
-   appears in a hash operator family is a candidate for hash joins,
-   hash aggregation, and related optimizations.  The hash operator family
-   is essential here since it identifies the hash function(s) to use.
-  </para>
- </sect2>
-
- <sect2 id="xindex-ordering-ops">
-  <title>Ordering Operators</title>
-
-  <para>
-   Some index access methods (currently, only GiST) support the concept of
-   <firstterm>ordering operators</>.  What we have been discussing so far
-   are <firstterm>search operators</>.  A search operator is one for which
-   the index can be searched to find all rows satisfying
-   <literal>WHERE</>
-   <replaceable>indexed_column</>
-   <replaceable>operator</>
-   <replaceable>constant</>.
-   Note that nothing is promised about the order in which the matching rows
-   will be returned.  In contrast, an ordering operator does not restrict the
-   set of rows that can be returned, but instead determines their order.
-   An ordering operator is one for which the index can be scanned to return
-   rows in the order represented by
-   <literal>ORDER BY</>
-   <replaceable>indexed_column</>
-   <replaceable>operator</>
-   <replaceable>constant</>.
-   The reason for defining ordering operators that way is that it supports
-   nearest-neighbor searches, if the operator is one that measures distance.
-   For example, a query like
-<programlisting><![CDATA[
-SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
-]]>
-</programlisting>
-   finds the ten places closest to a given target point.  A GiST index
-   on the location column can do this efficiently because
-   <literal>&lt;-&gt;</> is an ordering operator.
-  </para>
-
-  <para>
-   While search operators have to return Boolean results, ordering operators
-   usually return some other type, such as float or numeric for distances.
-   This type is normally not the same as the data type being indexed.
-   To avoid hard-wiring assumptions about the behavior of different data
-   types, the definition of an ordering operator is required to name
-   a B-tree operator family that specifies the sort ordering of the result
-   data type.  As was stated in the previous section, B-tree operator families
-   define <productname>PostgreSQL</productname>'s notion of ordering, so
-   this is a natural representation.  Since the point <literal>&lt;-&gt;</>
-   operator returns <type>float8</>, it could be specified in an operator
-   class creation command like this:
-<programlisting><![CDATA[
-OPERATOR 15    <-> (point, point) FOR ORDER BY float_ops
-]]>
-</programlisting>
-   where <literal>float_ops</> is the built-in operator family that includes
-   operations on <type>float8</>.  This declaration states that the index
-   is able to return rows in order of increasing values of the
-   <literal>&lt;-&gt;</> operator.
-  </para>
- </sect2>
-
- <sect2 id="xindex-opclass-features">
-  <title>Special Features of Operator Classes</title>
-&common;
-  <para>
-   There are two special features of operator classes that we have
-   not discussed yet, mainly because they are not useful
-   with the most commonly used index methods.
-  </para>
-
-  <para>
-   Normally, declaring an operator as a member of an operator class
-   (or family) means that the index method can retrieve exactly the set of rows
-   that satisfy a <literal>WHERE</> condition using the operator.  For example:
-<programlisting>
-SELECT * FROM table WHERE integer_column &lt; 4;
-</programlisting>
-   can be satisfied exactly by a B-tree index on the integer column.
-   But there are cases where an index is useful as an inexact guide to
-   the matching rows.  For example, if a GiST index stores only bounding boxes
-   for geometric objects, then it cannot exactly satisfy a <literal>WHERE</>
-   condition that tests overlap between nonrectangular objects such as
-   polygons.  Yet we could use the index to find objects whose bounding
-   box overlaps the bounding box of the target object, and then do the
-   exact overlap test only on the objects found by the index.  If this
-   scenario applies, the index is said to be <quote>lossy</> for the
-   operator.  Lossy index searches are implemented by having the index
-   method return a <firstterm>recheck</> flag when a row might or might
-   not really satisfy the query condition.  The core system will then
-   test the original query condition on the retrieved row to see whether
-   it should be returned as a valid match.  This approach works if
-   the index is guaranteed to return all the required rows, plus perhaps
-   some additional rows, which can be eliminated by performing the original
-   operator invocation.  The index methods that support lossy searches
-   (currently, GiST and GIN) allow the support functions of individual
-   operator classes to set the recheck flag, and so this is essentially an
-   operator-class feature.
-  </para>
-
-  <para>
-   Consider again the situation where we are storing in the index only
-   the bounding box of a complex object such as a polygon.  In this
-   case there's not much value in storing the whole polygon in the index
-   entry &mdash; we might as well store just a simpler object of type
-   <type>box</>.  This situation is expressed by the <literal>STORAGE</>
-   option in <command>CREATE OPERATOR CLASS</>: we'd write something like:
-
-<programlisting>
-CREATE OPERATOR CLASS polygon_ops
-    DEFAULT FOR TYPE polygon USING gist AS
-        ...
-        STORAGE box;
-</programlisting>
-
-   At present, only the GiST and GIN index methods support a
-   <literal>STORAGE</> type that's different from the column data type.
-   The GiST <function>compress</> and <function>decompress</> support
-   routines must deal with data-type conversion when <literal>STORAGE</>
-   is used.  In GIN, the <literal>STORAGE</> type identifies the type of
-   the <quote>key</> values, which normally is different from the type
-   of the indexed column &mdash; for example, an operator class for
-   integer-array columns might have keys that are just integers.  The
-   GIN <function>extractValue</> and <function>extractQuery</> support
-   routines are responsible for extracting keys from indexed values.
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/xlonly.sgmlin b/doc-xc/src/sgml/xlonly.sgmlin
deleted file mode 100644
index 2e6110c5b1..0000000000
--- a/doc-xc/src/sgml/xlonly.sgmlin
+++ /dev/null
@@ -1,7 +0,0 @@
-<!## XL>
-<note>
-<para>
-The following description applies only to <productname>Postgres-XL</>
-</para>
-</note>
-<!## end>
diff --git a/doc-xc/src/sgml/xml2.sgmlin b/doc-xc/src/sgml/xml2.sgmlin
deleted file mode 100644
index 8bb8e30461..0000000000
--- a/doc-xc/src/sgml/xml2.sgmlin
+++ /dev/null
@@ -1,491 +0,0 @@
-<!-- doc/src/sgml/xml2.sgml -->
-
-<sect1 id="xml2" xreflabel="xml2">
- <title>xml2</title>
-
- <indexterm zone="xml2">
-  <primary>xml2</primary>
- </indexterm>
-
-&common;
-
- <para>
-  The <filename>xml2</> module provides XPath querying and
-  XSLT functionality.
- </para>
-
- <sect2>
-  <title>Deprecation Notice</title>
-
-&common;
-  <para>
-   From <productname>PostgreSQL</> 8.3 on, there is XML-related
-   functionality based on the SQL/XML standard in the core server.
-   That functionality covers XML syntax checking and XPath queries,
-   which is what this module does, and more, but the API is
-   not at all compatible.  It is planned that this module will be
-   removed in PostgreSQL 8.4 in favor of the newer standard API, so
-   you are encouraged to try converting your applications.  If you
-   find that some of the functionality of this module is not
-   available in an adequate form with the newer API, please explain
-   your issue to [email protected] so that the deficiency
-   can be addressed.
-  </para>
- </sect2>
-
- <sect2>
-  <title>Description of Functions</title>
-
-&common;
-  <para>
-   <xref linkend="xml2-functions-table"> shows the functions provided by this module.
-   These functions provide straightforward XML parsing and XPath queries.
-   All arguments are of type <type>text</>, so for brevity that is not shown.
-  </para>
-
-  <table id="xml2-functions-table">
-   <title>Functions</title>
-   <tgroup cols="3">
-   <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Returns</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry>
-       <function>
-        xml_is_well_formed(document)
-       </function>
-      </entry>
-      <entry>
-       <type>bool</type>
-      </entry>
-      <entry>
-       <para>
-        This parses the document text in its parameter and returns true if the
-        document is well-formed XML.  (Note: before PostgreSQL 8.2, this
-        function was called <function>xml_valid()</>.  That is the wrong name
-        since validity and well-formedness have different meanings in XML.
-        The old name is still available, but is deprecated.)
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry>
-        <function>
-         xpath_string(document, query)
-        </function>
-      </entry>
-      <entry>
-       <type>text</type>
-      </entry>
-      <entry morerows="2">
-       <para>
-        These functions evaluate the XPath query on the supplied document, and
-        cast the result to the specified type.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry>
-       <function>
-        xpath_number(document, query)
-       </function>
-      </entry>
-      <entry>
-       <type>float4</type>
-      </entry>
-     </row>
-     <row>
-      <entry>
-       <function>
-        xpath_bool(document, query)
-       </function>
-      </entry>
-      <entry>
-       <type>bool</type>
-      </entry>
-     </row>
-     <row>
-      <entry>
-        <function>
-         xpath_nodeset(document, query, toptag, itemtag)
-        </function>
-      </entry>
-      <entry>
-       <type>text</type>
-      </entry>
-      <entry>
-       <para>
-       This evaluates query on document and wraps the result in XML tags. If
-       the result is multivalued, the output will look like:
-<synopsis>
-&lt;toptag&gt;
-&lt;itemtag&gt;Value 1 which could be an XML fragment&lt;/itemtag&gt;
-&lt;itemtag&gt;Value 2....&lt;/itemtag&gt;
-&lt;/toptag&gt;
-</synopsis>
-        If either <literal>toptag</> or <literal>itemtag</> is an empty string, the relevant tag is omitted.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry>
-        <function>
-         xpath_nodeset(document, query)
-        </function>
-      </entry>
-      <entry>
-       <type>text</type>
-      </entry>
-      <entry>
-       <para>
-        Like <function>xpath_nodeset(document, query, toptag, itemtag)</> but result omits both tags.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry>
-        <function>
-         xpath_nodeset(document, query, itemtag)
-        </function>
-      </entry>
-      <entry>
-       <type>text</type>
-      </entry>
-      <entry>
-       <para>
-        Like <function>xpath_nodeset(document, query, toptag, itemtag)</> but result omits toptag.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry>
-        <function>
-         xpath_list(document, query, separator)
-        </function>
-      </entry>
-      <entry>
-       <type>text</type>
-      </entry>
-      <entry>
-       <para>
-        This function returns multiple values separated by the specified
-        separator, for example <literal>Value 1,Value 2,Value 3</> if
-        separator is <literal>,</>.
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry>
-        <function>
-         xpath_list(document, query)
-        </function>
-      </entry>
-      <entry>
-       <type>text</type>
-      </entry>
-      <entry>
-       This is a wrapper for the above function that uses <literal>,</>
-       as the separator.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect2>
-
- <sect2>
-  <title><literal>xpath_table</literal></title>
-
-<synopsis>
-xpath_table(text key, text document, text relation, text xpaths, text criteria) returns setof record
-</synopsis>
-
-&common;
-  <para>
-   <function>xpath_table</> is a table function that evaluates a set of XPath
-   queries on each of a set of documents and returns the results as a
-   table. The primary key field from the original document table is returned
-   as the first column of the result so that the result set
-   can readily be used in joins.  The parameters are described in
-   <xref linkend="xml2-xpath-table-parameters">.
-  </para>
-
-  <table id="xml2-xpath-table-parameters">
-   <title><function>xpath_table</function> Parameters</title>
-   <tgroup cols="2">
-     <thead>
-     <row>
-      <entry>Parameter</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-    <tbody>
-     <row>
-      <entry><parameter>key</parameter></entry>
-      <entry>
-       <para>
-        the name of the <quote>key</> field &mdash; this is just a field to be used as
-        the first column of the output table, i.e., it identifies the record from
-        which each output row came (see note below about multiple values)
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><parameter>document</parameter></entry>
-      <entry>
-       <para>
-        the name of the field containing the XML document
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><parameter>relation</parameter></entry>
-      <entry>
-       <para>
-        the name of the table or view containing the documents
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><parameter>xpaths</parameter></entry>
-      <entry>
-       <para>
-        one or more XPath expressions, separated by <literal>|</literal>
-       </para>
-      </entry>
-     </row>
-     <row>
-      <entry><parameter>criteria</parameter></entry>
-      <entry>
-       <para>
-        the contents of the WHERE clause. This cannot be omitted, so use
-        <literal>true</literal> or <literal>1=1</literal> if you want to
-        process all the rows in the relation
-       </para>
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   These parameters (except the XPath strings) are just substituted
-   into a plain SQL SELECT statement, so you have some flexibility &mdash; the
-   statement is
-  </para>
-
-  <para>
-   <literal>
-    SELECT &lt;key&gt;, &lt;document&gt; FROM &lt;relation&gt; WHERE &lt;criteria&gt;
-   </literal>
-  </para>
-
-  <para>
-   so those parameters can be <emphasis>anything</> valid in those particular
-   locations. The result from this SELECT needs to return exactly two
-   columns (which it will unless you try to list multiple fields for key
-   or document). Beware that this simplistic approach requires that you
-   validate any user-supplied values to avoid SQL injection attacks.
-  </para>
-
-  <para>
-   The function has to be used in a <literal>FROM</> expression, with an
-   <literal>AS</> clause to specify the output columns; for example
-<programlisting>
-SELECT * FROM
-xpath_table('article_id',
-            'article_xml',
-            'articles',
-            '/article/author|/article/pages|/article/title',
-            'date_entered > ''2003-01-01'' ')
-AS t(article_id integer, author text, page_count integer, title text);
-</programlisting>
-   The <literal>AS</> clause defines the names and types of the columns in the
-   output table.  The first is the <quote>key</> field and the rest correspond
-   to the XPath queries.
-   If there are more XPath queries than result columns,
-   the extra queries will be ignored. If there are more result columns
-   than XPath queries, the extra columns will be NULL.
-  </para>
-
-  <para>
-   Notice that this example defines the <structname>page_count</> result
-   column as an integer.  The function deals internally with string
-   representations, so when you say you want an integer in the output, it will
-<!## PG>
-   take the string representation of the XPath result and use PostgreSQL input
-<!## end>
-<!## XC>
-   take the string representation of the XPath result and use Postgres-XC input
-<!## end>
-<!## XL>
-   take the string representation of the XPath result and use Postgres-XL input
-<!## end>
-   functions to transform it into an integer (or whatever type the <type>AS</>
-   clause requests). An error will result if it can't do this &mdash; for
-   example if the result is empty &mdash; so you may wish to just stick to
-   <type>text</> as the column type if you think your data has any problems.
-  </para>
-
-  <para>
-   The calling <command>SELECT</> statement doesn't necessarily have be
-   be just <literal>SELECT *</> &mdash; it can reference the output
-   columns by name or join them to other tables. The function produces a
-   virtual table with which you can perform any operation you wish (e.g.
-   aggregation, joining, sorting etc). So we could also have:
-<programlisting>
-SELECT t.title, p.fullname, p.email
-FROM xpath_table('article_id', 'article_xml', 'articles',
-                 '/article/title|/article/author/@id',
-                 'xpath_string(article_xml,''/article/@date'') > ''2003-03-20'' ')
-       AS t(article_id integer, title text, author_id integer),
-     tblPeopleInfo AS p
-WHERE t.author_id = p.person_id;
-</programlisting>
-   as a more complicated example. Of course, you could wrap all
-   of this in a view for convenience.
-  </para>
-
-  <sect3>
-   <title>Multivalued Results</title>
-
-&common;
-   <para>
-    The <function>xpath_table</> function assumes that the results of each XPath query
-    might be multivalued, so the number of rows returned by the function
-    may not be the same as the number of input documents. The first row
-    returned contains the first result from each query, the second row the
-    second result from each query. If one of the queries has fewer values
-    than the others, null values will be returned instead.
-   </para>
-
-   <para>
-    In some cases, a user will know that a given XPath query will return
-    only a single result (perhaps a unique document identifier) &mdash; if used
-    alongside an XPath query returning multiple results, the single-valued
-    result will appear only on the first row of the result. The solution
-    to this is to use the key field as part of a join against a simpler
-    XPath query. As an example:
-
-<programlisting>
-CREATE TABLE test (
-    id int PRIMARY KEY,
-    xml text
-);
-
-INSERT INTO test VALUES (1, '&lt;doc num="C1"&gt;
-&lt;line num="L1"&gt;&lt;a&gt;1&lt;/a&gt;&lt;b&gt;2&lt;/b&gt;&lt;c&gt;3&lt;/c&gt;&lt;/line&gt;
-&lt;line num="L2"&gt;&lt;a&gt;11&lt;/a&gt;&lt;b&gt;22&lt;/b&gt;&lt;c&gt;33&lt;/c&gt;&lt;/line&gt;
-&lt;/doc&gt;');
-
-INSERT INTO test VALUES (2, '&lt;doc num="C2"&gt;
-&lt;line num="L1"&gt;&lt;a&gt;111&lt;/a&gt;&lt;b&gt;222&lt;/b&gt;&lt;c&gt;333&lt;/c&gt;&lt;/line&gt;
-&lt;line num="L2"&gt;&lt;a&gt;111&lt;/a&gt;&lt;b&gt;222&lt;/b&gt;&lt;c&gt;333&lt;/c&gt;&lt;/line&gt;
-&lt;/doc&gt;');
-
-SELECT * FROM
-  xpath_table('id','xml','test',
-              '/doc/@num|/doc/line/@num|/doc/line/a|/doc/line/b|/doc/line/c',
-              'true')
-  AS t(id int, doc_num varchar(10), line_num varchar(10), val1 int, val2 int, val3 int)
-WHERE id = 1 ORDER BY doc_num, line_num
-
- id | doc_num | line_num | val1 | val2 | val3
-----+---------+----------+------+------+------
-  1 | C1      | L1       |    1 |    2 |    3
-  1 |         | L2       |   11 |   22 |   33
-</programlisting>
-   </para>
-
-   <para>
-    To get <literal>doc_num</> on every line, the solution is to use two invocations
-    of <function>xpath_table</> and join the results:
-
-<programlisting>
-SELECT t.*,i.doc_num FROM
-  xpath_table('id', 'xml', 'test',
-              '/doc/line/@num|/doc/line/a|/doc/line/b|/doc/line/c',
-              'true')
-    AS t(id int, line_num varchar(10), val1 int, val2 int, val3 int),
-  xpath_table('id', 'xml', 'test', '/doc/@num', 'true')
-    AS i(id int, doc_num varchar(10))
-WHERE i.id=t.id AND i.id=1
-ORDER BY doc_num, line_num;
-
- id | line_num | val1 | val2 | val3 | doc_num
-----+----------+------+------+------+---------
-  1 | L1       |    1 |    2 |    3 | C1
-  1 | L2       |   11 |   22 |   33 | C1
-(2 rows)
-</programlisting>
-   </para>
-  </sect3>
- </sect2>
-
- <sect2>
-  <title>XSLT Functions</title>
-
-&common;
-  <para>
-   The following functions are available if libxslt is installed:
-  </para>
-
-  <sect3>
-   <title><literal>xslt_process</literal></title>
-
-<synopsis>
-xslt_process(text document, text stylesheet, text paramlist) returns text
-</synopsis>
-
-&common;
-   <para>
-    This function applies the XSL stylesheet to the document and returns
-    the transformed result. The <literal>paramlist</> is a list of parameter
-    assignments to be used in the transformation, specified in the form
-    <literal>a=1,b=2</>. Note that the
-    parameter parsing is very simple-minded: parameter values cannot
-    contain commas!
-   </para>
-
-   <para>
-    Also note that if either the document or stylesheet values do not
-    begin with a &lt; then they will be treated as URLs and libxslt will
-    fetch them. It follows that you can use <function>xslt_process</> as a
-    means to fetch the contents of URLs &mdash; you should be aware of the
-    security implications of this.
-   </para>
-
-   <para>
-    There is also a two-parameter version of <function>xslt_process</> which
-    does not pass any parameters to the transformation.
-   </para>
-  </sect3>
- </sect2>
-
- <sect2>
-  <title>Author</title>
-
-  <para>
-   John Gray <email>[email protected]</email>
-  </para>
-
-  <para>
-   Development of this module was sponsored by Torchbox Ltd. (www.torchbox.com).
-<!## PG>
-   It has the same BSD licence as PostgreSQL.
-<!## end>
-<!## XC>
-   It has the same BSD licence as Postgres-XC.
-<!## end>
-<!## XL>
-   It has the same BSD licence as PostgreSQL.
-<!## end>
-  </para>
- </sect2>
-
-</sect1>
diff --git a/doc-xc/src/sgml/xoper.sgmlin b/doc-xc/src/sgml/xoper.sgmlin
deleted file mode 100644
index f9e0285b58..0000000000
--- a/doc-xc/src/sgml/xoper.sgmlin
+++ /dev/null
@@ -1,532 +0,0 @@
-<!-- doc/src/sgml/xoper.sgml -->
-
- <sect1 id="xoper">
-  <title>User-defined Operators</title>
-
-  <indexterm zone="xoper">
-   <primary>operator</primary>
-   <secondary>user-defined</secondary>
-  </indexterm>
-
-&common;
-
-  <para>
-   Every operator is <quote>syntactic sugar</quote> for a call to an
-   underlying function that does the real work; so you must
-   first create the underlying function before you can create
-   the operator.  However, an operator is <emphasis>not merely</emphasis>
-   syntactic sugar, because it carries additional information
-   that helps the query planner optimize queries that use the
-   operator.  The next section will be devoted to explaining
-   that additional information.
-  </para>
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> supports left unary, right
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> supports left unary, right
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> supports left unary, right
-<!## end>
-   unary, and binary operators.  Operators can be
-   overloaded;<indexterm><primary>overloading</primary><secondary>operators</secondary></indexterm>
-   that is, the same operator name can be used for different operators
-   that have different numbers and types of operands.  When a query is
-   executed, the system determines the operator to call from the
-   number and types of the provided operands.
-  </para>
-
-  <para>
-   Here is an example of creating an operator for adding two complex
-   numbers.  We assume we've already created the definition of type
-   <type>complex</type> (see <xref linkend="xtypes">).  First we need a
-   function that does the work, then we can define the operator:
-
-<programlisting>
-CREATE FUNCTION complex_add(complex, complex)
-    RETURNS complex
-    AS '<replaceable>filename</replaceable>', 'complex_add'
-    LANGUAGE C IMMUTABLE STRICT;
-
-CREATE OPERATOR + (
-    leftarg = complex,
-    rightarg = complex,
-    procedure = complex_add,
-    commutator = +
-);
-</programlisting>
-  </para>
-
-  <para>
-   Now we could execute a query like this:
-
-<screen>
-SELECT (a + b) AS c FROM test_complex;
-
-        c
------------------
- (5.2,6.05)
- (133.42,144.95)
-</screen>
-  </para>
-
-  <para>
-   We've shown how to create a binary operator here.  To create unary
-   operators, just omit one of <literal>leftarg</> (for left unary) or
-   <literal>rightarg</> (for right unary).  The <literal>procedure</>
-   clause and the argument clauses are the only required items in
-   <command>CREATE OPERATOR</command>.  The <literal>commutator</>
-   clause shown in the example is an optional hint to the query
-   optimizer.  Further details about <literal>commutator</> and other
-   optimizer hints appear in the next section.
-  </para>
- </sect1>
-
-  <sect1 id="xoper-optimization">
-   <title>Operator Optimization Information</title>
-&common;
-   <para>
-<!## PG>
-    A <productname>PostgreSQL</productname> operator definition can include
-<!## end>
-<!## XC>
-    A <productname>Postgres-XC</productname> operator definition can include
-<!## end>
-<!## XL>
-    A <productname>Postgres-XL</productname> operator definition can include
-<!## end>
-    several optional clauses that tell the system useful things about how
-    the operator behaves.  These clauses should be provided whenever
-    appropriate, because they can make for considerable speedups in execution
-    of queries that use the operator.  But if you provide them, you must be
-    sure that they are right!  Incorrect use of an optimization clause can
-    result in slow queries, subtly wrong output, or other Bad Things.
-    You can always leave out an optimization clause if you are not sure
-    about it; the only consequence is that queries might run slower than
-    they need to.
-   </para>
-
-   <para>
-    Additional optimization clauses might be added in future versions of
-<!## PG>
-    <productname>PostgreSQL</productname>.  The ones described here are all
-<!## end>
-<!## XC>
-    <productname>Postgres-XC</productname>.  The ones described here are all
-<!## end>
-<!## XL>
-    <productname>Postgres-XL</productname>.  The ones described here are all
-<!## end>
-    the ones that release &version; understands.
-   </para>
-
-   <sect2>
-    <title><literal>COMMUTATOR</></title>
-&common;
-    <para>
-     The <literal>COMMUTATOR</> clause, if provided, names an operator that is the
-     commutator of the operator being defined.  We say that operator A is the
-     commutator of operator B if (x A y) equals (y B x) for all possible input
-     values x, y.  Notice that B is also the commutator of A.  For example,
-     operators <literal>&lt;</> and <literal>&gt;</> for a particular data type are usually each others'
-     commutators, and operator <literal>+</> is usually commutative with itself.
-     But operator <literal>-</> is usually not commutative with anything.
-    </para>
-
-    <para>
-     The left operand type of a commutable operator is the same as the
-     right operand type of its commutator, and vice versa.  So the name of
-<!## PG>
-     the commutator operator is all that <productname>PostgreSQL</productname>
-<!## end>
-<!## XC>
-     the commutator operator is all that <productname>Postgres-XC</productname>
-<!## end>
-<!## XL>
-     the commutator operator is all that <productname>Postgres-XL</productname>
-<!## end>
-     needs to be given to look up the commutator, and that's all that needs to
-     be provided in the <literal>COMMUTATOR</> clause.
-    </para>
-
-    <para>
-     It's critical to provide commutator information for operators that
-     will be used in indexes and join clauses, because this allows the
-     query optimizer to <quote>flip around</> such a clause to the forms
-     needed for different plan types.  For example, consider a query with
-     a WHERE clause like <literal>tab1.x = tab2.y</>, where <literal>tab1.x</>
-     and <literal>tab2.y</> are of a user-defined type, and suppose that
-     <literal>tab2.y</> is indexed.  The optimizer cannot generate an
-     index scan unless it can determine how to flip the clause around to
-     <literal>tab2.y = tab1.x</>, because the index-scan machinery expects
-     to see the indexed column on the left of the operator it is given.
-<!## PG>
-     <productname>PostgreSQL</productname> will <emphasis>not</> simply
-<!## end>
-<!## XC>
-     <productname>Postgres-XC</productname> will <emphasis>not</> simply
-<!## end>
-<!## XL>
-     <productname>Postgres-XL</productname> will <emphasis>not</> simply
-<!## end>
-     assume that this is a valid transformation &mdash; the creator of the
-     <literal>=</> operator must specify that it is valid, by marking the
-     operator with commutator information.
-    </para>
-
-    <para>
-     When you are defining a self-commutative operator, you just do it.
-     When you are defining a pair of commutative operators, things are
-     a little trickier: how can the first one to be defined refer to the
-     other one, which you haven't defined yet?  There are two solutions
-     to this problem:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        One way is to omit the <literal>COMMUTATOR</> clause in the first operator that
-        you define, and then provide one in the second operator's definition.
-<!## PG>
-        Since <productname>PostgreSQL</productname> knows that commutative
-<!## end>
-<!## XC>
-        Since <productname>Postgres-XC</productname> knows that commutative
-<!## end>
-<!## XL>
-        Since <productname>Postgres-XL</productname> knows that commutative
-<!## end>
-        operators come in pairs, when it sees the second definition it will
-        automatically go back and fill in the missing <literal>COMMUTATOR</> clause in
-        the first definition.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The other, more straightforward way is just to include <literal>COMMUTATOR</> clauses
-<!## PG>
-        in both definitions.  When <productname>PostgreSQL</productname> processes
-<!## end>
-<!## XC>
-        in both definitions.  When <productname>Postgres-XC</productname> processes
-<!## end>
-<!## XL>
-        in both definitions.  When <productname>Postgres-XL</productname> processes
-<!## end>
-        the first definition and realizes that <literal>COMMUTATOR</> refers to a nonexistent
-        operator, the system will make a dummy entry for that operator in the
-        system catalog.  This dummy entry will have valid data only
-        for the operator name, left and right operand types, and result type,
-<!## PG>
-        since that's all that <productname>PostgreSQL</productname> can deduce
-<!## end>
-<!## XC>
-        since that's all that <productname>Postgres-XC</productname> can deduce
-<!## end>
-<!## XL>
-        since that's all that <productname>Postgres-XL</productname> can deduce
-<!## end>
-        at this point.  The first operator's catalog entry will link to this
-        dummy entry.  Later, when you define the second operator, the system
-        updates the dummy entry with the additional information from the second
-        definition.  If you try to use the dummy operator before it's been filled
-        in, you'll just get an error message.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title><literal>NEGATOR</></title>
-&common;
-    <para>
-     The <literal>NEGATOR</> clause, if provided, names an operator that is the
-     negator of the operator being defined.  We say that operator A
-     is the negator of operator B if both return Boolean results and
-     (x A y) equals NOT (x B y) for all possible inputs x, y.
-     Notice that B is also the negator of A.
-     For example, <literal>&lt;</> and <literal>&gt;=</> are a negator pair for most data types.
-     An operator can never validly be its own negator.
-    </para>
-
-   <para>
-    Unlike commutators, a pair of unary operators could validly be marked
-    as each others' negators; that would mean (A x) equals NOT (B x)
-    for all x, or the equivalent for right unary operators.
-   </para>
-
-   <para>
-    An operator's negator must have the same left and/or right operand types
-    as the operator to be defined, so just as with <literal>COMMUTATOR</>, only the operator
-    name need be given in the <literal>NEGATOR</> clause.
-   </para>
-
-   <para>
-    Providing a negator is very helpful to the query optimizer since
-    it allows expressions like <literal>NOT (x = y)</> to be simplified into
-    <literal>x &lt;&gt; y</>.  This comes up more often than you might think, because
-    <literal>NOT</> operations can be inserted as a consequence of other rearrangements.
-   </para>
-
-   <para>
-    Pairs of negator operators can be defined using the same methods
-    explained above for commutator pairs.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title><literal>RESTRICT</></title>
-&common;
-   <para>
-    The <literal>RESTRICT</> clause, if provided, names a restriction selectivity
-    estimation function for the operator.  (Note that this is a function
-    name, not an operator name.)  <literal>RESTRICT</> clauses only make sense for
-    binary operators that return <type>boolean</>.  The idea behind a restriction
-    selectivity estimator is to guess what fraction of the rows in a
-    table will satisfy a <literal>WHERE</literal>-clause condition of the form:
-<programlisting>
-column OP constant
-</programlisting>
-    for the current operator and a particular constant value.
-    This assists the optimizer by
-    giving it some idea of how many rows will be eliminated by <literal>WHERE</>
-    clauses that have this form.  (What happens if the constant is on
-    the left, you might be wondering?  Well, that's one of the things that
-    <literal>COMMUTATOR</> is for...)
-   </para>
-
-   <para>
-    Writing new restriction selectivity estimation functions is far beyond
-    the scope of this chapter, but fortunately you can usually just use
-    one of the system's standard estimators for many of your own operators.
-    These are the standard restriction estimators:
-    <simplelist>
-     <member><function>eqsel</> for <literal>=</></member>
-     <member><function>neqsel</> for <literal>&lt;&gt;</></member>
-     <member><function>scalarltsel</> for <literal>&lt;</> or <literal>&lt;=</></member>
-     <member><function>scalargtsel</> for <literal>&gt;</> or <literal>&gt;=</></member>
-   </simplelist>
-    It might seem a little odd that these are the categories, but they
-    make sense if you think about it.  <literal>=</> will typically accept only
-    a small fraction of the rows in a table; <literal>&lt;&gt;</> will typically reject
-    only a small fraction.  <literal>&lt;</> will accept a fraction that depends on
-    where the given constant falls in the range of values for that table
-    column (which, it just so happens, is information collected by
-    <command>ANALYZE</command> and made available to the selectivity estimator).
-    <literal>&lt;=</> will accept a slightly larger fraction than <literal>&lt;</> for the same
-    comparison constant, but they're close enough to not be worth
-    distinguishing, especially since we're not likely to do better than a
-    rough guess anyhow.  Similar remarks apply to <literal>&gt;</> and <literal>&gt;=</>.
-   </para>
-
-   <para>
-    You can frequently get away with using either <function>eqsel</function> or <function>neqsel</function> for
-    operators that have very high or very low selectivity, even if they
-    aren't really equality or inequality.  For example, the
-    approximate-equality geometric operators use <function>eqsel</function> on the assumption that
-    they'll usually only match a small fraction of the entries in a table.
-   </para>
-
-   <para>
-    You can use <function>scalarltsel</> and <function>scalargtsel</> for comparisons on data types that
-    have some sensible means of being converted into numeric scalars for
-    range comparisons.  If possible, add the data type to those understood
-    by the function <function>convert_to_scalar()</function> in <filename>src/backend/utils/adt/selfuncs.c</filename>.
-    (Eventually, this function should be replaced by per-data-type functions
-    identified through a column of the <classname>pg_type</> system catalog; but that hasn't happened
-    yet.)  If you do not do this, things will still work, but the optimizer's
-    estimates won't be as good as they could be.
-   </para>
-
-   <para>
-    There are additional selectivity estimation functions designed for geometric
-    operators in <filename>src/backend/utils/adt/geo_selfuncs.c</filename>: <function>areasel</function>, <function>positionsel</function>,
-    and <function>contsel</function>.  At this writing these are just stubs, but you might want
-    to use them (or even better, improve them) anyway.
-   </para>
-   </sect2>
-
-   <sect2>
-    <title><literal>JOIN</></title>
-&common;
-    <para>
-     The <literal>JOIN</> clause, if provided, names a join selectivity
-     estimation function for the operator.  (Note that this is a function
-     name, not an operator name.)  <literal>JOIN</> clauses only make sense for
-     binary operators that return <type>boolean</type>.  The idea behind a join
-     selectivity estimator is to guess what fraction of the rows in a
-     pair of tables will satisfy a <literal>WHERE</>-clause condition of the form:
-<programlisting>
-table1.column1 OP table2.column2
-</programlisting>
-     for the current operator.  As with the <literal>RESTRICT</literal> clause, this helps
-     the optimizer very substantially by letting it figure out which
-     of several possible join sequences is likely to take the least work.
-    </para>
-
-    <para>
-     As before, this chapter will make no attempt to explain how to write
-     a join selectivity estimator function, but will just suggest that
-     you use one of the standard estimators if one is applicable:
-     <simplelist>
-      <member><function>eqjoinsel</> for <literal>=</></member>
-      <member><function>neqjoinsel</> for <literal>&lt;&gt;</></member>
-      <member><function>scalarltjoinsel</> for <literal>&lt;</> or <literal>&lt;=</></member>
-      <member><function>scalargtjoinsel</> for <literal>&gt;</> or <literal>&gt;=</></member>
-      <member><function>areajoinsel</> for 2D area-based comparisons</member>
-      <member><function>positionjoinsel</> for 2D position-based comparisons</member>
-      <member><function>contjoinsel</> for 2D containment-based comparisons</member>
-     </simplelist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title><literal>HASHES</></title>
-&common;
-    <para>
-     The <literal>HASHES</literal> clause, if present, tells the system that
-     it is permissible to use the hash join method for a join based on this
-     operator.  <literal>HASHES</> only makes sense for a binary operator that
-     returns <literal>boolean</>, and in practice the operator must represent
-     equality for some data type or pair of data types.
-    </para>
-
-    <para>
-     The assumption underlying hash join is that the join operator can
-     only return true for pairs of left and right values that hash to the
-     same hash code.  If two values get put in different hash buckets, the
-     join will never compare them at all, implicitly assuming that the
-     result of the join operator must be false.  So it never makes sense
-     to specify <literal>HASHES</literal> for operators that do not represent
-     some form of equality.  In most cases it is only practical to support
-     hashing for operators that take the same data type on both sides.
-     However, sometimes it is possible to design compatible hash functions
-     for two or more data types; that is, functions that will generate the
-     same hash codes for <quote>equal</> values, even though the values
-     have different representations.  For example, it's fairly simple
-     to arrange this property when hashing integers of different widths.
-    </para>
-
-    <para>
-     To be marked <literal>HASHES</literal>, the join operator must appear
-     in a hash index operator family.  This is not enforced when you create
-     the operator, since of course the referencing operator family couldn't
-     exist yet.  But attempts to use the operator in hash joins will fail
-     at run time if no such operator family exists.  The system needs the
-     operator family to find the data-type-specific hash function(s) for the
-     operator's input data type(s).  Of course, you must also create suitable
-     hash functions before you can create the operator family.
-    </para>
-
-    <para>
-     Care should be exercised when preparing a hash function, because there
-     are machine-dependent ways in which it might fail to do the right thing.
-     For example, if your data type is a structure in which there might be
-     uninteresting pad bits, you cannot simply pass the whole structure to
-     <function>hash_any</>.  (Unless you write your other operators and
-     functions to ensure that the unused bits are always zero, which is the
-     recommended strategy.)
-     Another example is that on machines that meet the <acronym>IEEE</>
-     floating-point standard, negative zero and positive zero are different
-     values (different bit patterns) but they are defined to compare equal.
-     If a float value might contain negative zero then extra steps are needed
-     to ensure it generates the same hash value as positive zero.
-    </para>
-
-    <para>
-     A hash-joinable operator must have a commutator (itself if the two
-     operand data types are the same, or a related equality operator
-     if they are different) that appears in the same operator family.
-     If this is not the case, planner errors might occur when the operator
-     is used.  Also, it is a good idea (but not strictly required) for
-     a hash operator family that supports multiple data types to provide
-     equality operators for every combination of the data types; this
-     allows better optimization.
-    </para>
-
-    <note>
-    <para>
-     The function underlying a hash-joinable operator must be marked
-     immutable or stable.  If it is volatile, the system will never
-     attempt to use the operator for a hash join.
-    </para>
-    </note>
-
-    <note>
-    <para>
-     If a hash-joinable operator has an underlying function that is marked
-     strict, the
-     function must also be complete: that is, it should return true or
-     false, never null, for any two nonnull inputs.  If this rule is
-     not followed, hash-optimization of <literal>IN</> operations might
-     generate wrong results.  (Specifically, <literal>IN</> might return
-     false where the correct answer according to the standard would be null;
-     or it might yield an error complaining that it wasn't prepared for a
-     null result.)
-    </para>
-    </note>
-
-   </sect2>
-
-   <sect2>
-    <title><literal>MERGES</></title>
-&common;
-    <para>
-     The <literal>MERGES</literal> clause, if present, tells the system that
-     it is permissible to use the merge-join method for a join based on this
-     operator.  <literal>MERGES</> only makes sense for a binary operator that
-     returns <literal>boolean</>, and in practice the operator must represent
-     equality for some data type or pair of data types.
-    </para>
-
-    <para>
-     Merge join is based on the idea of sorting the left- and right-hand tables
-     into order and then scanning them in parallel.  So, both data types must
-     be capable of being fully ordered, and the join operator must be one
-     that can only succeed for pairs of values that fall at the
-     <quote>same place</>
-     in the sort order.  In practice this means that the join operator must
-     behave like equality.  But it is possible to merge-join two
-     distinct data types so long as they are logically compatible.  For
-     example, the <type>smallint</type>-versus-<type>integer</type>
-     equality operator is merge-joinable.
-     We only need sorting operators that will bring both data types into a
-     logically compatible sequence.
-    </para>
-
-    <para>
-     To be marked <literal>MERGES</literal>, the join operator must appear
-     as an equality member of a <literal>btree</> index operator family.
-     This is not enforced when you create
-     the operator, since of course the referencing operator family couldn't
-     exist yet.  But the operator will not actually be used for merge joins
-     unless a matching operator family can be found.  The
-     <literal>MERGES</literal> flag thus acts as a hint to the planner that
-     it's worth looking for a matching operator family.
-    </para>
-
-    <para>
-     A merge-joinable operator must have a commutator (itself if the two
-     operand data types are the same, or a related equality operator
-     if they are different) that appears in the same operator family.
-     If this is not the case, planner errors might occur when the operator
-     is used.  Also, it is a good idea (but not strictly required) for
-     a <literal>btree</> operator family that supports multiple data types to provide
-     equality operators for every combination of the data types; this
-     allows better optimization.
-    </para>
-
-    <note>
-    <para>
-     The function underlying a merge-joinable operator must be marked
-     immutable or stable.  If it is volatile, the system will never
-     attempt to use the operator for a merge join.
-    </para>
-    </note>
-   </sect2>
-  </sect1>
diff --git a/doc-xc/src/sgml/xplang.sgmlin b/doc-xc/src/sgml/xplang.sgmlin
deleted file mode 100644
index 1a8d54b3fa..0000000000
--- a/doc-xc/src/sgml/xplang.sgmlin
+++ /dev/null
@@ -1,274 +0,0 @@
-<!-- doc/src/sgml/xplang.sgml -->
-
- <chapter id="xplang">
-  <title>Procedural Languages</title>
-
-  <indexterm zone="xplang">
-   <primary>procedural language</primary>
-  </indexterm>
-
-&common;
-
-  <para>
-<!## PG>
-   <productname>PostgreSQL</productname> allows user-defined functions
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> allows user-defined functions
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> allows user-defined functions
-<!## end>
-   to be written in other languages besides SQL and C.  These other
-   languages are generically called <firstterm>procedural
-   languages</firstterm> (<acronym>PL</>s).  For a function
-   written in a procedural language, the database server has
-   no built-in knowledge about how to interpret the function's source
-   text. Instead, the task is passed to a special handler that knows
-   the details of the language.  The handler could either do all the
-   work of parsing, syntax analysis, execution, etc. itself, or it
-   could serve as <quote>glue</quote> between
-<!## PG>
-   <productname>PostgreSQL</productname> and an existing implementation
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> and an existing implementation
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> and an existing implementation
-<!## end>
-   of a programming language.  The handler itself is a
-   C language function compiled into a shared object and
-   loaded on demand, just like any other C function.
-  </para>
-
-  <para>
-   There are currently four procedural languages available in the
-<!## PG>
-   standard <productname>PostgreSQL</productname> distribution:
-<!## end>
-<!## XC>
-   standard <productname>Postgres-XC</productname> distribution:
-<!## end>
-<!## XL>
-   standard <productname>Postgres-XL</productname> distribution:
-<!## end>
-   <application>PL/pgSQL</application> (<xref linkend="plpgsql">),
-   <application>PL/Tcl</application> (<xref linkend="pltcl">),
-   <application>PL/Perl</application> (<xref linkend="plperl">), and
-   <application>PL/Python</application> (<xref linkend="plpython">).
-   There are additional procedural languages available that are not
-   included in the core distribution. <xref linkend="external-projects">
-   has information about finding them. In addition other languages can
-   be defined by users; the basics of developing a new procedural
-   language are covered in <xref linkend="plhandler">.
-  </para>
-
-  <sect1 id="xplang-install">
-   <title>Installing Procedural Languages</title>
-
-&common;
-   <para>
-    A procedural language must be <quote>installed</quote> into each
-    database where it is to be used.  But procedural languages installed in
-    the database <literal>template1</> are automatically available in all
-    subsequently created databases, since their entries in
-    <literal>template1</> will be copied by <command>CREATE DATABASE</>.
-    So the database administrator can
-    decide which languages are available in which databases and can make
-    some languages available by default if he chooses.
-   </para>
-
-   <para>
-    For the languages supplied with the standard distribution, it is
-    only necessary to execute <command>CREATE EXTENSION</>
-    <replaceable>language_name</> to install the language into the
-    current database.  Alternatively, the program <xref
-    linkend="app-createlang"> can be used to do this from the shell
-    command line.  For example, to install the language
-    <application>PL/Perl</application> into the database
-    <literal>template1</>, use:
-<programlisting>
-createlang plperl template1
-</programlisting>
-    The manual procedure described below is only recommended for
-    installing languages that have not been packaged as extensions.
-   </para>
-
-   <procedure>
-    <title>
-     Manual Procedural Language Installation
-    </title>
-
-    <para>
-     A procedural language is installed in a database in five steps,
-     which must be carried out by a database superuser.  In most cases
-     the required SQL commands should be packaged as the installation script
-     of an <quote>extension</>, so that <command>CREATE EXTENSION</> can be
-     used to execute them.
-    </para>
-
-    <step performance="required" id="xplang-install-cr1">
-     <para>
-      The shared object for the language handler must be compiled and
-      installed into an appropriate library directory.  This works in the same
-      way as building and installing modules with regular user-defined C
-      functions does; see <xref linkend="dfunc">.  Often, the language
-      handler will depend on an external library that provides the actual
-      programming language engine; if so, that must be installed as well.
-     </para>
-    </step>
-
-    <step performance="required" id="xplang-install-cr2">
-     <para>
-      The handler must be declared with the command
-<synopsis>
-CREATE FUNCTION <replaceable>handler_function_name</replaceable>()
-    RETURNS language_handler
-    AS '<replaceable>path-to-shared-object</replaceable>'
-    LANGUAGE C;
-</synopsis>
-      The special return type of <type>language_handler</type> tells
-      the database system that this function does not return one of
-      the defined <acronym>SQL</acronym> data types and is not directly usable
-      in <acronym>SQL</acronym> statements.
-     </para>
-    </step>
-
-    <step performance="optional" id="xplang-install-cr3">
-     <para>
-      Optionally, the language handler can provide an <quote>inline</>
-      handler function that executes anonymous code blocks
-      (<xref linkend="sql-do"> commands)
-      written in this language.  If an inline handler function
-      is provided by the language, declare it with a command like
-<synopsis>
-CREATE FUNCTION <replaceable>inline_function_name</replaceable>(internal)
-    RETURNS void
-    AS '<replaceable>path-to-shared-object</replaceable>'
-    LANGUAGE C;
-</synopsis>
-     </para>
-    </step>
-
-    <step performance="optional" id="xplang-install-cr4">
-     <para>
-      Optionally, the language handler can provide a <quote>validator</>
-      function that checks a function definition for correctness without
-      actually executing it.  The validator function is called by
-      <command>CREATE FUNCTION</> if it exists.  If a validator function
-      is provided by the language, declare it with a command like
-<synopsis>
-CREATE FUNCTION <replaceable>validator_function_name</replaceable>(oid)
-    RETURNS void
-    AS '<replaceable>path-to-shared-object</replaceable>'
-    LANGUAGE C STRICT;
-</synopsis>
-     </para>
-    </step>
-
-    <step performance="required" id="xplang-install-cr5">
-     <para>
-      Finally, the PL must be declared with the command
-<synopsis>
-CREATE <optional>TRUSTED</optional> <optional>PROCEDURAL</optional> LANGUAGE <replaceable>language-name</replaceable>
-    HANDLER <replaceable>handler_function_name</replaceable>
-    <optional>INLINE <replaceable>inline_function_name</replaceable></optional>
-    <optional>VALIDATOR <replaceable>validator_function_name</replaceable></optional> ;
-</synopsis>
-      The optional key word <literal>TRUSTED</literal> specifies that
-      the language does not grant access to data that the user would
-      not otherwise have.  Trusted languages are designed for ordinary
-      database users (those without superuser privilege) and allows them
-      to safely create functions and trigger
-      procedures. Since PL functions are executed inside the database
-      server, the <literal>TRUSTED</literal> flag should only be given
-      for languages that do not allow access to database server
-      internals or the file system. The languages
-      <application>PL/pgSQL</application>,
-      <application>PL/Tcl</application>, and
-      <application>PL/Perl</application>
-      are considered trusted; the languages
-      <application>PL/TclU</application>,
-      <application>PL/PerlU</application>, and
-      <application>PL/PythonU</application>
-      are designed to provide unlimited functionality and should
-      <emphasis>not</emphasis> be marked trusted.
-     </para>
-    </step>
-   </procedure>
-
-   <para>
-    <xref linkend="xplang-install-example"> shows how the manual
-    installation procedure would work with the language
-    <application>PL/Perl</application>.
-   </para>
-
-   <example id="xplang-install-example">
-    <title>Manual Installation of <application>PL/Perl</application></title>
-
-     <para>
-      The following command tells the database server where to find the
-      shared object for the <application>PL/Perl</application> language's call
-      handler function:
-
-<programlisting>
-CREATE FUNCTION plperl_call_handler() RETURNS language_handler AS
-    '$libdir/plperl' LANGUAGE C;
-</programlisting>
-     </para>
-
-     <para>
-      <application>PL/Perl</application> has an inline handler function
-      and a validator function, so we declare those too:
-
-<programlisting>
-CREATE FUNCTION plperl_inline_handler(internal) RETURNS void AS
-    '$libdir/plperl' LANGUAGE C;
-
-CREATE FUNCTION plperl_validator(oid) RETURNS void AS
-    '$libdir/plperl' LANGUAGE C STRICT;
-</programlisting>
-     </para>
-
-     <para>
-      The command:
-<programlisting>
-CREATE TRUSTED PROCEDURAL LANGUAGE plperl
-    HANDLER plperl_call_handler
-    INLINE plperl_inline_handler
-    VALIDATOR plperl_validator;
-</programlisting>
-      then defines that the previously declared functions
-      should be invoked for functions and trigger procedures where the
-      language attribute is <literal>plperl</literal>.
-     </para>
-  </example>
-
-   <para>
-<!## PG>
-    In a default <productname>PostgreSQL</productname> installation,
-<!## end>
-<!## XC>
-    In a default <productname>Postgres-XC</productname> installation,
-<!## end>
-<!## XL>
-    In a default <productname>Postgres-XL</productname> installation,
-<!## end>
-    the handler for the <application>PL/pgSQL</application> language
-    is built and installed into the <quote>library</quote>
-    directory; furthermore, the <application>PL/pgSQL</application> language
-    itself is installed in all databases.
-    If <application>Tcl</> support is configured in, the handlers for
-    <application>PL/Tcl</> and <application>PL/TclU</> are built and installed
-    in the library directory, but the language itself is not installed in any
-    database by default.
-    Likewise, the <application>PL/Perl</> and <application>PL/PerlU</>
-    handlers are built and installed if Perl support is configured, and the
-    <application>PL/PythonU</> handler is installed if Python support is
-    configured, but these languages are not installed by default.
-   </para>
-
-  </sect1>
-
-</chapter>
diff --git a/doc-xc/src/sgml/xtypes.sgmlin b/doc-xc/src/sgml/xtypes.sgmlin
deleted file mode 100644
index bf94ac5c56..0000000000
--- a/doc-xc/src/sgml/xtypes.sgmlin
+++ /dev/null
@@ -1,312 +0,0 @@
-<!-- doc/src/sgml/xtypes.sgml -->
-
- <sect1 id="xtypes">
-  <title>User-defined Types</title>
-
-  <indexterm zone="xtypes">
-   <primary>data type</primary>
-   <secondary>user-defined</secondary>
-  </indexterm>
-
-&common;
-
-  <para>
-   As described in <xref linkend="extend-type-system">,
-<!## PG>
-   <productname>PostgreSQL</productname> can be extended to support new
-<!## end>
-<!## XC>
-   <productname>Postgres-XC</productname> can be extended to support new
-<!## end>
-<!## XL>
-   <productname>Postgres-XL</productname> can be extended to support new
-<!## end>
-   data types.  This section describes how to define new base types,
-   which are data types defined below the level of the <acronym>SQL</>
-   language.  Creating a new base type requires implementing functions
-   to operate on the type in a low-level language, usually C.
-  </para>
-
-  <para>
-   The examples in this section can be found in
-   <filename>complex.sql</filename> and <filename>complex.c</filename>
-   in the <filename>src/tutorial</> directory of the source distribution.
-   See the <filename>README</> file in that directory for instructions
-   about running the examples.
-  </para>
-
- <para>
-  <indexterm>
-   <primary>input function</primary>
-  </indexterm>
-  <indexterm>
-   <primary>output function</primary>
-  </indexterm>
-  A user-defined type must always have input and output functions.
-  These functions determine how the type appears in strings (for input
-  by the user and output to the user) and how the type is organized in
-  memory.  The input function takes a null-terminated character string
-  as its argument and returns the internal (in memory) representation
-  of the type.  The output function takes the internal representation
-  of the type as argument and returns a null-terminated character
-  string.  If we want to do anything more with the type than merely
-  store it, we must provide additional functions to implement whatever
-  operations we'd like to have for the type.
- </para>
-
- <para>
-  Suppose we want to define a type <type>complex</> that represents
-  complex numbers. A natural way to represent a complex number in
-  memory would be the following C structure:
-
-<programlisting>
-typedef struct Complex {
-    double      x;
-    double      y;
-} Complex;
-</programlisting>
-
-  We will need to make this a pass-by-reference type, since it's too
-  large to fit into a single <type>Datum</> value.
- </para>
-
- <para>
-  As the external string representation of the type, we choose a
-  string of the form <literal>(x,y)</literal>.
- </para>
-
- <para>
-  The input and output functions are usually not hard to write,
-  especially the output function.  But when defining the external
-  string representation of the type, remember that you must eventually
-  write a complete and robust parser for that representation as your
-  input function.  For instance:
-
-<programlisting><![CDATA[
-PG_FUNCTION_INFO_V1(complex_in);
-
-Datum
-complex_in(PG_FUNCTION_ARGS)
-{
-    char       *str = PG_GETARG_CSTRING(0);
-    double      x,
-                y;
-    Complex    *result;
-
-    if (sscanf(str, " ( %lf , %lf )", &x, &y) != 2)
-        ereport(ERROR,
-                (errcode(ERRCODE_INVALID_TEXT_REPRESENTATION),
-                 errmsg("invalid input syntax for complex: \"%s\"",
-                        str)));
-
-    result = (Complex *) palloc(sizeof(Complex));
-    result->x = x;
-    result->y = y;
-    PG_RETURN_POINTER(result);
-}
-]]>
-</programlisting>
-
-  The output function can simply be:
-
-<programlisting><![CDATA[
-PG_FUNCTION_INFO_V1(complex_out);
-
-Datum
-complex_out(PG_FUNCTION_ARGS)
-{
-    Complex    *complex = (Complex *) PG_GETARG_POINTER(0);
-    char       *result;
-
-    result = (char *) palloc(100);
-    snprintf(result, 100, "(%g,%g)", complex->x, complex->y);
-    PG_RETURN_CSTRING(result);
-}
-]]>
-</programlisting>
- </para>
-
- <para>
-  You should be careful to make the input and output functions inverses of
-  each other.  If you do not, you will have severe problems when you
-  need to dump your data into a file and then read it back in.  This
-  is a particularly common problem when floating-point numbers are
-  involved.
- </para>
-
- <para>
-  Optionally, a user-defined type can provide binary input and output
-  routines.  Binary I/O is normally faster but less portable than textual
-  I/O.  As with textual I/O, it is up to you to define exactly what the
-  external binary representation is.  Most of the built-in data types
-  try to provide a machine-independent binary representation.  For
-  <type>complex</type>, we will piggy-back on the binary I/O converters
-  for type <type>float8</>:
-
-<programlisting><![CDATA[
-PG_FUNCTION_INFO_V1(complex_recv);
-
-Datum
-complex_recv(PG_FUNCTION_ARGS)
-{
-    StringInfo  buf = (StringInfo) PG_GETARG_POINTER(0);
-    Complex    *result;
-
-    result = (Complex *) palloc(sizeof(Complex));
-    result->x = pq_getmsgfloat8(buf);
-    result->y = pq_getmsgfloat8(buf);
-    PG_RETURN_POINTER(result);
-}
-
-PG_FUNCTION_INFO_V1(complex_send);
-
-Datum
-complex_send(PG_FUNCTION_ARGS)
-{
-    Complex    *complex = (Complex *) PG_GETARG_POINTER(0);
-    StringInfoData buf;
-
-    pq_begintypsend(&buf);
-    pq_sendfloat8(&buf, complex->x);
-    pq_sendfloat8(&buf, complex->y);
-    PG_RETURN_BYTEA_P(pq_endtypsend(&buf));
-}
-]]>
-</programlisting>
- </para>
-
- <para>
-  Once we have written the I/O functions and compiled them into a shared
-  library, we can define the <type>complex</type> type in SQL.
-  First we declare it as a shell type:
-
-<programlisting>
-CREATE TYPE complex;
-</programlisting>
-
-  This serves as a placeholder that allows us to reference the type while
-  defining its I/O functions.  Now we can define the I/O functions:
-
-<programlisting>
-CREATE FUNCTION complex_in(cstring)
-    RETURNS complex
-    AS '<replaceable>filename</replaceable>'
-    LANGUAGE C IMMUTABLE STRICT;
-
-CREATE FUNCTION complex_out(complex)
-    RETURNS cstring
-    AS '<replaceable>filename</replaceable>'
-    LANGUAGE C IMMUTABLE STRICT;
-
-CREATE FUNCTION complex_recv(internal)
-   RETURNS complex
-   AS '<replaceable>filename</replaceable>'
-   LANGUAGE C IMMUTABLE STRICT;
-
-CREATE FUNCTION complex_send(complex)
-   RETURNS bytea
-   AS '<replaceable>filename</replaceable>'
-   LANGUAGE C IMMUTABLE STRICT;
-</programlisting>
- </para>
-
- <para>
-  Finally, we can provide the full definition of the data type:
-<programlisting>
-CREATE TYPE complex (
-   internallength = 16,
-   input = complex_in,
-   output = complex_out,
-   receive = complex_recv,
-   send = complex_send,
-   alignment = double
-);
-</programlisting>
- </para>
-
- <para>
-  <indexterm>
-    <primary>array</primary>
-    <secondary>of user-defined type</secondary>
-  </indexterm>
-  When you define a new base type,
-<!## PG>
-  <productname>PostgreSQL</productname> automatically provides support
-<!## end>
-<!## XC>
-  <productname>Postgres-XC</productname> automatically provides support
-<!## end>
-<!## XL>
-  <productname>Postgres-XL</productname> automatically provides support
-<!## end>
-  for arrays of that type.  The array type typically
-  has the same name as the base type with the underscore character
-  (<literal>_</>) prepended.
- </para>
-
- <para>
-  Once the data type exists, we can declare additional functions to
-  provide useful operations on the data type.  Operators can then be
-  defined atop the functions, and if needed, operator classes can be
-  created to support indexing of the data type.  These additional
-  layers are discussed in following sections.
- </para>
-
- <para>
-   <indexterm>
-    <primary>TOAST</primary>
-    <secondary>and user-defined types</secondary>
-   </indexterm>
-  If the values of your data type vary in size (in internal form), you should
-  make the data type <acronym>TOAST</>-able (see <xref
-  linkend="storage-toast">). You should do this even if the data are always
-  too small to be compressed or stored externally, because
-  <acronym>TOAST</> can save space on small data too, by reducing header
-  overhead.
- </para>
-
- <para>
-  To do this, the internal representation must follow the standard layout for
-  variable-length data: the first four bytes must be a <type>char[4]</type>
-  field which is never accessed directly (customarily named
-  <structfield>vl_len_</>). You
-  must use <function>SET_VARSIZE()</function> to store the size of the datum
-  in this field and <function>VARSIZE()</function> to retrieve it. The C
-  functions operating on the data type must always be careful to unpack any
-  toasted values they are handed, by using <function>PG_DETOAST_DATUM</>.
-  (This detail is customarily hidden by defining type-specific
-  <function>GETARG_DATATYPE_P</function> macros.) Then, when running the
-  <command>CREATE TYPE</command> command, specify the internal length as
-  <literal>variable</> and select the appropriate storage option.
- </para>
-
- <para>
-  If the alignment is unimportant (either just for a specific function or
-  because the data type specifies byte alignment anyway) then it's possible
-  to avoid some of the overhead of <function>PG_DETOAST_DATUM</>. You can use
-  <function>PG_DETOAST_DATUM_PACKED</> instead (customarily hidden by
-  defining a <function>GETARG_DATATYPE_PP</> macro) and using the macros
-  <function>VARSIZE_ANY_EXHDR</> and <function>VARDATA_ANY</> to access
-  a potentially-packed datum.
-  Again, the data returned by these macros is not aligned even if the data
-  type definition specifies an alignment. If the alignment is important you
-  must go through the regular <function>PG_DETOAST_DATUM</> interface.
- </para>
-
- <note>
-  <para>
-   Older code frequently declares <structfield>vl_len_</> as an
-   <type>int32</> field instead of <type>char[4]</>.  This is OK as long as
-   the struct definition has other fields that have at least <type>int32</>
-   alignment.  But it is dangerous to use such a struct definition when
-   working with a potentially unaligned datum; the compiler may take it as
-   license to assume the datum actually is aligned, leading to core dumps on
-   architectures that are strict about alignment.
-  </para>
- </note>
-
- <para>
-  For further details see the description of the
-  <xref linkend="sql-createtype"> command.
- </para>
-</sect1>
diff --git a/src/Makefile b/src/Makefile
index c554bcf38b..b2295597bf 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -18,7 +18,6 @@ SUBDIRS = \
 	timezone \
 	gtm \
 	interfaces \
-	pgxc \
 	backend \
 	backend/utils/mb/conversion_procs \
 	backend/snowball \
diff --git a/src/bin/psql/Makefile b/src/bin/psql/Makefile
index ab42e81bd2..f1336d5026 100644
--- a/src/bin/psql/Makefile
+++ b/src/bin/psql/Makefile
@@ -16,10 +16,7 @@ subdir = src/bin/psql
 top_builddir = ../../..
 include $(top_builddir)/src/Makefile.global
 
-REFDOCDIR= $(top_srcdir)/doc-xc/src/sgml/ref
-
-MAKESGMLDIR = $(top_builddir)/src/pgxc/tools/makesgml
-SGMLDIR= $(top_builddir)/doc-xc/src/sgml
+REFDOCDIR= $(top_srcdir)/doc/src/sgml/ref
 
 override CPPFLAGS := -I. -I$(srcdir) -I$(libpq_srcdir) -I$(top_srcdir)/src/bin/pg_dump $(CPPFLAGS)
 
@@ -45,8 +42,6 @@ kwlookup.c: % : $(top_srcdir)/src/backend/parser/%
 
 sql_help.c: sql_help.h ;
 sql_help.h: create_help.pl $(wildcard $(REFDOCDIR)/*.sgml)
-	$(MAKE) -C $(MAKESGMLDIR)
-	$(MAKE) -C $(SGMLDIR) sgml-files
 	$(PERL) $< $(REFDOCDIR) $*
 
 # psqlscan is compiled as part of mainloop
diff --git a/src/pgxc/Makefile b/src/pgxc/Makefile
deleted file mode 100644
index 553e5deb73..0000000000
--- a/src/pgxc/Makefile
+++ /dev/null
@@ -1,17 +0,0 @@
-#----------------------------------------------------------------------------
-#
-# Postgres-XC documentation tool makefile
-#
-# Copyright (c) 2010-2012 Postgres-XC Development Group
-#
-# doc-xc/Makefile
-#
-#----------------------------------------------------------------------------
-
-subdir = src/pgxc
-top_builddir = ../..
-include $(top_builddir)/src/Makefile.global
-
-SUBDIRS = tools
-
-$(recurse)
diff --git a/src/pgxc/tools/Makefile b/src/pgxc/tools/Makefile
deleted file mode 100644
index 523d0994db..0000000000
--- a/src/pgxc/tools/Makefile
+++ /dev/null
@@ -1,18 +0,0 @@
-#----------------------------------------------------------------------------
-#
-# Postgres-XC documentation tool makefile
-#
-# Copyright (c) 2010-2012 Postgres-XC Development Group
-#
-# doc-xc/Makefile
-#
-#----------------------------------------------------------------------------
-
-subdir = src/pgxc/tools
-top_builddir = ../../..
-include $(top_builddir)/src/Makefile.global
-
-SUBDIRS = makesgml
-
-all distprep html man install installdirs uninstall clean distclean maintainer-clean maintainer-check:
-	$(MAKE) -C $(SUBDIRS) $@
diff --git a/src/pgxc/tools/makesgml/.gitignore b/src/pgxc/tools/makesgml/.gitignore
deleted file mode 100644
index a9141e02d3..0000000000
--- a/src/pgxc/tools/makesgml/.gitignore
+++ /dev/null
@@ -1 +0,0 @@
-/makesgml
diff --git a/src/pgxc/tools/makesgml/Makefile b/src/pgxc/tools/makesgml/Makefile
deleted file mode 100644
index b773bc001e..0000000000
--- a/src/pgxc/tools/makesgml/Makefile
+++ /dev/null
@@ -1,37 +0,0 @@
-#----------------------------------------------------------------------------
-#
-# Postgres-XC makesgml tool makefile
-#
-# Copyright(c) 2010-2012 Postgres-XC Development Group
-#
-# src/pgxc/tools/makesgml/Makefile
-#
-#-----------------------------------------------------------------------------
-
-PGFILEDESC = "makesgml - convert .sgmlin to .sgml"
-PGAPPICON=win32
-
-subdir = src/pgxc/tools/makesgml
-top_builddir = ../../../..
-include $(top_builddir)/src/Makefile.global
-
-override CPPFLAGS := -I. -I$(srcdir) $(CPPFLAGS)
-
-OBJS = makesgml.o
-
-makesgml: $(OBJS)
-	$(CC) $(CFLAGS) $(LDFLAGS) $^ -o $@$(X)
-
-all distprep html man: makesgml
-
-install: all installdirs
-	$(INSTALL_PROGRAM) makesgml$(X) '$(DESTDIR)$(bindir)/makesgml$(X)'
-
-installdirs:
-	$(MKDIR_P) '$(DESTDIR)$(bindir)'
-
-uninstall:
-	rm -rf '$(DESTDIR)$(bindir)/makesgml$(X)'
-
-clean distclean maintenance-clean maintainer-clean:
-	rm -rf makesgml$(X) $(OBJS)
diff --git a/src/pgxc/tools/makesgml/README b/src/pgxc/tools/makesgml/README
deleted file mode 100644
index 2c3a8b3016..0000000000
--- a/src/pgxc/tools/makesgml/README
+++ /dev/null
@@ -1,63 +0,0 @@
-README for SGML construction tool.
-
-Aug.2, 2011, Koichi Suzuki
-
-============================================
-This directory contains SGML source file build tool "makesgml".
-Please simply compile and place the binary to the directory of your
-choice.
-
-As you see, all the document "source" files are not ".sgml", but are
-".sgmlin".  This change was made to preserve all the original
-PostgreSQL document, select, modify and add common and Postgres-XC
-specific descriptions.
-
-Background and practice are as follows:
-
-We should be careful to make it easier to merge with later version of
-PostgreSQL SGML files. To do this, we can embed special "TAG" to
-distinguish what is common, what is PostgreSQL-specific and what is
-Postgres-XC specific. Also, we may want to distinguish translation to
-different languages.
-
-To make it easier to handle as an external tool, we can build
-dedicated (but somewhat general) tool to select what tags to be
-included. At present, the format is <!## tag> ... <!## end>. These
-tags can appear just itself as separate lines. Lines not enclosed with
-any such tags are common to all.
-
-So SGML file may look like... 
-
----------------------
-   ...
-   <para>
-   <!## PG>
-   ...
-   <!## end>
-   <!## XC>
-   ...
-   <!## end>
-   </para>
---------------------
-
-You can nest this tag. With the nest, you can include multiple
-translations in a single file.
-
-This can be handled by a command makesgml, which will be placed at
-postgres-xc/doc/tools.
-
-Makesgml can be invoked like 
-
-------------------
-makesgml -i inf -o outf -I include_tag ... -E exclude_tag ...
-------------------
-
-Each argument is optional and order of the argument is arbitrary. If
-you omit -i option, it will read from stdin. If -o is omitted, it will
-write to stdout. If input file include unspecified tags in the
-arguments, it will be treated as specified -E.
-
-All the sgml files from original PostgreSQL tarball will be renamed to
-sgmlin. Then it will be filtered by makesgml and fed to original
-document build scripts.
-
diff --git a/src/pgxc/tools/makesgml/makesgml.c b/src/pgxc/tools/makesgml/makesgml.c
deleted file mode 100644
index 1cf03228bf..0000000000
--- a/src/pgxc/tools/makesgml/makesgml.c
+++ /dev/null
@@ -1,379 +0,0 @@
-/*----------------------------------------------------------------------------
- *
- * makesgml - Postgres-XC document build tool
- *
- * Copyright (c) 2010-2012, Postgres-XC Development Group
- *
- * IDENTIFICATION
- *		src/pgxc/tools/makesgml/makesgml.c
- *
- * This tools converts .sgmlin files into .sgml files to be handled by
- * many tools to generate Postgres-XC documants.
- *
- * To mark the difference between PostgreSQL and Postgres-XC, .sgmlin
- * uses dedicated tabs <!## name> and <!## end>, where name is PG or XC
- * which indicates specific information for PostgreSQL and Postgres-XC
- * respectively.   This mechanism is introduced to make it easier
- * to merge PostgreSQL upgrades.
- *
- * In fact, name can be arbitrary identifier other than "end".  For example,
- * this can be <!## JP> or <!## EN> to indicate the language is Japanese or
- * English.
- *
- * This tool accepts the following arguments:
- *
- * -i infilename: specifies input file name. - means standard input.   If not
- *                specified, standard input will be used.
- * -o outfilename: specifies output file name. - means standard output.  If
- *                 not specified, standard output will be used.
- * -I name: specify the name tag which will be included in the output.
- *          You can specifiy this parameter as many times as needed.
- * -E name: specify the name tag which will be excluded in the output.
- *          You may specify this parameter as many times as needed.
- * -d opt: Specify the default handling of the tags which does not appear
- *         in -I or -E option.  opt can be i (include) or e (exluce).
- *         Default is e.
- *
- * To keep error massages in the following stage easy to track by the line 
- * number, excluded line will be replaced with brank line.
- *
- *--------------------------------------------------------------------------- 
- */
-#include <stdio.h>
-#include <string.h>
-#include <stdlib.h>
-#include <unistd.h>
-#include <errno.h>
-
-
-typedef struct tokenlist
-{
-	struct tokenlist *next;
-	char *token;
-} tokenlist;
-
-static int find_match(char *token, tokenlist *toks);
-static int find_match_exclude(char *token);
-static int find_match_include(char *token);
-static void usage(int exitcode);
-
-#define STARTTOKEN "<!##"
-
-tokenlist *ignoreToks = NULL;
-tokenlist *lastIgnoreToken = NULL;
-tokenlist *includeToks = NULL;
-tokenlist *lastIncludeToken = NULL;
-
-FILE *inf;
-FILE *outf;
-int inf_lno;
-char *progname;
-int default_include = 0;
-
-void make_sgml(int writeflag);
-void usage(int exitcode);
-void format_err(int lno);
-int my_getline(char *buf);
-
-int main(int argc, char *argv[])
-{
-	int  opt;
-	char *ifnam = NULL;
-	char *ofnam = NULL;
-
-	char *token;
-
-	inf = stdin;
-	outf = stdout;
-
-	progname = argv[0];
-	while ((opt = getopt(argc, argv, "i:o:E:I:d:")) != -1)
-	{
-		switch(opt) 
-		{
-			case 'i':
-				if (ifnam)
-				{
-					free(ifnam);
-					ifnam = NULL;
-				}
-
-				if ((strcmp(optarg, "-") == 0) || (strcmp(optarg, "stdin") == 0))
-					inf = stdin;
-				else
-					ifnam = strndup(optarg, strlen(optarg));
-				break;
-
-			case 'o':
-				if (ofnam)
-				{
-					free(ofnam);
-					ofnam = NULL;
-				}
-
-				if ((strcmp(optarg, "-") == 0) || (strcmp(optarg, "stdout") == 0))
-					outf = stdout;
-				else
-					ofnam = strndup(optarg, strlen(optarg));
-				break;
-
-			case 'E':
-				token = strndup(optarg,strlen(optarg));
-				if (ignoreToks == NULL)
-				{
-					ignoreToks = (tokenlist *)malloc(sizeof(tokenlist));
-					if (ignoreToks == NULL)
-						goto memerr;
-					ignoreToks->token = token;
-					ignoreToks->next = NULL;
-					lastIgnoreToken = ignoreToks;
-				}
-				else 
-				{
-					lastIgnoreToken->next = (tokenlist *)malloc(sizeof(tokenlist));
-					if (lastIgnoreToken->next == NULL)
-						goto memerr;
-					lastIgnoreToken = lastIgnoreToken->next;
-					lastIgnoreToken->next = NULL;
-					lastIgnoreToken->token = token;
-				}
-				break;
-
-			case 'I':
-				token = strndup(optarg, strlen(optarg));
-				if (includeToks == NULL)
-				{
-					includeToks = (tokenlist *)malloc(sizeof(tokenlist));
-					if (includeToks == NULL)
-						goto memerr;
-					includeToks->token = token;
-					includeToks->next = NULL;
-					lastIncludeToken = includeToks;
-				}
-				else
-				{
-					lastIncludeToken->next = (tokenlist *)malloc(sizeof(tokenlist));
-					if (lastIncludeToken->next == NULL)
-						goto memerr;
-					lastIncludeToken = lastIncludeToken->next;
-					lastIncludeToken->next = NULL;
-					lastIncludeToken->token = token;
-				}
-				break;
-
-			case 'd': /* Default handling: include/exclude */
-				if (strcmp(optarg, "i") == 0)
-					default_include = 1;
-				else if (strcmp(optarg, "e") == 0)
-					default_include = 0;
-				else
-					usage(1);
-				break;
-
-			default:
-				usage(1);
-				exit(1);
-		}
-	}
-	if (ifnam)
-	{
-		inf = fopen(ifnam, "r");
-		if (inf == NULL)
-		{
-			fprintf(stderr, "Cannot open input file %s, %s\n", ifnam, strerror(errno));
-			exit(1);
-		}
-	}
-	inf_lno = 0;
-	if (ofnam)
-	{
-		outf = fopen(ofnam, "w");
-		if (outf == NULL)
-		{
-			fprintf(stderr, "Cannot open output file %s, %s\n", ofnam, strerror(errno));
-			exit(1);
-		}
-	}
-	make_sgml(1);
-	exit(0);
-
-memerr:
-	fprintf(stderr, "Memory not available.\n");
-	exit(1);
-}
-
-int my_getline(char *buf)
-{
-	int c;
-
-	c = getc(inf);
-	if (c == EOF)
-	{
-		*buf = 0;
-		return EOF;
-	}
-	else 
-	{
-		ungetc(c, inf);
-	}
-	for (;;)
-	{
-		c = getc(inf);
-		switch(c) 
-		{
-			case '\n':
-				*buf++ = c;
-				*buf = 0;
-				inf_lno++;
-				return 1;
-			case EOF:
-				*buf = 0;
-				inf_lno++;
-				return 1;
-			default:
-				*buf++ = c;
-				continue;
-		}
-	}
-	exit(1);
-}
-
-
-static int find_match(char *token, tokenlist *toks)
-{
-	tokenlist *currToks;
-
-	for (currToks = toks; currToks; currToks = currToks->next)
-	{
-		if (strcmp(token, currToks->token) == 0)
-			return 1;
-	}
-	return 0;
-}
-
-static int find_match_exclude(char *token)
-{
-	return find_match(token, ignoreToks);
-}
-
-static int find_match_include(char *token)
-{
-	return find_match(token, includeToks);
-}
-
-void format_err(int lno)
-{
-	fprintf(stderr, "Input file format error. Line %d.\n", lno);
-	exit(1);
-}
-
-void make_sgml(int writeflag)
-{
-	int rv;
-	char inputline[4096];
-
-	for (;;)
-	{
-		char *curr;
-		char *token;
-
-		rv = my_getline(inputline);
-		if (rv == EOF)
-			return;
-		curr = inputline;
-		for (;;curr++)
-		{
-			if (*curr == ' ' || *curr == '\t')
-				continue;
-			else
-				break;
-		}
-		if (memcmp(curr, STARTTOKEN, strlen(STARTTOKEN)) == 0)
-		{
-			curr += strlen(STARTTOKEN);
-			if (*curr != ' ' && *curr != '\t')
-				format_err(inf_lno);
-
-			for (curr++;;curr++)
-			{
-				if (*curr == '\n' || *curr == 0)
-					format_err(inf_lno);
-				if (*curr == ' ' || *curr == '\t')
-					continue;
-				else
-					break;
-			}
-			token = curr;
-			for (;;curr++)
-			{
-				if (*curr == '\n' || *curr == 0)
-					format_err(inf_lno);
-
-				if (*curr == ' ' || *curr == '\t')
-				{
-					*curr = 0;
-					curr++;
-					break;
-				}
-				else if (*curr == '>')
-				{
-					*curr = 0;
-					curr++;
-					*curr = '>';
-					break;
-				}
-				else
-				{
-						continue;
-				}
-			}
-			for (;;curr++)
-			{
-				if (*curr == '\n' || *curr == 0)
-					format_err(inf_lno);
-
-					if (*curr == ' ' || *curr == '\t')
-						continue;
-					else if (*curr == '>')
-						break;
-					else
-						format_err(inf_lno);
-			}
-
-			/* You can write anything after clsing '>' */
-			fputc('\n', outf);
-			if (strcmp(token, "end") == 0)
-				return;
-			if (find_match_exclude(token))
-			{
-				make_sgml(0);
-			}
-			else if (find_match_include(token))
-			{
-				if (writeflag)
-					make_sgml(1);
-				else
-					make_sgml(0);
-			}
-			else {
-				make_sgml(0);
-			}
-		}
-		else
-		{
-			if (writeflag)
-				fputs(inputline, outf);
-			else
-				fputc('\n', outf);
-		}
-	}
-	exit(1);
-}
-
-static void usage(int exitcode)
-{
-	fprintf(stderr, 
-			"%s -i infile -o outfile [-d i|e ] -D exclude_token -D ... -U include_token -U ...\n", 
-			progname);
-	exit(exitcode);
-}